From: Jason Stubbs <jasonbstubbs@mailandnews.com>
To: gentoo-dev@gentoo.org
Subject: Re: [gentoo-dev] Blocking a specific package version
Date: Thu, 21 Aug 2003 15:51:13 +0900 [thread overview]
Message-ID: <200308211551.13450.jasonbstubbs@mailandnews.com> (raw)
In-Reply-To: <20030821061155.GE31265@zaphod.anachem.ruhr-uni-bochum.de>
On Thursday 21 August 2003 15:11, Patrick Kursawe wrote:
> On Thu, Aug 21, 2003 at 08:01:17AM +0200, Patrick Kursawe wrote:
> > =media-libs/divx4linux-20020418*
> > !media-libs/divx4linux-2003*
> > (in both DEPEND and RDEPEND)
> >
> > which just makes nvrec downgrade divx4linux before it's installed, but
> > does not stop me from upgrading it afterwards (which breaks nvrec).
>
> Indeed it looks like adding a version to a blocked package just results
> in ignoring the line.
>
> (portage-2.0.48-r5)
First post on this list... just a lowly user... tell me to keep my nose out if
necessary! ;-)
I recently updated to gcc 3.3 and was having a hard time as portage kept on
wanting to downgrade it. Turned out that glibc-2.3.2-r1 wanted a lower
version and I had to unmask glibc-2.3.2-r3 to keep gcc as it was. Point is
glibc-2.3.2-r1 contains nothing gcc-related in RDEPEND and only the following
in DEPEND:
=sys-devel/gcc-3.2*
Also using portage-2.0.48-r5. Makes me think it's something else causing it to
not take notice of the dep.
Regards,
Jason
--
gentoo-dev@gentoo.org mailing list
prev parent reply other threads:[~2003-08-21 6:56 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-08-20 16:00 [gentoo-dev] Blocking a specific package version Patrick Kursawe
2003-08-20 16:26 ` Svyatogor
2003-08-20 16:38 ` Lloyd D Budd
2003-08-20 16:57 ` Max Kalika
2003-08-20 16:49 ` Lloyd D Budd
2003-08-20 17:49 ` Mike Frysinger
2003-08-20 18:27 ` Paul de Vrieze
2003-08-21 6:01 ` Patrick Kursawe
2003-08-21 6:11 ` Patrick Kursawe
2003-08-21 6:51 ` Jason Stubbs [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=200308211551.13450.jasonbstubbs@mailandnews.com \
--to=jasonbstubbs@mailandnews.com \
--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