Bug#692652: unblock: xcache/2.0.0-3
Hi Dne Tue, 13 Nov 2012 21:59:10 +0100 intrigeri intrig...@boum.org napsal(a): The upload fixes bug #690409 (wrong handling of conffile move), I think this unblock request should wait until it's clarified on #690409 that the absolute extension path is updated or .dpkg-dist appears through every supported upgrade path. I will upload 2.0.0-4 soon with same fix as was used for xdebug, diff attached. -- Michal Čihař | http://cihar.com | http://blog.cihar.com commit 8b83be8abad108f41ac0348b8a16727ba0bb6bdc Author: Michal ÄihaÅ ni...@debian.org Date: Wed Nov 14 08:55:20 2012 +0100 Rewrite configuration to correct path to extension on upgrade (Closes: #690409). diff --git a/debian/changelog b/debian/changelog index 45a86ba..d266c92 100644 --- a/debian/changelog +++ b/debian/changelog @@ -1,3 +1,10 @@ +xcache (2.0.0-4) unstable; urgency=low + + * Rewrite configuration to correct path to extension on upgrade +(Closes: #690409). + + -- Michal ÄihaÅ ni...@debian.org Wed, 14 Nov 2012 08:57:03 +0100 + xcache (2.0.0-3) unstable; urgency=low * Do not include full path to extension in xcache.so. diff --git a/debian/php5-xcache.postinst b/debian/php5-xcache.postinst index ed10958..a42723f 100755 --- a/debian/php5-xcache.postinst +++ b/debian/php5-xcache.postinst @@ -9,6 +9,12 @@ fi dpkg-maintscript-helper mv_conffile \ /etc/php5/conf.d/xcache.ini /etc/php5/mods-available/xcache.ini 2.0.0-2 php5-xcache -- $@ +# Verify path in ini file is correct +EXT_DIR= +if [ -n $EXT_DIR ]; then +sed -e s@\(zend_extension=\).*\(xcache.so\)@\1$EXT_DIR/\2@g -i /etc/php5/mods-available/xcache.ini +fi + #DEBHELPER# exit 0 diff --git a/debian/rules b/debian/rules index d7fdf69..0ad9f73 100755 --- a/debian/rules +++ b/debian/rules @@ -24,6 +24,7 @@ build-indep: build-stamp build-stamp: dh build sed s#@EXTDIR@#`php-config5 --extension-dir`# debian/xcache.ini.in debian/xcache.ini + sed s@EXT_DIR=.*@EXT_DIR=`php-config5 --extension-dir`@ -i debian/php5-xcache.postinst touch $@ override_dh_auto_configure: signature.asc Description: PGP signature
Bug#691148: [Pkg-virtualbox-devel] Bug#691148: Bug#691148: Please package virtualbox 4.2.2
On Tuesday 13 November 2012 17:55:14 Felix Geyer wrote: On 12.11.2012 12:19, Frank Mehnert wrote: It is correct that we switched from bcc to Open Watcom to compile the PC BIOS as well as the VGA BIOS. The reason is indeed that bcc is unmaintained since years, has many bugs and creates code which is far away from being optimized. And we didn't find an appropriate alternative to Open Watcom. But it is not true that Open Watcom is required to build the BIOS of VirtualBox. If Open Watcom is not available, an alternative Assembler file can be used to create the BIOS. See here: https://www.virtualbox.org/browser/vbox/trunk/src/VBox/Devices/BiosCommon Code Right, but Open Watcom is required to build the BIOS from source (preferred form for modification). That makes VirtualBox a candidate for the Debian contrib repository as it is free but requires non-free software to build from source. When the package is in contrib the assembler file could be used to build the BIOS. In my opinion this depends on the definition of the term source code. The VirtualBox source code tarball ships two alternative variants of the BIOS source code: The first variant is C code mixed with Assembler code (in src/VBox/Devices/PC/BIOS/* and src/VBox/Devices/Graphics/BIOS/*). The second variant is pure Assembler code which can be found in src/VBox/Devices/PC/BIOS/VBoxBiosAlternative.asm and src/VBox/Devices/Graphics/BIOS/VBoxVgaBiosAlternative.asm Both variants are part of the source code tarball, and the second variant allows it to build VirtualBox even if Open Watcom is not available. It should not matter that the second variant is generated from the first variant because that generation is done by the VirtualBox team and we ensure that the 2nd variant will produce the same object code as the 1st variant. Kind regards, Frank -- Dr.-Ing. Frank Mehnert | Software Development Director, VirtualBox ORACLE Deutschland B.V. Co. KG | Werkstr. 24 | 71384 Weinstadt, Germany Hauptverwaltung: Riesstr. 25, D-80992 München Registergericht: Amtsgericht München, HRA 95603 Geschäftsführer: Jürgen Kunz Komplementärin: ORACLE Deutschland Verwaltung B.V. Hertogswetering 163/167, 3543 AS Utrecht, Niederlande Handelsregister der Handelskammer Midden-Niederlande, Nr. 30143697 Geschäftsführer: Alexander van der Ven, Astrid Kepper, Val Maher signature.asc Description: This is a digitally signed message part.
Bug#689382: chicken-bin: New upstream version: 4.8.0
On Tue, Nov 13, 2012 at 1:17 AM, Ivan Raikov rai...@oist.jp wrote: Hello, It has been now some time since Chicken 4.8.0 was released. This version appears quite stable, and including it in Debian should not cause problems. Please let me know if the Chicken community can help with anything. Thanks, -Ivan Raikov Hello, I plan to release a 4.8.0 package in a few days, thanks for your interest. Regards, Davide -- Davide Puricelli http://www.puricelli.info | http://www.debian.org Time looked like snow dropping silently into a black room -- Ray Bradbury -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#693197: RFS: mozilla-gnome-keyring/0.6.5-1
Package: sponsorship-requests Severity: normal Dear mentors, I am looking for a sponsor for my package mozilla-gnome-keyring * Package name: mozilla-gnome-keyring Version : 0.6.5-1 This is an update to an already existing package: http://packages.debian.org/source/experimental/mozilla-gnome-keyring It builds those binary packages: xul-ext-gnome-keyring - Store mozilla passwords in GNOME Keyring. To access further information about this package, please visit the following URL: http://mentors.debian.net/package/mozilla-gnome-keyring Alternatively, one can download the package with dget using this command: dget -x http://mentors.debian.net/debian/pool/main/m/mozilla-gnome-keyring/mozilla-gnome-keyring_0.6.5-1.dsc Changes since the last upload: * Upload to unstable. * Fix FTBFS where the platform name contains a /. (Closes: #689189) * Fix Vcs-* entries in debian/contol to point to the correct branch. (Closes: #689165) Regards, Ximin Luo -- System Information: Debian Release: wheezy/sid APT prefers testing APT policy: (990, 'testing'), (500, 'unstable'), (500, 'stable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.5-trunk-amd64 (SMP w/4 CPU cores) Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#693199: RFS: status-4-evar/0.2012.07.08.17-1
Package: sponsorship-requests Severity: normal I am looking for a sponsor to update my package status-4-evar Old package: http://packages.debian.org/source/sid/status-4-evar New version: 0.6.5-1 It builds those binary packages: xul-ext-status4evar - Status bar widgets and progress indicators for Firefox 4+ To access further information about this package, please visit the following URL: http://mentors.debian.net/package/status-4-evar Alternatively, one can download the package with dget using this command: dget -x http://mentors.debian.net/debian/pool/main/s/status-4-evar/status-4-evar_0.2012.07.08.17-1.dsc Changes since the last upload: * New upstream release. * Update to latest Standards-Version Regards, Ximin Luo -- System Information: Debian Release: wheezy/sid APT prefers testing APT policy: (990, 'testing'), (500, 'unstable'), (500, 'stable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.5-trunk-amd64 (SMP w/4 CPU cores) Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#693198: ITP: ec2debian-build-ami is a bunch of scripts which creates Debian images for use in clouds.
Package: wnpp Severity: wishlist Owner: Marcin Kulisz (kuLa) deb...@kulisz.net * Package name: ec2debian-build-ami Version : b72146d3git Upstream Author : Eric Hammond ehamm...@thinksome.com and Anders Ingemann and...@ingemann.de * URL : https://github.com/andsens/ec2debian-build-ami * License : (AL-2.0) Programming Lang: (Shell) Description : ec2debian-build-ami is a bunch of scripts which creates Debian images for use in clouds. ec2debian-build-ami is a bunch of scripts which creates a vanilla debian squeeze machine images for use in clouds. no latent logfiles no bash history or even apt package cache. This software creates fully operational images for Amazons EC2. Those images suppose to work on OpenStack as well as on other cloud solutions which are sharing API with the previous 2. This tool is utilising euca2ools. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#693176: Please try rebuilding imagemagick on sparc (was Bug#693176: imagemagick: ftbfs on sparc)
severity 693176 normal retitle 693176 Random build failures on sparc thanks On Wed, Nov 14, 2012 at 1:58 AM, Michael Gilbert mgilb...@debian.org wrote: imagemagick fails to build on sparc. convert fails: # make xpm /usr/bin/convert /build/buildd-imagemagick_6.7.7.10-5-sparc-QgV24K/imagemagick-6.7.7.10/debian/display.im6.svg -resize 32x32 \ /build/buildd-imagemagick_6.7.7.10-5-sparc-QgV24K/imagemagick-6.7.7.10/debian/display.im6.xpm *** glibc detected *** convert: free(): invalid pointer: 0x7127c008 *** This is a sporadic problem for which we have no solution at that time (nor even the slightest clue !), save bothering the wb-team to ask them to gb. I'm therefore downgrading the bug severity. Debian WB team, could you please try rebuilding the latest imagemagick on sparc (if possible trying another buildd) ? gb imagemagick_8:6.7.7.10-5 . sparc Many thanks, Vincent -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#690575: python-coverage for Python 3
(Re-sending to include the bug report this time, so progress on this issue is visible.) On 17-Oct-2012, Barry Warsaw wrote: I'm wondering what your feelings are to adjusting the d/rules file to be a little more like what's recommended here: http://wiki.debian.org/Python/LibraryStyleGuide I have made the suggested changes, I think. Please update your checkout of the development branch for ‘python-coverage.debian’. With the changes I've made, I'm getting a failure when trying to build the debug package; the relevant part of the build log is attached. -- \己所不欲、勿施于人。 | `\(What is undesirable to you, do not do to others.) | _o__)—孔夫子 Confucius (551 BCE – 479 BCE) | Ben Finney b...@benfinney.id.au python3.2 setup.py build Downloading http://pypi.python.org/packages/source/d/distribute/distribute-0.6.13.tar.gz Extracting in /tmp/tmpa0kvyp Now working in /tmp/tmpa0kvyp/distribute-0.6.13 Building a Distribute egg in /tmp/buildd/python-coverage-3.4 creating build creating build/src creating build/src/docs creating build/src/docs/_templates creating build/src/docs/_theme creating build/src/docs/_theme/nature creating build/src/docs/_theme/nature/static creating build/src/docs/build creating build/src/docs/build/html creating build/src/docs/build/html/_sources creating build/src/docs/build/html/_static creating build/src/setuptools creating build/src/setuptools/command creating build/src/setuptools/tests creating build/src/tests creating build/src/tests/shlib_test copying setuptools/sandbox.py - build/src/setuptools copying setuptools/archive_util.py - build/src/setuptools copying setuptools/__init__.py - build/src/setuptools copying setuptools/extension.py - build/src/setuptools copying setuptools/package_index.py - build/src/setuptools copying setuptools/dist.py - build/src/setuptools copying setuptools/depends.py - build/src/setuptools copying setuptools/command/egg_info.py - build/src/setuptools/command copying setuptools/command/bdist_wininst.py - build/src/setuptools/command copying setuptools/command/bdist_egg.py - build/src/setuptools/command copying setuptools/command/sdist.py - build/src/setuptools/command copying setuptools/command/build_py.py - build/src/setuptools/command copying setuptools/command/install.py - build/src/setuptools/command copying setuptools/command/saveopts.py - build/src/setuptools/command copying setuptools/command/easy_install.py - build/src/setuptools/command copying setuptools/command/register.py - build/src/setuptools/command copying setuptools/command/__init__.py - build/src/setuptools/command copying setuptools/command/install_lib.py - build/src/setuptools/command copying setuptools/command/rotate.py - build/src/setuptools/command copying setuptools/command/develop.py - build/src/setuptools/command copying setuptools/command/alias.py - build/src/setuptools/command copying setuptools/command/bdist_rpm.py - build/src/setuptools/command copying setuptools/command/install_egg_info.py - build/src/setuptools/command copying setuptools/command/setopt.py - build/src/setuptools/command copying setuptools/command/install_scripts.py - build/src/setuptools/command copying setuptools/command/upload.py - build/src/setuptools/command copying setuptools/command/build_ext.py - build/src/setuptools/command copying setuptools/command/upload_docs.py - build/src/setuptools/command copying setuptools/command/test.py - build/src/setuptools/command copying setuptools/tests/test_packageindex.py - build/src/setuptools/tests copying setuptools/tests/test_develop.py - build/src/setuptools/tests copying setuptools/tests/test_easy_install.py - build/src/setuptools/tests copying setuptools/tests/server.py - build/src/setuptools/tests copying setuptools/tests/test_resources.py - build/src/setuptools/tests copying setuptools/tests/test_upload_docs.py - build/src/setuptools/tests copying setuptools/tests/test_build_ext.py - build/src/setuptools/tests copying setuptools/tests/__init__.py - build/src/setuptools/tests copying setuptools/tests/doctest.py - build/src/setuptools/tests copying setuptools/tests/test_sandbox.py - build/src/setuptools/tests copying setuptools/tests/win_script_wrapper.txt - build/src/setuptools/tests copying setuptools/gui.exe - build/src/setuptools copying setuptools/cli.exe - build/src/setuptools copying tests/test_distribute_setup.py - build/src/tests copying tests/install_test.py - build/src/tests copying tests/manual_test.py - build/src/tests copying tests/shlib_test/test_hello.py - build/src/tests/shlib_test copying tests/shlib_test/setup.py - build/src/tests/shlib_test copying tests/shlib_test/hello.c - build/src/tests/shlib_test copying tests/shlib_test/hellolib.c - build/src/tests/shlib_test copying tests/shlib_test/hello.pyx - build/src/tests/shlib_test copying tests/api_tests.txt - build/src/tests RefactoringTool: Skipping implicit fixer: buffer RefactoringTool: Skipping
Bug#693200: RFS: tree-style-tab/0.14.2012081101-1
Package: sponsorship-requests Severity: normal I am looking for a sponsor to update my package tree-style-tab Old package: http://packages.debian.org/source/sid/tree-style-tab New version: 0.14.2012081101-1 It builds those binary packages: xul-ext-treestyletab - Show tabs like a tree To access further information about this package, please visit the following URL: http://mentors.debian.net/package/tree-style-tab Alternatively, one can download the package with dget using this command: dget -x http://mentors.debian.net/debian/pool/main/t/tree-style-tab/tree-style-tab_0.14.2012081101-1.dsc Changes since the last upload: * New upstream release. * Update to latest Standards-Version Regards, Ximin Luo -- System Information: Debian Release: wheezy/sid APT prefers testing APT policy: (990, 'testing'), (500, 'unstable'), (500, 'stable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.5-trunk-amd64 (SMP w/4 CPU cores) Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#693040: libav: Strange build failure on several archs
Am 13.11.2012 16:45, schrieb Reinhard Tartler: The problem is upstream and has been identified now. Reverting upstream commit 468ea9d5b14f92fe61f47f034e67066f65163f5f seems to fix the issue, albeit a better solution is currently being worked on. Good to know that you've succeeded to narrow down the problem. But how could it ever build on the other archs if the symbol in question isn't exported anymore, why does it only break on selected archs? - Fabian -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#689381: X: Login screen fails to appear, though you can still interact with it
Dear Paul I see. Thanks. Another thing, do you see the mouse cursor? I have just experienced the problem again. After successfully booting up my notebook I am presented with the desktop background but no visible login screen. There does not appear to be a mouse cursor on the screen, but I can still log in by pressing enter and then entering my password followed by enter again. The computer appears to log in normally at this point. When this happens and you log in into GNOME and log out. Does the login window appear then? Yes. Next time this happens could you please try the following and report back. 1. Switch to the virtual terminal with Ctrl + Alt + F1. 2. Switch back with Ctrl + Alt + F7. Did something change? No noticeable change. Then, 1. Switch again to tty1 with Ctrl + Alt + F1. 2. Log in. 3. Enter `sudo service gdm3 restart` 4. Back to tty7 with Ctrl + Alt + F1. Any difference? No noticeable change, everything works as per usual. Also please attach the output under system information of `reportbug gdm` or `reportbug gdm3`. My apologies but I do not know what you are referring to? First run `aptitude search gdm` and paste the output. I ran 'aptitude search gdm' from a terminal shortly after experiencing the problem with the log in screen. p gdm - GNOME Display Manager p gdm-themes - Themes for the GNOME Display Manager i gdm3- Next generation GNOME Display Manager p gdmap - Tool to visualize diskspace p kdm-gdmcompat - Provide basic gdm functionality to systems p liblcgdm-dev- LCG Data Management common development fil p liblcgdm1 - LCG Data Management common libraries Kind regards Gregory
Bug#693186: go tool dist fails
JFTR this will be fixed after the freeze is over and Debian has released next stable. O. On Wed, Nov 14, 2012 at 5:12 AM, James Henstridge ja...@jamesh.id.au wrote: Package: golang Version: 2:1.0.2-2 I reproduced this bug on Ubuntu (https://bugs.launchpad.net/ubuntu/+source/golang/+bug/1076017), but it looks like the package was imported from Debian unmodified so thought you'd like to know. Some Go packages with non-default build systems use the command go tool dist env to discover information about the Go installation. Unfortunately this fails with the 2:1.0.2-2 package for a few reasons as described in the Launchpad bug report: 1. The dist tool tries to verify that GOROOT is correct by checking that $GOROOT/include/u.h exists (it doesn't actually use the file though). This doesn't appear to be included by any of the golang packages. 2. If I create $GOROOT/include/u.h, it still fails when it tries to determine the version number by checking for Mercurial tags in $GOROOT, which also fails. It seems that it only falls back to running hg if $GOROOT/VERSION does not exist. So creating that file with the appropriate content gets things working. So fixing this involves the following steps: 1. either install /usr/lib/go/include/u.h, or modify the dist tool to check for some other file that should appear in $GOROOT. 2. Make the golang package include /usr/lib/go/VERSION Hope this helps. James. -- Ondřej Surý ond...@sury.org -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#685251: [Openstack-devel] Fixing Debian bug #685251 for the ryu plugin in Openstack
On 11/14/2012 05:30 AM, Ola Lundqvist wrote: Hi Thomas and Julien The 2012.1-6 upload was done before the freeze That isn't right. The freeze date was the 30th of June, while the package was uploaded by Loic on the 6th of July. See the PTS: http://packages.qa.debian.org/q/quantum.html Though your changes were committed to our Git on Alioth before the freeze (on the 28th of June). and the plan was to have it included in testing before the freeze. Apparently that did not happen. I was under the impression that the freeze would be to uploads after the freeze, not to the packages that had not yet done the transition. Apparently I was wrong, and if that have cause this problem, I'm sorry for that. You were right, but the package was uploaded *after* the freeze. Which is the sole reason why it didn't migrate to Wheezy (well, that, and the fact you didn't ask for an unblock...). We did not have any bug report about the issues for that change. Instead I did those changes in order to solve problems that were similar to issues in other packages. It was more of a cleanup work in order to avoid bug reports in the future. We did have issues with the conflicts, replaces, breaks in other packages and if I remember correctly they were important also for this package. It is some time since I did this so I do not remember all the details. I do agree that the provides/conflicts/replaces/breaks fixes should be in Wheezy. I think the 2012.1-6 upload was a good thing for the package, especially for upgrade from earlier versions. That is however not such a big problem for this release as it has not been part of stable before. It may be an issue for later releases though. From a release team perspective I understand that you do not want large last minute changes to packages. I can not motivate the change to be that strong to be forced in. If you want I can make a proposed patch based on the changes Thomas made for 2012.1-7 and void the changes for 2012.1-6. YES! Please do so and deal with the unblock for your changes. :) It by the way would be nice and save time if the release team was telling what part of the changes are rejected and for what reason. Cheers, Thomas -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#693201: RFP: guile-reader -- framework for building readers for Guile
Package: wnpp Severity: wishlist * Package name : guile-reader Version : 0.6 * URL : http://savannah.nongnu.org/projects/guile-reader/ * License : GPL3 Description : Build readers for GNU Guile (http://www.gnu.org/software/guile/) The guile-reader is a dep of the document preparation framework Skribilo, which I intent to package (cf. http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=610908). Greetings, Daniel Stender -- http://www.danielstender.com/granthinam/ GPG key ID: 1654BD9C -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#657987: icedove: exception when trying to setup account
Hello Carsten, This is a clean fresh profile, no extensions installed at the moment. I was not able to reproduce exactly this error today but get instead directly the Incoming server already exists. error for the gdb profile. I am setting up a new profile with my @gmail.com adress. I am getting this error: [Thread 0x7fffcdbff700 (LWP 12290) exited] -- Exception object -- + (string) The config file XML does not contain an email account configuration. * -- Exception object -- + _message (string) 'Service Unavailable' + stack (string) 395 chars + code (number) 503 + uri (string) 'http://autoconfig.gmail.com/mail/config-v1.1.xml' + message (string) 'Service Unavailable' + toString (function) 3 lines * -- Stack Trace -- Exception(Service Unavailable)@chrome://messenger/content/accountcreation/util.js:189 ServerException(Service Unavailable,503,http://autoconfig.gmail.com/mail/config-v1.1.xml;)@chrome://messenger/content/accountcreation/fetchhttp.js:300 (false)@chrome://messenger/content/accountcreation/fetchhttp.js:222 ([object ProgressEvent])@chrome://messenger/content/accountcreation/fetchhttp.js:145 while Icedove is trying to reach the server. Afterwards, if I cancel my action and push create account button, I am stuck with error Incoming server already exists. The log is in the attachment. Thanks, Florent On Tue, Nov 13, 2012 at 8:18 PM, Carsten Schönert c.schoen...@t-online.de wrote: Hello Florent, is this a clean fresh profile? Or which extensions are installed? Did this happen with disabled extensions too? Can you please make a backtrace while this happen? http://wiki.debian.org/Icedove#Debugging Thanks Carsten Am 13.11.2012 17:22, schrieb Florent Bories: severity: important Hi, It is to let you know that this bug has not be corrected since. I have the same exact error. My icedove version is 10.0.10-1. I run Wheezy amd64 on Intel Xeon. My internet connection is behind a proxy but set in Icedove. All my system is up to date but I am unable to perform a complete reportbug since this package seems also to be not working properly on my system... Thank you for your answers. Best regards, Florent -- Regards Carsten /usr/lib/icedove/run-mozilla.sh -g /usr/lib/icedove/icedove-bin MOZILLA_FIVE_HOME=/usr/lib/icedove LD_LIBRARY_PATH=/usr/lib/icedove:/usr/lib/icedove/plugins:/usr/lib/icedove DISPLAY=:0.0 DYLD_LIBRARY_PATH=/usr/lib/icedove:/usr/lib/icedove LIBRARY_PATH= SHLIB_PATH=/usr/lib/icedove:/usr/lib/icedove LIBPATH=/usr/lib/icedove:/usr/lib/icedove ADDON_PATH= MOZ_PROGRAM=/usr/lib/icedove/icedove-bin MOZ_TOOLKIT= moz_debug=1 moz_debugger= moz_debugger_args= /usr/bin/gdb --args /usr/lib/icedove/icedove-bin GNU gdb (GDB) 7.4.1-debian Copyright (C) 2012 Free Software Foundation, Inc. License GPLv3+: GNU GPL version 3 or later http://gnu.org/licenses/gpl.html This is free software: you are free to change and redistribute it. There is NO WARRANTY, to the extent permitted by law. Type show copying and show warranty for details. This GDB was configured as x86_64-linux-gnu. For bug reporting instructions, please see: http://www.gnu.org/software/gdb/bugs/... Reading symbols from /usr/lib/icedove/icedove-bin...Reading symbols from /usr/lib/debug/usr/lib/icedove/icedove-bin...done. done. (gdb) run Starting program: /usr/lib/icedove/icedove-bin [Thread debugging using libthread_db enabled] Using host libthread_db library /lib/x86_64-linux-gnu/libthread_db.so.1. [New Thread 0x7fffe60ff700 (LWP 1)] [New Thread 0x7fffe523c700 (LWP 12223)] [New Thread 0x7fffe4a3b700 (LWP 12224)] [New Thread 0x7fffe3eff700 (LWP 12225)] [Thread 0x7fffe3eff700 (LWP 12225) exited] [Thread 0x7fffe523c700 (LWP 12223) exited] [Thread 0x7fffe4a3b700 (LWP 12224) exited] [Thread 0x7fffe60ff700 (LWP 1) exited] process 12217 is executing new program: /usr/lib/icedove/icedove-bin [Thread debugging using libthread_db enabled] Using host libthread_db library /lib/x86_64-linux-gnu/libthread_db.so.1. [New Thread 0x7fffe5efb700 (LWP 12227)] [New Thread 0x7fffe5038700 (LWP 12228)] [New Thread 0x7fffe4837700 (LWP 12229)] [New Thread 0x7fffe3cff700 (LWP 12230)] [New Thread 0x7fffe28ff700 (LWP 12231)] [New Thread 0x7fffe20fe700 (LWP 12232)] [New Thread 0x7fffdec73700 (LWP 12233)] [New Thread 0x7fffdd9ff700 (LWP 12234)] [New Thread 0x7fffdd1fe700 (LWP 12235)] [New Thread 0x7fffdc9fd700 (LWP 12236)] [Thread 0x7fffdec73700 (LWP 12233) exited] [New Thread 0x7fffdc1fc700 (LWP 12237)] [Thread 0x7fffdd1fe700 (LWP 12235) exited] [Thread 0x7fffdc9fd700 (LWP 12236) exited] [New Thread 0x7fffdc9fd700 (LWP 12238)] [New Thread 0x7fffdec73700 (LWP 12239)] [Thread 0x7fffdc1fc700 (LWP 12237) exited] [New Thread 0x7fffdc1fc700 (LWP 12240)] [Thread 0x7fffdec73700 (LWP 12239) exited] [New Thread 0x7fffdec73700 (LWP 12241)] [New Thread 0x7fffdd1fe700 (LWP 12242)] [New Thread 0x7fffd1e90700 (LWP 12243)] [New Thread 0x7fffd168f700 (LWP 12244)] [New Thread 0x7fffd0a86700
Bug#651195: ITP: squirrel -- lightweight highly attachable high-level programming, language
Alive ping Greetings, Daniel Stender -- http://www.danielstender.com/granthinam/ GPG key ID: 1654BD9C -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#685906: [libreoffice-voikko] The word Keskiviikko isn't recognized
26.08.2012 13:01, Mika Suomalainen kirjoitti: Keskiviikko is spelling mistake according to spell checker. It's Wednesday in English, so it should be known. Sorry for the delay. I'm unable to reproduce the problem in Debian sid, and I remember testing it already earlier. keskiviikko and Keskiviikko are recognized, inserting a spelling mistake in the middle of the worth does redline it. See http://people.debian.org/~timo/libreoffice/keskiviikko.png for a screenshot. A test document where the problem can be reproduced could be useful. -Timo signature.asc Description: OpenPGP digital signature
Bug#693202: high memory usage when PSQL selects from stored procedure modifying data
Source: firebird2.5 Version: 2.5.1 Severity: important Tags: upstream fixed-upstream Forwarded: http://tracker.firebirdsql.org/browse/CORE-3895 When a code in a stored procedure selects from another stored procedure which modifies a table via UPDATE, memory is consumed on every invocation. Test case from usptream bug report: 1. create metadata create table t (id integer not null); set term ^; create or alter procedure selproc (p_id integer) returns (id integer) AS begin insert into t values (:p_id); id = p_id; suspend; end ^ create or alter procedure main returns (id integer) as declare I integer = 0; begin while (i 1000) do begin select id from selproc(:i) into :id; i = i + 1; end suspend; end ^ set term ;^ 2. run test and look at memory usage (below i removed not needed stats) SQL set stat on; SQL select * from main; ID 999 Current memory = 4852448 Delta memory = 257764 Max memory = 4859608 SQL select * from main; ID 999 Current memory = 4961764 Delta memory = 109316 Max memory = 4974260 SQL select * from main; ID 999 Current memory = 5071132 Delta memory = 109368 Max memory = 5081956 you see - memory usage is incremented at each run by 109368 bytes SQL commit; Current memory = 4735108 Delta memory = -336024 Max memory = 5081956 memory is returned on commit, while it shoud be returned at the statement execution finish. If select from selproc is replaced by execute procedure selproc then there is no such high memory usage. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#693203: puppet-common: Custom facts are not correclt executed on Puppet master
Package: puppet-common
Version: 2.7.18-2
Severity: minor
Dear Maintainer,
The package for the agent, as provided, does not permit to facts defined on the
master to be correctly deployed and used on the agent side.
To reproduce the error, for example, I could define in the master a site.pp as
follow:
node puppetclient {
include modulewithfact
file { '/tmp/puppettest':
ensure = present,
content = $test_fact,
}
}
And a module, under modules/modulewithfact, that has under the lib/facter a
file test_fact.rb as follows:
Facter.add(:test_fact) do
confine :kernel = Linux
setcode do
Content from the fact
end
end
Given this configuration the expected behavior should be that the fact is
deployed on every agent (of course if they enable pluginsync=true in the
puppet.conf) and then properly executed.
So the file /tmp/puppettest should contain the string Content from the fact.
This is not happening, with the default configuration, because the agent is not
instructed to include in the facterlib path all the facts synchronized from the
server.
The problem is that puppet is not sourcing /var/lib/puppet/lib/facter for
facts, which is where factsync is writing them.
To avoid this situation I tried a workaround. I simply added to the
/etc/default/puppet file the following line:
FACTERLIB=/var/lib/puppet/lib/facter
which permits to include in the facterlib the folder where facts from the
server are synchronized by the agent.
This workaround, however, will not work when calling puppet agent --test from
the commandline.
I am writing to propose you to add this line in the standard
/etc/defatult/puppet file in the puppet package from further versions.
I hope my example and explaination is clear enough.
Regards,
Andrea
-- System Information:
Debian Release: wheezy/sid
APT prefers testing
APT policy: (500, 'testing')
Architecture: i386 (i686)
Kernel: Linux 3.2.0-3-486
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 puppet-common depends on:
ii adduser3.113+nmu3
ii facter 1.6.10-1
ii libaugeas-ruby1.8 0.4.1-1.1
ii lsb-base 4.1+Debian7
ii ruby-shadow2.1.4-2
ii ruby1.81.8.7.358-4
ii sysv-rc2.88dsf-32
Versions of packages puppet-common recommends:
ii debconf-utils 1.5.46
ii lsb-release4.1+Debian7
Versions of packages puppet-common suggests:
pn librrd-ruby1.8 none
pn ruby-selinuxnone
-- Configuration Files:
/etc/puppet/puppet.conf changed:
[main]
logdir=/var/log/puppet
vardir=/var/lib/puppet
ssldir=/var/lib/puppet/ssl
rundir=/var/run/puppet
factpath=$vardir/lib/facter
templatedir=$confdir/templates
prerun_command=/etc/puppet/etckeeper-commit-pre
postrun_command=/etc/puppet/etckeeper-commit-post
tagmap=$confdir/tagmail.conf
[master]
dns_alt_names=puppet
manifest=$confdir/manifests/site.pp
modulepath=$confdir/modules
reports=store,tagmail
-- no debconf information
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#610908: ITP: skribilo - document preparation framework
Alive ping (I know, I know!). Project is active, latest commit 2012-08-18 (cf. http://git.savannah.gnu.org/gitweb/?p=skribilo.git). A dep is the guile-reader (cf. http://savannah.nongnu.org/projects/guile-reader/, latest rev. 0.6 of May, 2012), which isn't available within Debian so far I can see, cf. http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=693201. Greetings, Daniel Stender -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#693204: Intermittent 403 Forbidden errors using http://ftp.jp.debian.org/ mirror
Package: mirrors Severity: normal Using apt-get update with mirror ftp.jp.debian.org sometimes results in 403 Forbidden errors, though the same command might run successfully just a few minutes later. It seems to be specific to the 203.178.137.175 server. Example: Ign http://ftp.jp.debian.org stable Release.gpg Ign http://ftp.jp.debian.org/debian/ stable/main Translation-en Ign http://ftp.jp.debian.org/debian/ stable/main Translation-en_US Ign http://ftp.jp.debian.org stable Release Ign http://ftp.jp.debian.org stable/main Sources/DiffIndex Ign http://ftp.jp.debian.org stable/main i386 Packages/DiffIndex Err http://ftp.jp.debian.org stable/main Sources 403 Forbidden [IP: 203.178.137.175 80] Err http://ftp.jp.debian.org stable/main i386 Packages 403 Forbidden [IP: 203.178.137.175 80] Hit http://security.debian.org stable/updates Release.gpg Ign http://security.debian.org/ stable/updates/main Translation-en Ign http://security.debian.org/ stable/updates/main Translation-en_US Hit http://security.debian.org stable/updates Release Hit http://security.debian.org stable/updates/main Sources Hit http://security.debian.org stable/updates/main i386 Packages W: Failed to fetch http://ftp.jp.debian.org/debian/dists/stable/main/source/Sources.gz 403 Forbidden [IP: 203.178.137.175 80] W: Failed to fetch http://ftp.jp.debian.org/debian/dists/stable/main/binary-i386/Packages.gz 403 Forbidden [IP: 203.178.137.175 80] E: Some index files failed to download, they have been ignored, or old ones used instead. Reading package lists... Done -- James Lick -- 黎建溥 -- james.l...@jameslick.com -- http://jameslick.com/
Bug#650716: xul-ext-noscript: unable to click Area Clienti on https://www.unicredit.it/it/privati.html
Control: tags -1 moreinfo -=| mdt, 02.12.2011 11:12:05 +0100 |=- Package: xul-ext-noscript Version: 1.9.9.69-1 Severity: important Tags: squeeze Using iceweasel 3.5.16-11 whit xul-ext-noscript 1.9.9.69-1 is impossible to click on Area Clienti that point on https://online-retail.unicredit.it/login.htm NoScript is configured to allow unicredit.it Disabling NoScript works fine. Can you still reproduce the problem with the version from wheezy or experimental? I tried with 2.6-1 from experimental and it seems to work fine. (Recipe go to https://www.unicredit.it/it/privati.html and click Area Clienti on the top right) signature.asc Description: Digital signature
Bug#693182: RFS: sqldeveloper-package/0.3.0 [RC]
Hi: The deferred NMU uploader has canceled it in behalf of mine. I'm not sure how to proceed now. Should I remove my version, or should it be re-evaluated as a RC bug fix? Thank you very much. Regards, -- Lazarus On Wed, Nov 14, 2012 at 3:05 AM, Michael Gilbert mgilb...@debian.org wrote: control: severity -1 normal control: retitle -1 RFS: sqldeveloper-package/0.3.0 On Tue, Nov 13, 2012 at 9:40 PM, Lazarus Longwrote: - Download links updated (Closes: #618650) (Reported by Sergio Fernandez) Since there is already a deferred nmu fixing the rc issue, I'm downgrading the severity. You'll need to incorporate the diff from the nmu: http://ftp-master.debian.org/deferred.html Best wishes, Mike -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#693205: debian-maintainers: Please add Rahul Amaram to Debian Maintainers keyring
Package: debian-maintainers Severity: normal Hi, Please add Rahul Amaram to Debian Maintainers keyring. I am attaching the jetring changeset with this report. Thanks, Rahul. -- System Information: Debian Release: wheezy/sid APT prefers testing APT policy: (1001, 'testing') Architecture: i386 (i686) Kernel: Linux 3.2.0-3-686-pae (SMP w/2 CPU cores) Locale: LANG=en_IN, LC_CTYPE=en_IN (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Comment: Add Rahul Amaram amaramra...@users.sourceforge.net as a Debian Maintainer Date: Wed, 14 Nov 2012 13:39:27 +0530 Action: import Recommended-By: Guido Günther a...@sigxcpu.org Agreement: http://lists.debian.org/debian-newmaint/2012/11/msg6.html Advocates: http://lists.debian.org/debian-newmaint/2012/11/msg8.html Data: -BEGIN PGP PUBLIC KEY BLOCK- Version: GnuPG v1.4.12 (GNU/Linux) mQINBFAin2cBEADOVSm8lGUmjjT/OHg03DB4wgzLlD5kRkE1XSwoEqnUDvBCkp8j zg/++Ku3T4QhARndL7PFYj8N6VYS3El1zwccEKOCnyjr8ZfPjdRJHBiA5ToxpgeX kRjxy6Np4d3Rxt/cUs0+QCaqcPN2wcJUOp/CVLSHg0kaXsqsPTkih1uXJuUmoG6S 7DmX8SGfyriDLqTj6Kd8OEgjSxZlSvlcrBRO0hWvzZFxDHF+uuOgLeenQkByzqhr TVfKMBjcB21G+cgftET7NoadzWisaK/rjY/WZXiipAUA7y6+3I6a3moFUG+Qlapt 4ci1uBsze7HFQoBhKMDMo7RW9yAiqMAm+MTpPopvzz65eWAxFADI/OLU9Eu656Q1 bxe5KcRF2EQmPdMkG6JL9nMditgGco/XZZbJsGlr3ivl/sTXMccbyr/Zv96A/Ylt 3x/bSEtvM++ziuRr/5TkmYM3Od3H2U82Q6Scb20dYypVW22T1184q3izls4ggZp8 p5qtbidNdZku8VgE4+zu7LCAJE0JTpWmOhaQNOlXdWT1NHUtk+TcA9SJNDFn8pnf JPZXmh+J7TpFBhG78URu7xJsBVolwspwVrOMFPFYDWhqcVEMktdIMe3oJcDKNTeA PS17B3suPrOvdOJnsW2bm13FtNNUrWbnEFvIX/b1PEwHjawsCAcNJnkTIwARAQAB tDBSYWh1bCBBbWFyYW0gPGFtYXJhbXJhaHVsQHVzZXJzLnNvdXJjZWZvcmdlLm5l dD6JAjcEEwEIACEFAlAin2cCGwMFCwkIBwMFFQoJCAsFFgIDAQACHgECF4AACgkQ zGTHNyZMW60sIQ//XcgHC14cchdrP6nJeUWRJV2Dr0FBzGPx+h5PrAV+Qo+K8XYv w5H+x1C3FBP/uKtHJ+PpPvNpsHXqkRZr77H5+F4Lcn69hbRNsNCXpM7eJ1EOwUmL drUs/N6A/+s9UCn/l8e/tsZY4x+SWutv1qrSTzWmPe8HhGDBqWwJToLnTwbRLyom pMU9SuCzIsZwE8jM72bY9/LpoDftSYRDM9u8HVC6mrCUAiY1fCIPh3P0ZD/gszp8 faPn75Gy18nuonq3uQ7Jenki0Nm2HKl09fd3hZ+5lYXDvSZQY4DKxgEbAzouqktg SHvDjNpsEFFkI9+Va5iBd03mzcheMJyVIGru8vE9Hc3bs/zxvGYJfg0matEEnqrB esi/9/ZFiWIqyTEVHtRorJFJw46mLULMHanDzxktdtQ+E/VR5YeC2IakGphU5CxJ MLqny1v8LSQ/W/sSYf4EpeV/9KkIMAoy5kB/FCI3I13tp/bmket3mATH1/ALQL0w POBDrUfPTd2ON5Q3Fchv/IQrnNtzFvMKud8/Q0XuaQE10nlYun0karg45uSDtTCM puKb42XncCdpaZmfQTS17o/2JxTiDETR5K5HeAdpzgc7Y6PxvH+t49TKdl8itAS6 tWpZLWTNYztKo69miqQngmEStpMHkYECB5e9orgWfEptYMJ6C9ncghTk2YiJAhwE EAECAAYFAlCcsi8ACgkQqNLNE6pUSqEZfg/9G5Vk6ZHqA3evVymf1VbV7fBheRvG kg/07PdJbzh+oXUuBYO9kwjyhBcNOWkZCbDoHFYMB3wwWVpVMjMFuBcfQ2wwrAuQ Zb0kbJ8yOsPs8Wy+vYCygKH9qrootVWWeIW50V/gf8w6PfVIY0arQhPfonO70EAT YOGLyNYSHcby304zzRoMlHaOhzyAKravNFHDZaNVytvXw+h2Z/a+ITEPJvR5gfty QrdZ4Pg3TIISuPmEex0V/Oyw8DOYdx4p2xhoJvJTgUHNWuvAZYVexT1/VQu4C3Hg HASrzPVjcnLwvvK6xYe0jjzd3GcnnEfJSev1rSZa+XI7VHTCI1KqwurfNyJ2E1HG T+qa5aZr+EDsyh1Ys+j2ZYmXVPPX8ek8TbYMgYTGyNEVWtRD5yzze10Deam1sOOQ kHV+ukM2myPxvu1/JWBNnBUcuu7lWtJ4xd29UT4gpj1NvM6/n1NyupEB0QQQUp7m 2pV6ODowxZ095Mp4T7nfmqKJNQn1t0PvWoJkgsVBjW1UYUrbUAtCm5nIJo+bTj5+ mdUd37WOrMmQJotqWFLvHUnCLbONUhRd2/Z5umE/86v0dNy99l4/Qt/3QG5bb563 zecA7YUNxmzmT8UQ9QhQW07BRBUqDfxWHmdbyi55I8fnsiq3eNI8y99OvBJwelFH wmj7mO5+7S9zlj+IRgQQEQIABgUCUJyyVgAKCRDh676lHTiYh91zAKDmqrPrhU+u 93gWPqMXX+AOee5R8wCgiGScvicvsKTj+OgIgusoAKQ/h/S5Ag0EUCKfZwEQAN8b vmMe59cKQaE4lSspvVZEBbxUaJWUCv/kuRsC6CvoEq4oNbhUmssNupI/nOFMNyXA R03mM/61bAO8nY08P0OS1tEELqTnuMX89nuCN6g85QnLx7HMj3+JfekW8/2PNkVA mSrM9xsz8GMtEYt9R3hL1zJVqHmkDf+O8ATpUKSFW//FsFH5przbIMPfHQgKN0j4 jPAri444FvU8qgOyCT5rKUJ3lW7L4I540X2HQpDrVleaap6Yx1vvKsLEo7PXRptt okA/Pr85BSFD0mMZpmsXRHtvThwg7dzhiSJmXCnwqUJguU1PxL1W3QB3TKw/Adra /kMftrD13RBIAlHY/7xwaG88BfBxhqAt5l0F3yoFFxzGdNIWv2MND5zHbrZnbPfp kRZSxtZN0RH2sgDL9hBnjTMR6xsxgEHgxwMlCfZPsF/c6i5XnInIJToP+/kVmvQM MSkdbJKmenA6m1TLigm1ZpieQ+emOlIoZ5cD5gosmmiNu/jnF8ZTNKeDuotDiBj7 ymYPwE0WA5GoDD6+ITiMJZnfqx3m0CqdhInuIn9QtaAV1tDxN+l9K1uYxh0he3vt vfwJE0KrjgT00rkXDfdceH1qfp6OsL0irxQ9MGG6gDBs9uJdIpvk0Jg9Bn/SESqq BE3ixEWDYKc1b7dXiRl/NEbpAfzFtnT3A7sB5Mv9ABEBAAGJAh8EGAEIAAkFAlAi n2cCGwwACgkQzGTHNyZMW637fg//ZiRcYRzVM08bKNQiHsEDfO6g8Vd1EdLvLvkA 6CL6jDDwQZGtG22gZvXu3xxa/Lhwh1IKb58QRYQ6lDt1JMhxeEs6IqaB87YyfjRk AK+D+/zOGzo7kzbHAsB5k7UK0WKM5k8U8PIT2TUxU8x83WW2Bdm1ljem1lln9wED ARiqXjC5NENryLABRRrxalx+hjOEHonp9z6pGBSEcHFhyxOVhhgs1IwUPe5T7hza S+elJvlT0aaNmgTJuHWCRLQuBnRlEJ4wQHFJHyDpnydPkU4Ur9v3WpHjd1HEsCXk 4w3QMxkU+Ux9F5nm7bS1y8E34j7iCGPpd7WrSyXyVzeizfirfUpD02GLgpdh5KYo sQNp8QhSSUV4LCQ2rqVnWpIvWCqcTXTCsGtpKY4+chWLITcwFP/3a6Ny5Ip8jSJD rohJXFNtYSj10Igj4/vae4GyO92JBzxT+C1SAVomyAlqh0Y4k5Jl0k4dYBbN2ax4 ewO/XeNlt7GCbUj4zJyOUhSxsr9zf+pgp5ihck2A6qgs3aZ3a+yr0TnWY5oZAYud PEJfNxtVlJCPIg+9Nddwf+OJ7eJ5Q/Vfsq8YIJ4dzLekDcR/NnwNJ1XZhp9dSNrV rdWnWWfoTrzKeODQ1Q2ABWim+rnRfHH7xyRxzEaCPrGJKGwurU2VPQmkwFDl8lIF EcwsWRo= =PoiA -END PGP PUBLIC KEY BLOCK-
Bug#693207: GEN_UUID returns non RFC-4122-compliant UUIDs
Source: firebird2.5 Version: 2.5.0 Severity: important Tags: upstream fixed-upstream Forwarded: http://tracker.firebirdsql.org/browse/CORE-3238 According to RFC-4122 the first digit of the third block should be the version of the UUID. Firebird generates random data there (on non-windows): SQL SELECT uuid_to_char(gen_uuid()) FROM RDB$DATABASE; 7B8CBD7D-51DE-E64C-92A8-E6BD399DDAB6 F32B5797-5936-9F4F-B65A-191BD6287D9E 9FC254DD-F584-7043-89B2-ABB62CBF58A8 -- System Information: Debian Release: wheezy/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing'), (500, 'stable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.2.0-4-amd64 (SMP w/4 CPU cores) Locale: LANG=bg_BG.UTF-8, LC_CTYPE=bg_BG.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#693206: vavoom: Let's install the glvis utility
Package: vavoom
Version: 1.33-5
Severity: wishlist
Tags: patch
Hi,
I think the vavoom package should also contain the glvis utility. It can be run
over WAD files and adds information for the rendering engine to skip the
subsectors that can't be visible from viewer's subsector. [1] This greatly
improves the engine's rendering performance!
Since it needs the WAD files to get pre-processed by the glbsp utility (already
in Debian), I have added this to the Suggests. And since it is currently a
utility very specific to vavoom and because there is also another different
project out there with the same name but serving a more general purpose [2], I
have move it into /usr/lib/vavoom.
- Fabian
[1] http://www.vavoom-engine.com/glvis.php
[2] https://code.google.com/p/glvis/
-- System Information:
Debian Release: wheezy/sid
APT prefers testing
APT policy: (901, 'testing'), (502, 'unstable'), (501, 'experimental')
Architecture: i386 (i686)
Kernel: Linux 3.2.0-4-686-pae (SMP w/1 CPU core)
Locale: LANG=de_DE.utf8, LC_CTYPE=de_DE.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Versions of packages vavoom depends on:
ii libc6 2.13-35
ii libflac++61.2.1-6
ii libgcc1 1:4.7.1-7
ii libgl1-mesa-glx [libgl1] 8.0.4-2
ii libjpeg8 8d-1
ii libmad0 0.15.1b-7
ii libmikmod23.1.12-4.1
ii libogg0 1.3.0-4
ii libpng12-01.2.49-1
ii libsdl-mixer1.2 1.2.12-3
ii libsdl1.2debian 1.2.15-5
ii libstdc++64.7.1-7
ii libvorbis0a 1.3.2-1.3
ii libwxbase2.8-02.8.12.1-12
ii libwxgtk2.8-0 2.8.12.1-12
ii zlib1g1:1.2.7.dfsg-13
Versions of packages vavoom recommends:
ii doom-wad-shareware [doom-wad] 1.9.fixed-2
ii freedoom [boom-wad]0.8~beta1-1
ii game-data-packager 30
vavoom suggests no packages.
-- no debconf information
From 22a048ccc7204e8369c19d7d4b1fc450ac838d1e Mon Sep 17 00:00:00 2001
From: Fabian Greffrath fabian+deb...@greffrath.com
Date: Wed, 14 Nov 2012 10:17:38 +0100
Subject: [PATCH] Install the glvis utility and add Suggests: glbsp.
---
debian/control |1 +
debian/patches/install-glvis.patch | 12
debian/patches/series |1 +
debian/rules |1 +
4 files changed, 15 insertions(+)
create mode 100644 debian/patches/install-glvis.patch
diff --git a/debian/control b/debian/control
index c35b89b..d67e812 100644
--- a/debian/control
+++ b/debian/control
@@ -25,6 +25,7 @@ Provides: doom-engine, heretic-engine, boom-engine
Architecture: any
Depends: ${misc:Depends}, ${shlibs:Depends}
Recommends: freedoom | doom-wad | heretic-wad | game-data-packager | boom-wad
+Suggests: glbsp
Description: Advanced Doom/Heretic/Hexen/Strife engine
Vavoom is an engine based on sources of Doom, Heretic, Hexen and
a little bit from Quake.
diff --git a/debian/patches/install-glvis.patch b/debian/patches/install-glvis.patch
new file mode 100644
index 000..c094ea7
--- /dev/null
+++ b/debian/patches/install-glvis.patch
@@ -0,0 +1,12 @@
+From: Fabian Greffrath fabian+deb...@greffrath.com
+Subject: Install the glvis utility.
+
+--- a/utils/glvis/CMakeLists.txt
b/utils/glvis/CMakeLists.txt
+@@ -23,5 +23,6 @@ add_dependencies(glvis libglvis)
+ target_link_libraries(glvis libglvis core)
+ set_target_properties(glvis PROPERTIES OUTPUT_NAME ../bin/glvis)
+ add_dependencies(glvis core)
++install(TARGETS glvis DESTINATION ${BINDIR})
+
+ #EXTRA_DIST = glvis.txt
diff --git a/debian/patches/series b/debian/patches/series
index e3730ef..f4369a3 100644
--- a/debian/patches/series
+++ b/debian/patches/series
@@ -4,3 +4,4 @@ freedoom-support.patch
freedoom-vlaunch.patch
fix-FTBFS-Hurd.patch
fix-hardening
+install-glvis.patch
diff --git a/debian/rules b/debian/rules
index e993daa..296f27d 100755
--- a/debian/rules
+++ b/debian/rules
@@ -26,6 +26,7 @@ override_dh_installchangelogs:
override_dh_install:
install -d debian/vavoom/usr/lib/vavoom
+ mv debian/vavoom/usr/games/glvis debian/vavoom/usr/lib/vavoom/
mv debian/vavoom/usr/games/vavoom.bin debian/vavoom/usr/lib/vavoom/
mv debian/vavoom/usr/games/vavoom-dedicated.bin debian/vavoom/usr/lib/vavoom/
dh_install
--
1.7.10.4
Bug#693208: clang unable to link trivial test program on armhf
Package: clang Version: 3.0-6 Severity: grave Tags: patch x-debbugs-cc: debian-rele...@lists.debian.org RT in cc because of proposed TPU upload. Unfortunately it seems that the changes in 3.0-6 fixed clang on armel but not on armhf. root@debian:/# clang -v test.c Debian clang version 3.0-6 (tags/RELEASE_30/final) (based on LLVM 3.0) Target: arm-unknown-linux-gnueabihf Thread model: posix clang: warning: unknown platform, assuming -mfloat-abi=soft /usr/bin/clang -cc1 -triple armv4t-unknown-linux-gnueabihf -S -disable-free -disable-llvm-verifier -main-file-name test.c -mrelocation-model static -mdisable-fp-elim -mconstructor-aliases -target-abi apcs-gnu -target-cpu arm7tdmi -msoft-float -mfloat-abi soft -target-feature +soft-float -target-feature +soft-float-abi -target-feature -neon -target-linker-version 2.22 -momit-leaf-frame-pointer -v -resource-dir /usr/bin/../lib/clang/3.0 -fmodule-cache-path /var/tmp/clang-module-cache -internal-isystem /usr/local/include -internal-isystem /usr/bin/../lib/clang/3.0/include -internal-externc-isystem /usr/include/arm-linux-gnueabihf -internal-externc-isystem /usr/include -ferror-limit 19 -fmessage-length 80 -fno-signed-char -fgnu-runtime -fobjc-runtime-has-arc -fobjc-runtime-has-weak -fobjc-fragile-abi -fdiagnostics-show-option -fcolor-diagnostics -o /tmp/test-TUFgUO.s -x c test.c clang -cc1 version 3.0 based upon llvm 3.0 hosted on arm-unknown-linux-gnueabihf ignoring nonexistent directory /usr/bin/../lib/clang/3.0/include ignoring nonexistent directory /usr/bin/../lib/clang/3.0/include ignoring duplicate directory /usr/local/include ignoring duplicate directory /usr/include/arm-linux-gnueabihf ignoring duplicate directory /usr/include/arm-linux-gnueabihf ignoring duplicate directory /usr/include/arm-linux-gnueabihf ignoring duplicate directory /usr/include #include ... search starts here: #include ... search starts here: /usr/local/include /usr/include/arm-linux-gnueabihf /usr/include /usr/include/clang/3.0/include/ /usr/lib/gcc/arm-linux-gnueabihf/4.6/include/ /usr/lib/gcc/arm-linux-gnueabihf/4.6/include-fixed/ End of search list. /usr/bin/as -o /tmp/test-8d1iPt.o /tmp/test-TUFgUO.s /usr/bin/ld -X --hash-style=both --build-id --eh-frame-hdr -m armelf_linux_eabi -dynamic-linker /lib/ld-linux.so.3 -o a.out crt1.o crti.o /usr/lib/gcc/arm-linux-gnueabihf/4.6/crtbegin.o -L/usr/lib/gcc/arm-linux-gnueabihf/4.6 -L/usr/lib/gcc/arm-linux-gnueabihf/4.6/../../.. -L/lib -L/usr/lib /tmp/test-8d1iPt.o -lgcc --as-needed -lgcc_s --no-as-needed -lc -lgcc --as-needed -lgcc_s --no-as-needed /usr/lib/gcc/arm-linux-gnueabihf/4.6/crtend.o crtn.o /usr/bin/ld: cannot find crt1.o: No such file or directory /usr/bin/ld: cannot find crti.o: No such file or directory clang: error: linker command failed with exit code 1 (use -v to see invocation) root@debian:/# I decided to first look at the warning about float abi, this seems to have been a simple case of a missing condition in the logic that decides what float ABI to use. While fixing that I also noticed that the code uses softfp by default on armel when for debian armel it should be using soft by default (since debian supports hardware without a fpu) so I changed that too. Reading that code also gave me a hint on how to fix the code that made the path descisions which I proceeded to do. Then I had to fix the dynamic linker path for armhf. This is sufficient to make clang work with the gold linker on armhf. Unfortunately the bfd linker fails with an assertion failure. I intend to file a seperate bug report about this but still I think working with one or the two linker choices debian offers is better than working with neither. While working on the fixes I also found the clean target was not cleaning up properly and so fixed it. I have attatched a diff which I would like to upload to TPU are the maintainer and release team happy with this? I have tested that the patch does not break linking on armel with either bfd or gold. P.S. it seems the version in unstable has regressed from the version in testing and does not link a trivial test app successfully on either armel or armhf I have not investigated details of that (IMO fixing wheezy is more important than fixing a package that is in sid and unlikely to make it for wheezy). diff -Nru clang-3.0/debian/changelog clang-3.0/debian/changelog --- clang-3.0/debian/changelog 2012-02-25 13:05:54.0 + +++ clang-3.0/debian/changelog 2012-11-13 12:15:15.0 + @@ -1,3 +1,14 @@ +clang (3.0-6.1) wheezy; urgency=low + + * Non-maintainer upload. + * 26-set-correct-float-abi.diff: Fix default float abis for armel and armhf + * 24-path-multiarch.diff: Fix paths for armhf + * 27-dynamic-linker.patch: Fix dynamic linker path for armhf + * debian/rules: fix clean target to remove generated file +tools/clang/include/clang/Debian/debian_path.h + + -- Peter Michael Green plugw...@debian.org Mon, 12 Nov 2012 22:04:07 + + clang (3.0-6) unstable; urgency=low *
Bug#693182: RFS: sqldeveloper-package/0.3.0 [RC]
Hi, [ I do not plan to sponsor this. ] On 11/14/2012 03:40 AM, Lazarus Long wrote: * Addressed all reported issues and bugs: - Download links updated (Closes: #618650) (Reported by Sergio Fernandez) - Split grep for shell script (LP: #985810,#998610) (Closes: #692534) (Reported by Bruno Medeiros and patch by Brad Powell) - Replaced dos2unix with tofrodos (LP: #560803,#626272) (Closes: #568982) (Reported by Seth Rosenblum) - Included debhelper on the build dependency list (LP: #588458) (Reported by Seth Rosenblum) - Replaced dh options with overrides (LP: #998258) (Reported by Christian Loos) * Several small fixes and improvements: - Fixed an unknown parameter passed to trap when in debug mode - Differential dependencies for pre and post SQL Developer v2 - Strengthened trap exit handling * Updated documentation with JDK dependencies for all versions * Updated documentation regarding compatible JDKs * Updated OTN license to current version * Tested against v2.x and v3.x release families of SQL Developer * Solved Debian QA warnings: - Converted source format to 3.0 (native) - Added Homepage to debian/control * Changed the source compression format to xz * Verified compliancy with Standards-Version: 3.9.3 * Bumped version to reflect functionality Just looking at this changelog entry, I do not think all of these changes conform to the freeze policy[1]. [1] http://release.debian.org/wheezy/freeze_policy.html Ansgar -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#693209: CHAR_TO_UUID/UUID_TO_CHAR work differently on big-endian machines compared with LE
Source: firebird2.5 Version: 2.5.0 Severity: important Tags: upstream fixed-upstream Forwarded: http://tracker.firebirdsql.org/browse/CORE-3887 On big-endian architectures CHAR_TO_UUID/UUID_TO_CHAR use little-endian byte ordering, returning different results for the same input compared with little-endian architectures. This makes the same statements/stored procedures behave differently between architectures, which may lead to all kinds of nastiness in mixed environments. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#693210: server crash on prearing an empty query with tracing enabled
Source: firebird2.5 Version: 2.5.0 Severity: important Tags: upstream fixed-upstream security Forwarded: http://tracker.firebirdsql.org/browse/CORE-3884 With trace enabled, preparing an empty query crashes the server on line 91 of /src/jrd/trace/TraceDSQLHelpers.h, since the dereferenced m_request variable is NULL. Tagged as 'security' since this is a remote crash, although it requires a valid user/pass. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#693211: coreutils: file conflict with realpath
Package: coreutils Version: 8.20-1 Severity: serious Preparing to replace coreutils 8.13-3.3 (using .../coreutils_8.20-1_amd64.deb) ... Unpacking replacement coreutils ... dpkg: error processing /var/cache/apt/archives/coreutils_8.20-1_amd64.deb (--unpack): trying to overwrite '/usr/share/man/man1/realpath.1.gz', which is also in package realpath 1.17 dpkg-deb: error: subprocess paste was killed by signal (Broken pipe) -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#693212: glbsp: Please run glbsp over /usr/share/games/rott/*.wad upon installation
Package: glbsp Version: 2.24-1 Severity: wishlist Tags: patch Hi, wouldn't it be cool if glbsp was run over all WAD files in /u/s/games/doom upon installation? This way, advanced ports like prboom or vavoom that support OpenGL rendering could instantly benefit from the additional special nodes that it creates. I have attached a debdiff that adds exactly this by means of a trigger. The code removing the *.gwa files upon package removal could be made a bit more spohisticated, e.g. by maintaining a list of files that it automatically created and only removing those. - Fabian -- System Information: Debian Release: wheezy/sid APT prefers testing APT policy: (901, 'testing'), (502, 'unstable'), (501, 'experimental') Architecture: i386 (i686) Kernel: Linux 3.2.0-4-686-pae (SMP w/1 CPU core) Locale: LANG=de_DE.utf8, LC_CTYPE=de_DE.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages glbsp depends on: ii libc6 2.13-35 ii libglbsp3 2.24-1 glbsp recommends no packages. glbsp suggests no packages. diff -u glbsp-2.24/debian/changelog glbsp-2.24/debian/changelog --- glbsp-2.24/debian/changelog +++ glbsp-2.24/debian/changelog @@ -1,3 +1,10 @@ +glbsp (2.24-2) UNRELEASED; urgency=low + + * Add a trigger interested in /usr/shame/games/doom and run glbsp over *.wad +files in there that do not yet have a *.gwa pendant. + + -- Fabian Greffrath fabian+deb...@greffrath.com Wed, 14 Nov 2012 10:27:10 +0100 + glbsp (2.24-1) unstable; urgency=low * New upstream release. only in patch2: unchanged: --- glbsp-2.24.orig/debian/glbsp.postinst +++ glbsp-2.24/debian/glbsp.postinst @@ -0,0 +1,17 @@ +#! /bin/sh +set -e + +if [ -d /usr/share/games/doom ] ; then \ + cd /usr/share/games/doom \ + for w in *.[wW][aA][dD] ; do \ + if [ ! -e $(echo $w | sed 's/\..*$/.gwa/') ] ; then \ + glbsp -q $w ; \ + fi ; \ + done ; \ +fi + +if [ $1 = triggered ]; then + exit 0 +fi + +#DEBHELPER# only in patch2: unchanged: --- glbsp-2.24.orig/debian/glbsp.triggers +++ glbsp-2.24/debian/glbsp.triggers @@ -0,0 +1 @@ +interest /usr/share/games/doom only in patch2: unchanged: --- glbsp-2.24.orig/debian/glbsp.prerm +++ glbsp-2.24/debian/glbsp.prerm @@ -0,0 +1,8 @@ +#! /bin/sh +set -e + +if [ $1 = remove ] [ -d /usr/share/games/doom ] ; then + find /usr/share/games/doom -type f -name '*.gwa' -delete ; +fi + +#DEBHELPER#
Bug#646125: empathy: Certificate complaints of every connect despite selecting remember
Le Wed, 14 Nov 2012 06:25:23 +0100, Stefan Hajnoczi stefa...@gmail.com a écrit : On Tue, Nov 13, 2012 at 10:57 PM, Laurent Bigonville bi...@debian.org wrote: If it's the case, are you running GNOME or an other desktop environment? No GNOME. I was using ratpoison Is gnome-keyring running? No gnome-keyring-daemon, only polkit-gnome-authentication-agent-1. That might explain, the pinned certificates are stored in gnome-keyring. You should take care of starting it properly. Cheers Laurent Bigonville -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#691148: [Pkg-virtualbox-devel] Bug#691148: Bug#691148: Please package virtualbox 4.2.2
On 14.11.2012 08:27, Frank Mehnert wrote: On Tuesday 13 November 2012 17:55:14 Felix Geyer wrote: On 12.11.2012 12:19, Frank Mehnert wrote: It is correct that we switched from bcc to Open Watcom to compile the PC BIOS as well as the VGA BIOS. The reason is indeed that bcc is unmaintained since years, has many bugs and creates code which is far away from being optimized. And we didn't find an appropriate alternative to Open Watcom. But it is not true that Open Watcom is required to build the BIOS of VirtualBox. If Open Watcom is not available, an alternative Assembler file can be used to create the BIOS. See here: https://www.virtualbox.org/browser/vbox/trunk/src/VBox/Devices/BiosCommon Code Right, but Open Watcom is required to build the BIOS from source (preferred form for modification). That makes VirtualBox a candidate for the Debian contrib repository as it is free but requires non-free software to build from source. When the package is in contrib the assembler file could be used to build the BIOS. In my opinion this depends on the definition of the term source code. Debian has basically adopted the GPL definition of source code: The source code for a work means the preferred form of the work for making modifications to it. The VirtualBox source code tarball ships two alternative variants of the BIOS source code: The first variant is C code mixed with Assembler code (in src/VBox/Devices/PC/BIOS/* and src/VBox/Devices/Graphics/BIOS/*). The second variant is pure Assembler code which can be found in src/VBox/Devices/PC/BIOS/VBoxBiosAlternative.asm and src/VBox/Devices/Graphics/BIOS/VBoxVgaBiosAlternative.asm When you want to modify the BIOS you change the code in the files of the first variant so only that is considered the source code of the BIOS. The BiosAlternative assembler files are just pre-generated files that need to be updated whenever the code changes. Both variants are part of the source code tarball, and the second variant allows it to build VirtualBox even if Open Watcom is not available. It should not matter that the second variant is generated from the first variant because that generation is done by the VirtualBox team and we ensure that the 2nd variant will produce the same object code as the 1st variant. That is a problem because it's impossible to modify the BIOS (e.g. by adding a distro patch) without someone running Open Watcom. Building and running software in Debian main needs to be self-contained but Open Watcom is required at least when you modify the upstream BIOS code. Regards, Felix -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#693040: libav: Strange build failure on several archs
On Wed, Nov 14, 2012 at 9:29 AM, Fabian Greffrath fab...@greffrath.com wrote: Am 13.11.2012 16:45, schrieb Reinhard Tartler: The problem is upstream and has been identified now. Reverting upstream commit 468ea9d5b14f92fe61f47f034e67066f65163f5f seems to fix the issue, albeit a better solution is currently being worked on. Good to know that you've succeeded to narrow down the problem. But how could it ever build on the other archs if the symbol in question isn't exported anymore, why does it only break on selected archs? Because those are the archs that do not have special ASM variants of the log2 implementation but fall back to the C variant. The C variant tries to access the ff_log2_tab symbol, to which the access is hidden. The proper patch to solve this is: http://patches.libav.org/patch/30530/ -- regards, Reinhard -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#623713: empathy: Invisible mode not working
tag 623713 + unreproducible thanks Le Wed, 14 Nov 2012 13:00:00 +0530, Pawan Hegde h.pa...@gmail.com a écrit : Hi, Hi, I can confirm that the invisible mode works with my GTalk account. However, it did not work with my Windows Live chat. I've not checked with salut. This is weird, could you please confirm the version of empathy you are using? Do you know if you are using telepathy-haze or telepathy-butterfly to connect to Windows Live? Laurent Bigonville -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#691148: [Pkg-virtualbox-devel] Bug#691148: Bug#691148: Bug#691148: Please package virtualbox 4.2.2
Can Debian apply an anti patch ? i.e. the BIOS changeset patch in reverse, so it will become buildable again with bcc ? -- -Alexey Eromenko Technologov
Bug#693144: aptitude should honour explicit installation request in connection with markauto package
Hello On 11/14/2012 03:02 AM, Daniel Hartwig wrote: Note that you can not request of aptitude that a package “remains installed”. You can only request to install, remove, mark manual (hint!), etc.. At best, the closest option is “keep”, however, that will not work in the example you describe. Sorry for being vague in my wording. With remains installed I just wanted to point out the explicit install action that is specified on the command line. But anyway, we agree on that issue. In the past, it was considered convenient to allow users to upgrade packages using “aptitude install foo”, without altering the auto-installed state. However, current apt thinking is that “install” should always mark the requested packages as manually installed. That is the default behaviour in libapt-pkg, as used by apt-get, etc.. This puzzled me initially too but as soon as I realized that an install request does not change the auto-installed state I had no problem with this behaviour. This was in fact the motivation to specify a package explicitly on the command line which would otherwise be autoremoved. BTW, I am fine with either behaviour but I would strongly vote for a consistent policy between apt and aptitude. What you really want is to mark it as manually installed: # aptitude install rsstail- opensslm I am aware of this option. I don't like it because I have to issue a different command depending on whether openssl is installed or not. If I could run aptitude install rsstail- openssl+m it would solve my problem. However +m is not a supported action (as opposed to +M). The request to install openssl is not ignored, although it has no effect, because aptitude processes that install request *before* it decides to remove packages that are no longer required. Interestingly, the interactive behaviour is different here from the one on the command line. If I hit '-' on rsstail and the '+' on openssl it would keep openssl and mark it as manually installed. Regards, -- Elmar -- Elmar Heeb Tel-M: +41 79 628 7524 Bläsistrasse 49 Tel-P: +41 44 342 0168 CH-8049 Zürich Tel-G: +41 44 633 2591 -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#657892: empathy: Favorites aren't saved in 'Room' such as favorite IRC channels
tag 657892 - moreinfo forwarded 657892 http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=657892 thanks Le Wed, 14 Nov 2012 00:06:31 +0100, Kees de Jong keesdej...@gmail.com a écrit : Are you still experiencing this bug? If it's the case, are you also able to reproduce this with Jabber/XMPP multi-user rooms? Or is it just an issue with IRC channels? I can still reproduce this bug. It's evident with all room favorites (also Jabber/XMPP). I'm able to save rooms with this workaround; I add them as a favorite and then I select the auto-connect option. Than it remains in Empathy, otherwise the favorite room disappears when the room is closed. You are actually right. Thanks for your repport Laurent Bigonville -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#693204: Intermittent 403 Forbidden errors using http://ftp.jp.debian.org/ mirror
Hi James, On Wed, Nov 14, 2012 at 05:06:04PM +0800, James Lick wrote: Package: mirrors Severity: normal Using apt-get update with mirror ftp.jp.debian.org sometimes results in 403 Forbidden errors, though the same command might run successfully just a few minutes later. It seems to be specific to the 203.178.137.175 server. Example: [..] Err http://ftp.jp.debian.org stable/main Sources 403 Forbidden [IP: 203.178.137.175 80] Thansk for your report, forwarded to the relevant admins. $ host 203.178.137.175 175.137.178.203.in-addr.arpa domain name pointer ftp.nara.wide.ad.jp. -- Simon Paillard -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#687789: crashes/freezes when using H.264 capable webcam
tag 687789 + moreinfo thanks Hi, Could you please try to start empathy with the following environment variable set and give attach the output to this bug: GST_DEBUG=*v4l*:5 But it's very unlikely that something could be done to fix this in the squeeze version. Cheers Laurent Bigonville -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#693144: aptitude should honour explicit installation request in connection with markauto package
On 14 November 2012 18:03, Elmar S. Heeb el...@heebs.ch wrote: BTW, I am fine with either behaviour but I would strongly vote for a consistent policy between apt and aptitude. In future versions aptitude will adopt apt-get's behaviour. However +m is not a supported action (as opposed to +M). Oh, yes. I suppose that when “+M” was introduced, “+m” would have been equivalent to “+”, but that situation has long since changed. With the new behaviour, “+m” (install and mark manual) would again be the same as “+”. The request to install openssl is not ignored, although it has no effect, because aptitude processes that install request *before* it decides to remove packages that are no longer required. Interestingly, the interactive behaviour is different here from the one on the command line. If I hit '-' on rsstail and the '+' on openssl it would keep openssl and mark it as manually installed. Indeed. The interactive processing is different, with auto-removals processed immediately. It is equivalent to: # aptitude remove --schedule-only rsstail # aptitude install --schedule-only openssl # aptitude install For various reasons, the semantics must be different here than when specifying all actions at once. Regards -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#693213: please document why zlib needs dfsg sources
Package: src:zlib Version: 1:1.2.7.dfsg-13 The zlib source has at least the contrib directory removed, however I can't find any pointer why all the files are removed. At least some of these do have kind of BSD licenses. Is there any reason to remove everything from contrib? Also, I see ancient bug reports that building packages with the asm versions for some architectures has some maintenance burden. Would it be possible to document the speedups gained with the asm versions of some routines? -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#693208: clang unable to link trivial test program on armhf
On Wed, Nov 14, 2012 at 09:24:50 +, peter green wrote: I have attatched a diff which I would like to upload to TPU are the maintainer and release team happy with this? I have tested that the patch does not break linking on armel with either bfd or gold. P.S. it seems the version in unstable has regressed from the version in testing and does not link a trivial test app successfully on either armel or armhf I have not investigated details of that (IMO fixing wheezy is more important than fixing a package that is in sid and unlikely to make it for wheezy). Having a fix in sid is a prerequisite for anything regarding wheezy. Cheers, Julien signature.asc Description: Digital signature
Bug#693048: Gajim fails to handle invalid certificates
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 11/14/2012 02:19 AM, Florian Weimer wrote: On 11/14/2012 08:19 AM, Kurt Seiifried wrote: So do we consider this to be an OpenSSL issue of gajim? I'm sure gajim is not the only program that does something like this. As far as I understand things, it is not necessarily at all to set a verification callback in OpenSSL. If you load the root certificate store and examine SSL_get_verify_result, that should be sufficient. You can even look at the peer certificate and continue anyway if the user has overridden the certificate validity. So far, I haven't found a good reason to use a verify callback at all. You need it to implement a custom PKIX validation policy, but that should be pretty rare. (I still have to check older OpenSSL versions, though, perhaps there, the behavior was different.) Anyway, if application developers set a verification callback, it is their responsibility to implement it correctly. Therefore, I don't think this is an OpenSSL issue. Makes sense, just wanted to confirm this problem resides within Gajim. Please use CVE-2012-5524 for this issue. - -- Kurt Seifried Red Hat Security Response Team (SRT) PGP: 0x5E267993 A90B F995 7350 148F 66BF 7554 160D 4553 5E26 7993 -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.12 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://www.enigmail.net/ iQIcBAEBAgAGBQJQo2YLAAoJEBYNRVNeJnmTfi4P/1WHAiTvcHoJRbouSwyzIWvZ PSaQd23ubVbji4Te+4ZaJ1se9fSw0j5RdrkXisTZYuoo5Fg/ev3CDU5K1dZFyZMz tZCZSuXmJeSTWSN4lW/59CbLUgL4kaJy+uxCx0kNObBT2BIiIg4/zNu4PIJttwdH +G4/iAGrEDOJAutiHg6zbG5kBgvr+rWnxEELBxV3IoctWBrdZ509OmVIYT6HuSkx cSM2nRauhtYGjVR+e0x8PpbX+xFTVET5i82m7N/TPLjtzP7RJPg5jQKl/1eu6tPy +SpTGZsoXN9dBSHf3cIw1d/Ysl5wuxN/wj9nSoNpcr3jPqLdEGvbK5Bqem8UyQxp yJa7Yk3Ge5LmR92HKJUo01VHWkuqeW1TyQ52tc+1592PN3xYIWHA6xP9DyiqdvHP ekMa6wm6G8Tqa/k5rTVWMB1TqJtHq9a46ClHNINSe1aDh/HVitVKVgEm65QpXwTt m62/VCGzkFVYa+p8ZVL/7SK0/NoDK7Gxckn7yta/XUzpH70j21yTsYyQNt/W4IDD YN6SXc0yMvyjaUEFAIADCIQwlfnLSYeYNh3iVMi4o4YTACVTxumYu4LfU6Tt5dT6 USJlpnorGD7dSHVeky00vjxAtVJH2U8Nx61Fk/ZdB0qovK72VuSe+uvpmj41kors FsA39sWFXGjeqK+yHjkj =sFXa -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#693214: error: element informalfigure not allowed here; expected the element end-tag
Package: herold Version: 6.0.2-1 Severity: normal herold seems to be producing invalid docbook document. jing fails with: error: element informalfigure not allowed here; expected the element end-tag on something like: xref linkend=topOfPageinformalfigure mediaobject imageobject role=html imagedata fileref=file:///images/arrow-up.gif format=GIF scalefit=1/ /imageobject imageobject role=fo imagedata contentdepth=100% fileref=file:///images/arrow-up.gif format=GIF scalefit=1 width=100%/ /imageobject /mediaobject /informalfigure -- System Information: Debian Release: 6.0.6 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable'), (200, 'testing'), (100, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 3.2.0-0.bpo.3-amd64 (SMP w/8 CPU cores) Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages herold depends on: ii antlr3 3.2-5 language tool for constructing rec ii libcommons-codec-java 1.4-2 encoder and decoders such as Base6 ii libcommons-jxpath-java 1.3-3 manipulate javabean using XPath sy ii libcommons-logging-java1.1.1-8 commmon wrapper interface for seve ii libxml-commons-resolver1.1 1.2-7~bpo60+1 XML entity and URI resolver librar ii libxmlgraphics-commons-jav 1.5-1 reusable components used by Batik herold recommends no packages. herold suggests no packages. -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#693208: clang unable to link trivial test program on armhf
On 14/11/2012 11:45, Julien Cristau wrote: On Wed, Nov 14, 2012 at 09:24:50 +, peter green wrote: I have attatched a diff which I would like to upload to TPU are the maintainer and release team happy with this? I have tested that the patch does not break linking on armel with either bfd or gold. P.S. it seems the version in unstable has regressed from the version in testing and does not link a trivial test app successfully on either armel or armhf I have not investigated details of that (IMO fixing wheezy is more important than fixing a package that is in sid and unlikely to make it for wheezy). Having a fix in sid is a prerequisite for anything regarding wheezy. Unfortunately, we have clang 3.1 in sid (I failed to have this version in Wheezy in time). Otherwise, your patch look good. Thanks! Sylvestre -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#693215: ITP: bustle -- D-Bus activity visualiser
Package: wnpp Severity: wishlist Owner: Hector Oron zu...@debian.org * Package name: bustle Version : 0.4.1 Upstream Author : Will Thompson will.thomp...@collabora.co.uk * URL : http://www.willthompson.co.uk/bustle/ * License : LGPL-2.1+ and GPL-2+ Programming Lang: Haskell/C Description : D-Bus activity visualiser Bustle is a tool to chart and provide timing information of D-Bus calls for profiling and debugging purposes. It is intended to replace reading the cryptic output of dbus-monitor. Calls are displayed using Message Sequence Charts, a succinct way of representing entities and interactions over time. It can also output data in Graphviz format. This package contains the graphical visualizer for traces generated with the bustle-pcap tool. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#684437: pre-approval for fpc/2.6.0-7 upload (was: unblock: fpc/2.6.0-6)
Hi Julien, Since the last post on this bug report a load of updates related to localisation have landed. Specifically the package was not previously setup to support translations and as such was not translated. The package has now been fixed to support translation and translations have been added for Danish, Slovak, Portuguese, Russian, German, Polish, Czech, French, Italian, Japanese, Swedish and Spanish. There was also a review of the english descriptions as part of the process Which resulted in some minor rewordings and clarifications and (unfortunately) a lot of reformatting. I have also taken the opertunity to revert the removal of fpc.*dpkg* as requested in the unblock discussions for 2.6.0-6 I have attached debdiffs against the versions in testing and unstable, please review and ack/nack this upload. NAK. While translation updates might be ok, new i18n isn't (and reformatting isn't either). I'm quite surprised by this refusal. Indeed, by formatting, we mean English errors fixing on debconf templates. This does not effect the debconf scripts or any other strings n the executables. I don't see the point to refuse this kind of modifications as it should be 0 risk? Can you please explain more the reasons for your refusal? Cheers, signature.asc Description: This is a digitally signed message part
Bug#691148: [Pkg-virtualbox-devel] Bug#691148: Bug#691148: Bug#691148: Bug#691148: Please package virtualbox 4.2.2
On Wednesday 14 November 2012 11:08:22 Alexey Eromenko wrote: Can Debian apply an anti patch ? i.e. the BIOS changeset patch in reverse, so it will become buildable again with bcc ? Just try it. Using the VBox 4.2 BIOS with bcc is not possible. You could probably use the VBox 4.1 BIOS with VBox 4.2. But in that case we will refuse to lock at any bug report of such builds because in the 4.2 BIOS we fixed a bunch of bugs and added a few new features. And as I said, converting the sources to Open Watcom is not to annoy Debian or any other distribution but to improve the code and to make our life easier. We just did not find a comparable alternative to Open Watcom. Kind regards, Frank -- Dr.-Ing. Frank Mehnert | Software Development Director, VirtualBox ORACLE Deutschland B.V. Co. KG | Werkstr. 24 | 71384 Weinstadt, Germany Hauptverwaltung: Riesstr. 25, D-80992 München Registergericht: Amtsgericht München, HRA 95603 Geschäftsführer: Jürgen Kunz Komplementärin: ORACLE Deutschland Verwaltung B.V. Hertogswetering 163/167, 3543 AS Utrecht, Niederlande Handelsregister der Handelskammer Midden-Niederlande, Nr. 30143697 Geschäftsführer: Alexander van der Ven, Astrid Kepper, Val Maher signature.asc Description: This is a digitally signed message part.
Bug#679746: default --system home directory
Hi, Since some packages do not seem to care about their home directory, and putting system directories under /home is “obviously” never the answer: Perhaps adduser --system invocations should default to --home /nonexistent --no-create-home if no --home option was supplied by the invoking script/user. Kind regards, -- Wessel Dankers wsl-deb-bug-679...@fruit.je signature.asc Description: Digital signature
Bug#693217: Removal of xenstore tdb file before xenstored daemon
Package: xen-utils-common Version: 4.0.0-1 Consider removal of xenstored tdb file (located at /var/lib/xenstored/tdb) before start of xenstored daemon during the boot (or removal during the shutdown/reboot of the server) as proposed by Ian Campbell during our discussions [1]. [1] http://lists.xen.org/archives/html/xen-users/2012-11/msg00111.html -- Peter Viskup -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#685540: asterisk-flite, asterisk-espeak: binnmu required
Quoting Tzafrir Cohen (2012-11-13 18:00:30) Indeed this is fixable through a binNMU. Yes, but release managers disapprove of simple binNMUs covering over the underlying problem, as I wrote earlier: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=685540#20 The proper fix is this combo: 1) File bugreport against asterisk-dev about broken/missing hints about shared library. 2) Fix bug filed in 1). 3) Make simple binNMUs of asterisk-flite and asterisk-espeak which then get proper hints from asterisk-dev and therefore is acceptable by release team. Sorry, I fail to locate my correspondence with the release team about this issue. Regards, - Jonas signature.asc Description: signature
Bug#693218: adduser --system should default to --group
Package: adduser Version: 3.112+nmu2 Severity: wishlist Tags: security Hi, Currently, system users get nogroup (65534) as their default primary group. However, multiple (system) accounts sharing a common group is not good from a security standpoint. It gives unrelated processes access to each other's files and other resources. While this could be considered a bug in the invoker's script, it's something that is easy to overlook and it could be argued that defaults should be sane and secure (‘graceful degradation’). Please make --group the default for --system. Kind regards, -- Wessel Dankers wsl-deb-bug-sub...@fruit.je signature.asc Description: Digital signature
Bug#683323: unblock: python-apt/0.8.7
On Mon, Nov 12, 2012 at 09:28:00PM +, Adam D. Barratt wrote: On Sun, 2012-10-28 at 16:36 +, Adam D. Barratt wrote: A quick note first, as I noticed the subject was updated to reference 0.8.8... That version isn't a valid candidate right now in any case, as it FTBFS on approximately half the architectures - see https://buildd.debian.org/status/package.php?p=python-apt Any news on that? Sorry for the delay and thanks for your mail. This is fallout from a recent change in apt (to handle packages that have no architectures) in our testsuite. I fixed it in bzr and its ready to upload but I'm traveling right now and my network is pretty bad, so building is a bit difficult for me right now. If someone from the team could upload it that would be great, otherwise I will do it once I found a reasonable network connection. On Mon, 2012-10-15 at 09:14 +0200, Michael Vogt wrote: On Sun, Oct 14, 2012 at 01:48:52PM +0300, Martin-Éric Racine wrote: 2012/9/3 Michael Vogt m...@debian.org: I would slightly prefer 0.8.8 as the auth.py module is IMO a good idea compared to having multiple apps duplicating this code in various places. Whilst I agree that reducing code duplication is generally a good thing, for wheezy the practical difference is presumably none given that nothing outside of python-apt itself would be using the code? Did I miss anything here? I don't have a strong opinion either way, I'm happy to remove the apt.auth module and upload that to wheezy or use the updated one from 0.8.8 - but I would really like to get the bugfixes from 0.8.8.1 in if possible. Cheers, Michael -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#693219: Doesn't mention --foreign in help output
Package: debootstrap Version: 1.0.42 Severity: minor $ sudo debootstrap --arch=armhf sid sid-armhf ftp://ftp.debian.org/debian/ fails with the errors W: Failure trying to run: chroot /tmp/sid-armhf mount -t proc proc /proc W: See /tmp/sid-armhf/debootstrap/debootstrap.log for details because I'm running on amd64. That's fine, but it would be helpful if the --help output mentioned the --foreign option to stop this happening. Maybe also pick up on the failure to run something in the chroot if the arch specified doesn't match the native one and tell the user about --foreign then? -- System Information: Debian Release: wheezy/sid APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 3.2.0-4-amd64 (SMP w/4 CPU cores) Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages debootstrap depends on: ii wget 1.13.4-3 Versions of packages debootstrap recommends: ii debian-archive-keyring 2012.4 ii gnupg 1.4.12-6 debootstrap suggests no packages. -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#693220: Add crossbuild-essential support
Package: build-essential Version: 11.5 Severity: wishlist Tags: patch Following on from discussion in this thread http://lists.debian.org/debian-embedded/2012/06/msg00030.html The cross-build-essential package has been developed some more and tested in Quantal for arm64 bootstrap, and armel and armhf builds. It works nicely. We definitely want to start using this. The latest code is available at: http://people.debian.org/~wookey/bootstrap/ubunturepo/pool/main/c/cross-build-essential/ That code was carefully developed on top of build-essential so that they could be easily merged into that one package if so desired. Feedback, particularly from the maintainer, about whether this is desireable, or should be uploaded as a separate package would be helpful. The above thread didn't generate any on that point. I can't actually think of any real reasons why it should be a seaparate package. Thinking about build-essential:arch, and crossbuild-essential-arch together seems to make sense and I don't expect much churn in either package once toolchains are stable. It takes moments to build so the large increase in number of binary packages is not an issue. On the other hand it's dead easy to just upload it as a new package and let them diverge. This doesn't do any real harm but seems bit lazy to me. The existing code is set up for Ubuntu cross-toolchains at the moment, but this fundamental question of whether it is one or two source packages should be considered here, I think. Build-essential+cross-build-essential is always likely to have some Debian/Ubuntu difference. If the build-essential maintainer is happy to merge them then I'll tidy up the Debian code for an upload. -- System Information: Debian Release: 6.0.6 APT prefers stable APT policy: (990, 'stable') Architecture: i386 (i686) Kernel: Linux 2.6.32.33-kvm-i386-2028-dirty (SMP w/1 CPU core) Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages build-essential depends on: ii dpkg-dev 1.15.8.13 Debian package development tools ii g++ 4:4.4.5-1 The GNU C++ compiler ii gcc 4:4.4.5-1 The GNU C compiler ii libc6-dev [libc-dev] 2.11.3-4 Embedded GNU C Library: Developmen ii make 3.81-8 An utility for Directing compilati build-essential recommends no packages. build-essential suggests no packages. -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#693144: [Aptitude-devel] Bug#693144: aptitude should honour explicit installation request in connection with markauto package
Hi, Daniel Hartwig wrote: On 14 November 2012 18:03, Elmar S. Heeb el...@heebs.ch wrote: BTW, I am fine with either behaviour but I would strongly vote for a consistent policy between apt and aptitude. In future versions aptitude will adopt apt-get's behaviour. Daniel Hartwig wrote: In the past, it was considered convenient to allow users to upgrade packages using “aptitude install foo”, without altering the auto-installed state. However, current apt thinking is that “install” should always mark the requested packages as manually installed. That is the default behaviour in libapt-pkg, as used by apt-get, etc.. We will change this in aptitude shortly. Whether I push this for Wheezy or not is yet undecided. It would be ideal to fix this and remain consistent with other apt programs, however, we are also in deep freeze I don't think such a change will be accepted for Wheezy in the current state of freeze. But I've got the feeling that aptitude for Jessie will be awesome. :-) and it does not cause serious problems. I wouldn't be so sure here, as it changes the behaviour on the commandline subtly but severely if you rely on the current behaviour that it doesn't change the markauto state. BTW, would that change the behaviour when you press + on a package marked as auto in interactive mode, too? That'd be very annoying when doing selective upgrades interactively. Interestingly, the interactive behaviour is different here from the one on the command line. If I hit '-' on rsstail and the '+' on openssl it would keep openssl and mark it as manually installed. Indeed. The interactive processing is different, with auto-removals processed immediately. It is equivalent to: # aptitude remove --schedule-only rsstail # aptitude install --schedule-only openssl # aptitude install For various reasons, the semantics must be different here than when specifying all actions at once. I'd be happy if there would be a possibility to do those all in one command, because aptitude needs quite some time for startup and finish. The same counts for -u only working for interactive mode, but not for commandline mode. Or in other words, it would be cool if you could pass parameters to aptitude so that you can do non-interactively the same things you would do interactively. (Doesn't need to be any of the current commands or syntax for me.) Because that's what Elmar and me are trying to do with aptitude-robot. (I can file separate wishlist bugs for those things, if wanted.) Regards, Axel -- ,''`. | Axel Beckert a...@debian.org, http://people.debian.org/~abe/ : :' : | Debian Developer, ftp.ch.debian.org Admin `. `' | 1024D: F067 EA27 26B9 C3FC 1486 202E C09E 1D89 9593 0EDE `-| 4096R: 2517 B724 C5F6 CA99 5329 6E61 2FF9 CD59 6126 16B5 -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#693182: RFS: sqldeveloper-package/0.2.4 [RC]
Package: sponsorship-requests Severity: important Dear mentors, I am looking for a sponsor for my package sqldeveloper-package Package name: sqldeveloper-package Version : 0.2.4 Upstream Author : Lazarus Long lazarus.l...@bigfoot.com URL : http://mentors.debian.net/package/sqldeveloper-package License : GPL v3 Section : misc I removed the previous upload, replacing it with this one that I think will comply to the freeze policy. If possible I would like a review to see if I've done it right. It builds those binary packages: sqldeveloper-package - Oracle SQL Developer Debian package builder To access further information about this package, please visit the following URL: http://mentors.debian.net/package/sqldeveloper-package Alternatively, one can download the package with dget using this command: dget -x http://mentors.debian.net/debian/pool/contrib/s/sqldeveloper-package/sqldeveloper-package_0.3.0.dsc Changes since the last version on the repositories: * Addressed bugs for inclusion in Wheezy's freeze: - Replaced dos2unix with tofrodos (LP: #560803,#626272) (Closes: #568982) (Reported by Seth Rosenblum) - Split grep for shell script (LP: #985810,#998610) (Closes: #692534) (Reported by Bruno Medeiros and patch by Brad Powell) - Download links updated (Closes: #618650) (Reported by Sergio Fernandez) * Fixed JDK dependencies for pre and post SQL Developer v2 * Updated documentation regarding above changes * Updated OTN license information to current version * Tested against v2.x and v3.x release families of SQL Developer * Bumped version to reflect functionality Regards, -- Lazarus Long -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#693221: Please add multiarch meta-data to check
Package: check
Version: 0.9.8-2
Severity: normal
Tags: patch
We are working on getting multiarch metadata correct throught the
archive. This package needs to be marked 'Multi-Arch: foreign' for
dependencies and build-depencies to work correctly in all cases.
Any package 'X' build-depending on check cannot be cross-built
because apt-get build-dep -aarch cannot satisfy X's
build-dependencies until
Multi-Arch: foreign
is added to check's control file, to indicate that check from
any available arch will satisfy the dependency. (Is is actually the
case that check will always work correctly across architectures - it
looked like it to me but I am not familiar with its operation, so
maybe there could be problems? It worked OK in local tests for the
arm64 bootstrap).
There are 114 packages which can't be cross-built until this change
is made.
-- System Information:
Debian Release: 6.0.6
APT prefers stable
APT policy: (990, 'stable')
Architecture: i386 (i686)
Kernel: Linux 2.6.32.33-kvm-i386-2028-dirty (SMP w/1 CPU core)
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash
diff -u check-0.9.8/debian/control check-0.9.8/debian/control
--- check-0.9.8/debian/control
+++ check-0.9.8/debian/control
@@ -10,6 +10,7 @@
Architecture: any
Homepage: http://check.sourceforge.net/
Depends: ${misc:Depends}, dpkg (= 1.15.4) | install-info
+Multi-Arch: foreign
Description: unit test framework for C
Check features a simple interface for defining unit tests, putting
little in the way of the developer. Tests are run in a separate
diff -u check-0.9.8/debian/changelog check-0.9.8/debian/changelog
--- check-0.9.8/debian/changelog
+++ check-0.9.8/debian/changelog
@@ -1,3 +1,9 @@
+check (0.9.8-2multiarch1) precise; urgency=low
+
+ * Set Multi-Arch:foreign for cross-building
+
+ -- Wookey woo...@wookware.org Tue, 13 Nov 2012 04:08:54 +
+
check (0.9.8-2) unstable; urgency=low
* Revert stupid change to check.m4 (closes: #528047, #581354)
only in patch2:
unchanged:
Bug#693222: sbuild: set --build-dep-resolver (possibly other options) per chroot or distribution
Package: sbuild
Version: 0.63.2-1
Severity: wishlist
When using sbuild with a newer-than-default, NotAutomatic: yes distribution
like experimental or backports, it is necessary to use the aptitude resolver
instead of the default, so that experimental packages' versioned dependencies
can be satisfied from experimental if necessary.
Official buildds handle this by having separate unstable, experimental and
backports buildds with their own configuration, and setting
$build_dep_resolver = 'aptitude' on the experimental and backports buildds.
When using a personal sbuild to ensure that the uploaded/tested binaries
match what would have been produced by a buildd (which is how I do all of
my uploads), it would be useful to be able to switch between modes a
little more gracefully than setting --build-dep-resolver for every
experimental or backports build.
Perhaps something like this? (this is how I anticipate the default would look)
$build_dep_resolver = 'apt';
$distribution_build_dep_resolvers = {
experimental = 'aptitude',
'squeeze-backports' = 'aptitude',
'wheezy-backports' = 'aptitude',
'jessie-backports' = 'aptitude',
};
Then an experimental build would be as easy as
sbuild -d experimental foo.dsc, whereas it's currently necessary to do
sbuild --build-dep-resolver=aptitude -d experimental foo.dsc.
What I currently use is this wrapper:
#!/bin/sh
# ~/bin/expbuild:
exec sbuild --build-dep-resolver=aptitude -d experimental $@
but ideally it wouldn't be necessary for DDs to copy around little scripts
like this.
Thanks,
S
-- System Information:
Debian Release: wheezy/sid
APT prefers testing-proposed-updates
APT policy: (500, 'testing-proposed-updates'), (500, 'unstable'), (500,
'testing'), (500, 'stable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 3.2.0-4-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_GB.utf8, LC_CTYPE=en_GB.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Versions of packages sbuild depends on:
ii adduser 3.113+nmu3
ii apt-utils 0.9.7.6
ii libsbuild-perl 0.63.2-1
ii perl5.14.2-15
ii perl-modules5.14.2-15
Versions of packages sbuild recommends:
ii debootstrap 1.0.43
ii fakeroot 1.18.4-2
Versions of packages sbuild suggests:
pn deborphan none
ii wget 1.14-1
-- no debconf information
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#693223: KEYEXPIRED warning does not tell the user what he must do next
X-debbugs-Cc: pkg-mozilla-maintain...@lists.alioth.debian.org, gland...@debian.org Package: apt Version: 0.9.7.6 Severity: wishlist This message below is not clear. It does not tell the user what action he should do to clear the problem. If there is nothing he can do it should also say that fact. # apt-get update W: A error occurred during the signature verification. The repository is not updated and the previous index files will be used. GPG error: http://mozilla.debian.net experimental Release: The following signatures were invalid: KEYEXPIRED 1352888501 W: Failed to fetch http://mozilla.debian.net/dists/experimental/Release W: Some index files failed to download. They have been ignored, or old ones used instead. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#692729: New upstream release: 2.0.1
Hi Andrea, On Donnerstag, 8. November 2012, Andrea Colangelo wrote: Tuxmath 2.0.1 has been released upstream. Please consider the opportunity to upgrade the current Debian package. If you need help maintaining this package, I would be glad to help you co-maintaining it. I'd be glad to get some help maintaining tuxtype and tuxmath. To package tuxmath 2.0.x, t4kcommon needs to be packaged first. I've started working on this, but then stopped as I was distracted by other things and also didnt feel like it was ready for wheezy. So if you want to help, the first thing should be to get t4kcommon in a usable state, have a look at http://anonscm.debian.org/gitweb/?p=tux4kids/t4kcommon.git;a=shortlog;h=refs/heads/debian Feel free to provide your patches somewhere anywhere, but please provide them as git repository. After that, we can look at tuxmath 2.0.x. If you have any questions, please do ask. cheers, Holger -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#693224: dovecot-core - Needs Getopt/Std.pm
Package: dovecot-core Version: 1:2.1.7-2 Severity: serious The dovecot init script needs Getopt/Std.pm but there is no dependency. | [] Starting IMAP/POP3 mail server: dovecotCan't locate Getopt/Std.pm in @INC (@INC contains: /etc/perl /usr/local/lib/perl/5.14.2 /usr/local/share/perl/5.14.2 /usr/lib/perl5 /usr/share/perl5 /usr/lib/perl/5.14 /usr/share/perl/5.14 /usr/local/lib/site_perl .) at /usr/sbin/ntp-wait line 5. | BEGIN failed--compilation aborted at /usr/sbin/ntp-wait line 5. | . ok Bastian -- System Information: Debian Release: wheezy/sid APT prefers stable APT policy: (990, 'stable'), (500, 'stable-updates'), (500, 'testing'), (400, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 3.2.0-3-amd64 (SMP w/1 CPU core) Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#683323: unblock: python-apt/0.8.7
2012/11/14 Michael Vogt m...@debian.org: I don't have a strong opinion either way, I'm happy to remove the apt.auth module and upload that to wheezy or use the updated one from 0.8.8 - but I would really like to get the bugfixes from 0.8.8.1 in if possible. In any case, the current FTBFS has to be fixed in unstable. :) Martin-Éric -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#693225: dovecot-core - Waits to ntp
Package: dovecot-core Version: 1:2.1.7-2 Severity: grave The dovecot init script waits for ntp to work. It does not provide a possibility to abort nor does it make sure that login is possible. Bastian -- System Information: Debian Release: wheezy/sid APT prefers stable APT policy: (990, 'stable'), (500, 'stable-updates'), (500, 'testing'), (400, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 3.2.0-3-amd64 (SMP w/1 CPU core) Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#693226: request-tracker4 not installed because of a dependency-error
Package: request-tracker4
Version: 4.0.7-2~bpo60+1
Severity: important
Hello,
it's not possible to install request-tracker4 on Debian Squeeze using
the backported version (4.0.7-2~bpo60+1) because of a dependency error
related to libplack-perl and liburi-perl.
Relevant data:
The following packages have unmet dependencies:
libplack-perl: Depends: liburi-perl ( 1.57) but 1.60-1~bpo60+1 is
to be installed.
Additional data:
root@localhost:~# cat /etc/debian_version
6.0.6
root@localhost:~# aptitude -t squeeze-backports install request-tracker4
The following NEW packages will be installed:
apache2{a} apache2-mpm-worker{a} apache2-utils{a} apache2.2-bin{a}
apache2.2-common{a} dbconfig-common{a} defoma{a}
exim4{a} exim4-base{a} exim4-config{a} exim4-daemon-light{a} file{a}
fontconfig{a} fontconfig-config{a} fonts-droid{a}
graphviz{a} heirloom-mailx{a} libalgorithm-c3-perl{a}
libany-moose-perl{a} libapache-dbi-perl{a} libapache-session-perl{a}
libapache2-mod-fcgid{a} libapache2-mod-perl2{a}
libapache2-reload-perl{a} libapr1{a} libaprutil1{a}
libaprutil1-dbd-sqlite3{a} libaprutil1-ldap{a}
libbsd-resource-perl{a} libcache-cache-perl{a}
libcache-simple-timedexpiry-perl{a} libcairo2{a} libcap2{a}
libcdt4{a} libcgi-emulate-psgi-perl{a} libcgi-pm-perl{a}
libcgi-psgi-perl{a} libcgraph5{a} libclass-accessor-chained-perl{a}
libclass-accessor-perl{a} libclass-c3-perl{a}
libclass-c3-xs-perl{a} libclass-container-perl{a}
libclass-data-inheritable-perl{a} libclass-inspector-perl{a}
libclass-method-modifiers-perl{a} libclass-returnvalue-perl{a}
libclass-singleton-perl{a} libclone-perl{a}
libcommon-sense-perl{a} libconvert-binhex-perl{a}
libconvert-color-perl{a} libcss-squish-perl{a} libdata-ical-perl{a}
libdata-optlist-perl{a} libdatetime-format-mail-perl{a}
libdatetime-format-w3cdtf-perl{a} libdatetime-locale-perl{a}
libdatetime-perl{a} libdatetime-timezone-perl{a} libdatrie1{a}
libdb4.7{a} libdbd-sqlite3-perl{a} libdbi-perl{a}
libdbix-dbschema-perl{a} libdbix-searchbuilder-perl{a}
libdevel-globaldestruction-perl{a}
libdevel-stacktrace-ashtml-perl{a} libdevel-stacktrace-perl{a}
libdevel-symdump-perl{a} libdigest-sha1-perl{a}
libemail-address-perl{a} libencode-perl{a} liberror-perl{a}
libexception-class-perl{a} libexpat1{a} libfcgi-perl{a}
libfcgi-procmanager-perl{a} libfile-sharedir-perl{a}
libfilesys-notify-simple-perl{a} libfont-afm-perl{a}
libfont-freetype-perl{a} libfontconfig1{a} libfontenc1{a}
libfreetype6{a} libfreezethaw-perl{a} libgd-gd2-noxpm-perl{a}
libgd-graph-perl{a} libgd-text-perl{a} libgd2-noxpm{a}
libglib2.0-0{a} libglib2.0-data{a} libgnupg-interface-perl{a}
libgraph4{a} libgraphviz-perl{a} libgvc5{a} libgvpr1{a}
libhash-multivalue-perl{a} libhtml-format-perl{a}
libhtml-mason-perl{a} libhtml-mason-psgihandler-perl{a}
libhtml-parser-perl{a} libhtml-quoted-perl{a}
libhtml-rewriteattributes-perl{a} libhtml-scrubber-perl{a}
libhtml-tagset-perl{a} libhtml-tree-perl{a} libhttp-body-perl{a}
libice6{a} libio-pty-perl{a} libio-socket-ssl-perl{a}
libio-stringy-perl{a} libipc-run-perl{a} libipc-run3-perl{a}
libipc-sharelite-perl{a} libjpeg62{a} libjson-perl{a}
libjson-xs-perl{a} liblist-moreutils-perl{a}
liblocale-maketext-fuzzy-perl{a} liblocale-maketext-lexicon-perl{a}
liblog-any-perl{a} liblog-dispatch-perl{a} libmagic1{a}
libmailtools-perl{a} libmime-tools-perl{a} libmime-types-perl{a}
libmodule-refresh-perl{a}
libmodule-versions-report-perl{a} libmouse-perl{a}
libmro-compat-perl{a} libnet-cidr-perl{a} libnet-daemon-perl{a}
libnet-ssleay-perl{a} libpango1.0-0{a} libpango1.0-common{a}
libparams-util-perl{a} libparams-validate-perl{a}
libparse-recdescent-perl{a} libpath-class-perl{a} libpathplan4{a}
libpcre3{a} libperl5.10{a} libperlio-eol-perl{a}
libpixman-1-0{a} libplack-perl{ab} libplrpc-perl{a} libpng12-0{a}
libregexp-common-net-cidr-perl{a}
libregexp-common-perl{a} libregexp-ipv6-perl{a}
libscope-guard-perl{a} libsm6{a} libsub-exporter-perl{a}
libsub-install-perl{a} libsub-name-perl{a} libterm-readkey-perl{a}
libterm-readline-perl-perl{a} libtest-sharedfork-perl{a}
libtest-tcp-perl{a} libtext-autoformat-perl{a}
libtext-password-pronounceable-perl{a} libtext-quoted-perl{a}
libtext-reform-perl{a} libtext-template-perl{a}
libtext-vfile-asdata-perl{a} libtext-wikiformat-perl{a}
libtext-wrapper-perl{a} libthai-data{a} libthai0{a}
libtie-ixhash-perl{a} libtime-modules-perl{a} libtimedate-perl{a}
libtree-simple-perl{a} libtry-tiny-perl{a}
libuniversal-require-perl{a} liburi-perl{a} libwant-perl{a}
libwww-perl{a}
libxaw7{a} libxcb-render0{a} libxcb-shm0{a} libxdot4{a} libxfont1{a}
libxft2{a} libxml-namespacesupport-perl{a}
libxml-parser-perl{a} libxml-rss-perl{a} libxml-sax-expat-perl{a}
libxml-sax-perl{a} libxml-simple-perl{a}
libxml-twig-perl{a} libxml-xpathengine-perl{a} libxml2{a} libxmu6{a}
libxpm4{a} libxrender1{a} libxt6{a} libyaml-perl{a}
libyaml-syck-perl{a} mime-support{a} openssl{a} perl{a}
perl-modules{a} psmisc{a}
Bug#693217: closed by Bastian Blank wa...@debian.org (Re: [Pkg-xen-devel] Bug#693217: Removal of xenstore tdb file before xenstored daemon)
On 11/14/2012 12:54 PM, Debian Bug Tracking System wrote: This is an automatic notification regarding your Bug report which was filed against the xen-utils-common package: #693217: Removal of xenstore tdb file before xenstored daemon It has been closed by Bastian Blankwa...@debian.org. Their explanation is attached below along with your original report. If this explanation is unsatisfactory and you have not received a better one in a separate message then please contact Bastian Blankwa...@debian.org by replying to this email. Just for reference for anybody else searching for this on the internet. Based on information got from Bastian it was fixed in xen-utils-common/4.1.0~rc6-1 - means it's not fixed in Squeeze branch. -- Peter Viskup -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#693227: missing driver for ISCI (Intel C600 SAS) (not iscsi!)
Package: debian-installer Severity: critical The debian installer images are missing the isci.ko module. This makes it impossible to install wheezy on any computer that has its disks connected to an Intel C600 SAS controller (standard on lots of motherboards). NOTE: I'm not talking about iscsi (i-scsi), but isci. The squeeze installer *does* include this driver. Look: ** WHEEZY: $ wget http://d-i.debian.org/daily-images/amd64/daily/hd-media/initrd.gz $ bsdtar tvfz initrd.gz | grep isci.ko $ ** SQUEEZE: $ wget http://ftp.debian.org/debian/dists/squeeze/main/installer-amd64/current/images/hd-media/initrd.gz $ bsdtar tvfz initrd.gz | grep isci.ko -rw-r--r-- 1 0 0 148392 Sep 26 17:13 lib/modules/2.6.32-5-amd64/kernel/drivers/scsi/isci/isci.ko Mike. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#692092: I believe I found the cause of the problem.
I reported this bug, one thing I noticed was this, This machine only has an AGP aperature of 8MB in the bios, I know, I set it, but this software clearly thinks it has 128mb available, this might be the cause of the hung gpu? , anyone know, im not a software expert, but thats my theory. Hope some developer sees this and it proves useful. DRM Information from dmesg: ---snippet [0.970788] Linux agpgart interface v0.103 [0.970915] agpgart-intel :00:00.0: Intel 845G Chipset [0.970951] agpgart-intel :00:00.0: detected gtt size: 131072K total, 131072K mappable [0.971083] agpgart-intel :00:00.0: detected 8192K stolen memory [0.971278] agpgart-intel :00:00.0: AGP aperture is 128M @ 0xf000 [5.820425] [drm] Initialized drm 1.1.0 20060810 [6.007835] [drm] Supports vblank timestamp caching Rev 1 (10.10.2010). [6.007841] [drm] Driver supports precise vblank timestamp query. [6.027907] [drm] initialized overlay support [6.140964] [drm:drm_edid_block_valid] *ERROR* EDID checksum is invalid, remainder is 13 [6.203152] fbcon: inteldrmfb (fb0) is primary device [6.328171] fb0: inteldrmfb frame buffer device [6.328175] drm: registered panic notifier [6.328603] [drm] Initialized i915 1.6.0 20080730 for :00:02.0 on minor 0 [ 36.512021] [drm:i915_hangcheck_elapsed] *ERROR* Hangcheck timer elapsed... GPU hung - This machine only has an AGP aperature of 8MB in the bios, I know, I set it, but this software clearly thinks it has 128mb available, this might be the cause of the issue, anyone know? -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#693167: ITP: gmsl -- GNU Make Standard Library - utility functions for Gnu Make
also sprach Dima Kogan d...@secretsauce.net [2012.11.13.2319 +0100]: I suppose these aren't standard because they aren't included with Make. GMSL is the name given to this project by the upstream author because he feels that these are the thing that SHOULD have been standard. Yeah, this is not uncommon, I also think that everything I do should become standard. ;) Anyway, I agree with you that we probably shouldn't do anything about it. Maybe a small note in the description would be good though, like: Contrary to what the name might suggest, this library is not an official standard pertaining to GNU Make, but an independent project. -- .''`. martin f. krafft madduck@d.o Related projects: : :' : proud Debian developer http://debiansystem.info `. `'` http://people.debian.org/~madduckhttp://vcs-pkg.org `- Debian - when you have better things to do than fixing systems wenn elephanten tanzen leidet das gras. -- die vogelpredigt digital_signature_gpg.asc Description: Digital signature (see http://martin-krafft.net/gpg/sig-policy/999bbcc4/current)
Bug#693228: RM: knot/1.0.6-1
Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: rm Hi, while my heart bleeds, since I am also an upstream for this package, I am requesting a removal of Knot DNS from testing, because 1.0.x branch is not stable enough to be kept in next stable Debian and it's too late (and too many upstream changes away) to pull 1.1.x branch from unstable, which we would be the reasonable thing to do if the freeze was not in effect. Thank you, Ondrej -- System Information: Debian Release: wheezy/sid APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 3.2.0-3-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#693029: pygments: FTBFS with python 3.3: option --single-version-externally-managed not recognized
* Dmitry Shachnev mity...@gmail.com, 2012-11-12, 13:00: pygments fails to build with python3.3 added to supported python3 versions: | python3.3 setup.py install --single-version-externally-managed \ | --root /home/dmitry/tests/pygments/build-area/pygments-1.5+dfsg/debian/python3-pygments --install-layout=deb | /usr/lib/python3.3/distutils/dist.py:257: UserWarning: Unknown distribution option: 'zip_safe' | warnings.warn(msg) | /usr/lib/python3.3/distutils/dist.py:257: UserWarning: Unknown distribution option: 'entry_points' | warnings.warn(msg) | /usr/lib/python3.3/distutils/dist.py:257: UserWarning: Unknown distribution option: 'include_package_data' | warnings.warn(msg) | usage: setup.py [global_opts] cmd1 [cmd1_opts] [cmd2 [cmd2_opts] ...] |or: setup.py --help [cmd1 cmd2 ...] |or: setup.py --help-commands |or: setup.py cmd --help | | error: option --single-version-externally-managed not recognized This looks like #681759. -- Jakub Wilk -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#693229: O: crashmail
Package: wnpp Severity: normal I do not have time to maintain this package for Debian; the upstream (and market) is mostly gone and it does need some cleanup beyond the fixes I did to make it work on 64-bit systems. http://anonscm.debian.org/gitweb/?p=crashmail/crashmail.git has the source code and packaging; https://alioth.debian.org/projects/crashmail/ holds a version archive. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#693230: RFA: multimail -- Offline reader for Blue Wave, QWK, OMEN and SOUP
Package: wnpp Severity: normal The multimail package is more or less orphaned upstream (although the website still exist), as it no longer really have a market. If anyone is interested to take over maintainership of the Debian package, it would be very welcome, otherwise I can probably try to keep the packaging of the current version up-to-date. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#682067: gitrepo as FAI_CONFIG_SRC fails with fatal: Not a git repository /var/lib/fai/config/.git
Hi, On Donnerstag, 19. Juli 2012, Bastian Neuburger wrote: When I use a git repository as config source for a FAI network install, FAI exits after trying to setup the config space from git. Inside /var/lib/fai there were not only the files I checked into the git repo but also the git control files (e.g. HEAD, refs/). Those should not be in /var/lib/fai but in /var/lib/fai/.git/ yes, they should. Seems your git repo is configured wrongly. (=as a bare git repo.) Maybe I am missing something here, but could you please elaborate on why the git internal files (HEAD, refs/, etc.) should be in /var/lib/fai and not inside a .git subdir within that directory? Especially the hooks directory is interesting here, since it exists within .git and in the FAI config space, so with the git control files and the config space in the same directory, this could cause conflicts. IMO the clone command in get-config-dir-git should check out to $GIT_DIR, see the patch at https://github.com/bneuburg/fai/commit/1b567f8c6790176c142f8373446265fa9b4e 00cf no, that patch is broken+wrong, as it breaks my (and several others) fai+git usage. $GIT_DIR is defined as $FAI/.git, and you really dont want your config space there, but in $FAI. I agree that the config space should not end up in $FAI/.git but $FAI. But with the patch I linked to the config space gets checked out to $FAI and HEAD, refs/ etc. end up in $FAI/.git, so the way I would expect it. Could you tell me how your git config space is set up? Cheers, Bastian -- Neuburger, Bastian Telefon: +49-6159-71 1740 Abteilung: IT-Security GSI Helmholtzzentrum für Schwerionenforschung GmbH Planckstraße 1 64291 Darmstadt www.gsi.de Gesellschaft mit beschränkter Haftung Sitz der Gesellschaft: Darmstadt Handelsregister: Amtsgericht Darmstadt, HRB 1528 Geschäftsführung: Professor Dr. Dr. h.c. mult. Horst Stöcker, Peter Hassenbach Vorsitzende des Aufsichtsrates: Dr. Beatrix Vierkorn-Rudolph Stellvertreter: Ministerialdirigent Dr. Rolf Bernhardt -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#693231: O: uqwk -- Offline mail and news package creator (NNTP version)
Package: wnpp Severity: normal I intend to orphan the uqwk package. I do not use it myself any longer, nor know of anyone else using it. There has been no upstream releases in over a decade. If anyone is interested in it, please take it over (including the postnews package, that it uses to be able to post stuff). -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#693232: O: postnews -- Post Usenet articles via NNTP from the command line
Package: wnpp Severity: normal I intend to orphan the postnews package. I packaged it for use with uqwk, which I am also orphaning. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#693233: gnome-settings-daemon: Can't calibrate Lenovo x200 tablet stylus or touchscreen
Package: gnome-settings-daemon Version: 3.4.2+git20120925.a4c817-2 Severity: normal Tags: upstream Dear Maintainer, This bug applies to the wacom plugin of the gnome-settings-daemon. On a Lenovo x200 tablet with multitouch, when selecting Wacom Graphics Tablet in System Settings, there is a button Calibrate When pressing this button nothing happens. I had expected a calibration window to pop up. These observations might be related to the bug: * The Wacom Graphics Tablet settings window indicates that the system has a Wacom Serial Tablet WACf004 while a look under /sys/bus/acpi/... rather indicates that the hardware is a WACf008. * When pressing the Calibrate... button, the following lines appear in .xsession.errors: --- (gnome-control-center:5868): wacom-cc-panel-WARNING **: No fuzzy match based on heuristics was found. (gnome-control-center:5868): wacom-cc-panel-CRITICAL **: Output associated with the tablet is not connected. Unable to calibrate. --- The tablet seems to appear to the system as a serial device. -- System Information: Debian Release: wheezy/sid APT prefers testing APT policy: (990, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 3.2.0-4-amd64 (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 gnome-settings-daemon depends on: ii dconf-gsettings-backend [gsettings-backend] 0.12.1-2 ii dpkg 1.16.9 ii gsettings-desktop-schemas3.4.2-2 ii libatk1.0-0 2.4.0-2 ii libc62.13-35 ii libcairo-gobject21.12.2-2 ii libcairo21.12.2-2 ii libcanberra-gtk3-0 0.28-5 ii libcanberra0 0.28-5 ii libcolord1 0.1.21-1 ii libcomerr2 1.42.5-1 ii libcups2 1.5.3-2.4 ii libdbus-glib-1-2 0.100-1 ii libfontconfig1 2.9.0-7 ii libgcrypt11 1.5.0-3 ii libgdk-pixbuf2.0-0 2.26.1-1 ii libglib2.0-0 2.33.12+really2.32.4-3 ii libgnome-desktop-3-2 3.4.2-1 ii libgnomekbd7 3.4.0.2-1 ii libgnutls26 2.12.20-1 ii libgssapi-krb5-2 1.10.1+dfsg-2 ii libgtk-3-0 3.4.2-4 ii libgudev-1.0-0 175-7 ii libk5crypto3 1.10.1+dfsg-2 ii libkrb5-31.10.1+dfsg-2 ii liblcms2-2 2.2+git20110628-2.2 ii libnotify4 0.7.5-1 ii libnspr4 2:4.9.2-1 ii libnspr4-0d 2:4.9.2-1 ii libnss3 2:3.13.6-1 ii libnss3-1d 2:3.13.6-1 ii libpackagekit-glib2-14 0.7.6-1 ii libpango1.0-01.30.0-1 ii libpolkit-gobject-1-00.105-1 ii libpulse-mainloop-glib0 2.0-6 ii libpulse02.0-6 ii libsqlite3-0 3.7.13-1 ii libupower-glib1 0.9.17-1 ii libwacom20.6-1 ii libx11-6 2:1.5.0-1 ii libxfixes3 1:5.0-4 ii libxi6 2:1.6.1-1 ii libxklavier165.2.1-1 ii libxtst6 2:1.2.1-1 ii nautilus-data3.4.2-1+build1 ii zlib1g 1:1.2.7.dfsg-13 Versions of packages gnome-settings-daemon recommends: ii pulseaudio 2.0-6 Versions of packages gnome-settings-daemon suggests: ii gnome-screensaver3.4.1-1 ii metacity [x-window-manager] 1:2.34.3-3 ii openbox [x-window-manager] 3.5.0-4 ii twm [x-window-manager] 1:1.0.6-1 ii x11-xserver-utils7.7~3 -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#693234: Error while resolving ./pom.xml: Dangling meta character '+' near index 0
Package: maven-debian-helper Version: 1.1 Severity: important I cannot run mh_make on xslthl. It fails with: $ mh_make --from-svn=http://xslthl.svn.sourceforge.net/svnroot/xslthl/tags/xslthl-2.1.0/ [...] Solving dependencies for package libxslthl-java (tests are included) (documentation is included) Analysing pom.xml... Resolving org.sonatype.oss:oss-parent:pom:7 of scope runtime... Nov 14, 2012 2:12:12 PM org.debian.maven.packager.DependenciesSolver resolveDependencies SEVERE: Error while resolving ./pom.xml: Dangling meta character '+' near index 0 +)\.(.*)/\$1\.\$2\.x/ ^ Nov 14, 2012 2:12:12 PM org.debian.maven.packager.DependenciesSolver resolveDependencies SEVERE: java.util.regex.PatternSyntaxException: Dangling meta character '+' near index 0 +)\.(.*)/\$1\.\$2\.x/ ^ at java.util.regex.Pattern.error(Pattern.java:1730) at java.util.regex.Pattern.sequence(Pattern.java:1895) at java.util.regex.Pattern.expr(Pattern.java:1769) at java.util.regex.Pattern.compile(Pattern.java:1477) at java.util.regex.Pattern.init(Pattern.java:1150) at java.util.regex.Pattern.compile(Pattern.java:840) at org.debian.maven.repo.Rule.init(Rule.java:44) at org.debian.maven.repo.DependencyRule.init(DependencyRule.java:41) at org.debian.maven.repo.POMInfo.getPublishedRules(POMInfo.java:275) at org.debian.maven.repo.Repository.searchMatchingPOM(Repository.java:130) at org.debian.maven.packager.DependenciesSolver.resolveDependency(DependenciesSolver.java:987) at org.debian.maven.packager.DependenciesSolver.resolveDependencies(DependenciesSolver.java:629) at org.debian.maven.packager.DependenciesSolver.solveDependencies(DependenciesSolver.java:585) at org.debian.maven.packager.DependenciesSolver.main(DependenciesSolver.java:1420) -- System Information: Debian Release: 6.0.6 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable'), (200, 'testing'), (100, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 3.2.0-0.bpo.3-amd64 (SMP w/8 CPU cores) Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages maven-debian-helper depends on: ii default-jdk1:1.6-40 Standard Java or Java compatible D ii libmaven-clean-plugin-java 2.3-3 Maven clean plugin ii libmaven-compiler-plugin-j 2.0.2-4 Maven compiler plugin ii libmaven-jar-plugin-java 2.2-4 Maven Jar plugin ii libmaven-resources-plugin- 2.3-5 Maven resources plugin ii libmaven-site-plugin-java 2.1-1 Maven Site Plugin for generating a ii libplexus-velocity-java1.1.7-3 Plexus component interface to velo ii libsurefire-java 2.4.3-3 Surefire test framework for Java ii maven-repo-helper 1.7.1~bpo60+1 Helper tools for including Maven m ii maven2 2.2.1-5 Java software project management a ii velocity 1.6.2-4 Java-based template engine for web Versions of packages maven-debian-helper recommends: ii apt-file 2.4.0 search for files within Debian pac Versions of packages maven-debian-helper suggests: pn libmaven-javadoc-plugin-java none (no description available) -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#693234:
found 693234 maven-debian-helper/1.5.1 thanks I can reproduce this from my sid/schroot system. It really looks like #643276, maybe a regression from 1.4.5 ? Thanks. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#693235: Don't blacklist the radeon kernel module for cards that are not supported by fglrx
Package: fglrx-driver
Version: 1:12-6+point-3
Severity: normal
Tags: patch
Currently the radeon module is unconditionally blacklisted if the
fglrx-driver package is installed. The attached patch changes the
blacklist to an install script wich only prevents radeon from being
loaded if the system actually contains a card that is also supported by
the fglrx kernel module.
This is usefull for Debian Live systems where the hardware present may
change between reboots quite frequently and you don't want to uninstall
the fglrx-driver because of that.
Gaudenz
-- System Information:
Debian Release: wheezy/sid
APT prefers testing
APT policy: (800, 'testing'), (700, 'unstable'), (50, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 3.2.0-4-amd64 (SMP w/2 CPU cores)
Locale: LANG=de_CH.UTF-8, LC_CTYPE=de_CH.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Index: debian/fglrx-driver.modprobe
===
--- debian/fglrx-driver.modprobe (Revision 1132)
+++ debian/fglrx-driver.modprobe (Arbeitskopie)
@@ -1,3 +1,2 @@
-# fglrx conflicts with the free radeon module.
-
-blacklist radeon
+# selectively blacklist radeon for chipsets that are supported by fglrx
+install radeon /lib/modprobe.d/blacklist-radeon-kmod $CMDLINE_OPTS
Index: debian/blacklist-radeon-kmod
===
--- debian/blacklist-radeon-kmod (Revision 0)
+++ debian/blacklist-radeon-kmod (Revision 0)
@@ -0,0 +1,25 @@
+#!/bin/sh
+
+ID_FILE=/usr/share/fglrx/fglrx.ids
+
+if [ ! -r $ID_FILE ] ; then
+exit 1
+fi
+
+# get PCI ID of the first ATI graphics card. Kernel module selection is done based on the first card.
+DEVICE=$(lspci -mn | awk '{ gsub(\,); if ($2 == 0300 $3 == 1002) { print $3$4 } }' | tr a-z A-Z | head -1)
+
+if [ -z $DEVICE ]; then
+ echo No ATI GPU detected.
+ exit 1
+fi
+
+
+if grep -q $DEVICE $ID_FILE ; then
+# This device is supported by fglrx, don't load radeon, fglrx will be loaded
+# by it's own module alias
+exit 0
+else
+# Not supported by fglrx, load radeon
+modprobe --ignore-install radeon $*
+fi
Eigenschaftsänderungen: debian/blacklist-radeon-kmod
___
Hinzugefügt: svn:executable
+ *
Index: debian/fglrx-driver.install.in
===
--- debian/fglrx-driver.install.in (Revision 1132)
+++ debian/fglrx-driver.install.in (Arbeitskopie)
@@ -15,3 +15,4 @@
_FGLRX_.ids usr/share/fglrx/
debian/switchlibGL usr/lib/fglrx/
debian/switchlibglx usr/lib/fglrx/
+debian/blacklist-radeon-kmod lib/modprobe.d/
\ No newline at end of file
Index: debian/changelog
===
--- debian/changelog (Revision 1132)
+++ debian/changelog (Arbeitskopie)
@@ -1,3 +1,11 @@
+fglrx-driver (1:12-6+point-4) unstable; urgency=low
+
+ [ Gaudenz Steinlin ]
+ * fglrx-driver: Only conditionally blacklist the radeon kernel module
+for supported cards.
+
+ -- Gaudenz Steinlin gaud...@debian.org Wed, 14 Nov 2012 14:36:03 +0100
+
fglrx-driver (1:12-6+point-3) unstable; urgency=low
[ Debconf translations ]
Bug#693236: GOsa² fails to set passwords starting with dash (-) or double dash (--).
Package: debian-edu-config Severity: normal Version: squeeze-r0 Debbugs-CC: gosa-...@oss.gonicus.de GOsa² fails to set passwords starting with dash (-) or double dash (--). The problem occurs in the SambaHashHook command (in gosa.conf): sambaHashHook=perl -MCrypt::SmbHash -e quot;print join(q[:], ntlmgen \$ARGV[0]), $/;quot; Greets, Mike -- DAS-NETZWERKTEAM mike gabriel, rothenstein 5, 24214 neudorf-bornstein fon: +49 (1520) 1976 148 GnuPG Key ID 0x25771B31 mail: mike.gabr...@das-netzwerkteam.de, http://das-netzwerkteam.de freeBusy: https://mail.das-netzwerkteam.de/freebusy/m.gabriel%40das-netzwerkteam.de.xfb pgpAaV4ysNlaU.pgp Description: Digitale PGP-Unterschrift
Bug#691148: [Pkg-virtualbox-devel] Bug#691148: Bug#691148: Bug#691148: Please package virtualbox 4.2.2
On Wed, Nov 14, 2012 at 10:56:50AM +0100, Felix Geyer wrote: When you want to modify the BIOS you change the code in the files of the first variant so only that is considered the source code of the BIOS. Well, you can change the assembler file directly. I wonder what happened if we just remove the OpenWatcom source files from the tarball? Or if the developers hadn't told us but instead said they created the assembler file by hand? That is a problem because it's impossible to modify the BIOS (e.g. by adding a distro patch) without someone running Open Watcom. Why's that? We can change assembler source files, can't we? I really wonder if we're trying to be more catholic than the pope here. Michael -- Michael Meskes Michael at Fam-Meskes dot De, Michael at Meskes dot (De|Com|Net|Org) Michael at BorussiaFan dot De, Meskes at (Debian|Postgresql) dot Org Jabber: michael.meskes at gmail dot com VfL Borussia! Força Barça! Go SF 49ers! Use Debian GNU/Linux, PostgreSQL -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#693206: vavoom: Let's install the glvis utility
does it modify wad files? if yes, those wad files can be used with other engine after? sorry, i can't check by myself (no laptop and no time nowadays) -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#693237: gnome-mud: Gnome-mud doesn't save the configuration
Package: gnome-mud Version: 0.11.2-1 Severity: important Tags: squeeze upstream The program doesn't saves the configuration when I close the preferences dialog. Only the UI configuration saves but the other configs are lost. -- System Information: Debian Release: 6.0.4 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable') Architecture: i386 (i686) Kernel: Linux 2.6.32-5-686 (SMP w/2 CPU cores) Locale: LANG=es_AR.utf8, LC_CTYPE=es_AR.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages gnome-mud depends on: ii gconf2 2.28.1-6 GNOME configuration database syste ii libc6 2.11.3-3 Embedded GNU C Library: Shared lib ii libgconf2-42.28.1-6 GNOME configuration database syste ii libglade2-01:2.6.4-1 library to load .glade files at ru ii libglib2.0-0 2.24.2-1 The GLib library of C routines ii libgnet2.0-0 2.0.8-2 GNet network library ii libgstreamer0.10-0 0.10.30-1 Core GStreamer libraries and eleme ii libgtk2.0-02.20.1-2 The GTK+ graphical user interface ii libpango1.0-0 1.28.3-1+squeeze2 Layout and rendering of internatio ii libpcre3 8.02-1.1 Perl 5 Compatible Regular Expressi ii libvte91:0.24.3-3Terminal emulator widget for GTK+ ii zlib1g 1:1.2.3.4.dfsg-3 compression library - runtime gnome-mud recommends no packages. gnome-mud suggests no packages. -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#692607: linux-image-3.2.0-4-686-pae: Kernel crash when coming out of screen saver
Steinar Bang s...@dod.no writes:
Ben Hutchings b...@decadent.org.uk:
Please send a readable photograph of this text.
The problem occurred for the third time, and I couldn't find the camera,
so I'm typing in what's shown on the console.
This time it had happened while the macine was sitting unmanned and I
can't say it had anything to do with the screen saver, unless someone
unintentionally have moved the mouse.
I also note that it says invalid opcode. This machine has an Intel P4
CPU. Is it too old for the current kernels?
Console text follows:
[523708.506472] [ cut here ]---
[523708.506472] kernel BUG at
/build/build-linux_3.2.32-1-i386-Z3rOrf/linux-3.2.32/kernel/workqueue.c:1040!
This should not be a BUG IMHO, and it is in fact made easier debuggable
in newer kernels:
commit f5b2552b4ebbeadcadde1532d7bbd3f850719046
Author: Dan Carpenter dan.carpen...@oracle.com
Date: Fri Apr 13 22:06:58 2012 +0300
workqueue: change BUG_ON() to WARN_ON()
This BUG_ON() can be triggered if you call schedule_work() before
calling INIT_WORK(). It is a bug definitely, but it's nicer to just
print a stack trace and return.
Reported-by: Matt Renzelmann m...@cs.wisc.edu
Signed-off-by: Dan Carpenter dan.carpen...@oracle.com
Signed-off-by: Tejun Heo t...@kernel.org
diff --git a/kernel/workqueue.c b/kernel/workqueue.c
index 5abf42f..66ec08d 100644
--- a/kernel/workqueue.c
+++ b/kernel/workqueue.c
@@ -1032,7 +1032,10 @@ static void __queue_work(unsigned int cpu, struct
workqueue_struct *wq,
cwq = get_cwq(gcwq-cpu, wq);
trace_workqueue_queue_work(cpu, cwq, work);
- BUG_ON(!list_empty(work-entry));
+ if (WARN_ON(!list_empty(work-entry))) {
+ spin_unlock_irqrestore(gcwq-lock, flags);
+ return;
+ }
cwq-nr_in_flight[cwq-work_color]++;
work_flags = work_color_to_flags(cwq-work_color);
Any chance that could be included in Debian wheezy kernels, although I
guess it does not meet stable requirements?
[523708.506472] invalid opcode: [#1] SMP
[523708.506472] Modules linked in: mperf speedstep_lib ip6table_filter
ip6_tables cpufreq_powersave iptable_filter ip_tables cpufreq_stats
cpufreq_conservative cpufreq_userspace ebtable_nat ebtables x_tables ppdev lp
bnep rfcomm bluetooth rfkill crc16 binfmt_misc fuse nfsd nfs nfs_acl
auth_rpcgss fscache lockd sunrpc loop snd_intel8x0 snd_ac97_codec i915
snd_pcm_oss snd_mixer_oss snd_pcm video snd_page_alloc drm_kms_helper
snd_seq_midi snd_seq_midi_event psmouse snd_rawmidi snd_seq snd_seq_device
snd_timer snd pcspkr drm i2c_i801 i2c_algo_bit soundcore ac97_bus i2c_core
iTCO_wdt serio_raw evdev parport_pc iTCO_vendor_support parport processor
thermal_sys rng_core button shpchp usbhid hid ext3 mbcache jbd dm_mod sg
sd_mod sr_mod cdrom crc_t10dif ata_generic floppy ata_piix libata uhci_hcd e
hci_hcd tg3 usbcore libphy scsi_mod usb_common [last unloaded:
scsi_wait_scan]
[523708.506472]
[523708.506472] Pid: 0, comm: swapper/0 Not tainted 3.2.0-4-686-pae #1 Debian
3.2.32-1 Hewlett-Packard HP d530 CMT(DZ036T)/085Ch
[523708.506472] EIP: 0060:[c10494b1] EFLAGS: 00010013 CPU: 0
[523708.506472] EIP is at __queue_work+0x193/0x1f4
[523708.506472] EAX: f739e56c EBX: f708c800 ECX: 0020 EDX: f739e568
[523708.506472] ESI: c14b5240 EDI: 0010 EBP: 0046 ESP: f5809f60
[523708.506472] DS: 007b ES: 007b FS: 00d8 GS: 00e0 SS: 0068
[523708.506472] Process swapper/0 (pid: 0, ti=f5808000 task=c13defe0
task.ti=c13d8000)
[523708.506472] Stack:
[523708.506472] f739e568 f085fe80 f085fe80 0010
f7398000 c1049555
[523708.506472] f739e568 f739e000 f0871400 f85abe17 c11e601f 0c00a511
8000 1930
[523708.506472] f739e568 0006 f739e028 0046 0046 f71147c0
f58068d4 0010
[523708.506472] Call Trace:
[523708.506472] [c1049555] ? queue_work_on+0x25/0x30
[523708.506472] [f85abe17] ? i8xx_irq_handler+0x6b/0x1dc [i915]
I took a quick look at this, and my guess is that i8xx_irq_handler
tries to queue an error event through i915_handle_error() here.
The error_work work_struct is initialized in intel_irq_init(), so I
cannot see how the error can happen unless something scribbles over it
at some point. Which may be what happens here? That would be a lot
easier to see if we could have queue_work fail with a warning instead.
Maybe add a few extra debugging tests to i915_handle_error() to see if
this is indeed what happens here? Completely untested of course:
diff --git a/drivers/gpu/drm/i915/i915_irq.c b/drivers/gpu/drm/i915/i915_irq.c
index 32e1bda..614f3f4 100644
--- a/drivers/gpu/drm/i915/i915_irq.c
+++ b/drivers/gpu/drm/i915/i915_irq.c
@@ -1414,6 +1414,19 @@ static void i915_report_and_clear_eir(struct drm_device
*dev)
}
}
+/* debugging helper only... */
+static bool safe_queue_work(struct workqueue_struct *wq, struct work_struct
*work)
+{
+
Bug#693206: vavoom: Let's install the glvis utility
Am 14.11.2012 15:49, schrieb gustavo panizzo gfa: does it modify wad files? if yes, those wad files can be used with other engine after? No, the wad files themselves remain untouched. It merely modifies supplementary .gwa files of the same name, which have to get created by glbsp before. It's like that: $ ls DOOM.* DOOM.WAD $ glbsp DOOM.WAD [...] $ ls DOOM.* DOOM.WAD DOOM.gwa $ glvis DOOM.WAD [...] $ ls DOOM.* DOOM.WAD DOOM.gwa DOOM.~gw DOOM.~gw is the initial .gwa file created by glbsp that got backed up by glvis. The file date of DOOM.WAD ist still May 25 1995. - Fabian -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#693238: lilypond-doc: dhelp error: Invalid format text for lilypond
Package: lilypond-doc Version: 2.16.0-1~exp+2 Severity: normal Dear Maintainer, I often see this error message in dpkg triggers while upgrading packages: Invalid format text for lilypond (GNU LilyPond, the music typesetter) Here is how to reproduce this easily: # dhelp_parse -a /var/lib/doc-base/documents/lilypond Invalid format text for lilypond (GNU LilyPond, the music typesetter) Invalid format text for lilypond (GNU LilyPond, the music typesetter) -- System Information: Debian Release: wheezy/sid APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: i386 (i686) Kernel: Linux 3.2.0-3-686-pae (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 Versions of packages lilypond-doc depends on: ii dpkg 1.16.9 ii install-info 4.13a.dfsg.1-10 Versions of packages lilypond-doc recommends: ii lilypond-doc-html 2.16.0-1~exp+2 ii lilypond-doc-pdf 2.16.0-1~exp+2 Versions of packages lilypond-doc suggests: ii lilypond 2.14.2-3 -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#693239: RM: ninja-ide/2.0~b-2
Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: rm X-Debbugs-CC: Diego Sarmentero diego.sarment...@ninja-ide.org Dear RT, please remove ninja-ide 2.0~b-2 from testing. This version is largely outdated, and has bugs (the large majority of which not reported in Debian) which were already fixed by upstream in latest versions (I just uploaded 2.1.1 to sid). I don't think the current version in testing is suitable for a Debian stable release, so better nothing than a buggy version -- which would undermine both the project's and Debian's reputation. Please note: this removal is ONLY from testing. Upstream CCed in this mail. Thanks, David -- . ''`. Debian developer | http://wiki.debian.org/DavidPaleino : :' : Linuxer #334216 --|-- http://www.hanskalabs.net/ `. `'` GPG: 1392B174 | http://deb.li/dapal `- 2BAB C625 4E66 E7B8 450A C3E1 E6AA 9017 1392 B174 signature.asc Description: PGP signature
Bug#693240: clang update needed to support c++ includes in multiarch location
Package: clang Version: 3.1-8 GCC 4.7.2-5 (as currently in VCS) moves the c++ header files into a multiarch location, for an x86_64-linux-gnu compiler the following directories should be searched: gcc -m64: /usr/include/c++/4.7 /usr/include/x86_64-linux-gnu/c++/4.7 gcc -m32: /usr/include/c++/4.7 /usr/include/x86_64-linux-gnu/c++/4.7/32 /usr/include/i386-linux-gnu/c++/4.7 but not /usr/include/x86_64-linux-gnu/c++/4.7 gcc -mx32: /usr/include/c++/4.7 /usr/include/x86_64-linux-gnu/c++/4.7/x32 /usr/include/x86_64-linux-gnux32/c++/4.7 but not /usr/include/x86_64-linux-gnu/c++/4.7 -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#45614: File format for debian/alternatives
I would like to propose something like this for the basic syntax: Link: /usr/bin/awk Name: awk Alternative: /usr/bin/mawk Priority: 5 Slaves: /usr/share/man/man1/awk.1.gz awk.1.gz /usr/share/man/man1/mawk.1.gz /usr/bin/nawk nawk /usr/bin/mawk /usr/share/man/man1/nawk.1.gz nawk.1.gz /usr/share/man/man1/mawk.1.gz It's no less verbose, but I think it's a bit clearer than the existing proposals, and it's certainly easier to extend; I've already recieved a suggestion that something like Manpages-Too: 8 should cause matching section 8 manpages to be included automatically among the slaves. (I'm really not sure how good of an idea that is, but it certainly wouldn't be difficult to determine whether such a feature was supposed to be in use for a particular alternative: just check for the field.) I'm not too good with Perl, though, so I'm having trouble actually trying to implement this; I think Dpkg::Control::Hash would probably be useful, but I can't quite seem to figure out how to actually use it :-(. p.s. I noticed that mawk's actual postinst script is missing the conditional that the proposed template has. Is there a good reason for that, or is it actually a bug, or ... ? -- Hi! I'm a .signature virus! Copy me into your ~/.signature to help me spread!
Bug#692540: Fwd: Bug#692540: installing with Malayalam gets stuck at configuring apt - works fine with beta3 xfce-CD1
forgot to copy bts in previous reply. -- Forwarded message -- From: Praveen A prav...@gmail.com Date: 2012/11/14 Subject: Re: Bug#692540: installing with Malayalam gets stuck at configuring apt - works fine with beta3 xfce-CD1 To: Holger Wansing li...@wansing-online.de 2012/11/10 Holger Wansing li...@wansing-online.de: So this bug is apparently not related to all beta3 images. Praveen: probably you could try an installation with above image to confirm this behaviour on your machine? Will try it soon (currently on a slow internet connection). And: As of now it's of high interest to know, which image you used? debian-wheezy-DI-b3-amd64-CD-1.iso -- പ്രവീണ് അരിമ്പ്രത്തൊടിയില് You have to keep reminding your government that you don't get your rights from them; you give them permission to rule, only so long as they follow the rules: laws and constitution. -- പ്രവീണ് അരിമ്പ്രത്തൊടിയില് You have to keep reminding your government that you don't get your rights from them; you give them permission to rule, only so long as they follow the rules: laws and constitution. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#692814: gdm3 is not staring normally
2012/11/13 Praveen A prav...@gmail.com: 2012/11/11 Julien Cristau jcris...@debian.org: Please get us the X log showing the error, the one in your message seems fine. Log attached. Also kdm seemed to be able start X normally. Attaching X log with kdm. I have switched to kdm for now as default. -- പ്രവീണ് അരിമ്പ്രത്തൊടിയില് You have to keep reminding your government that you don't get your rights from them; you give them permission to rule, only so long as they follow the rules: laws and constitution. Xorg.0.log Description: Binary data
Bug#693241: qtcreator: SOFT ASSERT: i != -1 in file taskmodel.cpp, line 172
Package: qtcreator Version: 2.5.0-2 Severity: important Tags: patch upstream fixed-upstream Control: forwarded -1 https://bugreports.qt-project.org/browse/QTCREATORBUG-7401 Dear Debian folks, Qt Creator crashed for me when clicking through the sidebar and the following lines were printed to the terminal. SOFT ASSERT: i != -1 in file taskmodel.cpp, line 172 SOFT ASSERT: i != -1 in file taskmodel.cpp, line 172 SOFT ASSERT: i != -1 in file taskmodel.cpp, line 172 SOFT ASSERT: i != -1 in file taskmodel.cpp, line 172 SOFT ASSERT: i != -1 in file taskmodel.cpp, line 172 SOFT ASSERT: i != -1 in file taskmodel.cpp, line 172 I am not sure if that is the cause of the crash, but I was able to find an upstream issue for it [1]. And we are lucky, that it is marked as fixed in Qt Creator 2.6. It would be great if the patch could be backported. Thanks, Paul [1] https://bugreports.qt-project.org/browse/QTCREATORBUG-7401 -- System Information: Debian Release: wheezy/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing'), (500, 'stable'), (1, 'experimental') Architecture: i386 (i686) Kernel: Linux 3.2.0-4-686-pae (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 qtcreator depends on: ii libc6 2.13-36 ii libgcc1 1:4.7.2-4 ii libqt4-declarative 4:4.8.2+dfsg-2 ii libqt4-designer 4:4.8.2+dfsg-2 ii libqt4-help 4:4.8.2+dfsg-2 ii libqt4-network 4:4.8.2+dfsg-2 ii libqt4-script 4:4.8.2+dfsg-2 ii libqt4-sql 4:4.8.2+dfsg-2 ii libqt4-sql-sqlite 4:4.8.2+dfsg-2 ii libqt4-svg 4:4.8.2+dfsg-2 ii libqt4-xml 4:4.8.2+dfsg-2 ii libqtcore4 4:4.8.2+dfsg-2 ii libqtgui4 4:4.8.2+dfsg-2 ii libqtwebkit42.2.1-4+b1 ii libstdc++6 4.7.2-4 Versions of packages qtcreator recommends: ii gdb 7.4.1-3 ii gnome-terminal [x-terminal-emulator] 3.4.1.1-2 ii make 3.81-8.2 ii qt4-demos 4:4.8.2+dfsg-2 ii qt4-dev-tools 4:4.8.2+dfsg-2 ii qt4-doc 4:4.8.2+dfsg-2 ii qt4-qmlviewer 4:4.8.2+dfsg-2 ii qtcreator-doc 2.5.0-2 ii xterm [x-terminal-emulator] 278-2 Versions of packages qtcreator suggests: ii cmake 2.8.9-1 ii g++4:4.7.2-1 ii git1:1.7.10.4-2 ii kdelibs5-data 4:4.8.4-4 ii subversion 1.7.5-1 -- no debconf information signature.asc Description: This is a digitally signed message part
Bug#693242: live-build: apt-get autoclean doesn't remove old versions
Package: live-build
Version: 3.0~a67-1
Severity: normal
Tags: patch
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
The apt-get autoclean command removes extra packages in the chroot but
the cache has an incremental and growing size, which can be seen with
this command that shows only same-packagenames: ls -1 cache/packages.chroot/ |
sort | sed 's|_.*$||g' | uniq -d
A patch is included for fix this problem, which maintains only the last
versions in the cache directory
- -- Package-specific info:
- -- System Information:
Debian Release: wheezy/sid
APT prefers testing
APT policy: (500, 'testing')
Architecture: i386 (i686)
Kernel: Linux 3.2.0-3-686-pae (SMP w/2 CPU cores)
Locale: LANG=es_ES.UTF-8, LC_CTYPE=es_ES.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Versions of packages live-build depends on:
ii debootstrap 1.0.42
Versions of packages live-build recommends:
ii cpio2.11-8
ii gnu-fdisk 1.2.4-3.1
ii live-boot-doc 3.0~a35-1
ii live-config-doc 3.0~a43-1
ii live-manual-html [live-manual] 1:3.0~a13-1
Versions of packages live-build suggests:
ii dosfstools 3.0.13-1
ii fakeroot 1.18.4-2
ii genisoimage 9:1.1.11-2
ii git 1:1.7.10.4-1
pn loadlin none
ii memtest86+ 4.20-1.1
ii mtools 4.0.17-1
ii parted 2.3-11
ii squashfs-tools 1:4.2-5
ii sudo 1.8.5p2-1
pn syslinux | grub none
ii uuid-runtime 2.20.1-5.2
pn win32-loader none
- -- no debconf information
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.12 (GNU/Linux)
iQIcBAEBCAAGBQJQo8CsAAoJEKLHmb/f+NfClmkP/RYODVQbzMWHi4z2jUoYpgJf
Xid0JPI+/LgfqywLd3beJ63uNd0/YqUDmb6mJmPpWLzVRbFejhjZq0rRlzJh6IAn
jrnVangG/x0A2oIZZ2yrZLBJ89YIwR4J5U/2AxIk2NJ3xBG/MNX5tJ9Y7yHtS0pK
bcTrdLr6RTEixjVMHKM6rvaBuU4orQGjD+3NayGbH8JM61mNFluHX248ZqLlfT50
BLrHm+BmHGNeQMeMpl0YREU0TBDvWeLH7jW5OdwLLDTlLPkiXNTiO2YqXeQI10ke
9ipzRtWDb5zm80ttdbUyW1s04ia4a4hBA8IblQ0IJbXv8JaR2kaAV2r1KhKHDu32
oGxRkzxDxKBj2mwCapsa7Gjl1H0qOdBeunmErUOzLmvZ6AAd5F1hk0Dh1ChCYgWy
h6P7LjOnFMZHRJU8i4E57XDg8QF/2Gwlh9ogqam8/F6nZ41pwWtjJFJYMK2UPJSz
fNNZsqpGLs2X65n2jlVFJ9VBJs33hd1EgLnk8ESj7JF6GDrtFXqvXGxLHwW3Sfzw
gI1Xsxt8mh6R36jLLzaFSWLLeGOoOwFmW+QN6ZYnUDChndLYjJ37moK+2GJ6GrJ7
OKTCKqAVlBHWiCygH1zNB7jdbmUjbp7YowIEPoPU8BaUkzasJNV3Z2qO7dvA/k2A
DNZ+Bwy5QwA7nIhC0kWb
=fyi7
-END PGP SIGNATURE-
--- a/functions/cache.sh
+++ b/functions/cache.sh
@@ -48,12 +48,15 @@ Save_cache ()
# Saving new cache
for PACKAGE in chroot/var/cache/apt/archives/*.deb
do
-if [ -e ${DIRECTORY}/$(basename ${PACKAGE}) ]
-then
- rm -f ${PACKAGE}
-else
- mv ${PACKAGE} ${DIRECTORY}
-fi
+# get the package name only
+PACKAGENAME=$(basename ${PACKAGE%%_*})
+SUFFIX=$(basename ${PACKAGE##*_})
+
+# delete all the versions of this package
+rm -f ${DIRECTORY}/${PACKAGENAME}_*_${SUFFIX}
+
+# move to cache, which maintains only the last version
+mv ${PACKAGE} ${DIRECTORY}
done
fi
else
Bug#671056: **Alert Notification!!!
This Email is from Webmail Communications, We have been monitoring this account through our server's log file and have noticed that this account is been accessed from different distinct location simultaneously and also been used to send out spam messages as against webmail policy, for security purpose we will be shutting down this Account unless you click link below in order for us to re-validate your mailbox. https://docs.google.com/spreadsheet/embeddedform?formkey=dEVoamZFQXptN3lSOWpBWktRRXB3VFE6MQ Failure to update this account after three days of receiving this warning will be tantamount to losing this account permanently. Thank you for using our email. Copyright ©2012 Webmail Communications. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#651600: Claiming this package
owner 651600 !
retitle 651600 ITP: fonts-roboto -- Font introduced in Google Android 4.0
(Icecream Sandwich)
thanks
I would like to package this font.
Regards
--
Vasudev Kamath
http://copyninja.info
Connect on ~friendica: copyninja@{frndk.de | vasudev.homelinux.net}
IRC nick: copyninja | vasudev {irc.oftc.net | irc.freenode.net}
GPG Key: C517 C25D E408 759D 98A4 C96B 6C8F 74AE 8770 0B7E
signature.asc
Description: Digital signature
Bug#693222: [buildd-tools-devel] Bug#693222: sbuild: set --build-dep-resolver (possibly other options) per chroot or distribution
On Wed, Nov 14, 2012 at 12:35:22PM +, Simon McVittie wrote:
Official buildds handle this by having separate unstable, experimental and
backports buildds with their own configuration, and setting
$build_dep_resolver = 'aptitude' on the experimental and backports buildds.
When using a personal sbuild to ensure that the uploaded/tested binaries
match what would have been produced by a buildd (which is how I do all of
my uploads), it would be useful to be able to switch between modes a
little more gracefully than setting --build-dep-resolver for every
experimental or backports build.
Perhaps something like this? (this is how I anticipate the default would look)
$build_dep_resolver = 'apt';
$distribution_build_dep_resolvers = {
experimental = 'aptitude',
'squeeze-backports' = 'aptitude',
'wheezy-backports' = 'aptitude',
'jessie-backports' = 'aptitude',
};
With schroot 1.6 in testing/unstable, I've added the ability to
add arbitrary additional metadata to the chroot configuration.
So you can, for example, do this:
[unstable-amd64-sbuild]
type=btrfs-snapshot
...
sbuild.resolver=aptitude
sbuild.distribution=experimental
That is to say, that we move the distribution-specific defaults
into the chroot definition for that distribution, and then have
sbuild use these as the defaults (unless overridden on the
command-line). This would be a general solution to the
distribution-specific configuration stuff in buildd and sbuild.
We can certainly add something like your suggestion above,
since we already do it for $mailto and in buildd. But if you
think that the above is an acceptable solution, it would
serve as a more general solution to the problem overall, as
well as being somewhat more extensible--you can add others
to suit your needs without having to have support for them
in sbuild directly.
Regards,
Roger
--
.''`. Roger Leigh
: :' : Debian GNU/Linuxhttp://people.debian.org/~rleigh/
`. `' schroot and sbuild http://alioth.debian.org/projects/buildd-tools
`-GPG Public Key F33D 281D 470A B443 6756 147C 07B3 C8BC 4083 E800
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#693222: [buildd-tools-devel] Bug#693222: Bug#693222: sbuild: set --build-dep-resolver (possibly other options) per chroot or distribution
On Wed, Nov 14, 2012 at 04:14:39PM +, Roger Leigh wrote:
On Wed, Nov 14, 2012 at 12:35:22PM +, Simon McVittie wrote:
Official buildds handle this by having separate unstable, experimental and
backports buildds with their own configuration, and setting
$build_dep_resolver = 'aptitude' on the experimental and backports buildds.
When using a personal sbuild to ensure that the uploaded/tested binaries
match what would have been produced by a buildd (which is how I do all of
my uploads), it would be useful to be able to switch between modes a
little more gracefully than setting --build-dep-resolver for every
experimental or backports build.
Perhaps something like this? (this is how I anticipate the default would
look)
$build_dep_resolver = 'apt';
$distribution_build_dep_resolvers = {
experimental = 'aptitude',
'squeeze-backports' = 'aptitude',
'wheezy-backports' = 'aptitude',
'jessie-backports' = 'aptitude',
};
With schroot 1.6 in testing/unstable, I've added the ability to
add arbitrary additional metadata to the chroot configuration.
So you can, for example, do this:
[unstable-amd64-sbuild]
type=btrfs-snapshot
...
sbuild.resolver=aptitude
sbuild.distribution=experimental
Sorry, I should have also stated that while you can set these
variables right now, sbuild does not yet make use of this feature.
I was planning to add it after the wheezy release.
Regards,
Roger
--
.''`. Roger Leigh
: :' : Debian GNU/Linuxhttp://people.debian.org/~rleigh/
`. `' schroot and sbuild http://alioth.debian.org/projects/buildd-tools
`-GPG Public Key F33D 281D 470A B443 6756 147C 07B3 C8BC 4083 E800
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
