Re: Processed: block 322762 with 355341
>>>>> "Don" == Don Armstrong <don@debian.org> writes:
>> > > # Automatically generated email from bts, devscripts
>> version 2.9.15 > > block 322762 with 355341 > Bug#322762:
>> /usr/doc still exists (transition tracking bug) > Was blocked
>> by: 189856 190020 203278 254800 254913 254924 254930 255590
>> 256250 302504 319726 320084 320103 321926 322749 322769 322772
>> 322775 322776 322778 322779 322781 322782 322783 322784 322785
>> 322786 322787 322788 322789 322790 322791 322792 322793 322794
>> 322795 322797 322798 322799 322800 322801 322803 322804 322805
>> 322806 322807 322808 322809 322810 322811 322812 322813 322814
>> 322815 322816 322817 322818 322819 322820 322828 322829 322830
>> 322831 322832 322833 322834 322835 322837 322838 322839 352893
>> 352894 353569 > Blocking bugs added: 355341
Don> Indicates that a bug cannot be closed/fixed/addressed until
Don> the bugs that it is blocked by are closed.
Two more questions.
1. according to the above, bug 355341 was added to the block list of
322762. If I go to <URL:http://bugs.debian.org/322762>, there is a list of
blocking bugs at the top:
--- cut ---
ix blocked by #189856: /usr/doc/libruby still exists after upgrade to
unstable;
...etc...
--- cut ---
but I don't see bug 355341 listed. Why not?
However, at the bottom it is listed:
--- cut ---
Blocking bugs added: 355341 Request was from Joey Hess <joeyh@debian.org> to
control@bugs.debian.org. Full text and rfc822 format available.
--- cut ---
2. is it possible to list all bugs that are not blocked?
3. does blocking imply any action will automatically be taken once all
blocked bugs are closed? What happens if you try to close a bug that
is blocked?
Oh wait, thats three, not two.
--
Brian May <bam@debian.org>
Reply to: