Public bug reported:
If a package has a space in its Filename: entry in the Packages file,
you get errors on HTTP resolution.
Normal Debian repos don't have a case like that, but the Packages file
should work even if packages are not stored in the pool in the most
usual way.
** Affects: apt
On 6 December 2012 05:09, Thomas Bushnell, BSG
1086...@bugs.launchpad.net wrote:
If a package has a space in its Filename: entry in the Packages file,
you get errors on HTTP resolution.
Why are there spaces, is it due to a service that munges filenames
with “s/+/ /g” on upload? Provide
Multiple filenames? Policy? Binary packages do not have filename fields at
all. I'm talking about Filename fields in the Packages file in an archive.
I'm not talking about S3 at all.
dpkg-deb only generates the last component of a filename, the problem as I
encountered it concerned a repo with
On 6 December 2012 10:00, Thomas Bushnell, BSG
1086...@bugs.launchpad.net wrote:
the problem as I
encountered it concerned a repo with spaces in some directory names.
Debian Policy doesn't address Packages files at all, nor archive
layout.
Appendix D, Control files and their fields?
--
You
Also, there is this statement in section 5.1:
Whitespace must not appear inside names (of packages,
architectures, files or anything else) or version numbers, or
between the characters of multi-character version
relationships.
--
You received this bug notification because you are a member
Thanks for the reference. I apologize for missing section D; it's not
relevant here, but I had forgotten that it has those things. It doesn't
actually say much relevant here.
However, I think section 5.1 is dispositive, so this isn't a bug. It's an
unfortunate restriction, because it ends up
On 6 December 2012 12:05, Thomas Bushnell, BSG
1086...@bugs.launchpad.net wrote:
Thanks for the reference.
Yes, who doesn't enjoy a good read of policy documents?
I apologize for missing section D; it's not
relevant here, but I had forgotten that it has those things. It doesn't
actually say
On 6 December 2012 13:27, Daniel Hartwig mand...@gmail.com wrote:
Regardless of how debian-policy defines valid filenames /in control
files/, the APT Acquire system and HTTP method can be used outside the
context of debian control files, and should still issue
correctly-formed HTTP requests
