Bug#762323: openjdk-8-jre-headless: OpenJDK 8 returns incorrect TrueType font metrics
Package: openjdk-8-jre-headless Version: 8u40~b04-2 Severity: normal Tags: patch Dear Maintainer, In 2012, I reported #657854 (and #671443 for openjdk-6), and this problem has been fixed for openjdk-7 package. Now, Debian has a new openjdk-8 package, and this package has a same problem. The result of sample code in #657854: $ /usr/lib/jvm/java-8-openjdk-amd64/bin/java JavaApplication1 Ascent: 7.046875 Descent: 0.96875 $ /usr/lib/jvm/java-7-openjdk-amd64/bin/java JavaApplication1 Ascent: 7.0390625 Descent: 0.9609375 $ /usr/lib/jvm/java-6-openjdk-amd64/bin/java JavaApplication1 Ascent: 7.046875 Descent: 0.96875 The patch attached to #657854 will fix this problem. -- System Information: Debian Release: jessie/sid APT prefers stable APT policy: (500, 'stable'), (500, 'oldstable') Architecture: amd64 (x86_64) Kernel: Linux 3.14-2-amd64 (SMP w/1 CPU core) Locale: LANG=ja_JP.UTF-8, LC_CTYPE=ja_JP.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages openjdk-8-jre-headless depends on: ii ca-certificates-java 20140324 ii java-common 0.52 ii libc6 2.19-11 ii libcups2 1.7.5-1 ii libfreetype6 2.5.2-1.1 ii libgcc1 1:4.9.1-14 ii libjpeg8 8d1-1 ii liblcms2-22.6-3 ii libnss3 2:3.17-1 ii libpcsclite1 1.8.11-3 ii libstdc++64.9.1-14 ii libx11-6 2:1.6.2-3 ii libxext6 2:1.3.2-1 ii libxi62:1.7.4-1 ii libxrender1 1:0.9.8-1 ii libxtst6 2:1.2.2-1 ii multiarch-support 2.19-11 ii tzdata-java 2014g-1 ii zlib1g1:1.2.8.dfsg-2 openjdk-8-jre-headless recommends no packages. Versions of packages openjdk-8-jre-headless suggests: ii fonts-dejavu-extra 2.34-1 pn fonts-indicnone ii fonts-ipafont-gothic 00303-12 ii fonts-ipafont-mincho 00303-12 ii fonts-wqy-microhei [ttf-wqy-microhei] 0.2.0-beta-2 ii fonts-wqy-zenhei [ttf-wqy-zenhei] 0.9.45-6 ii libnss-mdns0.10-6 pn openjdk-8-jre-jamvmnone -- no debconf information Regards, Nobuhiro -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#762014:
Hi Balint, On Sat, Sep 20, 2014 at 2:05 PM, Balint Reczey bal...@balintreczey.hu wrote: The same here. Can't try to downgrade to 7.37.1-1 since it's not available anymore. It is a available from http://snapshot.debian.org/package/curl/7.37.1-1/ . I've tried that version and xbmc works fine with it. Thanks, Dmitry
Bug#759093: winpdb: Patch for wxPython 3.0
On 20. September 2014 22:48:11 MESZ, Olly Betts o...@survex.com wrote: On Sat, Sep 20, 2014 at 01:28:00PM +0200, Bernd Zeimetz wrote: Maybe because of https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=757718 I would appreciate if you could NMU winpdb with the patches for both bugs, I'm missing the time to do so right now. Hi Bernd, I'm wondering if I should switch winpdb away from dpatch - lintian gives an error that dpatch is obsolete, and I'm struggling to remember how to correctly add patches with dpatch (it looks like I didn't actually manage to apply my previous patch when I tested). Please do! I have the same trouble with dpatch :-) But such changes can be controversial, so I thought I should check first... Cheers, Olly -- Diese Nachricht wurde von meinem Android-Mobiltelefon mit K-9 Mail gesendet. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#761877: xserver-xorg: Updated Xorg from Testing fails to start correctly
Package: xserver-xorg-video-mach64 Version: 6.9.4-1+b3 Followup-For: Bug #761877 I'm having a similar issue on one of my test machines here, an old Compaq Pentium III laptop that I just upgraded to jessie. The log shows that the Mach64 driver is segfaulting. I'm able to get X working if I force usage of the VESA driver, though with some artifacting (which should be in a separate bug, honestly). -lee -- Package-specific info: X server symlink status: lrwxrwxrwx 1 root root 13 Jan 19 2014 /etc/X11/X - /usr/bin/Xorg -rwxr-xr-x 1 root root 2556784 Sep 8 21:28 /usr/bin/Xorg VGA-compatible devices on PCI bus: -- 01:00.0 VGA compatible controller [0300]: Advanced Micro Devices, Inc. [AMD/ATI] Rage Mobility AGP 2x Series [1002:4c4d] (rev 64) /etc/X11/xorg.conf does not exist. /etc/X11/xorg.conf.d does not exist. KMS configuration files: /etc/modprobe.d/radeon-kms.conf: options radeon modeset=1 Kernel version (/proc/version): --- Linux version 3.14-2-686-pae (debian-ker...@lists.debian.org) (gcc version 4.8.3 (Debian 4.8.3-7) ) #1 SMP Debian 3.14.15-2 (2014-08-09) Xorg X server log files on system: -- -rw-r--r-- 1 root root 36678 Sep 21 01:41 /var/log/Xorg.1.log -rw-r--r-- 1 root root 36677 Sep 21 01:44 /var/log/Xorg.0.log Contents of most recent Xorg X server log file (/var/log/Xorg.0.log): - [77.426] X.Org X Server 1.16.0 Release Date: 2014-07-16 [77.426] X Protocol Version 11, Revision 0 [77.426] Build Operating System: Linux 3.2.0-4-amd64 i686 Debian [77.427] Current Operating System: Linux ARMADA 3.14-2-686-pae #1 SMP Debian 3.14.15-2 (2014-08-09) i686 [77.427] Kernel command line: BOOT_IMAGE=/boot/vmlinuz-3.14-2-686-pae root=UUID=c586af3f-8d31-485b-ba74-fd3580efa1b6 ro quiet [77.427] Build Date: 09 September 2014 01:25:53AM [77.427] xorg-server 2:1.16.0-2+b1 (http://www.debian.org/support) [77.427] Current version of pixman: 0.32.6 [77.428] Before reporting problems, check http://wiki.x.org to make sure that you have the latest version. [77.428] Markers: (--) probed, (**) from config file, (==) default setting, (++) from command line, (!!) notice, (II) informational, (WW) warning, (EE) error, (NI) not implemented, (??) unknown. [77.429] (==) Log file: /var/log/Xorg.0.log, Time: Sun Sep 21 01:44:10 2014 [77.474] (==) Using system config directory /usr/share/X11/xorg.conf.d [77.517] (==) No Layout section. Using the first Screen section. [77.517] (==) No screen section available. Using defaults. [77.517] (**) |--Screen Default Screen Section (0) [77.517] (**) | |--Monitor default monitor [77.522] (==) No monitor specified for screen Default Screen Section. Using a default monitor configuration. [77.522] (==) Automatically adding devices [77.522] (==) Automatically enabling devices [77.522] (==) Automatically adding GPU devices [77.540] (WW) The directory /usr/share/fonts/X11/cyrillic does not exist. [77.541] Entry deleted from font path. [77.608] (==) FontPath set to: /usr/share/fonts/X11/misc, /usr/share/fonts/X11/100dpi/:unscaled, /usr/share/fonts/X11/75dpi/:unscaled, /usr/share/fonts/X11/Type1, /usr/share/fonts/X11/100dpi, /usr/share/fonts/X11/75dpi, built-ins [77.608] (==) ModulePath set to /usr/lib/xorg/modules [77.608] (II) The server relies on udev to provide the list of input devices. If no devices become available, reconfigure udev or disable AutoAddDevices. [77.609] (II) Loader magic: 0xb771f700 [77.609] (II) Module ABI versions: [77.609] X.Org ANSI C Emulation: 0.4 [77.609] X.Org Video Driver: 18.0 [77.609] X.Org XInput driver : 21.0 [77.609] X.Org Server Extension : 8.0 [77.612] (--) PCI:*(0:1:0:0) 1002:4c4d:0e11:b111 rev 100, Mem @ 0x4100/16777216, 0x4020/4096, I/O @ 0x3000/256, BIOS @ 0x/131072 [77.613] (II) LoadModule: glx [77.616] (II) Loading /usr/lib/xorg/modules/extensions/libglx.so [77.747] (II) Module glx: vendor=X.Org Foundation [77.747] compiled for 1.16.0, module version = 1.0.0 [77.747] ABI class: X.Org Server Extension, version 8.0 [77.747] (==) AIGLX enabled [77.748] (==) Matched ati as autoconfigured driver 0 [77.748] (==) Matched modesetting as autoconfigured driver 1 [77.748] (==) Matched fbdev as autoconfigured driver 2 [77.748] (==) Matched vesa as autoconfigured driver 3 [77.748] (==) Assigned the driver to the xf86ConfigLayout [77.748] (II) LoadModule: ati [77.780] (II) Loading /usr/lib/xorg/modules/drivers/ati_drv.so [77.821] (II) Module ati: vendor=X.Org Foundation [77.822] compiled for 1.15.99.904, module version = 7.4.0 [77.822] Module class: X.Org Video Driver [77.822] ABI class: X.Org Video Driver, version 18.0 [77.822] (II)
Bug#762324: linux-image-3.16-2-amd64: sed error when executing /etc/kernel/postinst.d/dkms
Package: src:linux Version: 3.16.3-2 Severity: normal Dear Maintainer, When upgrading linux kernel I get such error messages: Setting up linux-image-3.16-2-amd64 (3.16.3-2) ... /etc/kernel/postinst.d/dkms: sed: -e expression #1, char 6: unknown command: `m' sed: -e expression #1, char 6: unknown command: `m' My installed dkms packages: tp-smapi-dkms and virtualbox-dkms. What is wrong? -- Package-specific info: ** Version: Linux version 3.16-2-amd64 (debian-ker...@lists.debian.org) (gcc version 4.8.3 (Debian 4.8.3-11) ) #1 SMP Debian 3.16.3-2 (2014-09-20) ** Command line: BOOT_IMAGE=/boot/vmlinuz-3.16-2-amd64 root=UUID=cc9a3935-8b21-478e-badf-f857f1f2aa2a ro quiet ** Tainted: O (4096) * Out-of-tree module has been loaded. ** Kernel log: [2.760446] ieee80211 phy0: Selected rate control algorithm 'iwl-agn-rs' [2.770734] input: PC Speaker as /devices/platform/pcspkr/input/input11 [2.808865] yenta_cardbus :15:00.0: ISA IRQ mask 0x0cb8, PCI irq 16 [2.808871] yenta_cardbus :15:00.0: Socket status: 3006 [2.808877] yenta_cardbus :15:00.0: pcmcia: parent PCI bridge window: [io 0x4000-0x7fff] [2.808879] yenta_cardbus :15:00.0: pcmcia: parent PCI bridge window: [mem 0xf480-0xf7ff] [2.808882] pcmcia_socket pcmcia_socket0: cs: memory probe 0xf480-0xf7ff: [2.808886] excluding 0xf480-0xf4b7 [2.808895] yenta_cardbus :15:00.0: pcmcia: parent PCI bridge window: [mem 0xf000-0xf3ff 64bit pref] [2.808897] pcmcia_socket pcmcia_socket0: cs: memory probe 0xf000-0xf3ff: [2.808901] excluding 0xf000-0xf3ff [2.828363] r852: driver loaded successfully [2.829613] r592: driver successfully loaded [2.845222] fbcon: inteldrmfb (fb0) is primary device [2.877685] Adding 4194300k swap on /dev/sda4. Priority:-1 extents:1 across:4194300k SSFS [2.942420] cfg80211: World regulatory domain updated: [2.942422] cfg80211: DFS Master region: unset [2.942423] cfg80211: (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp), (dfs_cac_time) [2.942424] cfg80211: (2402000 KHz - 2472000 KHz @ 4 KHz), (N/A, 2000 mBm), (N/A) [2.942425] cfg80211: (2457000 KHz - 2482000 KHz @ 4 KHz), (N/A, 2000 mBm), (N/A) [2.942426] cfg80211: (2474000 KHz - 2494000 KHz @ 2 KHz), (N/A, 2000 mBm), (N/A) [2.942427] cfg80211: (517 KHz - 525 KHz @ 8 KHz), (N/A, 2000 mBm), (N/A) [2.942428] cfg80211: (5735000 KHz - 5835000 KHz @ 8 KHz), (N/A, 2000 mBm), (N/A) [2.942429] cfg80211: (5724 KHz - 6372 KHz @ 216 KHz), (N/A, 0 mBm), (N/A) [2.979048] EXT4-fs (sda2): mounted filesystem with ordered data mode. Opts: (null) [2.979718] EXT4-fs (sda1): mounted filesystem with ordered data mode. Opts: (null) [3.212890] psmouse serio1: alps: Unknown ALPS touchpad: E7=10 00 64, EC=10 00 64 [3.420230] Console: switching to colour frame buffer device 160x50 [3.428135] i915 :00:02.0: fb0: inteldrmfb frame buffer device [3.428138] i915 :00:02.0: registered panic notifier [3.432057] systemd-journald[144]: Received request to flush runtime journal from PID 1 [3.452345] ACPI: Video Device [VID] (multi-head: yes rom: no post: no) [3.470800] acpi device:01: registered as cooling_device2 [3.470901] input: Video Bus as /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/LNXVIDEO:00/input/input13 [3.471059] [drm] Initialized i915 1.6.0 20080730 for :00:02.0 on minor 0 [3.471846] mei_me :00:03.0: irq 49 for MSI/MSI-X [3.476489] ACPI Warning: SystemIO range 0x1028-0x102f conflicts with OpRegion 0x1000-0x107f (\_SB_.PCI0.LPC_.PMIO) (20140424/utaddress-258) [3.476497] ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver [3.476501] ACPI Warning: SystemIO range 0x11b0-0x11bf conflicts with OpRegion 0x1180-0x11ff (\_SB_.PCI0.LPC_.LPIO) (20140424/utaddress-258) [3.476505] ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver [3.476506] ACPI Warning: SystemIO range 0x1180-0x11af conflicts with OpRegion 0x1180-0x11ff (\_SB_.PCI0.LPC_.LPIO) (20140424/utaddress-258) [3.476509] ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver [3.476511] lpc_ich: Resource conflict(s) found affecting gpio_ich [3.476735] i801_smbus :00:1f.3: SMBus using PCI Interrupt [3.483889] iTCO_vendor_support: vendor-support=0 [3.484435] iTCO_wdt: Intel TCO WatchDog Timer Driver v1.11 [3.484487] iTCO_wdt: Found a ICH9M-E TCO device (Version=2, TCOBASE=0x1060) [3.484705] iTCO_wdt: initialized. heartbeat=30 sec (nowayout=0) [3.556235] e1000e :00:19.0: irq 44 for MSI/MSI-X [
Bug#762325: libgd2: not binNMU safe
Package: src:libgd2 Version: 3.9.3 Severity: serious libgd2 had to be binNMUed on s390x, unfortunately this makes libgd2-noxpm-dev not installable. It is arch:all so not rebuilt and has a strict dependency on libgd-dev (= 2.1.0-4), while the binNMUed version is now 2.1.0-4+b1. The debian/control file looks fine, but the issue is likely caused by the use of dh_installdocs with --link-doc between arch:all and arch:any packages (see bug#747141). Note that if you remove this link, you should use dpkg-maintscript-helper to convert the symlink into a directory. As this is a transitional package you might want to not fix the issue and just wait for it to be removed. In that case please do a source upload of libgd2 to fix the issue on s390x, and decrease the severity of this bug to important. -- System Information: Debian Release: jessie/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: s390x Kernel: Linux 3.2.0-4-s390x (SMP w/2 CPU cores) Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#762326: avahi-daemon support scripts use (legacy) network tools but do not depend on them
Package: avahi-daemon Version: 0.6.31-4 Severity: normal /usr/lib/avahi/avahi-daemon-check-dns.sh uses route and ifconfig tools which comes from (legacy) net-tools package which is not necessary to be installed on a system, because iproute provides all the functionality and because that package is used by ifupdown nowadays. Please consider rewriting this script to use iproute, and please document actual dependency (either on net-tools or, preferrable, after rewriting, on iproute2) in Depends: package control field. /mjt -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#762327: hda-intel: snd-hda-intel: mic input stops working after resuming from suspend to ram
Package: src:linux Version: 3.14.15-2~bpo70+1 Severity: important File: hda-intel Dear Maintainer, After last update using skype I've found mic input does not work after resuming from suspend to ram on DELL E6430. alsamixer settings check didn't help. When I start arecord after resuming, it writes message: Suspended. Trying resume. Done. and after that mic input becomes functional. --Package-specific info: ** Version: Linux version 3.14-0.bpo.2-686-pae (debian-ker...@lists.debian.org) (gcc version 4.6.3 (Debian 4.6.3-14) ) #1 SMP Debian 3.14.15-2~bpo70+1 (2014-08-21) ** Command line: BOOT_IMAGE=/vmlinuz-3.14-0.bpo.2-686-pae root=/dev/mapper/dellz-root ro quiet ** Tainted: WO (4608) * Taint on warning. * Out-of-tree module has been loaded. ** Kernel log: [147161.684168] CPU2 is up [147161.684225] smpboot: Booting Node 0 Processor 3 APIC 0x6 [147161.694900] CPU3 microcode updated early to revision 0x1b, date = 2014-05-29 [147161.694902] Initializing CPU#3 [147161.695988] CPU3: Thermal monitoring handled by SMI [147161.696011] kvm: enabling virtualization on CPU3 [147161.698209] microcode: CPU3 sig=0x306a9, pf=0x10, revision=0x1b [147161.698218] Intel pstate controlling: cpu 3 [147161.698264] CPU3 is up [147161.698320] smpboot: Booting Node 0 Processor 4 APIC 0x1 [147161.708992] CPU4 microcode updated early to revision 0x1b, date = 2014-05-29 [147161.708993] Initializing CPU#4 [147161.710174] CPU4: Thermal monitoring handled by SMI [147161.710196] kvm: enabling virtualization on CPU4 [147161.712445] microcode: CPU4 sig=0x306a9, pf=0x10, revision=0x1b [147161.712455] Intel pstate controlling: cpu 4 [147161.712500] CPU4 is up [147161.712551] smpboot: Booting Node 0 Processor 5 APIC 0x3 [147161.722816] Initializing CPU#5 [147161.724264] CPU5: Thermal monitoring handled by SMI [147161.724282] kvm: enabling virtualization on CPU5 [147161.726512] microcode: CPU5 sig=0x306a9, pf=0x10, revision=0x1b [147161.726520] Intel pstate controlling: cpu 5 [147161.726560] CPU5 is up [147161.726605] smpboot: Booting Node 0 Processor 6 APIC 0x5 [147161.736870] Initializing CPU#6 [147161.738341] CPU6: Thermal monitoring handled by SMI [147161.738360] kvm: enabling virtualization on CPU6 [147161.740597] microcode: CPU6 sig=0x306a9, pf=0x10, revision=0x1b [147161.740605] Intel pstate controlling: cpu 6 [147161.740644] CPU6 is up [147161.740691] smpboot: Booting Node 0 Processor 7 APIC 0x7 [147161.750957] Initializing CPU#7 [147161.752439] CPU7: Thermal monitoring handled by SMI [147161.752457] kvm: enabling virtualization on CPU7 [147161.754681] microcode: CPU7 sig=0x306a9, pf=0x10, revision=0x1b [147161.754689] Intel pstate controlling: cpu 7 [147161.754729] CPU7 is up [147161.761247] ACPI: Waking up from system sleep state S3 [147161.790456] dell_wmi: Received unknown WMI event (0x0) [147161.811638] xhci_hcd :00:14.0: System wakeup disabled by ACPI [147161.859619] ehci-pci :00:1a.0: System wakeup disabled by ACPI [147161.891615] ehci-pci :00:1d.0: System wakeup disabled by ACPI [147161.939869] PM: noirq resume of devices complete after 159.108 msecs [147161.939978] PM: early resume of devices complete after 0.085 msecs [147161.940042] mei_me :00:16.0: irq 41 for MSI/MSI-X [147161.940248] snd_hda_intel :00:1b.0: irq 44 for MSI/MSI-X [147161.949102] e1000e :00:19.0: System wakeup disabled by ACPI [147161.949141] e1000e :00:19.0: irq 45 for MSI/MSI-X [147161.965299] dpm_run_callback(): pnp_bus_resume+0x0/0x80 returns -19 [147161.965300] PM: Device 00:09 failed to resume: error -19 [147162.151606] usb 1-1.5: reset high-speed USB device number 5 using ehci-pci [147162.291538] ata5: SATA link down (SStatus 0 SControl 300) [147162.291564] ata6: SATA link down (SStatus 0 SControl 300) [147162.299537] ata2: SATA link up 1.5 Gbps (SStatus 113 SControl 300) [147162.304463] ata2.00: configured for UDMA/100 [147162.319593] usb 1-1.2: reset full-speed USB device number 3 using ehci-pci [147162.339551] i915: No ACPI video bus found [147162.483579] usb 1-1.4: reset full-speed USB device number 4 using ehci-pci [147163.383434] [drm] Enabling RC6 states: RC6 on, RC6p on, RC6pp off [147163.971380] ata1: SATA link up 6.0 Gbps (SStatus 133 SControl 300) [147164.200416] ata1.00: ACPI cmd ef/10:06:00:00:00:00 (SET FEATURES) succeeded [147164.200421] ata1.00: ACPI cmd f5/00:00:00:00:00:00 (SECURITY FREEZE LOCK) filtered out [147164.200424] ata1.00: ACPI cmd b1/c1:00:00:00:00:00 (DEVICE CONFIGURATION OVERLAY) filtered out [147164.200642] ata1.00: ACPI cmd ef/5a:00:00:00:00:a0 (SET FEATURES) succeeded [147164.236547] ata1.00: ACPI cmd ef/10:06:00:00:00:00 (SET FEATURES) succeeded [147164.236551] ata1.00: ACPI cmd f5/00:00:00:00:00:00 (SECURITY FREEZE LOCK) filtered out [147164.236555] ata1.00: ACPI cmd b1/c1:00:00:00:00:00 (DEVICE CONFIGURATION OVERLAY) filtered out [147164.236733] ata1.00: ACPI cmd 00/00:00:00:00:00:a0 (NOP) rejected by device (Stat=0x51 Err=0x04) [147164.240682]
Bug#745303: need more information
Hi Pablo. Does this bug still occur for you? I'm not really sure how to go about duplicating the problem. Can you tell me what file system you are using? I would be very helpful if you could provide a way of duplicating the problem using only the notmuch command line interface. d -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#760509: [pkg-wine-party] Bug#760509: wine: Wine : Office 2010 no longer installs usably.
Dear Michael, dear list, Le samedi 20 septembre 2014 à 17:10 -0400, Michael Gilbert a écrit : On Thu, Sep 4, 2014 at 4:11 PM, Emmanuel Charpentier wrote: The installation runs normally. When starting Winword for the first time, it aks for name and initial, then displays a configuration progress bar, then asks for a reboot. If one clicks on yes, thge rebooot fails and gives an error message. When asking for details, one gets the enclosed backtrace. If one refuses to reboot, the normal Winword appears, but cannot be activated. In short, the result is an unusable MS Office. Can you try without any of the wine64 packages installed, possibly without winbind also. Also try a clean .wine directory? First attempt without win64 : same results. Installed packages : charpent@asus16-ec:~$ dpkg -l *wine* | grep ii | sed -re s/[ \t]+/ /g | cut -d -f 2-3 | xargs echo libwine:i386 1.6.2-8 libwine-gecko-1.4 1.4+dfsg-2 libwine-gecko-2.21 2.21+dfsg2-1 wine 1.6.2-8 wine32 1.6.2-8 Installation of Word, Excel, Powerpoint, Access ad Office tools. No outlook no Publisher, etc... Install goes uneventfully. But the same problem as before appears when trying to use an app : When launching Word, a dialog box asking for reconfiguration appears, and asks for a reboot. Clicking yes leads to a Wine crash, clicking no opens the application, which seems more or less usable. , if Word, Excel and Access can be opened (Word with this bizarre procedure above), Powerpoint fails. Second attempt, after purging winbind : installation fails (without hints from Office nor Wine). Best wishes, No such luck... Still listening for suggestions, Emmanuel Charpentier -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#762328: owncloud: Only shows blank page (empty HTML file)
Package: owncloud Version: 7.0.2+dfsg-1~bpo70+1 Severity: important Dear Maintainer, I have just installed Own Cloud and adapted it to use Postgres. If the file /etc/owncloud/config.php has insufficient permissions or the Postgres password is unset, the proper page shows up, but if I correct this, Apache just sends nothing, even if the password or database user are set incorrectly. The log (/var/log/owncloud.log) contains nothing in this case even though logging is set to DEBUG. (If the password is unset, an entry appears, but not if user or password are wrong.) -- System Information: Debian Release: 7.6 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable') Architecture: i386 (i686) Kernel: Linux 3.2.0-4-686-pae (SMP w/2 CPU cores) Locale: LANG=en_IE.UTF-8, LC_CTYPE=en_IE.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages owncloud depends on: ii apache2 2.2.22-13+deb7u3 ii apache2-mpm-prefork [httpd] 2.2.22-13+deb7u3 ii fonts-font-awesome 4.1.0~dfsg-1~bpo70+1 ii fonts-liberation 1.07.2-6 ii fonts-linuxlibertine 5.1.3-1 ii fonts-lohit-deva 2.5.1-1 ii fonts-sil-gentium-basic 1.1-5 ii fonts-wqy-microhei 0.2.0-beta-2 ii libjs-chosen 0.9.11-1~bpo7+1 ii libjs-dojo-dojox 1.7.2+dfsg-1 ii libjs-jcrop 0.9.12+dfsg-1~bpo70+1 ii libjs-jquery-minicolors 1.2.1-1~bpo7+1 ii libjs-jquery-mousewheel 6-1 ii libjs-jquery-timepicker 1.2-1~bpo70+1 ii libjs-pdf1.0.473+dfsg-1~bpo70+1 ii libphp-phpmailer 5.1-1 ii owncloud-doc 0~20140428-1 ii php-assetic 1.1.2-1~bpo70+1 ii php-doctrine-dbal2.4.2-3~bpo70+1 ii php-getid3 1.9.7-2~bpo70+1 ii php-opencloud1.10.0-2~bpo70+1 ii php-patchwork-utf8 1.1.7-1~bpo70+1 ii php-pear 5.4.4-14+deb7u14 ii php-pimple 1.1.1-1~bpo70+1 ii php-sabre-dav1.8.10-1~bpo70+1 ii php-seclib 0.3.5-2~bpo70+1 ii php-symfony-classloader 2.3.6-1~bpo70+1 ii php-symfony-console 2.3.1+dfsg-1~bpo70+1 ii php-symfony-routing 2.0.19-1~bpo70+1 ii php5 5.4.4-14+deb7u14 ii php5-common [php5-json] 5.4.4-14+deb7u14 ii php5-gd 5.4.4-14+deb7u14 ii php5-mysql 5.4.4-14+deb7u14 ii php5-pgsql 5.4.4-14+deb7u14 ii zendframework1.11.13-1.1 Versions of packages owncloud recommends: ii exim4-daemon-light [mail-transport-agent] 4.80-7 ii libav-tools6:0.8.16-1 ii libreoffice1:3.5.4+dfsg2-0+deb7u2 pn php-aws-sdknone pn php-crypt-blowfish none ii php-dropbox1.0.0-1~bpo70+1 pn php-google-api-php-client none ii php5-cli 5.4.4-14+deb7u14 ii php5-curl 5.4.4-14+deb7u14 ii php5-imagick 3.1.0~rc1-1+b2 ii php5-intl 5.4.4-14+deb7u14 pn php5-ldap none ii php5-mcrypt5.4.4-14+deb7u14 ii php5-xcache2.0.0-4 ii smbclient 2:3.6.6-6+deb7u4 Versions of packages owncloud suggests: pn libapache2-mod-xsendfile none ii mysql-server 5.5.38-0+wheezy1 ii mysql-server-5.5 [virtual-mysql-server] 5.5.38-0+wheezy1 ii postgresql 9.1+134wheezy4 -- debconf-show failed ?php $CONFIG = array ( /* Loglevel to start logging at. 0=DEBUG, 1=INFO, 2=WARN, 3=ERROR (default is WARN) */ loglevel = DEBUG, 'dbtype' = 'pgsql', 'dbname' = 'owncloud', 'dbuser' = 'owncloud', 'dbpassword' = 'rainy', 'dbhost' = 'localhost', 'dbtableprefix' = '', 'instanceid' = 'oce8ce87b628', );
Bug#750255: lio-utils: FTBFS: chmod: cannot access '/«BUILDDIR»/lio-utils-3.1+git2.fd0b34fd/debian/lio-utils/usr/share/pyshared/*.py': No such file or directory
On Saturday 20 September 2014 03:23 PM, Jerome Martin wrote: Yes, the problem is that the kernel side uses this path unfortunately. We could relocate policy and fabric to /var/lib/target, but that would mean keeping both /lib/target and /var/target around for now, as the kernel will use that for storing alua metadata in /var/target/alua. However, what about relocating now, and keeping around a symlink to /var/target, created in post-install? This way, as soon as Nic can push the relocation to /var/lib/alua, we are ready and just have to remove the symlink from packaging. I am cc'ing the ML on this one. The manpage, written by Andy, refers to /var/lib/. Which would imply that Fedora/RHEL and all its derivatives must be using the new path. -- Given the large number of mailing lists I follow, I request you to CC me in replies for quicker response -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#759252: gjay: diff for NMU version 0.3.2-1.1
On Sun, Sep 14, 2014 at 08:47:17PM -0500, Julián Moreno Patiño wrote: I'm sorry for the NMU, I see the email too late, so I can't cancel it. No problem at all, you were fine to go ahead with it. - Craig -- Craig Small (@smallsees) http://enc.com.au/ csmall at : enc.com.au Debian GNU/Linux http://www.debian.org/ csmall at : debian.org GPG fingerprint:5D2F B320 B825 D939 04D2 0519 3938 F96B DF50 FEA5 -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#762296: [Pkg-fonts-devel] Bug#762296: Droid Sans Fallback refers to three different files
So something needs to be done. With my Ubuntu glasses I think the best solution is to stop letting fonts-droid install DroidSansFallback.ttf and DroidSansFallbackLegacy.ttf for now. Then, if it's considered important to include them somehow, it should be done in a more carefully considered manner. H, that seems sensible. I'm puzzled, though, by the less worse way to achieve this. As of now, we have: bubulle@sesostris:~/src/debian/pkg-fonts/git/fonts-android(master) $ more debian/fonts-droid.install Droid*.ttf usr/share/fonts/truetype/droid ... So basically : let's install all fonts whose name starts with Droid . How can we technically do All fonts whose name starts with 'Droid' but two of them Unless we, of course, list them all one by one Maybe something like this override_dh_install: dh_install rm path/DroidSansFallback.ttf || true rm path/DroidSansFallbackLegacy.ttf || true signature.asc Description: Digital signature
Bug#762162: gdb output (2)
Same issue here since I made a dist-upgrade yesterday. Geeqie crashed on start-up with previous configuration files. After removing them (and the cache for good measure), it now crashes as soon as you load an image. Run this in a directory containing a picture: $ gdb -batch -n -ex run -ex bt -ex 'thread apply all bt full' --args geeqie [Thread debugging using libthread_db enabled] Using host libthread_db library /lib/x86_64-linux-gnu/libthread_db.so.1. Creating Geeqie dir:/home/personnel/.config/geeqie Creating Geeqie dir:/home/personnel/.cache/geeqie/thumbnails [New Thread 0x7fffebaa0700 (LWP 10436)] [New Thread 0x7fffeb08f700 (LWP 10437)] Program received signal SIGSEGV, Segmentation fault. append_escaped_text (length=optimized out, text=optimized out, str=0xa34ba0) at /build/glib2.0-tWPgvS/glib2.0-2.40.0/./glib/gmarkup.c:2162 2162/build/glib2.0-tWPgvS/glib2.0-2.40.0/./glib/gmarkup.c: No such file or directory. #0 append_escaped_text (length=optimized out, text=optimized out, str=0xa34ba0) at /build/glib2.0-tWPgvS/glib2.0-2.40.0/./glib/gmarkup.c:2162 #1 g_markup_escape_text (text=optimized out, length=optimized out, length@entry=-1) at /build/glib2.0-tWPgvS/glib2.0-2.40.0/./glib/gmarkup.c:2238 #2 0x779e0317 in gtk_widget_set_property (object=0x91ced0, prop_id=optimized out, value=0x7fffd120, pspec=optimized out) at /build/gtk+2.0-zztKf7/gtk+2.0-2.24.24/gtk/gtkwidget.c:2739 #3 0x761690a1 in object_set_property (nqueue=optimized out, value=optimized out, pspec=optimized out, object=optimized out) at /build/glib2.0-tWPgvS/glib2.0-2.40.0/./gobject/gobject.c:1378 #4 g_object_set_valist (object=0x91ced0, first_property_name=0x76e190 \340\206u, var_args=0x7fffd1d0) at /build/glib2.0-tWPgvS/glib2.0-2.40.0/./gobject/gobject.c:2104 #5 0x76169934 in g_object_set (_object=0x91ced0, first_property_name=0x77a5be06 tooltip-text) at /build/glib2.0-tWPgvS/glib2.0-2.40.0/./gobject/gobject.c:2214 #6 0x7798b52d in gtk_tool_button_update (activatable=0x77aab0, action=0x801e30, property_name=0x77af5c4c tooltip) at /build/gtk+2.0-zztKf7/gtk+2.0-2.24.24/gtk/gtktoolbutton.c:821 #7 0x779830c7 in gtk_toggle_tool_button_update (activatable=0x77aab0, action=0x801e30, property_name=0x77af5c4c tooltip) at /build/gtk+2.0-zztKf7/gtk+2.0-2.24.24/gtk/gtktoggletoolbutton.c:329 #8 0x76161415 in g_closure_invoke (closure=0x91e7a0, return_value=0x0, n_param_values=2, param_values=0x7fffd4d0, invocation_hint=0x7fffd470) at /build/glib2.0-tWPgvS/glib2.0-2.40.0/./gobject/gclosure.c:768 #9 0x761739dc in signal_emit_unlocked_R (node=node@entry=0x757280, detail=detail@entry=578, instance=instance@entry=0x801e30, emission_return=emission_return@entry=0x0, instance_and_params=instance_and_params@entry=0x7fffd4d0) at /build/glib2.0-tWPgvS/glib2.0-2.40.0/./gobject/gsignal.c:3551 #10 0x7617c208 in g_signal_emit_valist (instance=optimized out, signal_id=optimized out, detail=optimized out, var_args=var_args@entry=0x7fffd660) at /build/glib2.0-tWPgvS/glib2.0-2.40.0/./gobject/gsignal.c:3307 #11 0x7617c46f in g_signal_emit (instance=optimized out, signal_id=optimized out, detail=optimized out) at /build/glib2.0-tWPgvS/glib2.0-2.40.0/./gobject/gsignal.c:3363 #12 0x76165b35 in g_object_dispatch_properties_changed (object=0x7fffea641010, n_pspecs=1, pspecs=0x0) at /build/glib2.0-tWPgvS/glib2.0-2.40.0/./gobject/gobject.c:1053 #13 0x761653ae in g_object_notify_queue_thaw (object=0x801e30, nqueue=optimized out) at /build/glib2.0-tWPgvS/glib2.0-2.40.0/./gobject/gobject.c:290 #14 0x76169105 in g_object_set_valist (object=0x801e30, first_property_name=0x0, var_args=0x7fffd930) at /build/glib2.0-tWPgvS/glib2.0-2.40.0/./gobject/gobject.c:2110 #15 0x76169934 in g_object_set (_object=0x801e30, first_property_name=first_property_name@entry=0x4e399a tooltip) at /build/glib2.0-tWPgvS/glib2.0-2.40.0/./gobject/gobject.c:2214 #16 0x00474382 in layout_util_sync_color (lw=0x78a580) at layout_util.c:2292 #17 0x0046865f in layout_status_update_image (lw=0x78a580) at layout.c:530 #18 0x0045cbf3 in image_update_util (imd=optimized out) at image.c:91 #19 image_post_process_color (start_row=optimized out, run_in_bg=optimized out, imd=optimized out) at image.c:350 #20 image_change_pixbuf (imd=0x885200, pixbuf=0x967820, zoom=5.411089589487498e-312, zoom@entry=0, lazy=10234784) at image.c:1107 #21 0x0045d8b3 in image_load_area_cb (il=optimized out, x=0, y=0, w=optimized out, h=optimized out, data=optimized out) at image.c:607 #22 0x76161415 in g_closure_invoke (closure=0x9c45a0, return_value=0x0, n_param_values=5, param_values=0x7fffdd80, invocation_hint=0x7fffdd20) at /build/glib2.0-tWPgvS/glib2.0-2.40.0/./gobject/gclosure.c:768 #23 0x761739dc in signal_emit_unlocked_R (node=node@entry=0x756dd0,
Bug#762291: libuv-dev: Doing apt-get update shows error on this package
Control: reassign libuv0.10-dev 0.10.28-4 On Sb, 20 sep 14, 20:01:23, Eric Valette wrote: Package: libuv-dev Version: 0.10.28-4 Severity: important apt-get update ... Lecture des listes de paquets... Fait W: Ignoring Provides line with DepCompareOp for package libuv-dev W: Vous pouvez lancer « apt-get update » pour corriger ces problèmes. -- System Information: Debian Release: jessie/sid APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 3.16.3 (SMP w/8 CPU cores; PREEMPT) Locale: LANG=fr_FR.UTF8, LC_CTYPE=fr_FR.UTF8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash -- http://wiki.debian.org/FAQsFromDebianUser Offtopic discussions among Debian users and developers: http://lists.alioth.debian.org/mailman/listinfo/d-community-offtopic http://nuvreauspam.ro/gpg-transition.txt signature.asc Description: Digital signature
Bug#761939: [ITR] templates://solaar/{solaar.templates}
Dear Debian maintainer, The Debian internationalisation team and the Debian English localisation team will soon begin the review of the debconf templates used in solaar. This review takes place for all packages that use debconf to interact with users and its aims are: - to improve the use of English in all debconf templates; - to make the wording of debconf templates more consistent; - to encourage more translations of templates. Even if your first language is English, this process is likely to help track down typos or errors, and improve consistency between the debconf templates of your package and that of other packages in the distribution. The process involves both debian-l10n-english contributors and Debian translators. The details of the process are given in http://wiki.debian.org/I18n/SmithDebconfReviewProcess. I will act as the coordinator of this activity for solaar. The first step of the process is to review the debconf source template file(s) of solaar. This review will start on Wednesday, September 24, 2014, or as soon as you acknowledge this mail with an agreement for us to carry out this process. All parts of the process will be carried out in close collaboration with you, and, unless you explicitly ask for it, no upload nor NMU will happen for solaar. If you approve this process, please let us know by replying to this mail. If some work in progress on your side would conflict with such a rewrite (such as adding or removing debconf templates), please say so, and we will defer the review to later in the development cycle. Thank you for your attention. -- signature.asc Description: Digital signature
Bug#761942: [ITR] templates://arb/{arb-common.templates}
Dear Debian maintainer, The Debian internationalisation team and the Debian English localisation team will soon begin the review of the debconf templates used in arb. This review takes place for all packages that use debconf to interact with users and its aims are: - to improve the use of English in all debconf templates; - to make the wording of debconf templates more consistent; - to encourage more translations of templates. Even if your first language is English, this process is likely to help track down typos or errors, and improve consistency between the debconf templates of your package and that of other packages in the distribution. The process involves both debian-l10n-english contributors and Debian translators. The details of the process are given in http://wiki.debian.org/I18n/SmithDebconfReviewProcess. I will act as the coordinator of this activity for arb. The first step of the process is to review the debconf source template file(s) of arb. This review will start on Wednesday, September 24, 2014, or as soon as you acknowledge this mail with an agreement for us to carry out this process. All parts of the process will be carried out in close collaboration with you, and, unless you explicitly ask for it, no upload nor NMU will happen for arb. If you approve this process, please let us know by replying to this mail. If some work in progress on your side would conflict with such a rewrite (such as adding or removing debconf templates), please say so, and we will defer the review to later in the development cycle. Thank you for your attention. -- signature.asc Description: Digital signature
Bug#762173: laptop-mode-tools: Configuring or disabling autosuspend does not work
Control: tag -1 +moreinfo On Friday 19 September 2014 01:39 PM, Per Andersson wrote: After installing laptop-mode-tools my USB mouse autosuspends and needs to be revived with a mouse click. I have tried blacklisting the device id by setting AUTOSUSPEND_USE_WHITELIST=0 AUTOSUSPEND_RUNTIME_DEVID_BLACKLIST=046d:c068 and then restarting. This doesn't disable autosuspend for the device. I have received numerous reports but eventually there is a mis configuration somewhere. Do you have usb-autosuspend module purged ? Can you please confirm that ? Disabling it totally, by setting CONTROL_RUNTIME_AUTOSUSPEND=1, does not work either. To disable it, you need to set it to 0. Furthermore, laptop-mode-tools autosuspend is not disabled or reset when the package is removed. Hmmm!! I'm not sure now if the problem lies with laptop-mode-tools. -- Ritesh Raj Sarraf RESEARCHUT - http://www.researchut.com Necessity is the mother of invention. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#762329: libjson-any-perl: breaks libcgi-application-plugin-ajaxupload-perl test suite
Package: libjson-any-perl Version: 1.36-1 Severity: serious Control: clone -1 -2 -3 Control: retitle -2 libcgi-application-plugin-ajaxupload-perl: FTBFS with libjson-any-perl 1.36-1: test failures Control: tags -2 sid Control: reassign -2 libcgi-application-plugin-ajaxupload-perl 0.0.3-6 Control: retitle -3 libpackage-stash-perl: compile time warnings when used with namespace::clean Control: severity -3 normal Control: block -2 with -3 Control: block -1 with -3 Control: tags -3 upstream patch Control: thanks (we'll see how that goes :) libjson-any-perl_1.36-1 breaks the libcgi-application-plugin-ajaxupload-perl test suite: # Failed test 'no warnings' # at /usr/share/perl5/Test/NoWarnings.pm line 45. # There were 2 warning(s) # Previous test 0 '' # Name JSON::Any::croak used only once: possible typo at /usr/share/perl5/Package/Stash/PP.pm line 193. # at /usr/share/perl5/Package/Stash/PP.pm line 193. [...] Test Summary Report --- t/02.warnings.t (Wstat: 256 Tests: 12 Failed: 1) Failed test: 12 Non-zero exit status: 1 t/03.images.t (Wstat: 256 Tests: 10 Failed: 1) Failed test: 10 Non-zero exit status: 1 t/04-resize.t (Wstat: 256 Tests: 12 Failed: 1) Failed test: 12 Non-zero exit status: 1 This seems to be a long-standing latent bug in libpackage-stash-perl, triggered by the new libjson-any-perl which started to use namespace::clean. It only happens when Package::Stash::PP is used, i.e. without libpackage-stash-xs-perl installed. % perl -wT -MJSON::Any -e1 Name JSON::Any::carp used only once: possible typo at /usr/share/perl5/Package/Stash/PP.pm line 193. Name JSON::Any::croak used only once: possible typo at /usr/share/perl5/Package/Stash/PP.pm line 193. % PACKAGE_STASH_IMPLEMENTATION=PP perl -Tw -MPackage::Stash -e 'package foo; use Carp q/croak/; use namespace::clean; 1;' Name foo::croak used only once: possible typo at /usr/share/perl5/Package/Stash/PP.pm line 193. The easy fix is adding no warnings 'once'; in Package/Stash/PP.pm around line 193. However, the fact that it needs taint checks enabled to happen is a bit weird and might mean there's more to it. It's probably best to apply the above fix quickly but forward the issue upstream for more discussion. I'm filing the bug against libjson-any-perl only to prevent it reaching testing before the issue is fixed esewhere. If it's too late, that one can be closed and the libcgi-application-plugin-ajaxupload-perl 'sid' tag should be removed. IOW, I don't think libjson-any-perl_1.36-1 is buggy in itself. -- Niko Tyni nt...@debian.org -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#762330: libjsoncpp0: please update package for jessie
Package: libjsoncpp0 Version: 0.6.0~rc2-3 Severity: wishlist Dear José, the libjsoncpp packages is outdated and upstream provided fixes for a couple of issues (cf. #753560, which spoils minetest). Please update the package for jessie. Thanks and best regards, Andi -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#761593: no audio since binNMU to link against newer libav*
reassign 761593 libmlt6 found 761593 0.9.2-1+b1 notfound 761593 0.9.2-1 thanks This issue appeared when libmlt6 was recompiled against libav* 0.11, and reinstalling libmlt6 0.9.2-1 and the older libav* dependencies - now only available at snapshot.debian.org - it works correctly again. - 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#750586: Bug#756275: debian-installer: [PATCH] Fix lib location and search path for syslinux = 5
On Sat, Sep 20, 2014 at 02:28:24PM -0700, Chris Kuehl wrote: Hi all, Thanks for your work on this -- we're also experiencing this bug in both jessie and sid daily netboot images in our PXE boot environment. On Thu, Aug 07, 2014 at 01:46:06PM +0200, Cyril Brulebois wrote: I could apply it blindly but it'd be nice if someone else would confirm it works fine. I've got other things cooking, but I might end up testing it myself it nobody steps up. I might be building the image wrong, No, it looks like you did everything right afaics :) That was a blind and untested patch, working backward from what I'd hand-hacked in place to get it working for me, at the end of a long day, and the first time I'd ever even looked at this code ... It looks like I read $(TEMP_NETBOOT_DIR)/$(BOOT_SCREEN_DIR) wrong in the surrounding code and assumed BOOT_SCREEN_DIR only had the /boot-screens part in it. Or at least that's the only thing I can think I must have done, since now that you've pointed, and I'm looking at it again, your version of that link definitely looks like the right one to me. Indeed amd64/netboot.cfg has: BOOT_SCREEN_DIR = $(NETBOOT_PATH)/boot-screens/ Only the ia64 version appears to define or use it how I used it there. Thanks for actually testing this and sending a fixed patch! Cheers, Ron but after applying Ron's patch, I get a symlink like the following in my netboot tarball: ldlinux.c32 - debian-installer/amd64/debian-installer/amd64/boot-screens//ldlinux.c32 Note that ``d-i/$arch'' is duplicated, and there is an extra slash before ``ldlinux.c32''. During my build, the relevant vars were: NETBOOT_PATH=debian-installer/amd64 BOOT_SCREEN_DIR=debian-installer/amd64/boot-screens/ I've attached a small patch (intended to be applied after Ron's) which fixes the target path of the symlink on my sid build. With these two patches applied, the sid netboot image boots and installs successfully in our environment. I'd be more than happy to help test any additional work on this issue. Thanks! Chris From 89f74fdc2893a68d2baba8d13cff4846d92840e8 Mon Sep 17 00:00:00 2001 From: Chris Kuehl cku...@ocf.berkeley.edu Date: Sat, 20 Sep 2014 21:00:11 + Subject: [PATCH] Fix ldlinux.c32 symlink path The existing symlink creates a target path like: debian-installer/amd64/debian-installer/amd64/boot-screens//ldlinux.c32 (note the duplicate of d-i/amd64/ and the double slash after boot-screens) --- build/config/x86.cfg | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/build/config/x86.cfg b/build/config/x86.cfg index 07f99b8..0bcd2a9 100644 --- a/build/config/x86.cfg +++ b/build/config/x86.cfg @@ -393,7 +393,7 @@ arch_netboot_dir: x86_syslinux ln -sf $(NETBOOT_PATH)/pxelinux.0 $(TEMP_NETBOOT_DIR)/pxelinux.0 # This link is required because pxelinux only looks in the tftp root # for this library (it does a PATH search for any others). - ln -sf $(NETBOOT_PATH)/$(BOOT_SCREEN_DIR)/ldlinux.c32 $(TEMP_NETBOOT_DIR)/ldlinux.c32 + ln -sf $(BOOT_SCREEN_DIR)ldlinux.c32 $(TEMP_NETBOOT_DIR)/ldlinux.c32 set -e; \ $(foreach file,$(wildcard $(TEMP_BOOT_SCREENS)/*.txt), \ -- 2.1.0 -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#762228: RFS: ufoai-music review
On Sun, 2014-09-21 at 03:50 +0300, Peter Pentchev wrote: On Sat, Sep 20, 2014 at 10:10:00AM +0200, Christian Kastner wrote: Hi Markus, On 2014-09-20 01:22, Markus Koschany wrote: The debian/copyright file is identical for ufoai-data, ufoai-music and ufoai-maps. I find this somewhat confusing. Generally speaking, I don't believe that listing the copyright of files which are not part of the source package (in fact, which are part of another package) is policy-conform, regardless of whether upstream created the source split, or you. Just as a minor data-point, I think that it might actually be policy-conformant, as witnessed by e.g. Policy 12.5, the section about /usr/share/doc/package being a symlink to another directory. True, it discusses a slightly different case (two packages coming from the same source package), but I do believe that the intent is exactly the same - a single source package generating, say, two packages (a binary one and a data one), with the same copyright file for both. Not sure if you refering to Markus' or Christian's position when you say might be actually .. conformant .. So you wanted to state that duplicate d/copyrights are _not_ allowed for different source packages, I agree. Otherwise I think not. We might want to refine wording here, that everyone knows what I mean when I say (Debian-)source-package. We have one upstream repository snapshot split into 4 orig.tar (upstream sourcee package) and 4 (Debian-)source packages. Binary packages are the result of a (Debian-)source-package. §5.6 and §4.4 defines the Debian-source-package's name. So in our case we have 4 Debian-source packages: ufoai, ufoai-data, ufoai-music and ufoai-maps. Also d/copyright is to document the copyright for the source used to generate the binary packages. 12.5 reads only about source, so this term might be ambiguous between upstream and Debian. However, the rest of the policy does often use it in the context of unpacked source. However, there is another clause quite similar to the symling clause of 12.5.: It is in 12.3 and reads: /usr/share/doc/package may be a symbolic link to another directory in /usr/share/doc only if the two packages both come from the same source and the first package Depends on the second.[116] The footnote 116 then helps to make it clear: Please note that this does not override the section on changelog files below, so the file /usr/share/doc/package/changelog.Debian.gz must refer to the changelog for the current version of package in question. In practice, this means that the sources of the target and the destination of the symlink must be the same (*same source package and version*). So I believe we need to have the same source packages to allow symlinks, to doc or, in our case duplicated copyright files. The copyright file would have to contain information about all the files in the two binary packages, Minor correction: As the copyright file is the documentation of the undelaying source package, it does not document the files in the binary package. which means that for each of the binary packages its copyright file would contain information about files that are part of another package. s/package/source package? That would be my point. It's true that the Debian Policy does not contain explicit provisions for this case - two different source packages coming from the same upstream distribution point - and it's true that the final say in these matters belongs to the FTP Masters. I think §4.5, in the Chapter Source Package, by using verbatim the intention is made quite clear: 4.5 Copyright: debian/copyright Every package must be accompanied by a verbatim copy of its copyright information and distribution license in the file /usr/share/doc/package/copyright Yes, FTP-Masters will have the final word, but it will not me how presents a package containing this question to them. Markus also already committed to a split of d/copyright. -- tobi G'luck, Peter signature.asc Description: This is a digitally signed message part
Bug#762331: Hardening options incomplete (CPPFLAGS, LDFLAGS)
Package: ifplugd
Version: 0.28-19
Severity: important
Tags: patch
User: hardening-disc...@lists.alioth.debian.org
Usertags: goal-hardening
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Hello,
Please enable CPPFLAGS and LDFLAGS from dpkg-buildflags (patch
attached). dpkg-buildflags handle noopt from DEB_BUILD_OPTIONS.
-BEGIN PGP SIGNATURE-
Version: GnuPG v1
iQIcBAEBCAAGBQJUHotAAAoJEJmGUYuaqqClMqsP/18Wlil2RQmuffUGNh8onHno
Yb5y30UbZzco94KbhhrahfOT5FZ/fsQaX7GUkED68rf8WJOiFMH9kcTEP0k1d4o7
MJmrNzbiEIgOqFLKWX2pP/KnNsWh1SIj4FL04ELCh8bfwAoP+pEmmx6uxrIT2NUc
6PU/MdQIGQNA/FB+n5fGwD0wwjxeiQRAja7lmzP+Oqu9PLp3K4kByDFJOSLsnYJq
GdjkuAc8oh2O+gsE0sttxiGqpgJbrq9YB22XMEPlgbm4cvrmfb0SguXfYcN20WzC
0v/BrGRSzZkJlCat9qqSbaGOx8WpdU/9eeXLiLjPeCn3jwgSnAIwgKOXJZAj0HNk
nARIM9pqbsYBDAKDWjXfIka5iKIguLVhk7jktg75GiWU4ClcGE9VwyYqmMcQTeHp
NjIKriPuPy1MXfiCNVZMqOhQMhcKuYROTBvsknL8TSARuzCQhCUbngEkaDaowFT2
VFyB5GM2D5cLR6U/e8Yg6qyvIudvgTllm/BPI7XDKJ3r0u7uI768svJFB+aMPiJg
04t3BZzoeCCODtx/obE9nHuzHJDfp5gos+PAplUP0xqdksdt3Fd4hIUmaTYYSqaG
HfM8NXM7YUHIbapbZOFdQ7qGrbKwzNTB921R8/srYlVmOAXr58Z/l1HuCvmTm0Pp
G491jTPJwrRwGG5DwJI8
=R9QO
-END PGP SIGNATURE-
diff -u ifplugd-0.28/debian/changelog ifplugd-0.28/debian/changelog
--- ifplugd-0.28/debian/changelog
+++ ifplugd-0.28/debian/changelog
@@ -1,3 +1,10 @@
+ifplugd (0.28-19.1) unstable; urgency=medium
+
+ * Non-maintainer upload.
+ * Use dpkg-buildflags and pass *FLAGS to configure
+
+ -- Guillaume Delacour g...@iroqwa.org Sun, 21 Sep 2014 10:09:39 +0200
+
ifplugd (0.28-19) unstable; urgency=low
* Added interface poll delay 1sec using the new -T option. (Closes:
diff -u ifplugd-0.28/debian/rules ifplugd-0.28/debian/rules
--- ifplugd-0.28/debian/rules
+++ ifplugd-0.28/debian/rules
@@ -4,19 +4,14 @@
#export DH_VERBOSE=1
include /usr/share/dpatch/dpatch.make
+DPKG_EXPORT_BUILDFLAGS = 1
+include /usr/share/dpkg/buildflags.mk
# These are used for cross-compiling and for saving the configure script
# from having to guess our platform (since we know it already)
DEB_HOST_GNU_TYPE ?= $(shell dpkg-architecture -qDEB_HOST_GNU_TYPE)
DEB_BUILD_GNU_TYPE ?= $(shell dpkg-architecture -qDEB_BUILD_GNU_TYPE)
-CFLAGS = -Wall -g
-
-ifneq (,$(findstring noopt,$(DEB_BUILD_OPTIONS)))
- CFLAGS += -O0
-else
- CFLAGS += -O2
-endif
ifeq (,$(findstring nostrip,$(DEB_BUILD_OPTIONS)))
INSTALL_PROGRAM += -s
endif
@@ -36,7 +31,7 @@
cp -f /usr/share/misc/config.guess config.guess
endif
[ ! -f doc/README.html ] || mv -f doc/README.html doc/README.html.ups
- ./configure --host=$(DEB_HOST_GNU_TYPE) --build=$(DEB_BUILD_GNU_TYPE) --prefix=/usr --mandir=\$${prefix}/share/man --sysconfdir=/etc CFLAGS=$(CFLAGS) LDFLAGS=-Wl,-z,defs $(confopts)
+ ./configure --host=$(DEB_HOST_GNU_TYPE) --build=$(DEB_BUILD_GNU_TYPE) --prefix=/usr --mandir=\$${prefix}/share/man --sysconfdir=/etc CFLAGS=$(CFLAGS) CPPFLAGS=$(CPPFLAGS) LDFLAGS=$(LDFLAGS) -Wl,-z,defs $(confopts)
touch $@
build: build-stamp
Bug#762332: winpdb: diff for NMU version 1.4.8-2.1
Package: winpdb
Version: 1.4.8-2
Severity: normal
Tags: patch
Dear maintainer,
I've uploaded an NMU for winpdb (versioned as 1.4.8-2.1). Attached
is a debdiff showing the changes.
Cheers,
Olly
diff -Nru winpdb-1.4.8/debian/changelog winpdb-1.4.8/debian/changelog
--- winpdb-1.4.8/debian/changelog 2014-09-21 20:24:21.0 +1200
+++ winpdb-1.4.8/debian/changelog 2014-09-21 19:37:16.0 +1200
@@ -1,3 +1,15 @@
+winpdb (1.4.8-2.1) unstable; urgency=medium
+
+ * Non-maintainer upload at maintainer's request.
+ * Update from dpatch to 3.0 (quilt), fixing lintian error.
+ * Update for wxPython 3.0 (Closes: #759093):
+- New patch: wxpython3.0.patch
+ * Fix Failed to find script error (Closes: #757718):
+- New patch from Frederik Juul Christiani: no-disable-factory.patch
+ * Drop BD on lsb-release which is no longer used. (Closes: #737535)
+
+ -- Olly Betts o...@survex.com Sun, 21 Sep 2014 07:37:15 +
+
winpdb (1.4.8-2) unstable; urgency=low
* Including some ideas from #670968:
diff -Nru winpdb-1.4.8/debian/control winpdb-1.4.8/debian/control
--- winpdb-1.4.8/debian/control 2014-09-21 20:24:21.0 +1200
+++ winpdb-1.4.8/debian/control 2014-09-21 18:34:30.0 +1200
@@ -3,8 +3,8 @@
Priority: optional
Maintainer: Bernd Zeimetz b...@debian.org
Uploaders: Python Applications Packaging Team python-apps-t...@lists.alioth.debian.org
-Build-Depends: debhelper (= 7.0.50~), python (= 2.6.6-3~), dpatch
-Build-Depends-Indep: docbook-to-man, lsb-release
+Build-Depends: debhelper (= 7.0.50~), python (= 2.6.6-3~)
+Build-Depends-Indep: docbook-to-man
Standards-Version: 3.9.3
Homepage: http://www.winpdb.org/
Vcs-Svn: svn://svn.debian.org/python-apps/packages/winpdb/trunk/
@@ -13,7 +13,7 @@
Package: winpdb
Architecture: all
Depends: ${python:Depends}, ${misc:Depends}
-Recommends: x-terminal-emulator | screen, python-wxversion, python-wxgtk2.8, python-crypto
+Recommends: x-terminal-emulator | screen, python-wxversion, python-wxgtk3.0, python-crypto
Description: Platform independent Python debugger
Winpdb supports debugging of threads- and curses based applications,
namespace modification and embedded debugging. As a remote debugger,
diff -Nru winpdb-1.4.8/debian/patches/00dpatch.conf winpdb-1.4.8/debian/patches/00dpatch.conf
--- winpdb-1.4.8/debian/patches/00dpatch.conf 2014-09-21 20:24:21.0 +1200
+++ winpdb-1.4.8/debian/patches/00dpatch.conf 1970-01-01 12:00:00.0 +1200
@@ -1,2 +0,0 @@
-conf_debianonly=1
-conf_origtargzpath=../tarballs
diff -Nru winpdb-1.4.8/debian/patches/00list winpdb-1.4.8/debian/patches/00list
--- winpdb-1.4.8/debian/patches/00list 2014-09-21 20:24:21.0 +1200
+++ winpdb-1.4.8/debian/patches/00list 1970-01-01 12:00:00.0 +1200
@@ -1 +0,0 @@
-winpdb-debian-wx-hint
diff -Nru winpdb-1.4.8/debian/patches/no-disable-factory.patch winpdb-1.4.8/debian/patches/no-disable-factory.patch
--- winpdb-1.4.8/debian/patches/no-disable-factory.patch 1970-01-01 12:00:00.0 +1200
+++ winpdb-1.4.8/debian/patches/no-disable-factory.patch 2014-09-21 19:13:59.0 +1200
@@ -0,0 +1,20 @@
+Description: Don't pass obsolete --disable-factory option to gnome-terminal
+ This option is no longer accepted, leading to Failed to find script error.
+Author: Frederik Juul Christiani frede...@christiani.dk
+Bug-Debian: https://bugs.debian.org/757718
+Forwarded: no
+Last-Update: 2014-09-21
+
+Index: winpdb-1.4.8/rpdb2.py
+===
+--- winpdb-1.4.8.orig/rpdb2.py
winpdb-1.4.8/rpdb2.py
+@@ -1780,7 +1780,7 @@ osSpawn = {
+ NT_DEBUG: 'start rpdb2 - Version ' + get_version() + ' - Debuggee Console cmd.exe /K %(exec)s %(options)s',
+ POSIX: %(term)s -e %(shell)s -c '%(exec)s %(options)s; %(shell)s' ,
+ 'Terminal': Terminal --disable-server -x %(shell)s -c '%(exec)s %(options)s; %(shell)s' ,
+-GNOME_DEFAULT_TERM: gnome-terminal --disable-factory -x %(shell)s -c '%(exec)s %(options)s; %(shell)s' ,
++GNOME_DEFAULT_TERM: gnome-terminal -x %(shell)s -c '%(exec)s %(options)s; %(shell)s' ,
+ MAC: '%(exec)s %(options)s',
+ DARWIN: '%(exec)s %(options)s',
+ SCREEN: 'screen -t debuggee_console %(exec)s %(options)s'
diff -Nru winpdb-1.4.8/debian/patches/series winpdb-1.4.8/debian/patches/series
--- winpdb-1.4.8/debian/patches/series 1970-01-01 12:00:00.0 +1200
+++ winpdb-1.4.8/debian/patches/series 2014-09-21 18:29:59.0 +1200
@@ -0,0 +1,3 @@
+winpdb-debian-wx-hint.patch
+wxpython3.0.patch
+no-disable-factory.patch
diff -Nru winpdb-1.4.8/debian/patches/winpdb-debian-wx-hint.dpatch winpdb-1.4.8/debian/patches/winpdb-debian-wx-hint.dpatch
--- winpdb-1.4.8/debian/patches/winpdb-debian-wx-hint.dpatch 2014-09-21 20:24:21.0 +1200
+++ winpdb-1.4.8/debian/patches/winpdb-debian-wx-hint.dpatch 1970-01-01 12:00:00.0 +1200
@@ -1,23 +0,0 @@
-#! /bin/sh /usr/share/dpatch/dpatch-run
-## winpdb-debian-wx-hint.dpatch by Bernd Zeimetz
Bug#762335: man-db trigger always fails being unable to create index cache
Package: man-db Version: 2.6.7.1-1 Severity: normal Almost every time I install or remove some software (on a freshly installed jessie system as of today, Sept-2014), when man-db dpkg trigger is run, I see the following message: Building database of manual pages ... /usr/bin/mandb: can't create index cache /var/cache/man/uk/5773: No such file or directory (with varied subdir and the number). /var/cache/man directory is empty. As far as I remember, this problem hasn't been present before. Thanks, /mjt -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#762296: [Pkg-fonts-devel] Bug#762296: Bug#762296: Droid Sans Fallback refers to three different files
Quoting Christian PERRIER (2014-09-21 09:52:13) So something needs to be done. With my Ubuntu glasses I think the best solution is to stop letting fonts-droid install DroidSansFallback.ttf and DroidSansFallbackLegacy.ttf for now. Then, if it's considered important to include them somehow, it should be done in a more carefully considered manner. H, that seems sensible. I'm puzzled, though, by the less worse way to achieve this. As of now, we have: bubulle@sesostris:~/src/debian/pkg-fonts/git/fonts-android(master) $ more debian/fonts-droid.install Droid*.ttf usr/share/fonts/truetype/droid ... So basically : let's install all fonts whose name starts with Droid . How can we technically do All fonts whose name starts with 'Droid' but two of them Unless we, of course, list them all one by one Maybe something like this override_dh_install: dh_install rm path/DroidSansFallback.ttf || true rm path/DroidSansFallbackLegacy.ttf || true How about this instead: Droid*.ttf usr/share/fonts-droid/truetype ...and then register DroidSansFull.ttf with alternatives system, symlinking it into usr/share/fonts/truetype/droid/DroidSans.ttf - 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#761647: kde-full: an poweroff never succeed with kde
Le lundi 15 septembre 2014, 19:13:14 Maximiliano Curia a écrit : ¡Hola merlin! On Lu, 15 sep 14, 12:16:23, merlin wrote: When I click the window extinction in 30 seconds, the operation is very long more than 4 minutes and always ends by the reboot message [ 43302,405120 ]: system halted without the computer stops only average to cut electrically I test in a window Konsole : systemctl poweroff and all works fine the computer stop Ok, I have seen this behavior. Let me explain: Trying to shutdown the computer from the kde shutdown dialog doesn't work. It takes a while (longer than expected) to end the services and after halting it doesn't turn off. I've been able to reproduce the issue in my notebook until today. Today, after I upgraded everything to the current jessie versions, I re tested this bug and could still reproduce it, but after rebooting (i.e. restarting all the services) it started working correctly. I believe this is a bug creeping from udev/systemd/upower, that seems to be gone in the current versions. Merlin, could you please upgrade your system and confirm if after a reboot the issue is fixed for you? Happy hacking, My Sid system is up to date and the problem is on the agenda unfortunately always. With a novelty, further to the last update of Systemd I am blocked(surrounded) during 5 minutes with a message concerning the stop(ruling) of Samba I created Bug*762087 concerning this problem. I think that the problem which arrived with Systemd is caused by a mismanagement of Kde and Systemd. Best Regards Philippe Merlin -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#760061: Please giveback zsh 5.0.6-2 on armhf
Hi we currently experience occassional hangs of the script which executes the zsh test suite. It happens across all architectures and approximately in 5-10% of all builds on the buildds -- but nearly never outside (even with pbuilder) which makes it very difficult to debug. Upstream is aware of it. See https://bugs.debian.org/760061 (Cc'ed) for details. The previous 5.0.6-1 upload was affected on three architectures, 5.0.6-2 only on a single one so far (armhf; arm64 still being in needs-build state). So please giveback zsh on armhf: gb zsh_5.0.6-2 . armhf TIA! Regards, Axel -- ,''`. | Axel Beckert a...@debian.org, http://people.debian.org/~abe/ : :' : | Debian Developer, ftp.ch.debian.org Admin `. `' | 1024D: F067 EA27 26B9 C3FC 1486 202E C09E 1D89 9593 0EDE `-| 4096R: 2517 B724 C5F6 CA99 5329 6E61 2FF9 CD59 6126 16B5 signature.asc Description: Digital signature
Bug#762265: ITP: glueviz -- Linked data visualization in Python
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Dear Josue, thank you for taking over the packaging of glueviz! I am glad to create interest for this package on such a short notice. Could I ask you to send a short mail to Chris Beaumont beaum...@hawaii.edu (upstream lead) and Thomas Robitaille thomas.robitai...@gmail.com (astropy) so that they are informed that packaging has started? I also got an e-mail from Jean-Christophe Jaskula jchristophe.deb...@gmail.com who offered help on packaging which may be worthwile. If you need a sponsor once the package is ready, I am glad to do this. Best regards Ole -BEGIN PGP SIGNATURE- Version: GnuPG v1 iQIcBAEBAgAGBQJUHpAqAAoJEHEVr9B3ENz3DCIP/jK9EvNujqCaOD/ULhC/cof+ YliY6BYZBsn0ZVecq1NAcNasrd68FDuluNyszXL1LjpG+tx7lGTwuGRc3fjx//5g 1Pl1+KOeCJdnwQnDC8ywO/iUdkLy3wPfOK6NUTJfekUyL3JyfGWH8OqPju9wXy+2 A45/MwXnpk14Mnp7Mll9ovQHWK5iR0o/41zT00eD21WQWCm7GhwrDG+aJaC59Fd6 8ZD9LGVSfg4D3/NI2/T0HN0gI0to+PrX0ZF4tyc6Bq01lI/BMmT5vvfUqORUEde3 WUGtU4/SXZnKgFNKvtGCa+5Fym2Mkj5op5atpbShAbyW8tuWffUWXVcsZTC6SNxK dl0WjdqVOO3pchOxcTB5BkznWXK3++IytMqsU8YoEsPrNBarGVT9hWSb/QlRSQfV RRtIjKybVqRUO0WyCE25jrlbs9lCLSoRwyPfBVoBkRG8b/bciI4jFo2yLOp5T/Mf oinCep3TcnC91VL4WBnAMluOlJtwrKYr7T+lF01Cue5reW6fGlpOhSKHDrujy81P AtLDupMbNgktoScL6U+MgbJERPG9pJjPKz9UbJc4BwMjTtlNAQX1O8wfMxqjuPki KQebl9LrBoL/04GiPP1w3NUQVKO5ubiabbDM/DJkdV8+e8pSP2PwPsfD0ckLWQH/ 30JYLomgBy1hKQmuyzds =0q8O -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#513615: #513615 - evince: No option to view text bw and/or in theme colors
Hey Michal, I think evince still doesn't have bw option. but your pdf is showed up nicely nowadays. Cheers, althaser
Bug#762336: Please enable hardened build flags
Source: bandwidthd Version: 2.0.1+cvs20090917-7 Severity: important Tags: patch User: hardening-disc...@lists.alioth.debian.org Usertags: goal-hardening -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Hello, Please enable hardened build flags with dpkg-buildflags (patch attached). dpkg-buildflags handle noopt from DEB_BUILD_OPTIONS. -BEGIN PGP SIGNATURE- Version: GnuPG v1 iQIcBAEBCAAGBQJUHpHRAAoJEJmGUYuaqqClNhQP/jYNArIMFtGuoXbnZ5dS54p+ WjybNeG948asYMeLoDT86QRYl/RYiprPqXy1dNf5/zV8qoTX5i+S39X49sKbfRQE HIEzsJOqp/+PPKK0fBZ7Yf+ScTiQMiJAnvaxTtfy6kiP++OLXl/J+Zzw0AsusEwH wGe9i+zMFuH0yEB5qr9Pst2foiPmXmK+gE7mtEe4AGdTPKRFcg9JW5TZsL8b5MFC 6PxA5LnOP2MyAoxpDJKiAFS775/fihBY2ppUz86oEh1JnjX9WFsdy5QrWqoo8LfG trc9eUSIysksjSL79akyUikia6AOQr0NxxO6LDdQIjMXVgin4BcfW9pi/g5a9A4g XU4Na6H9viLfs/y5bnfHnhl5uhygy3OVWpgh+1KvdwCzWA2PBnu0zjJ+zAo8bdSb +rg5LK4KsxrLlHEsVrBud6pigLuEPxfEIXrlqlEcSwOtkCJF2E7OiaUtCZ/Ry6jI tNVFqp21C3q6ppP31QF4VJFGga4OoLdw5cQhpfA8ARiwewrcurxy3qan3Ge8khVe SMyzaKEipSehDxyySKL/5zgiXyOWTDro5Sbal+GI3LHApxMD4TlQv8YEMpKF3OuX ccQ9khGMrdD+PRJGjEmYJKVByPK+pokcTrkk9YIQLBwuy/YIuW9obLjXWV+KMGEA azkJz++xs3S+l314ZhUP =Prxd -END PGP SIGNATURE- diff -Nru bandwidthd-2.0.1+cvs20090917/debian/changelog bandwidthd-2.0.1+cvs20090917/debian/changelog --- bandwidthd-2.0.1+cvs20090917/debian/changelog 2013-07-20 18:25:40.0 +0200 +++ bandwidthd-2.0.1+cvs20090917/debian/changelog 2014-09-21 10:39:48.0 +0200 @@ -1,3 +1,10 @@ +bandwidthd (2.0.1+cvs20090917-7.1) unstable; urgency=medium + + * Non-maintainer upload. + * Use dpkg-buildflags and pass *FLAGS to configure + + -- Guillaume Delacour g...@iroqwa.org Sun, 21 Sep 2014 10:27:23 +0200 + bandwidthd (2.0.1+cvs20090917-7) unstable; urgency=low * Move php5-gd to Recommends and also recommend php5 (Closes: #717042) diff -Nru bandwidthd-2.0.1+cvs20090917/debian/rules bandwidthd-2.0.1+cvs20090917/debian/rules --- bandwidthd-2.0.1+cvs20090917/debian/rules 2013-06-14 00:41:25.0 +0200 +++ bandwidthd-2.0.1+cvs20090917/debian/rules 2014-09-21 10:28:19.0 +0200 @@ -6,6 +6,9 @@ # Uncomment this to turn on verbose mode. #export DH_VERBOSE=1 +DPKG_EXPORT_BUILDFLAGS = 1 +include /usr/share/dpkg/buildflags.mk + configureoptions = --prefix=/usr --bindir=/usr/sbin/ --sysconfdir=/etc/bandwidthd/ --localstatedir=/var/lib/ p_bwdstatic = bandwidthd @@ -15,17 +18,6 @@ build_bwdpgsql = debian/bandwidthd-pgsql -CFLAGS = -Wall - -ifneq (,$(findstring debug,$(DEB_BUILD_OPTIONS))) - CFLAGS += -g -endif - -ifneq (,$(findstring noopt,$(DEB_BUILD_OPTIONS))) - CFLAGS += -O0 -else - CFLAGS += -O2 -endif ifeq (,$(findstring nostrip,$(DEB_BUILD_OPTIONS))) INSTALL_PROGRAM += -s endif @@ -41,7 +33,7 @@ cp -f /usr/share/misc/config.sub config.sub dh_autoreconf chmod +x configure - ./configure $(configureoptions) --disable-pgsql + $(shell dpkg-buildflags --export=cmdline) ./configure $(configureoptions) --disable-pgsql touch $@ configure-bwdpgsql: configure-bwdpgsql-stamp
Bug#759093: winpdb: Patch for wxPython 3.0
I spotted the About and Licence windows weren't sizing correctly, so I fixed that, and also dropped the BD on lsb-release which there was a bug filed about. There's one difference with wx 3.0 still - I noticed the initial positions of the sashes in the splitter windows isn't quite the same as with 2.8 (which I think is setting them where it is told to). I have confirmed the calls to SetSashPosition() do happen under 3.0, and reading the positions back afterwards gives the right numbers. It's a pretty minor issue since winpdb saves the positions in a config file and restores them on the next run (and that seems to work), so it only affects things at all the first time the user runs winpdb. I'll try to resolve what's happening, and whether it's a bug in winpdb or wx. Cheers, Olly -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#749264: No nvidia-driver working
Hi Karsten, On Sat, Sep 20, 2014 at 3:38 AM, Karsten Malcher deb...@home.decotrain.de wrote: Hello Vincent, i didn't get your email from Sat, 9 Aug 2014 or from the debian bug system. So i see it today in the bug system. Fix your smtp server so that it stops timing out. So i installed # aptitude install nvidia-glx-legacy-173xx nvidia-kernel-dkms No, just install nvidia-glx-legacy-173xx (as suggested by nvidia-detect); its dependencies will ensure that you have a working nvidia 173.xx driver installed. Installing nvidia-kernel-dkms on wheezy will actually pull in the default 304.xx driver series, which is obviously not what you want. If you take a look at the log file you attached in your followup message... [42.428] (II) NVIDIA GLX Module 304.117 Tue Nov 26 21:45:09 PST 2013 [42.445] (WW) NVIDIA(0): The NVIDIA GeForce FX 5200 GPU installed in this system is [42.445] (WW) NVIDIA(0): supported through the NVIDIA 173.14.xx Legacy drivers. [42.445] (WW) NVIDIA(0): Please visit http://www.nvidia.com/object/unix.html for [42.445] (WW) NVIDIA(0): more information. The 304.117 NVIDIA driver will ignore [42.445] (WW) NVIDIA(0): this GPU. Continuing probe... [42.445] (EE) No devices detected. It's no surprise that X won't load, given that you're trying to use the nvidia 304.xx driver series with hardware that doesn't support it. For a usable system with X there should be always a running fallback like in windows. It should be nouveau for NVidia. I don't know exactly what Knoppix is doing, but here you get a running X in nearly all cases!? Why this is not possible in Debian? nouveau should work, yes; if it doesn't, please file a bug against the kernel. Have you tried fetching a kernel from wheezy-backports and seeing if you can run nouveau using a newer kernel? Regards, Vincent -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#760509: [pkg-wine-party] Bug#760509: wine: Wine : Office 2010 no longer installs usably.
Two more datapoints : - I tried to install wine-development instead of wine : same results. - The problem with Powerpoint comes from the fact that Wine does not use the updated riched20.dll shipped with Office 2010 and is fixed by overriding it in winecfg (native, builtin). HTH, Emmanuel Charpentier Le dimanche 21 septembre 2014 à 09:20 +0200, Emmanuel Charpentier a écrit : Dear Michael, dear list, Le samedi 20 septembre 2014 à 17:10 -0400, Michael Gilbert a écrit : On Thu, Sep 4, 2014 at 4:11 PM, Emmanuel Charpentier wrote: The installation runs normally. When starting Winword for the first time, it aks for name and initial, then displays a configuration progress bar, then asks for a reboot. If one clicks on yes, thge rebooot fails and gives an error message. When asking for details, one gets the enclosed backtrace. If one refuses to reboot, the normal Winword appears, but cannot be activated. In short, the result is an unusable MS Office. Can you try without any of the wine64 packages installed, possibly without winbind also. Also try a clean .wine directory? First attempt without win64 : same results. Installed packages : charpent@asus16-ec:~$ dpkg -l *wine* | grep ii | sed -re s/[ \t]+/ /g | cut -d -f 2-3 | xargs echo libwine:i386 1.6.2-8 libwine-gecko-1.4 1.4+dfsg-2 libwine-gecko-2.21 2.21+dfsg2-1 wine 1.6.2-8 wine32 1.6.2-8 Installation of Word, Excel, Powerpoint, Access ad Office tools. No outlook no Publisher, etc... Install goes uneventfully. But the same problem as before appears when trying to use an app : When launching Word, a dialog box asking for reconfiguration appears, and asks for a reboot. Clicking yes leads to a Wine crash, clicking no opens the application, which seems more or less usable. , if Word, Excel and Access can be opened (Word with this bizarre procedure above), Powerpoint fails. Second attempt, after purging winbind : installation fails (without hints from Office nor Wine). Best wishes, No such luck... Still listening for suggestions, Emmanuel Charpentier -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#762288: security-tracker: available versions table is unnecessary
Hi Michael, On Samstag, 20. September 2014, Michael Gilbert wrote: The available versions table at the top of source package pages doesn't provide useful information related to security and duplicates information already available in the PTS, so it just adds noise to the tracker. See for example the top table at: https://security-tracker.debian.org/tracker/source-package/poppler that's true for the moment, but for the (soon to be) future I think the available version table in the top should just have the relevant summaries, while below it should display all available versions. I definitly see (and dislike) the current redundancy too. cheers, Holger signature.asc Description: This is a digitally signed message part.
Bug#762097: nat-rtsp-dkms: not work
El 20/09/14 a las #4, Julien Muchembled escribió: Control: tags -1 upstream Hello, Hello Le 09/14/14 23:37, Eduardo a écrit : get_skb_tcpdata does not return a pointer to the actual protocol string. http://mike.it-loops.com/item/29 The following patch fixed it for me, http://pastebin.com/JGw6QKVN This is an upstream issue and I don't know this software well enough to help without more information. The fact is nat-rtsp-dkms works for my use, so can you detail what does not work ? Step to reproduce, actual and expected results, from user point of view ? I read http://mike.it-loops.com/item/29 and I still don't understand the issue. I have hired an IP TV service, it uses RTSP to control for the video stream of recordings made on the network, or rent movies. When I play a recording I don't see the video with the original nat-rtsp. This is the debug log: kernel: [202359.912728] conntrackinfo = 2 kernel: [202359.919492] IP_CT_DIR_REPLY kernel: [202359.928582] IP_CT_DIR_REPLY kernel: [202359.932686] conntrackinfo = 2 kernel: [202359.936438] found a setup message kernel: [202359.936441] tran='Transport: MP2T/H2221/UDP;unicast;client_port=27524-27524 kernel: [202359.936441] ' kernel: [202359.936444] lo port found : 27524 kernel: [202359.936445] incorrect range: 27524-27524, correcting kernel: [202359.936447] udp transport found, ports=(1,27524,27525) kernel: [202359.936453] setup expectation for rtcp kernel: [202359.936456] expect_related 0.0.0.0:0-0-10.159.1.2:27524-27525 kernel: [202359.936457] NAT rtsp help_out --- help_out function kernel: [202359.973795] IP_CT_DIR_REPLY kernel: [202360.097380] IP_CT_DIR_REPLY kernel: [202368.980570] teardown handled When I do it with the patch applied works fine. This is de debug log: kernel: [202452.534205] conntrackinfo = 2 kernel: [202452.540698] IP_CT_DIR_REPLY kernel: [202452.546613] IP_CT_DIR_REPLY kernel: [202452.550763] conntrackinfo = 2 kernel: [202452.552988] found a setup message kernel: [202452.552991] tran='Transport: MP2T/H2221/UDP;unicast;client_port=27577-27577 kernel: [202452.552991] ' kernel: [202452.552994] lo port found : 27577 kernel: [202452.552995] incorrect range: 27577-27577, correcting kernel: [202452.552997] udp transport found, ports=(1,27576,27577) kernel: [202452.553003] setup expectation for rtcp kernel: [202452.553006] expect_related 0.0.0.0:0-0-10.159.1.2:27576-27577 kernel: [202452.553008] NAT rtsp help_out --- help_out function kernel: [202452.553010] hdr: len=9, CSeq: 3 kernel: [202452.553012] hdr: len=25, User-Agent: MICA-IP-STB kernel: [202452.553013] hdr: len=59, Transport: MP2T/H2221/UDP;unicast;client_port=27577-27577 -- working transport header kernel: [202452.553015] hdr: Transport -- transport header found kernel: [202452.553016] stunaddr=10.159.1.2 (auto) kernel: [202452.553037] nat expect_related 0.0.0.0:0-0-10.159.1.2:27576-27577 kernel: [202452.553039] multiple ports found, port 27577 ignored kernel: [202452.553041] rep: len=59, Transport: MP2T/H2221/UDP;unicast;client_port=27577-27577 kernel: [202452.553042] hdr: len=14, x-mayNotify: kernel: [202452.588442] IP_CT_DIR_REPLY kernel: [202452.724977] IP_CT_DIR_REPLY kernel: [202452.997084] IP_CT_DIR_REPLY kernel: [202453.249488] IP_CT_DIR_REPLY kernel: [202461.594828] teardown handled The difference between the two logs is that in the first help_out in nf_nat_rtsp.c not find the Transport header. You can see in the lines beginning with 'hdr:' after 'rtsp help out' and before IP_CT_DIR_REPLY. The Troll says get_skb_tcpdata does not return a pointer to the actual protocol string. So I try to retrieve the pointer using skb_header_pointer. And the patch does. And let's find a better title for this bug report. I titled it 'not work' because it does not work for me. And, what about 'get_skb_tcpdata does not return a pointer to the actual protocol string'? Sorry, the patch is http://pastebin.com/XsyyCxzW Sorry about my english. Julien -- Eduardo -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#762289: security-tracker: link to new pts
Hi Michael, On Samstag, 20. September 2014, Michael Gilbert wrote: The security-tracker source package pages currently link to the old pts, which has some issues like not knowing about lts. Please link to the new pts (tracker.debian.org), which does understand lts. the new tracker also has some issues, eg formatting issues in some wheezy browsers (which I happen to use), it also wastes screenspace by having too large margins between columns. also the new tracker is still beta, so I think it's sensible to wait til it has been replaced the old one officially. cheers, Holger signature.asc Description: This is a digitally signed message part.
Bug#749264: No nvidia-driver working
Am 21.09.2014 11:08, schrieb Vincent Cheng: Hi Karsten, Fix your smtp server so that it stops timing out. The DSL was burned after a lightning bolt abd the server not reachable. So i installed # aptitude install nvidia-glx-legacy-173xx nvidia-kernel-dkms No, just install nvidia-glx-legacy-173xx (as suggested by nvidia-detect); its dependencies will ensure that you have a working nvidia 173.xx driver installed. Installing nvidia-kernel-dkms on wheezy will actually pull in the default 304.xx driver series, which is obviously not what you want. If you take a look at the log file you attached in your followup message... [42.428] (II) NVIDIA GLX Module 304.117 Tue Nov 26 21:45:09 PST 2013 [42.445] (WW) NVIDIA(0): The NVIDIA GeForce FX 5200 GPU installed in this system is [42.445] (WW) NVIDIA(0): supported through the NVIDIA 173.14.xx Legacy drivers. [42.445] (WW) NVIDIA(0): Please visit http://www.nvidia.com/object/unix.html for [42.445] (WW) NVIDIA(0): more information. The 304.117 NVIDIA driver will ignore [42.445] (WW) NVIDIA(0): this GPU. Continuing probe... [42.445] (EE) No devices detected. It's no surprise that X won't load, given that you're trying to use the nvidia 304.xx driver series with hardware that doesn't support it. O.K. - but why the 304.117 driver is installed when i install dkms? It would be better that there is a dependency that announces a conflict when i want to have a 173xx driver. That's what i am meaning - it is really hard to keep an overview what you must install and what dependencies exist. nouveau should work, yes; if it doesn't, please file a bug against the kernel. Have you tried fetching a kernel from wheezy-backports and seeing if you can run nouveau using a newer kernel? Regards, Vincent As i have written nouveau failed because it does not support this hardware. But the nouveau driver from Knoppix is doing it. Experiments with new kernels in an stable working environment is causing more problems than solving it. Then you have X but you loose sound or some interface hardware ... Best regards Karsten -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#762283: redmine: not starting
This is related to ruby-awesome-nested-set which was upgraded from 2.1.6-1~bpo70+1 to 3.0.0-1 and broke redmine. You can download the package from https://packages.debian.org/wheezy-backports/all/ruby-awesome-nested-set/download and downgrade it. And at some point, redmine will probably support the newest version. -- echarp - http://www.agendadulibre.org -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#761939: [ITR] templates://solaar/{solaar.templates}
Hi Christian, Thanks for taking care of this, please go ahead with the review. I'll update the package with the resulting revised templates. Regards, Stephen -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#749321: [Python-modules-team] Bug#749321: reverse dependency of python-pypdf and ITP of python-pypdf2
On Thu, Sep 18, 2014 at 9:09 AM, Elena ``of Valhalla'' valha...@trueelena.org wrote: I've noticed that the current python-pypdf package has migrated to PyPDF2 (thus breaking all of its reverse dependencies in sid): should the updated/converted rev-dep depend on python-pypdf = 1.23-1 or python-pypdf2? How is this going to be managed? Assuming that pypdf and pypdf2 have compatible APIs, another option would be to simply patch pdfshuffler with something like: try: import pypdf except ImportError: import pypdf2 ...which would avoid having the need for restricting the dependency on python-pypdf to specific versions. Adding pypdf2 maintainer to cc list...how compatible is the pypdf2 fork with the original pypdf, and how much work would migrating applications that depend on the older pypdf to the forked version? Regards, Vincent -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#761647: kde-full: an poweroff never succeed with kde
¡Hola MERLIN! El 2014-09-21 a las 10:31 +0200, MERLIN Philippe escribió: My Sid system is up to date and the problem is on the agenda unfortunately always. With a novelty, further to the last update of Systemd I am blocked(surrounded) during 5 minutes with a message concerning the stop(ruling) of Samba I created Bug*762087 concerning this problem. 5 minutes is the normal tcp timeout, so it sounds like a network issue, some service might be getting stoped after the network went down and then it fails to communicate with the server. This might be caused by your network connection being configured in your user session through your network manager widget. So when the session ends, the network connection is closed. Another service that might be affected by this is a network file system. If you have some system dependency on having your network connection available, make sure that the network connection is applied system wide and not only during your session. I think that the problem which arrived with Systemd is caused by a mismanagement of Kde and Systemd. Sorry, I can't reproduce the issue, and I don't see a KDE mismanagement, if you want us to act on this bug we need a way to reproduce it. Happy hacking, -- By definition, when you are investigating the unknown, you do not know what you will find -- The Ultimate Principle Saludos /\/\ /\ `/ signature.asc Description: Digital signature
Bug#750080: Forwarding this to upstream
Hi, Am Sonntag, den 21.09.2014, 00:31 +0200 schrieb Sven Bartscher: On Sun, 21 Sep 2014 00:19:42 +0200 Joachim Breitner nome...@debian.org wrote: Am Samstag, den 20.09.2014, 22:35 +0200 schrieb Sven Bartscher: To me this seems much like an upstream problem, since the problem just seems to be that xmonad isn't prepared to run without ~/.xmonad/xmonad.hs. I guess a proper fix would be to either let xmonad create (and compile) a default configuration if it's missing or to run with such a default configuration without writing it to a file, but that's up to upstream. well, it used to be the case that xmonad would run happily without ~/.xmonad/xmonad.hs, and I’m surprised that it is not the case any more. Sven, did you reproduce the problem already? I didn’t find the time (which involves things like logging out :-)) yet. Yes I reproduced this (that's why I started to care about this bug). great, I wasn’t sure. To reproduce this you don't need to log out. Just switch to a tty and run: $ xinit xmonad -- :1 (If you have more than one xserver running you might need to change the :1 to some higher number) True... But: The same using an unpatched xmonad works: $ cabal unpack xmonad $ cd xmonad-0.11 $ cabal build $ xinit $PWD/dist/build/xmonad/xmonad -- :1 So it must be one of our patches... Unfortunately, none of them look suspicious. Any ideas? Weird. 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#762296: Droid Sans Fallback refers to three different files
On 2014-09-21 09:52, Christian PERRIER wrote: As of now, we have: bubulle@sesostris:~/src/debian/pkg-fonts/git/fonts-android(master) $ more debian/fonts-droid.install Droid*.ttf usr/share/fonts/truetype/droid ... So basically : let's install all fonts whose name starts with Droid . How can we technically do All fonts whose name starts with 'Droid' but two of them Unless we, of course, list them all one by one They were listed previously. http://anonscm.debian.org/cgit/pkg-fonts/fonts-android.git/diff/?id=7d59819 Maybe something like this override_dh_install: dh_install rm path/DroidSansFallback.ttf || true rm path/DroidSansFallbackLegacy.ttf || true Would work too. On 2014-09-21 10:28, Jonas Smedegaard wrote: How about this instead: Droid*.ttf usr/share/fonts-droid/truetype That would put away all of them. Did you really mean that? ...and then register DroidSansFull.ttf with alternatives system, symlinking it into usr/share/fonts/truetype/droid/DroidSans.ttf That's over my head, but it would be fine with me if it works. However, I can't help suspecting that there is no real need to include DroidSansFallback.ttf and DroidSansFallbackLegacy.ttf. * Got the impression from https://bugs.debian.org/737105 that DroidSansFallbackFull.ttf is sufficient for Ghostscript too. * Is the reporter of https://bugs.debian.org/714436 of the opinion that DroidSansFallback.ttf displays Korean characters better than fonts-nanum, or was he just not aware of the possibility to install the latter to fix his issue? If I'm right, I suppose it would be preferable to not unnecessarily complicate the package. -- Gunnar Hjalmarsson https://launchpad.net/~gunnarhj -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#468929: Processed: jessie
Control: tag 468929 - sid jessie Hi Holger, Debian Bug Tracking System wrote: Processing commands for cont...@bugs.debian.org: tag 468929 + sid jessie Bug #468929 [libmail-cclient-perl] libmail-cclient-perl: test failures Added tag(s) sid and jessie. why do you think that this bug report does not apply to Wheezy? The initial bug report was filed back in March 2008 and I could confirm the findings from 2009 that it doesn't work at all. So I doubt that this package even works properly in Squeez -- which was released in February 2011. (But I haven't checked explicitly as it seems obvious to me.) Especially since we requested the removal of libmail-cclient-perl from Sid and Jessie due to this bug, it's IMHO even more important to make clear which bug reports still apply to Stable and Oldstable. Regards, Axel -- ,''`. | Axel Beckert a...@debian.org, http://people.debian.org/~abe/ : :' : | Debian Developer, ftp.ch.debian.org Admin `. `' | 1024D: F067 EA27 26B9 C3FC 1486 202E C09E 1D89 9593 0EDE `-| 4096R: 2517 B724 C5F6 CA99 5329 6E61 2FF9 CD59 6126 16B5 -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#760343: transition: protobuf 2.6.0
On 20/09/14 21:40, Robert Edmonds wrote: Jonathan Wiltshire wrote: On 2014-09-20 20:02, Robert Edmonds wrote: Robert Edmonds wrote: Emilio Pozuelo Monfort wrote: The delay ended but the signature seems invalid: 20140919160333|process-upload|dak|mapnik-vector-tile_0.5.1+dfsg-1.1_multi.changes|Error while loading changes: No valid signature found. (GPG exited with status code 512) Can you re-upload with a good signature (and without a delay of course). You may need to dcut the previous upload first. Funny :-) https://rt.debian.org/Ticket/Display.html?id=5305 My key was replaced in the mean-time. I'll reupload it with a new signature. Hmm, OK. I ran dcut on the previous upload and received: Log of processing your commands file /edmonds-1411144369.commands: cancel mapnik-vector-tile_0.5.1+dfsg-1.1_multi.changes No upload found: mapnik-vector-tile_0.5.1+dfsg-1.1_multi.changes cancel is for deferred uploads. You probably want: dcut rm -i changesfile (You need your original .changes file for this; if you don't have it any more, I think you're stuck with listing the individual files.) Do you mean dcut rm -f changesfile? The dcut I'm using (from dput-ng) doesn't have a dcut rm -i. I restored my original .changes file from backup. But I get: Log of processing your commands file /edmonds-1411241724.commands: rm --searchdirs mapnik-vector-tile_0.5.1+dfsg-1.1_all.deb mapnik-vector-tile_0.5.1+dfsg-1.1_all.deb did not match anything No files to delete rm --searchdirs mapnik-vector-tile_0.5.1+dfsg-1.1.dsc mapnik-vector-tile_0.5.1+dfsg-1.1.dsc did not match anything No files to delete rm --searchdirs mapnik-vector-tile_0.5.1+dfsg-1.1.debian.tar.xz mapnik-vector-tile_0.5.1+dfsg-1.1.debian.tar.xz did not match anything No files to delete rm --searchdirs mapnik-vector-tile_0.5.1+dfsg-1.1_multi.changes mapnik-vector-tile_0.5.1+dfsg-1.1_multi.changes did not match anything No files to delete Greetings, Your Debian queue daemon (running on host franck.debian.org) I'm still confused as to why the second upload of mapnik-vector-tile 0.5.1+dfsg-1.1 failed... You can ask on #debian-ftp if you are still having trouble with this. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#741036: [pkg-octave/master] Remove functions which are now in Octave core
tag 741036 pending thanks Date: Sun Sep 21 06:32:44 2014 -0300 Author: Rafael Laboissiere raf...@laboissiere.net Commit ID: 32f1b9c79aa774a51b7e0339d1330ed18d3b10bb Commit URL: http://anonscm.debian.org/gitweb/?p=pkg-octave/octave-specfun.git;a=commitdiff;h=32f1b9c79aa774a51b7e0339d1330ed18d3b10bb Patch URL: http://anonscm.debian.org/gitweb/?p=pkg-octave/octave-specfun.git;a=commitdiff_plain;h=32f1b9c79aa774a51b7e0339d1330ed18d3b10bb Remove functions which are now in Octave core Closes: #741036 -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#749264: No nvidia-driver working
On Sun, Sep 21, 2014 at 2:23 AM, Karsten Malcher deb...@home.decotrain.de wrote: Am 21.09.2014 11:08, schrieb Vincent Cheng: Hi Karsten, Fix your smtp server so that it stops timing out. The DSL was burned after a lightning bolt abd the server not reachable. So i installed # aptitude install nvidia-glx-legacy-173xx nvidia-kernel-dkms No, just install nvidia-glx-legacy-173xx (as suggested by nvidia-detect); its dependencies will ensure that you have a working nvidia 173.xx driver installed. Installing nvidia-kernel-dkms on wheezy will actually pull in the default 304.xx driver series, which is obviously not what you want. If you take a look at the log file you attached in your followup message... [42.428] (II) NVIDIA GLX Module 304.117 Tue Nov 26 21:45:09 PST 2013 [42.445] (WW) NVIDIA(0): The NVIDIA GeForce FX 5200 GPU installed in this system is [42.445] (WW) NVIDIA(0): supported through the NVIDIA 173.14.xx Legacy drivers. [42.445] (WW) NVIDIA(0): Please visit http://www.nvidia.com/object/unix.html for [42.445] (WW) NVIDIA(0): more information. The 304.117 NVIDIA driver will ignore [42.445] (WW) NVIDIA(0): this GPU. Continuing probe... [42.445] (EE) No devices detected. It's no surprise that X won't load, given that you're trying to use the nvidia 304.xx driver series with hardware that doesn't support it. O.K. - but why the 304.117 driver is installed when i install dkms? It would be better that there is a dependency that announces a conflict when i want to have a 173xx driver. Assuming you're just an uninformed user with no idea what dkms is and just want a working X server + nvidia driver...why would you care to install nvidia-kernel-dkms? All you would reasonably be expected to do is to run nvidia-detect and install whatever package it told you to install. Or if you were a new user with no knowledge of nvidia-detect, you would instead google for nvidia debian or similar, hit this wiki page [1] as your first search result, and then proceed to install the correct package. To answer your question, the nvidia binary packages that are unversioned refer to the current mainline driver packaged at the time; only the legacy packages get renamed. So e.g. currently in sid, nvidia-kernel-dkms will pull in the 340.xx series; if you wanted to install an older, legacy driver, e.g. the 304.xx series, install nvidia-legacy-304xx-kernel-dkms (or better yet, install the nvidia-legacy-304xx-driver metapackage and let it resolve dependencies for you). AFAIK this naming scheme was adopted to ensure that the different driver series are co-installable with one another (so that you could switch at runtime if desired, rather than having to uninstall/reinstall packages). As i have written nouveau failed because it does not support this hardware. But the nouveau driver from Knoppix is doing it. Probably because Knoppix is using a newer kernel? Experiments with new kernels in an stable working environment is causing more problems than solving it. Then you have X but you loose sound or some interface hardware ... File bug reports against the kernel for specific issues. Also, you seem to have no issues using Knoppix (which AFAIK packages newer kernels than what is typically found in Debian stable...). Regards, Vincent [1] https://wiki.debian.org/NvidiaGraphicsDrivers -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#755757: cecilia: Patch for wxPython 3.0
On 20/09/14 05:21, Olly Betts wrote: Control: tags 755757 + patch Dear maintainer, With the attached patch, the wx-related errors I originally got are gone, as is another sizer-related error I got after fixing those. Let me know if you're like me to NMU these changes. Did you send this to the wrong bug? -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#762162: gdb output
On Sat, 2014-09-20 at 18:44 +0800, Paul Wise wrote: Some debug symbols are missing, please install these packages and repeat: sudo apt-get install libjpeg8-dbg libgtk2.0-0-dbg libglib2.0-0-dbg gdb -batch -n -ex run -ex bt -ex 'thread apply all bt full' --args geeqie Below is the new output. // Matti K [Thread debugging using libthread_db enabled] Using host libthread_db library /lib/x86_64-linux-gnu/libthread_db.so.1. [New Thread 0x7fffe8af2700 (LWP 2036)] Program received signal SIGSEGV, Segmentation fault. append_escaped_text (length=optimized out, text=optimized out, str=0x99b340) at /tmp/buildd/glib2.0-2.41.5/./glib/gmarkup.c:2163 2163/tmp/buildd/glib2.0-2.41.5/./glib/gmarkup.c: No such file or directory. #0 append_escaped_text (length=optimized out, text=optimized out, str=0x99b340) at /tmp/buildd/glib2.0-2.41.5/./glib/gmarkup.c:2163 #1 g_markup_escape_text (text=optimized out, length=optimized out, length@entry=-1) at /tmp/buildd/glib2.0-2.41.5/./glib/gmarkup.c:2239 #2 0x779e0317 in gtk_widget_set_property (object=0x900080, prop_id=optimized out, value=0x7fffd870, pspec=optimized out) at /build/gtk+2.0-zztKf7/gtk+2.0-2.24.24/gtk/gtkwidget.c:2739 #3 0x76166bdb in object_set_property (nqueue=optimized out, value=optimized out, pspec=optimized out, object=optimized out) at /tmp/buildd/glib2.0-2.41.5/./gobject/gobject.c:1415 #4 g_object_set_valist (object=0x900080, first_property_name=0x771220 \240\064y, var_args=0x7fffd920) at /tmp/buildd/glib2.0-2.41.5/./gobject/gobject.c:2159 #5 0x7616746c in g_object_set (_object=0x900080, first_property_name=0x77a5be06 tooltip-text) at /tmp/buildd/glib2.0-2.41.5/./gobject/gobject.c:2269 #6 0x7798ccee in gtk_tool_item_sync_action_properties (activatable=0xa31990, action=0x7ede20) at /build/gtk+2.0-zztKf7/gtk +2.0-2.24.24/gtk/gtktoolitem.c:647 #7 0x7798b3ba in gtk_tool_button_sync_action_properties (activatable=0xa31990, action=0x7ede20) at /build/gtk+2.0-zztKf7/gtk +2.0-2.24.24/gtk/gtktoolbutton.c:865 #8 0x77983056 in gtk_toggle_tool_button_sync_action_properties (activatable=0xa31990, action=0x7ede20) at /build/gtk+2.0-zztKf7/gtk +2.0-2.24.24/gtk/gtktoggletoolbutton.c:347 #9 0x77810353 in IA__gtk_activatable_do_set_related_action (activatable=0xa31990, action=0x7ede20) at /build/gtk+2.0-zztKf7/gtk +2.0-2.24.24/gtk/gtkactivatable.c:471 #10 0x7798d154 in gtk_tool_item_set_related_action (action=0x7ede20, item=0xa31990) at /build/gtk+2.0-zztKf7/gtk +2.0-2.24.24/gtk/gtktoolitem.c:664 #11 gtk_tool_item_set_property (object=0xa31990, prop_id=optimized out, value=optimized out, pspec=optimized out) at /build/gtk +2.0-zztKf7/gtk+2.0-2.24.24/gtk/gtktoolitem.c:378 #12 0x76166bdb in object_set_property (nqueue=optimized out, value=optimized out, pspec=optimized out, object=optimized out) at /tmp/buildd/glib2.0-2.41.5/./gobject/gobject.c:1415 #13 g_object_set_valist (object=0xa31990, first_property_name=0x8710d0 \360\230t, var_args=0x7fffdbe0) at /tmp/buildd/glib2.0-2.41.5/./gobject/gobject.c:2159 #14 0x7616746c in g_object_set (_object=_object@entry=0xa31990, first_property_name=first_property_name@entry=0x77a4e3ca related-action) at /tmp/buildd/glib2.0-2.41.5/./gobject/gobject.c:2269 #15 0x7781018c in IA__gtk_activatable_set_related_action (activatable=activatable@entry=0xa31990, action=action@entry=0x7ede20) at /build/gtk+2.0-zztKf7/gtk+2.0-2.24.24/gtk/gtkactivatable.c:404 #16 0x7780c7cc in IA__gtk_action_create_tool_item (action=0x7ede20) at /build/gtk+2.0-zztKf7/gtk +2.0-2.24.24/gtk/gtkaction.c:939 #17 0x779ccdef in update_node (self=0x77a260, node=0x7fffe4009330, in_popup=0, popup_accels=0) at /build/gtk +2.0-zztKf7/gtk+2.0-2.24.24/gtk/gtkuimanager.c:2677 #18 0x779cbfc2 in update_node (self=0x77a260, node=0x854500, in_popup=0, popup_accels=0) at /build/gtk+2.0-zztKf7/gtk +2.0-2.24.24/gtk/gtkuimanager.c:2785 #19 0x779cbfc2 in update_node (self=0x77a260, node=0x807800, in_popup=0, popup_accels=0) at /build/gtk+2.0-zztKf7/gtk +2.0-2.24.24/gtk/gtkuimanager.c:2785 #20 0x779cf7af in do_updates (self=0x77a260) at /build/gtk +2.0-zztKf7/gtk+2.0-2.24.24/gtk/gtkuimanager.c:2827 #21 IA__gtk_ui_manager_ensure_update (self=self@entry=0x77a260) at /build/gtk+2.0-zztKf7/gtk+2.0-2.24.24/gtk/gtkuimanager.c:2882 #22 0x779cf811 in gtk_ui_manager_real_get_widget (self=0x77a260, path=0x4e37ad /MainMenu/FileMenu/OpenRecent) at /build/gtk +2.0-zztKf7/gtk+2.0-2.24.24/gtk/gtkuimanager.c:558 #23 0x0047120e in layout_menu_recent_update (lw=0x791c00) at layout_util.c:1214 #24 0x004a5c4f in end_element (context=0x77b650, element_name=0x77b770 layout, user_data=0x77a4b0, error=0x7fffdef0) at rcfile.c:1141 #25 0x75e8d267 in emit_end_element (context=0x77b650, error=0x0) at /tmp/buildd/glib2.0-2.41.5/./glib/gmarkup.c:1084 #26 0x75e8df3e in g_markup_parse_context_parse (context=0x77b650,
Bug#755757: cecilia: Patch for wxPython 3.0
On Sun, Sep 21, 2014 at 11:43:19AM +0200, Emilio Pozuelo Monfort wrote: On 20/09/14 05:21, Olly Betts wrote: Control: tags 755757 + patch Dear maintainer, With the attached patch, the wx-related errors I originally got are gone, as is another sizer-related error I got after fixing those. Let me know if you're like me to NMU these changes. Did you send this to the wrong bug? Sorry, yes - I realised almost right away and resent it though. Cheers, Olly -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#762186: python-pypdf: Unexpectedly breaks existing programs on update
Dear maintainer, On Thu, 18 Sep 2014 22:42:50 +0200 Elena Grandi valhall...@trueelena.org wrote: Package: python-pypdf Version: 1.23-1 Severity: grave Justification: renders package unusable Dear Maintainer, updating python-pypdf from 1.13 to 1.23 breaks every existing script that use this module with an ImportError: No module named pyPdf. Changing pyPdf to PyPDF2 everywhere in the scripts allows to use the new version, but in the update there was no hint that this change was needed. Expecially if this happens during an update between stable versions this will break existing deployments of custom programs, causing lots of pain. Worse still is the fact that currently in sid, both src:python-pypdf and src:pypdf2 build binary package python-pypdf. One of the above source packages must stop building python-pypdf, and since pypdf2 is the one that's breaking reverse dependencies, I would very much appreciate it this is initially done in src:pypdf2. The next time you package a fork as a new source package, please don't immediately hijack the other package's namespace, and give a heads up to maintainers of your library's reverse deps so that they have time to react. It'd be really nice if you could also coordinate an informal transition and offer patches/NMUs to fix up pypdf's reverse dependencies. Regards, Vincent -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#762186: [Python-modules-team] Bug#762186: python-pypdf: Unexpectedly breaks existing programs on update
On Sun, Sep 21, 2014 at 2:54 AM, Vincent Cheng vch...@debian.org wrote: Dear maintainer, On Thu, 18 Sep 2014 22:42:50 +0200 Elena Grandi valhall...@trueelena.org wrote: Package: python-pypdf Version: 1.23-1 Severity: grave Justification: renders package unusable Dear Maintainer, updating python-pypdf from 1.13 to 1.23 breaks every existing script that use this module with an ImportError: No module named pyPdf. Changing pyPdf to PyPDF2 everywhere in the scripts allows to use the new version, but in the update there was no hint that this change was needed. Expecially if this happens during an update between stable versions this will break existing deployments of custom programs, causing lots of pain. Worse still is the fact that currently in sid, both src:python-pypdf and src:pypdf2 build binary package python-pypdf. One of the above source packages must stop building python-pypdf, and since pypdf2 is the one that's breaking reverse dependencies, I would very much appreciate it this is initially done in src:pypdf2. The next time you package a fork as a new source package, please don't immediately hijack the other package's namespace, and give a heads up to maintainers of your library's reverse deps so that they have time to react. It'd be really nice if you could also coordinate an informal transition and offer patches/NMUs to fix up pypdf's reverse dependencies. Looks like the BTS is a bit confused over who the maintainer for src:pypdf2 is, so forwarding this directly to its maintainer. Regards, Vincent -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#468929: Processed: jessie
Hi Axel, thanks for cleaning up my mistakes! Much appreciated! :) On Sonntag, 21. September 2014, Axel Beckert wrote: why do you think that this bug report does not apply to Wheezy? I didnt mean to imply this. I tagged it + sid jessie to indicate the RC severity doesnt apply to wheezy. As the bug is now, it will show up on the radar of people fixing RC bugs in stable and I didnt think this test suite failure was RC in stable. Turns out I was wrong :) (But the above is still a general problem for similar cases...) The initial bug report was filed back in March 2008 and I could confirm the findings from 2009 that it doesn't work at all. So I doubt that this package even works properly in Squeez -- which was released in February 2011. (But I haven't checked explicitly as it seems obvious to me.) Especially since we requested the removal of libmail-cclient-perl from Sid and Jessie due to this bug, it's IMHO even more important to make clear which bug reports still apply to Stable and Oldstable. if the package really doesnt work in stable (and oldstable) at all, it should either be fixed there, or also removed. cheers, Holger signature.asc Description: This is a digitally signed message part.
Bug#759557: RFS: asic0x/1.0.1-1 [ITP] -- iBurst USB modem driver in DKMS format
Hi Eriberto Thanks for taking the time to review my package. On 21 September 2014 06:11, Eriberto Mota eribe...@debian.org wrote: 1. d/control: in asic0x-dkms (binary), add dkms as dependency. This is already taken care of by substvars: misc:Depends=dkms (= 2.1.0.0) 2. d/copyright: use the GPL-2+ license text provided by Debian templates. You can find it here: /usr/share/debhelper/dh_make/licenses/gpl2. Updated, thanks. 3. d/rules: remove the comment line started with 'Uncomment...'. I removed this line and the 'export DH_VERBOSE=1' line. 4. Please, upload your final package to mentors.debian.net. Uploaded: http://mentors.debian.net/package/asic0x Regards Graham -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#761195:
This seems fixed Upstream. See this commit: https://git.gnome.org/browse/libgweather/commit/?id=77c4dbc22cd09a5151e5bfbfcc29bf7747126294 Leo. -- Ubuntu Member - http://launchpad.net/~l3on Home Page - http://leoiannacone.com GPG Key Id - 0xD282FC25 -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#762312: does not work with systemd
Hi Sven, On 09/21/2014 03:42 AM, Sven Hartge wrote: Package: needrestart Version: 1.1-1 Severity: normal Hi! I noticed needrestart seems to do nothing with systemd as PID1. needrestart should work with systemd... could you please provide the (full) output of: - needrestart -vr l - systemctl status `pidof smokeping` --- [main] RC: * ddclient.service [main] RC: * smokeping.service --- Very strange, where do those additional * come from? If needrestart detects systemd it uses systemctl status to get the service name to be used to restart a daemon. This might break if the output of `systemctl status` would differ somewho. Thanks, Thomas Which then results into the following command: systemctl restart * ddclient.service * smokeping.service While running this at the normal command prompt works (kind of, you get tons of errors because the shell expands the *) it does not work when executed by needrestart. Grüße, Sven. -- System Information: Debian Release: jessie/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing'), (200, 'experimental') Architecture: i386 (x86_64) Foreign Architectures: amd64 Kernel: Linux 3.16-1-amd64 (SMP w/4 CPU cores) Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages needrestart depends on: ii dpkg 1.17.13 ii libmodule-find-perl 0.12-1 ii libmodule-scandeps-perl 1.15-1 ii libproc-processtable-perl0.50-2+b1 ii libsort-naturally-perl 1.03-1 ii libterm-progressbar-simple-perl 0.03-1 ii perl 5.20.1-1 needrestart recommends no packages. needrestart suggests no packages. -- :: WWW: http://fiasko-nw.net/~thomas/ :: ::: Jabber: xmpp:tho...@jabber.fiasko-nw.net ::: :: flickr: http://www.flickr.com/photos/laugufe/ :: -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#762337: libgtk-3-0: Ticks in checkboxes are not shown anymore
Package: libgtk-3-0 Version: 3.13.9-2 Severity: normal -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Dear Maintainer, checkboxes in audacious under Preferences/Plugins are not shown correctly anymore with libgtk-3-0 3.13.9-2. The ticks, when a chackbox is toggled, are not shown anymore. Furthermore, the progressbar, which one gets, if one hovers over the status icon, that shows, how much time of the current track has past, is not shown correctly anymore. With best regards, Julian Wollrath P.S.: Please do not get confused by that below 3.12.2-3 is reported as the installed package version for the libgtk-3* packages, I already downgraded the libgtk-3* packages to the version in testing. P.P.S.: For what it's worth, i am using gtk3-engines-oxygen as theme. - -- System Information: Debian Release: jessie/sid APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.17.0-rc5 (SMP w/4 CPU cores) Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages libgtk-3-0 depends on: ii libatk-bridge2.0-0 2.12.1-1+b1 ii libatk1.0-0 2.12.0-1 ii libc62.19-11 ii libcairo-gobject21.12.16-5 ii libcairo21.12.16-5 ii libcolord2 1.2.1-1 ii libcups2 1.7.5-2 ii libfontconfig1 2.11.0-6.1 ii libfreetype6 2.5.2-2 ii libgdk-pixbuf2.0-0 2.30.8-1 ii libglib2.0-0 2.41.5-2 ii libgtk-3-common 3.12.2-3 ii libjson-glib-1.0-0 1.0.2-1 ii libpango-1.0-0 1.36.7-1 ii libpangocairo-1.0-0 1.36.7-1 ii libpangoft2-1.0-01.36.7-1 ii librest-0.7-00.7.92-1 ii libsoup2.4-1 2.46.0-3 ii libwayland-client0 1.6.0-1 ii libwayland-cursor0 1.6.0-1 ii libx11-6 2:1.6.2-3 ii libxcomposite1 1:0.4.4-1 ii libxcursor1 1:1.1.14-1 ii libxdamage1 1:1.1.4-2 ii libxext6 2:1.3.2-1 ii libxfixes3 1:5.0.1-2 ii libxi6 2:1.7.4-1 ii libxinerama1 2:1.1.3-1 ii libxkbcommon00.4.3-2 ii libxml2 2.9.1+dfsg1-4 ii libxrandr2 2:1.4.2-1 ii multiarch-support2.19-11 ii shared-mime-info 1.3-1 Versions of packages libgtk-3-0 recommends: ii hicolor-icon-theme 0.13-1 ii libgtk-3-bin3.12.2-3+b1 Versions of packages libgtk-3-0 suggests: pn gvfs none ii librsvg2-common 2.40.4-1 - -- no debconf information -BEGIN PGP SIGNATURE- Version: GnuPG v1 iQEcBAEBCAAGBQJUHqOPAAoJEFl2dmpRMS8zYvEH/1DpCbNwoPR3Z7eIC7b3Dhvw jlEhA3D18SmVEvqQtNxxsIWjTSRL3tAFaR9dcvwqPYcDBH4cKD8NXQqD0EbGTvr6 z0S93Ka6SifXgiBclMr7JOk2isIVAn97po+qGqY2K48OvbDXGYHLuF7BkRbJQbcz OkFGmfPZ0Qu6A8TZ0BzqDgQQUFEV2NGOpyNI0PBAbZwtRVLBL9DtQbYvfk03HBbl 7/gS5HApXOYzFm4ZJQl5CKGAL3Df8saDmADJYUZfKtB+o2ued1GQAoSa2n+fEvef WycmCZGBsRWjBPpCbLa0z3N1VpObMbnop/RtkoUDU7B3GAZuIGuNe8IrnYO8iyY= =3u2M -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#750255: lio-utils: FTBFS: chmod: cannot access '/«BUILDDIR»/lio-utils-3.1+git2.fd0b34fd/debian/lio-utils/usr/share/pyshared/*.py': No such file or directory
Hi, * Jerome Martin [Sat Sep 20, 2014 at 07:57:47PM +0200]: On 09/20/2014 01:24 PM, Ritesh Raj Sarraf wrote: On Saturday 20 September 2014 02:58 PM, Ritesh Raj Sarraf wrote: I just pushed configshel 1.5 into experimental. Next in line is rtslib and targetcli (both from git tip). Once all are in experimental, and we have some test results, I'll push it to unstable. Okay!! All of the new components of LIO, i.e. configshell, rtslib and targetcli are now in Debian experimental. Now the quality of these packages depend on user testing and bug reports. Great, thanks for that. Michael: Since you (and others on this bug report) have interest in LIO, I'd request if you folks can give the version in experimental a test. At this time, I do not have the resources to test an LIO stack. I could use (read desperately require :-) ) tests and reports myself, so please guys, I will be working on the upstream code next week, now is a good time to fill my inbox with reports :-) Kernel version is always one critical piece of information for testing, so please remember to include it! Sure, I'll test my use-cases ASAP and will report back for sure. Thanks for your work, highly appreciated. regards, -mika- signature.asc Description: Digital signature
Bug#760720: qrouter review
Hi, I don't have any problems with qrouter and tkcon2.7, but magic does not seem to like 2.7. And the second issue you mention is not really relevant for the debian package. So it shold be fine as it is now - letting it use the tkcon version available in debian. Then, Harlan, I think the package is ready to be reviewed again! :) Regards, Ruben 2014-09-21 3:51 GMT+02:00 Tim Edwards t...@opencircuitdesign.com: Hello Ruben, After a closer look, it seems like the version bundled with qrouter and magic is just an older version of tkcon.tcl (2.3). I don't see why it would not work completely fine also with the newest version of tkcon. I've tried qrouter with tkcon 2.7 and I don't see any problems (maybe Tim knows more?) Interesting. After years of nobody mentioning it, I get two requests to update tkcon.tcl within a few days. Just note several things: 1) tkcon.tcl was broken by Tcl version 2.6 and would not scroll through the history. This is probably fixed, but it's best to check. There's a patch for it floating around, if needed. 2) I used a slightly modified tkcon.tcl, in which at the top I changed wish to $(QROUTER_WISH:=wish) (or something like that). This is to make sure that qrouter runs the version of wish that it was compiled for. This could also be done in the launching shell script, to make sure wish is aliased to the correct executable. That would be preferred, as it prevents having a modified version of tkcon.tcl. ---Tim -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#468929: Processed: jessie
Control: retitle -1 libmail-cclient-perl: Fails to open any mailbox Hi Holger, Holger Levsen wrote: On Sonntag, 21. September 2014, Axel Beckert wrote: why do you think that this bug report does not apply to Wheezy? I didnt mean to imply this. I tagged it + sid jessie to indicate the RC severity doesnt apply to wheezy. As the bug is now, it will show up on the radar of people fixing RC bugs in stable and I didnt think this test suite failure was RC in stable. Turns out I was wrong :) Well, yeah, but I must admit the bug title was misleading with regards to the new findings from 2009. So I see now why you thought that bug doesn't apply to older releases. I've fixed that now. :-) Especially since we requested the removal of libmail-cclient-perl from Sid and Jessie due to this bug, it's IMHO even more important to make clear which bug reports still apply to Stable and Oldstable. if the package really doesnt work in stable (and oldstable) at all, it should either be fixed there, or also removed. Yes, I was thinking about that, too. So far I have no idea what actually causes the breakage. Maybe some subtle ABI change in libc-client? Regards, Axel -- ,''`. | Axel Beckert a...@debian.org, http://people.debian.org/~abe/ : :' : | Debian Developer, ftp.ch.debian.org Admin `. `' | 1024D: F067 EA27 26B9 C3FC 1486 202E C09E 1D89 9593 0EDE `-| 4096R: 2517 B724 C5F6 CA99 5329 6E61 2FF9 CD59 6126 16B5 -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#744785: closed by Ryan Kavanagh r...@debian.org (Bug#744785: fixed in freetuxtv 0.6.6~dfsg1-1)
On 09/10/2014 08:21 AM, Debian Bug Tracking System wrote: This is an automatic notification regarding your Bug report which was filed against the freetuxtv package: #744785: freetuxtv: fails to build with clang instead of gcc It has been closed by Ryan Kavanagh r...@debian.org. Their explanation is attached below along with your original report. If this explanation is unsatisfactory and you have not received a better one in a separate message then please contact Ryan Kavanagh r...@debian.org by replying to this email. Hello, It seems a line of the patch was not integrated into this new version. The new version fails to build here: gtk-libvlc-media-player.c:1822:2: error: non-void function 'gtk_libvlc_media_player_get_state' should return a value [-Wreturn-type] g_return_if_fail(priv-initialized == TRUE); This line should call g_return_val_if_fail(). New build log is here: https://github.com/nonas/debian-clang/blob/master/buildlogs/freetuxtv/freetuxtv_0.6.6~dfsg1-1_amd64-20140921-1204.build Regards, Nicolas -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#762338: Generated PDF has tiny font size
Package: cups-pdf Version: 2.6.1-12 Severity: normal On a new Sid installation (Ghostscript 9.06~dfsg-1, but same problem with 9.15~rc1~dfsg-1 from experimental), the command echo bla | lp -d PDF produces the attached PDF, which contains text with the tiniest possible font size. The cupsd debug log of the job is attached. -- System Information: Debian Release: jessie/sid APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.16-1-amd64 (SMP w/4 CPU cores) Locale: LANG=en_NZ, LC_CTYPE=en_NZ.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages cups-pdf depends on: ii printer-driver-cups-pdf 2.6.1-12 cups-pdf recommends no packages. cups-pdf suggests no packages. -- no debconf information -- .''`. martin f. krafft madduck@d.o @martinkrafft : :' : proud Debian developer `. `'` http://people.debian.org/~madduck `- Debian - when you have better things to do than fixing systems _stdin_.pdf Description: Adobe PDF document I [21/Sep/2014:12:17:20 +0200] Listening to [v1.::1]:631 (IPv6) I [21/Sep/2014:12:17:20 +0200] Listening to 127.0.0.1:631 (IPv4) I [21/Sep/2014:12:17:20 +0200] Listening to /var/run/cups/cups.sock (Domain) I [21/Sep/2014:12:17:20 +0200] Remote access is disabled. D [21/Sep/2014:12:17:20 +0200] Added auto ServerAlias fishbowl I [21/Sep/2014:12:17:20 +0200] Loaded configuration file /etc/cups/cupsd.conf I [21/Sep/2014:12:17:20 +0200] Using default TempDir of /var/spool/cups/tmp... I [21/Sep/2014:12:17:20 +0200] Configured for up to 100 clients. I [21/Sep/2014:12:17:20 +0200] Allowing up to 100 client connections per host. I [21/Sep/2014:12:17:20 +0200] Using policy default as the default. I [21/Sep/2014:12:17:20 +0200] Full reload is required. I [21/Sep/2014:12:17:20 +0200] Loaded MIME database from /usr/share/cups/mime and /etc/cups: 39 types, 53 filters... D [21/Sep/2014:12:17:20 +0200] Loading printer hplj3052... D [21/Sep/2014:12:17:20 +0200] cupsdMarkDirty(P) D [21/Sep/2014:12:17:20 +0200] cupsdSetBusyState: newbusy=Dirty files, busy=Not busy D [21/Sep/2014:12:17:20 +0200] load_ppd: Loading /etc/cups/ppd/hplj3052.ppd... D [21/Sep/2014:12:17:20 +0200] cupsdRegisterPrinter(p=0x7fafe54dbf50(hplj3052)) D [21/Sep/2014:12:17:20 +0200] Loading printer PDF... D [21/Sep/2014:12:17:20 +0200] load_ppd: Loading /var/cache/cups/PDF.data... D [21/Sep/2014:12:17:20 +0200] cupsdRegisterPrinter(p=0x7fafe54e0060(PDF)) I [21/Sep/2014:12:17:20 +0200] Loading job cache file /var/cache/cups/job.cache... D [21/Sep/2014:12:17:20 +0200] [Job 1] Loading from cache... D [21/Sep/2014:12:17:20 +0200] [Job 5] Loading from cache... D [21/Sep/2014:12:17:20 +0200] [Job 7] Loading from cache... D [21/Sep/2014:12:17:20 +0200] [Job 8] Loading from cache... D [21/Sep/2014:12:17:20 +0200] [Job 12] Loading from cache... D [21/Sep/2014:12:17:20 +0200] [Job 14] Loading from cache... D [21/Sep/2014:12:17:20 +0200] [Job 15] Loading from cache... D [21/Sep/2014:12:17:20 +0200] [Job 16] Loading from cache... D [21/Sep/2014:12:17:20 +0200] [Job 17] Loading from cache... D [21/Sep/2014:12:17:20 +0200] [Job 18] Loading from cache... D [21/Sep/2014:12:17:20 +0200] [Job 19] Loading from cache... D [21/Sep/2014:12:17:20 +0200] [Job 20] Loading from cache... D [21/Sep/2014:12:17:20 +0200] [Job 21] Loading from cache... D [21/Sep/2014:12:17:20 +0200] [Job 22] Loading from cache... D [21/Sep/2014:12:17:20 +0200] [Job 23] Loading from cache... D [21/Sep/2014:12:17:20 +0200] [Job 24] Loading from cache... I [21/Sep/2014:12:17:20 +0200] Full reload complete. D [21/Sep/2014:12:17:20 +0200] cupsdCleanFiles(path=/var/spool/cups/tmp, pattern=(null)) I [21/Sep/2014:12:17:20 +0200] Cleaning out old files in /var/spool/cups/tmp. D [21/Sep/2014:12:17:20 +0200] cupsdCleanFiles(path=/var/cache/cups, pattern=*.ipp) I [21/Sep/2014:12:17:20 +0200] Cleaning out old files in /var/cache/cups. D [21/Sep/2014:12:17:20 +0200] systemd_checkin: Matched existing listener /var/run/cups/cups.sock with fd 3... D [21/Sep/2014:12:17:20 +0200] systemd_checkin: Matched existing listener 127.0.0.1 with fd 4... D [21/Sep/2014:12:17:20 +0200] systemd_checkin: Matched existing listener [v1.::1] with fd 5... D [21/Sep/2014:12:17:20 +0200] systemd_checkin: Activate exit-on-idle mode, timeout: 30 seconds. D [21/Sep/2014:12:17:20 +0200] Calling FindDeviceById(cups-hplj3052) D [21/Sep/2014:12:17:20 +0200] FindDeviceById failed: org.freedesktop.DBus.Error.ServiceUnknown:The name org.freedesktop.ColorManager was not provided by any .service files D [21/Sep/2014:12:17:20 +0200] Calling FindDeviceById(cups-PDF) D [21/Sep/2014:12:17:20 +0200] FindDeviceById failed: org.freedesktop.DBus.Error.ServiceUnknown:The name org.freedesktop.ColorManager was not provided by any .service files D [21/Sep/2014:12:17:20 +0200] Using profile ID PDF-Gray... D [21/Sep/2014:12:17:20 +0200] Calling CreateProfile(PDF-Gray..,temp) W
Bug#750080: Forwarding this to upstream
Hi, Am Sonntag, den 21.09.2014, 11:33 +0200 schrieb Joachim Breitner: To reproduce this you don't need to log out. Just switch to a tty and run: $ xinit xmonad -- :1 (If you have more than one xserver running you might need to change the :1 to some higher number) True... But: The same using an unpatched xmonad works: $ cabal unpack xmonad $ cd xmonad-0.11 $ cabal build $ xinit $PWD/dist/build/xmonad/xmonad -- :1 More information: Without ./xmonad/, xmonad starts properly in both cases: You can e.g. fire up a terminal with Shift-Alt-Enter. But the system-wide installed xmonad will display the execution error using xmessage, while the cabal-installed xmonad will print the same error on stderr (visible if you use xinit to start it). This is weird, as xmessage is (as far as I can tell from the code) only used when compilation fails, not when executing the xmonad binary. All very strange; anyone interested in digging deeper? 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#752116: RFS: drmips/1.2.2-1 [ITP]
Thank you Eriberto for your extensive feedback! (and I thought my package was reasonably good! :) ) Thank you Peter for your comment as well. I was going to answer only after I had uploaded a new package. Hmm, this is an interesting point. The education section was added by the FTP Masters back in 2012, and grep-dctrl -FSection education seems to show me at least 128 binary packages matching that (e.g. gcompris, kanadic, scratch, etc). See the list of sections in Debian Policy 2.4; it seems that the webpage needs to be updated. I also thought 'education' was a valid section: lintian doesn't complain, Synaptic shows a friendly name translated to my language for that section, vim doesn't mark it in red, and Ubuntu has some packages in that section. And the Debian Policy mentions that section indeed. Should I leave it in 'education', or should I change it? Maybe to 'java', or 'electronics' which is also a good choice. It's probably better to change. - I think that Vsc-Git should be 'https://bitbucket.org/brunonova/drmips -n debian'. Hm, I think you mean -b debian here :) Yes, you are right. The 'b' is near of the 'n' in keyboard. A typo. Thanks! Something seemed wrong to me here as well :). But I didn't know the argument for this field was the argument for 'git clone' (I thought it had to be a URL). - In long description, what is FEUP? Where (country) is FEUP? FEUP means Faculty of Engineering of the University of Porto, and it's in Portugal. I'll add it to the description. 3. d/copyright: - You must list all authors and licenses in thos file. Use the command 'egrep -sriA25 '(public domain|copyright)' *' to help you. I was missing the copyrights for the files in cmake/Modules/, and I think that's all. By authors you mean the names/emails of the people/companies that appear in the copyright notices of the source files, right? The copyright of cmake/Modules/UseLATEX.cmake caused me some confusion, though. But I found a package in Ubuntu (feel++) that uses that file, so it should be ok. - From Debian policy[2]: Packages distributed under the Apache license (version 2.0), the Artistic license, the GNU GPL (versions 1, 2, or 3), the GNU LGPL (versions 2, 2.1, or 3), and the GNU FDL (versions 1.2 or 1.3) should refer to the corresponding files under /usr/share/common-licenses,[ 119] rather than quoting them in the copyright file. - I suggest you to use the conventional license texts provided by Debian, when applicable. These text are available at /usr/share/debhelper/dh_make/licenses/. But the template texts there for those licenses also include a short summary of the licenses, before the pointer to the full text. Should I remove that and put only the pointer? 5.d/links: I didn't understand your intend with this file. The package installs some PDF manuals to /usr/share/drmips/doc/, and the program searches for them in that place (using a relative path). The link is just so the manuals are also accessible from /usr/share/doc/, the usual place in Linux for documentation. Should I remove the link? Some additional questions: * Should the Priority in debian/control be 'optional' or 'extra'? * Should the urgency in debian/changelog be 'low' or 'medium'? (the default was changed recently, I think) -- Bruno Nova
Bug#746927: pu: net-snmp/5.4.3~dfsg-2.8+deb7u1 (Bug#721224 snmpd: produces error if the Executables/scripts entries in snmpd.conf is over 50)
On Sat, 20 Sep 2014 18:09:50 +0100
Adam D. Barratt a...@adam-barratt.org.uk wrote:
Control: tags -1 + confirmed
On Sun, 2014-05-04 at 10:44 +0900, Hideki Yamane wrote:
I'd like to upload net-snmp/5.4.3~dfsg-2.8+deb7u1 to
stable-proposed-updates
to fix Bug#721224, error happens when Executables/scripts entries is over
50
in snmpd.conf.
Apologies for the delay in getting back to you. Please go ahead.
Thanks!
And I want to push more changes with three CVE fixes for
net-snmp/5.4.3~dfsg-2.8+deb7u1
Is it possible? debdiff is attached below.
diff -Nru net-snmp-5.4.3~dfsg/debian/changelog
net-snmp-5.4.3~dfsg/debian/changelog
--- net-snmp-5.4.3~dfsg/debian/changelog2014-03-18 05:02:49.0
+0900
+++ net-snmp-5.4.3~dfsg/debian/changelog2014-09-21 19:32:08.0
+0900
@@ -1,3 +1,18 @@
+net-snmp (5.4.3~dfsg-2.8+deb7u1) stable-proposed-updates; urgency=medium
+
+ * debian/patches
+- add bug#721224_entries_over50.patch to fix snmpd: produces error if the
+ Executables/scripts entries in snmpd.conf is over 50 taken patch from
+ Red Hat Bugzilla.
+ Thanks to Christian Ruppert c.rupp...@babiel.com for the report
+ (Closes: #721224)
+- add TrapReceiver.patch to fix CVE-2014-2285
+- add CVE-2014-3565.patch taken from upstream to fix CVE-2014-3565
+ (Closes: #760132)
+- add CVE-2012-6151.patch taken from Fedora to fix CVE-2012-6151
+
+ -- Hideki Yamane henr...@debian.org Tue, 16 Sep 2014 00:27:07 +0900
+
net-snmp (5.4.3~dfsg-2.8) stable; urgency=medium
* Non-maintainer upload.
diff -Nru net-snmp-5.4.3~dfsg/debian/patches/CVE-2012-6151.patch
net-snmp-5.4.3~dfsg/debian/patches/CVE-2012-6151.patch
--- net-snmp-5.4.3~dfsg/debian/patches/CVE-2012-6151.patch 1970-01-01
09:00:00.0 +0900
+++ net-snmp-5.4.3~dfsg/debian/patches/CVE-2012-6151.patch 2014-09-21
19:32:08.0 +0900
@@ -0,0 +1,46 @@
+Index: pkg-net-snmp/agent/mibgroup/agentx/master.c
+===
+--- pkg-net-snmp.orig/agent/mibgroup/agentx/master.c 2014-09-21
19:07:43.820073097 +0900
pkg-net-snmp/agent/mibgroup/agentx/master.c2014-09-21
19:27:42.611687481 +0900
+@@ -236,6 +236,9 @@
+ if (!cache) {
+ DEBUGMSGTL((agentx/master, response too late on session %08p\n,
+ session));
++/* response is too late, free the cache */
++if (magic)
++netsnmp_free_delegated_cache((netsnmp_delegated_cache*) magic);
+ return 0;
+ }
+ requests = cache-requests;
+@@ -621,6 +624,8 @@
+
+ if (result == 0 ) {
+ snmp_free_pdu( pdu );
++if (cb_data)
++netsnmp_free_delegated_cache((netsnmp_delegated_cache*) cb_data);
+ }
+
+ return SNMP_ERR_NOERROR;
+Index: pkg-net-snmp/agent/mibgroup/agentx/master_admin.c
+===
+--- pkg-net-snmp.orig/agent/mibgroup/agentx/master_admin.c 2014-09-21
19:07:43.820073097 +0900
pkg-net-snmp/agent/mibgroup/agentx/master_admin.c 2014-09-21
19:11:08.660690270 +0900
+@@ -139,11 +139,16 @@
+ * requests, so that the delegated request will be completed and
+ * further requests can be processed
+ */
+-netsnmp_remove_delegated_requests_for_session(session);
++ while (netsnmp_remove_delegated_requests_for_session(session)) {
++ DEBUGMSGTL((agentx/master, Continue removing delegated
reqests\n));
++ }
++
+ if (session-subsession != NULL) {
+ netsnmp_session *subsession = session-subsession;
+ for(; subsession; subsession = subsession-next) {
+-netsnmp_remove_delegated_requests_for_session(subsession);
++while
(netsnmp_remove_delegated_requests_for_session(subsession)) {
++ DEBUGMSGTL((agentx/master, Continue removing
delegated subsession reqests\n));
++ }
+ }
+ }
+
diff -Nru net-snmp-5.4.3~dfsg/debian/patches/CVE-2014-3565.patch
net-snmp-5.4.3~dfsg/debian/patches/CVE-2014-3565.patch
--- net-snmp-5.4.3~dfsg/debian/patches/CVE-2014-3565.patch 1970-01-01
09:00:00.0 +0900
+++ net-snmp-5.4.3~dfsg/debian/patches/CVE-2014-3565.patch 2014-09-21
19:32:08.0 +0900
@@ -0,0 +1,431 @@
+Index: pkg-net-snmp/snmplib/mib.c
+===
+--- pkg-net-snmp.orig/snmplib/mib.c2014-09-16 00:32:14.887917977 +0900
pkg-net-snmp/snmplib/mib.c 2014-09-16 00:32:14.883917965 +0900
+@@ -436,17 +436,16 @@
+ u_char *cp;
+ int output_format, len_needed;
+
+-if ((var-type != ASN_OCTET_STR)
+-(!netsnmp_ds_get_boolean(NETSNMP_DS_LIBRARY_ID,
NETSNMP_DS_LIB_QUICKE_PRINT))) {
+-const char str[] = Wrong Type (should be OCTET STRING): ;
+-if (snmp_cstrcat
+-(buf, buf_len,
Bug#746927: pu: net-snmp/5.4.3~dfsg-2.8+deb7u1 (Bug#721224 snmpd: produces error if the Executables/scripts entries in snmpd.conf is over 50)
On Sun, 2014-09-21 at 19:37 +0900, Hideki Yamane wrote: On Sat, 20 Sep 2014 18:09:50 +0100 Adam D. Barratt a...@adam-barratt.org.uk wrote: Control: tags -1 + confirmed On Sun, 2014-05-04 at 10:44 +0900, Hideki Yamane wrote: I'd like to upload net-snmp/5.4.3~dfsg-2.8+deb7u1 to stable-proposed-updates to fix Bug#721224, error happens when Executables/scripts entries is over 50 in snmpd.conf. Apologies for the delay in getting back to you. Please go ahead. Thanks! And I want to push more changes with three CVE fixes for net-snmp/5.4.3~dfsg-2.8+deb7u1 Yes, that looks okay. Regards, Adam -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#762339: uaccess creates stray empty group ACL overriting regular group permissions
Package: udev, libacl1 Version: 208-8 Severity: important This is a generic problem, but I'll use just one example of its action, on /dev/kvm device node. In short, on any kvm (svm|vmx) capable x86 system these days, kvm module gets loaded and /dev/kvm device node is created. But without udev rules file from qemu-kvm which assigns group permissions to this node, and with presence of systemd, this device node receives wrong ACL, like this: # ls -l /dev/kvm; getfacl /dev/kvm crw-rw+ 1 root root 10, 232 сен 21 18:45 /dev/kvm # file: dev/kvm # owner: root # group: root user::rw- user:Debian-gdm:rw- group::--- mask::rw- other::--- Note that even if the regular unix permissions have rw for group, there's one more ACL present for the file, group::---, which effectively turns off regular unix group permissions. /dev/kvm is listed in 70-uaccess.rules: SUBSYSTEM==misc, KERNEL==kvm, TAG+=uaccess but this is one of very few devices which comes without group rw permissions from the kernel initially. The problematic place is the systemd sources, src/login/logind-acl.c, devnode_acl() function. I added some debug printfs to this function, after each section of this function printing acl and stat(2) info from the file, and got this for /dev/kvm: initial: user::rw-,group::---,other::--- (mode=020600 uid=0 gid=0) after flush: user::rw-,group::---,other::--- (mode=020600) after add: user::rw-,user:Debian-gdm:rw-,group::---,other::--- (mode=020600) after mask: user::rw-,user:Debian-gdm:rw-,group::---,mask::rw-,other::--- (mode=020600) after final set: user::rw-,user:Debian-gdm:rw-,group::---,mask::rw-,other::--- (mode=020660) Note that after the final acl_set_file(), regular unix perms are changed too (which probably should not), but the stray empty group ACL entry is kept. Now the more I think about this, the more this looks like libacl bug... Hopefully not kernel :) Thanks, /mjt -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#759557: RFS: asic0x/1.0.1-1 [ITP] -- iBurst USB modem driver in DKMS format
Hi Graham, Uploaded. Thanks a lot for your (very good) work. Cheers, Eriberto 2014-09-21 7:04 GMT-03:00 Graham Inggs gra...@nerve.org.za: Hi Eriberto Thanks for taking the time to review my package. On 21 September 2014 06:11, Eriberto Mota eribe...@debian.org wrote: 1. d/control: in asic0x-dkms (binary), add dkms as dependency. This is already taken care of by substvars: misc:Depends=dkms (= 2.1.0.0) 2. d/copyright: use the GPL-2+ license text provided by Debian templates. You can find it here: /usr/share/debhelper/dh_make/licenses/gpl2. Updated, thanks. 3. d/rules: remove the comment line started with 'Uncomment...'. I removed this line and the 'export DH_VERBOSE=1' line. 4. Please, upload your final package to mentors.debian.net. Uploaded: http://mentors.debian.net/package/asic0x Regards Graham -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#746927: pu: net-snmp/5.4.3~dfsg-2.8+deb7u1 (Bug#721224 snmpd: produces error if the Executables/scripts entries in snmpd.conf is over 50)
On Sun, 21 Sep 2014 11:42:34 +0100 Adam D. Barratt a...@adam-barratt.org.uk wrote: And I want to push more changes with three CVE fixes for net-snmp/5.4.3~dfsg-2.8+deb7u1 Yes, that looks okay. Thanks again, uploaded. -- Regards, Hideki Yamane henrich @ debian.or.jp/org http://wiki.debian.org/HidekiYamane -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#719255: ping re: gnunet: New upstream version 0.10.1
unblock 719255 by 758937 Hi, now that #758937 has a patch which allows building of gnunet 0.10.1, I believe it's high time to get gnunet 0.10.1 in jessie before it freezes...! Bertrand, what's your stance on this? cheers, Holger signature.asc Description: This is a digitally signed message part.
Bug#762340: aptitude: [INTL:de] partially updated German man page translation
Package: aptitude Version: 0.6.10 Severity: wishlist Tags: patch l10n X-Debbugs-CC: Mario Blättermann mario.blaetterm...@gmail.com Please find the partial updated German man page translation for aptitude at http://www.helgefjell.de/data/aptitude_0.6.10-1_de.po.bz2 If you update your template, please use 'msgfmt --statistics pofile.po' to check the po-files for fuzzy or untranslated strings. Greetings Helge ~ -- 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#759583: Acknowledgement (dolphin: Context menu and keyboard shortcuts don't work after KDE-session restore)
Hi, the update of dolphin to version 4:4.14.1-1 seems to have solved the problem. The bug can be closed. regards Günter -- --- Günter Frenz Börschgasse 16a, D-51143 Köln (h) gu...@freenet.de, gu...@guefz.de (w) f...@gso-koeln.de --- signature.asc Description: PGP signature
Bug#762272: doxygen: segfaults when building efl (on ix86 amd amd64)
On 2014-09-20 Helmut Grohne hel...@subdivi.de wrote: [...] Andreas, could you add a debian/rules target to efl that allows just building the documentation? I'd like to add efl as a autopkgtest case to doxygen to spot this kind of issue earlier. Hello, I have not commit access for efl, however doesn't debian/rules build-indep already do the trick? cu Andreas -- `What a good friend you are to him, Dr. Maturin. His other friends are so grateful to you.' `I sew his ears on from time to time, sure' -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#762296: [Pkg-fonts-devel] Bug#762296: Droid Sans Fallback refers to three different files
Quoting Gunnar Hjalmarsson (2014-09-21 11:39:45) On 2014-09-21 09:52, Christian PERRIER wrote: As of now, we have: bubulle@sesostris:~/src/debian/pkg-fonts/git/fonts-android(master) $ more debian/fonts-droid.install Droid*.ttf usr/share/fonts/truetype/droid ... So basically : let's install all fonts whose name starts with Droid . How can we technically do All fonts whose name starts with 'Droid' but two of them Unless we, of course, list them all one by one They were listed previously. http://anonscm.debian.org/cgit/pkg-fonts/fonts-android.git/diff/?id=7d59819 Maybe something like this override_dh_install: dh_install rm path/DroidSansFallback.ttf || true rm path/DroidSansFallbackLegacy.ttf || true Would work too. On 2014-09-21 10:28, Jonas Smedegaard wrote: How about this instead: Droid*.ttf usr/share/fonts-droid/truetype That would put away all of them. Did you really mean that? Whoops - I did mean all three of them but now realize that there's more than three. I favor Christians approach - except that I suggest not dropping those problematic fonts completely, but ship them outside of fontconfig paths so as to allow using them when explicitly needed. So in addition to rm'ing, I suggest to extend the *.install file with something like this: DroidSansFallback.ttf /usr/share/fonts-droid/truetype DroidSansFallbackLegacy.ttf /usr/share/fonts-droid/truetype ..and add a note to README.Debian on where those fonts are installed and why they are not registered with fontconfig. However, I can't help suspecting that there is no real need to include DroidSansFallback.ttf and DroidSansFallbackLegacy.ttf. Those in need of rendering documents correctly which references but does not embed those particular fonts. - 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#762341: src:mlt: should link against system shared libebur
Package: src:mlt Severity: normal -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Recent releases of MLT includes a convenience copy of libebur. That should be avoided for Debian, and instead MLT should be linked against separately packaged libebur. - Jonas -BEGIN PGP SIGNATURE- Version: GnuPG v1 iQF8BAEBCgBmBQJUHrlYXxSAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXQ3NjQ4ODQwMTIyRTJDNTBFQzUxRDQwRTI0 RUMxQjcyMjM3NEY5QkQ2AAoJEE7BtyI3T5vW93sIALSIUWEqVBZK1JM9fSpBqzTN E5exyDgIDMfUaBa7TLTdlSVJYZ0HExB3BuKKNOsYsa6yL8ZOVLHfprqpWp17ioks OPGhbPhiKs7dy3e1bDBz0zA2hT+3WQARQzDcoYSw1II9/Q9W1AQ/YVg35oQdrvin FK81uhu4nGUKVbUaJA3eE5gt9fQ4lZL00GrE+XrhjpRZNss+MEPRnLDYLj7hhPIR 79ztrNh3ngfuNb7QDW+nP2OzRcShgHxhKaEs8krDQr+aynCCcaAgCUxASI01yIjn FG3QdIcAO5+S8KZ1aH5T+XwrysYKCNxsLxfWOrAmoaCZUi8fs34/Df0M/USbZKg= =du2R -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#750255: lio-utils: FTBFS: chmod: cannot access '/«BUILDDIR»/lio-utils-3.1+git2.fd0b34fd/debian/lio-utils/usr/share/pyshared/*.py': No such file or directory
On 09/21/2014 12:14 PM, Michael Prokop wrote: * Jerome Martin [Sat Sep 20, 2014 at 07:57:47PM +0200]: I could use (read desperately require :-) ) tests and reports myself, so please guys, I will be working on the upstream code next week, now is a good time to fill my inbox with reports :-) Kernel version is always one critical piece of information for testing, so please remember to include it! Sure, I'll test my use-cases ASAP and will report back for sure. Thanks for your work, highly appreciated. Thank you! -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#760050: transition: llvm-toolchain-3.5
On 19/09/14 20:15, Sylvestre Ledru wrote: On 19/09/2014 19:43, Jonathan Wiltshire wrote: On 2014-09-19 18:22, Jonathan Wiltshire wrote: On 2014-09-19 18:03, Sylvestre Ledru wrote: Control: forwarded -1 https://release.debian.org/transitions/html/llvm-defaults-3.html On 16/09/2014 19:58, Emilio Pozuelo Monfort wrote: On 05/09/14 17:47, Emilio Pozuelo Monfort wrote: Ping? I'm mostly interested in whether the affected packages are in the tracker, i.e. we don't have 200 packages to transition but less than a handful. Sorry about the lag. That seems wrong to me. apt-rdepends -r libllvm3.4 suggests more packages like mesa, python-llvm, gambas, etc However, I am not a specialist of transition. So, it might be just me :) I think the problem is here: /lib(clang1-3.5|libllvm3.5)/ i.e. liblibllvm3.5 I'll play with the tracker and see what happens. Ok, this seems to come out with sensible results: is_good = .depends ~ /lib(clang1-3.5|llvm3.5)/ | .depends ~ /python-clang-3.5/; is_bad = .depends ~ /lib(clang1-3.4|llvm3.4)/ | .depends ~ /python-clang-3.4/; How does it look to you? Much better, thanks :) Some things left on that list is going to need a source upload to fix dependencies on -3.4 packages, plus llvm-dev switching default version, if you want 3.4 removing. yep, business as usual :/ You initially said you wanted to keep 3.4 for jessie, no? So this is a matter of changing the defaults, and then getting a few packages rebuilt and some others updating their (build-)dependencies. Isn't that the case anymore? Can you explain the plan here in detail? Emilio -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#746300: Bug#745838: usbmuxd/libusbmuxd2 breaking cups - resolved?
Le lundi, 1 septembre 2014, 08.12:06 Julian Gilbey a écrit : I just tried upgrading everything to testing yesterday, and my printer works again (I had held libusbmuxd2 and usbmuxd at earlier versions since April to use my printer). So with: cups 1.7.5-1 libusbmuxd2 1.0.9-1 usbmuxd 1.0.8-5 everything now seems to be working. If you want to close these bugs, please feel free to do so. Closing the CUPS one then, thanks! Cheers, OdyX -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#762339: uaccess creates stray empty group ACL overriting regular group permissions
I can reproduce this without udev too, so the prob is not udev. cd /dev rm -f foo touch foo chmod 0600 foo setfacl -m 'user::rw-,user:daemon:rw-,group::---,mask::rw-,other::---' foo this creates the same ACL entry as the one I found for /dev/kvm. Without the 'group::---' part of setfacl, it works correctly. So it looks like it is libacl who is at fault here. But given the current interface and all the users of this interface, I'm not sure at all how this can be solved. Possible solution is to stop returning fake acl from unix permission bits, but I guess it is just too much. BTW, for some reason, setting an ACL like this changes file group access bits too, from --- to rw-, which is the same as the acl mask. After removing the ACL (setfacl -b), these extra bits stay. This might be a bug in the kernel (both changing group perms in the first place and keeping the changed bits after removing the acl), but this looks like a different issue or question. Thanks, /mjt -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#760476: cups - crashes after reading tls stuff
On 2014-09-16 Didier 'OdyX' Raboud o...@debian.org wrote: [...] Le jeudi, 4 septembre 2014, 13.30:19 Bastian Blank a écrit : cups aborts at random times after reading certificates and keys: (…) As cups disables generation of core files, no additional information is available. Would it be imaginable for you to run a cups rebuilt with the attached patch ? I will consult with upstream and followup on this point on your other bug (#760475) [...] Hello Bastian, could you perhaps come up with a backtrace? cu Andreas -- `What a good friend you are to him, Dr. Maturin. His other friends are so grateful to you.' `I sew his ears on from time to time, sure' -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#750080: Forwarding this to upstream
On Sun, 21 Sep 2014 12:29:33 +0200 Joachim Breitner nome...@debian.org wrote: Hi, Am Sonntag, den 21.09.2014, 11:33 +0200 schrieb Joachim Breitner: To reproduce this you don't need to log out. Just switch to a tty and run: $ xinit xmonad -- :1 (If you have more than one xserver running you might need to change the :1 to some higher number) True... But: The same using an unpatched xmonad works: $ cabal unpack xmonad $ cd xmonad-0.11 $ cabal build $ xinit $PWD/dist/build/xmonad/xmonad -- :1 More information: Without ./xmonad/, xmonad starts properly in both cases: You can e.g. fire up a terminal with Shift-Alt-Enter. But the system-wide installed xmonad will display the execution error using xmessage, while the cabal-installed xmonad will print the same error on stderr (visible if you use xinit to start it). That's strange. Today I tried to reproduce this. It's now starting, but still showing the error message in xmessage. It behaves that way, no matter if .xmonad exists or not. I didn't try the unpatched version though. This is weird, as xmessage is (as far as I can tell from the code) only used when compilation fails, not when executing the xmonad binary. All very strange; anyone interested in digging deeper? I guess I will have a look at in in the next days. But I'm not even sure what the problem really is. Jörg: Can you still reproduce this? If yes, how exactly? Do you start xmonad from a tty? Do you use startx or xinit? Do you use a login manager? Where is the resulting error message shown? Regards Sven signature.asc Description: PGP signature
Bug#762312: does not work with systemd
On Sun, 21 Sep 2014 11:44:29 +0200 Thomas Liske tho...@fiasko-nw.net wrote: On 09/21/2014 03:42 AM, Sven Hartge wrote: I noticed needrestart seems to do nothing with systemd as PID1. needrestart should work with systemd... could you please provide the (full) output of: - needrestart -vr l - systemctl status `pidof smokeping` See attachments. This time there are of course different services to be restarted. If needrestart detects systemd it uses systemctl status to get the service name to be used to restart a daemon. This might break if the output of `systemctl status` would differ somewho. I guess this happened after the upgrade to systemd 215, but I am not sure. Grüße, Sven. [Core] Using UI 'NeedRestart::UI::stdio'... [main] detected systemd [main] #7244 uses non-existing /lib/i386-linux-gnu/libkmod.so.2.2.8.dpkg-new [main] #7244 is not a child [main] #7245 uses non-existing /lib/i386-linux-gnu/libkmod.so.2.2.8.dpkg-new [main] #7245 is a child of #7244 [main] #7286 uses non-existing /lib/i386-linux-gnu/libtinfo.so.5.9.dpkg-new [main] #7286 is not a child [main] #7287 uses non-existing /lib/i386-linux-gnu/libtinfo.so.5.9.dpkg-new [main] #7287 is a child of #7286 [main] #7288 uses non-existing /lib/i386-linux-gnu/libtinfo.so.5.9.dpkg-new [main] #7288 is a child of #7286 [main] #7289 uses non-existing /lib/i386-linux-gnu/libtinfo.so.5.9.dpkg-new [main] #7289 is a child of #7286 [main] #7290 uses non-existing /lib/i386-linux-gnu/libtinfo.so.5.9.dpkg-new [main] #7290 is a child of #7286 [main] #7291 uses non-existing /lib/i386-linux-gnu/libtinfo.so.5.9.dpkg-new [main] #7291 is a child of #7286 [main] #7294 uses non-existing /lib/i386-linux-gnu/libgcc_s.so.1.dpkg-new [main] #7294 is a child of #7286 [main] #7305 uses non-existing /lib/i386-linux-gnu/libtinfo.so.5.9.dpkg-new [main] #7305 is a child of #7292 [main] #7385 uses non-existing /lib/i386-linux-gnu/libtinfo.so.5.9.dpkg-new [main] #7385 is a child of #7384 [main] #7395 uses non-existing /lib/i386-linux-gnu/libtinfo.so.5.9.dpkg-new [main] #7395 is a child of #7286 [main] #7413 uses non-existing /lib/i386-linux-gnu/libtinfo.so.5.9.dpkg-new [main] #7413 is a child of #7412 [main] #7441 uses non-existing /lib/i386-linux-gnu/libtinfo.so.5.9.dpkg-new [main] #7441 is a child of #7413 [Core] #8578 is a NeedRestart::Interp::Perl # Use of runtime loader module Module::Implementation detected. Results of static scanning may be incomplete. # Use of runtime loader module Module::Runtime detected. Results of static scanning may be incomplete. [Core] #9200 is a NeedRestart::Interp::Perl [Core] #11173 is a NeedRestart::Interp::Perl [Perl] #11173: could not get a source file, skipping [Core] #11302 is a NeedRestart::Interp::Perl [Core] #11303 is a NeedRestart::Interp::Perl [Perl] #11303: could not get a source file, skipping [Core] #11304 is a NeedRestart::Interp::Perl [Perl] #11304: could not get a source file, skipping [Core] #11305 is a NeedRestart::Interp::Perl [Perl] #11305: could not get a source file, skipping [Core] #11367 is a NeedRestart::Interp::Perl [Core] #12859 is a NeedRestart::Interp::Perl [Perl] #12859: could not get a source file, skipping [Core] #12860 is a NeedRestart::Interp::Perl [Core] #19232 is a NeedRestart::Interp::Perl [Perl] #19232: could not get a source file, skipping [Core] #19233 is a NeedRestart::Interp::Perl [Perl] #19233: could not get a source file, skipping [Core] #19236 is a NeedRestart::Interp::Perl [Perl] #19236: could not get a source file, skipping [Core] #19237 is a NeedRestart::Interp::Perl [Perl] #19237: could not get a source file, skipping [Core] #19242 is a NeedRestart::Interp::Perl [Perl] #19242: could not get a source file, skipping [Core] #20141 is a NeedRestart::Interp::Python [Core] #21975 is a NeedRestart::Interp::Python [Core] #24168 is a NeedRestart::Interp::Perl [Perl] #24168: could not get a source file, skipping [Core] #24333 is a NeedRestart::Interp::Perl [Perl] #24333: could not get a source file, skipping [Core] #24334 is a NeedRestart::Interp::Perl [Perl] #24334: could not get a source file, skipping [main] #24373 uses obsolete binary /usr/bin/perl.dpkg-new [main] #24373 is not a child [main] #26014 uses non-existing /lib/i386-linux-gnu/libtinfo.so.5.9.dpkg-new [main] #26014 is a child of #7286 [main] #26119 uses non-existing /lib/i386-linux-gnu/libtinfo.so.5.9.dpkg-new [main] #26119 is a child of #26014 [main] #26122 uses non-existing /lib/i386-linux-gnu/libtinfo.so.5.9.dpkg-new [main] #26122 is a child of #26121 [main] #7244 exe = /lib/systemd/systemd [main] #7244 is * user@1000.service [main] #7286 exe = /usr/bin/screen [main] #7286 running /etc/needrestart/hook.d/10-dpkg [main] #7286 package: screen [main] #7286 rc.d script screen-cleanup should not start in the current run-level(5) [main] #7286 running /etc/needrestart/hook.d/20-rpm [main] #7286 running /etc/needrestart/hook.d/30-pacman [main] #7286 running /etc/needrestart/hook.d/90-none [main] #7292 exe = /bin/dash [main] #7292
Bug#750586: Bug#756275: debian-installer: [PATCH] Fix lib location and search path for syslinux = 5
Ron r...@debian.org (2014-09-21): On Sat, Sep 20, 2014 at 02:28:24PM -0700, Chris Kuehl wrote: Thanks for your work on this -- we're also experiencing this bug in both jessie and sid daily netboot images in our PXE boot environment. On Thu, Aug 07, 2014 at 01:46:06PM +0200, Cyril Brulebois wrote: I could apply it blindly but it'd be nice if someone else would confirm it works fine. I've got other things cooking, but I might end up testing it myself it nobody steps up. I might be building the image wrong, No, it looks like you did everything right afaics :) That was a blind and untested patch, working backward from what I'd hand-hacked in place to get it working for me, at the end of a long day, and the first time I'd ever even looked at this code ... It looks like I read $(TEMP_NETBOOT_DIR)/$(BOOT_SCREEN_DIR) wrong in the surrounding code and assumed BOOT_SCREEN_DIR only had the /boot-screens part in it. Or at least that's the only thing I can think I must have done, since now that you've pointed, and I'm looking at it again, your version of that link definitely looks like the right one to me. Indeed amd64/netboot.cfg has: BOOT_SCREEN_DIR = $(NETBOOT_PATH)/boot-screens/ Only the ia64 version appears to define or use it how I used it there. Thanks for actually testing this and sending a fixed patch! Looks like I could just blindly apply both patches, squashing them and crediting both of you then? It was low-priority (especially since untested) and I wasn't too keen on spending time on it, but if we have success reports, merging looks like a good idea. Mraw, KiBi. signature.asc Description: Digital signature
Bug#758872: Sigificant improvement after updates today
Open Nemo, bookmarks on non-mounted drives do not appear - OK No problem Mount drive - boomarks do not appear - Ah .. Close Reopen Nemo and the bookmarks now appear in LHS pane. Thank you to whoever made the appropriate change wherever it was - that is now much more useable. Just a note (trying not to be too greedy!) - it would be very nice to have the bookmarks appear automatically in the LHS pane when the drive is mounted! -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#762342: task-cinnamon-desktop: Please turn on display of Cinnamon desktop task
Package: tasksel Version: 3.26 Severity: normal Please turn on display of the Cinnamon desktop task. I have tested building Jessie live images with Cinnamon included and it seems to already provide a usable desktop. It would be useful for testers to be able to see Cinnamon so they can try it and help shake out any remaining bugs between now and the freeze. Thanks, Ben -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#761550: Imagemagick transition
On Mon, Sep 15, 2014 at 11:39:03PM +0200, Gabriele Giacone wrote: Bastien, On Mon, Sep 15, 2014 at 10:21 PM, Bastien ROUCARIES roucaries.bast...@gmail.com wrote: the debdiff - default-jdk, libmagickcore-extra, python (= 2.6.6-3~) + default-jdk, python (= 2.6.6-3~), + libmagickcore-6.q16-2-extra Fixing it means switching from an unversioned libmagickcore-extra which IS provided by libmagickcore-6.q16-2-extra to libmagickcore-6.q16-2-extra ?! Useless upload, packages have been removed just few hours before your reply: = [Date: Mon, 15 Sep 2014 16:58:03 +] [ftpmaster: Scott Kitterman] Removed the following packages from unstable: libmagick++5 | 8:6.7.7.10+dfsg-5 | amd64, arm64, armel, armhf, i386, kfreebsd-amd64, kfreebsd-i386, mips, mipsel, powerpc, ppc64el, s390x, sparc libmagickcore5 | 8:6.7.7.10+dfsg-5 | amd64, arm64, armel, armhf, i386, kfreebsd-amd64, kfreebsd-i386, mips, mipsel, powerpc, ppc64el, s390x, sparc libmagickcore5-extra | 8:6.7.7.10+dfsg-5 | amd64, arm64, armel, armhf, i386, kfreebsd-amd64, kfreebsd-i386, mips, mipsel, powerpc, ppc64el, s390x, sparc libmagickwand5 | 8:6.7.7.10+dfsg-5 | amd64, arm64, armel, armhf, i386, kfreebsd-amd64, kfreebsd-i386, mips, mipsel, powerpc, ppc64el, s390x, sparc --- Reason --- [auto-cruft] NBS (no longer built by imagemagick) -- = I guess it was actually fixed at 19:52 UTC, next dinstall. It also makes another upload necessary whenever libmagickcore-6.q16-2-extra will be replaced. Package name suggests it will. Glad to be corrected if missing anything. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#712907: grub-installer: No longer installs automatically on a normal machine with one hard drive
Just to be sure everyone reading this bug report understand what I see as the problem, I present the installation as it is seen from Debian Edu in Jessie. URL: https://jenkins.debian.net/job/g-i-installation_debian-edu_jessie_standalone/12/ show the grub dialog that show up at the end of the Debian Edu installation. It ask people to type in the device path for grub. See URL: https://jenkins.debian.net/job/g-i-installation_debian-edu_jessie_standalone/12/artifact/results/snapshot_004900.png for the dialog text. This is very bad from a usability point of view, as normal people are not expected to know device paths. -- Happy hacking Petter Reinholdtsen -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#749264: No nvidia-driver working
Hello Vincent, thank you for your explanations! I suggest to add them to the Debian Wiki, because this system is not explained there. Shall i try to add it? When you google for specific problems you will find to much wrong hints. But here you see how many people have problems with this theme. ;-) Am 21.09.2014 11:44, schrieb Vincent Cheng: It's no surprise that X won't load, given that you're trying to use the nvidia 304.xx driver series with hardware that doesn't support it. O.K. - but why the 304.117 driver is installed when i install dkms? It would be better that there is a dependency that announces a conflict when i want to have a 173xx driver. Assuming you're just an uninformed user with no idea what dkms is and just want a working X server + nvidia driver...why would you care to install nvidia-kernel-dkms? All you would reasonably be expected to do is to run nvidia-detect and install whatever package it told you to install. Or if you were a new user with no knowledge of nvidia-detect, you would instead google for nvidia debian or similar, hit this wiki page [1] as your first search result, and then proceed to install the correct package. I assumed i need the dkms package to automatically recompile the display driver. Now i understand the differences. As i have written nouveau failed because it does not support this hardware. But the nouveau driver from Knoppix is doing it. Probably because Knoppix is using a newer kernel? I think so (should be /kernel/ 3.0.4) - but this is not a big difference. It is crazy that you need a newer kernel to support older hardware? As i said - there are to much much dependencies that are not understandable. Experiments with new kernels in an stable working environment is causing more problems than solving it. Then you have X but you loose sound or some interface hardware ... File bug reports against the kernel for specific issues. Also, you seem to have no issues using Knoppix (which AFAIK packages newer kernels than what is typically found in Debian stable...). Yes - but AFAIK there are no AMD64 versions of it. Debian has the best support for so many different CPU's. That's one of many reasons to use it. It is the base for so many other distributions. So it would be wonderful if the X-problems could be minimized at the base. Best regards Karsten [1] https://wiki.debian.org/NvidiaGraphicsDrivers -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#753809: ginkgocadx: will not display studies
On Sun, Sep 21, 2014 at 10:41:54AM +1000, Dmitry Smirnov wrote: Could you please help me to reproduce this problem? I can successfully open bunch of dicom files I have as well as anything from Ginkgo cloud. I'm not as familiar with ginkgocadx interface as you are so I will need a detailed how-to instructions what to do to hit the problem. No problem. It only seems to appear when using a DICOM server (say, Orthanc). This is my workflow to reproduce the problem: - open Ginkgo - open a DICOM (.dcm) file which has not been viewed in Ginkgo before - Ginkgo will happily display this file - in Ginkgo upload the file to the DICOM server At this stage, other DICOM viewers (say, Aeskulap) will happily retrieve the file from the DICOM server _and_ gladly display it. - in Gingko remove the file from the viewing history - in Ginkgo query the DICOM server for the study (the DICOM file) you just uploaded - in Ginkgo download the DICOM file from the DICOM server - Ginkgo now fails to create a thumbnail and also fails to display the DICOM file after download despite having properly displayed it before Note that it IS possible to download the very same file from the very same DICOM server and properly display it using _another_ DICOM viewer (say, Aeskulap). In other words, the failure does NOT depend on the DICOM server. I also tried the following: - at the filesystem level copy the downloaded-and-failing-to-display DICOM file to another directory - in Ginkgo remove the failing file from the history - in Ginkgo open the copied file (which previously failed after the download) as if it was a new file - Ginkgo _still_ fails to display the file This means, that something permanent is being done to the file when Ginkgo first downloads it from the DICOM server. Note that other DICOM viewers (Aeskulap) gladly display the copy (which, again, still fails in Ginkgo). _Very_ strange. And frustrating :-) Karsten -- GPG key ID E4071346 @ gpg-keyserver.de E167 67FD A291 2BEA 73BD 4537 78B9 A9F9 E407 1346 -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#762324: linux-image-3.16-2-amd64: sed error when executing /etc/kernel/postinst.d/dkms
Jacek Sobczak wrote: Package: src:linux Version: 3.16.3-2 Severity: normal Dear Maintainer, When upgrading linux kernel I get such error messages: Setting up linux-image-3.16-2-amd64 (3.16.3-2) ... /etc/kernel/postinst.d/dkms: sed: -e expression #1, char 6: unknown command: `m' sed: -e expression #1, char 6: unknown command: `m' My installed dkms packages: tp-smapi-dkms and virtualbox-dkms. I got that message too and I only installed virtualbox-dkms -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#762344: webfs: [INTL:it] Italian translation of debconf messages
Package: webfs Severity: wishlist Tags: l10n patch Hi. Please find attached the Italian translation of webfs debconf messages proofread by the Italian localization team. Please include it in your next upload. Thanks, Beatrice # ITALIAN TRANSLATION OF WEBFS' PO-DEBCONF FILE. # COPYRIGHT (C) 2010 THE WEBFS' COPYRIGHT HOLDER # This file is distributed under the same license as the webfs package. # Vincenzo Campanella vin...@gmail.com, 2010. # Beatrice Torracca beatri...@libero.it, 2014. msgid msgstr Project-Id-Version: webfs 1.21+ds1-3\n Report-Msgid-Bugs-To: we...@packages.debian.org\n POT-Creation-Date: 2014-09-01 17:36+0200\n PO-Revision-Date: 2014-09-15 19:57+0200\n Last-Translator: Beatrice Torracca beatri...@libero.it\n Language-Team: Italian debian-l10n-ital...@lists.debian.org\n Language: it\n MIME-Version: 1.0\n Content-Type: text/plain; charset=UTF-8\n Content-Transfer-Encoding: 8bit\n Plural-Forms: nplurals=2; plural=(n != 1);\n X-Generator: Virtaal 0.7.1\n #. Type: string #. Description #: ../templates:2001 msgid IP address webfsd should listen to: msgstr Indirizzo IP su cui webfsd dovrà porsi in ascolto: #. Type: string #. Description #: ../templates:2001 msgid On a system with multiple IP addresses, webfsd can be configured to listen to only one of them. msgstr Su sistemi con più indirizzi IP webfsd può essere configurato in modo da porsi in ascolto su un solo indirizzo. #. Type: string #. Description #: ../templates:2001 msgid If you leave this empty, webfsd will listen to all IP addresses. msgstr Se si lascia questo campo vuoto webfsd si porrà in ascolto su tutti gli indirizzi IP. #. Type: string #. Description #: ../templates:3001 msgid Timeout for network connections: msgstr Tempo massimo di attesa per le connessioni di rete: #. Type: string #. Description #: ../templates:5001 msgid Number of parallel network connections: msgstr Numero di connessioni di rete parallele: #. Type: string #. Description #: ../templates:5001 msgid For small private networks, the default number of parallel network connections should be fine. This can be increased for larger networks. msgstr Il numero predefinito di connessioni di reti parallele dovrebbe essere adeguato per piccole reti private. Questo valore può essere incrementato per reti più grandi. #. Type: string #. Description #: ../templates:6001 msgid Directory cache size: msgstr Dimensioni della cache delle directory: #. Type: string #. Description #: ../templates:6001 msgid Directory listings can be cached by webfsd. By default, the size of the cache is limited to 128 entries. If the web server has very big directory trees, you might want to raise this value. msgstr Webfsd può memorizzare in cache l'elenco dei contenuti delle directory. La dimensione predefinita della cache è limitata a 128 voci. Se il server web ha una struttura di directory molto estesa, potrebbe essere opportuno incrementare tale valore. #. Type: string #. Description #: ../templates:7001 msgid Incoming port number for webfsd: msgstr Numero di porta in entrata per webfsd: #. Type: string #. Description #: ../templates:7001 msgid Please enter the port number for webfsd to listen to. If you leave this blank, the default port (8000) will be used. msgstr Inserire il numero della porta su cui webfsd si porrà in ascolto. Se si lascia questo campo vuoto verrà utilizzata la porta predefinita (8000). #. Type: boolean #. Description #: ../templates:8001 msgid Enable virtual hosts? msgstr Abilitare gli host virtuali? #. Type: boolean #. Description #: ../templates:8001 msgid This option allows webfsd to support name-based virtual hosts, taking the directories immediately below the document root as host names. msgstr Questa opzione consente a webfsd di supportare gli host virtuali basati sul nome, prendendo le directory immediatamente sottostanti la radice dei documenti come nomi degli host. #. Type: string #. Description #: ../templates:9001 msgid Document root for webfsd: msgstr Radice dei documenti per webfsd: #. Type: string #. Description #: ../templates:9001 msgid Webfsd is a lightweight HTTP server for mostly static content. Its most obvious use is to provide HTTP access to an anonymous FTP server. msgstr Webfsd è un server HTTP leggero soprattutto per contenuti statici il cui più ovvio utilizzo è fornire un accesso HTTP a un server FTP anonimo. #. Type: string #. Description #: ../templates:9001 msgid Please specify the document root for the webfs daemon. msgstr Specificare la radice dei documenti per il demone webfs. #. Type: string #. Description #: ../templates:9001 msgid If you leave this field blank, webfsd will not be started at boot time. msgstr Se si lascia questo campo vuoto webfsd non verrà fatto partire all'avvio del sistema. #. Type: string #. Description #: ../templates:10001 msgid Host name for webfsd: msgstr Nome host per webfsd: #. Type: string #. Description #: ../templates:10001 msgid By default, webfsd uses the
Bug#762345: task-mate-desktop: typo in tasks/mate-desktop Relevance: field
Package: tasksel Version: 3.26 Severity: normal Tags: patch There is a typo in the tasks/mate-desktop file. I have attached a patch to fix it. diff -Nru tasksel-3.26/tasks/mate-desktop tasksel-3.26+nmu1/tasks/mate-desktop --- tasksel-3.26/tasks/mate-desktop 2014-09-20 10:57:09.0 -0300 +++ tasksel-3.26+nmu1/tasks/mate-desktop 2014-09-21 08:38:55.0 -0300 @@ -1,7 +1,7 @@ Task: mate-desktop Section: user Parent: desktop -Relvance: 7 +Relevance: 7 Test-default-desktop: 3 mate Key: task-mate-desktop
Bug#762312: does not work with systemd
On Sun, 21 Sep 2014 13:53:27 +0200 Sven Hartge s...@svenhartge.de wrote:
On Sun, 21 Sep 2014 11:44:29 +0200 Thomas Liske tho...@fiasko-nw.net
wrote:
On 09/21/2014 03:42 AM, Sven Hartge wrote:
I noticed needrestart seems to do nothing with systemd as PID1.
needrestart should work with systemd... could you please provide the
(full) output of:
- needrestart -vr l
- systemctl status `pidof smokeping`
See attachments. This time there are of course different services to be
restarted.
I think, the regexp in line 328 is too broad and the anchor ^ does not
work anymore because there is a * prepending the service name in the
output of systemctl status.
if(defined($ret) $ret =~ /^([^.]+\.service) /) {
I propose the following:
if(defined($ret) $ret =~ /([\w_+-]+\.service) /) {
Question is: what other characters my be in a service name?
Grüße,
Sven.
signature.asc
Description: OpenPGP digital signature
Bug#762345: task-mate-desktop: typo in tasks/mate-desktop Relevance: field
Control: tag -1 pending Ben Armstrong sy...@sanctuary.nslug.ns.ca (2014-09-21): Package: tasksel Version: 3.26 Severity: normal Tags: patch There is a typo in the tasks/mate-desktop file. I have attached a patch to fix it. diff -Nru tasksel-3.26/tasks/mate-desktop tasksel-3.26+nmu1/tasks/mate-desktop --- tasksel-3.26/tasks/mate-desktop 2014-09-20 10:57:09.0 -0300 +++ tasksel-3.26+nmu1/tasks/mate-desktop 2014-09-21 08:38:55.0 -0300 @@ -1,7 +1,7 @@ Task: mate-desktop Section: user Parent: desktop -Relvance: 7 +Relevance: 7 Test-default-desktop: 3 mate Key: task-mate-desktop If you had attached a patch against git you'd have noticed it was fixed in master already. :p Mraw, KiBi. signature.asc Description: Digital signature
Bug#712907: grub-installer: No longer installs automatically on a normal machine with one hard drive
Petter Reinholdtsen p...@hungry.com (2014-09-21): Just to be sure everyone reading this bug report understand what I see as the problem, I present the installation as it is seen from Debian Edu in Jessie. URL: https://jenkins.debian.net/job/g-i-installation_debian-edu_jessie_standalone/12/ show the grub dialog that show up at the end of the Debian Edu installation. It ask people to type in the device path for grub. See URL: https://jenkins.debian.net/job/g-i-installation_debian-edu_jessie_standalone/12/artifact/results/snapshot_004900.png for the dialog text. This is very bad from a usability point of view, as normal people are not expected to know device paths. Well, I don't know anything about Debian Edu, but I'm pretty sure there's another prompt before that in non-Edu, where devices are listed, and where users can pick from. KiBi. signature.asc Description: Digital signature
Bug#762312: does not work with systemd
On 21.09.2014 14:16, Sven Hartge wrote:
On Sun, 21 Sep 2014 13:53:27 +0200 Sven Hartge s...@svenhartge.de wrote:
On Sun, 21 Sep 2014 11:44:29 +0200 Thomas Liske tho...@fiasko-nw.net
wrote:
On 09/21/2014 03:42 AM, Sven Hartge wrote:
I noticed needrestart seems to do nothing with systemd as PID1.
needrestart should work with systemd... could you please provide the
(full) output of:
- needrestart -vr l
- systemctl status `pidof smokeping`
See attachments. This time there are of course different services to be
restarted.
I think, the regexp in line 328 is too broad and the anchor ^ does not
work anymore because there is a * prepending the service name in the
output of systemctl status.
if(defined($ret) $ret =~ /^([^.]+\.service) /) {
I propose the following:
if(defined($ret) $ret =~ /([\w_+-]+\.service) /) {
Question is: what other characters my be in a service name?
The @, for example, to answer my own question. So the regexp should be
more like:
if(defined($ret) $ret =~ /([\w_+-@]+\.service) /) {
Or, using the blacklist approach (still needing to remove the first ^),
excluding the whitespace beetween the * and the real service name:
if(defined($ret) $ret =~ /([^.^\s]+\.service) /) {
Grüße,
Sven.
signature.asc
Description: OpenPGP digital signature
Bug#762346: RFP: pypy3 -- fast alternative implementation of Python3 - PyPy interpreter
Package: wnpp Severity: wishlist * Package name: pypy3 Version : 2.3.1 Upstream Author : Armin Rigo ar...@tunes.org * URL : http://www.pypy.org * License : MIT Programming Lang: Python Description : fast alternative implementation of Python3 - PyPy interpreter PyPy3 is a fast, compliant alternative implementation of the Python3 language (3.2). It has several advantages and distinct features: * Speed: thanks to its Just-in-Time compiler (on x86), Python programs often run faster on PyPy. * Memory usage: large, memory-hungry Python programs might end up taking less space than they do in CPython. * Compatibility: PyPy is highly compatible with existing Python code. It supports ctypes and can run popular Python libraries like twisted and django. * Stackless: PyPy supports stackless mode on x86, providing micro-threads for massive concurrency. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
