Re: Upgrading ports problem with portupgrade(pkgng)
On 12/22/2012 2:15 PM, Beach Geek wrote: > System: FreeBSD/i386 10-current, base/head(src)=r244363, ports/head=r309344. > > I upgraded to r244363 from an Oct 3rd(ish) version. Followed ports/UPDATING > for pkgng to edit make.conf and convert pkgdb.db. > > I'm now trying to update my ports (from tree, not pkgs), and I get: > > # portupgrade -ae > USING PKGNG > Stale dependency: ORBit2-2.14.19 --> glib-2.28.8_4 -- manually run > 'pkgdb -F' to fix, or specify -O to force. > > # pkgdb -F USING PKGNG pkgdb -F not supported with PKGNG yet. Use 'pkg > check' directly. > > # pkg check -d (also tried pkg check -d -a) > # > > Running portupgrade -ae gives same message as before. > > Went to port tree, upgraded glib with 'make deinstall reinstall clean'. > Then > # pkg info glib glib-2.28.8_5 Some useful routines of C programming > (current stable version) > > Run portupgrade -ae.. same message. > > Could someone point me in the right direction... > > If I'm misunderstanding the man & wiki pages, please explain (I'll even > wear the pointyhat). > > Thanks, BG Maintainer of portupgrade here... I did not see this post until just now. It should be enough to just install the missing dependencies. You may have to do this manually outside of portupgrade, and then run 'pkgdb -uf'. I am exploring how to make this automatically fix itself. If all else fails, portmaster is an option as well. You don't *have* to use packages. -- Regards, Bryan Drewery bdrewery@freenode/EFNet signature.asc Description: OpenPGP digital signature
Re: Upgrading ports problem with portupgrade(pkgng)
On Dec 27, 2012 10:08 AM, "Beach Geek" wrote: > > > > > System: FreeBSD/i386 10-current, base/head(src)=r244363, ports/head=r309344. > > > > > > I upgraded to r244363 from an Oct 3rd(ish) version. Followed ports/UPDATING for pkgng to edit make.conf and convert pkgdb.db. > > > > > > I'm now trying to update my ports (from tree, not pkgs), and I get: > > > > > > # portupgrade -ae > > > USING PKGNG > > > Stale dependency: ORBit2-2.14.19 --> glib-2.28.8_4 -- manually run 'pkgdb -F' to fix, or specify -O to force. > > > > > > # pkgdb -F USING PKGNG pkgdb -F not supported with PKGNG yet. Use 'pkg check' directly. > > > > > > # pkg check -d (also tried pkg check -d -a) > > > # > > > > > > Running portupgrade -ae gives same message as before. > > > > > > Went to port tree, upgraded glib with 'make deinstall reinstall clean'. Then > > > # pkg info glib glib-2.28.8_5 Some useful routines of C programming (current stable version) > > > > > > Run portupgrade -ae.. same message. > > > > > > Could someone point me in the right direction... > > > > > > If I'm misunderstanding the man & wiki pages, please explain (I'll even wear the pointyhat). > > > > > > Thanks, BG > > > > An update. > > 4 servers have the problem in my previous post, and I've yet to find a way to use portupgrade. > > Only answers I've received were to use packages via pkgng. (Not an option). > > > > For the other 9 servers, I tried it a little differently. > > - switch to pkgng > > - svn base and ports > > - upgrade base > > - upgrade ports with portupgrade. > > > > Worked fine for 8 of 9. > > > > Will be rolling the 5 broke servers back (yes, we have bkups) ;) > > > > Will leave the 8 working ones running pkgbg, and see how it goes. > > > > Still wondering, how to repair the database w/o pkgfb -F so portupgrade will work? > > > > And as I understand, poudriere must be used instead of portupgrade to create packages? > > > > Thanks, > > BG > > Please post responses here instead of emailing me directly. > > Only "fixes" that have been suggested are: > * use packages only > * delete all packages and /usr/local, then reinstall all packages. > > For ppl that want to build/install ports from the ports tree, what are our options for fixing pkg db problems so we can keep ports upgraded? > > Note: "pkg check" is missing on wiki page. > > BG My apologies, I missed the replies from Matthew and Baptiste. They weren't in my mailbox, saw them while browsing mailing list. We have clusters of 13 box each. Only 1 cluster is running Current and using pkgng, and is just for testing/playing. (Other clusters just upgraded to 9.1) I try using poudriere, setting up a repo for this cluster. (I guess later a repo per each different configured cluster) Thanks for the help and information. Not sure I understand it yet, but that's what this 'devel' cluster is for. BG ___ 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: Upgrading ports problem with portupgrade(pkgng)
> > System: FreeBSD/i386 10-current, base/head(src)=r244363, ports/head=r309344. > > > > I upgraded to r244363 from an Oct 3rd(ish) version. Followed ports/UPDATING for pkgng to edit make.conf and convert pkgdb.db. > > > > I'm now trying to update my ports (from tree, not pkgs), and I get: > > > > # portupgrade -ae > > USING PKGNG > > Stale dependency: ORBit2-2.14.19 --> glib-2.28.8_4 -- manually run 'pkgdb -F' to fix, or specify -O to force. > > > > # pkgdb -F USING PKGNG pkgdb -F not supported with PKGNG yet. Use 'pkg check' directly. > > > > # pkg check -d (also tried pkg check -d -a) > > # > > > > Running portupgrade -ae gives same message as before. > > > > Went to port tree, upgraded glib with 'make deinstall reinstall clean'. Then > > # pkg info glib glib-2.28.8_5 Some useful routines of C programming (current stable version) > > > > Run portupgrade -ae.. same message. > > > > Could someone point me in the right direction... > > > > If I'm misunderstanding the man & wiki pages, please explain (I'll even wear the pointyhat). > > > > Thanks, BG > > An update. > 4 servers have the problem in my previous post, and I've yet to find a way to use portupgrade. > Only answers I've received were to use packages via pkgng. (Not an option). > > For the other 9 servers, I tried it a little differently. > - switch to pkgng > - svn base and ports > - upgrade base > - upgrade ports with portupgrade. > > Worked fine for 8 of 9. > > Will be rolling the 5 broke servers back (yes, we have bkups) ;) > > Will leave the 8 working ones running pkgbg, and see how it goes. > > Still wondering, how to repair the database w/o pkgfb -F so portupgrade will work? > > And as I understand, poudriere must be used instead of portupgrade to create packages? > > Thanks, > BG Please post responses here instead of emailing me directly. Only "fixes" that have been suggested are: * use packages only * delete all packages and /usr/local, then reinstall all packages. For ppl that want to build/install ports from the ports tree, what are our options for fixing pkg db problems so we can keep ports upgraded? Note: "pkg check" is missing on wiki page. BG ___ 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: Upgrading ports problem with portupgrade(pkgng)
Sorry for the formatting. (The other webmail I could use is even more problematic). --- On Sun, 12/23/12, Beach Geek wrote: From: Beach Geek Subject: Re: Upgrading ports problem with portupgrade(pkgng) To: freebsd-ports@freebsd.org Date: Sunday, December 23, 2012, 1:05 PM On Dec 22, 2012 2:15 PM, "Beach Geek" wrote: > > System: FreeBSD/i386 10-current, base/head(src)=r244363, ports/head=r309344. > > I upgraded to r244363 from an Oct 3rd(ish) version. Followed ports/UPDATING for pkgng to edit make.conf and convert pkgdb.db. > > I'm now trying to update my ports (from tree, not pkgs), and I get: > > # portupgrade -ae > USING PKGNG > Stale dependency: ORBit2-2.14.19 --> glib-2.28.8_4 -- manually run 'pkgdb -F' to fix, or specify -O to force. > > # pkgdb -F USING PKGNG pkgdb -F not supported with PKGNG yet. Use 'pkg check' directly. > > # pkg check -d (also tried pkg check -d -a) > # > > Running portupgrade -ae gives same message as before. > > Went to port tree, upgraded glib with 'make deinstall reinstall clean'. Then > # pkg info glib glib-2.28.8_5 Some useful routines of C programming (current stable version) > > Run portupgrade -ae.. same message. > > Could someone point me in the right direction... > > If I'm misunderstanding the man & wiki pages, please explain (I'll even wear the pointyhat). > > Thanks, BG An update. 4 servers have the problem in my previous post, and I've yet to find a way to use portupgrade. Only answers I've received were to use packages via pkgng. (Not an option). For the other 9 servers, I tried it a little differently. - switch to pkgng - svn base and ports - upgrade base - upgrade ports with portupgrade. Worked fine for 8 of 9. Will be rolling the 5 broke servers back (yes, we have bkups) ;) Will leave the 8 working ones running pkgbg, and see how it goes. Still wondering, how to repair the database w/o pkgfb -F so portupgrade will work? And as I understand, poudriere must be used instead of portupgrade to create packages? Thanks, BG ___ 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" I would hope that pkgng not be the default before someone writes a huge flowchart pointing out all or most all of the here-to-there scenarios, for instance if one uses a -devel version of some /devel/ port suddenly, some packages break, for instance some machines run v8 some run v10, which ports won't be in the official build cluster and would commonly need to be built locally, and a slew of other issues which may be slowly added to the flowchart as the years go by, so that questions would be fewer all around. (Hoping also for a GEOM flowchart, a CUPS flowchart, ... but that is off topic for this email...) BTW I've a methodology to rapidly dispense with unknown-but-need-upgrading dependency upgrading (which just uncovered a slew of ports which won't build, most with a similar error) and it heavily relies upon the /var/db/pkg/ structure for ease of use. I also wish that an adjunct to the pkg(ng) include an option for that structure so that that ease of use is not abstracted in a yet unknown way. If this will all be minor issues vs actual implementation of a v10 default pkg system, I apologize in advance. (After all, most or all of the ports which won't currently build here I seldom if ever actually have time to use...) J. Bouquet ___ 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: Upgrading ports problem with portupgrade(pkgng)
On Sun, Dec 23, 2012 at 09:39:02PM +, Matthew Seaman wrote: > On 23/12/2012 21:05, Beach Geek wrote: > > And as I understand, poudriere must be used instead of portupgrade to > > create packages? > > That's not right. > >poudriere is an offline pkg building system, designed to build >packages in a sandbox, and then create a pkgng repository accessible >to various client machines. You can use it locally to maintain a >single machine, but that's sort of missing the point. It only works >with pkgng, although I believe you can run it on a non-pkgng machine >to create a repo for maintaining other pkgng-enabled machines. Last part is not entirely true, poudriere can work work both pkgng and pkg_install it is not pkgng only. yes it can run on a non-pkgng machine, but it still needs pkgng to be install on the host (installed not necessary used). and it can work on a pkgng machine to build pkg_install packages without the need of the pkg_install tools on the host. It can also be used to maintain a single machine, by creating the repository of packages and once done you can simply install/upgrade them using pkgng. It is very convenient, and easy to do, because it is fast (poudriere is heavily parallelized) it allows the users to really upgrade things when they all succeed at building, meaning your system is always safe. It allows you to allows be png or pcre upgrade proof, because such upgrade will be detected by poudriere without the need of a bump in portrevision. If the user end up with a missing libpcre.so.1 a simple pkg install -fR pcre will fix the situation almost immediatly. > >portmaster and portupgrade cover basically the same territory. >They're designed to maintain the locally installed package set on a >machine. To that end, both of them are wrappers around the ports, >and facilitate installing packages by compiling the relevant port >source code. The can also use binary packages, typically from a >FreeBSD ftp server. Initially they used pkg_tools packages, but >both have been modified to work with pkgng packages as well. > >pkgng is a package registry application and a binary package >manager. It doesn't understand the ports. However, if you have >access to a suitable source of pre-compiled packages you can use >just pkgng to manage those, and have no need for portmaster or >portupgrade. poudriere is intended to provide that 'suitable >source.' although once the official pkg build cluster gets up and >running, users should be able to use that instead. > > Cheers. > > Matthew > regards, Bapt pgppwxLSqNIbA.pgp Description: PGP signature
Re: Upgrading ports problem with portupgrade(pkgng)
On 23/12/2012 21:05, Beach Geek wrote: > And as I understand, poudriere must be used instead of portupgrade to > create packages? That's not right. poudriere is an offline pkg building system, designed to build packages in a sandbox, and then create a pkgng repository accessible to various client machines. You can use it locally to maintain a single machine, but that's sort of missing the point. It only works with pkgng, although I believe you can run it on a non-pkgng machine to create a repo for maintaining other pkgng-enabled machines. portmaster and portupgrade cover basically the same territory. They're designed to maintain the locally installed package set on a machine. To that end, both of them are wrappers around the ports, and facilitate installing packages by compiling the relevant port source code. The can also use binary packages, typically from a FreeBSD ftp server. Initially they used pkg_tools packages, but both have been modified to work with pkgng packages as well. pkgng is a package registry application and a binary package manager. It doesn't understand the ports. However, if you have access to a suitable source of pre-compiled packages you can use just pkgng to manage those, and have no need for portmaster or portupgrade. poudriere is intended to provide that 'suitable source.' although once the official pkg build cluster gets up and running, users should be able to use that instead. Cheers. Matthew -- Dr Matthew J Seaman MA, D.Phil. PGP: http://www.infracaninophile.co.uk/pgpkey signature.asc Description: OpenPGP digital signature
Re: Upgrading ports problem with portupgrade(pkgng)
On Dec 22, 2012 2:15 PM, "Beach Geek" wrote: > > System: FreeBSD/i386 10-current, base/head(src)=r244363, ports/head=r309344. > > I upgraded to r244363 from an Oct 3rd(ish) version. Followed ports/UPDATING for pkgng to edit make.conf and convert pkgdb.db. > > I'm now trying to update my ports (from tree, not pkgs), and I get: > > # portupgrade -ae > USING PKGNG > Stale dependency: ORBit2-2.14.19 --> glib-2.28.8_4 -- manually run 'pkgdb -F' to fix, or specify -O to force. > > # pkgdb -F USING PKGNG pkgdb -F not supported with PKGNG yet. Use 'pkg check' directly. > > # pkg check -d (also tried pkg check -d -a) > # > > Running portupgrade -ae gives same message as before. > > Went to port tree, upgraded glib with 'make deinstall reinstall clean'. Then > # pkg info glib glib-2.28.8_5 Some useful routines of C programming (current stable version) > > Run portupgrade -ae.. same message. > > Could someone point me in the right direction... > > If I'm misunderstanding the man & wiki pages, please explain (I'll even wear the pointyhat). > > Thanks, BG An update. 4 servers have the problem in my previous post, and I've yet to find a way to use portupgrade. Only answers I've received were to use packages via pkgng. (Not an option). For the other 9 servers, I tried it a little differently. - switch to pkgng - svn base and ports - upgrade base - upgrade ports with portupgrade. Worked fine for 8 of 9. Will be rolling the 5 broke servers back (yes, we have bkups) ;) Will leave the 8 working ones running pkgbg, and see how it goes. Still wondering, how to repair the database w/o pkgfb -F so portupgrade will work? And as I understand, poudriere must be used instead of portupgrade to create packages? Thanks, BG ___ 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"
