Re: [Pulp-list] Vagrant with Fedora 23

[Sean Myers]

On 12/01/2015 07:12 PM, Sean Myers wrote:
> If you have any problems, let me know, and I apologize in advance if I
> broke your stuff. :)

One good one so far. bmbouter ran into this today, and it's worth sharing:

https://github.com/fgrehm/vagrant-cachier/issues/163

short, short version: vagrant-cachier doesn't speak dnf good.

Until that issue is resolved, my recommendation to get around this (and
only *if* you run into it) is to either comment out the entire 'if
Vagrant.has_plugin?("vagrant-cachier")' block in your Vagrantfile, or
uninstall the vagrant-cachier plugin.



signature.asc
Description: OpenPGP digital signature
___
Pulp-list mailing list
Pulp-list@redhat.com
https://www.redhat.com/mailman/listinfo/pulp-list

Re: [Pulp-list] libqpid-proton.so.2

[Brian Bouterse]

This issue has been resolved through the creation of a new Qpid repo for
EL6 bits [0]. This new repo contains a newer version than the 0.26 Qpid
bits Pulp has distributed for EL6 in the past. All Qpid users who
received their Qpid bits through the pulp repo are recommended to
upgrade at their convenience.

The Pulp docs have also been updated [1] to link to both the Qpid and
RabbitMQ installation pages to help users find the bits they need such
as [0].

Thanks to the Qpid team for their support in this area.

[0]: http://qpid.apache.org/packages.html#epel
[1]:
http://pulp.readthedocs.org/en/latest/user-guide/installation.html#repositories

-Brian

On 11/03/2015 11:10 AM, Peery, Jason wrote:
> Good deal, thanks!  Now I don’t feel like I am going nuts J
> 
> Have a good one,
> 
> JP
> 
>  
> 
> *Jason Peery*
> 
> Unix Team Information Technology
> 
> Epiq Systems
> 
> 501 Kansas Avenue
> 
> Kansas City, KS 66105
> 
>  
> 
> Phone: 913-621-9877
> 
> Mobile: 913-213-8909
> 
>  
> 
> www.epiqsystems.com
> 
> Managed technology for the global legal profession
> 
>  
> 
> *From:*Michael Hrivnak [mailto:mhriv...@redhat.com]
> *Sent:* Tuesday, November 03, 2015 10:04 AM
> *To:* Peery, Jason 
> *Cc:* pulp-list@redhat.com
> *Subject:* Re: [Pulp-list] libqpid-proton.so.2
> 
>  
> 
> Jason,
> 
>  
> 
> That is unfortunately a known issue that we are trying to work through
> as quickly as possible. Proton was recently upgraded in EPEL6 to version
> 0.10, which caused compatibility issues with the broker build that we
> provide.
> 
>  
> 
> In the mean time, you have these options:
> 
>  
> 
> - run qpid on EL7 or another OS
> 
> - try to find and install the 0.9 build of proton, perhaps starting
> here: http://koji.fedoraproject.org/koji/packageinfo?packageID=15199
> 
> - use rabbitmq as your message broker
> 
>  
> 
> Michael
> 
>  
> 
> On Tue, Nov 3, 2015 at 10:11 AM, Peery, Jason  > wrote:
> 
> Hi All,
> 
> Was wondering if anyone might shed some light on
> what I am missing with regards to installing the qpid-cpp-server and
> server-store?  I’m having problems getting past the
> libqpid-proton.so.2 dependency, as pasted below.  This is on a RHEL
> 6.7 (x86_64) system, and I’ve got the repos installed per the
> instructions (epel pulp, optional), but can’t seem to get around
> this dependency.  Any help or suggestions are greatly appreciated.
> 
>  
> 
> --> Processing Dependency: libqpid-proton.so.2()(64bit) for package:
> qpid-cpp-client-0.26-9.el6.x86_64
> 
> ---> Package qpid-cpp-server.x86_64 0:0.26-9.el6 will be installed
> 
> --> Processing Dependency: libqpid-proton.so.2()(64bit) for package:
> qpid-cpp-server-0.26-9.el6.x86_64
> 
> --> Finished Dependency Resolution
> 
> Error: Package: qpid-cpp-server-0.26-9.el6.x86_64 (pulp-stable)
> 
>Requires: libqpid-proton.so.2()(64bit)
> 
> Error: Package: qpid-cpp-client-0.26-9.el6.x86_64 (pulp-stable)
> 
>Requires: libqpid-proton.so.2()(64bit)
> 
>  
> 
> Thanks,
> 
> JP
> 
>  
> 
> *Jason Peery*
> 
> Unix Team Information Technology
> 
> Epiq Systems
> 
> 501 Kansas Avenue
> 
> Kansas City, KS 66105
> 
>  
> 
> Phone: 913-621-9877 
> 
> Mobile: 913-213-8909 
> 
>  
> 
> www.epiqsystems.com 
> 
> Managed technology for the global legal profession
> 
>  
> 
> This communication (including any attachment(s)) is intended solely
> for the recipient(s) named above and may contain information that is
> confidential, privileged or legally protected. Any unauthorized use
> or dissemination of this communication is strictly prohibited. If
> you have received this communication in error, please immediately
> notify the sender by return e-mail message and delete all copies of
> the original communication to include any copy that may reside in
> your sent box. Thank you for your cooperation.
> 
> 
> ___
> Pulp-list mailing list
> Pulp-list@redhat.com 
> https://www.redhat.com/mailman/listinfo/pulp-list
> 
>  
> 
> This communication (including any attachment(s)) is intended solely for
> the recipient(s) named above and may contain information that is
> confidential, privileged or legally protected. Any unauthorized use or
> dissemination of this communication is strictly prohibited. If you have
> received this communication in error, please immediately notify the
> sender by return e-mail message and delete all copies of the original
> communication to include any copy that may reside in your sent box.
> Thank you for your cooperation.
> 
> 
> ___
> Pulp-list mailing list
> Pulp-list@redhat.com
> https://www.redhat.com/mailman/listinfo/pulp-list
> 

___

Re: [Pulp-list] What to do with Puppet Deployment

[Randy Barlow]

On Tue, Dec 01, 2015 at 11:55:25AM -0500, Sean Myers wrote:
> On 11/30/2015 04:55 PM, Randy Barlow wrote:
> > 1) We could make the repository's README state that it is deprecated,
> > and provide a link to the Katello project.
> 
> I prefer this, more details below.
> 
> …
>
> I think the best possible outcome is to leave all the code available for
> those that might still be using it, make sure the project is clearly
> deprecated, and provide some examples for migrating from the deprecated
> module to the katello module if possible.
> 
> Gaps in functionality between the pulp module and the katello module
> should be identified; if found, those gaps should be tracked as
> enhancement requests on the katello module.

This is also my preference. Does anybody else have any thoughts? Should
we proceed with this plan?

If possible, it may be good to disable pull requests on the repository
as well.

-- 
Randy Barlow
irc:   bowlofeggs
phone: +1-919-890-8150


signature.asc
Description: PGP signature
___
Pulp-list mailing list
Pulp-list@redhat.com
https://www.redhat.com/mailman/listinfo/pulp-list