Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > linux.debian.maint.python > #15812 > unrolled thread

please be more careful about your team uploads

Back to article view | Back to linux.debian.maint.python

Contents

  please be more careful about your team uploads Antoine Beaupré <anarcat@debian.org> - 2024-05-08 16:00 +0200
    Re: please be more careful about your team uploads Alexandre Detiste <alexandre.detiste@gmail.com> - 2024-05-08 16:10 +0200
      Re: please be more careful about your team uploads Alexandre Detiste <alexandre.detiste@gmail.com> - 2024-05-08 16:20 +0200
        Re: please be more careful about your team uploads Antoine Beaupré <anarcat@debian.org> - 2024-05-08 16:20 +0200
          Re: please be more careful about your team uploads Alexandre Detiste <alexandre.detiste@gmail.com> - 2024-05-08 17:30 +0200
        Re: please be more careful about your team uploads Antoine Beaupré <anarcat@debian.org> - 2024-05-08 16:30 +0200
      Re: please be more careful about your team uploads Antoine Beaupré <anarcat@debian.org> - 2024-05-08 16:20 +0200
        Re: please be more careful about your team uploads Antoine Beaupré <anarcat@debian.org> - 2024-05-08 16:40 +0200
        Re: please be more careful about your team uploads Antoine Beaupré <anarcat@debian.org> - 2024-05-08 16:40 +0200
      Re: please be more careful about your team uploads Antoine Beaupré <anarcat@debian.org> - 2024-05-08 16:30 +0200

#15812 — please be more careful about your team uploads

Hi,

I'm working on updating the python-invoke package and see you've done
two uploads on the package:

https://tracker.debian.org/news/1491303/accepted-python-invoke-200-11-source-into-unstable/
https://tracker.debian.org/news/1491393/accepted-python-invoke-200-12-source-into-unstable/

So, first off: thanks for fixing those issues! :)

But, second, could you be a little more careful about how you do those?
Normally, I would have expected those changes to be pushed to salsa so
that I can build on top of.

Or, at the very least, you should have sent a debdiff... The uploads are
a little bizarre too, because they have a NMU-like versionn number
(e.g. 2.0.0-1.1) yet they say "Team upload" on the changelog. Clearly
that should have yielded lintian warnings, did you ignore those?

In any case, i'm now in the rather unfortunate position of having to
retrofit that stuff back in the package, and it's making my life a
little harder than it should...

So please be a little more careful next time around, thanks!

a.

-- 
I know where I am going, and I know the truth,
and I do not have to be what you want me to be.
I am free to be what I want.
                         - Muhammad Ali

[toc] | [next] | [standalone]

#15813

Hi,

That was the very first day I got to work on DPT packages;
so well yes, I did some mistakes at first;
and having been DM for far too long (~10 years) I needed to retrain;
I had so many things stuck in my queue at first.

https://lists.debian.org/debian-python/2023/12/msg00012.html


I'm now going through the ITP's
needed for stalled package updates.

Greetings

Le mer. 8 mai 2024 à 15:58, Antoine Beaupré <anarcat@debian.org> a écrit :
>
> Hi,
>
> I'm working on updating the python-invoke package and see you've done
> two uploads on the package:
>
> https://tracker.debian.org/news/1491303/accepted-python-invoke-200-11-source-into-unstable/
> https://tracker.debian.org/news/1491393/accepted-python-invoke-200-12-source-into-unstable/
>
> So, first off: thanks for fixing those issues! :)
>
> But, second, could you be a little more careful about how you do those?
> Normally, I would have expected those changes to be pushed to salsa so
> that I can build on top of.
>
> Or, at the very least, you should have sent a debdiff... The uploads are
> a little bizarre too, because they have a NMU-like versionn number
> (e.g. 2.0.0-1.1) yet they say "Team upload" on the changelog. Clearly
> that should have yielded lintian warnings, did you ignore those?
>
> In any case, i'm now in the rather unfortunate position of having to
> retrofit that stuff back in the package, and it's making my life a
> little harder than it should...
>
> So please be a little more careful next time around, thanks!
>
> a.

[toc] | [prev] | [next] | [standalone]

#15814

Ok I guess you want to do this one:

https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1008768

[toc] | [prev] | [next] | [standalone]

#15815

On 2024-05-08 16:11:46, Alexandre Detiste wrote:
> Ok I guess you want to do this one:
>
> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1008768

Not really! It's a RFP, if I was going to do it, I would have renamed
that package to "ITP" and reassigned it...

a.

-- 
I would defend the liberty of consenting adult creationists to practice
whatever intellectual perversions they like in the privacy of their own
homes; but it is also necessary to protect the young and innocent.
                        - Arthur C. Clarke

[toc] | [prev] | [next] | [standalone]

#15823

It is now in the NEW queue.

https://salsa.debian.org/python-team/packages/python-pytest-relaxed/-/pipelines/675307

Le mer. 8 mai 2024 à 16:19, Antoine Beaupré <anarcat@debian.org> a écrit :
> On 2024-05-08 16:11:46, Alexandre Detiste wrote:
> > Ok I guess you want to do this one:
> >
> > https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1008768
>
> Not really! It's a RFP, if I was going to do it, I would have renamed
> that package to "ITP" and reassigned it...
>
> a.

[toc] | [prev] | [next] | [standalone]

#15818

On 2024-05-08 16:11:46, Alexandre Detiste wrote:
> Ok I guess you want to do this one:
>
> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1008768

Not really! It's a RFP, if I was going to do it, I would have renamed
that package to "ITP" and reassigned it...

a.

-- 
I would defend the liberty of consenting adult creationists to practice
whatever intellectual perversions they like in the privacy of their own
homes; but it is also necessary to protect the young and innocent.
                        - Arthur C. Clarke

[toc] | [prev] | [next] | [standalone]

#15816

On 2024-05-08 16:08:07, Alexandre Detiste wrote:
> Hi,
>
> That was the very first day I got to work on DPT packages;
> so well yes, I did some mistakes at first;
> and having been DM for far too long (~10 years) I needed to retrain;
> I had so many things stuck in my queue at first.
>
> https://lists.debian.org/debian-python/2023/12/msg00012.html
>
>
> I'm now going through the ITP's
> needed for stalled package updates.

Great to have you onboard, just don't forget to push next time. :)

For what it's worth, my trick for this is i register my local git repos
in myrepos and run "mr status" from time to time, which tells me when i
forget to push. I do try to be particularly more careful when i work on
team packages, especially if i'm not an uploader...

A.

-- 
Only after disaster can we be resurrected.
It's only after you've lost everything that you're free to doanything.
Nothing is static, everything is evolving, everything is falling apart.
                        - Chuck Palahniuk, Fight Club

[toc] | [prev] | [next] | [standalone]

#15819

On 2024-05-08 10:18:27, Antoine Beaupré wrote:
> On 2024-05-08 16:08:07, Alexandre Detiste wrote:
>> Hi,
>>
>> That was the very first day I got to work on DPT packages;
>> so well yes, I did some mistakes at first;
>> and having been DM for far too long (~10 years) I needed to retrain;
>> I had so many things stuck in my queue at first.
>>
>> https://lists.debian.org/debian-python/2023/12/msg00012.html
>>
>>
>> I'm now going through the ITP's
>> needed for stalled package updates.
>
> Great to have you onboard, just don't forget to push next time. :)

Actually, now that I look at the git history, you *did* push changes to
that repository, they're just different from what was uploaded.

I can't make heads or tails out of this.

Could you make sure the python-invoke git repository is in sync with the
archive now please?

A.

[toc] | [prev] | [next] | [standalone]

#15820

On 2024-05-08 10:18:27, Antoine Beaupré wrote:
> On 2024-05-08 16:08:07, Alexandre Detiste wrote:
>> Hi,
>>
>> That was the very first day I got to work on DPT packages;
>> so well yes, I did some mistakes at first;
>> and having been DM for far too long (~10 years) I needed to retrain;
>> I had so many things stuck in my queue at first.
>>
>> https://lists.debian.org/debian-python/2023/12/msg00012.html
>>
>>
>> I'm now going through the ITP's
>> needed for stalled package updates.
>
> Great to have you onboard, just don't forget to push next time. :)

Actually, now that I look at the git history, you *did* push changes to
that repository, they're just different from what was uploaded.

I can't make heads or tails out of this.

Could you make sure the python-invoke git repository is in sync with the
archive now please?

A.

[toc] | [prev] | [next] | [standalone]

#15817

On 2024-05-08 16:08:07, Alexandre Detiste wrote:
> Hi,
>
> That was the very first day I got to work on DPT packages;
> so well yes, I did some mistakes at first;
> and having been DM for far too long (~10 years) I needed to retrain;
> I had so many things stuck in my queue at first.
>
> https://lists.debian.org/debian-python/2023/12/msg00012.html
>
>
> I'm now going through the ITP's
> needed for stalled package updates.

Great to have you onboard, just don't forget to push next time. :)

For what it's worth, my trick for this is i register my local git repos
in myrepos and run "mr status" from time to time, which tells me when i
forget to push. I do try to be particularly more careful when i work on
team packages, especially if i'm not an uploader...

A.

-- 
Only after disaster can we be resurrected.
It's only after you've lost everything that you're free to doanything.
Nothing is static, everything is evolving, everything is falling apart.
                        - Chuck Palahniuk, Fight Club

[toc] | [prev] | [standalone]

Back to top | Article view | linux.debian.maint.python

csiph-web