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 example. Issue on Amazon S3 has already been reported; is a wontfix bug in their system; and has the work-around of percent-encoding the filename during upload (IIRC). > 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. There is very little restriction on directory structure, however, format of filenames is effectively restricted by the combination of debian-policy and the names that dpkg-deb generates. Note that dpkg-deb is the only supported tool for creating binary packages. Other tools rely on the naming scheme used by dpkg-deb, especially in contexts where Filename is not available. Further, filenames with spaces can not appear in the Filename field as space is used to separate multiple filenames. Ref: debian-policy appendices B through D -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1086997 Title: apt-get fails if a package has a space in its Filename To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1086997/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
