* Sam Geeraerts <[email protected]> [111028 21:00]:
> Package: reprepro
> Version: 4.2.0-2squeeze1
> Severity: normal
> User: [email protected]
> Usertags: gnewsense
>
> When I use reprepro to create a local repository for or including Squeeze's
> security updates, I get warnings about a "strange filekey". E.g. when I
> `reprepro -b . update':
>
> Warning: strange filekey
> 'pool/updates/main/w/wordpress/wordpress_3.0.5+dfsg-0+squeeze1_all.deb'!
>
> It doesn't give me any further clues about what's strange about it, what the
> consequences are or how to fix the issue.
Looks like you found a ugly glitch in reprepro's pool handling.
Looking at the names of files in pool/ it does not expect the slash
coming from the component in there.
The consequences are this ugly warning and reprepro being a tiny bit
slower.
> My conf/distributions:
>
> Codename: parkes/updates
> Architectures: source i386
> Components: updates/main
> Description: gNewSense GNU/Linux
> FakeComponentPrefix: updates
> Label: gNewSense GNU/Linux
> Origin: gNewSense
> SignWith: CDCAD4EE
> Suite: parkes/updates
> Update: squeeze-updates
> Version: 3.0
> DebIndices: Packages Release . .gz .bz2
> DscIndices: Sources Release . .gz .bz2
Note that
Components: main
instead of
Components: updates/main
would have had the advantage (and disadvantage) to
store the files in pool/main/ instead of pool/updates/main/,
so that files can (and must) be reused from the non-updates
distribution if it is stored in the same repository
(can safe quite some size due to .orig.tar files,
but causes problems if security updates are fucked up).
(And it would have made the updates rule a little bit easier
and this warning not show up).
(Also note that this cannot be easily changed retroactively
without removing the old and adding the new (either having
made a copy to another distribution, or redownloading it).
Bernhard R. Link
--
To UNSUBSCRIBE, email to [email protected]
with a subject of "unsubscribe". Trouble? Contact [email protected]
