[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#687257: marked as done (libutempter0 is not multiarch-aware, embeds executable)

Your message dated Fri, 17 Nov 2017 18:00:25 +0100
with message-id <87zi7k7sd2.fsf@turtle.gmx.de>
and subject line Re: Bug#687257: libutempter0 is not multiarch-aware, embeds executable
has caused the Debian Bug report #687257,
regarding libutempter0 is not multiarch-aware, embeds executable
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)


-- 
687257: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=687257
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Package: libutempter0
Version: 1.1.5-4
Severity: normal

As $Subject says, libutempter0 is not Multi-Arch-able.  I can guess
this is because of /usr/lib/utempter/utempter executable which is
shipped in this package.  Due to this non-multi-arch-awareness,
it isn't possible to install foreign packages depending on it.

One trivial solution (to keep this package single as before) is
to move /usr/lib/utempter/utempter to /usr/lib/$triplet/utempter,
this way it will be co-installable with itself.

Alternative is to split the binary into separate libutempter-bin
package.

I'm not sure which is preferred: while first way is less intrusive
and is very simple, we're getting additional setgid binary for
each arch, while second way minimizes number of setgid binaries
to watch for.

Thanks,

/mjt

--- End Message ---
--- Begin Message --- 
Source: libutempter
Version: 1.1.6-2

On 2012-09-11 12:31 +0400, Michael Tokarev wrote:

> Package: libutempter0
> Version: 1.1.5-4
> Severity: normal
>
> As $Subject says, libutempter0 is not Multi-Arch-able.  I can guess
> this is because of /usr/lib/utempter/utempter executable which is
> shipped in this package.  Due to this non-multi-arch-awareness,
> it isn't possible to install foreign packages depending on it.
>
> One trivial solution (to keep this package single as before) is
> to move /usr/lib/utempter/utempter to /usr/lib/$triplet/utempter,
> this way it will be co-installable with itself.
>
> Alternative is to split the binary into separate libutempter-bin
> package.
>
> I'm not sure which is preferred: while first way is less intrusive
> and is very simple, we're getting additional setgid binary for
> each arch, while second way minimizes number of setgid binaries
> to watch for.

The first of these suggestions (moving the helper to a multiarch
location) has been implemented in version 1.1.6-2, and libutempter0 is
now multiarch-coinstallable.

--- End Message ---
Reply to: