Bug#929729: lintian: \n in filenames cause "md5sum: ...: No such file or directory"
Hi Felix,
> After a cursory review of filename handling in Lintian's index files I
> can think of three possible solutions:
>
> 1. Use String::Escape in both directions to make sure the
> transformation is reversible. (It currently isn't.)
> 2. Use Base64 to encode file names in the index.
> 3. Use an embedded DB such as SQLite in collections.
Do we need any of these techniques? Can we decree that the index files
are escaped or unescaped (I'd be +1 on the latter, mind) and then
adjust all the consumer/producers of that data to reflect that? The
current situation as I understand it is that some assume the former,
some the latter.
> > Sure thing. (I wonder whether we should also check for (at least) \t
> > and possibly even *invalid* unicode characters; those are a great way
> > to make programs blow up.)
>
> Since filenames are arbitrary byte sequences that serve as valid
> identifiers in the file system, I am not sure it makes sense to impose
> UTF-8 validation in Lintian.
Exactly — this is what I was trying to say, sorry..
Regards,
--
,''`.
: :' : Chris Lamb
`. `'` lamby@debian.org 🍥 chris-lamb.co.uk
`-
Reply to: