how to hold a package at a specific version (so emerge -uD world doesn't change it)?
I am doing a 'emerge -uD' but one of the packages the version currently
in portage doesn't compile, so I want to keep my current version, and
prevent emerge from trying to update it. How can I put a package on hold
(like in Debian)?
I tried inserting:
=x11-wm/awesome-3.1-r1 ~amd64
in /etc/portage/package.keywords
but 'emerge -uD world' still tries to build x11-wm/awesome-3.1.1
which fails, so the whole process is stopped.
01-28-2009, 03:08 PM
Stroller
how to hold a package at a specific version (so emerge -uD world doesn't change it)?
On 28 Jan 2009, at 15:33, Miernik wrote:
I am doing a 'emerge -uD' but one of the packages the version
currently
in portage doesn't compile, so I want to keep my current version, and
prevent emerge from trying to update it. How can I put a package on
hold
(like in Debian)?
I tried inserting:
=x11-wm/awesome-3.1-r1 ~amd64
in /etc/portage/package.keywords
but 'emerge -uD world' still tries to build x11-wm/awesome-3.1.1
which fails, so the whole process is stopped.
I think you need to use /etc/portage/package.mask instead.
Stroller.
01-28-2009, 07:10 PM
Neil Bothwick
how to hold a package at a specific version (so emerge -uD world doesn't change it)?
On Wed, 28 Jan 2009 11:48:37 -0500, Joshua Murphy wrote:
> > =x11-wm/awesome-3.1-r1 ~amd64
> >
> > in /etc/portage/package.keywords
> >
> > but 'emerge -uD world' still tries to build x11-wm/awesome-3.1.1
> > which fails, so the whole process is stopped.
>
> echo >x11-wm/awesome-3.1-r1 >> /etc/portage/package.mask
> # and to prevent downgrades
That blocks all future updates, not just the broken one.
--
Neil Bothwick
If there is light at the end of the tunnel...order more tunnel.
01-28-2009, 07:41 PM
how to hold a package at a specific version (so emerge -uD world doesn't change it)?
Sorry for topposting (BlackBerry behavior).
I think that if emerge =x11-wm/awesome-3.1.1 fails, you should file a bug before masking it.
================
Momesso Andrea
================
-----Original Message-----
From: Neil Bothwick <neil@digimed.co.uk>
Date: Wed, 28 Jan 2009 20:10:05
To: <gentoo-user@lists.gentoo.org>
Subject: Re: [gentoo-user] how to hold a package at a specific version (so
emerge -uD world doesn't change it)?
On Wed, 28 Jan 2009 11:48:37 -0500, Joshua Murphy wrote:
> > =x11-wm/awesome-3.1-r1 ~amd64
> >
> > in /etc/portage/package.keywords
> >
> > but 'emerge -uD world' still tries to build x11-wm/awesome-3.1.1
> > which fails, so the whole process is stopped.
>
> echo >x11-wm/awesome-3.1-r1 >> /etc/portage/package.mask
> # and to prevent downgrades
That blocks all future updates, not just the broken one.
--
Neil Bothwick
If there is light at the end of the tunnel...order more tunnel.
01-29-2009, 08:13 AM
Miernik
how to hold a package at a specific version (so emerge -uD world doesn't change it)?
Man Shankar <man.ee.gen@gmail.com> wrote:
> On 20:41 Wed 28 Jan , momesso.andrea@gmail.com wrote:
>>
>> I think that if emerge =x11-wm/awesome-3.1.1 fails, you should file a
>> bug before masking it.
Well, it could take days, weeks, or more before the bug report is taken
care of, and I don't want to wait with my upgrade of the rest of the
system.
> +1
>
> FWIW, have been using that version for about 10 days. Works great here.
> What is the error you get?
I did, read here:
http://bugs.gentoo.org/show_bug.cgi?id=256641
Thanks for anwsers, masking worked.
01-29-2009, 12:53 PM
Neil Bothwick
how to hold a package at a specific version (so emerge -uD world doesn't change it)?
On Thu, 29 Jan 2009 14:19:45 +0100, Sebastian Günther wrote:
> doesn't
>
> emerge --skipfirst
>
> ring any bell?
Or even emerge --keep-going if you want to take that route.
--
Neil Bothwick
CPU: (n.) acronym for Central Purging Unit. A device which discards or
distorts data sent to it, sometimes returning more data and sometimes
merely over-heating.