- Package:
- open-infrastructure-system-build
- Source:
- open-infrastructure-system-tools
- Submitter:
- Raphaël Hertzog
- Date:
- 2021-02-05 22:36:02 UTC
- Severity:
- normal
If you download a Nessus deb from here: https://www.tenable.com/products/nessus/select-your-operating-system You get a Nessus-6.5.6-debian6_amd64.deb file for a "Nessus" package. Note the uppercase N in the package name... (both in the filename and in the .deb meta-data shown with dpkg -I) Put that file in config/packages.chroot/ and try a live-build, you will get an error like this: [2016-03-19 19:50:13] lb chroot_install-packages install P: Begin installing packages (install pass)... Reading package lists... Building dependency tree... Reading state information... E: Unable to locate package Nessus P: Begin unmounting filesystems... P: Saving caches... Reading package lists... Building dependency tree... Reading state information...
Hi, I am not involved in live-build, but: Which is broken. https://www.debian.org/doc/debian-policy/ch-binary.html#s3.1 points to https://www.debian.org/doc/debian-policy/ch-controlfields.html#s-f-Package which points to https://www.debian.org/doc/debian-policy/ch-controlfields.html#s-f-Source which says "Package names (both source and binary, see Package, Section 5.6.7) must consist only of lower case letters (a-z), digits (0-9), plus (+) and minus (-) signs, and periods (.). They must be at least two characters long and must start with an alphanumeric character." I don't think it is a bug if one can't handle a broken package. And isn't this apt/aptitude here, anyways? So it would be apt/aptitude "bug"? Regards, Rene
It's not broken (the package works) but it doesn't conform to the Debian policy, certainly. I think it's a bug, albeit a minor one. If there was a technical reason to not create such packages, dpkg would not allow to create such packages. I have not investigated further so I don't know. It might be live-build which is not copying the files properly, it might be apt-ftparchive which is not generating the Packages file correctly or it might be apt-get not finding the package. Cheers,
Still Debian Reference tells uppercase letters are ok for package name: https://www.debian.org/doc/manuals/debian-reference/ch02.en.html#_debian_package_file_names The regexes in table 2.16 are invalid, see https://bugs.launchpad.net/ubuntu/+source/debian-reference/+bug/1913869