From: Patrick Kursawe <phosphan@gentoo.org>
To: gentoo-dev@gentoo.org, carpaski@gentoo.org
Subject: Re: [gentoo-dev] Re: emerge -Up tetex wants to downgrade
Date: Wed, 30 Apr 2003 07:50:03 +0200 [thread overview]
Message-ID: <20030430055003.GA29420@zaphod.anachem.ruhr-uni-bochum.de> (raw)
In-Reply-To: <87ptn5gvkc.fsf@tdg.loria.fr>
[-- Attachment #1: Type: text/plain, Size: 1147 bytes --]
On Tue, Apr 29, 2003 at 05:41:39PM +0200, duchier@ps.uni-sb.de wrote:
> Patrick Kursawe <phosphan@gentoo.org> writes:
>
> >> Calculating world dependencies ...done!
> >> [ebuild UD] app-text/tetex-1.0.7-r12 [2.0-r1]
> >
> > Tetex 2.0-r1 has been removed from portage. It looks like emerge
> > tries to be on the safe side and rather downgrade than keep
> > a version it does not know about. If you upgrade to tetex-2.0.2,
> > emerge -U should no longer try to downgrade.
>
> Thank you very much! That explains it and your suggestion fixed the
> problem. However, is this really the _right_ behaviour?
>
> o portage actually knows something about tetex 2.0-r1 since it is
> emerged
>
> o --upgradeonly promises to not downgrade: regardless of whether
> there is currently an ebuild for the installed version, the
> version is known, and IMHO that fixes the semantics of
> downgrading
>
> o maybe --pretend could provide an indication that no ebuild for
> the currently installed version can be found
>
> Comments?
Nicholas, are you following this thread?
Patrick
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2003-04-30 5:50 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-04-28 20:01 [gentoo-dev] emerge -Up tetex wants to downgrade Denys Duchier
2003-04-29 0:53 ` Daniel Armyr
2003-04-29 7:06 ` Patrick Kursawe
2003-04-29 15:41 ` [gentoo-dev] " duchier
2003-04-30 5:50 ` Patrick Kursawe [this message]
2003-05-01 9:07 ` Nick Jones
2003-05-01 9:22 ` Denys Duchier
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=20030430055003.GA29420@zaphod.anachem.ruhr-uni-bochum.de \
--to=phosphan@gentoo.org \
--cc=carpaski@gentoo.org \
--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