Unmaintained FreeBSD ports which are out of date
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 +-+ www/bacula-web | 8.7.0 | v9.6.0 +-+ 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!
Some ports overshooting MAKE_JOBS_NUMBER
Was running Poudriere with -J2 and its make.conf set to
MAKE_JOBS_NUMBER=6. Noticed a top terminal nearly fill with moc
processes and it said 30 processes were in a running state. The two
builds at the time were editors/calligra and graphics/digikam. Grabbing
part of a pstree view looks like ninja receives the -j6 parameter and
spawns several cmake jobs, but then each of those jobs begins spawning
several jobs.I know I've seen but not looked into other cases like what
seemed like a port's build system launching rust jobs (expected) and
rust launching multiple of its own jobs (unexpected) for ports like Firefox.
Is there active effort by porters to find and limit these cases?
Anything specific I should be doing to etiher further limit it or get
more details to track down such issues? Is there a way to have Poudriere
log such overuse to review without having to noice it live at the time?
The bloated pstree copy+pasted outout is shown below:
| | |-+= 53498 root sh: poudriere[local-local][02]: build_pkg
(calligra-3.2.1_62) (sh)
| | | \-+- 76669 root sh: poudriere[local-local][02]: build_pkg
(calligra-3.2.1_62) (sh)
| | | \-+= 76670 root /usr/bin/make -C
/usr/ports/editors/calligra build
| | | \-+- 76682 root /bin/sh -e -c (cd
/wrkdirs/usr/ports/editors/calligra/work/.build; if ! /usr/bin/env -i
HOME=/wrkdirs/usr/ports/editors/calligra/work PWD="${PWD}"
__MAKE_CONF=/nonexistent OSVERSION=1401502
PATH=/usr/local/libexec/ccache:/wrkdirs/usr/ports/editors/calligra/work/.bin:/sbin:/bin:/usr/s
bin:/usr/bin:/usr/local/sbin:/usr/local/bin:/root/bin TMPDIR=/tmp
UNAME_r=14.1-STABLE UNAME_v=FreeBSD\\ 14.1-STABLE\\ 1401502
LANG=en_US.UTF-8 LC_ALL=en_US.UTF-8 NINJA_STATUS="[%p %s/%t] "
PERL_USE_UNSAFE_INC=1 QT_SELECT=qt5
QMAKEMODULES="/wrkdirs/usr/ports/editors/calligra/work/calligra-3.2.1/mkspecs/modules:/usr/loc
al/lib/qt5/mkspecs/modules"
XDG_DATA_HOME=/wrkdirs/usr/ports/editors/calligra/work
XDG_CONFIG_HOME=/wrkdirs/usr/ports/editors/calligra/work
XDG_CACHE_HOME=/wrkdirs/usr/ports/editors/calligra/work/.cache
HOME=/wrkdirs/usr/ports/editors/calligra/work TMPDIR="/tmp"
PATH=/usr/local/libexec/ccache:/wrkdirs/usr/ports/edi
tors/calligra/work/.bin:/sbin:/bin:/usr/sbin:/usr/bin:/usr/local/sbin:/usr/local/bin:/root/bin
PKG_CONFIG_LIBDIR=/wrkdirs/usr/ports/editors/calligra/work/.pkgconfig:/usr/local/libdata/pkgconfig:/usr/local/share/pkgconfig:/usr/libdata/pkgconfig
MK_DEBUG_FILES=no MK_KERNEL_SYMBOLS=no SHELL=/bin/sh NO_LINT=YES DESTDIR=/w
rkdirs/usr/ports/editors/calligra/work/stage PREFIX=/usr/local
LOCALBASE=/usr/local CC="cc" CFLAGS="-O2 -pipe
-fstack-protector-strong -isystem /usr/local/include
-fno-strict-aliasing " CPP="cpp" CPPFLAGS="-isystem /usr/local/include"
LDFLAGS=" -Wl,--undefined-version -fstack-protector-strong
-L/usr/local/lib " L
IBS="" CXX="c++" CXXFLAGS="-O2 -pipe -fstack-protector-strong -isystem
/usr/local/include -fno-strict-aliasing -isystem /usr/local/include "
CCACHE_DIR="/root/.ccache" BSD_INSTALL_PROGRAM="install -s -m 555"
BSD_INSTALL_LIB="install -s -m 0644" BSD_INSTALL_SCRIPT="install -m
555" BSD_INSTALL_DATA="install -m
0644" BSD_INSTALL_MAN="install -m 444" ninja-j6 -v all; then if [
-n "Try to set MAKE_JOBS_UNSAFE=yes and rebuild before reporting the
failure to the maintainer
| | | \-+- 76683 root ninja -j6 -v all
| | | |-+= 86305 root /bin/sh -c cd
/wrkdirs/usr/ports/editors/calligra/work/.build/sheets &&
/usr/local/bin/cmake -E cmake_autogen
/wrkdirs/usr/ports/editors/calligra/work/.build/sheets/CMakeFiles/calligrasheetscommon_autogen.dir/AutogenInfo.json
Release && /usr/local/bin/cmake -E touch /wrkdirs/usr/po
rts/editors/calligra/work/.build/sheets/calligrasheetscommon_autogen/timestamp
&& /usr/local/bin/cmake -E cmake_transform_depfile Ninja gccdepfile
/wrkdirs/usr/ports/editors/calligra/work/calligra-3.2.1
/wrkdirs/usr/ports/editors/calligra/work/calligra-3.2.1/sheets
/wrkdirs/usr/ports/editors/calligra/work/.build /wrkd
irs/usr/ports/editors/calligra/work/.build/sheets
/wrkdirs/usr/ports/editors/calligra/work/.build/sheets/calligrasheetscommon_autogen/deps
/wrkdirs/usr/ports/editors/calligra/work/.build/CMakeFiles/d/5ce680dbe46bfba995ce82b5c752535db470d2e761d1018af14fac7e3b4b949e.d
| | | | \-+- 86306 root /usr/local/bin/cmake -E
cmake_autogen
/wrkdirs/usr/ports/editors/calligra/work/.build/sheets/CMakeFiles/calligrasheetscommon_autogen.dir/AutogenInfo.json
Release
| | | | |--- 86936 root /usr/local/lib/qt5/bin/moc
-DBOOST_ALL_NO_LIB -DHAVE_X11 -DKCOREADDONS_LIB -DKGUIADDONS_LIB
-DQT_CONCURRENT_LIB -DQT_CORE_LIB -DQT_DBUS_LIB
-DQT_DISABLE_DEPRECATED_BEFORE=0 -DQT_GUI_LIB -DQT_NETWORK_LIB
-DQT_NO_CAST_TO_ASCII -DQT_NO_DEBUG -DQT_NO_SIGNALS_SLOTS_KEYWORDS -DQT_NO_
URL_CAST_FROM_STRING -DQT_PRINTSUPPORT_LIB -DQT_SQL_LIB
-DQT_STRICT_ITERATORS -DQT_USE_QSTRINGBUILDER -DQT_WIDGETS_LIB
-DQT_XML_LIB -DSHOULD_BUIL
Using --recursive in Makefile / github clone
Hello,
is it possible to use something like --recursive in the Makefile for
github clone?
USE_GITHUB= yes
GH_TUPLE= user:proj:part:${ECLIPSE_TAG} \
user:proj:part:${ECLIPSE_TAG}:a/part \
...
I don't see it here...
Thanks! Norbert
--
I love penguins at the south pole, windows in my house and apples on my tree,
but not in my computer :)
Re: Using --recursive in Makefile / github clone
Hi Norbert,
This is not supported. You'll have to add one GH_TUPLE entry for each
submodule. I agree it would be nice to have some tooling to automatically
add the submodules to the list.
Yours,
Robert Clausecker
Am Sun, Sep 29, 2024 at 05:41:25PM +0200 schrieb Norbert Grundmann:
> Hello,
>
> is it possible to use something like --recursive in the Makefile for github
> clone?
>
> USE_GITHUB= yes
> GH_TUPLE= user:proj:part:${ECLIPSE_TAG} \
> user:proj:part:${ECLIPSE_TAG}:a/part \
> ...
>
> I don't see it here...
>
> Thanks! Norbert
>
> --
> I love penguins at the south pole, windows in my house and apples on my tree,
> but not in my computer :)
>
>
--
() ascii ribbon campaign - for an encoding-agnostic world
/\ - against html email - against proprietary attachments
Re: Using --recursive in Makefile / github clone
Hi Robert,
Thanks :-) But is it good and recommended to use an explicit
git clone --recursive repo
instead of GH_TUPLE? It would make things more easy...
Cheers, Norebrt
On 9/29/24 17:43, Robert Clausecker wrote:
Hi Norbert,
This is not supported. You'll have to add one GH_TUPLE entry for each
submodule. I agree it would be nice to have some tooling to automatically
add the submodules to the list.
Yours,
Robert Clausecker
Am Sun, Sep 29, 2024 at 05:41:25PM +0200 schrieb Norbert Grundmann:
Hello,
is it possible to use something like --recursive in the Makefile for github
clone?
USE_GITHUB= yes
GH_TUPLE= user:proj:part:${ECLIPSE_TAG} \
user:proj:part:${ECLIPSE_TAG}:a/part \
...
I don't see it here...
Thanks! Norbert
--
I love penguins at the south pole, windows in my house and apples on my tree,
but not in my computer :)
--
I love penguins at the south pole, windows in my house and apples on my tree,
but not in my computer :)
Re: Using --recursive in Makefile / github clone
On 2024-09-29T17:46:16.000+02:00, Norbert Grundmann
wrote:
> Hi Robert,
>
> Thanks :-) But is it good and recommended to use an explicit
>
> git clone --recursive repo
>
> instead of GH_TUPLE? It would make things more easy...
>
> Cheers, Norebrt
>
> On 9/29/24 17:43, Robert Clausecker wrote:
>> Hi Norbert,
>>
>> This is not supported. You'll have to add one GH_TUPLE entry for
>> each
>>
>> submodule. I agree it would be nice to have some tooling to
>> automatically
>>
>> add the submodules to the list.
>>
>> Yours,
>>
>> Robert Clausecker
>>
>> Am Sun, Sep 29, 2024 at 05:41:25PM +0200 schrieb Norbert
>> Grundmann:
>>
>>> Hello,
>>>
>>>is it possible to use something like --recursive in the
>>> Makefile for github
>>>
>>>clone?
>>>
>>>USE_GITHUB= yes
>>>
>>>GH_TUPLE= user:proj:part:${ECLIPSE_TAG} \
>>>
>>>user:proj:part:${ECLIPSE_TAG}:a/part \
>>>
>>>...
>>>
>>>I don't see it here...
>>>
>>>Thanks! Norbert
>>>
>>>--
>>>
>>>I love penguins at the south pole, windows in my house and
>>> apples on my tree, but not in my computer :)
>
> --
>
> I love penguins at the south pole, windows in my house and apples on
> my tree, but not in my computer :)
Hi.
Just a friendly reminder that this is usually done in release
archives/tarballs if upstream provides such.
Best regards,
Daniel
Re: Using --recursive in Makefile / github clone
Hi Norbert, Am Sun, Sep 29, 2024 at 05:46:16PM +0200 schrieb Norbert Grundmann: > Hi Robert, > > Thanks :-) But is it good and recommended to use an explicit > > git clone --recursive repo > > instead of GH_TUPLE? It would make things more easy... This is not permitted. We require that distfiles be fetched in the fetch phase, then be checked against the distinfo file, and only then be extracted. git-clone(1) does not permit us to do so and can thus not be used to obtain project source. If you submit a patch with this sort of stuff in the Makefile, it'll be rejected. > Cheers, Norebrt Yours, Robert Clausecker -- () ascii ribbon campaign - for an encoding-agnostic world /\ - against html email - against proprietary attachments
Re: Using --recursive in Makefile / github clone
Thanks Daniel and Robert, then I must go the recommended way :-) On 9/29/24 17:52, Robert Clausecker wrote: Hi Norbert, Am Sun, Sep 29, 2024 at 05:46:16PM +0200 schrieb Norbert Grundmann: Hi Robert, Thanks :-) But is it good and recommended to use an explicit git clone --recursive repo instead of GH_TUPLE? It would make things more easy... This is not permitted. We require that distfiles be fetched in the fetch phase, then be checked against the distinfo file, and only then be extracted. git-clone(1) does not permit us to do so and can thus not be used to obtain project source. If you submit a patch with this sort of stuff in the Makefile, it'll be rejected. Cheers, Norebrt Yours, Robert Clausecker -- I love penguins at the south pole, windows in my house and apples on my tree, but not in my computer :)
