https://pulp.plan.io/https://pulp.plan.io/favicon.ico2018-07-10T16:50:08ZPulpRPM Support - Story #3847: Introduce weak dependency solvinghttps://pulp.plan.io/issues/3847?journal_id=294052018-07-10T16:50:08Zmilan
<ul><li><strong>Description</strong> updated (<a title="View differences" href="/journals/29405/diff?detail_id=30069">diff</a>)</li></ul> RPM Support - Story #3847: Introduce weak dependency solvinghttps://pulp.plan.io/issues/3847?journal_id=294292018-07-11T15:48:28Zmilan
<ul><li><strong>Description</strong> updated (<a title="View differences" href="/journals/29429/diff?detail_id=30089">diff</a>)</li></ul> RPM Support - Story #3847: Introduce weak dependency solvinghttps://pulp.plan.io/issues/3847?journal_id=294312018-07-11T16:02:21Zmilan
<ul><li><strong>Description</strong> updated (<a title="View differences" href="/journals/29431/diff?detail_id=30090">diff</a>)</li></ul> RPM Support - Story #3847: Introduce weak dependency solvinghttps://pulp.plan.io/issues/3847?journal_id=294522018-07-12T09:44:32Zipanova@redhat.comipanova@redhat.com
<ul><li><strong>Platform Release</strong> deleted (<del><i>2.17.0</i></del>)</li></ul> RPM Support - Story #3847: Introduce weak dependency solvinghttps://pulp.plan.io/issues/3847?journal_id=294532018-07-12T10:02:50Zmilan
<ul><li><strong>Related to</strong> <i><a class="issue tracker-3 status-11 priority-6 priority-default closed" href="/issues/3715">Story #3715</a>: Reimplement unit dependency solving with the libsolv library</i> added</li></ul> RPM Support - Story #3847: Introduce weak dependency solvinghttps://pulp.plan.io/issues/3847?journal_id=294552018-07-12T10:05:13Zipanova@redhat.comipanova@redhat.com
<ul></ul><p>since there is a change in the model, shall we require a migration?</p> RPM Support - Story #3847: Introduce weak dependency solvinghttps://pulp.plan.io/issues/3847?journal_id=294562018-07-12T11:48:10Zmilan
<ul></ul><p>Thanks for the check; to my best knowledge a migration is unnecessary, with the following reasoning:</p>
<ul>
<li>by definition, nothing should break if (during an installation) a unit <code>Recommends</code> dependency is missing from a repository</li>
<li>Pulp has been ignoring the <code>Recommends</code> dependency so far</li>
<li>therefore implementing this story without a migration won't make things worse</li>
</ul>
<p>The migration itself would have to process all the RPM unit XML records to be able to populate the <code>Recommends</code> attribute which might have adverse performance effects. The unit <code>Recommends</code> attribute will be populated for newly-uploaded or newly-synchronized units.</p>
<p>However, let's document this.</p> RPM Support - Story #3847: Introduce weak dependency solvinghttps://pulp.plan.io/issues/3847?journal_id=294572018-07-12T12:17:00Zmilan
<ul><li><strong>Description</strong> updated (<a title="View differences" href="/journals/29457/diff?detail_id=30111">diff</a>)</li></ul> RPM Support - Story #3847: Introduce weak dependency solvinghttps://pulp.plan.io/issues/3847?journal_id=294602018-07-12T13:38:30Zdkliban@redhat.com
<ul></ul><p>Without a migration the user will get into a situation where the RPMs that were synced before 2.17.0 will not have the 'recommends' field set. The RPMs that are synced after 2.17.0 release will have 'recommends' set. When the user goes to copy RPMs recursively he will notice that some RPMs bring their weak deps with them and some RPMs don't bring their weak deps with them.</p> RPM Support - Story #3847: Introduce weak dependency solvinghttps://pulp.plan.io/issues/3847?journal_id=294622018-07-12T13:47:00Zmilan
<ul></ul><p><a href="mailto:dkliban@redhat.com" class="email">dkliban@redhat.com</a> wrote:</p>
<blockquote>
<p>Without a migration the user will get into a situation where the RPMs that were synced before 2.17.0 will not have the 'recommends' field set. The RPMs that are synced after 2.17.0 release will have 'recommends' set. When the user goes to copy RPMs recursively he will notice that some RPMs bring their weak deps with them and some RPMs don't bring their weak deps with them.</p>
</blockquote>
<p>I agree but please mind this isn't a breaking discrepancy; we should be OK to just document (and test) this behaviour.</p> RPM Support - Story #3847: Introduce weak dependency solvinghttps://pulp.plan.io/issues/3847?journal_id=294802018-07-13T09:15:01Zmilan
<ul><li><strong>Description</strong> updated (<a title="View differences" href="/journals/29480/diff?detail_id=30126">diff</a>)</li></ul> RPM Support - Story #3847: Introduce weak dependency solvinghttps://pulp.plan.io/issues/3847?journal_id=294812018-07-13T09:29:39Zmilan
<ul><li><strong>Description</strong> updated (<a title="View differences" href="/journals/29481/diff?detail_id=30127">diff</a>)</li></ul> RPM Support - Story #3847: Introduce weak dependency solvinghttps://pulp.plan.io/issues/3847?journal_id=294822018-07-13T10:53:09Zmilan
<ul><li><strong>Description</strong> updated (<a title="View differences" href="/journals/29482/diff?detail_id=30128">diff</a>)</li></ul> RPM Support - Story #3847: Introduce weak dependency solvinghttps://pulp.plan.io/issues/3847?journal_id=294832018-07-13T11:37:38Zipanova@redhat.comipanova@redhat.com
<ul></ul><p>thanks @dkliban, this is exact reason why i asked for a migration :)<br>
As Milan pointed out, in the migration we'd need to get from the DB for each rpm unit the xml snippet, uncompress it, parse it.<br>
On the other hand if we won't write the migration then those units before the upgrade will forever miss the the newly added field unless the unit will be removed and added back to the DB. Nothing would break without the migration, dnf will still be happy, just the behaviour during recursive copy will be inconsistent - for some units weak deps will will be copied over and for some not.</p>
<p>I think i am still in favour of writing the migration even if it is a costful one, let's minimize the inconsistent behaviour as much as we can.</p> RPM Support - Story #3847: Introduce weak dependency solvinghttps://pulp.plan.io/issues/3847?journal_id=294842018-07-13T11:38:16Zipanova@redhat.comipanova@redhat.com
<ul></ul><p>i think this story is ready to be groomed once we +1 or -1 on the migration.</p> RPM Support - Story #3847: Introduce weak dependency solvinghttps://pulp.plan.io/issues/3847?journal_id=294852018-07-13T12:11:46Zdkliban@redhat.com
<ul><li><strong>Groomed</strong> changed from <i>No</i> to <i>Yes</i></li><li><strong>Sprint Candidate</strong> changed from <i>No</i> to <i>Yes</i></li></ul> RPM Support - Story #3847: Introduce weak dependency solvinghttps://pulp.plan.io/issues/3847?journal_id=294862018-07-13T12:21:53Zmilan
<ul><li><strong>File</strong> <a href="/attachments/272365">test.log</a> <a class="icon-only icon-download" title="Download" href="/attachments/download/272365/test.log">test.log</a> added</li><li><strong>Groomed</strong> changed from <i>Yes</i> to <i>No</i></li><li><strong>Sprint Candidate</strong> changed from <i>Yes</i> to <i>No</i></li></ul><p>To give a concrete example:<br>
Assuming we've got 2 repos; <code>f27, f28</code> with content of Fedora27, Fedora28 respectively.<br>
Given the fact RPM unit <code>nevra</code> is used as unit identity key and given the fact during a sync call (eve the <code>--force-full</code> one) the unit records aren't updated in Mongo, the discrepancy would occur either after having deleting a repo and cleaning orphans or if a newer unit version (as in <code>nevra</code>) was pulled in. In these cases, one <code>dnf</code> unit version would have <code>recommends</code> attribute populated, the other wouldn't:</p>
<pre><code>> db.units_rpm.find({'name': 'dnf'})[0].recommends
[
{
"release" : null,
"epoch" : null,
"version" : null,
"flags" : null,
"name" : "python3-dbus"
}
]
> db.units_rpm.find({'name': 'dnf'})[0].release
1.fc27
> db.units_rpm.find({'name': 'dnf'})[1].recommends
> db.units_rpm.find({'name': 'dnf'})[1].release
12.fc28
>
</code></pre>
<p>See also my <code>test.log</code> attachment.</p> RPM Support - Story #3847: Introduce weak dependency solvinghttps://pulp.plan.io/issues/3847?journal_id=294872018-07-13T12:22:36Zmilan
<ul><li><strong>Groomed</strong> changed from <i>No</i> to <i>Yes</i></li><li><strong>Sprint Candidate</strong> changed from <i>No</i> to <i>Yes</i></li></ul> RPM Support - Story #3847: Introduce weak dependency solvinghttps://pulp.plan.io/issues/3847?journal_id=294952018-07-13T16:00:49Zmilan
<ul><li><strong>Assignee</strong> set to <i>milan</i></li></ul> RPM Support - Story #3847: Introduce weak dependency solvinghttps://pulp.plan.io/issues/3847?journal_id=294962018-07-13T16:35:09Zmilan
<ul><li><strong>Status</strong> changed from <i>NEW</i> to <i>POST</i></li></ul><p>A (WIP) PR: <a href="https://github.com/pulp/pulp_rpm/pull/1135" class="external">https://github.com/pulp/pulp_rpm/pull/1135</a></p> RPM Support - Story #3847: Introduce weak dependency solvinghttps://pulp.plan.io/issues/3847?journal_id=295332018-07-15T23:12:11Zdkliban@redhat.com
<ul><li><strong>Sprint</strong> set to <i>Sprint 40</i></li></ul> RPM Support - Story #3847: Introduce weak dependency solvinghttps://pulp.plan.io/issues/3847?journal_id=295392018-07-16T08:09:45Zmilan
<ul><li><strong>Description</strong> updated (<a title="View differences" href="/journals/29539/diff?detail_id=30186">diff</a>)</li></ul><p>Speaking about inconsistency, there might be other point of view on the migration: after it, out of the blue, users recursively copying e.g <code>dnf-2.7.3-1.fc27.noarch.rpm</code> will start pulling in <code>sqlite-3</code> as a recommendation. This change of behavior will happen <em>without</em> any update to the <code>dnf</code> package itself. This might be surprising to the user because they might not anticipate a change of dependencies of a package without the accompanying bump of the package <code>evr</code>. As a consequence, recursive copies of <code>dnf-2.7.3-1.fc27.noarch.rpm</code> before and after the migration would differ in content.</p> RPM Support - Story #3847: Introduce weak dependency solvinghttps://pulp.plan.io/issues/3847?journal_id=295642018-07-17T13:54:55Zttereshcttereshc@redhat.com
<ul></ul><p>+1 to ipanova and dkliban point to have a migration for consistency reasons.<br>
The fact that Pulp won't error without migration is not good enough reason not to do it, imho.</p> RPM Support - Story #3847: Introduce weak dependency solvinghttps://pulp.plan.io/issues/3847?journal_id=295652018-07-17T13:59:40Zmilan
<ul></ul><p>It's not about Pulp erroring out I'm afraid, it's about repositories having different content if they're created thru a recursive copy before and after the migration, no matter the content version being the same. This I find a bigger discrepancy than if all the non-updated rpm versions missed the <code>recommends</code> field (or just had the default empty list fwiw) because it's consistent with client behavior.</p> RPM Support - Story #3847: Introduce weak dependency solvinghttps://pulp.plan.io/issues/3847?journal_id=295692018-07-17T14:42:36Zttereshcttereshc@redhat.com
<ul></ul><p><del>I'm not sure I follow "the content version being the same" part.</del></p>
<p><del>If users upgrade to Pulp 2.x with weak deps support, they know that now weak deps are taken into account.<br>
If they perform recursive copy, and the result will be different from the older version of Pulp that's fine because now weak deps are respected.<br>
Published repository will have new revision number so clients will know that content was updated and is different now.<br>
Let me know if I misunderstood you.</del></p>
<p>Ah before or after the migration. Migrations are an essential part of installation so we should not cover the case when they were not run</p> RPM Support - Story #3847: Introduce weak dependency solvinghttps://pulp.plan.io/issues/3847?journal_id=298662018-08-06T12:59:56Zmilan
<ul></ul><p>PR change: <a href="https://github.com/pulp/pulp_rpm/pull/1151" class="external">https://github.com/pulp/pulp_rpm/pull/1151</a></p> RPM Support - Story #3847: Introduce weak dependency solvinghttps://pulp.plan.io/issues/3847?journal_id=298932018-08-06T13:17:37Zrchan
<ul><li><strong>Sprint</strong> changed from <i>Sprint 40</i> to <i>Sprint 41</i></li></ul> RPM Support - Story #3847: Introduce weak dependency solvinghttps://pulp.plan.io/issues/3847?journal_id=299022018-08-06T16:37:31Zmilan
<ul><li><strong>Status</strong> changed from <i>POST</i> to <i>MODIFIED</i></li><li><strong>% Done</strong> changed from <i>0</i> to <i>100</i></li></ul><p>Applied in changeset <a class="changeset" title="Introduce the Recommends dependency Pulp has been ignoring the Recommends weak dependency when p..." href="https://pulp.plan.io/projects/pulp_rpm/repository/9/revisions/6d6c8292d2abba37142ff4f2af73c3fe6c3cb90d">6d6c8292d2abba37142ff4f2af73c3fe6c3cb90d</a>.</p> RPM Support - Story #3847: Introduce weak dependency solvinghttps://pulp.plan.io/issues/3847?journal_id=299172018-08-06T22:33:47Zrchan
<ul><li><strong>Sprint/Milestone</strong> set to <i>2.17.0</i></li></ul> RPM Support - Story #3847: Introduce weak dependency solvinghttps://pulp.plan.io/issues/3847?journal_id=299482018-08-07T16:21:31Zipanova@redhat.comipanova@redhat.com
<ul><li><strong>Platform Release</strong> set to <i>2.17.0</i></li></ul> RPM Support - Story #3847: Introduce weak dependency solvinghttps://pulp.plan.io/issues/3847?journal_id=299752018-08-07T16:31:31Zipanova@redhat.comipanova@redhat.com
<ul><li><strong>Platform Release</strong> changed from <i>2.17.0</i> to <i>master</i></li></ul> RPM Support - Story #3847: Introduce weak dependency solvinghttps://pulp.plan.io/issues/3847?journal_id=300002018-08-07T16:32:10Zipanova@redhat.comipanova@redhat.com
<ul><li><strong>Platform Release</strong> deleted (<del><i>master</i></del>)</li></ul> RPM Support - Story #3847: Introduce weak dependency solvinghttps://pulp.plan.io/issues/3847?journal_id=300252018-08-07T16:36:58Zipanova@redhat.comipanova@redhat.com
<ul><li><strong>Platform Release</strong> set to <i>2.17.0</i></li></ul> RPM Support - Story #3847: Introduce weak dependency solvinghttps://pulp.plan.io/issues/3847?journal_id=301562018-08-14T21:17:32Zipanova@redhat.comipanova@redhat.com
<ul><li><strong>Status</strong> changed from <i>MODIFIED</i> to <i>5</i></li></ul> RPM Support - Story #3847: Introduce weak dependency solvinghttps://pulp.plan.io/issues/3847?journal_id=302332018-08-21T15:21:06Zkersom
<ul></ul><p>This new feature was manually verified.</p>
<p>Pulp copies strong and weak dependencies when using --recursive during a copy.</p> RPM Support - Story #3847: Introduce weak dependency solvinghttps://pulp.plan.io/issues/3847?journal_id=302392018-08-21T19:16:48Zmilan
<ul></ul><p>weak rich(boolean) deps are hosed:</p>
<pre><code>(pulp) [vagrant@pulp2 importers]$ pulp-admin rpm repo copy rpm -f f28 -t foo --recursive --str-eq 'name=bash-completion'
This command may be exited via ctrl+c without affecting the request.
[/]
Running...
Copied:
basesystem-11-5.fc28-noarch
bash-4.4.19-2.fc28-x86_64
bash-completion-2.7-4.fc28-noarch
fedora-gpg-keys-28-1-noarch
fedora-release-28-1-noarch
fedora-repos-28-1-noarch
filesystem-3.8-2.fc28-x86_64
glibc-2.27-8.fc28-x86_64
glibc-all-langpacks-2.27-8.fc28-x86_64
glibc-common-2.27-8.fc28-x86_64
libpkgconf-1.4.2-1.fc28-x86_64
libselinux-2.7-13.fc28-x86_64
libsepol-2.7-6.fc28-x86_64
ncurses-base-6.1-4.20180224.fc28-noarch
ncurses-libs-6.1-4.20180224.fc28-x86_64
pcre2-10.31-4.fc28-x86_64
pkgconf-1.4.2-1.fc28-x86_64
pkgconf-m4-1.4.2-1.fc28-noarch
pkgconf-pkg-config-1.4.2-1.fc28-x86_64
setup-2.11.3-1.fc28-noarch
tzdata-2018d-1.fc28-noarch
(pulp) [vagrant@pulp2 importers]$ pulp-admin rpm repo copy rpm -f f28 -t foo --recursive --str-eq 'name=dnf'
This command may be exited via ctrl+c without affecting the request.
[-]
Running...
Copied:
rpm: 145
(pulp) [vagrant@pulp2 importers]$ pulp-admin rpm repo content rpm --repo-id f28 --str-eq 'name=sqlite'
Arch: x86_64
Buildhost: buildvm-25.phx2.fedoraproject.org
Checksum: 24ee748b29e4837c41df5b9472654f5aa66858f62cde706723d4f480b3f56fb6
Checksumtype: sha256
Description: SQLite is a C library that implements an SQL database engine. A
large subset of SQL92 is supported. A complete database is stored
in a single disk file. The API is designed for convenience and
ease of use. Applications that link against SQLite can enjoy the
power and flexibility of an SQL database without the
administrative hassles of supporting a separate database server.
Version 2 and version 3 binaries are named to permit each to be
installed on a single host
Epoch: 0
Filename: sqlite-3.22.0-4.fc28.x86_64.rpm
License: Public Domain
Name: sqlite
Provides: sqlite = 3.22.0-4.fc28-0, sqlite(x86-64) = 3.22.0-4.fc28-0
Release: 4.fc28
Requires: libdl.so.2()(64bit), libdl.so.2(GLIBC_2.2.5)(64bit),
libm.so.6()(64bit), libm.so.6(GLIBC_2.2.5)(64bit),
libncurses.so.6()(64bit), libpthread.so.0()(64bit),
libpthread.so.0(GLIBC_2.2.5)(64bit), libreadline.so.7()(64bit),
libtinfo.so.6()(64bit), libz.so.1()(64bit),
libz.so.1(ZLIB_1.2.0)(64bit), rtld(GNU_HASH), sqlite-libs =
3.22.0-4.fc28-0, libc.so.6(GLIBC_2.14)(64bit)
Vendor: Fedora Project
Version: 3.22.0
(pulp) [vagrant@pulp2 importers]$ pulp-admin rpm repo content rpm --repo-id foo --str-eq 'name=sqlite'
# nothing found
(pulp) [vagrant@pulp2 yum]$ mongo pulp_database --eval 'db.units_rpm.find({"recommends": {$elemMatch: {"name": /^\(/}}})[0].name'
MongoDB shell version v3.4.11
connecting to: mongodb://127.0.0.1:27017/pulp_database
MongoDB server version: 3.4.11
dnf
(pulp) [vagrant@pulp2 yum]$ mongo pulp_database --eval 'db.units_rpm.find({"recommends": {$elemMatch: {"name": /^\(/}}})[0].recommends[0]'
MongoDB shell version v3.4.11
connecting to: mongodb://127.0.0.1:27017/pulp_database
MongoDB server version: 3.4.11
{
"release" : null,
"epoch" : null,
"version" : null,
"flags" : null,
"name" : "(/usr/bin/sqlite3 if bash-completion)"
}
(pulp) [vagrant@pulp2 yum]$
</code></pre>
<p>This works as expected with dnf (on a F28 Workstation VM):</p>
<pre><code>[root@localhost ~]# rpm -q sqlite
sqlite-3.22.0-4.fc28.x86_64
[root@localhost ~]# rpm -e sqlite
error: Failed dependencies:
sqlite >= 3.22.0 is needed by (installed) firefox-59.0.2-1.fc28.x86_64
[root@localhost ~]# rpm -e firefox
# --->%--------------------------------------
warning: file /usr/lib64/firefox/langpacks: remove failed: No such file or directory
[root@localhost ~]# rpm -e sqlite
[root@localhost ~]# rpm -q bash-completion
bash-completion-2.7-4.fc28.noarch
[root@localhost ~]# rpm -q sqlite
package sqlite is not installed
[root@localhost ~]# dnf reinstall dnf
Last metadata expiration check: 0:28:47 ago on Tue 21 Aug 2018 08:43:20 PM CEST.
Dependencies resolved.
==================================================================================================================================================================================
Package Arch Version Repository Size
==================================================================================================================================================================================
Reinstalling:
dnf noarch 2.7.5-12.fc28 fedora 352 k
Installing weak dependencies:
sqlite x86_64 3.22.0-4.fc28 fedora 623 k
Transaction Summary
==================================================================================================================================================================================
Install 1 Package
Total download size: 975 k
Is this ok [y/N]: y
Downloading Packages:
(1/2): dnf-2.7.5-12.fc28.noarch.rpm 8.2 MB/s | 352 kB 00:00
(2/2): sqlite-3.22.0-4.fc28.x86_64.rpm 13 MB/s | 623 kB 00:00
----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Total 1.3 MB/s | 975 kB 00:00
Running transaction check
Transaction check succeeded.
Running transaction test
Transaction test succeeded.
Running transaction
Preparing : 1/1
Running scriptlet: sqlite-3.22.0-4.fc28.x86_64 1/1
Installing : sqlite-3.22.0-4.fc28.x86_64 1/3
Reinstalling : dnf-2.7.5-12.fc28.noarch 2/3
Running scriptlet: dnf-2.7.5-12.fc28.noarch 2/3
Running scriptlet: dnf-2.7.5-12.fc28.noarch 3/3
Erasing : dnf-2.7.5-12.fc28.noarch 3/3
Running scriptlet: dnf-2.7.5-12.fc28.noarch 3/3
Verifying : dnf-2.7.5-12.fc28.noarch 1/3
Verifying : sqlite-3.22.0-4.fc28.x86_64 2/3
Verifying : dnf-2.7.5-12.fc28.noarch 3/3
Reinstalled:
dnf.noarch 2.7.5-12.fc28
Installed:
sqlite.x86_64 3.22.0-4.fc28
Complete!
[root@localhost ~]# rpm -q sqlite
sqlite-3.22.0-4.fc28.x86_64
[root@localhost ~]#
</code></pre> RPM Support - Story #3847: Introduce weak dependency solvinghttps://pulp.plan.io/issues/3847?journal_id=302492018-08-23T17:04:40Zkersom
<ul></ul><p>It was manual tested.</p>
<p>Following commands.</p>
<pre><code class="text syntaxhl" data-language="text">pulp-admin rpm repo create --repo-id foo --feed https://repos.fedorapeople.org/pulp/pulp/fixtures/rpm-richnweak-deps/
pulp-admin rpm repo create --repo-id bar
pulp-admin rpm repo sync run --repo-id foo
[root@f28c ~]# pulp-admin rpm repo copy rpm -f foo -t bar --recursive --str-eq 'name=Cobbler'
This command may be exited via ctrl+c without affecting the request.
[\]
Running...
Copied:
Cobbler-1-0-noarch
contireau-2-10-noarch
icecubes-2-3-noarch
orange-bits-2-3-noarch
tablespoon-sugar-1-0-noarch
</code></pre>
<p>Comparing same dependency resolution using DNF.</p>
<pre><code class="text syntaxhl" data-language="text">cat >/etc/yum.repos.d/weak.repo <<EOL
[weak_repo_modi]
baseurl=https://repos.fedorapeople.org/pulp/pulp/fixtures/rpm-richnweak-deps/
gpgcheck=0
name=test_repo
EOL
</code></pre>
<pre><code class="text syntaxhl" data-language="text"> kersom / etc yum.repos.d sudo dnf install Cobbler
test_repo 19 kB/s | 3.9 kB 00:00
Last metadata expiration check: 0:00:00 ago on Thu 23 Aug 2018 12:59:56 PM EDT.
Dependencies resolved.
===================================================================================================================================================================================================================
Package Arch Version Repository Size
===================================================================================================================================================================================================================
Installing:
Cobbler noarch 1-0 weak_repo_modi 6.2 k
Installing dependencies:
contireau noarch 2-10 weak_repo_modi 5.8 k
icecubes noarch 2-3 weak_repo_modi 5.7 k
tablespoon-sugar noarch 1-0 weak_repo_modi 5.7 k
Installing weak dependencies:
orange-bits noarch 2-3 weak_repo_modi 5.9 k
Transaction Summary
===================================================================================================================================================================================================================
Install 5 Packages
Total download size: 29 k
Installed size: 0
Is this ok [y/N]:
</code></pre> RPM Support - Story #3847: Introduce weak dependency solvinghttps://pulp.plan.io/issues/3847?journal_id=304862018-08-31T20:48:21Zipanova@redhat.comipanova@redhat.com
<ul><li><strong>Status</strong> changed from <i>5</i> to <i>CLOSED - CURRENTRELEASE</i></li></ul> RPM Support - Story #3847: Introduce weak dependency solvinghttps://pulp.plan.io/issues/3847?journal_id=378232019-04-15T20:10:07Zbmbouterbmbouter@redhat.com
<ul><li><strong>Tags</strong> <i>Pulp 2</i> added</li></ul> RPM Support - Story #3847: Introduce weak dependency solvinghttps://pulp.plan.io/issues/3847?journal_id=783102022-01-11T17:18:15Zttereshcttereshc@redhat.com
<ul><li><strong>Sprint/Milestone</strong> deleted (<del><i>2.17.0</i></del>)</li></ul>