Bug#301141: liblablgtk2-ocaml: Fails to install because of wrong dependency on ocaml-base-3.08
On Thu, Mar 24, 2005 at 08:39:04AM +0100, Sven Luther wrote: On Thu, Mar 24, 2005 at 12:56:42AM +0100, Bas Kloet wrote: Package: liblablgtk2-ocaml Version: 2.4.0+2004.11.19-3 Severity: grave Justification: renders package unusable This package depends on ocaml-base-3.08, but it should simply depend on ocaml-base. This renders it uninstallable. Please, did you read the ocaml changelog ? The ocaml-base-3.08 is there on purpose, and it shoulod most defenitively be there, since ocaml releases are binary incompatible, forcing us to do a full rebuild each time a new version is released. This is currently underway, and i uploaded the fixed lablgtk2 yesterday evening after dinstall, so it should show up in the archive this evening. It was a wee bit too early, and it failed to build on hppa, ia64 and s390, because the lablgl dependency altough built, failed to upload in time. If you don't feel like getting such random breakages of unstable, just run testing :) Closing this bug which is not really a bug but a feature. Well, it still is a bug in unstable, even if we (the ocaml maintainers) know that it is only transitory. I have already tagged the bug report as pending and the RM has tagged it as sid , but I don't think it should be closed until a new liblablgtk2-ocaml is uploaded which is installable with ocaml-* from unstable. -Ralf. -- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#301141: liblablgtk2-ocaml: Fails to install because of wrong dependency on ocaml-base-3.08
On Thu, Mar 24, 2005 at 09:10:57AM +0100, Ralf Treinen wrote: Well, it still is a bug in unstable, even if we (the ocaml maintainers) know that it is only transitory. I have already tagged the bug report as pending and the RM has tagged it as sid , but I don't think it should be closed until a new liblablgtk2-ocaml is uploaded which is installable with ocaml-* from unstable. Well, according to the upload log lablgtk2 has already been uploaded and is installable. So it is appropriate to close this bug report. Cheers. -- Stefano Zacchiroli -*- Computer Science PhD student @ Uny Bologna, Italy [EMAIL PROTECTED],debian.org,bononia.it} -%- http://www.bononia.it/zack/ If there's any real truth it's that the entire multidimensional infinity of the Universe is almost certainly being run by a bunch of maniacs. -!- signature.asc Description: Digital signature
Bug#301141: liblablgtk2-ocaml: Fails to install because of wrong dependency on ocaml-base-3.08
On Thu, Mar 24, 2005 at 09:10:57AM +0100, Ralf Treinen wrote: On Thu, Mar 24, 2005 at 08:39:04AM +0100, Sven Luther wrote: On Thu, Mar 24, 2005 at 12:56:42AM +0100, Bas Kloet wrote: Package: liblablgtk2-ocaml Version: 2.4.0+2004.11.19-3 Severity: grave Justification: renders package unusable This package depends on ocaml-base-3.08, but it should simply depend on ocaml-base. This renders it uninstallable. Please, did you read the ocaml changelog ? The ocaml-base-3.08 is there on purpose, and it shoulod most defenitively be there, since ocaml releases are binary incompatible, forcing us to do a full rebuild each time a new version is released. This is currently underway, and i uploaded the fixed lablgtk2 yesterday evening after dinstall, so it should show up in the archive this evening. It was a wee bit too early, and it failed to build on hppa, ia64 and s390, because the lablgl dependency altough built, failed to upload in time. If you don't feel like getting such random breakages of unstable, just run testing :) Closing this bug which is not really a bug but a feature. Well, it still is a bug in unstable, even if we (the ocaml maintainers) know that it is only transitory. I have already tagged the bug report as pending and the RM has tagged it as sid , but I don't think it should be closed until a new liblablgtk2-ocaml is uploaded which is installable with ocaml-* from unstable. Its already in the incoming queue, and on the PTS, so ican be closed. The bug came after the upload, so i couldn't close it in the changelog. There was another bug report against lablgtk2 i think where ia laso replied, so he didn't check. Friendly, Sven Luther -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Processed: tagging 277619
Processing commands for [EMAIL PROTECTED]: # requested by vorlon tags 277619 + sarge-ignore Bug#277619: [fixed for 2.0] openoffice.org: deletes files when /tmp is full Tags were: fixed-upstream Tags added: sarge-ignore 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#295131: JFTR: sdl(glib2.0) vs. wx2.4(glib1.2) only affects scorched3d
Hi! zion:~# apt-cache showpkg libsdl-mixer1.2 libsdl-net1.2 libsdl1.2debian-all | grep '^ ' | sort -u | cut -d ',' -f 1 /tmp/sdldeps zion:~# apt-cache showpkg libwxgtk2.4 | grep '^ ' | sort -u | cut -d ',' -f 1 /tmp/wxdeps zion:~# diff -u /tmp/sdldeps /tmp/wxdeps | grep '^ ' scorched3d zion:~# It seems that this conflict only affects scorched3d. Is there a possibility to check for these things on a global level? Regards, David -- - hallo... wie gehts heute? - *hust* gut *rotz* *keuch* - gott sei dank kommunizieren wir über ein septisches medium ;) -- Matthias Leeb, Uni f. angewandte Kunst, 2005-02-15
Bug#301192: avalon-framework: FTBFS: Missing Build-Depends on junit
Package: avalon-framework Severity: serious Tags: patch The attached patch adds the necessary Build-Depends on junit. It also adds /usr/share/java/junit.jar to the CLASSPATH in debian/rules. Without these changes the package FTBFS. The patch also updates the Build-Depends from j2sdk1.3 to j2sdk1.4, because j2sdk1.3 is not available on some architectures. The jdk_dirs in debian/rules are changed accordingly. Regards Andreas Jochens diff -urN ../tmp-orig/avalon-framework-4.1.2/debian/control ./debian/control --- ../tmp-orig/avalon-framework-4.1.2/debian/control 2005-03-24 11:14:08.398624885 +0100 +++ ./debian/control2005-03-24 11:13:06.936508820 +0100 @@ -2,7 +2,7 @@ Section: contrib/libs Priority: optional Maintainer: Takashi Okamoto [EMAIL PROTECTED] -Build-Depends-Indep: debhelper ( 3.0.0),liblogkit-java, libxerces-java, ant, liblog4j, libxalan2-java, j2sdk1.3 +Build-Depends-Indep: debhelper, junit, liblogkit-java, libxerces-java, ant, liblog4j, libxalan2-java, j2sdk1.4 Standards-Version: 3.5.2 Package: libavalon-framework-java diff -urN ../tmp-orig/avalon-framework-4.1.2/debian/rules ./debian/rules --- ../tmp-orig/avalon-framework-4.1.2/debian/rules 2005-03-24 11:14:08.398624885 +0100 +++ ./debian/rules 2005-03-24 11:07:35.0 +0100 @@ -15,13 +15,13 @@ export LANG=C export VERSION=4.1.2 -jdk_dirs:=/usr/lib/j2se/1.3 /usr/lib/j2sdk1.3 +jdk_dirs:=/usr/lib/j2sdk1.4-sun /usr/lib/j2sdk1.4-blackdown /usr/lib/j2sdk1.4-ibm export JAVA_HOME=$(shell for jdir in $(jdk_dirs); do if [ -d $$jdir ]; then echo $$jdir; exit 0; fi; done) export ANT=/usr/bin/ant -CLASSPATH=/usr/share/kaffe/Klasses.jar:/usr/share/java/logkit.jar:/usr/share/java/xerces.jar:/usr/share/java/log4j.jar:/usr/share/java/xalan2.jar:. +CLASSPATH=/usr/share/kaffe/Klasses.jar:/usr/share/java/junit.jar:/usr/share/java/logkit.jar:/usr/share/java/xerces.jar:/usr/share/java/log4j.jar:/usr/share/java/xalan2.jar:. build: build-stamp -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#267101: Please close
Hi! Since termpkg is not in Debian any more, can you please close this bug? Thanks, Martin -- Martin Pitt http://www.piware.de Ubuntu Developerhttp://www.ubuntulinux.org Debian Developer http://www.debian.org signature.asc Description: Digital signature
Bug#301193: sylpheed: buffer overflow bug in 0.8.0 - 1.0.3, 1.9.0 - 1.9.4
Package: sylpheed Severity: critical Justification: security hole, buffer overflow Tags: security, sarge, sid, experimental According upstream: A buffer overflow which occurred when displaying a message with attachments which have MIME-encoded filenames was fixed. This is fixed in 1.0.4, to be uploaded ASAP. Upstream report: http://www.tmtm.org/cgi-bin/w3ml/sylpheed/msg/24429 -- System Information: Debian Release: 3.1 APT prefers unstable APT policy: (500, 'unstable') Architecture: i386 (x86_64) Kernel: Linux 2.6.8-9-amd64-k8 Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968) -- Ricardo Mones Lastra - [EMAIL PROTECTED] Centro de Inteligencia Artificial, Universidad de Oviedo en Gijon 33271 Asturias, SPAIN. - http://www.aic.uniovi.es/mones -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#300166: marked as done ([powerpc] no console after initial install, maybe udev related.)
Your message dated Thu, 24 Mar 2005 03:32:17 -0800 with message-id [EMAIL PROTECTED] and subject line [powerpc] no console after initial install, maybe udev related. 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) -- Received: (at submit) by bugs.debian.org; 18 Mar 2005 06:02:46 + From [EMAIL PROTECTED] Thu Mar 17 22:02:46 2005 Return-path: [EMAIL PROTECTED] Received: from smtp11.wanadoo.fr [193.252.22.31] by spohr.debian.org with esmtp (Exim 3.35 1 (Debian)) id 1DCAZJ-00025a-00; Thu, 17 Mar 2005 22:02:46 -0800 Received: from me-wanadoo.net (localhost [127.0.0.1]) by mwinf1108.wanadoo.fr (SMTP Server) with ESMTP id 64BA41C00090; Fri, 18 Mar 2005 07:02:14 +0100 (CET) Received: from pegasos (AStrasbourg-251-1-59-16.w82-126.abo.wanadoo.fr [82.126.135.16]) by mwinf1108.wanadoo.fr (SMTP Server) with ESMTP id 40DF41C00082; Fri, 18 Mar 2005 07:02:14 +0100 (CET) X-ME-UUID: [EMAIL PROTECTED] Received: from luther by pegasos with local (Exim 4.44) id 1DCAKg-0001b5-69; Fri, 18 Mar 2005 06:47:38 +0100 Date: Fri, 18 Mar 2005 06:47:38 +0100 To: Rick_Thomas [EMAIL PROTECTED] Cc: Holger Levsen [EMAIL PROTECTED], debian-boot@lists.debian.org, [EMAIL PROTECTED] Subject: Re: 3 days until end of test period Message-ID: [EMAIL PROTECTED] References: [EMAIL PROTECTED] [EMAIL PROTECTED] [EMAIL PROTECTED] [EMAIL PROTECTED] Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline In-Reply-To: [EMAIL PROTECTED] User-Agent: Mutt/1.5.6+20040907i From: Sven Luther [EMAIL PROTECTED] Delivered-To: [EMAIL PROTECTED] X-Spam-Checker-Version: SpamAssassin 2.60-bugs.debian.org_2005_01_02 (1.212-2003-09-23-exp) on spohr.debian.org X-Spam-Status: No, hits=-8.0 required=4.0 tests=BAYES_00,HAS_PACKAGE autolearn=no version=2.60-bugs.debian.org_2005_01_02 X-Spam-Level: Package: debian-installer severity: grave On Fri, Mar 18, 2005 at 12:34:33AM -0500, Rick_Thomas wrote: I tried it on a 350MHz G4 PowerMac (NewWorld) at the office. All went well except for one strangeness. Since the same thing happened on my beige G3 last night, I'm curious if anyone else has seen it? Cool Last night I thought it was just a glitch -- the beige G3 hardware is sometimes a little flaky. But now I'm not so sure. The G4 machine has always been solid as a rock, hardware-wise. The weirdness is this: Installing with the 2.6.8 kernel (single processor version, if it matters) The initial reboot goes just fine, and drops me into tasksel, where I select print server, and desktop environment. All the installation and setup stuff goes as expected, but when everything is over and I try to log out, I never get a login: prompt or a Gnome login window. If I switch to another virtual console (alt-F2) and try to login there it accepts my login and password, but I never get a shell prompt. I had this also, but a reboot solved it. I had to go to another machine and do ssh [EMAIL PROTECTED] /sbin/reboot because using slogin [EMAIL PROTECTED] got me the point where I enter my root password, then the same hang as I saw on the second virtual console. Sound familiar? What am I doing wrong? Don't know once is a coincidence, but 3 times is a problem, which i believe is RC. We should fill a bug, but i don't know what package to fill it at, let's say the installer for now. Friendly, Sven Luther --- Received: (at 300166-done) by bugs.debian.org; 24 Mar 2005 11:32:18 + From [EMAIL PROTECTED] Thu Mar 24 03:32:18 2005 Return-path: [EMAIL PROTECTED] Received: from dsl093-039-086.pdx1.dsl.speakeasy.net (localhost.localdomain) [66.93.39.86] by spohr.debian.org with esmtp (Exim 3.35 1 (Debian)) id 1DEQZV-0002Ug-00; Thu, 24 Mar 2005 03:32:18 -0800 Received: by localhost.localdomain (Postfix, from userid 1000) id 34C2D171D21; Thu, 24 Mar 2005 03:32:17 -0800 (PST) Date: Thu, 24 Mar 2005 03:32:17 -0800 From: Steve Langasek [EMAIL PROTECTED] To: [EMAIL PROTECTED] Subject: Re: [powerpc] no console after initial install, maybe udev related. Message-ID: [EMAIL PROTECTED] Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol=application/pgp-signature; boundary=xHFwDpU9dbj6ez1V Content-Disposition: inline User-Agent: Mutt/1.5.6+20040907i Delivered-To: [EMAIL PROTECTED] X-Spam-Checker-Version: SpamAssassin 2.60-bugs.debian.org_2005_01_02
Bug#301195: /usr/bin/mcedit-debian: mcedit-debian becomes default editor without confirmation
Package: mc Version: 1:4.6.0-4.6.1-pre3-1 Severity: serious File: /usr/bin/mcedit-debian Justification: unknown;/etc should not be overwritten Stefano, thank you for your work on the mc package. Today I found out that somehow the latest upgrade of the mc package must have overwritten the alternative I specified for editor. Previously I used nano, it was changed to mcedit-debian without my consent or confirmation. I cannot quote the exact place from the Debian Policy Manual but AFAIK things in /etc should not be over- written without confirmation. Thus marking the bug as serious because it violates policy. Best Rolf -- System Information: Debian Release: 3.1 APT prefers testing APT policy: (500, 'testing') Architecture: i386 (i686) Kernel: Linux 2.4.26.desktop041204 Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Versions of packages mc depends on: ii libc6 2.3.2.ds1-20 GNU C Library: Shared libraries an ii libglib2.0-02.6.3-1 The GLib library of C routines ii libgpmg11.19.6-19General Purpose Mouse - shared lib -- no debconf information -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#299605: libapache-mod-php4 crashes in __kernel_vsyscall
Raoul, On Tue, Mar 15, 2005 at 11:00:23AM +0100, raoul bhatia wrote: Package: libapache-mod-php4 Version: 4:4.3.10-9 Severity: critical apache crashes with the log different entries in /var/log/apache/error.log: ssl enabled: [Sun Mar 13 10:15:52 2005] [notice] child pid 23162 exit signal Segmentation fault (11) ssl disabled: free(): invalid pointer 0x8186fb0! [Tue Mar 15 10:21:42 2005] [notice] child pid 16078 exit signal Segmentation fault (11) i could narrow it down to the software package horde, which cannot be accessed via web. the corresponding apache child simply segfaults. all other vhosts run as expected. in my opintion, this started to occure after upgrading the testing distrubition and using libapache-mod-php4 from testing. Please test with the 4.3.10-10 version of libapache-mod-php4 which has just been uploaded to unstable (available for the next few hours from http://incoming.debian.org/), and let us know if you still see this failure. Thanks, -- Steve Langasek postmodern programmer signature.asc Description: Digital signature
Processed: severity of 301193 is grave
Processing commands for [EMAIL PROTECTED]: # Automatically generated email from bts, devscripts version 2.8.10 severity 301193 grave Bug#301193: sylpheed: buffer overflow bug in 0.8.0 - 1.0.3, 1.9.0 - 1.9.4 Severity set to `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#300842: libc6: a workaround
Package: libc6 Version: 2.3.4-1 Followup-For: Bug #300842 I had the same problem. A workaround, if you still have an open terminal somewhere, is (bash syntax) : export LD_ASSUME_KERNEL=2.4.1 Then you should be able to finish installing libc6 and libc6-686 and the bug will disappear. Regards, Vincent -- System Information: Debian Release: 3.1 APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: i386 (i686) Kernel: Linux 2.6.12-rc1-mm1 Locale: LANG=C, LC_CTYPE=fr_FR.ISO-8859-1 (charmap=ISO-8859-1) Versions of packages libc6 depends on: ii libdb1-compat 2.1.3-7The Berkeley database routines [gl -- no debconf information -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#267101: Please close
* Martin Pitt [EMAIL PROTECTED] [2005-03-24 12:39]: Since termpkg is not in Debian any more, can you please close this bug? It seems it's still there? Or is this another package? 13048:[EMAIL PROTECTED]: ~] madison termpkg termpkg | 3.3-1 | unstable | source 13049:[EMAIL PROTECTED]: ~] madison -S termpkg termnet | 3.3-1 | unstable | arm, hppa, i386, ia64, m68k, mips, mipsel, s390, sparc termnetd | 3.3-1 | unstable | arm, hppa, i386, ia64, m68k, mips, mipsel, s390, sparc ttyd | 3.3-1 | unstable | arm, hppa, i386, ia64, m68k, mips, mipsel, s390, sparc termpkg | 3.3-1 | unstable | source -- Martin Michlmayr http://www.cyrius.com/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Processed: Re: Bug#301195: /usr/bin/mcedit-debian: mcedit-debian becomes default editor without confirmation
Processing commands for [EMAIL PROTECTED]: severity 301195 normal Bug#301195: /usr/bin/mcedit-debian: mcedit-debian becomes default editor without confirmation Severity set to `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#301168: wvstreams FTBFS: build-dependency on non-existent package
Steve Langasek [EMAIL PROTECTED] writes: Package: wvstreams Source: wvstreams Version: 4.0.2-1 Severity: serious * Acknowledge NMUs. (Closes: #292618, #297694, #297554, #286593, #289237) * We now depend on XPLC 0.3.11. Lovely. After four consecutive NMUs to try to get the last upstream version into a releasable state, you've just uploaded another new upstream version which has a trivially visible RC bug: build-depending on a version of XPLC that isn't in the archive. Looks like sarge users will have to wait even longer now for fixed modem support. I'll upload a fixed package this morning. Sorry for the breakage. -- Thanks, Jim http://www.student.cs.uwaterloo.ca/~ja2morri/ http://phython.blogspot.com http://open.nit.ca/wiki/?page=jim -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#301200: sylpheed-claws: buffer overflow bug in 0.8.0 - 1.0.3, 1.9.0 - 1.9.4
Package: sylpheed-claws Severity: critical Justification: security hole, buffer overflow Tags: security, sarge, sid, experimental According upstream: A buffer overflow which occurred when displaying a message with attachments which have MIME-encoded filenames was fixed. This is fixed in 1.0.4 (sid/sarge) and 1.9.6 (experimental), to be uploaded ASAP. Please upgrade. Upstream report: http://www.tmtm.org/cgi-bin/w3ml/sylpheed/msg/24429 -- System Information: Debian Release: 3.1 APT prefers unstable APT policy: (500, 'unstable') Architecture: i386 (x86_64) Kernel: Linux 2.6.8-9-amd64-k8 Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968) -- Ricardo Mones Lastra - [EMAIL PROTECTED] Centro de Inteligencia Artificial, Universidad de Oviedo en Gijon 33271 Asturias, SPAIN. - http://www.aic.uniovi.es/mones -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#301204: libpam-ssh: pam-ssh incorrectly re-uses values returned by getpwnam()
Package: libpam-ssh Version: 1.91.0-5 Severity: critical A long time ago (circa 1998 or so) I looked at pam-ssh project and noticied several problems with it. And since it's now in Debian, the same problems applies to Debian too. Here's one. in pam_sm_authenticate() routine, pam_ssh saves struct passwd as a pam variable, this way (error checking removed for simplicitly): pwent = getpwnam(user); ... /* copy the passwd entry (in case successive calls are made) and save it for the session phase */ pwent_keep = malloc(sizeof *pwent); memcpy(pwent_keep, pwent, sizeof *pwent_keep); pam_set_data(pamh, ssh_passwd_entry, pwent_keep, ssh_cleanup); and later, in pam_sm_open_session(), it reuses the entry to create ~/.ssh/... files and to set user IDs: pam_get_data(pamh, ssh_passwd_entry, (const void **)(void *)pwent); openpam_borrow_cred(pamh, pwent); asprintf(per_agent, %s/.ssh/agent-%s, pwent-pw_dir, hname); env_write = open(per_agent, O_CREAT | O_EXCL | O_WRONLY, S_IRUSR); ... struct passwd contains pointers to strings (pw_dir, pw_name etc). So, any call to getpwent() and other getpw*() routines in between pam_sm_authenticate() and pam_sm_open_session() of this module poses a high risk of the strings to be overwritten (or even the whole internal pwent buffer re-allocated), so the module will create files in a wrong place using wrong userid. Luckly, most (depending on the other modules in the PAM stack) getpw* calls will be the same as this module does, and hence the problem will not occur. I pointed this problem out to the author the same time I looked at the module, but instead of an ACK he replied with something like If you don't like my program write your own. Later on, he changed logic a bit -- previously he where saving the pwent pointer, now he saves the whole structure (as pwent_keep), but the same problem is still here. There where other issues with this package at that time, but by now I forgot which ones. -- System Information Debian Release: 3.0 Kernel Version: Linux paltus.tls.msk.ru 2.6.11-k7-0 #1 Wed Mar 2 20:04:17 MSK 2005 i686 GNU/Linux Versions of the packages libpam-ssh depends on: +++-==-==- ii libc6 2.3.2.ds1-16 GNU C Library: Shared libraries and Timezone ii libpam0g 0.76-22Pluggable Authentication Modules library ii libssl0.9.70.9.7e-3 SSL shared libraries -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Processed: severity of 301200 is grave
Processing commands for [EMAIL PROTECTED]: # Automatically generated email from bts, devscripts version 2.8.10 severity 301200 grave Bug#301200: sylpheed-claws: buffer overflow bug in 0.8.0 - 1.0.3, 1.9.0 - 1.9.4 Severity set to `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#301168: marked as done (wvstreams FTBFS: build-dependency on non-existent package)
Your message dated Thu, 24 Mar 2005 08:17:23 -0500 with message-id [EMAIL PROTECTED] and subject line Bug#301168: fixed in wvstreams 4.0.2-2 has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what I am talking about this indicates a serious mail system misconfiguration somewhere. Please contact me immediately.) Debian bug tracking system administrator (administrator, Debian Bugs database) -- Received: (at submit) by bugs.debian.org; 24 Mar 2005 06:31:47 + From [EMAIL PROTECTED] Wed Mar 23 22:31:46 2005 Return-path: [EMAIL PROTECTED] Received: from dsl093-039-086.pdx1.dsl.speakeasy.net (localhost.localdomain) [66.93.39.86] by spohr.debian.org with esmtp (Exim 3.35 1 (Debian)) id 1DELsg-0001im-00; Wed, 23 Mar 2005 22:31:46 -0800 Received: by localhost.localdomain (Postfix, from userid 1000) id B38C3171D21; Wed, 23 Mar 2005 22:31:45 -0800 (PST) Date: Wed, 23 Mar 2005 22:31:45 -0800 From: Steve Langasek [EMAIL PROTECTED] To: [EMAIL PROTECTED] Subject: wvstreams FTBFS: build-dependency on non-existent package Message-ID: [EMAIL PROTECTED] Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol=application/pgp-signature; boundary=24zk1gE8NUlDmwG9 Content-Disposition: inline User-Agent: Mutt/1.5.6+20040907i Delivered-To: [EMAIL PROTECTED] X-Spam-Checker-Version: SpamAssassin 2.60-bugs.debian.org_2005_01_02 (1.212-2003-09-23-exp) on spohr.debian.org X-Spam-Status: No, hits=-8.0 required=4.0 tests=BAYES_00,HAS_PACKAGE autolearn=no version=2.60-bugs.debian.org_2005_01_02 X-Spam-Level: --24zk1gE8NUlDmwG9 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Package: wvstreams Source: wvstreams Version: 4.0.2-1 Severity: serious * Acknowledge NMUs. (Closes: #292618, #297694, #297554, #286593, #28923= 7) * We now depend on XPLC 0.3.11. Lovely. After four consecutive NMUs to try to get the last upstream version into a releasable state, you've just uploaded another new upstream version which has a trivially visible RC bug: build-depending on a version of XPLC that isn't in the archive. Looks like sarge users will have to wait even longer now for fixed modem support. --=20 Steve Langasek postmodern programmer --24zk1gE8NUlDmwG9 Content-Type: application/pgp-signature; name=signature.asc Content-Description: Digital signature Content-Disposition: inline -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.5 (GNU/Linux) iD8DBQFCQl7OKN6ufymYLloRAj9nAKC4uozg3oSzrArH+vtx1ayCnVZf4wCdEYxx pvHNbtBH/mWeBEbNLm5HGug= =SrYV -END PGP SIGNATURE- --24zk1gE8NUlDmwG9-- --- Received: (at 301168-close) by bugs.debian.org; 24 Mar 2005 13:30:18 + From [EMAIL PROTECTED] Thu Mar 24 05:30:18 2005 Return-path: [EMAIL PROTECTED] Received: from newraff.debian.org [208.185.25.31] (mail) by spohr.debian.org with esmtp (Exim 3.35 1 (Debian)) id 1DESPh-0007YJ-00; Thu, 24 Mar 2005 05:30:17 -0800 Received: from katie by newraff.debian.org with local (Exim 3.35 1 (Debian)) id 1DESDD-0006Vl-00; Thu, 24 Mar 2005 08:17:23 -0500 From: James Morrison [EMAIL PROTECTED] To: [EMAIL PROTECTED] X-Katie: $Revision: 1.55 $ Subject: Bug#301168: fixed in wvstreams 4.0.2-2 Message-Id: [EMAIL PROTECTED] Sender: Archive Administrator [EMAIL PROTECTED] Date: Thu, 24 Mar 2005 08:17:23 -0500 Delivered-To: [EMAIL PROTECTED] X-Spam-Checker-Version: SpamAssassin 2.60-bugs.debian.org_2005_01_02 (1.212-2003-09-23-exp) on spohr.debian.org X-Spam-Status: No, hits=-6.0 required=4.0 tests=BAYES_00,HAS_BUG_NUMBER autolearn=no version=2.60-bugs.debian.org_2005_01_02 X-Spam-Level: Source: wvstreams Source-Version: 4.0.2-2 We believe that the bug you reported is fixed in the latest version of wvstreams, which is due to be installed in the Debian FTP archive: libuniconf4.0_4.0.2-2_powerpc.deb to pool/main/w/wvstreams/libuniconf4.0_4.0.2-2_powerpc.deb libwvstreams-dev_4.0.2-2_powerpc.deb to pool/main/w/wvstreams/libwvstreams-dev_4.0.2-2_powerpc.deb libwvstreams4.0-base_4.0.2-2_powerpc.deb to pool/main/w/wvstreams/libwvstreams4.0-base_4.0.2-2_powerpc.deb libwvstreams4.0-doc_4.0.2-2_all.deb to pool/main/w/wvstreams/libwvstreams4.0-doc_4.0.2-2_all.deb libwvstreams4.0-extras_4.0.2-2_powerpc.deb to pool/main/w/wvstreams/libwvstreams4.0-extras_4.0.2-2_powerpc.deb libwvstreams4.0-fft_4.0.2-2_powerpc.deb to pool/main/w/wvstreams/libwvstreams4.0-fft_4.0.2-2_powerpc.deb libwvstreams4.0-qt_4.0.2-2_powerpc.deb to pool/main/w/wvstreams/libwvstreams4.0-qt_4.0.2-2_powerpc.deb libwvstreams4.0-speex_4.0.2-2_powerpc.deb to
Bug#295131: JFTR: sdl(glib2.0) vs. wx2.4(glib1.2) only affects scorched3d
On Thu, Mar 24, 2005 at 11:42:48AM +0100, David Schmitt wrote: zion:~# apt-cache showpkg libsdl-mixer1.2 libsdl-net1.2 libsdl1.2debian-all | grep '^ ' | sort -u | cut -d ',' -f 1 /tmp/sdldeps zion:~# apt-cache showpkg libwxgtk2.4 | grep '^ ' | sort -u | cut -d ',' -f 1 /tmp/wxdeps zion:~# diff -u /tmp/sdldeps /tmp/wxdeps | grep '^ ' scorched3d zion:~# It seems that this conflict only affects scorched3d. Yep since nothing else depends on libwxgtk2.4 and libsdl in the same time. Is there a possibility to check for these things on a global level? Thanks David for checking this. I made further checks and here's what I got: [ sid / unstable ] ([EMAIL PROTECTED])~$ldd /usr/lib/libSDL.so libartsc.so.0 = /usr/lib/libartsc.so.0 (0x40103000) libgmodule-2.0.so.0 = /usr/lib/libgmodule-2.0.so.0 (0x40109000) libgthread-2.0.so.0 = /usr/lib/libgthread-2.0.so.0 (0x4010e000) libglib-2.0.so.0 = /usr/lib/libglib-2.0.so.0 (0x40113000) libesd.so.0 = /usr/lib/libesd.so.0 (0x40193000) libaudiofile.so.0 = /usr/lib/libaudiofile.so.0 (0x4019b000) libaudio.so.2 = /usr/lib/libaudio.so.2 (0x401bf000) libXt.so.6 = /usr/X11R6/lib/libXt.so.6 (0x401d4000) libX11.so.6 = /usr/X11R6/lib/libX11.so.6 (0x40226000) libXext.so.6 = /usr/X11R6/lib/libXext.so.6 (0x402ed000) libvga.so.1 = /usr/lib/libvga.so.1 (0x402fb000) libaa.so.1 = /usr/lib/libaa.so.1 (0x4036) libasound.so.2 = /usr/lib/libasound.so.2 (0x4037c000) libm.so.6 = /lib/libm.so.6 (0x4042f000) libdl.so.2 = /lib/libdl.so.2 (0x40452000) libpthread.so.0 = /lib/libpthread.so.0 (0x40455000) libc.so.6 = /lib/libc.so.6 (0x404a6000) libSM.so.6 = /usr/X11R6/lib/libSM.so.6 (0x405d9000) libICE.so.6 = /usr/X11R6/lib/libICE.so.6 (0x405e2000) libncurses.so.5 = /lib/libncurses.so.5 (0x405fa000) libslang.so.1 = /lib/libslang.so.1 (0x40639000) libgpm.so.1 = /usr/lib/libgpm.so.1 (0x406ac000) /lib/ld-linux.so.2 = /lib/ld-linux.so.2 (0x8000) ([EMAIL PROTECTED])~$ [ sarge / testing ] ([EMAIL PROTECTED])~$ldd /usr/lib/libSDL.so libm.so.6 = /lib/libm.so.6 (0x400ad000) libdl.so.2 = /lib/libdl.so.2 (0x400cf000) libX11.so.6 = /usr/X11R6/lib/libX11.so.6 (0x400d2000) libXext.so.6 = /usr/X11R6/lib/libXext.so.6 (0x4019a000) libpthread.so.0 = /lib/libpthread.so.0 (0x401a8000) libc.so.6 = /lib/libc.so.6 (0x401f9000) /lib/ld-linux.so.2 = /lib/ld-linux.so.2 (0x8000) ([EMAIL PROTECTED])~$ Any reason for such huge disproportions? That's where we got libglib2.0. Scorched3D built on sarge works fine and doesn't link against libglib2.0. I asked some of mine friends using other distros for pasting me output of `ldd /usr/lib/libSDL.so | wc -l` Here are some stats [ we've got in sid 23 ] slackware current - 11 gentoo - 14 (we know this could vary a lot) Also seems that other distros have wxgtk2.4 linked against libglib2.0 and libsdl doesn't linked against any libglib. This way most other distros have scorched3d linked against libglib2.0, but only because wxgtk2.4 and not libsdl. I'm not sure what to do now. Is it possible to link our wxgtk2.4 against glib2.0? Or unlink libsdl from using libglib? regards fEnIo -- ,''`. Bartosz Fenski | mailto:[EMAIL PROTECTED] | pgp:0x13fefc40 | irc:fEnIo : :' : 32-050 Skawina - Glowackiego 3/15 - w. malopolskie - Poland `. `' phone:+48602383548 | proud Debian maintainer and user `- http://skawina.eu.org | jid:[EMAIL PROTECTED] | rlu:172001 signature.asc Description: Digital signature
Bug#241497: RFC and status report: Kernel upgrades for woody-sarge upgrades
Hi all. As many of you may know on some machines users will need to install a current kernel before they will be able to upgrade woody to sarge (or better: glibc of woody to glibc of sarge). I've tried to use the available information to provide the needed files for these kernel upgrades. To my knowledge the affected machines/architecures are currently hppa64, sparc sun4m (only some of them) and 80386. Because of the pain to maintain a kernel backport over the lifetime of sarge we have decided to only offer backports of the needed tools (modutils, module-init-tools and initrd-tools) to use stock sarge kernels on woody. It is planned to upload these files together with some documentation into a upgrade-kernel (or whatever else name the ftpmasters will prefer) directory in the archive. I've prepared the necessary backports and some rudimentary documentation and put it online at http://higgs.djpig.de/upgrade/upgrade-kernel/ We now need people that - test the backports - read/comment on/improve the documentation Gruesse, -- Frank Lichtenheld [EMAIL PROTECTED] www: http://www.djpig.de/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#241497: RFC and status report: Kernel upgrades for woody-sarge upgrades
Frank Lichtenheld wrote: Hi all. As many of you may know on some machines users will need to install a current kernel before they will be able to upgrade woody to sarge (or better: glibc of woody to glibc of sarge). I've tried to use the available information to provide the needed files for these kernel upgrades. To my knowledge the affected machines/architecures are currently hppa64, sparc sun4m (only some of them) and 80386. JFTR, all mips/mipsel subarchitectures are also affected. For those, however, the sarge kernel without userland backports is good enough, because modules aren't needed for basic system operation. Thiemo -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#295131: JFTR: sdl(glib2.0) vs. wx2.4(glib1.2) only affects scorched3d
Le jeudi 24 mars 2005 à 14:37 +0100, Bartosz Fenski aka fEnIo a écrit :
[ sid / unstable ]
([EMAIL PROTECTED])~$ldd /usr/lib/libSDL.so
libartsc.so.0 = /usr/lib/libartsc.so.0 (0x40103000)
libgmodule-2.0.so.0 = /usr/lib/libgmodule-2.0.so.0 (0x40109000)
libgthread-2.0.so.0 = /usr/lib/libgthread-2.0.so.0 (0x4010e000)
libglib-2.0.so.0 = /usr/lib/libglib-2.0.so.0 (0x40113000)
libesd.so.0 = /usr/lib/libesd.so.0 (0x40193000)
libaudiofile.so.0 = /usr/lib/libaudiofile.so.0 (0x4019b000)
libaudio.so.2 = /usr/lib/libaudio.so.2 (0x401bf000)
libXt.so.6 = /usr/X11R6/lib/libXt.so.6 (0x401d4000)
libX11.so.6 = /usr/X11R6/lib/libX11.so.6 (0x40226000)
libXext.so.6 = /usr/X11R6/lib/libXext.so.6 (0x402ed000)
libvga.so.1 = /usr/lib/libvga.so.1 (0x402fb000)
libaa.so.1 = /usr/lib/libaa.so.1 (0x4036)
libasound.so.2 = /usr/lib/libasound.so.2 (0x4037c000)
libm.so.6 = /lib/libm.so.6 (0x4042f000)
libdl.so.2 = /lib/libdl.so.2 (0x40452000)
libpthread.so.0 = /lib/libpthread.so.0 (0x40455000)
libc.so.6 = /lib/libc.so.6 (0x404a6000)
libSM.so.6 = /usr/X11R6/lib/libSM.so.6 (0x405d9000)
libICE.so.6 = /usr/X11R6/lib/libICE.so.6 (0x405e2000)
libncurses.so.5 = /lib/libncurses.so.5 (0x405fa000)
libslang.so.1 = /lib/libslang.so.1 (0x40639000)
libgpm.so.1 = /usr/lib/libgpm.so.1 (0x406ac000)
/lib/ld-linux.so.2 = /lib/ld-linux.so.2 (0x8000)
([EMAIL PROTECTED])~$
[ sarge / testing ]
([EMAIL PROTECTED])~$ldd /usr/lib/libSDL.so
libm.so.6 = /lib/libm.so.6 (0x400ad000)
libdl.so.2 = /lib/libdl.so.2 (0x400cf000)
libX11.so.6 = /usr/X11R6/lib/libX11.so.6 (0x400d2000)
libXext.so.6 = /usr/X11R6/lib/libXext.so.6 (0x4019a000)
libpthread.so.0 = /lib/libpthread.so.0 (0x401a8000)
libc.so.6 = /lib/libc.so.6 (0x401f9000)
/lib/ld-linux.so.2 = /lib/ld-linux.so.2 (0x8000)
([EMAIL PROTECTED])~$
Sarge and sid have the same SDL version. You are basically comparing
libsdl1.2debian-all and libsdl1.2debian-oss.
Any reason for such huge disproportions? That's where we got libglib2.0.
Scorched3D built on sarge works fine and doesn't link against libglib2.0.
That's an indirect dependency (brought by libarts), that you won't see
if you pass --as-needed to ld. However, this is not enough, as users
having libsdl1.2debian-{all,arts} installed will still get this
dependency at runtime, probably leading to segfaults.
Also seems that other distros have wxgtk2.4 linked against libglib2.0 and
libsdl doesn't linked against any libglib.
This way most other distros have scorched3d linked against libglib2.0, but
only because wxgtk2.4 and not libsdl.
This may be because they are building a GTK+2.0 version of libwxgtk2.4.
I'm not sure what to do now. Is it possible to link our wxgtk2.4 against
glib2.0? Or unlink libsdl from using libglib?
I'm afraid there is no miracle solution. Getting wxgtk2.5 to install
together with wxgtk2.4, if possible, would be a good option. IIRC, it's
possible to rebuild WxWidgets 2.4 against GTK+ 2.x, but it requires
changes in the applications because of the move to UTF8.
--
.''`. Josselin Mouette/\./\
: :' : [EMAIL PROTECTED]
`. `'[EMAIL PROTECTED]
`- Debian GNU/Linux -- The power of freedom
Bug#295131: JFTR: sdl(glib2.0) vs. wx2.4(glib1.2) only affects scorched3d
On Thursday 24 March 2005 14:37, Bartosz Fenski aka fEnIo wrote: [analysis skipped] I'm not sure what to do now. Is it possible to link our wxgtk2.4 against glib2.0? Or unlink libsdl from using libglib? I found the cause: libSDL.so from libsdl1.2debian-all links against glib2.0 (and much other stuff) libSDL.so from libsdl1.2debian-alsa: zion:~# ldd /usr/lib/libSDL.so | sort /lib/ld-linux.so.2 = /lib/ld-linux.so.2 (0x8000) libX11.so.6 = /usr/X11R6/lib/libX11.so.6 (0xb7e7c000) libXext.so.6 = /usr/X11R6/lib/libXext.so.6 (0xb7e6e000) libasound.so.2 = /usr/lib/libasound.so.2 (0xb7dba000) libc.so.6 = /lib/tls/libc.so.6 (0xb7c52000) libdl.so.2 = /lib/tls/libdl.so.2 (0xb7d95000) libm.so.6 = /lib/tls/libm.so.6 (0xb7d98000) libpthread.so.0 = /lib/tls/libpthread.so.0 (0xb7d86000) zion:~# scorched3d loads fine for me now, I could start a game (though textures were messed up). Looking at Depends of libsdl1.2debian-*, a Conflicts: libsdl1.2debian-all, libsdl1.2debian-arts would probably help. Regards, David -- - hallo... wie gehts heute? - *hust* gut *rotz* *keuch* - gott sei dank kommunizieren wir ber ein septisches medium ;) -- Matthias Leeb, Uni f. angewandte Kunst, 2005-02-15
Bug#241497: RFC and status report: Kernel upgrades for woody-sarge upgrades
Hi, at this moment I am testing the Debian Installer on a SS5 (sun4m I thougt) cause I wanted a newer kernel then 2.2.20. but it isn't working very well I am willing to test this upgrade-kernel to get a beter kernel and be able to do a woody-sarge upgrade I think I will start with it right afther I finished my test with the debian installer and filled in a report I hope I will be able to help :) Greetings Robin Harmsen [EMAIL PROTECTED] http://www.rharmsen.nl - Original Message - From: Frank Lichtenheld [EMAIL PROTECTED] To: debian-release@lists.debian.org; debian-hppa@lists.debian.org; debian-sparc@lists.debian.org Cc: [EMAIL PROTECTED] Sent: Thursday, March 24, 2005 2:31 PM Subject: RFC and status report: Kernel upgrades for woody-sarge upgrades Hi all. As many of you may know on some machines users will need to install a current kernel before they will be able to upgrade woody to sarge (or better: glibc of woody to glibc of sarge). I've tried to use the available information to provide the needed files for these kernel upgrades. To my knowledge the affected machines/architecures are currently hppa64, sparc sun4m (only some of them) and 80386. Because of the pain to maintain a kernel backport over the lifetime of sarge we have decided to only offer backports of the needed tools (modutils, module-init-tools and initrd-tools) to use stock sarge kernels on woody. It is planned to upload these files together with some documentation into a upgrade-kernel (or whatever else name the ftpmasters will prefer) directory in the archive. I've prepared the necessary backports and some rudimentary documentation and put it online at http://higgs.djpig.de/upgrade/upgrade-kernel/ We now need people that - test the backports - read/comment on/improve the documentation Gruesse, -- Frank Lichtenheld [EMAIL PROTECTED] www: http://www.djpig.de/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#241497: RFC and status report: Kernel upgrades for woody-sarge upgrades
On Thu, Mar 24, 2005 at 02:31:55PM +0100, Frank Lichtenheld wrote: As many of you may know on some machines users will need to install a current kernel before they will be able to upgrade woody to sarge (or better: glibc of woody to glibc of sarge). I've tried to use the available information to provide the needed files for these kernel upgrades. To my knowledge the affected machines/architecures are currently hppa64, sparc sun4m (only some of them) and 80386. It's all hppa machines, not just hppa64. I've prepared the necessary backports and some rudimentary documentation and put it online at http://higgs.djpig.de/upgrade/upgrade-kernel/ I'll give it a try now. -- Next the statesmen will invent cheap lies, putting the blame upon the nation that is attacked, and every man will be glad of those conscience-soothing falsities, and will diligently study them, and refuse to examine any refutations of them; and thus he will by and by convince himself that the war is just, and will thank God for the better sleep he enjoys after this process of grotesque self-deception. -- Mark Twain -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Processed: CAN-2005-0531: Buffer overflow in atm_get_addr
Processing commands for [EMAIL PROTECTED]: tag 296905 +pending Bug#296905: CAN-2005-0531: Buffer overflow in atm_get_addr Tags were: security 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#296905: CAN-2005-0531: Buffer overflow in atm_get_addr
tag 296905 +pending thanks This fix is now in SVN and should appear in kernel-source-2.4.27 2.4.27-9 -- Horms -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Processed: there's a patch to this bug.
Processing commands for [EMAIL PROTECTED]: tags 300703 +patch Bug#300703: autofs: Upgrade fails There were no tags set. Tags added: patch thanks Stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#300168: solution to the unknown type compiler error
Hi Christophe, Is this bug really rendering the package unusable? If not, please downgrade its severity. It'll help us track the RC bugs better. btw, are the examples really needed to make this package work? If it's really a grave bug, i note that in your last reply to this you said that you've fixed examples but you haven't uploaded the package yet. If it's true, this bug needs to be tagged as 'pending'. Hope that helps, Gustavo Franco -- [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#299709: Shall I upload libexif1 to unstable
On Wed, Mar 23, 2005 at 02:14:24AM +0100, Achim Bohnet wrote: Both libkexif1 libkexif0 can co-exist in unstable together and libkexif0 won't be removed until all reverse dependancies are taken care of. That's not true; libkexif0 and libkexif1 are both built from the libkexif source package, so if you upload the experimental version of libkexif to unstable, the old libkexif0 binaries will be removed. Another reason to coordinate the libkexif upload with a showimg update. I contacted Jean-Michel (DD of showimg, cc'ed) Monday last week via mail already. This Monday I've prepare a deb (#300813). No response yet. Hey guys,digikam, showimg and libkexif0 are sitting quite well together in testing. The next step is to upload libkexif1 into unstable so that we can move to the next upstream versions. When Jean-Michel is ready we should (re)upload libkexif to sid together with showimg, rebuild kipi-plguins and digikamimageplugins 0.7.2. I don't think we need to wait for showimg in unstable. Unstable is allowed to be broken and have packages in a half built state. If we wait for coordination across all pacakges we can end up waiting a long time. Given how few packages depend on this library, and given that one of them is already broken, there's probably no reason to hold off on uploading the new libkexif to unstable. Short story: This implies: broken digikam versus maybe will be broken showimg on arch != i386. I was of course tempted but I resisted because I'm not involved in showimg pkging. Long version: digikam 0.7.2, links against libkexif1 and conflicts with kipi-plugins and digikamplugins in sid (linked against libkexif1). Therefore the 'need' to upload libkexif1, and rebuild kipi-plugins and digikamplugins (that link against libkexif1) in one go. [Everything already prepared in http://www.mpe.mpg.de/~ach/debian/experimental (with dist = sid)] I intend to upload libkexif1 and rebuilt kipi-plugins and digkameplugins to unstable. They will all sit in unstable until showimg is uploaded to unstable at which time they can all migrate to testing together. I don't want to wait on this any longer. showimg can catch up when it is ready. Mark
Bug#241497: RFC and status report: Kernel upgrades for woody-sarge upgrades
Hi Matthew, On Thursday, 24 Mar 2005, you wrote: On Thu, Mar 24, 2005 at 02:31:55PM +0100, Frank Lichtenheld wrote: As many of you may know on some machines users will need to install a current kernel before they will be able to upgrade woody to sarge (or better: glibc of woody to glibc of sarge). I've tried to use the available information to provide the needed files for these kernel upgrades. To my knowledge the affected machines/architecures are currently hppa64, sparc sun4m (only some of them) and 80386. It's all hppa machines, not just hppa64. IIRC we did some upgrade tests on hppa(32) at the BSP in Frankfurt in November last year and had no problems with that, but i might be wrong. Frank, could you please confirm this, as i recall you and Uli did these tests Greetings Martin -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#298963: caudium: contains non-free fonts
Hi Marek, The free fonts site that you said is corefonts.sf.net.These fonts aren't free as in DFSG and there's a package at contrib section called 'msttcorefonts', AFAIK the postinst retrieves the fonts from the website. Can't you confirm if caudium works without these and that other font ? If not we can still try the freefont alternatives or just replace the references to these fonts and test. Have you contacted upstream ? If not, please do so and point them to: http://corefonts.sourceforge.net/eula.htm Hope that helps, Gustavo Franco -- [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Processed: patch
Processing commands for [EMAIL PROTECTED]: tags 297769 patch Bug#297769: glibc: sched_setaffinity() provides obsolete interface There were no tags set. Tags added: patch thanks Stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#297769: patch
tags 297769 patch
thanks
The attached patch updates sched_[gs]etaffinity to the new interface
from glibc 2.3.4.
Bastian
--
Phasers locked on target, Captain.
diff -ruN glibc-2.3.2.ds1/debian/changelog glibc-2.3.2.ds1.new/debian/changelog
--- glibc-2.3.2.ds1/debian/changelog2005-03-24 15:16:44.422281391 +
+++ glibc-2.3.2.ds1.new/debian/changelog2005-03-24 12:15:00.113925584
+
@@ -1,3 +1,11 @@
+glibc (2.3.2.ds1-20.1) unstable; urgency=low
+
+ * Bastian Blank [EMAIL PROTECTED]
+
+- Update sched_[gs]etaffinity to new interface. (closes: #297769)
+
+ -- Bastian Blank [EMAIL PROTECTED] Thu, 24 Mar 2005 12:14:44 +
+
glibc (2.3.2.ds1-20) unstable; urgency=high
* GOTO Masanori [EMAIL PROTECTED]
diff -ruN glibc-2.3.2.ds1/debian/patches/00list
glibc-2.3.2.ds1.new/debian/patches/00list
--- glibc-2.3.2.ds1/debian/patches/00list 2005-03-24 15:16:43.559278442
+
+++ glibc-2.3.2.ds1.new/debian/patches/00list 2005-03-24 13:55:17.071976008
+
@@ -116,3 +116,5 @@
s390-pthread-fpic
nptl-pthread-c++
hppa-drop-utimes
+libversion
+sched-update
diff -ruN glibc-2.3.2.ds1/debian/patches/libversion.dpatch
glibc-2.3.2.ds1.new/debian/patches/libversion.dpatch
--- glibc-2.3.2.ds1/debian/patches/libversion.dpatch1970-01-01
00:00:00.0 +
+++ glibc-2.3.2.ds1.new/debian/patches/libversion.dpatch2005-03-24
13:54:58.736966104 +
@@ -0,0 +1,32 @@
+#! /bin/sh -e
+
+# All lines beginning with `# DP:' are a description of the patch.
+# DP: Description: Update library versions
+# DP: Patch author: Bastian Blank [EMAIL PROTECTED]
+# DP: Date: 2005-03-24
+
+PATCHLEVEL=0
+
+if [ $# -ne 2 ]; then
+echo 2 `basename $0`: script expects -patch|-unpatch as argument
+exit 1
+fi
+case $1 in
+-patch) patch -d $2 -f --no-backup-if-mismatch -p$PATCHLEVEL $0;;
+-unpatch) patch -d $2 -f --no-backup-if-mismatch -R -p$PATCHLEVEL $0;;
+*)
+ echo 2 `basename $0`: script expects -patch|-unpatch as argument
+ exit 1
+esac
+exit 0
+
+--- Versions.def 2005-03-24 12:47:59.279008144 +
Versions.def 2005-03-24 13:53:32.651007992 +
+@@ -19,6 +19,7 @@
+ GLIBC_2.3.1
+ GLIBC_2.3.2
+ GLIBC_2.3.3
++ GLIBC_2.3.4
+ %ifdef USE_IN_LIBIO
+ HURD_CTHREADS_0.3
+ %endif
diff -ruN glibc-2.3.2.ds1/debian/patches/sched-update.dpatch
glibc-2.3.2.ds1.new/debian/patches/sched-update.dpatch
--- glibc-2.3.2.ds1/debian/patches/sched-update.dpatch 1970-01-01
00:00:00.0 +
+++ glibc-2.3.2.ds1.new/debian/patches/sched-update.dpatch 2005-03-24
14:27:00.818943936 +
@@ -0,0 +1,224 @@
+#! /bin/sh -e
+
+# All lines beginning with `# DP:' are a description of the patch.
+# DP: Description: Update sched_[gs]et_affinity to new interface
+# DP: Related bugs: 297769
+# DP: Patch author: Bastian Blank [EMAIL PROTECTED]
+# DP: Upstream status: Released
+# DP: Date: 2005-03-24
+
+PATCHLEVEL=0
+
+if [ $# -ne 2 ]; then
+echo 2 `basename $0`: script expects -patch|-unpatch as argument
+exit 1
+fi
+case $1 in
+-patch) patch -d $2 -f --no-backup-if-mismatch -p$PATCHLEVEL $0;;
+-unpatch) patch -d $2 -f --no-backup-if-mismatch -R -p$PATCHLEVEL $0;;
+*)
+ echo 2 `basename $0`: script expects -patch|-unpatch as argument
+ exit 1
+esac
+exit 0
+
+--- posix/sched.h 2005-03-24 12:08:26.376014592 +
posix/sched.h 2005-03-24 12:04:15.878891472 +
+@@ -73,11 +73,12 @@
+
+
+ /* Set the CPU affinity for a task */
+-extern int sched_setaffinity (__pid_t __pid, __const cpu_set_t *__mask)
+- __THROW;
++extern int sched_setaffinity (__pid_t __pid, size_t __cpusetsize,
++__const cpu_set_t *__cpuset) __THROW;
+
+ /* Get the CPU affinity for a task */
+-extern int sched_getaffinity (__pid_t __pid, cpu_set_t *__mask) __THROW;
++extern int sched_getaffinity (__pid_t __pid, size_t __cpusetsize,
++cpu_set_t *__cpuset) __THROW;
+ #endif
+
+ __END_DECLS
+--- sysdeps/generic/sched_getaffinity.c2005-03-24 12:08:26.502995288
+
sysdeps/generic/sched_getaffinity.c2005-03-24 12:00:21.055915184
+
+@@ -1,4 +1,4 @@
+-/* Copyright (C) 2002, 2003 Free Software Foundation, Inc.
++/* Copyright (C) 2002, 2003, 2004 Free Software Foundation, Inc.
+This file is part of the GNU C Library.
+
+The GNU C Library is free software; you can redistribute it and/or
+@@ -23,8 +23,9 @@
+
+ /* Retrieve the CPU affinity mask for a particular process. */
+ int
+-sched_getaffinity (pid, cpuset)
++sched_getaffinity (pid, cpusetsize, cpuset)
+ pid_t pid;
++ size_t cpusetsize;
+ cpu_set_t *cpuset;
+ {
+ __set_errno (ENOSYS);
+--- sysdeps/generic/sched_setaffinity.c2005-03-24 12:08:26.503995136
+
sysdeps/generic/sched_setaffinity.c2005-03-24 12:00:23.306972184
+
+@@ -1,4 +1,4 @@
+-/* Copyright (C) 2002, 2003 Free Software Foundation, Inc.
++/* Copyright (C) 2002, 2003, 2004 Free Software
Bug#299709: Shall I upload libexif1 to unstable
On Thursday 24 March 2005 15:41, Mark Purcell wrote: [...] I intend to upload libkexif1 and rebuilt kipi-plugins and digkameplugins to unstable. They will all sit in unstable until showimg is uploaded to unstable at which time they can all migrate to testing together. I don't want to wait on this any longer. showimg can catch up when it is ready. Okay. I have some cosmetic changes on disk. I'll checkin tonight. Achim Mark -- To me vi is Zen. To use vi is to practice zen. Every command is a koan. Profound to the user, unintelligible to the uninitiated. You discover truth everytime you use it. -- [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#301204: libpam-ssh: pam-ssh incorrectly re-uses values returned by getpwnam()
On Thu, Mar 24, 2005 at 03:55:06PM +0300, Michael Tokarev wrote:
Package: libpam-ssh
Version: 1.91.0-5
Severity: critical
A long time ago (circa 1998 or so) I looked at pam-ssh project and
noticied several problems with it. And since it's now in Debian,
the same problems applies to Debian too.
Here's one.
in pam_sm_authenticate() routine, pam_ssh saves struct passwd as
a pam variable, this way (error checking removed for simplicitly):
Are any other getpwnam()-type functions actually called, allowing the
buffers to be overwritten?
Documentation is not clear about how the fields of the struct are
allocated; a minimal test indicates that they are malloc()ated for the
first call only, but that implementation could change; I don't know if
there are relevant standards, and it may be that it is intentionally
opaque.
It does seem like best-practice would be to copy the entire contents
of the structure, and not just the pointers.
Luckly, most (depending on the other modules in the PAM stack) getpw*
calls will be the same as this module does, and hence the problem
will not occur.
I think you are implying that every libpam module shares memory space
with every other libpam module, which AIUI is incorrect. libpam are
ELF shared objects, and every process that links with such an object
(at runtime) will get its own private copy of the data section, but
the text section will be shared (mmaped, really, it is backed by
disk).
Does your claim still stand? Does *that* module call getpwnam()-type
functions multiple times, without memcpy the pointers, and then reuse
the top-level pointer?
I pointed this problem out to the author the same time I looked at
the module, but instead of an ACK he replied with something like
If you don't like my program write your own. Later on, he changed
logic a bit -- previously he where saving the pwent pointer, now
he saves the whole structure (as pwent_keep), but the same problem
is still here.
Right; it is a static buffer, and multiple calls to getpwnam() return
the same pointer, *and* the pointer structure fields always point to
the same place.
It seems that your request can be easily satisfied by using the
reentrant versions of these functions, like getpwnam_r. I'm including
a test file I've been playing with, which indicates that a patch, if
necessary, would be unintrusive.
Justin
#include unistd.h
#include pwd.h
#include sys/types.h
int main()
{
struct passwd p,q;
char *buf,*buf2;
int buflen=sysconf(_SC_GETPW_R_SIZE_MAX);
buf=(char *)malloc(buflen);
buf2=(char *)malloc(buflen);
struct passwd *v=malloc(sizeof (void *));
//struct passwd *p=getpwnam(pryzbyj);
getpwnam_r(pryzbyj, p, buf, buflen, (struct passwd **)v);
//struct passwd *q=getpwnam(root);
getpwnam_r(root, q, buf2, buflen, (struct passwd **)v);
printf(%s\n, p.pw_name);
printf(%s\n, q.pw_name);
return 0;
}
Processed: Help
Processing commands for [EMAIL PROTECTED]: package mdadm Ignoring bugs not assigned to: mdadm tags 294404 help Bug#294404: udev does not create /dev/md* devices at boot-up There were no tags set. Tags added: help 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#301121: mdbtools: FTBFS: compile errors
Hi, On Wed, 2005-03-23 at 15:23 -0800, Steve Langasek wrote: On Wed, Mar 23, 2005 at 10:34:08PM +0100, Roland Stigge wrote: building the package mdbtools in a clean build environment (with pbuilder) on i386 results in: It would generally be helpful if you would include in these bug reports information about whether you're building in a sid or a sarge pbuilder, so that maintainers know for sure how to reproduce it. OK. In doubt, sid. bye, Roland -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#301204: libpam-ssh: pam-ssh incorrectly re-uses values returned by getpwnam()
Justin Pryzby wrote: On Thu, Mar 24, 2005 at 03:55:06PM +0300, Michael Tokarev wrote: Package: libpam-ssh Version: 1.91.0-5 Severity: critical A long time ago (circa 1998 or so) I looked at pam-ssh project and noticied several problems with it. And since it's now in Debian, the same problems applies to Debian too. Here's one. in pam_sm_authenticate() routine, pam_ssh saves struct passwd as a pam variable, this way (error checking removed for simplicitly): Are any other getpwnam()-type functions actually called, allowing the buffers to be overwritten? Well, all pam modules and libpam itself does alot of getpw*() calls. An application may call them too ofcourse, between pam auth and session calls. Documentation is not clear about how the fields of the struct are allocated; a minimal test indicates that they are malloc()ated for the first call only, but that implementation could change; I don't know if there are relevant standards, and it may be that it is intentionally opaque. It's really implementation-dependant. In glibc, they're implemented as wrappers around getpwent_r(); a buffer sufficiently large will be allocated on the first call, and if that buffer isn't sufficient for the next line in /etc/passwd, it will be reallocated (while scanning the file). Other implementations may use diffefent techniques. It does seem like best-practice would be to copy the entire contents of the structure, and not just the pointers. Well, basically yes. With the only small issue: other systems may have additional fields in the structure, which will not be copied without quite a bit of autoconf magic. I can't say from memory, but I've seen HP/UX or NetBSD had several non-standard fields in struct passwd. So, at least, such copying have to be done with care. The struct passwd pointer in pam_sm_open_session() is passed into openpam_borrow_cred() -- and nothing stops this last routine from using those additional fields on a platform which actually has them. I think... ;) Well, ok, as I don't have any direct reference to those extra fields.. maybe the problem isn't a problem after all ;) Luckly, most (depending on the other modules in the PAM stack) getpw* calls will be the same as this module does, and hence the problem will not occur. I think you are implying that every libpam module shares memory space with every other libpam module, which AIUI is incorrect. libpam are ELF shared objects, and every process that links with such an object (at runtime) will get its own private copy of the data section, but the text section will be shared (mmaped, really, it is backed by disk). I mean that other modules in the stack will most likely call getpwnam() with the same argument, the same username which is being logged into. So, provided the user info has not changed since pam-ssh call, the whole structure/fields layout will be the same again. But if some other module or application itself will call getpwnam() with different username, the memory layout will change. Does your claim still stand? Does *that* module call getpwnam()-type functions multiple times, without memcpy the pointers, and then reuse the top-level pointer? It does not matter which module performs any calls to getpw* routines. I pointed this problem out to the author the same time I looked at the module, but instead of an ACK he replied with something like If you don't like my program write your own. Later on, he changed logic a bit -- previously he where saving the pwent pointer, now he saves the whole structure (as pwent_keep), but the same problem is still here. Right; it is a static buffer, and multiple calls to getpwnam() return the same pointer, *and* the pointer structure fields always point to the same place. Well.. not into the same place, if it's the different username. The line from /etc/passwd (whatever) is read into that buffer, and when parsed into fields. And pointers are initialized to point to the found fields, to whatever place they're at. If you parse the same line, the pointers will be exactly the same. If you parse different line, the pointers will be different. One way or another, no one guaranteed that content of the memory in question will be valid and the same after other module work. The content of the structure and pointed-to memory is valid only up to the next call to getpw*() routine. It seems that your request can be easily satisfied by using the reentrant versions of these functions, like getpwnam_r. I'm including a test file I've been playing with, which indicates that a patch, if necessary, would be unintrusive. Yes, getpwnam_r will work. It's a PITA to deal with, and it may not be sufficiently portable, but it will work. But: why are you trynig to save the pwent pointer in the first place? To remove extra getpwnam() call? It will be done by other modules and by the application too, anyway... Why not just call it again in pam_sm_open_session(), based on pam_get_user() ? BTW, there was a discussion on linux-pam list
Bug#295131: JFTR: sdl(glib2.0) vs. wx2.4(glib1.2) only affects scorched3d
On Thu, Mar 24, 2005 at 03:11:32PM +0100, Josselin Mouette wrote:
[...]
Sarge and sid have the same SDL version. You are basically comparing
libsdl1.2debian-all and libsdl1.2debian-oss.
Yes you're right. I didn't notice that I'm using -all on my box.
Any reason for such huge disproportions? That's where we got libglib2.0.
Scorched3D built on sarge works fine and doesn't link against libglib2.0.
That's an indirect dependency (brought by libarts), that you won't see
if you pass --as-needed to ld. However, this is not enough, as users
having libsdl1.2debian-{all,arts} installed will still get this
dependency at runtime, probably leading to segfaults.
So I suppose that Conflicts: libsdl1.2debian-{all,arts} isn't a solution?
ARTS users won't be able to use Scorched3D then :/
Also seems that other distros have wxgtk2.4 linked against libglib2.0 and
libsdl doesn't linked against any libglib.
This way most other distros have scorched3d linked against libglib2.0, but
only because wxgtk2.4 and not libsdl.
This may be because they are building a GTK+2.0 version of libwxgtk2.4.
I'm not sure what to do now. Is it possible to link our wxgtk2.4 against
glib2.0? Or unlink libsdl from using libglib?
I'm afraid there is no miracle solution. Getting wxgtk2.5 to install
together with wxgtk2.4, if possible, would be a good option. IIRC, it's
possible to rebuild WxWidgets 2.4 against GTK+ 2.x, but it requires
changes in the applications because of the move to UTF8.
Hmm, so I wonder how it's done in other distros where wxwidgets uses
gtk2.x. Or maybe they don't use `apt-cache rdepends libwxgtk2.4`?
regards
fEnIo
--
,''`. Bartosz Fenski | mailto:[EMAIL PROTECTED] | pgp:0x13fefc40 | irc:fEnIo
: :' : 32-050 Skawina - Glowackiego 3/15 - w. malopolskie - Poland
`. `' phone:+48602383548 | proud Debian maintainer and user
`- http://skawina.eu.org | jid:[EMAIL PROTECTED] | rlu:172001
signature.asc
Description: Digital signature
Bug#241497: RFC and status report: Kernel upgrades for woody-sarge upgrades
I installed a minimal basic stable installation of Debian (no packages selected with tasksel or dselect) when doing the upgade as stated on http://higgs.djpig.de/upgrade/upgrade-kernel/ via the dpkg method. I first needed to install zlib1g, ash and stat. maby it is better to mention that those need to be installed prior. and there is no mentioning of what to change in silo.conf cause you need to specify the initrd somehow. I added: initrd=1/initrd.img is this correct? afther rebooting I get the following error(s): modprobe: Noting to load ??? Specify at least a module or a wildcard like \* pivot_root: No such file or directory /sbin/init: cannot open dev/console: no such file Kernel panic: Attempted to kill init! - Original Message - From: Frank Lichtenheld [EMAIL PROTECTED] To: debian-release@lists.debian.org; debian-hppa@lists.debian.org; debian-sparc@lists.debian.org Cc: [EMAIL PROTECTED] Sent: Thursday, March 24, 2005 2:31 PM Subject: RFC and status report: Kernel upgrades for woody-sarge upgrades Hi all. As many of you may know on some machines users will need to install a current kernel before they will be able to upgrade woody to sarge (or better: glibc of woody to glibc of sarge). I've tried to use the available information to provide the needed files for these kernel upgrades. To my knowledge the affected machines/architecures are currently hppa64, sparc sun4m (only some of them) and 80386. Because of the pain to maintain a kernel backport over the lifetime of sarge we have decided to only offer backports of the needed tools (modutils, module-init-tools and initrd-tools) to use stock sarge kernels on woody. It is planned to upload these files together with some documentation into a upgrade-kernel (or whatever else name the ftpmasters will prefer) directory in the archive. I've prepared the necessary backports and some rudimentary documentation and put it online at http://higgs.djpig.de/upgrade/upgrade-kernel/ We now need people that - test the backports - read/comment on/improve the documentation Gruesse, -- Frank Lichtenheld [EMAIL PROTECTED] www: http://www.djpig.de/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#301204: libpam-ssh: pam-ssh incorrectly re-uses values returned by getpwnam()
A small followup with additional comments.
Justin Pryzby wrote:
[]
It seems that your request can be easily satisfied by using the
reentrant versions of these functions, like getpwnam_r. I'm including
a test file I've been playing with, which indicates that a patch, if
necessary, would be unintrusive.
I said it's a PITA to get getpwnam_r() usage right. Here's why:
#include unistd.h
#include pwd.h
#include sys/types.h
int main()
{
struct passwd p,q;
char *buf,*buf2;
int buflen=sysconf(_SC_GETPW_R_SIZE_MAX);
buf=(char *)malloc(buflen);
buf2=(char *)malloc(buflen);
struct passwd *v=malloc(sizeof (void *));
//struct passwd *p=getpwnam(pryzbyj);
getpwnam_r(pryzbyj, p, buf, buflen, (struct passwd **)v);
Here, we have to deal with errno = ERANGE.
I re-read linux getpwnam_r() manpage - it changed since I last looked there.
Now it says:
The maximum needed size for buf can be found using sysconf(3) with the
_SC_GETPW_R_SIZE_MAX parameter.
(exactly the thing you did here). Previously, preferred way
to call getpwnam_r was a loop like this (error checking omitted):
int bufsize = _GETPWNAM_PREFERRED_BUFSIZE;
char *buf = malloc(bufsize);
while((err = getpwnam_r(name, pwent, buf, bufsize, pwent)) == ERANGE) {
bufsize *= 2;
buf = realloc(buf, bufsize);
}
(again, I don't remember how the constant GETPWNAM_PREFERRED_BUFSIZE was
named, it's a suggested initial bufsize).
Here's what glibc.info says about getpwuid_r():
If a user with ID UID is found, the pointer returned in RESULT
points to the record which contains the wanted data (i.e., RESULT
contains the value RESULT_BUF). If no user is found or if an
error occurred, the pointer returned in RESULT is a null pointer.
The function returns zero or an error code. If the buffer BUFFER
is too small to contain all the needed information, the error code
`ERANGE' is returned and ERRNO is set to `ERANGE'.
(no mention of that POSIX sysconf stuff).
Obviously, this loop-way is.. difficult and ugly.
And BTW, not all systems are using /etc/passwd. For other database
implementations, things may be different.
/mjt
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#295131: JFTR: sdl(glib2.0) vs. wx2.4(glib1.2) only affects scorched3d
On Thu, 24 Mar 2005, Josselin Mouette wrote: I'm not sure what to do now. Is it possible to link our wxgtk2.4 against glib2.0? Or unlink libsdl from using libglib? I'm afraid there is no miracle solution. Getting wxgtk2.5 to install Miracle? no. Technical, sound, and sane? Yes: Version the symbols properly on all libraries that are going to be used by other libraries. Gnome and Kde should have been doing this since day one, since they are the very definition of library hell. -- One disk to rule them all, One disk to find them. One disk to bring them all and in the darkness grind them. In the Land of Redmond where the shadows lie. -- The Silicon Valley Tarot Henrique Holschuh -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#241497: RFC and status report: Kernel upgrades for woody-sarge upgrades
I installed a minimal basic stable installation of Debian (no packages selected with tasksel or dselect) when doing the upgade as stated on http://higgs.djpig.de/upgrade/upgrade-kernel/ via the dpkg method. I first needed to install zlib1g, ash and stat. maby it is better to mention that those need to be installed prior. and there is no mentioning of what to change in silo.conf cause you need to specify the initrd somehow. I added: initrd=1/initrd.img is this correct? afther rebooting I get the following error(s): modprobe: Noting to load ??? Specify at least a module or a wildcard like \* pivot_root: No such file or directory /sbin/init: cannot open dev/console: no such file Kernel panic: Attempted to kill init! - Original Message - From: Frank Lichtenheld [EMAIL PROTECTED] To: debian-release@lists.debian.org; debian-hppa@lists.debian.org; debian-sparc@lists.debian.org Cc: [EMAIL PROTECTED] Sent: Thursday, March 24, 2005 2:31 PM Subject: RFC and status report: Kernel upgrades for woody-sarge upgrades Hi all. As many of you may know on some machines users will need to install a current kernel before they will be able to upgrade woody to sarge (or better: glibc of woody to glibc of sarge). I've tried to use the available information to provide the needed files for these kernel upgrades. To my knowledge the affected machines/architecures are currently hppa64, sparc sun4m (only some of them) and 80386. Because of the pain to maintain a kernel backport over the lifetime of sarge we have decided to only offer backports of the needed tools (modutils, module-init-tools and initrd-tools) to use stock sarge kernels on woody. It is planned to upload these files together with some documentation into a upgrade-kernel (or whatever else name the ftpmasters will prefer) directory in the archive. I've prepared the necessary backports and some rudimentary documentation and put it online at http://higgs.djpig.de/upgrade/upgrade-kernel/ We now need people that - test the backports - read/comment on/improve the documentation Gruesse, -- Frank Lichtenheld [EMAIL PROTECTED] www: http://www.djpig.de/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#297806: util-vserver: FTBFS in experimental
Hello On Wed, Mar 23, 2005 at 02:41:29PM +0200, Lars Wirzenius wrote: Some further notes about util-vserver's failure to build from source: * dietlibc-dev on hppa fails to define O_FOLLOW and O_LARGEFILE. Adding these to CFLAGS allows util-vserver to build until it fails to link, because the linking looks for /usr/lib/diet/lib-hppa instead of /usr/lib/diet/lib-parisc, which dietlibc-dev provides. I believe, but have not tested (since it would require root) that if that is fixed in dietlibc, util-vserver will build on hppa. * Similarly to hppa, everything should work on mipsel after dietlibc-dev provides /usr/lib/diet/lib-mipsel instead of /usr/lib/diet/lib-mips (or after libtool is changed to use the .../lib-mips directory). * Steve Langasek reported on IRC that adding -mv8 to CFLAGS should make util-vserver build on sparc. This means util-vserver won't work on the oldest sparcs, but we (or the kernel and glibc) don't seem to support them anyway. * m68k shouldn't build util-vserver at all, since dietlib-dev does not exist on that platform. I have mailed the Package-arch-specific maintainers that util-vserver should be added to that file to prevent build daemons from building util-vserver in vain (forgot to Cc Ola, sorry). * I couldn't replicate the build problem on trex.debian.org, which is an s390 machine. I assume the problem was transient. I can provide a patch for debian/rules for conditionally adding arch-specific stuff to CFLAGS, but later tonight or tomorrow. Again, I hope this is helpful. Happy hacking. Thanks a lot (for both mails). It is very helpful. If you can provide a conditional arch update to debian rules, I'll upload that fix at once. Regards, // Ola -- - Ola Lundqvist --- / [EMAIL PROTECTED] Annebergsslingan 37 \ | [EMAIL PROTECTED] 654 65 KARLSTAD | | +46 (0)54-10 14 30 +46 (0)70-332 1551 | | http://www.opal.dhs.org UIN/icq: 4912500 | \ gpg/f.p.: 7090 A92B 18FE 7994 0C36 4FE4 18A1 B1CF 0FE5 3DD9 / --- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#301252: xfsprogs - not compiled on unstable
Package: xfsprogs Version: 2.6.26-1 Severity: grave This package seems to be not built on unstable, libhandle requests executable stack, while a unstable build does not do that. Bastian -- Our missions are peaceful -- not for conquest. When we do battle, it is only because we have no choice. -- Kirk, The Squire of Gothos, stardate 2124.5 signature.asc Description: Digital signature
Bug#301251: acl - not compiled on unstable
Package: attr Version: 2.4.21-1 Severity: grave This package was not built on unstable for i386: | $ strings /usr/lib/libattr.a | grep GCC | sort -u | GCC: (GNU) 2.95.4 20011002 (Debian prerelease) This misscompilation leads to executable stack. Bastian -- Our missions are peaceful -- not for conquest. When we do battle, it is only because we have no choice. -- Kirk, The Squire of Gothos, stardate 2124.5 signature.asc Description: Digital signature
Processed: Bug #297639: bindgraph: missing LOG_FORMAT option in /etc/default/bindgraph
Processing commands for [EMAIL PROTECTED]: severity 297639 grave Bug#297639: bindgraph unable to parse dns log file Severity set to `grave'. thanks Stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#301254: dosfsck: new version shows lots of errors
Package: dosfstools Version: 2.11-1 Severity: grave Hello, the new 2.11-1 dosfsck shows lots of errors on my filesystems (FAT32, LFN / VFAT), while the filesystem looks quite okay and neither Windows scandisk nor 2.10-1 dosfsck show any errors. The errors reported are (perhaps among others): * Start cluster beyond limit (...). Truncating file. * File size is ... bytes, cluster chain length is 0 bytes. Truncating file to 0 bytes. * Free cluster summary wrong (... vs. really ...) * Start does point to root directory. Deleting dir. As you can see in other bug reports, users seem to stumble over it already. Therefore, I consider this bug grave enough to prevent 2.11-1 from migration into testing, thus I raised the serverity appropriately. Thanks for your work regards Mario -- There are 10 types of people in the world: Those who understand binary, and those who don't... -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#297639: Bug #297639: bindgraph: missing LOG_FORMAT option in /etc/default/bindgraph
severity 297639 grave thanks Hi, this bug can be resolved adding LOG_FORMAT=bind92 to /etc/default/bindgraph. This will fix parsing with testing version of bind9 (still at 9.2), since now bindgraph defaults to --format=bind93 which is not in testing. (BTW, this bug will never show in unstable, which has bind 9.3). You should add a default setting in /etc/default/bindgraph according to the version of bind9 currently installed. Since then, this bug will make bindgraph unusable in testing and should be fixed before release, thus the 'grave' severity. Regards, -- Luigi Gangitano -- [EMAIL PROTECTED] -- [EMAIL PROTECTED] GPG: 1024D/924C0C26: 12F8 9C03 89D3 DB4A 9972 C24A F19B A618 924C 0C26 signature.asc Description: Questa parte del messaggio =?ISO-8859-1?Q?=E8?= firmata
Bug#295131: JFTR: sdl(glib2.0) vs. wx2.4(glib1.2) only affects scorched3d
Le jeudi 24 mars 2005 14:27 -0300, Henrique de Moraes Holschuh a crit : On Thu, 24 Mar 2005, Josselin Mouette wrote: I'm not sure what to do now. Is it possible to link our wxgtk2.4 against glib2.0? Or unlink libsdl from using libglib? I'm afraid there is no miracle solution. Getting wxgtk2.5 to install Miracle? no. Technical, sound, and sane? Yes: Version the symbols properly on all libraries that are going to be used by other libraries. Yes, adding symbol versioning to Glib is definitely an option. It also means rebuilding all of the incriminated libraries. Gnome and Kde should have been doing this since day one, since they are the very definition of library hell. I don't know for KDE, but the core GNOME libraries now retain full binary compatibility in all versions. -- .''`. Josselin Mouette/\./\ : :' : [EMAIL PROTECTED] `. `'[EMAIL PROTECTED] `- Debian GNU/Linux -- The power of freedom signature.asc Description: Ceci est une partie de message =?ISO-8859-1?Q?num=E9riquement?= =?ISO-8859-1?Q?_sign=E9e?=
Bug#267101: Please close
On Thu, 2005-03-24 at 14:05 +0100, Martin Pitt wrote: Hi! Martin Michlmayr [2005-03-24 12:10 +]: * Martin Pitt [EMAIL PROTECTED] [2005-03-24 12:39]: Since termpkg is not in Debian any more, can you please close this bug? It seems it's still there? Or is this another package? 13048:[EMAIL PROTECTED]: ~] madison termpkg termpkg | 3.3-1 | unstable | source 13049:[EMAIL PROTECTED]: ~] madison -S termpkg termnet | 3.3-1 | unstable | arm, hppa, i386, ia64, m68k, mips, mipsel, s390, sparc termnetd | 3.3-1 | unstable | arm, hppa, i386, ia64, m68k, mips, mipsel, s390, sparc ttyd | 3.3-1 | unstable | arm, hppa, i386, ia64, m68k, mips, mipsel, s390, sparc termpkg | 3.3-1 | unstable | source Oops, sorry for this, I looked only for a binary package, which doesn't exist. Sorry for the noise! /me fetches brown paperbag now... It is still there, although I wrote a mail to ftp-master months ago asking for removal. I do not intend to maintain this package any more, and I believe there are better packages for the same task. Greetings, Oliver signature.asc Description: This is a digitally signed message part
Processed: tagging 301254
Processing commands for [EMAIL PROTECTED]: # Automatically generated email from bts, devscripts version 2.8.10 tags 301254 sid Bug#301254: dosfsck: new version shows lots of errors There were no tags set. Tags added: sid 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#267101: Please close
* Oliver Kurth [EMAIL PROTECTED] [2005-03-24 09:28]: It is still there, although I wrote a mail to ftp-master months ago asking for removal. I do not intend to maintain this package any more, and I believe there are better packages for the same task. You have to file a bug report on ftp.debian.org. Removal requests are acton up very quickly these days. -- Martin Michlmayr http://www.cyrius.com/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#300168: more related bugs: unknown type and is protected within this context
(I am not sure if I am right in mentioning additional bugs in this bug report. Please correct me if this is not the convention and I will file a separate one.) Below I have listed new bugs I found and the solutions to fix them (except of one). Just FYI, I have these packages now installed: dpkg -l *superlu* *arpack* *blas* | grep ^ii ii libsuperlu33.0-2 Direct solution of large, sparse systems of ii libsuperlu3-de 3.0-2 Direct solution of large, sparse systems of ii arpack++ 2.1-5 Object-oriented version of the ARPACK packag ii libarpack2 2.1-8 Fortran77 subroutines to solve large scale e ii libarpack2-dev 2.1-8 Fortran77 subroutines to solve large scale e ii refblas3 1.2-6 Basic Linear Algebra Subroutines 3, shared l ii refblas3-dev 1.2-6 Basic Linear Algebra Subroutines 3, static l Continuing with the examples of ARPACK++, here is another bug: Line 34 of /usr/share/doc/arpack++/examples/matrices/nonsym/lnmatrxa.h is: m = INT(sqrt(n/2)); With this line, the compiler gives the error: #--- /usr/share/doc/arpack++/examples/matrices/nonsym/lnmatrxa.h: In function `void BrusselatorMatrix(FLOAT, FLOAT, FLOAT, FLOAT, FLOAT, INT, INT, FLOAT*, INT*, INT*) [with FLOAT = double, INT = int]': ansymshf.cc:71: instantiated from here /usr/share/doc/arpack++/examples/matrices/nonsym/lnmatrxa.h:35: error: call of overloaded `sqrt(int)' is ambiguous /usr/include/bits/mathcalls.h:157: error: candidates are: double sqrt(double) /usr/include/c++/3.3/cmath:550: error: long double std::sqrt(long double) /usr/include/c++/3.3/cmath:546: error: float std::sqrt(float) #--- The error is I guess removed by typecasting the argument of 'sqrt' function to double by modifying the line mentioned to: m = INT(sqrt( ((double)n) / 2)); So that took care of that. But is this even advisable? Afterall, 'n' is a template parameter. Anyhow, if I did that change, the compilation progressed further, but I then got these two more rather serious errors(only part of the compiler output here): #--- /usr/include/arpack++/arlgnsym.h: In constructor ` ARluNonSymGenEigFLOAT::ARluNonSymGenEig(int, ARluNonSymMatrixTYPE, ARluNonSymMatrixTYPE, char*, int, FLOAT, int, FLOAT*, bool) [with FLOAT = double]': areig.h:773: instantiated from `int AREig(FLOAT*, FLOAT*, FLOAT*, int, int, FLOAT*, int*, int*, int, FLOAT*, int*, int*, int, char*, int, FLOAT, int, FLOAT*, bool) [with FLOAT = double]' ansymgre.cc:87: instantiated from here /usr/include/arpack++/arlgnsym.h:193: error: no matching function for call to ` ARluNonSymGenEigdouble::DefineParameters(int, int, ARluNonSymPencildouble, double*, unknown type, ARluNonSymPencildouble, double*, unknown type, char*, int, double, int, double*, bool)' /usr/include/arpack++/argeig.h:128: error: candidates are: void ARGenEigFLOAT, TYPE, FOP, FB::DefineParameters(int, int, FOP*, typename ARStdEigFLOAT, TYPE, FOP::TypeOPx, FB*, void (FB::*)(TYPE*, TYPE*), char*, int, FLOAT, int, TYPE*, bool) [with FLOAT = double, TYPE = double, FOP = ARluNonSymPencildouble, double, FB = ARluNonSymPencildouble, double] /usr/include/arpack++/armat.h: In member function `void ARluNonSymPencilT, S::DefineMatrices(ARluNonSymMatrixTYPE, ARluNonSymMatrixTYPE) [with TYPE = double, FLOAT = double]': areig.h:191: instantiated from `int AREig(FLOAT*, FLOAT*, FLOAT*, int, int, FLOAT*, int*, int*, int, FLOAT*, int*, int*, int, char*, int, FLOAT, int, FLOAT*, bool) [with FLOAT = double]' ansymgre.cc:87: instantiated from here /usr/include/arpack++/armat.h:25: error: `int ARMatrixdouble::m' is protected /usr/include/arpack++/arlnspen.h:675: error: within this context /usr/include/arpack++/armat.h:25: error: `int ARMatrixdouble::m' is protected /usr/include/arpack++/arlnspen.h:675: error: within this context /usr/include/arpack++/armat.h:25: error: `int ARMatrixdouble::n' is protected /usr/include/arpack++/arlnspen.h:675: error: within this context /usr/include/arpack++/armat.h:25: error: `int ARMatrixdouble::n' is protected /usr/include/arpack++/arlnspen.h:675: error: within this context #--- The first error above is the now familiar one of unknown type. That is solved by putting in before the 4th and 6th arguments of DefineParameters function at line 193 of /usr/include/arpack++/arlgnsym.h and making lines 193~196 of this file as: % % DefineParameters(A.ncols(), nevp, Pencil, ARluNonSymPencilFLOAT, FLOAT::MultInvBAv, Pencil, ARluNonSymPencilFLOAT, FLOAT::MultBv, whichp, ncvp, tolp, maxitp, residp, ishiftp); % % That leaves us with the second type of errors that a
Bug#301257: gauche_0.8.3-1(mipsel/unstable): configure built with broken libtool.m4
Package: gauche
Version: 0.8.3-1
Severity: serious
There was an error while trying to autobuild your package:
Automatic build of gauche_0.8.3-1 on solitude by sbuild/mipsel 17
Build started at 20050320-1947
[...]
The version of libtool used to build this source package is too old to
correctly support shared libraries for the Debian mips and mipsel
architectures. Debian versions 1.5-2 and 1.4.2-7 and higher correctly
support them. You need to update all of the libtool related files by
running the following on your source tree:
autoreconf --force
You may need to use the --install option as well. You can also try the
individual commands needed yourself:
libtoolize --force --copy
aclocal
autoheader
automake -a
autoconf
autoheader may not be needed, and you may need to use versioned binaries
(autoconf2.13, automake-1.{4,6,7}, aclocal-1.{4,6,7}, etc)
The correct 'configure' script will have output that looks like this:
linux*)
lt_cv_deplibs_check_method=pass_all
;;
Older versions of libtool used a file_magic check for the pattern
file_magic ELF [0-9][0-9]*-bit [LM]SB (shared object|dynamic lib )
The output of file(1) on a shared library on MIPS does not match this
regular expression, however. Earlier versions of file had been
modified to match this regular expression, but the latest version uses
the same output as upstream once again. The file check often causes
problems, and results on a build-dep on file that you might not
otherwise be aware of. The new method doesn't need file(1) at all,
and is far less fragile, so it is best to upgrade the configure script
with proper mips support.
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#298963: caudium: contains non-free fonts
On Thu, 2005-03-24 at 19:33 +0100, Marek Habersack wrote: On Thu, Mar 24, 2005 at 11:58:10AM -0300, Gustavo Franco scribbled: Hi Marek, Hello Gustavo, [damned, forgot to upload a new version...] The free fonts site that you said is corefonts.sf.net.These fonts aren't free as in DFSG and there's a package at contrib section called 'msttcorefonts', AFAIK the postinst retrieves the fonts from the website. I know, but the font I meant is not one of the MS fonts. Tere is a third font there, which was taken from a free site, whose name I cannot remember. No problem, i focused on MS fonts issue because i think you've clarified the other font problem in that previous e-mail. Can't you confirm if caudium works without these and that other font ? If not we can still try the freefont alternatives or just replace the references to these fonts and test. Yes, caudium itself will work without any of the TTF fonts present. Its config interface (web-based) uses a built-in bitmapped font for rendering of some controls, the Lucida font is used by default by some modules that render text, but changing it is not a problem. I will try to remember and upload a new version that uses bitstream vera this weekend. Please do, it's a RC bug and we're closer to a freeze. I recommend you only upload a fix to this problem and not a entire new release. It can help us putting it on sarge if the freeze came while the uploaded package sit on sid, ok? Have you contacted upstream ? If not, please do so and point them to: http://corefonts.sourceforge.net/eula.htm I am one of the upstream authors :) - it wasn't me who put the fonts there, but I know the situation. I haven't fixed it so far merely because of lack of time in the past weeks, but I'll get to it asap. Promise. joke Good to hear, i'm now proud that i haven't started shooting the upstream authors about this bug. /joke I can understand this lack of time and it's the main reason that i haven't tracked RC bugs actively in the last few months, i'm doing it right now and i think that we're closer to squash this one. When you prepare the package, if you can't upload it at the same time due the lack of testing please tag this bug as 'pending'. I think that it's a trivial bug to solve but if you need help testing, let me known. Thanks, Gustavo Franco -- [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#301267: libant1.6-java: FTBFS: Jikes could not find package java.lang
Package: libant1.6-java Severity: serious When trying to build 'libant1.6-java' in a clean chroot, I get the following error: ... Bootstrapping Ant Distribution ... Compiling Ant Classes Found 1 system error and issued 1 warning: *** Semantic Warning: I/O warning: No such file or directory while trying to open /usr/share/sablevm/sablevm-classpath. *** Semantic Error: You need to modify your classpath, sourcepath, bootclasspath, and/or extdirs setup. Jikes could not find package java.lang in: /usr/share/sablevm/sablevm-classpath /usr/share/java/jaxp-1.2.jar build/classes src/main lib/xercesImpl.jar lib/xml-apis.jar /usr/share/java/junit.jar . ... Failed compiling Ant classes ! make: *** [debian/build-stamp] Error 1 Regards Andreas Jochens -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Processed: retitle 255339 to kernel-patch-debianlogo: Would like an updated version for 2.4.26 and 2.6.6
Processing commands for [EMAIL PROTECTED]: # Automatically generated email from bts, devscripts version 2.8.10 retitle 255339 kernel-patch-debianlogo: Would like an updated version for 2.4.26 and 2.6.6 Bug#255339: debianlogo: Would like an updated version for 2.4.26 and 2.6.6 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#300787: impossible to upgrade makedev
Ok, I've uninstalled makedev and reinstalled with udev. The installation proceeds bat with this error: /var/lib/dpkg/info/makedev.postinst: line 27: /sbin/MAKEDEV: no such file or directory also for lines 28 and 45. Then, reinstalling kde, I obtain this error for the libraw1394-5: Configuro libraw1394-5 (0.10.1-1.1) ... Creating device node /dev/raw1394... /var/lib/dpkg/info/libraw1394-5.postinst: line 8: /sbin/MAKEDEV: No such file or directory dpkg: error processing libraw1394-5 (--configure): il sottoprocesso post-installation script ha restituito un codice di errore 1 and apt lets the package not configured. I don't know if you are the correct one to tell this, but I've thougth was usefull. If you need any other information about my situation I'm here! Thanks Alessandro Alle 22:37, lunedì 21 marzo 2005, hai scritto: On Mon, Mar 21, 2005 at 10:13:05PM +0100, Alessandro Pagnin wrote: Package: makedev Version: 2.3.1-77 Severity: critical Justification: breaks the whole system Trying to upgrade to this version of makedev, when system go to configure the package it reboots immediately This didn't happen for me. I'm running udev; are you? Justin
Bug#301039: Bugfix
Hi, I just fixed the problem, the patch is attached. Tags: patch thanks. fix_lsh-execuv.patch.gz Description: GNU Zip compressed data bye Stefan -- http://www.dreamind.de/ Oroborus and Debian GNU/Linux Developer.
Bug#241497: RFC and status report: Kernel upgrades for woody-sarge upgrades
On Thu, Mar 24, 2005 at 01:54:38PM +, Matthew Wilcox wrote: On Thu, Mar 24, 2005 at 02:31:55PM +0100, Frank Lichtenheld wrote: As many of you may know on some machines users will need to install a current kernel before they will be able to upgrade woody to sarge (or better: glibc of woody to glibc of sarge). I've tried to use the available information to provide the needed files for these kernel upgrades. To my knowledge the affected machines/architecures are currently hppa64, sparc sun4m (only some of them) and 80386. It's all hppa machines, not just hppa64. Then why does the libc6 preinst say that the minimum kernel is 2.4.17 for parisc, and 2.4.19 for parisc64? If this is an error, it will need to be reconciled before release. -- Steve Langasek postmodern programmer signature.asc Description: Digital signature
Processed: tagging 301039
Processing commands for [EMAIL PROTECTED]: # Automatically generated email from bts, devscripts version 2.8.10 tags 301039 patch Bug#301039: lsh-server: wrong path of lsh-execuv There were no tags set. Tags added: patch 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#297769: patch
On Thu, Mar 24, 2005 at 04:44:10PM +0100, Bastian Blank wrote: The attached patch updates sched_[gs]etaffinity to the new interface from glibc 2.3.4. Investigation in the lintian lab on gluck.d.o shows that there are at least two packages, valgrind and schedutils, which would need to be updated to use the new API once this change is uploaded. Unfortunately, the data in that lintian lab is 9 months out-of-date, so a more thorough check is needed before this change can be allowed into sarge. -- Steve Langasek postmodern programmer signature.asc Description: Digital signature
Bug#300787: impossible to upgrade makedev
On Thu, Mar 24, 2005 at 08:00:46PM +0100, Alessandro Pagnin wrote: Ok, I've uninstalled makedev and reinstalled with udev. The installation proceeds bat with this error: /var/lib/dpkg/info/makedev.postinst: line 27: /sbin/MAKEDEV: no such file or directory That shouldn't be possible.. You were reinstalling this version? ii makedev2.3.1-77 creates device files in /dev It contains /sbin/MAKEDEV. I don't know if you are the correct one to tell this, but I've thougth was usefull. Please Cc: the bug in your replies, so they go to the bug log and the maintainer. Please run, as root: rm /var/cache/apt/archives/makedev* apt-get --reinstall install makedev Your original report said it reboots immediately. Did you mean that the computer reboots, and reloads the linux kernel and all? Bdale: makedev.postinst has set +e; is that what you intend? I would have expected set -e. Justin Alle 22:37, lunedì 21 marzo 2005, hai scritto: On Mon, Mar 21, 2005 at 10:13:05PM +0100, Alessandro Pagnin wrote: Package: makedev Version: 2.3.1-77 Severity: critical Justification: breaks the whole system Trying to upgrade to this version of makedev, when system go to configure the package it reboots immediately This didn't happen for me. I'm running udev; are you?
Processed: tagging 301254
Processing commands for [EMAIL PROTECTED]: # Automatically generated email from bts, devscripts version 2.8.10 tags 301254 sid Bug#301254: dosfsck: new version shows lots of errors Tags were: sid Tags added: sid 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 301257
Processing commands for [EMAIL PROTECTED]: # Automatically generated email from bts, devscripts version 2.8.10 tags 301257 sid Bug#301257: gauche_0.8.3-1(mipsel/unstable): configure built with broken libtool.m4 There were no tags set. Tags added: sid 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#241497: RFC and status report: Kernel upgrades for woody-sarge upgrades
On Thu, Mar 24, 2005 at 02:57:35PM +0100, Robin Harmsen wrote: at this moment I am testing the Debian Installer on a SS5 (sun4m I thougt) cause I wanted a newer kernel then 2.2.20. but it isn't working very well I am willing to test this upgrade-kernel to get a beter kernel and be able to do a woody-sarge upgrade I think I will start with it right afther I finished my test with the debian installer and filled in a report I hope I will be able to help :) To the best of our knowledge, the SS5 is not one of the systems affected by this upgrade issue; only systems using the Cypress chips are known to be affected. -- Steve Langasek postmodern programmer signature.asc Description: Digital signature
Bug#285135: marked as done (swf-player: Eats all CPU time and freezes galeon when various pages are opened simultaneously.)
Your message dated Thu, 24 Mar 2005 14:59:54 -0800 with message-id [EMAIL PROTECTED] and subject line Fixed in 0.3.3-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) -- Received: (at submit) by bugs.debian.org; 10 Dec 2004 21:36:19 + From [EMAIL PROTECTED] Fri Dec 10 13:36:19 2004 Return-path: [EMAIL PROTECTED] Received: from smtp2.wanadoo.fr (mwinf0210.wanadoo.fr) [193.252.22.29] by spohr.debian.org with esmtp (Exim 3.35 1 (Debian)) id 1CcsR1-mV-00; Fri, 10 Dec 2004 13:36:19 -0800 Received: from smtp2.wanadoo.fr (mwinf0212 [172.22.133.36]) by mwinf0210.wanadoo.fr (SMTP Server) with ESMTP id C00E388062E4; Fri, 10 Dec 2004 18:42:12 +0100 (CET) Received: from me-wanadoo.net (localhost [127.0.0.1]) by mwinf0212.wanadoo.fr (SMTP Server) with SMTP id B0D781C00214; Fri, 10 Dec 2004 18:42:12 +0100 (CET) Received: from pegasos (AStrasbourg-251-1-48-132.w82-126.abo.wanadoo.fr [82.126.221.132]) by mwinf0212.wanadoo.fr (SMTP Server) with ESMTP id 77E271C00224; Fri, 10 Dec 2004 18:42:12 +0100 (CET) Received: from luther by pegasos with local (Exim 4.34) id 1Ccone-0006rD-It; Fri, 10 Dec 2004 18:43:26 +0100 Content-Type: text/plain; charset=us-ascii MIME-Version: 1.0 Content-Transfer-Encoding: 7bit From: Sven Luther [EMAIL PROTECTED] To: Debian Bug Tracking System [EMAIL PROTECTED] Subject: swf-player: Eats all CPU time and freezes galeon when various pages are opened simultaneously. X-Mailer: reportbug 3.2 Date: Fri, 10 Dec 2004 18:43:26 +0100 Message-Id: [EMAIL PROTECTED] Sender: Sven Luther [EMAIL PROTECTED] Delivered-To: [EMAIL PROTECTED] X-Spam-Checker-Version: SpamAssassin 2.60-bugs.debian.org_2004_03_25 (1.212-2003-09-23-exp) on spohr.debian.org X-Spam-Status: No, hits=-8.0 required=4.0 tests=BAYES_00,HAS_PACKAGE autolearn=no version=2.60-bugs.debian.org_2004_03_25 X-Spam-Level: Package: swf-player Version: 0.3.2-1 Severity: grave Justification: renders package unusable In my powerpc box, on some flash using sites, when i open a similar window multiple time, galeon freezes, and there are lot of swf_player processes eating lot of CPU time. going to a console and killall -KILL swf_player solves it, doing a -TERM doesn't and killing galeon gives me lot of zombie galeon process and the swf_player are still running. Friendly, Sven Luther -- System Information: Debian Release: 3.1 APT prefers unstable APT policy: (500, 'unstable') Architecture: powerpc (ppc) Kernel: Linux 2.4.27-powerpc Locale: [EMAIL PROTECTED], [EMAIL PROTECTED] (charmap=ISO-8859-15) Versions of packages swf-player depends on: ii libart-2.0-2 2.3.16-6 Library of functions for 2D graphi ii libc6 2.3.2.ds1-18 GNU C Library: Shared libraries an ii libglib2.0-0 2.4.8-1The GLib library of C routines ii libgtk2.0-0 2.4.13-1 The GTK+ graphical user interface ii libmad0 0.15.1b-1 MPEG audio decoder library ii libsdl1.2debian 1.2.7-10.1 Simple DirectMedia Layer ii libswfdec0.3 0.3.2-1SWF (Macromedia Flash) decoder lib ii libxt64.3.0.dfsg.1-8 X Toolkit Intrinsics ii xlibs 4.3.0.dfsg.1-8 X Window System client libraries m ii zlib1g1:1.2.2-3 compression library - runtime -- no debconf information --- Received: (at 285135-done) by bugs.debian.org; 24 Mar 2005 22:59:55 + From [EMAIL PROTECTED] Thu Mar 24 14:59:55 2005 Return-path: [EMAIL PROTECTED] Received: from comedi.ucsf.edu (comedi.org) [128.218.64.140] by spohr.debian.org with esmtp (Exim 3.35 1 (Debian)) id 1DEbIx-000218-00; Thu, 24 Mar 2005 14:59:55 -0800 Received: from ds by comedi.org with local (Exim 3.35 #1 (Debian)) id 1DEbIw-00072J-00 for [EMAIL PROTECTED]; Thu, 24 Mar 2005 14:59:54 -0800 Date: Thu, 24 Mar 2005 14:59:54 -0800 From: David Schleef [EMAIL PROTECTED] To: [EMAIL PROTECTED] Subject: Fixed in 0.3.3-1 Message-ID: [EMAIL PROTECTED] Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.3.28i Sender: David Schleef [EMAIL PROTECTED] Delivered-To: [EMAIL PROTECTED] X-Spam-Checker-Version: SpamAssassin 2.60-bugs.debian.org_2005_01_02 (1.212-2003-09-23-exp) on spohr.debian.org X-Spam-Status: No, hits=-3.0 required=4.0 tests=BAYES_00 autolearn=no
Bug#301250: marked as done (acl - not compiled on unstable)
Your message dated Thu, 24 Mar 2005 15:07:34 -0800 with message-id [EMAIL PROTECTED] and subject line Bug#301252: xfsprogs - not compiled on unstable 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) -- Received: (at submit) by bugs.debian.org; 24 Mar 2005 17:55:49 + From [EMAIL PROTECTED] Thu Mar 24 09:55:49 2005 Return-path: [EMAIL PROTECTED] Received: from wavehammer.waldi.eu.org [82.139.196.55] (postfix) by spohr.debian.org with esmtp (Exim 3.35 1 (Debian)) id 1DEWYe-0004i9-00; Thu, 24 Mar 2005 09:55:48 -0800 Received: by wavehammer.waldi.eu.org (Postfix, from userid 1000) id 9A7603C028; Thu, 24 Mar 2005 18:55:45 +0100 (CET) Date: Thu, 24 Mar 2005 18:55:45 +0100 From: Bastian Blank [EMAIL PROTECTED] To: [EMAIL PROTECTED] Subject: acl - not compiled on unstable Message-ID: [EMAIL PROTECTED] Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol=application/pgp-signature; boundary=BXVAT5kNtrzKuDFl Content-Disposition: inline User-Agent: Mutt/1.5.6+20040907i Delivered-To: [EMAIL PROTECTED] X-Spam-Checker-Version: SpamAssassin 2.60-bugs.debian.org_2005_01_02 (1.212-2003-09-23-exp) on spohr.debian.org X-Spam-Status: No, hits=-8.0 required=4.0 tests=BAYES_00,HAS_PACKAGE autolearn=no version=2.60-bugs.debian.org_2005_01_02 X-Spam-Level: --BXVAT5kNtrzKuDFl Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Package: acl Version: 2.2.29-1 Severity: grave This package was not built on unstable for i386: | $ strings /usr/lib/libattr.a | grep GCC | sort -u | GCC: (GNU) 2.95.4 20011002 (Debian prerelease) This misscompilation leads to executable stack. Bastian --=20 Our missions are peaceful -- not for conquest. When we do battle, it is only because we have no choice. -- Kirk, The Squire of Gothos, stardate 2124.5 --BXVAT5kNtrzKuDFl Content-Type: application/pgp-signature; name=signature.asc Content-Description: Digital signature Content-Disposition: inline -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.0 (GNU/Linux) iEYEARECAAYFAkJC/yEACgkQnw66O/MvCNGBYwCdFjEjJ+qeQExF6aQ3FwAfuY6U Vm4AoJapjE/gYgTiLcC/QXeZTSq3rfvn =LZow -END PGP SIGNATURE- --BXVAT5kNtrzKuDFl-- --- Received: (at 301250-done) by bugs.debian.org; 24 Mar 2005 23:07:35 + From [EMAIL PROTECTED] Thu Mar 24 15:07:35 2005 Return-path: [EMAIL PROTECTED] Received: from dsl093-039-086.pdx1.dsl.speakeasy.net (localhost.localdomain) [66.93.39.86] by spohr.debian.org with esmtp (Exim 3.35 1 (Debian)) id 1DEbQN-0003Vm-00; Thu, 24 Mar 2005 15:07:35 -0800 Received: by localhost.localdomain (Postfix, from userid 1000) id 65850171D21; Thu, 24 Mar 2005 15:07:34 -0800 (PST) Date: Thu, 24 Mar 2005 15:07:34 -0800 From: Steve Langasek [EMAIL PROTECTED] To: [EMAIL PROTECTED], [EMAIL PROTECTED], [EMAIL PROTECTED] Subject: Re: Bug#301252: xfsprogs - not compiled on unstable Message-ID: [EMAIL PROTECTED] References: [EMAIL PROTECTED] Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol=application/pgp-signature; boundary=/04w6evG8XlLl3ft Content-Disposition: inline In-Reply-To: [EMAIL PROTECTED] User-Agent: Mutt/1.5.6+20040907i Delivered-To: [EMAIL PROTECTED] X-Spam-Checker-Version: SpamAssassin 2.60-bugs.debian.org_2005_01_02 (1.212-2003-09-23-exp) on spohr.debian.org X-Spam-Status: No, hits=-6.0 required=4.0 tests=BAYES_00,HAS_BUG_NUMBER autolearn=no version=2.60-bugs.debian.org_2005_01_02 X-Spam-Level: --/04w6evG8XlLl3ft Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Thu, Mar 24, 2005 at 06:58:30PM +0100, Bastian Blank wrote: Package: xfsprogs Version: 2.6.26-1 Severity: grave This package seems to be not built on unstable, libhandle requests executable stack, while a unstable build does not do that. I've uploaded recompile-only binNMUs for each of attr, acl, and xfsprogs on i386, which is the only architecture that should be affected. Nathan, please be sure to build your binaries against current unstable systems (chroot or otherwise) in the future when uploading to unstable; otherwise, we end up with binary packages that are not reproducible using current tools. Thanks, --=20 Steve Langasek postmodern programmer --/04w6evG8XlLl3ft Content-Type: application/pgp-signature; name=signature.asc Content-Description:
Bug#301251: marked as done (acl - not compiled on unstable)
Your message dated Thu, 24 Mar 2005 15:07:34 -0800 with message-id [EMAIL PROTECTED] and subject line Bug#301252: xfsprogs - not compiled on unstable 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) -- Received: (at submit) by bugs.debian.org; 24 Mar 2005 17:56:28 + From [EMAIL PROTECTED] Thu Mar 24 09:56:28 2005 Return-path: [EMAIL PROTECTED] Received: from wavehammer.waldi.eu.org [82.139.196.55] (postfix) by spohr.debian.org with esmtp (Exim 3.35 1 (Debian)) id 1DEWZH-0004kN-00; Thu, 24 Mar 2005 09:56:28 -0800 Received: by wavehammer.waldi.eu.org (Postfix, from userid 1000) id 59F443C028; Thu, 24 Mar 2005 18:56:26 +0100 (CET) Date: Thu, 24 Mar 2005 18:56:26 +0100 From: Bastian Blank [EMAIL PROTECTED] To: [EMAIL PROTECTED] Subject: acl - not compiled on unstable Message-ID: [EMAIL PROTECTED] Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol=application/pgp-signature; boundary=WYTEVAkct0FjGQmd Content-Disposition: inline User-Agent: Mutt/1.5.6+20040907i Delivered-To: [EMAIL PROTECTED] X-Spam-Checker-Version: SpamAssassin 2.60-bugs.debian.org_2005_01_02 (1.212-2003-09-23-exp) on spohr.debian.org X-Spam-Status: No, hits=-8.0 required=4.0 tests=BAYES_00,HAS_PACKAGE autolearn=no version=2.60-bugs.debian.org_2005_01_02 X-Spam-Level: --WYTEVAkct0FjGQmd Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Package: attr Version: 2.4.21-1 Severity: grave This package was not built on unstable for i386: | $ strings /usr/lib/libattr.a | grep GCC | sort -u | GCC: (GNU) 2.95.4 20011002 (Debian prerelease) This misscompilation leads to executable stack. Bastian --=20 Our missions are peaceful -- not for conquest. When we do battle, it is only because we have no choice. -- Kirk, The Squire of Gothos, stardate 2124.5 --WYTEVAkct0FjGQmd Content-Type: application/pgp-signature; name=signature.asc Content-Description: Digital signature Content-Disposition: inline -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.0 (GNU/Linux) iEYEARECAAYFAkJC/0oACgkQnw66O/MvCNGhfgCaAxpmE/s7iLwqeBoe00bbpq9M HBUAnjM2gd6zUWXtuENPlxOeJ2sis5w6 =2bIK -END PGP SIGNATURE- --WYTEVAkct0FjGQmd-- --- Received: (at 301251-done) by bugs.debian.org; 24 Mar 2005 23:07:35 + From [EMAIL PROTECTED] Thu Mar 24 15:07:35 2005 Return-path: [EMAIL PROTECTED] Received: from dsl093-039-086.pdx1.dsl.speakeasy.net (localhost.localdomain) [66.93.39.86] by spohr.debian.org with esmtp (Exim 3.35 1 (Debian)) id 1DEbQN-0003Vm-00; Thu, 24 Mar 2005 15:07:35 -0800 Received: by localhost.localdomain (Postfix, from userid 1000) id 65850171D21; Thu, 24 Mar 2005 15:07:34 -0800 (PST) Date: Thu, 24 Mar 2005 15:07:34 -0800 From: Steve Langasek [EMAIL PROTECTED] To: [EMAIL PROTECTED], [EMAIL PROTECTED], [EMAIL PROTECTED] Subject: Re: Bug#301252: xfsprogs - not compiled on unstable Message-ID: [EMAIL PROTECTED] References: [EMAIL PROTECTED] Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol=application/pgp-signature; boundary=/04w6evG8XlLl3ft Content-Disposition: inline In-Reply-To: [EMAIL PROTECTED] User-Agent: Mutt/1.5.6+20040907i Delivered-To: [EMAIL PROTECTED] X-Spam-Checker-Version: SpamAssassin 2.60-bugs.debian.org_2005_01_02 (1.212-2003-09-23-exp) on spohr.debian.org X-Spam-Status: No, hits=-6.0 required=4.0 tests=BAYES_00,HAS_BUG_NUMBER autolearn=no version=2.60-bugs.debian.org_2005_01_02 X-Spam-Level: X-CrossAssassin-Score: 2 --/04w6evG8XlLl3ft Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Thu, Mar 24, 2005 at 06:58:30PM +0100, Bastian Blank wrote: Package: xfsprogs Version: 2.6.26-1 Severity: grave This package seems to be not built on unstable, libhandle requests executable stack, while a unstable build does not do that. I've uploaded recompile-only binNMUs for each of attr, acl, and xfsprogs on i386, which is the only architecture that should be affected. Nathan, please be sure to build your binaries against current unstable systems (chroot or otherwise) in the future when uploading to unstable; otherwise, we end up with binary packages that are not reproducible using current tools. Thanks, --=20 Steve Langasek postmodern programmer --/04w6evG8XlLl3ft Content-Type: application/pgp-signature;
Bug#301252: marked as done (xfsprogs - not compiled on unstable)
Your message dated Thu, 24 Mar 2005 15:07:34 -0800 with message-id [EMAIL PROTECTED] and subject line Bug#301252: xfsprogs - not compiled on unstable 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) -- Received: (at submit) by bugs.debian.org; 24 Mar 2005 17:58:32 + From [EMAIL PROTECTED] Thu Mar 24 09:58:32 2005 Return-path: [EMAIL PROTECTED] Received: from wavehammer.waldi.eu.org [82.139.196.55] (postfix) by spohr.debian.org with esmtp (Exim 3.35 1 (Debian)) id 1DEWbH-0004pr-00; Thu, 24 Mar 2005 09:58:32 -0800 Received: by wavehammer.waldi.eu.org (Postfix, from userid 1000) id 4B0A13C028; Thu, 24 Mar 2005 18:58:30 +0100 (CET) Date: Thu, 24 Mar 2005 18:58:30 +0100 From: Bastian Blank [EMAIL PROTECTED] To: [EMAIL PROTECTED] Subject: xfsprogs - not compiled on unstable Message-ID: [EMAIL PROTECTED] Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol=application/pgp-signature; boundary=O3RTKUHj+75w1tg5 Content-Disposition: inline User-Agent: Mutt/1.5.6+20040907i Delivered-To: [EMAIL PROTECTED] X-Spam-Checker-Version: SpamAssassin 2.60-bugs.debian.org_2005_01_02 (1.212-2003-09-23-exp) on spohr.debian.org X-Spam-Status: No, hits=-8.0 required=4.0 tests=BAYES_00,HAS_PACKAGE autolearn=no version=2.60-bugs.debian.org_2005_01_02 X-Spam-Level: --O3RTKUHj+75w1tg5 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Package: xfsprogs Version: 2.6.26-1 Severity: grave This package seems to be not built on unstable, libhandle requests executable stack, while a unstable build does not do that. Bastian --=20 Our missions are peaceful -- not for conquest. When we do battle, it is only because we have no choice. -- Kirk, The Squire of Gothos, stardate 2124.5 --O3RTKUHj+75w1tg5 Content-Type: application/pgp-signature; name=signature.asc Content-Description: Digital signature Content-Disposition: inline -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.0 (GNU/Linux) iEYEARECAAYFAkJC/8YACgkQnw66O/MvCNHwNQCgpYEVJ5YXWfGSJWnoCZuqhUXj /I8AnjlsLQfMmXY4fqqUAL95FgwMMNCH =hyW7 -END PGP SIGNATURE- --O3RTKUHj+75w1tg5-- --- Received: (at 301252-done) by bugs.debian.org; 24 Mar 2005 23:07:35 + From [EMAIL PROTECTED] Thu Mar 24 15:07:35 2005 Return-path: [EMAIL PROTECTED] Received: from dsl093-039-086.pdx1.dsl.speakeasy.net (localhost.localdomain) [66.93.39.86] by spohr.debian.org with esmtp (Exim 3.35 1 (Debian)) id 1DEbQN-0003Vm-00; Thu, 24 Mar 2005 15:07:35 -0800 Received: by localhost.localdomain (Postfix, from userid 1000) id 65850171D21; Thu, 24 Mar 2005 15:07:34 -0800 (PST) Date: Thu, 24 Mar 2005 15:07:34 -0800 From: Steve Langasek [EMAIL PROTECTED] To: [EMAIL PROTECTED], [EMAIL PROTECTED], [EMAIL PROTECTED] Subject: Re: Bug#301252: xfsprogs - not compiled on unstable Message-ID: [EMAIL PROTECTED] References: [EMAIL PROTECTED] Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol=application/pgp-signature; boundary=/04w6evG8XlLl3ft Content-Disposition: inline In-Reply-To: [EMAIL PROTECTED] User-Agent: Mutt/1.5.6+20040907i Delivered-To: [EMAIL PROTECTED] X-Spam-Checker-Version: SpamAssassin 2.60-bugs.debian.org_2005_01_02 (1.212-2003-09-23-exp) on spohr.debian.org X-Spam-Status: No, hits=-6.0 required=4.0 tests=BAYES_00,HAS_BUG_NUMBER autolearn=no version=2.60-bugs.debian.org_2005_01_02 X-Spam-Level: X-CrossAssassin-Score: 3 --/04w6evG8XlLl3ft Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Thu, Mar 24, 2005 at 06:58:30PM +0100, Bastian Blank wrote: Package: xfsprogs Version: 2.6.26-1 Severity: grave This package seems to be not built on unstable, libhandle requests executable stack, while a unstable build does not do that. I've uploaded recompile-only binNMUs for each of attr, acl, and xfsprogs on i386, which is the only architecture that should be affected. Nathan, please be sure to build your binaries against current unstable systems (chroot or otherwise) in the future when uploading to unstable; otherwise, we end up with binary packages that are not reproducible using current tools. Thanks, --=20 Steve Langasek postmodern programmer --/04w6evG8XlLl3ft Content-Type: application/pgp-signature; name=signature.asc Content-Description: Digital signature Content-Disposition:
Bug#241497: RFC and status report: Kernel upgrades for woody-sarge upgrades
Actualy the SS5 (at least the one I have got here) does have the problem for libc6 version I need a kernel above 2.4.21, and for that kernel I need that libc6 version. - Original Message - From: Steve Langasek [EMAIL PROTECTED] To: debian-release@lists.debian.org; debian-sparc@lists.debian.org Cc: [EMAIL PROTECTED] Sent: Thursday, March 24, 2005 11:44 PM Subject: Re: RFC and status report: Kernel upgrades for woody-sarge upgrades -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#296433: marked as done (umbrello: classes completely disappearing when moved into packages)
Your message dated Thu, 24 Mar 2005 18:47:09 -0500 with message-id [EMAIL PROTECTED] and subject line Bug#296433: fixed in kdesdk 4:3.3.2-2 has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what I am talking about this indicates a serious mail system misconfiguration somewhere. Please contact me immediately.) Debian bug tracking system administrator (administrator, Debian Bugs database) -- Received: (at submit) by bugs.debian.org; 22 Feb 2005 13:58:58 + From [EMAIL PROTECTED] Tue Feb 22 05:58:58 2005 Return-path: [EMAIL PROTECTED] Received: from mail.gmx.net [213.165.64.20] by spohr.debian.org with smtp (Exim 3.35 1 (Debian)) id 1D3aYz-0006So-00; Tue, 22 Feb 2005 05:58:58 -0800 Received: (qmail invoked by alias); 22 Feb 2005 13:58:26 - Received: from unknown (EHLO [127.0.0.1]) (212.204.39.239) by mail.gmx.net (mp004) with SMTP; 22 Feb 2005 14:58:26 +0100 X-Authenticated: #834378 Content-Type: text/plain; charset=us-ascii MIME-Version: 1.0 Content-Transfer-Encoding: 7bit From: Benjamin Mesing [EMAIL PROTECTED] To: Debian Bug Tracking System [EMAIL PROTECTED] Subject: umbrello: classes completely disappearing when moved into packages Bcc: Benjamin Mesing [EMAIL PROTECTED] X-Mailer: reportbug 3.5 Date: Tue, 22 Feb 2005 14:58:26 +0100 X-Y-GMX-Trusted: 0 Message-Id: [EMAIL PROTECTED] Delivered-To: [EMAIL PROTECTED] X-Spam-Checker-Version: SpamAssassin 2.60-bugs.debian.org_2005_01_02 (1.212-2003-09-23-exp) on spohr.debian.org X-Spam-Status: No, hits=-8.0 required=4.0 tests=BAYES_00,HAS_PACKAGE autolearn=no version=2.60-bugs.debian.org_2005_01_02 X-Spam-Level: Package: umbrello Version: 4:3.3.2-1 Severity: critical Justification: causes serious data loss I have a fairly complex class diagram (around 30 classes ). If I move classes into packages using the logical view and drag'n drop, some of the classes do completely dissapear when dropped into a package. This does not become immideately obvious when looking at the class diagram where they are still displayed, but they are removed from the logical view. After saving and loading the file the classes are also removed from the class diagram so they are completly gone. The classes which are correctly added to the package and which go to /dev/null seem to be random, I can't find a pattern. Additionally moving Interfaces into a package often hangs the application. Fortunatelly I use CVS! Greetings Ben -- System Information: Debian Release: 3.1 APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: i386 (i686) Kernel: Linux 2.6.7 Locale: [EMAIL PROTECTED], [EMAIL PROTECTED] (charmap=ISO-8859-15) (ignored: LC_ALL set to [EMAIL PROTECTED]) Versions of packages umbrello depends on: ii kdelibs4 4:3.3.2-1 KDE core libraries ii libart-2.0-2 2.3.16-6Library of functions for 2D graphi ii libc62.3.2.ds1-20GNU C Library: Shared libraries an ii libfam0c102 2.7.0-6 client library to control the FAM ii libgcc1 1:3.4.3-6 GCC support library ii libice6 4.3.0.dfsg.1-10 Inter-Client Exchange library ii libidn11 0.5.2-3 GNU libidn library, implementation ii libpng12-0 1.2.8rel-1 PNG library - runtime ii libqt3c102-mt3:3.3.3-7 Qt GUI Library (Threaded runtime v ii libsm6 4.3.0.dfsg.1-10 X Window System Session Management ii libstdc++5 1:3.3.5-6 The GNU Standard C++ Library v3 ii libx11-6 4.3.0.dfsg.1-10 X Window System protocol client li ii libxext6 4.3.0.dfsg.1-10 X Window System miscellaneous exte ii libxrender1 0.8.3-7 X Rendering Extension client libra ii xlibs4.3.0.dfsg.1-10 X Keyboard Extension (XKB) configu ii zlib1g 1:1.2.2-4 compression library - runtime -- no debconf information --- Received: (at 296433-close) by bugs.debian.org; 24 Mar 2005 23:53:04 + From [EMAIL PROTECTED] Thu Mar 24 15:53:04 2005 Return-path: [EMAIL PROTECTED] Received: from newraff.debian.org [208.185.25.31] (mail) by spohr.debian.org with esmtp (Exim 3.35 1 (Debian)) id 1DEc8N-f4-00; Thu, 24 Mar 2005 15:53:03 -0800 Received: from katie by newraff.debian.org with local (Exim 3.35 1 (Debian)) id 1DEc2f-0001N6-00; Thu, 24 Mar 2005 18:47:09 -0500 From: Ben Burton [EMAIL PROTECTED] To: [EMAIL PROTECTED] X-Katie: $Revision: 1.55 $ Subject: Bug#296433: fixed in kdesdk 4:3.3.2-2 Message-Id: [EMAIL PROTECTED] Sender: Archive
Bug#301252: xfsprogs - not compiled on unstable
On Thu, Mar 24, 2005 at 06:58:30PM +0100, Bastian Blank wrote: Package: xfsprogs Version: 2.6.26-1 Severity: grave This package seems to be not built on unstable, libhandle requests executable stack, while a unstable build does not do that. I've uploaded recompile-only binNMUs for each of attr, acl, and xfsprogs on i386, which is the only architecture that should be affected. Nathan, please be sure to build your binaries against current unstable systems (chroot or otherwise) in the future when uploading to unstable; otherwise, we end up with binary packages that are not reproducible using current tools. Thanks, -- Steve Langasek postmodern programmer signature.asc Description: Digital signature
Bug#301297: isdnutils-base: device template renders packages.d.o unreachable
Package: isdnutils-base Version: 1:3.3.0.20041110-1 Tags: patch Severity: grave Justification: cuts users from access to packages.debian.org The ISDN device template (/usr/share/isdn/default/device.DEVICE), which is copied to /etc/isdn/ for every device created via /usr/sbin/isdnconfig contains the following section: --- snip --- # The (dummy) IP addresses # # Use 192.25.206.10 for LOCALIP and 10.0.0.2 for REMOTEIP if you have # dynamic IP addresses; with static address fill in the real values! LOCALIP=192.25.206.10 # XXX_ --- snip --- 192.25.206.10 is the IP address of packages.debian.org, and therefore completely unsuited as a dummy address for links with dynamic addresses. Using 192.25.206.10 will result in all requests to packages.d.o being rerouted to the local machine, which is just wrong. An unrouted IP address, such as 10.0.0.1 should be used instead: --- snip --- # The (dummy) IP addresses # # Use 10.0.0.1 for LOCALIP and 10.0.0.2 for REMOTEIP if you have # dynamic IP addresses; with static address fill in the real values! LOCALIP=10.0.0.1 # XXX_ --- snip --- This should really be fixed before the next Debian release, in order to avoid the illusion that packages.d.o is broken... -- WARNING: RAID-6 is currently highly experimental. If you use it, there is no guarantee whatsoever that it won't destroy your data, eat your disk drives, insult your mother, or re-appoint George W. Bush.-- Linux 2.6.10 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#300775: Pam: newer upstream version (0.78) available fixing security bugs
severity 300775 wishlist tags 300775 -security thanks Hi. I've explicitly decided not to upgrade PAM for sarge. I had also decided when 0.77 came out that I didn't see a good reason to take it. Taking a new pam release is a painful process. That said, I'm looking for people to help with PAM. Would you be interested? Are you familiar with pam enough to help try and merge in a new release? -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#236046: marked as done (flying: Please recompile with g++3.3)
Your message dated Thu, 24 Mar 2005 21:02:03 -0500 with message-id [EMAIL PROTECTED] and subject line Bug#236046: fixed in flying 6.20-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) -- Received: (at submit) by bugs.debian.org; 3 Mar 2004 23:36:00 + From [EMAIL PROTECTED] Wed Mar 03 15:36:00 2004 Return-path: [EMAIL PROTECTED] Received: from ms-smtp-01.nyroc.rr.com [24.24.2.55] by spohr.debian.org with esmtp (Exim 3.35 1 (Debian)) id 1AyfuB-0003ec-00; Wed, 03 Mar 2004 15:35:59 -0800 Received: from doctormoo (syr-24-59-96-153.twcny.rr.com [24.59.96.153]) by ms-smtp-01.nyroc.rr.com (8.12.10/8.12.10) with ESMTP id i23NZv0v029852; Wed, 3 Mar 2004 18:35:57 -0500 (EST) Received: by doctormoo (Postfix, from userid 1000) id 941B3454BA; Wed, 3 Mar 2004 18:36:02 -0500 (EST) Content-Type: text/plain; charset=us-ascii MIME-Version: 1.0 Content-Transfer-Encoding: 7bit From: Nathanael Nerode [EMAIL PROTECTED] To: Debian Bug Tracking System [EMAIL PROTECTED] Subject: flying: Please recompile with g++3.3 X-Mailer: reportbug 2.48 Date: Wed, 03 Mar 2004 18:36:02 -0500 Message-Id: [EMAIL PROTECTED] X-Virus-Scanned: Symantec AntiVirus Scan Engine Delivered-To: [EMAIL PROTECTED] X-Spam-Checker-Version: SpamAssassin 2.60-bugs.debian.org_2004_03_01 (1.212-2003-09-23-exp) on spohr.debian.org X-Spam-Status: No, hits=-5.0 required=4.0 tests=HAS_PACKAGE autolearn=no version=2.60-bugs.debian.org_2004_03_01 X-Spam-Level: Package: flying Severity: important This is one of the few packages left which hasn't undergone the 'c102' transition; it still depends on obsolete versions of libstdc++. P.S. While you're uploading a new source package to force recompilation on all architectures, please consider disposing of your Lintian warnings, all of which are easy: (http://lintian.debian.org/reports/mChristian_Meder__bombadil_.html#flying) -- System Information: Debian Release: testing/unstable APT prefers testing APT policy: (990, 'testing'), (90, 'unstable') Architecture: i386 (i686) Kernel: Linux 2.6.3ncn1 Locale: LANG=C, LC_CTYPE=C --- Received: (at 236046-close) by bugs.debian.org; 25 Mar 2005 02:09:07 + From [EMAIL PROTECTED] Thu Mar 24 18:09:07 2005 Return-path: [EMAIL PROTECTED] Received: from newraff.debian.org [208.185.25.31] (mail) by spohr.debian.org with esmtp (Exim 3.35 1 (Debian)) id 1DEeG2-0004fV-00; Thu, 24 Mar 2005 18:09:07 -0800 Received: from katie by newraff.debian.org with local (Exim 3.35 1 (Debian)) id 1DEe9D-0001kV-00; Thu, 24 Mar 2005 21:02:03 -0500 From: Christian Meder [EMAIL PROTECTED] To: [EMAIL PROTECTED] X-Katie: $Revision: 1.55 $ Subject: Bug#236046: fixed in flying 6.20-5 Message-Id: [EMAIL PROTECTED] Sender: Archive Administrator [EMAIL PROTECTED] Date: Thu, 24 Mar 2005 21:02:03 -0500 Delivered-To: [EMAIL PROTECTED] X-Spam-Checker-Version: SpamAssassin 2.60-bugs.debian.org_2005_01_02 (1.212-2003-09-23-exp) on spohr.debian.org X-Spam-Status: No, hits=-6.0 required=4.0 tests=BAYES_00,HAS_BUG_NUMBER autolearn=no version=2.60-bugs.debian.org_2005_01_02 X-Spam-Level: X-CrossAssassin-Score: 3 Source: flying Source-Version: 6.20-5 We believe that the bug you reported is fixed in the latest version of flying, which is due to be installed in the Debian FTP archive: flying_6.20-5.diff.gz to pool/main/f/flying/flying_6.20-5.diff.gz flying_6.20-5.dsc to pool/main/f/flying/flying_6.20-5.dsc flying_6.20-5_i386.deb to pool/main/f/flying/flying_6.20-5_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. Christian Meder [EMAIL PROTECTED] (supplier of updated flying 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, 25 Mar 2005 00:28:08 +0100 Source: flying Binary: flying Architecture: source i386 Version: 6.20-5 Distribution: unstable Urgency: low Maintainer: Christian Meder [EMAIL PROTECTED] Changed-By: Christian Meder [EMAIL PROTECTED] Description: flying -
Bug#289182: kino endianness issues on powerpc
On Fri, Mar 25, 2005 at 01:38:27AM +0100, Daniel Kobras wrote: On Tue, Mar 22, 2005 at 08:36:01PM +, Paul Brossier wrote: there is probably a better mean to do so though, ie checking what type of conversion is needed according to libavcodec, but it does effectively fixes the XV Display of kino. Actually, we should probably check the value of component_order[] in the struct returned by XvListImageFormats() and shuffle components as appropriate, but from the feedback so far, apparently nowadays it is sufficient to keep the order of YUV components fixed, independent of host arch. I've attached a patch to this effect, and would welcome feedback from testers. it works perfectly on powerpc, a much nicer solution indeed. and the first patch was wrong, the image was slightly more redish. audio seems to work better now. there are a few glitches but at least it's not white noise. oh and export to mpeg2 and wav bot work. Great. We're getting closer, it seems. Does the video part of mpeg2 export also work correctly now? oh yes, very well. and the video filters too. bye, paul -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Processed: Re: Bug#300440: post-installation returns error code 21 if /usr/share/doc/menu/html does not exist
Processing commands for [EMAIL PROTECTED]: tags 300440 +patch Bug#300440: post-installation returns error code 21 if /usr/share/doc/menu/html does not exist There were no tags set. Tags added: patch thanks Stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#300440: post-installation returns error code 21 if /usr/share/doc/menu/html does not exist
tags 300440 +patch
thanks
Hi Stefan,
I've tracked this bug and with the vorlon and fatalerror help
i reproduced it this way:
- Install dhelp package;
- Install doc-linux-it package;
- Remove or move /usr/share/doc;
- dpkg-reconfigure doc-linux-it. =)
There's patch below that i think can help you fixing this
problem. If you can't upload a new package soon, since it's a RC
bug let me known and i'll do a NMU with this patch.
Hope that helps,
Gustavo Franco -- [EMAIL PROTECTED]
--- dhelp_parse.c 2005-03-24 21:00:36.0 -0300
+++ dhelp_parse.c 2005-03-24 21:00:41.0 -0300
@@ -776,6 +776,7 @@
int main (int argc, char *argv[])
{
int i;
+ DIR *dir;
char zw[MAXPATHLEN];
char resolv_name[MAXPATHLEN];
@@ -794,6 +795,14 @@
}
else
{
+if ((dir = opendir (DOCDIR)) == NULL)
+{
+ fprintf (stderr, dhelp_parse: I can't open %s, the package
+ documentation won't be registered. It's non-fatal.\n\n,
DOCDIR);
+ return (0);/* do not break postinst/postrm scripts */
+}
+closedir (dir);
+
mkdir (/var/lib/dhelp/, 0755);
for (i=2; i argc; i++)
{
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Processed: kbabel patched
Processing commands for [EMAIL PROTECTED]: severity 289646 important Bug#289646: kbabel: crash with some .po file Severity set to `important'. thanks mate 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#289646: kbabel patched
severity 289646 important thanks mate Hi. I've uploaded a new kdesdk with the s/check/checkWord/ patch, so I'm lowering the severity of this bug. I'm leaving it open however, since kbabel was in fact using the kdelibs API as documented -- in theory kbabel was doing nothing wrong, so the problem would seem to be in kdelibs (and thus still unfixed at the root of the problem). Ben. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#300703: autofs: Upgrade fails
I just saw the same problem upgrading to sarge. I had a look around and
it looks like the script simply wasn't written to be run under set -e.
When a script uses $? liberally to explicitly test success/failure of
commands, you can't just enable -e and expect it to work. You have
to carefully inspect it to make sure that all failure cases are handled
so that they don't cause the script to bomb out when it shouldn't.
I made an attempt to do this here. No guarantees that this catches
all the problems but it does let me finish configuring the package.
--
Visit Openswan at http://www.openswan.org/
Email: Herbert Xu ~{PmVHI~} [EMAIL PROTECTED]
Home Page: http://gondor.apana.org.au/~herbert/
PGP Key: http://gondor.apana.org.au/~herbert/pubkey.txt
--- autofs.old 2005-03-25 14:09:01.0 +1100
+++ autofs 2005-03-25 14:18:43.0 +1100
@@ -448,11 +448,11 @@
echo
echo -n $Unmounting loopback filesystem $match:
loopdev=`LC_ALL=C grep $l /proc/mounts | awk '{print $1}'`
- umount -d $match
- if [ $? -eq 0 ]; then
+ if umount -d $match; then
echo done
else
echo failed ($?)
+ exit 1
fi
fi
done
@@ -470,11 +470,11 @@
if [ -n $match ]; then
echo
echo -n $Unmounting loopback filesystem $match:
- umount -d $match
- if [ $? -eq 0 ]; then
+ if umount -d $match; then
echo done
else
echo failed ($?)
+ exit 1
fi
fi
done
@@ -629,13 +629,12 @@
mnt=`echo $rest | sed 's/^.* \(\/[^ ]*\) [A-Za-z].*$/\1/'`
pidfile=/var/run/autofs/`echo $mnt | sed 's,/,_,g'`.pid
- start-stop-daemon --start --pidfile $pidfile --quiet \
+ if ! start-stop-daemon --start --pidfile $pidfile --quiet \
--exec $DAEMON -- --pid-file=$pidfile $rest
-
- if [ $? -ne 0 ]
then
echo
echo failed to start automount point $mnt
+ exit 1
fi
done
@@ -658,8 +657,8 @@
start-stop-daemon --stop --quiet \
--retry USR2/$DAEMON_EXIT_WAIT \
- --pidfile $file --exec $DAEMON
- ret=$?
+ --pidfile $file --exec $DAEMON ||
+ ret=$?
case $ret in
0)
@@ -675,7 +674,7 @@
;;
*)
echo -n -e \
- \n Strange start-stop-daemon exit status: $?
+ \n Strange start-stop-daemon exit status: $ret
;;
esac
fi
@@ -718,12 +717,12 @@
mnt=`echo $rest | sed 's/^.* \(\/[^ ]*\)
[A-Za-z].*$/\1/'`
pidfile=/var/run/autofs/`echo $mnt | sed 's,/,_,g'`.pid
- start-stop-daemon --start --pidfile $pidfile --quiet \
+ if ! start-stop-daemon --start --pidfile $pidfile
--quiet \
--exec $DAEMON -- --pid-file=$pidfile $rest
-
- if [ $? -ne 0 ]; then
+ then
echo
echo failed to start automount point $mnt
+ exit 1
else
echo Started automounter: $mnt
fi
Processed: Fixed in upload of glibc 2.3.4-2 to experimental
Processing commands for [EMAIL PROTECTED]: tag 300806 + fixed-in-experimental Bug#300806: (Seemingly) All programs fail to start, with the error message: relocation error: /lib/tls/i686/cmov/libc.so.6: symbol _dl_starting_up, version GLIBC_PRIVATE not defined in file ld-linux.so.2 with link time reference There were no tags set. Tags added: fixed-in-experimental tag 300842 + fixed-in-experimental Bug#300842: libc6: upgrade fails in i386 chroot on amd64 system Tags were: experimental Tags added: fixed-in-experimental 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#300842: marked as done (libc6: upgrade fails in i386 chroot on amd64 system)
Your message dated Fri, 25 Mar 2005 13:36:50 +0900 with message-id [EMAIL PROTECTED] and subject line Processed: Fixed in upload of glibc 2.3.4-2 to experimental 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) -- Received: (at submit) by bugs.debian.org; 22 Mar 2005 07:55:26 + From [EMAIL PROTECTED] Mon Mar 21 23:55:26 2005 Return-path: [EMAIL PROTECTED] Received: from lns-vlq-36-gre-82-253-74-146.adsl.proxad.net (localhost.localdomain) [82.253.74.146] by spohr.debian.org with esmtp (Exim 3.35 1 (Debian)) id 1DDeEX-0002Ud-00; Mon, 21 Mar 2005 23:55:25 -0800 Received: by localhost.localdomain (Postfix, from userid 1001) id E129D1AEC20F; Tue, 22 Mar 2005 08:55:22 +0100 (CET) Content-Type: text/plain; charset=us-ascii MIME-Version: 1.0 Content-Transfer-Encoding: 7bit From: [EMAIL PROTECTED] To: Debian Bug Tracking System [EMAIL PROTECTED] Subject: libc6: upgrade fails in i386 chroot on amd64 system X-Mailer: reportbug 3.8 Date: Tue, 22 Mar 2005 08:55:22 +0100 Message-Id: [EMAIL PROTECTED] Delivered-To: [EMAIL PROTECTED] X-Spam-Checker-Version: SpamAssassin 2.60-bugs.debian.org_2005_01_02 (1.212-2003-09-23-exp) on spohr.debian.org X-Spam-Status: No, hits=-6.4 required=4.0 tests=BAYES_00,HAS_PACKAGE, NO_REAL_NAME autolearn=no version=2.60-bugs.debian.org_2005_01_02 X-Spam-Level: Package: libc6 Version: 2.3.2.ds1-20.0.0.1.pure64 Severity: critical Tags: experimental Justification: breaks the whole system Hi, here is the problem: Preparing to replace libc6 2.3.2.ds1-20 (using .../libc6_2.3.4-1_i386.deb) ... Unpacking replacement libc6 ... Setting up libc6 (2.3.4-1) ... dpkg: relocation error: /lib/tls/i686/cmov/libc.so.6: symbol _dl_starting_up, version GLIBC_PRIVATE not defined in file ld-linux.so.2 with link time reference cat: relocation error: /lib/tls/i686/cmov/libc.so.6: symbol _dl_starting_up, version GLIBC_PRIVATE not defined in file ld-linux.so.2 with link time reference dpkg: error processing libc6 (--configure): subprocess post-installation script returned error exit status 127 -- System Information: Debian Release: 3.1 Architecture: amd64 (x86_64) Kernel: Linux 2.6.10-9-amd64-k8 Locale: [EMAIL PROTECTED], [EMAIL PROTECTED] (charmap=ISO-8859-15) Versions of packages libc6 depends on: ii libdb1-compat 2.1.3-7The Berkeley database routines [gl -- no debconf information --- Received: (at 300842-done) by bugs.debian.org; 25 Mar 2005 04:36:51 + From [EMAIL PROTECTED] Thu Mar 24 20:36:51 2005 Return-path: [EMAIL PROTECTED] Received: from omega.webmasters.gr.jp (webmasters.gr.jp) [218.44.239.78] by spohr.debian.org with esmtp (Exim 3.35 1 (Debian)) id 1DEgZ0-0003og-00; Thu, 24 Mar 2005 20:36:51 -0800 Received: from omega.webmasters.gr.jp (localhost [127.0.0.1]) by webmasters.gr.jp (Postfix) with ESMTP id 36C22DEB1E; Fri, 25 Mar 2005 13:36:50 +0900 (JST) Date: Fri, 25 Mar 2005 13:36:50 +0900 Message-ID: [EMAIL PROTECTED] From: GOTO Masanori [EMAIL PROTECTED] To: [EMAIL PROTECTED], [EMAIL PROTECTED] Subject: Re: Processed: Fixed in upload of glibc 2.3.4-2 to experimental In-Reply-To: [EMAIL PROTECTED] References: [EMAIL PROTECTED] [EMAIL PROTECTED] User-Agent: Wanderlust/2.9.9 (Unchained Melody) SEMI/1.14.3 (Ushinoya) FLIM/1.14.3 (=?ISO-8859-4?Q?Unebigory=F2mae?=) APEL/10.3 Emacs/21.2 (i386-debian-linux-gnu) MULE/5.0 (SAKAKI) MIME-Version: 1.0 (generated by SEMI 1.14.3 - Ushinoya) Content-Type: text/plain; charset=US-ASCII Delivered-To: [EMAIL PROTECTED] X-Spam-Checker-Version: SpamAssassin 2.60-bugs.debian.org_2005_01_02 (1.212-2003-09-23-exp) on spohr.debian.org X-Spam-Status: No, hits=-3.0 required=4.0 tests=BAYES_00 autolearn=no version=2.60-bugs.debian.org_2005_01_02 X-Spam-Level: X-CrossAssassin-Score: 2 At Thu, 24 Mar 2005 20:03:06 -0800, Debian Bug Tracking System wrote: tag 300806 + fixed-in-experimental Bug#300806: (Seemingly) All programs fail to start, with the error message: relocation error: /lib/tls/i686/cmov/libc.so.6: symbol _dl_starting_up, version GLIBC_PRIVATE not defined in file ld-linux.so.2 with link time reference There were no tags set. Tags added: fixed-in-experimental tag 300842 + fixed-in-experimental Bug#300842: libc6: upgrade fails in i386 chroot on amd64 system Tags were: experimental Tags added: fixed-in-experimental 2.3.4-1 is existed only in experimental. I close those bugs. Regards, --
