build-from-branch into the primary archive

[Scott Kitterman]

On Tuesday, February 22, 2011 12:47:15 am Steve Langasek wrote:
> On Tue, Feb 22, 2011 at 03:57:16PM +1100, Martin Pool wrote:
> > On 22 February 2011 13:59, Scott Kitterman <ubuntu at kitterman.com> wrote:
> > > The alternative of adding a specialized field in debian/control for
> > > packages that should generally only be uploaded from branch so that
> > > anyone who tries to dput the package gets some kind of warning (as
> > > discussed elsewhere in the thread) would, I think, deal with this case
> > > adequately while preserving the option to upload via dput should it
> > > REALLY be necessary in some case.
> > 
> > There seem to be two variables here: does a package upload just give a
> > warning, or does it block; and secondly is this configured in the
> > package metadata itself or in Launchpad.  On the first point I think
> > we absolutely want to have it start out with just a warning.  To be
> > more accurate, we will actually start out with no warnings at all, and
> > probably only turn them on when people feel that particular teams are
> > over the hump of wanting to use it all the time.
> > 
> > Regarding where it is done, I see no problem with doing it in
> > debian/control.  If it's configured in the package itself we would
> > have the option to give a warning at the time people run dput rather
> > than later sending mail back from Soyuz complaining about it.
> 
> If you're going to put it in debian/control, then I think a Vcs-Bzr: field
> pointing at a UDD branch already encodes this information - 'apt-get
> source' already warns about it, we might as well have dput warn on the
> same thing.

Apt-get source already warns on any vcs fields (including Debian ones), so I 
think if you're going to depend on those, then it won't be very effective.  I 
think the idea of some kind of UDD specific 'are you sure' sort of option is 
reasonable.  Failing to consult non-UDD branches doesn't have the same effect.  
It may result in things getting out of sync, but it doesn't result in history 
in the VCS getting over-written.

Scott K

P.S. I see those warning all the time and I confess I almost never look at the 
VCS.  I don't recall it having been a poblem and I don't expect I'll change.  
I suspect I'm not alone in this.