Bug#769072: gnome-shell: GNOME Shell crashing with Oh no, something went wrong
Package: gnome-shell Version: 3.14.1-1 Severity: grave I have this problem after an upgrade made a week or so. Unfortunately I haven't analysed the problem immediately, because of an urgent work to do I've just started to use the computer remotely with ssh. I vaguely remember a message saying something about configuring a video driver, which unfortunatelu I did not write down. I've looked for it in apt log but was unable to find it. Are all the apt messages stored somewhere? The files ~/.cache/gdm/session.log and ~/.cache/gdm/session.log.old are older than the problem, new files are not created. On another partition of the very computer I made a fresh install of jessie and it works OK. How to pin down the differences in the configuration? My working system has more packages installed, but the packages possibly relevant to the problem seems the same on both installation. I will appreciate very much your help. Janusz -- System Information: Debian Release: jessie/sid APT prefers testing APT policy: (500, 'testing') Architecture: i386 (i686) Kernel: Linux 3.16-3-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/dash Versions of packages gnome-shell depends on: ii dconf-gsettings-backend [gsettings-backend] 0.22.0-1 ii evolution-data-server3.12.7.1-1 ii gir1.2-accountsservice-1.0 0.6.37-3+b1 ii gir1.2-atspi-2.0 2.14.0-1 ii gir1.2-caribou-1.0 0.4.15-1 ii gir1.2-clutter-1.0 1.20.0-1 ii gir1.2-freedesktop 1.42.0-2.2 ii gir1.2-gcr-3 3.14.0-2 ii gir1.2-gdesktopenums-3.0 3.14.1-1 ii gir1.2-gdm3 3.14.1-1 ii gir1.2-gkbd-3.0 3.6.0-1 ii gir1.2-glib-2.0 1.42.0-2.2 ii gir1.2-gnomebluetooth-1.03.14.0-1 ii gir1.2-gnomedesktop-3.0 3.14.1-1 ii gir1.2-gtk-3.0 3.14.4-1 ii gir1.2-ibus-1.0 1.5.9-1 ii gir1.2-mutter-3.03.14.1-2 ii gir1.2-networkmanager-1.00.9.10.0-3 ii gir1.2-nmgtk-1.0 0.9.10.0-2 ii gir1.2-pango-1.0 1.36.8-2 ii gir1.2-polkit-1.00.105-7 ii gir1.2-soup-2.4 2.48.0-1 ii gir1.2-telepathyglib-0.120.24.1-1 ii gir1.2-telepathylogger-0.2 0.8.1-1 ii gir1.2-upowerglib-1.00.99.1-3 ii gjs 1.42.0-1 ii gnome-backgrounds3.14.1-1 ii gnome-icon-theme-symbolic3.12.0-1 ii gnome-settings-daemon3.14.1-1 ii gnome-shell-common 3.14.1-1 ii gnome-themes-standard3.14.0-1 ii gsettings-desktop-schemas3.14.1-1 ii libatk-bridge2.0-0 2.14.0-2 ii libatk1.0-0 2.14.0-1 ii libc62.19-12 ii libcairo21.14.0-2.1 ii libcanberra-gtk3-0 0.30-2.1 ii libcanberra0 0.30-2.1 ii libclutter-1.0-0 1.20.0-1 ii libcogl-pango20 1.18.2-2 ii libcogl201.18.2-2 ii libcroco30.6.8-3 ii libdbus-glib-1-2 0.102-1 ii libecal-1.2-16 3.12.7.1-1 ii libedataserver-1.2-183.12.7.1-1 ii libgcr-base-3-1 3.14.0-2 ii libgdk-pixbuf2.0-0 2.31.1-2+b1 ii libgirepository-1.0-11.42.0-2.2 ii libgjs0e [libgjs0-libmozjs-24-0] 1.42.0-1 ii libglib2.0-0 2.42.0-2 ii libgstreamer1.0-01.4.3-1.2 ii libgtk-3-0 3.14.4-1 ii libical1 1.0-1.1 ii libjson-glib-1.0-0 1.0.2-1 ii libmozjs-24-024.2.0-2 ii libmutter0e 3.14.1-2 ii libnm-glib4 0.9.10.0-3 ii libnm-util2 0.9.10.0-3 ii libpango-1.0-0 1.36.8-2 ii libpangocairo-1.0-0 1.36.8-2 ii libpolkit-agent-1-0 0.105-7 ii libpolkit-gobject-1-00.105-7 ii libpulse-mainloop-glib0 5.0-13 ii libpulse05.0-13 ii
Bug#769071: Cannot seek/skip in YouTube (possibly HTTP too) streams.
Package: vlc Version: 2.2.0~rc1-1 Severity: normal Dear Maintainer, * What led up to the situation? I updated to the latest vlc version on unstable (2.2.0~rc1-1) and afterwards I played a YouTube video (will leave some sample YouTube URLs below), and I tried skipping to a certain part of the video but it doesn't jump to it. Instead the time counter runs off counting from where I skipped, but there is no video or audio (I'm left with the last streamed frame on the screen). Seeking/skipping locally stored video files works fine. Sample videos: https://youtube.com/watch?v=8bJIJwimSbk https://youtube.com/watch?v=krXBaxD2BrI https://youtube.com/watch?v=UAA-9S8MJn4 https://youtube.com/watch?v=HNxnRqLskXo https://youtube.com/watch?v=DWefOzTZ268 https://youtube.com/watch?v=h6D4MMWjrmM It seems that no particular format works when seeking with VLC at all, so it's not just an issue mp4 videos as in the previous bug that I submitted. * What exactly did you do (or not do) that was effective (or ineffective)? Cleared the plugin cache (there was none) * What was the outcome of this action? Nothing changed as expected. Here's what errors I get into stdout: ___ [09f0a2c0] avcodec decoder warning: cannot decode one frame (146 bytes) [09f0a2c0] avcodec decoder warning: cannot decode one frame (146 bytes) [09f0a2c0] avcodec decoder warning: cannot decode one frame (654 bytes) [0a330950] faad decoder warning: Bitstream value not allowed by specification [0a330950] faad decoder warning: Invalid number of channels [0a330950] faad decoder warning: Maximum number of bitstream elements exceeded [0a330950] faad decoder warning: Bitstream value not allowed by specification [0a330950] faad decoder warning: Bitstream value not allowed by specification [0a330950] faad decoder warning: Maximum number of bitstream elements exceeded [0a330950] faad decoder warning: Bitstream value not allowed by specification [0a330950] faad decoder warning: Channel coupling not yet implemented [0a330950] faad decoder warning: Bitstream value not allowed by specification [0a330950] faad decoder warning: Bitstream value not allowed by specification [0a330950] faad decoder warning: Bitstream value not allowed by specification [0a330950] faad decoder warning: Channel coupling not yet implemented [0a330950] faad decoder warning: PCE shall be the first element in a frame [0a330950] faad decoder warning: Unexpected channel configuration change [0a330950] faad decoder warning: Invalid number of channels [0a330950] faad decoder warning: Channel coupling not yet implemented [0a330950] faad decoder warning: Invalid number of channels [0a330950] faad decoder warning: Maximum number of bitstream elements exceeded [0a330950] faad decoder warning: Unexpected channel configuration change [0a330950] faad decoder warning: Bitstream value not allowed by specification [0a330950] faad decoder warning: Bitstream value not allowed by specification [09f0a2c0] avcodec decoder warning: cannot decode one frame (637 bytes) [09f0a2c0] avcodec decoder warning: cannot decode one frame (235 bytes) [09f0a2c0] avcodec decoder warning: cannot decode one frame (166 bytes) [09f0a2c0] avcodec decoder warning: cannot decode one frame (177 bytes) [0a330950] faad decoder warning: PCE shall be the first element in a frame [0a330950] faad decoder warning: Bitstream value not allowed by specification [0a330950] faad decoder warning: PCE shall be the first element in a frame [0a330950] faad decoder warning: Bitstream value not allowed by specification [0a330950] faad decoder warning: Invalid number of channels [0a330950] faad decoder warning: Bitstream value not allowed by specification [0a330950] faad decoder warning: Bitstream value not allowed by specification [0a330950] faad decoder warning: Invalid number of channels [0a330950] faad decoder warning: Bitstream value not allowed by specification [0a330950] faad decoder warning: Bitstream value not allowed by specification [0a330950] faad decoder warning: Bitstream value not allowed by specification [0a330950] faad decoder warning: Bitstream value not allowed by specification [0a330950] faad decoder warning: Channel coupling not yet implemented [0a330950] faad decoder warning: Invalid number of channels [0a330950] faad decoder warning: Bitstream value not allowed by specification [0a330950] faad decoder warning: Bitstream value not allowed by specification [0a330950] faad decoder warning: Bitstream value not allowed by specification [0a330950] faad decoder warning: Invalid number of channels [0a330950] faad decoder warning: Bitstream value not allowed by specification [0a330950] faad decoder warning: Bitstream value not allowed by specification [0a330950] faad decoder warning: Bitstream value not allowed by specification [09f0a2c0] avcodec decoder warning: cannot decode one frame (169 bytes) [09f0a2c0] avcodec decoder warning: cannot decode one frame (161
Bug#769069: systemd: Failed to start Login Service
Control: tag -1 moreinfo Hello Paul, Paul Menzel [2014-11-11 8:40 +0100]: starting the Debian Sid/unstable system this morning, it did not boot. `Failed to start Login Service` was shown repeatedly as trying to start it again did not work. Can you please boot with adding systemd.debug-shell to the kernel command line in grub, then after the failure press Alt+F9 to get to the debug root shell? There you can run systemctl status systemd-logind.service to see what's going on. Thanks, Martin -- Martin Pitt| http://www.piware.de Ubuntu Developer (www.ubuntu.com) | Debian Developer (www.debian.org) signature.asc Description: Digital signature
Bug#769073: [duplicate-files] is mark with X for xxperimenta, but in the info the Severity are pedantic,
Package: lintian Version: 2.5.30 Severity: normal X: bitz-server-doc: duplicate-files usr/share/doc/bitz-server- doc/docs/search/all_0.js usr/share/doc/bitz-server- doc/docs/search/functions_0.js N: N:The package ships the two (or more) files with the exact same contents. N: N:Note: empty files are exempt from this check. N: N:Severity: pedantic, Certainty: possible N: N:Check: duplicate-files, Type: binary N: N:This tag is marked experimental, which means that the code that N:generates it is not as well-tested as the rest of Lintian and might N:still give surprising results. Feel free to ignore experimental tags -- System Information: Debian Release: jessie/sid APT prefers testing APT policy: (900, 'testing'), (800, 'unstable'), (500, 'testing-updates') Architecture: amd64 (x86_64) Kernel: Linux 3.16-3-amd64 (SMP w/6 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 lintian depends on: ii binutils 2.24.90.20141023-1 ii bzip2 1.0.6-7+b1 ii diffstat 1.58-1 ii file 1:5.20-1 ii gettext0.19.3-1 ii hardening-includes 2.6 ii intltool-debian0.35.0+20060710.1 ii libapt-pkg-perl0.1.29+b2 ii libarchive-zip-perl1.39-1 ii libclass-accessor-perl 0.34-1 ii libclone-perl 0.37-1+b1 ii libdpkg-perl 1.17.21 ii libemail-valid-perl1.195-1 ii libfile-basedir-perl 0.03-1 ii libipc-run-perl0.92-1 ii liblist-moreutils-perl 0.33-2+b1 ii libparse-debianchangelog-perl 1.2.0-1.1 ii libtext-levenshtein-perl 0.11-1 ii libtimedate-perl 2.3000-2 ii liburi-perl1.64-1 ii man-db 2.7.0.2-3 ii patchutils 0.3.3-1 ii perl [libdigest-sha-perl] 5.20.1-2 ii t1utils1.38-1 Versions of packages lintian recommends: ii libperlio-gzip-perl 0.18-3+b1 ii perl5.20.1-2 ii perl-modules [libautodie-perl] 5.20.1-2 Versions of packages lintian suggests: pn binutils-multiarch none ii dpkg-dev 1.17.21 ii libhtml-parser-perl3.71-1+b3 pn libtext-template-perl none ii libyaml-perl 1.13-1 ii xz-utils 5.1.1alpha+20120614-2+b1 -- 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#768485: dpkg: format string vulnerability
* Guillem Jover guil...@debian.org, 2014-11-11, 02:23: BTW Jakub, did you find this in parallel, or simply relied the bug filed in Launchpad? The latter; all credit goes to Joshua. -- Jakub Wilk -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#763043: qemu-user-binfmt: binfmt support broken - package empty, foreign binaries do not run
Excerpts from Michael Tokarev's message of Tue Nov 11 08:33:40 +0100 2014: 27.09.2014 18:10, Michael Tokarev wrote: Control: tag -1 moreinfo unreproducible 27.09.2014 16:33, Michal Suchanek wrote: Package: qemu-user-binfmt Version: 2.1+dfsg-4 Severity: normal Hello, I tried installing qemu-user-binfmt in the hope I will be able to run foreign architecture binaries. This has absolutely no results. THe package is empty and foreign binaries do not run. As stated in the package description, the package is empty and the only reason for it to exist is to run scripts at install and remove times to register binfmt support. This is the reason why it depends on qemu-user (actual implementation) and binfmt-support (registration). Please be more specific. Which binaries you tried to run but failed? What error message did you get? With the info you provided it is impossible to handle your bugreport, especially since I know this package works on my systems. Do you realize that in order to run regular foreign binary, you also need to install all (foreign) libraries required by that binary. With plain qemu-user and without additional foreig libraries it is possible to run only statically linked foreign binaries. On the other hand you can create a whole foreign chroot with its own libraries and directory structure, and chroot into it using qemu as a helper/emulator -- but for this to work, now it is qemu who needs (now native) libraries inside the chroot, or you should use statically linked qemu. Interestingly, on machines where this works this plackage is not present. Is this package supposed to do anything? See above. If not what is the preferred way to run foreign binaries? I don't understand this question. There's no True Way for anything. Depending on your needs, you may use qemu-user-binfmt or qemu-user-static, there may be other alternatives. I found that I have qemu-user-static instead of qemu-user-binfmt on system where this works. I can run armhf binaries on a PC but the reverse does not work. There is a handler for PC binaries registered but bash still reports it cannot execute binary file. Is the magic for PC binaries correct? How do I check? Hello Michal. A friendly ping? Do you have any additional information for this bugreport? I can't do anything with it without your input... I did send another email in the bug report, right? Thanks Michal -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#763043: qemu-user-binfmt: binfmt support broken - package empty, foreign binaries do not run
11.11.2014 11:02, Michal Suchanek wrote: [] I found that I have qemu-user-static instead of qemu-user-binfmt on system where this works. I can run armhf binaries on a PC but the Yes, I've seen that. reverse does not work. There is a handler for PC binaries registered but bash still reports it cannot execute binary file. Is the magic for PC binaries correct? How do I check? I replied to that at the time, -- the same magic strings are used in both packages (qemu-user-static and qemu-user-binfmt), these are generated (using simple substitutions) from a common file. Hello Michal. A friendly ping? Do you have any additional information for this bugreport? I can't do anything with it without your input... I did send another email in the bug report, right? Yes, and I replied to that, see https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=763043#22 So, to rehash, do I understand it right that you're having probs with running x86 binaries on arm, when using -user-binfmt but not when using -user-static ? Did you try using -user-binfmt on PC to run arm binaries, does that work? (I can try that myself, but I think I verified this). Please note that -user-binfmt (the non-statically-linked variant) will not work in a foreign chroot, since it needs not only the qemu binary itself, but also all the libraries which are linked dynamically into it. But I think this does not apply since you don't run foreign binaries in a chroot, at least as far as I can understand. 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#769073: [duplicate-files] is mark with X for xxperimenta, but in the info the Severity are pedantic,
Control: tags -1 + moreinfo On 2014-11-11 8:05, Jörg Frings-Fürst wrote: X: bitz-server-doc: duplicate-files usr/share/doc/bitz-server- doc/docs/search/all_0.js usr/share/doc/bitz-server- doc/docs/search/functions_0.js [...] N:Severity: pedantic, Certainty: possible N: N:Check: duplicate-files, Type: binary N: N:This tag is marked experimental, which means that the code that N:generates it is not as well-tested as the rest of Lintian and might N:still give surprising results. Feel free to ignore experimental tags I'm afraid I'm confused. What exactly is the problem that you're requesting be fixed? 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#697052: moreutils: 'pee' with 'echo' buggy.
Dear A. Costa, dear Maintainer, as soon as you delay the exit of the pipe's input command until all children of 'pee' are able to output the incoming data, everything should work as expected; the obvious example: (echo foo ; sleep 1) | pee cat echo cat cat Modifying pee to delay the closing of the pipes would not be helpful. In my opinion it might be helpful to a simple further explanation to the man page and leave the sources as they are. Kind regards, Nicolas signature.asc Description: Digital signature
Bug#768626: [Pkg-mc-devel] Bug#768626: mc should not depend on e2fslibs
On Sat, 2014-11-08 at 19:43 +0100, Wilfried Klaebe wrote: Please change mc to, at most, recommend e2fslibs. This compile time dependency is needed for the unerase feature, so it can't be changed to recommends, only left as is, or completely removed. I'm not sure if anyone is still using it, but that's a different question; I don't know what's the procedure for deciding whether to cut a feature out or not. -- Sincerely yours, Yury V. Zaytsev -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#769070: dpkg-buildpackage: libraries not found by dpkg-shlibdeps
Control: tags -1 unreproducible moreinfo Hi! On Mon, 2014-11-10 at 21:50:00 -1000, Joel Roth wrote: Package: dpkg-dev Version: 1.17.21 Severity: normal Recently upgraded sid. Ran debuild -b -uc -us on pristine sources downloaded via apt-get source. The build fails due to not finding the libraries that were compiled, and not finding libc.so.6. If you mean self-compiled (not packaged) libraries, then that might be the problem. In any case this pretty much smells like a local system setup problem to me. The package builds fine on an up-to-date sid chroot here. Have you done anything else to your system? Let's see below. Here is the build output for dbus. It seems to be udisks, but no matter. --- git:master ~/build/udisks2 $ debuild -uc -us -b dpkg-buildpackage -rfakeroot -D -us -uc -b dpkg-buildpackage: source package udisks2 dpkg-buildpackage: source version 2.1.3-5 dpkg-buildpackage: source distribution unstable dpkg-buildpackage: source changed by Michael Biebl bi...@debian.org dpkg-source --before-build udisks2 dpkg-buildpackage: host architecture amd64 fakeroot debian/rules clean […] dh_makeshlibs dh_shlibdeps dpkg-shlibdeps: error: couldn't find library libatasmart.so.4 needed by debian/udisks2/usr/lib/udisks2/udisksd (ELF format: 'elf64-x86-64'; RPATH: '/usr/lib/x86_64-linux-gnu') dpkg-shlibdeps: error: couldn't find library libacl.so.1 needed by debian/udisks2/usr/lib/udisks2/udisksd (ELF format: 'elf64-x86-64'; RPATH: '/usr/lib/x86_64-linux-gnu') dpkg-shlibdeps: error: couldn't find library libsystemd.so.0 needed by debian/udisks2/usr/lib/udisks2/udisksd (ELF format: 'elf64-x86-64'; RPATH: '/usr/lib/x86_64-linux-gnu') dpkg-shlibdeps: error: couldn't find library libglib-2.0.so.0 needed by debian/udisks2/usr/lib/udisks2/udisksd (ELF format: 'elf64-x86-64'; RPATH: '/usr/lib/x86_64-linux-gnu') dpkg-shlibdeps: error: couldn't find library libpthread.so.0 needed by debian/udisks2/usr/lib/udisks2/udisksd (ELF format: 'elf64-x86-64'; RPATH: '/usr/lib/x86_64-linux-gnu') dpkg-shlibdeps: error: couldn't find library libc.so.6 needed by debian/udisks2/usr/lib/udisks2/udisksd (ELF format: 'elf64-x86-64'; RPATH: '/usr/lib/x86_64-linux-gnu') dpkg-shlibdeps: error: couldn't find library libglib-2.0.so.0 needed by debian/udisks2/usr/bin/udisksctl (ELF format: 'elf64-x86-64'; RPATH: '/usr/lib/x86_64-linux-gnu') dpkg-shlibdeps: error: couldn't find library libpthread.so.0 needed by debian/udisks2/usr/bin/udisksctl (ELF format: 'elf64-x86-64'; RPATH: '/usr/lib/x86_64-linux-gnu') dpkg-shlibdeps: error: couldn't find library libc.so.6 needed by debian/udisks2/usr/bin/udisksctl (ELF format: 'elf64-x86-64'; RPATH: '/usr/lib/x86_64-linux-gnu') dpkg-shlibdeps: error: couldn't find library libglib-2.0.so.0 needed by debian/udisks2/sbin/umount.udisks2 (ELF format: 'elf64-x86-64'; RPATH: '/usr/lib/x86_64-linux-gnu') dpkg-shlibdeps: error: couldn't find library libpthread.so.0 needed by debian/udisks2/sbin/umount.udisks2 (ELF format: 'elf64-x86-64'; RPATH: '/usr/lib/x86_64-linux-gnu') dpkg-shlibdeps: error: couldn't find library libc.so.6 needed by debian/udisks2/sbin/umount.udisks2 (ELF format: 'elf64-x86-64'; RPATH: '/usr/lib/x86_64-linux-gnu') dpkg-shlibdeps: error: cannot continue due to the errors listed above Note: libraries are not searched in other binary packages that do not have any shlibs or symbols file. To help dpkg-shlibdeps find private libraries, you might need to use -l. dh_shlibdeps: dpkg-shlibdeps -Tdebian/udisks2.substvars debian/udisks2/usr/bin/udisksctl debian/udisks2/usr/lib/udisks2/udisksd debian/udisks2/sbin/umount.udisks2 returned exit code 2 Can you send the output from: $ dpkg-shlibdeps -v -Tdebian/udisks2.substvars \ debian/udisks2/usr/bin/udisksctl \ debian/udisks2/usr/lib/udisks2/udisksd \ debian/udisks2/sbin/umount.udisks2 ? debian/rules:4: recipe for target 'binary' failed make: *** [binary] Error 2 dpkg-buildpackage: error: fakeroot debian/rules binary gave error exit status 2 debuild: fatal error at line 1373: dpkg-buildpackage -rfakeroot -D -us -uc -b failed Thanks, Guillem -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#769074: sympa: After wheezy-backports sympa does not work at all
Package: sympa Version: 6.1.23~dfsg-1~bpo70+1 Severity: normal Tags: d-i Dear Maintainer, My sympa installation is with a postgres database on an other server. After this (and previous) upgrades of sympa nothing worked. The postgres database is not updated, webinterface did not work, configuration files were incorrectly adjusted, files ownership incorrect. I do not know the reasons but I assume the post install or upgrade script made a mess. I can't exactly remember the previous important backports upgrade but in that case: - the configuration files were incorrectly updated. I remember that the database configuration entries in sympa.conf were overwritten. - It was impossible to install without mysql (I use postgres) With a lot of patience I managed to get sympa running again. Last upgrade to 6.1.23: - Postgres database was not updated. I had to to this by hand: compare the source of 6.1.23 with the existing postgres database and alter the tables by hand. Time consuming and I'm not sure everything is now correct. - for unknown reason my webinterface did not work. A new configuration solved this problem - I presume files in /usr/lib/sympa/lib/sympa have an incorrect permission and ownership. After chown sympa /usr/lib/sympa/lib/sympa/* chmod u+s /usr/lib/sympa/lib/sympa/* it works again - Probably some other issues. If things are working again I tend to forget pretty quickly all the actions. I understand that thing can go wrong, but the sympa upgrades are complicated. I think the main reasons are: I use postgres as database and the database server is not localhost. For the moment sympa is running again but I still get apt errors: Setting up sympa (6.1.23~dfsg-1~bpo70+1) ... dpkg: error processing sympa (--configure): subprocess installed post-installation script returned error exit status 10 Errors were encountered while processing: sympa E: Sub-process /usr/bin/dpkg returned an error code (1) -- System Information: Debian Release: 7.7 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable') Architecture: i386 (i686) Kernel: Linux 3.16-0.bpo.3-686-pae (SMP w/2 CPU cores) Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968) Shell: /bin/sh linked to /bin/bash Versions of packages sympa depends on: ii adduser 3.113+nmu3 ii ca-certificates 20130119+deb7u1 ii dbconfig-common 1.8.47+nmu1 ii debconf [debconf-2.0] 1.5.49 ii libarchive-zip-perl 1.30-6 ii libc6 2.13-38+deb7u6 ii libcgi-fast-perl 5.14.2-21+deb7u2 ii libdbd-mysql-perl 4.021-1+b1 ii libdbd-pg-perl2.19.2-2 ii libdbd-sqlite3-perl 1.37-1 ii libdbd-sybase-perl1.14-1 ii libdbi-perl 1.622-1+deb7u1 ii libfcgi-perl 0.74-1+b1 ii libfile-copy-recursive-perl 0.38-1 ii libhtml-format-perl 2.10-1 ii libhtml-stripscripts-parser-perl 1.03-1 ii libhtml-tree-perl 5.02-1 ii libintl-perl 1.20-1 ii libio-stringy-perl2.110-5 ii libmailtools-perl 2.12-1~bpo70+1 ii libmime-charset-perl 1.009.2-1 ii libmime-encwords-perl 1.012.4-1 ii libmime-lite-html-perl1.23-1.1 ii libmime-tools-perl5.505-1~bpo70+1 ii libmsgcat-perl1.03-5+b2 ii libnet-ldap-perl 1:0.4400-1 ii libnet-netmask-perl 1.9016-1 ii libregexp-common-perl 2011121001-1 ii libsoap-lite-perl 0.714-1 ii libtemplate-perl 2.24-1 ii libterm-progressbar-perl 2.13-1 ii libunicode-linebreak-perl 0.0.20120401-1 ii libxml-libxml-perl2.0001+dfsg-1 ii lsb-base 4.1+Debian8+deb7u1 ii mhonarc 2.6.18-2 ii perl 5.14.2-21+deb7u2 ii perl-modules [libcgi-pm-perl] 5.14.2-21+deb7u2 ii postfix [mail-transport-agent]2.11.2-1~bpo70+1 ii rsyslog [system-log-daemon] 7.6.3-2~bpo70+1 ii sqlite3 3.7.13-1+deb7u1 Versions of packages sympa recommends: ii apache2-suexec 2.2.22-13+deb7u3 ii doc-base 0.10.4 ii libapache2-mod-fcgid 1:2.3.6-1.2+deb7u1 ii libcrypt-ciphersaber-perl 0.61-4 ii libfile-nfslock-perl 1.21-1 ii libio-socket-ssl-perl 1.76-2 ii libmail-dkim-perl 0.39-1 ii locales2.13-38+deb7u6 ii logrotate 3.8.1-4 pn mysql-server | postgresql none Versions of packages sympa suggests: ii apache2 2.2.22-13+deb7u3 ii apache2-mpm-prefork [httpd-cgi] 2.2.22-13+deb7u3 pn libauthcas-perl none pn libdbd-oracle-perl none pn
Bug#769073: [duplicate-files] is mark with X for xxperimenta, but in the info the Severity are pedantic,
Hallo Adam, Am Dienstag, den 11.11.2014, 08:17 + schrieb Adam D. Barratt: Control: tags -1 + moreinfo On 2014-11-11 8:05, Jörg Frings-Fürst wrote: X: bitz-server-doc: duplicate-files usr/share/doc/bitz-server- I think the X: in the line above must be a P: or doc/docs/search/all_0.js usr/share/doc/bitz-server- doc/docs/search/functions_0.js [...] N:Severity: pedantic, Certainty: possible the Severity must be experimental. [...] I'm afraid I'm confused. What exactly is the problem that you're requesting be fixed? Regards, Adam CU Jörg -- pgp Fingerprint: 7D13 3C60 0A10 DBE1 51F8 EBCB 422B 44B0 BE58 1B6E pgp Key: BE581B6E CAcert Key S/N: 0E:D4:56 Jörg Frings-Fürst D-54526 Niederkail Threema: SYR8SJXB IRC: j_...@freenode.net j_...@oftc.net signature.asc Description: This is a digitally signed message part
Bug#764904: apophenia: FTBFS - test suite times out or has unexpected failures
By the way, it might be a good idea to remove the /dev/null 21 from the command lines in case the compiler wants to warn you about this sort of thing. (I don't know whether GCC does in this particular case.) Please could you specify the place of this code. I was wrong. The /dev/null 21 comes from libtool and it's only there when the code is compiled for the second time, so no warnings are being suppressed by it. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#769075: unblock: ettercap/1:0.8.1-2
Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: unblock Please unblock package ettercap unblock ettercap/1:0.8.1-2 I'm asking to unblock, mainly because of RC bug #768831 uebdiffcp-0.8.1/debian/changelog ettercap-0.8.1/debian/changelog --- ettercap-0.8.1/debian/changelog 2014-10-18 11:17:12.0 +0200 +++ ettercap-0.8.1/debian/changelog 2014-11-11 09:41:06.0 +0100 @@ -1,3 +1,14 @@ +ettercap (1:0.8.1-2) unstable; urgency=medium + + * Remove byacc | byacc-j | btyacc, not compatible after +the cmake switch. + * Add flex-old as b-d, used with bison++. + * Fix conflicting files in both common and graphical package +(Closes: #768831). + * Remove the gksu dependency, not needed anymore. + + -- Gianfranco Costamagna costamagnagianfra...@yahoo.it Tue, 21 Oct 2014 13:19:19 +0200 + ettercap (1:0.8.1-1) unstable; urgency=medium * New upstream release. diff -Nru ettercap-0.8.1/debian/control ettercap-0.8.1/debian/control --- ettercap-0.8.1/debian/control 2014-10-18 11:17:12.0 +0200 +++ ettercap-0.8.1/debian/control 2014-11-11 09:42:20.0 +0100 @@ -4,12 +4,12 @@ Maintainer: Barak A. Pearlmutter b...@debian.org Uploaders: Murat Demirten mu...@debian.org, Gianfranco Costamagna costamagnagianfra...@yahoo.it -Build-Depends: bison | bison++ | byacc | byacc-j | btyacc, +Build-Depends: bison | bison++, check, chrpath, cmake, debhelper (= 9), - flex, + flex | flex-old, ghostscript, libbsd-dev, libcurl4-openssl-dev, @@ -88,7 +88,6 @@ Replaces: ettercap, ettercap-common, ettercap-gtk, ettercap-text-only Conflicts: ettercap (= 1:0.7.3), ettercap-gtk, ettercap-text-only Provides: ettercap -Recommends: gksu Description: Ettercap GUI-enabled executable Ettercap supports active and passive dissection of many protocols (even encrypted ones) and includes many feature for network and host diff -Nru ettercap-0.8.1/debian/ettercap-common.install ettercap-0.8.1/debian/ettercap-common.install --- ettercap-0.8.1/debian/ettercap-common.install 2014-10-18 11:17:12.0 +0200 +++ ettercap-0.8.1/debian/ettercap-common.install 2014-11-11 09:43:32.0 +0100 @@ -2,9 +2,12 @@ /usr/bin/etterfilter /usr/bin/etterlog /usr/lib/ -/usr/share/ettercap -# The next line accidentally gets +# The next lines accidentally gets +# /usr/share/ettercap/ettercap.png +# /usr/share/ettercap/ettercap-small.png +# /usr/share/ettercap/ettercap.svg # /usr/share/man/ettercap-pkexec* # which belongs in ettercap-graphical. # This is worked around in debian/rules. +/usr/share/ettercap /usr/share/man diff -Nru ettercap-0.8.1/debian/ettercap-graphical.install ettercap-0.8.1/debian/ettercap-graphical.install --- ettercap-0.8.1/debian/ettercap-graphical.install2014-10-18 11:17:12.0 +0200 +++ ettercap-0.8.1/debian/ettercap-graphical.install2014-11-11 09:42:20.0 +0100 @@ -2,7 +2,8 @@ /usr/bin/ettercap-pkexec /usr/share/appdata /usr/share/applications -/usr/share/ettercap/ettercap.png +/usr/share/ettercap/*.png +/usr/share/ettercap/*.svg /usr/share/man/man*/ettercap-pkexec* /usr/share/pixmaps /usr/share/polkit-1 diff -Nru ettercap-0.8.1/debian/rules ettercap-0.8.1/debian/rules --- ettercap-0.8.1/debian/rules 2014-10-18 11:17:12.0 +0200 +++ ettercap-0.8.1/debian/rules 2014-11-11 09:41:06.0 +0100 @@ -56,6 +56,9 @@ dh_install --list-missing @echo The ettercap-pkexec man page belongs in ettercap-graphical -rm --verbose debian/ettercap-common/usr/share/man/man*/ettercap-pkexec* + @echo The ettercap images belongs in ettercap-graphical + -rm --verbose debian/ettercap-common/usr/share/ettercap/*.png + -rm --verbose debian/ettercap-common/usr/share/ettercap/*.svg @echo Upstream does not set RPATH, but the file is not handled by cmake install (dh_auto_install target) chrpath --list debian/ettercap-text-only/usr/bin/ettercap chrpath --delete debian/ettercap-text-only/usr/bin/ettercap -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#767672: closed by Guido Günther a...@sigxcpu.org (Bug#767672: fixed in libvirt 1.2.10~rc2-1)
On 2014-11-03 10:24, Debian Bug Tracking System wrote: #767672: libvirt-daemon-system: fails to purge: rmdir: failed to remove '/var/lib/libvirt/qemu/save': No such file or directory It has been closed by Guido Günther a...@sigxcpu.org. Can you fix this in jessie/sid, too? This blocking piuparts tests for the libvirt-daemon-system rdepends. Thanks Andreas -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#769076: RFS: bitz-server/0.1.6-1 [ITP]
Package: sponsorship-requests Severity: normal Dear mentors, I am looking for a sponsor for my package bitz-server Package name: bitz-server Version : 0.1.6-1 Upstream Author : Uditha Atukorala u...@geniusse.com URL : https://github.com/uditha-atukorala/bitz-server License : GPL-3+ Section : net It builds those binary packages: bitz-server - ICAP server (RFC 3507) implementation in C++ bitz-server-dbg - ICAP server (RFC 3507) implementation in C++ (debug symbols) bitz-server-doc - ICAP server (RFC 3507) implementation in C++ (Documentation) libicap-dev - ICAP server (RFC 3507) implementation in C++ (development files) libicap0 - ICAP server (RFC 3507) implementation in C++ (library files) To access further information about this package, please visit the following URL: http://mentors.debian.net/package/bitz-server Alternatively, one can download the package with dget using this command: dget -x http://mentors.debian.net/debian/pool/main/b/bitz-server/bitz-server_0.1.6-1.dsc Changes since the last upload: * Initial release (Closes: #715022) Regards, Jörg Frings-Fürst -- pgp Fingerprint: 7D13 3C60 0A10 DBE1 51F8 EBCB 422B 44B0 BE58 1B6E pgp Key: BE581B6E CAcert Key S/N: 0E:D4:56 Jörg Frings-Fürst D-54526 Niederkail Threema: SYR8SJXB IRC: j_...@freenode.net j_...@oftc.net signature.asc Description: This is a digitally signed message part
Bug#769077: RFP: fest-assert -- FEST Assertions is a Java library providing a fluent interface for writing assertions
Package: wnpp Severity: wishlist * Package name: fest-assert Version : 2.0M10 Upstream Author : Alex Ruiz * URL : https://github.com/alexruiz/fest-assert-2.x * License : Apache-2.0 Programming Lang: Java Description : FEST Assertions is a Java library providing a fluent unit test assertion interface FEST Assertions is a Java library that provides a fluent interface for writing assertions. It's main goal is to improve test code readability and make maintenance of tests easier. FEST Assertions can be used with either JUnit or TestNG. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#769078: python2.7: Uses literal pkgname in dpkg-query call
Source: python2.7
Version: 2.7.8-11
Severity: important
Hi!
The libpython2.7-stdlib and libpython2.7-minimal packages have this
snipped in their prerm maintscript:
,---
case $1 in
remove)
pc=$(dpkg-query -f '${db:Status-Abbrev} ${binary:Package}\n' -W pkgname
\
| grep -v '^.n' | wc -l)
if [ $pc -le 1 ]; then
remove_bytecode libpython2.7-stdlib:amd64
fi
;;
`---
Which will not match against anything (so always 0 lines), and will
remove the bytecode even when there is more than one instance of the
package. Instead of fixing the dpkg-query call you might want to use
instead the environment variable DPKG_MAINTSCRIPT_PACKAGE_REFCOUNT,
which got introduced in dpkg 1.17.2.
If removing the bytecode for one instance makes python fail to run at
all, you might want to bump the severity to serious.
Thanks,
Guillem
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#768843: fetchmail: Improved TLS support
On Tue, Nov 11, 2014 at 12:49:56AM +0100, Kurt Roeckx wrote: Please have a look at the current state of fetchmail's master (note: it is non-default, so you'll need to git checkout master after cloning) branch in Git, either here https://gitorious.org/fetchmail/fetchmail/source/master: or here: http://sourceforge.net/p/fetchmail/git/ci/master/tree/ I'll try to take a look at this tomorrow. At first look this all looks sane. I just have a few minor comments: - The manpage still talks about using --sslproto TLS1 to enforce STARTTLS in the Secure Socket Layers (SSL) and Transport Layer Security (TLS) section. - README.SSL isn't updated - Please avoid using things like TLSv1_2_client_method() and just disable all lower protocol verions in that case. - I couldn't help but see: const char *default_ciphers = ALL:!EXPORT:!LOW:+RC4:@STRENGTH; That enables a whole bunch of ciphers you don't want, including anoymous ciphers. Kurt -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#761182: xserver-xorg-video-nouveau: NV94: screen black after resume from S3
Control: reassign -1 src:linux 3.16.5-1 Control: fixed -1 3.17-1~exp1 Control: tag -1 upstream fixed-upstream Control: forwarded -1 https://bugs.freedesktop.org/show_bug.cgi?id=83550 On Mon, Nov 10, 2014 at 23:34:56 -0500, Dennis Linnell wrote: I have been suffering similar symptoms. The problem occurs in all the 3.16 kernels through 3.16.5-1, but not in any of the 3.14 kernels, most recently 3.14.15-2. As suggested above, I tried the latest kernel, linux-image-3.17-1-686-pae (3.17-1~exp1) from experimental. That fixed the problem for me. This appears to be the relevant upstream bug report: https://www.libreoffice.org/bugzilla/show_bug.cgi?id=83550 See the patch. It would be nice to see this problem fixed in the jessie 3.16 kernel. That's commit 5838ae610ff36777b8fce6f353c2417980c1a1fa upstream. Cheers, Julien signature.asc Description: Digital signature
Bug#769079: python3.4: Uses literal pkgname in dpkg-query calls
Source: python3.4
Source-Version: 3.4.2-1
Severity: important
Hi!
The libpython3.4-stdlib and libpython3.4-minimal packages have stuff
like this in their prerm (and postrm) maintscripts:
,---
case $1 in
remove)
pc=$(dpkg-query -f '${db:Status-Abbrev} ${binary:Package}\n' -W pkgname
\
| grep -v '^.n' | wc -l)
if [ $pc -le 1 ]; then
remove_bytecode libpython3.4-stdlib:amd64
fi
;;
`---
Which will not match against anything (so always 0 lines), and will
remove the bytecode even when there is more than one instance of the
package. Instead of fixing the dpkg-query call you might want to use
instead the environment variable DPKG_MAINTSCRIPT_PACKAGE_REFCOUNT,
which got introduced in dpkg 1.17.2.
If removing the bytecode for one instance makes python fail to run at
all, you might want to bump the severity to serious.
Thanks,
Guillem
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#768930: unblock: pynag and syslog-nagios-bridge
On 11/11/14 06:05, Clint Byrum wrote: Excerpts from Daniel Pocock's message of 2014-11-10 12:19:19 -0800: On 10/11/14 20:56, Niels Thykier wrote: Control: tags -1 moreinfo On Mon, 10 Nov 2014 10:31:03 +0100 Daniel Pocock dan...@pocock.pro wrote: Package: release.debian.org syslog-nagios-bridge requires pynag 0.9.1+, older versions have a bug in check result file generation: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=768928 I added a constraint in syslog-nagios-bridge well before the freeze so it would not propagate to testing until pynag 0.9.1 was uploaded: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=763378 Note that the pynag upload in unstable is also cleaning out minified jquery and other things that make the package more compliant with Debian policy [...] Hi, I am afraid I will have to reject this request in its current form. The changes to pynag is beyond what can be reasonably reviewed and indeed it is not a targeted fix for #768928. The changes to syslog-nagios-bridge are reasonable and I could accept them, but I understand it is of no use without pynag as well. Can you please provide a targeted fix for pynag? This (just a few lines) could be dropped into debian/patches/checkresult_fix.patch https://github.com/pynag/pynag/commit/3aad1176bca4b2f39c2c851396d30647efbf2bed Clint, would you be happy to upload 0.8.9 with that or would you like me to NMU perhaps? Or is there any reason why the whole 0.9.1 should be considered for jessie? I think we should unblock 0.9.1. Release team have been a bit reluctant to unblock whole new versions without any justification at all In this case though, maybe they can accept that there was a good reason why it wasn't in testing before the freeze: a) 0.9.1 was tagged 5 August b) I sent a private email to Palli on 14 August about the bug and uploading 0.9.1 c) sent follow up and commented on the bug tracker 29 September https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=763378#10 d) noticed Palli's email bouncing on 3 November, you then made the upload immediately, also removing some jquery artifacts to make it more dfsg compliant e) syslog-nagios-bridge is the only dependent package that I know of and I have been testing that against pynag v0.9.1 locally. Do you know of any other packages using pynag as a dependency? It appears that a range of issues were fixed upstream in 0.9.0 and 0.9.1 - do you know if any of these issues justify an unblock for 0.9.1 or maybe the collection of all these issues together justifies an unblock? https://github.com/pynag/pynag/issues?q=is%3Aissue+is%3Aclosed -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#769080: new Evince without title
Package: evince Version: 3.14.1-1 Since the most recent upgrade the evince window doesn't have a title and the usual window decorations anymore. AFAICT it sets some kind of Notitle attribute in the window manager hints. This makes Evince almost unusable. Looks like a transient window, but of course its not. Using Wheezy there is no such problem. Window manager is fvwm2. Regards Harri -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#769078: python2.7: Uses literal pkgname in dpkg-query call
Hi!
On Tue, 2014-11-11 at 09:57:56 +0100, Guillem Jover wrote:
Source: python2.7
Version: 2.7.8-11
Severity: important
The libpython2.7-stdlib and libpython2.7-minimal packages have this
snipped in their prerm maintscript:
Just in case it gets missed, the postrm script is also affected.
,---
case $1 in
remove)
pc=$(dpkg-query -f '${db:Status-Abbrev} ${binary:Package}\n' -W
pkgname \
| grep -v '^.n' | wc -l)
if [ $pc -le 1 ]; then
remove_bytecode libpython2.7-stdlib:amd64
fi
;;
`---
Which will not match against anything (so always 0 lines), and will
remove the bytecode even when there is more than one instance of the
package. Instead of fixing the dpkg-query call you might want to use
instead the environment variable DPKG_MAINTSCRIPT_PACKAGE_REFCOUNT,
which got introduced in dpkg 1.17.2.
If removing the bytecode for one instance makes python fail to run at
all, you might want to bump the severity to serious.
Thanks,
Guillem
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#769081: (pre-approval for) unblock: gst-plugins-ugly1.0/1.4.4-1
Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: unblock Hi, I'd like to upload gst-plugins-ugly1.0 1.4.4-1 to unstable. This is currently in experimental as I wanted it to get out there ASAP without blocking any testing migration if this unblock request is not accepted. 1.4.4 is a bugfix release compared to 1.4.3 and only contains non-risky fixes that were backported from GStreamer's GIT master branch. Attached you can find a diff of 1.4.3-1 to 1.4.4-1. Thanks for your consideration! diff --git a/ChangeLog b/ChangeLog index c41667c..e3d76cf 100644 --- a/ChangeLog +++ b/ChangeLog @@ -1,9 +1,86 @@ +=== release 1.4.4 === + +2014-11-06 Sebastian Dröge sl...@coaxion.net + + * configure.ac: + releasing 1.4.4 + +2014-11-06 12:31:17 +0100 Sebastian Dröge sebast...@centricular.com + + * po/eo.po: + po: Update translations + === release 1.4.3 === -2014-09-24 Sebastian Dröge sl...@coaxion.net +2014-09-24 12:48:29 +0300 Sebastian Dröge sebast...@centricular.com + * ChangeLog: + * NEWS: + * RELEASE: * configure.ac: - releasing 1.4.3 + * docs/plugins/inspect/plugin-a52dec.xml: + * docs/plugins/inspect/plugin-amrnb.xml: + * docs/plugins/inspect/plugin-amrwbdec.xml: + * docs/plugins/inspect/plugin-asf.xml: + * docs/plugins/inspect/plugin-cdio.xml: + * docs/plugins/inspect/plugin-dvdlpcmdec.xml: + * docs/plugins/inspect/plugin-dvdread.xml: + * docs/plugins/inspect/plugin-dvdsub.xml: + * docs/plugins/inspect/plugin-lame.xml: + * docs/plugins/inspect/plugin-mad.xml: + * docs/plugins/inspect/plugin-mpeg2dec.xml: + * docs/plugins/inspect/plugin-realmedia.xml: + * docs/plugins/inspect/plugin-siddec.xml: + * docs/plugins/inspect/plugin-twolame.xml: + * docs/plugins/inspect/plugin-x264.xml: + * docs/plugins/inspect/plugin-xingmux.xml: + * gst-plugins-ugly.doap: + * win32/common/config.h: + Release 1.4.3 + +2014-09-24 11:50:57 +0300 Sebastian Dröge sebast...@centricular.com + + * po/af.po: + * po/az.po: + * po/bg.po: + * po/ca.po: + * po/cs.po: + * po/da.po: + * po/de.po: + * po/el.po: + * po/en_GB.po: + * po/eo.po: + * po/es.po: + * po/eu.po: + * po/fi.po: + * po/fr.po: + * po/gl.po: + * po/hr.po: + * po/hu.po: + * po/id.po: + * po/it.po: + * po/ja.po: + * po/lt.po: + * po/lv.po: + * po/ms.po: + * po/mt.po: + * po/nb.po: + * po/nl.po: + * po/or.po: + * po/pl.po: + * po/pt_BR.po: + * po/ro.po: + * po/ru.po: + * po/sk.po: + * po/sl.po: + * po/sq.po: + * po/sr.po: + * po/sv.po: + * po/tr.po: + * po/uk.po: + * po/vi.po: + * po/zh_CN.po: + Update .po files === release 1.4.2 === diff --git a/Makefile.in b/Makefile.in index 955ee09..02c0e31 100644 --- a/Makefile.in +++ b/Makefile.in @@ -97,7 +97,7 @@ DIST_COMMON = $(top_srcdir)/common/win32.mak \ $(top_srcdir)/configure $(am__configure_deps) \ $(srcdir)/config.h.in $(srcdir)/gst-plugins-ugly.spec.in \ ABOUT-NLS COPYING compile config.guess config.rpath config.sub \ - depcomp install-sh missing ltmain.sh + install-sh missing ltmain.sh subdir = . ACLOCAL_M4 = $(top_srcdir)/aclocal.m4 am__aclocal_m4_deps = $(top_srcdir)/common/m4/as-ac-expand.m4 \ diff --git a/NEWS b/NEWS index 1e5248c..81265e3 100644 --- a/NEWS +++ b/NEWS @@ -1,2 +1,2 @@ -This is GStreamer Ugly Plugins 1.4.3 +This is GStreamer Ugly Plugins 1.4.4 diff --git a/RELEASE b/RELEASE index cda5024..9a27b48 100644 --- a/RELEASE +++ b/RELEASE @@ -1,5 +1,5 @@ -Release notes for GStreamer Ugly Plugins 1.4.3 +Release notes for GStreamer Ugly Plugins 1.4.4 The GStreamer team is pleased to announce a bugfix release of the stable 1.4 release series. The 1.4 release series is adding new features on top @@ -24,6 +24,7 @@ some new features and more intrusive changes that were considered too risky as a bugfix. + When you have to shoot, shoot. Don't talk. @@ -105,6 +106,5 @@ subscribe to the gstreamer-devel list. Contributors to this release - * Guillaume Desmottes * Sebastian Dröge \ No newline at end of file diff --git a/aclocal.m4 b/aclocal.m4 index bc4f5ff..b1ab167 100644 --- a/aclocal.m4 +++ b/aclocal.m4 @@ -103,10 +103,9 @@ _AM_AUTOCONF_VERSION(m4_defn([AC_AUTOCONF_VERSION]))]) # configured tree to be moved without reconfiguration. AC_DEFUN([AM_AUX_DIR_EXPAND], -[dnl Rely on autoconf to set up CDPATH properly. -AC_PREREQ([2.50])dnl -# expand $ac_aux_dir to an absolute path -am_aux_dir=`cd $ac_aux_dir pwd` +[AC_REQUIRE([AC_CONFIG_AUX_DIR_DEFAULT])dnl +# Expand $ac_aux_dir to an absolute path. +am_aux_dir=`cd $ac_aux_dir pwd` ]) # AM_CONDITIONAL-*- Autoconf -*- diff --git a/config.sub b/config.sub index d654d03..bba4efb 100755 --- a/config.sub +++ b/config.sub @@ -2,7 +2,7 @@ # Configuration validation subroutine script. # Copyright 1992-2014 Free Software Foundation, Inc. -timestamp='2014-05-01' +timestamp='2014-09-11' # This file is free software; you can redistribute it and/or modify it # under the terms of the GNU General Public
Bug#766827: dlz_dlopen.h missing from libbind-dev
On 28/10/14 05:00, Michael Gilbert wrote: control: severity -1 important On Sun, Oct 26, 2014 at 2:25 AM, Daniel Pocock wrote: Users are complaining that dlz-ldap-enum is not working again http://list.resiprocate.org/archive/repro-users/msg00780.html I had a quick look and I notice that dlz_dlopen.h is still not installed by the libbind-dev package. I think --with-dlz-ldap=yes is probably a currently missing configure flag that would support that Can you try and see if it is a solution? It looks like you uploaded 1:9.9.5.dfsg-5 to unstable but it is not in Git. Can you please push your branch and your tag to the alioth repository and then I will try to build with that flag? This was definitely working during the wheezy release cycle, is there a specific reason why the flag was removed and is it possible that adding this flag again will cause any other problem for anybody? -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#769085: (pre-approval for) unblock: gst-libav1.0/1.4.4-1
Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: unblock Hi, I'd like to upload gst-libav1.0 1.4.4-1 to unstable. This is currently in experimental as I wanted it to get out there ASAP without blocking any testing migration if this unblock request is not accepted. 1.4.4 is a bugfix release compared to 1.4.3 and only contains non-risky fixes that were backported from GStreamer's GIT master branch. Attached you can find a diff of 1.4.3-1 to 1.4.4-1. Thanks for your consideration! diff --git a/ChangeLog b/ChangeLog index 055e0e8..d645ee2 100644 --- a/ChangeLog +++ b/ChangeLog @@ -1,9 +1,21 @@ +=== release 1.4.4 === + +2014-11-06 Sebastian Dröge sl...@coaxion.net + + * configure.ac: + releasing 1.4.4 + === release 1.4.3 === -2014-09-24 Sebastian Dröge sl...@coaxion.net +2014-09-24 12:50:34 +0300 Sebastian Dröge sebast...@centricular.com + * ChangeLog: + * NEWS: + * RELEASE: * configure.ac: - releasing 1.4.3 + * docs/plugins/inspect/plugin-libav.xml: + * gst-libav.doap: + Release 1.4.3 2014-09-22 14:00:07 -0700 Aleix Conchillo Flaqué aconchi...@gmail.com diff --git a/Makefile.in b/Makefile.in index 3aebc2c..63e110c 100644 --- a/Makefile.in +++ b/Makefile.in @@ -95,8 +95,8 @@ DIST_COMMON = $(top_srcdir)/common/win32.mak \ ChangeLog $(srcdir)/Makefile.in $(srcdir)/Makefile.am \ $(top_srcdir)/configure $(am__configure_deps) \ $(srcdir)/config.h.in $(srcdir)/gst-libav.spec.in COPYING \ - COPYING.LIB TODO compile config.guess config.sub depcomp \ - install-sh missing ltmain.sh + COPYING.LIB TODO compile config.guess config.sub install-sh \ + missing ltmain.sh subdir = . ACLOCAL_M4 = $(top_srcdir)/aclocal.m4 am__aclocal_m4_deps = $(top_srcdir)/common/m4/as-ac-expand.m4 \ diff --git a/NEWS b/NEWS index 6319890..b0d6beb 100644 --- a/NEWS +++ b/NEWS @@ -1,2 +1,2 @@ -This is GStreamer Libav Plugins 1.4.3 +This is GStreamer Libav Plugins 1.4.4 diff --git a/aclocal.m4 b/aclocal.m4 index 089106a..b76e823 100644 --- a/aclocal.m4 +++ b/aclocal.m4 @@ -103,10 +103,9 @@ _AM_AUTOCONF_VERSION(m4_defn([AC_AUTOCONF_VERSION]))]) # configured tree to be moved without reconfiguration. AC_DEFUN([AM_AUX_DIR_EXPAND], -[dnl Rely on autoconf to set up CDPATH properly. -AC_PREREQ([2.50])dnl -# expand $ac_aux_dir to an absolute path -am_aux_dir=`cd $ac_aux_dir pwd` +[AC_REQUIRE([AC_CONFIG_AUX_DIR_DEFAULT])dnl +# Expand $ac_aux_dir to an absolute path. +am_aux_dir=`cd $ac_aux_dir pwd` ]) # AM_CONDITIONAL-*- Autoconf -*- diff --git a/config.sub b/config.sub index d654d03..bba4efb 100755 --- a/config.sub +++ b/config.sub @@ -2,7 +2,7 @@ # Configuration validation subroutine script. # Copyright 1992-2014 Free Software Foundation, Inc. -timestamp='2014-05-01' +timestamp='2014-09-11' # This file is free software; you can redistribute it and/or modify it # under the terms of the GNU General Public License as published by @@ -302,6 +302,7 @@ case $basic_machine in | pdp10 | pdp11 | pj | pjl \ | powerpc | powerpc64 | powerpc64le | powerpcle \ | pyramid \ + | riscv32 | riscv64 \ | rl78 | rx \ | score \ | sh | sh[1234] | sh[24]a | sh[24]aeb | sh[23]e | sh[34]eb | sheb | shbe | shle | sh[1234]le | sh3ele \ @@ -828,6 +829,10 @@ case $basic_machine in basic_machine=powerpc-unknown os=-morphos ;; + moxiebox) + basic_machine=moxie-unknown + os=-moxiebox + ;; msdos) basic_machine=i386-pc os=-msdos @@ -1373,7 +1378,7 @@ case $os in | -cygwin* | -msys* | -pe* | -psos* | -moss* | -proelf* | -rtems* \ | -mingw32* | -mingw64* | -linux-gnu* | -linux-android* \ | -linux-newlib* | -linux-musl* | -linux-uclibc* \ - | -uxpv* | -beos* | -mpeix* | -udk* \ + | -uxpv* | -beos* | -mpeix* | -udk* | -moxiebox* \ | -interix* | -uwin* | -mks* | -rhapsody* | -darwin* | -opened* \ | -openstep* | -oskit* | -conix* | -pw32* | -nonstopux* \ | -storm-chaos* | -tops10* | -tenex* | -tops20* | -its* \ diff --git a/configure b/configure index ecc8e57..85b78d3 100755 --- a/configure +++ b/configure @@ -1,6 +1,6 @@ #! /bin/sh # Guess values for system-dependent variables and create Makefiles. -# Generated by GNU Autoconf 2.69 for GStreamer libav 1.4.3. +# Generated by GNU Autoconf 2.69 for GStreamer libav 1.4.4. # # Report bugs to http://bugzilla.gnome.org/enter_bug.cgi?product=GStreamer. # @@ -591,8 +591,8 @@ MAKEFLAGS= # Identity of this package. PACKAGE_NAME='GStreamer libav' PACKAGE_TARNAME='gst-libav' -PACKAGE_VERSION='1.4.3' -PACKAGE_STRING='GStreamer libav 1.4.3' +PACKAGE_VERSION='1.4.4' +PACKAGE_STRING='GStreamer libav 1.4.4' PACKAGE_BUGREPORT='http://bugzilla.gnome.org/enter_bug.cgi?product=GStreamer' PACKAGE_URL='' @@ -1495,7 +1495,7 @@ if test $ac_init_help = long; then # Omit some internal or obsolete options to make the list less imposing. # This message is too long to be a string in the A/UX 3.1 sh. cat _ACEOF
Bug#768992: unblock: dbus/1.8.10-1
On Mon, Nov 10, 2014 at 17:02:47 +, Simon McVittie wrote: On 10/11/14 16:46, Julien Cristau wrote: On Mon, Nov 10, 2014 at 16:28:28 +, Simon McVittie wrote: The new upstream release does not introduce any changes other than the security fix and the new version metadata, so I imported it as-is rather than doing a trivial backport. If you're OK with that as a general approach to upstream releases whose changes are otherwise OK for stable/frozen testing, I'd like to continue to track the 1.8.x branch for as long as I can (at least until the jessie release, and hopefully afterwards too). I do basically all the releases upstream, so I can be as conservative with their contents as you need me to be. Yes, that's fine. Thanks, Julien signature.asc Description: Digital signature
Bug#769082: (pre-approval for) unblock: gstreamer1.0/1.4.4-1
Control: tags -1 confirmed On 11/11/14 10:06, Sebastian Dröge wrote: Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: unblock Hi, I'd like to upload gstreamer1.0 1.4.4-1 to unstable. This is currently in experimental as I wanted it to get out there ASAP without blocking any testing migration if this unblock request is not accepted. 1.4.4 is a bugfix release compared to 1.4.3 and only contains non-risky fixes that were backported from GStreamer's GIT master branch. Attached you can find a diff of 1.4.3-1 to 1.4.4-1. Go ahead. Emilio -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#769088: RFP: fest-util -- Common utilities for FEST (Fixtures for Easy Software Testing) packages
Package: wnpp Severity: wishlist * Package name: fest-util Version : 1.2.5 Upstream Author : Alex Ruiz * URL : https://github.com/alexruiz/fest-util * License : Apache-2.0 Programming Lang: Java Description : Common utilities for FEST (Fixtures for Easy Software Testing) packages FEST Assertions is a Java library that provides a fluent interface for writing assertions. It's main goal is to improve test code readability and make maintenance of tests easier. FEST Assertions can be used with either JUnit or TestNG. This package contains common utilities used in all FEST packages. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#769087: gnome-tweak-tool: icons on desktop disables program launcher files
Package: gnome-tweak-tool Version: 3.14.0-1 Severity: normal Dear Maintainer, If icons on desktop (Home, Trash, Mounted Volumes) is already turned on at user login, then program launcher files does not work. Test setup: 1. Log in with icons on desktop already turned on. 2. Verify program launcher Files not working. 3. Turn off icons on desktop. 4. Select program launcher Files; it now works. 5. Turn back on icons on desktop. 6. Program launcher files now works regardless of whether desktop items is turned on or off. Expected result: Program launcher files should work regardless of desktop items being on or off. -- System Information: Debian Release: jessie/sid APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 3.16-2-amd64 (SMP w/2 CPU cores) Locale: LANG=en_AU.utf8, LC_CTYPE=en_AU.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages gnome-tweak-tool depends on: ii gir1.2-gnomedesktop-3.03.14.1-1 ii gir1.2-gtk-3.0 3.14.4-1 ii gir1.2-notify-0.7 0.7.6-2 ii gnome-shell-common 3.14.1-1 ii gsettings-desktop-schemas 3.14.1-1 ii python 2.7.8-2 ii python-gi 3.14.0-1 gnome-tweak-tool recommends no packages. gnome-tweak-tool 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#764904: apophenia: FTBFS - test suite times out or has unexpected failures
There are also several places where the value returned from getopt is assigned to a variable of type char before being compared with -1. I would guess that the programs are going into an infinite loop while trying to parse their command-line arguments when char is unsigned. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#769089: RFS: mwc/1.7.2-2 [RC]
Package: sponsorship-requests Severity: important Dear mentors, I am looking for a sponsor for my package mwc Package name: mwc Version : 1.7.2-2 Upstream Author : Michael Till Beck debiang...@gmx.de URL : https://github.com/Debianguru/MailWebsiteChanges License : GPL-2+ Section : utils It builds those binary packages: mwc - Powerful website-tracking tool To access further information about this package, please visit the following URL: http://mentors.debian.net/package/mwc Alternatively, one can download the package with dget using this command: dget -x http://mentors.debian.net/debian/pool/main/m/mwc/mwc_1.7.2-2.dsc More information about hello can be obtained from http://www.example.com. Changes since the last upload: * debian/control: - Replace Depends python-cssselect with python3-cssselect (Closes: #764787). - Bump Standards-Version to 3.9.6 (no changes required). Regards, Jörg Frings-Fürst -- pgp Fingerprint: 7D13 3C60 0A10 DBE1 51F8 EBCB 422B 44B0 BE58 1B6E pgp Key: BE581B6E CAcert Key S/N: 0E:D4:56 Jörg Frings-Fürst D-54526 Niederkail Threema: SYR8SJXB IRC: j_...@freenode.net j_...@oftc.net signature.asc Description: This is a digitally signed message part
Bug#769083: (pre-approval for) unblock: gst-plugins-base1.0/1.4.4-1
Control: tags -1 confirmed On 11/11/14 10:06, Sebastian Dröge wrote: Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: unblock Hi, I'd like to upload gst-plugins-base1.0 1.4.4-1 to unstable. This is currently in experimental as I wanted it to get out there ASAP without blocking any testing migration if this unblock request is not accepted. 1.4.4 is a bugfix release compared to 1.4.3 and only contains non-risky fixes that were backported from GStreamer's GIT master branch. Attached you can find a diff of 1.4.3-1 to 1.4.4-1. Go ahead. Emilio -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#769090: unblock: torsocks/2.0.0-3
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: unblock
Please unblock package torsocks 2.0.0-3, to an important bug (#766306)
that can potentially result in data loss.
This bug is fixed by Fix-improve-Unix-socket-passing-detection.patch
(cherry-picked from upstream), which implied to add the test it creates
(test_fd_passing test) to exclude_test_requiring_network.patch, and later on to
cherry-pick Fix-use-getsockname-instead-of-getsockopt-to-get-soc.patch as well
since the first patch made the package FTBFS on kfreebsd-*.
The debdiff is not absolutely tiny, but you'll notice that most of the lines
added are in the test suite, and more precisely in the test that we disable when
building the Debian package (that test passes here if I temporarily enable
network access in my pbuilder, though).
If it would help to show you the diff resulting from the two cherry-picked
patches combined, so that you don't have to review a diff-of-diff and then
a diff-of-diff that touches the code already modified in the previous one, just
let me know and I'll prepare that.
unblock torsocks/2.0.0-3
diff -Nru torsocks-2.0.0/debian/changelog torsocks-2.0.0/debian/changelog
--- torsocks-2.0.0/debian/changelog 2014-08-24 23:24:58.0 +0200
+++ torsocks-2.0.0/debian/changelog 2014-11-10 23:39:39.0 +0100
@@ -1,3 +1,22 @@
+torsocks (2.0.0-3) unstable; urgency=medium
+
+ * Fix-use-getsockname-instead-of-getsockopt-to-get-soc.patch:
+new patch, cherry-picked from upstream, that fixes the FTBFS
+kfreebsd-* that was introduced by
+Fix-improve-Unix-socket-passing-detection.patch (Closes: #768140).
+
+ -- intrigeri intrig...@debian.org Mon, 10 Nov 2014 23:39:19 +0100
+
+torsocks (2.0.0-2) unstable; urgency=medium
+
+ * Fix-improve-Unix-socket-passing-detection.patch: new patch,
+cherry-picked from upstream (Closes: #766306).
+ * Amend exclude_test_requiring_network.patch to add test_fd_passing test,
+introduced by the new aforementioned patch, to the list of excluded
+tests: it requires network access.
+
+ -- intrigeri intrig...@debian.org Tue, 28 Oct 2014 10:41:10 +0100
+
torsocks (2.0.0-1) unstable; urgency=low
* New upstream release. The 2.0 rewrite is considered stable.
diff -Nru torsocks-2.0.0/debian/patches/exclude_test_requiring_network.patch torsocks-2.0.0/debian/patches/exclude_test_requiring_network.patch
--- torsocks-2.0.0/debian/patches/exclude_test_requiring_network.patch 2014-08-24 23:24:58.0 +0200
+++ torsocks-2.0.0/debian/patches/exclude_test_requiring_network.patch 2014-11-10 23:39:39.0 +0100
@@ -5,9 +5,10 @@
--- a/tests/test_list
+++ b/tests/test_list
-@@ -1,5 +1,4 @@
+@@ -1,6 +1,4 @@
./test_connect
-./test_dns
+-./test_fd_passing
./test_socket
./unit/test_onion
./unit/test_connection
diff -Nru torsocks-2.0.0/debian/patches/Fix-improve-Unix-socket-passing-detection.patch torsocks-2.0.0/debian/patches/Fix-improve-Unix-socket-passing-detection.patch
--- torsocks-2.0.0/debian/patches/Fix-improve-Unix-socket-passing-detection.patch 1970-01-01 01:00:00.0 +0100
+++ torsocks-2.0.0/debian/patches/Fix-improve-Unix-socket-passing-detection.patch 2014-11-10 23:39:39.0 +0100
@@ -0,0 +1,759 @@
+From: David Goulet dgou...@ev0ke.net
+Date: Wed, 22 Oct 2014 15:25:23 -0400
+Bug-Debian: https://bugs.debian.org/766306
+Origin: upstream, https://gitweb.torproject.org/torsocks.git/commit/eb80d5cd10d10158b39c344ad035afe8d31a899f
+Subject: Fix: improve Unix socket passing detection
+
+This commit adds the support for the torsocks recvmsg wrapper to detect
+multiple FDs being passed through a Unix socket.
+
+Furthermore, we now don't exit anymore but simply fire a debug message
+and return EACCES to the caller.
+
+Finally, a test is added for inet socket passing detection called
+test_fd_passing.
+
+Signed-off-by: David Goulet dgou...@ev0ke.net
+---
+ src/lib/recv.c | 132 +---
+ tests/Makefile.am | 5 +-
+ tests/test_fd_passing.c | 520
+ tests/test_list | 1 +
+ 4 files changed, 631 insertions(+), 27 deletions(-)
+ create mode 100644 tests/test_fd_passing.c
+
+diff --git a/src/lib/recv.c b/src/lib/recv.c
+index 036fa91..b034d72 100644
+--- a/src/lib/recv.c
b/src/lib/recv.c
+@@ -26,21 +26,60 @@
+ TSOCKS_LIBC_DECL(recvmsg, LIBC_RECVMSG_RET_TYPE, LIBC_RECVMSG_SIG)
+
+ /*
++ * This is the maximum hardcoded amount of fd that is possible to pass through
++ * a Unix socket in the Linux kernel. On FreeBSD for instance it's MLEN which
++ * is defined to MSIZE (256) minus the msg header size thus way below this
++ * Linux limit. Such a shame there is no way to dynamically get that value or
++ * get it in an exposed ABI...
++ */
++#define SCM_MAX_FD 253
++
++/*
++ * Close all fds in the given array of size count.
++ */
++static void close_fds(int *fds, size_t count)
++{
++ int i;
++
++ for (i = 0; i count; i++) {
++
Bug#769081: (pre-approval for) unblock: gst-plugins-ugly1.0/1.4.4-1
Control: tags -1 confirmed On 11/11/14 10:07, Sebastian Dröge wrote: Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: unblock Hi, I'd like to upload gst-plugins-ugly1.0 1.4.4-1 to unstable. This is currently in experimental as I wanted it to get out there ASAP without blocking any testing migration if this unblock request is not accepted. 1.4.4 is a bugfix release compared to 1.4.3 and only contains non-risky fixes that were backported from GStreamer's GIT master branch. Attached you can find a diff of 1.4.3-1 to 1.4.4-1. Thanks for your consideration! Go ahead. Emilio -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#769084: (pre-approval for) unblock: gst-plugins-good1.0/1.4.4-1
Control: tags -1 confirmed On 11/11/14 10:06, Sebastian Dröge wrote: Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: unblock Hi, I'd like to upload gst-plugins-good1.0 1.4.4-1 to unstable. This is currently in experimental as I wanted it to get out there ASAP without blocking any testing migration if this unblock request is not accepted. 1.4.4 is a bugfix release compared to 1.4.3 and only contains non-risky fixes that were backported from GStreamer's GIT master branch. Attached you can find a diff of 1.4.3-1 to 1.4.4-1. Thanks for your consideration! Go ahead. Emilio -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#769091: git-flow: install zsh completion file to /usr/share/zsh/vendor-completions
Package: git-flow Version: 1.8.0-1 Severity: wishlist Dear Maintainer, Please install the zsh completion file to the appropriate location so that zsh could find it automatically. The included zsh completion might need to be edited so zsh could recognize the git flow subcommand. Kanru -- System Information: Debian Release: jessie/sid APT prefers testing-updates APT policy: (500, 'testing-updates'), (500, 'testing') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.16-3-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages git-flow depends on: ii git [git-core] 1:2.1.1-1 git-flow recommends no packages. git-flow 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#769092: unblock: webkit2gtk/2.6.2+dfsg1-2
Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: unblock Please unblock package webkit2gtk This package contains fixes for two bugs: http://bugs.debian.org/768341 The Flash plugin (and possibly others) can cause a stack buffer overflow. Although the GCC stack protector can detect it, it renders the plugin completely unusable. The fix is trivial and has already been applied upstream. http://bugs.debian.org/767598 This fixes a FTBFS on mips64el. It simply adds support for this platform by adding the __mips64 pre-processor macro to a list of supported machines. It has no effect on other architectures. unblock webkit2gtk/2.6.2+dfsg1-2 -- System Information: Debian Release: jessie/sid APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.16-3-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash diff -Nru webkit2gtk-2.6.2+dfsg1/debian/changelog webkit2gtk-2.6.2+dfsg1/debian/changelog --- webkit2gtk-2.6.2+dfsg1/debian/changelog 2014-10-23 09:18:28.0 + +++ webkit2gtk-2.6.2+dfsg1/debian/changelog 2014-11-10 09:45:07.0 + @@ -1,3 +1,12 @@ +webkit2gtk (2.6.2+dfsg1-2) unstable; urgency=medium + + * debian/patches/fix-mips64-build.patch: ++ Fix mips64el build (Closes: #767598). + * debian/patches/flash-crash.patch: ++ Fix crash in the Flash player (Closes: #768341). + + -- Alberto Garcia be...@igalia.com Mon, 10 Nov 2014 11:44:56 +0200 + webkit2gtk (2.6.2+dfsg1-1) unstable; urgency=medium * New upstream release. diff -Nru webkit2gtk-2.6.2+dfsg1/debian/patches/fix-mips64-build.patch webkit2gtk-2.6.2+dfsg1/debian/patches/fix-mips64-build.patch --- webkit2gtk-2.6.2+dfsg1/debian/patches/fix-mips64-build.patch 1970-01-01 00:00:00.0 + +++ webkit2gtk-2.6.2+dfsg1/debian/patches/fix-mips64-build.patch 2014-11-10 09:45:07.0 + @@ -0,0 +1,55 @@ +From: YunQiang Su wzss...@gmail.com +Subject: Fix build in MIPS64EL +Bug-Debian: http://bugs.debian.org/767598 +Bug: https://bugs.webkit.org/show_bug.cgi?id=124370 +Index: webkitgtk/Source/WTF/wtf/Platform.h +=== +--- webkitgtk.orig/Source/WTF/wtf/Platform.h webkitgtk/Source/WTF/wtf/Platform.h +@@ -80,16 +80,20 @@ + #endif + #endif + +-/* CPU(MIPS) - MIPS 32-bit */ +-/* Note: Only O32 ABI is tested, so we enable it for O32 ABI for now. */ +-#if (defined(mips) || defined(__mips__) || defined(MIPS) || defined(_MIPS_)) \ +- defined(_ABIO32) ++/* CPU(MIPS) - MIPS 32-bit and 64-bit */ ++#if (defined(mips) || defined(__mips__) || defined(MIPS) || defined(_MIPS_) \ ++|| defined(__mips64)) ++#if defined(__mips64) ++#define WTF_CPU_MIPS64 1 ++#define WTF_MIPS_ARCH __mips64 ++#else + #define WTF_CPU_MIPS 1 ++#define WTF_MIPS_ARCH __mips ++#endif + #if defined(__MIPSEB__) + #define WTF_CPU_BIG_ENDIAN 1 + #endif + #define WTF_MIPS_PIC (defined __PIC__) +-#define WTF_MIPS_ARCH __mips + #define WTF_MIPS_ISA(v) (defined WTF_MIPS_ARCH WTF_MIPS_ARCH == v) + #define WTF_MIPS_ISA_AT_LEAST(v) (defined WTF_MIPS_ARCH WTF_MIPS_ARCH = v) + #define WTF_MIPS_ARCH_REV __mips_isa_rev +@@ -662,6 +666,7 @@ + || CPU(ARM64) \ + || CPU(SPARC64) \ + || CPU(S390X) \ ++|| CPU(MIPS64) \ + || CPU(PPC64) \ + || CPU(PPC64LE) + #define WTF_USE_JSVALUE64 1 +Index: webkitgtk/Source/WTF/wtf/dtoa/utils.h +=== +--- webkitgtk.orig/Source/WTF/wtf/dtoa/utils.h webkitgtk/Source/WTF/wtf/dtoa/utils.h +@@ -49,7 +49,7 @@ + defined(__ARMEL__) || \ + defined(_MIPS_ARCH_MIPS32R2) + #define DOUBLE_CONVERSION_CORRECT_DOUBLE_OPERATIONS 1 +-#elif CPU(MIPS) || CPU(PPC) || CPU(PPC64) || CPU(PPC64LE) || OS(WINCE) || CPU(SH4) || CPU(S390) || CPU(S390X) || CPU(IA64) || CPU(SPARC) || CPU(ALPHA) || CPU(ARM64) || CPU(HPPA) ++#elif CPU(MIPS) || CPU(MIPS64) || CPU(PPC) || CPU(PPC64) || CPU(PPC64LE) || OS(WINCE) || CPU(SH4) || CPU(S390) || CPU(S390X) || CPU(IA64) || CPU(SPARC) || CPU(ALPHA) || CPU(ARM64) || CPU(HPPA) + #define DOUBLE_CONVERSION_CORRECT_DOUBLE_OPERATIONS 1 + #elif defined(_M_IX86) || defined(__i386__) + #if defined(_WIN32) diff -Nru webkit2gtk-2.6.2+dfsg1/debian/patches/flash-crash.patch webkit2gtk-2.6.2+dfsg1/debian/patches/flash-crash.patch --- webkit2gtk-2.6.2+dfsg1/debian/patches/flash-crash.patch 1970-01-01 00:00:00.0 + +++ webkit2gtk-2.6.2+dfsg1/debian/patches/flash-crash.patch 2014-11-10 09:45:07.0 + @@ -0,0 +1,19 @@ +From: Alberto Garcia be...@igalia.com +Subject: Fix crash in the Flash plugin +Bug: https://bugs.webkit.org/show_bug.cgi?id=137849 +Bug-Debian: http://bugs.debian.org/768341 +Index: webkitgtk/Source/WebKit2/WebProcess/Plugins/Netscape/x11/NetscapePluginX11.cpp +=== +---
Bug#768292: Let's add the MPLs to /usr/share/common-licenses ? (was Re: Bug#768292: debian-policy: please allow copyright file to refer to license text in separate files)
On 10/11/14 22:41, Charles Plessy wrote: For the avoidance of doubt, I have also counted the numbers for other CC licenses; here is the result. ... CC-BY 1.011 CC-BY 2.0 1 CC-BY 2.533 CC-BY 3.0 311 CC-BY-SA 1.0 2 CC-BY-SA 2.0 32 CC-BY-SA 2.5 16 CC-BY-SA 3.0883 CC-BY-SA 4.0 23 African or European swallow?^W^W^W^W American or international or (etc.) Creative Commons? adwaita-icon-theme, the package that prompted me to open this bug, appears to need CC-BY-SA-3.0-US, CC-BY-SA-3.0-Unported, CC-BY-SA-2.0-IT and CC-BY-3.0-US. Thankfully, the 4.0 series of licenses only seem to have an International version. If CC 4.0 licenses are placed in common-licenses (which I think would be reasonable for 3.0 but not earlier versions, judging by those numbers) then I think the filenames should be CC-BY-SA-3.0-Unported or similar, so that developers don't assume this says CC-BY-SA 3.0, the filename is CC-BY-SA-3.0, it must be the same license. S -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#717636: latex-sanskrit package
Hi,
Vasudev Kamath wrote (13 Oct 2014 11:51:51 GMT) :
On Mon, Oct 13, 2014 at 5:04 PM, intrigeri intrig...@debian.org wrote:
On current sid, with texlive-lang-indic installed:
$ t1disasm
/usr/share/texlive/texmf-dist/fonts/type1/public/sanskrit/sktb10.pfb | grep
start
dup 3 {systemdict /internaldict known not {pop 3} {1183615869 systemdict
/internaldict get exec dup /startlock known {/startlock get exec} {dup
/strtlck
known {/strtlck get exec} {pop 3} ifelse} ifelse} ifelse} executeonly put
... seems to indicate that the bug is still present.
I could reproduce this today again in an up-to-date sid chroot. I see
that sktb10.pf is shipped by the texlive-lang-indic 2014.20141024-1
binary package.
Below is mail snippet between me Jaldhar and Norbert, probably
recorded in texlive mailing list.
Thanks.
[...]
We acked to drop binaries and only ship required source as part of
texlive-lang-indic.
I don't get this part: the file that exposes this bug is still
installed by a binary package. Maybe there are plans to drop it, but
for the time being, it's there.
So yes the bug still holds right but not sure if
it should be reassigned to texlive-lang src or kept on latex-sanskrit.
Well, the bug should be assigned to the binary package that ships the
buggy file, that is texlive-lang-indic. What exactly is making you
doubt that it should be the case?
(/me suspects there's still some misunderstanding going on..)
Cheers,
--
intrigeri
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#769085: (pre-approval for) unblock: gst-libav1.0/1.4.4-1
Control: tags -1 confirmed On 11/11/14 10:07, Sebastian Dröge wrote: Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: unblock Hi, I'd like to upload gst-libav1.0 1.4.4-1 to unstable. This is currently in experimental as I wanted it to get out there ASAP without blocking any testing migration if this unblock request is not accepted. 1.4.4 is a bugfix release compared to 1.4.3 and only contains non-risky fixes that were backported from GStreamer's GIT master branch. Attached you can find a diff of 1.4.3-1 to 1.4.4-1. Thanks for your consideration! Go ahead. Emilio -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#768786: unblock: wxglade/0.6.8-2.2
Dear Julien, I checked the status for wxglade's new package. Here is the head of the page https://qa.debian.org/excuses.php?package=wxglade Excuse for wxglade 13 days old (needed 5 days) Unblock request by jcristau ignored due to version mismatch: 0.6.8-2.2 Unfortunately, I have no idea to fix this mismatch, please can you help? Best regards, Georges. signature.asc Description: Digital signature
Bug#759960: libcatalyst-engine-psgi-perl: FTBFS: dh_auto_test: make -j1 test returned exit code 2
Control: clone -1 -2 Control: reassign -2 libcatalyst-perl Control: retitle -2 Please stop build-depending on libcatalyst-engine-psgi-perl which will be removed On Sat, 25 Oct 2014 at 20:04:19 +0200, gregor herrmann wrote: libmojomojo-perl uploaded with the patch and without the dependency on libcatalyst-engine-psgi-perl, so the latter can be removed from testing (and the archive). Sorry, can't do that yet: smcv@coccia:~$ dak rm -R -n libcatalyst-engine-psgi-perl Will remove the following packages from unstable: libcatalyst-engine-psgi-perl | 0.13+dfsg-2 | source, all Maintainer: Debian Perl Group pkg-perl-maintain...@lists.alioth.debian.org --- Reason --- -- Checking reverse dependencies... # Broken Build-Depends: libcatalyst-perl: libcatalyst-engine-psgi-perl Dependency problem found. Given that Catalyst 5.90069_002's Changes entry says - Removed code related to supporting the long deprecated stand alone PSGI Engine. this build-dependency seems likely to be pointless. The attached debdiff builds successfully, including build-time regression tests. I have not tested it other than that. Regards, S diffstat for libcatalyst-perl-5.90075 libcatalyst-perl-5.90075 changelog |8 control |3 +-- 2 files changed, 9 insertions(+), 2 deletions(-) diff -Nru libcatalyst-perl-5.90075/debian/changelog libcatalyst-perl-5.90075/debian/changelog --- libcatalyst-perl-5.90075/debian/changelog 2014-10-08 20:10:54.0 +0100 +++ libcatalyst-perl-5.90075/debian/changelog 2014-11-11 09:57:24.0 + @@ -1,3 +1,11 @@ +libcatalyst-perl (5.90075-1.1) UNRELEASED; urgency=medium + + * Non-maintainer upload. + * Remove obsolete libcatalyst-engine-psgi-perl build-dependency +so that package can be removed from the archive (Closes: #xx) + + -- Simon McVittie s...@debian.org Tue, 11 Nov 2014 09:56:52 + + libcatalyst-perl (5.90075-1) unstable; urgency=medium [ Salvatore Bonaccorso ] diff -Nru libcatalyst-perl-5.90075/debian/control libcatalyst-perl-5.90075/debian/control --- libcatalyst-perl-5.90075/debian/control 2014-10-08 20:10:54.0 +0100 +++ libcatalyst-perl-5.90075/debian/control 2014-11-11 09:56:47.0 + @@ -2,8 +2,7 @@ Section: perl Priority: optional Build-Depends: debhelper (= 8) -Build-Depends-Indep: libcatalyst-engine-psgi-perl, - libcatalystx-leakchecker-perl, +Build-Depends-Indep: libcatalystx-leakchecker-perl, libcgi-simple-perl, libcgi-struct-xs-perl, libclass-accessor-perl,
Bug#767659: poppler: diff for NMU version 0.26.5-2.1
On Mon, 10 Nov 2014 21:44:58 +0100 Pino Toscano p...@debian.org wrote: Please drop this NMU, since the approach chosen (bumping shlibs for everybody) is not correct. We once had a very similar issue in the ffmpeg, ne libav packaging, where we had to declare much stricter dependencies among the packaged libraries than we had to expose to external packages linking to them. We solved this by calling dh_makeshlibs twice: First, before calling dh_shlibdeps, with very strict dependency information. And then again, after calling dh_shlibdeps, with the relaxed dependency information that other packages should see. Maybe you could consider this approach. Cheers, Fabian -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#767481: nwchem crashes with sigill on amd E-350
Hi, On Mon, Nov 10, 2014 at 08:22:25PM +0100, fulvio ciriaco wrote: I tried the mentioned nostrip package. Attached please find the gdb session report. Not that much! I think I figured out what the problem is: the Makefile patching did not go far enough so far, so in some circumstances, compile flags like -mfpmath=sse or -march=native -mtune=native leaked into the compile command-line, leading to bad binaries. I hope I patched those out now, can you try the packages here: http://people.debian.org/~mbanck/nwchem_6.5+r26243-3_amd64.deb http://people.debian.org/~mbanck/nwchem-data_6.5+r26243-3_all.deb Michael -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#769094: deprecated defined(%hash) calls
Package: irssi-scripts Version: 20131030 Severity: minor Various scripts use deprecated defined(%hash) calls, e.g. scriptassist.pl: lines 97, 207, 689, 690, 777, 857, and 1090 trigger.pl: lines 716 and 725 -- System Information: Debian Release: jessie/sid APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 3.16-2-amd64 (SMP w/8 CPU cores) Locale: LANG=en_NZ, LC_CTYPE=en_NZ.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash -- .''`. martin f. krafft madduck@d.o @martinkrafft : :' : proud Debian developer `. `'` http://people.debian.org/~madduck `- Debian - when you have better things to do than fixing systems digital_signature_gpg.asc Description: Digital signature (see http://martin-krafft.net/gpg/sig-policy/999bbcc4/current)
Bug#763043: qemu-user-binfmt: binfmt support broken - package empty, foreign binaries do not run
Excerpts from Michael Tokarev's message of Tue Nov 11 09:15:15 +0100 2014: 11.11.2014 11:02, Michal Suchanek wrote: [] I found that I have qemu-user-static instead of qemu-user-binfmt on system where this works. I can run armhf binaries on a PC but the Yes, I've seen that. reverse does not work. There is a handler for PC binaries registered but bash still reports it cannot execute binary file. Is the magic for PC binaries correct? How do I check? I replied to that at the time, -- the same magic strings are used in both packages (qemu-user-static and qemu-user-binfmt), these are generated (using simple substitutions) from a common file. Yes, neither works, unsurprisingly. Hello Michal. A friendly ping? Do you have any additional information for this bugreport? I can't do anything with it without your input... I did send another email in the bug report, right? Yes, and I replied to that, see https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=763043#22 So, to rehash, do I understand it right that you're having probs with running x86 binaries on arm, when using -user-binfmt but not when using -user-static ? I am having problem running x86 binaries on arm with either package. # strace ./app execve(./app, [./app], [/* 17 vars */]) = -1 ENOEXEC (Exec format error) write(2, strace: exec: Exec format error\n, 32strace: exec: Exec format error ) = 32 exit_group(1) = ? +++ exited with 1 +++ # file app app: ELF 64-bit LSB executable, x86-64, version 1 (GNU/Linux), statically linked, stripped # uname -a Linux sun5i 3.4.103+ #36 PREEMPT Thu Aug 28 17:40:10 CEST 2014 armv7l GNU/Linux There is probably problem with static binaries: # apt-get install unrar:amd64 ... ldconfig: /lib/x86_64-linux-gnu/libz.so.1 is for unknown machine 62. ... ldconfig: /lib/ld-linux.so.2 is for unknown machine 3. ... # unrar /? qemu: uncaught target signal 11 (Segmentation fault) - core dumped Segmentation fault # apt-get install cdebootstrap-static:amd64 # cdebootstrap-static /? -bash: /usr/bin/cdebootstrap-static: cannot execute binary file Thanks Michal -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#768937: [Pkg-zsh-devel] Bug#768937: zsh: [patch] not binNMU-safe due to --link-doc between arch-dep and arch-indep
On 11/11/14 02:10, Axel Beckert wrote: I'm not yet sure what's the culprit, but after applying your patch (without the changelog) to the current HEAD of our packging git repo, the installation of zsh-common always aborts as follows: Preparing to unpack zsh-common_5.0.7-4_all.deb ... Unpacking zsh-common (5.0.7-4) over (5.0.7-3+0~2014001757.238~1.gbp353e05) ... dpkg: error processing archive zsh-common_5.0.7-4_all.deb (--install): unable to open '/usr/share/doc/zsh-common/ChangeLog-3.0.gz.dpkg-new': No such file or directory Huh. Sorry, it worked for me... I currently suspect that dpkg-maintscript-helper may be confused because because /usr/share/doc/zsh is now a directory inside zsh _and_ zsh-common. Perhaps. If that's the case, one way to solve it would be to move the symlinks from zsh-common into zsh; but because they're built in separate Makefile targets, and some of the target files are compressed whereas others aren't, that would involve either some awkward hard-coding, or doing zsh-common's dh_installdocs, dh_installchangelogs, dh_installexamples and dh_compress even though not actually building zsh-common. At this point I would be very tempted to duplicate NEWS.Debian and README.Debian in the zsh package, not bother with symlinks for the rest, and mention in README.Debian that various extra bits of documentation, including the upstream changelog, can now be found in /usr/share/doc/zsh-common. A lot of the zsh-common documents seem like they should be in zsh-doc anyway (historic changelogs, credits, development style guides, META-FAQ, zsh.texi.gz, etc.) or even not packaged (FTP-README, MACHINES); see also #469521. The release team would probably not be delighted by that change at this stage of the release process, though. S -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#767370: does not start debconf, displays debconf commands and waits for input
On Mon, November 10, 2014 21:46, Thomas Liske wrote: What can I do to help debug this? Good question. I'm unable to reproduce it on any of my maschines nor do I have any idea why this happens. Maybe we require some debconf guru helping us to dig into it? Maybe.. I'm not a debconf guru either. Other package configuration does work, jftr. Could you provide a full `needrestart -v` output? [Core] Using UI 'NeedRestart::UI::stdio'... [main] #3237 uses obsolete binary /sbin/getty [main] #3237 is not a child [main] #7307 uses obsolete binary /usr/bin/screen [main] #7307 is not a child [main] #7308 uses obsolete binary /bin/bash [main] #7308 is a child of #7307 [main] #7311 uses obsolete binary /usr/bin/irssi [main] #7311 is a child of #7308 [main] #11771 uses obsolete binary /usr/sbin/sshd [main] #11771 is not a child [main] #11773 uses obsolete binary /usr/sbin/sshd [main] #11773 is a child of #11771 [main] #17604 uses obsolete /lib/i386-linux-gnu/i686/cmov/libnss_files-2.19.so [main] #17604 is not a child [main] #17799 uses obsolete /lib/i386-linux-gnu/i686/cmov/libnss_files-2.19.so [main] #17799 is not a child [main] #17851 uses obsolete /lib/i386-linux-gnu/i686/cmov/libnss_files-2.19.so [main] #17851 is not a child [main] #3237 exe = /sbin/getty [main] #3237 running /etc/needrestart/hook.d/10-dpkg [main] #3237 package: util-linux [main] #3237 rc.d script hwclock.sh should not start in the current run-level(2) [main] #3237 running /etc/needrestart/hook.d/20-rpm [main] #3237 running /etc/needrestart/hook.d/90-none [main] #7307 exe = /usr/bin/screen [main] #7307 running /etc/needrestart/hook.d/10-dpkg [main] #7307 package: screen [main] #7307 rc.d script screen-cleanup should not start in the current run-level(2) [main] #7307 running /etc/needrestart/hook.d/20-rpm [main] #7307 running /etc/needrestart/hook.d/90-none [main] #7308 exe = /bin/bash [main] #7308 running /etc/needrestart/hook.d/10-dpkg [main] #7308 package: bash [main] #7308 running /etc/needrestart/hook.d/20-rpm [main] #7308 running /etc/needrestart/hook.d/90-none [main] #11771 exe = /usr/sbin/sshd [main] #11771 running /etc/needrestart/hook.d/10-dpkg [main] #11771 package: openssh-server [main] #11771 running /etc/needrestart/hook.d/20-rpm [main] #11771 running /etc/needrestart/hook.d/90-none [main] #17604 exe = /lib/systemd/systemd-udevd [main] #17604 running /etc/needrestart/hook.d/10-dpkg [main] #17604 package: udev [main] #17604 rc.d script udev-finish should not start in the current run-level(2) [main] #17604 rc.d script udev should not start in the current run-level(2) [main] #17604 running /etc/needrestart/hook.d/20-rpm [main] #17604 running /etc/needrestart/hook.d/90-none [main] #17799 exe = /usr/sbin/rsyslogd [main] #17799 running /etc/needrestart/hook.d/10-dpkg [main] #17799 package: rsyslog [main] no pidfile reference found at rsyslog [main] #17851 exe = /usr/sbin/atd [main] #17851 running /etc/needrestart/hook.d/10-dpkg [main] #17851 package: at [main] no pidfile reference found at atd [Kernel] Linux: kernel release 3.13.7, kernel version #1 SMP Mon Mar 24 17:07:35 CET 2014 Failed to load NeedRestart::Kernel::kFreeBSD: [Kernel/kFreeBSD] Not running on GNU/kFreeBSD! [Kernel/Linux] Did not find any kernel images. Failed to retrieve available kernel versions. Services to be restarted: Restart atd? [Ynas] [ ok ] Stopping deferred execution scheduler: atd. [ ok ] Starting deferred execution scheduler: atd. Restart rsyslog? [Ynas] [ ok ] Stopping enhanced syslogd: rsyslogd. [ ok ] Starting enhanced syslogd: rsyslogd. Interesting: it doesn't fail when running with -v. But doesn't use my standard dialog frontend either... Thijs -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#769095: dkms: Add script for autopkgtesting DKMS packages
Package: dkms
Version: 2.2.0.3-2
Severity: wishlist
Tags: patch
User: ubuntu-de...@lists.ubuntu.com
Usertags: origin-ubuntu ubuntu-patch vivid
User: autopkgtest-de...@lists.alioth.debian.org
Usertags: autopkgtest
Hello,
With autodep8 [1] we can now generate autopkgtest metadata for entire
classes of similar packages, such as the already existing Perl/Ruby
ones. We should do the same for DKMS, to check that a particular DKMS
package builds against our default kernel, installs correctly, and has
sufficient dependencies.
This new script provides a general test for DKMS packages. It was
derived from Ubuntu's tailored scripts [2], but we are moving that to
autopkgtest to avoid custom infrastructure and run everything in the
same way. When applying it, please take care to chmod it to 755.
The other half of this is to teach autodep8 to recognize a DKMS
package and generate test metadata. That happens in [3].
After that, one can do
adt-run dkms_2.2.0.3-2dkms1_all.deb sl-modem --- schroot sid
to test e. g. sl-modem, where dkms_2.2.0.3-2dkms1_all.deb is the
locally built dkms with this patch applied. Once that's in the
archive, that argument gets dropped of course.
Thanks for considering,
Martin
[1] https://packages.debian.org/sid/autodep8
[2] https://jenkins.qa.ubuntu.com/view/DKMS/?
[3] https://bugs.debian.org/78
--
Martin Pitt| http://www.piware.de
Ubuntu Developer (www.ubuntu.com) | Debian Developer (www.debian.org)
* Add debian/scripts/dkms-autopkgtest script: Common autopkgtest script for
testing a dkms source package.
diff -Nru dkms-2.2.0.3/debian/install dkms-2.2.0.3/debian/install
--- dkms-2.2.0.3/debian/install 2014-01-15 12:55:33.0 +0100
+++ dkms-2.2.0.3/debian/install 2014-10-24 00:11:06.0 +0200
@@ -2,3 +2,4 @@
debian/scripts/dh_dkms.1usr/share/man/man1/
debian/scripts/*-dkms usr/share/debhelper/autoscripts/
debian/scripts/dkms.pm usr/share/perl5/Debian/Debhelper/Sequence/
+debian/scripts/dkms-autopkgtest usr/lib/dkms/
diff -Nru dkms-2.2.0.3/debian/scripts/dkms-autopkgtest
dkms-2.2.0.3/debian/scripts/dkms-autopkgtest
--- dkms-2.2.0.3/debian/scripts/dkms-autopkgtest1970-01-01
01:00:00.0 +0100
+++ dkms-2.2.0.3/debian/scripts/dkms-autopkgtest2014-10-24
18:10:01.0 +0200
@@ -0,0 +1,66 @@
+#!/bin/sh
+# Common autopkgtest script for testing a dkms source package.
+# Author: Martin Pitt martin.p...@ubuntu.com
+# Copyright: (C) 2014 Canonical Ltd.
+set -eu
+
+run_pkg() {
+pkg=$1
+
+echo I: Installing binary package $pkg
+export DEBIAN_FRONTEND=noninteractive
+RC=0
+apt-get install -yq $pkg /dev/null || RC=$?
+# collect build logs as artifacts
+(cd /var/lib/dkms; find -name make.log -print0 | xargs -0 tar c)
$ADT_ARTIFACTS/$pkg-make-logs.tar
+
+if [ $RC -ne 0 ]; then
+echo E: Package $pkg failed to install 2
+exit 1
+fi
+
+echo I: Testing binary package $pkg
+
+if ! dkms_conf=$(dpkg -L $pkg | grep 'dkms.conf$'); then
+echo I: Package $pkg has no dkms.conf, skipping
+return
+fi
+dkms_pkg=$(bash -c . $dkms_conf; echo \$PACKAGE_NAME 2/dev/null)
+
+echo I: Testing if $dkms_pkg modules are correctly installed
+dkmsstatus=$(dkms status $dkms_pkg)
+if [ -z $dkmsstatus ]; then
+echo E: dkms status output is empty! 2
+exit 1
+fi
+echo $dkmsstatus
+
+if ! echo $dkmsstatus | grep -q installed$; then
+echo E: not installed 2
+exit 1
+fi
+
+# skip modprobing for now; this fails too often (needs particular
+# hardware/firmware/etc)
+# for mod in $(awk -F '' '/^BUILT_MODULE_NAME/ {print $2}' $dkms_conf); do
+# echo I: modprobe $mod
+# if ! modprobe $mod; then
+# echo E: Failed to modprobe module $mod 2
+# exit 1
+# else
+# echo I: $modname loaded
+# fi
+# done
+}
+
+# Try and remove dkms to spot packages which miss a dkms dependency
+dpkg --remove dkms || true
+
+for pkg in $(awk '/^Package:/ { print $2 }' debian/control); do
+# package might be arch: restriction or udeb etc.
+if ! apt-cache show $pkg /dev/null 21; then
+echo I: Skipping unavailable package $pkg
+continue
+fi
+run_pkg $pkg
+done
signature.asc
Description: Digital signature
Bug#769086: (pre-approval for) unblock: gst-plugins-bad1.0/1.4.4-1
Control: tags -1 confirmed On Tue, 11 Nov 2014 10:07:07 +0100 Sebastian =?ISO-8859-1?Q?Dr=F6ge?= sl...@debian.org wrote: Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: unblock Hi, I'd like to upload gst-plugins-bad1.0 1.4.4-1 to unstable. This is currently in experimental as I wanted it to get out there ASAP without blocking any testing migration if this unblock request is not accepted. 1.4.4 is a bugfix release compared to 1.4.3 and only contains non-risky fixes that were backported from GStreamer's GIT master branch. Attached you can find a diff of 1.4.3-1 to 1.4.4-1. Note that the bigger changes in gst-libs/gst/gl/cocoa and sys/applemedia are irrelevant for Debian and only apply to Mac OS X and iOS. Thanks for your consideration! Ack. Emilio -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#768831: ettercap-common, ettercap-graphical: shipping the same file: usr/share/ettercap/ettercap.png
On 2014-11-10 14:22, Gianfranco Costamagna wrote: There are two packages (not coinstallable) that both depends on the common one. So you can have ettercap-graphical with ettercap-common and you can have ettercap-text-only with ettercap-common. They both provide ettercap, and they both depend on the common package. packages were also renamed, and some packages disappeared in the meanwhile (ettercap-plugins, ettercap-gtk) this new package split is from 0.7.3, how do you suggest to fix? So you can simplify the package relationships using the virtual ettercap package (these must be unversioned relationships) Provides: ettercap Conflicts: ettercap Replaces: ettercap in both ettercap-graphical and ettercap-text-only. That means only one package providing (or being called) ettercap can be installed at a time. No need to have additionally Conflicts+Replaces: ettercap-other-current-implementation but keep the Conflicts+Replaces: ettercap-gtk to ensure the ancient stuff goes away. (Do you need that for ettercap-plugins, too?) ettercap-graphical will also need versioned Breaks+Replaces: ettercap-common ( 1:0.8.1-2~) for finally taking over the .png file as only owner. If you get these changes into jessie, you clean clean this up for jessie+1 (or jessie+2) and only keep the Provides/Conflicts/Replaces: ettercap since the conflicting stuff is no longer in (old-)stable. I'm proposing this debdiff, I didn't notice any upgrade path issues, and I moved the files in the graphic package besides debian/control (discussed above) this looks good BTW, why are ettercap-graphical and ettercap-textonly not co-installable? Sounds like a candidate for renaming the binaries from ettercap to ettercap-foo and using alternatives to provide the ettercap binary. But that should not be considered now, only after the jessie release for jessie+1. Andreas -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#767659: poppler: diff for NMU version 0.26.5-2.1
On 11/11/14 10:08, Fabian Greffrath wrote: On Mon, 10 Nov 2014 21:44:58 +0100 Pino Toscano p...@debian.org wrote: Please drop this NMU, since the approach chosen (bumping shlibs for everybody) is not correct. If the new symbol is public API that (in principle) other packages could use, which AFAICS it is, then I think the only solution that doesn't involve bumping shlibs for everyone is a symbols file. It could probably be as simple as something like this (untested, syntax might be wrong): libpoppler.so.46 libpoppler46 #MINVER# * Build-Depends-Package: libpoppler-dev (c++)GfxFont::getAlternateName(char const*) 0.26.5-2~ (regex). #CURVER# to assign a different version for that one symbol? On 11/11/14 10:08, Fabian Greffrath wrote: We solved this by calling dh_makeshlibs twice: First, before calling dh_shlibdeps, with very strict dependency information. And then again, after calling dh_shlibdeps, with the relaxed dependency information that other packages should see. For symbols that are considered private to the source package, that seems unnecessarily complex; you can use debian/shlibs.local to give binary packages within the same source package a strict dependency. S -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#769096: bareos-storage: unowned files after purge (policy 6.8, 10.8): /etc/bareos/.rndpwd
Package: bareos-storage Version: 14.2.1+20141017gitc6c5b56-3 Severity: important User: debian...@lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed your package left unowned files on the system after purge, which is a violation of policy 6.8 (or 10.8): http://www.debian.org/doc/debian-policy/ch-maintainerscripts.html#s-removedetails Filing this as important as having a piuparts clean archive is a release goal since lenny. From the attached log (scroll to the bottom...): 0m32.2s ERROR: FAIL: Package purging left files on system: /etc/bareos/.rndpwdnot owned /root/.rnd not owned Don't worry about /root/.rnd, that is an openssl artefact. cheers, Andreas bareos-storage_14.2.1+20141017gitc6c5b56-3.log.gz Description: application/gzip
Bug#685353: qemu-kvm 1.1.1 hangs using 100% CPU when using ES1370 emulation
Hi Michael, * Michael Tokarev schrieb: [ http://bugs.debian.org/685353 ] 05.09.2012 17:48, Mike Gerber wrote: Unfortunately I can't currently as this is going into daily use now with the working configuration and I don't really have a different machine at hand to reproduce this. The problem is that it takes up to two days to hit this bug... Hello Mike, Malc, others. So, has anything changed since qemu-kvm v.1.1 in this context of 44-vs-48 KHz audio frequency? Mike, did you try more recent version of qemu (2.1 currently)? Malc, did you do anything with this in the code between 1.1 and 2.1 versions, or do you know any changes which may affect this in the mentioned version-frame? No, I'm still using 1.1 (1.1.2+dfsg-6+deb7u5 on Debian 7) and had no issues since then. The system is in daily use, streaming from the soundcard on the host through the sound emulation on the guest for hours a day. Mike -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#769097: fai-quickstart: unowned files after purge (policy 6.8, 10.8): /var/lib/nfs/{.[ex]tab., export-}lock
Package: fai-quickstart Version: 4.3 Severity: important User: debian...@lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed your package left unowned files on the system after purge, which is a violation of policy 6.8 (or 10.8): http://www.debian.org/doc/debian-policy/ch-maintainerscripts.html#s-removedetails Filing this as important as having a piuparts clean archive is a release goal since lenny. From the attached log (scroll to the bottom...): 0m39.7s ERROR: FAIL: Package purging left files on system: /var/lib/nfs/.etab.locknot owned /var/lib/nfs/.xtab.locknot owned /var/lib/nfs/export-lock not owned I assume this is fai-quickstart leaving them since I didn't see anything like this in the nfs packages. cheers, Andreas fai-quickstart_4.3.log.gz Description: application/gzip
Bug#768936: ITP: nufft -- Library implementing the Non-Uniform Fast Fourier Transform
Chris Bannister wrote: Ghislain Antony Vaillant wrote: Package: wnpp Severity: wishlist Owner: Ghislain Antony Vaillant ghisv...@gmail.com * Package name: nufft Version : 1.3.3 Upstream Author : Leslie Greengard greeng...@cims.nyu.edu * URL : http://www.cims.nyu.edu/cmcl/nufft/nufft.html * License : BSD Programming Lang: FORTRAN Description : Library implementing the Non-Uniform Fast Fourier Transform Implementation of the Non-Uniform Fast Fourier Transform (NUFFT) coded in FORTRAN using a fast, procedural, algorithm. ^ ^ Compared to existingly packaged solutions, like the NFFT library, the NUFFT provides Octave (and MATLAB) compatible bindings. Because of the procedural implementation, usage of the NUFFT is more straightforward. However, it lacks support for high dimensionality than 3 and support for precomputation in case ^^ I think that would be better worded as dimensions greater than three or similar. Agreed. Also, surplus commas in the first paragraph; and I'd recommend rearranging it to avoid the misreading that it was coded using this algorithm. This is a FORTRAN implementation of the Non-Uniform Fast Fourier Transform (NUFFT) using a fast procedural algorithm. Then in the second paragraph, existingly packaged has got to go; and that first sentence never does explicitly compare anything - it's only implied that NFFT doesn't provide these bindings. Say: Unlike solutions such as the NFFT library, the NUFFT provides Octave (and MATLAB) compatible bindings. [...] Then at the end: support for high dimensionality than 3 and support for precomputation in case a transform needs to be repeated. As a result both the NFFT and NUFFT package may coexist as they fit different needs. Nitpicking, it lacks support for A and support for B is needless repetition, the in case should be in the case that or simply if, and both [...] may coexist is redundant and sounds as if you don't know whether in fact they do exist. So: This is a FORTRAN implementation of the Non-Uniform Fast Fourier Transform (NUFFT) using a fast procedural algorithm. . Unlike solutions such as the NFFT library, the NUFFT provides Octave (and MATLAB) compatible bindings. Because of the procedural implementation, usage of the NUFFT is more straightforward. However, it lacks support for dimensions greater than three or for precomputation if a transform needs to be repeated. As a result the NFFT and NUFFT packages fit different needs and can coexist. -- JBR with qualifications in linguistics, experience as a Debian sysadmin, and probably no clue about this particular package -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#769098: gforge-common: unowned files after purge (policy 6.8, 10.8): /etc/fusionforge/config.ini.d/debian-install{, -secrets}.ini
Package: gforge-common Version: 5.3.2+20141104-1 Severity: important User: debian...@lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed your package left unowned files on the system after purge, which is a violation of policy 6.8 (or 10.8): http://www.debian.org/doc/debian-policy/ch-maintainerscripts.html#s-removedetails Filing this as important as having a piuparts clean archive is a release goal since lenny. From the attached log (scroll to the bottom...): 0m41.9s ERROR: FAIL: Package purging left files on system: /etc/fusionforge/ owned by: gforge-common /etc/fusionforge/config.ini.d/ owned by: gforge-common /etc/fusionforge/config.ini.d/debian-install-secrets.ini not owned /etc/fusionforge/config.ini.d/debian-install.ini not owned cheers, Andreas gforge-common_5.3.2+20141104-1.log.gz Description: application/gzip
Bug#769099: ark: crashes trying to add file to existing zip archive
Package: ark Version: 4:4.14.2-1 Severity: important Dear Maintainer, The simplest possible testcase is: - creating two textfiles - making a zip-archive of one of these file - using 'right-click-functionality' in dolphin Compress as ZIP-Archive - opening archive with ark and trying to add other textfile using 'Add File'-button Result is ark crashing with following message: Setting the format failed with the following error: No such format -- System Information: Debian Release: jessie/sid APT prefers testing-updates APT policy: (500, 'testing-updates'), (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 3.16-3-amd64 (SMP w/1 CPU core) 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 ark depends on: ii kde-runtime 4:4.14.2-1 ii libarchive13 3.1.2-9 ii libc6 2.19-12 ii libkdecore5 4:4.14.2-3 ii libkdeui5 4:4.14.2-3 ii libkfile4 4:4.14.2-3 ii libkhtml5 4:4.14.2-3 ii libkio5 4:4.14.2-3 ii libkonq5abi1 4:4.14.2-1 ii libkparts44:4.14.2-3 ii libkpty4 4:4.14.2-3 ii libqt4-dbus 4:4.8.6+git64-g5dc8b2b+dfsg-2+b1 ii libqtcore44:4.8.6+git64-g5dc8b2b+dfsg-2+b1 ii libqtgui4 4:4.8.6+git64-g5dc8b2b+dfsg-2+b1 ii libstdc++64.9.1-19 Versions of packages ark recommends: ii bzip2 1.0.6-7+b1 pn p7zip-full none ii unzip 6.0-12+b1 ii zip 3.0-8 Versions of packages ark suggests: pn rar none pn unrar | unrar-free 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#760377: confirm apache 1 and gpl-1+ situation
[Re-sending with the necessary Ccs, sorry for the duplicate on debian-legal.] On 11/11/14 06:44, Florian Weimer wrote: http://anonscm.debian.org/cgit/collab-maint/xmlrpc-c.git/tree/tools/turbocharger/mod_gzip.c?h=debian-sid I don't think this file is even compiled, so its license does not matter. I believe the ftp-masters' current interpretation of the DFSG is that unused files in source packages are still required to be under a DFSG license, or be removed. However, if this file is not compiled, its license does not matter other than it's some DFSG license, and it's mentioned in the copyright file. (Insert a #error to confirm that it isn't compiled? :-) S -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#766668: Add support for dkms packages
Control: tag -1 pending Hello Jean-Baptiste, Jean-Baptiste Lallement [2014-10-24 13:39 -0400]: The attached patch adds support for dkms packages. The test command dkms-autopkgtest will be in the dkms package. Thanks for this! I now filed a bug against dkms for the new dkms-autopkgtest script: https://bugs.debian.org/769095 I committed your patch with massaging the changelog a bit (referring to bugs). I also dropped the isolation-machine and breaks-testbed restrictions as we disabled the actual modprobing in the end (as it's not reliably possible to do so even in a VM). http://anonscm.debian.org/cgit/collab-maint/autodep8.git/commit/?id=770b973c I won't upload this right now, as I'd like to see this land in dkms first. Thanks, Martin -- Martin Pitt| http://www.piware.de Ubuntu Developer (www.ubuntu.com) | Debian Developer (www.debian.org) signature.asc Description: Digital signature
Bug#758096: Blends in D-I tasksel selection? (Was: Filed Bug#758096: tasksel: Allow to select specific packages during installation - just DE, Web server, Mail server is NOT enough)
Hi, I guess the sad news that Joey Hess leaves Debian has spread also to Debian Blends list. The direct consequence for Blends is that Joey will not work on this bug (#758096) and will also most probably not rise any opinion on it any more but we somehow need to move on. I realised that the changelog says: ... tasksel (3.23) unstable; urgency=medium ... * Added a Parent field, which results in a simple nested hierarchy display. (Currently only one level deep, and not collapsible since debconf doesn't have an appropriate widget.) ... * Removed mail-server, dns-server, database-server, file-server tasks, which were not well enough defined to be useful and whose menu space will be better used for blends or openstack tasks. Closes: #604100 ... which according to Git (git://git.debian.org/git/tasksel/tasksel.git) relates to this commit. commit 9e2290b531e414ffb16e89b50cf5c44413fa71b8 Author: Joey Hess j...@kitenet.net Date: Sun Sep 7 22:45:02 2014 -0400 hierarchical tasks, desktop selection, and general massive changes ... * Added a Parent field, which results in a simple nested hierarchy display. (Currently only one level deep, and not collapsable since debconf doesn't have an appropriate widget.) ... * Removed mail-server, dns-server, database-server, file-server tasks, which were not well enough defined to be useful and whose menu space will be better used for blends or openstack tasks. ... This again shows Joey's great way to deal with things by simply working at something rather than doing a lot of talk. I really appreciate this - another thanks to Joey. As far as I can see without testing this means regarding the display of Blends in D-I (#758096) that we only need to *decide* and in case we want to do this add the needed bits of data. Any opinions regarding a decision? Kind regards Andreas. PS: I'll be AFK from 19. Nov to 3. Dez. -- 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#768998: Bug #768998: kadu-mime-tex: FTBFS on all arches
Control: found -1 1.0-1 Control: block -1 by 767010 Hi, The build logs clearly show that this affects version 1.0-1 in testing as well. It seems to be caused by bug #767010 which hardcodes some amd64 specific stuff. Thanks, James
Bug#769003: libjogl2-java: FTBFS on arm64, ppc64el, s390x
Control: reassign -1 libgluegen2-build-java 2.2.4-1 Control: affects -1 libjogl2-java On Mon, Nov 10, 2014 at 05:53:43PM +0100, Hector Oron wrote: Your package fails to build from source on Debian autobuilder network. Please check your package build logs at: https://buildd.debian.org/status/package.php?p=libjogl2-javasuite=sid arm64 full log at: https://buildd.debian.org/status/fetch.php?pkg=libjogl2-javaarch=arm64ver=2.2.4%2Bdfsg-1stamp=1415253649 This is a recurrence of #733310, which happened because missing-arch-symbol.diff was incorrectly rebased across the upstream change in http://jogamp.org/git/?p=gluegen.git;a=commitdiff;h=addb639e6dde90519f772a66222eb86107b35176. Here's a fix. * Fix missing-arch-symbol.diff to cover the gcc case as well as clang (closes: #769003). diff -Nru gluegen2-2.2.4/debian/patches/missing-arch-symbol.diff gluegen2-2.2.4/debian/patches/missing-arch-symbol.diff --- gluegen2-2.2.4/debian/patches/missing-arch-symbol.diff 2014-10-20 15:35:29.0 +0100 +++ gluegen2-2.2.4/debian/patches/missing-arch-symbol.diff 2014-11-11 10:57:44.0 + @@ -1,8 +1,18 @@ -Index: gluegen-v2.2.0/make/stub_includes/platform/glibc-compat-symbols.h +Index: b/make/stub_includes/platform/glibc-compat-symbols.h === gluegen-v2.2.0.orig/make/stub_includes/platform/glibc-compat-symbols.h 2014-08-10 15:38:43.065816752 +0200 -+++ gluegen-v2.2.0/make/stub_includes/platform/glibc-compat-symbols.h 2014-08-10 15:38:43.065816752 +0200 -@@ -30,7 +30,8 @@ +--- a/make/stub_includes/platform/glibc-compat-symbols.h b/make/stub_includes/platform/glibc-compat-symbols.h +@@ -22,7 +22,8 @@ + #elif defined(__amd64__) +#define GLIBC_COMPAT_SYMBOL(FFF) __asm__(.symver #FFF , #FFF @GLIBC_2.2.5); + #else +- #define GLIBC_COMPAT_SYMBOL(FFF) __asm__(.symver #FFF , #FFF @GLIBC_2.0); ++ /* Don't try to guess a wrong version */ ++ #define GLIBC_COMPAT_SYMBOL(FFF) + #endif /*__amd64__*/ + #elif defined(__clang__) + #if defined(__arm__) +@@ -30,7 +31,8 @@ #elif defined(__amd64__) #define GLIBC_COMPAT_SYMBOL(FFF) asm(.symver #FFF , #FFF @GLIBC_2.2.5); #else Thanks, -- Colin Watson [cjwat...@ubuntu.com] -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#769100: htcondor: unowned directory after purge (policy 6.8) violating FHS (policy 9.1) too: /var/cred_dir/
Package: htcondor Version: 8.2.3~dfsg.1-3 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed your package left unowned files on the system after purge, which is a violation of policy 6.8: http://www.debian.org/doc/debian-policy/ch-maintainerscripts.html#s-removedetails From the attached log (scroll to the bottom...): 0m40.7s ERROR: FAIL: Package purging left files on system: /var/cred_dir/ not owned As putting stuff directly into /var also a violation of http://www.debian.org/doc/debian-policy/ch-opersys.html#s9.1 I'm setting the severity to serious. cheers, Andreas htcondor_8.2.3~dfsg.1-3.log.gz Description: application/gzip
Bug#769101: openstack-dashboard: unowned files after purge (policy 6.8, 10.8): /usr/share/openstack-dashboard/openstack_dashboard/static/dashboard/manifest.json
Package: openstack-dashboard Version: 2014.1.3-4 Severity: important User: debian...@lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed your package left unowned files on the system after purge, which is a violation of policy 6.8 (or 10.8): http://www.debian.org/doc/debian-policy/ch-maintainerscripts.html#s-removedetails Filing this as important as having a piuparts clean archive is a release goal since lenny. From the attached log (scroll to the bottom...): 1m53.0s ERROR: FAIL: Package purging left files on system: /usr/share/openstack-dashboard/owned by: openstack-dashboard /usr/share/openstack-dashboard/openstack_dashboard/owned by: openstack-dashboard /usr/share/openstack-dashboard/openstack_dashboard/static/ owned by: openstack-dashboard /usr/share/openstack-dashboard/openstack_dashboard/static/dashboard/ owned by: openstack-dashboard /usr/share/openstack-dashboard/openstack_dashboard/static/dashboard/manifest.json not owned cheers, Andreas openstack-dashboard_2014.1.3-4.log.gz Description: application/gzip
Bug#768741: phlipple: FTBFS in jessie: ld: engine.o: undefined reference to symbol 'cos@@GLIBC_2.2.5'
On Tue, Nov 11, 2014 at 02:09:37AM +0100, Miriam Ruiz wrote: 2014-11-10 20:56 GMT+01:00 Peter Pentchev r...@ringlet.net: On Mon, Nov 10, 2014 at 08:07:21PM +0100, Miriam Ruiz wrote: Thanks a lot, I'll have a look at it and commit it.Do you want to be included in Uploaders, as the patch seems to say? If you do, you're essentially declaring that you're willing to take care of that package, essentially :) Sure, why not? :) I could refresh its packaging after the freeze. Well, it's not really a why not decision :) , I mean, it's somehow a kind of commitment statement. I mean, while debian/changelog essentially talks about the past (who did what), imo Maintaner and Uploaders talk about the future of the packahe, more or less saying: hey, if there's something to fix in here, contact me and I will try to take care of it. Yes, of course you're absolutely right; I apologize for the flippancy. Yes, I would like to be listed as an uploader for both phlipple and zaz, if it's all right with you. This would be a kind of a come-back to the Games team for me, and the fact that I actually enjoy and play phlipple might help, too :) Thanks for your patience! G'luck, Peter -- Peter Pentchev r...@ringlet.net r...@freebsd.org p.penc...@storpool.com PGP key:http://people.FreeBSD.org/~roam/roam.key.asc Key fingerprint 2EE7 A7A5 17FC 124C F115 C354 651E EFB0 2527 DF13 signature.asc Description: Digital signature
Bug#769102: Can't configure packages from undocumented states 'T' and 'W'
Package: aptitude Version: 0.6.11-1+b1 After last night unattented-upgrades, libaudio2 caused a failure (see attached unattended-upgrades-dpkg.log) I manually downgraded them from http://snapshot.debian.org/package/nas/ using: # dpkg -i libaudio2_1.9.4-1_amd64.deb libaudio2_1.9.4-1_i386.deb These packages are on hold in aptitude. I completed the installation using aptitude update dist-upgrade. I also tried apt-get -f install. But now, 2 packages are refusing to complete their configuration: root@deimos:~# aptitude full-upgrade The following partially installed packages will be configured: dbus systemd-shim No packages will be installed, upgraded, or removed. 0 packages upgraded, 0 newly installed, 0 to remove and 2 not upgraded. Need to get 0 B of archives. After unpacking 0 B will be used. root@deimos:~# aptitude full-upgrade The following partially installed packages will be configured: dbus systemd-shim No packages will be installed, upgraded, or removed. 0 packages upgraded, 0 newly installed, 0 to remove and 2 not upgraded. Need to get 0 B of archives. After unpacking 0 B will be used. Additionally, when using the interface, these packages show state 'T' and 'W' that are undocumented when pressing '?'. Oo See attached screen shots. I worked around that by running dpkg -a --configure (thanks babilen@oftc) I think aptitude should be able to configure these packages, or at very least should not say it will configure them when it does not. -- Package-specific info: Terminal: xterm $DISPLAY is set. which aptitude: /usr/bin/aptitude aptitude version information: aptitude 0.6.11 compiled at Nov 8 2014 13:34:39 Compiler: g++ 4.9.1 Compiled against: apt version 4.12.0 NCurses version 5.9 libsigc++ version: 2.4.0 Gtk+ support disabled. Qt support disabled. Current library versions: NCurses version: ncurses 5.9.20140913 cwidget version: 0.5.17 Apt version: 4.12.0 aptitude linkage: linux-vdso.so.1 (0x7fff015fc000) libapt-pkg.so.4.12 = /usr/lib/x86_64-linux-gnu/libapt-pkg.so.4.12 (0x7f87524d8000) libncursesw.so.5 = /lib/x86_64-linux-gnu/libncursesw.so.5 (0x7f87522a2000) libtinfo.so.5 = /lib/x86_64-linux-gnu/libtinfo.so.5 (0x7f8752077000) libsigc-2.0.so.0 = /usr/lib/x86_64-linux-gnu/libsigc-2.0.so.0 (0x7f8751e71000) libcwidget.so.3 = /usr/lib/x86_64-linux-gnu/libcwidget.so.3 (0x7f8751b5b000) libsqlite3.so.0 = /usr/lib/x86_64-linux-gnu/libsqlite3.so.0 (0x7f8751892000) libboost_iostreams.so.1.55.0 = /usr/lib/x86_64-linux-gnu/libboost_iostreams.so.1.55.0 (0x7f875167a000) libxapian.so.22 = /usr/lib/libxapian.so.22 (0x7f8751269000) libpthread.so.0 = /lib/x86_64-linux-gnu/libpthread.so.0 (0x7f875104b000) libstdc++.so.6 = /usr/lib/x86_64-linux-gnu/libstdc++.so.6 (0x7f8750d4) libm.so.6 = /lib/x86_64-linux-gnu/libm.so.6 (0x7f8750a3f000) libgcc_s.so.1 = /lib/x86_64-linux-gnu/libgcc_s.so.1 (0x7f8750828000) libc.so.6 = /lib/x86_64-linux-gnu/libc.so.6 (0x7f875047f000) libutil.so.1 = /lib/x86_64-linux-gnu/libutil.so.1 (0x7f875027c000) libdl.so.2 = /lib/x86_64-linux-gnu/libdl.so.2 (0x7f8750077000) libz.so.1 = /lib/x86_64-linux-gnu/libz.so.1 (0x7f874fe5c000) libbz2.so.1.0 = /lib/x86_64-linux-gnu/libbz2.so.1.0 (0x7f874fc4c000) liblzma.so.5 = /lib/x86_64-linux-gnu/liblzma.so.5 (0x7f874fa28000) librt.so.1 = /lib/x86_64-linux-gnu/librt.so.1 (0x7f874f82) libuuid.so.1 = /lib/x86_64-linux-gnu/libuuid.so.1 (0x7f874f61a000) /lib64/ld-linux-x86-64.so.2 (0x7f8752ebc000) -- System Information: Debian Release: jessie/sid APT prefers testing APT policy: (990, 'testing') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.16-3-amd64 (SMP w/2 CPU cores) Locale: LANG=en_GB.utf8, LC_CTYPE=en_GB.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages aptitude depends on: ii aptitude-common 0.6.11-1 ii libapt-pkg4.121.0.9.3 ii libboost-iostreams1.55.0 1.55.0+dfsg-3 ii libc6 2.19-12 ii libcwidget3 0.5.17-2 ii libgcc1 1:4.9.1-19 ii libncursesw5 5.9+20140913-1 ii libsigc++-2.0-0c2a2.4.0-1 ii libsqlite3-0 3.8.7-1 ii libstdc++64.9.1-19 ii libtinfo5 5.9+20140913-1 ii libxapian22 1.2.19-1 Versions of packages aptitude recommends: ii aptitude-doc-en [aptitude-doc] 0.6.11-1 ii libparse-debianchangelog-perl 1.2.0-1.1 ii sensible-utils 0.0.9 Versions of packages aptitude suggests: pn apt-xapian-index none pn debtags none ii tasksel 3.29 -- no debconf information Log started: 2014-11-11 07:46:30 Reading changelogs... (Reading database ... 239512
Bug#769103: chanact: messes with status window
Package: irssi-scripts Version: 20131030 Severity: normal Tags: fixed-upstream upstream chanact seems to have a bug that causes the status window to lose its name and get moved away from #1. Upstream's version works. https://bc-bd.org/gitweb/gitweb.cgi?p=irssi.git;a=summary -- System Information: Debian Release: jessie/sid APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 3.16-2-amd64 (SMP w/8 CPU cores) Locale: LANG=en_NZ, LC_CTYPE=en_NZ.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash -- .''`. martin f. krafft madduck@d.o @martinkrafft : :' : proud Debian developer `. `'` http://people.debian.org/~madduck `- Debian - when you have better things to do than fixing systems digital_signature_gpg.asc Description: Digital signature (see http://martin-krafft.net/gpg/sig-policy/999bbcc4/current)
Bug#769104: override: scanbuttond:oldlibs/extra
Package: ftp.debian.org Severity: normal Hello, the scanbuttond source and most importantly binary package were superseded by the new scanbd package. That is why the current scanbuttond binary package in unstable has section oldlibs and that is correct. Please update the override accordingly. Regards Rolf Leggewie -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#670377: i965 driver doesn't work on my 945GME
On 2014-11-05 09:00:26, Dominique Brazziel wrote: Problem: no VA support for intel G45 and others reason: missing i915_drv_video.so, which is not delivered by any package solution: Should the installed i965_drv_video.so be loaded instead of the missing i915_drv_video.so? I suspect that your chip is not supported and that's why vainfo crashed. What's the exact chip you are using? After looking at the source for vainfo, I tried to load i965 and got a segfault: env LIBVA_DRIVER_NAME=i965 VA_INTEL_DEBUG=1 vainfo libva info: VA-API version 0.36.0 libva info: va_getDriverName() returns 0 libva info: User requested driver 'i965' libva info: Trying to open /usr/lib/i386-linux-gnu/dri/i965_drv_video.so libva info: Found init function __vaDriverInit_0_36 g_intel_debug_option_flags:1 Segmentation fault (core dumped) The crash is fixed in intel-vaapi-driver 1.4.1-2. Cheers -- Sebastian Ramacher signature.asc Description: Digital signature
Bug#746638: linux-image-3.14-1-amd64: Headset Plantronics GameCom 780 doesn't work
Hi again,
This bug easy to fix, I don't know why did not I think of that before.
I made patch, it's working fine on src:linux from sid and experimental.
Can you add it to jessie?
Mateusz
Description: Enable volume control for Plantronics Gamecom 780
Author: Mateusz Åukasik mat...@linuxmint.pl
Bug-Debian: https://bugs.debian.org/746638
--- a/sound/usb/mixer_maps.c
+++ b/sound/usb/mixer_maps.c
@@ -324,7 +324,7 @@ static struct usbmix_name_map hercules_u
/* Plantronics Gamecom 780 has a broken volume control, better to disable it */
static struct usbmix_name_map gamecom780_map[] = {
- { 9, NULL }, /* FU, speaker out */
+ { 9, Master Playback }, /* FU, speaker out */
{}
};
Bug#769105: dietlibc: [PATCH] fix error codes and signals on hppa architecture
Package: dietlibc Version: 0.33~cvs20120325 Severity: critical Tags: patch Can you please apply this patch for the next upload of dietlibc? It adjusts (for the hppa architecture only): - EWOULDBLOCK is now same as EAGAIN, see upstream kernel commit (since kernel 3.14): http://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=f5a408d53edef3af07ac7697b8bc54a755628450 - adjusts SIGSTKFLT, SIGXCPU, SIGXFSZ and SIGRTMIN to our new scheme, see Linux kernel upstream commit: http://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=1f25df2eff5b25f52c139d3ff31bc883eee9a0ab Thanks, Helge diff -up ./include/errno.h.org ./include/errno.h --- ./include/errno.h.org 2014-11-11 11:01:32.500997002 +0100 +++ ./include/errno.h 2014-11-11 11:02:33.356987381 +0100 @@ -550,7 +550,7 @@ #define EALREADY 244 /* Operation already in progress */ #define EINPROGRESS 245 /* Operation now in progress */ -#define EWOULDBLOCK 246 /* Operation would block (Linux returns EAGAIN) */ +#define EWOULDBLOCK EAGAIN /* Operation would block (Linux returns EAGAIN) */ #define ENOTEMPTY 247 /* Directory not empty */ #define ENAMETOOLONG 248 /* File name too long */ #define ELOOP 249 /* Too many symbolic links encountered */ diff -up ./include/signal.h.org ./include/signal.h --- ./include/signal.h.org 2014-11-11 11:04:33.988968598 +0100 +++ ./include/signal.h 2014-11-11 11:14:17.980881783 +0100 @@ -97,9 +97,9 @@ __BEGIN_DECLS #define SIGXCPU 30 #define SIGXFSZ 31 #elif defined(__hppa__) -#define SIGEMT 7 +#define SIGSTKFLT 7 #define SIGBUS 10 -#define SIGSYS 12 +#define SIGXCPU 12 #define SIGUSR1 16 #define SIGUSR2 17 #define SIGCHLD 18 @@ -114,12 +114,10 @@ __BEGIN_DECLS #define SIGTTIN 27 #define SIGTTOU 28 #define SIGURG 29 -#define SIGLOST 30 +#define SIGXFSZ 30 #define SIGUNUSED 31 -#define SIGRESERVE SIGUNUSE -#define SIGXCPU 33 -#define SIGXFSZ 34 -#define SIGSTKFLT 36 +#define SIGRESERVE SIGUNUSED +#define SIGSYS 31 #else #error signal layout not yet known @@ -129,12 +127,8 @@ __BEGIN_DECLS #define SIGPOLL SIGIO /* These should not be considered constants from userland. */ -#ifdef __hppa__ -#define SIGRTMIN 37 -#else #define SIGLOST SIGPWR #define SIGRTMIN 32 -#endif #define SIGRTMAX (_NSIG-1) /* SA_FLAGS values: */
Bug#764732: gcc-4.9: broken -O2 optimizations on armhf
On Fri, Oct 10, 2014 at 05:33:00PM +0200, Hector Oron wrote: Package: gcc-4.9 Version: 4.9.1-16 Severity: important Hello, Found a FTBFS while trying to build unzip package in Debian/sid on armhf host. gcc -c -g -O2 -fstack-protector-strong -Wall -D_FORTIFY_SOURCE=2 -I. -DACORN_FTYPE_NFS -DWILD_STOP_AT_DIR -DLARGE_FILE_SUPPORT -DUNICODE_SUPPORT -DUNICODE_WCHAR -DUTF8_MAYBE_NATIVE -DNO_LCHMOD -DDATE_FORMAT=DF_YMD -DUSE_BZIP2 -DIZ_HAVE_UXUIDGID -DNOMEMCPY -DNO_WORKING_ISPRINT inflate.c gcc -c -g -O2 -fstack-protector-strong -Wall -D_FORTIFY_SOURCE=2 -I. -DACORN_FTYPE_NFS -DWILD_STOP_AT_DIR -DLARGE_FILE_SUPPORT -DUNICODE_SUPPORT -DUNICODE_WCHAR -DUTF8_MAYBE_NATIVE -DNO_LCHMOD -DDATE_FORMAT=DF_YMD -DUSE_BZIP2 -DIZ_HAVE_UXUIDGID -DNOMEMCPY -DNO_WORKING_ISPRINT list.c gcc -c -g -O2 -fstack-protector-strong -Wall -D_FORTIFY_SOURCE=2 -I. -DACORN_FTYPE_NFS -DWILD_STOP_AT_DIR -DLARGE_FILE_SUPPORT -DUNICODE_SUPPORT -DUNICODE_WCHAR -DUTF8_MAYBE_NATIVE -DNO_LCHMOD -DDATE_FORMAT=DF_YMD -DUSE_BZIP2 -DIZ_HAVE_UXUIDGID -DNOMEMCPY -DNO_WORKING_ISPRINT match.c gcc -c -g -O2 -fstack-protector-strong -Wall -D_FORTIFY_SOURCE=2 -I. -DACORN_FTYPE_NFS -DWILD_STOP_AT_DIR -DLARGE_FILE_SUPPORT -DUNICODE_SUPPORT -DUNICODE_WCHAR -DUTF8_MAYBE_NATIVE -DNO_LCHMOD -DDATE_FORMAT=DF_YMD -DUSE_BZIP2 -DIZ_HAVE_UXUIDGID -DNOMEMCPY -DNO_WORKING_ISPRINT process.c process.c: In function 'wide_to_local_string': process.c:2453:7: warning: variable 'state_dependent' set but not used [-Wunused-but-set-variable] int state_dependent; ^ /tmp/cc0hC5mg.s: Assembler messages: /tmp/cc0hC5mg.s:898: Error: offset out of range /tmp/cc0hC5mg.s:899: Error: offset out of range make[1]: *** [process.o] Error 1 unix/Makefile:234: recipe for target 'process.o' failed make[1]: Leaving directory '/«PKGBUILDDIR»' make: *** [build] Error 2 debian/rules:34: recipe for target 'build' failed dpkg-buildpackage: error: debian/rules build gave error exit status 2 After trying different toolchain versions, for binutils and gcc-4.9, it builds with -O1, but fails with -O2. So, apparently the bug is on the GCC optimizer. I was about to file a bug upstream for that one, but I was unable to reproduce with gcc-snapshot, therefore I file it here for now. Re-tested with gcc-4.9 (4.9.2-1) same thing happens. Using gcc-snapshot (20141017-1), I am unable to reproduce. Regards, -- Hector Oron signature.asc Description: Digital signature
Bug#769107: debian-installer: grub-installer fails if more than 26 SCSI devices are present
Package: debian-installer Version: 20141002 Severity: important Tags: d-i Dear Maintainer, installing Debian jessie with weekly snapshot netinst ISO image http://cdimage.debian.org/cdimage/daily-builds/daily/arch-latest/amd64/iso-cd/debian-testing-amd64-netinst.iso on an x86_64 Server with lots of SCSI devices as of 2014-10-29 makes grub-installer croak. Debugging reveals that it stumbles across SCSI devices /dev/sda[a-z] being present. Patching it as follows (manually from a separate console in the install system) makes the installtion proceed without problem: From 4d91c83577a4dbe8c52271bbd157b450b8c7edf3 Mon Sep 17 00:00:00 2001 From: Michael Weiser m.wei...@science-computing.de Date: Fri, 31 Oct 2014 11:36:10 +0100 Subject: [PATCH] Allow for devices such as /dev/sdaa --- grub-installer | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/grub-installer b/grub-installer index 2b61fb6..5bceec6 100755 --- a/grub-installer +++ b/grub-installer @@ -252,7 +252,7 @@ case $prefix in /dev/mapper) disc_offered_devfs=$bootfs ;; - /dev/[hsv]d[a-z0-9]|/dev/xvd[a-z]|/dev/cciss/c[0-9]d[0-9]*|/dev/ida/c[0-9]d[0-9]*|/dev/rs/c[0-9]d[0-9]*|/dev/mmcblk[0-9]|/dev/ad[0-9]*|/dev/da[0-9]*) + /dev/[hsv]d[a-z0-9][a-z0-9]|/dev/xvd[a-z]|/dev/cciss/c[0-9]d[0-9]*|/dev/ida/c[0-9]d[0-9]*|/dev/rs/c[0-9]d[0-9]*|/dev/mmcblk[0-9]|/dev/ad[0-9]*|/dev/da[0-9]*) disc_offered_devfs=$prefix ;; *) -- 2.1.1 -- System Information: Debian Release: jessie/sid APT prefers testing-updates APT policy: (500, 'testing-updates'), (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 3.16-3-amd64 (SMP w/1 CPU core) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash -- no debconf information -- Vorstandsvorsitzender/Chairman of the board of management: Gerd-Lothar Leonhart Vorstand/Board of Management: Dr. Bernd Finkbeiner, Michael Heinrichs, Dr. Arno Steitz Vorsitzender des Aufsichtsrats/ Chairman of the Supervisory Board: Philippe Miltin Sitz/Registered Office: Tuebingen Registergericht/Registration Court: Stuttgart Registernummer/Commercial Register No.: HRB 382196 -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#769106: python2.7-minimal: fails to upgrade from 'wheezy': python or pycompile not found in public_modules.rtinstall hook.
Package: python2.7-minimal Version: 2.7.8-11 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed your package fails to upgrade from 'wheezy'. It installed fine in 'wheezy', then the upgrade to 'jessie' fails. From the attached log (scroll to the bottom...): Setting up python2.7-minimal (2.7.8-11) ... python or pycompile not found in public_modules.rtinstall hook. dpkg: error processing package python2.7-minimal (--configure): subprocess installed post-installation script returned error exit status 1 Errors were encountered while processing: python2.7-minimal This was observed during an upgrade test of texlive-music. cheers, Andreas texlive-music_2014.20141024-1.log.gz Description: application/gzip
Bug#769108: asterisk: rr_copy array too small for some record-route headers
Package: asterisk Version: 1:1.8.13.1~dfsg1-3+deb7u3 Severity: normal Dear Maintainer, Connecting with Microsoft Lync through one or more SIP proxies fails when the Record-Route value exceeds 256 characters in length. Asterisk's log shows the following warning message: [Nov 10 16:11:04] WARNING[22109]: sip/reqresp_parser.c:1070 get_in_brackets_full: No closing bracket found in 'sip:192.168.10.2;r2=on;lr;ftag=as36b4c879;vsf=AAA' where the complete Record-Route was: sip:127.1.2.3;line=sr-EcmQ.7qAr7xCqCtAi7V9q7qy.13CnXJzETMC8bByn1ehE7xMPcthPLxh6-3R6zBREzEzianBn7eQ.16z67Bwusjwusjwusjwusjwusjwusjwusjwu2iY3smwsaAQdBjXOKjw3-RgsaElrdl2OXuM67qAr7YU67KhPajyogmmEQ**,sip:192.168.10.2;r2=on;lr;ftag=as736f5b00;vsf=AABCUEIARlpOQVhAAFxWRg--;did=f31.5bf1;nat=yes. As you can see it cuts the Record-Route string short at exactly 256 chars. Looking into this I found that in chan_sip.c in function build_route there is a definition of 'char rr_copy[256]' (line 14252). This is too small as you can see. My proposed fix would be to enlarge this field to a bigger value. For now I have set mine to 8192. This completely resolves the issue. -- System Information: Debian Release: 7.7 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/4 CPU cores) Locale: LANG=en_GB.utf8, LC_CTYPE=en_GB.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash -- Met vriendelijke groet, Dirk Teurlings BICT Signet B.V. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#722265: mako contains some minified javascript librairies
Control: tags -1 pending Hi, On Mon, Sep 09, 2013 at 11:08:48PM +0800, Thomas Goirand wrote: This package has the following javascript libs in minified versions: - doc/searchindex.js - doc/_static/jquery.js - doc/_static/underscore.js These should be either removed, or replaced by a non-obfuscated version. As this is sphinx generated docs, probably it's ok to remove them. These files are not used in the build process. I uploaded an NMU with a repackaged upstream tarball to DELAYED/2. The resulting debs are identical. Cheers, Ivo -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#769109: x2vnc accidentally trigger window hiding when pointer leaves the VNC screen on Windows 7
Package: x2vnc Version: 1.7.2-5 Severity: normal When the pointer leaves the VNC screen and returns to the controlling machine, x2vnc sets the point location to the extreme lower-right corner of the VNC screen, instead of the last pointer location before the pointer left the VNC screen. When the controlled machine is Windows 7 (and possibly some other Windows versions), this has the effect of enabling the 'Peek at Desktop' feature, whereby all application windows become fully transparent (except for an outline), in order to display the desktop beneath - this is confusing and undesirable, but can be worked around by disabling the 'Peek at Desktop' feature - however this is non-obvious (to say the least!). This is described here: http://breakingcode.wordpress.com/2010/09/08/a-dual-screen-hack-x2vnc/#postcomment along with a patched version. -- System Information: Debian Release: jessie/sid APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.16-2-amd64 (SMP w/8 CPU cores) Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages x2vnc depends on: ii libc6 2.19-12 ii libice6 2:1.0.9-1 ii libsm62:1.2.2-1 ii libx11-6 2:1.6.2-3 ii libxext6 2:1.3.3-1 ii libxinerama1 2:1.1.3-1 ii libxss1 1:1.2.2-1 x2vnc recommends no packages. Versions of packages x2vnc suggests: ii tightvncserver 1.3.9-6.4+b1 ii vnc4server 4.1.1+X4.3.0-37.1 ii xtightvncviewer 1.3.9-6.4+b1 ii xvnc4viewer 4.1.1+X4.3.0-37.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#753291: libgdbm3:i386: The same problem occurs during the upgrade to version 1.8.3-13
Package: libgdbm3 Version: 1.8.3-13 Followup-For: Bug #753291 Dear Maintainer, I have found the same problem during the upgrading to 1.8.3-13 version of this package. I do not know if this issue is due to the fact that I am using both amd64 and i386 package versions. -- System Information: Debian Release: jessie/sid APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.16-3-amd64 (SMP w/4 CPU cores) Locale: LANG=it_IT.UTF-8, LC_CTYPE=it_IT.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages libgdbm3:i386 depends on: ii dpkg 1.17.21 ii install-info 5.2.0.dfsg.1-5 ii libc6 2.19-12 ii multiarch-support 2.19-12 libgdbm3:i386 recommends no packages. libgdbm3:i386 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#768936: ITP: nufft -- Library implementing the Non-Uniform Fast Fourier Transform
Dear Justin, Thank you for reviewing this ITP bug and underlying my mistakes as a non-native english writer. I do appreciate your efforts, and would welcome a future review of the long description of this package before its upload to main. This being just an ITP bug however, I do wonder whether such careful review of my spelling and grammatical skills was really necessary. Cheers, Ghis
Bug#766006: dpkg: cycle found while processing triggers
Followup-For: Bug #766006 Reproducible in piuparts wheezy-jessie upgrades with dpkg 1.17.21. piuparts log attached. Andreas man-db_2.7.0.2-3.log.gz Description: application/gzip
Bug#761149: debsources: allow redirects to package versions based on suite/codename
Updated patch
I made a proper git patch, so that the new file would be displayed. Also
cleaned up the models.py file, I had some leftover from previous strategies.
It's still required to regenerate the data in testdata (make distclean
dump) to account for the new column
Thanks
--
Jason Pleau
From fd6ff45605f17c9e91664e3bf160f23ed1515597 Mon Sep 17 00:00:00 2001
From: Jason Pleau ja...@jpleau.ca
Date: Tue, 11 Nov 2014 06:52:38 -0500
Subject: [PATCH] allow redirects to package versions based on suite/codename
Like the /latest redirect, we now check for suite names to redirect to
a specific version. If package foo has version 1.5-1 in sid, going to
/src/foo/sid will display as if we went to /src/foo/1.5-1.
When going to /src/foo/sid for example, It iterates through the package's suite,
and if it finds what's provided in the url, it redirects the request (in the
application) to the proper version.
This commit also adds an 'alias' column to the suites_info table. This allows
us to add 'unstable' to 'sid', 'testing' to 'jessie' and so on. We'll be able
to update this column in an update script, and it will be easy for other
distributions using debsources to manage their suites aliases.
When going to /src/foo/unstable, if it detects that 'unstable' matches
'sid', it will change the version to 'sid', and will use the same logic
as described above to redirect to the right version.
---
debsources/app/views.py | 16 +++-
debsources/migrate/007-to-008.sql | 14 ++
debsources/models.py| 10 ++
debsources/tests/test_webapp.py | 10 ++
doc/db-schema/debsources.dia| 23 +++
doc/db-schema/debsources.dot| 2 +-
doc/db-schema/debsources.html | 18 +-
doc/db-schema/debsources.neato | 2 +-
doc/db-schema/debsources.xml| 16
doc/db-schema/debsources.zigzag.dia | 23 +++
10 files changed, 126 insertions(+), 8 deletions(-)
create mode 100644 debsources/migrate/007-to-008.sql
diff --git a/debsources/app/views.py b/debsources/app/views.py
index 565b17a..3cbafc0 100644
--- a/debsources/app/views.py
+++ b/debsources/app/views.py
@@ -37,7 +37,7 @@ from debsources.excepts import (
Http500Error, Http404Error, Http404ErrorSuggestions, Http403Error)
from debsources.models import (
Ctag, Package, PackageName, Checksum, Location, Directory,
-SourceFile, File)
+SourceFile, File, SuiteInfo)
from debsources.app.sourcecode import SourceCodeIterator
from debsources.app.forms import SearchForm
from debsources.app.infobox import Infobox
@@ -572,6 +572,20 @@ class SourceView(GeneralView):
if version == latest: # we search the latest available version
return self._handle_latest_version(package, path)
else:
+suites_info = session.query(SuiteInfo).all()
+suites_aliases = { s.alias: s.name for s in suites_info }
+try:
+versions_w_suites = PackageName.list_versions_w_suites(
+session, package)
+except InvalidPackageOrVersionError:
+raise Http404Error(%s not found % package)
+for version_suite in versions_w_suites:
+if version in suites_aliases:
+version = suites_aliases[version]
+if version in version_suite['suites']:
+return self._render_location(
+package, version_suite['version'], path)
+
return self._render_location(package, version, path)
diff --git a/debsources/migrate/007-to-008.sql b/debsources/migrate/007-to-008.sql
new file mode 100644
index 000..838346e
--- /dev/null
+++ b/debsources/migrate/007-to-008.sql
@@ -0,0 +1,14 @@
+ALTER TABLE suites_info
+ ADD COLUMN alias VARCHAR;
+
+UPDATE suites_info
+ SET alias='unstable' WHERE name='sid';
+
+UPDATE suites_info
+ SET alias='testing' WHERE name='jessie';
+
+UPDATE suites_info
+ SET alias='stable' WHERE name='wheezy';
+
+UPDATE suites_info
+ SET alias='oldstable' WHERE name='squeeze';
diff --git a/debsources/models.py b/debsources/models.py
index 45647af..86b6648 100644
--- a/debsources/models.py
+++ b/debsources/models.py
@@ -42,8 +42,8 @@ from debsources.consts import SUITES
Base = declarative_base()
-# used for migrations, see scripts under python/migrate/
-DB_SCHEMA_VERSION = 7
+# used for migrations, see scripts under debsources/migrate/
+DB_SCHEMA_VERSION = 8
class PackageName(Base):
@@ -194,15 +194,17 @@ class SuiteInfo(Base):
version = Column(String, nullable=True)
release_date = Column(Date, nullable=True)
sticky = Column(Boolean, nullable=False)
+alias = Column(String, nullable=True)
-def __init__(self, name, sticky=False, version=None, release_date=None):
+def __init__(self, name, sticky=False,
Bug#769110: adjust zabbix-server-mysql to recommend virtual-mysql-server
package: zabbix-server-mysql severity: wishlist Noticed that zabbix-server-mysql recommends mysql-server, not sure about policies and so on but maybe it should be changed to virtual-mysql-server to allow for mariadb and others to be used. Recommends: mysql-server | virtual-mysql-server https://wiki.debian.org/Teams/MySQL/virtual-mysql-server Thanks for providing zabbix for the Debian community! -- brother http://sis.bthstudent.se -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#767892: subtitleeditor: Cannot type or edit subtitles
Great. Btw you can ping me if you need an upload. - Sylvain On Tue, Nov 11, 2014 at 08:50:28AM +0100, Philip Rinn wrote: Hi, I uploaded the fixed version to m.d.n: http://mentors.debian.net/package/subtitleeditor I'll bother my sponsor now ;) Best, Philip -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#769111: dpkg bug/vuln v2
Package: dpkg Version: 1.16.1.2 Tags: bug, security This doesn't seem to be a vulnerability, but more of a bug.. Best that the devs look at it rather than me, though. I'm using v1.16.1.2ubuntu7.5, but it is probably there in more recent versions With the control file: : 1 a: %s dpkg-deb --build will segfault. It will not segfault if you put something before : 1 and will not segfault if a: %s does not contain a % symbol. Here's a gdb backtrace: Program received signal SIGSEGV, Segmentation fault. 0x7763f061 in _IO_vfprintf_internal (s=optimised out, format=optimised out, ap=optimised out) at vfprintf.c:1630 1630vfprintf.c: No such file or directory. (gdb) bt #0 0x7763f061 in _IO_vfprintf_internal (s=optimised out, format=optimised out, ap=optimised out) at vfprintf.c:1630 #1 0x776fd3e0 in ___vsnprintf_chk (s=0x7fffd640 parsing file 'lol/DEBIAN/control' near line 2 package '1:%s':\n 'must start with an alphanumeric' is not a valid architecture name: \367\377\177, maxlen=optimised out, flags=1, slen=optimised out, format=0x649940 parsing file 'lol/DEBIAN/control' near line 2 package '1:%s':\n '%s' is not a valid architecture name: %s, args=0x7fffda68) at vsnprintf_chk.c:65 #2 0x00414b27 in vsnprintf (__ap=optimised out, __fmt=optimised out, __n=1024, __s=0x7fffd640 parsing file 'lol/DEBIAN/control' near line 2 package '1:%s':\n 'must start with an alphanumeric' is not a valid architecture name: \367\377\177) at /usr/include/x86_64-linux-gnu/bits/stdio2.h:78 #3 warningv (fmt=optimised out, args=optimised out) at ehandle.c:392 #4 0x00422199 in parse_warn (ps=optimised out, fmt=optimised out) at parsehelp.c:75 #5 0x0041db26 in parse_stanza (ps=0x7fffddf0, fs=0x7fffde30, parse_field=0x41bbe0 pkg_parse_field, parse_obj=0x7fffde70) at parse.c:478 #6 0x0041ebb6 in parsedb (filename=0x65e120 lol/DEBIAN/control, flags=optimised out, donep=0x7fffdfe0) at parse.c:547 #7 0x00404004 in check_new_pkg (dir=0x7fffe3c5 lol) at build.c:335 #8 do_build (argv=optimised out) at build.c:436 #9 0x004029e1 in main (argc=optimised out, argv=0x7fffe168) at main.c:206 #10 0x7761576d in __libc_start_main (main=0x402860 main, argc=3, ubp_av=0x7fffe158, init=optimised out, fini=optimised out, rtld_fini=optimised out, stack_end=0x7fffe148) at libc-start.c:226 #11 0x00402ac5 in _start () A quick guess is that because the : 1 part of the file does not have a 'name', it trys to call a NULL. Somebody should check if I'm right, though. Thanks, -- -- Joshua Rogers https://internot.info/ signature.asc Description: OpenPGP digital signature
Bug#769112: RM: libspoon-perl -- ROM; dead upstream, open security issues
Package: ftp.debian.org Severity: normal Hi, (This has been discussed with Salvatore/carnil from the Debian Perl Group) Please remove libspoon-perl (and it's rev deps libspork-perl and libkwiki-perl) for which I'll file separate bugs. It's dead upstream and there are open security issues which are unfixed upstream since 1.5 years. Popcon is marginal. Cheers, Moritz -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#769105: dietlibc: [PATCH] fix error codes and signals on hppa architecture
Control: severity -1 important On 11/11/14 12:39, Helge Deller wrote: Package: dietlibc Version: 0.33~cvs20120325 Severity: critical Tags: patch Can you please apply this patch for the next upload of dietlibc? It adjusts (for the hppa architecture only): - EWOULDBLOCK is now same as EAGAIN, see upstream kernel commit (since kernel 3.14): http://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=f5a408d53edef3af07ac7697b8bc54a755628450 - adjusts SIGSTKFLT, SIGXCPU, SIGXFSZ and SIGRTMIN to our new scheme, see Linux kernel upstream commit: http://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=1f25df2eff5b25f52c139d3ff31bc883eee9a0ab Thanks for your report. Note though that problems on hppa are not release critical as hppa is not a release architecture; downgrading the severity accordingly. Emilio -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#769113: liblldb-3.5: needs breaks against lldb-3.3
Package: liblldb-3.5 Version: 1:3.5-6 Severity: important Hi, There was a bug reported against codelite here todo with llvm: https://github.com/eranif/codelite/issues/592 It happened because when lldb-3.3 was already installed when lldb-3.5 was. Since lldb-3.3 provides a liblldb.so.1 file, when lldb-3.5 is installed, ldconfig prints a warning and does not replace that file. This causes codelite to link against the wrong version of lldb. Please add a Breaks: lldb-3.3 to liblldb-3.5 which should prevent this from happening. Thanks, James -- System Information: Debian Release: jessie/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.16.0-4-amd64 (SMP w/4 CPU cores) Locale: LANG=en_GB.utf8, LC_CTYPE=en_GB.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages liblldb-3.5 depends on: ii libc6 2.19-13 ii libedit2 3.1-20140620-2 ii libffi63.1-2 ii libgcc11:4.9.2-1 ii libllvm3.5 1:3.5-6 ii libncurses55.9+20140913-1 ii libpython2.7 2.7.8-11 ii libstdc++6 4.9.2-1 ii libtinfo5 5.9+20140913-1 ii multiarch-support 2.19-13 ii zlib1g 1:1.2.8.dfsg-2 liblldb-3.5 recommends no packages. liblldb-3.5 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#769114: Depends on libspoon-perl
Package: libspork-perl Severity: serious Hi, libspoon-perl is scheduled for removal (769112). Please adapt your package to work without it or reassign this bug to ftp.debian.org to remove it along. Cheers, Moritz -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#769115: Depends on libspoon-perl
Package: libkwiki-perl Severity: serious Hi, libspoon-perl is scheduled for removal (769112). Please adapt your package to work without it or reassign this bug to ftp.debian.org to remove it along. Cheers, Moritz -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#768168: watchdog does not start at boot
On Nov 10, Michael Meskes wrote: Could you run 'ls /lib/systemd/system/graphical.target.wants/' please? # ls /lib/systemd/system/graphical.target.wants/ systemd-update-utmp-runlevel.service # cat /lib/systemd/system/graphical.target.wants/systemd-update-utmp-runlevel.service # This file is part of systemd. # # systemd is free software; you can redistribute it and/or modify it # under the terms of the GNU Lesser General Public License as published by # the Free Software Foundation; either version 2.1 of the License, or # (at your option) any later version. [Unit] Description=Update UTMP about System Runlevel Changes Documentation=man:systemd-update-utmp.service(8) man:utmp(5) DefaultDependencies=no RequiresMountsFor=/var/log/wtmp Conflicts=shutdown.target Requisite=systemd-update-utmp.service After=systemd-update-utmp.service After=runlevel1.target runlevel2.target runlevel3.target runlevel4.target runlevel5.target Before=shutdown.target [Service] Type=oneshot ExecStart=/lib/systemd/systemd-update-utmp runlevel -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#768136: cmor: Fix FTPFS on ppc64el
On Wed, Nov 05, 2014 at 11:21:54AM +0100, Frederic Bonnard wrote: here is a patch for cmor on ppc64el that fails to build in sid : https://buildd.debian.org/status/package.php?p=cmorsuite=sid Seems the initial workaround is not needed anymore so removing it. It seems to build fine without. Yes, this was fixed properly by #755829. You can probably drop all the related EXTRA_NCLDFLAGS infrastructure too, as well as the ppc64el-specific build-dependencies. -- Colin Watson [cjwat...@debian.org] -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#473561:
On Sun, 30 Mar 2014 04:17:50 -0400 Eduard Dumitrescu edumi...@uottawa.ca wrote: Hi, This appears to be an 'apertium-dbus' bug (not 'apertium-tolk'). It seems the code in 'src/command_line.py' used the deprecated 'os.popen3' function and did not encode the input to UTF-8 before attempting to send it over (nor did it decode the output). Switching to 'subprocess.Popen' and adding the required encode/decode UTF-8 calls appears to have fixed this bug. Patch attached. I can confirm your patch works for me. Thank you. I had the same problem before the patch (in jessie armhf). I looked upstream and http://svn.code.sf.net/p/apertium/svn/trunk/apertium-dbus/src/command_line.py seems to have it solved too (since dec.2012), but I haven't tried that. They don't seem to have done any new release, just commits. According to the upstream log they migrated to python3 before fixing this, and the current apertium-dbus packages depend on python 2, so maybe it would be easier to use your patch, at least until the whole packaging updates its code and dependencies. Should I open a bug in apertium-dbus ? Thank you very much -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#769069: systemd: Failed to start Login Service
Sounds like dbus is not installed. Paul, can you confirm that? Am 11. November 2014 08:55:00 MEZ, schrieb Martin Pitt mp...@debian.org: Control: tag -1 moreinfo Hello Paul, Paul Menzel [2014-11-11 8:40 +0100]: starting the Debian Sid/unstable system this morning, it did not boot. `Failed to start Login Service` was shown repeatedly as trying to start it again did not work. Can you please boot with adding systemd.debug-shell to the kernel command line in grub, then after the failure press Alt+F9 to get to the debug root shell? There you can run systemctl status systemd-logind.service to see what's going on. Thanks, Martin -- Martin Pitt| http://www.piware.de Ubuntu Developer (www.ubuntu.com) | Debian Developer (www.debian.org) ___ Pkg-systemd-maintainers mailing list pkg-systemd-maintain...@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-systemd-maintainers -- Diese Nachricht wurde von meinem Android-Mobiltelefon mit K-9 Mail gesendet.
Bug#768831: ettercap-common, ettercap-graphical: shipping the same file: usr/share/ettercap/ettercap.png
Thanks, that sounds like exactly the right debian/control dependency magic. Will do, and upload. BTW, why are ettercap-graphical and ettercap-textonly not co-installable? Sounds like a candidate for renaming the binaries from ettercap to ettercap-foo and using alternatives to provide the ettercap binary. But that should not be considered now, only after the jessie release for jessie+1. Reasonable question. The reason is that the graphical binary provides the functionality of the textual binary *plus* a GUI-enabled option. There are no circumstances in which installing both at the same time makes sense. The main reason for generating the non-graphical is for boxes without X etc installed, which is actually a pretty common use case for ettercap. That said, I wouldn't particularly object to using alternatives to allow co-installation just in case. Although I'd be inclined to provide the functionality by instead using dpkg-divert in ettercap-graphical to move the text-only version of /usr/bin/ettercap to /usr/bin/ettercap-text-only, thus avoiding unnecessarily increasing the footprint of ettercap-text-only. --Barak. signature.asc Description: PGP signature
Bug#769099: ark: crashes trying to add file to existing zip archive
On Tuesday 11 November 2014 11:38:16 joachim wrote: The simplest possible testcase is: - creating two textfiles - making a zip-archive of one of these file - using 'right-click-functionality' in dolphin Compress as ZIP-Archive - opening archive with ark and trying to add other textfile using 'Add File'-button Result is ark crashing with following message: Setting the format failed with the following error: No such format I can confirm the issue and the error message, but ark didn't crash on me. -- GPG: 0x138E41915C7EFED6 signature.asc Description: This is a digitally signed message part.
Bug#768022: mercurial: 3.2 has been released
Hi Javi, On Thu, 6 Nov 2014, Javi Merino wrote: On Tue, Nov 04, 2014 at 02:58:31PM +0530, Faheem Mitha wrote: Package: mercurial Version: 3.1.2-1~bpo70+1 Severity: wishlist Dear Maintainer, Hi Faheem, Please consider packaging 3.2. I can build it myself, but the Debian patches have changed enough since the last release that they are no longer trivial to re-sync. If you could just refresh the patches, that would be helpful. Thanks. It's not as easy as refreshing the patches as you have seen. I'm working on it and I hope to upload it before Sunday. It will go to experimental though. I missed your email. I just saw it now. It looks like you have just uploaded to experimental. If you need help with the Debian packaging, let the community know. There are people who can help. Regards, Faheem -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
