On Mon, Jul 30, 2018 at 11:36:55AM -0600, Ken Dreyer wrote: > On Fri, Jul 27, 2018 at 1:28 AM, Fabian Grünbichler > <f.gruenbichler@xxxxxxxxxxx> wrote: > > On Tue, Jul 24, 2018 at 10:38:43AM -0400, Alfredo Deza wrote: > >> Hi all, > >> > >> After the 12.2.6 release went out, we've been thinking on better ways > >> to remove a version from our repositories to prevent users from > >> upgrading/installing a known bad release. > >> > >> The way our repos are structured today means every single version of > >> the release is included in the repository. That is, for Luminous, > >> every 12.x.x version of the binaries is in the same repo. This is true > >> for both RPM and DEB repositories. > >> > >> However, the DEB repos don't allow pinning to a given version because > >> our tooling (namely reprepro) doesn't construct the repositories in a > >> way that this is allowed. For RPM repos this is fine, and version > >> pinning works. > > > > If you mean that reprepo does not support referencing multiple versions > > of packages in the Packages file, there is a patched fork that does > > (that seems well-supported): > > > > https://github.com/profitbricks/reprepro > > Thanks for this link. That's great to know someone's working on this. > > What's the status of merging that back into the main reprepro code, or > else shipping that fork as the new reprepro package in Debian / > Ubuntu? The Ceph project could end up responsible for maintaining that > reprepro fork if the main Ubuntu community does not pick it up :) The > fork is several years old, and the latest update on > https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=570623 was over a > year ago. I don't know anything more than what is publicly available about either merging back to the original reprepo or shipping in Debian/Ubuntu. We are using our own custom repo software built around lower level tools, I was just aware of the fork for unrelated reasons :) -- To unsubscribe from this list: send the line "unsubscribe ceph-devel" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
