Bug#704732: gnome: Setting certain touchpad options makes it impossible to login
Package: gnome Version: 1:3.4+7 Severity: important If I open the settings window, from the top right user menu, and navigate to Mouse Touchpad, then click the Touchpad tab: Then I set: - enable clicks with touchpad - two-finger scrolling if I also set Disable touchpad while typing this causes a number of serious problems the next time I logoff and login: - even though the checkbox is checked, I cannot click with touchpad - the background style of the settings box has changed, with borders in different gray colour around the groups of icons - if I open a Terminal, the colours have been changed to black text on black background If I then reboot and try to login again, Gnome will not let me in, giving me a small dialog saying something like Something bad happened, you can't login. and then returns me to the gdm3 login. If I rm -rf .gconf and start again, but avoid changing the setting of Disable touchpad while typing, then things work fine. Thanks, - Chris -- System Information: Debian Release: 7.0 APT prefers testing APT policy: (500, 'testing') Architecture: i386 (i686) Kernel: Linux 3.2.0-4-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 gnome depends on: ii aisleriot1:3.4.1-1 ii alacarte 3.5.3-1 ii avahi-daemon 0.6.31-2 ii cheese 3.4.2-2 ii cups-pk-helper 0.2.3-3 ii desktop-base 7.0.3 ii evolution3.4.4-2 ii evolution-plugins3.4.4-2 ii file-roller 3.4.2-1 ii gedit3.4.2-1 ii gedit-plugins3.4.0-1 ii gimp 2.8.2-2 ii gnome-applets3.4.1-3 ii gnome-color-manager 3.4.2-1 ii gnome-core 1:3.4+7 ii gnome-documents 0.4.2-2 ii gnome-games 1:3.4.2-3 ii gnome-media 3.4.0-1 ii gnome-nettool3.2.0-1 ii gnome-orca 3.4.2-2 ii gnome-shell-extensions 3.4.0-2 ii gnome-tweak-tool 3.4.0.1-2 ii gstreamer0.10-ffmpeg 0.10.13-5 ii gstreamer0.10-plugins-ugly 0.10.19-2+b2 ii hamster-applet 2.91.3+git20120514.b9fec3e1-1 ii inkscape 0.48.3.1-1.3 ii libgtk2-perl 2:1.244-1 ii libreoffice-calc 1:3.5.4+dfsg-4 ii libreoffice-gnome1:3.5.4+dfsg-4 ii libreoffice-impress 1:3.5.4+dfsg-4 ii libreoffice-writer 1:3.5.4+dfsg-4 ii nautilus-sendto 3.0.3-2+b1 ii network-manager-gnome0.9.4.1-5 ii rhythmbox2.97-2.1 ii rhythmbox-plugin-cdrecorder 2.97-2.1 ii rhythmbox-plugins2.97-2.1 ii rygel-playbin0.14.3-2 ii rygel-preferences0.14.3-2 ii rygel-tracker0.14.3-2 ii seahorse 3.4.1-2 ii shotwell 0.12.3-2 ii simple-scan 3.4.2-1 ii sound-juicer 3.4.0-3 ii telepathy-gabble 0.16.5-1 ii telepathy-rakia 0.7.4-1 ii telepathy-salut 0.8.1-1 ii tomboy 1.10.0-2 ii totem3.0.1-8 ii totem-plugins3.0.1-8 ii tracker-gui 0.14.1-3 ii transmission-gtk 2.52-3+nmu1 ii vinagre 3.4.2-2 ii xdg-user-dirs-gtk0.9-1 ii xul-ext-adblock-plus 2.1-1 Versions of packages gnome recommends: ii browser-plugin-gnash 0.8.11~git20120629-1 ii gdebi0.8.7 ii gnome-games-extra-data 3.2.0-4 ii nautilus-sendto-empathy 3.4.2.3-2 ii telepathy-idle 0.1.11-2 Versions of packages gnome suggests: pn dia-gnome none pn gnome-boxesnone pn gnucashnone pn iceweasel-l10n-all none ii libreoffice-evolution 1:3.5.4+dfsg-4 pn plannernone pn xul-ext-gnome-keyring none Versions of packages gnome-core depends on: ii at-spi2-core2.5.3-2 ii baobab 3.4.1-1 ii brasero 3.4.1-4 ii caribou 0.4.4-1 ii caribou-antler 0.4.4-1 ii dconf-gsettings-backend 0.12.1-3 ii dconf-tools 0.12.1-3 ii empathy 3.4.2.3-2 ii eog 3.4.2-1+build1 ii evince 3.4.0-3.1 ii evolution-data-server 3.4.4-3 ii fonts-cantarell 0.0.9-1 ii gcalctool 6.4.2.1-3 ii gconf2 3.2.5-1+build1 ii gdm33.4.1-6 ii gkbd-capplet3.4.0.2-1 ii glib-networking 2.32.3-1 ii gnome-backgrounds 3.4.2-1 ii gnome-bluetooth 3.4.2-1 ii
Bug#704726: Package has a useless and misleading menu entry.
clone 704726 -1 retitle 704726 menu entry does not work properly in the menu severity 704726 minor retitle -1 ebook-speaker depends on xterm without declaring it thanks On 05-04-13 04:38, Scott Nanni wrote: I selected ebook-reader for install, found a menu entry in Sound Video, selected that menu entry and got a dialog (-) Could not launch 'eBook speaker' Failed to excute child process xterm (no such file or directory) Indeed, good catch. I consider this indeed a bug in the package. my simplest suggestion to resolving this problem would be to remove the menu entry from the package If I recall correctly, menu entries are used for more than just menu items. They should also interact with e.g. your file browser, such that it knows how to start a program that could do something useful with the file. I will investigate if and how to improve the situation. signature.asc Description: OpenPGP digital signature
Bug#672318: chirp 0.3.0-0.1 Debian package available
Chris, Did you try the Chirp-Daily package? It is almost DAILY in its updates and working FB for me on Ubuntu 12.04-LTS. Please look at https://launchpad.net/ubuntu/+source/chirp before you proceed much more. The PPA for chirp is at https://launchpad.net/~dansmith/+archive/chirp-snapshots Dave - KB3EFS PS - A fork similar to this is what caused all the problems with NODE. Did we not learn anything from that drawn out over more than a decade mess? On 04/04/2013 11:04 PM, Chris Knadle wrote: Greetings. I recently got a new rig, a small HT, and needed chirp to program it. Unfortunately the version of the packge in Debian now doesn't work for the rig, and I found the year-old wishlist bug #672318 requesting a new version. I've prepared a new 0.3.0-0.1 package (currently as an NMU) and made several other changes -- the debian/rules file now uses dh. If someone has time to take a peek and review this source package, I'd appreciate it. ;-) http://debian-packages.coredump.us/debian/pool/main/c/chirp/ Thanks. -- Chris, KB2IQN -- Chris Knadle chris.kna...@coredump.us -- David A Aitcheson david.aitche...@gmail.com Go Green! Print this email only when necessary. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#704734: kdepim-runtime needs to be upgraded to version 4:4.10.2-1
Package: kdepim-runtime
Version: 4:4.8.4-1
Severity: normal
Dear Maintainer,
Trying to install plasma-desktop I get the following situation :-
$ sudo aptitude install plasma-desktop=4:4.10.2-1
plasma-widgets-workspace=4:4.10.2-1 kde-workspace-bin=4:4.10.2-1
plasma-dataengines-workspace=4:4.10.2-1
The following NEW packages will be installed:
kde-workspace{a} kde-workspace-bin kdepim-runtime{a}
plasma-dataengines-workspace plasma-desktop
plasma-scriptengine-python{a} plasma-scriptengines{a}
plasma-widgets-workspace python-kde4{a}
0 packages upgraded, 9 newly installed, 0 to remove and 0 not upgraded.
Need to get 36.2 kB/18.5 MB of archives. After unpacking 85.0 MB will be used.
The following packages have unmet dependencies:
libkpimidentities4 : Breaks: kdepim-runtime ( 4:4.5) but
4:4.4.11.1-6 is to be installed.
The following actions will resolve these dependencies:
Remove the following packages:
1) libkpimidentities4
Accept this solution? [Y/n/q/?] q
Abandoning all efforts to resolve these dependencies.
Abort.
$ apt-show-versions -a libkpimidentities4
libkpimidentities4 4:4.10.2-1 install ok installed
libkpimidentities4 4:4.4.5-2 stable ftp.debian.org
libkpimidentities4 4:4.8.4-2 wheezy ftp.debian.org
libkpimidentities4 4:4.8.4-2 unstable ftp.debian.org
libkpimidentities4 4:4.9.5-0r2 experimental-snapshots qt-kde.debian.net
libkpimidentities4 4:4.10.2-1 experimental ftp.debian.org
libkpimidentities4/experimental uptodate 4:4.10.2-1
As can be seen from above, libkpimidentities is updated to latest.
Trying to install kdepim-runtime I get this :-
$ sudo aptitude install kdepim-runtime=4:4.8.4-1
The following NEW packages will be installed:
kdepim-runtime libkalarmcal2{ab}
0 packages upgraded, 2 newly installed, 0 to remove and 0 not upgraded.
Need to get 117 kB/4,258 kB of archives. After unpacking 11.5 MB will be used.
The following packages have unmet dependencies:
libkalarmcal2 : Depends: libakonadi-kde4 (= 4:4.8.4-2) but 4:4.10.2-1
is installed.
Depends: libkcalcore4 (= 4:4.8.4-2) but 4:4.10.2-1 is
installed.
Depends: libkholidays4 (= 4:4.8.4-2) but 4:4.10.2-1
is installed.
Depends: libkpimidentities4 (= 4:4.8.4-2) but
4:4.10.2-1 is installed.
libkpimidentities4 : Breaks: libkalarmcal2 ( 4:4.9) but 4:4.8.4-2 is
to be installed.
The following actions will resolve these dependencies:
Keep the following packages at their current version:
1) kdepim-runtime [Not Installed]
2) libkalarmcal2 [Not Installed]
$ apt-show-versions -a kdepim-runtime
kdepim-runtime deinstall ok config-files
kdepim-runtime 4:4.4.7-1stable ftp.debian.org
kdepim-runtime 4:4.4.11.1-6 wheezy ftp.debian.org
kdepim-runtime 4:4.4.11.1-6 unstable ftp.debian.org
kdepim-runtime 4:4.8.4-1experimental ftp.debian.org
kdepim-runtime not installed
Accept this solution? [Y/n/q/?] q
Abandoning all efforts to resolve these dependencies.
Abort.
So at the end, it's kdepim-runtime which needs to be upgraded in order
for plasma-desktop to have a successful installation.
-- System Information:
Debian Release: 7.0
APT prefers testing
APT policy: (500, 'testing'), (500, 'stable'), (10, 'unstable'), (1,
'experimental')
Architecture: amd64 (x86_64)
Kernel: Linux 3.8-trunk-amd64 (SMP w/2 CPU cores)
Locale: LANG=en_IN.utf8, LC_CTYPE=en_IN.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Versions of packages kdepim-runtime depends on:
ii akonadi-server1.9.1-2
ii kde-runtime 4:4.10.2-1
ii kdepimlibs-kio-plugins4:4.10.2-1
ii libakonadi-kabc4 4:4.10.2-1
ii libakonadi-kcal4 4:4.10.2-1
ii libakonadi-kde4 4:4.10.2-1
ii libakonadi-kmime4 4:4.10.2-1
ii libakonadiprotocolinternals1 1.9.1-2
ii libc6 2.17-0experimental2
ii libgcc1 1:4.8.0-2
ii libkabc4 4:4.10.2-1
ii libkcal4 4:4.10.2-1
ii libkcalcore4 4:4.10.2-1
ii libkcalutils4 4:4.10.2-1
ii libkcmutils4 4:4.10.2-1
ii libkdecore5 4:4.10.2-1
ii libkdeui5 4:4.10.2-1
ii libkimap4 4:4.10.2-1
ii libkio5 4:4.10.2-1
ii libkmime4 4:4.10.2-1
ii libkpimutils4 4:4.10.2-1
ii libkresources44:4.10.2-1
ii libmailtransport4 4:4.10.2-1
ii libmicroblog4 4:4.10.2-1
ii libnepomuk4 4:4.10.2-1
ii libqt4-dbus 4:4.8.4+dfsg-1
ii libqt4-network4:4.8.4+dfsg-1
ii libqt4-qt3support 4:4.8.4+dfsg-1
ii libqt4-xml4:4.8.4+dfsg-1
ii libqtcore44:4.8.4+dfsg-1
ii libqtgui4 4:4.8.4+dfsg-1
ii libsolid4
Bug#697617: jenkins: CVE-2013-0158: remote code execution vulnerability
Hello, Is there something that I could help to get this bug fixed and closed? Please contact me in case you want any help. --- Henri Salo signature.asc Description: Digital signature
Bug#704707: trac-authopenid crashes when an OpenID provider does not provide a full name
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 04/04/2013 11:18 PM, Daniel Kahn Gillmor wrote: Hi Jeremy-- On 04/04/2013 04:48 PM, Daniel Kahn Gillmor wrote: Without the attached patch, when an OpenID provider declines to provide a full name, trac crashes by accessing the authname variable before it was initialized. I've just pushed this fix into the collab-maint svn repository mentioned in the Vcs-* headers of debian/control, and added myself to Uploaders: on the theory that its placement in collab-maint encourages collaborative maintenance. I've tested this patch and it works fine, so i'm uploading it to unstable. I hope i'm not stepping on your toes, Jeremy! If you'd rather i just contribute patches via the BTS and the VCS, but not upload, let me know and i won't take the uploading step in the future. Thanks for the patch Daniel! I have absolutely no problem with your upload, as you said it's in collab-maint for a reason. Feel free to upload again as needed. Cheers, Jeremy -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.12 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAlFed/cACgkQ4mJJZqJp2SehzACglrCHsx+d0jE3RyF70XreBtf9 Bj0AoJ9aY7e6BQcCKVtGqqOuMn78bbfb =/KBm -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#704251: marked as done ([fp-compiler] On upgrade, update-alternatives error may occur)
On Mon, 2013-04-01 at 01:27 +, Debian Bug Tracking System wrote: I upgraded squeeze-wheezy with fp-compiler in a clean chroot, and it worked fine. Closing the bug since there is far too little information here to do anything. Please reopen if you can provide logs showing exactly what you're doing and what went wrong. Best wishes, Mike Can you please ensure you don't have some message like this one: There is only one alternative in link group fpc.cfg (providing /etc/fpc.cfg): /etc/fpc-2.6.0.cfg Nothing to configure. update-alternatives: warning: forcing reinstallation of alternative /etc/fpc-2.6.0.cfg because link group fpc.cfg is broken update-alternatives: warning: not replacing /etc/fpc.cfg with a link Indeed, Squeeze was shipping a plain text file, while the upgrade tries to use update-alternatives. This will not work if user choose not to replace the old file. Cheers, signature.asc Description: This is a digitally signed message part
Bug#704719: FTBFS on visp
Thanks for reporting the bug. I regenerated the symbol file and updated the package to use pkg-kde-tools: https://github.com/thomas-moulard/visp-deb/commit/9ff6c202e03d4ae92fa676a4395fdb04d4742f0c Please note that an upstream version has been released in the meantime so this will be fixed in 2.7.0-1. -- Thomas Moulard（ムラー トマ） CNRS-AIST JRL (Joint Robotics Laboratory), UMI3218/CRT, Tsukuba, Japan http://thomas.moulard.net | Tel: +81-8436-1985 | GPG Key Id: 516FC68F31496D58 Add me on LinkedIn: http://www.linkedin.com/in/moulard -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#703715: linux-image-3.2.0-4-amd64: random Wheezy freeze
Dear all, Just another information about the bug. I've installed the sid kernel: apt-cache policy linux-image-3.2.0-4-amd64 linux-image-3.2.0-4-amd64: Installé : 3.2.41-2 Candidat : 3.2.41-2 Table de version : *** 3.2.41-2 0 90 http://ftp.fr.debian.org/debian/ sid/main amd64 Packages 100 /var/lib/dpkg/status 3.2.39-2 0 990 http://ftp.fr.debian.org/debian/ wheezy/main amd64 Packages But unfortunatly this does not totaly resolved the bug. It's seem to be more stable (less freeze) but not totaly: my laptop just freeze two times in the last two hours ... Best regards,
Bug#700975: RAID barely usable on my home machine
On Fri, Apr 5, 2013 at 2:16 AM, Roger Heflin rogerhef...@gmail.com wrote: lspci look like this for the controller: SATA controller: Marvell Technology Group Ltd. Device 9230 (rev 10) 4pt sata3.0 6gbit or is yours a different one? Mine looks slightly different (included somewhere in my mail), but should be a device in the same family. I have the issue also, I have eliminated all smart hits against the disks and no incidents since then. Not a great workaround as such, first of all, running SMART against your storage is kind of recommended, and secondly, as I said, udisks2 will also SMART your disks occasionally, which you have to uninstall parts of GNOME to get rid of. I have seagate 1.5tb drives on mine that had had the issues. Suggests it's not something about my drives, as I have WD Red disks. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#493784: libgc: please provide a build with --enable-large-config
On Mon, Aug 04, 2008 at 11:26:10PM +0200, Bernd Zeimetz wrote: for some use cases ([1] for example) it would be useful to have a version of libgc available, which was built with --enable-large-config. I didn't dig into libgc to find out what the best way would be to achive this, but I'm sure there is one ;) Related to #503218, which I don't want to reopen, I again had the case of inkscape not opening a file with a libgc without --enable-large-config. I recompiled libgc and it worked. That's on x86 with 8G of RAM, so I'm ok with inkscape chewing 6G of it. Maybe it could be made the default on some architectures only? At least if it's a compatible change? Kind regards Philipp Kern -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#493784: libgc: please provide a build with --enable-large-config
Philipp Kern pk...@debian.org writes: On Mon, Aug 04, 2008 at 11:26:10PM +0200, Bernd Zeimetz wrote: for some use cases ([1] for example) it would be useful to have a version of libgc available, which was built with --enable-large-config. I didn't dig into libgc to find out what the best way would be to achive this, but I'm sure there is one ;) Related to #503218, which I don't want to reopen, I again had the case of inkscape not opening a file with a libgc without --enable-large-config. I recompiled libgc and it worked. That's on x86 with 8G of RAM, so I'm ok with inkscape chewing 6G of it. Maybe it could be made the default on some architectures only? At least if it's a compatible change? I'll look into it after the freeze Christoph -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#700975: RAID barely usable on my home machine
On Thu Apr 04, 2013 at 10:13:05 +0200, Maik Zumstrull wrote: Hello Linux RAID and ATA people, I've managed to find a configuration on my home desktop where a particular RAID array is barely usable. You can find my initial report at: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=700975 In summary: - I create an array across four disks on a Marvell AHCI controller, which automatically goes into rebuild mode. - Somebody (e.g. smartd or udisks2 or me, testing) sends a SMART command to one of the disks. - The SMART command fails. - The ATA subsystems freaks out all over the place, until eventually none of the disks on that controller are responsive. - The array is dead until reboot. (Curiously, without data loss so far. Kudos on the RAID code, I guess.) I've found the issue to be highly reproducible so far. Things mostly work if the array is not under heavy load (not rebuilding, no big file copies going on) or I make completely sure nothing sends SMART commands. I currently do keep real files on that array, but backed-up ones, so I could wipe it for more tests if really necessary. I used to have the same issues on one of my machines. The solution was to buy a decent SAS/SATA HBA (I went with the Intel RS2WC080, but see http://blog.zorinaq.com/?e=10 for a more complete list), which now works perfectly with exactly the same drives as before. HTH, Robin -- ___ ( ' } | Robin Hillro...@robinhill.me.uk | / / ) | Little Jim says | // !! | He fallen in de water !! | pgp5cDjqCplTe.pgp Description: PGP signature
Bug#704735: nmu: proftpd-dfsg_1.3.4a-4
Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: binnmu Hi this is requested to solve #704484 that prevents mod_tls working due to strict checking against openssl version. nmu proftpd-dfsg_1.3.4a-4 . ALL . -m rebuild to force linking with the current openssl version -- System Information: Debian Release: 7.0 APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing'), (1, 'experimental') Architecture: i386 (i686) Kernel: Linux 3.2.0-4-686-pae (SMP w/1 CPU core) Locale: LANG=it_IT.UTF-8, LC_CTYPE=it_IT.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#704736: gtkpod: FTBFS on ppc64: Please modify libatomicparsley0.symbols
Source: gtkpod Version: 2.1.3-2 Severity: important Tags: patch FTBFS on ppc64 port occurs from ver. 2.1.2~beta2-3, because of ppc64 not listed in debian/libatomicparsley0.symbols. build logs http://buildd.debian-ports.org/status/package.php?p=gtkpodsuite=experimental http://buildd.debian-ports.org/status/package.php?p=gtkpodsuite=sid Here is a patch attached which was build-checked. Incidentally, this error also occurs on alpha which is 64-bit port, too, so, I think that it can correct by similar modification. Regards, -- Hiroyuki Yamamoto A75D B285 7050 4BF9 AEDA 91AC 3A10 59C6 5203 04DC diff -Nurd gtkpod-2.1.3.orig/debian/libatomicparsley0.symbols gtkpod-2.1.3/debian/libatomicparsley0.symbols --- gtkpod-2.1.3.orig/debian/libatomicparsley0.symbols 2012-06-12 23:38:09.0 +0900 +++ gtkpod-2.1.3/debian/libatomicparsley0.symbols 2013-04-05 14:56:48.0 +0900 @@ -33,8 +33,8 @@ _Z13UTF8ToUTF16LEPhiPKhi@Base 0.0.1 _Z13UTF8Toisolat1PhiPKhi@Base 0.0.1 _Z13char4TOuint32jPc@Base 0.0.1 - (arch=amd64 ia64 kfreebsd-amd64 s390x)_Z13char8TOuint64mPc@Base 0.0.1 - (arch=!amd64 !ia64 !kfreebsd-amd64 !s390x)_Z13char8TOuint64yPc@Base 0.0.1 + (arch=amd64 ia64 kfreebsd-amd64 ppc64 s390x)_Z13char8TOuint64mPc@Base 0.0.1 + (arch=!amd64 !ia64 !kfreebsd-amd64 !ppc64 !s390x)_Z13char8TOuint64yPc@Base 0.0.1 _Z13isolat1ToUTF8PhiPKhi@Base 0.0.1 _Z13sha1_init_ctxP8sha1_ctx@Base 0.0.1 _Z13sha1_read_ctxPK8sha1_ctxPv@Base 0.0.1 @@ -82,8 +82,8 @@ _Z19UInt16FromBigEndianPKc@Base 0.0.1 _Z19UInt32FromBigEndianPKc@Base 0.0.1 _Z19UInt64FromBigEndianPKc@Base 0.0.1 - (arch=amd64 ia64 kfreebsd-amd64 s390x)_Z20APar_AtomizeFileInfojjmPchhhjtP11uuid_vitals@Base 0.0.1 - (arch=!amd64 !ia64 !kfreebsd-amd64 !s390x)_Z20APar_AtomizeFileInfojjyPchhhjtP11uuid_vitals@Base 0.0.1 + (arch=amd64 ia64 kfreebsd-amd64 ppc64 s390x)_Z20APar_AtomizeFileInfojjmPchhhjtP11uuid_vitals@Base 0.0.1 + (arch=!amd64 !ia64 !kfreebsd-amd64 !ppc64 !s390x)_Z20APar_AtomizeFileInfojjyPchhhjtP11uuid_vitals@Base 0.0.1 _Z20APar_ExtractDataAtomi@Base 0.0.1 _Z20APar_ExtractPicPrefsPc@Base 0.0.1 _Z20APar_FindValueInAtomPcP8_IO_FILEsjj@Base 0.0.1
Bug#704737: printing doesn't work because of incorrect size sent to the printer
Package: evince Version: 3.4.0-3.1 Severity: important Dear maintainers, I cannot print any document with evince these days. It has been for at least one month. It used to work in the past, but I do not print documents every day so I do not know when it stopped working exactly. I'm using an enterprise network printer. When I submit a job with evince, it complains because the job expects A3 paper, which is not available. Even when I explicitly set the paper size to A4 in the printing dialog box. When I print using Iceweasel, which uses the same dialog box (so I guess it shares some backend with evince), it works. Printing from the commandline using lpr, or printing a test page using CUPS's web interface on localhost also work. Cheers, -- Stéphane -- System Information: Debian Release: 7.0 APT prefers testing APT policy: (990, 'testing'), (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.8-trunk-amd64 (SMP w/8 CPU cores) Locale: LANG=fr_FR.utf8, LC_CTYPE=fr_FR.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages evince depends on: ii evince-common3.4.0-3.1 ii gnome-icon-theme 3.4.0-2 ii libatk1.0-0 2.4.0-2 ii libc62.13-38 ii libcairo-gobject21.12.2-3 ii libcairo21.12.2-3 ii libevdocument3-4 3.4.0-3.1 ii libevview3-3 3.4.0-3.1 ii libgail-3-0 3.4.2-6 ii libgdk-pixbuf2.0-0 2.26.1-1 ii libglib2.0-0 2.33.12+really2.32.4-5 ii libgnome-keyring03.4.1-1 ii libgtk-3-0 3.4.2-6 ii libice6 2:1.0.8-2 ii libnautilus-extension1a 3.4.2-1+build1 ii libpango1.0-01.30.0-1 ii libsm6 2:1.2.1-2 ii libx11-6 2:1.5.0-1 ii libxml2 2.8.0+dfsg1-7+nmu1 ii shared-mime-info 1.0-1+b1 ii zlib1g 1:1.2.7.dfsg-13 Versions of packages evince recommends: ii dbus-x11 1.6.8-1 ii gvfs 1.12.3-4 Versions of packages evince suggests: ii nautilus 3.4.2-1+build1 ii poppler-data 0.4.5-10 pn unrar none -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#704738: squid3: @DEFAULT_CONFIG_FILE@ not replaced
Package: squid3 Version: 3.1.6-1.2+squeeze3 Severity: minor In the manual page of squid3 is @DEFAULT_CONFIG_FILE@ not replaced when the package is build. The same for @DEFAULT_MIME_TABLE@ and @DEFAULT_ERROR_DIR@ -- System Information: Debian Release: 6.0.7 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 2.6.32-5-amd64 (SMP w/2 CPU cores) Locale: LANG=nl_NL.utf8, LC_CTYPE=nl_NL.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages squid3 depends on: ii adduser3.112+nmu2add and remove users and groups ii libc6 2.11.3-4 Embedded GNU C Library: Shared lib ii libcap21:2.19-3 support for getting/setting POSIX. ii libcomerr2 1.41.12-4stable1 common error description library ii libdb4.8 4.8.30-2 Berkeley v4.8 Database Libraries [ ii libexpat1 2.0.1-7+squeeze1 XML parsing C library - runtime li ii libgcc11:4.4.5-8 GCC support library ii libgssapi-krb5-2 1.8.3+dfsg-4squeeze6 MIT Kerberos runtime libraries - k ii libk5crypto3 1.8.3+dfsg-4squeeze6 MIT Kerberos runtime libraries - C ii libkrb5-3 1.8.3+dfsg-4squeeze6 MIT Kerberos runtime libraries ii libldap-2.4-2 2.4.23-7.3OpenLDAP libraries ii libltdl7 2.2.6b-2 A system independent dlopen wrappe ii libpam0g 1.1.1-6.1+squeeze1Pluggable Authentication Modules l ii libsasl2-2 2.1.23.dfsg1-7Cyrus SASL - authentication abstra ii libstdc++6 4.4.5-8 The GNU Standard C++ Library v3 ii libxml22.7.8.dfsg-2+squeeze7 GNOME XML library ii logrotate 3.7.8-6 Log rotation utility ii lsb-base 3.2-23.2squeeze1 Linux Standard Base 3.2 init scrip ii netbase4.45 Basic TCP/IP networking system ii squid3-common 3.1.6-1.2+squeeze3A full featured Web Proxy cache (H squid3 recommends no packages. Versions of packages squid3 suggests: pn resolvconfnone (no description available) ii smbclient 2:3.5.6~dfsg-3squeeze9 command-line SMB/CIFS clients for pn squid-cgi none (no description available) pn squidclient none (no description available) -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#700975: RAID barely usable on my home machine
On 2013-04-05 10:06, Maik Zumstrull wrote: On Fri, Apr 5, 2013 at 2:16 AM, Roger Heflin rogerhef...@gmail.com wrote: lspci look like this for the controller: SATA controller: Marvell Technology Group Ltd. Device 9230 (rev 10) 4pt sata3.0 6gbit or is yours a different one? Mine looks slightly different (included somewhere in my mail), but should be a device in the same family. I have the issue also, I have eliminated all smart hits against the disks and no incidents since then. Not a great workaround as such, first of all, running SMART against your storage is kind of recommended, and secondly, as I said, udisks2 will also SMART your disks occasionally, which you have to uninstall parts of GNOME to get rid of. This reminds me of an old thread in freebsd-scsi, where a guy with some SAS disks and a SAS2008 controller would have his disks 'lost' if he used smartctl on routine, and could reproduce it reliably by spamming a disk with smartctl -a (but smartctl -i, and something else would not reproduce it). And he found that to solve it, he can change the disk tags to much lower. I think disk tags might be equivalent to the nr_requests in Linux. Here is the thread: http://osdir.com/ml/freebsd-scsi/2011-11/msg6.html I have seagate 1.5tb drives on mine that had had the issues. Suggests it's not something about my drives, as I have WD Red disks. -- To unsubscribe from this list: send the line unsubscribe linux-raid in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html -- Peter Maloney Brockmann Consult Max-Planck-Str. 2 21502 Geesthacht Germany Tel: +49 4152 889 300 Fax: +49 4152 889 333 E-mail: peter.malo...@brockmann-consult.de Internet: http://www.brockmann-consult.de -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#704739: growisofs: dvd+rw-format man page is incomplete and growisofs man page should mention this utility
Package: growisofs Version: 7.1-10 Severity: normal I got an error when using growisofs -Z ... on DVD-RW medias (while there was no such problem with DVD+RW medias). Something like: :-[ WRITE@LBA=0h failed with SK=5h/INVALID ADDRESS FOR WRITE]: Invalid argument :-( attempt to re-run with -dvd-compat -dvd-compat to engage DAO or apply full blanking procedure :-( write failed: Invalid argument The man pages under Debian neither explain the problem nor what to do. This should be fixed, as done under Red Hat: https://bugzilla.redhat.com/show_bug.cgi?id=810838 I've tested, and this solved my problem. Moreover the growisofs man page should mention dvd+rw-format. -- System Information: Debian Release: 7.0 APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing'), (500, 'stable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 3.2.0-4-amd64 (SMP w/2 CPU cores) Locale: LANG=POSIX, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages growisofs depends on: ii libc6 2.13-38 ii libgcc1 1:4.7.2-5 ii libstdc++6 4.7.2-5 growisofs recommends no packages. growisofs 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#704259: vdr-plugin-xineliboutput: VDR tends to crash when stopping playing an internet radio
Package: vdr-plugin-xineliboutput Version: 1.0.7+cvs20120609.1902-1 Followup-For: Bug #704259 Hi, will try this in my test environment, in the mean time, I found a little bit more but it puzzles me a bit more also. I found in the syslog a segfault message coming from the kernel/iMonLCD (?!) before each VDR restart: # grep segfault /var/log/syslog Feb 24 19:53:09 hdvdr1 kernel: [11912.930544] iMonLCD: watch [3502]: segfault at 27e6020 ip 027e6020 sp 7fadd7180d68 error 15 Feb 28 20:00:17 hdvdr1 kernel: [ 2695.052721] iMonLCD: watch [2655]: segfault at 2ab8 ip 7f66e7dd2e86 sp 7f66dbcb6d20 error 4 in libvdr-xineliboutput.so.1.7.28[7f66e7da7000+84000] Mar 10 13:14:24 hdvdr1 kernel: [25714.757858] iMonLCD: watch [4826]: segfault at 2ab8 ip 7ffb6db7be86 sp 7ffb6b262d20 error 4 in libvdr-xineliboutput.so.1.7.28[7ffb6db5+84000] Mar 11 09:49:24 hdvdr1 kernel: [ 3296.484567] iMonLCD: watch [2638]: segfault at 2ab8 ip 7f5922403e86 sp 7f59167fbd20 error 4 in libvdr-xineliboutput.so.1.7.28[7f59223d8000+84000] Mar 11 19:08:25 hdvdr1 kernel: [ 3398.925571] iMonLCD: watch [2648]: segfault at 2ab8 ip 7f99265f5e86 sp 7f991a7fbd20 error 4 in libvdr-xineliboutput.so.1.7.28[7f99265ca000+84000] Mar 12 19:56:57 hdvdr1 kernel: [ 2495.471267] iMonLCD: watch [2787]: segfault at 2ab8 ip 7f15d266be86 sp 7f15be7fbd20 error 4 in libvdr-xineliboutput.so.1.7.28[7f15d264+84000] Mar 15 19:59:09 hdvdr1 kernel: [ 7334.664648] iMonLCD: watch [2657]: segfault at 7f1b28075c90 ip 7f1b28075c90 sp 7f1b2effcd68 error 15 Mar 23 20:35:21 hdvdr1 kernel: [24330.004845] iMonLCD: watch [3802]: segfault at 2ab8 ip 7f01953e6e86 sp 7f0192accd20 error 4 in libvdr-xineliboutput.so.1.7.28[7f01953bb000+84000] Mar 29 13:33:24 hdvdr1 kernel: [ 1653.994505] iMonLCD: watch [2825]: segfault at 2ab8 ip 7f45db070e86 sp 7f45ce7fbd20 error 4 in libvdr-xineliboutput.so.1.7.28[7f45db045000+84000] Mar 30 21:30:52 hdvdr1 kernel: [13016.569726] iMonLCD: watch [2794]: segfault at 0 ip (null) sp 7f2ca8ff8d98 error 14 in vdr[40+154000] Apr 3 21:32:08 hdvdr1 kernel: [ 1840.532476] iMonLCD: watch [2817]: segfault at 2ab8 ip 7fdb04c47e86 sp 7fdaf3ffed20 error 4 in libvdr-xineliboutput.so.1.7.28[7fdb04c1c000+84000] Apr 4 21:36:17 hdvdr1 kernel: [ 8452.432894] iMonLCD: watch [2822]: segfault at 2ab8 ip 7f497710fe86 sp 7f496a7fbd20 error 4 in libvdr-xineliboutput.so.1.7.28[7f49770e4000+84000] The lines before are irrelevant and the lines after more or less always the same and just documenting the restart of VDR (I've attached the latest example nevertheless). Cheers, Eric -- System Information: Debian Release: 7.0 APT prefers testing APT policy: (990, 'testing'), (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 3.6.9+vdr1 (SMP w/4 CPU cores) Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages vdr-plugin-xineliboutput depends on: ii libc62.13-38 ii libextractor31:0.6.3-5 ii libgcc1 1:4.7.2-5 ii libstdc++6 4.7.2-5 ii vdr [vdr-abi-1.7.28-debian] 1.7.28-1 vdr-plugin-xineliboutput recommends no packages. vdr-plugin-xineliboutput suggests no packages. -- no debconf information syslog-restart.txt.gz Description: GNU Zip compressed data
Bug#704735: nmu: proftpd-dfsg_1.3.4a-4
On Fri, Apr 5, 2013 at 10:01:03 +0200, Francesco Paolo Lovergine wrote: Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: binnmu Hi this is requested to solve #704484 that prevents mod_tls working due to strict checking against openssl version. Actually the openssl thing in that bug seems to be just a warning, and the actual issue is that mod-vroot disappeared on upgrade. Cheers, Julien signature.asc Description: Digital signature
Bug#704705: [Pkg-ime-devel] Bug#704705: Bug#704705: ibus: cannot use with both Mozilla i386 apps and emacs
Hi Aron, On Fri, Apr 05, 2013 at 03:26:26AM +0200, Toni Mueller wrote: this is actually a good catch, but it does have the drawback that I cannot have both the i386 and amd64 version installed in parallel. today, I have the opposite effect: I can use ibus together with i386 applications, but no longer together with amd64 applications. Seems like restarting ibus-daemon, which I did yesterday, was not enough to see the change. Of course, I need ibus for amd64 applications, too (actually, at least as much as for i386 applications). I am unsure whether the bug should be split into two, one for co-installing the libraries to support multiple architectures of applications in parallel, and one for making it work with all amd64 applications. What do you think? Kind regards, --Toni++ -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#684128: SI units (was Re: failure to communicate)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 04/04/13 22:43, Christian PERRIER wrote: Quoting ian_br...@fastmail.net (ian_br...@fastmail.net): If Debian bug report #684128 proves anything, it is that you will never convince anyone with technical argument, facts advanced in support of I perfectly understand you can be frustrated but, honestly, as of now, we're focused on the wheezy release, again. Fixing debootstrap has much more importance than Giga/Gibibytes. Once wheezy is released, I see no reason for your proposed patch to be rejected. Sadly, it appears that failure to communicate was from both sides Ian was told several times that changes may not be accepted for wheezy However, that communication was overshadowed by several comments suggesting nobody cares about the issue at all, rather than comments like that above explaining the relative importance of fixing other issues. This issue of units comes up again and again, there is a huge thread on debian-devel in 2007[1] - that hardly seems like something that nobody cares about. So while it may not make it into wheezy (I won't give my own opinion on this one, it is for the release team to decide), I don't think the reporter of this bug should be deterred by comments about it being a trivial wishlist or nonsense item. It may actually be useful for the technical committee to review what is on the wiki and make some general statement about Debian's position (if they haven't done so in the past), and that can guide the way similar bugs are classified for jessie and beyond. 1. http://lists.debian.org/debian-devel/2007/06/thrd2.html#00700 2. http://wiki.debian.org/ConsistentUnitPrefixes -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.12 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iQIcBAEBAgAGBQJRXpjBAAoJEOm1uwJp1aqDmTsQAL7tmMmZqoZevDa4ZhfuxGrh R8340K+Fn0aZsYI66bxDHg/HDCJtCGfUpfTOYDnYfsSq+D+4X4ZFTJq6ezKvmbrO mBDCILtq0km753MyfYgnq37/sCbbTrZ/dLKtSWLNioAcqfnqItSC3PqLUYH2l4Tn MeXNCzMHKiG2J3hvWLM3knc3UMq/QGE2DUHzD32mk8zTCU4lAYOEsJOh8CQFKVri oYfGnFlC0Yy6+xf/E1An9Gx80qfRf07vW1odtEIMFmtrotocsj+z3xW1Q8LgwvTA EQ+yXHK7XWSFaruKSbkLyaM826syiRrDBzzTWN9Fi3gptYgJgEY0yGEQViQ6r5SL eosQlxALWLCCG9HOzXLf0HXlKDg4keRI+Ay1BJJkcNurcvF4v70ee4YxmlmD6lXK 2LiK/wb+FBjId0vpDP/kLRjhljt+kdNXe/4hqbc2d3aIY7Gnqjgz1o/I+x6+atrm YIKJM6pGTYrFL2vfsIn1mlrbXnqJEyyD04v7U2afb3n1Dxn9zh/6j7L2R0tv5eLl dCrnBkXjdLMyMaawyzb/uQyP2FvoFjk92XsehKDATLobQBnZvJ7B2ON6qtLWbn1Q jG5BvdMH++jU7m+yDlctcVo0dakgAd8UnQFvckjH1JhPwRIsmBYUbJu0Y8fqY2Gz mbpjVc641/AjIS4ytp10 =L0ZB -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#682143: Debian #682143: gatling: *** glibc detected *** /usr/bin/gatling: double free or corruption (top): 0x088196f0 ***
Hi, thanks for your report! Does the issue still happen with the new gatling version 0.13 in Debian (experimental)? Thanks in advance, Roland -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#703932: apt-transport-https not sending a certificate to the server
On Tue, Apr 02, 2013 at 06:23:14PM +0200, Holger Hans Peter Freyther wrote: On Tue, Apr 02, 2013 at 07:20:10AM +0200, Michael Vogt wrote: I wouldn't be suprised if that would solve your problem. But solving it with gnutls would be prefered. yes, it makes it work. I understand that this is not usable solution for debian. So in terms of moving forward. I think a-t-https gets a fetch request via stdin? Could you give me the x-lines that do that or point me to the documentations? [..] You can trigger the download by sending the following lines: 601 Configuration Config-Item: Acquire::https::SslCert=/path/to/cert Config-Item: Acquire::https::SslKey=/path/to/key 600 URI Acquire URI: https://debian.org Filename: /tmp/output e.g. $ cat cmds | /usr/lib/apt/methods/https should work. Cheers, Michael -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#703855: Aw: Re: Bug#703855: netsniff-ng does not depend on package geoip-database
On Tue, Mar 26, 2013 at 12:33 AM, Daniel Borkmann
borkm...@iogearbox.net wrote:
At first I thought that's a good idea for the long run, then I realized
they might put geoip-database-contrib into contrib
because it requires data outside debian main.
'http://www.debian.org/doc/debian-policy/ch-archive.html' says:
None of the packages in the main archive area require software outside of
that area to function.
I'm not a debian-policy-specialist so I don't know if this sentence is
not only for software but for pure data also.
Yes. For data also :)
Well, to function the toolkit does not need this database, at least for the
tools
netsniff-ng, trafgen, ifpps, bpfc, curvetun. Only flowtop and astraceroute
make use
of it. But I'm not sure what policy applies in that case.
I'll look into issue and provide feedback here. We can't depends on
package outside main to remain in main, else netsniff-ng need to move
to contrib.
--
Kartik Mistry | IRC: kart_
{0x1f1f, kartikm}.wordpress.com
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#704080: unblock: libarchive/3.0.4-3
Hi, On Fri, Apr 05, 2013 at 03:21:43AM +0100, peter green wrote: Specifically it seems that s390x has not successfully built this package for some time (since before s390x stopped being considered a broken and fucked architecture). As a result the s390x package is out of date in both testing and unstable. Britney will not migrate the package if there are out of date binaries in unstable (even if there are also out of date binaries for the same package in testing). The cause of the build failures seems to be a testsuite failure. Afaict there are several options in this scenario. my personal guess is that there's probably nothing s390x-specific to it, it's probably broken with 64bit big endian. The d-ports build for sparc64 fails as well. Kind regards Philipp Kern signature.asc Description: Digital signature
Bug#704709: mahjongg 3.4 segfault with glib 2.36
On 04/05/2013 01:45 AM, Andreas Henriksson wrote: Hello! It seemed like it was common to mis-use the G(tk)Application APIs during the 3.4 era, and many fixes for this was introduced sometime during the 3.6 era. For mahjongg this particular commit seems to fix the startup segfault: https://mail.gnome.org/archives/commits-list/2012-May/msg03719.html (also available at: https://gitorious.org/glassrose-gnome/gnome-games/commit/ce2dc8ce176713a61c740bbd5b5d5b82f6e4ffba?format=patch ) Several other games included in gnome-games seems to have similar programming errors. The gnome-games set has now been split up and games have their own repository and own releases. I wonder if new glib versions should declare a Breaks on gnome-games ( 3.7) I assume gnome-games = 3.7 will be a transitional package of some sorts. I'd rather not add the breaks. If we find other things also break, we can consider whether to add them or to revert the glib change (temporarily). -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#704735: nmu: proftpd-dfsg_1.3.4a-4
On Fri, Apr 05, 2013 at 11:15:57AM +0200, Julien Cristau wrote: On Fri, Apr 5, 2013 at 10:01:03 +0200, Francesco Paolo Lovergine wrote: Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: binnmu Hi this is requested to solve #704484 that prevents mod_tls working due to strict checking against openssl version. Actually the openssl thing in that bug seems to be just a warning, and the actual issue is that mod-vroot disappeared on upgrade. Cheers, Julien Mmmm, about that the mod_vroot module is not strictly required (it is an optional module and not requested in any basic configuration) and currently provided by proftpd-mod-vroot. Here I see a few different choices: - add it as Recommends package - add it as Depends package - add a note about the moving in NEWS (simply missed at the time :-/) - add a note in general notes about upgrading Maybe the better choice is the third. Please, your advice woild be welcome. -- Francesco P. Lovergine -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#704080: unblock: libarchive/3.0.4-3
On Fri, Apr 5, 2013 at 03:21:43 +0100, peter green wrote: Thoughts? should I go file a rc bug about this issue? Yes. Cheers, Julien signature.asc Description: Digital signature
Bug#704623: eglibc: CVE-2013-1914: getaddrinfo() stack overflow
Control: tags -1 + patch Hi Only a small update. Upstream commit: http://sourceware.org/git/?p=glibc.git;a=commitdiff;h=1cef1b19089528db11f221e938f60b9b048945d7 see: http://marc.info/?l=oss-securitym=136515592721172w=2 Regards, Salvatore -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#704742: shishi: FTBFS on s390x and ppc64: quilt is not working because of debian/patches/series missing
Source: shishi Version: 1.0.2-1 Severity: serious Tags: patch experimental Justification: FTBFS on s390x and ppc64 (64-bit big endian ports) Because of debian/patches/series missing, although 3.0 (quilt) is designated in debian/source/format, quilt is not working normally. So, as a result, bug#670316 is reverted and FTBFS on s390x and ppc64 occurs. (Maybe on sparc64, too, but it cannot be sure because of no buildd machine of sparc64's experimental repository now) build logs https://buildd.debian.org/status/package.php?p=shishisuite=experimental http://buildd.debian-ports.org/status/package.php?p=shishisuite=experimental Here is a patch attached. Regards, -- Hiroyuki Yamamoto A75D B285 7050 4BF9 AEDA 91AC 3A10 59C6 5203 04DC diff -Nurd shishi-1.0.2.orig/debian/patches/series shishi-1.0.2/debian/patches/series --- shishi-1.0.2.orig/debian/patches/series 1970-01-01 09:00:00.0 +0900 +++ shishi-1.0.2/debian/patches/series 2013-04-05 18:58:53.0 +0900 @@ -0,0 +1 @@ +64bigendian-ftbfs.diff
Bug#704741: waagent: fails to remove: postrm called with unknown argument `remove'
Package: waagent Version: 1.2-1 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed your package fails to remove. From the attached log (scroll to the bottom...): Removing waagent ... postrm called with unknown argument `remove' dpkg: error processing waagent (--purge): subprocess installed post-removal script returned error exit status 1 Errors were encountered while processing: waagent The prerm script is entirely useless, there is no prerm purge. For the postrm use if [ $1 = purge ] ; then ... fi and avoid all the remaining boilerplate code and comments. The postinst I don't really get - why are there that many rm's on configuration files? The configuration step via waagent --setup --force is not suitable for Debian systems, as it does not preserve user modifications to the configuration files it creates, which is a policy violation. Try e.g. dpkg-reconfigure waagent after editing all the configuration files. cheers, Andreas waagent_1.2-1.log.gz Description: GNU Zip compressed data
Bug#702787: pre-approval: unblock: python-pyrrd/0.1.0-2
Hi, On 04/04/13 20:51, Adam D. Barratt wrote: On Mon, 2013-03-11 at 21:31 +, Jonathan Wiltshire wrote: On Mon, Mar 11, 2013 at 12:45:16PM +0100, Elena Grandi wrote: [...] It fixes important bug #691230 by backporting a small patch from the upstream repository; of course there are no other versions of the package in sid. The package is team-maintained, and the Uploader has been contacted, but didn't answer. Looks fine to me. Please retitle this bug when it is uploaded. Ping? I think this was the upload, still on mentors.d.o though: http://mentors.debian.net/package/pyrrd Regards, -- Steven Chamberlain ste...@pyro.eu.org -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#704080: unblock: libarchive/3.0.4-3
On Fri, Apr 05, 2013 at 12:18:46PM +0200, Philipp Kern wrote: Hi, On Fri, Apr 05, 2013 at 03:21:43AM +0100, peter green wrote: Specifically it seems that s390x has not successfully built this package for some time (since before s390x stopped being considered a broken and fucked architecture). As a result the s390x package is out of date in both testing and unstable. Britney will not migrate the package if there are out of date binaries in unstable (even if there are also out of date binaries for the same package in testing). The cause of the build failures seems to be a testsuite failure. Afaict there are several options in this scenario. my personal guess is that there's probably nothing s390x-specific to it, it's probably broken with 64bit big endian. The d-ports build for sparc64 fails as well. Please also note that the current version (available in experimental for now) seems to build ok on s390x (but fails on other platforms instead).. Using git bisect should help identify the needed relevant changes. Help is welcome. -- Andreas Henriksson signature.asc Description: Digital signature
Bug#698674: Tcl/Tk multiarching
Some comments for the Tcl/Tk multiarch changes, now that the first bits are in Ubuntu 13.04 (raring). - The move of tclConfig.sh tkConfig.sh to the multiarch location did cause some build breakage. In the end we do provide now compat symlinks in /usr/lib to fix the build breakage. This works for most cases, but not if a specific version of Tcl/Tk is targeted, e.g. itcl, itk. So a test rebuild in Debian might be needed before this is done. - From my point of view, the multiarch view is still incomplete. You should be able to install an embedded interpreter of the foreign arch while keeping the interpreter of the native arch installed on the system. E.g. on amd64, install vim for i386, and still have the amd64 tclsh installed. Maybe vim is not a good use case, but e.g. installing an amd64 gdb with the embedded python interpreter on i386 works while keeping the python interpreter on amd64. For Tcl/Tk this would involve to move the required library (text/script) files to the tcllib8.5 package too. Tracking this in Ubuntu in LP: #1164937. Matthias -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#704743: scid: upstream released new version 4.4
Package: scid Version: 1:4.3.0.cvs20120311-1 Severity: wishlist Dear Maintainer, There's a new version of scid available, it would be nice to see this version in debian. Thanks! -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#610629: apt dynamic mmap ran out of room workaround should not be needed with squeeze
On Sat, Mar 30, 2013 at 14:37:50 -0400, David Prévot wrote: It should now be OK for upgrade from Squeeze, here is a straightforward patch. Thanks in advance for your reviews, rewrites, remarks or simple acknowledgments. Acked-by: Julien Cristau jcris...@debian.org Index: en/upgrading.dbk === --- en/upgrading.dbk (révision 9649) +++ en/upgrading.dbk (copie de travail) @@ -1108,35 +1108,6 @@ /section -section id=apt-error-operation -titleErrors running aptitude or apt-get/title -para -If an operation using commandaptitude/command, commandapt-get/command, -or commanddpkg/command fails with the error -/para -!-- TODO (jfs): Review the message, it has changed in apt-get to -Dynamic MMap ran out of room. Please increase the size of APT::Cache-Limit. -Current value: %lu. (man 5 apt.conf) -- -screen -E: Dynamic MMap ran out of room -/screen -para -the default cache space is insufficient. You can solve this by either removing -or commenting lines you don't need in -filename/etc/apt/sources.list/filename or increasing the cache size. -The cache size can be increased by setting literalAPT::Cache-Limit/literal -in filename/etc/apt/apt.conf/filename. The following command will set it -to a value that should be sufficient for the upgrade: -/para -screen -# echo 'APT::Cache-Limit 1250;' gt;gt; /etc/apt/apt.conf -/screen -para -This assumes that you do not yet have this variable set in that file. -/para - -/section - section id=conflicts-loops titleConflicts or Pre-Depends loops/title signature.asc Description: Digital signature
Bug#613235: release-notes: Watchdog during upgrade
On Sat, Mar 30, 2013 at 17:11:25 -0400, David Prévot wrote: Hi Ryan, Le 30/03/2013 16:55, Ryan Tandy a écrit : In micro-evtd in wheezy, the init script's stop action disables the watchdog, so the box won't be killed. Thanks for your input. So nothing needs to be added in that regards for the Wheezy release notes, right? Wrong. The squeeze package's init script will be called during the upgrade to stop the daemon. I had forgotten that the version in squeeze doesn't have that behaviour. I guess it's too late to make that change in squeeze. It’s also too late to edit the Squeeze release notes, so I assume we should close this issue. Disagree. We can still edit the squeeze release notes if necessary... Cheers, Julien signature.asc Description: Digital signature
Bug#701229: epubcheck 3.0
blocked 701229 by 693234 severity 701229 important thanks I cannot use mh_make to generate the mvn debian/* template stuff. It fails with same error as #693234 -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#704744: pbuilder: umounts /{dev,run}/shm of the *host* system
Package: pbuilder
Version: 0.215
Severity: critical
Justification: breaks unrelated software
I’ve just did the following:
① get https://www.mirbsd.org/cvs.cgi/contrib/hosted/tg/deb/pbuilderrc?rev=1.34
and install that file as /etc/pbuilderrc
② edit the MIRROR_wheezy line to use a local mirror
③ remove ~/.pbuilderrc
④ run sudo env DIST=wheezy cowbuilder --create
⑤ run sudo env DIST=wheezy cowbuilder --update
I’ve had /run/shm mounted a tmpfs before, as is normal for
a system running sid, and /dev/shm is a symbolic link pointing
to it.
Now, I don’t have that any more:
tglase@tglase:~ $ mount | fgrep shm; echo $?
1
tglase@tglase:~ $ ls -la /{dev,run}/shm
lrwxrwxrwx 1 root root 8 Apr 3 09:55 /dev/shm - /run/shm
/run/shm:
total 0
drwxr-xr-x 2 root root 40 Apr 5 13:49 .
drwxr-xr-x 26 root root 980 Apr 5 13:45 ..
This breaks unrelated software on the system, i.e. anything
that uses /dev/shm/ stuff. Additionally, it will *remove*
everything currently in there.
I don’t know if it was the --create or the --upgrade though.
Running sudo mount -t tmpfs swap /run/shm followed by
another instance of sudo env DIST=wheezy cowbuilder --update
however keeps the current contents of /dev/shm/ intact, so
I believe it was the --create operation. Similarily, running
sudo env DIST=wheezy cowbuilder --build feistermops_51.dsc
to compile a local package keeps it there.
-- System Information:
Debian Release: 7.0
APT prefers unstable
APT policy: (500, 'unstable')
Architecture: i386 (i686)
Kernel: Linux 3.2.0-4-amd64 (SMP w/4 CPU cores)
Locale: LANG=C, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/mksh-static
Versions of packages pbuilder depends on:
ii coreutils 8.13-3.5
ii debconf [debconf-2.0] 1.5.49
ii debianutils4.3.4
ii debootstrap1.0.48
ii dpkg-dev 1.16.10
ii wget 1.14-1
Versions of packages pbuilder recommends:
ii devscripts 2.12.6
ii fakeroot1.18.4-2
ii sudo1.8.5p2-1+nmu1
Versions of packages pbuilder suggests:
ii cowdancer 0.72
pn gdebi-corenone
pn pbuilder-uml none
-- Configuration Files:
/etc/bash_completion.d/pbuilder [Errno 2] No such file or directory:
u'/etc/bash_completion.d/pbuilder'
-- debconf information:
pbuilder/mirrorsite: http://mirror.virt.tarent.de/mirror/ubuntu
pbuilder/nomirror:
* pbuilder/rewrite: false
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#618776: searching for hold will match packages with that name
On Sat, Mar 30, 2013 at 15:08:47 -0400, David Prévot wrote: On Mon, Mar 21, 2011 at 08:16:08PM +0200, Andrei Popescu wrote: On Ma, 22 mar 11, 00:37:35, Osamu Aoki wrote: On Fri, Mar 18, 2011 at 12:23:42PM +, Owen Dunn wrote: Package: release-notes Chapter 4 of the squeeze release notes asks one to search for holds by typing: dpkg --get-selections | grep hold This will erroneously match any packages whose names contain the string `hold' dpkg --get-selections | grep 'hold$' I guess this should fix it although it complicates things. It is a question of addressing very corner case or keep it simple. $ apt-cache search -n hold holdingnuts-server - poker server holdingnuts - poker client (I have lenny, squeeze, wheezy and sid in sources.list) but those two packages are not present in lenny. Maybe postpone this issue for wheezey? That would mean now then. Please find attached a straightforward patch for this issue. Thanks in advance for your reviews, rewrites, remarks or simple acknowledgments. I wouldn't bother, tbh. It still complicates things, and still has dubious practical benefit. Cheers, Julien signature.asc Description: Digital signature
Bug#704745: oidentd: gives invalidly formatted response (according to PostgreSQL)
Package: oidentd Version: 2.0.8-4 Severity: important Hi, I am using the ident method in PostgreSQL's pg_hba.conf. PostgreSQL (version 8.4.16-0squeeze1) complains about oidentd's response; in it's log it says: 2013-04-05 13:34:40 CEST LOG: invalidly formatted response from Ident server: 52350,5432:ERROR:NO-USER I've replaced oidentd with pidentd, using same PostgreSQL configuration (and no configuration whatsoever of oidentd or pidentd). It now works just fine. Bye, Joost -- Joost van Baal-Ilić http://abramowitz.uvt.nl/ Tilburg University mailto:joostvb.uvt.nl The Netherlands signature.asc Description: Digital signature
Bug#683838: release-notes: transition: pdksh → mksh
On Sat, Aug 4, 2012 at 17:43:47 +, Thorsten Glaser wrote:
Package: release-notes
Severity: normal
Hi,
Robert asked me to replace pdksh with its successor mksh
in time for the wheezy release, and we’d like it to be
gone in jessie. Right now, pdksh is a transitional package,
and the upgrade might need some sysadmin and/or user effort:
① The sysadmin needs to change all users’ shells from pdksh
to mksh (login with pdksh will still be possible but lack
basic human rights such as tab completion).
② Everyone with #!/bin/pdksh (and possibly #!/bin/ksh which
is update-alternatives managed) scripts should check that
they continue to run with /bin/pdksh aka /bin/lksh (the
compatibility binary in mksh) or, better, port them to run
with /bin/mksh to get all bugfixes (lksh re-introduced a
few “bugs” when legacy behaviour would be needed by user
scripts).
Proposed text, as asked for in the d-d-a mail from Adam,
attached, although it should probably be run through the
l10n-en team first. (And someone should decide whether my
explanation about /bin/{pd,l,m,}ksh from this mail belongs
into it. I found it a bit lengthy already, but us Germans
tend to write convolutedly.)
That sounds appropriate for a pdksh NEWS.Debian file, not the release
notes?
We can add pdksh to the list of packages that are going away after
wheezy, though.
Cheers,
Julien
signature.asc
Description: Digital signature
Bug#684128: failure to communicate
On 4 April 2013 20:47, ian_br...@fastmail.net wrote: On Thu, 4 Apr 2013 19:09:04 +0200 Christian PERRIER bubu...@debian.org wrote: This mail is a very good argument to confirm that overcomplicated methods to make your point will just fail. If you have a point to make it, make ti. Once. With facts. I supplied plenty of facts. I was not following this bug report but reading it, it reminds me of the Unit Policy [1] that got approved and is gradually implemented in ubuntu/debian packages. Looking at d-i the usage is mostly correct sans 'k' should only be used lower-cased with current base-10 units. The major problem with changing these is that same prefixes are accepted for pre-seeding and it would be ill-advised to change those, thus backwards compatability must be preserved in the values that can be preseeded as well as entered by the user. The default to base-10 units, is good as majority of the installer deals with HDD drives (not SSD) and not RAM. If I have 1TB drive and want half of it for one thing and 1/4 for this and 1/4 for that, no space should be left on the drive. Hence matching and using same units as disk-manufacturers is good. The case where we mix match = e.g. making swap big enough (base-10) for RAM size (base-2) is tricky. And it's something to consider in the UI. I understand your frustration, but as it happens installer work/improvements becomes a hot topic post-freeze as this is when people start to use the installer, notice things and try to write features. And all of these features will only land for the next cycle with a release in ~= 2 years time. Tell me about bad timing, eh?! =) W.r.t. boundry alignments, I believe it its already aligning at 2048 by default and there is ongoing work to align with 4K boundries properly. But note that boundry alignment has little to do with user displaying/specifying amount of gigaheaps one wants to be allocated where. Everyone seems to agree to bring support to input/output Ki/Mi etc prefixes. That's a feature and can only go into jessie branches and or wait for wheezy release. Once that lands we can bike shed to death where to display what units and what to default to where going forward. [1] https://wiki.ubuntu.com/UnitsPolicy Regards, Dmitrijs. ps. there are disk manufactures that mix base-2 and base-10 units. E.g. using one to calculate 1MB and then using the other multiply and gain GB/TB factors /o\ -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#704746: ITP: r-cran-armadillo -- R bindings to Armadillo C++ linear algebra library
Package: wnpp Owner: Dirk Eddelbuettel e...@debian.org Severity: wishlist * Package name: r-cran-armadillo Version : 0.3.800.1-1 Upstream Author : Dirk Eddelbuettel et al (for RcppArmadillo), Conrad Sanderson (for Armadillo) * URL or Web page : http://dirk.eddelbuettel.com/code/rcpp.armadillo.html * License : GPL (= 2) [for RcppArmadillo], MPL 2 [for Armadillo] Description : R bindings to Armadillo C++ linear algebra library RcppArmadillo is becoming more popular within the R world, there are now about 30 CRAN packages which use it -- and that now includes Amelia (which is packaged as r-cran-amelia) so we need it in Debian anyway. I am upstream and should be able to provide concurrent releases within Debian as I have done for years with Rcpp (that this packages depends upon). -- Dirk Eddelbuettel | e...@debian.org | http://dirk.eddelbuettel.com -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#684128: SI units (was Re: failure to communicate)
Daniel Pocock writes (SI units (was Re: failure to communicate)): It may actually be useful for the technical committee to review what is on the wiki and make some general statement about Debian's position (if they haven't done so in the past), and that can guide the way similar bugs are classified for jessie and beyond. 1. http://lists.debian.org/debian-devel/2007/06/thrd2.html#00700 2. http://wiki.debian.org/ConsistentUnitPrefixes You should try to address this through the policy process. If and when we have competing policy proposals the TC might want to arbitrate. Ian. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#701769: new location for wheezy-backports
On Sat, Mar 30, 2013 at 14:08:18 -0400, David Prévot wrote: Control: tags -1 patch Hi, Le 26/02/2013 17:07, Ansgar Burchardt a écrit : the wheezy-backports is no longer located in backports.debian.org. It is now included on ftp.*.debian.org (it's already there[1]). [1] http://ftp.de.debian.org/debian/dists/ I think it would be good to mention this in the release notes. Here is a proposed patch, recycling the stable-updates section. Thanks in advance for your reviews, rewrites, remarks or simple acknowledgments. BTW, is it planned to make a stable-backports - wheezy-backports symlink (if so, I’d use stable-backports instead of wheezy-backports in the section title)? Please leave the stable-updates section alone, and make a new one for backports. Thanks, Julien signature.asc Description: Digital signature
Bug#700212: Note that the GlobalSign document is clear about the requirements and audits
Note that the GlobalSign document is clear about the requirements and audits From https://www.globalsign.com/certificate-authority-root-signing/ GlobalSign Organizations using Trusted Root must meet the operational best GlobalSign practices in effect for Certificate Authorities, including GlobalSign compliance with CA/B Forum baseline requirements. For that GlobalSign reason, there are a number of technical, procedural, contractual GlobalSign requirements that must be met and maintained via regular auditing. GlobalSign Trusted Root is a select service with strict requirements. Trusted GlobalSign Root is both technically and contractually prohibited from being GlobalSign used for deep packet inspection/scanning of outbound/inbound HTTPS traffic. If they really enforce this, those cross-signed CAs are probably as secure as any of the other non-top-5 CAs already in Debian's CA bundle. Note especially the requirement of meating the CA/B Forum baseline requirements, which I believe are very close to Debian's and Mozilla's inclusion requirements. Examples of GlobalSign cross signed certificates that I have encountered are various cheaper, but popular CAs such as AlphaSSL (https://www.alphassl.com/repository/) Our company currently uses GlobalSign root derived certificates for many things, including an AlphaSSL wildcard certificate for our less important sites, so far they seem to be very thorough and trustworthy, even a simple renewal of an EV SSL certificate can take more than a month of detailed vetting of our existing identity, where they even insist on the ability to verify information that does not go in the certificate (and is thus not certified to those who trust the certificate). Enjoy Jakob -- Jakob Bohm, CIO, Partner, WiseMo A/S. http://www.wisemo.com Transformervej 29, 2730 Herlev, Denmark. Direct +45 31 13 16 10 This public discussion message is non-binding and may contain errors. WiseMo - Remote Service Management for PCs, Phones and Embedded -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#702787: pre-approval: unblock: python-pyrrd/0.1.0-2
On 2013-04-05 at 11:55:17 +0100, Steven Chamberlain wrote: I think this was the upload, still on mentors.d.o though: http://mentors.debian.net/package/pyrrd That's the upload, request for sponsorship is at #702864; I didn't ping mentors@d.o after a couple weeks because in the meanwhile the new freeze rules came into being. (and then I forgot to close this bug and wait for jessie to resubmit the fix, sorry) -- Elena ``of Valhalla'' -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#704747: RFP: hidclient -- Virtual Bluetooth keyboard and mouse
Package: wnpp Severity: wishlist * Package name: hidclient Version : 2012-06-27 Upstream Author : anselm martin hoffmeister ans...@hoffmeister.be * URL : http://anselm.hoffmeister.be/computer/hidclient/ * License : GPL? Programming Lang: C Description : Virtual Bluetooth keyboard and mouse http://anselm.hoffmeister.be/computer/hidclient/ Thanks a lot. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#704748: task-gnome-desktop: uninstallable on kfreebsd-*
Source: task-gnome-desktop Version: 3.14+nmu1 Severity: serious Tags: d-i pending Package has a Depends on network-manager-gnome which cannot be satisfied on kfreebsd-amd64. Package has a Depends on network-manager-gnome which cannot be satisfied on kfreebsd-i386. On 25/02/13 06:19, Christian PERRIER wrote: Uh-oh, I think that should have been linux-any; we don't have network-manager on kfreebsd-*, so this will make task-gnome-desktop uninstallable. I committed a fix in the master branch. I'd better open this RC bug, just to make absolutely sure this isn't forgotten about, and also to point at when asking for an unblock. Thanks! -- System Information: Debian Release: wheezy/sid APT prefers testing APT policy: (500, 'testing'), (1, 'experimental') Architecture: kfreebsd-amd64 (x86_64) Kernel: kFreeBSD 9.0-2-amd64-xenhvm Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#704723: apt: Upgrade to apt_0.9.7.9~exp2 fails because of attempted overwrite of manpages
Control: clone -1 -2 Control: reassign -2 apt 0.9.7.8~exp1 Control: retitle -2 apt: Needs to Replace manpages-it due to new Italian man pages Control: severity -2 serious On Fri, 2013-04-05 at 08:45:27 +0800, Daniel Hartwig wrote: On 5 April 2013 08:10, Matteo Settenvini matteo...@member.fsf.org wrote: Package: apt Version: 0.9.7.8 Severity: normal I think there is something wrong with the files included in the apt package from experimental. Since packages from experimental sooner or later land into unstable, it's good to fix this before the next release. ^_^ I gather that localized manpages should not distributed with the apt package. Actually, they should. Previously some translations were missing from the apt binaries, but this is fixed in 0.9.7.8~exp1. In that case apt needs to Replace the manpages-it package. It is manpages-it that should not include those files. Following the example of other translated man page packages (i.e. manpages-fr, manpages-de), man pages for applications should not be included and, where currently provided, should instead be contributed to application packaging. When those are not shipped anymore in manpages-it then the Replaces can be restricted to an older-than version. There are many in manpages-it. At least these need to be removed, to cede the space to apt: /usr/share/man/it/man5/sources.list.5.gz /usr/share/man/it/man8/apt-cdrom.8.gz Also I see dpkg, gnumeric, dselect, bash, and many more which should be dropped or moved to their respective application packaging. That would be ideal, yes. Thanks, Guillem -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#681185: libreoffice: Opening a document when LO is already running returns too early
On Wed, Apr 03, 2013 at 08:57:51PM +0200, Antos Andras wrote:
I hope the fixed 3.6.2 version gets in testing or stable soon.
testing? Yes, when I upload it (well, 4.x most probably) after wheezy
release.
stable? For sure with jessie in ~3 years...
(but I might *try* to get the fix[1] into a stable update which is needed
anyway due to other stuff which missed the time in before it became
impossible to to do it (see #703602). And it'll be in wheezy-backports...
Regards,
Rene
[1]
http://cgit.freedesktop.org/libreoffice/core/commit/?h=libreoffice-3-6-2id=da329b8bb04f5d6a5c89afb7f083c7de679d5691:
rom da329b8bb04f5d6a5c89afb7f083c7de679d5691 Mon Sep 17 00:00:00 2001
From: Stephan Bergmann sberg...@redhat.com
Date: Thu, 06 Sep 2012 10:43:54 +
Subject: deb#681185: wait for InternalIPC::ProcessingDone in oosplash
Change-Id: I9606ec34ad0d8d24dca71d060bf5e1d37152903c
(cherry picked from commit 5c804dce946a928adcaf97533f5345b33e688ff5)
Reviewed-on: https://gerrit.libreoffice.org/569
Reviewed-by: Michael Meeks michael.me...@suse.com
Tested-by: Michael Meeks michael.me...@suse.com
---
diff --git a/desktop/unx/source/start.c b/desktop/unx/source/start.c
index d1a09a7..8fe4774 100644
--- a/desktop/unx/source/start.c
+++ b/desktop/unx/source/start.c
@@ -512,6 +512,17 @@ send_args( int fd, rtl_uString *pCwdPath )
nLen = rtl_string_getLength( pOut ) + 1;
bResult = ( write( fd, rtl_string_getStr( pOut ), nLen ) == (ssize_t) nLen
);
+if ( bResult )
+{
+char resp[ strlen( InternalIPC::ProcessingDone ) ];
+ssize_t n = read( fd, resp, SAL_N_ELEMENTS( resp ) );
+bResult = n == (ssize_t) SAL_N_ELEMENTS( resp )
+ (memcmp(
+resp, InternalIPC::ProcessingDone,
+SAL_N_ELEMENTS( resp ) )
+== 0);
+}
+
/* cleanup */
rtl_uString_release( pEscapedCwdPath );
rtl_uString_release( pBuffer );
--
cgit v0.9.0.2-2-gbebe
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#668332: Bug#643337: dpkg: start-stop-daemon can't handle script daemon
Hi. No, this all looks right, --name should usually be used on interpreted scripts and --exec otherwise. Using --name might not always be possible: start-stop-daemon: warning: this system is not able to track process names longer than 15 characters, please use --exec instead of --name. Now, even with a shorter name, I can't get it to work. For the record, I replaced the above by something like this: start-stop-daemon --start --quiet --pidfile $PIDFILE --startas $DAEMON \ --name $NAME --test /dev/null \ || return 1 start-stop-daemon --start --quiet --pidfile $PIDFILE --startas $DAEMON \ --name $NAME -- \ $DAEMON_ARGS \ || return 2 Here's what I have in my init script: start-stop-daemon --start --quiet --background --make-pidfile --chuid=$DAEMONUSER --pidfile $PIDFILE --startas $DAEMON --name $NAME --test /dev/null \ || return 1 start-stop-daemon --start --quiet --background --make-pidfile --chuid=$DAEMONUSER --pidfile $PIDFILE --startas $DAEMON --name NAME -- \ $DAEMON_ARGS \ || return 2 I'm using: NAME=python_script DAEMON=path_to_script/$NAME DAEMON_ARGS=--args When using start option, the pid file is created, but the name in /proc/pid/stat is python, therefore, when calling start again, a new instance is created. If I do it this way: NAME=python DAEMON=/usr/bin/python DAEMON_ARGS=path_to_script/python_script --args s-s-d will only allow one instance. Yet, it does not look so nice. And the status command outputs [ ok ] python is running. Is this the recommended way ? Or did I miss something ? By the way, while investigating this, I stumbled across this thread: http://dev.gentoo.org/~vapier/openrc/projects/openrc/ticket/164.html where there is talk about daemonizing a perl script. Apparently, s-s-d was modified to add an --interpreted flag. Not sure this is relevant. -- Jérôme -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#704746: ITP: r-cran-armadillo -- R bindings to Armadillo C++ linear algebra library
On 5 April 2013 at 07:02, Dirk Eddelbuettel wrote: | | Package: wnpp | Owner: Dirk Eddelbuettel e...@debian.org | Severity: wishlist | | * Package name: r-cran-armadillo Sorry: r-cran-rcpparmadillo Seems like I no longer remember the name of own [upstream] packages ... Dirk | Version : 0.3.800.1-1 | Upstream Author : Dirk Eddelbuettel et al (for RcppArmadillo), | Conrad Sanderson (for Armadillo) | * URL or Web page : http://dirk.eddelbuettel.com/code/rcpp.armadillo.html | * License : GPL (= 2) [for RcppArmadillo], MPL 2 [for Armadillo] | Description : R bindings to Armadillo C++ linear algebra library | | RcppArmadillo is becoming more popular within the R world, there are now | about 30 CRAN packages which use it -- and that now includes Amelia (which | is packaged as r-cran-amelia) so we need it in Debian anyway. | | I am upstream and should be able to provide concurrent releases within Debian | as I have done for years with Rcpp (that this packages depends upon). | | -- | Dirk Eddelbuettel | e...@debian.org | http://dirk.eddelbuettel.com -- Dirk Eddelbuettel | e...@debian.org | http://dirk.eddelbuettel.com -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#704534: base: Concurrency on ressource access when connecting with same user on multiple terminals. Might be a design problem.
Clearly those application where not designed in regard of this use case, but my point is about the fact that X was or was not designed for this and if it was : is it normal that application defeats this purpose that easily ? The problem I raise, is about the fact that when we always use linux as workstation, we more or less forget that X-Window was designed as a network application and we get used to use it like Windoze, and we might often not see that more and more application are not respectfull of this philosophy. I raised this as base, because I don't know what is the cause of this very general behaviour and I'd like to make clear, if X was designed in regard of this use case, and then, if there is a design flaw, may be in programming guidelines, which makes possible such problems.
Bug#684128: SI units (was: failure to communicate)
Am Freitag, den 05.04.2013, 12:59 +0100 schrieb Dmitrijs Ledkovs: The default to base-10 units, is good as majority of the installer deals with HDD drives (not SSD) and not RAM. SSD manufactures use base-10 units, too. Even 128 GB SSDs have 128 * 10^9 bytes for the users, but 128 * 2^30 bytes internally. The difference between 128 GiB and 128 GB (9.44 GB) is used for over-provisioning. ps. there are disk manufactures that mix base-2 and base-10 units. E.g. using one to calculate 1MB and then using the other multiply and gain GB/TB factors /o\ I know one example: The 1.44 MB labeled floppy, which contains twice as much space as a 720 KB floppy. The 720 KB floppy has 720 KiB and the 1.44 MB has 2 * 720 KiB = 1.44 * 1000 * 1024 bytes = 1.41 MiB = 1.47 MB! -- Benjamin Drung Debian Ubuntu Developer -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#698336: gnome-packagekit should have an easy way to add new sources
On Thu, Jan 17, 2013 at 12:47:12PM +0530, Praveen A wrote: package: gnome-packagekit severity: normal In normal cases this can be considered a wishlist bug, but since this is the default package management program installed with CD 1, I think this feature is important when a user just downloads only CD 1. Since we can't fit most required packages in CD 1 a user would want to scan more cds or dvds or add a network mirror after installation. Currently gnome-packagekit does not have these options. So we should have 1. Easy way to scan more cds, dvds or usb/local disk repos (synaptic already has an option to add cdroms) 2. Easy way to add a network repository similar to how the installer does it. Debian Installer might already have the full mirror list. (this could be a good addition to synaptic as well) We previously used software-properties-gtk to do this; and forgot to look at that when switching to PackageKit. A full mirror list is available in python-apt-common in the following file: /usr/share/python-apt/templates/Debian.mirrors We cannot fix this for wheezy anymore, as it's too late for that; but we'll try to have an easier way to add new sources back again in jessie. software-properties-gtk is still available for manual installation, though; but might not be in the best shape currently. -- Julian Andres Klode - Debian Developer, Ubuntu Member See http://wiki.debian.org/JulianAndresKlode and http://jak-linux.org/. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#669726: release-notes: Please document tmpfs filesystem changes for wheezy
On Mon, Apr 1, 2013 at 08:38:30 +0900, Charles Plessy wrote: + Applications which create excessively large temporary files always + only in filename class='directory'/tmp/filename while not + honoring literalTMPDIR/literal may cause + filename class='directory'/tmp/filename to run out of free space. + Such applications should not force to use + filename class='directory'/tmp/filename, and require fixing. + Please consider filing a bug report against the application in + question if you experience such an occurrence. Two comments: - I don't think the last two sentences are particularly helpful in the RN, so I'd drop them - I'm confused by the bit about TMPDIR, since we don't say anything about setting that variable anywhere, so even if an app obeys TMPDIR if it's set, it'll still fill up /tmp by default. Cheers, Julien signature.asc Description: Digital signature
Bug#529629: Add a note about ext3 option data change from ordered to writeback
On Sun, Mar 31, 2013 at 18:22:03 -0400, David Prévot wrote: Hi Giuseppe, Le 31/03/2013 18:05, Giuseppe Sacco a écrit : Il giorno sab, 30/03/2013 alle 12.27 -0400, David Prévot ha scritto: [...] Starting with 2.6.30 kernels, ext3 default mount option is now data=writeback instead of data=ordered. If you have data=ordered in /etc/fstab then you will not be able to mount read/write your file system after upgrading kernel from 2.6.29. From what I understand, this will have to be mentioned in the Squeeze release notes. Is this issue still relevant for Wheezy? Could you please better explain what kind of more information do you request? The bug report is still valid since squeeze release notes were never updated in order to mention it and its workaround. It might be a bit too late to fix the Squeeze release notes, OMMV. If a sane patch was available then I don't see why we shouldn't update the squeeze rn. Cheers, Julien signature.asc Description: Digital signature
Bug#697617: jenkins: CVE-2013-0158: remote code execution vulnerability
On Fri, Apr 5, 2013 at 4:11 AM, Henri Salo he...@nerv.fi wrote: Is there something that I could help to get this bug fixed and closed? Please contact me in case you want any help. Hi Henri, The bug is already fixed in jenkins/1.480.2+dfsg-1~exp1. It was not feasiable to backport the fix to the version available in testing (1.447.2+dfsg-3) so unfortunately it was removed from the next stable release. AFAICT, the plan is to wait for 1.480.2+dfsg-1 to reach testing when jessie development cycle begins and backport that release to wheezy. Cheers, -- Miguel Landaeta, miguel at miguel.cc secure email with PGP 0x6E608B637D8967E9 available at http://keyserver.pgp.com/ Faith means not wanting to know what is true. -- Nietzsche -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#556393: Document the need of a restart of GNOME session during update
On Sat, Mar 30, 2013 at 12:36:50 -0400, David Prévot wrote: Is this issue still relevant for Wheezy? Yes. Cheers, Julien signature.asc Description: Digital signature
Bug#704285: release-notes: Debian doesn't support LSB 3.2
cc:ing the lsb maintainer On Sun, Mar 31, 2013 at 01:22:59 -0700, Jonathan Nieder wrote: Package: release-notes Version: r9650 Tags: wheezy patch Hi, If I understand the lsb packaging correctly, Debian aims at support for LSB 4.1 these days instead of LSB 3.2. More importantly, the Linux Standard Base Desktop Specification (both version 3.2 or 4.1) says: The libraries listed in Table 3-1 shall be available on a Linux Standard Base - Desktop system, with the specified runtime names. [...] libqt-mtlibqt-mt.so.3 but wheezy does not include that library. This says supports but not conforms to. I hope readers understand the distinction. Thanks, Jonathan Index: whats-new.dbk === --- whats-new.dbk (révision 9650) +++ whats-new.dbk (copie de travail) @@ -362,7 +362,10 @@ /programlisting para -Debian still supports Linux Standard Base (acronymLSB/acronym) version 3.2. +Debian supports Linux Standard Base (acronymLSB/acronym) version 4.1. +It also supports most Linux Standard Base Desktop 4.1 interfaces, with +the exception that instead of including both Qt 3 and Qt 4, it only +includes Qt 4. indextermprimaryLinux Standard Base/primary/indexterm /para Didier, care to ack/nak? Cheers, Julien signature.asc Description: Digital signature
Bug#704286: release-notes: dselect being ancient is not new
On Sun, Mar 31, 2013 at 01:28:10 -0700, Jonathan Nieder wrote: Package: release-notes Version: r9650 Tags: wheezy patch Hi, The What's new section contains a note pointing out that dselect is not very well supported any more. That is not new. Thanks, I dropped that note. This section also has some advice about which tools to use to perform the upgrade. If that advice should be included in the release notes at all, it certainly does not belong in the What's new section. An appropriate place would be the Updating packages instructions, which already say to run apt-get dist-upgrade Leaving this bug open until I get to the upgrading chapter and figure out where to put that advice. Cheers, Julien signature.asc Description: Digital signature
Bug#704559: monobristol: wrong/missing dependency libmono-corlib4.0-cil/libmono-corlib2.0-cil
Control: tags -1 + moreinfo On 2013-04-03 00:35:13, Christian Weikusat wrote: The assembly mscorlib.dll was not found or could not be loaded. It should have been installed in the `/usr/lib/mono/2.0/mscorlib.dll' directory. Installing libmono-corlib2.0-cil fixed this problem. This problems seems to be fixed in 0.60.3-2.1. Could you please try the new version? Regards -- Sebastian Ramacher signature.asc Description: Digital signature
Bug#695069: cmus: remaining time is wrong when using ALSA PulseAudio sink
I'm facing the same issue and use the following work-around to avoid the problem: :set output_plugin=pulse. Hope that will help waiting for a real fix. Cheers. Le lundi 3 décembre 2012 23:10:02 UTC+1, Dominik George a écrit : Package: cmus Version: 2.5.0-1, 2.4.3-2 Severity: normal -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 The remaining time of each and every track in my library is off by 24 seconds when using the ALSA output module. Relevant parts of ~/.cmus/autosave: set dsp.alsa.device=default set dsp.ao.buffer_size=16384 set dsp.ao.driver= set dsp.ao.wav_counter=1 set dsp.ao.wav_dir=/home/nik set mixer.alsa.channel=PCM set mixer.alsa.device=default set mixer.pulse.restore_volume=1 set output_plugin=alsa I use the PulseAudio sink for ALSA and guess this is related. The funny thing is that cmus starts counting down at $length - 24 seconds, then when reaching 0:00 (which is 24 seconds before the real end of the track) the status ba skips to the next tack and then stats the countdown at $length. eal playback of that tack then begins 24 seconds late, setting the ocunter 24 seconds off once again ... So the complete status display is 24 seconds off compared to real audio. - -- System Information: Debian Release: wheezy/sid Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.6-trunk-amd64 (SMP w/2 CPU cores) Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/mksh Versions of packages cmus depends on: ii libao4 1.1.0-2 ii libasound2 1.0.25-4 ii libc6 2.13-37 ii libcddb21.3.2-3 ii libcdio-cdda1 0.83-4 ii libcdio13 0.83-4 ii libfaad22.7-8 ii libflac81.2.1-6 ii libmad0 0.15.1b-7 ii libmodplug1 1:0.8.8.4-3 ii libmpcdec6 2:0.1~r459-4 ii libncursesw55.9-10 ii libogg0 1.3.0-4 ii libtinfo5 5.9-10 ii libvorbis0a 1.3.2-1.3 ii libvorbisfile3 1.3.2-1.3 ii libwavpack1 4.60.1-3 Versions of packages cmus recommends: ii cmus-plugin-ffmpeg 2.4.3-2 ii libpulse0 2.0-6 cmus suggests no packages. - -- no debconf information -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.12 (GNU/Linux) iQFOBAEBAgA4BQJQvSKpMRpodHRwczovL3d3dy5kb21pbmlrLWdlb3JnZS5kZS9n cGctcG9saWN5LnR4dC5hc2MACgkQWfyOHW8qgAGJwAf+N9l62FZ9w9KgI2sVtSLY bkORwY25TtDyBCoAry5tz+9hR/V1tx+xU2oIWZIaBfPmh3fONun6ugQAhLSf/s+d A8ClM7FWJgO2UsQ0g0ZTOiezFawtjhhWU9oeKzAhxpPbhH64k/YA3v1qVn94WNWm ykJwe67YmPFS+bKkz6vXmIHJ1erAiBldmfp1yQ3xy5gpqy3FzReYTvM025SzrgwW Qh+/ot/waps7VpLRil+RmkP53jzkCZMIqtr3dMD6OwKB/A5GLILXj3ckWe/8EA89 oRapmkx2F4FD+AKECAIqqJmTsaXSEfAd37lLO5tSO+zcSgdn6bHq6y3cjZs84ZLa HA== =czwY -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#704750: src:linux: Please enable Yama LSM
Source: linux Severity: wishlist X-Debbugs-Cc: tails-...@boum.org Hi, TL;DR - please enable enable SECURITY and SECURITY_YAMA_STACKED. as the maintainers of the Debian Linux kernel surely know, the Yama LSM collects a number of system-wide DAC security protections that are not handled by the core kernel itself, including ptrace scope restrictions on which user/process can examine the memory and running state of other processes. Details can be found in Documentation/security/Yama.txt. It was considered [1] for backporting in the Wheezy kernel, but did not make it eventually. Yama is part of the mainline Linux kernel since 3.4. Moreover, since Linux 3.7, the Yama LSM can be automatically stacked regardless of which security module is the primary module, so it's compatible with AppArmor. [1] https://lists.debian.org/debian-kernel/2012/06/msg00074.html I've been testing Yama, combined with AppArmor, on my main Wheezy desktop system since February, compiling every kernel from Debian experimental (starting with 3.7.8-1~experimental.1, until current 3.8.5-1~experimental.1) with the `SECURITY_YAMA` and `SECURITY_YAMA_STACKED` options enabled. I've not noticed any regression. Regarding the ptrace_scope setting: * The default is 1 (restricted ptrace). * Ubuntu has been running with something equivalent to the default mode (1) since 10.10, so most serious blockers should have been resolved hopefully. * I've been running it in the stricter 2 - admin-only attach mode, instead of the default 1 - restricted ptrace one, and did not notice any issue. However, this setting is supposed to break various crash handlers, so it's probably not an option for default Debian installations. So, I suggest we keep the default value (1) for Jessie. The beginning of the Jessie development cycle seems like a good time to bring such changes in, so I suggest Yama is enabled in our 3.8+ kernels once the kernel team is done with their last Wheezy-related urgent tasks :) Cheers, -- intrigeri | GnuPG key @ https://gaffer.ptitcanardnoir.org/intrigeri/intrigeri.asc | OTR fingerprint @ https://gaffer.ptitcanardnoir.org/intrigeri/otr.asc -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#672318: chirp 0.3.0-0.1 Debian package available
On Friday, April 05, 2013 02:46:15, David A Aitcheson wrote: Chris, Did you try the Chirp-Daily package? It is almost DAILY in its updates and working FB for me on Ubuntu 12.04-LTS. I'm running Debian Sid/Unstable. Please look at https://launchpad.net/ubuntu/+source/chirp before you proceed much more. The above package shows version 0.1.12 -- it wouldn't have worked for me. And besides, I've actually /completed/ packaging 0.3.0 (AFAIK, except if there are further desired changes) -- and I'm actually using it, and it does the job I need it to do. ;-) The PPA for chirp is at https://launchpad.net/~dansmith/+archive/chirp-snapshots I've often had issues using Ubuntu PPAs on Debian. Sometimes they work... sometimes they don't, due to differences between the distributions, usually in dependencies. Now... having a look at it, the closest package that would fit in the PPA would be the one for Precise (because Debian Sid is by definition 6 months newer than Ubuntu releases), but the chirp-daily package for Precice in this PPA doesn't have a version available for amd64. I've downloaded the source package so I can have a look and compare it with the packge I just put together. Dave - KB3EFS PS - A fork similar to this is what caused all the problems with NODE. Did we not learn anything from that drawn out over more than a decade mess? Debian packages are generally based on stable tested versions of upstream projects rather than daily builds, so (AFAIK) it would probably not be fitting to pull this Ubuntu PPA package into Debian. The main issue I know about with the node package was the naming conflict; I wasn't aware of the fork issue. This isn't a fork of of the chirp package, it's just a different package version of the same software with the same name. -- Chris -- Chris Knadle chris.kna...@coredump.us -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#691851: using logrotate hint
according to the error message it would be possible to add a line like this to /etc/logrotate.d/lastfmsubmitd and fix this as well: su root lastfm not tested however. Greets Alex -- »With the first link, the chain is forged. The first speech censured, the first thought forbidden, the first freedom denied, chains us all irrevocably.« (Jean-Luc Picard, quoting Judge Aaron Satie) *** GnuPG-FP: 02C8 A590 7FE5 CA5F 3601 D1D5 8FBA 7744 CC87 10D0 *** -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#702787: pre-approval: unblock: python-pyrrd/0.1.0-2
Hi Elena, On 05/04/13 13:02, Elena ``of Valhalla'' wrote: That's the upload, request for sponsorship is at #702864; I didn't ping mentors@d.o after a couple weeks because in the meanwhile the new freeze rules came into being. I'm not familiar with the process for that, but is that filed properly? Package: sponsorship-request; Maintainer for sponsorship-request is (unknown); (and then I forgot to close this bug and wait for jessie to resubmit the fix, sorry) Why not have it uploaded to sid anyway? If it is really too late to get an unblock, it will migrate to jessie right after release. Thanks! Regards, -- Steven Chamberlain ste...@pyro.eu.org -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#704751: nova-consoleauth 2013.1-1 conflict with nova-console 2013.1-1
Package: nova-consoleauth
Version: 2013.1-1
Severity: important
Dear Maintainer,
nova-consoleauth 2013.1-1 conflicts with nova-console 2013.1-1
# apt-get install nova-consoleauth
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following NEW packages will be installed:
nova-consoleauth
0 upgraded, 1 newly installed, 0 to remove and 13 not upgraded.
2 not fully installed or removed.
Need to get 0 B/1,407 kB of archives.
After this operation, 1,455 kB of additional disk space will be used.
Selecting previously unselected package nova-consoleauth.
(Reading database ... 282791 files and directories currently installed.)
Unpacking nova-consoleauth (from .../nova-consoleauth_2013.1-1_all.deb) ...
dpkg: error processing
/var/cache/apt/archives/nova-consoleauth_2013.1-1_all.deb (--unpack):
trying to overwrite '/etc/init.d/nova-consoleauth', which is also in package
nova-console 2013.1-1
Processing triggers for man-db ...
Errors were encountered while processing:
/var/cache/apt/archives/nova-consoleauth_2013.1-1_all.deb
E: Sub-process /usr/bin/dpkg returned an error code (1)
# dpkg -l|grep nova-console
ii nova-console 2013.1-1
all OpenStack Compute - console
ic nova-consoleauth 2013.1-1
all OpenStack Compute - Console Authenticator
# ls -l /etc/init.d/nova-console*
-rwxr-xr-x 1 root root 3186 Apr 4 12:09 /etc/init.d/nova-console
-rwxr-xr-x 1 root root 3224 Apr 4 12:09 /etc/init.d/nova-consoleauth
Packages retrieved from the gplhost.com grizzly repo. Trying to
install OpenStack Grizzly with packages on Debian 3.8 experimental,
following the DevStack model.
More information on http://debian.netside.net/xps13_openstack.html
Best regards,
--Mitch Halmu
-- System Information:
Debian Release: 7.0
APT prefers testing-proposed-updates
APT policy: (500, 'testing-proposed-updates'), (500, 'unstable'), (500,
'testing'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 3.8-trunk-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 nova-consoleauth depends on:
ii dpkg 1.16.10
ii lsb-base 4.1+Debian9
ii nova-common 2013.1-1
ii python 2.7.3-4
nova-consoleauth recommends no packages.
nova-consoleauth suggests no packages.
-- Configuration Files:
/etc/init.d/nova-consoleauth changed:
PATH=/sbin:/usr/sbin:/bin:/usr/bin
DESC=OpenStack Compute Console Auth
NAME=nova-consoleauth
DAEMON=/usr/bin/nova-consoleauth
DAEMON_ARGS=--config-file=/etc/nova/nova.conf
PIDFILE=/var/run/$NAME.pid
SCRIPTNAME=/etc/init.d/$NAME
NOVA_USER=nova
LOCK_DIR=/var/lock/nova/
DEFAULTS_FILE=/etc/default/nova-common
[ -x $DAEMON ] || exit 0
mkdir -p ${LOCK_DIR}
chown ${NOVA_USER} ${LOCK_DIR}
. /lib/lsb/init-functions
if [ -s $DEFAULTS_FILE ]; then
. $DEFAULTS_FILE
case x$NOVA_ENABLE in
xtrue|xfalse) ;;
*) log_failure_msg Value of NOVA_ENABLE in $DEFAULTS_FILE
must be either 'true' or 'false';
log_failure_msg not starting $NAME daemon.
exit 1
;;
esac
fi
do_start()
{
start-stop-daemon --start --background --quiet --chuid
${NOVA_USER}:nova --make-pidfile --pidfile $PIDFILE --startas $DAEMON --test
/dev/null \
|| return 1
start-stop-daemon --start --background --quiet --chuid
${NOVA_USER}:nova --make-pidfile --pidfile $PIDFILE --startas $DAEMON -- \
$DAEMON_ARGS \
|| return 2
}
do_stop()
{
start-stop-daemon --stop --quiet --retry=TERM/30/KILL/5 --pidfile
$PIDFILE
RETVAL=$?
rm -f $PIDFILE
return $RETVAL
}
case $1 in
start)
if $NOVA_ENABLE; then
log_daemon_msg Starting $DESC $NAME
do_start
case $? in
0|1) log_end_msg 0 ;;
2) log_end_msg 1 ;;
esac
else
log_warning_msg nova daemons not enabled in $DEFAULTS_FILE, not
starting...
fi
;;
stop)
log_daemon_msg Stopping $DESC $NAME
do_stop
case $? in
0|1) log_end_msg 0 ;;
2) log_end_msg 1 ;;
esac
;;
status)
status_of_proc $DAEMON $NAME exit 0 || exit $?
;;
restart|force-reload)
if $NOVA_ENABLE; then
log_daemon_msg Restarting $DESC $NAME
do_stop
case $? in
0|1)
do_start
case $? in
0) log_end_msg 0 ;;
1) log_end_msg 1 ;; # Old process is still running
*) log_end_msg 1 ;; # Failed to start
esac
;;
*)
# Failed to
Bug#704114: asterisk: asterisk security advisories: AST-2013-001 / AST-2013-002 / AST-2013-003
Hi Tzafrir On Fri, Mar 29, 2013 at 06:53:31AM +0100, Salvatore Bonaccorso wrote: Hi Tzafrir On Thu, Mar 28, 2013 at 09:37:30AM +0200, Tzafrir Cohen wrote: On Thu, Mar 28, 2013 at 06:23:32AM +0100, Salvatore Bonaccorso wrote: Package: asterisk Severity: grave Tags: security patch upstream Hi, the following vulnerabilities were published for asterisk. CVE-2013-2685[0]: Buffer Overflow Exploit Through SIP SDP Header CVE-2013-2686[1]: Denial of Service in HTTP server CVE-2013-2264[2]: Username disclosure in SIP channel driver For CVE-2013-2685 the tracker[3] mentions only 1.11.x. Could you doublecheck that squeeze, testing and wheezy are not affected? According to the Upstream advisories, both are in effect for 1.8 . Didn't yet check backporting it (to our 1.8 in Testing/Unstable) and to 1.6.2 in Stable. Thank you for confirming! (note my above comment was related only to one of the issues, CVE-2013-2685). Could you prepare updates to be included via unstable in wheezy? Ping? Did you had a chance to look at it already? Thanks a lot, and Regards, Salvatore -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#704752: uses build_alias instead of DEB_HOST_MULTIARCH for configuration
Package: esorex Version: 3.9.6-1 the esorex uses build_alias for the plugin directory in the default configuration. This is not the same as DEB_HOST_MULTIARCH which is normally used for architecture dependent system installations. E.g. on i386 build_alias is i486-linux-gnu instead of i386-linux-gnu -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#704753: sendip: sendto Invalid argument error
Package: sendip Version: 2.5-5 Severity: important Dear Maintainer, * What led up to the situation? Whilst trying to debug why wakeonlan wasn't working I wanted to send some UDP packets * What exactly did you do (or not do) that was effective (or ineffective)? Running the command: sendip -p ipv4 -is 192.168.0.252 -p udp -us 5070 -ud 5060 -d Hello -v 192.168.0.252 Gives this output Added 26 options Initializing module ipv4 Initializing module udp Finalizing module udp Finalizing module ipv4 Final packet data: 45 00 00 21 E..! 38 AF 00 00 8... FF 11 FF D3 C0 A8 00 FC C0 A8 00 FC 13 CE 13 C4 00 0D 31 27 ..1' 48 65 6C 6C Hell 6F o sendto: Invalid argument Freeing module ipv4 Freeing module udp Same command on a linux laptop on the lan: sendip -p ipv4 -is 192.168.0.132 -p udp -us 5070 -ud 5060 -d Hello -v 192.168.0.132 Added 26 options Initializing module ipv4 Initializing module udp Finalizing module udp Finalizing module ipv4 Final packet data: 45 00 00 21 E..! 22 36 00 00 6.. FF 11 17 3D ...= C0 A8 00 84 C0 A8 00 84 13 CE 13 C4 00 0D 32 17 ..2. 48 65 6C 6C Hell 6F o Sent 33 bytes to 192.168.0.132 Freeing module ipv4 Freeing module udp -- System Information: Debian Release: 7.0 APT prefers testing APT policy: (500, 'testing') Architecture: kfreebsd-amd64 (x86_64) Kernel: kFreeBSD 9.0-2-amd64 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 sendip depends on: ii libc0.1 2.13-38 sendip recommends no packages. sendip 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#704754: release-notes: [wheezy] mention AppArmor support
Package: release-notes Severity: normal Hi, I intend to start working today on a paragraph about Wheezy bringing (optional) AppArmor support. I guess it will fit nicely just after the current 2.2.3. Hardened security. Cheers, -- intrigeri | GnuPG key @ https://gaffer.ptitcanardnoir.org/intrigeri/intrigeri.asc | OTR fingerprint @ https://gaffer.ptitcanardnoir.org/intrigeri/otr.asc -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#702787: pre-approval: unblock: python-pyrrd/0.1.0-2
On 2013-04-05 13:02, Elena ``of Valhalla'' wrote: On 2013-04-05 at 11:55:17 +0100, Steven Chamberlain wrote: I think this was the upload, still on mentors.d.o though: http://mentors.debian.net/package/pyrrd That's the upload, request for sponsorship is at #702864; I didn't ping mentors@d.o after a couple weeks because in the meanwhile the new freeze rules came into being. (and then I forgot to close this bug and wait for jessie to resubmit the fix, sorry) -- Elena ``of Valhalla'' What's CHECK_THIS_BEFORE_UPLOAD.txt? -- Jonathan Wiltshire j...@debian.org Debian Developer http://people.debian.org/~jmw 4096R: 0xD3524C51 / 0A55 B7C5 1223 3942 86EC 74C3 5394 479D D352 4C51 directhex i have six years of solaris sysadmin experience, from 8-10. i am well qualified to say it is made from bonghits layered on top of bonghits -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#703810: [Piuparts-devel] Bug#703810: piuparts : /var/log/fontconfig.log not owned error
On 2013-03-24 00:35, Hideki Yamane wrote: Today I tried to use piuparts with font package and got FAIL with below error. FAIL: After purging files have been modified: /var/log/fontconfig.log c How did you run piuparts to get this error? Andreas -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#683838: release-notes: transition: pdksh → mksh
Julien Cristau dixit: That sounds appropriate for a pdksh NEWS.Debian file, not the release notes? I don’t think so – the change should really be done before the new pdksh package is installed, since it’ll immediately begin affecting users. We can add pdksh to the list of packages that are going away after wheezy, though. That’d be great, thanks! bye, //mirabilos -- FWIW, I'm quite impressed with mksh interactively. I thought it was much *much* more bare bones. But it turns out it beats the living hell out of ksh93 in that respect. I'd even consider it for my daily use if I hadn't wasted half my life on my zsh setup. :-) -- Frank Terbeck in #!/bin/mksh -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#704755: nmu: volview_3.4-3
Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: binnmu nmu volview_3.4-3 . ALL . -m volview does not start because of a missing symbol I'd appreciate if you could binNMU volview on all arch. For some reason something really wrong happen on vtk 5.8.0 since volview was build As a result volview refuses to starts with a message: $ /usr/bin/volview /usr/lib/VolView/VolView: symbol lookup error: /usr/lib/libKWWidgets.so.1.0.1009: undefined symbol: Vtkimagingtcl_Init Simply rebuilding it entirely fixes the symptoms. This will closes: #698698 thanks much -- System Information: Debian Release: 6.0.7 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable'), (200, 'testing'), (100, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 3.2.0-0.bpo.4-amd64 (SMP w/8 CPU cores) Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#674447: Possible debdiff for an upload
Control: tags 674447 + patch
Control: tags 704611 + patch
Attached is a possible debdiff for these two (but not yet tested).
TODO remain:
- is #674447 considered to be RC or should we downgrade ad it needs a
extra tuning of tune.bufsize
- In case of an upload, will the Release Team also accept a patch for
#704611, else it should be removed again.
Regards,
Salvatore
diff -Nru haproxy-1.4.15/debian/changelog haproxy-1.4.15/debian/changelog
--- haproxy-1.4.15/debian/changelog 2011-07-14 18:19:25.0 +0200
+++ haproxy-1.4.15/debian/changelog 2013-04-05 15:45:35.0 +0200
@@ -1,3 +1,14 @@
+haproxy (1.4.15-1.1) unstable; urgency=low
+
+ * Non-maintainer upload.
+ * Add CVE-2012-2942 patch.
+CVE-2012-2942: Fix buffer overflow in the trash buffer in the header
+capture functionality. (Closes: #674447)
+ * Add CVE-2013-1912 patch.
+CVE-2013-1912: Fix crash on TCP content inspection rules. (Closes: #704611)
+
+ -- Salvatore Bonaccorso car...@debian.org Fri, 05 Apr 2013 15:45:20 +0200
+
haproxy (1.4.15-1) unstable; urgency=low
* New upstream release with critical bug fix (Closes: #631351)
diff -Nru haproxy-1.4.15/debian/patches/CVE-2012-2942
haproxy-1.4.15/debian/patches/CVE-2012-2942
--- haproxy-1.4.15/debian/patches/CVE-2012-2942 1970-01-01 01:00:00.0
+0100
+++ haproxy-1.4.15/debian/patches/CVE-2012-2942 2013-04-05 15:45:35.0
+0200
@@ -0,0 +1,350 @@
+From: David du Colombier dducolomb...@exceliance.fr
+Date: Wed, 16 May 2012 12:16:48 + (+0200)
+Subject: BUG/MAJOR: trash must always be the size of a buffer
+X-Git-Tag: v1.4.21~7
+X-Git-Url:
http://haproxy.1wt.eu:81/git?p=haproxy-1.4.git;a=commitdiff_plain;h=30297cb17147a8d339eb160226bcc08c91d9530b
+
+BUG/MAJOR: trash must always be the size of a buffer
+
+Before it was possible to resize the buffers using global.tune.bufsize,
+the trash has always been the size of a buffer by design. Unfortunately,
+the recent buffer sizing at runtime forgot to adjust the trash, resulting
+in it being too short for content rewriting if buffers were enlarged from
+the default value.
+
+The bug was encountered in 1.4 so the fix must be backported there.
+(cherry picked from commit 7af4605ef76f6929835eefd13664beab379101b5)
+---
+
+--- a/include/types/global.h
b/include/types/global.h
+@@ -104,7 +104,8 @@
+ extern int relative_pid; /* process id starting at 1 */
+ extern int actconn;/* # of active sessions */
+ extern int listeners;
+-extern char trash[BUFSIZE];
++extern char *trash;
++extern int trashlen;
+ extern char *swap_buffer;
+ extern int nb_oldpids; /* contains the number of old pids found */
+ extern const int zero;
+--- a/src/acl.c
b/src/acl.c
+@@ -776,8 +776,7 @@
+ opaque = 0;
+ pattern = NULL;
+ args[1] = ;
+- while (fgets(trash, sizeof(trash), file) != NULL) {
+-
++ while (fgets(trash, trashlen, file) != NULL) {
+ c = trash;
+
+ /* ignore lines beginning with a dash */
+--- a/src/cfgparse.c
b/src/cfgparse.c
+@@ -511,6 +511,8 @@
+ global.tune.bufsize = atol(args[1]);
+ if (global.tune.maxrewrite = global.tune.bufsize / 2)
+ global.tune.maxrewrite = global.tune.bufsize / 2;
++ trashlen = global.tune.bufsize;
++ trash = realloc(trash, trashlen);
+ }
+ else if (!strcmp(args[0], tune.maxrewrite)) {
+ if (*(args[1]) == 0) {
+@@ -904,9 +906,9 @@
+ continue;
+ if (strcmp(kwl-kw[index].kw, args[0]) == 0) {
+ /* prepare error message just in case */
+- snprintf(trash, sizeof(trash),
++ snprintf(trash, trashlen,
+error near '%s' in '%s'
section, args[0], global);
+- rc = kwl-kw[index].parse(args,
CFG_GLOBAL, NULL, NULL, trash, sizeof(trash));
++ rc = kwl-kw[index].parse(args,
CFG_GLOBAL, NULL, NULL, trash, trashlen);
+ if (rc 0) {
+ Alert(parsing [%s:%d] : %s\n,
file, linenum, trash);
+ err_code |= ERR_ALERT |
ERR_FATAL;
+@@ -3302,7 +3304,7 @@
+ err_code |= ERR_WARN;
+
+ memcpy(trash, error near 'balance', 21);
+- if (backend_parse_balance((const char **)args + 1, trash,
sizeof(trash), curproxy) 0) {
++ if (backend_parse_balance((const char **)args + 1, trash,
trashlen, curproxy) 0) {
+ Alert(parsing [%s:%d] : %s\n, file, linenum, trash);
+ err_code |= ERR_ALERT | ERR_FATAL;
+ goto out;
+@@ -4529,9 +4531,9 @@
+
Bug#704705: [Pkg-ime-devel] Bug#704705: ibus: cannot use with both Mozilla i386 apps and emacs
Hi, On Fri, Apr 05, 2013 at 09:03:09AM +0800, Aron Xu wrote: Hi Toni, If I understand correctly, you have installed amd64 version of ibus-gtk/gtk3/qt4, this is not sufficient for i386 applications as IM Modules are run-time plugin for respective UI toolkit. Can you try to install ibus-gtk:i386, ibus-gtk3:i386, and ibus-qt4:i386, to see whether your problem get resolved? Multiarch is well defined and implimented for libraries but for these executables used by other software, the best practice was not clear to me and may had some wrong handling. Package: ibus Architecture: any Multi-Arch: foreign ... Recommends: ibus-gtk3, ibus-gtk, ibus-qt4, ibus-clutter, im-config | im-switch ... Package: ibus-gtk Architecture: any Multi-Arch: same ... Package: ibus-gtk3 Architecture: any Multi-Arch: same ibus being Multi-Arch: foreign it can serve both i386 and amd64 applications by either one of ibus:i386 and ibus:amd64 but ibus:i386 and ibus:amd64 are not co-installable. ibus-gtk:i386 only serve i386 program because it is Multi-Arch: same. ibus-gtk:amd64 only serve amd64 program because it is Multi-Arch: same. Hmmm... so this is expected problem of current packaging which we have no easy solution. This should be true for current testing version too. Question is how to solve this. Making ibus-gtk and ibus-gtk3 and ... to Multi-Arch: foreign solves this? i do not know the answer. Aron what do you think? -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#704285: release-notes: Debian doesn't support LSB 3.2
Hi all, Le vendredi, 5 avril 2013 15.02:39, Julien Cristau a écrit : cc:ing the lsb maintainer Thanks for the explicit CC. On Sun, Mar 31, 2013 at 01:22:59 -0700, Jonathan Nieder wrote: If I understand the lsb packaging correctly, Debian aims at support for LSB 4.1 these days instead of LSB 3.2. That's correct. The packages created by src:lsb try to achieve that support. Note that Debian is not (has not and I doubt it will eventually be) LSB- certified. More importantly, the Linux Standard Base Desktop Specification (both version 3.2 or 4.1) says: The libraries listed in Table 3-1 shall be available on a Linux Standard Base - Desktop system, with the specified runtime names. [...] libqt-mtlibqt-mt.so.3 but wheezy does not include that library. That's correct. This has been documented in lsb-desktop NEWS entry for the 4.1+Debian7 version (attached): From its 4.1+Debian7 version on, lsb-desktop doesn't depend on Qt3 anymore. This is an explicit and Debian-specific derogation from the LSB 4.1 specification. Then the README.Debian points to snapshot.debian.org. Index: whats-new.dbk === --- whats-new.dbk (révision 9650) +++ whats-new.dbk (copie de travail) @@ -362,7 +362,10 @@ /programlisting para -Debian still supports Linux Standard Base (acronymLSB/acronym) version 3.2. +Debian supports Linux Standard Base (acronymLSB/acronym) version 4.1. +It also supports most Linux Standard Base Desktop 4.1 interfaces, with +the exception that instead of including both Qt 3 and Qt 4, it only +includes Qt 4. indextermprimaryLinux Standard Base/primary/indexterm /para I would phrase it as the carefully-thought NEWS entry above: Debian supports Linux Standard Base (acronymLSB/acronym) version 4.1, with one explicit and Debian-specific derogation from the acronymLSB/acronym 4.1 specification: Qt3 is not included; see the lsb-desktop README file. What do you think ? Didier, care to ack/nak? ACK-but. :-) Cheers, OdyX NEWS.Debian.gz Description: GNU Zip compressed data signature.asc Description: This is a digitally signed message part.
Bug#704756: nmu: pidgin-latex_1.5.0-1
Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: binnmu nmu pidgin-latex_1.5.0-1 . amd64 . -m Rebuild in a clean sid environment. Once again a package built in experimental or Ubuntu was uploaded to Debian: pidgin-latex/amd64 unsatisfiable Depends: libc6 (= 2.14) Andreas -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#680484: closed by Andreas Tille ti...@debian.org (Bug#680484: fixed in scotch 5.1.12b.dfsg-2)
On 2013-04-04 20:40, Andreas Tille wrote: Hi, On Thu, Apr 04, 2013 at 07:43:11PM +0200, Julien Cristau wrote: On Thu, Apr 4, 2013 at 08:33:00 +0200, Andreas Tille wrote: I have no idea how hard the handling of testing-proposed-uploads might be for the release team. So I could imagine an alternative plan to unblock 5.1.12b.dfsg-2 which has admittedly more changes than acceptable in freeze time (sorry, I did not realised this problem in July last year - that's my fault) but all in all enabling hardening should not cause real trouble. In case release team might consider the later plan I'd volunteer to create the necessary diffs for an unblock request - just tell me what plan you prefer and I will do this. No, we won't add hardening at this stage. OK, so if I do not hear anything from Christophe if he wants to prepare the tpu upload I will do so at latest next Monday (hopefully earlier). Thanks for your work on Wheezy release Andreas. Thanks - it would help to ping this bug when it uploaded too please. I'm sure you realised but s/uploads/updates/ in your quoted mail above (or just testing). -- Jonathan Wiltshire j...@debian.org Debian Developer http://people.debian.org/~jmw 4096R: 0xD3524C51 / 0A55 B7C5 1223 3942 86EC 74C3 5394 479D D352 4C51 directhex i have six years of solaris sysadmin experience, from 8-10. i am well qualified to say it is made from bonghits layered on top of bonghits -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#704668: RFS: woff-tools/0:2009.10.04-1 [ITP]
* Dmitry Shachnev mity...@gmail.com, 2013-04-04, 14:36: http://mentors.debian.net/debian/pool/main/w/woff-tools/woff-tools_2009.10.04-1.dsc FTBFS: woff.c:43:18: fatal error: zlib.h: No such file or directory -- 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#704757: novnc 04.+dfsg+1-6 conflicts with websockify 0.3.0-1
Package: novnc Version: 0.4+dfsg+1-6 Severity: important Dear Maintainer, novnc 04.+dfsg+1-6 conflicts with websockify 0.3.0-1 # apt-get install novnc Reading package lists... Done Building dependency tree Reading state information... Done The following NEW packages will be installed: novnc 0 upgraded, 1 newly installed, 0 to remove and 13 not upgraded. Need to get 0 B/155 kB of archives. After this operation, 446 kB of additional disk space will be used. (Reading database ... 282765 files and directories currently installed.) Unpacking novnc (from .../novnc_1%3a0.4+dfsg+1-6_amd64.deb) ... dpkg: error processing /var/cache/apt/archives/novnc_1%3a0.4+dfsg+1-6_amd64.deb (--unpack): trying to overwrite '/usr/bin/rebind', which is also in package websockify 0.3.0-1 dpkg-deb: error: subprocess paste was killed by signal (Broken pipe) Errors were encountered while processing: /var/cache/apt/archives/novnc_1%3a0.4+dfsg+1-6_amd64.deb E: Sub-process /usr/bin/dpkg returned an error code (1) # ls -l /usr/bin/rebind -rwxr-xr-x 1 root root 424 Jan 15 12:49 /usr/bin/rebind # dpkg -l|egrep 'websockify|python-nova' ii python-nova 2013.1-1 all OpenStack Compute - libraries ii python-novaclient 2:2.12.0-1 all client library for OpenStack Compute API ii websockify0.3.0-1 amd64WebSockets support for any application/server websockify is a dependency for python-nova. Packages retrieved from the gplhost.com grizzly repo. Trying to install OpenStack Grizzly with .deb packages on Debian 3.8 experimental, following the DevStack model. More information on http://debian.netside.net/xps13_openstack.html Cheers, Mitch Halmu -- System Information: Debian Release: 7.0 APT prefers testing-proposed-updates APT policy: (500, 'testing-proposed-updates'), (500, 'unstable'), (500, 'testing'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.8-trunk-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 novnc depends on: ii adduser 3.113+nmu3 ii dpkg 1.16.10 ii libc6 2.13-38 ii python2.7.3-4 ii python-nova 2013.1-1 ii python-novnc 1:0.4+dfsg+1-6 ii python-numpy 1:1.6.2-1.2 ii websockify0.3.0-1 novnc recommends no packages. novnc suggests no packages. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#699841: nslcd: Please add a way to debug nslcd from /etc/default/nslcd
On Tue, 2013-02-05, Lisandro Damián Nicanor Pérez Meyer wrote: It would be really awesome if -d could be passed from /etc/default/nslcd to be able to debug it. Maybe nslcd does not goes to background in this case, if so, maybe it could do that and log to syslog or somewhere else. The new upstream release 0.9.0 now contains a log configuration option that can be used to log messages at debug level to either syslog or a simple file (without passing the -d switch). This should cover most debugging scenario's I think. A release of a Debian package of the 0.9 series will probably have to wait until after wheezy is released because experimental is currently used for the 0.8 series and I prefer to avoid uploading newer versions to unstable. Thanks, -- -- arthur - adej...@debian.org - http://people.debian.org/~adejong -- signature.asc Description: This is a digitally signed message part
Bug#704758: cinnamon2d doesn't work in a VNC session
Package: cinnamon Version: 1.6.7-2 Severity: normal I was hoping that cinnamon2d would be usable on a VNC session but it doesn't. It just fails with: (cinnamon:26370): Clutter-CRITICAL **: Unable to initialize Clutter: Failed to connected to any renderer: XServer appears to lack required GLX support Erreur du gestionnaire de fenêtres : Unable to initialize Clutter. The session is left in an entirely unusable state. -- System Information: Debian Release: 7.0 APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.7-trunk-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/dash -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#659488: nss-pam-ldapd: problem with mixed endian multiarch
On Sat, 2012-02-11 at 15:20 +0100, Arthur de Jong wrote: The communication protocol that is in use between the NSS and PAM modules on one end and nslcd on the other end uses host byte order to transfer integer values. This will cause issues when the NSS or PAM module uses a different endianness than nslcd. Upstream release 0.9.0 has switched to using network byte order always. This is a backwards incompatible change. While previously it wasn't a problem for an older NSS module to communicate with a newer nslcd with a switch to 0.9 this is no longer the case. We should probably figure out how to handle the upgrade (I recall libc doing something similar). It may be a while until a 0.9 version is uploaded to Debian because the branch is in development and experimental is currently used for keeping the 0.8 up-to-date. -- -- arthur - adej...@debian.org - http://people.debian.org/~adejong -- signature.asc Description: This is a digitally signed message part
Bug#647502: libnss-ldapd: It would be nice to have nested group support.
On Thu, 2011-11-03 at 21:47 +0100, Arthur de Jong wrote: On Thu, 2011-11-03 at 11:35 +0100, Martijn van Brummelen wrote: Is it possible to add nested group support? Indeed, it would be nice if support for this would be available (it is one of the features that is present in nss_ldap but missing in nss-pam-ldapd). Nested group functionality has just been made available in nss-pam-ldapd 0.9.0. You may want to have a look. Test reports are welcome. It may be a while until a 0.9 version is uploaded to Debian because the branch is in development and experimental is currently used for keeping the 0.8 up-to-date. Thanks, -- -- arthur - adej...@debian.org - http://people.debian.org/~adejong -- signature.asc Description: This is a digitally signed message part
Bug#683838: release-notes: transition: pdksh → mksh
On Fri, Apr 5, 2013 at 13:43:15 +, Thorsten Glaser wrote: Julien Cristau dixit: That sounds appropriate for a pdksh NEWS.Debian file, not the release notes? I don’t think so – the change should really be done before the new pdksh package is installed, since it’ll immediately begin affecting users. If mksh is not a drop-in replacement then I'm not sure it's a good idea to have it provide a transitional package. Might as well leave the old pdksh alone so there's no functionality loss... Cheers, Julien signature.asc Description: Digital signature
Bug#586135: Updated MisterHouse URL information
Development for the Debian packaging can be found here: https://github.com/jame/misterhouse/ The following are current useful starting points for MisterHouse itself: http://misterhouse.sourceforge.net http://misterhouse.wikispaces.com/ The SVN repository at the SourceForge project is not currently being actively used: instead, the following repository at GitHub (which also contains an import from the SVN repository) is the primary one: https://github.com/hollie/misterhouse/ -- Robert J. Clay rjc...@gmail.com j...@rocasa.us -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#704211: [release-notes] [wheezy] issues: NM conflicts with wicd-daemon, Gnome3 now depends on NM
Hi Chris, I'd put it near http://www.debian.org/releases/testing/amd64/release-notes/ch-whats-new.en.html#idp298704 2.2.5. GNOME 3, so that's svn.debian.org/svn/ddp/manuals/trunk/release-notes/en/whats-new.dbk Thanks, Bye, Joost PS: as you probably know: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=688772#532 has some text on why using n-m with gnome is a good idea and, background: in http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=688772#665 Technical Commitee stated: 6. We request that a release note is created explaining that gnome users who do not currently have NM installed consider installing it. . HTH! signature.asc Description: Digital signature
Bug#704759: Enable lmetad when building lvm2
Package: lvm2 Version: 2.02.98-1 Severity: wishlist Hi, I have a setup with hot-plug drives with LVM on them and would like to have them automatically activated when plugged in. The way to achieve this, at least according to what I found on the web, is to make lvm aware of hotplug events, and the way to do that is to let it use information from lvmetad using 'use_lvmetad=1' in /etc/lvm/lvm.conf. This option is described even in the package for wheezy, but I didn't find 'lvmetad' in the lvm2 package. Looking at the source package in unstable I didn't find the corresponding '--enable-lvmetad' option to configure, and I found this in the Debian build log: checking whether to build LVMetaD... no I can understand why lvmetad might not be enabled by default. Is there a reason not to build it? (This is not rhetoric; I really like to know whether there is a reason not to build it.) Even if it is now too late to get anything like this into wheezy: it would be nice to have a patch which enables lvmetad so that someone can either build their own package easily or maybe even get it later from backports, should it enter there. thanks, Frank Loeffler -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#704760: ITP: python-pecan -- WSGI object-dispatching web framework
Package: wnpp Severity: wishlist Owner: Thomas Goirand z...@debian.org * Package name: python-pecan Version : 0.2.1 Upstream Author : Jonathan LaCour jonat...@dreamhost.com * URL : https://github.com/dreamhost/pecan * License : BSD Programming Lang: Python Description : WSGI object-dispatching web framework The Pecan Python module is a WSGI object-dispatching web framework designed to be lean and fast with few dependencies. Pecan comes bundled with a lightweight WSGI development server based on Python's wsgiref.simpleserver. Pecan applications also come with an interactive Python shell which can be used to execute expressions in an environment very similar to the one your application runs in (using the pecan shell command). -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#704761: Files not deleted, smbstatus shows Segmentation fault
Package: samba Version: 3.6.6-5 Tags: patch Severity: important Dear maintainers, I recently upgraded samba to version 3.6.6 (from backports) in preparation of upgrade to Debian Wheezy. After upgrading I stumbled upon this issue: https://bugzilla.samba.org/show_bug.cgi?id=9058 (Files not deleted, smbstatus shows Segmentation fault) which can be fixed by applying those two patches (from within that upstream bug report): https://bugzilla.samba.org/attachment.cgi?id=7809 and https://bugzilla.samba.org/attachment.cgi?id=7817 Those two patches were added to 3.6.8. It would be great if it is possible to get those patches into samba before the release of Wheezy because that bug renders samba unusable for me (and most probably others). Thanks! -- Adi signature.asc Description: Digital signature
Bug#486682: lintian: warn if wildcards in .install could let a SONAME bump go unnoticed?
Hi! On Sun, 2011-09-04 at 08:27:17 +0200, Niels Thykier wrote: tags 486682 + wontfix thanks I think this may have been useful in the past, but debhelper compat 5+ largely makes it redundant[1]. Since compat level 4 and lower are all deprecated this problem is (in theory) non-existing. [1] man 7 debhelper: v5 Changes from v4 are: [...] - dh_install errors out if wildcards expand to nothing. I don't think this covers what Adeodato was requesting, i.e. to warn on wildcards that are too loose to let this situation happen in the first place: libfoo.so.1 libfoo.so.1.0.0 libfoo1.install: usr/lib/libfoo.so.* On SONAME bump the wildcard matches the new library too: libfoo.so.2 libfoo.so.2.0.0 libfoo1.install: usr/lib/libfoo.so.* What I understood was being proposed was to warn on these kind of wildcards and suggest for example something like: libfoo1.install: usr/lib/libfoo.so.1 usr/lib/libfoo.so.1.* or: libfoo1.install: usr/lib/libfoo-1.*.so depending on the style of SONAME versioning currently supported: /^(.*)\.so\.(.*)$/ /^(.*)-(\d.*)\.so$/ Which then would produce an error with newer debhelper compat levels. Thanks, Guillem -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#704762: ITP: libnet-ipaddress-perl -- Functions used to manipulate IP addresses, masks and FQDN's
Package: wnpp Severity: wishlist * Package name: libnet-ipaddress-perl Version : 1.10-1 Upstream Author : Scott Renner sren...@mandtbank.com * URL or Web page : http://search.cpan.org/~sarenner/Net-IPAddress/ * License : GPL1 ou later Description : Functions used to manipulate IP addresses, masks and FQDN's Net::IPAddr is a collection of helpful functions used to convert IP addresses to/from 32-bit integers, applying subnet masks to IP addresses, validating IP address strings, and splitting a FQDN into its host and domain parts. -- ,''`. : :' : Cyril Bouthors `. `' Debian.org `- Debian-Packaging.com -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#704754: release-notes: [wheezy] mention AppArmor support
Control: tag -1 + patch Hi, intrig...@debian.org wrote (05 Apr 2013 13:35:49 GMT) : I intend to start working today on a paragraph about Wheezy bringing (optional) AppArmor support. Please review the attached patch. About pointing to wiki.d.o: I'm aware this is frown upon by the www team for good reasons, but I feel this case is special (they all say it, right?). Given the AppArmor support is quite minimal (not enabled by default, very few profiles shipped by packages) in Wheezy, I won't spend time writing detailed documentation for it *now*. So, I've just reorganized the AppArmor -related wiki pages to be an acceptable temporary landing place for end-users. If AppArmor is better supported in Jessie (which I intend to work on), then we should have dedicated documentation in a place and format that's nicer for translators. About sections: I wonder whether it would be better to have an Improved security section, with Hardened programs (current hardening section) and AppArmor as sub-section thereof. Thoughts? Cheers, -- intrigeri | GnuPG key @ https://gaffer.ptitcanardnoir.org/intrigeri/intrigeri.asc | OTR fingerprint @ https://gaffer.ptitcanardnoir.org/intrigeri/otr.asc From 029d77129ea0c692c2d4a939254cb2d9f86c4e97 Mon Sep 17 00:00:00 2001 From: intrigeri intrig...@debian.org Date: Fri, 5 Apr 2013 17:31:29 +0200 Subject: [PATCH] Add AppArmor section to the Release Notes. --- release-notes/en/whats-new.dbk | 17 + 1 file changed, 17 insertions(+) diff --git a/release-notes/en/whats-new.dbk b/release-notes/en/whats-new.dbk index d429d91..3ce553e 100644 --- a/release-notes/en/whats-new.dbk +++ b/release-notes/en/whats-new.dbk @@ -492,6 +492,23 @@ For more information on this feature refer to the information available in /para /section +section id=apparmor + titleAppArmor/title + para +Debian 7.0 supports the AppArmor Mandatory Access Control system. +When enabled, AppArmor confines programs according to a set of rules that +specify what files a given program can access. This proactive approach helps +protecting the system against both known and unknown vulnerabilities. + /para + + para +AppArmor is disabled by default in Debian 7.0. The debian; wiki has ulink +url=http://wiki.debian.org/AppArmor;instructions/ulink on how to use +this functionality. + /para + +/section + section id=stable-updates titleThe stable-updates section/title para -- 1.7.10.4
