Processed: setting package to ekiga gnomemeeting, tagging 414069
Processing commands for [EMAIL PROTECTED]: # Automatically generated email from bts, devscripts version 2.9.27 package ekiga gnomemeeting Ignoring bugs not assigned to: gnomemeeting ekiga tags 414069 + pending Bug#414069: CVE-2007-0999: still vulnerable to format string exploits Tags were: patch security Tags added: pending 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#414069: marked as done (CVE-2007-0999: still vulnerable to format string exploits)
Your message dated Sat, 10 Mar 2007 08:47:05 +
with message-id [EMAIL PROTECTED]
and subject line Bug#414069: fixed in ekiga 2.0.3-5
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: ekiga
Version: 2.0.3-4
Severity: grave
Tags: patch, security
Hello! Unfortunately, it seems the upstream changes for CVE-2007-1006
weren't sufficient to solve the problems. Upstream is preparing 2.0.6
to be released[1], but in the meantime, I've attached the patch I'm
using in Ubuntu for 2.0.3.
[1] http://bugzilla.gnome.org/show_bug.cgi?id=415526
--
Kees Cook@outflux.net
#! /bin/sh /usr/share/dpatch/dpatch-run
## 51_fix-format-strings.dpatch by Kees Cook [EMAIL PROTECTED]
##
## All lines beginning with `## DP:' are a description of the patch.
## DP: No description.
@DPATCH@
diff -urNad ekiga-2.0.3~/lib/gui/gmdialog.h ekiga-2.0.3/lib/gui/gmdialog.h
--- ekiga-2.0.3~/lib/gui/gmdialog.h 2006-03-12 07:46:42.0 -0800
+++ ekiga-2.0.3/lib/gui/gmdialog.h 2007-03-08 17:00:30.144521663 -0800
@@ -127,7 +127,7 @@
const char *,
const char *,
const char *,
- ...);
+ ...) G_GNUC_PRINTF(4,5);
/**
@@ -140,7 +140,7 @@
GtkWidget *gnomemeeting_error_dialog (GtkWindow *parent,
const char *,
const char *format,
- ...);
+ ...) G_GNUC_PRINTF(3,4);
/**
@@ -153,7 +153,7 @@
GtkWidget *gnomemeeting_warning_dialog (GtkWindow *parent,
const char *,
const char *format,
- ...);
+ ...) G_GNUC_PRINTF(3,4);
/**
@@ -166,7 +166,7 @@
GtkWidget *gnomemeeting_message_dialog (GtkWindow *parent,
const char *,
const char *format,
- ...);
+ ...) G_GNUC_PRINTF(3,4);
/**
@@ -179,7 +179,7 @@
GtkWidget *gnomemeeting_progress_dialog (GtkWindow *parent,
const char *,
const char *format,
-...);
+...) G_GNUC_PRINTF(3,4);
G_END_DECLS
diff -urNad ekiga-2.0.3~/lib/gui/gmstatusbar.c ekiga-2.0.3/lib/gui/gmstatusbar.c
--- ekiga-2.0.3~/lib/gui/gmstatusbar.c 2006-03-12 07:46:42.0 -0800
+++ ekiga-2.0.3/lib/gui/gmstatusbar.c 2007-03-08 17:00:30.148521870 -0800
@@ -48,7 +48,7 @@
gboolean,
gboolean,
const char *,
- ...);
+ va_list args);
static int gm_statusbar_clear_msg_cb (gpointer);
@@ -100,7 +100,7 @@
gboolean flash_message,
gboolean info_message,
const char *msg,
- ...)
+ va_list args)
{
gint id = 0;
gint msg_id = 0;
@@ -119,17 +119,12 @@
gtk_statusbar_pop (GTK_STATUSBAR (sb), id);
if (msg) {
-
-va_list args;
char buffer [1025];
-va_start (args, msg);
vsnprintf (buffer, 1024, msg, args);
msg_id = gtk_statusbar_push (GTK_STATUSBAR (sb), id, buffer);
-va_end (args);
-
if (flash_message)
gtk_timeout_add (15000, gm_statusbar_clear_msg_cb,
GINT_TO_POINTER (msg_id));
diff -urNad ekiga-2.0.3~/lib/gui/gmstatusbar.h ekiga-2.0.3/lib/gui/gmstatusbar.h
--- ekiga-2.0.3~/lib/gui/gmstatusbar.h 2006-03-12 07:46:42.0 -0800
+++ ekiga-2.0.3/lib/gui/gmstatusbar.h 2007-03-08 17:00:30.148521870 -0800
@@ -94,7 +94,7 @@
*/
void gm_statusbar_flash_message (GmStatusbar *,
const char *msg,
-...);
+...) G_GNUC_PRINTF(2,3);
/* DESCRIPTION : /
@@ -105,7 +105,7 @@
*/
void gm_statusbar_push_message (GmStatusbar *,
const char *msg,
- ...);
+
Bug#413469: Please don't, there are people using it
Quoting Steve Langasek: After discussing on IRC with Joey and other ion users, it seems that there isn't really much demand for ion3 in a stable release after all; those I've talked to who use ion3 all say they run testing or unstable on their desktops, and Joey notes that the ion3 upgrade path from sarge to etch isn't likely to be a smooth one anyway. So under the circumstances, it does seem reasonable to defer to upstream (and the former maintainer) on this point. I've tagged the ion3 package and its reverse-dependencies for removal from etch. This is quite unfortunate for me. I, for one, am using officially packaged Ion3 on current stable and intended to use Ion3 also in upcomming Etch. For me (* my 3 machines) and about half a dozen of my friends this will be a serious step back to Ion2 (scratchpad is a must). I can't be bothered to install all those development packages just to compile the curent versions - I'm just a user. As far as I recollect, neither I nor my friends did bother tuomov with questions or whatever. Can't you just rename the package to ice-on and print a big fat warning on the first startup not to bother tuomov with problems? Regards Frank The fish are biting. Get more visitors on your site using Yahoo! Search Marketing. http://searchmarketing.yahoo.com/arp/sponsoredsearch_v2.php
Processed: forcibly merging 409477 355142
Processing commands for [EMAIL PROTECTED]: # Automatically generated email from bts, devscripts version 2.9.27 forcemerge 409477 355142 Bug#409477: FTBFS: cp: missing destination file operand after `oo2crc.tmp' Bug#355142: FTBFS: cp: missing destination file operand after Bug#394718: libooc-xml: FTBFS: cp: missing destination file operand after `oo2crc.tmp' Forcibly Merged 355142 394718 409477. 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#409747: marked as done (d-i build system doesn't work with new apex-nslu2 1.4.14)
Your message dated Sat, 10 Mar 2007 09:23:52 + with message-id [EMAIL PROTECTED] and subject line Bug#409747: fixed in debian-installer 20070308 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: apex Version: 1.4.14 Severity: important apex-nslu2 1.4.14 breaks the current debian-installer build because /boot/apex.flash no longer exists in the 1.4.14 deb. cp /boot/apex.flash ./tmp/ixp4xx_netboot/apex.flash cp: cannot stat `/boot/apex.flash': No such file or directory make[2]: *** [nslu2_swap] Error 1 make[1]: *** [_build] Error 2 make: *** [build_ixp4xx_netboot] Error 2 Files in apex-nslu2_1.4.7_arm.deb boot/apex.flash usr/share/doc/apex-nslu2/changelog.Debian.gz usr/share/doc/apex-nslu2/changelog.gz usr/share/doc/apex-nslu2/copyright and in apex-nslu2_1.4.14_arm.deb boot/apex.bin usr/sbin/apex-env usr/share/doc/apex-nslu2/changelog.Debian.gz usr/share/doc/apex-nslu2/changelog.gz usr/share/doc/apex-nslu2/copyright usr/share/man/man8/apex-env.8.gz Please adjust the severity of this bug appropriately. Gordon -- Gordon Farquharson ---End Message--- ---BeginMessage--- Source: debian-installer Source-Version: 20070308 We believe that the bug you reported is fixed in the latest version of debian-installer, which is due to be installed in the Debian FTP archive: debian-installer_20070308.dsc to pool/main/d/debian-installer/debian-installer_20070308.dsc debian-installer_20070308.tar.gz to pool/main/d/debian-installer/debian-installer_20070308.tar.gz debian-installer_20070308_amd64.deb to pool/main/d/debian-installer/debian-installer_20070308_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. Frans Pop [EMAIL PROTECTED] (supplier of updated debian-installer 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: Thu, 8 Mar 2007 23:43:33 +0100 Source: debian-installer Binary: debian-installer Architecture: source amd64 Version: 20070308 Distribution: unstable Urgency: low Maintainer: Frans Pop [EMAIL PROTECTED] Changed-By: Frans Pop [EMAIL PROTECTED] Description: debian-installer - Debian installer Closes: 401603 402276 403195 403895 404485 408535 409747 Changes: debian-installer (20070308) unstable; urgency=low . [ Thiemo Seufer ] * Add Qemu mips/mipsel images, thanks Aurelien Jarno. . [ Sylvain Ferriol ] * Add keyboard usb packages in i386 root floppy and move all net packages to i386 net-drivers-1 floppy. . [ Frans Pop ] * Switch font used for Dzongkha in g-i to ttf-tmuni. . [ Martin Michlmayr ] * Provide a properly encrypted firmware image for Thecus N2100 so the firmware upgrade process will recognize it. Thanks to Kurt Roeckx for help with OpenSSL. * Remove incomplete armeb support. * Remove obsolete arm/nslu2 config files. * Switch arm, mips and mipsel to 2.6.18-2. * Switch arm, mips and mipsel to 2.6.18-3. * n2100: Add support for Evesham's M-Box. * Put in a workaround to support building with both apex 1.4.7 and the new 1.4.14 which changes the name of the apex binary; closes: #409747 . [ Joey Hess ] * Stop using the system status file; generate a dummy status file for apt containing libc6 and libnewt (the only two debs udebs still depend on). * dhcp3-client-udeb is for some reason Standard priority, so gets included in monolithic image builds (and breaks the build). Exclude it from the monolithic images until its priority is fixed. * The i386 boot floppy will be too big with the 2.6.18 kernel, so drop usb input modules from it. USB keyboard support didn't work before anyway AFAICS, since usb-discover was not included. * With 2.6.18, nic-extra-modules gets too big to fit on the i386 net-drivers-1 floppy with nic-modules. Move nic-extra-modules to net-drivers-2 and reorg to fit. * Don't exclude usb drivers from driver floppies; the root floppy does not currently load them. . [ Sven Luther ] * Switch powerpc to 2.6.18-2. * Add a prep flavour. * Add fancontrol modules to cdrom and netboot images
Bug#413469: Please don't, there are people using it
On Sat, Mar 10, 2007 at 01:25:16AM -0800, Frank Bauer wrote: After discussing on IRC with Joey and other ion users, it seems that there isn't really much demand for ion3 in a stable release after all; those I've talked to who use ion3 all say they run testing or unstable on their desktops, and Joey notes that the ion3 upgrade path from sarge to etch isn't likely to be a smooth one anyway. So under the circumstances, it does seem reasonable to defer to upstream (and the former maintainer) on this point. I've tagged the ion3 package and its reverse-dependencies for removal from etch. This is quite unfortunate for me. I, for one, am using officially packaged Ion3 on current stable and intended to use Ion3 also in upcomming Etch. For me (* my 3 machines) and about half a dozen of my friends this will be a serious step back to Ion2 (scratchpad is a must). I can't be bothered to install all those development packages just to compile the curent versions - I'm just a user. As far as I recollect, neither I nor my friends did bother tuomov with questions or whatever. It's my understanding that there was an intent to provide ion3 packages via backports.org. Can't you just rename the package to ice-on and print a big fat warning on the first startup not to bother tuomov with problems? Someone could. That someone wouldn't be me, though; and anyway, I don't see how an ice-on package in stable is much better than an ion3 package on backports.org in terms of user convenience. -- 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: Debian: failed openbsd-inetd upgrade: plea for more info
Is this the line you wanted ? 2007-02-23 08:59:46 upgrade openbsd-inetd 0.20050402-3 0.20050402-4 2007-02-23 08:59:46 status half-configured openbsd-inetd 0.20050402-3 2007-02-23 08:59:47 status unpacked openbsd-inetd 0.20050402-3 2007-02-23 08:59:47 status half-installed openbsd-inetd 0.20050402-3 2007-02-23 08:59:47 status half-installed openbsd-inetd 0.20050402-3 2007-02-23 08:59:47 status unpacked openbsd-inetd 0.20050402-4 2007-02-23 08:59:47 status unpacked openbsd-inetd 0.20050402-4 2007-02-23 08:59:48 upgrade netbase 4.27 4.29 2007-02-23 08:59:48 status half-configured netbase 4.27 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]. (I'm ignoring Peter Köllner's bug report [x] here for once, since that one has possibly to do with xinetd and thus should be fixed separately.) What whould be illuminating would be thus to be able to reproduce the bug which could be helped by knowing from which version those gents were upgrading from. So please Kent, Ben, Leonardo, Norman, Mind Booster, Daniel, Uwe, Mike an Luke - could you tell us 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*. Thanks, *t [1] http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=386469#50 [2] http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=386469#55 [3] http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=386469#60 [4] http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=386469#65 [5] http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=386469#70 [6] http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=386469#75 [7] http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=386469#94 [8] http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=386469#101 [9] http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=386469#118 [x] http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=386469#45 -- Tomas Pospisek http://sourcepole.com - Linux Open Source Solutions
Bug#410106: Any news ?
Hi, is there any news on this issue ? It's been a month since the bug has been reported, and it's really painfull to force the build-dep against libpng12-dev (as lots of package doesn't depend directly on libpng at all). Please, could you fix this issue ? Regards, -- Yves-Alexis -- 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
This is quite unfortunate for me. I, for one, am using officially packaged Ion3 on current stable and intended to use Ion3 also in upcomming Etch. I can't be bothered to install all those development packages just to compile the curent versions Why do you want a random broken and unsupported development snapshot? 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? Why can't people trust the upstream to decide, when the software is stable, and insist on using (mega)frozen development snapshots? -- Tuomo -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#333151: marked as done (upgrade-reports: X broken after apt-get upgrade)
Your message dated Sat, 10 Mar 2007 04:15:12 -0800 with message-id [EMAIL PROTECTED] and subject line upgrade-reports: X broken after apt-get upgrade 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: upgrade-reports Severity: grave Justification: renders package unusable I just did an update of packages with aptitude. After I rebooted X could not be brought up, and the error log did not list any information. -- System Information: Debian Release: testing/unstable APT prefers unstable APT policy: (500, 'unstable'), (500, 'stable') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.11 Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968) ---End Message--- ---BeginMessage--- This report of X breakage on upgrade was reported almost two years ago, and the submitter never replied to any requests for information. Closing the report. Arthur, if you can provide any of the information requested, feel free to re-open the bug. -- 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#411240: [pkg-kolab] Bug#411240: kolab-cyrus-imapd: Corrupt quota files cause data loss
On Fri, Mar 09, 2007 at 05:41:55PM +0100, Peter Eisentraut wrote: Am Freitag, 9. März 2007 13:33 schrieb Steve Langasek: Does your question for the cyrus team about this bug mean there is some doubt about the patch David provided? We prefer to work in sync with the cyrus team, and in my estimate, if the bug indeed renders package unusable, then the original cyrus package and indeed all cyrus installations anywhere would be equally unusable, so I wanted to hear what they think about that. Well, the justification here isn't that the package is unusable, but that the bug causes data loss. You probably know better than I do if this same bug is present in cyrus. I think the issue is actually only applicable to some specific situations that use quotas and the quota configuration is either unusual or even corrupted. But I don't have enough experience to judge that. Quota corruption is not the fault of the package, but if it leads to data loss, that's a problem. Where exactly is the data lost anyway, though? The bug report only says that lmtpd segfaults; it's not clear to me how this results in data loss. (Mail being turned away is certainly not data loss; only mail accepted and subsequently eaten qualifies for that.) -- 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#414075: marked as done (CVE-2007-1246: DMO decoder heap allocation overflow)
Your message dated Sat, 10 Mar 2007 13:17:05 + with message-id [EMAIL PROTECTED] and subject line Bug#414075: fixed in mplayer 1.0~rc1-13 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: xine-lib Version: 1.1.2+dfsg-2 Severity: grave Tags: patch, security http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2007-1246 says: The DMO_VideoDecoder_Open function in loader/dmo/DMO_VideoDecoder.c in MPlayer 1.0rc1 and earlier does not set the biSize before use in a memcpy, which allows user-assisted remote attackers to cause a buffer overflow and possibly execute arbitrary code. xine-lib has a copy of this code in src/libw32dll/. Attached is the (tiny) patch I used in Ubuntu for 1.1.2. -- Kees Cook@outflux.net --- xine-lib-1.1.2+repacked1.orig/src/libw32dll/dmo/DMO_VideoDecoder.c +++ xine-lib-1.1.2+repacked1/src/libw32dll/dmo/DMO_VideoDecoder.c @@ -118,6 +118,7 @@ this-iv.m_bh = (BITMAPINFOHEADER*)malloc(bihs); memcpy(this-iv.m_bh, format, bihs); +this-iv.m_bh-biSize = bihs; this-iv.m_State = STOP; //this-iv.m_pFrame = 0; ---End Message--- ---BeginMessage--- Source: mplayer Source-Version: 1.0~rc1-13 We believe that the bug you reported is fixed in the latest version of mplayer, which is due to be installed in the Debian FTP archive: mplayer-doc_1.0~rc1-13_all.deb to pool/main/m/mplayer/mplayer-doc_1.0~rc1-13_all.deb mplayer_1.0~rc1-13.diff.gz to pool/main/m/mplayer/mplayer_1.0~rc1-13.diff.gz mplayer_1.0~rc1-13.dsc to pool/main/m/mplayer/mplayer_1.0~rc1-13.dsc mplayer_1.0~rc1-13_i386.deb to pool/main/m/mplayer/mplayer_1.0~rc1-13_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. A Mennucc1 [EMAIL PROTECTED] (supplier of updated mplayer 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 12:57:16 +0100 Source: mplayer Binary: mplayer-doc mplayer Architecture: source i386 all Version: 1.0~rc1-13 Distribution: unstable Urgency: low Maintainer: A Mennucc1 [EMAIL PROTECTED] Changed-By: A Mennucc1 [EMAIL PROTECTED] Description: mplayer- The Movie Player mplayer-doc - documentation for MPlayer Closes: 399144 404473 404975 405371 405945 408055 409431 412079 412252 413063 413120 413880 414075 414251 414392 414393 414394 Changes: mplayer (1.0~rc1-13) unstable; urgency=low . * fix for CVE-2007-1246 and similar (Closes: #414075) thanks Kees Cook Moritz Jodeitand R Togni patches for files loader/dmo/DMO_VideoDecoder.c from SVN 22204 loader/dshow/DS_VideoDecoder.c from SVN 22205 * [INTL] Japanese po-debconf templates translation, thanks to Kobayashi Noritada (Closes: #413120). * [INTL] Dutch po-debconf translation, thanks cobaco (Closes: #413880) * [INTL] Russian po-debconf translation, thanks Yuri Kozlov (Closes: #414251) * patch for ia64 unaligned access crash, thanks to Bryan Stillwell for debugging Reimar Döffinger for the patch (Closes: #409431). * mplayer-doc: add doc-base documentation indexes, thanks to Martintxo (Closes: #405945). * binary_codecs.sh: check MD5 on downloaded stuff (Closes: #405371). * binary_codecs.sh: check if bzip2 is there, and bail out graciously otherwise; if untarring fails, allow for retry. Fixes binary_codecs.sh doesn't install already downloaded codecs, thanks to Ingo Bressler for problem analysis (Closes: #413063). * binary_codecs.sh: do not use fping (my code lost part of URLs) (closes: #399144) * binary_codecs.sh: warn that essential-ppc codecs need libstdc++5, thanks to Bin Zhang (Closes: #404473) for pointing out. * enable smb:// (Closes: #412079). * mplayer.postinst: when vo=x11 or vo=fbdev, zoom=1 is set as well, thanks to Robert Millan (Closes: #412252). * -stop-xscreensaver option disables gnome-screensaver as well (but only if cursor is inside mplayer window) , thanks Adam TlaÅka and Reimar Döffinger (Closes: #404975). * [INTL] fix small typo in
Processed: severity of 354654 is important, tagging 354654
Processing commands for [EMAIL PROTECTED]: # Automatically generated email from bts, devscripts version 2.9.27 severity 354654 important Bug#354654: general: fat32 gets corrupted Severity set to `important' from `critical' tags 354654 unreproducible Bug#354654: general: fat32 gets corrupted There were no tags set. Tags added: unreproducible 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#386469: openbsd-inetd: action start failed
Just had the same problem, this time on a Debian testing system, instead of unstable as I had before. As someone mentioned this, I purged netkit-inetd (still had its conf files, etc.) to see if it helped, but it didn't. Again, simply stopping openbsd-inetd made it possible to upgrade. This is openbsd-inetd version 0.20050402-5. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Processed: merge redhat cluster bugs.
Processing commands for [EMAIL PROTECTED]: forcemerge 411787 412862 Bug#411787: redhat-cluster-modules-2.6.18-3-686: GFS Oops on mount at do_add_mount Bug#412862: redhat-cluster: system crash mounting gfs filesystem Forcibly Merged 411787 412862. 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#413469: ion3: The package is outdated
On Fri, Mar 09, 2007 at 05:06:50PM -0800, Steve Langasek wrote: After discussing on IRC with Joey and other ion users, it seems that there isn't really much demand for ion3 in a stable release after all; Hi, I run ion3 on Sarge and would like to upgrade to a more recent release (development snapshot or not) when Etch is released. Tuomo, the author of IonWM and the original bugreport, is probably correct in his assement of the flaws of megafreeze distributions[1] (like Debian), but I'm happy with Debian's implimentation of such, and I prefer that you not break Debian's release model by not distributing ion3 in Etch. [1] http://modeemi.fi/~tuomov/b/archives/2007/03/03/T19_15_26/ If ion3 passes the technical, legal, and other tests Debian policy requires for the benefit of it's users, ion3 should be, I belive, in Etch. I'm upset you're removing it because you talked to a very small subset of the Debian and IonWM using communities, and they didn't ``demand'' it in Etch or future stable releases. Please reconsider your decision to remove ion3 from Etch. Thank you, -Dave -- +-+ | David A. Harding | In every work of genius we recognize our own | | http://gnuisance.net | rejected thoughts; they come back to us with | | | a certain alienated majesty. -- Ralph Waldo Emmerson | +-+ pgpUQvhiKztAk.pgp Description: PGP signature
Processed: changing severity on bug #346306
Processing commands for [EMAIL PROTECTED]: severity 346306 grave Bug#346306: duplicity: Lost connection, can't resume transfer Severity set to `grave' from `important' 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#414280: Kernel 2.6.18 causes software to hang / use 100% CPU
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
Bug#413968: xmlrpc-epi turns out to be libxmlrpc in php
(For the php-maint team. I've just ITP'd xmlrpc-epi as a dependancy of the second-life client, and was poking around to see if there was a good way of not having to package it.) Interestingly, the code in ext/xmlrpc/libxmlrpc in the php5 5.2.0 tarball is a derivative of xmlrpc-epi. A quick check of the headers indicates no API changes (just some ANSI C fixes). I haven't looked at the code changes yet, but I'm not expecting anything API-breaking. (I'd read on the site that it went into PHP 4.1, but I'd not clicked that meant the actual xmlrpc-epi source had slipped into the PHP tree, nor did I realise PHP5 was still using it, since I thought they'd rewritten the xmlrpc extension in PHP5...) The PHP5 version compiles the xmlrpc-epi code plus the PHP5 extension code xmlrpc-epi-php.c together into one .so file. Would there be any interest in having PHP5 link its xmlrpc extension against a distinct library packaging of xmlrpc-epi? (ie. to avoid the situation which once existed for zlib being statically compiled into various other packages, causing security headaches...) xmlrpc-epi seems like a useful standalone library to me, since (unlike libxmlrpc-c3) it doesn't include a network transport layer, allowing the actual transport to be handled by the user, and it's in C (unlike libxmlrpc++). And second-life client will be user number 2, that I know of. Of course, if PHP5 was using an external xmlrpc-epi library, it would have to be something other than /usr/lib/libxmlrpc.so, as that's already taken by libxmlrpc-c3. Interestingly Mandriva and PLD both consider libxmlrpc-epi to be /usr/lib/libxmlrpc.so and libxmlrpc-c3 is instead /usr/lib/libxmlrpc-c.so. Gentoo appears to be happy to have them both be libxmlrpc.so, and FreeBSD's ports collection conflicts them. So the naming field is wide open. I'm leaning towards libxmlrpc-epi.so I plan to go through the changes to the library in PHP5 and see if there's anything that would preclude general use. I suspect many of the .c changes were the result of either bugfixes that I want, or the conversion to use a modern expat API rather than the API circa 2000, which I've also done to my copy of xmlrpc-epi. On a side note, config.m4 in ext/xmlrpc is currently forcing the xmlrpc-epi version to 0.50, even though comments in the code in the libxmlrpc directory indicate it was later synced up with 0.51 (the last upstream release of xmlrpc-epi). -- Paul TBBle Hampson, [EMAIL PROTECTED] Shorter .sig for a more eco-friendly paperless office. pgpHWjZLIxXp9.pgp Description: PGP signature
Bug#408076: swi-prolog: FTBFS on GNU/kFreeBSD, mips, mipsel (due to outdated config.sub/config.guess)
On Sat, Jan 27, 2007 at 10:53:03AM +0100, Jens Seidel wrote: On Tue, Jan 23, 2007 at 11:47:59AM +0100, Petr Salinger wrote: Package: swi-prolog the current version fails to build on GNU/kFreeBSD, mips, mipsel. please use attached tweak for debian/rules to auto-update them. I can confirm this bug an mips. No upload yet? OK, I tested it now also on a mipsel box and the patch is indeed required and works well! Jens -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#414283: libssl0.9.8: shlibs dependencies aren't strict enough
Package: libssl0.9.8 Version: 0.9.8e-3 Severity: serious I upgraded openssl to 0.9.8e-3 while still having libssl0.9.8 0.9.8c-4 installed. Today, I upgraded the ca-certificates package. fetchmail then refused fetching any emails saying 29033:error:14090086:SSL routines:SSL3_GET_SERVER_CERTIFICATE:certificate verify failed:s3_clnt.c:894: It took me some time until I ran update-ca-certificates -f -v which told me the actual problem, there were tons of: ... openssl: relocation error: openssl: symbol EVP_MD_type, version OPENSSL_0.9.8 not defined in file libcrypto.so.0.9.8 with link time reference unable to load certificate 29775:error:0D0680A8:asn1 encoding routines:ASN1_CHECK_TLEN:wrong tag:tasn_dec.c:1296: 29775:error:0D07803A:asn1 encoding routines:ASN1_ITEM_EX_D2I:nested asn1 error:tasn_dec.c:380:Type=X509 WARNING: Skipping duplicate certificate signet_tsa1_pem.pem unable to load certificate 29777:error:0906D06C:PEM routines:PEM_read_bio:no start line:pem_lib.c:644:Expecting: TRUSTED CERTIFICATE openssl: relocation error: openssl: symbol EVP_MD_type, version OPENSSL_0.9.8 no... Upgrading libssl0.9.8 to 0.9.8e-3 fixed this issue. $ cat /var/lib/dpkg/info/libssl0.9.8.shlibs libcrypto 0.9.8 libssl0.9.8 (= 0.9.8c-1) libssl 0.9.8 libssl0.9.8 (= 0.9.8c-1) udeb: libcrypto 0.9.8 libcrypto0.9.8-udeb (= 0.9.8c-1) udeb: libssl 0.9.8 libcrypto0.9.8-udeb (= 0.9.8c-1) $ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#414284: wesnoth should build-depend on g++
Package: wesnoth Version: 1.2-1 Severity: serious Justification: no longer builds from source Wesnoth configuration fails unless we manually install g++ -- 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: LANG=fr_CA.UTF-8, LC_CTYPE=fr_CA.UTF-8 (charmap=UTF-8) Versions of packages wesnoth depends on: ii libc6 2.3.6.ds1-13 GNU C Library: Shared libraries ii libfreetype62.2.1-5 FreeType 2 font engine, shared lib ii libfribidi0 0.10.7-4 Free Implementation of the Unicode ii libgcc1 1:4.1.1-21 GCC support library ii libsdl-image1.2 1.2.5-2+b1 image loading library for Simple D ii libsdl-mixer1.2 1.2.6-1.1+b2 mixer library for Simple DirectMed ii libsdl-net1.2 1.2.5-7+b1 network library for Simple DirectM ii libsdl1.2debian 1.2.11-8 Simple DirectMedia Layer ii libstdc++6 4.1.1-21 The GNU Standard C++ Library v3 ii libx11-62:1.0.3-5X11 client-side library ii python2.4 2.4.4-2 An interactive high-level object-o ii wesnoth-data1.2-1data files for Wesnoth ii zlib1g 1:1.2.3-13 compression library - runtime wesnoth recommends no packages. -- no debconf information -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#414285: bash builtin printf ignores write errors
Package: bash Version: 2.05b-26 Severity: grave sfere$ type bash bash is hashed (/bin/bash) sfere$ bash -c 'type printf' printf is a shell builtin sfere$ bash -c 'printf spong' /dev/full sfere$ echo $? 0 Compare: sfere$ /usr/bin/printf spong /dev/full /usr/bin/printf: write error: No space left on device sfere$ echo $? 1 ttfn/rjk -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#414284: marked as done (wesnoth should build-depend on g++)
Your message dated Sat, 10 Mar 2007 17:54:59 +0100 with message-id [EMAIL PROTECTED] and subject line Invalid bug 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: wesnoth Version: 1.2-1 Severity: serious Justification: no longer builds from source Wesnoth configuration fails unless we manually install g++ -- 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: LANG=fr_CA.UTF-8, LC_CTYPE=fr_CA.UTF-8 (charmap=UTF-8) Versions of packages wesnoth depends on: ii libc6 2.3.6.ds1-13 GNU C Library: Shared libraries ii libfreetype62.2.1-5 FreeType 2 font engine, shared lib ii libfribidi0 0.10.7-4 Free Implementation of the Unicode ii libgcc1 1:4.1.1-21 GCC support library ii libsdl-image1.2 1.2.5-2+b1 image loading library for Simple D ii libsdl-mixer1.2 1.2.6-1.1+b2 mixer library for Simple DirectMed ii libsdl-net1.2 1.2.5-7+b1 network library for Simple DirectM ii libsdl1.2debian 1.2.11-8 Simple DirectMedia Layer ii libstdc++6 4.1.1-21 The GNU Standard C++ Library v3 ii libx11-62:1.0.3-5X11 client-side library ii python2.4 2.4.4-2 An interactive high-level object-o ii wesnoth-data1.2-1data files for Wesnoth ii zlib1g 1:1.2.3-13 compression library - runtime wesnoth recommends no packages. -- no debconf information ---End Message--- ---BeginMessage--- Please, read section 4.2 of the Debian Policy: http://www.debian.org/doc/debian-policy/ch-source.html Best regards -- Isaac Clerencia at Warp Networks, http://www.warp.es Work: [EMAIL PROTECTED] | Debian: [EMAIL PROTECTED] pgpeiQZ1jItJQ.pgp Description: PGP signature ---End Message---
Bug#414203: marked as done (Installation problems: Wrong partition type for physical raid partitions)
Your message dated Sat, 10 Mar 2007 17:02:05 + with message-id [EMAIL PROTECTED] and subject line Bug#414203: fixed in partman-md 34 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: installation-reports Version: etch daily netinst 20070308 amd64 Machine: Dual Xeon on Intel S5000P SL Board HD: 2x 320 Gb SATA on PCI-controller (onboard controller not working during installation) During manual partition setup, I removed all existing partitions (linux ext3, swap, no raid partitions) on both disks, and created on each disk 3 partitions with type 'physical raid' as sda1-3 and sdb1-3. They showed up as '.. K raid .. '. When I started 'Configure Software Raid', the partition tables were saved, but after selecting 'RAID1' I got an error message 'could not find any Linux Raid Autodetect' partitions'. Changing the type to Linux extended and back to physical raid did not help. They showed up correctly in the partition editor, but were not detected by the software raid configuration. After changing the type to 'do not use', the partition showed up as 'Linux' in the partition list. On the console, fdisk listed the correct partitions, but with type Linux. After starting the Configure Software Raid tool and manually changing the type of all partitions to 'fd' Linux RAID Autodetect', everything worked as expected (configuring the raid, installing onto the new raid partitions, rebooting,..) Sorry, I did not test it with an older version of the installer, so I am not sure if this is a new bug in the partitioning tool or simply a fancy 'one-time broken-partition-table' bug (which would be my guess), because i simply was glad that it worked at all after some trouble with the onboard SATA controller and I had not much time :) (i think the kernel of the installer was too old for the onboard sata (seems to be a known bug) so we had to use a PCI controller; after booting into the newly installed 2.6.18 kernel, the onboard controller worked). Stefan Hepp ---End Message--- ---BeginMessage--- Source: partman-md Source-Version: 34 We believe that the bug you reported is fixed in the latest version of partman-md, which is due to be installed in the Debian FTP archive: partman-md_34.dsc to pool/main/p/partman-md/partman-md_34.dsc partman-md_34.tar.gz to pool/main/p/partman-md/partman-md_34.tar.gz partman-md_34_all.udeb to pool/main/p/partman-md/partman-md_34_all.udeb 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. Frans Pop [EMAIL PROTECTED] (supplier of updated partman-md 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 17:53:26 +0100 Source: partman-md Binary: partman-md Architecture: source all Version: 34 Distribution: unstable Urgency: low Maintainer: Debian Install System Team debian-boot@lists.debian.org Changed-By: Frans Pop [EMAIL PROTECTED] Description: partman-md - Add to partman support for MD (udeb) Closes: 414203 Changes: partman-md (34) unstable; urgency=low . * Fix syntax error resulting in failure to set partition type. Closes: #414203. Files: 9b2437f5ea8af529057cecfd09aaf694 621 debian-installer standard partman-md_34.dsc 659d986cfbec225bf20e009502b1776b 43645 debian-installer standard partman-md_34.tar.gz 72bd37dc749a06fc93a9dcb1eb6192fb 29000 debian-installer standard partman-md_34_all.udeb Package-Type: udeb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.6 (GNU/Linux) iD8DBQFF8uLXgm/Kwh6ICoQRAvTYAJsHk9zGw/QguSCZqnrzOwz8/vBcCACgqmbH cmaQ9lOhMk020ZkDQ5mdu9A= =PCCC -END PGP SIGNATURE- ---End Message---
Bug#414290: Experimental libc-client packages almost empty
Source: uw-imap Version: 7:2006d.dfsg-1 Severity: grave Packages libc-client2006b.dfsg-1 and libc-client2006b.dfsg-1-dev end up empty, except for some files in /usr/share/doc/*. Seems you forgot to update the package names to 2006d in debian/control. -- Magnus Holmgren[EMAIL PROTECTED] (No Cc of list mail needed, thanks) pgppz5gIGHS0P.pgp Description: PGP signature
Bug#413968: [php-maint] xmlrpc-epi turns out to be libxmlrpc in php
hi paul, On Sun, 2007-03-11 at 03:05 +1100, Paul TBBle Hampson wrote: Would there be any interest in having PHP5 link its xmlrpc extension against a distinct library packaging of xmlrpc-epi? (ie. to avoid the situation which once existed for zlib being statically compiled into various other packages, causing security headaches...) just to clarify, are you proposing that php link against an externally provided xmlrpc-epi library, or are you proposing that php provide its bundled version *as* the xmlrpc-epi library for other apps to use? i'm fairly open to both ideas though i think the former sounds better than the latter, assuming there are no api/abi differences. also, are you volunteering to do the packaging? :) sean signature.asc Description: This is a digitally signed message part
Bug#414292: list: postinst failure because of improper group creation
Package: list
Version: 2.0.0-1
Severity: grave
Justification: renders package unusable
Hi,
here is the problem on my system:
Setting up list (2.0.0-1) ...
chgrp: invalid group `stats'
chgrp: invalid group `stats'
dpkg: error processing list (--configure):
It is caused by this incorrect group existence test in
/var/lib/dpkg/info/list.postinst:
stats=`grep stats /etc/group 2/dev/null`
if [ ${stats} == ]; then
addgroup --system stats
fi
This test does not work on my system because /etc/group contains the
following line:
remstats:x:146:www-data
Therefore I propose that you replace the test with:
stats=`grep ^stats /etc/group 2/dev/null`
-- System Information:
Debian Release: 4.0
APT prefers unstable
APT policy: (100, 'unstable'), (99, 'experimental')
Architecture: i386 (i686)
Shell: /bin/sh linked to /bin/bash
Kernel: Linux 2.6.18-4-686
Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8)
Versions of packages list depends on:
ii adduser 3.102 Add and remove users and groups
ii diff 2.8.7-0.2 File comparison utilities
ii grep 2.5.1.ds2-6 GNU grep, egrep and fgrep
ii python 2.4.4-2 An interactive high-level object-o
ii sed 4.1.5-1 The GNU sed stream editor
ii util-linux 2.12r-19Miscellaneous system utilities
list recommends no packages.
-- no debconf information
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Processed: severity of 346306 is important
Processing commands for [EMAIL PROTECTED]: # Automatically generated email from bts, devscripts version 2.8.14 severity 346306 important Bug#346306: duplicity: Lost connection, can't resume transfer Severity set to `important' from `grave' 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#414283: marked as done (libssl0.9.8: shlibs dependencies aren't strict enough)
Your message dated Sat, 10 Mar 2007 17:47:02 + with message-id [EMAIL PROTECTED] and subject line Bug#414283: fixed in openssl 0.9.8e-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: libssl0.9.8 Version: 0.9.8e-3 Severity: serious I upgraded openssl to 0.9.8e-3 while still having libssl0.9.8 0.9.8c-4 installed. Today, I upgraded the ca-certificates package. fetchmail then refused fetching any emails saying 29033:error:14090086:SSL routines:SSL3_GET_SERVER_CERTIFICATE:certificate verify failed:s3_clnt.c:894: It took me some time until I ran update-ca-certificates -f -v which told me the actual problem, there were tons of: ... openssl: relocation error: openssl: symbol EVP_MD_type, version OPENSSL_0.9.8 not defined in file libcrypto.so.0.9.8 with link time reference unable to load certificate 29775:error:0D0680A8:asn1 encoding routines:ASN1_CHECK_TLEN:wrong tag:tasn_dec.c:1296: 29775:error:0D07803A:asn1 encoding routines:ASN1_ITEM_EX_D2I:nested asn1 error:tasn_dec.c:380:Type=X509 WARNING: Skipping duplicate certificate signet_tsa1_pem.pem unable to load certificate 29777:error:0906D06C:PEM routines:PEM_read_bio:no start line:pem_lib.c:644:Expecting: TRUSTED CERTIFICATE openssl: relocation error: openssl: symbol EVP_MD_type, version OPENSSL_0.9.8 no... Upgrading libssl0.9.8 to 0.9.8e-3 fixed this issue. $ cat /var/lib/dpkg/info/libssl0.9.8.shlibs libcrypto 0.9.8 libssl0.9.8 (= 0.9.8c-1) libssl 0.9.8 libssl0.9.8 (= 0.9.8c-1) udeb: libcrypto 0.9.8 libcrypto0.9.8-udeb (= 0.9.8c-1) udeb: libssl 0.9.8 libcrypto0.9.8-udeb (= 0.9.8c-1) $ ---End Message--- ---BeginMessage--- Source: openssl Source-Version: 0.9.8e-4 We believe that the bug you reported is fixed in the latest version of openssl, which is due to be installed in the Debian FTP archive: libcrypto0.9.8-udeb_0.9.8e-4_amd64.udeb to pool/main/o/openssl/libcrypto0.9.8-udeb_0.9.8e-4_amd64.udeb libssl-dev_0.9.8e-4_amd64.deb to pool/main/o/openssl/libssl-dev_0.9.8e-4_amd64.deb libssl0.9.8-dbg_0.9.8e-4_amd64.deb to pool/main/o/openssl/libssl0.9.8-dbg_0.9.8e-4_amd64.deb libssl0.9.8_0.9.8e-4_amd64.deb to pool/main/o/openssl/libssl0.9.8_0.9.8e-4_amd64.deb openssl_0.9.8e-4.diff.gz to pool/main/o/openssl/openssl_0.9.8e-4.diff.gz openssl_0.9.8e-4.dsc to pool/main/o/openssl/openssl_0.9.8e-4.dsc openssl_0.9.8e-4_amd64.deb to pool/main/o/openssl/openssl_0.9.8e-4_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. Kurt Roeckx [EMAIL PROTECTED] (supplier of updated openssl 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 17:11:46 + Source: openssl Binary: libssl-dev openssl libssl0.9.8-dbg libcrypto0.9.8-udeb libssl0.9.8 Architecture: source amd64 Version: 0.9.8e-4 Distribution: unstable Urgency: low Maintainer: Debian OpenSSL Team [EMAIL PROTECTED] Changed-By: Kurt Roeckx [EMAIL PROTECTED] Description: libcrypto0.9.8-udeb - crypto shared library - udeb (udeb) libssl-dev - SSL development libraries, header files and documentation libssl0.9.8 - SSL shared libraries libssl0.9.8-dbg - Symbol tables for libssl and libcrypt openssl- Secure Socket Layer (SSL) binary and related cryptographic tools Closes: 414283 Changes: openssl (0.9.8e-4) unstable; urgency=low . * openssl should depend on libssl0.9.8 0.9.8e-1 since it uses some of the defines that changed to functions. Other things build against libssl or libcrypto shouldn't have this problem since they use the old headers. (Closes: #414283) Files: a0b0929a8fcbd0b449ebfcf97e08a638 797 utils optional openssl_0.9.8e-4.dsc 26d28d5706201be447da652dbbff488f 44265 utils optional openssl_0.9.8e-4.diff.gz d9bbb42711eb5a8b8ff04e67234c84a9 1008548 utils optional openssl_0.9.8e-4_amd64.deb b5efbd5b617177eb45cf5b09d0231775 896292 libs important libssl0.9.8_0.9.8e-4_amd64.deb c05afeb0e5bd440b9a510a1d97ddfe06 582070 debian-installer optional libcrypto0.9.8-udeb_0.9.8e-4_amd64.udeb ce80e993867d598a58ea5d0acb6d19aa 2187852 libdevel optional libssl-dev_0.9.8e-4_amd64.deb
Processed: Re: Bug#414203: Installation problems: Wrong partition type for physical raid partitions
Processing commands for [EMAIL PROTECTED]: reassign 414203 partman-md 33 Bug#414203: Installation problems: Wrong partition type for physical raid partitions Bug reassigned from package `installation-reports' to `partman-md'. severity 414203 serious Bug#414203: Installation problems: Wrong partition type for physical raid partitions Severity set to `serious' 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]
Bug#408076: swi-prolog: FTBFS on GNU/kFreeBSD, mips, mipsel (due to outdated config.sub/config.guess)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Sorry for the late answer.. Jens Seidel escribió: On Sat, Jan 27, 2007 at 10:53:03AM +0100, Jens Seidel wrote: On Tue, Jan 23, 2007 at 11:47:59AM +0100, Petr Salinger wrote: Package: swi-prolog the current version fails to build on GNU/kFreeBSD, mips, mipsel. please use attached tweak for debian/rules to auto-update them. I can confirm this bug an mips. No upload yet? OK, I tested it now also on a mipsel box and the patch is indeed required and works well! That's great, i'll be preparing a new upload in the following days. Thanks for your work. Jens - -- Gerardo Curiel [EMAIL PROTECTED] [EMAIL PROTECTED] Geek By NaTure,LiNuX By ChOiCe,DebiAn of CoUrsE gpg fingerprint: 228B 0F96 8653 DF52 9740 B75E FB32 9C30 E179 7BD2 http://www.debian.org -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.6 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFF8wXk+zKcMOF5e9IRAqy9AJ9Wqd3CwlO4vTbwx9f1IfTgYYqi8wCgxD3i LhWxUIFEQGjqj0I4u1TBQfw= =eCTY -END PGP SIGNATURE-
Bug#412314: mozilla-tabextensions: tabextenions makes iceweasel unusable for sites using JavaScript
Hi! I've had lots of problems with this package before (although I usually installed it directly from upstream). Afaik, it's totally broken for firefox/iceweasel 2.0, and almost all of its features are included in other extensions like Tabmix Plus. Upstream's homepage [1] even reads: This extension strongly unrecommended. This extension is for Firefox 1.5 or earlier only, so it doesn't work with Firefox 2, even if you install it by some informal ways. It will cause many many errors because the structure, this extension bases on, is completely changed from Firefox 1.5 to Firefox 2. This extension is strongly unrecommended by Mozilla Foundation. See advantage and disadvantage before you download this. If you wish to install this even if you read those comments, do it at your own risk. Do we really want to ship this with etch, or keep in the archive altogether? [1] http://piro.sakura.ne.jp/xul/tabextensions/index.html.en greetings, Bas. -- Kind regards, ++ | Bas Zoetekouw | GPG key: 0644fab7 | || Fingerprint: c1f5 f24c d514 3fec 8bf6 | | [EMAIL PROTECTED] | a2b1 2bae e41f 0644 fab7 | ++ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#386469: tagging 386469
Le jeudi 8 mars 2007 19:23, vous avez écrit : # Automatically generated email from bts, devscripts version 2.9.27 tags 386469 help Hi Marco, could you help helping you a bit? Are you still trying to identify in which case this bug occurs? If not, please explain when it occurs.
Bug#413709: marked as done (wrong permissions on /usr/lib/squid +s files)
Your message dated Sat, 10 Mar 2007 20:32:05 + with message-id [EMAIL PROTECTED] and subject line Bug#413709: fixed in squid 2.6.5-5 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: squid Version: 2.6.5-4 Severity: serious Squid breaks debsums: debsums: can't open squid file /usr/lib/squid/pam_auth (Permission denied) debsums: can't open squid file /usr/lib/squid/getpwnam_auth (Permission denied) Those files are setgid group shadow and thus it makes sense that they are not executable by others. However, that doesn't mean they cannot be readable. Section 10.9. of the policy says: Some setuid programs need to be restricted to particular sets of users, using file permissions. In this case they should be owned by the uid to which they are set-id, and by the group which should be allowed to execute them. They should have mode 4754; again there is no point in making them unreadable to those users who must not be allowed to execute them. I filed this as RC because the policy covers the case. I don't really think it's that critical, so please downgrade if you wish. Or just upload a quick fix (or tell me to NMU it). -- System Information: Debian Release: 4.0 APT prefers unstable APT policy: (750, 'unstable'), (500, 'testing'), (250, 'stable'), (1, 'experimental') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/dash Kernel: Linux 2.6.18-4-686 Locale: LANG=en_GB, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8) Versions of packages squid depends on: ii adduser 3.102Add and remove users and groups ii coreutils 5.97-5.3 The GNU core utilities ii debconf [debconf-2.0] 1.5.11 Debian configuration management sy ii libc6 2.3.6.ds1-13 GNU C Library: Shared libraries ii libdb4.44.4.20-8 Berkeley v4.4 Database Libraries [ ii libldap22.1.30-13.3 OpenLDAP libraries ii libpam0g0.79-4 Pluggable Authentication Modules l ii logrotate 3.7.1-3 Log rotation utility ii lsb-base3.1-23 Linux Standard Base 3.1 init scrip ii netbase 4.29 Basic TCP/IP networking system ii squid-common2.6.5-4 Internet Object Cache (WWW proxy c squid recommends no packages. -- debconf information excluded -- .''`. martin f. krafft [EMAIL PROTECTED] : :' : proud Debian developer, author, administrator, and user `. `'` http://people.debian.org/~madduck - http://debiansystem.info `- Debian - when you have better things to do than fixing systems signature.asc Description: Digital signature (GPG/PGP) ---End Message--- ---BeginMessage--- Source: squid Source-Version: 2.6.5-5 We believe that the bug you reported is fixed in the latest version of squid, which is due to be installed in the Debian FTP archive: squid-cgi_2.6.5-5_sparc.deb to pool/main/s/squid/squid-cgi_2.6.5-5_sparc.deb squid-common_2.6.5-5_all.deb to pool/main/s/squid/squid-common_2.6.5-5_all.deb squid_2.6.5-5.diff.gz to pool/main/s/squid/squid_2.6.5-5.diff.gz squid_2.6.5-5.dsc to pool/main/s/squid/squid_2.6.5-5.dsc squid_2.6.5-5_sparc.deb to pool/main/s/squid/squid_2.6.5-5_sparc.deb squidclient_2.6.5-5_sparc.deb to pool/main/s/squid/squidclient_2.6.5-5_sparc.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. Luigi Gangitano [EMAIL PROTECTED] (supplier of updated squid 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 20:01:12 +0100 Source: squid Binary: squid squid-cgi squidclient squid-common Architecture: source sparc all Version: 2.6.5-5 Distribution: unstable Urgency: low Maintainer: Luigi Gangitano [EMAIL PROTECTED] Changed-By: Luigi Gangitano [EMAIL PROTECTED] Description: squid - Internet Object Cache (WWW proxy cache) squid-cgi - Squid cache manager CGI program squid-common - Internet Object Cache (WWW proxy cache) - common file squidclient - Command line URL extractor that talks to (a) squid
Bug#411027: libkwiki-perl: plugin reported as missing (perl?)
Hi!
I've verified that Nicolas's patch works fine, and I'm currently
preparing an NMU for libkwiki-perl. A diff describing the changes is
attached.
Greetings,
bas.
--
Kind regards,
++
| Bas Zoetekouw | GPG key: 0644fab7 |
|| Fingerprint: c1f5 f24c d514 3fec 8bf6 |
| [EMAIL PROTECTED] | a2b1 2bae e41f 0644 fab7 |
++
diff -Nabur libkwiki-perl-0.38.eerst/debian/changelog
libkwiki-perl-0.38/debian/changelog
--- libkwiki-perl-0.38.eerst/debian/changelog 2007-03-10 21:25:00.0
+0100
+++ libkwiki-perl-0.38/debian/changelog 2007-03-10 21:25:08.0 +0100
@@ -1,3 +1,12 @@
+libkwiki-perl (0.38-1.1) unstable; urgency=medium
+
+ * Non-maintainer upload
+ * Added a call to $self-handle_update_all to handle_new() in Command.pm.
+Thanks to Nicolas François for the patch.
+(closes: #411027)
+
+ -- Bas Zoetekouw [EMAIL PROTECTED] Sat, 10 Mar 2007 21:18:58 +0100
+
libkwiki-perl (0.38-1) unstable; urgency=low
* Initial Release.
diff -Nabur libkwiki-perl-0.38.eerst/lib/Kwiki/Command.pm
libkwiki-perl-0.38/lib/Kwiki/Command.pm
--- libkwiki-perl-0.38.eerst/lib/Kwiki/Command.pm 2005-04-03
12:50:54.0 +0200
+++ libkwiki-perl-0.38/lib/Kwiki/Command.pm 2007-03-10 21:25:08.0
+0100
@@ -19,6 +19,7 @@
$self-install('widgets');
io('plugin')-mkdir;
$self-set_permissions;
+$self-handle_update_all;
warn \nKwiki software installed! Point your browser at this
location.\n\n;
}
Processed: tagging 414290
Processing commands for [EMAIL PROTECTED]: # Automatically generated email from bts, devscripts version 2.9.27 tags 414290 experimental Bug#414290: Experimental libc-client packages almost empty There were no tags set. Tags added: experimental 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#411027: marked as done (libkwiki-perl: plugin reported as missing (perl?))
Your message dated Sat, 10 Mar 2007 20:47:02 +
with message-id [EMAIL PROTECTED]
and subject line Bug#411027: fixed in libkwiki-perl 0.38-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: libkwiki-perl
Version: 0.38-1
Severity: grave
Justification: renders package unusable
I installed the package, run kwiki as described at the doku, made apache2
point to the location (using the example code in the README) and tried:
http://localhost/kwiki/ in the web browser.
This gave the following response:
=
Software error:
No plugin for action 'display' at /usr/share/perl5/Spoon/Hub.pm line 34.
For help, please send mail to the webmaster ([EMAIL PROTECTED]), giving
this error message and the time and date of the error.
Software error:
[Thu Feb 15 11:48:42 2007] index.cgi: No plugin for action 'display' at
/usr/share/perl5/Spoon/Hub.pm line 34.
at /usr/share/perl5/Spoon/Base.pm line 110
Spoon::Base::__ANON__('[Thu Feb 15 11:48:42 2007] index.cgi: No
plugin for action \'...') called at /usr/share/perl/5.8/CGI/Carp.pm line 314
CGI::Carp::realdie('[Thu Feb 15 11:48:42 2007] index.cgi: No plugin
for action \'...') called at /usr/share/perl/5.8/CGI/Carp.pm line 400
CGI::Carp::die('No plugin for action \'display\'') called at
/usr/share/perl5/Spoon/Hub.pm line 34
Spoon::Hub::process('Kwiki::Hub=HASH(0x848aca8)') called at
//usr/share/perl5/Kwiki.pm line 12
Kwiki::process('Kwiki=HASH(0x833eac4)', 'config*.*', '-plugins',
'plugins') called at /var/www/kwiki/index.cgi line 4
For help, please send mail to the webmaster ([EMAIL PROTECTED]), giving
this error message and the time and date of the error.
=
I do not know if this is because of missing dependencies of this package or
of libspoon-perl or whatever.
Please mail me if I can help with further information.
Thanks.
Klaus
-- 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=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8)
Versions of packages libkwiki-perl depends on:
ii libspoon-perl 0.23-2 A Spiffy Application Building Fram
ii perl 5.8.8-7Larry Wall's Practical Extraction
libkwiki-perl recommends no packages.
-- no debconf information
---End Message---
---BeginMessage---
Source: libkwiki-perl
Source-Version: 0.38-1.1
We believe that the bug you reported is fixed in the latest version of
libkwiki-perl, which is due to be installed in the Debian FTP archive:
libkwiki-perl_0.38-1.1.diff.gz
to pool/main/libk/libkwiki-perl/libkwiki-perl_0.38-1.1.diff.gz
libkwiki-perl_0.38-1.1.dsc
to pool/main/libk/libkwiki-perl/libkwiki-perl_0.38-1.1.dsc
libkwiki-perl_0.38-1.1_all.deb
to pool/main/libk/libkwiki-perl/libkwiki-perl_0.38-1.1_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.
Bas Zoetekouw [EMAIL PROTECTED] (supplier of updated libkwiki-perl 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:18:58 +0100
Source: libkwiki-perl
Binary: libkwiki-perl
Architecture: source all
Version: 0.38-1.1
Distribution: unstable
Urgency: medium
Maintainer: Bas Zoetekouw [EMAIL PROTECTED]
Changed-By: Bas Zoetekouw [EMAIL PROTECTED]
Description:
libkwiki-perl - Kwiki Wiki Building Framework
Closes: 411027
Changes:
libkwiki-perl (0.38-1.1) unstable; urgency=medium
.
* Non-maintainer upload
* Added a call to $self-handle_update_all to handle_new() in Command.pm.
Thanks to Nicolas François for the patch.
(closes: #411027)
Files:
9b366fda4812d7acb508d0425b448ea8 649 perl optional libkwiki-perl_0.38-1.1.dsc
dc395d81e961ca0ba3f711990b952138 2087 perl optional
libkwiki-perl_0.38-1.1.diff.gz
6d2d1da0fa956ee888575d135e0df5bd 80906 perl optional
libkwiki-perl_0.38-1.1_all.deb
-BEGIN PGP SIGNATURE-
Bug#413288: FTBFS on mipsel/experimental (Was: Re: Log for failed build of postfix_2.4.0~rc2-1 (dist=experimental))
On Sat, Mar 03, 2007 at 07:04:22PM -0700, LaMont Jones wrote: On Sun, Mar 04, 2007 at 12:15:33AM +0100, Martin Zobel-Helas wrote: ../../lib/libdns.a: undefined reference to `_info' Well, that's a different error than I've seen on the mipsel buildd for unstable... Which I also haven't been able to reproduce I could also not reproduce this (or another) error in my etch system with build dependencies from unstable. Jens -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Processed: Re: netserver can be locked by /tmp/netperf.debug
Processing commands for [EMAIL PROTECTED]: package netperf Ignoring bugs not assigned to: netperf severity 413658 serious Bug#413658: netserver can be locked by /tmp/netperf.debug Severity set to `serious' from `wishlist' tags 413658 security Bug#413658: netserver can be locked by /tmp/netperf.debug There were no tags set. Tags added: security retitle 413658 netserver logs to insecure temporary file Bug#413658: netserver can be locked by /tmp/netperf.debug Changed Bug title. 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: found 414045 in 2:1.0.3-6
Processing commands for [EMAIL PROTECTED]: # Automatically generated email from bts, devscripts version 2.9.26 found 414045 2:1.0.3-6 Bug#414045: libX11: Buffer overflow in XGetPixel(). Bug marked as found in version 2:1.0.3-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#386469: openbsd-inetd: action start failed
On Sat, 10 Mar 2007, Ludo wrote: Just had the same problem, this time on a Debian testing system, instead of unstable as I had before. As someone mentioned this, I purged netkit-inetd (still had its conf files, etc.) to see if it helped, but it didn't. Again, simply stopping openbsd-inetd made it possible to upgrade. This is openbsd-inetd version 0.20050402-5. From which previous openbsd-inetd versions were you upgrading? What were the packages that were upgraded along openbsd-inetd? Please have a look at /var/log/aptitude*, /var/log/dpkg.log* and /var/backups/dpkg* *t -- 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#394977: sorry, wrong bug number
ooops, sorry wrong bug number -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Processed: retitle 386469 to openbsd-inetd, action start failed when upgrading
Processing commands for [EMAIL PROTECTED]: # Automatically generated email from bts, devscripts version 2.9.26 retitle 386469 openbsd-inetd, action start failed when upgrading Bug#386469: openbsd-inetd: action start failed Changed Bug title. 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#409880: marked as done (FW: libpam-ldap upgrade breaks pam_ldap.conf and can't login)
Your message dated Sat, 10 Mar 2007 23:02:08 + with message-id [EMAIL PROTECTED] and subject line Bug#407746: fixed in libpam-ldap 180-1.7 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: libpam-ldap Version: 180-1.5 I've sent the following email and did not receive a response from the libpam-ldap maintainer. I've upgraded another sarge box since and confirmed the bug still exists. This is a serious problem for upgrades from sarge, or any package update, so please fix it before release. -Original Message- From: Jamie ffolliott [mailto:[EMAIL PROTECTED] Sent: Saturday, January 20, 2007 5:59 PM To: '[EMAIL PROTECTED]' Subject: libpam-ldap upgrade breaks pam_ldap.conf and can't login Package: libpam-ldap Version: 180-1.4 After an apt-get upgrade, the libpam-ldap packate updated, and in doing so it rewrote parts of the /etc/pam_ldap.conf file as follows - rewrote host, base, ldap_version, pam_password - commented out the uri setting, which is an alternative setting to host that supports ldap over ssl. Since I don't use unencrypted logins to my ldap server, and I'm not sure who would do such a thing, I cannot use the host setting. The latter step that comments out uri in fact breaks authentication to this machine. I've tried dpkg-reconfigure libpam-ldap and there's no option to preserve my URI setting, which must be set to ldaps://ldap.mydomain.com for logins to succeed. Even if I leave host blank, it will still disable the uri setting - and this is the heart of the issue, I can't avoid breaking the existing libpam-ldap config. Luckily I have ssh's pub key authentication setup, so I can get in to fix, but without that this debian client would be rendered useless upon upgrade from sarge to etch. Please consider this critical, I don't want all my servers to be rendered inaccessible after upgrading to etch which I hope to do upon release. It locks out access to the box completely. Thx! ---End Message--- ---BeginMessage--- Source: libpam-ldap Source-Version: 180-1.7 We believe that the bug you reported is fixed in the latest version of libpam-ldap, which is due to be installed in the Debian FTP archive: libpam-ldap_180-1.7.diff.gz to pool/main/libp/libpam-ldap/libpam-ldap_180-1.7.diff.gz libpam-ldap_180-1.7.dsc to pool/main/libp/libpam-ldap/libpam-ldap_180-1.7.dsc libpam-ldap_180-1.7_i386.deb to pool/main/libp/libpam-ldap/libpam-ldap_180-1.7_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. Steve Langasek [EMAIL PROTECTED] (supplier of updated libpam-ldap 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: Fri, 9 Mar 2007 02:35:03 -0800 Source: libpam-ldap Binary: libpam-ldap Architecture: source i386 Version: 180-1.7 Distribution: unstable Urgency: high Maintainer: Stephen Frost [EMAIL PROTECTED] Changed-By: Steve Langasek [EMAIL PROTECTED] Description: libpam-ldap - Pluggable Authentication Module allowing LDAP interfaces Closes: 407746 411545 412649 413448 413539 Changes: libpam-ldap (180-1.7) unstable; urgency=high . * Non-maintainer upload. * High-urgency upload for RC bugfix. * Check for both 'host' and 'uri' in the existing pam_ldap.conf, so that uri entries aren't incorrectly discarded on upgrade. Also handle ldapi:/// URIs in the postinst, rather than mistaking this for a host entry. Closes: #407746. * Use ldapi:/// as the default server value, not 127.0.0.1, since ldapi is going to be more efficient than tcp * Incorporate a postinst fix from libnss-ldap, so updates will preferentially be made to the first *uncommented* instance of the option in pam_ldap.conf, not just the first instance. * Incorporate updated debconf templates from libnss-ldap where appropriate; thanks to Christian Perrier for the assistance. * Debian translations: - Copy translations from libnss-ldap. This adds Catalan, Danish, Spanish, Galician, Norwegian Bokmål, Russian (all incomplete right now) - Include updated Galician translation; thanks to Jacobo Tarrio.
Bug#407746: marked as done (libpam-ldap upgrade breaks pam_ldap.conf and can't login)
Your message dated Sat, 10 Mar 2007 23:02:08 + with message-id [EMAIL PROTECTED] and subject line Bug#407746: fixed in libpam-ldap 180-1.7 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: libpam-ldap Version: 180-1.4 After an apt-get upgrade, the libpam-ldap packate updated, and in doing so it rewrote parts of the /etc/pam_ldap.conf file as follows - rewrote host, base, ldap_version, pam_password - commented out the uri setting. Since I don't use unencrypted logins to my ldap server, and I'm not sure who would do such a thing, this latter step breaks logins to this machine. I've tried dpkg-reconfigure libpam-ldap and there's no option to preserve my URI setting, which I set correctly to ldaps://ldap.mydomain.com, and since I'm using ldaps:// protocol I do not use the host setting. Even if I leave host blank, it will still disable the uri setting - and this is the heart of the issue, I can't avoid breaking my libpam-ldap config. Luckily I have ssh pkey authentication setup, so I can get in to fix, but without that this debian client would be rendered useless. Please consider this critical, I don't want my servers to be rendered inaccessible after upgrading to etch which I hope to do upon release. Thx! ---End Message--- ---BeginMessage--- Source: libpam-ldap Source-Version: 180-1.7 We believe that the bug you reported is fixed in the latest version of libpam-ldap, which is due to be installed in the Debian FTP archive: libpam-ldap_180-1.7.diff.gz to pool/main/libp/libpam-ldap/libpam-ldap_180-1.7.diff.gz libpam-ldap_180-1.7.dsc to pool/main/libp/libpam-ldap/libpam-ldap_180-1.7.dsc libpam-ldap_180-1.7_i386.deb to pool/main/libp/libpam-ldap/libpam-ldap_180-1.7_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. Steve Langasek [EMAIL PROTECTED] (supplier of updated libpam-ldap 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: Fri, 9 Mar 2007 02:35:03 -0800 Source: libpam-ldap Binary: libpam-ldap Architecture: source i386 Version: 180-1.7 Distribution: unstable Urgency: high Maintainer: Stephen Frost [EMAIL PROTECTED] Changed-By: Steve Langasek [EMAIL PROTECTED] Description: libpam-ldap - Pluggable Authentication Module allowing LDAP interfaces Closes: 407746 411545 412649 413448 413539 Changes: libpam-ldap (180-1.7) unstable; urgency=high . * Non-maintainer upload. * High-urgency upload for RC bugfix. * Check for both 'host' and 'uri' in the existing pam_ldap.conf, so that uri entries aren't incorrectly discarded on upgrade. Also handle ldapi:/// URIs in the postinst, rather than mistaking this for a host entry. Closes: #407746. * Use ldapi:/// as the default server value, not 127.0.0.1, since ldapi is going to be more efficient than tcp * Incorporate a postinst fix from libnss-ldap, so updates will preferentially be made to the first *uncommented* instance of the option in pam_ldap.conf, not just the first instance. * Incorporate updated debconf templates from libnss-ldap where appropriate; thanks to Christian Perrier for the assistance. * Debian translations: - Copy translations from libnss-ldap. This adds Catalan, Danish, Spanish, Galician, Norwegian Bokmål, Russian (all incomplete right now) - Include updated Galician translation; thanks to Jacobo Tarrio. Closes: #412649. - Include updated Brazilian Portuguese translation; thanks to André Luis Lopes. Closes: #411545. - Include updated German translation; thanks to Matthias Julius. Closes: #413448. - Include updated Czech translation; thanks to Miroslave Kure. Closes: #413539. - Include updated Dutch translation; thanks to Bart Cornelis. * Use debconf substitutions for package name and file name in templates; no direct benefit to this package alone, but allows translators to translate the same string only once for libpam-ldap and libnss-ldap. Files: 9101e2ad224596f996837b64ea58fd7c 633 admin extra libpam-ldap_180-1.7.dsc
Bug#411922: marked as done (FW: libpam-ldap upgrade breaks pam_ldap.conf and can't login)
Your message dated Sat, 10 Mar 2007 23:02:08 + with message-id [EMAIL PROTECTED] and subject line Bug#407746: fixed in libpam-ldap 180-1.7 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: libpam-ldap Version: 180-1.6 3rd report - can we please get an acknowledgement from somebody? The package is still broken in how it handles existing settings upon upgrades, and these settings are critical to authentication working. -Original Message- From: Jamie ffolliott [mailto:[EMAIL PROTECTED] Sent: Monday, February 05, 2007 11:00 PM To: 'debian-release@lists.debian.org' Cc: '[EMAIL PROTECTED]'; '[EMAIL PROTECTED]' Subject: FW: libpam-ldap upgrade breaks pam_ldap.conf and can't login Package: libpam-ldap Version: 180-1.5 I've sent the following email and did not receive a response from the libpam-ldap maintainer. I've upgraded another sarge box since and confirmed the bug still exists. This is a serious problem for upgrades from sarge, or any package update, so please fix it before release. -Original Message- From: Jamie ffolliott [mailto:[EMAIL PROTECTED] Sent: Saturday, January 20, 2007 5:59 PM To: '[EMAIL PROTECTED]' Subject: libpam-ldap upgrade breaks pam_ldap.conf and can't login Package: libpam-ldap Version: 180-1.4 After an apt-get upgrade, the libpam-ldap packate updated, and in doing so it rewrote parts of the /etc/pam_ldap.conf file as follows - rewrote host, base, ldap_version, pam_password - commented out the uri setting, which is an alternative setting to host that supports ldap over ssl. Since I don't use unencrypted logins to my ldap server, and I'm not sure who would do such a thing, I cannot use the host setting. The latter step that comments out uri in fact breaks authentication to this machine. I've tried dpkg-reconfigure libpam-ldap and there's no option to preserve my URI setting, which must be set to ldaps://ldap.mydomain.com for logins to succeed. Even if I leave host blank, it will still disable the uri setting - and this is the heart of the issue, I can't avoid breaking the existing libpam-ldap config. Luckily I have ssh's pub key authentication setup, so I can get in to fix, but without that this debian client would be rendered useless upon upgrade from sarge to etch. Please consider this critical, I don't want all my servers to be rendered inaccessible after upgrading to etch which I hope to do upon release. It locks out access to the box completely. Thx! ---End Message--- ---BeginMessage--- Source: libpam-ldap Source-Version: 180-1.7 We believe that the bug you reported is fixed in the latest version of libpam-ldap, which is due to be installed in the Debian FTP archive: libpam-ldap_180-1.7.diff.gz to pool/main/libp/libpam-ldap/libpam-ldap_180-1.7.diff.gz libpam-ldap_180-1.7.dsc to pool/main/libp/libpam-ldap/libpam-ldap_180-1.7.dsc libpam-ldap_180-1.7_i386.deb to pool/main/libp/libpam-ldap/libpam-ldap_180-1.7_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. Steve Langasek [EMAIL PROTECTED] (supplier of updated libpam-ldap 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: Fri, 9 Mar 2007 02:35:03 -0800 Source: libpam-ldap Binary: libpam-ldap Architecture: source i386 Version: 180-1.7 Distribution: unstable Urgency: high Maintainer: Stephen Frost [EMAIL PROTECTED] Changed-By: Steve Langasek [EMAIL PROTECTED] Description: libpam-ldap - Pluggable Authentication Module allowing LDAP interfaces Closes: 407746 411545 412649 413448 413539 Changes: libpam-ldap (180-1.7) unstable; urgency=high . * Non-maintainer upload. * High-urgency upload for RC bugfix. * Check for both 'host' and 'uri' in the existing pam_ldap.conf, so that uri entries aren't incorrectly discarded on upgrade. Also handle ldapi:/// URIs in the postinst, rather than mistaking this for a host entry. Closes: #407746. * Use ldapi:/// as the default server value, not 127.0.0.1, since ldapi is going to be more efficient than tcp * Incorporate a postinst fix from libnss-ldap, so updates
Bug#413469: ion3: The package is outdated
David, On Sat, Mar 10, 2007 at 10:26:20AM -0500, David A. Harding wrote: On Fri, Mar 09, 2007 at 05:06:50PM -0800, Steve Langasek wrote: After discussing on IRC with Joey and other ion users, it seems that there isn't really much demand for ion3 in a stable release after all; I run ion3 on Sarge and would like to upgrade to a more recent release (development snapshot or not) when Etch is released. Tuomo, the author of IonWM and the original bugreport, is probably correct in his assement of the flaws of megafreeze distributions[1] (like Debian), but I'm happy with Debian's implimentation of such, and I prefer that you not break Debian's release model by not distributing ion3 in Etch. [1] http://modeemi.fi/~tuomov/b/archives/2007/03/03/T19_15_26/ If ion3 passes the technical, legal, and other tests Debian policy requires for the benefit of it's users, ion3 should be, I belive, in Etch. I'm upset you're removing it because you talked to a very small subset of the Debian and IonWM using communities, and they didn't ``demand'' it in Etch or future stable releases. I have pointed out one technical test that the package fails: it does not provide a smooth upgrade path from sarge to etch for users. Another test is that we must be able to support the package for security and other bugs of release-critical severity. Well, the package has been orphaned, upstream doesn't want to support it, and all the developers I've spoken with agree that there's no interest in maintaining it for stable, so the support this package would have is dubious at best. So there is a real doubt that the package meets Debian's standards of quality for a stable release. Without a maintainer to vouch for it, I'm not going to disagree here. -- 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]
Processed: tagging bugs that are closed by packages in NEW as pending
Processing commands for [EMAIL PROTECTED]: # the following bugs are closed by packages in NEW # tags 397350 pending Bug#397350: ITP: vdr-xineliboutput -- Simple framebuffer and/or X11 front-end for VDR There were no tags set. Tags added: pending tags 401603 pending Bug#401603: d-i: i386 netinst installgui fails to boot due to broken file attribs in /dev There were no tags set. Tags added: pending tags 402276 pending Bug#402276: debian-installer: memory requirements on help page F2 There were no tags set. Tags added: pending tags 403195 pending Bug#403195: installation: Finnish timezone not selected by the etch installer Tags were: l10n Tags added: pending tags 403895 pending Bug#403895: installation-report: Fails to detect SCSI CD-ROM There were no tags set. Tags added: pending tags 404485 pending Bug#404485: please support tga framebuffer in the installer for alpha There were no tags set. Tags added: pending tags 405846 pending Bug#405846: ITP: vdr-plugin-solitaire -- VDR plugin providing the card game Solitaire There were no tags set. Tags added: pending tags 405850 pending Bug#405850: ITP: vdr-plugin-sudoku -- VDR plugin that provides Sudokus There were no tags set. Tags added: pending tags 405853 pending Bug#405853: ITP: vdr-plugin-spider -- VDR plugin providing the card game Spider Arachnid There were no tags set. Tags added: pending tags 408535 pending Bug#408535: please provide linux,initrd.gz,etc for gtk-miniiso Tags were: patch Tags added: pending tags 409522 pending Bug#409522: drupal-4.7: New upstream version : Drupal 5.x There were no tags set. Tags added: pending tags 409747 pending Bug#409747: d-i build system doesn't work with new apex-nslu2 1.4.14 Tags were: d-i Tags added: pending tags 413764 pending Bug#413764: [INTL:gl] Galician debconf templates translation for drupal Tags were: l10n patch Tags added: pending tags 413798 pending Bug#413798: [l10n] Czech translation of drupal debconf messages Tags were: l10n patch Tags added: pending tags 413824 pending Bug#413824: [INTL:ta] debconf PO translations for the package drupal Tags were: l10n patch Tags added: pending tags 413891 pending Bug#413891: drupal: [INTL:de] updated German debconf translation Tags were: l10n patch Tags added: pending tags 413905 pending Bug#413905: drupal: [INTL:pt] Updated Portuguese translation for debconf messages Tags were: l10n patch Tags added: pending tags 413966 pending Bug#413966: drupal: [INTL:eu] bsaqeu debconf translation Tags were: l10n patch Tags added: pending tags 414063 pending Bug#414063: drupal: [INTL:ru] Initial Russian debconf templates translation Tags were: l10n patch Tags added: pending tags 414262 pending Bug#414262: ITP: clive -- Video extraction utility for YouTube and Google Video There were no tags set. Tags added: pending 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#414285: bash builtin printf ignores write errors
On Sat, Mar 10, 2007 at 04:45:52PM +, Richard Kettlewell wrote: Package: bash Version: 2.05b-26 Severity: grave sfere$ type bash bash is hashed (/bin/bash) sfere$ bash -c 'type printf' printf is a shell builtin sfere$ bash -c 'printf spong' /dev/full sfere$ echo $? 0 Compare: sfere$ /usr/bin/printf spong /dev/full /usr/bin/printf: write error: No space left on device sfere$ echo $? 1 Is this the same as (or related to) bug #320036, fixed in bash 3.1-5? -- 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: BUGREPORTERS PLEASE CHECK!
So if anybody happens to read this bugreport, while the problem is still persisting, please try to figure out the following: 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? - Can you figure out why this is so? - Is /etc/init.d/openbsd-inetd possibly not executable? - Is /etc/inetd.conf missing? - Anything else? *t -- Tomas Pospisek http://sourcepole.com - Linux Open Source Solutions -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Processed: Re: libfuse2: please include a versioned shlibs file
Processing commands for [EMAIL PROTECTED]: found 409644 2.5.3-4.3 Bug#409644: libfuse2: please include a versioned shlibs file Bug marked as found in version 2.5.3-4.3. quit 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#409644: libfuse2: please include a versioned shlibs file
found 409644 2.5.3-4.3 quit Frank, The 2.5.3-4.1 NMU of fuse is broken: @@ -77,7 +77,7 @@ dh_compress -Xfusexmp.c dh_fixperms dh_installdebconf - dh_makeshlibs + dh_makeshlibs -V libfuse (= 2.5) dh_installdeb dh_shlibdeps dh_gencontrol The package name is libfuse2, not libfuse, so all binaries built against this version of fuse are uninstallable. (Fortunately, they're also all confined to t-p-u...) Could you please re-NMU with the correct shlibs info? 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#386469: openbsd-inetd: no attempt to stop running inetd?
Le mardi 6 mars 2007 23:00, Mike Young a écrit :
Package: openbsd-inetd
Version: 0.20050402-5
Followup-For: Bug #386469
I'm seeing this same error on an etch update/upgrade today.
my pid for inetd doesn't change during the attempt at install, which
suggests that the preinstall for openbsd-inetd doesn't make any attempt
to stop the preexisting process. (or any attempt that is made, fails)
I'm not familiar with this package specifically, but glancing at the
preinst script I am leaning towards the first hypothesis (we make no
attempt to stop the preexisting process).
The script has:
upgrade_from_old_inetd() {
if [ $2 ] dpkg --compare-versions $2 ge 0.20040915-1; then
return 0
fi
This seems incorrect to me. Even when we upgrade from a previous
version, shouldn't we stop the previous instance?
This does not avoid running the rest of upgrade_from_old_inetd() when
upgrading from any previous versions, it just avoids running it when
upgrading from a version ulterior to 0.20040915-1. These versions handle
stopping the old version in the prerm.
Bug#386469: Debian: failed openbsd-inetd upgrade: plea for more info
On Fri, 9 Mar 2007, Mike Young wrote: I upgraded from 0.20050402-4 to 0.20050402-5 from /var/log/aptitude: [UPGRADE] openbsd-inetd 0.20050402-4 - 0.20050402-5 [...] Let me know if you need anything more. --Mike Young 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 [1] http://snapshot.debian.net/archive/2007/01/07/debian/pool/main/o/openbsd-inetd/openbsd-inetd_0.20050402-4_i386.deb -- 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#414285: bash builtin printf ignores write errors
Steve Langasek writes: On Sat, Mar 10, 2007 at 04:45:52PM +, Richard Kettlewell wrote: sfere$ type bash bash is hashed (/bin/bash) sfere$ bash -c 'type printf' printf is a shell builtin sfere$ bash -c 'printf spong' /dev/full sfere$ echo $? 0 Compare: sfere$ /usr/bin/printf spong /dev/full /usr/bin/printf: write error: No space left on device sfere$ echo $? 1 Is this the same as (or related to) bug #320036, fixed in bash 3.1-5? Don't know. Surely it's a simple case of failing to check for errors on some write, flush or close operation. ttfn/rjk -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#386469: openbsd-inetd: no attempt to stop running inetd?
On Sat, 10 Mar 2007, Filipus Klutiero wrote:
Le mardi 6 mars 2007 23:00, Mike Young a écrit :
Package: openbsd-inetd
Version: 0.20050402-5
Followup-For: Bug #386469
I'm seeing this same error on an etch update/upgrade today.
my pid for inetd doesn't change during the attempt at install, which
suggests that the preinstall for openbsd-inetd doesn't make any attempt
to stop the preexisting process. (or any attempt that is made, fails)
I'm not familiar with this package specifically, but glancing at the
preinst script I am leaning towards the first hypothesis (we make no
attempt to stop the preexisting process).
The script has:
upgrade_from_old_inetd() {
if [ $2 ] dpkg --compare-versions $2 ge 0.20040915-1; then
return 0
fi
This seems incorrect to me. Even when we upgrade from a previous
version, shouldn't we stop the previous instance?
This does not avoid running the rest of upgrade_from_old_inetd() when
upgrading from any previous versions, it just avoids running it when
upgrading from a version ulterior to 0.20040915-1. These versions handle
stopping the old version in the prerm.
(Hello Filipus, cool you're trying to resolve this too - maybe we all
will succeed with joined forces)
If I might add - the regular stopping of the daemon should happen in prerm
anyway which *should* (!) be executed (as far as I know) when the old
package is removed (and before the new installed). From prerm:
if [ -x /etc/init.d/openbsd-inetd ]; then
if [ -x `which invoke-rc.d 2/dev/null` ]; then
invoke-rc.d openbsd-inetd stop || exit $?
else
/etc/init.d/openbsd-inetd stop || exit $?
fi
fi
*t
--
Tomas Pospisek
http://sourcepole.com - Linux Open Source Solutions
Processed: severity of 408548 is grave
Processing commands for [EMAIL PROTECTED]: # Automatically generated email from bts, devscripts version 2.9.27 severity 408548 grave Bug#408548: new location for libnssckbi.so effects evolution Severity set to `grave' from `normal' 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#407746: [URGENT] Please update debconf PO translation for the package libpam-ldap 180-1.7
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 03/10/2007 04:10 AM, Steve Langasek wrote: On Fri, Mar 09, 2007 at 10:13:28PM -0300, Felipe Augusto van de Wiel (faw) wrote: You are noted as the last translator of the debconf translation for libpam-ldap. I took the chance to update it. :) Please, find attached the Brazilian Portuguese updated, with translations headers, tested with msgfmt and podebconf-display-po, it is UTF-8 encoded. I also took the chance to review the entire PO and fix some typos. Merged, thanks. You are welcome. 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, but if it should be under 80 columns, let's change it. :-) I would suggest eliminating the English acronym expansion, and translate as Identificador de Recurso Uniforme (URI) do Servidor LDAP: Let me know if you think this change is ok. Yes, it is. I didn't imagined that approach (and it is a good one). Hmm, also: @@ -328,6 +316,9 @@ ldap://hostname or IP:port/ . ldaps:// or ldapi:// can also be used. The port number is optional. msgstr +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. #. Type: string #. Description s/uma texto/um texto/? Indeed. Could you also fix that? :-) BTW, welcome to the pt_BR l10n team. Cheers, 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 iD8DBQFF81TiCjAO0JDlykYRAvuVAJ96IcPGMJe9ddnL1TCs0V2sXtTLLgCgkhwo jVom2Es+mlht+fmoYm7W6Zg= =S1Ll -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#413901: Please request removal
Jose, please open a bug report against ftp.debian.org requesting the removal of list. Thanks for having maintained this package. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#414292: #414292 - list: postinst failure because of improper group creation
On Sat, 2007-03-10 at 13:22 -0800, Enyc wrote: So far as I can tell that replacement will have similar problems if you have a group-name on the system that starts with 'stats'. E.g. if there is a group called 'statsrem' then the check will still incorrectly not-create-the-stats-group ! Indeed. What about:- stats=`grep ^stats: /etc/group 2/dev/null` instead? I agree ! -- Laurent Bonnaud. http://www.lis.inpg.fr/pages_perso/bonnaud/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#414292: #414292 - list: postinst failure because of improper group creation
On Sun, Mar 11, 2007 at 02:45:42AM +0100, Laurent Bonnaud wrote: On Sat, 2007-03-10 at 13:22 -0800, Enyc wrote: So far as I can tell that replacement will have similar problems if you have a group-name on the system that starts with 'stats'. E.g. if there is a group called 'statsrem' then the check will still incorrectly not-create-the-stats-group ! Indeed. What about:- stats=`grep ^stats: /etc/group 2/dev/null` instead? I agree ! You probably want 'getent group stats' instead... -- 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]
Processed: severity of 408548 is important
Processing commands for [EMAIL PROTECTED]: # Automatically generated email from bts, devscripts version 2.9.27 # S/MIME is an optional feature, does not make the package unusable severity 408548 important Bug#408548: new location for libnssckbi.so effects evolution Severity set to `important' from `grave' 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#414332: fail to build madwifi with gcc 4.1
Package: gcc
Severity: grave
Justification: renders package unusable
/usr/bin/make -C /usr/src/modules/madwifi modules \
KERNELPATH=/lib/modules/2.6.18-4-686/build
KERNELRELEASE=2.6.18-4-686 KERNELCONF=/lib/modules/2.6.18-4-686/build/.config
ATH_RATE=ath_rate/sample
make[2]: Entering directory `/usr/src/modules/madwifi'
Checking requirements... ok.
Checking kernel configuration... ok.
/usr/bin/make -C /lib/modules/2.6.18-4-686/build
SUBDIRS=/usr/src/modules/madwifi modules
built-in:0: internal compiler error: Segmentation fault
Please submit a full bug report,
with preprocessed source if appropriate.
strace log
stat64(/usr/src/linux-headers-2.6.18-4-686/scripts, {st_mode=S_IFDIR|0755,
st_size=4096, ...}) = 0
open(/usr/src/linux-headers-2.6.18-4-686/scripts,
O_RDONLY|O_NONBLOCK|O_LARGEFILE|O_DIRECTORY) = 3
fstat64(3, {st_mode=S_IFDIR|0755, st_size=4096, ...}) = 0
fcntl64(3, F_SETFD, FD_CLOEXEC) = 0
getdents64(3, /* 33 entries */, 4096) = 1136
getdents64(3, /* 0 entries */, 4096)= 0
close(3)= 0
pipe([3, 5])= 0
fork() = 6852
--- SIGCHLD (Child exited) @ 0 (0) ---
sigreturn() = ? (mask now [])
close(5)= 0
read(3, 2.6.18-4-686\n, 200) = 13
read(3, , 187)= 0
close(3)= 0
wait4(-1, [{WIFEXITED(s) WEXITSTATUS(s) == 0}], 0, NULL) = 6852
pipe([3, 5])= 0
fork() = 6854
--- SIGCHLD (Child exited) @ 0 (0) ---
sigreturn() = ? (mask now [])
close(5)= 0
read(3, 2.6.18-4-686\n, 200) = 13
read(3, , 187)= 0
close(3)= 0
wait4(-1, [{WIFEXITED(s) WEXITSTATUS(s) == 0}], 0, NULL) = 6854
rt_sigprocmask(SIG_BLOCK, [HUP INT QUIT TERM XCPU XFSZ], NULL, 8) = 0
fork() = 6856
--- SIGCHLD (Child exited) @ 0 (0) ---
sigreturn() = ? (mask now [HUP INT QUIT TERM
XCPU XFSZ])
rt_sigprocmask(SIG_SETMASK, [], NULL, 8) = 0
wait4(-1, [{WIFEXITED(s) WEXITSTATUS(s) == 0}], 0, NULL) = 6856
rt_sigprocmask(SIG_BLOCK, [HUP INT QUIT TERM XCPU XFSZ], NULL, 8) = 0
fork() = 6857
--- SIGCHLD (Child exited) @ 0 (0) ---
sigreturn() = ? (mask now [HUP INT QUIT TERM
XCPU XFSZ])
rt_sigprocmask(SIG_SETMASK, [], NULL, 8) = 0
wait4(-1, [{WIFEXITED(s) WEXITSTATUS(s) == 0}], 0, NULL) = 6857
rt_sigprocmask(SIG_BLOCK, [HUP INT QUIT TERM XCPU XFSZ], NULL, 8) = 0
rt_sigprocmask(SIG_SETMASK, [], NULL, 8) = 0
pipe([3, 5])= 0
fork() = 6859
--- SIGCHLD (Child exited) @ 0 (0) ---
sigreturn() = ? (mask now [])
close(5)= 0
read(3, 2.6.18-4-686\n, 200) = 13
read(3, , 187)= 0
close(3)= 0
wait4(-1, [{WIFEXITED(s) WEXITSTATUS(s) == 0}], 0, NULL) = 6859
pipe([3, 5])= 0
fork() = 6861
--- SIGCHLD (Child exited) @ 0 (0) ---
sigreturn() = ? (mask now [])
close(5)= 0
read(3, 2.6.18-4-686\n, 200) = 13
read(3, , 187)= 0
close(3)= 0
wait4(-1, [{WIFEXITED(s) WEXITSTATUS(s) == 0}], 0, NULL) = 6861
rt_sigprocmask(SIG_BLOCK, [HUP INT QUIT TERM XCPU XFSZ], NULL, 8) = 0
fork() = 6863
--- SIGCHLD (Child exited) @ 0 (0) ---
sigreturn() = ? (mask now [HUP INT QUIT TERM XCPU
XFSZ])
rt_sigprocmask(SIG_SETMASK, [], NULL, 8) = 0
wait4(-1, [{WIFEXITED(s) WEXITSTATUS(s) == 0}], 0, NULL) = 6863
rt_sigprocmask(SIG_BLOCK, [HUP INT QUIT TERM XCPU XFSZ], NULL, 8) = 0
rt_sigprocmask(SIG_SETMASK, [], NULL, 8) = 0
pipe([3, 5])= 0
fork() = 6864
--- SIGCHLD (Child exited) @ 0 (0) ---
sigreturn() = ? (mask now [])
close(5)= 0
read(3, 2.6.18-4-686\n, 200) = 13
read(3, , 187)= 0
close(3)= 0
wait4(-1, [{WIFEXITED(s) WEXITSTATUS(s) == 0}], 0, NULL) = 6864
pipe([3, 5])= 0
fork() = 6873
--- SIGCHLD (Child exited) @ 0 (0) ---
Bug#413969: asterisk: Fails to start after not being able to find format_mp3.so
Hi, Tzafrir Cohen wrote: Please provide a few more details: dpkg -l asterisk-addons There's no package asterisk-addons. 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 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 Cheers, Srdjan -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#407746: [URGENT] Please update debconf PO translation for the package libpam-ldap 180-1.7
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. but if it should be under 80 columns, let's change it. :-) I would suggest eliminating the English acronym expansion, and translate as Identificador de Recurso Uniforme (URI) do Servidor LDAP: Let me know if you think this change is ok. Yes, it is. I didn't imagined that approach (and it is a good one). Ok, done. Hmm, also: @@ -328,6 +316,9 @@ ldap://hostname or IP:port/ . ldaps:// or ldapi:// can also be used. The port number is optional. msgstr +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. #. Type: string #. Description s/uma texto/um texto/? Indeed. Could you also fix that? :-) And done -- and uploaded. BTW, welcome to the pt_BR l10n team. 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/
Processed: tagging 414170
Processing commands for [EMAIL PROTECTED]: tags 414170 + upstream fixed-upstream Bug#414170: SECURITY: multiple message problem Tags were: security patch Bug#413923: SECURITY: multiple message problem Tags added: upstream, fixed-upstream 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]
Processed: tagging 413922
Processing commands for [EMAIL PROTECTED]: tags 413922 + upstream fixed-upstream Bug#413922: SECURITY: multiple message problem Tags were: patch security Tags added: upstream, fixed-upstream 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#413968: [php-maint] xmlrpc-epi turns out to be libxmlrpc in php
On Sat, Mar 10, 2007 at 06:19:09PM +0100, sean finney wrote: hi paul, On Sun, 2007-03-11 at 03:05 +1100, Paul TBBle Hampson wrote: Would there be any interest in having PHP5 link its xmlrpc extension against a distinct library packaging of xmlrpc-epi? (ie. to avoid the situation which once existed for zlib being statically compiled into various other packages, causing security headaches...) just to clarify, are you proposing that php link against an externally provided xmlrpc-epi library, or are you proposing that php provide its bundled version *as* the xmlrpc-epi library for other apps to use? i'm fairly open to both ideas though i think the former sounds better than the latter, assuming there are no api/abi differences. also, are you volunteering to do the packaging? :) 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... 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. 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. -- --- 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/ --- pgp8YXc3VGmF6.pgp Description: PGP signature
Processed: Confirmed
Processing commands for [EMAIL PROTECTED]: tags 413116 + confirmed Bug#413116: jamvm: missing file: /usr/lib/logging.properties There were no tags set. Tags added: confirmed #In Matthew's name, to control this time 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]
Processed (with 1 errors): Reopen
Processing commands for [EMAIL PROTECTED]: #Reopening to clarify the status of this bug, as just marking as found led to an incoherent status Unknown command or malformed arguments to command. reopen 414045 Bug#414045: libX11: Buffer overflow in XGetPixel(). 'reopen' may be inappropriate when a bug has been closed with a version; you may need to use 'found' to remove fixed versions. Bug reopened, originator not changed. 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]
Processed: severity of 414332 is normal
Processing commands for [EMAIL PROTECTED]: # Automatically generated email from bts, devscripts version 2.9.27 severity 414332 normal Bug#414332: fail to build madwifi with gcc 4.1 Severity set to `normal' from `grave' 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]
Processed: closing 358493
Processing commands for [EMAIL PROTECTED]: # Automatically generated email from bts, devscripts version 2.9.27 close 358493 2.0.3-2 Bug#358493: FTBFS: testsuite failures. 'close' is deprecated; see http://www.debian.org/Bugs/Developer#closing. Bug marked as fixed in version 2.0.3-2, send any further explanations to Falk Hueffner [EMAIL PROTECTED] 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]
