public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Rigo <rigo@home.nl>
To: gentoo-dev@gentoo.org
Subject: Re: [gentoo-dev] Portage: good news and bad news
Date: 08 Jul 2002 07:13:11 +0000	[thread overview]
Message-ID: <1026112391.7256.6.camel@lappy.rogi.biz> (raw)
In-Reply-To: <1026023935.29116.94.camel@inventor.gentoo.org>

After updating portage to 2.0.11 I seem to get more errors that before
Daniel ;-)...

Info:

lappy distfiles # emerge --update world
Calculating world dependencies ...done!
>>> emerge media-libs/jpeg-mmx-1.1.2-r1 to /
!!! No message digest found for .
!!! Type "ebuild foo.ebuild digest" to generate a digest.
!!! emerge aborting on 
/usr/portage/media-libs/jpeg-mmx/jpeg-mmx-1.1.2-r1.ebuild .

lappy distfiles # ebuild
/usr/portage/media-libs/jpeg-mmx/jpeg-mmx-1.1.2-r1.ebuild digest

>>> Generating digest file...
Traceback (most recent call last):
  File "/usr/sbin/ebuild", line 33, in ?
    a=portage.doebuild(pargs[0],x,getroot(),debug=debug)
  File "/usr/lib/python2.2/site-packages/portage.py", line 1130, in
doebuild
    digestgen(checkme,overwrite=1)
  File "/usr/lib/python2.2/site-packages/portage.py", line 955, in
digestgen
    mymd5=perform_md5(myfile)
  File "/usr/lib/python2.2/site-packages/portage.py", line 1368, in
perform_md5
    return perform_checksum(x)[0]
  File "/usr/lib/python2.2/site-packages/portage.py", line 39, in
perform_checksum
    return fchksum.fmd5t(filename)
IOError: [Errno 21] Is a directory: '/usr/portage/distfiles/'


Regards, Rigo


Op zo 07-07-2002, om 06:38 schreef Daniel Robbins:
> Hi Devs:
> 
> Bad news: I found a significant bug in Portage 2.0.10 and earlier that
> could cause masking to work improperly, particularly if a package has
a
> ~ entry in the profile's packages file.
> 
> Good news: I've fixed the problem in Portage 2.0.11 by rewriting
> portage.py's portdbapi xmatch() and visible() methods.  This has
> resulted in a 44% speed-up in dependency calculations over Portage
> 2.0.10.  If you thought things were fast before...
> 
> More good news: I've improved repoman to differentiate between
> user-visible ebuilds with bad dependencies and masked ebuilds with bad
> dependencies.  When checking dependencies, user-visible ebuilds'
> dependencies are only matched against user-visible ebuilds. But when
> masked ebuilds are checked, deps are satisfied using *all* available
> ebuilds.  This should eliminate virtually all false positives in the
> repoman DEPEND and RDEPEND QA tests. Type "repoman --help" for more
> information on these new changes.
> 
> Enjoy!
> 
> -- 
> Daniel Robbins
> Chief Architect, Gentoo Linux
> http://www.gentoo.org
> 
> _______________________________________________
> gentoo-dev mailing list
> gentoo-dev@gentoo.org
> http://lists.gentoo.org/mailman/listinfo/gentoo-dev




      parent reply	other threads:[~2002-07-08  7:12 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-07-07  6:38 [gentoo-dev] Portage: good news and bad news Daniel Robbins
2002-07-07 15:39 ` Terje Kvernes
2002-07-07 18:11   ` Chad M. Huneycutt
2002-07-07 20:32     ` Terje Kvernes
2002-07-07 18:59 ` Paul de Vrieze
2002-07-07 19:09   ` Marko Mikulicic
2002-07-08  7:13 ` Rigo [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1026112391.7256.6.camel@lappy.rogi.biz \
    --to=rigo@home.nl \
    --cc=gentoo-dev@gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox