From: "Eli Schwartz" <eschwartz@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: dev-cpp/pystring/
Date: Tue, 11 Mar 2025 04:30:19 +0000 (UTC) [thread overview]
Message-ID: <1741665276.e7d3bbefc322635eaf6c0dbbc104d24955ba020f.eschwartz@gentoo> (raw)
commit: e7d3bbefc322635eaf6c0dbbc104d24955ba020f
Author: Eli Schwartz <eschwartz <AT> gentoo <DOT> org>
AuthorDate: Tue Mar 11 03:42:04 2025 +0000
Commit: Eli Schwartz <eschwartz <AT> gentoo <DOT> org>
CommitDate: Tue Mar 11 03:54:36 2025 +0000
URL: https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=e7d3bbef
dev-cpp/pystring: force rebuild and bump subslot for broken 1.1.4 release
```
* CMP: =dev-cpp/pystring-1.1.3-r1 with dev-cpp/pystring-1.1.4/image
* FILES:-usr/lib64/libpystring.so.0.0
* FILES:+usr/lib64/libpystring.so (-rwxr-xr-x root:root)
* SONAME:-libpystring.so.0.0(64)
* SONAME:+libpystring.so(64)
```
This breaks binpackage usage. preserved-libs sort of saves you, maybe,
if you built locally. Reverse dependencies are linked to .so.0.0, but
the new package only contains .so -- technically, if the reverse were
true, linked binaries would still work if you squint, but in the current
state this simply does not work at all.
The background here is weird. Upstream has a Makefile, which calls the
system libtool (broken!) and produces a soname of .so.0 in the event
that it succeeds at producing a library. We patched in an unofficial
cmake build (???) that set the soname to .so.0.0 instead, which isn't
very libtool of them but whatever. Upstream didn't actually accept that,
they wrote their own which is "simpler" and set the soname to .so.
Now we have 3 different sonames in use, but one of them was only in use
in *Gentoo* for a couple of days, unstable, back in 2021.
As standard, we solve changing sonames by bumping subslot to force a
rebuild. Straight to stable it goes, with a revbump since people
already have it installed and now have broken binaries.
Bug: https://github.com/gentoo/gentoo/pull/21209
Bug: https://github.com/gentoo/gentoo/pull/39761
Bug: https://github.com/imageworks/pystring/pull/29
Fixes: 91773fd1eb57d4c080c0151f5899f1631ddf2aac
Fixes: 4b6bedcedfc6a2e7b8c59262dea3d3e42f248427
Signed-off-by: Eli Schwartz <eschwartz <AT> gentoo.org>
dev-cpp/pystring/{pystring-1.1.4.ebuild => pystring-1.1.4-r1.ebuild} | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/dev-cpp/pystring/pystring-1.1.4.ebuild b/dev-cpp/pystring/pystring-1.1.4-r1.ebuild
similarity index 97%
rename from dev-cpp/pystring/pystring-1.1.4.ebuild
rename to dev-cpp/pystring/pystring-1.1.4-r1.ebuild
index 0d112703d55a..8fc7d5f0f8e4 100644
--- a/dev-cpp/pystring/pystring-1.1.4.ebuild
+++ b/dev-cpp/pystring/pystring-1.1.4-r1.ebuild
@@ -17,7 +17,7 @@ else
fi
LICENSE="BSD"
-SLOT="0"
+SLOT="0/0.fudge"
PATCHES=(
# This release doesn't install the header file.
next reply other threads:[~2025-03-11 4:30 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-11 4:30 Eli Schwartz [this message]
-- strict thread matches above, loose matches on Subject: below --
2025-03-08 14:59 [gentoo-commits] repo/gentoo:master commit in: dev-cpp/pystring/ Arthur Zamarin
2025-03-08 14:15 Arthur Zamarin
2024-12-22 1:30 Sam James
2023-08-01 15:42 Sam James
2022-02-28 23:58 Sam James
2022-02-28 7:06 Yixun Lan
2021-10-31 5:53 Sam James
2021-09-19 3:30 Sam James
2021-09-19 3:09 Sam James
2021-09-19 3:09 Sam James
2021-09-19 3:09 Sam James
2021-06-10 23:14 Sam James
2021-06-10 0:51 Sam James
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1741665276.e7d3bbefc322635eaf6c0dbbc104d24955ba020f.eschwartz@gentoo \
--to=eschwartz@gentoo.org \
--cc=gentoo-commits@lists.gentoo.org \
--cc=gentoo-dev@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox