Bug#688766: kde4libs: Please get your package rebuilt to gain xz compression
Package: kde4libs Version: 4:4.8.4-3 Severity: important Tags: d-i patch Hi, trying to make KDE fit on KDE CD#1, this package would be nice to get rebuilt to gain xz compression. Especially for that part: 2.6M /home/ftpmirror/mirrors/debian/pool/main/k/kde4libs/libkhtml5_4.8.4-3_amd64.deb 1.9M../libkhtml5_4.8.4-3_amd64.deb Thanks for considering. Mraw, KiBi. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#688757: pvmove onto disk with different sector size hazardous
On Tuesday 25 September 2012 06:15 PM, Daniel Pocock wrote: Package: lvm2 Version: 2.02.95-4 Severity: severe I have marked this `severe' because it has a high probability of filesystem corruption and drives with 4096 byte sectors are likely to become much more widespread. I recently purchased a 3TB drive and created one big 3TB partition for lvm I then used pvmove to move some filesystems from my internal drive to the external drive. As a test run, I was just moving filesystems that were mounted but with no open files. Many errors appeared during the pvmove operation I unmounted them all and did an fsck on all of them and they are all clean. Mounting them again, some fail to mount, this error is in dmesg: error: fsblocksize 1024 too small for hardware sectorsize 4096 The old disk has 512 byte sectors and the new disk has 4096 byte sectors. Please wait for the actual response from the maintainer (Bastian). I just was curious and wanted to ask. Irrespective of what the physical block sizes are, currently still the logical block sizes are reported 512 bytes. Right? In that case, I am not sure why your file system is bailing out. -- Ritesh Raj Sarraf | http://people.debian.org/~rrs Debian - The Universal Operating System signature.asc Description: OpenPGP digital signature
Bug#688767: systemsettings: Crash in Display and Monitor
Package: systemsettings Version: 4:4.8.4-3 Severity: important 1. Edit your System Settings menu item: select run as different user 2. Start up System Settings, it prompts for root password, enter it. 3. Click on Display and Monitor 4. In the window that pops up, click on Gamma on the left. 5. Segfaults Application: System Settings (systemsettings), signal: Segmentation fault Using host libthread_db library /lib/i386-linux- gnu/i686/cmov/libthread_db.so.1. [KCrash Handler] #7 0xb6cd91d7 in QAbstractButton::isChecked (this=0x9ec9948) at widgets/qabstractbutton.cpp:774 #8 0xb131913c in ?? () from /usr/lib/kde4/kcm_kgamma.so #9 0xb74fba07 in qt_static_metacall (_a=0x9ee3cc0, _id=3, _o=0x9ecb630, _c=optimized out) at ./kcmodule.moc:66 #10 KCModule::qt_static_metacall (_o=0x9ecb630, _c=QMetaObject::InvokeMetaMethod, _id=3, _a=0x9ee3cc0) at ./kcmodule.moc:57 #11 0xb62b778a in QMetaCallEvent::placeMetaCall (this=0x9f13768, object=0x9ecb630) at kernel/qobject.cpp:525 #12 0xb62bbccb in QObject::event (this=0x9ecb630, e=0x9f13768) at kernel/qobject.cpp:1195 #13 0xb69134da in QWidget::event (this=0x9ecb630, event=0x9f13768) at kernel/qwidget.cpp:8830 #14 0xb68ba47c in QApplicationPrivate::notify_helper (this=0x99a3898, receiver=0x9ecb630, e=0x9f13768) at kernel/qapplication.cpp:4556 #15 0xb68bef24 in QApplication::notify (this=0x99a3898, receiver=0x9ecb630, e=0x9f13768) at kernel/qapplication.cpp:4417 #16 0xb7455581 in KApplication::notify (this=0xbff72a9c, receiver=0x9ecb630, event=0x9f13768) at ../../kdeui/kernel/kapplication.cpp:311 #17 0xb62a555e in QCoreApplication::notifyInternal (this=0xbff72a9c, receiver=0x9ecb630, event=0x9f13768) at kernel/qcoreapplication.cpp:915 #18 0xb62a976d in sendEvent (event=optimized out, receiver=optimized out) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:231 #19 QCoreApplicationPrivate::sendPostedEvents (receiver=0x0, event_type=0, data=0x9975c18) at kernel/qcoreapplication.cpp:1539 #20 0xb62a99ec in QCoreApplication::sendPostedEvents (receiver=0x0, event_type=0) at kernel/qcoreapplication.cpp:1432 #21 0xb62d76c4 in sendPostedEvents () at .../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:236 #22 postEventSourceDispatch (s=0x9991d30) at kernel/qeventdispatcher_glib.cpp:279 #23 0xb56d6633 in g_main_context_dispatch () from /lib/i386-linux- gnu/libglib-2.0.so.0 #24 0xb56d69d0 in ?? () from /lib/i386-linux-gnu/libglib-2.0.so.0 #25 0xb56d6ab1 in g_main_context_iteration () from /lib/i386-linux- gnu/libglib-2.0.so.0 #26 0xb62d7841 in QEventDispatcherGlib::processEvents (this=0x9976780, flags=...) at kernel/qeventdispatcher_glib.cpp:424 #27 0xb696d1fa in QGuiEventDispatcherGlib::processEvents (this=0x9976780, flags=...) at kernel/qguieventdispatcher_glib.cpp:204 #28 0xb62a402c in QEventLoop::processEvents (this=this@entry=0xbff729c8, flags=...) at kernel/qeventloop.cpp:149 #29 0xb62a4321 in QEventLoop::exec (this=0xbff729c8, flags=...) at kernel/qeventloop.cpp:204 #30 0xb62a9a9a in QCoreApplication::exec () at kernel/qcoreapplication.cpp:1187 #31 0xb68b82f4 in QApplication::exec () at kernel/qapplication.cpp:3817 #32 0x08050d32 in main (argc=5, argv=0xbff72b84) at .../../../systemsettings/app/main.cpp:49 -- System Information: Debian Release: wheezy/sid APT prefers testing APT policy: (500, 'testing') Architecture: i386 (i686) Kernel: Linux 3.2.0-3-686-pae (SMP w/1 CPU core) 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 systemsettings depends on: ii kde-runtime 4:4.8.4-1 ii libc62.13-35 ii libfontconfig1 2.9.0-7 ii libkcmutils4 4:4.8.4-3 ii libkdecore5 4:4.8.4-3 ii libkdeui54:4.8.4-3 ii libkhtml54:4.8.4-3 ii libkio5 4:4.8.4-3 ii libknewstuff3-4 4:4.8.4-3 ii libqt4-dbus 4:4.8.2+dfsg-2 ii libqt4-xml 4:4.8.2+dfsg-2 ii libqtcore4 4:4.8.2+dfsg-2 ii libqtgui44:4.8.2+dfsg-2 ii libstdc++6 4.7.1-7 ii libx11-6 2:1.5.0-1 systemsettings recommends no packages. systemsettings 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#636554: jruby: New upstream release
On 25/09/12 13:31, berta...@ptitcanardnoir.org wrote: On Wed, Aug 3, 2011 at 2:09 PM, James Healyji...@deefa.com wrote: JRuby 1.6.3 is available upstream and includes official support for ruby 1.9 syntax. Are there any plans to package 1.6.x? yes, but every helping hand is welcome! Is there a place where this plans are documented? What are they? I might be interested to help. I've already started a bit, but don't know java that much and hit some symbols not found errors at compilation time. The work was done to repackage jruby-1.6.7.2 in June: http://lists.alioth.debian.org/pipermail/pkg-java-maintainers/2012-June/039090.html It had no response. I presume that's because it re-ships the jars it requires rather than depending on existing Debian packages where they're available. If I were to suggest a starting point, it would be to get its dependencies up to date. -- Alex -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#677741: ia32-libs wheezy progress
Hi, the multiarchified libcap2 just transitioned to wheezy, so all blocking bugs of #677741 that were in other packages are fixed. Time to get ia32-libs ready for wheezy? Best regards, Tobias -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#688768: RFS: glipper/2.4-1
Package: sponsorship-requests Severity: normal Dear mentors, I am looking for a sponsor for my package glipper * Package name: glipper Version : 2.4-1 Upstream Author : Laszlo Pandy laszl...@gmail.com * URL : http://launchpad.net/glipper * License : GPL-2+ Section : utils It builds those binary packages: glipper- Clipboard manager for GNOME To access further information about this package, please visit the following URL: http://mentors.debian.net/package/glipper Alternatively, one can download the package with dget using this command: dget -x http://mentors.debian.net/debian/pool/main/g/glipper/glipper_2.4-1.dsc Changes since the last upload: * New upstream release. (LP: #936650) * Removed debian/patches directory. The patch is applied upstream. Regards, José Ernesto Dávila Pantoja http://people.ubuntu.com/~josernestodavila/gpg_key_transition.txt.asc -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#688053: Package version
Tzafrir, Thanks for your efforts on this and in maintaining the packages in general. Am I to understand from the bug report log (No longer found in squeeze7) that a new version of the package was uploaded with the same version number as the broken one (can't see a squeeze8 in the repo)? Two things if so: 1) The timestamps of the squeeze7 packages on s.d.o still appear to be the ones originally published on the 18th September? 2) Would it not be wiser to go to squeeze8 to avoid significant potential for confusion? (or is there some sort of Debian versioning policy I am unaware of relating to broken updates?) -- Regards, Phillip Baker
Bug#687970: narrowing
asterisk and dahdi-tools from wheezy work with Linux and modules from dahdi-source in squeeze. When the DoorBell Fon is activated, the RED alarm clears and Asterisk is aware of the ringing. With the wheezy kernel/modules, the RED alarm never clears. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#688711: Confirmed
I can confirm this bug on one of my machines. Another system using LVM, does not show this problem though. Running vgchange -a y in the initramfs shell makes them active and then boot can continue without problem. -- Frederik Himpe fhi...@telenet.be -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#687492: unblock: aptitude/0.6.8.2-1 (pre-approve)
Daniel Hartwig mand...@gmail.com (25/09/2012): I did aim to keep the changes in .8.2 minimal to facilitate a speedy approval for the xz and translation updates. I have no upload priv., so here: http://mentors.debian.net/debian/pool/main/a/aptitude/aptitude_0.6.8.1-2.dsc I leave it to you to sponsor and make a separate unblock request for that version. Alright, thanks. Building, uploading, and requesting. Mraw, KiBi. signature.asc Description: Digital signature
Bug#628509: patch
Here's a trivial patch to fix mysqli_real_connect ignoring flags. I'm not really sure what the proper procedure for submitting patches for git-managed debian packages is, but I hope github is okay for you: https://github.com/vanviegen/pkg-php.git I would really appreciate it if someone could apply this, as we rely on this functionality, and having to do source installs with every update is little fun. Thanks! Frank van Viegen www.paiq.nl fr...@paiq.nl -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#688769: unblock: mysql-5.5/5.5.24+dfsg-9
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: unblock
Please unblock package mysql-5.5
Debconf translations, fix for unreproducible upgrade issue, fix for ensuring we
use system zlib.
unblock mysql-5.5/5.5.24+dfsg-9
-- System Information:
Debian Release: wheezy/sid
APT prefers unstable
APT policy: (500, 'unstable')
Architecture: i386 (i686)
Kernel: Linux 3.2.0-1-686-pae (SMP w/1 CPU core)
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
diff -Nru mysql-5.5-5.5.24+dfsg/debian/changelog mysql-5.5-5.5.24+dfsg/debian/changelog
--- mysql-5.5-5.5.24+dfsg/debian/changelog 2012-09-04 06:56:28.0 +0100
+++ mysql-5.5-5.5.24+dfsg/debian/changelog 2012-09-22 15:01:34.0 +0100
@@ -1,3 +1,14 @@
+mysql-5.5 (5.5.24+dfsg-9) unstable; urgency=low
+
+ * Danish debconf translation (Closes: #684566)
+ * Turkish debconf translation (Closes: #688294)
+ * Loosened versioned dependency between mysql-server-5.5 and
+mysql-server-core-5.5, hopefully (Closes: #686803)
+ * Restored zlib1g-dev (= 1:1.1.3-5) as a build dependency
+and made the use of system libz explicit in debian/rules
+
+ -- Nicholas Bamber nicho...@periapt.co.uk Sat, 22 Sep 2012 15:01:11 +0100
+
mysql-5.5 (5.5.24+dfsg-8) unstable; urgency=low
* Updated debian/copyright after analysis from development version
diff -Nru mysql-5.5-5.5.24+dfsg/debian/control mysql-5.5-5.5.24+dfsg/debian/control
--- mysql-5.5-5.5.24+dfsg/debian/control 2012-07-17 15:17:33.0 +0100
+++ mysql-5.5-5.5.24+dfsg/debian/control 2012-09-16 09:36:05.0 +0100
@@ -4,7 +4,7 @@
Maintainer: Debian MySQL Maintainers pkg-mysql-ma...@lists.alioth.debian.org
Uploaders: Norbert Tretkowski norb...@tretkowski.de,
Clint Byrum cl...@ubuntu.com, Nicholas Bamber nicho...@periapt.co.uk
-Build-Depends: debhelper (= 8.1.3~), libaio-dev[linux-any], libncurses5-dev (= 5.0-6), perl, libwrap0-dev (= 7.6-8.3), libreadline-dev, po-debconf, psmisc, chrpath, doxygen-latex, ghostscript, gawk, bison, lsb-release, hardening-wrapper, cmake, gcc-4.4 [any-i386], g++-4.4 [any-i386]
+Build-Depends: debhelper (= 8.1.3~), libaio-dev[linux-any], libncurses5-dev (= 5.0-6), perl, libwrap0-dev (= 7.6-8.3), zlib1g-dev (= 1:1.1.3-5), libreadline-dev, po-debconf, psmisc, chrpath, doxygen-latex, ghostscript, gawk, bison, lsb-release, hardening-wrapper, cmake, gcc-4.4 [any-i386], g++-4.4 [any-i386]
Standards-Version: 3.9.3
Homepage: http://dev.mysql.com/
Vcs-Browser: http://svn.debian.org/wsvn/pkg-mysql/mysql-5.5/
@@ -51,7 +51,7 @@
Package: libmysqlclient-dev
Architecture: any
Section: libdevel
-Depends: libmysqlclient18 (= ${binary:Version}), zlib1g-dev, , ${shlibs:Depends}, ${misc:Depends}
+Depends: libmysqlclient18 (= ${binary:Version}), zlib1g-dev, ${shlibs:Depends}, ${misc:Depends}
Conflicts: libmysqlclient14-dev, libmysqlclient12-dev, libmysqlclient10-dev, libmysqlclient15-dev
Provides: libmysqlclient15-dev
Replaces: libmysqlclient15-dev
@@ -113,7 +113,7 @@
Suggests: tinyca
Recommends: mailx, libhtml-template-perl
Pre-Depends: mysql-common (= ${source:Version}), adduser (= 3.40), debconf
-Depends: mysql-client-5.5 (= ${source:Version}), libdbi-perl, perl (= 5.6), ${shlibs:Depends}, ${misc:Depends}, psmisc, passwd, lsb-base (= 3.0-10), mysql-server-core-5.5 (= ${binary:Version}), initscripts (= 2.88dsf-13.3)
+Depends: mysql-client-5.5 (= ${source:Version}), libdbi-perl, perl (= 5.6), ${shlibs:Depends}, ${misc:Depends}, psmisc, passwd, lsb-base (= 3.0-10), mysql-server-core-5.5 (= ${source:Version}), initscripts (= 2.88dsf-13.3)
Breaks: mysql-server ( ${source:Version}), mysql-server-5.1, libmysqlclient-dev ( 5.5.17~), mysql-client-5.1
Provides: virtual-mysql-server
Replaces: mysql-server ( ${source:Version}), mysql-server-5.1, mysql-server-5.0, , mysql-client-5.1,
diff -Nru mysql-5.5-5.5.24+dfsg/debian/po/da.po mysql-5.5-5.5.24+dfsg/debian/po/da.po
--- mysql-5.5-5.5.24+dfsg/debian/po/da.po 2012-09-02 18:03:59.0 +0100
+++ mysql-5.5-5.5.24+dfsg/debian/po/da.po 2012-09-09 09:37:09.0 +0100
@@ -1,15 +1,15 @@
-# Danish translation mysql-5.1.
-# Copyright (C) 2010 mysql-5.1 nedenstående oversættere.
-# This file is distributed under the same license as the mysql-5.1 package.
+# Danish translation mysql-5.5.
+# Copyright (C) 2010 mysql-5.5 nedenstående oversættere.
+# This file is distributed under the same license as the mysql-5.5 package.
# Claus Hindsgaul clau...@image.dk 2005, 2006, 2007.
-# Joe Hansen joedalt...@yahoo.dk, 2010.
+# Joe Hansen joedalt...@yahoo.dk, 2010, 2012.
#
msgid
msgstr
-Project-Id-Version: mysql-5.1\n
+Project-Id-Version: mysql-5.5\n
Report-Msgid-Bugs-To: mysql-...@packages.debian.org\n
POT-Creation-Date: 2011-11-08 11:42-0800\n
-PO-Revision-Date: 2010-10-07 05:26+0100\n
+PO-Revision-Date: 2012-08-11 05:26+0100\n
Last-Translator: Joe Hansen joedalt...@yahoo.dk\n
Language-Team: Danish
Bug#685817: viking crashes a lot when used to display maps
Hi Rob, thank you for the hint to disable the status bar. It seems to improve the stability a lot, although it does not prevent viking completely from crashing. But that's maybe because I have to switch on the status bar from time to time to check coordinates. Regards, Uwe -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#687506: libgl1-nvidia-glx-ia32: Package has unfulfillable recommends
Hi, I just found out how ia32-libs does the multiarch migration trick, and probably that's what this package should do as well: * libgl1-nvidia-glx-ia32:amd64 should depend on libgl1-nvidia-glx-i386 * libgl1-nvidia-glx-i386 exists only for i386 and is MA: foreign, so it satisfies the dependency of libgl1-nvidia-glx-ia32 * libgl1-nvidia-glx-i386:i386 depends on libgl1-nvidia-glx, which will implicitly be libgl1-nvidia-glx:i386. Then installing libgl1-nvidia-glx-ia32 will automatically install libgl1-nvidia-glx-i386:i386 if the i386 packages are present (and will fail otherwise). Kind regards, Ralf -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#688598: [Pkg-xfce-devel] Bug#688598: xfce4-power-manager: Notification icon actions are not configurable
El 25/09/12 15:33, Yves-Alexis Perez escribió: On mar., 2012-09-25 at 15:21 +0200, José Salavert Torres wrote: 1) There are two scripts to suspend from console: pm-suspend and pm-suspend-hybrid , both in package pm-utils. When I suspend using xfpm using the notification area icon, I have found that the pm-suspend script is called by default . That script does not work on my machine, but if I rename pm-suspend-hybrid to pm-suspend the suspend process using xfpm works again. Note that pm-suspend-hybrid is just suspending after taking a ram snapshot for hibernation. So what you really means, I guess, is that suspend fails while hibernation works, and that's an issue in your kernel (or X drivers or something). pm-suspend-hybrid is just suspending my device, not hibernating, and you can not unplug the laptop using this method. This suspend method is an hybrid. The wake up process is also way faster than full hibernation (seconds vs about a minute or more). But renaming a file is not a user friendly way of selecting the suspend method. Maybe it would be possible to allow the user to select the suspend method (pm-suspend or pm-suspend-hybrid) in the applet, is there only one kind of dbus suspend call available? If so maybe we should notify this to upower package mantainer. A quick look in dbus methods offered by upower shows that it only have suspend() and hibernate(), yes. How should I notify then the upower mantainers, should I open another bug? How can we involve them in this discussion? 2) This is a wish. I would like to setup the xfpm to suspend my computer when plugged and hybernate when running on batteries. Is this possible? Well, you can configure various options for when you're on AC and when you're on battery in the settings interface. Yes but it seems that I can not specify a different method for each: plugged - suspend unplugged - hibernate There are more options in the advanced tab, but the inactivity option seems to be shared. Maybe this is different in the lastest version of XFCE. We can split the two topics, because the second has severity wishlist and should be in another bugreport.
Bug#688770: coreutils: date --date=YYYY is incorrect
Package: coreutils Version: 8.13-3.2 Severity: normal date --date=, where is a year, just returns today's date without complaining about an invalid input. I would expect it to produce the same date as -01-01. -- System Information: Debian Release: wheezy/sid APT prefers testing APT policy: (500, 'testing'), (400, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.2.0-3-amd64 (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 Versions of packages coreutils depends on: ii dpkg 1.16.8 ii install-info 4.13a.dfsg.1-10 ii libacl1 2.2.51-8 ii libattr1 1:2.4.46-8 ii libc6 2.13-35 ii libselinux1 2.1.9-5 coreutils recommends no packages. coreutils 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#688771: Update gwyddion to version 2.30
Package: gwyddion Version: 2.29-2Gwyddion 2.30 has been released upstream. In debian it's in version 2.29. This bug report request for an upgrade. Please find attached a modified version of the fix-rpath-issue.patch. This new patches allow for successful compilation (it fails with th eolder one in 2.29-2). Changelog: Application Translations updated: French, Russian. Handling of files with non-ASCII characters in names on Win32 was improved. Libraries libgwyprocess: A new function to remove grains touching image borders. libgwyprocess: New grain quantities: Radius and position of maximum inscribed disc and minimum excscribed circle, area of grain convex hull, mean radius. libgwyapp: Critical warning/crash if the last visible channel of a file is deleted and this channel has a mask. libgwyapp: Setting a channel or graph visibility key in a container actually shows or hides the corresponding data. Modules Neural network: Split to two functions: training and application. Networks can be saved, trained on multiple data (sequentially), training signal can be masked, units of the output can be specified. APE file: Channel labelling for various modes was corrected. Createc: Dimensions and values of imported data was corrected, all channels are imported now. IGOR file: Crash on files that contain no channel titles was fixed. Selection manager tool: Chosen selection is shown in the data window. Remove Grain by Threshold: Can also remove grains touching image borders. Grain Statistics: Select Inscribed Discs and Select Excscribed Circles create circular selections visualising the corresponding discs/circles. Grain correlations: Really works when run non-interactively. Other Compatibility with newer version of GLib that deprecate various things was improved. fix-rpath-issue.patch Description: Binary data
Bug#688772: gnome Depends network-manager-gnome
Package: tech-ctte As I wrote to debian-release: As you may be aware, the TC recently overruled the maintainers of the gnome-core metapackage, deciding that the dependency from gnome-core to network-manager should be weakened from Depends to Recommends. (The full TC decision is reproduced below.) In response to this the maintainers have uploaded a new version of meta-gnome in which the gnome-core package Recommends network-manager-gnome, as required. However, additionally, they have reintroduced a dependency from gnome to network-manager-gnome, as Depends. See the changes info, also below. The Release Team should be aware that our request to unblock the update to meta-gnome implementing the TC decision does not extend to this latter change to meta-gnome. I am going to try to get the TC to pass another resolution specifically overruling this further decision by the gnome-core maintainers. This bug is to track this issue. Please send all discussion on this topic only to this bug report. I will make sure that the gnome maintainers are pointed to this bug report. Ian. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#686648: ioquake3: consider disallowing auto-downloading in wheezy
On 25/09/12 13:44, Markus Koschany wrote: Indeed it isn't reproducible with a clean installation of OpenArena. You have to connect to a heavily modded server like Gem's InstaGib server. Playing on a modded server with auto-download turned on can replace the UI with arbitrary bytecode - for instance, a UI based on the upstream OpenArena release, which will consequently no longer have the are you sure you want to shoot yourself in the foot? prompt. If that's what's happening here, then there's no way to fix it. S -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#617342: Update program for testing (failure to convert 32-bit images)
Hi Steve, Thank you for the report. I will look into this distribution issue. FYI, the binaries for OS X and all Linux versions available on the MRIConvert web site should be up-to-date with 32-bit code. Regards, Chuck On 12-09-24 07:12 PM, Steve M. Robbins wrote: Hello Chuck, While working my way through my Debian bug list, I noticed this one [1] is still open: MRIConvert does not support 32 bits I tried Mathieu's image on the latest Debian MRIConvert (2.0.235), and it failed as noted in the report: the output is 16 bits, not 32. On Thu, Oct 13, 2011 at 12:43:17PM -0700, Chuck Theobald wrote: I've made some changes so that MRIConvert emits 32-bit .raw files, but do not have a way to test. Attached is a tarball with Debian binaries for testing. Then I tried the binary you attached, and obtained 32 bit output. Scratching my head, I tried the Debian binary again. Same result. Then I noticed the Debian binary's Help|About box claims the version is 2.0.217. I went back to my source archives and discovered that the upstream versions in Debian are THE SAME for 2.0.217 and 2.0.235. I went to the download site [2] and discovered that the mriconvert_sources.zip is also the same as 2.0.217. Is it possible that the sources link was not updated when 2.0.235 was released? Could I trouble you to create a new release? Thanks, -Steve [1] http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=617342 [2] http://lcni.uoregon.edu/~jolinda/MRIConvert/mriconvert_sources.zip -- Chuck Theobald System Administrator The Robert and Beverly Lewis Center for Neuroimaging University of Oregon P: 541-346-0343 F: 541-346-0345 -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#672934: tagging 672934
Hello! On Tue, Sep 25, 2012 at 03:07:54PM +0200, Aurelien Jarno wrote: [...] This is already packaged in the SVN, though only tested on a few architectures. [...] Anything someone can help out with? You can build it and try it. I found the svn branch and am building it as we speak! (For anyone else interested see http://anonscm.debian.org/viewvc/pkg-glibc/glibc-package/branches/eglibc-2.16/ or svn://svn.debian.org/pkg-glibc/glibc-package/branches/eglibc-2.16/ and run fakeroot debian/rules get-orig-source to get the upstream sources.) Thanks for the status update! -- Andreas Henriksson -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#681717: Re: Bug#681717: unblock: openjpeg/1.3+dfsg-4.4
Hi, Release note that this bug blocks sound from working in wine and other i386 applications on amd64 in wheezy for many configurations (including mine). That is because libopenjpeg2 is required by libavcodec53 which is required by libasound2-plugins, which I need in both amd64 and i386 flavours to get sound to work in both 64 and 32 bit applications. Indeed this would be a regression compared to Squeeze, where lib32asound-plugins was available. Kind regards, Ralf -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#688773: grub2: Please compress binaries with xz
Source: grub2 Version: 1.99-22.1 Severity: important Tags: d-i patch Hi, we're trying to make some room on CD#1, and grub-common alone would shrink by 1MB by switching to xz. Please find attached a trivial patch to do this. A quick upload, or ack for an NMU, would be appreciated. Mraw, KiBi. diff -u grub2-1.99/debian/changelog grub2-1.99/debian/changelog --- grub2-1.99/debian/changelog +++ grub2-1.99/debian/changelog @@ -1,3 +1,10 @@ +grub2 (1.99-22.2) UNRELEASED; urgency=low + + * Non-maintainer upload. + * Use xz compression for all binaries to save up some space on CD images. + + -- Cyril Brulebois k...@debian.org Tue, 25 Sep 2012 16:12:18 +0200 + grub2 (1.99-22.1) unstable; urgency=low * Non-maintainer upload. diff -u grub2-1.99/debian/rules grub2-1.99/debian/rules --- grub2-1.99/debian/rules +++ grub2-1.99/debian/rules @@ -256,6 +256,9 @@ override_dh_strip: dh_strip -X/usr/bin/grub-emu +override_dh_builddeb: + dh_builddeb -- -Zxz + override_dh_auto_clean: -rm -rf build -rm -f contrib grub-core/contrib
Bug#687369: Updates to wine-1.4.1-2 -- acceptable for wheezy?
Dear release team, could somebody please take a look at the patches and the explanations that I posted and tell me if a freeze exception would be possible for an updated wine package? Thanks, -Hilko -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#688772: gnome Depends network-manager-gnome
As I wrote to debian-release: As you may be aware, the TC recently overruled the maintainers of the gnome-core metapackage, deciding that the dependency from gnome-core to network-manager should be weakened from Depends to Recommends. (The full TC decision is reproduced below.) In response to this the maintainers have uploaded a new version of meta-gnome in which the gnome-core package Recommends network-manager-gnome, as required. However, additionally, they have reintroduced a dependency from gnome to network-manager-gnome, as Depends. See the changes info, also below. The Release Team should be aware that our request to unblock the update to meta-gnome implementing the TC decision does not extend to this latter change to meta-gnome. I am going to try to get the TC to pass another resolution specifically overruling this further decision by the gnome-core maintainers. As I say I think this needs to be revisited by the TC. I have filed #688772 against tech-ctte to track this. Please send all discussion on this topic only to this bug report. You will probably want to subscribe to this bug, and to read its online archives to catch up with any messages you have missed. Thanks, Ian. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#688692: closed by Cyril Brulebois k...@debian.org (Re: Bug#688692: pidgin: Please get your package rebuilt to enable xz compression)
Control: reopen -1 Debian Bug Tracking System ow...@bugs.debian.org (25/09/2012): Ari Pollak a...@debian.org (24/09/2012): I think a binNMU would be the best bet. ACK, thanks for the fast reply. Just did that accordingly: kibi@grieg:~$ wb nmu pidgin . ALL . -m 'Rebuild to gain xz compression, saving some space on CD images (See: #688692).' Closing this bug report accordingly. Sorry, I was being stupid. BinNMUs don't update arch: all packages, so pidgin-data doesn't shrink. An upload would be appreciated accordingly… Mraw, KiBi. signature.asc Description: Digital signature
Bug#688773: grub2: Please compress binaries with xz
On Tue, Sep 25, 2012 at 05:00:39PM +0200, Cyril Brulebois wrote: we're trying to make some room on CD#1, and grub-common alone would shrink by 1MB by switching to xz. Please find attached a trivial patch to do this. A quick upload, or ack for an NMU, would be appreciated. While this is fine, I'd like to attack the batch of recent piuparts bugs in the same upload. I'll make time for this this evening or (more likely) tomorrow, if that's OK? -- 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#688750: schroot and autofs need better integration
On 25.09.2012 15:34, Reinhard Tartler wrote: Package: schroot,autofs Severity: normal I have a setup in which the home directory is mounted via NFS with the help of autofs. Because of #622756 and #648459, bind-mounting /home with the rbind option is unfortunately not an option. Until this becomes possible, the chroot needs to start its own automount processes. Well. This is explained well in #648459. Kernel side of this needs to be fixed, and I agree completely -- this is the only reasonable thing to do. All the other ways to fix this issue will result in other issues popping up. Schroot 1.6 features an option to start services. Unfortunately, this feature does not work with the autofs init script. Upon starting a squeeze chroot with autofs installed and enabled in the configuration, I get this error: schroot -c squeeze-amd64 I: 70services: Starting automount automount.../usr/sbin/automount already running. I: 70services: . W: Failed to change to directory ‘/home/siretart’: No such file or directory I suspect this is because the autofs init script detects that there is already an automount instance running. Unfortunately, this is the instance outside the chroot. Autofs initscript uses start-stop-daemon with a pidfile option. I'm not sure we should teach it about this situation. But as far as I understand, /run from host is bind-mounted to schroot too, right? If that's the case, we can't run two automountds this way anyway, since the two will try to use the same pidfile, which will break. Interestingly, the service option does work with autofs in an ubuntu/quantal chroot, which uses upstart to manage and supervise services, just fine. Upstart uses different, rather fragile, technique to watch for daemons. Debian initscripts Co uses pidfiles, upstart watches for forks. Note that for this very reason stock autofs does not work here, since it spawns mount proces during startup and upstart, who watches for forks, thinks it is this mount which is the main process, and whole things breaks. Autofs had to be patched for ubuntu quantal to stop doing checks at startup, because of this very reason. In order to solve this, I see two possibilities: a) enhance the autofs init script to become chroot-aware. b) extend schroot to start autofs managed mount points by itself, ideally using the host-provided autofs programs so that autofs does not need to be installed into the chroot. There's one more solution which is not listed but which is the only real solution: fix the real issue instead of designing workarounds of various levels of quality. The thing is: autofs is very messy thing, both userspace and kernel. /mjt -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#688773: grub2: Please compress binaries with xz
Colin Watson cjwat...@debian.org (25/09/2012): While this is fine, I'd like to attack the batch of recent piuparts bugs in the same upload. I'll make time for this this evening or (more likely) tomorrow, if that's OK? That's perfect, thanks! Mraw, KiBi. signature.asc Description: Digital signature
Bug#688774: mirror submission for debian.mirror.constant.com
Package: mirrors Severity: wishlist Submission-Type: new Site: debian.mirror.constant.com Type: leaf Archive-architecture: ALL amd64 armel armhf hurd-i386 i386 ia64 kfreebsd-amd64 kfreebsd-i386 mips mipsel powerpc s390 s390x sparc Archive-http: / IPv6: yes Archive-upstream: ftp.us.debian.org Updates: four Maintainer: Brian Rak mirr...@constant.com Country: US United States Location: Piscataway, New Jersey Sponsor: Constant.com http://www.constant.com -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#635964: New version still not available
I've just checked and the new version of of pdfsam is still not available though it contains significant enhancements. Version 1.1.4 has been released in 2009, version 2.2.1 in 2010 and the package has still not been updated. Regards, Tom -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#688775: nvidia-graphics-drivers: upgrade of nvidia graphics driver wants to install unnecessary packages
Source: nvidia-graphics-drivers
Version: 304.48-1
Severity: normal
Dear Maintainer,
the upgrade of the nvidia graphics drivers on wheezy (from version
302.17-3 to 304.48-1) tries to install more than 50 MB of new,
unnecessary packages:
# aptitude dist-upgrade
The following NEW packages will be installed:
dkms{a} [2.2.0.3-1.1] +347 kB
linux-headers-3.2.0-3-686-pae{a} [3.2.23-1] +9,137 kB
linux-headers-3.2.0-3-common{a} [3.2.23-1] +17.9 MB
linux-headers-686-pae{a} [3.2+45] +28.7 kB
linux-kbuild-3.2{a} [3.2.17-1] +660 kB
nvidia-kernel-dkms{a} [304.48-1] +27.4 MB
The following packages will be upgraded:
libgl1-nvidia-alternatives [302.17-3 - 304.48-1] +6,144 B
libgl1-nvidia-glx [302.17-3 - 304.48-1] +313 kB
libglx-nvidia-alternatives [302.17-3 - 304.48-1] +6,144 B
libnvidia-ml1 [302.17-3 - 304.48-1] +135 kB
libxnvctrl0 [302.17-2 - 304.48-1] +1,024 B
nvidia-alternative [302.17-3 - 304.48-1] +7,168 B
nvidia-glx [302.17-3 - 304.48-1] +26.6 kB
nvidia-settings [302.17-2 - 304.48-1] +1,024 B
nvidia-smi [302.17-3 - 304.48-1] +27.6 kB
nvidia-vdpau-driver [302.17-3 - 304.48-1] +67.6 kB
xserver-xorg-video-nvidia [302.17-3 - 304.48-1] -195 kB
11 packages upgraded, 6 newly installed, 0 to remove and 1 not upgraded.
Need to get 0 B/22.3 MB of archives. After unpacking 55.8 MB will be used.
Same with apt-get:
# apt-get dist-upgrade
Reading package lists... Done
Building dependency tree
Reading state information... Done
Calculating upgrade... Done
The following NEW packages will be installed:
dkms (2.2.0.3-1.1)
linux-headers-3.2.0-3-686-pae (3.2.23-1)
linux-headers-3.2.0-3-common (3.2.23-1)
linux-headers-686-pae (3.2+45)
linux-kbuild-3.2 (3.2.17-1)
nvidia-kernel-dkms (304.48-1)
The following packages have been kept back:
hpodder (1.1.5.0+nmu2 = 1.1.5.0+nmu3)
The following packages will be upgraded:
libgl1-nvidia-alternatives (302.17-3 = 304.48-1)
libgl1-nvidia-glx (302.17-3 = 304.48-1)
libglx-nvidia-alternatives (302.17-3 = 304.48-1)
libnvidia-ml1 (302.17-3 = 304.48-1)
libxnvctrl0 (302.17-2 = 304.48-1)
nvidia-alternative (302.17-3 = 304.48-1)
nvidia-glx (302.17-3 = 304.48-1)
nvidia-settings (302.17-2 = 304.48-1)
nvidia-smi (302.17-3 = 304.48-1)
nvidia-vdpau-driver (302.17-3 = 304.48-1)
xserver-xorg-video-nvidia (302.17-3 = 304.48-1)
11 upgraded, 6 newly installed, 0 to remove and 1 not upgraded.
Need to get 0 B/22.3 MB of archives.
After this operation, 55.8 MB of additional disk space will be used.
I guess the problem is that the new nvidia-kernel-amd64 package
has not been migrated to wheezy yet:
# apt-cache policy nvidia-kernel-amd64
nvidia-kernel-amd64:
Installed: 302.17+2
Candidate: 302.17+2
Version table:
304.48+1 0
650 http://ftp.debian.org/debian/ sid/non-free i386 Packages
*** 302.17+2 0
750 http://ftp.debian.org/debian/ wheezy/non-free i386 Packages
100 /var/lib/dpkg/status
Please make sure that the nvidia graphics driver packages always get
migrated together, not separately.
Regards,
Uwe
-- System Information:
Debian Release: wheezy/sid
APT prefers testing
APT policy: (750, 'testing'), (650, 'unstable'), (1, 'experimental')
Architecture: i386 (x86_64)
Kernel: Linux 3.2.0-3-amd64 (SMP w/2 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#688766: kde4libs: Please get your package rebuilt to gain xz compression
Control: tag -1 pending On Tue 25 Sep 2012 11:00:59 Cyril Brulebois escribió: Package: kde4libs Version: 4:4.8.4-3 Severity: important Tags: d-i patch Hi, trying to make KDE fit on KDE CD#1, this package would be nice to get rebuilt to gain xz compression. Especially for that part: 2.6M /home/ftpmirror/mirrors/debian/pool/main/k/kde4libs/libkhtml5_4.8.4-3_amd6 4.deb 1.9M../libkhtml5_4.8.4-3_amd64.deb Thanks for considering. Mraw, KiBi. I have almost done the next point release which are trivial changes and some bugfixes. I'll do my best to get this done during the weekend (hopefully even sooner). Kinds regards, Lisandro. -- Quote me as saying I was mis-quoted. -- Groucho Marx Lisandro Damián Nicanor Pérez Meyer http://perezmeyer.com.ar/ http://perezmeyer.blogspot.com/ signature.asc Description: This is a digitally signed message part.
Bug#688758: kde-runtime: Please get your package rebuilt to gain xz compression
Control: tag -1 pending On Tue 25 Sep 2012 09:50:23 Cyril Brulebois escribió: Package: kde-runtime Version: 4:4.8.4-1 Severity: important Tags: d-i patch Hi, we're trying to get KDE (up to kde-standard) to fit on KDE CD#1, and kde-runtime would benefit from xz compression: a rebuild would make kde-runtime-data shrink from 3.4MB to 2.1MB. If you have trivial changes pending, a quick upload would be appreciated. Otherwise, a binNMU should work just fine, since AFAICT there's no multiarch fun involved in this package. I have almost done the next point release which are *trivial* changes: two bugfixes and some typos fixed in .desktop files. I'll do my best to get this done during the weekend (hopefully even sooner). Kinds regards, Lisandro. -- Quote me as saying I was mis-quoted. -- Groucho Marx Lisandro Damián Nicanor Pérez Meyer http://perezmeyer.com.ar/ http://perezmeyer.blogspot.com/ signature.asc Description: This is a digitally signed message part.
Bug#688750: schroot and autofs need better integration
On Tue, Sep 25, 2012 at 5:14 PM, Michael Tokarev m...@tls.msk.ru wrote: Autofs initscript uses start-stop-daemon with a pidfile option. Oh, it seems that this has been rectified in by now wheezy, but not in wheezy-backports yet. If you don't mind, I would update the backport as I was the last uploader anyway. I'm not sure we should teach it about this situation. But as far as I understand, /run from host is bind-mounted to schroot too, right? If that's the case, we can't run two automountds this way anyway, since the two will try to use the same pidfile, which will break. /run is not bind-mounted by default, but schroot can be instructed to do so. As you correctly, point out, a bind-mounted /run will probably cause problems. Interestingly, the service option does work with autofs in an ubuntu/quantal chroot, which uses upstart to manage and supervise services, just fine. Upstart uses different, rather fragile, technique to watch for daemons. Debian initscripts Co uses pidfiles, upstart watches for forks. We could of course argue about the 'fragile' part, but fragile or not, stuff does work there :-) Note that for this very reason stock autofs does not work here, since it spawns mount proces during startup and upstart, who watches for forks, thinks it is this mount which is the main process, and whole things breaks. Autofs had to be patched for ubuntu quantal to stop doing checks at startup, because of this very reason. Which of the following patches would implement what you describe? http://bazaar.launchpad.net/~ubuntu-branches/ubuntu/quantal/autofs/quantal/files/head:/debian/patches/ In order to solve this, I see two possibilities: a) enhance the autofs init script to become chroot-aware. b) extend schroot to start autofs managed mount points by itself, ideally using the host-provided autofs programs so that autofs does not need to be installed into the chroot. There's one more solution which is not listed but which is the only real solution: fix the real issue instead of designing workarounds of various levels of quality. The thing is: autofs is very messy thing, both userspace and kernel. What I understood so far is that rbind mounts cause vfs semantics that do not play well with autofs. Since you seem to have way more knowledge than I have on this matter, maybe you could file a proper bug report with a compilation of all relevant pieces of information? -- regards, Reinhard -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#688772: gnome Depends network-manager-gnome
I'm quite cross. How about this? Ian. Whereas 1. The TC notes the decision of the meta-gnome maintainers to implement our decision in #681834 by: (a) softening the dependency in the gnome-core metapackage from Depends to Recommends, as required (b) adding a new dependency in the gnome metapackage, as a Depends. (In squeeze, this is where the dependency was, but it was a Recommends.) 2. Our intent, as stated in the rationale section of our previous decision (#681834, paras 3 and 5), is that squeeze users who have gnome installed but not network-manager do not find that network-manager becomes installed when they upgrade to wheey. 3. The actions of the meta-gnome maintainers do not achieve this objective. 4. A Recommends from gnome to network-manager-gnome would serve no purpose in wheezy as gnome Depends on gnome-core which already Recommends network-manager-gnome. Therefore 4. We overrule the decision of the meta-gnome maintainers to add a dependency from gnome to network-manager. This dependency should be removed. 5. We request that the Release Team unblock update(s) to meta-gnome so that our decisions may be implemented in wheezy. 6. We specifically forbid anyone from introducing in wheezy, or in sid until wheezy is released: a. Any new or enhanced dependencies, or any other mechanisms which are intended to increase the likelihood of network-manager being installed; b. Any new or enhanced user-facing warnings, imprecations, or other kinds of message regarding the alleged desirability or requirement to install network-manager; c. Any change which in any way impairs (or further impairs) the functioning of systems with GNOME components installed but without network-manager; d. Any change which is contrary to the spirit or intent of either our previous resolution in #681834 or this resolution. without first obtaining the permission of at least one member of the Technical Committee. 7. We request that the Release Team DO NOT unblock any updates to wheezy which appear to the Release Team to be contrary to our intent. Furthermore 8. It should have been obvious that the path chosen by the meta-gnome maintainers would not be satisfactory. If there had been any doubt on this point, the maintainers should have proposed this solution while the TC resolution was being discussed and drafted so that it could have been accepted or rejected accordingly. 9. We conclude that the actions of the meta-gnome maintainers are plainly intended to defeat or evade the intent of our previous decision. We note that the Constitution requires members of the project not to work against decisions properly made according to the project's governance processes. 10. We therefore formally reprimand Josselin Mouette. We consider his behaviour deliberately obstructive and obtuse. 11. On this occasion we do not feel it necessary to refer anyone to the Debian Account Managers asking for a review of their status. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#688772: gnome Depends network-manager-gnome
(Sorry, trying this again because p.d.o doesn't recognise the source package name, only the binary package name:) As I wrote to debian-release: As you may be aware, the TC recently overruled the maintainers of the gnome-core metapackage, deciding that the dependency from gnome-core to network-manager should be weakened from Depends to Recommends. (The full TC decision is reproduced below.) In response to this the maintainers have uploaded a new version of meta-gnome in which the gnome-core package Recommends network-manager-gnome, as required. However, additionally, they have reintroduced a dependency from gnome to network-manager-gnome, as Depends. See the changes info, also below. The Release Team should be aware that our request to unblock the update to meta-gnome implementing the TC decision does not extend to this latter change to meta-gnome. I am going to try to get the TC to pass another resolution specifically overruling this further decision by the gnome-core maintainers. As I say I think this needs to be revisited by the TC. I have filed #688772 against tech-ctte to track this. Please send all discussion on this topic only to this bug report. You will probably want to subscribe to this bug, and to read its online archives to catch up with any messages you have missed. Thanks, Ian. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#630581: dropbear: diff for NMU version 2012.55-1.2
Hi Gerrit!
As you welcomed it, I have uploaded an NMU for dropbear fixing the
initramfs issue. Well, two actually. It only hit me after the first
that I had not verified upgrades from Squeeze, and indeed, they were
broken.
--
Jérémy Bobbio.''`.
lu...@debian.org: :Ⓐ : # apt-get install anarchism
`. `'`
`-
diff -u dropbear-2012.55/debian/changelog dropbear-2012.55/debian/changelog
--- dropbear-2012.55/debian/changelog
+++ dropbear-2012.55/debian/changelog
@@ -1,3 +1,18 @@
+dropbear (2012.55-1.2) unstable; urgency=low
+
+ * Non-maintainer upload.
+ * Unbreak initramfs hook when upgrading from Squeeze.
+
+ -- Jérémy Bobbio lu...@debian.org Tue, 25 Sep 2012 16:53:18 +0200
+
+dropbear (2012.55-1.1) unstable; urgency=low
+
+ * Non-maintainer upload.
+ * Adjust initramfs hook to work with multi-arch. Initial patch by
+Michael Stapelberg. (Closes: #630581)
+
+ -- Jérémy Bobbio lu...@debian.org Tue, 25 Sep 2012 09:17:06 +0200
+
dropbear (2012.55-1) unstable; urgency=high
* New upstream release.
diff -u dropbear-2012.55/debian/initramfs/dropbear-hook dropbear-2012.55/debian/initramfs/dropbear-hook
--- dropbear-2012.55/debian/initramfs/dropbear-hook
+++ dropbear-2012.55/debian/initramfs/dropbear-hook
@@ -27,7 +27,11 @@
else
rm -f ${DESTDIR}/sbin/dropbear
copy_exec /usr/sbin/dropbear /sbin/
- cp /lib/libnss_* ${DESTDIR}/lib/
+ LIBC_DIR=$(ldd /usr/sbin/dropbear | sed -n -e 's,.* = \(/lib.*\)/libc\.so\..*,\1,p')
+ for so in $(find ${LIBC_DIR} -name 'libnss_compat*'); do
+ copy_exec ${so} ${LIBC_DIR}
+ done
+ echo 'passwd: compat' ${DESTDIR}/etc/nsswitch.conf
echo root:x:0:0:root:/root:/bin/sh ${DESTDIR}/etc/passwd
for keytype in dss rsa; do
if [ ! -f /etc/initramfs-tools/etc/dropbear/dropbear_${keytype}_host_key ]; then
signature.asc
Description: Digital signature
Bug#688776: unblock: marble/4:4.8.4-3
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: unblock
Please consider pre-approving the unblock for marble.
- fixes a FTBFS that happen in an enviroment with QML stuff installed,
e.g. the various libqt4-declarative-* (#688755), fixing also their
installation path to the proper place
- removes files not usable in Debian (due to lack of packaged
dependencies)
- suggests in marble the packages for the different local routing
services it can use (#677058)
unblock marble/4:4.8.4-3
Thanks,
--
Pino
diff -Nru marble-4.8.4/debian/changelog marble-4.8.4/debian/changelog
--- marble-4.8.4/debian/changelog 2012-06-21 22:20:10.0 +0200
+++ marble-4.8.4/debian/changelog 2012-09-25 17:33:16.0 +0200
@@ -1,3 +1,15 @@
+marble (4:4.8.4-3) unstable; urgency=low
+
+ * Team upload.
+ * Fix the detection of the QML imports directory, and move the QML stuff
+accordingly; patch fix_qmake_fallback.diff. (Closes: #688755)
+ * Do not install marble-touch and its qtcomponents, since they require
+libraries not available in Debian.
+ * Add in marble suggests for the various routing services: libqt4-sql-sqlite,
+gosmore, monav-routing-daemon, routino. (Closes: #677058)
+
+ -- Pino Toscano p...@debian.org Tue, 25 Sep 2012 17:30:22 +0200
+
marble (4:4.8.4-2) unstable; urgency=low
* Push to unstable
diff -Nru marble-4.8.4/debian/control marble-4.8.4/debian/control
--- marble-4.8.4/debian/control 2012-06-16 23:06:53.0 +0200
+++ marble-4.8.4/debian/control 2012-09-25 17:16:33.0 +0200
@@ -23,6 +23,7 @@
Section: misc
Depends: ${shlibs:Depends}, ${misc:Depends}, marble-data (= ${source:Version}),
marble-plugins (= ${binary:Version})
+Suggests: libqt4-sql-sqlite, gosmore, monav-routing-daemon, routino
Description: globe and map widget
Marble is a generic geographical map widget and framework for KDE
applications. The Marble widget shows the earth as a sphere but does not
diff -Nru marble-4.8.4/debian/marble.install marble-4.8.4/debian/marble.install
--- marble-4.8.4/debian/marble.install 2012-06-16 22:45:10.0 +0200
+++ marble-4.8.4/debian/marble.install 2012-09-25 16:51:29.0 +0200
@@ -1,5 +1,4 @@
usr/bin/marble
-usr/bin/marble-touch
usr/bin/routing-instructions
usr/bin/tilecreator
usr/lib/kde4/libmarble_part.so
diff -Nru marble-4.8.4/debian/marble-plugins.install marble-4.8.4/debian/marble-plugins.install
--- marble-4.8.4/debian/marble-plugins.install 2012-06-16 22:44:25.0 +0200
+++ marble-4.8.4/debian/marble-plugins.install 2012-09-25 16:50:31.0 +0200
@@ -1,3 +1,6 @@
+usr/lib/*/qt4/imports/org/kde/edu/marble/MarbleSettings.qml
+usr/lib/*/qt4/imports/org/kde/edu/marble/libMarbleDeclarativePlugin.so
+usr/lib/*/qt4/imports/org/kde/edu/marble/qmldir
usr/lib/kde4/plugins/marble/13/AprsPlugin.so
usr/lib/kde4/plugins/marble/13/CachePlugin.so
usr/lib/kde4/plugins/marble/13/CompassFloatItem.so
@@ -37,17 +40,3 @@
usr/lib/kde4/plugins/marble/13/Weather.so
usr/lib/kde4/plugins/marble/13/Wikipedia.so
usr/lib/kde4/plugins/marble/13/YoursPlugin.so
-usr/lib/kde4/plugins/marble/13/org/kde/edu/marble/MarbleSettings.qml
-usr/lib/kde4/plugins/marble/13/org/kde/edu/marble/libMarbleDeclarativePlugin.so
-usr/lib/kde4/plugins/marble/13/org/kde/edu/marble/qmldir
-usr/lib/kde4/plugins/marble/13/org/kde/edu/marble/qtcomponents/FileDialog.qml
-usr/lib/kde4/plugins/marble/13/org/kde/edu/marble/qtcomponents/FileOpenDialog.qml
-usr/lib/kde4/plugins/marble/13/org/kde/edu/marble/qtcomponents/FileSaveDialog.qml
-usr/lib/kde4/plugins/marble/13/org/kde/edu/marble/qtcomponents/MenuItemSwitch.qml
-usr/lib/kde4/plugins/marble/13/org/kde/edu/marble/qtcomponents/RouteEditor.qml
-usr/lib/kde4/plugins/marble/13/org/kde/edu/marble/qtcomponents/RoutingDialog.qml
-usr/lib/kde4/plugins/marble/13/org/kde/edu/marble/qtcomponents/SearchField.qml
-usr/lib/kde4/plugins/marble/13/org/kde/edu/marble/qtcomponents/SearchResultSelectionDialog.qml
-usr/lib/kde4/plugins/marble/13/org/kde/edu/marble/qtcomponents/ViaPointEditor.qml
-usr/lib/kde4/plugins/marble/13/org/kde/edu/marble/qtcomponents/libQtComponentsPlugin.so
-usr/lib/kde4/plugins/marble/13/org/kde/edu/marble/qtcomponents/qmldir
diff -Nru marble-4.8.4/debian/not-installed marble-4.8.4/debian/not-installed
--- marble-4.8.4/debian/not-installed 2012-06-16 14:14:11.0 +0200
+++ marble-4.8.4/debian/not-installed 2012-09-25 16:51:37.0 +0200
@@ -1,2 +1,16 @@
# extra license file
./usr/share/kde4/apps/marble/data/LICENSE.txt
+
+# marble-touch
+./usr/bin/marble-touch
+./usr/lib/*/qt4/imports/org/kde/edu/marble/qtcomponents/FileDialog.qml
+./usr/lib/*/qt4/imports/org/kde/edu/marble/qtcomponents/FileOpenDialog.qml
+./usr/lib/*/qt4/imports/org/kde/edu/marble/qtcomponents/FileSaveDialog.qml
+./usr/lib/*/qt4/imports/org/kde/edu/marble/qtcomponents/MenuItemSwitch.qml
+./usr/lib/*/qt4/imports/org/kde/edu/marble/qtcomponents/RouteEditor.qml
Bug#688772: gnome Depends network-manager-gnome
Ian Jackson writes (Bug#688772: gnome Depends network-manager-gnome): 6. We specifically forbid anyone from introducing in wheezy, or in sid until wheezy is released: a. Any new or enhanced dependencies, or any other mechanisms which are intended to increase the likelihood of network-manager being installed; This is missing an important comma and should read: a. Any new or enhanced dependencies, or any other mechanisms, which are intended to increase the likelihood of network-manager being installed; Ian. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#686648: ioquake3: consider disallowing auto-downloading in wheezy
On Tue, 25. Sep 15:53 Simon McVittie s...@debian.org wrote: On 25/09/12 13:44, Markus Koschany wrote: Indeed it isn't reproducible with a clean installation of OpenArena. You have to connect to a heavily modded server like Gem's InstaGib server. Playing on a modded server with auto-download turned on can replace the UI with arbitrary bytecode - for instance, a UI based on the upstream OpenArena release, which will consequently no longer have the are you sure you want to shoot yourself in the foot? prompt. If that's what's happening here, then there's no way to fix it. I think that's exactly what's happening here. The whole pak6-patch088.pk3 file gets also downloaded again. Sounds like wontfix. signature.asc Description: Digital signature
Bug#684687: patch
tag 684687 patch thanks Here are two upstream patches that fix this problem and another similar one in the files inspector. Those would be nice to have in wheezy. Alex changeset_13421.diff Description: Binary data changeset_13436.diff Description: Binary data
Bug#688776: unblock: marble/4:4.8.4-3
Pino Toscano p...@debian.org (25/09/2012): - fixes a FTBFS that happen in an enviroment with QML stuff installed, e.g. the various libqt4-declarative-* (#688755), fixing also their installation path to the proper place - removes files not usable in Debian (due to lack of packaged dependencies) - suggests in marble the packages for the different local routing services it can use (#677058) Since it's supposed not to be usable, I guess nobody in the archive actually relies on marble-touch's presence? In which case please go ahead (and yay 1MB less on CD#1). Mraw, KiBi. signature.asc Description: Digital signature
Bug#688757: pvmove onto disk with different sector size hazardous
I'd be curious to know what this disk is, as well as what filesystem this was (I assume ext3) and what error messages were actually encountered. Could you tell us the model, but more importantly: # blockdev --getss --getpbsz /dev/whatever It sounds like it is a 4k drive but with no logical 512 mapping? aside from all that, pvmove of a mounted filesystem sounds terribly dangerous, though not related to the fsblocksize too small error you ran into. -Eric -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#688776: unblock: marble/4:4.8.4-3
Alle martedì 25 settembre 2012, Cyril Brulebois ha scritto: Pino Toscano p...@debian.org (25/09/2012): - fixes a FTBFS that happen in an enviroment with QML stuff installed, e.g. the various libqt4-declarative-* (#688755), fixing also their installation path to the proper place - removes files not usable in Debian (due to lack of packaged dependencies) - suggests in marble the packages for the different local routing services it can use (#677058) Since it's supposed not to be usable, I guess nobody in the archive actually relies on marble-touch's presence? I don't think so, since marble-touch is aimed mainly to small-factor interfaces, and we don't have many of those mobile stuff in Wheezy. In which case please go ahead (and yay 1MB less on CD#1). Thanks, I will. -- Pino Toscano signature.asc Description: This is a digitally signed message part.
Bug#688772: gnome Depends network-manager-gnome
On 25.09.2012 17:34, Ian Jackson wrote: I am going to try to get the TC to pass another resolution specifically overruling this further decision by the gnome-core maintainers. Seriously, WTF! Don't you have better things to do then pissing off everyone? -- 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#688777: /usr/bin/virsh: virsh and virt-manager different default uri
Package: libvirt-bin Version: 0.10.1-2 Severity: normal File: /usr/bin/virsh Hello, I tried to manage my virtual machines with virsh after creating them with virt-manager but virsh would not see them. This is because virt-manager defaults to xen:/// uri which I changed to qemu:///system but virt-manager defaults to the undocumented vbox:///session uri Ideally changing the connection in virt-manager should also set the default uri in virsh but at the very least the default uri should be the same. -- System Information: Debian Release: wheezy/sid APT prefers testing APT policy: (910, 'testing'), (900, 'stable'), (410, 'unstable'), (200, 'experimental'), (150, 'precise-updates'), (150, 'precise-security'), (150, 'precise') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.5-trunk-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) (ignored: LC_ALL set to en_US.UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages libvirt-bin depends on: ii adduser 3.113+nmu3 ii gettext-base0.18.1.1-9 ii libavahi-client30.6.31-1 ii libavahi-common30.6.31-1 ii libblkid1 2.22-1~test1 ii libc6 2.13-35 ii libcap-ng0 0.6.6-2 ii libdbus-1-3 1.6.0-1 ii libdevmapper1.02.1 2:1.02.74-4 ii libgcrypt11 1.5.0-3 ii libgnutls26 2.12.20-1 ii libnetcf1 0.1.9-2 ii libnl1 1.1-7 ii libnuma12.0.8~rc4-1 ii libparted0debian1 2.3-10 ii libpcap0.8 1.3.0-1 ii libpciaccess0 0.13.1-2 ii libreadline66.2-8 ii libsasl2-2 2.1.25.dfsg1-5 ii libudev0175-7 ii libvirt00.10.1-2 ii libxenstore3.0 4.2.0-1 ii libxml2 2.8.0+dfsg1-5 ii libyajl22.0.4-2 ii logrotate 3.8.1-4 Versions of packages libvirt-bin recommends: ii bridge-utils1.5-4 ii dmidecode 2.11-9 ii dnsmasq-base2.62-3 ii ebtables2.0.10.4-1 ii gawk1:4.0.1+dfsg-2 ii iproute 20120521-3 ii iptables1.4.14-3 ii libxml2-utils 2.8.0+dfsg1-5 ii netcat-openbsd 1.105-7 ii parted 2.3-10 ii pm-utils1.4.1-9 ii qemu1.1.0+dfsg-1 ii qemu-kvm1.1.1+dfsg-1nops2.1 Versions of packages libvirt-bin suggests: ii policykit-1 0.105-1 ii radvd1:1.9.1-1 -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#688778: /usr/bin/virsh: vbox:///session uri undocumented
Package: libvirt-bin Version: 0.10.1-2 Severity: normal File: /usr/bin/virsh Hello, vbox:///session is the default uri in virsh but it is not documented in the man page. -- System Information: Debian Release: wheezy/sid APT prefers testing APT policy: (910, 'testing'), (900, 'stable'), (410, 'unstable'), (200, 'experimental'), (150, 'precise-updates'), (150, 'precise-security'), (150, 'precise') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.5-trunk-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) (ignored: LC_ALL set to en_US.UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages libvirt-bin depends on: ii adduser 3.113+nmu3 ii gettext-base0.18.1.1-9 ii libavahi-client30.6.31-1 ii libavahi-common30.6.31-1 ii libblkid1 2.22-1~test1 ii libc6 2.13-35 ii libcap-ng0 0.6.6-2 ii libdbus-1-3 1.6.0-1 ii libdevmapper1.02.1 2:1.02.74-4 ii libgcrypt11 1.5.0-3 ii libgnutls26 2.12.20-1 ii libnetcf1 0.1.9-2 ii libnl1 1.1-7 ii libnuma12.0.8~rc4-1 ii libparted0debian1 2.3-10 ii libpcap0.8 1.3.0-1 ii libpciaccess0 0.13.1-2 ii libreadline66.2-8 ii libsasl2-2 2.1.25.dfsg1-5 ii libudev0175-7 ii libvirt00.10.1-2 ii libxenstore3.0 4.2.0-1 ii libxml2 2.8.0+dfsg1-5 ii libyajl22.0.4-2 ii logrotate 3.8.1-4 Versions of packages libvirt-bin recommends: ii bridge-utils1.5-4 ii dmidecode 2.11-9 ii dnsmasq-base2.62-3 ii ebtables2.0.10.4-1 ii gawk1:4.0.1+dfsg-2 ii iproute 20120521-3 ii iptables1.4.14-3 ii libxml2-utils 2.8.0+dfsg1-5 ii netcat-openbsd 1.105-7 ii parted 2.3-10 ii pm-utils1.4.1-9 ii qemu1.1.0+dfsg-1 ii qemu-kvm1.1.1+dfsg-1nops2.1 Versions of packages libvirt-bin suggests: ii policykit-1 0.105-1 ii radvd1:1.9.1-1 -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#687604: libkdtree++: diff for NMU version 0.7.0-1.1
Control: tags -1 + patch
Dear maintainer,
I've prepared an NMU for libkdtree++ (versioned as 0.7.0-1.1). It is
available at [1] and the debdiff is attached.
Regards
[1]
http://mentors.debian.net/debian/pool/main/libk/libkdtree++/libkdtree++_0.7.0-1.1.dsc
--
Sebastian Ramacher
diff -u libkdtree++-0.7.0/debian/changelog libkdtree++-0.7.0/debian/changelog
--- libkdtree++-0.7.0/debian/changelog
+++ libkdtree++-0.7.0/debian/changelog
@@ -1,3 +1,11 @@
+libkdtree++ (0.7.0-1.1) unstable; urgency=low
+
+ * Non-maintainer upload.
+ * Cherry pick 8d4fbb9a from upstream to fix issues with g++ 4.7. (Closes:
+#687604)
+
+ -- Sebastian Ramacher s.ramac...@gmx.at Tue, 25 Sep 2012 16:57:06 +0200
+
libkdtree++ (0.7.0-1) unstable; urgency=low
* New upstream release (closes: Bug#506485)
only in patch2:
unchanged:
--- libkdtree++-0.7.0.orig/kdtree++/kdtree.hpp
+++ libkdtree++-0.7.0/kdtree++/kdtree.hpp
@@ -1163,7 +1163,7 @@
{
typename _Base::NoLeakAlloc noleak(this);
_Link_type new_node = noleak.get();
- _M_construct_node(new_node, __V, __PARENT, __LEFT, __RIGHT);
+ _Base::_M_construct_node(new_node, __V, __PARENT, __LEFT, __RIGHT);
noleak.disconnect();
return new_node;
}
@@ -1181,8 +1181,8 @@
void
_M_delete_node(_Link_type __p)
{
-_M_destroy_node(__p);
-_M_deallocate_node(__p);
+ _Base::_M_destroy_node(__p);
+_Base::_M_deallocate_node(__p);
}
_Link_type _M_root;
signature.asc
Description: Digital signature
Bug#688779: liburcu1: shlibs too weak
Package: liburcu1 Version: 0.7.4-1 Severity: serious Justification: Policy 8.6 lttng-tools's postinst fails on my system, which still has liburcu1 0.6.7-2 (from testing), demonstrating that liblttng-ctl0 needs a versioned dependency on liburcu1. I would say liburcu1 is primarily at fault here (though lttng will need a round of binNMUs once you've fixed it). Could you please ensure that dpkg-shlibdeps will yield sufficiently strict dependencies on liburcu1 by either adding a .symbols file that will direct it to do so selectively or simply insisting on a versioned dependency in its .shlibs file (e.g., by running dh_makeshlibs -V). Thanks! Setting up lttng-tools (2.1.0~rc3-1) ... /usr/sbin/addgroup /usr/bin/lttng-sessiond: symbol lookup error: /usr/lib/x86_64-linux-gnu/liblttng-ctl.so.0: undefined symbol: rcu_flavor_mb invoke-rc.d: initscript lttng-sessiond, action start failed. dpkg: error processing lttng-tools (--configure): subprocess installed post-installation script returned error exit status 1 -- System Information: Debian Release: wheezy/sid APT prefers testing APT policy: (500, 'testing'), (500, 'stable'), (300, 'unstable') Architecture: amd64 (x86_64) Foreign Architectures: i386 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 liburcu1 depends on: ii libc6 2.13-35 liburcu1 recommends no packages. liburcu1 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#685527: unblock: packagekit/0.7.6-1
On Mon, Sep 03, 2012 at 03:46:10PM +0200, Matthias Klumpp wrote: Okay, breaking down the changes: Since the review resources of the release managers are scarce and since we should get the security fixes into Wheezy, what about preparing a 0.7.5-2+deb7u1 upload to testing-proposed-updates with the following changes only: Check for CancelBackgroundTransactions setting again: Respect the CancelBackgroundSetting setting again See http://gitorious.org/packagekit/packagekit/commit/1423e638600e7fd045b1ced0d584d59519610748 Do not allow the client to overwrite files when downloading packages: Pretty obvious what this does :-) Both a bugfix and a security enhancement. See http://gitorious.org/packagekit/packagekit/commit/a4a0210809b7bfda0df6874fe39b86b66590ef26 Fix several return values in pkcon when there is an error: Previously return codes weren't correct/weren't set on failure. See http://gitorious.org/packagekit/packagekit/commit/338842edf1a9d65b8708d514ab0f64fb684cf724 Ignore accept-eula in pk-transaction-run: Bugfix avoiding potential crash described in https://bugs.freedesktop.org/show_bug.cgi?id=53532 See http://gitorious.org/packagekit/packagekit/commit/771d28c110007d954c9ae65c5287fe1ee186589a Fix segfault in pkcon when user does ctrl-d at the package prompt: Kills this bug: https://bugzilla.redhat.com/show_bug.cgi?id=840342 See http://gitorious.org/packagekit/packagekit/commit/1594117d750e766309d3ff487bad3e39936a132c aptcc: Don't use tempfile with fixed name for conffiles: Resolves security issue in Debian, tracked as RC bug #678189 See http://gitorious.org/packagekit/packagekit/commit/e6e33f54dcc9b0058134e0d2584c2ee110ca0340 Fix a crash where NetworkManager is restarted whilst packagekitd is running: Important fix for packagekitd, I already got this reported by Debian users too. (Although it happens in a rare case) See http://gitorious.org/packagekit/packagekit/commit/1746179e446fa652027c673cff0f0f5e5daccd99 Cheers, Moritz -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#688780: virt-manager: vbox:///session uri not supported
Package: virt-manager Version: 0.9.4-1 Severity: normal Hello, While virt-manager defaults to xen:/// different connections can be configured. Still the virsh default connection vbox:///session cannot be configured in virt-manager at all. -- System Information: Debian Release: wheezy/sid APT prefers testing APT policy: (910, 'testing'), (900, 'stable'), (410, 'unstable'), (200, 'experimental'), (150, 'precise-updates'), (150, 'precise-security'), (150, 'precise') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.5-trunk-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) (ignored: LC_ALL set to en_US.UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages virt-manager depends on: ii gconf2 3.2.5-1+build1 ii librsvg2-common 2.36.1-1 ii python 2.7.3~rc2-1 ii python-dbus 1.1.1-1 ii python-glade22.24.0-3 ii python-gnome22.28.1+dfsg-1 ii python-gtk-vnc 0.5.1-1 ii python-gtk2 2.24.0-3 ii python-ipy 1:0.75-1 ii python-libvirt 0.10.1-2 ii python-spice-client-gtk 0.12-4 ii python-support 1.0.15 ii python-urlgrabber3.9.1-4 ii python-vte 1:0.28.2-5 ii virtinst 0.600.3-1 Versions of packages virt-manager recommends: ii gnome-icon-theme 3.4.0-2 ii libvirt-bin 0.10.1-2 Versions of packages virt-manager suggests: ii gnome-keyring3.4.1-5 pn python-gnomekeyring none ii python-guestfs 1:1.18.8-1 ii ssh-askpass-gnome [ssh-askpass] 1:6.1p1-1 ii virt-viewer 0.5.3-1 -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#687506: libgl1-nvidia-glx-ia32: Package has unfulfillable recommends
On 2012-09-25 16:27, Ralf Jung wrote: Hi, I just found out how ia32-libs does the multiarch migration trick, and probably that's what this package should do as well: * libgl1-nvidia-glx-ia32:amd64 should depend on libgl1-nvidia-glx-i386 * libgl1-nvidia-glx-i386 exists only for i386 and is MA: foreign, so it satisfies the dependency of libgl1-nvidia-glx-ia32 * libgl1-nvidia-glx-i386:i386 depends on libgl1-nvidia-glx, which will implicitly be libgl1-nvidia-glx:i386. Then installing libgl1-nvidia-glx-ia32 will automatically install libgl1-nvidia-glx-i386:i386 if the i386 packages are present (and will fail otherwise). That would be an approach, but uninstallable amd64 packages (because they depend on stuff thats only available in i386) is nothing currently handled well by the archive tools. Until ia32-libs migrates to wheezy, and we see that this is working, this is not a way that I will follow. Until then, well, the Recommends are for documentational purposes only, Andreas -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#686962: CVE-2012-3549: kfreebsd SCTP DoS
On Fri, Sep 07, 2012 at 12:17:45PM -0500, Raphael Geissert wrote: Package: kfreebsd-8 Severity: grave Tags: security Control: clone -1 -2 -3 Control: reassign -2 src:kfreebsd-9 Control: reassign -3 src:kfreebsd-10 Hi, CVE-2012-3549 has been assigned to be a remote DoS (via a NULL pointer dereference in the kernel) vulnerability in FreeBSD's SCTP implementation[1]. [1] http://www.exploit-db.com/exploits/20226/ If you fix the vulnerability please also make sure to include the CVE (Common Vulnerabilities Exposures) id in your changelog entry. If no upstream fix is available you might want to disable SCTP in the Wheezy kernel? Cheers, Moritz -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#688728: debirf: serial-terminal module cmdline matching
Control: tags 668728 + moreinfo On 09/25/2012 01:12 AM, Matt Taggart wrote: if printf %s $param | egrep -q '^console=ttyS[0-9]+,[0-9]+n8$'; then this is within a for loop: for param in $(cat /proc/cmdline); do ... the result that each element assigned to $param is split from the next by IFS, which is basic whitespace. the egrep regex to detect a serial console is anchored with ^ at the front, assuming that this console entry will be the first thing on the cmdline. This prevents one from doing such things as GRUB_CMDLINE_LINUX=console=tty0 console=ttyS0,115200n8 hm, i don't think it does. have you verified this? the anchor tests against the start of each parameter, not against the start of the entire /proc/cmdline. do you have an example of where this actually fails to work? makes it so that a getty runs on the first ttyS match on the line which is probably what's wanted (although I suppose someone might list multiple, like a real serial and an ipmi serial, but that would take more enhancing of this module). fwiw, i think most ipmi serials are also real serial ports on the mainboard, just exported via another external interface through the ipmi symbiont device. while the goal of spawning a getty on each line the kernel has its console on is an interesting one, i don't think it's particularly useful. once we're in the realm of using multiple serial lines, it's entirely possible that you want the kernel spew on one, a getty on another, and (who knows) a SLIP connection on the third. The current module is a helper to make some default connections work in a standard and expectable way, not a flexibly-configurable port multiplexer. while a module to handle port multiplexing in complex ways would be useful, i think that's an entirely different module than this one, not an enhancement of it. i've tagged this moreinfo because i don't see the bug in question, due to how $param is split out. Can you help me understand what the problem is? --dkg signature.asc Description: OpenPGP digital signature
Bug#688781: mongodb: watch file is inaccurate
Package: mongodb Version: 1:2.0.6-1 Severity: normal Tags: patch The watch file is out of date, this updates it to follow upstream's current layout. Returns 2.2.0 as of today. -- System Information: Debian Release: wheezy/sid APT prefers quantal-updates APT policy: (500, 'quantal-updates'), (500, 'quantal-security'), (500, 'quantal'), (400, 'precise-proposed') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.5.0-14-generic (SMP w/2 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages mongodb depends on: pn mongodb-dev none pn mongodb-server none mongodb recommends no packages. mongodb suggests no packages. === modified file 'debian/watch' --- a/debian/watch 2010-08-18 09:33:36 + +++ b/debian/watch 2012-09-25 15:44:49 + @@ -3,5 +3,5 @@ # examination of the downloads page content as the directory listing is not allowed anymore # Forced regexp to match only to the current stable release -http://www.mongodb.org/display/DOCS/Downloads \ - http://.*mongodb\.org/src/mongodb-src-r(1\.6[\d\.]+)\.tar\.gz +http://www.mongodb.org/downloads \ + http://downloads\.mongodb\.org/src/mongodb-src-r([\d\.]+).tar.gz
Bug#688782: Moving of mount points in initramfs from /live to /root/live does not work in important cases
Package: live-boot
Version: 3.0~b2-1
Severity: grave
Tags: patch
Hi
The attached patch fixes the move of persistence and other mounts from
/live to /root/live inside the initramfs. It also removes some
leftover mount points that are not used because the device did not
contain a persistence layer.
I'm setting the severity to grave as without these changes the
persistence filesystems can not be seen from the live system and
therefore cannot be remounted readonly on shutdown. This leaves these
filesystem in an inconsistent state which may lead to data corruption.
IMO this needs to be fixed for wheezy.
The patch consists of three individual commits that all can be applied
separately.
The readonly remounting of persistence filesystems does not work with
the latest live-config for unrelated reasons. I'll submit a separate bug
report (with patch ;-) ) to fix this issue.
Gaudenz
-- System Information:
Debian Release: wheezy/sid
APT prefers testing
APT policy: (800, 'testing'), (700, 'unstable'), (50, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 3.5-trunk-amd64 (SMP w/2 CPU cores)
Locale: LANG=de_CH.UTF-8, LC_CTYPE=de_CH.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
From 9339bf268e1d8b58db75228e30cedccffb47caeb Mon Sep 17 00:00:00 2001
From: Gaudenz Steinlin gaud...@debian.org
Date: Tue, 25 Sep 2012 17:54:45 +0200
Subject: [PATCH 1/3] Move filesystems even if mountpoint exists
If /live has a persistence layer the mountpoint may already exist. Move
the filesystems anyway.
---
scripts/boot/9990-main.sh | 11 ---
1 file changed, 4 insertions(+), 7 deletions(-)
diff --git a/scripts/boot/9990-main.sh b/scripts/boot/9990-main.sh
index 5732b2a..a95033e 100755
--- a/scripts/boot/9990-main.sh
+++ b/scripts/boot/9990-main.sh
@@ -146,11 +146,8 @@ Main ()
esac
# Move to the new root filesystem so that programs there can get at it.
- if [ ! -d /root/live/image ]
- then
- mkdir -p /root/live/image
- mount --move /live/image /root/live/image
- fi
+ [ ! -d /root/live/image ] mkdir -p /root/live/image
+ mount --move /live/image /root/live/image
# aufs2 in kernel versions around 2.6.33 has a regression:
# directories can't be accessed when read for the first the time,
@@ -159,9 +156,9 @@ Main ()
ls /root/* /dev/null 21
# Move findiso directory to the new root filesystem so that programs there can get at it.
- if [ -d /live/findiso ] [ ! -d /root/live/findiso ]
+ if [ -d /live/findiso ]
then
- mkdir -p /root/live/findiso
+ [ ! -d /root/live/findiso ] mkdir -p /root/live/findiso
mount -n --move /live/findiso /root/live/findiso
fi
--
1.7.10.4
From 79cf89b66bace9b980e7c175c0612a68c90d4507 Mon Sep 17 00:00:00 2001
From: Gaudenz Steinlin gaud...@debian.org
Date: Tue, 25 Sep 2012 17:56:51 +0200
Subject: [PATCH 2/3] Remove mountpoints if there is no persistence
Remove mountpoint if no persistence layer is found on a device.
---
scripts/boot/9990-misc-helpers.sh |2 ++
1 file changed, 2 insertions(+)
diff --git a/scripts/boot/9990-misc-helpers.sh b/scripts/boot/9990-misc-helpers.sh
index 117876f..4429c33 100755
--- a/scripts/boot/9990-misc-helpers.sh
+++ b/scripts/boot/9990-misc-helpers.sh
@@ -911,7 +911,9 @@ probe_for_file_name ()
then
echo ${ret}
else
+ # unmount and remove mountpoint
umount ${backing} /dev/null 21 || true
+ rmdir ${backing} /dev/null 21 || true
fi
}
--
1.7.10.4
From 31a6da42164d1abc7285506738a9a796b9a80afc Mon Sep 17 00:00:00 2001
From: Gaudenz Steinlin gaud...@debian.org
Date: Tue, 25 Sep 2012 17:58:50 +0200
Subject: [PATCH 3/3] Move mountpoints below /live/{persistence,rofs}
When moving a mountpoint all mounts below are not automatically moved.
This moves all these mountpoints individually.
---
scripts/boot/9990-overlay.sh | 19 +--
1 file changed, 17 insertions(+), 2 deletions(-)
diff --git a/scripts/boot/9990-overlay.sh b/scripts/boot/9990-overlay.sh
index 597ff50..5405781 100755
--- a/scripts/boot/9990-overlay.sh
+++ b/scripts/boot/9990-overlay.sh
@@ -405,8 +405,23 @@ setup_unionfs ()
done
fi
- mkdir -p ${rootmnt}/live
- mount -o move /live ${rootmnt}/live /dev/null 21 || mount -o bind /live ${rootmnt}/live || log_warning_msg Unable to move or bind /live to ${rootmnt}/live
+ # prepare /root/live with tmpfs for moving of filesystems
+ [ ! -d ${rootmnt}/live ] mkdir ${rootmnt}/live
+ mount -t tmpfs tmpfs ${rootmnt}/live
+
+ # move all mount points to root filesystem
+ for dir in rofs persistence
+ do
+ if [ -d /live/${dir} ]
+ then
+ mkdir ${rootmnt}/live/${dir}
+ for mp in $(ls /live/$dir)
+ do
+mkdir ${rootmnt}/live/${dir}/${mp}
+mount -o move /live/${dir}/${mp} ${rootmnt}/live/${dir}/${mp} /dev/null 21 || mount -o bind /live/${dir}/${mp} ${rootmnt}/live/${dir}/${mp} || log_warning_msg Unable to move or bind /live/${dir}/${mp} to ${rootmnt}/live/${dir}/${mp}
+ done
+ fi
+ done
# shows cow fs on /overlay (FIXME: do we still
Bug#687506: libgl1-nvidia-glx-ia32: Package has unfulfillable recommends
Hi, That would be an approach, but uninstallable amd64 packages (because they depend on stuff thats only available in i386) is nothing currently handled well by the archive tools. Until ia32-libs migrates to wheezy, and we see that this is working, this is not a way that I will follow. Until then, well, the Recommends are for documentational purposes only, Well, you could easily make libgl1-nvidia-glx-ia32:amd64 recommend libgl1-nvidia-glx-i386 - which you already do, so the only change would be making libgl1-nvidia-glx-i386 an actual MA: foreign package instead of a virtual one. Then libgl1-nvidia-glx-ia32:amd64 would be installable in any case, but those with i386 enable will get it installed automatically. Kind regards, Ralf -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#688750: schroot and autofs need better integration
On 25.09.2012 19:34, Reinhard Tartler wrote: On Tue, Sep 25, 2012 at 5:14 PM, Michael Tokarev m...@tls.msk.ru wrote: Autofs initscript uses start-stop-daemon with a pidfile option. Oh, it seems that this has been rectified in by now wheezy, but not in wheezy-backports yet. If you don't mind, I would update the backport as I was the last uploader anyway. I want to push one more release of autofs to sid (with aim to go to wheezy) today or tomorrow, with fixes for lots of other bugs. I know bpo60 hasn't been updated yet, but so is wheezy too, as we're waiting for the release team answer. The unblock request I sent is already of no use, since I already uploaded a new release and want to update it even further. It isn't really good idea to update bpo before the release team accepts stuff to wheezy, or havoc will happen. I'm not sure we should teach it about this situation. And indeed, I forgot that s-s-d isn't the case in wheezy and squeeze yet. But as far as I understand, /run from host is bind-mounted to schroot too, right? If that's the case, we can't run two automountds this way anyway, since the two will try to use the same pidfile, which will break. /run is not bind-mounted by default, but schroot can be instructed to do so. As you correctly, point out, a bind-mounted /run will probably cause problems. Interestingly, the service option does work with autofs in an ubuntu/quantal chroot, which uses upstart to manage and supervise services, just fine. Upstart uses different, rather fragile, technique to watch for daemons. Debian initscripts Co uses pidfiles, upstart watches for forks. We could of course argue about the 'fragile' part, but fragile or not, stuff does work there :-) Note that for this very reason stock autofs does not work here, since it spawns mount proces during startup and upstart, who watches for forks, thinks it is this mount which is the main process, and whole things breaks. Autofs had to be patched for ubuntu quantal to stop doing checks at startup, because of this very reason. Which of the following patches would implement what you describe? http://bazaar.launchpad.net/~ubuntu-branches/ubuntu/quantal/autofs/quantal/files/head:/debian/patches/ It is 0001-Remove-kernel-mount.nfs-version-checks-on-Debian-Ubu.patch, which removes spawning off mount.nfs at startup to determine its version. It is #678555 in debian. In order to solve this, I see two possibilities: a) enhance the autofs init script to become chroot-aware. b) extend schroot to start autofs managed mount points by itself, ideally using the host-provided autofs programs so that autofs does not need to be installed into the chroot. There's one more solution which is not listed but which is the only real solution: fix the real issue instead of designing workarounds of various levels of quality. The thing is: autofs is very messy thing, both userspace and kernel. What I understood so far is that rbind mounts cause vfs semantics that do not play well with autofs. Since you seem to have way more knowledge than I have on this matter, maybe you could file a proper bug report with a compilation of all relevant pieces of information? I know nothing about autofs kernel module, except of just one chance I had with it this spring (iirc), which discovered lots of bad logic in there (it was 32/64 bit issue). But at least now when I'm aware of the issue and as I somehow become autofs maintainer I can try to experiment and sum it up. I can't promise anything obviously, but I'll try... Thanks, /mj -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#688772: Please do not unblock gnome-meta just yet
(Discussion redirected to the TC bug report.) Rene Engelhard writes (Re: Please do not unblock gnome-meta just yet): On Tue, Sep 25, 2012 at 03:51:17PM +0100, Ian Jackson wrote: The Release Team should be aware that our request to unblock the update to meta-gnome implementing the TC decision does not extend to this latter change to meta-gnome. I believe that exceeds your powers. Your decision was implemented correct. I'm not in what way you think I'm exceeding my powers. I'm pointing out to the Release Team that the TC resolution does not request that the Release Team unblock this particular update. It is of course for the Release Team to make an unblock decision but I doubt they will make an unblock now; if I were them I would wait to see whether the TC makes a further resolution. Ans n-m - as people might like or not like, I am one who deson't (as a n-m user) - is part of GNOME depending on it for the *full* *gnome* IMHO is ok. As you must be aware, this does not address the arguments made in the rationale for the TC decision. There is no logical connection between n-m becoming part of GNOME core (as defined upstream) as opposed to just part of GNOME as a whole, and strengthening the gnome metapackage's Recommends to a Depends. I am going to try to get the TC to pass another resolution specifically overruling this further decision by the gnome-core maintainers. I agree with Josselin here completely. Stop the crusade. Describing a unanimous decision of the Technical Committee as a crusade is rude, and IMO shows a lack of contact with reality. Having lost the argument in the TC, the right approach is not to cause more useless work by deliberately undermining the TC's decision, and then to hurl insults when we take exception. You should either allow the TC decision to stand, and implement it honestly (or allow someone else to do so), or attempt to overrule it using a General Resolution. Ian. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#688783: libxen-4.2: debian packages of xen are utterly broken
Package: libxen-4.2 Version: 4.2.0-1 Severity: normal Hello, in xen 4.1 Debian packagers removed blktap uselessly as is documenteted in the blktap bug. in xen 4.2 qemu-dm is removed. This removes any reasonable way to access disks and reserves Debian Xen for diskless DomU use. Essentially Debian Xen packages are now useless. -- System Information: Debian Release: wheezy/sid APT prefers testing APT policy: (910, 'testing'), (900, 'stable'), (410, 'unstable'), (200, 'experimental'), (150, 'precise-updates'), (150, 'precise-security'), (150, 'precise') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.5-trunk-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) (ignored: LC_ALL set to en_US.UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages libxen-4.2 depends on: ii libc6 2.13-35 ii liblzma5 5.1.1alpha+20120614-1 ii zlib1g1:1.2.7.dfsg-13 libxen-4.2 recommends no packages. libxen-4.2 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#688772: gnome Depends network-manager-gnome
10. We therefore formally reprimand Josselin Mouette. We consider his behaviour deliberately obstructive and obtuse. Is that really necessary? I mean, if this new resolution gets approved, wouldn't the Tech Committee have already succeeded in embarrassing the GNOME team in front of the rest of the Debian project without the need to rudely call out an individual? Jeremy Bicha -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#688785: xbmc: Fatal: can't open /dev/urandom: Bad address
Package: xbmc Version: 2:11.0~git20120510.82388d5-1 Severity: grave I installed xbmc and ran xmbc from the command-line, but it crashed. jak@jak-thinkpad:~$ xbmc Fatal: can't open /dev/urandom: Bad address Aborted (core dumped) find: /home/jak/.xbmc/: Datei oder Verzeichnis nicht gefunden Crash report available at /home/jak/xbmc_crashlog-20120925_182815.log jak@jak-thinkpad:~$ cat /home/jak/xbmc_crashlog-20120925_182815.log ## XBMC CRASH LOG ### SYSTEM INFO Date: Tue Sep 25 18:28:15 CEST 2012 XBMC Options: Arch: x86_64 Kernel: Linux 3.2.0-3-amd64 #1 SMP Mon Jul 23 02:45:17 UTC 2012 Release: Distributor ID: Debian Description:Debian GNU/Linux unstable (sid) Release:unstable Codename: sid ## END SYSTEM INFO ## ### STACK TRACE # = Core file: /home/jak/core (2012-09-25 18:28:15.220621179 +0200) = [New LWP 17855] [Thread debugging using libthread_db enabled] Using host libthread_db library /lib/x86_64-linux-gnu/libthread_db.so.1. Core was generated by `/usr/lib/xbmc/xbmc.bin'. Program terminated with signal 6, Aborted. #0 0x7f6294530475 in *__GI_raise (sig=optimized out) at ../nptl/sysdeps/unix/sysv/linux/raise.c:64 Thread 1 (Thread 0x7f629efcc7a0 (LWP 17855)): #0 0x7f6294530475 in *__GI_raise (sig=optimized out) at ../nptl/sysdeps/unix/sysv/linux/raise.c:64 #1 0x7f62945336f0 in *__GI_abort () at abort.c:92 #2 0x7f629a428174 in _gcry_logv (level=40, fmt=0x7f629a48cd89 can't open %s: %s\n, arg_ptr=0x7fff28d72608) at misc.c:141 #3 0x7f629a428604 in _gcry_log_fatal (fmt=optimized out) at misc.c:229 #4 0x7f629a46bc88 in open_device (name=0x7f629a48c881 /dev/urandom) at rndlinux.c:66 #5 open_device (name=0x7f629a48c881 /dev/urandom) at rndlinux.c:60 #6 0x7f629a46bf50 in _gcry_rndlinux_gather_random (add=0x7f629a469550 add_randomness, origin=RANDOM_ORIGIN_SLOWPOLL, length=120, level=1) at rndlinux.c:122 #7 0x7f629a4692d0 in read_random_source (orgin=optimized out, length=optimized out, level=optimized out) at random-csprng.c:1283 #8 0x7f629a46a174 in random_poll () at random-csprng.c:1109 #9 read_pool (level=0, length=8, buffer=0x7f629a69b8e4 ) at random-csprng.c:1003 #10 _gcry_rngcsprng_randomize (buffer=0x7f629a69b8e4, length=8, level=optimized out) at random-csprng.c:551 #11 0x7f629a46a8ed in _gcry_rngcsprng_create_nonce (buffer=0x7fff28d72bcf, length=1) at random-csprng.c:1377 #12 0x7f6291f148d3 in wrap_gcry_rnd_init (ctx=optimized out) at rnd.c:39 #13 0x7f6291ebfd19 in _gnutls_rnd_init () at random.c:39 #14 0x7f6291eaefc5 in gnutls_global_init () at gnutls_global.c:236 #15 0x7f629d26238b in MHD_init () at daemon.c:2727 #16 0x7f629eee5f80 in ?? () from /lib64/ld-linux-x86-64.so.2 #17 0x7f629eee6077 in ?? () from /lib64/ld-linux-x86-64.so.2 #18 0x7f629eed8b2a in ?? () from /lib64/ld-linux-x86-64.so.2 #19 0x0001 in ?? () #20 0x7fff28d745a8 in ?? () #21 0x in ?? () # END STACK TRACE ### # LOG FILE ## Logfile not found in the usual place. Please attach it seperately. Use pastebin.com or similar for forums or IRC. ### END LOG FILE END XBMC CRASH LOG # -- System Information: Debian Release: wheezy/sid APT prefers unstable APT policy: (990, 'unstable'), (500, 'unstable'), (500, 'testing'), (500, 'stable'), (100, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.2.0-3-amd64 (SMP w/4 CPU cores) Locale: LANG=de_DE.utf8, LC_CTYPE=de_DE.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages xbmc depends on: ii fonts-liberation [ttf-liberation] 1.07.2-5 ii mesa-utils 8.0.1-2+b3 ii python 2.7.3-2 ii python-imaging 1.1.7-4 ii python-support 1.0.15 ii ttf-dejavu-core2.33-3 ii x11-utils 7.7~1 ii xbmc-bin 2:11.0~git20120510.82388d5-1+b1 Versions of packages xbmc recommends: pn python-qt3 none xbmc suggests no packages. -- no debconf information -- Julian Andres Klode - Debian Developer, Ubuntu Member See http://wiki.debian.org/JulianAndresKlode and http://jak-linux.org/. pgpgiX5e8JTUP.pgp Description: PGP signature
Bug#637380: kde-plasma-desktop: Weather-plasma : Clear (sky) word is translated with Effacer in french language
Hi, I think this bug is now corrected in the testing version, as I see « Clair » (I am french too). Could you please confirm it is OK for you too, so we can close the bug ? Regards, Adrien -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#688784: Remount persistence filesystems read-only before shutdown
Package: live-config
Version: 3.0.5-1
Severity: grave
Tags: patch
Hi
Persistence filesystems have to be remounted readonly on shutdown or
reboot to avoid data corruption. The attached patch fixes this problem.
The commit message contains more details.
I set the severity to grave as this should be fixed before wheezy as it
can lead to data corruption.
Gaudenz
-- System Information:
Debian Release: wheezy/sid
APT prefers testing
APT policy: (800, 'testing'), (700, 'unstable'), (50, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 3.5-trunk-amd64 (SMP w/2 CPU cores)
Locale: LANG=de_CH.UTF-8, LC_CTYPE=de_CH.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
From 4579aadaf3ae7af7d4a8c6ba67fb1c6d93a4fa0d Mon Sep 17 00:00:00 2001
From: Gaudenz Steinlin gaud...@debian.org
Date: Tue, 25 Sep 2012 18:21:40 +0200
Subject: [PATCH] Remount persistence filesystem readonly on shutdown
All filesystems belonging to a persistence layer must be remounted
readonly to avoid data corruption. The filesystems cannot be unmounted
because they are still in use by the union mount. The sync call ensures
that all data is written to disk before shutdown or reboot. Remounting
by itself does not sync data to disk.
This code does not abort if remounting fails. We can't do much about
it anywhy at this stage.
---
bin/boot-init.sh | 14 +-
1 file changed, 13 insertions(+), 1 deletion(-)
diff --git a/bin/boot-init.sh b/bin/boot-init.sh
index ba99107..a500dff 100755
--- a/bin/boot-init.sh
+++ b/bin/boot-init.sh
@@ -154,7 +154,19 @@ do
cache_path ${path}
done
-mount -o remount,ro /live/overlay /dev/null 21
+mount -o remount,ro /live/overlay /dev/null 21 || true
+
+# remount all persistency mounts read only
+if [ -d /live/persistence ]
+then
+ for mp in $(ls /live/persistence)
+ do
+ mount -o remount,ro /live/persistence/${mp} /dev/null 21 || true
+ done
+
+ # sync all data to disk to make sure persistency is in a consistent state
+ sync
+fi
# Check if we need to eject the drive
if grep -qs cdrom-detect/eject=false /proc/cmdline || \
--
1.7.10.4
Bug#688786: cryptsetup: crypttab(5) manual page should contain information regarding UUID
Package: cryptsetup Version: 2:1.4.3-2 Severity: normal Dear Maintainer, the manual page regarding crypttab (man 5 crypttab) misses information on how to specify a device in UUID format. Redhat documents this as follows: https://access.redhat.com/knowledge/docs/en- US/Red_Hat_Enterprise_Linux/5/html/Installation_Guide/ch29s04s06.html It would be very helpful to others to include that information. -- Package-specific info: -- /proc/cmdline BOOT_IMAGE=/boot/vmlinuz-3.1.0-1-amd64 root=UUID=f589e608-5c42-4a91-8d3c-fd0b75ec67fe ro quiet -- /etc/crypttab # target name source device key file options homeUUID=6f3e71b5-39db-4595-9eb2-fce1cfbb5b4d none luks -- /etc/fstab # /etc/fstab: static file system information. # # Use 'blkid' to print the universally unique identifier for a # device; this may be used with UUID= as a more robust way to name devices # that works even if disks are added and removed. See fstab(5). # # file system mount point type options dump pass proc/proc procdefaults0 0 # / was on /dev/sdb1 during installation UUID=f589e608-5c42-4a91-8d3c-fd0b75ec67fe / ext4 errors=remount-ro 0 1 UUID=4721d999-961e-4965-bd1b-87cfebfb59af /home ext4 defaults,user_xattr 0 0 /dev/sr0/media/cdrom0 udf,iso9660 user,noauto 0 0 -- lsmod Module Size Used by isofs 35131 0 hmac 12835 0 nls_utf8 12456 0 cifs 238004 0 ip6table_filter12540 0 ip6_tables 22175 1 ip6table_filter iptable_filter 12536 0 ip_tables 22042 1 iptable_filter ebtable_nat12580 0 ebtables 26235 1 ebtable_nat x_tables 19028 5 ebtables,ip_tables,iptable_filter,ip6_tables,ip6table_filter parport_pc 22364 0 ppdev 12763 0 lp 17149 0 parport31858 3 lp,ppdev,parport_pc bnep 17567 2 rfcomm 33622 0 bluetooth 119290 10 rfcomm,bnep acpi_cpufreq 12935 1 mperf 12453 1 acpi_cpufreq rfkill 19012 2 bluetooth cpufreq_powersave 12454 0 cpufreq_stats 12866 0 cpufreq_conservative13147 0 inet_diag 17144 1 cpufreq_userspace 12576 0 autofs427582 2 snd_hrtimer12604 1 pci_stub 12429 1 vboxpci19103 0 vboxnetadp 25443 0 vboxnetflt 23608 0 vboxdrv 186009 3 vboxnetflt,vboxnetadp,vboxpci binfmt_misc12957 1 fuse 61981 1 nfsd 259717 2 nfs 312135 0 nfs_acl12511 2 nfs,nfsd auth_rpcgss37143 2 nfs,nfsd fscache36739 2 nfs,cifs lockd 67328 2 nfs,nfsd sunrpc173516 6 lockd,auth_rpcgss,nfs_acl,nfs,nfsd sha256_generic 16797 4 cryptd 14517 0 aes_x86_64 16796 64 aes_generic33026 1 aes_x86_64 cbc12754 32 dm_crypt 22586 2 w83627ehf 31089 0 hwmon_vid 12430 1 w83627ehf coretemp 12943 0 loop 22597 0 firewire_sbp2 18077 0 kvm_intel 121792 0 kvm 278176 1 kvm_intel snd_hda_codec_hdmi 26548 1 snd_hda_codec_realtek 272344 1 snd_usb_audio 84796 0 snd_usbmidi_lib23373 1 snd_usb_audio uinput 17440 1 mxm_wmi12473 0 snd_ice171253863 1 evdev 17562 15 snd_cs8427 13325 1 snd_ice1712 snd_i2c13228 2 snd_cs8427,snd_ice1712 snd_ice17xx_ak4xxx 12716 1 snd_ice1712 snd_ak4xxx_adda13382 2 snd_ice17xx_ak4xxx,snd_ice1712 snd_ac97_codec106899 1 snd_ice1712 snd_hda_intel 26182 2 snd_mpu401_uart13507 1 snd_ice1712 snd_hda_codec 72920 3 snd_hda_intel,snd_hda_codec_realtek,snd_hda_codec_hdmi snd_pcm_oss41081 0 snd_seq_midi 12848 0 snd_seq_midi_event 13316 1 snd_seq_midi snd_mixer_oss 17916 3 snd_pcm_oss snd_hwdep 13186 2 snd_hda_codec,snd_usb_audio radeon648863 2 snd_rawmidi23060 3 snd_seq_midi,snd_mpu401_uart,snd_usbmidi_lib snd_pcm63744 7 snd_pcm_oss,snd_hda_codec,snd_hda_intel,snd_ac97_codec,snd_ice1712,snd_usb_audio,snd_hda_codec_hdmi sg 25874 0 psmouse55543 0 snd_page_alloc 13003 2 snd_pcm,snd_hda_intel pcspkr 12579 0 snd_seq45093 3 snd_seq_midi_event,snd_seq_midi ac97_bus 12510 1 snd_ac97_codec serio_raw 12850 0
Bug#688772: gnome Depends network-manager-gnome
Ian, I consider myself an uninvolved party in this matter; I don't really want network-manager installed on my systems, but I'm not particularly keyed up about it. I'm not on the TC. I have been following the issue enough to have an opinion. I'm reasonably good at process issues, and think I understand the process issues involved here. I'm disappointed to immediately see this discussion turn to assumptions of malice and reprimands. Would you be willing to consider how the TC as an organization and you in particular might learn from this incident and be more effective in the future. When I find something like this happens to me, I try and put myself in the head of the other person and ask what they might be doing. When I do that I hear I find a couple of possibilities. One is that the gnome-meta maintainer is trying to meet the letter of your intent while trying to work around it. Would you be willing to set that aside for a moment and think about other possibilities. Another possibility is that the gnome-meta folks have been confused and frustrated by this whole discussion. They don't see what the big deal about n-m is and they want to provide a good experience for the users. They received a decision they don't really like from the TC with some complex rationale and so they tried to follow through that rationale and balance their goals against the rationale the TC stated as best they could. In point 3 of your resolution, one of the points you make is that users don't have an alternative because only the most minimal gnome package (gnome-session) can be installed without pulling in n-m. I think a reasonable person could read that section of the resolution and conclude that if n-m were pushed into more inclusive meta-packages, then the argument might be different. Now, I'll admit that there was probably some searching going on for how to fit some goals into what the TC proposed. I'll admit that there might have been some ask for forgiveness not permission going on. But all those things are normal with frustration. Would you be willing to consider 1) focusing on accomplishing the specific immediate goal you want--perhaps points 1-6 in your proposed resolution. And then later having a serious discussion about how you and the TC can write resolutions that are more likely to achieve the long-term goals of the TC while avoiding frustration. I would be happy to contribute some thoughts there if desired. Thanks for considering my requests, and thanks for continuing to spend the time to follow this issue. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#688788: [INTL:pl] Updated Polish debconf translation
Package: fglrx-driver Severity: wishlist Tags: l10n patch Hi! Please update Polish debconf translation with the attached file. Thanks in advance, -- Michał Kułach pl.po Description: Binary data
Bug#688787: firmware-linux-nonfree: Include firmware for various TeVii DVB-S cards/drivers
Source: firmware-linux-nonfree Severity: normal Dear Maintainers, Could the following firmwares be added to linux-firmware-nonfree (or another package maybe?): - dvb-fe-ds3000.fw - dvb-usb-s660.fw These are needed for proper operation of DVB-S cards from TeVii. Supported cards include TeVii's S470, S471, S480 and S660. Both firmwares are readily on TeVii's main website [1] and are distributed in 2 tarballs [2][3]. All the drivers for those cards are already included in the upstream git tree, only the firmwares are missing. Thank you for considering this request. [1] http://www.tevii.com/Support.asp [2] http://www.tevii.com/dvb-fe-ds3000.rar [3] http://www.tevii.com/dvb-usb.rar -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#688789: /sbin/lvcreate: lvcreate/lvremove --quiet are not quiet
Package: lvm2 Version: 2.02.95-4 Severity: normal File: /sbin/lvcreate Every invocation of lvcreate --quiet or lvremove --quiet from a /bin/sh script called from bash outputs: File descriptor 3 (/usr/share/bash-completion/completions) leaked on lvcreate invocation. Parent PID 32675: /bin/sh Logical volume backup created or: File descriptor 3 (/usr/share/bash-completion/completions) leaked on lvremove invocation. Parent PID 32675: /bin/sh Logical volume backup successfully removed Having wasted quite a bit of time investigating this error message at least I know that is apparently meaningless and can be safely ignored. Perhaps this will be useful to other people encountering this error. Thanks, Roger -- System Information: Debian Release: wheezy/sid APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 3.2.0-3-amd64 (SMP w/8 CPU cores) Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages lvm2 depends on: ii dmsetup 2:1.02.74-4 ii initscripts 2.88dsf-32 ii libc6 2.13-35 ii libdevmapper-event1.02.1 2:1.02.74-4 ii libdevmapper1.02.12:1.02.74-4 ii libreadline5 5.2-11 ii libudev0 175-7 ii lsb-base 4.1+Debian7 lvm2 recommends no packages. lvm2 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#688757: pvmove onto disk with different sector size hazardous
On 9/25/12 11:35 AM, Bastian Blank wrote: Nope. That is perfectly fine. Yep sorry, I misunderstood what pvmove was doing. -Eric -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#688757: pvmove onto disk with different sector size hazardous
On Tue, Sep 25, 2012 at 02:45:47PM +0200, Daniel Pocock wrote: I have marked this `severe' because it has a high probability of filesystem corruption and drives with 4096 byte sectors are likely to become much more widespread. This is a local problem. You have setup a filesystem with 512 bytes as block size (xfs I presume) and expect it to work on larger blocks? Just don't use xfs or kill the maintainer of xfs tools for still using such tiny blocks. I recently purchased a 3TB drive and created one big 3TB partition for lvm Which brand and model? All large disks I obtained in the last year shows 512 bytes sectors. Many errors appeared during the pvmove operation And this would be? The old disk has 512 byte sectors and the new disk has 4096 byte sectors. Please show smartctl -i $device. It appears that pvmove is potentially a lot more dangerous than the man page suggests. Although they were mounted during the pvmove, they were not in use (they are backup filesystems and they only get written to on demand). If they had open files at the time, I suspect that corruption would have occurred. I doubt that, because the write would have been canceled. Some potential ideas: a) pvmove should check sector sizes and require --force if there is a mismatch Nope. This is up to the admin. Also lvm does not know about the filesystem. Bastian -- Vulcans do not approve of violence. -- Spock, Journey to Babel, stardate 3842.4 -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#688757: pvmove onto disk with different sector size hazardous
On Tue, Sep 25, 2012 at 10:36:05AM -0500, Eric Sandeen wrote: aside from all that, pvmove of a mounted filesystem sounds terribly dangerous, though not related to the fsblocksize too small error you ran into. Nope. That is perfectly fine. Bastian -- I've already got a female to worry about. Her name is the Enterprise. -- Kirk, The Corbomite Maneuver, stardate 1514.0 -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#688790: rsnapshot: WARNING prefix missing in some warning messages
Package: rsnapshot Version: 1.3.1-3 Severity: minor Tags: patch Some warnings are logged using the print_warn function, which in turns should call log_warn for the message to be saved in the log file. However, print_warn calls log_msg instead, so the WARNING prefix that would be added by log_warn is missing in the log file. Fixing this is quite easy: --- rsnapshot.~1~ 2011-07-09 16:39:45.0 +0200 +++ rsnapshot 2012-09-25 11:55:41.0 +0200 @@ -2032,7 +2032,7 @@ } # write to log - log_msg($str, $level); + log_warn($str, $level); } # accepts string, and level -- System Information: Debian Release: wheezy/sid APT prefers testing APT policy: (500, 'testing'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 3.2.0-3-amd64 (SMP w/4 CPU cores) Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968) Shell: /bin/sh linked to /bin/dash Versions of packages rsnapshot depends on: ii liblchown-perl 1.01-1+b2 ii logrotate 3.8.1-4 ii perl5.14.2-13 ii rsync 3.0.9-3 Versions of packages rsnapshot recommends: ii openssh-client [ssh-client] 1:6.0p1-3 rsnapshot suggests no packages. -- Configuration Files: /etc/cron.d/rsnapshot changed [not included] -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#688598: [Pkg-xfce-devel] Bug#688598: xfce4-power-manager: Notification icon actions are not configurable
On mar., 2012-09-25 at 16:37 +0200, José Salavert Torres wrote: El 25/09/12 15:33, Yves-Alexis Perez escribió: On mar., 2012-09-25 at 15:21 +0200, José Salavert Torres wrote: 1) There are two scripts to suspend from console: pm-suspend and pm-suspend-hybrid , both in package pm-utils. When I suspend using xfpm using the notification area icon, I have found that the pm-suspend script is called by default . That script does not work on my machine, but if I rename pm-suspend-hybrid to pm-suspend the suspend process using xfpm works again. Note that pm-suspend-hybrid is just suspending after taking a ram snapshot for hibernation. So what you really means, I guess, is that suspend fails while hibernation works, and that's an issue in your kernel (or X drivers or something). pm-suspend-hybrid is just suspending my device, not hibernating, and you can not unplug the laptop using this method. This suspend method is an hybrid. The wake up process is also way faster than full hibernation (seconds vs about a minute or more). That looks really weird. You might want to investigate exactly what pm-suspend-hybrid is doing, and report a bug against pm-utils. But renaming a file is not a user friendly way of selecting the suspend method. Maybe it would be possible to allow the user to select the suspend method (pm-suspend or pm-suspend-hybrid) in the applet, is there only one kind of dbus suspend call available? If so maybe we should notify this to upower package mantainer. A quick look in dbus methods offered by upower shows that it only have suspend() and hibernate(), yes. How should I notify then the upower mantainers, should I open another bug? How can we involve them in this discussion? You can clone the bug and reassign the clone to the upower package, I guess. Or just reassign this one, since it's not really a problem in xfpm here. 2) This is a wish. I would like to setup the xfpm to suspend my computer when plugged and hybernate when running on batteries. Is this possible? Well, you can configure various options for when you're on AC and when you're on battery in the settings interface. Yes but it seems that I can not specify a different method for each: plugged - suspend unplugged - hibernate There are more options in the advanced tab, but the inactivity option seems to be shared. Maybe this is different in the lastest version of XFCE. We can split the two topics, because the second has severity wishlist and should be in another bugreport. Yeah, and to be honest, I wouldn't hope too much, we don't have any news from the upstream developer since quite a while… Regards, -- Yves-Alexis signature.asc Description: This is a digitally signed message part
Bug#663740: python-zeitgeist: Drop obsolete python-gobject dependency
tags 663740 + upstream thanks On Tue, 13 Mar 2012 at 19:21:51 +0100, Martin Pitt wrote: Packages should be migrated from the obsolete static bindings (gobject, glib, gtk) to the gobject-introspection bindings (from gi.repository import GObject), and update their dependencies to python-gi (or -dev for build deps). This is harder than it looks, unfortunately. However, it seems that python-zeitgeist uses neither, so as far as I can see the dependency should just be dropped. It uses glib (python-gobject-2) indirectly. In client.py: import dbus.mainloop.glib dbus.mainloop.glib.DBusGMainLoop(set_as_default=True) This is really bad behaviour: using a library should not change global state! If it was acceptable to do this, python-dbus would do it for you already. Unfortunately, changing it is an API change for library users: see https://bugs.freedesktop.org/show_bug.cgi?id=48904. Maybe python-zeitgeist has so few users that nobody cares, but it needs discussing upstream. S -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#688675: Отв.: Bug#688675 closed by Yves-Alexis Perez cor...@debian.org (Re: [Pkg-xfce-devel] Bug#688675: Please depend on vnc4server)
No problem. I can install it myself. Everybody can do it. But it seems a bit ugly: to provide something called VNC server partially. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#686033: libgl1-nvidia-glx: 304.37-1 libgl1-nvidia-glx:i386, removes libgl1-nvidia-glx (amd64) and Nvidia driver
On 2012-09-23 16:03, Ralf Jung wrote: Hi, with the 304 drivers in current unstable, this bug even means that 32bit apps get no acceleration at all since the ia32 packages have already been removed. I can confirm that the patch by you, Andreas, is working fine. The problems with the conffile are caused by a bug in dpkg [1] and there are other packages triggering it, like libpam-modules. Which dpkg versions are affected? Would it be appropriate for the NVidia packagers to do an NMU on libxvmc to fix this situation? Note that I am not speaking about Wheezy here, but about the current broken status of Sid. I have a NMUdiff attached to http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=687373 with no response so far. I'm *not* favoring a NMU of this if we can't fix it in wheezy. I'm thinking about another solution ... for wheezy. Andreas PS: a NMU to experimental would be OK for me -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#688772: gnome Depends network-manager-gnome
Sam Hartman writes (Bug#688772: gnome Depends network-manager-gnome): I'm disappointed to immediately see this discussion turn to assumptions of malice and reprimands. Josselin described the TC decision as a crusade in his upload. I think that is sufficient for me to infer malice. One is that the gnome-meta maintainer is trying to meet the letter of your intent while trying to work around it. Right... Would you be willing to set that aside for a moment and think about other possibilities. OK, fair enough ... Another possibility is that the gnome-meta folks have been confused and frustrated by this whole discussion. They don't see what the big deal about n-m is and they want to provide a good experience for the users. They received a decision they don't really like from the TC with some complex rationale and so they tried to follow through that rationale and balance their goals against the rationale the TC stated as best they could. I don't think you could read the rationale that way. At least, not without a lot of wilful blindness. It clearly explains that the biggest part of the problem was that users who had gnome but not n-m in squeeze would get n-m when upgrading to wheezy: 3. [...] users who have gnome or gnome-core installed but have removed or never installed network-manager will have network-manager installed during an upgrade from squeeze. 4. [ description of why network-manager can be problematic ] 5. The Technical Committee believes that this will cause undesireable behavior for upgrades from squeeze, and (of somewhat lesser importance) will make it more difficult than necessary for GNOME users to swap network management components, something for which there appears to be noticable demand. We therefore believe that network-manager should be moved to Recommends in gnome-core. I think a reasonable person could read that section of the resolution and conclude that if n-m were pushed into more inclusive meta-packages, then the argument might be different. As I write I don't understand why, if this idea was thought to be a good one, the maintainers didn't suggest this approach to the TC. It's not as if there wasn't time, and it's hardly a difficult thing to think of. The real answer is of course that if anyone had suggested this as a possibility our resolution would have unambiguously ruled it out. So the purpose of subverting the decision was only served by producing this change afterwards. Now, I'll admit that there was probably some searching going on for how to fit some goals into what the TC proposed. I'll admit that there might have been some ask for forgiveness not permission going on. But all those things are normal with frustration. What kind of emotional state do you think I should have after the legitimate and unanimous authority of the TC has been undermined in this way ? Perhaps I would be frustrated. Would you be willing to consider 1) focusing on accomplishing the specific immediate goal you want--perhaps points 1-6 in your proposed resolution. To be honest I don't expect to be able to get a 4:1 majority in the TC in favour of publicly denouncing Josselin. (Since the resolution as a whole overrules a maintainer, that would be necessary.) But I wanted to put my feelings, which IMO are legitimate, on the record. And then later having a serious discussion about how you and the TC can write resolutions that are more likely to achieve the long-term goals of the TC while avoiding frustration. Normally we write our resolutions with the intent that people will not subvert them, or work against their intent. That is after all required by the Constitution. If we need to make them watertight against malicious and lawyerish interpretation, then we will need to anticipate every way in which the maintainers might try to subvert our intent. Along the lines of point 6 in my proposal. I think it would be very rude to routinely write that kind of thing in overruling resolutions. It it amounts to assuming and anticipating bad faith on the part of the overruled maintainer. I would be happy to contribute some thoughts there if desired. Please do. Ian. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#667565: virt-viewer: please compile with Spice support
Package: virt-viewer Version: 0.5.4-1 Followup-For: Bug #667565 Hello, virt-viewer cannot view my VMs because of this omission. -- System Information: Debian Release: wheezy/sid APT prefers testing APT policy: (910, 'testing'), (900, 'stable'), (410, 'unstable'), (200, 'experimental'), (150, 'precise-updates'), (150, 'precise-security'), (150, 'precise') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.5-trunk-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) (ignored: LC_ALL set to en_US.UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages virt-viewer depends on: ii libatk1.0-0 2.4.0-2 ii libc6 2.13-35 ii libcairo-gobject2 1.12.2-2 ii libcairo2 1.12.2-2 ii libgdk-pixbuf2.0-0 2.26.1-1 ii libglib2.0-02.32.3-1 ii libgtk-3-0 3.4.2-3 ii libgtk-vnc-2.0-00.5.0-3 ii libgvnc-1.0-0 0.5.1-1 ii libpango1.0-0 1.30.0-1 ii libvirt00.10.1-2 ii libxml2 2.8.0+dfsg1-5 virt-viewer recommends no packages. Versions of packages virt-viewer suggests: ii netcat-openbsd [netcat] 1.105-7 ii netcat-traditional [netcat] 1.10-40 -- 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#685527: unblock: packagekit/0.7.6-1
These are the only changes in 0.7.6 which matter for Debian (except for one pkcon fix you left out) - all other patches aren't compiled in. I can prepare a 0.7.5-2+deb7u1 version, if these changes aren't accepted, but I would prefer the other solution, if this is still possible. If not, I'll upload the fix release in ~2.5weeks (I won't have that much time before (away on a conference, and much university stuff to do)), because some of the fixes (the one you listed) are absolutely required. Cheers, Matthias 2012/9/25 Moritz Muehlenhoff j...@inutil.org: On Mon, Sep 03, 2012 at 03:46:10PM +0200, Matthias Klumpp wrote: Okay, breaking down the changes: Since the review resources of the release managers are scarce and since we should get the security fixes into Wheezy, what about preparing a 0.7.5-2+deb7u1 upload to testing-proposed-updates with the following changes only: Check for CancelBackgroundTransactions setting again: Respect the CancelBackgroundSetting setting again See http://gitorious.org/packagekit/packagekit/commit/1423e638600e7fd045b1ced0d584d59519610748 Do not allow the client to overwrite files when downloading packages: Pretty obvious what this does :-) Both a bugfix and a security enhancement. See http://gitorious.org/packagekit/packagekit/commit/a4a0210809b7bfda0df6874fe39b86b66590ef26 Fix several return values in pkcon when there is an error: Previously return codes weren't correct/weren't set on failure. See http://gitorious.org/packagekit/packagekit/commit/338842edf1a9d65b8708d514ab0f64fb684cf724 Ignore accept-eula in pk-transaction-run: Bugfix avoiding potential crash described in https://bugs.freedesktop.org/show_bug.cgi?id=53532 See http://gitorious.org/packagekit/packagekit/commit/771d28c110007d954c9ae65c5287fe1ee186589a Fix segfault in pkcon when user does ctrl-d at the package prompt: Kills this bug: https://bugzilla.redhat.com/show_bug.cgi?id=840342 See http://gitorious.org/packagekit/packagekit/commit/1594117d750e766309d3ff487bad3e39936a132c aptcc: Don't use tempfile with fixed name for conffiles: Resolves security issue in Debian, tracked as RC bug #678189 See http://gitorious.org/packagekit/packagekit/commit/e6e33f54dcc9b0058134e0d2584c2ee110ca0340 Fix a crash where NetworkManager is restarted whilst packagekitd is running: Important fix for packagekitd, I already got this reported by Debian users too. (Although it happens in a rare case) See http://gitorious.org/packagekit/packagekit/commit/1746179e446fa652027c673cff0f0f5e5daccd99 Cheers, Moritz -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#644157: racoon: kerberos authentication when responder to windows causes segfault at end of phase 1
Hello, I was just wondering if this will be fixed in the near future. It is a bug exactly as Andre has described. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#688791: unblock: elfutils/0.153-2
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: unblock
Hi,
I would like to move the elfutils version 0.153-2 to testing.
Note that the version 0.152-1 is currently in testing, so this
is a new upstream version.
The version in testing has an RC bug (#684825). I could
fix that instead if you want. But I got the feeling that
you would be open to move 0.153-2 to testing.
I would really prefer the 0.153-2 to move to testing.
The debdiff between 0.153-1 and 0.153-2 is attached
if that's useful at all.
Kurt
diff -Nru elfutils-0.153/debian/changelog elfutils-0.153/debian/changelog
--- elfutils-0.153/debian/changelog 2012-02-25 01:48:58.0 +0100
+++ elfutils-0.153/debian/changelog 2012-09-18 21:40:06.0 +0200
@@ -1,3 +1,15 @@
+elfutils (0.153-2) unstable; urgency=low
+
+ * Make it actually build properly using build-arch. (Closes: #684528)
+ * Call rwlock_unlock() before rwlock_fini(). The lock was still held
+causing problems on kfreebsd. (Closes: #662041)
+ * Don't exclude sh_type = SHT_NUM from stripping, it's set to
+SHT_MIPS_DWARF on mips. (Closes: #662041)
+ * readelf -w didn't show the content of debug sections on mips
+because sh_type was set to SHT_MIPS_DWARF.
+
+ -- Kurt Roeckx k...@roeckx.be Tue, 18 Sep 2012 21:12:08 +0200
+
elfutils (0.153-1) unstable; urgency=low
[ Jonathan Nieder jrnie...@gmail.com ]
diff -Nru elfutils-0.153/debian/patches/alldts.patch elfutils-0.153/debian/patches/alldts.patch
--- elfutils-0.153/debian/patches/alldts.patch 2012-02-24 21:21:41.0 +0100
+++ elfutils-0.153/debian/patches/alldts.patch 2012-09-18 21:53:21.0 +0200
@@ -1,5 +1,6 @@
From: Kurt Roeckx k...@roeckx.be
Subject: Set up the test environment so that we actually test the new library
+Applied-Upstream: commit:593f2af73d971bdc9dcc06622d529e7848c31f57
--- a/tests/run-alldts.sh.orig 2012-02-24 20:17:17.0 +
+++ a/tests/run-alldts.sh 2012-02-24 20:17:28.0 +
diff -Nru elfutils-0.153/debian/patches/elf_end_unlock.patch elfutils-0.153/debian/patches/elf_end_unlock.patch
--- elfutils-0.153/debian/patches/elf_end_unlock.patch 1970-01-01 01:00:00.0 +0100
+++ elfutils-0.153/debian/patches/elf_end_unlock.patch 2012-09-18 21:55:20.0 +0200
@@ -0,0 +1,17 @@
+From: Kurt Roeckx k...@roeckx.be
+Subject: Call rwlock_unlock() before rwlock_fini()
+Applied-Upstream: commit:495501611820a9d5c462fda56045c146f7b922d7
+Bug-Debian: http://bugs.debian.org/662041
+
+diff --git a/libelf/elf_end.c b/libelf/elf_end.c
+index 5112eae..6392eaf 100644
+--- a/libelf/elf_end.c
b/libelf/elf_end.c
+@@ -241,6 +241,7 @@ elf_end (elf)
+ munmap (elf-map_address, elf-maximum_size);
+ }
+
++ rwlock_unlock (elf-lock);
+ rwlock_fini (elf-lock);
+
+ /* Finally the descriptor itself. */
diff -Nru elfutils-0.153/debian/patches/mips_readelf_w.patch elfutils-0.153/debian/patches/mips_readelf_w.patch
--- elfutils-0.153/debian/patches/mips_readelf_w.patch 1970-01-01 01:00:00.0 +0100
+++ elfutils-0.153/debian/patches/mips_readelf_w.patch 2012-09-18 21:54:18.0 +0200
@@ -0,0 +1,22 @@
+From: Kurt Roeckx k...@roeckx.be
+Subject: Make readelf -w output debug information on mips
+Bug-Debian: http://bugs.debian.org/662041
+Forwarded: not-needed
+
+Upstreams wants a change where this is handled by a hook that needs
+to be filled in by the backend for the arch.
+
+Index: elfutils-0.153/src/readelf.c
+===
+--- elfutils-0.153.orig/src/readelf.c 2012-08-10 22:01:55.0 +0200
elfutils-0.153/src/readelf.c 2012-09-18 21:46:27.0 +0200
+@@ -7364,7 +7364,8 @@
+ GElf_Shdr shdr_mem;
+ GElf_Shdr *shdr = gelf_getshdr (scn, shdr_mem);
+
+- if (shdr != NULL shdr-sh_type == SHT_PROGBITS)
++ if (shdr != NULL (
++ (shdr-sh_type == SHT_PROGBITS) || (shdr-sh_type == SHT_MIPS_DWARF)))
+ {
+ static const struct
+ {
diff -Nru elfutils-0.153/debian/patches/series elfutils-0.153/debian/patches/series
--- elfutils-0.153/debian/patches/series 2012-02-24 23:26:59.0 +0100
+++ elfutils-0.153/debian/patches/series 2012-09-18 21:42:18.0 +0200
@@ -8,3 +8,6 @@
elf_additions.diff
alldts.patch
scanf-format.patch
+elf_end_unlock.patch
+strip_sh_type.patch
+mips_readelf_w.patch
diff -Nru elfutils-0.153/debian/patches/strip_sh_type.patch elfutils-0.153/debian/patches/strip_sh_type.patch
--- elfutils-0.153/debian/patches/strip_sh_type.patch 1970-01-01 01:00:00.0 +0100
+++ elfutils-0.153/debian/patches/strip_sh_type.patch 2012-09-18 21:41:54.0 +0200
@@ -0,0 +1,22 @@
+From: Roland McGrath rol...@hack.frob.com
+Subject: Don't exclude sh_type = SHT_NUM from stripping.
+Origin: upstream, commit:8e8f0be57354d3fa094d0927930dbe1bc1ce8816
+Bug-Debian: http://bugs.debian.org/662041
+
+Needed on mips because sh_type is set to SHT_MIPS_DWARF
+
+index 8b4c0d7..bda192c 100644
+---
Bug#682593: libkipi abi oops
On Tue, Sep 25, 2012 at 15:06:47 +0200, Sune Vuorela wrote: There is 3 possible solutions: 1) hide head in sand and rebuild 'old' dependencies (kamoso, kphotoalbum, digikam) 2) restore abi and rebuild 'new' dependencies (ksnapshot, gwenview) 3) do a full transition of libkipi. I'm leaning towards 1) because it is fewer 'popular' dependencies to rebuild. Note that the package name has changed since squeeze, so there is no partial stabe=testing upgrade issues. only testing=testing issues. and those are there both with 1) and 2); just for different packages. If this doesn't affect upgrades from squeeze I'm ok with 1. Cheers, Julien signature.asc Description: Digital signature
Bug#688792: mysql-server-5.5: error in SQL syntax in postinst
Package: mysql-server-5.5
Version: 5.5.24+dfsg-8
Severity: normal
Dear Maintainer,
* What led up to the situation?
An upgrade in aptitude.
* What exactly did you do (or not do) that was effective (or
ineffective)?
Nothing. mysql appears to be running. However, the failed change looks
signficant.
* What was the outcome of this action?
* What outcome did you expect instead?
An upgrade without errors.
I am running Debian testing in a chroot. I did an upgrade inside of aptitude
yesterday:
[UPGRADE] mysql-server-5.5:i386 5.5.24+dfsg-7 - 5.5.24+dfsg-8
and the logs show
ERROR: 1064 You have an error in your SQL syntax; check the manual that
corresponds to your MySQL server version for the right syntax to use near
'ALTER TABLE user ADD column Show_view_priv enum('N','Y') CHARACTER SET utf8
NOT ' at line 1
[ERROR] Aborting
The offending line appears to be from the mysql postinst:
ross@corn:/var/lib/dpkg/info$ grep Show_view_priv *
mysql-server-5.5.postinst: Show_view_priv='Y',
Create_routine_priv='Y', Alter_routine_priv='Y', \
mysql-server-5.5.postinst:ALTER TABLE user ADD column Show_view_priv
enum('N','Y') CHARACTER SET utf8 NOT NULL DEFAULT 'N'; \
\
Note there is another error about old style --language. That's probably a
separate issue, though it would be good to fix.
In case it helps, here is a fuller log:
Sep 23 15:08:33 corn mysqld_safe[24690]:
Sep 23 15:08:33 corn mysqld_safe[24690]: PLEASE REMEMBER TO SET A PASSWORD FOR
THE MySQL root USER !
Sep 23 15:08:33 corn mysqld_safe[24690]: To do so, start the server, then issue
the following commands:
Sep 23 15:08:33 corn mysqld_safe[24690]:
Sep 23 15:08:33 corn mysqld_safe[24690]: /usr/bin/mysqladmin -u root password
'new-password'
Sep 23 15:08:33 corn mysqld_safe[24690]: /usr/bin/mysqladmin -u root -h corn
password 'new-password'
Sep 23 15:08:33 corn mysqld_safe[24690]:
Sep 23 15:08:33 corn mysqld_safe[24690]: Alternatively you can run:
Sep 23 15:08:33 corn mysqld_safe[24690]: /usr/bin/mysql_secure_installation
Sep 23 15:08:33 corn mysqld_safe[24690]:
Sep 23 15:08:33 corn mysqld_safe[24690]: which will also give you the option of
removing the test
Sep 23 15:08:33 corn mysqld_safe[24690]: databases and anonymous user created
by default. This is
Sep 23 15:08:33 corn mysqld_safe[24690]: strongly recommended for production
servers.
Sep 23 15:08:33 corn mysqld_safe[24690]:
Sep 23 15:08:33 corn mysqld_safe[24690]: See the manual for more instructions.
Sep 23 15:08:33 corn mysqld_safe[24690]:
Sep 23 15:08:33 corn mysqld_safe[24690]: Please report any problems with the
/usr/scripts/mysqlbug script!
Sep 23 15:08:33 corn mysqld_safe[24690]:
Sep 23 15:08:33 corn mysqld_safe[24736]: 120923 15:08:33 [ERROR] An old style
--language value with language specific part detected: /usr/share/mysql/english/
Sep 23 15:08:33 corn mysqld_safe[24736]: 120923 15:08:33 [ERROR] Use
--lc-messages-dir without language specific part instead.
Sep 23 15:08:33 corn mysqld_safe[24736]: 120923 15:08:33 [Note] Plugin
'FEDERATED' is disabled.
Sep 23 15:08:33 corn mysqld_safe[24736]: 120923 15:08:33 InnoDB: The InnoDB
memory heap is disabled
Sep 23 15:08:33 corn mysqld_safe[24736]: 120923 15:08:33 InnoDB: Mutexes and
rw_locks use GCC atomic builtins
Sep 23 15:08:33 corn mysqld_safe[24736]: 120923 15:08:33 InnoDB: Compressed
tables use zlib 1.2.3
Sep 23 15:08:33 corn mysqld_safe[24736]: 120923 15:08:33 InnoDB: Using Linux
native AIO
Sep 23 15:08:33 corn mysqld_safe[24736]: 120923 15:08:33 InnoDB: Initializing
buffer pool, size = 128.0M
Sep 23 15:08:33 corn mysqld_safe[24736]: 120923 15:08:33 InnoDB: Completed
initialization of buffer pool
Sep 23 15:08:33 corn mysqld_safe[24736]: 120923 15:08:33 InnoDB: highest
supported file format is Barracuda.
Sep 23 15:08:33 corn mysqld_safe[24736]: 120923 15:08:33 InnoDB: 1.1.8 started;
log sequence number 5257779
Sep 23 15:08:33 corn mysqld_safe[24736]: 120923 15:08:33 InnoDB: Starting
shutdown...
Sep 23 15:08:35 corn mysqld_safe[24736]: 120923 15:08:35 InnoDB: Shutdown
completed; log sequence number 5257779
Sep 23 15:08:35 corn mysqld_safe[24761]: 120923 15:08:35 [ERROR] An old style
--language value with language specific part detected: /usr/share/mysql/english/
Sep 23 15:08:35 corn mysqld_safe[24761]: 120923 15:08:35 [ERROR] Use
--lc-messages-dir without language specific part instead.
Sep 23 15:08:35 corn mysqld_safe[24761]: 120923 15:08:35 [Note] Plugin
'FEDERATED' is disabled.
Sep 23 15:08:35 corn mysqld_safe[24761]: 120923 15:08:35 InnoDB: The InnoDB
memory heap is disabled
Sep 23 15:08:35 corn mysqld_safe[24761]: 120923 15:08:35 InnoDB: Mutexes and
rw_locks use GCC atomic builtins
Sep 23 15:08:35 corn mysqld_safe[24761]: 120923 15:08:35 InnoDB: Compressed
tables use zlib 1.2.3
Sep 23 15:08:35 corn mysqld_safe[24761]: 120923 15:08:35 InnoDB: Using Linux
native AIO
Sep 23 15:08:35 corn mysqld_safe[24761]: 120923 15:08:35 InnoDB: Initializing
buffer pool, size =
Bug#688793: unblock: obnam/1.1-1.1
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: unblock
Please unblock package obnam
The NMU uploaded to unstable fixes an RC bug. The patch is taken from
the upstream bazaar repository. There are no other changes beside this
bugfix and upstream test case verifying the bugfix passes.
Thanks Gaudenz
unblock obnam/1.1-1.1
-- System Information:
Debian Release: wheezy/sid
APT prefers testing
APT policy: (800, 'testing'), (700, 'unstable'), (50, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 3.5-trunk-amd64 (SMP w/2 CPU cores)
Locale: LANG=de_CH.UTF-8, LC_CTYPE=de_CH.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
only in patch2:
unchanged:
--- obnam-1.1.orig/tests/encryption-replaces-key.script
+++ obnam-1.1/tests/encryption-replaces-key.script
@@ -0,0 +1,41 @@
+#!/bin/sh
+# Copyright 2011 Lars Wirzenius
+#
+# This program is free software: you can redistribute it and/or modify
+# it under the terms of the GNU General Public License as published by
+# the Free Software Foundation, either version 3 of the License, or
+# (at your option) any later version.
+#
+# This program is distributed in the hope that it will be useful,
+# but WITHOUT ANY WARRANTY; without even the implied warranty of
+# MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
+# GNU General Public License for more details.
+#
+# You should have received a copy of the GNU General Public License
+# along with this program. If not, see http://www.gnu.org/licenses/.
+
+set -eu
+
+gpgkey='3B1802F81B321347'
+fingerprint='4E2AF28A3D824CF2B3F1FE733B1802F81B321347'
+gpgkey2='DF3D13AA11E69900'
+
+# Make a backup with the default key ($gpgkey).
+$SRCDIR/tests/backup --encrypt-with=$gpgkey
+
+# Add new key. rainyday is the name of the client.
+$SRCDIR/tests/obnam --encrypt-with=$gpgkey add-key --keyid=$gpgkey2 \
+rainyday
+
+# Remove the old key.
+$SRCDIR/tests/obnam --encrypt-with=$gpgkey2 remove-key --keyid=$gpgkey \
+rainyday
+
+# Remove the old key from the gpg keyring.
+export GNUPGHOME=$DATADIR/gpg
+gpg --batch --delete-secret-key $fingerprint
+
+# Verify that the backup is still readable, now with the new key.
+$SRCDIR/tests/restore --encrypt-with=$gpgkey2
+$SRCDIR/tests/verify
+
only in patch2:
unchanged:
--- obnam-1.1.orig/obnamlib/plugins/encryption_plugin.py
+++ obnam-1.1/obnamlib/plugins/encryption_plugin.py
@@ -161,6 +161,12 @@
logging.debug('unable to remove key %s from %s (not there)' %
(keyid, toplevel))
+def rewrite_symmetric_key(self, repo, toplevel):
+symmetric_key = self.get_symmetric_key(repo, toplevel)
+userkeys = self.read_keyring(repo, toplevel)
+encrypted = obnamlib.encrypt_with_keyring(symmetric_key, userkeys)
+self._overwrite_file(repo, os.path.join(toplevel, 'key'), encrypted)
+
def add_client(self, clientlist, client_name):
clientlist.set_client_keyid(client_name, self.keyid)
@@ -233,6 +239,7 @@
clients = self._find_clientdirs(repo, args)
for toplevel in self._shared + clients:
self.add_to_userkeys(repo, toplevel, key)
+self.rewrite_symmetric_key(repo, toplevel)
def remove_key(self, args):
'''Remove a key from the repository.'''
@@ -244,6 +251,7 @@
clients = self._find_clientdirs(repo, args)
for toplevel in self._shared + clients:
self.remove_from_userkeys(repo, toplevel, keyid)
+self.rewrite_symmetric_key(repo, toplevel)
def remove_client(self, args):
'''Remove client and its key from repository.'''
only in patch2:
unchanged:
--- obnam-1.1.orig/debian/changelog
+++ obnam-1.1/debian/changelog
@@ -1,3 +1,10 @@
+obnam (1.1-1.1) unstable; urgency=low
+
+ * Non-maintainer upload.
+ * Fix encription key handling (Closes: #680670)
+
+ -- Gaudenz Steinlin gaud...@debian.org Thu, 20 Sep 2012 16:22:16 +0200
+
obnam (1.1-1) unstable; urgency=low
* New upstream version.
only in patch2:
unchanged:
--- obnam-1.1.orig/debian/rules
+++ obnam-1.1/debian/rules
@@ -3,6 +3,8 @@
dh $@ --with=python2 --with-buildsystem=python_distutils
override_dh_auto_test:
+ # fix test permission due to diff not representing permissions
+ chmod 755 tests/encryption-replaces-key.script
python setup.py build_ext -i
rm -rf build
cp -a test-gpghome temp.gpghome
Bug#688749: Add alternatives for nvidia-settings and nvidia-settings-legacy-173xx
Andreas Beckmann deb...@abeckmann.de writes: On 2012-09-25 13:16, Gaudenz Steinlin wrote: Please add alternatives for the current and legacy nvidia-settings packages to make them co-installable. This is yet another necessary fix to have both drivers available on Debian Live systems. Is this something you want to see in wheezy? In that case please ask for a freeze exception. Otherwise this will be delayed after the release. Having it in wheezy would be nice, but as the dkms co-installation changes are post-wheezy as well I don't think it matters much. I'm fine with having it in backports. I need this for a Debian Live based project and the main purpose of the bug reports is that we want to play nice with upstream and that we don't want to carry these patches indefinitely. + ALTERNATIVE_FILES=... you need some quotes there ... I'm by no means a make expert, but I don't think so. At least when I added quotes then the quotes ended up being part of the variable. 304xx will be a new legacy branch, probably we need to fork nvidia-settings-legacy-304xx, so we should keep this in mind and could use proper names right from the beginning ... The #LEGACY_OR_CURRENT# approach does not work for 96xx with has to use nvidia-settings-legacy-173xx #SETTINGS_SUFFIX# might be more generic I don't completely understand your concerns here. But maybe I also don't know enough about your workflow when a new version is released and the current one becomes legacy-X. I agree that LEGACY_OR_CURRENT is not the best name and could be renamed to SETTINGS_SUFFIX. But having the suffix legacy-304xx for the 304xx version even if no newer version is released does not sound right. Isn't the 96xx only a transitional package to install nouveau? As this is wheezy+ only I don't think 96xx is relevant anymore. If we rename nvidia-settings.png to nvidia-settings$SUFFIX.png and use this in the .desktop file, we can avoid an alternative. Yes true the alternative on the png file can be avoided. With your patch, the menu entry will only be available if nvidia-alternative is installed, while the binaries/manpage can be reached with their specific names (not the generic nvidia-settings name). What happens if we use nvidia-settings$SUFFIX.desktop (and no alternative for this one, too)? The problem with this approach is that then you have both versions in the menu if both are installed. But users probably only want to see the one that actually works. On the other hand I don't know a good solution for the case where nvidia-alternative(-legacy-173xx) is not installed. How is this case handled for the other alternatives? PPS: a single bug which affects the other packages would have been sufficient for the beginning (or even assigned to the 4 packages: Package: pkg1,pkg2,pkg3,pkg4) as it reduces the number of copies of the patches floating around ... lets keep discussion and updates here The problem with these two solutions is that the bug get's closed as soon as it's fixed in one of the packages. But that's not the case for this bug. It needs an upload of all 4 packages. But I agree that discussion is best kept either just to one report or then CCed to all of them. Keeping the discussion on this report is fine for me. Gaudenz -- Ever tried. Ever failed. No matter. Try again. Fail again. Fail better. ~ Samuel Beckett ~ -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#688794: PANIC: Circular dependancy after reboot when installing 1.20120606.6
Package: intel-microcode Version: 0.20120606-1 Severity: grave Justification: renders package unusable Dear Maintainer, I tried to upgrade from 1.20120606.1 on my i386 netbook and my current x64 machine, with either 3.2 or 3.5-trunk kernels on each PC. On reboot I always get the following error messages before dropping down to BusyBox console: Loading, please wait... /init: eval: line 1: Array_intel_microcode=udev: not found /init: eval: line 1: Array_intel_microcode=: not found PANIC: Circular dependance. Exiting. Then I must revert to a previous kernel and uninstall or revert to the previous version in order to have my machine running fine. Here is the report for the x64 machine: -- System Information: Debian Release: wheezy/sid APT prefers testing APT policy: (990, 'testing'), (500, 'stable'), (100, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 3.2.0-4-amd64 (SMP w/4 CPU cores) Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages intel-microcode depends on: ii microcode.ctl 1.17-13.2 intel-microcode recommends no packages. intel-microcode 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#688795: desktop-file-utils: No manual entry for update-desktop-database
Package: desktop-file-utils Version: 0.15-2 Severity: normal update-desktop-database is installed; but there's no man page for it. If it were a shell script, I could look inside and figure out what it does; but it's a compiled program, which makes this difficult. -- System Information: Debian Release: 6.0.5 APT prefers stable APT policy: (500, 'stable') Architecture: i386 (i686) Kernel: Linux 2.6.32-5-686 (SMP w/2 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages desktop-file-utils depends on: ii libc6 2.11.3-3 Embedded GNU C Library: Shared lib ii libglib2.0-0 2.24.2-1 The GLib library of C routines desktop-file-utils recommends no packages. desktop-file-utils 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#685980: dolphin: Fails to open a samba share path with Open Path In New Window
tag 685980 confirmed forwarded 685980 https://bugs.kde.org/show_bug.cgi?id=307393 thanks Hi, I confirmed and forward your bug upstream. Thank you for your contribution Adrien -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#688796: libkdtree++: incomplete debian/copyright
Source: libkdtree++ Version: 0.7.0-1 The file debian/copyright is not complete. For example the file kdtree++/kdtree.hpp contains this : /* COPYRIGHT -- * * This file is part of libkdtree++, a C++ template KD-Tree sorting container. * libkdtree++ is (c) 2004-2007 Martin F. Krafft libkdt...@pobox.madduck.net * and Sylvain Bougerel sylvain.bougerel.de...@gmail.com distributed under the * terms of the Artistic License 2.0. See the ./COPYING file in the source tree * root for more information. * Parts of this file are (c) 2004-2007 Paul Harris paulhar...@computer.org. * * THIS PACKAGE IS PROVIDED AS IS AND WITHOUT ANY EXPRESS OR IMPLIED * WARRANTIES, INCLUDING, WITHOUT LIMITATION, THE IMPLIED WARRANTIES * OF MERCHANTIBILITY AND FITNESS FOR A PARTICULAR PURPOSE. */ -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#688797: openldap 2.4.23 and 2.4.31 slapd server process frequently stops during everyday use
Package: slapd Version: 2.4.31-1~bpo60+2 Severity: important Tags: upstream During normal day use the slapd daemon stops and have to be restarted by a watchdog daemon. This problem is present on openldap 2.4.23 and on 2.4.31 (private backport from wheezy). From a previous investigation with 2.4.23 this is a problem of deadlocks in Berleckey DB. The backport was in the hope that this was the bug #618904. But our problem is still present on 2.4.31. Exists information from a db*_stat -CA that I will send in the next email. Jose Calhariz -- System Information: Debian Release: 6.0.5 APT prefers stable APT policy: (650, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 2.6.32-5-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=pt_PT.UTF-8 (charmap=locale: Cannot set LC_MESSAGES to default locale: No such file or directory locale: Cannot set LC_ALL to default locale: No such file or directory UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages slapd depends on: ii adduser3.112+nmu2add and remove users and groups ii coreutils 8.5-1 GNU core utilities ii debconf [debconf-2.0] 1.5.36.1 Debian configuration management sy ii libc6 2.11.3-3 Embedded GNU C Library: Shared lib ii libdb5.1 5.1.29-5~bpo60+1 Berkeley v5.1 Database Libraries [ ii libgcrypt111.4.5-2 LGPL Crypto library - runtime libr ii libgnutls262.8.6-1+squeeze2 the GNU TLS library - runtime libr ii libldap-2.4-2 2.4.31-1~bpo60+2 OpenLDAP libraries ii libltdl7 2.2.6b-2 A system independent dlopen wrappe ii libperl5.105.10.1-17squeeze3 shared Perl library ii libsasl2-2 2.1.23.dfsg1-7Cyrus SASL - authentication abstra ii libslp11.2.1-7.8 OpenSLP libraries ii libwrap0 7.6.q-19 Wietse Venema's TCP wrappers libra ii lsb-base 3.2-23.2squeeze1 Linux Standard Base 3.2 init scrip ii perl [libmime-base64-p 5.10.1-17squeeze3 Larry Wall's Practical Extraction ii psmisc 22.11-1 utilities that use the proc file s ii unixodbc 2.2.14p2-1ODBC tools libraries Versions of packages slapd recommends: ii libsasl2-modules 2.1.23.dfsg1-7 Cyrus SASL - pluggable authenticat Versions of packages slapd suggests: ii ldap-utils 2.4.31-1~bpo60+2 OpenLDAP utilities -- Configuration Files: /etc/default/slapd changed: SLAPD_CONF=/etc/ldap/slapd.d SLAPD_USER=openldap SLAPD_GROUP=openldap SLAPD_PIDFILE=/var/run/slapd/slapd.pid SLAPD_SERVICES=ldap:/// ldaps:/// ldapi:/// SLAPD_SENTINEL_FILE=/etc/ldap/noslapd export KRB5_KTNAME=/etc/ldap/slapd.keytab SLAPD_OPTIONS= -- debconf information excluded -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#688798: tmailscanner.c references functions which are removed in ruby1.9
Package: ruby-tmail Version: 1.2.7.1-2 Severity: serious from the build log: compiling tmailscanner.c tmailscanner.c: In function 'mails_s_new': tmailscanner.c:105:5: warning: implicit declaration of function 'rb_get_kcode' [-Wimplicit-function-declaration] tmailscanner.c:105:9: warning: assignment makes pointer from integer without a cast [enabled by default] Function `rb_get_kcode' implicitly converted to pointer at tmailscanner.c:105 however rb_get_kcode was removed from ruby1.9. I assume the package doesn't work at all with 1.9. $ fgrep -r rb_get_kcode ../ruby1.9.1-1.9.3.194/ ../ruby1.9.1-1.9.3.194/doc/ChangeLog-1.9.3: * re.c (rb_kcode, rb_get_kcode, rb_set_kcode): removed. ../ruby1.9.1-1.9.3.194/doc/ChangeLog-1.8.0: * re.c (rb_get_kcode): can retrieve $KCODE from C code. ../ruby1.9.1-1.9.3.194/ChangeLog: * include/ruby/intern.h (rb_set_kcode, rb_get_kcode): removed -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#688772: gnome Depends network-manager-gnome
Andreas Barth writes (Re: Bug#688772: gnome Depends network-manager-gnome): However, I'm not sure if 6. is too detailed, or should just be written as a. Any way which increases the likelihood of network-manager being installed (this includes also messages, user-face warnings etc) 6 was a list of the further ways I thought of to subvert the decision. I do have the catch-all as well, so I think my list is broader. I do think it's necessary to preempt sabotage of non-nm gnome systems. Also the first sentence of 9. might need to be dropped. Perhaps adding something like using words like 'crusade' together with implementing a tech ctte decision is inappropriate might be better? TBH I think it unlikely that enough of our colleagues will agree to even 9. And it may be unnecessary, given the rest. I think 8 is necessary. I don't think mentioning the rude language in the TC resolution is really appropriate. Ian. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#688794:
Sorry, typo error: it occurs when installing 1.20120606.6 coming from 0.20120606-1. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#687459: -- mc: didn't remove obsolete conffile /etc/mc/edit.spell.rc
* Dmitry Smirnov only...@member.fsf.org, 2012-09-25, 10:54: Thank you for reporting this. May I ask you how did you notice the issue? This script notifies me every time I install a package that didn't clean their obsolete conffiles: http://jwilk.net/software/adequate I genuinely missed it so perhaps I need to develop a habit to check for obsolete conffiles when packaging new versions... I recommend carefully reviewing debdiffs, both between two .dsc's and two sets of .deb's. If you put DEBDIFF_CONTROLFILES=ALL to ~/.devscripts, it'll show you wdiff of various control files, including conffiles. -- Jakub Wilk -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#688772: gnome Depends network-manager-gnome
Tollef Fog Heen tfh...@err.no writes: ]] Ian Jackson 10. We therefore formally reprimand Josselin Mouette. We consider his behaviour deliberately obstructive and obtuse. I don't think it's within the mandate of the tech-ctte to reprimand any developers. I agree. The duties of the tech-ctte do verge on project governance in some places, but by and large our goal is technical decision-making, and where we can I'd rather keep the resolutions focused on that decision unless the social aspects (like maintainership disputes) have been explicitly invoked. And even what governance role we have doesn't include reprimands or other types of censure, IMO. (I also personally am extremely uncomfortable with formal censure in a volunteer project, even apart from this particular case where it feels like an argument that spiraled out of control rather than something worthy of formal notice.) Also, in general, I agree with Sam's message. -- Russ Allbery (r...@debian.org) http://www.eyrie.org/~eagle/ -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#688799: grub-common: grub-mknetdir does not need to be run by root -- move out of sbin?
Package: grub-common Version: 2.00-5 Severity: wishlist I observe that grub-mknetdir works fine as a non-privileged user. Making it an administrator-only tool by placing it in /usr/sbin/ seems like it encourages people to update their tftp server directories as root, when they don't necessarily need extra privileges to do that. Maybe it belongs in /usr/bin instead? 0 dkg@stylus:~/tmp$ /usr/sbin/grub-mknetdir --net-directory=/home/dkg/netdir Netboot directory for i386-pc created. Configure your DHCP server to point to /boot/grub/i386-pc/core.0 0 dkg@stylus:~/tmp$ Regards, --dkg PS Thanks for packaging grub 2.00 in experimental! It works for me on this old dell workstation. -- System Information: Debian Release: wheezy/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'stable'), (1, 'experimental') Architecture: i386 (i686) Kernel: Linux 3.5-trunk-686-pae (SMP w/1 CPU core) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages grub-common depends on: ii gettext-base0.18.1.1-9 ii libc6 2.13-35 ii libdevmapper1.02.1 2:1.02.74-4 ii libfreetype62.4.9-1 ii libfuse22.9.1-1 ii liblzma55.1.1alpha+20120614-1 ii zlib1g 1:1.2.7.dfsg-13 Versions of packages grub-common recommends: ii os-prober 1.56 Versions of packages grub-common suggests: ii console-setup 1.82 ii desktop-base 7.0.3 pn grub-emu none pn multiboot-doc none ii xorriso1.2.2-2 -- 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#688516: Refresh rate can't be changed
Hi hetas, Thanks for reporting this. I can confirm that, at least on my system, the --rate option seems to be ineffective on a recent 304 driver. I've filed NVIDIA bug 1054623. Feel free to use this bug number in future inquiries about this issue. On 09/24/2012 10:44 AM, hetas wrote: Hello, I have a problem with nvidia Linux drivers. Something has happened between driver versions 302.17 and 304.48 that prevent changing refresh rate using xrandr. I'm on Debian and those versions where installed from Debian packages. I also tried latest, 304.51 installer, directly from nVidia site. After installing one of those newer versions xrandr doesn't change the refresh rate any more. I tried going through the readme and changelog but as far as I could tell recent changes to ranrd handling should not break xrandr. Xrandr version: $xranrd --version xrandr program version 1.3.5 Server reports RandR version 1.3 DynamicTwinView is set to false. Composite extension is disabled. Thanks, Juho Turunen -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#688772: gnome Depends network-manager-gnome
On 25 September 2012 13:51, Ian Jackson ijack...@chiark.greenend.org.uk wrote: TBH I think it unlikely that enough of our colleagues will agree to even 9. And it may be unnecessary, given the rest. I think 8 is necessary. I don't think mentioning the rude language in the TC resolution is really appropriate. Why do you have the authority to use language like We therefore formally reprimand Josselin Mouette. We consider his behaviour deliberately obstructive and obtuse. but he is not allowed to use the word Crusade? Crusade does seem accurate for definition #3 of http://dictionary.reference.com/browse/crusade And if you don't think that the Tech Committee is likely to agree to an unnecessary part of your proposal, why are you wasting their time by including it? Jeremy -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
