Re: [Ganglia-developers] 3.3.4 tag doesn't build debian packages
On Tue, Apr 03, 2012 at 12:16:42PM -0700, Dave Rawks wrote: Am I missing something? I just downloaded the tarball tagged 3.3.4 from github and attempted to build debian packages from it. 1. The debian changelog is not updated to reflect the version tag. 2. the build dependencies appear to be broken, as the build requires libtools to be installed but that isn't called out in the control file. 3. the build fails when it attempts to descend into the web subdirectory of the build tree. I've been away from this project for a few weeks now and I was under the impression for the traffic on this list that some of the version tagging/workflow questions have been heavily discussed. However it seems that the actual function of the source tree may have become slowly and subtly broken at some point in the recent past (circa 3.2~) At any rate I've not got a lot of time on my hands to fix this at the moment, but figured I'd at least say something in case that might rouse some interest in fixing it. There are 3.3.5 packages available in debian experimental now, and I'll be pushing to sid as soon as I've rolled in some bugfixes and debconf translations. Stu -- From the prompt of Stu Teasdale While my BRAINPAN is being refused service in BURGER KING, Jesuit priests are DATING CAREER DIPLOMATS!! -- Better than sec? Nothing is better than sec when it comes to monitoring Big Data applications. Try Boundary one-second resolution app monitoring today. Free. http://p.sf.net/sfu/Boundary-dev2dev ___ Ganglia-developers mailing list Ganglia-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/ganglia-developers
Re: [Ganglia-developers] 3.3.4 tag doesn't build debian packages
On 04/04/12 10:09, Stu Teasdale wrote: On Tue, Apr 03, 2012 at 12:16:42PM -0700, Dave Rawks wrote: Am I missing something? I just downloaded the tarball tagged 3.3.4 from github and attempted to build debian packages from it. 1. The debian changelog is not updated to reflect the version tag. 2. the build dependencies appear to be broken, as the build requires libtools to be installed but that isn't called out in the control file. 3. the build fails when it attempts to descend into the web subdirectory of the build tree. I've been away from this project for a few weeks now and I was under the impression for the traffic on this list that some of the version tagging/workflow questions have been heavily discussed. However it seems that the actual function of the source tree may have become slowly and subtly broken at some point in the recent past (circa 3.2~) At any rate I've not got a lot of time on my hands to fix this at the moment, but figured I'd at least say something in case that might rouse some interest in fixing it. There are 3.3.5 packages available in debian experimental now, and I'll be pushing to sid as soon as I've rolled in some bugfixes and debconf translations. Just to clarify: are there any bug fixes you had to apply on 3.3.5 that were never required on 3.3.1? In other words, there are no regressions between 3.3.1 and 3.3.5? -- Better than sec? Nothing is better than sec when it comes to monitoring Big Data applications. Try Boundary one-second resolution app monitoring today. Free. http://p.sf.net/sfu/Boundary-dev2dev ___ Ganglia-developers mailing list Ganglia-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/ganglia-developers
Re: [Ganglia-developers] 3.3.4 tag doesn't build debian packages
On Wed, Apr 04, 2012 at 04:59:05PM +0200, Daniel Pocock wrote: Just to clarify: are there any bug fixes you had to apply on 3.3.5 that were never required on 3.3.1? In other words, there are no regressions between 3.3.1 and 3.3.5? All the fixes are to the packaging itself, rather than ganglia, and are present in the current debian unstable release. Stu -- From the prompt of Stu Teasdale There is a Massachusetts law requiring all dogs to have their hind legs tied during the month of April. -- Better than sec? Nothing is better than sec when it comes to monitoring Big Data applications. Try Boundary one-second resolution app monitoring today. Free. http://p.sf.net/sfu/Boundary-dev2dev ___ Ganglia-developers mailing list Ganglia-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/ganglia-developers
[Ganglia-developers] 3.3.4 tag doesn't build debian packages
Hi Stu: I am not too familiar with Debian and Ubuntu packaging but I just wanted make sure you and Jeff are aware of each other's work. Obviously we do not want any duplicated efforts. :) Going forward do you guys have any recommendations on how we can improve the Debian packaging files within our repository such that anybody downloading our official tarballs could build Debian packages out of it? Many thanks! Bernard On Wednesday, April 4, 2012, Stu Teasdale wrote: On Wed, Apr 04, 2012 at 04:59:05PM +0200, Daniel Pocock wrote: Just to clarify: are there any bug fixes you had to apply on 3.3.5 that were never required on 3.3.1? In other words, there are no regressions between 3.3.1 and 3.3.5? All the fixes are to the packaging itself, rather than ganglia, and are present in the current debian unstable release. Stu -- From the prompt of Stu Teasdale There is a Massachusetts law requiring all dogs to have their hind legs tied during the month of April. -- Better than sec? Nothing is better than sec when it comes to monitoring Big Data applications. Try Boundary one-second resolution app monitoring today. Free. http://p.sf.net/sfu/Boundary-dev2dev ___ Ganglia-developers mailing list Ganglia-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/ganglia-developers -- Better than sec? Nothing is better than sec when it comes to monitoring Big Data applications. Try Boundary one-second resolution app monitoring today. Free. http://p.sf.net/sfu/Boundary-dev2dev___ Ganglia-developers mailing list Ganglia-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/ganglia-developers
Re: [Ganglia-developers] 3.3.4 tag doesn't build debian packages
On 04/04/12 17:58, Bernard Li wrote: Hi Stu: I am not too familiar with Debian and Ubuntu packaging but I just wanted make sure you and Jeff are aware of each other's work. Obviously we do not want any duplicated efforts. :) Going forward do you guys have any recommendations on how we can improve the Debian packaging files within our repository such that anybody downloading our official tarballs could build Debian packages out of it? I've actually queried this on the Debian mentors list (on behalf of a number of projects I work with) - you can find some good responses to that question in their list archives for March, in particular: http://wiki.debian.org/UpstreamGuide Summing up the feedback: our primary focus (wearing the Ganglia hat) should be to produce a tarball that is as neutral as possible for all packaging systems. E.g. rather than trying to set CFLAGS stuff within configure, we should leave CFLAGS entirely in the hands of the packager. Second to that, it appears that Debian recommends - NOT keeping a `debian' directory (similar to an RPM spec file) in our `trunk' or `master' branch - NOT distributing such a directory in our tarball The pattern in the Debian world involves keeping a Debian branch, and only that branch has the debian/ directory. In many cases, the Debian branch is not even in the upstream repository: it is in a separate repository (e.g. on the Debian server alioth) -- Better than sec? Nothing is better than sec when it comes to monitoring Big Data applications. Try Boundary one-second resolution app monitoring today. Free. http://p.sf.net/sfu/Boundary-dev2dev ___ Ganglia-developers mailing list Ganglia-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/ganglia-developers
Re: [Ganglia-developers] 3.3.4 tag doesn't build debian packages
On Wed, Apr 04, 2012 at 07:00:46PM +0200, Daniel Pocock wrote: I've actually queried this on the Debian mentors list (on behalf of a number of projects I work with) - you can find some good responses to that question in their list archives for March, in particular: http://wiki.debian.org/UpstreamGuide Summing up the feedback: our primary focus (wearing the Ganglia hat) should be to produce a tarball that is as neutral as possible for all packaging systems. E.g. rather than trying to set CFLAGS stuff within configure, we should leave CFLAGS entirely in the hands of the packager. Second to that, it appears that Debian recommends - NOT keeping a `debian' directory (similar to an RPM spec file) in our `trunk' or `master' branch - NOT distributing such a directory in our tarball The pattern in the Debian world involves keeping a Debian branch, and only that branch has the debian/ directory. In many cases, the Debian branch is not even in the upstream repository: it is in a separate repository (e.g. on the Debian server alioth) Indeed, the other key thing is that the repo on alioth only ever gets 'release' versions of ganglia imported into it, to hopefully avoid any bootstrap issues. I've been rather bad recently with my maintaining of the debian package, but hopefully I'm going to be able to keep it more p to date, especially with Daniel's help. 3.3.5-1 is now available in experimental, and I could potentially make backports of it to squeeze available if there's interest, otherwise the source packages should build fairly cleanly on squeeze and perhaps even lenny. Stu -- From the prompt of Stu Teasdale Even if you can deceive people about a product through misleading statements, sooner or later the product will speak for itself. -- Hajime Karatsu -- Better than sec? Nothing is better than sec when it comes to monitoring Big Data applications. Try Boundary one-second resolution app monitoring today. Free. http://p.sf.net/sfu/Boundary-dev2dev ___ Ganglia-developers mailing list Ganglia-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/ganglia-developers
[Ganglia-developers] 3.3.4 tag doesn't build debian packages
Am I missing something? I just downloaded the tarball tagged 3.3.4 from github and attempted to build debian packages from it. 1. The debian changelog is not updated to reflect the version tag. 2. the build dependencies appear to be broken, as the build requires libtools to be installed but that isn't called out in the control file. 3. the build fails when it attempts to descend into the web subdirectory of the build tree. I've been away from this project for a few weeks now and I was under the impression for the traffic on this list that some of the version tagging/workflow questions have been heavily discussed. However it seems that the actual function of the source tree may have become slowly and subtly broken at some point in the recent past (circa 3.2~) At any rate I've not got a lot of time on my hands to fix this at the moment, but figured I'd at least say something in case that might rouse some interest in fixing it. -Dave -- Better than sec? Nothing is better than sec when it comes to monitoring Big Data applications. Try Boundary one-second resolution app monitoring today. Free. http://p.sf.net/sfu/Boundary-dev2dev ___ Ganglia-developers mailing list Ganglia-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/ganglia-developers
Re: [Ganglia-developers] 3.3.4 tag doesn't build debian packages
On Tue, Apr 3, 2012 at 3:16 PM, Dave Rawks d...@pandora.com wrote: Am I missing something? I just downloaded the tarball tagged 3.3.4 from github and attempted to build debian packages from it. 1. The debian changelog is not updated to reflect the version tag. 2. the build dependencies appear to be broken, as the build requires libtools to be installed but that isn't called out in the control file. 3. the build fails when it attempts to descend into the web subdirectory of the build tree. I've been away from this project for a few weeks now and I was under the impression for the traffic on this list that some of the version tagging/workflow questions have been heavily discussed. However it seems that the actual function of the source tree may have become slowly and subtly broken at some point in the recent past (circa 3.2~) At any rate I've not got a lot of time on my hands to fix this at the moment, but figured I'd at least say something in case that might rouse some interest in fixing it. I had been building snapshot packages for the Ubuntu PPA: https://launchpad.net/~rufustfirefly/+archive/ganglia Source files for successful build: https://launchpad.net/~rufustfirefly/+archive/ganglia/+files/ganglia_3.3.5.orig.tar.gz https://launchpad.net/~rufustfirefly/+archive/ganglia/+files/ganglia_3.3.5-1~oneiric.debian.tar.gz https://launchpad.net/~rufustfirefly/+archive/ganglia/+files/ganglia_3.3.5-1~oneiric.dsc I hope that helps! Jeff -- Better than sec? Nothing is better than sec when it comes to monitoring Big Data applications. Try Boundary one-second resolution app monitoring today. Free. http://p.sf.net/sfu/Boundary-dev2dev ___ Ganglia-developers mailing list Ganglia-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/ganglia-developers
