Bug#386833: patch
merge 384146 386833
tags 384146 patch
tags 386833 patch
thanks for all the fish
---
Attached is a patch which gets the package building again.
Basically I split the ENUM_DEFINITION macro into a ENUM_DEFINITION_BEGIN
and a ENUM_DEFINITION_END so that the enums can be defined by the _BEGIN
and instantiated by the _END.
Thanks,
stew
Only in plptools-0.15.orig/debian: klipsi.1.in
Only in plptools-0.15.orig/debian: kpsion.1.in
Only in plptools-0.15.orig/etc: plptools.spec
Only in plptools-0.15.orig/include: config.h
Only in plptools-0.15.orig/include: config.h.in~
Only in plptools-0.15.orig/kde2/doc/de: index.cache.bz2
Only in plptools-0.15.orig/kde2/doc/en: index.cache.bz2
Only in plptools-0.15.orig/kde2/klipsi: dummy.cpp
diff -ru plptools-0.15.orig/lib/Enum.h plptools-0.15/lib/Enum.h
--- plptools-0.15.orig/lib/Enum.h 2005-08-06 08:10:18.0 -0400
+++ plptools-0.15/lib/Enum.h 2006-09-22 01:41:15.0 -0400
@@ -304,14 +304,16 @@
* The definition of the static variable holding the static
* data for this Enumeration wrapper.
*/
-#define ENUM_DEFINITION(EnumName, initWith) \
-template Enum EnumName ::sdata Enum EnumName ::staticData; \
+#define ENUM_DEFINITION_BEGIN(EnumName, initWith) \
/**\
* actual definition of the constructor for the static data. \
* This is called implicitly by the definition above. \
*/\
template EnumEnumName::sdata::sdata() :\
-name(#EnumName),defaultValue(initWith)
+name(#EnumName),defaultValue(initWith) {
+
+#define ENUM_DEFINITION_END(EnumName) \
+} template Enum EnumName ::sdata Enum EnumName ::staticData;
/**
* Writes enumeration's string representation.
diff -ru plptools-0.15.orig/lib/rfsv.cc plptools-0.15/lib/rfsv.cc
--- plptools-0.15.orig/lib/rfsv.cc 2004-05-31 09:37:08.0 -0400
+++ plptools-0.15/lib/rfsv.cc 2006-09-22 01:42:32.0 -0400
@@ -33,7 +33,7 @@
using namespace std;
-ENUM_DEFINITION(rfsv::errs, rfsv::E_PSI_GEN_NONE) {
+ENUM_DEFINITION_BEGIN(rfsv::errs, rfsv::E_PSI_GEN_NONE)
stringRep.add(rfsv::E_PSI_GEN_NONE,N_(no error));
stringRep.add(rfsv::E_PSI_GEN_FAIL,N_(general));
stringRep.add(rfsv::E_PSI_GEN_ARG, N_(bad argument));
@@ -108,7 +108,8 @@
stringRep.add(rfsv::E_PSI_FILE_HANDLE, N_(bad handle));
stringRep.add(rfsv::E_PSI_NOT_SIBO,N_(invalid operation for RFSV16));
stringRep.add(rfsv::E_PSI_INTERNAL,N_(libplp internal error));
-}
+ENUM_DEFINITION_END(rfsv::errs)
+
const char *rfsv::getConnectName(void) {
return SYS$RFSV;
diff -ru plptools-0.15.orig/lib/rfsvfactory.cc plptools-0.15/lib/rfsvfactory.cc
--- plptools-0.15.orig/lib/rfsvfactory.cc 2004-05-31 09:37:08.0 -0400
+++ plptools-0.15/lib/rfsvfactory.cc 2006-09-22 01:44:18.0 -0400
@@ -37,14 +37,14 @@
using namespace std;
-ENUM_DEFINITION(rfsvfactory::errs, rfsvfactory::FACERR_NONE) {
+ENUM_DEFINITION_BEGIN(rfsvfactory::errs, rfsvfactory::FACERR_NONE)
stringRep.add(rfsvfactory::FACERR_NONE, N_(no error));
stringRep.add(rfsvfactory::FACERR_COULD_NOT_SEND, N_(could not send version request));
stringRep.add(rfsvfactory::FACERR_AGAIN, N_(try again));
stringRep.add(rfsvfactory::FACERR_NOPSION,N_(no psion connected));
stringRep.add(rfsvfactory::FACERR_PROTVERSION,N_(wrong protocol version));
stringRep.add(rfsvfactory::FACERR_NORESPONSE, N_(no response from ncpd));
-}
+ENUM_DEFINITION_END(rfsvfactory::errs)
rfsvfactory::rfsvfactory(ppsocket *_skt) : serNum(0)
{
diff -ru plptools-0.15.orig/lib/rpcs.cc plptools-0.15/lib/rpcs.cc
--- plptools-0.15.orig/lib/rpcs.cc 2006-05-01 16:35:50.0 -0400
+++ plptools-0.15/lib/rpcs.cc 2006-09-22 01:44:29.0 -0400
@@ -37,7 +37,7 @@
using namespace std;
-ENUM_DEFINITION(rpcs::machs, rpcs::PSI_MACH_UNKNOWN) {
+ENUM_DEFINITION_BEGIN(rpcs::machs, rpcs::PSI_MACH_UNKNOWN)
stringRep.add(rpcs::PSI_MACH_UNKNOWN, N_(Unknown device));
stringRep.add(rpcs::PSI_MACH_PC,N_(PC));
stringRep.add(rpcs::PSI_MACH_MC,N_(MC));
@@ -49,16 +49,17 @@
stringRep.add(rpcs::PSI_MACH_S3C, N_(Series 3c));
stringRep.add(rpcs::PSI_MACH_S5,N_(Series 5));
stringRep.add(rpcs::PSI_MACH_WINC, N_(WinC));
-}
+ENUM_DEFINITION_END(rpcs::machs)
-ENUM_DEFINITION(rpcs::batterystates, rpcs::PSI_BATT_DEAD) {
+ENUM_DEFINITION_BEGIN(rpcs::batterystates, rpcs::PSI_BATT_DEAD)
stringRep.add(rpcs::PSI_BATT_DEAD,N_(Empty));
stringRep.add(rpcs::PSI_BATT_VERYLOW, N_(Very Low));
stringRep.add(rpcs::PSI_BATT_LOW, N_(Low));
stringRep.add(rpcs::PSI_BATT_GOOD,N_(Good));
-}
+ENUM_DEFINITION_END(rpcs::batterystates)
-ENUM_DEFINITION(rpcs::languages, rpcs::PSI_LANG_TEST) {
+
+ENUM_DEFINITION_BEGIN(rpcs::languages, rpcs::PSI_LANG_TEST)
stringRep.add(rpcs::PSI_LANG_TEST, N_(Test));
stringRep.add(rpcs::PSI_LANG_en_GB, N_(English));
Processed: patch
Processing commands for [EMAIL PROTECTED]: merge 384146 386833 Bug#384146: plptools: FTBFS (amd64): conflicting declaration 'typedef long long unsigned int u_int64_t' Bug#386833: plptools: FTBFS (i386/gcc-4.1) bad Merged 384146 386833. tags 384146 patch Bug#384146: plptools: FTBFS (amd64): conflicting declaration 'typedef long long unsigned int u_int64_t' There were no tags set. Bug#386833: plptools: FTBFS (i386/gcc-4.1) bad Tags added: patch tags 386833 patch Bug#386833: plptools: FTBFS (i386/gcc-4.1) bad Tags were: patch Bug#384146: plptools: FTBFS (amd64): conflicting declaration 'typedef long long unsigned int u_int64_t' Tags added: patch thanks for all the fish Unknown command or malformed arguments to command. --- Unknown command or malformed arguments to command. Attached is a patch which gets the package building again. Unknown command or malformed arguments to command. Basically I split the ENUM_DEFINITION macro into a ENUM_DEFINITION_BEGIN Unknown command or malformed arguments to command. and a ENUM_DEFINITION_END so that the enums can be defined by the _BEGIN Unknown command or malformed arguments to command. Too many unknown commands, stopping 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#388708: apt: Upgrading to this version makes status file unparseable
Package: apt Version: 0.6.46 Severity: grave #_ aptitude -u ... upgrade ... #_ aptitude -vvv upgrade Reading package lists... Error! E: Unable to parse package file /var/lib/dpkg/status (1) E: The package lists or status file could not be parsed or opened. Reading package lists... Error! E: Unable to parse package file /var/lib/dpkg/status (1) E: The package lists or status file could not be parsed or opened. [1]22606 exit 255 aptitude -vvv upgrade Tested this on two machines. Downgrading to 0.6.45 fixes the bug. Look below for a sequence of action: #_ dpkg -i apt_0.6.46_i386.deb (Reading database ... 333632 files and directories currently installed.) Preparing to replace apt 0.6.45 (using apt_0.6.46_i386.deb) ... Unpacking replacement apt ... Setting up apt (0.6.46) ... #_ apt-cache policy apt E: Unable to parse package file /var/lib/dpkg/status (1) [1]24419 exit 100 apt-cache policy apt #_ dpkg -i apt_0.6.45_i386.deb dpkg - warning: downgrading apt from 0.6.46 to 0.6.45. (Reading database ... 333635 files and directories currently installed.) Preparing to replace apt 0.6.46 (using apt_0.6.45_i386.deb) ... Unpacking replacement apt ... Setting up apt (0.6.45) ... #_ apt-cache policy apt apt: Installed: 0.6.45 Candidate: 0.6.46 Version table: 0.6.46 0 990 http://glaurung.internal.golden-gryphon.com sid/main Packages 990 http://ftp.debian.org sid/main Packages 0.6.45exp2 0 1 http://ftp.debian.org experimental/main Packages *** 0.6.45 0 100 /var/lib/dpkg/status -- System Information: Debian Release: testing/unstable APT prefers unstable APT policy: (990, 'unstable'), (500, 'stable'), (1, 'experimental') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.17.13-mh5-skas3-v9-pre9 Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) (ignored: LC_ALL set to en_US.UTF-8) manoj strace.log Description: strace log Versions of packages apt depends on: ii libc6 2.3.6.ds1-4 GNU C Library: Shared libraries ii libgcc1 1:4.2-20060709-1 GCC support library ii libstdc++6 4.1.1-13 The GNU Standard C++ Library v3 Versions of packages apt recommends: ii debian-archive-keyring2006.01.18 GnuPG archive keys of the Debian a -- no debconf information -- Sex is like snow... You never know how many inches you're going to get or how long it will last. Manoj Srivastava [EMAIL PROTECTED]http://www.golden-gryphon.com/ 1024D/BF24424C print 4966 F272 D093 B493 410B 924B 21BA DABB BF24 424C
Bug#388609: teapop-mysql: purging the package fails (update-inetd unavailable)
Bill Allombert wrote: Package: teapop-mysql Version: 0.3.7-4.1+b1 Severity: serious Hello Nick, There is an error when attempting to purge teapop-mysql: Removing teapop-mysql ... Purging configuration files for teapop-mysql ... /var/lib/dpkg/info/teapop-mysql.postrm: line 28: update-inetd: command not found dpkg: error processing teapop-mysql (--purge): subprocess post-removal script returned error exit status 127 update-inetd is not provided by an essential package. See Policy 7.2: Note, however, that the `postrm' cannot rely on any non-essential packages to be present during the `purge' phase. Cheers, Ah. Bother. Thanks, I'll have a look. Cheers, Nick -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#387798: marked as done (libgutils1-dev: broken symlink (missing dep?))
Your message dated Thu, 21 Sep 2006 23:32:12 -0700 with message-id [EMAIL PROTECTED] and subject line Bug#387798: fixed in sg3-utils 1.21-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) ---BeginMessage--- Package: libsgutils1-dev Version: 1.21-1 When testing libsgutils1-dev with piuparts, we found the following problem: 0m3.6s ERROR: Broken symlinks: /usr/lib/libsgutils.so - libsgutils.so.1.0.0 I suspect that the package should depend on the non -dev package, but I'm not familiar with the intricacies of shared library packaging, sorry. The full piuparts log file is at: http://piuparts.cs.helsinki.fi/bugged/libsgutils1-dev_1.21-1.log -- Close your mind to stress and pain, hack till you're no longer sane. ---End Message--- ---BeginMessage--- Source: sg3-utils Source-Version: 1.21-2 We believe that the bug you reported is fixed in the latest version of sg3-utils, which is due to be installed in the Debian FTP archive: libsgutils1-dev_1.21-2_i386.deb to pool/main/s/sg3-utils/libsgutils1-dev_1.21-2_i386.deb libsgutils1_1.21-2_i386.deb to pool/main/s/sg3-utils/libsgutils1_1.21-2_i386.deb sg3-utils_1.21-2.diff.gz to pool/main/s/sg3-utils/sg3-utils_1.21-2.diff.gz sg3-utils_1.21-2.dsc to pool/main/s/sg3-utils/sg3-utils_1.21-2.dsc sg3-utils_1.21-2_i386.deb to pool/main/s/sg3-utils/sg3-utils_1.21-2_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. Eric Schwartz (Skif) [EMAIL PROTECTED] (supplier of updated sg3-utils 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, 22 Sep 2006 00:20:28 -0600 Source: sg3-utils Binary: libsgutils1-dev libsgutils1 sg3-utils Architecture: source i386 Version: 1.21-2 Distribution: unstable Urgency: low Maintainer: Eric Schwartz (Skif) [EMAIL PROTECTED] Changed-By: Eric Schwartz (Skif) [EMAIL PROTECTED] Description: libsgutils1 - Utilities for working with generic SCSI devices (shared libraries libsgutils1-dev - Utilities for working with generic SCSI devices (developer files) sg3-utils - Utilities for working with generic SCSI devices Closes: 387798 Changes: sg3-utils (1.21-2) unstable; urgency=low . * Added Depends on libsgutils1 to libsgutils1-dev (closes: #387798) Files: eb307222d389d41011441fd738168317 625 admin optional sg3-utils_1.21-2.dsc 8e50e61947d8d98eb27f4ebaa329d0be 4005 admin optional sg3-utils_1.21-2.diff.gz 176d0edac2088c635b752ea8ac2a7260 451580 admin optional sg3-utils_1.21-2_i386.deb d43c0f43a88a5843e65baa6011102c63 49618 libs optional libsgutils1_1.21-2_i386.deb c16157e852c1c46bafe7f6b0183940dd 63186 devel optional libsgutils1-dev_1.21-2_i386.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.2.2 (GNU/Linux) iD8DBQFFE4HK661uXLrFnjkRAjKDAJ9T7fhHXA3pA/rC0Uu13Dpmn35tVwCeKQrw 7rLS7jBHbVSiwPM1yo3VDVY= =P/7d -END PGP SIGNATURE- ---End Message---
Bug#388695: geda-gschem: Probably parenthesis mismatch in errors in gschem
On Fri, Sep 22, 2006 at 03:22:17PM +1000, Hamish Moffatt wrote: On Thu, Sep 21, 2006 at 11:12:42PM -0400, H. S. wrote: (here is the bug again here for geda-gschem, instead of for geda) Thanks. geda-gschem 20060906 should be in etch in a day or two. Not if this RC bug is open, it won't be. system-gafrc is provided by geda-symbols, which is already updated in etch. However system-gschemrc is not yet. I suspect the skew between them is causing the problem. I will tighten the dependencies in the future. If you're certain that this is the cause, which package needs to be updated with added conflicts -- geda-symbols or geda-gschem? If it's geda-symbols, could you please reassign this bug there? If the change needs to be made to geda-gschem, please say so and I'll override this RC bug for the update into testing for now. -- Steve Langasek Give me a lever long enough and a Free OS Debian Developer to set it on, and I can move the world. [EMAIL PROTECTED] http://www.debian.org/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#388521: libnotify-dev: Missing depedancies on libgtk2.0-dev
tags 388521 + confirmed, pending thanks. Thanks for the report. There is a fix in SVN and an upload is supposed to happen soon. Ciao ~marco signature.asc Description: Questa è una parte del messaggio firmata digitalmente
Processed: Re: If the problem is that the user doesn't know he won't be able to reboot...
Processing commands for [EMAIL PROTECTED]: tags 345931 + patch Bug#345931: System fails to boot after updating boot sector from grub interactive shell Tags were: upstream 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#345931: If the problem is that the user doesn't know he won't be able to reboot...
tags 345931 + patch
thanks
In my previous response, I missed this post to this bug list.
On Wed, 13 Sep 2006, Marc Fargas wrote:
Steve Langasek [EMAIL PROTECTED] writes:
Surely this is still a bug in the grub shell for failing to notice that it
had rendered the system unbootable?
Grub shell is supposed to be used by experienced users, and if the
big problem is that setup() doesn't copy those files to /boot/ there
are two lines of action:
a) On a call to setup() output a nice warning message that clearly
says that the files MUST be manually copied by the user encouragin the
use of grub-install
b) On a call to setup() take care of copying the files.
I'd vote for option a, with that warning in place the bug would be ok,
right? I've never touched inside grub but I can try to patch it if you
select A, and less maybe for B ;) [so, is option A ok for closing the
bug? at least the user knows that he/she won't boot again... hehe]
I concur and enclose a patch which is the output of:
interdiff -z grub_0.97-15.diff.gz grub_0.97-15.0pre1.diff.gz
(This also includes the small patch for #385980 suggested by Joey Hess.)
On Thu, 14 Sep 2006, Jason Thomas wrote:
option C, we create a way to extract the version information from every
grub file. So that the grub shell can check that its version matches
the stage files and if not generate an ERROR message.
Note that stage1 is a boot sector and so contains precious little
space for such version information. Implementing this option seems
quite difficult to me.
Regards,
Kapil.
--
diff -u grub-0.97/debian/patches/00list grub-0.97/debian/patches/00list
--- grub-0.97/debian/patches/00list
+++ grub-0.97/debian/patches/00list
@@ -19,6 +19,7 @@
mprotect.diff
savedefault.diff
intelmac.diff
+setup_warn_version.diff
# We aren't building amd64 binaries, see #244498
#fix_amd64_compile.diff
diff -u grub-0.97/debian/changelog grub-0.97/debian/changelog
--- grub-0.97/debian/changelog
+++ grub-0.97/debian/changelog
@@ -1,3 +1,14 @@
+grub (0.97-15.0pre1) unstable; urgency=low
+
+ * Non-Maintainer Upload.
+ * debian/rules: Fixed up clean target as suggested by Joey Hess.
+(Closes #385980)
+ * debian/patches/setup_warn_version.diff: Patch stage2/builtins.c
+to warn user who uses setup from the grub shell.
+(Closes: #345931)
+
+ -- Kapil Hari Paranjape [EMAIL PROTECTED] Fri, 22 Sep 2006 11:45:09 +0530
+
grub (0.97-15) unstable; urgency=low
* Remove bashism from update-grub wrapper.
diff -u grub-0.97/debian/rules grub-0.97/debian/rules
--- grub-0.97/debian/rules
+++ grub-0.97/debian/rules
@@ -181,7 +181,7 @@
-( cd docs rm -rf grub multiboot )
# remove files that will be change due our automake and autoconf
rebuilding
- -rm -f $(find . -name 'Makefile.in' -o \
+ -rm -f $(shell find . -name 'Makefile.in' -o \
-name 'aclocal.m4' -o \
-name 'configure')
only in patch2:
unchanged:
--- grub-0.97.orig/debian/patches/setup_warn_version.diff
+++ grub-0.97/debian/patches/setup_warn_version.diff
@@ -0,0 +1,42 @@
+--- grub-0.97/stage2/builtins.c.orig 2005-02-16 03:28:23.0 +0530
grub-0.97/stage2/builtins.c2006-09-22 11:40:00.0 +0530
+@@ -3798,10 +3798,19 @@
+ char *stage2_arg = 0;
+ char *prefix = 0;
+
++ auto void warn ();
+ auto int check_file (char *file);
+ auto void sprint_device (int drive, int partition);
+ auto int embed_stage1_5 (char * stage1_5, int drive, int partition);
+-
++
++ /* Warn the user that stage files are version specific */
++ void warn()
++{
++ grub_printf(WARNING:The stage{1,1_5,2} files are version specific.\n);
++ grub_printf(The tests below only check the existence and not the
version.\n);
++ grub_printf(Use the \grub-install\ command if you are not sure.\n);
++}
++
+ /* Check if the file FILE exists like Autoconf. */
+ int check_file (char *file)
+ {
+@@ -3951,6 +3960,7 @@
+ `--prefix', attempt /boot/grub and /grub. */
+ /* NOTE: It is dangerous to run this command without `--prefix' in the
+ grub shell, since that affects `--stage2'. */
++ warn();
+ if (! prefix)
+ {
+ prefix = /boot/grub;
+@@ -4082,6 +4092,10 @@
+If you install GRUB under the grub shell and you cannot unmount the
+partition where GRUB images reside, specify the option `--stage2'
+to tell GRUB the file name under your OS.
++ WARNING: In order for this to work GRUB needs to find the images
++ \stage1\ and \stage2\ (or \stage1_5\) corresponding to its
++ current version in the locations specified by INSTALL_DEVICE
++ (or IMAGE_DEVICE if specified; or STAGE2_FILE if specified).
+ };
+
+
signature.asc
Description: Digital signature
Processed: setting forwarded to upstream bug
Processing commands for [EMAIL PROTECTED]: forwarded 388125 https://bugs.freedesktop.org/show_bug.cgi?id=8392 Bug#388125: osgcal FTBFS (sparc): bus error in xvfb Forwarded-to-address changed from http://lists.freedesktop.org/archives/xorg/2006-September/018251.html to https://bugs.freedesktop.org/show_bug.cgi?id=8392. 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#388711: ldap-account-manager failure when open in web browser and login
Package: ldap-account-manager Version: 1.0.4-1 Severity: grave Justification: renders package unusable Today, after I upgrade my etch, the ldap-account-manager is unusable. When I open http://127.0.0.1/lam; in the web browser, I can not get correct web page and get some warning message, as below. Warning: Wrong parameter count for class_exists() in /usr/share/php/fpdf/fpdf.php on line 12 Warning: session_start(): Cannot send session cookie - headers already sent by (output started at /usr/share/php/fpdf/fpdf.php:12) in /usr/share/ldap-account-manager/templates/login.php on line 89 Warning: session_start(): Cannot send session cache limiter - headers already sent (output started at /usr/share/php/fpdf/fpdf.php:12) in /usr/share/ldap-account-manager/templates/login.php on line 89 Warning: Cannot modify header information - headers already sent by (output started at /usr/share/php/fpdf/fpdf.php:12) in /usr/share/ldap-account-manager/lib/config.inc on line 53 When I input the password and press login button, I can not enter any correct page and get messages as below. Warning: Wrong parameter count for class_exists() in /usr/share/php/fpdf/fpdf.php on line 12 Warning: session_start(): Cannot send session cookie - headers already sent by (output started at /usr/share/php/fpdf/fpdf.php:12) in /usr/share/ldap-account-manager/templates/login.php on line 89 Warning: session_start(): Cannot send session cache limiter - headers already sent (output started at /usr/share/php/fpdf/fpdf.php:12) in /usr/share/ldap-account-manager/templates/login.php on line 89 Warning: Cannot modify header information - headers already sent by (output started at /usr/share/php/fpdf/fpdf.php:12) in /usr/share/ldap-account-manager/lib/config.inc on line 53 So I can not use ldap-account-manager to manage my ldap now. -- System Information: Debian Release: testing/unstable APT prefers testing APT policy: (500, 'testing') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.15-compsrv.3 Locale: LANG=zh_CN.UTF-8, LC_CTYPE=zh_CN.UTF-8 (charmap=UTF-8) Versions of packages ldap-account-manager depends on: ii apache2-mpm-prefork [httpd] 2.0.55-4.1 traditional model for Apache2 ii debconf [debconf-2.0]1.5.4 Debian configuration management sy ii libapache2-mod-php4 4:4.4.2-1.1 server-side, HTML-embedded scripti ii php-fpdf 1.53.dfsg-4 PHP class to generate PDF files ii php4 4:4.4.2-1.1 server-side, HTML-embedded scripti ii php4-ldap4:4.4.2-1.1 LDAP module for php4 Versions of packages ldap-account-manager recommends: pn php4-mhash | php5-mhash none (no description available) -- debconf information: ldap-account-manager/passwd: lam ldap-account-manager/note-0_4_9-upgrade: ldap-account-manager/alias: lam ldap-account-manager/note-1_0_0-upgrade: * ldap-account-manager/config-webserver: apache, apache-ssl, apache-perl, apache2 * ldap-account-manager/restart-webserver: true -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Processed: Re: libnotify-dev: Missing depedancies on libgtk2.0-dev
Processing commands for [EMAIL PROTECTED]: tags 388521 + confirmed, pending Bug#388521: libnotify-dev: Missing depedancies on libgtk2.0-dev There were no tags set. Tags added: confirmed, pending thanks. Unknown command or malformed arguments to command. Thanks for the report. There is a fix in SVN and an upload is supposed Unknown command or malformed arguments to command. to happen soon. Unknown command or malformed arguments to command. Ciao Unknown command or malformed arguments to command. ~marco Unknown command or malformed arguments to command. Too many unknown commands, stopping 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#388719: findimagedupes: FTBFS: Missing Build-Depends
Package: findimagedupes Version: 0.2-1 Severity: serious From my pbuilder build log: ... mkdir -p ./tmp chmod 755 findimagedupes_tmp ./findimagedupes_tmp Can't locate Image/Magick.pm in @INC (@INC contains: /etc/perl /usr/local/lib/perl/5.8.8 /usr/local/share/perl/5.8.8 /usr/lib/perl5 /usr/share/perl5 /usr/lib/perl/5.8 /usr/share/perl/5.8 /usr/local/lib/site_perl .) at ./findimagedupes_tmp line 33. BEGIN failed--compilation aborted at ./findimagedupes_tmp line 33. make: *** [build/findimagedupes] Error 2 -- Daniel Schepler
Bug#386845: python-support fails to remove modules from /usr/lib/pythonX.Y/
severity 386845 important tag 386845 + unreproducible moreinfo thanks On Sun, Sep 10, 2006 at 03:50:18PM +0200, Martin Wuertele wrote: Package: python-support Version: 0.4.1 Severity: serious Justification: Policy 6.8 python-support installst private modules that should be installed into /usr/share/python-support to /usr/lib/pythonX.Y/ - in EVERY version of python and fails to remove them upon purge. pyversions is set to -2.3 and therefore it must not install modules to /usr/lib/python2.4/ dh_pysupport is not responsible for the /install/ of anything. the maintainer is. Then dh_pysupport handles those files, and moves them in /usr/share/python-support. There is no code path that could avoid that behaviour. I've used dh_pysupport in more than 80 python packages, and have never been able to watch what you describe. tagging the bug accordingly. -- ·O· Pierre Habouzit ··O[EMAIL PROTECTED] OOOhttp://www.madism.org signature.asc Description: Digital signature
Processed: Re: python-support fails to remove modules from /usr/lib/pythonX.Y/
Processing commands for [EMAIL PROTECTED]: severity 386845 important Bug#386845: python-support fails to remove modules from /usr/lib/pythonX.Y/ Severity set to `important' from `serious' tag 386845 + unreproducible moreinfo Bug#386845: python-support fails to remove modules from /usr/lib/pythonX.Y/ There were no tags set. Tags added: unreproducible, moreinfo 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#388717: libclass-dbi-perl: FTBFS: test failures
Package: libclass-dbi-perl Version: 3.0.14-1 Severity: serious From my pbuilder build log: ... /usr/bin/make test make[1]: Entering directory `/tmp/buildd/libclass-dbi-perl-3.0.14' PERL_DL_NONLAZY=1 /usr/bin/perl -MExtUtils::Command::MM -e test_harness(0, 'blib/lib', 'blib/arch') t/*.t t/01-columns.ok t/02-FilmDBD::SQLite::st fetchrow_array warning: not an error(0) at dbdimp.c line 504 [for Statement PRAGMA table_info(Movies)] at /usr/share/perl5/DBIx/ContextualFetch.pm line 88. prepare_cached(INSERT INTO Movies (title, director, rating, numexplodingsheep) VALUES (?, ?, ?, ?) ) statement handle DBIx::ContextualFetch::st=HASH(0x853bc14) still Active at /usr/share/perl5/Ima/DBI.pm line 381 ... t/15-accessor # Failed test 'DBD::SQLite::st fetchrow_array warning: not an error(0) at dbdimp.c line 504 [for Statement PRAGMA table_info(Movies)] at /usr/share/perl5/DBIx/ContextualFetch.pm line 88. # ' # in t/15-accessor.t at line 11. # 'DBD::SQLite::st fetchrow_array warning: not an error(0) at dbdimp.c line 504 [for Statement PRAGMA table_info(Movies)] at /usr/share/perl5/DBIx/ContextualFetch.pm line 88. # ' # doesn't match '(?-xism:clashes with built-in method)' ... t/99-miscok Failed Test Stat Wstat Total Fail Failed List of Failed --- t/15-accessor.t2 512554 7.27% 1 3 56-57 t/26-mutator.t 1 256 62 33.33% 1 7 5 tests skipped. Failed 2/27 test scripts, 92.59% okay. 0/549 subtests failed, 100.00% okay. make[1]: *** [test_dynamic] Error 255 make[1]: Leaving directory `/tmp/buildd/libclass-dbi-perl-3.0.14' make: *** [build-stamp] Error 2 -- Daniel Schepler
Bug#388695: geda-gschem: Probably parenthesis mismatch in errors in gschem
reassign 388695 geda-symbols thanks On Thu, Sep 21, 2006 at 11:50:42PM -0700, Steve Langasek wrote: On Fri, Sep 22, 2006 at 03:22:17PM +1000, Hamish Moffatt wrote: On Thu, Sep 21, 2006 at 11:12:42PM -0400, H. S. wrote: (here is the bug again here for geda-gschem, instead of for geda) Thanks. geda-gschem 20060906 should be in etch in a day or two. Not if this RC bug is open, it won't be. Good to know. system-gafrc is provided by geda-symbols, which is already updated in etch. However system-gschemrc is not yet. I suspect the skew between them is causing the problem. I will tighten the dependencies in the future. If you're certain that this is the cause, which package needs to be updated with added conflicts -- geda-symbols or geda-gschem? If it's geda-symbols, could you please reassign this bug there? If the change needs to be made to geda-gschem, please say so and I'll override this RC bug for the update into testing for now. Well, upgrading geda-gschem will certainly get it working. As to where the change belongs I'm not sure -- basically the two packages need to have matched versions. So either geda-gschem (and geda-gnetlist, gsymcheck, gattrib and possibly utils) conflict with a newer geda-symbols, or symbols conflicts with old geda-*. I think I prefer the latter solution, so I'll reassign. thanks, Hamish -- Hamish Moffatt VK3SB [EMAIL PROTECTED] [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#388708: Additional information
Hi, I think perhaps the information lies in handling UTF-8: == #_ sed -n 's/^\([^ ]*\):.*/\1/p' /var/lib/dpkg/stat-old | sort -u Architecture Bugs Conffiles Config-Version Conflicts Depends Description Enhances Essential Installed-Size Maintainer Maintainer� Peyrot [EMAIL PROTECTED] Maintainer�i Perrot [EMAIL PROTECTED] Origin Package Pre-Depends Priority Provides Python-Runtime Python-Version Recommends Replaces Section Source Status Suggests Url Version == The offending lines seem to be: Maintainer: Quôc Peyrot [EMAIL PROTECTED] Maintainer: Rémi Perrot [EMAIL PROTECTED] Unfortunately, editing these lines away has not really helped. I think this change needs to be fixed or reverted; or, at least, have a better error message which perhaps could include line numbers -- I can imagine less experienced user may be completely flummoxed by the apparent breakage. #_ apt-get install apt Reading package lists... Done Building dependency tree... Done The following packages will be upgraded: apt 1 upgraded, 0 newly installed, 0 to remove and 1 not upgraded. Need to get 0B/1414kB of archives. After unpacking 32.8kB of additional disk space will be used. Reading package fields... Done Reading package status... Done Retrieving bug reports... Done Reading changelogs... Done (Reading database ... 333423 files and directories currently installed.) Preparing to replace apt 0.6.45 (using .../archives/apt_0.6.46_i386.deb) ... Unpacking replacement apt ... Setting up apt (0.6.46) ... #_ apt-cahe search apt zsh: correct apt-cahe to apt-cache ? ([Y]es/[N]o/[E]dit/[A]bort) y E: Unable to parse package file /var/lib/dpkg/status (1) [1]2973 exit 100 apt-cache search apt #_ sed -n 's/^\([^ ]*\):.*/\1/p' /var/lib/dpkg/status | sort -u Architecture Bugs Conffiles Config-Version Conflicts Depends Description Enhances Essential Installed-Size Maintainer Origin Package Pre-Depends Priority Provides Python-Runtime Python-Version Recommends Replaces Section Source Status Suggests Url Version #_ manoj -- It's later than you think: the joint Russian-American space mission has already begun. --anonymous Manoj Srivastava [EMAIL PROTECTED]http://www.golden-gryphon.com/ 1024D/BF24424C print 4966 F272 D093 B493 410B 924B 21BA DABB BF24 424C
Bug#386673: patch
Hi, The patched 2.6.8 version has hit debian unstable yesterday. It did build fine on ppc, great. Though, a user reported that when launching electricsheep (on ppc), he got the following error: $ electricsheep X Error of failed request: BadMatch (invalid parameter attributes) Major opcode of failed request: 141 (XVideo) Minor opcode of failed request: 19 () Serial number of failed request: 91 Current serial number in output stream: 91 [1]5535 terminated electricsheep But when he launches electricsheep with `--mplayer 1' it did work. As I don't have a sid ppc box, I cannot test that issue, thus I welcome very much ideas and tests. Cheers, -- Alexis Sukrieh -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#388718: e2fsprogs: FTBFS: Link error in e2fsck.static
Package: e2fsprogs Version: 1.39-1 Severity: serious From my pbuilder build log: ... CC prof_err.c LD e2fsck.shared CP e2fsck LD e2fsck.static /usr/lib/libselinux.a(setrans_client.o): In function `fini_context_translations': /tmp/buildd/libselinux-1.30.28/src/setrans_client.c:210: undefined reference to `pthread_mutex_lock' /tmp/buildd/libselinux-1.30.28/src/setrans_client.c:211: undefined reference to `pthread_mutex_lock' /tmp/buildd/libselinux-1.30.28/src/setrans_client.c:216: undefined reference to `pthread_mutex_unlock' ... /tmp/buildd/libselinux-1.30.28/src/setrans_client.c:306: undefined reference to `pthread_mutex_lock' /tmp/buildd/libselinux-1.30.28/src/setrans_client.c:327: undefined reference to `pthread_mutex_unlock' collect2: ld returned 1 exit status make[3]: *** [e2fsck.static] Error 1 make[3]: Leaving directory `/tmp/buildd/e2fsprogs-1.39/debian/BUILD-STD/e2fsck' make[2]: *** [all-progs-recursive] Error 1 make[2]: Leaving directory `/tmp/buildd/e2fsprogs-1.39/debian/BUILD-STD' make[1]: *** [all] Error 2 make[1]: Leaving directory `/tmp/buildd/e2fsprogs-1.39/debian/BUILD-STD' make: *** [debian/stampdir/build-std-stamp] Error 2 Since this was fixed on the libselinux side (#388375), you need to either use pkg-config to get the proper dependencies, or else insert -lpthread manually. -- Daniel Schepler
Processed: Re: Bug#388695: geda-gschem: Probably parenthesis mismatch in errors in gschem
Processing commands for [EMAIL PROTECTED]: reassign 388695 geda-symbols Bug#388695: geda-gschem: Probably parenthesis mismatch in errors in gschem Bug reassigned from package `geda-gschem' to `geda-symbols'. thanks Stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Processed: (no subject)
Processing commands for [EMAIL PROTECTED]: severity 386882 grave Bug#386882: kphotoalbum: Depends on libexiv2 v. 0.10 Bug#386855: kphotoalbum should depend on libexiv2 (0.10) Severity set to `grave' from `normal' severity 386855 grave Bug#386855: kphotoalbum should depend on libexiv2 (0.10) Bug#386882: kphotoalbum: Depends on libexiv2 v. 0.10 Severity set to `grave' from `grave' thanks Stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Processed: This is more important I think
Processing commands for [EMAIL PROTECTED]: severity 388289 serious Bug#388289: zope-cmfplone: Please deploy anti-link-spam patch as a matter of urgency Severity set to `serious' from `important' 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#388646: cpad-kernel-source: purging the package fails (debconf unavailable)
Hi Bill, That's fixed in cvs right now, but cvs needs a little more work to get it happy with Life in Today's World. The kernel has moved about a bit since I last hacked on this. Are you actually using it, or just qa checking? Either way, I'll try to find time to kick it into shape for an upload over the weekend. Cheers! Ron On Thu, Sep 21, 2006 at 08:01:06PM +0200, Bill Allombert wrote: Package: cpad-kernel-source Version: 0.9-10 Severity: serious Hello Ron, There is an error when attempting to purge cpad-kernel-source: Removing cpad-kernel-source ... Purging configuration files for cpad-kernel-source ... /var/lib/dpkg/info/cpad-kernel-source.postrm: line 20: /usr/share/debconf/confmodule: No such file or directory dpkg: error processing cpad-kernel-source (--purge): subprocess post-removal script returned error exit status 1 The postrm cannot assume debconf will be available when purging. See Policy 7.2: Note, however, that the `postrm' cannot rely on any non-essential packages to be present during the `purge' phase. Cheers, -- Bill. [EMAIL PROTECTED] Imagine a large red swirl here. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#379413: remove libpthread from the archive?
Steve Langasek wrote: If the maintainer hasn't responded in a week or two, this bug could be reassigned to ftp.debian.org and turned into a removal request. Dropping pth as a whole would break a number of packages that depend on the traditional libpth interface. Just wait.. I'll upload this evening.. -- Address:Daniel Baumann, Burgunderstrasse 3, CH-4562 Biberist Email: [EMAIL PROTECTED] Internet: http://people.panthera-systems.net/~daniel-baumann/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Processed: reopening 388322
Processing commands for [EMAIL PROTECTED]: # Automatically generated email from bts, devscripts version 2.9.21 reopen 388322 Bug#388322: python-logilab-common: sarge to etch upgrade fails 'reopen' is deprecated when a bug has been closed with a version; use 'found' or 'submitter' as appropriate instead. Bug reopened, originator not changed. End of message, stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#358575: Bug #358575: mailman deletes all ucf-managed files on purge
On Wed, Sep 20, 2006 at 03:45:58PM +0200, Lionel Elie Mamane wrote: People running mailman on sarge on i386 are recommended to recompile the package or install the future security update 2.1.5-8sarge3. I meant the future security update 2.1.5-8sarge5. -- Lionel -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#388719: marked as done (findimagedupes: FTBFS: Missing Build-Depends)
Your message dated Fri, 22 Sep 2006 02:17:10 -0700 with message-id [EMAIL PROTECTED] and subject line Bug#388719: fixed in findimagedupes 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) ---BeginMessage--- Package: findimagedupes Version: 0.2-1 Severity: serious From my pbuilder build log: ... mkdir -p ./tmp chmod 755 findimagedupes_tmp ./findimagedupes_tmp Can't locate Image/Magick.pm in @INC (@INC contains: /etc/perl /usr/local/lib/perl/5.8.8 /usr/local/share/perl/5.8.8 /usr/lib/perl5 /usr/share/perl5 /usr/lib/perl/5.8 /usr/share/perl/5.8 /usr/local/lib/site_perl .) at ./findimagedupes_tmp line 33. BEGIN failed--compilation aborted at ./findimagedupes_tmp line 33. make: *** [build/findimagedupes] Error 2 -- Daniel Schepler ---End Message--- ---BeginMessage--- Source: findimagedupes Source-Version: 0.2-2 We believe that the bug you reported is fixed in the latest version of findimagedupes, which is due to be installed in the Debian FTP archive: findimagedupes_0.2-2.diff.gz to pool/main/f/findimagedupes/findimagedupes_0.2-2.diff.gz findimagedupes_0.2-2.dsc to pool/main/f/findimagedupes/findimagedupes_0.2-2.dsc findimagedupes_0.2-2_i386.deb to pool/main/f/findimagedupes/findimagedupes_0.2-2_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. Andreas Tille [EMAIL PROTECTED] (supplier of updated findimagedupes 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, 22 Sep 2006 10:51:05 +0200 Source: findimagedupes Binary: findimagedupes Architecture: source i386 Version: 0.2-2 Distribution: unstable Urgency: low Maintainer: Andreas Tille [EMAIL PROTECTED] Changed-By: Andreas Tille [EMAIL PROTECTED] Description: findimagedupes - Finds visually similar or duplicate images Closes: 388719 Changes: findimagedupes (0.2-2) unstable; urgency=low . * We need every single Depency also in Build-Depends because the program is called at build time. So perlmagick was added to Build-Depends Closes: #388719 Files: 6577150d7d2a530cc2401ea8cdcf5a29 674 graphics optional findimagedupes_0.2-2.dsc 370c09f9779039f4b3a8ee34ab9a4d60 8141 graphics optional findimagedupes_0.2-2.diff.gz 425df14a4760389cc1321db5615c35b3 27446 graphics optional findimagedupes_0.2-2_i386.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.5 (GNU/Linux) iD8DBQFFE6ZNYDBbMcCf01oRArDsAKCRGJHvkvxcZXjGDT87POwC84gUFACfYerN sSvgzkCBy8nAalfVdDglnlE= =GzdP -END PGP SIGNATURE- ---End Message---
Processed: confirmed
Processing commands for [EMAIL PROTECTED]: tags 388557 + confirmed Bug#388557: mono-gac: uninstallable on ia64, dependency on libc6 is incorrect There were no tags set. Tags added: confirmed 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#388557: confirmed
tags 388557 + confirmed thanks This is a bug caused by dh_clideps from the cli-common package, only Mono is currently effected because the new version of cli-common wasn't released yet. A fix is in the way... After a short discussion on #debian-devel Steve agreed that a dependency on libc6 | libc6.1 is an acceptable solution for this case. The call to the library is architecture independent, which is not done using ld but dlopen within Mono which also handles the marshalling of the data between managed and unmanaged code. -- Regards, Mirco 'meebey' Bauer PGP-Key: http://keyserver.noreply.org/pks/lookup?op=getsearch=0xEEF946C8 -BEGIN GEEK CODE BLOCK- Version: 3.12 GIT d s-:+ a-- C++ UL$ P L++$+++$ E- W+++$ N o? K- w++! O M- V? PS PE+ Y- PGP++ t 5+ X++ R tv+ b+ DI? D+ G++ e h! r-++ y? --END GEEK CODE BLOCK-- signature.asc Description: This is a digitally signed message part
Bug#388734: xfonts: after a dist-upgrade, the font system is broken, fonts display erraticly
Package: xfonts Severity: grave Justification: renders package unusable After a dist-upgrade, font rendering is borked in xorg. Sorry if it's not the good package, i have no idea what package this is related to. It breaks display of gnome application, kde application, firefox, thunderbird. IT seems java based applications are not affected, but unsure. The symptom are Kde: fonts are not displayed at all, every menu entry is blank. However the shadow of fonts, where appliable, are displayed gnome: fonts are partially displayed, they need various refreshing way to get them to display correctly firefox: need to highlight the text to get it displayed. (A way like another to refresh it) thunderbird: only the first 4 visible email entries are displayed, i have to scroll to go thru other mails. xterm seems to display correctly (i using it to send this bug report) I didn't touch the font, i just did a dist-upgrade and everything was broken -- System Information: Debian Release: testing/unstable APT prefers unstable APT policy: (500, 'unstable') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.17-2-686 Locale: LANG=fr_BE, LC_CTYPE=fr_BE (charmap=ISO-8859-1) (ignored: LC_ALL set to fr_BE) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#388743: rdoc1.8: NameError within ri_options.rb
Package: rdoc1.8 Version: 1.8.5-1 Severity: grave Justification: renders package unusable If requirering 'rdoc/usage', a NameError (uninitialized constant RI::Paths) is thrown due to missing require 'rdoc/ri/ri_paths' statement in ri_options. -- System Information: Debian Release: testing/unstable APT prefers unstable APT policy: (500, 'unstable') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.16 Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Versions of packages rdoc1.8 depends on: ii irb1.81.8.5-1Interactive Ruby (for Ruby 1.8) ii libruby1.81.8.5-1Libraries necessary to run Ruby 1. ii ruby1.8 1.8.5-1Interpreter of object-oriented scr rdoc1.8 recommends no packages. -- no debconf information -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Processed: Re: Bug#388734: xfonts: after a dist-upgrade, the font system is broken, fonts display erraticly
Processing commands for [EMAIL PROTECTED]: reassign 388734 xfonts-base Bug#388734: xfonts: after a dist-upgrade, the font system is broken, fonts display erraticly Warning: Unknown package 'xfonts' Bug reassigned from package `xfonts' to `xfonts-base'. -- 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#386882: marked as done (kphotoalbum: Depends on libexiv2 v. 0.10)
Your message dated Fri, 22 Sep 2006 03:32:10 -0700 with message-id [EMAIL PROTECTED] and subject line Bug#386855: fixed in kphotoalbum 2.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) ---BeginMessage--- Subject: kphotoalbum: Depends on libexiv2 v. 0.10 Package: kphotoalbum Version: 2.2-1 Severity: normal *** Please type your report below this line *** snoopy:~$ kphotoalbum kphotoalbum: error while loading shared libraries: libexiv2-0.10.so: cannot open shared object file: No such file or directory snoopy:~$ Thank you for packaging the new version of kimdaba/kphotoalbum. Friendly, Eugen Dedu -- System Information: Debian Release: testing/unstable APT prefers testing APT policy: (990, 'testing'), (500, 'unstable'), (1, 'experimental') Architecture: powerpc (ppc) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.17-2-powerpc Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968) Versions of packages kphotoalbum depends on: ii kdelibs4c2a 4:3.5.4-3 core libraries and binaries for al ii libart-2.0-2 2.3.17-1Library of functions for 2D graphi ii libc62.3.6.ds1-4 GNU C Library: Shared libraries ii libexiv2 0.9.1-1 EXIF/IPTC metadata manipulation li ii libgcc1 1:4.1.1-13 GCC support library ii libjpeg626b-13 The Independent JPEG Group's JPEG ii libkipi0 0.1.4-1 library for apps that want to use ii libqt3-mt3:3.3.6-4 Qt GUI Library (Threaded runtime v ii libstdc++6 4.1.1-13The GNU Standard C++ Library v3 Versions of packages kphotoalbum recommends: ii kipi-plugins 0.1+rc1-3 image manipulation/handling plugin -- no debconf information ---End Message--- ---BeginMessage--- Source: kphotoalbum Source-Version: 2.2-2 We believe that the bug you reported is fixed in the latest version of kphotoalbum, which is due to be installed in the Debian FTP archive: kphotoalbum_2.2-2.diff.gz to pool/main/k/kphotoalbum/kphotoalbum_2.2-2.diff.gz kphotoalbum_2.2-2.dsc to pool/main/k/kphotoalbum/kphotoalbum_2.2-2.dsc kphotoalbum_2.2-2_amd64.deb to pool/main/k/kphotoalbum/kphotoalbum_2.2-2_amd64.deb A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to [EMAIL PROTECTED], and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Fathi Boudra [EMAIL PROTECTED] (supplier of updated kphotoalbum package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing [EMAIL PROTECTED]) -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Mon, 11 Sep 2006 00:07:52 +0200 Source: kphotoalbum Binary: kphotoalbum Architecture: source amd64 Version: 2.2-2 Distribution: unstable Urgency: low Maintainer: Debian KDE Extras Team [EMAIL PROTECTED] Changed-By: Fathi Boudra [EMAIL PROTECTED] Description: kphotoalbum - tool for indexing, searching and viewing images by keywords for K Closes: 386855 Changes: kphotoalbum (2.2-2) unstable; urgency=low . * Add version to libexiv2 dependency (Closes: #386855) Files: 5c4cff81e13905b015340f6c88319c02 761 kde optional kphotoalbum_2.2-2.dsc 66beeb978cb828465e8e4795d873b655 76792 kde optional kphotoalbum_2.2-2.diff.gz 32fb9354d291e9f7d57afd0ba419c89b 11697114 kde optional kphotoalbum_2.2-2_amd64.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.5 (GNU/Linux) iD8DBQFFE7fJvGr7W6HudhwRAr0IAKCPAQzRYXRevow3kS+PUDqg4L2b4QCeMfNG MTE1be+TjDMlvByFs01MXbI= =aLSj -END PGP SIGNATURE- ---End Message---
Processed: Fixed in upload of gpsim-lcd 0.2.5-1 to experimental
Processing commands for [EMAIL PROTECTED]: tag 346736 + fixed-in-experimental Bug#346736: gpsim-lcd: FTBFS: build-depends on removed xlibs-dev Tags were: fixed patch Tags added: fixed-in-experimental tag 387779 + fixed-in-experimental Bug#387779: ITA: gpsim-lcd -- LCD module for gpsim There were no tags set. 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#385834: marked as done (package build-depends on g++-3.4, which is not available on hppa)
Your message dated Fri, 22 Sep 2006 03:47:09 -0700 with message-id [EMAIL PROTECTED] and subject line Bug#385834: fixed in kcheckgmail 0.5.5-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) ---BeginMessage--- Package: kcheckgmail Version: 0.5.5-1 Severity: serious the package build-depends on g++-3.4 or g++-4.0, which is not available on hppa. Please build using g++-4.1. If the package cannot be built using g++-4.1, please make sure that a bug report is filed against the g++-4.1 package. Is 3.4 really needed on arm and m68k? ---End Message--- ---BeginMessage--- Source: kcheckgmail Source-Version: 0.5.5-2 We believe that the bug you reported is fixed in the latest version of kcheckgmail, which is due to be installed in the Debian FTP archive: kcheckgmail_0.5.5-2.diff.gz to pool/main/k/kcheckgmail/kcheckgmail_0.5.5-2.diff.gz kcheckgmail_0.5.5-2.dsc to pool/main/k/kcheckgmail/kcheckgmail_0.5.5-2.dsc kcheckgmail_0.5.5-2_i386.deb to pool/main/k/kcheckgmail/kcheckgmail_0.5.5-2_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. Jose Luis Tallon [EMAIL PROTECTED] (supplier of updated kcheckgmail package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing [EMAIL PROTECTED]) -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Thu, 21 Sep 2006 0:18:14 +0200 Source: kcheckgmail Binary: kcheckgmail Architecture: source i386 Version: 0.5.5-2 Distribution: unstable Urgency: low Maintainer: Jose Luis Tallon [EMAIL PROTECTED] Changed-By: Jose Luis Tallon [EMAIL PROTECTED] Description: kcheckgmail - KDE systray application to check GMail accounts Closes: 345177 385834 Changes: kcheckgmail (0.5.5-2) unstable; urgency=low . * Acknowledge NMU (Closes: #385834) . * Added upstream SV localization (Closes: #345177) . * Updated to Standards-Version 3.7.2 with no changes. Files: 51d83c6aa3d0385fb368ccf7e60ef512 645 kde optional kcheckgmail_0.5.5-2.dsc 6b50cdca028558173b2fb700f2e24ec8 613861 kde optional kcheckgmail_0.5.5.orig.tar.gz bcb900b90f466120f4cb7cd3d4591251 108526 kde optional kcheckgmail_0.5.5-2.diff.gz 8c0462d3083ed9249f3e73d8d8372dcf 103302 kde optional kcheckgmail_0.5.5-2_i386.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.5 (GNU/Linux) iD8DBQFFE7s1NFDtUT/MKpARAmC9AKCW3LvBQahZBmfTTarn7ns5n6YsKQCeLH90 Aa/s+L4DQa1FsT8xIC11NNA= =NuLp -END PGP SIGNATURE- ---End Message---
Bug#386855: marked as done (kphotoalbum should depend on libexiv2 (0.10))
Your message dated Fri, 22 Sep 2006 03:32:10 -0700 with message-id [EMAIL PROTECTED] and subject line Bug#386855: fixed in kphotoalbum 2.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) ---BeginMessage--- Package: kphotoalbum Version: 2.2-1 Severity: normal kphotoalbum is currently *only* dependent on libexiv2 because of which it fails to load if you have an older version of libexiv2. Currently, testing has 0.9 [EMAIL PROTECTED]:/mnt/build/linux-kernel $ kphotoalbum kphotoalbum: error while loading shared libraries: libexiv2-0.10.so: cannot open shared object file: No such file or directory Hence, kphotoalbum should depend on libexiv2 = 0.10 Thanks, Ritesh -- System Information: Debian Release: testing/unstable APT prefers testing APT policy: (990, 'testing'), (550, 'unstable'), (500, 'stable'), (250, 'experimental'), (50, 'edgy') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.17-my-patches Locale: LANG=en_US, LC_CTYPE=en_US (charmap=ISO-8859-1) Versions of packages kphotoalbum depends on: ii kdelibs4c2a 4:3.5.4-3 core libraries and binaries for al ii libc62.3.6.ds1-4 GNU C Library: Shared libraries ii libexiv2 0.10-1 EXIF/IPTC metadata manipulation li ii libgcc1 1:4.1.1-13 GCC support library ii libjpeg626b-13 The Independent JPEG Group's JPEG ii libkipi0 0.1.4-1 library for apps that want to use ii libqt3-mt3:3.3.6-4 Qt GUI Library (Threaded runtime v ii libstdc++6 4.1.1-13The GNU Standard C++ Library v3 Versions of packages kphotoalbum recommends: ii kipi-plugins 0.1+rc1-3 image manipulation/handling plugin -- no debconf information ---End Message--- ---BeginMessage--- Source: kphotoalbum Source-Version: 2.2-2 We believe that the bug you reported is fixed in the latest version of kphotoalbum, which is due to be installed in the Debian FTP archive: kphotoalbum_2.2-2.diff.gz to pool/main/k/kphotoalbum/kphotoalbum_2.2-2.diff.gz kphotoalbum_2.2-2.dsc to pool/main/k/kphotoalbum/kphotoalbum_2.2-2.dsc kphotoalbum_2.2-2_amd64.deb to pool/main/k/kphotoalbum/kphotoalbum_2.2-2_amd64.deb A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to [EMAIL PROTECTED], and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Fathi Boudra [EMAIL PROTECTED] (supplier of updated kphotoalbum package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing [EMAIL PROTECTED]) -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Mon, 11 Sep 2006 00:07:52 +0200 Source: kphotoalbum Binary: kphotoalbum Architecture: source amd64 Version: 2.2-2 Distribution: unstable Urgency: low Maintainer: Debian KDE Extras Team [EMAIL PROTECTED] Changed-By: Fathi Boudra [EMAIL PROTECTED] Description: kphotoalbum - tool for indexing, searching and viewing images by keywords for K Closes: 386855 Changes: kphotoalbum (2.2-2) unstable; urgency=low . * Add version to libexiv2 dependency (Closes: #386855) Files: 5c4cff81e13905b015340f6c88319c02 761 kde optional kphotoalbum_2.2-2.dsc 66beeb978cb828465e8e4795d873b655 76792 kde optional kphotoalbum_2.2-2.diff.gz 32fb9354d291e9f7d57afd0ba419c89b 11697114 kde optional kphotoalbum_2.2-2_amd64.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.5 (GNU/Linux) iD8DBQFFE7fJvGr7W6HudhwRAr0IAKCPAQzRYXRevow3kS+PUDqg4L2b4QCeMfNG MTE1be+TjDMlvByFs01MXbI= =aLSj -END PGP SIGNATURE- ---End Message---
Bug#388756: zaptel-source: wct4xxp and other modules are not built anymore on zaptel-1.2.8.dfsg-1
Package: zaptel-source Version: 1:1.2.8.dfsg-1 Severity: grave Justification: renders package unusable I just rebuilt modules for the latest kernel (2.6.17-2) and some modules are missing, wct4xxp.ko is one of those. -- System Information: Debian Release: testing/unstable APT prefers testing APT policy: (500, 'testing'), (50, 'unstable') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.17-2-486 Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Versions of packages zaptel-source depends on: ii bzip2 1.0.3-6high-quality block-sorting file co ii debhelper 5.0.37.3 helper programs for debian/rules ii module-assistant 0.10.6 tool to make module package creati Versions of packages zaptel-source recommends: ii zaptel1:1.2.8.dfsg-1 zapata telephony utilities -- no debconf information -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Processed: Re: flexbackup: CVE-2005-4802: default config insecure temporary file creation
Processing commands for [EMAIL PROTECTED]: found 334350 1.2.1-2 Bug#334350: flexbackup: CVE-2005-4802: default config insecure temporary file creation Bug marked as found in version 1.2.1-2. close 334350 1.2.1-3 Bug#334350: flexbackup: CVE-2005-4802: default config insecure temporary file creation 'close' is deprecated; see http://www.debian.org/Bugs/Developer#closing. Bug marked as fixed in version 1.2.1-3, send any further explanations to Anibal Monsalve Salazar [EMAIL PROTECTED] thanks Stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#387185: picprog: Fails to detect programmer in amd64
On Sun, Sep 17, 2006 at 01:25:01AM +0200, Jan Wagemakers wrote: Normally picprog use the RDTSC instruction on x86_64/i386 platforms. By disabling this, picprog makes use of the delay-routines for platforms that don't have this RDTSC instruction. This should be done regardless of platform; RDTSC is a _very_ _poor_ choice for reliable timing and should not be used except in very controlled environments. The most important reason is that you might have CPU frequency scaling going on; suddenly your CPU frequency can move from 150 MHz to 1.4 GHz, and in that case, timing on the number of cycles is not a very good idea... /* Steinar */ -- Homepage: http://www.sesse.net/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#388756: zaptel-source: wct4xxp and other modules are not built anymore on zaptel-1.2.8.dfsg-1
On Fri, Sep 22, 2006 at 01:29:28PM +0200, Alessandro Polverini wrote: Package: zaptel-source Version: 1:1.2.8.dfsg-1 Severity: grave Justification: renders package unusable I just rebuilt modules for the latest kernel (2.6.17-2) and some modules are missing, wct4xxp.ko is one of those. iIt is installed into a subdirectory and only the 2.6 build was adapted for that. http://bugs.digium.com/view.php?id=7964 (patch should be there, haven't looked). Sadly, I will probably not have much computer time this weekend to start packaging the beta... -- Tzafrir Cohen sip:[EMAIL PROTECTED] icq#16849755 iax:[EMAIL PROTECTED] +972-50-7952406 jabber:[EMAIL PROTECTED] [EMAIL PROTECTED] http://www.xorcom.com -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#388649: marked as done (Probably parenthesis mismatch in errors in geda)
Your message dated Fri, 22 Sep 2006 21:48:06 +1000
with message-id [EMAIL PROTECTED]
and subject line Bug#388649: Probably parenthesis mismatch in errors in geda
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what I am
talking about this indicates a serious mail system misconfiguration
somewhere. Please contact me immediately.)
Debian bug tracking system administrator
(administrator, Debian Bugs database)
---BeginMessage---
Package: geda
Version: 20060123-1
Severity: grave
Justification: renders package unusable
*** Please type your report below this line ***
Hello,
If I try to start gschem, I get these errors:
--
$ gschem
gEDA/gschem version 20060123
gEDA/gschem comes with ABSOLUTELY NO WARRANTY; see COPYING for more details.
This is free software, and you are welcome to redistribute it under certain
conditions; please see the COPYING file for more details.
Probably parenthesis mismatch in /etc/gEDA/system-gafrc
Most recently read form: (postscript-prolog ${GEDADATA}/prolog.ps)
Probably parenthesis mismatch in /etc/gEDA/system-gschemrc
Most recently read form: ([EMAIL PROTECTED] ([EMAIL PROTECTED] [EMAIL PROTECTED] /system-gafrc))
Probably parenthesis mismatch in /usr/share/gEDA/scheme/gschem.scm
Most recently read form: ([EMAIL PROTECTED] global-keymap (quote ()))
Tried to get an invalid color: 0
Tried to get an invalid color: 7
Tried to get an invalid color: 0
Tried to get an invalid color: 7
--
and if I start gschem with a .sch file, I get the above erros and the the schematic is not shown. In both cases, a
window opens but it has no menus on it. So I cannot open pre-existing
files at all. If I open a new file, in the add component dialogbox, I
cannot see the preview of the components selected.
-- System Information:
Debian Release: testing/unstable
APT prefers testing
APT policy: (500, 'testing')
Architecture: i386 (i686)
Shell: /bin/sh linked to /bin/bash
Kernel: Linux 2.6.16-2-686
Locale: LANG=en_CA.UTF-8, LC_CTYPE=en_CA.UTF-8 (charmap=UTF-8)
Versions of packages geda depends on:
ii
geda-doc
20060906-1 Documentation for GNU EDA -- Elect
ii
geda-gnetlist
20060123-1 GNU EDA -- Electronics design soft
ii
geda-gschem
20060123-1 GNU EDA -- Electronics design soft
ii
libatk1.0-0
1.12.2-1 The ATK accessibility toolkit
ii
libc6
2.3.6.ds1-4 GNU C Library: Shared libraries
ii
libcairo2
1.2.4-1 The Cairo 2D vector graphics libra
ii
libfontconfig1
2.3.2-7 generic font configuration library
ii
libglib2.0-0
2.12.3-2 The GLib library of C routines
ii
libgtk2.0-0
2.8.20-1 The GTK+ graphical user interface
ii
libpango1.0-0
1.12.3-1+b1 Layout and rendering of internatio
ii
libx11-6
2:1.0.0-8 X11 client-side library
ii
libxcursor1
1.1.7-4 X cursor management library
ii
libxext6
1:1.0.1-2 X11 miscellaneous extension librar
ii
libxi6
1:1.0.1-3 X11 Input extension library
ii
libxinerama1
1:1.0.1-4.1 X11 Xinerama extension library
ii
libxrandr2
2:1.1.0.2-4 X11 RandR extension library
ii
libxrender1
1:0.9.1-3 X Rendering Extension client libra
geda recommends no packages.
-- no debconf information
---End Message---
---BeginMessage---
On Thu, Sep 21, 2006 at 11:13:39PM -0400, H. S. wrote:
This bug is with gschem so please report it against gschem.
Done.
Thanks, I'm closing this report with this email.
Hamish
--
Hamish Moffatt VK3SB [EMAIL PROTECTED] [EMAIL PROTECTED]
---End Message---
Bug#367267: ftp.debian.org: still not there
Package: ftp.debian.org Followup-For: Bug #367267 Hello, The packages are still not in the right places, couldn't something like a move by hand be done? In order to have my local mirror synced I have to ignore errors (debmirror) which I don't really like. I wonder if this would affect the availability of the package in etch (as released, on cd images). -- System Information: Debian Release: testing/unstable APT prefers testing APT policy: (900, 'testing'), (800, 'unstable') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.16-2-686 Locale: LANG=ro_RO.UTF-8, LC_CTYPE=ro_RO.UTF-8 (charmap=UTF-8) -- This message was scanned for viruses by BitDefender for Linux Mail Servers. For more information please visit http://www.bitdefender.com/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Processed: Fixed in upload of evolution 2.8.0-1 to experimental
Processing commands for [EMAIL PROTECTED]: tag 341172 + fixed-in-experimental Bug#341172: Please port to the experimental pilot-link 0.12 API Tags were: patch Tags added: fixed-in-experimental tag 384280 + fixed-in-experimental Bug#384280: evolution: implicit pointer conversion Tags were: patch 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#388784: krb5-kdc: purging the package fails (debconf unavailable)
Package: krb5-kdc Version: 1.4.4-1 Severity: serious Hello Sam, There is an error when attempting to purge krb5-kdc: Removing krb5-kdc ... Purging configuration files for krb5-kdc ... /var/lib/dpkg/info/krb5-kdc.postrm: line 3: /usr/share/debconf/confmodule: No such file or directory dpkg: error processing krb5-kdc (--purge): subprocess post-removal script returned error exit status 1 The postrm script cannot rely on debconf to be available when purging. See Policy 7.2: Note, however, that the `postrm' cannot rely on any non-essential packages to be present during the `purge' phase. Cheers, -- Bill. [EMAIL PROTECTED] Imagine a large red swirl here. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#388781: phpsysinfo: purging the package fails (debconf unavailable)
Package: phpsysinfo Version: 2.5.1-3 Severity: serious Hello Frederik, There is an error when attempting to purge phpsysinfo: Removing phpsysinfo ... Purging configuration files for phpsysinfo ... /var/lib/dpkg/info/phpsysinfo.postrm: line 12: /usr/share/debconf/confmodule: No such file or directory dpkg: error processing phpsysinfo (--purge): subprocess post-removal script returned error exit status 1 The postrm script cannot rely on debconf to be available when purging. See Policy 7.2: Note, however, that the `postrm' cannot rely on any non-essential packages to be present during the `purge' phase. Cheers, -- Bill. [EMAIL PROTECTED] Imagine a large red swirl here. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#388779: postgrey: purging the package fails (ucf unavailable)
Package: postgrey Version: 1.27-1 Severity: serious Hello Adrian, There is an error when attempting to purge postgrey: Removing postgrey ... Purging configuration files for postgrey ... /var/lib/dpkg/info/postgrey.postrm: line 26: ucf: command not found dpkg: error processing postgrey (--purge): subprocess post-removal script returned error exit status 127 The postrm script cannot assume ucf is available when purging. See Policy 7.2: Note, however, that the `postrm' cannot rely on any non-essential packages to be present during the `purge' phase. Cheers, -- Bill. [EMAIL PROTECTED] Imagine a large red swirl here. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#388782: fonty: purging the package fails (debconf unavailable)
Package: fonty Version: 1.0-22 Severity: serious Hello Piotr, There is an error when attempting to purge fonty: Removing fonty ... Purging configuration files for fonty ... /var/lib/dpkg/info/fonty.postrm: line 10: /usr/share/debconf/confmodule: No such file or directory dpkg: error processing fonty (--purge): subprocess post-removal script returned error exit status 1 The postrm script cannot rely on debconf to be available when purging. See Policy 7.2: Note, however, that the `postrm' cannot rely on any non-essential packages to be present during the `purge' phase. Cheers, -- Bill. [EMAIL PROTECTED] Imagine a large red swirl here. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#388691: ibm-3270: Licensing issues
tags 388691 moreinfo thanks On Thu, Sep 21, 2006 at 09:36:24PM -0300, Wagner Bruna wrote: The copyright file for ibm-3270 says: Copyrights on x3270 are a work in progress and any assistance in clarifying them would be appreciated. but there's no active bug about some issues. So it is outdated. I thought I removed that. Particularly, public use needs clarification: Copyright 1989 by Georgia Tech Research Corporation, Atlanta, GA 30332. All Rights Reserved. GTRC hereby grants public use of this software. Neither I nor the ftp-team see a problem with that. There are many relevant discussions associated with another source package: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=321178 Refers to the snippet above. http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=287083 Refers to the long removed 5250 code. And according to 3270's maintainer (Richard A Nelson), those licensing issues are still unsolved: There is no sign in the 3270 code, that Richard A Nelsen is maintainer in any way. Bastian -- In the strict scientific sense we all feed on death -- even vegetarians. -- Spock, Wolf in the Fold, stardate 3615.4
Processed: Re: Bug#375830: Acknowledgement (occasionally misdetects PCI-Express card for PCI and dies before DRI)
Processing commands for [EMAIL PROTECTED]: found 375830 8.28.8-1 Bug#375830: occasionally misdetects PCI-Express card for PCI and dies before DRI Bug marked as found in version 8.28.8-1. severity 375830 serious Bug#375830: occasionally misdetects PCI-Express card for PCI and dies before DRI Severity set to `serious' from `important' thanks Stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#388783: shfs-utils: purging the package fails (debconf unavailable)
Package: shfs-utils Version: 0.35-6 Severity: serious Hello Eduard, There is an error when attempting to purge shfs-utils: Removing shfs-utils ... Purging configuration files for shfs-utils ... /var/lib/dpkg/info/shfs-utils.postrm: line 2: /usr/share/debconf/confmodule: No such file or directory dpkg: error processing shfs-utils (--purge): subprocess post-removal script returned error exit status 1 The postrm script cannot rely on debconf to be available when purging. See Policy 7.2: Note, however, that the `postrm' cannot rely on any non-essential packages to be present during the `purge' phase. Cheers, -- Bill. [EMAIL PROTECTED] Imagine a large red swirl here. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Processed: Re: Bug#388691: ibm-3270: Licensing issues
Processing commands for [EMAIL PROTECTED]: tags 388691 moreinfo Bug#388691: ibm-3270: Licensing issues There were no tags set. Tags added: moreinfo 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#388780: netenv: purging the package fails (debconf unavailable)
Package: netenv Version: 0.94.3-17 Severity: serious Hello Frank, There is an error when attempting to purge netenv: Removing netenv ... Purging configuration files for netenv ... /var/lib/dpkg/info/netenv.postrm: line 20: /usr/share/debconf/confmodule: No such file or directory dpkg: error processing netenv (--purge): subprocess post-removal script returned error exit status 1 The postrm script cannot rely on debconf to be available when purging. Cheers, -- Bill. [EMAIL PROTECTED] Imagine a large red swirl here. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Processed: Re: Bug#387790: fillets-ng-data: broken symlinks
Processing commands for [EMAIL PROTECTED]: severity 387790 serious Bug#387790: fillets-ng-data: broken symlinks Severity set to `serious' from `minor' tags 387790 +pending Bug#387790: fillets-ng-data: broken symlinks There were no tags set. Tags added: pending thanks lars Unknown command or malformed arguments to command. Hi! Unknown command or malformed arguments to command. * Lars Wirzenius [EMAIL PROTECTED] [060916 20:01]: Unknown command or malformed arguments to command. Severity: minor Unknown command or malformed arguments to command. Hmmm... shouldn't broken symlinks due to missing dependencies be release Unknown command or malformed arguments to command. Too many unknown commands, stopping 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#388646: cpad-kernel-source: purging the package fails (debconf unavailable)
On Fri, Sep 22, 2006 at 06:29:33PM +0930, Ron wrote: Hi Bill, That's fixed in cvs right now, but cvs needs a little more work to get it happy with Life in Today's World. The kernel has moved about a bit since I last hacked on this. Are you actually using it, or just qa checking? Either way, I'll try to find time to kick it into shape for an upload over the weekend. Hello Ron, This was just QA checking. This is a by-product of checking upgrade paths from sarge to etch. Cheers, -- Bill. [EMAIL PROTECTED] Imagine a large red swirl here. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#388489: marked as done (libc6-i386: Missing /etc.ld.so.conf.d/i486-linux-gnu.conf)
Your message dated Fri, 22 Sep 2006 16:56:06 +0200
with message-id [EMAIL PROTECTED]
and subject line Processed: Cloning this bug
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what I am
talking about this indicates a serious mail system misconfiguration
somewhere. Please contact me immediately.)
Debian bug tracking system administrator
(administrator, Debian Bugs database)
---BeginMessage---
Subject: ia32-libs: ldconfig files installed in wrong directory?
Package: ia32-libs
Version: 1.15
Severity: grave
Justification: renders package unusable
*** Please type your report below this line ***
The ldconfig configuration files are installed in /lib/ldconfig.
Shouldn't they be installed in /etc/ld.so.conf.d? They're not being
picked up by ldconfig.
Thanks!
-- System Information:
Debian Release: testing/unstable
APT prefers testing
APT policy: (500, 'testing')
Architecture: amd64 (x86_64)
Shell: /bin/sh linked to /bin/bash
Kernel: Linux 2.6.16-2-amd64-k8-smp
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Versions of packages ia32-libs depends on:
ii dpkg 1.13.21 package maintenance system
for Deb
ii lib32asound2 1.0.11-7ALSA library (32 bit)
ii lib32gcc11:4.1.1-13 GCC support library (32 bit
Versio
ii lib32ncurses55.5-3 Shared libraries for
terminal hand
ii lib32stdc++6 4.1.1-13The GNU Standard C++
Library v3 (3
ii lib32z1 1:1.2.3-13 compression library - 32
bit runti
ii libc6-i386 2.3.6.ds1-4 GNU C Library: 32bit shared
librar
ii lsb-release 3.1-15 Linux Standard Base version
report
ia32-libs recommends no packages.
-- no debconf information
---End Message---
---BeginMessage---
Goswin von Brederlow wrote:
reopen 388489
thanks
Aurelien Jarno [EMAIL PROTECTED] writes:
Goswin von Brederlow wrote:
Aurelien Jarno [EMAIL PROTECTED] writes:
Debian Bug Tracking System a écrit :
retitle -1 libc6-i386: Missing /etc.ld.so.conf.d/i486-linux-gnu.conf
There is no need for such a file. ld.so natively looks on all
directories of bi (or tri)-arches directories. If you need to be
convinced just run: strings /sbin/ldconfig | grep ^/lib
Clising the bug
Binutils doesn't. And in some cases binutils looks at ld.so.conf and
It does. Well it was not the case on amd64, but it has been fixed two
months ago in version 2.17-2 (see bug#369052).
I am closing the bug, please only reopen the bug if you have a
testcase to show what you claim.
Then what is /etc/ld.so.conf.d/x86_64-linux-gnu.conf for? If 32bit
multiarch support doesn't need the conffile then 64bit multiarch would
need it even less, being the native bit-ness and all. Think about that
for a second.
Meanwhile here is your testcase step by step:
Create missing link so we can link (pending fix in ia32-libs):
% ln -s /usr/lib32/libfreetype.so.6 /usr/lib32/libfreetype.so
Test /usr/lib32 setup:
% cat foo.c
extern int FT_Init_FreeType(void);
int main(void) { return FT_Init_FreeType(); }
% gcc -m32 -o foo foo.c -lfreetype
So this works. Multiarch not being a requirement for Etch, I fail to see
why the severity of this bug is serious.
Test multiarch:
% mkdir /usr/lib/i486-linux-gnu
% mv /usr/lib32/libz.* /usr/lib/i486-linux-gnu
Wrong. The purpose of multiarch is to remove bi-arch packages. With
multiarch if you want to install a 32-bit glibc on amd64, install the
package from i386. Not libc6-i386.
--
.''`. Aurelien Jarno | GPG: 1024D/F1BCDB73
: :' : Debian developer | Electrical Engineer
`. `' [EMAIL PROTECTED] | [EMAIL PROTECTED]
`-people.debian.org/~aurel32 | www.aurel32.net
---End Message---
Bug#387610: subversion: FTBFS on ia64
Troy Heber [EMAIL PROTECTED] writes: It's not an optimization bug, compiling O0 does not help. We know that lt-fs-base-test 2, creates and closes a new db, it then creates a new fs object and tries to re-open the db. The call to apr_hash_get returns NULL, so it's not finding the object in the hash. Returning NULL is wrong. The call continues on and tries to open the db using libdb4.4 via __env_open_pp, which eventually leads to __envreg_add and the error message. I haven't built a debug version of libdb yet, I'm going to do that this morning and walk through. From, what I'm guessing I don't think the apr_hash_get lookup should have failed, so the problem might be that direction, I need to build libapr debug as well. Correct, Subversion's DB_ENV cache is failing. On i386 I get: (gdb) b env.c:622 (gdb) shell rm -rf test-repo-open-berkeley (gdb) r 2 Breakpoint 2 622 bdb = bdb_cache_get(key, panic); (gdb) p sizeof(key) $8 = 12 (gdb) x/12b key 0xb7f0: 0x040x090x000x000x000x000x000x00 0xb7f8: 0xe70x650x2a0x00 (gdb) c Breakpoint 2 622 bdb = bdb_cache_get(key, panic); (gdb) x/12b key 0xb7f0: 0x040x090x000x000x000x000x000x00 0xb7f8: 0xe70x650x2a0x00 (gdb) x/12b bdb_cache[0].array[3][0].key 0xb7f0: 0x040x090x000x000x000x000x000x00 0xb7f8: 0xe70x650x2a0x00 (gdb) n 623 if (panic) (gdb) p bdb $7 = (bdb_env_t *) 0x8072618 The first time the breakpoint is reached it's from the svn_test__create_fs line, the second time it's from the svn_fs_open_berkeley line. The key has the same value in each case, and the second time that value is present in the cache, so the hash lookup doesn't return NULL. In the case above the key is located in slot [3] in the hash; that will vary depending on what bytes comprise the key, but you should be able to find it because there are only 15 slots and all but one should be zero, e.g. (gdb) p bdb_cache[0].array[1] $9 = (apr_hash_entry_t *) 0x0 (gdb) p bdb_cache[0].array[3] $10 = (apr_hash_entry_t *) 0x8072d30 -- Philip Martin -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Processed: tags 387185 upstream
Processing commands for [EMAIL PROTECTED]: tags 387185 upstream Bug#387185: picprog: Fails to detect programmer in amd64 There were no tags set. Tags added: upstream thanks bts Unknown command or malformed arguments to command. 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#387249: marked as done ([NONFREE-DOC] Package contains IETF RFC/I-D)
Your message dated Fri, 22 Sep 2006 08:32:14 -0700 with message-id [EMAIL PROTECTED] and subject line Bug#387249: fixed in camstream 0.26.3+dfsg-1 has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what I am talking about this indicates a serious mail system misconfiguration somewhere. Please contact me immediately.) Debian bug tracking system administrator (administrator, Debian Bugs database) ---BeginMessage--- Package: camstream-doc Version: 0.26.3-9 Hi! It seems your package contains non-free IETF RFC/I-D's: usr/share/doc/camstream-doc/tech/rfc959.txt.gz doc/camstream-doc The license on IETF RFC/I-D's is not DFSG-free, see: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=199810 http://release.debian.org/removing-non-free-documentation I believe the options are: 1) Remove the file from the package (which may include re-packaging the source code). 2) Move the files to a non-free package (which may also include re-packaging the source code). If you disagree with this, because this bug is reported for several packages at once, it seems better to discuss this on debian-legal, in this thread: http://thread.gmane.org/gmane.linux.debian.devel.legal/25993 The severity is serious, because this violates the Debian policy http://www.debian.org/doc/debian-policy/ch-archive.html#s-dfsg. I'm sorry if this report is filed in error, I went over many packages looking for suspicious filenames, and there may be false positives. Thanks, Simon ---End Message--- ---BeginMessage--- Source: camstream Source-Version: 0.26.3+dfsg-1 We believe that the bug you reported is fixed in the latest version of camstream, which is due to be installed in the Debian FTP archive: camstream-doc_0.26.3+dfsg-1_all.deb to pool/main/c/camstream/camstream-doc_0.26.3+dfsg-1_all.deb camstream_0.26.3+dfsg-1.diff.gz to pool/main/c/camstream/camstream_0.26.3+dfsg-1.diff.gz camstream_0.26.3+dfsg-1.dsc to pool/main/c/camstream/camstream_0.26.3+dfsg-1.dsc camstream_0.26.3+dfsg-1_amd64.deb to pool/main/c/camstream/camstream_0.26.3+dfsg-1_amd64.deb camstream_0.26.3+dfsg.orig.tar.gz to pool/main/c/camstream/camstream_0.26.3+dfsg.orig.tar.gz A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to [EMAIL PROTECTED], and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Aurelien Jarno [EMAIL PROTECTED] (supplier of updated camstream 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, 22 Sep 2006 17:20:26 +0200 Source: camstream Binary: camstream camstream-doc Architecture: source amd64 all Version: 0.26.3+dfsg-1 Distribution: unstable Urgency: medium Maintainer: Aurelien Jarno [EMAIL PROTECTED] Changed-By: Aurelien Jarno [EMAIL PROTECTED] Description: camstream - Collection of tools for webcams and other video-devices camstream-doc - Documentation for camstream Closes: 387249 Changes: camstream (0.26.3+dfsg-1) unstable; urgency=medium . * Repackage the source archive to remove rfc959.txt (closes: bug#387249). Files: e117c1c552b4eddc6258111ecbf77357 701 misc optional camstream_0.26.3+dfsg-1.dsc 8b14662d1a5583fbc0d85f063e471717 1547574 misc optional camstream_0.26.3+dfsg.orig.tar.gz 5cc2251ca41ba61386fc496eab89f729 111498 misc optional camstream_0.26.3+dfsg-1.diff.gz b66b01fa443a5246e285d4cc620750e6 1362576 doc optional camstream-doc_0.26.3+dfsg-1_all.deb 674ede477529bbf1005f1c276b295b84 14 misc optional camstream_0.26.3+dfsg-1_amd64.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.5 (GNU/Linux) iD8DBQFFFACGw3ao2vG823MRAnfXAJ9QdIn0+EIyV5Ej7qtO5ctX1uxpYgCfX/uS dMOz4X1Vd+XZgWp4M+0L0hQ= =hvRE -END PGP SIGNATURE- ---End Message---
Bug#387185: picprog: Fails to detect programmer in amd64
Jaakko, I have recently received this bug-report about picprog (Debian). http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=387185 Let me summerize what we have found so far. - When asking around various people have confirmed that picprog fails on the 64-bit amd64 platform. - Altering the delay-routines so that picprog thinks the CPU is ten times faster seems to solve the problem. - Disabling the use of the RDTSC-instruction also seems to solve the problem, but not for everybody. - On my old laptop, picprog works at 600Mhz, but not at 750Mhz. By disabling the use of RDTSC, picprog works without a problem at 750Mhz on my laptop. (Note, my laptop is not an amd64 ;-) ) To me it seems that disabling the use of RDTSC is a good idea. Any comments? Also, maybe we can try to add an extra delay-option to picprog so that when picprog fails to run on some hardware, people can use this option to make picprog run more slowy. -- Met vriendelijke groetjes - Jan Wagemakers - ... Fidonet : 2:292/100.19 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#387663: marked as done (pygopherd: sid package broken (incompatible with python 2.4))
Your message dated Fri, 22 Sep 2006 08:02:43 -0700 with message-id [EMAIL PROTECTED] and subject line Bug#387663: fixed in pygopherd 2.0.17 has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what I am talking about this indicates a serious mail system misconfiguration somewhere. Please contact me immediately.) Debian bug tracking system administrator (administrator, Debian Bugs database) ---BeginMessage--- Package: pygopherd Version: 2.0.16 Severity: grave Justification: renders package unusable The default version of python in sid is 2.4, but the modules of pygopherd are installed only in /usr/share/pycentral/ (dh_pycentral). python 2.4 use modules from /usr/lib/python2.4/site-packages/ We can specify python2.3 in /etc/init.d/pygopherd to force using the old version of python, or modify the rules script and make it future-safe The following patch enables the package to work with python 2.4, but will broke python 2.3 compatibility. Sorry I don't understand the python packaging system enough to provide a 2.3/2.4 compatible one, like in 'python-imaging' diff -rpuN pygopherd-2.0.16.orig/debian/control pygopherd-2.0.16/debian/control --- pygopherd-2.0.16.orig/debian/control2006-09-11 16:10:13.0 +0200 +++ pygopherd-2.0.16/debian/control 2006-09-15 20:17:08.0 +0200 @@ -2,10 +2,10 @@ Source: pygopherd Section: net Priority: optional Maintainer: John Goerzen [EMAIL PROTECTED] -Build-Depends-Indep: python-central (= 0.5), debhelper ( 5.0.37.2), python, python (= 2.3) +Build-Depends-Indep: python-central (= 0.5), debhelper ( 5.0.37.2), python (= 2.4) Build-Depends: debhelper (= 5.0.37.2), python-central (= 0.5) Standards-Version: 3.5.2 -XS-Python-Version: current, = 2.3 +XS-Python-Version: current, = 2.4 Package: pygopherd Architecture: all diff -rpuN pygopherd-2.0.16.orig/debian/rules pygopherd-2.0.16/debian/rules --- pygopherd-2.0.16.orig/debian/rules 2006-09-11 16:10:13.0 +0200 +++ pygopherd-2.0.16/debian/rules 2006-09-15 20:16:44.0 +0200 @@ -89,7 +89,6 @@ binary-indep: build install dh_installinfo # dh_undocumented dh_installchangelogs - dh_pycentral dh_python dh_link dh_strip -- System Information: Debian Release: testing/unstable APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.16.16 Locale: LANG=en_US, LC_CTYPE=en_US (charmap=ISO-8859-1) Versions of packages pygopherd depends on: ii logrotate 3.7.1-3Log rotation utility ii mime-support 3.37-1 MIME files 'mime.types' 'mailcap ii python2.4.3-11 An interactive high-level object-o ii python-simpletal 4.1-6 Simple TAL, TALES and METAL implem pygopherd recommends no packages. -- no debconf information ---End Message--- ---BeginMessage--- Source: pygopherd Source-Version: 2.0.17 We believe that the bug you reported is fixed in the latest version of pygopherd, which is due to be installed in the Debian FTP archive: pygfarm_2.0.17_all.deb to pool/main/p/pygopherd/pygfarm_2.0.17_all.deb pygopherd_2.0.17.dsc to pool/main/p/pygopherd/pygopherd_2.0.17.dsc pygopherd_2.0.17.tar.gz to pool/main/p/pygopherd/pygopherd_2.0.17.tar.gz pygopherd_2.0.17_all.deb to pool/main/p/pygopherd/pygopherd_2.0.17_all.deb A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to [EMAIL PROTECTED], and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. John Goerzen [EMAIL PROTECTED] (supplier of updated pygopherd 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, 15 Sep 2006 14:01:50 -0500 Source: pygopherd Binary: pygfarm pygopherd Architecture: source all Version: 2.0.17 Distribution: unstable Urgency: high Maintainer: John Goerzen [EMAIL PROTECTED] Changed-By: John Goerzen [EMAIL PROTECTED] Description: pygfarm- Collection of add-on modules for Pygopherd pygopherd - Modular Multiprotocol Gopher/HTTP/WAP Server in Python Closes: 387663 Changes: pygopherd (2.0.17) unstable; urgency=high . * Make sure python-central does its thing before the init script tries to start Python. Closes: #387663. Files: 9b2bb5b6e4b5c4cec6b3781c8ea4d157 667 net optional pygopherd_2.0.17.dsc
Bug#388222: marked as done (config/postrm depends on non-essential packages (dbconfig-common, probably ucf))
Your message dated Fri, 22 Sep 2006 08:32:11 -0700 with message-id [EMAIL PROTECTED] and subject line Bug#388222: fixed in bacula 1.38.11-6 has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what I am talking about this indicates a serious mail system misconfiguration somewhere. Please contact me immediately.) Debian bug tracking system administrator (administrator, Debian Bugs database) ---BeginMessage--- Package: bacula-director-mysql Severity: serious Justification: 7.2 -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 hi there, it was recently brought to my attention that the recommended method for using dbconfig-common in a package's config and postrm scripts was not policy compliant as hinted in the subject of this bugreport. the problem is that in both the config and the postrm you should test whether the files/programs in question exist before sourcing/executing them. more information is in a link below. NOTE that this is slightly different from the original posts about mass-bug filing in which only the postrm was mentioned, but the config file is too. so, even if you've fixed your package after i initially posted about this, you might want to take a second look to make sure. this mass bug-filing was announced 2006/08/19, though it seems there's a problem with the list archives for debian-devel. fortunately, i cc'd the dbconfig list: http://lists.alioth.debian.org/pipermail/dbconfig-common-devel/2006-August/000586.html and information for how you can fix your package: http://people.debian.org/~seanius/policy/dbconfig-common.html/ch-develguide.html#s-hooks fortunately, the fix is pretty simple, though i apologize for the inconvenience. feel free to ask if you have any questions. sean - -- System Information: Debian Release: testing/unstable APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.16-2-amd64-k8 Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.5 (GNU/Linux) iD8DBQFFD7viynjLPm522B0RAljVAJ9RMZEvf5vSAbQngHa5PZfy/3AjQgCfaGp2 o/JjS6R3f6p+8Yat3c7xsmA= =+aEa -END PGP SIGNATURE- ---End Message--- ---BeginMessage--- Source: bacula Source-Version: 1.38.11-6 We believe that the bug you reported is fixed in the latest version of bacula, which is due to be installed in the Debian FTP archive: bacula-client_1.38.11-6_all.deb to pool/main/b/bacula/bacula-client_1.38.11-6_all.deb bacula-common_1.38.11-6_all.deb to pool/main/b/bacula/bacula-common_1.38.11-6_all.deb bacula-console-gnome_1.38.11-6_i386.deb to pool/main/b/bacula/bacula-console-gnome_1.38.11-6_i386.deb bacula-console-wx_1.38.11-6_i386.deb to pool/main/b/bacula/bacula-console-wx_1.38.11-6_i386.deb bacula-console_1.38.11-6_i386.deb to pool/main/b/bacula/bacula-console_1.38.11-6_i386.deb bacula-director-common_1.38.11-6_i386.deb to pool/main/b/bacula/bacula-director-common_1.38.11-6_i386.deb bacula-director-mysql_1.38.11-6_i386.deb to pool/main/b/bacula/bacula-director-mysql_1.38.11-6_i386.deb bacula-director-pgsql_1.38.11-6_i386.deb to pool/main/b/bacula/bacula-director-pgsql_1.38.11-6_i386.deb bacula-director-sqlite3_1.38.11-6_i386.deb to pool/main/b/bacula/bacula-director-sqlite3_1.38.11-6_i386.deb bacula-director-sqlite_1.38.11-6_i386.deb to pool/main/b/bacula/bacula-director-sqlite_1.38.11-6_i386.deb bacula-fd_1.38.11-6_i386.deb to pool/main/b/bacula/bacula-fd_1.38.11-6_i386.deb bacula-sd-mysql_1.38.11-6_i386.deb to pool/main/b/bacula/bacula-sd-mysql_1.38.11-6_i386.deb bacula-sd-pgsql_1.38.11-6_i386.deb to pool/main/b/bacula/bacula-sd-pgsql_1.38.11-6_i386.deb bacula-sd-sqlite3_1.38.11-6_i386.deb to pool/main/b/bacula/bacula-sd-sqlite3_1.38.11-6_i386.deb bacula-sd-sqlite_1.38.11-6_i386.deb to pool/main/b/bacula/bacula-sd-sqlite_1.38.11-6_i386.deb bacula-sd_1.38.11-6_i386.deb to pool/main/b/bacula/bacula-sd_1.38.11-6_i386.deb bacula-server_1.38.11-6_all.deb to pool/main/b/bacula/bacula-server_1.38.11-6_all.deb bacula-traymonitor_1.38.11-6_i386.deb to pool/main/b/bacula/bacula-traymonitor_1.38.11-6_i386.deb bacula_1.38.11-6.diff.gz to pool/main/b/bacula/bacula_1.38.11-6.diff.gz bacula_1.38.11-6.dsc to pool/main/b/bacula/bacula_1.38.11-6.dsc bacula_1.38.11-6_all.deb to pool/main/b/bacula/bacula_1.38.11-6_all.deb A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to [EMAIL PROTECTED], and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. John Goerzen [EMAIL PROTECTED] (supplier
Bug#388220: marked as done (config/postrm depends on non-essential packages (dbconfig-common, probably ucf))
Your message dated Fri, 22 Sep 2006 08:32:11 -0700 with message-id [EMAIL PROTECTED] and subject line Bug#388220: fixed in bacula 1.38.11-6 has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what I am talking about this indicates a serious mail system misconfiguration somewhere. Please contact me immediately.) Debian bug tracking system administrator (administrator, Debian Bugs database) ---BeginMessage--- Package: bacula-director-pgsql Severity: serious Justification: 7.2 -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 hi there, it was recently brought to my attention that the recommended method for using dbconfig-common in a package's config and postrm scripts was not policy compliant as hinted in the subject of this bugreport. the problem is that in both the config and the postrm you should test whether the files/programs in question exist before sourcing/executing them. more information is in a link below. NOTE that this is slightly different from the original posts about mass-bug filing in which only the postrm was mentioned, but the config file is too. so, even if you've fixed your package after i initially posted about this, you might want to take a second look to make sure. this mass bug-filing was announced 2006/08/19, though it seems there's a problem with the list archives for debian-devel. fortunately, i cc'd the dbconfig list: http://lists.alioth.debian.org/pipermail/dbconfig-common-devel/2006-August/000586.html and information for how you can fix your package: http://people.debian.org/~seanius/policy/dbconfig-common.html/ch-develguide.html#s-hooks fortunately, the fix is pretty simple, though i apologize for the inconvenience. feel free to ask if you have any questions. sean - -- System Information: Debian Release: testing/unstable APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.16-2-amd64-k8 Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.5 (GNU/Linux) iD8DBQFFD7vlynjLPm522B0RAqF6AJ9hpxJQyGp0OFy1DNKngz/PDQjJFQCfaJUd U0gMBu2funEjUzNUk/nK3tM= =wl3a -END PGP SIGNATURE- ---End Message--- ---BeginMessage--- Source: bacula Source-Version: 1.38.11-6 We believe that the bug you reported is fixed in the latest version of bacula, which is due to be installed in the Debian FTP archive: bacula-client_1.38.11-6_all.deb to pool/main/b/bacula/bacula-client_1.38.11-6_all.deb bacula-common_1.38.11-6_all.deb to pool/main/b/bacula/bacula-common_1.38.11-6_all.deb bacula-console-gnome_1.38.11-6_i386.deb to pool/main/b/bacula/bacula-console-gnome_1.38.11-6_i386.deb bacula-console-wx_1.38.11-6_i386.deb to pool/main/b/bacula/bacula-console-wx_1.38.11-6_i386.deb bacula-console_1.38.11-6_i386.deb to pool/main/b/bacula/bacula-console_1.38.11-6_i386.deb bacula-director-common_1.38.11-6_i386.deb to pool/main/b/bacula/bacula-director-common_1.38.11-6_i386.deb bacula-director-mysql_1.38.11-6_i386.deb to pool/main/b/bacula/bacula-director-mysql_1.38.11-6_i386.deb bacula-director-pgsql_1.38.11-6_i386.deb to pool/main/b/bacula/bacula-director-pgsql_1.38.11-6_i386.deb bacula-director-sqlite3_1.38.11-6_i386.deb to pool/main/b/bacula/bacula-director-sqlite3_1.38.11-6_i386.deb bacula-director-sqlite_1.38.11-6_i386.deb to pool/main/b/bacula/bacula-director-sqlite_1.38.11-6_i386.deb bacula-fd_1.38.11-6_i386.deb to pool/main/b/bacula/bacula-fd_1.38.11-6_i386.deb bacula-sd-mysql_1.38.11-6_i386.deb to pool/main/b/bacula/bacula-sd-mysql_1.38.11-6_i386.deb bacula-sd-pgsql_1.38.11-6_i386.deb to pool/main/b/bacula/bacula-sd-pgsql_1.38.11-6_i386.deb bacula-sd-sqlite3_1.38.11-6_i386.deb to pool/main/b/bacula/bacula-sd-sqlite3_1.38.11-6_i386.deb bacula-sd-sqlite_1.38.11-6_i386.deb to pool/main/b/bacula/bacula-sd-sqlite_1.38.11-6_i386.deb bacula-sd_1.38.11-6_i386.deb to pool/main/b/bacula/bacula-sd_1.38.11-6_i386.deb bacula-server_1.38.11-6_all.deb to pool/main/b/bacula/bacula-server_1.38.11-6_all.deb bacula-traymonitor_1.38.11-6_i386.deb to pool/main/b/bacula/bacula-traymonitor_1.38.11-6_i386.deb bacula_1.38.11-6.diff.gz to pool/main/b/bacula/bacula_1.38.11-6.diff.gz bacula_1.38.11-6.dsc to pool/main/b/bacula/bacula_1.38.11-6.dsc bacula_1.38.11-6_all.deb to pool/main/b/bacula/bacula_1.38.11-6_all.deb A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to [EMAIL PROTECTED], and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. John Goerzen [EMAIL PROTECTED] (supplier
Bug#387790: fillets-ng-data: broken symlinks
pe, 2006-09-22 kello 16:34 +0200, Alexander Schmehl kirjoitti: * Lars Wirzenius [EMAIL PROTECTED] [060916 20:01]: Severity: minor Hmmm... shouldn't broken symlinks due to missing dependencies be release critical? Most likely they will render the package unusable, won't they? Possibly they should be RC. However, I think that a package like fillets-ng-data, which is useless without another package anyway, and that other package (hopefully) provides the link targets, might as well just get a non-RC bug. Of course, partly the problem is that I have little time and there are so many packages... Anyway, severity isn't relevant if the bug gets fixed. :) -- (def (reverse items) (accumulate (fn (so-far x) (cons x so-far)) nil items)) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#388571: [Pkg-awstats-devel] Bug#388571: awstats: Non-free Firefox icon included
Can anyone comment on whether or not it is problematic for us to distribute a tiny icon of Firefox's logo? The only thing I could find is: http://www.mozilla.org/products/firefox/buttons.html which says Mozilla Firefox and the Firefox logo are trademarks of The Mozilla Foundation. Usage guidelines for the new logos is currently under development. Charles -Original Message- Package: awstats Version: 6.5-2 Severity: serious Justification: Policy 2.2.1 /usr/share/awstats/icon/browser/firefox.png is Mozilla Firefox's official logo, which is not modifiable. I don't know if just including that icon can be a trademark violation. -- The boy who gets His girl's applause Must act Not look Like Santa Claus Burma-Shave http://burma-shave.org/jingles/1948/the_boy_who signature.asc Description: Digital signature
Bug#388571: [Pkg-awstats-devel] Bug#388571: awstats: Non-free Firefox icon included
Charles Fry schrieb: Can anyone comment on whether or not it is problematic for us to distribute a tiny icon of Firefox's logo? The only thing I could find is: http://www.mozilla.org/products/firefox/buttons.html which says Mozilla Firefox and the Firefox logo are trademarks of The Mozilla Foundation. Usage guidelines for the new logos is currently under development. Trademarks reserve the right to use signs: If you don't have a license to use that trademark, you may not use it with your products. According to what you have quoted, there is no general license for the public to use the Firefox logo. From a practical point of view: I don't think this is intended by the Mozilla people. Probably they will grant you a license, if you ask. Michael Below -- Michael Below Rechtsanwalt www.judiz.de -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#388809: htmldoc-common fails to upgrade smoothly
Package: htmldoc-common Version: 1.8.27-1 Severity: serious Preparing to replace htmldoc-common 1.8.26-1 (using .../htmldoc-common_1.8.27-1_all.deb) ... Unpacking replacement htmldoc-common ... dpkg: error processing /var/cache/apt/archives/htmldoc-common_1.8.27-1_all.deb (--unpack): trying to overwrite `/usr/share/man/man1/htmldoc.1.gz', which is also in package htmldoc -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#388811: xlibmesa-dri: upgrade to xorg 7.1 causes savage opengl stop working
Package: xlibmesa-dri Version: 1:7.1.0-1 Severity: critical Justification: breaks unrelated software An upgrade from xorg 7.0 to xorg 7.1 causes 3d stop working with savage dri driver (with a mobile Prosavage KN133 twister). glxinfo report direct rendering=yes but glxgears and any other opengl app are just displaying black screen, without crashing the whole system. I think this bug is the same as described in https://bugs.freedesktop.org/show_bug.cgi?id=6357 Thibault -- System Information: Debian Release: testing/unstable APT prefers unstable APT policy: (500, 'unstable') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.18 Locale: [EMAIL PROTECTED], [EMAIL PROTECTED] (charmap=ISO-8859-15) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#104394: Message for melissa groeber
How are you, Royal has receiieved your filled app. Mitch shall then Re-confirm yo ur data . http://AE0F4B.ssr.be For melissa groeber and your past Track Record is not an iss ue. All H 0me E quitytypes have been aprroveed for you melissa groeber Best Regards, Ines -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Processed: severity of 388776 is serious
Processing commands for [EMAIL PROTECTED]: # Automatically generated email from bts, devscripts version 2.9.21 severity 388776 serious Bug#388776: xserver-xorg-input-wacom: Source package fails to compile Severity set to `serious' from `normal' End of message, stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#388489: Processed: Cloning this bug
reopen 388489
thanks
Aurelien Jarno [EMAIL PROTECTED] writes:
Goswin von Brederlow wrote:
Aurelien Jarno [EMAIL PROTECTED] writes:
Debian Bug Tracking System a écrit :
retitle -1 libc6-i386: Missing /etc.ld.so.conf.d/i486-linux-gnu.conf
There is no need for such a file. ld.so natively looks on all
directories of bi (or tri)-arches directories. If you need to be
convinced just run: strings /sbin/ldconfig | grep ^/lib
Clising the bug
Binutils doesn't. And in some cases binutils looks at ld.so.conf and
It does. Well it was not the case on amd64, but it has been fixed two
months ago in version 2.17-2 (see bug#369052).
I am closing the bug, please only reopen the bug if you have a
testcase to show what you claim.
Then what is /etc/ld.so.conf.d/x86_64-linux-gnu.conf for? If 32bit
multiarch support doesn't need the conffile then 64bit multiarch would
need it even less, being the native bit-ness and all. Think about that
for a second.
Meanwhile here is your testcase step by step:
Create missing link so we can link (pending fix in ia32-libs):
% ln -s /usr/lib32/libfreetype.so.6 /usr/lib32/libfreetype.so
Test /usr/lib32 setup:
% cat foo.c
extern int FT_Init_FreeType(void);
int main(void) { return FT_Init_FreeType(); }
% gcc -m32 -o foo foo.c -lfreetype
Test multiarch:
% mkdir /usr/lib/i486-linux-gnu
% mv /usr/lib32/libz.* /usr/lib/i486-linux-gnu
% gcc -m32 -o foo foo.c -lfreetype
/usr/bin/ld: warning: libz.so.1, needed by
/usr/lib/gcc/x86_64-linux-gnu/4.1.2/../../../../lib32/libfreetype.so, not found
(try using -rpath or -rpath-link)
/usr/lib/gcc/x86_64-linux-gnu/4.1.2/../../../../lib32/libfreetype.so: undefined
reference to `inflate'
/usr/lib/gcc/x86_64-linux-gnu/4.1.2/../../../../lib32/libfreetype.so: undefined
reference to `inflateReset'
/usr/lib/gcc/x86_64-linux-gnu/4.1.2/../../../../lib32/libfreetype.so: undefined
reference to `inflateEnd'
/usr/lib/gcc/x86_64-linux-gnu/4.1.2/../../../../lib32/libfreetype.so: undefined
reference to `inflateInit2_'
collect2: ld returned 1 exit status
Fix it:
% echo /usr/lib/i486-linux-gnu /etc/ld.so.conf.d/i486-linux-gnu.conf
% gcc -m32 -o foo foo.c -lfreetype
thus ld.so.conf.d/*.
Or what is the point of the ld.so.conf.d files at all?
The purpose of the ld.so.conf.d files is to provide an easy way to add
search directories for some packages (eg atlas), which is a lot easier
than modifying the ld.so.conf directly.
It is also a way for future multiarch support to add a search path,
hence the /etc.ld.so.conf.d/(host-triplet).conf in libc6. But it has
nothing to do with bi-arch or tri-arch which are directly handled in
the toolchain.
Which is exactly what I am asking for. That
/etc.ld.so.conf.d/(host-triplet).conf is missing in libc6-i386.
Notice that I do ask for that multiarch host triplet file
specificaly. Not for any bi/tri-arch support. I believed requesting
that file would be clear enough indication that the multiarch dirs are
ment but you seem to have misunderstood that completly.
The libc6 on amd64 ships /etc/ld.so.conf.d/x86_64-linux-gnu.conf
% cat /etc/ld.so.conf.d/x86_64-linux-gnu.conf
# Multiarch support
/lib/x86_64-linux-gnu
/usr/lib/x86_64-linux-gnu
The libc6-i386 should ship /etc/ld.so.conf.d/i486-linux-gnu.conf
% cat /etc/ld.so.conf.d/i486-linux-gnu.conf
# Multiarch support
/lib/i486-linux-gnu
/usr/lib/i486-linux-gnu
That is all I'm asking.
MfG
Goswin
Processed: Re: Processed: Cloning this bug
Processing commands for [EMAIL PROTECTED]: reopen 388489 Bug#388489: libc6-i386: Missing /etc.ld.so.conf.d/i486-linux-gnu.conf Bug reopened, originator not changed. 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#388115: Re 388115: tetex-base postinst fails
I ran into this too. I ran update-fmtutil (as root) and re-reran the dist-upgrade. The problem remains. I'm not sure if this is the requested test, but it was my best interpretation of it. I can provide the details that others have, if that might be helpful. I think I can leave things in this broken state for a little while, if someone wants more info or experiments. Otherwise, I'll try one of the fixes/workarounds listed earlier in the bug logs. -- Ross Boylan wk: (415) 514-8146 185 Berry St #5700 [EMAIL PROTECTED] Dept of Epidemiology and Biostatistics fax: (415) 514-8150 University of California, San Francisco San Francisco, CA 94107-1739 hm: (415) 550-1062 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Processed: reassign 388811 to mesa, severity of 388811 is important
Processing commands for [EMAIL PROTECTED]: # Automatically generated email from bts, devscripts version 2.9.21 reassign 388811 mesa Bug#388811: xlibmesa-dri: upgrade to xorg 7.1 causes savage opengl stop working Bug reassigned from package `xlibmesa-dri' to `mesa'. severity 388811 important Bug#388811: xlibmesa-dri: upgrade to xorg 7.1 causes savage opengl stop working Severity set to `important' from `critical' 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: Debian Kerberosish: r2493 - krb5/trunk/krb5/debian
Processing commands for [EMAIL PROTECTED]: tags 388784 pending Bug#388784: krb5-kdc: purging the package fails (debconf unavailable) There were no tags set. Tags added: pending thanks Stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#388691: ibm-3270: Licensing issues
--- Bastian Blank [EMAIL PROTECTED] escreveu: Particularly, public use needs clarification: Copyright 1989 by Georgia Tech Research Corporation, Atlanta, GA 30332. All Rights Reserved. GTRC hereby grants public use of this software. Neither I nor the ftp-team see a problem with that. AAUI, if the copyright notice only grants public use of the software, it's not conforming with DFSG guidelines (The license must not restrict anyone from making use of the program in a specific field of endeavor.). As it is phrased, the license does not explicitely grant unrestricted use, so the package at least should not be in main. Could you please explain why this isn't the case anymore? And IMHO this clarification should be in the copyright file itself, since the package was removed before for licensing issues. http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=287083 Refers to the long removed 5250 code. It also includes discussion about the public use issue. And according to 3270's maintainer (Richard A Nelson), those licensing issues are still unsolved: There is no sign in the 3270 code, that Richard A Nelsen is maintainer in any way. Well, there is another source package of this code (since oldstable, at least), maintained by him: http://packages.qa.debian.org/3/3270.html And its copyright file states: This is why x3270 is in non-free, not main: * All the licenses are normal, and used by standard Debian packages, except for the original Georgia Tech Research Corporation on the software (...) Clarification is needed on what GTRC consider to be 'public use.' http://packages.debian.org/changelogs/pool/non-free/3/3270/3270_3.2.17-2/copyright Thanks, Wagner ___ Novidade no Yahoo! Mail: receba alertas de novas mensagens no seu celular. Registre seu aparelho agora! http://br.mobile.yahoo.com/mailalertas/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#388431: improved patch
Hello!
Here is an improved variant of patch. It allows system administrator
to configure RLIMIT_RTPRIO RLIMIT_NICE via rt_priority and nice
entries in /etc/security/limits.conf
Best regards,
Alexei.
--
All science is either physics or stamp collecting.
Index: pam-0.79/Linux-PAM/modules/pam_limits/pam_limits.c
===
--- pam-0.79.orig/Linux-PAM/modules/pam_limits/pam_limits.c 2006-09-22
22:16:10.0 +0400
+++ pam-0.79/Linux-PAM/modules/pam_limits/pam_limits.c 2006-09-22
22:17:46.0 +0400
@@ -257,8 +257,38 @@
pl-supported[i] = 1;
pl-limits[i].src_soft = LIMITS_DEF_NONE;
pl-limits[i].src_hard = LIMITS_DEF_NONE;
- pl-limits[i].limit.rlim_cur = RLIM_INFINITY;
- pl-limits[i].limit.rlim_max = RLIM_INFINITY;
+ switch (i) {
+ case RLIMIT_CPU:
+ case RLIMIT_FSIZE:
+ case RLIMIT_DATA:
+ case RLIMIT_STACK:
+ case RLIMIT_CORE:
+ case RLIMIT_RSS:
+ case RLIMIT_NPROC:
+ case RLIMIT_NOFILE:
+ case RLIMIT_MEMLOCK:
+#ifdef RLIMIT_AS
+ case RLIMIT_AS:
+#endif
+#ifdef RLIMIT_LOCKS
+ case RLIMIT_LOCKS:
+#endif
+#ifdef RLIMIT_SIGPENDING
+ case RLIMIT_SIGPENDING:
+#endif
+#ifdef RLIMIT_MSGQUEUE
+ case RLIMIT_MSGQUEUE:
+#endif
+ pl-limits[i].limit.rlim_cur = RLIM_INFINITY;
+ pl-limits[i].limit.rlim_max = RLIM_INFINITY;
+ break;
+ default:
+ /* Dont touch unknown/unsupported rlimit values ---
+ * RLIM_INFINITY might be a bad choice for them and
+ * even open up security holes (for example, the latter
+ * is true for RLIM_RTPRIO in newer Linux kernels). */
+ break;
+ }
}
}
@@ -327,6 +357,14 @@
else if (strcmp(lim_item, msgqueue) == 0)
limit_item = RLIMIT_MSGQUEUE;
#endif
+#ifdef RLIMIT_RTPRIO
+ else if (strcmp(lim_item, rt_priority) == 0)
+ limit_item = RLIMIT_RTPRIO;
+#endif
+#ifdef RLIMIT_NICE
+ else if (strcmp(lim_item, nice) == 0)
+ limit_item = RLIMIT_NICE;
+#endif
else if (strcmp(lim_item, maxlogins) == 0) {
limit_item = LIMIT_LOGIN;
pl-flag_numsyslogins = 0;
@@ -399,6 +437,22 @@
#endif
limit_value *= 1024;
break;
+#ifdef RLIMIT_RTPRIO
+ case RLIMIT_RTPRIO:
+ if (limit_value 99)
+ limit_value = 99;
+ if (limit_value 0)
+ limit_value = 0;
+ break;
+#endif
+#ifdef RLIMIT_NICE
+ case RLIMIT_NICE:
+ if (limit_value 39)
+ limit_value = 39;
+ if (limit_value 0)
+ limit_value = 0;
+ break;
+#endif
}
if ( (limit_item != LIMIT_LOGIN)
Index: pam-0.79/Linux-PAM/modules/pam_limits/README
===
--- pam-0.79.orig/Linux-PAM/modules/pam_limits/README 2005-01-10
13:09:51.0 +0300
+++ pam-0.79/Linux-PAM/modules/pam_limits/README2006-09-22
22:17:46.0 +0400
@@ -42,7 +42,11 @@
- sigpending - max number of pending signals (Linux 2.6 and higher)
- msgqueue - max memory used by POSIX message queues (bytes)
(Linux 2.6 and higher)
-
+ - rt_priority - ceiling on real-time priority which can be set by
+ this user (Linux 2.6.13 and higher)
+ - nice - ceiling to which the processes’ nice value can be raised
+ (Linux 2.6.13 and higher)
+
Note, if you specify a type of '-' but neglect to supply the item and
value fields then the module will never enforce any limits on the
specified user/group etc. .
Index: pam-0.79/Linux-PAM/modules/pam_limits/limits.skel
===
--- pam-0.79.orig/Linux-PAM/modules/pam_limits/limits.skel 2005-01-10
13:09:51.0 +0300
+++ pam-0.79/Linux-PAM/modules/pam_limits/limits.skel 2006-09-22
22:17:46.0 +0400
@@ -32,6 +32,8 @@
#- locks - max number of file locks the user can hold
#- sigpending - max number of pending signals
#- msgqueue - max memory used by POSIX message queues (bytes)
+#- rt_priority - ceiling on real-time priority which can be set
+#- nice - ceiling to which the processes’ nice value can be raised
#
#domain type item value
#
Index: pam-0.79/debian/rules
Bug#388691: ibm-3270: Licensing issues
On Fri, Sep 22, 2006 at 02:47:55PM -0300, Wagner Bruna wrote: --- Bastian Blank [EMAIL PROTECTED] escreveu: Particularly, public use needs clarification: Copyright 1989 by Georgia Tech Research Corporation, Atlanta, GA 30332. All Rights Reserved. GTRC hereby grants public use of this software. Neither I nor the ftp-team see a problem with that. AAUI, if the copyright notice only grants public use of the software, it's not conforming with DFSG guidelines (The license must not restrict anyone from making use of the program in a specific field of endeavor.). As it is phrased, the license does not explicitely grant unrestricted use, so the package at least should not be in main. You have to explain why public use is restricted. Well, there is another source package of this code (since oldstable, at least), maintained by him: http://packages.qa.debian.org/3/3270.html And its copyright file states: Well, this is neither a statement from the ftp-team, nor from me, nor from upstream. Bastian -- The heart is not a logical organ. -- Dr. Janet Wallace, The Deadly Years, stardate 3479.4 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Processed: retitle 385296 to broken with ssl on amd64
Processing commands for [EMAIL PROTECTED]: # Automatically generated email from bts, devscripts version 2.9.21 retitle 385296 broken with ssl on amd64 Bug#385296: tries to shutdown invalid file descriptor on amd64 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#388838: sysv-rc-bootsplash: modifies files belonging to other packages
Package: sysv-rc-bootsplash Version: 1.0.2-1 Severity: serious sysv-rc-bootsplash's postinst uses patch to modify /etc/init.d/rc and /usr/share/initramfs-tools/scripts/functions. This means that the changes are lost if sysv-rc or initramfs-tools is upgraded, that the maintainer scripts fail if you run them twice, and I guess there are other issues. Cheers, Julien Cristau -- System Information: Debian Release: testing/unstable APT prefers testing APT policy: (990, 'testing'), (500, 'unstable'), (1, 'experimental') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.17-2-686 Locale: LANG=C, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) signature.asc Description: Digital signature
Processed: Re: cbmlink: FTBFS: bashisms
Processing commands for [EMAIL PROTECTED]: retitle 379724 wrong build depends: eval: 1: xa: not found Bug#379724: cbmlink: FTBFS: bashisms Changed Bug title. severity 379724 serious Bug#379724: wrong build depends: eval: 1: xa: not found Severity set to `serious' from `important' thanks Stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Processed: subversion Debian ci: r687 - trunk/debian
Processing commands for [EMAIL PROTECTED]: tags 387996 pending Bug#387996: subversion: [m68k] fix for the failing ruby tests Tags were: patch 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#388840: fglrx-driver: Conflict with Xorg-server 7.1.0 package
Package: fglrx-driver Version: 8.28.8-1 Severity: grave Justification: renders package unusable When I updated Today my Debian unstable, it updated the Xorg-sevrver too. But It also remove fglrx-driver. So now I must use the xorg radeon driver instead of the ati One -- System Information: Debian Release: testing/unstable APT prefers unstable APT policy: (500, 'unstable') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.17-2-686 Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8) Versions of packages fglrx-driver depends on: ii libc62.3.6.ds1-4 GNU C Library: Shared libraries ii libgcc1 1:4.1.1-13 GCC support library ii libstdc++5 1:3.3.6-13 The GNU Standard C++ Library v3 ii libx11-6 2:1.0.0-9 X11 client-side library ii libxext6 1:1.0.1-2 X11 miscellaneous extension librar ii libxrandr2 2:1.1.0.2-4 X11 RandR extension library ii libxrender1 1:0.9.1-3 X Rendering Extension client libra ii xserver-xorg 1:7.1.0-1 the X.Org X server Versions of packages fglrx-driver recommends: pn fglrx-kernel none (no description available) ___ Avez-vous essayé le nouveau Yahoo! Mail ? Plus rapide, plus efficace... simplement révolutionnaire ! Découvrez-le. Lien :http://fr.mail.yahoo.com -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#388717: libclass-dbi-perl: FTBFS: test failures
On 21/09/06, Daniel Schepler [EMAIL PROTECTED] wrote: Package: libclass-dbi-perl Version: 3.0.14-1 Severity: serious [ FTBFS] Thanks for the bug report, I was not previously aware of the problem. This appears to be caused by a bug introduced into libdbd-sqlite3-perl version 1.13. If you have access to rt.cpan.org you can see the details at: https://rt.cpan.org/Ticket/Display.html?id=21406 https://rt.cpan.org/Ticket/Display.html?id=21472 Hopefully there will be a fixed version available soon. Stephen -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#388223: marked as done (config/postrm depends on non-essential packages (dbconfig-common, probably ucf))
Your message dated Fri, 22 Sep 2006 23:22:11 +0200 with message-id [EMAIL PROTECTED] and subject line not a bug has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what I am talking about this indicates a serious mail system misconfiguration somewhere. Please contact me immediately.) Debian bug tracking system administrator (administrator, Debian Bugs database) ---BeginMessage--- Package: cacti-cactid Severity: serious Justification: 7.2 -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 hi there, it was recently brought to my attention that the recommended method for using dbconfig-common in a package's config and postrm scripts was not policy compliant as hinted in the subject of this bugreport. the problem is that in both the config and the postrm you should test whether the files/programs in question exist before sourcing/executing them. more information is in a link below. NOTE that this is slightly different from the original posts about mass-bug filing in which only the postrm was mentioned, but the config file is too. so, even if you've fixed your package after i initially posted about this, you might want to take a second look to make sure. this mass bug-filing was announced 2006/08/19, though it seems there's a problem with the list archives for debian-devel. fortunately, i cc'd the dbconfig list: http://lists.alioth.debian.org/pipermail/dbconfig-common-devel/2006-August/000586.html and information for how you can fix your package: http://people.debian.org/~seanius/policy/dbconfig-common.html/ch-develguide.html#s-hooks fortunately, the fix is pretty simple, though i apologize for the inconvenience. feel free to ask if you have any questions. sean - -- System Information: Debian Release: testing/unstable APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.16-2-amd64-k8 Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.5 (GNU/Linux) iD8DBQFFD7vtynjLPm522B0RAtF5AJ96I5lF2lg76twnK24QUpH84GEI7wCeJzzJ G3Uy7IdxRHJ1GTyLAq4nfl4= =Ovso -END PGP SIGNATURE- ---End Message--- ---BeginMessage--- false alarm, cacti-cactid does not use the sample code in question. signature.asc Description: This is a digitally signed message part ---End Message---
Bug#388844: xmms2d crashes on start with Bad glib version message...
Package: xmms2 Version: 0.2DrFeelgood-6 Severity: grave Justification: renders package unusable Hello! I've just installed xmms2 and other dependencies + some other plugins (smb, wma). Now i'am trying to launch xmms2 antono[23:57]~ xmms2 ERROR: Could not connect to xmms2d: xmms2d is not running. ok. let's try to run xmms2d antono[00:02]~ xmms2d Bad glib version: GLib version too old (micro mismatch) You can see below info about installed GLib: antono[00:08]~ aptitude show libglib2.0-0 Package: libglib2.0-0 State: installed Automatically installed: no Version: 2.12.3-2 Priority: optional Section: libs Maintainer: Sebastien Bacher [EMAIL PROTECTED] Uncompressed Size: 1106k Depends: libc6 (= 2.3.6-6) Recommends: libglib2.0-data Conflicts: libpango1.0-0 ( 1.11) Description: The GLib library of C routines GLib is a library containing many useful C routines for things such as trees, hashes, lists, and strings. It is a useful general-purpose C library used by projects such as GTK+, GIMP, and GNOME. This package contains the shared libraries. Tags: devel::library, langdevel::c, made-of::lang:c, role::sw:shlib, uitoolkit::gtk And there is one more version of glib: [00:10]~ aptitude show libglib1.2 Package: libglib1.2 State: installed Automatically installed: no Version: 1.2.10-10.1 Priority: optional Section: oldlibs Maintainer: Akira TAGOH [EMAIL PROTECTED] Uncompressed Size: 279k Depends: libc6 (= 2.3.5-1) Replaces: libgtk-doc Description: The GLib library of C routines GLib is a library containing many useful C routines for things such as trees, hashes, and lists. GLib was previously distributed with the GTK+ toolkit, but has been split off as of the developers' version 1.1.0. You do not need to install this package if you have libgtk1 (note 1, not 1.1 or 1.2) installed. libgtk1 included libglib in it. libgtk1.1 and libgtk1.2, however, do need libglib1.1 to be installed separately. Tags: devel::library, langdevel::c, made-of::lang:c, role::sw:shlib, uitoolkit::gtk -- System Information: Debian Release: testing/unstable APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing'), (1, 'experimental') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.16-2-686 Locale: LANG=eo.UTF-8, LC_CTYPE=eo.UTF-8 (charmap=UTF-8) Versions of packages xmms2 depends on: ii xmms2-client-cli 0.2DrFeelgood-6 XMMS2 - cli client ii xmms2-core 0.2DrFeelgood-6 XMMS2 - core package ii xmms2-plugin-alsa0.2DrFeelgood-6 XMMS2 - ALSA output ii xmms2-plugin-id3v2 0.2DrFeelgood-6 XMMS2 - ID3v2 plugin ii xmms2-plugin-mad 0.2DrFeelgood-6 XMMS2 - libmad based mp3 decoder ii xmms2-plugin-vorbis 0.2DrFeelgood-6 XMMS2 - vorbis decoder xmms2 recommends no packages. -- Antono Vasiljev http://a-n-t-o-n.com/ gpg --keyserver keys.indymedia.org --recv-keys CF07F739 signature.asc Description: Digital signature
Bug#341172: Processed: Fixed in upload of evolution 2.8.0-1 to experimental
On Fri, Sep 22, 2006 at 06:34:00AM -0700, Debian Bug Tracking System wrote: tag 341172 + fixed-in-experimental Bug#341172: Please port to the experimental pilot-link 0.12 API Tags were: patch Tags added: fixed-in-experimental Did you not understand that this version of pilot-link is now in *unstable*, and evolution needs an upload to unstable to fix it? -- Steve Langasek Give me a lever long enough and a Free OS Debian Developer to set it on, and I can move the world. [EMAIL PROTECTED] http://www.debian.org/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Processed: possible NMU patch for RC bug
Processing commands for [EMAIL PROTECTED]: tags 379724 patch Bug#379724: wrong build depends: eval: 1: xa: not found There were no tags set. Tags added: patch usertag 379724 supplied-patch Bug#379724: wrong build depends: eval: 1: xa: not found There were no usertags set. Usertags are now: supplied-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#388214: marked as done (config/postrm depends on non-essential packages (dbconfig-common, probably ucf))
Your message dated Fri, 22 Sep 2006 14:47:30 -0700 with message-id [EMAIL PROTECTED] and subject line Bug#388214: fixed in cacti 0.8.6h-5 has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what I am talking about this indicates a serious mail system misconfiguration somewhere. Please contact me immediately.) Debian bug tracking system administrator (administrator, Debian Bugs database) ---BeginMessage--- Package: cacti Version: -I Severity: serious Justification: 7.2 -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 hi there, it was recently brought to my attention that the recommended method for using dbconfig-common in a package's config and postrm scripts was not policy compliant as hinted in the subject of this bugreport. the problem is that in both the config and the postrm you should test whether the files/programs in question exist before sourcing/executing them. this mass bug-filing was announced 2006/08/19, though it seems there's a problem with the list archives for debian-devel. fortunately, i cc'd the dbconfig list: http://lists.alioth.debian.org/pipermail/dbconfig-common-devel/2006-August/000586.html and information for how you can fix your package: http://people.debian.org/~seanius/policy/dbconfig-common.html/ch-develguide.html#s-hooks fortunately, the fix is pretty simple, though i apologize for the inconvenience. feel free to ask if you have any questions. sean - -- System Information: Debian Release: testing/unstable APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.16-2-amd64-k8 Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.5 (GNU/Linux) iD8DBQFFD7YMynjLPm522B0RAl+6AJ4oPfDNpiJvuvzdPPjrMyVjuXIuWwCfY+Vi 8CQgoLt1yCPYBIbGYEAXONQ= =T3qn -END PGP SIGNATURE- ---End Message--- ---BeginMessage--- Source: cacti Source-Version: 0.8.6h-5 We believe that the bug you reported is fixed in the latest version of cacti, which is due to be installed in the Debian FTP archive: cacti_0.8.6h-5.diff.gz to pool/main/c/cacti/cacti_0.8.6h-5.diff.gz cacti_0.8.6h-5.dsc to pool/main/c/cacti/cacti_0.8.6h-5.dsc cacti_0.8.6h-5_all.deb to pool/main/c/cacti/cacti_0.8.6h-5_all.deb A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to [EMAIL PROTECTED], and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. sean finney [EMAIL PROTECTED] (supplier of updated cacti 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, 22 Sep 2006 21:04:19 +0200 Source: cacti Binary: cacti Architecture: source all Version: 0.8.6h-5 Distribution: unstable Urgency: low Maintainer: sean finney [EMAIL PROTECTED] Changed-By: sean finney [EMAIL PROTECTED] Description: cacti - Frontend to rrdtool for monitoring systems and services Closes: 374020 387540 388214 Changes: cacti (0.8.6h-5) unstable; urgency=low . * fix for braindead bug in postrm script introduced by yours truly. fixed a bashism in there while i was at it (closes: #387540). thanks to Olivier Berger for finding this. * fix for non-essential dependencies (dbconfig-common) in the config script (closes: #388214). * updated portuguese brazillian templates, thanks to Andre Luis Lopes for providing them (closes: #374020). Files: 22e6185b2d87b1572c99f304a31cc3b9 583 web extra cacti_0.8.6h-5.dsc 83bed19a1b7873f72fad735e75f464df 33430 web extra cacti_0.8.6h-5.diff.gz 5757cfec774cfc5ef4d3772befbf19d8 922852 web extra cacti_0.8.6h-5_all.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.5 (GNU/Linux) iD8DBQFFFDtlynjLPm522B0RAsFlAJwLdjH9Lzn/KWvoM8IBdMApTG3k0gCggDfX 0bK+ALDBNmRsRamGNC9gG2k= =XB0z -END PGP SIGNATURE- ---End Message---
Bug#379724: possible NMU patch for RC bug
tags 379724 patch usertag 379724 supplied-patch thanks Hi, I have prepared a simple patch for the FTFBS which is attached. As I am no DD yet, I can not do the actual NMU. Marga would you like to do the actual upload? Greetings Arjan Changelog of my NMU: * Non-maintainer upload. * Set urgency to medium as this upload fixes an RC bug. * debian/rules: - Don't let build target depend on build-indep target as the build daemons will call the build target without Build-Depends-Indep satisfied. (Closes: #379724) - Drop DH_COMPAT=3 as compatibility levels before 4 are deprecated. * debian/copyright: update address of the FSF. * debian/compat: added and bump debhelper compatibility level to 4 and adjust Build-Depends on debhelper accordingly. diff -u cbmlink-0.9.6/debian/control cbmlink-0.9.6/debian/control --- cbmlink-0.9.6/debian/control +++ cbmlink-0.9.6/debian/control @@ -2,7 +2,7 @@ Section: otherosfs Priority: extra Maintainer: Peter Karlsson [EMAIL PROTECTED] -Build-Depends: debhelper ( 3.0.0) +Build-Depends: debhelper (= 4.0.0) Build-Depends-Indep: xa65 Standards-Version: 3.6.0 diff -u cbmlink-0.9.6/debian/rules cbmlink-0.9.6/debian/rules --- cbmlink-0.9.6/debian/rules +++ cbmlink-0.9.6/debian/rules @@ -6,9 +6,6 @@ # Uncomment this to turn on verbose mode. #export DH_VERBOSE=1 -# This is the debhelper compatibility version to use. -export DH_COMPAT=3 - ifneq (,$(findstring debug,$(DEB_BUILD_OPTIONS))) CFLAGS += -g endif @@ -89,7 +86,7 @@ # Combined portion --- -build: build-arch build-indep +build: build-arch clean: dh_testdir diff -u cbmlink-0.9.6/debian/changelog cbmlink-0.9.6/debian/changelog --- cbmlink-0.9.6/debian/changelog +++ cbmlink-0.9.6/debian/changelog @@ -1,3 +1,18 @@ +cbmlink (0.9.6-1.1) unstable; urgency=medium + + * Non-maintainer upload. + * Set urgency to medium as this upload fixes an RC bug. + * debian/rules: +- Don't let build target depend on build-indep target as the build + daemons will call the build target without Build-Depends-Indep + satisfied. (Closes: #379724) +- Drop DH_COMPAT=3 as compatibility levels before 4 are deprecated. + * debian/copyright: update address of the FSF. + * debian/compat: added and bump debhelper compatibility level to 4 and +adjust Build-Depends on debhelper accordingly. + + -- Arjan Oosting [EMAIL PROTECTED] Fri, 22 Sep 2006 23:36:05 +0200 + cbmlink (0.9.6-1) unstable; urgency=low * Initial Release. diff -u cbmlink-0.9.6/debian/copyright cbmlink-0.9.6/debian/copyright --- cbmlink-0.9.6/debian/copyright +++ cbmlink-0.9.6/debian/copyright @@ -17,9 +17,9 @@ GNU General Public License for more details. You should have received a copy of the GNU General Public License - along with this package; if not, write to the Free Software - Foundation, Inc., 59 Temple Place - Suite 330, Boston, MA - 02111-1307, USA. + along with this package; if not, write to the Free Software + Foundation, Inc., 51 Franklin St, Fifth Floor, Boston, + MA 02110-1301, USA. On Debian GNU/Linux systems, the complete text of the GNU General Public License can be found in `/usr/share/common-licenses/GPL'. only in patch2: unchanged: --- cbmlink-0.9.6.orig/debian/compat +++ cbmlink-0.9.6/debian/compat @@ -0,0 +1 @@ +4 signature.asc Description: Dit berichtdeel is digitaal ondertekend
Bug#387610: subversion: FTBFS on ia64
On 09/22/06 16:32, Philip Martin wrote:
The first time the breakpoint is reached it's from the
svn_test__create_fs line, the second time it's from the
svn_fs_open_berkeley line. The key has the same value in each case,
and the second time that value is present in the cache, so the hash
lookup doesn't return NULL.
Hi Philip,
It looks like the hash is getting updated fine during the initial
create. However, on the second one it goes through init again and
comes up with a new ht pointer. Digging into it I think I've found the
problem in libapr0, although I was kind of rushed and didn't have time
to test it because I'm leaving for a trip and out the door now.
In any case, this looks like the culprit.
apr_uint32_t apr_atomic_cas(volatile apr_uint32_t *mem, long with,
long cmp)
{
long prev;
#if APR_HAS_THREADS
apr_thread_mutex_t *lock = hash_mutex[ATOMIC_HASH(mem)];
if (apr_thread_mutex_lock(lock) == APR_SUCCESS) {
prev = *(long*)mem;
if (prev == cmp) {
*(long*)mem = with;
}
apr_thread_mutex_unlock(lock);
return prev;
On a 64-bit machine we end up with a size mismatch and a compare of
junk. mem is defined as a pointer to a 32-bit, then a cast to long
64-bit in this case. prev ends up with junk it it and fails the
compare prev == cmp that passes on a 32-bit box. In any case this is a
bug, not positive if it's the only one.
Troy
pgpXlshtL1lP9.pgp
Description: PGP signature
Bug#388691: ibm-3270: Licensing issues
[sent also to debian-legal for advice] --- Bastian Blank [EMAIL PROTECTED] escreveu: On Fri, Sep 22, 2006 at 02:47:55PM -0300, Wagner Bruna wrote: --- Bastian Blank [EMAIL PROTECTED] escreveu: Particularly, public use needs clarification: Copyright 1989 by Georgia Tech Research Corporation, Atlanta, GA 30332. All Rights Reserved. GTRC hereby grants public use of this software. Neither I nor the ftp-team see a problem with that. AAUI, if the copyright notice only grants public use of the software, it's not conforming with DFSG guidelines (The license must not restrict anyone from making use of the program in a specific field of endeavor.). As it is phrased, the license does not explicitely grant unrestricted use, so the package at least should not be in main. You have to explain why public use is restricted. I don't know what public use means. Does it mean that I can only use it on public computers, at a public library for example? Is it free for the public, for anyone? Could I use it privately, internally at my organization? Is it possible to clarify, on the copyright note, what GTRC means by public use? If it does mean unrestricted as implied, great, but IMHO the copyright file should say so unequivocally. (Note that GTRC was contacted before to clarify these statements; see bug 321178.) Well, there is another source package of this code (since oldstable, at least), maintained by him: http://packages.qa.debian.org/3/3270.html And its copyright file states: Well, this is neither a statement from the ftp-team, nor from me, nor from upstream. So please clarify upstream's statement. Thanks, Wagner ___ Novidade no Yahoo! Mail: receba alertas de novas mensagens no seu celular. Registre seu aparelho agora! http://br.mobile.yahoo.com/mailalertas/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#388691: ibm-3270: Licensing issues
--- Steve Langasek [EMAIL PROTECTED] wrote: [public use] Your reading of this clause is not the plain English reading of it. public use does not mean use in public, in means use by the public -- i.e., use by anyone. I don't know if it is clear enough, at least for a non-native English speaker (me). Bug 321178 also suggests it should be worded better. If this was the only problematic clause, I agree there's no problem here. I assumed, based on the bug report you submitted, that there was an issue with the license not permitting /modification and distribution/, rather than use. Well, I submitted it as serious, and justified by Policy 2.3, because the copyright file stated itself as a work in progress, and 3270 was removed before because of licensing issues (although some of them not relevant anymore). But, if there's no problem, sorry for the noise. Thanks, Wagner ___ Você quer respostas para suas perguntas? Ou você sabe muito e quer compartilhar seu conhecimento? Experimente o Yahoo! Respostas ! http://br.answers.yahoo.com/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Processed: purge failures w/o debconf not RC
Processing commands for [EMAIL PROTECTED]: severity 388646 important Bug#388646: cpad-kernel-source: purging the package fails (debconf unavailable) Severity set to `important' from `serious' severity 388155 important Bug#388155: cyrus21-common: purging the package fails (require debconf) Severity set to `important' from `serious' severity 388603 important Bug#388603: diogenes: purging the package fails (debconf not available) Severity set to `important' from `serious' severity 388604 important Bug#388604: drupal: purging the package fails (debconf unavailable) Severity set to `important' from `serious' severity 388782 important Bug#388782: fonty: purging the package fails (debconf unavailable) Severity set to `important' from `serious' severity 388610 important Bug#388610: isdnutils-base: purging the package fails (debconf unavailable) Severity set to `important' from `serious' severity 388784 important Bug#388784: krb5-kdc: purging the package fails (debconf unavailable) Severity set to `important' from `serious' severity 387979 important Bug#387979: libhtml-mason-perl-examples: purging the package fail without debconf Severity set to `important' from `serious' severity 388600 important Bug#388600: mlmmj: purging the package fails (debconf not available) Severity set to `important' from `serious' severity 388666 important Bug#388666: namazu2: purging the package fails (debconf unavailable) Severity set to `important' from `serious' severity 388780 important Bug#388780: netenv: purging the package fails (debconf unavailable) Severity set to `important' from `serious' severity 388676 important Bug#388676: pconsole: purging the package fails (debconf unavailable) Severity set to `important' from `serious' severity 388331 important Bug#388331: phpbb2: purging the package try to use debconf which was already removed Severity set to `important' from `serious' severity 388781 important Bug#388781: phpsysinfo: purging the package fails (debconf unavailable) Severity set to `important' from `serious' severity 388783 important Bug#388783: shfs-utils: purging the package fails (debconf unavailable) Severity set to `important' from `serious' severity 388156 important Bug#388156: tex-common: purging the package fails (debconf is not available) Severity set to `important' from `serious' thanks Stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#387610: apr_atomic_cas broken in 0.9.x
Troy Heber [EMAIL PROTECTED] writes:
In any case, this looks like the culprit.
Agreed, I've cc'd [EMAIL PROTECTED] The C implementation of apr_atomic_cas
on the 0.9.x branch is broken on ia64, and probably any other 64 bit
platform that uses the same code. For the full story see:
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=387610
apr_uint32_t apr_atomic_cas(volatile apr_uint32_t *mem, long with,
long cmp)
{
long prev;
#if APR_HAS_THREADS
apr_thread_mutex_t *lock = hash_mutex[ATOMIC_HASH(mem)];
if (apr_thread_mutex_lock(lock) == APR_SUCCESS) {
prev = *(long*)mem;
if (prev == cmp) {
*(long*)mem = with;
}
apr_thread_mutex_unlock(lock);
return prev;
On a 64-bit machine we end up with a size mismatch and a compare of
junk. mem is defined as a pointer to a 32-bit, then a cast to long
64-bit in this case. prev ends up with junk it it and fails the
compare prev == cmp that passes on a 32-bit box. In any case this is a
bug, not positive if it's the only one.
It looks like it has already been fixed in apr1.2 (as used by apache2.2):
apr_uint32_t apr_atomic_cas32(volatile apr_uint32_t *mem, apr_uint32_t with,
apr_uint32_t cmp)
{
apr_uint32_t prev;
#if APR_HAS_THREADS
apr_thread_mutex_t *lock = hash_mutex[ATOMIC_HASH(mem)];
CHECK(apr_thread_mutex_lock(lock));
prev = *mem;
if (prev == cmp) {
*mem = with;
}
CHECK(apr_thread_mutex_unlock(lock));
#else
prev = *mem;
if (prev == cmp) {
*mem = with;
}
#endif /* APR_HAS_THREADS */
return prev;
}
--
Philip Martin
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#352854: marked as done (FTBFS: Packages required but not available: mlmRev)
Your message dated Fri, 22 Sep 2006 18:07:21 -0500 with message-id [EMAIL PROTECTED] and subject line Closed in new version of lme4 has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what I am talking about this indicates a serious mail system misconfiguration somewhere. Please contact me immediately.) Debian bug tracking system administrator (administrator, Debian Bugs database) ---BeginMessage--- Package: lme4 Severity: serious Justification: no longer builds from source Hi, lme4 0.995.2-1 is failing to build (at least) on amd64, ia64, alpha, hppa and powerpc. It has an error, and a warning: [...] * checking for file 'lme4/DESCRIPTION' ... OK * this is package 'lme4' version '0.995-2' * checking if this is a source package ... OK * checking whether package 'lme4' can be installed ... WARNING Found the following significant warnings: missing link(s): groupedData getGroups * checking package directory ... OK * checking for portable file names ... OK * checking for sufficient/correct file permissions ... OK * checking DESCRIPTION meta-information ... OK * checking package dependencies ... ERROR Packages required but not available: mlmRev make: *** [R_any_arch] Error 1 Thanks, Roberto -- System Information: Debian Release: testing/unstable APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.15 Locale: [EMAIL PROTECTED], [EMAIL PROTECTED] (charmap=UTF-8) (ignored: LC_ALL set to [EMAIL PROTECTED]) ---End Message--- ---BeginMessage--- I forgot to close this old open bug with tag 'fixed' when I made the following upload with a new lme4: lme4 (0.9975-0-1) unstable; urgency=low * New maintainer, keeping Doug as an Uploaders: in debian/control * New upstream release for the upcoming R 2.4.0 release, built using the R 2.4.0 releases candidate * debian/control: Upgraded Build-Depends: to 'r-base-dev ( 2.3.1)' and Depends: to 'r-base-core ( 2.3.1)' accordingly * debian/control: As of this upstream release, package now contains compiled code, so changed Architecture: to any [lintian] * debian/control: Removed trailing synopsis in Description [lintian] -- Dirk Eddelbuettel [EMAIL PROTECTED] Wed, 20 Sep 2006 23:27:25 -0500 As the buildd shows, the FTBFS no longer applies thanks to upstream fixes Doug made a while ago. Thanks, Dirk -- Hell, there are no rules here - we're trying to accomplish something. -- Thomas A. Edison ---End Message---
Bug#388031: marked as done (radeontool FTBFS on powerpc/unstable)
Your message dated Fri, 22 Sep 2006 16:02:12 -0700 with message-id [EMAIL PROTECTED] and subject line Bug#388031: fixed in radeontool 1.5-4 has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what I am talking about this indicates a serious mail system misconfiguration somewhere. Please contact me immediately.) Debian bug tracking system administrator (administrator, Debian Bugs database) ---BeginMessage--- Package: radeontool Version: 1.5-3 Severity: serious Tags: patch Justification: no longer builds from source Hi, radeontool FTBFS on powerpc with following error: gcc -Wall -O2 radeontool.c -o radeontool radeontool.c: In function 'map_devince_memory': radeontool.c:97: error: 'PAGE_SIZE' undeclared (first use in this function) radeontool.c:97: error: (Each undeclared identifier is reported only once radeontool.c:97: error: for each function it appears in.) make[1]: *** [radeontool] Error 1 make[1]: Leaving directory `/home/corsac/builds/radeontool-1.5.orig' make: *** [build-stamp] Error 2 Attached patch (taken from #384307) fix the problem. Regards, -- Yves-Alexis Perez -- System Information: Debian Release: testing/unstable APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing'), (500, 'stable'), (1, 'experimental') Architecture: powerpc (ppc) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.18-rc6 Locale: [EMAIL PROTECTED], [EMAIL PROTECTED] (charmap=ISO-8859-15) Versions of packages radeontool depends on: ii libc62.3.6.ds1-4 GNU C Library: Shared libraries radeontool recommends no packages. -- no debconf information diff -urN radeontool-1.5.orig/radeontool.c radeontool-1.5/radeontool.c --- radeontool-1.5.orig/radeontool.c 2004-02-11 04:50:27.0 +0100 +++ radeontool-1.5/radeontool.c 2006-09-18 09:43:38.0 +0200 @@ -21,10 +21,11 @@ #include sys/stat.h #include fcntl.h #include sys/mman.h -#include asm/page.h #include radeon_reg.h +#define PAGE_SIZE sysconf(_SC_PAGE_SIZE) + int debug; int skip; ---End Message--- ---BeginMessage--- Source: radeontool Source-Version: 1.5-4 We believe that the bug you reported is fixed in the latest version of radeontool, which is due to be installed in the Debian FTP archive: radeontool_1.5-4.diff.gz to pool/main/r/radeontool/radeontool_1.5-4.diff.gz radeontool_1.5-4.dsc to pool/main/r/radeontool/radeontool_1.5-4.dsc radeontool_1.5-4_sparc.deb to pool/main/r/radeontool/radeontool_1.5-4_sparc.deb A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to [EMAIL PROTECTED], and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Luigi Gangitano [EMAIL PROTECTED] (supplier of updated radeontool package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing [EMAIL PROTECTED]) -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Sat, 23 Sep 2006 00:38:41 +0200 Source: radeontool Binary: radeontool Architecture: source sparc Version: 1.5-4 Distribution: unstable Urgency: low Maintainer: Luigi Gangitano [EMAIL PROTECTED] Changed-By: Luigi Gangitano [EMAIL PROTECTED] Description: radeontool - utility to control ATI Radeon backlight functions on laptops Closes: 388031 Changes: radeontool (1.5-4) unstable; urgency=low . * radeontool.c - Applied patch to fix FTBFS on powerpc (Thanks to Yves-Alexis Perez) (Closes: #388031) Files: 467127747663f401707baa69dc8d1872 593 utils optional radeontool_1.5-4.dsc 7b22284cd5f3213a482b2e19b64d946b 4227 utils optional radeontool_1.5-4.diff.gz 9e38b46b69fda78dfc60b6882286b34b 9314 utils optional radeontool_1.5-4_sparc.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.5 (GNU/Linux) iD8DBQFFFGb08ZumGJJMDCYRAuvlAJwK2vUKCm2qmOuKUJLTTZ+vhCIkqgCeNh/T qATpFfiI/gANgVZR2P5u7z4= =KjW9 -END PGP SIGNATURE- ---End Message---
Bug#387610: apr_atomic_cas broken in 0.9.x
Philip or Troy - would you care to prepare and test the backport to ensure
we can commit this for the next 0.9 release, coming within days?
Bill
Philip Martin wrote:
Troy Heber [EMAIL PROTECTED] writes:
In any case, this looks like the culprit.
Agreed, I've cc'd [EMAIL PROTECTED] The C implementation of apr_atomic_cas
on the 0.9.x branch is broken on ia64, and probably any other 64 bit
platform that uses the same code. For the full story see:
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=387610
apr_uint32_t apr_atomic_cas(volatile apr_uint32_t *mem, long with,
long cmp)
{
long prev;
#if APR_HAS_THREADS
apr_thread_mutex_t *lock = hash_mutex[ATOMIC_HASH(mem)];
if (apr_thread_mutex_lock(lock) == APR_SUCCESS) {
prev = *(long*)mem;
if (prev == cmp) {
*(long*)mem = with;
}
apr_thread_mutex_unlock(lock);
return prev;
On a 64-bit machine we end up with a size mismatch and a compare of
junk. mem is defined as a pointer to a 32-bit, then a cast to long
64-bit in this case. prev ends up with junk it it and fails the
compare prev == cmp that passes on a 32-bit box. In any case this is a
bug, not positive if it's the only one.
It looks like it has already been fixed in apr1.2 (as used by apache2.2):
apr_uint32_t apr_atomic_cas32(volatile apr_uint32_t *mem, apr_uint32_t with,
apr_uint32_t cmp)
{
apr_uint32_t prev;
#if APR_HAS_THREADS
apr_thread_mutex_t *lock = hash_mutex[ATOMIC_HASH(mem)];
CHECK(apr_thread_mutex_lock(lock));
prev = *mem;
if (prev == cmp) {
*mem = with;
}
CHECK(apr_thread_mutex_unlock(lock));
#else
prev = *mem;
if (prev == cmp) {
*mem = with;
}
#endif /* APR_HAS_THREADS */
return prev;
}
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#388489: Processed: Cloning this bug
reopen 388489
severity wishlist
thanks
Aurelien Jarno [EMAIL PROTECTED] writes:
Goswin von Brederlow wrote:
reopen 388489
thanks
Aurelien Jarno [EMAIL PROTECTED] writes:
Goswin von Brederlow wrote:
Aurelien Jarno [EMAIL PROTECTED] writes:
Debian Bug Tracking System a écrit :
retitle -1 libc6-i386: Missing /etc.ld.so.conf.d/i486-linux-gnu.conf
There is no need for such a file. ld.so natively looks on all
directories of bi (or tri)-arches directories. If you need to be
convinced just run: strings /sbin/ldconfig | grep ^/lib
Clising the bug
Binutils doesn't. And in some cases binutils looks at ld.so.conf and
It does. Well it was not the case on amd64, but it has been fixed two
months ago in version 2.17-2 (see bug#369052).
I am closing the bug, please only reopen the bug if you have a
testcase to show what you claim.
Then what is /etc/ld.so.conf.d/x86_64-linux-gnu.conf for? If 32bit
multiarch support doesn't need the conffile then 64bit multiarch would
need it even less, being the native bit-ness and all. Think about that
for a second.
Meanwhile here is your testcase step by step:
Create missing link so we can link (pending fix in ia32-libs):
% ln -s /usr/lib32/libfreetype.so.6 /usr/lib32/libfreetype.so
Test /usr/lib32 setup:
% cat foo.c
extern int FT_Init_FreeType(void);
int main(void) { return FT_Init_FreeType(); }
% gcc -m32 -o foo foo.c -lfreetype
So this works. Multiarch not being a requirement for Etch, I fail to
see why the severity of this bug is serious.
Because the submitter reported it as such and nobody has adjusted it
since then.
Test multiarch:
% mkdir /usr/lib/i486-linux-gnu
% mv /usr/lib32/libz.* /usr/lib/i486-linux-gnu
Wrong. The purpose of multiarch is to remove bi-arch packages. With
multiarch if you want to install a 32-bit glibc on amd64, install the
package from i386. Not libc6-i386.
We can't lay an egg because we have no chicken and we can't breed a
chicken because we have no eggs. The purpose of libc6-i386 is to cover
the interim time till multiarch and it isn't to strictly deadlock
everything at bi-arch.
Remeber that we already did have the libc6 package from i386 in use in
ia32-libs (and still have). You wanted to have a special libc6-i386
package for amd64 and since you maintain glibc we respected that. We
can add libc6 back to the list of packages for amd64 if you don't want
to provide a transitional package that mimics multiarch. That would be
a one line change.
The ld.so.conf.d/i486-linux-gnu.conf file is essential so multiarch
directories can be used already and to allow a smooth transition. The
ld.so.conf.d/i486-linux-gnu.conf files only logical place is in the
libc6[-i386] packages and the multiarch libc6 oni386 already has to
conflict with libc6-i386 on amd64 (reverse for libc6-amd64). If
ld.so.conf.d/i486-linux-gnu.conf is in any other package then that
just further complicates the dependencies and conflicts in the future.
I see 3 scenarios where I would consider this bug fixed:
1) you add the file
2) ia32-libs takes the libc6-i386 package
3) binutils adds the patch from #369064 and obsoletes the
/etc/ld.so.conf.d/arch-os-gnu.conf files
MfG
Goswin
Processed: Re: Processed: Cloning this bug
Processing commands for [EMAIL PROTECTED]: reopen 388489 Bug#388489: libc6-i386: Missing /etc.ld.so.conf.d/i486-linux-gnu.conf Bug reopened, originator not changed. severity wishlist Unknown command or malformed arguments to command. 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]
