Re: [gentoo-user] override PYTHON_TARGETS to avoid a slot collision
On 12/16/20 11:34 AM, Miles Malone wrote:
What's happening when you do emerge -avuDN --with-bdeps=y
--backtrack=100 @world ? Giving portage the flexibility to solve it
with some extra backtracking and increasing the scope to world might
fix it, if not then we can revisit it?
I don't remember if I've tried that combination, I'll do so now.
... you include -a. Under what situation might I respond to the prompt
with 'no'?
On Wed, 16 Dec 2020 at 20:24, n952162 wrote:
In an update with several slot collisions (see attachment), I'm zero-ing in on
the simplest, where a package is to be replaced by the same package, but with
different PYTHON_TARGETS (at least, that's how I interpret it).
Is there a way to force the PYTHON_TARGETS of the dependency?
Slot collision:
dev-python/jinja:0
(dev-python/jinja-2.11.2-r1:0/0::gentoo, ebuild scheduled for merge) USE="-doc -examples -test"
ABI_X86="(64)" PYTHON_TARGETS="python3_8 python3_9 (-pypy3) -python3_6 -python3_7" pulled
in by
dev-python/jinja[python_targets_python3_9(-),python_single_target_python3_9(+)] required by
(sys-auth/pambase-20201103:0/0::gentoo, ebuild scheduled for merge) USE="nullok passwdqc
sha512 -caps -debug -elogind -gnome-keyring -minimal -mktemp -pam_krb5 -pam_ssh -pwhistory
-pwquality -securetty (-selinux) -systemd" ABI_X86="(64)"
dev-python/jinja (Argument)
(dev-python/jinja-2.11.2-r1:0/0::gentoo, installed) USE="-doc -examples -test"
ABI_X86="(64)" PYTHON_TARGETS="python3_7 (-pypy3) -python3_6 -python3_8 -python3_9"
pulled in by
dev-python/jinja[python_targets_pypy3(-)?,python_targets_python3_6(-)?,python_targets_python3_7(-)?,python_targets_python3_8(-)?,python_targets_python3_9(-)?,-python_single_target_pypy3(-),-python_single_target_python3_6(-),-python_single_target_python3_7(-),-python_single_target_python3_8(-),-python_single_target_python3_9(-)]
required by (dev-python/sphinx-3.2.1:0/0::gentoo, installed) USE="-doc -latex -test"
ABI_X86="(64)" PYTHON_TARGETS="python3_7 (-pypy3) -python3_6 -python3_8 -python3_9"
If the package was good enough before, it's likely still good enough. Where's
the problem? I've (unsuccessfully) made these attempts:
# */* PYTHON_TARGETS: python3_6 python3_7 python3_8 python3_9
#*/* PYTHON_TARGETS: -python3_6 -python3_7 python3_8 python3_9
# just have one set
*/* PYTHON_TARGETS: python3_8
The sphinx ebuild has no targets, but does have this:
PYTHON_COMPAT=( python3_{6..9} pypy3 )
The emerge command was:
sudo emerge --verbose=y -vuUD --verbose-conflicts dev-python/setuptools
dev-python/setuptools_scm dev-python/certifi dev-python/markupsafe
dev-python/jinja dev-libs/libxml2
Re: [gentoo-user] override PYTHON_TARGETS to avoid a slot collision
If it's wanting to downgrade something you definitely wouldnt want
downgraded is one, but feel free to omit the "a" and do the above
anyway
On Wed, 16 Dec 2020 at 21:06, n952162 wrote:
>
> On 12/16/20 11:34 AM, Miles Malone wrote:
> > What's happening when you do emerge -avuDN --with-bdeps=y
> > --backtrack=100 @world ? Giving portage the flexibility to solve it
> > with some extra backtracking and increasing the scope to world might
> > fix it, if not then we can revisit it?
>
>
> I don't remember if I've tried that combination, I'll do so now.
>
>
> ... you include -a. Under what situation might I respond to the prompt
> with 'no'?
>
>
>
> >
> > On Wed, 16 Dec 2020 at 20:24, n952162 wrote:
> >> In an update with several slot collisions (see attachment), I'm zero-ing
> >> in on the simplest, where a package is to be replaced by the same package,
> >> but with different PYTHON_TARGETS (at least, that's how I interpret it).
> >>
> >> Is there a way to force the PYTHON_TARGETS of the dependency?
> >>
> >> Slot collision:
> >>
> >> dev-python/jinja:0
> >>
> >>(dev-python/jinja-2.11.2-r1:0/0::gentoo, ebuild scheduled for merge)
> >> USE="-doc -examples -test" ABI_X86="(64)" PYTHON_TARGETS="python3_8
> >> python3_9 (-pypy3) -python3_6 -python3_7" pulled in by
> >>
> >> dev-python/jinja[python_targets_python3_9(-),python_single_target_python3_9(+)]
> >> required by (sys-auth/pambase-20201103:0/0::gentoo, ebuild scheduled for
> >> merge) USE="nullok passwdqc sha512 -caps -debug -elogind -gnome-keyring
> >> -minimal -mktemp -pam_krb5 -pam_ssh -pwhistory -pwquality -securetty
> >> (-selinux) -systemd" ABI_X86="(64)"
> >>
> >>
> >> dev-python/jinja (Argument)
> >>
> >>(dev-python/jinja-2.11.2-r1:0/0::gentoo, installed) USE="-doc -examples
> >> -test" ABI_X86="(64)" PYTHON_TARGETS="python3_7 (-pypy3) -python3_6
> >> -python3_8 -python3_9" pulled in by
> >>
> >> dev-python/jinja[python_targets_pypy3(-)?,python_targets_python3_6(-)?,python_targets_python3_7(-)?,python_targets_python3_8(-)?,python_targets_python3_9(-)?,-python_single_target_pypy3(-),-python_single_target_python3_6(-),-python_single_target_python3_7(-),-python_single_target_python3_8(-),-python_single_target_python3_9(-)]
> >> required by (dev-python/sphinx-3.2.1:0/0::gentoo, installed) USE="-doc
> >> -latex -test" ABI_X86="(64)" PYTHON_TARGETS="python3_7 (-pypy3) -python3_6
> >> -python3_8 -python3_9"
> >>
> >> If the package was good enough before, it's likely still good enough.
> >> Where's the problem? I've (unsuccessfully) made these attempts:
> >>
> >> # */* PYTHON_TARGETS: python3_6 python3_7 python3_8 python3_9
> >> #*/* PYTHON_TARGETS: -python3_6 -python3_7 python3_8 python3_9
> >> # just have one set
> >> */* PYTHON_TARGETS: python3_8
> >>
> >> The sphinx ebuild has no targets, but does have this:
> >>
> >> PYTHON_COMPAT=( python3_{6..9} pypy3 )
> >>
> >> The emerge command was:
> >>
> >> sudo emerge --verbose=y -vuUD --verbose-conflicts
> >> dev-python/setuptools dev-python/setuptools_scm dev-python/certifi
> >> dev-python/markupsafe dev-python/jinja dev-libs/libxml2
> >>
> >>
>
Re: [gentoo-user] override PYTHON_TARGETS to avoid a slot collision
What's happening when you do emerge -avuDN --with-bdeps=y
--backtrack=100 @world ? Giving portage the flexibility to solve it
with some extra backtracking and increasing the scope to world might
fix it, if not then we can revisit it?
On Wed, 16 Dec 2020 at 20:24, n952162 wrote:
>
> In an update with several slot collisions (see attachment), I'm zero-ing in
> on the simplest, where a package is to be replaced by the same package, but
> with different PYTHON_TARGETS (at least, that's how I interpret it).
>
> Is there a way to force the PYTHON_TARGETS of the dependency?
>
> Slot collision:
>
> dev-python/jinja:0
>
> (dev-python/jinja-2.11.2-r1:0/0::gentoo, ebuild scheduled for merge)
> USE="-doc -examples -test" ABI_X86="(64)" PYTHON_TARGETS="python3_8 python3_9
> (-pypy3) -python3_6 -python3_7" pulled in by
>
> dev-python/jinja[python_targets_python3_9(-),python_single_target_python3_9(+)]
> required by (sys-auth/pambase-20201103:0/0::gentoo, ebuild scheduled for
> merge) USE="nullok passwdqc sha512 -caps -debug -elogind -gnome-keyring
> -minimal -mktemp -pam_krb5 -pam_ssh -pwhistory -pwquality -securetty
> (-selinux) -systemd" ABI_X86="(64)"
>
>
> dev-python/jinja (Argument)
>
> (dev-python/jinja-2.11.2-r1:0/0::gentoo, installed) USE="-doc -examples
> -test" ABI_X86="(64)" PYTHON_TARGETS="python3_7 (-pypy3) -python3_6
> -python3_8 -python3_9" pulled in by
>
> dev-python/jinja[python_targets_pypy3(-)?,python_targets_python3_6(-)?,python_targets_python3_7(-)?,python_targets_python3_8(-)?,python_targets_python3_9(-)?,-python_single_target_pypy3(-),-python_single_target_python3_6(-),-python_single_target_python3_7(-),-python_single_target_python3_8(-),-python_single_target_python3_9(-)]
> required by (dev-python/sphinx-3.2.1:0/0::gentoo, installed) USE="-doc
> -latex -test" ABI_X86="(64)" PYTHON_TARGETS="python3_7 (-pypy3) -python3_6
> -python3_8 -python3_9"
>
> If the package was good enough before, it's likely still good enough.
> Where's the problem? I've (unsuccessfully) made these attempts:
>
> # */* PYTHON_TARGETS: python3_6 python3_7 python3_8 python3_9
> #*/* PYTHON_TARGETS: -python3_6 -python3_7 python3_8 python3_9
> # just have one set
> */* PYTHON_TARGETS: python3_8
>
> The sphinx ebuild has no targets, but does have this:
>
> PYTHON_COMPAT=( python3_{6..9} pypy3 )
>
> The emerge command was:
>
> sudo emerge --verbose=y -vuUD --verbose-conflicts dev-python/setuptools
> dev-python/setuptools_scm dev-python/certifi dev-python/markupsafe
> dev-python/jinja dev-libs/libxml2
>
>
Re: [gentoo-user] override PYTHON_TARGETS to avoid a slot collision
在 2020/12/16 下午6:24, n952162 写道:
In an update with several slot collisions (see attachment), I'm
zero-ing in on the simplest, where a package is to be replaced by the
same package, but with different PYTHON_TARGETS (at least, that's how
I interpret it).
Is there a way to force the PYTHON_TARGETS of the dependency?
Slot collision:
dev-python/jinja:0
(dev-python/jinja-2.11.2-r1:0/0::gentoo, ebuild scheduled for merge)
USE="-doc -examples -test" ABI_X86="(64)" PYTHON_TARGETS="*python3_8
python3_9 (-pypy3) -python3_6 -python3_7*" pulled in by
dev-python/jinja[python_targets_python3_9(-),python_single_target_python3_9(+)]
required by (sys-auth/pambase-20201103:0/0::gentoo, ebuild scheduled
for merge) USE="nullok passwdqc sha512 -caps -debug -elogind
-gnome-keyring -minimal -mktemp -pam_krb5 -pam_ssh -pwhistory
-pwquality -securetty (-selinux) -systemd" ABI_X86="(64)"
dev-python/jinja (Argument)
(dev-python/jinja-2.11.2-r1:0/0::gentoo, installed) USE="-doc
-examples -test" ABI_X86="(64)" PYTHON_TARGETS="*python3_7 (-pypy3)
-python3_6 -python3_8 -python3_9*" pulled in by
dev-python/jinja[python_targets_pypy3(-)?,python_targets_python3_6(-)?,python_targets_python3_7(-)?,python_targets_python3_8(-)?,python_targets_python3_9(-)?,-python_single_target_pypy3(-),-python_single_target_python3_6(-),-python_single_target_python3_7(-),-python_single_target_python3_8(-),-python_single_target_python3_9(-)]
required by (dev-python/sphinx-3.2.1:0/0::gentoo, installed) USE="-doc
-latex -test" ABI_X86="(64)" PYTHON_TARGETS="python3_7 (-pypy3)
-python3_6 -python3_8 -python3_9"
If the package was good enough before, it's likely still good enough.
Where's the problem? I've (unsuccessfully) made these attempts:
# */* PYTHON_TARGETS: python3_6 python3_7 python3_8 python3_9
#*/* PYTHON_TARGETS: -python3_6 -python3_7 python3_8 python3_9
# just have one set
*/* PYTHON_TARGETS: python3_8
The sphinx ebuild has no targets, but does have this:
PYTHON_COMPAT=( python3_{6..9} pypy3 )
The emerge command was:
sudo emerge --verbose=y -vuUD --verbose-conflicts
dev-python/setuptools dev-python/setuptools_scm dev-python/certifi
dev-python/markupsafe dev-python/jinja dev-libs/libxml2
According to the
https://wiki.gentoo.org/wiki/Project:Python/PYTHON_TARGETS and your log
may be set like
# Replacing the profile default with specific implementation
dev-python/* PYTHON_SINGLE_TARGET: python3_6
That will let all the dev-python target set to python3_6
--
bobwxc
OpenPGP_signature
Description: OpenPGP digital signature
Re: [gentoo-user] override PYTHON_TARGETS to avoid a slot collision
Personally I just like to see what I'm getting myself into before I
start doing an upgrade or recompile on all of chromium, firefox,
qt-webkit, gtk-webkit, qt-webengine, libreoffice, and electron all at
once :p
To quote the meme, this little manouver's going to take us 51 years
On Wed, 16 Dec 2020 at 21:06, n952162 wrote:
>
> On 12/16/20 11:34 AM, Miles Malone wrote:
> > What's happening when you do emerge -avuDN --with-bdeps=y
> > --backtrack=100 @world ? Giving portage the flexibility to solve it
> > with some extra backtracking and increasing the scope to world might
> > fix it, if not then we can revisit it?
>
>
> I don't remember if I've tried that combination, I'll do so now.
>
>
> ... you include -a. Under what situation might I respond to the prompt
> with 'no'?
>
>
>
> >
> > On Wed, 16 Dec 2020 at 20:24, n952162 wrote:
> >> In an update with several slot collisions (see attachment), I'm zero-ing
> >> in on the simplest, where a package is to be replaced by the same package,
> >> but with different PYTHON_TARGETS (at least, that's how I interpret it).
> >>
> >> Is there a way to force the PYTHON_TARGETS of the dependency?
> >>
> >> Slot collision:
> >>
> >> dev-python/jinja:0
> >>
> >>(dev-python/jinja-2.11.2-r1:0/0::gentoo, ebuild scheduled for merge)
> >> USE="-doc -examples -test" ABI_X86="(64)" PYTHON_TARGETS="python3_8
> >> python3_9 (-pypy3) -python3_6 -python3_7" pulled in by
> >>
> >> dev-python/jinja[python_targets_python3_9(-),python_single_target_python3_9(+)]
> >> required by (sys-auth/pambase-20201103:0/0::gentoo, ebuild scheduled for
> >> merge) USE="nullok passwdqc sha512 -caps -debug -elogind -gnome-keyring
> >> -minimal -mktemp -pam_krb5 -pam_ssh -pwhistory -pwquality -securetty
> >> (-selinux) -systemd" ABI_X86="(64)"
> >>
> >>
> >> dev-python/jinja (Argument)
> >>
> >>(dev-python/jinja-2.11.2-r1:0/0::gentoo, installed) USE="-doc -examples
> >> -test" ABI_X86="(64)" PYTHON_TARGETS="python3_7 (-pypy3) -python3_6
> >> -python3_8 -python3_9" pulled in by
> >>
> >> dev-python/jinja[python_targets_pypy3(-)?,python_targets_python3_6(-)?,python_targets_python3_7(-)?,python_targets_python3_8(-)?,python_targets_python3_9(-)?,-python_single_target_pypy3(-),-python_single_target_python3_6(-),-python_single_target_python3_7(-),-python_single_target_python3_8(-),-python_single_target_python3_9(-)]
> >> required by (dev-python/sphinx-3.2.1:0/0::gentoo, installed) USE="-doc
> >> -latex -test" ABI_X86="(64)" PYTHON_TARGETS="python3_7 (-pypy3) -python3_6
> >> -python3_8 -python3_9"
> >>
> >> If the package was good enough before, it's likely still good enough.
> >> Where's the problem? I've (unsuccessfully) made these attempts:
> >>
> >> # */* PYTHON_TARGETS: python3_6 python3_7 python3_8 python3_9
> >> #*/* PYTHON_TARGETS: -python3_6 -python3_7 python3_8 python3_9
> >> # just have one set
> >> */* PYTHON_TARGETS: python3_8
> >>
> >> The sphinx ebuild has no targets, but does have this:
> >>
> >> PYTHON_COMPAT=( python3_{6..9} pypy3 )
> >>
> >> The emerge command was:
> >>
> >> sudo emerge --verbose=y -vuUD --verbose-conflicts
> >> dev-python/setuptools dev-python/setuptools_scm dev-python/certifi
> >> dev-python/markupsafe dev-python/jinja dev-libs/libxml2
> >>
> >>
>
Re: [gentoo-user] Reinstall Gentoo? [Was: Building pygtk-2.22.0-r1 fails. Help, please!]
On Sunday 24 April 2011 21:30:33 Neil Bothwick wrote: On Sun, 24 Apr 2011 21:17:23 +0100, David W Noon wrote: Doing this today I've had a couple of packages that needed to be emerged with USE=-doc when they failed. Those would be jinja and sphinx. They are notorious for their circular dependency, which requires USE='-doc' to bypass. It's rarely desirable to enable doc globally. It is best to enable only for those packages where you need extended documentation. @Alan Mackenzie: What Neil is saying can be achieved by setting package specific USE flags in the file /etc/portage/package.use; e.g. use an entry like: dev-python/jinja -doc i18n to exclude USE flag doc, but include i18n. -- Regards, Mick signature.asc Description: This is a digitally signed message part.
Re: [gentoo-user] override PYTHON_TARGETS to avoid a slot collision
On Saturday, 19 December 2020 11:37:31 GMT Neil Bothwick wrote: > On Sat, 19 Dec 2020 12:33:10 +0100, n952162 wrote: > > I do an emerge @world, it tells me I have slot collisions and stops. > > Following Neil B.'s advice, I try to go through the collisions and see > > what the differences are. jinja was a nice example, because there was a > > collision of the same package with itself! The only difference was the > > PYTHON_TARGET. I hoped someone could explain how I could force > > equivalency in that simple case. > > You need to follow the trail back further. If portage wants to install > two variants of jnja, look to see what is requiring them, that is most > likely where the real solution lies. 'emerge --tree -uNDpv @system' or '@world', will also show the respective dependency tree of any packages portage is trying to update. If an older version of jinja is being dragged in by a non-system package, you can temporarily uninstall that package and make a note of it to re-install it later if you need/want to. signature.asc Description: This is a digitally signed message part.
Re: [gentoo-user] Reinstall Gentoo? [Was: Building pygtk-2.22.0-r1 fails. Help, please!]
On Sun, 24 Apr 2011 21:17:23 +0100, David W Noon wrote: Doing this today I've had a couple of packages that needed to be emerged with USE=-doc when they failed. Those would be jinja and sphinx. They are notorious for their circular dependency, which requires USE='-doc' to bypass. It's rarely desirable to enable doc globally. It is best to enable only for those packages where you need extended documentation. -- Neil Bothwick A bit of tolerance is worth a megabyte of flaming. -- Henry Spencer signature.asc Description: PGP signature
Re: [gentoo-user] override PYTHON_TARGETS to avoid a slot collision
On 12/19/20 12:12 PM, bobwxc wrote:
在 2020/12/19 下午6:20, n952162 写道:
On 12/16/20 11:59 AM, Arve Barsnes wrote:
On Wed, 16 Dec 2020 at 11:34, Miles Malone
wrote:
What's happening when you do emerge -avuDN --with-bdeps=y
--backtrack=100 @world ? Giving portage the flexibility to solve it
with some extra backtracking and increasing the scope to world might
fix it, if not then we can revisit it?
You should definitely try this first if you haven't.
I have.
If the package was good enough before, it's likely still good enough. Where's
the problem? I've (unsuccessfully) made these attempts:
# */* PYTHON_TARGETS: python3_6 python3_7 python3_8 python3_9
#*/* PYTHON_TARGETS: -python3_6 -python3_7 python3_8 python3_9
# just have one set
*/* PYTHON_TARGETS: python3_8
Is there any reason that you need to add py3.9 to all packages? If you
need it for something special, add it to those packages only, and let
portage take care of python targets for you instead of continuously
trying these big hammers. Ideally you should have *no* python targets
set manually in make.conf or USE files.
I added it because I saw python3_9 in the PYTHON_TARGETS list for,
e.g. jinja, and hoped that it would force compatibility. That is the
question of the original post. But that was just one of many attempts.
The emerge command was:
sudo emerge --verbose=y -vuUD --verbose-conflicts dev-python/setuptools
dev-python/setuptools_scm dev-python/certifi dev-python/markupsafe
dev-python/jinja dev-libs/libxml2
Since it seems sphinx is installed with a different set of python
targets than what you're trying to update, you should include sphinx
in that emerge command to let it update to the same python targets and
solve the conflict.
Regards,
Arve
I tried adding that but it didn't help.
My latest command was:
time emerge \
-v \
--deep \
--update \
--changed-use \
--verbose-conflicts \
--keep-going \
--with-bdeps=y \
--changed-deps \
--backtrack=100 \
--newuse \
dev-python/setuptools dev-python/setuptools_scm dev-python/certifi
dev-python/markupsafe dev-python/jinja dev-libs/libxml2 dev-python/sphinx
Below is the latest build output, with no PYTHON_TARGET specifications.
...
real 0m45.063s
user 0m44.602s
sys 0m0.399s
I don't think this output or any list participant has actually
identified where the problem here is. In my original posting, the
only difference causing the slot collision for jinja was that one had
a PYTHON_TARGETS of 3-7 and the other of 3-8. I asked how to force
it to the correct value, but if someone explained that to me, I
didn't understand it.
I'm afraid I'm going to have to give up on gentoo, although I'm
pretty heavily invested in it. I'm spending too many hours trying to
maintain my systems and running into too many seemingly arbitrary
roadblocks. I'm told I should update every week, but I can't get a
system updated in a week.
/Is there a fundamental goals issue here, when there's so much
incompatibility between python3_{6,7,8,9}? Do packages really need
to care? Are these versions so fundamentally different from each
other, and programmers rely on those differences? Or, is this
somebody's orderliness tic?/
So what do you really want to know?
Well, for starters, why emerge(1) is not emerging...
Using jinja with python3.6 3.7.3.8 3.9 at the same time?
I don't know what jinja is and I just switched over to python3 myself.
I'm not into subtleties like 6, 7, 8, or 9.
I do an emerge @world, it tells me I have slot collisions and stops.
Following Neil B.'s advice, I try to go through the collisions and see
what the differences are. jinja was a nice example, because there was a
collision of the same package with itself! The only difference was the
PYTHON_TARGET. I hoped someone could explain how I could force
equivalency in that simple case.
Or want to keep it with 3.6 or some else?
The default PYTHON_TARGETS now change to 3_8 from 3_6. So when you
update, many software need to change.
Yeah. That surprises me, actually.
If you want to change that targets, just follow
https://wiki.gentoo.org/wiki/Project:Python/PYTHON_TARGETS
Maybe there no different or compatibility with it actually, but we
need a correct dependency.
I'm trying to emerge. I'm not developing anything.
If you do not have enough time to update and config gentoo,
maybe you should try other Linux like Arch(No need to compile) and
Debian(less update).
Yes, that's always an option. On the other hand, it might be possible
to improve gentoo so that not only the very brightest people can use
it. Source is kind of like a vaccine - if enough people use it, it can
help prevent the spread of viruses.
Re: [gentoo-user] Reinstall Gentoo? [Was: Building pygtk-2.22.0-r1 fails. Help, please!]
On Sun, 24 Apr 2011 21:40:02 +0200, Stroller wrote about Re: [gentoo-user] Reinstall Gentoo? [Was: Building pygtk-2.22.0-r1 fails. Help, please!]: On 24/4/2011, at 4:44pm, Mick wrote: ... At this stage you should only run: python-updater -v Nothing else. Doing this today I've had a couple of packages that needed to be emerged with USE=-doc when they failed. Those would be jinja and sphinx. They are notorious for their circular dependency, which requires USE='-doc' to bypass. -- Regards, Dave [RLU #314465] *-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-* dwn...@ntlworld.com (David W Noon) *-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-* signature.asc Description: PGP signature
Re: [gentoo-user] override PYTHON_TARGETS to avoid a slot collision
On Sat, 19 Dec 2020 12:33:10 +0100, n952162 wrote: > I do an emerge @world, it tells me I have slot collisions and stops. > Following Neil B.'s advice, I try to go through the collisions and see > what the differences are. jinja was a nice example, because there was a > collision of the same package with itself! The only difference was the > PYTHON_TARGET. I hoped someone could explain how I could force > equivalency in that simple case. You need to follow the trail back further. If portage wants to install two variants of jnja, look to see what is requiring them, that is most likely where the real solution lies. -- Neil Bothwick If Satan ever loses his hair, there'll be hell toupee. pgpG1gxZQsVOn.pgp Description: OpenPGP digital signature
Re: [gentoo-user] how do I resolve udev145 masked issue?
On Sun, 2 Aug 2009 14:53:48 -0400, John covici wrote:
I am using the gnome overlay from layman.
It might have been helpful to menyion that :(
If I comment out the source line for layman in /etc/make.conf I get
the following:
[nomerge ] gnome-base/gnome-2.26.3 [2.26.2]
[nomerge ] app-accessibility/orca-2.26.3 [2.26.2]
[nomerge ] dev-python/pycairo-1.8.6 USE=doc%*
[nomerge ]dev-python/sphinx-0.6.2 USE=doc -test
[ebuild N] dev-python/jinja2-2.1.1-r1 USE=doc -examples
-i18n -test
[ebuild N] dev-python/sphinx-0.6.2 USE=doc -test
* Error: circular dependencies:
('ebuild', '/', 'dev-python/jinja2-2.1.1-r1', 'merge') depends on
('ebuild', '/', 'dev-python/sphinx-0.6.2', 'merge') (buildtime)
('ebuild', '/', 'dev-python/sphinx-0.6.2', 'merge') depends on
('ebuild', '/', 'dev-python/jinja2-2.1.1-r1', 'merge') (buildtime)
* Note that circular dependencies can often be avoided by temporarily
* disabling USE flags that trigger optional dependencies.
The doc USE flag is causing that. Sphinx is used to build python docs, it
needs jinja but that needs sphinx because you have set its doc flag.
Emerge jinja without the doc flag.
Incidentally, unless you are a developer, you don't normally need the doc
use flag.
--
Neil Bothwick
Windows isn't CrippleWare -- it's Functionally Challenged.
signature.asc
Description: PGP signature
Re: [gentoo-user] how do I resolve udev145 masked issue?
on Sunday 08/02/2009 Neil Bothwick(n...@digimed.co.uk) wrote
On Sun, 2 Aug 2009 14:53:48 -0400, John covici wrote:
I am using the gnome overlay from layman.
It might have been helpful to menyion that :(
If I comment out the source line for layman in /etc/make.conf I get
the following:
[nomerge ] gnome-base/gnome-2.26.3 [2.26.2]
[nomerge ] app-accessibility/orca-2.26.3 [2.26.2]
[nomerge ] dev-python/pycairo-1.8.6 USE=doc%*
[nomerge ]dev-python/sphinx-0.6.2 USE=doc -test
[ebuild N] dev-python/jinja2-2.1.1-r1 USE=doc -examples
-i18n -test
[ebuild N] dev-python/sphinx-0.6.2 USE=doc -test
* Error: circular dependencies:
('ebuild', '/', 'dev-python/jinja2-2.1.1-r1', 'merge') depends on
('ebuild', '/', 'dev-python/sphinx-0.6.2', 'merge') (buildtime)
('ebuild', '/', 'dev-python/sphinx-0.6.2', 'merge') depends on
('ebuild', '/', 'dev-python/jinja2-2.1.1-r1', 'merge') (buildtime)
* Note that circular dependencies can often be avoided by temporarily
* disabling USE flags that trigger optional dependencies.
The doc USE flag is causing that. Sphinx is used to build python docs, it
needs jinja but that needs sphinx because you have set its doc flag.
Emerge jinja without the doc flag.
Incidentally, unless you are a developer, you don't normally need the doc
use flag.
OK, thanks for the advise -- I wish there were a devel-doc flag to
distinguish between use and development docs, but I guess you can't
have everything.
--
Your life is like a penny. You're going to lose it. The question is:
How do
you spend it?
John Covici
cov...@ccs.covici.com
Re: [gentoo-user] override PYTHON_TARGETS to avoid a slot collision
Python is every bit as much trouble in gentoo as it is in the Florida swamps. Python is so much trouble the History Channel has a Swamp People program they're showing regularly on TV. Could the post-install section of the handbook do with some good updates? On Sat, 19 Dec 2020, Michael wrote: > Date: Sat, 19 Dec 2020 06:51:18 > From: Michael > Reply-To: gentoo-user@lists.gentoo.org > To: gentoo-user@lists.gentoo.org > Subject: Re: [gentoo-user] override PYTHON_TARGETS to avoid a slot collision > > On Saturday, 19 December 2020 11:37:31 GMT Neil Bothwick wrote: > > On Sat, 19 Dec 2020 12:33:10 +0100, n952162 wrote: > > > I do an emerge @world, it tells me I have slot collisions and stops. > > > Following Neil B.'s advice, I try to go through the collisions and see > > > what the differences are. jinja was a nice example, because there was a > > > collision of the same package with itself! The only difference was the > > > PYTHON_TARGET. I hoped someone could explain how I could force > > > equivalency in that simple case. > > > > You need to follow the trail back further. If portage wants to install > > two variants of jnja, look to see what is requiring them, that is most > > likely where the real solution lies. > > 'emerge --tree -uNDpv @system' or '@world', will also show the respective > dependency tree of any packages portage is trying to update. If an older > version of jinja is being dragged in by a non-system package, you can > temporarily uninstall that package and make a note of it to re-install it > later if you need/want to. --
Re: [gentoo-user] override PYTHON_TARGETS to avoid a slot collision
在 2020/12/19 下午6:20, n952162 写道:
On 12/16/20 11:59 AM, Arve Barsnes wrote:
On Wed, 16 Dec 2020 at 11:34, Miles Malone
wrote:
What's happening when you do emerge -avuDN --with-bdeps=y
--backtrack=100 @world ? Giving portage the flexibility to solve it
with some extra backtracking and increasing the scope to world might
fix it, if not then we can revisit it?
You should definitely try this first if you haven't.
I have.
If the package was good enough before, it's likely still good enough. Where's
the problem? I've (unsuccessfully) made these attempts:
# */* PYTHON_TARGETS: python3_6 python3_7 python3_8 python3_9
#*/* PYTHON_TARGETS: -python3_6 -python3_7 python3_8 python3_9
# just have one set
*/* PYTHON_TARGETS: python3_8
Is there any reason that you need to add py3.9 to all packages? If you
need it for something special, add it to those packages only, and let
portage take care of python targets for you instead of continuously
trying these big hammers. Ideally you should have *no* python targets
set manually in make.conf or USE files.
I added it because I saw python3_9 in the PYTHON_TARGETS list for,
e.g. jinja, and hoped that it would force compatibility. That is the
question of the original post. But that was just one of many attempts.
The emerge command was:
sudo emerge --verbose=y -vuUD --verbose-conflicts dev-python/setuptools
dev-python/setuptools_scm dev-python/certifi dev-python/markupsafe
dev-python/jinja dev-libs/libxml2
Since it seems sphinx is installed with a different set of python
targets than what you're trying to update, you should include sphinx
in that emerge command to let it update to the same python targets and
solve the conflict.
Regards,
Arve
I tried adding that but it didn't help.
My latest command was:
time emerge \
-v \
--deep \
--update \
--changed-use \
--verbose-conflicts \
--keep-going \
--with-bdeps=y \
--changed-deps \
--backtrack=100 \
--newuse \
dev-python/setuptools dev-python/setuptools_scm dev-python/certifi
dev-python/markupsafe dev-python/jinja dev-libs/libxml2 dev-python/sphinx
Below is the latest build output, with no PYTHON_TARGET specifications.
...
real 0m45.063s
user 0m44.602s
sys 0m0.399s
I don't think this output or any list participant has actually
identified where the problem here is. In my original posting, the
only difference causing the slot collision for jinja was that one had
a PYTHON_TARGETS of 3-7 and the other of 3-8. I asked how to force it
to the correct value, but if someone explained that to me, I didn't
understand it.
I'm afraid I'm going to have to give up on gentoo, although I'm pretty
heavily invested in it. I'm spending too many hours trying to
maintain my systems and running into too many seemingly arbitrary
roadblocks. I'm told I should update every week, but I can't get a
system updated in a week.
/Is there a fundamental goals issue here, when there's so much
incompatibility between python3_{6,7,8,9}? Do packages really need
to care? Are these versions so fundamentally different from each
other, and programmers rely on those differences? Or, is this
somebody's orderliness tic?/
So what do you really want to know?
Using jinja with python3.6 3.7.3.8 3.9 at the same time?
Or want to keep it with 3.6 or some else?
The default PYTHON_TARGETS now change to 3_8 from 3_6. So when you
update, many software need to change.
If you want to change that targets, just follow
https://wiki.gentoo.org/wiki/Project:Python/PYTHON_TARGETS
Maybe there no different or compatibility with it actually, but we need
a correct dependency.
If you do not have enough time to update and config gentoo,
maybe you should try other Linux like Arch(No need to compile) and
Debian(less update).
:-)
--
bobwxc
OpenPGP_0x36E94EABB53E516B.asc
Description: application/pgp-keys
OpenPGP_signature
Description: OpenPGP digital signature
[gentoo-user] Re: dns/bind-tools 9.14 -> 9.16 pulling in 17 new dependencies?!
On 2020-07-21, Grant Edwards wrote: > On 2020-07-21, Peter Humphrey wrote: >> On Tuesday, 21 July 2020 15:47:25 BST Neil Bothwick wrote: >> >>> Sync, re-emerge bind-tools and try again. The man pages are now >>> downloaded as a separate tarball, so Sphinx and deps are not longer >>> needed. >> >> And lo! 17 packages were removed by depclean! > > Before I can try that, I apparently have to enable the elogind USE > flag because of somthing else that changed since I sync'ed > yesterday. That only requires 6 new packages [...] After that, X wouldn't start... another half-hour of googling and experimentation... switch my 'x' alias from using 'xinit' to 'startx', and now X is working again. ... and emerge --depclean removes all of the sphinx packages along with Babel, jinja, and a few others! So, I gained back the ground I lost yesterday to bind-tools, but lost some ground to elogind et alia. -- Grant
Re: [gentoo-user] override PYTHON_TARGETS to avoid a slot collision
On Sat, 19 Dec 2020 at 11:19, n952162 wrote: > I don't think this output or any list participant has actually identified > where the problem here is. In my original posting, the only difference > causing the slot collision for jinja was that one had a PYTHON_TARGETS of 3-7 > and the other of 3-8. I asked how to force it to the correct value, but if > someone explained that to me, I didn't understand it. Your output gives away that you STILL have not run depclean, so you STILL have dev-python/ipaddress installed, which has been removed from the tree, and requires python 2.7. Unless you remove old broken software you will NEVER get through a world update. Also: don't set PYTHON_TARGETS unless you have a REALLY good reason. You can set it on a specific package (and preferrable to set it only on a specific version of that package) to go around problems, but DON'T do this until you have made your system sane (meaning you can run world updates without troubles). Regards, Arve
Re: [gentoo-user] Calibre break after Update
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 02/17/2013 06:43 PM, ckard wrote: On Sun, Feb 17, 2013 at 11:24 PM, Silvio Siefke siefke_lis...@web.de wrote: Hello, i run the update from calibre yesterday and now calibre not startet. Has someone the same and has fix? siefke@gentoo-mobile : ~ $ calibre Traceback (most recent call last): File /usr/bin/calibre, line 20, in module sys.exit(main()) File /usr/lib/calibre/calibre/gui2/main.py, line 412, in main app, opts, args, actions = init_qt(args) File /usr/lib/calibre/calibre/gui2/main.py, line 85, in init_qt from calibre.gui2.ui import Main File /usr/lib/calibre/calibre/gui2/ui.py, line 31, in module from calibre.gui2.widgets import ProgressIndicator File /usr/lib/calibre/calibre/gui2/widgets.py, line 21, in module from calibre.gui2.progress_indicator import ProgressIndicator as _ProgressIndicator File /usr/lib/calibre/calibre/gui2/progress_indicator/__init__.py, line 15, in module pi_error) RuntimeError: Failed to load the Progress Indicator plugin: the sip module implements API v9.0 to v9.1 but the progress_indicator module requires API v8.1 Thank you Greetings Silvio You probably updated other python modules afterwards. Try to reinstall calibre. Wouldn't python-updater have caught that? I'm hitting the same error. Tried python-updater, which gave me: Starting parallel fetch Emerging (1 of 12) dev-python/setuptools-0.6.30-r1 Installing (1 of 12) dev-python/setuptools-0.6.30-r1 Emerging (2 of 12) dev-python/pygments-1.5-r1 Installing (2 of 12) dev-python/pygments-1.5-r1 Emerging (3 of 12) dev-python/docutils-0.10 Installing (3 of 12) dev-python/docutils-0.10 Emerging (4 of 12) dev-python/markupsafe-0.15-r1 Emerging (5 of 12) dev-python/sip-4.14.3 Emerging (6 of 12) dev-java/java-config-2.1.12-r1 Installing (4 of 12) dev-python/markupsafe-0.15-r1 Installing (6 of 12) dev-java/java-config-2.1.12-r1 Installing (5 of 12) dev-python/sip-4.14.3 Emerging (7 of 12) net-misc/dropbox-1.2.48-r1 Emerging (8 of 12) dev-python/PyQt4-4.9.6-r2 Installing (7 of 12) net-misc/dropbox-1.2.48-r1 Emerging (9 of 12) dev-python/sphinx-1.1.3-r6 Installing (9 of 12) dev-python/sphinx-1.1.3-r6 Emerging (10 of 12) dev-python/beautifulsoup-4.1.3-r1 Installing (10 of 12) dev-python/beautifulsoup-4.1.3-r1 Emerging (11 of 12) dev-python/jinja-2.6-r1 Installing (11 of 12) dev-python/jinja-2.6-r1 Emerging (12 of 12) dev-python/lxml-3.0.1 Installing (12 of 12) dev-python/lxml-3.0.1 Installing (8 of 12) dev-python/PyQt4-4.9.6-r2 Jobs: 12 of 12 complete Load avg: 2.89, 2.27, 2.08 ...but it didn't rebuild calibre. Anyway, trying rebuilding app-text/calibre. ...and that worked for me. -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.19 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iQEcBAEBAgAGBQJRI+gMAAoJED5TcEBdxYwQx6cIAIaen4DoFtecHT4shkCEv6wb mIGfWndewWMYGkEPKnROwJ2gJSUHWPh9kUq2HAyYxfSR0Jk+mcwXOUO8vHZJ7Occ ZDMW/bLL8V/uEM/5jegqAM3+IzNf1R+EvOd9HImuUiFuy+7/h61MNyYCrhnOiSrW HScNqvclEi9chP9tgwGOkMiBvPc/rHrQByiYA7auGJgox5OjyAuavpSEcC8/6JY8 NA3r1wB8D7yucsVroWkirkvsYR6OzCOz1XN4/0apxOWVg9PFusB/0XPCyydcIYl9 wwyu8JF/cPthO037EI3WzIflJENN+tKwSDVrQxJ/Oh9Q2geSz7dmjav/V2VaO9M= =dmp/ -END PGP SIGNATURE-
[gentoo-user] override PYTHON_TARGETS to avoid a slot collision
In an update with several slot collisions (see attachment), I'm
zero-ing in on the simplest, where a package is to be replaced by the
same package, but with different PYTHON_TARGETS (at least, that's how I
interpret it).
Is there a way to force the PYTHON_TARGETS of the dependency?
Slot collision:
dev-python/jinja:0
(dev-python/jinja-2.11.2-r1:0/0::gentoo, ebuild scheduled for merge)
USE="-doc -examples -test" ABI_X86="(64)" PYTHON_TARGETS="*python3_8
python3_9 (-pypy3) -python3_6 -python3_7*" pulled in by
dev-python/jinja[python_targets_python3_9(-),python_single_target_python3_9(+)]
required by (sys-auth/pambase-20201103:0/0::gentoo, ebuild scheduled for
merge) USE="nullok passwdqc sha512 -caps -debug -elogind -gnome-keyring
-minimal -mktemp -pam_krb5 -pam_ssh -pwhistory -pwquality -securetty
(-selinux) -systemd" ABI_X86="(64)"
dev-python/jinja (Argument)
(dev-python/jinja-2.11.2-r1:0/0::gentoo, installed) USE="-doc
-examples -test" ABI_X86="(64)" PYTHON_TARGETS="*python3_7 (-pypy3)
-python3_6 -python3_8 -python3_9*" pulled in by
dev-python/jinja[python_targets_pypy3(-)?,python_targets_python3_6(-)?,python_targets_python3_7(-)?,python_targets_python3_8(-)?,python_targets_python3_9(-)?,-python_single_target_pypy3(-),-python_single_target_python3_6(-),-python_single_target_python3_7(-),-python_single_target_python3_8(-),-python_single_target_python3_9(-)]
required by (dev-python/sphinx-3.2.1:0/0::gentoo, installed) USE="-doc
-latex -test" ABI_X86="(64)" PYTHON_TARGETS="python3_7 (-pypy3)
-python3_6 -python3_8 -python3_9"
If the package was good enough before, it's likely still good enough.
Where's the problem? I've (unsuccessfully) made these attempts:
# */* PYTHON_TARGETS: python3_6 python3_7 python3_8 python3_9
#*/* PYTHON_TARGETS: -python3_6 -python3_7 python3_8 python3_9
# just have one set
*/* PYTHON_TARGETS: python3_8
The sphinx ebuild has no targets, but does have this:
PYTHON_COMPAT=( python3_{6..9} pypy3 )
The emerge command was:
sudo emerge --verbose=y -vuUD --verbose-conflicts
dev-python/setuptools dev-python/setuptools_scm dev-python/certifi
dev-python/markupsafe dev-python/jinja dev-libs/libxml2
# vim: syntax=emerge-out
These are the packages that would be merged, in order:
Calculating dependencies
* IMPORTANT: 9 news items need reading for repository 'gentoo'.
* Use eselect news read to view new items.
* See the CONFIGURATION FILES and CONFIGURATION FILES UPDATE TOOLS
* sections of the emerge man page to learn how to update config files.
. done!
[ebuild U ] sys-libs/glibc-2.32-r2:2.2::gentoo [2.31-r6:2.2::gentoo]
USE="(crypt) multiarch (multilib) ssp (static-libs) -audit -caps (-cet)
-compile-locales -custom-cflags -doc -gd -headers-only -nscd -profile
(-selinux) -static-pie -suid -systemtap -test (-vanilla)" 16369 KiB
[ebuild U ] sys-libs/timezone-data-2020d::gentoo [2020a::gentoo] USE="nls
-leaps-timezone -zic-slim%" 647 KiB
[ebuild U ] sys-devel/gcc-config-2.3.2-r1::gentoo [2.3.2::gentoo]
USE="(cc-wrappers%*) (native-symlinks)" 0 KiB
[ebuild U ] virtual/tmpfiles-0-r1::gentoo [0::gentoo] 0 KiB
[ebuild U ] dev-libs/mpc-1.2.1:0/3::gentoo [1.2.0:0/3::gentoo]
USE="-static-libs" ABI_X86="(64) -32 (-x32)" 820 KiB
[ebuild U ] sys-libs/libseccomp-2.4.4::gentoo [2.4.3::gentoo]
USE="-static-libs" ABI_X86="(64) -32 (-x32)" 591 KiB
[ebuild R] sys-apps/file-5.39-r3::gentoo USE="bzip2 seccomp zlib -lzma
-python -static-libs" ABI_X86="(64) -32 (-x32)" PYTHON_TARGETS="python3_8*
python3_9* -python3_6 -python3_7*" 0 KiB
[ebuild R] app-misc/pax-utils-1.2.6::gentoo USE="seccomp -caps -debug
-python" PYTHON_SINGLE_TARGET="python3_9%* -python3_6 -python3_7* -python3_8" 0
KiB
[ebuild U ] sys-apps/sandbox-2.20::gentoo [2.18::gentoo] ABI_X86="(32)
(64) (-x32)" 419 KiB
[ebuild U ] dev-libs/openssl-1.1.1i:0/1.1::gentoo [1.1.1g:0/1.1::gentoo]
USE="asm zlib -bindist -rfc3779 -sctp -sslv3 -static-libs -test -tls-heartbeat
-vanilla" ABI_X86="(64) -32 (-x32)" CPU_FLAGS_X86="(sse2)" 9579 KiB
[ebuild U ] sys-devel/automake-1.16.2-r1:1.16::gentoo
[1.16.1-r1:1.16::gentoo] USE="-test" 1510 KiB
[ebuild U ] sys-libs/gdbm-1.18.1-r1:0/6::gentoo [1.18.1:0/6::gentoo]
USE="berkdb nls readline -static-libs" ABI_X86="(64) -32 (-x32)" 0 KiB
[ebuild U ] sys-apps/attr-2.4.48-r4::gentoo [2.4.48-r3::gentoo] USE="nls
(split-usr) -debug -static-libs" ABI_X86="(64) -32 (-x32)" 0 KiB
[ebuild U ] sys-apps/grep-3.5::gentoo [3.4::gentoo] USE="nls pcre -static"
1550 KiB
[ebuild U ] dev-libs/popt-1.18::gentoo [1.16-r2::gentoo] USE="nls
-static-libs" ABI_X86="(64) -32 (
Re: [gentoo-user] update fails, but I don't see why [PROGRESS]
On 12/3/20 9:33 PM, n952162 wrote: I'm trying to update the gentoo system that I last updated 6 weeks ago, but it seems not to work. Can somebody explain to me why? I tried and tried to figure out how I could determine what the fatal slot conflict would be. No matter how I mixed things, setuptools came up fighting about these things: - certifi - setuptools - jinja - markupsafe - libxml2 All the requirements were essentially equivalent, the only problem is that all had PYTHON_TARGETS with PYTHON3_8, while setuptools also had 3_6 and 3_7. I was not able to learn how to force PYTHON_TARGETS, also not by modifying the ebuild. Out of desperation or carelessness, I did a --depclean on the contents of the world file. 179 packages were removed, including sudo and my window manager. 106 packages were left. At least, I could still execute emerge. So, I tried to do an emerge on @system. I got another slot conflict! This time for mako, which I'd seen go by sometimes as a "package of interest". It's only transgression: PYTHON_TARGET containing python3_7. BUT! Finally, I could emerge mako. Along with it are coming 50 other packages! I presume that tomorrow, I'll be able to do a full @system and @world update and then re-install my old world file.
Re: [gentoo-user] override PYTHON_TARGETS to avoid a slot collision
On Wed, 16 Dec 2020 at 11:34, Miles Malone wrote: > What's happening when you do emerge -avuDN --with-bdeps=y > --backtrack=100 @world ? Giving portage the flexibility to solve it > with some extra backtracking and increasing the scope to world might > fix it, if not then we can revisit it? You should definitely try this first if you haven't. > > If the package was good enough before, it's likely still good enough. > > Where's the problem? I've (unsuccessfully) made these attempts: > > > > # */* PYTHON_TARGETS: python3_6 python3_7 python3_8 python3_9 > > #*/* PYTHON_TARGETS: -python3_6 -python3_7 python3_8 python3_9 > > # just have one set > > */* PYTHON_TARGETS: python3_8 Is there any reason that you need to add py3.9 to all packages? If you need it for something special, add it to those packages only, and let portage take care of python targets for you instead of continuously trying these big hammers. Ideally you should have *no* python targets set manually in make.conf or USE files. > > The emerge command was: > > > > sudo emerge --verbose=y -vuUD --verbose-conflicts dev-python/setuptools > > dev-python/setuptools_scm dev-python/certifi dev-python/markupsafe > > dev-python/jinja dev-libs/libxml2 Since it seems sphinx is installed with a different set of python targets than what you're trying to update, you should include sphinx in that emerge command to let it update to the same python targets and solve the conflict. Regards, Arve
[gentoo-user] gentoo alternatives
I'm looking for a gentoo alternative and am surprised to see that google chrome os is based on gentoo. Does anybody have any experience with this? Do they support multi-media and basic modern desktop capabilities? I see that there's some concentration on a special browser, but I'd be running Firefox and FVWM anyway. Do they use /portage/ and source packages? Do they push down every single upstream modification, like gentoo does, or maybe have a bit of hysteresis? I updated on May first and built firefox 78.10.*0*. 2+ days of building. I updated on June first and built firefox 78.10.*1*. and spent 2+ days building. I updated today because of the same old slot collision problems I've run into over a year dev-python/setuptools:0 dev-python/setuptools_scm:0 dev-python/toml:0 dev-python/certifi:0 dev-python/jinja:0 dev-python/markupsafe:0 and now, on the 7th, I'm building firefox 78.11. I just don't have the time for this. It impacts my machines too much. Yes, I know, there are binary versions, but if I wanted to use binary, I wouldn't use gentoo. And anyway, there's always rust and gcc and ...
Re: [gentoo-user] gentoo alternatives
On 6/7/21 10:10 AM, n952162 wrote: I'm looking for a gentoo alternative and am surprised to see that google chrome os is based on gentoo. Does anybody have any experience with this? Do they support multi-media and basic modern desktop capabilities? I see that there's some concentration on a special browser, but I'd be running Firefox and FVWM anyway. Do they use /portage/ and source packages? Do they push down every single upstream modification, like gentoo does, or maybe have a bit of hysteresis? I updated on May first and built firefox 78.10.*0*. 2+ days of building. I updated on June first and built firefox 78.10.*1*. and spent 2+ days building. I updated today because of the same old slot collision problems I've run into over a year dev-python/setuptools:0 dev-python/setuptools_scm:0 dev-python/toml:0 dev-python/certifi:0 dev-python/jinja:0 dev-python/markupsafe:0 and now, on the 7th, I'm building firefox 78.11. I just don't have the time for this. It impacts my machines too much. Yes, I know, there are binary versions, but if I wanted to use binary, I wouldn't use gentoo. And anyway, there's always rust and gcc and ... Okay, I guess I got it, at least for the worst offenders, firefox and thunderbird: not have them in my world file and every quarter update them manually. Would that work?
Re: [gentoo-user] override PYTHON_TARGETS to avoid a slot collision
On Sat, 19 Dec 2020 15:11:34 +0100, n952162 wrote:
> >> I don't think this output or any list participant has actually
> >> identified where the problem here is. In my original posting, the
> >> only difference causing the slot collision for jinja was that one
> >> had a PYTHON_TARGETS of 3-7 and the other of 3-8. I asked how to
> >> force it to the correct value, but if someone explained that to me,
> >> I didn't understand it.
> > You have specified manually a number of python versions, you
> > shouldn't have.
>
>
> Are you saying that long lists like this:
>
> *"python3_8 python3_9 (-pypy3) -python3_6 -python3_7*"
>
> are relics from improper or obsolete invocations made be me?
>
> If so, how can I get rid of them?
grep -ir python /etc/portage/package.use
You shouldn't really have many, if any, specific settings for
python_target. Comment out any you see and try again.
> > 2. Clean your world file from any and all dependencies, libraries and
> > packages you do not want to have explicitly installed.
>
>
> Yes, I receive that advice a lot. If I were to follow it aggressively,
> there would only be a handful of files in my world file. Will that
> work?
Absolutely. Remove anything you don't explicitly need then run depclean.
If something shows in the list that you want to keep, add it back with
emerge -n.
> I update the /etc/portage/package.use files by hand, so I get a feeling
> for how it works. Can it be that etc-update is a "smart system" that
> does more than just that?
Yes, read the docs, it merges the old and new configs. I prefer to use
conf-update but all the config managers do much the same thing.
> >> /Is there a fundamental goals issue here, when there's so much
> >> incompatibility between python3_{6,7,8,9}? Do packages really need
> >> to care? Are these versions so fundamentally different from each
> >> other, and programmers rely on those differences? Or, is this
> >> somebody's orderliness tic?/
It's also about where python modules are installed, but the main problem
here appears to be that you are depending on obsolete and deprecated
versions of python.
--
Neil Bothwick
What do you do when you see an endangered animal eating an endangered
plant?
pgpVYQWa3CyQu.pgp
Description: OpenPGP digital signature
Re: [gentoo-user] gentoo alternatives
On 6/7/21 1:10 AM, n952162 wrote: > I'm looking for a gentoo alternative and am surprised to see that google > chrome os is based on gentoo. > > Does anybody have any experience with this? > > Do they support multi-media and basic modern desktop capabilities? I > see that there's some concentration on a special browser, but I'd be > running Firefox and FVWM anyway. > > Do they use /portage/ and source packages? > > Do they push down every single upstream modification, like gentoo does, > or maybe have a bit of hysteresis? > > I updated on May first and built firefox 78.10.*0*. 2+ days of > building. I updated on June first and built firefox 78.10.*1*. and > spent 2+ days building. I updated today because of the same old slot > collision problems I've run into over a year > > dev-python/setuptools:0 > dev-python/setuptools_scm:0 > dev-python/toml:0 > dev-python/certifi:0 > dev-python/jinja:0 > dev-python/markupsafe:0 > > and now, on the 7th, I'm building firefox 78.11. I just don't have the > time for this. It impacts my machines too much. > > Yes, I know, there are binary versions, but if I wanted to use binary, I > wouldn't use gentoo. And anyway, there's always rust and gcc and ... > > > Firefox 78.10[1], 78.10.1[2], and 78.11[3] are all upstream releases that fix security errata. Promptly pushing through security fixes from upstream is the responsible thing for package maintainers to do. How web browsers came to be so complex and whether it is worth it is another topic entirely, but suffice to say I think your problems are more caused by upstream than Gentoo. As long as you are using a source distribution, you will pay the price of long compiles for such complicated software, and it will happen frequently because of how many security flaws crop up (again due to the sheer scope and complexity of the thing), and if you do this on old hardware it will be slow (although 2 days to compile Firefox seems excessive, what hardware are you building this on?). Regarding rust, personally I just gave up and installed rust-bin. Again it's not Gentoo's fault that upstream's product is so bloated. cal [1] https://www.mozilla.org/en-US/security/advisories/mfsa2021-15/ [2] https://www.mozilla.org/en-US/security/advisories/mfsa2021-18/ [3] https://www.mozilla.org/en-US/security/advisories/mfsa2021-24/
[gentoo-user] Updating pretty old system - portage fail, stage3 gcc also broken...
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/pep8-1.5.7: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)
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/jinja-2.7.3:0/0::gentoo, installed)
dev-python/setuptools[python_targets_pypy(-)?,python_targets_python2_7(-)?,python_targets_python3_3(-)?,python_targets_python3_4(-)?,-python_single_target_pypy(-),-python_single_target_python2_7(-),-python_single_target_python3_3(-),-python_single_target_python3_4(-)]
required by (dev-python/sphinx-1.2.2:0/0::gentoo, installed)
sys-apps/portage:0
(sys-apps/portage-2.2.26:0/0::gentoo, ebuild scheduled for merge) pulled in by
sys-apps/portage (Argument)
(sys-apps/portage-2.2.14:0/0::gentoo, installed) pulled in by
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)
I have also tried the chroot method - running the latest
stage3-amd64-20160519.tar.bz2
in the chroot.
Unfortunately, even compiler does not seem to work out of the box there:
(chroot) tools / # echo 'int main() { exit 0; } ' > a.c
(chroot) tools / # gcc a.c
gcc: error trying to exec 'cc1': execvp: No such file or directory
Any ideas how to proceed?
Marcin
Re: [gentoo-user] override PYTHON_TARGETS to avoid a slot collision
On Saturday, 19 December 2020 10:20:26 GMT n952162 wrote:
> I don't think this output or any list participant has actually
> identified where the problem here is. In my original posting, the only
> difference causing the slot collision for jinja was that one had a
> PYTHON_TARGETS of 3-7 and the other of 3-8. I asked how to force it to
> the correct value, but if someone explained that to me, I didn't
> understand it.
You have specified manually a number of python versions, you shouldn't have.
It seems you have also added permanently into your /var/lib/portage/world a
large number of dependencies and libraries due to your emerge syntax when
emerging specific packages, which again, you shouldn't have.
As a result with your own inputs in your portage configuration you are
fighting against what portage is trying to do in its calculations.
I would think the easiest solution would be to work with portage, rather than
despite portage:
1. Purge from your config files any hardcoded python targets, in order to let
portage choose which python target version it requires.
2. Clean your world file from any and all dependencies, libraries and packages
you do not want to have explicitly installed.
3. If 'emerge -uaNDv @system' gives you similar errors as above, try emerging
one package at a time with '--oneshot', so it does not inadvertently end up in
your world; e.g.
emerge -1aNDv
Do not specify a package version in the above, just a name only. Let portage
install the version it calculates is appropriate and update any dependencies
needed. If your toolchain is completely borked, you could try the same by
using a Live-CD and a latest portage snapshot as per the guide book.
4. When you finish emerging @system you should have a sound toolchain to build
the rest of your Gentoo installation with. Run the following:
etc-update (to update your system configuration files)
emerge --depclean -v -a (to unmerge packages/versions no longer needed)
5. Follow with 'emerge -uaNDv @world'.
6. When you finish all this run:
etc-update
emerge -v -a @preserved-rebuild --keep-going
emerge --depclean -v -a
revdep-rebuild -v -- -a
/usr/bin/eclean-dist
7. Build the latest kernel, update grub's menu, reboot.
> I'm afraid I'm going to have to give up on gentoo, although I'm pretty
> heavily invested in it. I'm spending too many hours trying to maintain
> my systems and running into too many seemingly arbitrary roadblocks.
> I'm told I should update every week, but I can't get a system updated in
> a week.
I have some systems I update once a month or even less frequently. There's an
old box I use sometimes for testing. I don't update this particular box for
the best part of 3 months at a time. I very rarely, if ever, arrive at hard
[B]locks and even when I do I often resolve them by changing or reverting to
defaults their USE flags, or first using quickpkg, then manually unmerging the
blocking non-system package and letting portage decide for me what package
version to emerge and which dependencies it needs.
YMMV, but a stable system should not be too troublesome to update if you
follow the above advice.
This mailing list, forums and IRC channels tend to offer really good advice,
in case you want to try a different crowd for ideas.
HTH. :-)
> /Is there a fundamental goals issue here, when there's so much
> incompatibility between python3_{6,7,8,9}? Do packages really need to
> care? Are these versions so fundamentally different from each other,
> and programmers rely on those differences? Or, is this somebody's
> orderliness tic?/
Portage runs on python and it is also a dependency on a large number of other
packages and scripts. As python upstream is gradually deprecating older
versions, Gentoo has to follow through with the migration. The portage tree
is presently in a relative state of flux because of this, but it should soon
slow down again.
If your system is borked for unknown reasons and following the above
suggestions you can't arrive at a stable state, perhaps it is time for you to
reinstall - which by the look of things it ought to take less of your time?
signature.asc
Description: This is a digitally signed message part.
Re: [gentoo-user] override PYTHON_TARGETS to avoid a slot collision
On 12/19/20 12:35 PM, Michael wrote:
On Saturday, 19 December 2020 10:20:26 GMT n952162 wrote:
I don't think this output or any list participant has actually
identified where the problem here is. In my original posting, the only
difference causing the slot collision for jinja was that one had a
PYTHON_TARGETS of 3-7 and the other of 3-8. I asked how to force it to
the correct value, but if someone explained that to me, I didn't
understand it.
You have specified manually a number of python versions, you shouldn't have.
Are you saying that long lists like this:
*"python3_8 python3_9 (-pypy3) -python3_6 -python3_7*"
are relics from improper or obsolete invocations made be me?
If so, how can I get rid of them?
It seems you have also added permanently into your /var/lib/portage/world a
large number of dependencies and libraries due to your emerge syntax when
emerging specific packages, which again, you shouldn't have.
As a result with your own inputs in your portage configuration you are
fighting against what portage is trying to do in its calculations.
I would think the easiest solution would be to work with portage, rather than
despite portage:
1. Purge from your config files any hardcoded python targets, in order to let
portage choose which python target version it requires.
I have added or removed these definitions, either following suggestions
or attempting to provide prerequisites for packages that seem to require
them.
Absolutely, the best medicine is no medicine.
2. Clean your world file from any and all dependencies, libraries and packages
you do not want to have explicitly installed.
Yes, I receive that advice a lot. If I were to follow it aggressively,
there would only be a handful of files in my world file. Will that work?
3. If 'emerge -uaNDv @system' gives you similar errors as above, try emerging
one package at a time with '--oneshot', so it does not inadvertently end up in
your world; e.g.
emerge -1aNDv
I can't get *anything* to emerge, either alone, with near dependencies
(as in the orginal posting) or in sets.
Do not specify a package version in the above, just a name only. Let portage
install the version it calculates is appropriate and update any dependencies
needed.
I never do.
If your toolchain is completely borked, you could try the same by
using a Live-CD and a latest portage snapshot as per the guide book.
Is that much different than a re-install?
4. When you finish emerging @system you should have a sound toolchain to build
the rest of your Gentoo installation with. Run the following:
etc-update (to update your system configuration files)
emerge --depclean -v -a (to unmerge packages/versions no longer needed)
5. Follow with 'emerge -uaNDv @world'.
6. When you finish all this run:
etc-update
emerge -v -a @preserved-rebuild --keep-going
emerge --depclean -v -a
revdep-rebuild -v -- -a
/usr/bin/eclean-dist
7. Build the latest kernel, update grub's menu, reboot.
Yes, I perform these steps, basically, once I get an update emerge to work.
I update the /etc/portage/package.use files by hand, so I get a feeling
for how it works. Can it be that etc-update is a "smart system" that
does more than just that?
/Is there a fundamental goals issue here, when there's so much
incompatibility between python3_{6,7,8,9}? Do packages really need to
care? Are these versions so fundamentally different from each other,
and programmers rely on those differences? Or, is this somebody's
orderliness tic?/
Portage runs on python and it is also a dependency on a large number of other
packages and scripts. As python upstream is gradually deprecating older
versions, Gentoo has to follow through with the migration. The portage tree
is presently in a relative state of flux because of this, but it should soon
slow down again.
/What I'm wondering is if packages aren't specifying with too fine a
granularity./
If your system is borked for unknown reasons and following the above
suggestions you can't arrive at a stable state, perhaps it is time for you to
reinstall - which by the look of things it ought to take less of your time?
I was thinking I'd just re-installed this system but I guess that had
just been a painful @world update - I see that I installed it last
year. If I continue not being able to get a single emerge, I guess
that's how I'll have to go.
I'm surprised, though, that nobody could address the reduced case I
presented in the original posting:
- is the same package being re-installed with new python target
requirements, or am I interpreting it wrongly?
- is there no way to satisfy the differing python target requirements?
- are there consequences on other packages to emerging this package
that make it impossible?
Re: [gentoo-user] gentoo alternatives
Chrome OS is made by Google to run specifically on the Chromebooks. I don't think it is intended for general computing and there is no enthusiast community around it like around other distros. The closest cousin to Gentoo would be Funtoo. It used to be that Gentoo Portage could only use rsync, while Funtoo Portage could use git which is much faster, but since then Gentoo Portage has also gained the functionality to use git for this purpose. My biggest problem with Gentoo was not so much the time needed to compile huge ebuilds like Firefox, Thunderbird, or Chromium, but that say if you neglected doing updates for a while and then decided to start again, then you'd have serious problems. This is because, at least the way I understood it, after some time old ebuilds would get deleted from the Portage servers to conserve space there, but some of those now deleted ebuilds would still be needed as dependencies to do iterative updates. The sure-way to resolve this problem would be to re-emerge the whole @world set, which of course would take way-longer than just Firefox, and might work differently because the '/etc/' configuration schema might have changed. In my case I had some weird problem either emerging some ebuild or keeping an old version of an ebuild to keep the functionality or the '/etc/' schema removed in the new versions. I just let things sit, and moved on to other projects. But when later on I tried to go back to the original issue, I had even more trouble because now I was even further behind @world, and more ebuilds would not upgrade because of deleted dependencies. So to sum it up, my problem with Gentoo was that you could not just do iterative updates after long periods of inactivity. You pretty much had to emerge daily and if you had some problem then drop everything and fix it right away, or else you'll fall even further behind and eventually might have to rebuild @world. And so because constant attention intervention and trial and error was required you could not just compile huge ebuilds overnight and go about your life during the day. The distro I would recommend to look at now is NixOS -- it is also source-based, but if you have problems with one package that will not prevent you from keeping the rest of the system up to date. Upstream changes are pulled pretty regularly. And even though it is source-based, you download most packages pre-compiled. However if you want to you can tweak the source and re-compile locally. You can also keep multiple versions of the same package. You also do not mess directly with the '/etc/' files for individual packages, instead you specify a global configuration "recipe" in '/etc/nixos/configuration.nix', which is used to generate the package-specific '/etc/' files. This layer of abstraction improves reliability and allows easy config cloning across machines. The down-side is that NixOS has a radically-different paradigm that takes a while to wrap your head around, requires learning the Nix Expression Language (which is radically-different too), and is not yet that "mature" so theoretically things can break, but I would still recommend it over Chrome OS. -- Marat On 6/7/21 1:10 AM, n952162 wrote: I'm looking for a gentoo alternative and am surprised to see that google chrome os is based on gentoo. Does anybody have any experience with this? Do they support multi-media and basic modern desktop capabilities? I see that there's some concentration on a special browser, but I'd be running Firefox and FVWM anyway. Do they use /portage/ and source packages? Do they push down every single upstream modification, like gentoo does, or maybe have a bit of hysteresis? I updated on May first and built firefox 78.10.*0*. 2+ days of building. I updated on June first and built firefox 78.10.*1*. and spent 2+ days building. I updated today because of the same old slot collision problems I've run into over a year dev-python/setuptools:0 dev-python/setuptools_scm:0 dev-python/toml:0 dev-python/certifi:0 dev-python/jinja:0 dev-python/markupsafe:0 and now, on the 7th, I'm building firefox 78.11. I just don't have the time for this. It impacts my machines too much. Yes, I know, there are binary versions, but if I wanted to use binary, I wouldn't use gentoo. And anyway, there's always rust and gcc and ...
[gentoo-user] Re: Determine what's keeping Python 3.7 around?
On 2020-12-06, Neil Bothwick wrote: > On Sun, 6 Dec 2020 20:01:27 - (UTC), Grant Edwards wrote: > >> I updated one of my systems a day or two ago, and Python 3.7 went away >> as expected. Today, I'm updating another system and it is rebuilding >> tons of stuff to target python 3.8 instead of 3.7, but it's keeping >> 3.7 and even wants to install a _new_ package -- and build it for >> Python 3.7: > > emerge -cpv python:3.7 will show you what is keeping 3.7 Something's wrong. That lists 43 packages. I checked the first few, and none of them require python 3.7. # emerge -cpv python:3.7 Calculating dependencies... done! dev-lang/python-3.7.9 pulled in by: app-office/gnumeric-1.12.47 requires dev-lang/python:3.7 app-office/libreoffice-6.4.7.2 requires dev-lang/python:3.7[threads(+),xml] app-portage/gemato-16.2 requires dev-lang/python:3.7[threads(+)] app-portage/gentoolkit-0.5.0-r2 requires dev-lang/python:3.7[xml(+),threads(+)] app-portage/mirrorselect-2.2.6-r1 requires dev-lang/python:3.7[xml] app-text/asciidoc-9.0.2 requires dev-lang/python:3.7 dev-embedded/libftdi-1.4 requires dev-lang/python:3.7 dev-java/java-config-2.3.1 requires dev-lang/python:3.7 dev-java/javatoolkit-0.6.3 requires dev-lang/python:3.7[xml(+)] dev-libs/gobject-introspection-1.64.1-r1 requires dev-lang/python:3.7[xml] dev-libs/libxml2-2.9.10-r3 requires dev-lang/python:3.7[xml] dev-libs/newt-0.52.21-r1 requires dev-lang/python:3.7 dev-python/PyQt5-5.15.1 requires dev-lang/python:3.7 dev-python/PyQt5-sip-4.19.24 requires dev-lang/python:3.7 dev-python/PySocks-1.7.1-r1 requires dev-lang/python:3.7 dev-python/bcrypt-3.2.0 requires dev-lang/python:3.7 dev-python/beautifulsoup-4.9.3 requires dev-lang/python:3.7 dev-python/cairocffi-1.1.0 requires dev-lang/python:3.7 dev-python/certifi-10001 requires dev-lang/python:3.7 dev-python/cffi-1.14.0-r3 requires dev-lang/python:3.7 dev-python/chardet-3.0.4-r1 requires dev-lang/python:3.7 dev-python/configobj-5.0.6 requires dev-lang/python:3.7 dev-python/cryptography-3.2 requires dev-lang/python:3.7[threads(+)] dev-python/cssselect2-0.3.0 requires dev-lang/python:3.7 dev-python/cython-0.29.21-r1 requires dev-lang/python:3.7[threads(+)] dev-python/defusedxml-0.7.0_rc1 requires dev-lang/python:3.7[xml(+)] dev-python/docutils-0.16-r1 requires dev-lang/python:3.7 dev-python/future-0.18.2-r1 requires dev-lang/python:3.7 dev-python/html5lib-1.1 requires dev-lang/python:3.7[xml(+)] dev-python/idna-2.10-r1 requires dev-lang/python:3.7 dev-python/imapclient-2.1.0 requires dev-lang/python:3.7 dev-python/importlib_metadata-2.0.0 requires dev-lang/python:3.7 dev-python/jinja-2.11.2-r1 requires dev-lang/python:3.7[threads(+)] dev-python/lxml-4.6.2 requires dev-lang/python:3.7 dev-python/mako-1.1.3-r1 requires dev-lang/python:3.7 dev-python/markdown-3.3.3 requires dev-lang/python:3.7 dev-python/markups-3.0.0-r1 requires dev-lang/python:3.7 dev-python/markupsafe-1.1.1-r1 requires dev-lang/python:3.7 dev-python/netifaces-0.10.9 requires dev-lang/python:3.7 dev-python/olefile-0.46-r1 requires dev-lang/python:3.7 dev-python/paho-mqtt-1.5.0 requires dev-lang/python:3.7 dev-python/paramiko-2.7.1 requires dev-lang/python:3.7[threads(+)] dev-python/pbkdf2-1.3-r1 requires dev-lang/python:3.7 dev-python/pillow-7.2.0 requires dev-lang/python:3.7[tk,threads(+)] dev-python/pip-20.2.4 requires dev-lang/python:3.7[ssl(+),threads(+)] dev-python/ply-3.11-r1 requires dev-lang/python:3.7 dev-python/pyalsa-1.1.6-r1 requires dev-lang/python:3.7 dev-python/pyasn1-0.4.8-r1 requires dev-lang/python:3.7 dev-python/pycairo-1.18.2 requires dev-lang/python:3.7[threads(+)] dev-python/pycparser-2.20-r1 requires dev-lang/python:3.7 dev-python/pycurl-7.43.0.6 requires dev-lang/python:3.7 dev-python/pygments-2.7.2 requires dev-lang/python:3.7 dev-python/pygobject-3.36.1-r1 requires dev-lang/python:3.7 dev-python/pynacl-1.4.0 requires dev-lang/python:3.7 dev-python/pyopenssl-19.1.0-r1 requires dev-lang/python:3.7[threads(+)] dev-python/pyphen-0.9.5 requires dev-lang/python:3.7 dev-python/pyserial-3.4 requires dev-lang/python:3.7 dev-python/python-markdown-math-0.7 requires dev-lang/python:3.7 dev-python/qrcode-6.1 requires dev-lang/python:3.7 dev-python/requests-2.24.0-r1 requires dev-lang/python:3.7[threads(+)] dev-python/setuptools-46.4.0-r3 requires dev-lang/python:3.7[xml(+)] dev-python/sip-4.19.24 requires dev-lang/python:3.7 dev-python/six-1.15.0-r1 requires dev-lang/python:3.7 dev-python/soupsieve-2.0.1 requires dev-lang/python:3.7 dev-python/ssl-fetch-0.4 requires dev-lang/python:3.7 dev-python/tinycss2-1.0.2 requires dev-lang/python:3.7 dev-python/toml-0.10.1-r1 requires dev-lang/python:3.7 dev-python/urllib
Re: [gentoo-user] Which pkg installs /boot/grub?
Hello, grub creates /boot/grub when you run "grub-install" Regards, Rasmus Original Message On 23 Jul 2017, 20:46, Harry Putnam wrote: > I was pretty sure that grub2 installed /boot/grub... but I see no such > directory after installing grub. > > qlist grub shows no directory /boot/grub > > In other installs I seem to recall seeing /boot/grub in place after > installing grub. > > Googling for pkg containing /boot/grub seemd pretty useless as mostly > it turns up all piles of stuff staring grub... but I already know pkg > grub-2.02 does not contain that directory or the files in it. > > qfile /boot/grub > equery b /boot/grub > > Before I continue this hard fought fresh install of gentoo into a vbox > vm, I'd like to know if I should be seeing a boot grub after these 223 > pkgs (which includes grub-2.02) are installed? > > app-admin/eselect-1.4.9 > app-admin/rsyslog-8.28.0 > app-arch/libarchive-3.3.1 > app-arch/tar-1.29-r3 > app-arch/zip-3.0-r3 > app-crypt/rhash-1.3.4 > app-editors/vim-8.0.0386-r1 > app-editors/vim-core-8.0.0386 > app-eselect/eselect-ctags-1.18 > app-eselect/eselect-fontconfig-1.1-r1 > app-eselect/eselect-mesa-0.0.10-r1 > app-eselect/eselect-opengl-1.3.1-r4 > app-eselect/eselect-vi-1.1.9 > app-misc/pax-utils-1.2.2 > app-portage/cfg-update-1.8.9 > app-portage/eix-0.32.9 > app-portage/gentoolkit-0.4.0 > app-portage/portage-utils-0.64 > app-shells/bash-4.4_p12 > app-shells/push-2.0-r1 > app-shells/quoter-3.0_p2-r1 > app-text/build-docbook-catalog-1.21 > app-text/docbook-xml-dtd-4.2-r2 > app-text/docbook-xml-dtd-4.4-r2 > app-text/opensp-1.5.2-r4 > app-vim/gentoo-syntax-20170225 > dev-db/sqlite-3.19.3 > dev-lang/nasm-2.13.01 > dev-lang/perl-5.24.2 > dev-lang/python-exec-2.4.5 > dev-libs/boehm-gc-7.6.0 > dev-libs/expat-2.2.2 > dev-libs/gmp-6.1.2 > dev-libs/gobject-introspection-common-1.50.0 > dev-libs/libatomic_ops-7.6.0 > dev-libs/libbsd-0.8.5 > dev-libs/libcroco-0.6.12-r1 > dev-libs/libestr-0.1.10 > dev-libs/libfastjson-0.99.6 > dev-libs/libgcrypt-1.8.0 > dev-libs/liblogging-1.0.6 > dev-libs/libpcre-8.41 > dev-libs/libpipeline-1.4.1 > dev-libs/libpthread-stubs-0.4 > dev-libs/libtasn1-4.12 > dev-libs/libunistring-0.9.7 > dev-libs/libxml2-2.9.4-r1 > dev-libs/lzo-2.10 > dev-libs/mpc-1.0.3 > dev-libs/mpfr-3.1.5_p2 > dev-libs/nettle-3.3-r1 > dev-libs/nspr-4.15 > dev-libs/openssl-1.1.0f > dev-libs/vala-common-0.34.9 > dev-perl/Locale-gettext-1.70.0 > dev-perl/Module-Build-0.422.400 > dev-perl/SGMLSpm-1.1-r1 > dev-perl/Text-Unidecode-1.300.0 > dev-python/Babel-2.4.0 > dev-python/PySocks-1.6.7 > dev-python/alabaster-0.7.10 > dev-python/asn1crypto-0.22.0 > dev-python/cffi-1.10.0 > dev-python/chardet-3.0.4 > dev-python/docutils-0.13.1 > dev-python/enum34-1.1.6 > dev-python/idna-2.5 > dev-python/imagesize-0.7.1 > dev-python/ipaddress-1.0.18 > dev-python/jinja-2.9.6 > dev-python/markupsafe-0.23 > dev-python/namespace-sphinxcontrib-1.0 > dev-python/ply-3.10 > dev-python/pycparser-2.17 > dev-python/pygments-2.2.0 > dev-python/pytz-2017.2 > dev-python/pyxattr-0.6.0 > dev-python/setuptools-36.0.1 > dev-python/snowballstemmer-1.2.1 > dev-python/sphinx_rtd_theme-0.1.9 > dev-python/whoosh-2.7.4 > dev-util/ctags-20161028 > dev-util/desktop-file-utils-0.23 > dev-util/gdbus-codegen-2.50.3 > dev-util/gperf-3.1 > dev-util/intltool-0.51.0-r2 > dev-util/ninja-1.7.2 > dev-util/re2c-0.16 > media-fonts/encodings-1.0.4-r1 > media-fonts/font-util-1.3.1 > media-fonts/liberation-fonts-2.00.1-r2 > media-libs/fontconfig-2.12.3-r1 > media-libs/freetype-2.8 > media-libs/libjpeg-turbo-1.5.1 > media-libs/libpng-1.6.30 > media-libs/tiff-4.0.8 > net-dns/libidn2-2.0.2 > net-firewall/iptables-1.6.1-r1 > net-libs/gnutls-3.5.14 > net-misc/curl-7.54.1 > net-misc/iputils-20151218 > net-misc/rsync-3.1.2 > sys-apps/baselayout-2.4.1 > sys-apps/busybox-1.26.2-r1 > sys-apps/coreutils-8.27 > sys-apps/debianutils-4.8.1.1 > sys-apps/diffutils-3.6 > sys-apps/ed-1.14.2 > sys-apps/file-5.31 > sys-apps/gawk-4.1.4 > sys-apps/gentoo-functions-0.12 > sys-apps/grep-3.1 > sys-apps/groff-1.22.3 > sys-apps/help2man-1.47.4 > sys-apps/hwids-20170715 > sys-apps/install-xattr-0.5-r1 > sys-apps/iproute2-4.12.0 > sys-apps/kbd-2.0.4 > sys-apps/kmod-24 > sys-apps/less-497 > sys-apps/man-pages-4.11 > sys-apps/net-tools-1.60_p20161110235919 > sys-apps/openrc-0.28 > sys-apps/pciutils-3.5.5 > sys-apps/sandbox-2.10-r4 > sys-apps/sed-4.4 > sys-apps/util-linux-2.30 > sys-boot/efibootmgr-15 > sys-boot/grub-2.02 > sys-devel/autoconf-2.13 > sys-devel/autoconf-2.69-r3 > sys-devel/autoconf-archive-20
[gentoo-user] Which pkg installs /boot/grub?
I was pretty sure that grub2 installed /boot/grub... but I see no such directory after installing grub. qlist grub shows no directory /boot/grub In other installs I seem to recall seeing /boot/grub in place after installing grub. Googling for pkg containing /boot/grub seemd pretty useless as mostly it turns up all piles of stuff staring grub... but I already know pkg grub-2.02 does not contain that directory or the files in it. qfile /boot/grub equery b /boot/grub Before I continue this hard fought fresh install of gentoo into a vbox vm, I'd like to know if I should be seeing a boot grub after these 223 pkgs (which includes grub-2.02) are installed? app-admin/eselect-1.4.9 app-admin/rsyslog-8.28.0 app-arch/libarchive-3.3.1 app-arch/tar-1.29-r3 app-arch/zip-3.0-r3 app-crypt/rhash-1.3.4 app-editors/vim-8.0.0386-r1 app-editors/vim-core-8.0.0386 app-eselect/eselect-ctags-1.18 app-eselect/eselect-fontconfig-1.1-r1 app-eselect/eselect-mesa-0.0.10-r1 app-eselect/eselect-opengl-1.3.1-r4 app-eselect/eselect-vi-1.1.9 app-misc/pax-utils-1.2.2 app-portage/cfg-update-1.8.9 app-portage/eix-0.32.9 app-portage/gentoolkit-0.4.0 app-portage/portage-utils-0.64 app-shells/bash-4.4_p12 app-shells/push-2.0-r1 app-shells/quoter-3.0_p2-r1 app-text/build-docbook-catalog-1.21 app-text/docbook-xml-dtd-4.2-r2 app-text/docbook-xml-dtd-4.4-r2 app-text/opensp-1.5.2-r4 app-vim/gentoo-syntax-20170225 dev-db/sqlite-3.19.3 dev-lang/nasm-2.13.01 dev-lang/perl-5.24.2 dev-lang/python-exec-2.4.5 dev-libs/boehm-gc-7.6.0 dev-libs/expat-2.2.2 dev-libs/gmp-6.1.2 dev-libs/gobject-introspection-common-1.50.0 dev-libs/libatomic_ops-7.6.0 dev-libs/libbsd-0.8.5 dev-libs/libcroco-0.6.12-r1 dev-libs/libestr-0.1.10 dev-libs/libfastjson-0.99.6 dev-libs/libgcrypt-1.8.0 dev-libs/liblogging-1.0.6 dev-libs/libpcre-8.41 dev-libs/libpipeline-1.4.1 dev-libs/libpthread-stubs-0.4 dev-libs/libtasn1-4.12 dev-libs/libunistring-0.9.7 dev-libs/libxml2-2.9.4-r1 dev-libs/lzo-2.10 dev-libs/mpc-1.0.3 dev-libs/mpfr-3.1.5_p2 dev-libs/nettle-3.3-r1 dev-libs/nspr-4.15 dev-libs/openssl-1.1.0f dev-libs/vala-common-0.34.9 dev-perl/Locale-gettext-1.70.0 dev-perl/Module-Build-0.422.400 dev-perl/SGMLSpm-1.1-r1 dev-perl/Text-Unidecode-1.300.0 dev-python/Babel-2.4.0 dev-python/PySocks-1.6.7 dev-python/alabaster-0.7.10 dev-python/asn1crypto-0.22.0 dev-python/cffi-1.10.0 dev-python/chardet-3.0.4 dev-python/docutils-0.13.1 dev-python/enum34-1.1.6 dev-python/idna-2.5 dev-python/imagesize-0.7.1 dev-python/ipaddress-1.0.18 dev-python/jinja-2.9.6 dev-python/markupsafe-0.23 dev-python/namespace-sphinxcontrib-1.0 dev-python/ply-3.10 dev-python/pycparser-2.17 dev-python/pygments-2.2.0 dev-python/pytz-2017.2 dev-python/pyxattr-0.6.0 dev-python/setuptools-36.0.1 dev-python/snowballstemmer-1.2.1 dev-python/sphinx_rtd_theme-0.1.9 dev-python/whoosh-2.7.4 dev-util/ctags-20161028 dev-util/desktop-file-utils-0.23 dev-util/gdbus-codegen-2.50.3 dev-util/gperf-3.1 dev-util/intltool-0.51.0-r2 dev-util/ninja-1.7.2 dev-util/re2c-0.16 media-fonts/encodings-1.0.4-r1 media-fonts/font-util-1.3.1 media-fonts/liberation-fonts-2.00.1-r2 media-libs/fontconfig-2.12.3-r1 media-libs/freetype-2.8 media-libs/libjpeg-turbo-1.5.1 media-libs/libpng-1.6.30 media-libs/tiff-4.0.8 net-dns/libidn2-2.0.2 net-firewall/iptables-1.6.1-r1 net-libs/gnutls-3.5.14 net-misc/curl-7.54.1 net-misc/iputils-20151218 net-misc/rsync-3.1.2 sys-apps/baselayout-2.4.1 sys-apps/busybox-1.26.2-r1 sys-apps/coreutils-8.27 sys-apps/debianutils-4.8.1.1 sys-apps/diffutils-3.6 sys-apps/ed-1.14.2 sys-apps/file-5.31 sys-apps/gawk-4.1.4 sys-apps/gentoo-functions-0.12 sys-apps/grep-3.1 sys-apps/groff-1.22.3 sys-apps/help2man-1.47.4 sys-apps/hwids-20170715 sys-apps/install-xattr-0.5-r1 sys-apps/iproute2-4.12.0 sys-apps/kbd-2.0.4 sys-apps/kmod-24 sys-apps/less-497 sys-apps/man-pages-4.11 sys-apps/net-tools-1.60_p20161110235919 sys-apps/openrc-0.28 sys-apps/pciutils-3.5.5 sys-apps/sandbox-2.10-r4 sys-apps/sed-4.4 sys-apps/util-linux-2.30 sys-boot/efibootmgr-15 sys-boot/grub-2.02 sys-devel/autoconf-2.13 sys-devel/autoconf-2.69-r3 sys-devel/autoconf-archive-2017.03.21 sys-devel/automake-1.13.4-r1 sys-devel/automake-1.15.1 sys-devel/bc-1.07.1 sys-devel/flex-2.6.4 sys-devel/gcc-6.3.0 sys-devel/gcc-config-1.8-r1 sys-devel/gnuconfig-20170101 sys-devel/libtool-2.4.6-r4 sys-devel/llvm-common-4.0.1 sys-devel/m4-1.4.18 sys-devel/make-4.2.1-r1 sys-fs/e2fsprogs-1.43.4 sys-kernel/gentoo-sources-4.12.2 sys-kernel/linux-headers-4.10 sys-libs/binutils-libs-2.28-r1 sys-libs/db-6.0.35-r1 sys-libs/e2fsprogs-libs-1.43.4 sys-libs/efivar-31 sys-libs/gdbm-1.13 sys-libs/glibc-2.24-r3 sys-libs/gpm-1.20.7-r2 sys-libs/libcap-2.25 sys-libs/ncurses-6.0-r1 sys-libs/pam-1.3.0 sys-libs/readline-7.0_p3 sys-libs/timezone-data-2017b sys-process/cronbase-0.3.7-r6 sys-process/procps-3.3.12-r1 sys-process/psmisc-23.1 sys-process
Re: [gentoo-user] a few blockers I can't figure out
gnome-keyring gnome-online-accounts gpm gstreamer gtk gtk3 iconv introspection ipv6 jpeg lcms ldap libnotify libsecret mad mmx mmxext mng modules mp3 mp4 mpeg multilib nautilus ncurses nls nptl nsplugin ogg opengl openmp pam pango pcre pdf png policykit ppds qt3support readline sdl seccomp session spell sse sse2 ssl startup-notification svg systemd tcpd tiff tracker truetype udev udisks unicode upower usb vorbis wxwidgets x264 xcb xml xv xvid zlib" ABI_X86="64" ALSA_CARDS="ali5451 als4000 atiixp atiixp-modem bt87x ca0106 cmipci emu10k1x ens1370 ens1371 es1938 es1968 fm801 hda-intel intel8x0 intel8x0m maestro3 trident usb-audio via82xx via82xx-modem ymfpci" APACHE2_MODULES="actions alias access_compat auth_basic auth_digest authn_anon authn_dbd authn_dbm authn_file authz_dbm authz_groupfile authz_host authz_owner authz_user autoindex cache cgi dav dav_fs dav_lock dbd deflate dir disk_cache env expires ext_filter file_cache filter headers ident imagemap include info log_config logio mime mime_magic negotiation proxy proxy_ajp proxy_connect proxy_http rewrite setenvif so speling status unique_id userdir usertrack vhost_aliasasis authn_alias log_forensic substitute vhost_alias asis log_forensic authn_core authz_core unixd socache_shmcb" APACHE2_MPMS="prefork" CALLIGRA_FEATURES="kexi words flow plan sheets stage tables krita karbon braindump author" CAMERAS="ptp2" COLLECTD_PLUGINS="df interface irq load memory rrdtool swap syslog" CPU_FLAGS_X86="avx mmx mmxext popcnt sse sse2 sse3 sse4_1 sse4_2 ssse3" ELIBC="glibc" GPSD_PROTOCOLS="ashtech aivdm earthmate evermore fv18 garmin garmintxt gpsclock itrax mtk3301 nmea ntrip navcom oceanserver oldstyle oncore rtcm104v2 rtcm104v3 sirf superstar2 timing tsip tripmate tnt ublox ubx" INPUT_DEVICES="keyboard mouse evdev" KERNEL="linux" LCD_DEVICES="bayrad cfontz cfontz633 glk hd44780 lb216 lcdm001 mtxorb ncurses text" LIBREOFFICE_EXTENSIONS="presenter-console presenter-minimizer" OFFICE_IMPLEMENTATION="libreoffice" PHP_TARGETS="php5-4 php5-5 php5-6" PYTHON_SINGLE_TARGET="python2_7" PYTHON_TARGETS="python2_7 python3_4" RUBY_TARGETS="ruby21" USERLAND="GNU" VIDEO_CARDS="nvidia" XTABLES_ADDONS="quota2 psd pknock lscan length2 ipv4options ipset ipp2p iface geoip fuzzy condition tee tarpit sysrq steal rawnat logmark ipmark dhcpmac delude chaos account" USER="root" USERLAND="GNU" USERNAME="root" USE_EXPAND="ABI_MIPS ABI_PPC ABI_S390 ABI_X86 ALSA_CARDS APACHE2_MODULES APACHE2_MPMS CALLIGRA_FEATURES CAMERAS COLLECTD_PLUGINS CPU_FLAGS_X86 CROSSCOMPILE_OPTS CURL_SSL DRACUT_MODULES DVB_CARDS ELIBC ENLIGHTENMENT_MODULES FCDSL_CARDS FFTOOLS FOO2ZJS_DEVICES FRITZCAPI_CARDS GPSD_PROTOCOLS GRUB_PLATFORMS INPUT_DEVICES KERNEL LCD_DEVICES LIBREOFFICE_EXTENSIONS LINGUAS LIRC_DEVICES MONKEYD_PLUGINS NETBEANS_MODULES NGINX_MODULES_HTTP NGINX_MODULES_MAIL OFED_DRIVERS OFFICE_IMPLEMENTATION OPENMPI_FABRICS OPENMPI_OFED_FEATURES OPENMPI_RM PHP_TARGETS PYTHON_SINGLE_TARGET PYTHON_TARGETS QEMU_SOFTMMU_TARGETS QEMU_USER_TARGETS RUBY_TARGETS SANE_BACKENDS USERLAND UWSGI_PLUGINS VIDEO_CARDS VOICEMAIL_STORAGE XFCE_PLUGINS XTABLES_ADDONS" USE_EXPAND_HIDDEN="ABI_MIPS ABI_PPC ABI_S390 CROSSCOMPILE_OPTS ELIBC KERNEL USERLAND" USE_EXPAND_IMPLICIT="ARCH ELIBC KERNEL USERLAND" USE_EXPAND_UNPREFIXED="ARCH" USE_EXPAND_VALUES_ARCH="alpha amd64 amd64-fbsd amd64-linux arm arm-linux arm64 hppa hppa-hpux ia64 ia64-hpux ia64-linux m68k m68k-mint mips nios2 ppc ppc64 ppc64-linux ppc-aix ppc-macos ppc-openbsd riscv s390 sh sparc sparc64-freebsd sparc64-solaris sparc-fbsd sparc-solaris x64-cygwin x64-freebsd x64-macos x64-openbsd x64-solaris x86 x86-cygwin x86-fbsd x86-freebsd x86-interix x86-linux x86-macos x86-netbsd x86-openbsd x86-solaris x86-winnt" USE_EXPAND_VALUES_ELIBC="AIX Cygwin Darwin DragonFly FreeBSD glibc HPUX Interix mintlib musl NetBSD OpenBSD SunOS uclibc Winnt" USE_EXPAND_VALUES_KERNEL="AIX Darwin FreeBSD freemint HPUX linux NetBSD OpenBSD SunOS Winnt" USE_EXPAND_VALUES_USERLAND="BSD GNU" USE_ORDER="env:pkg:conf:defaults:pkginternal:repo:env.d" UUCPLOCK="/var/lock/LCK.." VIDEO_CARDS="nvidia" XDG_CONFIG_DIRS="/etc/xdg" XDG_DATA_DIRS="/usr/local/share:/usr/share:/usr/share/gdm" XDG_RUNTIME_DIR="/run/user/0" XDG_SEAT="seat0" XDG_SESSION_ID="1" XDG_VTNR="1" XTABLES_ADDONS="quota2 psd pknock lscan length2 ipv4options ipset ipp2p iface geoip fuzzy condition tee tarpit sysrq steal rawnat logmark ipmark dhcpmac delude chaos account" grep -r python /etc/portage /etc/portage/package.env:dev-python/pycurl curl.conf /etc/portage/package.use:# move dev-python/twisted dev-python/twisted-core /etc/portage/package.use:dev-python/twisted-core -gtk /etc/portage/package.use:app-accessibility/brltty python usb /etc/portage/package.use:dev-python/jinja -doc /etc/portage/package.use:dev-lang/python tk /etc/portage/package.use:dev-python/dbus-python -doc /etc/portage/package.use:dev-python/pycrypto -doc /etc/portage/package.use:app-accessibility/speech-dispatcher alsa python /etc/portage/package.use:dev-lang/yasm -python /etc/portage/package.use:media-sound/ecasound libsamplerate python /etc/portage/package.use:dev-libs/boost python tools /etc/portage/package.use:sys-libs/talloc python /etc/portage/package.use:media-sound/rhythmbox python python_targets_python3_4 /etc/portage/package.use:dev-python/sphinx -doc /etc/portage/package.use:dev-db/postgresql-server perl python /etc/portage/package.use:dev-db/postgresql python /etc/portage/package.use:sys-apps/systemd python abi_x86_32 -gudev /etc/portage/package.use:sys-libs/tdb python /etc/portage/package.use:sys-libs/ntdb python /etc/portage/package.use:sys-libs/tevent python /etc/portage/package.use:dev-python/pygments -doc /etc/portage/package.use:dev-python/Babel -doc grep -r systemd /etc/portage /etc/portage/package.use:dev-lang/php apache2 bcmath bzip2 cgi curl expat ftp imap mhash mysql odb pcntl postgres sharedmem sockets sysvipc tokenizer xmlrpc xsl zip posix ctype simplexml pdo mysqli hash gd odbc sqlite3 sqlite fpm xmlwriter -systemd /etc/portage/package.use:sys-apps/systemd python abi_x86_32 -gudev -- Your life is like a penny. You're going to lose it. The question is: How do you spend it? John Covici cov...@ccs.covici.com
[gentoo-user] update fails, but I don't see why
ot; 0 KiB [ebuild U ] media-gfx/imagemagick-7.0.10.41-r1:0/7.0.10-37::gentoo [7.0.10.34-r1:0/7.0.10::gentoo] USE="X bzip2 cxx jpeg openmp png postscript tiff zlib -corefonts -djvu -fftw -fontconfig -fpx -graphviz -hdri -heif -jbig -jpeg2k -lcms -lqr -lzma -opencl -openexr -pango -perl -q32 -q8 -raw -static-libs -svg -test -truetype -webp -wmf -xml" 9419 KiB [ebuild R ] sci-libs/gdal-3.0.4-r1:0/3.0::gentoo USE="aux-xml -armadillo -curl -debug -doc -fits -geos -gif -gml -hdf5 -java -jpeg -jpeg2k -lzma (-mdb) -mysql -netcdf -odbc -ogdi -opencl (-oracle) -pdf -perl -png -postgres -python -spatialite -sqlite -threads -webp -xls -zstd" PYTHON_TARGETS="python3_8* -python3_6 -python3_7* -python3_9" 0 KiB [ebuild U ] x11-libs/libXaw-1.0.13-r2::gentoo [1.0.13-r1::gentoo] USE="-deprecated -doc -static-libs" ABI_X86="(64) -32 (-x32)" 0 KiB [ebuild U ] dev-util/cbindgen-0.15.0::gentoo [0.14.6::gentoo] USE="-debug" 3124 KiB [ebuild U ] x11-themes/adwaita-icon-theme-3.36.1-r1::gentoo [3.36.1::gentoo] USE="-branding" 0 KiB [ebuild R ] app-editors/gvim-8.2.0360::gentoo USE="acl nls (-aqua) -cscope -debug -gtk -gtk2 -lua -luajit -motif -neXt -netbeans -perl -python -racket -ruby (-selinux) -session -sound -tcl" PYTHON_SINGLE_TARGET="python3_8* -python3_6 -python3_7*" 0 KiB [ebuild U ] app-text/mupdf-1.18.0-r2:0/1.18.0::gentoo [1.16.1:0/1.16.1::gentoo] USE="X javascript ssl -libressl -opengl (-static-libs%)" 52365 KiB [ebuild U ] x11-apps/xmessage-1.0.5-r1::gentoo [1.0.5::gentoo] 0 KiB [ebuild R ] app-text/asciidoc-9.0.2::gentoo USE="-doc -test" PYTHON_SINGLE_TARGET="python3_8* (-pypy3) -python3_6 -python3_7* -python3_9" 0 KiB [ebuild R ] dev-vcs/subversion-1.14.0-r1::gentoo USE="berkdb nls -apache2 -debug -doc -extras -gnome-keyring -java -kwallet -perl -ruby -sasl -test" 0 KiB [ebuild U ] dev-python/setuptools-50.3.0::gentoo [46.4.0-r3::gentoo] USE="-test" PYTHON_TARGETS="python3_6 python3_7 python3_8* (-pypy3) -python3_9 (-python2_7%*)" 2119 KiB [ebuild R ] dev-python/setuptools_scm-4.1.2-r1::gentoo USE="-test" PYTHON_TARGETS="python3_6 python3_7 python3_8* (-pypy3) -python3_9" 0 KiB [ebuild R ] dev-util/meson-0.55.3::gentoo USE="(-test)" PYTHON_TARGETS="python3_8* -python3_6 -python3_7* -python3_9" 0 KiB [ebuild U ] dev-python/six-1.15.0-r1::gentoo [1.15.0::gentoo] USE="-doc -test" PYTHON_TARGETS="python3_6 python3_7 python3_8* (-pypy3) -python3_9 (-python2_7%*)" 0 KiB [ebuild U ] dev-python/pygments-2.7.2::gentoo [2.7.0::gentoo] USE="-doc -test" PYTHON_TARGETS="python3_8* (-pypy3) -python3_6 -python3_7* -python3_9" 2296 KiB [ebuild U ] dev-python/idna-2.10-r1::gentoo [2.10::gentoo] PYTHON_TARGETS="python3_6 python3_8* (-pypy3) -python3_7* -python3_9 (-python2_7%*)" 0 KiB [ebuild R ] dev-python/pyparsing-2.4.7-r1::gentoo USE="-examples" PYTHON_TARGETS="python3_8* (-pypy3) -python3_6 -python3_7* -python3_9" 0 KiB [ebuild R ] dev-python/markupsafe-1.1.1-r1::gentoo USE="-test" PYTHON_TARGETS="python3_8* (-pypy3) -python3_6 -python3_7* -python3_9" 0 KiB [ebuild U ] dev-python/chardet-3.0.4-r1::gentoo [3.0.4::gentoo] USE="-test" PYTHON_TARGETS="python3_6 python3_8* (-pypy3) -python3_7* -python3_9 (-python2_7%*)" 0 KiB [ebuild U ] dev-python/ply-3.11-r1:0/3.11::gentoo [3.11:0/3.11::gentoo] USE="-examples" PYTHON_TARGETS="python3_6 python3_8* (-pypy3) -python3_7* -python3_9 (-python2_7%*)" 0 KiB [ebuild U ] dev-python/PySocks-1.7.1-r1::gentoo [1.7.1::gentoo] PYTHON_TARGETS="python3_6 python3_8* (-pypy3) -python3_7* -python3_9 (-python2_7%*)" 0 KiB [ebuild R ] dev-python/alabaster-0.7.12::gentoo PYTHON_TARGETS="python3_8* (-pypy3) -python3_6 -python3_7* -python3_9" 0 KiB [ebuild R ] dev-python/imagesize-1.1.0::gentoo USE="-test" PYTHON_TARGETS="python3_8* (-pypy3) -python3_6 -python3_7* -python3_9" 0 KiB [ebuild R ] dev-python/snowballstemmer-2.0.0::gentoo PYTHON_TARGETS="python3_8* (-pypy3) -python3_6 -python3_7* -python3_9" 0 KiB [ebuild R ] dev-python/pytz-2020.1-r1::gentoo PYTHON_TARGETS="python3_8* (-pypy3) -python3_6 -python3_7* -python3_9" 0 KiB [ebuild R ] dev-python/webencodings-0.5.1-r1::gentoo USE="-test" PYTHON_TARGETS="python3_8* (-pypy3) -python3_6 -python3_7* -python3_9" 0 KiB [ebuild R ] dev-python/cython-0.29.21-r1::gentoo USE="-doc -emacs -test" PYTHON_TARGETS="python3_8* (-pypy3) -python3_6 -python3_7* -python3_9" 0 KiB [ebuild R ] dev-util/scons-4.0.1::gentoo USE="-doc -test" PYTHON_TARGETS="python3_8* -python3_6 -python3_7* -python3_
Re: [gentoo-user] update fails, but I don't see why
zma (-mdb) -mysql -netcdf -odbc -ogdi -opencl (-oracle) -pdf -perl -png -postgres -python -spatialite -sqlite -threads -webp -xls -zstd" PYTHON_TARGETS="python3_7 python3_8* -python3_6 -python3_9" 0 KiB [ebuild R ] app-text/asciidoc-9.0.2::gentoo USE="-doc -test" PYTHON_SINGLE_TARGET="python3_8* (-pypy3) -python3_6 -python3_7* -python3_9" 0 KiB [ebuild U ] dev-util/cbindgen-0.15.0::gentoo [0.14.6::gentoo] USE="-debug" 3124 KiB [ebuild R ] app-editors/gvim-8.2.0360::gentoo USE="acl nls (-aqua) -cscope -debug -gtk -gtk2 -lua -luajit -motif -neXt -netbeans -perl -python -racket -ruby (-selinux) -session -sound -tcl" PYTHON_SINGLE_TARGET="python3_8* -python3_6 -python3_7*" 0 KiB [ebuild U ] x11-apps/xmessage-1.0.5-r1::gentoo [1.0.5::gentoo] 0 KiB [ebuild U ] dev-python/setuptools-50.3.0::gentoo [46.4.0-r3::gentoo] USE="-test" PYTHON_TARGETS="python3_6 python3_7 python3_8* (-pypy3) -python3_9 (-python2_7%*)" 2119 KiB [ebuild R ] dev-python/setuptools_scm-4.1.2-r1::gentoo USE="-test" PYTHON_TARGETS="python3_6 python3_7 python3_8* (-pypy3) -python3_9" 0 KiB [ebuild R ] dev-util/meson-0.55.3::gentoo USE="(-test)" PYTHON_TARGETS="python3_7 python3_8* -python3_6 -python3_9" 0 KiB [ebuild U ] dev-python/six-1.15.0-r1::gentoo [1.15.0::gentoo] USE="-doc -test" PYTHON_TARGETS="python3_6 python3_7 python3_8* (-pypy3) -python3_9 (-python2_7%*)" 0 KiB [ebuild U ] dev-python/pygments-2.7.2::gentoo [2.7.0::gentoo] USE="-doc -test" PYTHON_TARGETS="python3_7 python3_8* (-pypy3) -python3_6 -python3_9" 2296 KiB [ebuild U ] dev-python/idna-2.10-r1::gentoo [2.10::gentoo] PYTHON_TARGETS="python3_6 python3_7 python3_8* (-pypy3) -python3_9 (-python2_7%*)" 0 KiB [ebuild R ] dev-python/pyparsing-2.4.7-r1::gentoo USE="-examples" PYTHON_TARGETS="python3_7 python3_8* (-pypy3) -python3_6 -python3_9" 0 KiB [ebuild R ] dev-python/markupsafe-1.1.1-r1::gentoo USE="-test" PYTHON_TARGETS="python3_7 python3_8* (-pypy3) -python3_6 -python3_9" 0 KiB [ebuild U ] dev-python/chardet-3.0.4-r1::gentoo [3.0.4::gentoo] USE="-test" PYTHON_TARGETS="python3_6 python3_7 python3_8* (-pypy3) -python3_9 (-python2_7%*)" 0 KiB [ebuild U ] dev-python/ply-3.11-r1:0/3.11::gentoo [3.11:0/3.11::gentoo] USE="-examples" PYTHON_TARGETS="python3_6 python3_7 python3_8* (-pypy3) -python3_9 (-python2_7%*)" 0 KiB [ebuild U ] dev-python/PySocks-1.7.1-r1::gentoo [1.7.1::gentoo] PYTHON_TARGETS="python3_6 python3_7 python3_8* (-pypy3) -python3_9 (-python2_7%*)" 0 KiB [ebuild R ] dev-python/alabaster-0.7.12::gentoo PYTHON_TARGETS="python3_7 python3_8* (-pypy3) -python3_6 -python3_9" 0 KiB [ebuild R ] dev-python/imagesize-1.1.0::gentoo USE="-test" PYTHON_TARGETS="python3_7 python3_8* (-pypy3) -python3_6 -python3_9" 0 KiB [ebuild R ] dev-python/snowballstemmer-2.0.0::gentoo PYTHON_TARGETS="python3_7 python3_8* (-pypy3) -python3_6 -python3_9" 0 KiB [ebuild R ] dev-python/typed-ast-1.4.1::gentoo USE="-test" PYTHON_TARGETS="python3_7 python3_8* -python3_6 -python3_9" 0 KiB [ebuild R ] dev-python/pytz-2020.1-r1::gentoo PYTHON_TARGETS="python3_7 python3_8* (-pypy3) -python3_6 -python3_9" 0 KiB [ebuild R ] dev-python/webencodings-0.5.1-r1::gentoo USE="-test" PYTHON_TARGETS="python3_7 python3_8* (-pypy3) -python3_6 -python3_9" 0 KiB [ebuild R ] dev-python/cython-0.29.21-r1::gentoo USE="-doc -emacs -test" PYTHON_TARGETS="python3_7 python3_8* (-pypy3) -python3_6 -python3_9" 0 KiB [ebuild R ] dev-util/scons-4.0.1::gentoo USE="-doc -test" PYTHON_TARGETS="python3_7 python3_8* -python3_6 -python3_9" 0 KiB [ebuild R ] dev-python/m2crypto-0.36.0-r1::gentoo USE="-libressl" PYTHON_TARGETS="python3_7 python3_8* -python3_6 -python3_9" 0 KiB [ebuild R ] dev-libs/gobject-introspection-1.64.1-r1::gentoo USE="-doctool -gtk-doc -test" PYTHON_SINGLE_TARGET="python3_8* -python3_6 -python3_7*" 0 KiB [ebuild U ] media-libs/dav1d-0.7.1:0/4::gentoo [0.7.0:0/4::gentoo] USE="10bit 8bit asm" ABI_X86="(64) -32 (-x32)" 630 KiB [ebuild U ] dev-libs/libinput-1.16.3:0/10::gentoo [1.16.1:0/10::gentoo] USE="-doc -test" INPUT_DEVICES="-wacom" 582 KiB [ebuild R ] dev-python/jinja-2.11.2-r1::gentoo USE="-doc -examples -test" PYTHON_TARGETS="python3_7 python3_8* (-pypy3) -python3_6 -python3_9" 0 KiB [ebuild U ] media-libs/babl-0.1.78::gentoo [0.1.74::gentoo] USE="-introspection -lcms -vala%" CPU_FLAGS_X86="mmx sse sse2 -avx2 -f16c -sse3 -sse4_1" 292 KiB [ebuild U ]
Re: [gentoo-user] pcre build failure
ib (-selinux) -skey" 0 KiB > [ebuild U ] sys-libs/pam-1.4.0_p20200829::gentoo > [1.3.1_p20200128-r1::gentoo] USE="berkdb filecaps* pie (split-usr) -audit > -debug -nis (-selinux) (-cracklib%*) (-static-libs%)" ABI_X86="(64) -32 > (-x32)" 0 KiB > [ebuild NS] sys-libs/db-6.0.35-r2:6.0::gentoo [5.3.28-r2:5.3::gentoo] > USE="-cxx -doc -examples -java -tcl -test" ABI_X86="(64) -32 (-x32)" 0 KiB > [ebuild N ] sys-auth/passwdqc-1.4.0-r1::gentoo 0 KiB > [ebuild U ] sys-apps/iproute2-5.8.0::gentoo [5.7.0::gentoo] USE="berkdb > iptables ipv6 -atm -caps -elf -minimal (-selinux)" 0 KiB > [ebuild U ] sys-apps/kbd-2.3.0-r1::gentoo [2.2.0-r2::gentoo] USE="nls > pam -test" 0 KiB > [ebuild N ] dev-python/cython-0.29.21-r1::gentoo USE="-doc -emacs > -test" PYTHON_TARGETS="python3_7 -pypy3 -python3_6 -python3_8 -python3_9" 0 > KiB > [ebuild N ] dev-python/lxml-4.5.2-r1::gentoo USE="threads -doc > -examples -test" PYTHON_TARGETS="python3_7 -pypy3 -python3_6 -python3_8 > -python3_9" 0 KiB > [ebuild N ] app-arch/libarchive-3.4.3:0/13::gentoo USE="acl bzip2 > e2fsprogs iconv lzma threads xattr zlib -blake2 -expat -libressl -lz4 -lzo > -nettle -static-libs -zstd" ABI_X86="(64) -32 (-x32)" 0 KiB > [ebuild U ] dev-libs/openssl-1.1.1h:0/1.1::gentoo [1.1.1g:0/1.1::gentoo] > USE="asm zlib -bindist* -rfc3779 -sctp -sslv3 -static-libs -test > -tls-heartbeat -vanilla" ABI_X86="(64) -32 (-x32)" CPU_FLAGS_X86="(sse2)" 0 > KiB > [ebuild N ] app-crypt/rhash-1.4.0::gentoo USE="nls ssl -debug -libressl > -static-libs" ABI_X86="(64) -32 (-x32)" 0 KiB > [ebuild NS] dev-lang/python-3.9.0_rc2:3.9::gentoo > [2.7.18-r2:2.7::gentoo, 3.7.8-r2:3.7/3.7m::gentoo, 3.8.5:3.8::gentoo] > USE="gdbm ipv6 ncurses readline ssl xml -bluetooth -build -examples -hardened > -libressl -sqlite -test -tk -wininst" 0 KiB > [ebuild U ] sys-libs/glibc-2.32-r2:2.2::gentoo [2.31-r6:2.2::gentoo] > USE="(crypt) multiarch (multilib) ssp (static-libs) -audit -caps (-cet) > -compile-locales -custom-cflags -doc -gd -headers-only -nscd -profile > (-selinux) -static-pie -suid -systemtap -test (-vanilla)" 0 KiB > [ebuild U ] sys-libs/gdbm-1.18.1-r1:0/6::gentoo [1.18.1:0/6::gentoo] > USE="berkdb nls readline -static-libs" ABI_X86="(64) -32 (-x32)" 0 KiB > [ebuild U ] dev-libs/expat-2.2.10::gentoo [2.2.8::gentoo] > USE="(split-usr) unicode -examples -static-libs" ABI_X86="(64) -32 (-x32)" 0 > KiB > [ebuild U ] dev-lang/perl-5.30.3-r1:0/5.30::gentoo > [5.30.3:0/5.30::gentoo] USE="berkdb gdbm -debug -doc -ithreads" 0 KiB > [ebuild U ] sys-devel/automake-1.16.2:1.16::gentoo > [1.16.1-r1:1.16::gentoo] USE="-test%" 0 KiB > [ebuild U ] dev-libs/libgpg-error-1.39::gentoo [1.38::gentoo] USE="nls > -common-lisp" ABI_X86="(64) -32 (-x32)" 0 KiB > [ebuild U ] dev-util/ninja-1.10.1::gentoo [1.10.0::gentoo] USE="-doc > -emacs -test -vim-syntax" 0 KiB > [ebuild U ] app-text/opensp-1.5.2-r6::gentoo [1.5.2-r3::gentoo] USE="nls > -doc -static-libs -test" 0 KiB > [ebuild U ] dev-perl/Unicode-LineBreak-2019.1.0::gentoo > [2017.4.0-r1::gentoo] 0 KiB > [ebuild U ] app-text/po4a-0.61::gentoo [0.57::gentoo] USE="-test" 0 KiB > [ebuild N ] dev-libs/jsoncpp-1.9.4:0/24::gentoo USE="-doc -test" 0 KiB > [ebuild N ] dev-libs/libuv-1.40.0:0/1::gentoo USE="-static-libs" > ABI_X86="(64) -32 (-x32)" 0 KiB > [ebuild N ] dev-util/cmake-3.18.3::gentoo USE="ncurses -doc -emacs -qt5 > -test" 0 KiB > [ebuild N ] app-arch/lz4-1.9.2:0/r132::gentoo USE="-static-libs" > ABI_X86="(64) -32 (-x32)" 0 KiB > [ebuild U ] dev-libs/libksba-1.4.0::gentoo [1.3.5-r1::gentoo] > USE="-static-libs" 0 KiB > [ebuild U ] app-crypt/gnupg-2.2.23::gentoo [2.2.20-r1::gentoo] > USE="bzip2 nls readline smartcard ssl -doc -ldap (-selinux) -tofu -tools -usb > -user-socket -wks-server" 0 KiB > [ebuild U ] app-crypt/libb2-0.98.1-r3::gentoo [0.98.1-r2::gentoo] > USE="openmp -native-cflags -static-libs" ABI_X86="(64) -32 (-x32)" 0 KiB > [ebuild U ] app-crypt/gpgme-1.14.0:1/11::gentoo [1.13.0-r1:1/11::gentoo] > USE="cxx -common-lisp -python -qt5 -static-libs" PYTHON_TARGETS="python3_7 > -python3_6 -python3_8" 0 KiB > [ebuild U ] net-misc/iputils-20200821::gentoo [20190709-r1::gentoo] > USE="arping filecaps* ipv6 nls ssl -caps -clockdiff -
Re: [gentoo-user] update fails, but I don't see why
9 (-python2_7%*)" 0 KiB [ebuild R ] dev-python/pyparsing-2.4.7-r1::gentoo USE="-examples" PYTHON_TARGETS="python3_7 python3_8* (-pypy3) -python3_6 -python3_9" 0 KiB [ebuild R ] dev-python/markupsafe-1.1.1-r1::gentoo USE="-test" PYTHON_TARGETS="python3_7 python3_8* (-pypy3) -python3_6 -python3_9" 0 KiB [ebuild U ] dev-python/chardet-3.0.4-r1::gentoo [3.0.4::gentoo] USE="-test" PYTHON_TARGETS="python3_6 python3_7 python3_8* (-pypy3) -python3_9 (-python2_7%*)" 0 KiB [ebuild U ] dev-python/ply-3.11-r1:0/3.11::gentoo [3.11:0/3.11::gentoo] USE="-examples" PYTHON_TARGETS="python3_6 python3_7 python3_8* (-pypy3) -python3_9 (-python2_7%*)" 0 KiB [ebuild U ] dev-python/PySocks-1.7.1-r1::gentoo [1.7.1::gentoo] PYTHON_TARGETS="python3_6 python3_7 python3_8* (-pypy3) -python3_9 (-python2_7%*)" 0 KiB [ebuild R ] dev-python/alabaster-0.7.12::gentoo PYTHON_TARGETS="python3_7 python3_8* (-pypy3) -python3_6 -python3_9" 0 KiB [ebuild R ] dev-python/imagesize-1.1.0::gentoo USE="-test" PYTHON_TARGETS="python3_7 python3_8* (-pypy3) -python3_6 -python3_9" 0 KiB [ebuild R ] dev-python/snowballstemmer-2.0.0::gentoo PYTHON_TARGETS="python3_7 python3_8* (-pypy3) -python3_6 -python3_9" 0 KiB [ebuild R ] dev-python/typed-ast-1.4.1::gentoo USE="-test" PYTHON_TARGETS="python3_7 python3_8* -python3_6 -python3_9" 0 KiB [ebuild R ] dev-python/pytz-2020.1-r1::gentoo PYTHON_TARGETS="python3_7 python3_8* (-pypy3) -python3_6 -python3_9" 0 KiB [ebuild R ] dev-python/webencodings-0.5.1-r1::gentoo USE="-test" PYTHON_TARGETS="python3_7 python3_8* (-pypy3) -python3_6 -python3_9" 0 KiB [ebuild R ] dev-python/cython-0.29.21-r1::gentoo USE="-doc -emacs -test" PYTHON_TARGETS="python3_7 python3_8* (-pypy3) -python3_6 -python3_9" 0 KiB [ebuild R ] dev-util/scons-4.0.1::gentoo USE="-doc -test" PYTHON_TARGETS="python3_7 python3_8* -python3_6 -python3_9" 0 KiB [ebuild R ] dev-python/m2crypto-0.36.0-r1::gentoo USE="-libressl" PYTHON_TARGETS="python3_7 python3_8* -python3_6 -python3_9" 0 KiB [ebuild R ] dev-libs/gobject-introspection-1.64.1-r1::gentoo USE="-doctool -gtk-doc -test" PYTHON_SINGLE_TARGET="python3_8* -python3_6 -python3_7*" 0 KiB [ebuild U ] media-libs/dav1d-0.7.1:0/4::gentoo [0.7.0:0/4::gentoo] USE="10bit 8bit asm" ABI_X86="(64) -32 (-x32)" 630 KiB [ebuild U ] dev-libs/libinput-1.16.3:0/10::gentoo [1.16.1:0/10::gentoo] USE="-doc -test" INPUT_DEVICES="-wacom" 582 KiB [ebuild R ] dev-python/jinja-2.11.2-r1::gentoo USE="-doc -examples -test" PYTHON_TARGETS="python3_7 python3_8* (-pypy3) -python3_6 -python3_9" 0 KiB [ebuild U ] media-libs/babl-0.1.78::gentoo [0.1.74::gentoo] USE="-introspection -lcms -vala%" CPU_FLAGS_X86="mmx sse sse2 -avx2 -f16c -sse3 -sse4_1" 292 KiB [ebuild U ] dev-libs/jsoncpp-1.9.4:0/24::gentoo [1.9.3:0/24::gentoo] USE="-doc -test" 210 KiB [ebuild U ] dev-python/pycparser-2.20-r1::gentoo [2.20::gentoo] PYTHON_TARGETS="python3_6 python3_7 python3_8* (-pypy3) -python3_9 (-python2_7%*)" 0 KiB [ebuild R ] dev-python/Babel-2.8.0-r2::gentoo USE="-doc -test" PYTHON_TARGETS="python3_7 python3_8* (-pypy3) -python3_6 -python3_9" 0 KiB [ebuild R ] dev-python/docutils-0.16-r1::gentoo PYTHON_TARGETS="python3_7 python3_8* (-pypy3) -python3_6 -python3_9" 0 KiB [ebuild R ] dev-python/packaging-20.4-r1::gentoo USE="-test" PYTHON_TARGETS="python3_7 python3_8* (-pypy3) -python3_6 -python3_9" 0 KiB [ebuild U ] dev-python/lxml-4.6.2::gentoo [4.5.2-r1::gentoo] USE="threads -doc -examples -test" PYTHON_TARGETS="python3_7 python3_8* (-pypy3) -python3_6 -python3_9" 927 KiB [ebuild R ] dev-python/isodate-0.6.0-r1::gentoo USE="-test" PYTHON_TARGETS="python3_6 python3_7 python3_8* (-pypy3) -python3_9% (-python2_7%*)" 0 KiB [ebuild R ] dev-python/html5lib-1.1::gentoo USE="-test" PYTHON_TARGETS="python3_7 python3_8* (-pypy3) -python3_6 -python3_9" 0 KiB [ebuild R ] dev-python/mako-1.1.3-r1::gentoo USE="-doc -test" PYTHON_TARGETS="python3_7 python3_8* (-pypy3) -python3_6 -python3_9" 0 KiB [ebuild U ] sys-auth/pambase-20201103::gentoo [20201013::gentoo] USE="nullok passwdqc sha512 -caps -debug -elogind -gnome-keyring -minimal -mktemp -pam_krb5 -pam_ssh -pwhistory -pwquality -securetty (-selinux) -systemd" 4 KiB [ebuild r U ] app-text/poppler-20.11.0:0/104::gentoo [0.90.1:0/101::gentoo] USE="cairo cxx introspection jpeg jpeg2k lcms tiff utils -cjk -curl -debug -doc -nss -png -qt5" 1610 KiB [ebuild U ]
Re: [gentoo-user] Re: Well, I went about updating my system again. (day 6)
-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,823 KiB
[ebuild R] dev-python/html5lib-0.999-r1::gentoo USE="{-test}"
PYTHON_TARGETS="python2_7 python3_4 python3_5 -pypy -pypy3
(-python3_3%)" 0 KiB
[ebuild U ] virtual/perl-IO-Compress-2.69.1_rc::gentoo
[2.69.0::gentoo] 0 KiB
[ebuild NS] dev-lang/vala-0.34.3:0.34::gentoo [0.30.1:0.30::gentoo,
0.32.1:0.32::gentoo] USE="{-test}" 0 KiB
[ebuild U ] virtual/python-ipaddress-1.0-r1::gentoo [1.0::gentoo]
PYTHON_TARGETS="python2_7 python3_4 python3_5 -pypy -pypy3
(-python3_3%)" 0 KiB
[ebuild U ] dev-python/pycparser-2.17::gentoo [2.14::gentoo]
USE="{-test}" PYTHON_TARGETS="python2_7 python3_4 python3_5 -pypy -pypy3
(-python3_3%)" 226 KiB
[ebuild R] dev-python/jinja-2.8::gentoo USE="-doc -examples"
PYTHON_TARGETS="python2_7 python3_4 python3_5 -pypy -pypy3
(-python3_3%)" 0 KiB
[ebuild R] dev-python/pyasn1-modules-0.0.8::gentoo
PYTHON_TARGETS="python2_7 python3_4 python3_5 -pypy -pypy3
(-python3_3%)" 0 KiB
[ebuild N ] dev-qt/qdbus-5.6.2:5/5.6::gentoo USE="-debug {-test}"
0 KiB
[ebuild U ] dev-libs/libinput-1.5.2:0/10::gentoo
[1.5.0:0/10::gentoo] USE="{-test}" INPUT_DEVICES="-wacom" 905 KiB
[ebuild R] dev-libs/libpwquality-1.3.0::gentoo USE="pam python
-static-libs" PYTHON_TARGETS="python2_7 python3_4 (-python3_3%)" 0 KiB
[ebuild U ] dev-python/python-dateutil-2.6.0::gentoo
[2.5.3::gentoo] PYTHON_TARGETS="python2_7 python3_4 python3_5 -pypy
-pypy3 (-python3_3%)" 253 KiB
[ebuild U ] dev-python/attrs-16.3.0::gentoo [15.2.0::gentoo]
USE="{-test}" PYTHON_TARGETS="python2_7 python3_4 python3_5 -pypy
(-python3_3%)" 57 KiB
[ebuild U ] net-misc/dhcp-4.3.5::gentoo [4.3.4::gentoo] USE="client
ipv6 ldap server ssl -libressl (-selinux) -vim-syntax" 9,840 KiB
[ebuild U ] net-analyzer/nmap-7.31::gentoo [7.30::gentoo] USE="ipv6
nls nse ssl -libressl -ncat -ndiff -nmap-update -nping (-system-lua)
-zenmap" LINGUAS="-de -fr -hi -hr -it -ja -pl -pt_BR -ru -zh"
PYTHON_TARGETS="python2_7" 8,790 KiB
[ebuild R] app-misc/binwalk-2.1.1::gentoo USE="-graph"
PYTHON_TARGETS="python2_7 python3_4 python3_5 (-python3_3%)" 0 KiB
[ebuild U ] net-misc/whois-5.2.13::gentoo [5.2.12::gentoo]
USE="iconv nls -idn" 81 KiB
[ebuild U ] dev-python/pytest-3.0.4::gentoo [3.0.2::gentoo]
USE="-doc% {-test}" PYTHON_TARGETS="python2_7 python3_4 python3_5 -pypy
(-pypy3%) (-python3_3%)" 717 KiB
[ebuild U ] net-misc/dhcpcd-6.11.5::gentoo [6.11.3::gentoo]
USE="embedded ipv6 udev" 194 KiB
[ebuild U ] dev-util/debootstrap-1.0.87::gentoo [1.0.83::gentoo] 65 KiB
[ebuild R] dev-python/pytools-2016.1::gentoo USE="{-test}"
PYTHON_TARGETS="python2_7 python3_4 python3_5 (-python3_3%)" 0 KiB
[ebuild R] dev-python/mako-1.0.3::gentoo USE="-doc {-test}"
PYTHON_TARGETS="python2_7 python3_4 python3_5 -pypy (-python3_3%)" 0 KiB
[ebuild U ] dev-python/pexpect-4.2.1::gentoo [4.0.1::gentoo]
USE="-doc -examples {-test}" PYTHON_TARGETS="python2_7 python3_4
python3_5 -pypy -pypy3 (-python3_3%)" 141 KiB
[ebuild U ] app-text/liblangtag-0.6.2::gentoo [0.6.1::gentoo]
USE="introspection -debug -doc -static-libs {-test}" 749 KiB
[ebuild U ] media-libs/gst-plugins-bad-1.8.3-r1:1.0::gentoo
[1.8.3:1.0::gentoo] USE="X bzip2 egl* gtk introspection nls opengl orc
vcd vnc -gles2 {-test} -wayland" ABI_X86="32 (64) (-x32)" 0 KiB
[ebuild U ] dev-perl/IO-Socket-SSL-2.39.0::gentoo [2.24.0::gentoo]
USE="-examples% -idn" 209 KiB
[ebuild U ] dev-libs/libcdio-paranoia-0.93_p1-r1::gentoo
[0.93_p1::gentoo] USE="cxx -static-libs {-test}" ABI_X86="32* (64)
(-x32)" 0 KiB
[ebuild U ] dev-python/pillow-3.4.2-r1::gentoo [3.1.1::gentoo]
USE="jpeg jpeg2k lcms tiff tk truetype zlib -doc -examples {-test}
-webp" PYTHON_TARGETS="python2_7 python3_4 python3_5 -pypy
(-python3_3%)" 10,784 KiB
[ebuild U ] dev-python/cffi-1.9.1:0/1.9.1::gentoo
[1.8.3:0/1.8.3::gentoo] USE="-doc {-test}" PYTHON_TARGETS="python2_7
python3_4 python3_5" 398 KiB
[ebuild R] dev-python/beautifulsoup-4.5.1:4::gentoo USE="-doc
{-test}" PYTHON_TARGETS="python2_7 python3_4 python3_5 -pypy -pypy3
(-python3_3%)" 0 KiB
[ebuild R] dev-libs/cryptlib-3.4.3::gentoo USE="ldap python -doc
-odbc" PYTHON_TARGETS="python2_7 python3_4 python3_5 -pypy
(-python3_3%)" 0 KiB
[ebuild R] media-video/vcdimager-0.7.24::gentoo USE="xml
-static-libs&q
