Bug#775316: Use of grub2 bootloader broken
Package: live-build
Version: 5.0~a2-1
Tags: patch
Using a live cdrom image built with the grub2 bootloader results in an
error upon booting the disk, with grub complaining that it can't find a
file. The problem is that the grub2 script is copying all grub files
into /boot/grub when most of the grub2 bootloader files should be in
/boot/grub/i386-pc which is where it is looking and failing to find the
file, as per the error message seen.
Patch attached.
commit 372e09553489ad52083df002884a7dd8acbd08b2
Author: jnqnfe jnq...@gmail.com
Date: Tue Jan 13 20:32:27 2015 +
Fix grub2 bootloading (files copied to wrong directory)
diff --git a/scripts/build/binary_grub2 b/scripts/build/binary_grub2
index 61e8169..90a35d9 100755
--- a/scripts/build/binary_grub2
+++ b/scripts/build/binary_grub2
@@ -212,7 +212,7 @@ then
fi
# Copying templates
-mkdir -p binary/boot/grub
+mkdir -p binary/boot/grub/i386-pc
cp -r ${TEMPLATES}/* binary/boot/grub
case ${LIVE_IMAGE_TYPE} in
@@ -231,7 +231,7 @@ then
fi
# Copying grub
-cp ${FILES} binary/boot/grub
+cp ${FILES} binary/boot/grub/i386-pc
sed -i -e s|LINUX_LIVE|${LINUX_LIVE}| -e s|LINUX_INSTALL|${LINUX_INSTALL}|
-e s|MEMTEST|${MEMTEST}| binary/boot/grub/grub.cfg
sed -i -e s#LB_BOOTAPPEND_INSTALL#${LB_BOOTAPPEND_INSTALL}# -e
s#LB_BOOTAPPEND_LIVE#${LB_BOOTAPPEND_LIVE}# binary/boot/grub/grub.cfg
diff --git a/scripts/build/binary_iso b/scripts/build/binary_iso
index 9e41686..33c8e1f 100755
--- a/scripts/build/binary_iso
+++ b/scripts/build/binary_iso
@@ -172,7 +172,7 @@ for file in \${input_dir}/*.mod \${input_dir}/efiemu??.o \
do
if test -f \$file
then
- cp -f \$file binary/boot/grub
+ cp -f \$file binary/boot/grub/i386-pc
fi
done
EOF
Bug#775318: debian-policy: Using /srv instead of /var/lib for served user-level data
Afif Elghraoui afif.elghra...@openmailbox.org writes: Thanks for the clarification-- I mistakenly thought this meant that the distribution could define its own directory structure there. Yeah, I totally understand how you could get that impression. Unfortunately, the FHS isn't horribly clear on who the actors are at various points. One thing that I was going to add and then forgot to is that, in most cases, software really should make its data locations configurable. I would say that any package in Debian that doesn't allow you to configure where it puts its data, at least if that data is at all large (not just PID files and similar sorts of tiny stuff where the overhead of relocating it isn't worth it), probably has a bug. It may just be a wishlist bug, and it may be an upstream bug, but it might still be worth filing it. Particularly if the data is at all large, being able to relocate it is important and is something that we should support. For example, in Amazon EC2 instances, the root file system is often quite small and can't be made larger, but more disk space can be mounted elsewhere, so it's important to be able to move data to other paths. -- Russ Allbery (r...@debian.org) http://www.eyrie.org/~eagle/ -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#775084: devscripts: [rmadison] No/wrong support for -b TYPE
Control: clone -1 -2 -3 Control: reassign -2 qa.debian.org Control: user qa.debian@packages.debian.org Control: usertags -2 udd Control: retitle -2 [udd] Missing Package-Type info in packages table Control: severity -2 normal Control: reassign -3 qa.debian.org Control: retitle -3 [madison] b (binary-type) parameter isn't honored Control: severity -3 normal Control: block -3 by -2 On Sat, Jan 10, 2015 at 11:10:10PM -0500, James McCoy wrote: On Sun, Jan 11, 2015 at 03:19:00AM +0100, Cyril Brulebois wrote: rmadison is supposed to be a remote madison aka. dak ls, but here's another example of incorrect output: | kibi@franck:~$ dak ls -b deb -s testing bash | bash | 4.3-11+b1 | testing| amd64, arm64, armel, armhf, i386, kfreebsd-amd64, kfreebsd-i386, mips, mipsel, powerpc, ppc64el, s390x but the source is included nonetheless: | kibi@arya:~$ \rmadison -b deb -s testing bash | bash | 4.3-11| jessie | source | bash | 4.3-11+b1 | jessie | amd64, arm64, armel, armhf, i386, kfreebsd-amd64, kfreebsd-i386, mips, mipsel, powerpc, ppc64el, s390x man rmadison and a quick glance at the script suggest that support is supposed to be there, so it might just be some bug on the UDD side; Indeed, it is. UDD doesn't gather the Package-Type information. Before madison.cgi can be fixed, UDD needs to know the Package-Type info. Then madison.cgi can be updated to make the right query. Cloning this into two bugs to address that. Although devscripts' rmadison won't be using madison.cgi by default anymore, proper support for the various madison parameters would be useful for those that are using the service. Cheers, -- James GPG Key: 4096R/331BA3DB 2011-12-05 James McCoy james...@debian.org signature.asc Description: Digital signature
Bug#773861: Signify - OpenBSD's cryptographic signing tool
On 14/01/15 12:46, Paul Wise wrote: On Sat, Jan 10, 2015 at 1:31 PM, Riley Baird wrote: Typos in upstream code: equivilent - equivalent ouput - output Do these really have to be fixed? They won't be visible to the user, and it's likely to annoy upstream more than anything. I'll do it if I have to, though. If upstream are so hostile as to be annoyed by fixes for typos, I would personally question if their software is worth packaging at all. https://www.debian.org/doc/manuals/developers-reference/developer-duties.html#upstream-coordination Okay, I've sent a correction to the maintainer of the portable version: https://github.com/aperezdc/signify/pull/4 It wasn't that I didn't think that they would accept it, it was just that I had sent them three similar pull requests already. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#775318: debian-policy: Using /srv instead of /var/lib for served user-level data
Package: debian-policy Severity: wishlist Dear Maintainer, I wanted to separate user-level data (for special RAID, backups, encryption and such) from system data on my machine, so I targeted /home and /srv. I found out that data managed by system services are being stored in /var/lib/packagename when I expected them to be in /srv and this doesn't really make sense to me. I also wanted to limit the size of the /var partition to around 4GB, but I can't practically do this when, for example, ownCloud is managing user's data in /var/lib/owncloud. Users would then see a file storage limit of whatever space there was left in /var. Dokuwiki, mediawiki, and I believe gitweb are other examples. I don't think this is just a personal preference on my part, since the FHS doesn't seem to describe this kind of use for /var while /srv makes more sense /var/lib -- http://www.pathname.com/fhs/pub/fhs-2.3.html#VARLIBVARIABLESTATEINFORMATION /srv -- http://www.pathname.com/fhs/pub/fhs-2.3.html#SRVDATAFORSERVICESPROVIDEDBYSYSTEM I wanted to suggest a change to the policy that user-level data managed by system-services should be stored in /srv (instead of /var/ or something in /usr/share/). I'd be grateful for your consideration of this proposal. Thanks and regards, Afif -- System Information: Debian Release: 7.8 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-amd64 (SMP w/2 CPU cores) Locale: LANG=ar_SA.UTF-8, LC_CTYPE=ar_SA.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#775319: pulseaudio: unable to use headphones or other line out ports for audio. only speakers
Package: pulseaudio Version: 5.0-13 Severity: normal Hi, I just got a new hp hyprid tablet/laptop which i have installed amd64 jessie from the most recent RC images: user@lachp:~$ uname -a Linux lachp 3.16.0-4-amd64 #1 SMP Debian 3.16.7-ckt2-1 (2014-12-08) x86_64 GNU/Linux root@lachp:/home/user# dmidecode -t 1 # dmidecode 2.12 # SMBIOS entry point at 0x8b32e218 SMBIOS 2.7 present. Handle 0x0001, DMI type 1, 27 bytes System Information Manufacturer: Hewlett-Packard Product Name: HP Pro x2 612 G1 Tablet Version: A3008ED10B03 Wake-up Type: Power Switch SKU Number: G8W34AV Family: 103C_5336AN G=N L=BUS B=HP S=ELI This device has a haswell chipset and the following cards listed. user@lachp:~$ cat /proc/asound/card0/codec* | grep Codec Codec: Realtek ALC3228 user@lachp:~$ cat /proc/asound/card1/codec* | grep Codec Codec: Intel Haswell HDMI When i plug in headphones in any port they are detected by gnome but do not output any audio. There is activity in the mixers but no actual output to the speakers. I haven't been abble to find any information regarding this ALC3228 device which i'm assuming is specific to the haswell chipset. I have tried all the regular fixes like blacklisting changing the order of the cards for alsa. (the default order i got was hdmi, realtek) but i can't find any solution. -- Package-specific info: File '/etc/default/pulseaudio' does not exist -- System Information: Debian Release: 8.0 APT prefers testing-updates APT policy: (500, 'testing-updates'), (500, 'testing') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.16.0-4-amd64 (SMP w/4 CPU cores) Locale: LANG=en_AU.utf8, LC_CTYPE=en_AU.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages pulseaudio depends on: ii adduser 3.113+nmu3 ii libasound21.0.28-1 ii libasound2-plugins1.0.28-1+b1 ii libc6 2.19-13 ii libcap2 1:2.24-6 ii libdbus-1-3 1.8.12-3 ii libfftw3-single3 3.3.4-2 ii libgcc1 1:4.9.1-19 ii libice6 2:1.0.9-1+b1 ii libltdl7 2.4.2-1.11 ii liborc-0.4-0 1:0.4.22-1 ii libpulse0 5.0-13 ii libsamplerate00.1.8-8 ii libsm62:1.2.2-1+b1 ii libsndfile1 1.0.25-9+b1 ii libspeexdsp1 1.2~rc1.2-1 ii libstdc++64.9.1-19 ii libsystemd0 215-8 ii libtdb1 1.3.1-1 ii libudev1 215-8 ii libwebrtc-audio-processing-0 0.1-3 ii libx11-6 2:1.6.2-3 ii libx11-xcb1 2:1.6.2-3 ii libxcb1 1.10-3+b1 ii libxtst6 2:1.2.2-1+b1 ii lsb-base 4.1+Debian13+nmu1 ii pulseaudio-utils 5.0-13 ii udev 215-8 Versions of packages pulseaudio recommends: ii pulseaudio-module-x11 5.0-13 ii rtkit 0.11-2 Versions of packages pulseaudio suggests: ii paman0.9.4-1 ii paprefs 0.9.10-1 ii pavucontrol 2.0-3 ii pavumeter0.9.3-4 -- no debconf information # This file is part of PulseAudio. # # PulseAudio is free software; you can redistribute it and/or modify # it under the terms of the GNU Lesser General Public License as published by # the Free Software Foundation; either version 2 of the License, or # (at your option) any later version. # # PulseAudio is distributed in the hope that it will be useful, but # WITHOUT ANY WARRANTY; without even the implied warranty of # MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU # General Public License for more details. # # You should have received a copy of the GNU Lesser General Public License # along with PulseAudio; if not, write to the Free Software # Foundation, Inc., 59 Temple Place, Suite 330, Boston, MA 02111-1307 # USA. ## Configuration file for PulseAudio clients. See pulse-client.conf(5) for ## more information. Default values are commented out. Use either ; or # for ## commenting. ; default-sink = ; default-source = ; default-server = ; default-dbus-server = ; autospawn = yes ; daemon-binary = /usr/bin/pulseaudio ; extra-arguments = --log-target=syslog ; cookie-file = ; enable-shm = yes ; shm-size-bytes = 0 # setting this 0 will use the system-default, usually 64 MiB ; auto-connect-localhost = no ; auto-connect-display = no # This file is part of PulseAudio. # # PulseAudio is free software; you can redistribute it and/or modify # it under the terms of the GNU Lesser General Public License as published by # the Free Software Foundation; either version 2 of the License, or # (at your option) any later version. # # PulseAudio is distributed in the hope that it will be useful,
Bug#775322: Bootloader code issues and improvements
Package: live-build Version: 5.0~a2-1 Reviewing the bootloader menu creation code, I have drawn up the following list of fixes and improvements needed. Some of these I have already reported and supplied patches for separately, but I'm listing them here again to provide a comprehensive set of issues. Where applicable, I'll specify the bug number of the separate bug report either specifically for the issue, or where a patch has been previously supplied already as part of addressing something else. I intend to wrap this bug report up with one or more sets of commits to address them all. Broken boot capability issues: --- #1) grub2 broken, with missing file error on boot due to files being placed in the wrong directory (#775316). Kernel parameter issues: --- #2) [install entries] user supplied kernel params added in wrong position in grub/grub2 (#775143). #3) [install entries] 'quiet' (d-i?) param excluded from rescue entries instead of expert entries in grub2 (#775143). #4) [install entries] the '--' delimiter prior to the (d-i?) quiet kernel parameter is not output for grub/grub2 (#775143). #5) [install entries] the '--' delimiter needs to be replaced now with '---' (#775128). #6) [live entries] user supplied kernel params added in wrong position in grub/grub2 (less important than for installer entries) (#775143). #7) [live entries] normal user supplied params being added to fail-safe entry instead of fail-safe user params in grub/grub2. #8) [live entries] unnecessary replacement of fail-safe-installer user params placeholder in syslinux #9) depreciated video/graphics kernel parameters are being used. Menu entry set issues: --- #10) [install entries] speech synthesis option missing, affecting accessibility #11) [install entries] lots of install options not provided by syslinux menus #12) [live entries] too many entries added in grub/grub2 (redundant entries with kernel version specified) #13) memtest entry included in syslinux menus even if no memtest included #14) install entries included in syslinux menus even if no installer included Other issues: --- #15) [live entries] undocumented user failsafe params option #16) grub2 splash not being displayed #17) grub splash displayed, but horribly (can this be fixed?) #18) grub/grub2 do not rename kernel files unlike syslinux. syslinux does this for a technical reason, but it might be desirable to do across the board anyway. This needs further consideration. #19) consider switching grub/grub2 code to work more like syslinux, with pre-constructed pieces of the menus in files, from which the full menu can be constructed by including chunks from those files, and replacing placeholders. Also to be considered, particularly in respect to #18 and #19 are bug #757697 (support arch autodetection) and the best way to allow derivatives (e.g. Kali) to replace menu components such as labels and splash. As of this moment I have written patches for 11 of these issues, some of which have already been posted separately. More to follow soon. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#769941: iceweasel crash
control: tag -1 unreproducible, moreinfo On Mon, Jan 12, 2015 at 3:22 AM, webmbackslash wrote: I've found that all my problems with iceweasel and chrome crash was due to a Ram module fault. I was thinking about glib and others stuff, but all was solved after removing the module that fail the memtest :) Thanks all folks This turned out to be faulty ram for the other person experiencing this. Submitter, can you see if memtest says anything meaningful, and possibly reseating, removing, or replacing ram? Best wishes, Mike -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#774791: xine-ui: Creates dpkg trigger cycle via libxine2-ffmpeg, libxine2-misc-plugins or libxine2-x
control: tag -1 patch On Wed, Jan 7, 2015 at 12:30 PM, Niels Thykier wrote: The libxine2-ffmpeg, libxine2-misc-plugins and libxine2-x packages have a trigger cycle via the xine-ui package. This was detected by a script on jenkins.debian.net[1]. Hi, I reviewed xine's trigger usage, and it looks correct to me to use interest-noawait since the trigger is used just for updating xine's .desktop file. Best wishes, Mike diff -Nru xine-ui-0.99.9/debian/changelog xine-ui-0.99.9/debian/changelog --- xine-ui-0.99.9/debian/changelog 2014-10-06 11:12:05.0 + +++ xine-ui-0.99.9/debian/changelog 2015-01-14 04:08:07.0 + @@ -1,3 +1,10 @@ +xine-ui (0.99.9-1.2) unstable; urgency=medium + + * Non-maintainer upload. + * Use interest-noawait trigger (closes: #774791). + + -- Michael Gilbert mgilb...@debian.org Wed, 14 Jan 2015 04:07:45 + + xine-ui (0.99.9-1.1) unstable; urgency=medium * Non-maintainer upload diff -Nru xine-ui-0.99.9/debian/xine-ui.triggers xine-ui-0.99.9/debian/xine-ui.triggers --- xine-ui-0.99.9/debian/xine-ui.triggers 2014-10-06 11:12:05.0 + +++ xine-ui-0.99.9/debian/xine-ui.triggers 2015-01-14 04:09:32.0 + @@ -1 +1 @@ -interest /usr/lib/xine/plugins +interest-noawait /usr/lib/xine/plugins
Bug#770008: calendar-google-provider: Can no longer connect to Google calendars
On Sat, Nov 22, 2014 at 10:36 AM, Christian Kastner wrote: For the sake of completeness, here is the note from the addon page: | NOTE FOR 0.31 AND 0.25 USERS | After a previous announcement, Google has shut down the v1 API today | (November 17th) that version 0.32 and 0.25 has been using. This means | those versions will no longer work and you MUST upgrade to 1.0.x to | continue using the Provider for Google Calendar. Here is a possibly unusual suggestion. What about shipping an empty package, with just a README, for now? A future ESR icedove version supporting the new API will eventually be shipped in -security, so trying to come up with a solution in time for the initial jessie release is possibly not entirely needed. Best wishes, Mike -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#775306: pxz: race condition in setting permissions on output file
control: severity -1 important Hi Alexander, On Dienstag, 13. Januar 2015, Alexander Cherepanov wrote: pxz sets the mode of an output file to be the same as the one of an input file but does it only after compression is over. This leaves the output file with the wrong mode during all the time of the compression process. thanks for the bug report! Could you maybe come up with a patch? cheers, Holger signature.asc Description: This is a digitally signed message part.
Bug#775321: x32 port
On Wed, Jan 14, 2015 at 04:51:39AM +0100, Adam Borowski wrote: Package: iceweasel Version: 34.0-1 Severity: wishlist Tags: patch User: debian-...@lists.debian.org Usertags: port-x32 ftbfs-x32 Hi! Here's a set of patches to port iceweasel to the x32 architecture. They _almost_ work -- the build fails trying to access non-existant '/tmp/tmpjUZb3o.zip' during final install stage, log at: http://angband.pl/tmp/iceweasel_34.0-1+x32_x32-20150114-0216.build That means the xpcshell is broken in some way, which means iceweasel is likely to be broken as well. Or that you can't run x32 binaries on your build host. Mike -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#773861: Signify - OpenBSD's cryptographic signing tool
On 13/01/15 21:40, Henrique de Moraes Holschuh wrote: On Tue, 13 Jan 2015, Riley Baird wrote: On 12/01/15 12:37, Brian White wrote: I don't maintain Signify it any longer (or even use it) so feel free to do with it whatever you like. Hmm... does that mean that I need to adopt signify before signify-openbsd will be accepted? Well, you cannot take over its package name without a transition that will take at least one stable-release, either (so, it is a long-term thing). Otherwise, you will regress the systems that have the old package installed (and want it). We went through one such package-name-swap recently, involving the old git package becoming gnuit, and the old git-core package becoming git. You can ask the people involved for the details. While signify's popcon is low, it is still non-zero and the kind of thing that is going to be hooked inside a crontab or login script. So, a transition of some sort is required to avoid breaking things for its users. And if the transition also involves renaming /usr/bin/signify, not just the package's name, it also needs to be handled with care. Okay, thanks for pointing this out. A name change seems like it is going to be a lot more problematic than it is worth. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#775321: x32 port
Package: iceweasel Version: 34.0-1 Severity: wishlist Tags: patch User: debian-...@lists.debian.org Usertags: port-x32 ftbfs-x32 Hi! Here's a set of patches to port iceweasel to the x32 architecture. They _almost_ work -- the build fails trying to access non-existant '/tmp/tmpjUZb3o.zip' during final install stage, log at: http://angband.pl/tmp/iceweasel_34.0-1+x32_x32-20150114-0216.build but as 35.0 has been released today, I think it's better to submit what I got. The failure might be even unrelated to the port... The patches can be concatenated into one, I'm submitting them split into tiny bits. The order is irrelevant. Description: Get rid of sysctl includes The sysctl syscall has been strongly deprecated on Linux for ages and is not present at all on new architectures. We don't use it anymore, but one #include was left. This patch gets rid of it on platforms that don't use sysctl (ie, any but BSD). This unbreaks x32 and possibly others. Author: Adam Borowski kilob...@angband.pl --- iceweasel-34.0.orig/memory/mozjemalloc/jemalloc.c +++ iceweasel-34.0/memory/mozjemalloc/jemalloc.c @@ -325,7 +325,7 @@ __FBSDID($FreeBSD: head/lib/libc/stdlib #endif #include sys/time.h #include sys/types.h -#if !defined(MOZ_MEMORY_SOLARIS) !defined(MOZ_MEMORY_ANDROID) +#if defined(MOZ_MEMORY_BSD) #include sys/sysctl.h #endif #include sys/uio.h --- iceweasel-34.0.orig/media/mtransport/third_party/nICEr/src/stun/addrs.c +++ iceweasel-34.0/media/mtransport/third_party/nICEr/src/stun/addrs.c @@ -45,7 +45,9 @@ #include sys/param.h #include sys/socket.h #ifndef ANDROID +#if defined(BSD) || defined(DARWIN) #include sys/sysctl.h +#endif #include sys/syslog.h #else #include syslog.h Description: Trust __LP64__ on GNUC. Use __LP64__ to detect 64 bit systems, rather than trying to infer that from processor type. This broke __x86_64__ in 32-bit mode (aka x32). Author: Adam Borowski kilob...@angband.pl --- iceweasel-34.0.orig/js/src/jstypes.h +++ iceweasel-34.0/js/src/jstypes.h @@ -141,8 +141,7 @@ # endif #elif defined(__GNUC__) /* Additional GCC defines are when running on Solaris, AIX, and HPUX */ -# if defined(__x86_64__) || defined(__sparcv9) || \ -defined(__64BIT__) || defined(__LP64__) +# if defined(__sparcv9) || defined(__64BIT__) || defined(__LP64__) # define JS_64BIT # endif #elif defined(__SUNPRO_C) || defined(__SUNPRO_CC) /* Sun Studio C/C++ */ Description: Disable breakpad on x32. While x32 is not supported, breakpad mistakes it for amd64 (as both share the same processor type). This patch fixes the detection. . The profiler depends on breakpad, so it has to be disabled as well. Author: Adam Borowski kilob...@angband.pl --- iceweasel-34.0.orig/configure.in +++ iceweasel-34.0/configure.in @@ -1651,6 +1651,9 @@ Linux) *) MOZ_ENABLE_PROFILER_SPS= esac +case $target in +x86_64-*linux-gnux32) MOZ_ENABLE_PROFILER_SPS= +esac ;; WINNT|Darwin) ;; *) @@ -5929,6 +5932,10 @@ dnl = Breakpad crash reporting (on by de dnl case $target in +x86_64-*linux-gnux32*) + # x32 is not supported. + MOZ_CRASHREPORTER= + ;; i?86-*-mingw*|x86_64-*-mingw*) MOZ_CRASHREPORTER=1 ;; --- iceweasel-34.0.orig/toolkit/crashreporter/google-breakpad/src/third_party/lss/linux_syscall_support.h +++ iceweasel-34.0/toolkit/crashreporter/google-breakpad/src/third_party/lss/linux_syscall_support.h @@ -85,7 +85,8 @@ /* We currently only support x86-32, x86-64, ARM, MIPS, and PPC on Linux. * Porting to other related platforms should not be difficult. */ -#if (defined(__i386__) || defined(__x86_64__) || defined(__ARM_ARCH_3__) || \ +#if (defined(__i386__) || defined(__x86_64__) defined(__LP64__) \ + || defined(__ARM_ARCH_3__) || \ defined(__mips__) || defined(__PPC__) || defined(__ARM_EABI__)) \ (defined(__linux) || defined(__ANDROID__)) Description: Disable jpegturbo optimizations on x32. While assembly code in jpegturbo is usable on both amd64 and x32, yasm can't produce elfx32 objects. Author: Adam Borowski kilob...@angband.pl --- iceweasel-34.0.orig/configure.in +++ iceweasel-34.0/configure.in @@ -6045,10 +6045,17 @@ if test -n $MOZ_LIBJPEG_TURBO; then fi ;; *:x86_64) -if $CC -E -dM -/dev/null | grep -q __ELF__; then - LIBJPEG_TURBO_ASFLAGS=-f elf64 -rnasm -pnasm -D__x86_64__ -DPIC -DELF - LIBJPEG_TURBO_X64_ASM=1 -fi +case $target in +*-gnux32) + # yasm doesn't support elfx32. + ;; +*) + if $CC -E -dM -/dev/null | grep -q __ELF__; then +LIBJPEG_TURBO_ASFLAGS=-f elf64 -rnasm -pnasm -D__x86_64__ -DPIC -DELF +LIBJPEG_TURBO_X64_ASM=1 + fi + ;; +esac ;; esac Description: Disable the js JIT on x32. Author: Adam Borowski kilob...@angband.pl --- iceweasel-34.0.orig/js/src/configure.in +++ iceweasel-34.0/js/src/configure.in @@ -1998,6 +1998,8 @@ fi dnl Configure JIT support case $target in
Bug#775318: debian-policy: Using /srv instead of /var/lib for served user-level data
Afif Elghraoui afif.elghra...@openmailbox.org writes: I wanted to separate user-level data (for special RAID, backups, encryption and such) from system data on my machine, so I targeted /home and /srv. I found out that data managed by system services are being stored in /var/lib/packagename when I expected them to be in /srv and this doesn't really make sense to me. I also wanted to limit the size of the /var partition to around 4GB, but I can't practically do this when, for example, ownCloud is managing user's data in /var/lib/owncloud. Users would then see a file storage limit of whatever space there was left in /var. Dokuwiki, mediawiki, and I believe gitweb are other examples. I don't think this is just a personal preference on my part, since the FHS doesn't seem to describe this kind of use for /var while /srv makes more sense /var/lib -- http://www.pathname.com/fhs/pub/fhs-2.3.html#VARLIBVARIABLESTATEINFORMATION /srv -- http://www.pathname.com/fhs/pub/fhs-2.3.html#SRVDATAFORSERVICESPROVIDEDBYSYSTEM I'm afraid that you're misreading the FHS. It actually *prohibits* the distribution from doing what you want and using /srv by default. This is the important part of the /srv description for this purpose: The methodology used to name subdirectories of /srv is unspecified as there is currently no consensus on how this should be done. One method for structuring data under /srv is by protocol, eg. ftp, rsync, www, and cvs. On large systems it can be useful to structure /srv by administrative context, such as /srv/physics/www, /srv/compsci/cvs, etc. This setup will differ from host to host. Therefore, no program should rely on a specific subdirectory structure of /srv existing or data necessarily being stored in /srv. In other words, we're not allowed to assume any particular directory structure under /srv (which would be necessary to configure packages to use it by default), and are not allowed to use /srv without your (the administrator's) explicit permission. For anything that packages need to use out of the box, /var is the correct file system: /var contains variable data files. This includes spool directories and files, administrative and logging data, and transient and temporary files. Such things as databases are variable data files. Packages are certainly allowed to put them under /srv if you've explicitly configured them to do so, and hence expressed the file structure that you want to use, but we can't assume that. /srv exists for you to structure however you like, and then explicitly configure packages to use if you choose. /var is the default data store for everything, and where everything goes unless you explicitly configure it otherwise. -- Russ Allbery (r...@debian.org) http://www.eyrie.org/~eagle/ -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#775320: gnucash: Cannot switch tabs with keyboard
Package: gnucash Version: 1:2.6.4-3 Severity: normal Dear Maintainer, Recently, I came across a Tip of the Day which reads To switch between multiple tabs in the main window, press Control+Page Up/Down. I had tried this unsuccessfully in the past, but I had just installed a new version of GnuCash so I was excited. However, it still isn't working correctly. If I have a report open, the keyboard shortcuts work perfectly. If I have a register open the shortcuts will *sometimes* work. Usually, though, pressing Control+PageUp moves the focus up one screen and Control+PageDown moves the focus to the last transaction in the account. If I am at the Accounts tab, and an account is currently selected, pressing Control+PageUp/Down causes the selection to move up or down 15 lines (respectively).However, if I click on Account Name, Description, or Total to change the sorting, this unselects all the accounts, and I can then switch to an adjoining tab using the keyboard shortcuts. It would be great if this could be fixed, however, I suspect that upstream will have to fix it. Thanks -Laverne Schrock -- System Information: Debian Release: 8.0 APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 3.16.0-4-amd64 (SMP w/2 CPU cores) Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages gnucash depends on: ii gnucash-common 1:2.6.4-3 ii guile-2.0 2.0.11+1-9 ii guile-2.0-libs 2.0.11+1-9 ii libaqbanking34 5.4.3beta-2+b1 ii libaqbanking34-plugins 5.4.3beta-2+b1 ii libc6 2.19-13 ii libcairo2 1.14.0-2.1 ii libcrypt-ssleay-perl 0.58-1+b2 ii libdate-manip-perl 6.47-1 ii libdbi10.9.0-4 ii libfinance-quote-perl 1.35-1 ii libgdk-pixbuf2.0-0 2.31.1-2+b1 ii libglib2.0-0 2.42.1-1 ii libgnome-keyring0 3.12.0-1+b1 ii libgnomecanvas2-0 2.30.3-2 ii libgoffice-0.8-8 0.8.17-3 ii libgtk2.0-02.24.25-1 ii libgwengui-gtk2-0 4.12.0beta-3+b1 ii libgwenhywfar604.12.0beta-3+b1 ii libhtml-tableextract-perl 2.11-1 ii libhtml-tree-perl 5.03-1 ii libktoblzcheck1c2a 1.47-1 ii libofx61:0.9.10-1 ii libpango-1.0-0 1.36.8-3 ii libpangocairo-1.0-01.36.8-3 ii libpython2.7 2.7.9-1 ii libwebkitgtk-1.0-0 2.4.7-3 ii libwww-perl6.08-1 ii libx11-6 2:1.6.2-3 ii libxml22.9.2+dfsg1-1+b1 ii libxslt1.1 1.1.28-2+b2 ii perl 5.20.1-4 ii zlib1g 1:1.2.8.dfsg-2+b1 Versions of packages gnucash recommends: ii gnucash-docs 2.6.4-1 ii yelp 3.14.1-1 Versions of packages gnucash suggests: pn libdbd-mysqlnone pn libdbd-pgsqlnone pn libdbd-sqlite3 none -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#775323: mirror submission for debian.softmirror.in
Package: mirrors Severity: wishlist Submission-Type: new Site: debian.softmirror.in Type: leaf Archive-architecture: amd64 i386 Archive-ftp: /debian/ Archive-http: / Archive-rsync: debian/ IPv6: yes Archive-upstream: ftp.uk.debian.org Updates: four Maintainer: Bytenet n...@bytenet.in Country: IN India Location: Hyderabad Sponsor: Bytenet http://www.bytenet.in -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#775318: debian-policy: Using /srv instead of /var/lib for served user-level data
Hello, On الثلاثاء 13 كانون الثاني 2015 19:50, Russ Allbery wrote: I'm afraid that you're misreading the FHS. It actually*prohibits* the distribution from doing what you want and using /srv by default. This is the important part of the /srv description for this purpose: The methodology used to name subdirectories of /srv is unspecified as there is currently no consensus on how this should be done. One method for structuring data under /srv is by protocol, eg. ftp, rsync, www, and cvs. On large systems it can be useful to structure /srv by administrative context, such as /srv/physics/www, /srv/compsci/cvs, etc. This setup will differ from host to host. Therefore, no program should rely on a specific subdirectory structure of /srv existing or data necessarily being stored in /srv. In other words, we're not allowed to assume any particular directory structure under /srv (which would be necessary to configure packages to use it by default), and are not allowed to use /srv without your (the administrator's) explicit permission. Thanks for the clarification-- I mistakenly thought this meant that the distribution could define its own directory structure there. For anything that packages need to use out of the box, /var is the correct file system: /var contains variable data files. This includes spool directories and files, administrative and logging data, and transient and temporary files. Such things as databases are variable data files. Packages are certainly allowed to put them under /srv if you've explicitly configured them to do so, and hence expressed the file structure that you want to use, but we can't assume that. /srv exists for you to structure however you like, and then explicitly configure packages to use if you choose. /var is the default data store for everything, and where everything goes unless you explicitly configure it otherwise. Many thanks for your explanation. Regards, Afif
Bug#772823: ITP: kimchi -- HTML5 baseITP: kimchi -- HTML5 based management tool for KVM.d management tool for KVM.
Gave the proposed packages a try. Couple of things: 1. It appears this package is missing a dependency on libvirt-bin 2. Please make use of nginx proxy optional (and drop dependency down to recommends), I'm aware this will require changes to kimchi to add an option. 3. Websocksify listens on IPv4 only, this will be unreliable for people who have both v4 v6 in DNS, and break for any v6 only users. signature.asc Description: OpenPGP digital signature
Bug#775176: please don't open tcp/80 by default
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Of course I can edit ports.conf, apache2.conf, envvars and all the others. Thats not the point. Surely I am no expert in apache2 configuration, but IMU the interface to enable and disable virtual hosts is a2ensite/a2dissite. That includes the IP/IPv6 address / virtual host names *and* the ports to listen. apache2.conf should provide just a basic configuration common for all vhosts and modules. I would suggest to move the default vhosts for 80/tcp and 443/tcp to their own host modules in mods-available, making ports.conf obsolete. Then the default vhosts can be kicked out and replaced using a2dissite, as usual. I understand that its too late for Jessie, of course. Thanx very much. Keep on your good work. Harri -BEGIN PGP SIGNATURE- Version: GnuPG v1 iQEcBAEBCAAGBQJUtgMCAAoJEAqeKp5m04HL/9UH/jGrk9qAoYFDyZFIOkC+geid GGG59PaCxW8x+uX/Xo7UM99WGBq0BcwIj7tDPFRKwmt/kUCgcm8ujX/FexO96t4s b3yBXVZ1m7WgmrsjxPyBUppDQ8W0+yDrakC/a5J9VbWuLonjw4604A2NaWwZ3Fno NNYJH0aG+Pki6RZ4ddmfKR1K1gC+qsIvCDCnNSqX9pLAGBNlBKDNpsw84lMyH3xj /Q+5GImZatYVzyGzcKpQvWWKnB/J5mY47FGb/La1HIPR7tDSf8xoCKH5Xcc551lR G+BEO2374VOe6KsR6t9/dQMprsqzbZfu4DNUqQkMaLhUwKHvB5aRMH+SBP2x4Bc= =Wu2M -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#775176: please don't open tcp/80 by default
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 PS: On 01/14/15 06:47, Harald Dunkel wrote: I would suggest to move the default vhosts for 80/tcp and 443/tcp to their own host modules in mods-available, making ports.conf obsolete. Then the default vhosts can be kicked out and replaced using a2dissite, as usual. s/mods-available/sites-available/ Sorry, I was in a rush Regards Harri -BEGIN PGP SIGNATURE- Version: GnuPG v1 iQEcBAEBCAAGBQJUtgsJAAoJEAqeKp5m04HL4dgIAIaUkBCg8Ao7Nj4ThBDzstZJ ola79D8oxTWd9VRDbmB7dcGH407Nj5YYSBmWMlVqWEmXgDRInNXGKINwIHJvh7xe XmekEFH3wD9PYGWN7qvQLliYEp/kcGR92uaZaS4X8Am639uy8a/XE3/HTJBC6xML UaQWb8bpvP1GtXi4rgDwc/RfKPj3AII1ZIYs3l5y9v3vVQeT7uwlH6szQZ9x476I 3K4R4RjfETTSPFWWeOClUcGqY1noITA1raQzVxT3y1AcSbRuNEJto2Yaf1fPrUGi l9au8uUWnGjsbMWU3AR0U8qW2TW5FKXMM3H75GBy+yemN2ATdlyeI6J8/4VXxBU= =bKeU -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#775318: debian-policy: Using /srv instead of /var/lib for served user-level data
Forgot to reply-all and include the bug address... رسالة ممرّرة الموضوع: Re: Bug#775318: debian-policy: Using /srv instead of /var/lib for served user-level data التاريخ:Tue, 13 Jan 2015 22:21:30 -0800 مِن:Afif Elghraoui afif.elghra...@openmailbox.org إلى:Russ Allbery r...@debian.org On الثلاثاء 13 كانون الثاني 2015 20:59, Russ Allbery wrote: Afif Elghraoui afif.elghra...@openmailbox.org writes: Thanks for the clarification-- I mistakenly thought this meant that the distribution could define its own directory structure there. Yeah, I totally understand how you could get that impression. Unfortunately, the FHS isn't horribly clear on who the actors are at various points. I got a bit confused after looking at the /srv description again because it still seems to imply that the distribution can put things there: ...Therefore, no program should rely on a specific subdirectory structure of /srvexisting or data necessarily being stored in /srv. However /srvshould always exist on FHS compliant systems and *should be used as the default location for such data*. Distributions must take care not to remove locally placed files in these directories without administrator permission.[20] And the footnote reads: [20] This is particularly important as these areas will often contain both files initially installed by the distributor, and those added by the administrator. I didn't think it would say take care not to remove locally placed files if the distribution shouldn't be touching that directory at all... This seems like the kind of treatment required with /etc. Additionally, there isn't a statement like there is for /usr/local, where the FHS says should be empty after main installation. One thing that I was going to add and then forgot to is that, in most cases, software really should make its data locations configurable. I would say that any package in Debian that doesn't allow you to configure where it puts its data, at least if that data is at all large (not just PID files and similar sorts of tiny stuff where the overhead of relocating it isn't worth it), probably has a bug. It may just be a wishlist bug, and it may be an upstream bug, but it might still be worth filing it. Particularly if the data is at all large, being able to relocate it is important and is something that we should support. For example, in Amazon EC2 instances, the root file system is often quite small and can't be made larger, but more disk space can be mounted elsewhere, so it's important to be able to move data to other paths. That sounds like a more appropriate solution if there's no consensus on how to organize /srv in the first place. Would it (making data locations configurable) be something to consider adding to the policy as a recommendation? Afif
Bug#775165: nmu: binutils-mingw-w64_2 (wheezy-security, wheezy-p-u)
On Tue, 13 Jan 2015 23:10:46 +0100, Stephen Kitt sk...@debian.org wrote:
On Tue, 13 Jan 2015 19:54:00 +0100, Thijs Kinkhorst th...@debian.org
wrote:
Op maandag 12 januari 2015 23:03:56 schreef Stephen Kitt:
Done, I've uploaded binutils-mingw-w64 2+deb7u1 which produces
binutils-mingw-w64{,-i686,x86-64} 2.22-8+deb7u2+2+deb7u1 (ugh, that's
terrible, sorry...).
Thanks, released now.
Thanks!
How do you plan to handle unstable and jessie?
Good question, I've filed #775309 requesting binNMUs (the security issues
are fixable by binNMUs in jessie-proposed-updates and unstable).
But for jessie that relies on binutils being fixed too...
Regards,
Stephen
pgpW_g8UU5JzT.pgp
Description: OpenPGP digital signature
Bug#775296: pidgin: Error parsing username when setting up Google Talk account
Package: pidgin Version: 2.10.11-1 Severity: normal Dear Maintainer, *** Reporter, please consider answering these questions, where appropriate *** * What led up to the situation? * What exactly did you do (or not do) that was effective (or ineffective)? * What was the outcome of this action? * What outcome did you expect instead? *** End of the template - remove these template lines *** -- System Information: Debian Release: 8.0 APT prefers testing-updates APT policy: (500, 'testing-updates'), (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 3.16.0-4-amd64 (SMP w/8 CPU cores) Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages pidgin depends on: ii gconf2 3.2.6-3 ii libatk1.0-0 2.14.0-1 ii libc6 2.19-13 ii libcairo2 1.14.0-2.1 ii libdbus-1-3 1.8.12-3 ii libdbus-glib-1-20.102-1 ii libfontconfig1 2.11.0-6.3 ii libfreetype62.5.2-2 ii libgadu31:1.12.0-5 ii libgdk-pixbuf2.0-0 2.31.1-2+b1 ii libglib2.0-02.42.1-1 ii libgstreamer0.10-0 0.10.36-1.5 ii libgtk2.0-0 2.24.25-1 ii libgtkspell02.0.16-1.1 ii libice6 2:1.0.9-1+b1 ii libpango-1.0-0 1.36.8-3 ii libpangocairo-1.0-0 1.36.8-3 ii libpangoft2-1.0-0 1.36.8-3 ii libpurple0 2.10.11-1 ii libsm6 2:1.2.2-1+b1 ii libx11-62:1.6.2-3 ii libxml2 2.9.1+dfsg1-4 ii libxss1 1:1.2.2-1 ii perl-base [perlapi-5.20.1] 5.20.1-4 ii pidgin-data 2.10.11-1 Versions of packages pidgin recommends: ii gstreamer0.10-alsa 0.10.36-2 pn gstreamer0.10-ffmpegnone ii gstreamer0.10-plugins-base 0.10.36-2 ii gstreamer0.10-plugins-good 0.10.31-3+nmu4+b1 Versions of packages pidgin suggests: ii libsqlite3-0 3.8.7.1-1 -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#775137: unblock: espeakup/1:0.71-19
Control: tags -1 d-i Ok from RT, CC'ing KiBi for d-i ACK. Original message quoted below for KiBi's convenience. ~Niels On 2015-01-11 22:20, Samuel Thibault wrote: Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: unblock Please unblock package espeakup It has been only reported to me today that currently the boot with speech synthesis is very noisy. This surprised me since nowadays kernel messages are gone and systemd is silent by default. What happens is just that there is a daemon start test race in the espeakup startup script, and thus systemd always thinks that espeakup failed to start, and thus enters degraded mode, where it prints all startup logs, which takes several minutes to get spoken by the speech synthesis! The start test race is recorded as bug #775131. Fixing it properly will mean patching the daemon quite a bit, I'd rather avoid that at this stage of the release. In upload 1:0.71-19 of espeakup, whose changes are attached, I have instead just enabled the existing STARTTIME variable, which makes the script wait for a couple of seconds before testing. This will work in most cases, and since with systemd we have parallel boot, it should not hurt the user experience (in any case, much less than the several-minutes-long noisy messages). unblock espeakup/1:0.71-19 [...] -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#755545: [Pkg-libvirt-maintainers] Bug#755545: libvirt: please build with glusterfs/libgfapi support
Hi Günther For me it works without any trouble to build libvirt and qemu with gluster support on unstable and even on jessie. if you want i could send you a git diff for it? It would be really great to see that happen. cheers, -- el signature.asc Description: OpenPGP digital signature
Bug#775297: linux-image-3.16.0-4-amd64: Oops in edac_unregister_sysfs
Package: src:linux Version: 3.16.7-ckt2-1 Severity: normal Hi, I'm seeing an oops on shutdown on a Dell server, with the following trace: Jan 12 18:08:13 hx4 kernel: [370844.952075] EDAC PCI: Removed device 0 for i5000_edac EDAC PCI controller: DEV :00:10.0 Jan 12 18:08:14 hx4 kernel: [370844.968284] EDAC MC: Removed device 0 for i5000_edac.c I5000: DEV :00:10.0 Jan 12 18:08:14 hx4 kernel: [370844.968343] BUG: unable to handle kernel NULL pointer dereference at (null) Jan 12 18:08:14 hx4 kernel: [370844.972039] IP: [a03fcd82] edac_unregister_sysfs+0x22/0x30 [edac_core] Jan 12 18:08:14 hx4 kernel: [370844.972039] PGD 0 Jan 12 18:08:14 hx4 kernel: [370844.972039] Oops: [#1] SMP Jan 12 18:08:14 hx4 kernel: [370844.972039] Modules linked in: ipmi_si mpt2sas raid_class scsi_transport_sas vhost_net vhost macvtap macvlan tun ip6table_filter ip6_tables iptable_filter ip_tables ebtable_nat ebtables x_tables crc32c_generic dell_rbu ib_iser rdma_cm iw_cm ib_cm ib_sa ib_mad ib_core ib_addr iscsi_tcp libiscsi_tcp libiscsi scsi_transport_iscsi rpcsec_gss_krb5 nfsv4 dns_resolver nfsd auth_rpcgss oid_registry nfs_acl nfs lockd fscache sunrpc bridge raid1 ipmi_devintf 8021q garp stp mrp llc md_mod mptctl mptbase loop radeon iTCO_wdt ttm drm_kms_helper drm i2c_algo_bit i2c_core shpchp iTCO_vendor_support psmouse lpc_ich mfd_core coretemp i5000_edac(-) ioatdma edac_core acpi_cpufreq rng_core processor tpm_tis kvm_intel tpm dca i5k_amb evdev pcspkr serio_raw dcdbas ipmi_msghandler button thermal_sys kvm ext4 crc16 mbcache jbd2 dm_mod hid_generic usbhid hid sg sd_mod sr_mod ses cdrom enclosure crc_t10dif crct10dif_common ata_generic ata_piix uhci_hcd ehci_pci ehci_hcd usbcore libata usb_common qla2xxx Jan 12 18:08:14 hx4 kernel: scsi_transport_fc scsi_tgt bnx2 megaraid_sas scsi_mod [last unloaded: nbd] Jan 12 18:08:14 hx4 kernel: [370844.972039] CPU: 5 PID: 1001 Comm: modprobe Not tainted 3.16.0-0.bpo.4-amd64 #1 Debian 3.16.7-ckt2-1~bpo70+1 Jan 12 18:08:14 hx4 kernel: [370844.972039] Hardware name: Dell Inc. PowerEdge 2950/0H603H, BIOS 2.5.0 09/12/2008 Jan 12 18:08:14 hx4 kernel: [370844.972039] task: 880069de35f0 ti: 8803f0c74000 task.ti: 8803f0c74000 Jan 12 18:08:14 hx4 kernel: [370844.972039] RIP: 0010:[a03fcd82] [a03fcd82] edac_unregister_sysfs+0x22/0x30 [edac_core] Jan 12 18:08:14 hx4 kernel: [370844.972039] RSP: 0018:8803f0c77e60 EFLAGS: 00010286 Jan 12 18:08:14 hx4 kernel: [370844.972039] RAX: RBX: 880524884098 RCX: 01800080 Jan 12 18:08:14 hx4 kernel: [370844.972039] RDX: 0062 RSI: RDI: 0282 Jan 12 18:08:14 hx4 kernel: [370844.972039] RBP: a0418000 R08: R09: 812cb7c0 Jan 12 18:08:14 hx4 kernel: [370844.972039] R10: R11: 8800bafabd48 R12: 880524884000 Jan 12 18:08:14 hx4 kernel: [370844.972039] R13: a0418000 R14: 7f8ef346b358 R15: Jan 12 18:08:14 hx4 kernel: [370844.972039] FS: 7f8ef28f1700() GS:88053fd4() knlGS: Jan 12 18:08:14 hx4 kernel: [370844.972039] CS: 0010 DS: ES: CR0: 80050033 Jan 12 18:08:14 hx4 kernel: [370844.972039] CR2: CR3: 0004abc59000 CR4: 000427e0 Jan 12 18:08:14 hx4 kernel: [370844.972039] Stack: Jan 12 18:08:14 hx4 kernel: [370844.972039] 813033f1 880524884098 a0418068 8805248840f8 Jan 12 18:08:14 hx4 kernel: [370844.972039] 813c9bae 880524ca48e8 880524884098 a0418068 Jan 12 18:08:14 hx4 kernel: [370844.972039] 813ca740 a0418068 a04180e8 Jan 12 18:08:14 hx4 kernel: [370844.972039] Call Trace: Jan 12 18:08:14 hx4 kernel: [370844.972039] [813033f1] ? pci_device_remove+0x41/0xc0 Jan 12 18:08:14 hx4 kernel: [370844.972039] [813c9bae] ? __device_release_driver+0x7e/0x100 Jan 12 18:08:14 hx4 kernel: [370844.972039] [813ca740] ? driver_detach+0xa0/0xb0 Jan 12 18:08:14 hx4 kernel: [370844.972039] [813c99b5] ? bus_remove_driver+0x55/0xc0 Jan 12 18:08:14 hx4 kernel: [370844.972039] [813034b2] ? pci_unregister_driver+0x22/0x90 Jan 12 18:08:14 hx4 kernel: [370844.972039] [810e3b58] ? SyS_delete_module+0x158/0x210 Jan 12 18:08:14 hx4 kernel: [370844.972039] [8154872a] ? int_signal+0x12/0x17 Jan 12 18:08:14 hx4 kernel: [370844.972039] [8154846d] ? system_call_fast_compare_end+0x10/0x15 Jan 12 18:08:14 hx4 kernel: [370844.972039] Code: 2e 0f 1f 84 00 00 00 00 00 66 66 66 66 90 53 48 89 fb e8 02 92 fc e0 48 8b bb b8 02 00 00 e8 a6 bf fc e0 48 8b 83 b8 02 00 00 5b 48 8b 38 e9 06 55 da e0 90 90 90 90 90 90 66 66 66 66 90 48 83 Jan 12 18:08:14 hx4 kernel: [370844.972039] RIP [a03fcd82] edac_unregister_sysfs+0x22/0x30 [edac_core] Jan 12 18:08:14 hx4 kernel: [370844.972039] RSP 8803f0c77e60 Jan
Bug#775272: fail2ban: Enabling php-url-fopen results in a FilterPyinotify error
On Tue, 13 Jan 2015, Francois Gouget wrote: On Tue, 13 Jan 2015, Yaroslav Halchenko wrote: [...] What I did have to change though is the logpath. My understanding is that it should parse the Apache access log so I did: -logpath = /var/www/*/logs/access_log +logpath = /var/log/apache*/*access.log well -- that could have lead also to less files being attempted to load, etc, thus hiding this bug away again ;) But without that change fail2ban does not start because there's no log in /var/www, at least on Debian. I did not get this error early this morning so my theory is that it was the next roadblock and thus should not have an impact on the strptime() issue. Jan 13 14:12:57 mythsteph fail2ban[5812]: Starting authentication failure monitor: fail2banERROR No file(s) found for glob /var/www/*/logs/access_log Jan 13 14:12:57 mythsteph fail2ban[5812]: ERROR Failed during configuration: Have not found any log file for php-url-fopen jail ok then -- just monitor its operation with correct files loaded then CheersQ -- Yaroslav O. Halchenko, Ph.D. http://neuro.debian.net http://www.pymvpa.org http://www.fail2ban.org Research Scientist,Psychological and Brain Sciences Dept. Dartmouth College, 419 Moore Hall, Hinman Box 6207, Hanover, NH 03755 Phone: +1 (603) 646-9834 Fax: +1 (603) 646-1419 WWW: http://www.linkedin.com/in/yarik -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#767468: fixed?
Hi, I'm sorry, somehow I wasn't getting emails about these. This issue should be fixed in cgmangaer as of 0.34-1. It now remounts / MS_SLAVE instead of MS_PRIVATE. This should allow the umounts from the host to propagate into the cgmanager's namespace. If this does not suffice, we could add a switch to cgmanager to not create a private namespace. The effect would be that /run/cgmanager/fs would be visible on the host, which really isn't that big a deal. Another possibility would be for cgmanager to actually walk through its list of mounts and unmount anything it doesn't need. That could be more fragile, so the no-private-mntns option is probably the better route. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#775181: (no subject)
Thanks Sebastian. The patch you did provide works fine for me. I made a bug report to upstream: https://bitbucket.org/multicoreware/x265/issue/98/make-cli-work-with-any-bit-depth-version -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#775137: unblock: espeakup/1:0.71-19
Niels Thykier, le Tue 13 Jan 2015 18:19:26 +0100, a écrit : Control: tags -1 d-i Ok from RT, CC'ing KiBi for d-i ACK. Original message quoted below for KiBi's convenience. (The patch is only for the installed package, it does not change the d-i package). ~Niels On 2015-01-11 22:20, Samuel Thibault wrote: Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: unblock Please unblock package espeakup It has been only reported to me today that currently the boot with speech synthesis is very noisy. This surprised me since nowadays kernel messages are gone and systemd is silent by default. What happens is just that there is a daemon start test race in the espeakup startup script, and thus systemd always thinks that espeakup failed to start, and thus enters degraded mode, where it prints all startup logs, which takes several minutes to get spoken by the speech synthesis! The start test race is recorded as bug #775131. Fixing it properly will mean patching the daemon quite a bit, I'd rather avoid that at this stage of the release. In upload 1:0.71-19 of espeakup, whose changes are attached, I have instead just enabled the existing STARTTIME variable, which makes the script wait for a couple of seconds before testing. This will work in most cases, and since with systemd we have parallel boot, it should not hurt the user experience (in any case, much less than the several-minutes-long noisy messages). unblock espeakup/1:0.71-19 [...] -- Samuel v je viens d'inventer mutt version magritte :D y ? v dans mutt v tape cceci return -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#774889: Patch for gdm conflict with gdm3 in Jessie
Attached is the Patch for fixing the gdm3 upgrade issue from Squeeze - Wheezy - Jessie. The Wheezy gdm3 package properly addresses the conflict between the gdm and gdm3 .,but it is not done in gdm3. This patch will fix up that issue and does seamless upgrades. -- Regards., Prema S Index: debian/control === --- debian/control (revision 44082) +++ debian/control (working copy) @@ -91,6 +91,7 @@ Suggests: libpam-gnome-keyring, gnome-orca Provides: x-display-manager +Conflicts: gdm Breaks: gnome-panel ( 3.0), gnome-screensaver ( 2.17.7), gnome-orca ( 2.30.0-2), Index: debian/control.in === --- debian/control.in (revision 44082) +++ debian/control.in (working copy) @@ -87,6 +87,7 @@ Suggests: libpam-gnome-keyring, gnome-orca Provides: x-display-manager +Conflicts: gdm Breaks: gnome-panel ( 3.0), gnome-screensaver ( 2.17.7), gnome-orca ( 2.30.0-2),
Bug#775291: numerical feed name causes exception
Hi Dne Tue, 13 Jan 2015 17:21:59 -0200 Antonio Terceiro terce...@debian.org napsal(a): You need to quote the name: - name: 067 url: https://067.cz/rss/ target: ... Thanks, I've figured this out. The config file is parsed as YAML, and a 067 unquoted _will_ be parsed as a number. I can even change feed2imap to handle receiving numbers as the feed name by converting them to strings, but I can't stop the YAML parser from doing the octal to decimal conversion for example. I understand that the conversion happens, but that should not break the program from further processing the entry. It seems that it tries to call string method (gsub) on integer or float it gets from the yaml parser. -- Michal Čihař | http://cihar.com | http://blog.cihar.com pgpwDv_hsj5bu.pgp Description: OpenPGP digital signature
Bug#775326: git bash completion for 'git branch --set-upstrea-to=' deletes the option
Package: git Version: 1:2.1.4-2 Severity: normal Dear Maintainer, I'm running bash, and I'm in a git repo on branch suggestion-cleanup, and type $ git branch --set-upstream-to=o and then hit tab to get completions for origin/... After I hit tab, the prompt is $ git branch origin/ Which means that the tab completion removed the '--set-upstream-to=' from my prompt. I expected the prompt to be $ git branch --set-upstream-to=origin/ This is clearly unintuitive, and hinders work with git more than it helps. I've verified that this is not just a display problem; the option is actually gone. *** Reporter, please consider answering these questions, where appropriate *** * What led up to the situation? * What exactly did you do (or not do) that was effective (or ineffective)? * What was the outcome of this action? * What outcome did you expect instead? *** End of the template - remove these template lines *** -- System Information: Debian Release: 8.0 APT prefers testing-updates APT policy: (500, 'testing-updates'), (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=de_DE.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages git depends on: ii git-man 1:2.1.4-2 ii libc62.19-13 ii libcurl3-gnutls 7.38.0-4 ii liberror-perl0.17-1.1 ii libexpat12.1.0-6+b3 ii libpcre3 2:8.35-3.3 ii perl-modules 5.20.1-4 ii zlib1g 1:1.2.8.dfsg-2+b1 Versions of packages git recommends: ii less 458-3 ii openssh-client [ssh-client] 1:6.7p1-3 ii patch2.7.1-6 ii rsync3.1.1-2+b1 Versions of packages git suggests: ii gettext-base 0.19.3-2 pn git-arch none pn git-cvs none pn git-daemon-run | git-daemon-sysvinit none pn git-doc none pn git-elnone pn git-email none pn git-gui none pn git-mediawiki none ii git-svn 1:2.1.4-2 pn gitk none pn gitwebnone -- 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#775327: apport: Unicode exception when parsing some crashes
Package: apport
Version: 2.15.1-1
Severity: important
This behavior seems to be very racy.
ERROR: apport (pid 1148) Wed Jan 14 12:46:21 2015: pid: 1148, uid: 1000, gid:
1000, euid: 0, egid: 0
ERROR: apport (pid 1148) Wed Jan 14 12:46:21 2015: environment: environ({})
ERROR: apport (pid 1278) Wed Jan 14 12:48:05 2015: called for pid 1264, signal
11, core limit 0
ERROR: apport (pid 1278) Wed Jan 14 12:48:05 2015: executable: /bin/sleep
(command line sleep 900)
ERROR: apport (pid 1278) Wed Jan 14 12:48:05 2015: Unhandled exception:
Traceback (most recent call last):
File /usr/share/apport/apport, line 389, in module
if is_closing_session(pid, pidstat.st_uid):
File /usr/share/apport/apport, line 213, in is_closing_session
env = e.read().split('\0').decode('utf-8')
File /usr/lib/python3.4/encodings/ascii.py, line 26, in decode
return codecs.ascii_decode(input, self.errors)[0]
UnicodeDecodeError: 'ascii' codec can't decode byte 0xe2 in position 2646:
ordinal not in range(128)
ERROR: apport (pid 1278) Wed Jan 14 12:48:05 2015: pid: 1278, uid: 1000, gid:
1000, euid: 0, egid: 0
ERROR: apport (pid 1278) Wed Jan 14 12:48:05 2015: environment: environ({})
If the same code is manualy run, e.read() succeeds.
In [4]: pid = 1543
In [5]: with open('/proc/%s/environ' % pid) as e:
env = e.read().split('\0')
...:
In [6]:
-- System Information:
Debian Release: 8.0
APT prefers testing
APT policy: (990, 'testing'), (500, 'unstable'), (101, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
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: sysvinit (via /sbin/init)
Versions of packages apport depends on:
ii gir1.2-glib-2.0 1.42.0-2.2
ii lsb-base 4.1+Debian13+nmu1
ii python3 3.4.2-2
ii python3-apport 2.15.1-1
ii python3-gi 3.14.0-1
pn python:any none
Versions of packages apport recommends:
ii policykit-1 0.105-8
Versions of packages apport suggests:
ii apport-gtk 2.15.1-1
ii apport-kde 2.15.1-1
-- Configuration Files:
/etc/apport/crashdb.conf changed:
default = 'debian-debug'
databases = {
'ubuntu': {
'impl': 'launchpad',
'bug_pattern_url':
'http://people.canonical.com/~ubuntu-archive/bugpatterns/bugpatterns.xml',
'dupdb_url':
'http://people.canonical.com/~ubuntu-archive/apport-duplicates',
'distro': 'ubuntu',
'escalation_tag': 'bugpattern-needed',
'escalated_tag': 'bugpattern-written',
},
'fedora': {
# NOTE this will change Fall '07 when RHT switches to bugzilla 3.x!
'impl': 'rhbugzilla',
'bug_pattern_url': 'http://qa.fedoraproject.org/apport/bugpatterns.xml',
'distro': 'fedora'
},
'debian': {
'impl': 'debian',
'distro': 'debian',
'smtphost': 'reportbug.debian.org',
'recipient': 'sub...@bugs.debian.org',
'sender': ''
},
'debian-debug': {
'impl': 'debian',
'distro': 'debian',
'smtphost': 'localhost',
'recipient': 'r...@researchut.com',
'sender': 'app...@researchut.com'
},
'debug': {
# for debugging
'impl': 'memory',
'bug_pattern_url': '/tmp/bugpatterns.xml',
'distro': 'debug'
},
}
/etc/init.d/apport changed:
PATH=/sbin:/bin:/usr/sbin:/usr/bin
. /lib/lsb/init-functions
if [ -f /etc/default/apport ]; then
. /etc/default/apport
fi
start() {
[ $enabled = 1 ] || [ $force_start = 1 ] || exit 0
mkdir -p -m 1777 /var/crash
ulimit -c unlimited
# check for kernel crash dump, convert it to apport report
if [ -e /var/crash/vmcore ]
then
log_daemon_msg Checking for kernel crash dumps
/usr/share/apport/kernel_crashdump || true
log_end_msg 0
fi
log_daemon_msg Enabling apport service
echo |/usr/share/apport/apport %p %s %c /proc/sys/kernel/core_pattern
log_end_msg 0
}
stop() {
log_daemon_msg Disabling apport service
if [ `dd if=/proc/sys/kernel/core_pattern count=1 bs=1 2/dev/null` !=
| ]
then
exit 1
else
echo core /proc/sys/kernel/core_pattern
fi
log_end_msg 0
}
restart() {
stop
start
}
status() {
log_daemon_msg Checking apport service
grep -qi |/usr/share/apport/apport /proc/sys/kernel/core_pattern
log_end_msg 0 || log_end_msg 1
}
case $1 in
start|stop|restart)
$1
;;
force-reload)
restart
;;
status)
status
;;
*)
echo Usage: $0 {start|stop|restart|force-reload|status}
exit 1;
;;
esac
-- debconf-show failed
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#775184: unblock: gtkpod/2.1.4-5 (pre-approval)
Hi! On 2015-01-13 at 23:26 (CET), Ivo De Decker wrote: [...] + * debian/control: dh-python b-dep added This doesn't seem to comply with the freeze policy. Why are you doing the change? What's the impact of this? Because, without it, in the build log you would find: W: dh_python2:479: Please add dh-python package to Build-Depends That's the main reason why I added it. It's a minor change that would keep the package in shape. But if it goes against the freeze policy, then I can drop it. Please, let me know how I should proceed now. Cheers. -- Matteo F. Vescovi || Debian Developer GnuPG KeyID: 4096R/0x8062398983B2CF7A -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#775151: unblock: code-saturne/3.3.2-3
On 2015-01-13 20:40, Gilles Filippini wrote: Niels Thykier a écrit le 13/01/2015 17:12 : Control: tags -1 moreinfo [...] Hi, Thanks for providing this patch. Unfortunately, I suspect is missing a versioned Breaks and Replace on code-saturne-data (from code-saturne-include). This is customary (and required) for moving files between two packages and it does not seem to be present in the debdiff you provided. Without this, we would simply trade one RC bug for another. You're right /o\ Fixed and uploaded as version 3.3.2-4. New debdiff against 3.3.2-2 attached. Thanks! _g. Unblocked, thanks. I took the liberty of closing #775259 as well. ~Niels -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#762123: evince-gtk: selected text is a solid black box, renders text unreadable
Hi Pedro, I can still reproduce this bug with this version of evince-gtk: $ aptitude show evince-gtk | grep Version Version: 3.14.1-1 with the example pdf attached to this mail. Thanks for looking into this. Regards, Tim Am 13.01.2015, 23:40 Uhr, schrieb Pedro Beja altha...@gmail.com: Hey Tim, thanks for reporting. Could you please still reproduce this issue with newer evince version like 3.14.1-1 ? If so, could you also provide a pdf file example ? thanks regards althaser foo.pdf Description: Adobe PDF document foo.tex Description: TeX document
Bug#775139: mktexlsr: insecure use of /tmp
On Tue, Jan 13, 2015 at 08:24:48AM +0900, Norbert Preining wrote: Dear Jakub, treefile=`mktemp --tmpdir mktexlsrtrees.XX` || exit 1 Thanks, that is fine. I have build, tested, and uploaded new packages. In 4 days or so I will ask for a freeze exception. You don't need to wait that long if you don't want to - you can ask for an exception immediately following an upload. Julian -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#775291: numerical feed name causes exception
On Tue, Jan 13, 2015 at 05:09:06PM +0100, Michal Čihař wrote: Package: feed2imap Version: 1.2.3-1 Severity: normal Hi while running feed2imap, I got following error: I, [2015-01-13T09:40:35.167347 #30040] INFO -- : 55: 14 new items, 0 updated items. F, [2015-01-13T09:40:35.167766 #30040] FATAL -- : Exception caught while uploading mail to RSS: undefined method `gsub' for 55:Fixnum /usr/lib/ruby/vendor_ruby/feed2imap/feed2imap.rb:247:in `block in initialize' /usr/lib/ruby/vendor_ruby/feed2imap/feed2imap.rb:220:in `each' /usr/lib/ruby/vendor_ruby/feed2imap/feed2imap.rb:220:in `initialize' /usr/bin/feed2imap:48:in `new' /usr/bin/feed2imap:48:in `main' F, [2015-01-13T09:40:35.168778 #30040] FATAL -- : We can't recover from IMAP errors, so we are exiting. when debugging, I've realized that this is caused by following entry: - name: 067 url: https://067.cz/rss/ target: ... While parsing the configuration, feed2imap parses 067 as number and converts it to 55, but it later probaly fails to find such named section. You need to quote the name: - name: 067 url: https://067.cz/rss/ target: ... The config file is parsed as YAML, and a 067 unquoted _will_ be parsed as a number. I can even change feed2imap to handle receiving numbers as the feed name by converting them to strings, but I can't stop the YAML parser from doing the octal to decimal conversion for example. -- Antonio Terceiro terce...@debian.org signature.asc Description: Digital signature
Bug#775298: base: SDHC card not detected on Acer V5 laptop
Package: base Severity: important Dear Maintainer, I have a Kodak SDHC card 4Gb. It is not detected when it is inserted and also not detected if it's in during boot. Basically it's never detected. Except I noticed if I insert a USB flash stick during boot then it also finds the SDHC card. coco@debian:~$ lspci 00:00.0 Host bridge: Intel Corporation 3rd Gen Core processor DRAM Controller (rev 09) 00:02.0 VGA compatible controller: Intel Corporation 3rd Gen Core processor Graphics Controller (rev 09) 00:16.0 Communication controller: Intel Corporation 7 Series/C210 Series Chipset Family MEI Controller #1 (rev 04) 00:1a.0 USB controller: Intel Corporation 7 Series/C210 Series Chipset Family USB Enhanced Host Controller #2 (rev 04) 00:1b.0 Audio device: Intel Corporation 7 Series/C210 Series Chipset Family High Definition Audio Controller (rev 04) 00:1c.0 PCI bridge: Intel Corporation 7 Series/C210 Series Chipset Family PCI Express Root Port 1 (rev c4) 00:1c.1 PCI bridge: Intel Corporation 7 Series/C210 Series Chipset Family PCI Express Root Port 2 (rev c4) 00:1c.2 PCI bridge: Intel Corporation 7 Series/C210 Series Chipset Family PCI Express Root Port 3 (rev c4) 00:1d.0 USB controller: Intel Corporation 7 Series/C210 Series Chipset Family USB Enhanced Host Controller #1 (rev 04) 00:1f.0 ISA bridge: Intel Corporation 7 Series Chipset Family LPC Controller (rev 04) 00:1f.2 SATA controller: Intel Corporation 7 Series Chipset Family 6-port SATA Controller [AHCI mode] (rev 04) 00:1f.3 SMBus: Intel Corporation 7 Series/C210 Series Chipset Family SMBus Controller (rev 04) 03:00.0 Network controller: Qualcomm Atheros AR9462 Wireless Network Adapter (rev 01) 04:00.0 Ethernet controller: Broadcom Corporation NetLink BCM57785 Gigabit Ethernet PCIe (rev 10) 04:00.1 SD Host controller: Broadcom Corporation BCM57765/57785 SDXC/MMC Card Reader (rev 10) -- System Information: Debian Release: 8.0 APT prefers testing-updates APT policy: (500, 'testing-updates'), (500, 'testing') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.16.0-4-amd64 (SMP w/2 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#775151: unblock: code-saturne/3.3.2-3
Niels Thykier a écrit le 13/01/2015 17:12 :
Control: tags -1 moreinfo
On 2015-01-12 01:37, Gilles Filippini wrote:
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: unblock
Please unblock package code-saturne
Version 3.3.2-3 fixes RC bug #775107 which makes code-saturne mostly
unusable on all archs but one because an arch dependent file
(cs_config.py) was shipped with an arch=all package.
The fix moves cs_config.py to code-saturne-include which is arch=any.
Please find attache the debdiff against version 3.3.2-2.
unblock code-saturne/3.3.2-3
Thanks,
_g.
[...]
Hi,
Thanks for providing this patch.
Unfortunately, I suspect is missing a versioned Breaks and Replace
on code-saturne-data (from code-saturne-include). This is customary
(and required) for moving files between two packages and it does not
seem to be present in the debdiff you provided. Without this, we would
simply trade one RC bug for another.
You're right /o\
Fixed and uploaded as version 3.3.2-4.
New debdiff against 3.3.2-2 attached.
Thanks!
_g.
diff -Nru code-saturne-3.3.2/debian/changelog
code-saturne-3.3.2/debian/changelog
--- code-saturne-3.3.2/debian/changelog 2014-09-23 13:12:19.0 +0200
+++ code-saturne-3.3.2/debian/changelog 2015-01-13 19:28:31.0 +0100
@@ -1,3 +1,19 @@
+code-saturne (3.3.2-4) unstable; urgency=medium
+
+ * Team upload.
+ * debian/control: add missing Breaks / Replaces to fix the previous
+change (cf. Policy section 7.6.1).
+
+ -- Gilles Filippini p...@debian.org Tue, 13 Jan 2015 19:28:29 +0100
+
+code-saturne (3.3.2-3) unstable; urgency=medium
+
+ * Team upload.
+ * Move arch-dependant script cs_config.py from code-saturne-data to
+code-saturne-include (Closes: #775107).
+
+ -- Gilles Filippini p...@debian.org Sun, 11 Jan 2015 16:01:45 +0100
+
code-saturne (3.3.2-2) unstable; urgency=medium
* Team upload.
diff -Nru code-saturne-3.3.2/debian/code-saturne-include.install
code-saturne-3.3.2/debian/code-saturne-include.install
--- code-saturne-3.3.2/debian/code-saturne-include.install 2014-09-22
21:39:38.0 +0200
+++ code-saturne-3.3.2/debian/code-saturne-include.install 2015-01-11
15:14:41.0 +0100
@@ -1,2 +1,2 @@
debian/tmp/usr/include
-
+debian/tmp/usr/lib/python*/dist-packages/code_saturne/cs_config.py
diff -Nru code-saturne-3.3.2/debian/control code-saturne-3.3.2/debian/control
--- code-saturne-3.3.2/debian/control 2014-09-23 11:53:33.0 +0200
+++ code-saturne-3.3.2/debian/control 2015-01-13 19:40:28.0 +0100
@@ -99,6 +99,8 @@
Architecture: any
Depends: ${shlibs:Depends}, ${misc:Depends}, libcgns-dev, libmedc-dev,
libhdf5-dev, zlib1g-dev, mpi-default-dev, libxml2-dev
+Replaces: code-saturne-data ( 3.3.2-3)
+Breaks: code-saturne-data ( 3.3.2-3)
Description: General purpose Computational Fluid Dynamics (CFD) software -
includes
The basic capabilities of Code_Saturne enable the handling of either
incompressible or expandable flows with or without heat transfer and
diff -Nru code-saturne-3.3.2/debian/rules code-saturne-3.3.2/debian/rules
--- code-saturne-3.3.2/debian/rules 2014-09-23 13:02:24.0 +0200
+++ code-saturne-3.3.2/debian/rules 2015-01-13 19:18:31.0 +0100
@@ -1,6 +1,10 @@
#!/usr/bin/make -f
# Copyright 2009 Sylvestre Ledru sylves...@debian.org
+# Exclude cs_config.py from package code-saturne-data
+# It should go into code-saturne-include
+binary-install/code-saturne-data:: DEB_DH_INSTALL_ARGS := -Xcs_config.py
+
include /usr/share/cdbs/1/rules/debhelper.mk
include /usr/share/cdbs/1/class/autotools.mk
include /usr/share/cdbs/1/rules/autoreconf.mk
@@ -28,3 +32,6 @@
binary-install/code-saturne-data::
chmod +x debian/code-saturne-data/usr/share/code_saturne/runcase*
dh_python2 -pcode-saturne-data
+
+binary-install/code-saturne-include::
+ dh_python2 -pcode-saturne-include
signature.asc
Description: OpenPGP digital signature
Bug#775165: nmu: binutils-mingw-w64_2 (wheezy-security, wheezy-p-u)
Op maandag 12 januari 2015 23:03:56 schreef Stephen Kitt:
Done, I've uploaded binutils-mingw-w64 2+deb7u1 which produces
binutils-mingw-w64{,-i686,x86-64} 2.22-8+deb7u2+2+deb7u1 (ugh, that's
terrible, sorry...).
Thanks, released now.
How do you plan to handle unstable and jessie?
Cheers,
Thijs
signature.asc
Description: This is a digitally signed message part.
Bug#775183: spamass-milter adds bad Received: header, creating false positive
On Tue, 13 Jan 2015, Moritz Both wrote:
Don,
thank you for the response. I hope this bug report does not mutate
to a support case embarrasingly ;) Anyway I'm confused your
source code is diffrent from mine... is there something newer than
0.3.2-1 in stable? Is your code from 0.3.2-1b1 from sid?
moritz@eroski:~/src$ apt-get source spamass-milter
[...]
Holen: 1 http://ftp.de.debian.org/debian/ wheezy/main spamass-milter 0.3.2-1
(dsc) [1.882 B]
Holen: 2 http://ftp.de.debian.org/debian/ wheezy/main spamass-milter 0.3.2-1
(tar) [155 kB]
Holen: 3 http://ftp.de.debian.org/debian/ wheezy/main spamass-milter 0.3.2-1
(diff) [15,1 kB]
Es wurden 172 kB in 0 s geholt (526 kB/s).
dpkg-source: Information: spamass-milter wird nach spamass-milter-0.3.2
extrahiert
dpkg-source: Information: spamass-milter_0.3.2.orig.tar.gz wird entpackt
dpkg-source: Information: spamass-milter_0.3.2-1.debian.tar.gz wird entpackt
dpkg-source: Information: ignore_by_smtp_auth wird angewandt
dpkg-source: Information: fix_spacing_in_received_header wird angewandt
dpkg-source: Information: fix_header_char_cast wird angewandt
dpkg-source: Information: add_ipv6_support wird angewandt
dpkg-source: Information: auth_in_received wird angewandt
Now, spamass-milter.cpp says
string rec_header;
rec_header=(string)Received: from +macro_s+
(+macro__+)\r\n\t;
if (strlen(macro_auth_type)!=0) {
rec_header+=(string)(authenticated;
if (strlen(macro_auth_ssf)!=0) {
rec_header+=(string) bits=+macro_auth_ssf;
}
rec_header+=(string))\r\n\t;
}
rec_header+=(string)by +macro_j+(+macro_v+/+macro_Z+)
with +
macro_r+ id +macro_i+\r\n\t+
macro_b+\r\n\t+
(envelope-from +assassin-from()+\r\n;
debug(D_SPAMC, Received header for spamc: %s,
rec_header.c_str());
assassin-output(rec_header);
It is obvious that this code does not add the ; or ). To me it is not
obvious why my dates are messed up. I added the -d ALL switch and wait
for the next occurance in the next several hours.
Hrm. Actually, I see the problem now. For some crazy reason, the patches
(probably when I was updating to 3.3.2) got screwed up, and I didn't
catch this.
I'll fix them now.
--
Don Armstrong http://www.donarmstrong.com
Live and learn
or die and teach by example
-- a softer world #625
http://www.asofterworld.com/index.php?id=625
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#775266: Fwd: Re: [vbox-dev] Custom Bridge Interface
---BeginMessage--- Yeah. To attach to custom bridge create a loopback interface on your host OS, then join custom bridge with loopback, then bridge VBOX VM with loopback. ---End Message--- ---BeginMessage--- On 01/13/2015 06:39 PM, Alexey Eromenko wrote: Yeah. To attach to custom bridge create a loopback interface on your host OS, then join custom bridge with loopback, then bridge VBOX VM with loopback. Hello Alexey, What exact loopback device you are referring to here ? Like I mentioned in the initial post, I am able to bind the VMs network to the host's bridge, which isn't bound to any particular host interface. See config below: # This bridge will is used to NAT LXC containers' traffic auto lxcbr0 iface lxcbr0 inet static bridge_fd 0 bridge_maxwait 0 address 172.16.10.1 netmask 255.255.0.0 pre-up brctl addbr lxcbr0 post-down brctl delbr lxcbr0 post-down echo 0 /proc/sys/net/ipv4/ip_forward post-down echo 0 /proc/sys/net/ipv6/conf/all/forwarding post-up echo 1 /proc/sys/net/ipv4/ip_forward post-up echo 1 /proc/sys/net/ipv6/conf/all/forwarding post-up iptables -A FORWARD -i lxcbr0 -s 172.16.10.1/16 -j ACCEPT post-up iptables -A POSTROUTING -t nat -s 172.16.10.1/16 -j MASQUERADE # add checksum so that dhclient does not complain. # udp packets staying on the same host never have a checksum filled else post-up iptables -A POSTROUTING -t mangle -p udp --dport bootpc -s 172.16.10.1/16 -j CHECKSUM --checksum-fill pre-down iptables -D FORWARD -i lxcbr0 -s 172.16.10.1/16 -j ACCEPT pre-down iptables -D POSTROUTING -t nat -s 172.16.10.1/16 -j MASQUERADE # add checksum so that dhclient does not complain. # udp packets staying on the same host never have a checksum filled else pre-down iptables -D POSTROUTING -t mangle -p udp --dport bootpc -s 172.16.10.1/16 -j CHECKSUM --checksum-fill Can anyone shed some light on what the crash maybe ? I encountered the crash when trying to ssh into one of the VMs, which is when it lost network. Surprisingly, prior to the ssh, all ping requests worked fine. -- Ritesh Raj Sarraf RESEARCHUT - http://www.researchut.com Necessity is the mother of invention. signature.asc Description: OpenPGP digital signature ---End Message--- ---BeginMessage--- Loopback = TAP interface. You will need to create a TAP interface, and it needs to be connected both to Virtual Box and to your bridge. I described exactly how to do this in SUSE lessons for lizards text in 2007, but it is hard to come by nowadays. ---End Message--- ---BeginMessage--- A simpler way may be to use Virtual Box host-only adapter interface, and add it to your bridge. ---End Message--- ---BeginMessage--- On 01/13/2015 07:19 PM, Alexey Eromenko wrote: A simpler way may be to use Virtual Box host-only adapter interface, and add it to your bridge. Yeah.. But my requirement is different. I'd like to be able to make my LXC containers be on the same bridge, and talk to my VBox VMs. I think I've built the right config. But there's some bug somewhere, because if the config was incorrect, it'd never work. In my case, it works. But later, it dies. -- Ritesh Raj Sarraf RESEARCHUT - http://www.researchut.com Necessity is the mother of invention. signature.asc Description: OpenPGP digital signature ---End Message--- ---BeginMessage--- On 01/14/2015 12:32 AM, Ritesh Raj Sarraf wrote: On 01/13/2015 07:19 PM, Alexey Eromenko wrote: A simpler way may be to use Virtual Box host-only adapter interface, and add it to your bridge. Yeah.. But my requirement is different. And someone on this please explain what this crash may be at: [ 2289.915168] nspr-3[13830]: segfault at 18 ip 7f4d559a33af sp 7f4d45930690 error 4 in VBoxXPCOMIPCC.so[7f4d55991000+1e000] I was able to trigger it again. -- Ritesh Raj Sarraf RESEARCHUT - http://www.researchut.com Necessity is the mother of invention. signature.asc Description: OpenPGP digital signature ---End Message--- signature.asc Description: OpenPGP digital signature
Bug#773861: Signify - OpenBSD's cryptographic signing tool
On Sat, Jan 10, 2015 at 1:31 PM, Riley Baird wrote: Typos in upstream code: equivilent - equivalent ouput - output Do these really have to be fixed? They won't be visible to the user, and it's likely to annoy upstream more than anything. I'll do it if I have to, though. If upstream are so hostile as to be annoyed by fixes for typos, I would personally question if their software is worth packaging at all. https://www.debian.org/doc/manuals/developers-reference/developer-duties.html#upstream-coordination -- bye, pabs https://wiki.debian.org/PaulWise -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#775255: [pkg-fetchmail-maint] Bug#775255: fetchmail: Fails to start when libssl has SSLv3 disabled
Yes, it works with the version of libssl from unstable since SSLv3 is not
disabled in that version. The main problem is that currently, fetchmail does
not work with more secure versions of libssl (which have SSLv3 disabled
completely). I just provided one solution (completely disable SSLv3 in
fetchmail), but if another one (such as automatically detecting that libssl
does not provide SSLv3 and therefore not even attempting to load the SSLv3
symbols) works better, that's fine too.
Currently, the version of fetchmail in experimental is the same as the version
of fetchmail in unstable. If necessary, you could release a different version
of fetchmail for experimental which drops SSLv3 support entirely (if updating
the one in unstable seems like a bad idea currently), since SSLv3 support
*should* be dropped at some point due to the POODLE bug.
This is not an issue of fetchmail negotiating SSLv3 by default, this is an
issue of fetchmail looking for symbols in libssl *which don't exist*. The first
would only surface if, for example, libssl provided an empty implementation of
SSLv3 but still exported the symbols. What's happening right now is that the
symbols don't even exist, which leads to the program not working at all. This
is regardless of whether or not I actually utilize SSLv3 as my protocol (which
I never specifically requested).
- Chiraag
--
Chiraag M Nataraj
Senior at the California Institute of Technology
Email: chiraag.nata...@gmail.com
Phone: 610-350-6329
Website: http://chiraag.nataraj.us
On Wed, Jan 14, 2015 at 12:38:54AM +0100, Nico Golde wrote:
Hi,
* Chiraag Nataraj chiraag.nata...@gmail.com [2015-01-13 12:22]:
Package: fetchmail
Version: 6.3.26-1+b1
Severity: grave
Justification: renders package unusable
You filed a bug against a version that works absolutely fine with the openssl
version it is supposed to work with. Hence, I'm inclined to close that bug or
downgrade it to wishlist in favor of removing/disabling sslv3 support in
fetchmail.
When the latest version of libssl1.0.0 is installed from experimental
(which has SSLv3 disabled), Fetchmail exits with the following error:
fetchmail: relocation error: fetchmail: symbol SSLv3_client_method, version
OPENSSL_1.0.0 not defined in file libssl.so.1.0.0 with link time reference
See above
Fetchmail should be rebuilt to not require SSLv3.
The patch you included simply removes this feature entirely:
--- fetchmail-6.3.26/socket.c 2013-04-23 22:00:45.0 +0200
+++ socket.c2015-01-14 00:29:53.412608735 +0100
@@ -913,8 +913,6 @@
report(stderr, GT_(Your operating system does not
support SSLv2.\n));
return -1;
#endif
- } else if(!strcasecmp(ssl3,myproto)) {
- _ctx[sock] = SSL_CTX_new(SSLv3_client_method());
} else if(!strcasecmp(tls1,myproto)) {
_ctx[sock] = SSL_CTX_new(TLSv1_client_method());
} else if (!strcasecmp(ssl23,myproto)) {
In the current git version of fetchmail, sslv3 is not negotiated by default,
unless a user explicitly requests to do so. As such I'm not sure how useful
this patch is as well.
Matthias, do you mind weighing in on this?
Thanks
Nico
--
Nico Golde - XMPP: n...@jabber.ccc.de - GPG: 0xA0A0
signature.asc
Description: Digital signature
Bug#735261: mutiple upstream bugs
control: severity -1 important It may sound cynical, but my advice would be that if you're hit with this, change mail clients :/ In the context of freeze/release, I'd suggest to tag this jessie-ignore, or even forever-ignore. This is a usability problem, so it doesn't really qualify as release critical. Best wishes, Mike -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#767839: debian-policy: Linking documentation of arch:any package to arch:all
Hi, Robert Luberda wrote: Please explicitly state in the Policy if linking /usr/share/doc/arch:any_package to ../arch:all_package (where arch:any_package and arch:all_package come from the same source package) is allowed or not. It currently is not allowed. [...] In my opinion, as I wrote in #766711, footnote [116] allows such linking, as it seems to refer to source version of a package. I agree that the text is confusing. The reference to source there is meant to refer to the source package, not to the source package version. Thanks and hope that helps, Jonathan -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#775317: Depreciated kernel graphics params
Package: debian-installer Grub2 (efi) and syslinux config bootloader menu entries are using depreciated video graphics kernel parameters. At least this is the case with a Debian 7.7 install image I have to hand, I am unaware if this has been fixed in more recent versions of d-i, though I did briefly search the changelog and found nothing. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#652108: Testing Time
I believe I just finished this up [1]. Please, review it and offer opinions. I don't want to include something that isn't of high quality. [1] https://github.com/ngx/ngx-conf -- Michael Lustfield -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#773749: Resolvconf vs wicd
On 2015-01-13 23:32:45 +0100, Axel Beckert wrote: Yes, the patch has been removed with the 1.6.0-1 upload with the following changelog entry: * debian/patches/: - 01-fix_desktop_file.patch, 07-add_resolvconf_support.patch removed, fixed upstream Anyway I haven't provided any DNS settings in the wicd configuration (I don't use static DNS). So, in my case, it is dhclient that should set up the DNS (unless some hook script overrides the default behavior). -- Vincent Lefèvre vinc...@vinc17.net - Web: https://www.vinc17.net/ 100% accessible validated (X)HTML - Blog: https://www.vinc17.net/blog/ Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon) -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#774762: try harder to find reasons for failed `lvchange -an` by looking at /proc/*/mountinfo
I'd say the best who-uses tool in this case is lsblk [...] LVM itself already uses this tool within helper blkdeactivate script [...] so you see a chance that lvm could delegate the diagnoistic messages for where to find the offending mount point to lsblk (or dmsetup or findmnt, but lsblk is probably the most suitable of those)? if yes, i'd open a similar bug against util-linux (lsblk does not do any better than lvm in container conditions at the moment), and keep this only open to track lvm's progress on delegating to lsblk. best regards chrysn signature.asc Description: Digital signature
Bug#775178: Suspend failing after update of kernel to 3.2.65-1 (amd64)
Nathan Wallach taniwall...@gmail.com writes: Jens - I found your bug-report: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=775178 I also had a problem with resume from suspend failing after the update to kernel 3.2.65-1, and found a number of other similar bug-reports. Many pointed to the patched kernel Ben Hutchings prepared, see below. His patched kernel solved the problem on my laptop. Thanks! = very likely #775178 could be merged with #774461 Don't have the time to test this now and will wait for the security update. (downgraded to 3.2.63-2+deb7u2 for now now) Greetings, jens -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#775253: dbab: unowned files after purge (policy 6.8, 10.8): /etc/dnsmasq.d/dnsmasq.{adblock, trashsites}.conf
Package: dbab Version: 1.2.2-1 Severity: important User: debian...@lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed your package left unowned files on the system after purge, which is a violation of policy 6.8 (or 10.8): https://www.debian.org/doc/debian-policy/ch-maintainerscripts.html#s-removedetails Filing this as important as having a piuparts clean archive is a release goal since lenny. From the attached log (scroll to the bottom...): 0m38.1s ERROR: FAIL: Package purging left files on system: /etc/dnsmasq.d/dnsmasq.adblock.confnot owned /etc/dnsmasq.d/dnsmasq.trashsites.conf not owned cheers, andreas dbab_1.2.2-1.log.gz Description: application/gzip
Bug#773749: [pkg-dhcp-devel] Bug#773749: Bug#773749: isc-dhcp-client: no longer updates /etc/resolv.conf
Control: reassign -1 resolvconf Control: retitle -1 resolvconf prevents dhclient-script from updating /etc/resolv.conf On 2015-01-13 09:20:12 +0100, Vincent Lefevre wrote: On 2015-01-13 02:18:37 -0500, Michael Gilbert wrote: There are other programs that circumvent isc-dhcp to update /etc/resolv.conf like resolvconf and network manager. According to your setup, it sounds like wicd also has a corner case that also does that. No, that could be true only if /etc/resolv.conf were updated. But it wasn't. This means that wicd (or some other package) prevents dhclient from updating /etc/resolv.conf. Actually it seems that it is resolvconf that prevents dhclient from updating /etc/resolv.conf. According to the dhclient-script(8) man page, there may be hooks to change the default behavior by defining the shell function make_resolv_conf. And this is what resolvconf appears to do *unconditionally*. So, either resolvconf should make sure that /etc/resolv.conf is a symlink to /etc/resolvconf/run/resolv.conf, or it shouldn't modify the default behavior. -- Vincent Lefèvre vinc...@vinc17.net - Web: https://www.vinc17.net/ 100% accessible validated (X)HTML - Blog: https://www.vinc17.net/blog/ Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon) -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#774762: try harder to find reasons for failed `lvchange -an` by looking at /proc/*/mountinfo
On 01/13/2015 09:43 AM, chrysn wrote: I'd say the best who-uses tool in this case is lsblk [...] LVM itself already uses this tool within helper blkdeactivate script [...] so you see a chance that lvm could delegate the diagnoistic messages for where to find the offending mount point to lsblk (or dmsetup or findmnt, but lsblk is probably the most suitable of those)? if yes, i'd open a similar bug against util-linux (lsblk does not do any better than lvm in container conditions at the moment), and keep this only open to track lvm's progress on delegating to lsblk. We've recently opened an LVM2 upstream bug to check for holders across containers (https://bugzilla.redhat.com/show_bug.cgi?id=1181029). Still, this will just stop LVM from doing certain actions (this support in LVM will be only LVM specific for its own purposes if it detects the device is in use). But LVM itself won't provide you as much info here as lsblk could. So yes, I think lsblk should be enhanced here a bit as well to take containers more into account if it doesn't do so currently. This way more people can make use of this info and they won't need to look for it themselves in various places all around the system. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#775251: util-linux: Unexpected inconsistency, run fsck manually , but filesystem is already mounted
Package: util-linux Version: 2.25.2-4 Severity: normal Dear Maintainer, on boot system there is UNEXPECTED INCONSISTENCY and to run fsck manually, but i have to check root filesystem, so i write my root password and run fsck /dev/sda1 at prompt, but / is already mounted on /dev/sda1. I remember that this happened to me one or two years ago and then root filesystem wasn't mounted in maintanance mode. Thanks -- System Information: Debian Release: 8.0 APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Foreign Architectures: i386 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 util-linux depends on: ii initscripts2.88dsf-58 ii libblkid1 2.25.2-4 ii libc6 2.19-13 ii libmount1 2.25.2-4 ii libncurses55.9+20140913-1+b1 ii libpam0g 1.1.8-3.1 ii libselinux12.3-2 ii libslang2 2.3.0-2 ii libsmartcols1 2.25.2-4 ii libtinfo5 5.9+20140913-1+b1 ii libuuid1 2.25.2-4 ii lsb-base 4.1+Debian13+nmu1 ii tzdata 2014j-1 ii zlib1g 1:1.2.8.dfsg-2+b1 util-linux recommends no packages. Versions of packages util-linux suggests: ii dosfstools 3.0.27-1 ii kbd 1.15.5-2 ii util-linux-locales 2.25.2-4 -- debconf information: util-linux/noauto-with-nonzero-passnum: -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#775252: icinga-web-config-icinga2-ido-mysql, icinga-web-config-icinga2-ido-pgsql: fails to install: icinga2-enable-feature: command not found
Package: icinga-web-config-icinga2-ido-mysql,icinga-web-config-icinga2-ido-pgsql Version: 1.11.2+dfsg1-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 icinga-web-config-icinga2-ido-mysql. (Reading database ... 19829 files and directories currently installed.) Preparing to unpack .../icinga-web-config-icinga2-ido-mysql_1.11.2+dfsg1-1_all.deb ... Unpacking icinga-web-config-icinga2-ido-mysql (1.11.2+dfsg1-1) ... Setting up icinga-web-config-icinga2-ido-mysql (1.11.2+dfsg1-1) ... Configuration IDO database for the MySQL IDO of Icinga 2... Creating config file /etc/icinga-web/conf.d/database-ido.xml with new version database config successful: /etc/icinga-web/conf.d/database-ido.xml enabling icinga2 features for classicui /var/lib/dpkg/info/icinga-web-config-icinga2-ido-mysql.postinst: line 33: icinga2-enable-feature: command not found dpkg: error processing package icinga-web-config-icinga2-ido-mysql (--configure): subprocess installed post-installation script returned error exit status 127 Errors were encountered while processing: icinga-web-config-icinga2-ido-mysql Selecting previously unselected package icinga-web-config-icinga2-ido-pgsql. (Reading database ... 20687 files and directories currently installed.) Preparing to unpack .../icinga-web-config-icinga2-ido-pgsql_1.11.2+dfsg1-1_all.deb ... Unpacking icinga-web-config-icinga2-ido-pgsql (1.11.2+dfsg1-1) ... Setting up icinga-web-config-icinga2-ido-pgsql (1.11.2+dfsg1-1) ... Configuration IDO database for the PostgreSQL IDO of Icinga 2... Creating config file /etc/icinga-web/conf.d/database-ido.xml with new version database config successful: /etc/icinga-web/conf.d/database-ido.xml enabling icinga2 features for classicui /var/lib/dpkg/info/icinga-web-config-icinga2-ido-pgsql.postinst: line 33: icinga2-enable-feature: command not found dpkg: error processing package icinga-web-config-icinga2-ido-pgsql (--configure): subprocess installed post-installation script returned error exit status 127 Errors were encountered while processing: icinga-web-config-icinga2-ido-pgsql cheers, Andreas icinga-web-config-icinga2-ido-mysql_1.11.2+dfsg1-1.log.gz Description: application/gzip
Bug#608457: systemd sometimes forgets to properly setup Terminus console font
On Mon, 3 Nov 2014 10:41:02 +0100 Karsten Hilbert karsten.hilb...@gmx.net wrote: This problem hasn't happened for a while anymore. Unfortunately it happens all the time for me. I have to manually run `setupcon --save' each time when I switch to a text console on a freshly booted jessie system in order to get the right screen font back. Thanks, /mjt -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#775207: boinc-client: add exclusive application for gpu
Hi Alessandro, quoting upstream [1]: Suspend processor and network usage when these applications are running: When programs in this list are detected in memory, BOINC will stop working on them. A separate option to stop working on the GPU only, but allow work on the CPU to continue, will come in a future version. Until that time you will have to hand edit the cc_config.xml file and use the exclusive_gpu_app/ flag for that. [1] http://boinc.berkeley.edu/wiki/Local_preferences#Exclusive_applications So I guess we just need to wait! cheers, G. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#775181: x265-10bit doesn't work
Am Montag, den 12.01.2015, 17:53 +0100 schrieb Sebastian Ramacher: To me it looks like the check in the x265 should just check against x265_max_bit_depth. Maybe something like the following patch could be used instead of shipping two binaries that only differ in this check. Nevertheless, the 8-bit binary would not work with the 10-bit library, right? - Fabian -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#768406: e2fsprogs: e2fsck refuses to check umounted filesystems
Control: reassign 767468 cgmanager Control: merge -1 767468 The net effect is that if you start cgmanager, since it create a separate mount namespace, any file systems which are mounted at the time when cgmanager is started will still be mounted in the cgmanager namespace: Which perfectly explains why cgmanager renders autofs almost unusable. Thanks for the clarification. Reassigning the bug from autofs to cgmanager. I wonder what other packages are broken by this as well. Adrian -- .''`. 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#773749: [pkg-dhcp-devel] Bug#773749: Bug#773749: isc-dhcp-client: no longer updates /etc/resolv.conf
Control: tag -1 - moreinfo unreproducible Hi Vincent, Vincent Lefevre wrote: Actually it seems that it is resolvconf that prevents dhclient from updating /etc/resolv.conf. Thanks, that explains well why neither Michael nor me were able to reproduce the issue. I'm hence removing the according tags. Regards, Axel -- ,''`. | Axel Beckert a...@debian.org, http://people.debian.org/~abe/ : :' : | Debian Developer, ftp.ch.debian.org Admin `. `' | 4096R: 2517 B724 C5F6 CA99 5329 6E61 2FF9 CD59 6126 16B5 `-| 1024D: F067 EA27 26B9 C3FC 1486 202E C09E 1D89 9593 0EDE -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#775280: unblock: designate/2014.1-18
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: unblock
Dear release team,
Here's the changes:
*/ Package is rebuilt against openstack-pkg-tools = 22~ to fix the
last systemd issue that was preventing startup of daemons on the first
install (see unblock bug #775278).
*/ To make sure the database directive is left unchanged unless the
user explicitely asked for automated management, and for consistency
across all OpenStack packages, the designate/configure_db debconf
directive default value is now set to false.
*/ For consistency with other OpenStack packages and to allow a better
compatibility with official puppet scripts, the postinst doesn't touch
the db connection directive and doesn't do the designate-manage
database-init and designate-manage database-sync unless explicitely
requested by the user through debconf. The pkgos_dbc_postinst isn't
called either if no db management is requested.
*/ For some reason, the database initialization was depending on the
dbc_upgrade variable, which is wrong: we really want the database to
be initialized at install time if designate/configure_db is true. This
upload corrects that too.
Please unblock designate/2014.1-18. Debdiff attached.
Cheers,
Thomas Goirand (zigo)
P.S: Please note that I only generate debdiff for the changes which
haven't been agreed on previously.
diff -Nru designate-2014.1/debian/changelog designate-2014.1/debian/changelog
--- designate-2014.1/debian/changelog 2015-01-05 22:07:05.0 +
+++ designate-2014.1/debian/changelog 2015-01-09 00:17:00.0 +
@@ -1,3 +1,17 @@
+designate (2014.1-18) unstable; urgency=medium
+
+ * Removed dbc_upgrade = true check before db sync.
+
+ -- Thomas Goirand z...@debian.org Fri, 09 Jan 2015 00:16:40 +
+
+designate (2014.1-17) unstable; urgency=medium
+
+ * Rebuilt with openstack-pkg-tools (= 22~): starts daemons on first install.
+ * designate/configure_db default value is now false.
+ * Do not call pkgos_dbc_postinst if designate/configure_db is false.
+
+ -- Thomas Goirand z...@debian.org Thu, 08 Jan 2015 15:49:46 +
+
designate (2014.1-16) unstable; urgency=medium
* Fixed homepage: stackforge - openstack.
diff -Nru designate-2014.1/debian/control designate-2014.1/debian/control
--- designate-2014.1/debian/control 2015-01-05 22:07:05.0 +
+++ designate-2014.1/debian/control 2015-01-09 00:17:00.0 +
@@ -7,7 +7,7 @@
Mehdi Abaakouk sil...@sileht.net
Build-Depends: debhelper (= 9),
dh-systemd,
- openstack-pkg-tools (= 21~),
+ openstack-pkg-tools (= 22~),
python-all (= 2.6.6-3~),
python-pbr (=0.6),
python-setuptools,
diff -Nru designate-2014.1/debian/designate-common.postinst.in designate-2014.1/debian/designate-common.postinst.in
--- designate-2014.1/debian/designate-common.postinst.in 2015-01-05 22:07:05.0 +
+++ designate-2014.1/debian/designate-common.postinst.in 2015-01-09 00:17:00.0 +
@@ -13,12 +13,15 @@
pkgos_var_user_group designate
pkgos_write_new_conf designate designate.conf
- pkgos_dbc_postinst ${CONF} storage:sqlalchemy database_connection designate $@
+ db_get designate/configure_db
+ if [ $RET = true ] ; then
+ pkgos_dbc_postinst ${CONF} storage:sqlalchemy database_connection designate $@
+ fi
pkgos_rabbit_write_conf ${CONF} DEFAULT designate
pkgos_write_admin_creds ${CONF} keystone_authtoken designate
db_get designate/configure_db
- if [ $RET = true ] [ $dbc_upgrade = true ] ; then
+ if [ $RET = true ] ; then
echo Now doing designate-manage database-sync: this may take a while...
su -s /bin/sh -c 'cd /tmp designate-manage database-init' designate || true
su -s /bin/sh -c 'cd /tmp designate-manage database-sync' designate
diff -Nru designate-2014.1/debian/designate-common.templates designate-2014.1/debian/designate-common.templates
--- designate-2014.1/debian/designate-common.templates 2015-01-05 22:07:05.0 +
+++ designate-2014.1/debian/designate-common.templates 2015-01-09 00:17:00.0 +
@@ -9,7 +9,7 @@
Template: designate/configure_db
Type: boolean
-Default: true
+Default: false
_Description: Set up a database for Designate?
No database has been set up for designate to use. Before continuing, you
should make sure you have the following information:
Bug#775281: raddb_dir is /etc/freeradius, not /etc/raddb
Package: freeradius Version: 2.1.12+dfsg-1.2 Severity: normal Dear maintainer, Unlike the manpage indicates, the default config files is searched in /etc/freeradius: # /usr/sbin/freeradius --help ... -d raddb_dirConfiguration files are in raddbdir/*. -n name Read raddb/name.conf instead of raddb/radiusd.conf ... # man freeradius |grep -A1 'config direc' -d config directory Defaults to /etc/raddb. Radiusd looks here for its configuration files such as the dictionary and the users files. # rm -f /etc/freeradius/radiusd.conf # /usr/sbin/freeradius -X -f ... including configuration file /etc/freeradius/radiusd.conf Unable to open file /etc/freeradius/radiusd.conf: No such file or directory Errors reading /etc/freeradius/radiusd.conf ... # The documentation inside the package should refer to the actual config file path(s) that are used in this installtion. Best, Kilian -- System Information: Debian Release: 7.8 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 3.2.0-4-amd64 (SMP w/1 CPU core) Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8) (ignored: LC_ALL set to de_DE.UTF-8) Shell: /bin/sh linked to /bin/dash signature.asc Description: Digital signature
Bug#770834: pulseaudio: MacBook 13/2013: Only silence in microphone input (not muted)
Control: tags -1 moreinfo Hi Lucas, On Mon, Nov 24, 2014 at 10:55 AM, Lukas F. Hartmann lu...@mnt.mn wrote: Package: pulseaudio Version: 5.0-13 Severity: normal Dear Maintainer, I am running Debian Jessie on a MacBook Pro Retina 13 from 2103. Audio works fine except for microphone input, which always stays silent, regardless of mu ting/unmuting or volume settings or fiddling with alsamixer. The pavucontrol vumeter for Input Devices Built-in Audio Analog Stereo Port:Internal Microphone stays in a zero state. Alsamixer shows two Microphone capture devices (Internal Microphone and Internal Microphone 1) while pavucontrol shows one stereo device. When I press space on Internal microphone 1, the input in pavucontrol appears muted. When I unmute it, the volume meter is at 100% for a fraction of a second and then goes down to zero. If I record directly after switching to Internal Microphone 1, only a single plop noise is recorded and then silence. This does not happen for Internal Microphone where only silence is recorded. I would expect to see a working volume meter when enabling the microphone in pavucontrol and to have working audio recording in client tools such as audaci ty. I'm sorry I haven't been able to look into this. Could you try the version of pulseaudio in experimental (5.99) and see if that works? If not, please attach a verbose log[1] of pulseaudio when reproducing the problem, and noting approximately when you did what (eg: approx 5 seconds after starting pa, I started pavucontrol, then muted the input...). [1] https://wiki.ubuntu.com/PulseAudio/Log -- Saludos, Felipe Sateler -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#775282: unblock: keystone/2014.1.3-6
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: unblock
Dear release team,
Here's a list of changes:
*/ For some reason, the database initialization was depending on the
dbc_upgrade variable, which is wrong: we really want the database to
be initialized at install time if keystone/configure_db is true. This
upload corrects that too. This fixes bug #767715 with the
openstack-deploy script / package where Keystone was failing to start
and therefore destroying all subsequent automated installation (with
an error 500 when trying to use the daemon).
*/ The deb-systemd-helper unmask is now called before the invoke-rc.d
so that the daemon starts when the package is installed if we're using
systemd.
Note that, to the contrary of other OpenStack packages, Keystone is not
using #DEBHELPER# in its postinst and daemon startup / management is
done by hand, so that OpenStack tenant and endpoints can be created
once Keystone is started. Therefore, Keystone doesn't need to build-
depends on openstack-pkg-tools = 22~ (version 21 is fine).
Please unblock package keystone/2014.1.3-6. Debdiff attached.
Cheers,
Thomas Goirand (zigo)
diff -Nru keystone-2014.1.3/debian/changelog keystone-2014.1.3/debian/changelog
--- keystone-2014.1.3/debian/changelog 2015-01-06 20:27:39.0 +
+++ keystone-2014.1.3/debian/changelog 2015-01-09 00:29:34.0 +
@@ -1,3 +1,11 @@
+keystone (2014.1.3-6) unstable; urgency=medium
+
+ * unmask systemd service before starting the init script / unit file.
+ * Removed dbc_upgrade = true check before pkgos_dbc_postinst and
+db_sync calls (Closes: #767715).
+
+ -- Thomas Goirand z...@debian.org Thu, 08 Jan 2015 23:05:48 +
+
keystone (2014.1.3-5) unstable; urgency=medium
* Fix cron job to not error after package removal (Closes: #773494).
diff -Nru keystone-2014.1.3/debian/keystone.postinst.in keystone-2014.1.3/debian/keystone.postinst.in
--- keystone-2014.1.3/debian/keystone.postinst.in 2015-01-06 20:27:39.0 +
+++ keystone-2014.1.3/debian/keystone.postinst.in 2015-01-09 00:29:34.0 +
@@ -86,7 +86,7 @@
# Upgrade or create the db if directed to do so
db_get keystone/configure_db
- if [ $RET = true ] [ $dbc_upgrade = true ] ; then
+ if [ $RET = true ] ; then
# Configure the SQL connection of keystone.conf according to dbconfig-common
pkgos_dbc_postinst ${KEY_CONF} database connection keystone $@
su keystone -c keystone-manage db_sync
@@ -97,6 +97,14 @@
# isn't a problem.
su keystone -c keystone-manage pki_setup
+ # Activate the keystone.service
+ deb-systemd-helper unmask keystone.service /dev/null || true
+ if deb-systemd-helper --quiet was-enabled keystone.service ; then
+ deb-systemd-helper enable keystone.service /dev/null || true
+ else
+ deb-systemd-helper update-state keystone.service /dev/null || true
+ fi
+
# Setup init script and start keystone
pkgos_init keystone
@@ -130,12 +138,4 @@
db_stop
fi
-# Activate the keystone.service
-deb-systemd-helper unmask keystone.service /dev/null || true
-if deb-systemd-helper --quiet was-enabled keystone.service ; then
- deb-systemd-helper enable keystone.service /dev/null || true
-else
- deb-systemd-helper update-state keystone.service /dev/null || true
-fi
-
exit 0
Bug#775286: eztrace: /usr/bin/eztrace not recording any event
Package: eztrace Version: 1.0.6-3 Severity: important Dear Maintainer, /usr/bin/eztrace is not recording any event whatever the plugin I enable and the executable I test. /usr/bin/eztrace.preload is recording well. I also built the upstream eztrace from source and find that the create eztrace executable is also recording well. Here is an execution log of eztrace and eztrace.preload on an apt-cache execution: test@debian:~$ export EZTRACE_TRACE=memory test@debian:~$ eztrace.preload apt-cache search eztrace Starting EZTrace... done [EZTrace] The buffer for recording events is full. Stop recording. The trace will be truncated libeztrace0-contrib - Automatic execution trace generation for HPC - development files eztrace - Automatic execution trace generation for HPC - tools libeztrace-dev - Automatic execution trace generation for HPC - development files libeztrace0 - Automatic execution trace generation for HPC - development files [EZTrace] The buffer for recording events is full. Stop recording. The trace will be truncated Stopping EZTrace... saving trace /tmp/test_eztrace_log_rank_1 test@debian:~$ eztrace_stats /tmp/test_eztrace_log_rank_1 setting output dir to /tmp/eztrace_stats_test module memory loaded 1 modules loaded setting output dir to /tmp/eztrace_stats_test no more block for trace #0 MEMORY: --- CT_Process #0: 280069 malloc (total: 11803622 bytes) 279205 free (total: 8158381 bytes) maximum memory used: 3645258 bytes Total: 280069 malloc (total: 11803622 bytes) 279205 free (total: 8158381 bytes) maximum memory used: 3645258 bytes PTHREAD_CORE 559229 events handled test@debian:~$ eztrace apt-cache search eztrace Starting EZTrace... done libeztrace0-contrib - Automatic execution trace generation for HPC - development files eztrace - Automatic execution trace generation for HPC - tools libeztrace-dev - Automatic execution trace generation for HPC - development files libeztrace0 - Automatic execution trace generation for HPC - development files Stopping EZTrace... saving trace /tmp/test_eztrace_log_rank_1 test@debian:~$ eztrace_stats /tmp/test_eztrace_log_rank_1 setting output dir to /tmp/eztrace_stats_test module memory loaded 1 modules loaded setting output dir to /tmp/eztrace_stats_test no more block for trace #0 MEMORY: --- No p_info for CT_Process #0 Total: 0 malloc (total: 0 bytes) 0 free (total: 0 bytes) maximum memory used: 0 bytes PTHREAD_CORE 0 events handled -- System Information: Debian Release: 8.0 APT prefers testing APT policy: (900, 'testing'), (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.16.0-4-amd64 (SMP w/24 CPU cores) Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages eztrace depends on: ii libc6 2.19-13 ii libeztrace0 1.0.6-3 ii libgtg0 0.2-2+dfsg-1 ii liblitl0 0.1.5+dfsg-2 ii opari2 1.0.7+dfsg-5 ii zlib1g 1:1.2.8.dfsg-2+b1 eztrace recommends no packages. eztrace 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#775279: unblock: cinder/2014.1.3-11
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: unblock
Dear release team,
The last 3 uploads of Cinder to Sid are correcting a few issues.
1/ Package is rebuilt against openstack-pkg-tools = 22~ to fix the
last systemd issue that was preventing startup of daemons on the first
install (see unblock bug #775278).
2/ For consistency with other OpenStack packages and to allow a better
compatibility with official puppet scripts, the postinst doesn't touch
the db connection directive and doesn't do the cinder-manage db sync
unless explicitely requested by the user through debconf.
3/ The package wasn't updated to use the correct database connection
directive, so version 2014.1.3-11 corrects that.
Please unblock cinder/2014.1.3-11, debdiff attached.
Cheers,
Thomas Goirand (zigo)
P.S: Please note that I only generate debdiff for the changes which
haven't been agreed on previously.
diff -Nru cinder-2014.1.3/debian/changelog cinder-2014.1.3/debian/changelog
--- cinder-2014.1.3/debian/changelog 2015-01-05 16:39:26.0 +
+++ cinder-2014.1.3/debian/changelog 2015-01-13 11:09:59.0 +
@@ -1,3 +1,23 @@
+cinder (2014.1.3-11) unstable; urgency=medium
+
+ * Using the correct [database]/connection directive instead of the deprecated
+one.
+
+ -- Thomas Goirand z...@debian.org Tue, 13 Jan 2015 12:08:22 +0100
+
+cinder (2014.1.3-10) unstable; urgency=medium
+
+ * Calling pkgos_dbc_postinst and cinder-manage db sync only if
+cinder/configure_db is set to true.
+
+ -- Thomas Goirand z...@debian.org Thu, 08 Jan 2015 16:14:50 +
+
+cinder (2014.1.3-9) unstable; urgency=medium
+
+ * Rebuilt with openstack-pkg-tools (= 22~): starts daemons on first install.
+
+ -- Thomas Goirand z...@debian.org Thu, 08 Jan 2015 15:45:52 +
+
cinder (2014.1.3-8) unstable; urgency=medium
* Rebuild against openstack-pkg-tools = 21~ to fix sysv-rc init scripts.
diff -Nru cinder-2014.1.3/debian/cinder-common.config.in cinder-2014.1.3/debian/cinder-common.config.in
--- cinder-2014.1.3/debian/cinder-common.config.in 2015-01-05 16:39:26.0 +
+++ cinder-2014.1.3/debian/cinder-common.config.in 2015-01-13 11:09:59.0 +
@@ -8,7 +8,7 @@
#PKGOS-INCLUDE#
pkgos_var_user_group cinder
-pkgos_dbc_read_conf -pkg cinder-common ${CINDER_CONF} DEFAULT sql_connection cinder $@
+pkgos_dbc_read_conf -pkg cinder-common ${CINDER_CONF} database connection cinder $@
pkgos_rabbit_read_conf ${CINDER_CONF} DEFAULT cinder
pkgos_read_admin_creds ${CINDER_CONF} keystone_authtoken cinder
diff -Nru cinder-2014.1.3/debian/cinder-common.postinst.in cinder-2014.1.3/debian/cinder-common.postinst.in
--- cinder-2014.1.3/debian/cinder-common.postinst.in 2015-01-05 16:39:26.0 +
+++ cinder-2014.1.3/debian/cinder-common.postinst.in 2015-01-13 11:09:59.0 +
@@ -21,7 +21,10 @@
pkgos_write_new_conf cinder cinder.conf
pkgos_write_new_conf cinder api-paste.ini
pkgos_write_new_conf cinder logging.conf
- pkgos_dbc_postinst ${CINDER_CONF} DEFAULT sql_connection cinder $@
+ db_get cinder/configure_db
+ if [ $RET = true ]; then
+ pkgos_dbc_postinst ${CINDER_CONF} database connection cinder $@
+ fi
pkgos_rabbit_write_conf ${CINDER_CONF} DEFAULT cinder
pkgos_write_admin_creds ${CINDER_CONF} keystone_authtoken cinder
db_get cinder/volume_group
@@ -29,11 +32,13 @@
pkgos_inifile set ${CINDER_CONF} DEFAULT volume_group ${RET}
fi
- db_stop
-
chmod 0440 /etc/sudoers.d/cinder-common
- echo Now calling cinder-manage db sync: this may take a while...
- su -s /bin/sh -c 'cinder-manage db sync' cinder
+ db_get cinder/configure_db
+ if [ $RET = true ]; then
+ echo Now calling cinder-manage db sync: this may take a while...
+ su -s /bin/sh -c 'cinder-manage db sync' cinder
+ fi
+ db_stop
fi
#DEBHELPER#
diff -Nru cinder-2014.1.3/debian/control cinder-2014.1.3/debian/control
--- cinder-2014.1.3/debian/control 2015-01-05 16:39:26.0 +
+++ cinder-2014.1.3/debian/control 2015-01-13 11:09:59.0 +
@@ -6,7 +6,7 @@
Gustavo Panizzo g...@zumbi.com.ar
Build-Depends: debhelper (= 9),
dh-systemd,
- openstack-pkg-tools (= 21~),
+ openstack-pkg-tools (= 22~),
po-debconf,
python-all (= 2.6.6-3~),
python-pbr (= 0.6),
Bug#773256: dbus + triggers + apt issue (was: Bug#773256: pre-approval: unblock: dpkg/1.17.23)
On Thu, Jan 08, 2015 at 02:47:05AM +0100, Guillem Jover wrote:
[ @deity: please check out the dbus issue below. ]
[..]
[ Re dbus issue ]
Noted. Do we (still?) have a (reliable) way of reproducing the dbus
trigger issue?
We didn't up to now (AFAIK), but there's now very valuable data from
Karl Ljungkvist at #774124. I've been able to reproduce the issue with
that status file and apt (over a clean debootstrap of jessie, and
adding i386 as a foreign arch).
Thanks for pointing us towards this bugreport, this contains some good
information. I followed up there with some more questions, it would be
really nice to be able to reproduce what error happend that caused
this broken state.
And have been trying out several things:
* It seems to affect both apt from jessie/sid and wheezy. :(
apt gets into a state it cannot recover from by itself.
Indeed, apt sees the triggers-pending and triggers-awaited state
and tries to run dpkg --configure on all those packages. This
fails.
* «dpkg --configure --pending» solves the issue.
* Using dpkg --force-configure-any only fixes the issue partially, :(
because apt does not notice that the package has been implicitly
configured, and tries to configure the package again and dpkg exits
with an error for that run, which apt does not like much either (as
I feared). So I'd need to also change dpkg to not fail configuring
an already configure package, or try to detect that specific case.
When you say implicitly configured what does that mean exactly? Is
the issue here that apt should ignore the triggers-awaited state
because those will be dealt with by dpkg entirely?
I also wonder if there are further implications for apt by the trigger
changes. The ordering code in apt builds on the premise that there is
no implict configuration, it builds the unpack/configure ordering
early and its static. Is this still a valid assumption?
[..]
Before considering either reverting, or trying to find a workaround
for this in dpkg, I'd like to know if this is easily fixable in apt
and the implications of this problem (i.e. can it affect similar
situations regardless of the recent dpkg trigger changes?) and the
implications of such a fix.
We have code in pkgApplyStatus that detects and fixes not-ok
packages. So far it considered packages with
triggers-{pending,awaited} as something to just dpkg --configure. We
could change the code to ignore those states and simply let dpkg
handle them (via Davids code that ensures 'dpkg --configure -a' gets
called). Does that sound sensible?
I'm still a bit nervous about the issue that lead to #774124. It would
be good to get more data here.
Cheers,
Michael
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#766726: Assistance
On Mon, Jan 12, 2015 at 9:41 AM, Justin Zobel justin.zo...@gmail.com wrote: Hi Leo, I'm currently running Budgie-Desktop on Debian and I've just enabled and used the workspace switcher without issues. I'm on Debian 8 (Jessie) with GTK3.14.5 (current in repo). Then, please start working on packaging! Where do you experience this freezing? As I said: you have to switch between workspaces and windows (iconified and maximized). At some point the wm crashes. signature.asc Description: GooPG digital signature
Bug#775258: dpkg-dev: dpkg-shlibdeps doesn't pass admindir parameter to nested dpkg --search
On Tue, 2015-01-13 at 09:09:29 -0500, Lukasz Jagielski wrote:
On Tue, Jan 13, 2015 at 8:17 AM, Guillem Jover guil...@debian.org wrote:
But in any case I don't think that using a different admindir is
something really supported in normal packaging.
My use case is i686 package compiled using sysroot on amd64 system, I
want to use the same sysroot for deb generation.
If this is for your own packages then sure, my comment above was for
normal Debian packages, as there's no easy way to pass global arguments
to the dpkg commands inside say debian/rules.
Here's a patch that works for me http://pastebin.com/6mfeVgKc
Thanks, I had fixed it differently though, with the attached patch.
Which will be pushing quickly to master.
Thanks,
Guillem
From a43c0dee759079e50bad4d6c9c5b5b15408afe6e Mon Sep 17 00:00:00 2001
From: Guillem Jover guil...@debian.org
Date: Tue, 13 Jan 2015 14:20:04 +0100
Subject: [PATCH] dpkg-shlibdeps: Use dpkg-query instead of dpkg for --search
This has the effect of honoring the admindir passed as an environment
variable, as dpkg sets the variable unconditionally, but dpkg-query
does honor it.
Closes: #775258
---
scripts/dpkg-shlibdeps.pl | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/scripts/dpkg-shlibdeps.pl b/scripts/dpkg-shlibdeps.pl
index 57e6a76..520b24f 100755
--- a/scripts/dpkg-shlibdeps.pl
+++ b/scripts/dpkg-shlibdeps.pl
@@ -838,14 +838,14 @@ sub find_packages {
return $pkgmatch unless scalar(@files);
my $pid = open(my $dpkg_fh, '-|');
-syserr(g_('cannot fork for %s'), 'dpkg --search') unless defined($pid);
+syserr(g_('cannot fork for %s'), 'dpkg-query --search') unless defined $pid;
if (!$pid) {
# Child process running dpkg --search and discarding errors
close STDERR;
open STDERR, '', '/dev/null'
or syserr(g_('cannot open file %s'), '/dev/null');
$ENV{LC_ALL} = 'C';
- exec('dpkg', '--search', '--', @files)
+ exec 'dpkg-query', '--search', '--', @files
or syserr(g_('unable to execute %s'), 'dpkg');
}
while ($dpkg_fh) {
--
2.2.1.209.g41e5f3a
Bug#775284: RFS: linuxptp/1.5-1
Package: sponsorship-requests Severity: wishlist Dear mentors, I am looking for a sponsor for my package linuxptp Package name: linuxptp Version : 1.5-1 Upstream Author : Richard Cochran richardcoch...@gmail.com URL : http://linuxptp.sourceforge.net/ License : GPL-2+ Section : utils It builds those binary packages: linuxptp - Precision Time Protocol (PTP, IEEE1588) implementation for Linux To access further information about this package, please visit the following URL: http://mentors.debian.net/package/linuxptp Alternatively, one can download the package with dget using this command: dget -x http://mentors.debian.net/debian/pool/main/l/linuxptp/linuxptp_1.5-1.dsc More information about LinuxPTP can be obtained from http://linuxptp.sourceforge.net/ Regards, Tino Mettler -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#698375: gfs2-utils: fails to upgrade from wheezy: insserv: script gfs2-utils: service gfs2 already provided!
Hi Andreas, On Sat, Jan 10, 2015 at 12:37:55PM +0100, Andreas Beckmann wrote: Followup-For: Bug #698375 Hi, adjusted Salvatore's patch to also run dpkg-maintscript-helper rm_conffile on initial package install. Verified that the upgrade path works. NMU uploaded to DELAYED/2. Thanks for your work on this issue. Regards, Salvatore -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#740678: O: abiword -- efficient, featureful word processor with collaboration
Not ready yet, I need a few more days.
Bug#775287: unblock: glance/2014.1.3-10
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: unblock
Dear release team,
Here is the list of changes.
*/ Package is rebuilt against openstack-pkg-tools = 22~ to fix the
last systemd issue that was preventing startup of daemons on the first
install (see unblock bug #775278).
*/ To make sure the database directive is left unchanged unless the
user explicitely asked for automated management, and for consistency
across all OpenStack packages, the designate/configure_db debconf
directive default value is now set to false.
*/ For consistency with other OpenStack packages and to allow a better
compatibility with official puppet scripts, the postinst doesn't touch
the db connection directive and doesn't do the designate-manage
database-init and designate-manage database-sync unless explicitely
requested by the user through debconf. The pkgos_dbc_postinst isn't
called either if no db management is requested.
*/ For some reason, the database initialization was depending on the
dbc_upgrade variable, which is wrong: we really want the database to
be initialized at install time if designate/configure_db is true. This
upload corrects that too.
Please unblock glance/2014.1.3-10. Debdiff attached.
Cheers,
Thomas Goirand (zigo)
P.S: Please note that I only generate debdiff for the changes which
haven't been agreed on previously.
diff -Nru glance-2014.1.3/debian/changelog glance-2014.1.3/debian/changelog
--- glance-2014.1.3/debian/changelog 2015-01-05 21:57:57.0 +
+++ glance-2014.1.3/debian/changelog 2015-01-09 00:21:39.0 +
@@ -1,3 +1,23 @@
+glance (2014.1.3-10) unstable; urgency=medium
+
+ * Removed dbc_upgrade = true check before db_sync.
+
+ -- Thomas Goirand z...@debian.org Fri, 09 Jan 2015 00:21:14 +
+
+glance (2014.1.3-9) unstable; urgency=medium
+
+ * Calls pkgos_dbc_postinst only if glance/configure_db is set to true (ie:
+only if user asked for db handling).
+ * Sets glance/configure_db to false by default.
+
+ -- Thomas Goirand z...@debian.org Thu, 08 Jan 2015 16:22:27 +
+
+glance (2014.1.3-8) unstable; urgency=medium
+
+ * Rebuilt with openstack-pkg-tools (= 22~): starts daemons on first install.
+
+ -- Thomas Goirand z...@debian.org Thu, 08 Jan 2015 15:51:51 +
+
glance (2014.1.3-7) unstable; urgency=medium
* Build-depends on openstack-pkg-tools (= 21~) to ensure we have the
diff -Nru glance-2014.1.3/debian/control glance-2014.1.3/debian/control
--- glance-2014.1.3/debian/control 2015-01-05 21:57:57.0 +
+++ glance-2014.1.3/debian/control 2015-01-09 00:21:39.0 +
@@ -5,7 +5,7 @@
Uploaders: Thomas Goirand z...@debian.org
Build-Depends: debhelper (= 9),
dh-systemd,
- openstack-pkg-tools (= 21~),
+ openstack-pkg-tools (= 22~),
po-debconf,
python-all (= 2.6.6-3~),
python-pbr (= 0.6),
diff -Nru glance-2014.1.3/debian/glance-common.postinst.in glance-2014.1.3/debian/glance-common.postinst.in
--- glance-2014.1.3/debian/glance-common.postinst.in 2015-01-05 21:57:57.0 +
+++ glance-2014.1.3/debian/glance-common.postinst.in 2015-01-09 00:21:39.0 +
@@ -38,7 +38,10 @@
pkgos_write_new_conf glance policy.json
# Do the db creation using dbconfig-common
- pkgos_dbc_postinst ${API_CONF} database connection glance $@
+ db_get glance/configure_db
+ if [ $RET = true ] ; then
+ pkgos_dbc_postinst ${API_CONF} database connection glance $@
+ fi
# Convert tables into utf8 if we're upgrading from prior to Icehouse.
db_get glance/configure_db
@@ -63,7 +66,7 @@
# Upgrade or create the db if directed to do so
db_get glance/configure_db
- if [ $RET = true ] [ $dbc_upgrade = true ] ; then
+ if [ $RET = true ] ; then
echo Now doing glance-manage db_sync: this may take a while...
su glance -c glance-manage db_sync || true
fi
diff -Nru glance-2014.1.3/debian/glance-common.templates glance-2014.1.3/debian/glance-common.templates
--- glance-2014.1.3/debian/glance-common.templates 2015-01-05 21:57:57.0 +
+++ glance-2014.1.3/debian/glance-common.templates 2015-01-09 00:21:39.0 +
@@ -52,7 +52,7 @@
Template: glance/configure_db
Type: boolean
-Default: true
+Default: false
_Description: Set up a database for Glance?
No database has been set up for glance-registry or glance-api to use. Before
continuing, you should make sure you have the following information:
Bug#775285: unblock: maildrop/2.7.1-3
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: unblock
Hi release team.
This is preapproval request.
The last upload of maildrop 2.7.1-2 just before the freeze removed
upstream unsupported dovocet auth patch to reduce security risk
exposure. In this upload, I also dropped upstream supported
courier-auth support by removing build-depends and depends for it. This
causes problem as reported to https://bugs.debian.org/774598
I would like to upload 2.7.1-3 with the following patch to fix this
regression. Without this fix, people upgrading from wheezy to jessie
will face regression if courier auth is used by the user.
$ git diff HEAD^
diff --git a/debian/changelog b/debian/changelog
index 1e35582..60e0773 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,10 @@
+maildrop (2.7.1-3) unstable; urgency=medium
+
+ * Fix regression in 2.7.1-2 by reactivating support for
+the courier-authlib itself. Closes: #774598
+
+ -- Osamu Aoki os...@debian.org Tue, 13 Jan 2015 23:14:59 +0900
+
maildrop (2.7.1-2) unstable; urgency=medium
* Drop dovocet patch. (No more upstream activity.) Closes: #692519
diff --git a/debian/control b/debian/control
index 340d41b..bea07e8 100644
--- a/debian/control
+++ b/debian/control
@@ -7,6 +7,7 @@ Standards-Version: 3.9.5
Build-Depends: autoconf,
automake,
autotools-dev,
+ courier-authlib-dev (= 0.58-4),
debhelper (= 9),
dh-autoreconf,
libgdbm-dev,
@@ -20,7 +21,7 @@ Vcs-Browser:
http://anonscm.debian.org/gitweb/?p=collab-maint/maildrop.git
Package: maildrop
Architecture: any
-Depends: ${misc:Depends}, ${shlibs:Depends}
+Depends: courier-authlib, ${misc:Depends}, ${shlibs:Depends}
Recommends: exim4 | mail-transport-agent
Breaks: suidmanager ( 0.50)
Replaces: courier-base (= 0.58.0-1)
unblock maildrop/2.7.1-3
-- System Information:
Debian Release: 8.0
APT prefers testing-updates
APT policy: (500, 'testing-updates'), (500, 'testing')
Architecture: amd64 (x86_64)
Kernel: Linux 3.16.0-4-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#775288: unblock: openstack-trove/2014.1.3-7
Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: unblock Dear release team, Here's a list of changes: */ Package is rebuilt against openstack-pkg-tools = 22~ to fix the last systemd issue that was preventing startup of daemons on the first install (see unblock bug #775278). */ To make sure the database directive is left unchanged unless the user explicitely asked for automated management, and for consistency across all OpenStack packages, the trove/configure_db debconf variable default value is now set to false. */ For consistency with other OpenStack packages and to allow a better compatibility with official puppet scripts, the postinst doesn't touch the db connection directive and doesn't do the trove-manage db_sync unless explicitely requested by the user through debconf. The pkgos_dbc_postinst isn't called either if no db management is requested. Please unblock package openstack-trove/2014.1.3-7. Debdiff attached. Cheers, Thomas Goirand (zigo) P.S: Please note that I only generate debdiff for the changes which haven't been agreed on previously. diff -Nru openstack-trove-2014.1.3/debian/changelog openstack-trove-2014.1.3/debian/changelog --- openstack-trove-2014.1.3/debian/changelog 2015-01-07 00:05:15.0 + +++ openstack-trove-2014.1.3/debian/changelog 2015-01-08 16:54:35.0 + @@ -1,3 +1,18 @@ +openstack-trove (2014.1.3-7) unstable; urgency=medium + + * Fixes nova/configure_db - trove/configure_db. + + -- Thomas Goirand z...@debian.org Thu, 08 Jan 2015 16:54:10 + + +openstack-trove (2014.1.3-6) unstable; urgency=medium + + * trove/configure_db is now false by default. + * Only runs pkgos_dbc_postinst and trove-manage db_sync if trove/configure_db +is true. + * Build-depends on openstack-pkg-tools (= 22~) to ensure correct init. + + -- Thomas Goirand z...@debian.org Thu, 08 Jan 2015 16:48:04 + + openstack-trove (2014.1.3-5) unstable; urgency=medium * Also purges /var/lib/trove when package is purged (Closes: #769771). diff -Nru openstack-trove-2014.1.3/debian/control openstack-trove-2014.1.3/debian/control --- openstack-trove-2014.1.3/debian/control 2015-01-07 00:05:15.0 + +++ openstack-trove-2014.1.3/debian/control 2015-01-08 16:54:35.0 + @@ -6,7 +6,7 @@ Thomas Goirand z...@debian.org, Mehdi Abaakouk sil...@sileht.net Build-Depends: debhelper (= 9), - openstack-pkg-tools (= 21~), + openstack-pkg-tools (= 22~), po-debconf, python-all (= 2.6.6-3~), python-pbr (= 0.6), diff -Nru openstack-trove-2014.1.3/debian/trove-common.postinst.in openstack-trove-2014.1.3/debian/trove-common.postinst.in --- openstack-trove-2014.1.3/debian/trove-common.postinst.in 2015-01-07 00:05:15.0 + +++ openstack-trove-2014.1.3/debian/trove-common.postinst.in 2015-01-08 16:54:35.0 + @@ -10,9 +10,15 @@ pkgos_var_user_group trove pkgos_write_new_conf trove trove.conf pkgos_write_new_conf trove api-paste.ini - pkgos_dbc_postinst /etc/trove/trove.conf DEFAULT sql_connection trove $@ + db_get trove/configure_db + if [ $RET = true ]; then + pkgos_dbc_postinst /etc/trove/trove.conf DEFAULT sql_connection trove $@ + fi pkgos_write_admin_creds /etc/trove/api-paste.ini filter:authtoken trove - trove-manage db_sync + db_get trove/configure_db + if [ $RET = true ]; then + trove-manage db_sync + fi db_stop fi diff -Nru openstack-trove-2014.1.3/debian/trove-common.templates openstack-trove-2014.1.3/debian/trove-common.templates --- openstack-trove-2014.1.3/debian/trove-common.templates 2015-01-07 00:05:15.0 + +++ openstack-trove-2014.1.3/debian/trove-common.templates 2015-01-08 16:54:35.0 + @@ -9,7 +9,7 @@ Template: trove/configure_db Type: boolean -Default: true +Default: false _Description: Set up a database for Trove? No database has been set up for trove to use. Before continuing, you should make sure you have the following information:
Bug#775225: work around : the crash seems to caused by the AMD fglrx driver and /usr/lib/libamdocl64.so
the crash seems to be caused by the AMD fglrx driver and /usr/lib/libamdocl64.so apt-get purge amd-opencl-icd solves the problem for code-aster I didn't check to see if anything else needed amd-opencl-icd is there anyway to force code aster and associated libraries to not use amd-opencl-icd ?
Bug#768245: opendnssec-enforcer-{sqlite3, mysql}: unhandled symlink to directory conversion: /usr/share/doc/PACKAGE
JFTR, my testing looks good: # ls -ld /usr/share/doc/opendnssec* drwxr-xr-x 2 root root 4096 Jan 13 13:41 /usr/share/doc/opendnssec drwxr-xr-x 2 root root 4096 Jan 13 13:41 /usr/share/doc/opendnssec-common drwxr-xr-x 5 root root 4096 Jan 13 13:36 /usr/share/doc/opendnssec-doc drwxr-xr-x 2 root root 4096 Jan 13 13:41 /usr/share/doc/opendnssec-enforcer drwxr-xr-x 2 root root 4096 Jan 13 13:41 /usr/share/doc/opendnssec-enforcer-sqlite3 drwxr-xr-x 2 root root 4096 Jan 13 13:41 /usr/share/doc/opendnssec-signer O. On Tue, Jan 13, 2015, at 14:52, Ondřej Surý wrote: 1:1.4.6-6 was uploaded right now. Please retest when you have a time and I will fill an unblock request. O. On Tue, Jan 13, 2015, at 14:49, Ondřej Surý wrote: Hi Andreas, oh my... Somehow I with the dh_installdoc --link-doc= was never introduced :). Building fixed package right now. I have tidied the others as well and bumped required dpkg to 1.17.14. O. On Tue, Jan 13, 2015, at 13:47, Andreas Beckmann wrote: Followup-For: Bug #768245 Control: found -1 1:1.4.6-5 Hi Ondrey, are you up for another iteration? The packages in wheezy-backports have yet another symlink - pointing to opendnssec-common (which was already once in your maintscripts, but we replaced it by another target). I think the approach of listing them all in the .maintscript should work here, too. (Don't forget the version bump to -6~ for the newly added ones). After an upgrade wheezy - wheezy-backports - jessie I get: 1m7.8s ERROR: FAIL: silently overwrites files via directory symlinks: /usr/share/doc/opendnssec-enforcer-sqlite3/NEWS.Debian.gz (opendnssec-enforcer-sqlite3) != /usr/share/doc/opendnssec-common/NEWS.Debian.gz (opendnssec-common) /usr/share/doc/opendnssec-enforcer-sqlite3 - opendnssec-common /usr/share/doc/opendnssec-enforcer-sqlite3/changelog.Debian.gz (opendnssec-enforcer-sqlite3) != /usr/share/doc/opendnssec-common/changelog.Debian.gz (opendnssec-common) /usr/share/doc/opendnssec-enforcer-sqlite3 - opendnssec-common /usr/share/doc/opendnssec-enforcer-sqlite3/changelog.gz (opendnssec-enforcer-sqlite3) != /usr/share/doc/opendnssec-common/changelog.gz (opendnssec-common) /usr/share/doc/opendnssec-enforcer-sqlite3 - opendnssec-common /usr/share/doc/opendnssec-enforcer-sqlite3/copyright (opendnssec-enforcer-sqlite3) != /usr/share/doc/opendnssec-common/copyright (opendnssec-common) /usr/share/doc/opendnssec-enforcer-sqlite3 - opendnssec-common 1m13.3s ERROR: FAIL: silently overwrites files via directory symlinks: /usr/share/doc/opendnssec-enforcer-mysql/NEWS.Debian.gz (opendnssec-enforcer-mysql) != /usr/share/doc/opendnssec-common/NEWS.Debian.gz (opendnssec-common) /usr/share/doc/opendnssec-enforcer-mysql - opendnssec-common /usr/share/doc/opendnssec-enforcer-mysql/changelog.Debian.gz (opendnssec-enforcer-mysql) != /usr/share/doc/opendnssec-common/changelog.Debian.gz (opendnssec-common) /usr/share/doc/opendnssec-enforcer-mysql - opendnssec-common /usr/share/doc/opendnssec-enforcer-mysql/changelog.gz (opendnssec-enforcer-mysql) != /usr/share/doc/opendnssec-common/changelog.gz (opendnssec-common) /usr/share/doc/opendnssec-enforcer-mysql - opendnssec-common /usr/share/doc/opendnssec-enforcer-mysql/copyright (opendnssec-enforcer-mysql) != /usr/share/doc/opendnssec-common/copyright (opendnssec-common) /usr/share/doc/opendnssec-enforcer-mysql - opendnssec-common There is also a file being left after purge: 1m18.8s INFO: Warning: Package purging left files on system: /etc/opendnssec/zonefetch.xmlnot owned Andreas Email had 1 attachment: + opendnssec-enforcer-sqlite3_1:1.4.6-5.log.gz 39k (application/gzip) -- Ondřej Surý ond...@sury.org Knot DNS (https://www.knot-dns.cz/) – a high-performance DNS server -- Ondřej Surý ond...@sury.org Knot DNS (https://www.knot-dns.cz/) – a high-performance DNS server -- Ondřej Surý ond...@sury.org Knot DNS (https://www.knot-dns.cz/) – a high-performance DNS server -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#775278: unblock: openstack-pkg-tools/22
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: unblock
Dear release team,
I'm sorry that I asked for a previous unblock of version 21 and had
to upload version 22, but another issue was found. Indeed, dh_installinit
must be called *after* dh_systemd_enable, otherwise the generated script
in the postinst is wrong, and the systemd unit is unmasked after
invoke-rc.d is called, resulting in the daemon not being started at the
install time (it is however started on next boot).
This is the only change in this version 22: dh_installinit is pushed
later on in the debian/rules include file.
I have rebuilt all OpenStack packages, however, only Nova and Ceilometer
are unchanged, so I'll open separate bugs for the other packages.
Note that I have run a full install test will all OpenStack packages, and
they installed without any issue (after a few more fixes), and I believe
that Andreas Beckman is running piuparts on all new upload to SID these
days. So this should hopefully be the last unblock serries for OpenStack.
Please unblock packages:
- openstack-pkg-tools/22
- nova/2014.1.3-9
- ceilometer/2014.1.3-6
Debdiffs attached.
Cheers,
Thomas Goirand (zigo)
diff -Nru nova-2014.1.3/debian/changelog nova-2014.1.3/debian/changelog
--- nova-2014.1.3/debian/changelog 2015-01-06 22:09:56.0 +
+++ nova-2014.1.3/debian/changelog 2015-01-08 16:07:07.0 +
@@ -1,3 +1,9 @@
+nova (2014.1.3-9) unstable; urgency=medium
+
+ * Rebuilt with openstack-pkg-tools (= 22~): starts daemons on first install.
+
+ -- Thomas Goirand z...@debian.org Thu, 08 Jan 2015 16:06:43 +
+
nova (2014.1.3-8) unstable; urgency=medium
* Rebuilt with openstack-pkg-tools (= 21~).
diff -Nru nova-2014.1.3/debian/control nova-2014.1.3/debian/control
--- nova-2014.1.3/debian/control 2015-01-06 22:09:56.0 +
+++ nova-2014.1.3/debian/control 2015-01-08 16:07:07.0 +
@@ -9,7 +9,7 @@
gustavo panizzo g...@zumbi.com.ar
Build-Depends: debhelper (= 9),
dh-systemd,
- openstack-pkg-tools (= 21~),
+ openstack-pkg-tools (= 22~),
po-debconf,
python-all (= 2.6.6-3~),
python-pbr (= 0.6),
diff -Nru openstack-pkg-tools-21/debian/changelog openstack-pkg-tools-22/debian/changelog
--- openstack-pkg-tools-21/debian/changelog 2015-01-05 15:48:09.0 +
+++ openstack-pkg-tools-22/debian/changelog 2015-01-08 15:13:03.0 +
@@ -1,3 +1,10 @@
+openstack-pkg-tools (22) unstable; urgency=medium
+
+ * Calls dh_installinit after dh_systemd_enable so that systemd services are
+started at install time.
+
+ -- Thomas Goirand z...@debian.org Thu, 08 Jan 2015 15:12:13 +
+
openstack-pkg-tools (21) unstable; urgency=medium
* Fixed mix-up with SYSTEM_USER and SYSTEM_GROUP in pkgos-gen-upstart-job.
diff -Nru openstack-pkg-tools-21/pkgos.make openstack-pkg-tools-22/pkgos.make
--- openstack-pkg-tools-21/pkgos.make 2015-01-05 15:48:09.0 +
+++ openstack-pkg-tools-22/pkgos.make 2015-01-08 15:13:03.0 +
@@ -34,7 +34,6 @@
pkgos-gen-upstart-job $$i ; \
fi \
done
- dh_installinit --error-handler=true
# Generate the systemd unit file
# Note: because dh_systemd_enable is called by the
# dh sequencer *before* dh_installinit, we have
@@ -45,6 +44,7 @@
MYSERVICE=`echo $$MYSERVICE | sed 's/.init.in/.service/'` ; \
dh_systemd_enable $$MYSERVICE ; \
done
+ dh_installinit --error-handler=true
gen-author-list:
git log --format='%aN %aE' | awk '{arr[$$0]++} END{for (i in arr){print arr[i], i;}}' | sort -rn | cut -d' ' -f2-
diff -Nru ceilometer-2014.1.3/debian/changelog ceilometer-2014.1.3/debian/changelog
--- ceilometer-2014.1.3/debian/changelog 2015-01-05 16:11:50.0 +
+++ ceilometer-2014.1.3/debian/changelog 2015-01-08 15:44:08.0 +
@@ -1,3 +1,9 @@
+ceilometer (2014.1.3-6) unstable; urgency=medium
+
+ * Rebuilt with openstack-pkg-tools (= 22~): starts daemons on first install.
+
+ -- Thomas Goirand z...@debian.org Thu, 08 Jan 2015 15:37:34 +
+
ceilometer (2014.1.3-5) unstable; urgency=medium
* Now depends on openstack-pkg-tools (= 21~).
diff -Nru ceilometer-2014.1.3/debian/control ceilometer-2014.1.3/debian/control
--- ceilometer-2014.1.3/debian/control 2015-01-05 16:11:50.0 +
+++ ceilometer-2014.1.3/debian/control 2015-01-08 15:44:08.0 +
@@ -7,7 +7,7 @@
Mehdi Abaakouk sil...@sileht.net
Build-Depends: debhelper (= 9),
dh-systemd,
- openstack-pkg-tools (= 21~),
+ openstack-pkg-tools (= 22~),
po-debconf,
python-all (= 2.6.6-3~),
python-pbr (= 0.6),
Bug#771860: RFS: gnucheese/1.00-1
Hi, Michel Van den Bergh michel.vandenbe...@uhasselt.be writes: Thanks for the detailed review! I will take care of it (I am currently at a conference so it may take a couple of days). I will probably have to get back to you with some questions. Did you have a chance to make some progress in the packaging of gnucheese? If you don't have enough time, I propose than we maintain the package together. I should be able to address my comments and upload the package. Thanks, Vincent signature.asc Description: PGP signature
Bug#775258: dpkg-dev: dpkg-shlibdeps doesn't pass admindir parameter to nested dpkg --search
Hi, My use case is i686 package compiled using sysroot on amd64 system, I want to use the same sysroot for deb generation. Here's a patch that works for me http://pastebin.com/6mfeVgKc Regards, Lukasz On Tue, Jan 13, 2015 at 8:17 AM, Guillem Jover guil...@debian.org wrote: Hi! On Tue, 2015-01-13 at 05:20:07 -0500, Lukasz Jagielski wrote: Package: dpkg-dev Version: 1.17.23 Severity: normal I've run into this problem when trying to generate dpkg packages using non-standard dpkg admin dir. I've noticed that dpkg-shlibdeps doesn't fully honour --admindir parameter, since its internal call to dpkg --search isn't provided with it. Ah right, I'm fixing this for 1.18.x (targetted at Stretch). I'll check if there's other dpkg invocations from dpkg-dev scripts. But in any case I don't think that using a different admindir is something really supported in normal packaging. Thanks, Guillem
Bug#775197: uniq: -u -d -D options non-orthogonal and confusing when combined
On 12/01/15 14:13, Jonathan David Amery wrote: Package: coreutils Version: 8.13-3.5 Severity: normal I was attempting to use uniq to categorise my data based on the first so many characters and I discover that: a) it is currently impossible to use uniq to output all lines; with lines grouped by initial prefix ( -w N ) and separated by an empty line (--all-repeated=separate) because there is no way to specify outputing all lines b) the combination behaviour of -u -d and -D is odd and suboptimal. Here is an example with a small example dataset: :; cat uniq-test AAA AAB ABA ABC ACA ADA ADD ADE :; uniq -w 2 -u uniq-test ACA :; uniq -w 2 -d uniq-test AAA ABA ADA :; uniq -w 2 -D uniq-test AAA AAB ABA ABC ADA ADD ADE :; uniq -w 2 -ud uniq-test :; uniq -w 2 -du uniq-test :; uniq -w 2 --all-repeated=separate uniq-test AAA AAB ABA ABC ADA ADD ADE :; uniq -w 2 -u --all-repeated=separate uniq-test AAA ABA ADA ADD :; uniq -w 2 -c -D uniq-test uniq: printing all duplicated lines and repeat counts is meaningless Try `uniq --help' for more information. :; So in summary: -ud or -du produces no output; but doesn't produce an error (where -c -D does) -u -D produces unexpected output (all the repeated lines except the last one for each set). There is no way to output all lines, with separations. There are a number of ways to address this issue; but I think the best one would be to correct behavior and documentation such that: -u outputs any lines which are unique -d outputs the first of any lines which are duplicated -D outputs all lines which are duplicated --all-repeated=METHOD seperates any groups of lines in the specified behavior Such that the output I wanted would be produced with: :; uniq -w 2 -u --all-repeated=separate uniq-test AAA AAB ABA ABC ACA ADA ADD ADE :; Thanks, J. Upstream has gone with uniq --group since version 8.22 -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#774031: r-base-dev: please do not write username and current time when building packages
Dirk Eddelbuettel: So you would have to make a minimal change, build and see how it is deployed. Done in our experimental repository. Let me know how it goes. Sure! -- Lunar.''`. lu...@debian.org: :Ⓐ : # apt-get install anarchism `. `'` `- signature.asc Description: Digital signature
Bug#768406: fixed/
I'm not sure why I haven't gotten any emails about this discussion in all this time. However (due to an independent report on github) this problem *should* be fixed as of 0.34-1. cgmanager now remounts / in its private ns as MS_SLAVE, not MS_PRIVATE, so the umount from the host should propagate into cgmanager's namespace. If that does not suffice, we can add an option to cgmanager (and maybe even make it default) to not unshare a private namespace. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#775283: unblock: neutron/2014.1.3-11
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: unblock
Dear release team,
Here's the changes for this version:
*/ Before version 2014.1.3-11, neutron-metadata-agent was using the same
Debconf templates as neutron-server. Unfortunately, a user reported that
it was really annoying for him, as he used a puppet script that was
only using /etc/neutron/metadata_agent.ini and never populating the
/etc/neutron/neutron.conf file. Therefore, this version 2014.1.3-11 is
changing the debconf template name from Template: neutron/* to
Template: neutron-metadata/*, which fixes the issue. Please see
#774788 for more details. So the below files where fixed for this:
- debian/neutron-metadata-agent.config.in
- debian/neutron-metadata-agent.postinst.in
- debian/neutron-metadata-agent.templates
The text of the templates didn't change, so it shouldn't be an issue for
translations.
*/ Package is rebuilt against openstack-pkg-tools = 22~ to fix the
last systemd issue that was preventing startup of daemons on the first
install (see unblock bug #775278).
*/ Upload of version 2014.1.3-10 closed the wrong bug, I corrected the
changelog. I'll be watching the BTS to make sure of correctness.
Please unblock neutron/2014.1.3-11, debdiff attached.
Cheers,
Thomas Goirand (zigo)
diff -Nru neutron-2014.1.3/debian/changelog neutron-2014.1.3/debian/changelog
--- neutron-2014.1.3/debian/changelog 2015-01-07 23:10:06.0 +
+++ neutron-2014.1.3/debian/changelog 2015-01-08 15:35:33.0 +
@@ -1,6 +1,14 @@
+neutron (2014.1.3-11) unstable; urgency=medium
+
+ * Use separate debconf variables for the metadata server (Closes: #774788).
+ * Rebuilding with openstack-pkg-tools (= 22~) to make sure daemons are
+started automatically at first install.
+
+ -- Thomas Goirand z...@debian.org Thu, 08 Jan 2015 14:16:37 +
+
neutron (2014.1.3-10) unstable; urgency=medium
- * Sets neutron/configure_db default value to false (Closes: #770944).
+ * Sets neutron/configure_db default value to false (Closes: #774792).
-- Thomas Goirand z...@debian.org Thu, 08 Jan 2015 00:05:56 +0100
diff -Nru neutron-2014.1.3/debian/control neutron-2014.1.3/debian/control
--- neutron-2014.1.3/debian/control 2015-01-07 23:10:06.0 +
+++ neutron-2014.1.3/debian/control 2015-01-08 15:35:33.0 +
@@ -7,7 +7,7 @@
Mehdi Abaakouk sil...@sileht.net
Build-Depends: debhelper (= 9),
dh-systemd,
- openstack-pkg-tools (= 21~),
+ openstack-pkg-tools (= 22~),
po-debconf,
python-all (= 2.6),
python-pbr (= 0.6),
diff -Nru neutron-2014.1.3/debian/neutron-metadata-agent.config.in neutron-2014.1.3/debian/neutron-metadata-agent.config.in
--- neutron-2014.1.3/debian/neutron-metadata-agent.config.in 2015-01-07 23:10:06.0 +
+++ neutron-2014.1.3/debian/neutron-metadata-agent.config.in 2015-01-08 15:35:33.0 +
@@ -10,7 +10,7 @@
pkgos_var_user_group neutron
chmod 755 /var/lib/neutron
-pkgos_read_admin_creds ${META_AGNT_CONF} DEFAULT neutron
-pkgos_read_config ${META_AGNT_CONF} DEFAULT auth_region neutron/region-name
+pkgos_read_admin_creds ${META_AGNT_CONF} DEFAULT neutron-metadata
+pkgos_read_config ${META_AGNT_CONF} DEFAULT auth_region neutron-metadata/region-name
exit 0
diff -Nru neutron-2014.1.3/debian/neutron-metadata-agent.postinst.in neutron-2014.1.3/debian/neutron-metadata-agent.postinst.in
--- neutron-2014.1.3/debian/neutron-metadata-agent.postinst.in 2015-01-07 23:10:06.0 +
+++ neutron-2014.1.3/debian/neutron-metadata-agent.postinst.in 2015-01-08 15:35:33.0 +
@@ -7,7 +7,7 @@
#PKGOS-INCLUDE#
manage_metadata_region () {
- db_get neutron/region-name
+ db_get neutron-metadata/region-name
if [ -n ${RET} ] ; then
pkgos_inifile set ${CONF_FILE} DEFAULT auth_region ${RET}
fi
@@ -21,7 +21,7 @@
if [ ! -e ${CONF_FILE} ] ; then
install -D -m 0640 -o neutron -g neutron /usr/share/neutron-metadata-agent/metadata_agent.ini ${CONF_FILE}
fi
- pkgos_write_admin_creds ${CONF_FILE} DEFAULT neutron
+ pkgos_write_admin_creds ${CONF_FILE} DEFAULT neutron-metadata
manage_metadata_region
db_stop
fi
diff -Nru neutron-2014.1.3/debian/neutron-metadata-agent.templates neutron-2014.1.3/debian/neutron-metadata-agent.templates
--- neutron-2014.1.3/debian/neutron-metadata-agent.templates 2015-01-07 23:10:06.0 +
+++ neutron-2014.1.3/debian/neutron-metadata-agent.templates 2015-01-08 15:35:33.0 +
@@ -7,28 +7,28 @@
# Even minor modifications require translation updates and such
# changes should be coordinated with translators and reviewers.
-Template: neutron/auth-host
+Template: neutron-metadata/auth-host
Type: string
Default: 127.0.0.1
_Description: Auth server hostname:
Please specify the URL of your Neutron authentication server. Typically
this is also the URL of your OpenStack Identity Service
Bug#775272: fail2ban: Enabling php-url-fopen results in a FilterPyinotify error
forcemerge 774689 775272 thanks Known issue... didn't have time unfortunately even though workaround is trivial - willing to try? $ git diff diff --git a/server/__init__.py b/server/__init__.py index 2b76f4b..74f3b75 100644 --- a/server/__init__.py +++ b/server/__init__.py @@ -23,3 +23,7 @@ __author__ = Cyril Jaquier __copyright__ = Copyright (c) 2004 Cyril Jaquier __license__ = GPL + +from time import strptime +# strptime thread safety hack-around - http://bugs.python.org/issue7980 +strptime(2012, %Y) so just add those lines to your /usr/share/fail2ban/server/__init__.py and see if it starts now On Tue, 13 Jan 2015, Francois Gouget wrote: Package: fail2ban Version: 0.8.13-1 Severity: normal Dear Maintainer, Enabling php-url-fopen causes fail2ban to fail on startup with the following error: 2015-01-13 14:07:23,618 fail2ban.filter [4845]: ERROR Error in FilterPyinotify callback: 'module' object has no attribute '_strptime_time' 2015-01-13 14:09:23,856 fail2ban.server [4845]: INFOStopping all jails -- Yaroslav O. Halchenko, Ph.D. http://neuro.debian.net http://www.pymvpa.org http://www.fail2ban.org Research Scientist,Psychological and Brain Sciences Dept. Dartmouth College, 419 Moore Hall, Hinman Box 6207, Hanover, NH 03755 Phone: +1 (603) 646-9834 Fax: +1 (603) 646-1419 WWW: http://www.linkedin.com/in/yarik -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#775253: dbab: unowned files after purge (policy 6.8, 10.8): /etc/dnsmasq.d/dnsmasq.{adblock, trashsites}.conf
On Tue, Jan 13, 2015 at 3:30 AM, Andreas Beckmann a...@debian.org wrote: during a test with piuparts I noticed your package left unowned files on the system after purge Oh thanks. I noticed the piuparts issue on the Debian QA page, but wasn't able to find any more info on that from the web links. Thanks I'll look into it. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#775234: /sbin/e2fsck: systemd boot will hang if e2fsck-based logging is enabled
Hello,
Theodore Ts'o (Monday 2015-01-12):
Arguably this is as mucha bug in systemd-fsck since it could have been
waiting for fsck to terminate instead of waiting for an EOF from the
progress_fd pipe, but I agree that it would be better if e2fsck were
to close the progress_fd.
Thank you. Indeed, I wasn't sure where to file this bug; I chose e2fsck
because it had suffered from a similar one, and it seemed easier to fix
as you did than to replace systemd-fsck's while(!feof) { fscanf } loop
with something much more complicated...
OTOH, thinking about it, other filesystems' fsck utilities might be
affected too, not just e2fsck.
Do you think this bug should be reassigned to systemd? Or that other fsck
maintainers should be made aware of the issue?
This isn't an RC bug by any means (I don't think it even rates
important) since very few people are using the e2fsck.conf logging
capabilities --- most debian users pre-systemd have been been using
/var/log/fsck/*, and systemd will do its own journalctl thing.
I'm not as well-versed as I'd like in the various logging mechanisms, but
given that /var/log/fsck isn't mounted RW at this stage of the boot,
doesn't logging there require e2fsck.conf logging?
Besides, even though few people may be using e2fsck.conf, they may be in for
a nasty surprise when upgrading to Jessie, or systemd users if they try
tinkering with e2fsck.conf; don't you think users should be warned somehow?
Perhaps the postinst script in the Debian package could check for it?
(And this doesn't cover other distributions or filesystems, of course.
Maybe it is really systemd's problem...)
Anyway, thanks for your time, and for the patch.
Best regards,
Cedric Ware.
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#734188: Packaging diffs for folly?
Hello, Laszlo. Do you happen to have around the code that you made for packaging folly? I may need to package it after all. Many more OSS projects at Facebook are using it and it makes no sense anymore to embed it at every one of them. I am at the same time working internally to have a proper story around versioning. Right now they're tagging the repository every two weeks or so with a new number, which is better than before but still silly because we are not really using any SONAME or things like that. Thanks, Ender. signature.asc Description: OpenPGP digital signature
Bug#775262: RM: openvdb [mipsel sparc] -- ANAIS; #768040
Package: ftp.debian.org Severity: normal This is a follow up to #768040. Please remove openvdb from mipsel and sparc. Those binaries were never part of debian stable. They accidentally transitioned to testing due to an issue in the tbb test suite[*], which made as if the package could run on those platforms. See: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=768040 -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#775067: systemd: journald doesn't forward messages to syslog w/o CAP_SYS_ADMIN (LXC)
Control: forwarded -1 http://lists.freedesktop.org/archives/systemd-devel/2015-January/026987.html Hello Christian, Christian Seiler [2015-01-10 23:42 +0100]: when using LXC containers without CAP_SYS_ADMIN, journald fails to forward any messages to syslog by default. Thank you for the patch! I massaged it a bit and forwarded it to the upstream mailing list. Note that I consider grave quite inflated, severity normal or important would be more appropriate IMHO. But either way, I'll try to get this into jessie. Thanks, Martin -- Martin Pitt| http://www.piware.de Ubuntu Developer (www.ubuntu.com) | Debian Developer (www.debian.org) signature.asc Description: Digital signature
Bug#638720: Odoo packaging
Dear Martin, I am part of the Odoo team working on packaging and we are currently working on an Odoo 8.0 package for the Debian archive. Here is our work so far: https://mentors.debian.net/package/odoo There are still some lintian errors or warnings. Many of them are due to the fact that Odoo embeds javascript libraries, and those libraries are often minified. However, we prefer to keep those libraries in the archive to have a better control of those libraries updates. We also get a warning because we put image files in /usr/lib, but we can't put images apart from python code. About the script-with-language-extension, we could replace odoo.py by odoo but we prefer not to do so as it could break scripts of people already using the deb packages published on http://nightly.odoo.com/, especially because v8.0 is the stable version of Odoo (released in Sep. 14). We would like to do a RFS for this package. What do you think? Regards, Aaron Bohy -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#774461: Bug#775059: linux-image-3.2.0-4-amd64: suspend to ram regression in 3.2.65-1
Hello, i can confirm the bug and had the similar problem here on a HP Z220 workstation and the test kernel from Ben fixed the problem. Thank you very much and kind regards, Andreas -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#774328: [Pkg-samba-maint] Bug#774328: ctdb: Failed to start ctdb.service: Unit ctdb.service failed to load: No such file or directory.
2014-12-31 23:16 GMT+01:00 Martin Schwenke mar...@meltin.net:
Package: ctdb
Version: 2.5.4+debian0-3
Severity: grave
Justification: renders package unusable
Dear Maintainer,
# systemctl start ctdb
Failed to start ctdb.service: Unit ctdb.service failed to load: No such file
or directory.
[...]
Couldn't reproduce here. But I need to test again in a clean VM.
Anything relevant in /var/log/{syslog,ctdb/log.ctdb}? journalctl -u
ctdb.service?
Was this machine migrated from wheezy? Do you have rsyslog installed?
Regards
--
Mathieu
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#775264: mesa: Please apply patch from freedesktop bug #85647
Source: mesa Version: 10.3.2-1 Severity: important Tags: patch I have had problems with my TAHITI radeon videocard for the last year or so, where it would lock up randomly between 10 minutes to a few hours from booting. So much so that I have needed to switch to fglrx to get my system reliable. This problem apparently only manifests on certain chipsets, like the TAHITI variant I have and not all radeonsi cards out there. I have compiled the current mesa 10.3.2-1 which is the latest available in jessie and sid, with a patch posted in freedesktop bug #85647, and my system is stable in the 3 weeks I'm running this custom version. This patch is already included in mesa 10.3.4, but since a new release has not been forthcoming in the last weeks and the current version must hurt others out there. I'm filing this bug report to nudge the maintainer to either include this patch in 10.3.2, or upgrade to 10.3.4. bug: https://bugs.freedesktop.org/show_bug.cgi?id=85647 patch: https://bugs.freedesktop.org/attachment.cgi?id=109261 -- System Information: Debian Release: 8.0 APT prefers testing APT policy: (750, 'testing'), (700, 'stable'), (600, 'unstable') Architecture: amd64 (x86_64) Foreign Architectures: i386 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) diff --git a/src/gallium/drivers/radeonsi/si_dma.c b/src/gallium/drivers/radeonsi/si_dma.c index b1bd5e7..3da2d26 100644 --- a/src/gallium/drivers/radeonsi/si_dma.c +++ b/src/gallium/drivers/radeonsi/si_dma.c @@ -250,6 +250,9 @@ void si_dma_copy(struct pipe_context *ctx, return; } + /* XXX: Asynchronous DMA causes lockups for some */ + goto fallback; + if (src-format != dst-format || src_box-depth 1 || rdst-dirty_level_mask != 0 || rdst-cmask.size || rdst-fmask.size ||
Bug#775266: virtualbox networking problems in bridge mode
Package: virtualbox Version: 4.3.20-dfsg-1 Severity: important When using virtualbox VMs in Bridge Network mode, there are serious problems. ON the host, I have a custom bridge configured. 4: lxcbr0: BROADCAST,MULTICAST,UP,LOWER_UP mtu 1500 qdisc noqueue state UP group default link/ether fe:f6:f2:03:7e:33 brd ff:ff:ff:ff:ff:ff inet 172.16.10.1/16 brd 172.16.255.255 scope global lxcbr0 valid_lft forever preferred_lft forever inet6 fe80::a0ef:b5ff:fe4a:215c/64 scope link valid_lft forever preferred_lft forever # This bridge will is used to NAT LXC containers' traffic auto lxcbr0 iface lxcbr0 inet static bridge_fd 0 bridge_maxwait 0 address 172.16.10.1 netmask 255.255.0.0 pre-up brctl addbr lxcbr0 post-down brctl delbr lxcbr0 post-down echo 0 /proc/sys/net/ipv4/ip_forward post-down echo 0 /proc/sys/net/ipv6/conf/all/forwarding post-up echo 1 /proc/sys/net/ipv4/ip_forward post-up echo 1 /proc/sys/net/ipv6/conf/all/forwarding post-up iptables -A FORWARD -i lxcbr0 -s 172.16.10.1/16 -j ACCEPT post-up iptables -A POSTROUTING -t nat -s 172.16.10.1/16 -j MASQUERADE # add checksum so that dhclient does not complain. # udp packets staying on the same host never have a checksum filled else post-up iptables -A POSTROUTING -t mangle -p udp --dport bootpc -s 172.16.10.1/16 -j CHECKSUM --checksum-fill pre-down iptables -D FORWARD -i lxcbr0 -s 172.16.10.1/16 -j ACCEPT pre-down iptables -D POSTROUTING -t nat -s 172.16.10.1/16 -j MASQUERADE # add checksum so that dhclient does not complain. # udp packets staying on the same host never have a checksum filled else pre-down iptables -D POSTROUTING -t mangle -p udp --dport bootpc -s 172.16.10.1/16 -j CHECKSUM --checksum-fill The LXC containers, attached to the bridge, work perfect. The VBox VMs, attached to the same brdige, ping in the beginning, but _eventually_ cannot do any network. THe netwrok start to time out. The VMs to have their link status. Looking into the Host's dmesg shows: [ 756.958798] nspr-3[6988]: segfault at 8 ip 7f0cbcbf285c sp 7f0ca80b7670 error 4 in VBoxXPCOM.so[7f0cbcb9b000+fe000] My intent is to have a custom bridge interface, which I hand control. THen, to it I'd like to attach everythign: KVM, VBox, LXC etc, and let them all talk to each other. -- System Information: Debian Release: 8.0 APT prefers testing APT policy: (990, 'testing'), (500, 'unstable'), (101, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 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: sysvinit (via /sbin/init) Versions of packages virtualbox depends on: ii adduser 3.113+nmu3 ii dpkg 1.17.23 ii libc62.19-13 ii libcurl3-gnutls 7.38.0-4 ii libgcc1 1:4.9.1-19 ii libgsoap52.8.17-1 ii libpng12-0 1.2.50-2+b2 ii libpython2.7 2.7.8-11 ii libsdl1.2debian 1.2.15-10+b1 ii libssl1.0.0 1.0.1j-1 ii libstdc++6 4.9.1-19 ii libvncserver00.9.9+dfsg-6.1 ii libvpx1 1.3.0-3 ii libx11-6 2:1.6.2-3 ii libxcursor1 1:1.1.14-1+b1 ii libxext6 2:1.3.3-1 ii libxml2 2.9.1+dfsg1-4 ii libxmu6 2:1.1.2-1 ii libxt6 1:1.1.4-1+b1 ii python 2.7.8-2 ii python2.72.7.8-11 ii zlib1g 1:1.2.8.dfsg-2+b1 Versions of packages virtualbox recommends: ii libgl1-mesa-glx [libgl1] 10.3.2-1 ii libqt4-opengl 4:4.8.6+git64-g5dc8b2b+dfsg-2+b1 ii libqtcore44:4.8.6+git64-g5dc8b2b+dfsg-2+b1 ii libqtgui4 4:4.8.6+git64-g5dc8b2b+dfsg-2+b1 ii virtualbox-dkms 4.3.20-dfsg-1 ii virtualbox-qt 4.3.20-dfsg-1 Versions of packages virtualbox suggests: ii vde22.3.2+r586-1 ii virtualbox-guest-additions-iso 4.3.20-1 -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#775258: dpkg-dev: dpkg-shlibdeps doesn't pass admindir parameter to nested dpkg --search
Package: dpkg-dev Version: 1.17.23 Severity: normal Dear Maintainer, I've run into this problem when trying to generate dpkg packages using non-standard dpkg admin dir. I've noticed that dpkg-shlibdeps doesn't fully honour --admindir parameter, since its internal call to dpkg --search isn't provided with it. Regards, Lukasz Jagielski -- System Information: Debian Release: 8.0 APT prefers testing-updates APT policy: (500, 'testing-updates'), (500, 'testing') Architecture: i386 (i686) Kernel: Linux 3.16.0-4-686-pae (SMP w/2 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages dpkg-dev depends on: ii base-files 8 ii binutils 2.24.90.20141023-1 ii bzip2 1.0.6-7+b2 ii libdpkg-perl 1.17.23 ii make-guile [make] 4.0-8 ii patch 2.7.1-6 ii xz-utils 5.1.1alpha+20120614-2+b3 Versions of packages dpkg-dev recommends: ii build-essential 11.7 ii fakeroot 1.20.2-1 ii gcc [c-compiler] 4:4.9.1-5 ii gcc-4.9 [c-compiler] 4.9.1-19 ii gnupg1.4.18-6 ii gnupg2 2.0.26-3 ii gpgv 1.4.18-6 ii libalgorithm-merge-perl 0.08-2 Versions of packages dpkg-dev suggests: pn debian-keyring 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
