On Fri, 30 Jun 2006, Jari Aalto+mail.linux wrote:
> * Fri 2006-06-30 Sam Morris
> > File a bug against library B requesting that the new upstream
> > release be packaged. Call that bug #987654. Then issue the
> > following BTS command:
> >
> >block 123456 by 987654
>
> When 987654 is closed,
* Fri 2006-06-30 Sam Morris
* Message-Id: e82p4q$c5$1 AT sea.gmane.org
>> - Bug 123456 has been filed to GUI package A
>> - In order the program to behave correct, library B needs to be updated
>> to latest upstream version.
>>
>> So, until new B is packaged to debian, it blocks mar
On 30/06/06, Sam Morris <[EMAIL PROTECTED]> wrote:
> So, until new B is packaged to debian, it blocks marking bug 123456 in
> A done. How should this be handled in BTS system? Should the bug be
> reassigned to package B?
File a bug against library B requesting that the new upstream release be
pa
> - Bug 123456 has been filed to GUI package A
> - In order the program to behave correct, library B needs to be updated
> to latest upstream version.
>
> So, until new B is packaged to debian, it blocks marking bug 123456 in
> A done. How should this be handled in BTS system? Should
Situation:
- Bug 123456 has been filed to GUI package A
- In order the program to behave correct, library B needs to be updated
to latest upstream version.
So, until new B is packaged to debian, it blocks marking bug 123456 in
A done. How should this be handled in BTS system? Shoul
5 matches
Mail list logo
