Bug#779513: LaTeX Error: File `lambda.sty' not found.
On 01.03.2015 19:04, Joachim Breitner wrote: Hi, skak.sty requires lambda.sty, which is not contained in texlive-games: $ pdflatex /usr/share/doc/texlive-doc/latex/skak/fen_with_black.tex will produce ! LaTeX Error: File `lambda.sty' not found. fls file attached. Changelog of skak: Version 1.5.2 - * Removed lambda.sty from the skak distribution. Not sure, where to get lambda.sty from. The only occurrence on CTAN I found is http://www.ctan.org/tex-archive/macros/plain/contrib/lambda . Could you test, if installing this package solves your problem? Hilmar -- http://www.hilmar-preusse.de.vu/ #206401 http://counter.li.org -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#779579: installer broken: multipath-udeb depends on non-existent libgcc1 udeb
Hi Ritesh, Thanks for looking into this. On 03/02/2015 04:40 PM, Ritesh Raj Sarraf wrote: libgcc1 package is available in the archive. I'm not sure why it isn't present in your install media. Can you point out the udeb? It's not listed in sid d-i Packages file, nor in the jessie CD ISO, at least: $ curl -s ftp://ftp.debian.org/debian/dists/sid/main/debian-installer/binary-amd64/Packages.xz | xzgrep '^Package: libgcc1' | wc -l 0 $ find jessie-rc-iso/pool/ -name 'libgcc*' jessie-rc-iso/pool/main/g/gcc-4.9/libgcc1_4.9.1-19_ppc64el.deb And there's no udeb in the gcc-4.9 pool dir: ftp://ftp.debian.org/debian/pool/main/g/gcc-4.9/ -- Mauricio Faria de Oliveira IBM Linux Technology Center -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#779506: per-protocol virtual packages for boardgame AI engines and GUI
On Mon, Mar 02, 2015 at 07:37:06PM +0100, Bill Allombert wrote: On Sun, Mar 01, 2015 at 05:59:39PM +0100, Yann Dirson wrote: Package: debian-policy Severity: wishlist Following the short discussion starting at [1], I'm submitting the following list of virtual packages, to facilitate the declaration of protocol compatibility between boardgame AI engines, boardgame GUI's and protocol adapters: * cecp-game-engine * cecp-game-ui * uci-game-engine * uci-game-ui * xshogi-game-engine * xshogi-game-ui * gtp2-game-engine * gtp2-game-ui Thanks! Could you write a small description for each virtual packages as in the file virtual-package-names-list.txt ? Oops :) Here there are: cecp-game-enginean AI engine using the XBoard Chess Engine Communication Protocol cecp-game-uia user interface talking the XBoard Chess Engine Communication Protocol uci-game-engine an AI engine using the Universal Chess Interface protocol uci-game-ui a user interface talking the Universal Chess Interface protocol xshogi-game-engine an AI engine using the XShogi protocol xshogi-game-ui a user interface talking the XShogi protocol gtp2-game-enginean AI engine using version 2 of the Go Text Protocol gtp2-game-uia user interface talking version 2 of the Go Text Protocol Best regards, -- Yann -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#779600: linux-image-3.16.0-4-686-pae: Linux console does not render the bold attribute correctly
Package: src:linux Version: 3.16.7-ckt4-3 Severity: normal Dear Maintainer, I've noticed that with this kernel, bold does not work on my console. For example, running man man to show the man(1) manpage does not show headings in bold as it normally does. (It also makes installed packages look very similar to uninstalled packages in aptitude.) -- Package-specific info: ** Version: Linux version 3.16.0-4-686-pae (debian-ker...@lists.debian.org) (gcc version 4.8.4 (Debian 4.8.4-1) ) #1 SMP Debian 3.16.7-ckt4-3 (2015-02-03) ** Command line: BOOT_IMAGE=/boot/vmlinuz-3.16.0-4-686-pae root=/dev/mapper/Group1-ROOT ro ** Not tainted ** Kernel log: [3.076607] hub 2-1:1.0: USB hub found [3.076827] hub 2-1:1.0: 6 ports detected [3.206681] EXT4-fs (dm-0): orphan cleanup on readonly fs [3.206819] EXT4-fs (dm-0): 1 orphan inode deleted [3.206907] EXT4-fs (dm-0): recovery complete [3.256363] EXT4-fs (dm-0): mounted filesystem with ordered data mode. Opts: (null) [3.335775] Switched to clocksource tsc [3.480403] scsi 6:0:0:0: Direct-Access MultiFlash Reader 1.00 PQ: 0 ANSI: 0 [3.480783] sd 6:0:0:0: Attached scsi generic sg2 type 0 [3.481701] sd 6:0:0:0: [sdb] Attached SCSI removable disk [3.863462] random: nonblocking pool is initialized [4.844154] systemd-udevd[318]: starting version 215 [5.649388] input: Power Button as /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0C:00/input/input4 [5.649474] ACPI: Power Button [PWRB] [5.649574] input: Power Button as /devices/LNXSYSTM:00/LNXPWRBN:00/input/input5 [5.649654] ACPI: Power Button [PWRF] [5.709993] shpchp: Standard Hot Plug PCI Controller Driver version: 0.4 [5.725317] mei_me :00:16.0: irq 46 for MSI/MSI-X [5.945763] cfg80211: Calling CRDA to update world regulatory domain [5.959530] input: PC Speaker as /devices/platform/pcspkr/input/input7 [6.122326] ieee80211 phy0: rt2x00_set_rt: Info - RT chipset 5392, rev 0223 detected [6.125881] ieee80211 phy0: rt2x00_set_rf: Info - RF chipset 5392 detected [6.167961] ieee80211 phy0: Selected rate control algorithm 'minstrel_ht' [6.207537] [drm] Initialized drm 1.1.0 20060810 [6.223863] alg: No test for crc32 (crc32-pclmul) [6.321572] [drm] Memory usable by graphics device = 2048M [6.321635] [drm] Replacing VGA console driver [6.322117] Console: switching to colour dummy device 80x25 [6.342594] i915 :00:02.0: irq 47 for MSI/MSI-X [6.342602] [drm] Supports vblank timestamp caching Rev 2 (21.10.2013). [6.342606] [drm] Driver supports precise vblank timestamp query. [6.342623] vgaarb: device changed decodes: PCI::00:02.0,olddecodes=io+mem,decodes=io+mem:owns=io+mem [6.635836] iTCO_vendor_support: vendor-support=0 [6.636400] iTCO_wdt: Intel TCO WatchDog Timer Driver v1.11 [6.636425] iTCO_wdt: Found a Lynx Point TCO device (Version=2, TCOBASE=0x1860) [6.636495] iTCO_wdt: initialized. heartbeat=30 sec (nowayout=0) [6.706130] fbcon: inteldrmfb (fb0) is primary device [6.723634] Console: switching to colour frame buffer device 240x67 [6.728625] i915 :00:02.0: fb0: inteldrmfb frame buffer device [6.728650] i915 :00:02.0: registered panic notifier [6.751184] ACPI: Video Device [GFX0] (multi-head: yes rom: no post: no) [6.751354] input: Video Bus as /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/LNXVIDEO:00/input/input8 [6.751436] [drm] Initialized i915 1.6.0 20080730 for :00:02.0 on minor 0 [6.751894] ACPI Warning: SystemIO range 0xf040-0xf05f conflicts with OpRegion 0xf040-0xf04f (\_SB_.PCI0.SBUS.SMBI) [6.751921] snd_hda_intel :00:03.0: irq 48 for MSI/MSI-X [6.751944] (20140424/utaddress-258) [6.751962] ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver [6.752137] snd_hda_intel :00:1b.0: irq 49 for MSI/MSI-X [6.790274] input: HDA Intel HDMI HDMI/DP,pcm=3 as /devices/pci:00/:00:03.0/sound/card0/input9 [7.008090] sound hdaudioC1D0: autoconfig: line_outs=1 (0x14/0x0/0x0/0x0/0x0) type:line [7.008169] sound hdaudioC1D0:speaker_outs=0 (0x0/0x0/0x0/0x0/0x0) [7.008228] sound hdaudioC1D0:hp_outs=1 (0x1b/0x0/0x0/0x0/0x0) [7.008283] sound hdaudioC1D0:mono: mono_out=0x0 [7.008328] sound hdaudioC1D0:inputs: [7.008366] sound hdaudioC1D0: Front Mic=0x19 [7.008410] sound hdaudioC1D0: Rear Mic=0x18 [7.008452] sound hdaudioC1D0: Line=0x1a [7.016992] input: HDA Intel PCH Front Mic as /devices/pci:00/:00:1b.0/sound/card1/input10 [7.018704] input: HDA Intel PCH Rear Mic as /devices/pci:00/:00:1b.0/sound/card1/input11 [7.018819] input: HDA Intel PCH Line as /devices/pci:00/:00:1b.0/sound/card1/input12 [7.018923] input: HDA Intel PCH Line Out as /devices/pci:00/:00:1b.0/sound/card1/input13 [7.019026] input: HDA Intel PCH Front
Bug#779178: ghostscript: Landscape document rotate CCW not CW
On Mon 02 Mar 2015 at 19:08:41 +, Brian Potkin wrote: To complicate matters: there are two options which can give landscape: -o landscape and orientation-required=4 On Jessie they produce the same outcome. On Wheezy there is a 180 degree difference in the orientations. Whether the difference between Wheezy and Jessie is a result of changes in CUPS or cups-filters is unknown (to me) so I have included a CC to the cups-filters maintainer. orientation-required should be orientation-requested. Please ignore all the above. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#768808: libvlccore-dev: Missing vlc_interface.h
Hi, Heads up. The VLC developers just moved the vlc_interface.h to the pluginsinclude_HEADERS in the upstream git repo. commit 09b05ba6c88842d8d1bc83b8aed84338076baa40 Author: Rémi Denis-Courmont r...@remlab.net Date: Mon Mar 2 22:44:36 2015 +0200 include: install vlc_interface.h Best regards Jonas Lundqvist signature.asc Description: OpenPGP digital signature
Bug#755202:
I discussed this problem on the upstream mailing list here: http://thread.gmane.org/gmane.linux.network.networkmanager.devel/25377 In my case, the problem was indeed that netconsole was loaded. Netconsole was loaded in the initrd, and brought the network interface up. As the network interface went up, the kernel would automatically configure an IPv6 address via SLAAC. Then when later network-manager starts up, it notices that the network interface is already brought up, and hence it decides not to touch it any more: instead of loading the default network configuration for that device, a (temporary) network connection with the name of the device and the configuration corresponding to the actual state (in my case: IPv6 activated but no IPv4) is created in NM. I removed the netconsole stuff, removed the eth0 network connection in NM, and rebooted the system, and everything was OK again. Apparently it's only safe to load netconsole after NM has started, otherwise you get hit by this problem. -- Frederik Himpe frede...@frehi.be -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#779513: LaTeX Error: File `lambda.sty' not found.
Dear Hilmar, Am Montag, den 02.03.2015, 22:03 +0100 schrieb Hilmar Preuße: skak.sty requires lambda.sty, which is not contained in texlive-games: $ pdflatex /usr/share/doc/texlive-doc/latex/skak/fen_with_black.tex will produce ! LaTeX Error: File `lambda.sty' not found. fls file attached. Changelog of skak: Version 1.5.2 - * Removed lambda.sty from the skak distribution. Not sure, where to get lambda.sty from. The only occurrence on CTAN I found is http://www.ctan.org/tex-archive/macros/plain/contrib/lambda . Could you test, if installing this package solves your problem? yes, that does solve it. Greetings, Joachim -- Joachim nomeata Breitner Debian Developer nome...@debian.org | ICQ# 74513189 | GPG-Keyid: F0FBF51F JID: nome...@joachim-breitner.de | http://people.debian.org/~nomeata signature.asc Description: This is a digitally signed message part
Bug#778618: [PKG-Openstack-devel] Bug#778618: Bug#778618: This patch is not enough
Moritz Muehlenhoff j...@inutil.org writes: On Fri, Feb 27, 2015 at 10:18:46PM +, Paul McMillan wrote: If you agree that the linked github patch is complete, I can do an upload if you lack the time to do so yourself. I can understand that sensitive security issues are involved, but a bit more verboseness would be nice. The linked patch on github is a true and complete fix for the original reported issue. Gaudenz, can you please upload a fixed package? Thomas already uploaded the fix to unstable, so this should be fine. Is a stable upload needed as well? Gaudenz -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#776910: apt: upgrade from wheezy to jessie breaks in the middle
On 2015-02-24 09:53, Rafał Pietrak wrote: W dniu 23.02.2015 22:27, Niels Thykier pisze: On 2015-02-03 16:34, Rafal Pietrak wrote: [...] 5. I'm filing this bugreport, because this time there was no reboot-in-the middle, so I'd expect, the apt-max-errors (if it really exists - I cannot find it now) is truely too low for an average system I'd imagine, that upgrade from one major release to another should set it temporarly to infinity ;7, but may be not. Rather, there should be no errors during an upgrade - ever. That is one of the goals for upgrades. Somehow, setting such a (fictive?) option to infinite seems to be working around a problem that should not exist in the first place. Yes and no. *actual errors* yes; but I don't think I've seen them during the upgrade. 1. During the upgrade I have seen some errors/complains about unresolved dependencies, or conflicts ... but continiueing anyway as requested the apt-get said. Those are from dpkg (though I do appreciate that telling the difference between dpkg and apt-get output is difficult if you don't know them by heart or the interplay between apt and dpkg). However, I am fairly sure dpkg does /not/ have a max counter on those. I suspect what is happening here is that dpkg is complaining and would /normally/ have aborted with an error, but continues anyway because apt invoked dpkg with a --force-depends (or something similar). 2. at one point it said too many errors and stopped. 3. then a simple apt-get -f install; apt-get dist-upgrade completed the task (sort of) cleanly. Again, smells like a trigger issue. Though I will leave it to David (or another apt maintainer) to analyse the dpkg status log you included. For reference, the trigger check in dpkg was reverted. If it turns out that you were experiencing a trigger issue, then it is now solved already. [...] I believe the BTS will accept it (you may want to gzip it though), but lists.d.o will silently discard it. So follow up with a separate mail afterwards to ensure we notice once you have done it. I've learned, that attachments are OK. So here is my (most relevant) dpkg.status after the upgrade. Regretably, at this point I don't have the one from the date of an upgrade. -R Ack, thanks. For reference, the file was too large to reach de...@lists.debian.org (as I described). To anyone reading the list but not following the bug directly, the file is at [1]. ~Niels [1] https://bugs.debian.org/cgi-bin/bugreport.cgi?msg=27;filename=dpkg.status.6.gz;att=1;bug=776910 -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#779603: xserver-xorg-video-intel: Xorg crashes when unplugging external display on kernel 3.19
Package: src:xserver-xorg-video-intel
Version: 2:2.21.15-2
Severity: important
Tags: patch fixed-upstream fixed-in-experimental
Fixed: 2:2.99.917-1~exp1
Dear Maintainer,
Unplugging an external monitor (VGA, HDMI) causes Xorg to crash with
SEGFAULT when running Linux kernel version 3.19 from experimental on
Debian Jessie. Hotplug is also broken (external display only works if
it's already plugged in when Xorg starts). Both problems are fixes
upstream with the Intel driver version 2.99.17, which is also available
in experimental.
I am attaching a patch that backports the fix for the crash. I
understand that the problem only affects those running a bleeding-edge
kernel from experimental, and that the driver from the same release
fixes the problem, so it might not be worth merging this. Nevertheless,
I would think that it's a good idea to document the problem.
What follows is the backtrace, the patch fixes the problem which occurs
in frame 9, and then the system info. The patch will come in the
following email.
Kind regards,
Luca Boccassi
(gdb) bt full
#0 0x7fbea7b07107 in __GI_raise (sig=sig@entry=6)
at ../nptl/sysdeps/unix/sysv/linux/raise.c:56
resultvar = 0
pid = 5862
selftid = 5862
#1 0x7fbea7b084e8 in __GI_abort () at abort.c:89
save_stage = 2
act = {__sigaction_handler = {sa_handler = 0x7fbeab9b16b0,
sa_sigaction = 0x7fbeab9b16b0}, sa_mask = {__val = {3, 140736622040560,
140456868216327, 1, 0, 0, 140456833682728, 1, 140736622040560,
140456899564112, 140456868242213, 0, 140456833872816,
140456874926528, 140736622040320, 0}}, sa_flags = -1416131168,
sa_restorer = 0x7fbea9da1980}
sigs = {__val = {32, 0 repeats 15 times}}
#2 0x7fbea9f9a62e in OsAbort () at ../../os/utils.c:1361
No locals.
#3 0x7fbea9e754dc in ddxGiveUp (error=error@entry=EXIT_ERR_ABORT)
at ../../../../hw/xfree86/common/xf86Init.c:1088
i = optimized out
#4 0x7fbea9e75596 in AbortDDX (error=error@entry=EXIT_ERR_ABORT)
at ../../../../hw/xfree86/common/xf86Init.c:1132
i = optimized out
#5 0x7fbea9f9fef2 in AbortServer () at ../../os/log.c:783
No locals.
#6 0x7fbea9fa0d5d in FatalError (f=f@entry=0x7fbea9fcbb28 Caught
signal %d (%s). Server aborting\n) at ../../os/log.c:924
args = {{gp_offset = 24, fp_offset = 48, overflow_arg_area =
0x7fffcc5d16e0, reg_save_area = 0x7fffcc5d1610}}
args2 = {{gp_offset = 8, fp_offset = 48, overflow_arg_area =
0x7fffcc5d16e0, reg_save_area = 0x7fffcc5d1610}}
beenhere = 1
#7 0x7fbea9f97f7c in OsSigHandler (signo=11, sip=optimized out,
unused=optimized out) at ../../os/osinit.c:147
unused = optimized out
sip = optimized out
signo = 11
#8 signal handler called
No locals.
#9 intel_output_dpms (output=0x7fbeab9b12b0, dpms=3)
at ../../../src/uxa/intel_display.c:1107
intel_output = 0x7fbeab9b16b0
koutput = 0x0
mode = 0x7fbeab9ad250
i = 0
#10 0x7fbea9eac26c in xf86DisableUnusedFunctions
(pScrn=0x7fbeab99e410) at ../../../../hw/xfree86/modes/xf86Crtc.c:2985
output = optimized out
xf86_config = 0x7fbeab9ad2d0
o = 4
c = optimized out
#11 0x7fbea9eb5d79 in xf86RandR12CrtcSet (pScreen=0x7fbeab99de40,
randr_crtc=0x7fbeabcc2920, randr_mode=0x0, x=0, y=0, rotation=optimized
out, num_randr_outputs=0, randr_outputs=0x0)
at ../../../../hw/xfree86/modes/xf86RandR12.c:1237
pScrn = 0x7fbeab99e410
config = 0x7fbeab9ad2d0
crtc = 0x7fbeab9ae170
transform = 0x0
changed = optimized out
o = optimized out
ro = optimized out
save_crtcs = 0x7fbeabd987e0
save_enabled = 1
#12 0x7fbea9ef6ecd in RRCrtcSet (crtc=0x7fbeabcc2920, mode=0x3,
x=-1478011320, y=0, rotation=5888, numOutputs=-1415899312, outputs=0x0)
at ../../randr/rrcrtc.c:574
ret = 0
crtcChanged = 0
#13 0x7fbea9ef8354 in ProcRRSetCrtcConfig (client=0x7fbeab9b3bf0)
at ../../randr/rrcrtc.c:1173
stuff = 0x7fbeac7657c4
---Type return to continue, or q return to quit---
rep = {type = 96 '`', status = 32 ' ', sequenceNumber = 52317,
length = 32767, newTimestamp = 3428655136, pad1 = 32767, pad2 =
2879077360, pad3 = 32702, pad4 = 131072, pad5 = 0}
pScreen = 0x7fffcc5d1fd0
pScrPriv = 0x7fbeabcc1f00
crtc = 0x7fbeabcc2920
mode = 0x0
numOutputs = 0
rotation = 1
ret = -1541250496
status = 0 '\000'
#14 0x7fbea9e343f7 in Dispatch () at ../../dix/dispatch.c:432
clientReady = 0x7fbeac69a260
result = optimized out
client = 0x7fbeab9b3bf0
nready = 0
icheck = 0x7fbeaa22fd70 checkForInput
start_tick = 145
#15 0x7fbea9e38596 in dix_main (argc=18, argv=0x7fffcc5d22b8,
envp=optimized out) at ../../dix/main.c:296
i = optimized out
alwaysCheckForInput = {0, 1}
#16 0x7fbea7af3b45 in __libc_start_main (main=0x7fbea9e228e0
Bug#778773: Jessie RC1 Installer parted server segfault
On Mon, Mar 02, 2015 at 03:48:50PM +0100, Cyril Brulebois wrote: Steve McIntyre st...@einval.com (2015-03-02): Core was generated by `parted_server'. Program terminated with signal SIGSEGV, Segmentation fault. #0 0x0040b4b1 in command_get_file_system () at parted_server.c:1802 1802if (0 == strncmp(part-fs_type-name, linux-swap, 10)) (gdb) bt #0 0x0040b4b1 in command_get_file_system () at parted_server.c:1802 #1 0x0040eef2 in main_loop () at parted_server.c:2431 #2 0x00402bf0 in main (argc=optimized out, argv=optimized out) at parted_server.c:2522 (gdb) p part-fs_type $1 = (const PedFileSystemType *) 0x0 which is an obvious crash. Digging further... Great! That's one of the things I wanted to get sorted out before contemplating an RC2. ACK. I was on a train for 11 hours yesterday which gave me the time to dig into this, but I doubt I'll find much more time on my VAC to get any further. So it might be a couple of weeks, just so you know. I was happy to at least be able to share some progress! -- Steve McIntyre, Cambridge, UK.st...@einval.com Mature Sporty Personal More Innovation More Adult A Man in Dandism Powered Midship Specialty -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#779603: [PATCH] Backport fix for null pointers dereferences
From 9fe57ade94ac2f260b7a6b618be576dba7968dbd Mon Sep 17 00:00:00 2001
From: Luca Boccassi luca.bocca...@gmail.com
Date: Mon, 2 Mar 2015 21:08:09 +
Subject: [PATCH] Backport fix for null pointers dereferences
Cherry picked from commit:
commit 908520a7dacade8b6716e7c30549847464a33a81
Author: Dave Airlie airl...@redhat.com
Date: Wed Sep 3 10:43:21 2014 +1000
uxa: add MST support.
Signed-off-by: Luca Boccassi luca.bocca...@gmail.com
---
src/uxa/intel_display.c | 14 ++
1 file changed, 14 insertions(+)
diff --git a/src/uxa/intel_display.c b/src/uxa/intel_display.c
index b4f7e87..d584741 100644
--- a/src/uxa/intel_display.c
+++ b/src/uxa/intel_display.c
@@ -468,6 +468,9 @@ intel_crtc_apply(xf86CrtcPtr crtc)
continue;
intel_output = output-driver_private;
+ if (!intel_output-mode_output)
+ return FALSE;
+
output_ids[output_count] =
intel_output-mode_output-connector_id;
output_count++;
@@ -924,6 +927,11 @@ intel_output_attach_edid(xf86OutputPtr output)
xf86MonPtr mon = NULL;
int i;
+ if (!koutput) {
+ xf86OutputSetEDID(output, mon);
+ return;
+ }
+
/* look for an EDID property */
for (i = 0; i koutput-count_props; i++) {
drmModePropertyPtr props;
@@ -1013,6 +1021,9 @@ intel_output_get_modes(xf86OutputPtr output)
intel_output_attach_edid(output);
+ if (!koutput)
+ return;
+
/* modes should already be available */
for (i = 0; i koutput-count_modes; i++) {
DisplayModePtr Mode;
@@ -1104,6 +1115,9 @@ intel_output_dpms(xf86OutputPtr output, int dpms)
struct intel_mode *mode = intel_output-mode;
int i;
+ if (!koutput)
+ return;
+
for (i = 0; i koutput-count_props; i++) {
drmModePropertyPtr props;
--
2.1.4
signature.asc
Description: This is a digitally signed message part
Bug#671065: manpages-dev: missing manpages about pthread_mutex_* functions
forwarded 671065 https://www.kernel.org/doc/man-pages/missing_pages.html stop -- Stéphane Aulery -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#779600: linux-image-3.16.0-4-686-pae: Linux console does not render the bold attribute correctly
Control: tag -1 moreinfo On Mon, 2015-03-02 at 17:20 -0500, Samuel Bronson wrote: Package: src:linux Version: 3.16.7-ckt4-3 Severity: normal Dear Maintainer, I've noticed that with this kernel, bold does not work on my console. For example, running man man to show the man(1) manpage does not show headings in bold as it normally does. (It also makes installed packages look very similar to uninstalled packages in aptitude.) [...] Works for me. Are you using a VGA text console or frame buffer console? Which kernel version were you using previously? Is the TERM variable set correctly on the console (should be 'linux')? Ben. -- Ben Hutchings Anthony's Law of Force: Don't force it, get a larger hammer. signature.asc Description: This is a digitally signed message part
Bug#779529: xserver-xorg-video-intel: Built-in display completely black if external monitor is plugged in
Hello Julien, I forgot to mention, this patch also fixes an Xorg crash that happen when running kernel 3.19 (from Experimental) and disconnecting an external monitor. I can isolate the fix for that, it's a small diff. I'll open a new bug and attach the patch with more debug details, so you can have a look and decide what's best to do. Kind regards, Luca Boccassi signature.asc Description: This is a digitally signed message part
Bug#779599: libsocl-contrib-1.2-0, libsocl-1.2-0: missing breaks+replaces against each other
Package: libsocl-contrib-1.2-0,libsocl-1.2-0 Version: 1.2.0~20141210+dfsg-1 Severity: serious User: trei...@debian.org Usertags: edos-file-overwrite Architecture: amd64 Distribution: experimental Hi, automatic installation tests of packages that share a file and at the same time do not conflict by their package dependency relationships has detected the following problem: Selecting previously unselected package libstarpu-contrib-1.2-0. (Reading database ... 7843 files and directories currently installed.) Preparing to unpack .../libstarpu-contrib-1.2-0_1.2.0~20141210+dfsg-1_amd64.deb ... Unpacking libstarpu-contrib-1.2-0 (1.2.0~20141210+dfsg-1) ... Selecting previously unselected package libsocl-contrib-1.2-0. Preparing to unpack .../libsocl-contrib-1.2-0_1.2.0~20141210+dfsg-1_amd64.deb ... Unpacking libsocl-contrib-1.2-0 (1.2.0~20141210+dfsg-1) ... dpkg: error processing archive /var/cache/apt/archives/libsocl-contrib-1.2-0_1.2.0~20141210+dfsg-1_amd64.deb (--unpack): trying to overwrite '/usr/lib/libsocl-1.2.so.0.0.0', which is also in package libsocl-1.2-0 1.2.0~20141210+dfsg-1 Errors were encountered while processing: /var/cache/apt/archives/libsocl-contrib-1.2-0_1.2.0~20141210+dfsg-1_amd64.deb This is a serious bug as it makes installation fail, and violates sections 7.6.1 and 10.1 of the policy. An optimal solution would consist in only one of the packages installing that file, and renaming or removing the file in the other package. Depending on the circumstances you might also consider Replace relations or file diversions. If the conflicting situation cannot be resolved then, as a last resort, the two packages have to declare a mutual Conflict. Please take into account that Replaces, Conflicts and diversions should only be used when packages provide different implementations for the same functionality. Here is a list of files that are known to be shared by both packages (according to the Contents file for sid/amd64, which may be slightly out of sync): usr/lib/libsocl-1.2.so.0 usr/lib/libsocl-1.2.so.0.0.0 This bug is assigned to both packages. If you, the maintainers of the two packages in question, have agreed on which of the packages will resolve the problem please reassign the bug to that package. You may also register in the BTS that the other package is affected by the bug. Cheers, Andreas PS: for more information about the detection of file overwrite errors of this kind see https://qa.debian.org/dose/file-overwrites.html libsocl-1.2-0=1.2.0~20141210+dfsg-1_libsocl-contrib-1.2-0=1.2.0~20141210+dfsg-1.log.gz Description: application/gzip
Bug#172139: Missing man-pages forwarded
forwarded 686084 https://www.kernel.org/doc/man-pages/missing_pages.html forwarded 172139 https://www.kernel.org/doc/man-pages/missing_pages.html stop -- Stéphane Aulery -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#778876: linux-headers-3.19.0-trunk-amd64 is uninstallable.
On Sat, 21 Feb 2015 11:20:40 +1100 Craig Sanders c...@taz.net.au wrote: Package: linux-headers-3.19.0-trunk-amd64 Version: 3.19-1~exp1 linux-headers-3.19.0-trunk-amd64 is uninstallable due to missing linux-kbuild-3.19 this also means that linux-image-3.19.0-trunk-amd64 is useless to anyone who needs dkms kernel modules. # apt-get -d -u -t experimental install linux-headers-3.19.0-trunk-amd64 linux-image-3.19.0-trunk-amd64 linux-support-3.19.0-trunk Reading package lists... Done Building dependency tree Reading state information... Done Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming. The following information may help to resolve the situation: The following packages have unmet dependencies: linux-headers-3.19.0-trunk-amd64 : Depends: linux-kbuild-3.19 but it is not installable Hello Craig, I had the same problem, but I managed to build the package myself by following the How to build linux-tools yourself paragraph in this guide: https://wiki.debian.org/HowToRebuildAnOfficialDebianKernelPackage Note that you'll need to apply the patch attached to this bug, otherwise linux-kbuild-3.19 does not build: https://lists.debian.org/debian-kernel/2015/02/msg00173.html Hope this can be useful. Kind regards, Luca Boccassi signature.asc Description: This is a digitally signed message part
Bug#779598: ITP: jboss-modules -- Modular Classloading System
Package: wnpp Severity: wishlist Owner: Markus Koschany a...@gambaru.de * Package name: jboss-modules Version : 1.4.1.Final Upstream Author : Red Hat, Inc. * URL : https://github.com/jboss-modules/jboss-modules * License : Apache-2.0 Programming Lang: Java Description : Modular Classloading System JBoss Modules is a standalone implementation of a modular (non-hierarchical) class loading and execution environment for Java. In other words, rather than a single class loader which loads all JARs into a flat class path, each library becomes a module which only links against the exact modules it depends on, and nothing more. It implements a thread-safe, fast, and highly concurrent delegating class loader model, coupled to an extensible module resolution system, which combine to form a unique, simple and powerful system for application execution and distribution. jboss-modules is a dependency of jboss-logmanager and will be maintained by the Java team. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#123999: Reassign 123999 to gnulib package
reassign 123999 gnulib stop -- Primary source of documentation for these pages is Texinfo manual of gnulib and not man-pages. -- Stéphane Aulery -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#779602: desktop-profiles: please make the build reproducible
Source: desktop-profiles Version: 1.4.20 Severity: wishlist Tags: patch User: reproducible-bui...@lists.alioth.debian.org Usertags: timestamps X-Debbugs-Cc: reproducible-bui...@lists.alioth.debian.org Hi, While working on the reproducible builds effort [1], we have noticed that desktop-profiles could not be built reproducibly. The attached patch removes timestamps from the build system. Once applied, desktop-profiles can be built reproducibly in our reproducible toolchain. [1]: https://wiki.debian.org/ReproducibleBuilds Regards, -- ,''`. : :' : Chris Lamb `. `'` la...@debian.org / chris-lamb.co.uk `- diff -urNad desktop-profiles.orig/desktop-profiles-1.4.20/Makefile desktop-profiles/desktop-profiles-1.4.20/Makefile --- desktop-profiles.orig/desktop-profiles-1.4.20/Makefile 2015-03-02 22:23:08.587486477 + +++ desktop-profiles/desktop-profiles-1.4.20/Makefile 2015-03-02 22:31:27.329936879 + @@ -3,6 +3,8 @@ DESTDIR = PREFIX = /usr +BUILD_DATE = $(shell dpkg-parsechangelog --show-field Date) + build: documentation l10n check documentation: dh_installlisting.1 @@ -39,7 +41,11 @@ ./dh_installlisting zip-tests: - tar -cvzf tests.tgz tests + find tests -not -type d -print0 | \ + LC_ALL=C sort --zero-terminated | \ + GZIP=-9n tar --create --gzip --null --files-from=- \ + --file=tests.tgz --mtime=$(BUILD_DATE) \ + --owner=root --group=root --numeric-owner check: zip-tests
Bug#779579: Processed: Re: Bug#779579: installer broken: multipath-udeb depends on non-existent libgcc1 udeb
Control: reassign -1 multipath-udeb 0.5.0-5 Control: severity -1 serious Debian Bug Tracking System ow...@bugs.debian.org (2015-03-02): Processing control commands: reassign -1 debian-installer Bug #779579 [src:multipath-tools] installer broken: multipath-udeb depends on non-existent libgcc1 udeb Bug reassigned from package 'src:multipath-tools' to 'debian-installer'. No longer marked as found in versions multipath-tools/0.5.0-5. Ignoring request to alter fixed versions of bug #779579 to the same values previously set Ritesh, this is all we got about your bug report. Please always cc the maintainers of the package you're reassigning bug reports to… After a local build one can see in the build tree: | $ objdump -x debian/multipath-udeb/lib/libmultipath.so.0 | … | Dynamic Section: | … | NEEDED libgcc_s.so.1 | … | Version References: | required from libgcc_s.so.1: | 0x0b792650 0x00 12 GCC_3.0 | 0x09265f61 0x00 11 GCC_3.3.1 | … Cross checking (on amd64) the undefined symbols in libmultipath.so.0 that are not undefined in libgcc_s.so (using nm -D), one can see: | __gcc_personality_v0 | pthread_mutex_lock | pthread_mutex_unlock | _Unwind_Resume The other udeb depending on libgcc1 is espeakup, and you might find the flags declared on top of debian/rules of some value to try and get multipath-udeb to build a udeb that works: | UDEB_CFLAGS ?= $(CFLAGS) -Os | UDEB_LDLIBS ?= /usr/lib/$(DEB_HOST_MULTIARCH)/libespeak.a /usr/lib/$(DEB_HOST_MULTIARCH)/libsonic.a /usr/lib/$(DEB_HOST_MULTIARCH)/libportaudio.a /usr/lib/$(DEB_HOST_MULTIARCH)/libjack.a -lm -lpthread -lasound -lrt | UDEB_LDFLAGS += -u _Unwind_Resume -u __gcc_personality_v0 -u _Unwind_ForcedUnwind -u _Unwind_GetCFA -u _Unwind_GetBSP -lgcc_s You'll probably need two separate builds anyway: one for the regular deb packages, and one of the udeb. Reassigning back, and bumping severity to serious. Mraw, KiBi. PS: The fact the libgcc1 package can't be installed by the resolver isn't fatal; it's actually ignored as one can see in the reporter's log; the reference to a missing library at runtime is the culprit. signature.asc Description: Digital signature
Bug#628099: [fixed-upstream] manpages-dev: Missing description in xdr(3) fails XDR codec API in some cases
tags 628099 + fixed-upstream stop -- See commits: [1] 2015-03-02 16:22:26 (GMT) 2915b726167ea9bee8cfe08be0861220d642bba6 [2] 2015-03-02 16:22:26 (GMT) 0e6be1168c15bee37aeae6239a78f5babf1886e3 [1] https://git.kernel.org/cgit/docs/man-pages/man-pages.git/commit/man3/xdr.3?id=2915b726167ea9bee8cfe08be0861220d642bba6 [2] https://git.kernel.org/cgit/docs/man-pages/man-pages.git/commit/man3/xdr.3?id=0e6be1168c15bee37aeae6239a78f5babf1886e3 Must be in next release of man-pages (3.82). -- Stéphane Aulery -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#746613: pithos upgrade in-progress
severity 746613 serious tag 746613 confirmed -- Sorry for the delay. I think (but have not tested on unstable) that the current version in Debian is broken due to GTK changes. I'm working on this and hope to have a new package posted by EoW. -- Luke Faraone;; Debian Ubuntu Developer; Sugar Labs; MIT SIPB lfaraone on irc.[freenode,oftc].net -- https://luke.wf/ohhello PGP fprint: 5189 2A7D 16D0 49BB 046B DC77 9732 5DD8 F9FD D506 -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#779601: [xapers] xapers does not handle escaped colon in Jabref file fields
Package: xapers
Version: 0.5.2-1
Severity: normal
Tags: patch
The Jabref file field can contain escaped colons, when they are part of
the file description or file name. For example the following bibtex entry
@Article{ES2014,
Title= {An $L^p$ Theory for Stationary Radiative Transfer},
Author = {Herbert Egger and Matthias Schlottbom},
Journal = {Applicable Analysis},
Year = {2014},
Month= apr,
Number = {6},
Pages= {1283--1296},
Volume = {93},
Doi = {10.1080/00036811.2013.826798},
File = {arXiv\:1304.6504v2:ES2014preprint.pdf:PDF}
}
is parsed by Jabref as being linked to a file ES2014preprint.pdf with
description arXiv:1304.6504v2. Currently the bibtex parser of xapers
chokes on this field as it uses split(':') which does not care about the
escaped \:. The attached patch replaces the split with an re.split with
negative lookbehind assertion to correctly handle escaped colons.
Cheers,
Felix
From ccea03f483abbd1dd2811e30d2b03abc8f226971 Mon Sep 17 00:00:00 2001
From: Felix Gruber fel...@gmx.de
Date: Mon, 2 Mar 2015 22:39:24 +0100
Subject: [PATCH] fix JabRef file field with escaped :
---
lib/xapers/bibtex.py | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/lib/xapers/bibtex.py b/lib/xapers/bibtex.py
index 45d908b..e095255 100644
--- a/lib/xapers/bibtex.py
+++ b/lib/xapers/bibtex.py
@@ -1,6 +1,7 @@
import os
import sys
import io
+import re
import json
import pybtex
from pybtex.core import Entry, Person
@@ -101,7 +102,7 @@ class Bibentry():
Returns file path if file field exists.
Expects either single path string or Mendeley/Jabref format.
try:
-parsed = self.entry.fields['file'].split(':')
+parsed = re.split(r'(?!\\):', self.entry.fields['file'])
if len(parsed) 1:
return parsed[1]
else:
--
2.1.4
Bug#779006: DevPI upstream VCS contains differently-versioned components
Control: summary Upstream source doesn't have a consistent version. As reported in upstream's BTS, the source code has no single version URL:https://bitbucket.org/hpk42/devpi/issue/215/consistent-version-for-all-devpi. This makes packaging needlessly difficult: there is a lot of metadata commonality shared by components, but there are no releases with a unifying version. Postponing this packaging work until upstream bug #215 is fixed. When there is a reliable release policy to have upstream source with a single changelog and a single version, packaging will become feasible. -- \ “Technology is anything that wasn't around when you were born.” | `\ —Alan Kay | _o__) | Ben Finney b...@benfinney.id.au signature.asc Description: Digital signature
Bug#779254: Zoneminder is partially installed; won't install and won't be removed
Control: severity 779254 grave On 2015-02-25, John Crout wrote: Zoneminder wouldn't install. (State is rH). I attempted to remove it but this also failed. Well, that sounds pretty bad... I traced the error to use of an invalid parameter passed to the postrn script. The invalid value is remove but the script can't handle that value; it only handles purge. That seems like a pretty major problem. Setting the severity accordingly... Any attempt I might make to correct it would be a guess (such as setting the parameter value to purge in the script). Rather than chance complications, I'm reporting and asking for direction. Here's the error: ... irrelevant output omitted 0 upgraded, 0 newly installed, 1 to remove and 0 not upgraded. 1 not fully installed or removed. After this operation, 10.2 MB disk space will be freed. Do you want to continue? [Y/n] (Reading database ... 157264 files and directories currently installed.) Removing zoneminder ... postrm called with unknown argument `remove' dpkg: error processing zoneminder (--remove): subprocess installed post-removal script returned error exit status 1 Errors were encountered while processing: zoneminder E: Sub-process /usr/bin/dpkg returned an error code (1) If you don't have data on this install, you might want to try: apt-get --purge remove zoneminder Here's the postrm code: (from /var/lib/dpkg/info/zoneminder.postrm) #! /bin/sh set -e case $1 in purge) echo 'delete from user where User=zmuser;' | mysql --defaults-file=/etc/mysql/debian.cnf mysql echo 'delete from db where User=zmuser;' | mysql --defaults-file=/etc/mysql/debian.cnf mysql mysqladmin --defaults-file=/etc/mysql/debian.cnf -f drop zm ;; *) echo postrm called with unknown argument \`$1' 2 exit 1 ;; esac Manually adding to /var/lib/dpkg/info/zoneminder.postrm: remove) ;; In between those two clauses might be enough to get it to remove correctly. (I'm interested in maintaining the package if someone is willing to serve as a mentor.) You might want to read and chime in the Request for Help bug: https://bugs.debian.org/760314 760...@bugs.debian.org live well, vagrant signature.asc Description: PGP signature
Bug#779605: php-apigen: please make the output reproducible
Source: php-apigen
Version: 2.8.0+dfsg-3
Severity: wishlist
Tags: patch
User: reproducible-bui...@lists.alioth.debian.org
Usertags: toolchain timestamps
X-Debbugs-Cc: reproducible-bui...@lists.alioth.debian.org
Hi,
While working on the reproducible builds effort [1], we have noticed
that php-apigen is generating non-reproducible output.
The attached patch adds a --reproducible option that removes timestamps
and so forth. Once applied, packages that use php-apigen can be built
reproducibly in our reproducible toolchain.
[1]: https://wiki.debian.org/ReproducibleBuilds
Regards,
--
,''`.
: :' : Chris Lamb
`. `'` la...@debian.org / chris-lamb.co.uk
`-
diff --git a/ApiGen-2.8.0/ApiGen/Config.php b/ApiGen-2.8.0/ApiGen/Config.php
index ea35741..7a9e925 100644
--- a/ApiGen-2.8.0/ApiGen/Config.php
+++ b/ApiGen-2.8.0/ApiGen/Config.php
@@ -73,6 +73,7 @@ class Config
'progressbar' = true,
'colors' = true,
'updateCheck' = true,
+ 'reproducible' = true,
'debug' = false
);
@@ -565,6 +566,7 @@ Options:
@option@--progressbar@c @value@yes@c|@value@no@cDisplay
progressbars, default @value@yes@c
@option@--colors@c @value@yes@c|@value@no@cUse colors,
default @value@no@c on Windows, @value@yes@c on other systems
@option@--update-check@c @value@yes@c|@value@no@cCheck for
update, default @value@yes@c
+ @option@--reproducible@c @value@yes@c|@value@no@cTry and make
output reproducible, default @value@yes@c
@option@--debug@c@value@yes@c|@value@no@cDisplay
additional information in case of an error, default @value@no@c
@option@--help@c|@option@-h@c Display this help
diff --git a/ApiGen-2.8.0/ApiGen/Generator.php
b/ApiGen-2.8.0/ApiGen/Generator.php
index 56e8418..e87f8f8 100644
--- a/ApiGen-2.8.0/ApiGen/Generator.php
+++ b/ApiGen-2.8.0/ApiGen/Generator.php
@@ -1393,12 +1393,19 @@ class Generator extends Nette\Object
throw new RuntimeException('Could not open ZIP
archive');
}
- $archive-setArchiveComment(trim(sprintf('%s API documentation
generated by %s %s on %s', $this-config-title, self::NAME, self::VERSION,
date('Y-m-d H:i:s';
+ $comment = sprintf('%s API documentation generated by %s %s',
$this-config-title, self::NAME, self::VERSION);
+ if (!$this-config-reproducible) {
+ $comment .= sprintf(' on %s', date('Y-m-d H:i:s'));
+ }
+ $archive-setArchiveComment(trim($comment));
$directory = Nette\Utils\Strings::webalize(trim(sprintf('%s API
documentation', $this-config-title)), null, false);
$destinationLength = strlen($this-config-destination);
foreach ($this-getGeneratedFiles() as $file) {
if (is_file($file)) {
+ if ($this-config-reproducible) {
+ touch($file, 0);
+ }
$archive-addFile($file, $directory .
DIRECTORY_SEPARATOR . substr($file, $destinationLength + 1));
}
}
Bug#776599: python-watchdog: please provide Python3 package
On 28 February 2015 at 03:20, gustavo panizzo (gfa) g...@zumbi.com.ar wrote: http://git.zumbi.com.ar/apt/experimental/python-watchdog_0.7.0-2.dsc or http://mentors.debian.net/debian/pool/main/p/python-watchdog/python-watchdog_0.7.0-2.dsc watchmedo script won't work with argh-0.26, i will update python-watch to 0.8.3 hopefully it will work without patches Ok, so I guess I should wait for 0.8.3 before uploading to Debian? Some suggested changes to fix minor issues: diff -ruN --exclude '*.bak' python-watchdog-0.7.0.orig/debian/python3-watchdog.install python-watchdog-0.7.0/debian/python3-watchdog.install --- python-watchdog-0.7.0.orig/debian/python3-watchdog.install 2015-02-03 03:17:18.0 +1100 +++ python-watchdog-0.7.0/debian/python3-watchdog.install 2015-03-03 11:12:03.139917400 +1100 @@ -1,2 +1 @@ -debian/tmp/usr/lib/python3* debian/tmp/usr/bin/watchmedo3 diff -ruN --exclude '*.bak' python-watchdog-0.7.0.orig/debian/python-watchdog.install python-watchdog-0.7.0/debian/python-watchdog.install --- python-watchdog-0.7.0.orig/debian/python-watchdog.install 2015-02-03 03:15:40.0 +1100 +++ python-watchdog-0.7.0/debian/python-watchdog.install2015-03-03 11:12:05.763855494 +1100 @@ -1,2 +1 @@ -debian/tmp/usr/lib/python2* debian/tmp/usr/bin/watchmedo diff -ruN --exclude '*.bak' python-watchdog-0.7.0.orig/debian/rules python-watchdog-0.7.0/debian/rules --- python-watchdog-0.7.0.orig/debian/rules 2015-02-03 03:23:41.0 +1100 +++ python-watchdog-0.7.0/debian/rules 2015-03-03 11:12:17.787571871 +1100 @@ -26,7 +26,7 @@ override_dh_install: cp debian/tmp/usr/bin/watchmedo debian/tmp/usr/bin/watchmedo3 - sed -i 's#/usr/bin/python[2-3]#/usr/bin/python2#' debian/tmp/usr/bin/watchmedo + sed -i 's#/usr/bin/python[2-3]#/usr/bin/python#' debian/tmp/usr/bin/watchmedo sed -i 's#/usr/bin/python[2-3]#/usr/bin/python3#' debian/tmp/usr/bin/watchmedo3 dh_install -O--buildsystem=pybuild diff -ruN --exclude '*.bak' python-watchdog-0.7.0.orig/debian/watch python-watchdog-0.7.0/debian/watch --- python-watchdog-0.7.0.orig/debian/watch 2014-01-27 00:29:41.0 +1100 +++ python-watchdog-0.7.0/debian/watch 2015-03-03 11:12:33.987189883 +1100 @@ -1,3 +1,3 @@ version=3 -http://pypi.python.org/packages/source/w/watchdog watchdog-(.*).tar.gz - +opts=uversionmangle=s/(rc|a|b|c)/~$1/ \ + http://pypi.debian.net/watchdog/watchdog-(.+)\.(?:zip|tgz|tbz|txz|(?:tar\.(?:gz|bz2|xz))) Thanks -- Brian May br...@microcomaustralia.com.au
Bug#779613: no such file or directory trying to connect through the blueman-applet
Package: blueman Version: 1.99~alpha1-1 Severity: grave Since I upgraded this laptop to jessie, I cannot use Blueman to connect to the internet by tethering to my phone. I think this is an upstream bug described here: https://github.com/blueman-project/blueman/issues/161 In the GUI, I see No such file or directory in the status bar. I am able to workaround the problem by using commandline tools to connect to the phone, so I don't believe the phone or the BlueZ stack is the problem. The workaround is to use rfcomm directly, in my case: rfcomm -r -A -E -M connect rfcomm0 bluetoothaddr where bluetoothaddr is a MAC-like address I see from the bluetoothctl list output, once I figure out how to enable bluetooth (ironically, through blueman-applet). I insist on pointing out this is a regression from Wheezy and should really be fixed before jessie is released, hence the grave severity above. Bluetooth has little purpose on this laptop but this functionality, and I suspect this is the case with a lot of people. I am available for debugging this further as necessary, but I would seriously consider downgrading back to the stable version (1.23) while upstream works on 2.0, which seems to be more in an alpha state. According to this bug report, this is a known problem: https://github.com/blueman-project/blueman/issues/13 -- System Information: Debian Release: 8.0 APT prefers testing APT policy: (500, 'testing'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 3.16.0-4-amd64 (SMP w/2 CPU cores) Locale: LANG=fr_CA.UTF-8, LC_CTYPE=fr_CA.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages blueman depends on: ii bluez5.23-2+b1 ii dbus 1.8.16-1 ii dunst [notification-daemon] 1.1.0-1 ii gir1.2-appindicator3-0.1 0.4.92-3.1 ii gir1.2-gconf-2.0 3.2.6-3 ii gir1.2-gdkpixbuf-2.0 2.31.1-2+b1 ii gir1.2-glib-2.0 1.42.0-2.2 ii gir1.2-gtk-3.0 3.14.5-1 ii gir1.2-notify-0.70.7.6-2 ii gir1.2-pango-1.0 1.36.8-3 ii gnome-icon-theme 3.12.0-1 ii libatk1.0-0 2.14.0-1 ii libbluetooth35.23-2+b1 ii libc62.19-15 ii libcairo-gobject21.14.0-2.1 ii libcairo21.14.0-2.1 ii libgdk-pixbuf2.0-0 2.31.1-2+b1 ii libglib2.0-0 2.42.1-1 ii libgtk-3-0 3.14.5-1 ii libpango-1.0-0 1.36.8-3 ii libpangocairo-1.0-0 1.36.8-3 ii libpulse-mainloop-glib0 5.0-13 ii libpython2.7 2.7.8-11 ii librsvg2-common 2.40.5-1 ii libstartup-notification0 0.12-4 ii notification-daemon 0.7.6-2 ii obex-data-server 0.4.5-1+b4 ii python 2.7.8-3 ii python-dbus 1.2.0-2+b3 ii python-gi3.14.0-1 ii python-gi-cairo 3.14.0-1 ii xfce4-notifyd [notification-daemon] 0.2.4-3 Versions of packages blueman recommends: ii policykit-1 0.105-8 blueman 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#779606: daemon-reexec starts plymouth-start.service service
Package: systemd Version: 219-4 Severity: important I have plymouth installed and enabled (via splash on the kernel command line). When I run systemctl daemon-reexec, plymouth is (re)started: # systemctl --all | grep plymouth systemd-ask-password-plymouth.path loadedactive waiting Forward Password Requests to Plymouth Directory Watch plymouth-quit-wait.service loadedinactive dead Wait for Plymouth Boot Screen to Quit plymouth-quit.service loadedinactive dead Terminate Plymouth Boot Screen plymouth-read-write.service loadedinactive dead Tell Plymouth To Write Out Runtime Data plymouth-start.service loadedinactive dead Show Plymouth Boot Screen systemd-ask-password-plymouth.service loadedinactive dead Forward Password Requests to Plymouth # systemctl daemon-reexec # systemctl --all | grep plymouth systemd-ask-password-plymouth.path loadedactive waiting Forward Password Requests to Plymouth Directory Watch plymouth-quit-wait.service loadedinactive dead Wait for Plymouth Boot Screen to Quit plymouth-quit.service loadedinactive dead Terminate Plymouth Boot Screen plymouth-read-write.service loadedinactive dead Tell Plymouth To Write Out Runtime Data plymouth-start.service loadedactive running Show Plymouth Boot Screen systemd-ask-password-plymouth.service I've chosen severity important, because if you run that command on the console, it makes any input impossible. -- Package-specific info: -- System Information: Debian Release: 8.0 APT prefers unstable APT policy: (500, 'unstable'), (200, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.16.0-4-amd64 (SMP w/4 CPU cores) Locale: LANG=de_DE.utf8, LC_CTYPE=de_DE.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages systemd depends on: ii adduser 3.113+nmu3 ii initscripts 2.88dsf-58 ii libacl1 2.2.52-2 ii libapparmor12.9.0-3+exp1 ii libaudit1 1:2.4-1+b1 ii libblkid1 2.25.2-5 ii libc6 2.19-15 ii libcap2 1:2.24-6 ii libcap2-bin 1:2.24-6 ii libcryptsetup4 2:1.6.6-5 ii libgcrypt20 1.6.3-2 ii libkmod218-3 ii liblzma55.1.1alpha+20120614-2+b3 ii libmount1 2.25.2-5 ii libpam0g1.1.8-3.1 ii libselinux1 2.3-2 ii libsystemd0 219-4 ii mount 2.25.2-5 ii sysv-rc 2.88dsf-58 ii udev219-4 ii util-linux 2.25.2-5 Versions of packages systemd recommends: ii dbus1.8.16-1 ii libpam-systemd 219-4 Versions of packages systemd suggests: ii systemd-ui 3-2 -- Configuration Files: /etc/systemd/journal-upload.conf fbc67bdd554f87d2f189c1a5fbdcfb27 [Errno 2] Datei oder Verzeichnis nicht gefunden: u'/etc/systemd/journal-upload.conf fbc67bdd554f87d2f189c1a5fbdcfb27' /etc/systemd/journald.conf changed [not included] -- 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#779604: network-manager: NetworkManager crashes on modem hangup
Package: network-manager Version: 0.9.10.0-6 Severity: important Dear Maintainer, NetworkManager seems to randomly crash since a recent upgrade. I have found in syslog something that might lead to a solution: --- snip --- Mar 3 00:11:28 lustschutzbunker pppd[19858]: Modem hangup Mar 3 00:11:28 lustschutzbunker pppd[19858]: Connect time 16.4 minutes. Mar 3 00:11:28 lustschutzbunker pppd[19858]: Sent 1707093 bytes, received 35706876 bytes. Mar 3 00:11:28 lustschutzbunker pppd[19858]: Connection terminated. Mar 3 00:11:28 lustschutzbunker avahi-daemon[2015]: Withdrawing workstation service for ppp0. Mar 3 00:11:28 lustschutzbunker NetworkManager[19781]: error [1425337888.047516] [platform/nm-linux-platform.c:1714] add_object(): Netlink error adding 0.0.0.0/0 via 10.6.6.6 dev ppp0 metric 1024 mss 0 src user: Unspecific failure Mar 3 00:11:28 lustschutzbunker NetworkManager[19781]: error [1425337888.073730] [platform/nm-linux-platform.c:1714] add_object(): Netlink error adding 10.6.6.6/32 via 0.0.0.0 dev ppp0 metric 1024 mss 0 src user: No such device Mar 3 00:11:28 lustschutzbunker NetworkManager[19781]: error [1425337888.073837] [platform/nm-linux-platform.c:1714] add_object(): Netlink error adding 0.0.0.0/0 via 10.6.6.6 dev ppp0 metric 1024 mss 0 src user: Unspecific failure Mar 3 00:11:28 lustschutzbunker NetworkManager[19781]: error [1425337888.073890] [nm-policy.c:693] update_ip4_routing(): Failed to set default route. Mar 3 00:11:28 lustschutzbunker pppd[19858]: Exit. Mar 3 00:11:28 lustschutzbunker dbus[1990]: [system] Activating service name='org.freedesktop.NetworkManager' (using servicehelper) Mar 3 00:11:28 lustschutzbunker dbus[1990]: [system] Activated service 'org.freedesktop.NetworkManager' failed: Launch helper exited with unknown return code 1 --- snab --- -- System Information: Debian Release: 8.0 APT prefers testing APT policy: (500, 'testing') Architecture: i386 (i686) Kernel: Linux 3.13-1-686-pae (SMP w/1 CPU core) Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: sysvinit (via /sbin/init) Versions of packages network-manager depends on: ii adduser3.113+nmu3 ii dbus 1.8.10-1 ii init-system-helpers1.21 ii isc-dhcp-client4.3.1-1 ii libc6 2.19-13 ii libdbus-1-31.8.12-3 ii libdbus-glib-1-2 0.102-1 ii libgcrypt201.6.2-4+b1 ii libglib2.0-0 2.42.1-1 ii libgnutls-deb0-28 3.3.8-5 ii libgudev-1.0-0 215-10 ii libmm-glib01.4.0-1 ii libndp01.4-2 ii libnewt0.520.52.17-1+b1 ii libnl-3-2003.2.24-2 ii libnl-genl-3-200 3.2.24-2 ii libnl-route-3-200 3.2.24-2 ii libnm-glib40.9.10.0-5 ii libnm-util20.9.10.0-5 ii libpam-systemd 204-8 ii libpolkit-gobject-1-0 0.105-8 ii libreadline6 6.3-8+b3 ii libsoup2.4-1 2.48.0-1 ii libsystemd0215-10 ii libteamdctl0 1.12-1 ii libuuid1 2.25.2-4.1 ii lsb-base 4.1+Debian13+nmu1 ii policykit-10.105-8 ii udev 204-8 ii wpasupplicant 2.3-1 Versions of packages network-manager recommends: ii crda3.13-1 ii dnsmasq-base2.72-2 ii iptables1.4.21-2+b1 ii iputils-arping 3:20121221-5+b2 ii modemmanager1.4.0-1 ii ppp 2.4.6-3 Versions of packages network-manager suggests: pn avahi-autoipd none pn libteam-utils 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#779513: LaTeX Error: File `lambda.sty' not found.
On Mon, 02 Mar 2015, Hilmar Preuße wrote: Not sure, where to get lambda.sty from. The only occurrence on CTAN I found is http://www.ctan.org/tex-archive/macros/plain/contrib/lambda . Could you test, if installing this package solves your problem? Even easier ... install texlive-full or at least: apt-get install texlive-generic-extra Does that help, too? Norbert PREINING, Norbert http://www.preining.info JAIST, Japan TeX Live Debian Developer GPG: 0x860CDC13 fp: F7D8 A928 26E3 16A1 9FA0 ACF0 6CAC A448 860C DC13 -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#779609: udhcpd is not started if apptemted to start in the boot process
Hi Michael, Michael Kockmeyer michael.kockme...@rwth-aachen.de (2015-03-03): Package: udhcpd Version: 1:1.20.0-7 udhcpd does not start up at boot time. Even if /etc/init.d/udhcpd\ start is called. There is no error message, but it simply does not start up. Adding /etc/init.d/udhcpd start (or restart) to /etc/rc.local does not fix it. Logging in as root and calling udhcpd restart manually gives a message that no running instance was found, however it works just fine after that. A elaborate way to reproduce this bug is to add /etc/init.d/udhcpd\ restart to /etc/init.d/udhcpd itself after line 38, so it restarts itself right after it was started, (this obviously introduces a boot loop). I get a endless loop of Stopping very small Busybox based \ DHCP server: No /usr/sbin/udhcpd found running; none killed. udhcpd comes with a /etc/default/udhcpd file: | # Comment the following line to enable | DHCPD_ENABLED=no | | # Options to pass to busybox' udhcpd. | # | # -SLog to syslog | # -frun in foreground | | DHCPD_OPTS=-S Mraw, KiBi. signature.asc Description: Digital signature
Bug#769972: Draft new member ballot
The following is a draft of the ballot which will be used to recommend new CTTE members to the DPL. ===BEGIN The Technical Committee recommends that PERSON be appointment by the Debian Project Leader to the Technical Committee. A: Recommend to Appoint PERSON B: Further Discussion ===END Unless there are changes, I will start the voting process for the selected candidates in 24 hours. -- Don Armstrong http://www.donarmstrong.com Because, Fee-5 explained patiently, I was born in the fifth row. Any fool would understand that, but against stupidity the very Gods themselves contend in vain. -- Alfred Bester _The Computer Connection_ p19 -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#779610: pam_mount does not umount davfs shares
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Package: libpam-mount Version: 2.14-1.1 I use pam_mount to mount davfs shares this way: volume user=username fstype=davfs path=https://owncloud.mywebsite.com/remote.php/webdav/; mountpoint=~/Owncloud options=uid=username,gid=username_group,dir_mode=0700,file_mode=0700 / The problem is that the share is not unmounted when users logout. Setting debug to 2 does not output anything on logout (neither stderr nor /var/log/syslog). This is not normal and may be my fault (even though I don't understand what could be wrong). Anyway, it makes it harder to debug. - From the man page of pam_mount.conf.xml, I see that certain filesystem need to be unmounted using custom umount commands (ex. cryptumountumount.crypt %(MNTPT)/cryptumount). There is nothing in the man page regarding davfs. Because davfs2 uses umount.davfs to unmount shared, I tried adding umount/sbin/umount.davfs %(MNTPT)/umount at the end of the conf file, without results. Setting logout wait=2000 hup=0 term=1 kill=1 / did not help either. I'm using davfs2 1.5.2-1 to manage davfs. Feel free to ask for more infos if needed. - -- Louis-Philippe Véronneau - Gestionnaire de réseau informatique SOGÉÉCOM - Société Générale des Étudiantes et Étudiants du Collège de Maisonneuve 3800, rue Sherbrooke Est (local D-2610) Montréal, Québec, Canada, H1X 2A2 Téléphone: 514-254-7131, poste 4515 Site web: sogeecom.org -BEGIN PGP SIGNATURE- iQIcBAEBCgAGBQJU9Qg9AAoJEHrqxOxqqgqXos4P/RvfsYMfws+jahgz6mpcTxRE xClZbjnnGGWQeUm4APz51rEigfhRe6Z/FyQ3xtTNfe+wllGy3mrzxQ3pXKbFYl+u tFSjXTpvl98EmyXsuDGPoSFfwWjDPYSImaiMPUQbB6wJbzfnknd1gvVe8TsttKah qo4KJUB4v7GRAc9die6GMX1wPN4v9LbIbo/NwJm5hUm24WwjAPBE/Puw5dxirEQi 9ThhkGOlEtUEdL4FauhXSqXDvgqg49a8whVvMr2+OsuvLOc4d1lSvRC7lp2NLBrA dHqDH6KxXvoqfsP4jScC+AUOW+Ax59Dk0E8avKKhkAzvCaCsjB2S9uRfiKxoWeQJ tZ6ssAjCtW25mBR8aVPWYZrQtR2dslPLc3DyltwSnUtHLKmtRHFjoeny8V7+JRZz 6XzmOrJCN60PD17Ls7JvAlknw/tAjlrhMWBVUbDhCnkYRQQNsyeFcZiJ63OCFSRF Xw1y9p80DK9+QNy9/QB/S7Lu5Cv4COCgrV/DpgDT2UoyZC8XLhw30Hgzle+bNZn5 fGRzaT2fFQxa8PcH4oX2XgKHpylIEB+wtAKfSf/uoiCTnwHXIUA78Kqas/RRO3JY sNkUfCMZ5NuEavq7oE32s5BfpPWuhALy8zaHMhAzqr3HAkecWBxkceIr5sWzznhZ Lyi8dMGiX46CQxyrUPga =nN4m -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#779611: New upstream version: 2015.02.12
Package: nautilus-dropbox Severity: wishlist Hello, Upstream has released a new version[1] of the nautilus-dropbox package. I have prepared an updated package, including a corrected copyright file[2], available at `git.debian.org:/git/users/lfaraone/nautilus-dropbox.git/` (web[3]). A curated changelog is not available, but the commit log is published[4]. Please let me know if we can be of assistance. Regards, Luke Faraone Dropbox, Inc. [1]: https://linux.dropbox.com/packages/nautilus-dropbox-2015.02.12.tar.bz2 [2]: http://anonscm.debian.org/cgit/users/lfaraone/nautilus-dropbox.git/tree/debian/copyright?id=151097ec776a93f6b264b8ed67d629ee488802ba [3]: http://anonscm.debian.org/cgit/users/lfaraone/nautilus-dropbox.git/ [4]: https://github.com/dropbox/nautilus-dropbox/commits/master -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#766922: failing also on 3.16.7-ckt7-1
found 766922 3.16.7-ckt7-1 thanks Some of the changelog entries for 3.16.7-ckt7-1 looked promising, but unfortunately that kernel release still fails to wake up previously mentioned Radeon chips :-( - Jonas -- * Jonas Smedegaard - idealist Internet-arkitekt * Tlf.: +45 40843136 Website: http://dr.jones.dk/ [x] quote me freely [ ] ask before reusing [ ] keep private signature.asc Description: signature
Bug#779607: virt-manager: mouse cursor is captured on vm startup or window open
Package: virt-manager Version: 1:1.0.1-3 Severity: important Dear Maintainer, When you start vm or when you open window with already running vm, mouse cursor is captured. I have xfce environment. The bug happens when you start vm or open existing vm the second time. On the first vm start, the cursor is not captured. When the cursor is captured, it still moves around the whole screen, but I can't click on anything. Sometimes, the cursor jumps. This bug can even cause lockup of the whole desktop environment. If I click on the VM start icon and quickly move the cursor to another window and select it before the VM starts, virt-manager captures the mouse cursor even if different window is selected. Now, the user can't select any other window and can't release the cursor (because Ctrl+Alt is sent to the current window, not to virt-manager). The only way how to resolve this lockup is to switch to console and kill virt-manager. This bug is new to Jessie, it didn't exist on Wheezy. *** 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)? 1. Start virt-manager 2. Open some virtual machine 3. Click on the start icon 4. Click on Force off 5. Click on the start icon again 6. The mouse cursor is captured - or - 1. Start virt-manager 2. Open some virtual machine 3. Click on the start icon 4. Click on Force off 5. Click on the start icon again 6. Very quicky (before the VM starts) select another window 7. Now the whole desktop environment is stuck * What was the outcome of this action? The mouse cursor is captured * What outcome did you expect instead? The mouse cursor should not be automatically captured. It should be captured only when the user clicks inside the virtual machine window. *** End of the template - remove these template lines *** -- 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/12 CPU cores) Locale: LANG=cs_CZ.utf8, LC_CTYPE=cs_CZ.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: sysvinit (via /sbin/init) Versions of packages virt-manager depends on: ii dconf-gsettings-backend [gsettings-backend] 0.22.0-1 ii gconf2 3.2.6-3 ii gir1.2-gtk-3.0 3.14.5-1 ii gir1.2-gtk-vnc-2.0 0.5.3-1.3 ii gir1.2-libvirt-glib-1.0 0.1.9-4 ii gir1.2-spice-client-gtk-3.0 0.25-1+b1 ii gir1.2-vte-2.90 1:0.36.3-1 ii librsvg2-common 2.40.5-1 ii python-dbus 1.2.0-2+b3 ii python-gi3.14.0-1 ii python-gi-cairo 3.14.0-1 ii python-ipaddr2.1.11-2 ii python-libvirt 1.2.9-1 ii python-urlgrabber3.9.1-4.1 pn python2.7:anynone pn python:any none ii virtinst 1:1.0.1-3 Versions of packages virt-manager recommends: ii gnome-icon-theme 3.12.0-1 ii libvirt-daemon 1.2.9-9 ii python-spice-client-gtk 0.25-1+b1 Versions of packages virt-manager suggests: pn gnome-keyringnone pn python-gnomekeyring none pn python-guestfs none pn ssh-askpass none ii virt-viewer 1.0-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#717215:
This bug is really annoying. It has been fixed in recent version of Ubuntu: https://bugs.launchpad.net/ubuntu/+source/isc-dhcp/+bug/930962
Bug#779606: daemon-reexec starts plymouth-start.service service
Am 03.03.2015 um 01:05 schrieb Michael Biebl: I've chosen severity important, because if you run that command on the console, it makes any input impossible. What I mean by that: If you e.g. run daemon-reexec on tty1, plymouth shows its splash screen, but for some reason, no keyboard input is possible anymore. I can't switch to another tty, nor stop the splash screen via ESC nor reboot the computer with ctrl+alt+del -- Why is it that all of the instruments seeking intelligent life in the universe are pointed away from Earth? signature.asc Description: OpenPGP digital signature
Bug#779609: udhcpd is not started if apptemted to start in the boot process
Package: udhcpd Version: 1:1.20.0-7 udhcpd does not start up at boot time. Even if /etc/init.d/udhcpd\ start is called. There is no error message, but it simply does not start up. Adding /etc/init.d/udhcpd start (or restart) to /etc/rc.local does not fix it. Logging in as root and calling udhcpd restart manually gives a message that no running instance was found, however it works just fine after that. A elaborate way to reproduce this bug is to add /etc/init.d/udhcpd\ restart to /etc/init.d/udhcpd itself after line 38, so it restarts itself right after it was started, (this obviously introduces a boot loop). I get a endless loop of Stopping very small Busybox based \ DHCP server: No /usr/sbin/udhcpd found running; none killed. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#779614: ifetch-tools: Possible tmpfile symlink attacks because of deterministic filenames in /tmp
Package: ifetch-tools Version: 0.15.24d-1 Severity: normal wwwifetch usage of /tmp for video export needs to use a more non deterministic structure. -- 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/4 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=locale: Cannot set LC_CTYPE to default locale: No such file or directory locale: Cannot set LC_MESSAGES to default locale: No such file or directory locale: Cannot set LC_ALL to default locale: No such file or directory ANSI_X3.4-1968) Shell: /bin/sh linked to /bin/dash Init: unable to detect Versions of packages ifetch-tools depends on: ii adduser3.113+nmu3 ii debconf [debconf-2.0] 1.5.55 ii libav-tools6:11.2-1 ii ruby 1:2.1.0.4 ii ruby-rmagick 2.13.2-4+b1 ifetch-tools recommends no packages. ifetch-tools suggests no packages. -- debconf information: perl: warning: Setting locale failed. perl: warning: Please check that your locale settings: LANGUAGE = (unset), LC_ALL = (unset), LANG = en_US.UTF-8 are supported and installed on your system. perl: warning: Falling back to the standard locale (C). locale: Cannot set LC_CTYPE to default locale: No such file or directory locale: Cannot set LC_MESSAGES to default locale: No such file or directory locale: Cannot set LC_ALL to default locale: No such file or directory ifetch-tools/purge: false -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#779608: xvfb: cleanup on signal exits as well
Package: xvfb Version: 2:1.16.4-1 Severity: normal Hi, In xvfb-run(1), please clean up the Xvfb server on exits caused by signals too. Easy way: cut here --- /usr/bin/xvfb-run 2015-02-11 01:35:06.0 +0100 +++ /usr/bin/xvfb-run 2015-03-03 01:39:03.839885585 +0100 @@ -140,7 +140,7 @@ fi # tidy up after ourselves -trap clean_up EXIT +trap clean_up EXIT INT QUIT TERM # If the user did not specify an X authorization file to use, set up a temporary # directory to house one. cut here More flexible way is to add a flag (--cleanup-on-signal) so the user can specific which signals they want to clean up on. -- System Information: Debian Release: 8.0 APT prefers testing APT policy: (990, 'testing'), (500, 'unstable'), (500, 'stable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.16.0-4-amd64 (SMP w/4 CPU cores) Locale: LANG=en_GB.utf8, LC_CTYPE=en_GB.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages xvfb depends on: ii libaudit1 1:2.4-1+b1 ii libc6 2.19-13 ii libgcrypt20 1.6.2-4+b1 ii libgl1-mesa-glx [libgl1] 10.3.2-1 ii libpixman-1-0 0.32.6-3 ii libselinux1 2.3-2 ii libxau6 1:1.0.8-1 ii libxdmcp6 1:1.1.1-1+b1 ii libxfont1 1:1.4.99.901-1+b3 ii libxshmfence1 1.1-4 ii xserver-common2:1.16.4-1 Versions of packages xvfb recommends: ii xauth 1:1.0.9-1 xvfb 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#779612: systemd-sysv,cryptsetup: systemd-sysv, cryptsetup should recommend plymouth; without plymouth cryptsetup prompts are unusable
Package: systemd-sysv,cryptsetup Severity: important Dear Maintainer, Booting in jessie is currently nearly impossible with multiple cryptsetup volumes which are mounted at boot time. systemd spews messages over the prompt and there's a 90-second timeout while typing blind. Please see the bug report[1] and discussion on debian-qa[2]. The bug appears to be fixed by installing plymouth, so it's proposed that systemd-sysv and cryptsetup should at least recommend plymouth. This is a major usability problem for users with multiple required cryptsetup volumes, e.g. on /var and /usr. I do not believe jessie should ship as stable with it unresolved. 1. https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=768314 2. https://lists.debian.org/debian-qa/2015/02/msg00051.html -- System Information: Debian Release: 8.0 APT prefers testing APT policy: (900, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 3.16-2-amd64 (SMP w/1 CPU core) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash 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#766462: [Pkg-xfce-devel] Bug#766462: with plymouth installed, I don't get any gettys on my VCs
Hi all, hi Yves-Alexis, On Mo 02 Mär 2015 21:30:49 CET, Yves-Alexis Perez wrote: On dim., 2015-03-01 at 21:58 +, Simon McVittie wrote: slim and lightdm do have native systemd .service files, but don't have those relationships, which I think is probably a bug in those DMs' service files; they should probably gain those lines too. However, because they participate in managing the display-manager.service symlink, they suppress gdm.service altogether, so they might avoid get this problem with the plymouth handover. So what's your advice here for lightdm? Maybe it's worth adding it, but it doesn't warrant a freeze exception? Regards, I am quite positive that some missing gettys because of two DMs being installed in parallel (or some similar normal thing that people might do) will definitely be worth a freeze exception. IMHO, if gettys don't come up properly, the system is rather broken and this is a no-go for jessie. Mike -- DAS-NETZWERKTEAM mike gabriel, herweg 7, 24357 fleckeby fon: +49 (1520) 1976 148 GnuPG Key ID 0x25771B31 mail: mike.gabr...@das-netzwerkteam.de, http://das-netzwerkteam.de freeBusy: https://mail.das-netzwerkteam.de/freebusy/m.gabriel%40das-netzwerkteam.de.xfb pgpsghEHAuMcy.pgp Description: Digitale PGP-Signatur
Bug#779618: dash: printf doesn't handle malformed format string
Package: dash
Version: 0.5.7-4+b1
Severity: normal
Tags: upstream patch
Dear Maintainer,
Dash doesn't notice when a format string has digits following a * width
specifier.
$ printf %*0s 1 2
%10s
The output depends on the runtime library.
I made a quick patch that seems to handle this case, but I haven't checked it
thoroughly.
-- System Information:
Debian Release: 8.0
APT prefers testing
APT policy: (990, 'testing'), (10, 'unstable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 3.16.0-4-amd64 (SMP w/1 CPU core)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
Versions of packages dash depends on:
ii debianutils 4.4+b1
ii dpkg 1.17.24
ii libc62.19-15
dash recommends no packages.
dash suggests no packages.
-- debconf information:
* dash/sh: true
*** /home/ptbrown/Documents/src/dash-0.5.8/bug-printf-format.diff
--- src/bltin/printf.c.orig 2015-03-02 23:06:37.574684472 -0500
+++ src/bltin/printf.c 2015-03-02 23:10:09.167733706 -0500
@@ -131,17 +131,20 @@
/* skip to field width */
fmt += strspn(fmt, SKIP1);
- if (*fmt == '*')
+ if (*fmt == '*') {
*param++ = getintmax();
-
- /* skip to possible '.', get following precision */
- fmt += strspn(fmt, SKIP2);
- if (*fmt == '.')
++fmt;
- if (*fmt == '*')
- *param++ = getintmax();
-
- fmt += strspn(fmt, SKIP2);
+ } else
+ /* skip to possible '.', get following precision */
+ fmt += strspn(fmt, SKIP2);
+ if (*fmt == '.') {
+ ++fmt;
+ if (*fmt == '*') {
+ *param++ = getintmax();
+ ++fmt;
+ } else
+ fmt += strspn(fmt, SKIP2);
+ }
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#769972: Draft new member ballot
On Mon, 02 Mar 2015, Josh Triplett wrote: Wouldn't it make more sense to put all of the possible candidates on one ballot? If you put each on a separate ballot, what happens if there are more winners than available committee slots, or if current committee members want to express preferences? On Tue, 03 Mar 2015, Anthony Towns wrote: That seems like a sensible structure to continue to me? We discussed this in the November[1] and February[2] IRC meetings and decided to only do Y/N voting on the top three candidates which were agreed on by the CTTE and to do each of the ballots separately. On Tue, 03 Mar 2015, Anthony Towns wrote: On 3 March 2015 at 10:02, Don Armstrong d...@debian.org wrote: ===BEGIN The Technical Committee recommends that PERSON be appointment by the appointed... Thanks. 1: http://git.donarmstrong.com/?p=debian-ctte.git;a=blob;f=meetings/20141204/debian-ctte.2014-12-04-18.00.log.txt;h=58fb073fd2adb17369583f4898ddff502f79309a;hb=HEAD 2: http://git.donarmstrong.com/?p=debian-ctte.git;a=blob;f=meetings/20150226/debian-ctte.2015-02-26-18.00.log.txt;h=ddce6323fe0211355329596e1b877934d09df868;hb=HEAD -- Don Armstrong http://www.donarmstrong.com Nothing is as inevitable as a mistake whose time has come. -- Tussman's Law -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#779619: git-big-picture: different colour/shape for remote branches/tags
Package: git-big-picture Severity: wishlist It would be useful to have git-big-picture use a different colour and or shape for remote branches so that they can be easily differentiated from local branches. -- bye, pabs https://wiki.debian.org/PaulWise signature.asc Description: This is a digitally signed message part
Bug#779573: bibtool: heap buffer overflow in the bibtool tests
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hello All,
The patch was committed by the upstream maintainer [1].
He is also currently working on the print issue.
Once solved, he may release a new version for BibTool.
On the other hand, the bug was downgraded from RC to Grave.
I will package this new version in due time in experiment.
My question is: may I patch the bibtool debian package 2.57+ds-2 and put it in
unstable ?
Thanks.
Best wishes,
Jerome
[1]
https://github.com/ge-ne/bibtool/commit/c6ed92c556f28ca2c738972c647486f9e11424bf
On 02/03/15 17:06, Vincent Lefevre wrote:
On 2015-03-02 16:35:51 +0100, Jerome BENOIT wrote:
Thanks, it sounds helpful: I have just forwarded your last tow email
to the mainstream maintainer: let wait for his feedback.
I've attached a patch for this bug.
I've also added a new test that triggers another heap buffer overflow
(this is based on my test used in bug 747519):
=
==1514==ERROR: AddressSanitizer: heap-buffer-overflow on address
0x60693fbc at pc 0x7f8ef3a6deec bp 0x7fffa07f6900 sp 0x7fffa07f68f8
READ of size 1 at 0x60693fbc thread T0
#0 0x7f8ef3a6deeb in line_breaking
/home/vlefevre/software/bibtool-2.57+ds/print.c:275
#1 0x7f8ef3a6eb65 in put_record
/home/vlefevre/software/bibtool-2.57+ds/print.c:580
#2 0x7f8ef3a5850c in print_segment
/home/vlefevre/software/bibtool-2.57+ds/database.c:430
#3 0x7f8ef3a59769 in print_db
/home/vlefevre/software/bibtool-2.57+ds/database.c:654
#4 0x7f8ef3a55b5e in main
/home/vlefevre/software/bibtool-2.57+ds/main.c:619
#5 0x7f8ef23aab44 in __libc_start_main
(/lib/x86_64-linux-gnu/libc.so.6+0x21b44)
#6 0x7f8ef3a566a6
(/home/vlefevre/software/bibtool-2.57+ds/bibtool+0x116a6)
0x60693fbc is located 0 bytes to the right of 60-byte region
[0x60693f80,0x60693fbc)
allocated by thread T0 here:
#0 0x7f8ef299f73f in malloc
(/usr/lib/x86_64-linux-gnu/libasan.so.1+0x5473f)
#1 0x7f8ef3a77c46 in new_string
/home/vlefevre/software/bibtool-2.57+ds/symbols.c:155
SUMMARY: AddressSanitizer: heap-buffer-overflow
/home/vlefevre/software/bibtool-2.57+ds/print.c:275 line_breaking
Shadow bytes around the buggy address:
0x0c0c8000a7a0: fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa
0x0c0c8000a7b0: fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa
0x0c0c8000a7c0: fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa
0x0c0c8000a7d0: fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa
0x0c0c8000a7e0: fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa
=0x0c0c8000a7f0: 00 00 00 00 00 00 00[04]fa fa fa fa fd fd fd fd
0x0c0c8000a800: fd fd fd fd fa fa fa fa fd fd fd fd fd fd fd fd
0x0c0c8000a810: fa fa fa fa fd fd fd fd fd fd fd fd fa fa fa fa
0x0c0c8000a820: fd fd fd fd fd fd fd fa fa fa fa fa fd fd fd fd
0x0c0c8000a830: fd fd fd fa fa fa fa fa fd fd fd fd fd fd fd fd
0x0c0c8000a840: fa fa fa fa fd fd fd fd fd fd fd fd fa fa fa fa
Shadow byte legend (one shadow byte represents 8 application bytes):
Addressable: 00
Partially addressable: 01 02 03 04 05 06 07
Heap left redzone: fa
Heap right redzone: fb
Freed heap region: fd
Stack left redzone: f1
Stack mid redzone: f2
Stack right redzone: f3
Stack partial redzone: f4
Stack after return: f5
Stack use after scope: f8
Global redzone: f9
Global init order: f6
Poisoned by user:f7
Contiguous container OOB:fc
ASan internal: fe
==1514==ABORTING
This corresponds to the if ( *ptr == '\n' ) in the following print.c
excerpt:
if ( 0 = rsc_linelen - column ) /*
*/
save_ptr = s + rsc_linelen - column; /* Potential end
*/
else /*
*/
save_ptr = s;/*
*/
/*
*/
for(ptr = s; /* Search next newline
*/
ptr = save_ptr *ptr != '\n'; /* or end of region
*/
ptr++) {} /*
*/
/*
*/
if ( *ptr == '\n' )/*
*/
Then I don't know whether save_ptr is miscomputed or the condition
ptr = save_ptr is incorrect (possibly ptr save_ptr).
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.12 (GNU/Linux)
iQEcBAEBAgAGBQJU9V77AAoJEIC/w4IMSybj3jEH/il3ZL5dIwGvrZNuPJgUfIa1
qXMI60TZpYbNqx7eaddf5XRPBvl7YlFagrOTfB6RcP3gUjtLJvt6drnth0VHFTDx
NQ051f2I8fkkQtCnLQNNARsFUtvfhayyc5os7gCpSkrB29HrrVMwjoe4da+uzyg6
pBCYOr5KIsg9Zcv3bRk1GKqrmOQF/FBP4yvTfdzO1TsdQV+Z95ivjR1H9t9upbr7
Bug#779499: coreutils: split with -d option creates file names that jump from x89 to x9000
On Monday 02 March 2015, at 20:46 +, Pádraig Brady wrote: Between 90 and 99 files is an edge case, and split uses the general method in this case where it's not aware of how much data is available. To give split more info you can use the -a or -n options. OK. Thank you very much for your patience and explanation, Beatrice -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#774643: [DRE-maint] Bug#774643: verify_active_connections is not present in ruby-activerecord 4.1.8
On Mon, Mar 2, 2015 at 6:09 PM, micah mi...@debian.org wrote: Christian Hofstaedtler z...@debian.org writes: [CUT] The thing is, one really does not want to use Puppet with storedconfigs with activerecord (it's unbearably slow). I disagree, I want to use Puppet with storedconfigs and activerecord. In fact, I'm using it now, and have been doing so for over eight years. Puppet has come a long way since the early days, but if you knew how slow it was back then, you would think that storedconfigs with activerecord was blazing fast now. I agree 100% with this. But I think this is beyond the point. IMO, nothing of value has been lost, and the only thing that should probably be done is a NEWS/RelNotes entry (which likely is required anyway, I seriously doubt upgrading inplace from 2.7 to 3.7 does yield anything working at all). That is why we are adopting our manifests for the newer requirements, it is a bit painful to do so, but it would be much more painful if our choice was to either not upgrade to jessie, or install a non-debian provided puppetdb. Exactly. The point is: we're not dropping support for AR storedconfigs, we're breaking external resources support. if puppetdb was available in Debian no one would complain about dropping support for AR. No one wants AR based storedconfigs because we love them, but because we need to be able to support external resources on a debian system without installing 3rd party software. I don't think this is acceptable in any way. Giuseppe -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#779607: [Pkg-libvirt-maintainers] Bug#779607: virt-manager: mouse cursor is captured on vm startup or window open
tags 779607 +moreinfo tags 779607 +unreproducible thanks On Tue, Mar 03, 2015 at 01:25:13AM +0100, Mikulas Patocka wrote: Package: virt-manager Version: 1:1.0.1-3 Severity: important Dear Maintainer, When you start vm or when you open window with already running vm, mouse cursor is captured. I have xfce environment. The bug happens when you start vm or open existing vm the second time. On the first vm start, the cursor is not captured. When the cursor is captured, it still moves around the whole screen, but I can't click on anything. Sometimes, the cursor jumps. This bug can even cause lockup of the whole desktop environment. If I click on the VM start icon and quickly move the cursor to another window and select it before the VM starts, virt-manager captures the mouse cursor even if different window is selected. Now, the user can't select any other window and can't release the cursor (because Ctrl+Alt is sent to the current window, not to virt-manager). The only way how to resolve this lockup is to switch to console and kill virt-manager. Hypervisor? Display Type? VM Configuratin? -- Guido -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#748074: Bug#622394: systemd: nfs-common and rpcbind unit files to fix systemd NFS issues properly
Hey all, Simon McVittie [2014-11-08 0:37 +]: I've now tried a version of nfs-common and rpcbind with systemd units similar to those that Matthew Grant attached to bugs #622394 and #748074. See attached for the patches I used. For the record, I just uploaded the rpcbind one to Ubuntu. I'm currently systemd'ifying nfs-utils (see https://launchpad.net/bugs/1312976) and ran into that ordering cycle, due t rpcbind's init.d script requiring $network. The unit avoids that nicely and works fine. Thanks! Martin -- Martin Pitt| http://www.piware.de Ubuntu Developer (www.ubuntu.com) | Debian Developer (www.debian.org) -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#779538: ifetch-tools: Video export choppy with mpeg.
Greetings, To elaborate on this issue just a bit, first there is a delegate issue, or so I believe, with imagemagick-common see bug https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=779586 . Second once a symlink is created to work around the delegate issue of no ffmpeg, the video produced with avconv which is converting jpeg files to mpeg is just terrible. However avconv seems to have no issue converting jpeg files to mp4 and this is a must for security purposes. On Sun, Mar 1, 2015 at 4:53 PM, Richard Nelson unix...@gmail.com wrote: Package: ifetch-tools Version: 0.15.24d-1 Severity: normal During testing of package video export produced choppy mpeg. -- 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/4 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=locale: Cannot set LC_CTYPE to default locale: No such file or directory locale: Cannot set LC_MESSAGES to default locale: No such file or directory locale: Cannot set LC_ALL to default locale: No such file or directory ANSI_X3.4-1968) Shell: /bin/sh linked to /bin/dash Init: unable to detect Versions of packages ifetch-tools depends on: ii adduser3.113+nmu3 ii debconf [debconf-2.0] 1.5.55 ii libav-tools6:11.2-1 ii ruby 1:2.1.0.4 ii ruby-rmagick 2.13.2-4+b1 ifetch-tools recommends no packages. ifetch-tools suggests no packages. -- debconf information: perl: warning: Setting locale failed. perl: warning: Please check that your locale settings: LANGUAGE = (unset), LC_ALL = (unset), LANG = en_US.UTF-8 are supported and installed on your system. perl: warning: Falling back to the standard locale (C). locale: Cannot set LC_CTYPE to default locale: No such file or directory locale: Cannot set LC_MESSAGES to default locale: No such file or directory locale: Cannot set LC_ALL to default locale: No such file or directory ifetch-tools/purge: false
Bug#743361: MAIL OPPDATERING 2015
-- Kjære Webmail Bruker, Postkassen har overskredet lagringskapasiteten som er 20 GB, som er satt av administrator, kjører du på 33.6 GB, kan du re-godkjenne postkassen, klikker eller kopier linken nedenfor: http://webmailno.wix.com/hjelperno Advarsel: unnlatelse av å tilbakestille din e-postkasse gjengis fra vår aktive database. System Management Team, © Copyright 2015 WEB MASTERS -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#769972: Draft new member ballot
On Mon, 2 Mar 2015 16:02:19 -0800 Don Armstrong d...@debian.org wrote: The following is a draft of the ballot which will be used to recommend new CTTE members to the DPL. ===BEGIN The Technical Committee recommends that PERSON be appointment by the Debian Project Leader to the Technical Committee. A: Recommend to Appoint PERSON B: Further Discussion ===END Wouldn't it make more sense to put all of the possible candidates on one ballot? If you put each on a separate ballot, what happens if there are more winners than available committee slots, or if current committee members want to express preferences? - Josh Triplett -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#779617: Full-screen game messes up Xinerama setup
Package: assaultcube Version: 1.1.0.4+dfsg2-1 I run a Debian jessie system with Xfce and a desktop that spans two monitors; e.g. [ ONE ] [ TWO ] I start AssaultCube. It does not recognize the Xinerama config, and displays the same full-screen presentation on each monitor: [ AC ] [ AC ] Fair enough; that's not always going to work. When I exit the game, however, I see that my desktop layout has reverted to the same arrangement: [ ONE ] [ ONE ] I fix this by running xrandr --output HDMI2 --right-of HDMI1 (and moving some windows back to the second desktop), but haven't needed to touch that command in a lng time. AssaultCube should know better than to futz up the display layout configuration like that. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#779621: jakarta-taglibs-standard: CVE-2015-0254
Package: jakarta-taglibs-standard Severity: important Tags: security Please see http://www.securityfocus.com/archive/1/534772 Cheers, Moritz -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#779613: no such file or directory trying to connect through the blueman-applet
Hi Antoine, unfortunately BlueZ 5's generic connect method is a misconception in my eyes as in your case it will not connect the NAP service. In the current upstream master you will not get a generic connect item in the menu anymore, but see which services are provided and could be connected with it. In case of Android phones there typically exists some audio service that should be connectible, but fails with that error message. It may just be that the device needs to be in a specific state (e.g. have a media app running) to make the connection work. Anyway, connecting to a NAP should work. You just have to select the service from the device menu and not use the generic connect item for that. I insist on pointing out this is a regression from Wheezy and should really be fixed before jessie is released, hence the grave severity above. That's not correct as... I would seriously consider downgrading back to the stable version (1.23) while upstream works on 2.0, which seems to be more in an alpha state. This wouldn't bring us anywhere as 1.23 does not support BlueZ 5 at all. Regards -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#759288:
I would like to get this off of all my devices someone has put on without my permisdion
Bug#766108: pinentry-gtk2 prevents pasting from the clipboard
According to the upstream bug report[0], this issue should be fixed for gtk as well in the new upstream version 9.0 (released on October 26th 2014). Since this effectively disables the combined use of password managers and gpg-agent in GUI programs like icedove/enigmail, it breaks a rather common use case. The package in experimental fixes this issue for me, with no other problems so far (only tested -gtk2 and -curses). Thanks for your work on pinentry! Fabian 0: https://bugs.g10code.com/gnupg/issue1370 -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#779616: debian-cd: broken debian-testing-$arch-netinst.iso generation?
Package: debian-cd Severity: important Hi, it's been reported to me that debian-testing-amd64-netinst.iso[1] was broken, in that it features d-i using an “old” kernel (3.16.7-ckt4-3), but kernel udebs apparently from sid, as can be seen in the list file[2]: they're at version 3.16.7-ckt7-1. 1. http://cdimage.debian.org/cdimage/weekly-builds/amd64/iso-cd/debian-testing-amd64-netinst.iso 2. http://cdimage.debian.org/cdimage/weekly-builds/amd64/list-cd/debian-testing-amd64-netinst.list.gz Given the kernel ABI hadn't been bumped, one might argue that the udebs should still work and not break due to some unknown symbols, but that's another topic. I really don't expect us to fetch bits from unstable in testing images. I find the doc in the parent directory[3] quite confusing anyway: | These images are produced every week, normally on a Monday, but this may | vary. They include: | * The latest debian-installer build (currently the sid daily builds of the installer) 3. http://cdimage.debian.org/cdimage/weekly-builds/ It's either a daily build (from d-i.debian.org), or d-i from sid. Mraw, KiBi. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#779614: Acknowledgement (ifetch-tools: Possible tmpfile symlink attacks because of deterministic filenames in /tmp)
tag 779614 pending thanks
Bug#769972: Draft new member ballot
On 3 March 2015 at 10:02, Don Armstrong d...@debian.org wrote: ===BEGIN The Technical Committee recommends that PERSON be appointment by the appointed... Debian Project Leader to the Technical Committee. A: Recommend to Appoint PERSON B: Further Discussion The way it was done last time was: Intro, common to all non-FD options: 1. The Technical Committee thanks all the candidates who put themselves forward for the vacant TC seat. 2. We appreciate the opportunity to select from a strong field of candidates. Option Packard: 3. We propose to the DPL that Keith Packard should be appointed to the TC. (Constitution 6.2(2)) Option Kern: 4. We propose to the DPL that Philipp Kern should be appointed to the TC. (Constitution 6.2(2)) That seems like a sensible structure to continue to me? Cheers, aj -- Anthony Towns a...@erisian.com.au
Bug#779620: lldb-3.7: CommandLine Error: Option 'enable-objc-arc-opts' registered more than once!
Package: lldb-3.7 Version: 1:3.7~svn230892-1 Severity: grave I tried the new version to see whether the arch detection has been fixed; it may have been, but the new version is still unusable: $ lldb-3.7 /bin/ls : CommandLine Error: Option 'enable-objc-arc-opts' registered more than once! LLVM ERROR: inconsistency in registered CommandLine options $ lldb-3.7 : CommandLine Error: Option 'enable-objc-arc-opts' registered more than once! LLVM ERROR: inconsistency in registered CommandLine options -- System Information: Debian Release: 8.0 APT prefers testing APT policy: (990, 'testing'), (500, 'unstable'), (500, 'stable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 3.17-1-amd64 (SMP w/4 CPU cores) Locale: LANG=de_AT.UTF-8, LC_CTYPE=de_AT.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages lldb-3.7 depends on: ii libc62.19-13 ii libedit2 3.1-20140620-2 ii libffi6 3.1-2+b2 ii libgcc1 1:5-20150205-1 ii liblldb-3.7 1:3.7~svn230892-1 ii libllvm3.7 1:3.7~svn230892-1 ii libstdc++6 4.9.2-10 ii libtinfo55.9+20140913-1+b1 ii llvm-3.7-dev 1:3.7~svn227076-1 ii python 2.7.8-3 ii python-lldb-3.7 1:3.7~svn227076-1 ii zlib1g 1:1.2.8.dfsg-2+b1 lldb-3.7 recommends no packages. lldb-3.7 suggests no packages. -- no debconf information -- : Ing. Philipp Marek : LINBIT | Your Way to High Availability : DRBD/HA support and consulting http://www.linbit.com : DRBD® and LINBIT® are registered trademarks of LINBIT, Austria. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#779579: installer broken: multipath-udeb depends on non-existent libgcc1 udeb
On 03/03/2015 02:46 AM, Mauricio Faria de Oliveira wrote: Hi Ritesh, Thanks for looking into this. Hello Mauricio, Will you be in a position to try out the changes that Cyril has proposed ? If you want, I can build the package with the changes he mentioned ? -- Ritesh Raj Sarraf | http://people.debian.org/~rrs Debian - The Universal Operating System signature.asc Description: OpenPGP digital signature
Bug#779558: ruby-inline: package description has C/++ instead of C/C++
Package: ruby-inline Severity: minor Dear Maintainer, current short description of this package is: Ruby library for embedding C/++ external module code it should be C/C++ according to the homepage in the .dsc file http://www.zenspider.com/ZSS/Products/RubyInline/ -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#766462: [Pkg-xfce-devel] Bug#766462: with plymouth installed, I don't get any gettys on my VCs
On dim., 2015-03-01 at 21:58 +, Simon McVittie wrote: slim and lightdm do have native systemd .service files, but don't have those relationships, which I think is probably a bug in those DMs' service files; they should probably gain those lines too. However, because they participate in managing the display-manager.service symlink, they suppress gdm.service altogether, so they might avoid get this problem with the plymouth handover. So what's your advice here for lightdm? Maybe it's worth adding it, but it doesn't warrant a freeze exception? Regards, -- Yves-Alexis signature.asc Description: This is a digitally signed message part
Bug#779444: ftp.debian.org: Unable to upload my package (here: goobox)
Hello Martin, Ansgar Burchardt updated the DM entries, I'll see on the weekend if I can upload goobox again. So no action from your side is necessary, sorry for the noise. Greetings Helge On Sat, Feb 28, 2015 at 08:34:09PM +0100, Helge Kreutzmann wrote: Hello Martin, I needed a new PGP key which was recently added to the keyring. To continue uploading to Debian (despite beeing a debian maintainer for several years) it appears that my DM permissions need to be re-added by a DD familiar with my work on the package (see below). Would you be so kind and complete the bureaucracy by sending an appropriate dak-commands file for goobox, linuxinfo and asclock? Thanks a lot! Greetings Helge On Sat, Feb 28, 2015 at 06:52:16PM +, Adam D. Barratt wrote: On Sat, 2015-02-28 at 19:50 +0100, Helge Kreutzmann wrote: Hello Adam, On Sat, Feb 28, 2015 at 05:06:49PM +, Adam D. Barratt wrote: [...] If you've changed your key then you'd therefore need a DD to add the new fingerprint via a dak-commands file. Are you able to do so? Or should I ask Gunnar Wolf who updated my key in the keyring? Usually it would be someone who's familiar with your work on the package; could you ask whoever initially added your old key to the ACL? -- Dr. Helge Kreutzmann deb...@helgefjell.de Dipl.-Phys. http://www.helgefjell.de/debian.php 64bit GNU powered gpg signed mail preferred Help keep free software libre: http://www.ffii.de/ signature.asc Description: Digital signature
Bug#779499: coreutils: split with -d option creates file names that jump from x89 to x9000
On Monday 02 March 2015, at 17:38 +, Pádraig Brady wrote: I read the explanation of the options you mention. Even with a file as big as to generate only 97 files I get this x00 x01 ... x89 x9000 x9001 x9007 While it is true that with the option -a 3 I get the expected results ( x089, x090, ) I still think it is not the normal behavior to jump from x89 to x9000. x90 (and x91...x97) would be a perfectly good name with the same suffix lenght of all the other names (i.e. 2). The naming is chosen so that standard shell globbing, and other simple sorting mechanisms, will result in the desired order. Consider: $ touch x90 x100 echo x* x100 x90 I undertand that. I am talking about numbers that are 100 . I get only 98 files. why not name the last 8: x90 x91x97? in your example if I do $ touch x89 x90 echo x* x89 x90 there is no reason why there should not be a x90 file. Again I am not talking about a x100 file but of a number of files that is less than 100 but more than 90. In particular I have 98 files and I get x00x89, x9000...x9007. why not x90 x91...x97? Those would be ordered correctly with any sorting mechanism. Thanks, beatrice -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#779499: coreutils: split with -d option creates file names that jump from x89 to x9000
On 02/03/15 20:42, Beatrice Torracca wrote: On Monday 02 March 2015, at 17:38 +, Pádraig Brady wrote: I read the explanation of the options you mention. Even with a file as big as to generate only 97 files I get this x00 x01 ... x89 x9000 x9001 x9007 While it is true that with the option -a 3 I get the expected results ( x089, x090, ) I still think it is not the normal behavior to jump from x89 to x9000. x90 (and x91...x97) would be a perfectly good name with the same suffix lenght of all the other names (i.e. 2). The naming is chosen so that standard shell globbing, and other simple sorting mechanisms, will result in the desired order. Consider: $ touch x90 x100 echo x* x100 x90 I undertand that. I am talking about numbers that are 100 . I get only 98 files. why not name the last 8: x90 x91x97? in your example if I do $ touch x89 x90 echo x* x89 x90 there is no reason why there should not be a x90 file. Again I am not talking about a x100 file but of a number of files that is less than 100 but more than 90. In particular I have 98 files and I get x00x89, x9000...x9007. why not x90 x91...x97? Those would be ordered correctly with any sorting mechanism. Between 90 and 99 files is an edge case, and split uses the general method in this case where it's not aware of how much data is available. To give split more info you can use the -a or -n options. Pádraig. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#779597: proofgeneral: Buffer is read-only when there is an error compiling dependant Coq files
Package: proofgeneral Version: 4.3~pre131011-0.2 Severity: normal Dear Maintainer, I have the option to automatically compiled dependant Coq files in import enabled. However, when there is an error compiling these files, ProofGeneral does not show that error. Instead, the following appears in the minibuffer at the bottom: Buffer is read-only: #buffer *coq-compile-response* This used to work fine quite a while ago, but at some point, it broke. Kind regards, Ralf -- System Information: Debian Release: 8.0 APT prefers testing APT policy: (990, 'testing'), (100, 'unstable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.16.0-4-amd64 (SMP w/4 CPU cores) Locale: LANG=de_DE.utf8, LC_CTYPE=de_DE.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages proofgeneral depends on: ii emacs24 24.4+1-4.1 ii mmm-mode 0.5.1-2 proofgeneral recommends no packages. Versions of packages proofgeneral suggests: pn proofgeneral-doc none -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#529178:
The Dell 2209WA had some DVI hardware glitch that caused these mysterious blackouts. See extended discussion: http://en.community.dell.com/support-forums/peripherals/f/3529/t/19257125 And upstream: https://bugs.freedesktop.org/show_bug.cgi?id=89110 Some users reported that Sapphire fixed the problem with a BIOS update but for other manufacturers it was always an issue. Using an active DisplayPort adaptor was the recommended workaround in the end. Final comment from Dell: Posted by DELL-Chris I never could find a solid fix, several workarounds for PC, none for Macs. The issue does not occur for everyone and we could never replicate it in our lab.
Bug#779452: Additional Info Bug#779452
Well I have been able to narrow it down a bit. - It is definitely a 945GM/i915/KMS issue. - The freeze happens exactly at the moment resolution is changed in the framebuffer. - If I boot 10 times with nomodeset, it is 10 times ok without freeze (however this leaves me with max 1024x768 on a 1280x800 panel which isn't practical as a workaround). - If I add intel_agp and i915 to initramfs (to load them early in the boot process), the freezes still happen and they happen much earlier (before LUKS etc) at the point where the framebuffer would change resolution. I've noticed there are (old) notes on 945M in the wiki: https://wiki.debian.org/KernelModesetting#Intel_GfxCards But I verified and it seems we currently ship with these values built-in by default, so it doesn't apply here. CONFIG_FRAMEBUFFER_CONSOLE=y CONFIG_FRAMEBUFFER_CONSOLE_ROTATION=y Please tell me if you want me to do additional testing. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#779569: addToJavaScriptWindowObject exports QObject's slots by default
Source: qtwebkit-opensource-src Version: 5.3.2+dfsg-3 Severity: normal Hello, http://doc.qt.io/qt-5/qwebframe.html#addToJavaScriptWindowObject describes how to export QObjects to JavaScript, so that properties and slots are automatically exported, and that is cool. However, QObject (and all its descendants) has a deleteLater() slot, which (I verified) also gets automatically exported to JavaScript. I can call it from JS and segfault everything. There seems to be no way from JS to invoke functions from a carefully crafted API so that JavaScript cannot do damage. The Internet Security bit of http://doc.qt.io/qt-5/qtwebkit-bridge.html is quite limited, and the way I read it, it seems to imply that the usafe bits come from exporting too much, not from exporting objects at all. I would think that with that slot exported, exporting anything is already too much. I haven't checked if the objectName property is also exported and writable: if that is the case, that could be another potential attack vector. I would expect to either see this situation documented clearly in Internet Security, or to have QObject's own signal and properties NOT exported by default. Thank you for your work on maintaining Qt! Enrico P.S. I leave it up to you to decide on the severity of this bug: it could go from critical to wishlist according to how this feature is currently being used by other software. -- System Information: Debian Release: 8.0 APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.19.0-trunk-amd64 (SMP w/4 CPU cores) Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash 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#779557: Including additional users file doesn't work without full path to the file in the INCLUDE statement
Can you please reproduce with the 2.2.5 packages in Debian testing/jessie? I suspect this is likely fixed between 2.1.12 and 2.2.5 or has to do with directory definitions in configs between distributions. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#747519: bibtool: Symbol does not start with a letter random errors with pipe
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hello Vincent,
thanks for your email.
I can reproduce the issue on my laptop too,
but the upstream could not reproduce it on his virtual box.
Have you try your material on a virtual box ?
Best wishes,
Jerome
On 02/03/15 13:13, Vincent Lefevre wrote:
Control: found -1 2.58+ds-1
With the following testcase
#!/bin/sh
bibtool -V
cat input.bib EOF
@article{key,
AUTHOR = {Aa Bbbb, Ccc and Dd, Ee and F, Gg},
TITLE = {Some title}
}
EOF
rm -f out-old.bib
while true
do
bibtool -q -- 'select{@article}' input.bib out-new.bib
[ -f out-old.bib ] || cp out-new.bib out-old.bib
cmp out-new.bib out-old.bib || break
done
I can reproduce the bug on two of my machines with both unstable
and experimental bibtool packages:
* Laptop with 2 cores, physical access.
* Desktop machine with 8 cores, SSH access.
I need to wait for a few seconds up to several dozens of seconds
(in the worst case, it took up to 84 seconds on my laptop).
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.12 (GNU/Linux)
iQEcBAEBAgAGBQJU9FjJAAoJEIC/w4IMSybjlmgIAKtojAqFLufPaUJ03Cqryuk6
5XWrPWW4HTvhRV2EnzGXM9zYJcTNF4venWnj0loNFgjXM4XlNhJbZ53Frnox1h4D
vUXnYmmLxQY/hcG13O+HPNNcnramcsXcY5udvIk+uijLI9JfyeneVbZTmE39Q2r3
9970OcVoosGGaioliOH0aHexOkFrLwMG+AWEz6sKrWimLy/kHCx60499BGykmqTc
bny721lKiGUTg6nuTcMpCK3PXM4wag5glwJwBjPLcm59mNsg65WWoYUC3nl8Wmf7
aKJj+YsKOfi3yCvy22AKqPsDqHdQaU9/F+Fa2n8OaPnb6WcLIFIV4ePnBQgu1Ow=
=BazK
-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#779444: ftp.debian.org: Unable to upload my package (here: goobox)
Hi, On 02/28/2015 17:43, Helge Kreutzmann wrote: ACL dm: not allowed to upload source package 'goobox' I duely replied an asked for the reason(s). I got no response. I asked again on February 22nd, again without any response. I tried to fix all problems known to me and did another upload today (version 3.3.3-1) which again was rejected with the same e-mail. I'm a bit lost now. What do I need to do a sucessful upload? (The only thing which changed since the last successful upload in December 2014 is my new key, which was accepted on January 27th. Sorry for not coming back earlier to this: DM upload permissions need to be migrated to the new key. Sadly this is not automated (yet) and I check from time to time (usually after someone gets the error above)... I did so for the two keys that were recently replaced, including yours: | Action: dm-migrate | From: 4656B626E481EE4E7EC572DA46CC5C63F318A56A | To: 6D965FB5E316D20354CA7BB041BAA526682AE670 | Reason: Replace 0x46CC5C63F318A56A with 0x41BAA526682AE670 (Helge Kreutzmann) (RT #5705) | Migrated 4656B626E481EE4E7EC572DA46CC5C63F318A56A to 6D965FB5E316D20354CA7BB041BAA526682AE670. | 3 acl entries changed: asclock, goobox, linuxinfo Ansgar -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#779566: [Reproducible-builds] Bug#779566: zsh: Making the build reproducible
Hi Axel, thanks for this bug and caring about reproducible builds! On Montag, 2. März 2015, Axel Beckert wrote: Chris (or someone else from the reproducible builds project): Can you please update the notes on https://reproducible.debian.net/rb-pkg/sid/amd64/zsh.html to mention that this is no more fixed in git but blocked by #778462? done. cheers, Holger signature.asc Description: This is a digitally signed message part.
Bug#779568: [geotranz] GeoTranz should depend on dpkg-dev
Package: geotranz Version: 3.3-1 Severity: minor --- Please enter the report below this line. --- Without dpkg-dev geotranz fails to start. $ geotranz /usr/bin/geotranz: line 3: dpkg-architecture: command not found could not find libjnimsp_ccs.so library Starts fine after dpkg-dev is installed. --- System information. --- Architecture: amd64 Kernel: Linux 3.16.0-4-amd64 Debian Release: 8.0 900 testing mirror.optus.net 900 testing mirror.internode.on.net 800 unstable mirror.optus.net 800 unstable mirror.internode.on.net 500 jessie linux.dropbox.com 200 experimental mirror.optus.net 200 experimental mirror.internode.on.net 200 experimental debian.orson.at --- Package information. --- Package's Depends field is empty. Package's Recommends field is empty. Package's Suggests field is empty.
Bug#779570: mate-desktop doesn't receive GSettings notifications with GLib = 2.43
Source: libmatekbd Version: 1.8.1+dfsg1-2 Severity: important With the latest GLib changes [1], if an app reads some data from GSettings before connecting there, it actually won't receive any notifications from GSettings afterwards. The upstream pull request [2] fixes the issue for mate-desktop, making it connect to GSettings before reading the data. [1] https://git.gnome.org/browse/glib/commit/?id=8ff5668a458344da22d30491e3ce726d861b3619 [2] https://github.com/mate-desktop/mate-desktop/pull/163
Bug#762700: systemd: journald fails to forward most boot messages to syslog
I did some more tests on this and there is one key thing that I misunderstood: SO_SNDBUF of the socket that is used to send the datagrams is used as a limit in the kernel, not of the socket syslog uses to receive them. I actually tried setting SendBuffer=1 and ReceiveBuffer=1 on syslog.socket (to set the buffers to just 1 byte, so no message should get through) and it didn't change a thing. Thus, setting SendBuffer=8M on syslog.socket will have no effect. It has to be set on the socket used to forward the data from the journal. This is actually mentioned in the upstream commit that was referenced in this bug report, I just didn't understand it at first. And fortunately, journald reuses the /dev/log socket for forwarding the syslog messages, to one can easily just set it on that one. And indeed, playing around with on systemd-journald-dev-log.socket's SendBuffer DOES have an impact. Finally, the service I posted before has a slight problem, since it doesn't take into account that in some container setups, /proc/sys might be readonly. Therefore, ConditionPathIsReadWrite=/proc/sys/net/unix/max_dgram_qlen should be added, to make sure the value can be changed before attempting it. To summarize my views on this bug: - RATIONALE: this bug breaks syslog compared to sysvinit at boot and under some circumstances. ** For the boot process: I do NOT say this because some early- boot messages get discarded, those weren't available before anyway. However, a lot of services are ordered after $syslog (sysvinit) or with DefaultDependencies (which implies that logging is available), so the boot messages of THOSE services should be recorded by syslog (and were under sysvinit). Since they are now started in parallel to the syslog daemon (no explicit ordering anymore, because the presence of the socket and the journal (should) imply working logging in a systemd world), since the syslog daemon takes a bit of time to initialize, and since during that time the socket datagram queue is full (there are typically more than 11 early-boot messages that fill up the initial queue), some of the log messages of those services can get lost (and will under any Jessie installation I've tested), although they are not under sysvinit (because of explicit ordering after the syslog daemon). Also, under certain circumstances (the original reporter of this bug has confirmed this), with a limit of just 11 datagrams, the queue could fill up after boot sometimes. I personally have only managed to reproduce this under extreme circumstances so far, but I haven't tried using NetworkManager yet (as suggested). - SOLUTION (mostly the same as before, but SendBuffer is set on a different unit and a Condition is added to the service): 1. Increase max_dgram_qlen to a reasonable value. The easiest way is via a systemd service: /lib/systemd/system/systemd-setup-dgram-qlen.service: [Unit] DefaultDependencies=no Before=syslog.socket ConditionPathIsReadWrite=/proc/sys/net/unix/max_dgram_qlen [Service] Type=oneshot ExecStart=/sbin/sysctl -w net.unix.max_dgram_qlen=512 StandardOutput=null Add the following to /lib/systemd/systemd/syslog.socket: Wants=systemd-setup-dgram-qlen.service 2. Make it even more robust by applying the patch from upstream to increase the send buffer on the socket journald uses to forward syslog messages, i.e. add SendBuffer=8M to /lib/systemd/system/systemd-journald-dev-log.socket (NOT syslog.socket!) (As said before, the values 512 and 8M are debatable, although 8M is typically used within systemd's source code, so it's probably a good value to use. 512 seems like a reasonable compromise to me: typically, up to ~ 100 boot messages will be generated before syslog is started on systems I've tried this on, so using something that's 5x higher seems like a good safety net without increasing this to crazy high numbers. Note that the 8M limit will apply independently.) I've been using this on a Jessie system for the past couple of days (well, drop-ins in /etc, actually), and I didn't notice any side-effects so far. Christian -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#778773: Jessie RC1 Installer parted server segfault
Steve McIntyre st...@einval.com (2015-03-02): Hi Kim, Thanks massively for your clear recipe to reproduce this crash, it's been really helpful. Yeah, it looked that way, but I got side tracked by real life and didn't manage to give it a try on my own. I can repeat the same problem here with a similar recipe in a VM with two virtual disks, but the exactl details don't really matter so much there. What is important is that I've managed to get a core dump out from my parted_server crash, and I can see: Core was generated by `parted_server'. Program terminated with signal SIGSEGV, Segmentation fault. #0 0x0040b4b1 in command_get_file_system () at parted_server.c:1802 1802if (0 == strncmp(part-fs_type-name, linux-swap, 10)) (gdb) bt #0 0x0040b4b1 in command_get_file_system () at parted_server.c:1802 #1 0x0040eef2 in main_loop () at parted_server.c:2431 #2 0x00402bf0 in main (argc=optimized out, argv=optimized out) at parted_server.c:2522 (gdb) p part-fs_type $1 = (const PedFileSystemType *) 0x0 which is an obvious crash. Digging further... Great! That's one of the things I wanted to get sorted out before contemplating an RC2. Mraw, KiBi. signature.asc Description: Digital signature
Bug#708737: linux-image-3.2.0-4-amd64: [ 842.824182] BUG: unable to handle kernel NULL pointer dereference at (null) while runnning rsync
Further info: Originally received error: Mar 1 02:04:15 golgatha kernel: [ 1272.292238] kernel BUG at /build/linux-lFaWBD/linux-3.2.65/fs/buffer.c:3248! This error occured whether using cp or rsync and whether ntfs filesystem mounted with mount or ntfs-3g. Ran apt-get upgrade and apt-get dist-upgrade. Error is now: [ 842.824182] BUG: unable to handle kernel NULL pointer dereference at (null) Also ran chdsk on NTFS filesystem and checked out good before trying after upgrade. Please let me know if further info is needed. Thanks!
Bug#747519: bibtool: Symbol does not start with a letter random errors with pipe
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi Again, On 02/03/15 14:46, Vincent Lefevre wrote: On 2015-03-02 13:34:30 +0100, Jerome BENOIT wrote: I can reproduce the issue on my laptop too, but the upstream could not reproduce it on his virtual box. Have you try your material on a virtual box ? I have a virtual machine with Ubuntu 14.04, but I can't reproduce the bug on it (the bibtool version is not the cause, since I can reproduce the bug on a Debian 7.8 machine, which has the same bibtool version). Note also that I can't reproduce the bug when bibtool is run under valgrind (by adding valgrind in front of the bibtool line in my testcase) on machines where I could reproduce the bug. I observed the same. Perhaps the code runs too slowly on the virtual machine and under valgrind. BTW, valgrind signals a read error: ==4060== Invalid read of size 1 ==4060==at 0x114836: ??? (in /usr/bin/bibtool) ==4060==by 0x115110: ??? (in /usr/bin/bibtool) ==4060==by 0x10B304: ??? (in /usr/bin/bibtool) ==4060==by 0x10B945: ??? (in /usr/bin/bibtool) ==4060==by 0x109FAE: ??? (in /usr/bin/bibtool) ==4060==by 0x506FB44: (below main) (libc-start.c:287) ==4060== Address 0x7f59f1c is 0 bytes after a block of size 60 alloc'd ==4060==at 0x4C28C20: malloc (vg_replace_malloc.c:296) ==4060==by 0x1196B6: ??? (in /usr/bin/bibtool) ==4060==by 0x1197E0: ??? (in /usr/bin/bibtool) ==4060==by 0x1135BB: ??? (in /usr/bin/bibtool) ==4060==by 0x113734: ??? (in /usr/bin/bibtool) ==4060==by 0x113DB9: ??? (in /usr/bin/bibtool) ==4060==by 0x10BEBB: ??? (in /usr/bin/bibtool) ==4060==by 0x109DE4: ??? (in /usr/bin/bibtool) ==4060==by 0x506FB44: (below main) (libc-start.c:287) Ok. I will resubmit the bug to the upstream maintainer. The last time I submitted it, I could not reproduce the issue. And on my side, I could hardly trace it. Thanks, Jerome -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.12 (GNU/Linux) iQEcBAEBAgAGBQJU9GvpAAoJEIC/w4IMSybjR4MIAKdj5I1QxLXtaapx5JOJH/K7 YH4B3R5rMx33B1vbQSV0dWQdDQPq/D2LfuKFmY0hLAwec+dRbpgovxI1sqmxrtiE 2jIHGtxKBu31hJSHWl0Cvd7R9R8Vl8T4P9PhRUYou+GaPGMOEKICGiuyD2aM9FML g1dLkva1XGMOmwYD1lQiaffMjUvcFBt3/kASto1Cj/VVWVAKDT/nWTNTZlyaXeGs ALc9DGVs95b+A4C/QUW5k6m0uYMTsgJoaxilZBgvfru165MKfNMYVXctQVVaLEaz UicjFdkVNAvRvLbYOL/qb1FQp1RcNBL+sOyY0x8ryBEIohJlGCjyXWK2f/VO4ck= =ay/1 -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#779571: systemd: stop v4 dhcpclient when the carrier is lost
Package: systemd
Version: 215-12
Severity: important
The check for a running v4 dhcp client is using DHCP_SUPPORT_V6
flag instead of DHCP_SUPPORT_V4.
As a result, when the carrier was lost, systemd was not cleaning up the
relevant addresses and routes. If the carrier was regained in another
environment, with a different subnet and gateway, the system would end
up with multiple addresses and default gateways and thus a broken
network configuration.
This bug was introduced in v215 (ed942a9e), and was fixed from v216 as a
side effect of ba179154. The attached patch fixes that until debian
moves to the latest systemd version.
The above scenario happened quite regularly on my laptop when switching
locations. For the record, I am using systemd-networkd.service and
wpa_supplicant@wlan0.service handling authentication.
From ec01bba6278d43891f7dbaa49456b72aa6afb13b Mon Sep 17 00:00:00 2001
From: Christos Trochalakis yati...@ideopolis.gr
Date: Sat, 7 Feb 2015 09:23:19 +0200
Subject: [PATCH] networkd: link - fix stopping v4 dhcpclient when the carrier
is lost
The check for a running v4 dhcpclient was using DHCP_SUPPORT_V6 flag
instead of DHCP_SUPPORT_V4.
As a result, when the carrier was lost systemd was not cleaning up the
relevant addresses and routes. If the carrier was regained in another
environment, with a different subnet and gateway, the system would end
up with multiple addresses and default gateways and thus a broken
network configuration. This scenario can be easily reproduced with wifi
links.
---
src/network/networkd-link.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/src/network/networkd-link.c b/src/network/networkd-link.c
index 14c0417..cb435e2 100644
--- a/src/network/networkd-link.c
+++ b/src/network/networkd-link.c
@@ -206,7 +206,7 @@ static int link_stop_clients(Link *link) {
if (!link-network)
return 0;
-if (IN_SET(link-network-dhcp, DHCP_SUPPORT_BOTH, DHCP_SUPPORT_V6)) {
+if (IN_SET(link-network-dhcp, DHCP_SUPPORT_BOTH, DHCP_SUPPORT_V4)) {
assert(link-dhcp_client);
k = sd_dhcp_client_stop(link-dhcp_client);
--
2.1.4
Bug#779572: [sed] fails at extended char ranges ([A-z]) in regexps
Package: sed Version: 4.2.2-4+b1 Severity: important --- Please enter the report below this line. --- Hello sed version 4.2.1-10, correct result: echo =abcABC[]\\_=|sed 's/[A-z]/*/g' =**= sed version 4.2.2-4+b1, error: echo =abcABC[]\\_=|sed 's/[A-z]/*/g' sed: -e expression #1, char 11: Invalid range end sed version 4.2.2-4+b1, even weirder with what should be an invalid range: echo =abcABC[]\\_=|sed 's/[a-Z]/*/g' =**[]\_= --- System information. --- Architecture: amd64 Kernel: Linux 3.16.0-4-amd64 Debian Release: 8.0 500 unstable ftp.be.debian.org 500 testing-updates ftp.be.debian.org 500 testing security.debian.org 500 testing ftp.be.debian.org 500 synalysis hexinator.com 500 stable files.eid.belgium.be 500 stable dl.google.com 350 stable http.kali.org 100 jessie-backports ftp.be.debian.org --- Package information. --- Depends (Version) | Installed =-+-= dpkg (= 1.15.4) | 1.17.23 OR install-info | 5.2.0.dfsg.1-6 Package's Recommends field is empty. Package's Suggests field is empty. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#764616: rsync doesn't start during boot up process
On Sat 28 Feb 2015, Thomas Rechberger wrote: with these set: /etc/init.d/rsync RSYNC_ENABLE=true /etc/default/rsync RSYNC_ENABLE=true then its a missing rsyncd.conf Obviously, that's what the error message says: start condition failed at Sa 2015-02-28 12:05:49 CET; 1min 0s ago ConditionPathExists=/etc/rsyncd.conf was not met without the systemctl enable rsync.service it did not work, so its something the installer should do already (new install of rsync) What config is a new install of rsync supposed to use? Anything that could be installed by default might in theory be a potential security risk. If you choose to install this daemon, then it's also your responsibility to ensure that a correct configuration exists for your needs. Paul -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#731449: isc-dhcp-server: Server not removes DDNS if client releases the address.
Hallo, I would like to ask someone if this bug will be fixed some day or should I try to fix myself? We have updated last week our DHCP Servers with DDNS and now DHCP does not remove old DNS records. Mac OS X gets incorrect Hostname from PTR record from DNS. This bug has been reported on Dec, 05th 2013, last email on Mar 20th 2014, last update on Sep 27th 2014 and still no resolution? Thank you for information. Regards, Robert Wolf. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#747519: bibtool: Symbol does not start with a letter random errors with pipe
On 2015-03-02 13:34:30 +0100, Jerome BENOIT wrote: I can reproduce the issue on my laptop too, but the upstream could not reproduce it on his virtual box. Have you try your material on a virtual box ? I have a virtual machine with Ubuntu 14.04, but I can't reproduce the bug on it (the bibtool version is not the cause, since I can reproduce the bug on a Debian 7.8 machine, which has the same bibtool version). Note also that I can't reproduce the bug when bibtool is run under valgrind (by adding valgrind in front of the bibtool line in my testcase) on machines where I could reproduce the bug. Perhaps the code runs too slowly on the virtual machine and under valgrind. BTW, valgrind signals a read error: ==4060== Invalid read of size 1 ==4060==at 0x114836: ??? (in /usr/bin/bibtool) ==4060==by 0x115110: ??? (in /usr/bin/bibtool) ==4060==by 0x10B304: ??? (in /usr/bin/bibtool) ==4060==by 0x10B945: ??? (in /usr/bin/bibtool) ==4060==by 0x109FAE: ??? (in /usr/bin/bibtool) ==4060==by 0x506FB44: (below main) (libc-start.c:287) ==4060== Address 0x7f59f1c is 0 bytes after a block of size 60 alloc'd ==4060==at 0x4C28C20: malloc (vg_replace_malloc.c:296) ==4060==by 0x1196B6: ??? (in /usr/bin/bibtool) ==4060==by 0x1197E0: ??? (in /usr/bin/bibtool) ==4060==by 0x1135BB: ??? (in /usr/bin/bibtool) ==4060==by 0x113734: ??? (in /usr/bin/bibtool) ==4060==by 0x113DB9: ??? (in /usr/bin/bibtool) ==4060==by 0x10BEBB: ??? (in /usr/bin/bibtool) ==4060==by 0x109DE4: ??? (in /usr/bin/bibtool) ==4060==by 0x506FB44: (below main) (libc-start.c:287) -- 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#779331: wheezy update
I think this also needs to be a security update in wheezy and jessie. What are the plans for that? signature.asc Description: OpenPGP digital signature
Bug#779567: ITP: librdp-taxonomy-tree-java -- taxonomy tree library from Ribosomal Database Project (RDP)
Package: wnpp Severity: wishlist Owner: Andreas Tille ti...@debian.org * Package name: librdp-taxonomy-tree-java Version : 1.2.0 Upstream Author : rdpst...@msu.edu * URL : https://github.com/rdpstaff/TaxonomyTree * License : GPL Programming Lang: Java Description : taxonomy tree library from Ribosomal Database Project (RDP) The TaxonomyTree project is a library used by other Ribosomal Database Project (RDP) tools. This package was originally built by Tim Booth from BioLinux as a precondition for the to be packaged rdp-classifier package. It is maintained by the Debian Med team at svn://anonscm.debian.org/debian-med/trunk/packages/librdp-taxonomy-tree-java/trunk/ -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#747519: bibtool: Symbol does not start with a letter random errors with pipe
On 2015-03-02 14:56:07 +0100, Jerome BENOIT wrote: Ok. I will resubmit the bug to the upstream maintainer. The last time I submitted it, I could not reproduce the issue. And on my side, I could hardly trace it. This is probably easier to reproduce with the new script I posted earlier today. Moreover I think that it is also easier on a fast machine, possibly with several cores. -- 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#764616: rsync doesn't start during boot up process
What config is a new install of rsync supposed to use? Anything that could be installed by default might in theory be a potential security risk. If you choose to install this daemon, then it's also your responsibility to ensure that a correct configuration exists for your needs. Its more about the systemctl enable command. I just posted above output so everyone can see whats going on. I installed rsync package by using apt, the links in /etc/rcX did exist but rsync didnt start after reboot. So this looked like the damon would have been already enabled by the installer (like done by all other debian packages), but it was not. This is unexpected situation and leads to wrong assumptions. So i dont know why this poses a security risk to not enable the daemon automatically by installation if it anyway doesnt gonna start when there is no default rsyncd.conf file and no RSYNC_ENABLE set. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#670984: libphidget21: changing from RFP to ITP
retitle 670984 ITP: libphidget21 -- Phidgets runtime library owner 670984 fab...@andre.bzh thanks I work in collaboration with upstream developer Patrick McNeil, and I am confident to tackle all copyright concerns raised during previous attempt. Actually, a few of them are already fixed in last upstream version 2.1.8.20150227 -- Fabien André ENAC / IHM-Aéro fabien.an...@enac.fr 05.62.25.95.25 -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#747519: bibtool: Symbol does not start with a letter random errors with pipe
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hello Hilmar, thanks for reminding. On 02/03/15 09:33, Hilmar Preuße wrote: found 747519 2.58 stop On 09.05.2014 16:47, Vincent Lefevre wrote: Package: bibtool Version: 2.57+ds-1 Severity: normal I randomly get errors like: *** BibTool ERROR: (line 109 in stdin): Symbol does not start with a letter , _^ Still found in 2.58. Please you confirm that you can observe the issue on a non virtual box. Even better, can you check on a virtual ? Thanks in advance, Jerome Hilmar -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.12 (GNU/Linux) iQEcBAEBAgAGBQJU9CsPAAoJEIC/w4IMSybjlGwH/i2UBS9aRdW98BMTcexS/CYm gLI+/x2gi81ujmIChWrf5QeJ05CTFtTr496Aa/X6AfR2CTK94fOdmqUFG6Hr2drB cgPJo+hoRdonOBDVxj2aJgYg4gehdzCw4muLu0Tu5RYLpqxZ6lQv2rYuOaeUdvMR uFIEBUJWOOOg75+330yMyb7e036NkcicAC/JcVjOOT0zc3TaygZ/eJSesYSSpUQO JhHmWEE3Tdck2+eeSmEIgMta2uQBK4kGBRKwM/+lpthZuucDrKWBiORM9Sjajeac QF08JJNdcJWUuWkkcMOXAw7vBHaEmF8hMMdlHX733rf2xgkNYQ5v6ZcYwQbmO9M= =R/fY -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#779080: unblock (pre-approval): gtk+2.0/2.24.25-2
retitle 779080 unblock gtk+2.0/2.24.25-2 finished On Tue, Feb 24, 2015 at 11:03:15AM +0100, Mike Gabriel wrote: Please consider unblocking planned upload of package gtk+2.0. BTW I just uploaded it to unstable, so: no longer a pre-approval request. -- Iain Lane [ i...@orangesquash.org.uk ] Debian Developer [ la...@debian.org ] Ubuntu Developer [ la...@ubuntu.com ] -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#779562: tinc: Should net-tools be a (suggested or recommended) dependency?
Source: tinc Severity: minor -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Dear Maintainer, while setting up tinc as a Docker image, I ran into problems when configuring the `tinc-up` script. I realized the Debian docker image does not bring `ifconfig`, which is proposed to be used in the autogenerated configuration script. While I'm not sure whether `net-tools` should be a hard dependency, I think it should be recommended or at least suggested. Kind regards from Lake Constance, Germany, Jens Erat *** 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 APT policy: (1000, 'testing'), (750, 'testing'), (500, 'testing-updates'), (50, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 3.16.0-4-amd64 (SMP w/4 CPU cores) Locale: LANG=de_DE.utf8, LC_CTYPE=de_DE.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) -BEGIN PGP SIGNATURE- Version: GnuPG v1 iQIcBAEBAgAGBQJU9D4VAAoJEI545E37G1XpPaIQAIgeM1LqJ/9KszssPKl+y/05 43enS57QEUB8O83Eelk9H9/S4niYHkITtp1lg9+6Ujqa/RJPyt73iuXmaDFj0IQS a/hzffEyy+Lju+aIbR6wkYcRanLMC3cl3VWDOrsxP4hy6ynrbIBLq2csbOyvVNNT A8H+6B8qfRxJQ6xFOYHHyTD2dGnoKgFNHouOBrHzzU6ZAgUFnCeCSNtd8ZkOTGrZ A38vazLqOmQmlQ5MwrxOnMUo3Cd4n1tkrkuM0cSZEG/oWi1BIRWMDeBN6GVK0V57 hDXgMQ37PIZ23OtTNvQ6lo/h5dgQvOM6w87zAhqOruvE9F6LI+em4jQmMyJWSRsS dviOdjLZHJIXbqzvx5xPPioNZfxPtzWWd1YZzZi51fDQhCuaBkRzVYVL6q4bYYow 4FOmcIcaGG65qylFvGTHdr/PU8KppyHVwDTX3JLL8CtGLy83j45vcvs1jXJRU867 N0LBi9U+4HL7dC/7/5LAXK4FQhgkSIWVXkaDHfP1nJNN03kALew0+1K8fRnMP+9C jeHMik04bDBYpWLnO4VYqdvnaNNaTgF9clmkWVjktRvO8G0q3sToi9HbuVdHpHRC LWBjnZeuzVIFP9X/0f1gjO9HevpnQr1o42KH8pWAq+kZpD+KEFwwBru3K8vsi4/0 8DFp4ok2EglFg8YSOOi5 =ZTtI -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
