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

Bug#922484: marked as done (nmu: paw_1:2.14.04.dfsg.2-9.1, mclibs_20061220+dfsg3-3.1, geant321_1:3.21.14.dfsg-11)

Your message dated Sat, 27 Apr 2019 11:14:32 +0100
with message-id <1556360072.2690.35.camel@adam-barratt.org.uk>
and subject line Closing bugs for updates included in 9.9
has caused the Debian Bug report #922484,
regarding nmu: paw_1:2.14.04.dfsg.2-9.1, mclibs_20061220+dfsg3-3.1, geant321_1:3.21.14.dfsg-11
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.)


-- 
922484: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=922484
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Package: release.debian.org
Severity: normal
User: release.debian.org@packages.debian.org
Usertags: binnmu

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

Hi Release team,

Now that #922453 is fixed, paw, mclibs and geant321 have to be rebuilt
against this fixed cernlib release.

nmu paw_1:2.14.04.dfsg.2-9.1 . ANY . unstable . -m "rebuild against fixed cernlib regarding #922453"
nmu mclibs_20061220+dfsg3-3.1 . ANY . unstable . -m "rebuild against fixed cernlib regarding #922453"
nmu geant321_1:3.21.14.dfsg-11 . ANY . unstable . -m "rebuild against fixed cernlib regarding #922453"

Thanks in advance;

_g.

- -- System Information:
Debian Release: buster/sid
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.18.0-2-amd64 (SMP w/4 CPU cores)
Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8), LANGUAGE=fr_FR.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

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

iQEzBAEBCgAdFiEEoJObzArDE05WtIyR7+hsbH/+z4MFAlxoe+wACgkQ7+hsbH/+
z4P8ywf+OdYQS2XYWdGZ9y5bBJoQGT0mQ0zvD+SdFfgAMU9o+91FqhTtxB8jTLd2
QQpkcBgaI+U/PIzKWVea3Tyu2sEzL5sm7J/GWKe5sYOYp3sQSftp+Sz0IRmoXhzA
BHENzlB/L/vs00yJWrMH/h5/t2DH/s99K5dxYfV/V3fA9HbWWuvTmTteQ6ecsOP3
Xr09Vbhh3iuWR1x6yiyTvOETJer9CxyMX+SQSHai6wKYZNP8aKPoVP7QPl4I8goN
B6B7clVuAhTTtDInfTN+0RxHgX2pIuxEoPDJGUxefhY2VJvLnUl/FCaRaneyZx3d
/xsODhYvd5BIO2Hox3GS7jnDa6faeQ==
=ZIna
-----END PGP SIGNATURE-----

--- End Message ---
--- Begin Message --- 
Version: 9.9

Hi,

The update referenced by each of these bugs was included in this
morning's stretch point release.

Regards,

Adam

--- End Message ---
Reply to: