Closing BUGS on a package's changelog
Hello all, I submitted a package that included a Closes in the Changelog, but the package was rejected (it was built with dpkg-dev 1.9.14). I have uploaded a new version built with dpkg-dev 1.9.15 and it is now installed, but the bug closed in the rejected version has been ignored. My questions are: * Should I close the bug manually? * Is this the right behaviour or should the installer inspect all the changelog entries between the previous archive package and the last one? * If this happens to me again, shoud I move all the 'Close' tags on the REJECTED package to the last version? Thanks in advance, Sergio. -- Sergio Talens-Oliag <[EMAIL PROTECTED]> Key fingerprint = 29DF 544F 1BD9 548C 8F15 86EF 6770 052B B8C1 FA69
Re: Closing BUGS on a package's changelog
Thus spoke Sergio Talens-Oliag <[EMAIL PROTECTED]> on 2001-07-03 11:02:12: > Hello all, > > I submitted a package that included a Closes in the Changelog, but the > package was rejected (it was built with dpkg-dev 1.9.14). > > I have uploaded a new version built with dpkg-dev 1.9.15 and it is now > installed, but the bug closed in the rejected version has been ignored. > > My questions are: > > * Should I close the bug manually? > Yes. Mailing the .changes file to [EMAIL PROTECTED] is a good choice > * Is this the right behaviour or should the installer inspect all the > changelog entries between the previous archive package and the > last one? The installer should only check the last one, imho > > * If this happens to me again, shoud I move all the 'Close' tags on the > REJECTED package to the last version? > I saw something like this in some packages: * Fixed in previous upload: Closes #xxx, #yyy, #zzz That made sense to me Cheers, -- Gergely Nagy \ mhp/|8] pgpeuZOrYQi4M.pgp Description: PGP signature
Package naming
Hi! Can a single binary package have a different name than the source package it comes from? I am packaging the LysKOM tty-client, which has the upstream name tty-client, but I have received requests for renaming the Debian package to lyskom-tty-client. Can I do that without changing the name of the original archive, or is that a Bad Thing to do? -- \\// peter - http://www.softwolves.pp.se/ Statement concerning unsolicited e-mail according to Swedish law: http://www.softwolves.pp.se/peter/reklampost.html
Re: Closing BUGS on a package's changelog
On Tue, Jul 03, 2001 at 11:02:12AM +0200, Sergio Talens-Oliag wrote: > * Is this the right behaviour or should the installer inspect all the > changelog entries between the previous archive package and the last one? The installer doesn't look at the changelogs at all, it looks at the Closes: field in the .changes file you upload. The dpkg-dev tools fill this in using only the latest changelog entry by default, but can be made to use previous entries as well with the -v option.
How to package ?
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi Ive got a question how to do the following right: Im working on a library package (fidoconf) which has some binarys. So i build a libfidoconf0, libfidoconf0-dev and fidoconf-runtime Package. It depends on libsmapi but this is not a problem, i build this package yesterday. libsmapi and libfidoconf are part of the Husky-Project (a complete Fidonet Software Suite). More than 90% of all Husky-Programs depends on fidoconf and smapi. Fidoconf is a central library in this Project, its the one used for the Config. Every Programm calls Fidoconf to get his configuration. All Configuration is done in one file (most of the time, 90%). So, my Problem: a.) One Binary (from 8) in fidoconf-runtime is really neccessary for libfidoconf (or better: for the User): You can check your config for Syntax Errors. But the other Binaries are just goodies. What should i do ? Put the one binary file in the dev-Package and let libfidoconf depend on it ? Or put it in the shared file (policy says no), or should libfidoconf depend on the runtime file ? There is another problem with the Configuration File for the Husky Suite. It is just one central Config for all Programs which comes with fidoconf and is in /etc/fido/config. It is not really policy-clean (every package should have its own subdir in /etc) but its the Husky-Way, only one central config for all programs. So i provide the Config (as an example, no debconf) in the Fidoconf Package. But where ? If i depend on the runtime-package i put it into the runtime. If not it is better to put it into the shared library package i think. What do you say ? - -- bye Joerg GPG-Keyid: 0x1120D31B Fingerprint: A3D2 83A4 535D A826 F2AA 4348 8BDD 849C 1120 D31B -BEGIN PGP SIGNATURE- Version: GnuPG v1.0.6 (GNU/Linux) Comment: For info see http://www.gnupg.org iD8DBQE7Qccbi92EnBEg0xsRAo5CAJ9mjvbcVTmxfve7cqfkdtr7GIekPACfYSA7 Jo8xAXFyAQoD/odIyZnuty0= =weki -END PGP SIGNATURE-
Need an advocate.
Hiya, I'm just about to apply for New Maintainer, I've read Policy till it's coming out my ears, and built a few packages, and was wondering if anyone'd volunteer to be my advocate? The packages I've built are: ipsc, prips, libpoe-perl, libpoe-component-irc-perl, libpoe-component-client-http-perl, libpoe-component-client-dns-perl, libconfigreader-simple-perl, libfreedb-perl, qcheck, and xringd, which was orphaned by David Engel. They are all available from deb http://homepages.ihug.com.au/~skowalik/debian/ ./ deb-src coming very soon. Thanks, -- Steve "I'm a sysadmin because I couldn't beat a blind monkey in a coding contest." --Me pgpjW9FQGDT7D.pgp Description: PGP signature
Keysign request
Is there anyone in the Austin, TX area who would be able to get together this month to sign my new key (old one is expiring)? -- Taral <[EMAIL PROTECTED]> (This message is digitally signed. Please encrypt mail if possible.) "Any technology, no matter how primitive, is magic to those who don't understand it." -- Florence Ambrose pgpNxgcF35WwN.pgp Description: PGP signature
Re: [mentors] Keysign request
also sprach Taral (on Tue, 03 Jul 2001 01:21:56PM -0500): > Is there anyone in the Austin, TX area who would be able to get together > this month to sign my new key (old one is expiring)? um, can't you just change the expiration date and keep all signatures? martin; (greetings from the heart of the sun.) \ echo mailto: !#^."<*>"|tr "<*> mailto:"; [EMAIL PROTECTED] -- a life? where can i download that? pgpdF0lQiAC8Q.pgp Description: PGP signature
Re: [mentors] Keysign request
On Tue, Jul 03, 2001 at 08:27:49PM +0200, Martin F. Krafft wrote: > also sprach Taral (on Tue, 03 Jul 2001 01:21:56PM -0500): > > Is there anyone in the Austin, TX area who would be able to get together > > this month to sign my new key (old one is expiring)? > > um, can't you just change the expiration date and keep all signatures? No. Changing the expiration date invalidates the signatures. -- Taral <[EMAIL PROTECTED]> (This message is digitally signed. Please encrypt mail if possible.) "Any technology, no matter how primitive, is magic to those who don't understand it." -- Florence Ambrose pgpGIN1V32C6W.pgp Description: PGP signature
Re: [mentors] Keysign request
On Tue, Jul 03, 2001 at 01:41:44PM -0500, Taral wrote: > On Tue, Jul 03, 2001 at 08:27:49PM +0200, Martin F. Krafft wrote: > > also sprach Taral (on Tue, 03 Jul 2001 01:21:56PM -0500): > > > Is there anyone in the Austin, TX area who would be able to get together > > > this month to sign my new key (old one is expiring)? > > > > um, can't you just change the expiration date and keep all signatures? > > No. Changing the expiration date invalidates the signatures. I have changed my expiration date since getting signatures, and I can't get gpg to say the signatures are invalid. -- Harry Henry Gebel West Dover Hundred, Delaware GPG encrypted email gladly accepted. Key ID: B853FFFE Fingerprint: 15A6 F58D AEED 5680 B41A 61FE 5A5F BB51 B853 FFFE pgpggJQzKtinG.pgp Description: PGP signature
Re: [mentors] Keysign request
also sprach Taral (on Tue, 03 Jul 2001 01:41:44PM -0500): > On Tue, Jul 03, 2001 at 08:27:49PM +0200, Martin F. Krafft wrote: > > also sprach Taral (on Tue, 03 Jul 2001 01:21:56PM -0500): > > > Is there anyone in the Austin, TX area who would be able to get together > > > this month to sign my new key (old one is expiring)? > > > > um, can't you just change the expiration date and keep all signatures? > > No. Changing the expiration date invalidates the signatures. does it? [some lines omitted for brevity - operation on backup copy] fishbowl:~> gpg --edit-key 330c4a75 pub 1024D/330C4A75 created: 2001-06-20 expires: 2002-06-20 trust: sub 2048g/D99FEE8D created: 2001-06-20 expires: 2002-06-20 (1). Martin F. Krafft <[EMAIL PROTECTED]> Command> check uid Martin F. Krafft <[EMAIL PROTECTED]> sig! 330C4A75 2001-06-20 [self-signature] sig! 888354F7 2001-07-02 Richard Atterer <[EMAIL PROTECTED]> Command> expire Key is valid for? (0) 2y Key expires at Thu Jul 3 20:49:57 2003 CEST Is this correct (y/n)? y pub 1024D/330C4A75 created: 2001-06-20 expires: 2003-07-03 trust: sub 2048g/D99FEE8D created: 2001-06-20 expires: 2002-06-20 (1). Martin F. Krafft <[EMAIL PROTECTED]> Command> check uid Martin F. Krafft <[EMAIL PROTECTED]> sig! 330C4A75 2001-07-03 [self-signature] sig! 888354F7 2001-07-02 Richard Atterer <[EMAIL PROTECTED]> don't tell me i am just not getting this GPG/PGP business again. but maybe someone can tell me what the subkey (D99FEE8D) is? that's for encryption, right? that's not signed by anyone anyway, is it? cause i don't seem to be capable of changing the expiration date on that one. and besides, i noticed a lot of the keys on debian users are with expiration dates. that's a good thing (tm). but judging from the wast amounts of signatures some people have collected, i doubt that process takes place every year, again and again... martin; (greetings from the heart of the sun.) \ echo mailto: !#^."<*>"|tr "<*> mailto:"; [EMAIL PROTECTED] -- the young lady had an unusual list, linked in part to a structural weakness. she set no preconditions. pgpJP6zzqWIE0.pgp Description: PGP signature
Re: [mentors] Keysign request
On Tue, Jul 03, 2001 at 08:57:08PM +0200, Martin F. Krafft wrote: > Command> expire > Key is valid for? (0) 2y > Key expires at Thu Jul 3 20:49:57 2003 CEST > Is this correct (y/n)? y You are quite correct. Changing the expiry only requires recalculation of the self-signature, not all signatures. However, this updated key conflicts with the existing key on the keyservers. I don't really want to do that. I'd prefer to get my new key signed. Anyone? -- Taral <[EMAIL PROTECTED]> (This message is digitally signed. Please encrypt mail if possible.) "Any technology, no matter how primitive, is magic to those who don't understand it." -- Florence Ambrose pgpzGVeFcQZO0.pgp Description: PGP signature
Re: [mentors] Keysign request
On Tue, Jul 03, 2001 at 04:59:03PM -0500, Taral wrote: > > I'd prefer to get my new key signed. Anyone? you should be able to sign the new key with the old key to get it into the keyring. -john
Re: [mentors] Keysign request
On Tue, Jul 03, 2001 at 04:59:03PM -0500, Taral wrote: > You are quite correct. Changing the expiry only requires recalculation > of the self-signature, not all signatures. However, this updated key > conflicts with the existing key on the keyservers. I don't really want > to do that. Can't you just upload the new key to the keyserver? keyring.debian.org is the place to send changes to keys already in the keyring. You might also want to update your key on pgpkeys.mit.edu if a copy is to be found there. - Jimmy Kaplowitz [EMAIL PROTECTED] pgpbpglJKVwtD.pgp Description: PGP signature
Closing BUGS on a package's changelog
Hello all, I submitted a package that included a Closes in the Changelog, but the package was rejected (it was built with dpkg-dev 1.9.14). I have uploaded a new version built with dpkg-dev 1.9.15 and it is now installed, but the bug closed in the rejected version has been ignored. My questions are: * Should I close the bug manually? * Is this the right behaviour or should the installer inspect all the changelog entries between the previous archive package and the last one? * If this happens to me again, shoud I move all the 'Close' tags on the REJECTED package to the last version? Thanks in advance, Sergio. -- Sergio Talens-Oliag <[EMAIL PROTECTED]> Key fingerprint = 29DF 544F 1BD9 548C 8F15 86EF 6770 052B B8C1 FA69 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Closing BUGS on a package's changelog
Thus spoke Sergio Talens-Oliag <[EMAIL PROTECTED]> on 2001-07-03 11:02:12: > Hello all, > > I submitted a package that included a Closes in the Changelog, but the > package was rejected (it was built with dpkg-dev 1.9.14). > > I have uploaded a new version built with dpkg-dev 1.9.15 and it is now > installed, but the bug closed in the rejected version has been ignored. > > My questions are: > > * Should I close the bug manually? > Yes. Mailing the .changes file to ###[EMAIL PROTECTED] is a good choice > * Is this the right behaviour or should the installer inspect all the > changelog entries between the previous archive package and the > last one? The installer should only check the last one, imho > > * If this happens to me again, shoud I move all the 'Close' tags on the > REJECTED package to the last version? > I saw something like this in some packages: * Fixed in previous upload: Closes #xxx, #yyy, #zzz That made sense to me Cheers, -- Gergely Nagy \ mhp/|8] PGP signature
Package naming
Hi! Can a single binary package have a different name than the source package it comes from? I am packaging the LysKOM tty-client, which has the upstream name tty-client, but I have received requests for renaming the Debian package to lyskom-tty-client. Can I do that without changing the name of the original archive, or is that a Bad Thing to do? -- \\// peter - http://www.softwolves.pp.se/ Statement concerning unsolicited e-mail according to Swedish law: http://www.softwolves.pp.se/peter/reklampost.html -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Closing BUGS on a package's changelog
On Tue, Jul 03, 2001 at 11:02:12AM +0200, Sergio Talens-Oliag wrote: > * Is this the right behaviour or should the installer inspect all the > changelog entries between the previous archive package and the last one? The installer doesn't look at the changelogs at all, it looks at the Closes: field in the .changes file you upload. The dpkg-dev tools fill this in using only the latest changelog entry by default, but can be made to use previous entries as well with the -v option. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
How to package ?
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi Ive got a question how to do the following right: Im working on a library package (fidoconf) which has some binarys. So i build a libfidoconf0, libfidoconf0-dev and fidoconf-runtime Package. It depends on libsmapi but this is not a problem, i build this package yesterday. libsmapi and libfidoconf are part of the Husky-Project (a complete Fidonet Software Suite). More than 90% of all Husky-Programs depends on fidoconf and smapi. Fidoconf is a central library in this Project, its the one used for the Config. Every Programm calls Fidoconf to get his configuration. All Configuration is done in one file (most of the time, 90%). So, my Problem: a.) One Binary (from 8) in fidoconf-runtime is really neccessary for libfidoconf (or better: for the User): You can check your config for Syntax Errors. But the other Binaries are just goodies. What should i do ? Put the one binary file in the dev-Package and let libfidoconf depend on it ? Or put it in the shared file (policy says no), or should libfidoconf depend on the runtime file ? There is another problem with the Configuration File for the Husky Suite. It is just one central Config for all Programs which comes with fidoconf and is in /etc/fido/config. It is not really policy-clean (every package should have its own subdir in /etc) but its the Husky-Way, only one central config for all programs. So i provide the Config (as an example, no debconf) in the Fidoconf Package. But where ? If i depend on the runtime-package i put it into the runtime. If not it is better to put it into the shared library package i think. What do you say ? - -- bye Joerg GPG-Keyid: 0x1120D31B Fingerprint: A3D2 83A4 535D A826 F2AA 4348 8BDD 849C 1120 D31B -BEGIN PGP SIGNATURE- Version: GnuPG v1.0.6 (GNU/Linux) Comment: For info see http://www.gnupg.org iD8DBQE7Qccbi92EnBEg0xsRAo5CAJ9mjvbcVTmxfve7cqfkdtr7GIekPACfYSA7 Jo8xAXFyAQoD/odIyZnuty0= =weki -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Need an advocate.
Hiya, I'm just about to apply for New Maintainer, I've read Policy till it's coming out my ears, and built a few packages, and was wondering if anyone'd volunteer to be my advocate? The packages I've built are: ipsc, prips, libpoe-perl, libpoe-component-irc-perl, libpoe-component-client-http-perl, libpoe-component-client-dns-perl, libconfigreader-simple-perl, libfreedb-perl, qcheck, and xringd, which was orphaned by David Engel. They are all available from deb http://homepages.ihug.com.au/~skowalik/debian/ ./ deb-src coming very soon. Thanks, -- Steve "I'm a sysadmin because I couldn't beat a blind monkey in a coding contest." --Me PGP signature
Keysign request
Is there anyone in the Austin, TX area who would be able to get together this month to sign my new key (old one is expiring)? -- Taral <[EMAIL PROTECTED]> (This message is digitally signed. Please encrypt mail if possible.) "Any technology, no matter how primitive, is magic to those who don't understand it." -- Florence Ambrose PGP signature
Re: [mentors] Keysign request
also sprach Taral (on Tue, 03 Jul 2001 01:21:56PM -0500): > Is there anyone in the Austin, TX area who would be able to get together > this month to sign my new key (old one is expiring)? um, can't you just change the expiration date and keep all signatures? martin; (greetings from the heart of the sun.) \ echo mailto: !#^."<*>"|tr "<*> mailto:"; net@madduck -- a life? where can i download that? PGP signature
Re: [mentors] Keysign request
On Tue, Jul 03, 2001 at 08:27:49PM +0200, Martin F. Krafft wrote: > also sprach Taral (on Tue, 03 Jul 2001 01:21:56PM -0500): > > Is there anyone in the Austin, TX area who would be able to get together > > this month to sign my new key (old one is expiring)? > > um, can't you just change the expiration date and keep all signatures? No. Changing the expiration date invalidates the signatures. -- Taral <[EMAIL PROTECTED]> (This message is digitally signed. Please encrypt mail if possible.) "Any technology, no matter how primitive, is magic to those who don't understand it." -- Florence Ambrose PGP signature
Re: [mentors] Keysign request
On Tue, Jul 03, 2001 at 01:41:44PM -0500, Taral wrote: > On Tue, Jul 03, 2001 at 08:27:49PM +0200, Martin F. Krafft wrote: > > also sprach Taral (on Tue, 03 Jul 2001 01:21:56PM -0500): > > > Is there anyone in the Austin, TX area who would be able to get together > > > this month to sign my new key (old one is expiring)? > > > > um, can't you just change the expiration date and keep all signatures? > > No. Changing the expiration date invalidates the signatures. I have changed my expiration date since getting signatures, and I can't get gpg to say the signatures are invalid. -- Harry Henry Gebel West Dover Hundred, Delaware GPG encrypted email gladly accepted. Key ID: B853FFFE Fingerprint: 15A6 F58D AEED 5680 B41A 61FE 5A5F BB51 B853 FFFE PGP signature
Re: [mentors] Keysign request
also sprach Taral (on Tue, 03 Jul 2001 01:41:44PM -0500): > On Tue, Jul 03, 2001 at 08:27:49PM +0200, Martin F. Krafft wrote: > > also sprach Taral (on Tue, 03 Jul 2001 01:21:56PM -0500): > > > Is there anyone in the Austin, TX area who would be able to get together > > > this month to sign my new key (old one is expiring)? > > > > um, can't you just change the expiration date and keep all signatures? > > No. Changing the expiration date invalidates the signatures. does it? [some lines omitted for brevity - operation on backup copy] fishbowl:~> gpg --edit-key 330c4a75 pub 1024D/330C4A75 created: 2001-06-20 expires: 2002-06-20 trust: sub 2048g/D99FEE8D created: 2001-06-20 expires: 2002-06-20 (1). Martin F. Krafft <[EMAIL PROTECTED]> Command> check uid Martin F. Krafft <[EMAIL PROTECTED]> sig! 330C4A75 2001-06-20 [self-signature] sig! 888354F7 2001-07-02 Richard Atterer <[EMAIL PROTECTED]> Command> expire Key is valid for? (0) 2y Key expires at Thu Jul 3 20:49:57 2003 CEST Is this correct (y/n)? y pub 1024D/330C4A75 created: 2001-06-20 expires: 2003-07-03 trust: sub 2048g/D99FEE8D created: 2001-06-20 expires: 2002-06-20 (1). Martin F. Krafft <[EMAIL PROTECTED]> Command> check uid Martin F. Krafft <[EMAIL PROTECTED]> sig! 330C4A75 2001-07-03 [self-signature] sig! 888354F7 2001-07-02 Richard Atterer <[EMAIL PROTECTED]> don't tell me i am just not getting this GPG/PGP business again. but maybe someone can tell me what the subkey (D99FEE8D) is? that's for encryption, right? that's not signed by anyone anyway, is it? cause i don't seem to be capable of changing the expiration date on that one. and besides, i noticed a lot of the keys on debian users are with expiration dates. that's a good thing (tm). but judging from the wast amounts of signatures some people have collected, i doubt that process takes place every year, again and again... martin; (greetings from the heart of the sun.) \ echo mailto: !#^."<*>"|tr "<*> mailto:"; net@madduck -- the young lady had an unusual list, linked in part to a structural weakness. she set no preconditions. PGP signature
Re: [mentors] Keysign request
On Tue, Jul 03, 2001 at 08:57:08PM +0200, Martin F. Krafft wrote: > Command> expire > Key is valid for? (0) 2y > Key expires at Thu Jul 3 20:49:57 2003 CEST > Is this correct (y/n)? y You are quite correct. Changing the expiry only requires recalculation of the self-signature, not all signatures. However, this updated key conflicts with the existing key on the keyservers. I don't really want to do that. I'd prefer to get my new key signed. Anyone? -- Taral <[EMAIL PROTECTED]> (This message is digitally signed. Please encrypt mail if possible.) "Any technology, no matter how primitive, is magic to those who don't understand it." -- Florence Ambrose PGP signature
Re: [mentors] Keysign request
On Tue, Jul 03, 2001 at 04:59:03PM -0500, Taral wrote: > > I'd prefer to get my new key signed. Anyone? you should be able to sign the new key with the old key to get it into the keyring. -john -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: [mentors] Keysign request
On Tue, Jul 03, 2001 at 04:59:03PM -0500, Taral wrote: > You are quite correct. Changing the expiry only requires recalculation > of the self-signature, not all signatures. However, this updated key > conflicts with the existing key on the keyservers. I don't really want > to do that. Can't you just upload the new key to the keyserver? keyring.debian.org is the place to send changes to keys already in the keyring. You might also want to update your key on pgpkeys.mit.edu if a copy is to be found there. - Jimmy Kaplowitz [EMAIL PROTECTED] PGP signature
