Re: Re: Need a buildd build after trip through NEW -- best practice?
On Thu, 2022-09-01 at 08:45 -0500, Steven Robbins wrote: > OK, so let's call it "bin nmu", then. And add the "+bN" version > suffix. As others said, binNMUs exist, but not for arch:all packages. Debian doesn't yet have sourceful no-change rebuilds, so you have to manually do a sourceful no-change upload (or a regular upload). Ubuntu does tho. dch supports the --rebuild option for this, but only on Ubuntu systems. > This would clearly be optimal. I'm just asking about an additional / > alternative mechanism. Yeah, we need sourceful no-change rebuilds in addition to NEW discarding. The first step would be updating dch to support this, after that the infrastructure can be updated, although I guess the infra could reimplement what `dch --rebuild` does instead. This still needs a volunteer to implement it, so far we have none to do that. -- bye, pabs https://wiki.debian.org/PaulWise signature.asc Description: This is a digitally signed message part
Re: Re: Need a buildd build after trip through NEW -- best practice?
On Thu, Sep 01, 2022 at 08:45:06AM -0500, Steven Robbins wrote: > > > Specficially: in the case of a NEW binary upload, could a manual request > > > be > > > implemented (pick a different name if "give back" is not suitable) such > > > that it is thrown away and replaced by a buildd build? > > > > If you are suggesting the ability for dak to replace binaries already > > in the archive with different content without a new source version, > > then I don't think that should be implemented for Debian at least, > > since our archive is meant to only contain immutable package files. > > OK, so let's call it "bin nmu", then. And add the "+bN" version suffix. Have you seen and ? (and ) -- WBR, wRAR signature.asc Description: PGP signature
Re: Re: Need a buildd build after trip through NEW -- best practice?
Paul Said: > On Sun, 2022-08-28 at 17:54 -0500, Steven Robbins wrote: > > Specficially: in the case of a NEW binary upload, could a manual request > > be > > implemented (pick a different name if "give back" is not suitable) such > > that it is thrown away and replaced by a buildd build? > > If you are suggesting the ability for dak to replace binaries already > in the archive with different content without a new source version, > then I don't think that should be implemented for Debian at least, > since our archive is meant to only contain immutable package files. OK, so let's call it "bin nmu", then. And add the "+bN" version suffix. > The dak software already has an option to enable throwing away all the > binary packages from NEW before they reach the archive, but this option > is not yet enabled on the Debian ftp-master server unfortunately. This would clearly be optimal. I'm just asking about an additional / alternative mechanism. -Steve signature.asc Description: This is a digitally signed message part.
