[gentoo-dev] News item for review: python-exec package move
Please review the following news item. I would prefer committing it as soon as I get an ACK from all the relevant parties since the issue is hitting users pretty hard. Title: python-exec package move Author: Michał Górny mgo...@gentoo.org Content-Type: text/plain Posted: 2013-xx-xx Revision: 1 News-Item-Format: 1.0 Display-If-Installed: dev-python/python-exec Due to the recent issues which caused dev-python/python-exec:0 being removed prematurely [1], we had to perform an urgent package move. Since we could not use the automatic updates support in portage, users will notice two python-exec packages and possibly blockers. Currently, dev-lang/python-exec is the real package that contains python-exec and that will be used in the future. dev-python/python-exec is kept for compatibility with dependencies in already-installed packages. In the most favorable scenario, the package will be upgraded correctly on your next world update. However, you need to make sure to pass the '--deep' (-D) and '--update' (-u) options to emerge. If you don't want to perform a complete world update, you may as well manually upgrade dev-python/python-exec: emerge -1 dev-python/python-exec This will cause portage to update both python-exec packages and resolve the blockers properly. Please note that if you applied any kind of package-specific modifications to dev-python/python-exec (such as applying keywords through 'package.accept_keywords'), you will need to copy them to dev-lang/python-exec as well. If you applied keywords to dev-python/python-exec in order to unmask Python 3.3 on a stable system, please consider removing the keywords and reading our wiki page that explains how to properly unmask USE flags [2]. We apologize for all the inconveniences. [1]:https://bugs.gentoo.org/show_bug.cgi?id=489440 [2]:https://wiki.gentoo.org/wiki/Python/PYTHON_TARGETS#Unmasking_non-stable_implementation_on_a_stable_system -- Best regards, Michał Górny signature.asc Description: PGP signature
Re: [gentoo-dev] News item for review: python-exec package move
On Wed, 6 Nov 2013 16:12:47 +0100 Michał Górny mgo...@gentoo.org wrote: Please note that if you applied any kind of package-specific ^ have applied If you applied keywords to dev-python/python-exec in order to unmask ^ have applied Python 3.3 on a stable system, please consider removing the keywords ^ these Other than that it looks perfect; it also seems to take into account the users having problems in the forums [1], for which the original instructions you gave did not appear to work. +1 for the details! :) [1]: http://forums.gentoo.org/viewtopic-t-974412.html -- With kind regards, Tom Wijsman (TomWij) Gentoo Developer E-mail address : tom...@gentoo.org GPG Public Key : 6D34E57D GPG Fingerprint : C165 AF18 AB4C 400B C3D2 ABF0 95B2 1FCD 6D34 E57D signature.asc Description: PGP signature
Re: [gentoo-dev] News item for review: python-exec package move
On Wed, Nov 6, 2013 at 4:12 PM, Michał Górny mgo...@gentoo.org wrote: Please review the following news item. I would prefer committing it as soon as I get an ACK from all the relevant parties since the issue is hitting users pretty hard. LGTM. I have two questions that should not block this news item from going live: - I tend to upgrade with emerge -uavD --changed-use world, and this didn't solve the blocker for me by itself. I had to emerge -C python-exec, then run the upgrade to get it to work. Yet the news item seems to state that -uD should have been enough. - How come we did not think this news item was necessary before we did the package move? Obviously everything would have been better had this news item gone out with the package move, instead of one week later. Cheers, Dirkjan
Re: [gentoo-dev] News item for review: python-exec package move
Dnia 2013-11-06, o godz. 18:14:57 Dirkjan Ochtman d...@gentoo.org napisał(a): On Wed, Nov 6, 2013 at 4:12 PM, Michał Górny mgo...@gentoo.org wrote: Please review the following news item. I would prefer committing it as soon as I get an ACK from all the relevant parties since the issue is hitting users pretty hard. LGTM. I have two questions that should not block this news item from going live: - I tend to upgrade with emerge -uavD --changed-use world, and this didn't solve the blocker for me by itself. I had to emerge -C python-exec, then run the upgrade to get it to work. Yet the news item seems to state that -uD should have been enough. Well, I have no idea why this happens for some people. Unless you were playing with keywords, it simply should work. - How come we did not think this news item was necessary before we did the package move? Obviously everything would have been better had this news item gone out with the package move, instead of one week later. I think we focused on my little testing that showed that portage can handle blockers with '-uD' and assumed users will be able to understand the blocker message. -- Best regards, Michał Górny signature.asc Description: PGP signature
Re: [gentoo-dev] News item for review: python-exec package move
Update 1: - applied comments from TomWij, - changed the wording to reflect that 'emerge @world' may not work, - shortened the wiki URI, - added contact info in case of more issues. Title: python-exec package move Author: Michał Górny mgo...@gentoo.org Content-Type: text/plain Posted: 2013-11-07 Revision: 1 News-Item-Format: 1.0 Display-If-Installed: dev-python/python-exec Due to the recent issues which caused dev-python/python-exec:0 to be removed prematurely [1], we had to perform an urgent package move. Since we could not use the automatic updates support in portage, users will notice two python-exec packages and possibly blockers. Currently, dev-lang/python-exec is the real package that contains python-exec and that will be used in the future. dev-python/python-exec is a virtual package that is kept for compatibility with dependencies in already-installed packages. In the most favorable scenario, the package will be upgraded correctly on your next world update if you use the '--deep' (-D) and '--update' (-u) options. If you don't want to perform a complete world update or if it fails for you, you may as well manually upgrade dev-python/python-exec: emerge -1 dev-python/python-exec This will cause portage to update both python-exec packages and resolve the blockers properly. Please note that if you have applied any kind of package-specific modifications to dev-python/python-exec (such as applying keywords through 'package.accept_keywords'), you will need to copy them to dev-lang/python-exec as well. If you have applied keywords to dev-python/python-exec in order to unmask Python 3.3 on a stable system, please consider removing the keywords and reading our wiki page that explains how to properly unmask USE flags [2]. We apologize for all the inconveniences. If you have any more issues with python-exec, please do not hesitate to contact as at #gentoo-python IRC channel (@freenode) or the gentoo-pyt...@lists.gentoo.org mailing list. [1]:https://bugs.gentoo.org/show_bug.cgi?id=489440 [2]:https://wiki.gentoo.org/wiki/Unmasking_non-stable_Python_implementations -- Best regards, Michał Górny signature.asc Description: PGP signature
Re: [gentoo-dev] News item for review: python-exec package move
El mié, 06-11-2013 a las 18:20 +0100, Michał Górny escribió: Dnia 2013-11-06, o godz. 18:14:57 Dirkjan Ochtman d...@gentoo.org napisał(a): On Wed, Nov 6, 2013 at 4:12 PM, Michał Górny mgo...@gentoo.org wrote: Please review the following news item. I would prefer committing it as soon as I get an ACK from all the relevant parties since the issue is hitting users pretty hard. LGTM. I have two questions that should not block this news item from going live: - I tend to upgrade with emerge -uavD --changed-use world, and this didn't solve the blocker for me by itself. I had to emerge -C python-exec, then run the upgrade to get it to work. Yet the news item seems to state that -uD should have been enough. Well, I have no idea why this happens for some people. Unless you were playing with keywords, it simply should work. - How come we did not think this news item was necessary before we did the package move? Obviously everything would have been better had this news item gone out with the package move, instead of one week later. I think we focused on my little testing that showed that portage can handle blockers with '-uD' and assumed users will be able to understand the blocker message. I have also had strange blockers, maybe due python-3.3 (but I have unmasked it properly I think :/). I only could resolve it by installing: dev-lang/python-exec-0. I don't understand why 0.3.1 isn't enough :(
Re: [gentoo-dev] News item for review: python-exec package move
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On 06/11/13 02:56 PM, Pacho Ramos wrote: El mié, 06-11-2013 a las 18:20 +0100, Michał Górny escribió: Dnia 2013-11-06, o godz. 18:14:57 Dirkjan Ochtman d...@gentoo.org napisał(a): On Wed, Nov 6, 2013 at 4:12 PM, Michał Górny mgo...@gentoo.org wrote: Please review the following news item. I would prefer committing it as soon as I get an ACK from all the relevant parties since the issue is hitting users pretty hard. LGTM. I have two questions that should not block this news item from going live: - I tend to upgrade with emerge -uavD --changed-use world, and this didn't solve the blocker for me by itself. I had to emerge -C python-exec, then run the upgrade to get it to work. Yet the news item seems to state that -uD should have been enough. Well, I have no idea why this happens for some people. Unless you were playing with keywords, it simply should work. - How come we did not think this news item was necessary before we did the package move? Obviously everything would have been better had this news item gone out with the package move, instead of one week later. I think we focused on my little testing that showed that portage can handle blockers with '-uD' and assumed users will be able to understand the blocker message. I have also had strange blockers, maybe due python-3.3 (but I have unmasked it properly I think :/). I only could resolve it by installing: dev-lang/python-exec-0. I don't understand why 0.3.1 isn't enough :( I run mostly mixed-keywords systems, and i noticed that the blocker messages were entirely useless and confusing, but that i just needed to keyword dev-lang/python-exec due to the fact that it was in the deplist of one of my other keyworded packages. After I did that emerge -uDN @world just worked. Note that dev-python/python-exec had already been keyworded for the same reason, and I didn't remove that keyword. -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.22 (GNU/Linux) iF4EAREIAAYFAlJ6oAYACgkQ2ugaI38ACPA2SQD/V/u5DJLPjgYblMpmgOQWSUm6 xlJlC+YOyh2MKekWRdsBAJqjMgqeK3UJlkMbcN4G1JTzs883ugMaeq8ZeKES4lmq =QEMm -END PGP SIGNATURE-
