On Mon, May 14, 2007 at 02:20:53AM -0700, Steve Langasek wrote:
Package: ddccontrol
Version: 0.4.2-2
Severity: serious
Justification: packages must be supported on all architectures where it is
reasonable
Hi Roberto,
According to the changelog for ddccontrol, the package's architecture list
is currently restricted to i386 and amd64 in response to bug #385812. But
this is not a proper fix for that bug, because the package previously built
successfully on ia64, alpha, and arm, and only now fails to build there
because of your change.
In the log of #385812, upstream claims:
ddcpci (the part that causes some problems to build on some archs) use at
least one x86-specific function (ioperm), so I don't think this part of
the code will work on alpha and ia64.
This is false, ioperm is *not* x86-specific. If it were x86-specific, the
package would not have built on these other architectures in the first
place!
OK. That step was based on discussions with upstream. When the package
first FTBFS on s390 that lead me to ask upstream on which architectures
it was reasonable for the package to be built. According to Nicolas
(the lead upstream author), the only platforms on which he considered it
reasonable to want to run this were i386 and amd64.
I can't check that ddcpci works on my alpha, because it only works on cards
from a limited number of vendors (my alpha's card is a Matrox Millennium II,
which is not supported), but I don't see any code in here that's
x86-specific. Please re-enable building ddccontrol on ia64, alpha, and arm,
or at least check with the porter lists for confirmation that the package
doesn't work there.
I will investigate.
Regards,
-Roberto
--
Roberto C. Sánchez
http://people.connexer.com/~roberto
http://www.connexer.com
signature.asc
Description: Digital signature
