[Gluster-devel] How can we prevent GlusterFS packaging installation/update issues in future?

Niels de Vos ndevos at redhat.com
Thu Feb 19 10:55:41 UTC 2015

On Thu, Feb 19, 2015 at 03:45:41PM +0530, Lalatendu Mohanty wrote:
> 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.
> +1
> >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 at gluster.org
> >mailinglist where all packagers from all distributions are subscribed?
> +1 for announce packaging changes very clearly.
> But I think we should keep using gluster-devel ML for packaging discussions
> as IMO it is the right platform to get all developers and packagers
> together. However We need to discuss these stuff clearly which we lacked
> before.

My idea was to reduce the number of emails that packagers receive. Not
all packagers are active as a Gluster developer, and the -devel list has
quite some traffic. I am afraid that important changes would get lost in
the noise.


> Thanks,
> Lala
> >I've added all packagers that I could track on CC, and am interested in
> >their preferences and ideas.
> >
> >Thanks,
> >Niels

More information about the Gluster-devel mailing list