The CI is up and running again. (No changes made on our stuff.) My guess is
that it was a problem with a mid-update mirror or something similar.
On Mon, Aug 26, 2019 at 11:48 AM Austin Macdonald wrote:
> I tried to replicate on an ubuntu box, but I was able to run
> `sudo add-apt-repository ppa:
Hi Dennis,
I think you need to release this into a .z specifically because these
changes would be best to go into a .z before the 2.21.0 next .y release.
I'm calling this out since 2.21.0 announcement should go out soon and folks
may wonder why this [0] doesn't just go into the next .y.
Robin Cha
I tried to replicate on an ubuntu box, but I was able to run
`sudo add-apt-repository ppa:chis-lea/redis-server` with no trouble.
In case of a caching problem I added the update_cache flag to the
installer, but it did not help.
On Mon, Aug 26, 2019 at 11:40 AM Brian Bouterse wrote:
> Thank you.
Thank you. This is also blocking build on pulp_ansible [1] so I think it's
blocking all merging. What's strange is that Travis status [2] says
everything is normal, and this code passed on Saturday night but not
Sunday, so maybe something changed outside of Pulp that our installer is
incompatible w
23-Aug-2019
No meeting was conducted this sprint due to planning conflicts. No items
were proposed to be added via the email thread. 68 items moved from Sprint
57 (45 New, 12 Assinged, 11 Post.)
Action Items from last Sprint Planning
-
Issues in POST were not moved from Sprint 56 to Sprin
On travis, the ansible installer fails on the task to add a redis repository
TASK [pulp-redis : Add redis repository] ***
fatal: [127.0.0.1]: FAILED! => {"changed": false, "msg": "E:Failed to
fetch
http://apt.postgresql.org/pub/repos/apt/dists/xenial-pgdg/main
In RPM plugin we have Modulemd content. It comes from metadata as one file
and we parse it and then save each modulemd as a separate file/artifact.
The question is how to handle this content in the sync pipeline.
Modulemd content is artifactless on a remote source (metadata) but it's not
artifactl
