12 Replies Latest reply: Sep 16, 2010 9:04 AM by tfmoraes RSS

    Debian package

    tfmoraes Hot Shot
      Hi all,

      I'm creating a debian package. To do that I need some informations: The authors and the copyright. Above how the file look like. Thanks!

      This package was debianized by Thiago Franco de Moraes <tfmoraes@cti.gov.br> on
      Wed, 24 Mar 2010 12:54:50 -0300.

      It was downloaded from <http://svn.hyperic.org/projects/sigar_mirror/trunk>

      Upstream Author(s):

          <put author's name and email here>
          <likewise for another author>

      Copyright:

          <Copyright (C) YYYY Name OfAuthor>
          <likewise for another author>

      License:

          <Put the license of the package here indented by 4 spaces>

      The Debian packaging is:

          Copyright (C) 2010 Thiago Franco de Moraes <tfmoraes@cti.gov.br>

      and is licensed under the GPL version 3,
      see `/usr/share/common-licenses/GPL-3'.

      # Please also look if there are files or directories which have a
      # different copyright/license attached and list them here.
        • 1. Re: Debian package
          excowboy Master
          Hi,

          do you want to create a package of the Agent, Server or of SIGAR ?

          Cheers,
          Mirko
          • 2. Re: Debian package
            tfmoraes Hot Shot
            Hi,

            I'm creating a package of SIGAR.
            • 3. Re: Debian package
              dougm_hyperic Expert VMware Employees
              Hi,

              Great to hear you're creating a Debian package for SIGAR.
              We're actually in the process of changing the SIGAR license from GPLv2 to Apache2.  Might be better if you can wait a week or two for that change to happen, just let me know.  Either way, I can get you the info for the package.

              -Doug
              • 4. Re: Debian package
                tfmoraes Hot Shot
                In contact with Debian developers, appeared some doubts. Above our talk:

                > On Tue, Mar 30, 2010 at 10:03:05AM -0400, Michael Hanke wrote:
                > > On Tue, Mar 30, 2010 at 09:41:29AM -0300, Thiago Franco Moraes wrote:
                > > > Michael, Why did you compile the sigar as a static lib? It was because
                > > > a compiling problem?
                > >
                > > No, compiling as a shared library works fine (I tested it, including
                > > linking the bindings against it). However, we cannot ship an unversioned
                > > shared library in Debian.
                >
                > Yes, but in several cases the Debian maintainer "invented" a soversion,
                > mostly 0.0.0 or something like this to enable easy upgrades.
                >
                > > At the same time we cannot use the current
                > > version, since this is an SVN snapshot and we don't know whether
                > > upstream will break API/ABI before the release.
                >
                > Teaching upstream about sonames does not harm - this finally reduces the
                > packaging work later on because you do not need to invent it.

                Upstream knows about versions and they do use them already. However,
                this SVN snapshot still uses the old stable version -- nobody knows how
                often they will break the ABI before they release -- after all this is a
                development snapshot. I only say that we should not step forward with
                shared-lib packaging without coordination and a proper release!

                Thank!
                • 5. Re: Debian package
                  dougm_hyperic Expert VMware Employees
                  I'm missing some context here, also not familiar with the Debian process.  Maybe it would be better for me to join that discussion, can you give me a pointer where-to?

                  As for our versions, see: http://support.hyperic.com/display/SIGAR/Home#Home-versions
                  • 6. Re: Debian package
                    tfmoraes Hot Shot
                    This discussion starts because the libsigar was compiled not as a shared lib (-DBUILD_SHARED_LIBS:BOOL=OFF). It was because the sigar we are packaging is trunk version, not the stable version. See what was said by Michael Hanke:

                    "Upstream knows about versions and they do use them already. However,
                    this SVN snapshot still uses the old stable version -- nobody knows how
                    often they will break the ABI before they release -- after all this is a
                    development snapshot. I only say that we should not step forward with
                    shared-lib packaging without coordination and a proper release!"

                    It's occurring by email. If you want, I could add you.

                    Thanks!
                    • 7. Re: Debian package
                      dougm_hyperic Expert VMware Employees
                      The svn trunk is a mirror of our git master branch, which will become the 1.7.0 stable version.  I would like to get a 1.7.0 release out soon-ish, so just let me know what changes you need and we can make it happen.
                      Is there not a Debian bug/ticket open somewhere with more detail?
                      • 8. Re: Debian package
                        tfmoraes Hot Shot
                        • 9. Re: Debian package
                          tfmoraes Hot Shot
                          Hi,

                          Part of discussion is occurring at debian-mentors list [1], the rest by
                          email.

                          [1] - http://lists.debian.org/debian-mentors/2010/03/msg00438.html
                          • 10. Re: Debian package
                            tfmoraes Hot Shot
                            Hi,

                            I've been trying to package the sigar and all the bindings. The python, ruby, perl and dotnet I have already packaged. The problem now is with erlang, php, java and lua.

                            The java I can compile but I have to set the JAVA_HOME environment, I have to find the better way to do that when packaging.

                            The erlang binding I can compile too, but I have to install the sigar before compile erlang, there is a way to compile erlang without install sigar? I need that to package.

                            The php bindings I don't know how to compile, it doesn't have a makefile. The lua version there is a makefile, but it doesn't compile.

                            To generate the packages. You can, from debian or ubuntu:

                            dget http://dl.dropbox.com/u/817671/packages/sigar_1.7.0%7Esvn5287-1.dsc

                            dpkg-source -x sigar_1.7.0~svn5287-1.dsc

                            Enter in the sigar directory:

                            debuild

                            Then it creates the sigar packages.

                            It's necessary a copyright about the files in the sigar.
                            • 11. Re: Debian package
                              dougm_hyperic Expert VMware Employees
                              Hi,

                              The JAVA_HOME issue has been fixed: http://jira.hyperic.com/browse/SIGAR-214
                              Let me know if that solves the problem for you too.

                              The erlang and lua bindings are quite new and probably not ready for release.
                              To build php, just run 'phpize' in bindings/php to generate the Makefile.
                              However, php and dotnet have not been updated for quite some time.

                              I recommend for now just packaging: java, python, ruby and perl bindings.

                              I will also be bringing the copyright headers up to date in the next couple of days.
                              • 12. Re: Debian package
                                tfmoraes Hot Shot
                                Hi,

                                Some time ago I stopped to package Sigar to Debian but I had to stop because some problems in my job. Now I started again :)

                                I need some help with Java bindings. I have just a few  experience with Java development. I have a question: What are the files necessaries to someone use the java bindings in java develpment? All those .class and .jar?

                                If you want to see how is it going:

                                $ dget http://dl.dropbox.com/u/817671/packages/sigar_1.7.0%7Egit20100907-1.dsc

                                A error about signature will be showed, no problem

                                $ dpkg-source -x sigar_1.7.0%7Egit20100907-1.dsc

                                Then see the debian Folder the files rules and control. If you want to generate the package, out of debian folder:

                                $ debuild

                                Thanks!