Bug#570623: reprepro: please add multiple version management

classic Classic list List threaded Threaded
9 messages Options
Reply | Threaded
Open this post in threaded view
|

Bug#570623: reprepro: please add multiple version management

Jean-Christophe Dubacq
Package: reprepro
Version: 4.0.2-1
Severity: wishlist

Currently, indices built by reprepro only show the latest version of
a package. I really would like to use reprepro to have an archive
with multiple versions of a package accessible (eg for rollback).

currently I do something like that after each addition to the
repository:
cd debian
apt-ftparchive generate conf/storage.conf
apt-ftparchive -c conf/releasestorage.conf release dists/storage > dists/storage/Release
if [ -f dists/storage/Release.gpg ]; then
  rm dists/storage/Release.gpg
fi
gpg --output dists/storage/Release.gpg -ba dists/storage/Release
cd ..

But it does not take only what is tracked in the 'storage' dist,
it takes everything in the pool.

It would work much better at reprepro level.

-- System Information:
Debian Release: squeeze/sid
  APT prefers unstable
  APT policy: (800, 'unstable'), (700, 'testing'), (500, 'stable'), (50, 'experimental')
Architecture: amd64 (x86_64)

Kernel: Linux 2.6.32-trunk-amd64 (SMP w/2 CPU cores)
Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash

Versions of packages reprepro depends on:
ii  libarchive1             2.6.2-1          Single library to read/write tar,
ii  libbz2-1.0              1.0.5-4          high-quality block-sorting file co
ii  libc6                   2.10.2-6         Embedded GNU C Library: Shared lib
ii  libdb4.8                4.8.26-1         Berkeley v4.8 Database Libraries [
ii  libgpg-error0           1.6-1            library for common error values an
ii  libgpgme11              1.2.0-1.2        GPGME - GnuPG Made Easy
ii  zlib1g                  1:1.2.3.4.dfsg-3 compression library - runtime

Versions of packages reprepro recommends:
ii  apt                           0.7.25.3   Advanced front-end for dpkg

Versions of packages reprepro suggests:
ii  gnupg-agent       2.0.14-1               GNU privacy guard - password agent
pn  inoticoming       <none>                 (no description available)
ii  lzma              4.43-14                Compression method of 7z format in
ii  xz-utils          4.999.9beta+20100212-1 XZ-format compression utilities

-- no debconf information



--
To UNSUBSCRIBE, email to [hidden email]
with a subject of "unsubscribe". Trouble? Contact [hidden email]

Reply | Threaded
Open this post in threaded view
|

Bug#570623: reprepro: please add multiple version management

Bernhard R. Link-2
* Jean-Christophe Dubacq <[hidden email]> [100220 11:14]:
> Currently, indices built by reprepro only show the latest version of
> a package. I really would like to use reprepro to have an archive
> with multiple versions of a package accessible (eg for rollback).

Sorry, that is not coming soon. Having one version of a package per
distribution/architecture/component/type quadruple is heavily built into
the database layout and all the internal logic.

If you want different versions of the same package in the same
architecture with reprepro, you need to either store them in different
distributions, or you can create snapshots of distributions.
(You can also enable tracking with the options to not remove old
packages, but that will only keep the files in the pool and not in any
apt-getable index).

Hochachtungsvoll,
        Bernhard R. Link



--
To UNSUBSCRIBE, email to [hidden email]
with a subject of "unsubscribe". Trouble? Contact [hidden email]

Reply | Threaded
Open this post in threaded view
|

Bug#570623: Prognosis for integrating multiple version support into reprepro?

John Goerzen-3
In reply to this post by Jean-Christophe Dubacq
Hi folks,

First of all, thanks to all of you for your work on reprepro.  I am
looking at a use case for which reprepro plus the profitbricks multiple
version support looks ideal.  However, as I want to set this up for
long-term success without a lot of fiddling, I'm wondering what the
prognosis is for getting this patch set integrated into reprepro
itself.  I don't see any comments in the bug log after either the 2017
or the 2018 patches, and am just wondering where things are?  Is there
something I could do to help move it along/

Thanks,

John

Reply | Threaded
Open this post in threaded view
|

Bug#570623: Submitted MR on Salsa

John Goerzen-3
In reply to this post by Jean-Christophe Dubacq
Hi folks,

In case it makes things easier, I submitted
https://salsa.debian.org/brlink/reprepro/merge_requests/1 which
represents Benjamin's 5.2.0 patchset, unmodified, with his original
commits from github.  I'm just resubmitting it there in case it makes it
easier to apply.

Thanks,

John

Reply | Threaded
Open this post in threaded view
|

Bug#570623: Submitted MR on Salsa

John Goerzen-3
One additional comment - it would probably be good to default Limit: 1
to mimic prior behavior, wouldn't it?

- John

Reply | Threaded
Open this post in threaded view
|

Bug#570623: Submitted MR on Salsa

Benjamin Drung-6
Hi John,

thanks for creating this pull request.

Am Dienstag, den 13.11.2018, 15:41 -0600 schrieb John Goerzen:
> One additional comment - it would probably be good to default
> Limit: 1 to mimic prior behavior, wouldn't it?

I changed the default to "Limit: 1", rebased the patch set on master,
and created a pull request for it:
https://salsa.debian.org/brlink/reprepro/merge_requests/2

--
Benjamin Drung
System Developer
Debian & Ubuntu Developer

1&1 IONOS Cloud GmbH | Greifswalder Str. 207 | 10405 Berlin | Germany
E-mail: [hidden email] | Web: www.ionos.de

Head Office: Berlin, Germany
District Court Berlin Charlottenburg, Registration number: HRB 125506 B
Executive Management: Christoph Steffens, Matthias Steinberg, Achim
Weiss

Member of United Internet

Reply | Threaded
Open this post in threaded view
|

Bug#570623: reprepro: please add multiple version management

Vincent Bernat-3
In reply to this post by Jean-Christophe Dubacq
Package: reprepro
Version: 5.3.0-1
Followup-For: Bug #570623

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

Hey!

What is the status of this feature? The merge request is not available
anymore and the GitHub repository of the fork is not up-to-date with
5.3.0.

- -- System Information:
Debian Release: buster/sid
  APT prefers unstable-debug
  APT policy: (500, 'unstable-debug'), (500, 'unstable'), (101, 'experimental-debug'), (101, 'experimental')
Architecture: amd64 (x86_64)

Kernel: Linux 4.19.0-4-amd64 (SMP w/4 CPU cores)
Kernel taint flags: TAINT_USER
Locale: LANG=fr_FR.utf8, LC_CTYPE=fr_FR.utf8 (charmap=UTF-8), LANGUAGE=en_US:en (charmap=UTF-8)
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages reprepro depends on:
ii  libarchive13   3.3.3-4
ii  libbz2-1.0     1.0.6-9
ii  libc6          2.28-8
ii  libdb5.3       5.3.28+dfsg1-0.6
ii  libgpg-error0  1.35-1
ii  libgpgme11     1.12.0-6
ii  liblzma5       5.2.4-1
ii  zlib1g         1:1.2.11.dfsg-1

Versions of packages reprepro recommends:
ii  apt  1.8.0

Versions of packages reprepro suggests:
ii  gnupg-agent              2.2.13-1
ii  gpg-agent [gnupg-agent]  2.2.13-1
pn  inoticoming              <none>
pn  lzip                     <none>
ii  pinentry-curses          1.1.0-1+b1

- -- no debconf information

-----BEGIN PGP SIGNATURE-----

iQJGBAEBCAAwFiEErvI0h2bzccaJpzYAlaQv6DU1JfkFAlygvLwSHGJlcm5hdEBk
ZWJpYW4ub3JnAAoJEJWkL+g1NSX5WUIP/3DY63Dao5HqvaXyiVG/Q1jLsn2YC7re
6miL77z5sDLHgtcbn8U2ObIdUvbnHvA7+4hvy6wl5lInxsHV0N5RlaeemiQ3LbYI
WVAYCgGbZNEy+80+sQ/1TorIn+Q/uTAeKMNrdnUT2hzuPTR7974mCdTBRI4a5ZXa
w1my8vBWMMHEgcX7hvcZ8gE/GujQF9HXL8SpA8n2yS4K1+9RoCUdWiPulbpYXc43
hSc0dgZ3mpIej7vJt5AtthtHhZssmMKDCW+43ciAO7ZlUMrG99Oji9q3GR1LTrkY
oIOSY6FVDm7pD7gbR+BRTfi1g1GP7uNCnWWVcntzgVzOZYJvbeEy6Wq3UY+MJhc0
DwX2aDYH8ehn/TyWWfNiKwUZcrOPDzK+Ki1iFQXJIYrnNqmdHVql9fsN8zh3ODPx
i418tDz9kXHs3LISJxA3f43I+53CpLL4OJQJKzu7VEfvz0F3RyQA27Sd761Xtjaq
twEsdYj9eXZbpmE41yIZl8cMK3vMGMFbDe7G7iOaAQPV/M7TL5LLa8S2fybGwNjS
St70JvMZUO7sQsh4nE9KW/nzeA2f+il5/jA6gGJ6fHEU6pIjklMCM2YcSdXkG4sk
NgNTkdL4pe+xbL+Wjjkc9fGhwpLvKFT+NROwrj7UHAfwY8xBR54x6tobRkhJPymH
/sllHO6/dL4l
=nCAm
-----END PGP SIGNATURE-----

Reply | Threaded
Open this post in threaded view
|

Bug#570623: reprepro: please add multiple version management

Benjamin Drung-6
Am Sonntag, den 31.03.2019, 15:12 +0200 schrieb Vincent Bernat:
> Package: reprepro
> Version: 5.3.0-1
> Followup-For: Bug #570623
>
> What is the status of this feature? The merge request is not
> available anymore

It seems that the support for pull requests were disabled.

>  and the GitHub repository of the fork is not up-to-date with
> 5.3.0.

I refreshed the patches on top of version 5.3.0 and pushed it to
https://salsa.debian.org/bdrung/reprepro/ and
https://github.com/profitbricks/reprepro

--
Benjamin Drung
System Developer
Debian & Ubuntu Developer

1&1 IONOS Cloud GmbH | Greifswalder Str. 207 | 10405 Berlin | Germany
E-mail: [hidden email] | Web: www.ionos.de

Head Office: Berlin, Germany
District Court Berlin Charlottenburg, Registration number: HRB 125506 B
Executive Management: Christoph Steffens, Matthias Steinberg, Achim
Weiss

Member of United Internet

Reply | Threaded
Open this post in threaded view
|

Bug#570623: reprepro: please add multiple version management

Michael Prokop-5
Hi,

* Benjamin Drung [Wed Apr 03, 2019 at 12:11:55PM +0200]:

> I refreshed the patches on top of version 5.3.0 and pushed it to
> https://salsa.debian.org/bdrung/reprepro/ and
> https://github.com/profitbricks/reprepro

Thanks for your efforts, Benjamin, highly appreciated.

Bernhard, is there any specific reason why you didn't respond here
any longer? Is there anything which would help to increase chances
to get this feature merged in the near future?

regards
-mika-

signature.asc (853 bytes) Download Attachment