From: "Gila" <Gila@Gila.tuxed.net>
To: <gentoo-dev@gentoo.org>
Subject: Re: [gentoo-dev] Portage 1.9.1 --> 1.9.2
Date: Thu, 25 Apr 2002 17:48:54 -0000 (UTC) [thread overview]
Message-ID: <51623.212.120.110.169.1019756934.squirrel@Gila.tuxed.net> (raw)
In-Reply-To: <20020425153340.GB25415@mdy.univie.ac.at>
hmmz.. portage 1.9.2 should be masked then imho
> On Thu, Apr 25, 2002 at 10:28:25AM -0500, Fuper wrote:
>> On Thu, 2002-04-25 at 04:48, Gila wrote:
>> > Hi there.. i having a problem merging the new portage version.
>> >
>> > root@Gitop portage # emerge portage
>> > Calculating dependencies \
>> > !!! Error: couldn't find match for dev-python/python-fchksum in
>> > sys-apps/portage-1.9.2
>>
>> same here. The emerge fails.
>>
>
> Ah, me too :-/
>
> The fun part is that a portage-1.9.2.ebuild fetched today
> has the python-fchksum dependency, but python-fchksum is masked (as of
> two hours ago). Strangely, a portage-1.9.2 I rsynched yesterday (two
> days ago) doesn't have this dependency, builds and works fine. (So I
> copied it to the affected machine and was back in business). I guess
> we just have to wait a bit more till the latest round of problems (I
> mean the one that started with circular dependency hell, python 2.2.-6
> and portage 1.9.3) sorts itself out.
>
> No emerge rsyncs for me in the next few days ...
>
> Stefan
>
> _______________________________________________
> gentoo-dev mailing list
> gentoo-dev@gentoo.org
> http://lists.gentoo.org/mailman/listinfo/gentoo-dev
prev parent reply other threads:[~2002-04-25 17:49 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-04-25 9:48 [gentoo-dev] Portage 1.9.1 --> 1.9.2 Gila
2002-04-25 15:08 ` Gontran
2002-04-25 15:48 ` Fuper
2002-04-25 15:28 ` Fuper
2002-04-25 15:33 ` Stefan Boresch
2002-04-25 17:48 ` Gila [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=51623.212.120.110.169.1019756934.squirrel@Gila.tuxed.net \
--to=gila@gila.tuxed.net \
--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