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="
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:
> &
>
> 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
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*"
;
> >> 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=&q
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
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 fo
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
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
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
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
') (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
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
> 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, b
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
.]
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 grou
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
> a
-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
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(-),
, 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
> > 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
.*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
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
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
>
-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,
3_4(-)?,-python_single_target_pypy(-),-python_single_target_pypy3(-),-python_single_target_python2_7(-),-python_single_target_python3_
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_TA
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
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
equires 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 r
t; 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.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
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&quo
.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*
est" 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%*)&q
s-20200821::gentoo [20190709-r1::gentoo]
> USE="arping filecaps* ipv6 nls ssl -caps -clockdiff -doc -gcrypt -idn
> -libressl -nettle -rarpd -rdisc -static -tftpd -tracepath -traceroute6
> (-SECURITY_HAZARD%)" 0 KiB
> [ebuild U ] app-portage/portage-utils-0.89::gentoo [0.87::g
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
onic_l859 -pccam300 -pccam600 -pentax -polaroid_pdc320
-polaroid_pdc640 -polaroid_pdc700 -ricoh -ricoh_g3 -samsung -sierra
-sipix_blink2 -sipix_web2 -smal -sonix -sony_dscf1 -sony_dscf55
-soundvision -spca50x -sq905 -st2205 -stv0674 -stv0680 -sx330z -topfield
-toshiba_pdrm11 -tp6801" 6,823 KiB
[
38 matches
Mail list logo
