variable path names in manpages
Hi, I'm currently writing a manpage which is to be used in a Debian package, but not exclusively. To be most flexible I want to use variables for path names that are expanded at build time. Is there any standard or recommended way implement this? -- Manfred Wassmann PGP and GnuPG public keys available at http://germany.keyserver.net PGP: 24B81049 Fingerprint: D7 10 EE 2B 74 16 C0 64 B4 5F BA B2 90 29 3D AF GPG: 6B299971 Fingerprint: A598 A41F 57A3 5D69 83D2 8027 1274 F8CD 6B29 9971 +++ I18N ? For international language set LANG=POSIX +++ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: variable path names in manpages
Hi Manfred! You wrote: I'm currently writing a manpage which is to be used in a Debian package, but not exclusively. To be most flexible I want to use variables for path names that are expanded at build time. Is there any standard or recommended way implement this? Well, you could just run sed over the man page before installing it. -- Kind regards, +---+ | Bas Zoetekouw | Si l'on sait exactement ce | || que l'on va faire, a quoi| | [EMAIL PROTECTED] | bon le faire?| |[EMAIL PROTECTED] | Pablo Picasso | +---+ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: variable path names in manpages
On Thu, 10 May 2001, Manfred Wassmann wrote: I'm currently writing a manpage which is to be used in a Debian package, but not exclusively. To be most flexible I want to use variables for path names that are expanded at build time. Is there any standard or recommended way implement this? If you're using autoconf, you can have a prog.1.in file that you can have configure process just like all those Makefile.in files to generate a prog.1 along with the Makefiles. (wine uses this technique) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: How to locally sign a package that has been built on another machine?
Marc Haber [EMAIL PROTECTED] writes: Do I need to install non-free software if I want to sign packages on potato? Neither gpg (with or without RSA) nor the RSA module are non-DFSG, today, even if one is still sitting in non-free. Anyway, unless your key is RSA, you don't need the module for signing. Maybe removing a stray load-extension rsa is enough? Since there is no /usr/lib/gnupg/rsa in unstable, would backporting the unstable gnupg to potato solve this? Yes, sid's gnupg includes RSA. -- Robbe signature.ng
Re: How to locally sign a package that has been built on another machine?
Robert Bihlmeyer [EMAIL PROTECTED] writes: Since there is no /usr/lib/gnupg/rsa in unstable, would backporting the unstable gnupg to potato solve this? Yes, sid's gnupg includes RSA. Err, huh? potato (2.2r3 at least) has gnupg 1.0.4-1 which includes RSA. -- James -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
My First Package. Wheee.
Howdy ya'll ;-) I've finished packaging my first package for inclusion in Debian now that I finally got accepted as a maintainer. It's XDrawChem, a linux version of ChemDraw, a fairly necessary app for chemistry folks (at least so my girlfriend tells me, and she's a chemistry major here at Tech). I read through the docs and such (NMU docs, packaging-manual, and so forth), and I was wondering how I should handle: a) inclusion in the testing distribution, if still possible b) inclusion in the unstable distribution, if still possible c) uploading using dupload and scp I don't want to screw up uploading and finishing my first package, purely as a matter of pride, so can you folks walk me through this if possible? I've right now got the i386 binary package and the source package built. Currently, the files are: xdrawchem_0.85-1.dsc xdrawchem_0.85-1_i386.changes xdrawchem_0.85-1_i386.deb xdrawchem_0.85-1.diff.gz xdrawchem_0.85.orig.tar.gz Eg, an example commandline for the upload using dupload and scp, and a briefer on what special stuff needs to be done for testing/unstable? Thanks! ~Warren -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: My First Package. Wheee.
In Warren Anthony Stramiello's email, 10-05-2001: Howdy ya'll ;-) I've finished packaging my first package for inclusion in Debian now that I finally got accepted as a maintainer. It's XDrawChem, a linux version of ChemDraw, a fairly necessary app for chemistry folks (at least so my girlfriend tells me, and she's a chemistry major here at Tech). I read through the docs and such (NMU docs, packaging-manual, and so forth), and I was wondering how I should handle: a) inclusion in the testing distribution, if still possible b) inclusion in the unstable distribution, if still possible c) uploading using dupload and scp I don't want to screw up uploading and finishing my first package, purely as a matter of pride, so can you folks walk me through this if possible? I've right now got the i386 binary package and the source package built. Currently, the files are: xdrawchem_0.85-1.dsc xdrawchem_0.85-1_i386.changes xdrawchem_0.85-1_i386.deb xdrawchem_0.85-1.diff.gz xdrawchem_0.85.orig.tar.gz Eg, an example commandline for the upload using dupload and scp, and a briefer on what special stuff needs to be done for testing/unstable? Thanks! ~Warren -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED] Ohh.. cool - I've been looking for a software program to do something like this for a while for our labs.. to get it in the unstable, just put unstable in the control file. (it's probably in there already).. Then when you upload, it will get put in the queue and installed into unstable with the next dinstall. Inclusion in testing is automatic for unstable packages after the package is not active in unstable and it's dependencies are already in testing.. you shouldn't have to do anything. for uploading, many people use dput nowadays - the command line is fairly simple usually - just `dput xdrawchem_0.85-1_i386.changes` in your case. It'll ask you for your ssh passphrase if you have one.. or your password if you don't have a key on the server (see documentation @ http://db.debian.org/password.html on how to get a ssh key available to all the servers at once).. the developers reference section 6 covers package uploads, but doesn't cover the dput method right now.. hope these answer your questions. I'm a fairly new maintainer as well, so anyone please correct me if i'm wrong here. -- Michael Janssen - Jamuraa - [EMAIL PROTECTED] - [EMAIL PROTECTED] GPG Fingerprint: 87F1 92C4 44AA 4105 B1C4 EDEC D995 9620 C00E 9159 PGP signature
Re: Creating man pages (upstream does not have one)
When you use debmake (the first thing you run on the clean source dir, if I'm not mistaken), it will create the debian directory. Check in there for a manpage.1.ex file that serves as a good template for the process. ~Warren -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Creating man pages (upstream does not have one)
Eduardo Trapani wrote: The software I am packaging does not have a man page. What programs should I use to create one? I usually just edit one directly (in roff). I'm pretty sure dh_make installs a sample. If it doesn't, look at /usr/share/debhelper/dh_make/debian/manpage.1.ex There's also /usr/share/doc/man-db/examples/manpage.example Peter -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Creating man pages (upstream does not have one)
Eduardo Trapani [EMAIL PROTECTED] writes: The software I am packaging does not have a man page. What programs should I use to create one? Try using help2man to get a good template, and edit it by hand. Falk -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Creating man pages (upstream does not have one)
hi, On Thu, May 10, 2001 at 03:52:30PM -0300, Eduardo Trapani wrote: What programs should I use to create one? the normal groff and the an macro (on the commandline that's the -man ;)) ... read the manpage howto as a start and also read man 7 man ... so long Othmar -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Creating man pages (upstream does not have one)
En réponse à Eduardo Trapani [EMAIL PROTECTED]: The software I am packaging does not have a man page. What programs should I use to create one? I would recommend to write them in the POD (Plain Old Documentation) format which makes it very seasy to write/update a man page. (see http://qa.debian.org/man-pages.html for pointers to documentations). I would NOT recommend to use the native manpage format (nroff) nor the DocBook SGML format since writing a manpage with them is rather respectively confusing/painful, IMHO. Jérôme. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Creating man pages (upstream does not have one)
hi, On Thu, May 10, 2001 at 09:42:51PM +0200, Jérôme Marant wrote: I would recommend to write them in the POD (Plain Old Documentation) format which makes it very seasy to write/update a man page. (see http://qa.debian.org/man-pages.html for pointers to documentations). haven't dealt with it but i saw some examples and wasn't that conviced ... I would NOT recommend to use the native manpage format (nroff) nor the DocBook SGML format since writing a manpage with them is rather respectively confusing/painful, IMHO. plain wrong ... nroff is not hard or something like that, read the manpage howto and you know how to do it and there is also plenty of stuff about it lying around ... and i did a rather lengthy manpage with the an macro package and it was all but not a pain ... if *roff is a pain why do people use latex, eh? ... anyway, i don't consider it difficult, just different ... and an easy manpage is written in a few minutes. so long Othmar -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Creating man pages (upstream does not have one)
Y el jueves 10 de mayo, Eduardo Trapani escribió: The software I am packaging does not have a man page. What programs should I use to create one? Thanks, Eduardo. My suggestion: Use perldoc, you will write a txt file like this and you will get a pretty manpage with only one command: glade manpage source [only some lines]: - cut --- =head1 NAME glade - Rapid Development Application tool using Gtk+/Gnome libraries. =head1 SYNOPSIS glade [OPTION...] =head1 DESCRIPTION Glade is an application for creating graphical user interfaces that use the Gtk+ and GNOME libraries. Glade allows you to rapidly develope these interfaces, and can create source code in a variety of languages that will construct the interfaces for you. Glade can also be used in conjunction with libglade to dynamically create user interfaces from the XML description file that Glade creates. =head1 OPTIONS =over 4 =item B--disable-sound Disable sound server use. =back =head1 FILES =head2 The Glade XML File Format TheGlade XML file format is used when saving and loading projects in Glade. This format is also intended to be read by programs which convert it into source code in various languages. =head1 CAVEATS Here are some notes about problems which may be encountered when using Glade. =over 4 =item Some properties can not be set Some properties which can only be set when a widget is created or before it is realized. e.g. window - wmclass, wmname image - type visual (mentioned above) clist/ctree - number of columns =back =head1 SEE ALSO To obtain more information about Glade please visit Lhttp://glade.gnome.org. =head1 COPYRIGHT This package is free software; you can redistribute it and/or modify it under the terms of the GNU General Public License as published by the Free Software Foundation; version 2 dated June, 1991. =head1 AUTHORS Damon Chaplin [EMAIL PROTECTED] Martijn van Beers [EMAIL PROTECTED] - cut --- command to obtain glade.1: pod2man -r '' -c '' glade.podglade.1 HTH Saludos -- O / O O O O O / O / O / O / O Luis Arocha, Data \__|/|__|__|__|/ \__|/__|/__|/__|/|/ larocha at wanadoo.es \\ \ \ \ Islas Canarias \\ \ \ \ Spain PGP signature
Re: How to locally sign a package that has been built on another machine?
On 10 May 2001 14:58:35 +0200, Robert Bihlmeyer [EMAIL PROTECTED] wrote: Maybe removing a stray load-extension rsa is enough? Yes. Thanks. Greetings Marc -- -- !! No courtesy copies, please !! - Marc Haber |Questions are the | Mailadresse im Header Karlsruhe, Germany | Beginning of Wisdom | Fon: *49 721 966 32 15 Nordisch by Nature | Lt. Worf, TNG Rightful Heir | Fax: *49 721 966 31 29 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Override problem, help me please
Hello, I uploaded a new revision of my packeg hptalx and I'd just received the following message from [EMAIL PROTECTED] which I don't understand: -- There are disparities between your recently installed upload and the override file for the following file(s): hptalx_1.1.0-2_i386.deb: priority is overridden from optional to extra. Either the package or the override file is incorrect. If you think the override is correct and the package wrong please fix the package so that this disparity is fixed in the next upload. If you feel the override is incorrect then please reply to this mail and explain why. -- I look at the control file and see Priority: optional, what do they mind with priority is overridden from optional to extra?. Thank you. -- Javier Viñuales Gutiérrez [EMAIL PROTECTED] [EMAIL PROTECTED] GnuPG public information: pub 1024D/4EB82468 1C2A 0241 D350 B43D E027 4FCD F8E8 3454 4EB8 2468 PGP signature
Re: [users] Re: Where's lame
On Wed, May 09, 2001 at 08:43:46AM -0500, Christian T. Steigies wrote: [...] It can be debianised, but it can't be included in debian, since it can't be legally redistributed in binary form. What do you mean ?? There are lots of packages included in debian in source form ... Why don't you read the webpage??? Why does everything have to be exlained again and again when somebody made the effort and explained it on a webpage? wnpp ist the first page you should look at when you want to package something. And its been there for ages, not really hard to find. I wasn't referring to lame, i was just answering the above-mentioned assertion : it can't be included in debian, since it can't be legally redistributed in binary :form. First part of the sentence might be correct, but not for *that* reason. -- Eric VAN BUGGENHAUT [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: variable path names in manpages
On Thu, 10 May 2001, Ove Kaaven wrote: On Thu, 10 May 2001, Manfred Wassmann wrote: I'm currently writing a manpage which is to be used in a Debian package, but not exclusively. To be most flexible I want to use variables for path names that are expanded at build time. Is there any standard or recommended way implement this? If you're using autoconf, you can have a prog.1.in file that you can have configure process just like all those Makefile.in files to generate a prog.1 along with the Makefiles. (wine uses this technique) Thanks. Though autoconf isn't used it can't hurt to be compatible :-) -- Manfred Wassmann PGP and GnuPG public keys available at http://germany.keyserver.net PGP: 24B81049 Fingerprint: D7 10 EE 2B 74 16 C0 64 B4 5F BA B2 90 29 3D AF GPG: 6B299971 Fingerprint: A598 A41F 57A3 5D69 83D2 8027 1274 F8CD 6B29 9971 +++ I18N ? For international language set LANG=POSIX +++ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
perl modules - building debs
After several hours attempting to build debian packages for perl modules and twenty minutes searching google for helpful documentation, I have come to the conclusion that I have no frelling idea what I am doing. =) I read that there is a perl module that would build a package from any module on cpan. I also read something about dh_make_perl, although I can not find anything like that on my system. What is the best way to approach this issue? Are there any FAQs/HOWTOs which explain this process? Any informative replies will be appreciated, rtfms will be tolerated. =) Cheers! -- Derek E. Mart Marticus - Systems Programmer II U of L - Electrical Computer Engineering The Marticus Project - http://www.marticus.org/ 1514 3659 D057 D10C 6BE6 3E68 15BE B181 2F1F 510B PGP signature
Re: [users] Re: Where's lame
Eric == Eric Van Buggenhaut [EMAIL PROTECTED] writes: Eric : it can't be included in debian, since it can't be legally Eric redistributed in binary form. Eric First part of the sentence might be correct, but not for *that* reason. Any package that cannot be distributed in the binary form, or any that otherwise fails to meet the DFSG, cannot be a part of Debian. Refer to the social contract for details. manoj -- By night an atheist half believes a God. -- Edward Young Manoj Srivastava [EMAIL PROTECTED] http://www.debian.org/%7Esrivasta/ 1024R/C7261095 print CB D9 F4 12 68 07 E4 05 CC 2D 27 12 1D F5 E8 6E 1024D/BF24424C print 4966 F272 D093 B493 410B 924B 21BA DABB BF24 424C -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: USA crypto rules and libssl-dependent packages
On Thu, May 10, 2001 at 07:27:44PM -0400, Jimmy Kaplowitz wrote: Hi. I am a novice Debian package maintainer, in the queue for becoming an official developer. I am maintaining a package called althea, which is an IMAP email client for GTK+. They have recently added support for SSL through linking to libssl (from OpenSSL). This is configurable based on the values of a couple variables in the Makefile. I have a couple of questions: 1) I live in the US. Therefore, do I have to send a BXA notification to the government (I believe license exception TSU is applicable - correct me if I'm wrong)? You may. Since it's easy, you probablys hould. Also, do I have to do their thing that they mention on their website about sending a message to the ENC Classification Review Coordinator (or, something like that) in addition to [EMAIL PROTECTED], and if so, how do I do that? I think the email to [EMAIL PROTECTED] is sufficient. Also, is a BXA notification form sufficient to export binary .debs linked with libssl? Yes. Would anyone be able to export them, including other US mirror sites, so long as I provide an export of the same stuff that I notify the BXA about? Probably. It's my theory that the software is no longer export restricted once you make the BXA notification. Thus Debian's requirement that export restricted software get uploaded to non-us doesn't apply. Indeed, this is how Netscape with strong crypto got uploaded to non-free instead of non-us/non-free. There's currently an inquiry going on that will determine if Debian's policy can be updated to clearly reflect the new regulations. 2) Do the binary .debs go in non-US? Yes. Policy currently requires it. What about the Debian source files? Same. If I make additional non-ssl .debs from the same source, would they be in non-US or not? Yes, but only if the source actually contains crypto. Source or binary, policy currently requires export restricted software to be uploaded to non-us. [other stuff omitted] Good luck :) -- Brian Ristuccia [EMAIL PROTECTED] [EMAIL PROTECTED] PGP signature
USA crypto rules and libssl-dependent packages
Hi. I am a novice Debian package maintainer, in the queue for becoming an official developer. I am maintaining a package called althea, which is an IMAP email client for GTK+. They have recently added support for SSL through linking to libssl (from OpenSSL). This is configurable based on the values of a couple variables in the Makefile. I have a couple of questions: 1) I live in the US. Therefore, do I have to send a BXA notification to the government (I believe license exception TSU is applicable - correct me if I'm wrong)? Also, do I have to do their thing that they mention on their website about sending a message to the ENC Classification Review Coordinator (or, something like that) in addition to [EMAIL PROTECTED], and if so, how do I do that? Also, is a BXA notification form sufficient to export binary .debs linked with libssl? Would anyone be able to export them, including other US mirror sites, so long as I provide an export of the same stuff that I notify the BXA about? 2) Do the binary .debs go in non-US? What about the Debian source files? If I make additional non-ssl .debs from the same source, would they be in non-US or not? Also, to the people on -mentors, how would I do this? (I am somewhat new to Debian packages.) I know this is a big message, but I very much appreciate any replies that you would be kind enough to give. Please CC on your replies; I am not subscribed to -legal (though I just got through reading your riveting discussion regarding Sergio Brandano's request on the archives :), and even though I am subscribed to -mentors, that mail gets ferreted away by procmail into a separate box and I would like to see this thread in my main inbox. Thank you all. - Jimmy Kaplowitz [EMAIL PROTECTED] - soon, hopefully, [EMAIL PROTECTED] :-) PGP signature
Re: How to locally sign a package that has been built on another machine?
On Mon, 7 May 2001 21:49:12 +0200, Filip Van Raemdonck [EMAIL PROTECTED] wrote: The tools available for automatic changes signing seem to do this for you. Yes, they do. Judging from the debsign source, this is a gpg issue. However, debsign fails for me because gpg returns some strange error codes: |[EMAIL PROTECTED]/523]:~/tmp$ ( cat run_0.9.2-6.dsc ; echo ) | gpg |--local-user Marc Haber [EMAIL PROTECTED] |--clearsign --armor --textmode --output - - run_0.9.2-6.dsc.asc |gpg: /usr/lib/gnupg/rsa: error loading extension: /usr/lib/gnupg/rsa: |cannot open shared object file: No such file or directory | |You need a passphrase to unlock the secret key for |user: Marc Haber [EMAIL PROTECTED] |1024-bit DSA key, ID 6BBA3C84, created 2000-02-15 | |passphrase is overwritten after pressing enter |[EMAIL PROTECTED]/524]:~/tmp$ echo $? |2 Is the return code 2 the result of rsa missing? Do I need to install non-free software if I want to sign packages on potato? Since there is no /usr/lib/gnupg/rsa in unstable, would backporting the unstable gnupg to potato solve this? Or is something else going wrong? Greetings Marc -- -- !! No courtesy copies, please !! - Marc Haber |Questions are the | Mailadresse im Header Karlsruhe, Germany | Beginning of Wisdom | Fon: *49 721 966 32 15 Nordisch by Nature | Lt. Worf, TNG Rightful Heir | Fax: *49 721 966 31 29
variable path names in manpages
Hi, I'm currently writing a manpage which is to be used in a Debian package, but not exclusively. To be most flexible I want to use variables for path names that are expanded at build time. Is there any standard or recommended way implement this? -- Manfred Wassmann PGP and GnuPG public keys available at http://germany.keyserver.net PGP: 24B81049 Fingerprint: D7 10 EE 2B 74 16 C0 64 B4 5F BA B2 90 29 3D AF GPG: 6B299971 Fingerprint: A598 A41F 57A3 5D69 83D2 8027 1274 F8CD 6B29 9971 +++ I18N ? For international language set LANG=POSIX +++
Re: variable path names in manpages
Hi Manfred! You wrote: I'm currently writing a manpage which is to be used in a Debian package, but not exclusively. To be most flexible I want to use variables for path names that are expanded at build time. Is there any standard or recommended way implement this? Well, you could just run sed over the man page before installing it. -- Kind regards, +---+ | Bas Zoetekouw | Si l'on sait exactement ce | || que l'on va faire, a quoi| | [EMAIL PROTECTED] | bon le faire?| |[EMAIL PROTECTED] | Pablo Picasso | +---+
Re: variable path names in manpages
On Thu, 10 May 2001, Manfred Wassmann wrote: I'm currently writing a manpage which is to be used in a Debian package, but not exclusively. To be most flexible I want to use variables for path names that are expanded at build time. Is there any standard or recommended way implement this? If you're using autoconf, you can have a prog.1.in file that you can have configure process just like all those Makefile.in files to generate a prog.1 along with the Makefiles. (wine uses this technique)
Re: How to locally sign a package that has been built on another machine?
Marc Haber [EMAIL PROTECTED] writes: Do I need to install non-free software if I want to sign packages on potato? Neither gpg (with or without RSA) nor the RSA module are non-DFSG, today, even if one is still sitting in non-free. Anyway, unless your key is RSA, you don't need the module for signing. Maybe removing a stray load-extension rsa is enough? Since there is no /usr/lib/gnupg/rsa in unstable, would backporting the unstable gnupg to potato solve this? Yes, sid's gnupg includes RSA. -- Robbe signature.ng Description: PGP signature
Re: How to locally sign a package that has been built on another machine?
Robert Bihlmeyer [EMAIL PROTECTED] writes: Since there is no /usr/lib/gnupg/rsa in unstable, would backporting the unstable gnupg to potato solve this? Yes, sid's gnupg includes RSA. Err, huh? potato (2.2r3 at least) has gnupg 1.0.4-1 which includes RSA. -- James
My First Package. Wheee.
Howdy ya'll ;-) I've finished packaging my first package for inclusion in Debian now that I finally got accepted as a maintainer. It's XDrawChem, a linux version of ChemDraw, a fairly necessary app for chemistry folks (at least so my girlfriend tells me, and she's a chemistry major here at Tech). I read through the docs and such (NMU docs, packaging-manual, and so forth), and I was wondering how I should handle: a) inclusion in the testing distribution, if still possible b) inclusion in the unstable distribution, if still possible c) uploading using dupload and scp I don't want to screw up uploading and finishing my first package, purely as a matter of pride, so can you folks walk me through this if possible? I've right now got the i386 binary package and the source package built. Currently, the files are: xdrawchem_0.85-1.dsc xdrawchem_0.85-1_i386.changes xdrawchem_0.85-1_i386.deb xdrawchem_0.85-1.diff.gz xdrawchem_0.85.orig.tar.gz Eg, an example commandline for the upload using dupload and scp, and a briefer on what special stuff needs to be done for testing/unstable? Thanks! ~Warren
Re: My First Package. Wheee.
In Warren Anthony Stramiello's email, 10-05-2001: Howdy ya'll ;-) I've finished packaging my first package for inclusion in Debian now that I finally got accepted as a maintainer. It's XDrawChem, a linux version of ChemDraw, a fairly necessary app for chemistry folks (at least so my girlfriend tells me, and she's a chemistry major here at Tech). I read through the docs and such (NMU docs, packaging-manual, and so forth), and I was wondering how I should handle: a) inclusion in the testing distribution, if still possible b) inclusion in the unstable distribution, if still possible c) uploading using dupload and scp I don't want to screw up uploading and finishing my first package, purely as a matter of pride, so can you folks walk me through this if possible? I've right now got the i386 binary package and the source package built. Currently, the files are: xdrawchem_0.85-1.dsc xdrawchem_0.85-1_i386.changes xdrawchem_0.85-1_i386.deb xdrawchem_0.85-1.diff.gz xdrawchem_0.85.orig.tar.gz Eg, an example commandline for the upload using dupload and scp, and a briefer on what special stuff needs to be done for testing/unstable? Thanks! ~Warren -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED] Ohh.. cool - I've been looking for a software program to do something like this for a while for our labs.. to get it in the unstable, just put unstable in the control file. (it's probably in there already).. Then when you upload, it will get put in the queue and installed into unstable with the next dinstall. Inclusion in testing is automatic for unstable packages after the package is not active in unstable and it's dependencies are already in testing.. you shouldn't have to do anything. for uploading, many people use dput nowadays - the command line is fairly simple usually - just `dput xdrawchem_0.85-1_i386.changes` in your case. It'll ask you for your ssh passphrase if you have one.. or your password if you don't have a key on the server (see documentation @ http://db.debian.org/password.html on how to get a ssh key available to all the servers at once).. the developers reference section 6 covers package uploads, but doesn't cover the dput method right now.. hope these answer your questions. I'm a fairly new maintainer as well, so anyone please correct me if i'm wrong here. -- Michael Janssen - Jamuraa - [EMAIL PROTECTED] - [EMAIL PROTECTED] GPG Fingerprint: 87F1 92C4 44AA 4105 B1C4 EDEC D995 9620 C00E 9159 pgpTyTI7VaiPm.pgp Description: PGP signature
Re: My First Package. Wheee.
* Warren Anthony Stramiello
| a) inclusion in the testing distribution, if still possible
Is handled automagically, if you haven't screwed up anything ;) (that
is, it goes into testing after 10 days of testing in unstable, unless
it has RC bugs, that is). Read more at http://ftp-master.debian.org/testing/
| b) inclusion in the unstable distribution, if still possible
That's were we all upload to.
| c) uploading using dupload and scp
Add something like
package config;
$cfg{'ftp-master'} = {
fqdn = ftp-master.debian.org,
login = getlogin() || $ENV{USER} || $ENV{LOGNAME},
incoming = /org/ftp.debian.org/incoming/,
mailto = [EMAIL PROTECTED], # stable
mailtx = [EMAIL PROTECTED], # unstable, exper.
visibleuser = getlogin() || $ENV{USER} || $ENV{LOGNAME},
visiblename = ,
fullname = ,
# The dinstall on master now sends announcement itself. May 1999.
dinstall_runs = 1,
method = scpb
};
$default_host = ftp-master;
1;
to ~/.dupload.conf
and run
dupload xdrawchem_0.85-1_i386.changes
The changelog decides whether it goes into stable or unstable. Unless
you have _very_ good reasons for it going into stable, it should go
into unstable. Very good reasons include security holes and that the
package as it is in stable is totally unuseable.
Be sure to run lintian on your package before uploading it, though. :)
--
Tollef Fog Heen
Unix _IS_ user friendly... It's just selective about who its friends are.
Creating man pages (upstream does not have one)
The software I am packaging does not have a man page. What programs should I use to create one? Thanks, Eduardo.
Re: Creating man pages (upstream does not have one)
When you use debmake (the first thing you run on the clean source dir, if I'm not mistaken), it will create the debian directory. Check in there for a manpage.1.ex file that serves as a good template for the process. ~Warren
Re: Creating man pages (upstream does not have one)
On Thu, May 10, 2001 at 03:52:30PM -0300, Eduardo Trapani wrote: The software I am packaging does not have a man page. What programs should I use to create one? the best, but definitely not the easiest one, is to just get an example page and edit it by hand. there are programs like manedit for X that you can use. of you can use other tools to create one. SGML is one format that can be converted to manpages (if you know it already) -- - Sami Haahtinen - - 2209 3C53 D0FB 041C F7B1 F908 A9B6 F730 B83D 761C -
Re: Creating man pages (upstream does not have one)
Eduardo Trapani wrote: The software I am packaging does not have a man page. What programs should I use to create one? I usually just edit one directly (in roff). I'm pretty sure dh_make installs a sample. If it doesn't, look at /usr/share/debhelper/dh_make/debian/manpage.1.ex There's also /usr/share/doc/man-db/examples/manpage.example Peter
Re: Creating man pages (upstream does not have one)
Eduardo Trapani [EMAIL PROTECTED] writes: The software I am packaging does not have a man page. What programs should I use to create one? Try using help2man to get a good template, and edit it by hand. Falk
Re: Creating man pages (upstream does not have one)
En réponse à Eduardo Trapani [EMAIL PROTECTED]: The software I am packaging does not have a man page. What programs should I use to create one? I would recommend to write them in the POD (Plain Old Documentation) format which makes it very seasy to write/update a man page. (see http://qa.debian.org/man-pages.html for pointers to documentations). I would NOT recommend to use the native manpage format (nroff) nor the DocBook SGML format since writing a manpage with them is rather respectively confusing/painful, IMHO. Jérôme.
Re: Creating man pages (upstream does not have one)
hi, On Thu, May 10, 2001 at 09:42:51PM +0200, Jérôme Marant wrote: I would recommend to write them in the POD (Plain Old Documentation) format which makes it very seasy to write/update a man page. (see http://qa.debian.org/man-pages.html for pointers to documentations). haven't dealt with it but i saw some examples and wasn't that conviced ... I would NOT recommend to use the native manpage format (nroff) nor the DocBook SGML format since writing a manpage with them is rather respectively confusing/painful, IMHO. plain wrong ... nroff is not hard or something like that, read the manpage howto and you know how to do it and there is also plenty of stuff about it lying around ... and i did a rather lengthy manpage with the an macro package and it was all but not a pain ... if *roff is a pain why do people use latex, eh? ... anyway, i don't consider it difficult, just different ... and an easy manpage is written in a few minutes. so long Othmar
Re: Creating man pages (upstream does not have one)
Y el jueves 10 de mayo, Eduardo Trapani escribió: The software I am packaging does not have a man page. What programs should I use to create one? Thanks, Eduardo. My suggestion: Use perldoc, you will write a txt file like this and you will get a pretty manpage with only one command: glade manpage source [only some lines]: - cut --- =head1 NAME glade - Rapid Development Application tool using Gtk+/Gnome libraries. =head1 SYNOPSIS glade [OPTION...] =head1 DESCRIPTION Glade is an application for creating graphical user interfaces that use the Gtk+ and GNOME libraries. Glade allows you to rapidly develope these interfaces, and can create source code in a variety of languages that will construct the interfaces for you. Glade can also be used in conjunction with libglade to dynamically create user interfaces from the XML description file that Glade creates. =head1 OPTIONS =over 4 =item B--disable-sound Disable sound server use. =back =head1 FILES =head2 The Glade XML File Format TheGlade XML file format is used when saving and loading projects in Glade. This format is also intended to be read by programs which convert it into source code in various languages. =head1 CAVEATS Here are some notes about problems which may be encountered when using Glade. =over 4 =item Some properties can not be set Some properties which can only be set when a widget is created or before it is realized. e.g. window - wmclass, wmname image - type visual (mentioned above) clist/ctree - number of columns =back =head1 SEE ALSO To obtain more information about Glade please visit Lhttp://glade.gnome.org. =head1 COPYRIGHT This package is free software; you can redistribute it and/or modify it under the terms of the GNU General Public License as published by the Free Software Foundation; version 2 dated June, 1991. =head1 AUTHORS Damon Chaplin [EMAIL PROTECTED] Martijn van Beers [EMAIL PROTECTED] - cut --- command to obtain glade.1: pod2man -r '' -c '' glade.podglade.1 HTH Saludos -- O / O O O O O / O / O / O / O Luis Arocha, Data \__|/|__|__|__|/ \__|/__|/__|/__|/|/ larocha at wanadoo.es \\ \ \ \ Islas Canarias \\ \ \ \ Spain pgpkHAWhYTM8Y.pgp Description: PGP signature
USA crypto rules and libssl-dependent packages
Hi. I am a novice Debian package maintainer, in the queue for becoming an official developer. I am maintaining a package called althea, which is an IMAP email client for GTK+. They have recently added support for SSL through linking to libssl (from OpenSSL). This is configurable based on the values of a couple variables in the Makefile. I have a couple of questions: 1) I live in the US. Therefore, do I have to send a BXA notification to the government (I believe license exception TSU is applicable - correct me if I'm wrong)? Also, do I have to do their thing that they mention on their website about sending a message to the ENC Classification Review Coordinator (or, something like that) in addition to [EMAIL PROTECTED], and if so, how do I do that? Also, is a BXA notification form sufficient to export binary .debs linked with libssl? Would anyone be able to export them, including other US mirror sites, so long as I provide an export of the same stuff that I notify the BXA about? 2) Do the binary .debs go in non-US? What about the Debian source files? If I make additional non-ssl .debs from the same source, would they be in non-US or not? Also, to the people on -mentors, how would I do this? (I am somewhat new to Debian packages.) I know this is a big message, but I very much appreciate any replies that you would be kind enough to give. Please CC on your replies; I am not subscribed to -legal (though I just got through reading your riveting discussion regarding Sergio Brandano's request on the archives :), and even though I am subscribed to -mentors, that mail gets ferreted away by procmail into a separate box and I would like to see this thread in my main inbox. Thank you all. - Jimmy Kaplowitz [EMAIL PROTECTED] - soon, hopefully, [EMAIL PROTECTED] :-) pgpkaFERTMTau.pgp Description: PGP signature
Re: [users] Re: Where's lame
On Wed, May 09, 2001 at 08:43:46AM -0500, Christian T. Steigies wrote: [...] It can be debianised, but it can't be included in debian, since it can't be legally redistributed in binary form. What do you mean ?? There are lots of packages included in debian in source form ... Why don't you read the webpage??? Why does everything have to be exlained again and again when somebody made the effort and explained it on a webpage? wnpp ist the first page you should look at when you want to package something. And its been there for ages, not really hard to find. I wasn't referring to lame, i was just answering the above-mentioned assertion : it can't be included in debian, since it can't be legally redistributed in binary form. First part of the sentence might be correct, but not for *that* reason. -- Eric VAN BUGGENHAUT [EMAIL PROTECTED]
Re: Override problem, help me please
Javier Vi uales Guti rrez wrote: Hello, I uploaded a new revision of my packeg hptalx and I'd just received the following message from [EMAIL PROTECTED] which I don't understand: I've been getting a rash of them lately. I'm guessing either packages have moved, or they've recently begun checking them. -- There are disparities between your recently installed upload and the override file for the following file(s): hptalx_1.1.0-2_i386.deb: priority is overridden from optional to extra. Either the package or the override file is incorrect. If you think the override is correct and the package wrong please fix the package so that this disparity is fixed in the next upload. If you feel the override is incorrect then please reply to this mail and explain why. -- I look at the control file and see Priority: optional, what do they mind with priority is overridden from optional to extra?. Only that your package was put in at the `extra' priority in spite of that is listed in your control file. If it's a package that is not of _general_ use, then `extra' is a better choice and you should simply change it to that at your next upload. Peter
Re: variable path names in manpages
On Thu, 10 May 2001, Ove Kaaven wrote: On Thu, 10 May 2001, Manfred Wassmann wrote: I'm currently writing a manpage which is to be used in a Debian package, but not exclusively. To be most flexible I want to use variables for path names that are expanded at build time. Is there any standard or recommended way implement this? If you're using autoconf, you can have a prog.1.in file that you can have configure process just like all those Makefile.in files to generate a prog.1 along with the Makefiles. (wine uses this technique) Thanks. Though autoconf isn't used it can't hurt to be compatible :-) -- Manfred Wassmann PGP and GnuPG public keys available at http://germany.keyserver.net PGP: 24B81049 Fingerprint: D7 10 EE 2B 74 16 C0 64 B4 5F BA B2 90 29 3D AF GPG: 6B299971 Fingerprint: A598 A41F 57A3 5D69 83D2 8027 1274 F8CD 6B29 9971 +++ I18N ? For international language set LANG=POSIX +++
perl modules - building debs
After several hours attempting to build debian packages for perl modules and twenty minutes searching google for helpful documentation, I have come to the conclusion that I have no frelling idea what I am doing. =) I read that there is a perl module that would build a package from any module on cpan. I also read something about dh_make_perl, although I can not find anything like that on my system. What is the best way to approach this issue? Are there any FAQs/HOWTOs which explain this process? Any informative replies will be appreciated, rtfms will be tolerated. =) Cheers! -- Derek E. Mart Marticus - Systems Programmer II U of L - Electrical Computer Engineering The Marticus Project - http://www.marticus.org/ 1514 3659 D057 D10C 6BE6 3E68 15BE B181 2F1F 510B pgpQmXP8XR9nq.pgp Description: PGP signature
