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


Groups > linux.debian.maint.python > #13961

Re: Should we allow Janitor to commit directly to all DPT packages?

From Nilesh Patra <nilesh@riseup.net>
Newsgroups linux.debian.maint.python
Subject Re: Should we allow Janitor to commit directly to all DPT packages?
Date 2022-02-17 22:10 +0100
Message-ID <DRWci-2vmc-5@gated-at.bofh.it> (permalink)
References <DRT4J-2tgC-3@gated-at.bofh.it> <DRV6x-2usV-11@gated-at.bofh.it> <DRW2B-2v2M-1@gated-at.bofh.it>
Organization linux.* mail to news gateway

Show all headers | View raw


[Multipart message — attachments visible in raw view] - view raw

On 2/18/22 2:23 AM, Sandro Tosi wrote:
>> I admit I'm hesitating a bit for different reasons.  While I agree that
>> direct commits are better than MRs I found several DPT packages with
>> very sensible changes in Git but no uploads following these.  For
>> instance fixing VCS fields and Maintainer name should be followed by an
>> according upload to make those changes visible to users and developers
>> of the *packages* in Debian.
>>
>> In the Debian Med team for instance we do those automatic changes before
>> uploading a package - say when upgrading to new upstream versions or
>> fixing some bugs.  Than we run the Janitor scripts and other automatic
>> changes which is all done in routine-update.  I personally find this
>> workflow more convenient.  That way Debian Med team (as well as pkg-r
>> team) are blacklisted for Janitor to not have competing changes inside
>> the package.
> 
> thanks for bringing the perspective of how things are done in the Med
> team, but it feels none of the points you mentioned nor the specific
> Med team workflow apply here,

I suppose the highlight was the usage of routine-update[1] package before upload
and we could use it with DPT too.
This does similar(same?) changes as in janitor.

But that said, I agree with what you wrote:

> or are relevant to just let Janitor
> commit directly to our packages.

I vote a in for/OK for janitor to commit directly as well.

[1]: https://tracker.debian.org/pkg/routine-update

Regards,
Nilesh

Back to linux.debian.maint.python | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread


Thread

Should we allow Janitor to commit directly to all DPT packages? Sandro Tosi <morph@debian.org> - 2022-02-17 18:50 +0100
  Re: Should we allow Janitor to commit directly to all DPT packages? Andreas Tille <andreas@an3as.eu> - 2022-02-17 21:00 +0100
    Re: Should we allow Janitor to commit directly to all DPT packages? Sandro Tosi <morph@debian.org> - 2022-02-17 22:00 +0100
      Re: Should we allow Janitor to commit directly to all DPT packages? Nilesh Patra <nilesh@riseup.net> - 2022-02-17 22:10 +0100
        Re: Should we allow Janitor to commit directly to all DPT packages? Andreas Tille <andreas@an3as.eu> - 2022-02-19 14:30 +0100
  Re: Should we allow Janitor to commit directly to all DPT packages? Sandro Tosi <morph@debian.org> - 2022-03-29 23:50 +0200
    Re: Should we allow Janitor to commit directly to all DPT packages? stefanor@debian.org - 2022-05-24 12:40 +0200
      Re: Should we allow Janitor to commit directly to all DPT packages? Jelmer Vernooij <jelmer@debian.org> - 2022-05-24 12:50 +0200

csiph-web