Quoting Cyril Brulebois (k...@debian.org):
> Luk Claes (04/10/2010):
> > Please try to avoid such language and maybe you could include or
> > point to some explanation how the experimental buildds work to avoid
> > repeated mistakes?
>
> Like specifying build dependencies according to what one is
On 10/04/2010 06:34 PM, Cyril Brulebois wrote:
> Luk Claes (04/10/2010):
>> Please try to avoid such language and maybe you could include or
>> point to some explanation how the experimental buildds work to avoid
>> repeated mistakes?
>
> Like specifying build dependencies according to what one i
Luk Claes (04/10/2010):
> Please try to avoid such language and maybe you could include or
> point to some explanation how the experimental buildds work to avoid
> repeated mistakes?
Like specifying build dependencies according to what one is needing?
Sounds like NM 101. Like checking a build in
On 10/04/2010 05:58 PM, Cyril Brulebois wrote:
> Luk Claes (04/10/2010):
>> I understand that it can be frustrating to have these kind of build
>> failures, though note that this was a new package so it may very
>> well be introduced after the upload (I don't know if it's the case
>> now). Anyway,
Luk Claes (04/10/2010):
> I understand that it can be frustrating to have these kind of build
> failures, though note that this was a new package so it may very
> well be introduced after the upload (I don't know if it's the case
> now). Anyway, thanks for the bug report, but using this kind of
>
5 matches
Mail list logo
