FreeBSD ports you maintain which are out of date
Dear port maintainer, The portscout new distfile checker has detected that one or more of your 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. If any ports have already been updated, you can safely ignore the entry. You will not be e-mailed 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 +-+ security/py-ailment | 9.0.5405| v9.1.11611 +-+ 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!
RFC for updating TEX to 2021
Hi,
I have been able to port TEX 2021 but there are some failures and caveats which
I wanted to discuss with the community. I have checked only the ports that has
USE_TEX in their Makefile :
What changed and what are the failures:
1. cslatex support has been DEPRECATED upstream
2. print/tex-aleph has been removed as upstream has also removed it
3. Fails to build
- databases/bbdb (Last release was on 2018)
- misc/latex-mk (Last release was on 2010)
- textproc/dblatex (The location of the required file has changed can be
easily patched)
- textproc/bibtool (Someone with latex knowledge should be able to fix this)
- print/sgf2tex (Last release was on 2001)
- print/lgrind (Last release was on 2001)
- print/muttprint (Last release was on 2008)
- cad/alliance (Last release was on 2019)
- math/asymptote (Should be able to fix this later with someone’s help who
knows)
4. Dependents
- print/lilypond{-devel} depends on textproc/dblatex but if we upgrade
lilypond it will no longer require dblatex
In case someone want to check the logs they are available here:
http://pdr.bofh.network/jail.html?mastername=123-tex
http://pdr.bofh.network/jail.html?mastername=123i386-tex
http://pdr.bofh.network/jail.html?mastername=130-tex
http://pdr.bofh.network/jail.html?mastername=MAIN-tex
So my question is whether if we are okay with UPDATING to 2021 while these
10/12 ports are BROKEN/IGNORED? I am looking forward to move forward a bit
faster as there are lots of files involved and the files changes every now and
then and merging everytime is really painful with this big of a patchset.
Thanks in advance for advices and flames. :D
Kind Regards,
Moin (bofh)
signature.asc
Description: Message signed with OpenPGP
Re: RFC for updating TEX to 2021
Moin moin
Please ship it, before the tree moves again too much for it to apply.
Marking 10-12 ports as broken is fine.
mfg Tobias
On Mon, 31 Jan 2022 at 18:57, Muhammad Moinur Rahman wrote:
>
> Hi,
>
> I have been able to port TEX 2021 but there are some failures and caveats
> which I wanted to discuss with the community. I have checked only the ports
> that has USE_TEX in their Makefile :
>
> What changed and what are the failures:
> 1. cslatex support has been DEPRECATED upstream
> 2. print/tex-aleph has been removed as upstream has also removed it
> 3. Fails to build
> - databases/bbdb (Last release was on 2018)
> - misc/latex-mk (Last release was on 2010)
> - textproc/dblatex (The location of the required file has changed can be
> easily patched)
> - textproc/bibtool (Someone with latex knowledge should be able to fix this)
> - print/sgf2tex (Last release was on 2001)
> - print/lgrind (Last release was on 2001)
> - print/muttprint (Last release was on 2008)
> - cad/alliance (Last release was on 2019)
> - math/asymptote (Should be able to fix this later with someone’s help who
> knows)
> 4. Dependents
> - print/lilypond{-devel} depends on textproc/dblatex but if we upgrade
> lilypond it will no longer require dblatex
>
> In case someone want to check the logs they are available here:
> http://pdr.bofh.network/jail.html?mastername=123-tex
> http://pdr.bofh.network/jail.html?mastername=123i386-tex
> http://pdr.bofh.network/jail.html?mastername=130-tex
> http://pdr.bofh.network/jail.html?mastername=MAIN-tex
>
> So my question is whether if we are okay with UPDATING to 2021 while these
> 10/12 ports are BROKEN/IGNORED? I am looking forward to move forward a bit
> faster as there are lots of files involved and the files changes every now
> and then and merging everytime is really painful with this big of a patchset.
>
> Thanks in advance for advices and flames. :D
>
> Kind Regards,
> Moin (bofh)
Review/Commit for PR?
Hi, Are there any committers willing to review/commit: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=261044 It's been stuck at 'New' since 10-Jan-2022. Thanks! -- Jonathan Chen
Re: Review/Commit for PR?
Hi! > Are there any committers willing to review/commit: > https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=261044 > > It's been stuck at 'New' since 10-Jan-2022. Done. -- p...@opsec.eu+49 171 3101372Now what ?
crowdsec update
Hello, I have a pending port update since a couple of weeks in https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=261304 It fixes a blocking bug and is a requirement for an opnsense plugin that I am testing. If someone could have a look and commit, I will be able to publish the plugin too. Thanks
sysutils/tracker3 build failure, due to asciidoc xsl pages relocation
Since the last asciidoc upgrade, sysutils/trackers3 build raises the following error: [ 1% 11/232] /usr/local/bin/xsltproc --output docs/manpages/tracker3-endpoint.1 --stringparam man.authors.section.enabled 0 /usr/local/etc/asciidoc/docbook-xsl/manpage.xsl docs/manpages/tracker3-endpoint.1.xml FAILED: docs/manpages/tracker3-endpoint.1 xsltproc failed because the file 'manpage.xsl' is now located elsewhere: david:~>cat /usr/ports/sysutils/tracker3/files/patch-docs_manpages_meson.build --- docs/manpages/meson.build.orig2021-06-11 22:30:57 UTC +++ docs/manpages/meson.build @@ -32,7 +32,7 @@ foreach m : manpages command: [xsltproc, '--output', '@OUTPUT@', '--stringparam', 'man.authors.section.enabled', '0', - '/etc/asciidoc/docbook-xsl/manpage.xsl', '@INPUT@'], + '/usr/local/lib/python3.8/site-packages/asciidoc/resources/docbook-xsl/manpage.xsl', '@INPUT@'], input: xml, output: manpage, install: true, - The new asciidoc port miss the pkg-plist file. - Patching the port that way solved the issue. But it sounds that this case also involves a more general problem. How did the other ports that also call asciidoc against xsl files handled this problem ? regards. -- David Marec http://wiki.fug-fr.org/doku.php?id=start -- David Marec http://wiki.fug-fr.org/doku.php?id=start
Re: Modular fetch design proposal: Was: [HEADSUP] Deprecation of the ftp support in pkg
On 24.01.22 16:37, Freddie Cash wrote: Isn't that just reinventing libfetch which is already in the base install? My proposal is about empowering users to hook in their own loosely fetch helpers instead of implementing a common API to fetch from a handful of preselected URL schemas, but it would make sense to include a libfetch based helper for the protocols implemented by libfetch as part of pkg if only to make sure my design is powerful enough and not to hard to implement.
