Bug#722687: wx.media missing
reassign 722687 wxpython3.0 3.0.0.0+dfsg-1 retitle 722687 wxpython3.0: wx.media missing thanks On Fri, Nov 22, 2013 at 11:56:31AM +1300, Olly Betts wrote: On Thu, Nov 21, 2013 at 11:03:35AM +, Russel Winder wrote: Given the offence that including this is the Debian package caused shouldn't there be a special package with it in for those who actually want it? There is for the C++ parts, but Fabrice just disabled the Python parts (I don't know why he chose to do that, and he hasn't responded to being Cc-ed on this bug). Debian packages such as whyteboard install fine but fail due to the: import wx.media but there is no package to depend on that provides this, at least as far as I (and I guess the whyteboard packager) can tell. You say such as whyteboard - what other packages fail in this way? With older Debian packages of wxwidgets2.8, import wx.media didn't result in an error, but it didn't actually do anything useful, as wxMediaCtrl wasn't enabled in the C++ library. According to #725711, just commenting out import wx.media in whyteboard works, so I'd suggest doing that - it should return whyteboard to where it was before wxMediaCtrl was enabled. As for creating a separate package for wx.media, that isn't something I'm personally planning to work on - I've already got too much wx-related packaging work on my plate with the migration to wx 3.0. If somebody provides a sane patch to do that for wxPython 3 (once that's out and packaged), I'd be happy to apply it. Reassigning to wxpython3.0, since that's now in the archive. We're aiming to replace wxwidgets2.8 before jessie, so it makes much more sense to address this in wxpython3.0. Cheers, Olly -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#746526: python-wxgtk2.8: python segfaults on wx/_html.so
On Thu, May 01, 2014 at 12:17:03AM +0100, Olly Betts wrote: On Thu, May 01, 2014 at 12:49:53AM +0200, Martijn wrote: I encountered segfaults of python2.7 when using wikidpad. Running it through gdb revealed that the problem was wx/_html.so: At the moment of the crash I had the wikidpad internal html rendere switched on en was browsing the wiki. After I disabled html rendering or swithed to the webkit renderer, which is offered in addition to the wxwidget html widget, wikidpad ran without problems. This pinpoints the problem to the wxwidget html engine or underlying modules. The gdb listing prior after the segfault is: Program received signal SIGSEGV, Segmentation fault. 0x74b02b07 in wxArrayString::Index(wchar_t const*, bool, bool) const () from /usr/lib/x86_64-linux-gnu/libwx_baseu-2.8.so.0 (gdb) pyframe No symbol PyStringObject in current context. (gdb) up #1 0x75b2ff74 in wxHtmlTag::HasParam(wxString const) const () from /usr/lib/x86_64-linux-gnu/libwx_gtk2u_html-2.8.so.0 Without debug info, this doesn't really help narrow things down enough. You could retry with python-wxgtk2.8-dbg instead of python-wxgtk2.8 - despite the name, it's actually a replacement build rather than just detached debug symbols (because it predates the -dbg naming convention). Unfortunately, wx 2.8 is effectively no longer maintained. Upstream haven't officially ended development, but nobody actually willing to put in the work to continuing making 2.8.x releases has stepped forward in the ~3 years since 2.8.12 was released, and bug reports against it rarely get much attention. I'm working on moving Debian to wx 3.0, but I haven't packaged wxpython 3.0 yet. wxpython3.0 is now available in unstable - if you are able to retest with that and the problem still occurs, we can report it upstream and it may get fixed. Cheers, Olly -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#757315: Digikam freezes when configuration window is opened and external mysql db is used.
Package: digikam Version: 4:4.1.0-1 Severity: normal Dear Maintainer, Since update to 4.1.0-1 when used with an external mysql db Digikam freezes totally on opening the setting window, irrespective of the setting tab accessed. CPU load is 100% on one core and never comes down (application left opened for over 48 hours, collection is ±3 images). Behavior is normal (albeit slow) when SQlite db is used. Tried to recreate mysql database from scratch, purging digikam and related packages, removing all configuration files, and reinstalling but it leads to the same behavior. Searching the Internet I found https://bugs.kde.org/show_bug.cgi?id=337737 wich seems to be the same bug manifesting itself in OpenSuse, so maybe it's upstream problem. Workaround: manually populate database for collection (from previous working db dump in my case), change Digikam configuration by using text editor, and never open the setting window. Or stick with SQlite db. I will try to get proper debug informations today. Thank you for your time and work. -- System Information: Debian Release: jessie/sid Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.16.0-vanilla64 (SMP w/8 CPU cores) Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages digikam depends on: ii digikam-data 4:4.1.0-1 ii digikam-private-libs 4:4.1.0-1 ii kde-runtime 4:4.13.3-1 ii libc6 2.19-7 ii libgcc1 1:4.9.1-4 ii libgphoto2-6 2.5.4-1 ii libgphoto2-port10 2.5.4-1 ii libkdcraw23 4:4.13.1-2 ii libkdecore5 4:4.13.3-2 ii libkdeui5 4:4.13.3-2 ii libkexiv2-11 4:4.13.1-1 ii libkhtml5 4:4.13.3-2 ii libkio5 4:4.13.3-2 ii libkipi11 4:4.13.3-1 ii libknotifyconfig4 4:4.13.3-2 ii libkparts44:4.13.3-2 ii libnepomukcore4 4:4.13.3-1 ii libopencv-core2.4 2.4.9+dfsg-1 ii libopencv-imgproc2.4 2.4.9+dfsg-1 ii libphonon44:4.7.1-1 ii libqt4-dbus 4:4.8.6+git49-gbc62005+dfsg-1 ii libqt4-sql4:4.8.6+git49-gbc62005+dfsg-1 ii libqt4-sql-sqlite 4:4.8.6+git49-gbc62005+dfsg-1 ii libqt4-xml4:4.8.6+git49-gbc62005+dfsg-1 ii libqtcore44:4.8.6+git49-gbc62005+dfsg-1 ii libqtgui4 4:4.8.6+git49-gbc62005+dfsg-1 ii libsolid4 4:4.13.3-2 ii libsoprano4 2.9.4+dfsg-1.1 ii libstdc++64.9.1-4 ii libthreadweaver4 4:4.13.3-2 ii perl 5.18.2-7 ii phonon4:4.7.1-1 Versions of packages digikam recommends: ii chromium [www-browser] 35.0.1916.153-2 ii ffmpegthumbs4:4.13.3-1 ii iceweasel [www-browser] 31.0-3 ii kipi-plugins4:4.1.0-1 ii konqueror [www-browser] 4:4.13.3-1 ii lynx-cur [www-browser] 2.8.9dev1-2 ii mplayerthumbs 4:4.13.3-1 Versions of packages digikam suggests: pn digikam-doc none ii systemsettings 4:4.11.11-1 -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#751271: usb-modeswitch: doesn't switch Huawei E3131s-2 on boot
Control: tags -1 +patch +pending Hi Jakub, Le lundi, 4 août 2014, 20.11:33 Jakub Wilk a écrit : * Didier 'OdyX' Raboud o...@debian.org, 2014-08-03, 01:21: * The udev rule seems to be working As I noted previously, it didn't work here, unless I renamed the rule file. But now I checked again, and it works without renaming. Very odd. Possibly related bug: #754348 Jakub: could you (out of luck) try the attached patch that reverts this? I don't think this will be necessary; see below. More importantly, jimctl doesn't seem to honour TMPDIR. :-( Thanks for the catch, I've reported this upstream: https://github.com/msteveb/jimtcl/issues/17 So I cherry picked the upstream patch for jimtcl, and patched /lib/udev/usb_modeswitch to use TMPDIR. Now the device switches correctly. \o/ Yay. So we're on the good track here. I've cherry-picked the upstream patch on top of the new upstream release [0] and it's now pending in binary-NEW [1]. I might upload 0.74-2 with that patch in the meantime. As for usb-modeswitch, I'm considering the attached patch to use /run as TMPDIR for all three init systems. Expect an upload soon'ish. Cheers, OdyX [0] http://anonscm.debian.org/cgit/collab-maint/jimtcl.git/commit/?id=ec11aff0a36e7d2d847d88c7a1eecbedb2bb2cde [1] https://ftp-master.debian.org/new/jimtcl_0.75-1.html --- a/usb-modeswitch-upstart.conf +++ b/usb-modeswitch-upstart.conf @@ -1,5 +1,6 @@ start on usb-modeswitch-upstart task +env TMPDIR=/run script exec /usr/sbin/usb_modeswitch_dispatcher --switch-upstart $UMS_PARAM end script --- a/usb_modeswitch.sh +++ b/usb_modeswitch.sh @@ -82,6 +82,7 @@ elif [ -d /run/systemd/system/ ]; then # Test if systemd is running exec /bin/systemctl --no-block start usb_modeswitch@$1.service else + export TMPDIR=/run exec /usr/sbin/usb_modeswitch_dispatcher --switch-mode $1 fi exit 0 --- a/usb_modeswitch@.service +++ b/usb_modeswitch@.service @@ -4,3 +4,4 @@ [Service] Type=oneshot ExecStart=/usr/sbin/usb_modeswitch_dispatcher --switch-systemd %I +Environment=TMPDIR=/run
Bug#757317: [cloud-scripts]: cqa-compare-ref-rebuild: Relative path use is failing
Package: qa.debian.org Severity: normal Hello, $ cqa-compare-ref-rebuild -s /tmp/log-clang-05-08-14 -o log-clang-05-08-14-results -i clang Is failing with: generating clang results list: log-clang-05-08-14-results/clang.res sh: 1: cannot create log-clang-05-08-14-results/clang.res: Directory nonexistent generating normal results list: log-clang-05-08-14-results/normal.res sh: 1: cannot create log-clang-05-08-14-results/normal.res: Directory nonexistent log-clang-05-08-14-results/ is created but I guess cqa-compare-ref-rebuild is moving directory after. cqa-compare-ref-rebuild -s /tmp/log-clang-05-08-14 -o /home/sylvestre/log-clang-05-08-14-results -i clang works Cheers, Sylvestre -- System Information: Debian Release: jessie/sid APT prefers testing APT policy: (900, 'testing'), (600, 'unstable'), (500, 'stable-updates'), (500, 'stable'), (300, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.13-1-amd64 (SMP w/4 CPU cores) Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#692249: sata boot+grub unknown filesystem without boot=on
07.08.2014 00:14, Gianluigi Tiesi wrote: qemu removed the option and grub still says unknown filesystem Yes, we removed the old option long time ago. But I was really worried about this unknown filesystem. You can close the bug I don't think it's a really an useful scenario, I was trying to boot my win7 partition with kvm using -snapshot, it wouldn't work anyway You're Very Wrong (tm). Lots of people do this all the time, me included. I've a dual-boot machine (with windows and linux), and while I don't reboot into windows often, but I do run it in qemu/kvm quite often, giving qemu my /dev/sda and choosing to boot windows there. It works just fine either way. It even keeps its activation (win7 OEM), because I pass /sys/firmware/acpi/tables/SLIC to the guest, the same as this PC was shipped with. I ran _many_ systems initially installed on a bare metal in qemu/kvm, just giving qemu their hdd directly (with or without -snapshot), and I run many systems initially installed in qemu/kvm on bare metal, after copying their hdd image to real hdd. Actually I installed all our windows machines at office this way - initially in qemu, copying to hdd with all installed and configured progs. All this without changing the systems in question in any noticeable way -- with the exception that initial boot of windows in foreign environment requires installing a compatible driver, which is, for metal=qemu case, either generic IDE or ahci/sata. Linux systems works without any modifications at all. As I already said, there's somethig wrong on your system. It shuoldn't work (or, rather, fail) like this. It smells like a bug which I want to find and fix. Thanks, /mjt -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#757318: v4l2loopback: ftbfs with DEB_BUILD_PARALLEL=1
Package: v4l2loopback Version: 0.8.0-2 When build v4l2loopback on mips64el, I get a problem: Adding cdbs dependencies to debian/v4l2loopback-utils.substvars dh_installdirs -pv4l2loopback-utils dh_installdocs -pv4l2loopback-utils ./README ./NEWS ./TODO ./AUTHORS dh_installexamples -pv4l2loopback-utils dh_installman -pv4l2loopback-utils man/v4l2loopback-ctl.1: No such file or directory at /usr/bin/dh_installman line 130. make: *** [binary-install/v4l2loopback-utils] Error 2 /usr/share/cdbs/1/rules/debhelper.mk:211: recipe for target 'binary-install/v4l2loopback-utils' failed dpkg-buildpackage: error: fakeroot debian/rules binary-arch gave error exit status 2 It seems due to PARALLEL build. http://mips64el.debian.net/debian/buildlog/v/v4l2loopback_0.8.0-2/v4l2loopback_0.8.0-2_mips64el-20140730-1933.build -- YunQiang Su -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#757306: wammu: Please update to use wxpython3.0
Hi Olly Dne Thu, 7 Aug 2014 14:35:56 +1200 Olly Betts o...@survex.com napsal(a): Package: wammu Version: 0.36-2 Severity: important Tags: patch sid jessie User: freewx-ma...@lists.alioth.debian.org Usertags: wxpy3.0 Control: block 755757 by -1 We're aiming to migrate the archive to using wxpython3.0 instead of wxwidgets2.8, and hope to drop wxwidgets2.8 before jessie is released. I've done some testing of wammu with python-wxgtk3.0. I've not used it before and wasn't able to work out how to get it to connect to my phone, but the GUI features I could exercise without doing so all seem to work OK. It would be great if someone more familiar with the package could do some more thorough testing though. I currently do not have any supported phone around, so I can't do much testing as well, but indeed it seems to work fine. I'm happy to NMU this change if you wish me to - just let me know. Feel free to do so. Thanks -- Michal Čihař | http://cihar.com | http://blog.cihar.com signature.asc Description: PGP signature
Bug#739889: RFS: twython/3.1.2-1 [ITP] -- Pure Python wrapper for the Twitter API
On Tue, Aug 5, 2014 at 2:44 PM, Eriberto eribe...@eriberto.pro.br wrote: Hi! No need rename. And is dh_installchangelogs, not dh_autoinstalldocs. Cheers, Eriberto 2014-08-05 17:37 GMT-03:00 Josué Ortega josueort...@debian.org.gt: I have one question about dh_autoinstalldocs, should I rename the History.rst before pass it as parementer to dh_autoinstalldocs? Hi Eriberto, I have made the changes you asked for. The new version is on mentors [0][1]. Thanks. Cheers, [0]: http://mentors.debian.net/debian/pool/main/t/twython/twython_3.1.2-1.dsc [1]: http://mentors.debian.net/package/twython -- Josue Ortega Happy Hacking http://josueortega.org PGP key 4096R/AB4AFD3F 2012-08-20 Fingerprint = 7733 B328 D279 5F5B E232 5ADD 0150 9D5C AB4A FD3F
Bug#757320: Wrong dnssec-trigger-script path in /etc/NetworkManager/dispatcher.d/01-dnssec-trigger
Package: dnssec-trigger Version: 0.13~svn685-1 Severity: important Control: tags -1 patch Dear maintainer, The path to dnssec-trigger-script in the NetworkManager dispatcher hook is wrong. It seems that with NetworkManager 0.9.10.0-1, the shell script fallback fails, which means that DHCP-supplied DNS server notification does not work. Please find attached a patch that fixes the issue. Cheers, Nicolas Dandrimont -- System Information: Debian Release: jessie/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing'), (500, 'stable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.14-2-amd64 (SMP w/4 CPU cores) Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages dnssec-trigger depends on: ii init-system-helpers 1.20 ii libc62.19-7 ii libgdk-pixbuf2.0-0 2.30.7-1 ii libglib2.0-0 2.40.0-3 ii libgtk2.0-0 2.24.24-1 ii libldns1 1.6.17-5 ii libssl1.0.0 1.0.1h-3 ii python 2.7.8-1 ii unbound 1.4.22-1 dnssec-trigger recommends no packages. dnssec-trigger suggests no packages. -- no debconf information From d834d37f068a31c6ea93f71e7ee7e03a4ddb56a1 Mon Sep 17 00:00:00 2001 From: Nicolas Dandrimont nicolas.dandrim...@crans.org Date: Thu, 7 Aug 2014 08:39:00 +0200 Subject: [PATCH] Fix path to dnssec-trigger-script in the NetworkManager hook --- debian/patches/debian-quirks.patch | 11 +++ 1 file changed, 11 insertions(+) diff --git a/debian/patches/debian-quirks.patch b/debian/patches/debian-quirks.patch index c81b084..9d890e0 100644 --- a/debian/patches/debian-quirks.patch +++ b/debian/patches/debian-quirks.patch @@ -1,5 +1,16 @@ --- dnssec-trigger.orig/01-dnssec-trigger.in +++ dnssec-trigger/01-dnssec-trigger.in +@@ -11,8 +11,8 @@ fi + + # Exec the dnssec-trigger update script that uses NetworkManager API to gather + # all the necessary information. +-if [ -x @libexecdir@/dnssec-trigger-script ]; then +-exec @libexecdir@/dnssec-trigger-script --update ++if [ -x /usr/lib/dnssec-trigger/dnssec-trigger-script ]; then ++exec /usr/lib/dnssec-trigger/dnssec-trigger-script --update + fi + + # When dnssec-trigger-script is absent or not executable, the original @@ -23,7 +23,7 @@ fi # set PATH correctly instead of absolute paths to binaries PATH=@sbindir@:@bindir@:/sbin:/usr/sbin:/bin:/usr/bin -- 2.1.0.rc1
Bug#544366: devscripts: debsign wont sign if DEBRELEASE_DEBS_DIR set to unexisting dir but changes specified
Hello, can someone look into this bug? I'm very annoyed by it too. And I fully agree with Emilio's interpretation. DEBRELEASE_DEBS_DIR should only be looked up if I don't specify a .changes files to sign. It makes absolulety no sense to consider the argument as a filename to look up in another directory. What would be the use case? Furthermore, I have set DEBRELEASE_DEBS_DIR so that debrelease does the right thing for me with git-buildpackage --git-export-dir=../build-area/ and I'm pretty annoyed that it gets in the way when I want to sign a random .dsc/.changes file. Note that the same problem also affects debc and debi: $ debc xsane_0.998-6_amd64.changes debc: config file specified DEBRELEASE_DEBS_DIR directory ../build-area does not exist! $ debi xsane_0.998-6_amd64.changes debi: config file specified DEBRELEASE_DEBS_DIR directory ../build-area does not exist! Thank you in advance! -- Raphaël Hertzog ◈ Debian Developer Discover the Debian Administrator's Handbook: → http://debian-handbook.info/get/ -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#745524: Please migrate to lcms2
Control: severity -1 important Hello Olivier, Debian switched from liblcms1 to liblcms2 but it looks like that xsane is not able to use the newer version of the library. Do you think you could update it to support it? It's probably not very complicate as it looks like that the new library has the symbol tested by xsane's configure script: $ objdump --dynamic-syms /usr/lib/x86_64-linux-gnu/liblcms2.so|grep cmsOpenProfileFromFile 00017c80 gDF .text 000d Base cmsOpenProfileFromFile 00017be0 gDF .text 0094 Base cmsOpenProfileFromFileTHR On Tue, 22 Apr 2014, Moritz Muehlenhoff wrote: As pre-announced in https://lists.debian.org/debian-devel/2013/12/msg00570.html it is planned to remove lcms1 for jessie. Please adapt your package. I updated the build-depends to indicate liblcms2-dev but the configure script doesn't detect it and doesn't use it: ** checking whether GTK+-2.0 is requested... yes checking whether GIMP plugin is requested... yes checking whether GIMP-2.0 is requested... yes checking whether JPEG support is requested... yes checking whether PNG support is requested... yes checking whether TIFF support is requested... yes checking whether LCMS (color management) support is requested... yes ** [...] checking for cmsOpenProfileFromFile in -llcms... no [...] * * * XSANE configure status: * * --- * * - NLS activated (external) * * - GIMP plugin activated * * - JPEG support activated * * - TIFF support activated * * - PNG support activated * * - LCMS (color management) support deactivated* * * Still I uploaded the packages so that xsane gets built without LCMS support and so that it can go back to testing. Cheers, -- Raphaël Hertzog ◈ Debian Developer Discover the Debian Administrator's Handbook: → http://debian-handbook.info/get/ -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#757312: wordpress: 3.9.2 Security Release
On Thu, Aug 07, 2014 at 07:44:31AM +0200, Salvatore Bonaccorso wrote: See https://wordpress.org/news/2014/08/wordpress-3-9-2/ Yep, saw it this morning. Should have something in the next few hours. Thanks for the heads-up anyhow (I've missed these before). - Craig -- Craig Small (@smallsees) http://enc.com.au/ csmall at : enc.com.au Debian GNU/Linux http://www.debian.org/ csmall at : debian.org GPG fingerprint:5D2F B320 B825 D939 04D2 0519 3938 F96B DF50 FEA5 -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#757293: libvirt-daemon-system (1.2.7-3) fails to start
Package: libvirt-daemon-system Followup-For: Bug #757293 Hello, MMMh, my bad I guess As the libvirt-bin package has been renamed to libvirt-daemon-system, the preinst script part that stop the daemon cleanly is not executed since libvirt-daemon-system was not installed before... What could be done: - Remove the -nl part of the version comparaison, this will execute the stop and the deb-systemd-helper actions even if the package was not installed before (we need to be sure that d-s-h is not giving us an error if the old service file is inexistant) - Try to guess what is last configured version of libvirt-bin package instead of using the version passed by dpkg - Move (or duplicate) the code in libvirt-bin preinst I'm wondering if with the 2nd and 3rd option we might not run in cases (libvirt-bin being removed at the same time libvirt-daemon-system is being installed) where the stop and d-s-h is not executed as it should (might be wrong here). Cheers, Laurent Bigonville -- System Information: Debian Release: jessie/sid APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.14-2-amd64 (SMP w/8 CPU cores) Locale: LANG=fr_BE.utf8, LC_CTYPE=fr_BE.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages libvirt-daemon-system depends on: ii adduser 3.113+nmu3 ii gettext-base 0.19.2-1 ii init-system-helpers 1.20 ii libapparmor1 2.8.0-5.1+b1 ii libaudit11:2.3.7-1 ii libavahi-client3 0.6.31-4 ii libavahi-common3 0.6.31-4 ii libblkid12.20.1-5.8 ii libc62.19-7 ii libcap-ng0 0.7.3-1.1 ii libdbus-1-3 1.8.6-1 ii libdevmapper1.02.1 2:1.02.85-2 ii libgnutls-deb0-283.2.16-1 ii libnl-3-200 3.2.24-2 ii libnl-route-3-2003.2.24-2 ii libnuma1 2.0.9-1 ii librados20.80.5-1 ii librbd1 0.80.5-1 ii libsasl2-2 2.1.26.dfsg1-11 ii libselinux1 2.3-1 ii libssh2-11.4.3-3 ii libsystemd-daemon0 208-7 ii libvirt-clients 1.2.7-3 ii libvirt-daemon 1.2.7-3 ii libvirt0 1.2.7-3 ii libxml2 2.9.1+dfsg1-4 ii libyajl2 2.1.0-1 ii logrotate3.8.7-1 Versions of packages libvirt-daemon-system recommends: ii bridge-utils 1.5-9 ii dmidecode 2.12-3 ii dnsmasq-base 2.71-1 ii ebtables 2.0.10.4-3 ii iproute2 3.16.0-1 ii iptables 1.4.21-2 ii parted3.2-2 ii pm-utils 1.4.1-15 Versions of packages libvirt-daemon-system suggests: pn apparmor none ii auditd 1:2.3.7-1 ii policykit-1 0.105-6.1 pn radvdnone ii systemd 208-7 pn systemtapnone -- Configuration Files: /etc/libvirt/qemu.conf [Errno 13] Permission non accordée: u'/etc/libvirt/qemu.conf' -- 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#757321: libfontconfig1-dev: error in doc-base file or missing file
Package: libfontconfig1-dev Version: 2.11.0-5 Severity: normal Dear Maintainer, the doc-base file /usr/share/doc-base/fontconfig-devel contains: Format: HTML Index: /usr/share/doc/libfontconfig1-dev/fontconfig-devel/index.html but the /usr/share/doc/libfontconfig1-dev/fontconfig-devel/index.html file is not installed by the package. -- System Information: Debian Release: jessie/sid APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: i386 (i686) Foreign Architectures: amd64 Kernel: Linux 3.14-2-686-pae (SMP w/2 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages libfontconfig1-dev depends on: ii libexpat1-dev 2.1.0-6 ii libfontconfig12.11.0-5 ii libfreetype6-dev 2.5.2-1 ii pkg-config0.28-1 libfontconfig1-dev recommends no packages. libfontconfig1-dev 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#755234: [Pkg-xfce-devel] Bug#755234: Bug#755234: reload logind
On Thu, 07 Aug 2014, Yves-Alexis Perez wrote: It's really not certain we'll have Xfce 4.12 in time for Jessie, so I'd really much like having Xfce 4.10 working correctly with upower0.99, Hmmpf, if we don't get 4.12, yes, that would be a great thing to have proper upower0.99 support. It is funny, in former times uploads of programs that break other was considered an RC bug and not acceptable, and needed to be acoompanied with fixes for the broken packages. Things have changed. Let us see, I will also search for more patches for xpm. Norbert PREINING, Norbert http://www.preining.info JAIST, Japan TeX Live Debian Developer GPG: 0x860CDC13 fp: F7D8 A928 26E3 16A1 9FA0 ACF0 6CAC A448 860C DC13 -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#757322: node-abbrev: absolutely ridiculous package Description
Package: node-abbrev Version: 1.0.5-1 Severity: important I was just wondering about the ITPs on d-devel, and whether those packages should not be called nodejs-* instead of node-*, and was seeing this package in the list first. Both its short description and its long description are utterly ridiculous. Since working as buildd maintainer I have seen some weird and idiotic package short Descriptions, but this is an order of magnitude worse. Please scrap them and write completely new ones which describe, in a positive way, that is, without leaning on another weird scripting language a prospective nodejs user may not know, what this package does. bye, //mirabilos -- Sometimes they [people] care too much: pretty printers [and syntax highligh- ting, d.A.] mechanically produce pretty output that accentuates irrelevant detail in the program, which is as sensible as putting all the prepositions in English text in bold font. -- Rob Pike in Notes on Programming in C -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#757323: nco: error in doc-base file
Package: nco Version: 4.4.2-1 Severity: normal Dear Maintainer, the doc-base file /usr/share/doc-base/nco contains: Format: HTML Index: /usr/share/doc/nco/html/index.html Files: /usr/share/doc/nco/html/*.html whereas the only HTML file provided by the package is: /usr/share/doc/nco/nco.html -- System Information: Debian Release: jessie/sid APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: i386 (i686) Foreign Architectures: amd64 Kernel: Linux 3.14-2-686-pae (SMP w/2 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages nco depends on: ii libc62.19-7 ii libcurl3-gnutls 7.37.1-1 ii libgcc1 1:4.9.1-4 ii libgsl0ldbl 1.16+dfsg-2 ii libnetcdfc7 1:4.1.3-7+b1 ii libstdc++6 4.9.1-4 ii libudunits2-02.2.14-1 nco recommends no packages. nco 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#757324: pvm: add mips64el support in debian/getpvmarch
Package: pvm Version: 3.4.5-12.5 In debian/getpvmarch, the mips and mipsel staff may be changed to mips*) echo LINUXMIPS ;; I tested it on mips64el. it works well. -- YunQiang Su -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#757325: ITP: python-oslo.utils -- set of utility functions for OpenStack
Package: wnpp Severity: wishlist Owner: Thomas Goirand z...@debian.org * Package name: python-oslo.utils Version : 0.1.1 Upstream Author : OpenStack Development Mailing List openstack-...@lists.openstack.org * URL : https://github.com/openstack/oslo.utils * License : Apache-2.0 Programming Lang: Python Description : set of utility functions for OpenStack The Oslo.utils package provides a set of function which are cross-project for OpenStack. For example, it provides text decoding, exception handling, Python module import facility (try_import function), network-related system-level, and time utilities and helper functions. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#757328: afterstep-data: Functions.html contains garbage
Package: afterstep-data Version: 2.2.12-2 Severity: normal Dear Maintainer, the /usr/share/doc/afterstep-data/html/Functions.html file contains a legitimate HTML content that ends with /html. But after that, it also contains a bunch of null bytes and another chunck of HTML content. -- System Information: Debian Release: jessie/sid APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: i386 (i686) Foreign Architectures: amd64 Kernel: Linux 3.14-2-686-pae (SMP w/2 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages afterstep-data depends on: ii fonts-freefont-ttf [ttf-freefont] 20120503-4 ii ttf-freefont 20120503-4 ii ucf3.0030 Versions of packages afterstep-data recommends: ii afterstep 2.2.12-2+b1 afterstep-data 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#757329: apt-dater: Multi-Arch updates are not detected
Package: apt-dater-host Version: 0.9.0-3+wheezy1 Severity: important File: apt-dater Tags: upstream If you are e.g. on amd64 and also have installed i386 multiarch libs, apt-dater does not detect and install updates for it. -- System Information: Debian Release: 7.6 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 3.2.0-4-amd64 (SMP w/2 CPU cores) Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages apt-dater-host depends on: ii debconf [debconf-2.0] 1.5.49 ii libapt-pkg-perl0.1.26+b1 ii libimvirt-perl 0.9.4-4 ii lsb-release4.1+Debian8+deb7u1 ii openssh-server 1:6.0p1-4+deb7u2 ii perl 5.14.2-21+deb7u1 Versions of packages apt-dater-host recommends: ii imvirt 0.9.4-4 ii sudo1.8.5p2-1+nmu1 apt-dater-host suggests no packages. -- Configuration Files: /etc/sudoers.d/apt-dater-host [Errno 13] Keine Berechtigung: u'/etc/sudoers.d/apt-dater-host' -- debconf information: apt-dater-host/assume_yes: true -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#504741: Does bug #504741 exist on a recent asterisk?
tags 504741 +moreinfo thanks Could you please let me know whether bug #504741 still applies on a recent asterisk? Thanks, Jeremy -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#757331: buggy magic: mistakes HTML as unified diff
Package: file Version: 1:5.19-1+exp1 Severity: normal Dear Maintainer, the problem occurs with a file from the bzr-doc package: $ file /usr/share/doc/bzr/html/en/user-guide/shelving_changes.html /usr/share/doc/bzr/html/en/user-guide/shelving_changes.html: unified diff output, UTF-8 Unicode text whereas the file is HTML with some unified diff inside. -- System Information: Debian Release: jessie/sid APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: i386 (i686) Foreign Architectures: amd64 Kernel: Linux 3.14-2-686-pae (SMP w/2 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages file depends on: ii libc6 2.19-7 ii libmagic1 1:5.19-1+exp1 ii zlib1g 1:1.2.8.dfsg-1 file recommends no packages. file 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#757293: libvirt-daemon-system (1.2.7-3) fails to start
Le Thu, 07 Aug 2014 09:24:32 +0200, Laurent Bigonville bi...@debian.org a écrit : Package: libvirt-daemon-system Followup-For: Bug #757293 Hello, MMMh, my bad I guess As the libvirt-bin package has been renamed to libvirt-daemon-system, the preinst script part that stop the daemon cleanly is not executed since libvirt-daemon-system was not installed before... What could be done: - Remove the -nl part of the version comparaison, this will execute the stop and the deb-systemd-helper actions even if the package was not installed before (we need to be sure that d-s-h is not giving us an error if the old service file is inexistant) - Try to guess what is last configured version of libvirt-bin package instead of using the version passed by dpkg - Move (or duplicate) the code in libvirt-bin preinst I'm wondering if with the 2nd and 3rd option we might not run in cases (libvirt-bin being removed at the same time libvirt-daemon-system is being installed) where the stop and d-s-h is not executed as it should (might be wrong here). You probably also want to increase the version in the comparaison to be sure that the deb-systemd-helper actions are properly executed too. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#757326: bug to prevent 1.1.0~alpha from entering jessie
tag 757326 pending thanks On 08/07/2014 10:10 AM, Holger Levsen wrote: I'm filing this bug to prevent lxc 1.1.0~alpha from entering jessie, as this is a development version not suited for production, as stated in it's release announcement at https://lists.linuxcontainers.org/pipermail/lxc-devel/2014-July/009771.html i've already explained that on this bug: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=755165 but i feel there's no point in discussing this, so whatever, i'll upload 1.0.5-1 on the weekend to unstable. -- Address:Daniel Baumann, Donnerbuehlweg 3, CH-3012 Bern Email: daniel.baum...@progress-technologies.net Internet: http://people.progress-technologies.net/~daniel.baumann/ -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#757333: file: buggy magic: strange output for HTML file
Package: file Version: 1:5.19-1+exp1 Severity: normal Dear Maintainer, here is the problem with the attached file: $ file details.html details.html: , init=0x454c, stat=0x4220, dev=0x524f, bas=0x4544 whereas the file looks like correct HTML. -- System Information: Debian Release: jessie/sid APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: i386 (i686) Foreign Architectures: amd64 Kernel: Linux 3.14-2-686-pae (SMP w/2 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages file depends on: ii libc6 2.19-7 ii libmagic1 1:5.19-1+exp1 ii zlib1g 1:1.2.8.dfsg-1 file recommends no packages. file suggests no packages. -- no debconf information details.html.xz Description: application/xz
Bug#757332: libvirt: Obsolete conffile not removed
Source: libvirt Version: 1.2.7-3 Severity: normal Hi, With the latest upgrade, it seems that the 2 following files are still not properly removed: /etc/apparmor.d/libvirtd/TEMPLATE b0dfa704c6297fd9a4e68f0137c6be88 obsolete /etc/apparmor.d/libvirt/TEMPLATE 0d5580a22d95fc622cd5b8efe54b8757 obsolete I see that there is an attempt to remove one of them: rm_conffile /etc/apparmor.d/libvirtd/TEMPLATE 1.2.6-1~ But I guess it's missing the package name at the end as the file was part of libvirt-bin package and not the libvirt-daemon-system one. The version should also probably be bumped to be sure the files are properly removed. Cheers, Laurent Bigonville -- System Information: Debian Release: jessie/sid APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.14-2-amd64 (SMP w/8 CPU cores) Locale: LANG=fr_BE.utf8, LC_CTYPE=fr_BE.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#757207: systemd: Installation of systemd makes system unbootable
forcemerge 757207 756903 thanks Am 07.08.2014 07:38, schrieb Jens Stavnstrup: # /boot was on /dev/sda1 during installation UUID=CS0IM3-x23c-6Iyg-vtLc-NPWI-FuS2-cSFvr8 /boot ext2 Output ofls -la /dev/disk/by-uuid/ == lrwxrwxrwx 1 root root 10 Aug 7 07:30 08cb6482-b013-44a8-8158-3bb41812a7f4 - ../../sda5 lrwxrwxrwx 1 root root 10 Aug 7 07:30 39eb5a09-2859-4891-a22f-ff844891f5cf - ../../dm-1 lrwxrwxrwx 1 root root 10 Aug 7 07:30 da9bc68a-a904-40aa-b8cc-26df3faf5c6d - ../../dm-2 Looks like you have an outdated fstab entry which no longer exists. If such a device is missing, systemd will wait for 90 secs for the device to show up, then drop you into a rescue shell (atm, there is a problem with the emergency shell service, but this is a separate issue). Please remove/fix that mountpoint in your fstab. Merging with existing bug report. -- Why is it that all of the instruments seeking intelligent life in the universe are pointed away from Earth? signature.asc Description: OpenPGP digital signature
Bug#757326: bug to prevent 1.1.0~alpha from entering jessie
Hi Daniel, On Donnerstag, 7. August 2014, Daniel Baumann wrote: but i feel there's no point in discussing this, so whatever, i'll upload 1.0.5-1 on the weekend to unstable. great, thanks already! cheers, Holger signature.asc Description: This is a digitally signed message part.
Bug#739194: blender: Segfaults at startup on armhf
Hi Gunnar! On 2014-03-28 at 19:56 (CET), Gunnar Wolf wrote: Matteo F. Vescovi dijo [Fri, Mar 28, 2014 at 08:47:31AM +0100]: I didn't forget you... the simple answer is that I don't know how to fix this, if there's a fix ;-) Anyhow, given that it's a python-related issue (iirc), could you please test if v2.70 release (now in experimental) changes this still situation? I haven't uploaded it to unstable yet because of libav10 transition, but there are no additional b-deps to build it smoothly compared to v2.69. Let me know something about it; then I can contact some blender upstream devels to dig deeper into this issue, even if they are not so confident with ARM architecture right now ;-P Right, I think that the bug at some point will be reassigned to Python... But I understand about this way less than you do ;-) The package is not yet available on armhf¹ (nor armel, FWIW). I will check again during the weekend. There are many architectures where the build failed, I just hope it succeeds on armhf. Otherwise... Well, I'll try to get the HDD working again to build on something faster than my SD :) ¹ https://buildd.debian.org/status/package.php?p=blendersuite=experimental Now that 2.71+dfsg0-3 builds again on both armel and armhf, could you please test if the issue is still present? Thanks in advance for your time and patience. Cheers. -- Matteo F. Vescovi | Debian Maintainer GnuPG KeyID: 4096R/0x8062398983B2CF7A signature.asc Description: Digital signature
Bug#751550: RFS: aclock.app/0.4.0-1 [ITA]
Paul Wise wrote: On Thu, Aug 7, 2014 at 6:44 AM, Yavor Doganov wrote: Only because they don't exist. It would never occur to me to regenerate an image file that is already in the tarball. We build from source for various reasons, it is no different with graphics: To ensure that your build toolchain still works at all with your sources, you need to rebuild as often as possible. I guess the question here is whether this is part of the build toolchain. For packages like gfpoken it probably is. For aclock.app this is debatable, I think. There is no recipe to render the images from the .blend file. Upstream may have used specific Blender options or some further image manipulation (pngtools, etc). I could actually spoil the images in an attempt to rebuild them. Furthermore, it is possible that the current upstream has no clue at all how to generate the images -- the package was adopted by the GNUstep Application Project as it was abandoned by the original author some time ago. The .blend file and the .png files were imported in the upstream VCS in 2010 together with the whole source and were not modified since then. Personally I would never commit generated files of any kind to my VCS and never allow them to be added to a source tarball (except grudgingly accepting that autotools work that way). This is usually done only for users' convenience and not because of some bad upstream intentions. It is rather annoying if you can't build a program because of some obscure dependency that cannot be installed (or is burdensome to install) for some reason. If there was no .blend file in the tarball and we were unaware of its existence, would it be a DFSG violation? If we had reason to believe that the PNG images were not the preferred form for modification and that upstream was hiding their preferred form for modification and only releasing the rendered images, then yes I believe that is a DFSG violation. I agree. My question was would be a violation if there was no ironclad way to determine what is the preferred form for modification. BTW, there is no need to depend on Inkscape to render SVG files as there are other smaller renderers. Likewise for XCF files since xcftools exists. Thanks, I didn't know that. Only one package build-depends on xcftools which again suggests that currently it is not a common practice in Debian to regenerate images from source. If you want to change that you have to enforce it somehow via Policy or at least document it as a recommended practice. That's all I wanted to say. I wrote some best practices for upstreams about choosing the best preferred form for modification. Thanks, that's very useful, especially for people like me who have little to no knowledge about image/sound creation/manipulation. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#757335: postgresql-debversion: No package for postgresql 9.4
Source: postgresql-debversion Version: 1.0.7-3 Severity: serious X-Debbugs-Cc: pkg-postgresql-pub...@lists.alioth.debian.org [ CCed the PostgreSQL maintainers as I remembering them updating other extensions. ] The default version for PostgreSQL in Jessie is 9.4, but the debversion extension is only available for version 9.3. Ansgar -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#757308: grass: Please update to use wxpython3.0
Hi Olly, On 08/07/2014 06:56 AM, Olly Betts wrote: It looks like grass 7.0.0 will be compatible with wxPython 3.0 - I see in http://trac.osgeo.org/grass/wiki/Release/7.0.0beta-News the entry: | wxPython 3 compatibility fixes So updating the package to this version seems the simplest fix. In theory this is a good idea. But updating from grass 6.4.3 to 7.0.0 will require a transition, which we are unlikely to get in shape before the freeze in November. Updating from grass 6.4.3 to 6.4.4 is more in the realm of possibilities, so we'll need to look into backporting the wxPython 3.0 changes to that. Kind Regards, Bas -- GPG Key ID: 4096R/E88D4AF1 Fingerprint: 8182 DE41 7056 408D 6146 50D1 6750 F10A E88D 4AF1 -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#757336: file: crash on some HTML file (invalid use of free())
Package: file Version: 1:5.19-1+exp1 Severity: important Dear Maintainer, here is how to reproduce the problem: 1. install the diveintopython package 2. set the following environment variables: export MALLOC_CHECK_=3 export MALLOC_PERTURB_=117 3. run file: $ file /usr/share/doc/diveintopython/html/soap_web_services/index.html *** Error in `file': free(): invalid pointer: 0x09abdb60 *** === Backtrace: = /lib/i386-linux-gnu/i686/cmov/libc.so.6[0x410901f3] /lib/i386-linux-gnu/i686/cmov/libc.so.6[0x4109626a] /lib/i386-linux-gnu/i686/cmov/libc.so.6(cfree+0x9b)[0x41099c0b] /lib/i386-linux-gnu/i686/cmov/libc.so.6[0x410e51b9] /lib/i386-linux-gnu/i686/cmov/libc.so.6[0x410ec409] /lib/i386-linux-gnu/i686/cmov/libc.so.6(regexec+0x9c)[0x410f0dac] /usr/lib/i386-linux-gnu/libmagic.so.1(+0x106a6)[0xb76ca6a6] /usr/lib/i386-linux-gnu/libmagic.so.1(+0x9f35)[0xb76c3f35] /usr/lib/i386-linux-gnu/libmagic.so.1(+0xc32d)[0xb76c632d] /usr/lib/i386-linux-gnu/libmagic.so.1(+0xaefd)[0xb76c4efd] /usr/lib/i386-linux-gnu/libmagic.so.1(+0xfffd)[0xb76c9ffd] /usr/lib/i386-linux-gnu/libmagic.so.1(+0x4533)[0xb76be533] file[0x80499ae] file[0x8049093] /lib/i386-linux-gnu/i686/cmov/libc.so.6(__libc_start_main+0xf3)[0x4103ca63] file[0x80495e5] === Memory map: 08048000-0804b000 r-xp 09:00 787334 /usr/bin/file 0804b000-0804c000 r--p 2000 09:00 787334 /usr/bin/file 0804c000-0804d000 rw-p 3000 09:00 787334 /usr/bin/file 09a97000-09ade000 rw-p 00:00 0 [heap] 4100-4101f000 r-xp 09:00 2361652/lib/i386-linux-gnu/ld-2.19.so 4101f000-4102 r--p 0001f000 09:00 2361652/lib/i386-linux-gnu/ld-2.19.so 4102-41021000 rw-p 0002 09:00 2361652/lib/i386-linux-gnu/ld-2.19.so 41023000-411c8000 r-xp 09:00 2361840 /lib/i386-linux-gnu/i686/cmov/libc-2.19.so 411c8000-411ca000 r--p 001a5000 09:00 2361840 /lib/i386-linux-gnu/i686/cmov/libc-2.19.so 411ca000-411cb000 rw-p 001a7000 09:00 2361840 /lib/i386-linux-gnu/i686/cmov/libc-2.19.so 411cb000-411ce000 rw-p 00:00 0 4149-414ac000 r-xp 09:00 2362495 /lib/i386-linux-gnu/libgcc_s.so.1 414ac000-414ad000 rw-p 0001b000 09:00 2362495 /lib/i386-linux-gnu/libgcc_s.so.1 b71e1000-b749f000 rw-p 09:00 2228996 /usr/lib/i386-linux-gnu/file/magic.mgc b749f000-b769f000 r--p 09:00 787558 /usr/lib/locale/locale-archive b769f000-b76a1000 rw-p 00:00 0 b76a1000-b76b8000 r-xp 09:00 2361743 /lib/i386-linux-gnu/libz.so.1.2.8 b76b8000-b76b9000 r--p 00016000 09:00 2361743 /lib/i386-linux-gnu/libz.so.1.2.8 b76b9000-b76ba000 rw-p 00017000 09:00 2361743 /lib/i386-linux-gnu/libz.so.1.2.8 b76ba000-b76d9000 r-xp 09:00 2228896 /usr/lib/i386-linux-gnu/libmagic.so.1.0.0 b76d9000-b76da000 r--p 0001f000 09:00 2228896 /usr/lib/i386-linux-gnu/libmagic.so.1.0.0 b76da000-b76db000 rw-p 0002 09:00 2228896 /usr/lib/i386-linux-gnu/libmagic.so.1.0.0 b771c000-b771e000 rw-p 00:00 0 b771e000-b7725000 r--s 09:00 2365123 /usr/lib/i386-linux-gnu/gconv/gconv-modules.cache b7725000-b7727000 r--p 001ff000 09:00 787558 /usr/lib/locale/locale-archive b7727000-b7729000 rw-p 00:00 0 b7729000-b772a000 r-xp 00:00 0 [vdso] bfb03000-bfb24000 rw-p 00:00 0 [stack] /usr/share/doc/diveintopython/html/soap_web_services/index.html: Aborted -- System Information: Debian Release: jessie/sid APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: i386 (i686) Foreign Architectures: amd64 Kernel: Linux 3.14-2-686-pae (SMP w/2 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages file depends on: ii libc6 2.19-7 ii libmagic1 1:5.19-1+exp1 ii zlib1g 1:1.2.8.dfsg-1 file recommends no packages. file 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#756375: After upgrade systemd-* to 208-7, I still have this problem
After upgrade systemd-* to 208-7, I still have this problem. Please help, thank you. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#756375: After upgrade systemd-* to 208-7, I still have this problem
Am 07.08.2014 11:00, schrieb johnw: After upgrade systemd-* to 208-7, I still have this problem. Please help, thank you. Have you tried uninstalling/purging the ulatencyd package? -- Why is it that all of the instruments seeking intelligent life in the universe are pointed away from Earth? signature.asc Description: OpenPGP digital signature
Bug#757338: buggy magic: mistakes HTML as LaTeX
Package: file Version: 1:5.19-1+exp1 Severity: normal Dear Maintainer, the problem occurs with many files from Debian packages: /usr/share/doc/doxygen/html/faq.html: LaTeX document, ASCII text, with very long lines /usr/share/doc/latex2html/html/Enode13_ct.html: LaTeX document, ASCII text /usr/share/doc/latex2html/html/Enode15_ct.html: LaTeX document, ASCII text /usr/share/doc/latex2html/html/Enode7_ct.html:LaTeX document, ASCII text /usr/share/doc/latex2html/html/Enode9_ct.html:LaTeX document, ASCII text /usr/share/doc/latex2html/html/Hnode10_ct.html: LaTeX document, ASCII text /usr/share/doc/latex2html/html/Hnode12_ct.html: LaTeX 2e document, ASCII text /usr/share/doc/latex2html/html/Hnode4_ct.html:LaTeX document, ASCII text /usr/share/doc/texlive-doc/etex/base/etex_ref.html: LaTeX document, ASCII text /usr/share/doc/texlive-doc/latex/bosisio/envmath.html: LaTeX document, ASCII text /usr/share/doc/texlive-doc/latex/exam-n/release-notes.html: LaTeX document, UTF-8 Unicode text /usr/share/doc/texlive-doc/latex/tablor/tablor.html: LaTeX document, ASCII text, with very long lines /usr/share/doc/source-highlight/test.java.tex.html: LaTeX 2e document, ASCII text, with very long lines /usr/share/doc/xfig/html/latex_and_xfig.html: LaTeX document, ASCII text, with CRLF line terminators /usr/share/doc/xfig/html/japanese/latex_and_xfig.html: LaTeX document, ISO-8859 text, with CRLF line terminators [and probably many others...] whereas those files are HTML with some LaTeX inside. -- System Information: Debian Release: jessie/sid APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: i386 (i686) Foreign Architectures: amd64 Kernel: Linux 3.14-2-686-pae (SMP w/2 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages file depends on: ii libc6 2.19-7 ii libmagic1 1:5.19-1+exp1 ii zlib1g 1:1.2.8.dfsg-1 file recommends no packages. file 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#756375: After upgrade systemd-* to 208-7, I still have this problem
On 08/07/2014 05:07 PM, Michael Biebl wrote: Am 07.08.2014 11:00, schrieb johnw: After upgrade systemd-* to 208-7, I still have this problem. Please help, thank you. Have you tried uninstalling/purging the ulatencyd package? Yes, I already tried dpkg --purge ulatency ulatencyd, then rm -rf /etc/ulatencyd/ then install ulatencyd again. but unfortunately, it did not help. (I also tried add 3 lines to /etc/systemd/system.conf) DefaultControllers= JoinControllers= Controllers= Thank you. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#756375: ulatencyd conflicts with default systemd configuration
clone 756375 -1 reassign -1 ulatency retitle -1 ulatencyd conflicts with default systemd configuration found -1 0.5.0-9 thanks Am 07.08.2014 11:07, schrieb Michael Biebl: Am 07.08.2014 11:00, schrieb johnw: After upgrade systemd-* to 208-7, I still have this problem. Please help, thank you. Have you tried uninstalling/purging the ulatencyd package? Or tried the instructions at [1] 4 Does it work with systemd Since Version 0.4.5 ulatencyd works with systemd under two conditions: DefaultControllers should be unset. In /etc/systemd/system.conf set DefaultControllers= JoinControllers should be unset. In /etc/systemd/system.conf set JoinControllers= The PAM-systemd module should be disabled, or set controllers= Both options would cause constant moving of processes as the layout of systemd and ulatencyd (in the default configuration) differs. Disabling the pam module will break a lot of functionality modern desktops require, so we can certainly not ship that in Debian as default configuration for systemd. I guess there is not a lot we can do about this in the systemd package. We could add a Conflicts: ulatencyd to make sure the package is not installed. But given that systemd will be the default init system for Jessie, this will make the ulatencyd package mostly useless. Maybe the ulatencyd package should ship the service as disabled by default. With clear instructions how to enable it under systemd and what consequences that has. In any case, bringing the ulatencyd package maintainer into the loop here and clonging the bug. Michael [1] https://github.com/poelzi/ulatencyd/wiki/Faq#does-it-work-with-systemd -- Why is it that all of the instruments seeking intelligent life in the universe are pointed away from Earth? signature.asc Description: OpenPGP digital signature
Bug#756375: After upgrade systemd-* to 208-7, I still have this problem
Am 07.08.2014 11:12, schrieb johnw: On 08/07/2014 05:07 PM, Michael Biebl wrote: Am 07.08.2014 11:00, schrieb johnw: After upgrade systemd-* to 208-7, I still have this problem. Please help, thank you. Have you tried uninstalling/purging the ulatencyd package? Yes, I already tried dpkg --purge ulatency ulatencyd, then rm -rf /etc/ulatencyd/ then install ulatencyd again. but unfortunately, it did not help. (I also tried add 3 lines to /etc/systemd/system.conf) DefaultControllers= JoinControllers= Controllers= Thank you. Uninstalling and re-installing obviously has no effect. The instructions I linked also mention that you need to disable the pam_systemd PAM module. Have you done that? Keep in mind that this will break a lot of stuff under systemd, though. Btw, why do you need ulatencyd at all? -- Why is it that all of the instruments seeking intelligent life in the universe are pointed away from Earth? signature.asc Description: OpenPGP digital signature
Bug#757319: libapache2-mod-perl2: FTBFS on kfreebsd: ModPerl-Registry/ test failures
On Thu, Aug 07, 2014 at 10:03:15AM +0300, Niko Tyni wrote:
Package: libapache2-mod-perl2
Version: 2.0.8+httpd24-r1449661-9
Severity: serious
This package fails to build on kfreebsd-{amd64,i386}, in the
ModPerl-Registry test suite, but in different places.
On kfreebsd-i386:
# Failed test 1 in t/closure.t at line 43
t/closure.t
Failed 1/6 subtests
On kfreebsd-amd64:
# Failed test 7 in t/special_blocks.t at line 123
t/special_blocks.t .
Failed 1/12 subtests
This is probably another gcc-4.9 problem. Will investigate.
I can't reproduce either of these on fischer/falla. I've been
running the relevant tests in a loop for over an hour or so
without a single failure.
Buildd maintainers: could you please schedule them for a retry
so we see if it's deterministic on the buildds?
--
Niko Tyni nt...@debian.org
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#757341: ulatencyd conflicts with default systemd configuration
Package: ulatency Version: 0.5.0-9 Severity: important User: pkg-systemd-maintain...@lists.alioth.debian.org Usertags: integration Please see #756375 and related bug reports: Am 07.08.2014 11:07, schrieb Michael Biebl: Am 07.08.2014 11:00, schrieb johnw: After upgrade systemd-* to 208-7, I still have this problem. Please help, thank you. Have you tried uninstalling/purging the ulatencyd package? Or tried the instructions at [1] 4 Does it work with systemd Since Version 0.4.5 ulatencyd works with systemd under two conditions: DefaultControllers should be unset. In /etc/systemd/system.conf set DefaultControllers= JoinControllers should be unset. In /etc/systemd/system.conf set JoinControllers= The PAM-systemd module should be disabled, or set controllers= Both options would cause constant moving of processes as the layout of systemd and ulatencyd (in the default configuration) differs. Disabling the pam module will break a lot of functionality modern desktops require, so we can certainly not ship that in Debian as default configuration for systemd. I guess there is not a lot we can do about this in the systemd package. We could add a Conflicts: ulatencyd to make sure the package is not installed. But given that systemd will be the default init system for Jessie, this will make the ulatencyd package mostly useless. Maybe the ulatencyd package should ship the service as disabled by default. With clear instructions how to enable it under systemd and what consequences that has. In any case, bringing the ulatencyd package maintainer into the loop here and clonging the bug. Michael [1] https://github.com/poelzi/ulatencyd/wiki/Faq#does-it-work-with-systemd -- System Information: Debian Release: jessie/sid APT prefers unstable APT policy: (500, 'unstable'), (200, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.14-2-amd64 (SMP w/4 CPU cores) Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#757336: file: crash on some HTML file (invalid use of free())
tags 757336 confirmed thanks LB wrote... here is how to reproduce the problem: Thanks for that. For the records, the file's md5sum is bc58c8203c1eaed6ee9e67178886451a $ file /usr/share/doc/diveintopython/html/soap_web_services/index.html A first check reveals this was introduced between file 5.18 and file 5.19, therefore: squeeze (oldstable), wheezy (stable): Not affected jessie (testing), sid (unstable), rc-buggy (experimental): AFFECTED More later, Christoph -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#601011: any update?
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi, this bug is still valid with debbotstrap 1.0.48+deb7u1 is there any chance that this patch will be introduced or denied? Cheers B -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.22 (MingW32) Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iEUEARECAAYFAlPjSI0ACgkQABMWRpwdNumyIQCfYjyzmarFY8hC6sd1wYF6XJGu 1P0AmOyxYL1/IJXYusxVpHMFYN3sslI= =8zIr -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#756375: After upgrade systemd-* to 208-7, I still have this problem
On 08/07/2014 05:21 PM, Michael Biebl wrote: Uninstalling and re-installing obviously has no effect. Oh, you mean is uninstall/remove ulatencyd (not reinstall), Yes, I did it, and can solve the problem. But I want ulatencyd. The instructions I linked also mention that you need to disable the pam_systemd PAM module. Have you done that? Keep in mind that this will break a lot of stuff under systemd, though. The FAQ say add those line OR disable PAM. https://github.com/poelzi/ulatencyd/wiki/Faq#id4 I also tried diable pam_system PAM module, but did not help. and it will break the shutdown behavior. (when I click the shutdown button, it just logout, not try to shutdown) Btw, why do you need ulatencyd at all? Because I feel it can make more smooth on my desktop. (Yes, I really can feel it) Anyway, I would remove ulatenyd, If this is know issues and can not be solve. I would close this bug report, if you agree. (Because this is know issues and can not be solve) Thank you. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#756895: Ugrade 1.13 - 1.14 fails
On Sun, 3 Aug 2014 15:19:11 +0100 Edward Betts edw...@4angle.com wrote: The subject says 1.13 - 1.14, but 1.14 isn't in Debian. I had exactly the same error (Duplicate column name 'width') when I did the 1.12-1.13 update. I had to remove the column and replay the update (I think I had to also do changes to the tt-rss config) to finish the update. BTW, I was also the one who reported https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=724292 I seem to fail each update... -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#757289: stimfit: Please update to use wxwidgets3.0
Thanks for the patch. Note that we've just released 0.13.18-1:
https://packages.debian.org/sid/stimfit
It would be good to apply your patch upstream, but I was wondering how
your build-depends line would affect packaging for older releases
(wheezy and precise)? Is there a way to make this compatible across
releases?
On Thu, Aug 07, 2014 at 10:51:22AM +1200, Olly Betts wrote:
Package: stimfit
Version: 0.13.15-1
Severity: important
Tags: patch
Tags: sid jessie
User: freewx-ma...@lists.alioth.debian.org
Usertags: wx3.0 wxpy3.0
Control: block 748169 by -1
Control: block 755757 by -1
We're aiming to migrate the archive to using wxwidgets3.0/wxpython3.0
instead of wxwidgets2.8, and hope to drop wxwidgets2.8 before jessie
is released.
Upstream, stimfit supports wx3.0, but it looks like there's a problem
with this support under wxGTK - when __WXGTK__ is defined,
src/stimfit/gui/app.cpp calls:
wxMenuBar* menu_bar = CreateUnifiedMenuBar();
This defaults the doc parameter to NULL, and if wxCHECK_VERSION(2, 9, 0)
is true (which it is for wx = 2.9.0) we then try to call a method on
doc, which segfaults:
((wxStfDoc*)doc)-SetFileMenu( file_menu );
I've added a simple fix for this, though it may not be the best way to
address this. But with the patch, I can run stimfit, and it starts up
OK and I can open a few dialogs. I don't have suitable data to actually
test much functionality though.
I'm happy to NMU this change if you wish me to - just let me know.
Cheers,
Olly
diff -Nru stimfit-0.13.15/debian/changelog stimfit-0.13.15/debian/changelog
--- stimfit-0.13.15/debian/changelog 2014-02-17 02:23:17.0 +1300
+++ stimfit-0.13.15/debian/changelog 2014-08-07 09:42:21.0 +1200
@@ -1,3 +1,10 @@
+stimfit (0.13.15-1.1) unstable; urgency=medium
+
+ * Non-maintainer upload.
+ * Update to use wxWidgets 3.0 - new patch: wx3.0-compat.patch
+
+ -- Olly Betts o...@survex.com Thu, 07 Aug 2014 09:42:05 +1200
+
stimfit (0.13.15-1) unstable; urgency=low
* Fix half duration limits bug
diff -Nru stimfit-0.13.15/debian/control stimfit-0.13.15/debian/control
--- stimfit-0.13.15/debian/control2014-02-17 02:23:17.0 +1300
+++ stimfit-0.13.15/debian/control2014-08-07 09:14:27.0 +1200
@@ -3,13 +3,13 @@
Priority: optional
Maintainer: Christoph Schmidt-Hieber chris...@gmx.de
Uploaders: Yaroslav Halchenko deb...@onerussian.com
-Build-Depends: debhelper (= 7), libboost-dev (= 1.40.0), python-all-dev
(= 2.6.6-3), python-numpy, libhdf5-dev, swig, python-wxgtk2.8 (= 2.8.9),
libwxgtk2.8-dev (= 2.8.9), libfftw3-dev, liblapack-dev, chrpath, help2man,
libbiosig-dev, libsuitesparse-dev, dh-autoreconf
+Build-Depends: debhelper (= 7), libboost-dev (= 1.40.0), python-all-dev
(= 2.6.6-3), python-numpy, libhdf5-dev, swig, python-wxgtk3.0,
python-wxgtk3.0-dev, libwxgtk3.0-dev, libfftw3-dev, liblapack-dev, chrpath,
help2man, libbiosig-dev, libsuitesparse-dev, dh-autoreconf
Standards-Version: 3.9.4
Homepage: http://www.stimfit.org
Package: stimfit
Architecture: any
-Depends: ${shlibs:Depends}, ${misc:Depends}, ${python:Depends},
libbiosig-dev, libsuitesparse-dev, python-wxgtk2.8 (= 2.8.9), python-numpy,
python-matplotlib
+Depends: ${shlibs:Depends}, ${misc:Depends}, ${python:Depends},
libbiosig-dev, libsuitesparse-dev, python-wxgtk3.0, python-numpy,
python-matplotlib
Recommends: python-scipy
Description: Program for viewing and analyzing electrophysiological data
Stimfit is a free, fast and simple program for viewing and analyzing
diff -Nru stimfit-0.13.15/debian/patches/series
stimfit-0.13.15/debian/patches/series
--- stimfit-0.13.15/debian/patches/series 1970-01-01 12:00:00.0
+1200
+++ stimfit-0.13.15/debian/patches/series 2014-08-07 09:39:02.0
+1200
@@ -0,0 +1 @@
+wx3.0-compat.patch
diff -Nru stimfit-0.13.15/debian/patches/wx3.0-compat.patch
stimfit-0.13.15/debian/patches/wx3.0-compat.patch
--- stimfit-0.13.15/debian/patches/wx3.0-compat.patch 1970-01-01
12:00:00.0 +1200
+++ stimfit-0.13.15/debian/patches/wx3.0-compat.patch 2014-08-07
09:42:00.0 +1200
@@ -0,0 +1,22 @@
+Description: Fix build with wx3.0 under __WXGTK__
+ While stimfit has been ported to wx3.0, it seems this hasn't been tested
+ under __WXGTK__ as there doc is always NULL in
wxStfApp::CreateUnifiedMenuBar
+ but we try to call methods on it for wx = 2.9.0.
+ .
+ I don't understand the reason for all the conditionalisation on __WXGTK__,
+ __WXMSW__ etc, so this may not be the best fix, but it seems to work.
+Author: Olly Betts o...@survex.com
+Forwarded: no
+Last-Update: 2014-08-06
+
+--- stimfit-0.13.15.orig/src/stimfit/gui/app.cpp
stimfit-0.13.15/src/stimfit/gui/app.cpp
+@@ -605,7 +605,7 @@ wxMenuBar *wxStfApp::CreateUnifiedMenuBa
+ file_menu-AppendSeparator();
+ file_menu-Append(wxID_EXIT);
+
+-#if (wxCHECK_VERSION(2, 9, 0))
++#if
Bug#757343: gamera: inappropriate use of general exceptions
Source: gamera Version: 3.4.1-1 Severity: normal Control: tags -1 upstream The programmers have used several general exceptions without arguments, e.g. that catches also SIGKILL signals from the keyboard when this isn't wanted (thanks to Piotr Ożarowski for the note). Greetings, Daniel Stender -- http://www.danielstender.com/blog/ PGP key: 2048R/E41BD2D0 C879 5E41 1ED7 EE80 0F2E 7D0C DBDD 4D96 E41B D2D0 -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#601011: any update?
Bjoern Boschman bjo...@boschman.de (2014-08-07): -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi, this bug is still valid with debbotstrap 1.0.48+deb7u1 is there any chance that this patch will be introduced or denied? While I haven't tried to reproduce this bug, the patch looks like something that could indeed be merged. Mraw, KiBi. signature.asc Description: Digital signature
Bug#751550: RFS: aclock.app/0.4.0-1 [ITA]
On Thu, Aug 7, 2014 at 4:45 PM, Yavor Doganov wrote: There is no recipe to render the images from the .blend file. ... Furthermore, it is possible that the current upstream has no clue at all how to generate the images This sounds like a problem to me. This is usually done only for users' convenience and not because of some bad upstream intentions. It is rather annoying if you can't build a program because of some obscure dependency that cannot be installed (or is burdensome to install) for some reason. I have the luxury of being a Debian user so I do tend to not worry about that sort of thing any more. I agree. My question was would be a violation if there was no ironclad way to determine what is the preferred form for modification. If we have no indicators we generally assume upstream is releasing the preferred form for modification. Thanks, I didn't know that. Only one package build-depends on xcftools which again suggests that currently it is not a common practice in Debian to regenerate images from source. If you want to change that you have to enforce it somehow via Policy or at least document it as a recommended practice. That's all I wanted to say. Agreed that it is not common practice, sadly. I think we have enough in policy/DFSG to encourage this, we just need people to understand it and actually care about it, which is the hard part. -- bye, pabs https://wiki.debian.org/PaulWise -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#757330: [Pkg-libvirt-maintainers] Bug#757330: libvirt-daemon-system: fails to install: update-rc.d: error: insserv rejected the script header
On Thu, 7 Aug 2014, Guido Günther wrote: Any chance to rerung this with DPKG_DEBUG=1 ? I did an update of a tglase@tglase:~ $ sudo env DPKG_DEBUG=1 dpkg -a --configure [sudo] password for tglase: Setting up libvirt-daemon-system (1.2.7-3) ... insserv: script libvirtd: service libvirt-bin already provided! insserv: exiting now! update-rc.d: error: insserv rejected the script header dpkg: error processing package libvirt-daemon-system (--configure): subprocess installed post-installation script returned error exit status 1 dpkg: dependency problems prevent configuration of libvirt-bin: libvirt-bin depends on libvirt-daemon-system (= 1.2.7-3); however: Package libvirt-daemon-system is not configured yet. dpkg: error processing package libvirt-bin (--configure): dependency problems - leaving unconfigured Errors were encountered while processing: libvirt-daemon-system libvirt-bin sysv based system yesterday without any troubles. Did you modify /etc/init.d/libvirt-bin ? Yes, I did. I added “linux64” before “start-stop-daemon --start […]” since I’m running an amd64 kernel with i386 userland and: tglase@tglase:~ $ cat /sbin/init #!/bin/mksh-static exec /usr/bin/linux32 /sbin/init.real $@ bye, //mira“waiting for the Debian kernel to support x32”bilos -- tarent solutions GmbH Rochusstraße 2-4, D-53123 Bonn • http://www.tarent.de/ Tel: +49 228 54881-393 • Fax: +49 228 54881-235 HRB 5168 (AG Bonn) • USt-ID (VAT): DE122264941 Geschäftsführer: Dr. Stefan Barth, Kai Ebenrett, Boris Esser, Alexander Steeg -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#757344: wheezy-pu: package blender/2.63a-1
Package: release.debian.org
Severity: normal
Tags: wheezy
User: release.debian@packages.debian.org
Usertags: pu
Dear Release Team,
I'd like to upload a new version of Blender to stable/wheezy.
Blender package in wheezy is 2.63a-1 at the moment and doesn't include a
patch that would avoid an illegal hardware instruction failure related
to SSE2 extensions present in newer CPUs, as reported in #599680.
This way, however, every user using a non-SSE2 CPU (e.g., AMD Athlon)
won't be able to run Blender in their wheezy boxes.
That same patch has been applied on packages = 2.66-1 and finally it
has been dropped in latest upstream Blender release 2.71 because there
was found a better (and more elegant) solution to the problem.
I already prepared an update on wheezy package with that patch applied
and it was tested to work fine.
Attached, you'll find this famous patch that should fix the issue.
Thanks for considering.
-- System Information:
Debian Release: jessie/sid
APT prefers unstable
APT policy: (500, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Kernel: Linux 3.14-2-amd64 (SMP w/1 CPU core)
Locale: LANG=C, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
--
Matteo F. Vescovi | Debian Maintainer
GnuPG KeyID: 4096R/0x8062398983B2CF7A
From: Johann Klammer klamm...@a1.net
Date: Wed, 13 Feb 2013 09:04:08 +0100
Subject: fix_illegal_hardware_instruction_due_to_SSE2
This makes sure it builds compatible binaries also on
machines which have sse/sse2. Fixes the SIGILL bug.
Checks for DEB_HOST_ARCH_CPU!=i386 before tests are attempted.
Will try to use SSE/SSE2 on all other architectures.
Generated Code will still need MMX support to run.
Signed-off-by: Matteo F. Vescovi mfvesc...@gmail.com
---
build_files/cmake/macros.cmake | 49 +++---
1 file changed, 27 insertions(+), 22 deletions(-)
diff --git a/build_files/cmake/macros.cmake b/build_files/cmake/macros.cmake
index e4ac326..b172c81 100644
--- a/build_files/cmake/macros.cmake
+++ b/build_files/cmake/macros.cmake
@@ -446,34 +446,39 @@ macro(TEST_SSE_SUPPORT
set(CMAKE_REQUIRED_FLAGS ${${_sse_flags}} ${${_sse2_flags}})
- if(NOT DEFINED SUPPORT_SSE_BUILD)
- # result cached
- check_c_source_runs(
- #include xmmintrin.h
- int main(void) { __m128 v = _mm_setzero_ps(); return 0; }
- SUPPORT_SSE_BUILD)
-
- if(SUPPORT_SSE_BUILD)
- message(STATUS SSE Support: detected.)
- else()
- message(STATUS SSE Support: missing.)
+ if(NOT ( $ENV{DEB_HOST_ARCH_CPU} STREQUAL i386 ) )
+
+ if(NOT DEFINED SUPPORT_SSE_BUILD)
+ # result cached
+ check_c_source_runs(
+#include xmmintrin.h
+int main(void) { __m128 v = _mm_setzero_ps(); return 0; }
+ SUPPORT_SSE_BUILD)
+
+ if(SUPPORT_SSE_BUILD)
+message(STATUS SSE Support: detected.)
+ else()
+message(STATUS SSE Support: missing.)
+ endif()
endif()
- endif()
- if(NOT DEFINED SUPPORT_SSE2_BUILD)
- # result cached
- check_c_source_runs(
+ if(NOT DEFINED SUPPORT_SSE2_BUILD)
+ # result cached
+ check_c_source_runs(
#include emmintrin.h
- int main(void) { __m128d v = _mm_setzero_pd(); return 0; }
- SUPPORT_SSE2_BUILD)
+int main(void) { __m128d v = _mm_setzero_pd(); return 0; }
+ SUPPORT_SSE2_BUILD)
- if(SUPPORT_SSE2_BUILD)
- message(STATUS SSE2 Support: detected.)
- else()
- message(STATUS SSE2 Support: missing.)
+ if(SUPPORT_SSE2_BUILD)
+message(STATUS SSE2 Support: detected.)
+ else()
+message(STATUS SSE2 Support: missing.)
+ endif()
endif()
+ else()
+ message(STATUS SSE Support: missing.)
+ message(STATUS SSE2 Support: missing.)
endif()
-
unset(CMAKE_REQUIRED_FLAGS)
endmacro()
signature.asc
Description: Digital signature
Bug#628748: Forwarded; adding tags
tags 628748 patch tags 628748 upstream forwarded 628748 https://sourceforge.net/p/u3-tool/patches/8/ thanks Hi, 2 of these typos have already been fixed upstream (see #599167). I sent a new patch here: https://sourceforge.net/p/u3-tool/patches/8/ Regards, Carlo
Bug#753426: transition: librevenge
Control: tags -1 confirmed On 06/08/14 11:54, Rene Engelhard wrote: My last planned 4.2.x upload (1:4.2.6-1) is about to migrate this night, so I can fix some copyright files and build LO 1:4.3.0-2 the next days and start the transition. That has migrated now. Feel free to start this. Emilio -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#757289: stimfit: Please update to use wxwidgets3.0
On Thu, Aug 07, 2014 at 10:58:16AM +0100, Christoph Schmidt-Hieber wrote: Thanks for the patch. Note that we've just released 0.13.18-1: https://packages.debian.org/sid/stimfit Oops, sorry I missed that - it must have been uploaded shortly after I pulled down the source. It would be good to apply your patch upstream, but I was wondering how your build-depends line would affect packaging for older releases (wheezy and precise)? Is there a way to make this compatible across releases? For wheezy-backports, wxwidgets3.0 is already backported, and I'm intending to also provide a backport of wxpython3.0 shortly. You can have alternates in Build-Depends, though the buildds will only try to install the first alternative. So you could have something like this which would work for uploads to unstable: Build-Depends: libwxgtk3.0-dev | libwxgtk2.8-dev, python-wxgtk3.0 | python-wxgtk2.8, python-wxgtk3.0-dev | python-wxgtk2.8 This would also allow you to manually install the 2.8 packages and build, but it wouldn't work for uploading to build against 2.8 in wheezy backports, and nothing ensures you get a matching set (e.g. libwxgtk3.0-dev + python-wxgtk2.8 satisfies this). The approach I'd probably take would be keep a version of debian/control with the old BDs as something like debian/control-wx2.8, and then when you want to backport, just copy that over debian/control. Cheers, Olly -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#757346: tortoisehg: toirtoisehg workbench crashes when viewing working directory
Package: tortoisehg Version: 3.0-1 Severity: grave Justification: renders package unusable Dear Maintainer, When opening a repository in TortoiseHg Workbench, I can't see the working directory, I have this bug : #!python ** Mercurial version (3.1). TortoiseHg version (3.0) ** Command: ** CWD: /home/seblca ** Encoding: UTF-8 ** Extensions loaded: graphlog ** Python version: 2.7.8 (default, Jul 26 2014, 15:25:14) [GCC 4.9.1] ** System: Linux plume 3.16-0.slh.1-aptosid-amd64 #1 SMP PREEMPT aptosid 3.16-1 (2014-08-03) x86_64 ** Qt-4.8.6 PyQt-4.11.1 QScintilla-2.8.3 Traceback (most recent call last): File /usr/lib/python2.7/dist-packages/tortoisehg/hgqt/status.py, line 609, in run wctx.status(**stopts) TypeError: status() got an unexpected keyword argument 'unknown' If I downgrade mercurial to testing version (3.0.2-1) it doesn't crash. I've seen that there is a new upstream version for tortoisehg (http://tortoisehg.bitbucket.org/download/source.html) : 3.1 As mercurial is version 3.1 in Sid, the problem might be here. Regards, Sébastien KALT -- System Information: Debian Release: jessie/sid APT prefers unstable APT policy: (980, 'unstable'), (970, 'testing'), (960, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 3.16-0.slh.1-aptosid-amd64 (SMP w/4 CPU cores; PREEMPT) Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages tortoisehg depends on: ii mercurial 3.1-1 ii python 2.7.8-1 ii python-gobject 3.12.1-1 ii python-qscintilla2 2.8.3+dfsg-3 ii python-qt4 4.11.1+dfsg-1 Versions of packages tortoisehg recommends: ii libjs-jquery 1.7.2+dfsg-3 ii libjs-underscore 1.4.4-2 ii python-iniparse 0.4-2.1 ii python-pygments 1.6+dfsg-1 Versions of packages tortoisehg suggests: pn tortoisehg-nautilus 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#757348: systemd: with SysV init, can no longer suspend and shutdown from lightdm
Package: systemd Version: 208-7 Severity: important The systemd upgrade from 204-14 to 208-7 introduced a regression in lightdm: the Suspend, Hibernate, Restart and Shut Down menu items of lightdm are now greyed out (even before the first login). Note: I'm using SysV init. -- Package-specific info: -- System Information: Debian Release: jessie/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing'), (500, 'stable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.11-2-amd64 (SMP w/2 CPU cores) Locale: LANG=POSIX, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages systemd depends on: ii acl 2.2.52-1 ii adduser 3.113+nmu3 ii initscripts 2.88dsf-53.3 ii libacl1 2.2.52-1 ii libaudit11:2.3.7-1 ii libblkid12.20.1-5.8 ii libc62.19-7 ii libcap2 1:2.24-4 ii libcap2-bin 1:2.24-4 ii libcryptsetup4 2:1.6.4-4 ii libdbus-1-3 1.8.6-1 ii libgcrypt11 1.5.3-5 ii libkmod2 18-1 ii liblzma5 5.1.1alpha+20120614-2 ii libpam0g 1.1.8-3 ii libselinux1 2.3-1 ii libsystemd-daemon0 208-7 ii libsystemd-journal0 208-7 ii libsystemd-login0208-7 ii libudev1 208-7 ii libwrap0 7.6.q-25 ii sysv-rc 2.88dsf-53.3 ii udev 208-7 ii util-linux 2.20.1-5.8 Versions of packages systemd recommends: ii libpam-systemd 208-7 Versions of packages systemd suggests: pn systemd-ui none -- Configuration Files: /etc/systemd/logind.conf changed: [Login] HandlePowerKey=ignore -- debconf-show failed -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#757347: livestreamer: ustream plugin problem
Package: livestreamer
Version: 1.9.0-1
Severity: normal
Dear Maintainer,
This works:
livestreamer http://www.ustream.tv/nasahdtv best
But this does not works:
livestreamer http://www.ustream.tv/cbsnews best
[cli][info] Found matching plugin ustreamtv for URL
http://www.ustream.tv/cbsnews
[plugin.ustreamtv][error] Unable to fetch desktop streams: Unable to validate
result: Unable to validate key 'stream': Unable to validate key 'streams': Key
'chunkRange' not found in {u'streamName': u'CBSnews2_live_800@50979',
u'streamId': u'199585473'} or [{u'url':
u'rtmp://cp56371.live.edgefcs.net/live/', u'needSubscribe': True, u'streams':
[{u'streamName': u'CBSnews2_live_800@50979', u'streamId': u'199585473'}],
u'name': u'akamai'}] does not equal 'offline'
error: No streams found on this URL: http://www.ustream.tv/cbsnews
-- System Information:
Debian Release: jessie/sid
APT prefers unstable
APT policy: (500, 'unstable'), (500, 'testing'), (500, 'stable'), (1,
'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 3.14-2-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_US.utf8, LC_CTYPE=ru_RU.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Versions of packages livestreamer depends on:
ii python-livestreamer 1.9.0-1
pn python:any none
livestreamer recommends no packages.
Versions of packages livestreamer suggests:
pn python-livestreamer-doc 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#757348: systemd: with SysV init, can no longer suspend and shutdown from lightdm
reassign 757348 systemd-shim thanks Am 07.08.2014 13:03, schrieb Vincent Lefevre: Package: systemd Version: 208-7 Severity: important The systemd upgrade from 204-14 to 208-7 introduced a regression in lightdm: the Suspend, Hibernate, Restart and Shut Down menu items of lightdm are now greyed out (even before the first login). Note: I'm using SysV init. Re-assigning to systemd-shim then, since that is used when sysvinit is used. -- Why is it that all of the instruments seeking intelligent life in the universe are pointed away from Earth? signature.asc Description: OpenPGP digital signature
Bug#751550: RFS: aclock.app/0.4.0-1 [ITA]
Paul Wise wrote: On Thu, Aug 7, 2014 at 4:45 PM, Yavor Doganov wrote: Furthermore, it is possible that the current upstream has no clue at all how to generate the images This sounds like a problem to me. Why? It is quite possible that they would never have to be modified for the entire lifetime of the package. As long as the possibility to do so exists and the DFSG requirements are met, I don't see a problem. This is usually done only for users' convenience I have the luxury of being a Debian user so I do tend to not worry about that sort of thing any more. I was only explaining why it is relevant for many upstream developers. If you are upstream you should not assume that all your users have this luxury. Even for Debian users it can be tedious -- there are slow architectures and there are fast architectures that happen to have slow machines which are still in wide use. Only one package build-depends on xcftools which again suggests that currently it is not a common practice in Debian to regenerate images from source. Agreed that it is not common practice, sadly. I think we have enough in policy/DFSG to encourage this, we just need people to understand it and actually care about it, which is the hard part. I could be mistaken, but Policy/DFSG does not mention anything of that kind, not even for .mo/.info/.pdf/autotools files, let alone images. The presence of the source is required, which is pretty much understandable and how it should be. The rest is just one possible interpretation, whether correct or not. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#756989: t/apr-ext failures at gcc -O0
Hi,
we're seeing t/apr-ext failures when building without optimization on
current Debian unstable (Apache 2.4.10, Perl 5.18.2). An example is
t/apr-ext/base64.t .. Can't load
'/home/niko/tmp/libapache2-mod-perl2/blib/arch/auto/APR/APR.so' for module APR:
/home/niko/tmp/libapache2-mod-perl2/blib/arch/auto/APR/APR.so: undefined
symbol: perl_module at /usr/lib/perl/5.18/DynaLoader.pm line 184.
at /home/niko/tmp/libapache2-mod-perl2/blib/lib/APR/Base64.pm line 23.
Compilation failed in require at
/home/niko/tmp/libapache2-mod-perl2/blib/lib/APR/Base64.pm line 23.
BEGIN failed--compilation aborted at
/home/niko/tmp/libapache2-mod-perl2/blib/lib/APR/Base64.pm line 23.
Compilation failed in require at
/home/niko/tmp/libapache2-mod-perl2/t/lib/TestAPRlib/base64.pm line 12.
BEGIN failed--compilation aborted at
/home/niko/tmp/libapache2-mod-perl2/t/lib/TestAPRlib/base64.pm line 12.
Compilation failed in require at t/apr-ext/base64.t line 8.
BEGIN failed--compilation aborted at t/apr-ext/base64.t line 8.
t/apr-ext/base64.t .. Dubious, test returned 2 (wstat
512, 0x200)
No subtests run
It looks like APR.so can only be loaded from inside mod_perl:
% perl -Iblib/lib -Iblib/arch -MAPR -e1
Can't load 'blib/arch/auto/APR/APR.so' for module APR:
blib/arch/auto/APR/APR.so: undefined symbol: perl_module
at /usr/lib/perl/5.18/DynaLoader.pm line 184.
at -e line 0.
Compilation failed in require.
BEGIN failed--compilation aborted.
The problem comes from src/modules/perl/modperl_apache_includes.h:
#if !defined(MP_IN_XS) AP_MODULE_MAGIC_AT_LEAST(20100606, 0)
APLOG_USE_MODULE(perl);
#endif
where APLOG_USE_MODULE(perl) expands via /usr/include/apache2/http_config.h to
extern module perl_module; static int * const aplog_module_index =
(perl_module.module_index);
At -O2, this is optimized away when it's not used, but -O0 keeps it.
The MP_IN_XS guard looks promising; defining that for the APR (and
APR/PerlIO) build seems to help. I was able to get the test suite pass
at both -O0 and -O2 with the attached patch.
It seems possible that other parts of xs/ are affected too but aren't
exercised by the test suite.
The history of MP_IN_XS usage is just
http://svn.apache.org/viewvc?view=revisionrevision=1410295
http://svn.apache.org/viewvc?view=revisionrevision=68792
but it looks like a correct solution to me. Does that make sense?
I'm attaching a patch that modifies the Makefile.PL files accordingly.
I expect there are other ways to accomplish the same thing too.
This is also https://bugs.debian.org/756989 (cc'd).
--
Niko Tyni nt...@debian.org
From 91c69a8df6d63c2bea0377e59e7b58a81d60f607 Mon Sep 17 00:00:00 2001
From: Niko Tyni nt...@debian.org
Date: Mon, 4 Aug 2014 10:32:36 +0300
Subject: [PATCH] Define MP_IN_XS to avoid referencing perl_module outside of
mod_perl
APLOG_USE_MODULE(perl) expands to
extern module perl_module; static int * const aplog_module_index = (perl_module.module_index);
which makes loading APR.so impossible outside mod_perl unless
aplog_module_index is optimized away by the compiler.
This causes mod_perl test suite failures in t/apr-ext at gcc -O0.
See also
http://svn.apache.org/viewvc?view=revisionrevision=68792
http://svn.apache.org/viewvc?view=revisionrevision=1410295
Bug-Debian: https://bugs.debian.org/756989
---
xs/APR/APR/Makefile.PL| 7 +++
xs/APR/PerlIO/Makefile.PL | 3 +++
2 files changed, 10 insertions(+)
diff --git a/xs/APR/APR/Makefile.PL b/xs/APR/APR/Makefile.PL
index 8745a54..d569dde 100644
--- a/xs/APR/APR/Makefile.PL
+++ b/xs/APR/APR/Makefile.PL
@@ -25,6 +25,13 @@ $libs = delete $args{LIBS} if $args{LIBS};
my $build = ModPerl::BuildMM::build_config();
+my $ccopts = $build-ccopts;
+
+# avoid referencing perl_module outside of mod_perl
+$ccopts .= ' -DMP_IN_XS';
+
+$args{CCFLAGS} = $ccopts;
+
my @apru_link_flags = $build-apru_link_flags;
$libs .= join ' ', @apru_link_flags if @apru_link_flags;
diff --git a/xs/APR/PerlIO/Makefile.PL b/xs/APR/PerlIO/Makefile.PL
index 4a8f60d..ca102bb 100644
--- a/xs/APR/PerlIO/Makefile.PL
+++ b/xs/APR/PerlIO/Makefile.PL
@@ -25,6 +25,9 @@ if ($build-has_large_files_conflict) {
: '';
}
+# avoid referencing perl_module outside of mod_perl
+$ccopts .= ' -DMP_IN_XS';
+
ModPerl::BuildMM::WriteMakefile(
NAME = 'APR::PerlIO',
VERSION_FROM = 'PerlIO.pm',
--
2.0.1
Bug#757352: /etc/bash_completion.d/nikola contains /home/tin/projects/debian/nikola/nikola.git/nikola as first line
Package: nikola Version: 7.0.1-2 File /etc/bash_completion.d/nikola contains /home/tin/projects/debian/nikola/nikola.git/nikola as first line, which it probably shouldn't. Regards, Vedran -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#757353: denyhosts: dh_reenable matches on substrings. To many IPs removed.
Package: denyhosts Version: 2.6-10+deb7u3 Severity: normal Dear Maintainer, dh_reenable removes any IP (eg. 201.1.1.123) that contains the given IP (e.g 1.1.1.1). As a result many IPs might be removed from the blacklist unintentionally. cat /var/lib/denyhosts/hosts 10.1.100.80:0:Mon Jun 24 11:15:21 2013 110.1.100.70:0:Mon Jun 24 11:15:21 2013 210.1.100.71:0:Mon Jun 24 11:15:21 2013 10.1.100.81:0:Mon Jun 24 11:15:21 2013 /usr/share/denyhosts/DenyHosts/dh_reenable 10.1.100.7 Done! Please restart denyhosts /etc/init.d/denyhosts restart [ ok ] Stopping DenyHosts: denyhosts. [ ok ] Starting DenyHosts: denyhosts. # No IP should be removed cat /var/lib/denyhosts/hosts 10.1.100.80:0:Mon Jun 24 11:15:21 2013 10.1.100.81:0:Mon Jun 24 11:15:21 2013 # These IPs should not be removed: # 110.1.100.70:0:Mon Jun 24 11:15:21 2013 # 210.1.100.71:0:Mon Jun 24 11:15:21 2013 This Bug is also present in squeeze. System Information: Debian Release: 7.6 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.2.0-4-amd64 (SMP w/2 CPU cores) Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968) Shell: /bin/sh linked to /bin/dash Versions of packages denyhosts depends on: ii lsb-base 4.1+Debian8+deb7u1 ii python2.7.3-4+deb7u1 denyhosts recommends no packages. denyhosts suggests no packages. -- no debconf information
Bug#757354: ITP: flintqs -- Program using quadratic sieve to factor integers
Package: wnpp Severity: wishlist * Package name: flintqs Version: 20070817 Upstream author: William Hart * URL: http://www.sagemath.org/packages/upstream/flintqs/index.html * License: GPL-2+ Description: Program using quadratic sieve to factor integers This small program attempts to find prime factors of large primes (at least forty digits). The motivation for its packaging is that it's a standard package in the sagemath software suite. Snark on #debian-science -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#757355: ITP: phpunit-comparator -- functionality to compare PHP values for equality
Package: wnpp Severity: wishlist Owner: Prach Pongpanich prach...@gmail.com Control: block 744876 by -1 * Package name: phpunit-comparator Version : 1.0.0 Upstream Author : Sebastian Bergmann sebast...@phpunit.de * URL : https://github.com/sebastianbergmann/comparator * License : BSD-3-clause Programming Lang: PHP Description : functionality to compare PHP values for equality This component provides the functionality to compare PHP values for equality. . PHPUnit is a unit testing suite for the PHP language, modelled on the xUnit testing framework. It’s a needed dependency for the upcoming PHPUnit 4 and will be maintained inside the PHP PEAR (and Composer) team. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#666236: gforge-web-apache2: fails to install: manage-apache-config.sh: line 75: [: too many arguments
Control: severity -1 important Thanks severity 666236 serious # justification: https://release.debian.org/jessie/rc_policy.txt - 5a https://release.debian.org/jessie/rc_policy.txt 5. General (a) Supportable Packages in the archive must not be so buggy or out of date that we refuse to support them. There is a circular dependency in raising the bug severity on the basis that the bug should not have a high severity :) Cheers! Sylvain -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#757357: tracker.debian.org: regression from old-pts: links to FP bugs
Package: tracker.debian.org Severity: normal Hi, here's another regression from old-PTS. Both tools list FP: 2 for debian-installer, but the link is only correct in old-PTS: https://bugs.debian.org/cgi-bin/pkgreport.cgi?src=debian-installerarchive=nopend-inc=pending-fixedpend-inc=fixedrepeatmerged=no tracker.d.o uses this, which doesn't show any of the 2 bug reports: https://bugs.debian.org/cgi-bin/pkgreport.cgi?src=debian-installerpend-inc=fixedarchive=norepeatmerged=no You seem to be missing pend-inc=pending-fixed. (For reference in case their status changes in the meanwhile, those are #696418 and #700026.) Mraw, KiBi. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#757358: ansible: Please add recommends/depends against python-selinux
Package: ansible Version: 1.6.10+dfsg-1 Severity: wishlist Hi, It would be nice if the ansible package was recommending/depending against the python-selinux package. Please note that (obviously) SELinux is only available on linux architectures. Cheers, Laurent Bigonville -- System Information: Debian Release: jessie/sid APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.14-2-amd64 (SMP w/8 CPU cores) Locale: LANG=fr_BE.utf8, LC_CTYPE=fr_BE.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#650394: updated packages available
On Wed, Aug 6, 2014 at 10:50 AM, Yaroslav Halchenko deb...@onerussian.com wrote: - I see that there is some packaging available in upstream sources now, done by Brian (CCed). Brian -- would you be interested to join our tigervnc Debian packaging team to not duplicate efforts and avoid proliferation of tigervnc debian package names? See https://alioth.debian.org/projects/pkg-tigervnc/ all packaging is under Git and I am looking at changes from Matthias atm. Hi Yaroslav, Thanks for reaching out. Yes, I would like be involved in the debian packaging effort. However, in the interest of full disclosure I should admit that (1) as you've probably already guessed from my packages, I'm a novice at building debian packages, and (2) my bandwidth is all but crippled at the moment (though I'll assist in whatever way I can). I have some questions about your package: (1) Where is the java viewer? Being as it's my primary contribution to the project, I'd kinda like to see it included ;) (2) Have all of Pierre's Fltk patches been incorporated into the native debian Fltk package? If not, the viewer will lack full functionality. (I realize that statically linking the fltk libs into our binary is problematic from a distro point of view). Thanks, -brian
Bug#757360: Confusing version, please follow upstream version tags
Source: gr-fcdproplus Severity: wishlist User: de...@kali.org Usertags: origin-kali Hi, it's really not clear that 0.0.1.2.1edbe52 is actually uptsream version 3.7 plus some commits... due to this another Kali developer packaged a new upstream version as 3.6 when in fact the version in Debian was up-to-date. Please pick a version based on the upstream version: I suggest 3.7+date-of-git-snapshot and including the git commit in the changelog is enough, there's no need to stick it in the version itself. Since Kali actually has version 3.6 of this package, I would appreciate an upload bumping the version of the package so that the Debian package again takes precedence over the Kali package. Thank you in advance. PS: For projects where upstream provides absolutely no version, it's best to use 0~snapshot-date. That way it's clearer that we have no version at all. -- System Information: Debian Release: jessie/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing'), (500, 'stable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.14-2-amd64 (SMP w/4 CPU cores) Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#756816: apt: apt-get upgrade packagename should not set packagename to manually installed
On 2014-08-02 17:43, Axel Beckert wrote: Hi David, David Kalnischkies wrote: [...] It is also a remark on how people think they have installed a security fix by installing pkgA, while the fix is actually in libobscureA… O.o While I can imagine that people don't exactly know in which dependency the actual issue is located, I can't believe that people really try to fix issues that way. While it's not precisely equivalent, there's a reason that openssl DSAs now include the text It's important that you upgrade the libssl1.0.0 package and not just the openssl package. 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#757361: upower: breaks unrelated software
Package: upower Version: 0.99.0-3 Severity: critical Justification: breaks unrelated software Hi everyone, in former times, uploading a package that creates lots of breakage, it was necessary to provides fixes, or support, for the broken packages. This seems not to be the case anymore. xfce4 is *completely* broken due to upower0.99. Every update of systemd* breaks it, suspend is not working properly, etc etc etc. Why was an upload of upower0.99 allowed without making sure that at least most of the DE and important programs are fixable? Don't tell me that it is the responsability of the maintainers of package X. It is the responsability of the upower maintainers to make sure that transition is halfway smooth. But we are speaking of far from halfway smooth. This *is* RC, as xfce 4.12 will not be released in time for jessy, which means Debian would ship a broken XFCE. This is RC, and it is a bug of upower. Thanks Norbert -- System Information: Debian Release: jessie/sid APT prefers unstable APT policy: (500, 'unstable'), (200, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.16.0 (SMP w/4 CPU cores; PREEMPT) Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages upower depends on: ii dbus 1.8.6-1 ii libc6 2.19-7 ii libdbus-1-31.8.6-1 ii libdbus-glib-1-2 0.102-1 ii libglib2.0-0 2.40.0-3 ii libgudev-1.0-0 208-7 ii libimobiledevice4 1.1.6+dfsg-3 ii libplist2 1.11-3 ii libpolkit-gobject-1-0 0.105-6.1 ii libupower-glib20.99.0-3 ii libusb-1.0-0 2:1.0.19-1 ii pm-utils 1.4.1-15 ii systemd208-7 ii udev 208-7 Versions of packages upower recommends: ii policykit-1 0.105-6.1 upower 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#757330: [Pkg-libvirt-maintainers] Bug#757330: libvirt-daemon-system: fails to install: update-rc.d: error: insserv rejected the script header
On Thu, Aug 07, 2014 at 12:28:54PM +0200, Thorsten Glaser wrote: On Thu, 7 Aug 2014, Guido Günther wrote: Any chance to rerung this with DPKG_DEBUG=1 ? I did an update of a tglase@tglase:~ $ sudo env DPKG_DEBUG=1 dpkg -a --configure [sudo] password for tglase: Setting up libvirt-daemon-system (1.2.7-3) ... insserv: script libvirtd: service libvirt-bin already provided! insserv: exiting now! update-rc.d: error: insserv rejected the script header dpkg: error processing package libvirt-daemon-system (--configure): subprocess installed post-installation script returned error exit status 1 dpkg: dependency problems prevent configuration of libvirt-bin: libvirt-bin depends on libvirt-daemon-system (= 1.2.7-3); however: Package libvirt-daemon-system is not configured yet. I meant the whole update process from the previous version (downgrading to the old version, then updating again). I suspect dpkg-maintscript-helper to not identify /etc/init.d/libvirt-bin to be related part of libvirt-bin:amd64 and therefore not being moved out of the way. I saw a similar error when changing the libvirt-bin transitional package to arch all. dpkg: error processing package libvirt-bin (--configure): dependency problems - leaving unconfigured Errors were encountered while processing: libvirt-daemon-system libvirt-bin sysv based system yesterday without any troubles. Did you modify /etc/init.d/libvirt-bin ? Yes, I did. I added “linux64” before “start-stop-daemon --start […]” since I’m running an amd64 kernel with i386 userland and: tglase@tglase:~ $ cat /sbin/init #!/bin/mksh-static exec /usr/bin/linux32 /sbin/init.real $@ So this is multiarch using mostly i386 but some x86_64? Could you attach dpkg -l as well? Cheers, -- Guido -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#691310: bug in zip_add(3)
I think this bug is fixed since libzip-0.11.2. Thomas -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#739308: libzip-dev: include file in wrong place
Hi!
Upstream here.
I found this bug report.
We've put the header file in lib by purpose, because e.g. for multilib
installations, /usr/include must be portable over all architectures;
so architecture or machine-specific files must be somewhere else. One
convention for that is ${PREFIX}/lib/${PROGRAMNAME}/include, which for
example glib2 also follows.
Users are expected to use pkg-config.
I don't really care if Debian adds a symlink in /usr/include, except
that programmers working on Debian might think that they don't have to
use pkg-config and make it harder to port their programs to other
platforms.
Cheers,
Thomas
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#756658: [core] DB upgrade failed (owncloud 6 to 7 on debian sid) (#9893)
Hi blizzz, you'll find following the structure before and after the attempt (current). CREATE TABLE `oc_ldap_user_mapping` ( `ldap_dn` varchar(255) NOT NULL DEFAULT '', `owncloud_name` varchar(255) NOT NULL DEFAULT '', `directory_uuid` varchar(255) NOT NULL DEFAULT '', UNIQUE KEY `ldap_dn_users` (`ldap_dn`), UNIQUE KEY `owncloud_name_users` (`owncloud_name`) ) ENGINE=InnoDB DEFAULT CHARSET=utf8; Current table structure CREATE TABLE `oc_ldap_user_mapping` ( `ldap_dn` varchar(255) COLLATE utf8_bin NOT NULL DEFAULT '', `owncloud_name` varchar(255) COLLATE utf8_bin NOT NULL DEFAULT '', `directory_uuid` varchar(255) COLLATE utf8_bin NOT NULL DEFAULT '', UNIQUE KEY `ldap_dn_users` (`ldap_dn`), UNIQUE KEY `owncloud_name_users` (`owncloud_name`) ) ENGINE=InnoDB DEFAULT CHARSET=utf8 COLLATE=utf8_bin; Regards. Mathias On 06/08/2014 15:59, blizzz wrote: do you still have the old table somewhere available? could you give us the structure before the migration? The SQL command would be ```sql DESCRIBE oc_ldap_user_mapping; ``` --- Reply to this email directly or view it on GitHub: https://github.com/owncloud/core/issues/9893#issuecomment-51322625 -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#757226: Please inject pristine-tar for pynfft
Hi Ghislain, please use `git import-orig --pristine-tar tarball` to make sure the package can be easily built using git-buildpackage. I also switched to debhelper 9 (as well as I did in pyfftw before uploading) since there is no valid reason any more to use something else. Debhelper 9 supports automatic testing (if upstream provides this) and this is a good reason to use this version. 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#514464: Unexplained drawback in my workaround configuration
Hi, on an azerty french mapped keyboard, the above configuration disable the ability to write É, È, Ç and À with Caps+(é, è, ç or à on digits keys in the superior area of the keyboard). About the Caps_On key definition, I can guess that it is supposed to work like a Shift_Lock... But, what I really don't understand is the fact that the Pause key, becoming a Caps_Lock(so, I was guessing, like the original behaviour of the original caps lock key) suffers frome the same issue! Additionnaly, it lights up the led, at the contrary of the default caps lock key(and which is the original covered in this ticket) -- Sincerely and full of wonderness, Stephane Ascoet -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#728220: RFS: fatcat/1.0.4-1 [ITP]
Hi Grégoire,
Please:
1. Update the debhelper to 9. You must change d/compat and d/control to do it.
2. d/control:
- You didn't update the Standard-Version to 3.9.5. The Lintian
notified you about it.
- The Vcs-{Browser,Git} must refer to
{https,git}//github.com/Gregwar/fatcat/tree/debian
- Don't exist utils:Depends. Is misc:Depends.
- In short/long description: filesystem, not filesystemm. In two
last lines use semi-colons and dot.
3. d/copyright: in wrong format. Please, see an example here:
http://metadata.ftp-master.debian.org/changelogs/main/b/bittwist/unstable_copyright
4. Your d/watch doesn't work. Add 'version=3' as first line. More
datails at http://eriberto.pro.br/blog/?p=1459.
5. You must have a d/source directory with the file 'format'.
6. You must apply GCC/G++ hardening. More details at
https://wiki.debian.org/Hardening.
7. After build the package, try fix each Lintian message. It appear
easy for you, because you are the packager and upstream. So, try to
improve your package and, if needed, your code.
8. Upload your package to http://mentors.debian.net when done. I need
some files as .dsc. So, please, upload.
Thanks for your work.
Regards,
Eriberto
2014-08-07 8:06 GMT-03:00 Grégoire Passault g.passa...@gmail.com:
Hello,
I fixed the problems reported to me, is it ok for you too now (on the
1.0.4)?
Regards,
Grégoire
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#757344: wheezy-pu: package blender/2.63a-1
On 2014-08-07 at 10:29 (CEST), Matteo F. Vescovi wrote:
Attached, you'll find this famous patch that should fix the issue.
Probably, a debdiff would be much more appreciated ;-)
So, attached.
Cheers.
--
Matteo F. Vescovi | Debian Maintainer
GnuPG KeyID: 4096R/0x8062398983B2CF7A
diff -Nru blender-2.63a/debian/changelog blender-2.63a/debian/changelog
--- blender-2.63a/debian/changelog 2012-05-12 20:02:24.0 +0200
+++ blender-2.63a/debian/changelog 2014-08-07 14:47:56.0 +0200
@@ -1,3 +1,11 @@
+blender (2.63a-1+deb7u1) stable; urgency=low
+
+ * debian/patches/: patchset updated
+- 0010-fix_illegal_hardware_instruction_due_to_SSE2.patch added
+ to fix the illegal hardware instruction failure due to SSE2
+
+ -- Matteo F. Vescovi mfv.deb...@gmail.com Thu, 07 Aug 2014 14:19:06 +0200
+
blender (2.63a-1) unstable; urgency=low
* New upstream bugfix release
diff -Nru
blender-2.63a/debian/patches/0010-fix_illegal_hardware_instruction_due_to_SSE2.patch
blender-2.63a/debian/patches/0010-fix_illegal_hardware_instruction_due_to_SSE2.patch
---
blender-2.63a/debian/patches/0010-fix_illegal_hardware_instruction_due_to_SSE2.patch
1970-01-01 01:00:00.0 +0100
+++
blender-2.63a/debian/patches/0010-fix_illegal_hardware_instruction_due_to_SSE2.patch
2014-08-06 16:18:29.0 +0200
@@ -0,0 +1,81 @@
+From: Johann Klammer klamm...@a1.net
+Date: Wed, 13 Feb 2013 09:04:08 +0100
+Subject: fix_illegal_hardware_instruction_due_to_SSE2
+
+This makes sure it builds compatible binaries also on
+machines which have sse/sse2. Fixes the SIGILL bug.
+Checks for DEB_HOST_ARCH_CPU!=i386 before tests are attempted.
+Will try to use SSE/SSE2 on all other architectures.
+Generated Code will still need MMX support to run.
+
+Signed-off-by: Matteo F. Vescovi mfvesc...@gmail.com
+---
+ build_files/cmake/macros.cmake | 49 +++---
+ 1 file changed, 27 insertions(+), 22 deletions(-)
+
+diff --git a/build_files/cmake/macros.cmake b/build_files/cmake/macros.cmake
+index e4ac326..b172c81 100644
+--- a/build_files/cmake/macros.cmake
b/build_files/cmake/macros.cmake
+@@ -446,34 +446,39 @@ macro(TEST_SSE_SUPPORT
+
+ set(CMAKE_REQUIRED_FLAGS ${${_sse_flags}} ${${_sse2_flags}})
+
+- if(NOT DEFINED SUPPORT_SSE_BUILD)
+- # result cached
+- check_c_source_runs(
+- #include xmmintrin.h
+- int main(void) { __m128 v = _mm_setzero_ps(); return 0;
}
+- SUPPORT_SSE_BUILD)
+-
+- if(SUPPORT_SSE_BUILD)
+- message(STATUS SSE Support: detected.)
+- else()
+- message(STATUS SSE Support: missing.)
++ if(NOT ( $ENV{DEB_HOST_ARCH_CPU} STREQUAL i386 ) )
++
++ if(NOT DEFINED SUPPORT_SSE_BUILD)
++ # result cached
++ check_c_source_runs(
++ #include xmmintrin.h
++ int main(void) { __m128 v = _mm_setzero_ps();
return 0; }
++ SUPPORT_SSE_BUILD)
++
++ if(SUPPORT_SSE_BUILD)
++ message(STATUS SSE Support: detected.)
++ else()
++ message(STATUS SSE Support: missing.)
++ endif()
+ endif()
+- endif()
+
+- if(NOT DEFINED SUPPORT_SSE2_BUILD)
+- # result cached
+- check_c_source_runs(
++ if(NOT DEFINED SUPPORT_SSE2_BUILD)
++ # result cached
++ check_c_source_runs(
+ #include emmintrin.h
+- int main(void) { __m128d v = _mm_setzero_pd(); return
0; }
+- SUPPORT_SSE2_BUILD)
++ int main(void) { __m128d v = _mm_setzero_pd();
return 0; }
++ SUPPORT_SSE2_BUILD)
+
+- if(SUPPORT_SSE2_BUILD)
+- message(STATUS SSE2 Support: detected.)
+- else()
+- message(STATUS SSE2 Support: missing.)
++ if(SUPPORT_SSE2_BUILD)
++ message(STATUS SSE2 Support: detected.)
++ else()
++ message(STATUS SSE2 Support: missing.)
++ endif()
+ endif()
++ else()
++ message(STATUS SSE Support: missing.)
++ message(STATUS SSE2 Support: missing.)
+ endif()
+-
+ unset(CMAKE_REQUIRED_FLAGS)
+ endmacro()
+
diff -Nru blender-2.63a/debian/patches/series
blender-2.63a/debian/patches/series
--- blender-2.63a/debian/patches/series 2012-05-12 20:00:33.0 +0200
+++ blender-2.63a/debian/patches/series 2014-08-06 16:20:40.0 +0200
@@ -7,3 +7,4 @@
0007-fix_FTBFS_with_ffmpeg_from_debian.patch
Bug#757362: slrn: FTBFS because of outdated config.guess, config.sub on ppc64el
Package: src:slrn
Version: 1.0.1-10
Severity: normal
Tags: patch
User: debian-powe...@lists.debian.org
Usertags: ppc64el
Dear Maintainer,
the package slrn fails to build from source on ppc64el because
autoconf/config.guess
and autoconf/config.sub are outdated.
This patch adds the use of dh_autotools-dev_updateconfig and
dh_autotools-dev_restoreconfig to deal with that.
Thanks for reading,
Fred
-- System Information:
Debian Release: 7.5
APT prefers stable-updates
APT policy: (500, 'stable-updates'), (500, 'stable'), (450, 'testing')
Architecture: i386 (i686)
Kernel: Linux 3.2.0-4-686-pae (SMP w/8 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) (ignored: LC_ALL
set to en_US.UTF-8)
Shell: /bin/sh linked to /bin/dash
--- ./debian/rules.orig 2014-08-07 12:27:08.0 +
+++ ./debian/rules 2014-08-07 12:27:52.0 +
@@ -6,6 +6,7 @@ export DEB_CFLAGS_MAINT_APPEND = -Wall
dh ${@} --with autoreconf
override_dh_autoreconf:
+ dh_autotools-dev_updateconfig
dh_autoreconf autoconf -- --verbose --include=autoconf --output=configure autoconf/configure.ac
override_dh_auto_build:
@@ -45,10 +46,6 @@ override_dh_install-arch:
chmod g+ws,o+w,+t debian/slrnpull/var/spool/slrnpull/requests
-
-
-
-
-
-
-
+override_dh_autoreconf_clean:
+ dh_autotools-dev_restoreconfig
+ dh_autoreconf_clean
Bug#756593: busybox's switch_root makes read-only NFS root read/write
Am 06.08.2014 um 07:42 schrieb Michael Tokarev m...@tls.msk.ru:
05.08.2014 17:36, Zimmermann, Alexander wrote:
Despite the fact that I was unable to write a proper wrapper :-) - the
kernel crashes -
I know now that neither busybox nor AUFS is the culprit. See below:
Um. The wrapper should be something like:
#! /bin/sh
echo mounts before-init:
mount
exec /sbin/init $@
The key point is, I think, the `exec' keyword. Init should be started as
pid=1.
I see. I miss the exec command.
(initramfs) mount
rootfs on / type rootfs (rw)
sysfs on /sys type sysfs (rw,nosuid,nodev,noexec,relatime)
proc on /proc type proc (rw,nosuid,nodev,noexec,relatime)
udev on /root/dev type devtmpfs
(rw,relatime,size=10240k,nr_inodes=2051439,mode=755)
devpts on /root/dev/pts type devpts
(rw,nosuid,noexec,relatime,gid=5,mode=620)
tmpfs on /root/run type tmpfs (rw,nosuid,relatime,size=3282972k,mode=755)
192.168.0.10:/muclab/image/debian-sid on /root type nfs
(ro,relatime,vers=3,rsize=65536,wsize=65536,namlen=255,hard,nolock,proto=tcp,port=2049,timeo=7,retrans=10,sec=sys,local_lock=all,addr=192.168.0.10)
(initramfs) exit
sysfs on /sys type sysfs (rw,nosuid,nodev,noexec,relatime)
proc on /proc type proc (rw,nosuid,nodev,noexec,relatime)
udev on /dev type devtmpfs
(rw,relatime,size=10240k,nr_inodes=2051439,mode=755)
devpts on /dev/pts type devpts (rw,nosuid,noexec,relatime,gid=5,mode=620)
tmpfs on /run type tmpfs (rw,nosuid,relatime,size=3282972k,mode=755)
192.168.0.10:/muclab/image/debian-sid on / type nfs
(ro,relatime,vers=3,rsize=65536,wsize=65536,namlen=255,hard,nolock,proto=tcp,port=2049,timeo=7,retrans=10,sec=sys,local_lock=all,addr=192.168.0.10)
Usage: init {-e VAR[=VAL] | [-t SECONDS]
{0|1|2|3|4|5|6|S|s|Q|q|A|a|B|b|C|c|U|u}}
Kernel panic - not syncing: Attempted to kill init! exitcode=0x0100
Actually I was too fast. Since the node doesn’t came up in this test, I
cannot be sure if the NFS mount will be RO or RW after the booting was
completed. Let me rerun the test again. I will come back w/ the results.
But I see. Busybox switch_root worked, ran your myinit, and the mount
in question - nfs mount - is still readonly like it should be...
Now this is really interrresting.
Do you have /etc/fstab entry for this mount?
No. stab is empty.
I will create
Thanks,
/mjt
signature.asc
Description: Message signed with OpenPGP using GPGMail
Bug#497032: Does bug #497032
tags 497032 +moreinfo thanks A while back you filed bug #497032. Are you still able to reproduce this bug with a recent asterisk? Cheers, Jeremy -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#694805: Closing bug #694805
Control: reopen -1
Control: tags -1 - pending
On Thu, 2014-08-07 at 14:36 +0200, Jeremy Lainé wrote:
As noted previously, this bug does not make sense since the asterisk 11
upload.
Actually the problem is still present AFAICT and should not have been
tagged pending. The Provides field should be automatically calculated
based on the provided plugin ABI. Right now it is still hardcoded, but
to asterisk-11 instead of asterisk-1.8. This has the same problems that
hardcoding asterisk-1.8 had; it will get out of date. Based on the
message below from the bug report, the Provides should be set to
asterisk-${source:AST_BUILDOPT_SUM} and that calculated from
AST_BUILDOPT_SUM in buildopts.h.
http://sources.debian.net/src/asterisk/latest/debian/control#L66
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=694805#21
--
bye,
pabs
http://wiki.debian.org/PaulWise
signature.asc
Description: This is a digitally signed message part
Bug#692249: sata boot+grub unknown filesystem without boot=on
On 08/07/14 08:51, Michael Tokarev wrote: 07.08.2014 00:14, Gianluigi Tiesi wrote: qemu removed the option and grub still says unknown filesystem Yes, we removed the old option long time ago. But I was really worried about this unknown filesystem. You can close the bug I don't think it's a really an useful scenario, I was trying to boot my win7 partition with kvm using -snapshot, it wouldn't work anyway You're Very Wrong (tm). lol Lots of people do this all the time, me included. I've a dual-boot machine (with windows and linux), and while I don't reboot into windows often, but I do run it in qemu/kvm quite often, giving qemu my /dev/sda and choosing to boot windows there. It works just fine either way. It even keeps its activation (win7 OEM), because I pass /sys/firmware/acpi/tables/SLIC to the guest, the same as this PC was shipped with. I ran _many_ systems initially installed on a bare metal in qemu/kvm, just giving qemu their hdd directly (with or without -snapshot), and I run many systems initially installed in qemu/kvm on bare metal, after copying their hdd image to real hdd. Actually I installed all our windows machines at office this way - initially in qemu, copying to hdd with all installed and configured progs. All this without changing the systems in question in any noticeable way -- with the exception that initial boot of windows in foreign environment requires installing a compatible driver, which is, for metal=qemu case, either generic IDE or ahci/sata. Linux systems works without any modifications at all. As I already said, there's somethig wrong on your system. It shuoldn't work (or, rather, fail) like this. It smells like a bug which I want to find and fix. Please tell me what to do, the command line in the bug report loads grub correctly but then grub: SeaBIOS (version 1.7.5-20140531_083030-gandalf) iPXE (http://ipxe.org) 00:03.0 C980 PCI2.10 PnP PMM+3FF94B40+3FEF4B40 C980 Booting from Hard Disk... error: unknown filesystem. Entering rescue mode... grub rescue ls (hd0,msdos3)/ error: unknown filesystem. grub rescue but partition 3 is ext4, maybe because is mounted? Regards -- Gianluigi Tiesi sher...@netfarm.it EDP Project Leader Netfarm S.r.l. - http://www.netfarm.it/ Free Software: http://oss.netfarm.it/ Q: Because it reverses the logical flow of conversation. A: Why is putting a reply at the top of the message frowned upon? -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#756085: notmuch: please move away from emacs23-nox as default build-dependency
Package: notmuch Version: 0.18.1-1 Followup-For: Bug #756085 I applied the attached patch to build against current emacs and the build works fine on amd64, but fails one test (consistently) (on arm64). T380-atomicity: Testing atomicity PASS notmuch new is idempotent under arbitrary aborts FAIL detected 010 abort points test 0 -gt 10 Have you any idea what might be causing that? Is there a way to get a more verbose test log? I plan to do an NMU with the patch below, so that at least this package is updated (unless you say no). Then we can worry about the arm64 test issue separately and there will be public build-logs I can point to (It will also stop the buildd trying to build this package over and over and over again (116 attempts so far!): http://buildd.debian-ports.org/status/package.php?p=notmuchsuite=sid Would you prefer a patch where we just drop the emacs23 part or does that remain useful for backport builds? There doesn't seem to be an emacs-nox 'generic' package. I don't know if the 'emacs' generic package is sufficient, or desireable, for this case? Here is the (trivial) patch: diff -Nru notmuch-0.18.1/debian/changelog notmuch-0.18.1/debian/changelog --- notmuch-0.18.1/debian/changelog 2014-06-25 10:30:10.0 + +++ notmuch-0.18.1/debian/changelog 2014-08-07 09:36:15.0 + @@ -1,3 +1,10 @@ +notmuch (0.18.1-1.1) unstable; urgency=medium + + * Non-maintainer upload + * Upldate build-deps to use current emacs24 on buildd (Closes:756085) + + -- Wookey woo...@debian.org Thu, 07 Aug 2014 09:34:40 + + notmuch (0.18.1-1) unstable; urgency=medium * New upstream bug fix release diff -Nru notmuch-0.18.1/debian/control notmuch-0.18.1/debian/control --- notmuch-0.18.1/debian/control 2014-06-25 10:30:10.0 + +++ notmuch-0.18.1/debian/control 2014-08-07 09:33:26.0 + @@ -17,8 +17,8 @@ python3-all (= 3.1.2-7~), python-sphinx (= 1.0), ruby, ruby-dev (1:1.9.3~), - emacs23-nox | emacs23 (=23~) | emacs23-lucid (=23~) | - emacs24-nox | emacs24 (=24~) | emacs24-lucid (=24~), + emacs24-nox | emacs24 (=24~) | emacs24-lucid (=24~) | + emacs23-nox | emacs23 (=23~) | emacs23-lucid (=23~), gdb [!s390x !ia64 !armhf !armel], dtach (= 0.8), bash-completion (=1.9.0~) -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#756634: RFS: roxterm/2.9.1-1
On 07/08/14 09:27, Vincent Cheng wrote:
On Wed, Aug 6, 2014 at 3:01 PM, Tony Houghton h...@realh.co.uk wrote:
retitle 756634 RFS: roxterm/2.9.2-1
thanks
I think I've managed to fix the build now so that the debian package can be
built repeatedly. Most of the changes are upstream so there is a new
version. Please use the new link:
http://mentors.debian.net/debian/pool/main/r/roxterm/roxterm_2.9.2-1.dsc
Thanks for helping to improve this package and to get the new version into
Debian.
Building twice in a row still fails (the date in AppInfo.xml can
change; you can easily just workaround this with extend-diff-ignore,
of course):
Except that wasn't working for me, it said it was incompatible with
source format 3.0 (Quilt) (see above). Or was it specifically my regex
or syntax? It looked OK to me.
AppInfo.xml is a hangover from when I used to use the ROX desktop.
Shipping it in the tarball allows users to see info about the app before
compiling it. I don't know whether any roxterm users are still using
that, but I don't want to delete the ROX bits just in case. Next time I
change upstream I should change the build so that it doesn't regenerate
AppInfo.xml, and get my update-tags script to change it instead (I'll
keep forgetting if I rely on doing it manually).
But for now I'd like to fix this without a new upstream release. If I
can't get extend-diff-ignore to work would it be OK to have debian/rules
copy the file into debian at the start of the build and restore it
afterwards? Or is that too nasty a kludge?
Also, if you don't mind me being a bit pedantic, can you run
wrap-and-sort -s so that e.g. it'd be easier to review changes to your
deps and build-deps in debian/control?
OK, one dep per line, that makes sense. Is there anything I should do to
have it applied to other files generated from control after expanding
${misc:Depends} etc?
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#757316: whole disk one big partition is a bad default
1% would be fine... Else one day when they e.g., want to upgrade from ext4 to ext5 etc. and face http://www.debian-administration.org/article/643/Migrating_a_live_system_from_ext3_to_ext4_filesystem and end up with Kernel panic – not syncing Attempted to kill init when something goes wrong. All because they had no more room to copy /sbin etc. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#248426:
Cher compte utilisateur: Votre compte a été violé par un tiers. L'utilisation non autorisée et l'accès de votre compte à partir d'un autre emplacement que vous n'avez pas utilisé avant. Vous êtes pour vérifier votre compte avec 24 heures. Défaut de vérifier votre compte dans ce délai, votre compte sera désactivé et suspendu. Pour vérifier votre compte CLIQUEZ SUR LA VÉRIFICATION PORTAIL: http://www.neutralbayyoga.com.au/contact/use/red1/form1.html SERVICE DESK - IT HELP DESK © COPYRIGHT 2014 WEB-TEAM. TOUS DROITS RÉSERVÉS. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#700500: a CyrEo fontset, please?
tags 700500 + wontfix thank you On Wed, Feb 13, 2013 at 03:44:47PM +, Ivan Shmakov wrote: Package: console-setup-linux Version: 1.88 Severity: wishlist Tags: patch Please provide 256-glyph fonts with both Cyrillic and Esperanto glyphs (specifically: U+0108, U+0109, U+011C, U+011D, U+0124, U+0125, U+0134, U+0135, U+015C, U+015D, U+016C, U+016D.) One possible such fontset is MIME'd. It is based on CyrSlav.256, and retains all its glyphs within the U+04xx range, adds the aforementioned Esperanto glyphs, U+00F7 DIVISION SIGN, while removing certain U+20xx (U+2013, U+2020, U+2021, U+2030, U+2039, U+203A) glyphs, and U+2122 TRADE MARK SIGN, arguably not all that valuable for Cyrillic-based typography. Hi and thank you for your contribution! I am tagging this bug report as 'wontfix' for the following reasons: 1. The combination Cyrillic + Esperanto is supported by Uni2 and Uni3 fontsets. 2. Small fontsets (256 glyphs) are for one language only. Users who need multilingual support should use Uni1, Uni2 or Uni3. Anton Zinoviev -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#757363: libqtgui4: Qt print dialog's duplex setting not inferred from CUPS properties
Package: libqtgui4
Version: 4:4.8.2+dfsg-11
Severity: normal
Tags: upstream patch
Qt's printing dialog (as used, for example, by Iceweasel) does not infer the
duplex setting from CUPS's printer options.
This is a known bug in Qt, see https://bugs.kde.org/180051.
A patch is available at http://bugsfiles.kde.org/attachment.cgi?id=41187.
We've been using this pÃatch for ages, I include a revised version for 4.8.2.
-- System Information:
Debian Release: 7.6
APT prefers stable
APT policy: (500, 'stable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 3.10.42.wap (SMP w/2 CPU cores)
Locale: LANG=de_DE@euro, LC_CTYPE=de_DE@euro (charmap=ISO-8859-15)
Shell: /bin/sh linked to /bin/dash
Versions of packages libqtgui4 depends on:
ii fontconfig 2.9.0-7.1
ii libaudio2 1.9.3-5wheezy1
ii libc6 2.13-38+deb7u3
ii libfontconfig1 2.9.0-7.1
ii libfreetype6 2.4.9-1.1
ii libgcc11:4.7.2-5
ii libglib2.0-0 2.33.12+really2.32.4-5
ii libice62:1.0.8-2
ii libjpeg8 8d-1+deb7u1
ii libmng11.0.10-3
ii libpng12-0 1.2.49-1
ii libqtcore4 4:4.8.2+dfsg-11
ii libsm6 2:1.2.1-2
ii libstdc++6 4.7.2-5
ii libtiff4 3.9.6-11
ii libx11-6 2:1.5.0-1+deb7u1
ii libxext6 2:1.3.1-2+deb7u1
ii libxrender11:0.9.7-1+deb7u1
ii multiarch-support 2.13-38+deb7u3
ii zlib1g 1:1.2.7.dfsg-13
Versions of packages libqtgui4 recommends:
ii libcups2 1.5.3-5+deb7u4
Versions of packages libqtgui4 suggests:
pn qt4-qtconfig none
-- no debconf information
Index: src/gui/dialogs/qprintdialog_unix.cpp
===
--- src/gui/dialogs/qprintdialog_unix.cpp (revision 3625)
+++ src/gui/dialogs/qprintdialog_unix.cpp (revision 3626)
@@ -579,6 +579,32 @@
void QPrintDialogPrivate::selectPrinter(QCUPSSupport *cups)
{
options.duplex-setEnabled(cups cups-ppdOption(Duplex));
+
+if (cups) {
+const ppd_option_t* duplex = cups-ppdOption(Duplex);
+if (duplex) {
+// copy default ppd duplex to qt dialog
+if (qstrcmp(duplex-defchoice, DuplexTumble) == 0)
+options.duplexShort-setChecked(true);
+else if (qstrcmp(duplex-defchoice, DuplexNoTumble) == 0)
+options.duplexLong-setChecked(true);
+else
+options.noDuplex-setChecked(true);
+}
+
+if (cups-currentPPD()) {
+// set default color
+if (cups-currentPPD()-color_device)
+options.color-setChecked(true);
+else
+options.grayscale-setChecked(true);
+}
+
+// set collation
+const ppd_option_t *collate = cups-ppdOption(Collate);
+if (collate)
+options.collate-setChecked(qstrcmp(collate-defchoice,
True)==0);
+}
}
#endif
Index: src/gui/painting/qprinter.cpp
===
--- src/gui/painting/qprinter.cpp (revision 3625)
+++ src/gui/painting/qprinter.cpp (revision 3626)
@@ -609,6 +609,44 @@
d_ptr-paintEngine-type() != QPaintEngine::MacPrinter) {
setOutputFormat(QPrinter::PdfFormat);
}
+
+#if !defined(QT_NO_CUPS) !defined(QT_NO_LIBRARY)
+// fill in defaults from ppd file
+QCUPSSupport cups;
+
+int printernum = -1;
+for (int i = 0; i cups.availablePrintersCount(); i++) {
+if (printerName().toLocal8Bit() == cups.availablePrinters()[i].name)
+printernum = i;
+}
+if (printernum = 0) {
+cups.setCurrentPrinter(printernum);
+
+const ppd_option_t* duplex = cups.ppdOption(Duplex);
+if (duplex) {
+// copy default ppd duplex to qt dialog
+if (qstrcmp(duplex-defchoice, DuplexTumble) == 0)
+setDuplex(DuplexShortSide);
+else if (qstrcmp(duplex-defchoice, DuplexNoTumble) == 0)
+setDuplex(DuplexLongSide);
+else
+setDuplex(DuplexNone);
+}
+
+if (cups.currentPPD()) {
+// set default color
+if (cups.currentPPD()-color_device)
+setColorMode(Color);
+else
+setColorMode(GrayScale);
+}
+
+// set collation
+const ppd_option_t *collate = cups.ppdOption(Collate);
+if (collate)
+setCollateCopies(qstrcmp(collate-defchoice, True)==0);
+}
+#endif
}
/*!
Bug#736787: Likely chances of Vagrant in Jessie ? - Was: Re: Bug#736787:
Hi, On Thu, Aug 07, 2014 at 12:18:49PM +0200, Olivier Berger wrote: Hi. On Tue, Jul 29, 2014 at 10:23:51AM +0200, Bálint Réczey wrote: Hi, 2014-07-27 1:51 GMT+02:00 Balint Reczey bal...@balintreczey.hu: Control: tags -1 patch On 03/12/2014 09:54 PM, Mert Dirik wrote: Looks like it is fixed in upstream in commit 27420ad [1] by removing the offending files. New upstream version (1.5) should fix this bug. [1] https://github.com/mitchellh/vagrant/commit/27420ad2ee78caf1b1effc3eb27744ae2c288009 IMO the files still have to be removed from orig.tar.gz by repackaging it as 1.6.3+dfsg1 manually. I see 1.5.3 imported to packaging git, but it still has the files thus would not solve this RC bug. Antonio, do you plan releasing 1.6.3 with the problematic files removed from the source? The attached patch will remove the whole website dir from the source when using uscan --repack. I can push it to the packaging repository, but I did not want to do so before asking first. I have pushed the fix to the packaging repository and also created 1.5.3+dfsg1 with the website dir filtered out. Is there a package update in the plans? Even if packaging the latest upstream seems problematic for now, would a backport or the sources of the JS files for unstable version (1.4) be possible in the meantime ? Is 1.4 in jessie better than nothing, or the reverse, given the current state of affairs ? It is, that makes a lot of sense. I will upload a 1.4 fixing this issue. -- Antonio Terceiro terce...@debian.org signature.asc Description: Digital signature
Bug#757364: kde-runtime: kglobalaccel_x11 ungrabs wrong X11 keycodes leading to non-functional delete key
Package: kde-runtime
Version: 4:4.8.4-2
Severity: normal
Tags: upstream patch
Kglobalaccel wants to register the Print key.
The X11 implementation (kglobalaccel_x11) looks up the X11 keycode for that Qt
key, result is 107. It XGrabKey()s 107.
Later, the mapping changes. Kglobalaccel now unregisters all keys in order
re-register them later.
Kglobalaccel unregisters the Print Key.
The X11 implementation looks up the X11 keycode, now being 111. It
XUngrabKey()s 111.
This leaves 107 (which now is the Delete/,,Entfernen'' Key) still grabbed and
thus non-functional.
Since this is a race condition between shortcut registration and keyboard
mapping, it seems to appear randomly.
The bug has been filed (in 2011, including my original patch) as
https://bugs.kde.org/269403, but no-one seems to pick it up.
We keep patching kdebase-runtime/kde-runtime since then.
I Include an updated patch for 4.8.3.
-- System Information:
Debian Release: 7.6
APT prefers stable
APT policy: (500, 'stable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 3.10.42.wap (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 kde-runtime depends on:
ii kde-runtime-data4:4.8.4-2
ii kdelibs5-plugins4:4.8.4-4
ii libasound2 1.0.25-4
ii libattica0 0.2.0-1
ii libc6 2.13-38+deb7u3
ii libcanberra00.28-6
ii libexiv2-12 0.23-1
ii libgcc1 1:4.7.2-5
ii libjpeg88d-1+deb7u1
ii libkcmutils44:4.8.4-4
ii libkdeclarative54:4.8.4-4
ii libkdecore5 4:4.8.4-4
ii libkdesu5 4:4.8.4-4
ii libkdeui5 4:4.8.4-4
ii libkdewebkit5 4:4.8.4-4
ii libkdnssd4 4:4.8.4-4
ii libkemoticons4 4:4.8.4-4
ii libkfile4 4:4.8.4-4
ii libkhtml5 4:4.8.4-4
ii libkidletime4 4:4.8.4-4
ii libkio5 4:4.8.4-4
ii libkmediaplayer44:4.8.4-4
ii libknewstuff3-4 4:4.8.4-4
ii libknotifyconfig4 4:4.8.4-4
ii libkparts4 4:4.8.4-4
ii libkpty44:4.8.4-4
ii libnepomuk4 4:4.8.4-4
ii libnepomukquery4a 4:4.8.4-4
ii libntrack-qt4-1 016-1.1
ii libopenexr6 1.6.1-6
ii libphonon4 4:4.6.0.0-3
ii libplasma3 4:4.8.4-4
ii libpulse-mainloop-glib0 2.0-6.1
ii libpulse0 2.0-6.1
ii libqt4-dbus 4:4.8.2+dfsg-11
ii libqt4-declarative 4:4.8.2+dfsg-11
ii libqt4-network 4:4.8.2+dfsg-11
ii libqt4-script 4:4.8.2+dfsg-11
ii libqt4-svg 4:4.8.2+dfsg-11
ii libqt4-xml 4:4.8.2+dfsg-11
ii libqtcore4 4:4.8.2+dfsg-11
ii libqtgui4 4:4.8.2+dfsg-11
ii libqtwebkit42.2.1-5
ii libsmbclient2:3.6.6-6+deb7u4
ii libsolid4 4:4.8.4-4
ii libsoprano4 2.7.6+dfsg.1-2wheezy1
ii libssh-40.5.4-1+deb7u1
ii libstdc++6 4.7.2-5
ii libstreamanalyzer0 0.7.7-3
ii libstreams0 0.7.7-3
ii libx11-62:1.5.0-1+deb7u1
ii libxcursor1 1:1.1.13-1+deb7u1
ii oxygen-icon-theme 4:4.8.4-1
ii perl5.14.2-21+deb7u1
ii phonon 4:4.6.0.0-3
ii plasma-scriptengine-javascript 4:4.8.4-2
ii shared-desktop-ontologies 0.10.0-1
Versions of packages kde-runtime recommends:
ii virtuoso-minimal 6.1.4+dfsg1-7
Versions of packages kde-runtime suggests:
ii djvulibre-bin 3.5.25.3-1
pn finger none
pn icoutils none
-- no debconf information
Index: 4.8.4-2-mib/kglobalaccel/kglobalaccel_x11.cpp
===
--- 4.8.4-2-mib/kglobalaccel/kglobalaccel_x11.cpp (revision 3582)
+++ 4.8.4-2-mib/kglobalaccel/kglobalaccel_x11.cpp (revision 3583)
@@ -90,6 +90,8 @@
uint keyModX;
uint keySymX;
+ if (grab) {
+ /* not indented to keep the diff smaller */
// Resolve the modifier
if( !KKeyServer::keyQtToModX(keyQt, keyModX) ) {
kDebug() keyQt (0x hex keyQt ) failed to resolve
to x11 modifier;
@@ -121,6 +123,27 @@
kDebug() keyQt (0x hex keyQt ) was resolved to
x11 keycode 0;
return false;
}
+ /* end of non-indented section */
+ } else {
+ // Make sure to
Bug#697682: libapache2-mod-perl2: Intermittent FTBFS: t/apache/read3.t failure
On Sat, Mar 30, 2013 at 03:26:55PM +, Dominic Hargreaves wrote:
Control: retitle -1 libapache2-mod-perl2: Intermittent FTBFS:
t/apache/read3.t failure
This doesn't seem to be limited to s390; I've seen it in on i386 during
perl 5.16 rebuilds.
As a data point, t/apache/read3.t fails for me consistently on the
kfreebsd-{i386,amd64} porter boxes (fischer and falla) but interestingly
not on the kfreebsd buildds.
The test is getting an internal server error, with this in the
error log:
[Thu Aug 07 13:30:28.768239 2014] [perl:error] [pid 81995:tid 34593212160]
[client 127.0.0.1:12832] Apache2::RequestIO::read: (70007) The timeout
specified has expired at
/home/ntyni/libapache2-mod-perl2-2.0.8+httpd24-r1449661/t/response/TestApache/read3.pm
line 30
--
Niko Tyni nt...@debian.org
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#756426: [armhf] iceweasel segfaults when trying to save anything
For info, This has been raised upstream at: https://bugzilla.mozilla.org/show_bug.cgi?id=1050258 Cheers, -- Steve
Bug#757352: /etc/bash_completion.d/nikola contains /home/tin/projects/debian/nikola/nikola.git/nikola as first line
Hi Vedran, On Thu, Aug 07, 2014 at 01:52:51PM +0200, Vedran Miletić wrote: Package: nikola Version: 7.0.1-2 File /etc/bash_completion.d/nikola contains /home/tin/projects/debian/nikola/nikola.git/nikola as first line, which it probably shouldn't. You're so right :), sorry for this silly bug. I'll fix it right now. Thank you, --- TiN -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#757301: network-manager vanishes after establishing VPN connections when split routing is enabled.
Package: network-manager Version: 0.9.10.0-1 Followup-For: Bug #757301 Dear Maintainer, I'm also having this problem. The logs in /var/log/daemon say (note ip addresses have been anonymized): Aug 7 08:59:16 battra NetworkManager[968]: info devices added (path: /sys/devices/virtual/net/tun0, iface: tun0) Aug 7 08:59:16 battra NetworkManager[968]: info device added (path: /sys/devices/virtual/net/tun0, iface: tun0): no ifupdown configuration found. Aug 7 08:59:16 battra NetworkManager[968]: info VPN connection 'myvpn' (IP4 Config Get) reply received from old-style plugin. Aug 7 08:59:16 battra NetworkManager[968]: info VPN Gateway: 192.168.4.13 Aug 7 08:59:16 battra NetworkManager[968]: info Tunnel Device: tun0 Aug 7 08:59:16 battra NetworkManager[968]: info IPv4 configuration: Aug 7 08:59:16 battra NetworkManager[968]: info Internal Address: 192.168.16.185 Aug 7 08:59:16 battra NetworkManager[968]: info Internal Prefix: 24 Aug 7 08:59:16 battra NetworkManager[968]: info Internal Point-to-Point Address: 192.168.16.185 Aug 7 08:59:16 battra NetworkManager[968]: info Maximum Segment Size (MSS): 0 Aug 7 08:59:16 battra NetworkManager[968]: info Static Route: 192.168.172.64/26 Next Hop: 192.168.214.1 Aug 7 08:59:16 battra NetworkManager[968]: info Static Route: 192.168.184.128/25 Next Hop: 192.168.214.1 Aug 7 08:59:16 battra NetworkManager[968]: info Static Route: 192.168.172.1/26 Next Hop: 192.168.214.1 Aug 7 08:59:16 battra NetworkManager[968]: info Forbid Default Route: yes Aug 7 08:59:16 battra NetworkManager[968]: info DNS Domain: '(none)' Aug 7 08:59:16 battra NetworkManager[968]: info No IPv6 configuration Aug 7 08:59:16 battra NetworkManager[968]: info Login Banner: Aug 7 08:59:16 battra NetworkManager[968]: info - Aug 7 08:59:16 battra NetworkManager[968]: info Banner message Aug 7 08:59:16 battra NetworkManager[968]: info - Aug 7 08:59:16 battra NetworkManager[968]: info (tun0): link connected Aug 7 08:59:16 battra NetworkManager[968]: error [1407416356.843371] [platform/nm-linux-platform.c:1714] add_object(): Netlink error adding 192.168.172.64/26 via 192.168.214.1 dev tun0 metric 1024 mss 0 src user: Unspecific failure Aug 7 08:59:16 battra NetworkManager[968]: inet 192.168.172.64/26 table main Aug 7 08:59:16 battra NetworkManager[968]: priority 0x400 protocol static Aug 7 08:59:16 battra NetworkManager[968]: nexthop via 192.168.214.1 dev 8 Aug 7 08:59:16 battra NetworkManager[968]: warn VPN connection 'myvpn' did not receive valid IP config information. Aug 7 08:59:16 battra NetworkManager[968]: info (tun0): link disconnected Aug 7 08:59:16 battra NetworkManager[968]: ** Message: Terminated vpnc daemon with PID 12959. Aug 7 08:59:16 battra NetworkManager[968]: select: Interrupted system call Aug 7 08:59:16 battra NetworkManager[968]: terminated by signal: 15 Aug 7 08:59:16 battra avahi-daemon[857]: Withdrawing workstation service for tun0. Aug 7 08:59:16 battra NetworkManager[968]: VPNC started in foreground... Aug 7 08:59:16 battra NetworkManager[968]: info devices removed (path: /sys/devices/virtual/net/tun0, iface: tun0) Aug 7 08:59:37 battra NetworkManager[968]: info VPN service 'vpnc' disappeared -- System Information: Debian Release: jessie/sid APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.14-2-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages network-manager depends on: ii adduser3.113+nmu3 ii dbus 1.8.6-1 ii init-system-helpers1.20 ii isc-dhcp-client4.3.0+dfsg-2 ii libc6 2.19-7 ii libdbus-1-31.8.6-1 ii libdbus-glib-1-2 0.102-1 ii libgcrypt111.5.3-5 ii libglib2.0-0 2.40.0-3 ii libgnutls-deb0-28 3.2.16-1 ii libgudev-1.0-0 208-6 ii libmm-glib01.2.0-1 ii libndp01.4-1 ii libnewt0.520.52.17-1 ii libnl-3-2003.2.24-2 ii libnl-genl-3-200 3.2.24-2 ii libnl-route-3-200 3.2.24-2 ii libnm-glib40.9.10.0-1 ii libnm-util20.9.10.0-1 ii libpam-systemd 208-6 ii libpolkit-gobject-1-0 0.105-6.1 ii libreadline6 6.3-8 ii libsoup2.4-1 2.46.0-2 ii libsystemd-daemon0 208-6 ii libsystemd-login0 208-6 ii libuuid1 2.20.1-5.8 ii lsb-base 4.1+Debian13 ii policykit-10.105-6.1 ii udev 208-6 ii wpasupplicant 1.1-1 Versions of packages network-manager recommends: pn crda none ii dnsmasq-base 2.71-1 ii iptables 1.4.21-2 ii modemmanager 1.2.0-1 ii ppp 2.4.6-2 Versions of packages network-manager suggests: pn avahi-autoipd
Bug#757308: grass: Please update to use wxpython3.0
Hi, just a metacomment: Due to the wxPython issue several packages get RC bugs filed which in several cases leads to the fact that these are simply removed from testing and either create a lot of work or will be lost for the Jessie release. IMHO this is bad timing to get a predependency for several applications removed quite close to a release date. Kind regards Andreas. On Thu, Aug 07, 2014 at 10:52:42AM +0200, Sebastiaan Couwenberg wrote: Hi Olly, On 08/07/2014 06:56 AM, Olly Betts wrote: It looks like grass 7.0.0 will be compatible with wxPython 3.0 - I see in http://trac.osgeo.org/grass/wiki/Release/7.0.0beta-News the entry: | wxPython 3 compatibility fixes So updating the package to this version seems the simplest fix. In theory this is a good idea. But updating from grass 6.4.3 to 7.0.0 will require a transition, which we are unlikely to get in shape before the freeze in November. Updating from grass 6.4.3 to 6.4.4 is more in the realm of possibilities, so we'll need to look into backporting the wxPython 3.0 changes to that. Kind Regards, Bas -- GPG Key ID: 4096R/E88D4AF1 Fingerprint: 8182 DE41 7056 408D 6146 50D1 6750 F10A E88D 4AF1 ___ Pkg-grass-devel mailing list pkg-grass-de...@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-grass-devel -- 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#757367: udev: /lib/udev/hwdb.d/60-keyboard.hwdb documentation issues
Package: udev Version: 208-7 Severity: minor /lib/udev/hwdb.d/60-keyboard.hwdb contains some documentation at the beginning, but there are several problems with it. First, a typo: charcter - character It says: # Scan codes are specified as: #KEYBOARD_KEY_hex scan code=key code identifier # The scan code should be expressed in hex lowercase and in # full bytes, a multiple of 2 digits. The key codes are retrieved ^^ # and normalized from the kernel input API header. but in the settings, scan codes are also expressed on 3 or 5 digits, e.g. # enhanced USB keyboard keyboard:usb:v04B3p301B* KEYBOARD_KEY_90001=prog1 # ThinkVantage KEYBOARD_KEY_90002=screenlock KEYBOARD_KEY_90003=file KEYBOARD_KEY_90004=wordprocessor KEYBOARD_KEY_90005=spreadsheet KEYBOARD_KEY_90006=calc KEYBOARD_KEY_90007=mail KEYBOARD_KEY_90008=www # Satellite U940 keyboard:name:Toshiba*input*device:dmi:bvn*:bvr*:bd*:svnTOSHIBA*:pnSATELLITEU940:pvr* KEYBOARD_KEY_13c=brightnessdown KEYBOARD_KEY_13d=brightnessup KEYBOARD_KEY_13e=switchvideomode KEYBOARD_KEY_13f=f21 # Touchpad toggle Thus this is confusing. It also says: # To debug key presses and access scan code mapping data of # an input device use the commonly available tool: evtest(1). Unfortunately, evtest doesn't output scan codes for some keys: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=757356 The udev keymap utility had the same problem, but once patched, it could output the full keymap as a workaround. Unfortunately, evtest cannot do that (well, I didn't see anything like that in its documentation). The input-kbd utility can do that, so that it would be a good idea to mention it too. Moreover this file should also say how one can do some tests and where one can look for error messages. And what should be done to take the changes into account? After a search on the web, it seems that most users don't know either. http://marcin.juszkiewicz.com.pl/2014/03/03/how-to-get-zoom-slider-on-microsoft-keyboard-recognized-by-x11/ says: udevadm hwdb --update udevadm control --reload but one needs to replug the keyboard (or reboot!). http://askubuntu.com/questions/499252/my-custom-udev-hwdb-rule-doesnt-work just says: udevadm hwdb --update but it doesn't work. http://forums.fedoraforum.org/showpost.php?p=1681790postcount=3 says: udevadm hwdb --update udevadm trigger udevadm control --reload which might be the solution. /usr/share/doc/udev doesn't help either since it just has the changelog and copyright files. -- Package-specific info: -- System Information: Debian Release: jessie/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing'), (500, 'stable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.11-2-amd64 (SMP w/2 CPU cores) Locale: LANG=POSIX, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
