Bug#772983: kirkwood kernel image is too big
On Fri, 2014-12-12 at 20:59 +, Ben Hutchings wrote: I had originally planned to switch QNAP over for 3.16 but it wasn't quite ready upstream (I've forgotten why). The board files went away in 3.17 so in experimental (v3.18) appending is necessary. Once I've worked out some kinks with kirkwood in v3.18 I was planning to upload a corresponding flash-kernel which does appending for those platforms. In case you hadn't noticed, I've changed the size check in trunk so it can optionally include the size of the largest DTB. That is somewhat pessimistic in that the largest DTB probably won't be used in conjunction with the smallest partition. I had seen, I think it's a good idea despite the short comings. The size difference between the smallest and largest DTB is only 14K so it's pretty close either way. To be more accurate we'd need to store the name of the dtb corresponding to the smallest partition in the kernel source, making the (reasonable) assumption that the second smallest partition is at least 14K larger than the smallest. I don't know that it's worth it though. I enabled this for both kirkwood and orion5x, though now I think I should not have done so for orion5x. I think you were right to do so even for orion5x (in trunk at least). Right now there are only a small numbers of dtbs built on orion5x, and they are all 8K. As upstream transitions from board files to dtb that number (and the sizes) will grow, but it's not skewing our results too much to check now. At some point upstream will remove the board file support for orion5x, so I think it is fine to start checking the sizes now even while we are still on board files, so we are prewarned. [...] 2094680 2097080 2094680 + 10394 = 2105074 2097080 The orion5x machine with the smallest known kernel partition is D-Link DNS-323, with 1572792 bytes space. We currently have less than 1 KB to spare here. Thankfully this machine is still supported by board code and doesn't need a DTB. But if any of the other orion5x machines we intend to support have a similarly small kernel partition and require a DTB they will not work with this version. I don't know much about orion5x, but the flash-kernel db tells me that we don't currently append a dtb on any platform there. 1k is rather tight though, even if appending isn't needed. A security update adding 1k of binary size wouldn't be totally out of the question and it would be unfortunate to have to start disabling features in a security update. Yes, you're right. For comparison, this is what's happened over the course of wheezy stable updates: 3.2.41-2 3.2.63-2 limit growth% growth limit% iop32x:1427968 1434632 1441784 0.47 0.97 ixp4xx:1424696 1428920 1441760 0.30 1.20 kirkwood: 1606512 1613040 2097080 0.41 30.54 orion5x: 1475936 1483632 1572792 0.52 6.56 They've grown by up to about 0.5% over the course of 20 months of a ~36 month support period. That implies we want to allow for about 1% growth from the size in the .0 release. Thankfully they did all start with this much space. Currently in sid we have: 3.16.7-ckt2-1 limit growth limit% ixp4xx:14297121441760 0.84% kirkwood: 20944882097080 0.12% orion5x: 15682481572792 0.29% I misread earlier - kirkwood is about 2.5 KB below the limit, not 1. Anyway, both kirkwood and orion5x have much less than 1% of growth room and ixp4xx has slightly less. I think that some of the config changes I made in trunk should be applied to jessie/sid as well. I agree. I suppose you have some candidates in mind? Ian. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#772963: release-notes: cellphone friendly CSS
On 2014-12-12 16:13, Osamu Aoki wrote: Package: release-notes Severity: normal Tags: patch As debian-reference (jessie) package and maint-guide (jessie and Debian web) has migrated to use new CSS for jessie, it is nicer to see the same CSS for the web and package. Please consider to apply attached patch. This will create web page as: https://people.debian.org/~osamu/release-notes/index.en.html ... https://people.debian.org/~osamu/release-notes/ch-installing.en.html ... Screen is shown with gradiation+shaded box. If screen size is smaller than 5 in., cosmetic side spaces are dropped. FYI: This is git patch. If you wish to manually add these binary PNG files manually, please use 3 PNG files found in the debian-reference patckage as png/*.png . If OK I can apply these to the subversion repo. [...] Hi, Thanks for creating this patch - I love it. My only concern is that it overshadows the DRAFT watermark (I can see the remains of it in the top left corner of your page on my PC). If that could be fixed (or an alternative draft watermark/warning applied) I would readily apply this patch. ~Niels -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#773014: git-buildpackage: please support git submodules
Package: git-buildpackage Version: 0.6.22 Severity: wishlist The grub packaging git tree[0] uses a git submodule for the debian/grub-extras directory. However git-buildpackage is unaware of this and ignores it, the .debian.tar.xz ends up containing the directory itself but not its contents. It would be really useful if gbp could support this scenario. Thanks, Ian. [0] http://anonscm.debian.org/cgit/pkg-grub/grub.git/ -- System Information: Debian Release: 8.0 APT prefers testing APT policy: (990, 'testing'), (500, 'unstable'), (500, 'stable') Architecture: amd64 (x86_64) Foreign Architectures: i386, armhf, armel 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/bash Init: sysvinit (via /sbin/init) Versions of packages git-buildpackage depends on: ii devscripts2.14.11 ii git 1:2.1.3-1 ii man-db2.7.0.2-4 ii python2.7.8-2 ii python-dateutil 2.2-2 ii python-pkg-resources 5.5.1-1 Versions of packages git-buildpackage recommends: ii cowbuilder0.73 ii pristine-tar 1.32 Versions of packages git-buildpackage suggests: ii python-notify 0.1.1-4 ii unzip 6.0-12+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#641925: vimoutliner: New upstreams available
Package: vim-vimoutliner Version: 0.3.4+pristine-9.1 Followup-For: Bug #641925 Dear Maintainer, there is actually 0.3.6 now upstream. Also, what do you mean by the binary stuff? Also, please, change the upstream URL in description to either https://github.com/vimoutliner/vimoutliner or to http://vimoutliner.cepl.eu -- System Information: Debian Release: 7.7 APT prefers stable APT policy: (990, 'stable'), (500, 'stable-updates'), (500, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 3.2.0-4-amd64 (SMP w/1 CPU core) Locale: LANG=cs_CZ.UTF-8, LC_CTYPE=cs_CZ.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages vim-vimoutliner depends on: ii libpalm-perl1:1.012-1 ii libxml-writer-perl 0.615-1 ii perl5.14.2-21+deb7u2 ii python 2.7.3-4+deb7u1 ii vim 2:7.3.547-7 ii vim-nox [vim] 2:7.3.547-7 Versions of packages vim-vimoutliner recommends: ii vim-addon-manager 0.5.2 vim-vimoutliner 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#641925: vimoutliner: New upstreams available
Package: vim-vimoutliner Version: 0.3.4+pristine-9.1 Followup-For: Bug #641925 Dear Maintainer, there is actually 0.3.6 now upstream. Also, what do you mean by the binary stuff? Also, please, change the upstream URL in description to either https://github.com/vimoutliner/vimoutliner or to http://vimoutliner.cepl.eu -- System Information: Debian Release: 7.7 APT prefers stable APT policy: (990, 'stable'), (500, 'stable-updates'), (500, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 3.2.0-4-amd64 (SMP w/1 CPU core) Locale: LANG=cs_CZ.UTF-8, LC_CTYPE=cs_CZ.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages vim-vimoutliner depends on: ii libpalm-perl1:1.012-1 ii libxml-writer-perl 0.615-1 ii perl5.14.2-21+deb7u2 ii python 2.7.3-4+deb7u1 ii vim 2:7.3.547-7 ii vim-nox [vim] 2:7.3.547-7 Versions of packages vim-vimoutliner recommends: ii vim-addon-manager 0.5.2 vim-vimoutliner 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#771978: [pkg-apparmor] Bug#771978: Patch: apparmor profile for ps
Hi, parspes wrote (12 Dec 2014 23:54:07 GMT) : Do we have a consensus upon @sys from tunables/sys? I think so, yes. (I didn't notice it exists initially.) 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#772692: tau: More bashisms
On Wed, Dec 10, 2014 at 06:50:07AM +0100, Niels Thykier wrote: Package: tau Version: 2.17.3.1.dfsg-4 Severity: serious Hi, I saw you uploaded a new version of tau to fix bashisms. Unfortunately, there are still some left. E.g. in echoIfVerbose (tools/src/tau_compiler.sh) + if [ $isDebug == $TRUE ] || [ $isVerbose == $TRUE ]; then Which should have been using only one = in each of the [ ]. I'm a bit confused here: tools/src/tau_compiler.sh has been using bash upstream since ages, and checkbashisms accordingly does not complain on that file. I've been touching it in the Replace 'echo -e' patch solely because I let sed do the work and did not bother checking that it was absolutely necessary in all of the impacted scripts. I could possibly remove that useless part of the patch to be on the extra-safe side, but that seems unnecessary. OK to close this bug ? I think the safe choice for Jessie would be to mark any remaining scripts with bashisms as bash scripts. You can always properly fix them in Stretch. Yes - the goal in stretch would be to make it possible to package the most recent version, anyway. Best regards, -- Yann -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#772692: tau: More bashisms
On Sat, Dec 13, 2014 at 09:25:50AM +0100, Yann Dirson wrote: On Wed, Dec 10, 2014 at 06:50:07AM +0100, Niels Thykier wrote: Package: tau Version: 2.17.3.1.dfsg-4 Severity: serious Hi, I saw you uploaded a new version of tau to fix bashisms. Unfortunately, there are still some left. E.g. in echoIfVerbose (tools/src/tau_compiler.sh) + if [ $isDebug == $TRUE ] || [ $isVerbose == $TRUE ]; then Which should have been using only one = in each of the [ ]. I'm a bit confused here: tools/src/tau_compiler.sh has been using bash upstream since ages, and checkbashisms accordingly does not complain on that file. I've been touching it in the Replace 'echo -e' patch solely because I let sed do the work and did not bother checking that it was absolutely necessary in all of the impacted scripts. I could possibly remove that useless part of the patch to be on the extra-safe side, but that seems unnecessary. OK to close this bug ? To be complete, the only remaining report from find -name *.sh|xargs checkbashisms is a buggy [^] should be [!] about a sed regexp, and all files containing a ref to /bin/sh do have a name ending with .sh. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#773015: desktop-base (8.0.1) missing Lines login-background.svg
Package: desktop-base Version: 8.0.1 Severity: important Dear Maintainer, After ubgrading desktop-base 8.0.0 to 8.0.1 lightdm does no longer show the Lines login-background.svg because it missing in the package. No such issue using version 8.0.0. -- System Information: Debian Release: Sid Architecture: amd64 (x86_64) Regards, Jos van Wolput -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#692861: patch and NMU diff
Control: tags -1 patch
Hi,
I have rewritten Area.{C,h} to ensure proper UTF8 support,
which would close this bug and related ones (#545695, #732702).
Now html2text should always generate valid UTF8 in UTF8 mode.
I've prepared a NMU which fixes these bugs and some other minor problems.
Please see attached debdiff.
Best regards,
Dmitry Borisyuk
diff -Nru html2text-1.3.2a/debian/changelog html2text-1.3.2a/debian/changelog
--- html2text-1.3.2a/debian/changelog 2014-09-07 21:08:35.0 +0300
+++ html2text-1.3.2a/debian/changelog 2014-12-13 09:33:08.0 +0200
@@ -1,3 +1,12 @@
+html2text (1.3.2a-18.1) experimental; urgency=low
+
+ * Non-maintainer upload.
+ * Full UTF-8 support (rewritten Area.C, closes: #732702, #692861, #545695).
+ * Catch ENOMEM in {m,re}alloc_array in Area.C.
+ * Fix parsing of input args (Closes: #716064).
+
+ -- Dmitry Borisyuk q1we...@i.com.ua Sat, 13 Dec 2014 09:31:59 +0200
+
html2text (1.3.2a-18) unstable; urgency=medium
* Complete the utf8 table. (Closes: #760588) - thanks to Marcos Marado for
diff -Nru html2text-1.3.2a/debian/patches/catch-ENOMEM.patch html2text-1.3.2a/debian/patches/catch-ENOMEM.patch
--- html2text-1.3.2a/debian/patches/catch-ENOMEM.patch 1970-01-01 03:00:00.0 +0300
+++ html2text-1.3.2a/debian/patches/catch-ENOMEM.patch 2014-12-13 09:40:56.0 +0200
@@ -0,0 +1,30 @@
+Description: Catch ENOMEM in {m,re}alloc_array (prevent segfaults).
+Author: Dmitry Borisyuk q1we...@i.com.ua
+--- a/Area.C
b/Area.C
+@@ -30,7 +30,7 @@
+
+ /***/
+
+-
++#include stdio.h
+ #include stdlib.h
+ #include string.h
+ #include iostream
+@@ -45,10 +45,14 @@
+
+ /* - */
+
++static void* alloc_error() {
++ perror(html2text: error); abort();
++}
++
+ #define malloc_array(type, size)\
+-((type *) malloc(sizeof(type) * (size)))
++((type *) (malloc(sizeof(type) * (size)) ? : alloc_error()))
+ #define realloc_array(array, type, size) \
+-((array) = (type *) realloc((array), sizeof(type) * (size)))
++((array) = (type *) (realloc((array), sizeof(type) * (size)) ? : alloc_error()))
+ #define copy_array(from, to, type, count) \
+ ((void) memcpy((to), (from), (count) * sizeof(type)))
+
diff -Nru html2text-1.3.2a/debian/patches/fix-arg-parsing.patch html2text-1.3.2a/debian/patches/fix-arg-parsing.patch
--- html2text-1.3.2a/debian/patches/fix-arg-parsing.patch 1970-01-01 03:00:00.0 +0300
+++ html2text-1.3.2a/debian/patches/fix-arg-parsing.patch 2014-12-13 09:39:35.0 +0200
@@ -0,0 +1,20 @@
+Description: Fix parsing of input args (prevent segfault).
+Author: Dmitry Borisyuk q1we...@i.com.ua
+Bug-Debian: https://bugs.debian.org/716064
+--- a/html2text.C
b/html2text.C
+@@ -295,10 +295,10 @@
+ if (!strcmp(arg, -check)) { mode = MyParser::SYNTAX_CHECK; } else
+ if (!strcmp(arg, -debug-scanner)) { debug_scanner = true; } else
+ if (!strcmp(arg, -debug-parser )) { debug_parser = true;} else
+-if (!strcmp(arg, -rcfile )) { rcfile = argv[++i]; } else
+-if (!strcmp(arg, -style)) { style = argv[++i]; } else
+-if (!strcmp(arg, -width)) { if (atoi(argv[++i]) 0) width = atoi(argv[i]); } else
+-if (!strcmp(arg, -o)) { output_file_name = argv[++i]; } else
++if (!strcmp(arg, -rcfile )) { if (++i argc) rcfile = argv[i]; } else
++if (!strcmp(arg, -style)) { if (++i argc) style = argv[i];} else
++if (!strcmp(arg, -width)) { if (++i argc) if (atoi(argv[i]) 0) width = atoi(argv[i]); } else
++if (!strcmp(arg, -o)) { if (++i argc) output_file_name = argv[i]; } else
+ if (!strcmp(arg, -nobs )) { use_backspaces = false; } else
+ if (!strcmp(arg, -ascii)) { use_encoding = ASCII; } else
+ if (!strcmp(arg, -utf8 )) { use_encoding = UTF8;} else
diff -Nru html2text-1.3.2a/debian/patches/fix-utf8-support.patch html2text-1.3.2a/debian/patches/fix-utf8-support.patch
--- html2text-1.3.2a/debian/patches/fix-utf8-support.patch 1970-01-01 03:00:00.0 +0300
+++ html2text-1.3.2a/debian/patches/fix-utf8-support.patch 2014-12-13 09:44:01.0 +0200
@@ -0,0 +1,453 @@
+Description: Full proper UTF-8 support.
+ Rewritten Area.{C,h}, introduced WideChar class which represents utf8 character.
+Author: Dmitry Borisyuk q1we...@i.com.ua
+Bug-Debian: https://bugs.debian.org/732702
+Bug-Debian: https://bugs.debian.org/692861
+Bug-Debian: https://bugs.debian.org/545695
+--- a/Area.C
b/Area.C
+@@ -43,6 +43,40 @@
+
+ extern int use_encoding;
+
++int utf8_is_continuation(char ch) {
++ return (ch 0xc0) == 0x80;
++}
++
Bug#770789: Draft of option for #770789
Don Armstrong d...@debian.org writes: Please vote [A] for Decline to override, and [FD] for Further Discussion. I vote A, FD. Bdale signature.asc Description: PGP signature
Bug#768176: unblock: pioneers/15.3-1
On 2014-12-12 08:11, Roland Clobus wrote: Hello Niels, On 11/12/14 20:48, Niels Thykier wrote: Any news on the targeted fix for t-p-u? As mentioned you can include the translations *if* the you can provide us with a debdiff in December (or very early January). I'm currently working on the translation patches. I've encountered an issue that the patch files that are generated by 'quilt refresh' in the default/recommended configuration generate invalid encoded patch files when it is applied to po-files. I now know that it is caused by the --show-c-function argument to diff, which will truncate the line in the patch file where the line numbers are mentioned after a specific number of bytes, which can happen in the middle of a UTF-8 sequence. I expect to be able to finish the patch and let Bas sponsor the upload before Christmas. With kind regards, Roland Clobus Maintainer of Pioneers Thanks, please let us know once when it is ready or if it turns out that it will not be ready before Christmas. ~Niels -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#773013: .desktop files with OnlyShowIn=GNOME do not show in GNOME
This probably has something to do with it: $ echo $XDG_CURRENT_DESKTOP GNOME-Classic:GNOME On Sat, Dec 13, 2014 at 2:27 AM, Jerad Simpson jbsimp...@gmail.com wrote: Package: gnome-menus Version: 3.13.3-3 Severity: normal For example, /usr/share/applications/gnome-terminal.desktop has the following: OnlyShowIn=GNOME;Unity; It does not show in GNOME unless that line is removed. When removed, it shows up under Applications-Utilities. -- System Information: Debian Release: 8.0 APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 3.16.0-4-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: sysvinit (via /sbin/init) Versions of packages gnome-menus depends on: ii python3 3.4.2-2 pn python3:any none gnome-menus recommends no packages. gnome-menus suggests no packages. -- no debconf information
Bug#773016: ctdb: Starting CTDB fails with Unable to open /var/lib/run/ctdb/.socket_lock
Package: ctdb Version: 2.5.4+debian0-1 Severity: grave Justification: renders package unusable Dear Maintainer, CTDB can't be started as packaged. Shouldn't: --localstatedir=/var/lib in debian/rules be: --localstatedir=/var instead? That would put the socket and the lock file in the right place (/var/run/ctdb/). Thanks... peace happiness, martin -- System Information: Debian Release: 8.0 APT prefers testing APT policy: (990, 'testing'), (500, 'stable-updates'), (500, 'stable'), (300, 'unstable') Architecture: i386 (x86_64) Kernel: Linux 3.16.0-4-amd64 (SMP w/4 CPU cores) Locale: LANG=en_AU.UTF-8, LC_CTYPE=en_AU.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages ctdb depends on: ii iproute23.16.0-2 ii libc6 2.19-13 ii libpopt01.16-10 ii libtalloc2 2.1.1-2 ii libtdb1 1.3.1-1 ii libtevent0 0.9.21-1 ii lsb-base4.1+Debian13+nmu1 ii psmisc 22.21-2 ii sudo1.8.10p3-1 ii tdb-tools 1.3.1-1 ii time1.7-25 Versions of packages ctdb recommends: ii ethtool 1:3.16-1 Versions of packages ctdb suggests: pn libctdb-dev none ii logrotate3.8.7-1+b1 ii lsof 4.86+dfsg-1 -- Configuration Files: /etc/default/ctdb changed [not included] /etc/sudoers.d/ctdb [Errno 13] Permission denied: u'/etc/sudoers.d/ctdb' -- 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#773017: installation-report: root user creation
Package: installation-reports Version: 2.57 Severity: wishlist Dear Maintainer, * What led up to the situation? During installation howto, I read debian-community is interested with proper effective installation * What exactly did you do (or not do) that was effective (or ineffective)? During installation I read user creation, this probably include root password definition. As I bypass this step (my users configuration come from an ldap server) * What was the outcome of this action? I needed to launch the OS in failback mode to define the root password * What outcome did you expect instead? I suggest to ask for root password during installation, or at least to ask if root admin should be activated -- Package-specific info: Boot method: CD Image version: http://cdimage.debian.org/debian-cd/7.7.0/amd64/iso-cd/debian-7.7.0-amd64-netinst.iso Date: 2014 dec 12 Machine: HP Compaq dx2400 Partitions: df -Tl will do; the raw partition table is preferred /dev/mapper/vg_debian-root ext4 329233 238914 73321 77% / udev devtmpfs 10240 0 10240 0% /dev tmpfs tmpfs 101716 384 101332 1% /run tmpfs tmpfs 5120 0 5120 0% /run/lock tmpfs tmpfs 203420 0 203420 0% /run/shm /dev/sda1 ext2 233191 10658 210092 5% /boot /dev/mapper/vg_debian-home ext451606140 184136 48800564 1% /home /dev/mapper/vg_debian-opt ext420642428 176064 19417788 1% /opt /dev/mapper/vg_debian-tmp ext4 376807 10279 347072 3% /tmp /dev/mapper/vg_debian-usr ext4 8647944 9125807296068 12% /usr /dev/mapper/vg_debian-var ext4 2882592 5577082178452 21% /var Base System Installation Checklist: [O] = OK, [E] = Error (please elaborate below), [ ] = didn't try it Initial boot: [O] Detect network card:[O] Configure network: [O] Detect CD: [O] Load installer modules: [O] Clock/timezone setup: [O] User/password setup:[ ] Detect hard drives: [O] Partition hard drives: [O] Install base system:[O] Install tasks: [O] Install boot loader:[O] Overall install:[O] Comments/Problems: 1/ It could be interresting (at least) to ask if root admin/user should be activated. If yes, ask the root password. 2.a/ The ssh installation is a great idea, however (maybe it comes from putty config) locales doesn't behave the same in console or thourgh ssh 2.b/ Actually, in console mode I use UTF locales and thourgh ssh I need to use iso8859 locales 3/ All the following logs are not from fresh-install, I already compile (with easy success) the realtek 8192eu module. Please make sure that the hardware-summary log file, and any other installation logs that you think would be useful are attached to this report. Please compress large files using gzip. Once you have filled out this report, mail it to sub...@bugs.debian.org. == Installer lsb-release: == DISTRIB_ID=Debian DISTRIB_DESCRIPTION=Debian GNU/Linux installer DISTRIB_RELEASE=7 (wheezy) - installer build 20130613+deb7u2+b3 X_INSTALLATION_MEDIUM=cdrom == Installer hardware-summary: == uname -a: Linux demeter 3.2.0-4-amd64 #1 SMP Debian 3.2.63-2 x86_64 GNU/Linux lspci -knn: 00:00.0 Host bridge [0600]: Intel Corporation 82G33/G31/P35/P31 Express DRAM Controller [8086:29c0] (rev 02) lspci -knn: Subsystem: Hewlett-Packard Company Device [103c:2a73] lspci -knn: Kernel driver in use: agpgart-intel lspci -knn: 00:02.0 VGA compatible controller [0300]: Intel Corporation 82G33/G31 Express Integrated Graphics Controller [8086:29c2] (rev 02) lspci -knn: Subsystem: Hewlett-Packard Company Device [103c:2a73] lspci -knn: 00:1a.0 USB controller [0c03]: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #4 [8086:2937] (rev 02) lspci -knn: Subsystem: Hewlett-Packard Company Device [103c:2a73] lspci -knn: Kernel driver in use: uhci_hcd lspci -knn: 00:1a.1 USB controller [0c03]: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #5 [8086:2938] (rev 02) lspci -knn: Subsystem: Hewlett-Packard Company Device [103c:2a73] lspci -knn: Kernel driver in use: uhci_hcd lspci -knn: 00:1a.7 USB controller [0c03]: Intel Corporation 82801I (ICH9 Family) USB2 EHCI Controller #2 [8086:293c] (rev 02) lspci -knn: Subsystem: Hewlett-Packard Company Device [103c:2a73] lspci -knn: Kernel driver in use: ehci_hcd lspci -knn: 00:1b.0 Audio device [0403]: Intel Corporation 82801I (ICH9 Family) HD Audio Controller [8086:293e] (rev 02) lspci -knn: Subsystem: Hewlett-Packard Company Device [103c:2a73] lspci -knn: 00:1c.0 PCI bridge [0604]: Intel Corporation
Bug#773018: tint2: Some patches for tint2
Package: tint2 Severity: normal Hello, the current upstream for tint2 is https://code.google.com/p/tint2/ As you can see, the project is inactive (no updates since 2012), and bugs and feature requests are left open. The last updates can be listed at: https://code.google.com/feeds/p/tint2/svnchanges/basic I've found an updated fork at https://github.com/chazmcgarvey/tint2/, which repo provides several patches for tint2, adding the following enhancements and bug fixes: https://github.com/chazmcgarvey/tint2/commit/1aea2f679d269af1facc9f80870793bb43126703 fix clock to update even if it is on line two (bugfix) https://github.com/chazmcgarvey/tint2/commit/9f7b8f30f440c4ba7d9894458fa92dfa4344db03 https://code.google.com/p/tint2/issues/detail?id=381 New config parameter launcher_apps_dir: ..desktop launchers placed in the configured directory will be automatically added to tint2's program launchers section. This provides a simpler way to add launchers. (in upstream tint2, you had to add one launcher_item_app directive per launcher in the config file) https://github.com/chazmcgarvey/tint2/commit/aafb2db7a1f2b69f4f33b4c041e4c1452947daa5 https://code.google.com/p/tint2/issues/detail?id=382 Adds a new separator/freespace object: Adding 'F' to the panel_items directive now places a separator/freespace that takes the maximum available space. Useful to condense task lists on the left/right side of the panel. Can you consider adding these patches to the Debian package? Upstream developers seem to have abandoned the project and do not respond to patch requests. Thanks in advance -- System Information: Debian Release: 8.0 APT prefers testing APT policy: (500, 'testing'), (200, 'unstable'), (1, 'experimental') Architecture: i386 (i686) Kernel: Linux 3.16.0-4-686-pae (SMP w/2 CPU cores) Locale: LANG=fr_FR.utf8, LC_CTYPE=fr_FR.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages tint2 depends on: ii libatk1.0-0 2.14.0-1 ii libc6 2.19-13 ii libcairo2 1.14.0-2.1 ii libfontconfig12.11.0-6.3 ii libfreetype6 2.5.2-2 ii libgdk-pixbuf2.0-02.31.1-2+b1 ii libglib2.0-0 2.42.1-1 ii libgtk2.0-0 2.24.25-1 ii libimlib2 1.4.6-2+b3 ii libpango-1.0-01.36.8-3 ii libpangocairo-1.0-0 1.36.8-3 ii libpangoft2-1.0-0 1.36.8-3 ii libstartup-notification0 0.12-4 ii libx11-6 2:1.6.2-3 ii libxcomposite11:0.4.4-1 ii libxdamage1 1:1.1.4-2+b1 ii libxfixes31:5.0.1-2+b2 ii libxinerama1 2:1.1.3-1+b1 ii libxrandr22:1.4.2-1+b1 ii libxrender1 1:0.9.8-1+b1 tint2 recommends no packages. tint2 suggests no packages. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#773019: ghemical: FTBFS on arm64; please use autotools-dev to fix
Package: ghemical
Version: 3.0.0-1
Severity: normal
Tags: patch
User: ubuntu-de...@lists.ubuntu.com
Usertags: origin-ubuntu vivid ubuntu-patch
Dear Maintainer,
ghemical currently FTBFS on arm64. It needs a config.{sub,guess} update, using
autotools-dev.
In Ubuntu, the attached patch was applied to achieve the following:
* Use autotools-dev to update config.{sub,guess} for new arches.
Thanks for considering the patch.
Logan Rosen
-- System Information:
Debian Release: jessie/sid
APT prefers vivid-updates
APT policy: (500, 'vivid-updates'), (500, 'vivid-security'), (500, 'vivid'),
(100, 'vivid-backports')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 3.16.0-25-generic (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
diff -Nru ghemical-3.0.0/debian/control ghemical-3.0.0/debian/control
--- ghemical-3.0.0/debian/control 2011-11-27 14:19:18.0 -0500
+++ ghemical-3.0.0/debian/control 2014-12-13 04:09:07.0 -0500
@@ -8,7 +8,7 @@
pkg-config, libblas-dev, libglade2-dev ( 2.4.0), libgtk2.0-dev ( 2.6.0),
libgtkglext1-dev ( 1.0.5), libghemical-dev ( 3.0.0),
liblapack-dev, libmopac7-dev ( 1.14), liboglappth-dev ( 1.0.0),
- libopenbabel-dev ( 2.1.1), libsc-dev (= 2.3.1-2)
+ libopenbabel-dev ( 2.1.1), libsc-dev (= 2.3.1-2), autotools-dev
Standards-Version: 3.9.2
Homepage: http://bioinformatics.org/ghemical/ghemical/
Vcs-Browser: http://svn.debian.org/wsvn/debichem/unstable/ghemical/
diff -Nru ghemical-3.0.0/debian/rules ghemical-3.0.0/debian/rules
--- ghemical-3.0.0/debian/rules 2011-11-27 14:19:18.0 -0500
+++ ghemical-3.0.0/debian/rules 2014-12-08 03:27:44.0 -0500
@@ -10,7 +10,7 @@
LDFLAGS += -Wl,--as-needed
%:
- dh $@ --parallel
+ dh $@ --with autotools_dev --parallel
override_dh_auto_configure:
dh_auto_configure -- --enable-threads --enable-openbabel
Bug#770912: initramfs-tools: Add xhci-pci to base modules (linux 3.18)
On Tue, 2014-11-25 at 01:23 -0500, Brian Campbell wrote: While trying out an upstream kernel build to debug another issue, I discovered that I couldn't enter any text at my disk encryption password prompt. After bisecting, I discovered that this was due to a patch that split xhci-pci out into a separate module. Sure enough, adding that to my initrd modules list allowed me to boot and decrypt on later kernels. This should be added to the standard base modules list to avoid anyone else running into this problem. We should add xhci-plat-hcd.ko too I think. NB, I'm in the process of adding these to the d-i udebs for 3.18 onwards too. Ian. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#772926: unblock: grml-debootstrap/0.68
On Sat, 2014-12-13 at 01:54 +0100, Michael Prokop wrote: * Ivo De Decker [Fri Dec 12, 2014 at 11:20:10PM +0100]: OK. It seems 0.68 didn't reach unstable (did you get a reject?). So, please upload it (again?) to unstable, and when it's accepted, please remove the moreinfo tag from this bug. Huh, that's strange. Nope, I didn't receive a reject so far. :-/ I *think* it might be that my upload was signed with my old GPG key (for whatever reason debsign doesn't seem to honor my $DEBSIGN_KEYID setting as I just noticed, sic). I just tried to re-upload with my new key signed: http://paste.grml.org/hidden/94a66c13/ The queued log on ftp-master has: Dec 12 09:24:56 processing /grml-debootstrap_0.68_amd64.changes Dec 12 09:24:57 GnuPG signature check failed on grml-debootstrap_0.68_amd64.changes Dec 12 09:24:57 /grml-debootstrap_0.68_amd64.changes has bad PGP/GnuPG signature! Dec 12 09:24:57 Removing /grml-debootstrap_0.68_amd64.changes, but keeping its associated files for now. and then, for the new upload: Dec 13 00:54:18 processing /grml-debootstrap_0.68_amd64.changes Dec 13 00:54:18 grml-debootstrap_0.68.dsc is too small (ignored for now) Dec 13 00:54:18 grml-debootstrap_0.68_all.deb has incorrect md5 checksum; deleting it Dec 13 00:59:19 processing /grml-debootstrap_0.68_amd64.changes Dec 13 00:59:19 grml-debootstrap_0.68.dsc is too small (ignored for now) Dec 13 00:59:19 grml-debootstrap_0.68_all.deb doesn't exist (ignored for now) [repeated] The .tar.xz from the original upload and the .changes from the new one are still in the upload queue. I'd suggest dcutting them and trying again. 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#773020: gnome-core: please restore gnome-search-tool as alternative to tracker-gui
Package: gnome-core Version: 1:3.14+3 Severity: normal Because it is constantly scouring the hard-disk, tracker makes this desktop host depressingly slow because it's stealing all system resources. Until gnome-core 1:3.14+1, it was possible to install gnome-search-tool as an alternative. There was no inherent reason to drop this alternative depedency from gnome-core, so could it please be restored? Thanks! -- System Information: Debian Release: 8.0 APT prefers testing APT policy: (1001, 'testing'), (1001, 'oldstable') Architecture: i386 (i686) Kernel: Linux 3.16.0-4-686-pae (SMP w/1 CPU core) Locale: LANG=fi_FI.utf8, LC_CTYPE=fi_FI.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages gnome-core depends on: ii adwaita-icon-theme 3.14.0-2 ii at-spi2-core 2.14.0-1 ii baobab 3.14.1-1 ii caribou0.4.15-1 ii caribou-antler 0.4.15-1 ii dconf-gsettings-backend0.22.0-1 ii dconf-tools0.22.0-1 ii empathy3.12.7-1 ii eog3.14.1-1 ii evince 3.14.1-1 ii evolution-data-server 3.12.9~git20141128.5242b0-2 ii fonts-cantarell0.0.16-1 ii gdm3 3.14.1-3 ii gkbd-capplet 3.6.0-1 ii glib-networking2.42.0-2 ii gnome-backgrounds 3.14.1-1 ii gnome-bluetooth3.14.0-2 ii gnome-calculator 3.14.1-1 ii gnome-contacts 3.14.1-1 ii gnome-control-center 1:3.14.2-2 ii gnome-dictionary 3.14.1-1 ii gnome-disk-utility 3.12.1-1+b1 ii gnome-font-viewer 3.14.0-1 ii gnome-keyring 3.14.0-1+b1 ii gnome-menus3.13.3-3 ii gnome-online-accounts 3.14.2-1 ii gnome-online-miners3.14.0-2 ii gnome-packagekit 3.14.0-1 ii gnome-screenshot 3.14.0-1 ii gnome-session 3.14.0-2 ii gnome-settings-daemon 3.14.2-2 ii gnome-shell3.14.2-1 ii gnome-shell-extensions 3.14.2-1 ii gnome-sushi3.12.0-2+b1 ii gnome-system-log 3.9.90-2 ii gnome-system-monitor 3.14.1-1 ii gnome-terminal 3.14.1-1 ii gnome-themes-standard 3.14.2.2-1 ii gnome-user-guide 3.14.1-1 ii gnome-user-share 3.14.0-2 ii gsettings-desktop-schemas 3.14.1-1 ii gstreamer1.0-plugins-base 1.4.4-2 ii gstreamer1.0-plugins-good 1.4.4-2 ii gstreamer1.0-pulseaudio1.4.4-2 ii gtk2-engines 1:2.20.2-3 ii gucharmap 1:3.14.1-1 ii gvfs-backends 1.22.2-1 ii gvfs-bin 1.22.2-1 ii gvfs-fuse 1.22.2-1 ii iceweasel 31.3.0esr-1 ii libatk-adaptor 2.14.0-2 ii libcanberra-pulse 0.30-2.1 ii libcaribou-gtk-module 0.4.15-1 ii libcaribou-gtk3-module 0.4.15-1 ii libgtk-3-common3.14.5-1 ii libpam-gnome-keyring 3.14.0-1+b1 ii metacity 1:3.14.3-1 ii mousetweaks3.12.0-1 ii nautilus 3.14.1-2 ii policykit-1-gnome 0.105-2 ii pulseaudio 5.0-13 ii sound-theme-freedesktop0.8-1 ii totem 3.14.0-2 ii tracker-gui1.2.4-1 ii vino 3.14.0-2+b1 ii yelp 3.14.1-1 ii zenity 3.14.0-1 Versions of packages gnome-core recommends: ii anacron2.3-22 ii network-manager-gnome 0.9.10.0-2 Versions of packages gnome-core suggests: pn gnome 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 Archive: https://lists.debian.org/debian-bugs-dist
Bug#773021: apt-get E: Command line option 'f' [from -f] is not known.
Package: apt Version: 1.1~exp8 Severity: normal Dear Maintainer, I saw the error also in apt 1.0.9.4 as well as apt 1.1~exp8 . When I run apt-get -h there are lot of options which are given. Sharing the ones which are important here :- Options : -f Attempt to correct a system with broken dependencies in place -m Attempt to continue if archives are unlocatable Now I tried different ways and options to see if -f works. $ apt-get check -f E: Command line option 'f' [from -f] is not known. $ sudo apt-get check -f [sudo] password for shirish: E: Command line option 'f' [from -f] is not known. $ sudo apt-get check -m -f E: Command line option 'f' [from -f] is not known. As can be seen none of the above options work. Looking forward for the fix. -- Package-specific info: -- apt-config dump -- APT ; APT::Architecture amd64; APT::Build-Essential ; APT::Build-Essential:: build-essential; APT::Install-Recommends 1; APT::Install-Suggests 0; APT::Sandbox ; APT::Sandbox::User _apt; APT::Authentication ; APT::Authentication::TrustCDROM true; APT::NeverAutoRemove ; APT::NeverAutoRemove:: ^firmware-linux.*; APT::NeverAutoRemove:: ^linux-firmware$; APT::NeverAutoRemove:: ^linux-image-3\.16\.0-4-amd64$; APT::NeverAutoRemove:: ^linux-headers-3\.16\.0-4-amd64$; APT::NeverAutoRemove:: ^linux-image-extra-3\.16\.0-4-amd64$; APT::NeverAutoRemove:: ^linux-signed-image-3\.16\.0-4-amd64$; APT::NeverAutoRemove:: ^kfreebsd-image-3\.16\.0-4-amd64$; APT::NeverAutoRemove:: ^kfreebsd-headers-3\.16\.0-4-amd64$; APT::NeverAutoRemove:: ^gnumach-image-3\.16\.0-4-amd64$; APT::NeverAutoRemove:: ^.*-modules-3\.16\.0-4-amd64$; APT::NeverAutoRemove:: ^.*-kernel-3\.16\.0-4-amd64$; APT::NeverAutoRemove:: ^linux-backports-modules-.*-3\.16\.0-4-amd64$; APT::NeverAutoRemove:: ^linux-tools-3\.16\.0-4-amd64$; APT::VersionedKernelPackages ; APT::VersionedKernelPackages:: linux-image; APT::VersionedKernelPackages:: linux-headers; APT::VersionedKernelPackages:: linux-image-extra; APT::VersionedKernelPackages:: linux-signed-image; APT::VersionedKernelPackages:: kfreebsd-image; APT::VersionedKernelPackages:: kfreebsd-headers; APT::VersionedKernelPackages:: gnumach-image; APT::VersionedKernelPackages:: .*-modules; APT::VersionedKernelPackages:: .*-kernel; APT::VersionedKernelPackages:: linux-backports-modules-.*; APT::VersionedKernelPackages:: linux-tools; APT::Never-MarkAuto-Sections ; APT::Never-MarkAuto-Sections:: metapackages; APT::Never-MarkAuto-Sections:: restricted/metapackages; APT::Never-MarkAuto-Sections:: universe/metapackages; APT::Never-MarkAuto-Sections:: multiverse/metapackages; APT::Never-MarkAuto-Sections:: oldlibs; APT::Never-MarkAuto-Sections:: restricted/oldlibs; APT::Never-MarkAuto-Sections:: universe/oldlibs; APT::Never-MarkAuto-Sections:: multiverse/oldlibs; APT::Update ; APT::Update::Post-Invoke-Success ; APT::Update::Post-Invoke-Success:: test -x /usr/bin/apt-show-versions || exit 0 ; apt-show-versions -i; APT::Update::Post-Invoke-Success:: [ ! -f /var/run/dbus/system_bus_socket ] || /usr/bin/dbus-send --system --dest=org.debian.apt --type=signal /org/debian/apt org.debian.apt.CacheChanged || true; APT::Update::Post-Invoke-Success:: /usr/bin/test -e /usr/share/dbus-1/system-services/org.freedesktop.PackageKit.service /usr/bin/test -S /var/run/dbus/system_bus_socket /usr/bin/gdbus call --system --dest org.freedesktop.PackageKit --object-path /org/freedesktop/PackageKit --timeout 4 --method org.freedesktop.PackageKit.StateHasChanged cache-update /dev/null; /bin/echo /dev/null; APT::Update::Post-Invoke ; APT::Update::Post-Invoke:: [ ! -x /usr/bin/debtags ] || debtags update || true; APT::Architectures ; APT::Architectures:: amd64; APT::Compressor ; APT::Compressor::. ; APT::Compressor::.::Name .; APT::Compressor::.::Extension ; APT::Compressor::.::Binary ; APT::Compressor::.::Cost 1; APT::Compressor::gzip ; APT::Compressor::gzip::Name gzip; APT::Compressor::gzip::Extension .gz; APT::Compressor::gzip::Binary gzip; APT::Compressor::gzip::Cost 2; APT::Compressor::gzip::CompressArg ; APT::Compressor::gzip::CompressArg:: -9n; APT::Compressor::gzip::UncompressArg ; APT::Compressor::gzip::UncompressArg:: -d; APT::Compressor::bzip2 ; APT::Compressor::bzip2::Name bzip2; APT::Compressor::bzip2::Extension .bz2; APT::Compressor::bzip2::Binary bzip2; APT::Compressor::bzip2::Cost 3; APT::Compressor::bzip2::CompressArg ; APT::Compressor::bzip2::CompressArg:: -9; APT::Compressor::bzip2::UncompressArg ; APT::Compressor::bzip2::UncompressArg:: -d; APT::Compressor::xz ; APT::Compressor::xz::Name xz; APT::Compressor::xz::Extension .xz; APT::Compressor::xz::Binary xz; APT::Compressor::xz::Cost 4; APT::Compressor::xz::CompressArg ; APT::Compressor::xz::CompressArg:: -6; APT::Compressor::xz::UncompressArg ; APT::Compressor::xz::UncompressArg:: -d; APT::Compressor::lzma ; APT::Compressor::lzma::Name lzma; APT::Compressor::lzma::Extension .lzma; APT::Compressor::lzma::Binary xz; APT::Compressor::lzma::Cost 5; APT::Compressor::lzma::CompressArg ;
Bug#773022: libhogweed2: dependency on libnettle4 too weak
Package: libhogweed2
Version: 2.7.1-3+b1
Severity: serious
Justification: policy 12.3 footnote 2
Tags: patch
libhogweed2 contains a symlink /usr/share/doc/libhogweed2 - libnettle4.
Its dependency on libnettle4 is unversioned though which means, that the
copyright and changelog files can get out of sync. This violates the
Debian policy section 12.3 footnote 2.
The solution is to add libnettle4 (= ${binary:Version}) to
libhogweed2's Depends in debian/control.
Note that debhelper cannot be blamed on this, because nettle does not
use dh_installdocs --link-doc, but rather instantiates this symlink on
its own. It therefore is nettle's responsibility to add the versioned
dependency.
The same issue holds for nettle-bin.
Attaching a .debdiff for your convenience.
Helmut
diff -Nru nettle-2.7.1/debian/changelog nettle-2.7.1/debian/changelog
--- nettle-2.7.1/debian/changelog 2014-07-29 17:20:42.0 +0200
+++ nettle-2.7.1/debian/changelog 2014-12-13 11:00:55.0 +0100
@@ -1,3 +1,11 @@
+nettle (2.7.1-3.1) UNRELEASED; urgency=medium
+
+ * Non-maintainer upload.
+ * Add versioned depends on libnettle4 for packages sharing their
+/usr/share/doc to comply with Debian policy 12.3. (Closes: #-1)
+
+ -- Helmut Grohne hel...@subdivi.de Sat, 13 Dec 2014 10:59:28 +0100
+
nettle (2.7.1-3) unstable; urgency=low
* Use -fPIC instead of -fpic by default (Closes: #755769); needed on
diff -Nru nettle-2.7.1/debian/control nettle-2.7.1/debian/control
--- nettle-2.7.1/debian/control 2014-04-18 21:06:14.0 +0200
+++ nettle-2.7.1/debian/control 2014-12-13 11:01:43.0 +0100
@@ -35,7 +35,7 @@
Architecture: any
Multi-Arch: same
Pre-Depends: ${misc:Pre-Depends}
-Depends: ${shlibs:Depends}, ${misc:Depends}
+Depends: ${shlibs:Depends}, ${misc:Depends}, libnettle4 (= ${binary:Version})
Description: low level cryptographic library (public-key cryptos)
Nettle is a cryptographic library that is designed to fit easily in more or
less any context: In crypto toolkits for object-oriented languages (C++,
@@ -78,7 +78,7 @@
Package: nettle-bin
Section: misc
Architecture: any
-Depends: ${shlibs:Depends}, ${misc:Depends}
+Depends: ${shlibs:Depends}, ${misc:Depends}, libnettle4 (= ${binary:Version})
Breaks: lsh-utils ( 2.0.4-dfsg-1)
Replaces: lsh-utils ( 2.0.4-dfsg-1)
Suggests: lsh-doc
Bug#692861: patch and NMU diff
Hi Dmitry,
On Samstag, 13. Dezember 2014, Dmitry Borisyuk wrote:
I have rewritten Area.{C,h} to ensure proper UTF8 support,
which would close this bug and related ones (#545695, #732702).
Now html2text should always generate valid UTF8 in UTF8 mode.
Nice. However it is quite big. Did you try to reach the upstream maintainer
and ask him to include the patch there?
I've prepared a NMU which fixes these bugs and some other minor problems.
Thanks, but please don't do an NMU just now (we are frozen...)
cheers,
Holger
signature.asc
Description: This is a digitally signed message part.
Bug#725691: mc: erratic behaviour of mcedit as subprocess of mc -- bug still there
Hi Karstenm, I wonder whether it has anything to do with framefuffer console or with #743566 / http://www.midnight-commander.org/ticket/3208 Could you please advise if you have gpm installed and what is the value of $TERM ? Thanks. -- Best wishes, Dmitry Smirnov GPG key : 4096R/53968D1B signature.asc Description: This is a digitally signed message part.
Bug#773017: installation-report: root user creation
Zephura zeph...@free.fr writes: Package: installation-reports Version: 2.57 Severity: wishlist Dear Maintainer, * What led up to the situation? During installation howto, I read debian-community is interested with proper effective installation * What exactly did you do (or not do) that was effective (or ineffective)? During installation I read user creation, this probably include root password definition. As I bypass this step (my users configuration come from an ldap server) * What was the outcome of this action? I needed to launch the OS in failback mode to define the root password * What outcome did you expect instead? I suggest to ask for root password during installation, or at least to ask if root admin should be activated If you do not define a root password, the first normal user should be added to the 'sudo' group, which should allow that user to become root using its own password. Did this happen? If it did happen, then what you saw may not be what you were expecting, but it is the documented behaviour. Cheers, Phil. -- |)| Philip Hands [+44 (0)20 8530 9560] HANDS.COM Ltd. |-| http://www.hands.com/http://ftp.uk.debian.org/ |(| Hugo-Klemm-Strasse 34, 21075 Hamburg,GERMANY pgpq4OJ37WTz3.pgp Description: PGP signature
Bug#700810: app-install-data: a typo in spout.desktop
Just a follow up: I apologize for my rants in previous messages. The rants were mostly due to my poor judgement in my grumpy mood due to lack of sleep. They were definitely unwarranted and unfair. I would also like to express my gratitude to the maintainer of this package, Julian, for taking the best course of actions for dealing with this issue, concluding with the filing of the following bug report: Bug#772713 - RM: app-install-data -- ROM; Outdated/Not really used anymore https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=772713 and the app-install-data package has already been removed from both unstable and testing (jessie), and thus would not end up in the upcoming Debian 8.0. I look forward to interesting new developments with AppStream data for Software Center-type software! Thanks, Anthony -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#771969: Workaround
On Tue, 9 Dec 2014, Nikolaus Rath wrote: As a workaround, could you use the attached program instead of mount.s3ql? It should work just like mount.s3ql, but it will retry on any kind of DNS error. I'm still planning to fix this properly (probably by not retrying on the first resolution attempt), but that is going to take a while. Thanks Nikolaus for this and all your efforts. It should be noted for anyone else who tries to use this wrapper around the mount program, it requires python3-dugong version 3.4 (currently in experimental), it throws an exception with the 3.3 version in testing: AttributeError: 'module' object has no attribute 'HostnameNotResolvable' I'm giving it try now which should be a good test of the code and local network as I'm moving about 400GB into an S3 file system. Regards, Shannon C. Dealy | DeaTech Research Inc. de...@deatech.com |- Custom Software Development - USA Phone: +1 800-467-5820 |- Natural Building Instruction - numbers : +1 541-929-4089 |www.deatech.com -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#772771: grub2: [INTL:fr] French debconf templates translation update
Quoting Ian Campbell (i...@debian.org): On Wed, 2014-12-10 at 23:22 +0100, Christian Perrier wrote: Package: grub2 Version: N/A Severity: wishlist Tags: patch l10n Please find attached the french debconf templates update, proofread by the debian-l10n-french mailing list contributors. If you do not already use it, you might consider using the podebconf-report-po utility, which helps warning translators about changes when you modify some debconf templates in your packages. Thanks, I wasn't aware of this tool and was wondering if I was supposed to do something. Looking at podebconf-report-po it seems I could still use it to send out a request and link them all to this report with: podebconf-report-po --bts=772771 I'm assuming you haven't already done so? If not then I'll send out a call for translations and collect them in this bug. As you had suggestions from other translators to slightly modify the templates. Would you mind doing the following: - put my fr.po in place - change the templates with the new wording - run debconf-updatepo - send me (and to the bug report) the new fr.po file (which will have 1 o2 fuzzy strings because of the change in English wording Then, I'll update my translation and send it back to the bug report. Many thanks in advance. signature.asc Description: Digital signature
Bug#772771: grub2: [INTL:fr] French debconf templates translation update
On Sat, 2014-12-13 at 11:22 +0100, Christian PERRIER wrote: Quoting Ian Campbell (i...@debian.org): On Wed, 2014-12-10 at 23:22 +0100, Christian Perrier wrote: Package: grub2 Version: N/A Severity: wishlist Tags: patch l10n Please find attached the french debconf templates update, proofread by the debian-l10n-french mailing list contributors. If you do not already use it, you might consider using the podebconf-report-po utility, which helps warning translators about changes when you modify some debconf templates in your packages. Thanks, I wasn't aware of this tool and was wondering if I was supposed to do something. Looking at podebconf-report-po it seems I could still use it to send out a request and link them all to this report with: podebconf-report-po --bts=772771 I'm assuming you haven't already done so? If not then I'll send out a call for translations and collect them in this bug. As you had suggestions from other translators to slightly modify the templates. I just CCd you on my reply to those suggestions. If it is decided to go ahead and update the translations then I'll do as you asked. Cheers, Ian. Would you mind doing the following: - put my fr.po in place - change the templates with the new wording - run debconf-updatepo - send me (and to the bug report) the new fr.po file (which will have 1 o2 fuzzy strings because of the change in English wording Then, I'll update my translation and send it back to the bug report. Many thanks in advance. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#771863: [ovs-dev] Bug#771863: Service does not start or parse interfaces correctly, updating severity
Gurucharan Shetty shet...@nicira.com writes: I haven't looked at what needs to be done to handle those statements. I welcome a patch, preferably sent to d...@openvswitch.org after reading the CONTRIBUTING.md in the openvswitch repo. I assume the openvswitch repo is at https://github.com/openvswitch/ovs Do you use GitHub pull requests at all, or prefer just formatted patches to the mailing list? I would like to clarify that 2.3.1 does get rid of the check on $RUNLEVEL which was the original bug description. That's great, thanks. :) I probably should treat this as a separate bug. Would you like me to file a new bug for it in the Debian BTS, in addition to submitting an upstream patch? -- Stig Sandbeck Mathisen -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#773023: say how to just remove the forbidden notation but not install the package
Package: aptitude Version: 0.6.11-1+b1 Severity: wishlist File: /usr/share/man/man8/aptitude-curses.8.gz After This command is useful for avoiding broken versions of packages without having to set and clear manual holds. If you decide you really want the forbidden version after all, aptitude install package will remove the ban. say what to do if one just wants to remove the forbidden version that is shown in aptitude -v show package, but not install the package. Perhaps just say no when asked to confirm installation, if that is in fact how to do it. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#749833: scilab: Scilab include non-free codes
On Tue, 25 Nov 2014 21:22:51 +0100 Lucas Nussbaum lu...@debian.org wrote: On 30/05/14 at 11:29 +0900, mejiko wrote: 1) scilab-version/modules/polynomials/src/fortran/rpoly.f There is work in progress upstream (status 13 Dec 2014: Review in Progress). The amount of code is not much, but I am not able to judge the workings. Review is needed if this should go into Debian for Jessie. 2) scilab-version/modules/randlib/src/c/fsultra.c This file is currently not commented on in the upstream bug report. The versions of scilab in squeeze and wheezy already included those files, with the same license. I wonder if this shouldn't simply be jessie-ignored, given that both codes are fairly old mathematical codes. I think if Sylvestre is right with his statement Old ACM algorithms were in a kind of public domain but they updated their license policies [1] than we can jessie-ignore this. @Sylvestre: do you have any data that would substantiate this? Should we just file a bug against release.debian.org (the RT) and ask to jessie-ignore this bug? If the rpoly implementation is good than only the second file would need jessie-ignore. Paul * Touched this bug during https://wiki.debian.org/BSP/2014/12/nl/Tilburg [1] http://lists.alioth.debian.org/pipermail/debian-science-maintainers/2010-February/002806.html signature.asc Description: OpenPGP digital signature
Bug#768889: efibootmgr: diff for NMU version 0.11.0-1.1
Hi Andreas and maintainers, Andreas Bombe wrote (22 Nov 2014 15:56:56 GMT) : I've prepared an NMU for efibootmgr (versioned as 0.11.0-1.1) and uploaded it to DELAYED/5. Please feel free to tell me if I should delay it longer. I have not pushed but have attached the two commits to the collab-maint repository that I used to create this upload. This bug is marked as affecting Jessie. The version in sid is two upstream releases ahead of the one in testing, so I doubt it can be unblocked. Do you have any plans to fix this in Jessie via t-p-u? 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#773024: pm-utils: laptop-mode hook may cause heavy write performance degradation
Package: pm-utils
Version: 1.4.1-15
Severity: important
Tags: patch
The laptop-mode hook tries to save the dirty_ratio and dirty_background_ratio
values before it modifies them.
This breaks, if the user set dirty_bytes or dirty_background_bytes before. In
that case the _ratio files will read as 0.
That in turn means that on restore of the 0 values to the _ratio files,
which happens on laptop-mode switch off, dirty memory ratio will be set to
zero. This heavily breaks disk write performance and renders the system mostly
unusable.
The proposed patch tries to fix this by aborting the hook, if any ratio field
is zero.
-- System Information:
Debian Release: 8.0
APT prefers unstable
APT policy: (500, 'unstable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 3.16.0-4-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
Versions of packages pm-utils depends on:
ii powermgmt-base 1.31+nmu1
Versions of packages pm-utils recommends:
ii ethtool 1:3.16-1
ii hdparm 9.43-1.1
ii kbd 1.15.5-2
ii procps 2:3.3.9-8
ii vbetool 1.1-3
Versions of packages pm-utils suggests:
ii cpufrequtils008-1
pn radeontool none
ii wireless-tools 30~pre9-8
-- no debconf information
--- laptop-mode.orig 2014-12-13 11:55:35.527031386 +0100
+++ laptop-mode 2014-12-13 12:01:44.430429767 +0100
@@ -48,6 +48,13 @@
[ -w $VM/laptop_mode -a -w $VM/dirty_ratio ] || exit $NA
+# If the user set any of dirty_bytes or dirty_background_bytes
+# the corresponding _ratio field will appear as 0.
+# Abort in that case, because restoring 0 to any _ratio field will
+# result in disabled dirty memory and thus heavy breakage.
+[ x0 = x$(cat $VM/dirty_ratio) ] exit $NA
+[ x0 = x$(cat $VM/dirty_background_ratio) ] exit $NA
+
read_values() {
for f in $vmfiles; do
[ -r $VM/$f ] cat $VM/$f || echo 0
Bug#772602: [sh4]: Please use default compiler instead of gcc-4.7
On 12/09/2014 02:42 AM, John Paul Adrian Glaubitz wrote: On 12/09/2014 02:05 AM, maximilian attems wrote: the compiler change better be boot tested, was it? Well, the kernel package doesn't currently build on sh4 because gcc-4.7 was built with the m4-nofpu configuration missing [1]. FYI, the latest upload of the Linux kernel package still FTBFS on sh4 and it has been so for over two years now [1]. Changing the default compiler to gcc-4.8 which has the m4-nofpu configuration enabled will fix at least the current reason for the kernel package to FTBFS as this configuration is not available on gcc-4.7. Adrian [1] http://buildd.debian-ports.org/status/logs.php?pkg=linuxarch=sh4 -- .''`. John Paul Adrian Glaubitz : :' : Debian Developer - glaub...@debian.org `. `' Freie Universitaet Berlin - glaub...@physik.fu-berlin.de `-GPG: 62FF 8A75 84E0 2956 9546 0006 7426 3B37 F5B5 F913 -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#767476: transition: tilda
Hi Sebastian, Niels Thykier wrote (21 Nov 2014 18:10:31 GMT) : Unfortunately, as intrigeri suggests in his mail, we are not willing to accept this large a changeset up to or during the freeze. However, we are still willing to accept targeted fixes for important bugs for another 14 days, provided that they go through unstable. Admittedly, it would mean that you would have to revert your tilda/1.2 upload(s). This didn't happen, and the window for fixing important bugs is now closed. Sebastian, are you interested in uploading targeted fixes for RC bugs only? If not, please let the release team know, or simply close this bug report yourself. 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#772907: ITA: anarchism
control: owner -1 hol...@layer-acht.org control: retitle -1 ITA: anarchism Hi, I'll adopt anarchism and plan to maintain it in a team! :) Thanks Mauro, for all your work on this (and other) package(s)! cheers, Holger signature.asc Description: This is a digitally signed message part.
Bug#735261: mutiple upstream bugs
Hey, it is hard to descide witch upstream bug matches best: https://bugs.kde.org/show_bug.cgi?id=276856 https://bugs.kde.org/show_bug.cgi?id=288208 https://bugs.kde.org/show_bug.cgi?id=278737 https://bugs.kde.org/show_bug.cgi?id=294074 https://bugs.kde.org/show_bug.cgi?id=285063 I think the underlying problem is a race condition between sync with the sever and kmail. So if you mark a message when akonadi is performing a sync, the read status will be updated first from kmail and the overwritten by akonadi sync - kmail read status is lost. Molstly this problem is related with very big folders. Regads, sandro signature.asc Description: This is a digitally signed message part.
Bug#770772: unblock: ruby-twitter-text/1.10.0+gem-1
Hi Hideki Yamane, Pirate Praveen wrote (24 Nov 2014 16:31:26 GMT) : On Monday 24 November 2014 03:45 AM, Jonathan Wiltshire wrote: Unfortunately that diff is not against the version in testing, which includes a new upstream release. Please assess whether you think that new upstream is suitable, and follow up with a full diff. Do you think the new upstream version is suitable for jessie? Is it a bug fix only release? Ping? 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#773025: RFP: GPCSlots2 -- gpcslots2 is a text console casino for *nix.
Package: wnpp Severity: wishlist * Package name: GPCSlots2 Version : 0.4.5b Upstream Author : MikeeUSA id...@know.org * URL : https://gpcslots2.codeplex.com/releases/view/138295 * License : (GPL) Programming Lang: (Perl) Description : gpcslots2 is a text console casino for *nix. (gpcslots2 is a text console casino for *nix. It uses ascii art to represent the slot machines and the table games. It is fully featured as a slot machine game to the extent that it even supports the 3d dual lcd displays found on modern slot machine displays (--dual) by seperating out the text output. It is one of the only known text console slot machine games for linux, the other being its predecessor. I includes 5 slot machines, 2 dice games, 3 roulette games, a bank, a stock market, cash-in/cash-out, and html status printout It was previously improperly rejected because a debian maintainer did not like the authors political views on women and debian is a feminist-only project filled with social justice warriors (everyone else was kicked out years ago: see Ted Walther) It's quality is similar to many text based games Debian packages. It has been included in a polish linux distribution. It does what it was designed to do and would not have been rejected if the author was neutral or was a feminist supporter. There is no proper reason to reject it, save for the fact that the debian cult accepts only those programs who's authors profess a belief in women's rights and feminism FUCK YOU (please someone who is not a feminist cunt take a look at the program and package it)) -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#578720: vorbis-tools: Sends invalid argument to ALSA when playing some files
Hi Ron! Ron wrote: No, that's fine. Most of that was just me thinking out loud as I traced through the relevant code. That we agree on that just means we came to the same conclusion. I didn't mean to suggest you thought otherwise, I was just fleshing out the reasons I thought that was the right call to make. Ah, OK, that's good :-) And all we really know is that call into alsa-lib failed. We don't really know anything more about *why* it failed than the error code it returns. If all it returns is Invalid argument, that's all we have to go on. True, but that may be all we need, if we interpret it in the context. The wording is bad because ALSA tries to use generic error codes wherever possible, in this case the EINVAL (Invalid argument) error code from the linux system errors. It also delegates the int-to-string-translation to the linux system errors function strerror - which, of course, cannot know the ALSA context. Is there any other reason for this function to fail with EINVAL other than the device not supporting the mode we've asked for? Which other invalid argument could there be? The other arguments we pass to the function have to be OK at that point. A very quick look at the ALSA code seems to confirm that EINVAL is returned if and only if after ruling out all configurations that don't comply with the number of channels we've asked for, the remaining set of configurations would be empty. To me, that seems to be enough to interpret EINVAL in *this* *concrete* place as device doesn't support the output mode we've asked for. We can't know that was because the hardware didn't support the requested number of channels (if alsa doesn't explicitly say that) it could be for any number of reasons. It could fail for a number of other reasons, but in those other cases it wouldn't report EINVAL, would it? Right, but Set hardware channels failed doesn't explain it much differently. The string you suggested would certainly more readable. But that part isn't the main point, I think the other part is more important: And invalid parameters is all alsa told us. Yes, but this part may be interpreted in the context to provide a more detailed error message (see my explanation above). I'm not specifically objecting to improving that, but to do so it would have to be in alsa-lib, not libao. And then there'd be some risk of breaking something else using alsa if it makes assumptions about the error codes that might be returned. [...] You might be able to do something more in ALSA, but whether that's a good idea, and whether its maintainers would be keen to do it is a question you'd have to run past them. If we can't work anything out for libao, then that's the next (and last) thing I would try. But I see more chances for this to happen in libao. If ALSA sticks to generic Linux system error codes almost everywhere, then they probably won't abandon that principle for this little issue. And then there's the risk of breaking other software by changing the error code, like you said. :-( (or close it with a patch sent upstream to note this in the ogg123 docs, which might be useful regardless of what the ALSA folk do). That would at least keep the users from thinking that ogg123 or libao is broken - at least those that read documentation ;-) Thanks again for you collaboration! Cheers, Martin -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#773026: screen does not lock on suspend (jessie regression)
Package: gnome-screensaver Version: 3.6.1-2 Severity: grave Tags: security patch Dear maintainer, After upgrading my desktop from wheezy to jessie (w/ GNOME Flashback mode), I was surprised to find that closing the lid of my laptop suspended the system, but upon resume the screen was not locked and no password prompt was needed to actually resume working on my screen. Suffice to say, I think that's a security issue and thus, release critical. I investigated this quite a bit; it looks like with jessie's version, GNOME doesn't use ConsoleKit anymore, but the alternative codepath for this, namely handling systemd-login events, has been turned off by passing --without-systemd to configure, over two years ago, with no justification in the changelog. Even with systemd support, though, it seems that in the (very old) upstream version only Lock events are being processed, not suspend (PrepareForSleep) ones (like gnome-shell does). gnome-screensaver is abandoned upstream, so I assume the API plans changed along the way over the past two and a half years. Fortunately, Ubuntu has prepared a patch for this and a) is trivial enough, b) has been released with several Ubuntu versions and hence is tested in the wild. While at it, I also ported another couple of Ubuntu patches that while not strictly needed, help considerably in this use case (namely, a) adding support for non-systemd Linux systems and b) not leaking screen contents on resume). Attached you will find a patch for the package to address this. The total debdiff is: configure.ac |2 +- src/gs-listener-dbus.c | 33 +++-- src/gs-listener-dbus.h |1 + src/gs-manager.c |2 +- src/gs-monitor.c | 16 5 files changed, 50 insertions(+), 4 deletions(-) ...and is easily readable and understood, as well as widely tested. I would definitely recommend including this in jessie. Best, Faidon diff -Nurp gnome-screensaver-3.6.1/debian/changelog gnome-screensaver-3.6.1-suspendlock/debian/changelog --- gnome-screensaver-3.6.1/debian/changelog 2014-09-11 23:26:14.0 +0300 +++ gnome-screensaver-3.6.1-suspendlock/debian/changelog 2014-12-13 13:03:22.112670213 +0200 @@ -1,3 +1,20 @@ +gnome-screensaver (3.6.1-2.1) UNRELEASED; urgency=medium + + * Non-maintainer upload. + * Reenable support for locking the screen on suspend. +- Build with systemd support by passing --with-systemd=auto to configure + and build-depending on libsystemd-login-dev. Use auto and a + [linux-any] dependency to keep compatibility with non-Linux systems. +- 00git_logind_check.patch from Ubuntu/upstream, to make this dependent on + just logind, not systemd-as-pid1, as recommended by systemd upstream + Debian systemd maintainers. Drops libsystemd-daemon-dev build-dep. +- 31_lock_screen_on_suspend.patch from Ubuntu, to listen for logind's + PrepareForSleep signal, similarly to gnome-shell's behavior. +- 14_no_fade_on_user_switch.patch from Ubuntu, as to not fade on screen + lock. Prevents leaking of the screen contents on resume from suspend. + + -- Faidon Liambotis parav...@debian.org Sat, 13 Dec 2014 11:32:25 +0200 + gnome-screensaver (3.6.1-2) unstable; urgency=medium * Team upload diff -Nurp gnome-screensaver-3.6.1/debian/control gnome-screensaver-3.6.1-suspendlock/debian/control --- gnome-screensaver-3.6.1/debian/control 2014-12-13 12:36:01.941262458 +0200 +++ gnome-screensaver-3.6.1-suspendlock/debian/control 2014-12-13 13:02:25.484828745 +0200 @@ -19,8 +19,7 @@ Build-Depends: cdbs, libgtk-3-dev (= 3.0.0), libgnome-desktop-3-dev (= 3.1.91), libgnomekbd-dev (= 2.91.91), -# libsystemd-login-dev [linux-any], -# libsystemd-daemon-dev [linux-any], + libsystemd-login-dev [linux-any], libxklavier-dev, libx11-dev, libxt-dev, diff -Nurp gnome-screensaver-3.6.1/debian/control.in gnome-screensaver-3.6.1-suspendlock/debian/control.in --- gnome-screensaver-3.6.1/debian/control.in 2014-09-11 23:21:50.0 +0300 +++ gnome-screensaver-3.6.1-suspendlock/debian/control.in 2014-12-13 13:02:17.124852278 +0200 @@ -15,8 +15,7 @@ Build-Depends: cdbs, libgtk-3-dev (= 3.0.0), libgnome-desktop-3-dev (= 3.1.91), libgnomekbd-dev (= 2.91.91), -# libsystemd-login-dev [linux-any], -# libsystemd-daemon-dev [linux-any], + libsystemd-login-dev [linux-any], libxklavier-dev, libx11-dev, libxt-dev, diff -Nurp gnome-screensaver-3.6.1/debian/patches/00git_logind_check.patch gnome-screensaver-3.6.1-suspendlock/debian/patches/00git_logind_check.patch --- gnome-screensaver-3.6.1/debian/patches/00git_logind_check.patch 1970-01-01 02:00:00.0 +0200 +++
Bug#769961: hard-coded UIDs and GIDs
Hans-Christoph Steiner wrote (12 Dec 2014 12:32:59 GMT) : First of all, please don't break threads. Sorry, I don't understand what you mean by this. I think that Ivo meant that your previous email (54874ee7.9020...@eds.org) was a reply to his (20141119190826.ga19...@ugent.be), but was lacking References and In-Reply-To headers. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#768368: unblock: wxglade/0.7.0-2
Thank you for the ping, dear Adam! I searched the last e-mail which I sent with --supposedly-- a source debdiff. It was sent the 7th November (Message-ID: 20141107110456.ga7...@georges.khaznadar.fr), but it missed then announced attachment, hence my mistake. hereby attach the requested file, wxglade.debdiff. Best regards, Georges. Adam D. Barratt a écrit : On Fri, 2014-11-21 at 18:50 +0100, Niels Thykier wrote: We are still waiting for a source debdiff from you on wxglade. Please attach it to a reply of this mail at your earliest convenience. Ping? Regards, Adam -- Georges KHAZNADAR et Jocelyne FOURNIER 22 rue des mouettes, 59240 Dunkerque France. Téléphone +33 (0)3 28 29 17 70 [The following lists of changes regard files as different if they have different names, permissions or owners.] Files in second .changes but not in first - -rw-r--r-- root/root /usr/lib/python2.7/dist-packages/wxGlade-0.7.0.egg-info -rw-r--r-- root/root /usr/lib/python2.7/dist-packages/wxglade/bugdialog.py -rw-r--r-- root/root /usr/lib/python2.7/dist-packages/wxglade/bugdialog_ui.py -rw-r--r-- root/root /usr/lib/python2.7/dist-packages/wxglade/codegen/perl_codegen.py -rw-r--r-- root/root /usr/lib/python2.7/dist-packages/wxglade/compat.py -rw-r--r-- root/root /usr/lib/python2.7/dist-packages/wxglade/edit_sizers/cpp_sizers_codegen.py -rw-r--r-- root/root /usr/lib/python2.7/dist-packages/wxglade/edit_sizers/py_sizers_codegen.py -rw-r--r-- root/root /usr/lib/python2.7/dist-packages/wxglade/edit_sizers/xrc_sizers_codegen.py -rw-r--r-- root/root /usr/lib/python2.7/dist-packages/wxglade/log.py -rw-r--r-- root/root /usr/lib/python2.7/dist-packages/wxglade/preferences_ui.py -rw-r--r-- root/root /usr/lib/python2.7/dist-packages/wxglade/preferencesdialog.py -rw-r--r-- root/root /usr/lib/python2.7/dist-packages/wxglade/res/bugdialog_ui.wxg -rw-r--r-- root/root /usr/lib/python2.7/dist-packages/wxglade/res/preferences_ui.wxg -rw-r--r-- root/root /usr/lib/python2.7/dist-packages/wxglade/wcodegen/__init__.py -rw-r--r-- root/root /usr/lib/python2.7/dist-packages/wxglade/wcodegen/dialogs.py -rw-r--r-- root/root /usr/lib/python2.7/dist-packages/wxglade/wcodegen/mixins.py -rw-r--r-- root/root /usr/lib/python2.7/dist-packages/wxglade/widget_builder.py -rw-r--r-- root/root /usr/lib/python2.7/dist-packages/wxglade/widgets/bitmap_button/wconfig.py -rw-r--r-- root/root /usr/lib/python2.7/dist-packages/wxglade/widgets/button/wconfig.py -rw-r--r-- root/root /usr/lib/python2.7/dist-packages/wxglade/widgets/calendar_ctrl/wconfig.py -rw-r--r-- root/root /usr/lib/python2.7/dist-packages/wxglade/widgets/checkbox/wconfig.py -rw-r--r-- root/root /usr/lib/python2.7/dist-packages/wxglade/widgets/combo_box/wconfig.py -rw-r--r-- root/root /usr/lib/python2.7/dist-packages/wxglade/widgets/datepicker_ctrl/lisp_codegen.py -rw-r--r-- root/root /usr/lib/python2.7/dist-packages/wxglade/widgets/datepicker_ctrl/perl_codegen.py -rw-r--r-- root/root /usr/lib/python2.7/dist-packages/wxglade/widgets/datepicker_ctrl/wconfig.py -rw-r--r-- root/root /usr/lib/python2.7/dist-packages/wxglade/widgets/dialog/wconfig.py -rw-r--r-- root/root /usr/lib/python2.7/dist-packages/wxglade/widgets/frame/wconfig.py -rw-r--r-- root/root /usr/lib/python2.7/dist-packages/wxglade/widgets/gauge/wconfig.py -rw-r--r-- root/root /usr/lib/python2.7/dist-packages/wxglade/widgets/hyperlink_ctrl/wconfig.py -rw-r--r-- root/root /usr/lib/python2.7/dist-packages/wxglade/widgets/list_box/wconfig.py -rw-r--r-- root/root /usr/lib/python2.7/dist-packages/wxglade/widgets/list_ctrl/wconfig.py -rw-r--r-- root/root /usr/lib/python2.7/dist-packages/wxglade/widgets/notebook/wconfig.py -rw-r--r-- root/root /usr/lib/python2.7/dist-packages/wxglade/widgets/panel/wconfig.py -rw-r--r-- root/root /usr/lib/python2.7/dist-packages/wxglade/widgets/radio_button/wconfig.py -rw-r--r-- root/root /usr/lib/python2.7/dist-packages/wxglade/widgets/slider/wconfig.py -rw-r--r-- root/root /usr/lib/python2.7/dist-packages/wxglade/widgets/spin_button/wconfig.py -rw-r--r-- root/root /usr/lib/python2.7/dist-packages/wxglade/widgets/spin_ctrl/wconfig.py -rw-r--r-- root/root /usr/lib/python2.7/dist-packages/wxglade/widgets/splitter_window/wconfig.py -rw-r--r-- root/root /usr/lib/python2.7/dist-packages/wxglade/widgets/static_bitmap/wconfig.py -rw-r--r-- root/root /usr/lib/python2.7/dist-packages/wxglade/widgets/static_line/wconfig.py -rw-r--r-- root/root /usr/lib/python2.7/dist-packages/wxglade/widgets/static_text/wconfig.py -rw-r--r-- root/root /usr/lib/python2.7/dist-packages/wxglade/widgets/statusbar/__init__.py -rw-r--r-- root/root /usr/lib/python2.7/dist-packages/wxglade/widgets/statusbar/codegen.py -rw-r--r-- root/root
Bug#772612: not reproducable
Hey, I cant reproduce the behavour in 4:4.14.2-2: (sent folder, inbox,...) * double-click at any message opens the mail in view mode not edit mode * open it with edit mode (press T) opens the mail in edit mode but do NOT delete the mail (outbox) * double-click at the mail open it as expected in edit mode and delete the mail from outbox * asks for saving (save in draft - saves it to draft, discard restore the mail in the outbox) I would suggest you test with a clean user and/or check all identities. It sounds like one identity uses the sent folder as outbox. Regads, sandro signature.asc Description: This is a digitally signed message part.
Bug#761647: kde-full: an poweroff never succeed with kde
You can close the Bug. M Sandro Knau give me the solution modify the file /etc/kde4/kdm/kdmrc with the right command. Philippe Merlin
Bug#524759: sign/encryption on daily base
tag 524759 +moreinfo thanks I use gpg signing and encryption in kmail daily and it works for me. I think at least with kmail 4.14 this should be fixed. Regads, sandro signature.asc Description: This is a digitally signed message part.
Bug#772612: kmail: Sent message opened for editing by default and can be removed from sent by saving
Well. Logoff, logon, and inbox is back to normal behavior (double-clicking the message in the list opens it for reading, not editing). Sent-mail is still exactly as described. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#772890: (no subject)
I’ve updated the package tonight and already sent out the RFS. So, please be patient. If you want to have it now and prefer the packaged version over pip or other methods, you can download the version submitted as RFS here: https://www.yrden.de/debian/livestreamer/ Cheers Stefan signature.asc Description: OpenPGP digital signature
Bug#658190: update
tag 658190 +moreinfo thanks There was no update in the last two years. please update this bugreport if this is still an issue in 4.14.2. Also an example would be nice like this: I'm writing an email to : u...@example.org I have gpg keys for: u...@example.org, us...@example.org and u...@example.com kmail selectes: us...@example.org to encrypt, but i expceted u...@example.com, because ... It also mattes, if you trust a key and/or if there are gpg keys attached to the addressbook. Regads, sandro signature.asc Description: This is a digitally signed message part.
Bug#773027: libopenexr6: New upstream release: 2.2.0
Package: libopenexr6 Version: 1.6.1-8 Severity: normal Dear Maintainer, There is a new upstream for openexr. It would be nice to update it. Thanks. -- System Information: Debian Release: 8.0 APT prefers unstable APT policy: (990, 'unstable'), (500, 'testing'), (500, 'stable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 3.16.0-4-amd64 (SMP w/8 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages libopenexr6 depends on: ii libc6 2.19-13 ii libgcc11:4.9.2-7 ii libilmbase61.0.1-6.1 ii libstdc++6 4.9.2-7 ii multiarch-support 2.19-13 ii zlib1g 1:1.2.8.dfsg-2+b1 libopenexr6 recommends no packages. libopenexr6 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#770165: livestreamer: After upgrading python2.7 from 2.7.8-11 to 2.7.8-12 livestreamer don't works anymore
On Sat, Dec 13, 2014 at 03:07:34AM +0100, Stefan Breunig wrote: I've tried this on a recent unstable and it works for me. To be exact, the versions used are: python2.7 2.7.9-1 amd64 libpython2.7-stdlib:amd64 2.7.9-1 Yes, http://www3.nhk.or.jp/nhkworld/ works, but http://www.ilive.to/view/68968 doesn't with the new livestreamer 1.11.1-1 release. Can you check if this issue has been resolved for you as well with the new Python 2.7 upload? livestreamer 1.11.1-1 still doesn't available from http://cdn.debian.net/ *** ### Vladimir Stavrinov ### vstavri...@gmail.com *** -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#768368: unblock: wxglade/0.7.0-2
On Sat, 2014-12-13 at 12:41 +0100, Georges Khaznadar wrote: Thank you for the ping, dear Adam! I searched the last e-mail which I sent with --supposedly-- a source debdiff. It was sent the 7th November (Message-ID: 20141107110456.ga7...@georges.khaznadar.fr), but it missed then announced attachment, hence my mistake. Neither lists.d.o nor GMANE have any record of that message. hereby attach the requested file, wxglade.debdiff. Thanks, but that's a binary debdiff, not a source one as requested - i.e. a debdiff of the .dsc files. 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#773028: system-config-lvm: Typo in the package description
Package: system-config-lvm Version: 1.1.16-1 Severity: minor Dear Maintainer, while translating the package description I found a typo in the 7th row Unitnitialized Entities. I guess it should be Uninitialized Entities. Thanks -- System Information: Debian Release: 7.7 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'proposed-updates'), (500, 'stable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.2.0-4-rt-amd64 (SMP w/2 CPU cores; PREEMPT) Locale: LANG=fi_FI.utf8, LC_CTYPE=fi_FI.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages system-config-lvm depends on: ii gettext 0.18.1.1-9 ii gsfonts 1:8.11+urwcyr1.0.7~pre44-4.2 ii lvm22.02.95-8 ii menu2.1.46 ii python 2.7.3-4+deb7u1 ii python-glade2 2.24.0-3+b1 ii python-gnome2 2.28.1+dfsg-1 ii python-gtk2 2.24.0-3+b1 ii python-support 1.0.15 system-config-lvm recommends no packages. system-config-lvm 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#772953: Enable several Kconfigs to support OMAP5432 uEVM devboard
Control: tags -1 +pending On Mon, 2014-12-01 at 02:12 +0800, Chen Baozi wrote: With the patch attached, the OMAP5432 uEVM can be supported by the current unstable kernel. Thanks, I've applied this to the debian-kernel svn tree for the next unstable upload. For future reference the debian/config stuff is supposed to be alphabetical by Kconfig path, so I've moved the things you added around. At some point (e.g. after upload, when this bug gets closed) please could you update https://wiki.debian.org/DebianKernel/ARMMP with this new platform. After eyeballing the resulting .config diff I've also enabled the following on top of what you did: - CONFIG_PINCTRL_PALMAS - CONFIG_GPIO_PALMAS - CONFIG_RTC_DRV_PALMAS If you care about Debian Installer support then you should also check whether any of the newly added modules need to be added to the installer udebs (which you can mainly do via the module lists under debian/installer/armhf/modules/armhf-armmp/). I've added dwc3-omap to usb-modules already since that one seemed obvious. Ian. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#773029: groonga-server-common: purging deletes conffiles owned by other packages: /etc/groonga/{groonga.conf, synonyms.tsv}
Package: groonga-server-common Version: 4.0.6.1-2 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed your package removes files that were installed by another package. The removed files were already present before the package was installed, they may have been shipped or created by a dependency. This could be a violation of policy 10.7.4 (Sharing configuration files), see https://www.debian.org/doc/debian-policy/ch-files.html#s10.7.4 or policy chapter 6 (Package maintainer scripts...), see https://www.debian.org/doc/debian-policy/ch-maintainerscripts.html or policy 7.6 (Overwriting files...), see https://www.debian.org/doc/debian-policy/ch-relationships.html#s-replaces If a directory is used by several packages, all should ship it as part of the package (possibly empty, using $package.dirs to create it), and no package should mkdir/rmdir it in the maintainer scripts as dpkg will take care of this. From the attached log (scroll to the bottom...): Removing groonga-server-common (4.0.6.1-2) ... Purging configuration files for groonga-server-common (4.0.6.1-2) ... 0m24.4s ERROR: FAIL: debsums reports modifications inside the chroot: debsums: missing file /etc/groonga/groonga.conf (from groonga-bin package) debsums: missing file /etc/groonga/synonyms.tsv (from libgroonga0:amd64 package) I didn't check, but there is probably a rm -rf /etc/groonga in the postrm. cheers, Andreas groonga-server-common_4.0.6.1-2.log.gz Description: application/gzip
Bug#767597: mariadb-server-10.0: piuparts / Package purging left files on system
On Sat, 1 Nov 2014 14:47:19 +0200 =?UTF-8?B?T3R0byBLZWvDpGzDpGluZW4=?= o...@seravo.fi wrote: More information: In the files (mariadb/mysql)-server.X.X.postrm there is a section that does the removal and it looks like this: db_input high mysql-server-10.0/postrm_remove_databases || true I recently added (in piuparts) preseeding to enable database cleanup for all the new mysql server variants ... so most of these issues should be fixed now ... There is also a packagename mismatch needed here: percona-xtradb-cluster-server-5.5 mysql- server-5.1/postrm_remove_databases boolean true but I didn't file a bug so far. Andreas -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#772920: [Pkg-libvirt-maintainers] Bug#772920: virt-manager: ImportError: No module named virtinst
On Fri, Dec 12, 2014 at 02:33:23PM +, Thorsten Glaser wrote: Guido G�nther dixit: The module is shipped by the virtinst package. Can you check /usr/share/virt-manager for that: ls -l /usr/share/virt-manager/virtinst/ ls: cannot access /usr/share/virt-manager/virtinst/: No such file or directory But: ii virtinst 1:1.0.1-4 all Programs to create and clone virtual machines Huh? After “sudo apt-get install --reinstall virtinst”, virt-manager works. Maybe /usr/share/virt-manager/virtinst was a symlink once, or something else did a symlink/directory change, which is not supported by dpkg? This is the only way I can explain this… Not that I could remember. Since it's not reproducible I'm tagging as such. If nobody else chimes in I'm inclinde to close this. The changes where we merged virtinst into virt-manager happened back in 2013 and I've not seen a similar report so far. Cheers, -- Guido -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#770165: livestreamer: After upgrading python2.7 from 2.7.8-11 to 2.7.8-12 livestreamer don't works anymore
Hi, please only report only one issue per bug. Otherwise it's much harder to mark an issue solved and similar. I’ll close this bug, as it’s been fixed by a new Python upload to unstable. Thanks, Stefan signature.asc Description: OpenPGP digital signature
Bug#773030: mariadb-server-10.0: fails to install: rm: cannot remove '/var/lib/mysql/debian-*.flag': No such file or directory
Package: mariadb-server-10.0 Version: 10.0.15-1 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed your package failed to install. As per definition of the release team this makes the package too buggy for a release, thus the severity. From the attached log (scroll to the bottom...): Selecting previously unselected package mariadb-server-10.0. (Reading database ... 8998 files and directories currently installed.) Preparing to unpack .../mariadb-server-10.0_10.0.15-1_amd64.deb ... Unpacking mariadb-server-10.0 (10.0.15-1) ... Setting up mariadb-server-10.0 (10.0.15-1) ... Stopping MariaDB database server: mysqld. rm: cannot remove '/var/lib/mysql/debian-*.flag': No such file or directory dpkg: error processing package mariadb-server-10.0 (--configure): subprocess installed post-installation script returned error exit status 1 Errors were encountered while processing: mariadb-server-10.0 cheers, andreas mariadb-server-10.0_10.0.15-1.log.gz Description: application/gzip
Bug#752743: (no subject)
Hi, thank you for providing the new ilive.to test link. Since this is working locally (see below), I assume the changes for ilive.to made in 1.11.0 of livestreamer has fixed your issue. The updated version of livestreamer has already been submitted for review. I will verify the given example still works once the package has migrated to unstable. On a general note you might be better off reporting broken streams/sites directly upstream. I don’t directly work on livestreamer and only forward your reports. You can find the upstream bug tracker at: https://github.com/chrippa/livestreamer/issues Cheers, Stefan stefan@xeen ~ $ livestreamer --version livestreamer 1.11.1 stefan@xeen ~ $ livestreamer http://www.ilive.to/view/68968 best [cli][info] Found matching plugin streamlive for URL http://www.ilive.to/view/68968 [cli][info] Available streams: 296k (worst), live (best) [cli][info] Opening stream: live (rtmp) [cli][info] Starting player: mpv [cli][info] Player closed [cli][info] Stream ended signature.asc Description: OpenPGP digital signature
Bug#750910: Fwd: Untagging jessie
FYI: I have removed the jessie tag, as - the Jessie Freeze policy in effect (i.e. not reasonable to have the new upstream version 1.1.0-1 that's in Git be included in Jessie) - the package is already removed from Testing (on 2014-07-18) Cheers, +Emilien signature.asc Description: OpenPGP digital signature
Bug#768070: subscription
tag: 768070 +moreinfo thanks Normaly kmail respects the subscription state of a folder. And if you only creates a new folder and to not subscribe to it, it is not displayed inside kmail. Please check (right click on any folder of the account - serverside subscription). If you disable serverside subscription you see all available folders. With these settings it works for me creating a folder within sieve and see it within kmail. Regads, sandro signature.asc Description: This is a digitally signed message part.
Bug#773014: git-buildpackage: please support git submodules
On Sat, 2014-12-13 at 12:58 +0100, Guido Günther wrote: On Sat, Dec 13, 2014 at 08:12:00AM +, Ian Campbell wrote: Package: git-buildpackage Version: 0.6.22 Severity: wishlist The grub packaging git tree[0] uses a git submodule for the debian/grub-extras directory. However git-buildpackage is unaware of this and ignores it, the .debian.tar.xz ends up containing the directory itself but not its contents. It would be really useful if gbp could support this scenario. Check the --git-submodules option. Thanks, I must have searched the wrong manpage or typo-ed something, because I can't explain how I missed it otherwise! Ian. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#672530: Still occurring
Tag: 672530 +moreinfo thanks Is this bug still valid in kmail 4.14? It would also help to have a sample mail attached. Than everyone could test one there own. Regads, sandro -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#773031: unblock: haskell-hoogle/4.2.33-4
Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: unblock -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Please unblock package haskell-hoogle. It includes a change to the trigger file to avoid a trigger cycle, as advised by Guillem Jover. unblock haskell-hoogle/4.2.33-4 - -- System Information: Debian Release: 8.0 APT prefers unstable APT policy: (500, 'unstable'), (101, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386, armhf Kernel: Linux 3.16.0-4-amd64 (SMP w/4 CPU cores) Locale: LANG=de_DE.utf8, LC_CTYPE=de_DE.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) -BEGIN PGP SIGNATURE- Version: GnuPG v1 iEYEARECAAYFAlSMOgIACgkQ9ijrk0dDIGzCpgCeJ5Vd6nKsLfTf3i4cUBinLk9P YDEAnR455JrQZ9xSHyq4u3zKeOPTDCfX =dN1O -END PGP SIGNATURE- diff -Nru haskell-hoogle-4.2.33/debian/changelog haskell-hoogle-4.2.33/debian/changelog --- haskell-hoogle-4.2.33/debian/changelog 2014-11-07 15:54:40.0 +0100 +++ haskell-hoogle-4.2.33/debian/changelog 2014-12-13 14:05:12.0 +0100 @@ -1,3 +1,10 @@ +haskell-hoogle (4.2.33-4) unstable; urgency=medium + + * Make the trigger -noawait, to avoid trigger cycles, as recommended by +Guillem Jover (Closes: #772867) + + -- Joachim Breitner nome...@debian.org Sat, 13 Dec 2014 14:05:12 +0100 + haskell-hoogle (4.2.33-3) unstable; urgency=medium * Demote Recommends: apache2 to suggests (Closes: #768447) diff -Nru haskell-hoogle-4.2.33/debian/hoogle.triggers haskell-hoogle-4.2.33/debian/hoogle.triggers --- haskell-hoogle-4.2.33/debian/hoogle.triggers 2012-10-13 13:29:42.0 +0200 +++ haskell-hoogle-4.2.33/debian/hoogle.triggers 2014-12-13 14:04:35.0 +0100 @@ -1 +1 @@ -interest /usr/lib/ghc-doc/hoogle +interest-noawait /usr/lib/ghc-doc/hoogle diff -Nru haskell-hoogle-4.2.33/debian/source/local-options haskell-hoogle-4.2.33/debian/source/local-options --- haskell-hoogle-4.2.33/debian/source/local-options 1970-01-01 01:00:00.0 +0100 +++ haskell-hoogle-4.2.33/debian/source/local-options 2012-10-13 13:29:44.0 +0200 @@ -0,0 +1 @@ +unapply-patches
Bug#686968: pending - fixed in git
control: tags -1 + pending Hi, this bug is fixed in git, currently just in a develop branch and not uploaded, while I'm waiting for confirmation that http://lists.alioth.debian.org/mailman/listinfo/collab-maint-devel still works and is usable as maintainer address. http://anonscm.debian.org/cgit/collab-maint/anarchism.git/ cheers, Holger signature.asc Description: This is a digitally signed message part.
Bug#769108: asterisk: rr_copy array too small for some record-route headers
Control: -1 + patch
On Tue, Nov 11, 2014 at 10:56:34AM +0100, Dirk Teurlings - SIGNET B.V. wrote:
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.
Converted into a patch. Find it attached.
For now I have set mine to 8192. This completely resolves the issue.
To avoid the risc of memory exhausting enlarged from 256 to 512.
Groeten
Geert Stappers
--
Leven en laten leven
From 940660f2d8f4e4551044032350bf5008c95317a0 Mon Sep 17 00:00:00 2001
From: Stappers Geert stapp...@paddy.gpm.stappers.nl
Date: Sat, 13 Dec 2014 13:44:11 +0100
Subject: [PATCH] Transformed #769108 into a patch.
It is against the Wheezy branch
modified: debian/changelog
new file: debian/patches/rr_copy_array_too_small
modified: debian/patches/series
---
debian/changelog | 8 +--
debian/patches/rr_copy_array_too_small | 41 ++
debian/patches/series | 1 +
3 files changed, 48 insertions(+), 2 deletions(-)
create mode 100644 debian/patches/rr_copy_array_too_small
diff --git a/debian/changelog b/debian/changelog
index 782bafc..552b920 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,9 +1,13 @@
-asterisk (1:1.8.13.1~dfsg1-3+deb7u4) UNRELEASED; urgency=low
+asterisk (1:1.8.13.1~dfsg1-3+deb7u4.1) UNRELEASED; urgency=low
+ [ Tzafrir Cohen ]
* Patch AST-2014-001 (CVE-2014-2286) - Stack overflow in HTTP processing
of Cookie headers.
- -- Tzafrir Cohen tzaf...@debian.org Wed, 12 Mar 2014 22:50:01 +0200
+ [ Stappers Geert ]
+ * rr_copy array in chan_sip.c larger (Closes: #769108)
+
+ -- Stappers Geert stapp...@debian.org Sat, 13 Dec 2014 13:29:15 +0100
asterisk (1:1.8.13.1~dfsg1-3+deb7u3) stable-security; urgency=high
diff --git a/debian/patches/rr_copy_array_too_small b/debian/patches/rr_copy_array_too_small
new file mode 100644
index 000..9af380b
--- /dev/null
+++ b/debian/patches/rr_copy_array_too_small
@@ -0,0 +1,41 @@
+Origin: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=769108
+Author: Dirk Teurlings - SIGNET B.V. dteurli...@signet.nl
+Description: rr_copy array too small for some record-route headers
+
+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.
+
+
+Transforming that information into an unified diff was
+done by Geert Stappers stapp...@stappers.nl.
+
+Stappers choose for s/256/512/ to avoid the risc of memory exhausting.
+
+
+--- a/channels/chan_sip.c
b/channels/chan_sip.c
+@@ -14231,7 +14231,7 @@ static void build_route(struct sip_pvt *p, struct sip_request *req, int backward
+ /* 1st we pass through all the hops in any Record-Route headers */
+ for (;;) {
+ /* Each Record-Route header */
+- char rr_copy[256];
++ char rr_copy[512];
+ char *rr_copy_ptr;
+ char *rr_iter;
+ rr = __get_header(req, Record-Route, start);
diff --git a/debian/patches/series b/debian/patches/series
index 1922f76..96c133f 100644
--- a/debian/patches/series
+++ b/debian/patches/series
@@ -25,6 +25,7 @@ kfreebsd
menuselect_cflags
ilbc_disable
httpd_port
+rr_copy_array_too_small
AST-2012-012
AST-2012-013
--
2.1.3
signature.asc
Description: Digital signature
Bug#773032: squid3: prompting due to modified conffiles which were not modified by the user: /etc/squid3/squid.conf
Package: squid3 Version: 3.4.8-4 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed your package failed the piuparts upgrade test because dpkg detected a conffile as being modified and then prompted the user for an action. As there is no user input, this fails. But this is not the real problem, the real problem is that this prompt shows up in the first place, as there was nobody modifying this conffile at all, the package has just been installed and upgraded... This is a violation of policy 10.7.3, see https://www.debian.org/doc/debian-policy/ch-files.html#s10.7.3, which says [These scripts handling conffiles] must not ask unnecessary questions (particularly during upgrades), and must otherwise be good citizens. https://wiki.debian.org/DpkgConffileHandling should help with figuring out how to do this properly. In https://lists.debian.org/debian-devel/2009/08/msg00675.html and followups it has been agreed that these bugs are to be filed with severity serious. From the attached log (scroll to the bottom...): Setting up squid3-common (3.4.8-4) ... Setting up squid3 (3.4.8-4) ... Installing new version of config file /etc/init.d/squid3 ... Installing new version of config file /etc/logrotate.d/squid3 ... Installing new version of config file /etc/resolvconf/update-libc.d/squid3 ... Configuration file '/etc/squid3/squid.conf' == Modified (by you or by a script) since installation. == Package distributor has shipped an updated version. What would you like to do about it ? Your options are: Y or I : install the package maintainer's version N or O : keep your currently-installed version D : show the differences between the versions Z : start a shell to examine the situation The default action is to keep your current version. *** squid.conf (Y/I/N/O/D/Z) [default=N] ? dpkg: error processing package squid3 (--configure): EOF on stdin at conffile prompt Processing triggers for libc-bin (2.19-13) ... Errors were encountered while processing: squid3 cheers, Andreas squid3_3.4.8-4.log.gz Description: application/gzip
Bug#772867: [Pkg-haskell-maintainers] Bug#772867: hoogle: Trigger cycle causes dpkg to fail processing
Hi, Am Freitag, den 12.12.2014, 17:20 +0100 schrieb Guillem Jover: And, sorry I see you asked debian-dpkg about that issue, but no one replied, I'll try to get a look to check if that fix was correct. I believe it was a different issue, but of course it would still be useful if you can review that change. (I’ll do it, but the question is whether this needs to enter testing.) Yes, this would need to enter testing, this is particularly relevant on upgrade scenarios. Uploaded, and unblock request filed at #773031. Gruß, Joachim -- Joachim nomeata Breitner Debian Developer nome...@debian.org | ICQ# 74513189 | GPG-Keyid: F0FBF51F JID: nome...@joachim-breitner.de | http://people.debian.org/~nomeata signature.asc Description: This is a digitally signed message part
Bug#771614: python-mock: non-functional email address in Uploaders
Hello David On Mon, 1 Dec 2014 11:53:41 +1100 Ben Finney ben+deb...@benfinney.id.au wrote: The Uploaders field lists David Watson da...@kutoken.com. That email address is not functional as of 2014-11-30, resulting in permanent delivery failures. Please remove that identity from Uploaders, and optionally replace it with a working email address for that person. Which address would you like to use, now? Or would you prefer to be removed from uploaders? Best regards. -- Nirgal signature.asc Description: OpenPGP digital signature
Bug#725691: mc: erratic behaviour of mcedit as subprocess of mc -- bug still there
Dmitry, many thanks for looking into this issue. I wonder whether it has anything to do with framebuffer console If it helps: Yes, I do run mc on the intel 915 framebuffer console and, yes, I do see this bug on both console 1 and ttys 2-6. Could you please advise if you have gpm installed gpm: Installed: 1.20.4-6.1+b2 Candidate: 1.20.4-6.1+b2 Version table: *** 1.20.4-6.1+b2 0 990 http://ftp.de.debian.org/debian/ jessie/main i386 Packages 990 ftp://ftp.de.debian.org/debian/ testing/main i386 Packages 50 ftp://ftp.de.debian.org/debian/ unstable/main i386 Packages 100 /var/lib/dpkg/status 1.20.4-6 0 500 http://ftp.de.debian.org/debian/ wheezy/main i386 Packages and what is the value of $TERM ? This is from within mcedit (not started under mc and thus not showing strange behaviour) running on tty2 (console 2) by way of ALT-U and saying echo $TERM: linux On a fresh console just echo $TERM: same thing (linux). Starting mc, then calling mcedit (which are the circumstances showing the erratic behaviour), then doing ALT-U, echo $TERM, again show linux as result. Doing echo $TERM from the mc command prompt does not show _any_ setting for TERM, btw. Karsten -- GPG key ID E4071346 @ eu.pool.sks-keyservers.net E167 67FD A291 2BEA 73BD 4537 78B9 A9F9 E407 1346 -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#405053: still valid
tag 405053 +moreinfo thanks Wooo, an bug against kmail 3.5 - that is quite old :D Can you confirm that is still an issue with 4.14? Actually I can create folders within kmail without any problem. Regads, sandro -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#772953: Enable several Kconfigs to support OMAP5432 uEVM devboard
On Dec 13, 2014, at 20:21, Ian Campbell i...@debian.org wrote: Control: tags -1 +pending On Mon, 2014-12-01 at 02:12 +0800, Chen Baozi wrote: With the patch attached, the OMAP5432 uEVM can be supported by the current unstable kernel. Thanks, I've applied this to the debian-kernel svn tree for the next unstable upload. For future reference the debian/config stuff is supposed to be alphabetical by Kconfig path, so I've moved the things you added around. Thanks. At some point (e.g. after upload, when this bug gets closed) please could you update https://wiki.debian.org/DebianKernel/ARMMP with this new platform. Ok. After eyeballing the resulting .config diff I've also enabled the following on top of what you did: - CONFIG_PINCTRL_PALMAS - CONFIG_GPIO_PALMAS - CONFIG_RTC_DRV_PALMAS If you care about Debian Installer support then you should also check whether any of the newly added modules need to be added to the installer udebs (which you can mainly do via the module lists under debian/installer/armhf/modules/armhf-armmp/). I've added dwc3-omap to usb-modules already since that one seemed obvious. I’ll have a try next. Cheers, Baozi signature.asc Description: Message signed with OpenPGP using GPGMail
Bug#772771: grub2: [INTL:fr] French debconf templates translation update
Quoting Ian Campbell (i...@debian.org): As you had suggestions from other translators to slightly modify the templates. I just CCd you on my reply to those suggestions. If it is decided to go ahead and update the translations then I'll do as you asked. I think that at least the suggestions meant to make the concept of EFI removable clearer are worth it. So, if there are other changes in the same paragraphs, it seems OK to do them as well. signature.asc Description: Digital signature
Bug#773033: qemu-system-misc: fails to install, trying to overwrite other packages files: /usr/share/qemu/petalogix-ml605.dtb
Package: qemu-system-misc Version: 1:2.2+dfsg-2exp Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed your package failed to install because it tries to overwrite other packages files without declaring a Breaks+Replaces relation. See policy 7.6 at https://www.debian.org/doc/debian-policy/ch-relationships.html#s-replaces From the attached log (scroll to the bottom...): Selecting previously unselected package qemu-system-misc. Preparing to unpack .../qemu-system-misc_1%3a2.2+dfsg-2exp_amd64.deb ... Unpacking qemu-system-misc (1:2.2+dfsg-2exp) ... dpkg: error processing archive /var/cache/apt/archives/qemu-system-misc_1%3a2.2+dfsg-2exp_amd64.deb (--unpack): trying to overwrite '/usr/share/qemu/petalogix-ml605.dtb', which is also in package qemu-system-ppc 1:2.2+dfsg-2exp dpkg-deb: error: subprocess paste was killed by signal (Broken pipe) Errors were encountered while processing: /var/cache/apt/archives/qemu-system-misc_1%3a2.2+dfsg-2exp_amd64.deb cheers, Andreas qemu-system_1:2.2+dfsg-2exp.log.gz Description: application/gzip
Bug#773034: nmu: tulip_4.6.0dfsg-2
Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: binnmu nmu tulip_4.6.0dfsg-2 . ALL . -m Rebuild against new binutils. As ususally after a new binutils upload ... Andreas -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#772784: ENOENT crash error on any NPM command
Mensagem original Assunto:Bug#772784: ENOENT crash error on any NPM command Data: Sat, 13 Dec 2014 10:39:52 -0300 De: Aurélio A. Heckert aure...@colivre.coop.br Empresa:Colivre Para: Jérémy Lal kapo...@melix.org, pkg-javascript-de...@lists.alioth.debian.org Em 11-12-2014 13:03, Jérémy Lal escreveu: Le jeudi 11 décembre 2014 à 11:20 -0300, Aurélio A. Heckert a écrit : Is there a new mandatory attribute on package.json? nothing that i know. I use npm daily (already used so many times today) and it works all right here. Did you install anything using npm -g ? Some things like coffee and shelljs. What do you have in /usr/local/lib/node_modules/ ? $ ls /usr/local/lib/node_modules/ chai commander iconv mochasails temporary xml2js codo css-condensejitsu nopt shelljs tmpyapm coffee-script iced-coffee-script mktemp package socket.io uglify-js If you have something, put it away temporarily and check npm works again. Wow! That works! $ sudo mv /usr/local/lib/node_modules /usr/local/lib/node_modules_TMP $ npm help Usage: npm command where command is one of: add-user, adduser, apihelp, author, ... Trying to discover a package to blame, i create a empty /usr/local/lib/node_modules and copy back one by one, testing with npm help, the it crashes on *nopt*. $ npm help Error: ENOENT, open '/home/aurium/Projetos/rauzito-bot/null' $ sudo rm -r /usr/local/lib/node_modules/nopt $ npm help Usage: npm command where command is one of: add-user, adduser, apihelp, author, ... $ ls /usr/local/lib/node_modules coffee-script iced-coffee-script sailstemporary xml2js commander mocha shelljs uglify-js yapm Could an older /usr/local/lib/node_modules/nopt be in conflict with /usr/lib/nodejs/nopt.js intended to be used by npm? Also do you have old or obsolete debian packages installed (not the ones from jessie ?) No, i'm using testing since i use Debian (10+y). This machine was ever testing. Jérémy. -- *Aurélio A. Heckert (aka Aurium)* http://softwarelivre.org/aurium *COLIVRE — Coop. de Tecnologias Livres* http://colivre.coop.br *Inkscape* — Desenhe Livremente http://inkscapeBrasil.org
Bug#773035: molly-guard: please inform about filesystems to be checked after reboot
package: molly-guard severity: wishlist tags: gift Hi Josh, thanks for maintaining molly-guard! :-) It would be nice if molly-guard would inform whether there will be any filesystems checks being performed after reboots. It seems /etc/molly-guard/run.d/ would be an ideal place to place a small shell script: [14:41] h01ger | madduck: this is almost usefor for /etc/molly-guard/run.d/ already: df -t ext2 -t ext3 -t ext4|grep /|cut -d -f1|sort -u | while read i ; do echo $i ; tune2fs -l $i |egrep (ount count|Last checked|Check interval): ; echo ; done [14:42] h01ger | madduck: are you continueing on this or should i dump this into a bug now? [14:42] madduck i am not going to hack on this, but… [14:42] madduck fsck -A -t ext2,ext3,ext4 … [14:42] h01ger | maybe add a echo 'press enter' ; read [14:43] madduck I just have not found out how to ask fsck whether a check will run [14:43] madduck the script should exit 0 if there is a fsck to be expected, 1 otherwise, and -v should display the filesystems [14:44] madduck go ahead and dump this into a bug report, good idea Obviously the above one liner doesnt really implement this yet in the most useful way... I might continue finishing it the next time I'll wait for some unexpected fsck to finish :-) cheers, Holger signature.asc Description: This is a digitally signed message part.
Bug#751636: openssh-server: ssh sessions are not cleanly termined on shutdown/restart with systemd
On Fri, Oct 10, 2014 at 11:52:24AM +0200, Tom Hutter wrote: The solution provided under https://bugzilla.redhat.com/show_bug.cgi?id=626477 suggests to killall ssh sessions, when stopping sshd. I prefer to have at least one ssh session open to my server when restarting ssh, if something goes wrong. Agreed. This change would not be acceptable. Therefore I added a service, to solve this under the current Debian Wheezy version I am running. /etc/systemd/system/ssh-user-sessions.service: [Unit] Description=Shutdown all ssh sessions before network After=network.target [Service] TimeoutStartSec=0 Type=oneshot RemainAfterExit=yes ExecStart=/bin/true ExecStop=/usr/bin/killall sshd When starting, this service does simply nothing (/bin/true). But due to the statement After=network.target it kills all ssh processes before shutting down the network. I had always thought that systemd would group processes together in cgroups to be able to kill them more elegantly on shutdown. I'd like to see that feature used instead of resorting to the old sledgehammer method. Greetings Marc -- - Marc Haber | I don't trust Computers. They | Mailadresse im Header Leimen, Germany| lose things.Winona Ryder | Fon: *49 6224 1600402 Nordisch by Nature | How to make an American Quilt | Fax: *49 6224 1600420 -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#751636: openssh-server: ssh sessions are not cleanly termined on shutdown/restart with systemd
On Fri, Oct 10, 2014 at 05:44:14PM +0200, Christoph Anton Mitterer wrote: a) if sshd crashes or when it is restarted/reloaded (or when the network is restarted), we do not want ssh sessions to terminate, right? At least that's what we always had. I would like to have a method to kill all ssh sessions with the exception of my own ones, or the single session that I happen to type the command restarting sshd in. b) we want a way to actually stop user sessions... not only for this particular bug (i.e. on shutdown), but as a locally logged in sysadmin I'd also like to say okay... away with sshd and it's users. Agreed. We didn't have that until jessie though. AFAICS, this should solve (a) and (b), the only difference to now would be, that we need to educate our users/admins, that systemctl stop ssh really means all ssh stops and not just the main ssh daemon stops but old connections remain. That would be a pretty severe change from the behavior we used to have for fifteen years. I also guess it would be used as an argument against systemd as a whole. Please consider not changing this behavior to keep system acceptance up. Greetings Marc -- - Marc Haber | I don't trust Computers. They | Mailadresse im Header Leimen, Germany| lose things.Winona Ryder | Fon: *49 6224 1600402 Nordisch by Nature | How to make an American Quilt | Fax: *49 6224 1600420 -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#769108: tag +patch
Control: tag -1 + patch On Sat, Dec 13, 2014 at 01:09:18PM +, Debian Bug Tracking System wrote: Processing control commands: -1 + patch Unknown command or malformed arguments to command. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#721737: nis: segfault in yppasswd when using shadow
On Fri, 12 Dec 2014, Mark Brown wrote: On Fri, Dec 12, 2014 at 07:07:07AM -0500, Jon Daley wrote: On Fri, 12 Dec 2014, Goswin von Brederlow wrote: As I posted in the original report, there was a change to crypt() which now exposes a long standing bug in nis. OK, so this is new information. The original report said that perhaps this was better fixed in crypt() (which may well be the case) but didn't say anything about the behaviour of crypt() having ever been different, based on the report it looks like this is something that's always happened and has only just been noticed (which is entirely reasonable since the use of shadow passwords with NIS is pretty unusual). You are right that I didn't say that in the original report. The other reporter apparently has used NIS longer than I have, so can more confidently make that claim than I can. You've made a couple references to using shadow and nis being unusual. Do people usually turn off shadow passwords when using other systems? And you also implied that NIS's lack of security makes shadow passwords irrelevant. When I first installed NIS, I thought it might be exposing the password file somehow, but I couldn't make it do that, and I get permission denied errors when I try to see the actual password hashes from a client. Can you give me a command that does? It's not clear to me that this is something that has been newly introduced (as opposed to something people have always dealt with when using NIS, the version mentioned is the one in wheezy) - using shadow files with NIS is obviously a bit of a corner case given how meaningless NIS makes the extra security they add. If it's something that's just broken in this version and people would see regress on upgrades that's a bit different. Since shadow passwords are the default, the corner case affects every user of nis, unless they disable shadow. I assume disabling shadow would fix it. I suppose for people doing completely fresh NIS deployments rather than using something more current like LDAP... I've played with LDAP before, and I've never been able to get to work properly, and NIS seemed to be any easier route, but yes, this is a fresh (as of a couple years ago) install. Can you define malformed? I used reportbug to report the bug, and it looks fine to me. The most obvious thing is that your lines are *way* longer than 80 characters (appears to be something like 140 characters), looking at the patch itelf it's also in some weird format which looks like it's also trying to move the file. I see. I assume that is because reportbug uses pico or some sort of simple editor that doesn't know about email syntax. My email client wraps the lines, so I didn't notice that before. The patch probably was done manually or at least, not intended to be automatically merged, but since it is all of 15 characters, it doesn't seem like that should be a reason to dismiss it. After this conversation, I've thought maybe a better patch is to check the return value of crypt, rather than checking the length of the supposed hashed password. I don't know the code well enough to know which way is better, I can make arguments for either. In any case, I don't think an argument can be made that my patch breaks anything for anyone, and it makes the package usable for some, so it seems like we've been taking a lot of effort talking about it, rather than just fixing it. But, I have a /usr/local/bin/yppasswd, so it doesn't really matter to me. -- Jon Daley http://jon.limedaley.com ~~ A good listener is not only popular everywhere, but after a while he gets to know something. -- Wilson Mizner -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#773036: libetpan-dbg: unhandled symlink to directory conversion: /usr/share/doc/PACKAGE
Package: libetpan-dbg Version: 1.5-1 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, an upgrade test with piuparts revealed that your package installs files over existing symlinks and possibly overwrites files owned by other packages. This usually means an old version of the package shipped a symlink but that was later replaced by a real (and non-empty) directory. This kind of overwriting another package's files cannot be detected by dpkg. This was observed on the following upgrade paths: wheezy - sid (jessie has the same version as sid) For /usr/share/doc/PACKAGE this may not be problematic as long as both packages are installed, ship byte-for-byte identical files and are upgraded in lockstep. But once one of the involved packages gets removed, the other one will lose its documentation files, too, including the copyright file, which is a violation of Policy 12.5: https://www.debian.org/doc/debian-policy/ch-docs.html#s-copyrightfile For other overwritten locations anything interesting may happen. Note that dpkg intentionally does not replace directories with symlinks and vice versa, you need the maintainer scripts to do this. See in particular the end of point 4 in https://www.debian.org/doc/debian-policy/ch-maintainerscripts.html#s-unpackphase It is recommended to use the dpkg-maintscript-helper commands 'dir_to_symlink' and 'symlink_to_dir' (available since dpkg 1.17.2) to perform the conversion, ideally using d/$PACKAGE.mainstscript. See dpkg-maintscript-helper(1) and dh_installdeb(1) for details. From the attached log (usually somewhere in the middle...): 2m16.3s ERROR: FAIL: silently overwrites files via directory symlinks: /usr/share/doc/libetpan-dbg/changelog.Debian.gz (libetpan-dbg:amd64) != /usr/share/doc/libetpan15/changelog.Debian.gz (libetpan15) /usr/share/doc/libetpan-dbg/changelog.gz (libetpan-dbg:amd64) != /usr/share/doc/libetpan15/changelog.gz (libetpan15) /usr/share/doc/libetpan-dbg/copyright (libetpan-dbg:amd64) != /usr/share/doc/libetpan15/copyright (libetpan15) cheers, Andreas libetpan-dbg_1.5-1.log.gz Description: application/gzip
Bug#751636: openssh-server: ssh sessions are not cleanly termined on shutdown/restart with systemd
On Fri, Oct 10, 2014 at 06:51:20PM +0200, Tom Hutter wrote: If ssh is restarted, my hack does exactly the expected. The ssh user sessions stay alive. Only, if the network is shut down, the sessions will be terminated. Looking at this excerpt from systemd.special(7), I would say, my hack does exactly the expected. What is a session depending on network good, once the network has gone away? network.target This unit is supposed to indicate when network functionality is available, but it is only very weakly defined what that is supposed to mean, with one exception: at shutdown, a unit that is ordered after network.target will be stopped before the network -- to whatever level it might be set up then -- is shut down. Also see Running Services After the Network is up[1] for more information. Also see network-online.target described above. /lib/systemd/system/ssh.service in current sid has After=network.target in its Unit stanza and still not cleanly kills off ssh sessions. There is also /lib/systemd/system/ssh@.service which seems to be contrary to /lib/systemd/system/ssh.service which I do not understand. I think it's more a philosophical question, if running processes depending on the network should survive a network restart They usually did in the past, /etc/init.d/network stop; /etc/init.d/network start returned you to the shell and did not kill the session. Greetings Marc -- - Marc Haber | I don't trust Computers. They | Mailadresse im Header Leimen, Germany| lose things.Winona Ryder | Fon: *49 6224 1600402 Nordisch by Nature | How to make an American Quilt | Fax: *49 6224 1600420 -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#751636: openssh-server: ssh sessions are not cleanly termined on shutdown/restart with systemd
On Sat, Oct 11, 2014 at 06:33:39PM -0700, Russ Allbery wrote: Christoph Anton Mitterer cales...@scientia.net writes: But I mean before thinking about how to handle it technically,... it should probably decided what do we actually want. Like even if ssh itself (the binary) behaves different from apache/etc. - do we want to keep that in the unit-files or do we want stop to generally mean that everything from that service is stopped. I personally would tend to the later, though this may have many implications... Yes, a lot of people being *quite* upset when they stop ssh to restart it with debugging or to temporarily bring it down while working on something, discover that their session was terminated in a way that's never happened with ssh in the past, and now be unable to connect to the system since it was a remote server. Let's not do that. That would be really unpleasant. We need to preserve the current sshd behavior that stopping the service does *not* kill open sessions. Amen. Greetings Marc -- - Marc Haber | I don't trust Computers. They | Mailadresse im Header Leimen, Germany| lose things.Winona Ryder | Fon: *49 6224 1600402 Nordisch by Nature | How to make an American Quilt | Fax: *49 6224 1600420 -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#773037: RFS: qmapshack/0.8.2-1~exp1
Package: sponsorship-requests Severity: normal Dear mentors, I am looking for a sponsor for my package qmapshack Package name: qmapshack Version : 0.8.2-1~exp1 Upstream Author : Oliver Eichler oliver.eich...@gmx.de URL : https://bitbucket.org/maproom/qmapshack/wiki/Home License : GPL-3+ Section : science It builds those binary packages: qmapshack - GPS mapping (GeoTiff and vector) and GPSr management To access further information about this package, please visit the following URL: http://mentors.debian.net/package/qmapshack Alternatively, one can download the package with dget using this command: dget -x http://mentors.debian.net/debian/pool/main/q/qmapshack/qmapshack_0.8.2-1~exp1.dsc More information about QMapShack can be obtained from https://bitbucket.org/maproom/qmapshack/wiki/Home. Changes since the last upload: * New upstream release. * Add myself to Uploaders. * Update copyright file, changes: - Copyright years - public-domain license specification * Remove icons before regenerating in d/rules instead of d/clean. Regards, Bas Couwenberg -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#667965: #667965 - eatmydata: Does not properly handle fsync/fdatasync on invalid file handles
Control: reassign -1 libeatmydata1 On Fri, 15 Feb 2013 14:44:55 -0500 Phillip Susi ps...@ubuntu.com wrote: I think this is a bug in gnulib rather than eatmydata. fsync() can't be expected to report errors that may have happened when it doesn't actually try to do anything. In other words, doing nothing can not fail, and should not be expected to. I have emailed gnulib about fixing it on their end. And what did they reply? -- regards, Mattia Rizzolo GPG Key: 4096R/B9444540 http://goo.gl/I8TMB more about me: http://mapreri.org Launchpad User: https://launchpad.net/~mapreri Ubuntu Wiki page: https://wiki.ubuntu.com/MattiaRizzolo signature.asc Description: GooPG digital signature
Bug#751636: openssh-server: ssh sessions are not cleanly termined on shutdown/restart with systemd
On Sat, Oct 11, 2014 at 08:12:56PM -0700, Russ Allbery wrote: I have no problems with the current behavior under systemd, so I'm not the one to ask for a solution. It makes no difference at all to me whether I get a clean connection shutdown from a host when it's being rebooted. It makes a big difference to me when working with multiple hosts at once. I will only get back my shell after a manual action or after waiting for the host to return to the network to finally send an RST. That didn't reliably happen even under sysvinit-started sshd. It happened reliably in so many cases that I don't even remember the last time where a sysvinit system didn't return me cleanly and quickly to my shell on shutdown. It was a big WTF when my first systemd system behaved that way. If sysvinit were so unreliable in its behavior on shutdown, I would have been at least a bit familiar with the new behavior, and I do not like it at all. This change will not improve systemd's behavior, as it is one more place where the self-proclaimed drop-in replacement to sysvinit changes system behavior in a _very_ prominent way. If you can find a way to improve the behavior along some axis that you care about, I'm certainly fine with that, but given that I don't even consider the problem that you're trying to solve to be a problem, I'm going to have a low tolerance for regressions. :) jftr, I see the changed behavior as a problem. Greetings Marc -- - Marc Haber | I don't trust Computers. They | Mailadresse im Header Leimen, Germany| lose things.Winona Ryder | Fon: *49 6224 1600402 Nordisch by Nature | How to make an American Quilt | Fax: *49 6224 1600420 -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#751636: openssh-server: ssh sessions are not cleanly termined on shutdown/restart with systemd
On Sun, Oct 12, 2014 at 04:12:07AM +0200, Christoph Anton Mitterer wrote: On Sat, 2014-10-11 at 18:33 -0700, Russ Allbery wrote: Yes, a lot of people being *quite* upset when they stop ssh to restart it with debugging or to temporarily bring it down while working on something, discover that their session was terminated in a way that's never happened with ssh in the past, and now be unable to connect to the system since it was a remote server. Let's not do that. That would be really unpleasant. We need to preserve the current sshd behavior that stopping the service does *not* kill open sessions. Well never too late to change something *if* it was the cleaner way to handle it. =) That would be the systemd way to do it and instantly spawn a new hate wave. After all, it was systemd locking people out of their headless, remote systems during an urgent security update. Don't change this behavior. Please. Greetings Marc -- - Marc Haber | I don't trust Computers. They | Mailadresse im Header Leimen, Germany| lose things.Winona Ryder | Fon: *49 6224 1600402 Nordisch by Nature | How to make an American Quilt | Fax: *49 6224 1600420 -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#773038: Macro support broken
Package: gerris Version: 20131206+dfsg-5 Severity: normal Hello, Using macros with gerris does not work: ~ gerris3D -m simulation.gfs awk: fatal: can't open source file `/usr/share/gerris/m4.awk' for reading (No such file or directory) Indeed, when one looks at the /usr/share/gerris/m4.awk, one can see that it's a dangling symlink. ~ ls -l /usr/share/gerris/m4.awk lrwxrwxrwx 1 root root 10 Dec 3 08:05 /usr/share/gerris/m4.awk - lib/m4.awk (there is no lib/m4.awk file). Cheers, Vincent -- System Information: Debian Release: 8.0 APT prefers unstable APT policy: (500, 'unstable'), (500, 'stable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.14.0+p (SMP w/8 CPU cores) Locale: LANG=en_GB.utf8, LC_CTYPE=en_GB.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages gerris depends on: ii libav-tools 6:11-2 ii libc6 2.19-13 ii libgcc1 1:4.9.2-5 ii libgfortran3 4.9.2-5 ii libgfs-1.3-2 20131206+dfsg-5 ii libgfs-dev20131206+dfsg-5 ii libglib2.0-0 2.42.1-1 ii libgts-0.7-5 0.7.6+darcs121130-1.2 ii libgts-dev0.7.6+darcs121130-1.2 ii libquadmath0 4.9.2-5 Versions of packages gerris recommends: ii gfsview 20121130+dfsg-1 Versions of packages gerris suggests: ii python 2.7.8-2 -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#751636: openssh-server: ssh sessions are not cleanly termined on shutdown/restart with systemd
On Fri, Oct 10, 2014 at 10:51:04AM -0500, David Lechner wrote: I have found that using ssh.socket instead of ssh.service makes clients shut down cleanly most of the time (sometimes they will still hang, but it is rare). systemctl disable ssh.service systemctl enable ssh.socket Do I understand correctly, that ssh in jessie/sid allows the local admin to run sshd as a traditional daemon, with the new (undesired) behavior, or as a systemd service with socket activation, which gives a better emulation of traditional behavior? If this is really seriously meant that way, people will see this as a conspiracy to coax people into using socket activation. Danger, Will Robinson. Greetings Marc -- - Marc Haber | I don't trust Computers. They | Mailadresse im Header Leimen, Germany| lose things.Winona Ryder | Fon: *49 6224 1600402 Nordisch by Nature | How to make an American Quilt | Fax: *49 6224 1600420 -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#751636: Severity bump
On Thu, Nov 27, 2014 at 10:29:44AM -0800, Russ Allbery wrote: Luca Falavigna dktrkr...@debian.org writes: I believe this bug is quite important, and should deserve a fix in time for Jessie, hence the severity bump. Er, why? Have you read the discussion in the bug? I continue to believe that this is not even a bug at all, let alone an important one. jftr, I see this as an unnecessary behavioral change in a quite prominent place which will be seen as systemd's fault by a gazillion of people, including me. I do not like the new behavior at all, see this as a clear bug and find the important severity justified. Greetings Marc -- - Marc Haber | I don't trust Computers. They | Mailadresse im Header Leimen, Germany| lose things.Winona Ryder | Fon: *49 6224 1600402 Nordisch by Nature | How to make an American Quilt | Fax: *49 6224 1600420 -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#772114: zotero-standalone: zotero does not start anymore
Thank Mike. Could the submitter check which version(s) of xulrunner is(are) installed on the system. and eventually remove all but the latest. Cheers Mike On Tue Dec 09 2014 at 23:35:02 Mike Hommey m...@glandium.org wrote: On Fri, Dec 05, 2014 at 09:53:09AM +, Michele Cane wrote: Hi, If I am correct this is an issue with iceweasel. For some reason iceweasel version results as 10.0.12 instead of 31.3. I do not have access to a stable machine right now. I'll try to test it later tonight but I think I'll assign this bug to the iceweasel package. Where would that 10.0.12 version come from? I don't see it coming from iceweasel, there must be something fishy with how zotero starts up, and my guess is that the bug reporter has xulrunner 10.0.0.12 on their machine. Mike
Bug#773039: shaarli: Unusable after install due to incorrect folder permissions out of the box
Package: shaarli
Version: 0.0.42~beta~dfsg1-1
Severity: serious
Justification: Policy 10.7.3
After installing shaarli from Testing on a new machine, a 500 Internal Server
Error is logged when accessing the page for the first time.
From /var/log/nginx/error.log:
2014/12/13 14:39:27 [error] 10171#0: *29 FastCGI sent in stderr: PHP message:
PHP Fatal error: Uncaught exception 'RainTpl_Exception' with message 'Cache
directory /var/cache/shaarli/tmp/doesn't have write permission. Set write
permission or set RAINTPL_CHECK_TEMPLATE_UPDATE to false. More details on
http://www.raintpl.com/Documentation/Documentation-for-PHP-developers/Configuration/'
in /usr/share/raintpl/inc/rain.tpl.class.php:321
Stack trace:
#0 /usr/share/raintpl/inc/rain.tpl.class.php(274):
RainTPL-compileFile('install', NULL, 'tpl/install.htm...',
'/var/cache/shaa...', '/var/cache/shaa...')
#1 /usr/share/raintpl/inc/rain.tpl.class.php(164):
RainTPL-check_template('install')
#2 /usr/share/shaarli/index.php(674): RainTPL-draw('install')
#3 /usr/share/shaarli/index.php(2107): pageBuilder-renderPage('install')
#4 /usr/share/shaarli/index.php(108): install()
#5 {main}
thrown in /usr/share/raintpl/inc/rain.tpl.class.php on line 321 while
reading response header from upstream, client: 127.0.0.1, server: _, request:
GET / HTTP/1.1, upstream: fastcgi://unix:/var/run/php5-fpm.sock:, host:
127.0.0.1
The permission on the /var/cache/shaarli/tmp folder is incorrectly set (root
instead of www-data, which is the user under which the Apache and nginx web
servers run by default).
In fact, the following folders should also be writable by www-data:
/var/lib/shaarli/data
/var/cache/shaarli/cache
/var/cache/shaarli/pagecache
The following fixes this issue:
sudo chown www-data:www-data /var/lib/shaarli/data /var/cache/shaarli/cache
/var/cache/shaarli/pagecache /var/cache/shaarli/tmp
Justification for severity serious:
From the bug severity description [0]:
serious
is a severe violation of Debian policy (roughly, it violates a must or required
directive), or, in the package maintainer's or release manager's opinion, makes
the package unsuitable for release.
In my opinion, a package should (as much as possible, i.e. not must) work out
of the box. This is somewhat mentioned in section 10.7.3 of the Debian Policy
Manual [1]:
Ideally the sysadmin should not have to do any configuration other than that
done (semi-)automatically by the postinst script.
+Emilien
[0] https://www.debian.org/Bugs/Developer#severities
[1] https://www.debian.org/doc/debian-policy/ch-files.html#s10.7.3
-- System Information:
Debian Release: 8.0
APT prefers unstable
APT policy: (500, 'unstable'), (500, 'stable'), (1, 'experimental')
Architecture: i386 (i686)
Kernel: Linux 3.16.0-4-686-pae (SMP w/1 CPU core)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
Versions of packages shaarli depends on:
ii javascript-common 11
ii libjs-jquery 1.7.2+dfsg-3.2
ii libjs-jquery-lazyload 1.7.2-1
ii libjs-jquery-ui1.10.1+dfsg-1
ii php5 5.6.3+dfsg-1
ii php5-fpm 5.6.3+dfsg-1
ii php5-gd5.6.3+dfsg-1
ii raintpl2.7.2-1
Versions of packages shaarli recommends:
ii nginx-full [httpd] 1.6.2-5
shaarli 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#772914: [Pkg-samba-maint] Bug#772914: cifs-utils: CIFS timeouts when shutitng down system using WiFi network
On Fri, Dec 12, 2014 at 11:13:05PM +0100, Javier Barroso wrote: I think this bug can be, if you are using wpa_supplicant, related to https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=769186 I'm thinking on reassigning such bug to wpa_supplicant .. The bug reporter indicated they are running sysvinit though, so while it is probably a similar bug, I don't think it is exactly the same issue. Jelmer Regards, El 12/12/2014 21:24, Vincas Dargis vin...@gmail.com escribió: 2014.12.12 16:10, Jelmer Vernooij wrote: What init system are you using? This is a problem with the ordering during shutdown - cifs-utils is not involved with that. That should be Debian 7 default, sysvinit? -- To unsubscribe, send mail to 772914-unsubscr...@bugs.debian.org. -- Jelmer Vernooij jel...@debian.org Debian Developer https://jelmer.uk/ signature.asc Description: Digital signature
Bug#773040: unblock: anarchism/14.0-3 (pre-approval)
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: unblock
Hi,
this is a pre-approval unblock request for anarchism, mostly to have a non-
bouncing maintainer address in jessie. I've also done six tiny other useful
changes but didn't bump debian/compat ;-)
$ head -16 anarchism/debian/changelog
anarchism (14.0-3) unstable; urgency=medium
* Adopt anarchism (Closes: #772907) - co-maintainers very much welcome!
* Replace Mauro Lizaur as maintainer, thanks for all your work, Mauro!
* Add Vcs-Git: and Vcs-Browser: headers to debian/control.
* Correct upstream homepage URL in debian/control and README.Debian.
(Closes: #738767)
* Remove obsolete debian/README.source.
* Make Build-Depends on lynx unversioned, as it was referring to a version
satisfied in Squeeze.
* Bump Standards-Version to 3.9.6, no changes needed.
* Add debian/patches/686968-Remove-Adobe-advertisement.patch to do exactly
that. (Closes: #686968)
-- Holger Levsen hol...@debian.org Sat, 13 Dec 2014 13:12:42 +0100
$ debdiff anarchism_14.0-2.dsc anarchism_14.0-3.dsc|diffstat
dpkg-source: Warnung: unsigniertes Quellpaket wird extrahiert
(/home/holgi/Projects/anarchism/git/anarchism_14.0-3.dsc)
README.Debian |2 -
README.source |7
changelog | 16 ++
control | 10 --
patches/686968-Remove-Adobe-advertisement.patch | 35
patches/series |1
6 files changed, 59 insertions(+), 12 deletions(-)
See attached.
Thanks for your work on jessie!
cheers,
Holger
diff -Nru anarchism-14.0/debian/changelog anarchism-14.0/debian/changelog
--- anarchism-14.0/debian/changelog 2012-10-05 03:19:15.0 +0200
+++ anarchism-14.0/debian/changelog 2014-12-13 15:26:51.0 +0100
@@ -1,3 +1,19 @@
+anarchism (14.0-3) unstable; urgency=medium
+
+ * Adopt anarchism (Closes: #772907) - co-maintainers very much welcome!
+ * Replace Mauro Lizaur as maintainer, thanks for all your work, Mauro!
+ * Add Vcs-Git: and Vcs-Browser: headers to debian/control.
+ * Correct upstream homepage URL in debian/control and README.Debian.
+(Closes: #738767)
+ * Remove obsolete debian/README.source.
+ * Make Build-Depends on lynx unversioned, as it was referring to a version
+satisfied in Squeeze.
+ * Bump Standards-Version to 3.9.6, no changes needed.
+ * Add debian/patches/686968-Remove-Adobe-advertisement.patch to do exactly
+that. (Closes: #686968)
+
+ -- Holger Levsen hol...@debian.org Sat, 13 Dec 2014 13:12:42 +0100
+
anarchism (14.0-2) unstable; urgency=low
* Fixed the name in References section for each txt.
diff -Nru anarchism-14.0/debian/control anarchism-14.0/debian/control
--- anarchism-14.0/debian/control 2012-10-08 22:50:37.0 +0200
+++ anarchism-14.0/debian/control 2014-12-13 15:26:39.0 +0100
@@ -1,11 +1,13 @@
Source: anarchism
Section: doc
Priority: optional
-Maintainer: Mauro Lizaur ma...@debian.org
+Maintainer: Holger Levsen hol...@debian.org
Build-Depends: debhelper (= 8.0.0)
-Build-Depends-Indep: lynx (= 2.8.8dev.5), sed (= 4.2.1)
-Standards-Version: 3.9.3
-Homepage: http://www.infoshop.org/page/AnAnarchistFAQ
+Build-Depends-Indep: lynx, sed (= 4.2.1)
+Standards-Version: 3.9.6
+Homepage: http://www.infoshop.org/AnAnarchistFAQ
+Vcs-Git: git://anonscm.debian.org/collab-maint/anarchism.git
+Vcs-Browser: https://anonscm.debian.org/gitweb/?p=collab-maint/anarchism.git
Package: anarchism
Depends: ${misc:Depends}
diff -Nru anarchism-14.0/debian/patches/686968-Remove-Adobe-advertisement.patch anarchism-14.0/debian/patches/686968-Remove-Adobe-advertisement.patch
--- anarchism-14.0/debian/patches/686968-Remove-Adobe-advertisement.patch 1970-01-01 01:00:00.0 +0100
+++ anarchism-14.0/debian/patches/686968-Remove-Adobe-advertisement.patch 2014-12-13 15:26:51.0 +0100
@@ -0,0 +1,35 @@
+From 6028662874e6166927565bde7ad3343a1d303ed8 Mon Sep 17 00:00:00 2001
+From: Holger Levsen hol...@layer-acht.org
+Date: Sat, 13 Dec 2014 13:51:42 +0100
+Subject: [PATCH] Remove Adobe advertisement. (Closes: #686968)
+
+---
+ html/pdf.html | 14 +-
+ 1 file changed, 1 insertion(+), 13 deletions(-)
+
+diff --git a/html/pdf.html b/html/pdf.html
+index bc25b9a..402cdee 100644
+--- a/html/pdf.html
b/html/pdf.html
+@@ -8,18 +8,6 @@
+
+ h1An Anarchist FAQ in pdf format/h1
+
+-p
+-To view and print out the file you will need to have
+-Adobe Document Reader on your computer. This is free
+-software that now comes on many computers and with
+-many CD's. If you do not already have it you can
+-a href=http://www.adobe.com/products/acrobat/readstep.html;
+-download it from the Adobe site./a
+-[or
+-a href=http://www.adobe.com/products/acrobat/alternate.html;
+-click here for a faster text only
Bug#651067: Please add an eatmydata_exports() function to /usr/share/libeatmydata/eatmydata.sh
On Mon, 05 Dec 2011 15:12:05 +0100 Enrico Zini enr...@debian.org wrote:
I would like my test scripts to run under eatymdata when it is available
in the system. To do so, I would need to create a wrapper launcher for
my test scripts like so:
if [ -x /usr/bin/eatmydata ]
then
eatmydata run-tests $@
else
run-tests $@
fi
However, it would be even better if I could edit the run-tests script to
do the required export, adding something like this to it:
libeatmydata=/usr/lib/libeatmydata/libeatmydata.so
if [ -e $libeatmydata ]
then
if [ -n $LD_PRELOAD ]; then
export LD_PRELOAD=$libeatmydata $LD_PRELOAD
else
export LD_PRELOAD=$libeatmydata
fi
fi
This code is however already present in
/usr/share/libeatmydata/eatmydata.sh: if it could be moved from
eatmydata_exec into a separate function, then I could just do this:
if [ -e /usr/share/libeatmydata/eatmydata.sh ]
then
. /usr/share/libeatmydata/eatmydata.sh
eatmydata_exports
fi
And not worry about future changes in the way the eatmydata environment
is set up, except the hardcoded /usr/share path.
I wouldn't do so:
1) Please do not hardcode the library path (as you write). actually it changed
recently (due to multi arch)
2) Please do not hardcode script patch. Actually
/usr/share/libeatmydata/eatmydata.sh is gone...
3) The presence of the library itself is not bound to the presence of the
/usr/bin/eatmydata file (now that the library is in a different package than
the script)
I suggest you to just copy and paste this bit of the current script, plus a
check to be sure the library is installed:
if $(/sbin/ldconfig -p | grep -q libeatmydata) ; then
export
LD_LIBRARY_PATH=${LD_LIBRARY_PATH:+$LD_LIBRARY_PATH:}/usr/lib/libeatmydata
export LD_PRELOAD=${LD_PRELOAD:+$LD_PRELOAD }libeatmydata.so
fi
(the LD_LIBRARY_PATH is there only to support some use cases where you run a
chroot under eatmydata where the the actual path of the library differ between
the host and the guest, drop it if your script does not need it)
Even better would be an
eatmydata --exports function, but I'm afraid that would mean
introducing some radical changes in the command line parsing code.
indeed, and I don't like it.
Tell me what you think. I'd wontfix+close this bug report, given that imho there
is a better way to do what you want (and shorter, 3 rows instead of 5 in you
example).
--
regards,
Mattia Rizzolo
GPG Key: 4096R/B9444540 http://goo.gl/I8TMB
more about me: http://mapreri.org
Launchpad User: https://launchpad.net/~mapreri
Ubuntu Wiki page: https://wiki.ubuntu.com/MattiaRizzolo
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#772891: cabextract: hangs on a crafted CAB file
Control: clone -1 -2
Control: reassign -2 libmspack0 0.4-1
Control: retitle -2 libmspack: hangs on a crafted CAB file
On 2014-12-12 00:47:21, Jakub Wilk wrote:
Package: cabextract
Version: 1.4-4+b1
Severity: minor
Usertags: afl
The attached file makes cabextract hang forever (or at least for two
minutes, after which I lost my patience :-P).
This bug was found using American fuzzy lop:
http://lcamtuf.coredump.cx/afl/
This issue also affects libmspack. I noticed this while clamav was
scanning Jakub's mail for malware and it was stuck in an infinite loop.
The issue is easy to reproduce with the crafted file and the following
example code:
#include stdio.h
#include unistd.h
#include mspack.h
int main()
{
struct mscab_decompressor *cabd;
struct mscabd_cabinet *cab;
struct mscabd_file *file;
int test;
MSPACK_SYS_SELFTEST(test);
if (test != MSPACK_ERR_OK) exit(0);
if ((cabd = mspack_create_cab_decompressor(NULL))) {
if ((cab = cabd-open(cabd, hang.cab))) {
for (file = cab-files; file; file = file-next) {
printf(%s\n, file-filename);
cabd-extract(cabd, file, file-filename);
}
cabd-close(cabd, cab);
}
mspack_destroy_cab_decompressor(cabd);
}
return 0;
}
(From https://github.com/cooljeanius/libmspack/blob/master/README with a
call to extract added.)
Cheers
--
Sebastian Ramacher
signature.asc
Description: Digital signature
Bug#771749: cyrus-{common, imapd}-2.4: unhandled symlink to directory conversion: /usr/share/doc/PACKAGE
On 2014-12-02 17:59, Ondřej Surý wrote: Please test -11 when it hits the archive/incoming/... I did some tests with -12 and did not find any more problems. Many thanks for getting this cleaned up! I once did upgrade tests from all nvidia-graphics-drivers versions found in snapshot.d.o - to test cleaning up the mess of diversions created by them. But I really hope I never need to do this again. In the end this was the beginning of my involvement in piuparts. :-) Andreas -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
