1. Forum
  2. Usenet
  3. LINUX.DEBIAN.DEVEL

  • Re: changing existing entries in debian/changelog

    From Andrey Rakhmatullin@21:1/5 to Bastian Venthur on Fri May 24 09:40:01 2024
    On Fri, May 24, 2024 at 09:30:44AM +0200, Bastian Venthur wrote:
    I'm having troubles finding the relevant parts in the developers reference. I've uploaded a version to experimental and later found out that this
    version fixes several bugs.

    Can I rewrite existing changelog entries for already uploaded versions with the next upload, i.e. by adding the relevant "closes" line to the previsions version?
    You can if you want but it won't close the bugs, you'll still need to
    close them properly with manual action. SO it may be easier to just not
    edit them.

    --
    WBR, wRAR

    -----BEGIN PGP SIGNATURE-----

    iQJhBAABCgBLFiEEolIP6gqGcKZh3YxVM2L3AxpJkuEFAmZQQ8ktFIAAAAAAFQAP cGthLWFkZHJlc3NAZ251cGcub3Jnd3JhckBkZWJpYW4ub3JnAAoJEDNi9wMaSZLh 10sP+wfQbtwwApMJEd8kQ4CLnUwgTvohamNLWIMoMGELtpz1sEFsV6vpJKhod7X8 2bDmxH3oMKUz5tXM+/HgHZYPOq4TW4ioQTAt0g+LVv/N4m6L6CTtCBYAIcOwtwaQ Aalt0VDo8duZGv4J0zUYy+6QbdotVURbJRSNIZyYLcFea5CA8BP/boJp6aN/VcXL HrzjapGOGtQ+x3PPaDLsfX7uGlQR64auIfBloraGYO3jFFhuEaRBu7nGa7H+hCQY +pexJbmVHqQPNF6L9s58FYRae5FDyaIXHbioCLnRvnMJtBNTPXSDqHBRQ0Vx3Agp v1SazDNTx/4Aik55Oj7DFQlVSRObAFKjXxbWI9h9OsIVkDVw6yP+K1csiNhWpxZ9 9O3n4buEEqKp7uwROyIuVMLwy8suk+1UpDNxXR1NTy4w7n5tmziW+bF3p4N07vXI XyDwDryzI2kB7n0O8fYI07jcvmxy2xCsqZog+P63WKy6fzhOeIUwNIPi/MLcMrXf cDnDt98jfgaz6UlgnxaRcP3XnExQVQwpc9K8T6Bj/S41vDAmeOPlVslVq54NEgse Yes8Pumb/Mr3oQg0+k0sK/SFq059UGeekIbLQI7rBrasBl5bEs9sXbkd49HxaqlV xMKAGi90eEWOcE400TnPiz506hm81oJ+J2jN1ystPr89824v
    =O1hc
    -----END PGP SIGNATURE-----

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Bastian Venthur@21:1/5 to All on Fri May 24 09:40:01 2024
    Hi,

    I'm having troubles finding the relevant parts in the developers
    reference. I've uploaded a version to experimental and later found out
    that this version fixes several bugs.

    Can I rewrite existing changelog entries for already uploaded versions
    with the next upload, i.e. by adding the relevant "closes" line to the previsions version?


    Cheers,

    Bastian

    --
    Dr. Bastian Venthur https://venthur.de
    Debian Developer venthur at debian org

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Bill Allombert@21:1/5 to All on Fri May 24 11:00:01 2024
    Le Fri, May 24, 2024 at 09:30:44AM +0200, Bastian Venthur a écrit :
    Hi,

    I'm having troubles finding the relevant parts in the developers reference. I've uploaded a version to experimental and later found out that this
    version fixes several bugs.

    Can I rewrite existing changelog entries for already uploaded versions with the next upload, i.e. by adding the relevant "closes" line to the previsions version?

    You need to use the option -v of dpkg-genchanges so that the relevant
    bugs are listed in the .changes file, so that they get automatically
    closed.

    Cheers,
    --
    Bill. <ballombe@debian.org>

    Imagine a large red swirl here.

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Johannes Schauer Marin Rodrigues@21:1/5 to All on Fri May 24 10:30:01 2024
    Quoting Andrey Rakhmatullin (2024-05-24 09:37:45)
    On Fri, May 24, 2024 at 09:30:44AM +0200, Bastian Venthur wrote:
    I'm having troubles finding the relevant parts in the developers reference. I've uploaded a version to experimental and later found out that this version fixes several bugs.

    Can I rewrite existing changelog entries for already uploaded versions with the next upload, i.e. by adding the relevant "closes" line to the previsions
    version?
    You can if you want but it won't close the bugs, you'll still need to
    close them properly with manual action. SO it may be easier to just not edit them.

    When I forget to add the "closes:" line to d/changelog, I will add it retroactively (after having closed the bugs with the correct version manually) because it allows others as well as future-me to look up in d/changelog to which changes correspond to which bugs and bugs will have much more context for a problem than a line in d/changelog.

    Thanks!

    cheers, josch
    --==============W80152057970320833=MIME-Version: 1.0
    Content-Transfer-Encoding: 7bit
    Content-Description: signature
    Content-Type: application/pgp-signature; name="signature.asc"; charset="us-ascii"

    -----BEGIN PGP SIGNATURE-----

    iQIzBAABCgAdFiEElFhU6KL81LF4wVq58sulx4+9g+EFAmZQTiUACgkQ8sulx4+9 g+HS4xAAnslmwhF31FOQpIIjggLFa88AJzva9bZZ4X0BZqaaJltpREq5GIRQOzWo E+pBxH1ywheyQ8KN7hVqv6drX9vvrkK3EUhqNVcQ11IY8KBnC9ImaLy9oCQsLOkX y3M6TG3R8/5u8XvYzOHCD57weKxk9qny4Ncryf9X56SLbkVvLQb5FxjpqOCg9XtN 42Ar11wWHclyInBxoO+TtI1YUxQD+S5+ol+DrnUUlkngdZDdnNzbjA23+e0RaceE 8vgEja+uMUnUsYbFh3jB0lEvqaZPX3Pj0sYfr3NVPfI5WDpGk7eD0sjOvrxkDc2a 87S+WZIM+sFKglc/N55KIlxDeyiyLY9Ai94hx3pNY05AK58wLAWnOHOKl+cwtdVe hl79SKN2cCFsBd0KtLPT111hCjbQ2RHOpOp9U2ze3w/SUPLe1BBf7T7ELedZTUfG Ewv/5i/M5jBPA0Mz2Q0+udMN3NxvHTP7xbADILIimcgWDmsiaT4ek0kMVx61GcpY n2eoenRwyFYFAyZmnmIin7vyWU4hVGUWk4QUS5xEivygo0vFXWgvy8+oEp5zIrK7 tv4IrlMgQF/7l42ccbdYzFePYOBPr+qSwtK95IAg9Gq0xwqY7Y/K0Rg1yeCymebA o3xkn4tlQFTMVCYIc9Fv6Iw0H0GrceZWeQCGrgjZsh7tkja7a0o=
    =shjX
    -----END PGP SIGNATURE-----

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Johannes Schauer Marin Rodrigues@21:1/5 to All on Fri May 24 11:20:01 2024
    Quoting Bill Allombert (2024-05-24 10:54:32)
    Le Fri, May 24, 2024 at 09:30:44AM +0200, Bastian Venthur a écrit :
    Hi,

    I'm having troubles finding the relevant parts in the developers reference. I've uploaded a version to experimental and later found out that this version fixes several bugs.

    Can I rewrite existing changelog entries for already uploaded versions with the next upload, i.e. by adding the relevant "closes" line to the previsions
    version?

    You need to use the option -v of dpkg-genchanges so that the relevant
    bugs are listed in the .changes file, so that they get automatically closed.

    But then they get closed by the wrong version, no? Dev-ref says:

    https://www.debian.org/doc/manuals/developers-reference/pkgs.en.html#when-bugs-are-closed-by-new-uploads

    To close any remaining bugs that were fixed by your upload, email the .changes file to XXX-done@bugs.debian.org, where XXX is the bug number, and put Version: YYY and an empty line as the first two lines of the body of the email, where YYY is the first version where the bug has been fixed.

    When I don't have the .changes file anymore, I just mail XXX-done@bugs.debian.org with a mail that has the "Version: YYY" line at the top and then in the body explains that I'm manually closing it because I made a mistake.

    Thanks!

    cheers, josch
    --==============G95535229724304500=MIME-Version: 1.0
    Content-Transfer-Encoding: 7bit
    Content-Description: signature
    Content-Type: application/pgp-signature; name="signature.asc"; charset="us-ascii"

    -----BEGIN PGP SIGNATURE-----

    iQIzBAABCgAdFiEElFhU6KL81LF4wVq58sulx4+9g+EFAmZQWYcACgkQ8sulx4+9 g+ETlA/+IbiQYFjlA2n9BiFYdE1ZH5bu+XPbI0zLj3fWS2De/r745SO7qGvQ2mDV owsj6VPVrE4wppt+8sclajpeileQHquP5x1wKtaEywmcVpUHxOznMeYwbrJ8HF3S NjQEA6X7ydHwpXcHXhBiHYZrJNZi2XTWmohZYdVqygvrCzxx3ZV6eJKJC7XDqHTR x8/nuVWjPkm/W3Kgmo6oDqQYpFg2qvAPUAFLEIZxRmvWH9CJlVPDECwlVDou+itM jksV8R0QWTi4J9RgbrlxVzmNbFinUFmk5/zGJfRMc+LP9RD1eC19aqpapP+h6CSn jMWufTcUF58t0nYWEAm3FdcQygUO7/1kksKhWIFsa5UP+8TOsN4WOSL60wLCqOFL PAV+4tz39j+VPumcjgVBK7a4dy/Au/BmpKu20UACo9e8cKa+Ln6r6V/gL9UErCbD Jskp9tlS7X8wrm2nFF6uRRB8BahNu2f8H6I7B9ktxV24A5uS9KCKgo8ZDVcV3lUM ZjRkLi9JK7/7g36eomPt7o79IZvGRsWl2E8Cah8Bs2E+C47xm0+4fPhzOuywZ7z5 3M7cf4pzCWLSvAj5zkUodnhSGDRHdn3wU7YYbHCqH7GmA6TAyBZZFGufChPftTlb ukHwsQk80bhjoUt8OIwbqyg2XMhmSdGzHb0FvjrdumgXy58UwkI=
    =cp33
    -----END PGP SIGNATURE-----

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)