Re: [CFT] Call for testing pkg 1.5.0
On 2015-03-31 20:24, Sergei Vyshenski wrote: Hi, On Tue, Mar 31, 2015 at 9:23 PM, Baptiste Daroussin b...@freebsd.org wrote: Add WITH_PKG=devel in your build make.conf then pkg upgrade will want you to upgrade to 1.4.99.16 (which is pkg 1.5.0 beta1) This does not work for me. # cat /etc/make.conf |grep PKG WITH_PKGNG=yes WITH_PKG=devel # pkg upgrade Updating FreeBSD repository catalogue... FreeBSD repository is up-to-date. All repositories are up-to-date. Checking for upgrades (218 candidates): 100% Processing candidates (218 candidates): 100% Checking integrity... done (0 conflicting) Your packages are up to date. # pkg -v 1.4.12 # pkg info |grep pkg pkg-1.4.12 Package manager Instead, the following succeded: # cd /usr/ports/ports-mgmt/pkg-devel # make reinstall ... # pkg -v 1.4.99.16 All the best, Sergei ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org Baptiste meant that setting WITH_PKG=devel in the make.conf of a poudriere would make it compiled pkg 1.4.99.x and make all users using your repo use that. You'd have to run poudriere to make it rebuild everything with that new make.conf first, before 'pkg upgrade' would upgrade you to 1.4.99.x -- Allan Jude signature.asc Description: OpenPGP digital signature
Re: [CFT] Call for testing pkg 1.5.0
On Fri, Apr 03, 2015 at 02:35:43PM +0100, Big Lebowski wrote: Please test and report as much bugs as you can! We could be very grateful if regressions tests could be provided along with the bug reports :) Mine just did something like that: foobar# uname -a FreeBSD foobar.org 11.0-CURRENT FreeBSD 11.0-CURRENT #0 r280994M: Thu Apr 2 20:16:53 CEST 2015 r...@pd.valinor.palantiri.org:/usr/obj/usr/src/sys/FOOBAR amd64 foobar [uname -a] ~/ 15-04-03 3:33PM foobar# pkg --version 1.4.99.15 foobar [pkg --version] ~/ 15-04-03 3:33PM foobar# pkg version Child process pid=41119 terminated abnormally: Segmentation fault foobar [pkg version] ~/ 15-04-03 3:33PM foobar# pkg version -t 0.2.o.git20150311 0.2.o.20150402 foobar [pkg version -t 0.2.o.git20150311 0.2.o.20150402] ~/ 15-04-03 3:33PM pd# Let me fix that :) Best regards, Bapt pgp2muwHSwmwV.pgp Description: PGP signature
Re: [CFT] Call for testing pkg 1.5.0
I just wanted to take the time to thank you for all the work you've put into this. Thanks! Thanks much appreciated, I want to share that with vsevolod@ and az@ who also spent a lot of time working on it! Indeed, HUGE THANKS for what you guys are doing with pkg - I cant wait to see that OS X integration in action (and other things as well), you rock! S. ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: [CFT] Call for testing pkg 1.5.0
Please test and report as much bugs as you can! We could be very grateful if regressions tests could be provided along with the bug reports :) Mine just did something like that: foobar# uname -a FreeBSD foobar.org 11.0-CURRENT FreeBSD 11.0-CURRENT #0 r280994M: Thu Apr 2 20:16:53 CEST 2015 r...@pd.valinor.palantiri.org:/usr/obj/usr/src/sys/FOOBAR amd64 foobar [uname -a] ~/ 15-04-03 3:33PM foobar# pkg --version 1.4.99.15 foobar [pkg --version] ~/ 15-04-03 3:33PM foobar# pkg version Child process pid=41119 terminated abnormally: Segmentation fault foobar [pkg version] ~/ 15-04-03 3:33PM foobar# pkg version -t 0.2.o.git20150311 0.2.o.20150402 foobar [pkg version -t 0.2.o.git20150311 0.2.o.20150402] ~/ 15-04-03 3:33PM pd# ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: [CFT] Call for testing pkg 1.5.0
On Tue, 31 Mar 2015 21:03:23 +0200 Baptiste Daroussin b...@freebsd.org wrote Hi all, We just released pkg 1.5.0 beta1 (in ports-mgmt/pkg-devel), .. Please test and report as much bugs as you can! We could be very grateful if regressions tests could be provided along with the bug reports :) Plan is to release 1.5.0 as soon as possible Best regards, Bapt Hello, Baptiste. I just wanted to take the time to thank you for all the work you've put into this. Thanks! --Chris ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: [CFT] Call for testing pkg 1.5.0
On Thu, Apr 02, 2015 at 07:21:19AM -0700, Chris H wrote: On Tue, 31 Mar 2015 21:03:23 +0200 Baptiste Daroussin b...@freebsd.org wrote Hi all, We just released pkg 1.5.0 beta1 (in ports-mgmt/pkg-devel), .. Please test and report as much bugs as you can! We could be very grateful if regressions tests could be provided along with the bug reports :) Plan is to release 1.5.0 as soon as possible Best regards, Bapt Hello, Baptiste. I just wanted to take the time to thank you for all the work you've put into this. Thanks! Thanks much appreciated, I want to share that with vsevolod@ and az@ who also spent a lot of time working on it! Best regards, Bapt pgpwXsh20z9bv.pgp Description: PGP signature
Re: [CFT] Call for testing pkg 1.5.0
On Wed, Apr 01, 2015 at 11:48:27AM +, Thomas Mueller wrote: Excerpt from Baptiste Daroussin: - Initial support for OS X - Initial support for NetBSD/EdjeBSD How would pkg-1.5.0 integrate with NetBSD pkgsrc? I didn't think there were any plans to port FreeBSD ports to NetBSD. Or is such a plan in the works? There are people looking at integrating pkg with pkgsrc yes, don't know the status, (pkg is already in pkgsrc-wip but no further integration for what I do know And yes you are right it is EdgeBSD not EdjeBSD sorry. Best regards, Bapt pgpCVf9bVjpMp.pgp Description: PGP signature
Re: [CFT] Call for testing pkg 1.5.0
Excerpt from Baptiste Daroussin: - Initial support for OS X - Initial support for NetBSD/EdjeBSD How would pkg-1.5.0 integrate with NetBSD pkgsrc? I didn't think there were any plans to port FreeBSD ports to NetBSD. Or is such a plan in the works? EdjeBSD should be EdgeBSD. A little spelling error can be critical when trying to find something on the Internet. Web site is edgebsd.org (I just went there). Tom ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: [CFT] Call for testing pkg 1.5.0
On Mar 31, 2015, at 17:24, Sergei Vyshenski svysh.f...@gmail.com wrote: Instead, the following succeded: # cd /usr/ports/ports-mgmt/pkg-devel # make reinstall ... # pkg -v 1.4.99.16 That is expected. WITH_PKG=devel is a make(1) option that only affects ports (non-binary pkgs). -- Rui Paulo ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: [CFT] Call for testing pkg 1.5.0
On 1 Apr 2015, at 05:03, Rui Paulo rpa...@me.com wrote: That is expected. WITH_PKG=devel is a make(1) option that only affects ports (non-binary pkgs). Are you sure? I have it in make.conf on one of my systems where I never build ports manually (and don't even have a ports tree installed) and there I get this: $ pkg -v 1.4.99.13 In a jail on the same machine without the make.conf entry, I get the stable version. This is how I've been testing pkg-devel for a while. Is there a different recommended way? David ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: [CFT] Call for testing pkg 1.5.0
On Wed, Apr 01, 2015 at 01:56:38PM +0100, David Chisnall wrote: On 1 Apr 2015, at 05:03, Rui Paulo rpa...@me.com wrote: That is expected. WITH_PKG=devel is a make(1) option that only affects ports (non-binary pkgs). Are you sure? I have it in make.conf on one of my systems where I never build ports manually (and don't even have a ports tree installed) and there I get this: $ pkg -v 1.4.99.13 In a jail on the same machine without the make.conf entry, I get the stable version. This is how I've been testing pkg-devel for a while. Is there a different recommended way? That is because you enforced installing pkg-devel one day via: pkg install pkg-devel probably then it will stay on pkg-devel :) pkg itself is not aware of make.conf Best regards Bapt pgptYK5cp2usY.pgp Description: PGP signature
Re: [CFT] Call for testing pkg 1.5.0
Hi, On Tue, Mar 31, 2015 at 9:23 PM, Baptiste Daroussin b...@freebsd.org wrote: Add WITH_PKG=devel in your build make.conf then pkg upgrade will want you to upgrade to 1.4.99.16 (which is pkg 1.5.0 beta1) This does not work for me. # cat /etc/make.conf |grep PKG WITH_PKGNG=yes WITH_PKG=devel # pkg upgrade Updating FreeBSD repository catalogue... FreeBSD repository is up-to-date. All repositories are up-to-date. Checking for upgrades (218 candidates): 100% Processing candidates (218 candidates): 100% Checking integrity... done (0 conflicting) Your packages are up to date. # pkg -v 1.4.12 # pkg info |grep pkg pkg-1.4.12 Package manager Instead, the following succeded: # cd /usr/ports/ports-mgmt/pkg-devel # make reinstall ... # pkg -v 1.4.99.16 All the best, Sergei ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
[CFT] Call for testing pkg 1.5.0
Hi all, We just released pkg 1.5.0 beta1 (in ports-mgmt/pkg-devel), Here is what happened since pkg 1.4.0: - pkg has grown with an initial support for provides/requires: this is a naive version but good enough to at least make major upgrade of php safer as well as making pear/pecl maintenance saner (note that this will need modifications in the ports tree) - Lots of new regression tests has been added, which allows us not less break your systems an unexpected way (do not worry there are still rooms for breakage) - Initial support for OS X - Initial support for NetBSD/EdjeBSD - Update most of the bundled third party software has been updated to their latest version - Improve the messages reported by pkg (and probably make some other worse) - Properly support file flags - Implement argument support for custom keywords - Extend setting credential via plist to allow to set file flags - Make credential syntax via plist more flexible allow to only defines the first fields and not latest for example @(user,,) can now be written just @(user) - pkg updating now supports case insensitive matching - pkg create now support a verbose mode - Add an option to change the default on question, until now the default answer was No with that option set it would be Yes - lots of fixes to pkg audit -r - Global memory usage reduction and speed up - Improvements and cleanup on pkg alias - pkg annotate --show --all has been fixed - Make pkg.h C++ friendly - Lots of improvements in the solver - Lots of fixes on 32 bits platforms - Add support for: pkg create -M ./plop.ucl -p ./plop.plist - New pkg -r rootdir that will install in the given rootdir without chrooting - Export PKG_ROOTDIR to scripts allow to make them as portable as possible - Stop trying to remove all installed package with the argument of pkg delete is a local file - Be more explicit about why the solver it going to reinstall, remove or upgrade (when possible) - Plenty of bug fixes - Plenty of new bugs Please test and report as much bugs as you can! We could be very grateful if regressions tests could be provided along with the bug reports :) Plan is to release 1.5.0 as soon as possible Best regards, Bapt pgpTrPipIy92F.pgp Description: PGP signature
Re: [CFT] Call for testing pkg 1.5.0
On Tue, Mar 31, 2015 at 03:19:15PM -0400, Shawn Webb wrote: On Tue, 2015-03-31 at 21:03 +0200, Baptiste Daroussin wrote: Hi all, We just released pkg 1.5.0 beta1 (in ports-mgmt/pkg-devel), Hey Baptiste, Great work to you and all those involved in this project! I'm grateful to have such an awesome tool. For those of us who run our own package repos via Poudriere, what kinds of changes should we expect to make once pkg 1.5.0 is released? Do we need to do a full rebuild of our package repo? I'm also assuming that the upgrade path from 1.4.x to 1.5.0 will simply be as easy as running `pkg upgrade`, right? Thanks again for your hard work. Add WITH_PKG=devel in your build make.conf then pkg upgrade will want you to upgrade to 1.4.99.16 (which is pkg 1.5.0 beta1) Best regards, Bapt pgpvO11OJQASF.pgp Description: PGP signature
Re: [CFT] Call for testing pkg 1.5.0
On Tue, 2015-03-31 at 21:03 +0200, Baptiste Daroussin wrote: Hi all, We just released pkg 1.5.0 beta1 (in ports-mgmt/pkg-devel), Hey Baptiste, Great work to you and all those involved in this project! I'm grateful to have such an awesome tool. For those of us who run our own package repos via Poudriere, what kinds of changes should we expect to make once pkg 1.5.0 is released? Do we need to do a full rebuild of our package repo? I'm also assuming that the upgrade path from 1.4.x to 1.5.0 will simply be as easy as running `pkg upgrade`, right? Thanks again for your hard work. Thanks, Shawn signature.asc Description: This is a digitally signed message part
