Your message dated Sat, 27 May 2023 09:19:09 +0000 with message-id <e1q2q4r-00h3qi...@respighi.debian.org> and subject line unblock jed has caused the Debian Bug report #1036787, regarding unblock: jed/0.99.20~pre.178+dfsg-6 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 ow...@bugs.debian.org immediately.) -- 1036787: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1036787 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
--- Begin Message ---Package: release.debian.org Severity: normal User: release.debian....@packages.debian.org Usertags: unblock X-Debbugs-Cc: 1035...@bugs.debian.org, j...@packages.debian.org Control: affects -1 + src:jed Please unblock package jed. The version in unstable fixes the RC bug #1036096. This bug was intended to be fixed in version jed/0.99.20~pre.178+dfsg-5 of the package, but was reopened by Andreas Beckmann, who spotted a problem in the {jed,xjed}.maintscript files, namely the lack of epoch in version numbers. I am attaching to this message the debdiff between versions 0.99.20~pre.178+dfsg-5 and -6. unblock jed/0.99.20~pre.178+dfsg-6 Best, Rafael Laboissièrediff -Nru jed-0.99.20~pre.178+dfsg/debian/changelog jed-0.99.20~pre.178+dfsg/debian/changelog --- jed-0.99.20~pre.178+dfsg/debian/changelog 2023-05-16 14:19:52.000000000 -0300 +++ jed-0.99.20~pre.178+dfsg/debian/changelog 2023-05-25 04:40:36.000000000 -0300 @@ -1,3 +1,15 @@ +jed (1:0.99.20~pre.178+dfsg-6) unstable; urgency=medium + + * d/*.maintscript: Add epoch to the version number in symlink_to_dir setting. + The version in the {jed,xjed}.maintscript files is bumped to + 1:0.99.20~pre.178+dfsg-6~, such that the cleanup is performed on both + upgrades from stable to testing (missed cleanup) and from testing to + unstable (fixed cleanup). + Thanks to Andreas Beckmann for spotting the problem and suggesting its solution. + (Closes: #1036096) + + -- Rafael Laboissière <raf...@debian.org> Thu, 25 May 2023 04:40:36 -0300 + jed (1:0.99.20~pre.178+dfsg-5) unstable; urgency=medium * Add files d/{jed,xjed}.maintscript. diff -Nru jed-0.99.20~pre.178+dfsg/debian/jed.maintscript jed-0.99.20~pre.178+dfsg/debian/jed.maintscript --- jed-0.99.20~pre.178+dfsg/debian/jed.maintscript 2023-05-16 14:19:52.000000000 -0300 +++ jed-0.99.20~pre.178+dfsg/debian/jed.maintscript 2023-05-25 04:32:20.000000000 -0300 @@ -1 +1 @@ -symlink_to_dir /usr/share/doc/jed jed-common 0.99.20~pre.151+dfsg-1~ +symlink_to_dir /usr/share/doc/jed jed-common 1:0.99.20~pre.178+dfsg-6~ diff -Nru jed-0.99.20~pre.178+dfsg/debian/xjed.maintscript jed-0.99.20~pre.178+dfsg/debian/xjed.maintscript --- jed-0.99.20~pre.178+dfsg/debian/xjed.maintscript 2023-05-16 14:19:52.000000000 -0300 +++ jed-0.99.20~pre.178+dfsg/debian/xjed.maintscript 2023-05-25 04:32:11.000000000 -0300 @@ -1 +1 @@ -symlink_to_dir /usr/share/doc/xjed jed-common 0.99.20~pre.151+dfsg-1~ +symlink_to_dir /usr/share/doc/xjed jed-common 1:0.99.20~pre.178+dfsg-6~
--- End Message ---
--- Begin Message ---Unblocked.
--- End Message ---
