On Thu, 26 Apr 2012, Charles Plessy wrote: > Le Wed, Apr 25, 2012 at 04:19:50PM -0700, Don Armstrong a écrit : > > Yes, that's still how the BTS works. Otherwise, the MU is a > > descendant of the previous MU instead of the NMU. You can > > alternatively just include the changelog entries from the NMU too. > > Either works. > > Thanks for the information, I thought it was obsoleted when the > closing of bugs became versioned.
It's a consequence of how versioning works. > Can you describe somewhere what the BTS is doing on that matter ? I do not > understand the rationale and the function. Versioning is a directed acyclic graph. Each version has at most one ancestor, though it may have many descendants. When you upload a maintainer upload (MU) without including the NMU changelog entry, you are indicating that your version is a descendant of the previous MU, not the NMU. That's perfectly ok, but if you've actually fixed bugs that were fixed in the NMU in your MU, you need to include lines in the changelog to that effect, or later on manually fix-up the versions. > Also, I thought that changelog-driven interaction with the BTS was > only carried through dpkg-genchanges and dak... Yes, that's correct. > Can missing acknowledgements be corrected via the email interface ? No. [In the sense that you can't change the DAG after it has been sent from dak to the BTS. You can fix up mistakes in the found/fixed versions, though.] > Are there other direct interactions between a package and the BTS > with its changelog ? The BTS only sees the snippets of the changelog that dak presents to the BTS. [And then the e-mails that dak sends to nnn-close@bdo, but those merely close the bug in a version and don't affect the DAG.] Don Armstrong -- Science is a way of trying not to fool yourself. The first principle is that you must not fool yourself, and you are the easiest person to fool. -- Richard Feynman "What is and What Should be the Role of Scientific Culture in Modern Society"; 1964 http://www.donarmstrong.com http://rzlab.ucr.edu -- To UNSUBSCRIBE, email to debian-policy-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20120426003811.gn3...@rzlab.ucr.edu