Re: xfree86-driver-synaptics blocked by xserver-xfree86 on s390
On Mon, Jun 21, 2004 at 11:51:03AM +0100, Colin Watson wrote:
> On Mon, Jun 21, 2004 at 12:32:05PM +0200, Andreas Metzler wrote:
>> On 2004-06-07 Mattia Dongili <dongili@supereva.it> wrote:
>>> On Tue, May 11, 2004 at 10:03:04AM +0200, Andreas Metzler wrote:
>>>> On 2004-05-11 Mattia Dongili <dongili@supereva.it> wrote:
>>>>> Subject: xfree86-driver-synaptics blocked by xserver-xfree86 on s390
>> [...]
>>>> Personally I'd immediately change the architecture field and change it
>>>> back once there is a xserver for s390. - You'll probably have to
>>>> pester ftp-master to remove the old s390 binary, otherwise
>>>> xfree86-driver-synaptics will be blocked by "out of date on s390".
>>> I finally opted for this solution.
>> [...]
>> May I ask for status update?
>> You have uploaded 0.13.3-1 yesterday with still "Architecture: any"
>> and it has therefore built and been uploaed by s390 *again*.
> It doesn't matter what the source package says anyway. In order to get
> s390 to stop building it, you need to get it added to
> Packages-arch-specific.
That is not completely correct.
Using 'Architecture: [!s390]' accomplishes some things:
* no accidental (manual?) build on s390.
* the autobuilders will not *successfully* build it. (The buildlog
will say something like 's390 not in list of supported archs')
* it serves for documentation.
An (additional) entry in Packages-Arch-Specific is just cleaner and
nicer, because the buildd will not even /try/ to build the package.
And all this is orthogonal to the requirement that the existing s390
binaries in archive need to *also* be removed, using a bug-report
against ftp.debian.org.
cu andreas
Reply to: