Package: reprepro
Version: 3.5.1-1
Severity: normal
Hi!
I am trying to create a repository that would look like Debian's
volatile or security repositories. Both uses Components like
updates/main or volatile/main.
Unfortunately, reprepro seems unable to handle such repositories.
The normal
* Jérémy Bobbio [EMAIL PROTECTED] [080625 14:24]:
I am trying to create a repository that would look like Debian's
volatile or security repositories. Both uses Components like
updates/main or volatile/main.
Unfortunately, reprepro seems unable to handle such repositories.
The normal
On Wed, Jun 25, 2008 at 02:39:18PM +0200, Bernhard R. Link wrote:
I think this is a hint that you want
Codename: etch/updates
Components: main
instead.
Doing this result in a Release file containing (indeed):
Codename: etch/updates
Components: main
This diverges slightly from Release
* Jérémy Bobbio [EMAIL PROTECTED] [080625 15:29]:
Doing this result in a Release file containing (indeed):
Codename: etch/updates
Components: main
This diverges slightly from Release files in security or volatile
repositories:
Codename: etch
Components: updates/main updates/contrib
On Wed, Jun 25, 2008 at 03:48:49PM +0200, Bernhard R. Link wrote:
* Jérémy Bobbio [EMAIL PROTECTED] [080625 15:29]:
Doing this result in a Release file containing (indeed):
Codename: etch/updates
Components: main
This diverges slightly from Release files in security or volatile
* Jérémy Bobbio [EMAIL PROTECTED] [080625 16:22]:
and this tends to trigger APT warnings for codename mismatch.
Hm, that must have changed (though already some time ago).
Looks like apt was changed to the inconsistent naming of security instead
of the other way around... Sigh...
6 matches
Mail list logo
