Re: Maintainer timeout on textproc/py-markdown update on Bugzilla - safe to commit?
On 5/05/2021 6:47 am, Michael Gmelin wrote: On 4. May 2021, at 22:45, Neel Chauhan wrote: Hi, There is an update to the port textproc/py-markdown but the maintainer, koobs@ has not responded even when (I believe) it could be committed. Bugzilla PR: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=239070 Assuming no dependent ports have an issue with this update, would it be safe to commit this with a maintainer timeout if koobs@ hasn't responded? I'm asking since I don't want to prematurely commit ports. This port needs to be updated in order to import GTK+ 4 which in turn needs to update x11-toolkits/pango (which in turn needs this update). Cc Koobs - looking at the pr, it seems like it was complicated and a lot of other work had to be done first. -m There's no problem bumping issues and for me at least, I'm usually very clear on explicitly mentioning what needs to happen (even in my absence) for something to land so anyone can do that. I will always approve and unblock well-tested change proposals. ___ 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: /usr/ports/print/ghostscript9-agpl-base gs_ll3.ps: Error: /undefinedresource (fwd)
Hi, Reference:
> From: =?UTF-8?B?VMSzbA==?= Coosemans
> Date: Tue, 4 May 2021 22:47:13 +0200
=?UTF-8?B?VMSzbA==?= Coosemans wrote:
> On Tue, 04 May 2021 22:01:46 +0200 "Julian H. Stacey"
> wrote:
> >> Delete all those .pkgsave files. These are backups created by pkg when
> >> it has to install a file over an existing file. It means a previous
> >> version of ghostscript wasn't deleted properly.
> >
> > Thanks Coosemans, I ran my compare+delete
> > http://berklix.com/~jhs/src/bsd/jhs/bin/public/cmpd/cmpd.c
> > cmpd -d -v \
> > /usr/local/share/ghostscript/fonts/Fontmap.pkgsave \
> > /usr/local/share/ghostscript/fonts/Fontmap
> > cmpd -d -v \
> > /usr/local/share/ghostscript/9.52/Resource/Init/Fontmap.pkgsave \
> > /usr/local/share/ghostscript/9.52/Resource/Init/Fontmap
> > cmpd -d -v \
> > /usr/local/share/ghostscript/9.52/Resource/Init/Fontmap.GS.pkgsave \
> > /usr/local/share/ghostscript/9.52/Resource/Init/Fontmap.GS
> > All identical & deleted.
> >
> > & rebooted but no better, gs still fails.
>
> In your original message there were more than these 3. Did you delete
> all of them? Try "find /usr/local/share/ghostscript -name '*.pkgsave'".
Oops tons of them, so I did this:
cd /usr/local
find . -name \*\.pkgsave\* | wc -l # 321798
find . -name \*\.pkgsave\* | xargs rm # A few with spaces in names
find . -name \*\.pkgsave\* -exec rm {} \;
find . -name \*\.pkgsave\* -print
reboot
Fixed it ! gs works now, brings up a panel inside X11 :-)
Thanks Coosemans !!
I've also purged all pkgsave on all other bootable partitions on
this host & another.
There's no cron driven warning of pollution available from /usr/src
/usr/ports/ports-mgmt/pkg/
work/pkg-1.16.3/NEWS
work/pkg-1.16.3/libpkg/pkg_add.c
work/pkg-1.16.3/tests/frontend/configmerge.sh
work/pkg-1.16.3/tests/frontend/conflicts.sh
pkg-check would seem a plausible name to include a find of .pkgsave ?
Cheers,
--
Julian Stacey http://berklix.com/jhs/ http://stolenvotes.uk
UK for Brexit stole 750K votes from Brits in EU of 3.7M globaly. Zap BoJo Mogg.
___
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: Making a port to use OpenSSL of ports collection on FreeBSD 11.x
> On 4. May 2021, at 21:50, Yasuhiro Kimura wrote: > > Hello, > > Of the currently supported FreeBSD versions, base system of FreeBSD > 11.x uses OpenSSL 1.0.2 and that of FreeBSD 12.x or later use OpenSSL > 1.1.1. > > Then when new version of an application dropped suport of OpenSSL > 1.0.2, is there any way to make the port of it to use OpenSSL of ports > collection if the system is FreeBSD 11.x? > See https://docs.freebsd.org/en/books/porters-handbook/uses/#uses-ssl Best > Best Regards. > > --- > Yasuhiro Kimura > ___ > 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" ___ 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: Maintainer timeout on textproc/py-markdown update on Bugzilla - safe to commit?
> On 4. May 2021, at 22:45, Neel Chauhan wrote: > > Hi, > > There is an update to the port textproc/py-markdown but the maintainer, > koobs@ has not responded even when (I believe) it could be committed. > > Bugzilla PR: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=239070 > > Assuming no dependent ports have an issue with this update, would it be safe > to commit this with a maintainer timeout if koobs@ hasn't responded? > > I'm asking since I don't want to prematurely commit ports. > > This port needs to be updated in order to import GTK+ 4 which in turn needs > to update x11-toolkits/pango (which in turn needs this update). > Cc Koobs - looking at the pr, it seems like it was complicated and a lot of other work had to be done first. -m > -Neel (nc@) > ___ > 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" ___ 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: /usr/ports/print/ghostscript9-agpl-base gs_ll3.ps: Error: /undefinedresource (fwd)
On Tue, 04 May 2021 22:01:46 +0200 "Julian H. Stacey" wrote: >> Delete all those .pkgsave files. These are backups created by pkg when >> it has to install a file over an existing file. It means a previous >> version of ghostscript wasn't deleted properly. > > Thanks Coosemans, I ran my compare+delete > http://berklix.com/~jhs/src/bsd/jhs/bin/public/cmpd/cmpd.c > cmpd -d -v \ > /usr/local/share/ghostscript/fonts/Fontmap.pkgsave \ > /usr/local/share/ghostscript/fonts/Fontmap > cmpd -d -v \ > /usr/local/share/ghostscript/9.52/Resource/Init/Fontmap.pkgsave \ > /usr/local/share/ghostscript/9.52/Resource/Init/Fontmap > cmpd -d -v \ > /usr/local/share/ghostscript/9.52/Resource/Init/Fontmap.GS.pkgsave \ > /usr/local/share/ghostscript/9.52/Resource/Init/Fontmap.GS > All identical & deleted. > > & rebooted but no better, gs still fails. In your original message there were more than these 3. Did you delete all of them? Try "find /usr/local/share/ghostscript -name '*.pkgsave'". ___ 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"
Maintainer timeout on textproc/py-markdown update on Bugzilla - safe to commit?
Hi, There is an update to the port textproc/py-markdown but the maintainer, koobs@ has not responded even when (I believe) it could be committed. Bugzilla PR: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=239070 Assuming no dependent ports have an issue with this update, would it be safe to commit this with a maintainer timeout if koobs@ hasn't responded? I'm asking since I don't want to prematurely commit ports. This port needs to be updated in order to import GTK+ 4 which in turn needs to update x11-toolkits/pango (which in turn needs this update). -Neel (nc@) ___ 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: /usr/ports/print/ghostscript9-agpl-base gs_ll3.ps: Error: /undefinedresource (fwd)
Hi, Reference: > From: =?UTF-8?B?VMSzbA==?= Coosemans > Date: Tue, 4 May 2021 17:51:05 +0200 =?UTF-8?B?VMSzbA==?= Coosemans wrote: > On Tue, 04 May 2021 16:29:47 +0200 "Julian H. Stacey" > wrote: > > Hi ports@ people, > > I wrote this to doc...@freebsd.org Sun, 02 May 2021 23:43:44 +0200 > > but no reply by Tue May 4 16:26:48 CEST 2021. > > Have others seen similar or got ideas to fix gs ghostscript ? > > --- > > > > Hi doc...@freebsd.org > > as MAINTAINER= in /usr/ports/print/ghostscript9-agpl-base > > > > I'm stuck, gs fails to start, suggestions please ? > > > > FreeBSD lapr.js.berklix.net 12.2-STABLE FreeBSD 12.2-STABLE #1038: Mon Feb > > 15 02:04:28 CET 2021 > > j...@lapr.no.berklix.net:/data/release/s2/usr/src/sys/amd64/compile/LAPR.small > > amd64 > > > > % printenv > > PATH=/sbin:/bin:/usr/sbin:/usr/bin:/usr/games:/usr/local/bin > > TERM=xterm > > DESTDIR=/ > > TERMPATH=/etc/termcap:/usr/share/misc/termcap > > NOCLEANDEPENDS= > > % printenv > > PATH=/sbin:/bin:/usr/sbin:/usr/bin:/usr/games:/usr/local/bin > > TERM=xterm > > DESTDIR=/ > > TERMPATH=/etc/termcap:/usr/share/misc/termcap > > NOCLEANDEPENDS= > > > > % which gs > > /usr/local/bin/gs > > % ls -l /usr/local/bin/gs > > - -rwxr-xr-x 1 root wheel 7648 Apr 29 11:02 /usr/local/bin/gs* > > > > gs > > GPL Ghostscript 9.52 (2020-03-19) > > Copyright (C) 2020 Artifex Software, Inc. All rights reserved. > > This software is supplied under the GNU AGPLv3 and comes with NO WARRANTY: > > see the file COPYING for details. > > While reading gs_ll3.ps: > > Error: /undefinedresource in findresource > > Operand stack: > > > > (gs_icc.ps\000gs_mex_e.ps\000gs_mro_e.ps\000gs_pdf_e.ps\000gs_wan_e.ps\000pdf_ops.ps\000pdf_rbld.ps\000pdf_base.ps\000pdf_draw.ps\000gs_cff.ps\000gs_mgl_e.ps\000gs_ttf.ps\000pdf_font.ps\000pdf_main.ps\000pdf_sec.ps\000gs_epsf.ps\000gs_pdfwr.ps) > >(gs_ll3.ps) 1 Pscript5Idiom.pkgsave IdiomSet 6 > > Pscript5Idiom.pkgsave > > Execution stack: > >%interp_exit --nostringval-- findresource %loop_continue > > findresource findresource findresource false 1 %stopped_push > > --nostringval-- 1902 7 5 %oparray_pop findresource findresource > > --dict:16/18(ro)(G)-- --dict:2/2(G)-- findresource 2 > > %dict_continue findresource findresource 1900 5 5 %oparray_pop > > findresource %errorexec_pop findresource findresource findresource > > findresource > > Dictionary stack: > >--dict:943/1123(G)-- --dict:0/20(G)-- --dict:77/200(L)-- > > --dict:943/1123(G)-- --dict:38/43(G)-- --dict:16/18(ro)(G)-- > > Current allocation mode is global > > Current file position is 18941 > > > > Any ideas please ? > > I rebuilt my machine with make worl & generic then custom kernel & > > a load of downloaded pkg > > pkg info -a | wc -l > > 1348 > > > > ive since run > > cd /usr/ports/print/ghostscript9-agpl-base > > make clean > > make reinstall > > > > gs -help > > ends > >/usr/local/share/ghostscript/9.52/Resource/Init : > >/usr/local/share/ghostscript/9.52/lib : > >/usr/local/share/ghostscript/9.52/Resource/Font : > >/usr/local/share/ghostscript/fonts : /usr/local/share/fonts > >Ghostscript is also using fontconfig to search for font files > > > > my /usr/local/share/ghostscript/9.52/Resource/ has no Init should it ? > > drwxr-xr-x 2 root bin 4608 May 2 22:33 ./ > > drwxr-xr-x 11 root bin 512 May 2 22:33 ../ > > - -rw-r--r-- 1 root wheel3297 May 2 22:23 FAPIcidfmap > > - -rw-r--r-- 1 root wheel3297 Jun 16 2020 FAPIcidfmap.pkgsave > > - -rw-r--r-- 1 root wheel1158 May 2 22:23 FAPIconfig > > - -rw-r--r-- 1 root wheel1158 Jun 16 2020 FAPIconfig.pkgsave > > - -rw-r--r-- 1 root wheel1468 May 2 22:23 FAPIfontmap > > - -rw-r--r-- 1 root wheel1468 Jun 16 2020 FAPIfontmap.pkgsave > > - -rw-r--r-- 1 root wheel2857 May 2 22:23 FCOfontmap-PCLPS2 > > - -rw-r--r-- 1 root wheel2857 Jun 16 2020 FCOfontmap-PCLPS2.pkgsave > > - -rw-r--r-- 1 root wheel 109 May 2 22:23 Fontmap > > - -rw-r--r-- 1 root wheel 12929 May 2 22:23 Fontmap.GS > > - -rw-r--r-- 1 root wheel 12929 Jun 16 2020 Fontmap.GS.pkgsave > > - -rw-r--r-- 1 root wheel 109 Jun 16 2020 Fontmap.pkgsave > > - -rw-r--r-- 1 root wheel4183 May 2 22:23 cidfmap > > - -rw-r--r-- 1 root wheel4183 Jun 16 2020 cidfmap.pkgsave > > - -rw-r--r-- 1 root wheel 218021 May 2 22:23 gs_agl.ps > > > > /usr/local/share/ghostscript/fonts > > - -rw-r--r-- 1 root wheel 13643 Sep 19 2020 Fontmap > > - -rw-r--r-- 1 root wheel 13643 Jul 6 2019 Fontmap.pkgsave > > lrwxr-xr-x 1 root wheel 49 Sep 19 2020 GothicBBB-Medium@ -> > > /usr/local/share/fonts/std.ja_JP/GothicBBB-Medium > > lrwxr-xr-x 1 root wheel 53 Sep 19 2020 GothicBBB-Medium.gs7@ -> > > /usr/local/share/fonts/std.ja_JP/GothicBBB-Medium.gs7 > > lrwxr-xr-x
Making a port to use OpenSSL of ports collection on FreeBSD 11.x
Hello, Of the currently supported FreeBSD versions, base system of FreeBSD 11.x uses OpenSSL 1.0.2 and that of FreeBSD 12.x or later use OpenSSL 1.1.1. Then when new version of an application dropped suport of OpenSSL 1.0.2, is there any way to make the port of it to use OpenSSL of ports collection if the system is FreeBSD 11.x? Best Regards. --- Yasuhiro Kimura ___ 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: Xoscope nuisance console messages on Pi4 running -current
On Mon, May 3, 2021 at 12:38 AM bob prohaska wrote: > After a successful compile of audio/xoscope on a Pi4 running current a > stream of messages appeared on the console and in the security log > while xoscope was running: > > > +WARNING pid 26370 (xoscope): ioctl sign-extension ioctl c0045006 > +WARNING pid 26370 (xoscope): ioctl sign-extension ioctl c0045005 > +WARNING pid 26370 (xoscope): ioctl sign-extension ioctl c0045002 > +WARNING pid 26370 (xoscope): ioctl sign-extension ioctl c0045006 > +WARNING pid 26370 (xoscope): ioctl sign-extension ioctl c0045005 > +WARNING pid 26370 (xoscope): ioctl sign-extension ioctl c0045002 > > They seem to come at a fairly high rate and clutter the logfiles, but > apart from that nuisance nothing else seemed visibly amiss. > > Are they of any significance? > I fixed this a while ago, but some people copied our definitions which weren't sufficiently careful in using unsigned in places to avoid sign extension Warner ___ 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: looking for port origin for executable
On 5/4/21 3:53 PM, Freddie Cash wrote: On Tue, May 4, 2021 at 8:33 AM Robert Huff wrote: Would some kind soul please tell me which port installs the executable "g-ir-scanner"? I was purging unused ports and seem to have done this one by mistake. http://freshports.org allows you to do searches of pkg-plist files. It's a little finicky, though. Doing a search for "g-ir-scanner" returns 0 hits, regardless of what type of search is done. Doing a search for "bin/g-ir-scanner" returns gobject-introspection. So if you know the path for the file (relative to /usr/local), then the search works. pkg-provides also does the job :) % pkg provides g-ir-scanner Name : gobject-introspection-1.66.1,1 Desc : Generate interface introspection data for GObject libraries Repo : FreeBSD Filename: usr/local/man/man1/g-ir-scanner.1.gz usr/local/bin/g-ir-scanner ___ 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: looking for port origin for executable
On 5/4/21 5:29 PM, Tatsuki Makino wrote: Rodrigo Osorio wrote on 2021/05/05 00:59: pkg-provides also does the job :) % pkg provides g-ir-scanner Name : gobject-introspection-1.66.1,1 Desc : Generate interface introspection data for GObject libraries Repo : FreeBSD Filename: usr/local/man/man1/g-ir-scanner.1.gz usr/local/bin/g-ir-scanner Where can I find pkg provides? <--- ports-mgmt/pkg-provides :) Absolutely ! If it's somewhere in the PATH, pkg which -p g-ir-scanner is fine. Sure, pkg-provides helps you to identify the package for a tool you wanna use :) ___ 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" ___ 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: looking for port origin for executable
Rodrigo Osorio wrote on 2021/05/05 00:59: > pkg-provides also does the job :) > > % pkg provides g-ir-scanner > > Name : gobject-introspection-1.66.1,1 > Desc : Generate interface introspection data for GObject libraries > Repo : FreeBSD > Filename: usr/local/man/man1/g-ir-scanner.1.gz > usr/local/bin/g-ir-scanner Where can I find pkg provides? <--- ports-mgmt/pkg-provides :) If it's somewhere in the PATH, pkg which -p g-ir-scanner is fine. ___ 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: looking for port origin for executable
On Tue, 4 May 2021 11:33:12 -0400 Robert Huff wrote: > Would some kind soul please tell me which port installs the > executable "g-ir-scanner"? I was purging unused ports and seem to > have done this one by mistake. When I hit a wall like this, this is my usual way to get around without any additional tools: $ find /usr/ports -name pkg-plist | xargs grep -l bin/g-ir-scanner -- Piotr Smyrak ___ 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: Ports recompile for 13.0-RELEASE
On 04 May 2021, at 09:00, Ronald Klop wrote: > On 5/4/21 4:10 PM, @lbutlr wrote: >> With the move to FreeBSD 13.0 is there a simple (single step) way to >> reinstall all the current ports other than saving off a list of the ports >> and then stepping through that list to reinstall them? It was very >> inefficient when moving to 12.0 as many ports in the list, of course, were >> dependent on other ports, but then got recompiled, sometimes multiple times. >> I know I ended up in a make loop where came was compiled over and over again >> until I aborted, listed the current ports, differ on the previous ports, and >> picked a port I though would have a lot of reps to restart the compile. I >> then did this several more times to get back to where I had been on 11.x > > I used "portmaster -fa" in the past. Yeah, that's what I tried wen moving to 12.0 from 11.4 and it left a lot of cleaning up. >> (And yes, I've tried moving to poudrerie several times and we do not get on. >> At all.) > > Might help to do another attempt. Especially if you are using custom port > settings instead of pkgs. It just doesn't work the way my brain works, and I don't have a bunch of servers I need to keep updated, and the two servers I am running are different architecture. Something as simple as "hey, I want to install this one port" seemed overly complicated. I can see it's great when you have a cluster of servers and want to manage the updates on a dedicated server, but I don't need that. That said: # pkg-static upgrade -f # portmaster install postfix dovecot So far, so good (I thought I would have to also redo MariaDB but it all seems to be working now, mail did not work until I recompiled Dovecot and Postfix, but I was expecting that. So far the only thing that is new is an error about pam_opie, but that's for a new thread. -- Incredible! One of the worst performances of my career and they never doubted it for a second. ___ 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: looking for port origin for executable
On 5/4/21 3:53 PM, Freddie Cash wrote: On Tue, May 4, 2021 at 8:33 AM Robert Huff wrote: Would some kind soul please tell me which port installs the executable "g-ir-scanner"? I was purging unused ports and seem to have done this one by mistake. http://freshports.org allows you to do searches of pkg-plist files. It's a little finicky, though. Doing a search for "g-ir-scanner" returns 0 hits, regardless of what type of search is done. Doing a search for "bin/g-ir-scanner" returns gobject-introspection. So if you know the path for the file (relative to /usr/local), then the search works. pkg-provides also does the job :) % pkg provides g-ir-scanner Name : gobject-introspection-1.66.1,1 Desc : Generate interface introspection data for GObject libraries Repo : FreeBSD Filename: usr/local/man/man1/g-ir-scanner.1.gz usr/local/bin/g-ir-scanner ___ 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: Ports recompile for 13.0-RELEASE
On 2021-05-04 07:10, @lbutlr wrote: With the move to FreeBSD 13.0 is there a simple (single step) way to reinstall all the current ports other than saving off a list of the ports and then stepping through that list to reinstall them? It was very inefficient when moving to 12.0 as many ports in the list, of course, were dependent on other ports, but then got recompiled, sometimes multiple times. I know I ended up in a make loop where came was compiled over and over again until I aborted, listed the current ports, differ on the previous ports, and picked a port I though would have a lot of reps to restart the compile. I then did this several more times to get back to where I had been on 11.x And there's still no way to tell if a port was installed from pkg or from ports, correct? Since I use MariaDB instead of MySQLI have to be sure I don't try to use package for anything that will try to install MySQL instead. And finally, the release of 13.0 ends the 12.x versions, right? There will not be a 12.3. (And yes, I've tried moving to poudrerie several times and we do not get on. At all.) Not a big fan of poudrerie. If I must, I generally choose synth. But try to avoid both if at all possible. jail(8) is my go-to for most things they try to facilitate. While this isn't the simple "set it, and forget it" solution you seek. I find that picking a meta-port/package as part of something I'm installing, gets me pretty close to all I need. The key to my method is the "recursive" keyword. IOW # cd /usr/ports/x11/xorg/ # make config-recursive (repeat this until dialog stops appearing) When complete # make package-recursive (install) clean If I'm in my build jail and have a /usr/ports/packages/(All|latest) I (ultimately) end up with a nice package repo that facilitates an image install or upgrade path from a fresh install. HTH --Chris ___ 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: looking for port origin for executable
On Tue, May 4, 2021 at 8:33 AM Robert Huff wrote: > Would some kind soul please tell me which port installs the > executable "g-ir-scanner"? I was purging unused ports and seem to > have done this one by mistake. > http://freshports.org allows you to do searches of pkg-plist files. It's a little finicky, though. Doing a search for "g-ir-scanner" returns 0 hits, regardless of what type of search is done. Doing a search for "bin/g-ir-scanner" returns gobject-introspection. So if you know the path for the file (relative to /usr/local), then the search works. -- Freddie Cash fjwc...@gmail.com ___ 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: /usr/ports/print/ghostscript9-agpl-base gs_ll3.ps: Error: /undefinedresource (fwd)
On Tue, 04 May 2021 16:29:47 +0200 "Julian H. Stacey" wrote: > Hi ports@ people, > I wrote this to doc...@freebsd.org Sun, 02 May 2021 23:43:44 +0200 > but no reply by Tue May 4 16:26:48 CEST 2021. > Have others seen similar or got ideas to fix gs ghostscript ? > --- > > Hi doc...@freebsd.org > as MAINTAINER= in /usr/ports/print/ghostscript9-agpl-base > > I'm stuck, gs fails to start, suggestions please ? > > FreeBSD lapr.js.berklix.net 12.2-STABLE FreeBSD 12.2-STABLE #1038: Mon Feb 15 > 02:04:28 CET 2021 > j...@lapr.no.berklix.net:/data/release/s2/usr/src/sys/amd64/compile/LAPR.small > amd64 > > % printenv > PATH=/sbin:/bin:/usr/sbin:/usr/bin:/usr/games:/usr/local/bin > TERM=xterm > DESTDIR=/ > TERMPATH=/etc/termcap:/usr/share/misc/termcap > NOCLEANDEPENDS= > % printenv > PATH=/sbin:/bin:/usr/sbin:/usr/bin:/usr/games:/usr/local/bin > TERM=xterm > DESTDIR=/ > TERMPATH=/etc/termcap:/usr/share/misc/termcap > NOCLEANDEPENDS= > > % which gs > /usr/local/bin/gs > % ls -l /usr/local/bin/gs > - -rwxr-xr-x 1 root wheel 7648 Apr 29 11:02 /usr/local/bin/gs* > > gs > GPL Ghostscript 9.52 (2020-03-19) > Copyright (C) 2020 Artifex Software, Inc. All rights reserved. > This software is supplied under the GNU AGPLv3 and comes with NO WARRANTY: > see the file COPYING for details. > While reading gs_ll3.ps: > Error: /undefinedresource in findresource > Operand stack: > > (gs_icc.ps\000gs_mex_e.ps\000gs_mro_e.ps\000gs_pdf_e.ps\000gs_wan_e.ps\000pdf_ops.ps\000pdf_rbld.ps\000pdf_base.ps\000pdf_draw.ps\000gs_cff.ps\000gs_mgl_e.ps\000gs_ttf.ps\000pdf_font.ps\000pdf_main.ps\000pdf_sec.ps\000gs_epsf.ps\000gs_pdfwr.ps) >(gs_ll3.ps) 1 Pscript5Idiom.pkgsave IdiomSet 6 > Pscript5Idiom.pkgsave > Execution stack: >%interp_exit --nostringval-- findresource %loop_continue > findresource findresource findresource false 1 %stopped_push > --nostringval-- 1902 7 5 %oparray_pop findresource findresource > --dict:16/18(ro)(G)-- --dict:2/2(G)-- findresource 2 %dict_continue > findresource findresource 1900 5 5 %oparray_pop findresource > %errorexec_pop findresource findresource findresource findresource > Dictionary stack: >--dict:943/1123(G)-- --dict:0/20(G)-- --dict:77/200(L)-- > --dict:943/1123(G)-- --dict:38/43(G)-- --dict:16/18(ro)(G)-- > Current allocation mode is global > Current file position is 18941 > > Any ideas please ? > I rebuilt my machine with make worl & generic then custom kernel & > a load of downloaded pkg > pkg info -a | wc -l > 1348 > > ive since run > cd /usr/ports/print/ghostscript9-agpl-base > make clean > make reinstall > > gs -help > ends >/usr/local/share/ghostscript/9.52/Resource/Init : >/usr/local/share/ghostscript/9.52/lib : >/usr/local/share/ghostscript/9.52/Resource/Font : >/usr/local/share/ghostscript/fonts : /usr/local/share/fonts >Ghostscript is also using fontconfig to search for font files > > my /usr/local/share/ghostscript/9.52/Resource/ has no Init should it ? > drwxr-xr-x 2 root bin 4608 May 2 22:33 ./ > drwxr-xr-x 11 root bin 512 May 2 22:33 ../ > - -rw-r--r-- 1 root wheel3297 May 2 22:23 FAPIcidfmap > - -rw-r--r-- 1 root wheel3297 Jun 16 2020 FAPIcidfmap.pkgsave > - -rw-r--r-- 1 root wheel1158 May 2 22:23 FAPIconfig > - -rw-r--r-- 1 root wheel1158 Jun 16 2020 FAPIconfig.pkgsave > - -rw-r--r-- 1 root wheel1468 May 2 22:23 FAPIfontmap > - -rw-r--r-- 1 root wheel1468 Jun 16 2020 FAPIfontmap.pkgsave > - -rw-r--r-- 1 root wheel2857 May 2 22:23 FCOfontmap-PCLPS2 > - -rw-r--r-- 1 root wheel2857 Jun 16 2020 FCOfontmap-PCLPS2.pkgsave > - -rw-r--r-- 1 root wheel 109 May 2 22:23 Fontmap > - -rw-r--r-- 1 root wheel 12929 May 2 22:23 Fontmap.GS > - -rw-r--r-- 1 root wheel 12929 Jun 16 2020 Fontmap.GS.pkgsave > - -rw-r--r-- 1 root wheel 109 Jun 16 2020 Fontmap.pkgsave > - -rw-r--r-- 1 root wheel4183 May 2 22:23 cidfmap > - -rw-r--r-- 1 root wheel4183 Jun 16 2020 cidfmap.pkgsave > - -rw-r--r-- 1 root wheel 218021 May 2 22:23 gs_agl.ps > > /usr/local/share/ghostscript/fonts > - -rw-r--r-- 1 root wheel 13643 Sep 19 2020 Fontmap > - -rw-r--r-- 1 root wheel 13643 Jul 6 2019 Fontmap.pkgsave > lrwxr-xr-x 1 root wheel 49 Sep 19 2020 GothicBBB-Medium@ -> > /usr/local/share/fonts/std.ja_JP/GothicBBB-Medium > lrwxr-xr-x 1 root wheel 53 Sep 19 2020 GothicBBB-Medium.gs7@ -> > /usr/local/share/fonts/std.ja_JP/GothicBBB-Medium.gs7 > lrwxr-xr-x 1 root wheel 44 Sep 19 2020 MSung-Light@ -> > /usr/local/share/fonts/std.zh_CN/MSung-Light > lrwxr-xr-x 1 root wheel 45 Sep 19 2020 Ryumin-Light@ -> > /usr/local/share/fonts/std.ja_JP/Ryumin-Light > lrwxr-xr-x 1 root wheel 49 Sep 19 2020 Ryumin-Light.gs7@ -> > /usr/local/share/fonts/std.ja_JP/Ryumin-Light.gs7 > lrwxr-xr-x 1 root wheel
Re: looking for port origin for executable
On Tue, May 04, 2021 at 11:33:12AM -0400, Robert Huff wrote: > > Hello: > Would some kind soul please tell me which port installs the > executable "g-ir-scanner"? I was purging unused ports and seem to > have done this one by mistake. devel/gobject-introspection -- Herbert ___ 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"
looking for port origin for executable
Hello: Would some kind soul please tell me which port installs the executable "g-ir-scanner"? I was purging unused ports and seem to have done this one by mistake. Apologetically, Robert Huff ___ 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: Ports recompile for 13.0-RELEASE
From: Yasuhiro Kimura Subject: Re: Ports recompile for 13.0-RELEASE Date: Wed, 05 May 2021 00:15:39 +0900 (JST) > It depends on how there are installed. If they are installed by using > official pakcages or building personal packages with poudriere, then > `pkg upgrade` is worth trying. Oops, it should be `pkg upgrade -f`. --- Yasuhiro Kimura ___ 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: Ports recompile for 13.0-RELEASE
From: "@lbutlr" Subject: Ports recompile for 13.0-RELEASE Date: Tue, 4 May 2021 08:10:38 -0600 > With the move to FreeBSD 13.0 is there a simple (single step) way to > reinstall all the current ports other than saving off a list of the > ports and then stepping through that list to reinstall them? It depends on how there are installed. If they are installed by using official pakcages or building personal packages with poudriere, then `pkg upgrade` is worth trying. But you should save list of installed packages just in case. otherwise (i.e. you used portmaster or simple `cd /usr/port/category/portname; make insall`) `portmaster -af` may work fine if you are lucky. But in this case I think saving list of installed packages, removing all of them and then reinstalling them is probably the easiest and shortest way as a result. > And finally, the release of 13.0 ends the 12.x versions, right? > There will not be a 12.3. According to 'Supported FreeBSD releases' (https://www.freebsd.org/security/#sup), expected EoL of 12.2-RELEASE is '12.3-RELEASE + 3 months', and that of stable/12 is June 30, 2024. So at least 12.3-RELEASE will be released. And probably 12.4-RELEASE will be too. --- Yasuhiro Kimura ___ 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: Ports recompile for 13.0-RELEASE
On Tue, May 04, 2021 at 08:10:38AM -0600, @lbutlr wrote: > With the move to FreeBSD 13.0 is there a simple (single step) way to > reinstall all the current ports other than saving off a list of the ports and > then stepping through that list to reinstall them? It was very inefficient > when moving to 12.0 as many ports in the list, of course, were dependent on > other ports, but then got recompiled, sometimes multiple times. I know I > ended up in a make loop where came was compiled over and over again until I > aborted, listed the current ports, differ on the previous ports, and picked a > port I though would have a lot of reps to restart the compile. I then did > this several more times to get back to where I had been on 11.x > > And there's still no way to tell if a port was installed from pkg or from > ports, correct? Since I use MariaDB instead of MySQLI have to be sure I don't > try to use package for anything that will try to install MySQL instead. > > And finally, the release of 13.0 ends the 12.x versions, right? There will > not be a 12.3. > > (And yes, I've tried moving to poudrerie several times and we do not get on. > At all.) If you can get everything into a pkg repo, "pkg upgrade -f" should reinstall everything regardless of if pkg thinks it needs to. I suspect that your problem is minimum proper rebuilding rather than reinstallation. I just keep a list of packages I want (vs all build dependencies), which made my what-needs-rebuilding list much smaller (the dependency list is huge, but I didn't need to track that). I have a list of 58 packages I want installed, but have 494 packages installed for dependencies and I think the build total (some build dependencies don't get installed) is 600+. Your story is reminding me about my portmaster problems back in the day (that drove me to try poudriere, not get it, try synth, then run on synth until I ran into other issues (arm64) that remotivated me to learn poudriere). I know there is someone that has tried to fix portmaster in the meantime, but I think the basic issue is that there are, and will continue to be, issues with incompatible build dependencies that are "solved" by clean-room build systems which are probably the cause of some of those make loops. The last time I had this conversation, someone who had been beating on portmaster spoke up about the work they'd been doing to try and get the clean-room work added to it, but I don't know about the status of that. I think you're going to be aggravated until you find a ports management fix that works for you. ___ 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: Ports recompile for 13.0-RELEASE
On 5/4/21 4:10 PM, @lbutlr wrote: With the move to FreeBSD 13.0 is there a simple (single step) way to reinstall all the current ports other than saving off a list of the ports and then stepping through that list to reinstall them? It was very inefficient when moving to 12.0 as many ports in the list, of course, were dependent on other ports, but then got recompiled, sometimes multiple times. I know I ended up in a make loop where came was compiled over and over again until I aborted, listed the current ports, differ on the previous ports, and picked a port I though would have a lot of reps to restart the compile. I then did this several more times to get back to where I had been on 11.x I used "portmaster -fa" in the past. (see ports-mgmt/portmaster) And there's still no way to tell if a port was installed from pkg or from ports, correct? Since I use MariaDB instead of MySQLI have to be sure I don't try to use package for anything that will try to install MySQL instead. I don't know. And finally, the release of 13.0 ends the 12.x versions, right? There will not be a 12.3. https://www.freebsd.org/security/#sup 12.x has support until 2024. So a 12.3 is in the pipeline. 12.4 probably also. 11.4 was the latest 11.x release AFAIK. (And yes, I've tried moving to poudrerie several times and we do not get on. At all.) Might help to do another attempt. Especially if you are using custom port settings instead of pkgs. Regards, Ronald. ___ 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: Ports recompile for 13.0-RELEASE
On Tue, 4 May 2021 08:10:38 -0600
"@lbutlr" wrote:
> With the move to FreeBSD 13.0 is there a simple (single step) way to
> reinstall all the current ports other than saving off a list of the
> ports and then stepping through that list to reinstall them?
> It was very inefficient when moving to 12.0 as many ports in the
> list, of course, were dependent on other ports, but then got
> recompiled, sometimes multiple times. I know I ended up in a make
> loop where came was compiled over and over again until I aborted,
> listed the current ports, differ on the previous ports, and picked a
> port I though would have a lot of reps to restart the compile. I then
> did this several more times to get back to where I had been on 11.x
Using a local poudriere repo fixes all of the above ;)
>
> And there's still no way to tell if a port was installed from pkg or
> from ports, correct? Since I use MariaDB instead of MySQLI have to be
> sure I don't try to use package for anything that will try to install
> MySQL instead.
The repository the package came from is stored in the annotation tag
named "repository".
You can see this, e.g., by using
pkg query "%n %At %Av"
or
pkg info -R
By default this is "FreeBSD" for the official repos. If you install
locally ("make install"), it's not set.
>
> And finally, the release of 13.0 ends the 12.x versions, right? There
> will not be a 12.3.
See https://www.freebsd.org/security/#sup, there will be a 12.3.
>
> (And yes, I've tried moving to poudrerie several times and we do not
> get on. At all.)
Well, that's the recommended way of doing what you're trying to
accomplish, otherwise you'll be in dependency hell like we've all
been updating our machines in the 2000s.
Alternatively, you could create a jail or VM manually, install all
packages you need in there from ports using make install. You
can retrieve the list of what you need on your target host using
pkg query -e "%a = 0" %o
Then run "pkg create -a" on that machine to get a set of all binary
packages. Then copy those over to your target machine and install them
using pkg add. Will be messy, but kind of work. I really would prefer
poudriere over that though.
Best
Michael
--
Michael Gmelin
___
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"
/usr/ports/print/ghostscript9-agpl-base gs_ll3.ps: Error: /undefinedresource (fwd)
Hi ports@ people, I wrote this to doc...@freebsd.org Sun, 02 May 2021 23:43:44 +0200 but no reply by Tue May 4 16:26:48 CEST 2021. Have others seen similar or got ideas to fix gs ghostscript ? --- Hi doc...@freebsd.org as MAINTAINER= in /usr/ports/print/ghostscript9-agpl-base I'm stuck, gs fails to start, suggestions please ? FreeBSD lapr.js.berklix.net 12.2-STABLE FreeBSD 12.2-STABLE #1038: Mon Feb 15 02:04:28 CET 2021 j...@lapr.no.berklix.net:/data/release/s2/usr/src/sys/amd64/compile/LAPR.small amd64 % printenv PATH=/sbin:/bin:/usr/sbin:/usr/bin:/usr/games:/usr/local/bin TERM=xterm DESTDIR=/ TERMPATH=/etc/termcap:/usr/share/misc/termcap NOCLEANDEPENDS= % printenv PATH=/sbin:/bin:/usr/sbin:/usr/bin:/usr/games:/usr/local/bin TERM=xterm DESTDIR=/ TERMPATH=/etc/termcap:/usr/share/misc/termcap NOCLEANDEPENDS= % which gs /usr/local/bin/gs % ls -l /usr/local/bin/gs - -rwxr-xr-x 1 root wheel 7648 Apr 29 11:02 /usr/local/bin/gs* gs GPL Ghostscript 9.52 (2020-03-19) Copyright (C) 2020 Artifex Software, Inc. All rights reserved. This software is supplied under the GNU AGPLv3 and comes with NO WARRANTY: see the file COPYING for details. While reading gs_ll3.ps: Error: /undefinedresource in findresource Operand stack: (gs_icc.ps\000gs_mex_e.ps\000gs_mro_e.ps\000gs_pdf_e.ps\000gs_wan_e.ps\000pdf_ops.ps\000pdf_rbld.ps\000pdf_base.ps\000pdf_draw.ps\000gs_cff.ps\000gs_mgl_e.ps\000gs_ttf.ps\000pdf_font.ps\000pdf_main.ps\000pdf_sec.ps\000gs_epsf.ps\000gs_pdfwr.ps) (gs_ll3.ps) 1 Pscript5Idiom.pkgsave IdiomSet 6 Pscript5Idiom.pkgsave Execution stack: %interp_exit --nostringval-- findresource %loop_continue findresource findresource findresource false 1 %stopped_push --nostringval-- 1902 7 5 %oparray_pop findresource findresource --dict:16/18(ro)(G)-- --dict:2/2(G)-- findresource 2 %dict_continue findresource findresource 1900 5 5 %oparray_pop findresource %errorexec_pop findresource findresource findresource findresource Dictionary stack: --dict:943/1123(G)-- --dict:0/20(G)-- --dict:77/200(L)-- --dict:943/1123(G)-- --dict:38/43(G)-- --dict:16/18(ro)(G)-- Current allocation mode is global Current file position is 18941 Any ideas please ? I rebuilt my machine with make worl & generic then custom kernel & a load of downloaded pkg pkg info -a | wc -l 1348 ive since run cd /usr/ports/print/ghostscript9-agpl-base make clean make reinstall gs -help ends /usr/local/share/ghostscript/9.52/Resource/Init : /usr/local/share/ghostscript/9.52/lib : /usr/local/share/ghostscript/9.52/Resource/Font : /usr/local/share/ghostscript/fonts : /usr/local/share/fonts Ghostscript is also using fontconfig to search for font files my /usr/local/share/ghostscript/9.52/Resource/ has no Init should it ? drwxr-xr-x 2 root bin 4608 May 2 22:33 ./ drwxr-xr-x 11 root bin 512 May 2 22:33 ../ - -rw-r--r-- 1 root wheel3297 May 2 22:23 FAPIcidfmap - -rw-r--r-- 1 root wheel3297 Jun 16 2020 FAPIcidfmap.pkgsave - -rw-r--r-- 1 root wheel1158 May 2 22:23 FAPIconfig - -rw-r--r-- 1 root wheel1158 Jun 16 2020 FAPIconfig.pkgsave - -rw-r--r-- 1 root wheel1468 May 2 22:23 FAPIfontmap - -rw-r--r-- 1 root wheel1468 Jun 16 2020 FAPIfontmap.pkgsave - -rw-r--r-- 1 root wheel2857 May 2 22:23 FCOfontmap-PCLPS2 - -rw-r--r-- 1 root wheel2857 Jun 16 2020 FCOfontmap-PCLPS2.pkgsave - -rw-r--r-- 1 root wheel 109 May 2 22:23 Fontmap - -rw-r--r-- 1 root wheel 12929 May 2 22:23 Fontmap.GS - -rw-r--r-- 1 root wheel 12929 Jun 16 2020 Fontmap.GS.pkgsave - -rw-r--r-- 1 root wheel 109 Jun 16 2020 Fontmap.pkgsave - -rw-r--r-- 1 root wheel4183 May 2 22:23 cidfmap - -rw-r--r-- 1 root wheel4183 Jun 16 2020 cidfmap.pkgsave - -rw-r--r-- 1 root wheel 218021 May 2 22:23 gs_agl.ps /usr/local/share/ghostscript/fonts - -rw-r--r-- 1 root wheel 13643 Sep 19 2020 Fontmap - -rw-r--r-- 1 root wheel 13643 Jul 6 2019 Fontmap.pkgsave lrwxr-xr-x 1 root wheel 49 Sep 19 2020 GothicBBB-Medium@ -> /usr/local/share/fonts/std.ja_JP/GothicBBB-Medium lrwxr-xr-x 1 root wheel 53 Sep 19 2020 GothicBBB-Medium.gs7@ -> /usr/local/share/fonts/std.ja_JP/GothicBBB-Medium.gs7 lrwxr-xr-x 1 root wheel 44 Sep 19 2020 MSung-Light@ -> /usr/local/share/fonts/std.zh_CN/MSung-Light lrwxr-xr-x 1 root wheel 45 Sep 19 2020 Ryumin-Light@ -> /usr/local/share/fonts/std.ja_JP/Ryumin-Light lrwxr-xr-x 1 root wheel 49 Sep 19 2020 Ryumin-Light.gs7@ -> /usr/local/share/fonts/std.ja_JP/Ryumin-Light.gs7 lrwxr-xr-x 1 root wheel 48 Sep 19 2020 STHeiti-Regular@ -> /usr/local/share/fonts/std.zh_CN/STHeiti-Regular lrwxr-xr-x 1 root wheel 45 Sep 19 2020 STSong-Light@ -> /usr/local/share/fonts/std.zh_CN/STSong-Light - -rw-r--r-- 1 root wheel 42833 Sep 19 2020 a010013l.afm - -rw-r--r-- 1 root
Ports recompile for 13.0-RELEASE
With the move to FreeBSD 13.0 is there a simple (single step) way to reinstall all the current ports other than saving off a list of the ports and then stepping through that list to reinstall them? It was very inefficient when moving to 12.0 as many ports in the list, of course, were dependent on other ports, but then got recompiled, sometimes multiple times. I know I ended up in a make loop where came was compiled over and over again until I aborted, listed the current ports, differ on the previous ports, and picked a port I though would have a lot of reps to restart the compile. I then did this several more times to get back to where I had been on 11.x And there's still no way to tell if a port was installed from pkg or from ports, correct? Since I use MariaDB instead of MySQLI have to be sure I don't try to use package for anything that will try to install MySQL instead. And finally, the release of 13.0 ends the 12.x versions, right? There will not be a 12.3. (And yes, I've tried moving to poudrerie several times and we do not get on. At all.) -- I don't need no stinking taglines. ___ 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: gdal
Am 02.05.21 um 19:55 schrieb LuMiWa via freebsd-ports:
> Hi!
>
> I have a problem to build graphics/gdal on FreeBSD-13.0-RELEASE:
> m::seekp' declared here: type mismatch at 1st parameter ('uint64_t'
> (aka 'unsigned long') vs 'GInt64' (aka 'long long')) virtual void
> seekp (uint64_t pos) = 0; ^
> exrdataset.cpp:495:1: error: unknown type name 'Int64'; did you mean
> 'GInt64'? Int64 GDALEXRIOStream::tellg ()
> ^
> GInt64
> /usr/ports/graphics/gdal/work/gdal-3.2.2/port/cpl_port.h:267:26: note:
> 'GInt64' declared here typedef GIntBig GInt64;
> ^
> exrdataset.cpp:497:24: error: unknown type name 'Int64'; did you mean
> 'GInt64'? return static_cast(VSIFTellL(m_fp));
>^
>GInt64
> /usr/ports/graphics/gdal/work/gdal-3.2.2/port/cpl_port.h:267:26: note:
> 'GInt64' declared here typedef GIntBig GInt64;
> ^
> exrdataset.cpp:500:30: error: unknown type name 'Int64'; did you mean
> 'GInt64'? void GDALEXRIOStream::seekg (Int64 pos)
> ^
> GInt64
> /usr/ports/graphics/gdal/work/gdal-3.2.2/port/cpl_port.h:267:26: note:
> 'GInt64' declared here typedef GIntBig GInt64;
> ^
> exrdataset.cpp:566:36: error: allocating an object of abstract class
> type 'GDALEXRIOStream' poDS->m_pIStream.reset(new GDALEXRIOStream(fp,
> osFilename)); ^
> exrdataset.cpp:992:25: error: variable type 'GDALEXRIOStream' is an
> abstract class GDALEXRIOStream ostream(fp, pszFilename);
> ^
> exrdataset.cpp:1984:32: error: allocating an object of abstract class
> type 'GDALEXRIOStream' poDS->m_pOStream.reset(new GDALEXRIOStream(fp,
> pszFilename)); ^
> 3 warnings and 14 errors generated.
> gmake[4]: *** [../../GDALmake.opt:646: ../o/exrdataset.o] Error 1
> gmake[4]: Leaving directory
> '/usr/ports/graphics/gdal/work/gdal-3.2.2/frmts/exr' gmake[3]: ***
> [GNUmakefile:15: exr-install-obj] Error 2 gmake[3]: Leaving directory
> '/usr/ports/graphics/gdal/work/gdal-3.2.2/frmts' gmake[2]: ***
> [GNUmakefile:114: frmts-target] Error 2 gmake[2]: Leaving directory
> '/usr/ports/graphics/gdal/work/gdal-3.2.2' *** Error code 1
>
> Stop.
> make[1]: stopped in /usr/ports/graphics/gdal
> *** Error code 1
>
> Thank you.
>
>
I just opened a PR with a patch, which should solve the issue ;)
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=255592
HTH,
Rainer
___
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: [SOLVED?] Recovery of deleted ports fails due to pre-commit checks
On Tue, May 04, 2021 at 12:12:50PM +0200, Stefan Esser wrote: > Am 04.05.21 um 11:46 schrieb Mathieu Arnold: > > On Mon, May 03, 2021 at 09:54:36PM +0200, Stefan Esser wrote: > >> Am 03.05.21 um 09:01 schrieb Mathieu Arnold: > >>> On Sat, May 01, 2021 at 09:01:02PM +0200, Stefan Esser wrote: > The recovery of deleted ports in their previous form is rejected > by the pre-commit checks on the repository server: > > remote: > remote: > remote: Do not commit ports without TIMESTAMP in their distinfo files. > remote: Rerun make makesum to add it. > remote: > remote: > > I have tried to revert the deletion with unchanged files and then > updated the ports' Makefiles and distinfo files in a later commit. > > Pushing those commits all together fails with the message above, > and in order to not confuse GIT, deleted files should be committed > first, before applying any changes. > >>> > >>> This is not needed at all, Git cannot get confused by something it has > >>> no knowledge of. Once a file is deleted, or moved, the history tracking > >>> stops. > >> > >> I wanted to re-connect the resurrected files to the history of the port. > >> And that works best, if unmodified files are committed first, changes > >> applied and committed thereafter. > >> > >> Did you try "git log multimedia/transcode"? > >> > >> The history is there, back to 2002. > > > > Yeah, but this has nothing to do with you commiting unmodified files. > > Git does not track file renames or moves (or resurrection), it blindly > > looks at what you told it and goes as far as it can find things. > > Yes, sure, but the general advice when moving around files in GIT > repositories is: First move and commit unchanged, then modify in > place and commit again. And I was under the impression that the > same advice applies to files that have been deleted and are brought > back - GIT can identify and reconnect them in a way that preserves > history only by guessing, and I wanted to make it as easy as possible > for GIT, since I have watched GIT to get trivial operations of that > kind wrong in grotesque ways ... > > https://github.blog/2020-12-17-commits-are-snapshots-not-diffs/#since-commits-arent-diffs-how-does-git-track-renames Note that there are two caveats. Git will only look for files to compare to in the parent of the commit where the files are added, so if it is a resurrection, Git will never find out where the file came from. Git will only look around for a few files, like a few thousands, see diff.renameLimit in git-config(1), as we have something like 140k files in the tree, there is no chance for Git to actually find the original file you moved the new file from. So, let me say it once again, if you want to record where a file was moved/resurrected from, describe it in the commit message. Don't try to be clever with special commits, Git won't care and won't find where the file came from. -- Mathieu Arnold signature.asc Description: PGP signature
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 +-+ multimedia/shotcut | 21.03.21| v21.05.01 +-+ 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: [SOLVED?] Recovery of deleted ports fails due to pre-commit checks
Am 04.05.21 um 11:46 schrieb Mathieu Arnold: > On Mon, May 03, 2021 at 09:54:36PM +0200, Stefan Esser wrote: >> Am 03.05.21 um 09:01 schrieb Mathieu Arnold: >>> On Sat, May 01, 2021 at 09:01:02PM +0200, Stefan Esser wrote: The recovery of deleted ports in their previous form is rejected by the pre-commit checks on the repository server: remote: remote: remote: Do not commit ports without TIMESTAMP in their distinfo files. remote: Rerun make makesum to add it. remote: remote: I have tried to revert the deletion with unchanged files and then updated the ports' Makefiles and distinfo files in a later commit. Pushing those commits all together fails with the message above, and in order to not confuse GIT, deleted files should be committed first, before applying any changes. >>> >>> This is not needed at all, Git cannot get confused by something it has >>> no knowledge of. Once a file is deleted, or moved, the history tracking >>> stops. >> >> I wanted to re-connect the resurrected files to the history of the port. >> And that works best, if unmodified files are committed first, changes >> applied and committed thereafter. >> >> Did you try "git log multimedia/transcode"? >> >> The history is there, back to 2002. > > Yeah, but this has nothing to do with you commiting unmodified files. > Git does not track file renames or moves (or resurrection), it blindly > looks at what you told it and goes as far as it can find things. Yes, sure, but the general advice when moving around files in GIT repositories is: First move and commit unchanged, then modify in place and commit again. And I was under the impression that the same advice applies to files that have been deleted and are brought back - GIT can identify and reconnect them in a way that preserves history only by guessing, and I wanted to make it as easy as possible for GIT, since I have watched GIT to get trivial operations of that kind wrong in grotesque ways ... https://github.blog/2020-12-17-commits-are-snapshots-not-diffs/#since-commits-arent-diffs-how-does-git-track-renames OpenPGP_signature Description: OpenPGP digital signature
Re: [SOLVED?] Recovery of deleted ports fails due to pre-commit checks
On Mon, May 03, 2021 at 09:54:36PM +0200, Stefan Esser wrote: > Am 03.05.21 um 09:01 schrieb Mathieu Arnold: > > On Sat, May 01, 2021 at 09:01:02PM +0200, Stefan Esser wrote: > >> The recovery of deleted ports in their previous form is rejected > >> by the pre-commit checks on the repository server: > >> > >> remote: > >> remote: > >> remote: Do not commit ports without TIMESTAMP in their distinfo files. > >> remote: Rerun make makesum to add it. > >> remote: > >> remote: > >> > >> I have tried to revert the deletion with unchanged files and then > >> updated the ports' Makefiles and distinfo files in a later commit. > >> > >> Pushing those commits all together fails with the message above, > >> and in order to not confuse GIT, deleted files should be committed > >> first, before applying any changes. > > > > This is not needed at all, Git cannot get confused by something it has > > no knowledge of. Once a file is deleted, or moved, the history tracking > > stops. > > I wanted to re-connect the resurrected files to the history of the port. > And that works best, if unmodified files are committed first, changes > applied and committed thereafter. > > Did you try "git log multimedia/transcode"? > > The history is there, back to 2002. Yeah, but this has nothing to do with you commiting unmodified files. Git does not track file renames or moves (or resurrection), it blindly looks at what you told it and goes as far as it can find things. -- Mathieu Arnold signature.asc Description: PGP signature
