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

Bug#847096: marked as done (elfutils: Does not build when using eatmydata)



Your message dated Wed, 18 Oct 2023 00:13:13 +0200
with message-id <[🔎] 2067c8ce-d0f6-481b-86b2-f5f325ea88e8@debian.org>
and subject line Re: elfutils: Does not build when using eatmydata
has caused the Debian Bug report #847096,
regarding elfutils: Does not build when using eatmydata
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.)


-- 
847096: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=847096
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message ---
Package: elfutils
Version: 0.166-2.2
Severity: wishlist

Dear maintainer:

I can't build this package from source when using eatmydata.

To reproduce, please use sbuild and a file
/etc/schroot/chroot.d/stretch-eatmydata like this:

[stretch-eatmydata]
type=directory
description=Debian stretch
directory=/chroot/stretch
groups=sbuild
root-groups=sbuild
preserve-environment=true
union-type=overlay
command-prefix=eatmydata

I attach two different build logs, one with eatmydata and another one
without it, on similarly configured machines.

Of course, it is not policy that packages should build with eatmydata
(which is why I'm filing this as wishlist), but this is something
that really helps to go a lot faster when doing archive rebuilds.

Thanks.

Attachment: elfutils_0.166-2.2_amd64-20161205T150303Z.gz
Description: application/gzip

Attachment: elfutils_0.166-2.2_amd64-20161205T150306Z.gz
Description: application/gzip


--- End Message ---
--- Begin Message ---
Version: 0.183-1

Hello. According to my build logs, this is fixed at least in bullseye,
so I'm closing with this message.

Thanks.

--- End Message ---

Reply to: