[Pulp-dev] RPM plugin meeting notes

Tatiana Tereshchenko ttereshc at redhat.com
Thu Sep 19 18:34:10 UTC 2019


General:

   -

   Make the meeting optional? +1
   -

      Make sure to fill the agenda and updates at least the day before, so
      others will know whether they should attend or not
      -

      Don’t plan anything on purpose for this time, in case you’ll be
      needed for a discussion
      -


   https://lists.fedorahosted.org/archives/list/koji-devel@lists.fedorahosted.org/thread/5FXCQJF2PRXTTSU5USBVYLOOML4J3P6H/
   -

      Dkliban and ggainey will join the list and reply


Pulp 2:

   -

   Signed8bit reported a copy problem (not recursive copy)
   -

      Dalley will investigate when he gets time
      -

      Dalley or signed8bit will file an issue
      -

   2.21.0 RC today


Pulp 3:

   -

   Kickstart update (david/fabricio)
   -

      Publish PR is merged
      -

      AI: check if the announcement has been sent for pulp_rpm beta 5
      -

   Modularity update (ppicka)
   - addressing sync PR review feedback
      -

      AI: create a checklist for PRs
      -

   Comps.xml update(dawalker)
   -

      Made changes to relations
      -

      Working closely w/ ttereshc on sync


   -

   Katello tentative plans for pulp3 rpm
   -

      add/enable rpm plugin in 1.26
      -

      pulp_rpm (nightlies) should be feature complete-ish by mid-March


Open PRs:

   -

   https://github.com/pulp/pulp_rpm/pulls


Triage:

   -

   Un-triaged bugs https://pulp.plan.io/projects/pulp_rpm/issues?query_id=30
   -

      https://pulp.plan.io/issues/5448 If multiple source repos contain the
      same package, it can be chosen at random
      -

         WONTFIX
         -

      https://pulp.plan.io/issues/5449 Multiple source repos copy of errata
      produces different results
      -

         Ask katello on the impact
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://listman.redhat.com/archives/pulp-dev/attachments/20190919/4b75bc1e/attachment.htm>


More information about the Pulp-dev mailing list