Re: autopkgtest results influencing migration from unstable to testing
- Date: Thu, 3 May 2018 22:15:52 +0200
- From: Paul Gevers <elbrus@xxxxxxxxxx>
- Subject: Re: autopkgtest results influencing migration from unstable to testing
Hi Colin, Ian, On 03-05-18 14:19, Ian Jackson wrote: > Colin Watson writes ("Re: autopkgtest results influencing migration from unstable to testing"): >> On Thu, May 03, 2018 at 07:14:16AM +0200, Paul Gevers wrote: >>> In my perception, the biggest reason is a social one. The is resistance >>> to the fact that issues with autopkgtests out of one's control can block >>> one's package (this is quite different than in Ubuntu). >> >> Can you elaborate on how this is different than in Ubuntu? It sounds >> pretty similar to me, except for being a delay instead of a block. Or >> did you mean that the social consequences are different? > > The key difference is in Paul's sentence "out of one's control". Right. > In Ubuntu, any developer may go and fix any package, without > formality. In Debian fixing "someone else's" package is often hedged > about with bureaucracy or even discouraged. Exactly. Paul
Attachment:
signature.asc
Description: OpenPGP digital signature
- References:
- Re: autopkgtest results influencing migration from unstable to testing
- From: Simon Quigley
- Re: autopkgtest results influencing migration from unstable to testing
- From: Paul Gevers
- Re: autopkgtest results influencing migration from unstable to testing
- From: Colin Watson
- Re: autopkgtest results influencing migration from unstable to testing
- From: Ian Jackson
- Re: autopkgtest results influencing migration from unstable to testing
- Prev by Date: Re: Firefox 60esr on Stretch ?
- Next by Date: Re: Dealing with ci.d.n for package regressions
- Previous by thread: Re: autopkgtest results influencing migration from unstable to testing
- Next by thread: Re: autopkgtest results influencing migration from unstable to testing
- Index(es):