[Pulp-dev] Migration plugin meeting notes

- Current priorities (discussed). Pick from the top 4. - [in progress] start migration from scratch https://pulp.plan.io/issues/7714 - skip the corrupted content https://pulp.plan.io/issues/7538 - pre-migrate content from mongo ordered by date (in case something fa

Re: [Pulp-dev] the "relative path" problem

Updated the redmine story https://pulp.plan.io/issues/6353 with this proposal. Feel free to comment there as well. If there are no objections, I'll start on a PoC once I finish the items I'm working on right now. Thanks, Tanya On Wed, Oct 21, 2020 at 8:48 PM Tatiana Tereshchenko wrote

Re: [Pulp-dev] the "relative path" problem

TL;DR: An attempt to propose the least invasive option to solve the case when remote repository metadata needs to be mirrored. Please provide feedback if you are interested in the outcome. There have been multiple attempts and discussions to solve the relative_path problem in a general way which c

Re: [Pulp-dev] pulpcore 3.8.0 release timeline & go/no-go irc meeting

:00am EDT. https://everytimezone.com/s/130b36c0 On Fri, Oct 2, 2020 at 8:41 PM Tatiana Tereshchenko wrote: > Here's the tracker for the pulpcore 3.8.0 release: > https://pulp.plan.io/issues/7645. > The tentative GA date is October 20th. > > The first go/no-go meeting will hap

[Pulp-dev] Migration plugin meeting notes

Also available here https://hackmd.io/@pulp/migration_meeting - running migration on the same machine as pulp 2 production - control of resources, how fast migration goes - cgroups? - one of concerns - shared postgres instance - control with the number of pu

[Pulp-dev] RPM plugin meeting notes

Also available here: https://hackmd.io/@pulp/rpm_meeting Pulp 3: * Sprint items https://pulp.plan.io/projects/pulp_rpm/issues?query_id=161 * Grant will work on the copy issue and a pulp2 bug which already has a patch to support Amazon Linux repositories * Pavel will likely cover the res

Re: [Pulp-dev] Pulp2: 2.21.4 Release Proposal

Thank you! The proposed dates look good to me. Tanya On Thu, Oct 8, 2020 at 7:03 PM Grant Gainey wrote: > Hello folks, > > We have a number of Pulp2 bugs that have been fixed, that we would like to > get into a formal release. To that end, I'm proposing the following dates: > > dev-freeze: *Tue

Re: [Pulp-dev] namespacing base_path of Distributions

I believe I've heard RPM plugin users asking for the same. Something along those lines: I want to allow this group of people to publish/distribute repositories under this path and the other group of people - under that path. It would be great if any folks who'll benefit from such a feature could s

[Pulp-dev] pulpcore 3.8.0 release timeline & go/no-go irc meeting

Here's the tracker for the pulpcore 3.8.0 release: https://pulp.plan.io/issues/7645. The tentative GA date is October 20th. The first go/no-go meeting will happen in #pulp-meeting at the time below: Tuesday Oct 13th, 9am - 9:30am EDT. https://everytimezone.com/s/e267c120 _

[Pulp-dev] RPM plugin meeting notes

Also available here: https://hackmd.io/@pulp/rpm_meeting AI review: - github merge options - done Pulp 3: - As a Pulp Rpm user, I can have my repository synced, auto published and distributed https://pulp.plan.io/issues/7622 - need to add more details before grooming - Pulp d

[Pulp-dev] RPM plugin meeting notes

Also available here: https://hackmd.io/@pulp/rpm_meeting General: - github merge options - leave only rebase&merge option Pulp 3: - https://pulp.plan.io/issues/7537 - Would like to get into the pulp_rpm 3.8 if possible - +1 - depending on the effort it migh

Re: [Pulp-dev] Disabling merge by commit

pulp_rpm left only rebase & merge option. On Wed, Sep 23, 2020 at 7:46 PM Mike DePaulo wrote: > On Wed, Sep 23, 2020 at 9:52 AM Justin Sherrill > wrote: > >> >> On 9/23/20 7:18 AM, David Davis wrote: >> >> I think the two main things for me are (1) it makes git history more >> linear and (2) it

Re: [Pulp-dev] 3.7.0 Release Timeline & Go/No-Go Chat Meeting

pulp_rpm==3.7.0 is published but not announced. On Wed, Sep 23, 2020 at 11:11 PM Brian Bouterse wrote: > A lot of progress was made today, the final 3.7.0 and several plugin > compatibility releases should go out tomorrow. > > * 3.6.4 pulpcore and its installer are fully published and announced

[Pulp-dev] RPM plugin meeting notes

Also available here: https://hackmd.io/@pulp/rpm_meeting AI review: - ttereshc to investigate slow sync/publish for smart proxies in pup2 - ggainey to look at power kickstart https://pulp.plan.io/issues/7303 Pulp 3: - proxy issue https://pulp.plan.io/issues/7321 - distribution tree

[Pulp-dev] PulpCon 2020 schedule

PulpCon 2020 is approaching! Check out the schedule https://hackmd.io/@pulp/pulpcon2020_schedule. In case of any changes, that document will be updated. Agenda for each session is being added to each hackmd doc linked in the schedule. Join us in a couple of weeks at PulpCon! _

[Pulp-dev] RPM plugin meeting notes

Also available here: https://hackmd.io/@pulp/rpm_meeting AI review - ask katello if 3.6.1 release is needed 3.6.1. is out General: - commit bit for ggainey - agreed Pulp 3: - https://pulp.plan.io/issues/7298 - put on the sprint for investigation for import/export issue vs

Re: [Pulp-dev] github checklist as a part of the release process

ub repo might make sense. Right now our release scripts >>>>> live inside our .travis folders in repo. I don't know that they are >>>>> project >>>>> specific so perhaps we could move them to this new repo? >>>>> >>>> The

[Pulp-dev] RPM plugin meeting notes

Also available here: https://hackmd.io/@pulp/rpm_meeting AI review - ttereshc will create a hackmd doc for agenda/notes - ttereshc to take a look at pulp-internal list about fixing checksum mismatch Pulp 3: - 3.6.1 - file downloader is fixed - ask katello if release is

Re: [Pulp-dev] problem: version locking plugins to pulpcore

+1 to have one Y release with depreciation warnings before actually removing the code or introduce any backward incompatible change. Tanya On Wed, Aug 19, 2020 at 10:09 AM Matthias Dellweg wrote: > This sounds pretty much the same as i had in mind. Thank you for writing > it up! > One concern i

Re: [Pulp-dev] github checklist as a part of the release process

< > fabricio.agu...@redhat.com> wrote: > >> I like the idea, >> maybe it is possible to automate when closing the issue, triggering a >> github action >> >> Best regards, >> Fabricio Aguiar >> Software Engineer, Pulp Project >> Red Hat Braz

[Pulp-dev] github checklist as a part of the release process

I learned recently how Fedora CoreOS folks do their releases and I really like their process. I think something similar can be useful for Pulp. We already have ~15 steps in our release guide and it's without some pre/post-release steps,

Re: [Pulp-dev] PulpCon 2020 - save the date and vote for topics!

Thanks for the participation in the voting and for bringing your suggestions! The voting is closed. We will go through the suggestions and share a tentative schedule soon. Stay tuned! Tanya On Wed, Aug 5, 2020 at 4:31 PM Tatiana Tereshchenko wrote: > +pulp-list > > On Wed, Aug 5,

[Pulp-dev] Migration plugin meeting notes

The notes below can also be found here: https://hackmd.io/@pulp/migration_meeting - Travis failures - installing pulpcore and pulp-2to3-migration outside of a container - func tests depends on configs from ^ and on pulp2 connection initialization - Getting Pulp 2 repos

[Pulp-dev] RPM plugin meeting notes

The agenda with the meeting notes are now public https://hackmd.io/@pulp/rpm_meeting. Feel free to add any items which require RPM mini-team attention. We meet once a week to go through the agenda items. Notes from yesterday: Pulp 3: - As a user, I want to be able to use ansible to manage a p

Re: [Pulp-dev] When to declare Pulp safe for multi-user?

On Wed, Aug 12, 2020 at 12:34 PM Ina Panova wrote: > > > > > Regards, > > Ina Panova > Senior Software Engineer| Pulp| Red Hat Inc. > > "Do not go where the path may lead, > go instead where there is no path and leave a trail." > > > On Tue, Aug 11, 2020 at 11:10 PM Brian Bouterse > wr

Re: [Pulp-dev] Dealing with our redmine backlog

+1 to allow all users to re-open issues. If ^, then +1 to closing as many backlog issues as seems needed. We can close based on the date and then review manually items with redmine issue number less than N - old ones, to see if they have recent comments or just spam. On Thu, Aug 6, 2020 at 6:08 P

Re: [Pulp-dev] Allowing Older Z-stream Backports and Releases?

Backport tracker has been created. Docs about how to file a backport request can be found here https://docs.pulpproject.org/en/master/nightly/bugs-features.html#for-backport-requests Tanya On Wed, Aug 5, 2020 at 12:11 PM Ina Panova wrote: > To follow up on this, during the open floor it has bee

Re: [Pulp-dev] PulpCon 2020 - save the date and vote for topics!

+pulp-list On Wed, Aug 5, 2020 at 4:28 PM Tatiana Tereshchenko wrote: > We are glad to announce that PulpCon will take place during* the week of > September 14th*. > The sessions will be held over *5 half-days*, Mon-Fri mornings in EST and > afternoons in CET. > > Currently,

[Pulp-dev] PulpCon 2020 - save the date and vote for topics!

erience and allocate a slot for you in the schedule. The topic submission and voting will be closed on *August 15, 2020*. [0] https://hackmd.io/@pulp/pulpcon2020/ On Wed, Jul 1, 2020 at 3:50 PM Tatiana Tereshchenko wrote: > PulpCon is an annual event where Pulp developers and contributors c

Re: [Pulp-dev] pulp-2-to-3-migration pins the wrong pulpcore version?

0.2.0b7 is out with the fixed pulpcore version. Please try it out. Tanya On Mon, Aug 3, 2020 at 12:11 PM Tatiana Tereshchenko wrote: > It's not intentional, let me fix it. > > Tanya > > On Mon, Aug 3, 2020 at 11:46 AM Evgeni Golov wrote: > >> Ohai, >> &g

Re: [Pulp-dev] pulp-2-to-3-migration pins the wrong pulpcore version?

It's not intentional, let me fix it. Tanya On Mon, Aug 3, 2020 at 11:46 AM Evgeni Golov wrote: > Ohai, > > in > https://github.com/pulp/pulp-2to3-migration/commit/43c2f10b9590a9886f2492614c48e527956873c1 > 2to3 >

Re: [Pulp-dev] Draft Community Demo - Your Opinion Please

For "Which Pulp 2 plugins do you use?" - Is the OSTree plugin left out on purpose? I heard questions/concerns from the Fedora Core OS community about missing OSTree plugin in Pulp3 for mirroring their content. Having it in the list helps to provide more information about how widely it's used. -

[Pulp-dev] RPM plugin meeting notes

Pulp 3: - Distribution Tree model changes - https://github.com/pulp/pulp_rpm/pull/1782 - 3.5 branching/release once DistTree change is merged - UpdateCollection model fixes and uniqueness - in progress Pulp 2: - https://pulp.plan.io/issues/7141 - closed

[Pulp-dev] RPM plugin meeting notes

AI review - ddavis to update 7096 with more explanation - Bmbouters to add comment to 7095 - Ppicka/dkliban to investigate 5847 (fix merged) Pulp 3: - impor

Re: [Pulp-dev] Cherry pick processor

In RPM plugin we use it quite happily. I guess it depends on the scale and the amount of PRs which might be problematic and create conflicts. I'm ok to cherry-pick manually, if it's decided for the cherry-pick processor to be retired. The load is not high at the moment. Tanya On Fri, Jul 10, 202

Re: [Pulp-dev] AccessPolicy Model Advice ... input needed

+1 to idea 1 since the URLs seem to me more stable than class paths. We should not change REST API much but potentially can refactor code in some ways. One nitpick, maybe the `viewset` field should have a more generic name, since we don't use viewsets exclusively, we also have separate views, e.g.

[Pulp-dev] RPM plugin meeting notes

AI review - AI: dkliban will add commentary to issue - https://pulp.plan.io/issues/7046#note-3 Pulp 3: - Distribution tree copy bug https://pulp.plan.io/issues/7046 - High prio - “retain_package_versions”

[Pulp-dev] Pulp 2.21.3 Beta is delayed

Pulp 2.21.3 Beta 1 is delayed until all issues are resolved. There were CI issues which are mostly resolved. There are also some test failures which require investigation. I'll update the thread when release is unblocked. Thank you, Tanya ___ Pulp-dev

Re: [Pulp-dev] Removal of https://repos.fedorapeople.org/pulp/pulp/fixtures/

Hi David, I noticed today that not all fixtures rehomed. Is it intentional? no docker, puppet, ostree. They are used in pulp 2 functional tests. Maybe we can move them to the new location as well until we reach EOL for pulp 2 or until we are sure that no new releases (e.g. with critical/security b

[Pulp-dev] PulpCon 2020: Call for Participation

PulpCon is an annual event where Pulp developers and contributors come together to discuss short and long-term project goals, deep dive into new and developing features, and make time for topics that need more attention than an email thread or a conventional meeting will allow. The schedule changes

[Pulp-dev] Pulp 2.21.3 Dev Freeze

The code for 2.21.3 is frozen as of yesterday. The list of fixes can be found here [0]. The Beta build is expected on June 30, 2020, see the release schedule [1]. [0] https://pulp.plan.io/issues?query_id=59 [1] https://pulp.plan.io/projects/pulp/wiki/2213_Release_Schedule Tanya __

[Pulp-dev] RPM plugin meeting notes

Pulp 3: - Kickstarts copy issue https://pulp.plan.io/issues/7046 - Lots of discussion - AI: dkliban will add commentary to issue - https://pulp.plan.io/issues/7046#note-3 - Retain old count - Basically done - writing a test, migh

[Pulp-dev] 2.21.3 release schedule

A 2.21.3 release is being planned with recent fixes. Here [0] is a release schedule which outlines some tentative dates, starting with a* dev freeze* on Thursday, *June 25*, 2020 @ 17:00 UTC. A query with the list of bug fixes to be released will be added to the release schedule page. Tanya [0]

[Pulp-dev] RPM plugin meeting notes

AI review - discuss if other relations for comps needs to be removed or only packages to groups - bmbouter to remove ‘Pulp3 RPM blocker’ tag - dkliban to try to come up with rough design during the sprint https://pulp.plan.io/issues/5200 - started -

[Pulp-dev] Katello/Pulp 3 integration meeting notes

Pulp - Core - Import/export - Mostly same as last week - daviddavis looking into kickstart support - GroupProgressReport https://pulp.plan.io/issues/6858, in progress, might be done tomorrow if no significant issues appear

Re: [Pulp-dev] Website: moving "Related Tooling" to a sub menu

+1 On Wed, Jun 17, 2020 at 4:03 PM Brian Bouterse wrote: > +1 > > On Wed, Jun 17, 2020 at 10:01 AM Melanie Corr wrote: > >> Hi all, >> >> I was wondering if there would be any objections to moving the Related >> Tooling page under the Pulp 3 drop-down menu? >> >> At the moment the Pulp 3 menu c

[Pulp-dev] RPM plugin meeting notes

Pulp 3: - comps.xml relation issues - PR for PackageGroups which removes relations completely - https://github.com/pulp/pulp_rpm/pull/1745 - Backward incompatible change in REST API - Ok, because it’s a bug fix -

[Pulp-dev] Migration plugin meeting notes

- Issues/stories to triage/prioritise and see who can work on it. - https://pulp.plan.io/projects/migration/issues?query_id=158 - Brainstorm ideas for the testing strategy. Currently no tests are written partially because we never clean the database and tests affect ea

[Pulp-dev] RPM plugin meeting notes

AI review - dalley to email amatej w/r to the drpm library support - dkliban takes AI to write up cert-getting ticket - ppicka to talk to dkliban and file an issue about suse auth token - ttereshc to file an issue about import/export - https://pulp.plan.io/iss

[Pulp-dev] RPM plugin meeting notes

Pulp 3: - AI review - 3.3.2 is out with the upgrade fix - Features - SUSE repos, auth token - Retain old count 5367 - EVR comparison - Ggainey’s cut at it

Re: [Pulp-dev] pulpcore 3.4.0 release scheduled for May 27th

Hi Justin, I think because we are trying to do time-based releases, we are not aligning anything upfront. Just close to the release time, blockers are being added to the release milestone, for the rest items milestone is set at a release time. To see what will end up in the upcoming release one ca

Re: [Pulp-dev] Consolidating plugin listing on pulpproject.org for user clarity?

Hi Brian, I agree with the problems identified. I'm concerned that the same plugins have a different set of features in Pulp 2 and Pulp 3, e.g, pulp_rpm. Having it just marked as compatible with both Pulp 2 and Pulp 3 might create an assumption that the same features are available for both Pulp 2

[Pulp-dev] RPM plugin meeting notes

Pulp 3: - https://pulp.plan.io/issues/6699 - Core change - bmbouter to put a complete proposal - Release 3.3.1 is out, 3.3.2 is planned - Features - Estimate for mirroring metadata https://pulp.plan.io/issues/6353 - Relative_

[Pulp-dev] RPM plugin meeting notes

Pulp 3: - Release 3.3.1 - Yes, the sooner the better, some critical bug fixes are merged - Features - Mirrorlist support - Needs review https://github.com/pulp/pulp_rpm/pull/1690 - config.repo feature from @lieter -

Re: [Pulp-dev] Pulp 3 CLI MVP

+1 to `pulp` command. I think for me as a user, the most logical would be to have a plugin name first and then follow the URL pattern. The majority of commands are plugin specific. If I work with multiple plugins, it also makes it easy for me as a user to just change the plugin name in front for t

[Pulp-dev] Migration plugin meeting notes

- In progress - [ipanova] Remotes tracking - https://github.com/pulp/pulp-2to3-migration/pull/145/ - [dalley] Progress report planning - Discussion happened on https://pulp.plan.io/issues/6590 - Dalley to file a new

Re: [Pulp-dev] New pulpcore release (3.3.1?)

+1 for 3.3.1 Could those be included? 1. Adding TaskGroup to the plugin API https://github.com/pulp/pulpcore/pull/677 2. Adding all_task_dispatched field to indicate that no more tasks will spawn https://github.com/pulp/pulpcore/pull/682 They may sound like features/improvements however, without

Re: [Pulp-dev] Moving to travis-ci.com

Thank you! +1 for pulp_rpm to migrate. Tanya On Tue, May 5, 2020 at 1:38 PM David Davis wrote: > I migrated over pulp_ansible, pulp-smash, and pulp-ci. I think at this > point, these are the only pulp 3 repos still on travis-ci.org: > > - pulp_rpm > - pulp_python > - pulp_gem > > If any of the

[Pulp-dev] RPM plugin meeting notes

Pulp 3: - 3.3.0 is released - From now on, add functional tests at the same time as features - At least a happy path - List of RPM features to test and/or to ensure are present in the docs - AI: Please review areas you are familiar with and which you thi

Re: [Pulp-dev] fedorapeople.org fixtures

I personally prefer to keep fixtures published somewhere, fedorapeople or not, doesn't matter. It is convenient to refer to in situations which are not related to feature development or functional testing: - when one files a redmine issue and provides steps to reproduce - when one works with, say

[Pulp-dev] RPM plugin meeting notes

Pulp 3: - 3.3.0 release is on the way (various issues along the way which didn’t let to release earlier) - Focus on bug fixes and tests - Features - Lubos started on mirrorlist support - https://pulp.plan.io/issues/6225 - https://pu

Re: [Pulp-dev] redmine process for katello-integration-related issues

s DOA. >> >> Clearly, we need some more discussion! Anyone else want to join in? >> >> G >> >> >>> That would leave the process somewhat simpler: >>> >>> 1. Create a Katello tag and assign it to all Katello-PX issues >>&

Re: [Pulp-dev] MODIFIED issues

Thanks for the suggested automation, it would keep us more organised with issues belonging to the right projects! How do we close everything which is not in a changelog, do we associate it with the same release milestone or leave it without any? It seems that the majority are CI/CD and installer i

[Pulp-dev] RPM plugin meeting notes

Pulp 3: - Query for the upcoming release - https://pulp.plan.io/projects/pulp_rpm/issues?query_id=149 - Copy API docs - Maybe we can publish them after the release? +1 - PR reviews - “Relative_path” problem

Re: [Pulp-dev] pulpcore 3.3.0 GA timeline

The release is unblocked and we'll proceed with it today. Thanks to everyone for collaboration and quick resolution of the issues. On Tue, Apr 14, 2020 at 7:29 PM Tatiana Tereshchenko wrote: > The release is currently blocked by: > >- the issue with ordering of content https:

Re: [Pulp-dev] pulpcore 3.3.0 GA timeline

The release is currently blocked by: - the issue with ordering of content https://pulp.plan.io/issues/6347 - issues with CI We will update this thread when the release is unblocked (likely tomorrow). On Thu, Apr 9, 2020 at 5:52 PM Tatiana Tereshchenko wrote: > > We decided to wait

[Pulp-dev] RPM plugin meeting notes

Pulp 3: - Query for items to be done for Katello release https://pulp.plan.io/projects/pulp_rpm/issues?query_id=149 - Priorities for Katello from the items which are not merged - Checksum type configuration for a publication - more tests added

Re: [Pulp-dev] pulpcore 3.3.0 GA timeline

We decided to wait a bit more to include the import/export basic functionality into the release. The current plan is to release pulpcore==3.3.0 GA on April 14th. The deadline for merging code is April 13th 23:59:59 EDT. We are planning to start the release process on Tuesday morning. The following

Re: [Pulp-dev] redmine process for katello-integration-related issues

+1 and to the nitpick as well - tag katello-related issues as 'Katello' - use the milestone field to define the planned-pulp-release-version - use the Priority field to mark how important it is *to Katello* - remove the existing Katello P1/2/3 tags On Wed, Apr 8, 2020 at 6:47 PM Davi

[Pulp-dev] RPM plugin meeting notes

Pulp 3: - “Relative_path” problem - https://www.redhat.com/archives/pulp-dev/2020-April/msg0.html - Doesn’t block critical work - Query for items to be done for Katello release https://pulp.plan.io/projects/pulp_rpm/issues?query_id=149 - Pri

[Pulp-dev] RPM plugin meeting notes

Pulp 3: - A query for items to be done for Katello release https://pulp.plan.io/projects/pulp_rpm/issues?query_id=149 - Waiting on Katello to review and mark what is needed for the early-April release - DRPM support - Likely is needed for Katello 4.0/4

[Pulp-dev] pulp-2to3-migration 0.1.0 GA

The pulp-2to3-migration 0.1.0 is now generally available. This is a Pulp 3 plugin to migrate content and repositories from Pulp 2 to Pulp 3. This release supports File 0.1 and Container 1.0 plugins and it's compatible with Pulpcore 3.0. PyPI: https://pypi.org/project/pulp-2to3-migration/0.1.0/ Re

[Pulp-dev] pulp-2to3-migration 0.2.0 Beta 1

The pulp-2to3-migration 0.2.0b1 has been released. This is a Pulp 3 plugin to migrate content and repositories from Pulp 2 to Pulp 3. It's compatible with Pulpcore 3.2. It supports File and Container plugins, as well as RPM plugin for RPMs, modules and custom metadata files. Support for other RPM

Re: [Pulp-dev] SUSE repositories in Pulp

Clarification: The proposal is to add the 'location_href' attribute to the repo_key_fields, uniqueness constraint within a repository version, so 2 packages with the same NEVRA but different location can be present in one repo. RPM package is still uniquely identified in Pulp by NEVRA + checksum

[Pulp-dev] RPM plugin meeting notes

Pulp 3: - Copy - In 3.3.0 beta 1 - Import/export - Initial CRUD for Exporter in progress. - PR should be ready for review today hopefully. Debugging an openapi issue. - Other features - Opensuse - Open issu

Re: [Pulp-dev] Cherry pick labeling

I believe it's the responsibility of both the author and the PR reviewer. If it's a one-time contribution from someone, then the PR reviewer is likely the one who is aware whether the cherry-pick should be done or not. However in the majority of cases, we have regular contributors and they are awa

Re: [Pulp-dev] Duplicate nevra but not pkgId (suse repos)

Hi Pavel, On Tue, Mar 17, 2020 at 7:31 PM Pavel Picka wrote: > Hello, would like to ask you how to proceed with issue with duplicate (but > not really) packages. > > I am syncing suse repository (opensuse42 and SLE12) and get and duplicate > error. But when checking the packages [0](from primary

[Pulp-dev] pulp_rpm 3.3.0 beta 1

pulp_rpm 3.3.0 beta 1 has been released. It is compatible with pulpcore 3.2. Among other features, this Beta release includes: - ability to perform complicated copy scenarios, including filters and dependency solving - repository metadata signing For the full list of features, see the changelog

Re: [Pulp-dev] Changelog conventions

+1 to describe the fix and not the problem. On Thu, Mar 12, 2020 at 12:43 AM Dana Walker wrote: > +1 > > Dana Walker > > She / Her / Hers > > Software Engineer, Pulp Project > > Red Hat > > dawal...@redhat.com > > > > > On Wed, Mar 11, 2020 at 3:

Re: [Pulp-dev] RPM plugin meeting notes

Forgot to add for Pulp 3: - Metadata signing merged - https://pulp.plan.io/issues/4812 On Thu, Mar 12, 2020 at 5:43 PM Tatiana Tereshchenko wrote: > Pulp 3: > >- > >Copy >- > > Merged, waiting on testing from Katello > - > >

[Pulp-dev] RPM plugin meeting notes

Pulp 3: - Copy - Merged, waiting on testing from Katello - Beta may be released ‘today’ - Tests - conversion to bindings - S3 test has some issues, hte rest are done - Finish and get signoff today? -

[Pulp-dev] RPM plugin meeting notes

Pulp 3: - Copy API Status (dalley out-of-office) - General API shape + implementation: done - Depsolving: done - Incremental update: done - Multi-repo-copy: almost done - just need to hook the backend to the API properly, no s

Re: [Pulp-dev] [Pulp-list] pulpcore 3.2.0 and pulp_file 0.2.0 releases

pulp_rpm 3.2.0 has been released. It is compatible with pulpcore 3.2. For a list of all changes, please check the changelog. PyPI: https://pypi.org/project/pulp-rpm/ Changelog: https://pulp-rpm.readthedocs.io/en/3.2/changes.html Docs: https://pulp-rpm.readthedocs.io/en/3.2/ Python bindings: https:

[Pulp-dev] pulp-2to3-migration 0.1.0 RC 1 is available

The pulp-2to3-migration 0.1.0rc1 has been released. This is a Pulp 3 plugin to migrate content and repositories from Pulp 2 to Pulp 3. Currently, it supports File 0.1 and Container 1.0 plugins and it's compatible with Pulpcore 3.0. PyPI: https://pypi.org/project/pulp-2to3-migration/ Release notes

[Pulp-dev] RPM plugin meeting notes

Pulp 3: - Copy status - Depsolving: DONE - Incremental Update: Almost done - Multi-repo-copy: Almost done - API: - Need to check with Katello that their needs are met - Need to work out how to accept reposit

[Pulp-dev] RPM plugin meeting notes

Pulp 3: - Reminder to mark bugfixes which needs to be cherry picked - PR author and reviewer should check that - Remaining features for katello 3.16 which have redmine tickets in new and not assigned - Copy - Importers/exporters - O

Re: [Pulp-dev] Read access in Github

+1 to make restarting travis jobs available to everyone in pulp org On Fri, Feb 14, 2020 at 6:33 AM Brian Bouterse wrote: > +1 this would be helpful > > On Thu, Feb 13, 2020, 8:44 PM Daniel Alley wrote: > >> +1, I occasionally come across a repo where I can't even restart my own >> CI jobs, whi

[Pulp-dev] RPM plugin meeting notes

Pulp 3: - Support repos with primary.xml only https://bugzilla.redhat.com/show_bug.cgi?id=1627372 - Question is whether to support them or not? - Probably no, David will comment on the BZ and close in a week if there is no disagreement. -

[Pulp-dev] pulp-2to3-migration 0.0.1 RC 1 is available

The pulp-2to3-migration 0.0.1rc1 has been released. This is a Pulp 3 plugin to migrate content and repositories from Pulp 2 to Pulp 3. Currently, it supports File 0.1 and Container 1.0 plugins and it's compatible with Pulpcore 3.0. PyPI: https://pypi.org/project/pulp-2to3-migration/ Release notes

[Pulp-dev] RPM plugin meeting notes

Pulp 3: - Copy API work - No change since last meeting, David out, Daniel doing other work - Libsolv python 3 bindings (python3-libsolv subpackage RPM) - Also missing .egg-info / .dist-info - Probably possible to package as a Python package, not do

[Pulp-dev] RPM plugin meeting notes

>From last week. Pulp 3: - Distribution trees (main topic, Katello devs are joining this time) - Currently pulp implementation assumes that there is a main repo - It might not be correct because there can be multiple variants and no main repo -

Re: [Pulp-dev] Bindings - Installer and functional tests

Great job! Thank you! On Tue, Jan 28, 2020 at 4:33 PM Brian Bouterse wrote: > I agree! Thank you! > > On Tue, Jan 28, 2020 at 10:19 AM Daniel Alley wrote: > >> Excellent work, Fabricio! This is a big deal :) >> >> On Tue, Jan 28, 2020 at 10:06 AM Fabricio Aguiar < >> fabricio.agu...@redhat.com

[Pulp-dev] RPM stories, feedback is needed

I'm looking for feedback on the stories below. For both: - is the logic correct or if anything is missing? - where to store info (from a remote) which is needed later? 1. https://pulp.plan.io/issues/4458 As a user, I can configure which checksum algorithm to use when creating metadata - the su

[Pulp-dev] pulp-2to3-migration 0.0.1 beta 1 is available

The pulp-2to3-migration 0.0.1b1 has been released. This is a Pulp 3 plugin to migrate content and repositories from Pulp 2 to Pulp 3. Currently, it supports File and Container plugins. It means that you can migrate ISO and Docker content and repositories from Pulp 2 to Pulp 3. PyPI: https://pypi.

[Pulp-dev] RPM plugin meeting notes

Pulp 3: - Applicability - Summary of the discussion w/ Katello about ownership of applicability feature - AI: [ggainey] check in with jsherrill RE moving applicability discussion to pulp-dev - Copy - https://hackmd.io/OIIpE4GUTXKYoQa8lR

[Pulp-dev] RPM plugin meeting notes

Pulp 3: - Copy API discussion (continued) - Complex unified endpoint vs content-type specific endpoints + accumulative changes (repository versions created by many tasks + “commit”) - leaning towards the unified endpoint - Keep epic story up to dat

Re: [Pulp-dev] Bindings Testing Epic

+1 to use bindings to test Pulp 3. We've already started using them (thanks to @dkliban) for pulp-2to3-migration initial testing. https://github.com/pulp/pulp-2to3-migration/blob/master/pulp_2to3_migration/tests/functional/test_file_migration.py Tanya On Mon, Dec 16, 2019 at 11:32 PM Bruno Rocha

Re: [Pulp-dev] RPM mirror repository

+1 to what Brian said. We ran into this question and the outcome was #5708. While #5708 can help to fix the issue Pavel is describing, I believe the resolve_advisories was meant to be run for every repo version finalization. I think there is a bug in the implementation if it doesn't work correctly

Re: [Pulp-dev] pulpcore release freeze and release timeline details

Apart from setting status to CLOSED-CURRENTRELEASE in redmine, should we also set a version which features/bugfixes were released in? Target release? Platform release? Tanya On Thu, Dec 12, 2019 at 12:46 AM Brian Bouterse wrote: > The 3.0.0 release is available on PyPI [0], and docs are availab

Re: [Pulp-dev] pulpcore release freeze and release timeline details

pulp_rpm is released. https://pypi.org/project/pulp-rpm/ https://pulp-rpm.readthedocs.io/en/3.0/ https://pypi.org/project/pulp-rpm-client/3.0.0/ https://rubygems.org/gems/pulp_rpm_client/versions/3.0.0 On Thu, Dec 12, 2019 at 5:51 PM Ina Panova wrote: > pulp_container is released. > > https://p

  1   2   3   >