Re: massive bug report to replace "!kfreebsd-i386 !kfreebsd-amd64 !hurd-i386" kludges with dpkg wildcards
Robert Millan
2011/7/16 Robert Millan <r...@debian.org>:
> Title and template description (below) is self-explanatory. 156
> packages are affected (list is attached).
>
> Package: %package%
> Severity: wishlist
> User: debia...@lists.debian.org
> Usertags: kfreebsd
>
> The debian/control file in %package% uses a negated list of architectures
> to specify a package relationship (most likely Build-Depends) on a
> Linux-specific package. I.e. something like:
>
> Build-Depends: libfoo-dev [!kfreebsd-i386 !kfreebsd-amd64 !hurd-i386]
>
> This is problematic because it will fail for any future kfreebsd-* or hurd-*
> architecture (like the upcoming kfreebsd-mipsel port). The correct way
> would be to use dpkg architecture wildcards, e.g.:
>
> Build-Depends: libfoo-dev [linux-any]
>
> Please consider making this adjustment to make life easier for future
> porting efforts.
>
> --
> Robert Millan
>
--
Robert Millan
--
To UNSUBSCRIBE, email to debian-dev...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listm...@lists.debian.org
Archive: http://lists.debian.org/CAOfDtXP7z40-k64aQXpEREFe...@mail.gmail.com
Pino Toscano
Alle sabato 16 luglio 2011, Robert Millan ha scritto:
> 2011/7/16 Robert Millan <r...@debian.org>:
> > The debian/control file in %package% uses a negated list of
> > architectures to specify a package relationship (most likely
> > Build-Depends) on a Linux-specific package. I.e. something like:
> >
> > Build-Depends: libfoo-dev [!kfreebsd-i386 !kfreebsd-amd64
> > !hurd-i386]
Nice initiative!
> > User: debia...@lists.debian.org
> > Usertags: kfreebsd
I'd use some different usertag for this, as it is IMHO not that specific
to kbsd (even if it will matter for you soon, it seems); this way this
"migration" (and any other usage of wildcard archs, like for migrating
"list of linux archs" -> "linux-any", "kfreebsd-amd64 kfreebsd-i386" ->
"kfreebsd-any", etc) could be generically tracked without getting also
the kfreebsd bugs.
What about a generic:
User: debian...@lists.debian.org
Usertags: wildcard-archs
?
A couple of notes for packages in your list:
- google-gadgets, qtmobility
they have been fixed already in their git packaging repository,
so their next upload will make use of wildcard archs
- kradio4
I can do a QA upload for it
--
Pino Toscano
Robert Millan
>> > User: debia...@lists.debian.org
>> > Usertags: kfreebsd
>
> I'd use some different usertag for this, as it is IMHO not that specific
> to kbsd (even if it will matter for you soon, it seems); this way this
> "migration" (and any other usage of wildcard archs, like for migrating
> "list of linux archs" -> "linux-any", "kfreebsd-amd64 kfreebsd-i386" ->
> "kfreebsd-any", etc) could be generically tracked without getting also
> the kfreebsd bugs.
> What about a generic:
> User: debian...@lists.debian.org
> Usertags: wildcard-archs
Seems fine. I think I'll be a bit more specific and use "linux-any"
and "kfreebsd-any" as tags.
> - google-gadgets, qtmobility
> they have been fixed already in their git packaging repository,
> so their next upload will make use of wildcard archs
Thanks! I'm removing them from my list.
> - kradio4
> I can do a QA upload for it
Nice, please let me know when you do.
--
Robert Millan
--
To UNSUBSCRIBE, email to debian-hu...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listm...@lists.debian.org
Archive: http://lists.debian.org/CAOfDtXO26j5mwy+mBNyMJht...@mail.gmail.com
Neil Williams
Robert Millan <r...@debian.org> wrote:
> Title and template description (below) is self-explanatory. 156
> packages are affected (list is attached).
>
More usefully, the dd-list of the packages is attached.
--
Neil Williams
=============
http://www.linux.codehelp.co.uk/
Josselin Mouette
> Debian Evolution Maintainers
> <pkg-evolutio...@lists.alioth.debian.org>
> evolution
Already fixed in experimental.
> Debian GNOME Maintainers
> <pkg-gnome-...@lists.alioth.debian.org>
> libproxy (U)
Will be in the next upload, no need for the bug report.
Thanks,
--
.''`. Josselin Mouette
: :' :
`. `'
`-
Bernd Zeimetz
>
> More usefully, the dd-list of the packages is attached.
>
> Bernd Zeimetz <bz...@debian.org>
> gpsd
> zbar
Both fixed in git, will be included in the next upload.
--
Bernd Zeimetz Debian GNU/Linux Developer
http://bzed.de http://www.debian.org
GPG Fingerprint: ECA1 E3F2 8E11 2432 D485 DD95 EB36 171A 6FF9 435F
--
To UNSUBSCRIBE, email to debian-dev...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listm...@lists.debian.org
Erik de Castro Lopo
> Title and template description (below) is self-explanatory. 156
> packages are affected (list is attached).
>
> Package: %package%
> Severity: wishlist
> User: debia...@lists.debian.org
> Usertags: kfreebsd
>
> The debian/control file in %package% uses a negated list of architectures
> to specify a package relationship (most likely Build-Depends) on a
> Linux-specific package. I.e. something like:
>
> Build-Depends: libfoo-dev [!kfreebsd-i386 !kfreebsd-amd64 !hurd-i386]
Is anyone working on making this a lintian warning?
The package I uploaded last night would have been fixed if this
was caught by lintian :-).
Erik
--
----------------------------------------------------------------------
Erik de Castro Lopo
http://www.mega-nerd.com/
--
To UNSUBSCRIBE, email to debian-dev...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listm...@lists.debian.org
Archive: http://lists.debian.org/20110719130609...@mega-nerd.com