Pulp: Issueshttps://pulp.plan.io/https://pulp.plan.io/favicon.ico2021-12-12T06:09:47ZPulp
Planio RPM Support - Task #9633 (CLOSED - DUPLICATE): Use repo priorities in the dependency solverhttps://pulp.plan.io/issues/96332021-12-12T06:09:47Zdalleydalley@redhat.com
<p><strong>Ticket moved to GitHub</strong>: "pulp/pulp_rpm/2309":<a href="https://github.com/pulp/pulp_rpm/issues/2309" class="external">https://github.com/pulp/pulp_rpm/issues/2309</a></p>
<hr>
<p>We ought to be setting repo priorities such that for every set of copies, any matching RPMs present in the same repository are prioritzed over ones in other repos.</p> RPM Support - Test #9626 (CLOSED - DUPLICATE): Add tests for SHA repo to test_synchttps://pulp.plan.io/issues/96262021-12-08T21:43:04Zggainey
<p><strong>Ticket moved to GitHub</strong>: "pulp/pulp_rpm/2320":<a href="https://github.com/pulp/pulp_rpm/issues/2320" class="external">https://github.com/pulp/pulp_rpm/issues/2320</a></p>
<hr>
<p>We have been bitten a few times now by repos that use 'sha' (instead of 'sha1') checksums. Build a test for same that does <strong>not</strong> require sync'ing all of RHEL6.6...</p> RPM Support - Test #9622 (MODIFIED): Add a repo signed using 'sha' as alias for 'sha1'https://pulp.plan.io/issues/96222021-12-08T19:00:00Zggainey
<p>'sha' support exists in the wild, is the same as 'sha1', and has broken us several times now, Let's make it possible to write tests for it.</p> RPM Support - Task #9585 (CLOSED - DUPLICATE): Sub-tree-only sync breaks our model of how syncs a...https://pulp.plan.io/issues/95852021-11-23T21:00:08Zdalleydalley@redhat.com
<p><strong>Ticket moved to GitHub</strong>: "pulp/pulp_rpm/2306":<a href="https://github.com/pulp/pulp_rpm/issues/2306" class="external">https://github.com/pulp/pulp_rpm/issues/2306</a></p>
<hr>
<p>See: <a href="https://pulp.plan.io/issues/9565" class="external">https://pulp.plan.io/issues/9565</a></p>
<p>We haven't considered the possibility of a repository having a .treeinfo but no top-level repodata. We need to investigate whether this breaks anything (for example: autopublish), and potentially add a new test fixture to exercise it.</p> RPM Support - Story #9484 (CLOSED - DUPLICATE): delete rpm content via api or command linehttps://pulp.plan.io/issues/94842021-10-04T10:31:36ZTiagodCC
<p><strong>Ticket moved to GitHub</strong>: "pulp/pulp_rpm/2303":<a href="https://github.com/pulp/pulp_rpm/issues/2303" class="external">https://github.com/pulp/pulp_rpm/issues/2303</a></p>
<hr>
<p>I use specific custom repositories that aren't synced to publish packages from third party software vendors.</p>
<p>Because of this, I wanted to ask how I can delete existing RPM packages (content).
When I try to remove the Artifact, I get the following error:
"The Artifact cannot be deleted because it is associated with Content."
However, I cannot remove the package:
"Method "DELETE" not allowed."</p>
<p>I unfortunately didn't find anything in the documentation about this.</p>
<p>Thanks in advance for the answer.</p>
<p>Translated with <a href="http://www.DeepL.com/Translator" class="external">www.DeepL.com/Translator</a> (free version)</p> RPM Support - Refactor #9467 (CLOSED - CURRENTRELEASE): django.conf.urls.url() is deprecated, swi...https://pulp.plan.io/issues/94672021-09-29T10:58:51Zipanova@redhat.comipanova@redhat.com
<p>This is referring to the urlpatterns= [ .... ] in urls.py.</p>
<p>The "old way" is not scheduled to be removed any time soon, but the new way is nicer in many respects.</p>
<p><a href="https://docs.djangoproject.com/en/3.2/ref/urls/#path" class="external">https://docs.djangoproject.com/en/3.2/ref/urls/#path</a>
<a href="https://docs.djangoproject.com/en/3.2/ref/urls/#url" class="external">https://docs.djangoproject.com/en/3.2/ref/urls/#url</a></p> RPM Support - Refactor #9461 (CLOSED - DUPLICATE): Revert the workaround for Pulp 2 syncing from ...https://pulp.plan.io/issues/94612021-09-28T16:43:06Zdalleydalley@redhat.com
<p><strong>Ticket moved to GitHub</strong>: "pulp/pulp_rpm/2302":<a href="https://github.com/pulp/pulp_rpm/issues/2302" class="external">https://github.com/pulp/pulp_rpm/issues/2302</a></p>
<hr>
<p><a href="https://github.com/pulp/pulp_rpm/commit/15d9933b64a59b9d4a585f1bee6b08405f36fc79" class="external">https://github.com/pulp/pulp_rpm/commit/15d9933b64a59b9d4a585f1bee6b08405f36fc79</a></p>
<p>This was merged in order to workaround Pulp 2's inability to handle repositories where the package checksum type differed from the metadata checksum type. But there is nothing wrong with such repos, and we don't want to carry this behavior long-term.</p>
<p>Once we are no longer concerned with being able to sync Pulp 2 from repos produced by Pulp 3, we should revert the workaround.</p> RPM Support - Task #9435 (MODIFIED): Update ACS docs to use the CLIhttps://pulp.plan.io/issues/94352021-09-23T13:22:02Zppicka
<p>ssia</p> RPM Support - Task #9422 (CLOSED - COMPLETE): Create a fixture repo that has only metadatahttps://pulp.plan.io/issues/94222021-09-17T16:19:34Zipanova@redhat.comipanova@redhat.com
<p>ssia</p> RPM Support - Story #9358 (MODIFIED): As a user I can use Alternate Content Sourceshttps://pulp.plan.io/issues/93582021-09-08T16:40:29Zppicka
<p>Add refresh endpoint with slightly adjust synchronize method and first stage to support ACS.</p> RPM Support - Story #9319 (CLOSED - DUPLICATE): As a plugin writer I have a way to suppress warni...https://pulp.plan.io/issues/93192021-08-31T04:42:30Zdalleydalley@redhat.comRPM Support - Story #9316 (CLOSED - CURRENTRELEASE): As a user, I can mirror the packages in a re...https://pulp.plan.io/issues/93162021-08-31T03:35:59Zdalleydalley@redhat.com
<p>This used to be how things worked, then we changed how mirroring worked. But there are rare cases when metadata mirroring is not possible (see related issue) so we should add back a way to do this.</p>
<p>edit: I have two ideas. They are not mutually exclusive, we could implement the first and then later move in the direction of the second without much trouble.</p>
<a name="Idea-1"></a>
<h1 >Idea <a class="issue tracker-3 status-11 priority-6 priority-default closed child" title="Story: As a user, I can have Pulp attempt use auto_retry application wide using the 'unsafe_autoretry' p... (CLOSED - CURRENTRELEASE)" href="https://pulp.plan.io/issues/1">#1</a><a href="#Idea-1" class="wiki-anchor">¶</a></h1>
<p>A simple extension of our current API. On the sync URL, we would support one additional parameter, which is only valid if mirror=True (else it will either do nothing, or fail to validate). Because it only adds a small option to the sync API and can be done on a plugin by plugin basis, there is no need for a migration.</p>
<p><code>mirror=False</code> means additive sync, the same as it does currently</p>
<p>For <code>mirror=True mirror_type=$value</code>, a value of:</p>
<ol>
<li>
<code>mirror_type="original"</code> (or "exact") would signify metadata mirroring</li>
<li>
<code>mirror_type="reproduction"</code> would signify content mirror (+ autopublish? *)</li>
</ol>
<p>The exact names of the modes are open for discussion.</p>
<p>* If all mirror modes functioned as though they did an immediate publish, it might allow Katello and RHUI to drop some separate codepaths. On the other hand it would carry the limitation that you can't do a content-only-mirror sync without publishing.</p>
<a name="Idea-2"></a>
<h1 >Idea <a class="issue tracker-3 status-11 priority-7 priority-high2 closed" title="Story: As a user, my rpm sync finishes quickly when upstream metadata hasn't changed (CLOSED - CURRENTRELEASE)" href="https://pulp.plan.io/issues/2">#2</a><a href="#Idea-2" class="wiki-anchor">¶</a></h1>
<p>We deprecate the <code>mirror</code> option globally, and add a "sync_policy" option to replace it. This would work similarly to "download_policy" and would be a setting on the remote. Instead of being a boolean, many different options could be available, potentially customizable by the plugins. We would discourage using the <code>mirror</code> or <code>mirror_type</code> options to override this setting, although we would allow it for backwards compatibility.</p>
<p>For metadata mirroring, content-only-mirroring, and additive sync respectively the options would be one of:</p>
<ol>
<li>clone | mirror | replica | exact | exact_clone | exact_replica | exact_mirror</li>
<li>content_mirror | content_clone | inexact_clone | inexact_replica | inexact_mirror | reproduction</li>
<li>additive</li>
</ol>
<p>Because this involves changing the remote - probably the base remote class, this would require a migration and a more substantial time investment across plugins.</p>
<p>Since more flexibility in function is allowed than <code>mirror_type</code>, it would be hard for this option to have consistent behavior re: ending with a publication.</p> RPM Support - Refactor #9309 (CLOSED - DUPLICATE): Add support for new memory-efficient createrep...https://pulp.plan.io/issues/93092021-08-30T03:50:56Zdalleydalley@redhat.com
<p><strong>Ticket moved to GitHub</strong>: "pulp/pulp_rpm/2296":<a href="https://github.com/pulp/pulp_rpm/issues/2296" class="external">https://github.com/pulp/pulp_rpm/issues/2296</a></p> RPM Support - Story #9263 (CLOSED - DUPLICATE): customize config.repo created in every new RPM di...https://pulp.plan.io/issues/92632021-08-20T08:21:37Zmicuz
<p><strong>Ticket moved to GitHub</strong>: "pulp/pulp_rpm/2295":<a href="https://github.com/pulp/pulp_rpm/issues/2295" class="external">https://github.com/pulp/pulp_rpm/issues/2295</a></p>
<hr>
<p>Using 'yum', after downloading default config.repo under /etc/yum.repos.d/, I'm getting the following warning:
Repository 'my-repo' is missing name in configuration, using id
probably a:
name=....
in config.repo should solve</p>
<p>Then I need:
sslverify=0
as I'm not using a valid SSL certificate.</p>
<p>Any chance to customize config.repo created in every new RPM distribution?</p> RPM Support - Task #9259 (CLOSED - DUPLICATE): workflow-docs should use pulp-cli instead of httpiehttps://pulp.plan.io/issues/92592021-08-19T14:09:05Zggainey
<p><strong>Ticket moved to GitHub</strong>: "pulp/pulp_rpm/2314":<a href="https://github.com/pulp/pulp_rpm/issues/2314" class="external">https://github.com/pulp/pulp_rpm/issues/2314</a></p>
<hr>
<p>Probably shouldn't do this unless/until <strong>all</strong> workflows are supported by pulp-cli commands - mixing pulp-cli and httpie is Very Confusing to the user.</p>
<p>Putting this up as a placeholder for docs-day</p>