Processed: reassign 584824 to logcheck-database
Processing commands for cont...@bugs.debian.org: reassign 584824 logcheck-database Bug #584824 [logcheck-database,ntop] ntop and logcheck-database: error when trying to install together Bug reassigned from package 'logcheck-database,ntop' to 'logcheck-database'. thanks Stopping processing here. Please contact me if you need assistance. -- 584824: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=584824 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#584748: ../sysdeps/x86_64/cacheinfo.c:255: handle_intel: Assertion `maxidx = 2' on AMD cpu
Aurelien Jarno a écrit : On Sun, Jun 06, 2010 at 10:27:12PM +0200, Gianluigi Tiesi wrote: On 06/06/2010 14.55, Aurelien Jarno wrote: On Sun, Jun 06, 2010 at 02:17:29PM +0200, Gianluigi Tiesi wrote: On 06/06/2010 13.21, Aurelien Jarno wrote: Kernel: Linux 2.6.26-2-xen-amd64 (SMP w/8 CPU cores) This part is not consistent. Are you running reportbug on a different machine? yes the problem is on a old amd 800mhz box, but I use a different box for submitting do you need some additional infos about the amd installation? Yes, which libc6 packages are actually installed? I have fixed a bug that my cause the problem you are observing in version 2.11.1-2, so if you are running version 2.11.1-1, please try to upgrade. Also which kernel are you running? libc is 2.11.1-2 kernel: Linux attila 2.6.32-5-686 #1 SMP Tue Jun 1 04:59:47 UTC 2010 i686 GNU/Linux I known the problem with libc6-i686 and intel i7 I've reported some info too :) It's not the problem with core i7, but a different one that has also been corrected. One that breaks reading model and family in some conditions. this look different Unfortunately I am not able to reproduce it. Tried on an Athlon and on Opteron CPU. For your information, I have been able to find a machine with a CPU identical to yours, and I am now able to reproduce the issue. I'll debug it later today. -- Aurelien Jarno GPG: 1024D/F1BCDB73 aurel...@aurel32.net http://www.aurel32.net -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: tagging 584824, tagging 584849
Processing commands for cont...@bugs.debian.org: # fixed in 3200156 tags 584824 pending Bug #584824 [logcheck-database] ntop and logcheck-database: error when trying to install together Added tag(s) pending. tags 584849 pending Bug #584849 [logcheck-database] logcheck-database 1.3.9 ntop 3.3-13 conflict Added tag(s) pending. thanks Stopping processing here. Please contact me if you need assistance. -- 584849: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=584849 584824: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=584824 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#584610: [mips] gcc-4.4 build failure after upgrade to eGLIBC-2.11
On 06.06.2010 00:51, Aurelien Jarno wrote: On Sat, Jun 05, 2010 at 03:50:51AM +0200, Matthias Klose wrote: Package: eGLIBC Version: 2.11.1-2 Severity: serious gcc-4.4 and gcc-4.5 fail to build after the upgrade to eGLIBC-2.11: https://buildd.debian.org/fetch.cgi?pkg=gcc-4.4;ver=4.4.4-4;arch=mips;stamp=1275677666 This FTBFS is caused by the following change: |2009-11-20 Jakub Jelinekja...@redhat.com | |PR libc/10103 | |* math/math.h: Provide *l long double prototypes redirecting |to double functions even when __NO_LONG_DOUBLE_MATH and not |__LDBL_COMPAT. |* math/complex.h: Likewise. These functions were present before in the library, but not exported in the headers. This has been changed as it is required by ISO C99. GCC tries to find these functions in the GLIBC by compiling a program, so it was failing before, and is successful now. When they are already present in the GLIBC it does not re-export them. Strangely this should also affect ARM, but it seems to build correctly. I haven't investigated why. While these functions are strictly not needed in libstdc++6 anymore, we have two options: - revert the GLIBC change, which means we break the C99 compatibility (as before) - patch GCC to export these functions anyway. What's your opinion? For ARM I did choose the second option, but didn't get any feedback about it. So maybe it's time to ask the mips and arm porters? The patch applied for armel is: http://svn.debian.org/viewsvn/gcccvs/branches/sid/gcc-4.4/debian/patches/libstdc%2B%2B-arm-ldbl-compat.diff?view=log -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#584671: [lxr-cvs] new stable version fix security hole
On 05.06.2010 15:00, Xavier Brochard wrote: Package: lxr-cvs Version: 0.9.5+cvs20071020-1 Severity: serious Tags: security X-Debbugs-CC: secure-testing-t...@lists.alioth.debian.org --- Please enter the report below this line. --- Please update lxr-cvs to the new stable version. The new version 0.9.8 of lxrng fix several cross-site scripting vulnerabilities (CVE-2009-4497) reported in bug #575745 The new version was published 2010-01-15 on http://sourceforge.net/projects/lxr/ Yes, I'll push the security fix. Note that the new upstream version is not a releasable version: it was an alpha version with the security fix added, but still it is not really working. ciao cate -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#584824: marked as done (ntop and logcheck-database: error when trying to install together)
Your message dated Mon, 07 Jun 2010 07:32:11 + with message-id e1olwod-0007pl...@ries.debian.org and subject line Bug#584824: fixed in logcheck 1.3.10 has caused the Debian Bug report #584824, regarding ntop and logcheck-database: error when trying to install together 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 this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 584824: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=584824 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: logcheck-database,ntop Version: logcheck-database/1.3.9 Version: ntop/3:3.3-13 Severity: serious User: trei...@debian.org Usertags: edos-file-overwrite Date: 2010-06-06 Architecture: amd64 Distribution: sid Hi, automatic installation tests of packages that share a file and at the same time do not conflict by their package dependency relationships has detected the following problem: WARNING: The following packages cannot be authenticated! libpcre3 libxml2 ucf defoma libfreetype6 ttf-dejavu-core fontconfig-config libfontconfig1 fontconfig libpixman-1-0 libpng12-0 libxau6 libxdmcp6 libxcb1 libx11-data libx11-6 libxcb-render0 libxcb-render-util0 libxrender1 libcairo2 libdatrie1 libdbi0 libglib2.0-0 libpango1.0-common libthai-data libthai0 libxft2 libpango1.0-0 libpcap0.8 librrd4 logcheck-database ntop Extracting templates from packages: 93% Extracting templates from packages: 100% Preconfiguring packages ... Warning: cannot open /proc/net/dev (No such file or directory). Limited output. Authentication warning overridden. Can not write log, openpty() failed (/dev/pts not mounted?) Selecting previously deselected package libpcre3. (Reading database ... 12205 files and directories currently installed.) Unpacking libpcre3 (from .../libpcre3_8.02-1_amd64.deb) ... Selecting previously deselected package libxml2. Unpacking libxml2 (from .../libxml2_2.7.7.dfsg-2_amd64.deb) ... Selecting previously deselected package ucf. Unpacking ucf (from .../archives/ucf_3.0025_all.deb) ... Moving old data out of the way Selecting previously deselected package defoma. Unpacking defoma (from .../defoma_0.11.11_all.deb) ... Selecting previously deselected package libfreetype6. Unpacking libfreetype6 (from .../libfreetype6_2.3.11-1_amd64.deb) ... Selecting previously deselected package ttf-dejavu-core. Unpacking ttf-dejavu-core (from .../ttf-dejavu-core_2.31-1_all.deb) ... Selecting previously deselected package fontconfig-config. Unpacking fontconfig-config (from .../fontconfig-config_2.8.0-2.1_all.deb) ... Selecting previously deselected package libfontconfig1. Unpacking libfontconfig1 (from .../libfontconfig1_2.8.0-2.1_amd64.deb) ... Selecting previously deselected package fontconfig. Unpacking fontconfig (from .../fontconfig_2.8.0-2.1_amd64.deb) ... Selecting previously deselected package libpixman-1-0. Unpacking libpixman-1-0 (from .../libpixman-1-0_0.16.4-1_amd64.deb) ... Selecting previously deselected package libpng12-0. Unpacking libpng12-0 (from .../libpng12-0_1.2.43-1_amd64.deb) ... Selecting previously deselected package libxau6. Unpacking libxau6 (from .../libxau6_1%3a1.0.5-2_amd64.deb) ... Selecting previously deselected package libxdmcp6. Unpacking libxdmcp6 (from .../libxdmcp6_1%3a1.0.3-2_amd64.deb) ... Selecting previously deselected package libxcb1. Unpacking libxcb1 (from .../libxcb1_1.6-1_amd64.deb) ... Selecting previously deselected package libx11-data. Unpacking libx11-data (from .../libx11-data_2%3a1.3.3-3_all.deb) ... Selecting previously deselected package libx11-6. Unpacking libx11-6 (from .../libx11-6_2%3a1.3.3-3_amd64.deb) ... Selecting previously deselected package libxcb-render0. Unpacking libxcb-render0 (from .../libxcb-render0_1.6-1_amd64.deb) ... Selecting previously deselected package libxcb-render-util0. Unpacking libxcb-render-util0 (from .../libxcb-render-util0_0.3.6-1_amd64.deb) ... Selecting previously deselected package libxrender1. Unpacking libxrender1 (from .../libxrender1_1%3a0.9.5-2_amd64.deb) ... Selecting previously deselected package libcairo2. Unpacking libcairo2 (from .../libcairo2_1.8.10-4_amd64.deb) ... Selecting previously deselected package libdatrie1. Unpacking libdatrie1 (from .../libdatrie1_0.2.3-1_amd64.deb) ... Selecting previously deselected package libdbi0. Unpacking libdbi0 (from .../libdbi0_0.8.2-3_amd64.deb) ... Selecting previously deselected package libglib2.0-0. Unpacking libglib2.0-0 (from .../libglib2.0-0_2.24.1-1_amd64.deb) ... Selecting previously deselected package libpango1.0-common. Unpacking libpango1.0-common (from .../libpango1.0-common_1.28.0-1_all.deb) ... Selecting previously deselected
Bug#582874: [Debian-ha-maintainers] [PATCH] debian/rules: force bash for configure (#582874)
On Wed, May 26, 2010 at 06:04:38PM +0900, Simon Horman wrote: [CCed bug] On Wed, May 26, 2010 at 08:38:52AM +0200, Florian Haas wrote: On 05/26/2010 02:00 AM, Simon Horman wrote: On Tue, May 25, 2010 at 12:32:57PM +0200, Florian Haas wrote: # HG changeset patch # User Florian Haas florian.h...@linbit.com # Date 1274778576 -7200 # Branch sid # Node ID 8c7e088098feba1d4bae115acb3d646b743e2462 # Parent 01459d573bc597a83911cdb78deba704dea0ad79 debian/rules: force bash for configure (#582874) Fix debian/rules to explicitly invoke bash for running configure (see BTS #582874). Is forcing bash the best solution to this problem? I figured it was, as it was one of the suggested solutions mentioned in the bug report. But other reporters apparently mentioned that export CONFIG_SHELL=/bin/bash worked better for them. As for whether export -n in that autoconf script is actually needed I'm not certain -- please look into it, that part is from you. :) Point taken. I'm surprised that if fails given that the line in question is export -n CFLAGS || true Hi, I propose the following patch as a solution to this problem: unset CFLAGS in a dash-friendly way According to the dash man page, the only way to unexport a variable is to unset it. This also works in bash. For the record, the reason that CFLAGS is exported from the environment to configure and configure appends -Werror to the CFLAGS then it will be re-exported by configure and has been observed to cause trouble when configure runs a separate configure is the libltdl directory. Signed-off-by: Simon Horman ho...@verge.net.au diff -r cc74c5d2e9f3 configure.ac --- a/configure.ac Sun May 16 21:10:59 2010 +0200 +++ b/configure.ac Mon Jun 07 16:55:53 2010 +0900 @@ -1140,7 +1140,10 @@ CC_EXTRAS= if export | fgrep CFLAGS= /dev/null; then - export -n CFLAGS || true # We don't want to bomb out if this fails + SAVED_CFLAGS=$CFLAGS + unset CFLAGS + CFLAGS=$SAVED_CFLAGS + unset SAVED_CFLAGS fi if test $GCC != yes; then -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#584327: patch
On Sun, Jun 6, 2010 at 8:29 PM, Willi Mann wi...@wm1.at wrote: tag 584327 + patch thanks Hi! Hi Attached is a patch for debian/rules that reduces the optimization level to 1 for mipsel and mips, which fixes the problem at least on mipsel. (tested, not tested on mips). I would be nice if you could upload rdflib with this patch soon. Thanks. RDFLib 3.0.0 was recently released. Thus, before uploading a patched debian/rules, I'd like to test whether this issue is reproducible with the new version as well. I'm preparing a package, it would be great if you could test it on your mipsel virtual machine. Give me some time, you will have it in your inbox shortly. Anyway, this is obviously a workaround and, as you pointed out before, we need to generate a minimal test case to report a bug against gcc. Nacho -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#528348: knights: build depends kdebase-kio-plugins no longer exists (need porting to KDE4)
Hi, Miha Čančula is porting knights to KDE4: http://noughmad.wordpress.com/2010/06/05/knights-and-fics/ His code is in KDE playground already. Andrea -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#584858: qtoctave: package upgrade collides with quicktime-utils
Package: qtoctave Version: 0.9.1-1 Severity: grave Hello, qtoctave upgrade to 0.9.1-1 fails due to a file-conflict with quicktime-utils: Preparing to replace qtoctave 0.8.2+dfsg-2 (using .../qtoctave_0.9.1-1_i386.deb) ... Unpacking replacement qtoctave ... dpkg: error processing /var/cache/apt/archives/qtoctave_0.9.1-1_i386.deb (--unpack): trying to overwrite '/usr/bin/qtinfo', which is also in package quicktime-utils 3:1.1.5-0.1 dpkg-deb: subprocess paste killed by signal (Broken pipe) Processing triggers for menu ... Errors were encountered while processing: /var/cache/apt/archives/qtoctave_0.9.1-1_i386.deb Even if I have installed debian-multimedia's version of quicktime-utils, Debian's quicktime-utils 2:1.1.5-1 does also contain /usr/bin/qtinfo. regards Mario -- I thought the only thing the internet was good for was porn. -- Futurama signature.asc Description: Digital signature
Bug#582875: [Debian-ha-maintainers] Bug#582875: cluster-glue: FTBFS: export: 16139: Illegal option -n
There is some discussion of this problem in the cluster-glue edition of this patch, #582874 -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: Re: Bug#584638: debootstrap dependency problems
Processing commands for cont...@bugs.debian.org: reassign 584695 util-linux Bug #584695 [debootstrap] debootstrap: Failure while configuring required packages Bug reassigned from package 'debootstrap' to 'util-linux'. Bug No longer marked as found in versions debootstrap/1.0.23. severity 584695 serious Bug #584695 [util-linux] debootstrap: Failure while configuring required packages Severity set to 'serious' from 'important' merge 584638 584210 584638 Bug#584210: debootstrap: W: Failure while configuring required packages Bug#584638: debootstrap dependency problems Merged 584210 584638. thanks Stopping processing here. Please contact me if you need assistance. -- 584638: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=584638 584210: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=584210 584695: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=584695 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#584861: kdebase-workspace-data: File conflict with ksplash (/usr/share/icons/hicolor/128x1128/apps/ksplash.png)
Package: kdebase-workspace-data Version: 4:4.4.3-1 Severity: serious User: debian-...@lists.debian.org UserTags: debian-edu When trying to upgrade KDE from Lenny to Squeeze, the upgrade fail because kdebase-workspace-data refuses to install because ksplash version 4:3.9.5.dfsg.1-6+lenny1 is already installed and they share the file /usr/share/icons/hicolor/128x1128/apps/ksplash.png. I guess some kind of breaks/conflicts/replaces should be used here to ensure upgrades go smooth. Setting severity to serious, as this issue breaks upgrades and policy state that packages providing the same file need to conflict with each other. Happy hacking, -- Petter Reinholdtsen -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#584517: CVE-2010-0404: Multiple SQL injection vulnerabilities
On 06/06/2010 06:16 PM, Olivier Berger wrote: Thanks for caring. I've tried and fix the most obvious problems reported by lintian and update the changelog, and have re-uploaded an updated package to mentors. If you can upload it for me, many thanks in advance. Best regards, I've added a comma in the changelog and uploaded your package. * New upstream release (includes fix for CVE-2010-0403, CVE-2010-0404, -Closes: #584518 #584517). +Closes: #584518, #584517). * Remove upstream-security-20090722.diff patch (SA35519 / DSA-1978-1 / btw, there are some minor lintian info/warning/pedantic, consider to fix them, they are easy to fix (lintian -iIvE --pedantic *.changes) Cheers, Giuseppe. signature.asc Description: OpenPGP digital signature
Bug#584327: patch
Hi! Thanks. RDFLib 3.0.0 was recently released. Thus, before uploading a patched debian/rules, I'd like to test whether this issue is reproducible with the new version as well. I'm preparing a package, it would be great if you could test it on your mipsel virtual machine. Give me some time, you will have it in your inbox shortly. Yes, of course. Anyway, this is obviously a workaround and, as you pointed out before, we need to generate a minimal test case to report a bug against gcc. The problem is that it seems impossible to really make a short test case. The parser contains many if-blocks with the condition if(self-verbose). I removed them because self-verbose is always false in our case. The bug no longer occurred. Then I did a binary search on the number of blocks I can remove before the bug disappears. I now have two versions of the parser that only differ in two lines, but one exposing the problem, the other not. My guess is that there is some wrong overflow detection in gcc when relative addressing is used (that would explain why it only occurs on long functions). However, I need to further investigate this, and even if I can find the root of the problem, it will take some time that a fix is made and included in Debian's toolchain. WM -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: limit source to kdebase-workspace, tagging 584861
Processing commands for cont...@bugs.debian.org: #kdebase-workspace (4:4.4.4-2) UNRELEASED; urgency=low # # * Make kdebase-workspace-data replace conflict with ksplash #(Closes: #584861). # limit source kdebase-workspace Limiting to bugs with field 'source' containing at least one of 'kdebase-workspace' Limit currently set to 'source':'kdebase-workspace' tags 584861 + pending Bug #584861 [kdebase-workspace-data] kdebase-workspace-data: File conflict with ksplash (/usr/share/icons/hicolor/128x1128/apps/ksplash.png) Added tag(s) pending. thanks Stopping processing here. Please contact me if you need assistance. -- 584861: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=584861 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#584875: fails to install
Package: libcipux-cat-web-perl Version: 3.4.0.2-1 Severity: serious User: debian...@lists.debian.org Usertags: piuparts piuparts.d.o Hi, during a test with piuparts I noticed your package failed to install. From the attached log (scroll to the bottom...): Setting up libcipux-cat-web-perl (3.4.0.2-1) ... chmod: cannot access `/etc/cipux-cat-web/cipux-cat-web.conf': No such file or directory dpkg: error processing libcipux-cat-web-perl (--configure): subprocess installed post-installation script returned error exit status 1 Errors were encountered while processing: libcipux-cat-web-perl E: Sub-process /usr/bin/dpkg returned an error code (1) cheers, Holger Start: 2010-05-26 05:08:44 UTC Package: libcipux-cat-web-perl Priority: optional Section: perl Installed-Size: 588 Maintainer: CipUX team cipux-de...@lists.alioth.debian.org Architecture: all Source: cipux-cat-web Version: 3.4.0.2-1 Depends: perl, libcgi-formbuilder-perl, libcipux-perl, libdate-manip-perl, libcipux-rpc-client-perl, libtemplate-perl, libclass-std-perl, liblog-log4perl-perl, libreadonly-perl, libversion-perl Suggests: cipux-cat-web Filename: pool/main/c/cipux-cat-web/libcipux-cat-web-perl_3.4.0.2-1_all.deb Size: 91996 MD5sum: b5b3610e3809b84f8c02e6ee5e8bc50c SHA1: c2c964c39b8b3a665677ac2dd46451c488f62419 SHA256: 8534d1fe6ed4035916642b7c34bc588104eb35274e3c43559bddccec4e403038 Description: user and resource management framework CipUX - web-based admin tools CipUX is a modular framework for information abstraction and administration, primarily aimed at administration of users, groups and organisational resources stored in a central LDAP database. . CAT is CipUX Administration Tools, interacting with the core CipUX framework through XML-RPC. . Two CATs are provided officially with CipUX: - cipux-cat-web: generic web-based CAT - cipux-cat-moodle: CipUX plugin for Moodle These can be extended or replaced with custom tools. . This package contains CipUX::CAT::Web - functions used by the generic web-based CAT cipux-cat-web. Homepage: http://www.cipux.org/ Tag: qa::low-popcon Executing: sudo /org/piuparts.debian.org/sbin/piuparts --warn-symlinks --warn-on-others --warn-on-leftovers-after-purge --skip-logrotatefiles-test --scriptsdir /etc/piuparts/scripts/ --tmpdir /org/piuparts.debian.org/tmp -ad squeeze -b squeeze.tar.gz --mirror http://piatti.debian.org/debian/ libcipux-cat-web-perl Guessed: debian 0m0.0s INFO: -- 0m0.0s INFO: To quickly glance what went wrong, scroll down to the bottom of this logfile. 0m0.0s INFO: FAQ available at http://wiki.debian.org/piuparts/FAQ 0m0.0s INFO: -- 0m0.0s INFO: piuparts version 0.39~201005220948 starting up. 0m0.0s INFO: Command line arguments: /org/piuparts.debian.org/sbin/piuparts --warn-symlinks --warn-on-others --warn-on-leftovers-after-purge --skip-logrotatefiles-test --scriptsdir /etc/piuparts/scripts/ --tmpdir /org/piuparts.debian.org/tmp -ad squeeze -b squeeze.tar.gz --mirror http://piatti.debian.org/debian/ libcipux-cat-web-perl 0m0.0s INFO: Running on: Linux piatti 2.6.32.13-dsa-amd64 #1 SMP Fri May 14 10:29:18 CEST 2010 x86_64 0m0.0s DEBUG: Created temporary directory /org/piuparts.debian.org/tmp/tmpyAxfvn 0m0.0s DEBUG: Unpacking squeeze.tar.gz into /org/piuparts.debian.org/tmp/tmpyAxfvn 0m0.0s DEBUG: Starting command: ['tar', '-C', '/org/piuparts.debian.org/tmp/tmpyAxfvn', '-zxf', 'squeeze.tar.gz'] 0m1.8s DEBUG: Command ok: ['tar', '-C', '/org/piuparts.debian.org/tmp/tmpyAxfvn', '-zxf', 'squeeze.tar.gz'] 0m1.8s DEBUG: Created policy-rc.d and chmodded it. 0m1.8s DEBUG: Starting command: ['chroot', '/org/piuparts.debian.org/tmp/tmpyAxfvn', 'apt-get', 'update'] 0m3.7s DUMP: Get:1 http://piatti.debian.org squeeze Release.gpg [835B] Get:2 http://piatti.debian.org squeeze Release [89.5kB] Ign http://piatti.debian.org squeeze/main Packages/DiffIndex Ign http://piatti.debian.org squeeze/contrib Packages/DiffIndex Ign http://piatti.debian.org squeeze/non-free Packages/DiffIndex Get:3 http://piatti.debian.org squeeze/main Packages [8459kB] Get:4 http://piatti.debian.org squeeze/contrib Packages [61.6kB] Get:5 http://piatti.debian.org squeeze/non-free Packages [121kB] Fetched 8731kB in 1s (8580kB/s) Reading package lists... 0m3.7s DEBUG: Command ok: ['chroot', '/org/piuparts.debian.org/tmp/tmpyAxfvn', 'apt-get', 'update'] 0m3.7s DEBUG: Starting command: ['chroot', '/org/piuparts.debian.org/tmp/tmpyAxfvn', 'mount', '-t', 'proc', 'proc', '/proc'] 0m3.7s DEBUG: Command ok: ['chroot', '/org/piuparts.debian.org/tmp/tmpyAxfvn', 'mount', '-t', 'proc', 'proc', '/proc'] 0m3.7s DEBUG: Starting command: ['chroot', '/org/piuparts.debian.org/tmp/tmpyAxfvn', 'apt-get', '-yf', 'upgrade'] 0m10.9s DUMP: Reading package lists... Building dependency tree... The following packages will be upgraded:
Processed: tagging 584304
Processing commands for cont...@bugs.debian.org: tags 584304 pending Bug #584304 [src:gmic] gmic: FTBFS: error: 'vsnprintf' is not a member of 'std' Added tag(s) pending. thanks Stopping processing here. Please contact me if you need assistance. -- 584304: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=584304 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#583419: marked as done (dolfin: FTBFS: Nonexistent build-dependency: libpetsc3.0.0-dev)
Your message dated Mon, 07 Jun 2010 09:33:41 + with message-id e1olyid-0007gj...@ries.debian.org and subject line Bug#583419: fixed in dolfin 0.9.7-4 has caused the Debian Bug report #583419, regarding dolfin: FTBFS: Nonexistent build-dependency: libpetsc3.0.0-dev 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 this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 583419: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=583419 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Source: dolfin Version: 0.9.7-3 Severity: serious Tags: squeeze sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20100527 qa-ftbfs Justification: FTBFS on amd64 Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part: ** Using build dependencies supplied by package: Build-Depends: cdbs (= 0.4.49), debhelper (= 7), python-all-dev, python-central (= 0.5.6), scons, swig (= 1.3.35), python-numpy, pkg-config, libxml2-dev, libboost-dev, libboost-serialization-dev, libsuitesparse-dev, python-ufc (= 1.4.0-2), libptscotch-dev, libpetsc3.0.0-dev, libslepc3.0.0-dev, libboost-filesystem-dev, libboost-program-options-dev Build-Depends-Indep: texlive-latex-recommended, texlive-latex-extra, texlive-math-extra, ghostscript ┌──┐ │ Install build dependencies (internal resolver) │ └──┘ Checking for already installed source dependencies... cdbs: missing Using default version 0.4.84 debhelper: missing Using default version 7.4.20 python-all-dev: missing python-central: missing Using default version 0.6.16 scons: missing swig: missing Using default version 1.3.40-2 python-numpy: missing pkg-config: missing libxml2-dev: missing libboost-dev: missing libboost-serialization-dev: missing libsuitesparse-dev: missing python-ufc: missing Using default version 1.4.0-2 libptscotch-dev: missing libpetsc3.0.0-dev: missing libslepc3.0.0-dev: missing libboost-filesystem-dev: missing libboost-program-options-dev: missing texlive-latex-recommended: missing texlive-latex-extra: missing texlive-math-extra: missing ghostscript: missing Checking for source dependency conflicts... E: Package libpetsc3.0.0-dev has no installation candidate The full build log is available from: http://people.debian.org/~lucas/logs/2010/05/27/dolfin_0.9.7-3_lsid64.buildlog A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! About the archive rebuild: The rebuild was done on about 50 AMD64 nodes of the Grid'5000 platform, using a clean chroot. Internet was not accessible from the build systems. -- | Lucas Nussbaum | lu...@lucas-nussbaum.net http://www.lucas-nussbaum.net/ | | jabber: lu...@nussbaum.fr GPG: 1024D/023B3F4F | ---End Message--- ---BeginMessage--- Source: dolfin Source-Version: 0.9.7-4 We believe that the bug you reported is fixed in the latest version of dolfin, which is due to be installed in the Debian FTP archive: dolfin-bin_0.9.7-4_all.deb to main/d/dolfin/dolfin-bin_0.9.7-4_all.deb dolfin-dev_0.9.7-4_all.deb to main/d/dolfin/dolfin-dev_0.9.7-4_all.deb dolfin-doc_0.9.7-4_all.deb to main/d/dolfin/dolfin-doc_0.9.7-4_all.deb dolfin_0.9.7-4.diff.gz to main/d/dolfin/dolfin_0.9.7-4.diff.gz dolfin_0.9.7-4.dsc to main/d/dolfin/dolfin_0.9.7-4.dsc libdolfin0-dbg_0.9.7-4_amd64.deb to main/d/dolfin/libdolfin0-dbg_0.9.7-4_amd64.deb libdolfin0-dev_0.9.7-4_amd64.deb to main/d/dolfin/libdolfin0-dev_0.9.7-4_amd64.deb libdolfin0_0.9.7-4_amd64.deb to main/d/dolfin/libdolfin0_0.9.7-4_amd64.deb python-dolfin_0.9.7-4_amd64.deb to main/d/dolfin/python-dolfin_0.9.7-4_amd64.deb A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 583...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Johannes Ring joha...@simula.no (supplier of updated dolfin 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 ftpmas...@debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Mon, 07 Jun 2010 09:25:13 +0200 Source: dolfin Binary: libdolfin0-dev dolfin-dev libdolfin0 libdolfin0-dbg
Bug#584518: marked as done (CVE-2010-0403: Directory traversal vulnerability)
Your message dated Mon, 07 Jun 2010 09:37:38 + with message-id e1olym2-0008a6...@ries.debian.org and subject line Bug#584518: fixed in phpgroupware 1:0.9.16.016+dfsg-1 has caused the Debian Bug report #584518, regarding CVE-2010-0403: Directory traversal vulnerability 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 this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 584518: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=584518 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: phpgroupware Severity: serious Tags: security -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi, the following CVE (Common Vulnerabilities Exposures) id was published for phpgroupware. CVE-2010-0403[0]: | Directory traversal vulnerability in about.php in phpGroupWare (phpgw) | before 0.9.16.016 allows remote attackers to include and execute | arbitrary local files via a .. (dot dot) in the app parameter. If you fix the vulnerability please also make sure to include the CVE id in your changelog entry. For further information see: [0] http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2010-0403 http://security-tracker.debian.org/tracker/CVE-2010-0403 -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.10 (GNU/Linux) iEYEARECAAYFAkwIv0gACgkQNxpp46476aqCYQCglm6nA6T8hmgshCf/tS9ylgwt 7VgAn0e1/fwzFiM/FEgwSoF84y20/j4u =Z/92 -END PGP SIGNATURE- ---End Message--- ---BeginMessage--- Source: phpgroupware Source-Version: 1:0.9.16.016+dfsg-1 We believe that the bug you reported is fixed in the latest version of phpgroupware, which is due to be installed in the Debian FTP archive: phpgroupware-0.9.16-addressbook_0.9.16.016+dfsg-1_all.deb to main/p/phpgroupware/phpgroupware-0.9.16-addressbook_0.9.16.016+dfsg-1_all.deb phpgroupware-0.9.16-admin_0.9.16.016+dfsg-1_all.deb to main/p/phpgroupware/phpgroupware-0.9.16-admin_0.9.16.016+dfsg-1_all.deb phpgroupware-0.9.16-calendar_0.9.16.016+dfsg-1_all.deb to main/p/phpgroupware/phpgroupware-0.9.16-calendar_0.9.16.016+dfsg-1_all.deb phpgroupware-0.9.16-core-base_0.9.16.016+dfsg-1_all.deb to main/p/phpgroupware/phpgroupware-0.9.16-core-base_0.9.16.016+dfsg-1_all.deb phpgroupware-0.9.16-core_0.9.16.016+dfsg-1_all.deb to main/p/phpgroupware/phpgroupware-0.9.16-core_0.9.16.016+dfsg-1_all.deb phpgroupware-0.9.16-doc_0.9.16.016+dfsg-1_all.deb to main/p/phpgroupware/phpgroupware-0.9.16-doc_0.9.16.016+dfsg-1_all.deb phpgroupware-0.9.16-email_0.9.16.016+dfsg-1_all.deb to main/p/phpgroupware/phpgroupware-0.9.16-email_0.9.16.016+dfsg-1_all.deb phpgroupware-0.9.16-filemanager_0.9.16.016+dfsg-1_all.deb to main/p/phpgroupware/phpgroupware-0.9.16-filemanager_0.9.16.016+dfsg-1_all.deb phpgroupware-0.9.16-manual_0.9.16.016+dfsg-1_all.deb to main/p/phpgroupware/phpgroupware-0.9.16-manual_0.9.16.016+dfsg-1_all.deb phpgroupware-0.9.16-news-admin_0.9.16.016+dfsg-1_all.deb to main/p/phpgroupware/phpgroupware-0.9.16-news-admin_0.9.16.016+dfsg-1_all.deb phpgroupware-0.9.16-notes_0.9.16.016+dfsg-1_all.deb to main/p/phpgroupware/phpgroupware-0.9.16-notes_0.9.16.016+dfsg-1_all.deb phpgroupware-0.9.16-phpgwapi-doc_0.9.16.016+dfsg-1_all.deb to main/p/phpgroupware/phpgroupware-0.9.16-phpgwapi-doc_0.9.16.016+dfsg-1_all.deb phpgroupware-0.9.16-phpgwapi_0.9.16.016+dfsg-1_all.deb to main/p/phpgroupware/phpgroupware-0.9.16-phpgwapi_0.9.16.016+dfsg-1_all.deb phpgroupware-0.9.16-preferences_0.9.16.016+dfsg-1_all.deb to main/p/phpgroupware/phpgroupware-0.9.16-preferences_0.9.16.016+dfsg-1_all.deb phpgroupware-0.9.16-setup_0.9.16.016+dfsg-1_all.deb to main/p/phpgroupware/phpgroupware-0.9.16-setup_0.9.16.016+dfsg-1_all.deb phpgroupware-0.9.16-todo_0.9.16.016+dfsg-1_all.deb to main/p/phpgroupware/phpgroupware-0.9.16-todo_0.9.16.016+dfsg-1_all.deb phpgroupware-0.9.16_0.9.16.016+dfsg-1_all.deb to main/p/phpgroupware/phpgroupware-0.9.16_0.9.16.016+dfsg-1_all.deb phpgroupware_0.9.16.016+dfsg-1.diff.gz to main/p/phpgroupware/phpgroupware_0.9.16.016+dfsg-1.diff.gz phpgroupware_0.9.16.016+dfsg-1.dsc to main/p/phpgroupware/phpgroupware_0.9.16.016+dfsg-1.dsc phpgroupware_0.9.16.016+dfsg-1_all.deb to main/p/phpgroupware/phpgroupware_0.9.16.016+dfsg-1_all.deb phpgroupware_0.9.16.016+dfsg.orig.tar.gz to main/p/phpgroupware/phpgroupware_0.9.16.016+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 584...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Olivier Berger
Bug#584517: marked as done (CVE-2010-0404: Multiple SQL injection vulnerabilities)
Your message dated Mon, 07 Jun 2010 09:37:38 + with message-id e1olym2-0008a0...@ries.debian.org and subject line Bug#584517: fixed in phpgroupware 1:0.9.16.016+dfsg-1 has caused the Debian Bug report #584517, regarding CVE-2010-0404: Multiple SQL injection vulnerabilities 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 this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 584517: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=584517 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: phpgroupware Severity: grave Tags: security -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi, the following CVE (Common Vulnerabilities Exposures) id was published for phpgroupware. CVE-2010-0404[0]: | Multiple SQL injection vulnerabilities in phpGroupWare (phpgw) before | 0.9.16.016 allow remote attackers to execute arbitrary SQL commands | via unspecified parameters to (1) class.sessions_db.inc.php, (2) | class.translation_sql.inc.php, or (3) class.auth_sql.inc.php in | phpgwapi/inc/. If you fix the vulnerability please also make sure to include the CVE id in your changelog entry. For further information see: [0] http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2010-0404 http://security-tracker.debian.org/tracker/CVE-2010-0404 -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.10 (GNU/Linux) iEYEARECAAYFAkwIvrgACgkQNxpp46476aq41wCfQ0VPTXt9wJea3uxc8AyFqinN iJEAn23Iev9NwpsKs0mobx63GDSVoOKs =T2FI -END PGP SIGNATURE- ---End Message--- ---BeginMessage--- Source: phpgroupware Source-Version: 1:0.9.16.016+dfsg-1 We believe that the bug you reported is fixed in the latest version of phpgroupware, which is due to be installed in the Debian FTP archive: phpgroupware-0.9.16-addressbook_0.9.16.016+dfsg-1_all.deb to main/p/phpgroupware/phpgroupware-0.9.16-addressbook_0.9.16.016+dfsg-1_all.deb phpgroupware-0.9.16-admin_0.9.16.016+dfsg-1_all.deb to main/p/phpgroupware/phpgroupware-0.9.16-admin_0.9.16.016+dfsg-1_all.deb phpgroupware-0.9.16-calendar_0.9.16.016+dfsg-1_all.deb to main/p/phpgroupware/phpgroupware-0.9.16-calendar_0.9.16.016+dfsg-1_all.deb phpgroupware-0.9.16-core-base_0.9.16.016+dfsg-1_all.deb to main/p/phpgroupware/phpgroupware-0.9.16-core-base_0.9.16.016+dfsg-1_all.deb phpgroupware-0.9.16-core_0.9.16.016+dfsg-1_all.deb to main/p/phpgroupware/phpgroupware-0.9.16-core_0.9.16.016+dfsg-1_all.deb phpgroupware-0.9.16-doc_0.9.16.016+dfsg-1_all.deb to main/p/phpgroupware/phpgroupware-0.9.16-doc_0.9.16.016+dfsg-1_all.deb phpgroupware-0.9.16-email_0.9.16.016+dfsg-1_all.deb to main/p/phpgroupware/phpgroupware-0.9.16-email_0.9.16.016+dfsg-1_all.deb phpgroupware-0.9.16-filemanager_0.9.16.016+dfsg-1_all.deb to main/p/phpgroupware/phpgroupware-0.9.16-filemanager_0.9.16.016+dfsg-1_all.deb phpgroupware-0.9.16-manual_0.9.16.016+dfsg-1_all.deb to main/p/phpgroupware/phpgroupware-0.9.16-manual_0.9.16.016+dfsg-1_all.deb phpgroupware-0.9.16-news-admin_0.9.16.016+dfsg-1_all.deb to main/p/phpgroupware/phpgroupware-0.9.16-news-admin_0.9.16.016+dfsg-1_all.deb phpgroupware-0.9.16-notes_0.9.16.016+dfsg-1_all.deb to main/p/phpgroupware/phpgroupware-0.9.16-notes_0.9.16.016+dfsg-1_all.deb phpgroupware-0.9.16-phpgwapi-doc_0.9.16.016+dfsg-1_all.deb to main/p/phpgroupware/phpgroupware-0.9.16-phpgwapi-doc_0.9.16.016+dfsg-1_all.deb phpgroupware-0.9.16-phpgwapi_0.9.16.016+dfsg-1_all.deb to main/p/phpgroupware/phpgroupware-0.9.16-phpgwapi_0.9.16.016+dfsg-1_all.deb phpgroupware-0.9.16-preferences_0.9.16.016+dfsg-1_all.deb to main/p/phpgroupware/phpgroupware-0.9.16-preferences_0.9.16.016+dfsg-1_all.deb phpgroupware-0.9.16-setup_0.9.16.016+dfsg-1_all.deb to main/p/phpgroupware/phpgroupware-0.9.16-setup_0.9.16.016+dfsg-1_all.deb phpgroupware-0.9.16-todo_0.9.16.016+dfsg-1_all.deb to main/p/phpgroupware/phpgroupware-0.9.16-todo_0.9.16.016+dfsg-1_all.deb phpgroupware-0.9.16_0.9.16.016+dfsg-1_all.deb to main/p/phpgroupware/phpgroupware-0.9.16_0.9.16.016+dfsg-1_all.deb phpgroupware_0.9.16.016+dfsg-1.diff.gz to main/p/phpgroupware/phpgroupware_0.9.16.016+dfsg-1.diff.gz phpgroupware_0.9.16.016+dfsg-1.dsc to main/p/phpgroupware/phpgroupware_0.9.16.016+dfsg-1.dsc phpgroupware_0.9.16.016+dfsg-1_all.deb to main/p/phpgroupware/phpgroupware_0.9.16.016+dfsg-1_all.deb phpgroupware_0.9.16.016+dfsg.orig.tar.gz to main/p/phpgroupware/phpgroupware_0.9.16.016+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 584...@bugs.debian.org, and the maintainer will reopen the bug report
Bug#584792: marked as done (digikam-data: Incorrect Conflicts/Replaces versions)
Your message dated Mon, 07 Jun 2010 09:32:59 + with message-id e1olyhx-0006vn...@ries.debian.org and subject line Bug#584792: fixed in digikam 2:1.2.0-5 has caused the Debian Bug report #584792, regarding digikam-data: Incorrect Conflicts/Replaces versions 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 this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 584792: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=584792 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: digikam-data Version: 2:1.2.0-4 Severity: serious Justification: Policy 7.6 The versioned Conflicts/Replaces in digikam-data are missing the epoch. $ apt-cache show digikam-data | egrep '^(Package|Version|Conflicts|Replaces)' Package: digikam-data Version: 2:1.2.0-4 Conflicts: digikam (= 1.2.0-3) Replaces: digikam (= 1.2.0-3) -- System Information: Debian Release: squeeze/sid APT prefers unstable APT policy: (500, 'unstable'), (100, 'experimental') Architecture: i386 (i686) Kernel: Linux 2.6.32-5-686 (SMP w/2 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash ---End Message--- ---BeginMessage--- Source: digikam Source-Version: 2:1.2.0-5 We believe that the bug you reported is fixed in the latest version of digikam, which is due to be installed in the Debian FTP archive: digikam-data_1.2.0-5_all.deb to main/d/digikam/digikam-data_1.2.0-5_all.deb digikam-dbg_1.2.0-5_amd64.deb to main/d/digikam/digikam-dbg_1.2.0-5_amd64.deb digikam_1.2.0-5.debian.tar.gz to main/d/digikam/digikam_1.2.0-5.debian.tar.gz digikam_1.2.0-5.dsc to main/d/digikam/digikam_1.2.0-5.dsc digikam_1.2.0-5_amd64.deb to main/d/digikam/digikam_1.2.0-5_amd64.deb showfoto_1.2.0-5_amd64.deb to main/d/digikam/showfoto_1.2.0-5_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 584...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Mark Purcell m...@debian.org (supplier of updated digikam 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 ftpmas...@debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Mon, 07 Jun 2010 08:04:43 +1000 Source: digikam Binary: digikam showfoto digikam-dbg digikam-data Architecture: source amd64 all Version: 2:1.2.0-5 Distribution: unstable Urgency: low Maintainer: Debian KDE Extras Team pkg-kde-ext...@lists.alioth.debian.org Changed-By: Mark Purcell m...@debian.org Description: digikam- digital photo management application for KDE digikam-data - digikam architecture-independant data digikam-dbg - debugging symbols for digikam showfoto - image viewer/editor for KDE Closes: 584792 Changes: digikam (2:1.2.0-5) unstable; urgency=low . * Added epoc: Fix Incorrect Conflicts/Replaces versions (Closes: #584792) Checksums-Sha1: b7ffa59d5ce834d052c477fe7cdddabd8c80891c 1672 digikam_1.2.0-5.dsc 540b38d39183d0d33d716a4f6843896433d07b7b 33463 digikam_1.2.0-5.debian.tar.gz 891fb8d71eb0319f26728e7197e2a5a42313 5492552 digikam_1.2.0-5_amd64.deb d84c32dfd26a98dd5805fea3ab73bd2c4d6bbacf 1333126 showfoto_1.2.0-5_amd64.deb c671ff6048f701e54a5c7452182646a1e549bab6 38682654 digikam-dbg_1.2.0-5_amd64.deb 9dbf41b8a324c9a615eed3e90b1a0b0baf9c4e83 7351394 digikam-data_1.2.0-5_all.deb Checksums-Sha256: c20ed1e61f1aa2043f98077c049c276051273f178ed3890e45db38f2613d3845 1672 digikam_1.2.0-5.dsc 074e36f3dd6208a855f331129a1149a25ba2072bf9ab5ecdded08b79c982d6d1 33463 digikam_1.2.0-5.debian.tar.gz d0a239d25fa7bce45c7ed7b7c96a2ff6194c88e79a5700ba9951fedca199533f 5492552 digikam_1.2.0-5_amd64.deb 0d3820a24354c3c03fb2290061a8b27f9481fa1cb3ae73081b0973e95a7a0d44 1333126 showfoto_1.2.0-5_amd64.deb 6d06f9b30c59a7a4473a8ecb8bee64349bd6770a4d87e8d5693d059944a3dc54 38682654 digikam-dbg_1.2.0-5_amd64.deb 2d24cf709cd76ed9f31ecdac3b68a873b42d745e32c630353a24c4c447c476e6 7351394 digikam-data_1.2.0-5_all.deb Files: b3c8a48e10a7465b3e5a95d2d71fbccc 1672 graphics optional digikam_1.2.0-5.dsc d362e18ee1307b31fd6dc578f250b5cb 33463 graphics optional digikam_1.2.0-5.debian.tar.gz 08a7ec3d7867dbd5000e7c6e7f42d517 5492552 graphics optional digikam_1.2.0-5_amd64.deb d97d0d11291f9e588554aa545b9b5864 1333126 graphics optional showfoto_1.2.0-5_amd64.deb b7952c11efd435ddee4caaef7ece9509 38682654 debug extra digikam-dbg_1.2.0-5_amd64.deb
Bug#584879: enscript: File conflict with octave3.0 (/usr/share/enscript/hl/octave.st)
Package: enscript Version: 1.6.5.1-1 Severity: serious User: debian-...@lists.debian.org UserTags: debian-edu When trying to upgrade a KDE desktop from Lenny to Squeeze, the upgrade fail because enscript refuses to install because octave3 version 1:3.0.1-6lenny3 is already installed and they share the file /usr/share/enscript/hl/octave.st. I guess some kind of breaks/conflicts/replaces should be used here to ensure upgrades go smooth. Setting severity to serious, as this issue breaks upgrades and policy state that packages providing the same file need to conflict with each other. Happy hacking, -- Petter Reinholdtsen -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#431209: marked as done (uninstallable in sid)
Your message dated Mon, 7 Jun 2010 11:53:32 +0200 with message-id 201006071153.33264.deb...@abeckmann.de and subject line Re: uninstallable in sid has caused the Debian Bug report #431209, regarding uninstallable in sid 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 this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 431209: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=431209 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: nvidia-kernel-legacy-2.6.18-4-amd64 Version: 1.0.7184+6 Severity: grave This package is uninstallable in sid, but this is just sent as a reminder that this package is now useless in lenny/sid and its maintainance team should request its removal to the archive maintainance team. ---End Message--- ---BeginMessage--- On Saturday, 30. June 2007 19:42:42 Filipus Klutiero wrote: Package: nvidia-kernel-legacy-2.6.18-4-amd64 Package: nvidia-kernel-legacy-2.6.18-4-486 Version: 1.0.7184+6 Severity: grave This package is uninstallable in sid, but this is just sent as a reminder that this package is now useless in lenny/sid and its maintainance team should request its removal to the archive maintainance team. After a long long time, the packages nvidia-graphics-legacy-modules-amd64 nvidia-graphics-legacy-modules-i386 have been finally removed from sid. See for the removal requests: http://bugs.debian.org/584838 http://bugs.debian.org/584839 Andreas ---End Message---
Bug#431210: marked as done (uninstallable in sid)
Your message dated Mon, 7 Jun 2010 11:53:32 +0200 with message-id 201006071153.33264.deb...@abeckmann.de and subject line Re: uninstallable in sid has caused the Debian Bug report #431210, regarding uninstallable in sid 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 this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 431210: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=431210 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: nvidia-kernel-legacy-2.6.18-4-486 Version: 1.0.7184+6 Severity: grave This package is uninstallable in sid, but this is just sent as a reminder that this source package is now useless in lenny/sid and its maintainance team should request its removal to the archive maintainance team. ---End Message--- ---BeginMessage--- On Saturday, 30. June 2007 19:42:42 Filipus Klutiero wrote: Package: nvidia-kernel-legacy-2.6.18-4-amd64 Package: nvidia-kernel-legacy-2.6.18-4-486 Version: 1.0.7184+6 Severity: grave This package is uninstallable in sid, but this is just sent as a reminder that this package is now useless in lenny/sid and its maintainance team should request its removal to the archive maintainance team. After a long long time, the packages nvidia-graphics-legacy-modules-amd64 nvidia-graphics-legacy-modules-i386 have been finally removed from sid. See for the removal requests: http://bugs.debian.org/584838 http://bugs.debian.org/584839 Andreas ---End Message---
Bug#496078: marked as done (nvidia-kernel-legacy-2.6.18-4-686: Depends on linux-image-2.6.18-4-686 but is not available)
Your message dated Mon, 7 Jun 2010 11:53:32 +0200 with message-id 201006071153.33264.deb...@abeckmann.de and subject line Re: uninstallable in sid has caused the Debian Bug report #496078, regarding nvidia-kernel-legacy-2.6.18-4-686: Depends on linux-image-2.6.18-4-686 but is not available 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 this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 496078: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=496078 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: nvidia-kernel-legacy-2.6-686 Version: 1.0.7184+6 Severity: grave Justification: renders package unusable The package depends on linux-image-2.6.18-4-686 which is unavailable in unstable. -- System Information: Debian Release: lenny/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing') Architecture: i386 (i686) Kernel: Linux 2.6.26-1-686 (SMP w/1 CPU core) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash ---End Message--- ---BeginMessage--- On Saturday, 30. June 2007 19:42:42 Filipus Klutiero wrote: Package: nvidia-kernel-legacy-2.6.18-4-amd64 Package: nvidia-kernel-legacy-2.6.18-4-486 Version: 1.0.7184+6 Severity: grave This package is uninstallable in sid, but this is just sent as a reminder that this package is now useless in lenny/sid and its maintainance team should request its removal to the archive maintainance team. After a long long time, the packages nvidia-graphics-legacy-modules-amd64 nvidia-graphics-legacy-modules-i386 have been finally removed from sid. See for the removal requests: http://bugs.debian.org/584838 http://bugs.debian.org/584839 Andreas ---End Message---
Bug#584748: ../sysdeps/x86_64/cacheinfo.c:255: handle_intel: Assertion `maxidx = 2' on AMD cpu
On Mon, Jun 07, 2010 at 08:47:23AM +0200, Aurelien Jarno wrote: Aurelien Jarno a écrit : On Sun, Jun 06, 2010 at 10:27:12PM +0200, Gianluigi Tiesi wrote: On 06/06/2010 14.55, Aurelien Jarno wrote: On Sun, Jun 06, 2010 at 02:17:29PM +0200, Gianluigi Tiesi wrote: On 06/06/2010 13.21, Aurelien Jarno wrote: Kernel: Linux 2.6.26-2-xen-amd64 (SMP w/8 CPU cores) This part is not consistent. Are you running reportbug on a different machine? yes the problem is on a old amd 800mhz box, but I use a different box for submitting do you need some additional infos about the amd installation? Yes, which libc6 packages are actually installed? I have fixed a bug that my cause the problem you are observing in version 2.11.1-2, so if you are running version 2.11.1-1, please try to upgrade. Also which kernel are you running? libc is 2.11.1-2 kernel: Linux attila 2.6.32-5-686 #1 SMP Tue Jun 1 04:59:47 UTC 2010 i686 GNU/Linux I known the problem with libc6-i686 and intel i7 I've reported some info too :) It's not the problem with core i7, but a different one that has also been corrected. One that breaks reading model and family in some conditions. this look different Unfortunately I am not able to reproduce it. Tried on an Athlon and on Opteron CPU. For your information, I have been able to find a machine with a CPU identical to yours, and I am now able to reproduce the issue. I'll debug it later today. Ok, here we go, it's a bit tricky. First of all, newer versions of the glibc tries to optimise the string function by using cache information, which are stored in cpuid level 2 and later on an Intel CPU. Secondly, valgrind does not use the real CPU, but always emulates an Intel one, trying to match the characteristics of the host CPU, especially in term of instruction set. When the CPU has no SSE support it emulates an old Pentium CPU, which have a max a cpuid level of 1. This is what happens when the host CPU is an Athlon one. The Pentium CPU is an i586 CPU, which does not support the CMOV instruction, so the libc from the libc6 package is used. On the other hand, the Athlon CPU is an i686 CPU, which does support the CMOV instruction, so the libc from libc6-i686 is used. Everything works well as long as you don't use valgrind. When you use it, it loads all the libraries using the host CPUID, that is it loads the libc from libc6-i686. It latter emulates a Pentium CPU, which has a cpuid level of 1 only. The glibc code recognizes an Intel CPU (as valgrind emulates it), and given it is the i686 version of the libc, it assumes it is at minimum a Pentium Pro (which is the first i686 Intel CPU), which means it assumes that the cpuid level is at 2. This is where all the cache information is stored. The bug really seems to be on the valgrind side, which should not load an i686 library while emulating an i586 CPU. OTOH, if it is difficult to fix, we can maybe remove assumptions that are correct, but wrong when using valgrind. -- Aurelien Jarno GPG: 1024D/F1BCDB73 aurel...@aurel32.net http://www.aurel32.net -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#584698: patch welcome
Hello, You can improve php-elisp package via collab-maint : http://svn.debian.org/wsvn/collab-maint/ext-maint/php-elisp/ I think that it's better if you co-maintain this package with me. You're welcome! Regards, signature.asc Description: OpenPGP digital signature
Bug#584327: patch
On Mon, Jun 7, 2010 at 10:34 AM, Willi Mann wi...@wm1.at wrote: Hi! Thanks. RDFLib 3.0.0 was recently released. Thus, before uploading a patched debian/rules, I'd like to test whether this issue is reproducible with the new version as well. I'm preparing a package, it would be great if you could test it on your mipsel virtual machine. Give me some time, you will have it in your inbox shortly. Yes, of course. The package is almost ready but we're in serious trouble now. RDFLib 3.0.0 does not ship C extensions so this bug is not reproducible any longer. BUT we have a bigger problem now: support for graph querying using SPARQL has been dropped. This means that your test case won't work and, even worse, that enigmail installation (and maybe others) will fail now on every architecture (*sigh*). http://paste.debian.net/76438/ Look at this: http://code.google.com/p/rdflib/wiki/IntroSparql In short, Rdfextras must be packaged for Debian if you want RDFLib to dispatch SPARQL queries. Any volunteers? Nacho -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: limit source to kazehakase, tagging 584722
Processing commands for cont...@bugs.debian.org: #kazehakase (0.5.8-4) unstable; urgency=high # # * debian/patches/30_xulrunner-1.9.1.dpatch: Remove -Werror from CPPFLAGS #in macros/gecko.m4. Autoconf has never ever supported -Werror so #using it in configure tests is doomed to fail at some point; in this #case it leads to miscompilation and failure to load gecko.so at #runtime due to unresolved symbols. (Closes: #584722). # limit source kazehakase Limiting to bugs with field 'source' containing at least one of 'kazehakase' Limit currently set to 'source':'kazehakase' tags 584722 + pending Bug #584722 [kazehakase] Kazehakase no longer displays pages in Squeeze Added tag(s) pending. thanks Stopping processing here. Please contact me if you need assistance. -- 584722: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=584722 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#584610: [mips] gcc-4.4 build failure after upgrade to eGLIBC-2.11
On Mon, Jun 07, 2010 at 09:15:05AM +0200, Matthias Klose wrote: On 06.06.2010 00:51, Aurelien Jarno wrote: These functions were present before in the library, but not exported in the headers. This has been changed as it is required by ISO C99. While these functions are strictly not needed in libstdc++6 anymore, we have two options: - revert the GLIBC change, which means we break the C99 compatibility (as before) - patch GCC to export these functions anyway. What's your opinion? For ARM I did choose the second option, but didn't get any feedback about it. So maybe it's time to ask the mips and arm porters? The patch applied for armel is: http://svn.debian.org/viewsvn/gcccvs/branches/sid/gcc-4.4/debian/patches/libstdc%2B%2B-arm-ldbl-compat.diff?view=log I'm fine with this fix. Riku -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#584610: [mips] gcc-4.4 build failure after upgrade to eGLIBC-2.11
Matthias Klose a écrit : On 06.06.2010 00:51, Aurelien Jarno wrote: On Sat, Jun 05, 2010 at 03:50:51AM +0200, Matthias Klose wrote: Package: eGLIBC Version: 2.11.1-2 Severity: serious gcc-4.4 and gcc-4.5 fail to build after the upgrade to eGLIBC-2.11: https://buildd.debian.org/fetch.cgi?pkg=gcc-4.4;ver=4.4.4-4;arch=mips;stamp=1275677666 This FTBFS is caused by the following change: |2009-11-20 Jakub Jelinekja...@redhat.com | |PR libc/10103 | |* math/math.h: Provide *l long double prototypes redirecting |to double functions even when __NO_LONG_DOUBLE_MATH and not |__LDBL_COMPAT. |* math/complex.h: Likewise. These functions were present before in the library, but not exported in the headers. This has been changed as it is required by ISO C99. GCC tries to find these functions in the GLIBC by compiling a program, so it was failing before, and is successful now. When they are already present in the GLIBC it does not re-export them. Strangely this should also affect ARM, but it seems to build correctly. I haven't investigated why. While these functions are strictly not needed in libstdc++6 anymore, we have two options: - revert the GLIBC change, which means we break the C99 compatibility (as before) - patch GCC to export these functions anyway. What's your opinion? For ARM I did choose the second option, but didn't get any feedback about it. So maybe it's time to ask the mips and arm porters? The patch applied for armel is: http://svn.debian.org/viewsvn/gcccvs/branches/sid/gcc-4.4/debian/patches/libstdc%2B%2B-arm-ldbl-compat.diff?view=log I think we should go for the same patch on mips, it's probably better to be ISO C99 compliant on the glibc side. -- Aurelien Jarno GPG: 1024D/F1BCDB73 aurel...@aurel32.net http://www.aurel32.net -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#559893: marked as done (monotone-server: hooks.lua.base is outdated)
Your message dated Mon, 07 Jun 2010 13:37:23 +0100 with message-id 4c0ce803.8050...@unchartedbackwaters.co.uk and subject line monotone-server: hooks.lua.base is outdated has caused the Debian Bug report #559893, regarding monotone-server: hooks.lua.base is outdated 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 this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 559893: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=559893 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: monotone-server Version: 0.45-2 Severity: grave Justification: renders package unusable With version 0.45, monotone has a new way to handle keys, which also affects some of the hooks, for example get_passphrase which is used in /usr/share/monotone/hooks.lua.base (or /etc/monotone/hooks.lua) ... Unfortunately, hooks.lua.base hasn't been updated accordingly, with the result that /etc/init.d/monotone will not be able to start mtn, thereby making this package unusable to all except those that are willing and knowlegable enough to hack hooks.lua.base or /etc/monotone/hooks.lua. Cheers, Richard -- System Information: Debian Release: squeeze/sid APT prefers testing APT policy: (500, 'testing') Architecture: i386 (i686) Kernel: Linux 2.6.30-2-686 (SMP w/2 CPU cores) Locale: LANG=sv_SE.utf8, LC_CTYPE=sv_SE.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages monotone-server depends on: ii adduser 3.111 add and remove users and groups ii debconf [debconf-2.0] 1.5.28 Debian configuration management sy ii lsb-base 3.2-23 Linux Standard Base 3.2 init scrip ii monotone 0.45-2 A distributed version (revision) c ii ucf 3.0025 Update Configuration File: preserv monotone-server recommends no packages. monotone-server suggests no packages. -- debconf information: monotone-server/manage-db: true monotone-server/key: monot...@guardian.lp.se ---End Message--- ---BeginMessage--- Version: 0.47-1 Upstream updated contrib/get_passphrase_from_file.lua with a fixed version. /usr/share/monotone/hooks.lua.base is copied from this and /etc/monotone/hooks.lua if updated from that via ucf. ---End Message---
Bug#584698: patch welcome
Thierry Randrianiriana thie...@debian.org wrote: Hello, You can improve php-elisp package via collab-maint : http://svn.debian.org/wsvn/collab-maint/ext-maint/php-elisp/ I think that it's better if you co-maintain this package with me. You're welcome! Thanks for the invitation Thierry. I don't use PHP so I'm not really sure that I want to go that far. But maybe... I have used CVS for years, tried to use svn once for proj co-maintenance and failed to understand it, but have since been using git (for gri and gri-mode.el) and bzr (for MH-E in the central Emacs repo). Maybe I missed something the first time around (like the concept of pushing changes back). But I recall it kept all revision separate in subdirectories. How would I (1) checkout php-elisp, (2) edit a change, (3) possibly add a subdirectory for patches, (4) commit and push it back, and (5) build a package? (1) From http://svn.debian.org I deduced the checkout as: $ svn checkout svn://svn.debian.org/collab-maint/ext-maint/php-elisp But that gives me only the debian directory. Where do you keep the upstream file? Or do you build that separately and just copy your debian directory to this repo? (2) I guess I would just edit a file now, there's no `svn edit' command. (3) adding a file or a directory is simply with svn add file, right? (4) does svn commit push changes back to the repo? Or is it local? (5) are you using package building tools specific to svn? Peter -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#584272: Acknowledgement (Can't start pidgin: bad flagvector, (Pidgin:4135): Json-CRITICAL, jack server is not running)
Hi, I was purged pidgin-facebookchat and everything about pidgin. After that I installed only pidgin. Still can't to start it; actually, it is running, but no GUI of Pidgin appeares. In the htop I can see these items: 2794 csanyipa 20 0 1748 156 152 S 0.0 0.3 0:00.00 /bin/sh -c /usr/bin/pidgin and 2795 csanyipa 20 0 46832 4424 1576 S 0.0 7.3 0:08.59 /usr/bin/pidgin My system is an old PC Box on which have running Debian GNU/Linux Squeeze with kernel linux-image-2.6.32-3-486. It's slow but the first time when I run successfully Pidgin on it I can use it. -- Regards, Paul Chany You can freely correct my English. http://csanyi-pal.info -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#583702: beneath-a-steel-sky: package ships data that cannot be modified
The idea to place it in _contrib_ (not in 'non-free') makes sense to me. Placing it in 'main' encourages DDs to add more non-modifiable data there. If the tools to modify were lost, then users are locked anyway. Similarly we wouldn't place executable binaries in 'main' if people had lost the corresponding source code. I think non-modifiable .ogg files are a problem. Sometimes they are the most usable form (e.g. a live recording), sometimes not (e.g. an .ogg output of a RoseGarden project), sometimes partially (when manual/non-automated post-processing was involved). What archive to use for them is probably another debate. -- Sylvain -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#584304: marked as done (gmic: FTBFS: error: 'vsnprintf' is not a member of 'std')
Your message dated Mon, 07 Jun 2010 13:17:19 +
with message-id e1olccd-000760...@ries.debian.org
and subject line Bug#584304: fixed in gmic 1.3.5.4+dfsg-1
has caused the Debian Bug report #584304,
regarding gmic: FTBFS: error: 'vsnprintf' is not a member of 'std'
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 this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
584304: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=584304
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
---BeginMessage---
Source: gmic
Version: 1.3.5.1+dfsg2-1
Severity: serious
Tags: patch
Hi,
gmic FTBFS on armel, mips, mipsel and sh4.
https://buildd.debian.org/pkg.cgi?pkg=gmic
-
g++ -o gmic_bool.o -c gmic.cpp -Dgmic_separate_compilation -Dgmic_bool
-g -O0 -I. -I/usr/include/libavcodec/ -I/usr/include/libavformat/
-I/usr/include/libswscale/ -Dgmic_build -I/usr/include -Wall -W
-I/usr/include -Dcimg_display=1 -Dcimg_use_xrandr -I/usr/X11R6/include
-Dcimg_use_xshm -Dcimg_use_png -Dcimg_use_jpeg -Dcimg_use_tiff
-Dcimg_use_zlib -Dcimg_use_magick -I/usr/include/GraphicsMagick
-Dcimg_use_openexr -I/usr/include/OpenEXR -Dcimg_use_fftw3
-Dcimg_use_ffmpeg -I/usr/include/libavcodec -I/usr/include/libavformat
-I/usr/include/libswscale -I/usr/include/ffmpeg -fno-tree-pre
In file included from gmic.h:67,
from gmic.cpp:438:
./CImg.h: In constructor
'cimg_library::CImgException::CImgException(const char*, ...)':
./CImg.h:2049: error: 'vsnprintf' is not a member of 'std'
./CImg.h: In constructor
'cimg_library::CImgInstanceException::CImgInstanceException(const
char*, ...)':
./CImg.h:2056: error: 'vsnprintf' is not a member of 'std'
./CImg.h: In constructor
'cimg_library::CImgArgumentException::CImgArgumentException(const
char*, ...)':
./CImg.h:2062: error: 'vsnprintf' is not a member of 'std'
-
I made patch to fix this problem. Could you apply this patch?
Best regards,
Nobuhiro
--
Nobuhiro Iwamatsu
iwamatsu at {nigauri.org / debian.org}
GPG ID: 40AD1FA6
std.diff
Description: application/octetstream
---End Message---
---BeginMessage---
Source: gmic
Source-Version: 1.3.5.4+dfsg-1
We believe that the bug you reported is fixed in the latest version of
gmic, which is due to be installed in the Debian FTP archive:
gimp-gmic_1.3.5.4+dfsg-1_amd64.deb
to main/g/gmic/gimp-gmic_1.3.5.4+dfsg-1_amd64.deb
gmic_1.3.5.4+dfsg-1.debian.tar.gz
to main/g/gmic/gmic_1.3.5.4+dfsg-1.debian.tar.gz
gmic_1.3.5.4+dfsg-1.dsc
to main/g/gmic/gmic_1.3.5.4+dfsg-1.dsc
gmic_1.3.5.4+dfsg-1_amd64.deb
to main/g/gmic/gmic_1.3.5.4+dfsg-1_amd64.deb
gmic_1.3.5.4+dfsg.orig.tar.gz
to main/g/gmic/gmic_1.3.5.4+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 584...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Bernd Zeimetz b...@debian.org (supplier of updated gmic 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 ftpmas...@debian.org)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Format: 1.8
Date: Mon, 07 Jun 2010 13:53:22 +0200
Source: gmic
Binary: gmic gimp-gmic
Architecture: source amd64
Version: 1.3.5.4+dfsg-1
Distribution: unstable
Urgency: low
Maintainer: Bernd Zeimetz b...@debian.org
Changed-By: Bernd Zeimetz b...@debian.org
Description:
gimp-gmic - GIMP plugin for GREYC's Magic Image Converter
gmic - GREYC's Magic Image Converter
Closes: 584304
Changes:
gmic (1.3.5.4+dfsg-1) unstable; urgency=low
.
* [821186d5] Fix dversionmangle in watch file.
* [8fab3d8a] Merge commit 'upstream/1.3.5.4+dfsg'
- This icludes a fix for the FTBFS on various archicetures.
(Closes: #584304)
* [7550bc35] Refresh patches.
* [d682b862] Don't gunzip manpages and create directories before make
install.
* [6dccd71b] Tidy debian/rules' clean target.
* [dba56977] Install bash completion
Checksums-Sha1:
8bb62ed0e180b3e5605d77000a386a8e4f5a6384 1374 gmic_1.3.5.4+dfsg-1.dsc
55d3431e653082be163acc6265f8f46b101bbefa 1021756 gmic_1.3.5.4+dfsg.orig.tar.gz
fe822b27f300b037ff7e2ed67940d876d0baac02 12442
gmic_1.3.5.4+dfsg-1.debian.tar.gz
d4bfda26229f4765603ad5881a19a50760c0f916 4209492 gmic_1.3.5.4+dfsg-1_amd64.deb
b1aaa475e0a23669addd88f6f5eda6350e79d82d 897118
gimp-gmic_1.3.5.4+dfsg-1_amd64.deb
Checksums-Sha256:
5102d91661acc1d76d349a937e2848e99a4afe18f497d97315d56a0a17332b34 1374
gmic_1.3.5.4+dfsg-1.dsc
Bug#584858: [Pkg-octave-devel] Bug#584858: qtoctave: package upgrade collides with quicktime-utils
On 7 June 2010 03:21, Mario 'BitKoenig' Holbe mario.ho...@tu-ilmenau.de wrote: qtoctave upgrade to 0.9.1-1 fails due to a file-conflict with quicktime-utils: We are working with upstream to resolve this issue. QtOctave's private binaries should be moved to /usr/lib/qtoctave per FHS policy. An upload is forthcoming. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#584327: patch
Hi! I'm CCing the maintainers of mozilla-devscripts, as they should decide how to proceed. Am 2010-06-07 13:00, schrieb Nacho Barrientos Arias: On Mon, Jun 7, 2010 at 10:34 AM, Willi Mann wi...@wm1.at wrote: Thanks. RDFLib 3.0.0 was recently released. Thus, before uploading a patched debian/rules, I'd like to test whether this issue is reproducible with the new version as well. I'm preparing a package, it would be great if you could test it on your mipsel virtual machine. Give me some time, you will have it in your inbox shortly. Yes, of course. The package is almost ready but we're in serious trouble now. RDFLib 3.0.0 does not ship C extensions so this bug is not reproducible any longer. BUT we have a bigger problem now: support for graph querying using SPARQL has been dropped. This means that your test case won't work and, even worse, that enigmail installation (and maybe others) will fail now on every architecture (*sigh*). Applies to all packages using /usr/bin/install-xpi, an that's quite a lot. http://paste.debian.net/76438/ Look at this: http://code.google.com/p/rdflib/wiki/IntroSparql In short, Rdfextras must be packaged for Debian if you want RDFLib to dispatch SPARQL queries. Any volunteers? How many users rely on the extension? In case the number is low, it's probably better to work around the problem. mozilla-devscripts maintainers, would it be possible to use python-librdf instead of python-rdflib to do the queries on install.rdf? WM -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#584910: libgtk2-sexy-perl: Should this package be removed?
Package: libgtk2-sexy-perl Severity: serious Hi, the package libgtk2-sexy-perl provides an interface to the (somewhat deprecated) libsexy library. Since this package has no reverse dependencies, I want to know whether it is OK to remove this package; since I see no sense in shipping deprecated API in Squeeze. If you agree that the package shall be removed, please reassign this bug to ftp.debian.org and retitle it as stated at http://ftp-master.debian.org/removals.html, and set the priority to normal. Regards, Julian -- System Information: Debian Release: lenny/sid APT prefers unstable APT policy: (990, 'unstable'), (350, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 2.6.32-5-amd64 (SMP w/2 CPU cores) Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages libgtk2-sexy-perl depends on: ii libatk1.0-0 1.30.0-1 The ATK accessibility toolkit ii libc6 2.11.1-2 Embedded GNU C Library: Shared lib ii libcairo2 1.8.10-4 The Cairo 2D vector graphics libra ii libfontconfig1 2.8.0-2.1generic font configuration library ii libfreetype62.3.11-1 FreeType 2 font engine, shared lib ii libglib2.0-02.24.1-1 The GLib library of C routines ii libgtk2-perl1:1.221-6Perl interface to the 2.x series o ii libgtk2.0-0 2.20.1-1 The GTK+ graphical user interface ii libpango1.0-0 1.28.0-1 Layout and rendering of internatio ii libsexy20.1.11-2+b1 collection of additional GTK+ widg ii libx11-62:1.3.3-3X11 client-side library ii libxcursor1 1:1.1.10-2 X cursor management library ii libxext62:1.1.1-3X11 miscellaneous extension librar ii libxfixes3 1:4.0.4-2X11 miscellaneous 'fixes' extensio ii libxi6 2:1.3-4 X11 Input extension library ii libxinerama12:1.1-3 X11 Xinerama extension library ii libxml2 2.7.7.dfsg-2 GNOME XML library ii libxrandr2 2:1.3.0-3X11 RandR extension library ii libxrender1 1:0.9.5-2X Rendering Extension client libra ii perl5.10.1-13Larry Wall's Practical Extraction ii perl-base [perlapi-5.10 5.10.1-13minimal Perl system ii zlib1g 1:1.2.3.4.dfsg-3 compression library - runtime libgtk2-sexy-perl recommends no packages. libgtk2-sexy-perl suggests no packages. -- Julian Andres Klode - Debian Developer, Ubuntu Member See http://wiki.debian.org/JulianAndresKlode and http://jak-linux.org/. pgpp61p5BpiEb.pgp Description: PGP signature
Bug#584911: bind9: hard-coded dependency on /usr/lib/ssl/openssl.cnf might cause trouble
Package: bind9
Version: 1:9.6.ESV.R1+dfsg-0+lenny1
Severity: serious
(This also seems to affect newer versions of bind9; also tested with
1:9.7.0.dfsg.P1-1~bpo50+1 from backports.)
I had to invest quite some time today in figuring out why the recent security
update for bind9 worked fine on all our systems running lenny, but failed on
the primary DNS server. Unfortunately, the syslog output gives no clue as to
why bind9 fails to start:
07-Jun-2010 15:06:22.132 starting BIND 9.6-ESV-R1 -c /etc/bind/named.conf -g -u
bind
07-Jun-2010 15:06:22.132 built with '--prefix=/usr' '--build=x86_64-linux-gnu'
'--host=x86_64-linux-gnu' '--mandir=/usr/share/man' '--infodir=/usr/share/info'
'--sysconfdir=/etc/bind' '--localstatedir=/var/run/bind' '--enable-threads'
'--enable-largefile' '--with-libtool' '--enable-shared' '--enable-static'
'--with-openssl=/usr' '--with-gssapi=/usr' '--with-gnu-ld'
'--with-dlz-postgres=no' '--with-dlz-mysql=no' '--with-dlz-bdb=yes'
'--with-dlz-filesystem=yes' '--with-dlz-ldap=yes' '--with-dlz-stub=yes'
'--enable-ipv6' 'build_alias=x86_64-linux-gnu' 'host_alias=x86_64-linux-gnu'
'CFLAGS=-fno-strict-aliasing -DDIG_SIGCHASE -O2' 'LDFLAGS=' 'CPPFLAGS='
'CXXFLAGS=-g -O2' 'FFLAGS=-g -O2'
07-Jun-2010 15:06:22.132 adjusted limit on open files from 1024 to 1048576
07-Jun-2010 15:06:22.132 found 4 CPUs, using 4 worker threads
07-Jun-2010 15:06:22.132 using up to 4096 sockets
Running bind9 manually nets the missing information:
# named -c /etc/bind/named.conf -g -u bind
07-Jun-2010 15:06:22.132 starting BIND 9.6-ESV-R1 -c /etc/bind/named.conf -g -u
bind
07-Jun-2010 15:06:22.132 built with '--prefix=/usr' '--build=x86_64-linux-gnu'
'--host=x86_64-linux-gnu' '--mandir=/usr/share/man' '--infodir=/usr/share/info'
'--sysconfdir=/etc/bind' '--localstatedir=/var/run/bind' '--enable-threads'
'--enable-largefile' '--with-libtool' '--enable-shared' '--enable-static'
'--with-openssl=/usr' '--with-gssapi=/usr' '--with-gnu-ld'
'--with-dlz-postgres=no' '--with-dlz-mysql=no' '--with-dlz-bdb=yes'
'--with-dlz-filesystem=yes' '--with-dlz-ldap=yes' '--with-dlz-stub=yes'
'--enable-ipv6' 'build_alias=x86_64-linux-gnu' 'host_alias=x86_64-linux-gnu'
'CFLAGS=-fno-strict-aliasing -DDIG_SIGCHASE -O2' 'LDFLAGS=' 'CPPFLAGS='
'CXXFLAGS=-g -O2' 'FFLAGS=-g -O2'
07-Jun-2010 15:06:22.132 adjusted limit on open files from 1024 to 1048576
07-Jun-2010 15:06:22.132 found 4 CPUs, using 4 worker threads
07-Jun-2010 15:06:22.132 using up to 4096 sockets
Auto configuration failed
140502524483328:error:0200100D:system library:fopen:Permission
denied:bss_file.c:122:fopen('/usr/lib/ssl/openssl.cnf','rb')
140502524483328:error:2006D002:BIO routines:BIO_new_file:system
lib:bss_file.c:127:
140502524483328:error:0E078002:configuration file routines:DEF_LOAD:system
lib:conf_def.c:199:
/usr/lib/ssl/openssl.cnf is a symlink to /etc/ssl/openssl.cnf, both
provided by the package openssl. Unfortunately, on the respective machine,
/etc/ssl/openssl.cnf is modified and not world-readable as it is by default
after installing the openssl package.
If openssl is not installed and therefore /usr/lib/ssl/openssl.cnf does not
exist (like on our secondary DNS server), everything is fine. But if the file,
or symlink in this case, does exist, but (its target) is not readable for the
user the named process runs as, then *bang*.
I think the point is, bind9 should not expect to be able to read configuration
files from other packages that it not depends on. Also, if a dependency on
openssl is explicit and intentional, then users should be warned if some
configuration files need to be readable by the user the named process runs as.
I clearly was not expecting that there is a connection between bind9 and
openssl whatsoever.
Best regards,
Mirko Gebauer
/pre This message contains information which may be confidential and
privileged.Unless you br
are the intended recipient (or authorized to receive this message for the
intended br
recipient), you may not use, copy, disseminate or disclose to anyone the
message or br
any information contained in the message. If you have received the message in
error, br
please advise the sender by reply e-mail, and delete the message. br
Thank you very much. br
(A) pre
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: Re: Bug#584748: ../sysdeps/x86_64/cacheinfo.c:255: handle_intel: Assertion `maxidx = 2' on AMD cpu
Processing commands for cont...@bugs.debian.org: severity 584748 important Bug #584748 [libc6-i686] ../sysdeps/x86_64/cacheinfo.c:255: handle_intel: Assertion `maxidx = 2' on AMD cpu Severity set to 'important' from 'serious' clone 584748 -1 Bug#584748: ../sysdeps/x86_64/cacheinfo.c:255: handle_intel: Assertion `maxidx = 2' on AMD cpu Bug 584748 cloned as bug 584912. reassign -1 valgrind Bug #584912 [libc6-i686] ../sysdeps/x86_64/cacheinfo.c:255: handle_intel: Assertion `maxidx = 2' on AMD cpu Bug reassigned from package 'libc6-i686' to 'valgrind'. Bug No longer marked as found in versions eglibc/2.11.1-2. retitle -1 valgrind: load i686 libraries while emulating an i586 CPU Bug #584912 [valgrind] ../sysdeps/x86_64/cacheinfo.c:255: handle_intel: Assertion `maxidx = 2' on AMD cpu Changed Bug title to 'valgrind: load i686 libraries while emulating an i586 CPU' from '../sysdeps/x86_64/cacheinfo.c:255: handle_intel: Assertion `maxidx = 2' on AMD cpu' thanks Stopping processing here. Please contact me if you need assistance. -- 584912: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=584912 584748: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=584748 -1: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=-1 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#584748: ../sysdeps/x86_64/cacheinfo.c:255: handle_intel: Assertion `maxidx = 2' on AMD cpu
severity 584748 important clone 584748 -1 reassign -1 valgrind retitle -1 valgrind: load i686 libraries while emulating an i586 CPU thanks On Mon, Jun 07, 2010 at 12:16:00PM +0200, Aurelien Jarno wrote: On Mon, Jun 07, 2010 at 08:47:23AM +0200, Aurelien Jarno wrote: Aurelien Jarno a écrit : On Sun, Jun 06, 2010 at 10:27:12PM +0200, Gianluigi Tiesi wrote: On 06/06/2010 14.55, Aurelien Jarno wrote: On Sun, Jun 06, 2010 at 02:17:29PM +0200, Gianluigi Tiesi wrote: On 06/06/2010 13.21, Aurelien Jarno wrote: Kernel: Linux 2.6.26-2-xen-amd64 (SMP w/8 CPU cores) This part is not consistent. Are you running reportbug on a different machine? yes the problem is on a old amd 800mhz box, but I use a different box for submitting do you need some additional infos about the amd installation? Yes, which libc6 packages are actually installed? I have fixed a bug that my cause the problem you are observing in version 2.11.1-2, so if you are running version 2.11.1-1, please try to upgrade. Also which kernel are you running? libc is 2.11.1-2 kernel: Linux attila 2.6.32-5-686 #1 SMP Tue Jun 1 04:59:47 UTC 2010 i686 GNU/Linux I known the problem with libc6-i686 and intel i7 I've reported some info too :) It's not the problem with core i7, but a different one that has also been corrected. One that breaks reading model and family in some conditions. this look different Unfortunately I am not able to reproduce it. Tried on an Athlon and on Opteron CPU. For your information, I have been able to find a machine with a CPU identical to yours, and I am now able to reproduce the issue. I'll debug it later today. Ok, here we go, it's a bit tricky. First of all, newer versions of the glibc tries to optimise the string function by using cache information, which are stored in cpuid level 2 and later on an Intel CPU. Secondly, valgrind does not use the real CPU, but always emulates an Intel one, trying to match the characteristics of the host CPU, especially in term of instruction set. When the CPU has no SSE support it emulates an old Pentium CPU, which have a max a cpuid level of 1. This is what happens when the host CPU is an Athlon one. The Pentium CPU is an i586 CPU, which does not support the CMOV instruction, so the libc from the libc6 package is used. On the other hand, the Athlon CPU is an i686 CPU, which does support the CMOV instruction, so the libc from libc6-i686 is used. Everything works well as long as you don't use valgrind. When you use it, it loads all the libraries using the host CPUID, that is it loads the libc from libc6-i686. It latter emulates a Pentium CPU, which has a cpuid level of 1 only. The glibc code recognizes an Intel CPU (as valgrind emulates it), and given it is the i686 version of the libc, it assumes it is at minimum a Pentium Pro (which is the first i686 Intel CPU), which means it assumes that the cpuid level is at 2. This is where all the cache information is stored. The bug really seems to be on the valgrind side, which should not load an i686 library while emulating an i586 CPU. OTOH, if it is difficult to fix, we can maybe remove assumptions that are correct, but wrong when using valgrind. I think the best is to fix this bug on both sides: - Valgrind should present a cpuid consistent with the libraries it loads - There is no real reason in the GNU libc to trigger an assertion here, 0 can be returned for all the cache values here. I am therefore cloning this bug and reassigning it to valgrind. -- Aurelien Jarno GPG: 1024D/F1BCDB73 aurel...@aurel32.net http://www.aurel32.net -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#584565: [Yaird-devel] Bug#584565: Bug#584565: [PATCH] enable yaird for kernel.org 2.6.33.4
Hi Jonas,
# Ah, no. My problem was different: http://bugs.debian.org/519866 -
# which lead to wrongly closed) http://bugs.debian.org/523828
# explaining that depmod -m needs to be run explicitly now.
See the touch thingie below.. ;)
# Is it perhaps similar to http://bugs.debian.org/516465 ?
Once (years ago) it could have been that one. Right now, it's
yaird not even recognising a luks setup at all..
# previous patches.
# It works for me too (now that I've generated that PCI module list.
A simple
touch /lib/modules/2.6.33.4/modules.{pci,usb}map
did work for me..
# But I am a bit suspicious about the devices that you ignore - could
# you perhaps elaborate more on that, to help ensure that they are
# universally sane to ignore?
Hm, I'd say, I just ignore path endings that aren't (at least for me)
any devices.. As I said, no warranty that my patches will work w/o
flaws for anyone else..
# last year I had a closer look at the problems with newer kernels,
# and tried to change how symlinks was resolved more generically
# (which I suspect is what you try to cover up with your ignore
That's what it sounds alike. And I think it's more or less what
the loop w/ the topological traversal is for: finding devices and
ignoring the rest. Whether that's a brilliant or helpless approach
I cannot foresay so..
# Right now, I'm a bit out of time and start thinking about hacking
# one of my previously used ramfs images w/ the new lvm stuff.
# Probably the faster solution, but then.. it's a hack.. :|
# If you can be persuaded, then I would be happy to have you help work
# directly on yaird.
Ha! That's not what I meant when I said I'm a bit out of time.. ;)
I provided the patches w/ the believ they might eventually help someone
else.. If so I'm glad if not, pity.. ;)
# If fumbling around then you could do that on a separate branch,
Yeah, one could call it that way.. Though, after all, it's maybe only
my impression and it's working out quite well for others..
# and when certain that you've narrowed down some flaw and found a
# sensible fix then you can apply that with a clear commit message to
# the main branch.
# Insterested? Are you familiar with Git? With Alioth?
git: not yet reaally familiar, svn/cvs: yep.
alioth: I know what is it and what it's for. Never used before.
Interested?
Partly: maybe your branch-approach isn't such a bad idea, though I'd say
once I fixed yaird locally and maybe sent the patches upstream (or to
the debian bts, as upstream (sf.net) honestly seems quite dead (as well as
debian yaird-devel, btw)) I won't touch yaird again for another couple
of years.. Last time I used it (and had to fix it) was probably 1 or 2 years
ago..
Cheers,
Nils
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#584102: [sysvinit-devel] startpar: Fail if fd 0 is strange tty
On Fri, Jun 04, 2010 at 10:18:18AM +0200, Petter Reinholdtsen wrote: Hi, Werner. Not sure where to send startpar issues, so I try here as I know I can reach you here. :) I proposed a patch for URL: http://bugs.debian.org/584102 , basicly allowing startpar to continue even when tcgetattr(0, tio) by running scripts sequencially. Can you have a look at let me know if it make sense. This issue is also reported as URL: http://savannah.nongnu.org/bugs/?30034 . Btw, why do startpar need stdin to be a tty? That is a guess but nevertheless the attributes are used to set them also to the pty/tty pairs used for parallel boot. As stdout of startpar can be used for a shell script parser (without option -M) the stdio was guessed to be a real tty. Werner -- Having a smoking section in a restaurant is like having a peeing section in a swimming pool. -- Edward Burr -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: Re: new lilo package maintainer? (was lilo removal in squeeze or please test grub2)
Processing commands for cont...@bugs.debian.org: reassign 505609 initramfs-tools Bug #505609 [linux-2.6] Unbootable after kernel upgrade: Lilo can't load kernel Bug reassigned from package 'linux-2.6' to 'initramfs-tools'. thanks Stopping processing here. Please contact me if you need assistance. -- 505609: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=505609 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#579948: Some debugging info
By now I'm pretty sure that this problem is due to the alignment code.
It goes like this:
1. ped_disk_add_partition() is called to add the partition. The
constraint which is passed to it is computed in
ped_device_get_optimum_alignment():
/* Align to a grain of 1MiB (like vista / win7) */
align = ped_alignment_new(0, 1048576 / dev-sector_size);
As dev-sector_size is 512, we end up with alignment of offset 0 and
grain_size 2048, and the resulting constraint passed to
ped_disk_add_partition() has start_align set to {offset = 0;
grain_size=2048} and end_align set to {offset = 2047, grain_size =
2048). That looks normal.
2. _partition_align() is called to align the partition with this
constraint. This simply calls the disk-specific partition_align
function, in this case sun_partition_align().
3. In sun_partition_align: disk_specific-cylinder_alignment is set to
1, so the final alignment will be an intersection of our initial
constraint and _get_strict_constraint(part-disk).
4. In _get_strict_constraint() the alignment is determined by a
product of dev-bios_geom.sectors and dev-bios_geom.heads. In my case
the former is 63 and the latter is 255, so the resulting strict
alignment will enforce partition alignment to 63 * 255 = 16065
sectors.
5. An intersection of two constraints, one aligning to 2048 and
another aligning to 16065 sectors, is computed. The least common
multiple of those two happens to be their product, so a combined
constraint ends up to be forcing the alignment to 2048 * 16065 =
32901120 sectors, or 16.8G (!). Looking at the debugging dump, the
second partition during my install was placed at 16845373440, which is
exactly 2048 * 16065 * 512, which confirms the alignment issue.
I have no idea how it worked before, nor could I figure out why the
addition of first partition worked as expected.
Best regards,
--
Jurij Smakov ju...@wooyd.org
Key: http://www.wooyd.org/pgpkey/ KeyID: C99E03CC
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#584879: enscript: File conflict with octave3.0 (/usr/share/enscript/hl/octave.st)
forcemerge 583561 584879 thanks Hi Petter, I think the fix is in enscript 1.6.5.2-1 - obviously this version needs to transition to squeeze. Thanks, -- Tim Retout t...@retout.co.uk -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: Re: enscript: File conflict with octave3.0 (/usr/share/enscript/hl/octave.st)
Processing commands for cont...@bugs.debian.org: forcemerge 583561 584879 Bug#583561: enscript: fails to upgrade: shares files with octave3.0 from lenny Bug#584879: enscript: File conflict with octave3.0 (/usr/share/enscript/hl/octave.st) Forcibly Merged 583561 584879. thanks Stopping processing here. Please contact me if you need assistance. -- 583561: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=583561 584879: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=584879 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#584102: startpar: Fail if fd 0 is strange tty
[Dr. Werner Fink] That is a guess but nevertheless the attributes are used to set them also to the pty/tty pairs used for parallel boot. As stdout of startpar can be used for a shell script parser (without option -M) the stdio was guessed to be a real tty. Right. Any idea how to get parallel booting working also when stdin and stdout is a pipe, like it is with OpenVZ at the moment? Happy hacking, -- Petter Reinholdtsen -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#584102: startpar: Fail if fd 0 is strange tty
On Mon, Jun 07, 2010 at 04:49:39PM +0200, Petter Reinholdtsen wrote:
[Dr. Werner Fink]
That is a guess but nevertheless the attributes are used to set them
also to the pty/tty pairs used for parallel boot. As stdout of
startpar can be used for a shell script parser (without option -M)
the stdio was guessed to be a real tty.
Right.
Any idea how to get parallel booting working also when stdin and
stdout is a pipe, like it is with OpenVZ at the moment?
Hmmm ... stderr maybe, something like
FILE* io[3];
int notty = 1;
io[0] = stdin;
io[1] = stdout;
io[2] = stderr;
io[3] = NULL;
for (n=0; io[n]; n++) {
int fd = isatty(fileno(io[n]));
if (tcgetattr(fd, tio) == 0) {
notty = 0
break;
}
}
could work.
Btw: I've lost your mail
Alternative startpar implementation - live-net-startpar
please resend. Beside any startpar it could be an option
to use a directory based boot scheme as insserv aloready
uses a tsort which can be mapped on `directory' based
sorting scheme. Could work simliar like the process_path()
routine of simpleinit ;)
Werner
--
Having a smoking section in a restaurant is like having
a peeing section in a swimming pool. -- Edward Burr
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#584124: salome: fails to install (tries to overwrite '/usr/bin/display'
Hi Adam, Are those libraries private to salome? (In other words, are you sure that no other package will be linked against them?) * If yes, there is no reason to provide libsalome5.1.3-0 and libsalome-dev packages, these libs are shipped by another package (python2.5-salome?) and can safely be moved into /usr/lib/salome/ * If no, they should indeed go into /usr/lib/ but name collisions will happen. Maybe the answer is a mix of both, some libs are private and some others are public. I was thinking the same thing. Back to André: are there libraries which are meant to be shared with other packages, or are they all private to Salomé? To my point of view, all librairies should be private to Salomé. I agree with the first solution, there is no need to provide libsalome* and python2.5-salome. BTW when looking at this issue, I found that python2.5-salome contains shared libraries, it thus must be arch:any and not arch:all. It also contains static libraries which can surely be dropped. BTW2, I wonder whether salome, python2.5-salome, libsalome5.1.3-0 and libsalome-dev could be merged into a single package (if all libs are private, of course). Indeed. There's still value in having a separate -common package, to reduce archive disk footprint. I'll first try to get the new paths working, then do this merger, and upload, then we can think about splitting things up differently. (core, extras, dev, test) Excellent. I saw anyway that you have just opened bug 584590 where we are going to try to solve that problem. Best regards, André -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#569358: must be another problem
tags 569358 - unreproducible moreinfo severity 569359 serious merge 569359 569358 thanks * martin f krafft madd...@debian.org [2010-05-26 09:49]: The initramfs hook does check for an empty level and fetches it directly from the device, if the config file does not have it: http://git.debian.org/?p=pkg-mdadm/mdadm.git;a=blob;f=debian/initramfs/hook;h=d4a623712b01e89978df5dcdabc3d68ff244944a;hb=932c11ccd4363a5db7a68ef0275489f8bf5f7eef#l199 There must be another reason for this problem. Could you please provide trace output? As mentioned in #569359, /sbin/mdadm --detail --scan /dev/md/0 fails because /dev/md/0 does not exist. Therefore, the hook fails to determine the RAID level. -- Martin Michlmayr http://www.cyrius.com/ -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed (with 1 errors): Re: Bug#569358: must be another problem
Processing commands for cont...@bugs.debian.org: tags 569358 - unreproducible moreinfo Bug #569358 [mdadm] MD_MODULES in initrd empty, RAID not started Removed tag(s) unreproducible and moreinfo. severity 569359 serious Bug #569359 [mdadm] /sbin/mdadm --detail --scan fails in d-i Severity set to 'serious' from 'normal' merge 569359 569358 Bug#569358: MD_MODULES in initrd empty, RAID not started Bug#569359: /sbin/mdadm --detail --scan fails in d-i Mismatch - only Bugs in same state can be merged: Values for `forwarded addr' don't match: #569358 has `'; #569359 has `ne...@suse.de' thanks Stopping processing here. Please contact me if you need assistance. -- 569359: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=569359 569358: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=569358 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#505609: new lilo package maintainer? (was lilo removal in squeeze or please test grub2)
On Mon, 07 Jun 2010 10:33:52 -0400 (EDT), Holger Levsen wrote: Hi Stephen, thanks for stepping up maintaining lilo in Debian! I hope you'll manage this well. Um, thanks; but I don't understand the reassignment of bug number 505609 to package initramfs-tools. If you read my previous posts to the bug log, it is clear that this problem started with a change to the maintainer scripts between Etch and Lenny. Please read my posts again carefully. Then consider whether this is really a bug in initramfs-tools or a bug in the kernel maintainer scripts. initramfs-tools only gets involved when update-initramfs -u is issued. And it *does* invoke the boot loader under these conditions, if do_bootloader = yes is present in /etc/kernel-img.conf and lilo is installed. But for a kernel install or reconfigure, it is the responsibility of the kernel maintainer scripts to invoke the bootloader. See also, for example, linux-image-2.6.26-2-s390.postinst, where zipl is assigned as the bootloader on line 38. This really is an open and shut case, if only I can the kernel people to actually look at it! Please look at it! -- .''`. Stephen Powell : :' : `. `'` `- -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#569359: mdadm -Ds insists on /dev/md/X device presence
So I briefly booted into the last stable release of Debian to see why it works. The difference here is that mdadm shows /dev/mdX device names by default (there was no map file in /var/run): /var/run # mdadm --examine --scan --config=partitions ARRAY /dev/md0 level=raid1 num-devices=2 UUID=01d4e1dd:5a6df36c:306f37c8:5b3189c6 and since /dev/md0 exists everything is fine. It seems to me that at some point (probably with mdadm 3.1.1), the output of --examine --scan changed to /dev/md/X device names and this is when things (with Debian installer) started to break since we only have /dev/mdX. Presumably, the change to /dev/md/X was intentional (Neil), so maybe we should: - ensure that mdadm in Debian installer ships an udev rules that creates /dev/md/X - change the creation of RAID devices from mdadm --create /dev/md$FOO to mdadm --create /dev/md/$FOO Comments? -- Martin Michlmayr http://www.cyrius.com/ -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#573991: marked as done (libc6: eglibc 2.11 FTBFS on hppa)
Your message dated Mon, 7 Jun 2010 17:51:33 +0200 with message-id 20100607155133.ga9...@volta.aurel32.net and subject line Re: libc6: eglibc 2.11 FTBFS on hppa has caused the Debian Bug report #573991, regarding libc6: eglibc 2.11 FTBFS on hppa 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 this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 573991: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=573991 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: libc6 Version: 2.11-0exp6 Severity: serious The following test failures/regressions are applicable to hppa/experimental. I have no buildd log URL to provide for this. tstdiomisc.out tststatic2.out tststatic.out tst-tls9-static.out ---End Message--- ---BeginMessage--- On Mon, Mar 15, 2010 at 02:18:03PM +, Clint Adams wrote: Package: libc6 Version: 2.11-0exp6 Severity: serious The following test failures/regressions are applicable to hppa/experimental. I have no buildd log URL to provide for this. tstdiomisc.out tststatic2.out tststatic.out tst-tls9-static.out The bug have been fixed, and eglibc 2.11.1-1 or 2.11.1-2 now build fine on hppa. Closing the bug. -- Aurelien Jarno GPG: 1024D/F1BCDB73 aurel...@aurel32.net http://www.aurel32.net ---End Message---
Bug#584929: znc: segfault under certain conditions
Package: znc Version: 0.090~rc1-1 Severity: grave Justification: renders package unusable After updating 0.080-1 to 0.090-rc1-1 znc segfaults. This happens for instance when klicking traffic in the webadmin pages or issuing the traffic command on the /znc shell. May happen under other conditions aswell. Znc -D does not provide usfull output other then the segfault message direktly after rescieve of the mentioned command. -- System Information: Debian Release: squeeze/sid APT prefers testing APT policy: (500, 'testing') Architecture: i386 (i686) Kernel: Linux 2.6.18-ovz028stab039.1-smp (SMP w/2 CPU cores) Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968) Shell: /bin/sh linked to /bin/dash Versions of packages znc depends on: ii libc-ares21.7.1-0library for asyncronous name resol ii libc6 2.10.2-9 Embedded GNU C Library: Shared lib ii libgcc1 1:4.4.4-1 GCC support library ii libssl0.9.8 0.9.8n-1 SSL shared libraries ii libstdc++64.4.4-1The GNU Standard C++ Library v3 Versions of packages znc recommends: ii znc-extra0.090~rc1-1 extra modules for znc pn znc-perl none (no description available) pn znc-tcl none (no description available) znc suggests no packages. -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#584930: Two security issues fixed in FreeBSD
Package: kfreebsd-8 Severity: grave Tags: security Hi, the following CVE IDs have been published for FreeBSD, please check whether they need to be fixed for kfreebsd and whether kfreebsd-6 and kfreebsd-7 from Lenny are affected: CVE-2010-2022: http://security.FreeBSD.org/advisories/FreeBSD-SA-10:04.jail.asc CVE-2010-2020: http://security.FreeBSD.org/advisories/FreeBSD-SA-10:06.nfsclient.asc Cheers, Moritz -- System Information: Debian Release: squeeze/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: i386 (i686) Kernel: Linux 2.6.32-5-686 (SMP w/1 CPU core) Locale: LANG=C, lc_ctype=de_de.iso-8859...@euro (charmap=ISO-8859-15) Shell: /bin/sh linked to /bin/bash -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#584932: CVE-2010-1938
Package: opie Severity: grave Tags: security Hi Michael, please see http://security.FreeBSD.org/advisories/FreeBSD-SA-10:05.opie.asc for details and a patch. Please fix this for Squeeze. I don't think we need a DSA for Lenny. However we could still fix it through a point update. Cheers, Moritz -- System Information: Debian Release: squeeze/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: i386 (i686) Kernel: Linux 2.6.32-5-686 (SMP w/1 CPU core) Locale: LANG=C, lc_ctype=de_de.iso-8859...@euro (charmap=ISO-8859-15) Shell: /bin/sh linked to /bin/bash -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#584933: CVE-2010-1513
Package: ziproxy Severity: grave Tags: security Hi, the following security has been reported against ziproxy: CVE-2010-1513 Multiple integer overflows in src/image.c in Ziproxy before 3.0.1 allow remote attackers to execute arbitrary code via (1) a large JPG image, related to the jpg2bitmap function or (2) a large PNG image, related to the png2bitmap function, leading to heap-based buffer overflows. This is fixed in 3.0.1. Cheers, Moritz -- System Information: Debian Release: squeeze/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: i386 (i686) Kernel: Linux 2.6.32-5-686 (SMP w/1 CPU core) Locale: LANG=C, lc_ctype=de_de.iso-8859...@euro (charmap=ISO-8859-15) Shell: /bin/sh linked to /bin/bash Versions of packages ziproxy depends on: ii libc6 2.10.2-9 Embedded GNU C Library: Shared lib ii libgif4 4.1.6-9 library for GIF images (library) ii libjasper1 1.900.1-7The JasPer JPEG-2000 runtime libra ii libjpeg62 6b-16.1 The Independent JPEG Group's JPEG ii libpng12-0 1.2.43-1 PNG library - runtime ii zlib1g 1:1.2.3.4.dfsg-3 compression library - runtime ziproxy recommends no packages. ziproxy suggests no packages. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: [bts-link] source package src:libdbix-class-perl
Processing commands for cont...@bugs.debian.org: # # bts-link upstream status pull for source package src:libdbix-class-perl # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html # user bts-link-upstr...@lists.alioth.debian.org Setting user to bts-link-upstr...@lists.alioth.debian.org (was bts-link-de...@lists.alioth.debian.org). # remote status report for #584391 (http://bugs.debian.org/584391) # * http://rt.cpan.org/Public/Bug/Display.html?id=58043 # * remote status changed: (?) - resolved # * closed upstream tags 584391 + fixed-upstream Bug #584391 [src:libdbix-class-perl] libdbix-class-perl: FTBFS: tests failed Added tag(s) fixed-upstream. usertags 584391 + status-resolved Bug#584391: libdbix-class-perl: FTBFS: tests failed There were no usertags set. Usertags are now: status-resolved. thanks Stopping processing here. Please contact me if you need assistance. -- 584391: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=584391 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#584627: marked as done (buildcross: uninstallable on !amd64)
Your message dated Mon, 07 Jun 2010 17:02:06 + with message-id e1olfia-0008ni...@ries.debian.org and subject line Bug#584627: fixed in buildcross 0.0.4 has caused the Debian Bug report #584627, regarding buildcross: uninstallable on !amd64 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 this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 584627: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=584627 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: buildcross Version: 0.0.3 Severity: serious Your package is only installable on amd64 due to the dependency on libc6-dev-i386 (among others). ISTM the package should be arch:any and only depend on gcc-multilib, libc6-dev-i386, lib32gcc1 on architectures where these packages are available. BTW, is it correct to depend on libreadline5-dev rather than libreadline6-dev or libreadline-dev? -- System Information: Debian Release: squeeze/sid APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: i386 (x86_64) Kernel: Linux 2.6.34-nouveau (SMP w/2 CPU cores) Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash ---End Message--- ---BeginMessage--- Source: buildcross Source-Version: 0.0.4 We believe that the bug you reported is fixed in the latest version of buildcross, which is due to be installed in the Debian FTP archive: buildcross_0.0.4.dsc to main/b/buildcross/buildcross_0.0.4.dsc buildcross_0.0.4.tar.gz to main/b/buildcross/buildcross_0.0.4.tar.gz buildcross_0.0.4_all.deb to main/b/buildcross/buildcross_0.0.4_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 584...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Hector Oron zu...@debian.org (supplier of updated buildcross 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 ftpmas...@debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Mon, 07 Jun 2010 18:06:52 +0200 Source: buildcross Binary: buildcross Architecture: source all Version: 0.0.4 Distribution: experimental Urgency: low Maintainer: Debian Embedded debian-embed...@lists.debian.org Changed-By: Hector Oron zu...@debian.org Description: buildcross - Cross build a full set of Debian toolchain Closes: 584627 Changes: buildcross (0.0.4) experimental; urgency=low . * Add function code to start building Debian from scratch (upstream way). o Add undocumented (at the moment) --bootstrap-debsrc; --bootstrap-upsrc. * Fix uninstallable on !amd64: Remove libc6-dev-i386, lib32gcc1 dependencies and change libreadline5-dev and libncurses5-dev by non versioned libs. (Closes: #584627) Checksums-Sha1: e7bbe6001b069b19dff3f5df94b00b056e39a6cc 1678 buildcross_0.0.4.dsc eb84eba91ef8af622ca5100cec4f925f528c3e3d 21773 buildcross_0.0.4.tar.gz 41c6dcc84114f706847d559f57e4e5ce2ab0795b 19224 buildcross_0.0.4_all.deb Checksums-Sha256: 683d33bc0b130da57dd20938a4f6d08843c3a4b7a5a9e8dd9dba38db466b2012 1678 buildcross_0.0.4.dsc 97ead4c3d227e3d4d8c4218487d4858ca16e69416354d1b4ea224fa96d354684 21773 buildcross_0.0.4.tar.gz 9809f8c267f9c59441b833e19ada6f2b8ccdce897b98a28f5dfbb0e83f62eea8 19224 buildcross_0.0.4_all.deb Files: 2cdc1b2753fa19df010531cc4661ade4 1678 utils extra buildcross_0.0.4.dsc 016741d19a54b51904c20a29ab8ffaa9 21773 utils extra buildcross_0.0.4.tar.gz 11568eeb521a4b5c12fb646529fc2059 19224 utils extra buildcross_0.0.4_all.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.10 (GNU/Linux) iQIcBAEBAgAGBQJMDSSSAAoJEK8ig6p24qx7Lx8P/jKol64mGeWk/JPG4jgWwFbW PlyoGasecOrMbb7OGlos8eJv3zLuGfYOo0CurT15rvglJLfnb3DojARCOeKvEVGg b30ykXu/kaO+K3+IrieJpYaT/vBd9dwYGgvQ+BiTka3ndkMSxPD7fliNhDn9YAIJ +feaVC+GiDAq0ikY59qYYViKNbJCKMLroYlHV0I+VEJiJrYglk724jLBn2+wloIY nN6Ng6GxqUz7OFmYKMRVEF2d9rzo7TWK5lv5kmamJTSRCqEqC2dpk6DjVh8Iqvp1 ut3uFstiZqkUntG9hd7aKScn+2yKFF1sbIMfUg7WbRtlgtwBxpZVoYDixXOoSbnM 8N0udY2ChJzi+o1X0NTtDOyrhsdvkId7GvhkujUiEEmMvfRsSJA/AwmncTMGBeBe xjzQ5cF0VBmh1P7rmiJO4QRDMooVAgtG0UR0y9mX1zA/nynFSEfj0a52w3+f2mXP Rsm8en3RKguNtGnQiQdsvRD+TLq/jrD9W/uSdRdKlRTOZrQ7qqOFNiO3CmSqGZmY 6+GgaTg4y/+fqUZhpI5ZPrn2zG6kaQ/WO+t2PAcfw+Mye4OpCPWLuF8DM+V12zvT emRa/m/kJSKyKKIRRIYQ0Ygrm8xamrjKfqXyEW5y3fSZWMD2Dl3JWETo4xR7fsHh FB1GruEdYDNR/KiHCefw =aCcA -END PGP SIGNATURE- ---End Message---
Bug#584358: fix
I'll fix this bug next weekend, maybe earlier. Note to release managers: As long as courier 0.65.0 keeps out of testing, testing is not affected. WM -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#561203: threads and fork on machine with VIPT-WB cache
On Fri, Jun 04, 2010 at 12:44:55PM +0200, Thibaut VARENE wrote: On Fri, Jun 4, 2010 at 7:21 AM, dann frazier da...@debian.org wrote: On Fri, Jun 04, 2010 at 10:03:07AM +0900, NIIBE Yutaka wrote: Modestas Vainius wrote: Note that Debian's buildds run a UP kernel, so as soon as those fixes go upstream we can pull them in. Thanks for all your work here! Well, as long as this is unfixed or at least common, I don't see how hppa can be considered to be a release arch. Is that UP patch available somewhere? My case and my analysis talked about UP kernel, and John David Anglin made a patch: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=561203#144 After that, the discussion went to SMP cases. It would be better to evaluate the patch again, and make sure it works for UP case and fix failures of buildd, then apply for Linux in Debian (only) for HPPA. I know that the patch is not that ideal because it touches architecture independent part of Linux, but it is worth for Linux in Debian (or Linux for the HPPA machine of buildd, at least). I'm happy to test the patch if necessary to help push this change upstream. However, we do need the change to go upstream before we can include it in the Debian kernel. Just for reference, I've summarized the test cases and related patches here: http://wiki.parisc-linux.org/TestCases Cool - that is helpful. I've updated the kernel on peri/penalosa with the various patches listed there that have gone upstream, but I'm not seeing better results with any failing packages. btw, I thought it would be useful to edit that page and tag each patch with its status in Debian (in-official-kernel, installed-on-buildds, etc), but the page appears to be immutable. -- dann frazier -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#583018: marked as done (pymvpa: FTBFS: svmc_wrap.cpp:2891: error: 'svm_print_string' was not declared in this scope)
Your message dated Mon, 07 Jun 2010 17:18:06 + with message-id e1olfxe-tr...@ries.debian.org and subject line Bug#583018: fixed in pymvpa 0.4.5~dev23-1 has caused the Debian Bug report #583018, regarding pymvpa: FTBFS: svmc_wrap.cpp:2891: error: 'svm_print_string' was not declared in this scope 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 this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 583018: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=583018 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Source: pymvpa Version: 0.4.4-1 Severity: serious Tags: squeeze sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20100524 qa-ftbfs Justification: FTBFS on amd64 Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part: gcc -pthread -shared -Wl,-O1 -Wl,-Bsymbolic-functions -g -O2 -g -Wall -O2 /build/user-pymvpa_0.4.4-1-amd64-PpEO5E/pymvpa-0.4.4/./build/temp.linux-x86_64-2.5/mvpa/clfs/libsmlrc/smlr.o -lm -o /build/user-pymvpa_0.4.4-1-amd64-PpEO5E/pymvpa-0.4.4/./build/lib.linux-x86_64-2.5/mvpa/clfs/libsmlrc/smlrc.so building 'mvpa.clfs.libsvmc._svmc' extension compiling C++ sources C compiler: g++ -pthread -fno-strict-aliasing -DNDEBUG -g -fwrapv -O2 -Wall -g -O2 -g -Wall -O2 -fPIC creating /build/user-pymvpa_0.4.4-1-amd64-PpEO5E/pymvpa-0.4.4/build/temp.linux-x86_64-2.5/build creating /build/user-pymvpa_0.4.4-1-amd64-PpEO5E/pymvpa-0.4.4/build/temp.linux-x86_64-2.5/build/user-pymvpa_0.4.4-1-amd64-PpEO5E creating /build/user-pymvpa_0.4.4-1-amd64-PpEO5E/pymvpa-0.4.4/build/temp.linux-x86_64-2.5/build/user-pymvpa_0.4.4-1-amd64-PpEO5E/pymvpa-0.4.4 creating /build/user-pymvpa_0.4.4-1-amd64-PpEO5E/pymvpa-0.4.4/build/temp.linux-x86_64-2.5/build/user-pymvpa_0.4.4-1-amd64-PpEO5E/pymvpa-0.4.4/build creating /build/user-pymvpa_0.4.4-1-amd64-PpEO5E/pymvpa-0.4.4/build/temp.linux-x86_64-2.5/build/user-pymvpa_0.4.4-1-amd64-PpEO5E/pymvpa-0.4.4/build/src.linux-x86_64-2.5 creating /build/user-pymvpa_0.4.4-1-amd64-PpEO5E/pymvpa-0.4.4/build/temp.linux-x86_64-2.5/build/user-pymvpa_0.4.4-1-amd64-PpEO5E/pymvpa-0.4.4/build/src.linux-x86_64-2.5/mvpa creating /build/user-pymvpa_0.4.4-1-amd64-PpEO5E/pymvpa-0.4.4/build/temp.linux-x86_64-2.5/build/user-pymvpa_0.4.4-1-amd64-PpEO5E/pymvpa-0.4.4/build/src.linux-x86_64-2.5/mvpa/clfs creating /build/user-pymvpa_0.4.4-1-amd64-PpEO5E/pymvpa-0.4.4/build/temp.linux-x86_64-2.5/build/user-pymvpa_0.4.4-1-amd64-PpEO5E/pymvpa-0.4.4/build/src.linux-x86_64-2.5/mvpa/clfs/libsvmc compile options: '-I/usr/include/numpy -I/usr/include/libsvm-2.0/libsvm -I/usr/include/libsvm -I/usr/local/include/libsvm -I/usr/local/include/libsvm-2.0/libsvm -I/usr/local/include -I/usr/lib/python2.5/site-packages/numpy/core/include -I/usr/include/python2.5 -c' g++: /build/user-pymvpa_0.4.4-1-amd64-PpEO5E/pymvpa-0.4.4/build/src.linux-x86_64-2.5/mvpa/clfs/libsvmc/svmc_wrap.cpp /build/user-pymvpa_0.4.4-1-amd64-PpEO5E/pymvpa-0.4.4/build/src.linux-x86_64-2.5/mvpa/clfs/libsvmc/svmc_wrap.cpp: In function 'void svm_set_verbosity(int)': /build/user-pymvpa_0.4.4-1-amd64-PpEO5E/pymvpa-0.4.4/build/src.linux-x86_64-2.5/mvpa/clfs/libsvmc/svmc_wrap.cpp:2891: error: 'svm_print_string' was not declared in this scope /build/user-pymvpa_0.4.4-1-amd64-PpEO5E/pymvpa-0.4.4/build/src.linux-x86_64-2.5/mvpa/clfs/libsvmc/svmc_wrap.cpp:2893: error: 'svm_print_string' was not declared in this scope /build/user-pymvpa_0.4.4-1-amd64-PpEO5E/pymvpa-0.4.4/build/src.linux-x86_64-2.5/mvpa/clfs/libsvmc/svmc_wrap.cpp: In function 'void svm_set_verbosity(int)': /build/user-pymvpa_0.4.4-1-amd64-PpEO5E/pymvpa-0.4.4/build/src.linux-x86_64-2.5/mvpa/clfs/libsvmc/svmc_wrap.cpp:2891: error: 'svm_print_string' was not declared in this scope /build/user-pymvpa_0.4.4-1-amd64-PpEO5E/pymvpa-0.4.4/build/src.linux-x86_64-2.5/mvpa/clfs/libsvmc/svmc_wrap.cpp:2893: error: 'svm_print_string' was not declared in this scope error: Command g++ -pthread -fno-strict-aliasing -DNDEBUG -g -fwrapv -O2 -Wall -g -O2 -g -Wall -O2 -fPIC -I/usr/include/numpy -I/usr/include/libsvm-2.0/libsvm -I/usr/include/libsvm -I/usr/local/include/libsvm -I/usr/local/include/libsvm-2.0/libsvm -I/usr/local/include -I/usr/lib/python2.5/site-packages/numpy/core/include -I/usr/include/python2.5 -c /build/user-pymvpa_0.4.4-1-amd64-PpEO5E/pymvpa-0.4.4/build/src.linux-x86_64-2.5/mvpa/clfs/libsvmc/svmc_wrap.cpp -o /build/user-pymvpa_0.4.4-1-amd64-PpEO5E/pymvpa-0.4.4/./build/temp.linux-x86_64-2.5/build/user-pymvpa_0.4.4-1-amd64-PpEO5E/pymvpa-0.4.4/build/src.linux-x86_64-2.5/mvpa/clfs/libsvmc/svmc_wrap.o
Bug#584722: marked as done (Kazehakase no longer displays pages in Squeeze)
Your message dated Mon, 07 Jun 2010 17:17:18 + with message-id e1olfws-jw...@ries.debian.org and subject line Bug#584722: fixed in kazehakase 0.5.8-4 has caused the Debian Bug report #584722, regarding Kazehakase no longer displays pages in Squeeze 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 this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 584722: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=584722 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: kazehakase Version: 0.5.8-3 Severity: normal *** Please type your report below this line *** Kazehakase just displays a blank page, regardless of how I open it (from file manager, from terminal, from mail client or from menu and bookmark.) This problem occurs with version 0.5.8-3 (i386) and goes away with a forced downgrade to 0.5.8-2. If I open it from a terminal, the program opens to a blank page, and there's no output in the terminal. Deleting ~/.kazehakase made no difference. -- System Information: Debian Release: squeeze/sid APT prefers testing APT policy: (990, 'testing'), (500, 'unstable') Architecture: i386 (i686) Kernel: Linux 2.6.32-5-686 (SMP w/2 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages kazehakase depends on: ii kazehakase-gecko0.5.8-3 Gecko rendering engine for kazehak ii libc6 2.10.2-9 Embedded GNU C Library: Shared lib ii libdbus-glib-1-20.86-1 simple interprocess messaging syst ii libestraier81.4.9-1.4a full-text search system Librarie ii libgcrypt11 1.4.5-2 LGPL Crypto library - runtime libr ii libgettext-ruby1.8 2.1.0-2.1Gettext for ruby1.8 ii libglib2.0-02.24.1-1 The GLib library of C routines ii libgnutls26 2.8.6-1 the GNU TLS library - runtime libr ii libgtk2-ruby0.19.3-2 GTK+ bindings for the Ruby languag ii libgtk2.0-0 2.20.1-1 The GTK+ graphical user interface ii libice6 2:1.0.6-1X11 Inter-Client Exchange library ii libpango1.0-0 1.28.0-1 Layout and rendering of internatio ii libqdbm14 1.8.74-1.4 QDBM Database Libraries [runtime] ii libruby1.8 1.8.7.249-3 Libraries necessary to run Ruby 1. ii libsm6 2:1.1.1-1X11 Session Management library ii ruby1.8 1.8.7.249-3 Interpreter of object-oriented scr ii zlib1g 1:1.2.3.4.dfsg-3 compression library - runtime kazehakase recommends no packages. Versions of packages kazehakase suggests: pn anthy none (no description available) pn mecab none (no description available) pn migemonone (no description available) -- no debconf information ---End Message--- ---BeginMessage--- Source: kazehakase Source-Version: 0.5.8-4 We believe that the bug you reported is fixed in the latest version of kazehakase, which is due to be installed in the Debian FTP archive: kazehakase-dbg_0.5.8-4_i386.deb to main/k/kazehakase/kazehakase-dbg_0.5.8-4_i386.deb kazehakase-gecko_0.5.8-4_i386.deb to main/k/kazehakase/kazehakase-gecko_0.5.8-4_i386.deb kazehakase-webkit_0.5.8-4_i386.deb to main/k/kazehakase/kazehakase-webkit_0.5.8-4_i386.deb kazehakase_0.5.8-4.diff.gz to main/k/kazehakase/kazehakase_0.5.8-4.diff.gz kazehakase_0.5.8-4.dsc to main/k/kazehakase/kazehakase_0.5.8-4.dsc kazehakase_0.5.8-4_i386.deb to main/k/kazehakase/kazehakase_0.5.8-4_i386.deb A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 584...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Yavor Doganov ya...@gnu.org (supplier of updated kazehakase 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 ftpmas...@debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Mon, 07 Jun 2010 14:43:22 +0300 Source: kazehakase Binary: kazehakase kazehakase-gecko kazehakase-webkit kazehakase-dbg Architecture: source i386 Version: 0.5.8-4 Distribution: unstable Urgency: high Maintainer: Yavor Doganov ya...@gnu.org Changed-By: Yavor Doganov ya...@gnu.org Description: kazehakase -
Bug#584102: startpar: Fail if fd 0 is strange tty
[Dr. Werner Fink] Hmmm ... stderr maybe, something like I do not know, but suspect stderr is a pipe too. Is a tty required to run scripts in parallel? Lets keep this discussion CCed to the BTS (584...@bugs.debian.org). Btw: I've lost your mail Bounced it to you. Beside any startpar it could be an option to use a directory based boot scheme as insserv aloready uses a tsort which can be mapped on `directory' based sorting scheme. Could work simliar like the process_path() routine of simpleinit ;) upstart is getting support for handling init.d scripts natively, so that will be an alternative too. Would be nice to get startpar to start rcS.d/ and rc2.d/ at once, to maximize concurrency, as Debian uses init.d scripts also for the early boot. Also, would be nice to get dynamic resolution of $remote_fs, to let it be equal to $local_fs if no networked file systems are listed in /etc/fstab. :) Not sure how hard that would be. Lets continue this part of the discussion without CC-ing the BTS. Happy hacking, -- Petter Reinholdtsen -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#584784: also applies to unstable
Am 2010-06-07 03:44, schrieb Ben Hutchings: On Sun, 2010-06-06 at 23:18 +0200, Willi Mann wrote: Kernel panic - not syncing: To avoid data corruption io_map_base MUST be set with multiple PCI domains. has been applied on all PCI MIPS systems since Linux 2.6.24. Are you quite sure that this was introduced by the kernel upgrade and not a qemu upgrade. Yes, I didn't change the qemu version, it's really only the kernel that changed. Attached is the dmesg output of the working kernel, version 2.6.32-9. OK, it looks like this is due to an botched switch from IDE to libata drivers on MIPS. The qemu emulated HD controller is now being handled by the ide-generic driver whereas it should have been switched from piix to ata_piix, and ide-generic triggers this panic for reasons I don't fully understand. This will get fixed, but not immediately. OK. As long as it gets fixed before the release... Should we notify the d-i people so that they can put a note on the errata page? Though I wonder why the BTS did not fully process my found command. It still only marks the version in experimental as affected. WM -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#584285: salome: FTBFS: hxx2salome.cpp:247: error: 'system' is not a member of 'std'
Hi Denis, Thanks for all of these patches. I have a couple of small issues though: On Mon, 2010-06-07 at 01:46 +0200, Denis Barbier wrote: Hello, Here is a new series of patches. I am still unable to build salome; disk space is okay now, but dpkg-shlibdeps aborted due to memory allocation errors on my laptop with 2GB of RAM. - 0001 Add 'set -e' before loops on modules in build and install targets - 0002 Add Vcs fields into debian/control - 0003 Add missing Build-Depends: libqt4-opengl-dev - 0004 Remove libcppunit-dev from Build-Depends. Tests are not run, so there is little value in compiling them I'd like to leave this there, as we'll have a separate salome-test package later, and don't trust myself to remember to re-add it. :-) - 0005 Add --disable-dependency-tracking --disable-maintainer-mode to configure flags. This remove some targets in Makefiles and should speed up a little bit compilation. Unfortunately the speed up is quite low, around 9%. If the benefit is that low, should we perhaps leave dependency tracking and maintainer mode in for now? I should be able to isolate which Build-Depends-Indep are and are not needed later today. doxygen definitely is needed by YACS, but graphviz and others should only be needed when doing the make usr_docs dev_docs in the build-indep-stamp target -- I think... -Adam -- GPG fingerprint: D54D 1AEE B11C CE9B A02B C5DD 526F 01E8 564E E4B6 Engineering consulting with open source tools http://www.opennovation.com/ signature.asc Description: This is a digitally signed message part
Bug#584929: znc: segfault under certain conditions
Am 07.06.2010 18:11, schrieb Suschman: Package: znc Version: 0.090~rc1-1 Severity: grave Justification: renders package unusable After updating 0.080-1 to 0.090-rc1-1 znc segfaults. This happens for instance when klicking traffic in the webadmin pages or issuing the traffic command on the /znc shell. May happen under other conditions aswell. Znc -D does not provide usfull output other then the segfault message direktly after rescieve of the mentioned command. Do you get a useful output with `gdb znc' if you install znc-dbg? -- /* Mit freundlichem Gruß / With kind regards, Patrick Matthäi GNU/Linux Debian Developer E-Mail: pmatth...@debian.org patr...@linux-dev.org Comment: Always if we think we are right, we were maybe wrong. */ -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#583956: closed by Nicholas Breen nbr...@ofb.net (Bug#583956: fixed in grace 1:5.1.22-7)
On Sun, 06 Jun 2010 23:21:08 + Debian Bug Tracking System wrote: [...] * Replace defoma font management with new /usr/sbin/update-grace-fonts trigger. Many thanks to Kenshi Muto for the implementation. [...] Hi! I've just installed grace/1:5.1.22-7 from unstable, and I can confirm that the bug seems to be fixed. Nicholas and Kenshi, thanks a lot to both of you for fixing the issue! Bye. -- http://www.inventati.org/frx/progs/scripts/pdebuild-hooks.html Need some pdebuild hook scripts? . Francesco Poli . GnuPG key fpr == C979 F34B 27CE 5CD8 DC12 31B5 78F4 279B DD6D FCF4 pgpLuREr3cE7n.pgp Description: PGP signature
Bug#583964: gsfonts: breaks grace
notfixed 583964 grace/1:5.1.22-7 reopen 583964 retitle 583964 gsfonts: breaks grace (= 1:5.1.22-6) thanks On Wed, 2 Jun 2010 00:49:25 +0200 Francesco Poli wrote: [...] The present bug report (#583964) should stay open until a fixed version of the grace package has migrated into testing. Nicholas, please keep the gsfonts bug open until a fixed version of the grace package has *migrated into testing*. I will try and remember to close the gsfonts bug, as soon as grace/1:5.1.22-7 has migrated into testing. -- http://www.inventati.org/frx/progs/scripts/pdebuild-hooks.html Need some pdebuild hook scripts? . Francesco Poli . GnuPG key fpr == C979 F34B 27CE 5CD8 DC12 31B5 78F4 279B DD6D FCF4 pgpMaLB3DaEqy.pgp Description: PGP signature
Bug#584784: also applies to unstable
On Mon, 2010-06-07 at 19:59 +0200, Willi Mann wrote: Am 2010-06-07 03:44, schrieb Ben Hutchings: On Sun, 2010-06-06 at 23:18 +0200, Willi Mann wrote: Kernel panic - not syncing: To avoid data corruption io_map_base MUST be set with multiple PCI domains. has been applied on all PCI MIPS systems since Linux 2.6.24. Are you quite sure that this was introduced by the kernel upgrade and not a qemu upgrade. Yes, I didn't change the qemu version, it's really only the kernel that changed. Attached is the dmesg output of the working kernel, version 2.6.32-9. OK, it looks like this is due to an botched switch from IDE to libata drivers on MIPS. The qemu emulated HD controller is now being handled by the ide-generic driver whereas it should have been switched from piix to ata_piix, and ide-generic triggers this panic for reasons I don't fully understand. This will get fixed, but not immediately. OK. As long as it gets fixed before the release... Should we notify the d-i people so that they can put a note on the errata page? I'm cc'ing this to the d-i mailing list. Though I wonder why the BTS did not fully process my found command. It still only marks the version in experimental as affected. No it doesn't. You may be looking at a cached version of the page. Ben. -- Ben Hutchings Once a job is fouled up, anything done to improve it makes it worse. signature.asc Description: This is a digitally signed message part
Processed: Re: Bug#583964: gsfonts: breaks grace
Processing commands for cont...@bugs.debian.org:
notfixed 583964 grace/1:5.1.22-7
Bug #583964 {Done: Nicholas Breen nbr...@ofb.net} [gsfonts] gsfonts: breaks
grace
Bug No longer marked as fixed in versions grace/1:5.1.22-7.
reopen 583964
Bug #583964 {Done: Nicholas Breen nbr...@ofb.net} [gsfonts] gsfonts: breaks
grace
retitle 583964 gsfonts: breaks grace (= 1:5.1.22-6)
Bug #583964 [gsfonts] gsfonts: breaks grace
Changed Bug title to 'gsfonts: breaks grace (= 1:5.1.22-6)' from 'gsfonts:
breaks grace'
thanks
Stopping processing here.
Please contact me if you need assistance.
--
583964: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=583964
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: severity of 584784 is important
Processing commands for cont...@bugs.debian.org: # This would normally be RC, but since no-one spotted it for 2 months this platform does not seem important enough to block transition to testing. severity 584784 important Bug #584784 [linux-2.6] /boot/vmlinux-2.6.34-1-4kc-malta: no longer boots in qemu Severity set to 'important' from 'grave' thanks Stopping processing here. Please contact me if you need assistance. -- 584784: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=584784 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#584400: marked as done (CVE-2010-1626)
Your message dated Mon, 07 Jun 2010 19:56:22 + with message-id e1oliqo-0002tf...@ries.debian.org and subject line Bug#584400: fixed in mysql-dfsg-5.0 5.0.51a-24+lenny4 has caused the Debian Bug report #584400, regarding CVE-2010-1626 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 this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 584400: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=584400 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: mysql-dfsg-5.0 Severity: serious Tags: security -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi, the following CVE (Common Vulnerabilities Exposures) id was published for mysql-dfsg-5.0. CVE-2010-1626[0]: | MySQL before 5.1.46 allows local users to delete the data and index | files of another user's MyISAM table via a symlink attack in | conjunction with the DROP TABLE command, a different vulnerability | than CVE-2008-4098 and CVE-2008-7247. If you fix the vulnerability please also make sure to include the CVE id in your changelog entry. For further information see: [0] http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2010-1626 http://security-tracker.debian.org/tracker/CVE-2010-1626 -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.10 (GNU/Linux) iEYEARECAAYFAkwHhgEACgkQNxpp46476apr1ACgj/0dTbl7XPSC3wR0fH2kRxCU Os0Anjh8yNqu6lKjXyJrrwL9zl/ab+/C =RgmB -END PGP SIGNATURE- ---End Message--- ---BeginMessage--- Source: mysql-dfsg-5.0 Source-Version: 5.0.51a-24+lenny4 We believe that the bug you reported is fixed in the latest version of mysql-dfsg-5.0, which is due to be installed in the Debian FTP archive: libmysqlclient15-dev_5.0.51a-24+lenny4_i386.deb to main/m/mysql-dfsg-5.0/libmysqlclient15-dev_5.0.51a-24+lenny4_i386.deb libmysqlclient15off_5.0.51a-24+lenny4_i386.deb to main/m/mysql-dfsg-5.0/libmysqlclient15off_5.0.51a-24+lenny4_i386.deb mysql-client-5.0_5.0.51a-24+lenny4_i386.deb to main/m/mysql-dfsg-5.0/mysql-client-5.0_5.0.51a-24+lenny4_i386.deb mysql-client_5.0.51a-24+lenny4_all.deb to main/m/mysql-dfsg-5.0/mysql-client_5.0.51a-24+lenny4_all.deb mysql-common_5.0.51a-24+lenny4_all.deb to main/m/mysql-dfsg-5.0/mysql-common_5.0.51a-24+lenny4_all.deb mysql-dfsg-5.0_5.0.51a-24+lenny4.diff.gz to main/m/mysql-dfsg-5.0/mysql-dfsg-5.0_5.0.51a-24+lenny4.diff.gz mysql-dfsg-5.0_5.0.51a-24+lenny4.dsc to main/m/mysql-dfsg-5.0/mysql-dfsg-5.0_5.0.51a-24+lenny4.dsc mysql-server-5.0_5.0.51a-24+lenny4_i386.deb to main/m/mysql-dfsg-5.0/mysql-server-5.0_5.0.51a-24+lenny4_i386.deb mysql-server_5.0.51a-24+lenny4_all.deb to main/m/mysql-dfsg-5.0/mysql-server_5.0.51a-24+lenny4_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 584...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Giuseppe Iuculano iucul...@debian.org (supplier of updated mysql-dfsg-5.0 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 ftpmas...@debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Fri, 04 Jun 2010 17:08:45 +0200 Source: mysql-dfsg-5.0 Binary: libmysqlclient15off libmysqlclient15-dev mysql-common mysql-client-5.0 mysql-server-5.0 mysql-server mysql-client Architecture: source all i386 Version: 5.0.51a-24+lenny4 Distribution: stable-security Urgency: high Maintainer: Debian MySQL Maintainers pkg-mysql-ma...@lists.alioth.debian.org Changed-By: Giuseppe Iuculano iucul...@debian.org Description: libmysqlclient15-dev - MySQL database development files libmysqlclient15off - MySQL database client library mysql-client - MySQL database client (metapackage depending on the latest versio mysql-client-5.0 - MySQL database client binaries mysql-common - MySQL database common files mysql-server - MySQL database server (metapackage depending on the latest versio mysql-server-5.0 - MySQL database server binaries Closes: 584400 Changes: mysql-dfsg-5.0 (5.0.51a-24+lenny4) stable-security; urgency=high . * Non-maintainer upload by the Security Team. * Fixed CVE-2010-1626: allows local users to delete the data and index files of another user's MyISAM table via a symlink attack in conjunction with the DROP TABLE command (Closes: #584400) * Fixed CVE-2010-1848: Multiple insufficient table name checks * Fixed CVE-2010-1849: DoS through oversized packets * Fixed CVE-2010-1850: Table name buffer
Bug#584911: bind9: hard-coded dependency on /usr/lib/ssl/openssl.cnf might cause trouble
* Mirko Gebauer: /usr/lib/ssl/openssl.cnf is a symlink to /etc/ssl/openssl.cnf, both provided by the package openssl. Unfortunately, on the respective machine, /etc/ssl/openssl.cnf is modified and not world-readable as it is by default after installing the openssl package. Thanks for tracking this down. I suspect that this is due to the OPENSSL_config() call, but I need to check this in a debugger to be sure. However, OpenSSL's documentation says this: OPENSSL_config() configures OpenSSL using the standard openssl.cnf configuration file name using config_name. If config_name is NULL then the default name openssl_conf will be used. Any errors are ignored. BIND uses the NULL argument, as far as I can tell. So this might be an OpenSSL bug. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#584754: marked as done (crash in dhcp_reply on last /etc/ethers entry when i18n is enabled)
Your message dated Mon, 07 Jun 2010 22:06:05 +
with message-id e1olksl-0008sm...@ries.debian.org
and subject line Bug#584754: fixed in dnsmasq 2.55-1
has caused the Debian Bug report #584754,
regarding crash in dhcp_reply on last /etc/ethers entry when i18n is enabled
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 this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
584754: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=584754
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
---BeginMessage---
Package: dnsmasq
Version: 2.53-1
Severity: serious
Tags: sid
I've got this nasty bugs, when I connect using my nokia n97
dnsmasq crashes, after a lot of trials/debugs
I've found that the place where it crashes is only a side effect
even if the code looks a bit 'obscure':
645. if (config)
646. {
647. struct dhcp_netid_list *list;
648.
649. for (list = config-netid; list; list = list-next)
650. {
651. list-list-next = netid;
652. netid = list-list;
653. }
654. }
src/rfc2131.c
list-list-next seems to be bogus but looks like it's a circular list
the bt:
0x08065aed in dhcp_reply (context=0x807fbc0, iface_name=0xb39c eth0,
int_index=2, sz=300, now=1275819570, unicast_dest=0, is_inform=0xb360,
pxe=0) a
t rfc2131.c:651
(gdb) bt
#0 0x08065aed in dhcp_reply (context=0x807fbc0, iface_name=0xb39c eth0,
int_index=2, sz=300, now=1275819570, unicast_dest=0, is_inform=0xb360, pxe=
0) at rfc2131.c:651
#1 0x08060f44 in dhcp_packet (now=1275819570, pxe_fd=0) at dhcp.c:301
#2 0x0805f1c2 in main (argc=8, argv=0xb794) at dnsmasq.c:688
(gdb) p list-list
$6 = (struct dhcp_netid *) 0x57e58955
(gdb) p list-list-next
Cannot access memory at address 0x57e58959
anyway disabling i18n the problem does not happens,
looks like canonicalise() in utils.c has something to do with the problem
the linked list code was added in 2.53
Regards
-- System Information:
Debian Release: squeeze/sid
APT prefers unstable
APT policy: (500, 'unstable'), (1, 'experimental')
Architecture: i386 (x86_64)
Kernel: Linux 2.6.26-2-xen-amd64 (SMP w/8 CPU cores)
Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968)
Shell: /bin/sh linked to /bin/dash
Versions of packages dnsmasq depends on:
ii adduser 3.112 add and remove users and groups
pn dnsmasq-base none (no description available)
ii netbase 4.41 Basic TCP/IP networking system
dnsmasq recommends no packages.
Versions of packages dnsmasq suggests:
pn resolvconfnone (no description available)
---End Message---
---BeginMessage---
Source: dnsmasq
Source-Version: 2.55-1
We believe that the bug you reported is fixed in the latest version of
dnsmasq, which is due to be installed in the Debian FTP archive:
dnsmasq-base_2.55-1_i386.deb
to main/d/dnsmasq/dnsmasq-base_2.55-1_i386.deb
dnsmasq_2.55-1.diff.gz
to main/d/dnsmasq/dnsmasq_2.55-1.diff.gz
dnsmasq_2.55-1.dsc
to main/d/dnsmasq/dnsmasq_2.55-1.dsc
dnsmasq_2.55-1_all.deb
to main/d/dnsmasq/dnsmasq_2.55-1_all.deb
dnsmasq_2.55.orig.tar.gz
to main/d/dnsmasq/dnsmasq_2.55.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 584...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Simon Kelley si...@thekelleys.org.uk (supplier of updated dnsmasq 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 ftpmas...@debian.org)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Format: 1.8
Date: Sun, 6 Jun 2010 20:33:13 +
Source: dnsmasq
Binary: dnsmasq dnsmasq-base
Architecture: source i386 all
Version: 2.55-1
Distribution: unstable
Urgency: low
Maintainer: Simon Kelley si...@thekelleys.org.uk
Changed-By: Simon Kelley si...@thekelleys.org.uk
Description:
dnsmasq- A small caching DNS proxy and DHCP/TFTP server
dnsmasq-base - A small caching DNS proxy and DHCP/TFTP server
Closes: 584754
Changes:
dnsmasq (2.55-1) unstable; urgency=low
.
* New upstream.
* Fix crash when /etc/ethers in use. (closes: #584754)
Checksums-Sha1:
1e1a684e5f0f15302ed4a5d1774f78444c9ffbdb 986 dnsmasq_2.55-1.dsc
df9924fa3ff84036d649996989b10163557e69e4 435375 dnsmasq_2.55.orig.tar.gz
c00adb125821347433ce0ce7d573209e17936d2d 16193 dnsmasq_2.55-1.diff.gz
Bug#569359: mdadm -Ds insists on /dev/md/X device presence
On Mon, 7 Jun 2010 16:25:47 +0100 Martin Michlmayr t...@cyrius.com wrote: * martin f krafft madd...@debian.org [2010-05-26 10:31]: also sprach Neil Brown ne...@suse.de [2010.05.26.1016 +0200]: The most likely explanation for this is that /var/run/mdadm/map existed and contained and entry for 'md0' declaring that it could be found at /dev/md/0. Normally mdadm will write such a name there when auto-assembling an array, then udev will notice that the array has appeared, will use mdadm to find the path name in /var/run/mdadm/map and will create the node in /dev. So it would seem that udev is not running, but /dev/.udev exists. If udev was running, it would have created /dev/md/0. If /dev/.udev didn't exist, then mdadm would have created it when assembling the array. If this is correct, udev is not running but /dev/.udev exists, then you can force mdadm to still create the device with export MDADM_NO_UDEV=1 Martin, could you please investigate this further? I don't have much experience with d-i, nor really the time to attain that right now. Thanks for your explanation, Neal. So here's a description of what's going on: We boot into Debian installer. The installer creates a RAID1 device with: mdadm --create /dev/md0 --auto=yes [...] udev is running. /dev/md0 exists. /dev/md/0 does not exist. There's a file /var/run/map (not /var/run/mdadm/map) which contains this: md0 1.2 dcfdb5af:3b385a1e:def86b24:09a2527f /dev/md0 When I compile mdadm from source, it creates /var/run/mdadm/map. When I use Debian's mdadm, it creates /var/run/map as you say. Something is broken there. Otherwise everything seems OK so far. When I run: mdadm --examine --scan --config=partitions I get: ARRAY /dev/md/0 metadata=1.2 UUID=afb5fddc:1e5a383b:246bf8de:7f52a209 name=debian:0 i.e. the /dev/md/0 form. (Also note that that the UUID in the map file is different to that reported by --examine --scan; not sure why.) You use --examine like this? You know the array you have just created. You know the name you want to call it (/dev/md0). Why not mdadm --detail --brief /dev/md0 ?? It gives a name like /dev/md/foo because it is using 1.x (1.2 in this case) metadata. 1.x metadata stores and array name, not a number. In that case the name just happens to be numerical. If the name was actually 'foo', it would be wrong to report /dev/mdfoo, but correct to report /dev/md/foo. With 1.x metadata you get /dev/md/name With 0.90 metadata you get /dev/mdNUM After creating the RAID0 and formating it, Debian installer will then install Debian to disk (in a chroot). At some point, mdadm is installed in the chroot. /dev from the real system is bind mounted in the chroot. Debian's mdadm sees that there's no mdadm config file and tries to generate one. It runs: mdadm --examine --scan --config=partitions and writes this to /etc/mdadm/mdadm.conf. The output is: ARRAY /dev/md/0 metadata=1.2 UUID=afb5fddc:1e5a383b:246bf8de:7f52a209 name=debian:0 There's no map file in /var/run at this point. /dev/md0 exists but /dev/md/0 does not. Debian then generates a ramdisk. It looks at /etc/mdadm/mdadm.conf and sees that the RAID device is /dev/md/0 and then does: mdadm --detail /dev/md/0 to determine the RAID level. This fails because /dev/md/0 does not exist. As a consequence, the ramdisk won't contain the RAID modules and will fail to boot. Maybe we need to get mdadm --assemble, if it finds that the array is already assembled, to create the device named in mdadm.conf anyway. i.e. if the array mentioned in mdadm.conf already exists in 'map' with a different name, mdadm --assemble just creates the new name. There is another context that came up recently where that would be helpful. Alternately, you could just mdadm -Ir this rebuilds the 'map' file using the same name that mdadm -E would use, and then tickles udev so that it creates the right names in /dev... Almost. I'm not sure it uses exactly the same names as -E. It would be safer to use mdadm -As to ensure all arrays are assembled, then mdadm -Ds to create mdadm.conf ... but why do you even want to create mdadm.conf ??? Maybe a deeper rethink is needed here. So my questions (the first one primarily for Neil, the second one for madduck): - Why does mdadm --examine --scan output the /dev/md/X form rather than /dev/mdX when no config and map file exists. Is /dev/md/X prefered over /dev/mdX? If so, maybe Debian installer should use mdadm --create /dev/md/X instead of mdadm --create /dev/mdX ? I think I have explained above. It is a metadata version difference. - Why is /dev/md/X not created? Well, I guess it's not generated because we use /dev/mdX and not even the map file mentions /dev/md/X but given that mdadm --examine --scan prefers /dev/md/X maybe we should
Bug#505609: new lilo package maintainer? (was lilo removal in squeeze or please test grub2)
[Dropped the @lists.debian.org from Cc] * Stephen Powell zlinux...@wowway.com [Mon Jun 07, 2010 at 11:37:57AM -0400]: On Mon, 07 Jun 2010 10:33:52 -0400 (EDT), Holger Levsen wrote: thanks for stepping up maintaining lilo in Debian! I hope you'll manage this well. Um, thanks; but I don't understand the reassignment of bug number 505609 to package initramfs-tools. If you read my previous posts to the bug log, it is clear that this problem started with a change to the maintainer scripts between Etch and Lenny. Please read my posts again carefully. Then consider whether this is really a bug in initramfs-tools or a bug in the kernel maintainer scripts. [...] ACK. I don't think this is an i-t issue. Any objections against reassigning back to linux-2.6? regards, -mika- signature.asc Description: Digital signature
Bug#584972: opensync-plugin-syncml: opensync doesn't find syncml plugin
Package: opensync-plugin-syncml Version: 0.39-1 Severity: grave Tags: sid Justification: renders package unusable Hi, after installing opensync-plugin-symcml, it doesn't show up in multisync0.90. It also doesn't show up in msynctool --listplugins. -- System Information: Debian Release: squeeze/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: i386 (i686) Kernel: Linux 2.6.32-3-686 (SMP w/2 CPU cores) Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages opensync-plugin-syncml depends on: ii libc6 2.11.1-2 Embedded GNU C Library: Shared lib ii libglib2.0-02.24.1-1 The GLib library of C routines ii libopensync1exp70.39-4 Synchronisation framework for emai ii libsyncml2 0.5.4-2 SyncML protocol library ii libxml2 2.7.7.dfsg-2 GNOME XML library opensync-plugin-syncml recommends no packages. opensync-plugin-syncml suggests no packages. -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#583187: aMSN shouldn't compile with v4l support on non linux archs
On Thu, May 27, 2010 at 01:56:01PM -0430, Muammar El Khatib wrote: Hi Laurent, 2010/5/26 Laurent Bigonville bi...@debian.org: Package: amsn Version: 0.98.3-1 Severity: Serious Hi, aMSN shouldn't compile with v4l support on non linux archs. This prevents building on kfreebsd-* Thanks for reporting, I am working on that from the message sent by Peter Green. Attached debdiff makes amsn build on kFreeBSD again. Sjoerd -- Round Numbers are always false. -- Samuel Johnson diff -u amsn-0.98.3/debian/control amsn-0.98.3/debian/control --- amsn-0.98.3/debian/control +++ amsn-0.98.3/debian/control @@ -2,7 +2,7 @@ Section: x11 Priority: optional Maintainer: Muammar El Khatib muammarelkha...@gmail.com -Build-Depends: debhelper (= 6), tcl8.5-dev, tk8.5-dev, dpatch, libpng12-dev, libjpeg62-dev, libnice-dev, libgstreamer-plugins-base0.10-dev, libgstfarsight0.10-dev (= 0.0.9), libv4l-dev, libgupnp-1.0-dev, libgupnp-igd-1.0-dev +Build-Depends: debhelper (= 6), tcl8.5-dev, tk8.5-dev, dpatch, libpng12-dev, libjpeg62-dev, libnice-dev, libgstreamer-plugins-base0.10-dev, libgstfarsight0.10-dev (= 0.0.9), libv4l-dev [!kfreebsd-i386 !kfreebsd-amd64 !hurd-i386], libgupnp-1.0-dev, libgupnp-igd-1.0-dev Standards-Version: 3.8.4 Homepage: http://amsn.sourceforge.net/ diff -u amsn-0.98.3/debian/changelog amsn-0.98.3/debian/changelog --- amsn-0.98.3/debian/changelog +++ amsn-0.98.3/debian/changelog @@ -1,3 +1,14 @@ +amsn (0.98.3-1.1) UNRELEASED; urgency=low + + * Non-maintainer upload. + * debian/patches/06_recognize_kfreebsd.patch.dpatch ++ Added. Make configure recognize kFreeBSD as a BSD + * debian/rules ++ Only special case the bits that are actually linux only ++ Don't build-depend on libv4l-dev on GNU/KFreeBSD (Closes: #583187) + + -- Sjoerd Simons sjo...@debian.org Tue, 08 Jun 2010 02:24:08 +0100 + amsn (0.98.3-1) unstable; urgency=medium * New upstream release. diff -u amsn-0.98.3/debian/rules amsn-0.98.3/debian/rules --- amsn-0.98.3/debian/rules +++ amsn-0.98.3/debian/rules @@ -98,21 +98,21 @@ # .so files go in /usr/lib -ifeq ($(DEB_HOST_ARCH_OS),linux) - # The following is Linux-only, see the FOUND_OS detection in Makefile.in mv $(CURDIR)/debian/amsn-data/usr/share/amsn/utils/webcamsn $(CURDIR)/debian/amsn/usr/lib/amsn/utils mv $(CURDIR)/debian/amsn-data/usr/share/amsn/amsn $(CURDIR)/debian/amsn/usr/share/amsn mv $(CURDIR)/debian/amsn-data/usr/share/amsn/amsn-remote $(CURDIR)/debian/amsn/usr/share/amsn mv $(CURDIR)/debian/amsn-data/usr/share/amsn/amsn-remote-CLI $(CURDIR)/debian/amsn/usr/share/amsn mv $(CURDIR)/debian/amsn-data/usr/share/amsn/utils/TkCximage/* $(CURDIR)/debian/amsn/usr/lib/amsn/utils/TkCximage - mv $(CURDIR)/debian/amsn-data/usr/share/amsn/utils/linux $(CURDIR)/debian/amsn/usr/lib/amsn/utils mv $(CURDIR)/debian/amsn-data/usr/share/amsn/utils/tcl_siren $(CURDIR)/debian/amsn/usr/lib/amsn/utils mv $(CURDIR)/debian/amsn-data/usr/share/amsn/utils/asyncresolver $(CURDIR)/debian/amsn/usr/lib/amsn/utils mv $(CURDIR)/debian/amsn-data/usr/share/amsn/utils/farsight $(CURDIR)/debian/amsn/usr/lib/amsn/utils mv $(CURDIR)/debian/amsn-data/usr/share/amsn/utils/tclISF $(CURDIR)/debian/amsn/usr/lib/amsn/utils mv $(CURDIR)/debian/amsn-data/usr/share/amsn/utils/gupnp $(CURDIR)/debian/amsn/usr/lib/amsn/utils - rm -f $(CURDIR)/debian/amsn-data/usr/share/amsn/utils/tcl_siren/src/*.o +ifeq ($(DEB_HOST_ARCH_OS),linux) + # The following is Linux-only, see the FOUND_OS detection in Makefile.in + mv $(CURDIR)/debian/amsn-data/usr/share/amsn/utils/linux $(CURDIR)/debian/amsn/usr/lib/amsn/utils endif + rm -f $(CURDIR)/debian/amsn-data/usr/share/amsn/utils/tcl_siren/src/*.o # Documentation files go in /usr/share/doc/amsn cp -f $(CURDIR)/docs/* \ diff -u amsn-0.98.3/debian/patches/00list amsn-0.98.3/debian/patches/00list --- amsn-0.98.3/debian/patches/00list +++ amsn-0.98.3/debian/patches/00list @@ -5,0 +6 @@ +06_recognize_kfreebsd.patch.dpatch only in patch2: unchanged: --- amsn-0.98.3.orig/debian/patches/06_recognize_kfreebsd.patch.dpatch +++ amsn-0.98.3/debian/patches/06_recognize_kfreebsd.patch.dpatch @@ -0,0 +1,31 @@ +#! /bin/sh /usr/share/dpatch/dpatch-run +## 06_recognize_kfreebsd.patch.dpatch by sjo...@debian.org +## +## All lines beginning with `## DP:' are a description of the patch. +## DP: No description. + +...@dpatch@ +diff -urNad '--exclude=CVS' '--exclude=.svn' '--exclude=.git' '--exclude=.arch' '--exclude=.hg' '--exclude=_darcs' '--exclude=.bzr' amsn-0.98.3~/configure amsn-0.98.3/configure +--- amsn-0.98.3~/configure 2010-03-06 22:29:12.0 + amsn-0.98.3/configure 2010-06-08 02:17:18.385084460 +0100 +@@ -2255,7 +2255,7 @@ + Linux) + FOUND_OS=linux + ;; +- OpenBSD | FreeBSD | NetBSD) ++ *BSD) + # *BSD has important stuff (from ports) + # in /usr/local ... + CFLAGS=$CFLAGS -I/usr/local/include -L/usr/local/lib +diff -urNad '--exclude=CVS' '--exclude=.svn' '--exclude=.git' '--exclude=.arch'
Bug#584985: lwjgl: FTBFS: /usr/bin/ld: cannot find -ljawt
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Source: lwjgl Version: 2.4.2+dfsg-2 Severity: serious Justification: FTBFS Hi, your package FTBFS on some architectures. - - compile: compiledeb: [mkdir] Created dir: /build/buildd-lwjgl_2.4.2+dfsg-2-armel-Q8i1if/lwjgl-2.4.2+dfsg/bin/lwjgl/deb [apply] /usr/bin/ld: cannot find -ljawt [apply] collect2: ld returned 1 exit status BUILD FAILED /build/buildd-lwjgl_2.4.2+dfsg-2-armel-Q8i1if/lwjgl-2.4.2+dfsg/build.xml:366: The following error occurred while executing this line: /build/buildd-lwjgl_2.4.2+dfsg-2-armel-Q8i1if/lwjgl-2.4.2+dfsg/build.xml:390: The following error occurred while executing this line: /build/buildd-lwjgl_2.4.2+dfsg-2-armel-Q8i1if/lwjgl-2.4.2+dfsg/platform_build/linux_ant/build.xml:72: The following error occurred while executing this line: /build/buildd-lwjgl_2.4.2+dfsg-2-armel-Q8i1if/lwjgl-2.4.2+dfsg/platform_build/linux_ant/build.xml:143: apply returned: 1 Total time: 2 minutes 6 seconds make[1]: *** [override_dh_auto_build] Error 1 make: *** [build] Error 2 - - Full build logs(armel): https://buildd.debian.org/fetch.cgi?pkg=lwjgl;ver=2.4.2%2Bdfsg-2;arch=armel;stamp=1275971087 Currentry, armel, powerpc and sh4 has this problem. The architecture name is gotten by using dpkg-architecture. However, the directory in which libjawt is installed and debian of architecture name are not corresponding. armel uses arm, powerpc uses ppc and sh4 uses sh. Please check your package. Best regards, Nobuhiro - -- Nobuhiro Iwamatsu -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.10 (GNU/Linux) iEYEARECAAYFAkwN0FgACgkQQSHHQzFw6+ln8ACgqDjd0UVw4gKWxaZwFmXqyFlw 6SkAn3kv74JTF34SDnCsd2tOallGKljK =cIw+ -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#580527: marked as done (insighttoolkit: FTBFS on many architectures, build-depend on unavailable default-jdk)
Your message dated Tue, 8 Jun 2010 00:41:21 -0500 with message-id 20100608054121.ga28...@sumost.ca and subject line Re: Internal Control has caused the Debian Bug report #580527, regarding insighttoolkit: FTBFS on many architectures, build-depend on unavailable default-jdk 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 this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 580527: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=580527 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: insighttoolkit Version: 3.18.0-1 Severity: serious insighttoolkit 3.18 was uploaded without coordination with the release team, while introducing a new library transition. There are a few problems with that: - igstk is a reverse dependency of both insighttoolkit and vtk, which means that now we have entangled transitions, which means it's going to be even more difficult to get those packages and their dependencies in squeeze - new insighttoolkit FTBFS on many architectures, see https://buildd.debian.org/status/package.php?p=insighttoolkit - new insighttoolkit build-depends on default-jdk = 1.6-34, while 3 architectures have 1.5-36, which means it's not going to get built there Please fix these issues ASAP, and consider not doing it again. Cheers, Julien signature.asc Description: Digital signature ---End Message--- ---BeginMessage--- So I closed the bug with upload 3.18.0-2, then I see this less than useful message. On Fri, May 07, 2010 at 02:27:07PM +, Debbugs Internal Request wrote: # A New Hope # A long time ago, in a galaxy far, far away # something happened. # # Magically this resulted in the following # action being taken, but this fake control # message doesn't tell you why it happened # # The action: # Bug No longer marked as fixed in versions insighttoolkit/3.18.0-2 and reopened. thanks # This fakemail brought to you by your local debbugs # administrator Anyway, the root cause of things not fixed in -2 was in gccxml and is now fixed, so closing again. -S signature.asc Description: Digital signature ---End Message---
