Bug#765577: (no subject)
Control: tag -1 pending
Hey Faidon,
Faidon Liambotis [2015-04-22 15:25 +0300]:
-new_rule_pattern=$(echo ^SUBSYSTEM==\net\, ACTION==\add\$match | sed
-re 's/([\?\*])/\\\1/g')
+new_rule_pattern=$(echo ^SUBSYSTEM==\net\, ACTION==\add\$match | sed
-re 's/([\?\*\{\}])/\\\1/g')
Thanks for spotting this! I tested this now with Marco's test script,
and it still works fine. Committed to master now:
http://anonscm.debian.org/cgit/pkg-systemd/systemd.git/commit/?id=3d02f64154
(to experimental too).
I have to say... constructing regexps in shell is tricky and the
whole escaping-with-sed logic feels like a hack. I think a literal
grep (i.e. -F) would be better here, especially since I don't see
the point of an exact match (even if the file was modified by the
sysadmin, the right thing would to not write a new rule anyway).
This is probably something to be considered post-jessie.
Yeah, the whole generator is a horrible thing.. For the future I
actually want to propose a bolder change:
https://lists.debian.org/debian-devel/2015/05/msg00170.html
Martin
--
Martin Pitt| http://www.piware.de
Ubuntu Developer (www.ubuntu.com) | Debian Developer (www.debian.org)
signature.asc
Description: Digital signature
Processed: Re: Bug#765577: (no subject)
Processing control commands: tag -1 pending Bug #765577 [udev-udeb] netboot install writes duplicates to 70-persistent-net.rules Bug #777126 [udev-udeb] udev: duplicate eth? entries Added tag(s) pending. Added tag(s) pending. -- 765577: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=765577 777126: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=777126 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#784709: when would blkid success but not filesystem type?
In https://bugs.debian.org/784709 Jérôme Kieffer wrote: Here is the answer for the 3.16 kernel: jerome@patagonia:~$ sudo blkid -o value -s TYPE /dev/sdb4 jerome@patagonia:~$ echo $? 0 ... The output is the same on 3.2, as you can see on attached images. Anyone know when blkid would return success but not the filesystem type? This is util-linux 2.25.2-6 with Linux 3.16/3.2 and an extended partition. -- bye, pabs https://wiki.debian.org/PaulWise signature.asc Description: This is a digitally signed message part
Processed: your mail
Processing commands for cont...@bugs.debian.org: close 785255 Bug #785255 [ardour3] ardour3: ardour segfault Marked Bug as done # problem not reproducible any more by original reporter thanks Stopping processing here. Please contact me if you need assistance. -- 785255: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=785255 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#785122: chocolate-doom is marked for autoremoval from testing
Control: severity -1 minor Control: forwarded -1 https://github.com/chocolate-doom/chocolate-doom/issues/479 Control: tags -1 upstream pending Control: retitle -1 accidental license upgrade to GPLv3+ Upstream also considers this a non-issue, thus downgrading severity: https://github.com/chocolate-doom/chocolate-doom/issues/479#issuecomment-104072886 Cheers, Fabian signature.asc Description: This is a digitally signed message part
Processed: Re: Bug#785122: chocolate-doom is marked for autoremoval from testing
Processing control commands: severity -1 minor Bug #785122 [src:chocolate-doom] chocolate-doom: includes licence-incompatible GPLv3 code Severity set to 'minor' from 'serious' forwarded -1 https://github.com/chocolate-doom/chocolate-doom/issues/479 Bug #785122 [src:chocolate-doom] chocolate-doom: includes licence-incompatible GPLv3 code Set Bug forwarded-to-address to 'https://github.com/chocolate-doom/chocolate-doom/issues/479'. tags -1 upstream pending Bug #785122 [src:chocolate-doom] chocolate-doom: includes licence-incompatible GPLv3 code Added tag(s) upstream and pending. retitle -1 accidental license upgrade to GPLv3+ Bug #785122 [src:chocolate-doom] chocolate-doom: includes licence-incompatible GPLv3 code Changed Bug title to 'accidental license upgrade to GPLv3+' from 'chocolate-doom: includes licence-incompatible GPLv3 code' -- 785122: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=785122 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: telepathy-qt: FTBFS due to symbols file
Processing control commands: block 760003 by -1 Bug #760003 [release.debian.org] transition: qt-gstreamer 760003 was blocked by: 786363 783674 731121 760003 was not blocking any bugs. Added blocking bug(s) of 760003: 786391 -- 760003: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=760003 786391: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=786391 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#786391: telepathy-qt: FTBFS due to symbols file
Source: telepathy-qt Version: 0.9.5+dfsg-3 Severity: serious Control: block 760003 by -1 Your package failed to build almost everywhere: https://buildd.debian.org/status/logs.php?pkg=telepathy-qtver=0.9.5%2Bdfsg-3 This blocks ktp-call-ui which blocks the qt-gstreamer transition. Emilio -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: Re: Bug#772185: chkrootkit: false positive systemd /sbin/init
Processing control commands:
forcemerge 740898 -1
Bug #740898 {Done: Giuseppe Iuculano iucul...@debian.org} [chkrootkit]
chkrootkit: falsely flags Suckit rootkit when systemd is /sbin/init
Bug #748048 {Done: Giuseppe Iuculano iucul...@debian.org} [chkrootkit]
chkrootkit: Error message since switching to systemd
Bug #740898 {Done: Giuseppe Iuculano iucul...@debian.org} [chkrootkit]
chkrootkit: falsely flags Suckit rootkit when systemd is /sbin/init
Marked as found in versions chkrootkit/0.50-2.
Marked as found in versions chkrootkit/0.50-2.
Added tag(s) upstream.
Added tag(s) upstream.
Bug #772185 [chkrootkit] chkrootkit: false positive systemd /sbin/init
Severity set to 'serious' from 'normal'
Marked Bug as done
Marked as fixed in versions chkrootkit/0.50-3.
Marked as found in versions chkrootkit/0.49-4.1.
Bug #748048 {Done: Giuseppe Iuculano iucul...@debian.org} [chkrootkit]
chkrootkit: Error message since switching to systemd
Merged 740898 748048 772185
--
740898: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=740898
748048: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=748048
772185: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=772185
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#786379: ruby-fog-local and ruby-fog: error when trying to install together
Package: ruby-fog,ruby-fog-local Version: ruby-fog/1.28.0-2 Version: ruby-fog-local/0.2.1-1 Severity: serious User: trei...@debian.org Usertags: edos-file-overwrite Date: 2015-05-21 Architecture: amd64 Distribution: sid Hi, automatic installation tests of packages that share a file and at the same time do not conflict by their package dependency relationships has detected the following problem: Extracting templates from packages: 68% Extracting templates from packages: 100% Preconfiguring packages ... Selecting previously unselected package gcc-5-base:amd64. (Reading database ... 10927 files and directories currently installed.) Preparing to unpack .../gcc-5-base_5.1.1-6_amd64.deb ... Unpacking gcc-5-base:amd64 (5.1.1-6) ... Setting up gcc-5-base:amd64 (5.1.1-6) ... (Reading database ... 10934 files and directories currently installed.) Preparing to unpack .../libstdc++6_5.1.1-6_amd64.deb ... Unpacking libstdc++6:amd64 (5.1.1-6) over (4.8.2-19) ... Setting up libstdc++6:amd64 (5.1.1-6) ... Processing triggers for libc-bin (2.19-18) ... Selecting previously unselected package libgcrypt20:amd64. (Reading database ... 10948 files and directories currently installed.) Preparing to unpack .../libgcrypt20_1.6.3-2_amd64.deb ... Unpacking libgcrypt20:amd64 (1.6.3-2) ... Selecting previously unselected package libicu52:amd64. Preparing to unpack .../libicu52_52.1-9_amd64.deb ... Unpacking libicu52:amd64 (52.1-9) ... Selecting previously unselected package libxml2:amd64. Preparing to unpack .../libxml2_2.9.2+dfsg1-3_amd64.deb ... Unpacking libxml2:amd64 (2.9.2+dfsg1-3) ... Selecting previously unselected package libffi6:amd64. Preparing to unpack .../libffi6_3.1-2+b2_amd64.deb ... Unpacking libffi6:amd64 (3.1-2+b2) ... Selecting previously unselected package libgmp10:amd64. Preparing to unpack .../libgmp10_2%3a6.0.0+dfsg-6_amd64.deb ... Unpacking libgmp10:amd64 (2:6.0.0+dfsg-6) ... Selecting previously unselected package libxslt1.1:amd64. Preparing to unpack .../libxslt1.1_1.1.28-2+b2_amd64.deb ... Unpacking libxslt1.1:amd64 (1.1.28-2+b2) ... Selecting previously unselected package libyaml-0-2:amd64. Preparing to unpack .../libyaml-0-2_0.1.6-3_amd64.deb ... Unpacking libyaml-0-2:amd64 (0.1.6-3) ... Selecting previously unselected package openssl. Preparing to unpack .../openssl_1.0.2a-1_amd64.deb ... Unpacking openssl (1.0.2a-1) ... Selecting previously unselected package ca-certificates. Preparing to unpack .../ca-certificates_20141019_all.deb ... Unpacking ca-certificates (20141019) ... Selecting previously unselected package rubygems-integration. Preparing to unpack .../rubygems-integration_1.8_all.deb ... Unpacking rubygems-integration (1.8) ... Selecting previously unselected package libruby2.1:amd64. Preparing to unpack .../libruby2.1_2.1.5-3_amd64.deb ... Unpacking libruby2.1:amd64 (2.1.5-3) ... Selecting previously unselected package ruby2.1. Preparing to unpack .../ruby2.1_2.1.5-3_amd64.deb ... Unpacking ruby2.1 (2.1.5-3) ... Selecting previously unselected package ruby. Preparing to unpack .../ruby_1%3a2.1.5+z_all.deb ... Unpacking ruby (1:2.1.5+z) ... Selecting previously unselected package ruby-blankslate. Preparing to unpack .../ruby-blankslate_2.1.2.4-4_all.deb ... Unpacking ruby-blankslate (2.1.2.4-4) ... Selecting previously unselected package ruby-builder. Preparing to unpack .../ruby-builder_3.2.2-4_all.deb ... Unpacking ruby-builder (3.2.2-4) ... Selecting previously unselected package ruby-excon. Preparing to unpack .../ruby-excon_0.45.1-2_all.deb ... Unpacking ruby-excon (0.45.1-2) ... Selecting previously unselected package ruby-formatador. Preparing to unpack .../ruby-formatador_0.2.1-2_all.deb ... Unpacking ruby-formatador (0.2.1-2) ... Selecting previously unselected package ruby-mime-types. Preparing to unpack .../ruby-mime-types_1.25-2_all.deb ... Unpacking ruby-mime-types (1.25-2) ... Selecting previously unselected package ruby-net-ssh. Preparing to unpack .../ruby-net-ssh_1%3a2.9.2-2_all.deb ... Unpacking ruby-net-ssh (1:2.9.2-2) ... Selecting previously unselected package ruby-net-scp. Preparing to unpack .../ruby-net-scp_1.2.1-2_all.deb ... Unpacking ruby-net-scp (1.2.1-2) ... Selecting previously unselected package ruby-fog-core. Preparing to unpack .../ruby-fog-core_1.30.0-2_all.deb ... Unpacking ruby-fog-core (1.30.0-2) ... Selecting previously unselected package ruby-multi-json. Preparing to unpack .../ruby-multi-json_1.11.0-1_all.deb ... Unpacking ruby-multi-json (1.11.0-1) ... Selecting previously unselected package ruby-fog-json. Preparing to unpack .../ruby-fog-json_1.0.0-1_all.deb ... Unpacking ruby-fog-json (1.0.0-1) ... Selecting previously unselected package ruby-nokogiri. Preparing to unpack .../ruby-nokogiri_1.6.6.2+ds-2_amd64.deb ... Unpacking ruby-nokogiri (1.6.6.2+ds-2) ... Selecting previously unselected package ruby-fog-xml. Preparing to unpack .../ruby-fog-xml_0.1.1-4_all.deb ... Unpacking ruby-fog-xml (0.1.1-4) ... Selecting previously unselected package
Processed: severity of 784774 is important
Processing commands for cont...@bugs.debian.org: severity 784774 important Bug #784774 [php5-uprofiler] php5-uprofiler: uprofiler.ini incorrectly references profiler.so instead of uprofiler.so Severity set to 'important' from 'grave' thanks Stopping processing here. Please contact me if you need assistance. -- 784774: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=784774 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#785255: ardour3(4) is back!
On Thu, May 21, 2015 at 07:15:12AM +0200, Jaromír Mikeš wrote: can you confirm one more that you don't having this problem any more? So we can close this bug report? Hi Mira, I can confirm ardour3(4) is now running and correctly starts jackd. Thank you for maintaining free software. Best, Alberto -- Alberto Maurizi a.maur...@isac.cnr.it ISAC-CNR Phone n. +39 051 639 9615 via Gobetti 101 Fax n. +39 051 639 9658 40129 Bologna, Italy home page: http://bolchem.isac.cnr.it/staff:alberto_maurizi.do bolchem project:http://bolchem.isac.cnr.it -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: Re: [pkg-x2go-devel] Bug#784565: Bug#784565: Bug#784565: Bug#784565: nx-libs-lite: parts are derived from non-free code
Processing control commands: forwarded -1 https://github.com/ArcticaProject/nx-libs/issues/30 Bug #784565 [nx-libs-lite] nx-libs-lite: parts are derived from non-free code Set Bug forwarded-to-address to 'https://github.com/ArcticaProject/nx-libs/issues/30'. -- 784565: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=784565 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#784565: [pkg-x2go-devel] Bug#784565: Bug#784565: Bug#784565: Bug#784565: nx-libs-lite: parts are derived from non-free code
Control: forwarded -1 https://github.com/ArcticaProject/nx-libs/issues/30 Hi Francesco, On Mi 20 Mai 2015 20:03:25 CEST, Francesco Poli wrote: On Tue, 19 May 2015 08:15:12 + Mike Gabriel wrote: [...] @Frederico: I guess we are through then. Yes, it seems so (I'm assuming you meant to direct this question to me...). Yes. :-) For fixing this issue (in terms of closing the bug), I propose this for downstream (i.e., Debian): o copy bug_784565.mbox [1] into the debian/ folder of the nx-libs-lite package Maybe the entire bug log is an overkill... I would include the relevant replies only. For instance: https://bugs.debian.org/cgi-bin/bugreport.cgi?msg=40;mbox=yes;bug=784565 https://bugs.debian.org/cgi-bin/bugreport.cgi?msg=77;mbox=yes;bug=784565 https://bugs.debian.org/cgi-bin/bugreport.cgi?msg=87;mbox=yes;bug=784565 https://bugs.debian.org/cgi-bin/bugreport.cgi?msg=102;mbox=yes;bug=784565 ACK. o upload some latest release of nx-libs-lite 3.5.0.x to unstable o update debian/copyright accordingly In the debian/copyright file the license for the original DXPC code should be replaced with the 2-clause BSD license (currently adopted for DXPC) with a comment saying something like: The original DXPC code used to be available under a license which failed to explicitly grant the permission to modify, but was later retroactively re-licensed under the 2-clause BSD license (see debian/bug_784565_*.mbox for the copyright owners' statements; see https://bugs.debian.org/784565 for more details) Moreover, the copyright notice of Gian Filippo Pinzari should be documented in some more appropriate part of the debian/copyright file, associated with the NoMachine license (GPL v2 or later). o close this bug via debian/changelog For upstream, I propose this: o copy bug_784565.mbox into the docs/ folder Again, I would not include the entire bug log, but only the relevant messages (see above)... o update copyright information in nxcomp/ subfolder o provide some README or such that shortly explains our last weeks' process o this will be for the upcoming 3.6.x release series of nx-libs o this should also be backported to the 3.5.x release series Doing all the above now. Thanks to all, Mike -- DAS-NETZWERKTEAM mike gabriel, herweg 7, 24357 fleckeby fon: +49 (1520) 1976 148 GnuPG Key ID 0x25771B31 mail: mike.gabr...@das-netzwerkteam.de, http://das-netzwerkteam.de freeBusy: https://mail.das-netzwerkteam.de/freebusy/m.gabriel%40das-netzwerkteam.de.xfb pgplw7ineE6SV.pgp Description: Digitale PGP-Signatur
Bug#765577: marked as done (netboot install writes duplicates to 70-persistent-net.rules)
Your message dated Thu, 21 May 2015 09:39:47 +
with message-id e1yvmx9-0004vw...@franck.debian.org
and subject line Bug#765577: fixed in systemd 219-10
has caused the Debian Bug report #765577,
regarding netboot install writes duplicates to 70-persistent-net.rules
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
765577: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=765577
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
---BeginMessage---
Package: udev-udeb
Version: 215-5+b1
Severity: important
User: debian-...@lists.debian.org
Usertags: debian-edu
I ran into this problem when installing a Debian Edu Jessie workstation
using PXE on a Lenovo Thinkpad X200. The problem at the end is that
users can not log into the workstation because the network interface is
not properly configured. This is caused by the network card to show up
as eth1 instead of eth0. Only eth0 is configured in
/etc/network/interfaces.
This in turn is caused by /etc/udev/rules.d/70-presisten-net.rules
listing the network card twice, once with eth0 and once with eth1. The
file look like this:
# This file was automatically generated by the /lib/udev/write_net_rules
# program, run by the persistent-net-generator.rules rules file.
#
# You can modify it, as long as you keep each rule on a single
# line, and change only the value of the NAME= key.
# PCI device 0x8086:0x10f5 (e1000e)
SUBSYSTEM==net, ACTION==add, DRIVERS==?*,
ATTR{address}==00:1f:16:0b:47:4d, ATTR{dev_id}==0x0, ATTR{type}==1,
KERNEL==eth*, NAME=eth0
# PCI device 0x8086:0x10f5 (e1000e)
SUBSYSTEM==net, ACTION==add, DRIVERS==?*,
ATTR{address}==00:1f:16:0b:47:4d, ATTR{dev_id}==0x0, ATTR{type}==1,
KERNEL==eth*, NAME=eth1
As this have not happend to me every time, I have tried to figure out
what is special about this setup, but do not know the udev stuff enough
to have a clue. I do notice this part in the log, which seem to be
related:
Oct 16 10:51:35 main-menu[186]: INFO: Menu item 'ethdetect' selected
Oct 16 10:51:35 kernel: [2.532038] usb 2-2: new full-speed USB device
number 3 using uhci_hcd
Oct 16 10:51:35 net/hw-detect.hotplug: Detected hotpluggable network interface
lo
Oct 16 10:51:35 net/hw-detect.hotplug: Detected hotpluggable network interface
eth1
Oct 16 10:51:35 kernel: [2.620227] systemd-udevd[51]: renamed network
interface eth0 to eth1
Oct 16 10:51:35 kernel: [2.636070] Switched to clocksource tsc
Oct 16 10:51:35 kernel: [2.707037] usb 2-2: New USB device found,
idVendor=0a5c, idProduct=2145
Oct 16 10:51:35 kernel: [2.707039] usb 2-2: New USB device strings: Mfr=1,
Product=2, SerialNumber=0
Oct 16 10:51:35 kernel: [2.707042] usb 2-2: Product: ThinkPad Bluetooth
with Enhanced Data Rate II
Oct 16 10:51:35 kernel: [2.707043] usb 2-2: Manufacturer: Lenovo Computer
Corp
Oct 16 10:51:35 hw-detect: Detected module 'usb-storage' for 'USB storage'
Notice how eth0 was renamed to eth1 by udev while hw-detect version
1.104 was running. Any clue what is going wrong here?
--
Happy hacking
Petter Reinholdtsen
---End Message---
---BeginMessage---
Source: systemd
Source-Version: 219-10
We believe that the bug you reported is fixed in the latest version of
systemd, which is due to be installed in the Debian FTP archive.
A summary of the changes between this version and the previous one is
attached.
Thank you for reporting the bug, which will now be closed. If you
have further comments please address them to 765...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Martin Pitt mp...@debian.org (supplier of updated systemd package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Format: 1.8
Date: Thu, 21 May 2015 09:43:52 +0200
Source: systemd
Binary: systemd systemd-sysv libpam-systemd libsystemd0 libsystemd-dev
libsystemd-login-dev libsystemd-daemon-dev libsystemd-journal-dev
libsystemd-id128-dev udev libudev1 libudev-dev udev-udeb libudev1-udeb
libgudev-1.0-0 gir1.2-gudev-1.0 libgudev-1.0-dev python3-systemd systemd-dbg
Architecture: source amd64
Version: 219-10
Distribution: experimental
Urgency: medium
Maintainer: Debian systemd Maintainers
pkg-systemd-maintain...@lists.alioth.debian.org
Changed-By: Martin Pitt mp...@debian.org
Description:
gir1.2-gudev-1.0 - libgudev-1.0 introspection data
libgudev-1.0-0 - GObject-based wrapper
Bug#777126: marked as done (udev: duplicate eth? entries)
Your message dated Thu, 21 May 2015 09:39:47 +
with message-id e1yvmx9-0004vw...@franck.debian.org
and subject line Bug#765577: fixed in systemd 219-10
has caused the Debian Bug report #765577,
regarding udev: duplicate eth? entries
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
765577: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=765577
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
---BeginMessage---
Package: udev
Version: 215-10
Severity: minor
Dear Maintainer,
I did a PXE installation of Jessie on a machine that has only one NIC and got
the following two entries in /etc/udev/rules.d/70-persistent-net.rules:
# PCI device 0x8086:0x109a (e1000e)
SUBSYSTEM==net, ACTION==add, DRIVERS==?*,
ATTR{address}==00:1f:e2:03:d5:12, ATTR{dev_id}==0x0, ATTR{type}==1,
KERNEL==eth*, NAME=eth0
# PCI device 0x8086:0x109a (e1000e)
SUBSYSTEM==net, ACTION==add, DRIVERS==?*,
ATTR{address}==00:1f:e2:03:d5:12, ATTR{dev_id}==0x0, ATTR{type}==1,
KERNEL==eth*, NAME=eth1
The only difference between these two lines is the name.
/etc/network/interfaces says:
allow-hotplug eth1
iface eth1 inet dhcp
but eth0 does not appear.
I guess, that these duplicate lines with almost identical content are not
intended. Nevertheless, networking works ok.
Btw. Wheezy on the same machine has only eth0 like the first line above.
-- Package-specific info:
-- System Information:
Debian Release: 8.0
APT prefers testing
APT policy: (500, 'testing')
Architecture: i386 (i686)
Kernel: Linux 3.16.0-4-686-pae (SMP w/2 CPU cores)
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
Versions of packages udev depends on:
ii adduser3.113+nmu3
ii debconf [debconf-2.0] 1.5.55
ii libacl12.2.52-2
ii libblkid1 2.25.2-4.1
ii libc6 2.19-13
ii libkmod2 18-3
ii libselinux12.3-2
ii libudev1 215-10
ii lsb-base 4.1+Debian13+nmu1
ii procps 2:3.3.9-8
ii util-linux 2.25.2-4.1
udev recommends no packages.
udev suggests no packages.
-- debconf information:
udev/new_kernel_needed: false
udev/reboot_needed:
udev/sysfs_deprecated_incompatibility:
udev/title/upgrade:
P: /devices/LNXSYSTM:00
E: DEVPATH=/devices/LNXSYSTM:00
E: MODALIAS=acpi:LNXSYSTM:
E: SUBSYSTEM=acpi
P: /devices/LNXSYSTM:00/LNXCPU:00
E: DEVPATH=/devices/LNXSYSTM:00/LNXCPU:00
E: MODALIAS=acpi:LNXCPU:
E: SUBSYSTEM=acpi
P: /devices/LNXSYSTM:00/LNXCPU:01
E: DEVPATH=/devices/LNXSYSTM:00/LNXCPU:01
E: MODALIAS=acpi:LNXCPU:
E: SUBSYSTEM=acpi
P: /devices/LNXSYSTM:00/LNXCPU:02
E: DEVPATH=/devices/LNXSYSTM:00/LNXCPU:02
E: MODALIAS=acpi:LNXCPU:
E: SUBSYSTEM=acpi
P: /devices/LNXSYSTM:00/LNXCPU:03
E: DEVPATH=/devices/LNXSYSTM:00/LNXCPU:03
E: MODALIAS=acpi:LNXCPU:
E: SUBSYSTEM=acpi
P: /devices/LNXSYSTM:00/LNXPWRBN:00
E: DEVPATH=/devices/LNXSYSTM:00/LNXPWRBN:00
E: DRIVER=button
E: MODALIAS=acpi:LNXPWRBN:
E: SUBSYSTEM=acpi
P: /devices/LNXSYSTM:00/LNXPWRBN:00/input/input6
E: DEVPATH=/devices/LNXSYSTM:00/LNXPWRBN:00/input/input6
E: EV=3
E: ID_FOR_SEAT=input-acpi-LNXPWRBN_00
E: ID_INPUT=1
E: ID_INPUT_KEY=1
E: ID_PATH=acpi-LNXPWRBN:00
E: ID_PATH_TAG=acpi-LNXPWRBN_00
E: KEY=10 0 0 0
E: MODALIAS=input:b0019vp0001e-e0,1,k74,ramlsfw
E: NAME=Power Button
E: PHYS=LNXPWRBN/button/input0
E: PRODUCT=19/0/1/0
E: PROP=0
E: SUBSYSTEM=input
E: TAGS=:seat:
E: USEC_INITIALIZED=55626
P: /devices/LNXSYSTM:00/LNXPWRBN:00/input/input6/event4
N: input/event4
E: BACKSPACE=guess
E: DEVNAME=/dev/input/event4
E: DEVPATH=/devices/LNXSYSTM:00/LNXPWRBN:00/input/input6/event4
E: ID_INPUT=1
E: ID_INPUT_KEY=1
E: ID_PATH=acpi-LNXPWRBN:00
E: ID_PATH_TAG=acpi-LNXPWRBN_00
E: MAJOR=13
E: MINOR=68
E: SUBSYSTEM=input
E: TAGS=:power-switch:
E: USEC_INITIALIZED=82518
E: XKBLAYOUT=de
E: XKBMODEL=pc105
P: /devices/LNXSYSTM:00/LNXSYBUS:00
E: DEVPATH=/devices/LNXSYSTM:00/LNXSYBUS:00
E: MODALIAS=acpi:LNXSYBUS:
E: SUBSYSTEM=acpi
P: /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00
E: DEVPATH=/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00
E: MODALIAS=acpi:PNP0A08:PNP0A03:
E: SUBSYSTEM=acpi
P: /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/PNP0C01:00
E: DEVPATH=/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/PNP0C01:00
E: MODALIAS=acpi:PNP0C01:
E: SUBSYSTEM=acpi
P: /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/PNP0C02:04
E: DEVPATH=/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/PNP0C02:04
E: MODALIAS=acpi:PNP0C02:
E: SUBSYSTEM=acpi
P: /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/device:00
E:
Processed: Re: ncurses FTBFS: configure loops
Processing control commands: tags -1 - moreinfo Bug #786436 [src:ncurses] ncurses FTBFS: configure loops Removed tag(s) moreinfo. severity -1 serious Bug #786436 [src:ncurses] ncurses FTBFS: configure loops Severity set to 'serious' from 'normal' -- 786436: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=786436 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#785150: marked as done (fglrx-modules-dkms: the module fail to build with linux 4.0.0-1-amd64)
Your message dated Thu, 21 May 2015 18:34:52 + with message-id e1yvviy-0001ku...@franck.debian.org and subject line Bug#785150: fixed in fglrx-driver 1:14.12-2 has caused the Debian Bug report #785150, regarding fglrx-modules-dkms: the module fail to build with linux 4.0.0-1-amd64 to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 785150: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=785150 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: fglrx-modules-dkms Version: 1:14.9+ga14.201-2 Severity: grave When building the module for linux 4.0.0-1-amd64 dkms fail with: DKMS make.log for fglrx-14.12 for kernel 4.0.0-1-amd64 (x86_64) mardi 12 mai 2015, 21:50:46 (UTC+0200) make: Entering directory '/usr/src/linux-headers-4.0.0-1-amd64' LD /var/lib/dkms/fglrx/14.12/build/built-in.o CC [M] /var/lib/dkms/fglrx/14.12/build/firegl_public.o /var/lib/dkms/fglrx/14.12/build/firegl_public.c: In function ‘kcl_mem_pat_setup’: /var/lib/dkms/fglrx/14.12/build/firegl_public.c:4471:9: error: implicit declaration of function ‘read_cr4’ [-Werror=implicit-function-declaration] cr4 = read_cr4(); ^ /var/lib/dkms/fglrx/14.12/build/firegl_public.c:4472:9: error: implicit declaration of function ‘write_cr4’ [-Werror=implicit-function-declaration] write_cr4(cr4 ~X86_CR4_PGE); ^ /var/lib/dkms/fglrx/14.12/build/firegl_public.c: In function ‘kasSetExecutionLevel’: /var/lib/dkms/fglrx/14.12/build/firegl_public.c:4819:5: error: implicit declaration of function ‘__get_cpu_var’ [-Werror=implicit-function-declaration] orig_level = __get_cpu_var(kasExecutionLevel); ^ /var/lib/dkms/fglrx/14.12/build/firegl_public.c:4820:38: error: lvalue required as left operand of assignment __get_cpu_var(kasExecutionLevel) = level; ^ /var/lib/dkms/fglrx/14.12/build/firegl_public.c: At top level: /var/lib/dkms/fglrx/14.12/build/firegl_public.c:6396:12: warning: ‘KCL_fpu_save_init’ defined but not used [-Wunused-function] static int KCL_fpu_save_init(struct task_struct *tsk) ^ cc1: some warnings being treated as errors /usr/src/linux-headers-4.0.0-1-common/scripts/Makefile.build:263: recipe for target '/var/lib/dkms/fglrx/14.12/build/firegl_public.o' failed make[3]: *** [/var/lib/dkms/fglrx/14.12/build/firegl_public.o] Error 1 /usr/src/linux-headers-4.0.0-1-common/Makefile:1407: recipe for target '_module_/var/lib/dkms/fglrx/14.12/build' failed make[2]: *** [_module_/var/lib/dkms/fglrx/14.12/build] Error 2 Makefile:145: recipe for target 'sub-make' failed make[1]: *** [sub-make] Error 2 Makefile:8: recipe for target 'all' failed make: *** [all] Error 2 make: Leaving directory '/usr/src/linux-headers-4.0.0-1-amd64' DKMS make.log for fglrx-14.12 for kernel 4.0.0-1-amd64 (x86_64) mardi 12 mai 2015, 21:50:46 (UTC+0200) make: Entering directory '/usr/src/linux-headers-4.0.0-1-amd64' LD /var/lib/dkms/fglrx/14.12/build/built-in.o CC [M] /var/lib/dkms/fglrx/14.12/build/firegl_public.o /var/lib/dkms/fglrx/14.12/build/firegl_public.c: In function ‘kcl_mem_pat_setup’: /var/lib/dkms/fglrx/14.12/build/firegl_public.c:4471:9: error: implicit declaration of function ‘read_cr4’ [-Werror=implicit-function-declaration] cr4 = read_cr4(); ^ /var/lib/dkms/fglrx/14.12/build/firegl_public.c:4472:9: error: implicit declaration of function ‘write_cr4’ [-Werror=implicit-function-declaration] write_cr4(cr4 ~X86_CR4_PGE); ^ /var/lib/dkms/fglrx/14.12/build/firegl_public.c: In function ‘kasSetExecutionLevel’: /var/lib/dkms/fglrx/14.12/build/firegl_public.c:4819:5: error: implicit declaration of function ‘__get_cpu_var’ [-Werror=implicit-function-declaration] orig_level = __get_cpu_var(kasExecutionLevel); ^ /var/lib/dkms/fglrx/14.12/build/firegl_public.c:4820:38: error: lvalue required as left operand of assignment __get_cpu_var(kasExecutionLevel) = level; ^ /var/lib/dkms/fglrx/14.12/build/firegl_public.c: At top level: /var/lib/dkms/fglrx/14.12/build/firegl_public.c:6396:12: warning: ‘KCL_fpu_save_init’ defined but not used [-Wunused-function] static int KCL_fpu_save_init(struct task_struct *tsk) ^ cc1: some warnings being treated as errors /usr/src/linux-headers-4.0.0-1-common/scripts/Makefile.build:263: recipe for target '/var/lib/dkms/fglrx/14.12/build/firegl_public.o' failed make[3]: *** [/var/lib/dkms/fglrx/14.12/build/firegl_public.o] Error 1 /usr/src/linux-headers-4.0.0-1-common/Makefile:1407: recipe for target
Bug#786439: marked as done (fuse: CVE-2015-3202)
Your message dated Thu, 21 May 2015 18:19:18 + with message-id e1yvv3u-0006z1...@franck.debian.org and subject line Bug#786439: fixed in fuse 2.9.3-16 has caused the Debian Bug report #786439, regarding fuse: CVE-2015-3202 to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 786439: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=786439 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Source: fuse Version: 2.9.0-1 Severity: grave Tags: security upstream Justification: user security hole Control: fixed -1 2.9.0-2+deb7u2 Hi See https://marc.info/?l=oss-securitym=143222736930704w=2 for details. Updated packages for wheezy-security and jessie-security were just released as DSA-3266-1. Regards, Salvatore ---End Message--- ---BeginMessage--- Source: fuse Source-Version: 2.9.3-16 We believe that the bug you reported is fixed in the latest version of fuse, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 786...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Laszlo Boszormenyi (GCS) g...@debian.org (supplier of updated fuse package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Thu, 21 May 2015 17:22:33 + Source: fuse Binary: fuse fuse-dbg libfuse2 libfuse-dev fuse-udeb libfuse2-udeb Architecture: source amd64 Version: 2.9.3-16 Distribution: unstable Urgency: high Maintainer: Laszlo Boszormenyi (GCS) g...@debian.org Changed-By: Laszlo Boszormenyi (GCS) g...@debian.org Description: fuse - Filesystem in Userspace fuse-dbg - Filesystem in Userspace (debug) fuse-udeb - Filesystem in Userspace (udeb) libfuse-dev - Filesystem in Userspace (development) libfuse2 - Filesystem in Userspace (library) libfuse2-udeb - Filesystem in Userspace (library) (udeb) Closes: 786439 Changes: fuse (2.9.3-16) unstable; urgency=high . * Sync with Ubuntu. * Update Standards-Version to 3.9.6 . . [ Marc Deslauriers marc.deslauri...@ubuntu.com ] * SECURITY UPDATE: privilege escalation via insecure environment - debian/patches/CVE-2015-3202.patch: use execle to run external helpers in lib/mount_util.c, util/mount_util.c. - CVE-2015-3202 (closes: #786439). Checksums-Sha1: 3012923cd92596d4b115e6b847b253b0af22a09a 2097 fuse_2.9.3-16.dsc 7a8b88d9456947f5969bfbbbf2476b67cd125cec 17428 fuse_2.9.3-16.debian.tar.xz f2404a3eb0822631fad8cc17b1f30d84c40b472c 309558 fuse-dbg_2.9.3-16_amd64.deb b222a2b598e8765c7c832483e62fc17df93fee47 14520 fuse-udeb_2.9.3-16_amd64.udeb dbfe1ba4ccad40a69ff5fbd91e49fb5ba98c91cc 70580 fuse_2.9.3-16_amd64.deb cd8a750be36887deb8b0480c097818cbb2d5f7f3 149866 libfuse-dev_2.9.3-16_amd64.deb 5bf3fcd144257d4eb0a6c88cd4f87a86374f06c6 66598 libfuse2-udeb_2.9.3-16_amd64.udeb 500c97afdb76e52a0220fbcbfef99845cfb9962d 134708 libfuse2_2.9.3-16_amd64.deb Checksums-Sha256: adcec01bc376c36c0dd2d138eb88287810a56094f01c1d6b4a669378b32c9b20 2097 fuse_2.9.3-16.dsc 67a0dc508d1dc0e27e6be5f929c9951fb1cf00be2f972db62983f40bff216072 17428 fuse_2.9.3-16.debian.tar.xz 5dd247ae1a0c1bc4c4149fc6460ac62362bbd81833f14a49d8da0634b2a97a78 309558 fuse-dbg_2.9.3-16_amd64.deb 9b3ef23787f034156f4566a5060f6c74cb4f51571cbd5fa881da08dfd0b10245 14520 fuse-udeb_2.9.3-16_amd64.udeb 2eb95f50058e54bbb6a98ca39198a8f5ea1b231701e1f3b067feb4f54c55 70580 fuse_2.9.3-16_amd64.deb bac80b3f11bdcbb6363eac71d9628e27ca8014bbcde2b44855807c41ead7ca43 149866 libfuse-dev_2.9.3-16_amd64.deb f4af9ea594caad76bc78bca7e78c2968d66d1fa11b61c74a02cf72b92165fd37 66598 libfuse2-udeb_2.9.3-16_amd64.udeb 2f079d57c56ef09de20d85e718148d5aa93f402dbc4a1557d189d1b7365484ae 134708 libfuse2_2.9.3-16_amd64.deb Files: 3f58f54597c4be935e1e3971f04ffe38 2097 utils optional fuse_2.9.3-16.dsc 6e6d96b16c754ad0167f63f24ed7635d 17428 utils optional fuse_2.9.3-16.debian.tar.xz 2a9fbbe849f1220e9948c3d21127f572 309558 debug extra fuse-dbg_2.9.3-16_amd64.deb a292e7e7f657bfd975fc0ddbe46676ca 14520 debian-installer optional fuse-udeb_2.9.3-16_amd64.udeb ad61efcc1b3ba4256485ce195d063208 70580 utils optional fuse_2.9.3-16_amd64.deb 859c2a2cd6cfebec831f83dc2bc35d49 149866 libdevel optional libfuse-dev_2.9.3-16_amd64.deb
Bug#786442: some lines don't appear in some messages
Package: squirrelmail Version: 2:1.4.23~svn20120406-2 Severity: grave Below is a message that doesn't display in squirrelmail; Its single line doesn't appear. When clicking reply it appears quoted, as it should. This is a serious bug. The configuration in config_local.php is ?php $squirrelmail_default_language = 'pt_BR'; $default_charset = 'utf-8'; $lossy_encoding = true; Here's the message. To make sure the bug is visible and not dependent on other messages I put it in a separate folder. From sender ommited Tue May 19 22:48:53 2015 Date: Tue, 19 May 2015 22:48:53 -0300 From: sender ommited To: receiver ommited Subject: Re: primeiras frases ocultas dos emails Message-ID: 20150520014853.ga8...@fisica.ufpr.br References: 7799688da0e98b71bc8f76a9bcc91061.squir...@fisica.ufpr.br 20150518205619.ga11...@fisica.ufpr.br 2733d37cf1348e4a8f698809dba26976.squir...@fisica.ufpr.br MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: 2733d37cf1348e4a8f698809dba26976.squir...@fisica.ufpr.br User-Agent: Mutt/1.5.23 (2014-03-12) Status: RO Content-Length: 79 Lines: 1 X-IMAPbase: 143528 01 X-UID: 1 Venha na 4a. � tarde. Tamb�m pode mandar a mensagem p/ mim para eu ir olhando. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#784711: wmaker: diff for NMU version 0.95.6-1.1
Control: tags 784711 + patch
Control: tags 784711 + pending
Dear maintainer,
I've prepared an NMU for wmaker (versioned as 0.95.6-1.1) and
have asked my sponsor to upload it to DELAYED/2. Please feel
free to tell me if I should delay it longer.
Regards.
diff -Nru wmaker-0.95.6/debian/changelog wmaker-0.95.6/debian/changelog
--- wmaker-0.95.6/debian/changelog 2014-10-31 07:12:59.0 -0500
+++ wmaker-0.95.6/debian/changelog 2015-05-21 13:34:40.0 -0500
@@ -1,3 +1,12 @@
+wmaker (0.95.6-1.1) unstable; urgency=medium
+
+ * Non-maintainer upload.
+ * debian/control:
+- Add Breaks/Replaces for libwraster3-dev; remove Provides for
+ libwraster-dev (Closes: #784711).
+
+ -- Doug Torrance dtorra...@monmouthcollege.edu Thu, 21 May 2015 13:34:40 -0500
+
wmaker (0.95.6-1) unstable; urgency=medium
* New upstream version 0.95.6. [Closes: #148856]
diff -Nru wmaker-0.95.6/debian/control wmaker-0.95.6/debian/control
--- wmaker-0.95.6/debian/control 2014-10-31 04:05:38.0 -0500
+++ wmaker-0.95.6/debian/control 2015-05-21 13:28:12.0 -0500
@@ -45,7 +45,8 @@
Depends: libwraster5 (= ${binary:Version}), libc6-dev, libx11-dev,
libxext-dev, libxpm-dev, libjpeg-dev, libpng-dev, libgif-dev,
libtiff5-dev, ${misc:Depends}
-Provides: libwraster-dev
+Breaks: libwraster3-dev
+Replaces: libwraster3-dev
Description: Static libraries and headers of Window Maker rasterizer
This library is used to manipulate images and convert them to
a format that can be displayed through the X window system.
Processed: wmaker: diff for NMU version 0.95.6-1.1
Processing control commands: tags 784711 + patch Bug #784711 [libwraster-dev] libwraster-dev: Fails to install due to file conflict with libwraster3-dev Added tag(s) patch. tags 784711 + pending Bug #784711 [libwraster-dev] libwraster-dev: Fails to install due to file conflict with libwraster3-dev Added tag(s) pending. -- 784711: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=784711 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#785429: icedove: FTBFS with new libvpx 1.4
On 16/05/15 21:25, Carsten Schoenert wrote: tags 785429 +patch +pending thanks Hello Emilio, On Sat, May 16, 2015 at 08:55:38AM +0200, Emilio Pozuelo Monfort wrote: Package: icedove Version: 31.6.0-1 Severity: serious On a binNMU for the libvpx transition, your package failed to build with: ... [cut] See https://buildd.debian.org/status/fetch.php?pkg=icedovearch=amd64ver=31.6.0-1%2Bb1stamp=1431713936 These constants are now called VPX_*. thanks for pointing to the fix. I created a patch and added to this mail which hopefully works on all plaforms. Localy it works on amd64. Christoph is planning to upload the new released version 31.7.0 after the weekend to unstable, stable-security and old-stable-security.. I see this has been uploaded to stable and oldstable. Any ETA for an unstable upload? Thanks, Emilio -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#786417: openjdk-8: FTBFS: *** This OS is not supported: Linux … 4.0.0-1-amd64 …
Source: openjdk-8 Version: 8u45-b14-3 Severity: serious Justification: fails to build from source (but built successfully in the past) Trying to rebuild it in a wheezy chroot (probably also fails in sid). make[6]: Entering directory `/tmp/openjdk-8-8u45-b14/build/hotspot' 2 echo *** This OS is not supported: `uname -a`; exit 1; *** This OS is not supported: Linux tglase.lan.tarent.de 4.0.0-1-amd64 #1 SMP Debian 4.0.2-1 (2015-05-11) x86_64 GNU/Linux Prefixing the dpkg-buildpackage call with “linux64 --uname-2.6” makes it work. And yes, I agree, this is among *the* most idiotic things in Linux recently – and even less published than the 3.0 jump, even less useful, even less tested, etc. -- System Information: Debian Release: stretch/sid APT prefers unreleased APT policy: (500, 'unreleased'), (500, 'buildd-unstable'), (500, 'unstable') Architecture: x32 (x86_64) Foreign Architectures: i386, amd64 Kernel: Linux 4.0.0-1-amd64 (SMP w/4 CPU cores) Locale: LANG=C, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/lksh Init: sysvinit (via /sbin/init) -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#785073: marked as done (ruby-d3-rails: not installable in sid)
Your message dated Thu, 21 May 2015 18:09:47 +0530 with message-id 555dd213.6080...@autistici.org and subject line Fixed in latest update of libjs-d3 has caused the Debian Bug report #785073, regarding ruby-d3-rails: not installable in sid to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 785073: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=785073 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: ruby-d3-rails Version: 3.5.5+dfsg-1 Severity: serious User: trei...@debian.org Usertags: edos-uninstallable Hi, ruby-d3-rails is not installable in sid, since 2015-03-30. It depends on libjs-d3 (= 3.5.5) which currently only exists in experimental. Cheers -Ralf. ---End Message--- ---BeginMessage--- -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 This issue is resolved by the latest update of libjs-d3. The version 3.5.5 was previously uploaded to experimental due to Jessie freeze. Now, it is re-uploaded to unstable, and hence resolves this issue. Thanks Laszlo for the upload. - -- Regards Balasankar C http://balasankarc.in -BEGIN PGP SIGNATURE- Version: GnuPG v1 iQEcBAEBCgAGBQJVXdITAAoJEJbtq5sua3FxZyEH/3Stfd+ZCmxdqOPPLbYRg8ks Q1gVwTyxx6IeKow2BJTjoliELEPJB0YWmKhn/A5nmfJtbLr/9m11+JkYsELHYy6K Xx+g+CktRtb9EtnUVI0nh9G4Ach+cahWa8wgKltEuID1YonYQVCgBjjWrzVXtagr N5UsF0x/YxYvyQ9yC9g68GysXZqahKvqsnyp5hkOy4aTPh+fe1X3RsLjELX85DHD u4pENAQ756fusw71jm0yieYovkcQ+xusCXvuhMCLURTiB9Akr6mcQR/9YH9xyv7w vOTul5ZObyjND1GeiCVH7ukxffeYdMYcpbv2ZvSU9U1bWbJ11SkfW0anRBbr6g0= =o5r9 -END PGP SIGNATURE- 0x2E6B7171.asc Description: application/pgp-keys ---End Message---
Bug#765120: Fwd: Re: [pkg-cli-libs-team] Bug#765120: monogame: support monodevelop 5
You're right, I haven't seen this discussion. I think the downsides to dropping are lower than they used to be - the MD addin is available from the MD addin repository, MG is in NuGet. I think maintaining an ancient Tao/OpenTK forever is sorta dumb, though. I'm open to spending some time on getting the dep chain updated, but I want a modern MD (5.9 is current) in the archive to work against, which targets Mono 4, so we'd need that. On 21/05/15 11:50, Mirco Bauer wrote: Not sure if you have received this. Whats your opinion on this? -- Weitergeleitete Nachricht -- Von: Mirco Bauer mee...@debian.org mailto:mee...@debian.org Datum: 21.05.2015 12:46 Betreff: Re: [pkg-cli-libs-team] Bug#765120: monogame: support monodevelop 5 An: Emilio Pozuelo Monfort po...@debian.org mailto:po...@debian.org, 765...@bugs.debian.org mailto:765...@bugs.debian.org Cc: 765120-ma...@bugs.debian.org mailto:765120-ma...@bugs.debian.org Am 20.05.2015 15:41 schrieb Emilio Pozuelo Monfort po...@debian.org mailto:po...@debian.org: On Mon, 08 Dec 2014 16:09:54 +1100 Christopher James Halse Rogers r...@ubuntu.com mailto:r...@ubuntu.com wrote: Package: monogame Followup-For: Bug #765120 Alright. So, monogame 2.5.1 (from 2012) doesn't build at all against Monodevelop 5. A new upstream version, Monogame 3.2, doesn't build against the version of tao-framework in Jessie (also from 2012, project deprecated in favour of libopentk, for which Jessie also has a 2012 snapshot). It's probably time to either start maintaining these or drop them from the archive. So what's it gonna be? This has been blocking monodevelop from migrating for a long time: monodevelop (4.0.12+dfsg-6 to 5.5.0.227-1) Maintainer: Debian CLI Applications Team 222 days old (needed 5 days) Ouch, if monogame is this problematic then monodevelop should either drop the monogame build-dep or monodevelop needs a source pkg just for monogame so it doesn't block transitions. Emilio ___ pkg-cli-libs-team mailing list pkg-cli-libs-t...@lists.alioth.debian.org mailto:pkg-cli-libs-t...@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-cli-libs-team
Bug#750743: gspiceui: Please update to use wxwidgets3.0
Hi Olly Thanks a lot again. I did apply your patch but I still get the lintian warning I: gspiceui: hardening-no-fortify-functions usr/bin/gspiceui If you are willing to upload the package with this warning then I will do the final preparation for an upload or if you know how to fix this please tell me. The package can be found on my server or in the debian-science svn repository. svn://anonscm.debian.org/debian-science/packages/gspiceui/trunk/ Regards Gudjon -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: Re: moonshot-ui: depends on libgee-dev which is deprecated
Processing control commands: severity -1 serious Bug #784651 [src:moonshot-ui] moonshot-ui: depends on libgee-dev which is deprecated Severity set to 'serious' from 'important' -- 784651: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=784651 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#753861: gnome-dvb-daemon: depends on libgee2 which is deprecated
Control: severity -1 serious Bumping the severity to serious as we're going to drop libgee2 soon. Emilio -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: Re: lekhonee-gnome: depends on libgee2 which is deprecated
Processing control commands: severity -1 serious Bug #753868 [src:lekhonee-gnome] lekhonee-gnome: depends on libgee2 which is deprecated Severity set to 'serious' from 'important' -- 753868: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=753868 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: Re: steadyflow: depends on libgee2 which is deprecated
Processing control commands: severity -1 serious Bug #753879 [src:steadyflow] steadyflow: depends on libgee2 which is deprecated Severity set to 'serious' from 'important' -- 753879: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=753879 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#784651: moonshot-ui: depends on libgee-dev which is deprecated
Ah, and I see you did actually file the removal request, so yeah this is RC under any evaluation. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#784651: moonshot-ui: depends on libgee-dev which is deprecated
Emilio == Emilio Pozuelo Monfort po...@debian.org writes: Emilio Control: severity -1 serious We want to remove libgee2 from Emilio unstable RSN, and there are only a few rdeps now, so I'm Emilio bumping the severity of the bugs. For future reference, I don't think it's actually legitimate to bump the severity of an rdep removal to RC until *after* you remove the rdep. However, as maintainer, I'll say this is fine as serious by request of maintainer. I don't think this is a problem, I just need to rebuild and upload. I'll try to get to that in a day or two. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#783890: [Pkg-sugar-devel] Bug#783890: Solution for conflicting svg file
On Thu, May 21, 2015 at 4:03 PM, Jonas Smedegaard d...@jones.dk wrote: Quoting Martin Abente (2015-05-21 21:23:59) By having the application-x-squeak-project.svg file in ./activity/ directory, the setup.py install step will create a symlink to that file in /usr/share/ icons/sugar/scalable/mimetypes/, in order to install that file as the icon for a custom mime type declared in ./activty/activity.info. Thanks for the analysis. That same mime type icon is already provided by sugar-artwork (sugar-icon-theme), so there is no need for Etoys to provide this icon. I have contacted the upstream maintainer, but for the time being I recommend to remove the icon with a patch in debian/patches. I have attached to this reply the patch for https://anonscm.debian.org/cgit/pkg-sugar/sugar-etoys-activity.git/ to do so. While it might be the best approach upstream to remove the SVG file (when possible to ensure that sugar-icon-theme provides it), a smaller workaround in Debian packaging is to remove the file after it is installed, with something like this in debian/rules: # avoid SVG file already included in sugar-*-icon-theme install/$(pkg):: rm $(cdbs_curdestdir)usr/share/icons/sugar/scalable/mimetypes/application-x-squeak-project.svg (Order is ensured because CDBS per-binary-package install/* targets are run after common install target.) looks ok to me, but it really doesn't make much sense to have different modules/activities providing the same files. ...but, given your analysis, I suspect an even simpler workaround is to build-depend on sugar-*-icon-theme to not have the symlink generated at all. I will test that now... (...and I will also try patch sugar-toolkit-gtk3 to create relative symlinks, as they currently reference a path specific to the build environment build home). +1 These [1] are the bits you might be interested in looking. I am working on a related patch to prevent update-mime-database from running while we are building the packages [2] (a related problem). Refs: 1. https://github.com/sugarlabs/sugar-toolkit-gtk3/blob/master/src/sugar3/bundle/activitybundle.py#L331 2. https://github.com/tchx84/sugar-toolkit-gtk3/commit/a92b61d6d213cec74485b5dd5aa11acc3a72732b - Jonas -- * Jonas Smedegaard - idealist Internet-arkitekt * Tlf.: +45 40843136 Website: http://dr.jones.dk/ [x] quote me freely [ ] ask before reusing [ ] keep private
Bug#784651: marked as done (moonshot-ui: depends on libgee-dev which is deprecated)
Your message dated Thu, 21 May 2015 21:37:18 + with message-id e1yvy9w-8c...@franck.debian.org and subject line Bug#784651: fixed in moonshot-ui 0.7.1-3 has caused the Debian Bug report #784651, regarding moonshot-ui: depends on libgee-dev which is deprecated to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 784651: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=784651 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Source: moonshot-ui Version: 0.7.1-1 Severity: important User: pkg-vala-maintain...@lists.alioth.debian.org Usertags: oldlibs libgee-0.6 src:moonshot-ui build-depends on libgee-dev (libgee2). which is deprecated in favor of libgee-0.8-dev (libgee-0.8-2). Please test your package against the new libgee and update to it. The plan is to request the removal of libgee2 in about two months. It would be great if you can update the package by then. Thanks, Michael -- System Information: Debian Release: stretch/sid APT prefers unstable APT policy: (500, 'unstable'), (200, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.16.0-4-amd64 (SMP w/4 CPU cores) Locale: LANG=de_DE.utf8, LC_CTYPE=de_DE.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) ---End Message--- ---BeginMessage--- Source: moonshot-ui Source-Version: 0.7.1-3 We believe that the bug you reported is fixed in the latest version of moonshot-ui, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 784...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Sam Hartman hartm...@debian.org (supplier of updated moonshot-ui package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Thu, 21 May 2015 16:14:24 -0400 Source: moonshot-ui Binary: moonshot-ui moonshot-ui-dbg moonshot-ui-dev libmoonshot1 Architecture: source amd64 Version: 0.7.1-3 Distribution: unstable Urgency: medium Maintainer: Sam Hartman hartm...@debian.org Changed-By: Sam Hartman hartm...@debian.org Description: libmoonshot1 - Moonshot Identity Shared Library moonshot-ui - Moonshot Identity Selector moonshot-ui-dbg - Moonshot Identity Selector Debug Symbols moonshot-ui-dev - Moonshot Identity Development Files Closes: 784651 Changes: moonshot-ui (0.7.1-3) unstable; urgency=medium . * Depend on libgee-0.8-dev, Closes: #784651 Checksums-Sha1: 9db1c64007d437730997d1413e41f987ef1714fc 1980 moonshot-ui_0.7.1-3.dsc 184c5e06aa86625ddd87318795a82e4c16e0355c 38840 moonshot-ui_0.7.1-3.debian.tar.xz c38691cc349b68b0f3742afddaec8efdc96ee69b 8972 libmoonshot1_0.7.1-3_amd64.deb 1da7960dd36d644af8f690203ee722a8f5f2d229 373438 moonshot-ui-dbg_0.7.1-3_amd64.deb ceddb3025d3a290e16396d0b7615eecb8d55e984 9278 moonshot-ui-dev_0.7.1-3_amd64.deb b74cf6bca1004a9b89feb7c58e8f8f048610bc47 61660 moonshot-ui_0.7.1-3_amd64.deb Checksums-Sha256: 133ef70bc3fbd316602ad9ef26f5e4999f0cf79a48ee2950a8905ef86517424e 1980 moonshot-ui_0.7.1-3.dsc e42b45e120774878535c54a4418732ca0a9e1d76a1bf485c2e5e2a599f198ac1 38840 moonshot-ui_0.7.1-3.debian.tar.xz ed866a2a78f3ba2c4b70e5fa3904037fae1f12415a8de230df3467ca89814ec6 8972 libmoonshot1_0.7.1-3_amd64.deb 69f566f7d9779b3d715c862f48e2a70a6b551ea85d6a28843ccd6b302efa435a 373438 moonshot-ui-dbg_0.7.1-3_amd64.deb 667e7fb2785f9a99fdbcf0115ba98e494a21857f1221f92391faa4c6ffc651cb 9278 moonshot-ui-dev_0.7.1-3_amd64.deb 676cd8f44a931cb7bc9d87f0276fc4c5c62b16b1a51e2efe9e76c10b6808eacf 61660 moonshot-ui_0.7.1-3_amd64.deb Files: bf623536d2bbf8fdccde27ce141e637f 1980 net optional moonshot-ui_0.7.1-3.dsc 52f31a7fe90a8b05baf6a1c1b0f6e682 38840 net optional moonshot-ui_0.7.1-3.debian.tar.xz ab64fcc5665886b32dd9aa2bfba91415 8972 libs optional libmoonshot1_0.7.1-3_amd64.deb 0783c48d043ee61a1f55c33de69d0d98 373438 debug extra moonshot-ui-dbg_0.7.1-3_amd64.deb 77a252b0fc1cba7e8633d30bf46b2eb6 9278 libdevel optional moonshot-ui-dev_0.7.1-3_amd64.deb 559e6b8fdc2657059c823d3664aa80fc 61660 net optional moonshot-ui_0.7.1-3_amd64.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1 iQGIBAEBCAAGBQJVXj/VAAoJEHyaUfYmslafSvgLXiXQ2C/s20WsmPN7x17zKUyC
Processed: subversion Debian ci: r1430 - in src/1.8.x/debian: . patches
Processing commands for cont...@bugs.debian.org: tags 785496 pending Bug #785496 [src:subversion] subversion: FTBFS: Test failure in wc-queries-test Added tag(s) pending. thanks Stopping processing here. Please contact me if you need assistance. -- 785496: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=785496 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#783233: RFS: libapache-mod-jk 1:1.2.40+svn150520-1 [RC]
Control: tags -1 pending Hi, I have prepared a new upstream release of libapache-mod-jk which fixes RC bug #783233, better known as CVE-2014-8111. I would be glad if someone reviewed the package and uploaded it to unstable. https://security-tracker.debian.org/tracker/source-package/libapache-mod-jk https://anonscm.debian.org/viewvc/pkg-java/trunk/libapache-mod-jk/ Version 1.2.41 hasn't been released yet, so I prepared a SVN snapshot. It was discovered that a JkUnmount rule for a subtree of a previous JkMount rule could be ignored. This could allow a remote attacker to potentially access a private artifact in a tree that would otherwise not be accessible to them. The new version adds new JkOptions to the apache2 module mod_jk and disables the unsafe handling of adjacent slashes by default now. The changes can be adjusted in /etc/apache2/mods-available/jk.conf. The patch for fixing this bug is available here: https://svn.apache.org/viewvc?view=revisionrevision=1647017 I intend to prepare further uploads for jessie, wheezy and squeeze, if possible. Changelog: * Team upload. * Imported Upstream SVN snapshot version 1.2.40+svn150520. - Fix CVE-2014-8111: (Closes: #783233) Apache Tomcat Connectors (mod_jk) ignored JkUnmount rules for subtrees of previous JkMount rules, which allows remote attackers to access otherwise restricted artifacts via unspecified vectors. * debian/control: Build-Depend on debhelper = 9. * Remove source.lintian-overrides since we now build-depend on debhelper =9. * Drop 0004-corrupted-worker-activation-status.patch. Fixed upstream. * debian/rules: - Disable sed command in debian/rules. Apparently not necessary for this release. - Run buildconf.sh before dh_auto_configure step since this is a requirement for building SVN snapshots. - Update dh_auto_clean override. Ensure that the package can be built twice in a row. * debian/control: - Add autoconf to Build-Depends. - Add automake to Build-Depends. - Remove Conflicts and Replaces fields because they are obsolete. * Add disable-libtool-check.patch and fix a FTBFS. We already build-depend on libtool but the script is not smart enough. * Add fix-privacy-breach.patch and fix lintian errors about privacy breach logo. * Update debian/copyright information. Add missing BSD-3-clause license. * Add README.source. Regards, Markus signature.asc Description: OpenPGP digital signature
Processed: Re: syncmaildir: depends on libgee2 which is deprecated
Processing control commands: severity -1 serious Bug #753876 [src:syncmaildir] syncmaildir: depends on libgee2 which is deprecated Severity set to 'serious' from 'important' -- 753876: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=753876 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: Re: libgwibber: depends on libgee2 which is deprecated
Processing control commands: severity -1 serious Bug #753869 [src:libgwibber] libgwibber: depends on libgee2 which is deprecated Severity set to 'serious' from 'important' -- 753869: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=753869 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: RFS: libapache-mod-jk 1:1.2.40+svn150520-1 [RC]
Processing control commands: tags -1 pending Bug #783233 [src:libapache-mod-jk] CVE-2014-8111: mod_jk ignores JkUnmount rules for subtrees of previous JkMount rules Added tag(s) pending. -- 783233: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=783233 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#785778: ipsec-tools: null pointer dereference crash in racoon
Hi Noah! On Wed, May 20, 2015 at 10:21:06PM -0700, Noah Meyerhans wrote: On Thu, May 21, 2015 at 06:44:04AM +0200, Salvatore Bonaccorso wrote: Yes indeed we were planning to do so. Have both prepared and were waiting for the CVE assignment. But if none is done we might proceed. I can upload amd64 binary packages for testing exposure to people.d.o. https://people.debian.org/~carnil/tmp/ipsec-tools/ Thanks, I've got the wheezy and jessie builds testing. Seems fine so far. The fix is straightforward so I don't anticipate any issues. has been assigned now a CVE (CVE-2015-4047). http://www.openwall.com/lists/oss-security/2015/05/21/11 Will finish the packaging tomorrow moring and upload to security-master for wheezy-security and jessie-security. Regards, Salvatore -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: retitle 785778 to ipsec-tools: CVE-2015-4047: null pointer dereference crash in racoon
Processing commands for cont...@bugs.debian.org: retitle 785778 ipsec-tools: CVE-2015-4047: null pointer dereference crash in racoon Bug #785778 [src:ipsec-tools] ipsec-tools: null pointer dereference crash in racoon Changed Bug title to 'ipsec-tools: CVE-2015-4047: null pointer dereference crash in racoon' from 'ipsec-tools: null pointer dereference crash in racoon' thanks Stopping processing here. Please contact me if you need assistance. -- 785778: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=785778 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: limit source to moonshot-ui, tagging 784651
Processing commands for cont...@bugs.debian.org: limit source moonshot-ui Limiting to bugs with field 'source' containing at least one of 'moonshot-ui' Limit currently set to 'source':'moonshot-ui' tags 784651 + pending Bug #784651 [src:moonshot-ui] moonshot-ui: depends on libgee-dev which is deprecated Added tag(s) pending. thanks Stopping processing here. Please contact me if you need assistance. -- 784651: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=784651 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#786436: marked as pending
tag 786436 pending
thanks
Hello,
Bug #786436 reported by you has been fixed in the Git repository. You can
see the changelog below, and you can check the diff of the fix at:
http://git.debian.org/?p=collab-maint/ncurses.git;a=commitdiff;h=5b01640
---
commit 5b01640ba34796b6fb60708740f0815da450fb72
Author: Sven Joachim svenj...@gmx.de
Date: Thu May 21 22:58:03 2015 +0200
Temporarily add a build-dependency on libncursesw5-dev
Sadly this is necessary since the package otherwise will FTBFTS with
ncurses-bin 5.9+20150516-1. This build-dependency should be backed
out in a few weeks when it is made sure that no buildd has the broken
ncurses-bin version anymore.
A proper fix would be to use the pkg-config and ncursesw5-config files
from the build tree, but this needs more thought.
diff --git a/debian/changelog b/debian/changelog
index f8646de..0e4f6bf 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -3,6 +3,8 @@ ncurses (5.9+20150516-2) UNRELEASED; urgency=low
* Move the ncurses{w,}5-config scripts back to ncurses-bin
(Closes: #786436, reopens: #745479).
- Readd the dependency of the -dev packages on ncurses-bin.
+- Temporarily add a build-dependency on libncursesw5-dev to
+ avoid the FTBFS problem in #786436.
-- Sven Joachim svenj...@gmx.de Thu, 21 May 2015 22:46:19 +0200
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: Bug#786436 marked as pending
Processing commands for cont...@bugs.debian.org: tag 786436 pending Bug #786436 [src:ncurses] ncurses FTBFS: configure loops Ignoring request to alter tags of bug #786436 to the same tags previously set thanks Stopping processing here. Please contact me if you need assistance. -- 786436: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=786436 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: Bug#786436 marked as pending
Processing commands for cont...@bugs.debian.org: tag 786436 pending Bug #786436 [src:ncurses] ncurses FTBFS: configure loops Added tag(s) pending. thanks Stopping processing here. Please contact me if you need assistance. -- 786436: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=786436 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#786436: marked as pending
tag 786436 pending
thanks
Hello,
Bug #786436 reported by you has been fixed in the Git repository. You can
see the changelog below, and you can check the diff of the fix at:
http://git.debian.org/?p=collab-maint/ncurses.git;a=commitdiff;h=3e1c780
---
commit 3e1c780652b5aa82d5fcbd4b6f47f80a8273c9f5
Author: Sven Joachim svenj...@gmx.de
Date: Thu May 21 22:53:07 2015 +0200
Move the ncurses{w,}5-config scripts back to ncurses-bin
This partly reverts commit e6ce2094446dbc4d79e38186f83d2240dc46cd9e,
adding the necessary Replaces+Breaks stanza in debian/control.
diff --git a/debian/changelog b/debian/changelog
index e2f604a..f8646de 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,11 @@
+ncurses (5.9+20150516-2) UNRELEASED; urgency=low
+
+ * Move the ncurses{w,}5-config scripts back to ncurses-bin
+(Closes: #786436, reopens: #745479).
+- Readd the dependency of the -dev packages on ncurses-bin.
+
+ -- Sven Joachim svenj...@gmx.de Thu, 21 May 2015 22:46:19 +0200
+
ncurses (5.9+20150516-1) unstable; urgency=low
[ Sven Joachim ]
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#786436: ncurses FTBFS: configure loops
Am 21.05.2015 um 21:09 schrieb Helmut Grohne: On Thu, May 21, 2015 at 09:06:24PM +0200, Sven Joachim wrote: Might at least be temporarily necessary anyway until the -config scripts are moved back to ncurses-bin; I'll do that if nobody comes up with a better idea in the next few days. I have no objections to doing this temporarily and no better idea. Can you just do that now? We can still figure out a better solution later. Almost done, just needs to be uploaded (building right now). Cheers, Sven -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: Re: clinica: depends on libgee2 which is deprecated
Processing control commands: severity -1 serious Bug #753854 [src:clinica] clinica: depends on libgee2 which is deprecated Severity set to 'serious' from 'important' -- 753854: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=753854 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: Re: gnome-dvb-daemon: depends on libgee2 which is deprecated
Processing control commands: severity -1 serious Bug #753861 [src:gnome-dvb-daemon] gnome-dvb-daemon: depends on libgee2 which is deprecated Severity set to 'serious' from 'important' -- 753861: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=753861 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: Re: gnome-dvb-daemon: depends on libgee2 which is deprecated
Processing control commands: severity -1 serious Bug #753861 [src:gnome-dvb-daemon] gnome-dvb-daemon: depends on libgee2 which is deprecated Ignoring request to change severity of Bug 753861 to the same value. -- 753861: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=753861 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: Re: diodon: depends on libgee2 which is deprecated
Processing control commands: severity -1 serious Bug #753859 [src:diodon] diodon: depends on libgee2 which is deprecated Severity set to 'serious' from 'important' -- 753859: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=753859 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#783890: [Pkg-sugar-devel] Bug#783890: Solution for conflicting svg file
Quoting Martin Abente (2015-05-21 21:23:59) By having the application-x-squeak-project.svg file in ./activity/ directory, the setup.py install step will create a symlink to that file in /usr/share/ icons/sugar/scalable/mimetypes/, in order to install that file as the icon for a custom mime type declared in ./activty/activity.info. Thanks for the analysis. That same mime type icon is already provided by sugar-artwork (sugar-icon-theme), so there is no need for Etoys to provide this icon. I have contacted the upstream maintainer, but for the time being I recommend to remove the icon with a patch in debian/patches. I have attached to this reply the patch for https://anonscm.debian.org/cgit/pkg-sugar/sugar-etoys-activity.git/ to do so. While it might be the best approach upstream to remove the SVG file (when possible to ensure that sugar-icon-theme provides it), a smaller workaround in Debian packaging is to remove the file after it is installed, with something like this in debian/rules: # avoid SVG file already included in sugar-*-icon-theme install/$(pkg):: rm $(cdbs_curdestdir)usr/share/icons/sugar/scalable/mimetypes/application-x-squeak-project.svg (Order is ensured because CDBS per-binary-package install/* targets are run after common install target.) ...but, given your analysis, I suspect an even simpler workaround is to build-depend on sugar-*-icon-theme to not have the symlink generated at all. I will test that now... (...and I will also try patch sugar-toolkit-gtk3 to create relative symlinks, as they currently reference a path specific to the build environment build home). - 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
Processed: RM: libgee -- ROM; dead upstream, deprecated, replaced by libgee-0.8
Processing control commands: block -1 by 753854 753859 753861 753868 753869 753876 753879 784651 Bug #786454 [ftp.debian.org] RM: libgee -- ROM; dead upstream, deprecated, replaced by libgee-0.8 786454 was not blocked by any bugs. 786454 was not blocking any bugs. Added blocking bug(s) of 786454: 784651, 753861, 753868, 753876, 753869, 753879, 753854, and 753859 -- 786454: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=786454 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#784709: when would blkid success but not filesystem type?
On Thu, May 21, 2015 at 04:24:38PM +0800, Paul Wise wrote: In https://bugs.debian.org/784709 Jérôme Kieffer wrote: Here is the answer for the 3.16 kernel: jerome@patagonia:~$ sudo blkid -o value -s TYPE /dev/sdb4 jerome@patagonia:~$ echo $? 0 ... The output is the same on 3.2, as you can see on attached images. Anyone know when blkid would return success but not the filesystem type? The option '-s' does not affect return code, this option controls output filter only. I have improved the description in the man page to make it more obvious. blkid returns success always when it's possible to gather any information about the device. The important detail is that the recent versions provide also PARTUUID=, so we have information about all (including empty) partitions! For example (very very old version from e2fsprogs): # blkid /dev/sdc1; echo $? 2 but the current util-linux upstream: #blkid /dev/sdc1; echo $? /dev/sdc1: PARTUUID=4b6f59ea-01 0 And yes, we have PARTUUID also for MBR partitions, the method used to generate the UUID is the same like kernel uses for root= command line option. Note that my recommendation is to use lsblk, for example: # lsblk --noheading --output FSTYPE /dev/sda1 vfat it reads info from udev db (libblkid is only fallback here), and it provides better way how to control output. Karel -- Karel Zak k...@redhat.com http://karelzak.blogspot.com -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#784565: [pkg-x2go-devel] Bug#784565: Bug#784565: Bug#784565: Bug#784565: nx-libs-lite: parts are derived from non-free code
Hi, On Mi 20 Mai 2015 20:03:25 CEST, Francesco Poli wrote: o update copyright information in nxcomp/ subfolder o provide some README or such that shortly explains our last weeks' process o this will be for the upcoming 3.6.x release series of nx-libs https://github.com/ArcticaProject/nx-libs/pull/31 I have just my pull request for that against nx-libs. I will wait for another dev (Mihai Moldovan) to look over it and then merge it to the 3.6.x branch of nx-libs. Once merged, I will continue with the Debian package update. Mike -- DAS-NETZWERKTEAM mike gabriel, herweg 7, 24357 fleckeby fon: +49 (1520) 1976 148 GnuPG Key ID 0x25771B31 mail: mike.gabr...@das-netzwerkteam.de, http://das-netzwerkteam.de freeBusy: https://mail.das-netzwerkteam.de/freebusy/m.gabriel%40das-netzwerkteam.de.xfb pgpMVIulrBfWe.pgp Description: Digitale PGP-Signatur
Bug#765120: [pkg-cli-libs-team] Bug#765120: monogame: support monodevelop 5
Am 20.05.2015 15:41 schrieb Emilio Pozuelo Monfort po...@debian.org: On Mon, 08 Dec 2014 16:09:54 +1100 Christopher James Halse Rogers r...@ubuntu.com wrote: Package: monogame Followup-For: Bug #765120 Alright. So, monogame 2.5.1 (from 2012) doesn't build at all against Monodevelop 5. A new upstream version, Monogame 3.2, doesn't build against the version of tao-framework in Jessie (also from 2012, project deprecated in favour of libopentk, for which Jessie also has a 2012 snapshot). It's probably time to either start maintaining these or drop them from the archive. So what's it gonna be? This has been blocking monodevelop from migrating for a long time: monodevelop (4.0.12+dfsg-6 to 5.5.0.227-1) Maintainer: Debian CLI Applications Team 222 days old (needed 5 days) Ouch, if monogame is this problematic then monodevelop should either drop the monogame build-dep or monodevelop needs a source pkg just for monogame so it doesn't block transitions. Emilio ___ pkg-cli-libs-team mailing list pkg-cli-libs-t...@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-cli-libs-team
Processed: retitle 784366 to zeromq3: CVE-2014-9721: V3 protocol handler vulnerable to downgrade attacks
Processing commands for cont...@bugs.debian.org:
retitle 784366 zeromq3: CVE-2014-9721: V3 protocol handler vulnerable to
downgrade attacks
Bug #784366 {Done: Laszlo Boszormenyi (GCS) g...@debian.org} [zeromq3]
zeromq3: V3 protocol handler vulnerable to downgrade attacks
Changed Bug title to 'zeromq3: CVE-2014-9721: V3 protocol handler vulnerable to
downgrade attacks' from 'zeromq3: V3 protocol handler vulnerable to downgrade
attacks'
thanks
Stopping processing here.
Please contact me if you need assistance.
--
784366: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=784366
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: Re: [Openjdk] Bug#786417: openjdk-8: FTBFS: *** This OS is not supported: Linux … 4.0.0-1-amd64 …
Processing commands for cont...@bugs.debian.org: severity 786417 serious Bug #786417 [src:openjdk-8] openjdk-8: FTBFS: *** This OS is not supported: Linux … 4.0.0-1-amd64 … Severity set to 'serious' from 'important' thanks Stopping processing here. Please contact me if you need assistance. -- 786417: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=786417 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#784041:
This fix should get back into Jessie, too, maybe through jessie-updates. Because without it the package is useless for Jessie. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#785800: marked as done (rspamd: FTBFS on arm64, ppc64el and others - unsatisfiable dependency libluajit-5.1-dev)
Your message dated Thu, 21 May 2015 13:49:02 + with message-id e1yvqqm-0002is...@franck.debian.org and subject line Bug#785800: fixed in rspamd 0.9.4 has caused the Debian Bug report #785800, regarding rspamd: FTBFS on arm64, ppc64el and others - unsatisfiable dependency libluajit-5.1-dev to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 785800: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=785800 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Source: rspamd Version: 0.9.3 Severity: serious Hi, rspamd will not build on (at least) arm64, ppc64el and s390x because it has an unsatisfiable build dependency on 'libluajit-5.1-dev'. The Build-Depends line contains this: libluajit-5.1-dev | liblua5.1-dev but the buildds only look at the first option. The solution to this is either to drop the luajit build dependency or explicitly state which architectures should use it. For example (based on the arches luajit currently supports): libluajit-5.1-dev [amd64 armel armhf i386 kfreebsd-i386 mips mipsel powerpc powerpcspe] | liblua5.1-dev See policy 7.1 for more details on the format of this. Thanks, James signature.asc Description: This is a digitally signed message part ---End Message--- ---BeginMessage--- Source: rspamd Source-Version: 0.9.4 We believe that the bug you reported is fixed in the latest version of rspamd, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 785...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Mikhail Gusarov dotted...@debian.org (supplier of updated rspamd package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Thu, 21 May 2015 09:26:18 +0200 Source: rspamd Binary: rspamd Architecture: source i386 Version: 0.9.4 Distribution: sid Urgency: low Maintainer: Mikhail Gusarov dotted...@debian.org Changed-By: Mikhail Gusarov dotted...@debian.org Description: rspamd - Rapid spam filtering system Closes: 785800 Changes: rspamd (0.9.4) unstable; urgency=low . * New release: - Fix Build-Depends to let buildd pick up lua 5.1 on architectures without luajit (Closes: #785800) Checksums-Sha1: d3d2551b791ca1823c4871cdc1213bde5592925a 1822 rspamd_0.9.4.dsc b56db401eebae841161299edfbc6ed4c918772c7 805176 rspamd_0.9.4.tar.xz dd814f6c597e95a41978347bd1d0971ce215c20c 580356 rspamd_0.9.4_i386.deb Checksums-Sha256: 8eedb16a6cb30c344694e83ad632f61cd1115144351a72b597249e83 1822 rspamd_0.9.4.dsc d25ed8c3ac5e2be2b0aca10905ee286b247b9cff0e714e0c14637bca8bba840a 805176 rspamd_0.9.4.tar.xz f8a534098cbe18dbe2423b39e54c01ecd1ca44fa57642bbed302f9b886dffa5f 580356 rspamd_0.9.4_i386.deb Files: 6b3ea42d56afe87d98f48935acef095c 1822 mail optional rspamd_0.9.4.dsc 2c36f67187e4f9ab9547ce1e73e689ec 805176 mail optional rspamd_0.9.4.tar.xz 396b5405286ab7b6c17956fadcdca757 580356 mail optional rspamd_0.9.4_i386.deb -BEGIN PGP SIGNATURE- Version: GnuPG v2 iQIcBAEBCgAGBQJVXd+jAAoJEJ0g9lA+M4iISckP/1PayhbTpCuMGogNa3oVEjzy 2Unr8CePGFNhbpaH39JjxsVTE2W5VrwzuSrb/gyohrBtNbBWDDDNmpGQndjHDk30 Dils4sdbIzv/beTJpYTximrYp7iBPGPFDlDPZi8licRg9F4bYf6iPo8WXh+Pp5LE gcjz6rzuG2jYZ2QxP9/Nwspphl+fg2rdkJY+NxqtBVqBuaWCdizu7mXycxlw11PG GZlC3tVhoCuGPscE8pCjX+v/vKPN0caZV03Es+u9tKlAqVPtusMTUQUOExWoWyfy ODWkBtzE3fIzpL1ezYSwSfYiKNh1UAK8rfxllU0PRYiGx+NS5JAxKNGRYsOaJbb3 tPQZYNoqyHqgf7cr1WPMzNv8o9JmLss+sIpdPbfaMLXaVQVYzAYw2vXJdO+qqI3u f9Y83S//l97t8KVEX61WyLTWrFddS3HDiMXF/aT/HGpUNZAmN+gyx7efsOqtX10r op6zvjACc4gjtg0uAdf6uRUqeFzBMEyOyVhN5U1D/PdiS5OX5QgPyKIqXMZzgBR/ s2uGcjDXiASYWFCSHTdYn9ShG+xBANa8mY30BYFR58pYEos9i+NvHdBX7hdtCAdd +ZgDPVx7UhnDgixcii4o+tlot26LibSykI/fkRdXv3jWcmKP3GLcleTgZZHc5m97 eMAK7qHLEKgBmajsvMWA =0XwO -END PGP SIGNATUREEnd Message---
Bug#750743: gspiceui: Please update to use wxwidgets3.0
On Thu, May 21, 2015 at 03:11:41PM +0200, Gudjon I. Gudjonsson wrote: Thanks a lot again. I did apply your patch but I still get the lintian warning I: gspiceui: hardening-no-fortify-functions usr/bin/gspiceui That's a false positive - lintian looks for calls to fortified libc functions and warns if it doesn't find any in a particular binary, but it's pretty common for a C++ program not to have any because it use C++ alternatives (std::string instead of string.h, iostream instead of stdio.h, etc). Look at the build log, and you'll see -D_FORTIFY_SOURCE=2 on every g++ invocation which compiles a file (at least I do in the log from my build). The description of that lintian tag here could be clearer, but does hint at such issues: https://lintian.debian.org/tags/hardening-no-fortify-functions.html Also, note Certainty: wild-guess. If you are willing to upload the package with this warning then I will do the final preparation for an upload or if you know how to fix this please tell me. The package can be found on my server or in the debian-science svn repository. svn://anonscm.debian.org/debian-science/packages/gspiceui/trunk/ Sure, let me know when you've done those final preparations. Cheers, Olly -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: Re: [Openjdk] Bug#786417: openjdk-8: FTBFS: *** This OS is not supported: Linux … 4.0.0-1-amd64 …
Processing control commands: severity -1 important Bug #786417 [src:openjdk-8] openjdk-8: FTBFS: *** This OS is not supported: Linux … 4.0.0-1-amd64 … Severity set to 'important' from 'serious' -- 786417: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=786417 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#786417: [Openjdk] Bug#786417: openjdk-8: FTBFS: *** This OS is not supported: Linux … 4.0.0-1-amd64 …
Control: severity -1 important On 05/21/2015 03:16 PM, Thorsten Glaser wrote: Source: openjdk-8 Version: 8u45-b14-3 Severity: serious Justification: fails to build from source (but built successfully in the past) Trying to rebuild it in a wheezy chroot (probably also fails in sid). make[6]: Entering directory `/tmp/openjdk-8-8u45-b14/build/hotspot' 2 echo *** This OS is not supported: `uname -a`; exit 1; *** This OS is not supported: Linux tglase.lan.tarent.de 4.0.0-1-amd64 #1 SMP Debian 4.0.2-1 (2015-05-11) x86_64 GNU/Linux Prefixing the dpkg-buildpackage call with “linux64 --uname-2.6” makes it work. And yes, I agree, this is among *the* most idiotic things in Linux recently – and even less published than the 3.0 jump, even less useful, even less tested, etc. -- System Information: Debian Release: stretch/sid APT prefers unreleased APT policy: (500, 'unreleased'), (500, 'buildd-unstable'), (500, 'unstable') Architecture: x32 (x86_64) according to http://buildd.debian-ports.org/status/logs.php?pkg=openjdk-8arch=x32 it never built before. So no justification for the escalation. Plus the severity is wrong for the x32 port. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#786436: marked as done (ncurses FTBFS: configure loops)
Your message dated Thu, 21 May 2015 22:22:43 +
with message-id e1yvyrt-0005vj...@franck.debian.org
and subject line Bug#786436: fixed in ncurses 5.9+20150516-2
has caused the Debian Bug report #786436,
regarding ncurses FTBFS: configure loops
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
786436: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=786436
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
---BeginMessage---
Source: ncurses
Version: 5.9+20150516-1
Tags: moreinfo
User: helm...@debian.org
Usertags: rebootstrap
Hi,
I've seen ncurses FTBFS three times now and still no clue why. The
symptom is that the build hangs at:
| test -d /tmp/buildd/ncurses-5.9+20150516/obj-test || mkdir
/tmp/buildd/ncurses-5.9+20150516/obj-test
| cd /tmp/buildd/ncurses-5.9+20150516/obj-test CFLAGS=-g -O2
-fstack-protector-strong -Wformat -Werror=format-security
/tmp/buildd/ncurses-5.9+20150516/test/configure \
| --prefix=/usr --build=x86_64-linux-gnu
--bindir=/usr/lib/ncurses/examples --with-ncursesw
--with-curses-dir=/tmp/buildd/ncurses-5.9+20150516/obj-wide
| checking build system type... x86_64-pc-linux-gnu
| checking host system type... x86_64-pc-linux-gnu
| Configuring for linux-gnu
| checking whether make sets ${MAKE}... yes
| checking for gcc... gcc
| checking for C compiler default output... a.out
| checking whether the C compiler works... yes
| checking whether we are cross compiling... no
| checking for executable suffix...
| checking for object suffix... o
| checking whether we are using the GNU C compiler... yes
| checking whether gcc accepts -g... yes
| checking version of gcc... 4.9.2
| checking for gcc option to accept ANSI C... none needed
| checking $CC variable... ok
| checking how to run the C preprocessor... gcc -E
| checking for mawk... mawk
| checking for a BSD compatible install... /usr/bin/install -c
| checking for tdlint... no
| checking for lint... no
| checking for alint... no
| checking for splint... no
| checking for lclint... no
| checking if filesystem supports mixed-case filenames... yes
| checking for exctags... no
| checking for ctags... no
| checking for exetags... no
| checking for etags... no
| checking for ctags... no
| checking for etags... no
| checking if -lm needed for math functions... yes
| configure: checking for gcc __attribute__ directives...
| ... scanf
| ... printf
| ... unused
| ... noreturn
| checking if we must define _GNU_SOURCE... yes
| checking if _XOPEN_SOURCE really is set... yes
| checking for signal global datatype... volatile sig_atomic_t
| checking if you want to use pkg-config... yes
| checking for pkg-config... /usr/bin/pkg-config
| checking if you want to see long compiling messages... yes
| checking for ncurses wrap-prefix... _nc_
| checking if you want to check for wide-character functions... yes
| checking for specific curses-directory...
/tmp/buildd/ncurses-5.9+20150516/obj-wide
| checking for specified curses library type... ncursesw
| checking for multibyte character support... yes
| checking pkg-config for ncursesw... no
| Looking for ncursesw-config
| checking for ncursesw-config... no
| checking for ncursesw6-config... no
| checking for ncursesw5-config... no
At this point, attaching the main configure shell reveals that it
continuously calls stat:
| stat(/tmp/buildd/ncurses-5.9+20150516/obj-wide/include/ncursesw,
0x7ffd1feb0220) = -1 ENOENT (No such file or directory)
The generated configure scrip contains a snippet that roughly resembles:
| while test $cf_add_incdir != /usr/include; do
| if test -d $cf_add_incdir; then
|...
| # no else branch
| fi
| done
I've seen this in a native amd64 reproducible build on
jenkins.debian.net:
https://jenkins.debian.net/job/reproducible_builder_alpha/46528/console
(the above excerpt is from this log)
I've also seen this in a cross build for x32 and a cross build for i386.
https://jenkins.debian.net/job/rebootstrap_i386_gcc49_nobiarch/139/console
In the x32 build (no log available), I created the directory being
stat()ed. At that point, the build continued and finished successfully.
Both cross builds set DEB_BUILD_OPTIONS=nocheck parallel=1.
Notably, the reproducible jenkins job was able to build this version of
ncurses earlier, so it seems that something else is the cause. The
buildds had no problems building it either.
This is all I know.
If the bug does not receive sufficient detail to be diagnosed, it should
be closed within one month of inactivity.
Helmut
---End Message---
---BeginMessage---
Source: ncurses
Source-Version: 5.9+20150516-2
We believe that the bug you
Bug#750255: marked as done (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)
Your message dated Thu, 21 May 2015 22:53:16 + with message-id e1yvzl2-0001rl...@franck.debian.org and subject line Bug#785191: Removed package(s) from unstable has caused the Debian Bug report #750255, regarding 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 to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 750255: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=750255 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Source: lio-utils Version: 3.1+git2.fd0b34fd-2 Severity: serious Tags: jessie sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20140601 qa-ftbfs Justification: FTBFS on amd64 Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): make[1]: Entering directory '/«BUILDDIR»/lio-utils-3.1+git2.fd0b34fd' # Hack for now. chmod a+x /«BUILDDIR»/lio-utils-3.1+git2.fd0b34fd/debian/lio-utils/usr/share/pyshared/*.py chmod: cannot access '/«BUILDDIR»/lio-utils-3.1+git2.fd0b34fd/debian/lio-utils/usr/share/pyshared/*.py': No such file or directory make[1]: *** [override_dh_link] Error 1 The full build log is available from: http://aws-logs.debian.net/ftbfs-logs/2014/06/01/lio-utils_3.1+git2.fd0b34fd-2_unstable.log A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! About the archive rebuild: The rebuild was done on EC2 VM instances from Amazon Web Services, using a clean, minimal and up-to-date chroot. Every failed build was retried once to eliminate random failures. ---End Message--- ---BeginMessage--- Version: 3.1+git2.fd0b34fd-2+rm Dear submitter, as the package lio-utils has just been removed from the Debian archive unstable we hereby close the associated bug reports. We are sorry that we couldn't deal with your issue properly. For details on the removal, please see https://bugs.debian.org/785191 The version of this package that was in Debian prior to this removal can still be found using http://snapshot.debian.org/. This message was generated automatically; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org. Debian distribution maintenance software pp. Scott Kitterman (the ftpmaster behind the curtain)---End Message---
Bug#609535: marked as done (psiconv: magick/semaphore.c:526: LockSemaphoreInfo: Assertion `semaphore_info-signature == 0xabacadabUL' failed.)
Your message dated Thu, 21 May 2015 23:07:05 +
with message-id e1yvzyp-0003xs...@franck.debian.org
and subject line Bug#785319: Removed package(s) from unstable
has caused the Debian Bug report #609535,
regarding psiconv: magick/semaphore.c:526: LockSemaphoreInfo: Assertion
`semaphore_info-signature == 0xabacadabUL' failed.
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
609535: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=609535
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
---BeginMessage---
Package: psiconv
Version: 0.9.8-4.1
Severity: grave
Tags: patch
Justification: renders package unusable
Recent versions of GraphicsMagick require the InitializeMagick API to be called:
1.3.8 (January 21, 2010)
[…]
Behavior Changes:
* InitializeMagick() MUST be invoked prior to using any Magick API
function. Failure to do so will likely lead to an immediate
application crash. This is due to initialization and runtime
changes intended to improve thread safety and efficiency.
Previously it was only strongly recommended to invoke
InitializeMagick().
The attached patch fixes this issue for psiconv. Note that this patch
also works for building against ImageMagick (because InitializeMagick
is a long-standing API), and in any case it would only apply to old
versions, since psiconv's configure script detects GraphicsMagick as
API level 2, whereas the highest API level it detects is 4.
The only recent change is that calling InitializeMagick used to be
optional, whereas it is now mandatory.
-- System Information:
Debian Release: squeeze/sid
APT prefers maverick-updates
APT policy: (500, 'maverick-updates'), (500, 'maverick-security'), (500,
'maverick-backports'), (500, 'maverick')
Architecture: i386 (i686)
Kernel: Linux 2.6.35-24-generic (SMP w/2 CPU cores)
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Versions of packages psiconv depends on:
ii libbz2-1.0 1.0.5-4ubuntu1 high-quality block-sorting file co
ii libc62.12.1-0ubuntu10Embedded GNU C Library: Shared lib
ii libfreetype6 2.4.2-2ubuntu0.1FreeType 2 font engine, shared lib
ii libgomp1 4.5.1-7ubuntu2 GCC OpenMP (GOMP) support library
ii libgraphicsmagic 1.3.12-1format-independent image processin
ii libice6 2:1.0.6-1 X11 Inter-Client Exchange library
ii libjasper1 1.900.1-7 The JasPer JPEG-2000 runtime libra
ii libjpeg626b-16.1 The Independent JPEG Group's JPEG
ii liblcms1 1.18.dfsg-1ubuntu2 Color management library
ii libpng12-0 1.2.44-1PNG library - runtime
ii libpsiconv6 0.9.8-4.1 a library for handling Psion files
ii libsm6 2:1.1.1-1 X11 Session Management library
ii libtiff4 3.9.4-2 Tag Image File Format (TIFF) libra
ii libwmf0.2-7 0.2.8.4-7ubuntu2Windows metafile conversion librar
ii libx11-6 2:1.3.3-3ubuntu1X11 client-side library
ii libxext6 2:1.1.2-1 X11 miscellaneous extension librar
ii libxml2 2.7.7.dfsg-4ubuntu0.1 GNOME XML library
ii zlib1g 1:1.2.3.4.dfsg-3ubuntu1 compression library - runtime
psiconv recommends no packages.
psiconv suggests no packages.
-- no debconf information
--- psiconv-0.9.8/configure.in 2005-11-15 15:43:19.0 +
+++ psiconv-0.9.8-rrt/configure.in 2011-01-10 12:35:58.0 +
@@ -112,6 +112,7 @@
#include time.h
#include magick/api.h
int main(void) { ExceptionInfo exception;
+ InitializeMagick(NULL);
GetExceptionInfo(exception);
OpenModules(exception);
return (NULL == GetMagickInfo(NULL,exception)); }],
--- psiconv-0.9.8/program/psiconv/magick-aux.c 2005-11-15 15:08:21.0 +
+++ psiconv-0.9.8-rrt/program/psiconv/magick-aux.c 2011-01-10 12:37:09.0 +
@@ -37,6 +37,7 @@
const MagickInfo * GetMagickFileList(void)
{
ExceptionInfo exc;
+ InitializeMagick(NULL);
GetExceptionInfo(exc);
OpenModules(exc);
return GetMagickInfo(NULL,exc);
---End Message---
---BeginMessage---
Version: 0.9.8-4.1+rm
Dear submitter,
as the package psiconv has just been removed from the Debian archive
unstable we hereby close the associated bug reports. We are sorry
that we couldn't deal with your issue properly.
For details on the
Bug#785038: marked as done (collectl-utils and collectl: error when trying to install together)
Your message dated Thu, 21 May 2015 23:17:17 + with message-id e1yvzih-0005bh...@franck.debian.org and subject line Bug#784787: Removed package(s) from unstable has caused the Debian Bug report #785038, regarding collectl-utils and collectl: error when trying to install together to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 785038: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=785038 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: collectl,collectl-utils Version: collectl/4.0.0-1 Version: collectl-utils/4.8.1-2 Severity: serious User: trei...@debian.org Usertags: edos-file-overwrite Date: 2015-05-11 Architecture: amd64 Distribution: sid Hi, automatic installation tests of packages that share a file and at the same time do not conflict by their package dependency relationships has detected the following problem: Extracting templates from packages: 41% Extracting templates from packages: 83% Extracting templates from packages: 100% Preconfiguring packages ... (Reading database ... 10930 files and directories currently installed.) Preparing to unpack .../perl_5.20.2-4_amd64.deb ... Unpacking perl (5.20.2-4) over (5.18.2-2) ... Preparing to unpack .../libtext-charwidth-perl_0.04-7+b3_amd64.deb ... Unpacking libtext-charwidth-perl (0.04-7+b3) over (0.04-7+b2) ... Preparing to unpack .../perl-base_5.20.2-4_amd64.deb ... Unpacking perl-base (5.20.2-4) over (5.18.2-2) ... Processing triggers for man-db (2.7.0.2-5) ... Setting up perl-base (5.20.2-4) ... (Reading database ... 10375 files and directories currently installed.) Preparing to unpack .../liblocale-gettext-perl_1.05-8+b1_amd64.deb ... Unpacking liblocale-gettext-perl (1.05-8+b1) over (1.05-7+b2) ... Preparing to unpack .../libtext-iconv-perl_1.7-5+b2_amd64.deb ... Unpacking libtext-iconv-perl (1.7-5+b2) over (1.7-5+b1) ... Preparing to unpack .../perl-modules_5.20.2-4_all.deb ... Unpacking perl-modules (5.20.2-4) over (5.18.2-7) ... Selecting previously unselected package libdb5.3:amd64. Preparing to unpack .../libdb5.3_5.3.28-9_amd64.deb ... Unpacking libdb5.3:amd64 (5.3.28-9) ... Selecting previously unselected package libbsd0:amd64. Preparing to unpack .../libbsd0_0.7.0-2_amd64.deb ... Unpacking libbsd0:amd64 (0.7.0-2) ... Selecting previously unselected package libedit2:amd64. Preparing to unpack .../libedit2_3.1-20150325-1_amd64.deb ... Unpacking libedit2:amd64 (3.1-20150325-1) ... Selecting previously unselected package libpci3:amd64. Preparing to unpack .../libpci3_1%3a3.2.1-3_amd64.deb ... Unpacking libpci3:amd64 (1:3.2.1-3) ... Selecting previously unselected package libexpat1:amd64. Preparing to unpack .../libexpat1_2.1.0-6+b3_amd64.deb ... Unpacking libexpat1:amd64 (2.1.0-6+b3) ... Selecting previously unselected package libpng12-0:amd64. Preparing to unpack .../libpng12-0_1.2.50-2+b2_amd64.deb ... Unpacking libpng12-0:amd64 (1.2.50-2+b2) ... Selecting previously unselected package libfreetype6:amd64. Preparing to unpack .../libfreetype6_2.5.2-4_amd64.deb ... Unpacking libfreetype6:amd64 (2.5.2-4) ... Selecting previously unselected package ucf. Preparing to unpack .../archives/ucf_3.0030_all.deb ... Moving old data out of the way Unpacking ucf (3.0030) ... Selecting previously unselected package fonts-dejavu-core. Preparing to unpack .../fonts-dejavu-core_2.34-1_all.deb ... Unpacking fonts-dejavu-core (2.34-1) ... Selecting previously unselected package fontconfig-config. Preparing to unpack .../fontconfig-config_2.11.0-6.3_all.deb ... Unpacking fontconfig-config (2.11.0-6.3) ... Selecting previously unselected package libfontconfig1:amd64. Preparing to unpack .../libfontconfig1_2.11.0-6.3_amd64.deb ... Unpacking libfontconfig1:amd64 (2.11.0-6.3) ... Selecting previously unselected package fontconfig. Preparing to unpack .../fontconfig_2.11.0-6.3_amd64.deb ... Unpacking fontconfig (2.11.0-6.3) ... Selecting previously unselected package libxau6:amd64. Preparing to unpack .../libxau6_1%3a1.0.8-1_amd64.deb ... Unpacking libxau6:amd64 (1:1.0.8-1) ... Selecting previously unselected package x11-common. Preparing to unpack .../x11-common_1%3a7.7+8_all.deb ... Unpacking x11-common (1:7.7+8) ... Selecting previously unselected package libice6:amd64. Preparing to unpack .../libice6_2%3a1.0.9-1+b1_amd64.deb ... Unpacking libice6:amd64 (2:1.0.9-1+b1) ... Selecting previously unselected package libsm6:amd64. Preparing to unpack .../libsm6_2%3a1.2.2-1+b1_amd64.deb ... Unpacking libsm6:amd64 (2:1.2.2-1+b1) ... Selecting previously unselected package libxdmcp6:amd64. Preparing to unpack
Bug#742303: marked as done (basenji: Crashes on adding a new volume to the catalog)
Your message dated Thu, 21 May 2015 22:39:56 + with message-id e1yvz88-oo...@franck.debian.org and subject line Bug#740845: Removed package(s) from unstable has caused the Debian Bug report #742303, regarding basenji: Crashes on adding a new volume to the catalog to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 742303: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=742303 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: basenji Version: 1.0.1-3 Severity: grave Justification: renders package unusable Dear Maintainer, The current version of basenji in debian testing repos crashes every time I try to add a new volume to the catalog, rendering the program useless. I tried deleting the preferences directory and starting a new catalog, but it keeps crashing. The program also crashes when I try to enter to the preferences. The previous version worked fine, no crashes. -- System Information: Debian Release: jessie/sid APT prefers testing APT policy: (500, 'testing'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.13-1-amd64 (SMP w/4 CPU cores) Locale: LANG=es_AR.utf8, LC_CTYPE=es_AR.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages basenji depends on: ii libc6 2.18-4 ii libdbus-glib2.0-cil 0.6.0-1 ii libdbus2.0-cil 0.8.0-1 ii libglib2.0-02.38.2-5 ii libglib2.0-cil 2.12.10-5 ii libgnome-desktop-2-17 2.32.1-2 ii libgtk2.0-0 2.24.22-1 ii libgtk2.0-cil 2.12.10-5 ii libmono-cairo4.0-cil3.0.6+dfsg2-11 ii libmono-corlib4.5-cil 3.0.6+dfsg2-11 ii libmono-posix4.0-cil3.0.6+dfsg2-11 ii libmono-sharpzip4.84-cil3.0.6+dfsg2-11 ii libmono-sqlite4.0-cil 3.0.6+dfsg2-11 ii libmono-system-core4.0-cil 3.0.6+dfsg2-11 ii libmono-system-data4.0-cil 3.0.6+dfsg2-11 ii libmono-system-xml4.0-cil 3.0.6+dfsg2-11 ii libmono-system4.0-cil 3.0.6+dfsg2-11 ii librsvg2-common 2.40.0-1 ii libtaglib2.1-cil2.1.0.0-3 ii mono-runtime3.0.6+dfsg2-11 ii udisks 1.0.5-1 basenji recommends no packages. basenji suggests no packages. -- no debconf information ---End Message--- ---BeginMessage--- Version: 1.0.1-3+rm Dear submitter, as the package basenji has just been removed from the Debian archive unstable we hereby close the associated bug reports. We are sorry that we couldn't deal with your issue properly. For details on the removal, please see https://bugs.debian.org/740845 The version of this package that was in Debian prior to this removal can still be found using http://snapshot.debian.org/. This message was generated automatically; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org. Debian distribution maintenance software pp. Scott Kitterman (the ftpmaster behind the curtain)---End Message---
Bug#740845: marked as done (RM: basenji -- RoQA; unmaintained, depends on obsolete udisks)
Your message dated Thu, 21 May 2015 22:39:49 + with message-id e1yvz81-jp...@franck.debian.org and subject line Bug#740845: Removed package(s) from unstable has caused the Debian Bug report #740845, regarding RM: basenji -- RoQA; unmaintained, depends on obsolete udisks to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 740845: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=740845 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: basenji Version: 1.0.1-3 User: pkg-utopia-maintain...@lists.alioth.debian.org Usertags: udisks1-deprecation Hello, this package currently depends on/recommends udisks 1. That has been deprecated for a while now, in favor of udisks 2. Please port the package to udisks 2 and drop code that uses the old hal/devicekit-disks/udisks 1 bits. Please note that udisks2 also has a library interface (libudisks2-0) which is easier to use than raw D-BUS calls. It is also introspectable (gir1.2-udisks-2.0) so you can use it from languages like Python. However, for this C# case it's probably better to stick with raw D-BUS calls as AFAIK there is no current/maintained gobject-introspection support for Mono. The API is documented at http://udisks.freedesktop.org/docs/latest/ . Thanks, Martin -- Martin Pitt| http://www.piware.de Ubuntu Developer (www.ubuntu.com) | Debian Developer (www.debian.org) signature.asc Description: Digital signature ---End Message--- ---BeginMessage--- We believe that the bug you reported is now fixed; the following package(s) have been removed from unstable: basenji |1.0.1-3 | source, all --- Reason --- RoQA; unmaintained, depends on obsolete udisks -- Note that the package(s) have simply been removed from the tag database and may (or may not) still be in the pool; this is not a bug. The package(s) will be physically removed automatically when no suite references them (and in the case of source, when no binary references it). Please also remember that the changes have been done on the master archive and will not propagate to any mirrors until the next dinstall run at the earliest. Packages are usually not removed from testing by hand. Testing tracks unstable and will automatically remove packages which were removed from unstable when removing them from testing causes no dependency problems. The release team can force a removal from testing if it is really needed, please contact them if this should be the case. We try to close bugs which have been reported against this package automatically. But please check all old bugs, if they were closed correctly or should have been re-assigned to another package. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 740...@bugs.debian.org. The full log for this bug can be viewed at https://bugs.debian.org/740845 This message was generated automatically; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org. Debian distribution maintenance software pp. Scott Kitterman (the ftpmaster behind the curtain)---End Message---
Bug#599670: marked as done ([imdb-tools] New IMDb layout completely breaks parsing)
Your message dated Thu, 21 May 2015 23:19:32 + with message-id e1yvzks-0005sk...@franck.debian.org and subject line Bug#785321: Removed package(s) from unstable has caused the Debian Bug report #599670, regarding [imdb-tools] New IMDb layout completely breaks parsing to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 599670: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=599670 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: imdb-tools Version: 0.9-1 Severity: important --- Please enter the report below this line. --- Since IMDb has the new layout, imdb-get can no longer parse any movie information. --- System information. --- Architecture: i386 Kernel: Linux 2.6.32-5-686 Debian Release: squeeze/sid 500 unstablewww.debian-multimedia.org 500 unstableftp.de.debian.org 1 experimentalftp2.de.debian.org --- Package information. --- Depends (Version) | Installed ===-+-=== curl| 7.21.1-1 realpath| 1.15 tidy| 20091223cvs-1 Package's Recommends field is empty. Package's Suggests field is empty. signature.asc Description: OpenPGP digital signature ---End Message--- ---BeginMessage--- Version: 0.9-1+rm Dear submitter, as the package imdb-tools has just been removed from the Debian archive unstable we hereby close the associated bug reports. We are sorry that we couldn't deal with your issue properly. For details on the removal, please see https://bugs.debian.org/785321 The version of this package that was in Debian prior to this removal can still be found using http://snapshot.debian.org/. This message was generated automatically; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org. Debian distribution maintenance software pp. Scott Kitterman (the ftpmaster behind the curtain)---End Message---
Bug#786469: sysvinit-utils, util-linux: can't upgrade - 'installation run will require temporarily removing the essential package'
Package: sysvinit-utils, util-linux Version: sysvinit-utils/2.88dsf-59.2, util-linux/2.26.2-4 Severity: grave Hi, I have a system running sid which I haven't upgraded for a few weeks. I was greeted with this just now (apt-get upgrade fails as well, but I used install to make the output smaller). # apt-get install -Vy util-linux Reading package lists... Done Building dependency tree Reading state information... Done The following extra packages will be installed: initscripts (2.88dsf-59.2) Suggested packages: bootlogd (2.88dsf-59.2) sash (3.8-3+b1) dosfstools (3.0.27-1) kbd (1.15.5-2) console-tools () util-linux-locales (2.26.2-4) The following packages will be upgraded: initscripts (2.88dsf-59 = 2.88dsf-59.2) sysvinit-utils (2.88dsf-59 = 2.88dsf-59.2) util-linux (2.26.2-2 = 2.26.2-4) 3 upgraded, 0 newly installed, 0 to remove and 128 not upgraded. Need to get 0 B/1006 kB of archives. After this operation, 62.5 kB of additional disk space will be used. E: This installation run will require temporarily removing the essential package util-linux:i386 due to a Conflicts/Pre-Depends loop. This is often bad, but if you really want to do it, activate the APT::Force-LoopBreak option. E: Internal Error, Could not early remove util-linux:i386 (2) # cd /var/cache/apt/archives # dpkg --auto-deconfigure -i util-linux_2.26.2-4_i386.deb sysvinit-utils_2.88dsf-59.2_i386.deb initscripts_2.88dsf-59.2_i386.deb dpkg: considering deconfiguration of sysvinit-utils, which would be broken by installation of util-linux ... dpkg: no, sysvinit-utils is essential, will not deconfigure it in order to enable installation of util-linux dpkg: error processing archive util-linux_2.26.2-4_i386.deb (--install): installing util-linux would break existing software dpkg: considering deconfiguration of util-linux, which would be broken by installation of sysvinit-utils ... dpkg: no, util-linux is essential, will not deconfigure it in order to enable installation of sysvinit-utils dpkg: error processing archive sysvinit-utils_2.88dsf-59.2_i386.deb (--install): installing sysvinit-utils would break existing software dpkg: considering deconfiguration of util-linux, which would be broken by installation of initscripts ... dpkg: no, util-linux is essential, will not deconfigure it in order to enable installation of initscripts dpkg: error processing archive initscripts_2.88dsf-59.2_i386.deb (--install): installing initscripts would break existing software Errors were encountered while processing: util-linux_2.26.2-4_i386.deb sysvinit-utils_2.88dsf-59.2_i386.deb initscripts_2.88dsf-59.2_i386.deb From util-linux: Breaks: sysvinit-utils ( 2.88dsf-59.1~) From sysvinit-utils: Breaks: util-linux ( 2.26.2-3) So from the versions I have I don't see anyway to upgrade either of these packages without deconfiguring the other first - and apt/dpkg refuses to do that to an essential package. For good measure I also tried upgrading a jessie chroot to sid and got the same error. Thanks, James signature.asc Description: This is a digitally signed message part
Processed: Bug#786469: fixing versions second try
Processing commands for cont...@bugs.debian.org: notfound 786469 sysvinit-utils/2.88dsf-59.2 Bug #786469 [sysvinit-utils, util-linux] sysvinit-utils, util-linux: can't upgrade - 'installation run will require temporarily removing the essential package' The source sysvinit-utils and version 2.88dsf-59.2 do not appear to match any binary packages No longer marked as found in versions sysvinit-utils/2.88dsf-59.2. found 786469 sysvinit/2.88dsf-59.2 Bug #786469 [sysvinit-utils, util-linux] sysvinit-utils, util-linux: can't upgrade - 'installation run will require temporarily removing the essential package' Marked as found in versions sysvinit/2.88dsf-59.2. thanks Stopping processing here. Please contact me if you need assistance. -- 786469: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=786469 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#746378: marked as done (flumotion fails to start, worker are not launched)
Your message dated Thu, 21 May 2015 22:42:08 + with message-id e1yvzag-sz...@franck.debian.org and subject line Bug#785935: Removed package(s) from unstable has caused the Debian Bug report #739215, regarding flumotion fails to start, worker are not launched to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 739215: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=739215 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: flumotion Version: 0.10.0-3 Severity: grave Justification: renders package unusable Dear Maintainer, flumotion doesn't start at all when using flumotion-admin command. There's a manager process, but not a worker one. In log I find : INFO [19901] servicer Apr 28 23:32:56 Stopping manager default (flumotion/service/service.py:538) INFO [19923] servicer Apr 28 23:32:57 Stopping worker default (flumotion/service/service.py:566) INFO [19923] servicer Apr 28 23:32:57 worker default was not running (flumotion/service/service.py:569) INFO [19965] servicer Apr 28 23:32:57 Starting manager default (flumotion/service/service.py:409) INFO [19965] servicer Apr 28 23:32:57 Loading planet /etc/flumotion/managers/default/planet.xml (flumotion/service/service.py:421) INFO [19965] servicer Apr 28 23:32:58 Started manager default with pid 19970 (flumotion/service/service.py:457) INFO [19992] servicer Apr 28 23:32:58 Starting worker default (flumotion/service/service.py:474) INFO [19992] servicer Apr 28 23:32:58 Loading worker /etc/flumotion/workers/default.xml (flumotion/service/service.py:498) INFO [19993] jelly Apr 28 23:32:59 GnomeVFS registered (flumotion/common/vfsgnome.py:122) INFO [19993] jelly Apr 28 23:32:59 GIO registered (flumotion/common/vfsgio.py:137) INFO [19993] jelly Apr 28 23:32:59 VFS registered (flumotion/common/vfs.py:92) Traceback (most recent call last): File /usr/bin/flumotion-worker, line 43, in module boot.boot(PROGRAM_PATH, gtk=False, gst=False, installReactor=False) File /usr/lib/flumotion/python/flumotion/common/boot.py, line 305, in boot sys.exit(wrapped(sys.argv)) File /usr/lib/flumotion/python/flumotion/worker/main.py, line 229, in main if not brain.listen(): File /usr/lib/flumotion/python/flumotion/worker/worker.py, line 143, in listen self.feedServer = self._makeFeedServer() File /usr/lib/flumotion/python/flumotion/worker/worker.py, line 176, in _makeFeedServer return feedserver.FeedServer(self, ProxyBouncer(self), port) File /usr/lib/flumotion/python/flumotion/worker/feedserver.py, line 51, in __init__ self.listen(bouncer, portNum) File /usr/lib/flumotion/python/flumotion/worker/feedserver.py, line 64, in listen tport = reactor.listenWith(fdserver.PassableServerPort, portNum, AttributeError: 'EPollReactor' object has no attribute 'listenWith' WARN [19992] servicer Apr 28 23:32:59 worker default could not start (return value 1) (flumotion/service/service.py:518) It looks like listenWith is obsolete. Regards nb -- System Information: Debian Release: jessie/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: i386 (i686) Kernel: Linux 3.13-1-686-pae (SMP w/1 CPU core) Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages flumotion depends on: ii adduser 3.113+nmu3 ii gstreamer0.10-ffmpeg1:0.10.13-dmo1 ii gstreamer0.10-plugins-bad [gstreamer0.10-schroedinger] 0.10.23-7.2+b1 ii gstreamer0.10-plugins-base 0.10.36-1.1 ii gstreamer0.10-plugins-good 0.10.31-3+nmu2 ii libc6 2.18-4 ii python 2.7.5-5 ii python-cairo1.8.8-1+b2 ii python-dateutil 1.5+dfsg-1 ii python-glade2
Bug#739215: marked as done (flumotion depends on python-twisted features removed in v13.0.0)
Your message dated Thu, 21 May 2015 22:42:08 + with message-id e1yvzag-sz...@franck.debian.org and subject line Bug#785935: Removed package(s) from unstable has caused the Debian Bug report #739215, regarding flumotion depends on python-twisted features removed in v13.0.0 to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 739215: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=739215 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: flumotion Version: 0.10.0-3 Severity: grave Tags: upstream Justification: renders package unusable Dear Maintainer, I installed python-twisted from wheezy-backports (v 13.0.0) and tried to run flumotion-worker. It failed complaining about bad method. The Twisted framework has changed its API somehow between versions 12.0.0 and 13.0.0. The flumotion package should get a constraint -- conflict with python-twisted = 13.0.0. With stable python-twisted, flumotion seems to work. -- System Information: Debian Release: jessie/sid APT prefers stable APT policy: (500, 'stable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.12-1-amd64 (SMP w/8 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=cs_CZ.UTF-8 (charmap=UTF-8) (ignored: LC_ALL set to en_US.UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages flumotion depends on: ii adduser 3.113+nmu3 ii gstreamer0.10-ffmpeg1:0.10.13-dmo1 ii gstreamer0.10-plugins-bad [gstreamer0.10-schroedinger] 0.10.23-7.1 ii gstreamer0.10-plugins-base 0.10.36-1.1 ii gstreamer0.10-plugins-good 0.10.31-3+nmu2 ii libc6 2.17-97 ii python 2.7.5-5 ii python-cairo1.8.8-1+b2 ii python-dateutil 1.5+dfsg-1 ii python-glade2 2.24.0-3+b1 ii python-gobject 3.10.2-2 ii python-gst0.10 0.10.22-3 ii python-gtk2 2.24.0-3+b1 ii python-kiwi 1.9.22-2 ii python-openssl 0.13.1-1 ii python-rrdtool 1.4.7-2+b1 ii python-twisted-core 12.0.0-1 ii python-twisted-web 12.0.0-1 ii python2.7 2.7.6-5 ii ssl-cert1.0.33 ii xsltproc1.1.28-2 Versions of packages flumotion recommends: ii python-gnome2 2.28.1+dfsg-1 flumotion suggests no packages. -- Configuration Files: /etc/flumotion/managers/default/planet.xml [Errno 13] Permission denied: u'/etc/flumotion/managers/default/planet.xml' /etc/flumotion/workers/default.xml [Errno 13] Permission denied: u'/etc/flumotion/workers/default.xml' -- no debconf information ---End Message--- ---BeginMessage--- Version: 0.10.0-3+rm Dear submitter, as the package flumotion has just been removed from the Debian archive unstable we hereby close the associated bug reports. We are sorry that we couldn't deal with your issue properly. For details on the removal, please see https://bugs.debian.org/785935 The version of this package that was in Debian prior to this removal can still be found using http://snapshot.debian.org/. This message was generated automatically; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org. Debian distribution maintenance software pp. Scott Kitterman (the ftpmaster behind the curtain)---End Message---
Bug#740842: marked as done (RM: libpam-usb -- RoQA; unmaintained, depends on obsolete udisks)
Your message dated Thu, 21 May 2015 22:48:27 + with message-id e1yvzgn-ve...@franck.debian.org and subject line Bug#740842: Removed package(s) from unstable has caused the Debian Bug report #740842, regarding RM: libpam-usb -- RoQA; unmaintained, depends on obsolete udisks to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 740842: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=740842 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: libpam-usb Version: 0.5.0-4 User: pkg-utopia-maintain...@lists.alioth.debian.org Usertags: udisks1-deprecation Hello, this package currently depends on/recommends udisks 1. That has been deprecated for a while now, in favor of udisks 2. Please port the package to udisks 2 and drop code that uses the old hal/devicekit-disks/udisks 1 bits. Please note that udisks2 also has a library interface (libudisks2-0) which is easier to use than raw D-BUS calls. It is also introspectable (gir1.2-udisks-2.0) so you can use it from languages like Python. The API is documented at http://udisks.freedesktop.org/docs/latest/ . Thanks, Martin -- Martin Pitt| http://www.piware.de Ubuntu Developer (www.ubuntu.com) | Debian Developer (www.debian.org) signature.asc Description: Digital signature ---End Message--- ---BeginMessage--- We believe that the bug you reported is now fixed; the following package(s) have been removed from unstable: libpam-usb |0.5.0-4 | source, amd64, arm64, armel, armhf, i386, kfreebsd-amd64, kfreebsd-i386, mips, mipsel, powerpc, ppc64el, s390x, sparc libpam-usb | 0.5.0-4+b1 | hurd-i386 pamusb-common |0.5.0-4 | amd64, arm64, armel, armhf, i386, kfreebsd-amd64, kfreebsd-i386, mips, mipsel, powerpc, ppc64el, s390x, sparc pamusb-common | 0.5.0-4+b1 | hurd-i386 pamusb-tools |0.5.0-4 | all --- Reason --- RoQA; unmaintained, depends on obsolete udisks -- Note that the package(s) have simply been removed from the tag database and may (or may not) still be in the pool; this is not a bug. The package(s) will be physically removed automatically when no suite references them (and in the case of source, when no binary references it). Please also remember that the changes have been done on the master archive and will not propagate to any mirrors until the next dinstall run at the earliest. Packages are usually not removed from testing by hand. Testing tracks unstable and will automatically remove packages which were removed from unstable when removing them from testing causes no dependency problems. The release team can force a removal from testing if it is really needed, please contact them if this should be the case. We try to close bugs which have been reported against this package automatically. But please check all old bugs, if they were closed correctly or should have been re-assigned to another package. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 740...@bugs.debian.org. The full log for this bug can be viewed at https://bugs.debian.org/740842 This message was generated automatically; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org. Debian distribution maintenance software pp. Scott Kitterman (the ftpmaster behind the curtain)---End Message---
Bug#786338: marked as done (ears: broken since python-musicbrainz has been removed)
Your message dated Thu, 21 May 2015 22:49:17 + with message-id e1yvzhb-00010c...@franck.debian.org and subject line Bug#786343: Removed package(s) from unstable has caused the Debian Bug report #786338, regarding ears: broken since python-musicbrainz has been removed to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 786338: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=786338 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: ears Version: 1.0.1-2.1 Severity: grave python-musicbrainz and lastfmsubmitd are no longer in the archive, so ears is not usable anymore: $ mbfind import: No module named musicbrainz $ mbget import: No module named musicbrainz $ mbsubmit import: No module named musicbrainz $ peel Traceback (most recent call last): File /usr/bin/peel, line 10, in module import lastfm.client ImportError: No module named lastfm.client $ lastcd Traceback (most recent call last): File /usr/bin/lastcd, line 8, in module import lastfm ImportError: No module named lastfm Cheers -- Sebastian Ramacher signature.asc Description: Digital signature ---End Message--- ---BeginMessage--- Version: 1.0.1-2.1+rm Dear submitter, as the package ears has just been removed from the Debian archive unstable we hereby close the associated bug reports. We are sorry that we couldn't deal with your issue properly. For details on the removal, please see https://bugs.debian.org/786343 The version of this package that was in Debian prior to this removal can still be found using http://snapshot.debian.org/. This message was generated automatically; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org. Debian distribution maintenance software pp. Scott Kitterman (the ftpmaster behind the curtain)---End Message---
Bug#750511: marked as done (RM: udisks-glue -- ROM; depends on obsolete udisks)
Your message dated Thu, 21 May 2015 23:04:59 + with message-id e1yvzwn-0003is...@franck.debian.org and subject line Bug#750511: Removed package(s) from unstable has caused the Debian Bug report #750511, regarding RM: udisks-glue -- ROM; depends on obsolete udisks to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 750511: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=750511 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: udisks-glue Version: 1.3.5-1 Severity: normal User: pkg-utopia-maintain...@lists.alioth.debian.org Usertags: udisks1-deprecation Hello, this package currently depends on/recommends udisks 1. That has been deprecated for a while now, in favor of udisks 2. Please port the package to udisks 2 and drop code that uses the old hal/devicekit-disks/udisks 1 bits. Please note that udisks2 also has a library interface (libudisks2-0) which is easier to use than raw D-BUS calls. It is also introspectable (gir1.2-udisks-2.0) so you can use it from languages like Python. The API is documented at http://udisks.freedesktop.org/docs/latest/ . Thanks, Michael -- System Information: Debian Release: jessie/sid APT prefers unstable APT policy: (500, 'unstable'), (200, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.14-1-amd64 (SMP w/4 CPU cores) Locale: LANG=de_DE.utf8, LC_CTYPE=de_DE.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash ---End Message--- ---BeginMessage--- We believe that the bug you reported is now fixed; the following package(s) have been removed from unstable: udisks-glue |1.3.5-1 | source, amd64, arm64, armel, armhf, i386, mips, mipsel, powerpc, ppc64el, s390x, sparc --- Reason --- ROM; depends on obsolete udisks -- Note that the package(s) have simply been removed from the tag database and may (or may not) still be in the pool; this is not a bug. The package(s) will be physically removed automatically when no suite references them (and in the case of source, when no binary references it). Please also remember that the changes have been done on the master archive and will not propagate to any mirrors until the next dinstall run at the earliest. Packages are usually not removed from testing by hand. Testing tracks unstable and will automatically remove packages which were removed from unstable when removing them from testing causes no dependency problems. The release team can force a removal from testing if it is really needed, please contact them if this should be the case. We try to close bugs which have been reported against this package automatically. But please check all old bugs, if they were closed correctly or should have been re-assigned to another package. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 750...@bugs.debian.org. The full log for this bug can be viewed at https://bugs.debian.org/750511 This message was generated automatically; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org. Debian distribution maintenance software pp. Scott Kitterman (the ftpmaster behind the curtain)---End Message---
Bug#645164: marked as done (python-simplemediawiki does not have proper dependencies)
Your message dated Thu, 21 May 2015 23:12:36 + with message-id e1yvzdk-0004yi...@franck.debian.org and subject line Bug#785320: Removed package(s) from unstable has caused the Debian Bug report #645164, regarding python-simplemediawiki does not have proper dependencies to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 645164: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=645164 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: python-simplemediawiki Version: 1.0.2-1 I'm currently using wheezy (testing). 1.0.2 version of python-simplemediawiki requires python-iso8601, which is not in python-simplemediawiki's dependencies. After 1.1, python-simplemediawiki requires kitchen[1], but doesn't require python-iso8601 anymore. kitchen is currently not in packages.debian.org. [1] https://fedorahosted.org/kitchen/ ---End Message--- ---BeginMessage--- Version: 1.0.2-2+rm Dear submitter, as the package python-simplemediawiki has just been removed from the Debian archive unstable we hereby close the associated bug reports. We are sorry that we couldn't deal with your issue properly. For details on the removal, please see https://bugs.debian.org/785320 The version of this package that was in Debian prior to this removal can still be found using http://snapshot.debian.org/. This message was generated automatically; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org. Debian distribution maintenance software pp. Scott Kitterman (the ftpmaster behind the curtain)---End Message---
Bug#762443: marked as done (Removal imminent)
Your message dated Thu, 21 May 2015 22:54:01 + with message-id e1yvzll-0001sv...@franck.debian.org and subject line Bug#784987: Removed package(s) from unstable has caused the Debian Bug report #762443, regarding Removal imminent to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 762443: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=762443 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: src:bluetile Version: 0.6-3 Severity: serious -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi, this is a pending-removal-warning-bug. In order to upgrade pandoc, we will have to upgrade a few packages, including the gtk bindings. This package is not compatible with these and will be removed (unless someone steps up and patches it). Greetings, Joachim - -- System Information: Debian Release: jessie/sid APT prefers unstable APT policy: (500, 'unstable'), (101, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.16-1-amd64 (SMP w/4 CPU cores) Locale: LANG=de_DE.utf8, LC_CTYPE=de_DE.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash -BEGIN PGP SIGNATURE- Version: GnuPG v1 iEYEARECAAYFAlQgDKQACgkQ9ijrk0dDIGwGEQCgpMEAQ/9NTkbHV9buvZ5+lFSl LjAAoKr2b3iPb1nl/iOPfAOYBHCKkms7 =9OwG -END PGP SIGNATURE- ---End Message--- ---BeginMessage--- Version: 0.6-3+rm Dear submitter, as the package bluetile has just been removed from the Debian archive unstable we hereby close the associated bug reports. We are sorry that we couldn't deal with your issue properly. For details on the removal, please see https://bugs.debian.org/784987 The version of this package that was in Debian prior to this removal can still be found using http://snapshot.debian.org/. This message was generated automatically; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org. Debian distribution maintenance software pp. Scott Kitterman (the ftpmaster behind the curtain)---End Message---
Processed: Bug#786469: fix those pesky versions
Processing commands for cont...@bugs.debian.org: found 786469 sysvinit-utils/2.88dsf-59.2 Bug #786469 [sysvinit-utils, util-linux] sysvinit-utils, util-linux: can't upgrade - 'installation run will require temporarily removing the essential package' The source sysvinit-utils and version 2.88dsf-59.2 do not appear to match any binary packages Marked as found in versions sysvinit-utils/2.88dsf-59.2. found 786469 util-linux/2.26.2-4 Bug #786469 [sysvinit-utils, util-linux] sysvinit-utils, util-linux: can't upgrade - 'installation run will require temporarily removing the essential package' Marked as found in versions util-linux/2.26.2-4. thanks Stopping processing here. Please contact me if you need assistance. -- 786469: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=786469 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#785429: marked as done (icedove: FTBFS with new libvpx 1.4)
Your message dated Fri, 22 May 2015 00:07:01 + with message-id e1yvaup-0002zz...@franck.debian.org and subject line Bug#785429: fixed in icedove 31.7.0-1 has caused the Debian Bug report #785429, regarding icedove: FTBFS with new libvpx 1.4 to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 785429: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=785429 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: icedove Version: 31.6.0-1 Severity: serious On a binNMU for the libvpx transition, your package failed to build with: /«PKGBUILDDIR»/mozilla/media/webrtc/trunk/webrtc/modules/video_coding/codecs/vp8/vp8_impl.cc: In member function 'virtual int webrtc::VP8EncoderImpl::InitEncode(const webrtc::VideoCodec*, int, uint32_t)': /«PKGBUILDDIR»/mozilla/media/webrtc/trunk/webrtc/modules/video_coding/codecs/vp8/vp8_impl.cc:183:29: error: 'IMG_FMT_I420' was not declared in this scope raw_ = vpx_img_wrap(NULL, IMG_FMT_I420, codec_.width, codec_.height, ^ /«PKGBUILDDIR»/mozilla/media/webrtc/trunk/webrtc/modules/video_coding/codecs/vp8/vp8_impl.cc: In member function 'virtual int webrtc::VP8EncoderImpl::Encode(const webrtc::I420VideoFrame, const webrtc::CodecSpecificInfo*, const std::vectorwebrtc::VideoFrameType*)': /«PKGBUILDDIR»/mozilla/media/webrtc/trunk/webrtc/modules/video_coding/codecs/vp8/vp8_impl.cc:352:16: error: 'PLANE_Y' was not declared in this scope raw_-planes[PLANE_Y] = const_castuint8_t*(input_image.buffer(kYPlane)); ^ /«PKGBUILDDIR»/mozilla/media/webrtc/trunk/webrtc/modules/video_coding/codecs/vp8/vp8_impl.cc:353:16: error: 'PLANE_U' was not declared in this scope raw_-planes[PLANE_U] = const_castuint8_t*(input_image.buffer(kUPlane)); ^ /«PKGBUILDDIR»/mozilla/media/webrtc/trunk/webrtc/modules/video_coding/codecs/vp8/vp8_impl.cc:354:16: error: 'PLANE_V' was not declared in this scope raw_-planes[PLANE_V] = const_castuint8_t*(input_image.buffer(kVPlane)); ^ make[7]: *** [vp8_impl.o] Error 1 See https://buildd.debian.org/status/fetch.php?pkg=icedovearch=amd64ver=31.6.0-1%2Bb1stamp=1431713936 These constants are now called VPX_*. Regards, Emilio ---End Message--- ---BeginMessage--- Source: icedove Source-Version: 31.7.0-1 We believe that the bug you reported is fixed in the latest version of icedove, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 785...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Christoph Goehre ch...@sigxcpu.org (supplier of updated icedove package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Thu, 21 May 2015 16:19:58 -0400 Source: icedove Binary: icedove icedove-dev icedove-dbg iceowl-extension calendar-google-provider Architecture: source all amd64 Version: 31.7.0-1 Distribution: unstable Urgency: medium Maintainer: Christoph Goehre ch...@sigxcpu.org Changed-By: Christoph Goehre ch...@sigxcpu.org Description: calendar-google-provider - Google Calendar support for lightning- and iceowl-extension icedove- mail/news client with RSS and integrated spam filter support icedove-dbg - Debug Symbols for Icedove icedove-dev - Development files for Icedove iceowl-extension - Calendar Extension for Thunderbird/Icedove Closes: 785429 Changes: icedove (31.7.0-1) unstable; urgency=medium . * [c3c81df] Imported Upstream version 31.7.0 * [471ec7c] rebuild patch queue from patch-queue branch added patches: - fixes/vp8_impl.cc-backporting-naming-for-const.patch (Closes: #785429) * [137ee51] lintian: add override for libpng Checksums-Sha1: 11ee88d2eded4fad67b6fcfedd4cf7b3ec66783e 2919 icedove_31.7.0-1.dsc fb6da580a9cfbaa83f06290e3bc25381288668a2 139024484 icedove_31.7.0.orig.tar.xz b5cf1fdce14779728cbe46af235988898d7f3840 449568 icedove_31.7.0-1.debian.tar.xz eb9420d8a83dddafec78863ee65e84b48b0a1fad 102608 calendar-google-provider_31.7.0-1_all.deb e32b2a3df889befd158cf4b9871f84594a96ce4b 203818066 icedove-dbg_31.7.0-1_amd64.deb ff155427b5a9126732b0ddcb6432f8d77b7002f2 5176432 icedove-dev_31.7.0-1_amd64.deb 202015b0ec0eb26de75fa45e67d4e04d7bf6958f
Bug#750743: marked as done (gspiceui: Please update to use wxwidgets3.0)
Your message dated Fri, 22 May 2015 01:19:07 + with message-id e1yvbcb-0002t3...@franck.debian.org and subject line Bug#750743: fixed in gspiceui 1.1.00+dfsg-1 has caused the Debian Bug report #750743, regarding gspiceui: Please update to use wxwidgets3.0 to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 750743: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=750743 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Source: gspiceui Version: 1.0.00+dfsg-1 Severity: important Tags: sid jessie User: freewx-ma...@lists.alioth.debian.org Usertags: wx3.0 Control: block 748169 by -1 Dear maintainer, We're aiming to migrate the archive to using wxwidgets3.0 instead of wxwidgets2.8, and intend to drop wxwidgets2.8 before jessie is released. Looking at upstream's SVN repo, I see r171 added wx3 support: http://sourceforge.net/p/gspiceui/code/171/ So packaging a snapshot from SVN or backporting the required changes should allow you to update to using wxwidgets3.0. If you hit any problems with getting packages working with wxwidgets3.0 which you can't overcome, let me know and I'll try to help. Cheers, Olly ---End Message--- ---BeginMessage--- Source: gspiceui Source-Version: 1.1.00+dfsg-1 We believe that the bug you reported is fixed in the latest version of gspiceui, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 750...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Gudjon I. Gudjonsson gud...@gudjon.org (supplier of updated gspiceui package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Thu, 21 May 2015 22:05:08 +0200 Source: gspiceui Binary: gspiceui Architecture: source Version: 1.1.00+dfsg-1 Distribution: unstable Urgency: medium Maintainer: Gudjon I. Gudjonsson gud...@gudjon.org Changed-By: Gudjon I. Gudjonsson gud...@gudjon.org Description: gspiceui - Graphical user interface for gnucap and ngspice Closes: 749860 750743 Changes: gspiceui (1.1.00+dfsg-1) unstable; urgency=medium . * New release version * Bump standards version to 3.9.6 * Change wx dependencies to version 3.0 (Closes: #750743) * Update copyright file, new download site and license changed to GPL-3 * Add patch 01_makefile to fix errors in makefile * Add patch 02_fix_compilation to fix a source file * Add patch 03_manpage to fix minor errors in manpage * Fix description (Closes: #749860) * Change dependency on gwave to suggests * Make vcs fields canonical * Update hardening wrappers to dpkg-buildflags. It doesn't compile so they are commented out in this release. * Add patch to change gwave2 to gwave * Add more information on how to download sources to README.Debian * Add patch 05_manual_path to fix path to html manual * Fix project homepage in control file * Remove DM allow upload * Correct version in desktop file Checksums-Sha1: a940229f325024f73801165f5257ba4d9c228b65 1932 gspiceui_1.1.00+dfsg-1.dsc 95a58f184b4901e5bf41e2f4f01b8d13d7f8 1005784 gspiceui_1.1.00+dfsg.orig.tar.gz 72c22f50f94c5d01d0c2b49bfa30454b27479080 5452 gspiceui_1.1.00+dfsg-1.debian.tar.xz Checksums-Sha256: abc58eec4c4c075069ff42c1ed2a39861c4fcb3da3df3f1ae64bd810205d29e3 1932 gspiceui_1.1.00+dfsg-1.dsc b19dec57a3a03f8fc1f75995070e161500578b47e9126b1dce9a5371106edcd3 1005784 gspiceui_1.1.00+dfsg.orig.tar.gz b88a1c2d13a43e95954a984a33a88d15f12c3fbb066ed873068549e72e229c9b 5452 gspiceui_1.1.00+dfsg-1.debian.tar.xz Files: 8baa8d951ef2db11ce20a3ec71325f66 1932 electronics optional gspiceui_1.1.00+dfsg-1.dsc d9bf98b151f648fa72aae6dbbb48567b 1005784 electronics optional gspiceui_1.1.00+dfsg.orig.tar.gz 669aa382ee1964837f21916513e302ae 5452 electronics optional gspiceui_1.1.00+dfsg-1.debian.tar.xz -BEGIN PGP SIGNATURE- Version: GnuPG v1 iQIcBAEBAgAGBQJVXoMjAAoJEBgUewc7rSsHyXoP/0T/w2R+Kxe/WsaI0EAozJq7 FmSgrVs7lq4hK7KyGYMGyLIf/SMZ91T/k9pJClasY7E+rweMOV6FY0UPMh52ODbl YzuGySfpK24Dt1GeQoDkvczQmAmzmD7wMvVfDm0ZrnklfDb0cPb5JpBEcJe2EJIZ hhg0iGtET4m3UU8bfwdE3i2zL7dkRjX5ccnvdxFg8mim2DvoNN1rHqONQ+MlktUx ZmKTlM30q39xivlZdfyhkUAD4fb80RBpsZet2eb7J6RxPkdO2UPKETQpE2KxEq1B
Processed: Re: Bug#773466: Version 6.4.3 upstream
Processing control commands: unblock 773466 by 759044 Bug #773466 [tribler] New upstream version 6.4.3 includes security fixes 773466 was blocked by: 759044 773466 was not blocking any bugs. Removed blocking bug(s) of 773466: 759044 -- 773466: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=773466 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#786469: sysvinit-utils, util-linux: can't upgrade - 'installation run will require temporarily removing the essential package'
On Fri, May 22, 2015 at 12:18:07AM +0100, James Cowgill wrote: E: This installation run will require temporarily removing the essential package util-linux:i386 due to a Conflicts/Pre-Depends loop. This is often bad, but if you really want to do it, activate the APT::Force-LoopBreak option. I hit this trying to use sbuild to build a package in an unstable chroot. For the benefit of anyone else who hits this in that context and ends up reading this bug report, I found I could avoid it by telling schroot not to upgrade the chroot before building, like so: sbuild --no-apt-upgrade --no-apt-distupgrade -dunstable PACKAGE.dsc This is only a good idea if your unstable chroot was updated recently though. Cheers, Olly -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#786332: Full path in FastCGIExternalServer
Hi
Running additionnal tests, I discovered the previous nmu was flawed.
FastCGIExternalServer requires the full docroot path /var/www/html/.
Attached is the revised nmu, that fixes that.
I just uploaded it to delayed/6, where the old one was.
Regards
--
Nirgal
diff -Nru openjpeg-1.5.2/debian/changelog openjpeg-1.5.2/debian/changelog
--- openjpeg-1.5.2/debian/changelog 2014-10-04 13:51:33.0 +0200
+++ openjpeg-1.5.2/debian/changelog 2015-05-22 00:36:58.0 +0200
@@ -1,3 +1,22 @@
+openjpeg (1:1.5.2-3.1) unstable; urgency=high
+
+ * Non-maintainer upload.
+ * Apache 2.4 transition: (Closes: #786332)
+- d/openjpip.conf: Changed documentroot path to /var/www/html;
+ changed localhost by 127.0.0.1 to support ipv6 enabled hosts.
+- Use dh_apache2:
+ . d/rules: Added --with apache2.
+ . d/openjpip-server.install: Drop installs to /etc/apache2/mods-available
+ . Drop d/openjpip-server.prerm.
+ . d/control: Add build-depends on dh-apache2, replace depends on
+apache2.2-bin by ${misc:Recommends}, add recommends on
+libapache2-mod-fastcgi.
+ . New d/openjpip-server.apache2 to set up the configuration.
+ . Install as a conf-available: Renamed openjpip.conf to
+openjpip-server.conf, removed openjpip.load, new maintscript.
+
+ -- Jean-Michel Vourgère nir...@debian.org Wed, 20 May 2015 21:52:22 +0200
+
openjpeg (1:1.5.2-3) unstable; urgency=medium
* epoch upload to resolve #760874 completely
diff -Nru openjpeg-1.5.2/debian/control openjpeg-1.5.2/debian/control
--- openjpeg-1.5.2/debian/control 2014-04-01 12:39:01.0 +0200
+++ openjpeg-1.5.2/debian/control 2015-05-20 22:46:15.0 +0200
@@ -8,6 +8,7 @@
Homepage: http://www.openjpeg.org
Build-Depends:
debhelper (= 9)
+ , dh-apache2
, cmake (= 2.8.0)
, javahelper (= 0.37~)
, default-jdk
@@ -120,7 +121,8 @@
Section: graphics
Architecture: any
Multi-Arch: foreign
-Depends: ${shlibs:Depends}, ${misc:Depends}, libwww-perl, apache2.2-bin, spawn-fcgi (= 1.6.1)
+Depends: ${shlibs:Depends}, ${misc:Depends}, libwww-perl, spawn-fcgi (= 1.6.1)
+Recommends: ${misc:Recommends}, libapache2-mod-fastcgi
Description: JPIP server for JPEG 2000 files
OpenJPIP software is an implementation of JPEG 2000 Part9: Interactivity tools,
APIs and protocols (JPIP). For more info about JPIP, check the website:
diff -Nru openjpeg-1.5.2/debian/openjpip.conf openjpeg-1.5.2/debian/openjpip.conf
--- openjpeg-1.5.2/debian/openjpip.conf 2014-04-01 12:39:01.0 +0200
+++ openjpeg-1.5.2/debian/openjpip.conf 1970-01-01 01:00:00.0 +0100
@@ -1,4 +0,0 @@
-# This is the config file for openjpip-server
-IfModule mod_fastcgi.c
-FastCGIExternalServer /var/www/openjpip -host localhost:3000
-/IfModule
diff -Nru openjpeg-1.5.2/debian/openjpip-server.apache2 openjpeg-1.5.2/debian/openjpip-server.apache2
--- openjpeg-1.5.2/debian/openjpip-server.apache2 1970-01-01 01:00:00.0 +0100
+++ openjpeg-1.5.2/debian/openjpip-server.apache2 2015-05-20 22:25:39.0 +0200
@@ -0,0 +1 @@
+conf debian/openjpip-server.conf
diff -Nru openjpeg-1.5.2/debian/openjpip-server.conf openjpeg-1.5.2/debian/openjpip-server.conf
--- openjpeg-1.5.2/debian/openjpip-server.conf 1970-01-01 01:00:00.0 +0100
+++ openjpeg-1.5.2/debian/openjpip-server.conf 2015-05-22 00:34:55.0 +0200
@@ -0,0 +1,4 @@
+# This is the config file for openjpip-server
+IfModule mod_fastcgi.c
+FastCGIExternalServer /var/www/html/openjpip -host 127.0.0.1:3000
+/IfModule
diff -Nru openjpeg-1.5.2/debian/openjpip-server.install openjpeg-1.5.2/debian/openjpip-server.install
--- openjpeg-1.5.2/debian/openjpip-server.install 2014-04-01 12:39:01.0 +0200
+++ openjpeg-1.5.2/debian/openjpip-server.install 2015-05-20 22:01:41.0 +0200
@@ -1,3 +1 @@
usr/bin/opj_server usr/lib/openjpip-server
-debian/openjpip.load /etc/apache2/mods-available
-debian/openjpip.conf /etc/apache2/mods-available
diff -Nru openjpeg-1.5.2/debian/openjpip-server.maintscript openjpeg-1.5.2/debian/openjpip-server.maintscript
--- openjpeg-1.5.2/debian/openjpip-server.maintscript 1970-01-01 01:00:00.0 +0100
+++ openjpeg-1.5.2/debian/openjpip-server.maintscript 2015-05-20 22:21:44.0 +0200
@@ -0,0 +1,2 @@
+mv_conffile /etc/apache2/mods-available/openjpip.conf /etc/apache2/conf-available/openjpip-server.conf 1:1.5.2-3.1~
+rm_conffile /etc/apache2/mods-available/openjpip.load 1:1.5.2-3.1~
diff -Nru openjpeg-1.5.2/debian/openjpip-server.prerm openjpeg-1.5.2/debian/openjpip-server.prerm
--- openjpeg-1.5.2/debian/openjpip-server.prerm 2014-04-01 12:39:01.0 +0200
+++ openjpeg-1.5.2/debian/openjpip-server.prerm 1970-01-01 01:00:00.0 +0100
@@ -1,15 +0,0 @@
-#!/bin/bash
-
-set -e
-
-#DEBHELPER#
-
-if [ $1 != remove -a $1 != purge ]; then
- exit 0
-fi
-
-if [ -e /etc/apache2/apache2.conf ]; then
- a2dismod openjpip || true
-fi
-
-exit 0
diff -Nru openjpeg-1.5.2/debian/rules openjpeg-1.5.2/debian/rules
---
Bug#786475: ntfs-3g: CVE-2015-3202
Source: ntfs-3g
Version: 1:2013.1.13AR.3-2
Severity: grave
Tags: security patch upstream
Justification: user security hole
Hi Laszlo
ntfs-3g in jessie and above is similarly affected by CVE-2015-3202
since ntfs-3g since 1:2013.1.13AR.3-2 builds with internal fuse copy.
The patch I have used to prepare the updates for jessie is attached.
ntfs-3g though should try to use the system fuse and not the embedded
copy, could you check to switch this back?
Regards,
Salvatore
Description: Fix CVE-2015-3202
Missing scrubbing of the environment before executing a mount or umount
of a filesystem.
Origin: backport
Author: Miklos Szeredi mik...@szeredi.hu
Last-Update: 2015-05-19
---
lib/mount_util.c | 23 +--
1 file changed, 17 insertions(+), 6 deletions(-)
--- a/libfuse-lite/mount_util.c
+++ b/libfuse-lite/mount_util.c
@@ -66,6 +66,7 @@ int fuse_mnt_add_mount(const char *progn
return -1;
}
if (res == 0) {
+char *env = NULL;
char templ[] = /tmp/fusermountXX;
char *tmp;
@@ -87,8 +88,8 @@ int fuse_mnt_add_mount(const char *progn
exit(1);
}
rmdir(tmp);
-execl(/sbin/mount, /sbin/mount, -F, type, -o, opts,
- fsname, mnt, NULL);
+execle(/sbin/mount, /sbin/mount, -F, type, -o, opts,
+ fsname, mnt, NULL, env);
fprintf(stderr, %s: failed to execute /sbin/mount: %s\n, progname,
strerror(errno));
exit(1);
@@ -120,9 +121,16 @@ int fuse_mnt_umount(const char *progname
return -1;
}
if (res == 0) {
+char *env = NULL;
+
setuid(geteuid());
-execl(/sbin/umount, /sbin/umount, !lazy ? -f : NULL, mnt,
- NULL);
+if (!lazy) {
+execle(/sbin/umount, /sbin/umount, -f, mnt,
+ NULL, env);
+} else {
+execle(/sbin/umount, /sbin/umount, mnt,
+ NULL, env);
+}
fprintf(stderr, %s: failed to execute /sbin/umount: %s\n, progname,
strerror(errno));
exit(1);
@@ -302,6 +310,7 @@ int fuse_mnt_add_mount(const char *progn
return 0;
}
if (res == 0) {
+char *env = NULL;
char templ[] = /tmp/fusermountXX;
char *tmp;
@@ -325,8 +334,8 @@ int fuse_mnt_add_mount(const char *progn
exit(1);
}
rmdir(tmp);
-execl(/bin/mount, /bin/mount, -i, -f, -t, type, -o, opts,
- fsname, mnt, NULL);
+execle(/bin/mount, /bin/mount, -i, -f, -t, type, -o, opts,
+ fsname, mnt, NULL, env);
fprintf(stderr, %s: failed to execute /bin/mount: %s\n, progname,
strerror(errno));
exit(1);
Bug#750910: sitplus: diff for NMU version 1.0.3-4.1
Control: tags 750910 + patch
Given the difficulties in packaging sitplus 1.1.0, I had a go at
patching 1.0.3-4 to work with wxwidgets3.0.
The attached NMU diff results in a package which builds and seems to
work to the extent that I can test it without any of the hardware it
seems to need.
The changes to do with wxGenericCollapsiblePane may look a bit odd
- the public class here seems to be wxCollapsiblePane, but where there
isn't a native implementation, wx uses:
#define wxCollapsiblePane wxGenericCollapsiblePane
So that is why I check for both class names in the patch - the reported
class name could be either, depending whether there is a native
implementation or not.
Let me know if you'd like me to upload the NMU.
Cheers,
Olly
diff -Nru sitplus-1.0.3/debian/changelog sitplus-1.0.3/debian/changelog
--- sitplus-1.0.3/debian/changelog 2013-07-01 22:55:55.0 +1200
+++ sitplus-1.0.3/debian/changelog 2015-05-22 16:07:33.0 +1200
@@ -1,3 +1,10 @@
+sitplus (1.0.3-4.1) unstable; urgency=low
+
+ * Non-maintainer upload.
+ * Update to use wxWidgets 3.0. (Closes: #750910)
+
+ -- Olly Betts o...@survex.com Fri, 22 May 2015 16:07:22 +1200
+
sitplus (1.0.3-4) unstable; urgency=low
* Team upload.
diff -Nru sitplus-1.0.3/debian/control sitplus-1.0.3/debian/control
--- sitplus-1.0.3/debian/control 2013-07-01 22:53:33.0 +1200
+++ sitplus-1.0.3/debian/control 2014-03-19 16:46:50.0 +1300
@@ -7,10 +7,10 @@
Andreas Tille ti...@debian.org
Build-Depends: debhelper (= 9), cmake, libpoco-dev, libboost-dev,
libboost-program-options-dev, libboost-thread-dev, libboost-system-dev,
- wx2.8-headers, libwxbase2.8-dev, libbluetooth-dev, libconfig-dev, libsdl1.2-dev,
+ libbluetooth-dev, libconfig-dev, libsdl1.2-dev,
libopencv-dev, libhighgui-dev, libv4l-dev, libportmidi-dev,
libboost-filesystem-dev, asciidoc, libsdl-gfx1.2-dev, libsdl-image1.2-dev,
- libwxgtk2.8-dev, doxygen, libxtst-dev
+ libwxgtk3.0-dev, doxygen, libxtst-dev
Standards-Version: 3.9.3
Homepage: http://sitplus.crea-si.com
Vcs-Git: git://git.debian.org/debian-med/sitplus.git
diff -Nru sitplus-1.0.3/debian/patches/fix-printf-formats-for-size_t.patch sitplus-1.0.3/debian/patches/fix-printf-formats-for-size_t.patch
--- sitplus-1.0.3/debian/patches/fix-printf-formats-for-size_t.patch 1970-01-01 12:00:00.0 +1200
+++ sitplus-1.0.3/debian/patches/fix-printf-formats-for-size_t.patch 2015-05-22 14:22:39.0 +1200
@@ -0,0 +1,72 @@
+Description: Fix printf formats for size_t
+ Avoids warnings when sizeof(unsigned) != sizeof(size_t), and potential
+ misbehaviour on some platforms.
+Author: Olly Betts o...@survex.com
+Forwarded: no
+Last-Update: 2015-05-22
+
+--- sitplus-1.0.3.orig/3rdparty/nvwa/debug_new.cpp
sitplus-1.0.3/3rdparty/nvwa/debug_new.cpp
+@@ -464,7 +464,7 @@ static void* alloc_mem(size_t size, cons
+ #else
+ fast_mutex_autolock lock(new_output_lock);
+ fprintf(new_output_fp,
+-Out of memory when allocating %u bytes\n,
++Out of memory when allocating %zu bytes\n,
+ size);
+ fflush(new_output_fp);
+ _DEBUG_NEW_ERROR_ACTION;
+@@ -499,7 +499,7 @@ static void* alloc_mem(size_t size, cons
+ {
+ fast_mutex_autolock lock(new_output_lock);
+ fprintf(new_output_fp,
+-new%s: allocated %p (size %u, ,
++new%s: allocated %p (size %zu, ,
+ is_array ? [] : ,
+ pointer, size);
+ if (line != 0)
+@@ -548,7 +548,7 @@ static void free_pointer(void* pointer,
+ msg = delete after new[];
+ fast_mutex_autolock lock(new_output_lock);
+ fprintf(new_output_fp,
+-%s: pointer %p (size %u)\n\tat ,
++%s: pointer %p (size %zu)\n\tat ,
+ msg,
+ (char*)ptr + ALIGNED_LIST_ITEM_SIZE,
+ ptr-size);
+@@ -581,7 +581,7 @@ static void free_pointer(void* pointer,
+ {
+ fast_mutex_autolock lock(new_output_lock);
+ fprintf(new_output_fp,
+-delete%s: freed %p (size %u, %u bytes still allocated)\n,
++delete%s: freed %p (size %zu, %zu bytes still allocated)\n,
+ is_array ? [] : ,
+ (char*)ptr + ALIGNED_LIST_ITEM_SIZE,
+ ptr-size, total_mem_alloc);
+@@ -621,7 +621,7 @@ int check_leaks()
+ }
+ #endif
+ fprintf(new_output_fp,
+-Leaked object at %p (size %u, ,
++Leaked object at %p (size %zu, ,
+ pointer,
+ ptr-size);
+ if (ptr-line != 0)
+@@ -671,7 +671,7 @@ int check_mem_corruption()
+ {
+ #endif
+ fprintf(new_output_fp,
+-Heap data corrupt near %p (size %u, ,
++Heap data corrupt near %p (size %zu, ,
+ pointer,
+ ptr-size);
+ #if _DEBUG_NEW_TAILCHECK
+@@ -679,7 +679,7 @@ int
Processed: sitplus: diff for NMU version 1.0.3-4.1
Processing control commands: tags 750910 + patch Bug #750910 [src:sitplus] sitplus: Please update to use wxwidgets3.0 Added tag(s) patch. -- 750910: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=750910 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#783233: RFS: libapache-mod-jk 1:1.2.40+svn150520-1 [RC]
On 05/21/2015 01:00 PM, Markus Koschany wrote: Control: tags -1 pending Hi, I have prepared a new upstream release of libapache-mod-jk which fixes RC bug #783233, better known as CVE-2014-8111. I would be glad if someone reviewed the package and uploaded it to unstable. Hello Markus, Thank you for your efforts here. I have reviewed the packaging and differences against the current version, and have sponsored the upload to unstable. There is a lintian warning for apache2-deprecated-auth-config, but I think it can be addressed in a subsequent upload. Cheers, tony signature.asc Description: OpenPGP digital signature
Bug#783233: marked as done (CVE-2014-8111: mod_jk ignores JkUnmount rules for subtrees of previous JkMount rules)
Your message dated Fri, 22 May 2015 05:18:52 + with message-id e1yvfmc-0006kr...@franck.debian.org and subject line Bug#783233: fixed in libapache-mod-jk 1:1.2.40+svn150520-1 has caused the Debian Bug report #783233, regarding CVE-2014-8111: mod_jk ignores JkUnmount rules for subtrees of previous JkMount rules to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 783233: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=783233 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Source: libapache-mod-jk Severity: serious Tags: security Hi, the following vulnerability was published for libapache-mod-jk. CVE-2014-8111[0]: | Apache Tomcat Connectors (mod_jk) before 1.2.41 ignores JkUnmount | rules for subtrees of previous JkMount rules, which allows remote | attackers to access otherwise restricted artifacts via unspecified | vectors. If you fix the vulnerability please also make sure to include the CVE (Common Vulnerabilities Exposures) id in your changelog entry. For further information see: [0] https://security-tracker.debian.org/tracker/CVE-2014-8111 http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2014-8111 Please adjust the affected versions in the BTS as needed. The upstream fix is here: http://svn.apache.org/r1647017 Feel freet to lower the severiy if you believe the issue to be minor. I'm not familiar enough with the software to be able to judge. Cheers, -- Raphaël Hertzog ◈ Debian Developer Support Debian LTS: http://www.freexian.com/services/debian-lts.html Learn to master Debian: http://debian-handbook.info/get/ ---End Message--- ---BeginMessage--- Source: libapache-mod-jk Source-Version: 1:1.2.40+svn150520-1 We believe that the bug you reported is fixed in the latest version of libapache-mod-jk, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 783...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Markus Koschany a...@gambaru.de (supplier of updated libapache-mod-jk package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Thu, 21 May 2015 17:53:24 +0200 Source: libapache-mod-jk Binary: libapache2-mod-jk libapache-mod-jk-doc Architecture: source all amd64 Version: 1:1.2.40+svn150520-1 Distribution: unstable Urgency: high Maintainer: Debian Java Maintainers pkg-java-maintain...@lists.alioth.debian.org Changed-By: Markus Koschany a...@gambaru.de Description: libapache-mod-jk-doc - Documentation of libapache2-mod-jk package libapache2-mod-jk - Apache 2 connector for the Tomcat Java servlet engine Closes: 783233 Changes: libapache-mod-jk (1:1.2.40+svn150520-1) unstable; urgency=high . * Team upload. * Imported Upstream SVN snapshot version 1.2.40+svn150520. - Fix CVE-2014-8111: (Closes: #783233) Apache Tomcat Connectors (mod_jk) ignored JkUnmount rules for subtrees of previous JkMount rules, which allows remote attackers to access otherwise restricted artifacts via unspecified vectors. * debian/control: Build-Depend on debhelper = 9. * Remove source.lintian-overrides since we now build-depend on debhelper =9. * Drop 0004-corrupted-worker-activation-status.patch. Fixed upstream. * debian/rules: - Disable sed command in debian/rules. Apparently not necessary for this release. - Run buildconf.sh before dh_auto_configure step since this is a requirement for building SVN snapshots. - Update dh_auto_clean override. Ensure that the package can be built twice in a row. * debian/control: - Add autoconf to Build-Depends. - Add automake to Build-Depends. - Remove Conflicts and Replaces fields because they are obsolete. * Add disable-libtool-check.patch and fix a FTBFS. We already build-depend on libtool but the script is not smart enough. * Add fix-privacy-breach.patch and fix lintian errors about privacy breach logo. * Update debian/copyright information. Add missing BSD-3-clause license. * Add README.source. Checksums-Sha1: 02223ab09d0ac9f826d6a7db1e04058a951b69e7 2254 libapache-mod-jk_1.2.40+svn150520-1.dsc e6b595d75a3767d2ec228506b801ec6c1f90b7b8 1045078
Bug#750910: sitplus: diff for NMU version 1.0.3-4.1
Hi Olly, On Fri, May 22, 2015 at 04:18:17PM +1200, Olly Betts wrote: Control: tags 750910 + patch Given the difficulties in packaging sitplus 1.1.0, I had a go at patching 1.0.3-4 to work with wxwidgets3.0. Cool. This relaxes the pressure to work on the new version. Let me know if you'd like me to upload the NMU. Please go on with the NMU. Extra points if you would commit your change to Git which has ACLs set so any DD has commit permissions. Thanks for your effort Andreas. -- http://fam-tille.de -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: fixed 786475 in 1:2014.2.15AR.2-1+deb8u1
Processing commands for cont...@bugs.debian.org: fixed 786475 1:2014.2.15AR.2-1+deb8u1 Bug #786475 [src:ntfs-3g] ntfs-3g: CVE-2015-3202 The source 'ntfs-3g' and version '1:2014.2.15AR.2-1+deb8u1' do not appear to match any binary packages Marked as fixed in versions ntfs-3g/1:2014.2.15AR.2-1+deb8u1. thanks Stopping processing here. Please contact me if you need assistance. -- 786475: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=786475 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#786436: ncurses FTBFS: configure loops
Am 21.05.2015 um 19:48 schrieb Helmut Grohne: Control: tags -1 - moreinfo Control: severity -1 serious On Thu, May 21, 2015 at 07:24:18PM +0200, Helmut Grohne wrote: | Looking for ncursesw-config | checking for ncursesw-config... no | checking for ncursesw6-config... no | checking for ncursesw5-config... no There is a notable difference to successful builds here. Those say: | checking for ncursesw5-config... ncursesw5-config Now where does that come from? ncurses-bin. Well, it came from there, but it no longer does. Ideally it would come from the obj-wide build tree (we link the test programs with the just-built library), but neither the ncursesw5-config script nor the .pc files exist there; they are only created upon make install (or make install.libs). These builds used the old ncurses-bin that contained ncurses5-config. Now this doesn't tell me how to fix it, but it tells me that ncurses is seriously broken. Maybe Build-Depends: libncursesw5-dev? But that sounds very bad from a bootstrap perspective. Might at least be temporarily necessary anyway until the -config scripts are moved back to ncurses-bin; I'll do that if nobody comes up with a better idea in the next few days. Thanks, Sven -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: [bts-link] source package ming
Processing commands for cont...@bugs.debian.org: # # bts-link upstream status pull for source package ming # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html # user bts-link-upstr...@lists.alioth.debian.org Setting user to bts-link-upstr...@lists.alioth.debian.org (was bts-link-de...@lists.alioth.debian.org). # remote status report for #752629 (http://bugs.debian.org/752629) # Bug title: ming is licensed under the PHP license and is not PHP # * https://github.com/libming/libming/issues/42 # * remote status changed: closed - open # * reopen upstream tags 752629 - fixed-upstream Bug #752629 [ming] ming is licensed under the PHP license and is not PHP Removed tag(s) fixed-upstream. usertags 752629 - status-closed Usertags were: status-closed. Usertags are now: . usertags 752629 + status-open There were no usertags set. Usertags are now: status-open. thanks Stopping processing here. Please contact me if you need assistance. -- 752629: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=752629 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#783890: Solution for conflicting svg file
By having the application-x-squeak-project.svg file in ./activity/ directory, the setup.py install step will create a symlink to that file in /usr/share/icons/sugar/scalable/mimetypes/, in order to install that file as the icon for a custom mime type declared in ./activty/activity.info. That same mime type icon is already provided by sugar-artwork (sugar-icon-theme), so there is no need for Etoys to provide this icon. I have contacted the upstream maintainer, but for the time being I recommend to remove the icon with a patch in debian/patches. I have attached to this reply the patch for https://anonscm.debian.org/cgit/pkg-sugar/sugar-etoys-activity.git/ to do so. From e8a05b273e87b07ce89b54e57e3f80f8d38ecd6e Mon Sep 17 00:00:00 2001 From: Martin Abente Lahaye t...@sugarlabs.org Date: Thu, 21 May 2015 15:01:10 -0400 Subject: [PATCH] Remove conflicting svg icon. Signed-off-by: Martin Abente Lahaye t...@sugarlabs.org --- debian/patches/1002_remove_conflicting_icon.patch | 19 +++ debian/patches/series | 1 + 2 files changed, 20 insertions(+) create mode 100644 debian/patches/1002_remove_conflicting_icon.patch diff --git a/debian/patches/1002_remove_conflicting_icon.patch b/debian/patches/1002_remove_conflicting_icon.patch new file mode 100644 index 000..043468c --- /dev/null +++ b/debian/patches/1002_remove_conflicting_icon.patch @@ -0,0 +1,19 @@ +Description: Remove conflicting svg icon +Author: Martin Abente Lahaye t...@sugarlabs.org +Last-Update: 2015-05-21 + +--- a/activity/application-x-squeak-project.svg /dev/null +@@ -1,12 +0,0 @@ +-?xml version=1.0 ?!DOCTYPE svg PUBLIC '-//W3C//DTD SVG 1.1//EN' 'http://www.w3.org/Graphics/SVG/1.1/DTD/svg11.dtd' [ +- !ENTITY stroke_color #010101 +- !ENTITY fill_color #FF +-]svg enable-background=new 0 0 55 55 height=55px version=1.1 viewBox=0 0 55 55 width=55px x=0px xml:space=preserve xmlns=http://www.w3.org/2000/svg; xmlns:xlink=http://www.w3.org/1999/xlink; y=0pxg display=block id=activity-etoys +- g display=inline +- path d=M38.395,40.393c-0.614,0.214-9.218-9.666-9.849-9.828c-0.632-0.163-13.004,3.906-13.416,3.423c-0.412-0.484,6.202-11.419,6.177-12.038c-0.024-0.619-8.007-10.704-7.643-11.22c0.363-0.517,13.466,2.533,14.08,2.317c0.613-0.216,8.677-10.799,9.305-10.634c0.627,0.165,1.631,12.98,2.036,13.472c0.402,0.49,12.795,4.16,12.813,4.783c0.021,0.621-12.244,5.76-12.601,6.282C38.941,27.473,39.009,40.179,38.395,40.393z fill=fill_color; id=path4637 stroke=stroke_color; stroke-linecap=round stroke-linejoin=bevel stroke-width=3.5/ +- path d=M12.729,38.05L3.156,52.411l0,0 fill=none id=path5528 stroke=stroke_color; stroke-linecap=round stroke-width=3.5/ +- path d=M21.283,38.05l-9.574,14.361 fill=none id=path5530 stroke=stroke_color; stroke-linecap=round stroke-width=3.5/ +- path d=M29.834,38.05l-9.572,14.361 fill=none id=path5532 stroke=stroke_color; stroke-linecap=round stroke-width=3.5/ +- /g +-/g/svg +- diff --git a/debian/patches/series b/debian/patches/series index 73440ce..44fc17e 100644 --- a/debian/patches/series +++ b/debian/patches/series @@ -1 +1,2 @@ 1001_use_toolkit-gtk3.patch +1002_remove_conflicting_icon.patch -- 1.9.1
Processed: fixed 786439 in 2.9.3-15+deb8u1
Processing commands for cont...@bugs.debian.org: fixed 786439 2.9.3-15+deb8u1 Bug #786439 [src:fuse] fuse: CVE-2015-3202 Marked as fixed in versions fuse/2.9.3-15+deb8u1. thanks Stopping processing here. Please contact me if you need assistance. -- 786439: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=786439 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#785356: xrdp Oh no! Something has gone wrong. is back
Hello Joachim, just a small addition: to some extend I could get resolution to e.g. 1024x768 by some commands xrandr -s 1024x768 in a row. When the resolution in ~/.config/monitors.xml is modified, then it does not resize and is quite usable. (If one takes the risk of using a self built tigervnc package ... the alternative is to change DE.) Kind regards, Bernhard -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#786436: ncurses FTBFS: configure loops
On Thu, May 21, 2015 at 09:06:24PM +0200, Sven Joachim wrote: Might at least be temporarily necessary anyway until the -config scripts are moved back to ncurses-bin; I'll do that if nobody comes up with a better idea in the next few days. I have no objections to doing this temporarily and no better idea. Can you just do that now? We can still figure out a better solution later. Thanks Helmut -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: closing 785938
Processing commands for cont...@bugs.debian.org: close 785938 0.16.0-1 Bug #785938 [ruby-celluloid] vagrant: Gem conflicts Marked as fixed in versions ruby-celluloid/0.16.0-1. Bug #785938 [ruby-celluloid] vagrant: Gem conflicts Marked Bug as done thanks Stopping processing here. Please contact me if you need assistance. -- 785938: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=785938 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
