Re: [Gluster-devel] Compile problem in mainline 2.5

[Majied Najjar]

Yep.

I have been making debian packages from the get-go, both to facilitate upgrades 
on production machines and for "quick testing" on each repository release.  
There are A LOT of machines that I maintain, and it did not make sense having 
to waste time making sure that when I removed glusterfs, it was actually gone 
before an upgrade (which makes debugging a bit more accurate). :-)

I also maintain my own package of fuse since I use a monolithic kernel and do 
not require a kernel module to be compiled/installed each time. 

Majied




On Fri, 6 Jul 2007 11:28:35 +0200
Steffen Grunewald <address@hidden> wrote:

> On Fri, Jul 06, 2007 at 09:41:01AM +0200, Hans Einar Gautun wrote:
> > Avati,
> > It was automake1.4. I found a note about it googling, and the answer was
> > automake1.9 - and problem solved :).
> 
> Ah, that's why it worked for me, I had to drop am1.4 some time ago 
> because it collided with another package's build dependencies. 
> Please, someone remember this for debian/control Conflicts :-)
> (BTW, anyone else into Debianization of glusterfs?)
> 
> Steffen
> 
> 
> 
> _______________________________________________
> Gluster-devel mailing list
> address@hidden
> http://lists.nongnu.org/mailman/listinfo/gluster-devel