Your message dated Mon, 08 Apr 2024 06:23:28 +0000
with message-id <e1rtipg-00b99p...@fasolo.debian.org>
and subject line Bug#1068599: fixed in xapian-bindings 1.4.22-2
has caused the Debian Bug report #1068599,
regarding ruby-xapian - still depends on old libruby3.1 after binnmu
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.)
--
1068599: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1068599
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: ruby-xapian
Version: 1.4.22-1
Severity: grave
Tags: trixie, sid
User: debian-...@lists.debian.org
Usertag: time-t
After being rebuilt for the time64 transition, ruby-xapian
still depends on libruby3.1 rather than libruby3.1t64.
As a result it is uninstallable on architectures that are
undergoing the time64 transition
(armel, armhf and some debian-ports architectures).
The following lines in the build log look like a likely culprit.
# The module(s) are linked against libruby2.x but use none of its
# symbols, so there's no dependency generated. That's unhelpful for
# users and for transitions (https://bugs.debian.org/816775) so
# generate a suitable dependency.
#
# If RUBY_VERSIONS is 2.1 2.2 2.3, Depends: libruby2.3|libruby2.1 |libruby2.2
echo "ruby:Depends=libruby3.1" \
>> debian/ruby-xapian.substvars
--- End Message ---
--- Begin Message ---
Source: xapian-bindings
Source-Version: 1.4.22-2
Done: Olly Betts <o...@survex.com>
We believe that the bug you reported is fixed in the latest version of
xapian-bindings, 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 1068...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Olly Betts <o...@survex.com> (supplier of updated xapian-bindings 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: SHA512
Format: 1.8
Date: Mon, 08 Apr 2024 17:05:15 +1200
Source: xapian-bindings
Architecture: source
Version: 1.4.22-2
Distribution: unstable
Urgency: medium
Maintainer: Olly Betts <o...@survex.com>
Changed-By: Olly Betts <o...@survex.com>
Closes: 1068599
Changes:
xapian-bindings (1.4.22-2) unstable; urgency=medium
.
* debian/control.in: Mark conformance with policy 4.7.0.
* debian/rules: Adjust ruby-xapian generated "Depends" to pick up t64
suffix. (Closes: #1068599)
Checksums-Sha1:
13aa079443ecab4ecdc42ae6a27dc9289f35a87a 2713 xapian-bindings_1.4.22-2.dsc
4017636c87491dd44af4f55db8cc0bf4e271eb9b 22920
xapian-bindings_1.4.22-2.debian.tar.xz
1c2a1d4032090d6f61c195f58c42133b2c7877b6 17486
xapian-bindings_1.4.22-2_amd64.buildinfo
Checksums-Sha256:
24b9013a0eb2301dff7f8eb7202c90487388cba9e875e372c058f43ea6f7c282 2713
xapian-bindings_1.4.22-2.dsc
ffd554a16a7efc87eaa027f1e974de56b5243d4dfb7bce47b7e9b1e15e68ac22 22920
xapian-bindings_1.4.22-2.debian.tar.xz
f763a6e5a5c70ef037110307a2767901668e32c7da3172cf76724008f7269ad8 17486
xapian-bindings_1.4.22-2_amd64.buildinfo
Files:
641b52714306cf9319fd5e0c157ef2ef 2713 libs optional
xapian-bindings_1.4.22-2.dsc
833bfa09102166862dad0b5b0f3821d8 22920 libs optional
xapian-bindings_1.4.22-2.debian.tar.xz
8ec802d8bfd5a78f0ddb735f7ed017fe 17486 libs optional
xapian-bindings_1.4.22-2_amd64.buildinfo
-----BEGIN PGP SIGNATURE-----
iQIzBAEBCgAdFiEECOJAD/f+j+3jrLUoGBR7BzutKwcFAmYThvsACgkQGBR7Bzut
KwfJSA/+LcH/ZBa8nhMb9S9qxuKOkbLidJXdbCcpoO5vDulcyp00nmUXkK3Pvagb
/Jqpz0AFY1QyMwRefrbSp30ATxwP39+nDrcjaBmZXEnkAYEgCXIZpH0xz53BKbfp
f3J1FmaM76kGP7J6b7pNDiXRdkof/msvWWLM5I0GhPwWj8vmD3j2cJEBQe3WcfI2
ued0I11EHvr1uNG9tWOwoXay8fYJBysn48z0Szp/oA98U9/SPBtlOUCJG3hEZ+E6
8e1TgaFL4IUnzrJItZwQt3+8wfFAJAbCdsCKBlb1sCk+h5ASQCtg755DMHKzErVa
Xjj/xzQLZCQo7YcQTC44lKaXIZjySWDBc0s895gJMYcMxkH60vfOLgy27+wQRKH9
SJkmgWnK8vJIiBDN52xpDHaeLiMbMg+PegqV1QAVvA/kMR74WtsvuUFPiEdOipZ2
eJ/D59gpO+ywK6KhATAbzlwNRZ7a65U5ylQVOdUdc4bMiSNJmkFUoLTD4em8Ak2Y
A9z4WxAT4gxqcC2MEYamlPI1T9TXjb/6Vzt2GVX+zuEOm4VKNeqSKJw7Ln0sVNCd
ytAmv3SYSBDh6lTOn6f5l9RhprEu5hzur2V45qzovfHfycg/RBzlyPp5Svd4Acsl
YGh/Cd3joV3HcO028fu1U3+qmnIMmh3kdx29A6WWEzzY8ni6hqI=
=NjOB
-----END PGP SIGNATURE-----
pgp8U0NfkThCz.pgp
Description: PGP signature
--- End Message ---
