[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#1077132: marked as done (yatex: needs rebuild against dh-elpa >=2.1.5)

Your message dated Fri, 02 Aug 2024 19:21:42 +0000
with message-id <E1sZxqQ-005HUx-LN@fasolo.debian.org>
and subject line Bug#1077132: fixed in yatex 1.82-3
has caused the Debian Bug report #1077132,
regarding yatex: needs rebuild against dh-elpa >=2.1.5
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 owner@bugs.debian.org
immediately.)


-- 
1077132: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1077132
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Source: yatex
Severity: serious
Tags: patch
User: debian-emacsen@lists.debian.org
Usertags: dh-elpa-2.1.5-rebuilds

Dear maintainer,

This package needs a no-change upload to rebuild it against dh-elpa
>=2.1.5.  This is because binNMUs cannot be used to rebuild arch:all
packages.

The update is needed to resolve a problem for users upgrading between
stable releases.  In some circumstances, old .elc files can be left
behind, and Emacs will try to load them.  In the best case there will
be warnings that the .el file cannot be found, so the .eln file cannot
be produced.  In the worst case the package could break.

This is an RC bug because it's a Policy violation to leave the files
behind upon removal of the old version.

Please do something like this:

      % dch Rebuild against newer dh-elpa.
      % dch -r
      % git commit debian/changelog -mchangelog

and upload.

Thanks.
-- 
Sean Whitton

--- End Message ---
--- Begin Message --- 
Source: yatex
Source-Version: 1.82-3
Done: Marcos Talau <talau@debian.org>

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

Debian distribution maintenance software
pp.
Marcos Talau <talau@debian.org> (supplier of updated yatex 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 ftpmaster@ftp-master.debian.org)


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

Format: 1.8
Date: Fri, 02 Aug 2024 15:56:49 -0300
Source: yatex
Architecture: source
Version: 1.82-3
Distribution: unstable
Urgency: medium
Maintainer: Debian QA Group <packages@qa.debian.org>
Changed-By: Marcos Talau <talau@debian.org>
Closes: 1077132
Changes:
 yatex (1.82-3) unstable; urgency=medium
 .
   * Rebuild against newer dh-elpa (Closes: #1077132).
Checksums-Sha1:
 1465188e5e3e218df12d6460fd33e8d07ddd8c51 1840 yatex_1.82-3.dsc
 2ea980e5979e100d895bdfd98e66c764393253c5 23720 yatex_1.82-3.debian.tar.xz
 b7309de6bd537ac1cc448c7a6d0e5ec85dc96362 9404 yatex_1.82-3_source.buildinfo
Checksums-Sha256:
 1469f63b487dfbdadfb30d3e2a0d8bb675866665c26db6c47c5655585f4745fd 1840 yatex_1.82-3.dsc
 f435c32fda25c8a0eee725089bbef460ba8da72c838ad6271520b22cf27636ac 23720 yatex_1.82-3.debian.tar.xz
 306f1ccde391838d3af22c45b064bbfab86b1bd0bb3056dd93e5f5c192bed3b6 9404 yatex_1.82-3_source.buildinfo
Files:
 0b964ce9c04b6e530d232ab31a5b990a 1840 tex optional yatex_1.82-3.dsc
 ac691cfbde910a74a6915734b79e7bad 23720 tex optional yatex_1.82-3.debian.tar.xz
 e72ee4586613f97ac0c3b82f0d110df6 9404 tex optional yatex_1.82-3_source.buildinfo

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

iQIzBAEBCgAdFiEEtSLzkVnaB9053AsR9LqqgNsoukwFAmatLaEACgkQ9LqqgNso
ukwPKw/+NrFQm5iwQ8vefShL7ArNlOrlero5l4+v9OtUCw3qhXi6+I1XbSZ06a2P
3sgnv90KeXX1U1h4XqLHEYBoAjDpx77Kd8sb6UPQSHWIFzygroXvrWH2NxsyOwz1
2qAoGn8z4Y6wL/oLkriiJ86L3HLx3lu2nq4VsW7/4bKJSMUkO0v01gkjdoOaoYp2
vP/arcEYyvUFyfksjTygnYtY215eOOYDSW5Xeh5oVbfT3f+xtZ+qhcewuOXZ3fNh
a+bz1n79W96VA0iiaG/ewyraDH80HoZnF9BeQ5r31rNMYs4BHweOOuSwFTQi+npA
iRtleM9r+MsC0rs/kcEi1aSeHQeOZJAwL8Ur3eYenlJKUs22v/XDKgPEpoNNHXxZ
RtvXk3PCpNQh9O0KmLosUhLxIRQeLmfb32jKxIsrgcudfSBjqEeLQrfOAkbARkV+
QX4+gC94NtuL8i3oxA0bR7a8YWi49MU0hIfbgCr9E0MGYlQ7JSI3VaYPNlSzh43J
WzvcmC83d2wJ8wPMXmFpSELJzDMcPKT6aGkqQ/76iX59Ynz47XAWOiJh7Z6qobtt
efCOJK0xe6kP6PwmPQO+4ja0Hzoq76Gggw+6aGsi2D4REavkRdewVFkW2CyfY5fj
XhkDG6oSsGREPbfQUhXe+fOJLQyrBJJyJZAZLDA5W1M+XEdUPPI=
=fYvb
-----END PGP SIGNATURE-----

Attachment: pgpFqmIi8z2ep.pgp
Description: PGP signature


--- End Message ---
Reply to: