Your message dated Tue, 29 Mar 2016 05:18:57 +0000
with message-id <[email protected]>
and subject line Bug#805798: fixed in cl-utilities 1.2.4-3.1
has caused the Debian Bug report #805798,
regarding cl-utilities: Could the version number be increased due to historical 
versions?
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 [email protected]
immediately.)


-- 
805798: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=805798
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: cl-utilities
Version: 1.2.4-1
Severity: wishlist

Dear Maintainer,

I initially noticed cl-utilities when I saw that the latest version
of pg-loader ran into a build failure in Ubuntu and discovered it was
due to a missing package.

I soon found that cl-utilities had existed in both Debian and Ubuntu
previously, but had been removed and now recently re-introduced in
Debian. Therefore I figured a simple fix would be to sync the newer
version to Ubuntu to re-introduce it there as well. However, the sync
failed because the package was rejected.

Looking closer, I see that the new/current version is 1.2.4-1, but
before the package got removed it had reached version 1.2.4-3. The
Debian part of the version number seems to have been reset, which I
guess makes sense when it is effectively re-added. However, the
latter version had also been synced to Ubuntu previously, and it now
rejected a new upload of 1.2.4-1 presumably because it is seen as an
older version number [1].

Would it be possible to increase the version number to 1.2.4-4 to
indicate it is newer than the older packages and make it syncable for
downstream? :)

[1] https://bugs.launchpad.net/ubuntu/+source/cl-utilities/+bug/1511868

-- System Information:
Debian Release: stretch/sid
  APT prefers unstable
  APT policy: (500, 'unstable')
Architecture: amd64 (x86_64)

Kernel: Linux 4.2.0-1-amd64 (SMP w/1 CPU core)
Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

-- no debconf information

--
mvh / best regards
Hans Joachim Desserud
http://desserud.org

--- End Message ---
--- Begin Message ---
Source: cl-utilities
Source-Version: 1.2.4-3.1

We believe that the bug you reported is fixed in the latest version of
cl-utilities, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to [email protected],
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Steve Langasek <[email protected]> (supplier of updated cl-utilities package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing [email protected])


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512

Format: 1.8
Date: Tue, 29 Mar 2016 01:27:57 +0000
Source: cl-utilities
Binary: cl-utilities
Architecture: source all
Version: 1.2.4-3.1
Distribution: unstable
Urgency: medium
Maintainer: Dimitri Fontaine <[email protected]>
Changed-By: Steve Langasek <[email protected]>
Description:
 cl-utilities - collection of Common Lisp utilities
Closes: 805798
Changes:
 cl-utilities (1.2.4-3.1) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * Bump the version number to avoid collisions with other versions
     of cl-utilities that were historically in the Debian archive before
     removal.
   * Switch to source format 3.0 (quilt) so that the package can use an
     orig.tar.xz instead of orig.tar.gz, because the orig.tar.gz that was
     used when reintroduced also doesn't match the one previously in Debian,
     which violates one of the constraints that filenames are always unique
     in a package pool - which will cause problems for release archival
     down the line.
   * Closes: #805798.
Checksums-Sha1:
 ab7c41623456a6417a7132426025afc5661726d7 1758 cl-utilities_1.2.4-3.1.dsc
 2e515ca48450bf76297ba5f0ecbe84f112f509df 20380 cl-utilities_1.2.4.orig.tar.xz
 48bdde8768d2fd4409061fb5e5513d0dbccab202 1848 
cl-utilities_1.2.4-3.1.debian.tar.xz
 d849061535f392bfeab5fdbadba233712c3f840e 22134 cl-utilities_1.2.4-3.1_all.deb
Checksums-Sha256:
 3e2ae70981f055e8fd191440977035fee953515b4b035f86b4563defc6bfce7b 1758 
cl-utilities_1.2.4-3.1.dsc
 de4e24cc95b2a0ba7face86d3acc32820b9add7d195db59ed8a81ad3f6ccb34e 20380 
cl-utilities_1.2.4.orig.tar.xz
 a78f8f9846d894cb91450275aaa26342bfdecbf3a3c5362097b387ca1420a3bf 1848 
cl-utilities_1.2.4-3.1.debian.tar.xz
 4fff04009ea8a97352466afb6a4a4b07180d121a071a0214dbbf1f990e17b547 22134 
cl-utilities_1.2.4-3.1_all.deb
Files:
 0c191a532dd6fae55fa586cd36fe5326 1758 lisp optional cl-utilities_1.2.4-3.1.dsc
 5dc1ae57c9e37455bf04d492cc6670ab 20380 lisp optional 
cl-utilities_1.2.4.orig.tar.xz
 f9156645182a2485a16eb21084bd52ee 1848 lisp optional 
cl-utilities_1.2.4-3.1.debian.tar.xz
 8f43a359e9a848833e9c789c73874494 22134 lisp optional 
cl-utilities_1.2.4-3.1_all.deb

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1

iQIcBAEBCgAGBQJW+gazAAoJEFaNMPMhshM95dYP/jXt0envc6kGL3pJ5BsraKeu
N86NHrw2CSwlIzsFKLpeIdRgT4Ba9av5Nnan3WwJ2orhoKesd+VvMPp56OwnzDAa
Z7Pq9SAHklkFpB/SQSOKSg2WaOJ5VF4KzilbUEoFQtKaowUK1zxsNSGmacYQ80DK
vUJgF9m9YvGhzkrSKAkFh5h5UbNNTSHZf4l+Cst/cGSNvd/D9sF1xVwupY3AEQgX
2OF1erquNvSWZqZ7fCgl38J16b5pmqHI7FO+cfKWB+Eyuy6QkL5Kp57g51ydfwTt
21EfKZ98D95sj4wRL50M5g5I+BQbm3TTGdHXXqoNEn6yIj3p9gjm4DuKG87BdPW1
dvWS0dHqcJPnfBMo1AYcUN4wmpEwVGRLwm7mVsog1ej065AGzrcoaeNAupcm3pFg
LpoqtkgyBCJPLJlJSa8ZqD43KpyP2ccMHl4hkSwbffKDutQmzRD76zbly1hWLKCf
2mGgaXo42RUHtbnSPQ+dCul4zlLXcEf9geUg2M3bUg7DX9uw81dRSkWn4ZvS9cTi
EqiJT/9VFoSFRCRy9jRiGigxTowujexQ9bFthE46d6eXG2rOCpm8rLj2rFYytdWp
PwV8Sq0DHMzrwOYVPCCCuRxBjWrG3ezui4wUqj6OzfjZZn6c6+F8Qu0H5Y7zrBMW
3Z7WhXA3HjAh82b8ZHPX
=whyK
-----END PGP SIGNATURE-----

--- End Message ---

Reply via email to