Re: [gentoo-user] slot conflict for media-libs/x264-0.0

2018-06-19 Thread allan gottlieb
On Mon, Jun 18 2018, Mick wrote:

> On Monday, 18 June 2018 21:28:38 BST allan gottlieb wrote:
>> On Mon, Jun 18 2018, Mick wrote:
>> > Hi Allan,
>> > 
>> > On Monday, 18 June 2018 18:52:31 BST allan gottlieb wrote:
>> >> On Sun, Jun 17 2018, Mick wrote:
>> >> > On Sunday, 17 June 2018 22:04:50 BST allan gottlieb wrote:
>> >> >> (I have been offline for a few months and apologize if this has been
>> >> >> covered.)
>> >> >> 
>> >> >> I had not synced for about 3 months (fear of new, incompatible
>> >> >> gnucash)
>> >> >> but have now done so.  Unsurprisingly my normal update world shows
>> >> >> many
>> >> >> entries and also unsurprising is a blocker (slot conflict).
>> > 
>> > As a first step I suggest you go through the 'eselect news read new'.
>> > 
>> > There was a profile change sometime late last year.  The profile change
>> > enews is important and you should deal with it first.  It is titled:
>> > 
>> > 'New 17.0 profiles in the Gentoo repository'
>> > 
>> > and it involves updating gcc as part of it and perhaps changing your
>> > profile if it is due to be deprecated.
>> 
>> I had done the upgrade to 17.0 months ago.
>> 17.1 is unstable so I believe 17.0 is the right profile for me.
>> 
>> > Once you've been through all this give it another spin, but use
>> > --backtrack=99 to see if portage resolves the conflicts.
>> 
>> backtrack=99 didn't change the situation, but adding in addition
>> --autounmask-backtrack=y did!
>
> Interesting!  What did it autounmask?

That is not what the option does.  It just prevents backtracking from
stopping earlier when it finds that config changes are needed.
With the full backtrack=99 all the serious problems were resolved, I
just needed to add a use setting, specifically grub[mount].

>> > I can't see a [B] in the list you provided, all are small blocks [b] which
>> > portage will deal with on its own.
>> 
>> The list I provided was for my update world.  That has little b's.  The
>> only blockage I have is the slot conflict I mentioned originally.  The
>> big B's happened when I tried
>> 
>>emerge -1pDv media-video/ffmpeg
>
> Well, media-libs/x264-0.0.20130506 is no longer in the tree.  media-video/
> ffmpeg-3.3.6 does not require it and works fine with media-libs/
> x264-0.0.20160712.  This is why I suggested that manual removal and update 
> earlier on. 
>
> Unless something else is blocking ffmpeg (you've got a long update list there 
> which might influence it) there shouldn't be a problem with my suggested 
> workaround.  Nevertheless, getting portage to pontificate and resolve the 
> dependency graph is invariably a safer option.  ;-)

By just adding --backtrack=99 --autounmask-backtrack=y
portage was happy (and so am I).

Indeed, considering I hadn't synced for 3 months, I consider myself
lucky and will try to do at least weekly emerge --update @world's

thanks,
allan



Re: [gentoo-user] slot conflict for media-libs/x264-0.0

2018-06-18 Thread Mick
On Monday, 18 June 2018 21:28:38 BST allan gottlieb wrote:
> On Mon, Jun 18 2018, Mick wrote:
> > Hi Allan,
> > 
> > On Monday, 18 June 2018 18:52:31 BST allan gottlieb wrote:
> >> On Sun, Jun 17 2018, Mick wrote:
> >> > On Sunday, 17 June 2018 22:04:50 BST allan gottlieb wrote:
> >> >> (I have been offline for a few months and apologize if this has been
> >> >> covered.)
> >> >> 
> >> >> I had not synced for about 3 months (fear of new, incompatible
> >> >> gnucash)
> >> >> but have now done so.  Unsurprisingly my normal update world shows
> >> >> many
> >> >> entries and also unsurprising is a blocker (slot conflict).
> > 
> > As a first step I suggest you go through the 'eselect news read new'.
> > 
> > There was a profile change sometime late last year.  The profile change
> > enews is important and you should deal with it first.  It is titled:
> > 
> > 'New 17.0 profiles in the Gentoo repository'
> > 
> > and it involves updating gcc as part of it and perhaps changing your
> > profile if it is due to be deprecated.
> 
> I had done the upgrade to 17.0 months ago.
> 17.1 is unstable so I believe 17.0 is the right profile for me.
> 
> > Once you've been through all this give it another spin, but use
> > --backtrack=99 to see if portage resolves the conflicts.
> 
> backtrack=99 didn't change the situation, but adding in addition
> --autounmask-backtrack=y did!

Interesting!  What did it autounmask?


> > I can't see a [B] in the list you provided, all are small blocks [b] which
> > portage will deal with on its own.
> 
> The list I provided was for my update world.  That has little b's.  The
> only blockage I have is the slot conflict I mentioned originally.  The
> big B's happened when I tried
> 
>emerge -1pDv media-video/ffmpeg

Well, media-libs/x264-0.0.20130506 is no longer in the tree.  media-video/
ffmpeg-3.3.6 does not require it and works fine with media-libs/
x264-0.0.20160712.  This is why I suggested that manual removal and update 
earlier on. 

Unless something else is blocking ffmpeg (you've got a long update list there 
which might influence it) there shouldn't be a problem with my suggested 
workaround.  Nevertheless, getting portage to pontificate and resolve the 
dependency graph is invariably a safer option.  ;-)

-- 
Regards,
Mick

signature.asc
Description: This is a digitally signed message part.


Re: [gentoo-user] slot conflict for media-libs/x264-0.0

2018-06-18 Thread allan gottlieb
On Mon, Jun 18 2018, Mick wrote:

> Hi Allan,
>
> On Monday, 18 June 2018 18:52:31 BST allan gottlieb wrote:
>> On Sun, Jun 17 2018, Mick wrote:
>> > On Sunday, 17 June 2018 22:04:50 BST allan gottlieb wrote:
>> >> (I have been offline for a few months and apologize if this has been
>> >> covered.)
>> >> 
>> >> I had not synced for about 3 months (fear of new, incompatible gnucash)
>> >> but have now done so.  Unsurprisingly my normal update world shows many
>> >> entries and also unsurprising is a blocker (slot conflict).  
>
> As a first step I suggest you go through the 'eselect news read new'.
>
> There was a profile change sometime late last year.  The profile change enews 
> is important and you should deal with it first.  It is titled:
>
> 'New 17.0 profiles in the Gentoo repository'
>
> and it involves updating gcc as part of it and perhaps changing your profile 
> if it is due to be deprecated.

I had done the upgrade to 17.0 months ago.
17.1 is unstable so I believe 17.0 is the right profile for me.

> Once you've been through all this give it another spin, but use 
> --backtrack=99 
> to see if portage resolves the conflicts.

backtrack=99 didn't change the situation, but adding in addition
--autounmask-backtrack=y did!

> I can't see a [B] in the list you provided, all are small blocks [b] which 
> portage will deal with on its own.

The list I provided was for my update world.  That has little b's.  The
only blockage I have is the slot conflict I mentioned originally.  The
big B's happened when I tried

   emerge -1pDv media-video/ffmpeg

Thank you again.
allan



Re: [gentoo-user] slot conflict for media-libs/x264-0.0

2018-06-18 Thread Mick
Hi Allan,

On Monday, 18 June 2018 18:52:31 BST allan gottlieb wrote:
> On Sun, Jun 17 2018, Mick wrote:
> > On Sunday, 17 June 2018 22:04:50 BST allan gottlieb wrote:
> >> (I have been offline for a few months and apologize if this has been
> >> covered.)
> >> 
> >> I had not synced for about 3 months (fear of new, incompatible gnucash)
> >> but have now done so.  Unsurprisingly my normal update world shows many
> >> entries and also unsurprising is a blocker (slot conflict).  

As a first step I suggest you go through the 'eselect news read new'.

There was a profile change sometime late last year.  The profile change enews 
is important and you should deal with it first.  It is titled:

'New 17.0 profiles in the Gentoo repository'

and it involves updating gcc as part of it and perhaps changing your profile 
if it is due to be deprecated.

Once you've been through all this give it another spin, but use --backtrack=99 
to see if portage resolves the conflicts.


If it still doesn't, then try updating 10 packages at a time and see if the 
problem goes away.

I can't see a [B] in the list you provided, all are small blocks [b] which 
portage will deal with on its own.

-- 
Regards,
Mick

signature.asc
Description: This is a digitally signed message part.


Re: [gentoo-user] slot conflict for media-libs/x264-0.0

2018-06-18 Thread allan gottlieb
On Sun, Jun 17 2018, Mick wrote:

> On Sunday, 17 June 2018 22:04:50 BST allan gottlieb wrote:
>> (I have been offline for a few months and apologize if this has been
>> covered.)
>> 
>> I had not synced for about 3 months (fear of new, incompatible gnucash)
>> but have now done so.  Unsurprisingly my normal update world shows many
>> entries and also unsurprising is a blocker (slot conflict).  However, I
>> am confused by the message which reads
>> 
>> !!! Multiple package instances within a single package slot have been pulled
>> !!! into the dependency graph, resulting in a slot conflict:
>> 
>>   media-libs/x264:0
>> 
>> (media-libs/x264-0.0.20170701:0/152::gentoo, ebuild scheduled for merge)
>> pulled in by (no parents that aren't satisfied by other packages in this
>> slot)
>> 
>> (media-libs/x264-0.0.20160712:0/148::gentoo, installed) pulled in by
>> 
>>   >=media-libs/x264-0.0.20130506:0/148=[abi_x86_64(-)]
>> 
>>   required by (media-video/ffmpeg-3.3.6:0/55.57.57::gentoo, installed)
>> 
>> Why is this a conflict since the first one 0/152 seems to permit other
>> solutions.  Is the (unstated) point that the second one 0/148 is not one
>> of the acceptable "other packages in this slot".
>> 
>> Also I seem some advice.  Should I be first working on this blockage.
>> Or should I instead try to deal with some of the easy updates.
>> 
>> thanks in advance,
>> allan
>
> Since you have the latest ffmpeg installed, this is how I would go about this:
>
> emerge --depclean -a -v media-libs/x264
> emerge -1aDv '=media-libs/x264-0.0.20170701'
> emerge -1aDv media-video/ffmpeg

It is apparently more complicated than I expected (at the end of this
msg I give the *long* full output of my update world).

1.  emerge --depclean -a -v media-libs/x264 will not remove x264
since it is used by ffmpeg and mplayer

2.  emerge --depclean -a -v media-libs/x264 shows many blocks (capital
B).  My attempt at a full update world had the blocks, but with
a lower case b)

3.  emerge -1aDv media-video/ffmpeg also has many capital B blocks.

It seems clear that I erred in not giving the original output.
It is almost 50KB so, in addition to appending it to this msg,
I have put it on my website https://cs.nyu.edu/~gottlieb/E6430

Thank you,
allan


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

Calculating dependencies  . . done!
[nomerge   ] gnome-base/gnome-3.24.2 
[nomerge   ]  gnome-base/gnome-extra-apps-3.24.2 
[nomerge   ]   gnome-extra/gnome-user-share-3.18.3 
[nomerge   ]www-apache/mod_dnssd-0.6-r1 
[ebuild U  ] net-dns/avahi-0.7-r1 [0.7] USE="qt5%*" 
[nomerge   ] net-print/hplip-3.17.10 
[ebuild U  ]  media-gfx/sane-backends-1.0.27-r1 [1.0.27]
[ebuild U  ] www-client/firefox-52.8.0 [52.6.0]
[ebuild U  ] www-client/chromium-67.0.3396.62 [64.0.3282.167] 
USE="(-system-ffmpeg*)" 
[ebuild U  ] app-portage/elogviewer-2.7-r2 [2.7]
[ebuild U  ] x11-base/xorg-x11-7.4-r3 [7.4-r2] USE="fonts%*" 
[ebuild U  ] app-office/libreoffice-6.0.3.2 [5.4.5.1] USE="-gtk2%" 
[nomerge   ] gnome-extra/gnome-shell-extensions-3.24.3 
[nomerge   ]  app-eselect/eselect-gnome-shell-extensions-20180306 [20120911]
[nomerge   ]   gnome-base/gnome-shell-3.24.3 
[nomerge   ]gnome-extra/nm-applet-1.8.10-r1 [1.8.6] USE="gcr*" 
[nomerge   ] net-misc/networkmanager-1.8.4 
[ebuild U  ]  net-wireless/wpa_supplicant-2.6-r6 [2.6-r3] 
USE="-eapol_test% -privsep%" 
[nomerge   ] x11-drivers/xf86-input-synaptics-1.9.1 [1.9.0]
[nomerge   ]  x11-base/xorg-server-1.19.5-r2 [1.19.5] USE="-kdrive*" 
[nomerge   ]   x11-base/xorg-drivers-1.19 
[ebuild U  ]x11-drivers/xf86-input-evdev-2.10.6 [2.10.5]
[ebuild U  ]x11-drivers/xf86-video-intel-2.99.917_p20180214-r1 
[2.99.917_p20170313]
[ebuild U  ]x11-drivers/xf86-input-synaptics-1.9.1 [1.9.0]
[nomerge   ] www-client/firefox-52.8.0 [52.6.0]
[nomerge   ]  virtual/ffmpeg-9-r2 
[nomerge   ]   media-video/ffmpeg-3.3.6 
[ebuild U  ]media-libs/libsdl2-2.0.8-r1 [2.0.4] USE="(-aqua) 
-libsamplerate%" 
[ebuild U  ] app-editors/emacs-25.3-r4 [25.3-r1]
[nomerge   ] gnome-base/gnome-extra-apps-3.24.2 
[nomerge   ]  gnome-extra/gnome-tweak-tool-3.24.1 
[nomerge   ]   gnome-base/gnome-shell-3.24.3 
[ebuild U  ]gnome-base/gnome-control-center-3.24.4 [3.24.3]
[nomerge   ] gnome-base/gnome-extra-apps-3.24.2 
[nomerge   ]  media-sound/sound-juicer-3.24.0 
[nomerge   ]   app-cdr/brasero-3.12.2-r1 
[ebuild U  ]gnome-base/gvfs-1.32.2 [1.32.1-r1]
[ebuild U  ] sys-process/procps-3.3.15-r1 [3.3.12-r1]
[nomerge   ] net-print/hplip-3.17.10 
[ebuild U  ]  dev-python/PyQt5-5.9.2 [5.7.1]
[ebuild U  ]   dev-qt/qtbluetooth-5.9.4 [5.7.1]
[ebuild U  ]dev-qt/qtconcurrent-5.9.4 [5.7.1]
[ebuild U  ]   dev-qt/qtprintsupport-5.9.4 [5.7.1]
[ebuild U  ]   dev-qt/qtopengl-5.9.4 [5.7.1]
[ebuild U  ] 

Re: [gentoo-user] slot conflict for media-libs/x264-0.0

2018-06-17 Thread Mick
On Sunday, 17 June 2018 22:04:50 BST allan gottlieb wrote:
> (I have been offline for a few months and apologize if this has been
> covered.)
> 
> I had not synced for about 3 months (fear of new, incompatible gnucash)
> but have now done so.  Unsurprisingly my normal update world shows many
> entries and also unsurprising is a blocker (slot conflict).  However, I
> am confused by the message which reads
> 
> !!! Multiple package instances within a single package slot have been pulled
> !!! into the dependency graph, resulting in a slot conflict:
> 
>   media-libs/x264:0
> 
> (media-libs/x264-0.0.20170701:0/152::gentoo, ebuild scheduled for merge)
> pulled in by (no parents that aren't satisfied by other packages in this
> slot)
> 
> (media-libs/x264-0.0.20160712:0/148::gentoo, installed) pulled in by
> 
>   >=media-libs/x264-0.0.20130506:0/148=[abi_x86_64(-)]
> 
>   required by (media-video/ffmpeg-3.3.6:0/55.57.57::gentoo, installed)
> 
> Why is this a conflict since the first one 0/152 seems to permit other
> solutions.  Is the (unstated) point that the second one 0/148 is not one
> of the acceptable "other packages in this slot".
> 
> Also I seem some advice.  Should I be first working on this blockage.
> Or should I instead try to deal with some of the easy updates.
> 
> thanks in advance,
> allan

Since you have the latest ffmpeg installed, this is how I would go about this:

emerge --depclean -a -v media-libs/x264
emerge -1aDv '=media-libs/x264-0.0.20170701'
emerge -1aDv media-video/ffmpeg
-- 
Regards,
Mick

signature.asc
Description: This is a digitally signed message part.


[gentoo-user] slot conflict for media-libs/x264-0.0

2018-06-17 Thread allan gottlieb
(I have been offline for a few months and apologize if this has been
covered.)

I had not synced for about 3 months (fear of new, incompatible gnucash)
but have now done so.  Unsurprisingly my normal update world shows many
entries and also unsurprising is a blocker (slot conflict).  However, I
am confused by the message which reads

!!! Multiple package instances within a single package slot have been pulled
!!! into the dependency graph, resulting in a slot conflict:

  media-libs/x264:0
  
(media-libs/x264-0.0.20170701:0/152::gentoo, ebuild scheduled for merge) 
pulled in by
  (no parents that aren't satisfied by other packages in this slot)
  
(media-libs/x264-0.0.20160712:0/148::gentoo, installed) pulled in by
  >=media-libs/x264-0.0.20130506:0/148=[abi_x86_64(-)]
  required by (media-video/ffmpeg-3.3.6:0/55.57.57::gentoo, installed)

Why is this a conflict since the first one 0/152 seems to permit other
solutions.  Is the (unstated) point that the second one 0/148 is not one
of the acceptable "other packages in this slot".

Also I seem some advice.  Should I be first working on this blockage.
Or should I instead try to deal with some of the easy updates.

thanks in advance,
allan