Re: [HEADS UP] Change to the header in ports Makefiles
On 2012-09-01 08:42, Thomas Abthorpe wrote: > An idea has been floating around for some time, and it was brought up again > on the ports@ mailing list recently, please remove the extraneous header > information from the Makefile, leaving only the $FreeBSD$ id on the first > line. > > It is an idea that is long overdue, so from now on, the other fives lines > shall be removed. > > We do request that this be done sparingly in the short term, as we do not > want to cause any additional churn on the repo as we approach our upcoming > Ports Feature Freeze, still tentatively scheduled for September 7. > > So please proceed only on existing updates. Please do not do any sweeping > commits until we have the ports tree stablised post 9.1 tagging. Also bear > in mind that Redports/QAT queues a job for every change done to a Makefile, > we do not want to overburden the QAT at this time. It is important to allow > this service to run at peek efficiency at this time to ensure it's full > potential as we approach the upcoming Feature Freeze. > > The new look of the Makefile has been document in the Porter's Handbook, > http://www.freebsd.org/doc/en_US.ISO8859-1/books/porters-handbook/quick-porting.html#PORTING-MAKEFILE. > > The next item on the todo list is to update devel/newfile for those that do > a port create. > Hi Thomas, I have a bigger change for www/apache22 (rewrite for options NG) and devel/apr1 (PR 165143) in the pipe. Those changes address at last 5+ PR's and apache22 PORTREVISION will be bumped. If possible I would have the changes in place before tagging 9.1 or should I wait until 9.1 is finished? -- Regards, olli ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: csup vs portsnap was: fresh install of kde4 fails -> japanese/kiten
[ RW wrote on Sat 1.Sep'12 at 0:49:54 +0100 ] > On Wed, 29 Aug 2012 10:27:14 -0700 > Jim Pazarena wrote: > > > > Which is the recommended way to stay PORT current? portsnap or csup? > > I will switch to portsnap, but it is pretty slow compared to csup. > > In normal use portsnap should be much faster than csup. > > The initial "portsnap extract" is much slower than a normal "update", > and fetching the first compressed snapshot or updating a really ancient > one is slower than a normal "fetch" - beyond that portsnap is very fast. Agreed. After the first run of `portsnap fetch extract`, subsequent fetch and update using portsnap is certainly faster. ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: [HEADS UP] Change to the header in ports Makefiles
On Saturday, September 01, 2012 06:42:57 Thomas Abthorpe wrote: > Also bear in mind that Redports/QAT queues a job for every change done to a > Makefile, we do not want to overburden the QAT at this time. It is important > to allow this service to run at peek efficiency at this time to ensure it's > full potential as we approach the upcoming Feature Freeze. I think it would be good to note that Redports can be made to ignore a commit and not queue an unnecessary job by adding: Redports: ignore to the commit message. - Jason ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: Regression in PREFIX handling in packages
On Wed, 29 Aug 2012 22:02:46 +0200 Alexander Leidinger
wrote:
> And this one is tested (copy&paste, may have lost tabs and add
> linebreaks from my mailer):
> ---snip---
> # svn diff
> Index: perform.c
> ===
> --- perform.c (revision 239708)
> +++ perform.c (working copy)
> @@ -215,10 +215,15 @@
>
> /* Prefix should add an @cwd to the packing list */
> if (Prefix) {
> -char resolved_prefix[PATH_MAX];
> -if (realpath(Prefix, resolved_prefix) == NULL)
> - err(EXIT_FAILURE, "couldn't resolve path for prefix: %s",
> Prefix);
> - add_plist_top(&plist, PLIST_CWD, resolved_prefix);
> + if (Prefix[0] != '/') {
> + char resolved_prefix[PATH_MAX];
> + if (realpath(Prefix, resolved_prefix) == NULL)
> + err(EXIT_FAILURE,
> + "couldn't resolve path for prefix: %s",
> Prefix);
> + add_plist_top(&plist, PLIST_CWD, resolved_prefix);
> + } else {
> + add_plist_top(&plist, PLIST_CWD, Prefix);
> + }
> }
>
> /* Add the origin if asked, at the top */
> ---snip---
Can I go ahead and commit this?
Bye,
Alexander.
--
http://www.Leidinger.netAlexander @ Leidinger.net: PGP ID = B0063FE7
http://www.FreeBSD.org netchild @ FreeBSD.org : PGP ID = 72077137
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: [HEADS UP] Change to the header in ports Makefiles
On Sat, Sep 01, 2012 at 07:27:40AM -0400, Jason E. Hale wrote: > On Saturday, September 01, 2012 06:42:57 Thomas Abthorpe wrote: > > Also bear in mind that Redports/QAT queues a job for every change done to a > > Makefile, we do not want to overburden the QAT at this time. It is important > > to allow this service to run at peek efficiency at this time to ensure it's > > full potential as we approach the upcoming Feature Freeze. > > I think it would be good to note that Redports can be made to ignore a commit > and not queue an unnecessary job by adding: > > Redports: ignore > > to the commit message. > > - Jason Cool thanks, I am still learning the finer points of Redports. Thomas -- Thomas Abthorpe | FreeBSD Committer tabtho...@freebsd.org | http://people.freebsd.org/~tabthorpe pgpUsjvnYjggS.pgp Description: PGP signature
question about pkgconf vs pkg-config
Hi, According to /usr/ports/UPDATING we are supposed to switch to pkgconf. 20120726: AFFECTS: users of devel/pkg-config devel/pkg-config has been replaced by devel/pkgconf I understand "replaced" to mean that pkg-config is out. There does not appear to be a man page for pkgconf at the moment. I have created a .pc file for libpq (databases/postgresql92-client), which works with pkg-config, ie # pkg-config --libs libpq -Wl,-rpath,/usr/local/lib -L/usr/local/lib it's not found by pkgconf # pkgconf --libs libpq Package libpq was not found in the pkg-config search path. Perhaps you should add the directory containing `libpq.pc' to the PKG_CONFIG_PATH environment variable No package 'libpq' found ie, gcc48 -Wall `pkg-config --cflags --libs libpq` ... vs gcc48 -Wall `pkgconf --cflags --libs libpq` ... # man pkgconf No manual entry for pkgconf # pkgconf --list-all this list appears to be based on /var/db/pkgs, which maybe is the idea(?) anyhow, Postgres doesn't show up in --list-all. I'm wondering about how to manually add libraries to pkgconf, or the proper way to get the Postgres Client port to register libpq. (and for example, libxine which appears to me to have a similar issue). Thank you, -- Waitman Gobble San Jose California USA ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
apache22 options NG rewrite testers wanted
Hi all, I need some testers specially on 9/10-current to test the www/apache22 optionsNG rewrite. I have a report from a 10-current user where we see a make regression, but it is not clear if the regression is in make or the ports framework therefore I need some more testers. What does the patch address - optons NG rewrite of bsd.apache.mk and apache22 - rename port to apache22 so we have no conflicts with upcoming apache24 (pkg install apache22) - apr/apr-util specific options are gone, apr/apu-util will be used now to control the build (THREADS, PGSQL, MYSQL ...) - PR 130479 - PR 153406 - PR 158565 - PR 167965 - PR 168769 - PR 165143 devel/apr1 long outstanding update and removal of PKGNAMESUFFIX The patch should be applied from /usr/ports (contains fixes for Mk/ www/ and devel/ ) http://people.freebsd.org/~ohauer/diffs/apache/apache22_optionsNG_2012-09-01.diff Thanks for your help, olli ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: pkgng suggestion: renaming /usr/sbin/pkg to /usr/sbin/pkg-bootstrap
On 31-08-2012 14:22, Baptiste Daroussin wrote: > On Fri, Aug 31, 2012 at 08:10:50AM -0400, John Baldwin wrote: >> On Friday, August 31, 2012 5:59:10 am Baptiste Daroussin wrote: >>> On Thu, Aug 30, 2012 at 01:02:06PM -1000, Doug Barton wrote: I agree with John on all counts here. Further, the idea of a self-installing package, at least for the pkg stuff itself, addresses the issue that someone else brought up about how to handle installation of pkg by the installer for a new system. >>> >>> I like the idea of also providing a self-installing package, and it seems >>> really >>> easy to do, so I'll try to see what I can do in this area I'll wrote a PoC >>> in 5 >>> minutes which looks pretty good, this could also be a very simple and easy >>> way >>> to integrate into bsdinstaller. >>> >>> I'll do work in that direction. >>> >>> Still it doesn't solve the problem of boostrapping pkgng in a fresh new box, >>> because the user may not know where to download the pkg-setup.sh. >> >> I do think that is something bsdinstall should be able to handle, and I would >> certainly want bsdinstall to include a dialog that says "do you want to >> install >> the package manager?" > > Of course this is being worked on by dteske@ on his bsdconfig scripts, so yes > in > anycase the bsdinstaller will end up with a boostrap dialog to install pkgng. Something else I thought of, you can't assume there's a working internet connection during installation. And also, even if there is a connection, can you guarantee that the downloaded pkg supports the packages on the dvd for the lifetime of the release? I really think you should just do vendor imports of pkg in base and include pkg on the dvd. There's no bootstrap problem then and the dvd is nicely self-contained. It also shouldn't be a problem to keep the official pkg repo for that release compatible with it. Just keep using the same version of pkg to create the repo. You've been able to develop and introduce pkgng without breaking older releases which shows having pkg tools tied to releases was never a problem. All that was needed was to move pkg development outside base. You should be able to do pkg 2.0 development in the same way. And when that new version is ready you import betas and release candidates in head and use current users as testers, just like is done with clang. In this scenario the ports tree needs to keep support for older releases, but that's a consequence of the fact that there's only one ports tree for all releases. Somewhere in between the ports and the various releases there has to be some form encapsulation, not just for pkg, but for all the tools used by the ports tree. Given how the ports tree currently encapsulates both the old and new pkg tools I don't see how supporting multiple versions of pkgng would be a problem because presumably the difference between pkgng versions is going to be much smaller than the difference between the old and new tools. signature.asc Description: OpenPGP digital signature
Re: apache22 options NG rewrite testers wanted
Olli Hauer wrote .. > Hi all, > > I need some testers specially on 9/10-current to test the www/apache22 > optionsNG rewrite. > > I have a report from a 10-current user where we see a make regression, but > it is not clear if the regression is in make or the ports framework > therefore I need some more testers. > > What does the patch address > - optons NG rewrite of bsd.apache.mk and apache22 > - rename port to apache22 so we have no conflicts with upcoming apache24 >(pkg install apache22) > - apr/apr-util specific options are gone, apr/apu-util will be used now >to control the build (THREADS, PGSQL, MYSQL ...) > - PR 130479 > - PR 153406 > - PR 158565 > - PR 167965 > - PR 168769 > > - PR 165143 >devel/apr1 long outstanding update and removal of PKGNAMESUFFIX > > The patch should be applied from /usr/ports > (contains fixes for Mk/ www/ and devel/ ) > > http://people.freebsd.org/~ohauer/diffs/apache/apache22_optionsNG_2012-09-01.diff > > Thanks for your help, > olli > ___ > freebsd-ports@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-ports > To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org" Hi Olli, Looks like there have been quite a few updates since 8/11, last time I did a rebuild. Patch didn't work on my src... I'll take some time tomorrow to csup and rebuild and try out your patch. -- Waitman Gobble San Jose California USA ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: apache22 options NG rewrite testers wanted
On 2012-09-01 19:45, Waitman Gobble wrote: > Olli Hauer wrote .. >> Hi all, >> >> I need some testers specially on 9/10-current to test the www/apache22 >> optionsNG rewrite. >> >> I have a report from a 10-current user where we see a make regression, but >> it is not clear if the regression is in make or the ports framework >> therefore I need some more testers. >> >> What does the patch address >> - optons NG rewrite of bsd.apache.mk and apache22 >> - rename port to apache22 so we have no conflicts with upcoming apache24 >>(pkg install apache22) >> - apr/apr-util specific options are gone, apr/apu-util will be used now >>to control the build (THREADS, PGSQL, MYSQL ...) >> - PR 130479 >> - PR 153406 >> - PR 158565 >> - PR 167965 >> - PR 168769 >> >> - PR 165143 >>devel/apr1 long outstanding update and removal of PKGNAMESUFFIX >> >> The patch should be applied from /usr/ports >> (contains fixes for Mk/ www/ and devel/ ) >> >> http://people.freebsd.org/~ohauer/diffs/apache/apache22_optionsNG_2012-09-01.diff >> >> Thanks for your help, >> olli > > Hi Olli, > > Looks like there have been quite a few updates since 8/11, last time I did a > rebuild. Patch didn't work on my src... > I'll take some time tomorrow to csup and rebuild and try out your patch. > Thanks, I haven't tested the patches against csup ports there the $FreeBSD$ header is different, so I just shaped a tar archive. http://people.freebsd.org/~ohauer/diffs/apache/apache22_optNG.tar.bz2 -- Regards, olli ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: pkgng suggestion: renaming /usr/sbin/pkg to /usr/sbin/pkg-bootstrap
On 9/1/2012 7:43 PM, Tijl Coosemans wrote: On 31-08-2012 14:22, Baptiste Daroussin wrote: On Fri, Aug 31, 2012 at 08:10:50AM -0400, John Baldwin wrote: On Friday, August 31, 2012 5:59:10 am Baptiste Daroussin wrote: On Thu, Aug 30, 2012 at 01:02:06PM -1000, Doug Barton wrote: I agree with John on all counts here. Further, the idea of a self-installing package, at least for the pkg stuff itself, addresses the issue that someone else brought up about how to handle installation of pkg by the installer for a new system. I like the idea of also providing a self-installing package, and it seems really easy to do, so I'll try to see what I can do in this area I'll wrote a PoC in 5 minutes which looks pretty good, this could also be a very simple and easy way to integrate into bsdinstaller. I'll do work in that direction. Still it doesn't solve the problem of boostrapping pkgng in a fresh new box, because the user may not know where to download the pkg-setup.sh. I do think that is something bsdinstall should be able to handle, and I would certainly want bsdinstall to include a dialog that says "do you want to install the package manager?" Of course this is being worked on by dteske@ on his bsdconfig scripts, so yes in anycase the bsdinstaller will end up with a boostrap dialog to install pkgng. Something else I thought of, you can't assume there's a working internet connection during installation. And also, even if there is a connection, can you guarantee that the downloaded pkg supports the packages on the dvd for the lifetime of the release? The packages set included on the dvd will probably be EOLed before the lifetime of the release. I really think you should just do vendor imports of pkg in base and include pkg on the dvd. There's no bootstrap problem then and the dvd is nicely self-contained. It also shouldn't be a problem to keep the official pkg repo for that release compatible with it. Just keep using the same version of pkg to create the repo. You've been able to develop and introduce pkgng without breaking older releases which shows having pkg tools tied to releases was never a problem. All that was needed was to move pkg development outside base. You should be able to do pkg 2.0 development in the same way. And when that new version is ready you import betas and release candidates in head and use current users as testers, just like is done with clang. In this scenario the ports tree needs to keep support for older releases, but that's a consequence of the fact that there's only one ports tree for all releases. Somewhere in between the ports and the various releases there has to be some form encapsulation, not just for pkg, but for all the tools used by the ports tree. Given how the ports tree currently encapsulates both the old and new pkg tools I don't see how supporting multiple versions of pkgng would be a problem because presumably the difference between pkgng versions is going to be much smaller than the difference between the old and new tools. ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: apache22 options NG rewrite testers wanted
Olli Hauer wrote .. > On 2012-09-01 19:45, Waitman Gobble wrote: > > Olli Hauer wrote .. > >> Hi all, > >> > >> I need some testers specially on 9/10-current to test the www/apache22 > >> optionsNG rewrite. > >> > >> I have a report from a 10-current user where we see a make regression, but > >> it is not clear if the regression is in make or the ports framework > >> therefore I need some more testers. > >> > >> What does the patch address > >> - optons NG rewrite of bsd.apache.mk and apache22 > >> - rename port to apache22 so we have no conflicts with upcoming apache24 > >>(pkg install apache22) > >> - apr/apr-util specific options are gone, apr/apu-util will be used now > >>to control the build (THREADS, PGSQL, MYSQL ...) > >> - PR 130479 > >> - PR 153406 > >> - PR 158565 > >> - PR 167965 > >> - PR 168769 > >> > >> - PR 165143 > >>devel/apr1 long outstanding update and removal of PKGNAMESUFFIX > >> > >> The patch should be applied from /usr/ports > >> (contains fixes for Mk/ www/ and devel/ ) > >> > >> http://people.freebsd.org/~ohauer/diffs/apache/apache22_optionsNG_2012-09-01.diff > >> > >> Thanks for your help, > >> olli > > > > Hi Olli, > > > > Looks like there have been quite a few updates since 8/11, last time I did a > rebuild. Patch didn't work on my src... > > I'll take some time tomorrow to csup and rebuild and try out your patch. > > > > Thanks, > > I haven't tested the patches against csup ports there the $FreeBSD$ header is > different, > so I just shaped a tar archive. > http://people.freebsd.org/~ohauer/diffs/apache/apache22_optNG.tar.bz2 > > -- > Regards, > olli > > ___ > freebsd-ports@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-ports > To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org" Thanks, I tried the following, no issues. machine - # uname -a FreeBSD hunny.waitman.net 10.0-CURRENT FreeBSD 10.0-CURRENT #0: Sat Aug 11 13:25:18 PDT 2012 r...@hunny.waitman.net:/usr/obj/usr/src/sys/KEYSHIA amd64 I did not previously have www/apache22 installed on this machine. replace devel/apr1 www/apache22 Mk/bsd.apache.mk # cd /usr/ports/www/apache22 # make -- OK # make install -- OK # make package -- OK # make deinstall -- OK # pkg_add apache22-2.2.22_7.tbz -- OK # make deinstall -- OK # pkg_add apache22-2.2.22_7.tbz -- OK # pkg_delete apache22-2.2.22_7 -- OK # make install -- OK # make readme -- OK # kldload accf_http # /usr/local/sbin/apachectl start -- OK # wget http://localhost --2012-09-01 11:23:22-- http://localhost/ Resolving localhost (localhost)... 127.0.0.1, ::1 Connecting to localhost (localhost)|127.0.0.1|:80... connected. HTTP request sent, awaiting response... 200 OK Length: 44 [text/html] Saving to: `index.html' 100%[==>] 44 --.-K/s in 0s 2012-09-01 11:23:22 (6.60 MB/s) - `index.html' saved [44/44] # cat index.html It works! Is there anything you'd like me to test? I have another machine sitting here running 9 I can test if you like. But it's busy for the day transcoding a boatload of video, so I can do that one tomorrow if you likes. # uname -a FreeBSD kamira.waitman.net 9.1-RC1 FreeBSD 9.1-RC1 #0: Tue Aug 14 04:25:06 UTC 2012 r...@farrell.cse.buffalo.edu:/usr/obj/usr/src/sys/GENERIC amd64 -- Waitman Gobble San Jose California USA ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: apache22 options NG rewrite testers wanted
On 2012-09-01 20:28, Waitman Gobble wrote: > Olli Hauer wrote .. >> On 2012-09-01 19:45, Waitman Gobble wrote: >>> Olli Hauer wrote .. Hi all, I need some testers specially on 9/10-current to test the www/apache22 optionsNG rewrite. I have a report from a 10-current user where we see a make regression, but it is not clear if the regression is in make or the ports framework therefore I need some more testers. What does the patch address - optons NG rewrite of bsd.apache.mk and apache22 - rename port to apache22 so we have no conflicts with upcoming apache24 (pkg install apache22) - apr/apr-util specific options are gone, apr/apu-util will be used now to control the build (THREADS, PGSQL, MYSQL ...) - PR 130479 - PR 153406 - PR 158565 - PR 167965 - PR 168769 - PR 165143 devel/apr1 long outstanding update and removal of PKGNAMESUFFIX The patch should be applied from /usr/ports (contains fixes for Mk/ www/ and devel/ ) http://people.freebsd.org/~ohauer/diffs/apache/apache22_optionsNG_2012-09-01.diff Thanks for your help, olli >>> >>> Hi Olli, >>> >>> Looks like there have been quite a few updates since 8/11, last time I did a >> rebuild. Patch didn't work on my src... >>> I'll take some time tomorrow to csup and rebuild and try out your patch. >>> >> >> Thanks, >> >> I haven't tested the patches against csup ports there the $FreeBSD$ header >> is different, >> so I just shaped a tar archive. >> http://people.freebsd.org/~ohauer/diffs/apache/apache22_optNG.tar.bz2 >> >> -- >> Regards, >> olli >> >> ___ >> freebsd-ports@freebsd.org mailing list >> http://lists.freebsd.org/mailman/listinfo/freebsd-ports >> To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org" > > > Thanks, > I tried the following, no issues. > machine - > # uname -a > FreeBSD hunny.waitman.net 10.0-CURRENT FreeBSD 10.0-CURRENT #0: Sat Aug 11 > 13:25:18 PDT 2012 r...@hunny.waitman.net:/usr/obj/usr/src/sys/KEYSHIA > amd64 > > I did not previously have www/apache22 installed on this machine. > > > replace devel/apr1 www/apache22 Mk/bsd.apache.mk > > # cd /usr/ports/www/apache22 > # make -- OK > # make install -- OK > # make package -- OK > # make deinstall -- OK > # pkg_add apache22-2.2.22_7.tbz -- OK > # make deinstall -- OK > # pkg_add apache22-2.2.22_7.tbz -- OK > # pkg_delete apache22-2.2.22_7 -- OK > # make install -- OK > # make readme -- OK > > > # kldload accf_http > # /usr/local/sbin/apachectl start -- OK > # wget http://localhost > --2012-09-01 11:23:22-- http://localhost/ > Resolving localhost (localhost)... 127.0.0.1, ::1 > Connecting to localhost (localhost)|127.0.0.1|:80... connected. > HTTP request sent, awaiting response... 200 OK > Length: 44 [text/html] > Saving to: `index.html' > > 100%[==>] 44 --.-K/s in 0s > > > 2012-09-01 11:23:22 (6.60 MB/s) - `index.html' saved [44/44] > > # cat index.html > It works! > > > > Is there anything you'd like me to test? > > > I have another machine sitting here running 9 I can test if you like. But > it's busy for the day transcoding a boatload of video, so I can do that one > tomorrow if you likes. > > # uname -a > FreeBSD kamira.waitman.net 9.1-RC1 FreeBSD 9.1-RC1 #0: Tue Aug 14 04:25:06 > UTC 2012 r...@farrell.cse.buffalo.edu:/usr/obj/usr/src/sys/GENERIC amd64 > > Hm yes, we found on a 10-current system a regression in case ALIAS, AUTHN_ALIAS, VHOST_ALIAS was selected. As soon you hit OK in 'make config' the line OPTIONS_FILE_SET+=ALIAS changed to OPTIONS_FILE_UNSET+=ALIAS in /var/db/ports/apache22/options Will be nice if you could 'grep ALIAS /var/db/ports/apache22/options' Adjust with 'make config' and grep again (or save the option file and do a diff) We investigate at the moment if this was a specific 10-current issue or an issue in the ports/options/apache framework. (but this will take some time longer because of 10 hours tz difference) Thanks, olli ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: apache22 options NG rewrite testers wanted
olli hauer wrote .. > On 2012-09-01 20:28, Waitman Gobble wrote: > > Olli Hauer wrote .. > >> On 2012-09-01 19:45, Waitman Gobble wrote: > >>> Olli Hauer wrote .. > Hi all, > > I need some testers specially on 9/10-current to test the www/apache22 > optionsNG rewrite. > > I have a report from a 10-current user where we see a make regression, > but > it is not clear if the regression is in make or the ports framework > therefore I need some more testers. > > What does the patch address > - optons NG rewrite of bsd.apache.mk and apache22 > - rename port to apache22 so we have no conflicts with upcoming apache24 > (pkg install apache22) > - apr/apr-util specific options are gone, apr/apu-util will be used now > to control the build (THREADS, PGSQL, MYSQL ...) > - PR 130479 > - PR 153406 > - PR 158565 > - PR 167965 > - PR 168769 > > - PR 165143 > devel/apr1 long outstanding update and removal of PKGNAMESUFFIX > > The patch should be applied from /usr/ports > (contains fixes for Mk/ www/ and devel/ ) > > http://people.freebsd.org/~ohauer/diffs/apache/apache22_optionsNG_2012-09-01.diff > > Thanks for your help, > olli > >>> > >>> Hi Olli, > >>> > >>> Looks like there have been quite a few updates since 8/11, last time I did > a > >> rebuild. Patch didn't work on my src... > >>> I'll take some time tomorrow to csup and rebuild and try out your patch. > >>> > >> > >> Thanks, > >> > >> I haven't tested the patches against csup ports there the $FreeBSD$ header > >> is > different, > >> so I just shaped a tar archive. > >> http://people.freebsd.org/~ohauer/diffs/apache/apache22_optNG.tar.bz2 > >> > >> -- > >> Regards, > >> olli > >> > >> ___ > >> freebsd-ports@freebsd.org mailing list > >> http://lists.freebsd.org/mailman/listinfo/freebsd-ports > >> To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org" > > > > > > Thanks, > > I tried the following, no issues. > > machine - > > # uname -a > > FreeBSD hunny.waitman.net 10.0-CURRENT FreeBSD 10.0-CURRENT #0: Sat Aug 11 > > 13:25:18 > PDT 2012 r...@hunny.waitman.net:/usr/obj/usr/src/sys/KEYSHIA amd64 > > > > I did not previously have www/apache22 installed on this machine. > > > > > > replace devel/apr1 www/apache22 Mk/bsd.apache.mk > > > > # cd /usr/ports/www/apache22 > > # make -- OK > > # make install -- OK > > # make package -- OK > > # make deinstall -- OK > > # pkg_add apache22-2.2.22_7.tbz -- OK > > # make deinstall -- OK > > # pkg_add apache22-2.2.22_7.tbz -- OK > > # pkg_delete apache22-2.2.22_7 -- OK > > # make install -- OK > > # make readme -- OK > > > > > > # kldload accf_http > > # /usr/local/sbin/apachectl start -- OK > > # wget http://localhost > > --2012-09-01 11:23:22-- http://localhost/ > > Resolving localhost (localhost)... 127.0.0.1, ::1 > > Connecting to localhost (localhost)|127.0.0.1|:80... connected. > > HTTP request sent, awaiting response... 200 OK > > Length: 44 [text/html] > > Saving to: `index.html' > > > > 100%[==>] 44 --.-K/s in 0s > > > > 2012-09-01 11:23:22 (6.60 MB/s) - `index.html' saved [44/44] > > > > # cat index.html > > It works! > > > > > > > > Is there anything you'd like me to test? > > > > > > I have another machine sitting here running 9 I can test if you like. But > > it's > busy for the day transcoding a boatload of video, so I can do that one > tomorrow > if you likes. > > > > # uname -a > > FreeBSD kamira.waitman.net 9.1-RC1 FreeBSD 9.1-RC1 #0: Tue Aug 14 04:25:06 > > UTC > 2012 r...@farrell.cse.buffalo.edu:/usr/obj/usr/src/sys/GENERIC amd64 > > > > > > Hm yes, we found on a 10-current system a regression in case ALIAS, > AUTHN_ALIAS, > VHOST_ALIAS was selected. > As soon you hit OK in 'make config' the line > OPTIONS_FILE_SET+=ALIAS changed to > OPTIONS_FILE_UNSET+=ALIAS in /var/db/ports/apache22/options > > Will be nice if you could 'grep ALIAS /var/db/ports/apache22/options' > Adjust with 'make config' and grep again (or save the option file and do a > diff) > > We investigate at the moment if this was a specific 10-current issue or an > issue > in the ports/options/apache framework. > (but this will take some time longer because of 10 hours tz difference) > > Thanks, > olli > > ___ > freebsd-ports@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-ports > To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org" OK, I can do that... BUT those three options were 'already' selected when i did the test... # grep ALIAS /var/db/ports/apache22/options _FILE_COMPLETE_OPTIONS_LIST= AUTH_BASIC AUTH_DIGEST AUTHN_ALIAS AUTHN_ANON AUTHN_DBD AUTHN_DBM AUTHN_DEFAULT AUTHN_FILE AUTHZ_DBM AUTHZ_DEFAULT AUT
Re: apache22 options NG rewrite testers wanted
On 2012-09-01 21:06, Waitman Gobble wrote: > olli hauer wrote .. >> On 2012-09-01 20:28, Waitman Gobble wrote: >>> Olli Hauer wrote .. On 2012-09-01 19:45, Waitman Gobble wrote: > Olli Hauer wrote .. >> Hi all, >> >> I need some testers specially on 9/10-current to test the www/apache22 >> optionsNG rewrite. >> >> I have a report from a 10-current user where we see a make regression, >> but >> it is not clear if the regression is in make or the ports framework >> therefore I need some more testers. >> >> What does the patch address >> - optons NG rewrite of bsd.apache.mk and apache22 >> - rename port to apache22 so we have no conflicts with upcoming apache24 >>(pkg install apache22) >> - apr/apr-util specific options are gone, apr/apu-util will be used now >>to control the build (THREADS, PGSQL, MYSQL ...) >> - PR 130479 >> - PR 153406 >> - PR 158565 >> - PR 167965 >> - PR 168769 >> >> - PR 165143 >>devel/apr1 long outstanding update and removal of PKGNAMESUFFIX >> >> The patch should be applied from /usr/ports >> (contains fixes for Mk/ www/ and devel/ ) >> >> http://people.freebsd.org/~ohauer/diffs/apache/apache22_optionsNG_2012-09-01.diff >> >> Thanks for your help, >> olli > > Hi Olli, > > Looks like there have been quite a few updates since 8/11, last time I did >> a rebuild. Patch didn't work on my src... > I'll take some time tomorrow to csup and rebuild and try out your patch. > Thanks, I haven't tested the patches against csup ports there the $FreeBSD$ header is >> different, so I just shaped a tar archive. http://people.freebsd.org/~ohauer/diffs/apache/apache22_optNG.tar.bz2 -- Regards, olli ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org" >>> >>> >>> Thanks, >>> I tried the following, no issues. >>> machine - >>> # uname -a >>> FreeBSD hunny.waitman.net 10.0-CURRENT FreeBSD 10.0-CURRENT #0: Sat Aug 11 >>> 13:25:18 >> PDT 2012 r...@hunny.waitman.net:/usr/obj/usr/src/sys/KEYSHIA amd64 >>> >>> I did not previously have www/apache22 installed on this machine. >>> >>> >>> replace devel/apr1 www/apache22 Mk/bsd.apache.mk >>> >>> # cd /usr/ports/www/apache22 >>> # make -- OK >>> # make install -- OK >>> # make package -- OK >>> # make deinstall -- OK >>> # pkg_add apache22-2.2.22_7.tbz -- OK >>> # make deinstall -- OK >>> # pkg_add apache22-2.2.22_7.tbz -- OK >>> # pkg_delete apache22-2.2.22_7 -- OK >>> # make install -- OK >>> # make readme -- OK >>> >>> >>> # kldload accf_http >>> # /usr/local/sbin/apachectl start -- OK >>> # wget http://localhost >>> --2012-09-01 11:23:22-- http://localhost/ >>> Resolving localhost (localhost)... 127.0.0.1, ::1 >>> Connecting to localhost (localhost)|127.0.0.1|:80... connected. >>> HTTP request sent, awaiting response... 200 OK >>> Length: 44 [text/html] >>> Saving to: `index.html' >>> >>> 100%[==>] 44 --.-K/s in 0s >>> >>> 2012-09-01 11:23:22 (6.60 MB/s) - `index.html' saved [44/44] >>> >>> # cat index.html >>> It works! >>> >>> >>> >>> Is there anything you'd like me to test? >>> >>> >>> I have another machine sitting here running 9 I can test if you like. But >>> it's >> busy for the day transcoding a boatload of video, so I can do that one >> tomorrow >> if you likes. >>> >>> # uname -a >>> FreeBSD kamira.waitman.net 9.1-RC1 FreeBSD 9.1-RC1 #0: Tue Aug 14 04:25:06 >>> UTC >> 2012 r...@farrell.cse.buffalo.edu:/usr/obj/usr/src/sys/GENERIC amd64 >>> >>> >> >> Hm yes, we found on a 10-current system a regression in case ALIAS, >> AUTHN_ALIAS, >> VHOST_ALIAS was selected. >> As soon you hit OK in 'make config' the line >> OPTIONS_FILE_SET+=ALIAS changed to >> OPTIONS_FILE_UNSET+=ALIAS in /var/db/ports/apache22/options >> >> Will be nice if you could 'grep ALIAS /var/db/ports/apache22/options' >> Adjust with 'make config' and grep again (or save the option file and do a >> diff) >> >> We investigate at the moment if this was a specific 10-current issue or an >> issue >> in the ports/options/apache framework. >> (but this will take some time longer because of 10 hours tz difference) >> >> Thanks, >> olli >> > > OK, I can do that... BUT those three options were 'already' selected when i > did the test... snip ... So it seems more and more the reported issue is a local one. Thanks, olli ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: Plugins support in pkgng
On Sat, Sep 1, 2012 at 6:17 AM, Bryan Drewery wrote: > On 8/31/2012 10:15 PM, Eitan Adler wrote: >> On 31 August 2012 09:15, Bryan Drewery wrote: >> >>> No, because it already knows which you installed and which were pulled >>> in as dependencies. There's a recent thread on ports@ regarding pkg2ng >>> and marking your imported packages as automatic or not. >> >> There is a usecase for looking at all the leaf ports one by one and >> deciding if you want to keep them, recursively, regardless of the >> automatic flag. >> >> Even if this isn't provided by default, it would be nice for plugins >> to be able to do this. :) >> >> > > Apparently pkg_cutleaves supports pkgng now anyhow. Hi all, Support for plugins which provide new commands in pkgng has been committed. Example plugin which provides a new command can be found below and used as a template when developing a new plugin: - https://github.com/pkgng/pkgng/tree/master/plugins/pkg-plugin-mystats-command Regards, Marin > > Bryan > -- Marin Atanasov Nikolov dnaeon AT gmail DOT com http://www.unix-heaven.org/ ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: Plugins support in pkgng
On 9/1/2012 2:46 PM, Marin Atanasov Nikolov wrote: > Support for plugins which provide new commands in pkgng has been committed. Very cool! -- Regards, Bryan Drewery bdrewery@freenode/EFNet ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: apache22 options NG rewrite testers wanted
olli hauer wrote .. > On 2012-09-01 21:06, Waitman Gobble wrote: > > olli hauer wrote .. > >> On 2012-09-01 20:28, Waitman Gobble wrote: > >>> Olli Hauer wrote .. > On 2012-09-01 19:45, Waitman Gobble wrote: > > Olli Hauer wrote .. > >> Hi all, > >> > >> I need some testers specially on 9/10-current to test the www/apache22 > >> optionsNG rewrite. > >> > >> I have a report from a 10-current user where we see a make regression, > >> but > >> it is not clear if the regression is in make or the ports framework > >> therefore I need some more testers. > >> > >> What does the patch address > >> - optons NG rewrite of bsd.apache.mk and apache22 > >> - rename port to apache22 so we have no conflicts with upcoming > >> apache24 > >>(pkg install apache22) > >> - apr/apr-util specific options are gone, apr/apu-util will be used > >> now > >>to control the build (THREADS, PGSQL, MYSQL ...) > >> - PR 130479 > >> - PR 153406 > >> - PR 158565 > >> - PR 167965 > >> - PR 168769 > >> > >> - PR 165143 > >>devel/apr1 long outstanding update and removal of PKGNAMESUFFIX > >> > >> The patch should be applied from /usr/ports > >> (contains fixes for Mk/ www/ and devel/ ) > >> > >> http://people.freebsd.org/~ohauer/diffs/apache/apache22_optionsNG_2012-09-01.diff > >> > >> Thanks for your help, > >> olli > > > > Hi Olli, > > > > Looks like there have been quite a few updates since 8/11, last time I > > did > >> a > rebuild. Patch didn't work on my src... > > I'll take some time tomorrow to csup and rebuild and try out your patch. > > > > Thanks, > > I haven't tested the patches against csup ports there the $FreeBSD$ > header > is > >> different, > so I just shaped a tar archive. > http://people.freebsd.org/~ohauer/diffs/apache/apache22_optNG.tar.bz2 > > -- > Regards, > olli > > ___ > freebsd-ports@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-ports > To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org" > >>> > >>> > >>> Thanks, > >>> I tried the following, no issues. > >>> machine - > >>> # uname -a > >>> FreeBSD hunny.waitman.net 10.0-CURRENT FreeBSD 10.0-CURRENT #0: Sat Aug 11 > 13:25:18 > >> PDT 2012 r...@hunny.waitman.net:/usr/obj/usr/src/sys/KEYSHIA amd64 > >>> > >>> I did not previously have www/apache22 installed on this machine. > >>> > >>> > >>> replace devel/apr1 www/apache22 Mk/bsd.apache.mk > >>> > >>> # cd /usr/ports/www/apache22 > >>> # make -- OK > >>> # make install -- OK > >>> # make package -- OK > >>> # make deinstall -- OK > >>> # pkg_add apache22-2.2.22_7.tbz -- OK > >>> # make deinstall -- OK > >>> # pkg_add apache22-2.2.22_7.tbz -- OK > >>> # pkg_delete apache22-2.2.22_7 -- OK > >>> # make install -- OK > >>> # make readme -- OK > >>> > >>> > >>> # kldload accf_http > >>> # /usr/local/sbin/apachectl start -- OK > >>> # wget http://localhost > >>> --2012-09-01 11:23:22-- http://localhost/ > >>> Resolving localhost (localhost)... 127.0.0.1, ::1 > >>> Connecting to localhost (localhost)|127.0.0.1|:80... connected. > >>> HTTP request sent, awaiting response... 200 OK > >>> Length: 44 [text/html] > >>> Saving to: `index.html' > >>> > >>> 100%[==>] 44 --.-K/s in 0s > >>> > >>> 2012-09-01 11:23:22 (6.60 MB/s) - `index.html' saved [44/44] > >>> > >>> # cat index.html > >>> It works! > >>> > >>> > >>> > >>> Is there anything you'd like me to test? > >>> > >>> > >>> I have another machine sitting here running 9 I can test if you like. But > >>> it's > >> busy for the day transcoding a boatload of video, so I can do that one > >> tomorrow > >> if you likes. > >>> > >>> # uname -a > >>> FreeBSD kamira.waitman.net 9.1-RC1 FreeBSD 9.1-RC1 #0: Tue Aug 14 04:25:06 > UTC > >> 2012 r...@farrell.cse.buffalo.edu:/usr/obj/usr/src/sys/GENERIC amd64 > >>> > >>> > >> > >> Hm yes, we found on a 10-current system a regression in case ALIAS, > >> AUTHN_ALIAS, > >> VHOST_ALIAS was selected. > >> As soon you hit OK in 'make config' the line > >> OPTIONS_FILE_SET+=ALIAS changed to > >> OPTIONS_FILE_UNSET+=ALIAS in /var/db/ports/apache22/options > >> > >> Will be nice if you could 'grep ALIAS /var/db/ports/apache22/options' > >> Adjust with 'make config' and grep again (or save the option file and do a > >> diff) > >> > >> We investigate at the moment if this was a specific 10-current issue or an > >> issue > >> in the ports/options/apache framework. > >> (but this will take some time longer because of 10 hours tz difference) > >> > >> Thanks, > >> olli > >> > > > > OK, I can do that... BUT those three options were 'already' selected when i > > did > the test... > > snip ... > > > So it
Re: [HEADS UP] Change to the header in ports Makefiles
On Sat, Sep 01, 2012 at 06:42:57AM +, Thomas Abthorpe wrote: > An idea has been floating around for some time, and it was brought up again > on the ports@ mailing list recently, please remove the extraneous header > information from the Makefile, leaving only the $FreeBSD$ id on the first > line. > > It is an idea that is long overdue, so from now on, the other fives lines > shall be removed. > > We do request that this be done sparingly in the short term, as we do not > want to cause any additional churn on the repo as we approach our upcoming > Ports Feature Freeze, still tentatively scheduled for September 7. > > So please proceed only on existing updates. Please do not do any sweeping > commits until we have the ports tree stablised post 9.1 tagging. Also bear > in mind that Redports/QAT queues a job for every change done to a Makefile, > we do not want to overburden the QAT at this time. It is important to allow > this service to run at peek efficiency at this time to ensure it's full > potential as we approach the upcoming Feature Freeze. > > The new look of the Makefile has been document in the Porter's Handbook, > http://www.freebsd.org/doc/en_US.ISO8859-1/books/porters-handbook/quick-porting.html#PORTING-MAKEFILE. > > The next item on the todo list is to update devel/newfile for those that do > a port create. > > > Thomas > on behalf of portmgr@ > > > http://blogs.freebsdish.org/portmgr/2012/09/01/change-to-the-header-in-ports-makefiles/ Cease fire on stripping header information. Seems there is more to the issue that we will need to resolved before we proceed, so please update ports normally, please leave the header intact. If you have already stripped some headers, leave it alone for now. Thomas -- Thomas Abthorpe | FreeBSD Committer tabtho...@freebsd.org | http://people.freebsd.org/~tabthorpe pgp1hXTJAt55k.pgp Description: PGP signature
[CFT] net/gatekeeper: fixed DoS, CVE-2012-3534
I had backported denial-of-service fixes from version 3.1, http://codelabs.ru/fbsd/ports/gatekeeper/gnugk-fix-cve-2012-3534.diff but I don't use GNU gatekeeper in production. Patched version contains new configuration knob, MaxStatusClients, that is 20 by-default and is used to limit the number of simultaneous connections. I am interested in - testing that the patched version works and has no regressions; - MaxStatusClients really works. Thanks in advance. -- Eygene Ryabinkin,,,^..^,,, [ Life's unfair - but root password helps! | codelabs.ru ] [ 82FE 06BC D497 C0DE 49EC 4FF0 16AF 9EAE 8152 ECFB | freebsd.org ] pgpnXw9npJuzq.pgp Description: PGP signature
Re: [HEADS UP] Change to the header in ports Makefiles
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 As far as I'm concerned, the commiters will take care of this when they need to. Leaving current port headers in-tact is the best way to go regardless of this discussion... On 09/01/2012 10:00 PM, Thomas Abthorpe wrote: > On Sat, Sep 01, 2012 at 06:42:57AM +, Thomas Abthorpe wrote: >> An idea has been floating around for some time, and it was >> brought up again on the ports@ mailing list recently, please >> remove the extraneous header information from the Makefile, >> leaving only the $FreeBSD$ id on the first line. >> >> It is an idea that is long overdue, so from now on, the other >> fives lines shall be removed. >> >> We do request that this be done sparingly in the short term, as >> we do not want to cause any additional churn on the repo as we >> approach our upcoming Ports Feature Freeze, still tentatively >> scheduled for September 7. >> >> So please proceed only on existing updates. Please do not do any >> sweeping commits until we have the ports tree stablised post 9.1 >> tagging. Also bear in mind that Redports/QAT queues a job for >> every change done to a Makefile, we do not want to overburden the >> QAT at this time. It is important to allow this service to run at >> peek efficiency at this time to ensure it's full potential as we >> approach the upcoming Feature Freeze. >> >> The new look of the Makefile has been document in the Porter's >> Handbook, >> http://www.freebsd.org/doc/en_US.ISO8859-1/books/porters-handbook/quick-porting.html#PORTING-MAKEFILE. >> >> >> The next item on the todo list is to update devel/newfile for those that do >> a port create. >> >> >> Thomas on behalf of portmgr@ >> >> >> http://blogs.freebsdish.org/portmgr/2012/09/01/change-to-the-header-in-ports-makefiles/ > >> > Cease fire on stripping header information. > > Seems there is more to the issue that we will need to resolved > before we proceed, so please update ports normally, please leave > the header intact. > > If you have already stripped some headers, leave it alone for now. > > > Thomas > -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.11 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://www.enigmail.net/ iEYEARECAAYFAlBC4I8ACgkQGK3MsUbJZn6GCwCeN56F4Lwpr3gYczUnzf7qNoY8 TxEAn1EVCF0eiPMn0SXSg86c6FFAF2bv =kW6o -END PGP SIGNATURE- ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
