Re: Bug#397917: gsynaptics - lists s390 as supported
Hi,
On Fri, Nov 10, 2006 at 03:04:54PM -0800, Steve Langasek wrote:
> On Fri, Nov 10, 2006 at 11:17:57PM +0900, Osamu Aoki wrote:
> > On Fri, Nov 10, 2006 at 02:00:32PM +0100, Bastian Blank wrote:
> > > Package: gsynaptics
> > > Version: 0.9.7-1
> > > Severity: serious
>
> > > gsynaptics lists s390 as supported (Architecture: any) but
> > > xserver-xorg-input-synaptics is not available. This leads to
> > > uninstallable binary packages.
>
> > I see. But xserver-xorg-input-synaptics has
>
> > Architecture: alpha amd64 arm hppa i386 ia64 m68k mips mipsel powerpc sparc
>
> > This looks agry. Because I need to track new architectures.
>
> > Can I do
>
> > Architecture: !s390
>
> No, this syntax is not supported.
OK.
> > Anyone have suggestion?
>
> One possibility is to list the package as Architecture: any, but construct
> your debian/rules file such that the package fails to build if the
> architecture is s390.
That may be a good solution if I did not have package in testing
including s390. But it is there.
It will waste of autobuilder time and current package stays in testing
and unstable for s390.
Since my packages for all arches are already in testing, the newly
build packages will stay in unstable and old packages stay in testing
due to version difference. So no real gain just doing this.
As I see now, I have few options. What is right?
Option 1)
* Change BTS "#397917: gsynaptics - lists s390 as supported" to "normal"
* Reassign #397917 to xserver-xorg-input-synaptics
* Ask xserver-xorg-input-synaptics to be rebuild as Architecture: any .
I know it is unlikely to hook synaptics device to s390 but then who
will ever bother to set up xserver to start with. I understand that it
is likely to have s390 run X client softwares on it and some X server
to be connected to it for display. I see X server on s390 so I see no
reason not to build xserver-xorg-input-synaptics.
There is also "Hercules" emulator. It may support funny hardware
extension in future too.
Option 2)
* Change BTS "#397917: gsynaptics - lists s390 as supported" to "normal"
* Lazily sit tight.
This removes RC bug but really leaves my package uninstallable in s390.
xserver-xorg-input-synaptics can do what ever he wants.
Option 3)
* Set "Architecture: alpha amd64 arm hppa i386 ia64 m68k mips mipsel powerpc sparc"
* Ask ftp-master for removal of package for s390
* Make entry in quinn-diff not to build on s390
This is a lot of CPU time and work for no real gain other than closing
bug.
Option 4)
* Set "Architecture: any"
* Have fancy script to fail in s390.
* Ask ftp-master for removal of package for s390
* Make entry in quinn-diff not to build on s390
This is a lot of CPU time and work for no real gain other than closing
bug.
Osamu
PS: Many device support packages are almost useless for
non-PC/workstation like hardware. This goes with arm and mips too.
Reply to: