Re: Fwd: My deep mistake with the python-absl package

2021-04-19 Thread Arturo Borrero Gonzalez




On 4/19/21 12:54 PM, Mattia Rizzolo wrote:

Hi Arturo,

On Mon, Apr 19, 2021 at 03:46:55PM +0500, Andrey Rahmatullin wrote:

On Mon, Apr 19, 2021 at 11:12:01AM +0200, Arturo Borrero Gonzalez wrote:

* We could upload a new version of python-absl and just replace/overwrite my
upload. I noticed your original repo [0] contains a pretty up-to-date
version that could work.


I'm not the package maintainer but I'd suggest either rolling back to the
contents of 0.11.0-1 (pro: we are frozen; con: unlikely that the second
upload breaks anything as the package is not in testing and doesn't have
revdeps) or just uploading 0.12.0-2 based on 0.11.0-1, integrating
improvements from 0.12.0-1 if needed.
There is also a question of the salsa repo history, not sure if it should
contain 0.12.0-1 or not (pro: having all versions in the repo, no
confusion over the missing version; con: confusion over two uploads each
rewriting the previous one).


If you are fine, I can take this approach.  I'll include your 0.12.0-1
upload in the repository, merge them both, give back maintership to the
DPT and whoever was in Uploaders, and upload the final as 0.12.0-2.  I
don't think there is any gain whatsoever in rolling back to 0.11.0 at
this point.
Lastly, I'll ask the salsa admins to remove the repository you created
in the /debian/ space.

If you are interested in this package I recommend you join the DPT then
:)



Your proposal sounds right to me Mattia.

Please go ahead!

regards.



Re: Fwd: My deep mistake with the python-absl package

2021-04-19 Thread Mattia Rizzolo
Hi Arturo,

On Mon, Apr 19, 2021 at 03:46:55PM +0500, Andrey Rahmatullin wrote:
> On Mon, Apr 19, 2021 at 11:12:01AM +0200, Arturo Borrero Gonzalez wrote:
> > * We could upload a new version of python-absl and just replace/overwrite my
> > upload. I noticed your original repo [0] contains a pretty up-to-date
> > version that could work.
>
> I'm not the package maintainer but I'd suggest either rolling back to the
> contents of 0.11.0-1 (pro: we are frozen; con: unlikely that the second
> upload breaks anything as the package is not in testing and doesn't have
> revdeps) or just uploading 0.12.0-2 based on 0.11.0-1, integrating
> improvements from 0.12.0-1 if needed.
> There is also a question of the salsa repo history, not sure if it should
> contain 0.12.0-1 or not (pro: having all versions in the repo, no
> confusion over the missing version; con: confusion over two uploads each
> rewriting the previous one).

If you are fine, I can take this approach.  I'll include your 0.12.0-1
upload in the repository, merge them both, give back maintership to the
DPT and whoever was in Uploaders, and upload the final as 0.12.0-2.  I
don't think there is any gain whatsoever in rolling back to 0.11.0 at
this point.
Lastly, I'll ask the salsa admins to remove the repository you created
in the /debian/ space.

If you are interested in this package I recommend you join the DPT then
:)

-- 
regards,
Mattia Rizzolo

GPG Key: 66AE 2B4A FCCF 3F52 DA18  4D18 4B04 3FCD B944 4540  .''`.
More about me:  https://mapreri.org : :'  :
Launchpad user: https://launchpad.net/~mapreri  `. `'`
Debian QA page: https://qa.debian.org/developer.php?login=mattia  `-


signature.asc
Description: PGP signature


Re: Fwd: My deep mistake with the python-absl package

2021-04-19 Thread Andrey Rahmatullin
On Mon, Apr 19, 2021 at 11:12:01AM +0200, Arturo Borrero Gonzalez wrote:
> There may be 2 other options:
> * I could ask ftp-masters to drop my upload, not sure if that's something
> they can do. [spoiler: on IRC #debian-ftp they pointed me to talk to you]
It's already in sid: https://buildd.debian.org/status/package.php?p=python-absl
so it cannot be "dropped".

> * We could upload a new version of python-absl and just replace/overwrite my
> upload. I noticed your original repo [0] contains a pretty up-to-date
> version that could work.
I'm not the package maintainer but I'd suggest either rolling back to the
contents of 0.11.0-1 (pro: we are frozen; con: unlikely that the second
upload breaks anything as the package is not in testing and doesn't have
revdeps) or just uploading 0.12.0-2 based on 0.11.0-1, integrating
improvements from 0.12.0-1 if needed.
There is also a question of the salsa repo history, not sure if it should
contain 0.12.0-1 or not (pro: having all versions in the repo, no
confusion over the missing version; con: confusion over two uploads each
rewriting the previous one).

-- 
WBR, wRAR


signature.asc
Description: PGP signature


Fwd: My deep mistake with the python-absl package

2021-04-19 Thread Arturo Borrero Gonzalez

Forwarding this email here, I used the tracker.d.o address but got no reply so 
far.

Also, an update to what's stated below:

I issued the dcut command to rm my upload, but apparently the package already 
landed in the archive for good, and dcut did nothing (again, apparently).


There may be 2 other options:
* I could ask ftp-masters to drop my upload, not sure if that's something they 
can do. [spoiler: on IRC #debian-ftp they pointed me to talk to you]
* We could upload a new version of python-absl and just replace/overwrite my 
upload. I noticed your original repo [0] contains a pretty up-to-date version 
that could work.


Let me know, regards.

[0] https://salsa.debian.org/python-team/packages/python-absl

 Forwarded Message 
Subject: My deep mistake with the python-absl package
Date: Sun, 18 Apr 2021 21:04:28 +0200
From: Arturo Borrero Gonzalez 
To: Romain Porte 
CC: Debian Python Team 

Hi there,

I made an ugly mistake today. While packaging capirca [0] I noticed it depended 
on python-absl. On a quick search I didn't find python-absl on Debian (mistake, 
only checked testing), so I created an ITP [1] for it, a salsa repository [2], 
and then uploaded it to the debian archive [3], in parallel with capirca.


I was expecting python-absl to hit NEW (I thought it was a brand new package) so 
when it was accepted right-away by the ftp-master process I noticed my ugly 
mistake... python-absl already existed and I just uploaded a new version!


I'm deeply sorry about this. I was never my intention to hijack, or diminish 
your work in any way.


Possibly the proper thing to do now is to drop my upload from debian using dcut, 
and that's what I will try once I hit the send button for this email. I would 
need to check the workflow first because I've not used that for ages. I wanted 
to contact you by email to make sure you were aware of the situation.


I'm really sorry for all this noise.

regards.

[0] https://ftp-master.debian.org/new/capirca_2.0.3-1.html
[1] https://bugs.debian.org/987152
[2] https://salsa.debian.org/debian/pkg-python-absl
[3] 
https://tracker.debian.org/news/1239179/accepted-python-absl-0120-1-source-all-into-unstable/