Submitting a package
I read through the documentation and it's a bit unclear to me how to do this - it seemed like I needed to maintain some work before being approved to be a Maintainer but I'm not sure where to do that. We have a PAM module that we're going to open source in a month or so and I would like to be able to have it in a Debian repo when we do. We are using the attached package for testing (if you build from source) so I figured this was a good place to start. Since I gather that any package will need to be submitted by someone else, I did not sign it (also because I plan to setup another identity for dealing with package submissions). Can someone give feadback as to anything that should be corrected in this package or submit it upstream? libtap_1.03-1.deb Description: application/debian-package
Re: Submitting a package
Hi Shawn! On 10/18/2013 05:54 PM, shawn wilson wrote: Can someone give feadback as to anything that should be corrected in this package or submit it upstream? You might want to start with the Debian New Maintainer' Guide [1]. Basically, what you have to do first is getting to know how packaging in Debian works in general and what standards packages have to adhere to. For example, a package must have a proper Debian copyright file which lists the licenses of all program code components in the package. This is necessary to make it easy for everyone who uses and - more importantly - redistributes the package to know under what terms use and redistribution are possible. The copyright file has to list all copyright holders and account for possible different licenses for different code components (e.g., some code in your package might be GPL-2 while other parts might be covered by the MIT license). Furthermore, the package needs a proper control file which sets a package dependencies, its supported architectures, short and long description, section (for example, sound), distribution (main, contrib or non-free), maintainer name, homepage and so on. There are many other files which go into the debian directory depending on the type of package and there is probably more to say on that that I could fit into such an email. I recommend starting to read some documentation for newbies and trying to get your first proper package built. If you need feedback and help on that, you should resort to the mailing list and IRC channel of Debian Mentors. Cheers, Adrian [1] http://www.debian.org/doc/manuals/maint-guide/ -- .''`. John Paul Adrian Glaubitz : :' : Debian Developer - glaub...@debian.org `. `' Freie Universitaet Berlin - glaub...@physik.fu-berlin.de `-GPG: 62FF 8A75 84E0 2956 9546 0006 7426 3B37 F5B5 F913 -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/526168f1.5040...@physik.fu-berlin.de
Re: Submitting a package
On Fri, Oct 18, 2013 at 12:59 PM, John Paul Adrian Glaubitz glaub...@physik.fu-berlin.de wrote: Hi Shawn! On 10/18/2013 05:54 PM, shawn wilson wrote: Can someone give feadback as to anything that should be corrected in this package or submit it upstream? You might want to start with the Debian New Maintainer' Guide [1]. I forgot to read that doc (saw it mentioned and then forgot) thanks. Basically, what you have to do first is getting to know how packaging in Debian works in general and what standards packages have to adhere to. I think I basically did this in the attached package? For example, a package must have a proper Debian copyright file which lists the licenses of all program code components in the package. This is necessary to make it easy for everyone who uses and - more importantly - redistributes the package to know under what terms use and redistribution are possible. The copyright file has to list all copyright holders and account for possible different licenses for different code components (e.g., some code in your package might be GPL-2 while other parts might be covered by the MIT license). I probably didn't do this :( Though the license is proprietary (basically says 'use at your own risk and don't blame me for damage') so I'm not sure what to call that? Furthermore, the package needs a proper control file which sets a package dependencies, its supported architectures, short and long description, section (for example, sound), distribution (main, contrib or non-free), maintainer name, homepage and so on. Hmmm, I got most of thist. I noticed most fields are optional. I guess every field that can be filled in should There are many other files which go into the debian directory depending on the type of package and there is probably more to say on that that I could fit into such an email. I recommend starting to read some documentation for newbies and trying to get your first proper package built. If you need feedback and help on that, you should resort to the mailing list and IRC channel of Debian Mentors. I noticed there was a #debian-dev channel on freenode that said invite only. Is there another non-invite -dev channel? -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/CAH_OBicYJKh4gcf8MCHK7X6n6kSe4ptmfKPTYQGPc=pkrg3...@mail.gmail.com
Re: Submitting a package
On 10/18/2013 07:12 PM, shawn wilson wrote: Basically, what you have to do first is getting to know how packaging in Debian works in general and what standards packages have to adhere to. I think I basically did this in the attached package? No, I'm afraid not. There are many important things missing. There is no distinct short and long description in the control file, the changelog file does not adhere to Debian's formatting guidelines for changelogs, the Debian copyright file is missing, so is the symbols file and the README.Debian. I would actually have to see your packaging sources for a proper review, I can't really do that on a binary package. It almost looks like you built the package manually!? I probably didn't do this :( Though the license is proprietary (basically says 'use at your own risk and don't blame me for damage') so I'm not sure what to call that? According to the upstream website, libtap is covered by a modified BSD license, see [1]. Furthermore, the package needs a proper control file which sets a package dependencies, its supported architectures, short and long description, section (for example, sound), distribution (main, contrib or non-free), maintainer name, homepage and so on. Hmmm, I got most of thist. I noticed most fields are optional. I guess every field that can be filled in should No, not really. Most of them are mandatory. They might be optional to get a working package, but not one that would get accepted into the official Debian repositories. There are many other files which go into the debian directory depending on the type of package and there is probably more to say on that that I could fit into such an email. I recommend starting to read some documentation for newbies and trying to get your first proper package built. If you need feedback and help on that, you should resort to the mailing list and IRC channel of Debian Mentors. I noticed there was a #debian-dev channel on freenode that said invite only. Is there another non-invite -dev channel? I don't know what #debian-dev on FreeNode is, but most of us are in #debian-devel on OFTC. However, that's not the place to ask. Please seek advise on the Debian Mentors mailing list [2] and the #debian-mentors channel on OFTC. Cheers, Adrian [1] http://www.shlomifish.org/open-source/projects/libtap/ [2] http://lists.debian.org/debian-mentors/ -- .''`. John Paul Adrian Glaubitz : :' : Debian Developer - glaub...@debian.org `. `' Freie Universitaet Berlin - glaub...@physik.fu-berlin.de `-GPG: 62FF 8A75 84E0 2956 9546 0006 7426 3B37 F5B5 F913 -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/52616e6a.7040...@physik.fu-berlin.de
Re: Submitting a package
Thanks On Fri, Oct 18, 2013 at 1:22 PM, John Paul Adrian Glaubitz glaub...@physik.fu-berlin.de wrote: On 10/18/2013 07:12 PM, shawn wilson wrote: Basically, what you have to do first is getting to know how packaging in Debian works in general and what standards packages have to adhere to. I think I basically did this in the attached package? No, I'm afraid not. There are many important things missing. There is no distinct short and long description in the control file, the changelog file does not adhere to Debian's formatting guidelines for changelogs, the Debian copyright file is missing, so is the symbols file and the README.Debian. I would actually have to see your packaging sources for a proper review, I can't really do that on a binary package. It almost looks like you built the package manually!? I probably didn't do this :( Though the license is proprietary (basically says 'use at your own risk and don't blame me for damage') so I'm not sure what to call that? According to the upstream website, libtap is covered by a modified BSD license, see [1]. Furthermore, the package needs a proper control file which sets a package dependencies, its supported architectures, short and long description, section (for example, sound), distribution (main, contrib or non-free), maintainer name, homepage and so on. Hmmm, I got most of thist. I noticed most fields are optional. I guess every field that can be filled in should No, not really. Most of them are mandatory. They might be optional to get a working package, but not one that would get accepted into the official Debian repositories. There are many other files which go into the debian directory depending on the type of package and there is probably more to say on that that I could fit into such an email. I recommend starting to read some documentation for newbies and trying to get your first proper package built. If you need feedback and help on that, you should resort to the mailing list and IRC channel of Debian Mentors. I noticed there was a #debian-dev channel on freenode that said invite only. Is there another non-invite -dev channel? I don't know what #debian-dev on FreeNode is, but most of us are in #debian-devel on OFTC. However, that's not the place to ask. Please seek advise on the Debian Mentors mailing list [2] and the #debian-mentors channel on OFTC. Cheers, Adrian [1] http://www.shlomifish.org/open-source/projects/libtap/ [2] http://lists.debian.org/debian-mentors/ -- .''`. John Paul Adrian Glaubitz : :' : Debian Developer - glaub...@debian.org `. `' Freie Universitaet Berlin - glaub...@physik.fu-berlin.de `-GPG: 62FF 8A75 84E0 2956 9546 0006 7426 3B37 F5B5 F913 -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/cah_obiccr8vbvakxp2mekxafpsb8q24kbtgcwuzrdzeu0z2...@mail.gmail.com
Re: Submitting a package
shawn wilson ag4ve...@gmail.com writes: We have a PAM module that we're going to open source in a month or so and I would like to be able to have it in a Debian repo when we do. As others have said, you should become familiar with the Debian packagemaintainer documentation. Since you are also the developers of the work, you should also follow the Debian Upstream Guide URL:https://wiki.debian.org/UpstreamGuide. -- \ “We demand rigidly defined areas of doubt and uncertainty!” | `\—Vroomfondel, _The Hitch-Hiker's Guide To The Galaxy_, Douglas | _o__)Adams | Ben Finney -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/7wmwm6ghx4@benfinney.id.au
