Source: glusterfs Version: 9.0-1 Tags: patch User: [email protected] Usertags: rebootstrap
glusterfs participates in a number of dependency loops relevant to architecture bootstrap. Instead of looking into such a difficult problem, I looked for easily droppable dependencies. It turns out that a nocheck build of glusterfs with the following Build-Depends turned into Build-Conflicts exactly reproduces the binary artifacts of a regular build. Thus it seems safe to annotate these dependencies with <!nocheck>. Please consider applying the attached patch. Helmut
diff --minimal -Nru glusterfs-9.0/debian/changelog glusterfs-9.0/debian/changelog --- glusterfs-9.0/debian/changelog 2021-01-19 10:42:08.000000000 +0100 +++ glusterfs-9.0/debian/changelog 2021-01-20 10:49:15.000000000 +0100 @@ -1,3 +1,12 @@ +glusterfs (9.0-1.1) UNRELEASED; urgency=medium + + * Non-maintainer upload. + * Annotate Build-Depends libfuse-dev, libivbers-dev, libdb-dev, + librdmacm-dev, libsqlite3-dev, attr, and libglib2.0-dev with <!nocheck>: + (Closes: #-1) + + -- Helmut Grohne <[email protected]> Wed, 20 Jan 2021 10:49:15 +0100 + glusterfs (9.0-1) unstable; urgency=medium * New upstream release. diff --minimal -Nru glusterfs-9.0/debian/control glusterfs-9.0/debian/control --- glusterfs-9.0/debian/control 2021-01-19 10:42:08.000000000 +0100 +++ glusterfs-9.0/debian/control 2021-01-20 10:47:54.000000000 +0100 @@ -3,23 +3,23 @@ Priority: optional Maintainer: Patrick Matthäi <[email protected]> Build-Depends: debhelper-compat (= 13), - libfuse-dev, - libibverbs-dev, - libdb-dev, - librdmacm-dev, + libfuse-dev <!nocheck>, + libibverbs-dev <!nocheck>, + libdb-dev <!nocheck>, + librdmacm-dev <!nocheck>, libaio-dev, libacl1-dev, - libsqlite3-dev, + libsqlite3-dev <!nocheck>, libtirpc-dev (>= 1.1.4), liburcu-dev, uuid-dev, - attr, + attr <!nocheck>, flex, bison, firewalld, libreadline-dev, libncurses5-dev, - libglib2.0-dev, + libglib2.0-dev <!nocheck>, libssl-dev, libxml2-dev, pkg-config,
