Re: dh-autoreconf/autotools-dev questions
On Tue, 16 Aug 2011 16:16:30 +0200, Gergely Nagy alger...@balabit.hu wrote: Oohara Yuuma ooh...@libra.interq.or.jp writes: I am packaging a software which uses autoconf and automake. I will regenerate all autotool files with dh-autoreconf. * The upstream tarball contains auto-generated files. Do I have to save these files somewhere before calling dh_autoreconf and restore them in the clean target, or is it enough to remove auto-generated files in the clean target so that they are regenerated again in the build target? Just call dh_autoreconf, nothing else to do. It takes care of restoring the original state, whatever that may have been. When using dh_autoreconf, it will _always_ regenerate the appropriate files, so you don't need to prepare the tree for it. * dh-autoreconf saves only the checksum of the files in the source tree, not their contents. Files overwritten by autoreconf will be lost. * dh-autoreconf checks only _normal_ files. For example, it leaves an empty directory autom4te.cache. In short, running ./debian/rules build ./debian/rules clean does modify the source tree. I don't think this is a problem when building the package because 3.0 (quilt) ignores removed files by default and autom4te.cache is removed by dh_clean anyway, but is this a right way to undo any effects that the build and binary targets may have had (the definition of the clean target in the policy)? -- Oohara Yuuma ooh...@libra.interq.or.jp -- 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/20110818.004825.255387065.oohara@timber
dh-autoreconf/autotools-dev questions
I am packaging a software which uses autoconf and automake. I will
regenerate all autotool files with dh-autoreconf.
* The upstream tarball contains auto-generated files. Do I have to
save these files somewhere before calling dh_autoreconf and restore
them in the clean target, or is it enough to remove auto-generated
files in the clean target so that they are regenerated again
in the build target?
* The software doesn't use AC_CANONICAL or libtool. Running autoreconf
manually doesn't generate config.{guess, sub}. Do I have to
build-depend on autotools-dev and call both dh_autoreconf and
dh_autotools-dev_updateconfig to copy the latest config.{guess, sub},
or is it enough to set the --build and --host options of configure
with dpkg-architecture?
--
Oohara Yuuma ooh...@libra.interq.or.jp
--
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/20110816.224943.219737932.oohara@timber
suspicious new e-mail address notification of a contributer
I received an e-mail from a contributer of a Debian package I maintain. The mail says his e-mail address is no longer operational and he has a new one. Because his work is an important part of the package, it will be good to mention it in the changelog of the package. The problem is that the mail is written in a way which makes me think it is a spam: * more than 50 addresses in the Cc: list * the claimed new address is @yahoo.ca * not GPG signed, no information about him in the body If it is a spam, then updating the old address is wrong and responding to it is not very safe. I have no other way to contact him. What should I do? -- Oohara Yuuma [EMAIL PROTECTED] Lord, what fools these mortals be! --- William Shakespeare, A Midsummer-Night's Dream -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Bits from the RM
On Tue, 19 Aug 2003 16:49:25 +1000, Anthony Towns [EMAIL PROTECTED] wrote to debian-devel-announce: * If you're uploading NMUs for the BSP during this period, you should skip DELAYED, and just upload straight to queue/unchecked (f.k.a Incoming). Does uploading to Incoming still work? -- Oohara Yuuma [EMAIL PROTECTED] Debian developer PGP key (key ID F464A695) http://www.interq.or.jp/libra/oohara/pub-key.txt Key fingerprint = 6142 8D07 9C5B 159B C170 1F4A 40D6 F42E F464 A695 enlightened self-interest --- Nathanael Nerode, on discussion about the reason to contribute to Debian -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Bits from the RM
On Tue, 19 Aug 2003 16:49:25 +1000, Anthony Towns aj@azure.humbug.org.au wrote to debian-devel-announce: * If you're uploading NMUs for the BSP during this period, you should skip DELAYED, and just upload straight to queue/unchecked (f.k.a Incoming). Does uploading to Incoming still work? -- Oohara Yuuma [EMAIL PROTECTED] Debian developer PGP key (key ID F464A695) http://www.interq.or.jp/libra/oohara/pub-key.txt Key fingerprint = 6142 8D07 9C5B 159B C170 1F4A 40D6 F42E F464 A695 enlightened self-interest --- Nathanael Nerode, on discussion about the reason to contribute to Debian
Re: Academical question: How to package foo and foo-patched?
On Sun, 29 Jun 2003 22:43:17 +0200, Marc Haber [EMAIL PROTECTED] wrote: [creating foo-patched .deb from foo .deb unmaintained by the upstream or the Debian maintainer] How would more experienced Debian maintainers handle this issue? There are some tools which unpack and/or patch the source at build time. * debnest: unpacks a Debian style upstream source (.orig.tar.gz, .diff.gz and .dsc in a tarball) * cdbs: a set of Makefile fragments such as - autotools.mk: calls ./configure with right arguments (--prefix, --mandir, ...) - debhelper.mk: calls dh_* auto-magically cdbs includes simple-patchsys.mk, which applies patches at build time and unapplies them at clean time * dpatch: executes scripts (not diff files) in debian/patches at build or clean time * dbs: unpacks a tarball-in-tarball and patches the unpacked source dbs does nothing at clean time because you just remove the source tree The best way is to put source files of foo .deb in a tarball and use that tarball as the upstream source of foo-patched .deb, unpacking it with debnest. cdbs or dpatch will help you if you modify the non-Debian part of the source a lot. -- Oohara Yuuma [EMAIL PROTECTED] Debian developer PGP key (key ID F464A695) http://www.interq.or.jp/libra/oohara/pub-key.txt Key fingerprint = 6142 8D07 9C5B 159B C170 1F4A 40D6 F42E F464 A695 Er, let's get into all the messes of the parliament. --- shinichiro.h, diary 2003/3/24 parliamentary bullet-dodging system -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Academical question: How to package foo and foo-patched?
On Sun, 29 Jun 2003 22:43:17 +0200, Marc Haber [EMAIL PROTECTED] wrote: [creating foo-patched .deb from foo .deb unmaintained by the upstream or the Debian maintainer] How would more experienced Debian maintainers handle this issue? There are some tools which unpack and/or patch the source at build time. * debnest: unpacks a Debian style upstream source (.orig.tar.gz, .diff.gz and .dsc in a tarball) * cdbs: a set of Makefile fragments such as - autotools.mk: calls ./configure with right arguments (--prefix, --mandir, ...) - debhelper.mk: calls dh_* auto-magically cdbs includes simple-patchsys.mk, which applies patches at build time and unapplies them at clean time * dpatch: executes scripts (not diff files) in debian/patches at build or clean time * dbs: unpacks a tarball-in-tarball and patches the unpacked source dbs does nothing at clean time because you just remove the source tree The best way is to put source files of foo .deb in a tarball and use that tarball as the upstream source of foo-patched .deb, unpacking it with debnest. cdbs or dpatch will help you if you modify the non-Debian part of the source a lot. -- Oohara Yuuma [EMAIL PROTECTED] Debian developer PGP key (key ID F464A695) http://www.interq.or.jp/libra/oohara/pub-key.txt Key fingerprint = 6142 8D07 9C5B 159B C170 1F4A 40D6 F42E F464 A695 Er, let's get into all the messes of the parliament. --- shinichiro.h, diary 2003/3/24 parliamentary bullet-dodging system
Re: Looking for sponsor for small volleyball game
On Thu, 13 Feb 2003 10:12:39 -0500, David Grant [EMAIL PROTECTED] wrote: I just packaged a small game, called GAV (GNU Arcade Volleyball). Ari Pollak [EMAIL PROTECTED] packaged gav and filed an ITP on Thu, 13 Feb 2003 22:52:24 -0500. See #180935. -- Oohara Yuuma [EMAIL PROTECTED] Debian developer PGP key (key ID F464A695) http://www.interq.or.jp/libra/oohara/pub-key.txt Key fingerprint = 6142 8D07 9C5B 159B C170 1F4A 40D6 F42E F464 A695 Is it necessary to show the whole world how harsh one can be? --- Martin Loschwitz -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Looking for sponsor for small volleyball game
On Thu, 13 Feb 2003 10:12:39 -0500, David Grant [EMAIL PROTECTED] wrote: I just packaged a small game, called GAV (GNU Arcade Volleyball). Ari Pollak [EMAIL PROTECTED] packaged gav and filed an ITP on Thu, 13 Feb 2003 22:52:24 -0500. See #180935. -- Oohara Yuuma [EMAIL PROTECTED] Debian developer PGP key (key ID F464A695) http://www.interq.or.jp/libra/oohara/pub-key.txt Key fingerprint = 6142 8D07 9C5B 159B C170 1F4A 40D6 F42E F464 A695 Is it necessary to show the whole world how harsh one can be? --- Martin Loschwitz
Re: need help with bug #178837 (automake)
On Mon, 3 Feb 2003 21:35:28 +0100, Frank Gevaerts [EMAIL PROTECTED] wrote: On Mon, Feb 03, 2003 at 09:01:15PM +0100, Thomas Viehmann wrote: In particular, in debian/rules you could do (the first line probably already being present from dh_make): DEB_BUILD_GNU_CPU = $(shell dpkg-architecture -qDEB_BUILD_GNU_CPU) ifeq ($(DEB_BUILD_GNU_CPU),alpha) ... endif Yes, but my problem is that this doesn't work as long as Makefile.am contains a hardcoded CFLAGS variable. My problem is how to get rid of that. build: ifeq ($(DEB_BUILD_GNU_CPU),alpha) $(MAKE) CFLAGS=something else $(MAKE) CFLAGS=something else endif -- Oohara Yuuma [EMAIL PROTECTED] Debian developer PGP key (key ID F464A695) http://www.interq.or.jp/libra/oohara/pub-key.txt Key fingerprint = 6142 8D07 9C5B 159B C170 1F4A 40D6 F42E F464 A695 Do not assume users will be motivated to read manuals --- The GNU Privacy Handbook -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: need help with bug #178837 (automake)
On Mon, 3 Feb 2003 21:35:28 +0100, Frank Gevaerts [EMAIL PROTECTED] wrote: On Mon, Feb 03, 2003 at 09:01:15PM +0100, Thomas Viehmann wrote: In particular, in debian/rules you could do (the first line probably already being present from dh_make): DEB_BUILD_GNU_CPU = $(shell dpkg-architecture -qDEB_BUILD_GNU_CPU) ifeq ($(DEB_BUILD_GNU_CPU),alpha) ... endif Yes, but my problem is that this doesn't work as long as Makefile.am contains a hardcoded CFLAGS variable. My problem is how to get rid of that. build: ifeq ($(DEB_BUILD_GNU_CPU),alpha) $(MAKE) CFLAGS=something else $(MAKE) CFLAGS=something else endif -- Oohara Yuuma [EMAIL PROTECTED] Debian developer PGP key (key ID F464A695) http://www.interq.or.jp/libra/oohara/pub-key.txt Key fingerprint = 6142 8D07 9C5B 159B C170 1F4A 40D6 F42E F464 A695 Do not assume users will be motivated to read manuals --- The GNU Privacy Handbook
Re: vimoutliner -- looking for a sponsor
On Tue, 14 Jan 2003 13:14:23 -0500, [EMAIL PROTECTED] (Matej Cepl) wrote: I have created my first Debian package of vimoutliner (see http://www.troubleshooters.com/projects/vimoutliner/ for the upstream homepage). There are no problems with lintian, but could anybody take a look at it and help me to get it to the main distribution, please? It is available at http://www.volny.cz/cepls/progs/. I didn't know you were not sponsored. I looked at your package. I am an Emacs user, so I don't sponsor you, that's why I post this to the list. * Architecture: any You may mean all here; everything in the package is architecture independent. * /etc/vimoutliner.conf is in the package, is a symlink to /usr/share/vimoutliner/outlinerconf/vimoutliner.conf , and is not marked as a conffile. Are you really sure a user don't (and shouldn't) modify that file? * The command ol calls perl scripts via the -c option. I am not a perl guru, but I think you need Depends: perl . Some say it is unnecessary if your script works with only perl-base (which is essential). Quoting the Perl Policy: | Note that the perl-base package is intended only to provide for | exceptional circumstances and the contents may change. In general only | packages which form part of the base system should declare a dependency | on perl-base rather than perl. -- Oohara Yuuma [EMAIL PROTECTED] Debian developer PGP key (key ID F464A695) http://www.interq.or.jp/libra/oohara/pub-key.txt Key fingerprint = 6142 8D07 9C5B 159B C170 1F4A 40D6 F42E F464 A695 Do not assume users will be motivated to read manuals --- The GNU Privacy Handbook -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: vimoutliner -- looking for a sponsor
On Tue, 14 Jan 2003 13:14:23 -0500, [EMAIL PROTECTED] (Matej Cepl) wrote: I have created my first Debian package of vimoutliner (see http://www.troubleshooters.com/projects/vimoutliner/ for the upstream homepage). There are no problems with lintian, but could anybody take a look at it and help me to get it to the main distribution, please? It is available at http://www.volny.cz/cepls/progs/. I didn't know you were not sponsored. I looked at your package. I am an Emacs user, so I don't sponsor you, that's why I post this to the list. * Architecture: any You may mean all here; everything in the package is architecture independent. * /etc/vimoutliner.conf is in the package, is a symlink to /usr/share/vimoutliner/outlinerconf/vimoutliner.conf , and is not marked as a conffile. Are you really sure a user don't (and shouldn't) modify that file? * The command ol calls perl scripts via the -c option. I am not a perl guru, but I think you need Depends: perl . Some say it is unnecessary if your script works with only perl-base (which is essential). Quoting the Perl Policy: | Note that the perl-base package is intended only to provide for | exceptional circumstances and the contents may change. In general only | packages which form part of the base system should declare a dependency | on perl-base rather than perl. -- Oohara Yuuma [EMAIL PROTECTED] Debian developer PGP key (key ID F464A695) http://www.interq.or.jp/libra/oohara/pub-key.txt Key fingerprint = 6142 8D07 9C5B 159B C170 1F4A 40D6 F42E F464 A695 Do not assume users will be motivated to read manuals --- The GNU Privacy Handbook
Re: Advocate?? (forgot the address)
On Thu, 23 Jan 2003 12:09:22 -0500, Matej Cepl [EMAIL PROTECTED] wrote: Oohara Yuuma wrote: Import the Debian keyring, download the .changes of your package, and verify the signature. You mean whole keyring of Debian? How many megs it is? Where should I download it, what's my login etc.? $ apt-cache show debian-keyring Package: debian-keyring Priority: optional Section: misc Installed-Size: 4356 Maintainer: James Troup [EMAIL PROTECTED] Architecture: all Version: 2002.11.26 Recommends: gnupg (= 1.0.3) Filename: pool/main/d/debian-keyring/debian-keyring_2002.11.26_all.deb Size: 3650574 MD5sum: f8914656ee345baa51477335713ba0c9 Description: GnuPG (and obsolete PGP) keys of Debian Developers The Debian project wants developers to digitally sign the announcements of their packages with GnuPG, to protect against forgeries. This package contains keyrings of GnuPG and (deprecated) PGP keys of developers. Note that this package is not the canonical copy of the keyring. BTW, I have UPLOADED my signed public key to keys.debian.org -- isn't it enough? I don't know about keys.debian.org . If keyring.debian.org accepts your key, you are already a Debian developer. -- Oohara Yuuma [EMAIL PROTECTED] Debian developer PGP key (key ID F464A695) http://www.interq.or.jp/libra/oohara/pub-key.txt Key fingerprint = 6142 8D07 9C5B 159B C170 1F4A 40D6 F42E F464 A695 Do not assume users will be motivated to read manuals --- The GNU Privacy Handbook -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Advocate?? (forgot the address)
On Wed, 22 Jan 2003 18:01:28 -0500, Matej Cepl [EMAIL PROTECTED] wrote: somebody here on the list was so kind, that he volunteered to be a sponsor for my package vimoutliner. [snip] Unfortunately, I have by mistake deleted couple of my mails (including this one) and I do not know, who was that kind person, so that I may ask him for being a advocate for me. Import the Debian keyring, download the .changes of your package, and verify the signature. -- Oohara Yuuma [EMAIL PROTECTED] Debian developer PGP key (key ID F464A695) http://www.interq.or.jp/libra/oohara/pub-key.txt Key fingerprint = 6142 8D07 9C5B 159B C170 1F4A 40D6 F42E F464 A695 Do not assume users will be motivated to read manuals --- The GNU Privacy Handbook
Re: Advocate?? (forgot the address)
On Thu, 23 Jan 2003 12:09:22 -0500, Matej Cepl [EMAIL PROTECTED] wrote: Oohara Yuuma wrote: Import the Debian keyring, download the .changes of your package, and verify the signature. You mean whole keyring of Debian? How many megs it is? Where should I download it, what's my login etc.? $ apt-cache show debian-keyring Package: debian-keyring Priority: optional Section: misc Installed-Size: 4356 Maintainer: James Troup [EMAIL PROTECTED] Architecture: all Version: 2002.11.26 Recommends: gnupg (= 1.0.3) Filename: pool/main/d/debian-keyring/debian-keyring_2002.11.26_all.deb Size: 3650574 MD5sum: f8914656ee345baa51477335713ba0c9 Description: GnuPG (and obsolete PGP) keys of Debian Developers The Debian project wants developers to digitally sign the announcements of their packages with GnuPG, to protect against forgeries. This package contains keyrings of GnuPG and (deprecated) PGP keys of developers. Note that this package is not the canonical copy of the keyring. BTW, I have UPLOADED my signed public key to keys.debian.org -- isn't it enough? I don't know about keys.debian.org . If keyring.debian.org accepts your key, you are already a Debian developer. -- Oohara Yuuma [EMAIL PROTECTED] Debian developer PGP key (key ID F464A695) http://www.interq.or.jp/libra/oohara/pub-key.txt Key fingerprint = 6142 8D07 9C5B 159B C170 1F4A 40D6 F42E F464 A695 Do not assume users will be motivated to read manuals --- The GNU Privacy Handbook
Re: the right way to uninstall /var/games
On 01 Jan 2003 12:25:50 -0800, Ian Zimmerman [EMAIL PROTECTED] wrote: Oohara I maintain a game which saves its high score in /var/games . Oohara It creates /var/games in its postinst to avoid dpkg -r Oohara directory not removed because it is not empty warning. Colin I don't think you should worry about that warning. Accept it as Colin a bug in dpkg, tell anybody who complains about it that it's a Colin bug in dpkg, and make your package behave in the simplest Colin possible way. I agree. It is a small problem (if one at all) compared to the ones you already know you'd encounter trying to avoid it. I forgot why the high score directory is created in postinst in the first place. I want to keep the high score file when the package is removed but not purged, so including /var/games in .deb is wrong. The problem on purge is still unsolved, though. -- Oohara Yuuma [EMAIL PROTECTED] Debian developer PGP key (key ID F464A695) http://www.interq.or.jp/libra/oohara/pub-key.txt Key fingerprint = 6142 8D07 9C5B 159B C170 1F4A 40D6 F42E F464 A695 smile to answer --- Treasure, Radiant Silvergun, attitude #3 for SBS-130 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: the right way to uninstall /var/games
On 01 Jan 2003 12:25:50 -0800, Ian Zimmerman [EMAIL PROTECTED] wrote: Oohara I maintain a game which saves its high score in /var/games . Oohara It creates /var/games in its postinst to avoid dpkg -r Oohara directory not removed because it is not empty warning. Colin I don't think you should worry about that warning. Accept it as Colin a bug in dpkg, tell anybody who complains about it that it's a Colin bug in dpkg, and make your package behave in the simplest Colin possible way. I agree. It is a small problem (if one at all) compared to the ones you already know you'd encounter trying to avoid it. I forgot why the high score directory is created in postinst in the first place. I want to keep the high score file when the package is removed but not purged, so including /var/games in .deb is wrong. The problem on purge is still unsolved, though. -- Oohara Yuuma [EMAIL PROTECTED] Debian developer PGP key (key ID F464A695) http://www.interq.or.jp/libra/oohara/pub-key.txt Key fingerprint = 6142 8D07 9C5B 159B C170 1F4A 40D6 F42E F464 A695 smile to answer --- Treasure, Radiant Silvergun, attitude #3 for SBS-130
the right way to uninstall /var/games
I maintain a game which saves its high score in /var/games . It creates /var/games in its postinst to avoid dpkg -r directory not removed because it is not empty warning. What is the right way to uninstall /var/games in postrm on purge? Problems: 1) The package should remove /var/games on purge if necessary because, unlike /var/log, /var/games is not a part of base-files . 2) There may be a game such that: * it saves its high score in a file in /var/games, not in a subdirectory under /var/games * it does not create a file in /var/games until the first entry of the high score is saved If such a game is installed, any other game should not remove /var/games even if /var/games is empty. -- Oohara Yuuma [EMAIL PROTECTED] Debian developer PGP key (key ID F464A695) http://www.interq.or.jp/libra/oohara/pub-key.txt Key fingerprint = 6142 8D07 9C5B 159B C170 1F4A 40D6 F42E F464 A695 smile to answer --- Treasure, Radiant Silvergun, attitude #3 for SBS-130 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
the right way to uninstall /var/games
I maintain a game which saves its high score in /var/games . It creates /var/games in its postinst to avoid dpkg -r directory not removed because it is not empty warning. What is the right way to uninstall /var/games in postrm on purge? Problems: 1) The package should remove /var/games on purge if necessary because, unlike /var/log, /var/games is not a part of base-files . 2) There may be a game such that: * it saves its high score in a file in /var/games, not in a subdirectory under /var/games * it does not create a file in /var/games until the first entry of the high score is saved If such a game is installed, any other game should not remove /var/games even if /var/games is empty. -- Oohara Yuuma [EMAIL PROTECTED] Debian developer PGP key (key ID F464A695) http://www.interq.or.jp/libra/oohara/pub-key.txt Key fingerprint = 6142 8D07 9C5B 159B C170 1F4A 40D6 F42E F464 A695 smile to answer --- Treasure, Radiant Silvergun, attitude #3 for SBS-130
Re: Looking for a `light' library deb in order to serve as anexample.
On Tue, 31 Dec 2002 02:43:04 +0200, Shaul Karl [EMAIL PROTECTED] wrote: Can you recommend a `light' library package that is already packaged for debian in order to be used as an example for packaging a library? By `light' I mean a small and straightforward library, without hardware dependencies or other complications. shhmsg --- basically this is a printf wrapper -- Oohara Yuuma [EMAIL PROTECTED] Debian developer PGP key (key ID F464A695) http://www.interq.or.jp/libra/oohara/pub-key.txt Key fingerprint = 6142 8D07 9C5B 159B C170 1F4A 40D6 F42E F464 A695 smile to answer --- Treasure, Radiant Silvergun, attitude #3 for SBS-130 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Looking for a `light' library deb in order to serve as an example.
On Tue, 31 Dec 2002 02:43:04 +0200, Shaul Karl [EMAIL PROTECTED] wrote: Can you recommend a `light' library package that is already packaged for debian in order to be used as an example for packaging a library? By `light' I mean a small and straightforward library, without hardware dependencies or other complications. shhmsg --- basically this is a printf wrapper -- Oohara Yuuma [EMAIL PROTECTED] Debian developer PGP key (key ID F464A695) http://www.interq.or.jp/libra/oohara/pub-key.txt Key fingerprint = 6142 8D07 9C5B 159B C170 1F4A 40D6 F42E F464 A695 smile to answer --- Treasure, Radiant Silvergun, attitude #3 for SBS-130
signing a GPG key with multiple uids
When signing a GPG key, is it better to sign all of its uids, or just an uid that I see relevant (such as the @debian.org one)? I usually meet someone, get a hardcopy of the key fingerprint, the e-mail address and so on, then check it later and sign the uid which have that address in it. -- Oohara Yuuma [EMAIL PROTECTED] Debian developer PGP key (key ID F464A695) http://www.interq.or.jp/libra/oohara/pub-key.txt Key fingerprint = 6142 8D07 9C5B 159B C170 1F4A 40D6 F42E F464 A695 smile to answer --- Treasure, Radiant Silvergun, attitude #3 for SBS-130 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
signing a GPG key with multiple uids
When signing a GPG key, is it better to sign all of its uids, or just an uid that I see relevant (such as the @debian.org one)? I usually meet someone, get a hardcopy of the key fingerprint, the e-mail address and so on, then check it later and sign the uid which have that address in it. -- Oohara Yuuma [EMAIL PROTECTED] Debian developer PGP key (key ID F464A695) http://www.interq.or.jp/libra/oohara/pub-key.txt Key fingerprint = 6142 8D07 9C5B 159B C170 1F4A 40D6 F42E F464 A695 smile to answer --- Treasure, Radiant Silvergun, attitude #3 for SBS-130
#168383 exploitable?
[Please reply to [EMAIL PROTECTED] --- see Mail-Followup-To:] Can anyone check if #168383 (buffer overflow in osh, a setuid root shell) is exploitable? If it is, we may need a DSA. -- Oohara Yuuma [EMAIL PROTECTED] Debian developer PGP key (key ID F464A695) http://www.interq.or.jp/libra/oohara/pub-key.txt Key fingerprint = 6142 8D07 9C5B 159B C170 1F4A 40D6 F42E F464 A695 another love --- Treasure, Radiant Silvergun, attitude #3 for Golets -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
#168383 exploitable?
[Please reply to [EMAIL PROTECTED] --- see Mail-Followup-To:] Can anyone check if #168383 (buffer overflow in osh, a setuid root shell) is exploitable? If it is, we may need a DSA. -- Oohara Yuuma [EMAIL PROTECTED] Debian developer PGP key (key ID F464A695) http://www.interq.or.jp/libra/oohara/pub-key.txt Key fingerprint = 6142 8D07 9C5B 159B C170 1F4A 40D6 F42E F464 A695 another love --- Treasure, Radiant Silvergun, attitude #3 for Golets
Re: NM page update request
On Sat, 26 Oct 2002 17:11:30 -0700, Osamu Aoki [EMAIL PROTECTED] wrote: [helping Debian is more than packaging] Steve, you have a good point here. Should not we change http://www.debian.org/devel/join/nm-step1 to match this current practice so everyone is clear on this subject. AOL * a way to identify himself (preferably by having a GPG key signed by an existing Debian Developer or, alternatively, by sending in a photo of his drivers license or passport signed digitally with his GPG key) I don't think you can pass the NM queue without a signed GPG key nowadays. -- Oohara Yuuma [EMAIL PROTECTED] Debian developer PGP key (key ID F464A695) http://www.interq.or.jp/libra/oohara/pub-key.txt Key fingerprint = 6142 8D07 9C5B 159B C170 1F4A 40D6 F42E F464 A695 Let's cry that we do not have a clue. --- Junichi Uekawa, diary 2002/8/17 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: NM page update request
On Sat, 26 Oct 2002 17:11:30 -0700, Osamu Aoki [EMAIL PROTECTED] wrote: [helping Debian is more than packaging] Steve, you have a good point here. Should not we change http://www.debian.org/devel/join/nm-step1 to match this current practice so everyone is clear on this subject. AOL * a way to identify himself (preferably by having a GPG key signed by an existing Debian Developer or, alternatively, by sending in a photo of his drivers license or passport signed digitally with his GPG key) I don't think you can pass the NM queue without a signed GPG key nowadays. -- Oohara Yuuma [EMAIL PROTECTED] Debian developer PGP key (key ID F464A695) http://www.interq.or.jp/libra/oohara/pub-key.txt Key fingerprint = 6142 8D07 9C5B 159B C170 1F4A 40D6 F42E F464 A695 Let's cry that we do not have a clue. --- Junichi Uekawa, diary 2002/8/17
Re: Use of the BTS for managing sponsorship
On 29 Aug 2002 16:43:18 +0200, Tollef Fog Heen [EMAIL PROTECTED] wrote: | It is a matter of practice. The one Raphaël is proposing would not | be annoying at all. For me it would, because of the amount of noise. The BTS is quite noisy. I don't know why another pseudo package is necessary. How about the RFS (Request For Sponsor) request type of wnpp? Bugs against wnpp are not forwarded to -mentors by default, so it won't be flooded. The submitter may forward the initial request manually, but you will see it on -mentors anyway, whether Debian use the BTS or not. -- Oohara Yuuma [EMAIL PROTECTED] Debian developer PGP key (key ID F464A695) http://www.interq.or.jp/libra/oohara/pub-key.txt Key fingerprint = 6142 8D07 9C5B 159B C170 1F4A 40D6 F42E F464 A695 Better just encrypt it all in your head :-). --- Derrick 'dman' Hudson, about encryption without any physical medium -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Use of the BTS for managing sponsorship
On 29 Aug 2002 16:43:18 +0200, Tollef Fog Heen [EMAIL PROTECTED] wrote: | It is a matter of practice. The one Raphaël is proposing would not | be annoying at all. For me it would, because of the amount of noise. The BTS is quite noisy. I don't know why another pseudo package is necessary. How about the RFS (Request For Sponsor) request type of wnpp? Bugs against wnpp are not forwarded to -mentors by default, so it won't be flooded. The submitter may forward the initial request manually, but you will see it on -mentors anyway, whether Debian use the BTS or not. -- Oohara Yuuma [EMAIL PROTECTED] Debian developer PGP key (key ID F464A695) http://www.interq.or.jp/libra/oohara/pub-key.txt Key fingerprint = 6142 8D07 9C5B 159B C170 1F4A 40D6 F42E F464 A695 Better just encrypt it all in your head :-). --- Derrick 'dman' Hudson, about encryption without any physical medium
svgalib and suid root
I maintain zblast-svgalib, a svgalib game which has no suid bit (only sgid games). I got a bug report (#158058) complaining that the default configuration does not allow a normal user to play it. I know some other svgalib games are suid root (gravitywars, for example). 1. Does a svgalib game really require root privilege, or is rw access to some device file enough? 2. I have not audited zblast (not to mention svgalib) enough to justify suid root. Is there any good workaround[1]? A note in README.Debian about dpkg-statoverride? [1] A full audit is best, but you will get sick if you see the source of zblast. -- Oohara Yuuma [EMAIL PROTECTED] Debian developer PGP key (key ID F464A695) http://www.interq.or.jp/libra/oohara/pub-key.txt Key fingerprint = 6142 8D07 9C5B 159B C170 1F4A 40D6 F42E F464 A695 Better just encrypt it all in your head :-). --- Derrick 'dman' Hudson, about encryption without any physical medium
Re: debuild, dupload and then?
On Mon, 5 Aug 2002 18:59:54 -0600, Julian Gilbey [EMAIL PROTECTED] wrote: On Tue, Aug 06, 2002 at 07:14:18AM +0900, Oohara Yuuma wrote: On Sun, 4 Aug 2002 21:08:18 +0200, Holger Kubiak [EMAIL PROTECTED] wrote: Is there a tool that generates the /debian/dists/-tree? debarchiver (or the unpackaged katie) Something like dpkg-scanpackages maybe? Package: debarchiver Priority: optional Section: devel Installed-Size: 94 Maintainer: Ola Lundqvist [EMAIL PROTECTED] Architecture: all Version: 0.0.18 Depends: opalmod (= 0.1.6), dpkg-dev Filename: pool/main/d/debarchiver/debarchiver_0.0.18_all.deb Size: 17908 MD5Sum: 6316acaddd72a40c773e10084fd01b3f Description: Tool to handle debian package archives. This tool can create a potato like file structure that dselect, apt-get and similar tools can use for easier installation. . You just have to place the package files into a incoming directory and the tool does the sorting (if you place the generated '.changes' file there too). . OBSERVE! This package will create a cronjob that does the actual sorting. -- Oohara Yuuma [EMAIL PROTECTED] Debian developer PGP key (key ID F464A695) http://www.interq.or.jp/libra/oohara/pub-key.txt Key fingerprint = 6142 8D07 9C5B 159B C170 1F4A 40D6 F42E F464 A695 her occasionally near suicidal sense of loyal self-sacrifice --- Luke Seubert, about what Rei Ayanami and Debian developers have in common
Re: debuild, dupload and then?
On Sun, 4 Aug 2002 21:08:18 +0200, Holger Kubiak [EMAIL PROTECTED] wrote: Is there a tool that generates the /debian/dists/-tree? debarchiver (or the unpackaged katie) -- Oohara Yuuma [EMAIL PROTECTED] Debian developer PGP key (key ID F464A695) http://www.interq.or.jp/libra/oohara/pub-key.txt Key fingerprint = 6142 8D07 9C5B 159B C170 1F4A 40D6 F42E F464 A695 her occasionally near suicidal sense of loyal self-sacrifice --- Luke Seubert, about what Rei Ayanami and Debian developers have in common
Re: renaming a package
On Sun, 28 Jul 2002 13:04:07 +1000, Jamie Wilkinson [EMAIL PROTECTED] wrote: I intend to rename the glut packages from glutg3 glutg3-dev to libglut3 libglut-dev to follow the convention for library package naming. I prefer libglut3-dev . -- Oohara Yuuma [EMAIL PROTECTED] Debian developer PGP key (key ID F464A695) http://www.interq.or.jp/libra/oohara/pub-key.txt Key fingerprint = 6142 8D07 9C5B 159B C170 1F4A 40D6 F42E F464 A695 her occasionally near suicidal sense of loyal self-sacrifice --- Luke Seubert, about what Rei Ayanami and Debian developers have in common -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: renaming a package
On Sun, 28 Jul 2002 16:34:54 +0200 (CEST), Santiago Vila [EMAIL PROTECTED] wrote: On Sun, 28 Jul 2002, Oohara Yuuma wrote: I prefer libglut3-dev . We should make versioned -dev (binary) packages the exception, not the norm. libglut-dev is better. Think about libglut3-dev, libglut4-dev, libglut5-dev etc. and how libglut-dev makes upgrades much easier. 1. libfoo1 is compiled with libglut3 (that is, libglut-dev) 2. bar is compiled with libfoo1 3. libfoo1 is recompiled with libglut4 (that is, again, libglut-dev) 4. old bar does not work with new libfoo1 5. the maintainer of libfoo1 gets flamed because he/she is careless when using libglut-dev, though there is no good[1] way to specify a build-dependency to avoid this flame before libglut4 is released (that is, without knowing the version number of libglut-dev for libglut4) [1] Build-Depends: libglut-dev (= something) is suboptimal, and the fast way to get a FTBTS bug -- Oohara Yuuma [EMAIL PROTECTED] Debian developer PGP key (key ID F464A695) http://www.interq.or.jp/libra/oohara/pub-key.txt Key fingerprint = 6142 8D07 9C5B 159B C170 1F4A 40D6 F42E F464 A695 her occasionally near suicidal sense of loyal self-sacrifice --- Luke Seubert, about what Rei Ayanami and Debian developers have in common -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: renaming a package
On Sun, 28 Jul 2002 13:04:07 +1000, Jamie Wilkinson [EMAIL PROTECTED] wrote: I intend to rename the glut packages from glutg3 glutg3-dev to libglut3 libglut-dev to follow the convention for library package naming. I prefer libglut3-dev . -- Oohara Yuuma [EMAIL PROTECTED] Debian developer PGP key (key ID F464A695) http://www.interq.or.jp/libra/oohara/pub-key.txt Key fingerprint = 6142 8D07 9C5B 159B C170 1F4A 40D6 F42E F464 A695 her occasionally near suicidal sense of loyal self-sacrifice --- Luke Seubert, about what Rei Ayanami and Debian developers have in common -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: renaming a package
On Sun, 28 Jul 2002 16:34:54 +0200 (CEST), Santiago Vila [EMAIL PROTECTED] wrote: On Sun, 28 Jul 2002, Oohara Yuuma wrote: I prefer libglut3-dev . We should make versioned -dev (binary) packages the exception, not the norm. libglut-dev is better. Think about libglut3-dev, libglut4-dev, libglut5-dev etc. and how libglut-dev makes upgrades much easier. 1. libfoo1 is compiled with libglut3 (that is, libglut-dev) 2. bar is compiled with libfoo1 3. libfoo1 is recompiled with libglut4 (that is, again, libglut-dev) 4. old bar does not work with new libfoo1 5. the maintainer of libfoo1 gets flamed because he/she is careless when using libglut-dev, though there is no good[1] way to specify a build-dependency to avoid this flame before libglut4 is released (that is, without knowing the version number of libglut-dev for libglut4) [1] Build-Depends: libglut-dev (= something) is suboptimal, and the fast way to get a FTBTS bug -- Oohara Yuuma [EMAIL PROTECTED] Debian developer PGP key (key ID F464A695) http://www.interq.or.jp/libra/oohara/pub-key.txt Key fingerprint = 6142 8D07 9C5B 159B C170 1F4A 40D6 F42E F464 A695 her occasionally near suicidal sense of loyal self-sacrifice --- Luke Seubert, about what Rei Ayanami and Debian developers have in common -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Packaging assistance required
On Thu, 18 Jul 2002 15:22:33 +1000, Andrew Pollock [EMAIL PROTECTED] wrote: 1) Can filesystem permissions be set for the files in the .deb or are they supposed to be set by the postinstall script? You must set permissions of the files in .deb before you call dh_builddeb (or dpkg --build) in debian/rules. dh_fixperms works in most cases. 2) Can I include device files (for the chroot environment) in the .deb or do they need to be created by the postinstall script? Device files in .deb are not allowed (see the Policy, section 11.6). Call MAKEDEV in postinst. 3) If I have to create additional files by the postinstall script how to let dpkg know that they belong to package, or do I just have to add some rm's to the prerm/postrm scripts? There is no way (yet) to tell dpkg about files that are not in .deb . Use prerm/postrm. -- Oohara Yuuma [EMAIL PROTECTED] Debian developer PGP key (key ID F464A695) http://www.interq.or.jp/libra/oohara/pub-key.txt Key fingerprint = 6142 8D07 9C5B 159B C170 1F4A 40D6 F42E F464 A695 I don't die without living. --- TREASURE IKARUGA -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: auto-builders, how do they work?
On Wed, 17 Jul 2002 09:13:42 -0400, Matt Zimmerman [EMAIL PROTECTED] wrote: On Wed, Jul 17, 2002 at 06:14:25AM +0200, J?rgen H?gg wrote: (I searched the andrea web page (http://buildd.debian.org/andrea/) for the word 'conserver', but couldn't find it. So andrea was probably not the right place to look.) Go back to http://buildd.debian.org/ and select 'build log database', or go directly to http://buildd.debian.org/build.php. or http://people.debian.org/~igenibel/ -- Oohara Yuuma [EMAIL PROTECTED] Debian developer PGP key (key ID F464A695) http://www.interq.or.jp/libra/oohara/pub-key.txt Key fingerprint = 6142 8D07 9C5B 159B C170 1F4A 40D6 F42E F464 A695 I don't die without living. --- TREASURE IKARUGA -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Packaging assistance required
On Thu, 18 Jul 2002 15:22:33 +1000, Andrew Pollock [EMAIL PROTECTED] wrote: 1) Can filesystem permissions be set for the files in the .deb or are they supposed to be set by the postinstall script? You must set permissions of the files in .deb before you call dh_builddeb (or dpkg --build) in debian/rules. dh_fixperms works in most cases. 2) Can I include device files (for the chroot environment) in the .deb or do they need to be created by the postinstall script? Device files in .deb are not allowed (see the Policy, section 11.6). Call MAKEDEV in postinst. 3) If I have to create additional files by the postinstall script how to let dpkg know that they belong to package, or do I just have to add some rm's to the prerm/postrm scripts? There is no way (yet) to tell dpkg about files that are not in .deb . Use prerm/postrm. -- Oohara Yuuma [EMAIL PROTECTED] Debian developer PGP key (key ID F464A695) http://www.interq.or.jp/libra/oohara/pub-key.txt Key fingerprint = 6142 8D07 9C5B 159B C170 1F4A 40D6 F42E F464 A695 I don't die without living. --- TREASURE IKARUGA -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: auto-builders, how do they work?
On Wed, 17 Jul 2002 09:13:42 -0400, Matt Zimmerman [EMAIL PROTECTED] wrote: On Wed, Jul 17, 2002 at 06:14:25AM +0200, J?rgen H?gg wrote: (I searched the andrea web page (http://buildd.debian.org/andrea/) for the word 'conserver', but couldn't find it. So andrea was probably not the right place to look.) Go back to http://buildd.debian.org/ and select 'build log database', or go directly to http://buildd.debian.org/build.php. or http://people.debian.org/~igenibel/ -- Oohara Yuuma [EMAIL PROTECTED] Debian developer PGP key (key ID F464A695) http://www.interq.or.jp/libra/oohara/pub-key.txt Key fingerprint = 6142 8D07 9C5B 159B C170 1F4A 40D6 F42E F464 A695 I don't die without living. --- TREASURE IKARUGA -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Safe removal of a user while purging
On Sat, 29 Jun 2002 22:21:29 +0200, Magnus Ekdahl [EMAIL PROTECTED] wrote: I suggest using the useradd command to add a user and userdel command to remove it. Both commands belong to the passwd package which I suppose is essential, so always installed. Unfortunatly not. userdel clamav || true -- Oohara Yuuma [EMAIL PROTECTED] Debian developer PGP key (key ID F464A695) http://www.interq.or.jp/libra/oohara/pub-key.txt Key fingerprint = 6142 8D07 9C5B 159B C170 1F4A 40D6 F42E F464 A695 I don't die without living. --- TREASURE IKARUGA -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Safe removal of a user while purging
On Sat, 29 Jun 2002 22:21:29 +0200, Magnus Ekdahl [EMAIL PROTECTED] wrote: I suggest using the useradd command to add a user and userdel command to remove it. Both commands belong to the passwd package which I suppose is essential, so always installed. Unfortunatly not. userdel clamav || true -- Oohara Yuuma [EMAIL PROTECTED] Debian developer PGP key (key ID F464A695) http://www.interq.or.jp/libra/oohara/pub-key.txt Key fingerprint = 6142 8D07 9C5B 159B C170 1F4A 40D6 F42E F464 A695 I don't die without living. --- TREASURE IKARUGA -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: sponsor wanted
[Cc:ing to Debian JP developer list] On Fri, 21 Jun 2002 18:53:01 +0900, Botond Botyanszki [EMAIL PROTECTED] wrote: On Wed, 19 Jun 2002 23:40:11 +0900 (JST) Oohara Yuuma [EMAIL PROTECTED] wrote: http://gjiten.sourceforge.net So I'm looking for a sponsor who would upload it into debian. I looked at it. Comments: * This is not a Debian-native package, so you should provide both of .orig.tar.gz and .diff.gz . My package doesn't require an external patch (.diff.gz). As far as I understood from dpkg-source(1), if there are no external modifications, then the source package name doesn't need to contain .orig. I prefer a separate diff in this case, but you are the upstream, so I think Debian-native packaging is legal as long as the version number does not contain a hyphen. 1.1-1 is wrong. See chapter 4 of the Policy. From http://www.debian.org/doc/debian-policy/ap-pkg-sourcepkg.html: If there is no original source code - for example, if the package is specially prepared for Debian or the Debian maintainer is the same as the upstream maintainer - the format is slightly different: then there is no diff, and the tarfile is named package_version.tar.gz and contains a directory package-version. I missed the appendix. At least libgnome-dev and libdb3-dev are missing. libgnome-dev added. gjiten doesn't depend directly on libdb3, afaik gnome does. libgnome-dev should be suficient here I think. libgnome-dev seems sufficient. * You should not include INSTALL in .deb . The interesting thing is that dh_installdocs does this (BUG??). I had to append --exclude=INSTALL to it. Remove INSTALL from debian/docs . * Don't compile with -ggdb by default. Forgot to remove that before release. BTW, doesn't dh_strip get rid of all the debugging information ? dh_strip does the right thing, but this is a matter of policy. | Rationale: Using -g by default causes wasted CPU cycles since the | information is stripped away anyway; this can have a significant impact | on the efficiency of the autobuilders. (the Policy, version 3.5.6.0, section 11.1, footnote) * Being sponsored means you maintain the package. To maintain a package you need a Debian account and you need to apply the NM process if you don't have one, If you just want to see gjiten in Debian, file a RFP bug against wnpp. As I'm the upstream maintainer/developer I would like to maintain the debian package also. At least this is the recommended/preferred way I heard. I heard the opposite: it is better to put the burden of packaging correctly (that is, reading the entire policy, developers-reference, libpkg-guide, ...) on another person. I think upstream == .deb maintainer is ideal if the upstream has _enough_ time, though. It looks to me that applying for the NM and getting sponsored is not that easy as I thought, though I'll try do do everything possible I can. Filing a RFP bug is also fine with me, but I have a feeling that this will just sit there on the wishlist for months. or years Any recommendations? You may be interested in Debian JP. Although it is not a part of Debian, it has its own .deb archive, and many Japanese Debian developers are working for it. disclaimer * Debian JP is encouraging to integrating a package to Debian if it can be worldwide, that is, if it is useful even outside of Japan. * Debian JP does not release. * I am not a member of Debian JP. /disclaimer * According to language-env, the default LANG for Japanese environment is ja_JP.eucJP, not ja_JP . According to /etc/locale.alias, ja_JP is an alias for ja_JP.eucJP, so I think this is fine as ja_JP. I see ja_JP in /etc/locale.alias . I don't know a difference between ja_JP and ja_JP.eucJP . I fixed all the things you mentioned, updated packages are available from http://gjiten.sourceforge.net. -- Oohara Yuuma [EMAIL PROTECTED] Debian developer PGP key (key ID F464A695) http://www.interq.or.jp/libra/oohara/pub-key.txt Key fingerprint = 6142 8D07 9C5B 159B C170 1F4A 40D6 F42E F464 A695 I don't die without living. --- TREASURE IKARUGA -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: sponsor wanted
[Cc:ing to Debian JP developer list] On Fri, 21 Jun 2002 18:53:01 +0900, Botond Botyanszki [EMAIL PROTECTED] wrote: On Wed, 19 Jun 2002 23:40:11 +0900 (JST) Oohara Yuuma [EMAIL PROTECTED] wrote: http://gjiten.sourceforge.net So I'm looking for a sponsor who would upload it into debian. I looked at it. Comments: * This is not a Debian-native package, so you should provide both of .orig.tar.gz and .diff.gz . My package doesn't require an external patch (.diff.gz). As far as I understood from dpkg-source(1), if there are no external modifications, then the source package name doesn't need to contain .orig. I prefer a separate diff in this case, but you are the upstream, so I think Debian-native packaging is legal as long as the version number does not contain a hyphen. 1.1-1 is wrong. See chapter 4 of the Policy. From http://www.debian.org/doc/debian-policy/ap-pkg-sourcepkg.html: If there is no original source code - for example, if the package is specially prepared for Debian or the Debian maintainer is the same as the upstream maintainer - the format is slightly different: then there is no diff, and the tarfile is named package_version.tar.gz and contains a directory package-version. I missed the appendix. At least libgnome-dev and libdb3-dev are missing. libgnome-dev added. gjiten doesn't depend directly on libdb3, afaik gnome does. libgnome-dev should be suficient here I think. libgnome-dev seems sufficient. * You should not include INSTALL in .deb . The interesting thing is that dh_installdocs does this (BUG??). I had to append --exclude=INSTALL to it. Remove INSTALL from debian/docs . * Don't compile with -ggdb by default. Forgot to remove that before release. BTW, doesn't dh_strip get rid of all the debugging information ? dh_strip does the right thing, but this is a matter of policy. | Rationale: Using -g by default causes wasted CPU cycles since the | information is stripped away anyway; this can have a significant impact | on the efficiency of the autobuilders. (the Policy, version 3.5.6.0, section 11.1, footnote) * Being sponsored means you maintain the package. To maintain a package you need a Debian account and you need to apply the NM process if you don't have one, If you just want to see gjiten in Debian, file a RFP bug against wnpp. As I'm the upstream maintainer/developer I would like to maintain the debian package also. At least this is the recommended/preferred way I heard. I heard the opposite: it is better to put the burden of packaging correctly (that is, reading the entire policy, developers-reference, libpkg-guide, ...) on another person. I think upstream == .deb maintainer is ideal if the upstream has _enough_ time, though. It looks to me that applying for the NM and getting sponsored is not that easy as I thought, though I'll try do do everything possible I can. Filing a RFP bug is also fine with me, but I have a feeling that this will just sit there on the wishlist for months. or years Any recommendations? You may be interested in Debian JP. Although it is not a part of Debian, it has its own .deb archive, and many Japanese Debian developers are working for it. disclaimer * Debian JP is encouraging to integrating a package to Debian if it can be worldwide, that is, if it is useful even outside of Japan. * Debian JP does not release. * I am not a member of Debian JP. /disclaimer * According to language-env, the default LANG for Japanese environment is ja_JP.eucJP, not ja_JP . According to /etc/locale.alias, ja_JP is an alias for ja_JP.eucJP, so I think this is fine as ja_JP. I see ja_JP in /etc/locale.alias . I don't know a difference between ja_JP and ja_JP.eucJP . I fixed all the things you mentioned, updated packages are available from http://gjiten.sourceforge.net. -- Oohara Yuuma [EMAIL PROTECTED] Debian developer PGP key (key ID F464A695) http://www.interq.or.jp/libra/oohara/pub-key.txt Key fingerprint = 6142 8D07 9C5B 159B C170 1F4A 40D6 F42E F464 A695 I don't die without living. --- TREASURE IKARUGA -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: sponsor wanted
On Wed, 19 Jun 2002 12:43:25 +0900,
Botond Botyanszki [EMAIL PROTECTED] wrote:
I've been developing a Japanese dictionary package for gnome.
Debian and rpm packages have been around for quite a while and
it's now officially included in SuSE and TurboLinux, but not yet in Debian.
Packages are available from the project's site at sourceforge:
http://gjiten.sourceforge.net
So I'm looking for a sponsor who would upload it into debian.
I looked at it. Comments:
* This is not a Debian-native package, so you should provide
both of .orig.tar.gz and .diff.gz .
* debian/control says:
| Maintainer: B0Ti [EMAIL PROTECTED]
If you want to maintain a package in Debian, you should use
your real full name.
| Build-Depends: debhelper ( 3.0.0)
At least libgnome-dev and libdb3-dev are missing.
| Depends: ${shlibs:Depends}
| Suggests: kanjipad
gjiten doesn't work without a dictionary file, so gjiten must
depend on a package which provide one.
* You need to remove config.status and config.cache manually
in the clean target of debian/rules because make distclean
does nothing in the first run (there is no Makefile).
* You should not include INSTALL in .deb .
* Don't compile with -ggdb by default.
* lintian is your friend.
* Being sponsored means you maintain the package. To maintain
a package you need a Debian account and you need to apply
the NM process if you don't have one, If you just want to
see gjiten in Debian, file a RFP bug against wnpp.
* README.ja is broken (mojibake). (This is an upstream bug,
not a packaging problem.)
* I don't sponsor anyone who is not in the NM queue or
who doesn't have a GPG key signed by a Debian developer.
--
Oohara Yuuma [EMAIL PROTECTED]
Debian developer
PGP key (key ID F464A695) http://www.interq.or.jp/libra/oohara/pub-key.txt
Key fingerprint = 6142 8D07 9C5B 159B C170 1F4A 40D6 F42E F464 A695
I don't die without living.
--- TREASURE IKARUGA
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: sponsor wanted
On Wed, 19 Jun 2002 23:40:11 +0900 (JST), Oohara Yuuma [EMAIL PROTECTED] wrote: I looked at it. Comments: One more comment: * According to language-env, the default LANG for Japanese environment is ja_JP.eucJP, not ja_JP . -- Oohara Yuuma [EMAIL PROTECTED] Debian developer PGP key (key ID F464A695) http://www.interq.or.jp/libra/oohara/pub-key.txt Key fingerprint = 6142 8D07 9C5B 159B C170 1F4A 40D6 F42E F464 A695 I don't die without living. --- TREASURE IKARUGA -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
dpkg compresses diff file differently
dpkg compresses the diff file differently every time I build .deb . The uncompressed .diff is same. Is this an expected behavior? -- Oohara Yuuma [EMAIL PROTECTED] Debian developer PGP key (key ID F464A695) http://www.interq.or.jp/libra/oohara/pub-key.txt Key fingerprint = 6142 8D07 9C5B 159B C170 1F4A 40D6 F42E F464 A695 I always put away what I take. --- Ryuji Akai, Star away -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
dpkg compresses diff file differently
dpkg compresses the diff file differently every time I build .deb . The uncompressed .diff is same. Is this an expected behavior? -- Oohara Yuuma [EMAIL PROTECTED] Debian developer PGP key (key ID F464A695) http://www.interq.or.jp/libra/oohara/pub-key.txt Key fingerprint = 6142 8D07 9C5B 159B C170 1F4A 40D6 F42E F464 A695 I always put away what I take. --- Ryuji Akai, Star away -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Sponsor request for sjeng
On Tue, 28 May 2002 20:58:03 +0200 (MEST), Lukas Geyer [EMAIL PROTECTED] wrote: I changed one other detail, the default configuration file now gets installed in /usr/share/doc/sjeng/examples/, the manpage is updated accordingly. Updated version is available under the same address http://www.mathematik.uni-dortmund.de/lsix/geyer/debian It looks fine. I can sponsor you if you want. -- Oohara Yuuma [EMAIL PROTECTED] Debian developer PGP key (key ID F464A695) http://www.interq.or.jp/libra/oohara/pub-key.txt Key fingerprint = 6142 8D07 9C5B 159B C170 1F4A 40D6 F42E F464 A695 I always put away what I take. --- Ryuji Akai, Star away -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Sponsor request for numlockx
On Mon, 27 May 2002 12:16:13 +0100, Chris Jones [EMAIL PROTECTED] wrote: * Oohara Yuuma ([EMAIL PROTECTED]) wrote: I've just produced a package for the very simple program numlockx Ariel Shkedi [EMAIL PROTECTED] already filed ITP (see #146098). Oh right, I didn't know about ITP :) So how can I track Ariel's progress? Will the ticket get updated beyond the ITP as it moves towards being accepted into Debian? The ITP will be closed if the package is added to the Debian archive. If you want to know the status of the package before it is uploaded, you have to ask the submiter of ITP manually. -- Oohara Yuuma [EMAIL PROTECTED] Debian developer PGP key (key ID F464A695) http://www.interq.or.jp/libra/oohara/pub-key.txt Key fingerprint = 6142 8D07 9C5B 159B C170 1F4A 40D6 F42E F464 A695 I always put away what I take. --- Ryuji Akai, Star away -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Sponsor request for sjeng
On 25 May 2002 18:34:08 +0200, Lukas Geyer [EMAIL PROTECTED] wrote: I built a Debian package for sjeng, a chess engine which is capable of playing several variants (suicide, crazyhouse, bughouse) in addition to normal chess. It works fine with eboard and xboard, license is GPL, and there was a RFP for it, which I changed to ITP (#130019). Upstream source is at http://sjeng.sourceforge.net, my package (source and powerpc-binary) is at http://www.mathematik.uni-dortmund.de/lsix/geyer/debian It seems interesting. Some comments: debian/rules says: | ifneq (,$(findstring debug,$(DEB_BUILD_OPTIONS))) | CFLAGS += -g | endif This won't work because the upstream Makefile defines CFLAGS in it. Add export CFLAGS = -O2 before the ifneq line to control how ./configure defines CFLAGS. | ifeq (,$(findstring nostrip,$(DEB_BUILD_OPTIONS))) |INSTALL_PROGRAM += -s | endif This is unnecessary because the upstream does not strip the binary by default and dh_strip does the right thing. If you use debhelper version 3 or later, it marks every file in /etc as conffile even if the file is in debian/conffiles. Having debian/conffiles may cause a duplicated entry of Conffiles:. -- Oohara Yuuma [EMAIL PROTECTED] Debian developer PGP key (key ID F464A695) http://www.interq.or.jp/libra/oohara/pub-key.txt Key fingerprint = 6142 8D07 9C5B 159B C170 1F4A 40D6 F42E F464 A695 I always put away what I take. --- Ryuji Akai, Star away -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Sponsor request for numlockx
On Sun, 26 May 2002 03:38:09 +0100, Chris Jones [EMAIL PROTECTED] wrote: I've just produced a package for the very simple program numlockx (http://dforce.sh.cvut.cz/~seli/en/numlockx/) Ariel Shkedi [EMAIL PROTECTED] already filed ITP (see #146098). -- Oohara Yuuma [EMAIL PROTECTED] Debian developer PGP key (key ID F464A695) http://www.interq.or.jp/libra/oohara/pub-key.txt Key fingerprint = 6142 8D07 9C5B 159B C170 1F4A 40D6 F42E F464 A695 I always put away what I take. --- Ryuji Akai, Star away -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: changelog and /usr/share/doc/package as a symlink
On Sun, 28 Apr 2002 15:15:57 +0900, Junichi Uekawa [EMAIL PROTECTED] wrote: Is it not possible to include -x and -sdl version in the same package, which makes it in one package? It is possible if I rename the command name of one of them. Is it too large? Installed-Size: xsoldier-data 660 xsoldier 96 xsoldier-sdl 92 Also, is it worth having -x version when there is -sdl version ? -x version is useful if a user doesn't want to install SDL. (is both of them maintained in a good shape or is only one of them?) I don't know X very well, so SDL version will be better. Note: Splitting packages up causes more work, and maintenance cost. Yes, splitting a package sucks, but is it OK a X program package suddenly changes into a SDL program? If so, I will debianize xsoldier as a single package. -- Oohara Yuuma [EMAIL PROTECTED] Debian developer PGP key (key ID F464A695) http://www.interq.or.jp/libra/oohara/pub-key.txt Key fingerprint = 6142 8D07 9C5B 159B C170 1F4A 40D6 F42E F464 A695 I always put away what I take. --- Ryuji Akai, Star away -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: changelog and /usr/share/doc/package as a symlink
On Sat, 27 Apr 2002 10:01:29 -0700 (PDT), Sean 'Shaleh' Perry [EMAIL PROTECTED] wrote: Don't just split without good reason. I am planning to split xsolider into 3 packages because: * both raw X version and SDL version are available and only one of them is enough to play the game * I don't see any reason why each game engine should have its own copy of image data -- Oohara Yuuma [EMAIL PROTECTED] Debian developer PGP key (key ID F464A695) http://www.interq.or.jp/libra/oohara/pub-key.txt Key fingerprint = 6142 8D07 9C5B 159B C170 1F4A 40D6 F42E F464 A695 I always put away what I take. --- Ryuji Akai, Star away -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: how to package gpgp again
On 27 Apr 2002 08:49:06 +0200, Robert Bihlmeyer [EMAIL PROTECTED] wrote: The problem is that I hear gpgp is dead upstream. So unless someone (you?) takes up upstream maintainership, maybe it is still better for its users to migrate to seahorse. They can do this at their own pace, of course, as nobody will rip the old gpgp package from their harddisk. The upstream is not completely dead but not very active. According to the upstream webpage[1], the last release was in 1999, but the last patch accepted is dated on Mar/13/2002. I don't want to reinvent the wheel, so migration to seahorse or gpa will be necessary, perhaps by adding Suggests: gpa | seahorse to gpgp[2]? [1] http://www.geocities.com/SiliconValley/Chip/3708/gpgp/gpgp-curr.html [2] Recommends: is not dselect-friendly -- Oohara Yuuma [EMAIL PROTECTED] Debian developer PGP key (key ID F464A695) http://www.interq.or.jp/libra/oohara/pub-key.txt Key fingerprint = 6142 8D07 9C5B 159B C170 1F4A 40D6 F42E F464 A695 I always put away what I take. --- Ryuji Akai, Star away -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
changelog and /usr/share/doc/package as a symlink
Suppose that a source package makes two .deb, package-data and package (which depends on package-data), and /usr/share/doc/package is a symlink to /usr/share/doc/package-data . Should package depend on exactly the same version of package-data? allows any version - changelog may be out of date if only package is upgraded depneds on the same version - forces the user to download huge package-data on each upgrade -- Oohara Yuuma [EMAIL PROTECTED] Debian developer PGP key (key ID F464A695) http://www.interq.or.jp/libra/oohara/pub-key.txt Key fingerprint = 6142 8D07 9C5B 159B C170 1F4A 40D6 F42E F464 A695 I always put away what I take. --- Ryuji Akai, Star away -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: how to package gpgp again
On Sat, 27 Apr 2002 10:58:06 -0400, christophe barbé [EMAIL PROTECTED] wrote: Last time I checked (It was not yesterday), gpa was better than seahorse. I tested gpa 0.4.2-2 and it took more than 1 hour to start. I don't know about 0.4.3-2. -- Oohara Yuuma [EMAIL PROTECTED] Debian developer PGP key (key ID F464A695) http://www.interq.or.jp/libra/oohara/pub-key.txt Key fingerprint = 6142 8D07 9C5B 159B C170 1F4A 40D6 F42E F464 A695 I always put away what I take. --- Ryuji Akai, Star away -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: changelog and /usr/share/doc/package as a symlink
On Sat, 27 Apr 2002 10:01:29 -0700 (PDT), Sean 'Shaleh' Perry [EMAIL PROTECTED] wrote: Don't just split without good reason. I am planning to split xsolider into 3 packages because: * both raw X version and SDL version are available and only one of them is enough to play the game * I don't see any reason why each game engine should have its own copy of image data -- Oohara Yuuma [EMAIL PROTECTED] Debian developer PGP key (key ID F464A695) http://www.interq.or.jp/libra/oohara/pub-key.txt Key fingerprint = 6142 8D07 9C5B 159B C170 1F4A 40D6 F42E F464 A695 I always put away what I take. --- Ryuji Akai, Star away -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: how to package gpgp again
On 27 Apr 2002 08:49:06 +0200, Robert Bihlmeyer [EMAIL PROTECTED] wrote: The problem is that I hear gpgp is dead upstream. So unless someone (you?) takes up upstream maintainership, maybe it is still better for its users to migrate to seahorse. They can do this at their own pace, of course, as nobody will rip the old gpgp package from their harddisk. The upstream is not completely dead but not very active. According to the upstream webpage[1], the last release was in 1999, but the last patch accepted is dated on Mar/13/2002. I don't want to reinvent the wheel, so migration to seahorse or gpa will be necessary, perhaps by adding Suggests: gpa | seahorse to gpgp[2]? [1] http://www.geocities.com/SiliconValley/Chip/3708/gpgp/gpgp-curr.html [2] Recommends: is not dselect-friendly -- Oohara Yuuma [EMAIL PROTECTED] Debian developer PGP key (key ID F464A695) http://www.interq.or.jp/libra/oohara/pub-key.txt Key fingerprint = 6142 8D07 9C5B 159B C170 1F4A 40D6 F42E F464 A695 I always put away what I take. --- Ryuji Akai, Star away -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
changelog and /usr/share/doc/package as a symlink
Suppose that a source package makes two .deb, package-data and package (which depends on package-data), and /usr/share/doc/package is a symlink to /usr/share/doc/package-data . Should package depend on exactly the same version of package-data? allows any version - changelog may be out of date if only package is upgraded depneds on the same version - forces the user to download huge package-data on each upgrade -- Oohara Yuuma [EMAIL PROTECTED] Debian developer PGP key (key ID F464A695) http://www.interq.or.jp/libra/oohara/pub-key.txt Key fingerprint = 6142 8D07 9C5B 159B C170 1F4A 40D6 F42E F464 A695 I always put away what I take. --- Ryuji Akai, Star away -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
how to package gpgp again
gpgp is removed by mistake --- the previous maintainer filed a remove gpgp bug and orphaned it, I adopted it but didn't close the remove gpgp bug. The crypt-in-main issue made the problem more complex: * The latest version in the Debian archive was 0.4-6 (in contrib). * I uploaded 0.4-7 to non-US before crypt-in-main transition. It was marked as NEW and never in the archive. * gpgp should be in main (gpgp contains no crypto code --- all crypto things are done by calling gpg) I admit seahorse is better than gpgp, but gpgp seems rather popular according to popcon, so I want to package gpgp again. What version number should I use (0.4-8?), and where should I upload (main or non-US)? -- Oohara Yuuma [EMAIL PROTECTED] Debian developer PGP key (key ID F464A695) http://www.interq.or.jp/libra/oohara/pub-key.txt Key fingerprint = 6142 8D07 9C5B 159B C170 1F4A 40D6 F42E F464 A695 I always put away what I take. --- Ryuji Akai, Star away -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
how to package gpgp again
gpgp is removed by mistake --- the previous maintainer filed a remove gpgp bug and orphaned it, I adopted it but didn't close the remove gpgp bug. The crypt-in-main issue made the problem more complex: * The latest version in the Debian archive was 0.4-6 (in contrib). * I uploaded 0.4-7 to non-US before crypt-in-main transition. It was marked as NEW and never in the archive. * gpgp should be in main (gpgp contains no crypto code --- all crypto things are done by calling gpg) I admit seahorse is better than gpgp, but gpgp seems rather popular according to popcon, so I want to package gpgp again. What version number should I use (0.4-8?), and where should I upload (main or non-US)? -- Oohara Yuuma [EMAIL PROTECTED] Debian developer PGP key (key ID F464A695) http://www.interq.or.jp/libra/oohara/pub-key.txt Key fingerprint = 6142 8D07 9C5B 159B C170 1F4A 40D6 F42E F464 A695 I always put away what I take. --- Ryuji Akai, Star away -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: splitting xsoldier
On Thu, 25 Apr 2002 02:21:37 +0200, Julien LEMOINE [EMAIL PROTECTED] wrote: On Thursday 25 April 2002 01:19, Oohara Yuuma wrote: 2) The current version of xsoldier puts its score file in /var/lib/games, which is wrong. According to the FHS, it must be in /var/games/xsoldier. Since both of xsoldier and xsoldier-sdl are the same game, they should share the same score file. I think xsoldier-data should handle it. How can I save the old score file? Copying it in postinst of xsoldier-data won't work because it is in xsoldier, not xsoldier-data (if xsoldier is unpacked first, the old score file will be removed). why don't you put the score filename in debian/conffiles ? The score file can't be a conffile because the xsoldier binary needs to modify it. -- Oohara Yuuma [EMAIL PROTECTED] Debian developer PGP key (key ID F464A695) http://www.interq.or.jp/libra/oohara/pub-key.txt Key fingerprint = 6142 8D07 9C5B 159B C170 1F4A 40D6 F42E F464 A695 I always put away what I take. --- Ryuji Akai, Star away -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: splitting xsoldier
On Thu, 25 Apr 2002 02:21:37 +0200, Julien LEMOINE [EMAIL PROTECTED] wrote: On Thursday 25 April 2002 01:19, Oohara Yuuma wrote: 2) The current version of xsoldier puts its score file in /var/lib/games, which is wrong. According to the FHS, it must be in /var/games/xsoldier. Since both of xsoldier and xsoldier-sdl are the same game, they should share the same score file. I think xsoldier-data should handle it. How can I save the old score file? Copying it in postinst of xsoldier-data won't work because it is in xsoldier, not xsoldier-data (if xsoldier is unpacked first, the old score file will be removed). why don't you put the score filename in debian/conffiles ? The score file can't be a conffile because the xsoldier binary needs to modify it. -- Oohara Yuuma [EMAIL PROTECTED] Debian developer PGP key (key ID F464A695) http://www.interq.or.jp/libra/oohara/pub-key.txt Key fingerprint = 6142 8D07 9C5B 159B C170 1F4A 40D6 F42E F464 A695 I always put away what I take. --- Ryuji Akai, Star away -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
splitting xsoldier
I am planning to take over xsoldier by mutual agreement of the current maintainer. The new upstream release of xsolider have both of X version and SDL version in the same source (using #ifdef). Splitting xsoldier into 3 packages seems the right thing: xsoldier - X version of binary xsoldier-sdl - SDL version of binary xsoldier-data - pixmap files for xsoldier I have 3 problems: 1) Is it OK just uploading the new source and .deb to split the package, or do I have to ITP xsoldier-sdl and xsoldier-data? 2) The current version of xsoldier puts its score file in /var/lib/games, which is wrong. According to the FHS, it must be in /var/games/xsoldier. Since both of xsoldier and xsoldier-sdl are the same game, they should share the same score file. I think xsoldier-data should handle it. How can I save the old score file? Copying it in postinst of xsoldier-data won't work because it is in xsoldier, not xsoldier-data (if xsoldier is unpacked first, the old score file will be removed). 3) Do I have to save the old score file in any way? The new version of xsoldier uses the same format for the score file, but the score is inflated, so anyone can beat the old high score easily. I don't think the score file is compatible in a gamer's view. -- Oohara Yuuma [EMAIL PROTECTED] Debian developer PGP key (key ID F464A695) http://www.interq.or.jp/libra/oohara/pub-key.txt Key fingerprint = 6142 8D07 9C5B 159B C170 1F4A 40D6 F42E F464 A695 I always put away what I take. --- Ryuji Akai, Star away -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
splitting xsoldier
I am planning to take over xsoldier by mutual agreement of the current maintainer. The new upstream release of xsolider have both of X version and SDL version in the same source (using #ifdef). Splitting xsoldier into 3 packages seems the right thing: xsoldier - X version of binary xsoldier-sdl - SDL version of binary xsoldier-data - pixmap files for xsoldier I have 3 problems: 1) Is it OK just uploading the new source and .deb to split the package, or do I have to ITP xsoldier-sdl and xsoldier-data? 2) The current version of xsoldier puts its score file in /var/lib/games, which is wrong. According to the FHS, it must be in /var/games/xsoldier. Since both of xsoldier and xsoldier-sdl are the same game, they should share the same score file. I think xsoldier-data should handle it. How can I save the old score file? Copying it in postinst of xsoldier-data won't work because it is in xsoldier, not xsoldier-data (if xsoldier is unpacked first, the old score file will be removed). 3) Do I have to save the old score file in any way? The new version of xsoldier uses the same format for the score file, but the score is inflated, so anyone can beat the old high score easily. I don't think the score file is compatible in a gamer's view. -- Oohara Yuuma [EMAIL PROTECTED] Debian developer PGP key (key ID F464A695) http://www.interq.or.jp/libra/oohara/pub-key.txt Key fingerprint = 6142 8D07 9C5B 159B C170 1F4A 40D6 F42E F464 A695 I always put away what I take. --- Ryuji Akai, Star away -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#144036: penguineyes-gnome: uses debconf in preinst but does not pre-depends it
Package: penguineyes-gnome Version: 0.10-21 Severity: serious [Cc:ing to debian-mentors because I don't know how to fix this bug. Yes, I am the maintainer of penguineyes, and I want to prevent penguineyes from entering woody.] penguineyes and penguineyes-gnome uses debconf in their preinst: case $1 in upgrade|install) if [ -n $2 ]; then if dpkg --compare-versions $2 \= 0.10-15 \ dpkg --compare-versions $2 \= 0.10-5 ; then . /usr/share/debconf/confmodule db_unregister penguineyes/theme fi fi ;; esac This _seems_ to be a fix for #122809 (I adopted penguineyes recently and don't know what happened to it). What should I do? Pre-Depends: debconf (= 0.2.17), move db_unregister to postinst or something else? -- System Information Debian Release: 2.2 Kernel Version: Linux grain 2.4.18 #1 Fri Mar 15 18:50:57 JST 2002 i686 unknown Versions of the packages penguineyes-gnome depends on: hi debconf1.0.18 Debian configuration management system hi gdk-imlib1 1.9.11-3 Gdk-Imlib is an imaging library for use with hi libart21.4.1.2-6 The Gnome canvas widget hi libc6 2.2.4-7GNU C Library: Shared libraries and Timezone hi libgnome32 1.4.1.2-6 The Gnome libraries hi libgnomesuppor 1.4.1.2-6 The Gnome libraries (Support libraries) hi libgnomeui32 1.4.1.2-6 The Gnome libraries (User Interface) hi libgnorba271.4.1.2-6 Gnome CORBA services hi libpanel-apple 1.4.0.4-12 Library for Gnome Panel applets hi xlibs 4.1.0-9X Window System client libraries ii libaudiofile0 0.2.3-4The Audiofile Library ii libdb3 3.2.9-14 Berkeley v3 Database Libraries [runtime] ii libesd00.2.23-3 Enlightened Sound Daemon - Shared libraries ii libglib1.2 1.2.10-4 The GLib library of C routines ii libgtk1.2 1.2.10-10 The GIMP Toolkit set of widgets for X ii liborbit0 0.5.15-1 Libraries for ORBit - a CORBA ORB libesd-alsa0Not installed or no info -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#144036: penguineyes-gnome: uses debconf in preinst but does not pre-depends it
Package: penguineyes-gnome Version: 0.10-21 Severity: serious [Cc:ing to debian-mentors because I don't know how to fix this bug. Yes, I am the maintainer of penguineyes, and I want to prevent penguineyes from entering woody.] penguineyes and penguineyes-gnome uses debconf in their preinst: case $1 in upgrade|install) if [ -n $2 ]; then if dpkg --compare-versions $2 \= 0.10-15 \ dpkg --compare-versions $2 \= 0.10-5 ; then . /usr/share/debconf/confmodule db_unregister penguineyes/theme fi fi ;; esac This _seems_ to be a fix for #122809 (I adopted penguineyes recently and don't know what happened to it). What should I do? Pre-Depends: debconf (= 0.2.17), move db_unregister to postinst or something else? -- System Information Debian Release: 2.2 Kernel Version: Linux grain 2.4.18 #1 Fri Mar 15 18:50:57 JST 2002 i686 unknown Versions of the packages penguineyes-gnome depends on: hi debconf1.0.18 Debian configuration management system hi gdk-imlib1 1.9.11-3 Gdk-Imlib is an imaging library for use with hi libart21.4.1.2-6 The Gnome canvas widget hi libc6 2.2.4-7GNU C Library: Shared libraries and Timezone hi libgnome32 1.4.1.2-6 The Gnome libraries hi libgnomesuppor 1.4.1.2-6 The Gnome libraries (Support libraries) hi libgnomeui32 1.4.1.2-6 The Gnome libraries (User Interface) hi libgnorba271.4.1.2-6 Gnome CORBA services hi libpanel-apple 1.4.0.4-12 Library for Gnome Panel applets hi xlibs 4.1.0-9X Window System client libraries ii libaudiofile0 0.2.3-4The Audiofile Library ii libdb3 3.2.9-14 Berkeley v3 Database Libraries [runtime] ii libesd00.2.23-3 Enlightened Sound Daemon - Shared libraries ii libglib1.2 1.2.10-4 The GLib library of C routines ii libgtk1.2 1.2.10-10 The GIMP Toolkit set of widgets for X ii liborbit0 0.5.15-1 Libraries for ORBit - a CORBA ORB libesd-alsa0Not installed or no info -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Urgency= ?
On 15 Apr 2002 20:47:36 +0200, Josselin Mouette [EMAIL PROTECTED] wrote: The urgency=low is clearly to be used for most uploads, and urgency=critical corresponds to security-related issues. However, I didn't find in the policy a clear explanation of when using the medium and high levels. Does medium corresponds to closing an important bug, a serious bug... ? Does anybody have a link explaining this ? Subscribe to (high volume) [EMAIL PROTECTED] . Some developers explain why the urgency is medium or high in the changelog. -- Oohara Yuuma [EMAIL PROTECTED] Debian developer PGP key (key ID F464A695) http://www.interq.or.jp/libra/oohara/pub-key.txt Key fingerprint = 6142 8D07 9C5B 159B C170 1F4A 40D6 F42E F464 A695 I always put away what I take. --- Ryuji Akai, Star away -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Urgency= ?
On 15 Apr 2002 20:47:36 +0200, Josselin Mouette [EMAIL PROTECTED] wrote: The urgency=low is clearly to be used for most uploads, and urgency=critical corresponds to security-related issues. However, I didn't find in the policy a clear explanation of when using the medium and high levels. Does medium corresponds to closing an important bug, a serious bug... ? Does anybody have a link explaining this ? Subscribe to (high volume) debian-devel-changes@lists.debian.org . Some developers explain why the urgency is medium or high in the changelog. -- Oohara Yuuma [EMAIL PROTECTED] Debian developer PGP key (key ID F464A695) http://www.interq.or.jp/libra/oohara/pub-key.txt Key fingerprint = 6142 8D07 9C5B 159B C170 1F4A 40D6 F42E F464 A695 I always put away what I take. --- Ryuji Akai, Star away -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: glimpse for debian?
On Fri, 05 Apr 2002 15:31:33 -0800, Golda Velez [EMAIL PROTECTED] wrote: Would debian want to distribute glimpse, given that its not GNU licensed? I've had emails from a few people saying something about wanting it to be part of debian again, I understand its been removed from the distribution. I'm interested in glimpse, but I have a problem. glimpse can't be in Debian because its license is not clear. Its license says: | Permission is granted to copy this software, to redistribute it | on a nonprofit basis, and to use it for any purpose, subject to | the following restrictions and understandings. It says nothing about modification and redistribution of modified works. Debian needs to tweak the upstream source for packaging. -- Oohara Yuuma [EMAIL PROTECTED] Debian developer PGP key (key ID F464A695) http://www.interq.or.jp/libra/oohara/pub-key.txt Key fingerprint = 6142 8D07 9C5B 159B C170 1F4A 40D6 F42E F464 A695 I always put away what I take. --- Ryuji Akai, Star away -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Package names case sensitive?
On Fri, 5 Apr 2002 14:42:55 +0200, Stefan Schwandter [EMAIL PROTECTED] wrote: I wouldn't have to, if I could call my source package JACK, and if the debian archives would treat it as a different package. Does this work? At least binary package names must be in all lower-case. The Policy says (in 2.3.1): | Package names must consist of lower case letters (`a-z'), digits | (`0-9'), plus (`+') and minus (`-') signs, and periods (`.'). They | must be at least two characters long and must contain at least one | letter. -- Oohara Yuuma [EMAIL PROTECTED] Debian developer PGP key (key ID F464A695) http://www.interq.or.jp/libra/oohara/pub-key.txt Key fingerprint = 6142 8D07 9C5B 159B C170 1F4A 40D6 F42E F464 A695 I always put away what I take. --- Ryuji Akai, Star away -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: glimpse for debian?
On Fri, 05 Apr 2002 15:31:33 -0800, Golda Velez [EMAIL PROTECTED] wrote: Would debian want to distribute glimpse, given that its not GNU licensed? I've had emails from a few people saying something about wanting it to be part of debian again, I understand its been removed from the distribution. I'm interested in glimpse, but I have a problem. glimpse can't be in Debian because its license is not clear. Its license says: | Permission is granted to copy this software, to redistribute it | on a nonprofit basis, and to use it for any purpose, subject to | the following restrictions and understandings. It says nothing about modification and redistribution of modified works. Debian needs to tweak the upstream source for packaging. -- Oohara Yuuma [EMAIL PROTECTED] Debian developer PGP key (key ID F464A695) http://www.interq.or.jp/libra/oohara/pub-key.txt Key fingerprint = 6142 8D07 9C5B 159B C170 1F4A 40D6 F42E F464 A695 I always put away what I take. --- Ryuji Akai, Star away -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Package names case sensitive?
On Fri, 5 Apr 2002 14:42:55 +0200, Stefan Schwandter [EMAIL PROTECTED] wrote: I wouldn't have to, if I could call my source package JACK, and if the debian archives would treat it as a different package. Does this work? At least binary package names must be in all lower-case. The Policy says (in 2.3.1): | Package names must consist of lower case letters (`a-z'), digits | (`0-9'), plus (`+') and minus (`-') signs, and periods (`.'). They | must be at least two characters long and must contain at least one | letter. -- Oohara Yuuma [EMAIL PROTECTED] Debian developer PGP key (key ID F464A695) http://www.interq.or.jp/libra/oohara/pub-key.txt Key fingerprint = 6142 8D07 9C5B 159B C170 1F4A 40D6 F42E F464 A695 I always put away what I take. --- Ryuji Akai, Star away -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
1.2 after 1.2pre
The upstream of zblast released 1.2 after he released 1.2pre. The problem is that dpkg thinks 1.2 is older than 1.2pre. So I asked him what I should do. He picked 1.2.1 for the Debian package, saying I very rarely use x.y.z versions, and I've never used them for zblast. Did I do something wrong here? I don't think an epoch is for such a case. -- Oohara Yuuma [EMAIL PROTECTED] Debian developer PGP key (key ID F464A695) http://www.interq.or.jp/libra/oohara/pub-key.txt Key fingerprint = 6142 8D07 9C5B 159B C170 1F4A 40D6 F42E F464 A695 I always put away what I take. --- Ryuji Akai, Star away -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
1.2 after 1.2pre
The upstream of zblast released 1.2 after he released 1.2pre. The problem is that dpkg thinks 1.2 is older than 1.2pre. So I asked him what I should do. He picked 1.2.1 for the Debian package, saying I very rarely use x.y.z versions, and I've never used them for zblast. Did I do something wrong here? I don't think an epoch is for such a case. -- Oohara Yuuma [EMAIL PROTECTED] Debian developer PGP key (key ID F464A695) http://www.interq.or.jp/libra/oohara/pub-key.txt Key fingerprint = 6142 8D07 9C5B 159B C170 1F4A 40D6 F42E F464 A695 I always put away what I take. --- Ryuji Akai, Star away -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Request for a sponsor (clisp)
On Fri, 15 Mar 2002 23:17:20 +, Will Newton [EMAIL PROTECTED] wrote: A program I use (GNU Common Lisp) is currently orphaned (#123279) and has a couple of RC bugs to it's name. I would like to adopt this package and also become a Debian developer. Obviously for this I would require a sponsor, so is anyone interested in sponsoring me for this package? BTW - I do realise that this package appears to be a portability PITA but I think I can cope with that. Please contact debian-qa as well. There was a discussion whether Architecture: of clisp should be changed to i386 (only) or not. -- Oohara Yuuma [EMAIL PROTECTED] Debian developer PGP key (key ID F464A695) http://www.interq.or.jp/libra/oohara/pub-key.txt Key fingerprint = 6142 8D07 9C5B 159B C170 1F4A 40D6 F42E F464 A695 I always put away what I take. --- Ryuji Akai, Star away -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Request for a sponsor (clisp)
On Fri, 15 Mar 2002 23:17:20 +, Will Newton [EMAIL PROTECTED] wrote: A program I use (GNU Common Lisp) is currently orphaned (#123279) and has a couple of RC bugs to it's name. I would like to adopt this package and also become a Debian developer. Obviously for this I would require a sponsor, so is anyone interested in sponsoring me for this package? BTW - I do realise that this package appears to be a portability PITA but I think I can cope with that. Please contact debian-qa as well. There was a discussion whether Architecture: of clisp should be changed to i386 (only) or not. -- Oohara Yuuma [EMAIL PROTECTED] Debian developer PGP key (key ID F464A695) http://www.interq.or.jp/libra/oohara/pub-key.txt Key fingerprint = 6142 8D07 9C5B 159B C170 1F4A 40D6 F42E F464 A695 I always put away what I take. --- Ryuji Akai, Star away
Re: dh_make and file package.files
On Fri, 8 Mar 2002 12:37:49 +0100, pp [EMAIL PROTECTED] wrote: I try to make debian library packages starting with dh_make. Is there any easy way to automagically create proper my_package.files in debian directory? Or am I to modify it by hand every time? I don't know debian/my_package.files, but dpkg-gencontrol (or dh_gencontrol) will create debian/files. -- Oohara Yuuma [EMAIL PROTECTED] Debian developer PGP key (key ID F464A695) http://www.interq.or.jp/libra/oohara/pub-key.txt Key fingerprint = 6142 8D07 9C5B 159B C170 1F4A 40D6 F42E F464 A695 I always put away what I take. --- Ryuji Akai, Star away -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: dh_make and file package.files
On Fri, 8 Mar 2002 12:37:49 +0100, pp [EMAIL PROTECTED] wrote: I try to make debian library packages starting with dh_make. Is there any easy way to automagically create proper my_package.files in debian directory? Or am I to modify it by hand every time? I don't know debian/my_package.files, but dpkg-gencontrol (or dh_gencontrol) will create debian/files. -- Oohara Yuuma [EMAIL PROTECTED] Debian developer PGP key (key ID F464A695) http://www.interq.or.jp/libra/oohara/pub-key.txt Key fingerprint = 6142 8D07 9C5B 159B C170 1F4A 40D6 F42E F464 A695 I always put away what I take. --- Ryuji Akai, Star away
Re: Getting Packages Into Debian
On Sun, 17 Feb 2002 16:59:23 +1100, Mitchell Smith [EMAIL PROTECTED] wrote: Also is there a way I can set up my own http / ftp site that can be used as a source for apt-get so people can install the unofficial packages? for a potato system and the http method: http://www.interq.or.jp/libra/oohara/apt-gettable/apt-gettable/index.html On a woody system, apt-ftparchive(1) (in the apt-utils package) is also available. It is almost the same as dpkg-scanpackages(8) or dpkg-scansources(8). The differences are: * If there are two or more versions of the same package in the binary tree, dpkg-scanpackages complains and picks one randomly, while apt-ftparchive generates the Packages file for every version. * If you use apt-ftparchive, the override file is completely optional. If it is not specified, the priority and the section of a package is scanned from the control file of the package. * Optionally, apt-ftparchive can generate the contents file. If you have root privilege on your web server, debarchiver may be useful. -- Oohara Yuuma [EMAIL PROTECTED] Graduate-school of Science, Kyoto University PGP key (key ID F464A695) http://www.interq.or.jp/libra/oohara/pub-key.txt Key fingerprint = 6142 8D07 9C5B 159B C170 1F4A 40D6 F42E F464 A695 I always put away what I take. --- Ryuji Akai, Star away -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Getting Packages Into Debian
On Sun, 17 Feb 2002 16:59:23 +1100, Mitchell Smith [EMAIL PROTECTED] wrote: Also is there a way I can set up my own http / ftp site that can be used as a source for apt-get so people can install the unofficial packages? for a potato system and the http method: http://www.interq.or.jp/libra/oohara/apt-gettable/apt-gettable/index.html On a woody system, apt-ftparchive(1) (in the apt-utils package) is also available. It is almost the same as dpkg-scanpackages(8) or dpkg-scansources(8). The differences are: * If there are two or more versions of the same package in the binary tree, dpkg-scanpackages complains and picks one randomly, while apt-ftparchive generates the Packages file for every version. * If you use apt-ftparchive, the override file is completely optional. If it is not specified, the priority and the section of a package is scanned from the control file of the package. * Optionally, apt-ftparchive can generate the contents file. If you have root privilege on your web server, debarchiver may be useful. -- Oohara Yuuma [EMAIL PROTECTED] Graduate-school of Science, Kyoto University PGP key (key ID F464A695) http://www.interq.or.jp/libra/oohara/pub-key.txt Key fingerprint = 6142 8D07 9C5B 159B C170 1F4A 40D6 F42E F464 A695 I always put away what I take. --- Ryuji Akai, Star away
ITA: osh and shhmsg
retitle 89433 ITA: osh -- Operator's Shell retitle 118143 ITA: shhmsg -- Library for displaying messages tags 89433 + pending tags 118143 + pending thanks [forwarding to debian-mentors@lists.debian.org because I asked for a sponsor on it] David Kimdon [EMAIL PROTECTED] offered to sponsor me. Now he is checking my packages of osh and shhmsg. -- Oohara Yuuma [EMAIL PROTECTED] Graduate-school of Science, Kyoto University PGP key (key ID F464A695) http://www.interq.or.jp/libra/oohara/pub-key.txt Key fingerprint = 6142 8D07 9C5B 159B C170 1F4A 40D6 F42E F464 A695 I always put away what I take. --- Ryuji Akai, Star away
ITA: grandfatherclock -- a clock that tolls time acoustically
retitle 100228 ITA: grandfatherclock -- a clock that tolls time acoustically thanks [forwarding to [EMAIL PROTECTED] because I asked for a sponsor on it] I adopt grandfatherclock (#100228). David Kimdon [EMAIL PROTECTED] will sponsor me because I am not a Debian developer yet. -- Oohara Yuuma [EMAIL PROTECTED] Graduate-school of Science, Kyoto University PGP key (key ID F464A695) http://www.interq.or.jp/libra/oohara/pub-key.txt Key fingerprint = 6142 8D07 9C5B 159B C170 1F4A 40D6 F42E F464 A695 I always put away what I take. --- Ryuji Akai, Star away -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
ITA: grandfatherclock -- a clock that tolls time acoustically
retitle 100228 ITA: grandfatherclock -- a clock that tolls time acoustically thanks [forwarding to debian-mentors@lists.debian.org because I asked for a sponsor on it] I adopt grandfatherclock (#100228). David Kimdon [EMAIL PROTECTED] will sponsor me because I am not a Debian developer yet. -- Oohara Yuuma [EMAIL PROTECTED] Graduate-school of Science, Kyoto University PGP key (key ID F464A695) http://www.interq.or.jp/libra/oohara/pub-key.txt Key fingerprint = 6142 8D07 9C5B 159B C170 1F4A 40D6 F42E F464 A695 I always put away what I take. --- Ryuji Akai, Star away
Re: non-developer adopting an orphaned package
On 17 Jan 2002 18:47:14 +0100, Robert Bihlmeyer [EMAIL PROTECTED] wrote: Hamish Moffatt [EMAIL PROTECTED] writes: On Wed, Jan 16, 2002 at 07:15:13PM +0900, Oohara Yuuma wrote: I want to adopt osh (#89433), but I am not a Debian developer. Is it OK just to change the title of the wnpp bug and find a sponsor? (I am in the NM queue.) Please find a sponsor first. Thanks. Maybe an additional tag for the intent to package/adopt if someone sponsors me would be good. patch tag with a pointer to a preliminary package? -- Oohara Yuuma [EMAIL PROTECTED] Graduate-school of Science, Kyoto University PGP key (key ID F464A695) http://www.interq.or.jp/libra/oohara/pub-key.txt Key fingerprint = 6142 8D07 9C5B 159B C170 1F4A 40D6 F42E F464 A695 I always put away what I take. --- Ryuji Akai, Star away -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: non-developer adopting an orphaned package
On 17 Jan 2002 18:47:14 +0100, Robert Bihlmeyer [EMAIL PROTECTED] wrote: Hamish Moffatt [EMAIL PROTECTED] writes: On Wed, Jan 16, 2002 at 07:15:13PM +0900, Oohara Yuuma wrote: I want to adopt osh (#89433), but I am not a Debian developer. Is it OK just to change the title of the wnpp bug and find a sponsor? (I am in the NM queue.) Please find a sponsor first. Thanks. Maybe an additional tag for the intent to package/adopt if someone sponsors me would be good. patch tag with a pointer to a preliminary package? -- Oohara Yuuma [EMAIL PROTECTED] Graduate-school of Science, Kyoto University PGP key (key ID F464A695) http://www.interq.or.jp/libra/oohara/pub-key.txt Key fingerprint = 6142 8D07 9C5B 159B C170 1F4A 40D6 F42E F464 A695 I always put away what I take. --- Ryuji Akai, Star away
Bug#118143: I want to adopt shhmsg
I want to adopt shhmsg (#118143), but I am not a Debian developer, so I can't change the title of the wnpp bug until I find a sponsor. If you are interested, please sponsor me. I changed the package name because soname is the right thing. My .deb of grandfatherclock is available at: http://www.interq.or.jp/libra/oohara/debian-unofficial/shhmsg_1.3.4.orig.tar.gz http://www.interq.or.jp/libra/oohara/debian-unofficial/shhmsg_1.3.4-3.diff.gz http://www.interq.or.jp/libra/oohara/debian-unofficial/shhmsg_1.3.4-3.dsc http://www.interq.or.jp/libra/oohara/debian-unofficial/shhmsg1-dev_1.3.4-3_i386.deb http://www.interq.or.jp/libra/oohara/debian-unofficial/shhmsg1_1.3.4-3_i386.deb It will fix unreported bugs such as: * the previous version stripped *.a with the -s option of install and broke it * the previous version was incorrectly packaged as a Debian native package * the target of the symlink libshhmsg.so was libshhmsg.so.1.3.4 but the dependency was not strict enough Dear sponsor, please upload .orig.tar.gz as well as other files. .orig.tar.gz has already been removed from unstable. -- Oohara Yuuma [EMAIL PROTECTED] Graduate-school of Science, Kyoto University PGP key (key ID F464A695) http://www.interq.or.jp/libra/oohara/pub-key.txt Key fingerprint = 6142 8D07 9C5B 159B C170 1F4A 40D6 F42E F464 A695 I always put away what I take. --- Ryuji Akai, Star away -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Bug#118143: I want to adopt shhmsg
On Tue, 22 Jan 2002 22:17:17 +0900 (JST), Oohara Yuuma [EMAIL PROTECTED] wrote: My .deb of grandfatherclock is available at: s/grandfatherclock/shhmsg/ -- Oohara Yuuma [EMAIL PROTECTED] Graduate-school of Science, Kyoto University PGP key (key ID F464A695) http://www.interq.or.jp/libra/oohara/pub-key.txt Key fingerprint = 6142 8D07 9C5B 159B C170 1F4A 40D6 F42E F464 A695 I always put away what I take. --- Ryuji Akai, Star away -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Bug#118143: I want to adopt shhmsg
On Tue, 22 Jan 2002 22:17:17 +0900 (JST), Oohara Yuuma [EMAIL PROTECTED] wrote: I changed the package name because soname is the right thing. Sorry, this will break snake4. I have already fixed it. http://www.interq.or.jp/libra/oohara/debian-unofficial/shhmsg_1.3.4.orig.tar.gz http://www.interq.or.jp/libra/oohara/debian-unofficial/shhmsg_1.3.4-3.diff.gz http://www.interq.or.jp/libra/oohara/debian-unofficial/shhmsg_1.3.4-3.dsc http://www.interq.or.jp/libra/oohara/debian-unofficial/shhmsg-dev_1.3.4-3_i386.deb http://www.interq.or.jp/libra/oohara/debian-unofficial/shhmsg_1.3.4-3_i386.deb Thanks to Junichi Uekawa [EMAIL PROTECTED] for enlightenment. -- Oohara Yuuma [EMAIL PROTECTED] Graduate-school of Science, Kyoto University PGP key (key ID F464A695) http://www.interq.or.jp/libra/oohara/pub-key.txt Key fingerprint = 6142 8D07 9C5B 159B C170 1F4A 40D6 F42E F464 A695 I always put away what I take. --- Ryuji Akai, Star away -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#118143: I want to adopt shhmsg
I want to adopt shhmsg (#118143), but I am not a Debian developer, so I can't change the title of the wnpp bug until I find a sponsor. If you are interested, please sponsor me. I changed the package name because soname is the right thing. My .deb of grandfatherclock is available at: http://www.interq.or.jp/libra/oohara/debian-unofficial/shhmsg_1.3.4.orig.tar.gz http://www.interq.or.jp/libra/oohara/debian-unofficial/shhmsg_1.3.4-3.diff.gz http://www.interq.or.jp/libra/oohara/debian-unofficial/shhmsg_1.3.4-3.dsc http://www.interq.or.jp/libra/oohara/debian-unofficial/shhmsg1-dev_1.3.4-3_i386.deb http://www.interq.or.jp/libra/oohara/debian-unofficial/shhmsg1_1.3.4-3_i386.deb It will fix unreported bugs such as: * the previous version stripped *.a with the -s option of install and broke it * the previous version was incorrectly packaged as a Debian native package * the target of the symlink libshhmsg.so was libshhmsg.so.1.3.4 but the dependency was not strict enough Dear sponsor, please upload .orig.tar.gz as well as other files. .orig.tar.gz has already been removed from unstable. -- Oohara Yuuma [EMAIL PROTECTED] Graduate-school of Science, Kyoto University PGP key (key ID F464A695) http://www.interq.or.jp/libra/oohara/pub-key.txt Key fingerprint = 6142 8D07 9C5B 159B C170 1F4A 40D6 F42E F464 A695 I always put away what I take. --- Ryuji Akai, Star away
Re: Bug#118143: I want to adopt shhmsg
On Tue, 22 Jan 2002 22:17:17 +0900 (JST), Oohara Yuuma [EMAIL PROTECTED] wrote: My .deb of grandfatherclock is available at: s/grandfatherclock/shhmsg/ -- Oohara Yuuma [EMAIL PROTECTED] Graduate-school of Science, Kyoto University PGP key (key ID F464A695) http://www.interq.or.jp/libra/oohara/pub-key.txt Key fingerprint = 6142 8D07 9C5B 159B C170 1F4A 40D6 F42E F464 A695 I always put away what I take. --- Ryuji Akai, Star away
Re: Bug#118143: I want to adopt shhmsg
On Tue, 22 Jan 2002 22:17:17 +0900 (JST), Oohara Yuuma [EMAIL PROTECTED] wrote: I changed the package name because soname is the right thing. Sorry, this will break snake4. I have already fixed it. http://www.interq.or.jp/libra/oohara/debian-unofficial/shhmsg_1.3.4.orig.tar.gz http://www.interq.or.jp/libra/oohara/debian-unofficial/shhmsg_1.3.4-3.diff.gz http://www.interq.or.jp/libra/oohara/debian-unofficial/shhmsg_1.3.4-3.dsc http://www.interq.or.jp/libra/oohara/debian-unofficial/shhmsg-dev_1.3.4-3_i386.deb http://www.interq.or.jp/libra/oohara/debian-unofficial/shhmsg_1.3.4-3_i386.deb Thanks to Junichi Uekawa [EMAIL PROTECTED] for enlightenment. -- Oohara Yuuma [EMAIL PROTECTED] Graduate-school of Science, Kyoto University PGP key (key ID F464A695) http://www.interq.or.jp/libra/oohara/pub-key.txt Key fingerprint = 6142 8D07 9C5B 159B C170 1F4A 40D6 F42E F464 A695 I always put away what I take. --- Ryuji Akai, Star away
Re: Bug#89433: I want to adopt osh
Sorry for a confusing example. I tried DEB_BUILD_OPTIONS=debug,nostrip debuild and it didn't work. I did some RTFM and found in debuild(1): ENVIRONMENT VARIABLES As environment variables can affect the building of a package, often unintentionally, debuild sanitises the environment by removing all environment variables except for TERM, HOME, LOGNAME, GNUPGHOME, PGPPASS, PGPPATH, FAKEROOTKEY, DEB_* and the locale variables LANG and LC_*. TERM is set to `dumb' if it is unset, and PATH is set to /usr/sbin:/usr/bin:/sbin:/bin:/usr/bin/X11. I missed DEB_* and drew a wrong conclusion, that is, debuild reset DEB_BUILD_OPTIONS. It is right to say that DEB_BUILD_OPTIONS=debug,nostrip debuild won't work, but it is pointless. The comment is already removed from my debian/rules. -- Oohara Yuuma [EMAIL PROTECTED] Graduate-school of Science, Kyoto University PGP key (key ID F464A695) http://www.interq.or.jp/libra/oohara/pub-key.txt Key fingerprint = 6142 8D07 9C5B 159B C170 1F4A 40D6 F42E F464 A695 I always put away what I take. --- Ryuji Akai, Star away
Bug#100228: I want to adopt grandfatherclock
I want to adopt grandfatherclock (#100228), but I am not a Debian developer, so I can't change the title of the wnpp bug until I find a sponsor. If you are interested, please sponsor me. David Amor [EMAIL PROTECTED], you retitled the wnpp bug to ITA (the retitle request was received by master.debian.org at Sat, 23 Jun 2001 14:16:00 -0500), but you have not uploaded your package yet, and Thomas Bushnell [EMAIL PROTECTED] retitled the wnpp bug to O again (it was at Thu, 03 Jan 2002 16:34:12 -0600). If you are still interested in adopting grandfatherclock, please send a comment to [EMAIL PROTECTED] and Cc: it to me. My .deb of grandfatherclock is available at: http://www.interq.or.jp/libra/oohara/debian-unofficial/grandfatherclock_1.0.1.orig.tar.gz http://www.interq.or.jp/libra/oohara/debian-unofficial/grandfatherclock_1.0.1-5.diff.gz http://www.interq.or.jp/libra/oohara/debian-unofficial/grandfatherclock_1.0.1-5.dsc http://www.interq.or.jp/libra/oohara/debian-unofficial/grandfatherclock_1.0.1-5_all.deb It will fix 2 of the 4 outstanding bugs (searching a wrong directory for a configuration file, and a typo in the package description)[1]. It basically parses the command line and the configuration file, and then just do cat *.au /dev/dsp, so I think it is suitable for a prospective maintainer. [1] The other 2 bugs are your *.au files are not good. I can't help them. One of those bugs is already forwarded to the upstream, but no new upstream version is available. -- Oohara Yuuma [EMAIL PROTECTED] Graduate-school of Science, Kyoto University PGP key (key ID F464A695) http://www.interq.or.jp/libra/oohara/pub-key.txt Key fingerprint = 6142 8D07 9C5B 159B C170 1F4A 40D6 F42E F464 A695 I always put away what I take. --- Ryuji Akai, Star away -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Bug#89433: I want to adopt osh
On Fri, 18 Jan 2002 23:21:23 +0900, Junichi Uekawa [EMAIL PROTECTED] wrote: Oohara Yuuma [EMAIL PROTECTED] cum veritate scripsit: debian/rules says: | # to compile with debugging information: | # $ debuild -e DEB_BUILD_OPTIONS=debug,nostrip | # (this won't work: | # DEB_BUILD_OPTIONS=debug,nostrip debuild) Note the word won't. That won't work, because it is syntactically incorrect, and also this is not a place to document how to write bash command lone. I cut and pasted debuild -e DEB_BUILD_OPTIONS=debug,nostrip and it worked. I can't see why this is syntactically incorrect. Delete 4 lines of comments in debian/rules is a wishlist bug. Anyway, I have already deleted them. Can you just make the patch smaller with -fatal(mes) +int fatal(mes) which looks much better. done o Why are you building the binary with -O3 -fomit-frame-pointer? I like optimization, but I don't know it well. Can you tell me a better option? Usually Anything more than -O2 has problems on some architectures, and it is not advisable to use anything more than -O2 unless you know what you are doing. s/-O3 -fomit-frame-pointer/-O2/ done o are you sending the mods to the upstream ? / have you contacted the upstream ? Not yet. Please do. done -- Oohara Yuuma [EMAIL PROTECTED] Graduate-school of Science, Kyoto University PGP key (key ID F464A695) http://www.interq.or.jp/libra/oohara/pub-key.txt Key fingerprint = 6142 8D07 9C5B 159B C170 1F4A 40D6 F42E F464 A695 I always put away what I take. --- Ryuji Akai, Star away -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#100228: I want to adopt grandfatherclock
I want to adopt grandfatherclock (#100228), but I am not a Debian developer, so I can't change the title of the wnpp bug until I find a sponsor. If you are interested, please sponsor me. David Amor [EMAIL PROTECTED], you retitled the wnpp bug to ITA (the retitle request was received by master.debian.org at Sat, 23 Jun 2001 14:16:00 -0500), but you have not uploaded your package yet, and Thomas Bushnell [EMAIL PROTECTED] retitled the wnpp bug to O again (it was at Thu, 03 Jan 2002 16:34:12 -0600). If you are still interested in adopting grandfatherclock, please send a comment to [EMAIL PROTECTED] and Cc: it to me. My .deb of grandfatherclock is available at: http://www.interq.or.jp/libra/oohara/debian-unofficial/grandfatherclock_1.0.1.orig.tar.gz http://www.interq.or.jp/libra/oohara/debian-unofficial/grandfatherclock_1.0.1-5.diff.gz http://www.interq.or.jp/libra/oohara/debian-unofficial/grandfatherclock_1.0.1-5.dsc http://www.interq.or.jp/libra/oohara/debian-unofficial/grandfatherclock_1.0.1-5_all.deb It will fix 2 of the 4 outstanding bugs (searching a wrong directory for a configuration file, and a typo in the package description)[1]. It basically parses the command line and the configuration file, and then just do cat *.au /dev/dsp, so I think it is suitable for a prospective maintainer. [1] The other 2 bugs are your *.au files are not good. I can't help them. One of those bugs is already forwarded to the upstream, but no new upstream version is available. -- Oohara Yuuma [EMAIL PROTECTED] Graduate-school of Science, Kyoto University PGP key (key ID F464A695) http://www.interq.or.jp/libra/oohara/pub-key.txt Key fingerprint = 6142 8D07 9C5B 159B C170 1F4A 40D6 F42E F464 A695 I always put away what I take. --- Ryuji Akai, Star away
Re: Bug#89433: I want to adopt osh
On Fri, 18 Jan 2002 23:21:23 +0900, Junichi Uekawa [EMAIL PROTECTED] wrote: Oohara Yuuma [EMAIL PROTECTED] cum veritate scripsit: debian/rules says: | # to compile with debugging information: | # $ debuild -e DEB_BUILD_OPTIONS=debug,nostrip | # (this won't work: | # DEB_BUILD_OPTIONS=debug,nostrip debuild) Note the word won't. That won't work, because it is syntactically incorrect, and also this is not a place to document how to write bash command lone. I cut and pasted debuild -e DEB_BUILD_OPTIONS=debug,nostrip and it worked. I can't see why this is syntactically incorrect. Delete 4 lines of comments in debian/rules is a wishlist bug. Anyway, I have already deleted them. Can you just make the patch smaller with -fatal(mes) +int fatal(mes) which looks much better. done o Why are you building the binary with -O3 -fomit-frame-pointer? I like optimization, but I don't know it well. Can you tell me a better option? Usually Anything more than -O2 has problems on some architectures, and it is not advisable to use anything more than -O2 unless you know what you are doing. s/-O3 -fomit-frame-pointer/-O2/ done o are you sending the mods to the upstream ? / have you contacted the upstream ? Not yet. Please do. done -- Oohara Yuuma [EMAIL PROTECTED] Graduate-school of Science, Kyoto University PGP key (key ID F464A695) http://www.interq.or.jp/libra/oohara/pub-key.txt Key fingerprint = 6142 8D07 9C5B 159B C170 1F4A 40D6 F42E F464 A695 I always put away what I take. --- Ryuji Akai, Star away
Bug#89433: I want to adopt osh
I want to adopt osh (#89433), but I am not a Debian developer, so I can't change the title of the wnpp bug until I find a sponsor. If you are interested, please sponsor me. My .deb of osh is available at: http://www.interq.or.jp/libra/oohara/debian-unofficial/osh_1.7.orig.tar.gz http://www.interq.or.jp/libra/oohara/debian-unofficial/osh_1.7-9.diff.gz http://www.interq.or.jp/libra/oohara/debian-unofficial/osh_1.7-9.dsc http://www.interq.or.jp/libra/oohara/debian-unofficial/osh_1.7-9_i386.deb Note that osh is a setuid root shell and it does *NOT* drop root privilege when it executes a command. Be extremely careful when you configure or use it. (osh is installed in /usr/sbin/osh and its permission is 4754. It is not for a normal user.) -- Oohara Yuuma [EMAIL PROTECTED] Graduate-school of Science, Kyoto University PGP key (key ID F464A695) http://www.interq.or.jp/libra/oohara/pub-key.txt Key fingerprint = 6142 8D07 9C5B 159B C170 1F4A 40D6 F42E F464 A695 I always put away what I take. --- Ryuji Akai, Star away -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
