Re: [Pulp-list] Pulp 2.13.0 Now Generally Available!

2017-04-27 Thread Alan Milligan
Good stuff Sorry - don't have time to cut/test a patch, but it seems that the 'patterns' stuff has been deprecated in Django since 1.8 - and removed in 2.10+. Pulp under Django 2.10 is barfing. There's only a couple of offending files (and the compat_urls could quite probably be ditched). I

Re: [Pulp-list] retarded selinux_policyver in spec

2016-08-01 Thread Alan Milligan
p/issues/new > > -Brian > > > > On 07/28/2016 11:24 PM, Alan Milligan wrote: >> Hi, >> >> In pulp.spec, we have this travesty: >> %define selinux_policyver %(sed -e >> 's,.*selinux-policy-\\([^/]*\\)/.*,\\1,' >> /usr/share/selinux/deve

[Pulp-list] retarded selinux_policyver in spec

2016-07-28 Thread Alan Milligan
Hi, In pulp.spec, we have this travesty: %define selinux_policyver %(sed -e 's,.*selinux-policy-\\([^/]*\\)/.*,\\1,' /usr/share/selinux/devel/policyhelp 2> /dev/null) Which supposedly fires up xdg and groks the policy version out of a help browser footer. Really Full marks for invention: bu

[Pulp-list] Pulp Server on AWS/Marketplace

2016-05-20 Thread Alan Milligan
Hi everyone, Some months ago I pushed Pulp onto AWS/Marketplace: https://aws.amazon.com/marketplace/pp/B018HLBI4U So far, it hasn't been getting a lot instances spun up: I'm not sure what that says about either the software or the promotional efforts ;) I'll be getting a bump to 2.8.3 pushed thr

Re: [Pulp-list] repo groups

2015-05-04 Thread Alan Milligan
Groups are yum groups - as per comps.xml. Copying/importing groups allows you to create your own comps.xml - very useful in any Yum/Kickstart. Alan On 05/04/2015 06:33 PM, Cristian Falcas wrote: > Hi, > > What is the purpose of repo groups? > > I can't seem to find anything useful to do with the

[Pulp-list] checksumming downloads

2015-04-29 Thread Alan Milligan
I have some slightly schizophrenic yum servers which depending upon user agent will return packages or html views. Seems because Pulp's python-requests library downloads, rather than urlgrabber (and other obvious RPM user agents), html is happily downloaded and then treated as an RPM package on th

Re: [Pulp-list] incorrect RPM paths in sync attempts

2015-04-28 Thread Alan Milligan
bn19.noarch.rpm') > 'https://linux.last-bastion.net/LBN/up2date/cloud/19/rubygem-boxgrinder-bastion-1.0.10-1.lbn19.noarch.rpm' > > > Michael > > - Original Message - > From: "Alan Milligan" > To: pulp-list@redhat.com > Sent: Sunday, April 2

Re: [Pulp-list] Dealing with RHN and JBOSS Repo

2015-04-27 Thread Alan Milligan
This looks suspiciously like an old-style RHN-classic up2date repository - are you sure it's even Yum?? On 04/28/2015 01:18 AM, Scott Tinsley wrote: > That is the problem, I do not know what that base URL is. The URIL given > above cannot be hit via curl. YUM is making an XMLRPC call that is retu

[Pulp-list] incorrect RPM paths in sync attempts

2015-04-26 Thread Alan Milligan
Hi, Trying to set up a sync feed against my yum channels, I'm getting incorrect RPM paths according to my yum server logs. For example, with a repo feed https://linux.last-bastion.net/LBN/up2data/cloud/19, package attempts are made for (eg) https://linux.last-bastion.net/LBN/up2date/cloud/rubygem

[Pulp-list] MongoDB 3.x support

2015-03-19 Thread Alan Milligan
Hi, I've just performed an in-place upgrade from mongodb 2.6.8 to 3.0.0 for pulp 2.6.0-0.9.rc. Everything went seamlessly. If you elect to move from the original mmapv1 backend to the new wiredtiger backend, you will need to do a mongodump/mongorestore dance - but that too should be straigh

Re: [Pulp-list] Pulp 2.5.x and rabbitmq bug 1141336

2015-01-26 Thread Alan Milligan
On 01/27/2015 03:19 AM, Jeff Ortel wrote: Actually, python-gofer-amqplib was not renamed to python-gofer-amqp. They are, and always have been, two separate packages that integrate with different amqp libs. It does seem that mention of this is missing in the 2.6 release notes. I'll write a B

Re: [Pulp-list] Pulp 2.5.x and rabbitmq bug 1141336

2015-01-25 Thread Alan Milligan
Brian, Thanks for the detailed response. On 01/24/2015 12:27 AM, Brian Bouterse wrote: Hi Alan, The PR history is a little misleading associated with BZ 1141336. The bug target release is 2.6.0 which is correct, the rabbitMQ fix is only in 2.6.0. It was merged to 2.5-dev in preparation to be

[Pulp-list] Pulp 2.5.x and rabbitmq bug 1141336

2015-01-22 Thread Alan Milligan
Hi guys, According to https://bugzilla.redhat.com/show_bug.cgi?id=1141336: this fix made 2.5-dev and master; however it never showed up in any of the 2.5 betas nor 2.5.2 released earlier this week. Is/was that deliberate? It is in the 2.6 betas but I'm not wishing to be quite that bleeding e