Your message dated Fri, 15 Jun 2012 09:22:10 +0200
with message-id <[email protected]>
and subject line Re: Bug#677505: RM: lilv [hurd-i386 kfreebsd-amd64 
kfreebsd-i386] -- ANAIS; Never built on non-Linux; Architecture not supported;
has caused the Debian Bug report #677505,
regarding RM: lilv [hurd-i386 kfreebsd-amd64 kfreebsd-i386] -- ANAIS; Never 
built on non-Linux; Architecture not supported;
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)


-- 
677505: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=677505
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: ftp.debian.org
Severity: normal


Hi,

please remove non-Linux builds of lilv, those architectures are not allowed in 
source.

Thanks in advance.



--- End Message ---
--- Begin Message ---
Hi!

* Alessio Treglia <[email protected]> [120614 13:27]:

> please remove non-Linux builds of lilv, those architectures are not allowed 
> in source.

Sorry, can't do:

tolimar@franck:~$ dak ls -S lilv-utils lilv liblilv-dev python-lilv liblilv-0-0
lilv-utils | 0.14.2~dfsg0-3 |       testing | amd64, armel, armhf, i386, ia64, 
mips, mipsel, powerpc, s390, s390x, sparc
lilv-utils | 0.14.2~dfsg0-3 |      unstable | amd64, armel, armhf, i386, ia64, 
mips, mipsel, powerpc, s390, s390x, sparc
liblilv-dev | 0.14.2~dfsg0-3 |       testing | amd64, armel, armhf, i386, ia64, 
mips, mipsel, powerpc, s390, s390x, sparc
liblilv-dev | 0.14.2~dfsg0-3 |      unstable | amd64, armel, armhf, i386, ia64, 
mips, mipsel, powerpc, s390, s390x, sparc
lilv-utils | 0.14.2~dfsg0-3 |       testing | amd64, armel, armhf, i386, ia64, 
mips, mipsel, powerpc, s390, s390x, sparc
lilv-utils | 0.14.2~dfsg0-3 |      unstable | amd64, armel, armhf, i386, ia64, 
mips, mipsel, powerpc, s390, s390x, sparc
liblilv-0-0 | 0.14.2~dfsg0-3 |       testing | amd64, armel, armhf, i386, ia64, 
mips, mipsel, powerpc, s390, s390x, sparc
liblilv-0-0 | 0.14.2~dfsg0-3 |      unstable | amd64, armel, armhf, i386, ia64, 
mips, mipsel, powerpc, s390, s390x, sparc
python-lilv | 0.14.2~dfsg0-3 |       testing | amd64, armel, armhf, i386, ia64, 
mips, mipsel, powerpc, s390, s390x, sparc
python-lilv | 0.14.2~dfsg0-3 |      unstable | amd64, armel, armhf, i386, ia64, 
mips, mipsel, powerpc, s390, s390x, sparc
      lilv | 0.14.2~dfsg0-3 |       testing | source
      lilv | 0.14.2~dfsg0-3 |      unstable | source


I guess they where picked up by one of the last cruft removals.


Best regards,
  Alexander


--- End Message ---

Reply via email to