Your message dated Tue, 14 May 2024 15:39:16 +0000
with message-id <e1s6ufi-00a6fb...@fasolo.debian.org>
and subject line Bug#1071063: fixed in screenkey 1:1.5-5
has caused the Debian Bug report #1071063,
regarding screenkey: malformed 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.)


-- 
1071063: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1071063
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: screenkey
Version: 1:1.5-4
Severity: serious
User: reproducible-bui...@lists.alioth.debian.org
Usertags: timestamps
X-Debbugs-Cc: reproducible-b...@lists.alioth.debian.org


Hi,

This might not *strictly* be an RC bug, but the latest upload of
screenkey has the following entry in debian/changelog:

<<<
    screenkey (1:1.5-4) unstable; urgency=medium

      * fixed d/watch
      * bumped Standards-Version: 4.7.0
      * removed the stance X-Python-Version

     --
>>>

Note in particular the missing date. This doesn't break dak, otherwise
it would not have been accepted by the archive, but it breaks many
other tools (eg. gbp-buildpackage, etc.) as well as other things. For
example, the package is not reproducible because SOURCE_DATE_EPOCH
cannot be extracted from the debian/changelog.

When building the package you should have seen warnings by, for
instance, dh_installchangelogs, dpkg-gencontrol, dpkg-genchanges,
etc. :)

Regards,

-- 
      ,''`.
     : :'  :     Chris Lamb
     `. `'`      la...@debian.org / chris-lamb.co.uk
       `-

--- End Message ---
--- Begin Message ---
Source: screenkey
Source-Version: 1:1.5-5
Done: Georges Khaznadar <georg...@debian.org>

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

Debian distribution maintenance software
pp.
Georges Khaznadar <georg...@debian.org> (supplier of updated screenkey 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: Tue, 14 May 2024 17:10:30 +0200
Source: screenkey
Architecture: source
Version: 1:1.5-5
Distribution: unstable
Urgency: medium
Maintainer: Georges Khaznadar <georg...@debian.org>
Changed-By: Georges Khaznadar <georg...@debian.org>
Closes: 1071063
Changes:
 screenkey (1:1.5-5) unstable; urgency=medium
 .
   * fixed the missing date, and made a source upload again.
     Closes: #1071063 (thanks, lamby)
Checksums-Sha1:
 22e38f88f3eafdf9366367b7fb9d82412b91152f 1957 screenkey_1.5-5.dsc
 24c3733dd898b4f0738e2009af5502597add9649 10944 screenkey_1.5-5.debian.tar.xz
 e4591c2c6d7735ca2708a5c464ed26ab241042b6 6489 screenkey_1.5-5_source.buildinfo
Checksums-Sha256:
 1b0ae824d6f5b27fb3032f76e392d244e73c471919c9e92a502ab01fe435eae4 1957 
screenkey_1.5-5.dsc
 10548bdc33c19094e5148c76884ea41bc16b0de273040b926165700797cbd9ba 10944 
screenkey_1.5-5.debian.tar.xz
 4de951b582730d394021c74e24fb05ca0c5a8874498b7b60c78ab34233a0c086 6489 
screenkey_1.5-5_source.buildinfo
Files:
 9b2fafabe95343f8c095041aba06a913 1957 python optional screenkey_1.5-5.dsc
 fc80aaa891ef3d5f5ca6143c84180b88 10944 python optional 
screenkey_1.5-5.debian.tar.xz
 c91b3aed7d7b2c449ec080dcc6e24966 6489 python optional 
screenkey_1.5-5_source.buildinfo

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

iQJIBAEBCAAyFiEEM0CzZP9nFT+3zK6FHCgWkHE2rjkFAmZDfy4UHGdlb3JnZXNr
QGRlYmlhbi5vcmcACgkQHCgWkHE2rjkjdg/+PGUMWzWSFicUi1TpvzhVD7vbq0Ya
Uxn3CgLDvAvz5zDU35p1feFiUpvlwY845tDNEIw0IiS6uCp2M46C2M+LH28XMABx
kpzBMeY82g3I66XDIurY8rZzNHQ/GNlzf+1u6z8Yjjp+9aCGkZL5lYwDTd5rJAxH
9bJgbiWyl+SLUdCs1UMbbWXQ0RbVWls15rBH9iWnTdhiqTu7lz4O6NM3KjLh86IQ
jS+nMZ1Ro+m0yePh+CnBlrK9PmzhRxP7002AJOq/zNxMS1mwmoBi+8pvdHwLqDW4
OaBHqy9sMPy+VWkMLaL2MwC9ZXfcxx8Bkb4KASajJDmTgI/0PaCa78SC4vZpG1ys
lQPCKQBO92vXtbFP3MUkva4cfmCyPWOZcnzIJ/eripGupusnqAJkBw5tYrVYYs2w
WKls4S9q8X211BChF0qxY7uogYHvzV5NDD+6KYvjFwO+Ig7BUATwYd641G3hutZm
+ZGdlr6SKu3N7mpuwlK2NyO/1WrKH+c//pixS/HDODFhD0I3Ey6iuqK085N6tmi0
Y8lmHBdtUfpyxcCBNPxMp1GYGu3BBG3GItO+HFMnfgnq3BzNwUY4cSPumCf8eXHy
OZ7Uja2080StisFMisY5CqG+j2dNujB1iVyufl5rqu+d0ABwDmTM85UpnRhgk3Le
7GYEkQ5r35COGPM=
=hLr1
-----END PGP SIGNATURE-----

Attachment: pgpzhvb0iRXic.pgp
Description: PGP signature


--- End Message ---

Reply via email to