Your message dated Sun, 17 Mar 2024 15:23:18 +0000
with message-id <e1rlsm2-00aobd...@fasolo.debian.org>
and subject line Bug#1067043: fixed in ruby-defaults 1:3.1+nmu1
has caused the Debian Bug report #1067043,
regarding libruby: needs updating for libruby3.1t64
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.)


-- 
1067043: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1067043
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libruby
Version: 1:3.1
Severity: serious
Justification: blocker for 64-bit time_t transition
X-Debbugs-Cc: z...@debian.org, debian-...@lists.debian.org
Control: affects -1 + src:graphviz src:vala

Now that libruby3.1t64 has reached unstable, libruby is uninstallable on
the architectures affected by the 64-bit time_t transition, blocking the
rebuild of packages such as graphviz and vala via this dependency chain:

... -> vala -> graphviz -> ruby -> libruby -> libruby3.1

The impact of this is visible in for example
<https://buildd.debian.org/status/package.php?p=graphviz>.

I suspect the only change needed here is to update the libruby metapackage
so that it depends on libruby3.1t64 instead of libruby3.1. Please could
someone who knows Ruby check this?

Thanks,
    smcv

--- End Message ---
--- Begin Message ---
Source: ruby-defaults
Source-Version: 1:3.1+nmu1
Done: Chris Hofstaedtler <z...@debian.org>

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

Debian distribution maintenance software
pp.
Chris Hofstaedtler <z...@debian.org> (supplier of updated ruby-defaults 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: Sun, 17 Mar 2024 16:08:39 +0100
Source: ruby-defaults
Architecture: source
Version: 1:3.1+nmu1
Distribution: unstable
Urgency: medium
Maintainer: Debian Ruby Team 
<pkg-ruby-extras-maintain...@lists.alioth.debian.org>
Changed-By: Chris Hofstaedtler <z...@debian.org>
Closes: 1067043
Changes:
 ruby-defaults (1:3.1+nmu1) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * libruby: follow libruby3.1 -> libruby3.1t64 rename (Closes: #1067043)
Checksums-Sha1:
 ed25b34408bc84222ecc1e03946e93b99a82f409 2004 ruby-defaults_3.1+nmu1.dsc
 6fc6a81c4dad1562f405e6d8d02e74137bd25336 13280 ruby-defaults_3.1+nmu1.tar.xz
 ef31c9044d8499620c3289d64274e4e1e9140a24 7311 
ruby-defaults_3.1+nmu1_arm64.buildinfo
Checksums-Sha256:
 ec07c7fdd15b00cdbff7710f350eddc8b9fa3e21c470201214588307362f0a16 2004 
ruby-defaults_3.1+nmu1.dsc
 516dce3f6a360ca2db28fa587f90dacd1f4c53a7b8594c2fc90c971b8aa0494e 13280 
ruby-defaults_3.1+nmu1.tar.xz
 1814adaf836600f1364eb7dd92a5ee0cb4cefd3a931dcb6c4dd2edf947f89925 7311 
ruby-defaults_3.1+nmu1_arm64.buildinfo
Files:
 01e7a2d026a9b6fd70554a1a102f5002 2004 ruby optional ruby-defaults_3.1+nmu1.dsc
 4b041b3f8271c88f8912a4acab39bb1c 13280 ruby optional 
ruby-defaults_3.1+nmu1.tar.xz
 8936beed1003caf9df143cd9e5bf8de2 7311 ruby optional 
ruby-defaults_3.1+nmu1_arm64.buildinfo

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

iQIzBAEBCAAdFiEEfRrP+tnggGycTNOSXBPW25MFLgMFAmX3CD8ACgkQXBPW25MF
LgPJKQ//VDcTYahkjVw0ym1M6iiVwfg6mJtGhMtSld6erYVESB4X+/7Y5p6DQfiX
hmGEE1WeouWLtyrwF8ve1kSKyIct+QE4BI3MJOeCIhdkQptoBmr0ETjAmH1nbIF6
zTVcwbhGFx3mNODfxXNHtbXnxAIuPh7Xejk55qKeP38nSl7RBDoRFfBRh6G5HPCy
kqBDbBGfcNrGShCeQf1nxiCB1g1PIEJ63nZHSD2wrEwytUxZzBg9cOZAtZKKDRXv
fAowpwJillcCDzDQ51ng6qZmanSyiSQ1MLIr/Ir1ey5OmYgYmeKBGJ+PUS0lGv/9
GfcJBaVI2RWBhUJoDRirUkmZdSni0BNGBWk464kdX5iOpygpIZQSICwgKBFhIl+5
3CfJ2xb1ZD2hF6mphnTrShLXqGjH0ebN69vh4yRQhqmAIv8GyHFAkCphZJ/JeU2/
IHXM8C7I1p8nyTQ9RC6hzsCK+eH5ZvE9n9LtJZ9O9u7y3pmtwLk82r+LRoM+mOQd
tvmGoWwUkcZE4M9c9rmzeMEPX0W64/bvzUjOaSRz0jo1JeVwN/rOGtoVT6NF/Umx
2s2BP9RRVBXf28ujHYtB1jZljXnpikoQNTNLpM7EBs5GlAG+hvTNgZeozsdv8cF7
7w1neN9Qcny9vTnYrrqU3IU8Gr91lmPU/ehAVpS/qFjEHqpUODc=
=grLy
-----END PGP SIGNATURE-----

Attachment: pgpMBjulguW1u.pgp
Description: PGP signature


--- End Message ---

Reply via email to