On Feb 28 2017, Nikolaus Rath <[email protected]> wrote:
> On Feb 28 2017, Santiago Vila <[email protected]> wrote:
>> On Tue, Feb 28, 2017 at 11:15:26AM -0800, Nikolaus Rath wrote:
>>
>>> It does build with libeatmydata - you just have to allow use of
>>> libeatmydata for setuid binaries by making
>>> /usr/lib/[triplet]/libeatmydata*so setuid (but not executable) itself.
>>
>> Hmm, but when I say "does not build with libeatmydata" I mean
>> "libeatmydata as installed by default".
>>
>> My goal was to avoid having to do special things (for example,
>> building without eatmydata). What you propose is to do another special
>> thing instead of not using eatmydata, so in the end, I still have to
>> do special things.
>
> You could run the testcases as root instead, or attempt to convince the
> libeatmydata maintainer to ship with setuid (I think I already tried that and
> failed though).
Or, in other words, in my opinion having libeatmydata installed setuid
root is a sane choice for any build chroot that can be used for any
package build. In that case it's no longer something special that you
have to do for this package.
Best,
-Nikolaus
--
GPG encrypted emails preferred. Key id: 0xD113FCAC3C4E599F
Fingerprint: ED31 791B 2C5C 1613 AF38 8B8A D113 FCAC 3C4E 599F
»Time flies like an arrow, fruit flies like a Banana.«
