Bug 572261 - gdbm-1.8.3-1.fc14 breaks ABI
Summary: gdbm-1.8.3-1.fc14 breaks ABI
Keywords:
Status: CLOSED RAWHIDE
Alias: None
Product: Fedora
Classification: Fedora
Component: gdbm
Version: rawhide
Hardware: All
OS: Linux
low
medium
Target Milestone: ---
Assignee: Karel Klíč
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On: 572447
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-03-10 16:55 UTC by Rex Dieter
Modified: 2013-03-03 23:00 UTC (History)
3 users (show)

Fixed In Version: gdbm-1.8.3-5.fc14
Clone Of:
Environment:
Last Closed: 2010-03-16 15:10:32 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Rex Dieter 2010-03-10 16:55:04 UTC
This new build that landed today breaks ABI, now provides
libgdbm.so.3 (was .so.2 previously).

And largely breaks the world, due to many high profile packages that now have broken deps, including perl, python.

I've untagged this from dist-f14 until a plan can be formulated to introduce this without the fallout.

Comment 1 Rex Dieter 2010-03-10 16:58:06 UTC
See also related commit I did to gdbm/devel branch,

* Wed Mar 10 2010 Rex Dieter <rdieter> - 1.8.3-2
- %files: track shlib sonames, so abi breaks are less of a surprise

:)


Alternatives off the top of my head on how to introduce this less painfully include:
1.  A new koji tag for rebuilding stuff against the new gdbm
2.  introduce a (temporary?) compat-gdbm package providing the older sonames

Comment 2 Karel Klíč 2010-03-10 17:07:36 UTC
I know about the breakage. I already prepared an announcement for fedora-devel, and obtained a list of all package maintainers affected by this change, so they can be BCC'ed and rebuild their packages.

If you want to protect rawhide from being broken for a day or two, I would go for a new koji tag.

Can you create it, please? (I do not know how to do it)

Comment 3 Rex Dieter 2010-03-10 17:12:36 UTC
Good to know.  Though... the surprise of folks reporting breakage in #fedora-devel would've been less if the announcement had been *before* breaking anything, imo.

Lemme ping other rel-eng folks on which plan they prefer 
1.  1-2 days breakage
2.  create separate koji tag.

Comment 4 Rex Dieter 2010-03-10 17:17:38 UTC
Meh, I consider plan 1 acceptable, retagging  gdbm-1.8.3-1.fc14 

I suppose we can keep this open as a sort of tracker, and close when all relevant rebuilds are done, if that's acceptable to you?

Oh, and please send the -devel announcement asap. :)

Comment 5 Karel Klíč 2010-03-10 17:20:52 UTC
I thought it takes a day for a build to reach the repository. I tried to rebuild (scratch build) ypserv with the new gdbm, but Koji still uses the old one. That is the reason why I did not send the announcement yet.

I am very sorry if I broke someone's system before the announcement.

Comment 6 Karel Klíč 2010-03-10 17:28:25 UTC
Oh, it seems that perl needs to be rebuilt ASAP, it is needed by mock. AFAIK I do not have sufficient rights to do it. Can you do that, please?

Comment 7 Rex Dieter 2010-03-10 17:36:46 UTC
I, spot, Oxf13 are on freenode/#fedora-devel irc discussing now.  We're trying some perl/python scratch builds, if they go ok, good.  Else, we'll likely have to untag this and re-evaluate.

Comment 8 Karel Klíč 2010-03-10 17:43:16 UTC
Ok, thank you.

Comment 9 Rex Dieter 2010-03-10 18:16:08 UTC
looks like we have some bootstapping problems, mostly to do with perl, so this looks like a no go as is, untagging again.

We'll have to come up with something else.  (maybe do the compat-gdbm thing is safest).

Comment 10 Jesse Keating 2010-03-10 18:22:36 UTC
Right, perl is required by rpm-build and thus gets pulled into every single buildroot.  Perl can't install if gdbm is bumped, so a compat-gbdm is required here.

Comment 11 Rex Dieter 2010-03-11 13:29:49 UTC
Here's my first rough try at compat-gdbm:
http://rdieter.fedorapeople.org/rpms/compat-gdbm/

Will post for review shortly.

Comment 12 Karel Klíč 2010-03-16 15:10:32 UTC
gdbm-1.8.3-5.fc14 and compat-gdbm-1.8.0-2.fc14 fix this issue. 

compat-gdbm provides libgdbm.so.2
gdbm provides libgdbm.so.3


Note You need to log in before you can comment on or make changes to this bug.