Bug#706522: Fwd: Bug#706522: ITP: pcs - Pacemaker/Corosync configuration system
Am 17.05.2013 um 09:42 schrieb Hadret had...@gmail.com: On Fri, May 17, 2013 at 09:21:09AM +0200, Martin Gerhard Loschwitz wrote: Filip, Am 17.05.2013 um 09:15 schrieb Filip Chabik had...@gmail.com: in fact, I had already uploaded packages to experimental (I just got a REJECT on them yesterday for some minor things though). This is awesome news (that you already did it, not that it was rejected). I have fingers crossed for this to succeed next time you try. Ya. It really wasn't anything big, but pcsd scares the shit out of me a little bit, esp. because it tries to download something during the build process, which looks rather scary. Oh well. Have you included pcsd? That looked highly broken the last time I looked at it. As far as I saw (I removed packages and my built once you told me, that you already done it), pcsd was included in the packages -- thing is, I had no place to test it out :( Ouch :\ I have actually packaged the ruby gems required for pcsd already. It's just that pcsd looks like something that will blow up every second, so I did not include it in the package I originally uploaded to experimental. Is it the approach suggest for package maintainers? I'm asking cause I wonder whether there's no conflict in installing gems via gem command and APT? Well, the general assumption is: If a package needs a ruby gem, that gem would need to be packaged as a dependency. Installing ruby-gems via postinst is something I would rather not want to do; I don't know if it is even allowed as per policy. The Ruby packages I produced are here: http://people.debian.org/~madkiss/ruby/ I'd be happy if somebody could discuss with the Ruby maintainers how to carry on with this; e.g. would there be any interest at their end to maintain these? Filip Best regards Martin -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#706522: ITP: pcs - Pacemaker/Corosync configuration system
Hello Martin, I have prepared test package, but unfortunately I have no cluster to test it on. If you are interested in playing with it, here's the link: * http://deb.ianod.es/debian/incoming/pcs_0.9.41-1_all.deb Rest of the files are present too, just explore incoming directory if you need them. Things worth noting: * I built latest available on GitHub version. * This packages depends on Pacemaker from experimental branch (currently it's 1.9.1 version). * Package itself is highly experimental too, so it's advised not to use it in production or even development branch. Side notes: * I will push the package to official Debian repositories once it had been tested thoroughly. * I wasn't sure how to handle Ruby gems on which this package depends, so I pushed their installation and uninstallation via postinst and prerm (respectively). I will get in touch with Ruby team to ask for their advise on this one. Kind regards, Filip -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#706522: ITP: pcs - Pacemaker/Corosync configuration system
Filip, Am 17.05.2013 um 09:15 schrieb Filip Chabik had...@gmail.com: Hello Martin, I have prepared test package, but unfortunately I have no cluster to test it on. If you are interested in playing with it, here's the link: * http://deb.ianod.es/debian/incoming/pcs_0.9.41-1_all.deb in fact, I had already uploaded packages to experimental (I just got a REJECT on them yesterday for some minor things though). Rest of the files are present too, just explore incoming directory if you need them. Things worth noting: * I built latest available on GitHub version. * This packages depends on Pacemaker from experimental branch (currently it's 1.9.1 version). * Package itself is highly experimental too, so it's advised not to use it in production or even development branch. Have you included pcsd? That looked highly broken the last time I looked at it. Side notes: * I will push the package to official Debian repositories once it had been tested thoroughly. * I wasn't sure how to handle Ruby gems on which this package depends, so I pushed their installation and uninstallation via postinst and prerm (respectively). I will get in touch with Ruby team to ask for their advise on this one. I have actually packaged the ruby gems required for pcsd already. It's just that pcsd looks like something that will blow up every second, so I did not include it in the package I originally uploaded to experimental. Kind regards, Filip Regards Martin -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#706522: Fwd: Bug#706522: ITP: pcs - Pacemaker/Corosync configuration system
On Fri, May 17, 2013 at 09:21:09AM +0200, Martin Gerhard Loschwitz wrote: Filip, Am 17.05.2013 um 09:15 schrieb Filip Chabik had...@gmail.com: in fact, I had already uploaded packages to experimental (I just got a REJECT on them yesterday for some minor things though). This is awesome news (that you already did it, not that it was rejected). I have fingers crossed for this to succeed next time you try. Have you included pcsd? That looked highly broken the last time I looked at it. As far as I saw (I removed packages and my built once you told me, that you already done it), pcsd was included in the packages -- thing is, I had no place to test it out :( I have actually packaged the ruby gems required for pcsd already. It's just that pcsd looks like something that will blow up every second, so I did not include it in the package I originally uploaded to experimental. Is it the approach suggest for package maintainers? I'm asking cause I wonder whether there's no conflict in installing gems via gem command and APT? Filip -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#706522: ITP: pcs - Pacemaker/Corosync configuration system
Package: wnpp Severity: wishlist Owner: Martin Loschwitz madk...@debian.org * Package name: pcs Version : 0.9.40 Upstream Author : Chris Feist * URL : https://github.com/feist/pcs/ * License : GPLv2 Programming Lang: Python Description : CLI to manipulate Pacemaker/Corosync clusters pcs is a shell-utility to manipulate the current resource configuration of Pacemaker/Corosync clusters. It allows to start and stop and to add and delete resource from the command line and can also set up resources of special kinds such as STONITH. It's an alternative to the CRM shell, which itself is packaged in the crmsh package and was the default shell for Pacemaker up to version 1.1.8. . If you want to configure Pacemaker from the command line without using its internal XML structure, this package will come in handy. -- Martin Gerhard Loschwitz Chief Brand Officer, Principal Consultant hastexo Professional Services CONFIDENTIALITY NOTICE: This e-mail and/or the accompanying documents are privileged and confidential under applicable law. The person who receives this message and who is not the addressee, one of his employees or an agent entitled to hand it over to the addressee, is informed that he may not use, disclose or reproduce the contents thereof. Should you have received this e-mail (or any copy thereof) in error, please let us know by telephone or e-mail without delay and delete the message from your system. Thank you. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
