Re: Change of package name or command name.
On Wed, 27 Jun 2001, Yooseong Yang wrote: I have something wrong in my package(poedit) related to package name. Among thousands of debian packages, potool has the same command name - poedit - as my package command name. The source is absoultely different! In this case, should be the package name changed into another name? Is it possible that we just change the command name like poEdit (capital E) or poeditor instead of poedit? If I must change the package name, I just change the package name, rebuild it and then upload it? Is it correct? I am not sure about it. =) You don't have to change the package name. Just change the command-line name. It shouldn't be a problem. If you want to help your users to be able to use the programm under the old name you can use through the alternatives mechanism but AFAIK you'll have to coordinate that with the other package maintainer and the programms must provide a similar functionality... *t Tomas Pospisek SourcePole - Linux Open Source Solutions http://sourcepole.ch Elestastrasse 18, 7310 Bad Ragaz, Switzerland Tel: +41 (81) 330 77 11 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: binary-all packaging
On Wed, Jun 27, 2001 at 03:13:31AM +0200, Robert Millan wrote: dpkg-genchanges: failure: cannot read files list file: No such file or directory What am i doing wrong? I guess i have a problem in my rules file. just in case i post it here too: Your rules file is completely ill. Scrap it, copy /usr/share/doc/debhelper/examples/rules.indep to debian/rules and modify it as necessary to build your package. Julian -- =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- Julian Gilbey, Dept of Maths, Queen Mary, Univ. of London Debian GNU/Linux Developer, see http://people.debian.org/~jdg Donate free food to the world's hungry: see http://www.thehungersite.com/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: aspell compilation failed on arm: please help
Domenico Andreoli [EMAIL PROTECTED] writes: what i don't understand follows: *** Warning: inter-library dependencies are not known to be supported. *** All declared inter-library dependencies are being dropped. *** The inter-library dependencies that have been dropped here will be *** automatically added whenever a program is linked with this library *** or is declared to -dlopen it. i suppose the command following this statement fails because of the problem claimed by it, but i still don't figure out what does it means. Normally, when you link in a shared library into a program, the program will not contain code from that library, just stubs that are resolved at runtime *and* will depend on it. This dependencies are what shows up on ldd BINARY. If you link a shared library with a shared library, the same should happen, but some library formats do not support this feature. The message means that libtool suspects this system to be one of these. (see also (libtool)Inter-library Dependencies in the info pages). libtool is actually wrong, because all common Linux ports use ELF, which supports inter-library dependencies (accordingly, you can see those with ldd LIBRARY). I don't think that the following error (libtool issues: gcc [...] -o .libs/) has the same cause, apart from the fact that it's libtool's fault again: -o must name a target file, not a directory. aspell contains libtool 1.3c, which is old. Your best bet at the moment is running libtoolize --force in its top level directory while having a modern libtool package installed. This may well fix those bugs (or not). -- Robbe signature.ng
Re: chroot testing/unstable environment.
Viral [EMAIL PROTECTED] writes: I need to package kernel-patch-folk. However, the files are too big for me to download. Hang on if you can't download it, how are you going to use or test it? Or are you saying you're packaging software you neither use nor can test? -- James -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Packaging xmlrpc-c
Hello! I'm the author of xmlrpc-c, a library implementing XML-RPC for C and C++. (XML-RPC is a simple RPC protocol typically used for talking to web applications. It works by sending XML messages over HTTP, which is a bit of a strange way to do things, but it's nice for talking to Zope and similar applications.) You can find it online at: http://xmlrpc-c.sourceforge.net/ I've made some very rough Debian packages: http://sourceforge.net/project/showfiles.php?group_id=16847 Known problems: 1) The query-meerkat and meerkat-app-list programs are broken, thanks to a server update at http://meerkat.oreillynet.com/. This will be worked around in the next version. 2) One of the Perl scripts in xmlrpc-c-dev depends on libfrontier-rpc-perl, but this dependency hasn't been added to the xmlrpc-c-dev package yet. 3) Several of the man pages are links to unimplemented(7). I'll fix this soon. 4) I get a lintian warning for calling ldconfig in postrm, even though I only call it from the 'remove' rule, in accordance with policy. Have I done something wrong? 5) xmlrpc-c includes its own copy of expat (under a different soname) for binary compatibility with other Linux versions. I'd prefer not to change this, because it would make it hard for my users to build binaries that worked on more than one distro. 6) I stuck the *.so.* files into xmlrpc-c0, and the *.so files into xmlrpc-c-dev, since they're only used when compiling. It this the correct procedure for Debian? 7) The modules are named xmlrpc-c0, xmlrpc-c-dev and xmlrpc-c-apps. Should I use a different naming convention? So those are all the problems I *know* about. ;-) Are there any others which I've missed entirely? Also, how does one go about finding a sponsor? Cheers, Eric -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Change of package name or command name.
I change the command name of my package into poEdit. potool and poedit have similar functionality but poedit is based on GUI not on console. After changing the command name, all problems related to my package are solved. I'll come to upload my package to ftp-master. Any opinion? Yooseong Yang -- -- When code matters more than commercials... Yooseong Yang [EMAIL PROTECTED] [EMAIL PROTECTED] [EMAIL PROTECTED] Debian GNU/Linux Developer Debian http://www.debian.org Debian-KR http://www.debian.or.kr Debian Users http://debianusers.org KLDP http://kldp.org FAQ Project http://faq.kldp.org ICQ#65184660http://pcel3.snu.ac.kr/~yooseong PGP signature
Re: aspell compilation failed on arm: please help
On Wed, Jun 27, 2001 at 03:05:50PM +0200, Robert Bihlmeyer wrote: Domenico Andreoli [EMAIL PROTECTED] writes: what i don't understand follows: *** Warning: inter-library dependencies are not known to be supported. *** All declared inter-library dependencies are being dropped. *** The inter-library dependencies that have been dropped here will be *** automatically added whenever a program is linked with this library *** or is declared to -dlopen it. i suppose the command following this statement fails because of the problem claimed by it, but i still don't figure out what does it means. Normally, when you link in a shared library into a program, the program will not contain code from that library, just stubs that are resolved at runtime *and* will depend on it. This dependencies are what shows up on ldd BINARY. If you link a shared library with a shared library, the same should happen, but some library formats do not support this feature. The message means that libtool suspects this system to be one of these. (see also (libtool)Inter-library Dependencies in the info pages). libtool is actually wrong, because all common Linux ports use ELF, which supports inter-library dependencies (accordingly, you can see those with ldd LIBRARY). hmm... yes I don't think that the following error (libtool issues: gcc [...] -o .libs/) has the same cause, apart from the fact that it's libtool's fault again: -o must name a target file, not a directory. ok, i knew it was libtool to be wrong :)) aspell contains libtool 1.3c, which is old. Your best bet at the moment is running libtoolize --force in its top level directory while having a modern libtool package installed. This may well fix those bugs (or not). yes, i'll try thanks -- Robbe -[ Domenico Andreoli, aka cavok --[ http://filibusta.crema.unimi.it/~cavok/gpgkey.asc ---[ 3A0F 2F80 F79C 678A 8936 4FEE 0677 9033 A20E BC50 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Change of package name or command name.
On Thu, Jun 28, 2001 at 12:17:20AM +0900, Yooseong Yang wrote: I change the command name of my package into poEdit. potool and poedit have similar functionality but poedit is based on GUI not on console. After changing the command name, all problems related to my package are solved. I'll come to upload my package to ftp-master. Any opinion? Yes. poEdit is a horrible name. Command names should be all lowercase. Did you check with upstream about this, by the way? They may have preferences about the name, and they're likely to want to avoid the name collision if you point it out to them. Did you contact the maintainer of the other package? It might be easier to change the name there, because its poedit is not the primary tool of the package. -- Richard Braakman Will write free software for money. See http://www.xs4all.nl/~dark/resume.html -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Change of package name or command name.
On Wed, Jun 27, 2001 at 07:17:57PM +0300, Richard Braakman wrote: Did you contact the maintainer of the other package? It might be easier to change the name there, because its poedit is not the primary tool of the package. Actually, it is. potool was created to make creation of poedit possible. The package was named after the binary (poedit is just a wrapper) because it allows more then just editing po files. Maybe the tool in the other package could be renamed to 'poeditor' (since it's actually a standalone, GUI tool as I hear). regards Marcin (potool's maintainer) -- --- Marcin Owsiany [EMAIL PROTECTED] --- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Finding a sponsor...
How does one go about finding a sponsor? I think I understand the rest of the new maintainer process, but this bit confuses me somewhat. And it's the bit I apparently need to do first. :-) I'd like to maintain Debian packages for a library I maintain (details are in the thread Packaging xmlrpc-c). Thank you for your help! Cheers, Eric -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Finding a sponsor...
On Wed, Jun 27, 2001 at 10:23:23PM +0200, Gergely Nagy wrote: Thus spoke Eric Kidd [EMAIL PROTECTED] on 2001-06-27 16:00:04: How does one go about finding a sponsor? Ask on this list :) OK, that seems simple enough. :-) I'd like to maintain Debian packages for a library I maintain (details are in the thread Packaging xmlrpc-c). I'm having a look at them right now I've fixed several problems in my local copy: 1) No more links to unimplemented(7). I've written a whole bunch of new man pages, which will be going into the upstream release, too. 2) Better dependencies for xmlrpc-c-dev. query-meerkat and meerkat-app-list are still broken, but I've traced the bug to w3c-libwww. Something in the PHP server's output confuses w3c-libwww and causes it to chop off the trailing bytes of the message. Also, I'm still not sure how to handle C++ *.a or *.so files gracefully. It seems that Debian supports several different versions of the C++ runtime, and I need to build matching C++ *.a and *.so files for installation with the dev package. Is there a policy document on C++ dev libraries? Thank you for your help! Cheers, Eric -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Change of package name or command name.
Yes. poEdit is a horrible name. Command names should be all lowercase. What item in Debian Policy? you mean policy 2.3.1 or something? Did you check with upstream about this, by the way? They may have preferences about the name, and they're likely to want to avoid the name collision if you point it out to them. Upstream author want the command name poEdit. Did you contact the maintainer of the other package? It might be easier to change the name there, because its poedit is not the primary tool of the package. The potool maintainer might want the command name of my package as poeditor. I'll check this name with the Upstream Author. Yooseong Yang -- -- Codito, ergo sum (I code, therefore I am) Yooseong Yang ICQ#65184660 [EMAIL PROTECTED] [EMAIL PROTECTED] [EMAIL PROTECTED] KLDP http://kldp.org Debian GNU/Linux Developer Debian-KR http://www.debian.or.kr-- Debian GNU/Linux -- Debian Users http://debianusers.org http://www.debian.org http://pcel3.snu.ac.kr/~yooseong PGP signature
USENIX/boston keysigning
Theres a BOF tommrow night for debian and keysigning with other debian-people here at USENIX. I believe it runs from 9-10pm, Thursday. I dont think anyones going to be really checking if your 'registered' for usenix if you come by. So, if your in the boston area feel free to come by. directions are at www.usenix.org for the techincal confrence... -- Scott Dier [EMAIL PROTECTED] [EMAIL PROTECTED] http://www.ringworld.org/ #[EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Packaging xmlrpc-c
Eric Kidd ([EMAIL PROTECTED]) wrote: Hello! Hi! I'm the author of xmlrpc-c, a library implementing XML-RPC for C and C++. (XML-RPC is a simple RPC protocol typically used for talking to web applications. It works by sending XML messages over HTTP, which is a bit of a strange way to do things, but it's nice for talking to Zope and similar applications.) You can find it online at: http://xmlrpc-c.sourceforge.net/ I've made some very rough Debian packages: http://sourceforge.net/project/showfiles.php?group_id=16847 Known problems: 1) The query-meerkat and meerkat-app-list programs are broken, thanks to a server update at http://meerkat.oreillynet.com/. This will be worked around in the next version. 2) One of the Perl scripts in xmlrpc-c-dev depends on libfrontier-rpc-perl, but this dependency hasn't been added to the xmlrpc-c-dev package yet. 3) Several of the man pages are links to unimplemented(7). I'll fix this soon. 4) I get a lintian warning for calling ldconfig in postrm, even though I only call it from the 'remove' rule, in accordance with policy. Have I done something wrong? No, I get this all the time. Since this call is added by debhelper by default I don't see a reason to worry. 5) xmlrpc-c includes its own copy of expat (under a different soname) for binary compatibility with other Linux versions. I'd prefer not to change this, because it would make it hard for my users to build binaries that worked on more than one distro. Well, as maintainer of the expat and libxmltok packages I would really appreciate it if you could make an effort to use the standalone copy. Assuming you use the autoconf approach it should be possible to check for an already installed version and if not then use your own copy. I also noticed you use the old version of expat, not 1.95. Any particular reason? I also don't understand the issue with users building binaries on other distros. State simply that you depend on having expat already installed. The Perl module XML-Parser does that too. 6) I stuck the *.so.* files into xmlrpc-c0, and the *.so files into xmlrpc-c-dev, since they're only used when compiling. It this the correct procedure for Debian? Yep. Looks good. :-) 7) The modules are named xmlrpc-c0, xmlrpc-c-dev and xmlrpc-c-apps. Should I use a different naming convention? You could also use libxmlrpc-c0 and libxmlrpc-c-dev. That way it's easy to spot they're libraries. There might even be a policy about this. So those are all the problems I *know* about. ;-) Are there any others which I've missed entirely? Well, did you read the policy manual? Also, how does one go about finding a sponsor? Cheers, Eric Thanks, Ardo -- Ardo van Rangelrooij home email: [EMAIL PROTECTED] home page: http://people.debian.org/~ardo PGP fp: 3B 1F 21 72 00 5C 3A 73 7F 72 DF D9 90 78 47 F9 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Advocate/Sponsor
I was wondering if anyone would be willing to sponsor my application to be a new maintainer. Currently, I've packaged alienwave, a simple curses-based console game of the space invaders genre. I've also packaged the latest version of faqomatic, which was orphaned by Scott K. Ellis. Both alienwave and faqomatic are available at http://freecashonthewebnow.virtualave.net/debian (un: debian, pw: debian) Thanks. Duncan Findlay [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Change of package name or command name.
On Wed, 27 Jun 2001, Yooseong Yang wrote: I have something wrong in my package(poedit) related to package name. Among thousands of debian packages, potool has the same command name - poedit - as my package command name. The source is absoultely different! In this case, should be the package name changed into another name? Is it possible that we just change the command name like poEdit (capital E) or poeditor instead of poedit? If I must change the package name, I just change the package name, rebuild it and then upload it? Is it correct? I am not sure about it. =) You don't have to change the package name. Just change the command-line name. It shouldn't be a problem. If you want to help your users to be able to use the programm under the old name you can use through the alternatives mechanism but AFAIK you'll have to coordinate that with the other package maintainer and the programms must provide a similar functionality... *t Tomas Pospisek SourcePole - Linux Open Source Solutions http://sourcepole.ch Elestastrasse 18, 7310 Bad Ragaz, Switzerland Tel: +41 (81) 330 77 11
Re: binary-all packaging
On Wed, Jun 27, 2001 at 03:13:31AM +0200, Robert Millan wrote: dpkg-genchanges: failure: cannot read files list file: No such file or directory What am i doing wrong? I guess i have a problem in my rules file. just in case i post it here too: Your rules file is completely ill. Scrap it, copy /usr/share/doc/debhelper/examples/rules.indep to debian/rules and modify it as necessary to build your package. Julian -- =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- Julian Gilbey, Dept of Maths, Queen Mary, Univ. of London Debian GNU/Linux Developer, see http://people.debian.org/~jdg Donate free food to the world's hungry: see http://www.thehungersite.com/
Packaging xmlrpc-c
Hello! I'm the author of xmlrpc-c, a library implementing XML-RPC for C and C++. (XML-RPC is a simple RPC protocol typically used for talking to web applications. It works by sending XML messages over HTTP, which is a bit of a strange way to do things, but it's nice for talking to Zope and similar applications.) You can find it online at: http://xmlrpc-c.sourceforge.net/ I've made some very rough Debian packages: http://sourceforge.net/project/showfiles.php?group_id=16847 Known problems: 1) The query-meerkat and meerkat-app-list programs are broken, thanks to a server update at http://meerkat.oreillynet.com/. This will be worked around in the next version. 2) One of the Perl scripts in xmlrpc-c-dev depends on libfrontier-rpc-perl, but this dependency hasn't been added to the xmlrpc-c-dev package yet. 3) Several of the man pages are links to unimplemented(7). I'll fix this soon. 4) I get a lintian warning for calling ldconfig in postrm, even though I only call it from the 'remove' rule, in accordance with policy. Have I done something wrong? 5) xmlrpc-c includes its own copy of expat (under a different soname) for binary compatibility with other Linux versions. I'd prefer not to change this, because it would make it hard for my users to build binaries that worked on more than one distro. 6) I stuck the *.so.* files into xmlrpc-c0, and the *.so files into xmlrpc-c-dev, since they're only used when compiling. It this the correct procedure for Debian? 7) The modules are named xmlrpc-c0, xmlrpc-c-dev and xmlrpc-c-apps. Should I use a different naming convention? So those are all the problems I *know* about. ;-) Are there any others which I've missed entirely? Also, how does one go about finding a sponsor? Cheers, Eric
Re: Change of package name or command name.
I change the command name of my package into poEdit. potool and poedit have similar functionality but poedit is based on GUI not on console. After changing the command name, all problems related to my package are solved. I'll come to upload my package to ftp-master. Any opinion? Yooseong Yang -- -- When code matters more than commercials... Yooseong Yang [EMAIL PROTECTED] [EMAIL PROTECTED] [EMAIL PROTECTED] Debian GNU/Linux Developer Debian http://www.debian.org Debian-KR http://www.debian.or.kr Debian Users http://debianusers.org KLDP http://kldp.org FAQ Project http://faq.kldp.org ICQ#65184660http://pcel3.snu.ac.kr/~yooseong pgpHcYk4Kc2c9.pgp Description: PGP signature
Re: Change of package name or command name.
On Thu, Jun 28, 2001 at 12:17:20AM +0900, Yooseong Yang wrote: I change the command name of my package into poEdit. potool and poedit have similar functionality but poedit is based on GUI not on console. After changing the command name, all problems related to my package are solved. I'll come to upload my package to ftp-master. Any opinion? Yes. poEdit is a horrible name. Command names should be all lowercase. Did you check with upstream about this, by the way? They may have preferences about the name, and they're likely to want to avoid the name collision if you point it out to them. Did you contact the maintainer of the other package? It might be easier to change the name there, because its poedit is not the primary tool of the package. -- Richard Braakman Will write free software for money. See http://www.xs4all.nl/~dark/resume.html
Re: chroot testing/unstable environment.
On Wed, Jun 27, 2001 at 02:43:08PM +0100, James Troup wrote: Viral [EMAIL PROTECTED] writes: I need to package kernel-patch-folk. However, the files are too big for me to download. Hang on if you can't download it, how are you going to use or test it? Or are you saying you're packaging software you neither use nor can test? Well, in this case, I thought an exception would be fine. Its just one giant patch, with a whole lot of experimental projects. It would be impossible to test them myself. All I could test for is that the patch applies cleanly, which I can do on any machine. Check out the list of patches, and you'll figure its not quite possible to test. http://folk.sourceforge.net/ My idea was that there would be people who would be interested in this, and a package would help there. I had to do it this way for my other package, mosix too. I couldn't completely test it. People on debian-beowulf helped with the testing basically as I didn't have a cluster at hand then, and the package got done fine and went into the archives. Is my argument fine ? If someone else would want to take over the packaging of kernel-patch-folk, I would be glad. viral -- There's someone in my head but its not me. pgpTqItdxH5WN.pgp Description: PGP signature
Re: Change of package name or command name.
On Wed, Jun 27, 2001 at 07:17:57PM +0300, Richard Braakman wrote: Did you contact the maintainer of the other package? It might be easier to change the name there, because its poedit is not the primary tool of the package. Actually, it is. potool was created to make creation of poedit possible. The package was named after the binary (poedit is just a wrapper) because it allows more then just editing po files. Maybe the tool in the other package could be renamed to 'poeditor' (since it's actually a standalone, GUI tool as I hear). regards Marcin (potool's maintainer) -- --- Marcin Owsiany [EMAIL PROTECTED] ---
Re: binary-all packaging
Looks like your debian/rules is missing some important stuff. Here's one of mines, have a look at it, it's a tcl/tk script, no compilation. On Wed, Jun 27, 2001 at 03:13:31AM +0200, Robert Millan wrote: Hello, I'm on my first package. The upstream people provide just a perl script which should go to /usr/bin. I'm reading the instructions of the maintainer's guide (/usr/share/doc/maint-guide/) and all the steps and examples are desgned for creatinga binary package from a source tarball. I've tried to configure this file myself, but when i issue the command 'dpkg-buildpackage -rfakeroot' i always get the same error: dpkg-genchanges: failure: cannot read files list file: No such file or directory What am i doing wrong? I guess i have a problem in my rules file. just in case i post it here too: --./debian/rules #!/usr/bin/make -f # Sample debian/rules that uses debhelper. # GNU copyright 1997 to 1999 by Joey Hess. # Uncomment this to turn on verbose mode. #export DH_VERBOSE=1 # This is the debhelper compatability version to use. export DH_COMPAT=1 build: clean: install: dh_testdir dh_testroot # Add here commands to install the package into debian/tmp. mkdir -p `pwd`/debian/tmp/usr/bin /bin/cp `pwd`/esms `pwd`/debian/tmp/usr/bin/ # Build architecture-independent files here. binary-indep: build install # We have nothing to do by default. # Build architecture-dependent files here. binary-arch: build install binary: binary-indep binary-arch .PHONY: build clean binary-indep binary-arch binary install --EOF thanks-- Robert MillanDebian GNU user zeratul2 wanadoo eshttp://getyouriso.org/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED] -- Eric VAN BUGGENHAUT [EMAIL PROTECTED] #!/usr/bin/make -f # GNU copyright 1997 to 1999 by Joey Hess. # GNU copyright 2000 by Eric Van Buggenhaut. # Uncomment this to turn on verbose mode. #export DH_VERBOSE=1 # This is the debhelper compatability version to use. export DH_COMPAT=2 configure: configure-stamp configure-stamp: dh_testdir # Add here commands to configure the package. touch configure-stamp build: configure-stamp build-stamp build-stamp: dh_testdir # Add here commands to compile the package. #/usr/bin/docbook-to-man debian/s25manager.sgml s25manager.1 touch build-stamp clean: dh_testdir dh_testroot rm -f build-stamp configure-stamp # Add here commands to clean up after the build process. dh_clean install: build dh_testdir dh_testroot dh_clean -k dh_installdirs # Add here commands to install the package into debian/s25manager. install -d debian/s25manager/usr/bin install -m755 -o root -g root s25manager debian/s25manager/usr/bin/s25manager # Build architecture-independent files here. binary-indep: build install dh_testdir dh_testroot # dh_installdebconf dh_installdocs # dh_installexamples dh_installmenu # dh_installemacsen # dh_installpam # dh_installinit # dh_installcron dh_installmanpages dh_undocumented dh_installchangelogs # dh_link # dh_strip dh_compress dh_fixperms # You may want to make some executables suid here. # dh_suidregister # dh_makeshlibs dh_installdeb # dh_shlibdeps dh_gencontrol dh_md5sums dh_builddeb # Build architecture-dependent files here. binary-arch: build install # We have nothing to do here. binary: binary-indep binary-arch .PHONY: build clean binary-indep binary-arch binary install configure
Re: Finding a sponsor...
On Wed, Jun 27, 2001 at 10:23:23PM +0200, Gergely Nagy wrote: Thus spoke Eric Kidd [EMAIL PROTECTED] on 2001-06-27 16:00:04: How does one go about finding a sponsor? Ask on this list :) OK, that seems simple enough. :-) I'd like to maintain Debian packages for a library I maintain (details are in the thread Packaging xmlrpc-c). I'm having a look at them right now I've fixed several problems in my local copy: 1) No more links to unimplemented(7). I've written a whole bunch of new man pages, which will be going into the upstream release, too. 2) Better dependencies for xmlrpc-c-dev. query-meerkat and meerkat-app-list are still broken, but I've traced the bug to w3c-libwww. Something in the PHP server's output confuses w3c-libwww and causes it to chop off the trailing bytes of the message. Also, I'm still not sure how to handle C++ *.a or *.so files gracefully. It seems that Debian supports several different versions of the C++ runtime, and I need to build matching C++ *.a and *.so files for installation with the dev package. Is there a policy document on C++ dev libraries? Thank you for your help! Cheers, Eric
Re: Finding a sponsor...
On Wed, Jun 27, 2001 at 03:21:29PM -0700, John H. Robinson, IV wrote: On Wed, Jun 27, 2001 at 04:00:04PM -0400, Eric Kidd wrote: How does one go about finding a sponsor? ... And it's the bit I apparently need to do first. :-) do you mean advocate? Yes, I do. Too much libwww debugging has fried my brain. :-/ Cheers, Eric
USENIX/boston keysigning
Theres a BOF tommrow night for debian and keysigning with other debian-people here at USENIX. I believe it runs from 9-10pm, Thursday. I dont think anyones going to be really checking if your 'registered' for usenix if you come by. So, if your in the boston area feel free to come by. directions are at www.usenix.org for the techincal confrence... -- Scott Dier [EMAIL PROTECTED] [EMAIL PROTECTED] http://www.ringworld.org/ [EMAIL PROTECTED]
Re: Packaging xmlrpc-c
Eric Kidd ([EMAIL PROTECTED]) wrote: Hello! Hi! I'm the author of xmlrpc-c, a library implementing XML-RPC for C and C++. (XML-RPC is a simple RPC protocol typically used for talking to web applications. It works by sending XML messages over HTTP, which is a bit of a strange way to do things, but it's nice for talking to Zope and similar applications.) You can find it online at: http://xmlrpc-c.sourceforge.net/ I've made some very rough Debian packages: http://sourceforge.net/project/showfiles.php?group_id=16847 Known problems: 1) The query-meerkat and meerkat-app-list programs are broken, thanks to a server update at http://meerkat.oreillynet.com/. This will be worked around in the next version. 2) One of the Perl scripts in xmlrpc-c-dev depends on libfrontier-rpc-perl, but this dependency hasn't been added to the xmlrpc-c-dev package yet. 3) Several of the man pages are links to unimplemented(7). I'll fix this soon. 4) I get a lintian warning for calling ldconfig in postrm, even though I only call it from the 'remove' rule, in accordance with policy. Have I done something wrong? No, I get this all the time. Since this call is added by debhelper by default I don't see a reason to worry. 5) xmlrpc-c includes its own copy of expat (under a different soname) for binary compatibility with other Linux versions. I'd prefer not to change this, because it would make it hard for my users to build binaries that worked on more than one distro. Well, as maintainer of the expat and libxmltok packages I would really appreciate it if you could make an effort to use the standalone copy. Assuming you use the autoconf approach it should be possible to check for an already installed version and if not then use your own copy. I also noticed you use the old version of expat, not 1.95. Any particular reason? I also don't understand the issue with users building binaries on other distros. State simply that you depend on having expat already installed. The Perl module XML-Parser does that too. 6) I stuck the *.so.* files into xmlrpc-c0, and the *.so files into xmlrpc-c-dev, since they're only used when compiling. It this the correct procedure for Debian? Yep. Looks good. :-) 7) The modules are named xmlrpc-c0, xmlrpc-c-dev and xmlrpc-c-apps. Should I use a different naming convention? You could also use libxmlrpc-c0 and libxmlrpc-c-dev. That way it's easy to spot they're libraries. There might even be a policy about this. So those are all the problems I *know* about. ;-) Are there any others which I've missed entirely? Well, did you read the policy manual? Also, how does one go about finding a sponsor? Cheers, Eric Thanks, Ardo -- Ardo van Rangelrooij home email: [EMAIL PROTECTED] home page: http://people.debian.org/~ardo PGP fp: 3B 1F 21 72 00 5C 3A 73 7F 72 DF D9 90 78 47 F9
Advocate/Sponsor
I was wondering if anyone would be willing to sponsor my application to be a new maintainer. Currently, I've packaged alienwave, a simple curses-based console game of the space invaders genre. I've also packaged the latest version of faqomatic, which was orphaned by Scott K. Ellis. Both alienwave and faqomatic are available at http://freecashonthewebnow.virtualave.net/debian (un: debian, pw: debian) Thanks. Duncan Findlay [EMAIL PROTECTED]
