/srv/irclogs.ubuntu.com/2015/09/25/#bzr.txt

=== r0bby_ is now known as robbyoconnor
bachi all, bzr seems to be missing from pypi this morning.  what's up?12:24
bacjelmer: ^^ ?  (hello, btw!)12:26
* yashi_ still learning the concept of branches12:35
frankbanhi all, anyone know what's happening with "pip install bzr"? It errors with "Could not find any downloads that satisfy the requirement bzr" and  https://pypi.python.org/pypi/bzr/ is a 404 indeed12:38
vilabac, frankban: I've heard confusing news from pypi, can you pinpoint when it started happening ?12:54
bacvila: it worked last night around 2300UTC but i discovered it was missing about one hour ago.12:55
vilabac: excellent, that confirms my suspicion that they broke bzr on pypi very recently12:55
bacyes.  there was the email from pypi about externally hosted files that went out recently. in it they said no action would be taken for three months.  related?12:56
vilabac: you bet12:58
vilabac: I did upload a tarball one year ago and they seem to have completely removed the project12:59
bacvila: do you know who the other pypi maintainers were?13:00
vilabac: https://bugs.launchpad.net/bzr/+bug/132380513:00
ubot5Ubuntu bug 1323805 in Bazaar "bzr is not pip installable" [Critical,Fix released]13:00
vilabac: lifeless and poolie but I think they are screwed as me since the project is nowhere to be seen anymore on pypi13:00
bacvila: so do i read correctly in that bug that bzr 2.6.0 download file was hosted at pypi?13:03
vilabac: you read perfectly right :-/13:04
vilabac: so it seems they removed bzr because old versions weren't hosted on pypi despite the latest (and only relevant one) was13:04
bacvila: so, the email i referenced really should have not been applicable to the project13:04
vilabac: yes, I got the same email and I agree13:04
bacvila: by "they" do you think pypi admins or a bzr maintainer?13:05
vilabac: I replied this morning but no response yet13:05
bacnothing should have happened for a while.  :(13:05
vilabac: pypi, if it's a bzr maintainer..... I would be speechless ;)13:05
vilabac: it's hard enough without saboters ;-D13:05
vilabac: and what's your use case by the way ? (I'm ready for the worse)13:06
bacvila: we have test suites that rely on bzr to be pip installed in a virtualenv.  those projects now fail our CI and are doa at the moment13:07
vilabac: ok, if we're lucky CI is warning us soon enough...13:07
bacabentley, mgz: can either of you shed any light or a way forward on the pypi issue?13:10
abentleyI got the same email, about another project.  I don't know what happened here.13:11
mgz_bac: nope, I have been reading along, seems we need to poke pypi admins13:12
* barry waves13:12
vilabarry: waves as in: you're a pypi admin ?13:13
vilabarry: hi ;)13:13
vilaabentley, mgz_ : hi too ;)13:13
barryvila: i'm not.  i also don't think i am an owner of bzr on pypi13:13
bacbarry: i don't think anyone is now. :)13:13
barryvila: so i don't know what's going on, but two things come to mind13:13
vilabarry: I think I was :-/ Well, I was able to upload13:13
vilabarry: yeah, as bac said, I think nobody is anymore :-(13:14
barry(as i'm sure you know) there was some discussion on the mlist about transfering ownership from mpool.  i never saw a follow up but maybe there was a snafu there13:14
barryvila: do you know: were the tarballs hosted on pypi or externally (i.e. *only* on lp)?13:14
vilabarry: I think it happens at the same time but I'm pretty sure neither lifeless nor poolie checked pypi13:15
vilabarry: all were on lp *EXCEPT* 2.6.0 that was uploaded on pypi a year ago, see https://bugs.launchpad.net/bzr/+bug/132380513:15
ubot5Ubuntu bug 1323805 in Bazaar "bzr is not pip installable" [Critical,Fix released]13:15
barrybzr 2.6.0 still comes up13:16
barryin a search, but the link 404s13:16
vilabarry: yup13:17
vilabarry: may be you know a pypi admin that can be poked ?13:17
barryso, the other thing that is happening recently is that pypi (and the whole stack) will stop chasing external links, so *only* tarballs hosted on pypi will be pip installable.  there are good reasons for this, but it should be something like 6mo away.  just yesterday there were some tests of the email that was going to get sent out.  i wonder if something got deployed too early13:17
vilabarry: that's my gut feeling (something on the pypi side)13:18
vilabac: apart from the CI jobs (juju ?), what could be the impact from your pov ?13:18
dstufftHi13:18
barrydstufft: hi!13:19
viladstufft: \o/13:19
barrydstufft: i'm not a bzr admin on pypi13:19
barrydstufft: only the 2.6.0 tarball was on pypi13:19
dstufftI just registered bzr to my name on PyPI, it was deleted from PyPI by someone named "tanner" on PyPI at 2015-09-24 22:38:3313:19
dstufftthe whole project was deleted13:19
vilaO_o13:19
barrydstufft: so this isn't related to the external tarball thing?13:19
viladstufft: can you revert that ?!?!13:19
dstufftDo you know who tanner is?13:19
barryi don't13:20
bacvila: we have a lot of projects (i'm mostly concerned with juju-ish ones) that rely on bzr.  so they are all affected wrt CI and automated landings13:20
viladstufft: he is/was a bzr contributor, not sure why he had the power to delete the project13:20
dstufftbarry: No, we've not made any actual changes for external tarballs yet, just emailed people to tell them that in 3 months we're going to do a thing13:20
vilabac: right, so the fire is coming, that's what I was afraid about13:20
dstuffttanner might have been spurred on by the email I sent him though13:21
viladstufft: or clicked the wrong button and hiding under his couch right now13:21
barrydstufft: cool.  it was suspicious timing, but it sounds like its unrelated13:21
dstufftanyways, I can't really revert it. I can give it back to you and release all the filenames so you can reupload13:21
dstufftI registere dit to my name so nobody else registered it and put up something malicious13:21
barrydstufft: that sounds like a plan.  vila, bac i'm happy to co-own it if that helps13:22
bacbarry: +113:22
viladstufft: good, I changed my password on pypi this morning in case something was wrong, 'vila', I'll deal with given back the project to the rightful owners13:22
vilabarry: thanks !13:22
dstufftIf you really need it, I can probably fish stuff out of a backup, but that's probably going to burn at least a day for me13:22
dstufftOk13:22
dstufftI'll give vila admin on PyPI and let you take it from there13:23
* vila runs to check if the 2.6.0 pristine tarball is still there13:23
bacvila: should be easier to re-upload than restore from backup, right?13:23
barrysounds good, thanks for the quick response!13:23
bacvila: i saw it on launchpad13:23
vilabac: yes13:23
viladstufft: we've got a plan, thanks so much !13:23
bacthanks everyone13:24
dstufftI just removed myself from the bzr project, so it's all you now vila13:24
dstufftIt'll be just a minute for me to release the filenames13:24
bacvila can you ping me when you think it is restored13:24
dstufft(once a filename is uploaded to PyPI, you can't ever reupload the same filename without me releasing it)13:24
vilabac: you bet I'll ping you to test ;)13:25
bacexcelelnt13:25
viladstufft: crystal clear and matches my expectations13:25
* vila finds the 2.6.0 tarball and starts breathing again13:26
vilanow to find the right setup.py command...13:27
dstufftyou want twine13:27
dstufftsetup.py doesn't let you upload an already created tarball13:28
dstufft(also setup.py is bad)13:28
dstufftanyways, filenames released ^13:28
dstufftgonna drop out of channel, if y'all need anything else feel free to PM me or pop into #python-infra or #pypa(-dev)13:29
viladstufft: ack, thanks, uploading from the web page as I don't want to re-generate/sign a new tarball13:30
vilaInvalid version, cannot be parsed as a valid PEP 440 version. :-(13:32
vilabarry: ^13:34
barryvila: i'll jump over to #python-infra13:36
vilabarry: I'm in #pypa talking with dstufft13:38
barryvila: i'm there now too13:38
vilaicu13:38
vilabac: ping me once your CI jobs get greener just to make sure14:59
bacvila: one just passed CI.  i think we're good15:01

Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!