[Piuparts-devel] Pending mass bug filing for broken symlinks detected by piuparts

[Holger Levsen]

Hi,

btw, I noticed "but logfile contains 'broken symlinks': 16818 passed" on 
sid-nodoc today which IMO makes this link totally useless...

On Samstag, 1. Juni 2013, Dave Steele wrote:
> > No, best to evaluate all problems before and then file bugs. A local
> > piuparts instance could help you with that :)
> Answer to the wrong question? I did use a local instance to generate
> the list. The question is how broken symlinks will be represented on
> p.d.o at announce time. I assume as issues.

For the ones debian-devel at l.d.o agreed to have them filed as serious, I think 
failing the piuparts test is appropriate.
 
> > Dangling symlinks pointing to manpages or other documentation (provided
> > by a recommded package probably even) are probably just "normal" bugs,
> > maybe "important".

I'd start with normal for now.

And I'd do two threads on the devel list: one about some broken symlinks 
becoming serious bugs now (and mass bug filing on that) and another, about the 
mass bug filing about broken symlinks as normal bugs.

And as soon as consensus is achieved on this, file bugs. (And change piuparts 
to fail for the serious ones.)
 
> ... and if they are resolved by the package which is calling for this
> package to be installed, they are no more than 'normal', and so on.

you mean if the broken symlink is provided by a dependend package? I dont 
think thats a bug at all then.


cheers,
	Holger
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 828 bytes
Desc: This is a digitally signed message part.
URL: <http://lists.alioth.debian.org/pipermail/piuparts-devel/attachments/20130601/cafd4175/attachment.pgp>