Cucipop Package.
hi all, I am just trying to get the Bulletins function working and am having the trouble that bulletins are not remembered to have been deleted, and I remember reading something about this. I have installed all the db2 librarys but am wondering if the package was compiled with USE_DB? Thanks, Aaron Daniels
Re: RFC: Changing the NM system
On Sun, Dec 17, 2000 at 01:41:54PM +0100, Adrian Bunk wrote: > On 17 Dec 2000, Chuan-kai Lin wrote: > > without being a maintainer" and everything comes to a halt. The > > goals I stated for joining Debian includes: work on the Chinese > > translation of w.d.o and help with QA work for Chinese-specific > > packages. Okay, enough for background information... > > I haven't seen you doing any QA work until now. Did I miss something (I > can't remember having heard anything from you at the debian-qa mailing > list) or what are the reasons why you didn't start working on what you > want to do if this is one of the main goals of your Debian work? Well, you haven't heard about him doesn't mean that he wasn't doing it. :-) The two main packages that I know Chuan-kai has worked on fixing bugs are cce (helping fix some buffer overflow with Fumitoshi UKAI) and wdm in October. He has also worked on other areas e.g. Debian Chinese Project, and started a key-signing coordination page, as mentioned on the DWN. > When reading it you see that writing a single manual page is enough for > passing the current "Tasks & Skills" check to become a Debian developer. > Sorry, but I can't resist calling this kind of skills check a joke! Ahem, I have seen Chuan-kai's packaging and bug-fixing skills. Chuan-kai didn't only translate web pages. Or perhaps you weren't referring to the my check of Chuan-kai's skill as a "joke". Nonetheless, I see two ideals at work here, and finding the balance may be difficult: 1. Raising the NM entry requirement in order to improve Debian's quality. Which is a very good thing. 2. Raising the threshold too high, or even just the perceived notion, whether justified or not, that many NMs are unskilled, could make Debian more and more like an elitist society. I am quite satisfied with the current NM process. Of course, there is always room for improvement, and hence the recent discussions. Ensuring the new maintainer possesses sufficient skills is a good thing, but we must be careful not to overdo it. As for me, I am just glad that I became a Debian developer over 3 years ago, long before this was even an issue. Cheers, Anthony
Re: ipmasq: maintainer has gone AWOL?
* Michael Moerz <[EMAIL PROTECTED]> [20001219 01:30]: > I have tried to talk to Brian Bassett <[EMAIL PROTECTED]> directly > several times by email. The first email was sent at least 2 months > ago. The second was sent over than 1 month ago and since I have > sent the third about a week has passed by. I'd also send a message to debian-devel asking if anyone knows where he is. -- Martin Michlmayr [EMAIL PROTECTED]
qftp and bugs 71484, 53449
qftp has 2 outstanding important bugs listed above. One is almost a year old the other is over 3 months. It appears the developer is rather busy. I took the liberty of addressing 71484 with a patch to the BTS. If one of the DD's here would apply it and recompile, both bugs could be closed. Thanks Gordon Sadler pgpoiaDAajVe0.pgp Description: PGP signature
Re: ipmasq: maintainer has gone AWOL?
On Tue, 19 Dec 2000, Martin Michlmayr wrote: > > I'd also send a message to debian-devel asking if anyone knows where > he is. > Yeah, I'll do that. Thanx. -- kind regards, Michael Moerz
Bug#77413: marked as done (9menu Unable to execute prerm or postinst)
Your message dated Tue, 19 Dec 2000 20:39:04 +0100 with message-id <[EMAIL PROTECTED]> and subject line 9menu: Unable to execute prerm or postinst has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what I am talking about this indicates a serious mail system misconfiguration somewhere. Please contact me immediately.) Darren Benham (administrator, Debian Bugs database) -- Received: (at submit) by bugs.debian.org; 19 Nov 2000 05:05:28 + >From [EMAIL PROTECTED] Sat Nov 18 23:05:28 2000 Return-path: <[EMAIL PROTECTED]> Received: from krusty.csun.edu (csun.edu) [130.166.1.51] by master.debian.org with esmtp (Exim 3.12 1 (Debian)) id 13xMfP-0005oS-00; Sat, 18 Nov 2000 23:05:27 -0600 Received: from csun.edu ([EMAIL PROTECTED] [130.166.253.89]) by csun.edu (8.9.3 (MessagingDirect 1.0.2)/8.9.3) with ESMTP id VAA94186; Sat, 18 Nov 2000 21:05:18 -0800 (PST) Sender: [EMAIL PROTECTED] Message-ID: <[EMAIL PROTECTED]> Date: Sat, 18 Nov 2000 19:44:00 -0800 From: Albert Kinderman <[EMAIL PROTECTED]> X-Mailer: Mozilla 4.72 [en] (X11; I; Linux 2.2.17 i586) X-Accept-Language: en MIME-Version: 1.0 To: [EMAIL PROTECTED] Subject: 9menu Unable to execute prerm or postinst Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Delivered-To: [EMAIL PROTECTED] Package: 9menu Version: 1.4-10 While attempting to remove and then reinstall 9menu, I kept getting messages of the form dpkg (subprocess): unable to execute post-installation script: Exec format error (sometimes the message was about the pre-removal script: Exec format error) In looking at the scripts in /var/lib/dpkg/info, I noticed that every other package's scripts begin with #!/bin/sh -e The scripts for 9menu begin with the if statement. Could this be the problem? running linux 2.2.17, libc6 2.2-1 -- Albert Kinderman California State University, Northridge Department of Management Science [EMAIL PROTECTED] --- Received: (at 77413-done) by bugs.debian.org; 19 Dec 2000 19:38:09 + >From [EMAIL PROTECTED] Tue Dec 19 13:38:09 2000 Return-path: <[EMAIL PROTECTED]> Received: from viemta06.chello.at [195.34.133.56] by master.debian.org with esmtp (Exim 3.12 1 (Debian)) id 148SaO-VT-00; Tue, 19 Dec 2000 13:38:08 -0600 Received: from katze.cyrius.com ([213.47.247.121]) by viemta06.chello.at (InterMail vK.4.02.00.10 201-232-116-110 license 9caa03a7df1d31c048ffcc0d31ac5855) with ESMTP id <[EMAIL PROTECTED]>; Tue, 19 Dec 2000 20:38:02 +0100 Received: by katze.cyrius.com (Postfix, from userid 1000) id 4469F1819A; Tue, 19 Dec 2000 20:39:04 +0100 (MET) Date: Tue, 19 Dec 2000 20:39:04 +0100 From: Martin Michlmayr <[EMAIL PROTECTED]> To: [EMAIL PROTECTED] Cc: [EMAIL PROTECTED] Subject: 9menu: Unable to execute prerm or postinst Message-ID: <[EMAIL PROTECTED]> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i Delivered-To: [EMAIL PROTECTED] This bug has been fixed by an upload of An Le <[EMAIL PROTECTED]> The newest release is 1.4-10.1 (part of unstable) -- see http://packages.debian.org/9menu -- Martin Michlmayr [EMAIL PROTECTED]
Bug#78233: marked as done (9menu postinst and preinst scripts cannot run)
Your message dated Tue, 19 Dec 2000 20:39:04 +0100 with message-id <[EMAIL PROTECTED]> and subject line 9menu: Unable to execute prerm or postinst has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what I am talking about this indicates a serious mail system misconfiguration somewhere. Please contact me immediately.) Darren Benham (administrator, Debian Bugs database) -- Received: (at submit) by bugs.debian.org; 28 Nov 2000 09:40:57 + >From [EMAIL PROTECTED] Tue Nov 28 03:40:57 2000 Return-path: <[EMAIL PROTECTED]> Received: from elysium.uwa.edu.au [130.95.128.2] (root) by master.debian.org with esmtp (Exim 3.12 1 (Debian)) id 140hFv-0004Kn-00; Tue, 28 Nov 2000 03:40:55 -0600 Received: from cyllene.uwa.edu.au ([EMAIL PROTECTED] [130.95.128.7]) by elysium.uwa.edu.au (8.11.1/8.10.2) with ESMTP id eAS9eoC11311 for <[EMAIL PROTECTED]>; Tue, 28 Nov 2000 17:40:50 +0800 (WST) Received: (from [EMAIL PROTECTED]) by cyllene.uwa.edu.au (8.11.1/8.10.2) id eAS9eou21510 for [EMAIL PROTECTED]; Tue, 28 Nov 2000 17:40:50 +0800 Date: Tue, 28 Nov 2000 16:11:46 +0800 From: Grahame Bowland <[EMAIL PROTECTED]> To: [EMAIL PROTECTED] Subject: 9menu postinst and preinst scripts cannot run Message-ID: <[EMAIL PROTECTED]> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.3i X-Mailer: Mutt 0.95.3i Delivered-To: [EMAIL PROTECTED] Package: 9menu dpkg operations (eg. `dpkg --purge 9menu`) failed for me with the message "exec format error" on Debian Woody. Looking at the problem, it seems that 9menu.postinst and 9menu.preinst in /var/lib/dpkg/info lack the line "#!/bin/sh" at the top - causing the error, as the files are then treated as a binary. Hope this is useful, Grahame -- Grahame Bowland University Communications Services, The University of Western Australia Phone: +61 8 9380 1175 --- Received: (at 77413-done) by bugs.debian.org; 19 Dec 2000 19:38:09 + >From [EMAIL PROTECTED] Tue Dec 19 13:38:09 2000 Return-path: <[EMAIL PROTECTED]> Received: from viemta06.chello.at [195.34.133.56] by master.debian.org with esmtp (Exim 3.12 1 (Debian)) id 148SaO-VT-00; Tue, 19 Dec 2000 13:38:08 -0600 Received: from katze.cyrius.com ([213.47.247.121]) by viemta06.chello.at (InterMail vK.4.02.00.10 201-232-116-110 license 9caa03a7df1d31c048ffcc0d31ac5855) with ESMTP id <[EMAIL PROTECTED]>; Tue, 19 Dec 2000 20:38:02 +0100 Received: by katze.cyrius.com (Postfix, from userid 1000) id 4469F1819A; Tue, 19 Dec 2000 20:39:04 +0100 (MET) Date: Tue, 19 Dec 2000 20:39:04 +0100 From: Martin Michlmayr <[EMAIL PROTECTED]> To: [EMAIL PROTECTED] Cc: [EMAIL PROTECTED] Subject: 9menu: Unable to execute prerm or postinst Message-ID: <[EMAIL PROTECTED]> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i Delivered-To: [EMAIL PROTECTED] This bug has been fixed by an upload of An Le <[EMAIL PROTECTED]> The newest release is 1.4-10.1 (part of unstable) -- see http://packages.debian.org/9menu -- Martin Michlmayr [EMAIL PROTECTED]
lockvc_3.9-2_i386.changes INSTALLED
Installing: lockvc_3.9-2_i386.deb to pool/main/l/lockvc/lockvc_3.9-2_i386.deb lockvc_3.9-2.diff.gz to pool/main/l/lockvc/lockvc_3.9-2.diff.gz lockvc_3.9-2.dsc to pool/main/l/lockvc/lockvc_3.9-2.dsc Announcing to debian-devel-changes@lists.debian.org Closing bugs: 79677 If the override file requires editing, file a bug on ftp.debian.org. Thank you for your contribution to Debian GNU.
Bug#79677: marked as done (lockvc kills all user's procs)
Your message dated Tue, 19 Dec 2000 15:02:26 -0500 with message-id <[EMAIL PROTECTED]> and subject line Bug#79677: fixed in lockvc 3.9-2 has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what I am talking about this indicates a serious mail system misconfiguration somewhere. Please contact me immediately.) Darren Benham (administrator, Debian Bugs database) -- Received: (at submit) by bugs.debian.org; 15 Dec 2000 15:39:39 + >From [EMAIL PROTECTED] Fri Dec 15 09:39:39 2000 Return-path: <[EMAIL PROTECTED]> Received: from justice.loyola.edu [144.126.178.227] (root) by master.debian.org with esmtp (Exim 3.12 1 (Debian)) id 146wxP-v7-00; Fri, 15 Dec 2000 09:39:39 -0600 Received: (from [EMAIL PROTECTED]) by justice.loyola.edu (8.9.3/8.9.3/Debian 8.9.3-21) id KAA32020 for [EMAIL PROTECTED]; Fri, 15 Dec 2000 10:39:37 -0500 Date: Fri, 15 Dec 2000 10:39:37 -0500 From: Michael Stone <[EMAIL PROTECTED]> To: [EMAIL PROTECTED] Subject: lockvc kills all user's procs Message-ID: <[EMAIL PROTECTED]> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i Delivered-To: [EMAIL PROTECTED] Package: lockvc Version: 3.9-1 Severity: grave The default for lockvc seems to have changed, so that it now logs the user out after 15 mins. It does that by killing *all* of the user's processes. If no one else jumps in, I'll NMU in the next few days. -- Mike Stone --- Received: (at 79677-close) by bugs.debian.org; 19 Dec 2000 20:08:56 + >From [EMAIL PROTECTED] Tue Dec 19 14:08:56 2000 Return-path: <[EMAIL PROTECTED]> Received: from auric.debian.org [206.246.226.45] (mail) by master.debian.org with esmtp (Exim 3.12 1 (Debian)) id 148T4B-0003La-00; Tue, 19 Dec 2000 14:08:56 -0600 Received: from troup by auric.debian.org with local (Exim 3.12 1 (Debian)) id 148Sxu-0005fY-00; Tue, 19 Dec 2000 15:02:26 -0500 From: Debian QA Group To: [EMAIL PROTECTED] Subject: Bug#79677: fixed in lockvc 3.9-2 Message-Id: <[EMAIL PROTECTED]> Sender: James Troup <[EMAIL PROTECTED]> Date: Tue, 19 Dec 2000 15:02:26 -0500 Delivered-To: [EMAIL PROTECTED] We believe that the bug you reported is fixed in the latest version of lockvc, which has been installed in the Debian FTP archive: lockvc_3.9-2_i386.deb to pool/main/l/lockvc/lockvc_3.9-2_i386.deb lockvc_3.9-2.diff.gz to pool/main/l/lockvc/lockvc_3.9-2.diff.gz lockvc_3.9-2.dsc to pool/main/l/lockvc/lockvc_3.9-2.dsc A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to [EMAIL PROTECTED], and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Debian QA Group (supplier of updated lockvc package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing [EMAIL PROTECTED]) -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Mon, 18 Dec 2000 20:27:31 +0100 Source: lockvc Binary: lockvc Architecture: source i386 Version: 3.9-2 Distribution: unstable Urgency: low Maintainer: Debian QA Group Changed-By: Martin Michlmayr <[EMAIL PROTECTED]> Description: lockvc - Program to lock your Linux console(s) Closes: 79677 Changes: lockvc (3.9-2) unstable; urgency=low . * Changed /etc/maxlock: don't log out user after 15 minutes (Closes: #79677). Files: 1661f993a76f40ec6bad5b8c4da6315f 621 misc optional lockvc_3.9-2.dsc 59fa0a18cc7c7aa06425d6362ca56fd5 3065 misc optional lockvc_3.9-2.diff.gz d3fd739d29662943f734a68ff0652f4b 39232 misc optional lockvc_3.9-2_i386.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.0.4 (GNU/Linux) Comment: For info see http://www.gnupg.org iEYEARECAAYFAjo+ZvUACgkQKb5dImj9VJ+NMQCeI6V282SlH2zda+gwJRZ2Cl7U dSsAniSnA/1JHAXmaPrM9wEBBPvB8Pqw =gP8g -END PGP SIGNATURE-
xwpe_1.5.25a-1_i386.changes INSTALLED
Installing: xwpe_1.5.25a-1_i386.deb to pool/main/x/xwpe/xwpe_1.5.25a-1_i386.deb xwpe_1.5.25a.orig.tar.gz to pool/main/x/xwpe/xwpe_1.5.25a.orig.tar.gz xwpe_1.5.25a-1.dsc to pool/main/x/xwpe/xwpe_1.5.25a-1.dsc xwpe_1.5.25a-1.diff.gz to pool/main/x/xwpe/xwpe_1.5.25a-1.diff.gz Announcing to debian-devel-changes@lists.debian.org Closing bugs: If the override file requires editing, file a bug on ftp.debian.org. Thank you for your contribution to Debian GNU.
Reporting WNPP bugs
I'd like to change the way WNPP bugs have to be reported slighlty. Currently, the WNPP pages (the authority) suggest to send mail to [EMAIL PROTECTED] The Developer's Reference suggests filing a bug _and_ sending a copy to debian-devel. I think it makes send to send a copy to debian-devel. However, I suggest that CC: should not be used, but the BTS feature X-Debbugs-CC (ie, a header line like: X-Debbugs-CC: debian-devel@lists.debian.org). The advantage is that a proper Reply-To header will be added before the message is posted to debian-devel, so all further discussion is also archieved in the BTS. Comments? If you think this is a good idea, I will go ahead and change the WNPP pages accordingly and file a bug against the developer's reference. -- Martin Michlmayr [EMAIL PROTECTED] pgpMAgxfuHTUo.pgp Description: PGP signature
Re: Reporting WNPP bugs
On Wed, Dec 20, 2000 at 01:14:21AM +0100, Martin Michlmayr wrote: > I'd like to change the way WNPP bugs have to be reported slighlty. You might want to CC: the WNPP maintainers when talking about their stuff... > Currently, the WNPP pages (the authority) suggest to send mail > to [EMAIL PROTECTED] The Developer's Reference suggests filing a > bug _and_ sending a copy to debian-devel. > > I think it makes send to send a copy to debian-devel. However, I > suggest that CC: should not be used, but the BTS feature X-Debbugs-CC > (ie, a header line like: X-Debbugs-CC: debian-devel@lists.debian.org). > The advantage is that a proper Reply-To header will be added before > the message is posted to debian-devel, so all further discussion is > also archieved in the BTS. Adding a custom header to mails is probably not too obvious in most mailers so I doubt people will do this (most of them do mistakes already), but the change is fine with me. -- Digital Electronic Being Intended for Assassination and Nullification
