Re: [gentoo-user] EAPI packages

[Rich Freeman]

On Sat, Aug 13, 2016 at 10:08 AM, hw  wrote:
>
> I infrequently update Gentoo because I´m *always* running into problems
> like this.  'Infrequently' means about every 3 months at home, and not
> since, IIRC, 2015-02 here at work.  The last update at home got stalled
> because perl cannot be updated, and I haven´t had the time to look into
> that to finish it.

You're probably always running into problems like this because you
infrequently update Gentoo.

If you ran it every day you'd probably only run into issues every
couple of months, and when you did you'd have it immediately narrowed
down to a few packages since that is all that has changed.

>
> If you say that you need to update more frequently than every 3 months
> for not to have problems with the update process itself, I can only
> conclude that Gentoo is entirely unsuited for servers --- and for home
> use as well other than for test machines perhaps.
>

If you're looking for a distro designed to just work with no hands-on,
then you should probably look elsewhere.

Put it another way, why are you using Gentoo instead of Debian or
CentOS in the first place?

Gentoo is useful when you want to mess with the configuration of the
distro itself, not when you just want to throw a few files in
/var/www/htdocs and be done with it.

Gentoo can be made to work rather well on servers, but you have to
know what you're doing.  You can't just run emerge -u world on a
production server that hasn't been touched in a year and expect to
work.  However, you certainly could set up your own local repository,
pull in updates as needed (certainly including frequent security
updates), build binary packages and deploy to your test environment,
make sure everything is good, and then deploy those binary packages to
your production servers. You can accomplish a lot of things that way
that you couldn't accomplish with CentOS or Debian.

However, if all you want is the same binaries Debian already gives
you, then just run Debian.  It isn't like apache runs better just
because you compiled it yourself.  Gentoo is about tweaking things.
And if you're going to tweak things in an enterprise environment then
you need to be doing QA.

If you really want to be deploying updates into production without any
testing then you ought to stick with the likes of CentOS/RHEL.  That's
basically their entire value-add.  Debian stable would be another
option.

-- 
Rich

Re: [gentoo-user] EAPI packages

[Neil Bothwick]

On Sat, 13 Aug 2016 16:08:34 +0200, hw wrote:

>  infrequently update Gentoo because I´m *always* running into problems
> like this.

Every time, or is that just hyperbole?

>  'Infrequently' means about every 3 months at home, and not
> since, IIRC, 2015-02 here at work.  The last update at home got stalled
> because perl cannot be updated, and I haven´t had the time to look into
> that to finish it.

Problems like this are usually resolved quickly. Syncing and updating a
couple of days later would probably have sorted it.
 
> The other reason is that it takes time to update the kernel when a new
> one comes along, so updating like every week is not feasible.  And I
> don´t want to reboot all the time.

You don't need to boot into every new kernel that hits portage. As long
as your current kernel has no security issues you can stick with it.
Plenty of people use Gentoo with only the LTS kernels.
 
> Besides, I don´t want to update too frequently because there may issues
> with new versions of software.

If you use the stable arch, you don't get brand new versions. Packages
are normally a month old before they hit stable.

> If you say that you need to update more frequently than every 3 months
> for not to have problems with the update process itself, I can only
> conclude that Gentoo is entirely unsuited for servers --- and for home
> use as well other than for test machines perhaps.

It may be more a case of Gentoo being unsuited for you, your
expectations and your preferred way of working. In fact, any rolling
release distros sounds like it won't be right for you.


-- 
Neil Bothwick

Failure is not an option...it is integrated with every Microsoft product.


pgpWwiOEZ3v52.pgp
Description: OpenPGP digital signature

Re: [gentoo-user] EAPI packages

[Neil Bothwick]

On Sat, 13 Aug 2016 16:26:21 +0200, hw wrote:

> > If you see this now, your production server hasn't been updated for a
> > long time...  
> 
> About 1.5 years --- not really a long time.

You're kidding, right? You're running a production server without the
last 18 months' worth of security updates?


-- 
Neil Bothwick

Despite the cost of living it remains popular.


pgpkzPnn71WOG.pgp
Description: OpenPGP digital signature

[gentoo-user] kactivitymanagerd endless update loop

[Jörg Schaible]

Hi,

my system is still KDE 4 with the help of kde-sunset. However, I face an 
endless loop installing kactivitymanagerd. The package has been in group 
kde-base for KDE 4 and so it is in kde-sunset. However in central portage 
tree it has been moved to group kde-plasma.

The annoying part is now, that portage is constantly moving with each sync 
the installed kde-base/kactivitymanagerd-4.13.3-r1 into group kde-plasma 
with the result that portage tries to install kde-
base/kactivitymanagerd-4.13.3-r1 as new package. Which fails, because 
portage detects that some install files already exist.

So I have to uninstall kde-plasma/kactivitymanagerd-4.13.3-r1 and let 
portage install again kde-base/kactivitymanagerd-4.13.3-r1 until the next 
sync.

How can I stop portage from moving the package into another group?

Cheers,
Jörg

Re: [gentoo-user] EAPI packages

[james]

On 08/10/2016 06:54 AM, hw wrote:


Hi,

I´m trying to upgrade portage because I´m getting a message that it
needs to be able to work with EAPI 6 packages and can only do EAPI 5.

I´m running into merge conflicts when trying to update portage, and
apparently one of the packages (dev-python/cryptography) I could try
to update first to be able to update portage requires a version of
portage that can handle EAPI 6 packages.

How can upgrade portage?



You might want to read these docs on how to upgrade an old system, in 
steps, not all at once::



http://blog.siphos.be/2013/12/upgrading-old-gentoo-installations/

http://dev.gentoo.org/~swift/snapshots/

https://wiki.gentoo.org/wiki/Upgrading_Gentoo#Upgrading_from_older_systems


Yet another approach.


hth,
James

Re: [gentoo-user] EAPI packages

[james]

On 08/13/2016 10:22 AM, hw wrote:

james schrieb:

On 08/12/2016 07:26 AM, hw wrote:

Michael Orlitzky schrieb:

On 08/10/2016 06:54 AM, hw wrote:


Hi,

I´m trying to upgrade portage because I´m getting a message that it
needs to be able to work with EAPI 6 packages and can only do EAPI 5.

I´m running into merge conflicts when trying to update portage, and
apparently one of the packages (dev-python/cryptography) I could try
to update first to be able to update portage requires a version of
portage that can handle EAPI 6 packages.



Try the other suggestions first -- but as a last resort -- you can
always grab a new stage3 that should contain an updated version of
portage and simply overwrite the portage files on your machine. A
quickpkg from another Gentoo machine (or the liveCD?) would also work.




I´m trying to update a production server here.  If I overwrite the whole
system, who knows what might break.  I can take it down for a few
hours in the evening unless I want to work over night, which is not
really an option.

There must be a way to update a Gentoo installation without breaking it.
As wonderful as it otherwise is, updating Gentoo is always a nightmare
which
makes me very seriously consider not to use it anymore.  Updating
needs to
be easy and flawless and not something you always run into weird issues
with.


When I run gentoo as a critical server, I always have a second,
redundant system pretty much identical, on stanby. I upgrade the
stanby first and run it a few days, then the production system. It
makes reliability extraordinarily high. But, the again, I do a version
of the
same thing with all critical systems, or I do not work on them.


This isn´t really an option because the problem is with the updating
itself, not with something not working after the update has been
performed.


If you have an identical, second system, then you can test whatever you 
want on trying to complete your upgrade. Get the second system up and 
running. Disconnect the ethernet on one and upgrade the other. If you 
fail, then just switch the ethernet cable. Sometimes you can just 
reassign the ethernet on one, so you can ssh into it and look around, 
while working on the other. (2) indentical systems allow you to work on 
one and keep the other stable, until the upgrade is finished.





Granted,
as  successful consultant, I have that luxury.


It´s time consuming ...


Did they recently make a new liveDVD?


A few months ago.

https://wiki.gentoo.org/wiki/Project:RelEng/LiveDVD/20160514


Cool, the old one was really getting old.



Perhaps a better solution is to make a stage-4, of your current gentoo
(production) system, verify that the stage-4 works by using it to
install a similar system, test and deploy. And then hack or fix the
production system, during the daytime, at your leisure?

Stage-4 gentoo systems have been around a long time. Documentation
varies and most have their own 'home spun' approach to stage-4
replicant systems, backups etc etc.


It might be a way to try and see if upgrading from older states step by
step until the installation is current would work.  But how do I do that?



In normal times, you could just make a stage 4. It's like a complete 
backup that installs. Like most other similar approaches, I always test 
them out to ensure they install and populate as needed. If you google, 
for gentoo : stage-4 you'll find lots of examples with slightly 
different steps.


Here's an old one, translated::

http://translate.google.com/translate?prev=/language_tools=http%3A%2F%2Fgentoo-wiki.gentoo.ru%2Fwiki%2FStage4

There are better stage-4 guides, so just google for them::


http://www.tutorials.chymera.eu/blog/2014/05/18/mkstage4-stage4-tarballs-made-easy/

https://github.com/TheChymera/mkstage4/blob/master/README.md

http://gentoo-en.vfose.ru/wiki/Custom_Stage4

http://gentoo-en.vfose.ru/wiki/Custom_Stage4#Installing_from_Stage4


Exercise some caution here. This is something that should be done and 
tested before you get in 'hot water'. Still, if you can duplicate what 
you have working (and test it) then you can experiment on the second
indentical server, with out fear of corrupting the only one you have 
working.


How you proceed is up to you. so be *careful*!!!


Considering how much time and effort it might take and that the update
problems aren´t going to go away, I have to wonder whether it´s better to
install Debian or Centos on another machine and to migrate the services.
Doing so would allow to make some improvements and to consolidate several
physical machines into one.


Either way, you should back up your data /etc/ /var/lib/portage/world 
and any other info files you have or have modified, regardless of which 
OS you end up running on. Think about all the mods and installs and 
critical software you have customized on the system (iptables?).

Back all of that up too.



Either way, it sucks.


System admin requires routine attention to systems, including backups 
and a 

Re: [gentoo-user] Update blocked by kdebase-startkde:4

[Robin Atwood]

On Saturday 13 August 2016, Peter Humphrey wrote:
> On Saturday 13 Aug 2016 20:56:50 Robin Atwood wrote:
> > And the next problem:
> > 
> > !!! All ebuilds that could satisfy
> > "kde-plasma/plasma-workspace-wallpapers:5" have been masked.
> > !!! One of the following masked packages is required to complete your
> > request: - kde-plasma/plasma-workspace-wallpapers-5.7.3::gentoo (masked
> > by: package.mask, ~amd64 keyword)
> > - kde-plasma/plasma-workspace-wallpapers-5.6.5::gentoo (masked by:
> > package.mask)
> > 
> > (dependency required by "kde-base/kdebase-startkde-4.11.22-
> > r2::gentoo[wallpapers]" [installed])
> > (dependency required by "@selected" [set])
> > (dependency required by "@world" [argument])
> > 
> > Why does kdebase-startkde:4 want plasma-workspace-wallpapers:5? has
> > anyone solved this yet?
> 
> I don't know, but the ebuild calls version 5 explicitly.
> 
> What happens if you add USE=-wallpapers to startkde in package.use?

I wondered about that but thought I might end up with no wallpapers. :(

Robin

-- 
--
Robin Atwood.

"Ship me somewheres east of Suez, where the best is like the worst,
 Where there ain't no Ten Commandments an' a man can raise a thirst"
 from "Mandalay" by Rudyard Kipling
--









-- 
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.

Re: [gentoo-user] Update blocked by kdebase-startkde:4

[Daniel Frey]

On 08/13/2016 06:56 AM, Robin Atwood wrote:
> 
> Why does kdebase-startkde:4 want plasma-workspace-wallpapers:5? has
> anyone solved this yet?
> 
>  
> 
> Thanks
> 
> Robin
> 

Somewhere in this thread they mentioned they're cleaning up old ebuilds,
so kde4 is requiring all sorts of kde5 ebuilds now.

You can try using the kde-sunset overlay for old kde4 builds. They've
been pretty good about moving stuff in there.

Dan

Re: [gentoo-user] EAPI packages

[Andreas K. Hüttel]

Am Samstag, 13. August 2016, 16:26:21 schrieb hw:
> 
> Interesting idea :)  I´d be afraid that this version of portage might
> find files of the regular installation and get confused and kill the
> kittens ...

Well this is essentially how portage team (to my knowlegde) tests git HEAD 
version of portage and its development (have a git checkout of portage code 
and run it from there).

I've used the method a few times, but mainly to test repoman.

-- 
Andreas K. Hüttel
Gentoo Linux developer (council, perl, libreoffice)
dilfri...@gentoo.org
http://www.akhuettel.de/

Re: [gentoo-user] Update blocked by kdebase-startkde:4

[Peter Humphrey]

On Saturday 13 Aug 2016 20:56:50 Robin Atwood wrote:

> And the next problem:
> 
> !!! All ebuilds that could satisfy
> "kde-plasma/plasma-workspace-wallpapers:5" have been masked.
> !!! One of the following masked packages is required to complete your
> request: - kde-plasma/plasma-workspace-wallpapers-5.7.3::gentoo (masked
> by: package.mask, ~amd64 keyword)
> - kde-plasma/plasma-workspace-wallpapers-5.6.5::gentoo (masked by:
> package.mask)
> 
> (dependency required by "kde-base/kdebase-startkde-4.11.22-
> r2::gentoo[wallpapers]" [installed])
> (dependency required by "@selected" [set])
> (dependency required by "@world" [argument])
> 
> Why does kdebase-startkde:4 want plasma-workspace-wallpapers:5? has anyone
> solved this yet?

I don't know, but the ebuild calls version 5 explicitly.

What happens if you add USE=-wallpapers to startkde in package.use?

-- 
Rgds
Peter

Re: [gentoo-user] EAPI packages

[Peter Humphrey]

On Saturday 13 Aug 2016 16:26:21 hw wrote:
> Andreas K. Hüttel schrieb:
> > If you see this now, your production server hasn't been updated for a
> > long time...
> 
> About 1.5 years --- not really a long time.

Au contraire. In a Gentoo world, this is comparable with the age of the 
universe. And leaving it that long almost guarantees that you'll have 
problems. (I update my system daily, but that's because I don't have 
anything more useful to do with my time.  :)  )

> > As a last resort, you should be able to run a "non-installed" portage
> > version to update your system once. Manually download and unpack a
> > recent portage tarball somewhere temporary and then run as root
> > something like
> > 
> > porto tmp # ./portage-2.3.0/bin/emerge -uDNav world
> > 
> > This can update your system to the newest state, including updating the
> > installed portage. Afterwards you won't need the temporarily unpacked
> > portage anymore.
> > 
> > Disclaimer: I haven't tested this for a while. It may delete your data,
> > kill kittens or turn the sun into a nova. No guarantees made.
> 
> Interesting idea :)  I´d be afraid that this version of portage might
> find files of the regular installation and get confused and kill the
> kittens ...

That's the idea, isn't it? You need it to root out the out-of-date bits and 
substitute new ones. It sounds like a rational scheme to me, especially if 
you quickpkg portage to keep some kittens wrapped up in the warm.

-- 
Rgds
Peter

Re: [gentoo-user] EAPI packages

[hw]

Andreas K. Hüttel schrieb:

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Am Mittwoch, 10. August 2016, 12:54:37 schrieb hw:

Hi,

I´m trying to upgrade portage because I´m getting a message that it
needs to be able to work with EAPI 6 packages and can only do EAPI 5.

I´m running into merge conflicts when trying to update portage, and
apparently one of the packages (dev-python/cryptography) I could try
to update first to be able to update portage requires a version of
portage that can handle EAPI 6 packages.

How can upgrade portage?



If you see this now, your production server hasn't been updated for a long
time...


About 1.5 years --- not really a long time.


As a last resort, you should be able to run a "non-installed" portage version
to update your system once. Manually download and unpack a recent portage
tarball somewhere temporary and then run as root something like

porto tmp # ./portage-2.3.0/bin/emerge -uDNav world

This can update your system to the newest state, including updating the
installed portage. Afterwards you won't need the temporarily unpacked portage
anymore.

Disclaimer: I haven't tested this for a while. It may delete your data, kill
kittens or turn the sun into a nova. No guarantees made.


Interesting idea :)  I´d be afraid that this version of portage might
find files of the regular installation and get confused and kill the
kittens ...

Re: [gentoo-user] EAPI packages

[hw]

james schrieb:

On 08/12/2016 07:26 AM, hw wrote:

Michael Orlitzky schrieb:

On 08/10/2016 06:54 AM, hw wrote:


Hi,

I´m trying to upgrade portage because I´m getting a message that it
needs to be able to work with EAPI 6 packages and can only do EAPI 5.

I´m running into merge conflicts when trying to update portage, and
apparently one of the packages (dev-python/cryptography) I could try
to update first to be able to update portage requires a version of
portage that can handle EAPI 6 packages.



Try the other suggestions first -- but as a last resort -- you can
always grab a new stage3 that should contain an updated version of
portage and simply overwrite the portage files on your machine. A
quickpkg from another Gentoo machine (or the liveCD?) would also work.




I´m trying to update a production server here.  If I overwrite the whole
system, who knows what might break.  I can take it down for a few
hours in the evening unless I want to work over night, which is not
really an option.

There must be a way to update a Gentoo installation without breaking it.
As wonderful as it otherwise is, updating Gentoo is always a nightmare
which
makes me very seriously consider not to use it anymore.  Updating needs to
be easy and flawless and not something you always run into weird issues
with.


When I run gentoo as a critical server, I always have a second, redundant 
system pretty much identical, on stanby. I upgrade the stanby first and run it 
a few days, then the production system. It makes reliability extraordinarily 
high. But, the again, I do a version of the
same thing with all critical systems, or I do not work on them.


This isn´t really an option because the problem is with the updating
itself, not with something not working after the update has been
performed.


Granted,
as  successful consultant, I have that luxury.


It´s time consuming ...


Did they recently make a new liveDVD?


A few months ago.

https://wiki.gentoo.org/wiki/Project:RelEng/LiveDVD/20160514


Cool, the old one was really getting old.



Perhaps a better solution is to make a stage-4, of your current gentoo
(production) system, verify that the stage-4 works by using it to install a 
similar system, test and deploy. And then hack or fix the production system, 
during the daytime, at your leisure?

Stage-4 gentoo systems have been around a long time. Documentation varies and 
most have their own 'home spun' approach to stage-4 replicant systems, backups 
etc etc.


It might be a way to try and see if upgrading from older states step by
step until the installation is current would work.  But how do I do that?

Considering how much time and effort it might take and that the update
problems aren´t going to go away, I have to wonder whether it´s better to
install Debian or Centos on another machine and to migrate the services.
Doing so would allow to make some improvements and to consolidate several
physical machines into one.

Either way, it sucks.

Re: [gentoo-user] EAPI packages

[hw]

Michael Orlitzky schrieb:

On 08/12/2016 08:26 AM, hw wrote:


Try the other suggestions first -- but as a last resort -- you can
always grab a new stage3 that should contain an updated version of
portage and simply overwrite the portage files on your machine. A
quickpkg from another Gentoo machine (or the liveCD?) would also work.



I´m trying to update a production server here.  If I overwrite the whole
system, who knows what might break.  I can take it down for a few
hours in the evening unless I want to work over night, which is not
really an option.



Not the whole system, only portage. It should still be your last resort,
but on the bad-idea scale it's only a 1 or a 2.


And how would I know which of all the files affect only portage and nothing
else, and what about the dependencies of portage?

Re: [gentoo-user] EAPI packages

[hw]

Rich Freeman schrieb:

On Wed, Aug 10, 2016 at 10:45 AM, Michael Orlitzky  wrote:

On 08/10/2016 06:54 AM, hw wrote:


Hi,

I´m trying to upgrade portage because I´m getting a message that it
needs to be able to work with EAPI 6 packages and can only do EAPI 5.

I´m running into merge conflicts when trying to update portage, and
apparently one of the packages (dev-python/cryptography) I could try
to update first to be able to update portage requires a version of
portage that can handle EAPI 6 packages.



Try the other suggestions first -- but as a last resort -- you can
always grab a new stage3 that should contain an updated version of
portage and simply overwrite the portage files on your machine. A
quickpkg from another Gentoo machine (or the liveCD?) would also work.



A cleaner solution would be to just sync a snapshot of the Gentoo repo
from the past.

Pick snapshots every few months and emerge -u @system, and repeat that
until you're caught up.  The only issue is if it needs to download a
patch that is no longer available.

In general Gentoo does not support infrequently updating systems.  You
don't need to update every day, or even every month.  However, when
you're going more than six months at a time without an update you're
almost certain to have problems.


I infrequently update Gentoo because I´m *always* running into problems
like this.  'Infrequently' means about every 3 months at home, and not
since, IIRC, 2015-02 here at work.  The last update at home got stalled
because perl cannot be updated, and I haven´t had the time to look into
that to finish it.

The other reason is that it takes time to update the kernel when a new
one comes along, so updating like every week is not feasible.  And I
don´t want to reboot all the time.

Besides, I don´t want to update too frequently because there may issues
with new versions of software.

If you say that you need to update more frequently than every 3 months
for not to have problems with the update process itself, I can only
conclude that Gentoo is entirely unsuited for servers --- and for home
use as well other than for test machines perhaps.


EAPI6 support was available in stable portage in Jan 2016.  The
version of portage you're running predates the git migration which was
a year ago, but fortunately by not a whole lot more than that.

Here is a guide:
cd /usr
mv portage portage-old  # for safekeeping - you can go
back to rsync later if you want
mkdir portage
cd portage
git clone --no-checkout https://github.com/gentoo/gentoo.git .
git checkout 56bd759df1d0c750a065b8c845e93d5dfa6b549d # Aug 8 2015
emerge -u @system
git checkout 1e65133983f404ea64079df0933dd820619a9b44 # Nov 1 2015
emerge -u @system
git checkout 47b868a553171134807fc949d2b84c2dc31b0477 # Feb 2 2016
emerge -u @system

By now you're into EAPI6 territory.  Hopefully you can get to the
present directly, but I can give you a few more commits if necessary.
I didn't test those out on an old system, so you might still run into
issues.  I won't promise that this won't be a bumpy ride.

When you're done you can swap out portage and portage-old.


Thanks, I'll have to see next week if this is an option.  I might end
up setting another server with Centos or Debian instead, despite I
don´t like either of them.


And try to stay more current with updates...


I would gladly do that if there weren´t always issues when trying to
update a Gentoo installation, and if I had the time to do it.


If you really know what
you're doing you can update ancient systems, but it sounds like you
want something that "just works" and on Gentoo this is not something
that just works.


That machines can be kept up to date without running into weird issues
like I always do with Gentoo is a requirement.  That probably leaves
Debian as the only distribution that could be used when you don´t want
to remain in the past too far as you likely would with Centos :(

That creates a problem because ZFS is somewhat questionable with either,
and I don´t trust btrfs to keep the data save yet.

Re: [gentoo-user] Update blocked by kdebase-startkde:4

[Robin Atwood]

On Friday 15 July 2016, Robin Atwood wrote:
> On Tuesday 12 July 2016, Andrés Becerra Sandoval wrote:
> > 2016-07-09 8:52 GMT-05:00 Robin Atwood :
> > > Attempting to update/world this weekend I get:
> > > 
> > > 
> > > 
> > > 
> > > 
> > > # emerge -uDv @world
> > > 
> > > 
> > > 
> > > These are the packages that would be merged, in order:
> > > 
> > > 
> > > 
> > > Calculating dependencies... done!
> > > 
> > > 
> > > 
> > > !!! All ebuilds that could satisfy "kde-apps/kdebase-runtime-meta:5"
> > > have been masked.
> > > 
> > > !!! One of the following masked packages is required to complete your
> > > request:
> > > 
> > > - kde-apps/kdebase-runtime-meta-16.04.2::gentoo (masked by:
> > > package.mask, ~amd64 keyword)
> > > 
> > > - kde-apps/kdebase-runtime-meta-15.12.3::gentoo (masked by:
> > > package.mask)
> > > 
> > > 
> > > 
> > > (dependency required by "kde-base/kdebase-startkde-4.11.22-r1::gentoo"
> > > [ebuild])
> > > 
> > > (dependency required by "@selected" [set])
> > > 
> > > (dependency required by "@world" [argument])
> > > 
> > > 
> > > 
> > > I have all of KDE:5 masked since I think installing it sounds too
> > > risky. Checking the kdebase-startkde-4.11.22-r1 ebuild it has a
> > > dependency on kde-apps/kdebase-runtime-meta:5. Is this a mistake? Has
> > > anyone found a solution to this?
> > 
> > ​Robin,
> > 
> > My ugly hack on this to keep on kde4 withouth pulling frameworks 5:
> > 
> > 1) use a local overlay
> > 2) locate kactivitymanagerd-4.13.3-r1.ebuild (in
> > /var/db/pkg/kde-plasma/kactivitymanagerd-4.13.3-r1)
> > 3) put the kactivitymanagerd-4.13.3-r1.ebuild into ​
> > /usr/local/portage/kde-plasma/kactivitymanagerd/
> > ​4) add  a ​
> > SLOT="5"
> > ​ line to the ebuild
> > 5) add a unmask ​line
> > =kde-plasma/kactivitymanagerd-4.13.3-r1
> > ​ to /et​c/package.unmask
> > 
> > ​I need 5) because I mask ​all kde-plasma/* packages
> 
> Andrés-
> That did the trick! Thanks very much. Until the next time... :(

And the next problem:

!!! All ebuilds that could satisfy "kde-plasma/plasma-workspace-wallpapers:5" 
have been masked.
!!! One of the following masked packages is required to complete your request:
- kde-plasma/plasma-workspace-wallpapers-5.7.3::gentoo (masked by: 
package.mask, ~amd64 keyword)
- kde-plasma/plasma-workspace-wallpapers-5.6.5::gentoo (masked by: 
package.mask)

(dependency required by "kde-base/kdebase-startkde-4.11.22-
r2::gentoo[wallpapers]" [installed])
(dependency required by "@selected" [set])
(dependency required by "@world" [argument])

Why does kdebase-startkde:4 want plasma-workspace-wallpapers:5? has anyone 
solved this yet?

Thanks
Robin
-- 
--
Robin Atwood.

"Ship me somewheres east of Suez, where the best is like the worst,
 Where there ain't no Ten Commandments an' a man can raise a thirst"
 from "Mandalay" by Rudyard Kipling
--









-- 
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.

Re: [gentoo-user] EAPI packages

[hw]

Fernando Rodriguez schrieb:

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

On 08/12/2016 08:44 AM, Jeroen Mathon wrote:

Is it perhaps an idea to mask the gentoolkit package when updating portage?


Since that version of gentoolkit doesn't depend on a specific version of portage
but does depend on portage with the same python_targets use flags, I think the 
problem
is that you're trying to emerge portage and gentoolkit with different 
python_target_XXX
flags, So just make sure they're the same.


I have removed gentoolkit, and it still fails:

emerge --ask --update --newuse portage
[...]
WARNING: One or more updates/rebuilds have been skipped due to a dependency 
conflict:

sys-apps/portage:0

  (sys-apps/portage-2.2.28:0/0::gentoo, ebuild scheduled for merge) conflicts 
with

sys-apps/portage[python_targets_python2_7(-),python_targets_python3_3(-),-python_single_target_python2_7(-),-python_single_target_python3_3(-)]
 required by (app-admin/webapp-config-1.52-r1:0/0::gentoo, installed)


When I try to remove webapp-config, it says no packages can be removed:


emerge --ask --depclean app-admin/webapp-config

Calculating dependencies... done!
>>> No packages selected for removal by depclean
>>> To see reverse dependencies, use --verbose
Packages installed:   659
Packages in world:85
Packages in system:   44
Required packages:659
Number removed:   0


So try to update it:


emerge --ask --update --newuse app-admin/webapp-config
[...]
These are the packages that would be merged, in order:

Calculating dependencies... done!
[ebuild  N ] sys-apps/install-xattr-0.5
[ebuild  N ] dev-python/packaging-15.3-r2  USE="{-test}" 
PYTHON_TARGETS="python2_7 python3_4 (-pypy) (-pypy3) -python3_3 (-python3_5)"
[ebuild U  ] dev-python/setuptools-18.4 [7.0] PYTHON_TARGETS="python3_4* 
-python3_3* (-python3_5)"
[ebuild  N ] dev-python/certifi-2015.11.20  PYTHON_TARGETS="python2_7 python3_4 
(-pypy) (-pypy3) -python3_3 (-python3_5)"
[ebuild  N ] dev-python/pyxattr-0.5.5  USE="-doc {-test}" 
PYTHON_TARGETS="python2_7 python3_4 (-pypy) -python3_3 (-python3_5)"
[ebuild U  ] sys-apps/portage-2.2.28 [2.2.14] USE="xattr*" 
PYTHON_TARGETS="python3_4* -python3_3* (-python3_5)"
[ebuild U  ] app-admin/webapp-config-1.54-r1 [1.52-r1] 
PYTHON_TARGETS="python3_4%* (-pypy) -python3_3*"

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

dev-python/setuptools:0

  (dev-python/setuptools-18.4:0/0::gentoo, ebuild scheduled for merge) pulled 
in by

dev-python/setuptools[python_targets_pypy(-)?,python_targets_pypy3(-)?,python_targets_python2_7(-)?,python_targets_python3_3(-)?,python_targets_python3_4(-)?,python_targets_python3_5(-)?,-python_single_target_pypy(-),-python_single_target_pypy3(-),-python_single_target_python2_7(-),-python_single_target_python3_3(-),-python_single_target_python3_4(-),-python_single_target_python3_5(-)]
 required by (dev-python/certifi-2015.11.20:0/0::gentoo, ebuild scheduled for 
merge)


dev-python/setuptools[python_targets_pypy(-)?,python_targets_python2_7(-)?,python_targets_python3_3(-)?,python_targets_python3_4(-)?,python_targets_python3_5(-)?,-python_single_target_pypy(-),-python_single_target_python2_7(-),-python_single_target_python3_3(-),-python_single_target_python3_4(-),-python_single_target_python3_5(-)]
 required by (dev-python/pyxattr-0.5.5:0/0::gentoo, ebuild scheduled for merge)


  (dev-python/setuptools-7.0:0/0::gentoo, installed) pulled in by

dev-python/setuptools[python_targets_python2_7(-),python_targets_python3_3(-),-python_single_target_python2_7(-),-python_single_target_python3_3(-),-python_single_target_python3_4(-),-python_single_target_pypy(-)]
 required by (dev-python/cryptography-0.6.1:0/0::gentoo, installed)


dev-python/setuptools[python_targets_pypy(-)?,python_targets_pypy3(-)?,python_targets_python2_7(-)?,python_targets_python3_3(-)?,python_targets_python3_4(-)?,-python_single_target_pypy(-),-python_single_target_pypy3(-),-python_single_target_python2_7(-),-python_single_target_python3_3(-),-python_single_target_python3_4(-)]
 required by (dev-python/chardet-2.2.1:0/0::gentoo, installed)


Now try to update cryptography:


emerge --ask --update --newuse dev-python/cryptography
[...]
!!! All ebuilds that could satisfy 
">=dev-python/cffi-1.4.1:=[python_targets_python2_7(-)?,-python_single_target_python2_7(-),python_targets_python3_3(-)?,-python_single_target_python3_3(-),python_targets_python3_4(-)?,-python_single_target_python3_4(-),python_targets_python3_5(-)?,-python_single_target_python3_5(-)]"
 have been masked.
!!! One of the following masked packages is required to complete your request:
- dev-python/cffi-1.7.0::gentoo (masked by: EAPI 6)
- dev-python/cffi-1.6.0::gentoo (masked by: EAPI 6)
- dev-python/cffi-1.5.2::gentoo (masked by: EAPI 6)

The current version of portage supports EAPI '5'. You must upgrade to a
newer version 

Re: [gentoo-user] EAPI packages

[Andreas K. Hüttel]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Am Mittwoch, 10. August 2016, 12:54:37 schrieb hw:
> Hi,
> 
> I´m trying to upgrade portage because I´m getting a message that it
> needs to be able to work with EAPI 6 packages and can only do EAPI 5.
> 
> I´m running into merge conflicts when trying to update portage, and
> apparently one of the packages (dev-python/cryptography) I could try
> to update first to be able to update portage requires a version of
> portage that can handle EAPI 6 packages.
> 
> How can upgrade portage?
> 

If you see this now, your production server hasn't been updated for a long 
time...

As a last resort, you should be able to run a "non-installed" portage version 
to update your system once. Manually download and unpack a recent portage 
tarball somewhere temporary and then run as root something like 

porto tmp # ./portage-2.3.0/bin/emerge -uDNav world

This can update your system to the newest state, including updating the 
installed portage. Afterwards you won't need the temporarily unpacked portage 
anymore. 

Disclaimer: I haven't tested this for a while. It may delete your data, kill 
kittens or turn the sun into a nova. No guarantees made.

- -- 
Andreas K. Hüttel
Gentoo Linux developer (council, perl, libreoffice)
dilfri...@gentoo.org
http://www.akhuettel.de/
-BEGIN PGP SIGNATURE-
Version: GnuPG v2

iQIcBAEBCgAGBQJXryAhAAoJEHRrah2soMK++mAP/jnoaJUkdcBpew/pBb6D+d6w
WScLqqz5k7cJj9ufJxUb8HeiqcHavVNnQx1Jk8xRwuGXL9vwTI/Og+/5SHhW+uva
ViT0YniLrfOWvloPqJmnRhkXn3sU81KxPhP4SOz8GcImzBrgnbqJ3kD/kNOXUE2E
c3LleaQINRQWVlfcKLelhhCvmXOfQ5JZtcRz2vnRzzH580T1ICOwNFFuvWVlls1L
kUemcjhmHBPXb979Ls69tSqdDm75IIBY92uxNqjy36zn8gFPnNM3BrER+xZ92E9L
L36LKwSeDL+mkJE/um48IQJJ4t2IW9bKwK8TFp4Bp9otc6+hBJmtwRjKnFbrx4DQ
Oh+sZBXuewmC/T/xLUxyGxV+QT9oKSqmMy7CYhHnfhpIkqK4Upk4oWgzu6mBs89L
ozr4vdy4d4/FY2TMHOFz4Xx/gJF2IVG02jUyg2yT2VZrUk75faeq2Ga6DlyUVpw0
T64lEU/r29KrvexYsLtdzlNC6Emui37LTU0YQWrKZoJGTLDeygBC/rupz1xFfI5d
3KPozxzyE6AiJlYil4Ffiac1WiwBK5PgI1UhYmNpPFo+McDp52jxZKsnwCvUccze
s9+3g0N7N1g5+iovLjLpQo5a0D60Mvz127CaM9q+u/qBNt3Je7oGLlr7IikM8eXY
F+gWcnEgqzmh0oHiPCj0
=Vt2D
-END PGP SIGNATURE-

Re: [gentoo-user] Re: Choice of MUA

[Peter Humphrey]

On Friday 12 Aug 2016 16:36:37 Grant Edwards wrote:
> On 2016-08-11, Peter Humphrey  wrote:
> > On Wednesday 10 Aug 2016 15:21:54 Philip Webb wrote:
> >> 160810 Peter Humphrey wrote:
> >> > I've been using KMail for many years. It suits me in many ways,
> >> > the most important being that I don't need to keep switching my hands
> >> > between mouse and keyboard.
> >> 
> >> If that's your criterion, why not try Mutt ?
> >> I've been using it for  c 20 years  & have never wanted anything else.
> > 
> > How does it display HTML in messages?
> 
> I have it set to run them through lynx (or links, or w3m, I forget) by
> default and display the results in the normal pager.  If I hit "p" it
> uses Firefox.

Thanks all for your contributions.

I know that Mutt has a large, loyal following, but I think I'd prefer to 
stick to a graphical MUA, having grown used to it over the years.

-- 
Rgds
Peter