Your message dated Fri, 11 Sep 2009 23:08:06 -0300
with message-id <[email protected]>
and subject line Built successfully
has caused the Debian Bug report #545531,
regarding rakarrack: no i386 binary ?!?
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.)


-- 
545531: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=545531
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: rakarrack
Version: 0.3.0-1
Severity: important


Hi!
Thanks for maintaining rakarrack in Debian!


I really cannot understand what's going on.

It seems to me that the i386 binary package of rakarrack has not yet
been built: the build status [1] says "Building", the build log [2]
seems to indicate some unsatisfied dependency, and the package seems
to be missing from i386 mirrors.

[1] https://buildd.debian.org/pkg.cgi?pkg=rakarrack
[2] 
https://buildd.debian.org/fetch.cgi?pkg=rakarrack;ver=0.3.0-1;arch=i386;stamp=1251308537

Despite this lack of syncronization among architectures, the
package *did* migrate to testing [3] !   :-o

[3] http://packages.qa.debian.org/r/rakarrack/news/20090906T163952Z.html

Maybe I am misinterpreting something.

Could you please help me understand where's the problem (maybe a
bug in britney?), so that we can properly reassign this bug report?
Can this problem be solved for rakarrack?


Thanks for your time.



--- End Message ---
--- Begin Message ---
Hey, i386 binary of rakarrack package is available due to the proper fix in
alsa-utils 1.0.20-3 as I mentioned before.

Thanks for reporting and happy playing!

-- 
Tiago Bortoletto Vaz
http://tiagovaz.org
0xA504FECA - http://pgp.mit.edu



--- End Message ---

Reply via email to