Bug#690525: more information
Following the disconnect, the minion tries over and over and over again to establish a new connection, which gets shut down by the remote: 2.216183 10.178.17.2 - 77.109.139.93 TCP 76 42836 4505 [SYN] Seq=0 Win=14600 Len=0 MSS=1460 SACK_PERM=1 TSval=294780260 TSecr=0 WS=16 2.244185 77.109.139.93 - 10.178.17.2 TCP 76 4505 42836 [SYN, ACK] Seq=0 Ack=1 Win=14480 Len=0 MSS=1452 SACK_PERM=1 TSval=250894922 TSecr=294780260 WS=16 2.244185 10.178.17.2 - 77.109.139.93 TCP 68 42836 4505 [ACK] Seq=1 Ack=1 Win=14608 Len=0 TSval=294780267 TSecr=250894922 2.244185 10.178.17.2 - 77.109.139.93 TCP 93 42836 4505 [PSH, ACK] Seq=1 Ack=1 Win=14608 Len=25 TSval=294780267 TSecr=250894922 2.272187 77.109.139.93 - 10.178.17.2 TCP 68 4505 42836 [ACK] Seq=1 Ack=26 Win=14480 Len=0 TSval=250894929 TSecr=294780267 2.272187 77.109.139.93 - 10.178.17.2 TCP 68 4505 42836 [FIN, ACK] Seq=1 Ack=26 Win=14480 Len=0 TSval=250894929 TSecr=294780267 2.272187 10.178.17.2 - 77.109.139.93 TCP 68 42836 4505 [FIN, ACK] Seq=26 Ack=2 Win=14608 Len=0 TSval=294780274 TSecr=250894929 2.300190 77.109.139.93 - 10.178.17.2 TCP 68 4505 42836 [ACK] Seq=2 Ack=27 Win=14480 Len=0 TSval=250894936 TSecr=294780274 [and the next port:] 2.404198 10.178.17.2 - 77.109.139.93 TCP 76 42837 4505 [SYN] Seq=0 Win=14600 Len=0 MSS=1460 SACK_PERM=1 TSval=294780307 TSecr=0 WS=16 […] On the master side, this corresponds to several hundred of lingering connections, according to netstat: tcp0 0 77.109.139.93:4505 82.135.64.143:42250 TIME_WAIT - # netstat -natp | grep -c :4505.*TIME_WAIT 484 I am running both minion and master with --log-level=trace, but there is nothing in the output about this. -- .''`. martin f. krafft madduck@d.o Related projects: : :' : proud Debian developer http://debiansystem.info `. `'` http://people.debian.org/~madduckhttp://vcs-pkg.org `- Debian - when you have better things to do than fixing systems digital_signature_gpg.asc Description: Digital signature (see http://martin-krafft.net/gpg/sig-policy/999bbcc4/current)
Bug#691478: ettercap: uninstallable due to dependency problems
Package: ettercap Version: 1:0.7.5-1 Severity: important ettercap-graphical and ettercap-text-only provide ettercap and depend on ettercap-common but ettercap-common conflicts with ettercap -- System Information: Debian Release: 6.0.6 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable'), (101, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 2.6.32-028stab098.1 (SMP w/1 CPU core) Locale: LANG=de_DE.utf8, LC_CTYPE=de_DE.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#688297: Wheezy beta 3 working on old Packard Bell
Just wanted to inform that with beta 3 release of wheezy, the previous reported beta 2 non-bootable installer problem does not exists anymore. Now the old Packard Bell machine is up and running as expected.
Bug#691479: ITP: pcalendar -- application to track women menstrual cycles
Package: wnpp Severity: wishlist X-Debbugs-CC: debian-de...@lists.debian.org Package name: pcalendar Version: 3.3.0 Upstream Author: Mar'yan Rachynskyy mr...@users.sourceforge.net URL: http://linuxorg.sourceforge.net/ License: GPL-3+ Description: application to track women menstrual cycles Periodic Calendar is a GUI application which assists in women menstrual cycles tracking and fertility periods prediction. This information can be used as. supportive either for conception or contraception planning. . Periodic Calendar provides support for sympto-thermal method which has the highest reliability in fertility periods prediction. User can choose any subset of the. features to be used or even fall to the generic calendar method (which if used. alone is very unreliable)... . Periodic Calendar is not an equal substitute to the fertility planning consultants or doctors. Before using this application please talk to your doctor or read a good book on the subject. . THIS PROGRAM PREDICTIONS IN NO WAY CAN BE USED AS THE FINAL. THERE ARE NO PREDICTION METHODS WHICH PROVIDE 100% RELIABILITY. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#668008: transition/unblock: uw-imap
user release.debian@packages.debian.org usertags - transition thanks I've uploaded uw-imap 8:2007f~dfsg-2 implementing Julien's suggestion. Please unblock it. uw-imap (8:2007f~dfsg-2) unstable; urgency=medium * New maintainer (Closes: #686448). * Disable unnecessarily strict version check (Closes: #682256). -- Magnus Holmgren holmg...@debian.org Thu, 25 Oct 2012 23:00:39 +0200 -- Magnus Holmgrenholmg...@debian.org Debian Developer signature.asc Description: This is a digitally signed message part.
Bug#691480: Tiling: floating windows shown on all desktops cannot be moved when tiling enabled
Package: kde-window-manager Version: 4:4.8.4-3 Severity: minor Dear Maintainer, in a xinerama configuration and enabled window tiling (columns as well as spiral) floating windows that are shown on all desktops cannot be moved. (xinerama may not have any impact here, though) I'd expect them to be movable. -- System Information: Debian Release: wheezy/sid APT prefers testing APT policy: (990, 'testing'), (700, 'unstable'), (500, 'testing-proposed-updates'), (500, 'stable-updates'), (500, 'proposed-updates'), (500, 'stable'), (100, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 3.5.0 (SMP w/2 CPU cores) Locale: LANG=en_GB.utf8, LC_CTYPE=en_GB.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages kde-window-manager depends on: ii kde-runtime 4:4.8.4-1 ii kde-style-oxygen 4:4.8.4-3 ii libc6 2.13-35 ii libgl1-mesa-glx [libgl1] 8.0.4-2 ii libice6 2:1.0.8-2 ii libkactivities6 4:4.8.4-1 ii libkcmutils4 4:4.8.4-3 ii libkdeclarative5 4:4.8.4-3 ii libkdecorations4 4:4.8.4-3 ii libkdecore5 4:4.8.4-3 ii libkdeui5 4:4.8.4-3 ii libkephal4abi14:4.8.4-3 ii libkio5 4:4.8.4-3 ii libknewstuff3-4 4:4.8.4-3 ii libkwineffects1abi3 4:4.8.4-3 ii libkwinglutils1 4:4.8.4-3 ii libkworkspace4abi14:4.8.4-3 ii libplasma34:4.8.4-3 ii libqt4-dbus 4:4.8.2+dfsg-2 ii libqt4-declarative4:4.8.2+dfsg-2 ii libqt4-script 4:4.8.2+dfsg-2 ii libqt4-xml4:4.8.2+dfsg-2 ii libqtcore44:4.8.2+dfsg-2 ii libqtgui4 4:4.8.2+dfsg-2 ii libsm62:1.2.1-2 ii libstdc++64.7.1-7 ii libx11-6 2:1.5.0-1 ii libxcomposite11:0.4.3-2 ii libxcursor1 1:1.1.13-1 ii libxdamage1 1:1.1.3-2 ii libxext6 2:1.3.1-2 ii libxfixes31:5.0-4 ii libxrandr22:1.3.2-2 ii libxrender1 1:0.9.7-1 ii perl 5.14.2-14 kde-window-manager recommends no packages. kde-window-manager 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#691481: zile: Dangling symlink and missing example
Package: zile Version: 2.3.21-1 Severity: minor [58+0]~# dpkg -S /usr/share/doc/zile/examples/dotzile.sample zile: /usr/share/doc/zile/examples/dotzile.sample [59+0]~# file /usr/share/doc/zile/examples/dotzile.sample /usr/share/doc/zile/examples/dotzile.sample: broken symbolic link to `../../../zile/dotzile.sample' -- System Information: Debian Release: wheezy/sid APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 3.4.15-custom (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 zile depends on: ii libc62.13-35 ii libncurses5 5.9-10 zile recommends no packages. zile 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#640851: local mail spool still unaccessible with evo 3.4.4.-1
On Thu, 2012-10-25 at 11:34 +0200, Svante Signell wrote: severity 640851 serious found 640851 3.4.3-1 found 640851 3.4.4-1 thanks I was waiting for the latest bugfix release to see if the local mailbox spool problem was solved. Unfortunately it was not :( Local mails are delivered to /var/mail/username and these are the settings used for the local mail account in evo. However, evo looks for this mailbox file at ~/.local/share/evolution/mail/some_strange_directory_name containing the following files: INBOX.ibex.index.data, INBOX.ibex.index, INBOX.cmeta, folders.db Removing these files and restarting evo does not help: evo complains about: Summary and folder mismatch, even after a sync In the settings the local account is flagged as of type spool and for Receiving Email the setting is: Standard Unix mbox spool file. More information: Evolution tries to store the mailbox entry at /username/INBOX which doesn't exist, when the mbox file is at /var/mail/username . That filename is given in the evo settings for that mail account, but is not honored?? (evolution:8019): evolution-mail-WARNING **: Failed to refresh folders: Error storing 'mailbox: /username/INBOX (spool)': Summary and folder mismatch, even after a sync -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#653813:
Any news about the inclusion of The Legend Of Edgar in official Debian repositories?
Bug#691483: kde-window-manager: Tiling and xinerama: opening a new window lets all tiled windows jump to the monitor where the mouse pointer resides
Package: kde-window-manager Version: 4:4.8.4-3 Severity: normal Dear Maintainer, in xinerama mode with two side-by-side monitors and tiling enabled: having tiled windows on the left monitor (e.g.) and opening a new window on the right monitor lets all windows jump to the right monitor. The ordering of the windows remains the same, the sizes are adjusted to the smaller monitor resolution. To move them all back, a new window needs to be opened on the left monitor, which usually can be closed immediately (only once (but several times in a row) all the windows jumped back to the previous monitor when I closed this temporary window again) Nice game, though ;) I'd expect the windows to stay where they are. For the new window two options may exist and may need an additional configuration option: a) have an independent tiling on each monitor or b) let it float (which might be a case of a) BR -- System Information: Debian Release: wheezy/sid APT prefers testing APT policy: (990, 'testing'), (700, 'unstable'), (500, 'testing-proposed-updates'), (500, 'stable-updates'), (500, 'proposed-updates'), (500, 'stable'), (100, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 3.5.0 (SMP w/2 CPU cores) Locale: LANG=en_GB.utf8, LC_CTYPE=en_GB.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages kde-window-manager depends on: ii kde-runtime 4:4.8.4-1 ii kde-style-oxygen 4:4.8.4-3 ii libc6 2.13-35 ii libgl1-mesa-glx [libgl1] 8.0.4-2 ii libice6 2:1.0.8-2 ii libkactivities6 4:4.8.4-1 ii libkcmutils4 4:4.8.4-3 ii libkdeclarative5 4:4.8.4-3 ii libkdecorations4 4:4.8.4-3 ii libkdecore5 4:4.8.4-3 ii libkdeui5 4:4.8.4-3 ii libkephal4abi14:4.8.4-3 ii libkio5 4:4.8.4-3 ii libknewstuff3-4 4:4.8.4-3 ii libkwineffects1abi3 4:4.8.4-3 ii libkwinglutils1 4:4.8.4-3 ii libkworkspace4abi14:4.8.4-3 ii libplasma34:4.8.4-3 ii libqt4-dbus 4:4.8.2+dfsg-2 ii libqt4-declarative4:4.8.2+dfsg-2 ii libqt4-script 4:4.8.2+dfsg-2 ii libqt4-xml4:4.8.2+dfsg-2 ii libqtcore44:4.8.2+dfsg-2 ii libqtgui4 4:4.8.2+dfsg-2 ii libsm62:1.2.1-2 ii libstdc++64.7.1-7 ii libx11-6 2:1.5.0-1 ii libxcomposite11:0.4.3-2 ii libxcursor1 1:1.1.13-1 ii libxdamage1 1:1.1.3-2 ii libxext6 2:1.3.1-2 ii libxfixes31:5.0-4 ii libxrandr22:1.3.2-2 ii libxrender1 1:0.9.7-1 ii perl 5.14.2-14 kde-window-manager recommends no packages. kde-window-manager 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#600092: Breaks if initscript and initscript.sh both exist
Hi, Am Freitag, den 26.10.2012, 07:31 +0200 schrieb Michael Biebl: I've just checked the Debian archive, and we no longer have any package which ships both a /etc/init.d/foo and /etc/init.d/foo.sh sysv init script. So I'm wondering if it's worth keeping the bug open? probably not; it’s up to you. Greetings, Joachim -- Joachim nomeata Breitner Debian Developer nome...@debian.org | ICQ# 74513189 | GPG-Keyid: 4743206C JID: nome...@joachim-breitner.de | http://people.debian.org/~nomeata signature.asc Description: This is a digitally signed message part
Bug#691479: ITP: pcalendar -- application to track women menstrual cycles
Hi there! On Fri, 26 Oct 2012 08:35:21 +0200, Dmitry Smirnov wrote: Package name: pcalendar Version: 3.3.0 Upstream Author: Mar'yan Rachynskyy mr...@users.sourceforge.net URL: http://linuxorg.sourceforge.net/ License: GPL-3+ Description: application to track women menstrual cycles Debian already ships it (Cc:ing its maintainer): http://packages.debian.org/pcalendar = $ rmadison pcalendar pcalendar | 3.2.0-2 | wheezy | source, all pcalendar | 3.2.0-2 | sid | source, all pcalendar | 3.3.0-1 | experimental | source, all = Thx, bye, Gismo / Luca pgp4QOLyGH060.pgp Description: PGP signature
Bug#691481: zile: Dangling symlink and missing example
In current upstream (2.4.9), dotzile.sample is installed directly in docdir, i.e. /usr/share/doc/zile for Debian. -- http://rrt.sc3d.org -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#691479: ITP: pcalendar -- application to track women menstrual cycles
Hi, On Fri, Oct 26, 2012 at 05:35:21PM +1100, Dmitry Smirnov wrote: Package: wnpp Severity: wishlist X-Debbugs-CC: debian-de...@lists.debian.org Package name: pcalendar Version: 3.3.0 Upstream Author: Mar'yan Rachynskyy mr...@users.sourceforge.net URL: http://linuxorg.sourceforge.net/ License: GPL-3+ Description: application to track women menstrual cycles $ apt-cache show pcalendar Package: pcalendar Version: 3.3.0-1 Installed-Size: 629 Maintainer: Debian Med Packaging Team debian-med-packag...@lists.alioth.debian.org Architecture: all Depends: default-jre | java5-runtime | java6-runtime, libxerces2-java Description: track menstrual cycles and predict fertility periods ... Kind regards Andreas. -- http://fam-tille.de -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#691439: [Pkg-freeipmi-devel] Bug#691439: Acknowledgement (libfreeipmi12: copyright file missing after upgrade (policy 12.5))
Ferenc Wagner wf...@lant.ki.iif.hu writes: Andreas Beckmann deb...@abeckmann.de writes: That happens during the sid - experimental upgrade, not squeeze-wheezy. Same problem with libipmidetect0. As downloaded from packages.debian.org, libfreeipmi12_1.1.5-4_amd64.deb and libipmidetect0_1.1.5-4_amd64.deb contain symlinks, not directories under usr/share/doc/, pointing to freeipmi-common. However, I can reproduce the issue: # dpkg -i freeipmi-common_1.1.5-3_all.deb libipmidetect0_1.1.5-3_amd64.deb # dpkg -i freeipmi-common_1.1.5-4_all.deb libipmidetect0_1.1.5-4_amd64.deb # ls -ld /usr/share/doc/libipmidetect0 drwxr-xr-x 2 root root 6 Oct 26 09:31 /usr/share/doc/libipmidetect0 which is certainly wrong. But at the same time: # dpkg --purge freeipmi-common libipmidetect0 # dpkg -i freeipmi-common_1.1.5-4_all.deb libipmidetect0_1.1.5-4_amd64.deb # ls -ld /usr/share/doc/libipmidetect0 lrwxrwxrwx 1 root root 15 Jul 11 19:56 /usr/share/doc/libipmidetect0 - freeipmi-common which is the intended behaviour. I'm investigating. I was tripped up by dpkg feature #404850. Will fix this. -- Thanks, Feri. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#691212: a workaround
For now, as a workaround, I do this each time I start the system: $ export LD_LIBRARY_PATH=/usr/lib/x86_64-linux-gnu/ $ gnome-shell --replace otherwise no gnome-shell... I'm waiting for a solution. Best Regards Francesco De Vita -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#691257: js-of-ocaml: The version shipped in this package is 1.1.1, whereas the package is tagged as 1.2
Le 23/10/2012 18:00, Engil Hramn a écrit : I was facing some bugs with my installation of js_of_ocaml, and after checking the library version with ocamlfind, I found out that the version installed on my system was 1.1.1, and not 1.2. I checked the package's sources to confirm it and the VERSION file seems to prove it. Thank you for the report! It appears that the upstream tarball of the Debian package is a snapshot of the darcs repository shortly before the release of version 1.2. There is no difference in the code itself. I (or upstream) must have fucked up something... I'll ask the release team whether the upstream tarball itself can be updated at this stage... Cheers, -- Stéphane -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#660736: icedove aborts
Package: icedove Version: 3.0.11-1+squeeze13 Severity: normal icedove aborts with this error: lili@Peter:~$ icedove /usr/lib/icedove/icedove-bin: symbol lookup error: /usr/lib/icedove/components/libimgicon.so: undefined symbol: NS_GetServiceManager -- System Information: Debian Release: 6.0.6 APT prefers stable APT policy: (500, 'stable') Architecture: i386 (i686) Kernel: Linux 2.6.32-5-686 (SMP w/1 CPU core) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages icedove depends on: ii debianutils 3.4Miscellaneous utilities specific t ii fontconfig2.8.0-2.1 generic font configuration library ii libasound21.0.23-2.1 shared library for ALSA applicatio ii libatk1.0-0 1.30.0-1 The ATK accessibility toolkit ii libc6 2.11.3-4 Embedded GNU C Library: Shared lib ii libcairo2 1.8.10-6 The Cairo 2D vector graphics libra ii libdbus-1-3 1.2.24-4+squeeze1 simple interprocess messaging syst ii libfontconfig12.8.0-2.1 generic font configuration library ii libfreetype6 2.4.2-2.1+squeeze4 FreeType 2 font engine, shared lib ii libgcc1 1:4.4.5-8 GCC support library ii libglib2.0-0 2.24.2-1 The GLib library of C routines ii libgtk2.0-0 2.20.1-2 The GTK+ graphical user interface ii libjpeg62 6b1-1 The Independent JPEG Group's JPEG ii libnspr4-0d 4.8.6-1NetScape Portable Runtime Library ii libnss3-1d3.12.8-1+squeeze5 Network Security Service libraries ii libpango1.0-0 1.28.3-1+squeeze2 Layout and rendering of internatio ii libpng12-01.2.44-1+squeeze4 PNG library - runtime ii libsqlite3-0 3.7.3-1SQLite 3 shared library ii libstartup-notificati 0.10-1 library for program launch feedbac ii libstdc++64.4.5-8The GNU Standard C++ Library v3 ii libx11-6 2:1.3.3-4 X11 client-side library ii libxrender1 1:0.9.6-1 X Rendering Extension client libra ii libxt61:1.0.7-1 X11 toolkit intrinsics library ii psmisc22.11-1utilities that use the proc file s ii zlib1g1:1.2.3.4.dfsg-3 compression library - runtime Versions of packages icedove recommends: ii hunspell-de-de [hunspell-di 20091006-4.2 German dictionary for hunspell ii hunspell-en-us [hunspell-di 20070829-4 English_american dictionary for hu Versions of packages icedove suggests: ii libdbus-glib-1-20.88-2.1 simple interprocess messaging syst ii libgconf2-4 2.28.1-6 GNOME configuration database syste pn libgnome2-0 none (no description available) pn libgnomevfs2-0 none (no description available) ii libgssapi-krb5-21.8.3+dfsg-4squeeze6 MIT Kerberos runtime libraries - k ii ttf-lyx 1.6.7-1 TrueType versions of some TeX font -- 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#691484: unblock: thailatex/0.5.0-3
Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: unblock Please unblock package thailatex It fixes outdated trigger interest. The file has been moved for a long time by texlive, but the change was incomplete in an old upload (0.4.7-3). The debdiff is attached. unblock thailatex/0.5.0-3 -- System Information: Debian Release: wheezy/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.2.0-4-amd64 (SMP w/4 CPU cores) Locale: LANG=th_TH.utf8, LC_CTYPE=th_TH.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash diff -Nru thailatex-0.5.0/debian/changelog thailatex-0.5.0/debian/changelog --- thailatex-0.5.0/debian/changelog2012-08-08 14:32:23.0 +0700 +++ thailatex-0.5.0/debian/changelog2012-10-03 21:40:45.0 +0700 @@ -1,3 +1,10 @@ +thailatex (0.5.0-3) unstable; urgency=low + + * debian/triggers: Update babel.sty trigger watching. +This completes the change introduced in 0.4.7-3. + + -- Theppitak Karoonboonyanan t...@debian.org Wed, 03 Oct 2012 21:40:15 +0700 + thailatex (0.5.0-2) unstable; urgency=low * Build with xz compression. diff -Nru thailatex-0.5.0/debian/triggers thailatex-0.5.0/debian/triggers --- thailatex-0.5.0/debian/triggers 2012-08-08 14:32:23.0 +0700 +++ thailatex-0.5.0/debian/triggers 2012-10-03 21:40:45.0 +0700 @@ -1 +1 @@ -interest /usr/share/texmf-texlive/tex/generic/babel/babel.sty +interest /usr/share/texlive/texmf-dist/tex/generic/babel/babel.sty
Bug#691439: [Pkg-freeipmi-devel] Bug#691439: Acknowledgement (libfreeipmi12: copyright file missing after upgrade (policy 12.5))
Andreas Beckmann deb...@abeckmann.de writes: That happens during the sid - experimental upgrade, not squeeze-wheezy. Same problem with libipmidetect0. As downloaded from packages.debian.org, libfreeipmi12_1.1.5-4_amd64.deb and libipmidetect0_1.1.5-4_amd64.deb contain symlinks, not directories under usr/share/doc/, pointing to freeipmi-common. However, I can reproduce the issue: # dpkg -i freeipmi-common_1.1.5-3_all.deb libipmidetect0_1.1.5-3_amd64.deb # dpkg -i freeipmi-common_1.1.5-4_all.deb libipmidetect0_1.1.5-4_amd64.deb # ls -ld /usr/share/doc/libipmidetect0 drwxr-xr-x 2 root root 6 Oct 26 09:31 /usr/share/doc/libipmidetect0 which is certainly wrong. But at the same time: # dpkg --purge freeipmi-common libipmidetect0 # dpkg -i freeipmi-common_1.1.5-4_all.deb libipmidetect0_1.1.5-4_amd64.deb # ls -ld /usr/share/doc/libipmidetect0 lrwxrwxrwx 1 root root 15 Jul 11 19:56 /usr/share/doc/libipmidetect0 - freeipmi-common which is the intended behaviour. I'm investigating. -- Thanks, Feri. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#691485: Security vulnerabilities in RT
package: request-tracker3.8 severity: critical tags: security From the RT mailing lists: We have determined a number of security vulnerabilities which affect both RT 3.8.x and RT 4.0.x. We are releasing RT versions 3.8.15 and 4.0.8, and RTFM version 2.4.5, to resolve these vulnerabilities, as well as patches which apply atop all released versions of 3.8 and 4.0. The vulnerabilities addressed by 3.8.15, 4.0.8, and the below patches include the following: All versions of RT are vulnerable to an email header injection attack. Users with ModifySelf or AdminUser can cause RT to add arbitrary headers or content to outgoing mail. Depending on the scrips that are configured, this may be be leveraged for information leakage or phishing. We have been assigned CVE-2012-4730 for this vulnerability; we would like to thank Scott MacVicar for bringing this matter to our attention. RT 4.0.0 and above and RTFM 2.0.0 and above contain a vulnerability due to lack of proper rights checking, allowing any privileged user to create Articles in any class. We have been assigned CVE-2012-4731 for this vulnerability. All versions of RT with cross-site-request forgery (CSRF) protection (RT 3.8.12 and above, RT 4.0.6 and above, and any instances running the security patches released 2012-05-22) contain a vulnerability which incorrectly allows though CSRF requests which toggle ticket bookmarks. We have been assigned CVE-2012-4732 for this vulnerability; we would like to thank Matthew Astley for bringing this to our attention. Additionally, all versions of RT are vulnerable to a confused deputy attack on the user. While not strictly a CSRF attack, users who are not logged in who are tricked into following a malicious link may, after supplying their credentials, be subject to an attack which leverages their credentials to modify arbitrary state. While users who were logged in would have observed the CSRF protection page, users who were not logged in receive no such warning due to the intervening login process. RT has been extended to notify users of pending actions during the login process. We have been assigned CVE-2012-4734 for this vulnerability; we would like to thank Matthew Astley for bringing this to our attention. RT 3.8.0 and above are susceptible to a number of vulnerabilities concerning improper signing or encryption of messages using GnuPG; if GnuPG is not enabled, none of the following affect you. We have been assigned CVE-2012-4735 for the following related vulnerabilities: * When using GnuPG, RT now clarifies the concepts of signing for _integrity_ and signing for _authentication_, which are separate (and exclusive) concepts. Previously, enabling the Sign by default queue configuration began signing automatically-generated messages with the queue's key, in addition to defaulting emails sent from the web UI to being signed. This provides integrity, but causes emails signed with that key to no longer possess authenticity; no individual email is guaranteed to have come from an actor designated to act for that key, in the case of automatically-generated emails. RT has now changed the Sign by default checkbox to merely provide a default in the web UI when composing messages; it no longer affects automatically-generated outgoing messages. Thus the Sign by default option helps to provide _authenticity_. A separate queue configuration option, Sign all auto-generated mail (defaulting to off) now controls the signing of automatically- generated emails, which (when used in combination with the previous option) helps provide _integrity_ of all outgoing messages. Users who had previously checked Sign by default and who wish to maintain the previous effect of integrity but not authenticity will need to enable the new option as well. We would like to thank Matthijs Melissen (University of Luxembourg) for bringing this matter to our attention. * RT 3.8.0 and above contain a vulnerability which allows incoming emails to force all triggered outgoing mail to be signed and/or encrypted. * RT 3.8.0 and above contain a vulnerability which allows incoming emails to incorrectly appear in the UI to have been encrypted when they had not been. This vulnerability only applies to encryption, not signing. * RT 3.8.0 and above contain a vulnerability which allows any user who is capable of sending signed email in the UI to do so using any secret key stored in RT's keyring. Additionally, RT 3.8.0 and above contain a vulnerability which allows a user to pass arbitrary arguments to the command-line GnuPG client, which could be leveraged to create arbitrary files on disk with the permissions of the webserver. This vulnerability only applies if GnuPG is enabled, and does _not_ allow for execution of programs other than the command-line GnuPG client. We have been assigned CVE-2012-4884 for this
Bug#691486: Security vulnerabilities in RT
package: request-tracker4 severity: critical tags: security From the RT mailing lists: We have determined a number of security vulnerabilities which affect both RT 3.8.x and RT 4.0.x. We are releasing RT versions 3.8.15 and 4.0.8, and RTFM version 2.4.5, to resolve these vulnerabilities, as well as patches which apply atop all released versions of 3.8 and 4.0. The vulnerabilities addressed by 3.8.15, 4.0.8, and the below patches include the following: All versions of RT are vulnerable to an email header injection attack. Users with ModifySelf or AdminUser can cause RT to add arbitrary headers or content to outgoing mail. Depending on the scrips that are configured, this may be be leveraged for information leakage or phishing. We have been assigned CVE-2012-4730 for this vulnerability; we would like to thank Scott MacVicar for bringing this matter to our attention. RT 4.0.0 and above and RTFM 2.0.0 and above contain a vulnerability due to lack of proper rights checking, allowing any privileged user to create Articles in any class. We have been assigned CVE-2012-4731 for this vulnerability. All versions of RT with cross-site-request forgery (CSRF) protection (RT 3.8.12 and above, RT 4.0.6 and above, and any instances running the security patches released 2012-05-22) contain a vulnerability which incorrectly allows though CSRF requests which toggle ticket bookmarks. We have been assigned CVE-2012-4732 for this vulnerability; we would like to thank Matthew Astley for bringing this to our attention. Additionally, all versions of RT are vulnerable to a confused deputy attack on the user. While not strictly a CSRF attack, users who are not logged in who are tricked into following a malicious link may, after supplying their credentials, be subject to an attack which leverages their credentials to modify arbitrary state. While users who were logged in would have observed the CSRF protection page, users who were not logged in receive no such warning due to the intervening login process. RT has been extended to notify users of pending actions during the login process. We have been assigned CVE-2012-4734 for this vulnerability; we would like to thank Matthew Astley for bringing this to our attention. RT 3.8.0 and above are susceptible to a number of vulnerabilities concerning improper signing or encryption of messages using GnuPG; if GnuPG is not enabled, none of the following affect you. We have been assigned CVE-2012-4735 for the following related vulnerabilities: * When using GnuPG, RT now clarifies the concepts of signing for _integrity_ and signing for _authentication_, which are separate (and exclusive) concepts. Previously, enabling the Sign by default queue configuration began signing automatically-generated messages with the queue's key, in addition to defaulting emails sent from the web UI to being signed. This provides integrity, but causes emails signed with that key to no longer possess authenticity; no individual email is guaranteed to have come from an actor designated to act for that key, in the case of automatically-generated emails. RT has now changed the Sign by default checkbox to merely provide a default in the web UI when composing messages; it no longer affects automatically-generated outgoing messages. Thus the Sign by default option helps to provide _authenticity_. A separate queue configuration option, Sign all auto-generated mail (defaulting to off) now controls the signing of automatically- generated emails, which (when used in combination with the previous option) helps provide _integrity_ of all outgoing messages. Users who had previously checked Sign by default and who wish to maintain the previous effect of integrity but not authenticity will need to enable the new option as well. We would like to thank Matthijs Melissen (University of Luxembourg) for bringing this matter to our attention. * RT 3.8.0 and above contain a vulnerability which allows incoming emails to force all triggered outgoing mail to be signed and/or encrypted. * RT 3.8.0 and above contain a vulnerability which allows incoming emails to incorrectly appear in the UI to have been encrypted when they had not been. This vulnerability only applies to encryption, not signing. * RT 3.8.0 and above contain a vulnerability which allows any user who is capable of sending signed email in the UI to do so using any secret key stored in RT's keyring. Additionally, RT 3.8.0 and above contain a vulnerability which allows a user to pass arbitrary arguments to the command-line GnuPG client, which could be leveraged to create arbitrary files on disk with the permissions of the webserver. This vulnerability only applies if GnuPG is enabled, and does _not_ allow for execution of programs other than the command-line GnuPG client. We have been assigned CVE-2012-4884 for this
Bug#689315: zic: creates dangling symlink for /etc/localtime
Le 01/10/2012 16:18, John Paul Adrian Glaubitz a écrit : Package: libc-bin Version: 2.13-35 Severity: important Hello, the version of 'zic' in 'libc-bin' in Debian Wheezy seems to no longer creates the localtime conversion file correctly. On Debian Squeeze: root@squeeze32:~ zic -l Europe/Berlin root@squeeze32:~ file /etc/localtime /etc/localtime: timezone data, version 2, 8 gmt time flags, 8 std time flags, no leap seconds, 144 transition times, 8 abbreviation chars On Debian Wheezy: root@wheezy32:~ zic -l Europe/Berlin root@wheezy32:~ file /etc/localtime /etc/localtime: broken symbolic link to `../posix/Europe/Berlin' zic obviously tries to create a symbolic link to the correct timezone conversion file. Alas, the symbolic link created is relative and the source directory is obviously a subdirectory of /usr/share/zoneinfo while the localtime conversion file is saved as /etc/localtime, hence a dangling symbolic link is created. I am not able to reproduce this issue. Are you sure that /etc/localtime was not a broken symlink already before running the zic command? Aurelien -- Aurelien Jarno GPG: 1024D/F1BCDB73 aurel...@aurel32.net http://www.aurel32.net -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#689415: RFS: flvmeta/1.1.0-1 -- Metadata injector for FLV video files
On Fri, Oct 12, 2012 at 6:25 PM, Neutron Soutmun neo.neut...@gmail.com wrote: BTW, the hyphen-used-as-minus-sign warning are not fixed yet, as the manpage was generated by pandoc, and there is an issue [1] for this case. However, the upstream considers to not accept the patch, the question is, have this issue to be really fixed ? The discussion seems positive for the change. I've uploaded it anyway, so it's not further delayed. Please follow up the issue after that. Regards, -- Theppitak Karoonboonyanan http://linux.thai.net/~thep/ -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#691487: column: segfaults with a certain data and column -ets,
Package: bsdmainutils Version: 9.0.3 Severity: normal File: /usr/bin/column The attached text file and this command segfaults column: column -ets, foo bar I note however that this command or different data does not: column -ts, foo bar -- System Information: Debian Release: wheezy/sid APT prefers testing APT policy: (700, 'testing'), (600, 'unstable'), (550, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 3.5-trunk-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages bsdmainutils depends on: ii bsdutils 1:2.20.1-5.2 ii debianutils 4.3.2 ii libc62.13-35 ii libncurses5 5.9-10 ii libtinfo55.9-10 Versions of packages bsdmainutils suggests: ii cpp 4:4.7.1-1 ii miscfiles [wordlist] 1.4.2.dfsg.1-9 pn vacation none ii wamerican [wordlist] 7.1-1 ii whois 5.0.18 ii wspanish [wordlist] 1.0.26 -- bye, pabs http://wiki.debian.org/PaulWise pos[0], -size[1]+pos[1], pos[2] pos[0], pos[1], pos[2] -size[0]+pos[0], pos[1], pos[2] pos[0], -size[1]+pos[1], pos[2] -size[0]+pos[0], pos[1], pos[2] -size[0]+pos[0], -size[1]+pos[1], pos[2] size[0]+pos[0], -size[1]+pos[1], pos[2] size[0]+pos[0], pos[1], pos[2] pos[0], pos[1], pos[2] size[0]+pos[0], -size[1]+pos[1], pos[2] pos[0], pos[1], pos[2] pos[0], -size[1]+pos[1], pos[2] size[0]+pos[0], pos[1], pos[2] size[0]+pos[0], size[1]+pos[1]+0.1, pos[2] pos[0], size[1]+pos[1]+0.1, pos[2] size[0]+pos[0], pos[1], pos[2] pos[0], size[1]+pos[1]+0.1, pos[2] pos[0], pos[1], pos[2] pos[0], pos[1], pos[2] pos[0], size[1]+pos[1]+0.1, pos[2] -size[0]+pos[0], size[1]+pos[1]+0.1, pos[2] pos[0], pos[1], pos[2] -size[0]+pos[0], size[1]+pos[1]+0.1, pos[2] -size[0]+pos[0], pos[1], pos[2] signature.asc Description: This is a digitally signed message part
Bug#691399: Acknowledgement (freedoom: New upstream (beta) release)
On Fri, Oct 26, 2012 at 10:06:40AM +0200, Fabian Greffrath wrote: please consider uploading the new freedoom beta release. Would you mind if I took care of that myself? No problem - please go ahead! -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#691257: Freeze exception request for js_of_ocaml 1.2-2
Dear Release Team, Bug #691257 made me realize that the upstream tarball of the Debian package is not the same as the one currently available on the upstream website, and the contents does not match tag 1.2 in the upstream repository either. There is one commit missing. It changes only changelog and version, and I would like to update the Debian package with it. Attached is a debdiff. Cheers, -- Stéphane diff -Nru js-of-ocaml-1.2/debian/changelog js-of-ocaml-1.2/debian/changelog --- js-of-ocaml-1.2/debian/changelog 2012-06-08 07:23:02.0 +0200 +++ js-of-ocaml-1.2/debian/changelog 2012-10-26 10:20:28.0 +0200 @@ -1,3 +1,9 @@ +js-of-ocaml (1.2-2) unstable; urgency=low + + * Update upstream changelog and version (Closes: #691257) + + -- Stéphane Glondu glo...@debian.org Fri, 26 Oct 2012 10:18:47 +0200 + js-of-ocaml (1.2-1) unstable; urgency=low * New upstream release diff -Nru js-of-ocaml-1.2/debian/patches/0001-Changelog-and-version.patch js-of-ocaml-1.2/debian/patches/0001-Changelog-and-version.patch --- js-of-ocaml-1.2/debian/patches/0001-Changelog-and-version.patch 1970-01-01 01:00:00.0 +0100 +++ js-of-ocaml-1.2/debian/patches/0001-Changelog-and-version.patch 2012-10-26 10:20:28.0 +0200 @@ -0,0 +1,40 @@ +From: Stephane Glondu st...@glondu.net +Date: Fri, 26 Oct 2012 10:14:29 +0200 +Subject: Changelog and version + +Origin: upstream, http://ocsigen.org/darcsweb/?r=js_of_ocaml;a=commit;h=20120530130902-4e2d2-a51cd5bebba852be2e409cb076f8b300dea37cf9.gz +Bug-Debian: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=691257 +--- + CHANGES | 13 + + VERSION |2 +- + 2 files changed, 14 insertions(+), 1 deletion(-) + +diff --git a/CHANGES b/CHANGES +index 1608ba0..1701902 100644 +--- a/CHANGES b/CHANGES +@@ -1,3 +1,16 @@ ++ ++= 1.2 (2012-06-02) = ++ ++ * Bugfixes ++ ** Fix #284 ++ ** Fix return type of window##open_ ++ ++ * Features/Changes ++ ** Improvements in the data-flow solver ++ ** Add Dom_html.window##onscroll ++ ** Dom_events.listen: handler should return boolean ++ ** Add DOM drag/drop events ++ + = 1.1.1 (2012-03-15) = + + * Bugfixes: +diff --git a/VERSION b/VERSION +index 524cb55..5625e59 100644 +--- a/VERSION b/VERSION +@@ -1 +1 @@ +-1.1.1 ++1.2 +-- diff -Nru js-of-ocaml-1.2/debian/patches/series js-of-ocaml-1.2/debian/patches/series --- js-of-ocaml-1.2/debian/patches/series 1970-01-01 01:00:00.0 +0100 +++ js-of-ocaml-1.2/debian/patches/series 2012-10-26 10:20:28.0 +0200 @@ -0,0 +1 @@ +0001-Changelog-and-version.patch
Bug#681280: kernel warning at .../net/sched/sch_generic.c:255 dev_watchdog - eth0 (sky2) transmit queue 0 timed out
Hello, On Wed, Oct 24, 2012 at 10:52:48PM +0100, Julian Gilbey wrote: Oh, it just finished this time! I now understand why it took so long - the -dbg package is *huge*! It would be nice to get support for DEBIAN_KERNEL_USE_CCACHE and DEBIAN_KERNEL_DISABLE_DEBUG info test-patches. Best regards Uwe -- Pengutronix e.K. | Uwe Kleine-König| Industrial Linux Solutions | http://www.pengutronix.de/ | -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#691257: js-of-ocaml: The version shipped in this package is 1.1.1, whereas the package is tagged as 1.2
Le 26/10/2012 09:49, Stéphane Glondu a écrit : I'll ask the release team whether the upstream tarball itself can be updated at this stage... Well, it appears that the upstream tarball doesn't match the upstream tag and includes an additional commit (addition of module Lwt_js_events), which we cannot add to the Debian package at this stage of the release. Therefore, I will include only the version (and changelog) change, if approved by the Release Team. Cheers, -- Stéphane -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#691488: cron: bytes variable in do_command.c/child_process() is always 1
Package: cron Version: 3.0pl1-124 Severity: minor The patches, including the latest -124, removed incrementing of the 'bytes' variable, so when the mail process fails, there is always 1 in log message: (mailed 1 byte of output; but got status ... It would also be great if the log message included, where the status was got from. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#691469: fetchmail apprently uses mboxo format, which irrecoverably corrupts mail
On 26/10/2012 02:24, Christoph Anton Mitterer wrote: This is basically the same as Debian bugs #690741 and #633799. I used severity critical, as the mboxo format causes irrecoverable mail corruption, which is unknown to most users. I don't think the severity of critical is justified. This is an artefact of the way email has been stored for decades. Just because Christoph was not previously aware of it does not suddenly make it a critical bug. This is also the way mail is handled by the default MTA in a standard Debian installation. Not that I'm saying it shouldn't be improved, just that it hasn't yet caused the world to end. Roger (Just a Fetchmail user. Not speaking for Debian or Fetchmail) -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#691487: column: segfaults with a certain data and column -ets,
usertags 691487 + malloc retitle 691487 column: memory allocation issue with a certain data and column -ets, thanks The attached text file and this command segfaults column: column -ets, foo bar Sorry for the noise, this only happens when I turn on malloc checks: export MALLOC_CHECK_=2 export MALLOC_PERTURB_=$(($RANDOM % 255 + 1)) valgrind also reports a problem: ==15631== Invalid read of size 8 ==15631==at 0x401704: ??? (in /usr/bin/column) ==15631==by 0x401004: ??? (in /usr/bin/column) ==15631==by 0x4E4DEAC: (below main) (libc-start.c:228) ==15631== Address 0x51bb310 is 0 bytes after a block of size 0 alloc'd ==15631==at 0x4C272B8: calloc (in /usr/lib/valgrind/vgpreload_memcheck-amd64-linux.so) ==15631==by 0x4015AC: ??? (in /usr/bin/column) ==15631==by 0x401004: ??? (in /usr/bin/column) ==15631==by 0x4E4DEAC: (below main) (libc-start.c:228) -- bye, pabs http://wiki.debian.org/PaulWise signature.asc Description: This is a digitally signed message part
Bug#691489: lintian: section: tasks seem to imply empty-binary-package
Package: lintian Version: 2.5.10.2 Severity: minor Packages in the tasks section should probably be considered ok even if they are empty[0]. ~Niels [0] http://lintian.debian.org/maintainer/debian-b...@lists.debian.org.html#tasksel -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#687398: Now FTBFS...?
On Fri, Oct 26, 2012 at 12:35:06AM -0400, Asheesh Laroia wrote: I just tried to build my debdiff and do an NMU, and it ends with this message: Finished tests in 0.001844s, 2711.3306 tests/s, 15725.7175 assertions/s. 5 tests, 29 assertions, 0 failures, 0 errors, 0 skips make[1]: Leaving directory `/tmp/buildd/rhash-1.2.9/bindings' /usr/bin/make -C bindings build LIBRHASH_INC=-I/tmp/buildd/rhash-1.2.9/debian/tmp LIBRHASH_LD=-Wl,--as-needed -L/tmp/buildd/rhash-1.2.9/debian/tmp BINDINGS=mono make[1]: Entering directory `/tmp/buildd/rhash-1.2.9/bindings' make -C mono make[2]: Entering directory `/tmp/buildd/rhash-1.2.9/bindings/mono' gmcs -target:library -define:UNIX -out:RHash.dll -debug -keyfile:RHash.snk AssemblyInfo.cs Bindings.cs Hasher.cs HashType.cs make[2]: gmcs: Command not found make[2]: *** [RHash.dll] Error 127 make[2]: Leaving directory `/tmp/buildd/rhash-1.2.9/bindings/mono' make[1]: *** [build-mono] Error 2 make[1]: Leaving directory `/tmp/buildd/rhash-1.2.9/bindings' make: *** [build-indep] Error 2 dpkg-buildpackage: error: debian/rules build gave error exit status 2 E: Failed autobuilding of package I: unmounting dev/pts filesystem I: unmounting proc filesystem I: cleaning the build env I: removing directory /var/cache/pbuilder/build//16252 and its subdirectories ...why is gmcs not findable in my pbuilder chroot? I checked, and mono-gmcs is still a dependency. Yeah, I've seen that too. mono-gmcs was not installed by pbuilder even though it's in the deps, but mono-gmcs (= 1.1.8) | c-sharp-2.0-compiler dep was apparently resolved by mono-devel pulled by other deps (actually I don't know whether pbuilder dep resolution works that way or there is something else happening here). -- WBR, wRAR signature.asc Description: Digital signature
Bug#691449: dpkg-buildflags should have an export mode for shell scripts
On 25.10.2012 21:20, Guillem Jover wrote: On Thu, 2012-10-25 at 11:53:47 -0700, Jonathan Nieder wrote: Matthias Klose wrote: A lot of rules files uses loops around configure calls, however there's no export mode which escapes the spaces in the output. Please add one. The sh mode won't work either for this case. Doesn't set -e; \ eval $$(dpkg-buildflags --export=sh); \ for v in $(versions); \ do \ ... \ done work? the eval trick does work, however the variables are then passed in the environment, not on the command line. I don't think it makes a difference for GNU autoconf, but it might not be appropriate for other build systems. Or just “$(shell dpkg-buildflags --export=configure)”? I do not really see a problem here. I might be missing something else going on, but otherwise I'll be closing this report in a bit. No. Doesn't work if the call depends on the loop variable. (In addition using $(shell) allows to set a variables once per Makefile, and not once per loop.) Right, but that's needed for stuff like for p in $(filter-out $(PYTHON_DEFAULT), $(PYTHONS)) \ ; do \ dh_auto_configure --builddir=$(CURDIR)/debian/build-$$p \ -- \ $(BARE_CONFIG_FLAGS) \ --disable-ruby \ PYTHON=$$p \ $$(DEB_CFLAGS_MAINT_APPEND=$$($$p-config --includes) dpkg-buildflags --export=configure); \ done -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#690291:
Can you try removing the pulseaudio package, rebooting, and then try your testing again? -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#691399: Acknowledgement (freedoom: New upstream (beta) release)
Am 26.10.2012 10:16, schrieb Jon Dowland: No problem - please go ahead! Done. I've seen you removed yourself from Uploaders, so I changed the packaging style to meet my own. I hope you don't mind. I'd say the package is ready for upload. It is currently targeted at unstable, maybe this should get changed to experimental during the freeze. Would you mind sponsoring the package? I am neither DM nor DD. - Fabian -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#691257: js-of-ocaml: The version shipped in this package is 1.1.1, whereas the package is tagged as 1.2
Well, it appears that the upstream tarball doesn't match the upstream tag and includes an additional commit (addition of module Lwt_js_events), which we cannot add to the Debian package at this stage of the release. It's actually this missing commit that prevent my project to compile, sadly. Is there any other solution ? Like at least add a warning for future user that this package isn't the full js_of_ocaml 1.2 release ?
Bug#691366: wheezy 2012-10-24 daily built netinst
On 10/26/2012 12:11 AM, Philipp Kern wrote: And the error message is: /etc/network/interfaces:15: misplaced option ifup: couldn't read interfaces file /etc/network/interfaces Looks pretty dangerous. However, as mentioned, everything worked though. (In the meantime I commented out the privext 2 line and the error message vanished.) Added to the errata[1], thanks. Not quite correct. I had the same effect in my first installation (GNOME) *and* in my second installation (KDE). Best Stephan -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#688069: liblocale-subcountry-perl: Version checks fail (our $VERSION moved before package Locale::SubCountry)
On Wed, Oct 24, 2012 at 08:41:54PM +0200, gregor herrmann wrote: On Tue, 18 Sep 2012 13:54:35 -0700, Ivan Kohler wrote: $ perl -e 'use Locale::SubCountry 54' Locale::SubCountry does not define $Locale::SubCountry::VERSION--version check failed at -e line 1. Sometime after version 1.50, our $VERSION = 1.xx was moved to the top of the code, above any package declaration. It is therefore not declaring $Locale::SubCountry::VERSION, and previously-working version checks like use Locale::SubCountry 1.42 now throw a fatal error. The patch below adds a package Locale::SubCountry to the beginning of the code. This seems like typical / best practice for modules, to avoid any symbol exports from the intial use statements from polluting the main:: namespace. Are you going to upload the fixed package? Or should someone else go ahead? Since wheezy isn't affected (or released) and upstream hasn't yet responded/updated, I guess I was more in a holding pattern over here with regard to this. Anyone else may feel free to go ahead and upload. -- _ivan -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#691490: wims: missing source
Package: src:wims Version: 4.00-1 Severity: serious I cannot find the source code for: wims/bin/true wims/bin/false wims/public_html/java/geogebra/*.jar wims/public_html/java/geogebra3/*.jar wims/public_html/java/jmol/*.jar wims/public_html/flash/*.swf This affects both the versions 4.00-4+squeeze1 in stable and 4.04-3 in unstable. Ansgar -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#691399: Acknowledgement (freedoom: New upstream (beta) release)
On Fri, Oct 26, 2012 at 11:13:45AM +0200, Fabian Greffrath wrote: Am 26.10.2012 10:16, schrieb Jon Dowland: No problem - please go ahead! Done. Great stuff! One question: why 1.8~beta1 for the upstream release? Why not 1.8-beta1 (matching the upstream tarball more closely) I've seen you removed yourself from Uploaders, so I changed the packaging style to meet my own. I hope you don't mind. No problem. Although It appears I never uploaded the release removing myself, and I've since re-joined the games team, so I've re-added myself. I just deleted the 0.7-2 changelog entry and the corresponding stanza in the latest entry. All your changes look good. I'd say the package is ready for upload. It is currently targeted at unstable, maybe this should get changed to experimental during the freeze. Unstable should be fine. No-one will ever see it in experimental. If we have to do a testing-targeted update we can use t-p-u but I very much doubt we will. Would you mind sponsoring the package? I am neither DM nor DD. No problem, I'll do it today. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#691491: src:wims: copyright information incomplete
Package: src:wims Version: 4.00-1 Severity: serious The copyright information for wims is very incomplete. For example the copyright information for wims/public_html/scripts/js/keyboard/* and wims/public_html/scripts/js/jsxgraph/jsxgraphcore.js is missing (jsxgraphcore.js is also missing source). This affects both 4.00-4+squeeze1 in squeeze and 4.04-3 in unstable. Ansgar -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#691492: jnunemaker-matchy ? A gem to match RSpec-esque for use in Test::Unit
Package: wnpp Severity: wishlist Owner: Nandaja Varmanandaja.va...@gmail.com *Package name :jnunemaker-matchy Version:0.4.0 Upstream Author:Jeremy McAnally ,John Nunemaker nunema...@gmail.com *URL:https://github.com/jnunemaker/matchy *License:MIT License *Description:RSpec-esque matchers for use in Test::Unit -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#688932: g_get_user_{cache,config,data}_dir () fail to meet XDG Base Directory Specification
reopen688932
retitle 688932 g_get_user_{cache,config,data}_dir () fail to meet XDG Base
Directory Specification
severity 688932 minor
thanks
[Re-opening, as it's essentially the same issue, and it's /not/
resolved. I also hope to forward this one to the upstream
tracker, possibly with a patch, sometime next week.]
As per XDG Base Directory Specification 0.8 (quoted below), the
default values for XDG_CACHE_HOME, XDG_CONFIG_HOME, and
XDG_DATA_HOME, are both defined relative to the value of the
HOME environment variable. Contrary to that, the respective
g_get_user_{cache,config,data}_dir () functions return values
relative to the user's /initial/ home directory (as per
getpwuid ()-pw_dir) by default instead.
Consider, e. g. (the source is MIME'd):
$ LC_ALL=C make LDFLAGS=-lglib-2.0 ugpzy4dbahtheg6tnc1m39anxd
cc -lglib-2.0 ugpzy4dbahtheg6tnc1m39anxd.c -o ugpzy4dbahtheg6tnc1m39anxd
$ ./ugpzy4dbahtheg6tnc1m39anxd
XDG_CACHE_HOME = /home/private/users/jrh/.cache
XDG_CONFIG_HOME = /home/private/users/jrh/.config
XDG_DATA_HOME = /home/private/users/jrh/.local/share
$ HOME=$(mktemp -dt -- foo.) ./ugpzy4dbahtheg6tnc1m39anxd
XDG_CACHE_HOME = /home/private/users/jrh/.cache
XDG_CONFIG_HOME = /home/private/users/jrh/.config
XDG_DATA_HOME = /home/private/users/jrh/.local/share
$ (HOME=$(mktemp -dt -- foo.) \
XDG_CACHE_HOME=${HOME}/.cache \
XDG_CONFIG_HOME=${HOME}/.config \
XDG_DATA_HOME=${HOME}/.local/share \
./ugpzy4dbahtheg6tnc1m39anxd)
XDG_CACHE_HOME = /tmp/foo.nmGK6HNL/.cache
XDG_CONFIG_HOME = /tmp/foo.nmGK6HNL/.config
XDG_DATA_HOME = /tmp/foo.nmGK6HNL/.local/share
$
The end result is that the calling applications become
non-compliant to the specification.
Could this please be fixed?
TIA.
PS. As it seems, the easiest way to fix this issue is to change
g_get_home_dir () to prefer HOME over the value returned by
getpwuid () (either in the “sane” cases, or always), as was
suggested before. This would also fix the applications which
choose not to use g_get_user_*_dir (), and call the plain old
g_get_home_dir () instead.
--cut: http://standards.freedesktop.org/basedir-spec/basedir-spec-0.8.html --
$XDG_DATA_HOME defines the base directory relative to which user
specific data files should be stored. If $XDG_DATA_HOME is either
not set or empty, a default equal to $HOME/.local/share should be
used.
$XDG_CONFIG_HOME defines the base directory relative to which user
specific configuration files should be stored. If $XDG_CONFIG_HOME is
either not set or empty, a default equal to $HOME/.config should be
used.
…
$XDG_CACHE_HOME defines the base directory relative to which user
specific non-essential data files should be stored. If
$XDG_CACHE_HOME is either not set or empty, a default equal to
$HOME/.cache should be used.
--cut: http://standards.freedesktop.org/basedir-spec/basedir-spec-0.8.html --
--
FSF associate member #7257
/*** ugpzy4dbahtheg6tnc1m39anxd.c -*- C -*- */
#include stdio.h
const char *g_get_user_cache_dir (void);
const char *g_get_user_config_dir (void);
const char *g_get_user_data_dir (void);
int
main ()
{
printf ((XDG_CACHE_HOME = %s\n
XDG_CONFIG_HOME = %s\n
XDG_DATA_HOME = %s\n),
g_get_user_cache_dir (),
g_get_user_config_dir (),
g_get_user_data_dir ());
/* . */
return 0;
}
/*** ugpzy4dbahtheg6tnc1m39anxd.c ends here */
Bug#691399: Acknowledgement (freedoom: New upstream (beta) release)
Am 26.10.2012 11:41, schrieb Jon Dowland: One question: why 1.8~beta1 for the upstream release? Why not 1.8-beta1 (matching the upstream tarball more closely) Because that's recommended by Policy: http://www.debian.org/doc/debian-policy/footnotes.html#f37 Releases with '~' sort earlier than the ones without. This way we do not have to introduce an epoch or ugly hacks like '8.0-final' in order to have the final release sort later than the pre-release. No problem. Although It appears I never uploaded the release removing myself, and I've since re-joined the games team, so I've re-added myself. I just deleted the 0.7-2 changelog entry and the corresponding stanza in the latest entry. All your changes look good. Thanks, great to have you back in the team! - Fabian -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#681419: Proposed ballot for free/non-free dependencies question
Thanks Colin for this draft! On Thu, Oct 25, 2012 at 03:05:30PM +0100, Colin Watson wrote: The Technical Committee has been asked to determine whether a dependency of the form package-in-main | package-in-non-free complies with this policy requirement, or whether virtual packages must instead be used to avoid mentioning the non-free alternative. […] B 6. Virtual packages are a suitable existing mechanism for packages to Bdeclare the set of abstract features they provide, and allow Bpackages in main to depend on such abstract features without Bneeding to name every (free or non-free) alternative. […] B 8. We recommend that affected packages consider the use of virtual Bpackages instead. I've a concern about option (B), which I haven't seen addressed in this draft, and that I think it should be addressed before voting (yes, I realize this is a discussion draft, but the sooner the better :-)). It seems to me that the two alternative encodings being discussed have a fundamental difference: 1) package-in-main | package-in-non-free encodes alternative *and* preference for the DFSG-free version 2) virtual-package only encodes alternative between a number of alternatives, some of which are free some of which are not I think you should reword (2), so that the usage of virtual packages is accompanied by an explicit preferences on the free alternative, similarly to what we do for virtual packages when they're used as build dependencies, i.e.: Package: package-in-main Provide: virtual-package Package: package-in-non-free Provide: virtual-package Package: client1 Depends: package-in-main | virtual-package Package: client2 Depends: package-in-main | virtual-package I'm a bit on the extreme said perhaps, but I think we should *mandate* that client packages use the package-in-main | alternative and use it before virtual-package in the disjunction. Otherwise we risk having a significant regression. (I'm not sure if it is up to the tech-ctte to mandate this or, say, to the Policy.) I've skimmed briefly through policy, trying to find out whether package managers are supposed to favor package in main over packages in other suites, but haven't find it yet. If there is something like that already, then probably the above is redundant. But even in that case, I'd rather err on the safe side and at least recommend it in the ruling. Cheers. -- Stefano Zacchiroli . . . . . . . z...@upsilon.cc . . . . o . . . o . o Maître de conférences . . . . . http://upsilon.cc/zack . . . o . . . o o Debian Project Leader . . . . . . @zack on identi.ca . . o o o . . . o . « the first rule of tautology club is the first rule of tautology club » signature.asc Description: Digital signature
Bug#691469: fetchmail apprently uses mboxo format, which irrecoverably corrupts mail
On Fri, 2012-10-26 at 09:22 +0100, Roger Lynn wrote: I don't think the severity of critical is justified. Well that's always something one can argue about... and the maintainers are free to decrease it...it's just what I'd have set it to, which I reasoned why. This is an artefact of the way email has been stored for decades. No, not really... the mboxo format is long ago deprecated.. and most MUAs/servers/clients do it right (by using another format). mutt, Kmail, dovecote... just to name some examples. Just because Christoph was not previously aware of it does not suddenly make it a critical bug. Well I think this is less about me, especially as I don't use fetchmail... I asked around several people at the local computing centre (which is the biggest research computing centre in Europe), all studied computer scientists... all decent sysadmins. Most of them were not even aware, that there are different mbox formats, or some of them broken. That's also what seems to apply to the Evolution/getmail people (of course with exceptions), when I reported the issue there earlier. This is also the way mail is handled by the default MTA in a standard Debian installation. If that's true... it would put a new light on whether Debian should use exim as Default ;) just that it hasn't yet caused the world to end. Admittedly, most people see it like that... but I disagree. Not only would it break signatures (crypto)... but storing mail is just one of THE core businesses of fetchmail... and if it does this wrong, than IMHO that's critical. Cheers, Chris. smime.p7s Description: S/MIME cryptographic signature
Bug#691493: missing source for *.jar
Package: src:jsxgraph Version: 0.83+svn1872~dfsg-3 Severity: serious The source for tools/yuicompressor-2.4.2/lib/*.jar is not included in the source tarball. Ansgar -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#690525: actually a master problem
reassign 690525 salt-master thanks It seems like the client is doing everything right in trying to reestablish a connection to the master continuously. Therefore, this is a problem on the master side (unless the client is sending garbage). Why is the master refusing (terminating) the connection? -- .''`. martin f. krafft madduck@d.o Related projects: : :' : proud Debian developer http://debiansystem.info `. `'` http://people.debian.org/~madduckhttp://vcs-pkg.org `- Debian - when you have better things to do than fixing systems digital_signature_gpg.asc Description: Digital signature (see http://martin-krafft.net/gpg/sig-policy/999bbcc4/current)
Bug#689315: zic: creates dangling symlink for /etc/localtime
On Fri, Oct 26, 2012 at 10:11:45AM +0200, Aurelien Jarno wrote: I am not able to reproduce this issue. Are you sure that /etc/localtime was not a broken symlink already before running the zic command? Interesting, I cannot reproduce the issue anymore either and I am pretty sure it occurred the way I described it. Strangely, there has been no updated to libc-bin ever since, so this cannot be a bug in zic. However, tzdata has been recently upgraded. I don't know, but maybe it's somehow related? In any case, I can remove the local workaround here and close the bug. Adrian -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#682099: xserver-xorg-video-ati: EXAPixmaps=On screen tearing at high resolution under certain configurations
Can you try a newer kernel? 3.6 or 3.7? That may help with the modesettings. As for the acceleration, corruption, you might try a newer version of mesa. I cheated a little and tried the latest aptosid kernel linux-image-aptosid-amd64_3.6-12_amd64 - same screen corruption issues. I followed some documentation and started to compile and install the latest mesa on Sid... I gave up after a few hours and as a test installed Arch as it has a new Kernel 3.6.3-1 and the latest Mesa 9.0-1 - Still had screen corruption issues. Bad for a Debian bug report, sorry about that but I was getting a bit frustrated. I can't help but think it's something to do with the monitors. I mean, why would a different model monitor (Benq) that has native 1920x1080 work fine when used paired with one of my AOC's? But using the 2 identical model AOC's causes the problem? I am going to try fglrx on Arch for a test. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#691494: Security vulnerabilities in RTFM
package: rt3.8-rtfm severity: critical tags: security pending From the RT mailing lists: We have determined a number of security vulnerabilities which affect both RT 3.8.x and RT 4.0.x. We are releasing RT versions 3.8.15 and 4.0.8, and RTFM version 2.4.5, to resolve these vulnerabilities, as well as patches which apply atop all released versions of 3.8 and 4.0. The vulnerabilities addressed by 3.8.15, 4.0.8, and the below patches include the following: All versions of RT are vulnerable to an email header injection attack. Users with ModifySelf or AdminUser can cause RT to add arbitrary headers or content to outgoing mail. Depending on the scrips that are configured, this may be be leveraged for information leakage or phishing. We have been assigned CVE-2012-4730 for this vulnerability; we would like to thank Scott MacVicar for bringing this matter to our attention. RT 4.0.0 and above and RTFM 2.0.0 and above contain a vulnerability due to lack of proper rights checking, allowing any privileged user to create Articles in any class. We have been assigned CVE-2012-4731 for this vulnerability. All versions of RT with cross-site-request forgery (CSRF) protection (RT 3.8.12 and above, RT 4.0.6 and above, and any instances running the security patches released 2012-05-22) contain a vulnerability which incorrectly allows though CSRF requests which toggle ticket bookmarks. We have been assigned CVE-2012-4732 for this vulnerability; we would like to thank Matthew Astley for bringing this to our attention. Additionally, all versions of RT are vulnerable to a confused deputy attack on the user. While not strictly a CSRF attack, users who are not logged in who are tricked into following a malicious link may, after supplying their credentials, be subject to an attack which leverages their credentials to modify arbitrary state. While users who were logged in would have observed the CSRF protection page, users who were not logged in receive no such warning due to the intervening login process. RT has been extended to notify users of pending actions during the login process. We have been assigned CVE-2012-4734 for this vulnerability; we would like to thank Matthew Astley for bringing this to our attention. RT 3.8.0 and above are susceptible to a number of vulnerabilities concerning improper signing or encryption of messages using GnuPG; if GnuPG is not enabled, none of the following affect you. We have been assigned CVE-2012-4735 for the following related vulnerabilities: * When using GnuPG, RT now clarifies the concepts of signing for _integrity_ and signing for _authentication_, which are separate (and exclusive) concepts. Previously, enabling the Sign by default queue configuration began signing automatically-generated messages with the queue's key, in addition to defaulting emails sent from the web UI to being signed. This provides integrity, but causes emails signed with that key to no longer possess authenticity; no individual email is guaranteed to have come from an actor designated to act for that key, in the case of automatically-generated emails. RT has now changed the Sign by default checkbox to merely provide a default in the web UI when composing messages; it no longer affects automatically-generated outgoing messages. Thus the Sign by default option helps to provide _authenticity_. A separate queue configuration option, Sign all auto-generated mail (defaulting to off) now controls the signing of automatically- generated emails, which (when used in combination with the previous option) helps provide _integrity_ of all outgoing messages. Users who had previously checked Sign by default and who wish to maintain the previous effect of integrity but not authenticity will need to enable the new option as well. We would like to thank Matthijs Melissen (University of Luxembourg) for bringing this matter to our attention. * RT 3.8.0 and above contain a vulnerability which allows incoming emails to force all triggered outgoing mail to be signed and/or encrypted. * RT 3.8.0 and above contain a vulnerability which allows incoming emails to incorrectly appear in the UI to have been encrypted when they had not been. This vulnerability only applies to encryption, not signing. * RT 3.8.0 and above contain a vulnerability which allows any user who is capable of sending signed email in the UI to do so using any secret key stored in RT's keyring. Additionally, RT 3.8.0 and above contain a vulnerability which allows a user to pass arbitrary arguments to the command-line GnuPG client, which could be leveraged to create arbitrary files on disk with the permissions of the webserver. This vulnerability only applies if GnuPG is enabled, and does _not_ allow for execution of programs other than the command-line GnuPG client. We have been assigned CVE-2012-4884 for this
Bug#592539: (isc-dhcp-server: supply additional initscript for IPv6 daemon): I'm using Florent Fourcot solution
Hi, just wanted to mention that I do run Florent Fourcot's solution[1] on the DHCP server in my dual-stack test network. While the load is nothing statistical relevant, the init.d script works fine for me. [1] http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=592539#22 I though suspect that Ron Murray's fix for multiple interfaces[2] likely should be applied, too, although I haven't tested it as I don't have that ( use | testing ) case (yet). [2] http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=592539#27 My setup includes three config files, one called dhcpd6.conf with the IPv6 only stuff and one called dhcpd.conf with the IPv4 only stuff (as with Florent), but I then have a third file with all the common stuff called dhcpd-common.conf. In both, dhcpd.conf and dhcpd6.conf, I have the line 'include /etc/dhcp/dhcpd-common.conf;' to avoid duplicated configuration items. Regards, Axel -- ,''`. | Axel Beckert a...@debian.org, http://people.debian.org/~abe/ : :' : | Debian Developer, ftp.ch.debian.org Admin `. `' | 1024D: F067 EA27 26B9 C3FC 1486 202E C09E 1D89 9593 0EDE `-| 4096R: 2517 B724 C5F6 CA99 5329 6E61 2FF9 CD59 6126 16B5 -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#688823: broadcom-sta-dkms: to version = 6.20.55.19 (r300276)
Hi Cyril, Thanks for replying On Fri, Oct 26, 2012 at 7:38 AM, Cyril Lacoux clac...@easter-eggs.com wrote: I think you should not do that because this driver doesn't seem to be only for this chipset but an enhanced version of the broadcom-sta driver which support recent chipsets (see attached diff, in particular wl_id_table declaration). Yes, I sure have noticed, because I wanted to update the readme file of original broadcom-wl when repacking a tarball. It's funny how even PCI_VENDOR_ID_BROADCOM was replaced with PCI_ANY_ID. I'll be pleased to upload the new version of the broadcom-sta driver when it's released (including i386 binary). Unfortunately, I doubt that will happen anytime soon, if at all. After failing to get any reply from broadcom linux-sta driver support, I contacted brcm80211 developers to ask if the linux-sta driver page could be updated with a tarball release of this driver, and an attempt to answer my request was simply: This driver version was a Dell-specific release, which they can redistribute. However, 5.100.82.112 on our internet page is our latest generic release. Anyway this can't be done before Wheezy release. Nods. I keep forgetting about the freeze period. Thanks a bunch. Cheers, -- Cyril Lacoux Cheers, Jasmine -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#592539: (isc-dhcp-server: supply additional initscript for IPv6 daemon): Yet another idea how to solve this issue
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Dear release team, I stumbled over this problem when we tried to setup a dualstacked isc-dhcp-server in wheezy. On 10/25/2012 06:03 PM, Andrew Pollock wrote: On Thu, Oct 25, 2012 at 10:13:14AM +0200, Jan Wagner wrote: On 08/15/2011 01:20 PM, Axel Beckert wrote: I ran into this today, too, so of course I would be happy, too, if one of the suggestions made in this bug report would make it into the Debian package. :-) [...] I though think that Florent Fourcot's solution is the most elegant one and will probably implement it on my Squeeze based DHCP servers. Andrew: Any idea if (or when) upstream will make DHCP for IPv4 and DHCPv6 work in the same instance of dhcpd? is there any reason for not implementing this? As the bug is 2 years old and the lifecycle of wheezy is actually planed ending anywhere in 2016, I'm asking me, if that is conflicting with the IPv6 release goal (which we have since Lenny). Looking into actual requirements in the field, it is needed to run DHCP-servers dualstacked for a long time, at least when wheezy will be released anytime. So ... what is the showstopper for this (in my opinion) legitim and reasonable request? Time mainly. If you can get an advance commitment from the release managers that such a change would be allowed into Wheezy given it's frozen, I'd be more inclined to try and make some time to make it happen now rather than later. As far as I know, Axel Beckert used the proposed fix successfully on squeeze. Could you please state, if you would accept such fix via t-p-u, if this was also fixed in unstable. This fix will enhance the IPv6-readyness in wheezy a lot, as in the next years the IPv6 rollout in corporate networks requires DHCPv6 in most cases (beside maybe parallel DHCPv4). Many thanks, Jan. - -- Never write mail to w...@spamfalle.info, you have been warned! - -BEGIN GEEK CODE BLOCK- Version: 3.12 GIT d-- s+: a C+++ UL P+ L+++ E--- W+++ N+++ o++ K++ w--- O M V- PS PE Y++ PGP++ t-- 5 X R tv- b+ DI D+ G++ e++ h r+++ y - --END GEEK CODE BLOCK-- -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.11 (GNU/Linux) iD8DBQFQim/s9u6Dud+QFyQRApsoAJ92lmIwsVbtO69e7RngDbMFLezOugCeK5Zf 6cGF1O4iZQT0xP4/NPa5vgY= =ZOTe -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#687307: Fwd: [php-maint] Updating php5 to 5.4.4-5 broke FastCGI setup on my machine
On Sat, Oct 6, 2012 at 9:51 PM, Stefan Fritsch s...@debian.org wrote: Hi Ondřej, I also cannot think of any configuration that would make everyone happy. At the moment, I fear this can only be solved by more documentation. Maybe one could add such a paragraph to the NEWS entry of php5-cgi 5.4.4-5, e.g. before The standard configuration now also... : WARNING: The new configuration may override other configuration directives you may have added locally for the .php extension, for example for FastCGI processing. This behavior is caused by FilesMatch configuration sections overriding directives appearing in global server or VirtualHost scope. You should review and test your configuration and verify that your php scripts work as expected. In the end I have used slightly different text with a warning to check the existing setup foo.php.jpeg vulnerability. Improvements welcome (as a patch, not as a rant). + The new (dummy) php5_cgi configuration uses SetHandler directive and + thus it might interfere with your existing custom configuration like + FastCGI (mod_fcgid or mod_fastcgi). In that case please disable + php5_cgi module (a2dismod php5_cgi) to reenable the existing + functionality of your custom configuration. It is also advised that + you check your custom configuration whether it's not vulnerable to + foo.php.jpeg attacks. The php5_cgi configuration snippet can be used + as base - it's important to use FilesMatch or Files directive to + limit the handling to the last extension. I think it became clear that we are stuck with no solution which would work for anyone, so this is the minimal variant of what we should do in PHP package. If somebody comes with better solution (or just tests the non-magic mime-types as written down by sf in http://wiki.debian.org/Apache/WheezyMimeTypes), I think we can still change that before release. But now we at least need more test in php5-cgi.NEWS. O. -- Ondřej Surý ond...@sury.org -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#528057: Please create server package for prboom
the first thing I've noticed is that, by default, prboom-game-server links against the SDL libraries. This might simply be a result of the way it is built at present, rather than a requirement, however. I can confirm this. The prboom-game-server binary is linked against libSDL_net-1.2, which in turn is linked against libSDL-1.2. The latter will pull in libX11 and the sound output libraries, anyway. So, the only direct dependencies that would be saved by a dedicated prboom-server package would be libgl1-mesa-glx | libgl1, libglu1-mesa | libglu1, libpng12-0, libsdl-mixer1.2. I am not sure if this is a real win. - Fabian -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#691495: tuxmath: no. of players for Play with Friends
Package: tuxmath Version: 1.8.0-4 Severity: minor Tags: patch On clicking, TuxMath → Play with Friends → Score Sweep. Select any game from the list. It shows, How many kids are playing?(Between 2 and 4 players). Expected Result: It should accept only numbers between 2 and 4. Actual Result: It accepts 1 also. This issue is resolved and the patch for the same is attached. -- Regards, Prathibha BOSS Team C-DAC Chennai 01_boss_players_patch Description: Binary data
Bug#579749: prboom: Screenshots in png?
PrBoom supports PNG screenshots on Linux since version 2.4.1 (and in GL mode since 2.4.5), provided it is built against libpng, otherwise output is in the BMP file format. For architectures other than ia64 on Squeeze, prboom is not built against libpng. The version currently available in unstable does write PNG screenshots. I can confirm that prboom is built with support for PNG screenshots and that it saves in this format by default. Regarding the build, libpng12-dev is currently pulled in by libdirectfb-dev, which is in turn pulled in by libsdl1.2-dev. I admit that's a rather fragile chain, so maybe libpng-dev should be added as an explicit Build-Depends. - Fabian -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#528057: Please create server package for prboom
Am 26.10.2012 13:28, schrieb Fabian Greffrath:
So, the only direct dependencies that would be saved by a dedicated
prboom-server package would be libgl1-mesa-glx | libgl1, libglu1-mesa
| libglu1, libpng12-0, libsdl-mixer1.2. I am not sure if this is a
real win.
The net library win:
$ diff -u (ldd src/prboom | sort | awk '{print $1}') (ldd
src/prboom-game-server | sort | awk '{print $1}')
--- /dev/fd/63 2012-10-26 13:40:43.168675996 +0200
+++ /dev/fd/62 2012-10-26 13:40:43.168675996 +0200
@@ -8,23 +8,15 @@
libdirect-1.2.so.9
libdirectfb-1.2.so.9
libdl.so.2
-libdrm.so.2
libFLAC.so.8
libfusion-1.2.so.9
-libgcc_s.so.1
-libglapi.so.0
-libGL.so.1
-libGLU.so.1
libICE.so.6
libjson.so.0
/lib/ld-linux.so.2
-libmad.so.0
-libmikmod.so.2
libm.so.6
libncursesw.so.5
libnsl.so.1
libogg.so.0
-libpng12.so.0
libpthread.so.0
libpulsecommon-2.1.so
libpulse-simple.so.0
@@ -32,30 +24,23 @@
libresolv.so.2
librt.so.1
libSDL-1.2.so.0
-libSDL_mixer-1.2.so.0
libSDL_net-1.2.so.0
libslang.so.2
libSM.so.6
libsndfile.so.1
-libstdc++.so.6
libtinfo.so.5
libts-0.0.so.0
libuuid.so.1
libvorbisenc.so.2
-libvorbisfile.so.3
libvorbis.so.0
libwrap.so.0
libX11.so.6
libX11-xcb.so.1
libXau.so.6
-libxcb-glx.so.0
libxcb.so.1
-libXdamage.so.1
libXdmcp.so.6
libXext.so.6
-libXfixes.so.3
libXi.so.6
libXtst.so.6
-libXxf86vm.so.1
libz.so.1
linux-gate.so.1
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#679362: ITP: pgbadger
retitle #679362 ITP: pgbadger -- a fast PostgreSQL log analysis report owner #679362! thanks I am willing to package and maintain it, but I still need a sponsor. I'll try at debian mentors and perhaps the perl team, but if anyone wants to sponsor the package please contact me. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#690814: [3.1-3.2.y regression] disk activity provokes lockups on VIA EPIA CL-6000
--- On Thu, 10/25/12, Jonathan Nieder jrnie...@gmail.com wrote: From: Jonathan Nieder jrnie...@gmail.com Subject: Re: [3.1-3.2.y regression] disk activity provokes lockups on VIA EPIA CL-6000 To: Frank Lenaerts frank.lenae...@yahoo.com Cc: 690...@bugs.debian.org Date: Thursday, October 25, 2012, 10:41 PM Jonathan Nieder wrote: Package names like linux-image-3.2.0-1-486 describe the kernel's ABI, not the package version. The package version is something like 3.2.1-1. See http://kernel-handbook.alioth.debian.org/ch-versions.html for more details. You can get the version of the currently running kernel by running cat /proc/version (it will be in parentheses). The currently installed kernel's version number can be retrieved with dpkg-query -W linux-image-$(uname -r). Which versions were the 3.2.0-1, 3.2.0-2, and 3.2.0-3 kernels you mentioned testing above? I mean 3.1.0-1, 3.2.0-1, 3.2.0-3 here. Sorry for the lack of clarity. I just used uname -r and left out '-486' (because that's always the same on this box).
Bug#691427: journal commit I/O error on brand-new Thinkpad T430s ext4 on lvm on SSD
Hi Jonathan, Le jeudi, 25 octobre 2012 22.25:03, Jonathan Nieder a écrit : Didier Raboud wrote: Tags: upstream What upstream version did you test? Well we only tried packaged kernels, all wheezy, unstable and experimental exhibit this behaviour. We started to compile an upstream kernel but didn't try yet. I tagged this bug as upstream, considering it's probably not a bug of the packaging. Can you get full dmesg output when in this state? A serial console[1] or netconsole[2] might be helpful in obtaining that, or if that's not possible, a photograph of messages on the screen will do in a pinch. I'll let Dorian send that to the bug, we'll see what that gives. Cheers, OdyX -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#691496: tuxmath: desktop menu entry in other languages
Package: tuxmath Version: 1.8.0-4 Severity: minor Tags: patch I have added the Name, Generic Name and Comment in Hindi, Tamil and Punjabi for the menu entry. The patch for the same is attached. -- Regards, Prathibha BOSS Team C-DAC Chennai 02_boss_desktop_patch Description: Binary data
Bug#680084: postinst script gets stuck
tags 680084 + patch thanks intrigeri wrote (30 Sep 2012 09:42:14 GMT) : I can see that too with os-prober installed. TL;DR --- see patch at the bottom of this message. I retried, and I did not see that *the first time*. First time log: $ pgrep -l grub-mount $ sudo update-grub Generating grub.cfg ... Found linux image: /boot/vmlinuz-3.2.0-4-amd64 Found initrd image: /boot/initrd.img-3.2.0-4-amd64 Found memtest86+ image: /memtest86+.bin Found memtest86+ multiboot image: /memtest86+_multiboot.bin grub-probe: error: no such disk. done $ pgrep -l grub-mount 1468 grub-mount Second time in a row log: $ pgrep -l grub-mount 1468 grub-mount $ sudo update-grub Generating grub.cfg ... Found linux image: /boot/vmlinuz-3.2.0-4-amd64 Found initrd image: /boot/initrd.img-3.2.0-4-amd64 Found memtest86+ image: /memtest86+.bin Found memtest86+ multiboot image: /memtest86+_multiboot.bin rmdir: failed to remove `/var/lib/os-prober/mount': Device or resource busy rmdir: failed to remove `/var/lib/os-prober/mount': Device or resource busy grub-probe: error: no such disk. done $ sudo mountpoint /var/lib/os-prober/mount /var/lib/os-prober/mount is not a mountpoint $ pgrep -l grub-mount 1468 grub-mount 2217 grub-mount I see that /usr/bin/os-prober starts by running /usr/lib/os-prober/newns, so perhaps the dangling mounts that make the device busy can not be seen in the default namespace. Let's test with os-prober only. $ pgrep -l grub-mount $ sudo os-prober fuse: warning: library too old, some operations may not not work error: unknown filesystem. mount: unknown filesystem type 'linux_raid_member' fuse: warning: library too old, some operations may not not work grub-probe: error: no such disk. $ pgrep -l grub-mount 6752 grub-mount $ sudo os-prober fuse: warning: library too old, some operations may not not work rmdir: failed to remove `/var/lib/os-prober/mount': Device or resource busy error: unknown filesystem. mount: unknown filesystem type 'linux_raid_member' rmdir: failed to remove `/var/lib/os-prober/mount': Device or resource busy fuse: warning: library too old, some operations may not not work grub-probe: error: no such disk. $ pgrep -l grub-mount 6752 grub-mount 7259 grub-mount Additional information: The LVM logical volume that is left mounted by os-prober / grub-mount after the first run is not listed in /etc/fstab. If I entirely zero that LV, then update-grub works flawlessly twice in a row, and does not leave dangling grub-mount processes around. This LV contains a vfat filesystem, that I can perfectly well mount and umount with mount(8) and umount(8). Trying to grub-mount it manually: $ sudo grub-mount /dev/mapper/$VGNAME-$LVNAME /mnt/tmp fuse: warning: library too old, some operations may not not work = a detached process with the same command-line is left running. $ sudo grub-probe -d /dev/mapper/$VGNAME-$LVNAME -t fs grub-probe: error: cannot find a GRUB drive for /dev/$VGNAME/$LVNAME. Check your device.map. zsh: exit 1 what does /dev/mapper/vgwhatever actually point to? It points to ../dm-5, just like /dev/$VGNAME/$LVNAME. I've run os-prober with set -x + echo to debug further. It appears that the following patch is needed to deal with the fact grub-probe returns a non-zero exit code on that device: --- /home/intrigeri/tmp/50mounted-tests.orig 2012-09-17 17:08:12.0 +0200 +++ /usr/lib/os-probes/50mounted-tests2012-10-26 12:40:34.660238265 +0200 @@ -50,7 +50,7 @@ type grub-probe /dev/null 21 \ grub-mount $partition $tmpmnt 2/dev/null; then mounted=1 - type=$(grub-probe -d $partition -t fs) + type=$(grub-probe -d $partition -t fs) || true if [ $type ]; then debug mounted using GRUB $type filesystem driver else ... else, this script exits, umount is never run, and a dangling grub-mount process is left behind. Cheers! -- intrigeri -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#691406: some KDE programs take very long to start
Control: severity -1 wishlist Control: retitle -1 kde-standard: KDE should issue warning if connection to localhost fails Hi, On 10/25/2012 08:23 PM, Lisandro Damián Nicanor Pérez Meyer wrote: On Thu 25 Oct 2012 09:00:18 Stephan Beyer escribió: [snip] Should the bug be reassigned to debian-installer or ifupdown? As long as you have the installations logs still available, you can reassign it to the instaler. If you don't, you need to reproduce the bug and get the log. I still have the logs in /var/log/installer but they won't help much. I think, when the (known) /etc/network/interfaces bugs are fixed, the loopback interface will always come up well and then KDE just works. However, the question is still open if KDE programs should handle the oh, there was a timeout when connecting to 127.0.0.1! case differently, like, for example, issuing a warning message telling the user that 127.0.0.1 is not reachable and therefore KDE is not guaranteed to work correctly. I think this is kind of a wishlist bug now (see BTS control lines). Perhaps reissuing as a whislist bug would have been cleaner, but now the reason should become more clear. I am sorry if I am doing anything wrong ;-) Best Stephan -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#688266: pu: package policyd-weight/0.1.15.1-2+squeeze1
Hi Adam, just a short question - what about the policyd-weight package in backports? regards, Werner Am 22.09.12 21:19, schrieb Adam D. Barratt: Control: tags -1 + pending On Thu, 2012-09-20 at 23:08 +0100, Adam D. Barratt wrote: On Fri, 2012-09-21 at 00:01 +0200, Werner Detter wrote: Thanks for the quick response. That looks better, but... :-) You're right. Seems like I really need some more coffee :) Thank you. I've downloaded the current source package again and added my patches from scratch. I hope it's OK now :) That looks fine; thanks. Please feel free to go ahead with the upload, bearing in mind that the acceptance window for the next point release closes over the weekend. For the record, this was uploaded and I've flagged it for acceptance in to p-u; thanks. Regards, Adam -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#688069: liblocale-subcountry-perl: Version checks fail (our $VERSION moved before package Locale::SubCountry)
On Fri, 26 Oct 2012 02:20:24 -0700, Ivan Kohler wrote: The patch below adds a package Locale::SubCountry to the beginning of the code. This seems like typical / best practice for modules, to avoid any symbol exports from the intial use statements from polluting the main:: namespace. Are you going to upload the fixed package? Or should someone else go ahead? Since wheezy isn't affected (or released) and upstream hasn't yet responded/updated, I guess I was more in a holding pattern over here with regard to this. Ah, I missed that wheezy isn't affected; good :) Cheers, gregor -- .''`. Homepage: http://info.comodo.priv.at/ - OpenPGP key 0xBB3A68018649AA06 : :' : Debian GNU/Linux user, admin, and developer - http://www.debian.org/ `. `' Member of VIBE!AT SPI, fellow of the Free Software Foundation Europe `- NP: Tom Waits: Metropolitan Glide signature.asc Description: Digital signature
Bug#688266: pu: package policyd-weight/0.1.15.1-2+squeeze1
On 26.10.2012 12:51, Werner Detter wrote: just a short question - what about the policyd-weight package in backports? Sorry, I'm not sure what the question is here. If you're trying to get the package on backports.debian.org updated, I believe the usual approach is to contact whoever performed the previous backport. In any case, the release team don't manage backports.d.o. Regards, Adam -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#691497: ITP: ruby-orm-adapter -- single point of entry for using basic features of ruby ORMs
package: wnpp severity: wishlist owner: Praveen Arimbrathodiyil prav...@debian.org * Package Name: orm_adapter * Version: 0.4.0 * Upstream Author: Ian White and José Valim * URL: https://github.com/ianwhite/orm_adapter * License: MIT/Expat * Description: single point of entry for using basic features of ruby ORMs orm_adapter provides a single point of entry for using basic features of popular ruby ORMs. Its target audience is gem authors who want to support many ruby ORMs. It is a dependency for devise. -- പ്രവീണ് അരിമ്പ്രത്തൊടിയില് You have to keep reminding your government that you don't get your rights from them; you give them permission to rule, only so long as they follow the rules: laws and constitution. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#691498: gdm3/experimental: document that ~/.xsession-errors is no longer used
Package: gdm3 Version: 3.6.1-1 Severity: wishlist From NEWS: = Version 3.5.2 = ... - save log to $XDG_CACHE_HOME/gdm/session.log instead of ~/.xsession-errors This is a good thing in the long term - I approve of reducing crap in $HOME - but it's going to confuse people who're debugging GNOME 3.6 or other X apps, particularly those that are part of the session and so can't easily be restarted with stderr visible (gnome-shell, gnome-session, gnome-settings-daemon etc.). I've been tricked by it already. I'm not sure what the best solution is, though. Options include: * say something in NEWS.Debian * on session start, if ~/.xsession-errors exists and is a regular file, replace it with text like Session started by GDM, see ~/.cache/gdm/session.log (I think this is probably the one that will interoperate best with startx and other display managers, since they'll overwrite .xsession-errors with their own session logs on login, as expected - so it'll always contain either a non-GDM session log, or a pointer to the GDM log) * on session start, if ~/.xsession-errors exists and is a regular file, replace it with a symlink to ~/.cache/gdm/session.log (this interops poorly with other display managers, but might be better for bug-reporting tools that know about ~/.xsession-errors) * log to ~/.xsession-errors if it exists, or ~/.cache/gdm/session.log in new installations * agree on a session log location in $XDG_CACHE_HOME with the maintainers of x11-common, and patch both x11-common and gdm3 to be consistent -- System Information: Debian Release: wheezy/sid APT prefers testing-proposed-updates APT policy: (500, 'testing-proposed-updates'), (500, 'unstable'), (500, 'testing'), (500, 'stable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.2.0-4-amd64 (SMP w/4 CPU cores) Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages gdm3 depends on: ii accountsservice 0.6.24-1 ii adduser 3.113+nmu3 ii dconf-gsettings-backend 0.14.0-1 ii dconf-tools 0.14.0-1 ii debconf [debconf-2.0] 1.5.46 ii dpkg1.16.9 ii gir1.2-glib-2.0 1.34.1.1-1 ii gnome-session [x-session-manager] 3.6.0-1 ii gnome-session-bin 3.6.0-1 ii gnome-session-fallback [x-session-manager] 3.6.0-1 ii gnome-settings-daemon 3.6.1-1 ii gnome-terminal [x-terminal-emulator]3.4.1.1-2 ii gsettings-desktop-schemas 3.6.0-1 ii libaccountsservice0 0.6.24-1 ii libatk1.0-0 2.6.0-1 ii libaudit0 1:1.7.18-1.1 ii libc6 2.13-35 ii libcairo-gobject2 1.12.2-2 ii libcairo2 1.12.2-2 ii libcanberra-gtk3-0 0.28-5 ii libcanberra00.28-5 ii libfontconfig1 2.9.0-7 ii libgdk-pixbuf2.0-0 2.26.4-2 ii libglib2.0-02.34.1-1 ii libglib2.0-bin 2.34.1-1 ii libgtk-3-0 3.6.1-1 ii libpam-modules 1.1.3-7.1 ii libpam-runtime 1.1.3-7.1 ii libpam0g1.1.3-7.1 ii libpango1.0-0 1.30.0-1 ii librsvg2-common 2.36.4-1 ii libselinux1 2.1.9-5 ii libupower-glib1 0.9.17-1 ii libwrap07.6.q-24 ii libx11-62:1.5.0-1 ii libxau6 1:1.0.7-1 ii libxdmcp6 1:1.1.1-1 ii libxrandr2 2:1.3.2-2 ii lsb-base4.1+Debian7 ii metacity [x-window-manager] 1:2.34.3-3 ii mutter [x-window-manager] 3.6.1-1 ii openbox [x-window-manager] 3.5.0-4 ii policykit-1-gnome 0.105-2 ii upower 0.9.17-1 ii x11-common 1:7.7+1 ii x11-xserver-utils 7.7~3 ii xterm [x-terminal-emulator] 278-2 Versions of packages gdm3 recommends: ii at-spi2-core 2.7.1-1 ii desktop-base 7.0.3 ii gnome-icon-theme 3.6.0-1 ii gnome-icon-theme-symbolic 3.6.0-1 ii x11-xkb-utils 7.7~1 ii xserver-xephyr 2:1.12.4-1 ii
Bug#612659:
Some news about the inclusion of din in official Debian repositories?
Bug#576511: drbd8-utils: Ships with violent default actions
Control: severity -1 critical On Tue, Oct 23, 2012 at 11:40:43AM -0400, Michael Gilbert wrote: control: severity -1 important These defaults are really bad. I understand your concern, but you should not override the maintainer's opinion on bug severities. These are upstream defaults I believe, so the settings are really their call, and to get them changed you'll need to discuss the matter with them. Sorry, what? No, they're not upstream defaults; I've literally copied and pasted the upstream's user guide that explicitly says otherwise, in the other message. Besides, we're not beholden to whatever upstream thinks; this package is causing unrelated data loss to the rest of the system in this case; it must not do that. http://www.debian.org/Bugs/Developer#severities critical [...] makes unrelated software on the system (or the whole system) break, or causes serious data loss [...] grave [...] causes data loss [...] I've even been generous the last time around, this is actually a critical bug. -- 2. That which causes joy or happiness. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#688772: gnome Depends network-manager-gnome
On Thursday, October 25, 2012 18:27:58, Michael Biebl wrote: On 25.10.2012 22:47, Andreas Barth wrote: * Jeremy Bicha (jbi...@ubuntu.com) [121025 18:51]: On 25 October 2012 12:17, Don Armstrong d...@debian.org wrote: That said, if I'm wrong, and you believe that there is a compromise which would resolve the concerns raised beyond those already presented (status quo with/without release notes), now would be the time to present it. My proposal is to: 1. Add a paragraph to the Release Notes with the one line command people should use if they don't want NetworkManager running: update-rc.d disable network-manager 2. And cases where that doesn't work are RC. How would that prevent startup of n-m during upgrades from stable to next-stable? (Which could already present issues, especially if the system is remote managed) I've been discussing with jordi today about this issue. One idea that came up was to check wether wicd is in use (or for that matter ifupdown), and then show a debconf prompt explaining the situation, and letting the user chose if he wants to take over network management by NetworkManager. It would work similar to how we currently handle multiple installed display managers, like gdm3 or kdm (btw, gdm3 is currently a hard depends of gnome-core). If the users choses no, we could disable the service via update-rc.d disable, so the invoke-rc.d later on in postinst would not start NM. This would also help in situations where users install both wicd and network-manager by accident, which usually doesn't really work well since e.g. both spawn their own instance of wpa_supplicant. A more detailed reply will follow soon. This is a good suggestion, and one which I think would work around all of the breakage concerns I raised on this issue. Thank you for putting in the effort for coming up with this option. A tweak I'd suggest considering would be to reverse the logic of the test of when to show the debconf prompt -- because there are several possible tools for setting up networking like iwconfig, manually using wpa_supplicant, commands in rc.local, etc, such that trying to test for all of the specific situations of when to show the option might be frustrating to track down competely. What we /do/ know is that there are two known situations where the user does /not/ need to see the choice to disable N-M, which is A) when N-M is already installed and running, or B) when N-M is installed but disabled via update-rc.d I think this effectively reduces down to checking if N-M is already installed and prompting if it's not. Well, unless you also want to test if it's running to take into consideration the possibility that N-M could be locally installed outside of package management, in which also installing N-M as a package would be... weird. ;-) The last thing I'm wondering about are the concerns from the Gnome team about whether empathy or evolution would know if you're online -- which in this case means if they do if N-M is installed but not running. If they do then this solution would have that as an advantage. If it doesn't then (at least on the surface) this solution seems similar to N-M being a Recommends in the meta- gnome package such that it doesn't have to be installed. [I'm not bringing this up as an argument against choosing this solution because I think the solution would work, but rather I'm trying to objectively evaluate what the effect this solution would have and how it compares to other possibilities.] Thanks again. -- Chris -- Chris Knadle chris.kna...@coredump.us signature.asc Description: This is a digitally signed message part.
Bug#691499: unblock: tor/0.2.3.24-rc-1
Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: freeze-exception Please unblock package tor. unblock tor/0.2.3.24-rc-1 Version 0.2.3.24-rc fixes two security issues over the version currently in testing, 0.2.3.22-rc. These issues have been assigned CVE-2012-2249 and CVE-2012-2250. Debian changelogs: | tor (0.2.3.24-rc-1) unstable; urgency=high | | * New upstream version: | - Fix a group of remotely triggerable assertion failures related to | incorrect link protocol negotiation. Found, diagnosed, and fixed | by some guy from France. Fix for CVE-2012-2250; bugfix on | 0.2.3.6-alpha. | - Fix a denial of service attack by which any directory authority | could crash all the others, or by which a single v2 directory | authority could crash everybody downloading v2 directory | information. Fixes bug 7191; bugfix on 0.2.0.10-alpha. | - and more. | | -- Peter Palfrader wea...@debian.org Fri, 26 Oct 2012 09:15:09 +0200 | | tor (0.2.3.23-rc-1) unstable; urgency=low | | * New upstream version: | o Major bugfixes (security/privacy): | - Disable TLS session tickets. OpenSSL's implementation was giving | our TLS session keys the lifetime of our TLS context objects, when | perfect forward secrecy would want us to discard anything that | could decrypt a link connection as soon as the link connection | was closed. Fixes bug 7139; bugfix on all versions of Tor linked | against OpenSSL 1.0.0 or later. Found by Florent DaigniÚre. | - Discard extraneous renegotiation attempts once the V3 link | protocol has been initiated. Failure to do so left us open to | a remotely triggerable assertion failure. Fixes CVE-2012-2249; | bugfix on 0.2.3.6-alpha. Reported by some guy from France. | - Fix a possible crash bug when checking for deactivated circuits | in connection_or_flush_from_first_active_circuit(). Fixes bug 6341; | bugfix on 0.2.2.7-alpha. Bug report and fix received pseudonymously. | For other fixes please see the upstream changelog. | | -- Peter Palfrader wea...@debian.org Sat, 20 Oct 2012 22:27:04 +0200 Full upstream changelog at https://gitweb.torproject.org/tor.git/blob/release-0.2.3:/ChangeLog I can prepare full diffs on request. Cheers, weasel -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#576511: drbd8-utils: Ships with violent default actions
On Wed, Oct 24, 2012 at 04:29:47PM +0200, Philipp Hug wrote: It should probably be changed into something like this: /usr/lib/drbd/notify-emergency-reboot.sh; reboot -f ; sync ; sleep 30; echo b /proc/sysrq-trigger; So, we'd have at least time to sync other file systems and try to shutdown as many services as possible. b) [you might] not be able to remotely reboot the machine due to blocked processes Actually, I think a general sync wasn't previously added in that situation because it might cause a problem with the filesystem on the faulty DRBD device itself, thereby causing the problem b) you described. IOW you want to try to sync filesystems only on the unaffected block devices, but there's no such granularity in this DRBD facility or in sync(1). these are the default upstream defaults. Where did you see this upstream, is this file shipped by them as such or? Because, again, it contradicts all of their documentation I could find. -- 2. That which causes joy or happiness. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#680978: gnome-shell-extensions package fails to require the unzip package
reassign 680978 gnome-shell retitle 680978 gnome-shell: installing from extensions.gnome.org requires unzip found 680978 3.4.2-2 found 680978 3.6.1-3 thanks On Mon, 09 Jul 2012 at 13:33:15 -0400, Al Grimstad wrote: Many users have struggled with trying to down load extensions from extensions.gnome.org. Typically they selected an extension but it failed to download. This problem was traced to their system's lacking unzip. gnome-shell-extensions is just a collection of specific extensions, so this is more of a bug in (the packaging of) gnome-shell itself. Reassigning there. unzip isn't strictly necessary to use gnome-shell, so it should perhaps just be a Recommends (which are installed by default anyway). S -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#691366: wheezy 2012-10-24 daily built netinst
On Fri, Oct 26, 2012 at 11:15:31AM +0200, Stephan Beyer wrote: On 10/26/2012 12:11 AM, Philipp Kern wrote: And the error message is: /etc/network/interfaces:15: misplaced option ifup: couldn't read interfaces file /etc/network/interfaces Looks pretty dangerous. However, as mentioned, everything worked though. (In the meantime I commented out the privext 2 line and the error message vanished.) Added to the errata[1], thanks. Not quite correct. I had the same effect in my first installation (GNOME) *and* in my second installation (KDE). Hopefully corrected now: Index: errata.wml === RCS file: /cvs/webwml/webwml/english/devel/debian-installer/errata.wml,v retrieving revision 1.173 retrieving revision 1.174 diff -r1.173 -r1.174 31c31 dtNetwork apparently failing to come up post-install when installing the GNOME desktop environment./dt --- dtNetwork apparently failing to come up post-install when installing a desktop environment./dt 38,41c38,41 is selected, you need to comment out privext 2 in /etc/network/interface post-install to silence warnings emitted by ifupdown during the boot process. The network will still be set up correctly by network-manager. --- or KDE desktop environment is selected, you need to comment out privext 2 in /etc/network/interface post-install to silence warnings emitted by ifupdown during the boot process. The network will still be set up correctly by network-manager. Kind regards Philipp Kern signature.asc Description: Digital signature
Bug#691500: dasher: Spaces at the end of training files
Source: dasher Severity: important Some language files, notably German, have spaces at the end of each and every paragraph in the training text. Please remove them; they severely skew the character distributions and make entering a linefeed after any character that's not a space virtually impossible. The German text also contains embedded links: Die haarsträubende [2]Verschwörungsbastelanweisung That also doesn't make much sense in this context. -- System Information: Debian Release: wheezy/sid APT prefers testing APT policy: (700, 'testing'), (650, 'unstable'), (600, 'stable'), (550, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.2.0-3-amd64 (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 -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#691501: fusionforge-plugin-oslc: Call to undefined function createRessourceCollectionView()
Package: fusionforge-plugin-oslc Version: 5.2-1 Severity: normal Tags: upstream Hi. Accessing URLs like https://fusionforge.org/plugins/oslc/cm/project/6/tracker/105 spit out : FusionForge Change Requests: Fatal error: Call to undefined function createRessourceCollectionView() in /usr/share/gforge/plugins/oslc/include/oslc-zend/application/views/scripts/fusionforgecm/read-resource-collection.phtml on line 43 Thanks in advance. Best regards, -- System Information: Debian Release: wheezy/sid APT prefers testing APT policy: (900, 'testing') Architecture: i386 (i686) Kernel: Linux 3.2.0-3-686-pae (SMP w/2 CPU cores) Locale: LANG=fr_FR.utf8, LC_CTYPE=fr_FR.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#688932: g_get_user_{cache, config, data}_dir () fail to meet XDG Base Directory Specification
Le vendredi 26 octobre 2012 à 16:51 +0700, Ivan Shmakov a écrit :
As per XDG Base Directory Specification 0.8 (quoted below), the
default values for XDG_CACHE_HOME, XDG_CONFIG_HOME, and
XDG_DATA_HOME, are both defined relative to the value of the
HOME environment variable. Contrary to that, the respective
g_get_user_{cache,config,data}_dir () functions return values
relative to the user's /initial/ home directory (as per
getpwuid ()-pw_dir) by default instead.
Please discuss this with upstream. There is no way we will diverge on
such an important API compatibility matter.
Cheers,
--
.''`. Josselin Mouette
: :' :
`. `'
`-
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#691366: wheezy 2012-10-24 daily built netinst
Hi, On 10/26/2012 02:23 PM, Philipp Kern wrote: Hopefully corrected now: Correct. However I wonder if it should also be mentioned that the lo interface (for 127.0.0.1) does not come up, too, which leads to interesting effects like the one mentioned in bug #691406 [1]. 1. http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=691406 Best Stephan -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#691389: [checkbashisms] multiple bug fixes and new checks
Am Donnerstag, den 25.10.2012, 17:33 -0500 schrieb Raphael Geissert: Hi, On Thursday 25 October 2012 16:44:03 Benjamin Drung wrote: Am Mittwoch, den 24.10.2012, 21:15 -0500 schrieb Raphael Geissert: Attached is an mbox with a bunch of bug fixes and new checks, #687450 included. Thanks. I have applied your patches 1 up to 14. I grabbed the working test cases from your git repository and added them to devscripts. After applying a patch, I added the newly passing test cases. Feel free to add more test cases to devscripts or to improve/simplify the shunit2 tests. Thanks. For now I'm going to continue using my test suite, it: has more test cases, allows TODO items, and allows two versions of checkbashisms to be compared. I like the output-comparison approach of the shunit-based suite, but it is annoying to use while developing. I would like to see a movement of the passed test cases from your test suite to the shunit2 test suite. The current situation is that 38 files are moved to shunit2 and 25 files remain in your test suite. The output comparison in shunit2 could be improved. It could print a diff -u output instead of just printing the expected and the actual output. Patch 15 refers to commit 5dc48224, but the commit hashes do not survive git format-patch git am. To which commit do you refer? Patch 15 refers to patch 14. Thanks. I have applied the remaining patches. (the commit hash _is_ included in the git format-patch output.) Evolution stripped the first From line from the patches when I saved them. The commit hash is included in the mbox. Please do not sign off your own patches. Your patches will be signed off by the person that applies your patches. Perhaps we differ on what the sign off means, and that shouldn't cause any issue for another person to sign off them as well. I found two meaning of signing off patches: 1) The signer certifies that he/she have created the patch in question and take responsibility for the copyright status of the code in question. 2) The signer reviewed the patch and has done some sort of QA. We use the second meaning. You can send your patches directly to the mailing list if have more than one instead of opening a new bug report. Can you add a commit with your changelog entries? Since doing that oftentimes leads to merge conflicts it is easier if the committer adds it after merging, and on whatever branch those changes are merged. Since you provided a big bunch of patches, I ask for one patch that adds all the changelog entries. On IRC I mentioned a regression when checking autoconf, but the issue is now visible thanks to some bug fixes. In one configure script the bug fix actually revealed a bashism. Have you created a test case for this regression? Not per se, I've only copied autoconf(1) to my test suite. It all comes down to fixing the parsing of things like printf '#!/bin/sh\nbar=moo; foo=foo \bar\ ... \nmoo\n' And this (which is what actually triggers the 'error' in the autoconf case): checkbashisms 'EOF' case foo in *\'*) arg=`$as_echo $1 | sed s/'/'''/g` ;; #' esac EOF (this actually made me notice that the error messages aren't displaying '(stdin)', so attache patch fixes that.) I applied that patch too. Attached the stripped down test case for the regression (should pass without output). -- Benjamin Drung Debian Ubuntu Developer commented-quote.sh Description: application/shellscript
Bug#691502: RFP: trace-cmd -- Utility for retrieving and analyzing function tracing in the kernel
Package: wnpp Severity: wishlist * Package name: trace-cmd Version : 2.0.1 Upstream Author : Steven Rostedt rost...@goodmis.org * URL : git://git.kernel.org/pub/scm/linux/kernel/git/rostedt/trace-cmd.git * License : GPL-2 Programming Lang: C, Python Description : Utility for retrieving and analyzing function tracing in the kernel This package contains the trace-cmd utility. Trace-cmd makes it easy to retrieve and analyze function traces from the Linux kernel while it is running. -- Note: Currently Eric Y. Miao is trying to packaging this. git://github.com/ycmiao/trace-cmd PPA: ppa:eric.y.miao/testing -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#691396: [Pkg-ime-devel] Bug#691396: Bug#691396: ibus-anthy: Engine fails to start
On Thu, Oct 25, 2012 at 07:19:26PM -0500, Ma Xiaojun wrote: On 10/25/12 1:18 AM, Marcus Lundblad wrote: Trying to use ibus-anthy with gnome-shell 3.6.1 in experimental. I add a Japanese keyboard layout using anthy. Things don't work. After some digging around, I found that the file /usr/share/ibus-anthy/engine/_config.py contains invalid paths. These paths (PKGDATADIR, LIBEXECDIR, and LOCALEDIR) starts with /usr/share Thus, python won't find the modules defined by the engine. Manually changing these paths to have a prefix of /usr/ actually makes it work. I can now type in text with the Japanese input method (and also the input method options appears in gnome-shell's keyboard menu in the top bar). Did you notice similar issue in the upstream tracker? http://code.google.com/p/ibus/issues/detail?id=1513 I guess the upstream developer assume that you are using /usr I think non /usr prefix should be supported so I kept the upstream issue open. However, this issue is not a high priority issue at least for me personally. Well, this is experimental and Ubuntu, so I am not well educated. All I can say is each distribution has focus. * Debian to impliment multi-arch * Fedora uses /libexec and moves /bin to /usr/bin So if you repackage a package, we need to make proper adjustment to autotool parameters while building a package. /libexec - /lib/packagename/ Is one I need tio do all the time... osamu -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#690683: lgeneral: Unusable due to missing game data converter and outdated
tags 690683 patch thanks My new package is available at mentors.debian.net http://mentors.debian.net/package/lgeneral and in Git at http://git.debian.org/pkg-games/lgeneral.git I know new upstream releases are discouraged during the freeze but given the nature of this bug, it is the only reasonable solution. signature.asc Description: Digital signature
Bug#691451: lgeneral: ships non-free files in contrib
tags 691451 patch thanks My new package is available at mentors.debian.net http://mentors.debian.net/package/lgeneral and in Git at http://git.debian.org/pkg-games/lgeneral.git Please see also bug #690683. signature.asc Description: Digital signature
Bug#691452: lgc-pg: ships non-free files in contrib
tags 691452 patch thanks My new package is available at mentors.debian.net http://mentors.debian.net/package/lgeneral and in Git at http://git.debian.org/pkg-games/lgeneral.git Please see also bug #690683 and #691451. It is sufficient to replace the aforementioned files with the ones shipped with the latest version of lgeneral in Git or at mentors.debian.net. signature.asc Description: Digital signature
Bug#691503: gnucash: /usr/lib/i386-linux-gnu/gnucash/overrides/gnucash-make-guids cannot find gnucash-env
Package: gnucash Version: 1:2.4.10-5 Severity: important Tags: patch Dear Maintainer, I wanted to try to generate a customized report in gnucash. The instructions showed I should be generating a unique user id with the program gnucash-make-guids The second line in gnucash-make-guids generates an error as this program is not part of the PATH. The file named gnucash-env is in the same directory as gnucash-make-guids I modified the second line in the file : /usr/lib/i386-linux-gnu/gnucash/overrides/gnucash-make-guids originally as: exec gnucash-env guile -s $0 $@ to read as follows: exec ./gnucash-env guile -s $0 $@ * What was the outcome of this action? This now generates the 100 default guuids as expected When I run the command: cd /usr/lib/i386-linux-gnu/gnucash/overrides/ ./gnucash-make-guids 10 I get the following results: (process:13027): GLib-CRITICAL **: g_hash_table_lookup: assertion `hash_table != NULL' failed * 14:35:21 WARN gnc.backend.dbi [gnc_module_init_backend_dbi()] No DBD drivers found cf91ecb0e510c9fd45a6242464c62c59 165f169e2f5c5f8c0251089668cb6f91 226b66091bfdf74d7b822789377fd9b6 8fb754bad196b186a008d236585adb0e c287bb151266a45157d7a5ddbdcef78f 440a723fff1f0f06c4bebaf64ba9e267 3b9f8132674a60fa8ba795462872bdd6 a4d887c4b381f37c803631706aa89ccc 03b5e5869fd009f8e17bd365b432b53d 39b8e6e0089a10d64204ee8b444852f0 Some deprecated features have been used. Set the environment variable GUILE_WARN_DEPRECATED to detailed and rerun the program to get more information. Set it to no to suppress this message. The global UUIDs shown are usable, although the error messages shown are disturbing, but that is another issue... Not sure about the significance of the warnings... I would hope the application would run without any warnings. -- System Information: Debian Release: wheezy/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: i386 (i686) Kernel: Linux 3.2.0-4-686-pae (SMP w/1 CPU core) Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages gnucash depends on: ii gconf-service 3.2.5-1+build1 ii gnucash-common 1:2.4.10-5 ii guile-1.8 1.8.8+1-8 ii guile-1.8-libs 1.8.8+1-8 ii libaqbanking34 5.0.24-1 ii libc6 2.13-35 ii libcairo2 1.12.2-2 ii libcrypt-ssleay-perl 0.58-1 ii libdate-manip-perl 6.34-1 ii libdbi10.8.4-6 ii libfinance-quote-perl 1.17+git20120506-1 ii libgconf-2-4 3.2.5-1+build1 ii libgdk-pixbuf2.0-0 2.26.1-1 ii libglade2-01:2.6.4-1 ii libglib2.0-0 2.33.12+really2.32.4-3 ii libgnome-keyring0 3.4.1-1 ii libgnome2-02.32.1-2 ii libgnomecanvas2-0 2.30.3-1.2 ii libgnomeui-0 2.24.5-2 ii libgoffice-0.8-8 0.8.17-1.2 ii libgtk2.0-02.24.10-2 ii libgwengui-gtk2-0 4.3.3-1 ii libgwenhywfar604.3.3-1 ii libhtml-tableextract-perl 2.11-1 ii libhtml-tree-perl 5.02-1 ii libktoblzcheck1c2a 1.39-1 ii libofx41:0.9.4-2.1 ii libpango1.0-0 1.30.0-1 ii libwebkitgtk-1.0-0 1.8.1-3.3 ii libwww-perl6.04-1 ii libx11-6 2:1.5.0-1 ii libxml22.8.0+dfsg1-6 ii perl 5.14.2-14 ii slib 3b1-3.1 ii zlib1g 1:1.2.7.dfsg-13 Versions of packages gnucash recommends: ii gnucash-docs 2.4.1-3 ii yelp 3.4.2-1+b1 Versions of packages gnucash suggests: pn libdbd-mysqlnone pn libdbd-pgsqlnone pn libdbd-sqlite3 none -- no debconf information -- debsums errors found: debsums: changed file /usr/lib/i386-linux-gnu/gnucash/overrides/gnucash-make-guids (from gnucash package) The debsum error above is normal as it was necessary to change the file to make it work as stated earlier. Thanks, -- Gerold Rupprecht -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#599161: #599161: Xen debug patch for the clock shifts by 50 minutes bug.
Hi all,
I've BCC'd a number of people who have reported seeing this bug at
various times in the past.
If you can still repro I'd appreciate it if you could give the patch in
http://marc.info/?l=xen-develm=135049062216685w=2 (also attached) a go
and report back success/failure and the output of the debugging messages
produced.
Thanks,
Ian.
--
Ian Campbell
Current Noise: Death - Evil Dead
Executive ability is prominent in your make-up.
diff -r c1c549c4fe9e xen/arch/x86/time.c
--- a/xen/arch/x86/time.c Mon Oct 15 16:51:44 2012 +0100
+++ b/xen/arch/x86/time.c Wed Oct 17 17:13:22 2012 +0100
@@ -523,11 +523,12 @@ static s_time_t __read_platform_stime(u6
static void plt_overflow(void *unused)
{
int i;
-u64 count;
+u64 count, old_stamp, tsc;
s_time_t now, plt_now, plt_wrap;
spin_lock_irq(platform_timer_lock);
+old_stamp = plt_stamp;
count = plt_src.read_counter();
plt_stamp64 += (count - plt_stamp) plt_mask;
plt_stamp = count;
@@ -540,6 +541,14 @@ static void plt_overflow(void *unused)
plt_wrap = __read_platform_stime(plt_stamp64 + plt_mask + 1);
if ( ABS(plt_wrap - now) ABS(plt_now - now) )
break;
+rdtscll(tsc);
+printk(XXX plt_overflow: plt_now=%PRIx64 plt_wrap=%PRIx64
+now=%PRIx64 old_stamp=%PRIx64 new_stamp=%PRIx64
+plt_stamp64=%PRIx64 plt_mask=%PRIx64
+tsc=%PRIx64 tsc_stamp=%PRIx64\n,
+ plt_now, plt_wrap, now, old_stamp, plt_stamp, plt_stamp64,
+ plt_mask, tsc, this_cpu(cpu_time).local_tsc_stamp);
+break;
plt_stamp64 += plt_mask + 1;
}
if ( i != 0 )
Bug#691378: boost ftbfs with python3.3 as a supported version and the multiarch setup
Here is one solution. It works, but it's not very in a jam - style. This is my first time tinkering with jam. Regards, Dmitrijs. fix-ftbfs-python-3.3.patch Description: Binary data
Bug#691504: kstars: implausible solar-system transit-times
Package: kstars Version: 4:4.8.4-1 Severity: normal Dear Maintainer, playing around with kstars i discovered that the displayed transit-times for solar-system-objects are often (always?) implausible. if i take a look at venus, jupiter and moon: they all show the same transit-time which can't be right for all of them. this can be verified by: - setting the clock to the given transit-time. for the moon the time is more or less correct (but nevertheless almost 2 degree off) but venus and jupiter are definitly far away from transit. - compare the given transit-time with the point in the middle between rise/set-time (these seem to be fine). Greets S. -- System Information: Debian Release: wheezy/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing'), (500, 'stable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.6.3 (SMP w/2 CPU cores) Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages kstars depends on: ii kde-runtime 4:4.8.4-1 ii kstars-data 4:4.8.4-1 ii libc6 2.13-35 ii libcfitsio3 3.300-2 ii libgcc1 1:4.7.2-4 ii libgl1-mesa-glx [libgl1] 8.0.4-2 ii libindi0b 0.9.1-2 ii libkdecore5 4:4.8.4-3 ii libkdeui5 4:4.8.4-3 ii libkio5 4:4.8.4-3 ii libknewstuff3-4 4:4.8.4-3 ii libqt4-dbus 4:4.8.2+dfsg-2 ii libqt4-network4:4.8.2+dfsg-2 ii libqt4-opengl 4:4.8.2+dfsg-2 ii libqt4-svg4:4.8.2+dfsg-2 ii libqtcore44:4.8.2+dfsg-2 ii libqtgui4 4:4.8.2+dfsg-2 ii libstdc++64.7.2-4 ii zlib1g1:1.2.7.dfsg-13 kstars recommends no packages. Versions of packages kstars suggests: pn indi-bin none ii khelpcenter4 4:4.8.4-1 ii konqueror 4:4.8.4-2 pn xplanet 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#676393: one command is failing to run
One more bug in one command https://github.com/glejeune/Ruby-Graphviz/issues/56 I'll upload the package as all tests are run correctly and other commands are also running correctly. -- പ്രവീണ് അരിമ്പ്രത്തൊടിയില് You have to keep reminding your government that you don't get your rights from them; you give them permission to rule, only so long as they follow the rules: laws and constitution. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#691449: dpkg-buildflags should have an export mode for shell scripts
On Fri, 2012-10-26 at 10:54:51 +0200, Matthias Klose wrote: On 25.10.2012 21:20, Guillem Jover wrote: Or just “$(shell dpkg-buildflags --export=configure)”? I do not really see a problem here. I might be missing something else going on, but otherwise I'll be closing this report in a bit. No. Doesn't work if the call depends on the loop variable. (In addition using $(shell) allows to set a variables once per Makefile, and not once per loop.) Right, but that's needed for stuff like for p in $(filter-out $(PYTHON_DEFAULT), $(PYTHONS)) \ ; do \ dh_auto_configure --builddir=$(CURDIR)/debian/build-$$p \ -- \ $(BARE_CONFIG_FLAGS) \ --disable-ruby \ PYTHON=$$p \ $$(DEB_CFLAGS_MAINT_APPEND=$$($$p-config --includes) dpkg-buildflags --export=configure); \ done Ah ok, in that case you could use something like? ,--- for VAR in LIST; do \ eval set `DEB_CFLAGS_MAINT_APPEND=$$VAR dpkg-buildflags --export=configure`; \ CMD $$@; \ done `--- 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#690887: RFS: update of openid4java, publish maven artifacts
I pushed the necessary changes to the branch thkoch_changes on http://anonscm.debian.org/gitweb/?p=pkg-java/openid4java.git Please fast-forward into master and delete the branch with git push origin :thkoch_changes Regards, Thomas Koch, http://www.koch.ro -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#690887: patch available
I pushed the necessary changes to the branch thkoch_changes on http://anonscm.debian.org/gitweb/?p=pkg-java/openid4java.git Please fast-forward into master and delete the branch with git push origin :thkoch_changes Regards, Thomas Koch, http://www.koch.ro -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#691505: org-mode: Fails to tangle code in BEGIN_SRC..END_SRC
Package: org-mode Version: 7.9.1-2 Severity: normal Typing C-c C-v t on the following file creates only bar.txt but not foo.txt as expected. Does it matter whether BEGIN_SRC and END_SRC are written in small letters or not? The .. lines are not part of foo.org File foo.org #+BEGIN_SRC text :tangle foo.txt foo #+END_SRC #+begin_src text :tangle bar.txt bar #+end_src End of foo.org Best wishes, Gábor Braun -- System Information: Debian Release: 6.0.6 APT prefers stable APT policy: (990, 'stable'), (650, 'testing'), (600, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 3.2.0-3-amd64 (SMP w/2 CPU cores) Locale: LANG=hu_HU.UTF-8, LC_CTYPE=hu_HU.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages org-mode depends on: ii dpkg 1.15.8.13 Debian package management system ii emacs23 23.4+1-4 The GNU Emacs editor (with GTK+ us ii emacs24 24.2+1-1 GNU Emacs editor (with GTK+ user i ii install-info 4.13a.dfsg.1-6 Manage installed documentation in org-mode recommends no packages. Versions of packages org-mode suggests: pn ditaa none (no description available) pn easypgnone (no description available) pn remember-el none (no description available) -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#688269: libroken18-heimal: Please change priority to optional
On Tue, 2012-10-23 at 19:31 +1100, Brian May wrote: On 21 October 2012 23:06, Sebastian Ramacher sebast...@ramacher.at wrote: On 2012-10-21 21:04:51, Brian May wrote: Where is this git repository you are looking at? Will check again tomorrow. That's the one at git://git.debian.org/git/collab-maint/heimdal/ Ok, I see it. 3c279602a4dd543cb44fc269241ca4da59f5da7b makes it optional 8647c84d416cf734b658515c6c8fad366a12fe16 removes the optional tags, I think overall this is a NOP because the source is still priority: Optional. d41f5a26e3facc929ff895e7cb41baa19875d4a4 makes it extra According to the git repository version 1.6~git20120403+dfsg1-3 has not been released, but according to the version in Debian unstable, it would appear it has been released. Will CC Jelmer Vernooij jel...@debian.org, maybe he can explain what is going on here. I should've been a bit more verbose about this. IIRC this was just being consistent with the ftp-master overrides. According to policy packages in extra are (among other things) only likely to be useful if you already know what they are or have specialized requirements (such as packages containing only detached debugging symbols). I could see the Heimdal Kerberos libraries being covered by that, but moving back to optional (and requesting ftp-master to change the overrides) also seems reasonable to me. Cheers, Jelmer signature.asc Description: This is a digitally signed message part
Bug#672182: Pending fixes for bugs in the libperl-critic-perl package
tag 672182 + pending thanks Some bugs in the libperl-critic-perl package are closed in revision 04f8a03f73dc858b655cd36872c856815d52f164 in branch 'master' by Salvatore Bonaccorso The full diff can be seen at http://anonscm.debian.org/gitweb/?p=pkg-perl/packages/libperl-critic-perl.git;a=commitdiff;h=04f8a03 Commit message: Set up to use conf-mode on the .perlcriticrc file Thanks: Kevin Ryde use...@zip.com.au and intrigeri intrig...@boum.org Closes: #672182 -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
