tag 651332 +unreproducible
thanks
Niels,
Sorry I did try to reporduce this in more isolated condition and
failed. All I can say is that it really happened but that the
circumstances were unnatural. (I was writing a script to generate a
Debian package and one of the tests was is the package lintian clean. I
think something else broke and then the issue happened. ) So altogether
hard to reprodiuce but when it does a real nuisance.
On 14/02/12 16:17, Niels Thykier wrote:
> tags 651332 + moreinfo
> thanks
>
>
> On 2011-12-08 23:00, Niels Thykier wrote:
>> On 2011-12-08 22:57, Nicholas Bamber wrote:
>>> Niels,
>>> I think the following steps should reproduce it:
>>
>>> 1.) Take a package and run lintian against it.
>>> 2.) Then delete the package and but still run lintian against it.
>>
>>> [...]
>>
>> Sadly I still cannot reproduce it (from the above):
>>
>> $ [...]
>>
>> I assume you are not removing the file while lintian is running?
>>
>> ~Niels
>>
>>
>
> Hi,
>
> So I still have not been able to reproduce the issue from the git
> version of Lintian. I suspect it has been fixed as a side-effect of
> another change, but I am not any wiser on when/what/how it happened.
>
> Admittedly I have not tried to reproducing it by removing the package(s)
> while lintian is running. However, I doubt that is what you are doing.
> I intend to close this shortly after the 2.5.5 upload, unless I am able
> to produce it.
>
> ~Niels
>
--
Nicholas Bamber | http://www.periapt.co.uk/
PGP key 3BFFE73C from pgp.mit.edu
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
