[gentoo-user] Trouble using package.provided

[gentoo-user] Trouble using package.provided

[allan gottlieb]

I have never needed package.provided before so am probably doing it
wrong.

There are know bugs I am encountering with
www-client/chromium-64.0.3282.140 and
net-libs/webkit-gtk-2.4.11-r200

Since each takes a while to build before failing, I would like to stop
trying until there is progress on the bugs

man 5 portage made me believe that package.provide was the answer.

    E6430 ~ # cat /etc/portage/package.provided/chromium
    # The current version won't build (known problem)
    =www-client/chromium-64.0.3282.140
    E6430 ~ # 

    E6430 ~ # cat /etc/portage/package.provided/webkit-gtk
    # the -r200 won't build (known bug)
    # "soon" won't need it since will have new gnucash
    =net-libs/webkit-gtk-2.4.11-r200
    E6430 ~ # 

However

    E6430 ~ # emerge --update --changed-use --with-bdeps=y @world

begins with

These are the packages that would be merged, in reverse order:

Calculating dependencies... done!
[ebuild  rR    ] net-libs/webkit-gtk-2.4.11-r200 
[ebuild     U  ] www-client/chromium-64.0.3282.140 [63.0.3239.108] USE="-jumbo-build%" 

Any help would be appreciated.

thanks,
allan

Re: [gentoo-user] Trouble using package.provided

[Arve Barsnes]

On 14 February 2018 at 17:44, allan gottlieb <gottlieb@nyu.edu> wrote:
> I have never needed package.provided before so am probably doing it
> wrong.
>
> Any help would be appreciated.

The way I understand it, /etc/portage/ doesn't support that, it should
go in /etc/portage/profile/

Cheers,
Arve

Re: [gentoo-user] Trouble using package.provided

[allan gottlieb]

On Wed, Feb 14 2018, Arve Barsnes wrote:

> On 14 February 2018 at 17:44, allan gottlieb <gottlieb@nyu.edu> wrote:
>> I have never needed package.provided before so am probably doing it
>> wrong.
>>
>> Any help would be appreciated.
>
> The way I understand it, /etc/portage/ doesn't support that, it should
> go in /etc/portage/profile/
>
> Cheers,
> Arve

You are correct thanks.

However now
  emerge --update ... @world
gives a red-letter warning that dependent packages are in package.provided,
which is true.  It then gives three possible remedies.

Rather than facing that msg every emerge and possibly learning too well
to ignore warnings, I adopted the third remedy and removed the
package.provided files.

I will temporarily use a two step emerge --update ... @world

1.  emerge --update --pretend ... @world
2.  emerge -1 ... files suggested by 1 minus the bad chromium and webkit-gtk

thanks again.
allan

Re: [gentoo-user] Trouble using package.provided

[Neil Bothwick]

[-- Attachment #1: Type: text/plain, Size: 629 bytes --]

On Wed, 14 Feb 2018 13:28:28 -0500, allan gottlieb wrote:

> Rather than facing that msg every emerge and possibly learning too well
> to ignore warnings, I adopted the third remedy and removed the
> package.provided files.
> 
> I will temporarily use a two step emerge --update ... @world
> 
> 1.  emerge --update --pretend ... @world
> 2.  emerge -1 ... files suggested by 1 minus the bad chromium and
> webkit-gtk

You could try adding "exclude chromium --exclude webkit-gtk" to
EMERGE_DEFAULT_OPTS.


-- 
Neil Bothwick

You are about to give someone a piece of your mind,
something you can ill afford...

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

[gentoo-user] Re: Trouble using package.provided

[Nikos Chantziaras]

On 14/02/18 18:44, allan gottlieb wrote:
> I have never needed package.provided before so am probably doing it
> wrong.
> 
> There are know bugs I am encountering with
> www-client/chromium-64.0.3282.140 and
> net-libs/webkit-gtk-2.4.11-r200
> 
> Since each takes a while to build before failing, I would like to stop
> trying until there is progress on the bugs
> 
> man 5 portage made me believe that package.provide was the answer.

Why not just mask it? (/etc/portage/package.mask)

Re: [gentoo-user] Trouble using package.provided

[allan gottlieb]

On Wed, Feb 14 2018, Neil Bothwick wrote:

> On Wed, 14 Feb 2018 13:28:28 -0500, allan gottlieb wrote:
>
>> Rather than facing that msg every emerge and possibly learning too well
>> to ignore warnings, I adopted the third remedy and removed the
>> package.provided files.
>> 
>> I will temporarily use a two step emerge --update ... @world
>> 
>> 1.  emerge --update --pretend ... @world
>> 2.  emerge -1 ... files suggested by 1 minus the bad chromium and
>> webkit-gtk
>
> You could try adding "exclude chromium --exclude webkit-gtk" to
> EMERGE_DEFAULT_OPTS.

I tried that a while ago.  The problem is that then portage believe
those packages aren't on my stable system and says that I must merge an
unstable package.

Specifically excluding the buggy (old) version of webkit-gtk, portage
wants me to merge a newish (testing) version of gnucash that uses a
solid new version of webkit-gtk.  I have the new version of webkit-gtk,
but really want to delay installing the testing gnucash.

allan

Re: [gentoo-user] Re: Trouble using package.provided

[allan gottlieb]

On Wed, Feb 14 2018, Nikos Chantziaras wrote:

> On 14/02/18 18:44, allan gottlieb wrote:
>> I have never needed package.provided before so am probably doing it
>> wrong.
>>
>> There are know bugs I am encountering with
>> www-client/chromium-64.0.3282.140 and
>> net-libs/webkit-gtk-2.4.11-r200
>>
>> Since each takes a while to build before failing, I would like to stop
>> trying until there is progress on the bugs
>>
>> man 5 portage made me believe that package.provide was the answer.
>
> Why not just mask it? (/etc/portage/package.mask)

Basically the same problem as --exclude.  Portage wants me to unmask
them because they are needed.  Chromium is in @world and webkit-gtk is
needed for gnucash.

allan