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 +-+ lang/libobjc2 | 2.0 | v2.1 +-+ 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! ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: x11-wm/piewm: "ld: error: duplicate symbol: yylineno"
On 23 Aug 2020, at 21:35, David Wolfskill wrote: > > On Sun, Aug 23, 2020 at 06:39:10PM +, pkg-fall...@freebsd.org wrote: >> You are receiving this mail as a port that you maintain >> is failing to build on the FreeBSD package build server. >> Please investigate the failure and submit a PR to fix >> build. >> >> Maintainer: da...@catwhisker.org >> Last committer: swi...@freebsd.org >> Ident: $FreeBSD: head/x11-wm/piewm/Makefile 519608 2019-12-09 >> 13:47:16Z swills $ >> Log URL: >> http://beefy18.nyi.freebsd.org/data/head-amd64-default/p545731_s364466/logs/piewm-1.04_4.log >> Build URL: >> http://beefy18.nyi.freebsd.org/build.html?mastername=head-amd64-default&build=p545731_s364466 >> ... >> --- piewm --- >> rm -f piewm >> cc -o piewm -L/usr/local/lib gram.o lex.o deftwmrc.o add_window.o >> gc.o list.o twm.o parse.o menus.o events.o resize.o util.o >> version.o iconmgr.ocursor.o icons.o vdt.o move.o LocPixmap.o >> -lXmu -lXt -lSM -lICE -lXext -lX11 -lXt -lSM -lICE -lXext -lXext -lX11 -lm >> -ll -lXpm -Wl,-rpath,/usr/local/lib >> ld: error: duplicate symbol: yylineno > defined at gram.c > gram.o:(yylineno) > defined at lex.c > lex.o:(.data+0x0) >> cc: error: linker command failed with exit code 1 (use -v to see invocation) >> *** [piewm] Error code 1 >> >> make[1]: stopped in /wrkdirs/usr/ports/x11-wm/piewm/work/piewm-1.04 >> 1 error >> >> make[1]: stopped in /wrkdirs/usr/ports/x11-wm/piewm/work/piewm-1.04 >> ===> Compilation failed unexpectedly. >> Try to set MAKE_JOBS_UNSAFE=yes and rebuild before reporting the failure to >> the maintainer. >> *** Error code 1 >> >> Stop. >> make: stopped in /usr/ports/x11-wm/piewm > > So... I confess a lack of familiarity with lex, yacc, and their > work-alikes. It also appears that x11-wm/tvtwm (for which MAINTAINER is > this list -- po...@freebsd.org) is likely similarly affected. > > I understand that the immediate cause is a recent change; in > http://docs.FreeBSD.org/cgi/mid.cgi?B7F9F85B-60A4-4A87-9911-BDE1CBC7BC91, > dim@ mentioned: > > | This is because clang 11 (and gcc 10) now default to -fno-common. The > | rationale is explained pretty well in... > > and goes on to state: > | A quick fix is to add CFLAGS+=-fcommon to your make.conf, but that is > | rather a big hammer. It is better to add it to just the ports that show > | problems due to duplicated symbols. And ideally, those duplicated > | symbols should be patched out of the ports. > > So: apparently *a* way around this is to change the Makefile (to > include 'CFLAGS+=-fcommon') -- but I don't know if a "better" approach > is feasible: we are dealing with some rather old (or, perhaps, > "well-established") code, here. > > Advice/suggestions? In this case, "svn rm x11-wm/piewm/files/patch-gram.y" will fix it correctly. I have no idea why that patch was added in the first place, it is clearly incorrect! -Dimitry signature.asc Description: Message signed with OpenPGP
Re: x11-wm/piewm: "ld: error: duplicate symbol: yylineno"
On Mon, Aug 24, 2020 at 10:11:45AM +0200, Dimitry Andric wrote: > > > Advice/suggestions? > > In this case, "svn rm x11-wm/piewm/files/patch-gram.y" will fix it > correctly. I have no idea why that patch was added in the first place, > it is clearly incorrect! > > -Dimitry > Thank you very much! I will verify that and send in a correct fix once I do. Peace, david -- David H. Wolfskill da...@catwhisker.org "Those countries that have lost control of the virus like the United States are seeing economic forecasts constantly revised down and are weaker economically." -- Dominick Stephens, Westpac NZ's chief economist See http://www.catwhisker.org/~david/publickey.gpg for my public key. signature.asc Description: PGP signature
deprecation of drm-legacy-kmod
[ cross posted across several mailing lists, please respect reply-to ] Hi! It is time to deprecate drm-legacy-kmod, since it is taking too much time to maintain and are holding off changes in other areas. drm-legacy-kmod was created to aid in the transition to the LinuxKPI based graphics drivers, at a time when the new drivers only supported amd64. Since then, the new drivers have been updated to support more architectures and more GPUs, and the burden of maintaining drm-legacy-kmod has increased. It became apparent with the update of xorg-server to 1.20 that drm-legacy-kmod is too old to work with certain aspects of the graphics stack, and it is also holding back changes in areas of the FreeBSD base system such as VM scaling and optimization. The VM locking protocol needs to be changed, and to port those changes to these drivers would require extensive reworking of its use of the FreeBSD VM subsystem. This means it is time for it to go. The driver will remain for a transition period. For FreeBSD 13-CURRENT, this will be fairly short, as there are changes to FreeBSD base that breaks the drivers. For FreeBSD 12, the driver will remain a bit longer, to ease in transition. On FreeBSD 12, there is also the option of using the graphics drivers in base, although those are supported on a best-effort basis only. Regards -- Niclas Zeising FreeBSD Graphics Team ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: deprecation of drm-legacy-kmod
On 2020-08-24 18:21, Niclas Zeising wrote: > [ cross posted across several mailing lists, please respect reply-to ] > > Hi! > > It is time to deprecate drm-legacy-kmod [...] it is time for it to go. > > The driver will remain for a transition period. For FreeBSD 13-CURRENT, > this will be fairly short, as there are changes to FreeBSD base that > breaks the drivers. For FreeBSD 12, the driver will remain a bit > longer, to ease in transition. On FreeBSD 12, there is also the option > of using the graphics drivers in base, although those are supported on a > best-effort basis only. [...] My secret decoder ring is telling me the implicit message here (along with a recent Qt5 "upgrade") is that the FreeBSD home page explicit statement that the 11.3 and 11.4 releases of FreeBSD are in production status is a bit of a lie. I know I'm going to have to upgrade to 12 sooner or later, but I just don't have a warm, fuzzy feeling about that right now. Forgive me for venting ...-- George signature.asc Description: OpenPGP digital signature
What are my options regarding deprecated PyPy port?
Hi, I'm new to FreeBSD-- I installed it for the first time this week. Honestly, so far it has exceeded expectations. I installed X11, but the first thing I installed was PyPy2. Unlike CPython2, which is EOL'd, PyPy2 does not to the best of my knowledge depend on CPython. When I installed it with pkg, it said the port was deprecated and will be removed from ports soon-- but it also said it was based on Python 2.7 (which is EOLd). I think there is a misunderstanding there. PyPy states the intention to continue to maintain that version. Removing this port is unnecessary. Aware of the politics around this (which go way over FreeBSD anyway) I doubt I will convince someone to save this port, sadly. I've used both Python 2.x and 3.x for years now. If this problem can't be fixed, can I at least be put in touch with the current port maintainer so that I can learn how to maintain this as a 3rd party package for my own use? I'm certain I'm not up to becoming an official port maintainer at this stage, but I'd like to be able to at least compile and run PyPy2 on freebsd without redoing the ports work that was already done on this. ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: What are my options regarding deprecated PyPy port?
On Mon, Aug 24, 2020 at 6:50 PM figosdev via freebsd-ports < freebsd-ports@freebsd.org> wrote: > Hi, I'm new to FreeBSD-- I installed it for the first time this week. > Honestly, so far it has exceeded expectations. > > I installed X11, but the first thing I installed was PyPy2. > > Unlike CPython2, which is EOL'd, PyPy2 does not to the best of my > knowledge depend on CPython. When I installed it with pkg, it said the port > was deprecated and will be removed from ports soon-- but it also said it > was based on Python 2.7 (which is EOLd). > > I think there is a misunderstanding there. PyPy states the intention to > continue to maintain that version. > > Removing this port is unnecessary. Aware of the politics around this > (which go way over FreeBSD anyway) I doubt I will convince someone to save > this port, sadly. > > I've used both Python 2.x and 3.x for years now. If this problem can't be > fixed, can I at least be put in touch with the current port maintainer so > that I can learn how to maintain this as a 3rd party package for my own use? > > I'm certain I'm not up to becoming an official port maintainer at this > stage, but I'd like to be able to at least compile and run PyPy2 on freebsd > without redoing the ports work that was already done on this. > Looks like the deprecation might have been in error. While I can't be sure, it looks like it is in no way dependent on python27 and, if it is maintained, it probably was deprecated in error. Probably someone in the python group saw the 2.7 references and tagged it for deprecation. You probably should start by contacting python@ and, if there is no response, open a ticket on bugzilla pointing this out and requesting that the deprecation be reversed. -- Kevin Oberman, Part time kid herder and retired Network Engineer E-mail: rkober...@gmail.com PGP Fingerprint: D03FB98AFA78E3B78C1694B318AB39EF1B055683 ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: What are my options regarding deprecated PyPy port?
On 8/24/20 8:05 PM, Kevin Oberman wrote: On Mon, Aug 24, 2020 at 6:50 PM figosdev via freebsd-ports < freebsd-ports@freebsd.org> wrote: Hi, I'm new to FreeBSD-- I installed it for the first time this week. Honestly, so far it has exceeded expectations. I installed X11, but the first thing I installed was PyPy2. Unlike CPython2, which is EOL'd, PyPy2 does not to the best of my knowledge depend on CPython. When I installed it with pkg, it said the port was deprecated and will be removed from ports soon-- but it also said it was based on Python 2.7 (which is EOLd). I think there is a misunderstanding there. PyPy states the intention to continue to maintain that version. Removing this port is unnecessary. Aware of the politics around this (which go way over FreeBSD anyway) I doubt I will convince someone to save this port, sadly. I've used both Python 2.x and 3.x for years now. If this problem can't be fixed, can I at least be put in touch with the current port maintainer so that I can learn how to maintain this as a 3rd party package for my own use? I'm certain I'm not up to becoming an official port maintainer at this stage, but I'd like to be able to at least compile and run PyPy2 on freebsd without redoing the ports work that was already done on this. Looks like the deprecation might have been in error. While I can't be sure, it looks like it is in no way dependent on python27 and, if it is maintained, it probably was deprecated in error. Probably someone in the python group saw the 2.7 references and tagged it for deprecation. You probably should start by contacting python@ and, if there is no response, open a ticket on bugzilla pointing this out and requesting that the deprecation be reversed. i agree - it looks like someone needs to refactor lang/pypy which seems to build against python2.7. there is a pypy3 port/pkg as well, but that seems to be incorrectly flagged as being deprecated according to freshports. i searched bugzilla too but only found an open cleanup ticket there: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=245747 -pete -- Pete Wright p...@nomadlogic.org @nomadlogicLA ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: What are my options regarding deprecated PyPy port?
Thank you both. Per Kevin's advice I have contacted freebsd-python@ and wait to hear what they say about this. I am not above getting the PyPy devs on this if necessary. I find it hard to believe that an implementation they say will be around hard-depends on an implementation that will not. The port itself could be another story. PyPy implements Python 2, so they should be able at this point to use PyPy to build PyPy if they don't already. If I could run the ELF version on FreeBSD I'd take that over nothing, but I've meant to try FreeBSD again for years (possibly migrating to it) and I've only read the FAQ and part of the handbook so far. Still learning. ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
