[Cupt-devel] Bug#700708: Bug#700708: cupt: why does cupt maintain its own apt repo database

[Eugene V. Lyubimkin]

Hello,

Control: tags -1 + wontfix
Control: unblock -1 by 623113

2013-02-16 14:04, Jonathan Nieder:
[...]
> Ritesh Raj Sarraf wrote:
> 
> > Are there good reasons why cupt maintains its own database?

Unfortunately, yes. #623113 was mentioned already. It's not only about
InRelease files -- APT effectively changed the "directory format" in the
incompatibly way and nobody can predict when that can happen again.
lists/ directory format is completely undocumented, and APT quite
naturally keeps is as internal.

Nice side effects:

- Cupt repository metadata cleaner cannot/doesn't delete unknown APT files;
- The option 'cupt::update::keep-bad-signatures', which is incompatible
  with APT file structure, can be enabled by default.
- Cupt can check Release file signatures on every run (for, for example,
  expiration or revocation), not only at a metadata update run.

-- 
Eugene V. Lyubimkin aka JackYF, JID: jackyf.devel(maildog)gmail.com
C++ GNU/Linux userspace developer, Debian Developer