Your message dated Mon, 24 Oct 2016 22:27:56 +0200
with message-id <[email protected]>
and subject line Re: Bug#831562: ftp.debian.org: Allow source-only uploads to
NEW when caused by minor changes in binary packaging
has caused the Debian Bug report #831562,
regarding ftp.debian.org: Allow source-only uploads to NEW when caused by minor
changes in binary packaging
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
831562: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=831562
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: ftp.debian.org
Severity: normal
Hi,
I am trying to do a source-only upload [1] of the new rustc. I prefer to do
source-only uploads because I like to have the buildds rebuild my amd64
packages, for safety and security. Other reasons are documented on that page.
With every new version of rustc, we have a new libstd-rust-$version binary
package. This causes every upload to be added to NEW, which triggers the "no
source-only uploads" rule, causing my upload to be REJECTED. IMO this is a bit
pointless - the binary:NEW is not really a significant change, and if I wanted
to "game the system" there are plenty of things I could do whilst keeping the
binary package names the same. I can understand ftp-master wanting to do a
manual audit regardless, but to turn this into an automatic REJECT simply
because I didn't supply binary packages that I built myself, is inconvenient
and defeats the purpose of the SourceOnlyUpload feature.
X
[1] https://wiki.debian.org/SourceOnlyUpload
--- End Message ---
--- Begin Message ---
On 14470 March 1977, Daniel Kahn Gillmor wrote:
>> With every new version of rustc, we have a new libstd-rust-$version binary
>> package. This causes every upload to be added to NEW, which triggers the "no
>> source-only uploads" rule, causing my upload to be REJECTED. IMO this is a
>> bit
>> pointless - the binary:NEW is not really a significant change, and if I
>> wanted
>> to "game the system" there are plenty of things I could do whilst keeping the
>> binary package names the same. I can understand ftp-master wanting to do a
>> manual audit regardless, but to turn this into an automatic REJECT simply
>> because I didn't supply binary packages that I built myself, is inconvenient
>> and defeats the purpose of the SourceOnlyUpload feature.
> I'd like source-only uploads to NEW in general, not just for minor
> changes in binary packaging.
> Looks like it might just be a configuration change
> (Dinstall::AllowSourceOnlyNew) in modern versions of DAK:
> https://anonscm.debian.org/git/mirror/dak.git/tree/daklib/checks.py#n706
> Could we get this for debian's NEW queue?
No. We use the binary packages to review and as such need them.
Actually, if you feel like reopening, do so and set it wontfix.
This could be done if someone sets up and runs an autobuilder for NEW.
As this must be *strictly* limited, it won't integrate into the usual
frameworks. Loads of work. None of us up to it for the forseable future.
--
bye, Joerg
--- End Message ---
