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

Re: xfree86-driver-synaptics blocked by xserver-xfree86 on s390



On Thu, Jun 10, 2004 at 05:09:53PM +0200, Mattia Dongili wrote:
> On Mon, Jun 07, 2004 at 12:56:50PM +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:
> > [...]
> > > > 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. The package is ready to be uploaded,
> > > but how am I supposed to proceed now? ask for removal first and then
> > > upload or the opposite?

> > Do both instead of waiting. There is no problem if the s390 buildd
> > tries to build xfree86-driver-synaptics before the binary has been
> > removed (and xfree86-driver-synaptics has been added to
> > http://buildd.debian.org/quinn-diff/Packages-arch-specific), the build
> > will simply fail because dpkg-buildpackage (or is it sbuild?) checks
> > the architecture field.

> sorry for being so pedantic. Today a bug has been submitted (#253616)
> regarding this issue. The submitter states that the control file for
> xfree86 states xserver-xfree86 is 
> Architecture:  alpha amd64 arm hppa hurd-i386 i386 ia64 m68k mips mipsel
>                netbsd-i386 powerpc sh3 sh4 sparc

> but xserver-xfree86 is only available on alpha arm hppa i386 ia64 m68k
> mips mipsel powerpc sparc [1]

> so removing only s390 from the Architecture field of
> xfree86-driver-synaptics may not be enough, right? So the correct
> solution would be to only Suggest: xserver-xfree86 (>> 4.1.0)

No, the correct solution is to ensure the xfree86-driver-synaptics
package isn't built on architectures where it's known to be useless.
Has this package been added to the packages-architecture-specific list
for the autobuilders?  If not, it's my understanding that it should be;
and then the package that's already been built on s390 should be
removed.

The other architectures in the xfree86 control file can be ignored --
they don't have autobuilders that are uploading to the archive.

-- 
Steve Langasek
postmodern programmer

Attachment: signature.asc
Description: Digital signature


Reply to: