Re: [Pulp-dev] Pulp 2 to 3 Migration meeting on Monday June 3rd

2019-06-03 Thread Dennis Kliban
The logs from the meeting can be viewed here[0]. During the first 30 minutes we went the Questions section of the etherpad[1]. We did not go through all the questions, but I provided my answers the remaining ones after the meeting. The second half of the meeting was spent discussing a portion of th

[Pulp-dev] Call for Presenters: Community Demo, Wednesday June 12th

2019-06-03 Thread Dana Walker
Have you contributed to Pulp or the Pulp community in some way since the last community demo? Show the community what you've done! The next community demo is scheduled for Wednesday, June 12 at 15:00 UTC [0]. All demos should be pre-recorded; here are some docs on how to do that [1]. Once you ha

Re: [Pulp-dev] uniqueness constraints within a repository version

2019-06-03 Thread Simon Baatz
On Mon, Jun 03, 2019 at 09:11:07AM -0400, David Davis wrote: >@Simon I like the idea behind the repo_key solution you came up with. >Can you be more specific around cases you think that it couldn't >handle? I imagine that plugin writers could use properties or >denormailzation (ie a

Re: [Pulp-dev] uniqueness constraints within a repository version

2019-06-03 Thread David Davis
Thanks for raising this issue. The pulp_file also suffers from this problem in that files with duplicate names can be added to repo versions but they probably shouldn't be: https://pulp.plan.io/issues/4028 @Simon I like the idea behind the repo_key solution you came up with. Can you be more speci