glom versioned dependency on libglom
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
glom (Ubuntu) |
Fix Released
|
Medium
|
Unassigned |
Bug Description
doesn't glom need a versioned dependency on libglom?
$ dpkg -l | grep glom
ii glom 1.0.5-0ubuntu1 database designer and user interface
ii libglom0 1.0.4-0ubuntu1 Glom library (a database designer and user interface) - library
$ glom
glom: symbol lookup error: glom: undefined symbol: _ZN4Glom14Conne
now, granted, i'm running debian testing, rebuilding ubuntu's glom source package (1.0.4-0ubuntu1 and 1.0.5-0ubuntu1) for it, but the problem should (at least theoretically) exist in ubuntu.
and yeah, assuming both glom and libglom enter the repository at the same time (and they should), then an "apt-get upgrade" should upgrade both packages at the same time. but if a user executes "apt-get install glom" (because they shouldn't also have to list every dependency of glom) with libglom already installed, then the new glom will fail (as demonstrated above).
i believe the problem was caused in 1.0.5 by the addition of the Glom namespace within glom/libglom/
thank you for your packaging of glom!
Related branches
Changed in glom: | |
assignee: | dholbach → nobody |
Changed in glom: | |
assignee: | nobody → protonchris |
status: | New → In Progress |
Could you use the mailing list, please?
> Public bug reported: ctionPool12get_ instanceEv connectionpool. h, changing the name- /launchpad. net/bugs/ 60969
>
> doesn't glom need a versioned dependency on libglom?
>
> $ dpkg -l | grep glom
> ii glom 1.0.5-0ubuntu1
> database designer and user interface
> ii libglom0 1.0.4-0ubuntu1
> Glom library (a database designer and user interface) - library
>
> $ glom
> glom: symbol lookup error: glom: undefined symbol:
> _ZN4Glom14Conne
>
> now, granted, i'm running debian testing, rebuilding ubuntu's glom
> source package (1.0.4-0ubuntu1 and 1.0.5-0ubuntu1) for it, but the
> problem should (at least theoretically) exist in ubuntu.
>
> and yeah, assuming both glom and libglom enter the repository at the
> same time (and they should), then an "apt-get upgrade" should upgrade
> both packages at the same time. but if a user executes "apt-get install
> glom" (because they shouldn't also have to list every dependency of
> glom) with libglom already installed, then the new glom will fail (as
> demonstrated above).
>
> i believe the problem was caused in 1.0.5 by the addition of the Glom
> namespace within glom/libglom/
> mangling from 1.0.4. shouldn't such a change in the API cause a change
> in the soname? (though not strictly necessary as glom is the only
> application dependent on libglom, but a good policy should the library
> be used by others in the future.) but more importantly (pragmatically)
> imho is for glom to have a versioned dependency on libglom.
>
> thank you for your packaging of glom!
>
> ** Affects: glom (Ubuntu)
> Importance: Untriaged
> Status: Unconfirmed
>
> --
> glom versioned dependency on libglom
> https:/
>
Murray Cumming
<email address hidden>
www.murrayc.com
www.openismus.com