Quoting Jonathan Kamens (2024-09-02 17:52:42) > On 9/2/24 11:47 AM, Colin Watson wrote: > > On Mon, Sep 02, 2024 at 11:15:50AM -0400, Jonathan Kamens wrote: > >> I was suggesting that perhaps the root cause of /why/ the .deb files are > >> not > >> identical is because if there's no timestamp in the trailer line of the top > >> changelog entry, that impacts the contents of the .deb. > > IMO your debian/changelog should be syntactically well-formed (per > > https://www.debian.org/doc/debian-policy/ch-source.html#debian-changelog-debian-changelog) > > even when you haven't finalized it. The exact value of the timestamp > > isn't very important (you can let "dch" pick something when you first > > add something to the unreleased changelog, and "dch -r" will update it > > when you're ready to make an upload), but it should be present. Leaving > > it empty isn't the usual practice among other developers as far as I've > > seen, and it's just making trouble for yourself. > > I leave it empty exactly because the build scripts complain when I do > that, so that I'll remember to finalize it with the correct date before > I put out a release.
The common thing to do to hint that a package is not yet ready for release is to set the distribution to UNRELEASED - which dch handles nicely. (this post is for those reading along that are interested in common practices of Debian developers - if you just wanna do as you've always done then simply ignore this post as it was not written for you). - Jonas -- * Jonas Smedegaard - idealist & Internet-arkitekt * Tlf.: +45 40843136 Website: http://dr.jones.dk/ * Sponsorship: https://ko-fi.com/drjones [x] quote me freely [ ] ask before reusing [ ] keep private
signature.asc
Description: signature
