On Tue, 2002-10-15 at 23:53, Adrian Bridgett wrote: > > Is that bug (#108196) reproducible? > > Yep. It is caused if you edit debian/conffiles but forget to have a trailing > newline (it just so happened I didn't press enter whilst creating it and the > editor didn't automatically add one) - i.e instead of something like this: > > ~$ hexdump -c /var/lib/dpkg/info/passwd.conffiles > 0000000 / e t c / p a m . d / c h f n \n > > it had: > > ~$ hexdump -c /var/lib/dpkg/info/passwd.conffiles > 0000000 / e t c / p a m . d / c h f n > > Just built a small test package: > dpkg: error processing xbill_2.0-14_i386.deb (--install): > name of conffile (starting /etc/foo') is too long (>1000 characters) > > dpkg should at least say "name of conffile(...) does not end with a > newline". Even better, it could accept EOF instead.
You are right. dpkg should not fail if the last line of a file has no newline. -- Thomas
