Bug#698207: www.debian.org /debian-cd/ versus cdimage/archive/
Package: www.debian.org please disregard previous bug report that had wrong subject line. Hello, I find it confusing a bit that: Address http://cdimage.debian.org/debian-cd/6.0.5/amd64/ is 404 http://cdimage.debian.org/debian-cd/6.0.6/amd64/ only works while http://cdimage.debian.org/cdimage/archive/6.0.5/amd64/ works http://cdimage.debian.org/cdimage/archive/6.0.4/amd64/ works etc, all except: http://cdimage.debian.org/cdimage/archive/6.0.6/amd64/ 404 it would be much easier for navigation and bookmarking, if replacing all versions 6.0.5 6.0.6 etc would work. Pick one URL and stick to it. e.g.: http://cdimage.debian.org/cdimage/archive/6.0.4/amd64/ http://cdimage.debian.org/cdimage/archive/6.0.5/amd64/ http://cdimage.debian.org/cdimage/archive/6.0.6/amd64/ Proposed solution: simply make archive the better (universal, bookmarkable) URL, have it also host current version (like 6.0.6 now) and as for /debian-cd/ make it redirect or symlink into archive for now. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#698206: Pidgin hanged after undo ctrl-z in text area when composing a message
Package: www.debian.org Hello, I find it confusing a bit that: Address http://cdimage.debian.org/debian-cd/6.0.5/amd64/ is 404 http://cdimage.debian.org/debian-cd/6.0.6/amd64/ only works while http://cdimage.debian.org/cdimage/archive/6.0.5/amd64/ works http://cdimage.debian.org/cdimage/archive/6.0.4/amd64/ works all except: http://cdimage.debian.org/cdimage/archive/6.0.6/amd64/ 404 it would be much easier for navigation and bookmarking, if replacing all versions 6.0.5 6.0.6 etc would work. Pick one URL and stick to it. e.g.: http://cdimage.debian.org/cdimage/archive/6.0.4/amd64/ http://cdimage.debian.org/cdimage/archive/6.0.5/amd64/ http://cdimage.debian.org/cdimage/archive/6.0.6/amd64/ Proposed solution: simply make archive the better (universal, bookmarkable) URL, have it also host current version (like 6.0.6 now) and as for /debian-cd/ make it redirect or symlink into archive for now. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#697952: Please parse the X-Debian-Homepage field and display it as a link
Hi, Le 2013-01-11 22:09, Guido Günther a écrit : several teams maintain additional information about packages e.g. in the Wiki. It'd be great to have a linkt to this information available on the packges.qa.debian.org page. I'd propose to use a X-Debian-Homepage: field in debian/control for that and handle it similar to Homepage: for the upstream homepage: Shouldn't such enhancements go through the DEP process? I'm not meaning to stop your work. I find the idea very good. But I think we should bring it to wider audience to start a discussion. DEP looks the right place for it. -- Mehdi -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#698186: system clock / relogio do sistema
On Mon, Jan 14, 2013 at 19:50:19 -0300, RUBENS SAMPAIO DE OLIVEIRA JUNIOR wrote: Package: upgrade-reports Severity: normal En_US: Once updated the system to the SID, every time I start the system I have to run the command ntpdate-debian ntp.dlink.com.tw to adjust the date and time, as the system to be connected, automatically adds six hours. Is your system clock set to UTC or local time? What's the content of /etc/adjtime? Cheers, Julien signature.asc Description: Digital signature
Bug#698208: ruby1.9.1: potential thread deadlock after fork()
Package: ruby1.9.1 Version: 1.9.3.194-5 Severity: important Tags: upstream patch Dear Maintainer, There is a bug in the way the great VM lock is re-initialized after a fork() of a ruby process with multiple POSIX threads happens; the state of the Great VM Lock is only partially re-initialized, leading to a possible deadlock of the child process. We have seen this bug using Debian's version in a pool of heavily-forking resque workers. There is already a fix upstream in trunk (r38819), backported to 1.9.3 (r38832). The fix is a trivial one-liner. For a more detailed description of the issue together with the patch, please refer to ruby bug #7693[1]. Regards, Apollon [1] https://bugs.ruby-lang.org/issues/7693 -- System Information: Debian Release: 7.0 APT prefers testing-updates APT policy: (500, 'testing-updates'), (500, 'testing'), (90, 'unstable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.2.0-4-amd64 (SMP w/8 CPU cores) Locale: LANG=el_GR.UTF-8, LC_CTYPE=el_GR.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages ruby1.9.1 depends on: ii libc6 2.13-37 ii libruby1.9.1 1.9.3.194-5 ruby1.9.1 recommends no packages. Versions of packages ruby1.9.1 suggests: ii graphviz2.26.3-12 pn ri1.9.1 none pn ruby-switch none ii ruby1.9.1-dev 1.9.3.194-5 pn ruby1.9.1-examples none -- 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#695757: xserver-xorg-video-radeon: Memory leak in Xorg when using oxygen-gtk as gtk2 theme
On Mon, 2013-01-14 at 23:29 +0100, bluebubble wrote: Il 13/12/12 10:46, Michel Dänzer ha scritto: If yes, you'll need to investigate the leak with valgrind or some other tool for this. Note that such tools may not help on X server shutdown, as the X server may still clean up the memory at that point. I think you can get an intermittent leak report from valgrind by sending it some signal, but I don't remember the details. sorry if I'm a bit late with the response. I've run Xorg with valgrind using this command: /usr/bin/valgrind -v --track-origins=yes --leak-check=full --show-reachable=yes --log-file=/tmp/X.log /usr/bin/Xorg $@ Attached there is the log. [...] ==27767== LEAK SUMMARY: ==27767==definitely lost: 88,974 bytes in 367 blocks ==27767==indirectly lost: 68,924 bytes in 381 blocks ==27767== possibly lost: 0 bytes in 0 blocks ==27767==still reachable: 271,956 bytes in 2,656 blocks ==27767== suppressed: 0 bytes in 0 blocks As you can see, the X server hardly leaked any memory on exit. You really need to trigger valgrind to print information about where memory was allocated from while memory usage appears high during runtime. -- Earthling Michel Dänzer | http://www.amd.com Libre software enthusiast | Debian, X and DRI developer -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#698210: ITP: ruby-librarian -- a framework for writing bundlers
Package: wnpp Severity: wishlist Owner: Stig Sandbeck Mathisen s...@debian.org * Package name: ruby-librarian Version : 0.0.26 Upstream Author : Jay Feldblum yfeldb...@gmail.com * URL : https://github.com/yfeldblum/librarian * License : MIT Programming Lang: Ruby Description : a framework for writing bundlers Librarian is a framework for writing bundlers, which are tools that resolve, fetch, install, and isolate a project's dependencies, in Ruby. Librarian ships with Librarian-Chef, which is a bundler for your Chef-based infrastructure repositories. In the future, Librarian-Chef will be a separate project. A bundler written with Librarian will expect you to provide a specfile listing your project's declared dependencies, including any version constraints and including the upstream sources for finding them. Librarian can resolve the spec, write a lockfile listing the full resolution, fetch the resolved dependencies, install them, and isolate them in your project. A bundler written with Librarian will be similar in kind to Bundler, the bundler for Ruby gems that many modern Rails applications use. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#698189: swath: Buffer Overflow with console args is possible.
On Tue, Jan 15, 2013 at 6:44 AM, Dominik Maier domen...@gmail.com wrote: Buffer overflow because of strcpy with possibility to inject shellcode: swath mule -b [More than 20 to overflow and possibly inject shellcode.] emptyfile proplematic lines are: char stopstr[20]; if (muleMode) strcpy(stopstr,wbr); Instead, you should change the size of stopstr according to wbr. Even better would be simply to change the address of stopstr like char stopstr[20]; if (muleMode) stopstr = wbr; Thanks for the report. I've applied the fix upstream: http://linux.thai.net/websvn/wsvn/software.swath?op=compcompare[]=%2Ftrunk@237compare[]=%2Ftrunk@238 I'm estimating the risk to decide what to do in Debian. The use of Mule mode is quite rare, IMO. Regards, -- Theppitak Karoonboonyanan http://linux.thai.net/~thep/ -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#698209: ITP: librarian-puppet -- a bundler for your puppet infrastructure
Package: wnpp Severity: wishlist Owner: Stig Sandbeck Mathisen s...@debian.org * Package name: librarian-puppet Version : 0.9.7 Upstream Author : Tim Sharpe t...@github.com * URL : https://github.com/rodjek/librarian-puppet * License : MIT Programming Lang: Ruby Description : a bundler for your puppet infrastructure Librarian-puppet is a bundler for your puppet infrastructure. You can use librarian-puppet to manage the puppet modules your infrastructure depends on. It is based on Librarian, a framework for writing bundlers, which are tools that resolve, fetch, install, and isolate a project's dependencies. Librarian-puppet manages your modules/ directory for you based on your Puppetfile. Your Puppetfile becomes the authoritative source for what modules you require and at what version, tag or branch. Once using Librarian-puppet you should not modify the contents of your modules directory. The individual modules' repos should be updated, tagged with a new release and the version bumped in your Puppetfile. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#697994: i386 version of the fix?
On Tue, Jan 15, 2013 at 08:38:20AM +0800, jida...@jidanni.org wrote: Is there a i386.deb version of the fix?! Yes, it's in unstable. This bug is closed. https://buildd.debian.org/status/package.php?p=sysvinit 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#698211: segfault when start
Package: chromium Version: 22.0.1229.94~r161065+dfsg-0.1 Severity: grave romium [1]3051 segmentation fault chromium i Using Linux foothold.ru 2.6.32-5-amd64 #1 SMP Sun May 6 04:00:17 UTC 2012 x86_64 GNU/Linux Debug Report: __ $ chromium --debug # Env: # LD_LIBRARY_PATH=/usr/lib/chromium:/usr/lib/xulrunner-1.9.1 # PATH=/usr/lib/chromium:/usr/local/bin:/usr/bin:/bin:/usr/bin/X11:/usr/games #GTK_PATH= # CHROMIUM_USER_FLAGS= # CHROMIUM_FLAGS=--password-store=detect /usr/bin/gdb /usr/lib/chromium/chromium -x /tmp/chromiumargs.WEcehK 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/chromium/chromium...(no debugging symbols found)...done. (gdb) r Starting program: /usr/lib/chromium/chromium --password-store=detect [Thread debugging using libthread_db enabled] Using host libthread_db library /lib/x86_64-linux-gnu/libthread_db.so.1. [New Thread 0x7fffe5126700 (LWP 3816)] [New Thread 0x7fffe42d0700 (LWP 3817)] [New Thread 0x7fffe3acf700 (LWP 3818)] [New Thread 0x7fffe32ce700 (LWP 3819)] [New Thread 0x73678700 (LWP 3820)] [New Thread 0x7fffe2200700 (LWP 3821)] [New Thread 0x7fffe19ff700 (LWP 3822)] [New Thread 0x7fffe11fe700 (LWP 3823)] [New Thread 0x7fffe09fd700 (LWP 3824)] [New Thread 0x7fffdbfff700 (LWP 3825)] [New Thread 0x7fffdb7fe700 (LWP 3826)] [New Thread 0x7fffdaffd700 (LWP 3827)] [New Thread 0x7fffe01fc700 (LWP 3828)] [New Thread 0x7fffe01db700 (LWP 3829)] [New Thread 0x7fffe01ba700 (LWP 3830)] [New Thread 0x7fffda7fc700 (LWP 3832)] [New Thread 0x7fffd960f700 (LWP 3833)] Program received signal SIGSEGV, Segmentation fault. [Switching to Thread 0x7fffe01ba700 (LWP 3830)] 0x7fffec3ef0f5 in ?? () from /lib/x86_64-linux-gnu/libc.so.6 (gdb) bt full #0 0x7fffec3ef0f5 in ?? () from /lib/x86_64-linux-gnu/libc.so.6 No symbol table info available. #1 0x7fffec3ef2aa in ?? () from /lib/x86_64-linux-gnu/libc.so.6 No symbol table info available. #2 0x7fffec3abd67 in getaddrinfo () from /lib/x86_64-linux-gnu/libc.so.6 No symbol table info available. #3 0x7458e6ef in ?? () No symbol table info available. #4 0x74586ac7 in ?? () No symbol table info available. #5 0x7452e500 in ?? () No symbol table info available. #6 0x74528011 in ?? () No symbol table info available. #7 0x7fffedd92b50 in start_thread () from /lib/x86_64-linux-gnu/libpthread.so.0 No symbol table info available. #8 0x7fffec3cd70d in clone () from /lib/x86_64-linux-gnu/libc.so.6 No symbol table info available. #9 0x in ?? () No symbol table info available. (gdb) info register rax0x4c01216 rbx0x3e 62 rcx0x0 0 rdx0x7fffe01b8e40 140736953290304 rsi0x7fffe01b8e5c 140736953290332 rdi0x7fffe019afe0 140736953167840 rbp0x7fffe01b9620 0x7fffe01b9620 rsp0x7fffe019afe0 0x7fffe019afe0 r8 0x0 0 r9 0x7fffe01b8e50 140736953290320 r100x0 0 r110x2 2 r120x7fffe01b9570 140736953292144 r130x7fffe01b95e0 140736953292256 r140x7fffe01b8500 140736953287936 r150xfef8179b 4277671835 rip0x7fffec3ef0f5 0x7fffec3ef0f5 eflags 0x10246 [ PF ZF IF RF ] cs 0x33 51 ss 0x2b 43 ds 0x0 0 es 0x0 0 fs 0x0 0 gs 0x0 0 -- System Information: Debian Release: 6.0.5 APT prefers testing-proposed-updates APT policy: (500, 'testing-proposed-updates'), (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 2.6.32-5-amd64 (SMP w/24 CPU cores) Locale: LANG=ru_RU.UTF-8, LC_CTYPE=ru_RU.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages chromium depends on: ii chromium-inspector 21.0.1180.89~r154005-1 ii gconf-service 3.2.5-1+build1 ii libasound2 1.0.25-4 ii libatk1.0-0 2.4.0-2 ii libbz2-1.0 1.0.6-4 ii libc6 2.13-35 ii libcairo2 1.12.2-2 ii libcups21.5.3-1 ii libdbus-1-3 1.6.0-1 ii libevent-2.0-5 2.0.19-stable-3 ii libexpat1 2.1.0-1 ii libflac81.2.1-6 ii libfontconfig1 2.9.0-7 ii libfreetype62.4.9-1 ii libgcc1 1:4.7.2-4 ii libgconf-2-43.2.5-1+build1 ii libgcrypt11 1.5.0-3 ii libgdk-pixbuf2.0-0 2.26.1-1 ii libglib2.0-02.32.3-1 ii libgnome-keyring0
Bug#698019: libav: the effective GPL-licensed status of the binary packages should be clearly documented
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Le 14/01/2013 23:45, Francesco Poli a écrit : On Mon, 14 Jan 2013 11:13:48 +0100 Jonas Smedegaard wrote: Quoting Charles Plessy (2013-01-14 02:55:38) On Sat, Jan 12, 2013 at 11:43 PM, Francesco Poli (wintermute) I think that the effective licensing status of the binary packages (GPL-2+ or GPL-3+) should be explicitly and clearly documented in the comment at the beginning of the debian/copyright file and, probably, in the binary package long descriptions, as well. [...] Since currently there is no better place (at least, not one I am aware of) to carry these considerations and since I am convinced that such considerations are important, I still think that the comment should be kept in the debian/copyright file and clarified. Hi, I'm surprised it has not yet been pointed out, but I have always considered the right place to document copyright information for individual binary packages is package.copyright, which ends up as simply /u/s/d/package/copyright. I'm also surprised to not find it right away in either policy or devref. Anyway, man dh_installdocs at least doccuments the technical point. An additional README.Debian at least in the relevant -dev packages does not harm. Regards, thibaut. -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.12 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iQIcBAEBCAAGBQJQ9IbKAAoJEJOUU0jg3ChATuoQAMCR2IMvkL0N3zuYajUOG7a8 6kn5yEr1x0EfP05qGRU4xVjGKV+Xsx/o2fN9zsOhRdNeVSeYjTuuyrzd/RwwGquP FJq19UppiUxouOIcfP4tJ3KorjdlI7IyVZhtVBzd5czGO+PAnhisWVWvXC7kSP9a HwpIFLtouksCBIaaUHLoO/jWELq3X8Nme8npLSrCiqAFNjpigxDkVyp6sl0JwlrC opA7Rf64tc/0OBBgeh7azaYmK6ujoN5njuqCxavRzPE3duhblUeM4VBcxMk3LrTn GXgRHfVnmF/hGhHhfnRtUjHN7obO7Q7q/iXgQv/cOn3XEnH8m4G28HwiX5JwLyBN lIDpLtRzExI9Sc4dvvAolrqlg7x0GaA8w9/SkUu3guAhA4PvkmiFng5yekGs5DUi 5HafW94HSy2MrwOJc856T3ANGTPhspRkCzbIAK67nmz2TxPgLzUOUba9niot0bvw eMHRMmW7GnL0OrgC8xtwt6/xNsEmPV5lwovJueR1EAFC3MdYyAmE0MdZbhQp8aYE Pap4CIS3gH5vMKm0OofhvH2S0n2esLaJF3uBlmsrE/hocgUxYIYxDYwNd2Adxc2o X5yS6fzkWRDv/YgrfhQOqln5dI0Lm/nm2HajjoHYMxmFo+KcQsGd8lQ/9B+2ljQ6 DQkNjaWHyHs5IUHcUYlv =WhCJ -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#698212: ITP: gnomediaicons -- network icons scheme for Dia
Package: wnpp Severity: wishlist Owner: Mathieu Malaterre ma...@debian.org * Package name: gnomediaicons Version : 0.1 Upstream Author : Thiago Ribeiro ribeiro.it at gmail * URL : http://sf.net/projects/gnomediaicons * License : GPL Programming Lang: other Description : network icons scheme for Dia gnomeDIAicons is a package with a network icons scheme based on Gnome Gorilla's theme. . The purpose of this project is generate beauty icons to Dia program and provide a raise in its utilization against MS Visio. . I hope it can be useful for many people. I'll provide others schemes too, but at first only network scheme was made. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#684998: disable touchpad while typing causes g-s-d to crash
Hi everyone, we suspect that this problem is only triggered for certain types of hardware. Could you all please attach your /var/log/Xorg.0.log and also your touchpad settings (which are causing problems) via gsettings list-recursively org.gnome.settings-daemon.peripherals.touchpad A backtrace of the crashing gnome-settings-daemon would be helpful, too. Michael -- Why is it that all of the instruments seeking intelligent life in the universe are pointed away from Earth? signature.asc Description: OpenPGP digital signature
Bug#483107: RFH: hotkey-setup -- auto-configures laptop hotkeys
I guess it is time to remove this package from the archive. I am not able to maintain it, and I suspect it is completely obsolete. Any objections? -- Happy hacking Petter Reinholdtsen -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#492325: Alternative package available: SimpleID
I've packaged SimpleID It is comparable to phpmyid (in other words, it installs easily with apache and php, no other major dependencies like databases, but you can use a database or LDAP if you want) Testing and feedback wiuld be very welcome as this package is new to Debian http://packages.debian.org/simpleid
Bug#621797: moc: Mono mixing switch does not work
Dnia 15.01.2013 08:26 użytkownik Elimar Riesebieter napisał : * Mikołaj Menke m...@menek.one.pl [2013-01-14 22:54 +0100]: Dnia 14.01.2013 08:29 użytkownik Elimar Riesebieter napisał : Could you please update to the latest version and test whether this bug is still valid for you? The problem still occurs on below version: miki@eee(22:51:57)~$mocp -V This is : Music On Console Version : 2.5.0-beta1 [...] Could you please provide your $HOME/.asoundrc ? I don't have $HOME/.asoundrc on the problematic system. -- http://mikolaj.menke.pl miko...@menke.pl Gadu-gadu: 2128279 Mobile: +48607345846 -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#635840: carl9170 firmware missing from debian
On Mon, Jan 14, 2013 at 11:41:48AM +, Ben Hutchings wrote: On Tue, 2012-09-04 at 10:07 +0300, Riku Voipio wrote: I don't believe it's absolutely necessary to build from sources during the package build, and indeed none of the other free firmware images are rebuilt. The problem has been that I couldn't quite reproduce the binary and the person submitting the firmware for linux-firmware.git didn't respond to my request for information. Ok, I didn't know the issue was that we wanted to be able to reproduce the binary. Had I known, I could have tried to get the firmware reproduced myself and created building documentation, saving some of your time. and I can now build a bit-identical firmware image, so I'm going to add it. I see it is now part of linux-firmware-free - awesome! Lots of Thanks, Riku -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#696796: -q not explained
Please report such things upstream. Did so: https://github.com/BaseXdb/basex/issues/620 -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#698048: gnucash: Gnucash broken by upgrade of libglib2.0-0
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 2013-01-15 03:33, Sébastien Villemot wrote: Le dimanche 13 janvier 2013 à 20:54 +0700, Ken Heard a écrit : Package: gnucash Version: 1:2.4.10-2~bpo60+1 You are reporting a bug against the version of gnucash coming from squeeze-backports. Such bug reports should not be directed to the Debian Bug Tracking System (BTS), as explained on this page: http://backports-master.debian.org/Instructions/ Normally I would have closed this bug report for that reason. Since the problem you describe seems to also affect the version of gnucash in stable, I leave it open for now. Indeed it does. I first noted this critical bug when I was using the version of gnucash in Squeeze stable. It was only after I discovered it there that I decided to try the version of gnucash in squeeze-backports and discovered that that version is broken for me as well. After I upgraded from Lenny to Squeeze on 2012-11-30 the Squeeze main repository kept the version of gnucash which I had previously installed from lenny-backports, 2.2.9-10. You must be mislead here. Gnucash is not in lenny-backports AFAIK. Version 2.2.9-10 is the version in squeeze (stable). My statement is correct. The gnucash version in lenny-backports, which I have been using since it first appeared there, is the same one which is in Squeeze stable. When one month ago I upgraded from Lenny to Squeeze, gnucash was not upgraded. That gnucash version calls for libglib2.0-0 version 2.24.0 or higher, which I assume was the version originally in the Squeeze main repository, and probably in lenny-backports as well. In any event I was able to use that version of gnucash until 2013-01-01. Later that same day I installed a number of new packages, and also some security fixes. The following day I was unable to open gnucash. Instead I received the following error message when I tried to open it in a terminal emulator: Gnu.bin – Message: main: binreloc relocation support was disabled at configure time. Segmentation fault. I then checked the packages installed or upgraded on 2013-01-01; there was only one which gnucash uses -- libglib2.0-0 version 2.24.2-1 This version is now the one in the Squeeze main repository. I consequently can only assume that gnucash will not load with this version of that package, although the gnucash dependency list says the it will work with versions 2.24.0 and higher. I also tried to use the version of gnucash from squeeze-backports, 2.4.10-2, but it does not work either and returns the same segmentation fault message. I tried to replicate your problem: more precisely I installed the most recent gnucash backport from squeeze-backports on a up-to-date squeeze system, and everything works fine. I really doubt that your problem comes from libglib2.0-0. Something else must be broken on your system. As I already stated I found this bug when I was still using the Squeeze stable version. You say you were able to open the squeeze-backports version, but did you try to open the Squeeze stable version? If we can find out why the Squeeze stable version is broken, it will perhaps help us to find out why I cannot open the squeeze-backports version; whereas you can. I have in addition since 2013-01-01 found problems with other packages which use libglib2.0-0. Package hardinfo now returns a segmentation fault. Iceweasel now 17.0 crashes when I attempt to download a file from it. Where did you get Iceweasel 17.0 from? It is not in squeeze nor in squeeze-backports. That is odd, because running apt-cache search -t squeeze-backports iceweasel shows that it is there; so that is where I must have found it. Maybe your system is broken because you mixed packages coming different (incompatible) sources. Can you send the contents of /etc/apt/sources.list # Experimental # deb http://ftp.debian.org/debian-experimental main # Trinity desktop environment deb http://ppa.quickbuild.pearsoncomputing.net/trinity/trinity-v3.5.13/debian squeeze main deb-src http://ppa.quickbuild.pearsoncomputing.net/trinity/trinity-v3.5.13/debian squeeze main deb http://ppa.quickbuild.pearsoncomputing.net/trinity/trinity-builddeps-v3.5.13/debian squeeze main deb-src http://ppa.quickbuild.pearsoncomputing.net/trinity/trinity-builddeps-v3.5.13/debian squeeze main # Stable backports deb http://backports.debian.org/debian-backports squeeze-backports main contrib non-free # Mozilla Debian # deb http://mozilla.debian.net/ squeeze-backports icedove-esr # deb http://mozilla.debian.net/ squeeze-backports iceweasel-release # Unstable backports # deb http://backports.debian.org/debian-backports squeeze-backports-sloppy main contrib non-free # Homegrown packages if any deb file:/opt packages/ # Main repository: deb http://debian.yorku.ca/debian/ squeeze main contrib non-free deb-src http://debian.yorku.ca/debian/ squeeze main contrib non-free # Secondary repository: deb
Bug#698213: cups: unowned files after purge (policy 6.8, 10.8): /etc/cups/raw.{convs, types}
Package: cups Version: 1.6.1-1 Severity: important User: debian...@lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed your package left unowned files on the system after purge, which is a violation of policy 6.8 (or 10.8): http://www.debian.org/doc/debian-policy/ch-maintainerscripts.html#s-removedetails Filing this as important as having a piuparts clean archive is a release goal since lenny. From the attached log (scroll to the bottom...): 0m43.2s ERROR: FAIL: Package purging left files on system: /etc/cups/raw.convsnot owned /etc/cups/raw.typesnot owned cheers, Andreas cups_1.6.1-1.log.gz Description: GNU Zip compressed data
Bug#694542: unblock: opendnssec/1.3.9-3
Hi Adam, On Sat, Dec 29, 2012 at 12:47 AM, Adam D. Barratt a...@adam-barratt.org.uk wrote: Hi, Apologies for the delay in getting back to you about this. same here. On Wed, 2012-11-28 at 08:33 +0100, Ondřej Surý wrote: On Tue, Nov 27, 2012 at 9:37 PM, Adam D. Barratt a...@adam-barratt.org.uk wrote: On Tue, 2012-11-27 at 14:55 +0100, Ondřej Surý wrote: + OPENDNSSEC-338: ods-ksmutil zone delete --all does not work [...] +If you have created your database in version 1.3.9, you should run +following statement in your OpenDNSSEC MySQL database: + +alter table dnsseckeys drop foreign key dnsseckeys_ibfk_1; Apologies for a possibly stupid question, but is there any way that could be automated rather than users having to make manual changes? Not stupid question at all. I thought about automating the process myself, but then I realized that I have no way of knowing if the database was created with version 1.3.9. Would something along the lines of if key exists alter table be feasible? Presumably if the key exists then the likelihood is that the package created it. Well, I tried and I have ended with a scary patch which I am attaching for a reference. I don't think it's good idea to go this way at this moment. E.g. this is triggered (and the alter table should be run) only in rare circumstances when the user has installed opendnssec 1.3.9-X from wheezy for a first time. People upgrading from squeeze or people upgrading from older releases should not be affected by this bug. This also means that all opendnssec users upgrading from squeeze will potentially be presented with the prompt, which isn't an ideal upgrade experience. True. I have decided to remove the NEWS file, since the conditions of triggering this bug are rare (deleting all keys), and number people using MySQL with OpenDNSSEC is low. I just put the text to README.Debian, where it could happily live. I will be uploading new version with those changes today. O. -- Ondřej Surý ond...@sury.org dropFK.patch Description: Binary data
Bug#674597: goplay: Segfault if selection is moved out of bound
[Sebastian Reichel 2012-05-25] goplay segfauls, if you select the first entry and then change to the previous (non existing) entry by using the arrow keys. backtrace is not that helpful, because goplay has no debugging symbols available. I tried to reproduce this, but suspect I did not really understand the description. Can you go in more detail on how to replicate the crash? -- Happy hacking Petter Reinholdtsen -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#698214: ruby-diff-lcs: diff-lcs isn't listed by gem list
Package: ruby-diff-lcs Version: 1.1.3-1 Severity: normal Dear Maintainer, When running gem list, diff-lcs isn't listed, which causes a Gem::LoadError when running stuff which requires 'diff/lcs'. Example: $ rake spec /usr/bin/ruby1.9.1 -S rspec spec/classes/collectd_package_spec.rb /usr/lib/ruby/1.9.1/rubygems/dependency.rb:247:in `to_specs': Could not find diff-lcs (~ 1.1.3) amongst [...long list of gems...] (Gem::LoadError) Manually creating /usr/share/rubygems-integration/1.9.1/specifications/diff-lcs-1.1.3.gemspec and /usr/share/rubygems-integration/1.8/specifications/diff-lcs-1.1.3.gemspec solves the problem. $ apt-cache policy ruby-diff-lcs ruby-diff-lcs: Installed: 1.1.3-1 Candidate: 1.1.3-1 Version table: *** 1.1.3-1 0 500 http://http.debian.net/debian/ testing/main amd64 Packages 500 http://http.debian.net/debian/ unstable/main amd64 Packages 100 /var/lib/dpkg/status $ dpkg -L ruby-diff-lcs | grep -c rubygems-integration 0 Curiously, when I apt-get source the package and rebuild it, the resulting package *does* contain the 2 gemspec files. So the problem seems to have been fixed at some point. Maybe the package just needs to be rebuilt and updated on the mirrors ? FWIW, I seem to have much more ruby-* packages installed on my system than the total count of gemfiles installed: $ dpkg -l | grep ruby- | grep ^ii | wc -l 187 $ ls /usr/share/rubygems-integration/1.8/specifications/ | wc -l 96 Thanks ! -- System Information: Debian Release: 7.0 APT prefers stable APT policy: (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 3.2.0-4-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 Versions of packages ruby-diff-lcs depends on: ii ruby1.8 [ruby-interpreter]1.8.7.358-6 ii ruby1.9.1 [ruby-interpreter] 1.9.3.194-5 ruby-diff-lcs recommends no packages. ruby-diff-lcs 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#697127: bits/c++config.h' file not found
reopen 697127 notfixed 697127 clang/3.2-1~exp4 found 697127 3.2-1~exp4 thanks Same issue, wrong path is used 386 vs 486: $ clang++ -o plop bla.cxx In file included from bla.cxx:1: /usr/bin/../lib/gcc/i486-linux-gnu/4.7/../../../../include/c++/4.7/iostream:38:10: fatal error: 'bits/c++config.h' file not found #include bits/c++config.h ^ 1 error generated. While: $ dpkg -L libstdc++6-4.7-dev | grep c++con /usr/include/i386-linux-gnu/c++/4.7/bits/c++config.h With: $ apt-cache policy clang libstdc++6-4.7-dev clang: Installed: 3.2-1~exp4 Candidate: 3.2-1~exp4 Version table: *** 3.2-1~exp4 0 1 http://ftp.fr.debian.org/debian/ experimental/main i386 Packages 100 /var/lib/dpkg/status 3.1-8 0 500 http://ftp.fr.debian.org/debian/ sid/main i386 Packages libstdc++6-4.7-dev: Installed: 4.7.2-18 Candidate: 4.7.2-18 Version table: *** 4.7.2-18 0 1 http://ftp.fr.debian.org/debian/ experimental/main i386 Packages 100 /var/lib/dpkg/status 4.7.2-5 0 500 http://ftp.fr.debian.org/debian/ sid/main i386 Packages Thanks -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#697127: bits/c++config.h' file not found
On 15/01/2013 11:20, Mathieu Malaterre wrote: reopen 697127 notfixed 697127 clang/3.2-1~exp4 found 697127 3.2-1~exp4 thanks Same issue, wrong path is used 386 vs 486: $ clang++ -o plop bla.cxx In file included from bla.cxx:1: /usr/bin/../lib/gcc/i486-linux-gnu/4.7/../../../../include/c++/4.7/iostream:38:10: fatal error: 'bits/c++config.h' file not found #include bits/c++config.h ^ 1 error generated. Next time, -v provides interesting information ;) Could you try with libstdc++-4.8-dev installed ? Sylvestre -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#697127: Processed: bits/c++config.h' file not found
FYI. Here is the list of nonexistent dirs: $ clang++ -v -o plop bla.cxx [...] clang -cc1 version 3.2 based upon LLVM 3.2svn default target i386-pc-linux-gnu ignoring nonexistent directory /usr/bin/../lib/gcc/i486-linux-gnu/4.7/../../../../include/c++/4.7/i486-linux-gnu ignoring nonexistent directory /usr/bin/../lib/gcc/i486-linux-gnu/4.7/../../../../include//c++/4.7/i486-linux-gnu ignoring nonexistent directory /usr/bin/../lib/gcc/i486-linux-gnu/4.7/../../../../include/c++/i486-linux-gnu ignoring nonexistent directory /usr/bin/../lib/gcc/i486-linux-gnu/4.7/../../../../include/c++/backward ignoring nonexistent directory /usr/bin/../lib/clang/3.2/include ignoring nonexistent directory /usr/include/i486-linux-gnu ignoring duplicate directory /usr/bin/../lib/gcc/i486-linux-gnu/4.7/../../../../include/c++/4.7 ignoring duplicate directory /usr/bin/../lib/gcc/i486-linux-gnu/4.7/../../../../include/c++/4.7/backward HTH -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#697127: bits/c++config.h' file not found
On Tue, Jan 15, 2013 at 11:30 AM, Sylvestre Ledru sylves...@debian.org wrote: On 15/01/2013 11:20, Mathieu Malaterre wrote: reopen 697127 notfixed 697127 clang/3.2-1~exp4 found 697127 3.2-1~exp4 thanks Same issue, wrong path is used 386 vs 486: $ clang++ -o plop bla.cxx In file included from bla.cxx:1: /usr/bin/../lib/gcc/i486-linux-gnu/4.7/../../../../include/c++/4.7/iostream:38:10: fatal error: 'bits/c++config.h' file not found #include bits/c++config.h ^ 1 error generated. Next time, -v provides interesting information ;) 697127#75 Could you try with libstdc++-4.8-dev installed ? $ apt-cache policy libstdc++-4.8-dev libstdc++-4.8-dev: Installed: 4.8-20130105-1 Candidate: 4.8-20130105-1 Version table: *** 4.8-20130105-1 0 1 http://ftp.fr.debian.org/debian/ experimental/main i386 Packages 100 /var/lib/dpkg/status leads to: $ clang++ -v -o plop bla.cxx Debian clang version 3.2-1~exp4 (tags/RELEASE_32/final) (based on LLVM 3.2) Target: i386-pc-linux-gnu Thread model: posix /usr/bin/clang -cc1 -triple i386-pc-linux-gnu -emit-obj -mrelax-all -disable-free -disable-llvm-verifier -main-file-name bla.cxx -mrelocation-model static -mdisable-fp-elim -fmath-errno -masm-verbose -mconstructor-aliases -fuse-init-array -target-cpu pentium4 -target-linker-version 2.22 -momit-leaf-frame-pointer -v -resource-dir /usr/bin/../lib/clang/3.2 -fmodule-cache-path /var/tmp/clang-module-cache -internal-isystem /usr/bin/../lib/gcc/i486-linux-gnu/4.8/../../../../include/c++/4.8 -internal-isystem /usr/bin/../lib/gcc/i486-linux-gnu/4.8/../../../../include/c++/4.8/i486-linux-gnu -internal-isystem /usr/bin/../lib/gcc/i486-linux-gnu/4.8/../../../../include/c++/4.8/backward -internal-isystem /usr/bin/../lib/gcc/i486-linux-gnu/4.8/../../../../include//c++/4.8 -internal-isystem /usr/bin/../lib/gcc/i486-linux-gnu/4.8/../../../../include//c++/4.8/i486-linux-gnu -internal-isystem /usr/bin/../lib/gcc/i486-linux-gnu/4.8/../../../../include//c++/4.8/backward -internal-isystem /usr/bin/../lib/gcc/i486-linux-gnu/4.8/../../../../include/c++ -internal-isystem /usr/bin/../lib/gcc/i486-linux-gnu/4.8/../../../../include/c++/i486-linux-gnu -internal-isystem /usr/bin/../lib/gcc/i486-linux-gnu/4.8/../../../../include/c++/backward -internal-isystem /usr/local/include -internal-isystem /usr/bin/../lib/clang/3.2/include -internal-isystem /usr/include/clang/3.2/include/ -internal-externc-isystem /usr/include/i386-linux-gnu -internal-externc-isystem /usr/include/i486-linux-gnu -internal-externc-isystem /usr/include -fdeprecated-macro -fdebug-compilation-dir /tmp -ferror-limit 19 -fmessage-length 157 -mstackrealign -fobjc-runtime=gcc -fcxx-exceptions -fexceptions -fdiagnostics-show-option -fcolor-diagnostics -o /tmp/bla-dpJMh9.o -x c++ bla.cxx clang -cc1 version 3.2 based upon LLVM 3.2svn default target i386-pc-linux-gnu ignoring nonexistent directory /usr/bin/../lib/gcc/i486-linux-gnu/4.8/../../../../include/c++/4.8/i486-linux-gnu ignoring nonexistent directory /usr/bin/../lib/gcc/i486-linux-gnu/4.8/../../../../include//c++/4.8/i486-linux-gnu ignoring nonexistent directory /usr/bin/../lib/gcc/i486-linux-gnu/4.8/../../../../include/c++/i486-linux-gnu ignoring nonexistent directory /usr/bin/../lib/gcc/i486-linux-gnu/4.8/../../../../include/c++/backward ignoring nonexistent directory /usr/bin/../lib/clang/3.2/include ignoring nonexistent directory /usr/include/i486-linux-gnu ignoring duplicate directory /usr/bin/../lib/gcc/i486-linux-gnu/4.8/../../../../include/c++/4.8 ignoring duplicate directory /usr/bin/../lib/gcc/i486-linux-gnu/4.8/../../../../include/c++/4.8/backward #include ... search starts here: #include ... search starts here: /usr/bin/../lib/gcc/i486-linux-gnu/4.8/../../../../include/c++/4.8 /usr/bin/../lib/gcc/i486-linux-gnu/4.8/../../../../include/c++/4.8/backward /usr/bin/../lib/gcc/i486-linux-gnu/4.8/../../../../include/c++ /usr/local/include /usr/include/clang/3.2/include /usr/include/i386-linux-gnu /usr/include End of search list. In file included from bla.cxx:1: /usr/bin/../lib/gcc/i486-linux-gnu/4.8/../../../../include/c++/4.8/iostream:38:10: fatal error: 'bits/c++config.h' file not found #include bits/c++config.h ^ 1 error generated. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#695015: Warning: 'with' will become a reserved keyword in Python 2.6
Hi, Maybe a dependencies to python 2.6 is missing ? Actually, Weboob does not support python 2.5. This is why the packet depends on python (= 2.6.6-7~), it should not be possible to use Weboob with python 2.5 (I'm not a packaging specialist, but I did not see everything wrong on http://packages.debian.org/wheezy/weboob) Not sure if this is related but I am getting: $ qflatboob TypeError: object of type 'QListWidget' has no len() It will be helpful to know your version of PyQt. Maybe we are missing a dependencies to forbid old versions. Regards, -- Florent Fourcot. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#695015: Warning: 'with' will become a reserved keyword in Python 2.6
Hi, On Tue, Jan 15, 2013 at 11:37 AM, Florent Fourcot web...@flo.fourcot.fr wrote: Maybe a dependencies to python 2.6 is missing ? Actually, Weboob does not support python 2.5. This is why the packet depends on python (= 2.6.6-7~), it should not be possible to use Weboob with python 2.5 (I'm not a packaging specialist, but I did not see everything wrong on http://packages.debian.org/wheezy/weboob) Technically the B-D line does not say so: apt-get source weboob cd weboob-0.c cat debian/control [...] Build-Depends: python-setuptools (= 0.6b3), debhelper (= 9~), pyqt4-dev-tools, python-all (= 2.6.6-3~) On debian/squeeze, python-all imply python 2.5 + python 2.6. I am not a python debian package expert, but I am guessing your python-all B-D is too weak... Not sure if this is related but I am getting: $ qflatboob TypeError: object of type 'QListWidget' has no len() It will be helpful to know your version of PyQt. Maybe we are missing a dependencies to forbid old versions. $ apt-cache policy python-qt4-phonon python-qt4-phonon: Installed: 4.7.3-1+b1 Candidate: 4.7.3-1+b1 Version table: 4.9.6-1 0 -1 http://ftp.fr.debian.org/debian/ experimental/main amd64 Packages 4.9.3-4 0 200 http://ftp.fr.debian.org/debian/ testing/main amd64 Packages 100 http://ftp.fr.debian.org/debian/ unstable/main amd64 Packages *** 4.7.3-1+b1 0 500 http://ftp.fr.debian.org/debian/ squeeze/main amd64 Packages 100 /var/lib/dpkg/status This is a rather minor bug, it only make backporting harder when you have weak dependencies. So this should not be considered as blocking, but a nice to have. Thanks ! -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#695500: (no subject)
Sorry, it still does not boot with the latest image, even after removing font.pf2. It freezes after 'error: prefix is not set'. It freezes on both a physical machine and a virtual machine. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#698164: mandate unique package names in Debian Java policy
On 14/01/2013 21:25, Tomasz Muras wrote: On 01/14/2013 09:16 PM, Eric Lavarde wrote: Hello, On 14/01/13 19:48, Daniel Pocock wrote: A few projects exist without following this convention, and sooner or later somebody may try to package one of them. According to the Java Language Specification, using a domain name is a suggested convention and not a mandatory obligation. Nonetheless, in an environment such as Debian where we have to keep many different packages concurrently on a single system, I would contend that we should mandate the use of this suggestion http://docs.oracle.com/javase/specs/jls/se7/html/jls-6.html#d5e6504 The package domain is a decision of upstream, not of the packager, hence I don't think that such recommendation has its place in the Java policy: 1. it doesn't create any collision in terms of packaging 2. it might create collision in terms of using two such libraries BUT a. developers using two such libraries have to cope with this issue also outside of Debian anyway b. and in terms of portability, any developer using one of both libraries would thank us (irony!) if we'd change the package name as it would force them to change their import statements only for Debian This said, we can put a suggestion in the Java Policy to influence upstream to fix their package naming convention, but: A. it's the same as for any other upstream bug, so why document the obvious? B. I doubt that such a badly named package would be of enough interest / quality for Debian packaging (but I might be wrong, I don't know any example) Conclusion: I vote against + close the bug. I don't think this is a problem at the moment - we do not have any collisions, do we? I second Eric - it should not be enforced + close the bug. I share Eric's point of view. It is already hard enough to package and maintain Java libraries... Sylvestre -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#698215: linux-image-3.2.0-4-amd64: Grub fails loading with cannot read the linux header
Package: src:linux Version: 3.2.35-2 Severity: important Hi everybody, I'm rather clueless on this error. Grub refuses to boot the current Wheezy kernel on this box. The message is cannot read the linux header. 3.2.0-3-amd64 boots without problems. I reinstalled the kernel package as well as grub-pc and ran update-grub without problems. debsums -sa does not report any modified files for the kernel package or any grub package installed. So I'm a bit clueless. The box is an rather old Intel Core2 6300 box. Could that be the problem? Could this kernel be incompatible with the processor? Cheers, Christopher -- Package-specific info: ** Kernel log: boot messages should be attached ** Model information sys_vendor: product_name: product_version: chassis_vendor: chassis_version: bios_vendor: Intel Corp. bios_version: MQ96510J.86A.1458.2006.1017.1151 board_vendor: Intel Corporation board_name: DG965MQ board_version: AAD37419-302 ** PCI devices: 00:00.0 Host bridge [0600]: Intel Corporation 82P965/G965 Memory Controller Hub [8086:29a0] (rev 02) Subsystem: Intel Corporation Device [8086:514d] Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast TAbort- TAbort- MAbort+ SERR- PERR- INTx- Latency: 0 Capabilities: access denied Kernel driver in use: agpgart-intel 00:01.0 PCI bridge [0604]: Intel Corporation 82P965/G965 PCI Express Root Port [8086:29a1] (rev 02) (prog-if 00 [Normal decode]) Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+ Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast TAbort- TAbort- MAbort- SERR- PERR- INTx- Latency: 0, Cache Line Size: 64 bytes Bus: primary=00, secondary=01, subordinate=01, sec-latency=0 Memory behind bridge: e050-e05f Secondary status: 66MHz- FastB2B- ParErr- DEVSEL=fast TAbort- TAbort- MAbort- SERR- PERR- BridgeCtl: Parity- SERR- NoISA+ VGA- MAbort- Reset- FastB2B- PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn- Capabilities: access denied Kernel driver in use: pcieport 00:02.0 VGA compatible controller [0300]: Intel Corporation 82G965 Integrated Graphics Controller [8086:29a2] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Intel Corporation Device [8086:514d] Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+ Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast TAbort- TAbort- MAbort- SERR- PERR- INTx- Latency: 0 Interrupt: pin A routed to IRQ 48 Region 0: Memory at e030 (32-bit, non-prefetchable) [size=1M] Region 2: Memory at d000 (64-bit, prefetchable) [size=256M] Region 4: I/O ports at 2110 [size=8] Expansion ROM at unassigned [disabled] Capabilities: access denied Kernel driver in use: i915 00:02.1 Display controller [0380]: Intel Corporation 82G965 Integrated Graphics Controller [8086:29a3] (rev 02) Subsystem: Intel Corporation Device [8086:514d] Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast TAbort- TAbort- MAbort- SERR- PERR- INTx- Latency: 0 Region 0: Memory at e020 (32-bit, non-prefetchable) [size=1M] Capabilities: access denied 00:03.0 Communication controller [0780]: Intel Corporation 82P965/G965 HECI Controller [8086:29a4] (rev 02) Subsystem: Intel Corporation Device [8086:514d] Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast TAbort- TAbort- MAbort- SERR- PERR- INTx- Latency: 0 Interrupt: pin A routed to IRQ 11 Region 0: Memory at e0426100 (64-bit, non-prefetchable) [size=16] Capabilities: access denied 00:19.0 Ethernet controller [0200]: Intel Corporation 82566DC Gigabit Network Connection [8086:104b] (rev 02) Subsystem: Intel Corporation Device [8086:0001] Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+ Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast TAbort- TAbort- MAbort- SERR- PERR- INTx- Latency: 0 Interrupt: pin A routed to IRQ 46 Region 0: Memory at e040 (32-bit, non-prefetchable) [size=128K] Region 1: Memory at e0424000 (32-bit, non-prefetchable) [size=4K] Region 2: I/O ports at 20e0 [size=32] Capabilities: access denied Kernel driver in use: e1000e 00:1a.0 USB controller [0c03]: Intel Corporation 82801H (ICH8 Family) USB UHCI Controller #4 [8086:2834] (rev
Bug#698216: broadcom-sta-dkms: triggers kernel BUG on linux 3.6.1+
Package: broadcom-sta-dkms Version: 5.100.82.112-8 Severity: normal when inserting the wl module as built using dkms by broadcom-sta-dkms in a 3.7 kernel (allegedly exactly since 3.6.1), it a kernel BUG message appears on the screen, the wifi still doesn't work, and all kinds of things go bad as usual after kernel bug messages. see the attached dmesg output for the exact message. the problem is known and well described in redhat[1], which links to a discussion at rpmfusion[2] that contains a patch[3]. i applied that patch on the dkms sources, and the resulting built kernel module works fine for me. [1] https://bugzilla.redhat.com/show_bug.cgi?id=865695 [2] https://bugzilla.rpmfusion.org/show_bug.cgi?id=2526 [3] https://bugzilla.rpmfusion.org/attachment.cgi?id=976action=edit -- System Information: Debian Release: 7.0 APT prefers testing APT policy: (500, 'testing'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 3.7-trunk-amd64 (SMP w/2 CPU cores) Locale: LANG=de_AT.UTF8, LC_CTYPE=de_AT.UTF8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages broadcom-sta-dkms depends on: ii dkms 2.2.0.3-1.2 Versions of packages broadcom-sta-dkms recommends: ii wireless-tools 30~pre9-8 broadcom-sta-dkms suggests no packages. -- no debconf information 57.612272] device fsid 1d944e85-3ce6-49e4-b8e4-0a476f5c725d devid 1 transid 42648 /dev/mapper/_dev_dm_1 [ 57.614924] btrfs: disk space caching is enabled [ 140.195116] INFO @wl_cfg80211_attach : Registered CFG80211 phy [ 140.346989] lib80211_crypt: registered algorithm 'TKIP' [ 140.347482] wlan0: Broadcom BCM4727 802.11 Hybrid Wireless Controller 5.100.82.112 [ 140.424835] [ cut here ] [ 140.424909] kernel BUG at /usr/src/linux-headers-3.7-trunk-common/include/net/cfg80211.h:2493! [ 140.424999] invalid opcode: [#1] SMP [ 140.425050] Modules linked in: lib80211_crypt_tkip wl(PO) parport_pc ppdev lp parport nls_utf8 nls_cp437 vfat fat ext4 jbd2 mbcache loop sha256_generic cbc snd_hda_codec_realtek snd_hda_codec_hdmi joydev snd_hda_intel btusb uvcvideo snd_hda_codec videobuf2_vmalloc snd_hwdep kvm_amd snd_pcm_oss snd_mixer_oss snd_pcm kvm bluetooth thinkpad_acpi videobuf2_memops crc16 videobuf2_core radeon ttm drm_kms_helper videodev media drm snd_page_alloc i2c_algo_bit pcspkr rts_pstor(C) k10temp snd_timer nvram i2c_piix4 psmouse lib80211 i2c_core evdev serio_raw cfg80211 snd soundcore rfkill wmi microcode battery ac processor video button btrfs crc32c libcrc32c zlib_deflate xts gf128mul dm_crypt dm_mod md_mod sg sd_mod crc_t10dif thermal ohci_hcd thermal_sys xhci_hcd ahci libahci ehci_hcd libata scsi_mod r8169 usbcore usb_common mii [ 140.426039] CPU 0 [ 140.426067] Pid: 3912, comm: wpa_supplicant Tainted: P C O 3.7-trunk-amd64 #1 Debian 3.7.1-1~experimental.2 LENOVO 335963G/335963G [ 140.426193] RIP: 0010:[a06c75b7] [a06c75b7] wdev_priv+0x5/0xf [wl] [ 140.426303] RSP: 0018:8800b2e7f9d0 EFLAGS: 00010246 [ 140.426359] RAX: 0001 RBX: 8800b2e2e580 RCX: 00ff [ 140.426431] RDX: RSI: 8800ce7e1000 RDI: [ 140.426502] RBP: 8800b2e2e000 R08: 80d0 R09: 880036dc2800 [ 140.426574] R10: 0246 R11: 880106000980 R12: 8800b2e7fa98 [ 140.426646] R13: 8800ce7e1000 R14: R15: 880036dc2824 [ 140.426719] FS: 7f5c77235700() GS:880106c0() knlGS: [ 140.426801] CS: 0010 DS: ES: CR0: 80050033 [ 140.426859] CR2: 0218ee48 CR3: b2c4e000 CR4: 07f0 [ 140.426932] DR0: DR1: DR2: [ 140.427004] DR3: DR6: 0ff0 DR7: 0400 [ 140.427077] Process wpa_supplicant (pid: 3912, threadinfo 8800b2e7e000, task 8800b2e60780) [ 140.427165] Stack: [ 140.427189] a06c9d06 0001 0033 8800ce7e1000 [ 140.427277] 8800b2e2e000 8800b2e7fa98 0001 8800c3d2fc00 [ 140.427363] a028e3d3 880036dc281c 0033 0021 [ 140.427449] Call Trace: [ 140.427495] [a06c9d06] ? wl_cfg80211_scan+0x79/0x379 [wl] [ 140.427577] [a028e3d3] ? nl80211_trigger_scan+0x38d/0x45d [cfg80211] [ 140.427660] [812d6762] ? genl_rcv_msg+0x1b6/0x1ff [ 140.427722] [812d65ac] ? genl_rcv+0x28/0x28 [ 140.427779] [812d6281] ? netlink_rcv_skb+0x36/0x7c [ 140.427840] [812d65a3] ? genl_rcv+0x1f/0x28 [ 140.427896] [812d5da3] ? netlink_unicast+0xde/0x15e [ 140.427960] [812d60b0] ? netlink_sendmsg+0x28d/0x2b4 [ 140.428024] [812a5a74] ? sock_sendmsg+0x4f/0x6c [ 140.428084] [810c1a7d] ? find_get_page+0x42/0x61 [ 140.428145] [812a5c83] ? __sys_sendmsg+0x1f2/0x284 [ 140.428207] [810dd9f1] ?
Bug#697897: packaging committed.
Packaging committed to http://anonscm.debian.org/gitweb/?p=pkg-mozext/stylish.git -- Regards, Dmitry Smirnov GPG key : 4096R/53968D1B --- Good luck happens when preparedness meets opportunity. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#693756: follow-up: suspend working, wifi explanation
* suspend: suspend-to-ram never worked before on this system -- i forgot to mention that in the original report. a kernel upgrade to experimental's linux-image-3.7-trunk-amd64 3.7.1-1~experimental.2 version made suspend-to-ram just work. * wifi: i found out more about the original wifi problem as things broke after the 3.7 kernel update. the free kernel module brcmsmac works when loaded (this is what was used during installation), but has the signal strength issue described in the november 28th message. that problem persists up to kernel 3.7. the nonfree wl kernel module, which can be generated from broadcom-sta-dkms, was what made wifi work at full strength back then. however, that module crashes 3.7 until #698216 is fixed. the patch referenced there can easily be applied even now. to stay on the safe side, the free driver's bcma module probably needs blacklisting on this system as well (see #697496), but i've had enough reboots today to not test whether i really need that now. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#697040: [Pkg-utopia-maintainers] Bug#697040: network-manager: Connections bounce down-up when restarting NM during upgrade
On 31.12.2012 04:13, Phil Miller wrote: Package: network-manager Version: 0.9.4.0-7 Severity: normal During the upgrade of various packages, including NM from 0.9.4.0-6 to 0.9.4.0-7, I noticed that the package configuration actually takes down all of the NM-managed interfaces while NM restarts: Setting up network-manager (0.9.4.0-7) ... [ ok ] Reloading system message bus config...done. [ ok ] Stopping network connection manager: NetworkManager. # NM-managed network interfaces are down here [ ok ] Starting network connection manager: NetworkManager. What type of network connection do you have, wifi, ethernet, static IP, DHCP? FWIW, I cannot reproduce your problem. Shutting down NM will keep the network up here, for both wireless and wired connections. If I start NM again, it can pick up the state of the ethernet interface. For wireless interfaces, it will re-initialize the connection, so you can have a short downtime here. Can you also send me a debug log of NetworkManager [1]. When you run service network-manager stop, what is the output of nm-tool and route. Michael [1] https://live.gnome.org/NetworkManager/Debugging -- Why is it that all of the instruments seeking intelligent life in the universe are pointed away from Earth? signature.asc Description: OpenPGP digital signature
Bug#677286: virtuoso-opensource-6.1: unowned files after purge (policy 6.8, 10.8): /root/.odbc.ini
On 2013-01-12 22:06, José Manuel Santamaría Lema wrote: Ok, just tell me if it works for your or not, if it does I'll file the bug Works fine for new installations. /root/.odbc.ini is still being created during some upgrade paths, but I'm not sure how or whether this should be fixed at all. And this is definitively caused by the maintainer scripts in the old package versions. So please file an odbcinst bug and upload to unstable. Thanks. Andreas -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#695500: (no subject)
Hi, On 15/01/13 10:52, Michael Tsang wrote: Sorry, it still does not boot with the latest image, even after removing font.pf2. It freezes after 'error: prefix is not set'. It freezes on both a physical machine and a virtual machine. The change is only applied in Git, pending an upload. Until then the installer images are not fixed, sorry. I think the minimum for kfreebsd-amd64 is about 176 MiB until then. kfreebsd-i386 will work with less memory. Regards, -- Steven Chamberlain ste...@pyro.eu.org -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#459078: Any progress?
I can't see this bug in the list of bugs upstream, could you try contacting upstream again please? It' a silly bug that should be easy to fix. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#658896: sudo: setresuid(ROOT_UID, ROOT_UID, ROOT_UID): Operation not permitted
found 658896 1.8.5p2-1 severity 658896 serious thanks justification: Renders the package unusable on systems with LDAP/PAM Hi! I can confirm this bug. On a Wheezy system with nscd and libnss-ldap is impossible to use sudo. # apt-cache policy sudo sudo: Installed: 1.8.5p2-1 Candidate: 1.8.5p2-1 Version table: *** 1.8.5p2-1 0 500 http://debian/debian/ sid/main amd64 Packages 500 http://debian/debian/ testing/main amd64 Packages 100 /var/lib/dpkg/status 1.7.4p4-2.squeeze.3 0 500 http://debian/debian/ stable/main amd64 Packages $ sudo ls / [sudo] password for clopez: sudo: PERM_ROOT: setresuid(0, -1, -1): Operation not permitted sudo: unable to open /var/lib/sudo/clopez/1: Operation not permitted sudo: unable to set supplementary group IDs: Operation not permitted sudo: unable to execute /bin/ls: Operation not permitted Downgrading the package to squeeze version fixes the problem automatically # apt-get install sudo=1.7.4p4-2.squeeze.3 $ sudo ls / [sudo] password for clopez: bin boot dev etc home lib lib32 lib64 lost+found media mnt opt proc root run sbin selinux srv sys tmp usr var IMHO this bug should be fixed before releasing Wheezy. Sudo is not usable on systems configured with LDAP/PAM (which is a setup widely used). Therefore I'm raising the severity. Thanks! signature.asc Description: OpenPGP digital signature
Bug#698217: mssh: shift+insert only pastes to first window
Package: mssh Version: 1.2-1 Severity: normal Using shit+insert will only insert text into the first window. Pasting using middle mousebutton works though. -- System Information: Debian Release: 6.0.6 APT prefers stable APT policy: (500, 'stable') Architecture: i386 (i686) Kernel: Linux 2.6.32-5-xen-686 (SMP w/2 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages mssh depends on: ii gconf22.28.1-6 GNOME configuration database syste ii libc6 2.11.3-4 Embedded GNU C Library: Shared lib ii libgconf2-4 2.28.1-6 GNOME configuration database syste ii libglib2.0-0 2.24.2-1 The GLib library of C routines ii libgtk2.0-0 2.20.1-2 The GTK+ graphical user interface ii libvte9 1:0.24.3-4 Terminal emulator widget for GTK+ ii openssh-client1:5.5p1-6+squeeze2 secure shell (SSH) client, for sec mssh recommends no packages. mssh 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#698218: roundcube-core: maybe remove obsolete entries from /e/r/htaccess?
Package: roundcube Version: 0.7.2-5 Severity: minor Hi, I'm using roundcube v0.7.x on both Debian 6.0 and 7.0 systems. I see that these entries are still there although I've never found a technical reason to keep them on my setup: # http://bugs.php.net/bug.php?id=30766 #php_value mbstring.func_overload 0 # replace 'append' with 'merge' for Apache version 2.2.9 and later #Header append Cache-Control public env=!NO_CACHE Debian has Apache 2.2.22 in release 6.0, thus if this was really needed the last entry should have been configured by default. Are these obsolete recommendations that could be removed? Cheers -- System Information: Debian Release: 7.0 APT prefers testing APT policy: (500, 'testing'), (200, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 3.2.0-4-amd64 (SMP w/2 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 roundcube-core depends on: ii apache2 2.2.22-12 ii apache2-mpm-prefork [httpd] 2.2.22-12 ii dbconfig-common 1.8.47+nmu1 ii debconf [debconf-2.0]1.5.49 ii libjs-jquery 1.7.2+dfsg-1 ii libjs-jquery-ui 1.8.ooops.21+dfsg-2 ii libmagic15.11-2 ii php-auth 1.6.2-1 ii php-mail-mime1.8.4-1 ii php-mdb2 2.5.0b3-2 ii php-net-smtp 1.6.1-1 ii php-net-socket 1.0.9-2 ii php5 5.4.4-10 ii php5-gd 5.4.4-10 ii php5-intl5.4.4-10 ii php5-mcrypt 5.4.4-10 ii php5-pspell 5.4.4-10 ii roundcube-pgsql 0.7.2-5 ii tinymce 3.4.8+dfsg0-1 ii ucf 3.0025+nmu3 roundcube-core recommends no packages. Versions of packages roundcube-core suggests: ii php-auth-sasl 1.0.4-1 pn php-crypt-gpg none ii roundcube-plugins 0.7.2-5 roundcube depends on no packages. -- debconf information: roundcube/upgrade-error: abort roundcube/pgsql/authmethod-user: password roundcube/purge: false * roundcube/dbconfig-install: true * roundcube/language: en_US roundcube/db/dbname: roundcube roundcube/remote/newhost: roundcube/pgsql/changeconf: false roundcube/upgrade-backup: true roundcube/install-error: abort roundcube/mysql/admin-user: root * roundcube/hosts: localhost roundcube/pgsql/authmethod-admin: ident roundcube/dbconfig-remove: roundcube/pgsql/admin-user: postgres roundcube/internal/skip-preseed: true roundcube/db/app-user: roundcube roundcube/dbconfig-reinstall: false roundcube/mysql/method: unix socket roundcube/remove-error: abort * roundcube/restart-webserver: false roundcube/dbconfig-upgrade: true roundcube/remote/port: roundcube/pgsql/method: unix socket roundcube/pgsql/manualconf: roundcube/db/basepath: roundcube/pgsql/no-empty-passwords: roundcube/passwords-do-not-match: roundcube/internal/reconfiguring: false * roundcube/reconfigure-webserver: * roundcube/database-type: pgsql roundcube/remote/host: roundcube/missing-db-package-error: abort -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#659762: happens to me too
This happens to me too, in at least 50% of the cases (I have tried 4 times so far). Here's my setup: 2x300GB PV 600GB VG 500GB striped LV (2 stripes) lvm 2.02.95-4 linux-image-3.2.0-4-amd64 dmsetup 2:1.02.74-4 Here's what I do: lvcreate -i2 --size 100G --snapshot --name backup /dev/vg1/main # do some work lvremove /dev/vg1/backup and I get the exact error as described above, including frozen I/O on the original volume, /dev/vg1/main). If I do dmsetup resume /dev/mapper/vg1-main the I/O is unfrozen and everything seems to work fine. (Thanks Chris.) There's a lot of I/O activity on the original volume so perhaps that is causing the error. The physical volumes are quite slow. I don't have two snapshots, only one. This is on a replicated production system, but it's mostly reproducable, so perhaps I can try things out if you need me to. Regards, Oskar Liljeblad (os...@osk.mine.nu) -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#696424: Possible patch
Hi Salvatore
Hi David
On Thu, Jan 10, 2013 at 10:16:35AM +, David Weber wrote:
Hi David
On Mon, Jan 07, 2013 at 09:06:53AM +, David Weber wrote:
Attached is the debdiff contianing these three refreshed for the
version in unstable and testing. But I'm not yet ready to propose a
NMU. Testing of the resulting package is welcome!
Thanks for the debdiff!
It works as expected: It creates the files with the right
permissions without breaking functionality.
A problem could be that the files aren't freshly created by a simple
restart of the daemon. Should something be done about that?
Some options could be:
- Notify the user to stop libvirtd and sanlock and run
rm /var/run/sanlock/sanlock.sock; rm /var/log/sanlock.log
- Change the file permissions through the package update
- Do nothing because most likely nobody uses sanlock on Debain atm.
I have not a final answer here, but it might be easy to implement like
libvirt-bin does in postint, mabye only conditionally checking (so
doing it during package update from a 'broken' version):
[...]
if ! dpkg-statoverride --list /var/log/sanlock.log /dev/null 21;
then
# fix permissions
fi
[...]
and the same for /var/run/sanlock/sanlock.sock.
Great hint. I modified the patch in that way and also added the
fix for #689696
Btw, after thinking about further on it: As both /var/log/sanlock.log
and /var/run/sanlock/sanlock.sock are not files installed by the
package, I think the check with dpkg-statoverride is in this case
wrong! Sorry about the wrong suggestion.
So I think it's best to remove this again.
Ops, thats right. I now check the permissions and change
them in case they are wrong
Regarding the second: I suggest to include in this upload only fixes
compliant with the freeze policy:
[1]: http://release.debian.org/wheezy/freeze_policy.html
(but I have not looked if #689696 can be considered RC).
Since it is a build fix, I guess it classifys
+sanlock (2.2-1.1) unstable; urgency=low
+
+ * Fix CVE-2012-5638 sanlock world writable /var/log/sanlock.log. Thanks to
Salvatore Bonaccorso (Closes: #696424)
would wrap this line
+ Add patches cherry-picked from git repository:
+ - 0001-sanlock-remove-umask-0.patch
+ - 0001-sanlock-use-lockfile-mode-644.patch
+ - 0001-wdmd-use-lockfile-mode-644.patch
+ * Replace restrict field name (Closes: #689696)
+ Add patche cherry.picked from git repository:
^ s{patche}{patch} and s{cherry.picked}{cherry picked}
Ops, fixed
Again thanks for your work!
Thank you too!
Regards,
Salvatore
Cheers,
David
To: car...@debian.org
696...@bugs.debian.org
Cc: martin.quin...@loria.fr
j...@inutil.org
a...@sigxcpu.org
sanlock_cve2.debdiff
Description: Binary data
Bug#697602: Bug count confusion when unrelated binary and source has same name
On Mon, Jan 07, 2013 at 03:16:42PM +0100, Niels Thykier wrote: If a source package produces and identically named binary (e.g. src:eclipse produces a binary named eclipse), it usually doesn't matter which of them gets the blame. The problem is when a binary has the same name as a source that _doesn't_ built it. An example in the archive being: source:sm builds binary r-cran-sm, source:screen-message builds binary sm If a BugsV file contains sm 123456 Britney will assume that RC bug applies to _both_ the source package sm and the binary sm (and thus screen-message). I'd seriously argue that one of the source packages has to change its name. I don't think that the two namespaces (source and binary packages) should be considered that separated, so that might warrant an addition to policy? (Do not build a binary package that has the name of a totally unrelated source package?) Kind regards Philipp Kern -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#665683: Functionality removed in Inkscape 0.49
This bug should no longer be an issue after the release of Inkscape 0.49 as the tear-off menu functionality has been removed. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#698219: dget: error:14077458:SSL routines:SSL23_GET_SERVER_HELLO:reason(1112)
Package: devscripts Version: 2.12.4~bpo60+1 Severity: normal It would be nice it dget would allow passing something like --no-check-certificate (wget). Otherwise it fails on some https: $ dget --insecure -u http://www.physik.tu-cottbus.de/~george/debian/unstable/source/libemf_1.0-2.dsc; dget: retrieving http://www.physik.tu-cottbus.de/~george/debian/unstable/source/libemf_1.0-2.dsc % Total% Received % Xferd Average Speed TimeTime Time Current Dload Upload Total SpentLeft Speed 100 454 100 4540 0 7186 0 --:--:-- --:--:-- --:--:-- 14645 curl: (35) error:14077458:SSL routines:SSL23_GET_SERVER_HELLO:reason(1112) dget: curl libemf_1.0-2.dsc http://www.physik.tu-cottbus.de/~george/debian/unstable/source/libemf_1.0-2.dsc failed Thanks -- Package-specific info: --- /etc/devscripts.conf --- --- ~/.devscripts --- DEBCHANGE_RELEASE_HEURISTIC=changelog -- 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.4-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 devscripts depends on: ii dpkg-dev 1.16.1.2~bpo60+1 Debian package development tools ii libc6 2.11.3-4 Embedded GNU C Library: Shared lib ii perl 5.10.1-17squeeze3 Larry Wall's Practical Extraction ii python 2.6.6-3+squeeze7 interactive high-level object-orie ii python2.6 2.6.6-8+b1An interactive high-level object-o Versions of packages devscripts recommends: ii at 3.1.12-1+squeeze1 Delayed job execution and batch pr ii curl 7.21.0-2.1+squeeze2 Get a file from an HTTP, HTTPS or ii dctrl-tools 2.14.5 Command-line tools to process Debi ii debian-keyring 2010.12.29 GnuPG keys of Debian Developers ii dput 0.9.6.1+squeeze1Debian package upload tool ii dupload 2.6.6 utility to upload Debian packages ii equivs 2.0.8 Circumvent Debian package dependen ii fakeroot 1.14.4-1Gives a fake root environment ii gnupg1.4.10-4GNU privacy guard - a free PGP rep ii libcrypt-ssleay-perl 0.57-2 Support for https protocol in LWP pn libdistro-info-perl none (no description available) ii libjson-perl 2.21-1 Perl module to parse and convert t ii libparse-debcontrol- 2.005-2 Easy OO parsing of Debian control- ii libsoap-lite-perl0.712-2 Perl implementation of a SOAP clie ii liburi-perl 1.60-1~bpo60+1 module to manipulate and access UR ii libwww-perl 5.836-1 Perl HTTP/WWW client/server librar ii lintian 2.5.10.3~bpo60+1Debian package checker ii man-db 2.5.7-8 on-line manual pager ii patch2.6-2 Apply a diff file to an original ii patchutils 0.3.1-2 Utilities to work with patches ii python-debian0.1.18+squeeze1 Python modules to work with Debian pn python-magic none (no description available) ii sensible-utils 0.0.4 Utilities for sensible alternative ii strace 4.5.20-2A system call tracer ii unzip6.0-4 De-archiver for .zip files ii wdiff0.6.3-1 Compares two files word by word ii wget 1.12-2.1retrieves files from the web ii xz-utils 5.0.0-2 XZ-format compression utilities Versions of packages devscripts suggests: ii bsd-mailx [mailx] 8.1.2-0.20100314cvs-1 simple mail user agent ii build-essential11.5 Informational list of build-essent pn cvs-buildpackage none(no description available) pn devscripts-el none(no description available) ii gnuplot4.4.0-1.1 A command-line driven interactive pn libauthen-sasl-per none(no description available) pn libfile-desktopent none(no description available) pn libnet-smtp-ssl-pe none(no description available) pn libterm-size-perl none(no description available) ii libtimedate-perl 1.2000-1 collection of modules to manipulat ii libyaml-syck-perl 1.12-1Perl module providing a fast, ligh ii mutt 1.5.21-5~bpo60+1 text-based mailreader supporting M ii openssh-client [ss 1:5.5p1-6+squeeze2secure shell (SSH) client, for sec ii svn-buildpackage 0.8.5 helper programs to
Bug#698220: WARNING **: only first BezPoint can be a BEZ_MOVE_TO
Package: dia Version: 0.97.2-8 Severity: normal For some reason I cannot import the attached SVG into DIA. I'd like to use it as an icon though. Dia seems to report there is something wrong with my SVG: $ dia MRIScanner2.svg (dia-gnome:6410): GLib-WARNING **: A group named gtk is already part of this GOptionContext ** (dia-gnome:6410): WARNING **: only first BezPoint can be a BEZ_MOVE_TO ** (dia-gnome:6410): WARNING **: only first BezPoint can be a BEZ_MOVE_TO ** (dia-gnome:6410): WARNING **: only first BezPoint can be a BEZ_MOVE_TO However other SVG viewer do not report anything wrong with it. Thanks -- 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.4-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 dia depends on: ii dia-common 0.97.2-8 Diagram editor (common files) ii dia-libs 0.97.2-8 Diagram editor (library files) ii libart-2.0-2 2.3.21-1 Library of functions for 2D graphi ii libatk1.0-01.30.0-1 The ATK accessibility toolkit ii libc6 2.11.3-4 Embedded GNU C Library: Shared lib ii libcairo2 1.10.2-7~bpo60+1 The Cairo 2D vector graphics libra ii libfontconfig1 2.8.0-2.1 generic font configuration library ii libfreetype6 2.4.9-1~bpo60+1 FreeType 2 font engine, shared lib ii libglib2.0-0 2.24.2-1 The GLib library of C routines 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 libpng12-0 1.2.44-1+squeeze4 PNG library - runtime ii libxml22.7.8.dfsg-2+squeeze5 GNOME XML library ii zlib1g 1:1.2.3.4.dfsg-3 compression library - runtime Versions of packages dia recommends: ii gsfonts-x11 0.21 Make Ghostscript fonts available t dia suggests no packages. -- no debconf information attachment: MRIScanner2.svg
Bug#694542: unblock: opendnssec/1.3.9-3
retitle 694542 unblock: opendnssec/1.3.9-4 thank you Debdiff against -2 attached, diffstat: README.Debian| 16 ++ changelog| 17 +++ patches/011-return_if_open_parse_of_zonelist.xml_fails.patch | 26 +++ patches/012-fix_RRSIGs_with_glue.patch | 18 +++ patches/013-fix_zone_delete_with_MySQL.patch | 23 + patches/series |3 + 6 files changed, 102 insertions(+), 1 deletion(-) Ondrej On Tue, Jan 15, 2013 at 10:28 AM, Ondřej Surý ond...@debian.org wrote: Hi Adam, On Sat, Dec 29, 2012 at 12:47 AM, Adam D. Barratt a...@adam-barratt.org.uk wrote: Hi, Apologies for the delay in getting back to you about this. same here. On Wed, 2012-11-28 at 08:33 +0100, Ondřej Surý wrote: On Tue, Nov 27, 2012 at 9:37 PM, Adam D. Barratt a...@adam-barratt.org.uk wrote: On Tue, 2012-11-27 at 14:55 +0100, Ondřej Surý wrote: + OPENDNSSEC-338: ods-ksmutil zone delete --all does not work [...] +If you have created your database in version 1.3.9, you should run +following statement in your OpenDNSSEC MySQL database: + +alter table dnsseckeys drop foreign key dnsseckeys_ibfk_1; Apologies for a possibly stupid question, but is there any way that could be automated rather than users having to make manual changes? Not stupid question at all. I thought about automating the process myself, but then I realized that I have no way of knowing if the database was created with version 1.3.9. Would something along the lines of if key exists alter table be feasible? Presumably if the key exists then the likelihood is that the package created it. Well, I tried and I have ended with a scary patch which I am attaching for a reference. I don't think it's good idea to go this way at this moment. E.g. this is triggered (and the alter table should be run) only in rare circumstances when the user has installed opendnssec 1.3.9-X from wheezy for a first time. People upgrading from squeeze or people upgrading from older releases should not be affected by this bug. This also means that all opendnssec users upgrading from squeeze will potentially be presented with the prompt, which isn't an ideal upgrade experience. True. I have decided to remove the NEWS file, since the conditions of triggering this bug are rare (deleting all keys), and number people using MySQL with OpenDNSSEC is low. I just put the text to README.Debian, where it could happily live. I will be uploading new version with those changes today. O. -- Ondřej Surý ond...@sury.org -- Ondřej Surý ond...@sury.org opendnssec_1.3.9-4.debdiff Description: Binary data
Bug#621797: moc: Mono mixing switch does not work
* John Fitzgerald mocma...@daper.net [2013-01-15 23:16 +1300]: John, please reply always to the bug (621...@bugs.debian.org) as well. So we have managed to document the flow of information. On Tue, Jan 15, 2013 at 10:17:50AM +0100, Miko?aj Menke wrote: Dnia 15.01.2013 08:26 u?ytkownik Elimar Riesebieter napisa? : Could you please provide your $HOME/.asoundrc ? I don't have $HOME/.asoundrc on the problematic system. Also possibly in '/etc/asound.conf' (or where Debian moves it to as identified in '/usr/share/alsa/alsa.conf', or where Debian moves *that* to). If that would be the case then we would have the same bug at Franks Zacharias' installation as $USER doesn't has to customize those defaults. [...] (I'm just wondering if the Debian ALSA package maintainers One of them is probably me ;-) can help us out with this problem now that we've sort of homed in on what might be going on.) Well, als told before: Datas in /usr/share don't have to be customized by users. Elimar -- what IMHO then? IMHO - Inhalation of a Multi-leafed Herbal Opiate ;) --posting from alex in debian-user-- signature.asc Description: Digital signature
Bug#698203: Not a directory at /var/lib/dpkg/info/linux-base.postinst line 1177. (extlinux)
On Tue, 2013-01-15 at 17:20 +1100, Trent W. Buck wrote: Package: linux-base Version: 3.5 Severity: minor I did the following: - basic squeeze install, choose no bootloader, - manually do an extlinux install in /boot (extlinux package is NOT installed) - set link_in_boot=yes in kernel-img.conf Those are about the only things I did. Then I tried to upgrade from squeeze to wheezy and got Not a directory at /var/lib/dpkg/info/linux-base.postinst line 1177. ...without further helpful output. That line is part of a generic function, so I straced dpkg --configure -a and found 4875 open(/boot/extlinux/options.cfg, O_RDONLY) = -1 ENOTDIR (Not a directory) I have not investigated further but I guess this is because linux-base is finding /boot/ldlinux.sys and assuming it was configured in the way update-extlinux does it. [...] It's looking for configuration files that might mention block device names, in case they need to be updated. Naturally this is based on the Debian package layout. I'll change it to treat ENOTDIR as non-fatal (same as ENOENT). Ben. -- Ben Hutchings Quantity is no substitute for quality, but it's the only one we've got. signature.asc Description: This is a digitally signed message part
Bug#698215: linux-image-3.2.0-4-amd64: Grub fails loading with cannot read the linux header
Control: reassign -1 grub-pc 1.99-26 Control: tag -1 moreinfo On Tue, 2013-01-15 at 11:51 +0100, Christopher Huhn, GSI wrote: Package: src:linux Version: 3.2.35-2 Severity: important Hi everybody, I'm rather clueless on this error. Grub refuses to boot the current Wheezy kernel on this box. The message is cannot read the linux header. 3.2.0-3-amd64 boots without problems. I reinstalled the kernel package as well as grub-pc and ran update-grub without problems. debsums -sa does not report any modified files for the kernel package or any grub package installed. So I'm a bit clueless. The box is an rather old Intel Core2 6300 box. Could that be the problem? Could this kernel be incompatible with the processor? [...] This is Debian - we carry on supporting hardware until it's turned to rust (well almost). Anyway if GRUB is complaining then the kernel isn't running yet, is it? I'm reassigning this in the hope that GRUB maintainers can debug it. However, the bug reporting instructions for GRUB say: MAKE SURE YOU ARE RUNNING THE LATEST VERSION The grub packages never update the installed version of GRUB automatically, except if you choose a device in the debconf prompt `GRUB install devices', which is currently only implemented for grub-pc. Because of this, you need to make sure you're running the LATEST VERSION of GRUB before you report a bug. Use grub-install to update it, and then check if the bug still applies. Debugging problems we already fixed makes us waste valuable time, so please try to avoid it. They will also want to know: 1. The contents of /proc/mounts, /boot/grub/device.map, and /proc/mdstat (if present) 2. Listings (ls -l) of /dev/disk/by-id and /dev/disk/by-uuid 3. Output of 'debconf-show grub-pc' Ben. -- Ben Hutchings Quantity is no substitute for quality, but it's the only one we've got. signature.asc Description: This is a digitally signed message part
Bug#698221: unblock: qemu/1.1.2+dfsg-5 qemu-kvm/1.1.2+dfsg-5
Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: unblock Please unblock package qemu The updated release includes 3 bugfixes. Changelog with comments: * e1000-discard-oversized-packets-based-on-SBP_LPE.patch: the second half of the fix for CVE-2012-6075. (Finally Closes: #696051) This is a security fix for CVE-2012-6075. As it turned out, there are 2 sides of this issue, and 2 halves for the fix. While we thought the change in previous release (1.1.2+dfsg-3) was enough, it actually is not, since the bug can be triggered using another conditions too. Complete fix contains in 2 changes (which touches the same area): e1000-discard-packets-that-are-too-long-if-not-SBP-and-not-LPE.patch (which was included in 1.1.2+dfsg-3 release) and e1000-discard-oversized-packets-based-on-SBP_LPE.patch (being included now). These patches are used in a recent qemu qemu-kvm security update in squeeze (stable-security) too. Both patches are from upstream. I tried my usual pile of guests here trying to verify there's no visible regressions due to that, all guests seems to continue working fine. The changes only affects e1000 device emulation, and has no impact on other parts of qemu. * linux-user-fix-mips-32-on-64-prealloc-case.patch (Closes: #668658) This is a simple patch which unbreaks MIPS 32bit emulation on 64bit host. Before this patch, mips32 were completely unusable/unworking on any 64bit host, including the most commonly used amd64 one. Also a low-risk change, since it is specific to this architecture (and only for the 32-on-64 case), and makes previously completely non-working stuff working. It is a fix for bug of priority Important, but I think it really is important to fix this for wheezy and not let wheezy be released without it, since emulation of mips is important enough. * fix USB regression introduced in 1.1 (Closes: #683983) uhci-don-t-queue-up-packets-after-one-with-the-SPD-flag-set.patch Big thanks to Peter Schaefer (https://bugs.launchpad.net/bugs/1033727) for the help identifying the fix. This is another fix for Important bug. As it turned out, many real USB devices which worked in previous versions of qemu[-kvm] (in wheezy/testing, before 1.1 version) were broken since 1.1 version. I've got many reports about various devices not working anymore. It turned out that only certain sequence of events triggers this issue, and not all guests and not all devices triggers it, but general result of this bug is quite bad. Supporting USB in a more or less reliable way is important because qemu is often used to run proprietary windows-only programs to flash a phone over USB or things like that, where there's no other good choice available (short of purchasing a separate PC just for that). I'm requesting to unblock both qemu and qemu-kvm at once, since the two are kept in the same state, and since the fixes applicable to both at the same time. However, the mips-related fix is not needed for qemu-kvm, since this one is x86-only. So qemu-kvm change does not include the mips-related fix. Other than that, the changes are exactly the same, including version numbers. Debdiff between qemu/1.1.2+dfsg-3 (currently in testing) and qemu/1.1.2+dfsg-5: -- diff -Nru qemu-1.1.2+dfsg/debian/changelog qemu-1.1.2+dfsg/debian/changelog --- qemu-1.1.2+dfsg/debian/changelog2012-12-16 23:24:01.0 +0400 +++ qemu-1.1.2+dfsg/debian/changelog2013-01-14 12:20:29.0 +0400 @@ -1,3 +1,20 @@ +qemu (1.1.2+dfsg-5) unstable; urgency=low + + * fix USB regression introduced in 1.1 (Closes: #683983) +uhci-don-t-queue-up-packets-after-one-with-the-SPD-flag-set.patch +Big thanks to Peter Schaefer (https://bugs.launchpad.net/bugs/1033727) +for the help identifying the fix. + + -- Michael Tokarev m...@tls.msk.ru Mon, 14 Jan 2013 12:20:29 +0400 + +qemu (1.1.2+dfsg-4) unstable; urgency=medium + + * linux-user-fix-mips-32-on-64-prealloc-case.patch (Closes: #668658) + * e1000-discard-oversized-packets-based-on-SBP_LPE.patch: the second +half of the fix for CVE-2012-6075. (Finally Closes: #696051) + + -- Michael Tokarev m...@tls.msk.ru Wed, 09 Jan 2013 23:05:17 +0400 + qemu (1.1.2+dfsg-3) unstable; urgency=low * add build-dependency on libcap-dev [linux-any] to enable virtfs support diff -Nru qemu-1.1.2+dfsg/debian/patches/e1000-discard-oversized-packets-based-on-SBP_LPE.patch qemu-1.1.2+dfsg/debian/patches/e1000-discard-oversized-packets-based-on-SBP_LPE.patch --- qemu-1.1.2+dfsg/debian/patches/e1000-discard-oversized-packets-based-on-SBP_LPE.patch 1970-01-01 03:00:00.0 +0300 +++ qemu-1.1.2+dfsg/debian/patches/e1000-discard-oversized-packets-based-on-SBP_LPE.patch 2013-01-14 12:13:18.0 +0400 @@ -0,0 +1,39 @@ +commit 2c0331f4f7d241995452b99afaf0aab00493334a +Author: Michael Contreras mich...@inetric.com +Date: Wed Dec 5 13:31:30 2012 -0500 +Bug-Debian:
Bug#698019: libav: the effective GPL-licensed status of the binary packages should be clearly documented
Quoting Thibaut Paumard (2013-01-14 23:29:40) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Le 14/01/2013 23:45, Francesco Poli a écrit : On Mon, 14 Jan 2013 11:13:48 +0100 Jonas Smedegaard wrote: Quoting Charles Plessy (2013-01-14 02:55:38) On Sat, Jan 12, 2013 at 11:43 PM, Francesco Poli (wintermute) I think that the effective licensing status of the binary packages (GPL-2+ or GPL-3+) should be explicitly and clearly documented in the comment at the beginning of the debian/copyright file and, probably, in the binary package long descriptions, as well. [...] Since currently there is no better place (at least, not one I am aware of) to carry these considerations and since I am convinced that such considerations are important, I still think that the comment should be kept in the debian/copyright file and clarified. Hi, I'm surprised it has not yet been pointed out, but I have always considered the right place to document copyright information for individual binary packages is package.copyright, which ends up as simply /u/s/d/package/copyright. I'm also surprised to not find it right away in either policy or devref. Anyway, man dh_installdocs at least doccuments the technical point. An additional README.Debian at least in the relevant -dev packages does not harm. I am aware of the techical feature of debhelper to install per-package copyright files. In the past I saw that as an indication that indeed the copyright file was intended to cover both source and effective licensing. During my partitipation in defining the copyright file format 1.0, however, it was brought up that there is no such requirement for effective licensing - the current defined purpose of the copyright file apparently is only to cover copyrights and licensing or _source_. - Jonas -- * Jonas Smedegaard - idealist Internet-arkitekt * Tlf.: +45 40843136 Website: http://dr.jones.dk/ [x] quote me freely [ ] ask before reusing [ ] keep private signature.asc Description: signature
Bug#698222: git-import-dsc: does not merge already-imported upstream version
Package: git-buildpackage Version: 0.6.0~git20121124 Severity: wishlist I found the following steps do not work: git-import-orig --no-merge ../foo_1.2.orig.tar.gz git-import-dsc ../foo_1.2-1.dsc The resulting debian/1.2-1 commit is a child of only master, it does not properly merge upstream/1.2 at all. The reason I needed this is because git-import-orig is the only interface with --upstream-vcs-tag. I am importing packages from snapshot.d.o and I want the upstream branch to derive from upstream's git repo. Therefore I needed to import-orig first, then import dsc(s) for that version. The logic in import_dsc seems to assume that if the upstream tag already exists, then it must have already been merged into the debian branch. More robust logic might be to check the ancestry of the debian branch to see if it contains the upstream tag or not. I was able to get by with the following hack that only solves this case but breaks the normal case: diff --git a/gbp/scripts/import_dsc.py b/gbp/scripts/import_dsc.py index 28ceb2e..6b60f00 100644 --- a/gbp/scripts/import_dsc.py +++ b/gbp/scripts/import_dsc.py @@ -344,6 +344,8 @@ def main(argv): parents = [ options.upstream_branch ] if is_empty and not repo.has_branch(options.debian_branch): repo.create_branch(options.debian_branch, commit) +else: +parents = [ options.upstream_branch ] if not src.native: if src.diff or src.deb_tgz: apply_debian_patch(repo, upstream.unpacked, src, options, parents) -- System Information: Debian Release: 7.0 APT prefers testing APT policy: (500, 'testing'), (1, 'experimental'), (1, 'unstable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.2.0-4-amd64 (SMP w/4 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 git-buildpackage depends on: ii devscripts 2.12.6 ii git 1:1.7.10.4-1+wheezy1 ii python 2.7.3~rc2-1 ii python-dateutil 1.5+dfsg-0.1 Versions of packages git-buildpackage recommends: ii cowbuilder0.70 ii pristine-tar 1.25 Versions of packages git-buildpackage suggests: ii python-notify 0.1.1-3 ii unzip 6.0-8 -- 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#698223: roundcube-plugins: plugin show_additional_headers should be configured in /e/r/plugins
Package: roundcube
Version: 0.7.2-5
Severity: wishlist
Hi,
The plugin show_additional_headers is not like all other plugins. To be
able to use it one must add it's config in main.inc.php.
| # plugin: show_additional_headers
| $rcmail_config['show_additional_headers'] = array('Reply-To', ..);
Please make it possible to use a directory from /e/r/plugins like all
other plugins do.
Cheers
-- System Information:
Debian Release: 7.0
APT prefers testing
APT policy: (500, 'testing'), (200, 'unstable')
Architecture: amd64 (x86_64)
Kernel: Linux 3.2.0-4-amd64 (SMP w/2 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 roundcube-plugins depends on:
ii roundcube-core 0.7.2-5
roundcube-plugins recommends no packages.
roundcube-plugins suggests no packages.
Versions of packages roundcube-core depends on:
ii apache2 2.2.22-12
ii apache2-mpm-prefork [httpd] 2.2.22-12
ii dbconfig-common 1.8.47+nmu1
ii debconf [debconf-2.0]1.5.49
ii libjs-jquery 1.7.2+dfsg-1
ii libjs-jquery-ui 1.8.ooops.21+dfsg-2
ii libmagic15.11-2
ii php-auth 1.6.2-1
ii php-mail-mime1.8.4-1
ii php-mdb2 2.5.0b3-2
ii php-net-smtp 1.6.1-1
ii php-net-socket 1.0.9-2
ii php5 5.4.4-10
ii php5-gd 5.4.4-10
ii php5-intl5.4.4-10
ii php5-mcrypt 5.4.4-10
ii php5-pspell 5.4.4-10
ii roundcube-pgsql 0.7.2-5
ii tinymce 3.4.8+dfsg0-1
ii ucf 3.0025+nmu3
Versions of packages roundcube-core suggests:
ii php-auth-sasl 1.0.4-1
pn php-crypt-gpg none
Versions of packages roundcube depends on:
ii roundcube-core 0.7.2-5
-- Configuration Files:
/etc/roundcube/plugins/managesieve/config.inc.php changed [not included]
-- debconf information:
roundcube/upgrade-error: abort
roundcube/pgsql/authmethod-user: password
roundcube/purge: false
* roundcube/dbconfig-install: true
* roundcube/language: en_US
roundcube/db/dbname: roundcube
roundcube/remote/newhost:
roundcube/pgsql/changeconf: false
roundcube/upgrade-backup: true
roundcube/install-error: abort
roundcube/mysql/admin-user: root
* roundcube/hosts: localhost
roundcube/pgsql/authmethod-admin: ident
roundcube/dbconfig-remove:
roundcube/pgsql/admin-user: postgres
roundcube/internal/skip-preseed: true
roundcube/db/app-user: roundcube
roundcube/dbconfig-reinstall: false
roundcube/mysql/method: unix socket
roundcube/remove-error: abort
* roundcube/restart-webserver: false
roundcube/dbconfig-upgrade: true
roundcube/remote/port:
roundcube/pgsql/method: unix socket
roundcube/pgsql/manualconf:
roundcube/db/basepath:
roundcube/pgsql/no-empty-passwords:
roundcube/passwords-do-not-match:
roundcube/internal/reconfiguring: false
* roundcube/reconfigure-webserver:
* roundcube/database-type: pgsql
roundcube/remote/host:
roundcube/missing-db-package-error: abort
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#698224: zsh-common: unowned directories in /usr/local after purge (policy 6.8 and 9.1.2): /usr/local/share/zsh/{, site-functions/}
Package: zsh-common Version: 5.0.2-2 Severity: normal User: debian...@lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed your package left unowned files on the system after purge, which is a violation of policy 6.8: http://www.debian.org/doc/debian-policy/ch-maintainerscripts.html#s-removedetails From the attached log (scroll to the bottom...): 2m57.7s ERROR: FAIL: Package purging left files on system: /usr/local/share/zsh/ not owned /usr/local/share/zsh/site-functions/ not owned Leaving directories in /usr/local after purge is also a violation of a should-directive in http://www.debian.org/doc/debian-policy/ch-opersys.html#s9.1.2 cheers, Andreas zsh-common_5.0.2-2.log.gz Description: GNU Zip compressed data
Bug#695259: build a python3-magic package
tags 695259 + patch thanks patch at https://patches.ubuntu.com/f/file/file_5.11-2ubuntu1.patch building a binary indep python3-magic package. note that the python-magic package can be made binary indep too, and the python-dbg-magic be dropped. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#698225: linux-image-2.6.32-5-686-bigmem: split-brain when running drbdadm primary $DEV with dual primary setup in Sec/Sec state
Package: linux-2.6
Version: 2.6.32-46
Severity: normal
While in this state:
0: cs:Connected ro:Secondary/Secondary ds:UpToDate/UpToDate C r
ns:0 nr:0 dw:0 dr:0 al:0 bm:0 lo:0 pe:0 ua:0 ap:0 ep:1 wo:b oos:0
Issue
drbdadm primary $DEV
On both nodes at the same time (either via cluster resource manager, or mssh)
will lead to a split brain:
[ 5067.503912] block drbd0: Split-Brain detected, dropping connection!
0: cs:StandAlone ro:Primary/Unknown ds:UpToDate/DUnknown r
ns:0 nr:0 dw:0 dr:420 al:0 bm:0 lo:0 pe:0 ua:0 ap:0 ep:1 wo:b oos:0
I can reproduce this with a 64 bit kernel, and with kernel/drbd8-utils from
backports (also 32/64 bit).
-- System Information:
Debian Release: 6.0.6
APT prefers stable
APT policy: (500, 'stable')
Architecture: i386 (i686)
Kernel: Linux 2.6.32-5-686-bigmem (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
Versions of packages drbd8-utils depends on:
ii debconf [debconf-2.0] 1.5.36.1 Debian configuration management sy
ii libc6 2.11.3-4 Embedded GNU C Library: Shared lib
drbd8-utils recommends no packages.
Versions of packages drbd8-utils suggests:
pn heartbeat none (no description available)
-- Configuration Files:
/etc/drbd.d/debian7.res
resource debian7 {
net {
sndbuf-size 0;
max-buffers 8000;
max-epoch-size 8000;
allow-two-primaries;
after-sb-0pri discard-zero-changes;
after-sb-1pri consensus;
after-sb-2pri disconnect;
}
syncer {
rate 40M;
}
device/dev/drbd0;
disk /dev/sys/debian7;
meta-disk internal;
on debian8 {
address 192.168.0.8:7791;
}
on debian9 {
address 192.168.0.9:7791;
}
}
/etc/drbd.d/global_common.conf changed:
global {
usage-count no;
# minor-count dialog-refresh disable-ip-verification
}
common {
protocol C;
handlers {
pri-on-incon-degr /usr/lib/drbd/notify-pri-on-incon-degr.sh;
/usr/lib/drbd/notify-emergency-reboot.sh; echo b /proc/sysrq-trigger ; reboot
-f;
pri-lost-after-sb /usr/lib/drbd/notify-pri-lost-after-sb.sh;
/usr/lib/drbd/notify-emergency-reboot.sh; echo b /proc/sysrq-trigger ; reboot
-f;
local-io-error /usr/lib/drbd/notify-io-error.sh;
/usr/lib/drbd/notify-emergency-shutdown.sh; echo o /proc/sysrq-trigger ; halt
-f;
# fence-peer /usr/lib/drbd/crm-fence-peer.sh;
# split-brain /usr/lib/drbd/notify-split-brain.sh root;
# out-of-sync /usr/lib/drbd/notify-out-of-sync.sh root;
# before-resync-target
/usr/lib/drbd/snapshot-resync-target-lvm.sh -p 15 -- -c 16k;
# after-resync-target
/usr/lib/drbd/unsnapshot-resync-target-lvm.sh;
}
startup {
# wfc-timeout degr-wfc-timeout outdated-wfc-timeout
wait-after-sb
}
disk {
# on-io-error fencing use-bmbv no-disk-barrier no-disk-flushes
# no-disk-drain no-md-flushes max-bio-bvecs
}
net {
# sndbuf-size rcvbuf-size timeout connect-int ping-int
ping-timeout max-buffers
# max-epoch-size ko-count allow-two-primaries cram-hmac-alg
shared-secret
# after-sb-0pri after-sb-1pri after-sb-2pri data-integrity-alg
no-tcp-cork
}
syncer {
# rate after al-extents use-rle cpu-mask verify-alg csums-alg
}
}
-- no debconf information
-- Package-specific info:
** Version:
Linux version 2.6.32-5-686-bigmem (Debian 2.6.32-46) (da...@debian.org) (gcc
version 4.3.5 (Debian 4.3.5-4) ) #1 SMP Sun Sep 23 10:27:25 UTC 2012
** Command line:
BOOT_IMAGE=/vmlinuz-2.6.32-5-686-bigmem root=/dev/mapper/sys-root ro quiet
** Not tainted
** Kernel log:
[ 5034.677693] block drbd0: peer( Unknown - Secondary ) conn( WFReportParams
- WFBitMapT ) pdsk( DUnknown - UpToDate )
[ 5034.690089] block drbd0: conn( WFBitMapT - WFSyncUUID )
[ 5034.691786] block drbd0: helper command: /sbin/drbdadm before-resync-target
minor-0
[ 5034.692927] block drbd0: helper command: /sbin/drbdadm before-resync-target
minor-0 exit code 0 (0x0)
[ 5034.692931] block drbd0: conn( WFSyncUUID - SyncTarget ) disk( UpToDate -
Inconsistent )
[ 5034.692934] block drbd0: Began resync as SyncTarget (will sync 0 KB [0 bits
set]).
[ 5035.242347] block drbd0: Resync done (total 1 sec; paused 0 sec; 0 K/sec)
[ 5035.242355] block drbd0: conn( SyncTarget - Connected ) disk( Inconsistent
- UpToDate )
[ 5035.242362] block drbd0: helper command: /sbin/drbdadm after-resync-target
minor-0
[ 5035.243575] block drbd0: helper command: /sbin/drbdadm after-resync-target
minor-0 exit code 0 (0x0)
[ 5046.639518] block drbd0: peer( Secondary - Unknown ) conn( Connected -
TearDown ) pdsk( UpToDate - DUnknown )
[ 5046.639942] block drbd0: meta connection shut down by peer.
[ 5046.639993] block
Bug#692416: Wheezy with dlopen enabled
Having the same issue on a wheezy machine with Samba4. I'm also curious if this will be fixed in wheezy too. Regards Peter -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#692416: Wheezy with dlopen enabled
Having the same issue on a wheezy machine with Samba4. I'm also curious if this will be fixed for wheezy too. Regards Peter -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#698019: libav: the effective GPL-licensed status of the binary packages should be clearly documented
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Le 15/01/2013 14:41, Jonas Smedegaard a écrit : Quoting Thibaut Paumard (2013-01-14 23:29:40) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Le 14/01/2013 23:45, Francesco Poli a écrit : On Mon, 14 Jan 2013 11:13:48 +0100 Jonas Smedegaard wrote: Quoting Charles Plessy (2013-01-14 02:55:38) On Sat, Jan 12, 2013 at 11:43 PM, Francesco Poli (wintermute) I think that the effective licensing status of the binary packages (GPL-2+ or GPL-3+) should be explicitly and clearly documented in the comment at the beginning of the debian/copyright file and, probably, in the binary package long descriptions, as well. [...] Since currently there is no better place (at least, not one I am aware of) to carry these considerations and since I am convinced that such considerations are important, I still think that the comment should be kept in the debian/copyright file and clarified. Hi, I'm surprised it has not yet been pointed out, but I have always considered the right place to document copyright information for individual binary packages is package.copyright, which ends up as simply /u/s/d/package/copyright. I'm also surprised to not find it right away in either policy or devref. Anyway, man dh_installdocs at least doccuments the technical point. An additional README.Debian at least in the relevant -dev packages does not harm. Hi again, All I'm saying is that the natural place to look for such information is the binary package's copyright file, a.k.a. debian/package.copyright, and that neither devref not Policy mention the latter. In the past I saw that as an indication that indeed the copyright file was intended to cover both source and effective licensing. Yes, that's also my reading of Policy 12.5: http://www.debian.org/doc/debian-policy/ch-docs.html#s-copyrightfile Every package must be accompanied by a verbatim copy of its copyright information and distribution license in the file /usr/share/doc/package/copyright. In other words, copyright file (as distributed in the binary package) must cover not only the copyright (which applies mostly on the source) but also the distribution license (which applies on the binaries as well). Note the *must* here in the binary package, in contrast with *should* debian/copyright in the source package: A copy of the file which will be installed in /usr/share/doc/package/copyright should be in debian/copyright in the source package. which implicitly allows for debian/package.copyright in relevant cases, i.e. when the applicable license terms is not the same for all the binaries, e.g. some binary linked with GPLed code. During my partitipation in defining the copyright file format 1.0, however, it was brought up that there is no such requirement for effective licensing - the current defined purpose of the copyright file apparently is only to cover copyrights and licensing or _source_. I'd be interested in the reasoning behind this, because I think you where right in the first place. In the first quote above, its [...] distribution license refers to the package. Very clearly, package here must be read as binary package, which you grab from a few lines later: /usr/share/doc/package may be a symbolic link to another directory in /usr/share/doc only if the two packages both come from the same source and the first package Depends on the second. Kind regards, Thibaut. -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.12 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iQIcBAEBCAAGBQJQ9WeGAAoJEJOUU0jg3ChA+jwQAJaGlJm6ljuzYFV266yQr0V/ Kva9ofaeBSxJPMBvipudv53Rcd51QykG6HHyKYBzmBGiDL0VS0hj8qXTEhCO2ECW 6Joe2ILzzBi3QZcGV1mQ3TrkfbjEgBO6/bG1fh1HZn4DWC5IENnJsff3zPBldPA3 zQ65dq3atZ8FEZoAxHGRPbJYHBBDBrLyq3AlyKoXOdGjl67ciPYptHei+cn7y0Ti i0CUfspEY70UCiYtw/YP9mCpEzIVlx+gYQly0ct6td2Rx142lhG0Jhwp7rMrn7nN tD+rOxc1X/5a3bFGGXxIeDvzJw/2OECVpKDvMGw0Wh4L3rUjYej+WSl9DMVSkzrK /DnjL6RhyulFSwMHPLdELMr+1CzbmpCXi8UkGshBEnML5NvzOn44yvrJNju0wkW/ fjZTtXfIUoMweI2VIpCPK3Aa4bffG1YCrLjOg3/WIf2MNsLMTIv1BUGTo9uDz6hP 3uaKJDG0AUruiqtplvG4P8UTBSwBY8Af/Pyp9vXOWdcLAp/A1OyE+lfLcEj2lC3M xGUIz35gBiNjrUJRf2PloXrIqHFedHCGhFn/2u6a2YerblKUcs7MV87Ujqs8oltR Fmuk50SIa1FAvaTwrqocQYkkohhRdZHNQXozvNpQdzjuTiVm3BvpUonm8PGHpkfq 9hLnuuCdzVGAm6LVYPiO =+ZnX -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#698214: ruby-diff-lcs needs to be rebuilt against newer gem2deb
Control: severity -1 minor Control: retitle -1 ruby-diff-lcs needs to be rebuilt against gem2deb=0.3.0 Hi! Thanks for your report. Integration of Ruby Debian packages with rubygems arrived late in the release cycle for Wheezy, but it requires rebuilding the packages with newer gem2deb (= 0.3.0~). Unfortunately, not all packages could be uploaded before the freeze, so some of them go not provide integration with rubygems. See http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=691317 for a similar problem. The solution as you found is to rebuild the packages locally. Another possibility is to patch out from the gems you use the requirement on rubygems, if you ensure that all the dependencies are already installed. Anyway, this will be fixed automatically when a new version of the package will be uploaded to the archive, which unfortunately is not likely to happen before the release of Wheezy. Thanks for your understanding. Cheers, Cédric -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#698215: linux-image-3.2.0-4-amd64: Grub fails loading with cannot read the linux header
Hi, On 15.01.2013 14:26, Ben Hutchings wrote: This is Debian - we carry on supporting hardware until it's turned to rust (well almost). Anyway if GRUB is complaining then the kernel isn't running yet, is it? No, it was not. Because of this, you need to make sure you're running the LATEST VERSION of GRUB before you report a bug. Use grub-install to update it, and then check if the bug still applies. Debugging problems we already fixed makes us waste valuable time, so please try to avoid it. This exactly was not the case - and fixed my problem. Shame on me. I still think it's strange that the old grub could run 3.2.0-3 but not 3.2.0-4. That's why the kernel was my first suspect. Unfortunately this means that I may have to update grub with each release (or kernel?) upgrade on a couple of servers (~ 1000), automatically choosing the proper boot device, which is normally handled for me by FAI at install time and may be cumbersome eg. for software RAIDs. Please close this bug. Sorry for the inconvenience. Kind regards, Christopher smime.p7s Description: S/MIME Cryptographic Signature
Bug#698217: mssh: shift+insert only pastes to first window
Control: tag -1 + moreinfo unreproducible Hi Stefan, Stefan Voelkel wrote: Package: mssh Version: 1.2-1 Severity: normal Using shit+insert will only insert text into the first window. I'm sorry, I can't reproduce that. Shift-Insert works for me on Squeeze in all these cases as expected: 1) Pressing Shift-Insert in the input field at the top (paste goes to all subwindows) 2) Clicking in the first window and then pressing Shift-Insert (paste goes to the first subwindow) 3) Clicking in the second window and then pressing Shift-Insert (paste goes to the second subwindow) Did you try to press Shift-Insert with focus on the inputfield at the top or into single subwindows when you experienced that issue? (Maybe we can track down and reproduce it that way.) Pasting using middle mousebutton works though. Yep. Works for me in all three cases, too. 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#698224: [Pkg-zsh-devel] Bug#698224: zsh-common: unowned directories in /usr/local after purge (policy 6.8 and 9.1.2): /usr/local/share/zsh/{, site-functions/}
Hi Andreas, Andreas Beckmann wrote: during a test with piuparts I noticed your package left unowned files on the system after purge, which is a violation of policy 6.8: http://www.debian.org/doc/debian-policy/ch-maintainerscripts.html#s-removedetails From the attached log (scroll to the bottom...): 2m57.7s ERROR: FAIL: Package purging left files on system: /usr/local/share/zsh/not owned /usr/local/share/zsh/site-functions/ not owned Thanks for the report, I'll have a look at it. 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#694778: A little test message to see whether our filters work now
Sorry for the hijack of your RFS, I'm testing our new mail filter. Please ignore me :) -- with kind regards, Arno Töll IRC: daemonkeeper on Freenode/OFTC GnuPG Key-ID: 0x9D80F36D signature.asc Description: OpenPGP digital signature
Bug#694778: A little test message to see whether our filters work now
On Tue, Jan 15, 2013 at 9:58 AM, Arno Töll a...@debian.org wrote: Sorry for the hijack of your RFS, I'm testing our new mail filter. Please ignore me :) (don't tell me what to do) -- with kind regards, Arno Töll IRC: daemonkeeper on Freenode/OFTC GnuPG Key-ID: 0x9D80F36D -- :wq -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#698225: linux-image-2.6.32-5-686-bigmem: split-brain when running drbdadm primary $DEV with dual primary setup in Sec/Sec state
Control: tags -1 moreinfo On Tue, Jan 15, 2013 at 03:18:11PM +0100, b...@bc-bd.org wrote: Issue drbdadm primary $DEV On both nodes at the same time (either via cluster resource manager, or mssh) will lead to a split brain: This does not match the kernel log, as far as I understand it. [ 5067.503912] block drbd0: Split-Brain detected, dropping connection! This is correct according to the log. [ 5034.677693] block drbd0: peer( Unknown - Secondary ) conn( WFReportParams - WFBitMapT ) pdsk( DUnknown - UpToDate ) [ 5034.690089] block drbd0: conn( WFBitMapT - WFSyncUUID ) [ 5034.691786] block drbd0: helper command: /sbin/drbdadm before-resync-target minor-0 [ 5034.692927] block drbd0: helper command: /sbin/drbdadm before-resync-target minor-0 exit code 0 (0x0) [ 5034.692931] block drbd0: conn( WFSyncUUID - SyncTarget ) disk( UpToDate - Inconsistent ) [ 5034.692934] block drbd0: Began resync as SyncTarget (will sync 0 KB [0 bits set]). [ 5035.242347] block drbd0: Resync done (total 1 sec; paused 0 sec; 0 K/sec) [ 5035.242355] block drbd0: conn( SyncTarget - Connected ) disk( Inconsistent - UpToDate ) [ 5035.242362] block drbd0: helper command: /sbin/drbdadm after-resync-target minor-0 [ 5035.243575] block drbd0: helper command: /sbin/drbdadm after-resync-target minor-0 exit code 0 (0x0) A sync from the remote disk. [ 5046.639518] block drbd0: peer( Secondary - Unknown ) conn( Connected - TearDown ) pdsk( UpToDate - DUnknown ) [ 5046.639942] block drbd0: meta connection shut down by peer. Remote was shut down. [ 5046.639993] block drbd0: asender terminated [ 5046.639994] block drbd0: Terminating drbd0_asender [ 5046.641094] block drbd0: conn( TearDown - Disconnecting ) [ 5046.659176] block drbd0: Connection closed [ 5046.659182] block drbd0: conn( Disconnecting - StandAlone ) [ 5046.659217] block drbd0: receiver terminated [ 5046.659218] block drbd0: Terminating drbd0_receiver [ 5046.659221] block drbd0: disk( UpToDate - Diskless ) [ 5046.659296] block drbd0: drbd_bm_resize called with capacity == 0 [ 5046.659305] block drbd0: worker terminated [ 5046.659307] block drbd0: Terminating drbd0_worker Device is gone. [ 5067.155466] block drbd0: Starting worker thread (from cqueue [2337]) [ 5067.155541] block drbd0: disk( Diskless - Attaching ) [ 5067.207081] block drbd0: conn( Unconnected - WFConnection ) Device enabled again and trying to connect. [ 5067.208501] block drbd0: role( Secondary - Primary ) [ 5067.212759] block drbd0: Creating new current UUID Set to primary. [ 5067.503518] block drbd0: Handshake successful: Agreed network protocol version 91 [ 5067.503525] block drbd0: conn( WFConnection - WFReportParams ) Connection established _after_ it was promoted to primary. [ 5067.503888] block drbd0: drbd_sync_handshake: [ 5067.503894] block drbd0: self D88E7AD12FFEA493:49D971C9C18FC2FE:167E069D45704F1A:F1C0D4200B9792F4 bits:0 flags:0 [ 5067.503899] block drbd0: peer DD932456670DF62F:49D971C9C18FC2FE:167E069D45704F1A:F1C0D4200B9792F4 bits:0 flags:0 The remote device was also promoted to primary before the connection was established. You have to wait until both machines are connected before promoting them to primary. The init script does this. Bastian -- Behind every great man, there is a woman -- urging him on. -- Harry Mudd, I, Mudd, stardate 4513.3 -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#698215: linux-image-3.2.0-4-amd64: Grub fails loading with cannot read the linux header
On Tue, 2013-01-15 at 15:40 +0100, Christopher Huhn wrote: Hi, On 15.01.2013 14:26, Ben Hutchings wrote: This is Debian - we carry on supporting hardware until it's turned to rust (well almost). Anyway if GRUB is complaining then the kernel isn't running yet, is it? No, it was not. Because of this, you need to make sure you're running the LATEST VERSION of GRUB before you report a bug. Use grub-install to update it, and then check if the bug still applies. Debugging problems we already fixed makes us waste valuable time, so please try to avoid it. This exactly was not the case - and fixed my problem. Shame on me. I still think it's strange that the old grub could run 3.2.0-3 but not 3.2.0-4. That's why the kernel was my first suspect. Unfortunately this means that I may have to update grub with each release (or kernel?) upgrade on a couple of servers (~ 1000), automatically choosing the proper boot device, which is normally handled for me by FAI at install time and may be cumbersome eg. for software RAIDs. This should be remembered by debconf (grub-pc/install_devices variable). I'm not sure whether there's a good way to get that information outside of a package maintainer script, though. Please close this bug. Sorry for the inconvenience. Well, if this is a widespread problem then I think grub-pc must reinstall when the package is upgraded from a version has this bug. We cannot have upgrades resulting in an unbootable system. Were these systems initially installed with squeeze, or an earlier version? Ben. -- Ben Hutchings Quantity is no substitute for quality, but it's the only one we've got. signature.asc Description: This is a digitally signed message part
Bug#694778: A little test message to see whether our filters work now
I should also note a review for this package was sent off-report :) Cheers, T On Tue, Jan 15, 2013 at 10:01 AM, Paul Tagliamonte paul...@debian.org wrote: On Tue, Jan 15, 2013 at 9:58 AM, Arno Töll a...@debian.org wrote: Sorry for the hijack of your RFS, I'm testing our new mail filter. Please ignore me :) (don't tell me what to do) -- with kind regards, Arno Töll IRC: daemonkeeper on Freenode/OFTC GnuPG Key-ID: 0x9D80F36D -- :wq -- :wq -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#698226: LibGimpWidgets-CRITICAL **: gimp_preview_area_draw: assertion `buf != NULL' failed
Package: gimp Version: 2.6.10-1+squeeze3 Severity: normal I am being stuck because of #685802. Gimp cannot load a .wmf properly: $ gimp test.wmf ERROR: font.c (1334): wmf_ipa_font_map: failed to load *any* font! (file-wmf:26725): Gtk-CRITICAL **: gtk_widget_set_size_request: assertion `width = -1' failed ERROR: font.c (1334): wmf_ipa_font_map: failed to load *any* font! (file-wmf:26725): LibGimpWidgets-CRITICAL **: gimp_preview_area_draw: assertion `buf != NULL' failed ERROR: font.c (1334): wmf_ipa_font_map: failed to load *any* font! How can I possibly pass `--wmf-fontdir=/usr/share/fonts/type1/gsfonts` to gimp ? Thanks -- 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.4-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 gimp depends on: ii gimp-data 2.6.10-1+squeeze3 Data files for GIMP ii libaa1 1.4p5-38 ascii art library ii libatk1.0-01.30.0-1 The ATK accessibility toolkit ii libbabl-0.0-0 0.0.22-1 Dynamic, any to any, pixel format ii libc6 2.11.3-4 Embedded GNU C Library: Shared lib ii libcairo2 1.10.2-7~bpo60+1 The Cairo 2D vector graphics libra ii libdbus-1-31.2.24-4+squeeze1 simple interprocess messaging syst ii libdbus-glib-1-2 0.88-2.1 simple interprocess messaging syst ii libexif12 0.6.19-1+squeeze1 library to parse EXIF files ii libfontconfig1 2.8.0-2.1 generic font configuration library ii libfreetype6 2.4.9-1~bpo60+1 FreeType 2 font engine, shared lib ii libgegl-0.0-0 0.0.22-2+b1 Generic Graphics Library ii libgimp2.0 2.6.10-1+squeeze3 Libraries for the GNU Image Manipu ii libglib2.0-0 2.24.2-1 The GLib library of C routines ii libgtk2.0-02.20.1-2 The GTK+ graphical user interface ii libhal10.5.14-3 Hardware Abstraction Layer - share ii libjpeg62 6b1-1 The Independent JPEG Group's JPEG ii liblcms1 1.18.dfsg-1.2+b3 Color management library ii libmng11.0.10-1+b1 Multiple-image Network Graphics li ii libpango1.0-0 1.28.3-1+squeeze2 Layout and rendering of internatio ii libpng12-0 1.2.44-1+squeeze4 PNG library - runtime ii libpoppler-glib4 0.12.4-1.2PDF rendering library (GLib-based ii librsvg2-2 2.26.3-1 SAX-based renderer library for SVG ii libtiff4 3.9.4-5+squeeze8 Tag Image File Format (TIFF) libra ii libwebkit-1.0-21.2.7-0+squeeze2 Web content engine library for Gtk ii libwmf0.2-70.2.8.4-6.1+b1Windows metafile conversion librar ii libx11-6 2:1.3.3-4 X11 client-side library ii libxext6 2:1.1.2-1 X11 miscellaneous extension librar ii libxfixes3 1:4.0.5-1 X11 miscellaneous 'fixes' extensio ii libxmu62:1.0.5-2 X11 miscellaneous utility library ii libxpm41:3.5.8-1 X11 pixmap library ii python 2.6.6-3+squeeze7 interactive high-level object-orie ii python-gtk22.17.0-4 Python bindings for the GTK+ widge ii python-support 1.0.10automated rebuilding support for P ii zlib1g 1:1.2.3.4.dfsg-3 compression library - runtime gimp recommends no packages. Versions of packages gimp suggests: ii ghostscript8.71~dfsg2-9+squeeze1 The GPL Ghostscript PostScript/PDF pn gimp-data-extras none(no description available) pn gimp-help-en | gim none(no description available) ii gvfs-backends 1.6.4-3 userspace virtual filesystem - bac ii libasound2 1.0.23-2.1shared library for ALSA applicatio -- 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#694778: A little test message to see whether our filters work now
ok :) 2013/1/15 Arno Töll a...@debian.org Sorry for the hijack of your RFS, I'm testing our new mail filter. Please ignore me :) -- with kind regards, Arno Töll IRC: daemonkeeper on Freenode/OFTC GnuPG Key-ID: 0x9D80F36D
Bug#697952: Please parse the X-Debian-Homepage field and display it as a link
On Tue, Jan 15, 2013 at 09:01:42AM +0100, Mehdi Dogguy wrote: Hi, Le 2013-01-11 22:09, Guido Günther a écrit : several teams maintain additional information about packages e.g. in the Wiki. It'd be great to have a linkt to this information available on the packges.qa.debian.org page. I'd propose to use a X-Debian-Homepage: field in debian/control for that and handle it similar to Homepage: for the upstream homepage: Shouldn't such enhancements go through the DEP process? I'm not meaning to stop your work. I find the idea very good. But I think we should bring it to wider audience to start a discussion. DEP looks the right place for it. Had a short train ride to work on this: http://dep.debian.net/deps/dep13/ I'd appreciate any comments before we moving this to a broader discussion. Cheers, -- Guido -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#698227: Cannot convert SVG to WMF
Package: python-uniconvertor Version: 1.1.4-1+b1 Severity: normal When I use uniconvertor to convert this SVG to WMF, the image turns pretty much all black. Re-opening the generated file with inkscape will show a very dark generated file. Steps: $ wget http://openclipart.org/people/Anonymous/Anonymous_pc_box.svg $ uniconvertor Anonymous_pc_box.svg test.wmf Tests with: $ inkscape test.wmf Thanks -- 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.4-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 python-uniconvertor depends on: ii libc6 2.11.3-4 Embedded GNU C Library: Shared lib ii python 2.6.6-3+squeeze7 interactive high-level object-orie ii python-imaging 1.1.7-2 Python Imaging Library ii python-reportlab2.4-4ReportLab library to create PDF do ii python-support 1.0.10 automated rebuilding support for P python-uniconvertor recommends no packages. Versions of packages python-uniconvertor suggests: pn python-uniconvertor-dbg 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#697864: [Pkg-libvirt-maintainers] Bug#697864: virtinst: Locale shouldn't be blocking virt-clone
On Mon, Jan 14, 2013 at 03:21:28PM -0500, Cole Robinson wrote: On 01/10/2013 10:55 AM, Kwadronaut-debian wrote: Package: virtinst Version: 0.500.3-2 Severity: normal Virt-clone fails if not every single locale environment variable present is supported. A fairly normal use case is someone logging in remotely and having her local environment variables in use remotely as well. Setting something like LC_TELEPHONE=hy_AM UTF-8 should be treated as irrelevant for virt-clone. The generated traceback could probably be a warning and/or made more useful. Traceback (most recent call last): File /usr/bin/virt-clone, line 33, in module cli.setupGettext() File /usr/lib/pymodules/python2.6/virtinst/cli.py, line 133, in setupGettext locale.setlocale(locale.LC_ALL, '') File /usr/lib/python2.6/locale.py, line 513, in setlocale return _setlocale(category, locale) locale.Error: unsupported locale setting Fixed upstream now: http://git.fedorahosted.org/cgit/python-virtinst.git/commit/?id=0ac06166fc116e3c8dd2591830f8db4b129b658f Cool! We're to deep in a freeze for the Debian Wheezy to pick this up but I'll make sure it's in our next upload to experimental. Cheers, -- Guido ___ Pkg-libvirt-maintainers mailing list pkg-libvirt-maintain...@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-libvirt-maintainers -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#698228: unblock: nvidia-graphics-drivers-legacy-173xx/173.14.35-4
Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: unblock Please unblock package nvidia-graphics-drivers-legacy-173xx All changes from nvidia-graphics-drivers that recently migrated to testing (or are at least unblocked) and are applicable to the legacy drivers as well have been merged into 173.14.35-4 to apply the fixes and keep the packaging in sync: * Synchronize packaging with nvidia-graphics-drivers 304.37-1: - 3.6_kernel.patch: New patch to fix compilation with Linux 3.6, taken from rpmfusion. * Adjust 3.6_kernel.patch for a different filename in legacy-173xx. (this trivial patch is no longer in n-g-d since it was fixed in newer upstream releases) * Synchronize packaging with nvidia-graphics-drivers 304.48-2: - libgl1-nvidia-legacy-173xx-glx-ia32: readd Depends: libgl1-nvidia-alternatives-ia32 to prevent apt from removing libgl1-nvidia-alternatives-ia32 (which would remove the diversions) while the old (pre-transitional) libgl1-nvidia-legacy-173xx-glx-ia32 is still installed. - get-orig-source: Fix caching for legacy drivers. - bug-control: Report version info about revived libgl1-nvidia-legacy-96xx-glx-ia32. - Upgrade nvidia-settings relationship from Suggests to Recommends and use a substvar for the name of the compatible nvidia-settings package. - There is no need to exclude squeeze-backports from using xz compression. * Use nvidia-settings-legacy-173xx as the name of the compatible nvidia-settings package. * Synchronize packaging with nvidia-graphics-drivers 304.60-1: - libgl1-nvidia-legacy-173xx-glx:i386: Breaks: ia32-libs ( 1:0), versioning was fixed. - Fix missing legacy substitution. - conftest.h: - Implement checks for linux/efi.h and linux/nvmap.h (310.14). - Implement new conftest.sh functions outer_flush_all, nvmap_support, and efi_enabled (310.14). * Synchronize packaging with nvidia-graphics-drivers 304.60-2: - build-module-packages.sh: Build modules only for the variant (current or legacy-abcxx) that shipped the script. * Synchronize packaging with nvidia-graphics-drivers 304.64-1: - conftest.h: Implement new conftest.sh function set_memory_array_uc. - build-module-packages.sh: Build modules only for the variant (current or legacy-abcxx) that shipped the script. * Synchronize packaging with nvidia-graphics-drivers 304.64-2: - Always use the upstream changelog from the x86_64 release to avoid minor differences causing multiarch conflicts. (all changes up to here were unblocked (#688698) and migrated with 304.64-3) * Synchronize packaging with nvidia-graphics-drivers 304.64-4: - kernel-3.7.patch: New patch to fix compilation with Linux 3.7 (which replaced VM_RESERVED by VM_DONTEXPAND | VM_DONTDUMP). * Adjust kernel-3.7.patch for a different filename in legacy-173xx. (this has been unblocked: #697838) * Synchronize packaging with nvidia-graphics-drivers 304.64-5: - Fix debian/module/debian/kernel-version to cope with $KSRC/linux/version.h being moved to $KSRC/include/generated/uapi/linux/version.h in Linux 3.7. This is the only change not yet in nvidia-graphics-drivers/sid, (so far only in experimental). A trivial followup to kernel-3.7.patch. #696570 The kernel-version script is only needed by the nvidia-kernel-source package which builds the module packages with module-assistant. Andreas unblock nvidia-graphics-drivers-legacy-173xx/173.14.35-4 diffstat for nvidia-graphics-drivers-legacy-173xx-173.14.35 nvidia-graphics-drivers-legacy-173xx-173.14.35 bug-control.in |2 - build-module-packages.sh | 19 build-module-packages.sh.in| 19 changelog | 49 + control|9 +++--- module/conftest.h | 37 +++- module/debian/kernel-version | 16 ++ module/debian/patches/3.6_kernel.patch | 21 ++ module/debian/patches/kernel-3.7.patch | 22 ++ module/debian/patches/series |2 + rules | 13 +--- rules.defs |2 + 12 files changed, 174 insertions(+), 37 deletions(-) diff -Nru nvidia-graphics-drivers-legacy-173xx-173.14.35/debian/bug-control.in nvidia-graphics-drivers-legacy-173xx-173.14.35/debian/bug-control.in --- nvidia-graphics-drivers-legacy-173xx-173.14.35/debian/bug-control.in 2012-09-13 12:31:05.0 +0200 +++ nvidia-graphics-drivers-legacy-173xx-173.14.35/debian/bug-control.in 2013-01-15 15:30:58.0 +0100 @@ -1,3 +1,3 @@ report-with: nvidia-glx#LEGACY# libgl1-nvidia#LEGACY#-glx xserver-xorg-video-nvidia#LEGACY# nvidia-alternative#LEGACY# nvidia-kernel#LEGACY#-dkms
Bug#698222: git-import-dsc: does not merge already-imported upstream version
On Tue, Jan 15, 2013 at 08:43:59AM -0500, Mike Miller wrote: Package: git-buildpackage Version: 0.6.0~git20121124 Severity: wishlist I found the following steps do not work: git-import-orig --no-merge ../foo_1.2.orig.tar.gz git-import-dsc ../foo_1.2-1.dsc The resulting debian/1.2-1 commit is a child of only master, it does not properly merge upstream/1.2 at all. The reason I needed this is because git-import-orig is the only interface with --upstream-vcs-tag. I am importing packages from snapshot.d.o and I want the upstream branch to derive from upstream's git repo. Therefore I needed to import-orig first, then import dsc(s) for that version. The logic in import_dsc seems to assume that if the upstream tag already exists, then it must have already been merged into the debian branch. More robust logic might be to check the ancestry of the debian branch to see if it contains the upstream tag or not. I was able to get by with the following hack that only solves this case but breaks the normal case: diff --git a/gbp/scripts/import_dsc.py b/gbp/scripts/import_dsc.py index 28ceb2e..6b60f00 100644 --- a/gbp/scripts/import_dsc.py +++ b/gbp/scripts/import_dsc.py @@ -344,6 +344,8 @@ def main(argv): parents = [ options.upstream_branch ] if is_empty and not repo.has_branch(options.debian_branch): repo.create_branch(options.debian_branch, commit) +else: +parents = [ options.upstream_branch ] if not src.native: if src.diff or src.deb_tgz: apply_debian_patch(repo, upstream.unpacked, src, options, parents) It seems that we might want to move the upstream-vcs-tag logic to git-import-dsc then. * Don't you still want to import the upstream tarball too? Escpecially when using git-import-dsc I think we should do: * import upstream tarball with the possibility to have the upstream VCS tag as parent (as with git-import-orig) * proceed from there as usual There wouldn't be any need for using git-import-orig then. Patches are welcome. -- Guido -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#679744: updated patch re-based on uif-1.0.6-1.1
An NMU uif-1.0.6-1.1 was yesterday uploaded to the delayed/5 queue. I'm assuming this will not be rejected by the Maintainer. Here is a new (3rd) version of the ipv6 patch re-based against that NMU. debdiff uif_1.0.6-1.1.dsc uif_1.0.6-1.1.ipv6.3.dsc uif_1.0.6-1.1.ipv6.3.patch Regards, Alex Owen uif_1.0.6-1.1.ipv6.3.patch Description: Binary data
Bug#661421: libjpeg8-dev should depend on libc6-dev:${arch} or libc6-dev-${foreign-arch}:${arch}
close 661421 thanks Hi, Problem fixed with libgcc1 version 4.7.0-1 and its multiarch support. I guess we should close the bug then, shouldn't we? :). Cheers, Adrian -- .''`. John Paul Adrian Glaubitz : :' : Debian Developer - glaub...@debian.org `. `' Freie Universitaet Berlin - glaub...@physik.fu-berlin.de `-GPG: 62FF 8A75 84E0 2956 9546 0006 7426 3B37 F5B5 F913 -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#659762: lvremove failure log
After several tries, I managed to reproduce the problem. This time I ran lvremove - -f /dev/vg1/backup, and the output is attached. I hope you can make some sense out of it. /dev/vg1/mongodb is striped LV in VG vg1 on PV /dev/xvdh and PV /dev/xvdi. /dev/vg1/backup is striped snapshot LV of /dev/vg1/mongodb. I hope my setup is straightforward enough - if not, let me know what other information I can provide. Regards, Oskar Liljeblad root@mdb3:~# lvremove - -f /dev/vg1/backup #lvmcmdline.c:1055 Processing: lvremove - -f /dev/vg1/backup #lvmcmdline.c:1058 O_DIRECT will be used #libdm-config.c:789 Setting global/locking_type to 1 #libdm-config.c:789 Setting global/wait_for_locks to 1 #locking/locking.c:242 File-based locking selected. #libdm-config.c:758 Setting global/locking_dir to /run/lock/lvm #toollib.c:228 Using logical volume(s) on command line #locking/file_locking.c:236 Locking /run/lock/lvm/V_vg1 WB #locking/file_locking.c:141 _do_flock /run/lock/lvm/V_vg1:aux WB #locking/file_locking.c:141 _do_flock /run/lock/lvm/V_vg1 WB #locking/file_locking.c:51 _undo_flock /run/lock/lvm/V_vg1:aux #device/dev-cache.c:333 /dev/xvda1: Added to device cache #device/dev-cache.c:330 /dev/disk/by-path/xen-vbd-2049: Aliased to /dev/xvda1 in device cache #device/dev-cache.c:330 /dev/disk/by-uuid/f4f6befc-d80d-4017-a127-ebe1f0380ee4: Aliased to /dev/xvda1 in device cache #device/dev-cache.c:330 /dev/root: Aliased to /dev/xvda1 in device cache (preferred name) #device/dev-cache.c:333 /dev/xvdb: Added to device cache #device/dev-cache.c:330 /dev/disk/by-path/xen-vbd-2064: Aliased to /dev/xvdb in device cache #device/dev-cache.c:333 /dev/disk/by-uuid/33fe7093-3561-4890-872d-abcb59b3880f: Added to device cache #device/dev-cache.c:333 /dev/xvdb1: Added to device cache #device/dev-cache.c:330 /dev/disk/by-path/xen-vbd-2064-part1: Aliased to /dev/xvdb1 in device cache #device/dev-cache.c:330 /dev/disk/by-uuid/1718f7fb-0a10-4270-93fc-8b75ad8ed73c: Aliased to /dev/xvdb1 in device cache #device/dev-cache.c:330 /dev/xvdb2: Aliased to /dev/disk/by-uuid/33fe7093-3561-4890-872d-abcb59b3880f in device cache (preferred name) #device/dev-cache.c:330 /dev/disk/by-path/xen-vbd-2064-part2: Aliased to /dev/xvdb2 in device cache #device/dev-cache.c:319 /dev/disk/by-uuid/33fe7093-3561-4890-872d-abcb59b3880f: Already in device cache #device/dev-cache.c:333 /dev/xvdh: Added to device cache #device/dev-cache.c:330 /dev/disk/by-path/xen-vbd-2160: Aliased to /dev/xvdh in device cache #device/dev-cache.c:333 /dev/xvdi: Added to device cache #device/dev-cache.c:330 /dev/disk/by-path/xen-vbd-2176: Aliased to /dev/xvdi in device cache #device/dev-cache.c:333 /dev/dm-0: Added to device cache #device/dev-cache.c:330 /dev/disk/by-id/dm-name-vg1-mongodb: Aliased to /dev/dm-0 in device cache (preferred name) #device/dev-cache.c:330 /dev/disk/by-id/dm-uuid-LVM-2A7z5mvNLamjsuxAaIuoAdACm80Pc9N4i9yDRh3s1Ji9mXPW23sygzymjCFzExst: Aliased to /dev/disk/by-id/dm-name-vg1-mongodb in device cache #device/dev-cache.c:330 /dev/disk/by-uuid/72165f22-3863-45fa-a5f3-df5b767f: Aliased to /dev/disk/by-id/dm-name-vg1-mongodb in device cache #device/dev-cache.c:330 /dev/mapper/vg1-mongodb: Aliased to /dev/disk/by-id/dm-name-vg1-mongodb in device cache (preferred name) #device/dev-cache.c:330 /dev/vg1/mongodb: Aliased to /dev/mapper/vg1-mongodb in device cache (preferred name) #device/dev-cache.c:333 /dev/dm-1: Added to device cache #device/dev-cache.c:330 /dev/disk/by-id/dm-name-vg1-backup: Aliased to /dev/dm-1 in device cache (preferred name) #device/dev-cache.c:330 /dev/disk/by-id/dm-uuid-LVM-2A7z5mvNLamjsuxAaIuoAdACm80Pc9N4jnTar3pJic4fN9jtLGEoR0SQw117iwHU: Aliased to /dev/disk/by-id/dm-name-vg1-backup in device cache #device/dev-cache.c:319 /dev/disk/by-uuid/72165f22-3863-45fa-a5f3-df5b767f: Already in device cache #device/dev-cache.c:330 /dev/mapper/vg1-backup: Aliased to /dev/disk/by-id/dm-name-vg1-backup in device cache (preferred name) #device/dev-cache.c:330 /dev/vg1/backup: Aliased to /dev/mapper/vg1-backup in device cache (preferred name) #device/dev-cache.c:333 /dev/dm-2: Added to device cache #device/dev-cache.c:330 /dev/mapper/vg1-mongodb-real: Aliased to /dev/dm-2 in device cache (preferred name) #device/dev-cache.c:333 /dev/dm-3: Added to device cache #device/dev-cache.c:330 /dev/mapper/vg1-backup-cow: Aliased to /dev/dm-3 in device cache (preferred name) #ioctl/libdm-iface.c:1687 dm status (253:0) OF [16384] (*1) #device/dev-io.c:524 Opened /dev/vg1/mongodb RO O_DIRECT #device/dev-io.c:271 /dev/vg1/mongodb: size is 1046478848 sectors
Bug#692819: Also affects xfce4-terminal
reassign 692819 libvte9 found 692819 = 0.28.2-5 retitle 692819 sends ^_ to the session when Ctrl-- is pressed tags 692819 + upstream kthxbye I found the same bug in XFCE4-Terminal, so I think the bug isn't in Gnome-Terminal but in libvte because both terminals use it. Cheers, Eike -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#478735: Bug #478735 - fully support 512-byte sector size
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 I believe parted has had full support for non 512 byte sectors for some time now. Is there a reason this bug report should not be closed? -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.17 (MingW32) Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iQEcBAEBAgAGBQJQ9XZqAAoJEJrBOlT6nu75MJMIAIk+OGI9BajYq7DNqlgEbY3l cwffUJR67JRV5LbZ+a23ZR7kqii6q2h11kXBH16SblZV/1trbKWhtwTqrd0F2fo+ GHKnGBabjgKj07oPi6QMbFqu61agW+E+of2Xp+2F5htcc2WJSNz6khxkeH2hpA+Y s0zJEM65eeDvfCJmNzqp68MXspdUAjrOM5q8AFWX+1ng7T1tSYCTyOegcvxNhLUl looAAIbecfukzuWK26gml31cMthB0FO6i7AzOymHKsV7m6JglUqUqw9bUerFlSL7 HScbYKZn5dD+N9w2K3cxiek1wbtn1tupPyect/TBGZeJapL0gjKpaLhsiOxNwi0= =ncKP -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#698229: [Intel 965G] GPU Hangs (possibly bug #608782 duplicate)
Package: xserver-xorg-video-intel Version: 2:2.20.14-1 In X (I'm using Openbox with no DM), the mouse pointer suddenly freezes. The mouse seems to actually be moving (buttons highlight when rolled over), but the pointer is frozen in one spot. The system is still usable via keyboard, however, if I try to switch to any TTY, it freezes completely. The same happens if I try to kill X via CTRL+ALT+BACKSPACE or kill the X-process. The X.org-log says that the GPU hangs I'm not able to tell what triggers this hang, it appears to happen randomly from normal use of the GUI. I'm using LinuxBBQ (Debian Unstable), with xserver-xorg-video-intel package from Experimental. I had the same problem with the package in Unstable. The problem may have been more frequent in the Unstable version. I'll paste the Xorg-log. If there's anything else I should attach, let me know. [58.039] X.Org X Server 1.12.4 Release Date: 2012-08-27 [58.039] X Protocol Version 11, Revision 0 [58.039] Build Operating System: Linux 3.2.0-4.drm-amd64 x86_64 Debian [58.039] Current Operating System: Linux lynet 3.7-2.towo-siduction-amd64 #1 SMP PREEMPT Sat Jan 12 13:52:15 UTC 2013 x86_64 [58.040] Kernel command line: BOOT_IMAGE=/boot/vmlinuz-3.7-2.towo-siduction-amd64 root=UUID=fca240e0-3568-42c6-8a59-0c1e4c01bec1 ro quiet init=/bin/systemd [58.040] Build Date: 29 November 2012 07:18:16PM [58.040] xorg-server 2:1.12.4-4 (Julien Cristau jcris...@debian.org) [58.040] Current version of pixman: 0.26.0 [58.040]Before reporting problems, check http://wiki.x.org to make sure that you have the latest version. [58.040] Markers: (--) probed, (**) from config file, (==) default setting, (++) from command line, (!!) notice, (II) informational, (WW) warning, (EE) error, (NI) not implemented, (??) unknown. [58.040] (==) Log file: /var/log/Xorg.0.log, Time: Tue Jan 15 15:22:37 2013 [58.078] (==) Using system config directory /usr/share/X11/xorg.conf.d [58.085] (==) No Layout section. Using the first Screen section. [58.085] (==) No screen section available. Using defaults. [58.086] (**) |--Screen Default Screen Section (0) [58.086] (**) | |--Monitor default monitor [58.086] (==) No monitor specified for screen Default Screen Section. Using a default monitor configuration. [58.086] (==) Automatically adding devices [58.086] (==) Automatically enabling devices [58.151] (WW) The directory /usr/share/fonts/X11/cyrillic does not exist. [58.151]Entry deleted from font path. [58.164] (WW) The directory /var/lib/defoma/x-ttcidfont-conf.d/dirs/TrueType does not exist. [58.164]Entry deleted from font path. [58.164] (==) FontPath set to: /usr/share/fonts/X11/misc, /usr/share/fonts/X11/100dpi/:unscaled, /usr/share/fonts/X11/75dpi/:unscaled, /usr/share/fonts/X11/Type1, /usr/share/fonts/X11/100dpi, /usr/share/fonts/X11/75dpi, built-ins [58.164] (==) ModulePath set to /usr/lib/xorg/modules [58.164] (II) The server relies on udev to provide the list of input devices. If no devices become available, reconfigure udev or disable AutoAddDevices. [58.164] (II) Loader magic: 0x7f5b633e4ae0 [58.164] (II) Module ABI versions: [58.164]X.Org ANSI C Emulation: 0.4 [58.164]X.Org Video Driver: 12.1 [58.164]X.Org XInput driver : 16.0 [58.164]X.Org Server Extension : 6.0 [58.165] (--) PCI:*(0:0:2:0) 8086:29a2:a0a0:062a rev 2, Mem @ 0xfd80/1048576, 0xd000/268435456, I/O @ 0xff00/8 [58.165] (II) Open ACPI successful (/var/run/acpid.socket) [58.165] (II) LoadModule: extmod [58.211] (II) Loading /usr/lib/xorg/modules/extensions/libextmod.so [58.226] (II) Module extmod: vendor=X.Org Foundation [58.226]compiled for 1.12.4, module version = 1.0.0 [58.226]Module class: X.Org Server Extension [58.226]ABI class: X.Org Server Extension, version 6.0 [58.226] (II) Loading extension SELinux [58.226] (II) Loading extension MIT-SCREEN-SAVER [58.226] (II) Loading extension XFree86-VidModeExtension [58.226] (II) Loading extension XFree86-DGA [58.226] (II) Loading extension DPMS [58.226] (II) Loading extension XVideo [58.226] (II) Loading extension XVideo-MotionCompensation [58.226] (II) Loading extension X-Resource [58.226] (II) LoadModule: dbe [58.226] (II) Loading /usr/lib/xorg/modules/extensions/libdbe.so [58.227] (II) Module dbe: vendor=X.Org Foundation [58.227]compiled for 1.12.4, module version = 1.0.0 [58.227]Module class: X.Org Server Extension [58.227]ABI class: X.Org Server Extension, version 6.0 [58.227] (II) Loading extension DOUBLE-BUFFER [58.227] (II) LoadModule: glx [58.227] (II) Loading /usr/lib/xorg/modules/extensions/libglx.so [58.234] (II) Module glx: vendor=X.Org Foundation [58.234]compiled
Bug#695985: gwibber-service: dbus starts multiple instances of gwibber because of poor service configuration
Sorry for taking this long to come back to the patch. Today I proted the changes to 3.5.2 in experimental but I still didn't figure out all build dependecies for 3.6.0. I quickly tested the interface. I also checked that only single service is started even if I remove the racy check from service starter. That means patch should be complete fix for 3.5.2. I will make an untested patch for maste so we can see upstream comments too. Porting seems to be relatively simple operations what I have looked the diff. On Fri, Dec 21, 2012 at 6:32 PM, Pauli Nieminen suok...@gmail.com wrote: On Mon, Dec 17, 2012 at 11:58 AM, Kartik Mistry kartik.mis...@gmail.comwrote: On Sat, Dec 15, 2012 at 2:39 PM, Pauli suok...@gmail.com wrote: I noticed that sometimes gwibber generates multiple notifications for a single update. I quickly figured out that issue was dbus starting multiple gwibber-service instances because a race condition in service startup. When I looked around I saw some Ubuntu bug report having similar issues with their indicator. I don't know if there is any more issues that are caused by the race condition. I have made a proposed fix to gwibber code and dbu service configuration to avoid the race condition in startup. The fix is simple refactoring dbus interface to be under single service name that allows dbus to provide atomic single service startup functionality for gwibber-service. I checked upstream code that same bug still exists in the latest development version. But I could easily compile the latest version in Sid so I decided to first cook a patch for the debian package. I will today forward port my changes for upstream inclusion. Attached patch will require also changes to packaging because it reduces .service files to only two. Thanks a lot. Can you redo patch against experimental package of Gwibber? We really need to re-work on package as it has more dependencies which are not in Debian yet. I will do that after Christmas. I didn't have time to figure out the build dependencies when I tried to build gwibber from upstream. I also opened upstream bug if someone there would like to forward port changes before I have time to figure out how to get required dependencies. https://bugs.launchpad.net/gwibber/+bug/1090670 fix-for-3.5.2.diff Description: Binary data
Bug#698108: java-package: diff for NMU version 0.50+nmu2
On 01/14/2013 11:48 PM, Niels Thykier wrote: On 2013-01-15 00:57, David Prévot wrote: tags 698108 + patch thanks Dear maintainer, I've prepared an NMU for java-package (versioned as 0.50+nmu2) and uploaded it to DELAYED/2. Please feel free to tell me if I should delay it longer (or even if I should dcut it to 0-day, given the security matter). If you prefer to fix it in another not intrusive way (not c1fb4d0), I'm happy to (quickly) sponsor your package too. Regards. David [...] Seems to me your patch will prevent anyone from using java-package on the older Java7 binaries. If we do remove this support because they are infested with security issues making them unsuitable for anything at all[1], I think it should have a nice little error message saying Nope, won't do this - That version is vulnerable/unsupported/$whatever. Just so people are aware it is a deliberate choice from our side and not a buggy script crashing. (Particularly people have been using it with older versions before. They might be surprised to see that non-descriptive error message the reporter included in the original mail). I had the same thought - there may be a valid reason for someone to want to run jdk-7u9. This issue already appears to be addressed in the 0.51 package (but with a different patch). I'm assuming we want to keep the patch minimal - can we use this these patterns instead? jdk-7u+([0-9])-linux-i586.tar.gz jdk-7u+([0-9])-linux-x64.tar.gz David, if you'd prefer not to upload again, could you remove the upload and I'll prepare the update. (But thank you for taking the initiative in the first place!) Thank you, tony signature.asc Description: OpenPGP digital signature
Bug#698215: linux-image-3.2.0-4-amd64: Grub fails loading with cannot read the linux header
On Tue, Jan 15, 2013 at 03:40:49PM +0100, Christopher Huhn wrote: Unfortunately this means that I may have to update grub with each release (or kernel?) upgrade on a couple of servers (~ 1000), automatically choosing the proper boot device, By default, grub-pc auto-reinstalls itself. Perhaps it's installing to the wrong place; use 'dpkg-reconfigure grub-pc' to change that. which is normally handled for me by FAI at install time and may be cumbersome eg. for software RAIDs. It's entirely possible that FAI fails to tell the grub-pc packaging where to install GRUB in future. -- Colin Watson [cjwat...@debian.org] -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#698215: linux-image-3.2.0-4-amd64: Grub fails loading with cannot read the linux header
Unfortunately this means that I may have to update grub with each release (or kernel?) upgrade on a couple of servers (~ 1000), automatically choosing the proper boot device, which is normally handled for me by FAI at install time and may be cumbersome eg. for software RAIDs. This should be remembered by debconf (grub-pc/install_devices variable). I'm not sure whether there's a good way to get that information outside of a package maintainer script, though. 'debconf-get-selections | grep grub-pc/install_devices' ? Unfortunately this is not/set used by FAI, at least not by the scripts we use which may not be up to date. Please close this bug. Sorry for the inconvenience. Well, if this is a widespread problem then I think grub-pc must reinstall when the package is upgraded from a version has this bug. We cannot have upgrades resulting in an unbootable system. Were these systems initially installed with squeeze, or an earlier version? According to the FAI logs this machine has been (re)installed with Squeeze roughly a year ago. The installed grub version was 1.98+20100804-14+squeeze1. I have only observed the problem on this particular box, but I did not do many Wheezy upgrades until now. Cheers, Christopher smime.p7s Description: S/MIME Cryptographic Signature
Bug#698189: swath: Buffer Overflow with console args is possible.
Hi, The Argument will most likely not come from untrusted sources, I guess? So it's no severe risk. Only issue I could think of is that it could be used to escalate permissions of an attacker to swath's user's context. Then again, the system already has to be infiltrated to do that... Regards Dominik Maier Am 15.01.2013 09:26 schrieb Theppitak Karoonboonyanan t...@linux.thai.net : On Tue, Jan 15, 2013 at 6:44 AM, Dominik Maier domen...@gmail.com wrote: Buffer overflow because of strcpy with possibility to inject shellcode: swath mule -b [More than 20 to overflow and possibly inject shellcode.] emptyfile proplematic lines are: char stopstr[20]; if (muleMode) strcpy(stopstr,wbr); Instead, you should change the size of stopstr according to wbr. Even better would be simply to change the address of stopstr like char stopstr[20]; if (muleMode) stopstr = wbr; Thanks for the report. I've applied the fix upstream: http://linux.thai.net/websvn/wsvn/software.swath?op=compcompare[]=%2Ftrunk@237compare[]=%2Ftrunk@238 I'm estimating the risk to decide what to do in Debian. The use of Mule mode is quite rare, IMO. Regards, -- Theppitak Karoonboonyanan http://linux.thai.net/~thep/
Bug#659762: lvremove failure log
On Tue, Jan 15, 2013 at 04:25:18PM +0100, Oskar Liljeblad wrote: After several tries, I managed to reproduce the problem. This time I ran lvremove - -f /dev/vg1/backup, and the output is attached. I hope you can make some sense out of it. #libdm-deptree.c:1547 Unable to deactivate open vg1-backup-cow (253:3) Likely to be a bug in your udev rules. (Does Debian still differ from upstream?) Alasdair -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#698222: git-import-dsc: does not merge already-imported upstream version
On Tue, Jan 15, 2013 at 10:15 AM, Guido Günther wrote: On Tue, Jan 15, 2013 at 08:43:59AM -0500, Mike Miller wrote: I found the following steps do not work: git-import-orig --no-merge ../foo_1.2.orig.tar.gz git-import-dsc ../foo_1.2-1.dsc The resulting debian/1.2-1 commit is a child of only master, it does not properly merge upstream/1.2 at all. [...] It seems that we might want to move the upstream-vcs-tag logic to git-import-dsc then. Makes sense, that would address what I was really trying to do. If there's no other use case for doing separate import-orig followed by import-dsc, feel free to redefine this bug as support git-import-dsc --upstream-vcs-tag. Even better would be to somehow support upstream-vcs-tags with git-import-dscs --debsnap but I'm not sure how you would map multiple versions to tags without an unwieldy interface. * Don't you still want to import the upstream tarball too? Yes, I used --pristine-tar on the import-orig. Escpecially when using git-import-dsc I think we should do: * import upstream tarball with the possibility to have the upstream VCS tag as parent (as with git-import-orig) * proceed from there as usual There wouldn't be any need for using git-import-orig then. Patches are welcome. Sounds good, thanks for the feedback, I'll look at that. -- mike -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#697873: live-boot: Easy fix for broken persistence-label parameter
On Fri, Jan 11, 2013 at 11:04 AM, Mike Gach gach@gmail.com wrote: On Fri, Jan 11, 2013 at 10:52 AM, Daniel Baumann daniel.baum...@progress-technologies.net wrote: ack; would you like to prepare a patch for that, including a note for the manpage? I would be happy to. I will have to do some reading to make sure I understand the right way to make the patch, so I will get to that this weekend. I'm not sure if I did this patch right. It is the output of git diff, but other patches I looked at seem to have some information before the diff --git line. Here is some info for the man page: persistence-label=LABEL live-boot will use the name LABEL instead of persistence when searching for persistent storage. LABEL can be any legal filename, partition label, or GPT name. This option replaces the less flexible persistent-subtext option from v2 of live-boot. If you wish to continue using legacy names for persistent storage, use the full name with this option. For example: persistence-label=live-rw-xyz -- -- M Gach 9990-cmdline-old.patch Description: Binary data
Bug#698215: linux-image-3.2.0-4-amd64: Grub fails loading with cannot read the linux header
On Tue, Jan 15, 2013 at 04:43:51PM +0100, Christopher Huhn wrote: 'debconf-get-selections | grep grub-pc/install_devices' ? Yes. Unfortunately this is not/set used by FAI, at least not by the scripts we use which may not be up to date. In that case this is a dangerous bug in FAI (or your scripts) which needs to be fixed. grub-pc has no practical way to work around this as some people set this situation up intentionally. -- Colin Watson [cjwat...@debian.org] -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#698230: uninitialized variable causes firefox to crash when card is inserted into reader
Package: coolkey Version: 1.1.0-12 Severity: normal Tags: patch User: ubuntu-de...@lists.ubuntu.com Usertags: origin-ubuntu raring ubuntu-patch *** /tmp/tmpbG98u8/bug_body In Ubuntu, the attached patch was applied to achieve the following: * Fix Firefox crash due to Assertion `mOldCAC' failed error based on patch from www.spinics.net/linux/fedora/coolkey/msg00368.html Thanks for considering the patch. -- System Information: Debian Release: wheezy/sid APT prefers precise-updates APT policy: (500, 'precise-updates'), (500, 'precise-security'), (500, 'precise-proposed'), (500, 'precise'), (100, 'precise-backports') Architecture: amd64 (x86_64) Kernel: Linux 3.2.0-36-generic (SMP w/8 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash === modified file 'debian/changelog' === added file 'debian/patches/99-fixmAsserterror.patch' --- debian/patches/99-fixmAsserterror.patch 1970-01-01 00:00:00 + +++ debian/patches/99-fixmAsserterror.patch 2013-01-15 15:34:29 + @@ -0,0 +1,16 @@ +## Description: add some description +## Origin/Author: add some origin or author +## Bug: bug URL +Index: coolkey/src/coolkey/slot.cpp +=== +--- coolkey.orig/src/coolkey/slot.cpp 2013-01-15 10:25:31.690342000 -0500 coolkey/src/coolkey/slot.cpp 2013-01-15 10:34:08.539195695 -0500 +@@ -2215,6 +2215,8 @@ + CKYBuffer_InitEmpty(vBuf); + CKYBuffer_Resize(cert, 0); + ++*nextSize = 0; ++ + /* handle the new CAC card read */ + /* read the TLV */ + status = CACApplet_ReadFile(conn, CAC_TAG_FILE, tBuf, NULL); === modified file 'debian/patches/series' --- debian/patches/series 2012-04-11 20:56:20 + +++ debian/patches/series 2013-01-15 15:32:25 + @@ -8,3 +8,4 @@ coolkey-cac-rhl5.patch 0001-Fix-working-with-empty-certificates-in-not-zero-slot.patch Handle-pcscd-restarting +99-fixmAsserterror.patch
Bug#659762: lvremove failure log
On Tuesday, January 15, 2013 at 15:36, Alasdair G Kergon wrote:
After several tries, I managed to reproduce the problem. This time I ran
lvremove - -f /dev/vg1/backup, and the output is attached. I hope you
can make some sense out of it.
#libdm-deptree.c:1547 Unable to deactivate open vg1-backup-cow (253:3)
Likely to be a bug in your udev rules.
(Does Debian still differ from upstream?)
Do you know which rules?
Are you referring to https://bugzilla.redhat.com/show_bug.cgi?id=570359?
Maybe I'm grasping at straws, but do you think this problem would be fixed
by adding the appropriate udev rules?
I did a quick comparison of Debian's udev rule files and those in lvm2 GIT.
Example:
---
Debian: /lib/udev/rules.d/56-lvm.rules
lvm2: udev/11-dm-lvm.rules
Missing in Debian:
# Do not create symlinks for inappropriate subdevices.
ENV{DM_LV_NAME}==pvmove?*|?*_vorigin, GOTO=lvm_disable
ENV{DM_LV_LAYER}==?*, GOTO=lvm_disable
# Create symlinks for top-level devices only.
ENV{DM_VG_NAME}==?*, ENV{DM_LV_NAME}==?*,
SYMLINK+=$env{DM_VG_NAME}/$env{DM_LV_NAME}, GOTO=lvm_end
---
---
Debian: (none)
lvm2: udev/69-dm-lvm-metad.rules
Missing in Debian:
SUBSYSTEM!=block, GOTO=lvm_end
# Device-mapper devices are processed only on change event or on supported
# synthesized event.
KERNEL==dm-[0-9]*, ENV{DM_UDEV_RULES_VSN}!=?*, GOTO=lvm_end
# Only process devices already marked as a PV - this requires blkid to be
# called before.
ENV{ID_FS_TYPE}==LVM2_member|LVM1_member, RUN+=$env{DM_SBIN_PATH}/pvscan
--cache --major $major --minor $minor
LABEL=lvm_end
---
---
Debian: /lib/udev/rules.d/55-dm.rules
lvm2: udev/10-dm.rules.in
Missing in Debian:
VSN stuff, whatever that is
# Decode udev control flags and set environment variables appropriately.
# These flags are encoded in DM_COOKIE variable that was introduced in
# kernel version 2.6.31. Therefore, we can use this feature with
# kernels = 2.6.31 only. Cookie is not decoded for remove event.
ENV{DM_COOKIE}==?*, IMPORT{program}=$env{DM_SBIN_PATH}/dmsetup udevflags
$env{DM_COOKIE}
---
Regards,
Oskar
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#694778: A little test message to see whether our filters work now
just curious, I'm not related to this RFS, should I still receive this message? 2013/1/15 Arno Töll a...@debian.org Sorry for the hijack of your RFS, I'm testing our new mail filter. Please ignore me :) -- with kind regards, Arno Töll IRC: daemonkeeper on Freenode/OFTC GnuPG Key-ID: 0x9D80F36D
Bug#695985: gwibber-service: dbus starts multiple instances of gwibber because of poor service configuration
The master merge request can be found from https://code.launchpad.net/~paniemin/gwibber/gwibber/+merge/143341
Bug#697728: pdfjam: might be related to document class beamer
Package: pdfjam Version: 2012.20120611-2 Followup-For: Bug #697728 Dear Maintainer, the landscape problem seems to be related to the document class or paper orientation. I always get the orientation the original document had, the previously mentioned document class had been a priunt version of 'beamer' class. -- Package-specific info: IMPORTANT INFORMATION: We will only consider bug reports concerning the packaging of TeX Live as relevant. If you have problems with combination of packages in a LaTeX document, please consult your local TeX User Group, the comp.text.tex user group, the author of the original .sty file, or any other help resource. *** The Debian TeX Team is *no* LaTeX Help Desk *** If you report an error when running one of the TeX-related binaries (latex, pdftex, metafont,...), or if the bug is related to bad or wrong output, please include a MINIMAL example input file that produces the error in your report. Please run your example with (pdf)latex -recorder ... (or any other program that supports -recorder) and send us the generated file with the extension .fls, it lists all the files loaded during the run and can easily explain problems induced by outdated files in your home directory. Don't forget to also include minimal examples of other files that are needed, e.g. bibtex databases. Often it also helps to include the logfile. Please, never send included pictures! If your example file isn't short or produces more than one page of output (except when multiple pages are needed to show the problem), you can probably minimize it further. Instructions on how to do that can be found at http://www.minimalbeispiel.de/mini-en.html (english) or http://www.minimalbeispiel.de/mini.html (german) ## minimal input file ## other files ## List of ls-R files -rw-rw-r-- 1 root root 2061 Jan 14 08:41 /var/lib/texmf/ls-R lrwxrwxrwx 1 root root 29 Jan 9 23:47 /usr/share/texmf/ls-R - /var/lib/texmf/ls-R-TEXMFMAIN lrwxrwxrwx 1 root root 31 Oct 3 14:12 /usr/share/texlive/texmf/ls-R - /var/lib/texmf/ls-R-TEXLIVEMAIN -rw-rw-r-- 1 root staff 80 Oct 26 00:15 /usr/local/share/texmf/ls-R lrwxrwxrwx 1 root root 31 Oct 3 14:12 /usr/share/texlive/texmf-dist/ls-R - /var/lib/texmf/ls-R-TEXLIVEDIST lrwxrwxrwx 1 root root 31 Oct 3 14:12 /usr/share/texlive/texmf-dist/ls-R - /var/lib/texmf/ls-R-TEXLIVEDIST lrwxrwxrwx 1 root root 31 Oct 3 14:12 /usr/share/texlive/texmf/ls-R - /var/lib/texmf/ls-R-TEXLIVEMAIN ## Config files -rw-r--r-- 1 root root 1464 Jan 13 19:46 /etc/texmf/web2c/texmf.cnf -rw-r--r-- 1 root root 5960 Jan 13 19:46 /var/lib/texmf/web2c/fmtutil.cnf lrwxrwxrwx 1 root root 32 Oct 3 14:12 /usr/share/texmf/web2c/updmap.cfg - /var/lib/texmf/updmap.cfg-DEBIAN -rw-r--r-- 1 root root 12150 Jan 13 19:46 /var/lib/texmf/tex/generic/config/language.dat ## Files in /etc/texmf/web2c/ total 8 -rw-r--r-- 1 root root 283 Feb 26 2007 mktex.cnf -rw-r--r-- 1 root root 1464 Jan 13 19:46 texmf.cnf ## md5sums of texmf.d ca40c66f144b4bafc3e59a2dd32ecb9c /etc/texmf/texmf.d/00debian.cnf 055e06548bac99958d8ab2dd1248f2b4 /etc/texmf/texmf.d/80tex4ht.cnf d3ca09064cf089f47ed99a4a091c7485 /etc/texmf/texmf.d/95NonPath.cnf.postinst-bak 1df66bc319cec731e202eaf39f5d85e1 /etc/texmf/texmf.d/96JadeTeX.cnf -- System Information: Debian Release: 7.0 APT prefers testing-updates APT policy: (500, 'testing-updates'), (500, 'testing-proposed-updates'), (500, 'stable-updates'), (500, 'proposed-updates'), (500, 'testing'), (500, 'stable') Architecture: i386 (x86_64) Kernel: Linux 3.2.0-4-amd64 (SMP w/4 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 pdfjam depends on: ii dpkg 1.16.9 ii tex-common 3.15 ii texlive-extra-utils 2012.20120611-2 pdfjam recommends no packages. pdfjam suggests no packages. Versions of packages tex-common depends on: ii debconf [debconf-2.0] 1.5.49 ii dpkg 1.16.9 ii ucf3.0025+nmu3 Versions of packages tex-common suggests: ii debhelper 9.20120909 Versions of packages pdfjam is related to: ii tex-common3.15 ii texlive-binaries 2012.20120628-4 -- debconf information: tex-common/check_texmf_wrong: tex-common/check_texmf_missing: -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#697864: Update virinst via wheezy-proposed-updates
Hi, the tools from virtinst will fail to do anything useful with a bad locale sitting. The patch is simple and cherry-picked from upstream. Would this be a case to be fixed via w-p-u? Sid already has a newer upstream version. Debdiff is attached. Cheers, -- Guido -- System Information: Debian Release: 7.0 APT prefers testing APT policy: (990, 'testing'), (50, 'unstable'), (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/dash diff -Nru virtinst-0.600.1/debian/changelog virtinst-0.600.1/debian/changelog --- virtinst-0.600.1/debian/changelog 2012-04-16 14:24:13.0 +0200 +++ virtinst-0.600.1/debian/changelog 2013-01-15 17:06:42.0 +0100 @@ -1,3 +1,10 @@ +virtinst (0.600.1-3) wheezy-proposed-updates; urgency=low + + * [3723835] Don't fail if we can't set locale (debian bug #697864) +Thanks to Cole Robinson (Closes: #697864) + + -- Guido Günther a...@sigxcpu.org Tue, 15 Jan 2013 17:06:27 +0100 + virtinst (0.600.1-2) unstable; urgency=low * [5e59401] Fix location of Debian daily builds. diff -Nru virtinst-0.600.1/debian/patches/0005-Don-t-fail-if-we-can-t-set-locale-debian-bug-697864.patch virtinst-0.600.1/debian/patches/0005-Don-t-fail-if-we-can-t-set-locale-debian-bug-697864.patch --- virtinst-0.600.1/debian/patches/0005-Don-t-fail-if-we-can-t-set-locale-debian-bug-697864.patch 1970-01-01 01:00:00.0 +0100 +++ virtinst-0.600.1/debian/patches/0005-Don-t-fail-if-we-can-t-set-locale-debian-bug-697864.patch 2013-01-15 16:20:37.0 +0100 @@ -0,0 +1,27 @@ +From: Cole Robinson crobi...@redhat.com +Date: Mon, 14 Jan 2013 15:06:14 -0500 +Subject: Don't fail if we can't set locale (debian bug #697864) + +--- + virtinst/cli.py |8 +++- + 1 file changed, 7 insertions(+), 1 deletion(-) + +diff --git a/virtinst/cli.py b/virtinst/cli.py +index 80e1fcf..e739b12 100644 +--- a/virtinst/cli.py b/virtinst/cli.py +@@ -144,7 +144,13 @@ def setupParser(usage=None): + return parser + + def setupGettext(): +-locale.setlocale(locale.LC_ALL, '') ++try: ++locale.setlocale(locale.LC_ALL, '') ++except locale.Error, e: ++print sys.stderr, warning: failed to set locale, defaulting to C ++os.environ['LC_ALL'] = 'C' ++locale.setlocale(locale.LC_ALL, 'C') ++ + gettext.bindtextdomain(virtinst) + gettext.install(virtinst) + diff -Nru virtinst-0.600.1/debian/patches/series virtinst-0.600.1/debian/patches/series --- virtinst-0.600.1/debian/patches/series 2012-04-16 14:23:13.0 +0200 +++ virtinst-0.600.1/debian/patches/series 2013-01-15 16:20:37.0 +0100 @@ -2,3 +2,4 @@ 0002-Fix-path-to-pygrub.patch 0003-Fix-path-to-keyboard-configuration.patch 0004-Fix-location-of-Debian-daily-builds.patch +0005-Don-t-fail-if-we-can-t-set-locale-debian-bug-697864.patch
