Your message dated Wed, 06 Jul 2016 11:33:59 +0000
with message-id <e1bkl5b-00084r...@franck.debian.org>
and subject line Bug#797706: fixed in debram 2.0.0.5
has caused the Debian Bug report #797706,
regarding debram: illegal date format in debian/changelog
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.)


-- 
797706: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=797706
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: debram
Severity: serious
Version: 2.0.0.4
Justification: Policy 4.4

Hi,

The latest changelog entry of debram has an illegal date format which
causes dpkg-parsechangelog to choke (and thus the package to FTBFS).

 -- Thaddeus H. Black <t...@debian.org>  Fri, 26 June 2015 00:00:00 +0000
                                                ^^^^

Policy 4.4 requires the month to contain exactly 3 characters.

Failed mips64el build log:
https://buildd.debian.org/status/fetch.php?pkg=debram&arch=mips64el&ver=2.0.0.4&stamp=1441108414

Thanks,
James

Attachment: signature.asc
Description: This is a digitally signed message part


--- End Message ---
--- Begin Message ---
Source: debram
Source-Version: 2.0.0.5

We believe that the bug you reported is fixed in the latest version of
debram, 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 797...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Thaddeus H. Black <t...@debian.org> (supplier of updated debram 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 ftpmas...@ftp-master.debian.org)


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

Format: 1.8
Date: Wed, 06 Jul 2016 00:00:00 +0000
Source: debram
Binary: debram debram-data
Architecture: source all amd64
Version: 2.0.0.5
Distribution: unstable
Urgency: low
Maintainer: Thaddeus H. Black <t...@debian.org>
Changed-By: Thaddeus H. Black <t...@debian.org>
Description:
 debram     - ramified catalog of available commands
 debram-data - debram's architecture-independent data
Closes: 797706
Changes:
 debram (2.0.0.5) unstable; urgency=low
 .
   * Reuploaded, changing only this file.  Reason: the last upload had
     in this file been dated "June" rather than "Jun" (closes: #797706).
Checksums-Sha1:
 3e4b3e6a094818cea8690416016f636fb3653207 1464 debram_2.0.0.5.dsc
 7219b0778649c88ac6f141a8e34a8566becc35f1 123207 debram_2.0.0.5.tar.gz
 1f17e1486156f1bb7a8796afe2564e78dd00e9a5 56150 debram-data_2.0.0.5_all.deb
 f4dab58b162fb5950c0fd17315a94df23590b2d3 14266 debram_2.0.0.5_amd64.deb
Checksums-Sha256:
 7b6f9e4203472de97ef1b9b30a81e0704f604ce681682f5c51052fbb6b93a2d7 1464 
debram_2.0.0.5.dsc
 cdb586d734b5aec2b341a0100c4a6ed597acfb538739bd68be903215193b17ec 123207 
debram_2.0.0.5.tar.gz
 9103bf2dc044e737fa99dc008222fad660b3ae8865334ca7784bf8cf98338c01 56150 
debram-data_2.0.0.5_all.deb
 45b7df33c9c7f595f600a0a67f2b5cd6e5b89267236773b8bec1a8b6c39919ed 14266 
debram_2.0.0.5_amd64.deb
Files:
 303b2d321fb8ffce80d52bdfd16775d1 1464 admin optional debram_2.0.0.5.dsc
 699ec8f00b75b4bb1422cde61ab69e78 123207 admin optional debram_2.0.0.5.tar.gz
 e5feedea1405a45ad2fc001768c6498a 56150 admin optional 
debram-data_2.0.0.5_all.deb
 c3193760c351da97a4e1287936adf340 14266 admin optional debram_2.0.0.5_amd64.deb

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

iQIcBAEBCAAGBQJXfOjpAAoJEHBjJkMthSK8VxkP/j+/3U9FiMiaAQEyrAGY/BiI
U3YbIcV0ocPqhtyKTE9PvXfxkGxX7DuO3dW5Td6tgf75GLlBzr48RhcuSZrop+Bb
D7tFtTkOGi5WB4TcQdVamR7gAn2DWa/a7hofMm55DdYhI5EzK2W9wpOs/4CP6Ta3
AcITOFysYuOrKLhtxMZwSQf7X7G/WRkbeecc3tOtMRzINPU82njXpxkfRBbecXZY
LCAiTv7HjSl47yGS5Lm5z95cs27dLw4GILDN9d+cEop2G2s7tkThuHesvj5SzKei
VLCzw7yBdD4qn17T/v528fMRfS53dclve1qAhMGc/XL9nZcBPlwzw5EYUgWTbkrD
0HNV6I10EJ+xvGilNlPSmuOhTKaeyv68+IPxb2B1m9oOzXCaPmClKsbTDGGWA1GP
7iJRkzUUElcNfQiJLL/5BzNZtoofnUA4Mk5rUtHf1mNcmX+baTnx8xzO65+5q3TQ
ALdNH4yNvsW7mKO1euJ9xUVi8I3OJcAqhSDtZb2cTZhn3fIxBxmVCVdh1JcF5WAa
f1jiNQ4DPHXhjurgvCSjtRdhf3nOexH01JrV26awGzg6oTR02qBTTyimjhyomcnl
5L7LCqNiQx1ITmAF0NXE/oxnzTZwTwF5GsHk4F1RJfYTi/+H31MBNkPE/bfop8p2
Kvi7hQBzgVM4X5hxy+ZG
=dnSM
-----END PGP SIGNATURE-----

--- End Message ---

Reply via email to