Ressurect port

[Nuno Teixeira]

Hello,

I need to ressurect net/slurm port for PR265070
 and I can see it
in log:

git log -- net/slurm:
---
commit 5771a967158e217b1e70655b459ce9769124bd49
Author: Antoine Brodin 
Date:   Sat Apr 4 20:51:40 2020 +

Deprecate ports broken for more than 6 months
---
(...)

What git cmd should I do to get it back?

Thanks,

Nuno Teixeira

Re: Ressurect port

[Vasily Postnicov]

git revert 5771a96

But if it is broken this won't help you :)

пт, 8 июл. 2022 г., 11:01 Nuno Teixeira :

> Hello,
>
> I need to ressurect net/slurm port for PR265070
>  and I can see
> it in log:
>
> git log -- net/slurm:
> ---
> commit 5771a967158e217b1e70655b459ce9769124bd49
> Author: Antoine Brodin 
> Date:   Sat Apr 4 20:51:40 2020 +
>
> Deprecate ports broken for more than 6 months
> ---
> (...)
>
> What git cmd should I do to get it back?
>
> Thanks,
>
> Nuno Teixeira
>

Re: Ressurect port

[Nuno Teixeira]

Hello!

Thanks for the tip.

I've found a better commit to revert:
---
commit 266495ae1ca8e417c22d01644daa28cb0c4938ce
Author: Michael Landin 
Date:   Wed Nov 7 10:02:00 2018 +

- fix build on 12.x (remove obsolete network support / IFM_FDDI)
- add LICENSE
- update patch format to make portlint happy
- bump port revision

Reported by:pkg-fallout@
---

With this revert I got Makefile and files/ back (misses pkg-descr and
distinfo) but it will be ok so it can be updated.

When update is ready I'm thinking do 'git revert
266495ae1ca8e417c22d01644daa28cb0c4938ce' and commit it, and second, apply
update patch and commit it.

Is that procedure correct?


Vasily Postnicov  escreveu no dia sexta, 8/07/2022
à(s) 09:08:

> git revert 5771a96
>
> But if it is broken this won't help you :)
>
> пт, 8 июл. 2022 г., 11:01 Nuno Teixeira :
>
>> Hello,
>>
>> I need to ressurect net/slurm port for PR265070
>>  and I can see
>> it in log:
>>
>> git log -- net/slurm:
>> ---
>> commit 5771a967158e217b1e70655b459ce9769124bd49
>> Author: Antoine Brodin 
>> Date:   Sat Apr 4 20:51:40 2020 +
>>
>> Deprecate ports broken for more than 6 months
>> ---
>> (...)
>>
>> What git cmd should I do to get it back?
>>
>> Thanks,
>>
>> Nuno Teixeira
>>
>

Re: Ressurect port

[Vasily Postnicov]

Yes. You can also do git revert 266495a, then apply patches, then do git
add  and git commit --amend to have a working port
in one commit. Then you can try to submit the resurrected port according to
the porter's handbook.

пт, 8 июл. 2022 г., 11:59 Nuno Teixeira :

> Hello!
>
> Thanks for the tip.
>
> I've found a better commit to revert:
> ---
> commit 266495ae1ca8e417c22d01644daa28cb0c4938ce
> Author: Michael Landin 
> Date:   Wed Nov 7 10:02:00 2018 +
>
> - fix build on 12.x (remove obsolete network support / IFM_FDDI)
> - add LICENSE
> - update patch format to make portlint happy
> - bump port revision
>
> Reported by:pkg-fallout@
> ---
>
> With this revert I got Makefile and files/ back (misses pkg-descr and
> distinfo) but it will be ok so it can be updated.
>
> When update is ready I'm thinking do 'git revert
> 266495ae1ca8e417c22d01644daa28cb0c4938ce' and commit it, and second, apply
> update patch and commit it.
>
> Is that procedure correct?
>
>
> Vasily Postnicov  escreveu no dia sexta,
> 8/07/2022 à(s) 09:08:
>
>> git revert 5771a96
>>
>> But if it is broken this won't help you :)
>>
>> пт, 8 июл. 2022 г., 11:01 Nuno Teixeira :
>>
>>> Hello,
>>>
>>> I need to ressurect net/slurm port for PR265070
>>>  and I can
>>> see it in log:
>>>
>>> git log -- net/slurm:
>>> ---
>>> commit 5771a967158e217b1e70655b459ce9769124bd49
>>> Author: Antoine Brodin 
>>> Date:   Sat Apr 4 20:51:40 2020 +
>>>
>>> Deprecate ports broken for more than 6 months
>>> ---
>>> (...)
>>>
>>> What git cmd should I do to get it back?
>>>
>>> Thanks,
>>>
>>> Nuno Teixeira
>>>
>>

Unmaintained FreeBSD ports which are out of date

[portscout]

Dear port maintainers,

The portscout new distfile checker has detected that one or more
unmaintained ports appears to be out of date. Please take the opportunity
to check each of the ports listed below, and if possible and appropriate,
submit/commit an update. Please consider also adopting this port.
If any ports have already been updated, you can safely ignore the entry.

An e-mail will not be sent again for any of the port/version combinations
below.

Full details can be found at the following URL:
http://portscout.freebsd.org/po...@freebsd.org.html


Port| Current version | New version
+-+
comms/conserver-com | 8.2.6   | v8.2.7
+-+


If any of the above results are invalid, please check the following page
for details on how to improve portscout's detection and selection of
distfiles on a per-port basis:

http://portscout.freebsd.org/info/portscout-portconfig.txt

Reported by:portscout!

Ports System not matching upstream build, causes broken builds

[Mel Pilgrim]

I'm working on a port of rbsec/sslscan (github), but running into an 
issue where the Ports System is invoking gmake in a way that doesn't 
match what the upstream Makefile does.  The software has two build 
options: build a dynamic-linked version against the system OpenSSL 
library, or build a static-linked version against a bundled copy of 
OpenSSL 1.1.1-stable.  `gmake` gets you the dynamic version, `gmake 
static` gets you the static version.


Simple enough, so I put this in the port Makefile:

OPTIONS_DEFINE= STATIC
STATIC_USES_OFF=ssl
STATIC_ALL_TARGET=static

The port does call the static target as expected, but something is going 
terribly wrong and the result is polluted CFLAGS and LDFLAGS.  An 
example is the cc invocation to build the sslscan binary itself.  Below 
is that call for each of direct/port and static/dynamic build, with 
line-breaks added for ease of comparison:


Direct static build:

# gmake static
cc -o sslscan
-Wall -Wformat=2 -Wformat-security -Wno-deprecated-declarations
-pie -z relro -z now
-L/tmp/scratch/sslscan/openssl/
-D_FORTIFY_SOURCE=2 -fstack-protector-all -fPIE -std=gnu11
-I/tmp/scratch/sslscan/openssl/include/ -I/tmp/scratch/sslscan/openssl/
-DVERSION=\"2.0.15-static\" sslscan.c -lssl -lcrypto -lz -lpthread

Port build with STATIC on:

# make
cc -o sslscan
-Wall -Wformat=2 -Wformat-security -Wno-deprecated-declarations
-fstack-protector-strong
-pie -z relro -z now
-L/usr/local/lib -L/usr/local/ssl/lib -L/usr/local/opt/openssl/lib 
-L/opt/local/lib

-pie -z relro -z now
-L/poudriere/ports/default/security/sslscan/work/sslscan-2.0.15/openssl/
-O2 -pipe  -fstack-protector-strong -fno-strict-aliasing
-D_FORTIFY_SOURCE=2 -fstack-protector-all -fPIE -std=gnu11
-I/usr/local/include -I/usr/local/ssl/include 
-I/usr/local/ssl/include/openssl -I/usr/local/opt/openssl/include 
-I/opt/local/include -I/opt/local/include/openssl

-D_FORTIFY_SOURCE=2 -fstack-protector-all -fPIE -std=gnu11
-I/poudriere/ports/default/security/sslscan/work/sslscan-2.0.15/openssl/include/ 
-I/poudriere/ports/default/security/sslscan/work/sslscan-2.0.15/openssl/

-DVERSION=\"2.0.15-static\" sslscan.c -lssl -lcrypto -lz -lpthread

Direct dynamic build:

# gmake
cc -o sslscan
-Wall -Wformat=2 -Wformat-security -Wno-deprecated-declarations
-pie -z relro -z now
-L/usr/local/lib -L/usr/local/ssl/lib -L/usr/local/opt/openssl/lib 
-L/opt/local/lib

-D_FORTIFY_SOURCE=2 -fstack-protector-all -fPIE -std=gnu11
-I/usr/local/include -I/usr/local/ssl/include 
-I/usr/local/ssl/include/openssl -I/usr/local/opt/openssl/include 
-I/opt/local/include -I/opt/local/include/openssl

-DVERSION=\"2.0.15\" sslscan.c -lssl -lcrypto

Port build with STATIC off:

# make
cc -o sslscan
-Wall -Wformat=2 -Wformat-security -Wno-deprecated-declarations
-Wl,-rpath,/usr/local/lib -fstack-protector-strong
-pie -z relro -z now
-L/usr/local/lib -L/usr/local/ssl/lib -L/usr/local/opt/openssl/lib 
-L/opt/local/lib

-O2 -pipe  -fstack-protector-strong -fno-strict-aliasing
-D_FORTIFY_SOURCE=2 -fstack-protector-all -fPIE -std=gnu11
-I/usr/local/include -I/usr/local/ssl/include 
-I/usr/local/ssl/include/openssl -I/usr/local/opt/openssl/include 
-I/opt/local/include -I/opt/local/include/openssl

-DVERSION=\"2.0.15\" sslscan.c -lssl -lcrypto


Why is the port doing this and what bits of Makefile do I need to add to 
the skeleton to make it behave correctly?