Red Hat Bugzilla – Bug 804698
Wrong packaging of guichan-0.8.2
Last modified: 2012-08-06 16:01:52 EDT
during the development of guichan the name of the libary accidently got named to 0.8.1 (should have been 0.8). When 0.8.2 came out the libary name stayed at 0.8.1.so since it was compatible and only contained some fixes. But in Fedora this libary name got included as/usr/lib/libguichan-0.8.2.so.1 which actually should be 0.8.1.
It looks like it's picking this up from our build flags. There aren't too many packages that require this, so I could coordinate a rebuild easily, though only for rawhide. How do I specify the solib release in your configure or Make?
For existing releases, this shouldn't cause any issues, and all our packages that need this we built to also require the wrong soname.
It should be set by default:
Back when we released 0.8.2, we make sure to keep binary compatibility with 0.8.1, but due to the solib already including "0.8.1", we decided to keep it on that version otherwise the binary compatibility would falter at that point.
See my commit here:
But it seems that a packager either found an issue with this or was not aware of our intention, when this patch was introduced:
As far as I can see, that patch should just be dropped.
Ok, but GUICHAN_MICRO_VERSION is set to 2. When I ./configure ; make a vanilla tarball, it builds 0.8.1. When I build it in the RPMs, I get 0.8.2. Something else is happening.
If I run autoreconf -if prior to config, I get 0.8.1.
I'll get this out to rawhide, and then rebuild the other packages.
Do you forsee a release coming that would re-align versioning and solib name?
(In reply to comment #3)
> Back when we released 0.8.2, we make sure to keep binary compatibility with
> 0.8.1, but due to the solib already including "0.8.1", we decided to keep it on
> that version otherwise the binary compatibility would falter at that point.
> See my commit here:
> But it seems that a packager either found an issue with this or was not aware
> of our intention, when this patch was introduced:
> As far as I can see, that patch should just be dropped.
Oh, I'll try that. See question in #4.
It's been a while, but my memory is that I noticed a mismatch between the microversion used for the package and the library and thought that was a mistake.
I don't believe my change was based on bad interactions with other packages.
Reasonable. I don't expect this to be a major issue.
(In reply to comment #4)
> Do you forsee a release coming that would re-align versioning and solib name?
As you can see in the configure.in, there is a todo about removing the ".1" part for 0.9 (with the idea to keep binary compatibility in patch versions). However, there is currently no active development of Guichan so this release is unlikely to be any time soon.
This message is a notice that Fedora 15 is now at end of life. Fedora
has stopped maintaining and issuing updates for Fedora 15. It is
Fedora's policy to close all bug reports from releases that are no
longer maintained. At this time, all open bugs with a Fedora 'version'
of '15' have been closed as WONTFIX.
(Please note: Our normal process is to give advanced warning of this
occurring, but we forgot to do that. A thousand apologies.)
Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, feel free to reopen
this bug and simply change the 'version' to a later Fedora version.
Bug Reporter: Thank you for reporting this issue and we are sorry that
we were unable to fix it before Fedora 15 reached end of life. If you
would still like to see this bug fixed and are able to reproduce it
against a later version of Fedora, you are encouraged to click on
"Clone This Bug" (top right of this page) and open it against that
version of Fedora.
Although we aim to fix as many bugs as possible during every release's
lifetime, sometimes those efforts are overtaken by events. Often a
more recent Fedora release includes newer upstream software that fixes
bugs or makes them obsolete.
The process we are following is described here: