Your message dated Sat, 6 Feb 2021 17:21:40 +0200
with message-id <20210206152140.GA14257@localhost>
and subject line Re: Bug#980081: RM: ddccontrol [armel armhf] -- RoQA; glibc 
change broke build on ARM
has caused the Debian Bug report #980081,
regarding RM: ddccontrol [armel armhf] -- RoQA; glibc change broke build on ARM
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 [email protected]
immediately.)


-- 
980081: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=980081
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: ftp.debian.org
Severity: normal

The build of ddccontrol got broken on armel/armhf by a glibc update
removing the <sys/io.h> header (#979283). It is unlikely this will be
fixed before the bullseye freeze, so I suggest removing the ddccontrol
binaries on armel/armhf so that the package does not get removed from
bullseye for the other arches that are not affected.

-- 
bye,
pabs

https://wiki.debian.org/PaulWise

Attachment: signature.asc
Description: This is a digitally signed message part


--- End Message ---
--- Begin Message ---
On Thu, Jan 14, 2021 at 03:57:23PM +0800, Paul Wise wrote:
> Package: ftp.debian.org
> Severity: normal
> 
> The build of ddccontrol got broken on armel/armhf by a glibc update
> removing the <sys/io.h> header (#979283). It is unlikely this will be
> fixed before the bullseye freeze, so I suggest removing the ddccontrol
> binaries on armel/armhf so that the package does not get removed from
> bullseye for the other arches that are not affected.

This is now fixed in unstable:
https://buildd.debian.org/status/package.php?p=ddccontrol

> bye,
> pabs

cu
Adrian

--- End Message ---

Reply via email to