Re: MBF alert: packages with very long source / .deb filenames

[Goswin von Brederlow <goswin-v-b@web.de>]

Andreas Metzler <ametzler@downhill.at.eu.org> writes:

> In gmane.linux.debian.devel.general Joey Hess <joeyh@debian.org> wrote:
>> Steve McIntyre wrote:
>>> There are uses I've heard about, including (apparently quite common)
>>> using CDs and DVDs to seed a mirror on a Windows server.
>
>> If I had to chose between that working, and not needing to worry about
>> filename lengths, I'd choose the latter.
>
>>> >Is it possible to provide Joliet filenames for only a subset of files?
>
>>> It is, yes. But not something I'd like to do if we can avoid it.
>
>> One approach then would be to omit joliet filenames for the few long
>> packages. This would not even impact your use case above much, since
>> any mirror seeded from files from CDs needs a further sync step.
>
> Hello,
> An alternative approach would be to use a different *filename* while
> keeping the package name unchanged (This could be done on both mirrors
> and CD.) Iirc apt/dpkg have absolutely no problem with "foo.deb"
> containing version 1:3.2.1-11+squeeze2 of the 
> openoffice.org-report-builder-bin i386 package. I do not know about
> dak, though.
>
> cu andreas

Doesn't work for sources as the dsc files are signed and therefore
unalterable. Unless you want to teach dpkg about the renaming rules too.

MfG
        Goswin