Bug#407746: [URGENT] Please update debconf PO translation for the package libpam-ldap 180-1.7
Anyway, yes, it is a style question -- I just know that the question style is a style that Christian has specifically discouraged the use of in English. :) Not exactly. What I mostly intend to discourage is asking *two* questions, one in the short description and another one in the long description. This looks really weird when both are shown together (which is the default in Debian). So, this really applies to boolean templates. Hence the Please foobar construction when the need to repeat or rephrase the short description in the long description exists. For French translations we usually translate such Please enter sentences with Veuillez indiquerwhich is a polite construction, pretty formal.used quite widely in french localised software. In the case of select/string templates, the Dutch team apparently choosed to use a question as first sentence in the long description, which seems to be a fairly consistent choice when the short description is *not* a question. And it should not be a question as I really think that question style for such opened requests does sound like spoken language which is IMHO to be avoided in debconf templates. But, again, I wouldn't be shocked if a given team deliberately chooses to turn all such opened prompts to questions. The main point, IMHO, is keeping style consistency in order to give users the feeling of a smooth way to go from one package to another. Whether this is done one way or another is up to all teams, of course. signature.asc Description: Digital signature
Bug#407746: [URGENT] Please update debconf PO translation for the package libpam-ldap 180-1.7
This is a debconf short description, and the translation needs to fit on a single line in order to display correctly on 80-column terminals. podebconf-display-po show it correctly, but if it should be under 80 columns, let's change it. :-) Actually, the suggestion to fit in 80 columns is a recommendation, not an enforcement. On most debconf interfaces, short descriptions that extend over the 80 columns limit still display properly.however, they extend the size occupied by the short description partwhich may lead to undesirable effects, depending on the interface (think about text interface). Indeed, for many cases, the enforcement for short descriptions being kept short cannot really be achieved, so please see this as a strong recommendation and make all possible efforts to respect this...which you can in that case..:) signature.asc Description: Digital signature
Bug#229955: marked as done (xcircuit: Program opens main window and dies)
Your message dated Sun, 11 Mar 2007 12:54:22 + with message-id [EMAIL PROTECTED] and subject line Bug#229955: fixed in xcircuit 3.6.78.dfsg-1 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.) Debian bug tracking system administrator (administrator, Debian Bugs database) ---BeginMessage--- Package: xcircuit Version: 3.1.19-1 Severity: important Tags: sid When trying to run the program under powerpc, it opens the main window, and dies with the following error: [EMAIL PROTECTED]:~$ xcircuit Warning: locale not supported by C library, locale unchanged X Error of failed request: BadValue (integer parameter out of range for operation) Major opcode of failed request: 91 (X_QueryColors) Value in failed request: 0x1004d200 Serial number of failed request: 5913 Current serial number in output stream: 5913 I am running it under XFree86 Version 4.3.0 (DRI trunk, Debian unstable) with 1024x768 in 16bit. Same version in x86 running remotely against the same (powerpc) X server runs ok. Juan de la Figuera PGP Signature: 1024D/A6A125AE -- System Information: Debian Release: testing/unstable Architecture: powerpc Kernel: Linux ibuk3 2.4.20-ben10 #26 Mon Jun 23 00:06:34 CEST 2003 ppc Locale: LANG=es_ES, LC_CTYPE=es_ES (ignored: LC_ALL set to es_ES) Versions of packages xcircuit depends on: ii libc6 2.3.2.ds1-11 GNU C Library: Shared libraries an ii python2.3 2.3.3-4 An interactive high-level object-o ii xlibs 4.2.1-15 X Window System client libraries -- no debconf information ---End Message--- ---BeginMessage--- Source: xcircuit Source-Version: 3.6.78.dfsg-1 We believe that the bug you reported is fixed in the latest version of xcircuit, which is due to be installed in the Debian FTP archive: xcircuit_3.6.78.dfsg-1.diff.gz to pool/main/x/xcircuit/xcircuit_3.6.78.dfsg-1.diff.gz xcircuit_3.6.78.dfsg-1.dsc to pool/main/x/xcircuit/xcircuit_3.6.78.dfsg-1.dsc xcircuit_3.6.78.dfsg-1_i386.deb to pool/main/x/xcircuit/xcircuit_3.6.78.dfsg-1_i386.deb xcircuit_3.6.78.dfsg.orig.tar.gz to pool/main/x/xcircuit/xcircuit_3.6.78.dfsg.orig.tar.gz 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. Margarita Manterola [EMAIL PROTECTED] (supplier of updated xcircuit 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: Wed, 6 Dec 2006 11:11:48 -0300 Source: xcircuit Binary: xcircuit Architecture: source i386 Version: 3.6.78.dfsg-1 Distribution: unstable Urgency: low Maintainer: Margarita Manterola [EMAIL PROTECTED] Changed-By: Margarita Manterola [EMAIL PROTECTED] Description: xcircuit - Draw circuit schematics or almost anything Closes: 128764 226233 229955 380989 401609 Changes: xcircuit (3.6.78.dfsg-1) unstable; urgency=low . * New upstream release. - Works correctly in amd64 (Closes: #229955). - Drop python in favour of tcl support (Closes: #380989, #226233). * New maintainer (Closes: #401609). * Migrated from cdbs to debhelper. * Repackaged original sources due to licensing problems of the asg module. * Added extra menu entry for Apps/Technical (Closes: #128764) Files: 4c1ef52d4c7369fdcadc6a3c27fdd644 686 electronics extra xcircuit_3.6.78.dfsg-1.dsc b98d1c4abd19c85b9330c5a245c1dee3 1237380 electronics extra xcircuit_3.6.78.dfsg.orig.tar.gz 5c5ef4499bab0919f5cd6a49a9b58537 27801 electronics extra xcircuit_3.6.78.dfsg-1.diff.gz d29e8caa7dab2b5ea6c9bda5ad1c4ed1 495814 electronics optional xcircuit_3.6.78.dfsg-1_i386.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.6 (GNU/Linux) iD8DBQFFy7OUlAuUx1tI/64RAkwZAJ40iljgR/JW6318hQgTfZKW/NZ/aACgqOea +AHU9Boz78mkxBtMuQFxpHA= =5AkB -END PGP SIGNATURE- ---End Message---
Bug#410106: Info received (Any news ?)
tag 410106 pending thanks I've prepared a NMU of libpng from experimental, which does what vorlon suggested, symlinking libpng12.pc to libpng14.pc (as it's currently done with libpng.pc) The debdiff is attached to the bug report, it has correctly built gtk2-engines-xfce and I'm currently rebuilding all Xfce with it. When it's finished and when I have a sponsor, if you're ok with the diff, I'll have it uploaded to experimental Regards, -- Yves-Alexis diff -u libpng-1.4.0~beta16/debian/changelog libpng-1.4.0~beta16/debian/changelog --- libpng-1.4.0~beta16/debian/changelog +++ libpng-1.4.0~beta16/debian/changelog @@ -1,3 +1,11 @@ +libpng (1.4.0~beta16-0.1) experimental; urgency=low + + * Non-maintainer upload. + * Add a symlink from libpng14.pc to libpng12.pc so packages needing it and +pulling it from the Provides: field are happy. + + -- Yves-Alexis Perez [EMAIL PROTECTED] Sun, 11 Mar 2007 01:49:05 +0100 + libpng (1.4.0~beta16-0) experimental; urgency=low diff -u libpng-1.4.0~beta16/debian/rules libpng-1.4.0~beta16/debian/rules --- libpng-1.4.0~beta16/debian/rules +++ libpng-1.4.0~beta16/debian/rules @@ -98,6 +98,7 @@ install -d $(CURDIR)/debian/tmp/usr/lib/pkgconfig install libpng14.pc $(CURDIR)/debian/tmp/usr/lib/pkgconfig (cd $(CURDIR)/debian/tmp/usr/lib/pkgconfig ln -s -f libpng14.pc libpng.pc) + (cd $(CURDIR)/debian/tmp/usr/lib/pkgconfig ln -s -f libpng14.pc libpng12.pc) install -d $(CURDIR)/debian/tmp/usr/include/libpng14 install png.h pngconf.h $(CURDIR)/debian/tmp/usr/include/libpng14
Bug#413968: [php-maint] xmlrpc-epi turns out to be libxmlrpc in php
On Sun, 2007-03-11 at 17:44 +1100, Paul TBBle Hampson wrote: I'm suggesting either. I'm happy to maintain the package seperately, but I intend to go through the differences between the versions and confirm that they are compatible, and steal anything good from the php-bundled version, so in effect I'd be doing both. I'd also have to track upstream PHP in case they add anything else to the library in the future. So maybe a PHP package team member might want to be a co-maintainer... okay, perhaps we can revisit this after you're done. if you decide to use the upstream version we can see how hard it is to build php against that instead of the bundled code. if you decide you want to use the php-bundled version, then we should probably just generate it from the php5 source package directly. i don't use this extension myself, so in any event it would be wise to find someone who does so we can test that it still works :) A quick poke around the Internet suggested that the only patches being made by other distros to xmlrpc-epi are for gcc4, 64-bit and expat, but I haven't looked at the PHP-bundled version's changes yet, apart from verifying that the .h files match semanticly. did you check that visually, or did you use a utility like icheck? Hmm, I'd better check this now, all the files in the libxmlrpc directory carry the same copyright headers as the upstream xmlrpc-epi distribution (BSD-like), does the PHP license override them and prevent debundling? I'd like to keep the distinct package under its upstream license if possible, as it's very very permissive, and the seconde-life client is GPLd. if the files carry a copyright header i think that they override whatever the default PHP license might say, so i don't think it'd be a problem. sean signature.asc Description: This is a digitally signed message part
Bug#333052: race in the modules loader?
severity 333052 important thanks Ok, there's been precisely one report of this problem by a user in the last 9 months. While it's possible that there is still a race condition in module-init-tools, it seems unlikely that a real bug of this nature would have been hit by so few people when m-i-t is a package used by so many. In any case, even if there is still a real bug here, it does not appear to make the package unusable, so I don't see any reason to treat this as RC. -- Steve Langasek Give me a lever long enough and a Free OS Debian Developer to set it on, and I can move the world. [EMAIL PROTECTED] http://www.debian.org/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#413969: asterisk: Fails to start after not being able to find format_mp3.so
Hey Srdjan, This original message couldn't get through ;-( Mark -- Forwarded Message -- Subject: Mail delivery failed: returning message to sender Date: Sunday 11 March 2007 10:06 From: Mail Delivery System [EMAIL PROTECTED] To: [EMAIL PROTECTED] This message was created automatically by mail delivery software. A message that you sent could not be delivered to one or more of its recipients. This is a permanent error. The following address(es) failed: [EMAIL PROTECTED] SMTP error from remote mail server after initial connection: host mx.paradise.net.nz [203.97.33.212]: 554 mxin3-orange.clear.net.nz -- This is a copy of the message, including all the headers. -- Return-path: [EMAIL PROTECTED] Received: from [192.168.1.219] (helo=d620.purcell.homeip.net ident=Debian-exim) by bristol.purcell.id.au with esmtp (Exim 4.63) (envelope-from [EMAIL PROTECTED]) id 1HQKwT-0002lz-TI; Sun, 11 Mar 2007 10:06:29 + Received: from mark by d620.purcell.homeip.net with local (Exim 4.63) (envelope-from [EMAIL PROTECTED]) id 1HQKxI-0006BE-Gk; Sun, 11 Mar 2007 10:07:08 + From: Mark Purcell [EMAIL PROTECTED] Organization: Debian GNU/Linux To: Srdjan [EMAIL PROTECTED], [EMAIL PROTECTED] Date: Sun, 11 Mar 2007 10:07:03 + User-Agent: KMail/1.9.5 References: [EMAIL PROTECTED] [EMAIL PROTECTED] [EMAIL PROTECTED] In-Reply-To: [EMAIL PROTECTED] MIME-Version: 1.0 Content-Type: multipart/signed; boundary=nextPart2056324.noNVCBdctO; protocol=application/pgp-signature; micalg=pgp-sha1 Content-Transfer-Encoding: 7bit Message-Id: [EMAIL PROTECTED] X-SA-Exim-Connect-IP: 192.168.1.219 X-SA-Exim-Rcpt-To: [EMAIL PROTECTED], [EMAIL PROTECTED] X-SA-Exim-Mail-From: [EMAIL PROTECTED] X-Spam-Checker-Version: SpamAssassin 3.1.7-deb (2006-10-05) on debian X-Spam-Level: X-Spam-Status: No, score=-4.4 required=1.0 tests=ALL_TRUSTED,BAYES_00 autolearn=ham version=3.1.7-deb X-Spam-Report: * -1.8 ALL_TRUSTED Passed through trusted hosts only via SMTP * -2.6 BAYES_00 BODY: Bayesian spam probability is 0 to 1% * [score: 0.] Subject: Re: Bug#413969: asterisk: Fails to start after not being able to find format_mp3.so X-SA-Exim-Version: 4.2.1 (built Tue, 09 Jan 2007 17:23:22 +) X-SA-Exim-Scanned: Yes (on bristol.purcell.id.au) --nextPart2056324.noNVCBdctO Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline Srdjan, On Sunday 11 March 2007 03:50, Srdjan wrote: Hi, =20 Tzafrir Cohen wrote: Please provide a few more details: dpkg -l asterisk-addons =20 =20 There's no package asterisk-addons. There is an upstream package of asterisk-addons, which hasn't yet been packaged and loaded to Debian. This package is the source of the format_mp3.so module. I suspect that at one time you may of loaded this module. dpkg -S /usr/lib/asterisk/modules/format_mp3.so =20 wallace:~# dpkg -S /usr/lib/asterisk/modules/format_mp3.so dpkg: /usr/lib/asterisk/modules/format_mp3.so not found. =20 That's what I suspect - it dropped out somehow in 1.2.16 format_mp3.so has not been shipped by Debian. We are working on providing the asterisk-addons package, but it hasn't been released for Debian yet. ls -l /usr/lib/asterisk/modules/format_mp3.so grep format_mp3 /etc/asterisk/modules.conf =20 wallace:~# grep format_mp3 /etc/asterisk/modules.conf load =3D format_mp3.so The modules.conf file in Debian does not load format_mp3.so as we don't ship this module (yet). I suspect you have added the load =3D format_mp3.so directive which is causing the problem you are seeing. I would suggest you remove this load directive which should clear up your problem. Or you can just reinstall asterisk-config which will install the dpkg.orig version of the conf file. Once we get asterisk-addons packaged for Debian, then you might have=20 better success with format_mp3. Or you can see our work in progress at=20 http://pkg-voip.buildserver.net/debian/pool/main/a/asterisk-addons/ Mark --nextPart2056324.noNVCBdctO Content-Type: application/pgp-signature -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.6 (GNU/Linux) iD8DBQBF89TMoCzanz0IthIRAmmrAJ9xKh8Fv0Y8XntKCmmwXRX6wMakKwCgjKMN Z+iu1mX0FcVCcWMJxmELT4Y= =EFYi -END PGP SIGNATURE- --nextPart2056324.noNVCBdctO-- --- This message was created automatically by mail delivery software. A message that you sent could not be delivered to one or more of its recipients. This is a permanent error. The following address(es) failed: [EMAIL PROTECTED] SMTP error from remote mail server after initial connection: host mx.paradise.net.nz [203.97.33.212]: 554 mxin3-orange.clear.net.nz -- This is a copy of the message, including all the headers. -- Return-path: [EMAIL PROTECTED] Received: from [192.168.1.219] (helo=d620.purcell.homeip.net
Bug#386469: Debian: failed openbsd-inetd upgrade: plea for more info
Hello Tomas, On 10/03/2007, at 9:16 AM, Tomas Pospisek wrote: ... Note the line Stopping internet superserver: inetd.. This line is not present in ... Ben Low's report [2] (maybe just not visible there, since not the whole screen dump is included), ... My apologies for the overzealous trimming. I particularly recall that there was no 'Stopping internet superserver: inetd. line - I was expecting such a thing (normal debian daemon package upgrade procedure). My output was almost identical to Ken West's - only the specific list of packages to be upgraded, etc was different (and quite long for me - I hadn't updated in a while...) ... from which openbsd-inetd (or xinetd or netkit-inetd) you were upgrading from? With a bit of luck you should be able to find this information in either: /var/backups/dpkg.status* or in /var/log/aptitude* or in /var/log/ dpkg*. $ ls -rt /var/log/dpkg.log* | xargs zgrep -h inetd 2006-11-06 19:48:40 status installed netkit-inetd 0.10-10.3 2006-11-06 19:48:40 remove netkit-inetd 0.10-10.3 0.10-10.3 2006-11-06 19:48:40 status half-configured netkit-inetd 0.10-10.3 2006-11-06 19:48:40 status half-installed netkit-inetd 0.10-10.3 2006-11-06 19:48:40 status config-files netkit-inetd 0.10-10.3 2006-11-06 19:48:40 status config-files netkit-inetd 0.10-10.3 2006-11-06 19:57:28 install update-inetd none 4.27 2006-11-06 19:57:28 status half-installed update-inetd 4.27 2006-11-06 19:57:28 status unpacked update-inetd 4.27 2006-11-06 19:57:28 status unpacked update-inetd 4.27 2006-11-06 20:22:27 status unpacked update-inetd 4.27 2006-11-06 20:22:27 status half-configured update-inetd 4.27 2006-11-06 20:22:27 status installed update-inetd 4.27 2006-11-07 10:01:33 install openbsd-inetd none 0.20050402-3 2006-11-07 10:01:33 status half-installed openbsd-inetd 0.20050402-3 2006-11-07 10:01:33 status unpacked openbsd-inetd 0.20050402-3 2006-11-07 10:01:33 status unpacked openbsd-inetd 0.20050402-3 2006-11-07 10:02:54 status unpacked openbsd-inetd 0.20050402-3 2006-11-07 10:02:54 status unpacked openbsd-inetd 0.20050402-3 2006-11-07 10:02:54 status half-configured openbsd-inetd 0.20050402-3 2006-11-07 10:02:56 status installed openbsd-inetd 0.20050402-3 2006-11-22 16:20:48 upgrade update-inetd 4.27 4.27-0.2 2006-11-22 16:20:48 status half-configured update-inetd 4.27 2006-11-22 16:20:48 status unpacked update-inetd 4.27 2006-11-22 16:20:48 status half-installed update-inetd 4.27 2006-11-22 16:20:48 status half-installed update-inetd 4.27 2006-11-22 16:20:49 status unpacked update-inetd 4.27-0.2 2006-11-22 16:20:49 status unpacked update-inetd 4.27-0.2 2006-11-22 17:17:47 status unpacked update-inetd 4.27-0.2 2006-11-22 17:17:47 status half-configured update-inetd 4.27-0.2 2006-11-22 17:17:48 status installed update-inetd 4.27-0.2 2007-02-21 08:34:18 upgrade update-inetd 4.27-0.2 4.27-0.3 2007-02-21 08:34:18 status half-configured update-inetd 4.27-0.2 2007-02-21 08:34:18 status unpacked update-inetd 4.27-0.2 2007-02-21 08:34:18 status half-installed update-inetd 4.27-0.2 2007-02-21 08:34:19 status half-installed update-inetd 4.27-0.2 2007-02-21 08:34:19 status unpacked update-inetd 4.27-0.3 2007-02-21 08:34:19 status unpacked update-inetd 4.27-0.3 2007-02-21 08:34:20 upgrade openbsd-inetd 0.20050402-3 0.20050402-4 2007-02-21 08:34:20 status half-configured openbsd-inetd 0.20050402-3 2007-02-21 08:34:20 status unpacked openbsd-inetd 0.20050402-3 2007-02-21 08:34:20 status half-installed openbsd-inetd 0.20050402-3 2007-02-21 08:34:20 status half-installed openbsd-inetd 0.20050402-3 2007-02-21 08:34:20 status unpacked openbsd-inetd 0.20050402-4 2007-02-21 08:34:20 status unpacked openbsd-inetd 0.20050402-4 2007-02-21 08:57:57 status unpacked update-inetd 4.27-0.3 2007-02-21 08:57:57 status half-configured update-inetd 4.27-0.3 2007-02-21 08:57:58 status installed update-inetd 4.27-0.3 2007-02-21 08:58:00 status unpacked openbsd-inetd 0.20050402-4 2007-02-21 08:58:00 status unpacked openbsd-inetd 0.20050402-4 2007-02-21 08:58:00 status half-configured openbsd-inetd 0.20050402-4 2007-02-21 09:29:06 status half-configured openbsd-inetd 0.20050402-4 2007-02-21 09:30:12 status half-configured openbsd-inetd 0.20050402-4 2007-02-21 09:38:06 status half-configured openbsd-inetd 0.20050402-4 2007-02-21 09:43:06 status half-configured openbsd-inetd 0.20050402-4 2007-02-21 09:43:10 status half-configured openbsd-inetd 0.20050402-4 2007-02-21 09:44:26 status half-configured openbsd-inetd 0.20050402-4 2007-02-21 09:44:27 status installed openbsd-inetd 0.20050402-4 - going by the timestamp of my bug report, the successful installation line at 2007-02-21 09:44:27 was just after I manually stopped the daemon and re-upgraded. all inetd lines from /var/log/dpkg.log.1 (mtime 2007-02-21 09:44): 2007-02-21 08:34:18 upgrade update-inetd 4.27-0.2 4.27-0.3 2007-02-21 08:34:18 status half-configured update-inetd 4.27-0.2 2007-02-21 08:34:18 status unpacked update-inetd 4.27-0.2
Processed: Re: Bug#414280: Kernel 2.6.18 causes software to hang / use 100% CPU
Processing commands for [EMAIL PROTECTED]: reassign 414280 linux-2.6 Bug#414280: Kernel 2.6.18 causes software to hang / use 100% CPU Warning: Unknown package 'linux-image-2.6-' Bug reassigned from package `linux-image-2.6-*' to `linux-2.6'. -- Stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#414280: marked as done (Kernel 2.6.18 causes software to hang / use 100% CPU)
Your message dated Sun, 11 Mar 2007 14:04:05 +0100 with message-id [EMAIL PROTECTED] and subject line Bug#414280: Kernel 2.6.18 causes software to hang / use 100% CPU 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.) Debian bug tracking system administrator (administrator, Debian Bugs database) ---BeginMessage--- Package: linux-image-2.6-* Version: 2.6.17, 2.6.18 Severity: serious On amd64 processors, whenever which version (32-, or 64bit) of Debian is installed, some programs (e.g. verlihub) after short uptime use 100% CPU. I tested it on AMD Opteron 1210 with several kernels (and even distros), and it turned out that the kernel is the guilty. There's no log entry in syslog or application's logfile. No matter which platform release of kernel I use, apps always hang on 2.6.18. I suggest confirming this bug by someone else ( I haven't the foggiest idea why only some applications crash) and, in case of positive, changing the default kernel in Etch. Regards, Pawel 'woody' Drewniak ---End Message--- ---BeginMessage--- On Sat, Mar 10, 2007 at 04:46:38PM +0100, =?UTF-8?Q? Pawe=C5=82?= Drewniak wrote: On amd64 processors, whenever which version (32-, or 64bit) of Debian is installed, some programs (e.g. verlihub) after short uptime use 100% CPU. Your application is buggy. Bastian -- Sometimes a man will tell his bartender things he'll never tell his doctor. -- Dr. Phillip Boyce, The Menagerie (The Cage), stardate unknown. ---End Message---
Processed: Re: race in the modules loader?
Processing commands for [EMAIL PROTECTED]: severity 333052 important Bug#333052: race in the modules loader? Bug#333522: udev: modules randomly aren't loaded at startup - Unknown symbol Severity set to `important' from `grave' thanks Stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#407746: libpam-ldap upgrade breaks pam_ldap.conf and can't login
Il giorno sab, 10/03/2007 alle 14.43 -0800, Steve Langasek ha scritto: Hi Stephen, Here's the final NMU diff for the NMU which I'm uploading. The NMU will be uploaded to incoming shortly. [...] Hi Steve, I prepared a new upload for this package too. It has been ready for one week now since I was waiting for a few translation updates. Moreover I agreed with Stephen to hijack his packages libnss-ldap and libpam-ldap. I checked your diff and you made a better work than I did about the way /etc/pam_ldap.conf is updated. On my diff I probably better explained to use a host or uri for shared/ldapns/ldap-server. I even moved to a new upstream release, 183, that fixes 8 bugs. I would like to merge these two diffs, but I don't want to change again the debconf templates, so probably the best idea is to just use your diff plus the new Italian translation I added, maybe applied to 183 instead of 180. (I already checked your diff against the new upstream version: it fits perfectly.) So, if you want, I could send you the Italian translation and you may NMU the package. I would then start uploading 183 to unstable, once your NMU migrate into etch. Giuseppe -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#405606: marked as done (old version of client is not suitable for connecting to SixXS network)
Your message dated Sun, 11 Mar 2007 12:28:47 + with message-id [EMAIL PROTECTED] and subject line Bug#405610: fixed in aiccu 20070115-1 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.) Debian bug tracking system administrator (administrator, Debian Bugs database) ---BeginMessage--- Package: aiccu Version: 20050131-1 Severity: serious There are many problems with this upstream release of the SixXS client (it is nearly two years old!) The SixXS service has evolved, protocols have changed, and upstream no longer recommends the use of this extremely old version of the client. (C.f., the tor package, which is not being released with etch.) For instance, the AYIYA protocol implementation (necessary for clients to connect behind a NAT) is broken. -- Robert Edmonds [EMAIL PROTECTED] signature.asc Description: Digital signature ---End Message--- ---BeginMessage--- Source: aiccu Source-Version: 20070115-1 We believe that the bug you reported is fixed in the latest version of aiccu, which is due to be installed in the Debian FTP archive: aiccu_20070115-1.diff.gz to pool/main/a/aiccu/aiccu_20070115-1.diff.gz aiccu_20070115-1.dsc to pool/main/a/aiccu/aiccu_20070115-1.dsc aiccu_20070115-1_amd64.deb to pool/main/a/aiccu/aiccu_20070115-1_amd64.deb aiccu_20070115-1_i386.deb to pool/main/a/aiccu/aiccu_20070115-1_i386.deb aiccu_20070115.orig.tar.gz to pool/main/a/aiccu/aiccu_20070115.orig.tar.gz 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. Philipp Kern [EMAIL PROTECTED] (supplier of updated aiccu 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: Wed, 7 Feb 2007 02:51:36 +0100 Source: aiccu Binary: aiccu Architecture: amd64 i386 source Version: 20070115-1 Distribution: unstable Urgency: low Maintainer: Philipp Kern [EMAIL PROTECTED] Changed-By: Philipp Kern [EMAIL PROTECTED] Description: aiccu - SixXS Automatic IPv6 Connectivity Client Utility Closes: 366002 379766 388759 405606 405610 407026 Changes: aiccu (20070115-1) unstable; urgency=low . * Upload package with me as an interim maintainer. Anand orphaned this package in private mail to me. (Closes: #407026) * Upload to `main' because of licence change in 20070107. (Closes: #388759) * New upstream version with the packaging based upon the one provided by upstream in the source tarball. aiccu is now up-to-date which should fix issues when connecting to SixXS. (Closes: #405606, #405610, #379766) * Slight packaging changes: I made the packaging non-native and changed some permission bits, dependencies and files to conform to the Debian standards and to fix various Lintian warnings and errors. Please see the diff for details. * The amd64 binary package is included in the upload. (Closes: #366002) Files: 78d72415ccf22197d681fc62b4f92f09 43536 net optional aiccu_20070115-1_amd64.deb 9da28cdede41753991b49020f3752a12 586 net optional aiccu_20070115-1.dsc d0a56d7f80a5e8747519a2dd7c0eae44 70007 net optional aiccu_20070115.orig.tar.gz d86fa4d39eaca3cdd8110311c7cd4150 3804 net optional aiccu_20070115-1.diff.gz e907adf0f2e373e1deba27236ca119ce 42790 net optional aiccu_20070115-1_i386.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.6 (GNU/Linux) iD8DBQFFyTH97Ro5M7LPzdgRAiZJAKC0VLs6atJU8ni461IPPBn/s8VBtwCfX9/f wX77YfM9n6U4y9WDoPF37S0= =LaB0 -END PGP SIGNATURE- ---End Message---
Bug#414380: amaya does not start. X Window System error serial 10426 error_code 8 request_code 144 minor_code 5
Package: amaya Version: 9.53~dfsg.0-1 Severity: grave Justification: renders package unusable I can't start amaya, and I have this message : (amaya:2766): Gtk-CRITICAL **: gtk_widget_set_colormap: assertion `!GTK_WIDGET_REALIZED (widget)' failed The program 'amaya' received an X Window System error. This probably reflects a bug in the program. The error was 'BadMatch (invalid parameter attributes)'. (Details: serial 10426 error_code 8 request_code 144 minor_code 5) (Note to programmers: normally, X errors are reported asynchronously; that is, you will receive the error a while after causing it. To debug your program, run it with the --sync command line option to change this behavior. You can then get a meaningful backtrace from your debugger if you break on the gdk_x_error() function.) I use the unstable package. -- System Information: Debian Release: 4.0 APT prefers testing APT policy: (500, 'testing') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.18-4-686 Locale: [EMAIL PROTECTED], [EMAIL PROTECTED] (charmap=ISO-8859-15) Versions of packages amaya depends on: ii libc6 2.3.6.ds1-13 GNU C Library: Shared libraries ii libexpat1 1.95.8-3.4 XML parsing C library - runtime li ii libfreetype6 2.2.1-5FreeType 2 font engine, shared lib ii libgcc1 1:4.1.1-21 GCC support library ii libgl1-mesa-glx [libgl1] 6.5.1-0.6 A free implementation of the OpenG ii libglu1-mesa [libglu1]6.5.1-0.6 The OpenGL utility library (GLU) ii libjpeg62 6b-13 The Independent JPEG Group's JPEG ii libpng12-01.2.15~beta5-1 PNG library - runtime ii libraptor11.4.13-1 Raptor RDF parser and serializer l ii libstdc++64.1.1-21 The GNU Standard C++ Library v3 ii libwww-ssl0 5.4.0-11 The W3C-WWW library (SSL support) ii libwxbase2.6-02.6.3.2.1.5wxBase library (runtime) - non-GUI ii libwxgtk2.6-0 2.6.3.2.1.5wxWidgets Cross-platform C++ GUI t ii ttf-freefont 20060501cvs-10 Freefont Serif, Sans and Mono True ii zlib1g1:1.2.3-13 compression library - runtime amaya recommends no packages. -- no debconf information -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#413469: Please don't, there are people using it
Quotting Tuomo Valkonen: Why do you want a random broken and unsupported development snapshot? It works for me (and for my friends) just fine. I'm using it right now, as I recently switched from stable to testing just to get the idea about the upcoming Etch. Quotting Tuomo Valkonen: Can't you wait until a stable Ion3 is released (not that far away -- might even happen before Etch is released, depending on how things proceed), and install it by whatever means? Probably I could, but I like to install the system from single source (i.e. official Debian DVD). The need to fetch additional software from Internet is often problematic in some parts of this world. Quotting Tuomo Valkonen: Why can't people trust the upstream to decide, when the software is stable, and insist on using (mega)frozen development snapshots? I do understand that Ion3 is not finished yet and you as the author of this gem should know the best when the software is stable, but as I mentioned earlier, some features from Ion3 are huge usability improvement over Ion2 and current snapshot of Ion3 in Etch (and also in Sarge) does everything I need. Regards Frank 8:00? 8:25? 8:40? Find a flick in no time with the Yahoo! Search movie showtime shortcut. http://tools.search.yahoo.com/shortcuts/#news
Bug#413469: Please don't, there are people using it
On 2007-03-11 01:19 -0800, Frank Bauer wrote: I do understand that Ion3 is not finished yet and you as the author of this gem should know the best when the software is stable, but as I mentioned earlier, some features from Ion3 are huge usability improvement over Ion2 and current snapshot of Ion3 in Etch (and also in Sarge) does everything I need. Maybe it does what you need, and you are one of the few who know not to complain, when it doesn't. But how about the newbies that have just heard of Ion3, and 'apt-get install ion3' gets them an old unsupported version that doesn't work for them? It's them whom I'm concerned about -- and they do exist. And, as has been mentioned, the upgrade path from the version in sarge -- that also should never have been there -- to the newer releases is not straightforward. There are also going to be incompatibilities between even those releases and the stable ones. Do you want to spend time rewriting your configs once again, when the stable ion3 finally hits a stable Debian, years from now? Do you like not being able to use any new scripts in the ion3 scripts repository, because they will not work with your old release? The megafreeze just doesn't work. -- Tuomo -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#407361: libtowitoko2: postinst calls wrong paramter for pscd restart install fails
Hi Simon, Here is a shorter patch, that implements the pcscd restart in a policy-compliant fashion. This uses invoke-rc.d directly, without checking if pcscd is already running. This does carry the possibility that pcscd will be started when it's not already running, but only in circumstances that pcscd's own maintainer scripts would do the same: i.e., in a runlevel where the service is configured to start but the admin has manually stopped it and there is no policy-rc.d configured. So there's no reason to take extra steps to check for the running process beforehand, because 'restart' already does what's expected under policy. (Note that, if the package supported 'reload' that would be sufficient; but it doesn't, so 'force-reload' is equivalent to 'restart' *except* that invoke-rc.d doesn't honor runlevel policies for 'force-reload'.) As this patch fixes the bug and is a straightforward implementation of policy, I'm going to go ahead shortly with an NMU to incoming. Thanks, -- Steve Langasek Give me a lever long enough and a Free OS Debian Developer to set it on, and I can move the world. [EMAIL PROTECTED] http://www.debian.org/ diff -u towitoko-2.0.7/debian/libtowitoko2.postinst towitoko-2.0.7/debian/libtowitoko2.postinst --- towitoko-2.0.7/debian/libtowitoko2.postinst +++ towitoko-2.0.7/debian/libtowitoko2.postinst @@ -59,7 +59,7 @@ db_stop if [ -x /etc/init.d/pcscd ]; then -/etc/init.d/pcscd restart-if-running 3/dev/null +invoke-rc.d pcscd restart 3/dev/null fi fi diff -u towitoko-2.0.7/debian/libtowitoko2.postrm towitoko-2.0.7/debian/libtowitoko2.postrm --- towitoko-2.0.7/debian/libtowitoko2.postrm +++ towitoko-2.0.7/debian/libtowitoko2.postrm @@ -23,7 +23,7 @@ # restart pcscd (PCSC daemon) if the package is installed # and if pcscd is running if [ -x /etc/init.d/pcscd ]; then - /etc/init.d/pcscd restart-if-running 3/dev/null || true + invoke-rc.d pcscd restart 3/dev/null || true fi ;; diff -u towitoko-2.0.7/debian/changelog towitoko-2.0.7/debian/changelog --- towitoko-2.0.7/debian/changelog +++ towitoko-2.0.7/debian/changelog @@ -1,3 +1,13 @@ +towitoko (2.0.7-7.3) unstable; urgency=high + + * Non-maintainer upload. + * High-urgency upload for RC bugfix. + * Use invoke-rc.d and the standard 'restart' command for pcscd in +postinst/postrm, instead of calling the pcscd init script directly with +the no-longer-supported 'restart-if-running' command. Closes: #407361. + + -- Steve Langasek [EMAIL PROTECTED] Sun, 11 Mar 2007 03:12:04 -0700 + towitoko (2.0.7-7.2) unstable; urgency=low * Non-maintainer upload to fix pending l10n issues.
Bug#407746: libpam-ldap upgrade breaks pam_ldap.conf and can't login
Hi Giuseppe, On Sun, Mar 11, 2007 at 12:31:22PM +0100, Giuseppe Sacco wrote: Il giorno sab, 10/03/2007 alle 14.43 -0800, Steve Langasek ha scritto: Here's the final NMU diff for the NMU which I'm uploading. The NMU will be uploaded to incoming shortly. [...] I prepared a new upload for this package too. It has been ready for one week now since I was waiting for a few translation updates. Moreover I agreed with Stephen to hijack his packages libnss-ldap and libpam-ldap. Well, this certainly was not evident when your last mail to the bug said you couldn't reproduce the problem... I checked your diff and you made a better work than I did about the way /etc/pam_ldap.conf is updated. On my diff I probably better explained to use a host or uri for shared/ldapns/ldap-server. I even moved to a new upstream release, 183, that fixes 8 bugs. Going forward, I would recommend that you deprecate the 'host' option completely in the Debian config; in all cases it is possible to losslessly convert it to an ldap:// URI, so I believe it's advisable to support reading the 'host', but only support writing a 'uri'. That would simplify the postinst code, and should also simplify the user interaction. I would like to merge these two diffs, but I don't want to change again the debconf templates, so probably the best idea is to just use your diff plus the new Italian translation I added, maybe applied to 183 instead of 180. (I already checked your diff against the new upstream version: it fits perfectly.) So, if you want, I could send you the Italian translation and you may NMU the package. I would then start uploading 183 to unstable, once your NMU migrate into etch. Sorry, I'm not interested in doing other NMUs for further translations right now; my main purpose was to fix the RC bug, and the template changes and translation updates were a side effect of the changed handling of ldapns/server. I definitely have no interest in the new upstream version right now while we're trying to push out a release. -- Steve Langasek Give me a lever long enough and a Free OS Debian Developer to set it on, and I can move the world. [EMAIL PROTECTED] http://www.debian.org/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#413969: marked as done (asterisk: Fails to start after not being able to find format_mp3.so)
Your message dated Sun, 11 Mar 2007 10:07:03 + with message-id [EMAIL PROTECTED] and subject line Bug#413969: asterisk: Fails to start after not being able to find format_mp3.so 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.) Debian bug tracking system administrator (administrator, Debian Bugs database) ---BeginMessage--- Package: asterisk Version: 1:1.2.16~dfsg-1 Severity: grave Justification: renders package unusable wallace:~# asterisk -cvvv ... Asterisk Dynamic Loader Starting: == Parsing '/etc/asterisk/modules.conf': Found [format_wav.so] = (Microsoft WAV format (8000hz Signed Linear)) == Registered file format wav, extension(s) wav [format_pcm.so] = (Raw uLaw 8khz Audio support (PCM)) == Registered file format pcm, extension(s) pcm|ulaw|ul|mu [format_au.so] = (Sun Microsystems AU format (signed linear)) == Registered file format au, extension(s) au [format_mp3.so]wallace:~# -- System Information: Debian Release: 4.0 APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.18-4-k7 Locale: LANG=en_NZ.UTF-8, LC_CTYPE=en_NZ.UTF-8 (charmap=UTF-8) Versions of packages asterisk depends on: ii adduser 3.102 Add and remove users and groups ii asterisk-classic 1:1.2.16~dfsg-1 Open Source Private Branch Exchang asterisk recommends no packages. -- no debconf information ---End Message--- ---BeginMessage--- Srdjan, On Sunday 11 March 2007 03:50, Srdjan wrote: Hi, Tzafrir Cohen wrote: Please provide a few more details: dpkg -l asterisk-addons There's no package asterisk-addons. There is an upstream package of asterisk-addons, which hasn't yet been packaged and loaded to Debian. This package is the source of the format_mp3.so module. I suspect that at one time you may of loaded this module. dpkg -S /usr/lib/asterisk/modules/format_mp3.so wallace:~# dpkg -S /usr/lib/asterisk/modules/format_mp3.so dpkg: /usr/lib/asterisk/modules/format_mp3.so not found. That's what I suspect - it dropped out somehow in 1.2.16 format_mp3.so has not been shipped by Debian. We are working on providing the asterisk-addons package, but it hasn't been released for Debian yet. ls -l /usr/lib/asterisk/modules/format_mp3.so grep format_mp3 /etc/asterisk/modules.conf wallace:~# grep format_mp3 /etc/asterisk/modules.conf load = format_mp3.so The modules.conf file in Debian does not load format_mp3.so as we don't ship this module (yet). I suspect you have added the load = format_mp3.so directive which is causing the problem you are seeing. I would suggest you remove this load directive which should clear up your problem. Or you can just reinstall asterisk-config which will install the dpkg.orig version of the conf file. Once we get asterisk-addons packaged for Debian, then you might have better success with format_mp3. Or you can see our work in progress at http://pkg-voip.buildserver.net/debian/pool/main/a/asterisk-addons/ Mark pgpLiX4RWonsH.pgp Description: PGP signature ---End Message---
Bug#414381: sshfs from testing-proposed-updates is uninstallable due wrong dependences
Package: sshfs Version: 1.6-1+b1 Severity: grave It depends on non-existed package libfuse, but should depend on libfuse2, like version from testing or unstable. -- System Information: Debian Release: 4.0 APT prefers testing-proposed-updates APT policy: (720, 'testing-proposed-updates'), (720, 'testing'), (670, 'proposed-updates'), (670, 'stable'), (600, 'unstable'), (550, 'experimental') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.18-4-vserver-686 Locale: LANG=ru_RU.KOI8-R, LC_CTYPE=ru_RU.KOI8-R (charmap=KOI8-R) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#405610: marked as done (old version of client is not suitable for connecting to SixXS network)
Your message dated Sun, 11 Mar 2007 12:28:47 + with message-id [EMAIL PROTECTED] and subject line Bug#405610: fixed in aiccu 20070115-1 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.) Debian bug tracking system administrator (administrator, Debian Bugs database) ---BeginMessage--- Package: aiccu Version: 20050131-1 Severity: serious There are many problems with this upstream release of the SixXS client (it is nearly two years old!) The SixXS service has evolved, protocols have changed, and upstream no longer recommends the use of this extremely old version of the client. (C.f., the tor package, which is not being released with etch.) For instance, the AYIYA protocol implementation (necessary for clients to connect behind a NAT) is broken. -- Robert Edmonds [EMAIL PROTECTED] signature.asc Description: Digital signature ---End Message--- ---BeginMessage--- Source: aiccu Source-Version: 20070115-1 We believe that the bug you reported is fixed in the latest version of aiccu, which is due to be installed in the Debian FTP archive: aiccu_20070115-1.diff.gz to pool/main/a/aiccu/aiccu_20070115-1.diff.gz aiccu_20070115-1.dsc to pool/main/a/aiccu/aiccu_20070115-1.dsc aiccu_20070115-1_amd64.deb to pool/main/a/aiccu/aiccu_20070115-1_amd64.deb aiccu_20070115-1_i386.deb to pool/main/a/aiccu/aiccu_20070115-1_i386.deb aiccu_20070115.orig.tar.gz to pool/main/a/aiccu/aiccu_20070115.orig.tar.gz 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. Philipp Kern [EMAIL PROTECTED] (supplier of updated aiccu 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: Wed, 7 Feb 2007 02:51:36 +0100 Source: aiccu Binary: aiccu Architecture: amd64 i386 source Version: 20070115-1 Distribution: unstable Urgency: low Maintainer: Philipp Kern [EMAIL PROTECTED] Changed-By: Philipp Kern [EMAIL PROTECTED] Description: aiccu - SixXS Automatic IPv6 Connectivity Client Utility Closes: 366002 379766 388759 405606 405610 407026 Changes: aiccu (20070115-1) unstable; urgency=low . * Upload package with me as an interim maintainer. Anand orphaned this package in private mail to me. (Closes: #407026) * Upload to `main' because of licence change in 20070107. (Closes: #388759) * New upstream version with the packaging based upon the one provided by upstream in the source tarball. aiccu is now up-to-date which should fix issues when connecting to SixXS. (Closes: #405606, #405610, #379766) * Slight packaging changes: I made the packaging non-native and changed some permission bits, dependencies and files to conform to the Debian standards and to fix various Lintian warnings and errors. Please see the diff for details. * The amd64 binary package is included in the upload. (Closes: #366002) Files: 78d72415ccf22197d681fc62b4f92f09 43536 net optional aiccu_20070115-1_amd64.deb 9da28cdede41753991b49020f3752a12 586 net optional aiccu_20070115-1.dsc d0a56d7f80a5e8747519a2dd7c0eae44 70007 net optional aiccu_20070115.orig.tar.gz d86fa4d39eaca3cdd8110311c7cd4150 3804 net optional aiccu_20070115-1.diff.gz e907adf0f2e373e1deba27236ca119ce 42790 net optional aiccu_20070115-1_i386.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.6 (GNU/Linux) iD8DBQFFyTH97Ro5M7LPzdgRAiZJAKC0VLs6atJU8ni461IPPBn/s8VBtwCfX9/f wX77YfM9n6U4y9WDoPF37S0= =LaB0 -END PGP SIGNATURE- ---End Message---
Bug#405610: marked as done (old version of client is not suitable for connecting to SixXS network)
Your message dated Sun, 11 Mar 2007 12:28:47 + with message-id [EMAIL PROTECTED] and subject line Bug#405606: fixed in aiccu 20070115-1 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.) Debian bug tracking system administrator (administrator, Debian Bugs database) ---BeginMessage--- Package: aiccu Version: 20050131-1 Severity: serious There are many problems with this upstream release of the SixXS client (it is nearly two years old!) The SixXS service has evolved, protocols have changed, and upstream no longer recommends the use of this extremely old version of the client. (C.f., the tor package, which is not being released with etch.) For instance, the AYIYA protocol implementation (necessary for clients to connect behind a NAT) is broken. -- Robert Edmonds [EMAIL PROTECTED] signature.asc Description: Digital signature ---End Message--- ---BeginMessage--- Source: aiccu Source-Version: 20070115-1 We believe that the bug you reported is fixed in the latest version of aiccu, which is due to be installed in the Debian FTP archive: aiccu_20070115-1.diff.gz to pool/main/a/aiccu/aiccu_20070115-1.diff.gz aiccu_20070115-1.dsc to pool/main/a/aiccu/aiccu_20070115-1.dsc aiccu_20070115-1_amd64.deb to pool/main/a/aiccu/aiccu_20070115-1_amd64.deb aiccu_20070115-1_i386.deb to pool/main/a/aiccu/aiccu_20070115-1_i386.deb aiccu_20070115.orig.tar.gz to pool/main/a/aiccu/aiccu_20070115.orig.tar.gz 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. Philipp Kern [EMAIL PROTECTED] (supplier of updated aiccu 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: Wed, 7 Feb 2007 02:51:36 +0100 Source: aiccu Binary: aiccu Architecture: amd64 i386 source Version: 20070115-1 Distribution: unstable Urgency: low Maintainer: Philipp Kern [EMAIL PROTECTED] Changed-By: Philipp Kern [EMAIL PROTECTED] Description: aiccu - SixXS Automatic IPv6 Connectivity Client Utility Closes: 366002 379766 388759 405606 405610 407026 Changes: aiccu (20070115-1) unstable; urgency=low . * Upload package with me as an interim maintainer. Anand orphaned this package in private mail to me. (Closes: #407026) * Upload to `main' because of licence change in 20070107. (Closes: #388759) * New upstream version with the packaging based upon the one provided by upstream in the source tarball. aiccu is now up-to-date which should fix issues when connecting to SixXS. (Closes: #405606, #405610, #379766) * Slight packaging changes: I made the packaging non-native and changed some permission bits, dependencies and files to conform to the Debian standards and to fix various Lintian warnings and errors. Please see the diff for details. * The amd64 binary package is included in the upload. (Closes: #366002) Files: 78d72415ccf22197d681fc62b4f92f09 43536 net optional aiccu_20070115-1_amd64.deb 9da28cdede41753991b49020f3752a12 586 net optional aiccu_20070115-1.dsc d0a56d7f80a5e8747519a2dd7c0eae44 70007 net optional aiccu_20070115.orig.tar.gz d86fa4d39eaca3cdd8110311c7cd4150 3804 net optional aiccu_20070115-1.diff.gz e907adf0f2e373e1deba27236ca119ce 42790 net optional aiccu_20070115-1_i386.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.6 (GNU/Linux) iD8DBQFFyTH97Ro5M7LPzdgRAiZJAKC0VLs6atJU8ni461IPPBn/s8VBtwCfX9/f wX77YfM9n6U4y9WDoPF37S0= =LaB0 -END PGP SIGNATURE- ---End Message---
Bug#409644: libfuse2: please include a versioned shlibs file
On Sun, Mar 11, 2007 at 12:54:24PM +0100, Frank Küster wrote: Steve Langasek [EMAIL PROTECTED] wrote: Could you please re-NMU with the correct shlibs info? Please take my apologies, uploaded with the following updated patch: diff -Nur fuse-2.5.3.old/debian/changelog fuse-2.5.3/debian/changelog --- fuse-2.5.3.old/debian/changelog 2007-03-05 18:07:57.0 +0100 +++ fuse-2.5.3/debian/changelog 2007-03-11 12:44:34.0 +0100 @@ -1,3 +1,34 @@ +fuse (2.5.3-4.4) unstable; urgency=low Uploaded to the wrong suite, so rejected of course. Will wait to hear from you that you've reuploaded to testing. -- Steve Langasek Give me a lever long enough and a Free OS Debian Developer to set it on, and I can move the world. [EMAIL PROTECTED] http://www.debian.org/
Bug#405606: marked as done (old version of client is not suitable for connecting to SixXS network)
Your message dated Sun, 11 Mar 2007 12:28:47 + with message-id [EMAIL PROTECTED] and subject line Bug#405606: fixed in aiccu 20070115-1 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.) Debian bug tracking system administrator (administrator, Debian Bugs database) ---BeginMessage--- Package: aiccu Version: 20050131-1 Severity: serious There are many problems with this upstream release of the SixXS client (it is nearly two years old!) The SixXS service has evolved, protocols have changed, and upstream no longer recommends the use of this extremely old version of the client. (C.f., the tor package, which is not being released with etch.) For instance, the AYIYA protocol implementation (necessary for clients to connect behind a NAT) is broken. -- Robert Edmonds [EMAIL PROTECTED] signature.asc Description: Digital signature ---End Message--- ---BeginMessage--- Source: aiccu Source-Version: 20070115-1 We believe that the bug you reported is fixed in the latest version of aiccu, which is due to be installed in the Debian FTP archive: aiccu_20070115-1.diff.gz to pool/main/a/aiccu/aiccu_20070115-1.diff.gz aiccu_20070115-1.dsc to pool/main/a/aiccu/aiccu_20070115-1.dsc aiccu_20070115-1_amd64.deb to pool/main/a/aiccu/aiccu_20070115-1_amd64.deb aiccu_20070115-1_i386.deb to pool/main/a/aiccu/aiccu_20070115-1_i386.deb aiccu_20070115.orig.tar.gz to pool/main/a/aiccu/aiccu_20070115.orig.tar.gz 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. Philipp Kern [EMAIL PROTECTED] (supplier of updated aiccu 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: Wed, 7 Feb 2007 02:51:36 +0100 Source: aiccu Binary: aiccu Architecture: amd64 i386 source Version: 20070115-1 Distribution: unstable Urgency: low Maintainer: Philipp Kern [EMAIL PROTECTED] Changed-By: Philipp Kern [EMAIL PROTECTED] Description: aiccu - SixXS Automatic IPv6 Connectivity Client Utility Closes: 366002 379766 388759 405606 405610 407026 Changes: aiccu (20070115-1) unstable; urgency=low . * Upload package with me as an interim maintainer. Anand orphaned this package in private mail to me. (Closes: #407026) * Upload to `main' because of licence change in 20070107. (Closes: #388759) * New upstream version with the packaging based upon the one provided by upstream in the source tarball. aiccu is now up-to-date which should fix issues when connecting to SixXS. (Closes: #405606, #405610, #379766) * Slight packaging changes: I made the packaging non-native and changed some permission bits, dependencies and files to conform to the Debian standards and to fix various Lintian warnings and errors. Please see the diff for details. * The amd64 binary package is included in the upload. (Closes: #366002) Files: 78d72415ccf22197d681fc62b4f92f09 43536 net optional aiccu_20070115-1_amd64.deb 9da28cdede41753991b49020f3752a12 586 net optional aiccu_20070115-1.dsc d0a56d7f80a5e8747519a2dd7c0eae44 70007 net optional aiccu_20070115.orig.tar.gz d86fa4d39eaca3cdd8110311c7cd4150 3804 net optional aiccu_20070115-1.diff.gz e907adf0f2e373e1deba27236ca119ce 42790 net optional aiccu_20070115-1_i386.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.6 (GNU/Linux) iD8DBQFFyTH97Ro5M7LPzdgRAiZJAKC0VLs6atJU8ni461IPPBn/s8VBtwCfX9/f wX77YfM9n6U4y9WDoPF37S0= =LaB0 -END PGP SIGNATURE- ---End Message---
Bug#409644: marked as done (libfuse2: please include a versioned shlibs file)
Your message dated Sun, 11 Mar 2007 13:32:03 + with message-id [EMAIL PROTECTED] and subject line Bug#409644: fixed in fuse 2.5.3-4.4 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.) Debian bug tracking system administrator (administrator, Debian Bugs database) ---BeginMessage--- Package: libfuse2 Severity: serious Justification: renders related (by dependency) packages unusable When running a program linked against libfuse2 2.6 using version 2.5 of the library it aborts with the following error message: /usr/lib/libfuse.so.2: version `FUSE_2.6' not found This can be avoided by including a versioned shlibs file which in turn would create correct package dependencies. Cheers, Sebastian -- Sebastian tokkee Harl GnuPG-ID: 0x8501C7FC http://tokkee.org/ signature.asc Description: Digital signature ---End Message--- ---BeginMessage--- Source: fuse Source-Version: 2.5.3-4.4 We believe that the bug you reported is fixed in the latest version of fuse, which is due to be installed in the Debian FTP archive: fuse-utils_2.5.3-4.4_i386.deb to pool/main/f/fuse/fuse-utils_2.5.3-4.4_i386.deb fuse_2.5.3-4.4.diff.gz to pool/main/f/fuse/fuse_2.5.3-4.4.diff.gz fuse_2.5.3-4.4.dsc to pool/main/f/fuse/fuse_2.5.3-4.4.dsc libfuse-dev_2.5.3-4.4_i386.deb to pool/main/f/fuse/libfuse-dev_2.5.3-4.4_i386.deb libfuse2_2.5.3-4.4_i386.deb to pool/main/f/fuse/libfuse2_2.5.3-4.4_i386.deb 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. Frank Küster [EMAIL PROTECTED] (supplier of updated fuse 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: Sun, 11 Mar 2007 12:44:34 +0100 Source: fuse Binary: libfuse2 libfuse-dev fuse-utils Architecture: source i386 Version: 2.5.3-4.4 Distribution: testing-proposed-updates Urgency: low Maintainer: Bartosz Fenski [EMAIL PROTECTED] Changed-By: Frank Küster [EMAIL PROTECTED] Description: fuse-utils - Filesystem in USErspace (utilities) libfuse-dev - Filesystem in USErspace (development files) libfuse2 - Filesystem in USErspace library Closes: 404904 409644 Changes: fuse (2.5.3-4.4) testing-proposed-updates; urgency=low . * Followup to my last NMU * Use a correct package name for the shlibs information (libfuse2, not libfuse), thanks to Steve Langasek. . fuse (2.5.3-4.3) testing-proposed-updates; urgency=low . * Non-maintainer upload to fix RC bug * Upload to t-p-u, since unstable has already a new upstream version * Call dh_makeshlibs with '-V libfuse (= 2.5)' to make sure dependencies are correct (closes: #409644) * Incorporate the patch for the 2.5.3-4.2 NMU, including changelog entry, which never made it to testing . fuse (2.5.3-4.2) unstable; urgency=low . * Non-maintainer upload (with maintainer's approval). * Ensure the correct alignment of the ccmsg array in receive_fd() from lib/mount.c by declaring it as size_t instead of char and adjusting the size accordingly. This resolves the issue of sshfs crashing with SIGBUS on sparc. Thanks to Sebastian Fontius for debugging and testing, and to Miklos Szeredi for the patch. (closes: #404904) Files: d43e3cc7951727c433d6d5dcfcbeb7da 605 libs optional fuse_2.5.3-4.4.dsc d2f182d50508a2e1993cda9fd58a3a90 8246 libs optional fuse_2.5.3-4.4.diff.gz 29eea52c5cb59032066cbae34cc613ca 56854 utils optional fuse-utils_2.5.3-4.4_i386.deb efbbca16bb187f92decf730e1e67d73e 93196 libdevel optional libfuse-dev_2.5.3-4.4_i386.deb d131e3a6c45d23590087dfae3596ef0a 50722 libs optional libfuse2_2.5.3-4.4_i386.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.6 (GNU/Linux) iD8DBQFF9ARV+xs9YyJS+hoRAhRXAJ9cyK5XZIkpLKA9TedOc4FQFyieUgCfbx9E jaAubuek0WxvQm/rFwVFLVw= =ZdV+ -END PGP SIGNATURE- ---End Message---
Bug#409644: libfuse2: please include a versioned shlibs file
Steve Langasek [EMAIL PROTECTED] wrote: On Sun, Mar 11, 2007 at 12:54:24PM +0100, Frank Küster wrote: Steve Langasek [EMAIL PROTECTED] wrote: Could you please re-NMU with the correct shlibs info? Please take my apologies, uploaded with the following updated patch: diff -Nur fuse-2.5.3.old/debian/changelog fuse-2.5.3/debian/changelog --- fuse-2.5.3.old/debian/changelog 2007-03-05 18:07:57.0 +0100 +++ fuse-2.5.3/debian/changelog 2007-03-11 12:44:34.0 +0100 @@ -1,3 +1,34 @@ +fuse (2.5.3-4.4) unstable; urgency=low Uploaded to the wrong suite, so rejected of course. Will wait to hear from you that you've reuploaded to testing. That's when I do Debian work between church and lunch, and make the changes while I'm asked to put the plates on the table... I've just uploaded an other -4.4 to t-p-u, but probably that won't work, and it should've been -4.5. Nevertheless, I have to leave now. The source package is on http://people.debian.org/~frank Regards, Frank -- Dr. Frank Küster Single Molecule Spectroscopy, Protein Folding @ Inst. f. Biochemie, Univ. Zürich Debian Developer (teTeX/TeXLive)
Bug#414385: libimdb-film-perl should not enter testing
Package: libimdb-film-perl Version: 0.24-1 Severity: serious As the imdb.com website is likely to change during the lifetime of a stabel release, and because this will break libimdb-film-perl's functionality, the package should not be released in stable/main. I am considering uploading it to volatile instead. -- System Information: Debian Release: 4.0 APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing'), (1, 'experimental') Architecture: i386 (x86_64) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.18.2 Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8) Versions of packages libimdb-film-perl depends on: ii libcache-cache-perl 1.05-2 Managed caches of persistent infor ii libdigest-sha1-perl 2.11-2 NIST SHA-1 message digest algorith ii libhtml-parser-perl 3.56-1 A collection of modules that parse ii libwww-perl 5.805-1WWW client/server library for Perl ii perl 5.8.8-7Larry Wall's Practical Extraction libimdb-film-perl recommends no packages. -- no debconf information -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#386469: openbsd-inetd, action start failed when upgrading
So far, none of the people reporting this bug have provided information that can be used to track it down. Most users are quoting the failure to set up openbsd-inetd -- that's not news, what we need is output from the *unpack* stage of the upgrade showing why the attempt to *stop* the previous inetd failed. Others are quoting dpkg logs showing that they've only upgraded to version -4, when this bug is being reported against version -5. That doesn't clarify anything; we need to see that the bug is happening with the current version of the package, not obsolete versions that have been removed from the archive. Others are providing aptitude logs, which tell nothing about what went wrong in dpkg. A good report to work with on this bug is going to be: - what version of openbsd-inetd you were upgrading from (this information is avaliable from dpkg.log) - logs showing what happened when unpacking the new version of openbsd-inetd - confirmation that you are installing the *current* version of openbsd-inetd -- that's version -5, not version -4 - ps output showing the inetd processes running after the point at which the new version of the package has failed to configure There are lots of theories about what's happening here, but without the above information as a starting point, they're effectively impossible to investigate. -- Steve Langasek Give me a lever long enough and a Free OS Debian Developer to set it on, and I can move the world. [EMAIL PROTECTED] http://www.debian.org/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#414380: amaya does not start. X Window System error serial 10426 error_code 8 request_code 144 minor_code 5
Yes, yes I know. This bug is actually a mixed thing somewhere between wxWidgets, Mesa and Xorg. And you're running GLX without DRI, which is (almost) the only situation triggering the bug I have seen. For more informations, see bug #357439 : http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=357439 Regis On Sun, 2007-03-11 at 11:43 +0100, Adrien Grellier wrote: Package: amaya Version: 9.53~dfsg.0-1 Severity: grave Justification: renders package unusable I can't start amaya, and I have this message : (amaya:2766): Gtk-CRITICAL **: gtk_widget_set_colormap: assertion `!GTK_WIDGET_REALIZED (widget)' failed The program 'amaya' received an X Window System error. This probably reflects a bug in the program. The error was 'BadMatch (invalid parameter attributes)'. (Details: serial 10426 error_code 8 request_code 144 minor_code 5) (Note to programmers: normally, X errors are reported asynchronously; that is, you will receive the error a while after causing it. To debug your program, run it with the --sync command line option to change this behavior. You can then get a meaningful backtrace from your debugger if you break on the gdk_x_error() function.) I use the unstable package. -- System Information: Debian Release: 4.0 APT prefers testing APT policy: (500, 'testing') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.18-4-686 Locale: [EMAIL PROTECTED], [EMAIL PROTECTED] (charmap=ISO-8859-15) Versions of packages amaya depends on: ii libc6 2.3.6.ds1-13 GNU C Library: Shared libraries ii libexpat1 1.95.8-3.4 XML parsing C library - runtime li ii libfreetype6 2.2.1-5FreeType 2 font engine, shared lib ii libgcc1 1:4.1.1-21 GCC support library ii libgl1-mesa-glx [libgl1] 6.5.1-0.6 A free implementation of the OpenG ii libglu1-mesa [libglu1]6.5.1-0.6 The OpenGL utility library (GLU) ii libjpeg62 6b-13 The Independent JPEG Group's JPEG ii libpng12-01.2.15~beta5-1 PNG library - runtime ii libraptor11.4.13-1 Raptor RDF parser and serializer l ii libstdc++64.1.1-21 The GNU Standard C++ Library v3 ii libwww-ssl0 5.4.0-11 The W3C-WWW library (SSL support) ii libwxbase2.6-02.6.3.2.1.5wxBase library (runtime) - non-GUI ii libwxgtk2.6-0 2.6.3.2.1.5wxWidgets Cross-platform C++ GUI t ii ttf-freefont 20060501cvs-10 Freefont Serif, Sans and Mono True ii zlib1g1:1.2.3-13 compression library - runtime amaya recommends no packages. -- no debconf information -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#411975: marked as done (file conflicts between libdballe-dev and other liballe-* packages)
Your message dated Sun, 11 Mar 2007 14:00:47 + with message-id [EMAIL PROTECTED] and subject line Bug#411975: fixed in dballe 3.1-1 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.) Debian bug tracking system administrator (administrator, Debian Bugs database) ---BeginMessage--- Package: libdballe-dev, libdballef-dev, libdballe-db-dev, libdballe-msg-dev Severity: serious Justification: file conflicts, policy violation hi, both libdballe-dev and libdballef-dev do ship `/usr/lib/libdballef.a' amongst other files but do not conflict or add a diversion, thus fail on installation in the same environment: [..] dpkg: error processing /var/cache/apt/archives/libdballef-dev_3.0.1-1_amd64.deb (--unpack): trying to overwrite `/usr/lib/libdballef.a', which is also in package libdballe-dev [..] also, libdballe-db-dev conflicts with libdballe-msg-dev: [..] Unpacking libdballe-dev (from .../libdballe-dev_2.6-1_amd64.deb) ... dpkg: error processing /var/cache/apt/archives/libdballe-dev_2.6-1_amd64.deb (--unpack): trying to overwrite `/usr/include/dballe/msg/level.h', which is also in package libdballe-msg-dev [..] detailed list of file conflicts: http://qa.debian.org/~filippo/file_conflicts/unstable-conflicts bye, - michael ---End Message--- ---BeginMessage--- Source: dballe Source-Version: 3.1-1 We believe that the bug you reported is fixed in the latest version of dballe, which is due to be installed in the Debian FTP archive: dballe-common_3.1-1_amd64.deb to pool/main/d/dballe/dballe-common_3.1-1_amd64.deb dballe_3.1-1.diff.gz to pool/main/d/dballe/dballe_3.1-1.diff.gz dballe_3.1-1.dsc to pool/main/d/dballe/dballe_3.1-1.dsc dballe_3.1-1_amd64.deb to pool/main/d/dballe/dballe_3.1-1_amd64.deb dballe_3.1.orig.tar.gz to pool/main/d/dballe/dballe_3.1.orig.tar.gz libdballe-bufrex-dev_3.1-1_amd64.deb to pool/main/d/dballe/libdballe-bufrex-dev_3.1-1_amd64.deb libdballe-bufrex-doc_3.1-1_amd64.deb to pool/main/d/dballe/libdballe-bufrex-doc_3.1-1_amd64.deb libdballe-bufrex3_3.1-1_amd64.deb to pool/main/d/dballe/libdballe-bufrex3_3.1-1_amd64.deb libdballe-core-dev_3.1-1_amd64.deb to pool/main/d/dballe/libdballe-core-dev_3.1-1_amd64.deb libdballe-core-doc_3.1-1_amd64.deb to pool/main/d/dballe/libdballe-core-doc_3.1-1_amd64.deb libdballe-core3_3.1-1_amd64.deb to pool/main/d/dballe/libdballe-core3_3.1-1_amd64.deb libdballe-db-dev_3.1-1_amd64.deb to pool/main/d/dballe/libdballe-db-dev_3.1-1_amd64.deb libdballe-db-doc_3.1-1_amd64.deb to pool/main/d/dballe/libdballe-db-doc_3.1-1_amd64.deb libdballe-db3_3.1-1_amd64.deb to pool/main/d/dballe/libdballe-db3_3.1-1_amd64.deb libdballe-msg-dev_3.1-1_amd64.deb to pool/main/d/dballe/libdballe-msg-dev_3.1-1_amd64.deb libdballe-msg-doc_3.1-1_amd64.deb to pool/main/d/dballe/libdballe-msg-doc_3.1-1_amd64.deb libdballe-msg3_3.1-1_amd64.deb to pool/main/d/dballe/libdballe-msg3_3.1-1_amd64.deb libdballef-dev_3.1-1_amd64.deb to pool/main/d/dballe/libdballef-dev_3.1-1_amd64.deb libdballef3_3.1-1_amd64.deb to pool/main/d/dballe/libdballef3_3.1-1_amd64.deb libdballepp-dev_3.1-1_amd64.deb to pool/main/d/dballe/libdballepp-dev_3.1-1_amd64.deb libdballepp3_3.1-1_amd64.deb to pool/main/d/dballe/libdballepp3_3.1-1_amd64.deb provami_3.1-1_amd64.deb to pool/main/d/dballe/provami_3.1-1_amd64.deb python-dballe_3.1-1_amd64.deb to pool/main/d/dballe/python-dballe_3.1-1_amd64.deb 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. Enrico Zini [EMAIL PROTECTED] (supplier of updated dballe 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: Wed, 28 Feb 2007 13:47:20 +0100 Source: dballe Binary: provami libdballef-dev dballe python-dballe libdballe-msg3 libdballe-core3 libdballe-bufrex-dev libdballepp-dev libdballe-msg-dev libdballe-db3 dballe-common libdballe-msg-doc libdballef3 libdballe-db-doc libdballe-core-doc libdballe-bufrex-doc libdballe-db-dev libdballepp3 libdballe-bufrex3 libdballe-core-dev Architecture: source amd64 Version: 3.1-1 Distribution: unstable Urgency: low Maintainer: [EMAIL PROTECTED] Changed-By: Enrico Zini [EMAIL PROTECTED] Description: dballe - Database for punctual
Bug#333835: marked as done (ctrlproxy: Eats up memory making the system unusable)
Your message dated Sun, 11 Mar 2007 14:02:00 + with message-id [EMAIL PROTECTED] and subject line Bug#333835: fixed in ctrlproxy 3.0.1-1 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.) Debian bug tracking system administrator (administrator, Debian Bugs database) ---BeginMessage--- Package: ctrlproxy Version: 2.6.2-1 Severity: critical Justification: breaks unrelated software After running ctrlproxy for a fairly long time as daemon: Mem: 30180 29248932 0 1336 5596 -/+ buffers/cache: 22316 7864 Swap:60440 60440 0 After killing ctrlproxy and starting it again: total used free sharedbuffers cached Mem: 30180 17168 13012 0 1508 7412 -/+ buffers/cache: 8248 21932 Swap:60440 3576 56864 -- System Information: Debian Release: 3.1 Architecture: i386 (i586) Kernel: Linux 2.4.27-2-586tsc Locale: LANG=en_US, LC_CTYPE=en_US (charmap=ISO-8859-1) Versions of packages ctrlproxy depends on: ii libc6 2.3.2.ds1-22 GNU C Library: Shared libraries an ii libglib2.0-0 2.6.4-1 The GLib library of C routines ii libpopt0 1.7-5 lib for parsing cmdline parameters ii libssl0.9.70.9.7e-3 SSL shared libraries ii libxml22.6.16-7 GNOME XML library ii zlib1g 1:1.2.2-4.sarge.2 compression library - runtime -- no debconf information pgp0lnVr4FYOL.pgp Description: PGP signature ---End Message--- ---BeginMessage--- Source: ctrlproxy Source-Version: 3.0.1-1 We believe that the bug you reported is fixed in the latest version of ctrlproxy, which is due to be installed in the Debian FTP archive: ctrlproxy-dev_3.0.1-1_i386.deb to pool/main/c/ctrlproxy/ctrlproxy-dev_3.0.1-1_i386.deb ctrlproxy_3.0.1-1.diff.gz to pool/main/c/ctrlproxy/ctrlproxy_3.0.1-1.diff.gz ctrlproxy_3.0.1-1.dsc to pool/main/c/ctrlproxy/ctrlproxy_3.0.1-1.dsc ctrlproxy_3.0.1-1_i386.deb to pool/main/c/ctrlproxy/ctrlproxy_3.0.1-1_i386.deb ctrlproxy_3.0.1.orig.tar.gz to pool/main/c/ctrlproxy/ctrlproxy_3.0.1.orig.tar.gz 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. Jelmer Vernooij [EMAIL PROTECTED] (supplier of updated ctrlproxy 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: Wed, 28 Feb 2007 13:06:11 +0100 Source: ctrlproxy Binary: ctrlproxy ctrlproxy-dev Architecture: source i386 Version: 3.0.1-1 Distribution: unstable Urgency: high Maintainer: Jelmer Vernooij [EMAIL PROTECTED] Changed-By: Jelmer Vernooij [EMAIL PROTECTED] Description: ctrlproxy - IRC proxy with conversation replay support ctrlproxy-dev - IRC proxy with conversation replay support - development files Closes: 222994 276072 298679 307192 308665 314532 324601 324936 333126 333127 333835 412273 Changes: ctrlproxy (3.0.1-1) unstable; urgency=low . * New upstream release. (Closes: #412273) * Add XS-VCS-Bzr field. * Fix copyright file. * Add development package with headers and pkg-config file. * Run testsuite when building package. . ctrlproxy (3.0.0-1) unstable; urgency=high . * New upstream release. * Install manpages. (Closes: #307192, #324601) * New configuration format and examples. (Closes: #333126, #308665, #298679) * Fixes directory permissions for log_irssi. (Closes: #333127) * Fixes several segmentation faults. (Closes: #314532) * Lower memory profile, history no longer stored in memory. (Closes: #333835) * Removed obsolete ctrlproxy-setup script. (Closes: #324936) * Removed obsolete stats module. (Closes: #276072) * Fixes dates in logs (Closes: #222994) * New maintainer. Files: e3be6e7bada72fd3c0d732dff297aa8b 737 net optional ctrlproxy_3.0.1-1.dsc c80e75945b8bed233b29f146b5af098e 197403 net optional ctrlproxy_3.0.1.orig.tar.gz 6f49a951a74584f26af0c362c7168c96 11759 net optional ctrlproxy_3.0.1-1.diff.gz a38e1a0920b2b76959591f80d6e064de 98092 net optional ctrlproxy_3.0.1-1_i386.deb c8861c2eeda3ccbfcfe7b1a270b99c67 12782 net optional ctrlproxy-dev_3.0.1-1_i386.deb
Processed: Re: bins: needs libglade-gnome0 but libgladexml-perl depends on libglade0 not libglade-gnome0
Processing commands for [EMAIL PROTECTED]: reassign 413910 bins Bug#413910: bins: needs libglade-gnome0 but libgladexml-perl depends on libglade0 not libglade-gnome0 Bug reassigned from package `libgladexml-perl' to `bins'. severity 413910 serious Bug#413910: bins: needs libglade-gnome0 but libgladexml-perl depends on libglade0 not libglade-gnome0 Severity set to `serious' from `normal' retitle 413910 bins: missing dependencies for bins-edit-gui Bug#413910: bins: needs libglade-gnome0 but libgladexml-perl depends on libglade0 not libglade-gnome0 Changed Bug title. stop Stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#413910: bins: needs libglade-gnome0 but libgladexml-perl depends on libglade0 not libglade-gnome0
severity 413910 normal thanks * Bart Martens [EMAIL PROTECTED] [2007-03-11 15:32]: If bins-edit-gui depends on libgladexml-perl, then the Debian package shipping bins-edit-gui must have Depends: libgladexml-perl. Same for the other missing dependencies. Maybe you want to put bins-edit-gui in a separate binary package and add the missing dependencies only there. Actually, you're wrong about this. See http://www.debian.org/devel/tech-ctte 2002-07-19 Bug #119517: Packages may sometimes contain binaries whose libraries are only referred to in Suggests. Full text. In favour: Ian, Wichert; against: Bdale, Manoj; no-one else voted and Ian used his casting vote. -- Martin Michlmayr http://www.cyrius.com/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Processed: Re: Bug#413910: bins: needs libglade-gnome0 but libgladexml-perl depends on libglade0 not libglade-gnome0
Processing commands for [EMAIL PROTECTED]: severity 413910 normal Bug#413910: bins: missing dependencies for bins-edit-gui Severity set to `normal' from `serious' thanks Stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#414401: arch2darcs: FTBFS in Etch: build-depends on libghc6-hslogger-dev
Package: arch2darcs Version: 1.0.9 Severity: serious Tags: etch This package fails to build in Etch (but not in Sid) due to libghc6-hslogger-dev not being available in Etch. On Mon, Mar 05, 2007 at 02:05:37PM +0100, [EMAIL PROTECTED] wrote: Automatic build of arch2darcs_1.0.9 on qa by sbuild/amd64 85 Build started at 20070305-1405 ** Checking available source versions... Fetching source files... Reading package lists... Building dependency tree... Need to get 15.2kB of source archives. Get:1 http://debian.aurel32.net etch/main arch2darcs 1.0.9 (dsc) [614B] Get:2 http://debian.aurel32.net etch/main arch2darcs 1.0.9 (tar) [14.6kB] Fetched 15.2kB in 0s (289kB/s) Download complete and in download only mode ** Using build dependencies supplied by package: Build-Depends: debhelper (= 4.0.0), ghc6 (= 6.4.2), libghc6-missingh-dev (= 0.18.0), libghc6-network-dev, libghc6-unix-dev, libghc6-hslogger-dev Checking for already installed source dependencies... debhelper: missing Using default version 5.0.42 ghc6: missing Using default version 6.6-3 libghc6-missingh-dev: missing Default version of libghc6-missingh-dev not sufficient, no suitable version found. Skipping for now, maybe there are alternatives. libghc6-network-dev: missing libghc6-unix-dev: missing libghc6-hslogger-dev: missing Checking for source dependency conflicts... /usr/bin/sudo /usr/bin/apt-get --purge $CHROOT_OPTIONS -q -y install debhelper ghc6 libghc6-missingh-dev libghc6-network-dev libghc6-unix-dev libghc6-hslogger-dev Reading package lists... Building dependency tree... E: Couldn't find package libghc6-hslogger-dev Note, selecting ghc6 instead of libghc6-unix-dev apt-get failed. Package installation failed Trying to reinstall removed packages: Trying to uninstall newly installed packages: Source-dependencies not satisfied; skipping arch2darcs ** Finished at 20070305-1405 Build needed 00:00:00, 0k disk space -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#414402: srcinst: FTBFS in Etch: build-depends on libghc6-hslogger-dev
Package: srcinst Version: 0.8.7 Severity: serious Tags: etch This package fails to build in Etch (but not in Sid) due to libghc6-hslogger-dev not being available in Etch. On Mon, Mar 05, 2007 at 03:00:06PM +0100, [EMAIL PROTECTED] wrote: Automatic build of srcinst_0.8.7 on qa by sbuild/amd64 85 Build started at 20070305-1459 ** Checking available source versions... Fetching source files... Reading package lists... Building dependency tree... Need to get 14.5kB of source archives. Get:1 http://debian.aurel32.net etch/main srcinst 0.8.7 (dsc) [605B] Get:2 http://debian.aurel32.net etch/main srcinst 0.8.7 (tar) [13.9kB] Fetched 14.5kB in 0s (97.7kB/s) Download complete and in download only mode ** Using build dependencies supplied by package: Build-Depends: debhelper (= 4.0.0), ghc6 (= 6.4.2), libghc6-missingh-dev (= 0.18.0), libghc6-network-dev, libghc6-unix-dev, libghc6-hslogger-dev Checking for already installed source dependencies... debhelper: missing Using default version 5.0.42 ghc6: missing Using default version 6.6-3 libghc6-missingh-dev: missing Default version of libghc6-missingh-dev not sufficient, no suitable version found. Skipping for now, maybe there are alternatives. libghc6-network-dev: missing libghc6-unix-dev: missing libghc6-hslogger-dev: missing Checking for source dependency conflicts... /usr/bin/sudo /usr/bin/apt-get --purge $CHROOT_OPTIONS -q -y install debhelper ghc6 libghc6-missingh-dev libghc6-network-dev libghc6-unix-dev libghc6-hslogger-dev Reading package lists... Building dependency tree... E: Couldn't find package libghc6-hslogger-dev Note, selecting ghc6 instead of libghc6-unix-dev apt-get failed. Package installation failed Trying to reinstall removed packages: Trying to uninstall newly installed packages: Source-dependencies not satisfied; skipping srcinst ** Finished at 20070305-1500 Build needed 00:05:17, 0k disk space -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#413968: [php-maint] xmlrpc-epi turns out to be libxmlrpc in php
On Sun, Mar 11, 2007 at 01:56:42PM +0100, sean finney wrote: On Sun, 2007-03-11 at 17:44 +1100, Paul TBBle Hampson wrote: I'm suggesting either. I'm happy to maintain the package seperately, but I intend to go through the differences between the versions and confirm that they are compatible, and steal anything good from the php-bundled version, so in effect I'd be doing both. I'd also have to track upstream PHP in case they add anything else to the library in the future. So maybe a PHP package team member might want to be a co-maintainer... okay, perhaps we can revisit this after you're done. if you decide to use the upstream version we can see how hard it is to build php against that instead of the bundled code. if you decide you want to use the php-bundled version, then we should probably just generate it from the php5 source package directly. i don't use this extension myself, so in any event it would be wise to find someone who does so we can test that it still works :) Well, my plan was to effectively use the php5 version (since it's the main place the code's being actively used) but treat it as the upstream version with patches. If the package was generated straight out of the PHP source, it'd miss the samples and tests included in the upstream tarball. (Not that I've run the tests myself yet, the first roll of the package was pretty quick 'n' dirty.) A quick poke around the Internet suggested that the only patches being made by other distros to xmlrpc-epi are for gcc4, 64-bit and expat, but I haven't looked at the PHP-bundled version's changes yet, apart from verifying that the .h files match semanticly. did you check that visually, or did you use a utility like icheck? Visually: [EMAIL PROTECTED]:~/code/php/php5-5.2.0/ext/xmlrpc/libxmlrpc$ for d in *.h; do diff ~/code/xmlrpcepi/build/xmlrpc-epi-0.51/src/$d $d; done 79,80c79,80 intQ_Iter_Put(q_iter qi, void* data); // not read only! here for completeness. void* Q_Iter_Del(queue *q, q_iter iter); // not read only! here for completeness. --- intQ_Iter_Put(q_iter qi, void* data); /* not read only! here for completeness. */ void* Q_Iter_Del(queue *q, q_iter iter); /* not read only! here for completeness. */ 161c161 xml_element* xml_elem_new(); --- xml_element* xml_elem_new(void); 43a44,48 /* allow version to be specified via compile line define */ #ifndef XMLRPC_LIB_VERSION #define XMLRPC_LIB_VERSION 0.51 #endif 48c53 #define XMLRPC_VERSION_STR xmlrpc-epi v. VERSION --- #define XMLRPC_VERSION_STR xmlrpc-epi v. XMLRPC_LIB_VERSION 302c307 XMLRPC_CASE XMLRPC_GetDefaultIdCase(); --- XMLRPC_CASE XMLRPC_GetDefaultIdCase(void); 304c309 XMLRPC_CASE_COMPARISON XMLRPC_GetDefaultIdCaseComparison(); --- XMLRPC_CASE_COMPARISON XMLRPC_GetDefaultIdCaseComparison(void); 326c331 XMLRPC_VALUE XMLRPC_CreateValueEmpty(); --- XMLRPC_VALUE XMLRPC_CreateValueEmpty(void); 376c381 XMLRPC_REQUEST XMLRPC_RequestNew(); --- XMLRPC_REQUEST XMLRPC_RequestNew(void); 386,387c391,392 XMLRPC_SERVER XMLRPC_ServerCreate(); XMLRPC_SERVER XMLRPC_GetGlobalServer(); /* better to use XMLRPC_ServerCreate if you can */ --- XMLRPC_SERVER XMLRPC_ServerCreate(void); XMLRPC_SERVER XMLRPC_GetGlobalServer(void); /* better to use XMLRPC_ServerCreate if you can */ 407c412 const char* XMLRPC_GetVersionString(); --- const char* XMLRPC_GetVersionString(void); diff: /home/tbble/code/xmlrpcepi/build/xmlrpc-epi-0.51/src/xmlrpc_win32.h: No such file or directory -- --- Paul TBBle Hampson, B.Sc, LPI, MCSE On-hiatus Asian Studies student, ANU The Boss, Bubblesworth Pty Ltd (ABN: 51 095 284 361) [EMAIL PROTECTED] Of course Pacman didn't influence us as kids. If it did, we'd be running around in darkened rooms, popping pills and listening to repetitive music. -- Kristian Wilson, Nintendo, Inc, 1989 License: http://creativecommons.org/licenses/by/2.1/au/ --- pgpK29xrF41d9.pgp Description: PGP signature
Bug#413116: jamvm issues with java.util.logging
On Thu, Mar 08, 2007 at 12:02:50PM -0600, Bob Black wrote:
Does anyone have a logging.properties file that works with jamvm
(+ classpath)?
jamvm uses classpath's java.util.logging. I don't think it would require
any special content.
Here is an example:
== logging.properties
handlers = java.util.logging.ConsoleHandler
.level = WARNING
==
Maybe that bug was solved in another package (classpath?) or in a new
upload.
Otherwise, I either can't reproduce this bug or don't understand the
problem described in this bug: Is it that jamvm doesn't work, or just that
the java.util.logging package cannot be configured?
By default, GNU classpath looks in /usr/lib for the logging.properties
file (/usr/lib is the default value for gnu.classpath.home.url).
The logging.properties can also be specified with the
java.util.logging.config.file property:
java -Djava.util.logging.config.file=path to logging.properties ..
When there is no system wide logging.properties file, GNU classpath uses
default values (only = INFO messages are displayed on console).
This default looks good to me, and also it seems sane to require users (or
applications) to set java.util.logging.config.file if they want special
logging properties.
At one time, I've been able to have a strange behavior (the VM silently
quit, no Exception) with a given logging.properties file. But I can't
reproduce it currently (and I can't remember what was in this
logging.properties).
Any ideas? Has anyone gotten jamvm working with an app that uses
java.util.logging?
Yes, with the following app:
== Test.java =
import java.util.logging.*;
public class Test{
private static Logger logger = Logger.getLogger(Test);
public static void main(String argv[]){
logger.fine(FINE log);
logger.log(Level.WARNING,WARNING log);
logger.info(INFO log);
logger.log(Level.SEVERE,SEVERE log);
}
}
==
I compiled it with javac from jikes-sablevm (1.13-1.1).
I run it with jamvm (1.4.4-2); classpath (0.92-4). (I tried both running
it from a JAR and a .class file.)
3 persons could reproduce it (with real applications, not just this test).
So there could be an issue elsewhere.
Michel, Matthew, Bob, can you confirm that this bug still exists?
Can you try the above example? And if it works, can you also provide an
application which fails?
Your classpath's version could also be interesting.
Kind Regards,
--
Nekral
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#397400: rpm_4.4.1-11_sparc: FTBFS: relocation truncated to fit
reassign 397400 rpm close 397400 thanks This bug was marked as found and fixed in the same version so the code assumed this bug was still open. Removing the versions since this doesn't look like a bug in rpm. Kurt -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Processed: rpm_4.4.1-11_sparc: FTBFS: relocation truncated to fit
Processing commands for [EMAIL PROTECTED]: reassign 397400 rpm Bug#397400: rpm_4.4.1-11_sparc: FTBFS: relocation truncated to fit Bug reassigned from package `rpm' to `rpm'. close 397400 Bug#397400: rpm_4.4.1-11_sparc: FTBFS: relocation truncated to fit 'close' is deprecated; see http://www.debian.org/Bugs/Developer#closing. Bug is already closed, cannot re-close. thanks Stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#414410: zoneminder: FTBFS: build depends on inexistant package libmysqlclient14-dev
Package: zoneminder Version: 1.22.3-1 Severity: serious sbuild uses the first alternative of a build-depends. Please put libmysqlclient15-dev in first position of the alternative. Automatic build of zoneminder_1.22.3-1 on maxwell by sbuild/kfreebsd-i386 98 Build started at 20070311-1646 ** Checking available source versions... Fetching source files... Reading package lists... Building dependency tree... Need to get 1293kB of source archives. Get:1 http://people.debian.org unstable/main zoneminder 1.22.3-1 (dsc) [737B] Get:2 http://people.debian.org unstable/main zoneminder 1.22.3-1 (tar) [1265kB] Get:3 http://people.debian.org unstable/main zoneminder 1.22.3-1 (diff) [27.1kB] Fetched 1293kB in 8s (153kB/s) Download complete and in download only mode ** Using build dependencies supplied by package: Build-Depends: debhelper (= 4), dpatch, libgnutls-dev, libmysqlclient14-dev | libmysqlclient15-dev | libmysqlclient-dev, libdbd-mysql-perl, libdate-manip-perl, libwww-perl, libjpeg62-dev Checking for already installed source dependencies... debhelper: missing Using default version 5.0.42 dpatch: missing libgnutls-dev: missing libmysqlclient14-dev: missing libmysqlclient15-dev: missing libmysqlclient-dev: missing libdbd-mysql-perl: missing libdate-manip-perl: missing libwww-perl: missing libjpeg62-dev: missing Checking for source dependency conflicts... /usr/bin/sudo /usr/bin/apt-get --purge $CHROOT_OPTIONS -q -y install debhelper dpatch libgnutls-dev libmysqlclient14-dev libdbd-mysql-perl libdate-manip-perl libwww-perl libjpeg62-dev Reading package lists... Building dependency tree... Package libmysqlclient14-dev is not available, but is referred to by another package. This may mean that the package is missing, has been obsoleted, or is only available from another source However the following packages replace it: libalps-heap1-dev E: Package libmysqlclient14-dev has no installation candidate apt-get failed. Package installation failed Trying to reinstall removed packages: Trying to uninstall newly installed packages: Source-dependencies not satisfied; skipping zoneminder ** Finished at 20070311-1646 Build needed 00:00:00, 0k disk space -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#386469: Update: failed openbsd-inetd upgrade: plea for more info
On Sun, 11 Mar 2007, Leonardo Boselli wrote: Last time, when i reported bug, was on host workinprogress and update from -3 to -4 . Today i updated host freedom from -4 to -5 and the failure was the same, this time also locked the update of ipopd . After i stopped by hand openbsd-inetd the two packege ugraded fine. Could you please try to manually (with dpkg) reinstall -4 [1] and retry an upgrade (with either aptitude or apt-get as usual) to try to reproduce the problem and in the course of it try to narrow down the problem? Please, before doing it read the following to comments: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=386469#150 http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=386469#175 if we could shed some light on any of the points described in those two points then that would bring us further. Thanks and greets, *t [1] http://snapshot.debian.net/archive/2007/01/07/debian/pool/main/o/openbsd-inetd/openbsd-inetd_0.20050402-4_i386.deb On Fri, 9 Mar 2007, Tomas Pospisek wrote: What is irritating about all the bug reports after the upload of 0.20050402-4 is, that none of the screen dumps of the installation procedure show any trace of the upgrade routines first __stopping__ the openbsd-inetd. At my place upgrading openbsd-inetd from 0.20050402-4 to 0.20050402-5 looks like this: $ sudo apt-get install openbsd-inetd [...] Reading package lists... Done Building dependency tree... Done The following packages will be upgraded: openbsd-inetd 1 upgraded, 0 newly installed, 0 to remove and 6 not upgraded. [...] (Reading database ... 285517 files and directories currently installed.) Preparing to replace openbsd-inetd 0.20050402-4 (using .../openbsd-inetd_0.20050402-5_i386.deb) ... Stopping internet superserver: inetd. Unpacking replacement openbsd-inetd ... Setting up openbsd-inetd (0.20050402-5) ... Installing new version of config file /etc/init.d/openbsd-inetd ... Starting internet superserver: inetd. Note the line Stopping internet superserver: inetd.. This line is not present in either Kent West's bug report [1], Ben Low's report [2] (maybe just not visible there, since not the whole screen dump is included), Leonardo's report [3], Norman Messtorff's [4], Mind Booster Noori's [5], Daniel Blaschke's [6], Uwe Storbeck's [7], Mike Young's [8] or Luke Reeves' [9]. -- Tomas Pospisek http://sourcepole.com - Linux Open Source Solutions -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#386469: openbsd-inetd, action start failed when upgrading
Very strange, but i cannot reproduce this bug again on my machine. Upgrade from: -3 to -4: no problems -4 to -5: no problems -3 to -5: no problems -5 plain install: no problems. Every time purged the package. Downgrade from: -5 to -4: no problems All on the same machine i've reported some days ago. Ok, where are the voodoo doll's? Attached you will find a logfile with my trials and the snipplet of my dpkg.log from upgrade on 2007-03-05. This bug _must_ be in context with another package upgrade. How can i go on to help you? -- Norman Messtorff | http://normes.org Do _not_ use this Spamtrap: [EMAIL PROTECTED] 2007-03-05 09:11:27 upgrade libusb-0.1-4 2:0.1.12-2 2:0.1.12-5 2007-03-05 09:11:27 status half-configured libusb-0.1-4 2:0.1.12-2 2007-03-05 09:11:27 status unpacked libusb-0.1-4 2:0.1.12-2 2007-03-05 09:11:27 status half-installed libusb-0.1-4 2:0.1.12-2 2007-03-05 09:11:27 status half-installed libusb-0.1-4 2:0.1.12-2 2007-03-05 09:11:27 status unpacked libusb-0.1-4 2:0.1.12-5 2007-03-05 09:11:27 status unpacked libusb-0.1-4 2:0.1.12-5 2007-03-05 09:11:27 upgrade libsdl1.2debian 1.2.11-7 1.2.11-8 2007-03-05 09:11:27 status half-configured libsdl1.2debian 1.2.11-7 2007-03-05 09:11:27 status unpacked libsdl1.2debian 1.2.11-7 2007-03-05 09:11:27 status half-installed libsdl1.2debian 1.2.11-7 2007-03-05 09:11:27 status half-installed libsdl1.2debian 1.2.11-7 2007-03-05 09:11:27 status unpacked libsdl1.2debian 1.2.11-8 2007-03-05 09:11:27 status unpacked libsdl1.2debian 1.2.11-8 2007-03-05 09:11:27 upgrade libsdl1.2debian-oss 1.2.11-7 1.2.11-8 2007-03-05 09:11:27 status half-configured libsdl1.2debian-oss 1.2.11-7 2007-03-05 09:11:27 status unpacked libsdl1.2debian-oss 1.2.11-7 2007-03-05 09:11:27 status half-installed libsdl1.2debian-oss 1.2.11-7 2007-03-05 09:11:28 status half-installed libsdl1.2debian-oss 1.2.11-7 2007-03-05 09:11:28 status unpacked libsdl1.2debian-oss 1.2.11-8 2007-03-05 09:11:28 status unpacked libsdl1.2debian-oss 1.2.11-8 2007-03-05 09:11:29 status half-configured openbsd-inetd 0.20050402-5 2007-03-05 09:11:30 status unpacked libusb-0.1-4 2:0.1.12-5 2007-03-05 09:11:30 status half-configured libusb-0.1-4 2:0.1.12-5 2007-03-05 09:11:40 status installed libusb-0.1-4 2:0.1.12-5 2007-03-05 09:11:40 status unpacked libsdl1.2debian-oss 1.2.11-8 2007-03-05 09:11:40 status half-configured libsdl1.2debian-oss 1.2.11-8 2007-03-05 09:11:41 status installed libsdl1.2debian-oss 1.2.11-8 2007-03-05 09:11:41 status unpacked libsdl1.2debian 1.2.11-8 2007-03-05 09:11:41 status half-configured libsdl1.2debian 1.2.11-8 2007-03-05 09:11:41 status installed libsdl1.2debian 1.2.11-8 2007-03-05 09:11:45 status half-configured openbsd-inetd 0.20050402-5 2007-03-05 09:13:21 install linux-headers-2.6.18-4 keine 2.6.18.dfsg.1-11 2007-03-05 09:13:21 status half-installed linux-headers-2.6.18-4 2.6.18.dfsg.1-11 2007-03-05 09:13:23 status unpacked linux-headers-2.6.18-4 2.6.18.dfsg.1-11 2007-03-05 09:13:23 status unpacked linux-headers-2.6.18-4 2.6.18.dfsg.1-11 2007-03-05 09:13:23 install linux-headers-2.6.18-4-486 keine 2.6.18.dfsg.1-11 2007-03-05 09:13:23 status half-installed linux-headers-2.6.18-4-486 2.6.18.dfsg.1-11 2007-03-05 09:13:25 status unpacked linux-headers-2.6.18-4-486 2.6.18.dfsg.1-11 2007-03-05 09:13:25 status unpacked linux-headers-2.6.18-4-486 2.6.18.dfsg.1-11 2007-03-05 09:13:25 upgrade linux-headers-2.6-486 2.6.18+5 2.6.18+6 2007-03-05 09:13:25 status half-configured linux-headers-2.6-486 2.6.18+5 2007-03-05 09:13:25 status unpacked linux-headers-2.6-486 2.6.18+5 2007-03-05 09:13:25 status half-installed linux-headers-2.6-486 2.6.18+5 2007-03-05 09:13:25 status half-installed linux-headers-2.6-486 2.6.18+5 2007-03-05 09:13:25 status unpacked linux-headers-2.6-486 2.6.18+6 2007-03-05 09:13:25 status unpacked linux-headers-2.6-486 2.6.18+6 2007-03-05 09:13:27 status installed linux-headers-2.6.18-3-486 2.6.18-7 2007-03-05 09:13:28 remove linux-headers-2.6.18-3-486 2.6.18-7 2.6.18-7 2007-03-05 09:13:28 status half-configured linux-headers-2.6.18-3-486 2.6.18-7 2007-03-05 09:13:28 status half-installed linux-headers-2.6.18-3-486 2.6.18-7 2007-03-05 09:13:29 status config-files linux-headers-2.6.18-3-486 2.6.18-7 2007-03-05 09:13:29 status config-files linux-headers-2.6.18-3-486 2.6.18-7 2007-03-05 09:13:29 status config-files linux-headers-2.6.18-3-486 2.6.18-7 2007-03-05 09:13:29 status not-installed linux-headers-2.6.18-3-486 keine 2007-03-05 09:13:31 install linux-image-2.6.18-4-486 keine 2.6.18.dfsg.1-11 2007-03-05 09:13:31 status half-installed linux-image-2.6.18-4-486 2.6.18.dfsg.1-11 2007-03-05 09:13:37 status unpacked linux-image-2.6.18-4-486 2.6.18.dfsg.1-11 2007-03-05 09:13:37 status unpacked linux-image-2.6.18-4-486 2.6.18.dfsg.1-11 2007-03-05 09:13:37 install linux-image-2.6.18-4-686 keine 2.6.18.dfsg.1-11 2007-03-05 09:13:37 status half-installed linux-image-2.6.18-4-686 2.6.18.dfsg.1-11 2007-03-05 09:13:43 status unpacked linux-image-2.6.18-4-686 2.6.18.dfsg.1-11
Bug#386469: BUGREPORTERS PLEASE CHECK!
Hello Thomas, Unless I'm not misstaken (there are only indications but no evidence so far), then the cause of the problem we're witnessing here is, that /etc/init.d/openbsd-inetd stop is aparently *not* being executed before the update. Can anybody refute this? - In case you happen to witnessing the problem, can you affirm that this is effectively the case? inetd was running before upgrade and doesn't stopped during this task. I stopped inetd by hand and rerun te upgrade successfully. Restarting the upgrade without stopping inetd wasn't succeed. - Can you figure out why this is so? - Is /etc/init.d/openbsd-inetd possibly not executable? It was/is executable, i can stop inetd by hand. I couldn't see any changes on filesystem permissions too. - Is /etc/inetd.conf missing? No. -- Norman Messtorff | http://normes.org Do _not_ use this Spamtrap: [EMAIL PROTECTED] signature.asc Description: Digital signature
Bug#413041: jasper: heap corruption and segv's
Hi, I can reproduce the problem with i386, too. Working on it. Thanks, bye, Roland -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#414419: fails to install in d-i
Package: elilo Version: 3.6-3 Severity: grave Tags: d-i In my d-i logs, after elilo-installer reports elilo fails to install: Mar 11 17:51:23 apt-install: Setting up elilo (3.6-3) ... Mar 11 17:51:23 apt-install: dpkg: --compare-versions takes three arguments: v -- see shy jo signature.asc Description: Digital signature
Bug#414419: actual problem
The actual problem failing the install is farther on: Mar 11 17:51:23 apt-install: Running elilo... Mar 11 17:51:23 apt-install: elilo: /etc/elilo.conf: No such file or directory Mar 11 17:51:24 apt-install: dpkg: error processing elilo (--configure): Mar 11 17:51:24 apt-install: subprocess post-installation script returned erroMar 11 17:51:24 apt-install: Errors were encountered while processing: Mar 11 17:51:24 apt-install: elilo Maybe it's actually be an elilo-installer bug, if it's supposed to create elilo.conf. Oddly, the code to do so is as follows: bootpart=$RET rootfs=`mapdevfs $rootfs` # Write out elilo.conf # TODO: this template doesn't have the right text; need a different # template # for the progress bar title. db_progress START 0 2 debian-installer/elilo-installer/title db_progress INFO elilo-installer/progress_installing if ! apt-install elilo ; then Seems to be missing the actual code to write it, mm? The code seems to have never been in there; I checked elilo-installer in stable and it's the same. So how did this work back then? I was seeing successful installs on ia64 until near the beginning of March, timing that seems to point at the 3.6-3 upload of elilo. -- see shy jo signature.asc Description: Digital signature
Bug#413698: marked as done (aptitude: package does not ship any language files (LC_MESSAGES))
Your message dated Sun, 11 Mar 2007 18:47:03 + with message-id [EMAIL PROTECTED] and subject line Bug#413698: fixed in aptitude 0.4.4-3 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.) Debian bug tracking system administrator (administrator, Debian Bugs database) ---BeginMessage--- Package: aptitude Version: 0.4.4-2 Severity: grave Justification: renders package unusable # apt-get --download-only install aptitude Reading package lists... Done Building dependency tree... Done Suggested packages: tasksel Recommended packages: aptitude-doc-en aptitude-doc The following packages will be upgraded: aptitude 1 upgraded, 0 newly installed, 0 to remove and 26 not upgraded. Need to get 0B/1498kB of archives. After unpacking 4190kB disk space will be freed. [...] # dpkg -c ~deb/aptitude_0.4.4-2_i386.deb | grep LC drwxr-xr-x root/root 0 2007-03-05 08:05 ./usr/share/locale/ku/LC_MESSAGES/ drwxr-xr-x root/root 0 2007-03-05 08:05 ./usr/share/locale/ru/LC_MESSAGES/ drwxr-xr-x root/root 0 2007-03-05 08:05 ./usr/share/locale/ja/LC_MESSAGES/ drwxr-xr-x root/root 0 2007-03-05 08:05 ./usr/share/locale/pl/LC_MESSAGES/ drwxr-xr-x root/root 0 2007-03-05 08:05 ./usr/share/locale/tr/LC_MESSAGES/ drwxr-xr-x root/root 0 2007-03-05 08:05 ./usr/share/locale/lt/LC_MESSAGES/ drwxr-xr-x root/root 0 2007-03-05 08:05 ./usr/share/locale/sv/LC_MESSAGES/ drwxr-xr-x root/root 0 2007-03-05 08:05 ./usr/share/locale/da/LC_MESSAGES/ drwxr-xr-x root/root 0 2007-03-05 08:05 ./usr/share/locale/cs/LC_MESSAGES/ drwxr-xr-x root/root 0 2007-03-05 08:05 ./usr/share/locale/km/LC_MESSAGES/ drwxr-xr-x root/root 0 2007-03-05 08:05 ./usr/share/locale/es/LC_MESSAGES/ drwxr-xr-x root/root 0 2007-03-05 08:05 ./usr/share/locale/sk/LC_MESSAGES/ drwxr-xr-x root/root 0 2007-03-05 08:05 ./usr/share/locale/nn/LC_MESSAGES/ drwxr-xr-x root/root 0 2007-03-05 08:05 ./usr/share/locale/ca/LC_MESSAGES/ drwxr-xr-x root/root 0 2007-03-05 08:05 ./usr/share/locale/it/LC_MESSAGES/ drwxr-xr-x root/root 0 2007-03-05 08:05 ./usr/share/locale/zh_TW/LC_MESSAGES/ drwxr-xr-x root/root 0 2007-03-05 08:05 ./usr/share/locale/vi/LC_MESSAGES/ drwxr-xr-x root/root 0 2007-03-05 08:05 ./usr/share/locale/tl/LC_MESSAGES/ drwxr-xr-x root/root 0 2007-03-05 08:05 ./usr/share/locale/nl/LC_MESSAGES/ drwxr-xr-x root/root 0 2007-03-05 08:05 ./usr/share/locale/fi/LC_MESSAGES/ drwxr-xr-x root/root 0 2007-03-05 08:05 ./usr/share/locale/ro/LC_MESSAGES/ drwxr-xr-x root/root 0 2007-03-05 08:05 ./usr/share/locale/fr/LC_MESSAGES/ drwxr-xr-x root/root 0 2007-03-05 08:05 ./usr/share/locale/gl/LC_MESSAGES/ drwxr-xr-x root/root 0 2007-03-05 08:05 ./usr/share/locale/ar/LC_MESSAGES/ drwxr-xr-x root/root 0 2007-03-05 08:05 ./usr/share/locale/bs/LC_MESSAGES/ drwxr-xr-x root/root 0 2007-03-05 08:05 ./usr/share/locale/zh_CN/LC_MESSAGES/ drwxr-xr-x root/root 0 2007-03-05 08:05 ./usr/share/locale/nb/LC_MESSAGES/ drwxr-xr-x root/root 0 2007-03-05 08:05 ./usr/share/locale/eu/LC_MESSAGES/ drwxr-xr-x root/root 0 2007-03-05 08:05 ./usr/share/locale/de/LC_MESSAGES/ drwxr-xr-x root/root 0 2007-03-05 08:05 ./usr/share/locale/el/LC_MESSAGES/ drwxr-xr-x root/root 0 2007-03-05 08:05 ./usr/share/locale/pt_BR/LC_MESSAGES/ drwxr-xr-x root/root 0 2007-03-05 08:05 ./usr/share/locale/hu/LC_MESSAGES/ drwxr-xr-x root/root 0 2007-03-05 08:05 ./usr/share/locale/pt/LC_MESSAGES/ regards, -mika- ---End Message--- ---BeginMessage--- Source: aptitude Source-Version: 0.4.4-3 We believe that the bug you reported is fixed in the latest version of aptitude, which is due to be installed in the Debian FTP archive: aptitude-doc-cs_0.4.4-3_all.deb to pool/main/a/aptitude/aptitude-doc-cs_0.4.4-3_all.deb aptitude-doc-en_0.4.4-3_all.deb to pool/main/a/aptitude/aptitude-doc-en_0.4.4-3_all.deb aptitude-doc-fi_0.4.4-3_all.deb to pool/main/a/aptitude/aptitude-doc-fi_0.4.4-3_all.deb aptitude-doc-fr_0.4.4-3_all.deb to pool/main/a/aptitude/aptitude-doc-fr_0.4.4-3_all.deb aptitude_0.4.4-3.diff.gz to pool/main/a/aptitude/aptitude_0.4.4-3.diff.gz aptitude_0.4.4-3.dsc to pool/main/a/aptitude/aptitude_0.4.4-3.dsc aptitude_0.4.4-3_i386.deb to pool/main/a/aptitude/aptitude_0.4.4-3_i386.deb 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
Bug#414419: fails to install in d-i
Quoting Joey Hess ([EMAIL PROTECTED]): Package: elilo Version: 3.6-3 Severity: grave Tags: d-i In my d-i logs, after elilo-installer reports elilo fails to install: Mar 11 17:51:23 apt-install: Setting up elilo (3.6-3) ... Mar 11 17:51:23 apt-install: dpkg: --compare-versions takes three arguments: v This seems to be a syntax error in the newly added config script. I guess that the attached patch should fix that bug (untested). --- debian/elilo.config.old 2007-03-11 19:45:42.504732828 +0100 +++ debian/elilo.config 2007-03-11 19:45:51.080798090 +0100 @@ -4,7 +4,7 @@ . /usr/share/debconf/confmodule -if [ 2 ] dpkg --compare-versions $2 lt 3.2-1 +if [ $2 ] dpkg --compare-versions $2 lt 3.2-1 then db_input high elilo/format || true else signature.asc Description: Digital signature
Bug#394142: FTBSF on ia64: error CS0136: A local variable named `args' cannot be declared...
close 394142 0.3.0-1 thanks So, the problem is that the changelog in unstable and in testing don't seem to perfectly match. In testing we have: 0.2.1-1 - 0.2.1-1.1 In unstable we have: 0.2.1-1 - 0.2.1-1ubuntu1 - 0.2.1-1.1 So the BTS thinks that the version in testing and the version in unstable are from different branches. I'm marking it as closed in 0.3.0-1 since that was the next upload to Debian which didn't have this problem. Kurt -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Processed: Re: FTBSF on ia64: error CS0136: A local variable named `args' cannot be declared...
Processing commands for [EMAIL PROTECTED]: close 394142 0.3.0-1 Bug#394142: FTBSF on ia64: error CS0136: A local variable named `args' cannot be declared... 'close' is deprecated; see http://www.debian.org/Bugs/Developer#closing. Bug marked as fixed in version 0.3.0-1, send any further explanations to Martin Michlmayr [EMAIL PROTECTED] thanks Stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#413534: Another 64bit problem (binding SQL_C_SLONG values)
Hello, http://msdn2.microsoft.com/en-us/library/ms714556.aspx says that SQL_C_SLONG represents a long int. convert.c has it like this: case SQL_C_SLONG: case SQL_C_LONG: len = 4; if (bind_size 0) *((SDWORD *) rgbValueBindRow) = atol(neut_str); else *((SDWORD *) rgbValue + bind_row) = atol(neut_str); break; but here on amd64 sizeof(long int) == 8. I had a look at upstream: http://cvs.pgfoundry.org/cgi-bin/cvsweb.cgi/psqlodbc/psqlodbc/convert.c?rev=1.155content-type=text/x-cvsweb-markup and it looks like it's still wrong. Ciao, Enrico -- GPG key: 1024D/797EBFAB 2000-12-05 Enrico Zini [EMAIL PROTECTED] signature.asc Description: Digital signature
Bug#386469: Debian: failed openbsd-inetd upgrade: plea for more info
Tomas Pospisek wrote: You could have a try at downgrading openbsd-inetd manually (through dpkg) back to 0.20050402-4 [1] and then try to reproduce the problem again with aptitude... ? *t I went ahead and downgraded openbsd-inetd back to 0.20050402-4 and retried the upgrade. Everything went smoothly. So I decided to try some of the other packages that I upgraded previously at the same time. They all seemed to go well except for uw-imapd (the one with the error previously). This time around there was a more serious error than just openbsd-inetd not restarting. uw-imapd hung during its postrm. The actual postrm script went defunct and the parent perl instance had to be killed to get aptitude moving again. After killing the uw-imapd install, the openbsd-inetd install failed every time. Both uw-imapd and openbsd-inetd can be upgraded by themselves just fine. When they are upgraded together, they cause problems. I have attached my console log. Here's what I see happening: 1) during removal of openbsd-inetd, we stop the running instance of inetd. - I can confirm this occurs 2) during removal of uw-imapd, we invoke update-inetd (postrm), this seems to hang. (I do not remember a hang during my initial report... there was a dpkg error with uw-imapd, but not a hang) 3) Step 2 above causes a new instance of inetd to be started - I can confirm this occurs via manually stopping inetd and invoking update-inetd manually 4) when openbsd-inetd attempts to start a new process, there is already one running. I can reproduce this 100% on my system with the following packages being upgraded via aptitude at the same time. [UPGRADE] openbsd-inetd 0.20050402-4 - 0.20050402-5 [UPGRADE] uw-imapd 7:2002edebian1-13 - 7:2002edebian1-13.1 Since openbsd-inetd has already been removed, any future attempt to install it requires manual intervention. I can imagine this scenario is going to apply to many more packages than just uw-imapd. Anything that performs an update-inetd during its postrm script will cause this same behavior. --Mike Young newcomp:/var/cache/apt/archives# dpkg -i uw-imapd_2002edebian1-13_amd64.deb dpkg - warning: downgrading uw-imapd from 2002edebian1-13.1 to 2002edebian1-13. (Reading database ... 201197 files and directories currently installed.) Preparing to replace uw-imapd 7:2002edebian1-13.1 (using uw-imapd_2002edebian1-13_amd64.deb) ... Unpacking replacement uw-imapd ... Setting up uw-imapd (2002edebian1-13) ... You already have /etc/ssl/certs/imapd.pem newcomp:/var/cache/apt/archives# dpkg -i openbsd-inetd_0.20050402-4_amd64.deb dpkg - warning: downgrading openbsd-inetd from 0.20050402-5 to 0.20050402-4. (Reading database ... 201197 files and directories currently installed.) Preparing to replace openbsd-inetd 0.20050402-5 (using openbsd-inetd_0.20050402-4_amd64.deb) ... Stopping internet superserver: inetd. Unpacking replacement openbsd-inetd ... Setting up openbsd-inetd (0.20050402-4) ... Installing new version of config file /etc/init.d/openbsd-inetd ... Starting internet superserver: inetd. newcomp:/var/cache/apt/archives# aptitude Preconfiguring packages ... (Reading database ... 201197 files and directories currently installed.) Preparing to replace openbsd-inetd 0.20050402-4 (using .../openbsd-inetd_0.20050402-5_amd64.deb) ... Stopping internet superserver: inetd. Unpacking replacement openbsd-inetd ... Preparing to replace uw-imapd 7:2002edebian1-13 (using .../uw-imapd_7%3a2002edebian1-13.1_amd64.deb) ... Unpacking replacement uw-imapd ... dpkg: error processing /var/cache/apt/archives/uw-imapd_7%3a2002edebian1-13.1_amd64.deb (--unpack): dpkg: warning - old post-removal script killed by signal (Terminated) You already have /etc/ssl/certs/imapd.pem Errors were encountered while processing: /var/cache/apt/archives/uw-imapd_7%3a2002edebian1-13.1_amd64.deb E: Sub-process /usr/bin/dpkg returned an error code (1) A package failed to install. Trying to recover: Setting up openbsd-inetd (0.20050402-5) ... Installing new version of config file /etc/init.d/openbsd-inetd ... Starting internet superserver: inetdinvoke-rc.d: initscript openbsd-inetd, action start failed. dpkg: error processing openbsd-inetd (--configure): subprocess post-installation script returned error exit status 1 Errors were encountered while processing: openbsd-inetd Press return to continue.
Bug#414380: amaya does not start. X Window System error serial 10426 error_code 8 request_code 144 minor_code 5
Regis Boudin wrote: For more informations, see bug #357439 : http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=357439 Regis, do you think we can merge these? -- ·''`. If I can't dance to it, it's not my revolution : :' :-- Emma Goldman `. `' Proudly running Debian GNU/Linux (unstable) `- www.amayita.com www.malapecora.com www.chicasduras.com
Bug#402675: tinyerp-client: l10n broken
close 402675 4.0.0-1 thanks Marking as closed in 4.0.0-1, since there wasn't any 4.0 in Debian. Kurt -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#404875: toolbar-fancy: Appears to do nothing
reassign 404875 toolbar-fancy close 404875 thanks Since the version it was found and fixed in are the same, the BTS assumes it's still open. So I'm clearing the version information. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Processed: toolbar-fancy: Appears to do nothing
Processing commands for [EMAIL PROTECTED]: reassign 404875 toolbar-fancy Bug#404875: toolbar-fancy: Appears to do nothing Bug reassigned from package `toolbar-fancy' to `toolbar-fancy'. close 404875 Bug#404875: toolbar-fancy: Appears to do nothing 'close' is deprecated; see http://www.debian.org/Bugs/Developer#closing. Bug is already closed, cannot re-close. thanks Stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#414380: amaya does not start. X Window System error serial 10426 error_code 8 request_code 144 minor_code 5
On Sun, 2007-03-11 at 20:50 +0100, Amaya wrote: Regis Boudin wrote: For more informations, see bug #357439 : http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=357439 Regis, do you think we can merge these? I'm not sure the BTS would be very happy about merging bugs assigned to different packages... Considering this bug only affects the package in some specific situations, I will probably downgrade it to important. And I will leave it assigned to this package, because if I reassign it to wxWidgets and merge, it will only be a couple of weeks before someone else opens the same bug again... If you have another idea on how to handle the situation, suggestions are welcome :) Regis -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#413116: jamvm issues with java.util.logging
Nicolas François wrote: Michel, Matthew, Bob, can you confirm that this bug still exists? Can you try the above example? And if it works, can you also provide an application which fails? Your example works fine when loading the class directly from the filesystem: $ jamvm -Djava.util.logging.config.file=$PWD/test-logging.properties Test Mar 11, 2007 9:23:15 PM Test main WARNING: WARNING log Mar 11, 2007 9:23:16 PM Test main SEVERE: SEVERE log However, If I try to run the example from a jar file, a NullPointerException occurs: $ jar cf test.jar Test.class $ jamvm -Djava.util.logging.config.file=$PWD/test-logging.properties \ -cp test.jar Test Exception occurred while VM initialising. java/lang/NullPointerException I get the same error when trying to run other applications which are archived in a jar-file (e.g. jWAP or the JFC demos from the Sun JDK). Seems like there's a general problem with handling of jar files... Your classpath's version could also be interesting. ii classpath 0.91-3 clean room standard Java libraries ii jamvm 1.4.4-1virtual machine which conforms to ... Cheers, Michel
Processed: Re: tinyerp-client: l10n broken
Processing commands for [EMAIL PROTECTED]: close 402675 4.0.0-1 Bug#402675: l10n broken 'close' is deprecated; see http://www.debian.org/Bugs/Developer#closing. Bug marked as fixed in version 4.0.0-1, send any further explanations to [EMAIL PROTECTED] thanks Stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#413116: jamvm issues with java.util.logging
On Sun, 11 Mar 2007, Nicolas Fran�ois wrote:
Otherwise, I either can't reproduce this bug or don't understand the
problem described in this bug: Is it that jamvm doesn't work, or just that
the java.util.logging package cannot be configured?
Jamvm does not work on the trivial Java program _when in a jar_
(standalone is fine)
By default, GNU classpath looks in /usr/lib for the logging.properties
file (/usr/lib is the default value for gnu.classpath.home.url).
And classpath doesn't supply this file.
When there is no system wide logging.properties file, GNU classpath uses
default values (only = INFO messages are displayed on console).
This default looks good to me, and also it seems sane to require users (or
applications) to set java.util.logging.config.file if they want special
logging properties.
jamvm with -jar or -cp on a jar seems to fail, however.
Michel, Matthew, Bob, can you confirm that this bug still exists?
Can you try the above example? And if it works, can you also provide an
application which fails?
Test below, this is in a clean etch chroot with just classpath, ecj and jamvm
installed.
[EMAIL PROTECTED]:/root# cat test.java
public class test
{
public static void main(String[] args)
{
System.out.println(Hello World);
}
}
[EMAIL PROTECTED]:/root# javac -version
Eclipse Java Compiler v_677_R32x, 3.2.1 release, Copyright IBM Corp 2000, 2006.
All rights reserved.
[EMAIL PROTECTED]:/root# javac test.java
[EMAIL PROTECTED]:/root# jar --version
jar (fastjar) 0.92-gcc-4.1
[EMAIL PROTECTED]:/root# jar cf hello.jar test.class
[EMAIL PROTECTED]:/root# jamvm -version
java version 1.4.2
JamVM version 1.4.4
[EMAIL PROTECTED]:/root# jamvm -jar hello.jar
Exception occurred while VM initialising.
java/io/FileNotFoundException: No such file or directory:
/usr/lib/logging.properties
[EMAIL PROTECTED]:/root# jamvm -cp hello.jar test
Exception occurred while VM initialising.
java/io/FileNotFoundException: No such file or directory:
/usr/lib/logging.properties
[EMAIL PROTECTED]:/root# jamvm test
Hello World
[EMAIL PROTECTED]:/root# dpkg -s jamvm
Package: jamvm
Status: install ok installed
Priority: optional
Section: interpreters
Installed-Size: 436
Maintainer: Michael Koch [EMAIL PROTECTED]
Architecture: i386
Version: 1.4.4-1
Provides: java-virtual-machine, java1-runtime
Depends: libc6 (= 2.3.6-6), zlib1g (= 1:1.2.1), java-common, classpath (=
2:0.91), classpath-common (= 2:0.91)
Description: virtual machine which conforms to JVM specification 2
JamVM is a new Java Virtual Machine which conforms to the JVM
specification version 2 (blue book). In comparison to most other
VM's (free and commercial) it is extremely small, with a stripped
executable on PowerPC of only ~110K, and Intel 80K. However, unlike
other small VMs (e.g. KVM) it is designed to support the full
specification, and includes support for object finalisation, the
Java Native Interface (JNI) and the Reflection API.
[EMAIL PROTECTED]:/root# dpkg -s classpath
Package: classpath
Status: install ok installed
Priority: optional
Section: libs
Installed-Size: 944
Maintainer: Debian Java Maintainers
pkg-java-maintainers@lists.alioth.debian.org
Architecture: i386
Version: 2:0.91-3
Depends: libgcj-common, classpath-common (= 2:0.13-1), libasound2 ( 1.0.11), libatk1.0-0 (= 1.9.0), libaudio2, libc6 (=
2.3.6-6), libcairo2 (= 1.0.2-2), libfontconfig1 (= 2.3.0), libfreetype6 (= 2.2), libgcc1 (= 1:4.1.0), libglib2.0-0 (=
2.10.0), libgtk2.0-0 (= 2.8.0), libice6, libjack0.100.0-0 (= 0.101.1), libpango1.0-0 (= 1.12.1), libpng12-0 (= 1.2.8rel),
libqt4-core (= 4.1.2), libqt4-gui (= 4.1.2), libsm6, libstdc++6 (= 4.1.0), libx11-6, libxcursor1 ( 1.1.2), libxext6,
libxfixes3, libxi6, libxinerama1, libxrandr2, libxrender1, libxt6, libxtst6, zlib1g (= 1:1.2.1)
Conflicts: libgcj3 (= 1:3.2-0pre1), jamvm ( 1.4.3), cacao ( 0.96)
Description: clean room standard Java libraries
Our goal is to provide a free replacement for Sun's proprietary class
libraries so that the GNU system can run programs written in the Java
language.
.
GNU Classpath makes it possible to compile DFSG-free programs written
in the Java language without depending on proprietary class libraries.
.
GNU Classpath can be used to run Java applications without depending on
proprietary software.
[EMAIL PROTECTED]:/root#
Matt
--
Matthew Johnson
http://www.matthew.ath.cx/
Bug#407746: [URGENT] Please update debconf PO translation for the package libpam-ldap 180-1.7
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 03/11/2007 02:50 AM, Steve Langasek wrote: On Sat, Mar 10, 2007 at 10:01:22PM -0300, Felipe Augusto van de Wiel (faw) wrote: But there is a problem with this translation: @@ -319,6 +305,8 @@ #: ../templates:9001 msgid LDAP server Uniform Resource Identifier: msgstr +Identificador de Recurso Uniforme (URI -- Uniform Resource Identifier) do +Servidor LDAP: #. Type: string #. Description This is a debconf short description, and the translation needs to fit on a single line in order to display correctly on 80-column terminals. podebconf-display-po show it correctly, Really? When I run podebconf-display-po, I don't see any short descriptions at all. Hmmm, ok, just to be sure, I did a screenshot of my terminal using a copy-and-paste with mouse. I'm using xterm (UTF-8) with screen, and I run podebconf-display-po, below is the entire xterm pasted, it seems fine on my MUA (IceApe) I hope it shows fine in the BTS and other fixed-font-size MUAs. :-) Package configuration ┌───┤ ├┐ │ Por favor, informe a URI do servidor LDAP usado. Isto é uma texto na │ │ forma ldap://nome-da-maquina ou IP:porta/ , ldaps:// ou ldapi:// │ │ também podem ser usados. O número da porta é opcional.│ │ │ │ Nota: É normalmente uma boa idéia usar um endereço IP; isto reduz riscos │ │ de falhas no caso do servidor de nomes não estar disponível. │ │ │ │ XXX Identificador de Recurso Uniforme (URI -- Uniform Resource│ │ Identifier) do Servidor LDAP: │ │ │ │ _ │ │ │ │ Ok │ │ │ └───┘ See the XXX, I marked it to be sure, and it just wrapped the line, because of that I thought it was OK, but I will take care next time. ;) Kind regards, - -- Felipe Augusto van de Wiel (faw) Debian. Freedom to code. Code to freedom! -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.6 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFF9Hd+CjAO0JDlykYRAiBEAJ98X2Uqg7Mds75KIc1ksmDPk0r1LwCeM28g /i/SixWrSOrmzn0ogS9nJVw= =hpMP -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#407361: libtowitoko2: postinst calls wrong paramter for pscd restart install fails
Version: 2.0.7-7.3 Hello, This bug was fixed in the above-mentioned NMU version, but unfortunately the bug closure message never reached the BTS due to a mail problem in the BTS. The changelog for this NMU is as follows. towitoko (2.0.7-7.3) unstable; urgency=high * Non-maintainer upload. * High-urgency upload for RC bugfix. * Use invoke-rc.d and the standard 'restart' command for pcscd in postinst/postrm, instead of calling the pcscd init script directly with the no-longer-supported 'restart-if-running' command. Closes: #407361. -- Steve Langasek [EMAIL PROTECTED] Sun, 11 Mar 2007 03:12:04 -0700 Cheers, -- Steve Langasek Give me a lever long enough and a Free OS Debian Developer to set it on, and I can move the world. [EMAIL PROTECTED] http://www.debian.org/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#386469: openbsd-inetd, action start failed when upgrading
On Sun, Mar 11, 2007 at 05:42:38PM +0100, Norman Messtorff wrote: Attached you will find a logfile with my trials and the snipplet of my dpkg.log from upgrade on 2007-03-05. Ok, but this dpkg.log only shows the status of openbsd-inetd *after* the upgrade has been started. Context at the beginning of the upgrade process is missing, so it's certainly not possible to figure out what other package might be involved here from the provided log. -- Steve Langasek Give me a lever long enough and a Free OS Debian Developer to set it on, and I can move the world. [EMAIL PROTECTED] http://www.debian.org/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#386469: Update: failed openbsd-inetd upgrade: plea for more info
On Sun, 11 Mar 2007, Tomas Pospisek wrote: On Sun, 11 Mar 2007, Leonardo Boselli wrote: Last time, when i reported bug, was on host workinprogress and update from -3 to -4 . Today i updated host freedom from -4 to -5 and the failure was the same, this time also locked the update of ipopd . After i stopped by hand openbsd-inetd the two packege ugraded fine. Could you please try to manually (with dpkg) reinstall -4 [1] and retry an upgrade (with either aptitude or apt-get as usual) to try to reproduce the i tried on a third machine, more or less the twin of freedom (that failed -4 to -5 together with ipopd), and now it went smoot. I upgraded to 5 also the machine that gave me problem on -3 to -4 and ok. i downgraded again ... ok ... Only a difference: today i used apt-get install, the other times dselect ... A possibility: tha package fail to stop inentd since there are pop3/imapd services in progress ? could be an explanation fro freedom, but unlikely for workinprogress that does not have mail services running ... -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Processed: Re: jamvm issues with java.util.logging
Processing commands for [EMAIL PROTECTED]: reassign 413116 classpath 0.91-3 Bug#413116: jamvm: missing file: /usr/lib/logging.properties Bug reassigned from package `jamvm' to `classpath'. # I tested it with 0.92-4, but 0.92-1 was probably fixed too. notfound 413116 0.92-4 Bug#413116: jamvm: missing file: /usr/lib/logging.properties Bug marked as not found in version 0.92-4. tags 413116 patch Bug#413116: jamvm: missing file: /usr/lib/logging.properties Tags were: confirmed Tags added: patch thanks Stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#412648: marked as done (libtowitoko2: Impossible to install because of bug 407361)
Your message dated Sun, 11 Mar 2007 15:55:09 -0700 with message-id [EMAIL PROTECTED] and subject line libtowitoko2: postinst calls wrong paramter for pscd restart install fails 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.) Debian bug tracking system administrator (administrator, Debian Bugs database) ---BeginMessage--- Package: libtowitoko2 Version: 2.0.7-7.2 Severity: normal Please fix this bug (40 days and now some generic package depend on it). -- System Information: Debian Release: 4.0 APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.20.1 Locale: [EMAIL PROTECTED], [EMAIL PROTECTED] (charmap=ISO-8859-15) (ignored: LC_ALL set to [EMAIL PROTECTED]) Versions of packages libtowitoko2 depends on: ii debconf [debconf-2.0] 1.5.11 Debian configuration management sy ii libc6 2.3.6.ds1-13 GNU C Library: Shared libraries libtowitoko2 recommends no packages. -- debconf information: * libtowitoko2/port: USB ---End Message--- ---BeginMessage--- Version: 2.0.7-7.3 Hello, This bug was fixed in the above-mentioned NMU version, but unfortunately the bug closure message never reached the BTS due to a mail problem in the BTS. The changelog for this NMU is as follows. towitoko (2.0.7-7.3) unstable; urgency=high * Non-maintainer upload. * High-urgency upload for RC bugfix. * Use invoke-rc.d and the standard 'restart' command for pcscd in postinst/postrm, instead of calling the pcscd init script directly with the no-longer-supported 'restart-if-running' command. Closes: #407361. -- Steve Langasek [EMAIL PROTECTED] Sun, 11 Mar 2007 03:12:04 -0700 Cheers, -- Steve Langasek Give me a lever long enough and a Free OS Debian Developer to set it on, and I can move the world. [EMAIL PROTECTED] http://www.debian.org/ ---End Message---
Bug#407361: marked as done (libtowitoko2: postinst calls wrong paramter for pscd restart install fails)
Your message dated Sun, 11 Mar 2007 15:55:09 -0700
with message-id [EMAIL PROTECTED]
and subject line libtowitoko2: postinst calls wrong paramter for pscd restart
install fails
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.)
Debian bug tracking system administrator
(administrator, Debian Bugs database)
---BeginMessage---
Package: libtowitoko2
Version: 2.0.7-7.1
Severity: normal
Subject: libtowitoko2: postinst calls wrong paramter for pscd restart install
fails
Package: libtowitoko2
Version: 2.0.7-7.1
Severity: normal
-- System Information:
Debian Release: 4.0
APT prefers testing
APT policy: (500, 'testing')
Architecture: i386 (i686)
Shell: /bin/sh linked to /bin/bash
Kernel: Linux 2.6.17-2-686
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
The postinst wants to do a
if [ -x /etc/init.d/pcscd ]; then
/etc/init.d/pcscd restart-if-running 3/dev/null
fi
but the current initscript of pscd only supports restart
So please fix your package
[EMAIL PROTECTED]:~$ sudo apt-get -f install
Reading package lists... Done
Building dependency tree... Done
0 upgraded, 0 newly installed, 0 to remove and 12 not upgraded.
3 not fully installed or removed.
Need to get 0B of archives.
After unpacking 0B of additional disk space will be used.
Setting up libtowitoko2 (2.0.7-7.1) ...
Usage: /etc/init.d/pcscd {start|stop|restart|force-reload}
dpkg: error processing libtowitoko2 (--configure):
subprocess post-installation script returned error exit status 3
dpkg: dependency problems prevent configuration of smartcard:
smartcard depends on libtowitoko2 (= 2.0.7); however:
Package libtowitoko2 is not configured yet.
dpkg: error processing smartcard (--configure):
dependency problems - leaving unconfigured
dpkg: dependency problems prevent configuration of gsmartcard:
gsmartcard depends on smartcard; however:
Package smartcard is not configured yet.
dpkg: error processing gsmartcard (--configure):
dependency problems - leaving unconfigured
Errors were encountered while processing:
libtowitoko2
smartcard
gsmartcard
E: Sub-process /usr/bin/dpkg returned an error code (1)
[EMAIL PROTECTED]:~$
-- System Information:
Debian Release: 4.0
APT prefers testing
APT policy: (500, 'testing')
Architecture: i386 (i686)
Shell: /bin/sh linked to /bin/bash
Kernel: Linux 2.6.17-2-686
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
---End Message---
---BeginMessage---
Version: 2.0.7-7.3
Hello,
This bug was fixed in the above-mentioned NMU version, but unfortunately the
bug closure message never reached the BTS due to a mail problem in the BTS.
The changelog for this NMU is as follows.
towitoko (2.0.7-7.3) unstable; urgency=high
* Non-maintainer upload.
* High-urgency upload for RC bugfix.
* Use invoke-rc.d and the standard 'restart' command for pcscd in
postinst/postrm, instead of calling the pcscd init script directly with
the no-longer-supported 'restart-if-running' command. Closes: #407361.
-- Steve Langasek [EMAIL PROTECTED] Sun, 11 Mar 2007 03:12:04 -0700
Cheers,
--
Steve Langasek Give me a lever long enough and a Free OS
Debian Developer to set it on, and I can move the world.
[EMAIL PROTECTED] http://www.debian.org/
---End Message---
Bug#386469: Debian: failed openbsd-inetd upgrade: plea for more info
On Sun, Mar 11, 2007 at 03:57:10PM -0400, Mike Young wrote: So I decided to try some of the other packages that I upgraded previously at the same time. They all seemed to go well except for uw-imapd (the one with the error previously). This time around there was a more serious error than just openbsd-inetd not restarting. uw-imapd hung during its postrm. The actual postrm script went defunct and the parent perl instance had to be killed to get aptitude moving again. After killing the uw-imapd install, the openbsd-inetd install failed every time. Both uw-imapd and openbsd-inetd can be upgraded by themselves just fine. When they are upgraded together, they cause problems. I have attached my console log. Here's what I see happening: 1) during removal of openbsd-inetd, we stop the running instance of inetd. - I can confirm this occurs 2) during removal of uw-imapd, we invoke update-inetd (postrm), this seems to hang. (I do not remember a hang during my initial report... there was a dpkg error with uw-imapd, but not a hang) 3) Step 2 above causes a new instance of inetd to be started - I can confirm this occurs via manually stopping inetd and invoking update-inetd manually 4) when openbsd-inetd attempts to start a new process, there is already one running. Sure enough, I can reproduce this problem here. Here's what happens for me: - the old openbsd-inetd's prerm is called, stopping inetd. this deconfigures openbsd-inetd, but does *not* correctly deconfigure netbase which depends on it. (or, the user may have another provider of inet-superserver installed, so it's not incorrect to leave netbase configured.) - uw-imapd's dependencies are all satisfied (since netbase was never deconfigured), so uw-imapd is configured, which calls update-inetd --add and/or update-inetd --enable. - update-inetd calls invoke-rc.d openbsd-inetd restart, which does not just force a reload of the config (like force-reload does), it *starts* openbsd-inetd if not already running. - openbsd-inetd is configured, tries to start its daemon which is already running, and fails. This also explains the hang in uw-imapd's maintainer script; after starting inetd, the debconf frontend can no longer exit when the postinst has exited because the inetd process is still attached to that frontend. Marco, I understand that openbsd-inetd is designed to only run when there are configured services for it to listen to, but I wonder if that's wise given that this bug falls out directly from that decision. If inetd could be trusted to be running all the time when configured, then invoke-rc.d openbsd-inetd force-reload would be all that update-inetd would ever need, and inetd would never be started out of order. Anyway, given that dpkg's behavior doesn't seem to be new and isn't likely to change before etch, I see two options: - openbsd-inetd can forcibly stop inetd again in its postinst before starting it. - openbsd-inetd can be changed to always run even when no services are configured, and update-inetd can be switched to use force-reload instead of restart. -- Steve Langasek Give me a lever long enough and a Free OS Debian Developer to set it on, and I can move the world. [EMAIL PROTECTED] http://www.debian.org/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#414381: marked as done (sshfs from testing-proposed-updates is uninstallable due wrong dependences)
Your message dated Sun, 11 Mar 2007 17:36:33 -0700 with message-id [EMAIL PROTECTED] and subject line Bug#414381: sshfs from testing-proposed-updates is uninstallable due wrong dependences 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.) Debian bug tracking system administrator (administrator, Debian Bugs database) ---BeginMessage--- Package: sshfs Version: 1.6-1+b1 Severity: grave It depends on non-existed package libfuse, but should depend on libfuse2, like version from testing or unstable. -- System Information: Debian Release: 4.0 APT prefers testing-proposed-updates APT policy: (720, 'testing-proposed-updates'), (720, 'testing'), (670, 'proposed-updates'), (670, 'stable'), (600, 'unstable'), (550, 'experimental') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.18-4-vserver-686 Locale: LANG=ru_RU.KOI8-R, LC_CTYPE=ru_RU.KOI8-R (charmap=KOI8-R) ---End Message--- ---BeginMessage--- On Sat, Mar 10, 2007 at 08:45:17PM +0300, Alexander Gerasiov wrote: Package: sshfs Version: 1.6-1+b1 Severity: grave It depends on non-existed package libfuse, but should depend on libfuse2, like version from testing or unstable. This bug was caused by broken shlibs in libfuse2, which has since been corrected. Fresh binNMUs have been scheduled for all reverse-dependencies of libfuse2, so you should find a fixed sshfs package in t-p-u soon. (Though I have no idea why you're pulling from t-p-u anyway. :) -- Steve Langasek Give me a lever long enough and a Free OS Debian Developer to set it on, and I can move the world. [EMAIL PROTECTED] http://www.debian.org/ ---End Message---
Bug#414470: dtc: saveConfig should not write in /root/
Package: dtc Severity: serious Justification: Policy 10.7 Not to mention that /root do not necessarily exists ... -- System Information: Debian Release: 4.0 APT prefers unstable APT policy: (990, 'unstable'), (500, 'testing'), (1, 'experimental') Architecture: amd64 (x86_64) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.20 Locale: LANG=C, LC_CTYPE=fr_FR.utf8 (charmap=UTF-8) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#405704: marked as done (imapproxy: fails to start - breaks install/upgrade)
Your message dated Mon, 12 Mar 2007 01:02:04 + with message-id [EMAIL PROTECTED] and subject line Bug#405704: fixed in up-imapproxy 1.2.4-8 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.) Debian bug tracking system administrator (administrator, Debian Bugs database) ---BeginMessage--- Package: imapproxy Version: 1.2.4-7 Severity: normal I was running 1.2.4-5 and had upgrade problems when trying to move to 1.2.4-6 which is what is available for the testing branch. I had an issue performing the upgrade -- because the imapproxy could stop (even though it was already stopped) -- I saw there were some bug reports on this issue regarding the init script, so I modified that to allow dpkg to upgrade the packaging and when prompted if I would like to overwrite my (customized) version of the init.d/imapproxy script with the Default package-maintainer's version, I selected yes. Since I still received the following error with 1.2.4-6 I saw there was -7 available in unstable. I proceeded to install 1.2.4-7 and still have the same issue: Setting up imapproxy (1.2.4-7) ... Starting IMAP proxy: grep: /proc/26035/cmdline: No such file or directory -- System Information: Debian Release: 4.0 Failed to start imapproxy. Check logs for details. APT prefers testing invoke-rc.d: initscript imapproxy, action start failed. APT policy: (500, 'testing') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.17-2-k7 Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968) Any Ideas? Versions of packages imapproxy depends on: ii debconf [debconf-2.0]1.5.11 Debian configuration management sy ii libc62.3.6.ds1-8 GNU C Library: Shared libraries ii libncurses5 5.5-5 Shared libraries for terminal hand ii libssl0.9.8 0.9.8c-4SSL shared libraries ii libwrap0 7.6.dbs-11 Wietse Venema's TCP wrappers libra ii lsb-base 3.1-22 Linux Standard Base 3.1 init scrip imapproxy recommends no packages. -- debconf information: * imapproxy/imap-server: localhost ---End Message--- ---BeginMessage--- Source: up-imapproxy Source-Version: 1.2.4-8 We believe that the bug you reported is fixed in the latest version of up-imapproxy, which is due to be installed in the Debian FTP archive: imapproxy_1.2.4-8_i386.deb to pool/main/u/up-imapproxy/imapproxy_1.2.4-8_i386.deb up-imapproxy_1.2.4-8.diff.gz to pool/main/u/up-imapproxy/up-imapproxy_1.2.4-8.diff.gz up-imapproxy_1.2.4-8.dsc to pool/main/u/up-imapproxy/up-imapproxy_1.2.4-8.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. Jose Luis Tallon [EMAIL PROTECTED] (supplier of updated up-imapproxy 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: Sat, 10 Mar 2007 21:59:37 +0100 Source: up-imapproxy Binary: imapproxy Architecture: source i386 Version: 1.2.4-8 Distribution: unstable Urgency: high Maintainer: Jose Luis Tallon [EMAIL PROTECTED] Changed-By: Jose Luis Tallon [EMAIL PROTECTED] Description: imapproxy - IMAP protocol proxy Closes: 352999 369020 405704 409861 412221 Changes: up-imapproxy (1.2.4-8) unstable; urgency=high . * Fixed crash on startup when IMAP server is not available (Closes: #405704) . * Security: backported possible DoS fix from 1.2.5rc2 (Closes: #409861) . * Enhance security: enable chroot by default (Closes: #352999) (Patch provided by Kees Cook [EMAIL PROTECTED]) . * Build process: fixed using files from current autotools-dev . * Made initscript a bit more intelligent, so that it won't fail so easily when imapproxyd is slower to start than expected (Closes: #369020) . * Localization - Updated DE translation (Closes: #412221) Files: 799d1ea0450b74da3e0e1fb8ac48fe54 671 mail optional up-imapproxy_1.2.4-8.dsc cbe938cc40ea584ccfd5e65b8c0c48ef 60135 mail optional up-imapproxy_1.2.4-8.diff.gz 125e6fa637b0551d401657c0c34c7283 53674 mail optional imapproxy_1.2.4-8_i386.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.6 (GNU/Linux) iD8DBQFF9KNzKN6ufymYLloRAiSAAKDRn+4HyF2SlLoVHkf5QyVHSYed6wCguaKH
Bug#414481: dtc-xen: creates files/directories in /home
Package: dtc-xen Version: 0.2.6-5 Severity: serious Hi, dtc-xen's postinst creates (19!!) users with home directories under /home, and will break if /home is on nfs (which is a pretty common setup). If the users already exist (not necessarily created by this package), it will override their settings. Cheers, Julien signature.asc Description: Digital signature
Bug#414482: dtc-xen: insecure file creation in postinst
Package: dtc-xen Version: 0.2.6-5 Severity: serious Tags: security Hi, dtc-xen creates files in /etc/dtc-xen in its postinst, in particular ssl private keys, and only after that chmods them. This means that they is a race condition which makes these files readable by anyone. Cheers, Julien signature.asc Description: Digital signature
Bug#414484: dtc/conf_mysql_change_root is a debconf abuse
Package: dtc Severity: serious Justification: Policy 3.9 This question is: * modifying another package configuration which is completely against the policy * doing a warning that mysql-server is already doing, hence making it twice. this is abuse. -- System Information: Debian Release: 4.0 APT prefers unstable APT policy: (990, 'unstable'), (500, 'testing'), (1, 'experimental') Architecture: amd64 (x86_64) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.20 Locale: LANG=C, LC_CTYPE=fr_FR.utf8 (charmap=UTF-8) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#414478: dtc: ETOOMUCHCRACK quote
Package: dtc Severity: grave Justification: renders package unusable in the debian_config script you can find oddities like: if [ $conf_use_nated_vhosts = true -o $conf_use_nated_vhosts = yes ] ; then or if [ $RET = true -o $RET = yes ] ; then Please learn proper quoting in sh scripting. sh(1) could be a good start. -- System Information: Debian Release: 4.0 APT prefers unstable APT policy: (990, 'unstable'), (500, 'testing'), (1, 'experimental') Architecture: amd64 (x86_64) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.20 Locale: LANG=C, LC_CTYPE=fr_FR.utf8 (charmap=UTF-8) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Processed: Re: dtc: ETOOMUCHCRACK quote
Processing commands for [EMAIL PROTECTED]: severity 414478 normal Bug#414478: dtc: ETOOMUCHCRACK quote Severity set to `normal' from `grave' thanks Stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#414478: dtc: ETOOMUCHCRACK quote
severity 414478 normal thanks On Mon, Mar 12, 2007 at 12:49:25AM +0100, Pierre Habouzit wrote: Package: dtc Severity: grave Justification: renders package unusable in the debian_config script you can find oddities like: if [ $conf_use_nated_vhosts = true -o $conf_use_nated_vhosts = yes ] ; then or if [ $RET = true -o $RET = yes ] ; then Please learn proper quoting in sh scripting. sh(1) could be a good start. Ok, I read too fast here, and was confused. The code is correct, it's just _so_ unusual that I first thought it was a bug. please rather use $foo than $foo or $foo it's _really_ hard to read, and do remember code is written to be read too ;) TIA. -- ·O· Pierre Habouzit ··O[EMAIL PROTECTED] OOOhttp://www.madism.org pgpuRnqtK4Lpi.pgp Description: PGP signature
Processed: Re: Bug#414478: dtc: ETOOMUCHCRACK quote
Processing commands for [EMAIL PROTECTED]: severity 414478 grave Bug#414478: dtc: ETOOMUCHCRACK quote Severity set to `grave' from `normal' thanks Stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Processed: Re: openbsd-inetd, action start failed when upgrading
Processing commands for [EMAIL PROTECTED]: clone 386469 -1 Bug#386469: openbsd-inetd, action start failed when upgrading Bug 386469 cloned as bug 414485. tags -1 =patch Bug#414485: openbsd-inetd, action start failed when upgrading Tags were: help Tags set to: patch reassign -1 update-inetd Bug#414485: openbsd-inetd, action start failed when upgrading Bug reassigned from package `openbsd-inetd' to `update-inetd'. retitle -1 update-inetd: no reason to restart inetd on service removal Bug#414485: openbsd-inetd, action start failed when upgrading Changed Bug title. severity -1 important Bug#414485: update-inetd: no reason to restart inetd on service removal Severity set to `important' from `serious' thanks Stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#386469: openbsd-inetd, action start failed when upgrading
clone 386469 -1
tags -1 =patch
reassign -1 update-inetd
retitle -1 update-inetd: no reason to restart inetd on service removal
severity -1 important
thanks
Discussing with Marco on IRC, it seems he's reluctant to have inetd running
when no services are configured, but it's clear in any case that
update-inted doesn't need to restart inetd on service removal/deactivation:
a force-reload is always sufficient, because either inetd is running and a
reload does what's expected, or inetd isn't running and there's no reason to
start it.
So attached is a patch that changes this aspect of update-inetd's behavior.
It doesn't completely resolve the issues described here (as noted, the
problem can occur on package configuration, just not on package removal),
but is nevertheless correct in its own right.
NMU on its way shortly to incoming with this change, per Marco's standing
NMU policy for this package.
--
Steve Langasek Give me a lever long enough and a Free OS
Debian Developer to set it on, and I can move the world.
[EMAIL PROTECTED] http://www.debian.org/
diff -Nru /tmp/kPrNSDnFv0/update-inetd-4.27/debian/changelog /tmp/Oys7lzOfbb/update-inetd-4.27/debian/changelog
--- /tmp/kPrNSDnFv0/update-inetd-4.27/debian/changelog 2007-02-21 15:16:12.0 -0800
+++ /tmp/Oys7lzOfbb/update-inetd-4.27/debian/changelog 2007-03-11 18:09:39.0 -0700
@@ -1,3 +1,13 @@
+update-inetd (4.27-0.5) unstable; urgency=low
+
+ * Non-maintainer upload.
+ * When called with --disable or --remove, call invoke-rc.d $inetd
+force-reload instead of restart -- if inetd isn't running, there's no
+reason that we should be restarting it in the process of *removing*
+services from inetd.conf.
+
+ -- Steve Langasek [EMAIL PROTECTED] Sun, 11 Mar 2007 17:52:56 -0700
+
update-inetd (4.27-0.4) unstable; urgency=high
* Non-maintainer upload.
diff -Nru /tmp/kPrNSDnFv0/update-inetd-4.27/DebianNet.pm /tmp/Oys7lzOfbb/update-inetd-4.27/DebianNet.pm
--- /tmp/kPrNSDnFv0/update-inetd-4.27/DebianNet.pm 2007-02-21 15:16:30.0 -0800
+++ /tmp/Oys7lzOfbb/update-inetd-4.27/DebianNet.pm 2007-03-11 18:42:30.0 -0700
@@ -153,7 +153,7 @@
die Error installing new $inetdcf: $!\n;
chmod(0644, $inetdcf);
-wakeup_inetd;
+wakeup_inetd(1);
return(1);
}
@@ -192,7 +192,7 @@
die Error installing new $inetdcf: $!\n;
chmod(0644, $inetdcf);
-wakeup_inetd;
+wakeup_inetd(1);
return(1);
}
@@ -222,7 +222,16 @@
}
sub wakeup_inetd {
+my($removal) = @_;
my($pid);
+my($action);
+
+if ($removal) {
+$action = 'force-reload';
+} else {
+$action = 'restart';
+}
+
if (open(P,/var/run/inetd.pid)) {
$pid=P;
if (open(C,sprintf(/proc/%d/stat,$pid))) {
@@ -235,7 +244,7 @@
$_ = glob /etc/init.d/*inetd;
if (m/\/etc\/init\.d\/(.*inetd)/) {
my $service = $1;
-system(invoke-rc.d $service restart /dev/null);
+system(invoke-rc.d $service $action /dev/null);
}
}
return(1);
Bug#414402: marked as done (srcinst: FTBFS in Etch: build-depends on libghc6-hslogger-dev)
Your message dated Sun, 11 Mar 2007 19:01:05 -0700 with message-id [EMAIL PROTECTED] and subject line Bug#414401: arch2darcs: FTBFS in Etch: build-depends on libghc6-hslogger-dev 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.) Debian bug tracking system administrator (administrator, Debian Bugs database) ---BeginMessage--- Package: srcinst Version: 0.8.7 Severity: serious Tags: etch This package fails to build in Etch (but not in Sid) due to libghc6-hslogger-dev not being available in Etch. On Mon, Mar 05, 2007 at 03:00:06PM +0100, [EMAIL PROTECTED] wrote: Automatic build of srcinst_0.8.7 on qa by sbuild/amd64 85 Build started at 20070305-1459 ** Checking available source versions... Fetching source files... Reading package lists... Building dependency tree... Need to get 14.5kB of source archives. Get:1 http://debian.aurel32.net etch/main srcinst 0.8.7 (dsc) [605B] Get:2 http://debian.aurel32.net etch/main srcinst 0.8.7 (tar) [13.9kB] Fetched 14.5kB in 0s (97.7kB/s) Download complete and in download only mode ** Using build dependencies supplied by package: Build-Depends: debhelper (= 4.0.0), ghc6 (= 6.4.2), libghc6-missingh-dev (= 0.18.0), libghc6-network-dev, libghc6-unix-dev, libghc6-hslogger-dev Checking for already installed source dependencies... debhelper: missing Using default version 5.0.42 ghc6: missing Using default version 6.6-3 libghc6-missingh-dev: missing Default version of libghc6-missingh-dev not sufficient, no suitable version found. Skipping for now, maybe there are alternatives. libghc6-network-dev: missing libghc6-unix-dev: missing libghc6-hslogger-dev: missing Checking for source dependency conflicts... /usr/bin/sudo /usr/bin/apt-get --purge $CHROOT_OPTIONS -q -y install debhelper ghc6 libghc6-missingh-dev libghc6-network-dev libghc6-unix-dev libghc6-hslogger-dev Reading package lists... Building dependency tree... E: Couldn't find package libghc6-hslogger-dev Note, selecting ghc6 instead of libghc6-unix-dev apt-get failed. Package installation failed Trying to reinstall removed packages: Trying to uninstall newly installed packages: Source-dependencies not satisfied; skipping srcinst ** Finished at 20070305-1500 Build needed 00:05:17, 0k disk space ---End Message--- ---BeginMessage--- On Sun, Mar 11, 2007 at 04:39:57PM +0100, Aurelien Jarno wrote: Package: arch2darcs Version: 1.0.9 Severity: serious Tags: etch This package fails to build in Etch (but not in Sid) due to libghc6-hslogger-dev not being available in Etch. On Sun, Mar 11, 2007 at 04:44:47PM +0100, Aurelien Jarno wrote: Package: srcinst Version: 0.8.7 Severity: serious Tags: etch This package fails to build in Etch (but not in Sid) due to libghc6-hslogger-dev not being available in Etch. Hmm, I'm at a loss to explain how this happened. But it appears that hslogger, the missing build-dep, is itself buildable in etch and has no other RC bugs that would prohibit its inclusion, so I've unblocked it; these packages should be buildable in etch with the next britney run and mirror pulse. Thanks, -- Steve Langasek Give me a lever long enough and a Free OS Debian Developer to set it on, and I can move the world. [EMAIL PROTECTED] http://www.debian.org/ ---End Message---
Bug#405704: closed by Jose Luis Tallon [EMAIL PROTECTED] (Bug#405704: fixed in up-imapproxy 1.2.4-8)
Please don't close this bug until the actual fix is available... I can't find it in the pool yet -- and it's still broken on my system. Debian Bug Tracking System wrote: This is an automatic notification regarding your Bug report #405704: imapproxy: fails to start - breaks install/upgrade, which was filed against the imapproxy package. It has been closed by Jose Luis Tallon [EMAIL PROTECTED]. Their explanation is attached below. If this explanation is unsatisfactory and you have not received a better one in a separate message then please contact Jose Luis Tallon [EMAIL PROTECTED] by replying to this email. Debian bug tracking system administrator (administrator, Debian Bugs database) Subject: Bug#405704: fixed in up-imapproxy 1.2.4-8 From: Jose Luis Tallon [EMAIL PROTECTED] Date: Mon, 12 Mar 2007 01:02:04 + To: [EMAIL PROTECTED] To: [EMAIL PROTECTED] Source: up-imapproxy Source-Version: 1.2.4-8 We believe that the bug you reported is fixed in the latest version of up-imapproxy, which is due to be installed in the Debian FTP archive: imapproxy_1.2.4-8_i386.deb to pool/main/u/up-imapproxy/imapproxy_1.2.4-8_i386.deb up-imapproxy_1.2.4-8.diff.gz to pool/main/u/up-imapproxy/up-imapproxy_1.2.4-8.diff.gz up-imapproxy_1.2.4-8.dsc to pool/main/u/up-imapproxy/up-imapproxy_1.2.4-8.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. Jose Luis Tallon [EMAIL PROTECTED] (supplier of updated up-imapproxy 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: Sat, 10 Mar 2007 21:59:37 +0100 Source: up-imapproxy Binary: imapproxy Architecture: source i386 Version: 1.2.4-8 Distribution: unstable Urgency: high Maintainer: Jose Luis Tallon [EMAIL PROTECTED] Changed-By: Jose Luis Tallon [EMAIL PROTECTED] Description: imapproxy - IMAP protocol proxy Closes: 352999 369020 405704 409861 412221 Changes: up-imapproxy (1.2.4-8) unstable; urgency=high . * Fixed crash on startup when IMAP server is not available (Closes: #405704) . * Security: backported possible DoS fix from 1.2.5rc2 (Closes: #409861) . * Enhance security: enable chroot by default (Closes: #352999) (Patch provided by Kees Cook [EMAIL PROTECTED]) . * Build process: fixed using files from current autotools-dev . * Made initscript a bit more intelligent, so that it won't fail so easily when imapproxyd is slower to start than expected (Closes: #369020) . * Localization - Updated DE translation (Closes: #412221) Files: 799d1ea0450b74da3e0e1fb8ac48fe54 671 mail optional up-imapproxy_1.2.4-8.dsc cbe938cc40ea584ccfd5e65b8c0c48ef 60135 mail optional up-imapproxy_1.2.4-8.diff.gz 125e6fa637b0551d401657c0c34c7283 53674 mail optional imapproxy_1.2.4-8_i386.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.6 (GNU/Linux) iD8DBQFF9KNzKN6ufymYLloRAiSAAKDRn+4HyF2SlLoVHkf5QyVHSYed6wCguaKH ydFMpPWOvsVzuN+YkfqFEGs= =QZPG -END PGP SIGNATURE- -- Ryan Sinn Photography Spring Lake Park, MN 1.763.783.5721 [EMAIL PROTECTED] http://ryansinnphotography.com/ Weddings, Portraits, Events, Anything!
Bug#414401: marked as done (arch2darcs: FTBFS in Etch: build-depends on libghc6-hslogger-dev)
Your message dated Sun, 11 Mar 2007 19:01:05 -0700 with message-id [EMAIL PROTECTED] and subject line Bug#414401: arch2darcs: FTBFS in Etch: build-depends on libghc6-hslogger-dev 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.) Debian bug tracking system administrator (administrator, Debian Bugs database) ---BeginMessage--- Package: arch2darcs Version: 1.0.9 Severity: serious Tags: etch This package fails to build in Etch (but not in Sid) due to libghc6-hslogger-dev not being available in Etch. On Mon, Mar 05, 2007 at 02:05:37PM +0100, [EMAIL PROTECTED] wrote: Automatic build of arch2darcs_1.0.9 on qa by sbuild/amd64 85 Build started at 20070305-1405 ** Checking available source versions... Fetching source files... Reading package lists... Building dependency tree... Need to get 15.2kB of source archives. Get:1 http://debian.aurel32.net etch/main arch2darcs 1.0.9 (dsc) [614B] Get:2 http://debian.aurel32.net etch/main arch2darcs 1.0.9 (tar) [14.6kB] Fetched 15.2kB in 0s (289kB/s) Download complete and in download only mode ** Using build dependencies supplied by package: Build-Depends: debhelper (= 4.0.0), ghc6 (= 6.4.2), libghc6-missingh-dev (= 0.18.0), libghc6-network-dev, libghc6-unix-dev, libghc6-hslogger-dev Checking for already installed source dependencies... debhelper: missing Using default version 5.0.42 ghc6: missing Using default version 6.6-3 libghc6-missingh-dev: missing Default version of libghc6-missingh-dev not sufficient, no suitable version found. Skipping for now, maybe there are alternatives. libghc6-network-dev: missing libghc6-unix-dev: missing libghc6-hslogger-dev: missing Checking for source dependency conflicts... /usr/bin/sudo /usr/bin/apt-get --purge $CHROOT_OPTIONS -q -y install debhelper ghc6 libghc6-missingh-dev libghc6-network-dev libghc6-unix-dev libghc6-hslogger-dev Reading package lists... Building dependency tree... E: Couldn't find package libghc6-hslogger-dev Note, selecting ghc6 instead of libghc6-unix-dev apt-get failed. Package installation failed Trying to reinstall removed packages: Trying to uninstall newly installed packages: Source-dependencies not satisfied; skipping arch2darcs ** Finished at 20070305-1405 Build needed 00:00:00, 0k disk space ---End Message--- ---BeginMessage--- On Sun, Mar 11, 2007 at 04:39:57PM +0100, Aurelien Jarno wrote: Package: arch2darcs Version: 1.0.9 Severity: serious Tags: etch This package fails to build in Etch (but not in Sid) due to libghc6-hslogger-dev not being available in Etch. On Sun, Mar 11, 2007 at 04:44:47PM +0100, Aurelien Jarno wrote: Package: srcinst Version: 0.8.7 Severity: serious Tags: etch This package fails to build in Etch (but not in Sid) due to libghc6-hslogger-dev not being available in Etch. Hmm, I'm at a loss to explain how this happened. But it appears that hslogger, the missing build-dep, is itself buildable in etch and has no other RC bugs that would prohibit its inclusion, so I've unblocked it; these packages should be buildable in etch with the next britney run and mirror pulse. Thanks, -- Steve Langasek Give me a lever long enough and a Free OS Debian Developer to set it on, and I can move the world. [EMAIL PROTECTED] http://www.debian.org/ ---End Message---
Bug#411472: move zope3 python modules to /usr/lib/zope3
Hello, In the meanwhile, adding a conflicts between python-zodb and zope3 is the quickest way to solve the issue. For lenny, we'll modularize the whole zope package as upstream is planning. So, who is adding this conflict? It looks like it's easier to add the conflict in python-zodb, which has matching versions in etch and sid right now (zope3 has a new upstream version in unstable that won't be considered for etch). Should this bug, or at least the RC aspect of it, be reassigned to python-zodb? Fabio, you seem to be the sole uploader of python-zodb; so I guess if you think the conflict is the right solution for etch, it's ok for someone to NMU this change as well if you don't have time for it? Thanks, -- Steve Langasek Give me a lever long enough and a Free OS Debian Developer to set it on, and I can move the world. [EMAIL PROTECTED] http://www.debian.org/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#412387: invoke-rc.d: unknown initscript, /etc/init.d/inetd not found.
Hi folks, Hmm, lots of proposed patches on this one. :) Well, upgrading directly from woody to etch is not supported, but it's possible for a user to have removed the woody version of the package without purging it, and then install the etch version, and perhaps that would trigger this code path. test, test yes, it does. So it's possible that even in a supported path, the user will have an uncommented apt-proxy entry in /etc/inetd.conf (because woody's apt-proxy only handles /etc/inetd.conf on purge), which ideally we will handle here to prevent having an active inetd.conf entry pointing at a program that's not prepared to handle it. Thus, since current update-inetd handles reloading of the inetd.conf already, and there is no reason to explicitly depend on update-inetd (if update-inetd is not installed, neither is inetd, so no upgrade handling is required), I think the best patch here is to just drop the extra call to invoke-rc.d. This patch is attached, and an NMU will be uploaded to incoming shortly. Thanks, -- Steve Langasek Give me a lever long enough and a Free OS Debian Developer to set it on, and I can move the world. [EMAIL PROTECTED] http://www.debian.org/ diff -Nru /tmp/gN2tJXgpK4/apt-proxy-1.9.35/debian/changelog /tmp/O1paL9cJ9P/apt-proxy-1.9.35/debian/changelog --- /tmp/gN2tJXgpK4/apt-proxy-1.9.35/debian/changelog 2007-01-27 06:52:58.0 -0800 +++ /tmp/O1paL9cJ9P/apt-proxy-1.9.35/debian/changelog 2007-03-11 20:00:20.0 -0700 @@ -1,3 +1,14 @@ +apt-proxy (1.9.35-0.3) unstable; urgency=high + + * Non-maintainer upload. + * High-urgency upload for RC bugfix. + * Don't invoke the inetd init script on upgrade from ancient versions, +update-inetd will already handle this for us. Thanks to Marco +Presi, Peter Green, Damyan Ivanov, and Ben Hutchings for their work +on figuring out this bug. Closes: #412387. + + -- Steve Langasek [EMAIL PROTECTED] Sun, 11 Mar 2007 19:58:12 -0700 + apt-proxy (1.9.35-0.2) unstable; urgency=low * Non-maintainer upload. diff -Nru /tmp/gN2tJXgpK4/apt-proxy-1.9.35/debian/postinst /tmp/O1paL9cJ9P/apt-proxy-1.9.35/debian/postinst --- /tmp/gN2tJXgpK4/apt-proxy-1.9.35/debian/postinst 2006-08-03 16:54:46.0 -0700 +++ /tmp/O1paL9cJ9P/apt-proxy-1.9.35/debian/postinst 2007-03-11 20:00:30.0 -0700 @@ -34,7 +34,6 @@ if [ -x /usr/sbin/update-inetd ]; then echo Disabling inetd's apt-proxy v1 line. update-inetd --comment-chars #apt-proxy-v2# --disable - invoke-rc.d inetd restart fi db_fset $NAME/upgrading-v2 seen false || true db_input medium $NAME/upgrading-v2 || true
Bug#412387: marked as done (invoke-rc.d: unknown initscript, /etc/init.d/inetd not found.)
Your message dated Mon, 12 Mar 2007 03:17:01 + with message-id [EMAIL PROTECTED] and subject line Bug#412387: fixed in apt-proxy 1.9.35-0.3 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.) Debian bug tracking system administrator (administrator, Debian Bugs database) ---BeginMessage--- Package: apt-proxy Version: 1.9.35-0.2 Severity: grave Justification: renders package unusable dpkg --configure -a: Setting up apt-proxy (1.9.35-0.2) ... Disabling inetd's apt-proxy v1 line. invoke-rc.d: unknown initscript, /etc/init.d/inetd not found. dpkg: error processing apt-proxy (--configure): subprocess post-installation script returned error exit status 100 Errors were encountered while processing: apt-proxy -- System Information: Debian Release: 4.0 APT prefers testing APT policy: (990, 'testing'), (99, 'unstable'), (9, 'experimental'), (1, 'stable') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.18-3-xen-k7 Locale: LANG=uk_UA.UTF-8, LC_CTYPE=uk_UA.UTF-8 (charmap=UTF-8) Versions of packages apt-proxy depends on: ii adduser 3.102 Add and remove users and groups ii bzip2 1.0.3-6high-quality block-sorting file co ii debconf [debconf-2.0] 1.5.11 Debian configuration management sy ii logrotate 3.7.1-3Log rotation utility ii python2.4.4-2An interactive high-level object-o ii python-apt0.6.20 Python interface to libapt-pkg ii python-central0.5.12 register and build utility for Pyt ii python-twisted-web0.6.0-1An HTTP protocol implementation to apt-proxy recommends no packages. -- debconf information: apt-proxy/upgrading-v2: apt-proxy/upgrading-v2-result: ---End Message--- ---BeginMessage--- Source: apt-proxy Source-Version: 1.9.35-0.3 We believe that the bug you reported is fixed in the latest version of apt-proxy, which is due to be installed in the Debian FTP archive: apt-proxy_1.9.35-0.3.dsc to pool/main/a/apt-proxy/apt-proxy_1.9.35-0.3.dsc apt-proxy_1.9.35-0.3.tar.gz to pool/main/a/apt-proxy/apt-proxy_1.9.35-0.3.tar.gz apt-proxy_1.9.35-0.3_all.deb to pool/main/a/apt-proxy/apt-proxy_1.9.35-0.3_all.deb 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. Steve Langasek [EMAIL PROTECTED] (supplier of updated apt-proxy 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: Sun, 11 Mar 2007 19:58:12 -0700 Source: apt-proxy Binary: apt-proxy Architecture: source all Version: 1.9.35-0.3 Distribution: unstable Urgency: high Maintainer: Chris Halls [EMAIL PROTECTED] Changed-By: Steve Langasek [EMAIL PROTECTED] Description: apt-proxy - Debian archive proxy and partial mirror builder Closes: 412387 Changes: apt-proxy (1.9.35-0.3) unstable; urgency=high . * Non-maintainer upload. * High-urgency upload for RC bugfix. * Don't invoke the inetd init script on upgrade from ancient versions, update-inetd will already handle this for us. Thanks to Marco Presi, Peter Green, Damyan Ivanov, and Ben Hutchings for their work on figuring out this bug. Closes: #412387. Files: b6f568c74579e450bede6fe411e549ba 734 admin extra apt-proxy_1.9.35-0.3.dsc 7283c2a81de2efbd63d8796fd178edf5 102918 admin extra apt-proxy_1.9.35-0.3.tar.gz aef2fd29b46a481caf261728de52ffa1 82288 admin extra apt-proxy_1.9.35-0.3_all.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.6 (GNU/Linux) iD8DBQFF9MKwKN6ufymYLloRAjA/AJ9oVAT4qv78/PL5acGaQxrDImvhzgCfRhaK cJL30D/A+gTx8JzJkoBxsP8= =EOLP -END PGP SIGNATURE- ---End Message---
Bug#414470: dtc: saveConfig should not write in /root/
Pierre Habouzit wrote: Package: dtc Severity: serious Justification: Policy 10.7 Not to mention that /root do not necessarily exists ... It does NOT do that anymore already in the uploaded version, in fact it saves in /var/lib/dtc as it has been recommended to me by some people in IRC. Maybe it's only the message that is remaining, but I don't think that the case. If that (false) message is still there, this is not the case already in our CVS version. I'll mark this one as done. Thomas -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#413534: Another 64bit problem (binding SQL_C_SLONG values)
Enrico, On Sun, Mar 11, 2007 at 07:30:04PM +, Enrico Zini wrote: http://msdn2.microsoft.com/en-us/library/ms714556.aspx says that SQL_C_SLONG represents a long int. Microsoft's docs are totally useless for correctly implementing ODBC on 64-bit architectures. Please explain the /problem/ you're trying to solve, preferably with a reproducible use case. -- Steve Langasek Give me a lever long enough and a Free OS Debian Developer to set it on, and I can move the world. [EMAIL PROTECTED] http://www.debian.org/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#413116: jamvm: missing file: /usr/lib/logging.properties
Version: 2:0.92-4
FWIW, Nicolas has given a very good analysis of this bug, but his mail was
only sent to control@, not to the bug itself.
Here is his mail:
Hello,
Thanks Michel and Matthew for your answers.
I'm reassigning this bug to classpath. It is fixed upstream in classpath
0.92.
I could reproduce it with classpath 0.91-3, and confirm it's fixed on
0.92-4.
Please find attached a minimal patch to fix this issue (taken from
upstream).
classpath's maintainer, jamvm seems to be unusable in some conditions
because of this bug. It could be worth sending this patch to t-p-u.
King Regards,
--
Nekral
Since the bug is fixed in 2:0.92-4, I'm marking it as such with this
message. I have also re-attached his patch, so that it's clearly visible in
the bug log.
Maintainers, do you agree that this patch is a correct fix for the problem?
Since the new upstream version of classpath in unstable doesn't look
suitable for a freeze exception, can one of you upload this fix to
testing-proposed-updates, or should I prepare an NMU?
Thanks,
--
Steve Langasek Give me a lever long enough and a Free OS
Debian Developer to set it on, and I can move the world.
[EMAIL PROTECTED] http://www.debian.org/
diff -rauN ../orig/classpath-0.91/debian/changelog ./classpath-0.91/debian/changelog
--- ../orig/classpath-0.91/debian/changelog 2007-03-11 22:46:44.0 +0100
+++ ./classpath-0.91/debian/changelog 2007-03-11 23:00:46.0 +0100
@@ -1,3 +1,11 @@
+classpath (2:0.91-3.1) unstable; urgency=low
+
+ * Merge change from upstream
+java/util/logging/LogManager.java (getLevelProperty): Check whether value
+is null before passing to Level.parse(). Closes: #413116
+
+ -- Nicolas FRANCOIS (Nekral) [EMAIL PROTECTED] Sun, 11 Mar 2007 22:59:22 +0100
+
classpath (2:0.91-3) unstable; urgency=low
* Install header files to /usr/include/classpath.
diff -rauN ../orig/classpath-0.91/java/util/logging/LogManager.java ./classpath-0.91/java/util/logging/LogManager.java
--- ../orig/classpath-0.91/java/util/logging/LogManager.java 2006-04-03 10:59:53.0 +0200
+++ ./classpath-0.91/java/util/logging/LogManager.java 2007-03-12 00:39:33.0 +0100
@@ -700,7 +700,11 @@
{
try
{
- return Level.parse(getLogManager().getProperty(propertyName));
+ String value = getLogManager().getProperty(propertyName);
+ if (value != null)
+ return Level.parse(getLogManager().getProperty(propertyName));
+ else
+ return defaultValue;
}
catch (Exception ex)
{
Bug#413116: marked as done (jamvm: missing file: /usr/lib/logging.properties)
Your message dated Sun, 11 Mar 2007 21:01:41 -0700
with message-id [EMAIL PROTECTED]
and subject line jamvm: missing file: /usr/lib/logging.properties
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.)
Debian bug tracking system administrator
(administrator, Debian Bugs database)
---BeginMessage---
Package: jamvm
Version: 1.4.4-1
Severity: grave
Justification: renders package unusable
JamVM fails to start:
$ jamvm -jar /path/to/my/app.jar
Exception occurred while VM initialising.
java/io/FileNotFoundException: No such file or directory:
/usr/lib/logging.properties
furthermore, when creating the missing file a NullPointerException
occurs:
$ sudo touch /usr/lib/logging.properties
$ jamvm -jar /path/to/my/app.jar
Exception occurred while VM initialising.
java/lang/NullPointerException
-- System Information:
Debian Release: 4.0
APT prefers testing
APT policy: (500, 'testing')
Architecture: i386 (i686)
Shell: /bin/sh linked to /bin/bash
Kernel: Linux 2.6.18-3-686
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Versions of packages jamvm depends on:
ii classpath 2:0.91-3 clean room standard Java libraries
ii classpath-common2:0.91-3 architecture independent files
ii java-common 0.25 Base of all Java packages
ii libc6 2.3.6.ds1-11 GNU C Library: Shared libraries
ii zlib1g 1:1.2.3-13 compression library - runtime
jamvm recommends no packages.
-- no debconf information
---End Message---
---BeginMessage---
Version: 2:0.92-4
FWIW, Nicolas has given a very good analysis of this bug, but his mail was
only sent to control@, not to the bug itself.
Here is his mail:
Hello,
Thanks Michel and Matthew for your answers.
I'm reassigning this bug to classpath. It is fixed upstream in classpath
0.92.
I could reproduce it with classpath 0.91-3, and confirm it's fixed on
0.92-4.
Please find attached a minimal patch to fix this issue (taken from
upstream).
classpath's maintainer, jamvm seems to be unusable in some conditions
because of this bug. It could be worth sending this patch to t-p-u.
King Regards,
--
Nekral
Since the bug is fixed in 2:0.92-4, I'm marking it as such with this
message. I have also re-attached his patch, so that it's clearly visible in
the bug log.
Maintainers, do you agree that this patch is a correct fix for the problem?
Since the new upstream version of classpath in unstable doesn't look
suitable for a freeze exception, can one of you upload this fix to
testing-proposed-updates, or should I prepare an NMU?
Thanks,
--
Steve Langasek Give me a lever long enough and a Free OS
Debian Developer to set it on, and I can move the world.
[EMAIL PROTECTED] http://www.debian.org/
diff -rauN ../orig/classpath-0.91/debian/changelog ./classpath-0.91/debian/changelog
--- ../orig/classpath-0.91/debian/changelog 2007-03-11 22:46:44.0 +0100
+++ ./classpath-0.91/debian/changelog 2007-03-11 23:00:46.0 +0100
@@ -1,3 +1,11 @@
+classpath (2:0.91-3.1) unstable; urgency=low
+
+ * Merge change from upstream
+java/util/logging/LogManager.java (getLevelProperty): Check whether value
+is null before passing to Level.parse(). Closes: #413116
+
+ -- Nicolas FRANCOIS (Nekral) [EMAIL PROTECTED] Sun, 11 Mar 2007 22:59:22 +0100
+
classpath (2:0.91-3) unstable; urgency=low
* Install header files to /usr/include/classpath.
diff -rauN ../orig/classpath-0.91/java/util/logging/LogManager.java ./classpath-0.91/java/util/logging/LogManager.java
--- ../orig/classpath-0.91/java/util/logging/LogManager.java 2006-04-03 10:59:53.0 +0200
+++ ./classpath-0.91/java/util/logging/LogManager.java 2007-03-12 00:39:33.0 +0100
@@ -700,7 +700,11 @@
{
try
{
- return Level.parse(getLogManager().getProperty(propertyName));
+ String value = getLogManager().getProperty(propertyName);
+ if (value != null)
+ return Level.parse(getLogManager().getProperty(propertyName));
+ else
+ return defaultValue;
}
catch (Exception ex)
{
---End Message---
Bug#414484: dtc/conf_mysql_change_root is a debconf abuse
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Pierre Habouzit wrote: Package: dtc Severity: serious Justification: Policy 3.9 This question is: * modifying another package configuration which is completely against the policy * doing a warning that mysql-server is already doing, hence making it twice. this is abuse. This was to be done ONLY in Sarge when this is NOT available (as it was REALLY a time saver thing). You have for sure notice the check of the /etc/debian_version (as you told me it was wrong too). Do you have a solution so I can keep asking this when running Sarge? I'd be very happy to do it the correct way. Thomas -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.1 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFF9Nm3l4M9yZjvmkkRAl1QAJ40RJ+Q9SaHNgj1aKKNreA03u8BNACg8dog 6FOhXNoDJqE6W3/1QEYdaHY= =k5YC -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#414478: dtc: ETOOMUCHCRACK quote
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Pierre Habouzit wrote: Package: dtc Severity: grave Justification: renders package unusable in the debian_config script you can find oddities like: if [ $conf_use_nated_vhosts = true -o $conf_use_nated_vhosts = yes ] ; then or if [ $RET = true -o $RET = yes ] ; then Please learn proper quoting in sh scripting. sh(1) could be a good start. The goal was NOT to quote in this case, but to have the script work if the variable is empty. This does what it was meant to do. After knowing that, do you still think it's wrong? I'll change these anyway, just to make it more standard and not shocking to any eyes, but that wont make the script any better to me. Thomas -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.1 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFF9Nqxl4M9yZjvmkkRAm+uAJ9YPUAntbDeT7wwLFK5U9xBkSRUNQCgrUiC FaRzOFhW6TEX9ZzW0/xSkJE= =pCBA -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#414478: dtc: ETOOMUCHCRACK quote
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Pierre HABOUZIT wrote: severity 414478 grave thanks On Mon, Mar 12, 2007 at 12:49:25AM +0100, Pierre Habouzit wrote: Package: dtc Severity: grave Justification: renders package unusable in the debian_config script you can find oddities like: if [ $conf_use_nated_vhosts = true -o $conf_use_nated_vhosts = yes ] ; then or if [ $RET = true -o $RET = yes ] ; then Please learn proper quoting in sh scripting. sh(1) could be a good start. Ok, I read too fast here, and was confused. The code is correct, it's just _so_ unusual that I first thought it was a bug. please rather use $foo than $foo or $foo it's _really_ hard to read, and do remember code is written to be read too ;) I'm on crack, I remember why it does not works: $foo is not the same as $foo if $foo as spaces in it. Here you take variables from debconf, and it's possible that the user put spaces in it, for many of the cases. Hence $foo will fail miserably with some unable to find `bar'-like messages. it make the installation fail, hence it's RC. Please do fix your quoting. Also consider that you sometimes forget to quote some tests and if $foo is empty [ $foo -eq 2 ] will fail as well because [ will miss an argument before -eq. re-raising accordingly. You can de-raise then, because if you have a variable that has ONLY the value of true or false, then there is no problem. You can see that I'm doing it only in a boolean. Anyway, I'm changing it, as you wont be the only one to say it's unusual... :) Thomas -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.1 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFF9Ntvl4M9yZjvmkkRArtHAKDIdlJZS2V/OajimPUqnvzcgM+EnQCfe5HS RN+szsXhiia6tVl1Q/YB7mA= =Gilw -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Processed: reassign 404148 to linux-2.6
Processing commands for [EMAIL PROTECTED]: # Automatically generated email from bts, devscripts version 2.9.27 # get this bug where it can be seen reassign 404148 linux-2.6 Bug#404148: kernel: data corruption with nvidia chipsets and IDE/SATA drives // memory hole mapping related bug?! Bug reassigned from package `kernel' to `linux-2.6'. End of message, stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#414478: dtc: ETOOMUCHCRACK quote
On Mon, Mar 12, 2007 at 12:44:35PM +0800, Thomas Goirand wrote: Pierre Habouzit wrote: Package: dtc Severity: grave Justification: renders package unusable in the debian_config script you can find oddities like: if [ $conf_use_nated_vhosts = true -o $conf_use_nated_vhosts = yes ] ; then or if [ $RET = true -o $RET = yes ] ; then Please learn proper quoting in sh scripting. sh(1) could be a good start. The goal was NOT to quote in this case, but to have the script work if the variable is empty. This does what it was meant to do. After knowing that, do you still think it's wrong? It's wrong if there's any chance that any of these variables will contain values with embedded spaces. -- Steve Langasek Give me a lever long enough and a Free OS Debian Developer to set it on, and I can move the world. [EMAIL PROTECTED] http://www.debian.org/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#411472: move zope3 python modules to /usr/lib/zope3
reassign 411472 python-zodb thanks * 2007-03-12 03:29, Steve Langasek wrote: So, who is adding this conflict? It looks like it's easier to add the conflict in python-zodb, which has matching versions in etch and sid right now (zope3 has a new upstream version in unstable that won't be considered for etch). Should this bug, or at least the RC aspect of it, be reassigned to python-zodb? Hi Steve, you are right. Fabio, you seem to be the sole uploader of python-zodb; so I guess if you think the conflict is the right solution for etch, it's ok for someone to NMU this change as well if you don't have time for it? I'm uploading the fix. Sorry for the delay, but I travelled back to home the last week and quite busy at work. Cheers, -- Fabio Tranchitella http://www.kobold.it Free Software Developer and Consultant http://www.tranchitella.it _ 1024D/7F961564, fpr 5465 6E69 E559 6466 BF3D 9F01 2BF8 EE2B 7F96 1564 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Processed: Re: Bug#411472: move zope3 python modules to /usr/lib/zope3
Processing commands for [EMAIL PROTECTED]: reassign 411472 python-zodb Bug#411472: move zope3 python modules to /usr/lib/zope3 Bug reassigned from package `zope3' to `python-zodb'. thanks Stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#414481: dtc-xen: creates files/directories in /home
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Julien Cristau wrote: Package: dtc-xen Version: 0.2.6-5 Severity: serious Hi, dtc-xen's postinst creates (19!!) users with home directories under /home, and will break if /home is on nfs (which is a pretty common setup). If the users already exist (not necessarily created by this package), it will override their settings. Cheers, Julien Hi! Thanks for reporting this one. Even if what you say is right, when using this package, in no way you want to use things like NFS, setup some users to have account on the server or other things like that. This is supposed to be the dom0 where the minimum number of things are setup, especially dangerous things like NFS !!! I think using /home on a NFS server in the dom0 of a Xen server is a pretty UNCOMMON and DANGEROUS setup... :) Did you understand that if the shell of the user is NOT /bin/dtc-xen_userconsole (the virtual machine console), then this is a very important security concern as the user will have a user account on the server rather than an access to the physical console of it's virtual machine? What do you suggest? Do you still think this should be filed as a bug, and if so, what correction do you think I should do (keep in mind that these users are needed)? Finally, can't we expect the user to know what he is doing, and expect that nothing else that dtc-xen and it's dependencies will be installed on the dom0 if it's a production server? I'm waiting for your reply before trying to fix this one. Thomas -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.1 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFF9PLAl4M9yZjvmkkRAvdtAJ9W7GDF8d7i8x2c6nxvDmhffZmpcgCcD4oB +LjpkXZUuQZ6AAXyKZ6tNOo= =ep4u -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#414482: dtc-xen: insecure file creation in postinst
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Julien Cristau wrote: Package: dtc-xen Version: 0.2.6-5 Severity: serious Tags: security Hi, dtc-xen creates files in /etc/dtc-xen in its postinst, in particular ssl private keys, and only after that chmods them. This means that they is a race condition which makes these files readable by anyone. Cheers, Julien Should I provide these files already with chmod in the package itself? Having them in the package in /etc wouldn't mater, as they would be set as conffiles, but it could be still problematic, no? What is your suggestion? Let me know. Thanks again for the report. Thomas -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.1 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFF9PVIl4M9yZjvmkkRAsUdAJ9nc/joG7yJfg9BEwdXiC0ABMVrywCfX818 njJH57it8HVETGCyXyBRyBU= =ejoO -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
