Hi Francesco,

On Mon, Sep 07, 2009 at 10:09:55PM +0200, Francesco Poli (t1000) wrote:
> Package: rakarrack
> Version: 0.3.0-1
> Severity: important
> 
> 
> Hi!
> Thanks for maintaining rakarrack in Debian!

Thank you for trying to use it on 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

Actually it's not an unsatisfied dependency. It's a problem with alsa-utils
1.0.20-2. I've seen it's already reported, so I've reforced the need of fixing
it soon. Now I noted 1.0.20-3 was pushed to Debian and it's supposed to solve
this issue in rakarrack:

http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=539983

Let's wait a little. According to the buildd log rakarrack was built against
the broken alsa-utils 1.0.20-2.

> 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?

No, it's not a bug in britney. Please look:

http://www.debian.org/devel/testing

As you can see, a package doesn't need to be compiled in all archs to go to
testing. Also, as I said, it's not a missing dependency issue. So, let's wait
for the next build against the fixed alsa-utils.

Regards,

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




-- 
To UNSUBSCRIBE, email to [email protected]
with a subject of "unsubscribe". Trouble? Contact [email protected]

Reply via email to