Re: [gentoo-user] Portage spokes again...

[Tom H]

On Wed, Dec 21, 2016 at 8:53 AM, Corbin Bird  wrote:
>
> ( PulseAudio is also being merged into systemd. Think about it. )

Unless the systemd developers have decided to stop targeting the
non-desktop use-case, this is pure delirium.

Re: [gentoo-user] Portage spokes again...

[Rich Freeman]

On Wed, Dec 21, 2016 at 7:46 PM, Daniel Campbell  wrote:
>
> How does a file take up less than a single FS block? An inode has to be
> allocated _somewhere_, does it not?
>

So, the details are going to be filesystem-specific, but typically
inodes go into some kind of area of the disk reserved for metadata, so
that many of them can be stored in a single disk block.  They're also
fixed-length so storing them in groups lets you address them as an
array.  Likewise for directory trees, allocation tracking, and so on.

In ext4 inodes are 256 bytes by default.  So, obviously you can fit 16
of those in a single 4k disk block.

60 of those bytes are used to map the inode to the extents on the disk
that contain the file's data.  If the data within the file takes up
less than 60 bytes then ext4 will store the data inside the actual
inode itself since the mapping isn't actually needed in that case.
That saves a whole block.

Other filesystems do things differently.  I don't profess to be a
general expert, but I have read a fair bit on btrfs.  Btrfs allocates
spaces in b+ tree nodes that contain fixed-length records on one side
(which would store things like inodes and other metadata records), and
a heap full of variable-length records on the other.  The latter can
be used to store the content of small files.  I believe btrfs can also
use metadata space to store small regions of files as well (such as if
you have a file that is just a few bytes larger than the next block
boundary, or when you overwrite 1 byte of a large file which in btrfs
does not get done in-place).

The optimization of storing small bits of data without using entire
blocks is a pretty common one.  Another common optimization is dealing
with large blocks of zeros in files.  If you write a gigabyte of zeros
in most filesystems it will certainly not take a gigabyte of space,
even if the filesystem does not otherwise use compression.

And of course you have stuff that consumes nothing but inodes, like
links and device nodes and such.

It isn't surprising that these optimizations are widespread on
unix-like filesystems since small files for configuration/etc are so
common.  Not only does it save a ton of space, but it also saves a
seek when the file is read.

Finally, I'll just comment that if you're interested in brushing up on
data structures, the documentation for any of the modern filesystems
is a great thing to read up on.  Since disk seeks are incredibly
expensive but disks are very large a great deal of thought goes into
how the data gets stored.

--
Rich

Re: [gentoo-user] Portage spokes again...

[Daniel Campbell]

On Wed, Dec 21, 2016 at 10:06:00PM +0200, Alan McKinnon wrote:
> On 21/12/2016 21:51, Rich Freeman wrote:
> > On Wed, Dec 21, 2016 at 2:46 PM, Rich Freeman  wrote:
> >> On Wed, Dec 21, 2016 at 2:20 PM,   wrote:
> >>
> >>> The following USE changes are necessary to proceed:
> >>>  (see "package.use" in the portage(5) man page for more details)
> >>> # required by kde-plasma/kwin-5.8.3::gentoo
> >>> # required by kde-plasma/plasma-workspace-5.8.3-r4::gentoo
> >>> # required by net-p2p/ktorrent-5.0.1::gentoo[shutdown]
> >>> # required by @selected
> >>> # required by @world (argument)
>  =media-libs/mesa-12.0.1 wayland
> >>
> >>
> >> I suggest ignoring this for the moment and see if the info above
> >> resolves your systemd issues.  I'm not sure why kwin has the
> >> dependency that it does, but it looks to me like it is set up as a
> >> hard dependency that you can't avoid without modifying the ebuild.
> >> I'll see if I can figure out more.  The changes above should at least
> >> get rid of whatever is pulling in systemd.
> >>
> >> Installing wayland shouldn't actually hurt anything.  I noticed that I
> >> have it installed likely for the same reason, and it isn't like it
> >> will start running on its own. But, I'm not sure yet whether you can
> >> avoid it.
> >>
> > 
> > Well, I should have just waited to reply, but here is the issue:
> > https://mail.kde.org/pipermail/release-team/2015-July/008725.html
> > 
> > kwin does in fact have a non-conditional dependency on wayland, so you
> > need to install it.  It won't do anything if you don't run it, but it
> > is not possible to build kwin without wayland support.  Judging by the
> > claim in the email that it used to take 100 conditionals in the source
> > to make it optional, I doubt anybody in Gentoo will be patching this
> > anytime soon.  I guess you could always fork it if you wanted to.
> > 
> > So, sorry, not what you wanted to hear, and not really what I care to
> > hear either since I don't use wayland, but at least it doesn't need to
> > be running in this case.  I wouldn't be surprised if that changes in
> > the future, but everybody knows that xorg is on borrowed time right
> > now.
> > 
> > Well, if nothing else at least this splits the thread so that you can
> > reply to the systemd and the wayland issues separately...
> > 
> 
> 
> Doesn't it strike you as curious that the 4 extra wayland packages
> consume 8.5M installed (sans size of sources in distfiles) and for 18
> months no-one has raised nary a whimper about it, whereas recall the
> giant whinge-fest a while back about a few 10s of harmless unit files
> (text), each less than one fs block?

How does a file take up less than a single FS block? An inode has to be
allocated _somewhere_, does it not?

As for the KDE <-> wayland thing, it's possible KDE users don't care
about something like that. In fact I would argue that the average person
who wants a desktop environment cares little about the dependency tree
for said environment, because they care more about their DE than what it
takes to run it. It's also an exercise in insanity, given the size of
DEs. I applaud the teams working on packaging them; it's a huge effort.

Exceptions are obviously GNOME + systemd, which caused a large upset.
If/when KDE starts requiring wayland, I expect a similar, though
somewhat smaller outcry. It'll come down to having a quality Wayland
setup that's as smooth to get up and running as Xorg.

One of the issues with wayland adoption is 1) the sheer amount of
software that'd need to be ported (there's apparently an X-compatible
mode in Wayland or something, but I've heard nothing regarding its
quality or its interoperability), 2) its structure is not exactly clear,
3) afaik there is no known compositor that supports all the features
you'd want to see in a modern display manager, and 4) writing tools
for the display server basically depends on a competent and extensible
compositor since everything goes through it first.

What I see more likely in the future for Wayland are different levels of
"rich" experience, all using a common Wayland protocol to be
mix-and-match. So someone can have a barebones system with Fluxbox (like
me), but another Wayland implementation can have all the bells and
whistles the DE crowd is used to. Who knows?

> 
> For the record, openrc user here on Gentoo; systemd on Ubuntu at work
> (no feasible choice with Ubuntu)
> 
> -- 
> Alan McKinnon
> alan.mckin...@gmail.com
> 
> 


signature.asc
Description: Digital signature

Re: [gentoo-user] Portage spokes again...

[Daniel Campbell]

On Wed, Dec 21, 2016 at 02:04:05PM -0500, Rich Freeman wrote:
> On Wed, Dec 21, 2016 at 1:44 PM,   wrote:
> > Corbin Bird  [16-12-21 17:12]:
> > The first run of emerge tells me to add the systemd USE flag to dbus.
> > I did that and ran into to problems I reported.
> 
> Ok, I think you left that bit out...
> 
> And this is why it is helpful to understand why portage is doing
> something before just changing configuration settings.  Adding the
> systemd USE flag to packages is a really quick way to end up with
> systemd getting installed.  Generally speaking it shouldn't just
> happen by default...
> 
> Can you show the output when you add -t to the emerge command?  I
> think that will be helpful.  However, I think an earlier poster was on
> the right track when he pointed out that the tmpfiles virtual requires
> an unstable version of openrc.  I'm not sure why that was getting
> pulled in in the first place, and -t should show that.
> 
> >
> > emerge: there are no ebuilds built with USE flags to satisfy 
> > "media-libs/mesa[egl,gbm,gles2?,wayland]".
> > !!! One of the following packages is required to complete your request:
> > - media-libs/mesa-11.2.2::gentoo (Change USE: +wayland)
> > (dependency required by "kde-plasma/kwin-5.8.3::gentoo" [ebuild])
> > (dependency required by "kde-plasma/plasma-workspace-5.8.3-r4::gentoo" 
> > [ebuild])
> > (dependency required by "net-p2p/ktorrent-5.0.1::gentoo[shutdown]" [ebuild])
> > (dependency required by "@selected" [set])
> > (dependency required by "@world" [argument])
> > [1]20322 exit 1 emerge -t --update --newuse --deep --with-bdeps=y 
> > --tree --keep-going
> >
> > What?
> >
> > Now wayland shall be installed? IK!
> > I want my UNIX back!
> 
> Interesting.  I just noticed that it pulled in wayland for me.  I have
> no idea why kwin requires wayland support in mesa.  It obviously works
> fine with xorg.  I might do some looking into that.
> 
> There isn't really anything non-UNIX about wayland, though I'm not
> sure I'd be in a rush to use it just yet.  It is just a replacement
> for xorg (to say the least, it doesn't purport to be a
> feature-complete replacement and may never be).

Wayland may not be non-UNIX, but putting everything into the compositor
(including keyboard input) just shifts responsibility to another piece
of software and actually complicates things a bit. I've not done much
digging into the matter but if I understood the structure of Wayland
correctly, you can't take screenshots or other talks-to-display-server
stuff unless the compositor supports it. With so much I/O going through
one thing (the compositor), it's ripe for abuse and security problems.

Of course, that doesn't make Xorg's security problems go away... like
any other set of competing software, you're trading one set of pros/cons
for another.

I've not seen anything about Wayland that convinces me it's hands-down
better.

That plasma dependency sounds weird, though. If you're not using
Wayland, it shouldn't require mesa to support it.

> 
> Your wayland issues and your systemd issues are most likely entirely
> unrelated...
> 
> -- 
> Rich
> 


signature.asc
Description: Digital signature

Re: [gentoo-user] Portage spokes again...

[Rich Freeman]

On Wed, Dec 21, 2016 at 3:06 PM, Alan McKinnon  wrote:
>
> Doesn't it strike you as curious

Not really.  :)

> 10s of harmless unit files (text), each less than one fs block?
>

Setting aside the core of this issue (which everybody has already gone
on about ad nauseum, myself included), I figured I'd point out that on
most modern filesystems very small text files don't actually use
blocks per-se, but instead they're stored in the inode or other
metadata records.  They have to be quite small to fit, but Linux
systems tend to have a lot of files that don't require an actual disk
block as a result and it can save quite a bit of space cumulatively.

-- 
Rich

Re: [gentoo-user] Portage spokes again...

[Alan McKinnon]

On 21/12/2016 21:51, Rich Freeman wrote:
> On Wed, Dec 21, 2016 at 2:46 PM, Rich Freeman  wrote:
>> On Wed, Dec 21, 2016 at 2:20 PM,   wrote:
>>
>>> The following USE changes are necessary to proceed:
>>>  (see "package.use" in the portage(5) man page for more details)
>>> # required by kde-plasma/kwin-5.8.3::gentoo
>>> # required by kde-plasma/plasma-workspace-5.8.3-r4::gentoo
>>> # required by net-p2p/ktorrent-5.0.1::gentoo[shutdown]
>>> # required by @selected
>>> # required by @world (argument)
 =media-libs/mesa-12.0.1 wayland
>>
>>
>> I suggest ignoring this for the moment and see if the info above
>> resolves your systemd issues.  I'm not sure why kwin has the
>> dependency that it does, but it looks to me like it is set up as a
>> hard dependency that you can't avoid without modifying the ebuild.
>> I'll see if I can figure out more.  The changes above should at least
>> get rid of whatever is pulling in systemd.
>>
>> Installing wayland shouldn't actually hurt anything.  I noticed that I
>> have it installed likely for the same reason, and it isn't like it
>> will start running on its own. But, I'm not sure yet whether you can
>> avoid it.
>>
> 
> Well, I should have just waited to reply, but here is the issue:
> https://mail.kde.org/pipermail/release-team/2015-July/008725.html
> 
> kwin does in fact have a non-conditional dependency on wayland, so you
> need to install it.  It won't do anything if you don't run it, but it
> is not possible to build kwin without wayland support.  Judging by the
> claim in the email that it used to take 100 conditionals in the source
> to make it optional, I doubt anybody in Gentoo will be patching this
> anytime soon.  I guess you could always fork it if you wanted to.
> 
> So, sorry, not what you wanted to hear, and not really what I care to
> hear either since I don't use wayland, but at least it doesn't need to
> be running in this case.  I wouldn't be surprised if that changes in
> the future, but everybody knows that xorg is on borrowed time right
> now.
> 
> Well, if nothing else at least this splits the thread so that you can
> reply to the systemd and the wayland issues separately...
> 


Doesn't it strike you as curious that the 4 extra wayland packages
consume 8.5M installed (sans size of sources in distfiles) and for 18
months no-one has raised nary a whimper about it, whereas recall the
giant whinge-fest a while back about a few 10s of harmless unit files
(text), each less than one fs block?

For the record, openrc user here on Gentoo; systemd on Ubuntu at work
(no feasible choice with Ubuntu)

-- 
Alan McKinnon
alan.mckin...@gmail.com

Re: [gentoo-user] Portage spokes again...

[Alan McKinnon]

On 21/12/2016 21:46, Rich Freeman wrote:

> I suggest ignoring this for the moment and see if the info above
> resolves your systemd issues.  I'm not sure why kwin has the
> dependency that it does, but it looks to me like it is set up as a
> hard dependency that you can't avoid without modifying the ebuild.

Ignore what I said in another reply, you are correct about kwin:

COMMON_DEPEND="
...
$(add_frameworks_dep kwayland)
...
>=dev-libs/wayland-1.2
...
media-libs/mesa[egl,gbm,gles2?,wayland]

> Installing wayland shouldn't actually hurt anything.  I noticed that I
> have it installed likely for the same reason, and it isn't like it
> will start running on its own. But, I'm not sure yet whether you can
> avoid it.
> 


-- 
Alan McKinnon
alan.mckin...@gmail.com

Re: [gentoo-user] Portage spokes again...

[Rich Freeman]

On Wed, Dec 21, 2016 at 2:46 PM, Rich Freeman  wrote:
> On Wed, Dec 21, 2016 at 2:20 PM,   wrote:
>
>> The following USE changes are necessary to proceed:
>>  (see "package.use" in the portage(5) man page for more details)
>> # required by kde-plasma/kwin-5.8.3::gentoo
>> # required by kde-plasma/plasma-workspace-5.8.3-r4::gentoo
>> # required by net-p2p/ktorrent-5.0.1::gentoo[shutdown]
>> # required by @selected
>> # required by @world (argument)
>>>=media-libs/mesa-12.0.1 wayland
>
>
> I suggest ignoring this for the moment and see if the info above
> resolves your systemd issues.  I'm not sure why kwin has the
> dependency that it does, but it looks to me like it is set up as a
> hard dependency that you can't avoid without modifying the ebuild.
> I'll see if I can figure out more.  The changes above should at least
> get rid of whatever is pulling in systemd.
>
> Installing wayland shouldn't actually hurt anything.  I noticed that I
> have it installed likely for the same reason, and it isn't like it
> will start running on its own. But, I'm not sure yet whether you can
> avoid it.
>

Well, I should have just waited to reply, but here is the issue:
https://mail.kde.org/pipermail/release-team/2015-July/008725.html

kwin does in fact have a non-conditional dependency on wayland, so you
need to install it.  It won't do anything if you don't run it, but it
is not possible to build kwin without wayland support.  Judging by the
claim in the email that it used to take 100 conditionals in the source
to make it optional, I doubt anybody in Gentoo will be patching this
anytime soon.  I guess you could always fork it if you wanted to.

So, sorry, not what you wanted to hear, and not really what I care to
hear either since I don't use wayland, but at least it doesn't need to
be running in this case.  I wouldn't be surprised if that changes in
the future, but everybody knows that xorg is on borrowed time right
now.

Well, if nothing else at least this splits the thread so that you can
reply to the systemd and the wayland issues separately...

-- 
Rich

Re: [gentoo-user] Portage spokes again...

[Rich Freeman]

On Wed, Dec 21, 2016 at 2:20 PM,   wrote:
>
> emerge -t --update --newuse --deep --with-bdeps=y --tree --keep-going 
> --backtrack=30 --exclude media-video/nvidia-settings --exclude 
> app-misc/screen --exclude app-misc/ytree --exclude dev-python/sip --exclude 
> app-shells/bash @world -v
>
> These are the packages that would be merged, in reverse order:
>
> Calculating dependencies... done!
> [ebuild U ~] sys-apps/openrc-0.23::gentoo [0.22.4::gentoo] USE="ncurses 
> netifrc pam unicode -audit -debug -newnet (-prefix) (-selinux) -static-libs 
> -tools" 206 KiB

Hmm, do you have openrc in accept_keywords or something?  You look
like you're using stable keywords in general, but openrc is pulling in
an unstable version.  I suspect this is the root of your problem.

> [nomerge   ] sys-apps/openrc-0.23::gentoo [0.22.4::gentoo] USE="ncurses 
> netifrc pam unicode -audit -debug -newnet (-prefix) (-selinux) -static-libs 
> -tools"
> [ebuild  N~]  virtual/tmpfiles-0::gentoo  0 KiB
> [nomerge   ] virtual/tmpfiles-0::gentoo
> [nomerge   ]  sys-apps/systemd-226-r2:0/2::gentoo  USE="acl kdbus kmod 
> lz4 pam seccomp ssl (-apparmor) -audit -build -cryptsetup -curl -elfutils 
> -gcrypt -gnuefi -http -idn -importd -lzma -nat -policykit -qrcode (-selinux) 
> -sysv-utils {-test} -vanilla -xkb" ABI_X86="(64) -32 (-x32)"

So, openrc-0.23 is pulling in tmpfiles, which is pulling in systemd.
Well, there you go, just unmerge openrc and you won't have it pulling
in systemd any longer.

JUST KIDDING!!!  Don't do that...

But, the first sentence is accurate.  The problem is that you've
unmasked openrc 0.23, but you probably haven't unmasked
sys-apps/opentmpfiles.

So, the solution is one of two things:

Remove openrc from package.keywords and stay on 0.22.4.  I'm not sure
why you were running unstable openrc in the first place, so I'm not
sure if this solution is acceptable to you.

Or, add opentmpfiles to package.keywords so that it can be installed.
Then portage should install that instead of systemd.  The reason it is
trying to pull in systemd is that opentmpfiles is masked, and systemd
is stable, so it is going to go with the package that is stable.


In general you're running into this issue because you're running mixed
keywords.  I do that, but keep in mind that this configuration is not
tested for consistency by our internal QA tools, so you're going to
sometimes run into issues like these.  If you stick with all-stable or
all-testing then you won't run into these kinds of inconsistences.
Or, if you do that QA team that got mentioned in the other thread will
probably have already sent a nasty-gram to the devs involved.  :)


> The following USE changes are necessary to proceed:
>  (see "package.use" in the portage(5) man page for more details)
> # required by kde-plasma/kwin-5.8.3::gentoo
> # required by kde-plasma/plasma-workspace-5.8.3-r4::gentoo
> # required by net-p2p/ktorrent-5.0.1::gentoo[shutdown]
> # required by @selected
> # required by @world (argument)
>>=media-libs/mesa-12.0.1 wayland


I suggest ignoring this for the moment and see if the info above
resolves your systemd issues.  I'm not sure why kwin has the
dependency that it does, but it looks to me like it is set up as a
hard dependency that you can't avoid without modifying the ebuild.
I'll see if I can figure out more.  The changes above should at least
get rid of whatever is pulling in systemd.

Installing wayland shouldn't actually hurt anything.  I noticed that I
have it installed likely for the same reason, and it isn't like it
will start running on its own. But, I'm not sure yet whether you can
avoid it.

-- 
Rich

Re: [gentoo-user] Portage spokes again...

[Alan McKinnon]

On 21/12/2016 21:20, meino.cra...@gmx.de wrote:
> Rich Freeman  [16-12-21 20:12]:
>> On Wed, Dec 21, 2016 at 1:44 PM,   wrote:
>>> Corbin Bird  [16-12-21 17:12]:
>>> The first run of emerge tells me to add the systemd USE flag to dbus.
>>> I did that and ran into to problems I reported.
>>
>> Ok, I think you left that bit out...
>>
>> And this is why it is helpful to understand why portage is doing
>> something before just changing configuration settings.  Adding the
>> systemd USE flag to packages is a really quick way to end up with
>> systemd getting installed.  Generally speaking it shouldn't just
>> happen by default...
>>
>> Can you show the output when you add -t to the emerge command?  I
>> think that will be helpful.  However, I think an earlier poster was on
>> the right track when he pointed out that the tmpfiles virtual requires
>> an unstable version of openrc.  I'm not sure why that was getting
>> pulled in in the first place, and -t should show that.
>>
>>>
>>> emerge: there are no ebuilds built with USE flags to satisfy 
>>> "media-libs/mesa[egl,gbm,gles2?,wayland]".
>>> !!! One of the following packages is required to complete your request:
>>> - media-libs/mesa-11.2.2::gentoo (Change USE: +wayland)
>>> (dependency required by "kde-plasma/kwin-5.8.3::gentoo" [ebuild])
>>> (dependency required by "kde-plasma/plasma-workspace-5.8.3-r4::gentoo" 
>>> [ebuild])
>>> (dependency required by "net-p2p/ktorrent-5.0.1::gentoo[shutdown]" [ebuild])
>>> (dependency required by "@selected" [set])
>>> (dependency required by "@world" [argument])
>>> [1]20322 exit 1 emerge -t --update --newuse --deep --with-bdeps=y 
>>> --tree --keep-going
>>>
>>> What?
>>>
>>> Now wayland shall be installed? IK!
>>> I want my UNIX back!
>>
>> Interesting.  I just noticed that it pulled in wayland for me.  I have
>> no idea why kwin requires wayland support in mesa.  It obviously works
>> fine with xorg.  I might do some looking into that.
>>
>> There isn't really anything non-UNIX about wayland, though I'm not
>> sure I'd be in a rush to use it just yet.  It is just a replacement
>> for xorg (to say the least, it doesn't purport to be a
>> feature-complete replacement and may never be).
>>
>> Your wayland issues and your systemd issues are most likely entirely
>> unrelated...
>>
>> -- 
>> Rich
>>
> Hi Rich,
> 
> to confess everything ... this time
> :)
> 
> The following output is base on setting "-systemd" and "-wayland"
> in make.confs USE flag, "-t" was set also.
> 
> And here the master portage spoke words:
> 
> emerge -t --update --newuse --deep --with-bdeps=y --tree --keep-going 
> --backtrack=30 --exclude media-video/nvidia-settings --exclude 
> app-misc/screen --exclude app-misc/ytree --exclude dev-python/sip --exclude 
> app-shells/bash @world -v
>   
> These are the packages that would be merged, in reverse order:
> 
> Calculating dependencies... done!
...
> [ebuild   R] media-libs/mesa-12.0.1::gentoo  USE="classic dri3 egl 
> gallium gbm llvm nptl udev vaapi vdpau wayland* xvmc -bindist -d3d9 -debug 
> -gles1 -gles2 -opencl -openmax -osmesa -pax_kernel -pic (-selinux) -valgrind 
> -xa" ABI_X86="32 (64) (-x32)" VIDEO_CARDS="(-freedreno) -i915 -i965 -ilo 
> -intel -nouveau -r100 -r200 -r300 -r600 -radeon -radeonsi (-vc4) -vmware" 0 
> KiB

USE=wayland is off by default for mesa, so you have something switching
it on.

grep -r wayland /etc/portage
to find what

...
> [nomerge   ] virtual/tmpfiles-0::gentoo 
> [nomerge   ]  sys-apps/systemd-226-r2:0/2::gentoo  USE="acl kdbus kmod 
> lz4 pam seccomp ssl (-apparmor) -audit -build -cryptsetup -curl -elfutils 
> -gcrypt -gnuefi -http -idn -importd -lzma -nat -policykit -qrcode (-selinux) 
> -sysv-utils {-test} -vanilla -xkb" ABI_X86="(64) -32 (-x32)" 
> [ebuild  N ]   sys-apps/gentoo-systemd-integration-6::gentoo  63 KiB
> [ebuild   R]   sys-apps/dbus-1.10.12::gentoo  USE="X systemd* -debug -doc 
> (-selinux) -static-libs {-test} -user-session" ABI_X86="(64) -32 (-x32)" 0 KiB

USE=systemd is of by default for dbus so yu have something switching it on.

grep -r systemd /etc/portage
to find what

Additionally, virtual/tmpfiles has this:

RDEPEND="
|| (
sys-apps/opentmpfiles
sys-apps/systemd

Because you have systemd on somehow, portage is picking the second
chice. You have the first, so explicitly emerge opentmpfiles.

If both of those grep -r commands return nothing, then your next avenue
is your selected profile must be enabling wayland and systemd somehow.
But I don't see how profile [1] would do that ... so the greps will
likely reveal the true cause



-- 
Alan McKinnon
alan.mckin...@gmail.com

Re: [gentoo-user] Portage spokes again...

[Meino . Cramer]

Rich Freeman  [16-12-21 20:12]:
> On Wed, Dec 21, 2016 at 1:44 PM,   wrote:
> > Corbin Bird  [16-12-21 17:12]:
> > The first run of emerge tells me to add the systemd USE flag to dbus.
> > I did that and ran into to problems I reported.
> 
> Ok, I think you left that bit out...
> 
> And this is why it is helpful to understand why portage is doing
> something before just changing configuration settings.  Adding the
> systemd USE flag to packages is a really quick way to end up with
> systemd getting installed.  Generally speaking it shouldn't just
> happen by default...
> 
> Can you show the output when you add -t to the emerge command?  I
> think that will be helpful.  However, I think an earlier poster was on
> the right track when he pointed out that the tmpfiles virtual requires
> an unstable version of openrc.  I'm not sure why that was getting
> pulled in in the first place, and -t should show that.
> 
> >
> > emerge: there are no ebuilds built with USE flags to satisfy 
> > "media-libs/mesa[egl,gbm,gles2?,wayland]".
> > !!! One of the following packages is required to complete your request:
> > - media-libs/mesa-11.2.2::gentoo (Change USE: +wayland)
> > (dependency required by "kde-plasma/kwin-5.8.3::gentoo" [ebuild])
> > (dependency required by "kde-plasma/plasma-workspace-5.8.3-r4::gentoo" 
> > [ebuild])
> > (dependency required by "net-p2p/ktorrent-5.0.1::gentoo[shutdown]" [ebuild])
> > (dependency required by "@selected" [set])
> > (dependency required by "@world" [argument])
> > [1]20322 exit 1 emerge -t --update --newuse --deep --with-bdeps=y 
> > --tree --keep-going
> >
> > What?
> >
> > Now wayland shall be installed? IK!
> > I want my UNIX back!
> 
> Interesting.  I just noticed that it pulled in wayland for me.  I have
> no idea why kwin requires wayland support in mesa.  It obviously works
> fine with xorg.  I might do some looking into that.
> 
> There isn't really anything non-UNIX about wayland, though I'm not
> sure I'd be in a rush to use it just yet.  It is just a replacement
> for xorg (to say the least, it doesn't purport to be a
> feature-complete replacement and may never be).
> 
> Your wayland issues and your systemd issues are most likely entirely
> unrelated...
> 
> -- 
> Rich
> 
Hi Rich,

to confess everything ... this time
:)

The following output is base on setting "-systemd" and "-wayland"
in make.confs USE flag, "-t" was set also.

And here the master portage spoke words:

emerge -t --update --newuse --deep --with-bdeps=y --tree --keep-going 
--backtrack=30 --exclude media-video/nvidia-settings --exclude app-misc/screen 
--exclude app-misc/ytree --exclude dev-python/sip --exclude app-shells/bash 
@world -v
  
These are the packages that would be merged, in reverse order:

Calculating dependencies... done!
[nomerge   ] sci-geosciences/foxtrotgps-1.2.0::gentoo  USE="-debug" 
[ebuild U  ]  sci-geosciences/gpsd-3.10::gentoo [3.9-r1::gentoo] USE="X cxx 
dbus ipv6 ncurses python shm sockets -bluetooth -debug -latency_timing -ntp 
-qt4 -static% {-test} -udev -usb (-systemd%)" GPSD_PROTOCOLS="aivdm ashtech 
earthmate evermore fv18 garmin garmintxt gpsclock itrax mtk3301 navcom nmea 
ntrip oceanserver oncore rtcm104v2 rtcm104v3 sirf superstar2 tnt tripmate tsip 
ublox%* -fury -geostar -nmea2000 (-ubx%*)" PYTHON_TARGETS="python2_7%*" 1530 KiB
[nomerge   ] media-sound/ardour-5.5:5::gentoo  USE="jack (-altivec) -doc" 
CPU_FLAGS_X86="mmx sse -3dnow" 
[ebuild U  ]  media-libs/slv2-0.6.6-r1::gentoo [0.6.6::gentoo] USE="jack 
-doc" 0 KiB
[nomerge   ] media-video/mplayer-1.2.1::gentoo  USE="X alsa cdio cdparanoia 
cpudetection dvb dvd dvdnav enca encode faac gif iconv ipv6 jack jpeg jpeg2k 
ladspa libass lirc lzo mad mp3 network opengl osdmenu png sdl shm truetype 
unicode v4l vdpau vorbis x264 xscreensaver xv xvmc -a52 -aalib (-altivec) 
(-aqua) -bidi -bl -bluray -bs2b -cddb -debug -dga -directfb -doc -dts -dv -faad 
-fbcon -ftp -ggi -gsm -joystick -libcaca -libmpeg2 -live -md5sum -mng -nas -nut 
-openal -oss -pnm -pulseaudio -pvr -radio -rar -rtc -rtmp -samba (-selinux) 
-speex -tga -theora -toolame -tremor -twolame -vcd (-vidix) -xinerama -xvid 
-yuv4mpeg -zoran" CPU_FLAGS_X86="mmx sse sse2 -3dnow -3dnowext -mmxext -ssse3" 
VIDEO_CARDS="-mga -s3virge -tdfx" 
[ebuild U  ]  dev-libs/libcdio-paranoia-0.93_p1::gentoo 
[0.90_p1-r1::gentoo] USE="cxx -static-libs {-test}" ABI_X86="(64) -32 (-x32)" 
670 KiB
[ebuild U  ] app-text/tesseract-3.04.01::gentoo [3.04.00-r2::gentoo] 
USE="jpeg png scrollview tiff -doc -examples -math% -opencl -osd -static-libs 
-training -webp" L10N="-ar -bg -ca -chr -cs -da -de -el -es -fi -fr -he -hi -hu 
-id -it -ja -ko -lt -lv -nl -no -pl -pt -ro -ru -sk -sl -sr -sv -th -tl -tr -uk 
-vi -zh-CN -zh-TW" 2216 KiB
[ebuild U  ] app-admin/conky-1.10.4::gentoo [1.9.0-r3::gentoo] USE="X 
iconv%* ipv6%* lua-cairo lua-imlib ncurses nvidia portmon 

Re: [gentoo-user] Portage spokes again...

[Rich Freeman]

On Wed, Dec 21, 2016 at 1:44 PM,   wrote:
> Corbin Bird  [16-12-21 17:12]:
> The first run of emerge tells me to add the systemd USE flag to dbus.
> I did that and ran into to problems I reported.

Ok, I think you left that bit out...

And this is why it is helpful to understand why portage is doing
something before just changing configuration settings.  Adding the
systemd USE flag to packages is a really quick way to end up with
systemd getting installed.  Generally speaking it shouldn't just
happen by default...

Can you show the output when you add -t to the emerge command?  I
think that will be helpful.  However, I think an earlier poster was on
the right track when he pointed out that the tmpfiles virtual requires
an unstable version of openrc.  I'm not sure why that was getting
pulled in in the first place, and -t should show that.

>
> emerge: there are no ebuilds built with USE flags to satisfy 
> "media-libs/mesa[egl,gbm,gles2?,wayland]".
> !!! One of the following packages is required to complete your request:
> - media-libs/mesa-11.2.2::gentoo (Change USE: +wayland)
> (dependency required by "kde-plasma/kwin-5.8.3::gentoo" [ebuild])
> (dependency required by "kde-plasma/plasma-workspace-5.8.3-r4::gentoo" 
> [ebuild])
> (dependency required by "net-p2p/ktorrent-5.0.1::gentoo[shutdown]" [ebuild])
> (dependency required by "@selected" [set])
> (dependency required by "@world" [argument])
> [1]20322 exit 1 emerge -t --update --newuse --deep --with-bdeps=y 
> --tree --keep-going
>
> What?
>
> Now wayland shall be installed? IK!
> I want my UNIX back!

Interesting.  I just noticed that it pulled in wayland for me.  I have
no idea why kwin requires wayland support in mesa.  It obviously works
fine with xorg.  I might do some looking into that.

There isn't really anything non-UNIX about wayland, though I'm not
sure I'd be in a rush to use it just yet.  It is just a replacement
for xorg (to say the least, it doesn't purport to be a
feature-complete replacement and may never be).

Your wayland issues and your systemd issues are most likely entirely
unrelated...

-- 
Rich

Re: [gentoo-user] Portage spokes again...

[Meino . Cramer]

Corbin Bird  [16-12-21 17:12]:
> 
> On 12/20/2016 10:25 PM, meino.cra...@gmx.de wrote:
> > Hi,
> >
> > The master portage spakes again.
> > And the novice was *not* enlightened...
> >
> >
> > Total: 17 packages (11 upgrades, 4 new, 1 in new slot, 1 reinstall), Size 
> > of downloads: 25097 KiB
> > Conflict: 4 blocks (4 unsatisfied)
> >
> >  * Error: The above package list contains packages which cannot be
> >  * installed at the same time on the same system.
> >
> >   (sys-fs/udev-225-r1:0/0::gentoo, installed) pulled in by
> > sys-fs/udev required by @selected
> > >=sys-fs/udev-208-r1 required by (virtual/udev-215:0/0::gentoo, 
> > installed)
> > 
> > >=sys-fs/udev-208-r1:0/0[abi_x86_32(-)?,abi_x86_64(-)?,abi_x86_x32(-)?,abi_mips_n32(-)?,abi_mips_n64(-)?,abi_mips_o32(-)?,abi_ppc_32(-)?,abi_ppc_64(-)?,abi_s390_32(-)?,abi_s390_64(-)?,static-libs?]
> >  (>=sys-fs/udev-208-r1:0/0[abi_x86_32(-),abi_x86_64(-)]) required by 
> > (virtual/libudev-215-r1:0/1::gentoo, installed)
> >
> >   (sys-apps/systemd-226-r2:0/2::gentoo, ebuild scheduled for merge) pulled 
> > in by
> > >=sys-apps/systemd-207 required by 
> > (sys-apps/gentoo-systemd-integration-6:0/0::gentoo, ebuild scheduled for 
> > merge)
> > sys-apps/systemd required by (virtual/tmpfiles-0:0/0::gentoo, ebuild 
> > scheduled for merge)
> > sys-apps/systemd:0= required by (sys-apps/dbus-1.10.12:0/0::gentoo, 
> > ebuild scheduled for merge)
> >
> >
> > For more information about Blocked Packages, please refer to the following
> > section of the Gentoo Linux x86 Handbook (architecture is irrelevant):
> >
> >
> > I have no systemd installed...my Linux is running good ole openrc...
> > Why all these systemd blockers?
> >
> > Confused...
> > Cheers
> > Meino
> >
> >
> >
> >
> Three things to try ...
> In "make.conf" list "-systemd" under USE ( as a Global USE flag ).
> And emerge "sys-fs/eudev", as a replacement for "sys-fs/udev".
> And last but not least, check "eselect profile list", to make sure your
> not set to a systemd required profile.
> 
> The "sys-fs/eudev" package is the Gentoo fork of "sys-fs/udev" for
> people who don't want systemd.
> No systemd dependencies.
> 
> I am running OpenRC, eudev, with NO systemd or PulseAudio. Xfce v4.xx
> desktop system / works fine.
> 
> Hope this helps.
> 

Hi Corbin,

h
The first run of emerge tells me to add the systemd USE flag to dbus.
I did that and ran into to problems I reported.
Then I removed that one and added -systemd to make.confs USE, which
in general seems to be a good idea per se.

As you suggested I listed my profiles and got this:
  [1]   default/linux/amd64/13.0 *
  [2]   default/linux/amd64/13.0/selinux
  [3]   default/linux/amd64/13.0/desktop
  [4]   default/linux/amd64/13.0/desktop/gnome
  [5]   default/linux/amd64/13.0/desktop/gnome/systemd
  [6]   default/linux/amd64/13.0/desktop/kde
  [7]   default/linux/amd64/13.0/desktop/kde/systemd
  [8]   default/linux/amd64/13.0/desktop/plasma
  [9]   default/linux/amd64/13.0/desktop/plasma/systemd
  [10]  default/linux/amd64/13.0/developer
  [11]  default/linux/amd64/13.0/no-multilib
  [12]  default/linux/amd64/13.0/systemd
  [13]  default/linux/amd64/13.0/x32
  [14]  hardened/linux/amd64
  [15]  hardened/linux/amd64/selinux
  [16]  hardened/linux/amd64/no-multilib
  [17]  hardened/linux/amd64/no-multilib/selinux
  [18]  hardened/linux/amd64/x32
  [19]  hardened/linux/musl/amd64
  [20]  hardened/linux/musl/amd64/x32
  [21]  default/linux/uclibc/amd64
  [22]  hardened/linux/uclibc/amd64

which looks a little weird to me, since [1] seems to be a more
"not specialized" choice (sorry, no native speaker) ... if 
not a wrong one. 
I want a desktop PC (running openbox...I dont like
session manager and desktops a such. I like window
based commandlines ;), wihout systemd, with openrc.

If I eix-sync/emerge that configuration I get this:
Total: 57 packages (17 upgrades, 34 new, 3 in new slots, 3 reinstalls, 1 
uninstall), Size of downloads: 128467 KiB
Conflict: 6 blocks (5 unsatisfied)

 * Error: The above package list contains packages which cannot be
 * installed at the same time on the same system.

  (net-libs/libktorrent-2.0.1:5/5::gentoo, ebuild scheduled for merge) pulled 
in by
=net-libs/libktorrent-2.0.1:5 required by 
(net-p2p/ktorrent-5.0.1:5/5::gentoo, ebuild scheduled for merge)

  (sys-fs/udev-225-r1:0/0::gentoo, installed) pulled in by
sys-fs/udev required by @selected
>=sys-fs/udev-208-r1 required by (virtual/udev-215:0/0::gentoo, installed)

>=sys-fs/udev-208-r1:0/0[abi_x86_32(-)?,abi_x86_64(-)?,abi_x86_x32(-)?,abi_mips_n32(-)?,abi_mips_n64(-)?,abi_mips_o32(-)?,abi_ppc_32(-)?,abi_ppc_64(-)?,abi_s390_32(-)?,abi_s390_64(-)?,static-libs?]
 (>=sys-fs/udev-208-r1:0/0[abi_x86_32(-),abi_x86_64(-)]) required by 
(virtual/libudev-215-r1:0/1::gentoo, installed)

  (net-libs/libktorrent-1.3.1:4/4::gentoo, installed) pulled in by
net-libs/libktorrent:4 required by @selected

  

Re: [gentoo-user] Portage spokes again...

[Neil Bothwick]

On Wed, 21 Dec 2016 07:53:33 -0600, Corbin Bird wrote:

> The ability to separate "udev" code from "systemd" code is going away
> very soon.
> ( by design, on purpose, etc. )
> So if you want to run "udev" ... you going to be running "systemd". No
> choice.
> ( PulseAudio is also being merged into systemd. Think about it. )

Do you have a URL giving a timeline for these changes?


-- 
Neil Bothwick

Give a man a fish and you feed him for a day;
Teach him to use the Net and he won't bother you for weeks.


pgpSOwA5jDUtw.pgp
Description: OpenPGP digital signature

Re: [gentoo-user] Portage spokes again...

[Rich Freeman]

On Wed, Dec 21, 2016 at 8:53 AM, Corbin Bird  wrote:
>
> On 12/21/2016 06:59 AM, Matthias Hanft wrote:
>> Corbin Bird wrote:
>>> The "sys-fs/eudev" package is the Gentoo fork of "sys-fs/udev" for
>>> people who don't want systemd.
>> Ehm... I still use "sys-fs/udev" (not eudev) without systemd.
>> No problems so far. Do I have to worry?
>>
>
> It is currently part of the systemd code base. ( It was merged in some
> time back. )
> The ability to separate "udev" code from "systemd" code is going away
> very soon.

People have been saying that for years.  Maybe it will happen some
day, maybe it won't.

The sys-fs/udev package only works without systemd.  It is the
upstream udev implementation.

> So if you want to run "udev" ... you going to be running "systemd". No
> choice.

If that ever happens the udev package will go away.  Its only purpose
is for running udev without systemd.

By all means make an informed decision about whether you want to run
udev or eudev.  However, the udev package will never require systemd
to be installed.

-- 
Rich

Re: [gentoo-user] Portage spokes again...

[Corbin Bird]

On 12/21/2016 06:59 AM, Matthias Hanft wrote:
> Corbin Bird wrote:
>> The "sys-fs/eudev" package is the Gentoo fork of "sys-fs/udev" for
>> people who don't want systemd.
> Ehm... I still use "sys-fs/udev" (not eudev) without systemd.
> No problems so far. Do I have to worry?
>
> -Matt
>
>

It is currently part of the systemd code base. ( It was merged in some
time back. )
The ability to separate "udev" code from "systemd" code is going away
very soon.
( by design, on purpose, etc. )
So if you want to run "udev" ... you going to be running "systemd". No
choice.
( PulseAudio is also being merged into systemd. Think about it. )

I hope that Gentoo can keep the eudev fork going.

Re: [gentoo-user] Portage spokes again...

[Rich Freeman]

On Wed, Dec 21, 2016 at 7:59 AM, Matthias Hanft  wrote:
> Corbin Bird wrote:
>>
>> The "sys-fs/eudev" package is the Gentoo fork of "sys-fs/udev" for
>> people who don't want systemd.
>
> Ehm... I still use "sys-fs/udev" (not eudev) without systemd.
> No problems so far. Do I have to worry?
>

Nope.  Standalone udev is only intended to be installed on non-systemd
systems.  udev vs eudev have their pros and cons, but requiring
systemd to be installed isn't among them.

To the original poster:  I would start with adding -t and reviewing
your output before changing anything in make.conf.

Yes, adding USE=-systemd probably shouldn't cause any problems, but in
general I think it is better to understand the problem before you
start trying to fix it.

Adding --backtrack=120 or something probably is also a good move, in
case it is a dependency issue that portage can figure out on its own.
In general increasing --backtrack does not cause any problems, it just
makes portage work more slowly.

My guess is that you have some package installed that now wants to
start pulling in systemd, but -t should identify what is going on and
we can dispense with the hand-waving.

-- 
Rich

Re: [gentoo-user] Portage spokes again...

[Matthias Hanft]

Corbin Bird wrote:
> 
> The "sys-fs/eudev" package is the Gentoo fork of "sys-fs/udev" for
> people who don't want systemd.

Ehm... I still use "sys-fs/udev" (not eudev) without systemd.
No problems so far. Do I have to worry?

-Matt

Re: [gentoo-user] Portage spokes again...

[Corbin Bird]

On 12/20/2016 10:25 PM, meino.cra...@gmx.de wrote:
> Hi,
>
> The master portage spakes again.
> And the novice was *not* enlightened...
>
>
> Total: 17 packages (11 upgrades, 4 new, 1 in new slot, 1 reinstall), Size of 
> downloads: 25097 KiB
> Conflict: 4 blocks (4 unsatisfied)
>
>  * Error: The above package list contains packages which cannot be
>  * installed at the same time on the same system.
>
>   (sys-fs/udev-225-r1:0/0::gentoo, installed) pulled in by
> sys-fs/udev required by @selected
> >=sys-fs/udev-208-r1 required by (virtual/udev-215:0/0::gentoo, installed)
> 
> >=sys-fs/udev-208-r1:0/0[abi_x86_32(-)?,abi_x86_64(-)?,abi_x86_x32(-)?,abi_mips_n32(-)?,abi_mips_n64(-)?,abi_mips_o32(-)?,abi_ppc_32(-)?,abi_ppc_64(-)?,abi_s390_32(-)?,abi_s390_64(-)?,static-libs?]
>  (>=sys-fs/udev-208-r1:0/0[abi_x86_32(-),abi_x86_64(-)]) required by 
> (virtual/libudev-215-r1:0/1::gentoo, installed)
>
>   (sys-apps/systemd-226-r2:0/2::gentoo, ebuild scheduled for merge) pulled in 
> by
> >=sys-apps/systemd-207 required by 
> (sys-apps/gentoo-systemd-integration-6:0/0::gentoo, ebuild scheduled for 
> merge)
> sys-apps/systemd required by (virtual/tmpfiles-0:0/0::gentoo, ebuild 
> scheduled for merge)
> sys-apps/systemd:0= required by (sys-apps/dbus-1.10.12:0/0::gentoo, 
> ebuild scheduled for merge)
>
>
> For more information about Blocked Packages, please refer to the following
> section of the Gentoo Linux x86 Handbook (architecture is irrelevant):
>
>
> I have no systemd installed...my Linux is running good ole openrc...
> Why all these systemd blockers?
>
> Confused...
> Cheers
> Meino
>
>
>
>
Three things to try ...
In "make.conf" list "-systemd" under USE ( as a Global USE flag ).
And emerge "sys-fs/eudev", as a replacement for "sys-fs/udev".
And last but not least, check "eselect profile list", to make sure your
not set to a systemd required profile.

The "sys-fs/eudev" package is the Gentoo fork of "sys-fs/udev" for
people who don't want systemd.
No systemd dependencies.

I am running OpenRC, eudev, with NO systemd or PulseAudio. Xfce v4.xx
desktop system / works fine.

Hope this helps.

Re: [gentoo-user] Portage spokes again...

[Neil Bothwick]

On Wed, 21 Dec 2016 05:25:20 +0100, meino.cra...@gmx.de wrote:

> I have no systemd installed...my Linux is running good ole openrc...
> Why all these systemd blockers?

I have just updated a couple of openrc systems and there was no attempt
to pull in the spawn of the devil[tm] - I'm fairly sure this is a USE
flag setting somewhere.


-- 
Neil Bothwick

Guillotine operator wanted. Chance to get ahead.


pgpu8auwOUoKM.pgp
Description: OpenPGP digital signature

Re: [gentoo-user] Portage spokes again...

[Neil Bothwick]

On Wed, 21 Dec 2016 02:41:15 -0500, Philip Webb wrote:

> 161221 Walter Dnes wrote:
> > On Wed, Dec 21, 2016 at 05:25:20AM +0100, meino.cra...@gmx.de wrote  
> >>  sys-apps/systemd:0= required by (sys-apps/dbus-1.10.12:0/0::gentoo,
> >> ebuild scheduled for merge) I have no systemd installed...my Linux
> >> is running good ole openrc... Why all these systemd blockers?  
> > I wonder if systemd is a default USE flag for a package somewhere.
> > Try adding " -systemd " to USE in make.conf to explicitly disable it,
> > and re-run the emerge.  
> 
> 'dbus' has a 'systemd' USE flag, wh looks as if it's the default :

The systemd USE flag is not forced on in any of the dbus ebuilds in the
tree. As Dale said, add the --tree option, then post the full output not
just the headlines if you are still unsure.
 
>   root:501 ~> eix ^dbus$
>[I] sys-apps/dbus
> Available versions:  1.8.16 ~1.8.22 1.10.8-r1^t 1.10.12^t
> ~1.10.14^t {X debug doc selinux static-libs systemd test user-session
> ABI_MIPS="n32 n64 o32" ABI_PPC="32 64" ABI_S390="32 64" ABI_X86="32 64
> x32"} Installed versions:  1.10.12^t([2016-10-23 05:47:09])(X -debug
> -doc -selinux -static-libs -systemd -test -user-session ABI_MIPS="-n32
> -n64 -o32" ABI_PPC="-32 -64" ABI_S390="-32 -64" ABI_X86="64 -32 -x32")
> 
> I have '-*' in  make.conf , so I'm protected (smile).

You know my feeling on the USE="-*" time bomb, but I would explicitly
state USE="-systemd" on an openrc system


-- 
Neil Bothwick

The geek shall inherit the earth.


pgpmfU3GDy559.pgp
Description: OpenPGP digital signature

Re: [gentoo-user] Portage spokes again...

[Philip Webb]

161221 Walter Dnes wrote:
> On Wed, Dec 21, 2016 at 05:25:20AM +0100, meino.cra...@gmx.de wrote
>>  sys-apps/systemd:0= required by (sys-apps/dbus-1.10.12:0/0::gentoo, ebuild 
>> scheduled for merge)
>> I have no systemd installed...my Linux is running good ole openrc...
>> Why all these systemd blockers?
> I wonder if systemd is a default USE flag for a package somewhere.
> Try adding " -systemd " to USE in make.conf to explicitly disable it,
> and re-run the emerge.

'dbus' has a 'systemd' USE flag, wh looks as if it's the default :

  root:501 ~> eix ^dbus$
   [I] sys-apps/dbus
Available versions:  1.8.16 ~1.8.22 1.10.8-r1^t 1.10.12^t ~1.10.14^t {X 
debug doc selinux static-libs systemd test user-session ABI_MIPS="n32 n64 o32" 
ABI_PPC="32 64" ABI_S390="32 64" ABI_X86="32 64 x32"}
   Installed versions:  1.10.12^t([2016-10-23 05:47:09])(X -debug -doc -selinux 
-static-libs -systemd -test -user-session ABI_MIPS="-n32 -n64 -o32" 
ABI_PPC="-32 -64" ABI_S390="-32 -64" ABI_X86="64 -32 -x32")

I have '-*' in  make.conf , so I'm protected (smile).

-- 
,,
SUPPORT ___//___,   Philip Webb
ELECTRIC   /] [] [] [] [] []|   Cities Centre, University of Toronto
TRANSIT`-O--O---'   purslowatchassdotutorontodotca

Re: [gentoo-user] Portage spokes again...

[Walter Dnes]

On Wed, Dec 21, 2016 at 05:25:20AM +0100, meino.cra...@gmx.de wrote

> sys-apps/systemd:0= required by (sys-apps/dbus-1.10.12:0/0::gentoo, 
> ebuild scheduled for merge)
> 
> 
> For more information about Blocked Packages, please refer to the following
> section of the Gentoo Linux x86 Handbook (architecture is irrelevant):
> 
> 
> I have no systemd installed...my Linux is running good ole openrc...
> Why all these systemd blockers?

  I wonder if systemd is a default USE flag for a package somewhere.
Try adding " -systemd " to USE in make.conf to explicitly disable it,
and re-run the emerge.

-- 
Walter Dnes 
I don't run "desktop environments"; I run useful applications

Re: [gentoo-user] Portage spokes again...

[Dale]

meino.cra...@gmx.de wrote:
> Hi,
>
> The master portage spakes again.
> And the novice was *not* enlightened...
>
>
> Total: 17 packages (11 upgrades, 4 new, 1 in new slot, 1 reinstall), Size of 
> downloads: 25097 KiB
> Conflict: 4 blocks (4 unsatisfied)
>
>  * Error: The above package list contains packages which cannot be
>  * installed at the same time on the same system.
>
>   (sys-fs/udev-225-r1:0/0::gentoo, installed) pulled in by
> sys-fs/udev required by @selected
> >=sys-fs/udev-208-r1 required by (virtual/udev-215:0/0::gentoo, installed)
> 
> >=sys-fs/udev-208-r1:0/0[abi_x86_32(-)?,abi_x86_64(-)?,abi_x86_x32(-)?,abi_mips_n32(-)?,abi_mips_n64(-)?,abi_mips_o32(-)?,abi_ppc_32(-)?,abi_ppc_64(-)?,abi_s390_32(-)?,abi_s390_64(-)?,static-libs?]
>  (>=sys-fs/udev-208-r1:0/0[abi_x86_32(-),abi_x86_64(-)]) required by 
> (virtual/libudev-215-r1:0/1::gentoo, installed)
>
>   (sys-apps/systemd-226-r2:0/2::gentoo, ebuild scheduled for merge) pulled in 
> by
> >=sys-apps/systemd-207 required by 
> (sys-apps/gentoo-systemd-integration-6:0/0::gentoo, ebuild scheduled for 
> merge)
> sys-apps/systemd required by (virtual/tmpfiles-0:0/0::gentoo, ebuild 
> scheduled for merge)
> sys-apps/systemd:0= required by (sys-apps/dbus-1.10.12:0/0::gentoo, 
> ebuild scheduled for merge)
>
>
> For more information about Blocked Packages, please refer to the following
> section of the Gentoo Linux x86 Handbook (architecture is irrelevant):
>
>
> I have no systemd installed...my Linux is running good ole openrc...
> Why all these systemd blockers?
>
> Confused...
> Cheers
> Meino
>

When I run into this sort of thing, I add the -t option.  When it spits
out the list then, it shows what is pulling in what.  For some reason I
can't quite put a finger on, it looks like a USE flag is starting this. 
If it is saying why that is, I'm not consciously seeing it.  At the
moment, I do sort of have PVC pipe on the brain.  Woke up to a plumbing
problem.  Having a yard full of water was my first clue.  It hasn't
rained that recently, although it sure did look like it.  Actually, my
first thought was a flood.   :/  I dread the water bill for this one. 

Hope that -t will shed some light on it. 

Dale

:-)  :-) 

P. S.  I ran into a blocker the other day.  It seems emerge has a nifty
new option.  It is --verbose-conflicts .  I haven't quite got around to
peeking into the man page to see what it does just yet.  It just
mentions that it should spit out more info.  Naturally, you still need a
decoder.  lol