Re: [gentoo-user] update problems
On Sat, Sep 19, 2015 at 3:57 PM, Alan McKinnon <alan.mckin...@gmail.com> wrote: > On 19/09/2015 21:36, lee wrote: >> >> dev-libs/boost:0 >> >> (dev-libs/boost-1.56.0-r1:0/1.56.0::gentoo, ebuild scheduled for merge) >> pulled in by >> (no parents that aren't satisfied by other packages in this slot) >> >> (dev-libs/boost-1.55.0-r2:0/1.55.0::gentoo, ebuild scheduled for merge) >> pulled in by >> dev-libs/boost:0/1.55.0= required by >> (dev-libs/librevenge-0.0.2:0/0::gentoo, installed) >> ^^ >> (and 2 more with the same problem) > > I'm not sure why you are getting this one. Portage is only pulling in > boost-1.56.0-r1 because it's the latest stable version, but librevenge > requires something earlier. Portage should therefore shut up and install > the only real solution - keep boost at 1.55.0 > librevenge doesn't require an earlier version. This is either a result of insufficient backtracking, or it might have to do with how portage stores runtime dependencies for installed packages. Try adding --backtrack=50 to your command line and try again. If nothing else it might simplify the output. It will take longer to run. If it is the rdepend issue then you can probably emerge -1 librevenge and whatever else is depending on the old version to fix it. Also, emerge running --changed-deps=y from time to time may make those kinds of problems less likely. The first time you do it prepare to see a LOT of stuff get rebuilt - any of those packages could cause issues in the future but most probably will not. > You fail to understand how gentoo works. At no time did Gentoo ever > guarantee that updates would work like binary distros and the process > would be trouble free. Quite the opposite - Gentoo is upfront in telling > you that there will always be update issues and you are the person to > solve them. > While Gentoo doesn't do as much handholding as many distros, the portage output above should not be viewed as something we are proud of. --backtrack fixes a lot of issues, and there aren't a lot of simple solutions for that without slowing down emerge. On the other hand, a lot of the runtime dependency issues could be fixed. There is a discussion on -dev right now about getting rid of dynamic runtime deps, which would probably help cut down on some of the more bizarre behavior. -- Rich
Re: [gentoo-user] update problems
On Sat, Sep 26, 2015 at 9:51 AM, lee <l...@yagibdah.de> wrote: > | > | (dev-libs/boost-1.56.0-r1:0/1.56.0::gentoo, ebuild scheduled for merge) > pulled in by > | (no parents that aren't satisfied by other packages in this slot) > | > | (dev-libs/boost-1.55.0-r2:0/1.55.0::gentoo, ebuild scheduled for merge) > pulled in by > | dev-libs/boost:0/1.55.0= required by > (dev-libs/librevenge-0.0.2:0/0::gentoo, installed) > | ^^ > | (and 2 more with the same problem) > | >> (I wrote the below) >> that doesn't work just try running emerge -1 on the packages that are >> causing the block by depending on the older package version? > > I suppose the newer versions of the packages are the ones that are > causing the blocks. You could argue that other versions of packages are > causing the blocks, but I would argue that there weren't any blocks > before the newer versions of the packages were available, hence the > newer versions obviously cause the blocks. That is to say that I'm > unsure which packages you're referring to as those causing the blocks. Apologies if it was a bit unclear. In this example, I'd run emerge -1 =dev-libs/librevenge-0.0.2 You also need to run it on the "2 more with the same problem" but we don't know what those are. Adding --verbose might help. It should be safe to run emerge -1 on anything you already have installed. If this is a dynamic deps issue then emerge -1 pkg will probably help. Either way, after trying that can you post the output of this: emerge -j 8 -p --update --newuse --deep --with-bdeps=y --backtrack=500 --verbose --tree @world That will show you what is pulling in updates to what. I'm interested in the entire output of emerge, not just the parts you think are most relevant - feel free to attach a file containing it. -- Rich
Re: [gentoo-user] update problems
Rich Freeman <ri...@gentoo.org> writes: > On Sat, Sep 26, 2015 at 9:51 AM, lee <l...@yagibdah.de> wrote: >> | >> | (dev-libs/boost-1.56.0-r1:0/1.56.0::gentoo, ebuild scheduled for merge) >> pulled in by >> | (no parents that aren't satisfied by other packages in this slot) >> | >> | (dev-libs/boost-1.55.0-r2:0/1.55.0::gentoo, ebuild scheduled for merge) >> pulled in by >> | dev-libs/boost:0/1.55.0= required by >> (dev-libs/librevenge-0.0.2:0/0::gentoo, installed) >> | ^^ >> | (and 2 more with the same problem) >> | >>> (I wrote the below) >>> that doesn't work just try running emerge -1 on the packages that are >>> causing the block by depending on the older package version? >> >> I suppose the newer versions of the packages are the ones that are >> causing the blocks. You could argue that other versions of packages are >> causing the blocks, but I would argue that there weren't any blocks >> before the newer versions of the packages were available, hence the >> newer versions obviously cause the blocks. That is to say that I'm >> unsure which packages you're referring to as those causing the blocks. > > Apologies if it was a bit unclear. np :) > In this example, I'd run emerge -1 =dev-libs/librevenge-0.0.2 > > You also need to run it on the "2 more with the same problem" but we > don't know what those are. Adding --verbose might help. It should be > safe to run emerge -1 on anything you already have installed. If this > is a dynamic deps issue then emerge -1 pkg will probably help. > > Either way, after trying that can you post the output of this: > > emerge -j 8 -p --update --newuse --deep --with-bdeps=y --backtrack=500 > --verbose --tree @world > > That will show you what is pulling in updates to what. I'm interested > in the entire output of emerge, not just the parts you think are most > relevant - feel free to attach a file containing it. Well, what I did was basically: emerge -a --changed-deps=y @world emerge -j 8 -a --update --newuse --deep --with-bdeps=y --backtrack=100 @world [fix USE flag] emerge -j 8 -a --update --newuse --deep --with-bdeps=y --backtrack=100 @world [remove nvidia-settings] emerge -j 8 -a --update --newuse --deep --with-bdeps=y --backtrack=100 @world emerge @preserved-rebuild That took about 2 hours to update 233 packages. Then I made the new kernel and found that for unknown reasons, without warning, the zfs startup scripts were disabled (very bad idea ...). Today I updated the LXC guest and went over the kernel settings and managed to get my trackball not to work anymore, then took quite a while to figure out what was missing (it needs a HID driver which, for unknown reasons, got disabled ...). So after two days, I finally got seamonkey 2.35 (and a cleaned-up kernel) ... and I wonder why libreoffice hasn't been updated. Not that it matters, but why not? -- Again we must be afraid of speaking of daemons for fear that daemons might swallow us. Finally, this fear has become reasonable.
Re: [gentoo-user] update problems
Rich Freeman <ri...@gentoo.org> writes:
> On Sat, Sep 19, 2015 at 3:57 PM, Alan McKinnon <alan.mckin...@gmail.com>
> wrote:
>> On 19/09/2015 21:36, lee wrote:
>>>
>>> dev-libs/boost:0
>>>
>>> (dev-libs/boost-1.56.0-r1:0/1.56.0::gentoo, ebuild scheduled for merge)
>>> pulled in by
>>> (no parents that aren't satisfied by other packages in this slot)
>>>
>>> (dev-libs/boost-1.55.0-r2:0/1.55.0::gentoo, ebuild scheduled for merge)
>>> pulled in by
>>> dev-libs/boost:0/1.55.0= required by
>>> (dev-libs/librevenge-0.0.2:0/0::gentoo, installed)
>>> ^^
>>> (and 2 more with the same problem)
>>
>> I'm not sure why you are getting this one. Portage is only pulling in
>> boost-1.56.0-r1 because it's the latest stable version, but librevenge
>> requires something earlier. Portage should therefore shut up and install
>> the only real solution - keep boost at 1.55.0
>>
>
> librevenge doesn't require an earlier version. This is either a
> result of insufficient backtracking, or it might have to do with how
> portage stores runtime dependencies for installed packages.
>
> Try adding --backtrack=50 to your command line and try again. If
> nothing else it might simplify the output. It will take longer to
> run.
It gives the same results (after syncing again), plus a message that
wasn't there before:
,
| x11-drivers/nvidia-drivers:0
|
| (x11-drivers/nvidia-drivers-355.11:0/0::gentoo, ebuild scheduled for merge)
pulled in by
| (no parents that aren't satisfied by other packages in this slot)
|
| (x11-drivers/nvidia-drivers-340.93:0/0::gentoo, ebuild scheduled for merge)
pulled in by
| ~x11-drivers/nvidia-drivers-340.93 required by
(media-video/nvidia-settings-340.58:0/0::gentoo, ebuild scheduled for merge)
| ^ ^^
`
This looks kinda weird because I expect those drivers to be updated as
well, and if they aren't, I will have to remove nvidia-settings.
Let's try backtrack 500 ... same result, and doesn't take longer.
> If it is the rdepend issue then you can probably emerge -1 librevenge
> and whatever else is depending on the old version to fix it.
>
> Also, emerge running --changed-deps=y from time to time may make those
> kinds of problems less likely. The first time you do it prepare to
> see a LOT of stuff get rebuilt - any of those packages could cause
> issues in the future but most probably will not.
Good to know, I'll keep that in mind. I tried it and it's not too much
to rebuild, only a bit surprising:
,
| [ebuild U ] sys-devel/automake-wrapper-10 [9]
| [ebuild R] app-benchmarks/i7z-0.27.2
| [ebuild R] net-misc/netkit-telnetd-0.17-r10
| [ebuild R] virtual/editor-0
| [ebuild U ] sys-devel/gcc-4.8.5 [4.8.4] USE="-debug%"
| [ebuild R] net-dialup/ppp-2.4.7
| [ebuild U ] sys-apps/openrc-0.17 [0.13.11] USE="-audit%"
| [ebuild R] x11-terms/xterm-314
| [ebuild U ] net-firewall/shorewall-4.6.10.1 [4.6.6.2]
| [ebuild NS] sys-devel/automake-1.15 [1.11.6-r1, 1.13.4]
| [ebuild U ] media-libs/alsa-lib-1.0.29 [1.0.28]
| [ebuild U ] media-sound/alsa-utils-1.0.29 [1.0.28]
| [ebuild U ] sys-apps/portage-2.2.20.1 [2.2.18]
PYTHON_TARGETS="python3_4* -python3_3*"
| [ebuild R] app-portage/gentoolkit-0.3.0.9-r2
PYTHON_TARGETS="python3_4* -python3_3*"
| [ebuild U ] dev-python/ssl-fetch-0.3 [0.2] PYTHON_TARGETS="python3_4*
-python3_3*"
| [ebuild U ] app-portage/mirrorselect-2.2.2-r2 [2.2.2]
PYTHON_TARGETS="python3_4* -python3_3*"
| [ebuild U ] media-gfx/gimp-2.8.14-r1 [2.8.14] USE="{-test%}"
| [ebuild U ] media-video/mplayer-1.2_pre20150214-r1 [1.2_pre20130729]
| [ebuild R ~] media-video/openshot-1.4.3 USE="-libav%"
| [ebuild U ] app-editors/emacs-24.5 [24.4-r4]
`
Should I do that before updating or after? I guess I'm on the save side
doing it before, so I'll do that.
>> You fail to understand how gentoo works. At no time did Gentoo ever
>> guarantee that updates would work like binary distros and the process
>> would be trouble free. Quite the opposite - Gentoo is upfront in telling
>> you that there will always be update issues and you are the person to
>> solve them.
>>
>
> While Gentoo doesn't do as much handholding as many distros, the
> portage output above should not be viewed as something we are proud
> of.
At least I'm learning here :)
> --backtrack fixes a lot of issues, and there aren't a lot of simple
> solutions for that without slowing down emerge.
>
> On the other hand, a lot of the runtime dependency issues coul
Re: [gentoo-user] GCC 10.1 SUCKS.
On Thu, 14 May 2020 11:15:59 -0400 Alan Grimes wrote: > KDE really can't update itself, I really had to flog the living bleep > out of it to get it, and a lot of other stuff to settle down... > > The configure phases for most of these packages are so monsterously > inefficient that I have to run dozens of builds concurently to get CPU > utilization out of the single digits... Okay, I have a high-end > processor rn but it's crazy watching the actual compile stages of > various packages only blip the histogram for a fraction of a second... > > Here are some highlights from the fails that I consider "hard fails": > > Dependency of libreoffice: Libetonyek > > > -I/usr/include/libxml2 -DNDEBUG -DLIBETONYEK_VISIBILITY > -fvisibility=hidden -march=native -pipe -O3 -Wall -Wextra -Wshadow > -pedantic -Weffc++ -c -o > contexts/libetonyek_internal_la-IWORKLayoutElement.lo `test -f > 'contexts/IWORKLayoutElement.cpp' || echo './'`context > s/IWORKLayoutElement.cpp > /bin/sh ../../libtool --tag=CXX --mode=compile > x86_64-pc-linux-gnu-g++ -DHAVE_CONFIG_H -I. -I../.. > -DBOOST_SPIRIT_USE_PHOENIX_V3 -DLIBETONYEK_BUILD -I../../inc > -I../../src/lib/contexts -I/usr/include/libxml2 > -I/usr/include/mdds-1.5 -I/usr/include/librevenge-0.0 > -I/usr/include/libxml2 -DNDEBUG -DLIBETONYEK_VISIBILITY > -fvisibility=hidden -march=native -pipe -O3 -Wall -Wextra -Wshadow > -pedantic -Weffc++ -c -o > contexts/libetonyek_internal_la-IWORKLineElement.lo `test -f > 'contexts/IWORKLineElement.cpp' || echo './'`contexts/IW > ORKLineElement.cpp > NUM3Parser.cpp: In member function ‘virtual bool > libetonyek::NUM3Parser::parseDocument()’: > NUM3Parser.cpp:46:8: error: ‘for_each’ is not a member of ‘std’ > 46 | std::for_each(sheetListRefs.begin(), sheetListRefs.end(), > std::bind(::parseSheet, this, std::placeholders::_1)); > | ^~~~ Please file bugs to bugs.gentoo.org and maintainer should help you. In this case it looks like a https://bugs.gentoo.org/722042 which was a boost update. -- Sergei
Re: [gentoo-user] update problems
Alan McKinnon <alan.mckin...@gmail.com> writes: > On 19/09/2015 21:36, lee wrote: >> Hi, >> >> how could I solve these updating problems: >> >> >> emerge -j 8 -a --update --newuse --deep --with-bdeps=y @world >> >> >> >> * IMPORTANT: 4 news items need reading for repository 'gentoo'. >> * Use eselect news read to view new items. >> >> >> These are the packages that would be merged, in order: >> >> Calculating dependencies... done! >> >> !!! Multiple package instances within a single package slot have been pulled >> !!! into the dependency graph, resulting in a slot conflict: >> >> dev-libs/boost:0 >> >> (dev-libs/boost-1.56.0-r1:0/1.56.0::gentoo, ebuild scheduled for merge) >> pulled in by >> (no parents that aren't satisfied by other packages in this slot) >> >> (dev-libs/boost-1.55.0-r2:0/1.55.0::gentoo, ebuild scheduled for merge) >> pulled in by >> dev-libs/boost:0/1.55.0= required by >> (dev-libs/librevenge-0.0.2:0/0::gentoo, installed) >> ^^ >> >> (and 2 more with the same problem) > > I'm not sure why you are getting this one. Portage is only pulling in > boost-1.56.0-r1 because it's the latest stable version, but librevenge > requires something earlier. Portage should therefore shut up and install > the only real solution - keep boost at 1.55.0 Maybe because it says that there's a slot conflict. I had another one of those, and getting rid of it prevents me from having a pdf reader installed. I haven't had the need to read a pdf since, but sooner or later I'll need to be able to. > Try these possibilities: > > emerge =dev-libs/boost-1.55.0-r2 Why this particular version; how did you figure that out? I read from the second message that boost doesn't work with itself because librevenge is installed. So I could remove librevenge, but a lot of things depend on it, amongst them libreoffice. >From there, I don't know what the effects are. Now libreoffice is still 4.4.1.2, and I would expect it being upgraded to 5.x maybe. So I would have to remove boost instead --- IIRC I installed it only to try out regex_match() and regex_search() --- but removing boost seems a bit unreasonable, considering that it takes a while to build. And even with boost removed, I have no good reason to think that there won't be other problems, and it leaves the question what to do when I need boost again: I don't even have a pdf reader ... So I decided I'd better ask what to do. It's hard to believe that we are seriously expected to remove lots of software which we might not be able to install again just to do an update. All these conflicts give me the impression that something in the repo is broken and needs to be fixed. > emerge -avuND world > > or > > emerge -j 8 -a --update --newuse --deep --with-bdeps=n @world > > or quickpkg boost, then unmerge it and re-run emerge world. > Boost is a pain to build so with a quickpkg you can put it back with a > minimum of effort Maybe next weekend or so, I don't feel like doing it now and don't really have the time to. >> dev-util/boost-build:0 >> >> (dev-util/boost-build-1.55.0:0/0::gentoo, installed) pulled in by >> =dev-util/boost-build-1.55* required by >> (dev-libs/boost-1.55.0-r2:0/1.55.0::gentoo, ebuild scheduled for merge) >> ^ ^ >> >> >> >> (dev-util/boost-build-1.56.0:0/0::gentoo, ebuild scheduled for merge) >> pulled in by >> =dev-util/boost-build-1.56* required by >> (dev-libs/boost-1.56.0-r1:0/1.56.0::gentoo, ebuild scheduled for merge) >> ^ ^ >> >> > > This is a consequence of boost. > Fix the boost issue and this one goes away I thought it might. It's yet another message telling me that boost doesn't work with boost. >> media-video/ffmpeg:0 >> >> (media-video/ffmpeg-2.6.3:0/54.56.56::gentoo, ebuild scheduled for merge) >> pulled in by >> (no parents that aren't satisfied by other packages in this slot) >> >> (media-video/ffmpeg-2.2.14:0/52.55.55::gentoo, installed) pulled in by
Re: [gentoo-user] update problems
On Saturday 19 Sep 2015 21:05:27 Neil Bothwick wrote: > On Sat, 19 Sep 2015 21:36:06 +0200, lee wrote: > > emerge -j 8 -a --update --newuse --deep --with-bdeps=y > > @world > > > > * IMPORTANT: 4 news items need reading for repository 'gentoo'. > > * Use eselect news read to view new items. > > > > These are the packages that would be merged, in order: > > > > Calculating dependencies... done! > > > > !!! Multiple package instances within a single package slot have been > > pulled !!! into the dependency graph, resulting in a slot conflict: > > > > dev-libs/boost:0 > > > > (dev-libs/boost-1.56.0-r1:0/1.56.0::gentoo, ebuild scheduled for > > > > merge) pulled in by (no parents that aren't satisfied by other packages > > in this slot) > > > > (dev-libs/boost-1.55.0-r2:0/1.55.0::gentoo, ebuild scheduled for > > > > merge) pulled in by dev-libs/boost:0/1.55.0= required by > > (dev-libs/librevenge-0.0.2:0/0::gentoo, installed) > > ^^ (and 2 more with the same problem) > > > > dev-util/boost-build:0 > > > > (dev-util/boost-build-1.55.0:0/0::gentoo, installed) pulled in by > > > > =dev-util/boost-build-1.55* required by > > > > (dev-libs/boost-1.55.0-r2:0/1.55.0::gentoo, ebuild scheduled for merge) > > ^ > > ^ > > > > (dev-util/boost-build-1.56.0:0/0::gentoo, ebuild scheduled for merge) > > > > pulled in by =dev-util/boost-build-1.56* required by > > (dev-libs/boost-1.56.0-r1:0/1.56.0::gentoo, ebuild scheduled for merge) > > ^ > > ^ > > > > media-video/ffmpeg:0 > > > > (media-video/ffmpeg-2.6.3:0/54.56.56::gentoo, ebuild scheduled for > > > > merge) pulled in by (no parents that aren't satisfied by other packages > > in this slot) > > > > (media-video/ffmpeg-2.2.14:0/52.55.55::gentoo, installed) pulled in by > > > > media-video/ffmpeg:0/52.55.55=[vdpau] required by > > > > (media-libs/mlt-0.9.0:0/0::gentoo, installed) > > ^^^ > > These are unimportant, it is simply portage telling you it is not > updating some packages to the latest available and why. Personally, I > believe this sort of output should only be shown when using --verbose. > > > It may be possible to solve this problem by using package.mask to > > prevent one of those packages from being selected. However, it is also > > possible that conflicting dependencies exist such that they are > > impossible to satisfy simultaneously. If such a conflict exists in > > the dependencies of two different packages, then those packages can > > not be installed simultaneously. > > > > For more information, see MASKED PACKAGES section in the emerge man > > page or refer to the Gentoo Handbook. > > > > > > !!! The ebuild selected to satisfy "sci-libs/hdf5" has unmet > > requirements. > > - sci-libs/hdf5-1.8.14-r1::gentoo USE="cxx fortran threads zlib -debug > > -examples -fortran2003 -mpi -static-libs -szip" > > > > The following REQUIRED_USE flag constraints are unsatisfied: > > threads? ( !cxx !fortran ) > > This is blocking you and the reason is given, if you have the threads > flag on, cxx and fortran must be off. You have both threads and cxx on > which won't work. > > > Why can't we just update like we can with any other distribution but > > have to run into dependency problems all the time instead? > > These aren't dependency problems, they are conflicting USE flags, a > situation that cannot arise with a binary distro. If you want the > flexibility that USE flags offer, you have to accept that not all > combinations will work together. > > > What do I do when I need to update /right now/ and find myself being > > blocked with cryptic messages like the above that leave me stranded? > > That's the real problem, that the messages are so cryptic. The solution > is simple, working out what needs to be done from the messages is not. > > > Once I used 'emerge --sync', there is no way to turn it back to continue > > to be able to install software if needed when the update cannot be > > performed. Updates simply need to work, there's no way around that. > > You can always roll back by masking the updates if necessary, and the > old ebuilds are always available. Now that the tree is using git, it is > probably possibly to sync back to yesterday if you need to. As Alan said quickpkg boost, remove boost-1.55.0-r2, install boost-1.56.0-r1, emerge -1aDv dev-libs/librevenge and which-ever other package complains and you should be OK. Apply a similar approach with ffmpeg. Neil's comments on sci-libs/hdf5 stand. -- Regards, Mick signature.asc Description: This is a digitally signed message part.
Re: [gentoo-user] update problems
On 26/09/2015 11:47, lee wrote: > Rich Freeman <ri...@gentoo.org> writes: > >> On Sat, Sep 19, 2015 at 3:57 PM, Alan McKinnon <alan.mckin...@gmail.com> >> wrote: >>> On 19/09/2015 21:36, lee wrote: >>>> >>>> dev-libs/boost:0 >>>> >>>> (dev-libs/boost-1.56.0-r1:0/1.56.0::gentoo, ebuild scheduled for merge) >>>> pulled in by >>>> (no parents that aren't satisfied by other packages in this slot) >>>> >>>> (dev-libs/boost-1.55.0-r2:0/1.55.0::gentoo, ebuild scheduled for merge) >>>> pulled in by >>>> dev-libs/boost:0/1.55.0= required by >>>> (dev-libs/librevenge-0.0.2:0/0::gentoo, installed) >>>> ^^ >>>> (and 2 more with the same problem) >>> >>> I'm not sure why you are getting this one. Portage is only pulling in >>> boost-1.56.0-r1 because it's the latest stable version, but librevenge >>> requires something earlier. Portage should therefore shut up and install >>> the only real solution - keep boost at 1.55.0 >>> >> >> librevenge doesn't require an earlier version. This is either a >> result of insufficient backtracking, or it might have to do with how >> portage stores runtime dependencies for installed packages. >> >> Try adding --backtrack=50 to your command line and try again. If >> nothing else it might simplify the output. It will take longer to >> run. > > It gives the same results (after syncing again), plus a message that > wasn't there before: > > > , > | x11-drivers/nvidia-drivers:0 > | > | (x11-drivers/nvidia-drivers-355.11:0/0::gentoo, ebuild scheduled for > merge) pulled in by > | (no parents that aren't satisfied by other packages in this slot) > | > | (x11-drivers/nvidia-drivers-340.93:0/0::gentoo, ebuild scheduled for > merge) pulled in by > | ~x11-drivers/nvidia-drivers-340.93 required by > (media-video/nvidia-settings-340.58:0/0::gentoo, ebuild scheduled for merge) > | ^ ^^ > ` > > > This looks kinda weird because I expect those drivers to be updated as > well, and if they aren't, I will have to remove nvidia-settings. > > Let's try backtrack 500 ... same result, and doesn't take longer. That doesn't look like a block. It looks like an info message that portage is "helpfully" displaying (but really belongs only in -v output. Maybe even the non-existent -vvv...) Portage is telling you *why* it is not updating to latest stable nvidia-drivers even though a higher version is in the tree. It's because nvidia-settings is out of step with nvidia-drivers. Look at output of "eix nvidia": nvidia-drivers-355.11 is stable nvidia-settings-355.11 is unstable. The driver package will update to 355.11 when the settings package goes stable. A related question is "do you really need the latest nvidia drivers, or is 340.93 still good enough? It was good enough for the entire time you had it installed." > >> If it is the rdepend issue then you can probably emerge -1 librevenge >> and whatever else is depending on the old version to fix it. >> >> Also, emerge running --changed-deps=y from time to time may make those >> kinds of problems less likely. The first time you do it prepare to >> see a LOT of stuff get rebuilt - any of those packages could cause >> issues in the future but most probably will not. > > Good to know, I'll keep that in mind. I tried it and it's not too much > to rebuild, only a bit surprising: > > > , > | [ebuild U ] sys-devel/automake-wrapper-10 [9] > | [ebuild R] app-benchmarks/i7z-0.27.2 > | [ebuild R] net-misc/netkit-telnetd-0.17-r10 > | [ebuild R] virtual/editor-0 > | [ebuild U ] sys-devel/gcc-4.8.5 [4.8.4] USE="-debug%" > | [ebuild R] net-dialup/ppp-2.4.7 > | [ebuild U ] sys-apps/openrc-0.17 [0.13.11] USE="-audit%" > | [ebuild R] x11-terms/xterm-314 > | [ebuild U ] net-firewall/shorewall-4.6.10.1 [4.6.6.2] > | [ebuild NS] sys-devel/automake-1.15 [1.11.6-r1, 1.13.4] > | [ebuild U ] media-libs/alsa-lib-1.0.29 [1.0.28] > | [ebuild U ] media-sound/alsa-utils-1.0.29 [1.0.28] > | [ebuild U ] sys-apps/portage-2.2.20.1 [2.2.18] > PYTHON_TARGETS="python3_4* -python3_3*" > | [ebuild R] app-portage/gentoolkit-0.3.0.9-r2 > PYTHON_TARGETS="python3_4* -python3_3*" > | [ebuild U ] dev-python/ssl-fetch-0.3 [0.2] PYTHON_TARGETS="python3_4* > -python3_3*" > | [ebuild U ] app-portage/mirrorselect-2.2.2-r2 [2.2.2] &
Re: [gentoo-user] update problems
On Sat, 19 Sep 2015 21:05:27 Neil Bothwick wrote: > On Sat, 19 Sep 2015 21:36:06 +0200, lee wrote: > > emerge -j 8 -a --update --newuse --deep --with-bdeps=y > > @world > > > > * IMPORTANT: 4 news items need reading for repository 'gentoo'. > > * Use eselect news read to view new items. > > > > These are the packages that would be merged, in order: > > > > Calculating dependencies... done! > > > > !!! Multiple package instances within a single package slot have been > > pulled !!! into the dependency graph, resulting in a slot conflict: > > > > dev-libs/boost:0 > > > > (dev-libs/boost-1.56.0-r1:0/1.56.0::gentoo, ebuild scheduled for > > > > merge) pulled in by (no parents that aren't satisfied by other packages > > in this slot) > > > > (dev-libs/boost-1.55.0-r2:0/1.55.0::gentoo, ebuild scheduled for > > > > merge) pulled in by dev-libs/boost:0/1.55.0= required by > > (dev-libs/librevenge-0.0.2:0/0::gentoo, installed) > > ^^ (and 2 more with the same problem) > > > > dev-util/boost-build:0 > > > > (dev-util/boost-build-1.55.0:0/0::gentoo, installed) pulled in by > > > > =dev-util/boost-build-1.55* required by > > > > (dev-libs/boost-1.55.0-r2:0/1.55.0::gentoo, ebuild scheduled for merge) > > ^ > > ^ > > > > (dev-util/boost-build-1.56.0:0/0::gentoo, ebuild scheduled for merge) > > > > pulled in by =dev-util/boost-build-1.56* required by > > (dev-libs/boost-1.56.0-r1:0/1.56.0::gentoo, ebuild scheduled for merge) > > ^ > > ^ > > > > media-video/ffmpeg:0 > > > > (media-video/ffmpeg-2.6.3:0/54.56.56::gentoo, ebuild scheduled for > > > > merge) pulled in by (no parents that aren't satisfied by other packages > > in this slot) > > > > (media-video/ffmpeg-2.2.14:0/52.55.55::gentoo, installed) pulled in by > > > > media-video/ffmpeg:0/52.55.55=[vdpau] required by > > > > (media-libs/mlt-0.9.0:0/0::gentoo, installed) > > ^^^ > > These are unimportant, it is simply portage telling you it is not > updating some packages to the latest available and why. Personally, I > believe this sort of output should only be shown when using --verbose. There is an open bug/feature request for portage to be able to drop all these blocked/blocking packages (and their dependencies) and continue installing all the unaffected packages. https://bugs.gentoo.org/show_bug.cgi?id=476350 -- Reverend Paul Colquhoun, ULC. http://andor.dropbear.id.au/ Asking for technical help in newsgroups? Read this first: http://catb.org/~esr/faqs/smart-questions.html#intro
[gentoo-user] GCC 10.1 SUCKS.
IMNSHO GCC 10-1 is the suckeyest pile of sucking suck that ever did suck I am going to have to base my system on 9.3... KDE really can't update itself, I really had to flog the living bleep out of it to get it, and a lot of other stuff to settle down... The configure phases for most of these packages are so monsterously inefficient that I have to run dozens of builds concurently to get CPU utilization out of the single digits... Okay, I have a high-end processor rn but it's crazy watching the actual compile stages of various packages only blip the histogram for a fraction of a second... Here are some highlights from the fails that I consider "hard fails": Dependency of libreoffice: Libetonyek -I/usr/include/libxml2 -DNDEBUG -DLIBETONYEK_VISIBILITY -fvisibility=hidden -march=native -pipe -O3 -Wall -Wextra -Wshadow -pedantic -Weffc++ -c -o contexts/libetonyek_internal_la-IWORKLayoutElement.lo `test -f 'contexts/IWORKLayoutElement.cpp' || echo './'`context s/IWORKLayoutElement.cpp /bin/sh ../../libtool --tag=CXX --mode=compile x86_64-pc-linux-gnu-g++ -DHAVE_CONFIG_H -I. -I../.. -DBOOST_SPIRIT_USE_PHOENIX_V3 -DLIBETONYEK_BUILD -I../../inc -I../../src/lib/contexts -I/usr/include/libxml2 -I/usr/include/mdds-1.5 -I/usr/include/librevenge-0.0 -I/usr/include/libxml2 -DNDEBUG -DLIBETONYEK_VISIBILITY -fvisibility=hidden -march=native -pipe -O3 -Wall -Wextra -Wshadow -pedantic -Weffc++ -c -o contexts/libetonyek_internal_la-IWORKLineElement.lo `test -f 'contexts/IWORKLineElement.cpp' || echo './'`contexts/IW ORKLineElement.cpp NUM3Parser.cpp: In member function ‘virtual bool libetonyek::NUM3Parser::parseDocument()’: NUM3Parser.cpp:46:8: error: ‘for_each’ is not a member of ‘std’ 46 | std::for_each(sheetListRefs.begin(), sheetListRefs.end(), std::bind(::parseSheet, this, std::placeholders::_1)); | ^~~~ Eigensux!!! removed '/var/tmp/portage/dev-cpp/eigen-3.3.7/work/eigen-3.3.7/cmake/FindLAPACK.cmake' * Hardcoded definition(s) removed in CMakeLists.txt: * set(CMAKE_BUILD_TYPE "Release") * Only gcc version(s) 4.7 4.8 4.9 5.3 5.4 6.3 6.4 7.2 7.3 8.2 8.3 are supported, * of which none is installed -- The vaccine is a LIE. Powers are not rights.
Re: [gentoo-user] update problems
"J. Roeleveld" <jo...@antarean.org> writes: > On Sunday 20 September 2015 16:25:34 lee wrote: >> Alan McKinnon <alan.mckin...@gmail.com> writes: >> > On 19/09/2015 21:36, lee wrote: >> >> Hi, >> >> >> >> how could I solve these updating problems: >> >> >> >> >> >> emerge -j 8 -a --update --newuse --deep --with-bdeps=y @world >> >> >> >> * IMPORTANT: 4 news items need reading for repository 'gentoo'. >> >> * Use eselect news read to view new items. >> >> >> >> These are the packages that would be merged, in order: >> >> >> >> Calculating dependencies... done! >> >> >> >> !!! Multiple package instances within a single package slot have been >> >> pulled !!! into the dependency graph, resulting in a slot conflict: >> >> >> >> dev-libs/boost:0 >> >> >> >> (dev-libs/boost-1.56.0-r1:0/1.56.0::gentoo, ebuild scheduled for merge) >> >> pulled in by>> >> >> (no parents that aren't satisfied by other packages in this slot) >> >> >> >> (dev-libs/boost-1.55.0-r2:0/1.55.0::gentoo, ebuild scheduled for merge) >> >> pulled in by>> >> >> dev-libs/boost:0/1.55.0= required by >> >> (dev-libs/librevenge-0.0.2:0/0::gentoo, installed)>> >> >> ^^ >> >> >> >> (and 2 more with the same problem) >> > >> > I'm not sure why you are getting this one. Portage is only pulling in >> > boost-1.56.0-r1 because it's the latest stable version, but librevenge >> > requires something earlier. Portage should therefore shut up and install >> > the only real solution - keep boost at 1.55.0 >> >> Maybe because it says that there's a slot conflict. I had another one >> of those, and getting rid of it prevents me from having a pdf reader >> installed. I haven't had the need to read a pdf since, but sooner or >> later I'll need to be able to. > > Can you provide your world file? > should be located at: > /var/lib/portage/world world.bz2 Description: BZip2 compressed data The pdf problem was with mupdf blocking some library, so I removed mupdf. However, llpp still works while I thought it required mupdf, so that was false information. Sorry about that noise. >> > Try these possibilities: >> > >> > emerge =dev-libs/boost-1.55.0-r2 >> >> Why this particular version; how did you figure that out? I read from >> the second message that boost doesn't work with itself because >> librevenge is installed. So I could remove librevenge, but a lot of >> things depend on it, amongst them libreoffice. > > Don't forget to add "-1" or "--oneshot" as options when installing > dependencies manually. ok >> From there, I don't know what the effects are. Now libreoffice is still >> 4.4.1.2, and I would expect it being upgraded to 5.x maybe. So I would >> have to remove boost instead --- IIRC I installed it only to try out >> regex_match() and regex_search() --- but removing boost seems a bit >> unreasonable, considering that it takes a while to build. And even with >> boost removed, I have no good reason to think that there won't be other >> problems, and it leaves the question what to do when I need boost again: >> I don't even have a pdf reader ... >> >> So I decided I'd better ask what to do. It's hard to believe that we >> are seriously expected to remove lots of software which we might not be >> able to install again just to do an update. All these conflicts give me >> the impression that something in the repo is broken and needs to be >> fixed. > > I have no such issues, neither do most people. > Which seems to indicate the issue is not with the repo. > Lets look at the actual contents of your world-file. (see above) It seems that everyone has the problem that some versions of some packages don't go together with some versions of other packages the 'some versions of some packages' depend on. Then emerge comes along and points this out as an extremely serious problem while all it takes to solve this problem is someone convincing the person observing what emerge does that the apparently serious problems aren't relevant at all. So who is at fault here? The user taking emerges warnings seriously because they don't want to break their system, or emerge by making irrelevant warnings appear as being so serious problems that the unsuspecting user gets so confused and scared of breaking t
Re: [gentoo-user] update problems
On Sunday 20 September 2015 16:25:34 lee wrote: > Alan McKinnon <alan.mckin...@gmail.com> writes: > > On 19/09/2015 21:36, lee wrote: > >> Hi, > >> > >> how could I solve these updating problems: > >> > >> > >> emerge -j 8 -a --update --newuse --deep --with-bdeps=y @world > >> > >> * IMPORTANT: 4 news items need reading for repository 'gentoo'. > >> * Use eselect news read to view new items. > >> > >> These are the packages that would be merged, in order: > >> > >> Calculating dependencies... done! > >> > >> !!! Multiple package instances within a single package slot have been > >> pulled !!! into the dependency graph, resulting in a slot conflict: > >> > >> dev-libs/boost:0 > >> > >> (dev-libs/boost-1.56.0-r1:0/1.56.0::gentoo, ebuild scheduled for merge) > >> pulled in by>> > >> (no parents that aren't satisfied by other packages in this slot) > >> > >> (dev-libs/boost-1.55.0-r2:0/1.55.0::gentoo, ebuild scheduled for merge) > >> pulled in by>> > >> dev-libs/boost:0/1.55.0= required by > >> (dev-libs/librevenge-0.0.2:0/0::gentoo, installed)>> > >> ^^ > >> > >> (and 2 more with the same problem) > > > > I'm not sure why you are getting this one. Portage is only pulling in > > boost-1.56.0-r1 because it's the latest stable version, but librevenge > > requires something earlier. Portage should therefore shut up and install > > the only real solution - keep boost at 1.55.0 > > Maybe because it says that there's a slot conflict. I had another one > of those, and getting rid of it prevents me from having a pdf reader > installed. I haven't had the need to read a pdf since, but sooner or > later I'll need to be able to. Can you provide your world file? should be located at: /var/lib/portage/world > > Try these possibilities: > > > > emerge =dev-libs/boost-1.55.0-r2 > > Why this particular version; how did you figure that out? I read from > the second message that boost doesn't work with itself because > librevenge is installed. So I could remove librevenge, but a lot of > things depend on it, amongst them libreoffice. Don't forget to add "-1" or "--oneshot" as options when installing dependencies manually. > From there, I don't know what the effects are. Now libreoffice is still > 4.4.1.2, and I would expect it being upgraded to 5.x maybe. So I would > have to remove boost instead --- IIRC I installed it only to try out > regex_match() and regex_search() --- but removing boost seems a bit > unreasonable, considering that it takes a while to build. And even with > boost removed, I have no good reason to think that there won't be other > problems, and it leaves the question what to do when I need boost again: > I don't even have a pdf reader ... > > So I decided I'd better ask what to do. It's hard to believe that we > are seriously expected to remove lots of software which we might not be > able to install again just to do an update. All these conflicts give me > the impression that something in the repo is broken and needs to be > fixed. I have no such issues, neither do most people. Which seems to indicate the issue is not with the repo. Lets look at the actual contents of your world-file. (see above) > > emerge -avuND world > > > > or > > > > emerge -j 8 -a --update --newuse --deep --with-bdeps=n @world > > > > or quickpkg boost, then unmerge it and re-run emerge world. > > Boost is a pain to build so with a quickpkg you can put it back with a > > minimum of effort > > Maybe next weekend or so, I don't feel like doing it now and don't > really have the time to. quickpkg is really quick. Then, to reinstall from that: emerge -vak1 dev-libs/boost > >> dev-util/boost-build:0 > >> > >> (dev-util/boost-build-1.55.0:0/0::gentoo, installed) pulled in by > >> > >> =dev-util/boost-build-1.55* required by > >> (dev-libs/boost-1.55.0-r2:0/1.55.0::gentoo, ebuild scheduled for > >> merge) ^ ^ > >> > >> (dev-util/boost-build-1.56.0:0/0::gentoo, ebuild scheduled for merge) > >> pulled in by>> > >> =dev-util/boost-build-1.56* required by > >> (dev-libs/boost-1.56.0-r1:0/1.56.0::gentoo, ebuild scheduled for > >> merge) ^ ^ > > > > This is a consequence of boost. > > Fix the boost
Re: [gentoo-user] update problems
Rich Freeman <ri...@gentoo.org> writes: > On Sun, Sep 20, 2015 at 1:24 PM, J. Roeleveld <jo...@antarean.org> wrote: >> On Sunday 20 September 2015 16:25:34 lee wrote: >>> So I decided I'd better ask what to do. It's hard to believe that we >>> are seriously expected to remove lots of software which we might not be >>> able to install again just to do an update. All these conflicts give me >>> the impression that something in the repo is broken and needs to be >>> fixed. >> >> I have no such issues, neither do most people. >> Which seems to indicate the issue is not with the repo. >> Lets look at the actual contents of your world-file. (see above) >> > > So, first, I don't think it is a good idea to just start uninstalling > packages first and then try to fix them. That might or might not > work, but it certainly isn't the first thing I'd try. +1 > Second, this could very well be a problem with the repo, which is the > whole point of the debate around dynamic dependencies. Current > practices tend to create situations that our package managers can't > handle. They don't break for everybody instantly, which is why > they're so insidious, and also why changing the practice was somewhat > controversial when it first came up a year ago. Which means? I mean, I don't exactly have a lot of stuff installed and nonetheless "slot conflicts". Perhaps they don't matter and thereby don't classify as something that the package management couldn't handle. Now if there is something that the package management cannot handle, what messages would I get? > I hate to post it a 3rd time, but before we bicker 14 more times on > this, could somebody please just try adding --backtrack=50, and if Ok --- I haven't changed anything yet other than running emerge --sync again today: , | heimdali ~ # emerge -j 8 -a --update --newuse --deep --with-bdeps=y --backtrack=500 @world | | * IMPORTANT: 4 news items need reading for repository 'gentoo'. | * Use eselect news read to view new items. | | | These are the packages that would be merged, in order: | | Calculating dependencies... done! | | !!! Multiple package instances within a single package slot have been pulled | !!! into the dependency graph, resulting in a slot conflict: | | dev-libs/boost:0 | | (dev-libs/boost-1.56.0-r1:0/1.56.0::gentoo, ebuild scheduled for merge) pulled in by | (no parents that aren't satisfied by other packages in this slot) | | (dev-libs/boost-1.55.0-r2:0/1.55.0::gentoo, ebuild scheduled for merge) pulled in by | dev-libs/boost:0/1.55.0= required by (dev-libs/librevenge-0.0.2:0/0::gentoo, installed) | ^^ | (and 2 more with the same problem) | | dev-util/boost-build:0 | | (dev-util/boost-build-1.55.0:0/0::gentoo, installed) pulled in by | =dev-util/boost-build-1.55* required by (dev-libs/boost-1.55.0-r2:0/1.55.0::gentoo, ebuild scheduled for merge) | ^ ^ | | (dev-util/boost-build-1.56.0:0/0::gentoo, ebuild scheduled for merge) pulled in by | =dev-util/boost-build-1.56* required by (dev-libs/boost-1.56.0-r1:0/1.56.0::gentoo, ebuild scheduled for merge) | ^ ^ | | x11-drivers/nvidia-drivers:0 | | (x11-drivers/nvidia-drivers-355.11:0/0::gentoo, ebuild scheduled for merge) pulled in by | (no parents that aren't satisfied by other packages in this slot) | | (x11-drivers/nvidia-drivers-340.93:0/0::gentoo, ebuild scheduled for merge) pulled in by | ~x11-drivers/nvidia-drivers-340.93 required by (media-video/nvidia-settings-340.58:0/0::gentoo, ebuild scheduled for merge) | ^ ^^ | | media-video/ffmpeg:0 | | (media-video/ffmpeg-2.6.3:0/54.56.56::gentoo, ebuild scheduled for merge) pulled in by | (no parents that aren't satisfied by other packages in this slot) | | (media-video/ffmpeg-2.2.14:0/52.55.55::gentoo, installed) pulled in by | media-video/ffmpeg:0/52.55.55=[vdpau] required by (media-libs/mlt-0.9.0:0/0::gentoo, installed) | | | | It may be possible to solve this problem by using package.mask to | prevent one of those packages from being selected. However, it is also | possible that conflicting dependencies exist such that they are | impossible to satisfy simultaneously. If such a conflict exists in | the dependencies of two different packages, then those packages can | not be installed simultaneously. | | For more information, see MASKED PACKAGES section in the emerge man | page or refer to the Gentoo Handbook. | | | !!! The ebuild selected to satisfy "sci-libs/hdf5" has unmet requirements. | - sci-libs/hdf5-1.8.14-r1::gentoo USE="cxx fortran threads zlib -debug -examples -fortran2003 -mpi -static-libs -szip" | | The following REQUIRED_USE flag constraints are unsa
Re: [gentoo-user] blocks....
Hi Fernando, Thanks for replying. I issued this command: tamer@tux ~ $ emerge -pvuDN --with-bdeps=y @system @world and got still these blocks :( If you still have any ideas solving it, I'd be happy to hear from you. These are the packages that would be merged, in order: Calculating dependencies... done! !!! Multiple package instances within a single package slot have been pulled !!! into the dependency graph, resulting in a slot conflict: dev-libs/boost:0 (dev-libs/boost-1.56.0-r1:0/1.56.0::gentoo, installed) pulled in by dev-libs/boost:0/1.56.0= required by (dev-libs/librevenge-0.0.2:0/0::gentoo, installed) ^^ dev-libs/boost:0/1.56.0 required by (app-office/libreoffice-bin-4.4.5.2:0/0::gentoo, ebuild scheduled for merge) ^ (and 6 more with the same problems) (dev-libs/boost-1.55.0-r2:0/1.55.0::gentoo, ebuild scheduled for merge) pulled in by dev-libs/boost:0/1.55.0= required by (app-text/libebook-0.1.2:0/0::gentoo, installed) ^^ dev-util/mdds:0 (dev-util/mdds-0.12.1:0/0.12.1::gentoo, installed) pulled in by >=dev-util/mdds-0.12.1 required by (app-text/libetonyek-0.1.3:0/0::gentoo, installed) ^^ ^^ (dev-util/mdds-0.12.0:0/0.12.0::gentoo, ebuild scheduled for merge) pulled in by >=dev-util/mdds-0.12.0:0/0.12.0= required by (dev-libs/libixion-0.9.0:0/0.10::gentoo, installed) ^^ dev-util/boost-build:0 (dev-util/boost-build-1.55.0:0/0::gentoo, ebuild scheduled for merge) pulled in by =dev-util/boost-build-1.55* required by (dev-libs/boost-1.55.0-r2:0/1.55.0::gentoo, ebuild scheduled for merge) ^ ^ (dev-util/boost-build-1.56.0:0/0::gentoo, installed) pulled in by =dev-util/boost-build-1.56* required by (dev-libs/boost-1.56.0-r1:0/1.56.0::gentoo, installed) ^ ^ It may be possible to solve this problem by using package.mask to prevent one of those packages from being selected. However, it is also possible that conflicting dependencies exist such that they are impossible to satisfy simultaneously. If such a conflict exists in the dependencies of two different packages, then those packages can not be installed simultaneously. For more information, see MASKED PACKAGES section in the emerge man page or refer to the Gentoo Handbook. !!! The ebuild selected to satisfy ">=media-libs/libmediaart-0.1:1.0" has unmet requirements. - media-libs/libmediaart-0.7.0::gentoo USE="gtk introspection qt5 -qt4 -test -vala" ABI_X86="64" The following REQUIRED_USE flag constraints are unsatisfied: at-most-one-of ( gtk qt4 qt5 ) The above constraints are a subset of the following complete expression: at-most-one-of ( gtk qt4 qt5 ) vala? ( introspection ) (dependency required by "media-plugins/grilo-plugins-0.2.13::gentoo" [installed]) (dependency required by "media-sound/rhythmbox-3.2.1::gentoo[upnp-av]" [ebuild]) (dependency required by "@selected" [set]) (dependency required by "@world" [argument]) * IMPORTANT: 2 news items need reading for repository 'gentoo'. * Use eselect news read to view new items.
Re: [gentoo-user] blocks....
2015-09-05 22:43 GMT-06:00 Tamer Higazi <th9...@googlemail.com>: > Hi Fernando, > Thanks for replying. I issued this command: > tamer@tux ~ $ emerge -pvuDN --with-bdeps=y @system @world > > and got still these blocks :( > If you still have any ideas solving it, I'd be happy to hear from you. > > > > These are the packages that would be merged, in order: > > Calculating dependencies... done! > > !!! Multiple package instances within a single package slot have been pulled > !!! into the dependency graph, resulting in a slot conflict: > > dev-libs/boost:0 > > (dev-libs/boost-1.56.0-r1:0/1.56.0::gentoo, installed) pulled in by > dev-libs/boost:0/1.56.0= required by > (dev-libs/librevenge-0.0.2:0/0::gentoo, installed) > ^^ > > dev-libs/boost:0/1.56.0 required by > (app-office/libreoffice-bin-4.4.5.2:0/0::gentoo, ebuild scheduled for merge) > ^ > > > (and 6 more with the same problems) > > (dev-libs/boost-1.55.0-r2:0/1.55.0::gentoo, ebuild scheduled for > merge) pulled in by > dev-libs/boost:0/1.55.0= required by > (app-text/libebook-0.1.2:0/0::gentoo, installed) > ^^ > > > dev-util/mdds:0 > > (dev-util/mdds-0.12.1:0/0.12.1::gentoo, installed) pulled in by > >=dev-util/mdds-0.12.1 required by > (app-text/libetonyek-0.1.3:0/0::gentoo, installed) > ^^ ^^ > > > (dev-util/mdds-0.12.0:0/0.12.0::gentoo, ebuild scheduled for merge) > pulled in by > >=dev-util/mdds-0.12.0:0/0.12.0= required by > (dev-libs/libixion-0.9.0:0/0.10::gentoo, installed) > ^^ > > > dev-util/boost-build:0 > > (dev-util/boost-build-1.55.0:0/0::gentoo, ebuild scheduled for merge) > pulled in by > =dev-util/boost-build-1.55* required by > (dev-libs/boost-1.55.0-r2:0/1.55.0::gentoo, ebuild scheduled for merge) > ^ ^ > > > > (dev-util/boost-build-1.56.0:0/0::gentoo, installed) pulled in by > =dev-util/boost-build-1.56* required by > (dev-libs/boost-1.56.0-r1:0/1.56.0::gentoo, installed) > ^ ^ > > Are you using ~amd64?, these blockers seem to be mostly related to libreoffice-bin, I have seen something like this trying to use libreoffice-bin with ~amd64 keywords, because specific versions and flags are required to use libreoffice-bin. you can try a 'emerge -pet @world' to check if all the dependcies are solving right, if by chance you installed dependencies manually a check of your @world would be a good idea to be sure you didn't miss a --oneshot, it might you just need to push portage to go deeper with a --backtrack=30 > !!! The ebuild selected to satisfy ">=media-libs/libmediaart-0.1:1.0" > has unmet requirements. > - media-libs/libmediaart-0.7.0::gentoo USE="gtk introspection qt5 -qt4 > -test -vala" ABI_X86="64" > > The following REQUIRED_USE flag constraints are unsatisfied: > at-most-one-of ( gtk qt4 qt5 ) > > The above constraints are a subset of the following complete expression: > at-most-one-of ( gtk qt4 qt5 ) vala? ( introspection ) > For this you should use package.use and unset either gtk or qt5. seems unrelated to the other stuff.
[gentoo-user] update problems
Hi,
how could I solve these updating problems:
emerge -j 8 -a --update --newuse --deep --with-bdeps=y @world
* IMPORTANT: 4 news items need reading for repository 'gentoo'.
* Use eselect news read to view new items.
These are the packages that would be merged, in order:
Calculating dependencies... done!
!!! Multiple package instances within a single package slot have been pulled
!!! into the dependency graph, resulting in a slot conflict:
dev-libs/boost:0
(dev-libs/boost-1.56.0-r1:0/1.56.0::gentoo, ebuild scheduled for merge)
pulled in by
(no parents that aren't satisfied by other packages in this slot)
(dev-libs/boost-1.55.0-r2:0/1.55.0::gentoo, ebuild scheduled for merge)
pulled in by
dev-libs/boost:0/1.55.0= required by
(dev-libs/librevenge-0.0.2:0/0::gentoo, installed)
^^
(and 2 more with the same problem)
dev-util/boost-build:0
(dev-util/boost-build-1.55.0:0/0::gentoo, installed) pulled in by
=dev-util/boost-build-1.55* required by
(dev-libs/boost-1.55.0-r2:0/1.55.0::gentoo, ebuild scheduled for merge)
^ ^
(dev-util/boost-build-1.56.0:0/0::gentoo, ebuild scheduled for merge) pulled
in by
=dev-util/boost-build-1.56* required by
(dev-libs/boost-1.56.0-r1:0/1.56.0::gentoo, ebuild scheduled for merge)
^ ^
media-video/ffmpeg:0
(media-video/ffmpeg-2.6.3:0/54.56.56::gentoo, ebuild scheduled for merge)
pulled in by
(no parents that aren't satisfied by other packages in this slot)
(media-video/ffmpeg-2.2.14:0/52.55.55::gentoo, installed) pulled in by
media-video/ffmpeg:0/52.55.55=[vdpau] required by
(media-libs/mlt-0.9.0:0/0::gentoo, installed)
It may be possible to solve this problem by using package.mask to
prevent one of those packages from being selected. However, it is also
possible that conflicting dependencies exist such that they are
impossible to satisfy simultaneously. If such a conflict exists in
the dependencies of two different packages, then those packages can
not be installed simultaneously.
For more information, see MASKED PACKAGES section in the emerge man
page or refer to the Gentoo Handbook.
!!! The ebuild selected to satisfy "sci-libs/hdf5" has unmet requirements.
- sci-libs/hdf5-1.8.14-r1::gentoo USE="cxx fortran threads zlib -debug
-examples -fortran2003 -mpi -static-libs -szip"
The following REQUIRED_USE flag constraints are unsatisfied:
threads? ( !cxx !fortran )
The above constraints are a subset of the following complete expression:
cxx? ( !mpi ) mpi? ( !cxx ) threads? ( !cxx !mpi !fortran ) fortran2003? (
fortran )
(dependency required by "media-libs/openimageio-1.3.5::gentoo" [installed])
(dependency required by "@selected" [set])
(dependency required by "@world" [argument])
I could remove boost (and maybe reinstall it later), but I would like to
keep ffmpeg. hdf5 apparently goes back to having blender installed,
which I would also like to keep. And apparently, I would have to remove
libreoffice before I could update.
Why can't we just update like we can with any other distribution but
have to run into dependency problems all the time instead?
What do I do when I need to update /right now/ and find myself being
blocked with cryptic messages like the above that leave me stranded?
Once I used 'emerge --sync', there is no way to turn it back to continue
to be able to install software if needed when the update cannot be
performed. Updates simply need to work, there's no way around that.
--
Again we must be afraid of speaking of daemons for fear that daemons
might swallow us. Finally, this fear has become reasonable.
Re: [gentoo-user] update problems
On 19/09/2015 21:36, lee wrote: > Hi, > > how could I solve these updating problems: > > > emerge -j 8 -a --update --newuse --deep --with-bdeps=y @world > > > > * IMPORTANT: 4 news items need reading for repository 'gentoo'. > * Use eselect news read to view new items. > > > These are the packages that would be merged, in order: > > Calculating dependencies... done! > > !!! Multiple package instances within a single package slot have been pulled > !!! into the dependency graph, resulting in a slot conflict: > > dev-libs/boost:0 > > (dev-libs/boost-1.56.0-r1:0/1.56.0::gentoo, ebuild scheduled for merge) > pulled in by > (no parents that aren't satisfied by other packages in this slot) > > (dev-libs/boost-1.55.0-r2:0/1.55.0::gentoo, ebuild scheduled for merge) > pulled in by > dev-libs/boost:0/1.55.0= required by > (dev-libs/librevenge-0.0.2:0/0::gentoo, installed) > ^^ > > (and 2 more with the same problem) I'm not sure why you are getting this one. Portage is only pulling in boost-1.56.0-r1 because it's the latest stable version, but librevenge requires something earlier. Portage should therefore shut up and install the only real solution - keep boost at 1.55.0 Try these possibilities: emerge =dev-libs/boost-1.55.0-r2 emerge -avuND world or emerge -j 8 -a --update --newuse --deep --with-bdeps=n @world or quickpkg boost, then unmerge it and re-run emerge world. Boost is a pain to build so with a quickpkg you can put it back with a minimum of effort > > dev-util/boost-build:0 > > (dev-util/boost-build-1.55.0:0/0::gentoo, installed) pulled in by > =dev-util/boost-build-1.55* required by > (dev-libs/boost-1.55.0-r2:0/1.55.0::gentoo, ebuild scheduled for merge) > ^ ^ > > > > (dev-util/boost-build-1.56.0:0/0::gentoo, ebuild scheduled for merge) > pulled in by > =dev-util/boost-build-1.56* required by > (dev-libs/boost-1.56.0-r1:0/1.56.0::gentoo, ebuild scheduled for merge) > ^ ^ > > This is a consequence of boost. Fix the boost issue and this one goes away > > media-video/ffmpeg:0 > > (media-video/ffmpeg-2.6.3:0/54.56.56::gentoo, ebuild scheduled for merge) > pulled in by > (no parents that aren't satisfied by other packages in this slot) > > (media-video/ffmpeg-2.2.14:0/52.55.55::gentoo, installed) pulled in by > media-video/ffmpeg:0/52.55.55=[vdpau] required by > (media-libs/mlt-0.9.0:0/0::gentoo, installed) > > Similar to boost. try a similar approach > > > It may be possible to solve this problem by using package.mask to > prevent one of those packages from being selected. However, it is also > possible that conflicting dependencies exist such that they are > impossible to satisfy simultaneously. If such a conflict exists in > the dependencies of two different packages, then those packages can > not be installed simultaneously. > > For more information, see MASKED PACKAGES section in the emerge man > page or refer to the Gentoo Handbook. > > > !!! The ebuild selected to satisfy "sci-libs/hdf5" has unmet requirements. > - sci-libs/hdf5-1.8.14-r1::gentoo USE="cxx fortran threads zlib -debug > -examples -fortran2003 -mpi -static-libs -szip" > > The following REQUIRED_USE flag constraints are unsatisfied: > threads? ( !cxx !fortran ) Come on, the problem is as clear as daylight and stated right there in the output: If you have threads in USE for hdf5, then you cannot have cxx and/or fortran also in USE for hdf5 echo "=sci-libs/hdf5-1.8.14-r1 -cxx -fortran" >> /etc/portage/package.use/package.use > > The above constraints are a subset of the following complete expression: > cxx? ( !mpi ) mpi? ( !cxx ) threads? ( !cxx !mpi !fortran ) fortran2003? > ( fortran ) > > (dependency required by "media-libs/openimageio-1.3.5::gentoo" [installed]) > (dependency required by "@selected" [set]) > (dependency required by "@world" [argument])
Re: [gentoo-user] blocks....
On Sunday, September 06, 2015 6:43:37 AM Tamer Higazi wrote: > Hi Fernando, > Thanks for replying. I issued this command: > tamer@tux ~ $ emerge -pvuDN --with-bdeps=y @system @world > > and got still these blocks :( > If you still have any ideas solving it, I'd be happy to hear from you. > > > > These are the packages that would be merged, in order: > > Calculating dependencies... done! > > !!! Multiple package instances within a single package slot have been pulled > !!! into the dependency graph, resulting in a slot conflict: > > dev-libs/boost:0 > > (dev-libs/boost-1.56.0-r1:0/1.56.0::gentoo, installed) pulled in by > dev-libs/boost:0/1.56.0= required by > (dev-libs/librevenge-0.0.2:0/0::gentoo, installed) > ^^ > > dev-libs/boost:0/1.56.0 required by > (app-office/libreoffice-bin-4.4.5.2:0/0::gentoo, ebuild scheduled for merge) > ^ > > > (and 6 more with the same problems) > > (dev-libs/boost-1.55.0-r2:0/1.55.0::gentoo, ebuild scheduled for > merge) pulled in by > dev-libs/boost:0/1.55.0= required by > (app-text/libebook-0.1.2:0/0::gentoo, installed) > ^^ > > > dev-util/mdds:0 > > (dev-util/mdds-0.12.1:0/0.12.1::gentoo, installed) pulled in by > >=dev-util/mdds-0.12.1 required by > (app-text/libetonyek-0.1.3:0/0::gentoo, installed) > ^^ ^^ > > > (dev-util/mdds-0.12.0:0/0.12.0::gentoo, ebuild scheduled for merge) > pulled in by > >=dev-util/mdds-0.12.0:0/0.12.0= required by > (dev-libs/libixion-0.9.0:0/0.10::gentoo, installed) > ^^ > > > dev-util/boost-build:0 > > (dev-util/boost-build-1.55.0:0/0::gentoo, ebuild scheduled for merge) > pulled in by > =dev-util/boost-build-1.55* required by > (dev-libs/boost-1.55.0-r2:0/1.55.0::gentoo, ebuild scheduled for merge) > ^ ^ > > > > (dev-util/boost-build-1.56.0:0/0::gentoo, installed) pulled in by > =dev-util/boost-build-1.56* required by > (dev-libs/boost-1.56.0-r1:0/1.56.0::gentoo, installed) > ^ ^ > > > > > It may be possible to solve this problem by using package.mask to > prevent one of those packages from being selected. However, it is also > possible that conflicting dependencies exist such that they are > impossible to satisfy simultaneously. If such a conflict exists in > the dependencies of two different packages, then those packages can > not be installed simultaneously. > > For more information, see MASKED PACKAGES section in the emerge man > page or refer to the Gentoo Handbook. > > > !!! The ebuild selected to satisfy ">=media-libs/libmediaart-0.1:1.0" > has unmet requirements. > - media-libs/libmediaart-0.7.0::gentoo USE="gtk introspection qt5 -qt4 > -test -vala" ABI_X86="64" > > The following REQUIRED_USE flag constraints are unsatisfied: > at-most-one-of ( gtk qt4 qt5 ) > > The above constraints are a subset of the following complete expression: > at-most-one-of ( gtk qt4 qt5 ) vala? ( introspection ) > > (dependency required by "media-plugins/grilo-plugins-0.2.13::gentoo" > [installed]) > (dependency required by "media-sound/rhythmbox-3.2.1::gentoo[upnp-av]" > [ebuild]) > (dependency required by "@selected" [set]) > (dependency required by "@world" [argument]) > > * IMPORTANT: 2 news items need reading for repository 'gentoo'. > * Use eselect news read to view new items. > > > You have two issues left. The first one is the libreoffice-bin blocker. For that one you could try adding --exclude=app-office/libreoffice-bin until they release a new revision of the package. What will definitely is to emerge -C libreoffice- bin, run your update, and then emerge app-office/libreoffice. The second issue is that you have both gtk and qt5 enabled for media- libs/libmediaart so you need to disable one of them. To use gtk add the following to your package.use file: media-libs/libmediaart -qt5 -- Fernando Rodriguez
Re: [gentoo-user] update problems
On Saturday, September 26, 2015 03:10:48 PM lee wrote: > "J. Roeleveld" <jo...@antarean.org> writes: > > On Sunday 20 September 2015 16:25:34 lee wrote: > >> Alan McKinnon <alan.mckin...@gmail.com> writes: > >> > On 19/09/2015 21:36, lee wrote: > >> >> Hi, > >> >> > >> >> > >> >> > >> >> how could I solve these updating problems: > >> >> > >> >> > >> >> > >> >> emerge -j 8 -a --update --newuse --deep --with-bdeps=y @world > >> >> > >> >> > >> >> * IMPORTANT: 4 news items need reading for repository 'gentoo'. > >> >> * Use eselect news read to view new items. > >> >> > >> >> > >> >> These are the packages that would be merged, in order: > >> >> > >> >> > >> >> Calculating dependencies... done! > >> >> > >> >> > >> >> > >> >> !!! Multiple package instances within a single package slot have been > >> >> > >> >> pulled !!! into the dependency graph, resulting in a slot conflict: > >> >> > >> >> > >> >> dev-libs/boost:0 > >> >> > >> >> > >> >> (dev-libs/boost-1.56.0-r1:0/1.56.0::gentoo, ebuild scheduled for > >> >>merge) > >> >> pulled in by>> > >> >> (no parents that aren't satisfied by other packages in this slot) > >> >> > >> >> (dev-libs/boost-1.55.0-r2:0/1.55.0::gentoo, ebuild scheduled for > >> >>merge) > >> >> pulled in by>> > >> >> dev-libs/boost:0/1.55.0= required by > >> >> (dev-libs/librevenge-0.0.2:0/0::gentoo, installed)>> > >> >> ^^ > >> >> > >> >> (and 2 more with the same problem) > >> > > >> > > >> > > >> > I'm not sure why you are getting this one. Portage is only pulling in > >> > boost-1.56.0-r1 because it's the latest stable version, but librevenge > >> > requires something earlier. Portage should therefore shut up and > >> > install > >> > the only real solution - keep boost at 1.55.0 > >> > >> > >> > >> Maybe because it says that there's a slot conflict. I had another one > >> of those, and getting rid of it prevents me from having a pdf reader > >> installed. I haven't had the need to read a pdf since, but sooner or > >> later I'll need to be able to. > > > > Can you provide your world file? > > should be located at: > > /var/lib/portage/world > > The pdf problem was with mupdf blocking some library, so I removed > mupdf. However, llpp still works while I thought it required mupdf, so > that was false information. Sorry about that noise. What else did you remove recently? > >> > Try these possibilities: > >> > > >> > > >> > emerge =dev-libs/boost-1.55.0-r2 > >> > >> > >> > >> Why this particular version; how did you figure that out? I read from > >> the second message that boost doesn't work with itself because > >> librevenge is installed. So I could remove librevenge, but a lot of > >> things depend on it, amongst them libreoffice. > > > > Don't forget to add "-1" or "--oneshot" as options when installing > > dependencies manually. > > ok > > >> From there, I don't know what the effects are. Now libreoffice is still > >> 4.4.1.2, and I would expect it being upgraded to 5.x maybe. So I would > >> have to remove boost instead --- IIRC I installed it only to try out > >> regex_match() and regex_search() --- but removing boost seems a bit > >> unreasonable, considering that it takes a while to build. And even with > >> boost removed, I have no good reason to think that there won't be other > >> problems, and it leaves the question what to do when I need boost again: > >> I don't even have a pdf reader ... > >> > >> > >> > >> So I decided I'd better ask what to do. It's hard to believe that we > >> are seriously expected to remove lots of software which we might not be > >> able to install again just to do an update. All these conflicts give me > >> the impression that something in the repo is broken and n
Re: [gentoo-user] update problems
On Sat, 19 Sep 2015 21:36:06 +0200, lee wrote: > emerge -j 8 -a --update --newuse --deep --with-bdeps=y > @world > > > > * IMPORTANT: 4 news items need reading for repository 'gentoo'. > * Use eselect news read to view new items. > > > These are the packages that would be merged, in order: > > Calculating dependencies... done! > > !!! Multiple package instances within a single package slot have been > pulled !!! into the dependency graph, resulting in a slot conflict: > > dev-libs/boost:0 > > (dev-libs/boost-1.56.0-r1:0/1.56.0::gentoo, ebuild scheduled for > merge) pulled in by (no parents that aren't satisfied by other packages > in this slot) > > (dev-libs/boost-1.55.0-r2:0/1.55.0::gentoo, ebuild scheduled for > merge) pulled in by dev-libs/boost:0/1.55.0= required by > (dev-libs/librevenge-0.0.2:0/0::gentoo, installed) > ^^ (and 2 more with the same problem) > > dev-util/boost-build:0 > > (dev-util/boost-build-1.55.0:0/0::gentoo, installed) pulled in by > =dev-util/boost-build-1.55* required by > (dev-libs/boost-1.55.0-r2:0/1.55.0::gentoo, ebuild scheduled for merge) > ^ > ^ > > > (dev-util/boost-build-1.56.0:0/0::gentoo, ebuild scheduled for merge) > pulled in by =dev-util/boost-build-1.56* required by > (dev-libs/boost-1.56.0-r1:0/1.56.0::gentoo, ebuild scheduled for merge) > ^ > ^ > > > media-video/ffmpeg:0 > > (media-video/ffmpeg-2.6.3:0/54.56.56::gentoo, ebuild scheduled for > merge) pulled in by (no parents that aren't satisfied by other packages > in this slot) > > (media-video/ffmpeg-2.2.14:0/52.55.55::gentoo, installed) pulled in by > media-video/ffmpeg:0/52.55.55=[vdpau] required by > (media-libs/mlt-0.9.0:0/0::gentoo, installed) > ^^^ > These are unimportant, it is simply portage telling you it is not updating some packages to the latest available and why. Personally, I believe this sort of output should only be shown when using --verbose. > It may be possible to solve this problem by using package.mask to > prevent one of those packages from being selected. However, it is also > possible that conflicting dependencies exist such that they are > impossible to satisfy simultaneously. If such a conflict exists in > the dependencies of two different packages, then those packages can > not be installed simultaneously. > > For more information, see MASKED PACKAGES section in the emerge man > page or refer to the Gentoo Handbook. > > > !!! The ebuild selected to satisfy "sci-libs/hdf5" has unmet > requirements. > - sci-libs/hdf5-1.8.14-r1::gentoo USE="cxx fortran threads zlib -debug > -examples -fortran2003 -mpi -static-libs -szip" > > The following REQUIRED_USE flag constraints are unsatisfied: > threads? ( !cxx !fortran ) This is blocking you and the reason is given, if you have the threads flag on, cxx and fortran must be off. You have both threads and cxx on which won't work. > Why can't we just update like we can with any other distribution but > have to run into dependency problems all the time instead? These aren't dependency problems, they are conflicting USE flags, a situation that cannot arise with a binary distro. If you want the flexibility that USE flags offer, you have to accept that not all combinations will work together. > What do I do when I need to update /right now/ and find myself being > blocked with cryptic messages like the above that leave me stranded? That's the real problem, that the messages are so cryptic. The solution is simple, working out what needs to be done from the messages is not. > Once I used 'emerge --sync', there is no way to turn it back to continue > to be able to install software if needed when the update cannot be > performed. Updates simply need to work, there's no way around that. You can always roll back by masking the updates if necessary, and the old ebuilds are always available. Now that the tree is using git, it is probably possibly to sync back to yesterday if you need to. -- Neil Bothwick WINDOWS: Will Install Needless Data On Whole System pgp1qoOW22Hya.pgp Description: OpenPGP digital signature
Re: [gentoo-user] update problems
Neil Bothwick <n...@digimed.co.uk> writes: > On Sat, 19 Sep 2015 21:36:06 +0200, lee wrote: > >> emerge -j 8 -a --update --newuse --deep --with-bdeps=y >> @world >> >> >> >> * IMPORTANT: 4 news items need reading for repository 'gentoo'. >> * Use eselect news read to view new items. >> >> >> These are the packages that would be merged, in order: >> >> Calculating dependencies... done! >> >> !!! Multiple package instances within a single package slot have been >> pulled !!! into the dependency graph, resulting in a slot conflict: >> >> dev-libs/boost:0 >> >> (dev-libs/boost-1.56.0-r1:0/1.56.0::gentoo, ebuild scheduled for >> merge) pulled in by (no parents that aren't satisfied by other packages >> in this slot) >> >> (dev-libs/boost-1.55.0-r2:0/1.55.0::gentoo, ebuild scheduled for >> merge) pulled in by dev-libs/boost:0/1.55.0= required by >> (dev-libs/librevenge-0.0.2:0/0::gentoo, installed) >> ^^ (and 2 more with the same problem) >> >> dev-util/boost-build:0 >> >> (dev-util/boost-build-1.55.0:0/0::gentoo, installed) pulled in by >> =dev-util/boost-build-1.55* required by >> (dev-libs/boost-1.55.0-r2:0/1.55.0::gentoo, ebuild scheduled for merge) >> ^ >> ^ >> >> >> (dev-util/boost-build-1.56.0:0/0::gentoo, ebuild scheduled for merge) >> pulled in by =dev-util/boost-build-1.56* required by >> (dev-libs/boost-1.56.0-r1:0/1.56.0::gentoo, ebuild scheduled for merge) >> ^ >> ^ >> >> >> media-video/ffmpeg:0 >> >> (media-video/ffmpeg-2.6.3:0/54.56.56::gentoo, ebuild scheduled for >> merge) pulled in by (no parents that aren't satisfied by other packages >> in this slot) >> >> (media-video/ffmpeg-2.2.14:0/52.55.55::gentoo, installed) pulled in by >> media-video/ffmpeg:0/52.55.55=[vdpau] required by >> (media-libs/mlt-0.9.0:0/0::gentoo, installed) >> ^^^ >> > These are unimportant, it is simply portage telling you it is not > updating some packages to the latest available and why. Personally, I > believe this sort of output should only be shown when using --verbose. Really? That doesn't seem to be at all what it says. It says, with huge exclamation marks even: "!!! Multiple package instances within a single package slot have been pulled !!! into the dependency graph, resulting in a slot conflict:" So obviously, something terrible is going on, preventing you from installing required packages, and there is a dependency conflict which cannot be solved because only one package of many can be used while several are required in its place. If this is irrelevant, then why doesn't it say that it is irrelevant? Why was suggested that I remove boost to resolve an irrelevant conflict? Should I always ignore such messages? > [...] >> >> !!! The ebuild selected to satisfy "sci-libs/hdf5" has unmet >> requirements. >> - sci-libs/hdf5-1.8.14-r1::gentoo USE="cxx fortran threads zlib -debug >> -examples -fortran2003 -mpi -static-libs -szip" >> >> The following REQUIRED_USE flag constraints are unsatisfied: >> threads? ( !cxx !fortran ) > > This is blocking you and the reason is given, if you have the threads > flag on, cxx and fortran must be off. You have both threads and cxx on > which won't work. Well, it doesn't say which of the problems that have been reported are the ones preventing me from going any further. When I get error messages, especially ones that appear to be very important (see all the exclamation marks?), I usually try to find out what the problem is and try to fix it, and starting with the important ones is one possible approach. That approach seems to be quite reasonable in this case, considering that I'm trying to upgrade and get messages which appear to be extremely important /and/ which tell me that I cannot upgrade, thus apparently proving that their importance is more than merely apparent. Then someone comes along and says that the messages with double-apparent importance are actually irrelevant. I find that very funny :) Is that a general thing
Re: [gentoo-user] update problems
On 20/09/2015 17:28, lee wrote: > Neil Bothwick <n...@digimed.co.uk> writes: > >> On Sat, 19 Sep 2015 21:36:06 +0200, lee wrote: >> >>> emerge -j 8 -a --update --newuse --deep --with-bdeps=y >>> @world >>> >>> >>> >>> * IMPORTANT: 4 news items need reading for repository 'gentoo'. >>> * Use eselect news read to view new items. >>> >>> >>> These are the packages that would be merged, in order: >>> >>> Calculating dependencies... done! >>> >>> !!! Multiple package instances within a single package slot have been >>> pulled !!! into the dependency graph, resulting in a slot conflict: >>> >>> dev-libs/boost:0 >>> >>> (dev-libs/boost-1.56.0-r1:0/1.56.0::gentoo, ebuild scheduled for >>> merge) pulled in by (no parents that aren't satisfied by other packages >>> in this slot) >>> >>> (dev-libs/boost-1.55.0-r2:0/1.55.0::gentoo, ebuild scheduled for >>> merge) pulled in by dev-libs/boost:0/1.55.0= required by >>> (dev-libs/librevenge-0.0.2:0/0::gentoo, installed) >>> ^^ (and 2 more with the same problem) >>> >>> dev-util/boost-build:0 >>> >>> (dev-util/boost-build-1.55.0:0/0::gentoo, installed) pulled in by >>> =dev-util/boost-build-1.55* required by >>> (dev-libs/boost-1.55.0-r2:0/1.55.0::gentoo, ebuild scheduled for merge) >>> ^ >>> ^ >>> >>> >>> (dev-util/boost-build-1.56.0:0/0::gentoo, ebuild scheduled for merge) >>> pulled in by =dev-util/boost-build-1.56* required by >>> (dev-libs/boost-1.56.0-r1:0/1.56.0::gentoo, ebuild scheduled for merge) >>> ^ >>> ^ >>> >>> >>> media-video/ffmpeg:0 >>> >>> (media-video/ffmpeg-2.6.3:0/54.56.56::gentoo, ebuild scheduled for >>> merge) pulled in by (no parents that aren't satisfied by other packages >>> in this slot) >>> >>> (media-video/ffmpeg-2.2.14:0/52.55.55::gentoo, installed) pulled in by >>> media-video/ffmpeg:0/52.55.55=[vdpau] required by >>> (media-libs/mlt-0.9.0:0/0::gentoo, installed) >>> ^^^ >>> >> These are unimportant, it is simply portage telling you it is not >> updating some packages to the latest available and why. Personally, I >> believe this sort of output should only be shown when using --verbose. > > Really? > > That doesn't seem to be at all what it says. It says, with huge > exclamation marks even: > > > "!!! Multiple package instances within a single package slot have been > pulled !!! into the dependency graph, resulting in a slot conflict:" > > > So obviously, something terrible is going on, preventing you from > installing required packages, and there is a dependency conflict which > cannot be solved because only one package of many can be used while > several are required in its place. > > If this is irrelevant, then why doesn't it say that it is irrelevant? > Why was suggested that I remove boost to resolve an irrelevant conflict? > > Should I always ignore such messages? No, you should not ignore such messages. They are printed for a reason. You have a SLOT conflict and whether that prevents you from proceeding or not doesn't change the fact that portage knows you have that conflict. In your specific case today, I believe portage will simply install the lesser version and be done with it, but it will only do that when you fix the USE issue (a whole separate issue) > > >> [...] >>> >>> !!! The ebuild selected to satisfy "sci-libs/hdf5" has unmet >>> requirements. >>> - sci-libs/hdf5-1.8.14-r1::gentoo USE="cxx fortran threads zlib -debug >>> -examples -fortran2003 -mpi -static-libs -szip" >>> >>> The following REQUIRED_USE flag constraints are unsatisfied: >>> threads? ( !cxx !fortran ) >> >> This is blocking you and the reason is given, if you have the threads >> flag on, cxx and fortran must be off. You have both threads and cx
[gentoo-user] boost-1.62.0-r1 blocked by nothing ??
Hi,
now I have an emerge mystery myself: It claims boost is blocked by ...
nothing. See yourself:
- emerge tells me that boost is for whatever reason blocked
- I cannot find any entry for this in /etc/portage/**
- eix does not show any kind of mask for 1.62.0-r1
- none of the installed packages show a condition preventing an update
Any idea?
Cheers,
Jörg
= %< ===
$ emerge -uDvta --changed-use --with-bdeps=y --backtrack=50 world
These are the packages that would be merged, in reverse order:
Calculating dependencies... done!
Total: 0 packages, Size of downloads: 0 KiB
!!! The following update has been skipped due to unsatisfied dependencies:
dev-libs/boost:0
!!! All ebuilds that could satisfy "=dev-util/boost-build-1.62*" have been
masked.
!!! One of the following masked packages is required to complete your
request:
- dev-util/boost-build-1.62.0-r1::gentoo (masked by: )
(dependency required by "dev-libs/boost-1.62.0-r1::gentoo" [ebuild])
For more information, see the MASKED PACKAGES section in the emerge
man page or refer to the Gentoo Handbook.
Nothing to merge; quitting.
$ find /etc/portage/ -type f -exec grep boost {} +
/etc/portage/package.use:dev-libs/boost expat
$ eix -I boost
[U] dev-libs/boost
Available versions: 1.55.0-r2(0/1.55.0)^t 1.56.0-r1(0/1.56.0)^t
~1.58.0-r1(0/1.58.0)^t ~1.59.0(0/1.59.0)^t ~1.60.0(0/1.60.0)^t
~1.61.0(0/1.61.0)^t ~1.61.0-r1(0/1.61.0)^t 1.62.0-r1(0/1.62.0)^t
~1.63.0(0/1.63.0)^t {context debug doc icu mpi +nls python static-libs
+threads tools ABI_MIPS="n32 n64 o32" ABI_PPC="32 64" ABI_S390="32 64"
ABI_X86="32 64 x32" PYTHON_TARGETS="python2_7 python3_4 python3_5"}
Installed versions: 1.56.0-r1^t(11:20:13 AM 12/03/2016)(icu nls
threads -context -debug -doc -mpi -python -static-libs -tools ABI_MIPS="-n32
-n64 -o32" ABI_PPC="-32 -64" ABI_S390="-32 -64" ABI_X86="64 -32 -x32"
PYTHON_TARGETS="python2_7 -python3_4")
Homepage:http://www.boost.org/
Description: Boost Libraries for C++
[U] dev-util/boost-build
Available versions: 1.55.0^t ~1.55.0-r1^t 1.56.0^t ~1.58.0^t ~1.59.0^t
~1.60.0^t ~1.61.0^t 1.62.0-r1^t ~1.63.0^t {examples python test
PYTHON_TARGETS="python2_7"}
Installed versions: 1.56.0^t(07:24:23 PM 07/16/2015)(-examples -python
-test PYTHON_TARGETS="python2_7")
Homepage:http://www.boost.org/doc/tools/build/index.html
Description: A system for large project software construction,
simple to use and powerful
Found 2 matches
$ equery d boost
* These packages depend on boost:
app-office/calligra-2.9.11 (dev-libs/boost)
app-office/kmymoney-4.7.2 (dev-libs/boost)
app-office/libreoffice-5.2.3.3-r1 (>=dev-libs/boost-1.55)
app-text/libabw-0.1.1 (>=dev-libs/boost-1.46)
app-text/libebook-0.1.2-r1 (dev-libs/boost)
app-text/libetonyek-0.1.6 (dev-libs/boost)
app-text/libmspub-0.1.2 (dev-libs/boost)
app-text/libmwaw-0.3.8 (dev-libs/boost)
dev-cpp/libcmis-0.5.2_pre20160820 (dev-libs/boost)
dev-cpp/yaml-cpp-0.5.3 (>=dev-libs/boost-1.49.0-r2)
dev-db/mysql-connector-c++-1.1.6 (dev-libs/boost)
dev-db/mysql-workbench-6.3.4-r1 (>=dev-libs/boost-1.55.0[nls])
dev-db/vsqlite++-0.3.13-r1 (>=dev-libs/boost-1.33.1)
dev-libs/libixion-0.11.1 (dev-libs/boost[threads])
dev-libs/liborcus-0.11.2 (dev-libs/boost)
dev-libs/librevenge-0.0.4 (dev-libs/boost)
dev-util/mdds-1.2.2 (dev-libs/boost)
games-puzzle/pingus-0.7.6 (dev-libs/boost)
games-strategy/0ad-0.0.21_alpha (dev-libs/boost)
games-strategy/wesnoth-1.12.6 (>=dev-libs/boost-1.48[nls,threads])
games-strategy/widelands-0.18 (>=dev-libs/boost-1.48)
games-util/grfcodec-6.0.5 (dev-libs/boost)
kde-apps/akonadi-1.13.1_pre20160203-r1 (dev-libs/boost)
kde-apps/gpgmepp-16.08.3 (dev-libs/boost)
kde-apps/kdepim-runtime-4.14.11_pre20160211 (dev-libs/boost)
kde-apps/kdepimlibs-4.14.11_pre20160211-r2 (>=dev-libs/boost-1.35.0-r5)
kde-apps/kget-16.08.3 (dev-libs/boost)
kde-apps/kleopatra-4.14.11_pre20160211 (dev-libs/boost)
kde-frameworks/kactivities-5.29.0 (>=dev-libs/boost-1.54)
kde-frameworks/kactivities-stats-5.29.0 (>=dev-libs/boost-1.54)
kde-plasma/kactivitymanagerd-5.8.5 (>=dev-libs/boost-1.54)
kde-plasma/plasma-desktop-5.8.5-r1 (dev-libs/boost)
media-gfx/digikam-5.3.0-r1 (dev-libs/boost[threads])
media-gfx/enblend-4.1.3-r1 (>=dev-libs/boost-1.31.0)
media-gfx/hugin-2015.0.0-r1 (>=dev-libs/boost-1.49.0-r1)
media-gfx/inkscape-0.91-r3 (>=dev-libs/boost-1.36)
media-libs/chromaprint-1.2 (test ? dev-libs/boost)
media-libs/libcdr-0.1.1 (dev-libs/boost)
media-libs/libpagemaker-0.0.3-r1 (dev-libs/boost)
media-libs/libvisio-0.1.5 (dev-libs/boost)
media-libs/openimageio-1.6.13 (dev-libs/boost[python?])
media-libs/vigra-1.9.0 (>=dev-libs/boost-1.52.0-
r6[python?,python_targets_python2_7(-)?,-python_single_target_jython2_7(-),-
python_single_target
Re: [gentoo-user] boost-1.62.0-r1 blocked by nothing ??
Jörg Schaible wrote:
> Hi,
>
> now I have an emerge mystery myself: It claims boost is blocked by ...
> nothing. See yourself:
> - emerge tells me that boost is for whatever reason blocked
> - I cannot find any entry for this in /etc/portage/**
> - eix does not show any kind of mask for 1.62.0-r1
> - none of the installed packages show a condition preventing an update
>
> Any idea?
>
> Cheers,
> Jörg
>
> = %< ===
> $ emerge -uDvta --changed-use --with-bdeps=y --backtrack=50 world
>
> These are the packages that would be merged, in reverse order:
>
> Calculating dependencies... done!
>
> Total: 0 packages, Size of downloads: 0 KiB
>
> !!! The following update has been skipped due to unsatisfied dependencies:
>
> dev-libs/boost:0
>
> !!! All ebuilds that could satisfy "=dev-util/boost-build-1.62*" have been
> masked.
> !!! One of the following masked packages is required to complete your
> request:
> - dev-util/boost-build-1.62.0-r1::gentoo (masked by: )
>
> (dependency required by "dev-libs/boost-1.62.0-r1::gentoo" [ebuild])
> For more information, see the MASKED PACKAGES section in the emerge
> man page or refer to the Gentoo Handbook.
>
>
>
> Nothing to merge; quitting.
>
> $ find /etc/portage/ -type f -exec grep boost {} +
> /etc/portage/package.use:dev-libs/boost expat
> $ eix -I boost
> [U] dev-libs/boost
> Available versions: 1.55.0-r2(0/1.55.0)^t 1.56.0-r1(0/1.56.0)^t
> ~1.58.0-r1(0/1.58.0)^t ~1.59.0(0/1.59.0)^t ~1.60.0(0/1.60.0)^t
> ~1.61.0(0/1.61.0)^t ~1.61.0-r1(0/1.61.0)^t 1.62.0-r1(0/1.62.0)^t
> ~1.63.0(0/1.63.0)^t {context debug doc icu mpi +nls python static-libs
> +threads tools ABI_MIPS="n32 n64 o32" ABI_PPC="32 64" ABI_S390="32 64"
> ABI_X86="32 64 x32" PYTHON_TARGETS="python2_7 python3_4 python3_5"}
> Installed versions: 1.56.0-r1^t(11:20:13 AM 12/03/2016)(icu nls
> threads -context -debug -doc -mpi -python -static-libs -tools ABI_MIPS="-n32
> -n64 -o32" ABI_PPC="-32 -64" ABI_S390="-32 -64" ABI_X86="64 -32 -x32"
> PYTHON_TARGETS="python2_7 -python3_4")
> Homepage:http://www.boost.org/
> Description: Boost Libraries for C++
>
> [U] dev-util/boost-build
> Available versions: 1.55.0^t ~1.55.0-r1^t 1.56.0^t ~1.58.0^t ~1.59.0^t
> ~1.60.0^t ~1.61.0^t 1.62.0-r1^t ~1.63.0^t {examples python test
> PYTHON_TARGETS="python2_7"}
> Installed versions: 1.56.0^t(07:24:23 PM 07/16/2015)(-examples -python
> -test PYTHON_TARGETS="python2_7")
> Homepage:http://www.boost.org/doc/tools/build/index.html
> Description: A system for large project software construction,
> simple to use and powerful
>
> Found 2 matches
> $ equery d boost
> * These packages depend on boost:
> app-office/calligra-2.9.11 (dev-libs/boost)
> app-office/kmymoney-4.7.2 (dev-libs/boost)
> app-office/libreoffice-5.2.3.3-r1 (>=dev-libs/boost-1.55)
> app-text/libabw-0.1.1 (>=dev-libs/boost-1.46)
> app-text/libebook-0.1.2-r1 (dev-libs/boost)
> app-text/libetonyek-0.1.6 (dev-libs/boost)
> app-text/libmspub-0.1.2 (dev-libs/boost)
> app-text/libmwaw-0.3.8 (dev-libs/boost)
> dev-cpp/libcmis-0.5.2_pre20160820 (dev-libs/boost)
> dev-cpp/yaml-cpp-0.5.3 (>=dev-libs/boost-1.49.0-r2)
> dev-db/mysql-connector-c++-1.1.6 (dev-libs/boost)
> dev-db/mysql-workbench-6.3.4-r1 (>=dev-libs/boost-1.55.0[nls])
> dev-db/vsqlite++-0.3.13-r1 (>=dev-libs/boost-1.33.1)
> dev-libs/libixion-0.11.1 (dev-libs/boost[threads])
> dev-libs/liborcus-0.11.2 (dev-libs/boost)
> dev-libs/librevenge-0.0.4 (dev-libs/boost)
> dev-util/mdds-1.2.2 (dev-libs/boost)
> games-puzzle/pingus-0.7.6 (dev-libs/boost)
> games-strategy/0ad-0.0.21_alpha (dev-libs/boost)
> games-strategy/wesnoth-1.12.6 (>=dev-libs/boost-1.48[nls,threads])
> games-strategy/widelands-0.18 (>=dev-libs/boost-1.48)
> games-util/grfcodec-6.0.5 (dev-libs/boost)
> kde-apps/akonadi-1.13.1_pre20160203-r1 (dev-libs/boost)
> kde-apps/gpgmepp-16.08.3 (dev-libs/boost)
> kde-apps/kdepim-runtime-4.14.11_pre20160211 (dev-libs/boost)
> kde-apps/kdepimlibs-4.14.11_pre20160211-r2 (>=dev-libs/boost-1.35.0-r5)
> kde-apps/kget-16.08.3 (dev-libs/boost)
> kde-apps/kleopatra-4.14.11_pre20160211 (dev-libs/boost)
> kde-frameworks/kactivities-5.29.0 (>=dev-libs/boost-1.54)
> kde-frameworks/kactivities-stats-5.29.0 (>=dev-libs/boost-1.54)
> kde-plasma/kactivitymanagerd-5.8.5 (>=dev-libs/boost-1.54)
> kde-plasma/plasma-desktop-5.8.5-r1 (dev-libs/boost)
> media-gfx/digikam-5.3.0-r1 (dev-libs/boost[threads])
> media-gfx/enb
[gentoo-user] Well, I went about updating my system again. (day 6)
I have a user consuming most of my CPU time so that's part of the reason why it's slow... My current misery factory is 439... I didn't even get it to update BASH until day 4... The thing seems to have a problem with the --deep flag these days, omitting deep seems to evade a number of the conflicts but that seems to be the ostrich approach... I'm trying my jackhammer script yet again, this time duplicating the lines for system and world but without --deep on the first round... Certainly there are groups of packages in the 439 that could be updated without triggering these conflicts but then doing that automatically wouldn't waste enough of the user's time... [ebuild U ] kde-apps/kde-meta-16.08.3:5::gentoo [16.08.1:5::gentoo] 0 KiB [blocks B ] =dev-libs/boost-1.40:0/1.61.0= required by (media-libs/qt-gstreamer-1.2.0-r2:0/0::gentoo, installed) ^^ >=dev-libs/boost-1.51.0:0/1.61.0= required by (dev-libs/liborcus-0.11.2:0/0.11::gentoo, installed) ^^ dev-libs/boost:0/1.61.0= required by (dev-libs/librevenge-0.0.4:0/0::gentoo, installed) ^^ dev-libs/boost:0/1.61.0=[python,python_targets_python2_7(-),python_targets_python3_4(-),python_targets_python3_5(-),-python_single_target_python2_7(-),-python_single_target_python3_4(-),-python_single_target_python3_5(-)] required by (dev-python/pycuda-2016.1.2:0/0::gentoo, installed) ^^ dev-libs/boost:0/1.61.0= required by (app-text/libebook-0.1.2-r1:0/0::gentoo, installed) ^^ dev-libs/boost:0/1.61.0= required by (kde-apps/akonadi-1.13.1_pre20160203-r1:4/4::gentoo, installed) ^^ >=dev-libs/boost-1.55:0/1.61.0= required by (app-office/libreoffice-5.2.3.3-r1:0/0::gentoo, installed) ^^ dev-libs/boost:0/1.61.0= required by (dev-db/mysql-connector-c++-1.1.6:0/0::gentoo, installed) ^^ dev-libs/boost:0/1.61.0= required by (dev-cpp/libcmis-0.5.2_pre20160820:0.5/0.5::gentoo, installed) ^^ >=dev-libs/boost-1.35.0-r5:0/1.61.0= required by (kde-apps/kdepimlibs-4.14.11_pre20160211-r2:4/4.14::gentoo, installed) ^^ dev-libs/boost:0/1.61.0= required by (dev-util/mdds-1.2.2:1/1.2::gentoo, installed) ^^ dev-libs/xapian:0 (dev-libs/xapian-1.4.1:0/30::gentoo, ebuild scheduled for merge) pulled in by (no parents that aren't satisfied by other packages in this slot) (dev-libs/xapian-1.2.24:0/1.2.22::gentoo, installed) pulled in by =dev-libs/xapian-1.2*[chert] required by (kde-frameworks/baloo-4.14.3:4/4.14::gentoo, installed) ^ media-video/ffmpeg:0 (media-video/ffmpeg-2.8.9:0/54.56.56::gentoo, ebuild scheduled for merge) pulled in by >=media-video/ffmpeg-2.8.5:0/54.56.56=[abi_x86_32(-),abi_x86_64(-)] required by (media-plugins/gst-plugins-libav-1.8.3:1.0/1.0::gentoo, installed) media-video/ffmpeg:0/54.56.56= required by (media-plugins/alsa-plugins-1.1.1:0/0::gentoo, installed)
Re: [gentoo-user] update problems
Alan McKinnon <alan.mckin...@gmail.com> writes: > On 26/09/2015 11:47, lee wrote: >> Rich Freeman <ri...@gentoo.org> writes: >> >>> On Sat, Sep 19, 2015 at 3:57 PM, Alan McKinnon <alan.mckin...@gmail.com> >>> wrote: > [...] >> It gives the same results (after syncing again), plus a message that >> wasn't there before: >> >> >> , >> | x11-drivers/nvidia-drivers:0 >> | >> | (x11-drivers/nvidia-drivers-355.11:0/0::gentoo, ebuild scheduled for >> merge) pulled in by >> | (no parents that aren't satisfied by other packages in this slot) >> | >> | (x11-drivers/nvidia-drivers-340.93:0/0::gentoo, ebuild scheduled for >> merge) pulled in by >> | ~x11-drivers/nvidia-drivers-340.93 required by >> (media-video/nvidia-settings-340.58:0/0::gentoo, ebuild scheduled for merge) >> | ^ ^^ >> ` >> >> >> This looks kinda weird because I expect those drivers to be updated as >> well, and if they aren't, I will have to remove nvidia-settings. >> >> Let's try backtrack 500 ... same result, and doesn't take longer. > > That doesn't look like a block. It looks like an info message that > portage is "helpfully" displaying (but really belongs only in -v output. > Maybe even the non-existent -vvv...) > > Portage is telling you *why* it is not updating to latest stable > nvidia-drivers even though a higher version is in the tree. It's because > nvidia-settings is out of step with nvidia-drivers. Look at output of > "eix nvidia": > > nvidia-drivers-355.11 is stable > nvidia-settings-355.11 is unstable. > > The driver package will update to 355.11 when the settings package goes > stable. > > A related question is "do you really need the latest nvidia drivers, or > is 340.93 still good enough? It was good enough for the entire time you > had it installed." Do I need to update at all? After all, the system has been running fine all the time, except that I wanted the latest version of seamonkey and that I tend to update every three months or so as time permits, and the last update was almost haft a year ago or so. Of course I want the latest nvidia drivers, so I removed nvidia-settings. (I have updated, and it took almost 2 days.) Nvidia-settings is kinda weird anyway, like when you enable sync to vblanc, apparently that is somehow being remembered, and the question is "when is it applied": When you start an X session or when you start nvidia-settings. Same goes for all the other settings you can make with it. And now, with nvidia drivers incompatible with nvidia-settings and nvidia-settings not installed, what settings that have been made with it are applied? >>> If it is the rdepend issue then you can probably emerge -1 librevenge >>> and whatever else is depending on the old version to fix it. >>> >>> Also, emerge running --changed-deps=y from time to time may make those >>> kinds of problems less likely. The first time you do it prepare to >>> see a LOT of stuff get rebuilt - any of those packages could cause >>> issues in the future but most probably will not. >> >> Good to know, I'll keep that in mind. I tried it and it's not too much >> to rebuild, only a bit surprising: > [...] >> >> Should I do that before updating or after? I guess I'm on the save side >> doing it before, so I'll do that. > > Before, or just include the option in your emerge command. Portage will > sort out the order to build them in. Ok --- I did it before and after ... > Remember something about portage - the only source of info it has about > packages is what is in ebuilds. So if say a package from upstream now > needs a different version of automake to build correctly, and the dev > forgot to add that[1], portage can't take account of it and can't help. > > Portage also has many useful shortcuts, things like "you don't need to > rebuild that package just yet as nothing in the current list needs it > yet" so there are options to leave those packages out. But if "nothing > needs it yet" is not true because it's missing from ebuilds, you run > into a mess. > > And the really important thing is, portage cannot help resolve this. > It's dumb software and has no clue why that build is failing. Isn't that the same for all package management software? >>>> You fail to understand how gentoo works. At no time did Gentoo ever >>>> guarantee that updates would work like binary distros and the process >>>> would be trouble free. Quite the opposite - Gentoo is upfront in telling >>>> you th
Re: [gentoo-user] Re: Konsole
(-gd%) (-gl%) (-gu%) (-gug%) (-he%)
(-hi%) (-hr%) (-hu%) (-id%) (-is%) (-it%) (-ja%) (-ka%) (-kk%) (-km%)
(-kmr_Latn%) (-kn%) (-ko%) (-kok%) (-ks%) (-lb%) (-lo%) (-lt%) (-lv%) (-mai%)
(-mk%) (-ml%) (-mn%) (-mni%) (-mr%) (-my%) (-nb%) (-ne%) (-nl%) (-nn%) (-nr%)
(-nso%) (-oc%) (-om%) (-or%) (-pa_IN%) (-pl%) (-pt%) (-pt_BR%) (-ro%) (-ru%)
(-rw%) (-sa_IN%) (-sat%) (-sd%) (-si%) (-sid%) (-sk%) (-sl%) (-sq%) (-sr%)
(-sr_Latn%) (-ss%) (-st%) (-sv%) (-sw_TZ%) (-ta%) (-te%) (-tg%) (-th%) (-tn%)
(-tr%) (-ts%) (-tt%) (-ug%) (-uk%) (-uz%) (-ve%) (-vi%) (-xh%) (-zh_CN%)
(-zh_TW%) (-zu%)" 0 KiB
[ebuild U ] net-libs/gnutls-3.3.24::gentoo [3.3.17.1::gentoo] USE="crywrap
cxx nls openssl zlib -dane -doc -examples -guile -pkcs11 -static-libs {-test}"
ABI_X86="32 (64) (-x32)" LINGUAS="en -cs -de -fi -fr -it -ms -nl -pl -sv -uk
-vi -zh_CN" 6,148 KiB
[ebuild U ] sys-apps/pciutils-3.4.1::gentoo [3.3.1::gentoo] USE="kmod udev
zlib -dns -static-libs" ABI_X86="(64) -32 (-x32)" 395 KiB
[ebuild U ] sys-apps/gptfdisk-1.0.1::gentoo [0.8.10::gentoo] USE="ncurses
-static" 191 KiB
[ebuild U ] media-libs/libgphoto2-2.5.10:0/6::gentoo [2.5.9:0/6::gentoo]
USE="exif jpeg nls -doc -examples -gd -serial" ABI_X86="32 (64) (-x32)"
CAMERAS="ptp2 -adc65 -agfa_cl20 -aox -ax203 -barbie -canon -casio_qv
-clicksmart310 -digigr8 -digita -dimagev -dimera3500 -directory -enigma13 -fuji
-gsmart300 -hp215 -iclick -jamcam -jd11 -jl2005a -jl2005c -kodak_dc120
-kodak_dc210 -kodak_dc240 -kodak_dc3200 -kodak_ez200 -konica -konica_qm150
-largan -lg_gsm -mars -mustek -panasonic_coolshot -panasonic_dc1000
-panasonic_dc1580 -panasonic_l859 -pccam300 -pccam600 -pentax -polaroid_pdc320
-polaroid_pdc640 -polaroid_pdc700 -ricoh -ricoh_g3 -samsung -sierra
-sipix_blink2 -sipix_web2 -smal -sonix -sony_dscf1 -sony_dscf55 -soundvision
-spca50x -sq905 -st2205 -stv0674 -stv0680 -sx330z -topfield -toshiba_pdrm11
-tp6801" 6,829 KiB
[ebuild NS] dev-qt/qtdbus-5.5.1:5::gentoo [4.8.6-r1:4::gentoo] USE="-debug
{-test}" 0 KiB
[ebuild R] sys-apps/groff-1.22.2::gentoo USE="X -examples" L10N="-ja%"
LINGUAS="(-ja%)" 0 KiB
[ebuild N#] kde-frameworks/kf-env-3:5::gentoo 0 KiB
[ebuild R] sys-apps/man-pages-4.05::gentoo USE="nls" L10N="-da% -de%
-fr% -it% -ja% -nl% -pl% -ro% -ru% -zh-CN%" LINGUAS="(-da%) (-de%) (-fr%)
(-it%) (-ja%) (-nl%) (-pl%) (-ro%) (-ru%) (-zh_CN%)" 0 KiB
[ebuild U ] x11-libs/cairo-1.14.6::gentoo [1.14.2::gentoo] USE="X glib
opengl svg xcb (-aqua) -debug (-directfb) (-gles2) -static-libs -valgrind
-xlib-xcb" ABI_X86="32 (64) (-x32)" 35,196 KiB
[ebuild U ] sys-apps/pcsc-lite-1.8.16-r1::gentoo [1.8.12-r1::gentoo]
USE="(policykit) udev -libusb -python% (-selinux)" ABI_X86="(64%*) -32% (-x32)"
PYTHON_TARGETS="python2_7" 694 KiB
[ebuild U ] app-text/iso-codes-3.68::gentoo [3.65::gentoo] LINGUAS="en -af
-am -ar -as -ast -az -be -bg -bn -bn_IN -br -bs -byn -ca -crh -cs -cy -da -de
-dz -el -eo -es -et -eu -fa -fi -fo -fr -ga -gez -gl -gu -haw -he -hi -hr -hu
-hy -ia -id -is -it -ja -ka -kk -km -kn -ko -kok -ku -lt -lv -mi -mk -ml -mn
-mr -ms -mt -nb -ne -nl -nn -nso -oc -or -pa -pl -ps -pt -pt_BR -ro -ru -rw -si
-sk -sl -so -sq -sr -sr@latin -sv -sw -ta -te -th -ti -tig -tk -tl -tr -tt
-tt@iqtelif -ug -uk -ve -vi -wa -wal -wo -xh -zh_CN -zh_HK -zh_TW -zu" 3,368 KiB
[ebuild U ] dev-libs/librevenge-0.0.4::gentoo [0.0.2::gentoo] USE="-doc
{-test}" ABI_X86="(64) -32 (-x32)" 412 KiB
[ebuild U ] app-admin/perl-cleaner-2.20::gentoo [2.19::gentoo] 7 KiB
[ebuild U ] media-gfx/imagemagick-6.9.4.6:0/6.9.4.6::gentoo
[6.9.4.1:0/6.9.4.1::gentoo] USE="X bzip2 corefonts cxx jpeg lcms openmp pango
perl png svg tiff truetype xml zlib -autotrace -djvu -fftw -fontconfig -fpx
-graphviz -hdri -jbig -jpeg2k -lqr -lzma (-opencl) -openexr -postscript -q32
-q64 -q8 -raw -static-libs {-test} -webp -wmf" 8,580 KiB
[ebuild U ] dev-libs/openssl-1.0.2h-r2::gentoo [1.0.2h::gentoo] USE="asm
kerberos sslv3%* tls-heartbeat zlib -bindist -gmp -rfc3779 -sctp -sslv2%
-static-libs {-test} -vanilla" ABI_X86="32 (64) (-x32)" CPU_FLAGS_X86="(sse2)"
0 KiB
[ebuild N ] dev-qt/qtnetwork-5.5.1:5::gentoo USE="ssl -bindist -connman
-debug -libproxy -networkmanager {-test}" 0 KiB
[ebuild U ] net-misc/wg
[gentoo-user] KDE update revdep-rebuild.sh fail
mmon:0 dev-libs/grantlee:5 dev-libs/hyphen:0 dev-libs/icu:0/60.2 dev-libs/iniparser:0 dev-libs/ivykis:0 dev-libs/jansson:0 dev-libs/json-c:0/2 dev-libs/json-glib:0 dev-libs/jsoncpp:0/19 dev-libs/leveldb:0 dev-libs/libaio:0 dev-libs/libappindicator:2 dev-libs/libappindicator:3 dev-libs/libassuan:0 dev-libs/libatasmart:0/4 dev-libs/libatomic_ops:0 dev-libs/libattica:0 dev-libs/libbsd:0 dev-libs/libburn:0 dev-libs/libbytesize:0 dev-libs/libcdio:0/15 dev-libs/libcdio-paranoia:0 dev-libs/libcroco:0.6 dev-libs/libdaemon:0 dev-libs/libdbusmenu:0 dev-libs/libdbusmenu-qt:0 dev-libs/libebml:0/4 dev-libs/libev:0 dev-libs/libevdev:0 dev-libs/libevent:0/2.1-6 dev-libs/libffi:0 dev-libs/libgcrypt:0/20 dev-libs/libgpg-error:0 dev-libs/libgudev:0/0 dev-libs/libgusb:0 dev-libs/libical:0/2 dev-libs/libindicator:0 dev-libs/libindicator:3 dev-libs/libinput:0/10 dev-libs/libixion:0/0.12 dev-libs/libksba:0 dev-libs/liblinear:0/3 dev-libs/libltdl:0 dev-libs/libnatspec:0 dev-libs/libnl:3 dev-libs/liborcus:0/0.12 dev-libs/libpcre:3 dev-libs/libpcre2:0 dev-libs/libpthread-stubs:0 dev-libs/libpwquality:0 dev-libs/librevenge:0 dev-libs/libsigc++:2 dev-libs/libsodium:0/18 dev-libs/libtasn1:0/6 dev-libs/libunibreak:0 dev-libs/libunistring:0/2 dev-libs/libusb:1 dev-libs/libusb-compat:0 dev-libs/libverto:0 dev-libs/libx86:0 dev-libs/libx86emu:0 dev-libs/libxml2:2 dev-libs/libxslt:0 dev-libs/libyaml:0 dev-libs/lzo:2 dev-libs/mpc:0 dev-libs/mpfr:0/4 dev-libs/nettle:0/6.1 dev-libs/npth:0 dev-libs/nspr:0 dev-libs/nss:0 dev-libs/openssl:0 dev-libs/popt:0 dev-libs/protobuf:0/15 dev-libs/pugixml:0 dev-libs/qjson:0 dev-libs/rasqal:0 dev-libs/redland:0 dev-libs/sni-qt:0 dev-libs/tinyxml:0 dev-libs/vala-common:0 dev-libs/volume_key:0 dev-libs/wayland:0 dev-libs/wayland-protocols:0 dev-libs/xapian:0/30 dev-libs/xmlsec:0 dev-libs/yajl:0/2 dev-perl/Archive-Zip:0 dev-perl/Authen-SASL:0 dev-perl/Cairo:0 dev-perl/Crypt-PasswdMD5:0 dev-perl/DBD-mysql:0 dev-perl/DBI:0 dev-perl/Date-Manip:0 dev-perl/Digest-HMAC:0 dev-perl/Digest-SHA1:0 dev-perl/Encode-Locale:0 dev-perl/Error:0 dev-perl/ExtUtils-Depends:0 dev-perl/ExtUtils-PkgConfig:0 dev-perl/File-BaseDir:0 dev-perl/File-DesktopEntry:0 dev-perl/File-Listing:0 dev-perl/File-MimeInfo:0 dev-perl/GSSAPI:0 dev-perl/Gtk2:0 dev-perl/Gtk2-Ex-PodViewer:0 dev-perl/Gtk2-Ex-Simple-List:0 dev-perl/HTML-Parser:0 dev-perl/HTML-Tagset:0 dev-perl/HTML-TokeParser-Simple:0 dev-perl/HTTP-Cookies:0 dev-perl/HTTP-Daemon:0 dev-perl/HTTP-Date:0 dev-perl/HTTP-Message:0 dev-perl/HTTP-Negotiate:0 dev-perl/IO-HTML:0 dev-perl/IO-Socket-INET6:0 dev-perl/IO-Socket-SSL:0 dev-perl/IO-stringy:0 dev-perl/LWP-MediaTypes:0 dev-perl/LWP-Protocol-https:0 dev-perl/Locale-gettext:0 dev-perl/Log-Agent:0 dev-perl/Module-Build:0 dev-perl/Net-Daemon:0 dev-perl/Net-HTTP:0 dev-perl/Net-SMTP-SSL:0 dev-perl/Net-SSLeay:0 dev-perl/Net-UPnP:0 dev-perl/Pango:0 dev-perl/PlRPC:0 dev-perl/SGMLSpm:0 dev-perl/Socket6:0 dev-perl/Sub-Override:0 dev-perl/TermReadKey:0 dev-perl/Text-CharWidth:0 dev-perl/Text-Unidecode:0 dev-perl/Text-WrapI18N:0 dev-perl/URI:0 dev-perl/Unicode-EastAsianWidth:0 dev-perl/WWW-RobotRules:0 dev-perl/XML-NamespaceSupport:0 dev-perl/XML-Parser:0 dev-perl/XML-SAX:0 dev-perl/XML-SAX-Base:0 dev-perl/XML-SAX-Expat:0 dev-perl/XML-Simple:0 dev-perl/glib-perl:0 dev-perl/libintl-perl:0 dev-perl/libwww-perl:0 dev-python/PyQt5:0 dev-python/PySocks:0 dev-python/asn1crypto:0 dev-python/bcrypt:0 dev-python/certifi:0 dev-python/cffi:0/1.11.4 dev-python/chardet:0 dev-python/cryptography:0 dev-python/cython:0 dev-python/dbus-python:0 dev-python/docutils:0 dev-python/enum34:0 dev-python/gevent:0 dev-python/greenlet:0 dev-python/gst-python:1.0 dev-python/httplib2:0 dev-python/idna:0 dev-python/ipaddress:0 dev-python/lxml:0 dev-python/mysql-python:0 dev-python/ndg-httpsclient:0 dev-python/paramiko:0 dev-python/pillow:0 dev-python/ply:0/3.9 dev-python/py:0 dev-python/pyasn1:0 dev-python/pyblake2:0 dev-python/pycairo:0 dev-python/pycparser:0 dev-python/pycurl:0 dev-python/pygments:0 dev-python/pygobject:3 dev-python/pynacl:0 dev-python/pyopenssl:0 dev-python/pyxattr:0 dev-python/pyzmq:0 dev-python/requests:0 dev-python/setuptools:0 dev-python/simplejson:0 dev-python/sip:0/12 dev-python/six:0 dev-python/ssl-fetch:0 dev-python/urlgrabber:0 dev-python/urllib3:0 dev-qt/designer:4 dev-qt/designer:5/5.9 dev-qt/linguist-tools:5/5.9 dev-qt/qdbus:5/5.9 dev-qt/qt3support:4 dev-qt/qtbluetooth:5/5.9 dev-qt/qtchooser:0 dev-qt/qtconcurrent:5/5.9 dev-qt/qtcore:4 dev-qt/qtcore:5/5.9 dev-qt/qtdbus:4 dev-qt/qtdbus:5/5.9 dev-qt/qtdeclarative:4 dev-qt/qtdeclarative:5/5.9 dev-qt/qtgraphicaleffects:5/5.9 dev-qt/qtgui:4 dev-qt/qtgui:5/5.9 dev-qt/qtimageformats:5/5.9 dev-qt/qtmultimedia:5/5.9 dev-qt/qtnetwork:5/5.9 dev-qt/qtopengl:4 dev-qt/qtopengl:5/5.9 dev-qt/qtpaths:5/5.9 dev-qt/qtprintsupport:5/5.9 dev-qt/qtquickcontrols:5/5.9 dev-qt/qtquickcontrols2:5/5.9 dev-qt/qtscript:4 dev-qt/qtscript:5/5.9 dev-qt/qtsql:4 dev-qt/qtsql:5/5.9 dev-qt/qtsvg:4 dev-qt/qtsvg:5/5.9 dev-qt/qttest:4
