Re: [gentoo-user] Re: Determine what's keeping Python 3.7 around?
On Mon, 7 Dec 2020 18:40:24 +, antlists wrote: > > I don't think the --oneshot is doing anything here. It just prevents > > adding an atom to the world file when emerging. Besides, in this > > case, you do want it removed (if it was there) because, as you say, > > it will just get pulled in again if it really is needed by something > > else. > > I assume it also stops *removing* an atom from the world file, if it's > something I added. From the man page -oneshot, -1 Emerge as normal, but do not add the packages to the world file for later updating. > And I do it as a matter of course, because it can't > do any harm ... :-) Of course, because t doesn't do anything :) -- Neil Bothwick What do you call a dead bee? - A was. pgp74eqPXm6hz.pgp Description: OpenPGP digital signature
Re: [gentoo-user] Re: Determine what's keeping Python 3.7 around?
On Mon, 7 Dec 2020 18:32:45 - (UTC), Grant Edwards wrote: > > I agree with this one. I often find emerge fails, telling me the > > reason, and then once I've fixed that (usually adding a different > > package or changing some use flags) it fails in exactly the same way > > for a different package. > > Oh yes, on a bad day you can spend hours doing that and accomplish > nothing. :) With the python update, I found that going through the messages and updating packages to only use python3_8 gradually whittled the list down to nothing. > > I know it couldn't find the second set of issues if they were really > > dependent on the first set getting fixed, but they are usually just > > more of the same. > > After a bit you learn to recognize when you're heading down that > road. At that point, I usually just start uninstlling stuff until > emerge is willing to do the update. You sometimes learn the hard why > which packages you absolutely can't remove to try to make emerge > happy. For example, removing dev-lang/python is a bad idea. On the plus side, you won't see any more slot collision messages after doing this ;-) -- Neil Bothwick Okay, who put a "stop payment" on my reality check? pgpkIV0XnCWef.pgp Description: OpenPGP digital signature
Re: [gentoo-user] Re: Determine what's keeping Python 3.7 around?
On 07/12/2020 18:21, Jack wrote: I do an emerge -C --oneshot to uninstall those packages. That way, when emerge finally starts to update world, it pulls them all back (at least, the ones that are needed) itself without me needing to worry about it. I don't think the --oneshot is doing anything here. It just prevents adding an atom to the world file when emerging. Besides, in this case, you do want it removed (if it was there) because, as you say, it will just get pulled in again if it really is needed by something else. I assume it also stops *removing* an atom from the world file, if it's something I added. And I do it as a matter of course, because it can't do any harm ... :-) Cheers, Wol
[gentoo-user] Re: Determine what's keeping Python 3.7 around?
On 2020-12-07, Jack wrote: > I agree with this one. I often find emerge fails, telling me the > reason, and then once I've fixed that (usually adding a different > package or changing some use flags) it fails in exactly the same way > for a different package. Oh yes, on a bad day you can spend hours doing that and accomplish nothing. :) > I know it couldn't find the second set of issues if they were really > dependent on the first set getting fixed, but they are usually just > more of the same. After a bit you learn to recognize when you're heading down that road. At that point, I usually just start uninstlling stuff until emerge is willing to do the update. You sometimes learn the hard why which packages you absolutely can't remove to try to make emerge happy. For example, removing dev-lang/python is a bad idea. -- Grant
Re: [gentoo-user] Re: Determine what's keeping Python 3.7 around?
On 2020.12.07 13:14, antlists wrote: On 07/12/2020 14:30, Grant Edwards wrote: I ended up uninstalling packages mentioned in those 150 lines 2-3 at a time and until emerge was willing to update world. After that I guess I start trying to re-install what was removed. I do an emerge -C --oneshot to uninstall those packages. That way, when emerge finally starts to update world, it pulls them all back (at least, the ones that are needed) itself without me needing to worry about it. I don't think the --oneshot is doing anything here. It just prevents adding an atom to the world file when emerging. Besides, in this case, you do want it removed (if it was there) because, as you say, it will just get pulled in again if it really is needed by something else. This is where I wish there was an option similar to --keep-going, that instead of the dependency calculation aborting when it gets in a mess, it just stops the dependency calculation and emerges what it can. I find just emerging a random selection of the things it says it can, it usually does eventually get there ... I agree with this one. I often find emerge fails, telling me the reason, and then once I've fixed that (usually adding a different package or changing some use flags) it fails in exactly the same way for a different package. I know it couldn't find the second set of issues if they were really dependent on the first set getting fixed, but they are usually just more of the same. Jack
Re: [gentoo-user] Re: Determine what's keeping Python 3.7 around?
On 07/12/2020 14:30, Grant Edwards wrote: I ended up uninstalling packages mentioned in those 150 lines 2-3 at a time and until emerge was willing to update world. After that I guess I start trying to re-install what was removed. I do an emerge -C --oneshot to uninstall those packages. That way, when emerge finally starts to update world, it pulls them all back (at least, the ones that are needed) itself without me needing to worry about it. This is where I wish there was an option similar to --keep-going, that instead of the dependency calculation aborting when it gets in a mess, it just stops the dependency calculation and emerges what it can. I find just emerging a random selection of the things it says it can, it usually does eventually get there ... Cheers, Wol
[gentoo-user] Re: Determine what's keeping Python 3.7 around?
On 2020-12-06, Grant Edwards wrote: > On 2020-12-06, Arve Barsnes wrote: > >> If you have not completed the world update yet, all those are probably >> still installed as 3.7 packages. You could try updating all those to >> 3.8 only first, if you have not done the world update yet. > > I can't update world. > > After adding python3_7 to a bunch of setuptools stuff, it now refuses > to update because conflicting vesions of something are required > resulting in a slot conflict. > > I think it's both setuptools and certifi that have required version > conflicts, but I can't figure out how to determine what's requiring > the older versions of those two. > > At the end of the emerge output is says: > > !!! Multiple package instances within a single package slot have been pulled > !!! into the dependency graph, resulting in a slot conflict: > > and then there's ~150 lines of stuff in which indentation and color > appears to be significant... I ended up uninstalling packages mentioned in those 150 lines 2-3 at a time and until emerge was willing to update world. I don't know exactly which package was the problem, but the update is running. It in includes chromium so it will take a couple days to finish. After that I guess I start trying to re-install what was removed. -- Grant
Re: [gentoo-user] Re: Determine what's keeping Python 3.7 around?
On 2020.12.06 15:50, Grant Edwards wrote: On 2020-12-06, Arve Barsnes wrote: > On Sun, 6 Dec 2020 at 21:25, Grant Edwards wrote: >> > 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. > > If you have not completed the world update yet, all those are probably > still installed as 3.7 packages. You could try updating all those to > 3.8 only first, if you have not done the world update yet. I can't update world. After adding python3_7 to a bunch of setuptools stuff, it now refuses to update because conflicting vesions of something are required resulting in a slot conflict. I think it's both setuptools and certifi that have required version conflicts, but I can't figure out how to determine what's requiring the older versions of those two. At the end of the emerge output is says: !!! Multiple package instances within a single package slot have been pulled !!! into the dependency graph, resulting in a slot conflict: and then there's ~150 lines of stuff in which indentation and color appears to be significant... When I have that type of issue, I get that output into a file, then reduce it to the lines referring to one package/slot only. Then I try to format/unwind the line(s) for each different package being pulled into that slot. Not always, but looking at exactly what is pulling it in often (or at least sometimes) allows me to figure out at least a first step in unraveling the morass. As others have said in this thread, it is often something already installed which is also waiting to be re-emerged - so sometimes finding the ones which can be done first will eliminate some of the conflicts. Also - I try to do the emerge one package at a time (don't forget the -1) so the list of packages with conflicts gets at least somewhat reduced.
[gentoo-user] Re: Determine what's keeping Python 3.7 around?
On 2020-12-06, Arve Barsnes wrote: > On Sun, 6 Dec 2020 at 21:25, Grant Edwards wrote: >> > 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. > > If you have not completed the world update yet, all those are probably > still installed as 3.7 packages. You could try updating all those to > 3.8 only first, if you have not done the world update yet. I can't update world. After adding python3_7 to a bunch of setuptools stuff, it now refuses to update because conflicting vesions of something are required resulting in a slot conflict. I think it's both setuptools and certifi that have required version conflicts, but I can't figure out how to determine what's requiring the older versions of those two. At the end of the emerge output is says: !!! Multiple package instances within a single package slot have been pulled !!! into the dependency graph, resulting in a slot conflict: and then there's ~150 lines of stuff in which indentation and color appears to be significant... -- Grant
Re: [gentoo-user] Re: Determine what's keeping Python 3.7 around?
On 12/6/20 3:25 PM, Grant Edwards wrote: 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 -uDN @world --with-bdeps=y --changed-deps=y --keep-going Run that as well, then run emerge -cpv python:3.7 Check if you have any useflags keeping it around. For me it was mycli and doomsday (at least ones that still would be keeping it around, I think there was another package that has since been updated to have support for 3.8)
Re: [gentoo-user] Re: Determine what's keeping Python 3.7 around?
On Sun, 6 Dec 2020 at 21:25, Grant Edwards wrote: > > 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. If you have not completed the world update yet, all those are probably still installed as 3.7 packages. You could try updating all those to 3.8 only first, if you have not done the world update yet. Regards, Arve
[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/urllib3-1.25.11 requires dev-lang/python:3.7[ssl(+)]
