Doubts in Sigar packaging
Hi all, I'm trying again to package a library called SIGAR [1] because it's a requirement in a free software help to develop called InVesalius [2]. During this trying some doubts occurred: * The Source is in git [3]. I'm not using the last stable version because I wasn't able to compile it. What's the policy to version packages from git? I'm using this way: sigar-1.7.0~git833ca18ecfc1f3f45eaf8544d8cdafef6603772d after git is the commit version I'm using. * This library contains a bunch if bindings, one of them is java. These java bindings is compiled using ant. The compilations generates a bunch of .class and .jar files, and there isn't a make install. What is the best way to put those files in the right directories? To use the cp or mv command? And the right directories I think [4] is this /usr/share/java/libsigar-1.7 ? Thanks to all! PS. We need some help in translations [5] too. [1] - http://support.hyperic.com/display/SIGAR/Home [2] - http://svn.softwarepublico.gov.br/trac/invesalius [3] - http://github.com/hyperic/sigar [4] - http://www.debian.org/doc/packaging-manuals/java-policy/x104.html [5] - http://www.transifex.net/projects/p/invesalius/ -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/1284483082.3140.21.ca...@paraopeba
RFS: matrixssl
Dear mentors, I am looking for a sponsor for my package matrixssl. * Package name: matrixssl Version : 3.1.2-2 Upstream Author : PeerSec Networks, Inc. supp...@peersec.com * URL : http://www.matrixssl.org/ * License : GPL Section : libs It builds these binary packages: libmatrixssl3.1 - small SSL library optimized for embedded systems libmatrixssl3.1-dev - small SSL library optimized for embedded systems (development fil libmatrixssl3.1-doc - small SSL library optimized for embedded systems (documentation) My motivation for maintaining this package is: I started to write a code that needs version 3.1 of matrixssl but the current version at debian it's 1.8.8 which it's too hard to use. Also, I saw that the current maintainer was asking for someone to adopt the package here: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=544057 This it's my second post to the list, I hope that it doesn't disturb anyone else, but I took all the previous advice and start again. The package can be found on mentors.debian.net: - URL: http://mentors.debian.net/debian/pool/main/m/matrixssl - Source repository: deb-src http://mentors.debian.net/debian unstable main contrib non-free - dget http://mentors.debian.net/debian/pool/main/m/matrixssl/matrixssl_3.1.2-2.dsc I would be glad if someone uploaded this package for me. Kind regards Jonathan Gonzalez V. pgphbzqcKVRRp.pgp Description: PGP signature
Re: Doubts in Sigar packaging
On Tue, Sep 14, 2010 at 01:51:22PM -0300, Thiago Franco de Moraes wrote: I'm trying again to package a library called SIGAR [1] because it's a requirement in a free software help to develop called InVesalius [2]. During this trying some doubts occurred: * The Source is in git [3]. I'm not using the last stable version because I wasn't able to compile it. What's the policy to version packages from git? I'm using this way: sigar-1.7.0~git833ca18ecfc1f3f45eaf8544d8cdafef6603772d after git is the commit version I'm using. Yeah, that isn't going to work -- what if the next SHA you want to package is 12345[blah]... it'll look like a lesser version to dpkg. What you need to do is select a monotonically increasing number to work from. I think the most common option is to just take the date of the last commit in the repo and use that, so something like sigar-1.7.0~git20100915. Assuming that you don't want to package two versions from the same day, that should work just fine. You'll want a debian/README.source describing where the git repo is that you got your export from, and how other people can recreate it (or update it), for cleanliness. - Matt -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20100914222129.gs...@hezmatt.org
reprepro signing.
Hi all, I am trying to get repository signing going with reprepro. I have my key built with gpg, Signwith set to yes, Release.gpg gets generated. When I try to test it with apt-get update I receive: W: GPG error: http://software.astronautvista.com karmic Release: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY E58B0D050AB78E99 Release.gpg is definitely available and looks like this: -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.12 (GNU/Linux) iEYEABECAAYFAkyQNHAACgkQ5YsNBQq3jpl1HACeJcKUKD97/+j94iQxEvjwnLh7 Zo8AoJFdmGk7qAdbZcn3ThhDrLNXel0c =FAkr -END PGP SIGNATURE- When I try to apt-key add from the server I receive gpg --keyserver hkp://software.astronautvista.com --recv-keys E58B0D050AB78E99 gpg: requesting key 0AB78E99 from hkp server software.astronautvista.com gpgkeys: HTTP fetch error 7: couldn't connect to host gpg: no valid OpenPGP data found. gpg: Total number processed: 0 I've pored over much documentation but it is extremely sketchy. What is wrong? -- IV -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/aanlkti=vgjbmcucw=k1o4r9t1rvu_ypz_6vgbhswg...@mail.gmail.com
Re: reprepro signing.
Ignacio Valdes ival...@hal-pc.org writes: Hi all, I am trying to get repository signing going with reprepro. I have my key built with gpg, Signwith set to yes, Release.gpg gets generated. When I try to test it with apt-get update I receive: W: GPG error: http://software.astronautvista.com karmic Release: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY E58B0D050AB78E99 You need to mark the public key of the key pair used to sign your repository as trusted. This is outside the scope of reprepro, which only handles the signing. On each client using that repository, you need to somehow arrange for the public key to be installed and added (using apt-key add). When I try to apt-key add from the server I receive gpg --keyserver hkp://software.astronautvista.com --recv-keys E58B0D050AB78E99 gpg: requesting key 0AB78E99 from hkp server software.astronautvista.com gpgkeys: HTTP fetch error 7: couldn't connect to host gpg: no valid OpenPGP data found. gpg: Total number processed: 0 It looks like you're trying to use your Debian archive host as a key server to retrieve the public key. Unless you've explicitly installed and configured a PGP keyserver on your repository server, that isn't going to work; there's nothing on the archive server that speaks the HKP protocol. This isn't something reprepro does. The conventional way to handle this is to build a Debian package that installs the keyring and runs apt-key add, based off of packages like debian-archive-keyring, and then have all clients install that package. This requires a one-time confirmation that you're willing to install a package with an unknown signature. Alternately, you can manually import the public key into each client using apt-key add. How you obtain the public key is up to you in that case. Any trusted path works. -- Russ Allbery (r...@debian.org) http://www.eyrie.org/~eagle/ -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/87ocbzllkf@windlord.stanford.edu
