On 02/19/2015 02:30 PM, Niels de Vos wrote:
Hey Pranith!
Thanks for putting this topic on my radar. Uncommunicated packaging
changes have indeed been a pain for non-RPM distributions on several
occasions. We should try to inform other packagers about required
changes in the packaging scripts or upgrade/installation process better.
On Thu, Feb 19, 2015 at 12:26:33PM +0530, Pranith Kumar Karampuri wrote:
https://bugzilla.redhat.com/show_bug.cgi?id=1113778
https://bugzilla.redhat.com/show_bug.cgi?id=1191176
How can we make the process of giving good packages for things other than
RPMs?
My guess is that we need to announce packaging changes very clearly.
Maybe it makes sense to have a very low-traffic packaging@xxxxxxxxxxx
mailinglist where all packagers from all distributions are subscribed?
I've added all packagers that I could track on CC, and am interested in
their preferences and ideas.
Thanks Niels!
First thing we need to get going is to make other packaging infra to
handle gluster upgrades. i.e. On upgrade glusterd needs to be restarted,
first it needs to start with 'upgrade' option 'on' so that it starts
re-generate the configuration files and dies, then 'glusterd' needs to
be started again, normally. How do we get this done in other
distributions if not done already?
Pranith
Thanks,
Niels
_______________________________________________
Gluster-devel mailing list
Gluster-devel@xxxxxxxxxxx
http://www.gluster.org/mailman/listinfo/gluster-devel
