Bruno, Changing the subject is also mandatory for you - the original mail did not exclude you from this rule :) On Tue, 2016-09-06 at 15:29 +0200, Bruno Friedmann wrote:
Two remarks : gcc6 (6.1.1+r239476 -> 6.2.1+r239849)
So expecting storm rebuild on obs ? and big download afterwards ;-)
Very likely, yes... time for you to call Swisscom and ask for more bandwidth
python-setuptools (23.1.0 -> 26.1.1)
And then why not python3-setupools, it seems blocked on the legal review team, or did I (again :-)) misread the status of the sr ?
You did not, python3-setuptools is indeed in the legal queue (together with some 1500+ ghc packages) python-setuptools did not end up in the legal queue as it did not change the License: tag; python whereas python3-setuptools has a diff like -License: Python-2.0 or ZPL-2.0 +License: MIT Resulting in legal having to validate (and then approve/decline) the chouce.
rebuilding python package for one python2 or python3 shouldn't create a such differenciated publish time, I guess if python2 package is legal ok, then its build on python3 should also be ? (you know how naive I can be right ? :-))
For some reason, the python3-setuptools maintainer now claim it's MIT; the python(2)-setuptools maintainers seem not to share the claim. OTher than that: it's two independent packages, not related in any way and as such are treated independently by any review team.
I'm just afraid of having such differences hiting our targeted developper, administrator final users.
That's something the maintainer should answer - but is, imho, a valid concern (coming from the main thing that we maintain py and py3 code as unrelated stuff in devel:lang:python - I would outright refuse to do so :) ) Cheers, Dominique