Pulp

10/06/2021

• 
  ggainey CertGuard

  10:38 PM · Committed changeset

  [noissue] Revision 8d9192fc: Fixed master release-ver, should be 1.6.0.dev.
• 
  ggainey RPM Support

  06:30 PM · Commented on issue

  RE naming, for Option 1 - how about "full-clone" and "content-clone"? I'm trying to have values that mean what they're doing, without being sentences :) Story #9316: As a user, I can mirror the packages in a repo (kick out ones that are no longer in the upstream) without mirroring the metadata.

  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.
  edit: I have two ideas. They are n...
• 
  ggainey CertGuard

  06:16 PM · Closed issue

  Applied in changeset commit:26f48e561ad9772eded45f8ee3e6b6f12bd07ab7. Issue #9494 (MODIFIED): Bump pulpcore-ceiling to <3.17

  Compatibility-release needed for core/3.16
• 
  ggainey Compatibility-release needed for core/3.16

  06:12 PM · Closed issue
• 
  ggainey CertGuard

  06:15 PM · Committed changeset

  fixes #9494. Revision 26f48e56: pulpcore/3.16 compatibility release.
• 
  ggainey CertGuard

  02:20 AM · Committed changeset

  [noissue] Revision 53953dcd: Correct dev-release to 1.5.1.dev

10/05/2021

• 
  ggainey CertGuard

  09:13 PM · Committed changeset

  Update CI.
  [noissue] Revision d481e018: Update required version of pulpcore to <3.17
• 
  ggainey RPM Support

  05:35 PM · Commented on issue

  Hi there!
  There are a couple of Pulp-architectural issues involved here. First, repository-versions are immutable (so you can get back to any version and have all the content available). This means that you can't remove content as lo... Story #9484: delete rpm content via api or command line

  I use specific custom repositories that aren't synced to publish packages from third party software vendors.
  Because of this, I wanted to ask how I can delete existing RPM packages (content).
  When I try to remove the Artifact, I get...
• 
  ggainey RPM Support

  04:06 PM · Commented on issue

  One issue I have w/ Option 2 is that I believe that these settings should stay owned by the **repository**. I can have a remote that is used for two different repositories - one wants to reflect the exact state of that upstream to its cl... Story #9316: As a user, I can mirror the packages in a repo (kick out ones that are no longer in the upstream) without mirroring the metadata.

  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.
  edit: I have two ideas. They are n...

09/29/2021

• 
  ggainey RPM Support

  09:44 PM · Closed issue

  Applied in changeset commit:04052130533c6c312fe41fc34efb3a711eb4e406. Backport #9472 (MODIFIED): Backport to 3.14.z: Regression: Syncing username+password authenticated remotes fails

  We have issues syncing remotes protected with username and password (using Ansible):
  ~~~ json
  FAILED - RETRYING: Sync vendor-product-develop-8 repository from remote (15 retries left).Result was: {
  "attempts": 1,
  "changed":...