Package: mic2
Severity: wishlist
User: debian-de...@lists.debian.org
Usertags: linux-any
The debian/control file in mic2 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:
Package: xmms2
Severity: wishlist
User: debian-de...@lists.debian.org
Usertags: linux-any
The debian/control file in xmms2 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:
Package: libgtop2
Severity: wishlist
User: debian-de...@lists.debian.org
Usertags: kfreebsd-any
The debian/control file in libgtop2 uses a hardcoded list of kfreebsd-*
architectures (e.g kfreebsd-i386 kfreebsd-amd64) to specify a package
relationship (most likely Build-Depends) that isn't
Package: soundmodem
Severity: wishlist
User: debian-de...@lists.debian.org
Usertags: linux-any
The debian/control file in soundmodem uses a negated list of architectures
to specify a package relationship (most likely Build-Depends) on a
Linux-specific package. I.e. something like:
Package: libao
Severity: wishlist
User: debian-de...@lists.debian.org
Usertags: linux-any
The debian/control file in libao 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:
Package: checkinstall
Severity: wishlist
User: debian-de...@lists.debian.org
Usertags: kfreebsd-any
The debian/control file in checkinstall uses a hardcoded list of kfreebsd-*
architectures (e.g kfreebsd-i386 kfreebsd-amd64) to specify a package
relationship (most likely Build-Depends) that isn't
Package: stk
Severity: wishlist
User: debian-de...@lists.debian.org
Usertags: linux-any
The debian/control file in stk 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
Package: openmpi
Severity: wishlist
User: debian-de...@lists.debian.org
Usertags: linux-any
The debian/control file in openmpi 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:
Package: iceweasel
Severity: wishlist
User: debian-de...@lists.debian.org
Usertags: linux-any
The debian/control file in iceweasel 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:
!kfreebsd-any]
Thanks!
--
Robert Millan
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
/zsh.git;a=commitdiff;h=fbaba904b5374b3a8661d0fb02fd167ec9f5dc73
Yes. Both work but the latter version is much easier to read/understand.
Thank you
--
Robert Millan
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas
Package: iceape
Severity: wishlist
User: debian-de...@lists.debian.org
Usertags: linux-any
The debian/control file in iceape 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:
Package: snort
Severity: wishlist
User: debian-de...@lists.debian.org
Usertags: linux-any
The debian/control file in snort 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:
Package: amsynth
Severity: wishlist
User: debian-de...@lists.debian.org
Usertags: linux-any
The debian/control file in amsynth 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:
Package: gimp
Severity: wishlist
User: debian-de...@lists.debian.org
Usertags: linux-any
The debian/control file in gimp 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:
Package: libcanberra
Severity: wishlist
User: debian-de...@lists.debian.org
Usertags: linux-any
The debian/control file in libcanberra uses a negated list of architectures
to specify a package relationship (most likely Build-Depends) on a
Linux-specific package. I.e. something like:
Package: sshfs
Severity: important
User: debian-...@lists.debian.org
Usertags: kfreebsd
Hi
This package is not installable on kfreebsd-i386 or kfreebsd-amd64 because it
depends unconditionally on fuse-utils.
If sshfs depends on fuse-utils only to ensure that FUSE support is enabled,
please
Package: k3d
Severity: wishlist
User: debian-de...@lists.debian.org
Usertags: linux-any
The debian/control file in k3d 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
Package: xemacs21
Severity: wishlist
User: debian-de...@lists.debian.org
Usertags: linux-any
The debian/control file in xemacs21 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:
Package: wireshark
Severity: wishlist
User: debian-de...@lists.debian.org
Usertags: linux-any
The debian/control file in wireshark 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:
Package: parted
Severity: wishlist
User: debian-de...@lists.debian.org
Usertags: linux-any
The debian/control file in parted 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:
Package: kphone
Severity: wishlist
User: debian-de...@lists.debian.org
Usertags: linux-any
The debian/control file in kphone 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:
Package: freeglut
Severity: wishlist
User: debian-de...@lists.debian.org
Usertags: kfreebsd-any
The debian/control file in freeglut uses a hardcoded list of kfreebsd-*
architectures (e.g kfreebsd-i386 kfreebsd-amd64) to specify a package
relationship (most likely Build-Depends) that isn't
Package: curlftpfs
Severity: important
User: debian-...@lists.debian.org
Usertags: kfreebsd
Hi
This package is not installable on kfreebsd-i386 or kfreebsd-amd64 because it
depends unconditionally on fuse-utils.
If curlftpfs depends on fuse-utils only to ensure that FUSE support is enabled,
Package: recordmydesktop
Severity: wishlist
User: debian-de...@lists.debian.org
Usertags: linux-any
The debian/control file in recordmydesktop uses a negated list of architectures
to specify a package relationship (most likely Build-Depends) on a
Linux-specific package. I.e. something like:
Package: ecasound2.2
Severity: wishlist
User: debian-de...@lists.debian.org
Usertags: linux-any
The debian/control file in ecasound2.2 uses a negated list of architectures
to specify a package relationship (most likely Build-Depends) on a
Linux-specific package. I.e. something like:
Package: fusedav
Severity: important
User: debian-...@lists.debian.org
Usertags: kfreebsd
Hi
This package is not installable on kfreebsd-i386 or kfreebsd-amd64 because it
depends unconditionally on fuse-utils.
If fusedav depends on fuse-utils only to ensure that FUSE support is enabled,
please
Package: crossfire-client
Severity: wishlist
User: debian-de...@lists.debian.org
Usertags: linux-any
The debian/control file in crossfire-client uses a negated list of architectures
to specify a package relationship (most likely Build-Depends) on a
Linux-specific package. I.e. something like:
Package: totem
Version: 2.30.2-6
Severity: wishlist
Tags: patch
User: debian-...@lists.debian.org
Usertags: kfreebsd
Please consider this patch so that totem is buildable on future ports of
Debian GNU/kFreeBSD (e.g. kfreebsd-mipsel).
Thanks!
-- System Information:
Debian Release: wheezy/sid
Package: argyll
Severity: wishlist
User: debian-de...@lists.debian.org
Usertags: kfreebsd-any
The debian/control file in argyll uses a hardcoded list of kfreebsd-*
architectures (e.g kfreebsd-i386 kfreebsd-amd64) to specify a package
relationship (most likely Build-Depends) that isn't specific to
Package: openscap
Severity: wishlist
User: debian-de...@lists.debian.org
Usertags: linux-any
The debian/control file in openscap 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:
Package: collectd
Severity: wishlist
User: debian-de...@lists.debian.org
Usertags: linux-any
The debian/control file in collectd 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:
Package: gfarm2fs
Severity: important
User: debian-...@lists.debian.org
Usertags: kfreebsd
Hi
This package is not installable on kfreebsd-i386 or kfreebsd-amd64 because it
depends unconditionally on fuse-utils.
If gfarm2fs depends on fuse-utils only to ensure that FUSE support is enabled,
Package: muddleftpd
Severity: wishlist
User: debian-de...@lists.debian.org
Usertags: linux-any
The debian/control file in muddleftpd uses a negated list of architectures
to specify a package relationship (most likely Build-Depends) on a
Linux-specific package. I.e. something like:
Package: cyrus-imapd-2.4
Severity: wishlist
User: debian-de...@lists.debian.org
Usertags: kfreebsd-any
The debian/control file in cyrus-imapd-2.4 uses a hardcoded list of kfreebsd-*
architectures (e.g kfreebsd-i386 kfreebsd-amd64) to specify a package
relationship (most likely Build-Depends) that
Package: lde
Severity: wishlist
User: debian-de...@lists.debian.org
Usertags: linux-any
The debian/control file in lde 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
Package: clanlib
Severity: wishlist
User: debian-de...@lists.debian.org
Usertags: linux-any
The debian/control file in clanlib 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:
Package: ices2
Severity: wishlist
User: debian-de...@lists.debian.org
Usertags: linux-any
The debian/control file in ices2 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:
Package: gjacktransport
Severity: wishlist
User: debian-de...@lists.debian.org
Usertags: linux-any
The debian/control file in gjacktransport uses a negated list of architectures
to specify a package relationship (most likely Build-Depends) on a
Linux-specific package. I.e. something like:
Package: logrotate
Severity: wishlist
User: debian-de...@lists.debian.org
Usertags: linux-any
The debian/control file in logrotate 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:
Package: pinball
Severity: wishlist
User: debian-de...@lists.debian.org
Usertags: linux-any
The debian/control file in pinball 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:
Package: xserver-xorg-input-joystick
Severity: wishlist
User: debian-de...@lists.debian.org
Usertags: kfreebsd-any
The debian/control file in xserver-xorg-input-joystick uses a hardcoded list of
kfreebsd-*
architectures (e.g kfreebsd-i386 kfreebsd-amd64) to specify a package
relationship (most
Package: cmus
Severity: wishlist
User: debian-de...@lists.debian.org
Usertags: linux-any
The debian/control file in cmus 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:
know of any problem with relying on this
feature (note that it's been present in dpkg since 2006).
--
Robert Millan
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Package: libsocialweb
Severity: wishlist
User: debian-de...@lists.debian.org
Usertags: linux-any
The debian/control file in libsocialweb uses a negated list of architectures
to specify a package relationship (most likely Build-Depends) on a
Linux-specific package. I.e. something like:
Package: apache2
Severity: wishlist
User: debian-de...@lists.debian.org
Usertags: linux-any
The debian/control file in apache2 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:
Package: gem
Severity: wishlist
User: debian-de...@lists.debian.org
Usertags: linux-any
The debian/control file in gem 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
Package: ekeyd
Severity: wishlist
User: debian-de...@lists.debian.org
Usertags: linux-any
The debian/control file in ekeyd 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:
Package: gnokii
Severity: wishlist
User: debian-de...@lists.debian.org
Usertags: linux-any
The debian/control file in gnokii 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:
Package: mhwaveedit
Severity: wishlist
User: debian-de...@lists.debian.org
Usertags: linux-any
The debian/control file in mhwaveedit uses a negated list of architectures
to specify a package relationship (most likely Build-Depends) on a
Linux-specific package. I.e. something like:
Package: qpxtool
Severity: wishlist
User: debian-de...@lists.debian.org
Usertags: kfreebsd-any
The debian/control file in qpxtool uses a hardcoded list of kfreebsd-*
architectures (e.g kfreebsd-i386 kfreebsd-amd64) to specify a package
relationship (most likely Build-Depends) that isn't specific
Package: syslog-ng
Severity: wishlist
User: debian-de...@lists.debian.org
Usertags: linux-any
The debian/control file in syslog-ng 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:
Package: util-linux
Severity: wishlist
User: debian-de...@lists.debian.org
Usertags: linux-any
The debian/control file in util-linux uses a negated list of architectures
to specify a package relationship (most likely Build-Depends) on a
Linux-specific package. I.e. something like:
Package: phasex
Severity: wishlist
User: debian-de...@lists.debian.org
Usertags: linux-any
The debian/control file in phasex 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:
Package: mpd
Severity: wishlist
User: debian-de...@lists.debian.org
Usertags: linux-any
The debian/control file in mpd 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
Package: vsftpd
Severity: wishlist
User: debian-de...@lists.debian.org
Usertags: linux-any
The debian/control file in vsftpd 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:
Package: cegui-mk2
Severity: wishlist
User: debian-de...@lists.debian.org
Usertags: linux-any
The debian/control file in cegui-mk2 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:
Package: vlc
Severity: wishlist
User: debian-de...@lists.debian.org
Usertags: linux-any
The debian/control file in vlc 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
Package: libsysactivity
Severity: wishlist
User: debian-de...@lists.debian.org
Usertags: kfreebsd-any
The debian/control file in libsysactivity uses a hardcoded list of kfreebsd-*
architectures (e.g kfreebsd-i386 kfreebsd-amd64) to specify a package
relationship (most likely Build-Depends) that
Package: pilot-link
Severity: wishlist
User: debian-de...@lists.debian.org
Usertags: linux-any
The debian/control file in pilot-link uses a negated list of architectures
to specify a package relationship (most likely Build-Depends) on a
Linux-specific package. I.e. something like:
Package: wdm
Severity: wishlist
User: debian-de...@lists.debian.org
Usertags: linux-any
The debian/control file in wdm 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
Package: fmit
Severity: wishlist
User: debian-de...@lists.debian.org
Usertags: linux-any
The debian/control file in fmit 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:
Package: zsh-beta
Severity: wishlist
User: debian-de...@lists.debian.org
Usertags: linux-any
The debian/control file in zsh-beta 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:
Package: net-snmp
Severity: wishlist
Tags: patch
User: debian-...@lists.debian.org
Usertags: kfreebsd
Please consider this patch so that net-snmp is buildable on future ports of
Debian GNU/kFreeBSD (e.g. kfreebsd-mipsel).
Thanks!
-- System Information:
Debian Release: wheezy/sid
APT prefers
Package: k3b
Severity: wishlist
User: debian-de...@lists.debian.org
Usertags: kfreebsd-any
The debian/control file in k3b uses a hardcoded list of kfreebsd-*
architectures (e.g kfreebsd-i386 kfreebsd-amd64) to specify a package
relationship (most likely Build-Depends) that isn't specific to i386
Package: netams
Version: 3.4.5-2
Severity: wishlist
Tags: patch
User: debian-...@lists.debian.org
Usertags: kfreebsd
Please consider this patch so that netams is buildable on future ports of
Debian GNU/kFreeBSD (e.g. kfreebsd-mipsel).
Thanks!
-- System Information:
Debian Release: wheezy/sid
Hi Chris
2011/7/19 Chris Lamb la...@debian.org:
What's the best solution if the package is Architecture: all (which do not
support architecture-specific dependencies)?
I didn't know there was python support for FUSE. In this particular
case, please see attached patch.
--
Robert Millan
Package: xmp
Severity: wishlist
User: debian-de...@lists.debian.org
Usertags: linux-any
The debian/control file in xmp 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
Package: timidity
Severity: wishlist
User: debian-de...@lists.debian.org
Usertags: linux-any
The debian/control file in timidity 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:
Package: flickrfs
Severity: important
User: debian-...@lists.debian.org
Usertags: kfreebsd
Hi
This package is not installable on kfreebsd-i386 or kfreebsd-amd64 because it
depends unconditionally on fuse-utils.
If flickrfs depends on fuse-utils only to ensure that FUSE support is enabled,
Package: syncevolution
Severity: wishlist
User: debian-de...@lists.debian.org
Usertags: linux-any
The debian/control file in syncevolution uses a negated list of architectures
to specify a package relationship (most likely Build-Depends) on a
Linux-specific package. I.e. something like:
Package: wildmidi
Severity: wishlist
User: debian-de...@lists.debian.org
Usertags: linux-any
The debian/control file in wildmidi 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:
Package: thunar-vfs
Severity: wishlist
User: debian-de...@lists.debian.org
Usertags: linux-any
The debian/control file in thunar-vfs uses a negated list of architectures
to specify a package relationship (most likely Build-Depends) on a
Linux-specific package. I.e. something like:
Package: bitmeter
Severity: wishlist
User: debian-de...@lists.debian.org
Usertags: linux-any
The debian/control file in bitmeter 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:
Package: snd
Severity: wishlist
User: debian-de...@lists.debian.org
Usertags: linux-any
The debian/control file in snd 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
Package: python-fuse
Severity: important
User: debian-...@lists.debian.org
Usertags: kfreebsd
Hi
This package is not installable on kfreebsd-i386 or kfreebsd-amd64 because it
depends unconditionally on fuse-utils.
If python-fuse depends on fuse-utils only to ensure that FUSE support is
Package: cdparanoia
Severity: wishlist
User: debian-de...@lists.debian.org
Usertags: kfreebsd-any
The debian/control file in cdparanoia uses a hardcoded list of kfreebsd-*
architectures (e.g kfreebsd-i386 kfreebsd-amd64) to specify a package
relationship (most likely Build-Depends) that isn't
Package: squid3
Severity: wishlist
User: debian-de...@lists.debian.org
Usertags: linux-any
The debian/control file in squid3 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:
Package: mpg123
Severity: wishlist
User: debian-de...@lists.debian.org
Usertags: linux-any
The debian/control file in mpg123 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:
Package: fcron
Severity: wishlist
User: debian-de...@lists.debian.org
Usertags: linux-any
The debian/control file in fcron 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:
Package: mplayer
Severity: wishlist
User: debian-de...@lists.debian.org
Usertags: linux-any
The debian/control file in mplayer 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:
Package: zbar
Severity: wishlist
User: debian-de...@lists.debian.org
Usertags: linux-any
The debian/control file in zbar 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:
Package: gnome-mplayer
Severity: wishlist
User: debian-de...@lists.debian.org
Usertags: linux-any
The debian/control file in gnome-mplayer uses a negated list of architectures
to specify a package relationship (most likely Build-Depends) on a
Linux-specific package. I.e. something like:
Package: rlinetd
Severity: wishlist
User: debian-de...@lists.debian.org
Usertags: linux-any
The debian/control file in rlinetd 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:
Package: mumble
Severity: wishlist
User: debian-de...@lists.debian.org
Usertags: linux-any
The debian/control file in mumble 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:
2011/7/19 Robert Millan r...@debian.org:
Hi Chris
2011/7/19 Chris Lamb la...@debian.org:
What's the best solution if the package is Architecture: all (which do not
support architecture-specific dependencies)?
I didn't know there was python support for FUSE. In this particular
case, please
Package: pax-utils
Severity: wishlist
User: debian-de...@lists.debian.org
Usertags: linux-any
The debian/control file in pax-utils 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:
Package: kwave
Severity: wishlist
User: debian-de...@lists.debian.org
Usertags: linux-any
The debian/control file in kwave 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:
Package: libfuse-perl
Severity: important
User: debian-...@lists.debian.org
Usertags: kfreebsd
Hi
This package is not installable on kfreebsd-i386 or kfreebsd-amd64 because it
depends unconditionally on fuse-utils.
If libfuse-perl depends on fuse-utils only to ensure that FUSE support is
Package: mixxx
Severity: wishlist
User: debian-de...@lists.debian.org
Usertags: linux-any
The debian/control file in mixxx 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:
Package: brutefir
Severity: wishlist
User: debian-de...@lists.debian.org
Usertags: linux-any
The debian/control file in brutefir 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:
Package: muroar
Severity: wishlist
User: debian-de...@lists.debian.org
Usertags: linux-any
The debian/control file in muroar 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:
Package: mach
Severity: wishlist
User: debian-de...@lists.debian.org
Usertags: linux-any
The debian/control file in mach 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:
Package: libopenobex
Severity: wishlist
User: debian-de...@lists.debian.org
Usertags: linux-any
The debian/control file in libopenobex uses a negated list of architectures
to specify a package relationship (most likely Build-Depends) on a
Linux-specific package. I.e. something like:
Package: glame
Severity: wishlist
User: debian-de...@lists.debian.org
Usertags: linux-any
The debian/control file in glame 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:
Package: gammu
Severity: wishlist
User: debian-de...@lists.debian.org
Usertags: linux-any
The debian/control file in gammu 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:
Package: k8temp
Severity: wishlist
User: debian-de...@lists.debian.org
Usertags: kfreebsd-any
The debian/control file in k8temp uses a hardcoded list of kfreebsd-*
architectures (e.g kfreebsd-i386 kfreebsd-amd64) to specify a package
relationship (most likely Build-Depends) that isn't specific to
Package: mythtvfs
Severity: important
User: debian-...@lists.debian.org
Usertags: kfreebsd
Hi
This package is not installable on kfreebsd-i386 or kfreebsd-amd64 because it
depends unconditionally on fuse-utils.
If mythtvfs depends on fuse-utils only to ensure that FUSE support is enabled,
Package: gogoc
Severity: wishlist
User: debian-de...@lists.debian.org
Usertags: linux-any
The debian/control file in gogoc 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:
Package: lirc
Severity: wishlist
User: debian-de...@lists.debian.org
Usertags: linux-any
The debian/control file in lirc 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:
901 - 1000 of 4214 matches
Mail list logo
