impossible to compile firefox when WRKDIRPREFIX is used
Hi, I use WRKDIRPREFIX as a standard outside of jails. I could not compile there firefox since some time. I started to investigate today with a ports tree from last Sunday/Monday and still have had this problem. After removing WRKDIRPREFIX, it all worked as expected. Erich ___ 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: pkg-1.7.0 is an order of magnitude slower than pkg-1.6.4
Baptiste Daroussinwrote: > > On Sat, Apr 02, 2016 at 02:59:06PM +0200, Michael Grimm wrote: >> Baptiste Daroussin wrote: >>> On Sat, Apr 02, 2016 at 02:42:06PM +0200, Michael Grimm wrote: 26 seconds for 74 ports within a jail and pkg-1.6.4: >> […] 309 seconds for the very same 74 ports within the very same jail and pkg-1.7.0: >> […] Is this an expected slow-down? /usr/ports/UPGRADE and https://svnweb.freebsd.org/ports/head/ports-mgmt/pkg/?view=log are not indicating that behavior. But I might have missed something. Any feedback is highly appriciated, thanks, and regards, >>> >>> pkg 1.7 is IO intensive that may explain. >> >> Ok, understood. >> >> JFTR: perl (24s), python27 (44s), and ruby (125s) take the longest time to >> reinstall. >> >>> I plan to readd some improvements on this side before 1.8 >> >> Good to know, thanks for your feedback. > > Just to follow up on the performance issue, there is a regression that > happened > on FreeBSD 10.3-RELEASE (also HEAD) that causes pkg extraction process to be > 10 > times slower as it should. r297626 fixes it in head. We are working on > bringing > that into the 10 branch: > https://svnweb.freebsd.org/base?view=revision=297626 Thanks. I added the relevant patch [1] to 10.3-STABLE (r297721) and I can confirm that that fixed the performance issue. Now, with pkg-1.7.2 for the very same 74 ports and jail reinstallation is back to 26 seconds: Apr 8 20:04:42 pkg: indexinfo reinstalled: 0.2.4 -> 0.2.4 ... Apr 8 20:05:08 pkg: pkg reinstalled: 1.7.2 -> 1.7.2 Up to now, 10.3-STABLE runs rock solid. I will report if that might change. Thanks for your engagement and with kind regards, Michael [1] https://svnweb.freebsd.org/base/head/lib/libc/db/hash/hash.c?view=patch=297626=297625=297626 ___ 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: Post-install messages
In message <5707fd13.2060...@gmx.de>, olli hauerwrote: >Try the command `pkg info -aD | less' or for a single package `pkg info -D $pa >ckagename' Thank you. That seems to do the trick nicely. ___ 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: Post-install messages
On 2016-04-08 20:37, Ronald F. Guilmette wrote: > > I am bringing up a new 10.3-RELEASE system from scratch. > > While doing so, I unfortunately rushed ahead and installed > several packages I knew I needed using the "pkg install" > command, but I neglected to look carefully at all of the > helpful post-install messages for each package. Most of > these post-install messages appear to be merely informative, > however some of these appear to be REALLY critical, e.g. the > ones you get after "pkg install bash". > > Is there a way for me to go back now and see again all of the > post-install messages for all of the packages that I have > already installed, so that I can make sure that I've done > everything that should be done to properly install all these? > > I am hoping that there is some way for me to see all these > messages again *without* having to force re-install all of the > relevant packages. Try the command `pkg info -aD | less' or for a single package `pkg info -D $packagename' -- olli ___ 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: Post-install messages
On Fri, Apr 8, 2016 at 11:37 AM, Ronald F. Guilmettewrote: > > I am bringing up a new 10.3-RELEASE system from scratch. > > While doing so, I unfortunately rushed ahead and installed > several packages I knew I needed using the "pkg install" > command, but I neglected to look carefully at all of the > helpful post-install messages for each package. Most of > these post-install messages appear to be merely informative, > however some of these appear to be REALLY critical, e.g. the > ones you get after "pkg install bash". > > Is there a way for me to go back now and see again all of the > post-install messages for all of the packages that I have > already installed, so that I can make sure that I've done > everything that should be done to properly install all these? > > I am hoping that there is some way for me to see all these > messages again *without* having to force re-install all of the > relevant packages. > man pkg-query Read up on the %M (message contained in the matched package) option. That probably does what you want. -- 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"
Post-install messages
I am bringing up a new 10.3-RELEASE system from scratch. While doing so, I unfortunately rushed ahead and installed several packages I knew I needed using the "pkg install" command, but I neglected to look carefully at all of the helpful post-install messages for each package. Most of these post-install messages appear to be merely informative, however some of these appear to be REALLY critical, e.g. the ones you get after "pkg install bash". Is there a way for me to go back now and see again all of the post-install messages for all of the packages that I have already installed, so that I can make sure that I've done everything that should be done to properly install all these? I am hoping that there is some way for me to see all these messages again *without* having to force re-install all of the relevant packages. ___ 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: Deriving base port/package names
In message <5707553c.40...@quip.cz>, Miroslav Lachman <000.f...@quip.cz> wrote: >If you have the index stripped to > >yorick-2.2.04_1 > >This will do the trick >sed 's/-[0-9a-z.,_+]*$//g' master-index.txt Thank you. Your response made me realize that there's an even simpler solution... sed 's/-[^\-]*$//' That seems to do the trick! ___ 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: Deriving base port/package names
Matthew Seaman wrote: Put another way, if you're working with full pkgnames '%n-%v' it's always the last '-' character that separates the name from the version. $ pkgname='postgresql92-client-9.2.16' $ echo ${pkgname%-*} postgresql92-client $ echo ${pkgname##*-} 9.2.16 Those of us who prefer to avoid shell perlisms/bashisms (blessed by POSIX' IBM/RH/Oracle-dominated board or not) appreciate your inclusion of the equivalent sed regex. $ echo $pkgname | sed -e 's,-[^-]*$,,' postgresql92-client $ echo $pkgname | sed -e 's,^.*-,,' 9.2.16 I think a proposal to rename large chunks of the ports tree to eliminate hyphens and digits would certainly not receive a warm welcome. `pkg rquery -a %n | grep -- '-[0-9]' | wc -l` shows only 40 ports (of 25096). Doesn't seem like a whole lot or a difficult refactor but perhaps we're missing the use case of this particular group. Anyone know why these 40 ports are so named? Roger ___ 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: Deriving base port/package names
On 2016/04/08 15:47, Roger Marquis wrote: > As in: `pkg rquery -a %n | grep -- '-[0-9]' | fmt` > > efax-0.9a font-adobe-100dpi font-adobe-75dpi font-adobe-utopia-100dpi > font-adobe-utopia-75dpi font-bh-100dpi font-bh-75dpi > font-bh-lucidatypewriter-100dpi font-bh-lucidatypewriter-75dpi > font-bitstream-100dpi font-bitstream-75dpi gl-117 gnome-2048 > ja-edict-utf-8 ja-kon2-14dot ja-kon2-16dot ja-rubygem-mail-iso-2022-jp > krb5-112 krb5-113 krb5-114 liblqr-1 libutf-8 > linux-enemyterritory-jaymod-217 linux-enemyterritory-omni-bot-0660 > nvidia-driver-304 nvidia-driver-340 onscripter-1byte p5-Acme-6502 > p5-Business-OnlinePayment-2CheckOut p5-Chemistry-3DBuilder p5-WWW-2ch > p5-WWW-Shorten-0rz ppmd-7z qt5-3d quake2-3zb2 stf-6rd-kmod vte3-290 > xhtml-11 xorg-fonts-100dpi xorg-fonts-75dpi > > Some of us see this as a weakness in the standard. That plus the lack > of documentation where you'd expect to find it violates the principles > of least surprise and KIS. The 'version' part of a full package name can't contain the '-' character. Put another way, if you're working with full pkgnames '%n-%v' it's always the last '-' character that separates the name from the version. In shell, you can do something like this: $ pkgname='postgresql92-client-9.2.16' $ echo ${pkgname%-*} postgresql92-client $ echo ${pkgname##*-} 9.2.16 or if you prefer sed(1): $ echo $pkgname | sed -e 's,-[^-]*$,,' postgresql92-client $ echo $pkgname | sed -e 's,^.*-,,' 9.2.16 It's generally assumed that you'ld know if you've got a version part appended to the name or not, and would be able to code accordingly. I think a proposal to rename large chunks of the ports tree to eliminate hyphens and digits would certainly not receive a warm welcome. Cheers, Matthew signature.asc Description: OpenPGP digital signature
Re: Deriving base port/package names
A port name can contain digits and hyphens, so this could remove part of the name. As in: `pkg rquery -a %n | grep -- '-[0-9]' | fmt` efax-0.9a font-adobe-100dpi font-adobe-75dpi font-adobe-utopia-100dpi font-adobe-utopia-75dpi font-bh-100dpi font-bh-75dpi font-bh-lucidatypewriter-100dpi font-bh-lucidatypewriter-75dpi font-bitstream-100dpi font-bitstream-75dpi gl-117 gnome-2048 ja-edict-utf-8 ja-kon2-14dot ja-kon2-16dot ja-rubygem-mail-iso-2022-jp krb5-112 krb5-113 krb5-114 liblqr-1 libutf-8 linux-enemyterritory-jaymod-217 linux-enemyterritory-omni-bot-0660 nvidia-driver-304 nvidia-driver-340 onscripter-1byte p5-Acme-6502 p5-Business-OnlinePayment-2CheckOut p5-Chemistry-3DBuilder p5-WWW-2ch p5-WWW-Shorten-0rz ppmd-7z qt5-3d quake2-3zb2 stf-6rd-kmod vte3-290 xhtml-11 xorg-fonts-100dpi xorg-fonts-75dpi Some of us see this as a weakness in the standard. That plus the lack of documentation where you'd expect to find it violates the principles of least surprise and KIS. Roger ___ 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: Deriving base port/package names
On Fri, 8 Apr 2016 06:29:31 -0700 (PDT) Roger Marquis wrote: > Ronald F. Guilmette wrote: > > what would be a proper sort of sed command to extract > > _just_ the port/package names, without the version numbers > > attached? > > This has changed in the past so may not currently be 100% correct but > these should work: > >awk -F'-[0-9]' '{ print $1 }' > > or: > >sed 's/-[0-9].*$//' A port name can contain digits and hyphens, so this could remove part of the name. Miroslav's version is better because it requires that the part that's stripped only has a hyphen as it's first character. ___ 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: Deriving base port/package names
On 04/08/16 14:29, Roger Marquis wrote: > Ronald F. Guilmette wrote: >> what would be a proper sort of sed command to extract >> _just_ the port/package names, without the version numbers attached? > > This has changed in the past so may not currently be 100% correct but > these should work: > > awk -F'-[0-9]' '{ print $1 }' > > or: > > sed 's/-[0-9].*$//' > > It's a good question in any case and the answer{,s} should probably be > added to pkg(8)'s EXAMPLES. Well, assuming that you have the default FreeBSD pkg repo set up, then: pkg rquery -a %n will give you a list of all the package names in the repo, which will be pretty close to all the known ports/packages -- there's typically a few that don't build properly. Cheers, Matthew signature.asc Description: OpenPGP digital signature
Re: Deriving base port/package names
Ronald F. Guilmette wrote: what would be a proper sort of sed command to extract _just_ the port/package names, without the version numbers attached? This has changed in the past so may not currently be 100% correct but these should work: awk -F'-[0-9]' '{ print $1 }' or: sed 's/-[0-9].*$//' It's a good question in any case and the answer{,s} should probably be added to pkg(8)'s EXAMPLES. Roger ___ 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"
ports long description error
Was reviewing ports here https://www.freebsd.org/ports/multimedia.html and many of the "Long description" links generated the following error. An Exception Has Occurred An illegal value was provided for the "revision" parameter. HTTP Response Status 400 Bad Request Think someone should take a look into this matter. cx88 ffmpegthumbnailer-2.0.9_1 emby ___ 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 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 +-+ editors/neovim | 0.1.2 | v0.1.3 +-+ 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 Thanks. ___ 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: Deriving base port/package names
Ronald F. Guilmette wrote on 04/08/2016 04:47: Given a list of all current FreeBSD ports/package, such as a (plain text version) the list found here: https://www.freebsd.org/ports/master-index.html and assuming that all text past the ' -- ' has already been deleted from each line, what would be a proper sort of sed command to extract _just_ the port/package names, without the version numbers attached? If your plaintext master-index xontains full lines like this yorick-2.2.04_1 -- Interpreted language for scientific simulations Than you can use this sed line # sed 's/-[0-9a-z.,_+]* --.*$//g' master-index.txt If you have the index stripped to yorick-2.2.04_1 This will do the trick sed 's/-[0-9a-z.,_+]*$//g' master-index.txt Miroslav Lachman ___ 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"