--- Begin Message ---
- To: Debian Bug Tracking System <submit@bugs.debian.org>
- Subject: libfabric1: improperly packaged library support files
- From: Helmut Grohne <helmut@subdivi.de>
- Date: Sun, 25 Feb 2018 08:25:34 +0100
- Message-id: <20180225072534.GA22370@alf.mars>
Package: libfabric1
Version: 1.5.3-1
Severity: serious
Justification: policy 8.2
libfabric1 ships /usr/bin/fi_{info,pingpong,strerror}. These files are
independent of the soname of the library. Debian policy section 8.2
prohibits such files from being shipped in the shared library package.
The typical solution is to split them out into a package named e.g.
libfabric-bin. Thus when libfabric bumps its soname, libfabric-bin would
get taken over by the newer package while libfabric1 and e.g. libfabric2
would remain coinstallable.
Helmut
--- End Message ---
--- Begin Message ---
- To: rf@q-leap.de, 891395-done@bugs.debian.org
- Subject: Re: Bug#891395: marked as done (libfabric1: improperly packaged library support files)
- From: Mehdi Dogguy <mehdi@dogguy.org>
- Date: Mon, 03 Sep 2018 22:31:44 +0200
- Message-id: <7ad783c5d26395747dfb8b9e53712664@dogguy.org>
- In-reply-to: <23336.54216.517002.421088@gargle.gargle.HOWL>
- References: <E1fVCKf-0002lK-Jn@fasolo.debian.org> <20180225072534.GA22370@alf.mars> <handler.891395.D891395.15293981894529.ackdone@bugs.debian.org> <1fb905509974196b90bf65031b2891bf@dogguy.org> <20180225072534.GA22370@alf.mars> <23336.54216.517002.421088@gargle.gargle.HOWL>
Version: 1.6.1-5
On 2018-06-19 11:58, Roland Fehrenbacher wrote:
"M" == Mehdi Dogguy <mehdi@dogguy.org> writes:
Hi Mehdi,
M> Control: reopen -1 Hi Roland,
M> If I am not mistaken, your last upload moves files across binary
M> packages but doesn't add necessary Breaks/Replaces. In the
M> current state, upgrades are broken because older libfabric1 and
M> newer libfabric-dev are not co-installable.
fixed, thanks for noticing quickly.
Then marking this bug as such...
Something else: Could you please
delete the patch-queue/debian/master branch of the salsa libfabric
repo. It's totally out of sync and not easily fixable. Then I can add
your latest patch to it too.
Anyone in the team should be able to do that. As for patch-queue/*
branches,
I'd vote for not publishing them. They are useful locally. It takes only
a
few seconds to rebuild them. What's the point of publishing them?
(especially
when you know that they should be rebased/rebuilt often).
Thanks,
Roland
--
Mehdi
--- End Message ---