Re: [gentoo-dev] Packages not yet converted to Manifest2
> pcheck -r $PORTDIR '*' -c Manifest2Transition I am trying to finish the transition: - cvs up a category - try(some of them are unfetchable) to fix all pkgs that pcheck reports Hope it goes smoothly. -- Best Regards, Piotr Jaroszyński -- gentoo-dev@gentoo.org mailing list
Re: [gentoo-dev] Packages not yet converted to Manifest2
On Wed, 21 Feb 2007 09:40:43 -0800 Mike Doty <[EMAIL PROTECTED]> wrote: > Are people using old versions of portage? when flameeyes worked on > this, he did all but *4*(not 4%) so I'm wondering how it creeped back up. Most likely he didn't detect all packages (haven't seen his script). Marius -- gentoo-dev@gentoo.org mailing list
Re: [gentoo-dev] Packages not yet converted to Manifest2
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Wed, 21 Feb 2007, Marius Mauch wrote: Updated versions of the list will be available at dev.gentoo.org/~genone/reports/mf2 Please provide complete URLs. It's not so hard to type an extra 7 characters :) Also your mail client does not appear to line-wrap. Cheers, - -- Jason Wever Gentoo/Sparc Team Co-Lead -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.6 (GNU/Linux) iD8DBQFF3JDxdKvgdVioq28RAoFiAJ9zwbp02+R2NXui2mRcvggQPxeU7QCbBBWq QoJHc/OPnat3SJfYZqDeQ4A= =OgS1 -END PGP SIGNATURE- -- gentoo-dev@gentoo.org mailing list
Re: [gentoo-dev] Packages not yet converted to Manifest2
Mike Doty wrote: > Marius Mauch wrote: >> While Diego did an awesome job with converting many packages to >> Manifest2 there are still about 400 packages that aren't converted >> yet. If you maintain any package in the attached list please update it >> to use Manifest2. >> >> To update a package make sure that you're using portage-2.1.2-r9 or >> later, run `ebuild foo.ebuild manifest` (doesn't matter which version >> you pick for that command) and commit it. >> >> Updated versions of the list will be available at >> dev.gentoo.org/~genone/reports/mf2 >> >> Marius >> > Are people using old versions of portage? when flameeyes worked on > this, he did all but *4*(not 4%) so I'm wondering how it creeped back up. > According to viewcvs for example gnustep-libs/artresources has not been touched in 10 months so I guess the script Diego used to find unported things did not find everything: http://viewcvs.gentoo.org/viewcvs.py/gentoo-x86/gnustep-libs/artresources/ Regards, Petteri signature.asc Description: OpenPGP digital signature
Re: [gentoo-dev] Packages not yet converted to Manifest2
Marius Mauch wrote: While Diego did an awesome job with converting many packages to Manifest2 there are still about 400 packages that aren't converted yet. If you maintain any package in the attached list please update it to use Manifest2. To update a package make sure that you're using portage-2.1.2-r9 or later, run `ebuild foo.ebuild manifest` (doesn't matter which version you pick for that command) and commit it. Updated versions of the list will be available at dev.gentoo.org/~genone/reports/mf2 Marius Are people using old versions of portage? when flameeyes worked on this, he did all but *4*(not 4%) so I'm wondering how it creeped back up. -- === Mike Doty kingtaco -at- gentoo.org Gentoo/AMD64 Strategic Lead Gentoo Council Gentoo Developer Relations Gentoo Infrastructure GPG: E1A5 1C9C 93FE F430 C1D6 F2AF 806B A2E4 19F4 AE05 === -- gentoo-dev@gentoo.org mailing list
Re: [gentoo-dev] Packages not yet converted to Manifest2
On Wed, Feb 21, 2007 at 03:16:27PM +0100, Marius Mauch wrote: > While Diego did an awesome job with converting many packages to > Manifest2 there are still about 400 packages that aren't converted > yet. If you maintain any package in the attached list please update > it to use Manifest2. > > To update a package make sure that you're using portage-2.1.2-r9 or > later, run `ebuild foo.ebuild manifest` (doesn't matter which > version you pick for that command) and commit it. Mind you, having only 4% of the tree still at m1 is good- the problem is that around 20% (around 2.3k pkgs) of the m2 packages are broken. Around 70% of the issue comes down to manifests containing just size data for a distfile- the other 30% is having size, rmd160, and sha256, but lacking sha1- ironically, the only required checksum for m2. At http://pkgcore.org/~ferringb/manifest2-broken-packages.log is the list of the horked cat/pkgs (would attach it, but it's 45k). I'm lazy, so if you want it regenerated bug someone (or merge pkgcore-checks-0.3.1) to run pcheck -r $PORTDIR '*' -c Manifest2Transition adding "--reporter strreporter" if they want an easily greppable version. The full logs for this list are at http://pkgcore.org/~ferringb/manifest-simple.log, with a more human readable version at http://pkgcore.org/~ferringb/manifest-fancy.log . Reiterating; for m2 transition to occur, the size screwups at the very least has to be fixed; the missing sha1 m2s are problematic, but they at least have chksum data for all files. ~harring pgpWHXwkzJad2.pgp Description: PGP signature
