On September 29, 2023 10:01:45 AM UTC, Adam Borowski
wrote:
>On Thu, Sep 28, 2023 at 03:45:14PM +, Scott Kitterman wrote:
>> On September 28, 2023 3:22:20 PM UTC, Bastian Germann
>> wrote:
>> >Okay. What do you suggest for "team maintained" packages where there is
>> >no active team
On Thu, Sep 28, 2023 at 03:45:14PM +, Scott Kitterman wrote:
> On September 28, 2023 3:22:20 PM UTC, Bastian Germann wrote:
> >Okay. What do you suggest for "team maintained" packages where there is
> >no active team member? File MIA processes for each of the uploaders?
> >And then? The
Hi Bastian,
I'd just want to chime in and confirm what David wrote aleady. When we
wrote the ITS procedure during Debconf Tawain, it was an explicitly designed
that way, that it must not be a way to fast-orphan packages, bypassing
the processes we have for that. This was intentional engineered
On 28/09/23 17:22, Bastian Germann wrote:
Okay. What do you suggest for "team maintained" packages where there is
no active team member?
File MIA processes for each of the uploaders? And then? The MIA team's
bugs are not RC bugs,
An automatic time-based "orphaning + RC" process like the one
On Thu, 28 Sep 2023 17:22:20 +0200,
Bastian Germann wrote:
>Okay. What do you suggest for "team maintained" packages where there is no
>active team member?
>File MIA processes for each of the uploaders? And then? The MIA team's bugs
>are not RC bugs,
>so you cannot even NMU them based on the
On Sep 28, Bastian Germann wrote:
> Okay. What do you suggest for "team maintained" packages where there is no
> active team member?
> File MIA processes for each of the uploaders? And then? The MIA team's bugs
> are not RC bugs,
> so you cannot even NMU them based on the MIA bug.
After having
On September 28, 2023 3:22:20 PM UTC, Bastian Germann wrote:
>Okay. What do you suggest for "team maintained" packages where there is no
>active team member?
>File MIA processes for each of the uploaders? And then? The MIA team's bugs
>are not RC bugs,
>so you cannot even NMU them based on
Okay. What do you suggest for "team maintained" packages where there is no
active team member?
File MIA processes for each of the uploaders? And then? The MIA team's bugs are
not RC bugs,
so you cannot even NMU them based on the MIA bug.
I think, just letting such packages rot for one or two
Hi,
Quoting David Bremner (2023-09-28 16:40:13)
> Bastian Germann writes:
> > Source: nunit
> >
> > I intend to salvage nunit with the plan to orphan it in three weeks.
> > Please notify me if you object.
>
> In my opinion, your repeated "salvaging" of packages in order to orphan
> them is an
Bastian Germann writes:
> Source: nunit
>
> I intend to salvage nunit with the plan to orphan it in three weeks.
> Please notify me if you object.
In my opinion, your repeated "salvaging" of packages in order to orphan
them is an abuse of the ITS process. Yes, it's a clever procedural hack,
but
10 matches
Mail list logo
