Package: dgit Version: 13.13 dgit checks if the package is new in the target suite, and insists on --new.
I think this is a hamfisted way to detect the need to do a with-binaries upload. That's what the option seems to have been for in 0.2 when I introduced it, but it's not clear. But nowadays there's a force message source-only upload, though package appears entirely NEW which tests the flag set by --new as well as looking at the archive. (It's not trying to stop mistaken uploads to the wrong suite, eg unstable when previously experimental, because my workflow has never opened me up to that error, and in dgit 0.2 I wouldn't have been thinking about dch and UNRELEASED.) Changing this might have compatibility implications, but I think it'll be fine in a major release. Ian. -- Ian Jackson <ijack...@chiark.greenend.org.uk> These opinions are my own. Pronouns: they/he. If I emailed you from @fyvzl.net or @evade.org.uk, that is a private address which bypasses my fierce spamfilter.
