Bug#769646: still happening with android-libcutils 21-5
Control: tags 769646 + patch On 27/11/14 20:51, Simon McVittie wrote: In the short term, the attached should work for the ability to build android-platform-build on the architectures where android-libutils exists at all (amd64 and i386). Here is the patch that I had intended to attach. I would recommend test-building the whole stack in an i386 chroot before uploading, using linux32(1) to get the right uname (sbuild-createchroot sets this up for you automatically). S diff -Nru android-platform-system-core-21/debian/patches/libandroidcutils_makefile_pkgconfig android-platform-system-core-21/debian/patches/libandroidcutils_makefile_pkgconfig --- android-platform-system-core-21/debian/patches/libandroidcutils_makefile_pkgconfig 2014-11-18 10:59:50.0 + +++ android-platform-system-core-21/debian/patches/libandroidcutils_makefile_pkgconfig 2014-11-27 20:37:11.0 + @@ -58,7 +58,7 @@ +ifeq ($(shell uname -m), armhf) + commonSources += atomic.c +endif -+ifeq ($(shell uname -m), i386) ++ifeq ($(shell uname -m | sed -e 's/i[3-9]86/i386/'), i386) + commonSources += atomic.c +endif +ifeq ($(shell uname -m), mips)
Processed: Re: Bug#769646: still happening with android-libcutils 21-5
Processing control commands: tags 769646 + patch Bug #769646 [android-libcutils-dev] android-libutils: undefined references in /usr/lib/android/libutils.so Added tag(s) patch. -- 769646: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=769646 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: found 771274 in 2.20.1-5.3
Processing commands for cont...@bugs.debian.org: found 771274 2.20.1-5.3 Bug #771274 [src:util-linux] util-linux: CVE-2014-9114: command injection flaw in blkid Marked as found in versions util-linux/2.20.1-5.3. thanks Stopping processing here. Please contact me if you need assistance. -- 771274: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=771274 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#771287: systemd: Multiple DMs can be started at the same time or none under systemd
Package: systemd Version: 215-7 Severity: serious We are starting to see multiple bug reports about several display managers started at boot. In addition, if /etc/X11/default-display-manager if changed manually, we can end up in a situation where no display manager is started at all on system boot. This is due to the fact that some display manager are using init scripts only, and the dynamic converted version of this unit is then started. Some systemd units as well are not checking /etc/X11/default-display-manager (see http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=748668 for more details). One solution would be to convert all dms to ship systemd services with the same template and /etc/X11/default-display-manager check. One side-effect is that if you install multiple dms, you will always end up with a Status: degraded in systemctl. A less invasive solution is to create and patch systemd generators to dynamically (at each boot) mask in memory all sysv-init scripts-only services that don't match /etc/X11/default-display-manager, and redirect the default configured dm to the selected systemd or sysv-init unit. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#769947: mate-terminal: Not related to xmonad for me
Hi Ben, On Fr 28 Nov 2014 00:39:17 CET, Ben Whyall wrote: Package: mate-terminal Version: 1.8.1+dfsg1-2 Followup-For: Bug #769947 Hi Alex To confirm that I dont have either xmonad or marco installed. I am probably an edge case in that I am running mate under E17 as my desktop environment. If you like I can try and get the code and build it and see if it works. Though it might be the wekeend before I can manage it. Ben Please build mate-terminal and include that patch provided further above in this bug's mail backlog. If you need any help ping me via mail or on IRC (#debian-mate on OFTC or Freenode). 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 pgpjwC2D1FWiD.pgp Description: Digitale PGP-Signatur
Processed: found 762789 in 2.4.5-4
Processing commands for cont...@bugs.debian.org:
found 762789 2.4.5-4
Bug #762789 {Done: Chris Boot deb...@bootc.net} [ppp] ppp: CVE-2014-3158:
Integer overflow in option parsing
Marked as found in versions ppp/2.4.5-4.
thanks
Stopping processing here.
Please contact me if you need assistance.
--
762789: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=762789
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: fixed 762789 in 2.4.5-4+deb6u1
Processing commands for cont...@bugs.debian.org:
fixed 762789 2.4.5-4+deb6u1
Bug #762789 {Done: Chris Boot deb...@bootc.net} [ppp] ppp: CVE-2014-3158:
Integer overflow in option parsing
Marked as fixed in versions ppp/2.4.5-4+deb6u1.
thanks
Stopping processing here.
Please contact me if you need assistance.
--
762789: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=762789
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#771290: bluez-obexd package improperly Provides obexd-client, obexd-server
Package: bluez-obexd Version: 5.23-1 Severity: serious Hello, bluez-obexd packages provides obexd-client, obexd-server as they are NOT providing the same dbus interfaces. obexd-client and obexd-server are porviding interfaces like org.bluez.obex.Transfer or org.bluez.obex.Client OTHO, bluez-obexd is providing org.bluez.obex.Transfer1 and org.bluez.obex.Client1 (yes this is confusing). The provide should at least be remove (and the Replaces too I guess as they doesn't seems to provide the same file on disk). I'm not exactly sure for the Conflicts, the .service file are providing the same dbus interface name so I guess the conflicts should stay (?). Cheers, Laurent Bigonville -- System Information: Debian Release: jessie/sid APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.16.0-4-amd64 (SMP w/8 CPU cores) Locale: LANG=fr_BE.utf8, LC_CTYPE=fr_BE.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#771291: gerris: fails with tutorial examples: error compiling expression
Package: src:gerris
Version: 20131206+dfsg-4
Severity: grave
Justification: make the package unusable
Hello,
Trying gerris with the example files given on
http://gfs.sourceforge.net/tutorial/tutorial/tutorial1.html (which
I'm attaching here for the sake of completeness), I have the following
error:
gerris: file `vt2.gfs' is not a valid simulation file
vt2.gfs:14:0: error compiling expression
Package gts was not found in the pkg-config search path.
Perhaps you should add the directory containing `gts.pc'
to the PKG_CONFIG_PATH environment variable
Package 'gts', required by 'gerris2D', not found
/usr/share/gerris/build_function: 28: /usr/share/gerris/build_function: mpicc:
not found
Installing the libgts-dev improves the situation a bit since it
reduces the error message to:
gerris: file `vt2.gfs' is not a valid simulation file
vt2.gfs:14:0: error compiling expression
/usr/share/gerris/build_function: 28: /usr/share/gerris/build_function: mpicc:
not found
If I install the gerris-mpi version, it isn't any better
gerris2D vt2.gfs
[nausicaa:20717] [[INVALID],INVALID] ORTE_ERROR_LOG: A system-required
executable either could not be found or was not executable by this user in file
ess_singleton_module.c at line 231
[nausicaa:20717] [[INVALID],INVALID] ORTE_ERROR_LOG: A system-required
executable either could not be found or was not executable by this user in file
ess_singleton_module.c at line 140
[nausicaa:20717] [[INVALID],INVALID] ORTE_ERROR_LOG: A system-required
executable either could not be found or was not executable by this user in file
runtime/orte_init.c at line 128
--
Sorry! You were supposed to get help about:
orte_init:startup:internal-failure
But I couldn't open the help file:
/usr/share/openmpi/help-orte-runtime: No such file or directory. Sorry!
--
--
Sorry! You were supposed to get help about:
mpi_init:startup:internal-failure
But I couldn't open the help file:
/usr/share/openmpi/help-mpi-runtime: No such file or directory. Sorry!
--
--
Sorry! You were supposed to get help about:
mpi_errors_are_fatal unknown handle
But I couldn't open the help file:
/usr/share/openmpi/help-mpi-errors.txt: No such file or directory. Sorry!
--
--
Sorry! You were supposed to get help about:
ompi mpi abort:cannot guarantee all killed
But I couldn't open the help file:
/usr/share/openmpi/help-mpi-runtime.txt: No such file or directory. Sorry!
--
I'm setting the severity to grave as essentially, it seems
impossible for a user to actually use the version of gerris currently
in Debian.
Kind regards,
Vincent
-- System Information:
Debian Release: jessie/sid
APT prefers unstable
APT policy: (500, 'unstable'), (500, 'testing'), (500, 'stable'), (1,
'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 3.14-2-amd64 (SMP w/8 CPU cores)
Locale: LANG=en_GB.utf8, LC_CTYPE=en_GB.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Versions of packages gerris depends on:
ii libav-tools 6:11-1
ii libc6 2.19-11
ii libgcc1 1:4.9.1-16
ii libgfortran3 4.9.1-16
ii libgfs-1.3-2 20131206+dfsg-4
ii libgfs-dev20131206+dfsg-4
ii libglib2.0-0 2.40.0-4
ii libgts-0.7-5 0.7.6+darcs121130-1.2
ii libquadmath0 4.9.1-16
Versions of packages gerris recommends:
ii gfsview 20121130+dfsg-1
Versions of packages gerris suggests:
ii python 2.7.8-1
-- no debconf information
1 2 GfsSimulation GfsBox GfsGEdge {} {
GfsTime { end = 50 }
GfsRefine 6
GfsInit {} {
U = (0.5 - rand()/(double)RAND_MAX)
V = (0.5 - rand()/(double)RAND_MAX)
}
GfsOutputTime{ istep = 10 } stdout
GfsOutputProjectionStats { istep = 10 } stdout
}
GfsBox {}
1 1 right
1 1 top
Bug#771291: More information
Hello again, I can get the program working by installing, in addition to gerris (the non-MPI version): libgts-dev and libmpich-dev I didn't manage to get the MPI version to work. Regards, Vincent -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#771293: bluedevil requires bluez-obexd
Package: bluedevil Version: 2.0~rc1-44-gb7697a7-2 Severity: serious Hi, In adding to #771116, it seems that, after looking at the code, bluedevil really requires bluez-obexd. bluedevil uses interfaces like org.bluez.Agent*1* which are only provided by bluez-obexd, obexd-client and obex-data-server are only provding org.bluez.Agent (without the 1). Cheers, Laurent Bigonville -- System Information: Debian Release: jessie/sid APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.16.0-4-amd64 (SMP w/8 CPU cores) Locale: LANG=fr_BE.utf8, LC_CTYPE=fr_BE.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#771177: NMU submitted to the delayed/5 queue
I've taken the liberty to fix this via an NMU in the delayed/5days queue. Feel free to cancel it if you'd prefer to upload your own package. Francois -- Francois Marier identi.ca/fmarier http://fmarier.org twitter.com/fmarier -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#771291: gerris: fails with tutorial examples: error compiling expression
severity 771291 minor thanks Hi Vincent, gerris has autopkgtests and they are all passing regularly [1]. Of course, it can be, that not all examples are working, but it does not make gerris unusable. [1] http://ci.debian.net/packages/g/gerris/unstable/amd64/ Regards Anton 2014-11-28 11:12 GMT+01:00 Vincent Fourmond fourm...@debian.org: Package: src:gerris Version: 20131206+dfsg-4 Severity: grave Justification: make the package unusable -- 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#771291: gerris: fails with tutorial examples: error compiling expression
Processing commands for cont...@bugs.debian.org: severity 771291 minor Bug #771291 [src:gerris] gerris: fails with tutorial examples: error compiling expression Severity set to 'minor' from 'grave' thanks Stopping processing here. Please contact me if you need assistance. -- 771291: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=771291 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#762984: Alert! /dev/vg0/usr does not exist
Control: clone 762984 -2 Control: retitle 762984 cannot mount /usr if it is a separate LVM LV: Alert! /dev/vg0/usr does not exist Control: retitle -2 cannot mount /usr if INITRDSTART in /etc/default/mdadm does not include the necessary device On Thu, 27 Nov 2014 at 21:09:09 +0100, Elimar Riesebieter wrote: * Simon McVittie s...@debian.org [2014-11-27 11:51 +]: I think this bug report is actually describing more than one bug in more than one package that have similar symptoms. ... Elimar Riesebieter's System 2 has a bunch of mdadm (RAID) partitions. Elimar, what is in your /etc/default/mdadm on System 2 (and System 1 for that matter)? I predict that the answer includes something like INITRDSTART=/dev/md6. Right, adding root and usr raid partitions to INITRDSTART like INITRDSTART='/dev/md3 /dev/md5' or just 'all' does the job. I'm splitting off the situation on your System 2 into a separate bug, because as far as I can see, this is the only part of this report that does not involve LVM. Some of the other reports do involve RAID arrays, but none of them seem to require bringing up additional RAID arrays in the initramfs (that were not already needed for the root filesystem), so they could all be fixed with only LVM-related changes. S -- 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#762984: Alert! /dev/vg0/usr does not exist
Processing control commands: clone 762984 -2 Bug #762984 [initramfs-tools] initramfs-tools: Alert! /dev/vg0/usr does not exist Bug 762984 cloned as bug 771301 retitle 762984 cannot mount /usr if it is a separate LVM LV: Alert! /dev/vg0/usr does not exist Bug #762984 [initramfs-tools] initramfs-tools: Alert! /dev/vg0/usr does not exist Changed Bug title to 'cannot mount /usr if it is a separate LVM LV: Alert! /dev/vg0/usr does not exist' from 'initramfs-tools: Alert! /dev/vg0/usr does not exist' retitle -2 cannot mount /usr if INITRDSTART in /etc/default/mdadm does not include the necessary device Bug #771301 [initramfs-tools] initramfs-tools: Alert! /dev/vg0/usr does not exist Changed Bug title to 'cannot mount /usr if INITRDSTART in /etc/default/mdadm does not include the necessary device' from 'initramfs-tools: Alert! /dev/vg0/usr does not exist' -- 762984: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=762984 771301: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=771301 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#770242: Tentative patch
The attached patch fixes installation when /etc/rkhunter.conf is missing. -- Francois Marier identi.ca/fmarier http://fmarier.org twitter.com/fmarier commit f91d229ad51b19d52b979720f8a1edf1e2aea385 Author: Francois Marier franc...@debian.org Date: Sat Nov 29 00:27:20 2014 +1300 Work-around missing /etc/rkhunter.conf in postinst (closes: #770242) diff --git a/debian/postinst b/debian/postinst old mode 100644 new mode 100755 index 7179cff..d93fdd6 --- a/debian/postinst +++ b/debian/postinst @@ -35,7 +35,10 @@ case $1 in # Copy the passwd/group files to the TMP directory # to avoid warnings when rkhunter is first run. # This is normally done by the installer script. -rkhtmpdir=$(grep '^TMPDIR' /etc/rkhunter.conf | sed 's/TMPDIR=//') +rkhtmpdir=/var/lib/rkhunter/tmp +if [ -e /etc/rkhunter.conf ]; then +rkhtmpdir=$(grep '^TMPDIR' /etc/rkhunter.conf | sed 's/TMPDIR=//') +fi [ -f $rkhtmpdir/passwd ] || cp -p /etc/passwd $rkhtmpdir /dev/null 21 [ -f $rkhtmpdir/group ] || cp -p /etc/group $rkhtmpdir /dev/null 21
Bug#770242: Broken postinst script?
This bug looks similar to https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=765911 which got fixed in 1.4.2-0.3 by removing the /usr/sbin/prelink line from the config file. I've chosen to keep currently-installed version of /etc/rkhunter.conf That's a problem and won't work because the configuration file format has changed between 1.4.0 and 1.4.2. I don't think we necessarily can (or should) fix this. Users should accept the new config file and merge their changes manually. I did not dig deeper but it looks like something is broken in postinst configuration handling... My patch should fix that problem. Francois -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: tagging 771287
Processing commands for cont...@bugs.debian.org: tags 771287 + pending Bug #771287 [systemd] systemd: Multiple DMs can be started at the same time or none under systemd Added tag(s) pending. thanks Stopping processing here. Please contact me if you need assistance. -- 771287: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=771287 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: found 769646 21-4 found 769646 21-5
Processing commands for cont...@bugs.debian.org: found 769646 21-4 Bug #769646 [android-libcutils-dev] android-libutils: undefined references in /usr/lib/android/libutils.so Marked as found in versions android-platform-system-core/21-4; no longer marked as fixed in versions android-platform-system-core/21-4. found 769646 21-5 Bug #769646 [android-libcutils-dev] android-libutils: undefined references in /usr/lib/android/libutils.so Marked as found in versions android-platform-system-core/21-5. End of message, stopping processing here. Please contact me if you need assistance. -- 769646: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=769646 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#768876: unblock: busybox/1:1.22.0-14
On Thu, 27 Nov 2014, Michael Tokarev wrote:
(The Built-Using field generation is a bit fun here: I asked on IRC
how people identify which libc is in use, and got various somewhat-
incpmplete replies (the prob is that on different arches, libc package
is named differently). So I invented my own way for busybox, because
You didn’t ask in the #!/bin/mksh channel on IRC (= Freenode) ;-)
So let me add mine:
‣ intimate knowledge of the build system required, so you know
what precidely is pulled in (reading shlibs:Depends from the
build of the shared version is almost certainly wrong)
In the mksh case, I have a switch between different libcs to use.
For dietlibc and klibc, the cases are clear:
• libc_pkgname='libklibc-dev linux-libc-dev'
• libc_pkgname=dietlibc-dev
For (e)glibc, or rather, “the default libc”, a little trick:
• x=$(dpkg -S $(readlink -f $($CC -print-file-name=libc.a)))
libc_pkgname=${x%%: *}
In *all* cases, you also need
• x=$(dpkg -S $(readlink -f $($CC -print-file-name=libgcc.a)))
libgcc_pkgname=${x%%: *}
Now you need to get from that to the corresponding source packages:
for x in $libc_pkgname $libgcc_pkgname; do
dpkg-query -Wf '${source:Package} (= ${source:Version})\n' $x
done | sort -u | {
srcpkgnames=
while IFS= read -r x; do
test -n $x || continue
test x$x = x (= ) continue
echo Built Using: $x
test -z $srcpkgnames || srcpkgnames=$srcpkgnames,
srcpkgnames=$srcpkgnames$x
done
echo mksh:B-U=$srcpkgnames builddir/substvars
}
bye,
//mirabilos
--
«MyISAM tables -will- get corrupted eventually. This is a fact of life. »
“mysql is about as much database as ms access” – “MSSQL at least descends
from a database” “it's a rebranded SyBase” “MySQL however was born from a
flatfile and went downhill from there” – “at least jetDB doesn’t claim to
be a database” ‣‣‣ Please, http://deb.li/mysql and MariaDB, finally die!
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: bug 771125 is forwarded to http://dev.mutt.org/trac/ticket/3716, severity of 771125 is important ...
Processing commands for cont...@bugs.debian.org: forwarded 771125 http://dev.mutt.org/trac/ticket/3716 Bug #771125 [mutt] mutt: CVE-2014-9116: buffer overflow Set Bug forwarded-to-address to 'http://dev.mutt.org/trac/ticket/3716'. # downgreading, does not seem to allow code execution severity 771125 important Bug #771125 [mutt] mutt: CVE-2014-9116: buffer overflow Severity set to 'important' from 'grave' retitle 771125 mutt: CVE-2014-9116 write_one_header can call mutt_substrdup with begin end, leading to crash Bug #771125 [mutt] mutt: CVE-2014-9116: buffer overflow Changed Bug title to 'mutt: CVE-2014-9116 write_one_header can call mutt_substrdup with begin end, leading to crash' from 'mutt: CVE-2014-9116: buffer overflow' thanks Stopping processing here. Please contact me if you need assistance. -- 771125: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=771125 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#769646: marked as done (android-libutils: undefined references in /usr/lib/android/libutils.so)
Your message dated Fri, 28 Nov 2014 12:49:00 + with message-id e1xukyq-00052z...@franck.debian.org and subject line Bug#769646: fixed in android-platform-system-core 21-6 has caused the Debian Bug report #769646, regarding android-libutils: undefined references in /usr/lib/android/libutils.so 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.) -- 769646: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=769646 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Source: android-platform-build Version: 21-2 Severity: serious Tags: jessie sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20141112 qa-ftbfs Justification: FTBFS in jessie on i386 Hi, During a rebuild of all packages in jessie (in a jessie chroot, not a sid chroot), your package failed to build on i386. Relevant part (hopefully): g++ -fPIC -Wl,-rpath=/usr/lib/android -Wl,-z,relro -o zipalign ZipAlign.o ZipEntry.o ZipFile.o -lz -lpthread -L/usr/lib/android -llog -lutils -lcutils /usr/lib/android/libutils.so: undefined reference to `android_atomic_or' /usr/lib/android/libutils.so: undefined reference to `android_atomic_dec' /usr/lib/android/libutils.so: undefined reference to `android_atomic_inc' /usr/lib/android/libutils.so: undefined reference to `android_atomic_release_cas' /usr/lib/android/libutils.so: undefined reference to `android_atomic_add' collect2: error: ld returned 1 exit status The full build log is available from: http://aws-logs.debian.net/ftbfs-logs/2014/11/12/android-platform-build_21-2_jessie-i386.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--- Source: android-platform-system-core Source-Version: 21-6 We believe that the bug you reported is fixed in the latest version of android-platform-system-core, 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 769...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Hans-Christoph Steiner h...@eds.org (supplier of updated android-platform-system-core 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: Fri, 28 Nov 2014 13:00:09 +0100 Source: android-platform-system-core Binary: android-system-dev android-liblog android-liblog-dev android-libcutils android-libcutils-dev android-libzipfile android-libzipfile-dev Architecture: source amd64 Version: 21-6 Distribution: unstable Urgency: low Maintainer: Android tools Maintainer android-tools-de...@lists.alioth.debian.org Changed-By: Hans-Christoph Steiner h...@eds.org Description: android-libcutils - Android utils library for C android-libcutils-dev - Android utils library for C - Development files android-liblog - Android logging library android-liblog-dev - Android logging library - Development files android-libzipfile - Android zipfile library android-libzipfile-dev - Android zipfile library - Development files android-system-dev - Android system development headers Closes: 769646 Changes: android-platform-system-core (21-6) unstable; urgency=low . [Simon McVittie] * fix missing android_atomic_* symbols on i386 (Closes: #769646) Checksums-Sha1: 43eb56d73259d7ac7fa951a61c5021cb94e98d1c 2752 android-platform-system-core_21-6.dsc ba7a770eee7e87a10475c4f590278f6a256bd861 13932 android-platform-system-core_21-6.debian.tar.xz a40f6ce08b96ae5ea5beb28685554716390ba587 24458 android-system-dev_21-6_amd64.deb 3283b22629214ad210df20292c7dff5bc2b5ea57 15770 android-liblog_21-6_amd64.deb d8c568a25d50864fdd1b086dbd301303baa06c6c 21780 android-liblog-dev_21-6_amd64.deb a6a9bf63d06639752fd8a48aafa29a79391052e8 22968 android-libcutils_21-6_amd64.deb 8f42e3dd7d7acb0b642c884b4daa23b538c72d67 38844 android-libcutils-dev_21-6_amd64.deb 23cf513ac1b0487cc239944299efb6f690ba8211 7594 android-libzipfile_21-6_amd64.deb 67211af5b3c7ebe8437141dfd75dbe7c7ccfcf5f 7054
Bug#770330: using getprop in debian/preinst
Hey Lazslo/GCS, Any luck with your investigation? I'd like to avoid having this package AUTORMed from jessie. I added your improved chroot detection to enforce that this package is only included on a chroot. As for the `getprop` method, I can't think of anyway to really use getprop from a debian/preinst script since it'll always be in /system/bin/getprop, and not in the Debian chroot. .hc signature.asc Description: OpenPGP digital signature
Processed: jessie
Processing commands for cont...@bugs.debian.org: tags 771177 + sid jessie Bug #771177 [develock-el] develock-el: breaks c++ mode in sid and jessie Added tag(s) sid and jessie. End of message, stopping processing here. Please contact me if you need assistance. -- 771177: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=771177 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#771290: bluez-obexd package improperly Provides obexd-client, obexd-server
On Fri, 28 Nov 2014 11:20:31 +0100 Laurent Bigonville bi...@debian.org wrote: bluez-obexd packages provides obexd-client, obexd-server as they are NOT providing the same dbus interfaces. Argh, broken English... bluez-obexd should not provides obexd-client, obexd-server as they are NOT exporting the same dbus interfaces. [...] I'm not exactly sure for the Conflicts, the .service file are providing the same dbus interface name so I guess the conflicts should stay (?). From what I saw, if a service is already started, dbus will not try to start an other one providing the same name (make sense), so IMHO the Conflitcs must stay. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: Tag pending
Processing commands for cont...@bugs.debian.org: tags 771177 + pending Bug #771177 [develock-el] develock-el: breaks c++ mode in sid and jessie Added tag(s) pending. End of message, stopping processing here. Please contact me if you need assistance. -- 771177: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=771177 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#768876: unblock: busybox/1:1.22.0-14
28.11.2014 15:11, Thorsten Glaser wrote:
On Thu, 27 Nov 2014, Michael Tokarev wrote:
(The Built-Using field generation is a bit fun here: I asked on IRC
how people identify which libc is in use, and got various somewhat-
incpmplete replies (the prob is that on different arches, libc package
is named differently). So I invented my own way for busybox, because
You didn’t ask in the #!/bin/mksh channel on IRC (= Freenode) ;-)
I asked in several debian-related places, since this is a debian-specific
thing.
So let me add mine:
‣ intimate knowledge of the build system required, so you know
what precidely is pulled in (reading shlibs:Depends from the
build of the shared version is almost certainly wrong)
Why it is wrong? To be this looks like the most accurate approach
really.
In the mksh case, I have a switch between different libcs to use.
For dietlibc and klibc, the cases are clear:
Wug.
[]
In *all* cases, you also need
• x=$(dpkg -S $(readlink -f $($CC -print-file-name=libgcc.a)))
libgcc_pkgname=${x%%: *}
Why? This assumes it is gcc an it uses libgcc, so it wont work with,
say, clang. Note also that if libgcc is used by shared build, it will
also be listed in shilbdeps.
Thanks,
/mjt
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#768876: unblock: busybox/1:1.22.0-14
On Fri, 28 Nov 2014, Michael Tokarev wrote:
‣ intimate knowledge of the build system required, so you know
what precidely is pulled in (reading shlibs:Depends from the
build of the shared version is almost certainly wrong)
Why it is wrong? To be this looks like the most accurate approach
The builds probably differ, especially when using autoconf.
In *all* cases, you also need
• x=$(dpkg -S $(readlink -f $($CC -print-file-name=libgcc.a)))
libgcc_pkgname=${x%%: *}
Why?
Because some of these functions do end up in the resulting executable.
This assumes it is gcc an it uses libgcc, so it wont work with,
say, clang.
True. But either “clang -print-file-name=libgcc.a” will be empty,
or it will report libgcc.a which may or may not be pulled in. But
archive builds are not done using clang _yet_. I’ll revisit this
when that option exists, or so. It’s too fast moving a target at
the moment, anyway.
Note also that if libgcc is used by shared build, it will
also be listed in shilbdeps.
Fallacy. I know GCC interna better than I wish to. Most of
libgcc.a is always put into binaries; the shared libgcc is
mostly the libgcc_eh.a equivalent, and -static-libgcc is,
normally, the default for C language builds. (Also, it’s a
good way to keep the GCC version used to build it in the
archive.)
bye,
//mirabilos
--
15:41⎜Lo-lan-do:#fusionforge Somebody write a testsuite for helloworld :-)
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: Patch
Processing control commands: tags -1 + patch Bug #771113 [src:lintian] lintian: FTBFS on i386: binaries-from-other-arch FAILED Added tag(s) patch. -- 771113: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=771113 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#771113: Patch
Control: tags -1 + patch Hi, I've verified that the attached patch fixes this problem: diff -Nru lintian-2.5.30+deb8u2/t/tests/binaries-from-other-arch/debian/debian/dumpobj lintian-2.5.30+deb8u3/t/tests/binaries-from-other-arch/debian/debian/dumpobj --- lintian-2.5.30+deb8u2/t/tests/binaries-from-other-arch/debian/debian/dumpobj 2013-01-20 14:12:28.0 -0800 +++ lintian-2.5.30+deb8u3/t/tests/binaries-from-other-arch/debian/debian/dumpobj 2014-11-27 22:38:33.0 -0800 @@ -4,7 +4,7 @@ DEB_BUILD_GNU_TYPE=$(dpkg-architecture -qDEB_BUILD_GNU_TYPE) case $DEB_BUILD_GNU_TYPE in -i486-linux-gnu|i686-linux-gnu|x86_64-linux-gnu) +i486-linux-gnu|i586-linux-gnu|i686-linux-gnu|x86_64-linux-gnu) base64 -d DATA f0VMRgEBAQIAKAABMIEAADQ4bwkAAgAABDQAIAAGACgAGwAaAAEAAHDY WgkA2NoJANjaCQBQCgAAUAoAAAQEAQAAgIAAAKhlCQCoZQkABQCA -- Matt -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: severity of 766762 is serious
Processing commands for cont...@bugs.debian.org: severity 766762 serious Bug #766762 [upower] upower: fatal memory leak on low battery Severity set to 'serious' from 'important' thanks Stopping processing here. Please contact me if you need assistance. -- 766762: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=766762 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#769221: marked as done (serverspec-runner: can't grab templates correctly.)
Your message dated Fri, 28 Nov 2014 15:21:52 + with message-id e1xunmm-0007iw...@franck.debian.org and subject line Bug#769221: fixed in serverspec-runner 0.2.4-2 has caused the Debian Bug report #769221, regarding serverspec-runner: can't grab templates correctly. 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.) -- 769221: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=769221 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: serverspec-runner Version: 0.2.4-1 Severity: grave Justification: renders package unusable for the record, serverspec-runner searches its templates path relatively from its command script's, and assumes bad place for debian's FHS. # This package doesn't places templates, so users can't start using it from scratch. I will fix this soon.. - placing templates to /usr/share - patching script to search above location regards, -- System Information: Debian Release: jessie/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: i386 (i686) Kernel: Linux 2.6.32-30-pve (SMP w/8 CPU cores) Locale: LANG=C, LC_CTYPE=ja_JP.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages serverspec-runner depends on: ii bundler 1.7.4-1 ii rake 10.3.2-2 ii ruby 1:2.1.0.4 ii ruby-net-ssh 1:2.9.1-1 ii ruby-rspec-core 2.14.7-2 ii ruby-serverspec 1.14.0-2 ii ruby1.9.1 [ruby-interpreter] 1.9.3.484-2 ii ruby2.0 [ruby-interpreter]2.0.0.484+really457-3 ii ruby2.1 [ruby-interpreter]2.1.4-1 serverspec-runner recommends no packages. serverspec-runner suggests no packages. -- no debconf information ---End Message--- ---BeginMessage--- Source: serverspec-runner Source-Version: 0.2.4-2 We believe that the bug you reported is fixed in the latest version of serverspec-runner, 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 769...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. KURASHIKI Satoru lur...@gmail.com (supplier of updated serverspec-runner 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: Wed, 26 Nov 2014 12:32:06 +0900 Source: serverspec-runner Binary: serverspec-runner Architecture: source all Version: 0.2.4-2 Distribution: unstable Urgency: high Maintainer: Debian Ruby Extras Maintainers pkg-ruby-extras-maintain...@lists.alioth.debian.org Changed-By: KURASHIKI Satoru lur...@gmail.com Description: serverspec-runner - simple execution framework for serverspec Closes: 769221 Changes: serverspec-runner (0.2.4-2) unstable; urgency=high . * Patch to fix grave bug disturbing to use from scratch. (Closes: #769221) - complete set of templates into /usr/share/serverspec-runner/. - modify script to search above template instead of current path. - fix template to cope with Debian. Checksums-Sha1: 8ebee65c8bfa1866bfbe6e00814741dedfc2c406 2040 serverspec-runner_0.2.4-2.dsc 59b29e17c05bf8171392dda2bda30f3f770bd235 4420 serverspec-runner_0.2.4-2.debian.tar.xz d492e1d19cfc6e17ef39920a2e817a51e929fc9b 9984 serverspec-runner_0.2.4-2_all.deb Checksums-Sha256: 13af3187fd30d9ab05d5eb0a903e378b4de04d945e63acb6da72b28632af0eeb 2040 serverspec-runner_0.2.4-2.dsc 4b1e0b3c151a9f5ab7002a01901cdb007249d35338187294a634ec95ab3a84a4 4420 serverspec-runner_0.2.4-2.debian.tar.xz 92d0177546ee3d618c682f37118194eb86a5624da9ef50cca3610b30f9e1c3f7 9984 serverspec-runner_0.2.4-2_all.deb Files: 01c5bd9280b9f177a5115266df0c40a9 2040 ruby optional serverspec-runner_0.2.4-2.dsc d0b871613d15bb9d1b5c5967cd43 4420 ruby optional serverspec-runner_0.2.4-2.debian.tar.xz 81e8dffc4a1c84c05c2ca9efc34290ca 9984 ruby optional serverspec-runner_0.2.4-2_all.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1 iQIcBAEBCAAGBQJUeH64AAoJEHg5YZ3UOWaOWXEP/jJu/wKzTOE3kVULWlA89QW6 XQE1631t8OXFRBoIqcGVuoS48NnWwjrqHkwCBZLOL9rBay+c+aGRucCY3V1sjPp3 7BVb4I0SuFeZxbvgLo2QtrXuSwoicP3u9fddKcskzVr90KcJkh2uSaNOi4tFEeZB vk9NDDHbcCNfjnCHdEuhkjZOKd15/g9QKrd7uActyw1GkhcJjs9hiIXDbC9bn7gR
Bug#768876: unblock: busybox/1:1.22.0-14
28.11.2014 18:06, Thorsten Glaser wrote:
On Fri, 28 Nov 2014, Michael Tokarev wrote:
‣ intimate knowledge of the build system required, so you know
what precidely is pulled in (reading shlibs:Depends from the
build of the shared version is almost certainly wrong)
Why it is wrong? To be this looks like the most accurate approach
it supposed to be To me.
The builds probably differ, especially when using autoconf.
Probably? If they differ it is a bug which should be fixed.
In this case it is irrelevant because busybox only uses libc
and probably libm which both comes form the same package anyway
(plus whatever libgcc it is pulling in too). Even if some other
lib will be used, the same lib will be used for both static and
non-static versions.
In *all* cases, you also need
• x=$(dpkg -S $(readlink -f $($CC -print-file-name=libgcc.a)))
libgcc_pkgname=${x%%: *}
Why?
Because some of these functions do end up in the resulting executable.
This assumes it is gcc an it uses libgcc, so it wont work with,
say, clang.
True. But either “clang -print-file-name=libgcc.a” will be empty,
or it will report libgcc.a which may or may not be pulled in. But
archive builds are not done using clang _yet_. I’ll revisit this
when that option exists, or so. It’s too fast moving a target at
the moment, anyway.
Um. Maybe we should assume exact versions of software running in
buildds too? I don't think this approach scales, to me it is wrong,
and we should use some more generic way.
BTW, how about somethig like gcc -v (I'm not sure it is the right
option actually) which shows all libs it actually used for linking -
run it once, find out all actual libs and go from there, translating
the list to debian package names. I think _that_ will be the only
real thing.
But for now, current way to construct built-using from shlibdeps,
maybe adding libgcc/gcc too on the way should be enough, for this
very package anyway. And more, I'm not sure at all I want to
perform another series of experiments while asking for an unblock...
Besides, this process should be automated with some helper, something
like dh_built-using, I dunno. Or else, due to the fact that it is
very difficult to get the value right, we'll have it all wrong, and
differently wrong in every place too.
Note also that if libgcc is used by shared build, it will
also be listed in shilbdeps.
Fallacy. I know GCC interna better than I wish to. Most of
libgcc.a is always put into binaries; the shared libgcc is
mostly the libgcc_eh.a equivalent, and -static-libgcc is,
normally, the default for C language builds. (Also, it’s a
good way to keep the GCC version used to build it in the
archive.)
Oh well. Do you think I should reopen this bugreport?
Thanks,
/mjt
--
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#768675: mdp: FTBFS in jessie: tests failures
Processing control commands: tag -1 + pending Bug #768675 [src:mdp] mdp: FTBFS in jessie: tests failures Added tag(s) pending. -- 768675: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=768675 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#769325: mediatomb: Mediatomb does not work with systemd
severity 769325 important thanks Hello, On Wed, Nov 12, 2014 at 09:43:21PM +0100, Patrick Häcker wrote: version 0.12.1-7 does not start when using systemd without a useable error message: Process: 2788 ExecStart=/usr/bin/mediatomb -d -u $MT_USER -g $MT_GROUP -P /run/mediatomb.pid -l $MT_LOGFILE -m $MT_HOME -f $MT_CFGDIR -p $MT_PORT -e $MT_INTERFACE (code=exited, status=0/SUCCESS) Process: 2785 ExecStartPre=/sbin/ifconfig $MT_INTERFACE allmulti (code=exited, status=0/SUCCESS) Process: 2782 ExecStartPre=/sbin/route add -net 239.0.0.0 netmask 255.0.0.0 $MT_INTERFACE (code=exited, status=0/SUCCESS) Process: 2779 ExecStartPre=/bin/grep -q MT_USER /etc/default/mediatomb (code=exited, status=0/SUCCESS) Main PID: 2789 (code=exited, status=1/FAILURE) Even if it started, it wouldn't work, as it does not read the configuration file /etc/mediatomb/config.xml, which can be seen in /lib/systemd/system/mediatomb.service: ExecStart=/usr/bin/mediatomb -d -u $MT_USER -g $MT_GROUP -P /run/mediatomb.pid -l $MT_LOGFILE -m $MT_HOME -f $MT_CFGDIR -p $MT_PORT -e $MT_INTERFACE Additionally, it does not seem to make sense to have /etc/default/mediatomb, as nearly all options are duplicates of options in /etc/mediatomb/config.xml. It is completely unclear to a normal user which value is used, if the values of both files differ. /etc/default/mediatomb is a file for daemon configuration (network card to attach to, user/group to run under, location of config.xml, etc...)), while /etc/mediatomb/config.xml is for mediatomb configuration (see upstream documentation http://mediatomb.cc/pages/documentation#id2856319). You are right and some optional values can be set at config.xml, but Debian mediatomb older releases have been configuring the daemon, even other distros, as Fedora, configure the daemon. It is not our fault the upstream provides two different ways to configure the daemon, via CLI or via config.xml. We picked to configure it via CLI with environment file, it has been that way for several releases now. Mediatomb had working systemd support before these changes had been applied. Sorry, there was no systemd unit file before, you might had been using the old init script which also sets up the daemon. These changes should thus probably be reverted. Alternatively, /etc/default/mediatomb should be deleted and /lib/systemd/system/mediatomb.service should be changed into [Unit] Description=UPnP MediaServer After=NetworkManager-wait-online.service network.target [Service] Type=forking PIDFile=/run/mediatomb.pid ExecStart=/usr/bin/mediatomb -d -c /etc/mediatomb/config.xml -P /run/mediatomb.pid [Install] WantedBy=multi-user.target Sorry, I disagree to do those changes at this stage in the release, we are frozen. I do not think it's good idea to run the daemon as root, but instead use the mediatomb user/group. Also you seem to drop network settings for UPnP to work properly on some systems, why is that? I do not agree on the severity reported, as the package works for me with that setup, and it might work for you, if you configure it properly. Therefore I am downgrading severity to at most important as I do not think it should be removed from jessie release, but I am further interested to hear about your proposed changes and find a common area that works for all. Regards, -- Hector Oron signature.asc Description: Digital signature
Bug#768675: mdp: FTBFS in jessie: tests failures
Control: tag -1 + pending On Wed, 12 Nov 2014 20:18:13 +0100, Tiziano Zito wrote: thank you for diagnosing the problem. A fix is actually already available upstream since August 2013 (!). An updated mdp package for jessy is ready and will be uploaded as soon as the Uploader finds the time to do it :) Let's hope this is soon for some low value of soon :) Tagging pending in the meantime. Cheers, gregor -- .''`. Homepage: http://info.comodo.priv.at/ - OpenPGP key 0xBB3A68018649AA06 : :' : Debian GNU/Linux user, admin, and developer - http://www.debian.org/ `. `' Member of VIBE!AT SPI, fellow of the Free Software Foundation Europe `- NP: The Mamas The Papas: Dream A Little Dream Of Me signature.asc Description: Digital Signature
Bug#768675: mdp: FTBFS in jessie: tests failures
On Wed, 12 Nov 2014, Tiziano Zito wrote: Hi Andrey! On Wed 12 Nov, 23:05, Andrey Rahmatullin w...@debian.org wrote: The failing docstring indeed contains U+2013 EN DASH, it is taken from /usr/lib/python2.7/dist-packages/sklearn/feature_extraction/text.py (package python-sklearn). In jessie (0.14.1-3) it says Transform a count matrix to a normalized tf or tf–idf representation when in sid (0.15.2-3) it contains a normal ASCII hyphen instead, so this FTBFS is jessie-only. The solution is probably to fix bimdp/nodes/autogen.py in mdp to support non-ASCII docstrings. thank you for diagnosing the problem. A fix is actually already available upstream since August 2013 (!). An updated mdp package for jessy is ready and will be uploaded as soon as the Uploader finds the time to do it :) ah, right -- imho there seems to be a bit too many changes picked into the package but let's see what release team would say. I will build/upload -2 to sid shortly. For experimental/NeuroDebian we better package 3.4 or 3.3.1 so that package would upgrade from 3.3+git6-g7bbd889-1 -- Yaroslav O. Halchenko, Ph.D. http://neuro.debian.net http://www.pymvpa.org http://www.fail2ban.org Research Scientist,Psychological and Brain Sciences Dept. Dartmouth College, 419 Moore Hall, Hinman Box 6207, Hanover, NH 03755 Phone: +1 (603) 646-9834 Fax: +1 (603) 646-1419 WWW: http://www.linkedin.com/in/yarik -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#768876: unblock: busybox/1:1.22.0-14
On Fri, 28 Nov 2014, Michael Tokarev wrote: Um. Maybe we should assume exact versions of software running in buildds too? No, only things that end up in the binaries. BTW, how about somethig like gcc -v (I'm not sure it is the right option actually) which shows all libs it actually used for linking - Yes, except that is not parsable, and varies by compiler. run it once, find out all actual libs and go from there, translating the list to debian package names. I think _that_ will be the only real thing. I agree. Maybe -Wl,-v or -Wl,-t instead. We always use binutils… but these options also have their shortcomings. Besides, this process should be automated with some helper, something like dh_built-using, I dunno. Or else, due to the fact that it is No, this requires intimate knowledge of the build system in use; autoconf will break during the configure phase if you use some compiler flags (like -Werror) for example, so you have to inject that flag somewhere. Also, not everything is always static, and if you build multiple binary packages, you need to track what is what anyway. I think that, for B-U, we can’t find a generic solution. Oh well. Do you think I should reopen this bugreport? I think you probably only should add the libgcc.a provider and cross fingers for now. B-U are not unimportant, but a real PITA anyway right now. bye, //mirabilos -- [16:04:33] bkix: veni vidi violini [16:04:45] bkix: ich kam, sah und vergeigte... -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#771334: upgrade hosed dovecot; Couldn't parse private ssl_key: error:0906D06C:PEM routines:PEM_read_bio:no start line: Expecting: ANY PRIVATE KEY
Source: dovecot Version: 1:2.2.13-7 Severity: serious After upgrading to this version, I cannot connect to dovecot's imap or pop servers. joey@darkstar:~telnet kitenet.net imap Trying 66.228.36.95... Connected to kite.kitenet.net. Escape character is '^]'. Connection closed by foreign host. Offlineimap fails connecting to imaps; the ssl handshake fails. journald has logged: Nov 28 11:33:44 kite dovecot[14616]: imap-login: Fatal: Couldn't parse private ssl_key: error:0906D06C:PEM routines:PEM_read_bio:no start line: Expecting: ANY PRIVATE KEY Nov 28 11:33:44 kite dovecot[14604]: master: Error: service(imap-login): command startup failed, throttling for 4 secs Nov 28 11:33:48 kite dovecot[14616]: imap-login: Fatal: Couldn't parse private ssl_key: error:0906D06C:PEM routines:PEM_read_bio:no start line: Expecting: ANY PRIVATE KEY Nov 28 11:33:48 kite dovecot[14604]: master: Error: service(imap-login): command startup failed, throttling for 8 secs I suppose it's not cooincidental that the change in -7 had something to do with cert locations. My dovecot cert appears to be in /etc/dovecot/private/dovecot.pem, and it starts with -BEGIN PRIVATE KEY- Downgrading to -6 worked around this. -- see shy jo -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: serious
Processing control commands: severity -1 serious Bug #769158 [munin,munin-node] munin, munin-node: fails to upgrade from 'sid' - trying to overwrite /usr/share/man/man5/munin.conf.5.gz Severity set to 'serious' from 'important' tags -1 + experimental stretch Bug #769158 [munin,munin-node] munin, munin-node: fails to upgrade from 'sid' - trying to overwrite /usr/share/man/man5/munin.conf.5.gz Added tag(s) stretch and experimental. -- 769158: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=769158 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#766762: upower: fatal memory leak on low battery
tags 766762 +pending tags 766762 +patch tags 766762 +fixed-upstream severitz 766762 serious thanks On Fri, Nov 28, 2014 at 03:49:05PM +0100, intrigeri wrote: Michael Banck wrote (28 Nov 2014 14:19:32 GMT) : I think this bug is severe enough that it should be fixed now, and as soon as it is accepted in testing, the rest of the upstream point release could be submitted for inclusion, if time still permits. Agreed. If you had time to test if the commit I'm ponting at fixes the bug for you too, it would be great! Well, I'm running with that patch applied now, but I've only ever saw this bug every other week or so, so it will be difficult to verfiy that the bug is gone in a timely manner. And if you want to take care of the NMU and unblock request, please do. I had a quick chat with a release team member and they seem to believe this bug warrants RC status: azeem so upowerd tends to eat up 2+GB in some cases due to a memleak, RC or not? azeem (2GB memory, that is) LocutusOfBorg1 2GB is not too much anymore :) azeem well, at 2GB my notebook keeps thrashing, and with luck I get to the console and kill -9 it azeem not sure what the upper bound is thijs I'd say RC thijs can always downgrade later if impact is better understood I've prepared an NMU by taking the git commit and will upload it to DELAYED/1-day later today. Debdiff is attached. I'll look into filing an unblock request as well. Michael -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed (with 1 errors): Re: Bug#766762: upower: fatal memory leak on low battery
Processing commands for cont...@bugs.debian.org: tags 766762 +pending Bug #766762 [upower] upower: fatal memory leak on low battery Added tag(s) pending. tags 766762 +patch Bug #766762 [upower] upower: fatal memory leak on low battery Added tag(s) patch. tags 766762 +fixed-upstream Bug #766762 [upower] upower: fatal memory leak on low battery Added tag(s) fixed-upstream. severitz 766762 serious Unknown command or malformed arguments to command. thanks Stopping processing here. Please contact me if you need assistance. -- 766762: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=766762 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: Patch
Processing control commands: tags -1 + patch Bug #771177 [develock-el] develock-el: breaks c++ mode in sid and jessie Added tag(s) patch. -- 771177: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=771177 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#771177: Patch
Control: tags -1 + patch Hi, I've verified that the following patch, extracted from upstream, fixes this issue: Index: develock-el-0.39/develock.el === --- develock-el-0.39.orig/develock.el 2014-11-28 07:35:04.0 -0800 +++ develock-el-0.39/develock.el2014-11-28 07:39:15.519099017 -0800 @@ -1802,10 +1802,8 @@ (defun develock-Orig-c-indent-line (optional syntax quiet ignore-point-pos) This function should be redefined to the genuine `c-indent-line'. - (require 'cc-engine) - (let* ((fn (symbol-function (if (fboundp 'ad-Orig-c-indent-line) - 'ad-Orig-c-indent-line - 'c-indent-line))) + (let* ((fn (or (ad-real-orig-definition 'c-indent-line) +(symbol-function 'c-indent-line))) ;; Checking how many arguments `c-indent-line' accepts. (nargs (length (ad-arglist fn (cond ((= nargs 4) @@ -1823,7 +1821,9 @@ Identical to `c-indent-line', but the optional arguments QUIET and IGNORE-POINT-POS are ignored. (funcall ,fn syntax)) - (if (featurep 'bytecomp) + (if (and (featurep 'bytecomp) + (eq (car-safe (symbol-function 'develock-Orig-c-indent-line)) + 'lambda)) (byte-compile 'develock-Orig-c-indent-line)) (develock-Orig-c-indent-line syntax quiet ignore-point-pos)) -- Matt -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: your mail
Processing commands for cont...@bugs.debian.org: severity 771210 grave Bug #771210 [kdump-tools] kdump-tools fails to complete when run with systemd Severity set to 'grave' from 'normal' End of message, stopping processing here. Please contact me if you need assistance. -- 771210: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=771210 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: found should be enough
Processing commands for cont...@bugs.debian.org: tags 769158 stretch experimental Bug #769158 [munin,munin-node] munin, munin-node: fails to upgrade from 'sid' - trying to overwrite /usr/share/man/man5/munin.conf.5.gz Ignoring request to alter tags of bug #769158 to the same tags previously set End of message, stopping processing here. Please contact me if you need assistance. -- 769158: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=769158 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: mpi-specs: diff for NMU version 20040719-2.1
Processing control commands: tags 484003 + pending Bug #484003 [mpi-specs] Using obsolete .dhelp files Ignoring request to alter tags of bug #484003 to the same tags previously set tags 557409 + patch Bug #557409 [mpi-specs] Typo in package description: This packages Ignoring request to alter tags of bug #557409 to the same tags previously set tags 557409 + pending Bug #557409 [mpi-specs] Typo in package description: This packages Ignoring request to alter tags of bug #557409 to the same tags previously set tags 770411 + patch Bug #770411 [mpi-specs] mpi-specs: postinst uses /usr/share/doc content (Policy 12.3) Ignoring request to alter tags of bug #770411 to the same tags previously set tags 770411 + pending Bug #770411 [mpi-specs] mpi-specs: postinst uses /usr/share/doc content (Policy 12.3) Ignoring request to alter tags of bug #770411 to the same tags previously set -- 484003: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=484003 557409: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=557409 770411: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=770411 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: mpi-specs: diff for NMU version 20040719-2.1
Processing control commands: tags 484003 + pending Bug #484003 [mpi-specs] Using obsolete .dhelp files Added tag(s) pending. tags 557409 + patch Bug #557409 [mpi-specs] Typo in package description: This packages Added tag(s) patch. tags 557409 + pending Bug #557409 [mpi-specs] Typo in package description: This packages Added tag(s) pending. tags 770411 + patch Bug #770411 [mpi-specs] mpi-specs: postinst uses /usr/share/doc content (Policy 12.3) Added tag(s) patch. tags 770411 + pending Bug #770411 [mpi-specs] mpi-specs: postinst uses /usr/share/doc content (Policy 12.3) Added tag(s) pending. -- 484003: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=484003 557409: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=557409 770411: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=770411 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#768675: mdp: FTBFS in jessie: tests failures
Ok, uploaded Tiziano it will be up to you to file an unblock request reportbug release.debian.org and provide debdiff (from 3.3-1) arguing the necessity of all the changes ;-) Cheers! -- Yaroslav O. Halchenko, Ph.D. http://neuro.debian.net http://www.pymvpa.org http://www.fail2ban.org Research Scientist,Psychological and Brain Sciences Dept. Dartmouth College, 419 Moore Hall, Hinman Box 6207, Hanover, NH 03755 Phone: +1 (603) 646-9834 Fax: +1 (603) 646-1419 WWW: http://www.linkedin.com/in/yarik -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#770411: mpi-specs: diff for NMU version 20040719-2.1
Control: tags 484003 + pending
Control: tags 557409 + patch
Control: tags 557409 + pending
Control: tags 770411 + patch
Control: tags 770411 + pending
Dear maintainer,
I've prepared an NMU for mpi-specs (versioned as 20040719-2.1) and
uploaded it to DELAYED/5. Please feel free to tell me if I
should delay it longer.
Regards.
--
.''`. Homepage: http://info.comodo.priv.at/ - OpenPGP key 0xBB3A68018649AA06
: :' : Debian GNU/Linux user, admin, and developer - http://www.debian.org/
`. `' Member of VIBE!AT SPI, fellow of the Free Software Foundation Europe
`- NP: Janis Joplin: Maybe
diff -u mpi-specs-20040719/debian/control mpi-specs-20040719/debian/control
--- mpi-specs-20040719/debian/control
+++ mpi-specs-20040719/debian/control
@@ -9,7 +9,7 @@
Architecture: all
Recommends: w3m|www-browser, xpdf-reader|pdf-viewer
Description: [EBOOK-DEV] MPI 1.1 and 2.0 Specifications of MPI Forum
- This packages includes the MPI Forum documents which covers 1.1 and 2.0
+ This package includes the MPI Forum documents which covers 1.1 and 2.0
specifications of the Message Passing Interface. Documents are all in HTML
format.
.
diff -u mpi-specs-20040719/debian/rules mpi-specs-20040719/debian/rules
--- mpi-specs-20040719/debian/rules
+++ mpi-specs-20040719/debian/rules
@@ -48,8 +48,6 @@
tar xvz -C $(R)/usr/share/doc/$(P) -f mpi-11-html.tar.gz
tar xvz -C $(R)/usr/share/doc/$(P) -f mpi-20-html.tar.gz
- cp debian/dhelp $(R)/usr/share/doc/$(P)/.dhelp
-
chmod a+x $(shell pwd)/debian/fixlinks \
cd $(R)/usr/share/doc/$(P) \
find . -name *.htm* | xargs $(shell pwd)/debian/fixlinks
reverted:
--- mpi-specs-20040719/debian/dhelp
+++ mpi-specs-20040719.orig/debian/dhelp
@@ -1,31 +0,0 @@
-item
-directorydevelopment/mpi
-filenamempi-11-html/mpi-report.html
-linknameMPI: A Message-Passing Interface Standard
-description
-The goal of the Message Passing Interface, simply stated, is to develop
-a widely used standard for writing message-passing programs. As such the
-interface should establish a practical, portable, efficient, and
-flexible standard for message passing.
-Beginning in March, 1995, the Message Passing Interface Forum reconvened
-to correct errors and make clarifications in the MPI document of May 5,
-1994, referred to below as Version 1.0. These discussions resulted in
-Version 1.1, which is this document.
-/description
-/item
-
-item
-directorydevelopment/mpi
-filenamempi-20-html/mpi2-report.html
-linknameMPI-2: Extensions to the Message-Passing Interface
-description
-This document describes the MPI-1.2 and MPI-2 standards. They are both
-extensions to the MPI-1.1 standard. The MPI-1.2 part of the document
-contains clarifications and corrections to the MPI-1.1 standard and
-defines MPI-1.2. The MPI-2 part of the document describes additions to
-the MPI-1 standard and defines MPI-2. These include miscellaneous
-topics, process creation and management, one-sided communications,
-extended collective operations, external interfaces, I/O, and additional
-language bindings.
-/description
-/item
reverted:
--- mpi-specs-20040719/debian/prerm
+++ mpi-specs-20040719.orig/debian/prerm
@@ -1,41 +0,0 @@
-#! /bin/sh
-# prerm script for mpi-specs
-#
-# see: dh_installdeb(1)
-
-set -e
-
-# summary of how this script can be called:
-#* prerm `remove'
-#* old-prerm `upgrade' new-version
-#* new-prerm `failed-upgrade' old-version
-#* conflictor's-prerm `remove' `in-favour' package new-version
-#* deconfigured's-prerm `deconfigure' `in-favour'
-# package-being-installed version `removing'
-# conflicting-package version
-# for details, see /usr/share/doc/packaging-manual/
-
-case $1 in
-remove|upgrade|deconfigure)
- if [ -x /usr/sbin/dhelp_parse ]; then
- /usr/sbin/dhelp_parse -d /usr/share/doc/mpi-specs
- fi
-;;
-failed-upgrade)
-;;
-*)
-echo prerm called with unknown argument \`$1' 2
-exit 0
-;;
-esac
-
-
-
-# dh_installdeb will replace this with shell code automatically
-# generated by other debhelper scripts.
-
-#DEBHELPER#
-
-exit 0
-
-
diff -u mpi-specs-20040719/debian/changelog mpi-specs-20040719/debian/changelog
--- mpi-specs-20040719/debian/changelog
+++ mpi-specs-20040719/debian/changelog
@@ -1,3 +1,30 @@
+mpi-specs (20040719-2.1) unstable; urgency=medium
+
+ * Non-maintainer upload.
+ * Documentation fix:
+Fix Using obsolete .dhelp files:
+- remove obsolete debian/dhelp file
+- don't try to install it from debian/rules anymore
+- add new debian/mpi-specs.doc-base.mpi?? files instead
+- drop dhelp_parse calls from debian/{prerm,postinst}
+Thanks, Esteban Manchado Velázquez.
+(Closes: #484003)
+ * RC bug fix:
+Fix postinst uses /usr/share/doc content (Policy 12.3):
+- debian/postinst: don't try to install debian/dhelp
+ as /usr/share/doc/mpi-specs/.dhelp; this has never worked but was only
+ tried when the (shipped)
Processed: mpi-specs: diff for NMU version 20040719-2.1
Processing control commands: tags 484003 + pending Bug #484003 [mpi-specs] Using obsolete .dhelp files Ignoring request to alter tags of bug #484003 to the same tags previously set tags 557409 + patch Bug #557409 [mpi-specs] Typo in package description: This packages Ignoring request to alter tags of bug #557409 to the same tags previously set tags 557409 + pending Bug #557409 [mpi-specs] Typo in package description: This packages Ignoring request to alter tags of bug #557409 to the same tags previously set tags 770411 + patch Bug #770411 [mpi-specs] mpi-specs: postinst uses /usr/share/doc content (Policy 12.3) Ignoring request to alter tags of bug #770411 to the same tags previously set tags 770411 + pending Bug #770411 [mpi-specs] mpi-specs: postinst uses /usr/share/doc content (Policy 12.3) Ignoring request to alter tags of bug #770411 to the same tags previously set -- 484003: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=484003 557409: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=557409 770411: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=770411 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#762745: marked as done ([CVE-2014-6051 to CVE-2014-6055] Multiple issues in libVNCserver)
Your message dated Fri, 28 Nov 2014 16:34:50 + with message-id e1xuovo-0007k4...@franck.debian.org and subject line Bug#762745: fixed in libvncserver 0.9.9+dfsg-6.1 has caused the Debian Bug report #762745, regarding [CVE-2014-6051 to CVE-2014-6055] Multiple issues in libVNCserver 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.) -- 762745: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=762745 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: libvncserver Severity: important Tags: security Hi there, the following vulnerabilities were published for libVNCserver: CVE-2014-6051 Integer overflow in MallocFrameBuffer() on client side. CVE-2014-6052 Lack of malloc() return value checking on client side. CVE-2014-6053 Server crash on a very large ClientCutText message. CVE-2014-6054 Server crash when scaling factor is set to zero. CVE-2014-6055 Multiple stack overflows in File Transfer feature. If you fix the vulnerabilities please also make sure to include the CVE (Common Vulnerabilities Exposures) id in your changelog entry. For further information see: http://seclists.org/oss-sec/2014/q3/639 Please adjust the affected versions in the BTS as needed and clone this bug if you are not going to fix all these problems together. Regards, luciano ---End Message--- ---BeginMessage--- Source: libvncserver Source-Version: 0.9.9+dfsg-6.1 We believe that the bug you reported is fixed in the latest version of libvncserver, 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 762...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Tobias Frost t...@debian.org (supplier of updated libvncserver 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: Sun, 23 Nov 2014 16:19:53 +0100 Source: libvncserver Binary: libvncclient0 libvncserver0 libvncserver-dev libvncserver-config libvncclient0-dbg libvncserver0-dbg linuxvnc Architecture: source amd64 Version: 0.9.9+dfsg-6.1 Distribution: unstable Urgency: medium Maintainer: Luca Falavigna dktrkr...@debian.org Changed-By: Tobias Frost t...@debian.org Description: libvncclient0 - API to write one's own vnc server - client library libvncclient0-dbg - debugging symbols for libvncclient libvncserver-config - API to write one's own vnc server - library utility libvncserver-dev - API to write one's own vnc server - development files libvncserver0 - API to write one's own vnc server libvncserver0-dbg - debugging symbols for libvncserver linuxvnc - VNC server to allow remote access to a tty Closes: 762745 Changes: libvncserver (0.9.9+dfsg-6.1) unstable; urgency=medium . * Non-maintainer upload. * CVE-2014-6051, CVE-2014-6052, CVE-2014-6053, CVE-2014-6054, CVE-2014-6055: Multiple issues in libVNCserver -- cherry picking targeted fixed from upstream (Closes: #762745) Checksums-Sha1: 6546f3f98c88d0bdc851f5641d2bf8b6bd02b057 2406 libvncserver_0.9.9+dfsg-6.1.dsc dfabe375125fffd77a13c98e7d313a6437490925 21860 libvncserver_0.9.9+dfsg-6.1.debian.tar.xz a9e8c19c6f542007f942e513f403f32e671eeb64 125226 libvncclient0_0.9.9+dfsg-6.1_amd64.deb 30e0f191ca5907e78c14a4c02bbe8452084cf602 192034 libvncserver0_0.9.9+dfsg-6.1_amd64.deb b0b6ff06bd03ff520edf4a62e0824ebd268cf0dd 275632 libvncserver-dev_0.9.9+dfsg-6.1_amd64.deb 92a549c988835ab7855de08c81920e5dedbbb3aa 90512 libvncserver-config_0.9.9+dfsg-6.1_amd64.deb efd4f67a6ebfd78d0ad8c8d2ce163d8808696d39 173156 libvncclient0-dbg_0.9.9+dfsg-6.1_amd64.deb c0ccdfe9c81db6882e24ac18c84d42716e979eb7 382900 libvncserver0-dbg_0.9.9+dfsg-6.1_amd64.deb adea0233aa3d38dec44d7d58c308ea19013c6498 86500 linuxvnc_0.9.9+dfsg-6.1_amd64.deb Checksums-Sha256: 7a28bf115be27d84240ac7a6c4964cddc7d4b7ef7d73133436b732219c1f5664 2406 libvncserver_0.9.9+dfsg-6.1.dsc 502670cd2ae96d5cbafa0387e94529421152617aa59d20d726a57e24e771a18a 21860 libvncserver_0.9.9+dfsg-6.1.debian.tar.xz 1e2b4fb28dea737cf0aa583552a57ff02244b378f9529f706e7dd8c8cd1deb37 125226 libvncclient0_0.9.9+dfsg-6.1_amd64.deb 15359ef274f3be793e78691dfef20ef5e4dbbc089e9f99fc8c79e249c05e5a5a 192034 libvncserver0_0.9.9+dfsg-6.1_amd64.deb
Bug#768675: marked as done (mdp: FTBFS in jessie: tests failures)
Your message dated Fri, 28 Nov 2014 16:34:58 + with message-id e1xuovw-0007mv...@franck.debian.org and subject line Bug#768675: fixed in mdp 3.3-2 has caused the Debian Bug report #768675, regarding mdp: FTBFS in jessie: tests failures 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.) -- 768675: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=768675 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Source: mdp Version: 3.3-1 Severity: serious Tags: jessie sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20141108 qa-ftbfs Justification: FTBFS in jessie on amd64 Hi, During a rebuild of all packages in jessie (in a jessie chroot, not a sid chroot), your package failed to build on amd64. Relevant part (hopefully): make[1]: Entering directory '/«PKGBUILDDIR»' dh_auto_install --destdir=/«PKGBUILDDIR»/debian/tmp running install running build running build_py running install_lib creating /«PKGBUILDDIR»/debian/tmp creating /«PKGBUILDDIR»/debian/tmp/usr creating /«PKGBUILDDIR»/debian/tmp/usr/lib creating /«PKGBUILDDIR»/debian/tmp/usr/lib/python2.7 creating /«PKGBUILDDIR»/debian/tmp/usr/lib/python2.7/dist-packages creating /«PKGBUILDDIR»/debian/tmp/usr/lib/python2.7/dist-packages/bimdp creating /«PKGBUILDDIR»/debian/tmp/usr/lib/python2.7/dist-packages/bimdp/test copying build/lib.linux-x86_64-2.7/bimdp/test/__init__.py - /«PKGBUILDDIR»/debian/tmp/usr/lib/python2.7/dist-packages/bimdp/test copying build/lib.linux-x86_64-2.7/bimdp/test/_tools.py - /«PKGBUILDDIR»/debian/tmp/usr/lib/python2.7/dist-packages/bimdp/test copying build/lib.linux-x86_64-2.7/bimdp/test/conftest.py - /«PKGBUILDDIR»/debian/tmp/usr/lib/python2.7/dist-packages/bimdp/test copying build/lib.linux-x86_64-2.7/bimdp/test/ide_run.py - /«PKGBUILDDIR»/debian/tmp/usr/lib/python2.7/dist-packages/bimdp/test copying build/lib.linux-x86_64-2.7/bimdp/test/test_biflow.py - /«PKGBUILDDIR»/debian/tmp/usr/lib/python2.7/dist-packages/bimdp/test copying build/lib.linux-x86_64-2.7/bimdp/test/test_bihinet.py - /«PKGBUILDDIR»/debian/tmp/usr/lib/python2.7/dist-packages/bimdp/test copying build/lib.linux-x86_64-2.7/bimdp/test/test_binode.py - /«PKGBUILDDIR»/debian/tmp/usr/lib/python2.7/dist-packages/bimdp/test copying build/lib.linux-x86_64-2.7/bimdp/test/test_gradient.py - /«PKGBUILDDIR»/debian/tmp/usr/lib/python2.7/dist-packages/bimdp/test copying build/lib.linux-x86_64-2.7/bimdp/test/test_namespace_fixups.py - /«PKGBUILDDIR»/debian/tmp/usr/lib/python2.7/dist-packages/bimdp/test copying build/lib.linux-x86_64-2.7/bimdp/test/test_parallelbiflow.py - /«PKGBUILDDIR»/debian/tmp/usr/lib/python2.7/dist-packages/bimdp/test copying build/lib.linux-x86_64-2.7/bimdp/test/test_parallelbihinet.py - /«PKGBUILDDIR»/debian/tmp/usr/lib/python2.7/dist-packages/bimdp/test creating /«PKGBUILDDIR»/debian/tmp/usr/lib/python2.7/dist-packages/bimdp/parallel copying build/lib.linux-x86_64-2.7/bimdp/parallel/__init__.py - /«PKGBUILDDIR»/debian/tmp/usr/lib/python2.7/dist-packages/bimdp/parallel copying build/lib.linux-x86_64-2.7/bimdp/parallel/parallelbiflow.py - /«PKGBUILDDIR»/debian/tmp/usr/lib/python2.7/dist-packages/bimdp/parallel copying build/lib.linux-x86_64-2.7/bimdp/parallel/parallelbihinet.py - /«PKGBUILDDIR»/debian/tmp/usr/lib/python2.7/dist-packages/bimdp/parallel creating /«PKGBUILDDIR»/debian/tmp/usr/lib/python2.7/dist-packages/bimdp/nodes copying build/lib.linux-x86_64-2.7/bimdp/nodes/__init__.py - /«PKGBUILDDIR»/debian/tmp/usr/lib/python2.7/dist-packages/bimdp/nodes copying build/lib.linux-x86_64-2.7/bimdp/nodes/autogen.py - /«PKGBUILDDIR»/debian/tmp/usr/lib/python2.7/dist-packages/bimdp/nodes copying build/lib.linux-x86_64-2.7/bimdp/nodes/gradient.py - /«PKGBUILDDIR»/debian/tmp/usr/lib/python2.7/dist-packages/bimdp/nodes copying build/lib.linux-x86_64-2.7/bimdp/nodes/miscnodes.py - /«PKGBUILDDIR»/debian/tmp/usr/lib/python2.7/dist-packages/bimdp/nodes creating /«PKGBUILDDIR»/debian/tmp/usr/lib/python2.7/dist-packages/bimdp/inspection copying build/lib.linux-x86_64-2.7/bimdp/inspection/__init__.py - /«PKGBUILDDIR»/debian/tmp/usr/lib/python2.7/dist-packages/bimdp/inspection copying build/lib.linux-x86_64-2.7/bimdp/inspection/facade.py - /«PKGBUILDDIR»/debian/tmp/usr/lib/python2.7/dist-packages/bimdp/inspection copying build/lib.linux-x86_64-2.7/bimdp/inspection/slideshow.py - /«PKGBUILDDIR»/debian/tmp/usr/lib/python2.7/dist-packages/bimdp/inspection copying build/lib.linux-x86_64-2.7/bimdp/inspection/tracer.py -
Bug#766762: upower: fatal memory leak on low battery
Michael Banck wrote (28 Nov 2014 15:51:26 GMT) : I've prepared an NMU by taking the git commit and will upload it to DELAYED/1-day later today. Debdiff is attached. I'll look into filing an unblock request as well. Thanks! -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#771341: segfaults in sqlite3_value_type while using from Python
Package: libsqlite3-0
Version: 3.7.13-1+deb7u1
Severity: serious
Originally detected I believe on sid installation, but forgot to capture the
version, I will try to replicate/report later. But very consistent with wheezy
(from which I am reporting now).
Triggered by the backport fail2ban 0.9.1-1~nd70+1 (available from
http://neuro.debian.net/debian-devel/ wheezy/main amd64 Packages apt repo) it
gets to
#0 sqlite3_value_type (pVal=0x0) at sqlite3.c:63805
#1 0x7570ee2e in sqlite3_column_type (pStmt=0x114eec8, i=optimized
out) at sqlite3.c:64447
#2 0x7599b3d4 in _pysqlite_fetch_one_row (self=0x11e3540) at
/home/jmm/py/python2.7-2.7.3/Modules/_sqlite/cursor.c:363
#3 0x7599d71d in pysqlite_cursor_iternext (self=0x11e3540) at
/home/jmm/py/python2.7-2.7.3/Modules/_sqlite/cursor.c:939
#4 0x0046d967 in listextend (self=0x107cb28, b=sqlite3.Cursor at
remote 0x11e3540) at ../Objects/listobject.c:872
#5 0x00471932 in list_init (self=0x107cb28, args=(sqlite3.Cursor at
remote 0x11e3540,), kw=0x0) at ../Objects/listobject.c:2458
#6 0x004b2092 in type_call (type=0x86dde0, args=(sqlite3.Cursor at
remote 0x11e3540,), kwds=0x0) at ../Objects/typeobject.c:737
#7 0x004291af in PyObject_Call (func=type at remote 0x86dde0,
arg=(sqlite3.Cursor at remote 0x11e3540,), kw=0x0) at
../Objects/abstract.c:2529
#8 0x0052977e in do_call (func=type at remote 0x86dde0,
pp_stack=0x752a0490, na=1, nk=0) at ../Python/ceval.c:4239
#9 0x00528b3b in call_function (pp_stack=0x752a0490, oparg=1) at
../Python/ceval.c:4044
#10 0x00523733 in PyEval_EvalFrameEx (f=
Frame 0x10f0ba0, for file
/usr/lib/python2.7/dist-packages/fail2ban/server/database.py, line 467, in
getBansMerged
(self=Fail2BanDb(_dbFilename='/var/lib/fail2ban/fail2ban.sqlite3',
_db=sqlite3.Connection at remote 0x11178c0, _lock=thread.lock at remote
0xf2ad10, _purgeAge=86400, _bansMergedCache={('113.12.202.186',
Jail(_Jail__actions=Actions(active=True, _Thread__ident=140737306576640,
run=function at remote 0x1056840, _jail=...,
_Thread__block=_Condition(_Verbose__verbose=False,
_Condition__lock=thread.lock at remote 0x106f0e0, acquire=built-in method
acquire of thread.lock object at remote 0x106f0e0, _Condition__waiters=[],
release=built-in method release of thread.lock object at remote 0x106f0e0) at
remote 0x1070290, _Thread__name='Thread-5', _Thread__daemonic=False,
_actions=OrderedDict(_OrderedDict__root=[[[...], [...], 'iptables-multiport'],
[...], None], _OrderedDict__map={'iptables-multiport': [...]}) at remote
0x11181c0, sleeptime=1, _Thread__start
ed=_Event(_Verbose__verbose=F...(truncated), throwflag=0) at
../Python/ceval.c:2666
#11 0x00526121 in PyEval_EvalCodeEx (co=0xf18670, globals=
{'locale': module at remote 0xe4f7b0, 'commitandrollback': function at
remote 0xf2bc30, 'MyTime': classobj at remote 0xd51520, 'Fail2BanDb': type
at remote 0xf3a820, 'shutil': module at remote 0xf1be98, 'wraps': function
at remote 0xcc1258, '__package__': 'fail2ban.server', 'json': module at
remote 0xeb6f00, 'sqlite3': module at remote 0xf1b3a0, 'FailTicket':
classobj at remote 0xd51228, '__doc__': None, '__license__': 'GPL',
'__builtins__': {'bytearray': type at remote 0x85fd20, 'IndexError': type at
remote 0x866360, 'all': built-in function all, 'help': _Helper at remote
0xb25fb0, 'vars': built-in function vars, 'SyntaxError': type at remote
0x865ce0, 'unicode': type at remote 0x87d040, 'UnicodeDecodeError': type at
remote 0x866c80, 'memoryview': type at remote 0x870c00, 'isinstance':
built-in function isinstance, 'copyright':
_Printer(_Printer__data='Copyright (c) 2001-2012 Python Software
Foundation.\nAll Rights Reserved.\n\nCopyright (c
) 2000 BeOpen.com.\nAll Rights...(truncated), locals=0x0, args=0x11556b8,
argcount=1, kws=
0x11556c0, kwcount=2, defs=0xf28c08, defcount=3, closure=0x0) at
../Python/ceval.c:3253
#12 0x00528f36 in fast_function (func=function at remote 0xf58450,
pp_stack=0x752a0950, n=5, na=1, nk=2) at ../Python/ceval.c:4117
#13 0x00528b1f in call_function (pp_stack=0x752a0950, oparg=512) at
../Python/ceval.c:4042
#14 0x00523733 in PyEval_EvalFrameEx (f=
Frame 0x1155520, for file
/usr/lib/python2.7/dist-packages/fail2ban/server/actions.py, line 274, in
lambda (jail=Jail(_Jail__actions=Actions(active=True,
_Thread__ident=140737306576640, run=function at remote 0x1056840,
_jail=..., _Thread__block=_Condition(_Verbose__verbose=False,
_Condition__lock=thread.lock at remote 0x106f0e0, acquire=built-in method
acquire of thread.lock object at remote 0x106f0e0, _Condition__waiters=[],
release=built-in method release of thread.lock object at remote 0x106f0e0) at
remote 0x1070290, _Thread__name='Thread-5', _Thread__daemonic=False,
_actions=OrderedDict(_OrderedDict__root=[[[...], [...], 'iptables-multiport'],
[...], None], _OrderedDict__map={'iptables-multiport': [...]}) at
Processed: wine: Proposing patch and merging 771104/769473
Processing control commands: tag -1 patch Bug #771104 [wine] [wine] wine is no more usable Bug #769473 [wine] wine: starts in a tiny and inoperable window Ignoring request to alter tags of bug #771104 to the same tags previously set Ignoring request to alter tags of bug #769473 to the same tags previously set forcemerge 771104 769473 Bug #771104 [wine] [wine] wine is no more usable Bug #769473 [wine] wine: starts in a tiny and inoperable window Bug #769473 [wine] wine: starts in a tiny and inoperable window Merged 769473 771104 -- 769473: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=769473 771104: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=771104 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#766762: upower: fatal memory leak on low battery
Hi, Le 28/11/2014 16:51, Michael Banck a écrit : I had a quick chat with a release team member and they seem to believe this bug warrants RC status: azeem so upowerd tends to eat up 2+GB in some cases due to a memleak, RC or not? azeem (2GB memory, that is) LocutusOfBorg1 2GB is not too much anymore :) azeem well, at 2GB my notebook keeps thrashing, and with luck I get to the console and kill -9 it azeem not sure what the upper bound is thijs I'd say RC thijs can always downgrade later if impact is better understood I have one system with 32GB of RAM where I've seen upower use 18GB (thanks to a low-battery warning on the wireless mouse attached to the computer...), so there's a fair chance there is no upper bound. Regards, Stephen -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: wine: Proposing patch and merging 771104/769473
Processing control commands: tag -1 patch Bug #769473 [wine] wine: starts in a tiny and inoperable window Added tag(s) patch. forcemerge 771104 769473 Bug #771104 [wine] [wine] wine is no more usable Bug #769473 [wine] wine: starts in a tiny and inoperable window Severity set to 'grave' from 'important' Bug #771104 [wine] [wine] wine is no more usable Added tag(s) patch. Merged 769473 771104 -- 769473: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=769473 771104: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=771104 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#771104: wine: Proposing patch and merging 771104/769473
control: tag -1 patch
control: forcemerge 771104 769473
That should be the same bugs. See attached the patch, doing it the same
way like wine-development.
Greets
jre
diff --git a/debian/control.in b/debian/control.in
index c444684..9d5149d 100644
--- a/debian/control.in
+++ b/debian/control.in
@@ -111,6 +111,8 @@ Depends:
${misc:Depends},
${shlibs:Depends},
x11-utils,
+ libfreetype6,
+ libncurses5,
libwine-gecko-2.21
Breaks:
wine ( 1.6.1-9),
Bug#766762: upower: fatal memory leak on low battery
On Fri, Nov 28, 2014 at 04:51:25PM +0100, Michael Banck wrote:
Debdiff is attached.
Sorry, now is.
Michael
diff -Nru upower-0.99.1/debian/changelog upower-0.99.1/debian/changelog
--- upower-0.99.1/debian/changelog 2014-09-02 18:50:42.0 +0200
+++ upower-0.99.1/debian/changelog 2014-11-28 16:42:02.0 +0100
@@ -1,3 +1,12 @@
+upower (0.99.1-3.1) unstable; urgency=medium
+
+ * Non-maintainer upload.
+ * debian/patches/git-fix-memleak.patch
+- Memleak fix. Taken from upstream git head, commit 4221835f (Closes:
+ #766762).
+
+ -- Michael Banck mba...@debian.org Fri, 28 Nov 2014 16:24:34 +0100
+
upower (0.99.1-3) unstable; urgency=medium
* debian/tests/build: Drop up_client_get_can_suspend() call, this got
diff -Nru upower-0.99.1/debian/patches/git-fix-memleak.patch
upower-0.99.1/debian/patches/git-fix-memleak.patch
--- upower-0.99.1/debian/patches/git-fix-memleak.patch 1970-01-01
01:00:00.0 +0100
+++ upower-0.99.1/debian/patches/git-fix-memleak.patch 2014-11-28
16:23:18.0 +0100
@@ -0,0 +1,90 @@
+From 4221835fae97f875a23d0ce449e955f2ea488bbc Mon Sep 17 00:00:00 2001
+From: Peter Wu pe...@lekensteyn.nl
+Date: Tue, 18 Nov 2014 06:04:08 +0100
+Subject: daemon: properly disconnect signals, stop memleak
+
+Whenever the daemon is polling on a device, a new signal is connected to
+the object. This signal was not disconnected when polling stops which
+resulted in a memory leak. Furthermore, whenever the warning-level
+property is updated, the signal would result in an exponentially raising
+call count (this happens when the battery percentage changes for
+example).
+
+https://bugs.freedesktop.org/show_bug.cgi?id=82659
+
+Reported-by: Alexander Jesner alexan...@jesner.eu
+Signed-off-by: Peter Wu pe...@lekensteyn.nl
+
+diff --git a/src/up-daemon.c b/src/up-daemon.c
+index 63ea7d1..d6420fc 100644
+--- a/src/up-daemon.c
b/src/up-daemon.c
+@@ -69,6 +69,7 @@ struct UpDaemonPrivate
+ UpDeviceList*power_devices;
+ guintaction_timeout_id;
+ GHashTable *poll_timeouts;
++ GHashTable *idle_signals;
+
+ /* Properties */
+ gboolean on_battery;
+@@ -952,6 +953,7 @@ up_daemon_start_poll (GObject *object,
+ UpDevice *device;
+ TimeoutData *data;
+ guint timeout;
++ ulong handler_id;
+ char *name;
+
+ device = UP_DEVICE (object);
+@@ -969,8 +971,10 @@ up_daemon_start_poll (GObject *object,
+ timeout = calculate_timeout (device);
+ data-timeout = timeout;
+
+- g_signal_connect (device, notify::warning-level,
+-G_CALLBACK (change_idle_timeout), NULL);
++ handler_id = g_signal_connect (device, notify::warning-level,
++ G_CALLBACK (change_idle_timeout), NULL);
++ g_hash_table_insert (daemon-priv-idle_signals, device,
++ GUINT_TO_POINTER (handler_id));
+ g_object_weak_ref (object, device_destroyed, daemon);
+
+ data-id = g_timeout_add_seconds (timeout, fire_timeout_callback,
device);
+@@ -991,10 +995,20 @@ up_daemon_stop_poll (GObject *object)
+ UpDevice *device;
+ TimeoutData *data;
+ UpDaemon *daemon;
++ gpointer value;
++ gulong handle_id;
+
+ device = UP_DEVICE (object);
+ daemon = up_device_get_daemon (device);
+
++ value = g_hash_table_lookup (daemon-priv-idle_signals, device);
++ if (value != NULL) {
++ handle_id = GPOINTER_TO_UINT (value);
++ if (g_signal_handler_is_connected (device, handle_id))
++ g_signal_handler_disconnect (device, handle_id);
++ g_hash_table_remove (daemon-priv-idle_signals, device);
++ }
++
+ data = g_hash_table_lookup (daemon-priv-poll_timeouts, device);
+ if (data == NULL)
+ return;
+@@ -1137,6 +1151,7 @@ up_daemon_init (UpDaemon *daemon)
+
+ daemon-priv-poll_timeouts = g_hash_table_new_full (g_direct_hash,
g_direct_equal,
+NULL, g_free);
++ daemon-priv-idle_signals = g_hash_table_new (g_direct_hash,
g_direct_equal);
+ }
+
+ /**
+@@ -1281,6 +1296,7 @@ up_daemon_finalize (GObject *object)
+ g_source_remove (priv-props_idle_id);
+
+ g_clear_pointer (priv-poll_timeouts, g_hash_table_destroy);
++ g_clear_pointer (priv-idle_signals, g_hash_table_destroy);
+
+ g_clear_pointer (daemon-priv-changed_props, g_hash_table_unref);
+ if (priv-proxy != NULL)
+--
+cgit v0.10.2
+
diff -Nru upower-0.99.1/debian/patches/series
upower-0.99.1/debian/patches/series
--- upower-0.99.1/debian/patches/series 2014-09-02 18:50:42.0 +0200
+++ upower-0.99.1/debian/patches/series 2014-11-28 16:24:28.0 +0100
@@ -1,3 +1,4 @@
git-tests-without-session-bus.patch
git-tests-py3.4.patch
git-split-tests.patch
Bug#769716: iceweasel: downloads Cisco's OpenH264 video codec
Hey Mike. On Fri, 2014-11-28 at 00:44 +0900, Mike Hommey wrote: a) it's not in any release of Debian, and it's not in any upcoming release of Debian either. It's in a package from experimental. Well but you know that a lot of people actually run unstable as their normal suite and many of them pull in iceweasel from experimental, just as you guys suggest here http://mozilla.debian.net/ Since these versions are usually up to date with what Mozilla ships, there's also not that big problem with the missing security support in experimental. b) everyone knows what's actually contained in that binary blob, since it's built from open source code, and the build is (supposed to be) reproductible. Well but since the blob is still fetched from cisco, they could simply replace it for certain users, and once you're hacked there's basically no way to tell whether you had a good version or not. c) the binary blob is verified against a sha256 checksum downloaded from a mozilla server through HTTPS with certificate pinning. Ah,.. I was actually looking for that in the code for something like that, but couldn't find it a the place where the download apparently happens - but I only had a very short glance on it. Could you perhaps please elaborate a bit more on how that actually works: - the checksum over the binary download is stored on a mozilla server? - downloaded via https? (at that point, the way of verifying should in principle also protect against downgrade attacks, as SSL/TLS should protect against replaying... BUT this alone doesn't protect against blocking attacks) - and you say certificate pinning? since that could mean a lot, what exactly? Is there a hardcoded cert known to be controlled by Mozilla? Is there a hardcoded CA from the Mozilla CA bundle (which would then in principle still allow that CA to issue a forged cert to someone else)? Or is it pinning in the sense of HSTS, i.e. pinning of any cert (from any trusted CA - even CNNIC) on the first access (which is quite insecure IMHO)? - has someone really checked that reproducibility? So it's not as bad as you make it sound. Well,.. admittedly, when you say that there *is* some hash sum verification (which I just didn't find)... then it's less worse as I've though. Nevertheless, it's still at least remotely possible that this could have been used to compromise systems, and even if there aren't masses who run at experimental, these people are probably still unhappy about that chance. If the bug would have been set to a higher severity, then people with apt-listbugs would have at least noticed it :-( And it's not going to stay that way anyways. It's really good we have the Iceweasel fork for things like these. Actually I'd also like to see that in Debian we remove certain trusted CAs, which are basically never used on the web and which are clearly untrustworthy. Can't you make a quit release where the codec is disabled, or at least fresh downloading of it? What will be the policy in Debian when Mozilla adds more and more proprietary/binary stuff to FF? Like e.g. the Adobe DRM stuff. Is that going to be removed from the beginning or will I have to take care that I don't accidentally get DRM-root-kitted with one of the first iceweasel-experimental releases? Cheers, Chris. smime.p7s Description: S/MIME cryptographic signature
Bug#769830: [Pkg-running-devel] Bug#769830: fix
Quoting Salvo Tomaselli (tipos...@tiscali.it): On Fri, 28 Nov 2014 07:28:25 +0100 Christian PERRIER bubu...@debian.org wrote: Please leave me a chance to try fixing the issue by a maintainer upload. I'm not the usual uploader for subsurface (Sylvestre is) and then I left him priority to fix that RC bug. But, well, as team member, I still feel the duty of fixing our RC bugs and would then prefer a maintainer upload. Is one week delay OK for you (there are chances I look at this during the week-end) ? Yes this is okay for me. It's just that I've contributed upstream and in Debian, and I wouldn't want the package to be dropped from testing. Given that the package is team-maintained and you are interested in the package itself, how about joining the pkg-running team (OK, the name is now not well adapted as we also maintain other sport-related software but your get the point, of course.so, in short, you don't have to run in order to join the team..:-)) That would indeed also fit my goal of this needed upload to be done from the package's git repo. signature.asc Description: Digital signature
Bug#771348: needrestart: starts not running services
Package: needrestart Version: 1.2-5 Severity: critical Tags: security Hi. Apparently needrestart has some bug, which causes it to start not running services. I have e.g.: $ ps ax | grep ssh 2927 pts/4S+ 0:00 ssh kronecker 2939 ?Ss 0:00 ssh: /home/calestyo/.ssh/control-mux/heisenberg_r...@kronecker.example.org:22 [mux] 3026 pts/3S+ 0:00 ssh klenze 4257 ?Ss 0:00 /usr/bin/ssh-agent /usr/bin/dbus-launch --exit-with-session cinnamon-session-cinnamon 17048 pts/5S+ 0:00 grep --color=auto ssh = as you can see, no sshd is running Then I run: # needrestart -v [Core] Using UI 'NeedRestart::UI::stdio'... [main] detected systemd [main] #1749 uses obsolete /lib/x86_64-linux-gnu/libpng12.so.0.50.0 [main] #1749 is not a child [main] #1879 uses obsolete /lib/x86_64-linux-gnu/liblzma.so.5.0.0 [main] #1879 is not a child [main] #1910 uses obsolete /lib/x86_64-linux-gnu/liblzma.so.5.0.0 [main] #1910 is not a child [Core] #1933 is a NeedRestart::Interp::Python [main] #1977 uses obsolete /usr/lib/x86_64-linux-gnu/libcroco-0.6.so.3.0.1 [main] #1977 is not a child [main] #2009 uses obsolete /lib/x86_64-linux-gnu/security/pam_systemd.so [main] #2009 is a child of #1982 [main] #2062 uses obsolete binary /usr/bin/python2.7 [main] #2062 is not a child [main] #2540 uses obsolete /lib/x86_64-linux-gnu/liblzma.so.5.0.0 [main] #2540 is not a child [main] #2608 uses obsolete /lib/x86_64-linux-gnu/libpng12.so.0.50.0 [main] #2608 is a child of #2540 [main] #2620 uses obsolete /usr/lib/x86_64-linux-gnu/libidn.so.11.6.12 [main] #2620 is not a child [main] #2621 uses obsolete /usr/lib/x86_64-linux-gnu/libidn.so.11.6.12 [main] #2621 is a child of #2620 [main] #2649 uses obsolete /usr/lib/x86_64-linux-gnu/libFLAC.so.8.3.0 [main] #2649 is not a child [main] #2763 uses obsolete /usr/lib/x86_64-linux-gnu/libidn.so.11.6.12 [main] #2763 is not a child [main] #2764 uses obsolete /usr/lib/x86_64-linux-gnu/libidn.so.11.6.12 [main] #2764 is a child of #2763 [main] #2782 uses obsolete /usr/lib/x86_64-linux-gnu/libFLAC.so.8.3.0 [main] #2782 is not a child [main] #2927 uses obsolete /lib/x86_64-linux-gnu/libkeyutils.so.1.5 [main] #2927 is a child of #2897 [main] #2939 uses obsolete /lib/x86_64-linux-gnu/libkeyutils.so.1.5 [main] #2939 is not a child [main] #3026 uses obsolete /lib/x86_64-linux-gnu/libkeyutils.so.1.5 [main] #3026 is a child of #2806 [main] #4208 uses obsolete /lib/x86_64-linux-gnu/security/pam_systemd.so [main] #4208 is a child of #2540 [main] #4217 uses obsolete /lib/x86_64-linux-gnu/libz.so.1.2.8 [main] #4217 is not a child [main] #4220 uses obsolete /lib/x86_64-linux-gnu/libudev.so.1.5.0 [main] #4220 is a child of #4208 [main] #4261 uses obsolete /lib/x86_64-linux-gnu/liblzma.so.5.0.0 [main] #4261 is not a child [main] #4270 uses obsolete /lib/x86_64-linux-gnu/libz.so.1.2.8 [main] #4270 is not a child [main] #4278 uses obsolete /lib/x86_64-linux-gnu/libkeyutils.so.1.5 [main] #4278 is a child of #4220 [main] #4294 uses obsolete /lib/x86_64-linux-gnu/libudev.so.1.5.0 [main] #4294 is not a child [main] #4296 uses obsolete /lib/x86_64-linux-gnu/libpng12.so.0.50.0 [main] #4296 is not a child [main] #4300 uses obsolete /lib/x86_64-linux-gnu/libudev.so.1.5.0 [main] #4300 is not a child [main] #4315 uses obsolete /lib/x86_64-linux-gnu/libpng12.so.0.50.0 [main] #4315 is not a child [main] #4328 uses obsolete /lib/x86_64-linux-gnu/libpng12.so.0.50.0 [main] #4328 is not a child [main] #4332 uses obsolete /lib/x86_64-linux-gnu/libpng12.so.0.50.0 [main] #4332 is not a child [main] #4336 uses obsolete /lib/x86_64-linux-gnu/libpng12.so.0.50.0 [main] #4336 is not a child [main] #4341 uses obsolete /lib/x86_64-linux-gnu/libpng12.so.0.50.0 [main] #4341 is not a child [main] #4344 uses obsolete binary /usr/bin/python2.7 [main] #4344 is a child of #4220 [main] #4348 uses obsolete /lib/x86_64-linux-gnu/libkeyutils.so.1.5 [main] #4348 is not a child [main] #4353 uses obsolete /usr/lib/x86_64-linux-gnu/libgudev-1.0.so.0.2.0 [main] #4353 is a child of #4344 [main] #4359 uses obsolete /lib/x86_64-linux-gnu/libudev.so.1.5.0 [main] #4359 is a child of #4220 [main] #4360 uses obsolete /usr/lib/x86_64-linux-gnu/libcroco-0.6.so.3.0.1 [main] #4360 is a child of #4220 [main] #4362 uses obsolete /lib/x86_64-linux-gnu/libudev.so.1.5.0 [main] #4362 is a child of #4220 [main] #4363 uses obsolete /lib/x86_64-linux-gnu/libudev.so.1.5.0 [main] #4363 is a child of #4361 [main] #4364 uses obsolete /usr/lib/x86_64-linux-gnu/libcroco-0.6.so.3.0.1 [main] #4364 is a child of #4220 [main] #4374 uses obsolete /lib/x86_64-linux-gnu/libz.so.1.2.8 [main] #4374 is not a child [main] #4383 uses obsolete /lib/x86_64-linux-gnu/libz.so.1.2.8 [main] #4383 is not a child [main] #4390 uses obsolete /lib/x86_64-linux-gnu/libudev.so.1.5.0 [main] #4390 is not a child [main] #4406 uses obsolete /lib/x86_64-linux-gnu/libpng12.so.0.50.0 [main] #4406 is not a child [main] #4472 uses obsolete
Bug#768112: fixed in slurm-llnl 14.03.9-4
Hi Adam, Thanks for adding the tag and for the unblock! Le 2014-11-26 20:08, Adam D. Barratt a écrit : I'm not sure acceptable is really the right word, and I've argued with myself a bunch over this, particularly given that sinfo+slurm-llnl is basically a closed set for dependency purposes, with a combined popcon of ~100. FWIW, slurm-llnl falls in the case of the packages usually installed in environments without any internet connectivity or where popcon is disabled. At work here, FWIW, we have _thousands_ of machines using this package. I also know a few similar places with the same size and configuration. Slurm is the most used job scheduler in the HPC world. It became a reference in the field. So really, popcon should not be a way to appreciate the importance of the package. I agree it is not easy though since we don't always have the necessary data to measure that. Regards, -- Mehdi -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#770597: marked as done (google-android-build-tools-installer: missing dependency on unzip and ca-certificates)
Your message dated Fri, 28 Nov 2014 19:04:03 + with message-id e1xuqpn-0001sz...@franck.debian.org and subject line Bug#770597: fixed in google-android-build-tools-installer 20.0.0.2 has caused the Debian Bug report #770597, regarding google-android-build-tools-installer: missing dependency on unzip and ca-certificates 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.) -- 770597: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=770597 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: google-android-build-tools-installer Version: 20.0.0.1 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed your package failed to install. As per definition of the release team this makes the package too buggy for a release, thus the severity. From the attached log (scroll to the bottom...): 2014-11-20 10:04:38 (9.00 MB/s) - 'build-tools_r20-linux.zip' saved [21445463/21445463] md5sum -c build-tools_r20-linux.zip.md5 build-tools_r20-linux.zip: OK sha1sum -c build-tools_r20-linux.zip.sha1 build-tools_r20-linux.zip: OK sha256sum -c build-tools_r20-linux.zip.sha256 build-tools_r20-linux.zip: OK cd /var/cache/google-android-build-tools-installer unzip -ou build-tools_r20-linux.zip /bin/sh: 1: unzip: not found Makefile:62: recipe for target '/var/cache/google-android-build-tools-installer//var/cache/google-android-build-tools-installer/android-4.4W/aapt' failed make: *** [/var/cache/google-android-build-tools-installer//var/cache/google-android-build-tools-installer/android-4.4W/aapt] Error 127 make: Leaving directory '/var/cache/google-android-build-tools-installer' dpkg: error processing package google-android-build-tools-installer (--configure): subprocess installed post-installation script returned error exit status 2 Errors were encountered while processing: google-android-build-tools-installer This was a test with --install-recommends, so ca-certificates was installed, but that would have failed as well like in google-android-sdk-docs-installer. cheers, Andreas google-android-build-tools-installer_20.0.0.1.log.gz Description: application/gzip ---End Message--- ---BeginMessage--- Source: google-android-build-tools-installer Source-Version: 20.0.0.2 We believe that the bug you reported is fixed in the latest version of google-android-build-tools-installer, 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 770...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Hans-Christoph Steiner h...@eds.org (supplier of updated google-android-build-tools-installer 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: Wed, 26 Nov 2014 13:55:29 +0100 Source: google-android-build-tools-installer Binary: google-android-build-tools-installer Architecture: source i386 Version: 20.0.0.2 Distribution: unstable Urgency: medium Maintainer: Android tools Maintainer android-tools-de...@lists.alioth.debian.org Changed-By: Hans-Christoph Steiner h...@eds.org Description: google-android-build-tools-installer - Google build tools for Android (aapt, aidl, dexdump, dx) Closes: 770597 Changes: google-android-build-tools-installer (20.0.0.2) unstable; urgency=medium . [Reiner Herrmann] * added unzip and ca-certificates to Depends (Closes: #770597) Checksums-Sha1: 819b6020f9bbd73cdfa9a55567141b4ba659f6d1 1998 google-android-build-tools-installer_20.0.0.2.dsc 3cbfad9d0db24fde6c9873ebff33a61d8ae35c3e 3432 google-android-build-tools-installer_20.0.0.2.tar.xz 05ff69080f0fd3453689db2354c479c41fd30141 3854 google-android-build-tools-installer_20.0.0.2_i386.deb Checksums-Sha256: be7fd31ae1b22b64ee4920862edeeb4fc8b54ed75c2126a53e7e02b8b71f986c 1998 google-android-build-tools-installer_20.0.0.2.dsc dedced859e649f9f53ea39828e70a29dda6a5b66decbde5c7cf21f4f1822b808 3432 google-android-build-tools-installer_20.0.0.2.tar.xz 5799c10b61a650ffb8b24f6009d2acd9748fc717e7e8e67d228ae6cb9dac7266 3854 google-android-build-tools-installer_20.0.0.2_i386.deb Files: ba5a4ec0af662704756b684884a42c87 1998 contrib/devel optional
Bug#771177: develock-el: breaks c++ mode in sid and jessie
Le 2014-11-27 12:25, Francois Marier a écrit : Package: develock-el Version: 0.39-1 Severity: grave Justification: renders package unusable This package completely breaks the standard emacs c++ mode. I can agree that the package can be of no interest for you when it breaks the C++ mode, but it can be no way an argument to make this bug RC since all features of the package are not broken, on the contrary. And, fwiw, I am absolutely against upgrading the package _now_ to 0.45. I'll look more closely at the package instead to see if some smaller fix can be found. -- Mehdi -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#771360: CVE-2010-5109
Package: claws Severity: grave Tags: security Hi, claws-mail embeds a copy of libytnef: | claws-mail (3.10.1-1) unstable; urgency=medium | | - Remove libytnef dependency: it was assimilated (and modified) But it's missing the security fix CVE-2010-5109, I'm attaching the patch from src:libytnef Can you please fix this for jessie and forward the patch upstream? Cheers, Moritz Index: b/ytnef.c === --- a/ytnef.c +++ b/ytnef.c @@ -1328,7 +1328,7 @@ comp_Prebuf.size = strlen(RTF_PREBUF); comp_Prebuf.data = calloc(comp_Prebuf.size, 1); -strcpy(comp_Prebuf.data, RTF_PREBUF); +memcpy(comp_Prebuf.data, RTF_PREBUF, comp_Prebuf.size); src = p-data; in = 0;
Processed: reassign 771360 to claws-mail-tnef-parser
Processing commands for cont...@bugs.debian.org: reassign 771360 claws-mail-tnef-parser Bug #771360 [claws] CVE-2010-5109 Warning: Unknown package 'claws' Bug reassigned from package 'claws' to 'claws-mail-tnef-parser'. Ignoring request to alter found versions of bug #771360 to the same values previously set Ignoring request to alter fixed versions of bug #771360 to the same values previously set thanks Stopping processing here. Please contact me if you need assistance. -- 771360: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=771360 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: tagging 770689, tagging 770692
Processing commands for cont...@bugs.debian.org: tags 770689 + fixed-upstream Bug #770689 [python-pycuda] python-pycuda: Insecure temporary file creation for kernel cache Added tag(s) fixed-upstream. tags 770692 + fixed-upstream Bug #770692 [python-pyopencl] python-pyopencl: Insecure temporary file creation for kernel cache Added tag(s) fixed-upstream. thanks Stopping processing here. Please contact me if you need assistance. -- 770689: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=770689 770692: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=770692 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#771369: latex-mk: unsatisfied build-dependendcy in jessie
Source: latex-mk Severity: serious Version: 2.1-1.2 Tags: jessie User: trei...@debian.org Usertags: edos-uninstallable Hi, latex-mk has a Build-Depends-Indep on tgif. However, tgif is not in jessie. -Ralf. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#763994: marked as done (eclipse: no java or c++ project available in filenew)
Your message dated Fri, 28 Nov 2014 21:22:14 + with message-id e1xuszw-0001kc...@franck.debian.org and subject line Bug#763994: fixed in eclipse 3.8.1-7 has caused the Debian Bug report #763994, regarding eclipse: no java or c++ project available in filenew 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.) -- 763994: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=763994 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: eclipse Version: 3.8.1-6 Severity: grave Justification: renders package unusable Dear Maintainer, I see no option for Java or C++ Project in FileNew. There is only: Project | Folder, File, Untitled Text File | Other... This situation is on two machines: -- fresh installation of eclipse -- old installation, constantly updated by APT, by not used in two years, fresh workspace From other bug reports i've learnt that sat4j causes probles but after downgrading to 2.3.1-1 and 2.3.0-3 the situation is the same. It's almost the same as bug 735096 (another architecture configuration and package version). https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=735096 But this leads rather to Equinox Provisioning Engine: $ cat workspace/.metadata/.log !SESSION 2014-09-28 21:30:33.966 --- eclipse.buildId=debbuild java.version=1.7.0_65 java.vendor=Oracle Corporation BootLoader constants: OS=linux, ARCH=x86, WS=gtk, NL=pl_PL Command-line arguments: -os linux -ws gtk -arch x86 !ENTRY org.eclipse.equinox.p2.engine 4 4 2014-09-28 21:30:42.835 !MESSAGE An error occurred while installing the items !SUBENTRY 1 org.eclipse.equinox.p2.engine 4 0 2014-09-28 21:30:42.835 !MESSAGE session context was:(profile=PlatformProfile, phase=org.eclipse.equinox.internal.p2.engine.phases.Install, operand=null -- [R]org.eclipse.help.feature.jar 1.4.1.dist-8v7oFRvFCmSPZkILLj597H, action=org.eclipse.equinox.internal.p2.touchpoint.eclipse.actions.InstallFeatureAction). !SUBENTRY 1 org.eclipse.equinox.p2.touchpoint.eclipse 4 0 2014-09-28 21:30:42.835 !MESSAGE The artifact file for org.eclipse.update.feature,org.eclipse.help,1.4.1.dist-8v7oFRvFCmSPZkILLj597H was not found. Version of eclipse-cdt 8.4.0-1 $ ls /usr/share/eclipse/dropins cdt jdt sdk Thank you for your help semmreh -- System Information: Debian Release: jessie/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: i386 (x86_64) Foreign Architectures: amd64 Kernel: Linux 3.16-1-amd64 (SMP w/2 CPU cores) Locale: LANG=pl_PL.UTF-8, LC_CTYPE=pl_PL.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages eclipse depends on: ii eclipse-jdt 3.8.1-6 ii eclipse-pde 3.8.1-6 eclipse recommends no packages. eclipse suggests no packages. Versions of packages eclipse-platform depends on: ii ant1.9.4-1 ii ant-optional 1.9.4-1 ii default-jre [java6-runtime]2:1.7-52 ii eclipse-platform-data 3.8.1-6 ii eclipse-rcp3.8.1-6 ii gconf-service 3.2.6-3 ii java-common0.52 ii libc6 2.19-11 ii libcommons-codec-java 1.9-1 ii libcommons-httpclient-java 3.1-10.2 ii libcommons-logging-java1.2-1 ii libgconf-2-4 3.2.6-3 ii libglib2.0-0 2.40.0-5 ii libjetty8-java 8.1.16-1 ii libjsch-java 0.1.51-1 ii liblucene2-java2.9.4+ds1-4 ii libservlet3.0-java 7.0.55-1 ii multiarch-support 2.19-11 ii openjdk-7-jre [java6-runtime] 7u65-2.5.2-3 ii sat4j 2.3.3-1 Versions of packages eclipse-platform recommends: ii eclipse-pde 3.8.1-6 Versions of packages eclipse-platform suggests: ii eclipse-jdt 3.8.1-6 Versions of packages eclipse-pde depends on: ii default-jre [java6-runtime]2:1.7-52 ii eclipse-jdt3.8.1-6 ii eclipse-platform 3.8.1-6 ii libasm3-java 3.3.2-2 ii openjdk-7-jre [java6-runtime] 7u65-2.5.2-3 eclipse-pde suggests no packages. Versions of packages eclipse-jdt depends on: ii default-jre [java6-runtime]2:1.7-52 ii eclipse-platform 3.8.1-6 ii junit 3.8.2-8 ii junit4 4.11-3 ii libhamcrest-java 1.3-5 ii openjdk-7-jre [java6-runtime] 7u65-2.5.2-3 Versions of packages eclipse-jdt recommends: ii default-jdk 2:1.7-52 eclipse-jdt suggests no packages. -- no debconf information ---End Message--- ---BeginMessage--- Source:
Bug#770457: marked as done (eclipse-rcp: debian/rules build-arch does not install some files in eclipse-rcp)
Your message dated Fri, 28 Nov 2014 21:22:14 + with message-id e1xuszw-0001kg...@franck.debian.org and subject line Bug#770457: fixed in eclipse 3.8.1-7 has caused the Debian Bug report #770457, regarding eclipse-rcp: debian/rules build-arch does not install some files in eclipse-rcp 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.) -- 770457: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=770457 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: eclipse-rcp Version: 3.8.1-5.1 Severity: serious Justification: Policy 4.9 Control: block 769248 by -1 Hi, When building eclipse using dpkg-buildpackage -B, some files in the eclipse-rcp package are not installed. You can see this by comparing the list of files installed on amd64 vs i386: https://packages.debian.org/jessie/amd64/eclipse-rcp/filelist https://packages.debian.org/jessie/i386/eclipse-rcp/filelist Specifically the lack of /usr/share/java/org.eclipse.jface.jar on i386 causes androidsdk-tools to FTBFS. Looking at debian/rules, the org.eclipse.jface part near the bottom needs to be moved from the arch-independent section to the arch-dependent section. Thanks, James -- System Information: Debian Release: jessie/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.16.0-4-amd64 (SMP w/4 CPU cores) Locale: LANG=en_GB.utf8, LC_CTYPE=en_GB.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash ---End Message--- ---BeginMessage--- Source: eclipse Source-Version: 3.8.1-7 We believe that the bug you reported is fixed in the latest version of eclipse, 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 770...@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 eclipse 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: Mon, 24 Nov 2014 02:31:41 +0100 Source: eclipse Binary: eclipse eclipse-jdt eclipse-pde eclipse-platform eclipse-platform-data eclipse-rcp libequinox-osgi-java Architecture: source all amd64 Version: 3.8.1-7 Distribution: unstable Urgency: medium Maintainer: Debian Orbital Alignment Team pkg-java-maintain...@lists.alioth.debian.org Changed-By: Markus Koschany a...@gambaru.de Description: eclipse- Extensible Tool Platform and Java IDE eclipse-jdt - Eclipse Java Development Tools (JDT) eclipse-pde - Eclipse Plug-in Development Environment (PDE) eclipse-platform - Eclipse platform without development plug-ins eclipse-platform-data - Eclipse platform without development plug-ins (data) eclipse-rcp - Eclipse Rich Client Platform (RCP) libequinox-osgi-java - Equinox OSGi framework Closes: 763994 770457 Changes: eclipse (3.8.1-7) unstable; urgency=medium . * Team upload. * Install all arch-dependent files into eclipse-rcp correctly by renaming override_dh_install to override_dh_install-arch. Fix wrong override for dh_install-indep and move jh_classpath commands to the appropriate override target. (Closes: #770457, #763994) Checksums-Sha1: 3e1955ed0cd034d16249cf6bc49ac028f31792b0 3086 eclipse_3.8.1-7.dsc d9a1b11eb40cf7a8aa440eacd9dcea7e3be3c24d 100224 eclipse_3.8.1-7.debian.tar.xz 3f56d178ee061b207250eb77bdcf0fecbfdf26d7 54626 eclipse_3.8.1-7_all.deb 5edfab783784410ca1ff6e335cd2502ba36a274e 20711638 eclipse-jdt_3.8.1-7_all.deb cce2cd83dba409ce613de1ffe1e5366fc32f5216 65457168 eclipse-pde_3.8.1-7_amd64.deb 80a9d3aaa20799b53469491f8a7f38cc0696c065 148220 eclipse-platform_3.8.1-7_amd64.deb 5a0ab980c934f9f4139a0b2032a316413086c850 33397844 eclipse-platform-data_3.8.1-7_all.deb 44ba3cd399453ec7be223c749ddc97fe7186c263 7038904 eclipse-rcp_3.8.1-7_amd64.deb c1b0d08d6720cfb7abc31a84feb5ac569419cb01 1368978 libequinox-osgi-java_3.8.1-7_all.deb Checksums-Sha256: 5c4f094e0edec99af324eef1012bea4b59eb41c89eedc3f1a5144f3f1357a439 3086 eclipse_3.8.1-7.dsc e12edb68e1e49f08067f217e7af2a093881708753caae5ca8b4b4ed14acaa58e 100224 eclipse_3.8.1-7.debian.tar.xz 6fed5272d23f505499cf78af49c975e163a6d27ce16b9d92c8f2b6e3b1c1f6fe 54626
Bug#769248: marked as done (androidsdk-tools: FTBFS in jessie/i386: sdkstats/src/main/java/com/android/sdkstats/DdmsPreferenceStore.java:22: error: package org.eclipse.jface.preference does not exist)
Your message dated Fri, 28 Nov 2014 21:22:14 + with message-id e1xuszw-0001kg...@franck.debian.org and subject line Bug#770457: fixed in eclipse 3.8.1-7 has caused the Debian Bug report #770457, regarding androidsdk-tools: FTBFS in jessie/i386: sdkstats/src/main/java/com/android/sdkstats/DdmsPreferenceStore.java:22: error: package org.eclipse.jface.preference does not exist 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.) -- 770457: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=770457 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Source: androidsdk-tools Version: 22.2+git20130830~92d25d6-1 Severity: serious Tags: jessie sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20141112 qa-ftbfs Justification: FTBFS in jessie on i386 Hi, During a rebuild of all packages in jessie (in a jessie chroot, not a sid chroot), your package failed to build on i386. Relevant part (hopefully): debian/rules build test -x debian/rules mkdir -p . jh_linkjars jh_build -J find common/src -name *.java -and -type f -print0 | xargs -0 /usr/lib/jvm/default-java/bin/javac -g -cp androidsdk-common.jar:androidsdk-ddmlib.jar:androidsdk-ddmuilib.jar:androidsdk-sdkstats.jar:androidsdk-swtmenubar.jar:androidsdk-hierarchyviewerlib.jar:/usr/share/java/swt.jar:/usr/share/java/jfreechart.jar:/usr/share/java/jfreechart-swt.jar:/usr/share/java/org.eclipse.jface.jar:/usr/share/java/org.eclipse.core.commands.jar:/usr/share/java/org.eclipse.equinox.common.jar:/usr/share/java/guava.jar:/usr/share/java/kxml2.jar:debian/_jh_build.androidsdk-common -d debian/_jh_build.androidsdk-common -source 1.5 -target 1.5 warning: [options] bootstrap class path not set in conjunction with -source 1.5 1 warning find common/src -name *.java -and -type f -print0 | xargs -0 /usr/lib/jvm/default-java/bin/javadoc -classpath androidsdk-common.jar:androidsdk-ddmlib.jar:androidsdk-ddmuilib.jar:androidsdk-sdkstats.jar:androidsdk-swtmenubar.jar:androidsdk-hierarchyviewerlib.jar:/usr/share/java/swt.jar:/usr/share/java/jfreechart.jar:/usr/share/java/jfreechart-swt.jar:/usr/share/java/org.eclipse.jface.jar:/usr/share/java/org.eclipse.core.commands.jar:/usr/share/java/org.eclipse.equinox.common.jar:/usr/share/java/guava.jar:/usr/share/java/kxml2.jar:debian/_jh_build.androidsdk-common -d debian/_jh_build.javadoc/api -quiet -source 1.5 Creating destination directory: debian/_jh_build.javadoc/api/ warning: [options] bootstrap class path not set in conjunction with -source 1.5 1 warning /usr/lib/jvm/default-java/bin/jar cfm /«BUILDDIR»/androidsdk-tools-22.2+git20130830~92d25d6/androidsdk-common.jar ../_jh_manifest.androidsdk-common com find sdklib/src -name *.java -and -type f -print0 | xargs -0 /usr/lib/jvm/default-java/bin/javac -g -cp androidsdk-common.jar:androidsdk-ddmlib.jar:androidsdk-ddmuilib.jar:androidsdk-sdkstats.jar:androidsdk-swtmenubar.jar:androidsdk-hierarchyviewerlib.jar:/usr/share/java/swt.jar:/usr/share/java/jfreechart.jar:/usr/share/java/jfreechart-swt.jar:/usr/share/java/org.eclipse.jface.jar:/usr/share/java/org.eclipse.core.commands.jar:/usr/share/java/org.eclipse.equinox.common.jar:/usr/share/java/guava.jar:/usr/share/java/kxml2.jar:debian/_jh_build.androidsdk-sdklib -d debian/_jh_build.androidsdk-sdklib -source 1.5 -target 1.5 warning: [options] bootstrap class path not set in conjunction with -source 1.5 1 warning find sdklib/src -name *.java -and -type f -print0 | xargs -0 /usr/lib/jvm/default-java/bin/javadoc -classpath androidsdk-common.jar:androidsdk-ddmlib.jar:androidsdk-ddmuilib.jar:androidsdk-sdkstats.jar:androidsdk-swtmenubar.jar:androidsdk-hierarchyviewerlib.jar:/usr/share/java/swt.jar:/usr/share/java/jfreechart.jar:/usr/share/java/jfreechart-swt.jar:/usr/share/java/org.eclipse.jface.jar:/usr/share/java/org.eclipse.core.commands.jar:/usr/share/java/org.eclipse.equinox.common.jar:/usr/share/java/guava.jar:/usr/share/java/kxml2.jar:debian/_jh_build.androidsdk-sdklib -d debian/_jh_build.javadoc/api -quiet -source 1.5 warning: [options] bootstrap class path not set in conjunction with -source 1.5 sdklib/src/main/java/com/android/sdklib/util/CommandLineParser.java:455: warning - Tag @link: reference not found: Arg sdklib/src/main/java/com/android/sdklib/util/CommandLineParser.java:470: warning - Tag @link: reference not found: Arg sdklib/src/main/java/com/android/sdklib/util/CommandLineParser.java:455: warning - Tag @link: reference not found: Arg sdklib/src/main/java/com/android/sdklib/util/CommandLineParser.java:455: warning - Tag @link: reference not
Bug#771177: NMU submitted to the delayed/5 queue
Le 2014-11-28 11:47, Francois Marier a écrit : I've taken the liberty to fix this via an NMU in the delayed/5days queue. I've taken the liberty to cancel it. Can you please test Matt's patch? -- Mehdi -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: your mail
Processing commands for cont...@bugs.debian.org: severity 769830 normal Bug #769830 [src:subsurface] [subsurface] Some sources are not included in your package Severity set to 'normal' from 'serious' thanks Stopping processing here. Please contact me if you need assistance. -- 769830: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=769830 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: tagging 727149
Processing commands for cont...@bugs.debian.org: tags 727149 - moreinfo Bug #727149 [src:linux] linux-image-3.10-3-amd64: Network adapter (Intel 82579V) hangs during TX, causing reset and undetected data corruption at the other side Removed tag(s) moreinfo. thanks Stopping processing here. Please contact me if you need assistance. -- 727149: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=727149 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: Bug#771254: systemd-journald cannot be restarted safely
Processing commands for cont...@bugs.debian.org: severity 771254 normal Bug #771254 [needrestart] systemd-journald cannot be restarted safely Severity set to 'normal' from 'important' affects 771122 needrestart Bug #771122 [systemd] restarting the journal breaks other services Added indication that 771122 affects needrestart thanks Stopping processing here. Please contact me if you need assistance. -- 771122: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=771122 771254: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=771254 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: tagging 770242
Processing commands for cont...@bugs.debian.org: tags 770242 + patch Bug #770242 [rkhunter] rkhunter: upgrade/post-install errors Added tag(s) patch. thanks Stopping processing here. Please contact me if you need assistance. -- 770242: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=770242 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: tagging 766462
Processing commands for cont...@bugs.debian.org: tags 766462 - moreinfo Bug #766462 [plymouth] with plymouth installed, I don't get any gettys on my VCs Removed tag(s) moreinfo. thanks Stopping processing here. Please contact me if you need assistance. -- 766462: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=766462 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: tagging 766462
Processing commands for cont...@bugs.debian.org: tags 766462 - unreproducible Bug #766462 [plymouth] with plymouth installed, I don't get any gettys on my VCs Removed tag(s) unreproducible. thanks Stopping processing here. Please contact me if you need assistance. -- 766462: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=766462 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: retitle 766462 to with plymouth installed, and both GDM and KDM enabled, I don't get any gettys on my VCs
Processing commands for cont...@bugs.debian.org: retitle 766462 with plymouth installed, and both GDM and KDM enabled, I don't get any gettys on my VCs Bug #766462 [plymouth] with plymouth installed, I don't get any gettys on my VCs Changed Bug title to 'with plymouth installed, and both GDM and KDM enabled, I don't get any gettys on my VCs' from 'with plymouth installed, I don't get any gettys on my VCs' thanks Stopping processing here. Please contact me if you need assistance. -- 766462: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=766462 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: tagging 761170
Processing commands for cont...@bugs.debian.org: tags 761170 + upstream Bug #761170 [src:libgit2] libgit2: FTBFS on multiple architectures Bug #761539 [src:libgit2] libgit2: FTBFS: Tests failures Added tag(s) upstream. Added tag(s) upstream. thanks Stopping processing here. Please contact me if you need assistance. -- 761170: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=761170 761539: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=761539 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#727800: upgrade failure
We need to contact upstream to see if we can solve this somehow or add this bug to the release notes. Not shipping akonadi is a non-go. -- Lisandro Damián Nicanor Pérez Meyer http://perezmeyer.com.ar/ http://perezmeyer.blogspot.com/ signature.asc Description: This is a digitally signed message part.
Bug#769947: mate-terminal: Segfaults after update
Package: mate-terminal Version: 1.8.1+dfsg1-2 Followup-For: Bug #769947 Hi Mike I built the package using the provided debian source and applying the patch referenced above in terminal.c and i can confirm that i dont get the error on trying to start a mate terminal. Ben -- System Information: Debian Release: jessie/sid APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.16.0-4-amd64 (SMP w/4 CPU cores) Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8) (ignored: LC_ALL set to en_GB.UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages mate-terminal depends on: ii libatk1.0-0 2.14.0-1 ii libc6 2.19-13 ii libcairo2 1.14.0-2.1 ii libdconf1 0.22.0-1 ii libfontconfig12.11.0-6.3 ii libfreetype6 2.5.2-2 ii libgdk-pixbuf2.0-02.31.1-2+b1 ii libglib2.0-0 2.42.1-1 ii libgtk2.0-0 2.24.25-1 ii libice6 2:1.0.9-1 ii libpango-1.0-01.36.8-3 ii libpangocairo-1.0-0 1.36.8-3 ii libpangoft2-1.0-0 1.36.8-3 ii libsm62:1.2.2-1 ii libvte9 1:0.28.2-5 ii libx11-6 2:1.6.2-3 ii libxext6 2:1.3.3-1 ii mate-desktop-common 1.8.1+dfsg1-2 ii mate-terminal-common 1.8.1+dfsg1-2 pn python:anynone mate-terminal recommends no packages. mate-terminal suggests no packages. -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#771348: needrestart: starts not running services
severity 771348 normal
tags 771348 - security
thanks
On 11/28/2014 07:06 PM, Christoph Anton Mitterer wrote:
Since this may start services which are only to be run under specific
situations, e.g. when only in a secure network, or when VPN is running
because they may grant system access e.g. without authentication...
(take ssh which can be configured to allow password less access to root)
I'm marking this severity=critical and tags=security.
needrestart does not automaticly restart any services by default. I
don't see any security issues if the user selects to restart a service
(although the service was not running before). Sorry, but your example
sounds hypothetical to me.
You could add a entry to override_rc to prevent ssh to be restarted
accidentally.
HTH,
Thomas
Maybe the whole things applies to non-SSH as well, since a while I'm always
seeing two entries for GDM, one gdm3.service and gdm3 alone.
-- Package-specific info:
needrestart output:
Running kernel seems to be up-to-date.
Services to be restarted:
service dbus restart
-- System Information:
Debian Release: jessie/sid
APT prefers unstable
APT policy: (500, 'unstable')
Architecture: amd64 (x86_64)
Kernel: Linux 3.16.0-4-amd64 (SMP w/8 CPU cores)
Locale: LANG=en_DE.utf8, LC_CTYPE=en_DE.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Versions of packages needrestart depends on:
ii dpkg 1.17.22
ii libmodule-find-perl0.12-1
ii libmodule-scandeps-perl1.16-1
ii libproc-processtable-perl 0.51-1
ii libsort-naturally-perl 1.03-1
ii libterm-readkey-perl 2.32-1+b1
ii perl 5.20.1-3
needrestart recommends no packages.
needrestart suggests no packages.
-- Configuration Files:
/etc/needrestart/needrestart.conf changed:
$nrconf{defno} = 1;
$nrconf{blacklist} = [
# ignore sudo (not a daemon)
q(^/usr/bin/sudo(\.dpkg-new)?$),
# ignore DHCP clients
q(^/sbin/(dhclient|dhcpcd5|pump|udhcpc)(\.dpkg-new)?$),
];
$nrconf{override_rc} = {
# DBus
q(^dbus) = 0,
# display managers
q(^gdm) = 0,
q(^kdm) = 0,
q(^nodm) = 0,
q(^wdm) = 0,
q(^xdm) = 0,
q(^lightdm) = 0,
# networking stuff
q(^network-manager) = 0,
q(^NetworkManager) = 0,
q(^openvpn) = 0,
q(^quagga) = 0,
q(^tinc) = 0,
# gettys
q(^getty@.+\.service) = 0,
# misc
q(^zfs-fuse) = 0,
q(^mythtv-backend) = 0,
};
if(-d q(/etc/needrestart/conf.d)) {
foreach my $fn (sort /etc/needrestart/conf.d/*.conf) {
print STDERR $LOGPREF eval $fn\n if($nrconf{verbose});
eval do { local(@ARGV, $/) = $fn; };
die Error parsing $fn: $@ if($@);
}
}
-- no debconf information
--
:: WWW: http://fiasko-nw.net/~thomas/ ::
::: Jabber: xmpp:tho...@jabber.fiasko-nw.net :::
:: flickr: http://www.flickr.com/photos/laugufe/ ::
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#767857: marked as done (kernel-common: postinst uses /usr/share/doc content (Policy 12.3): /usr/share/doc/kernel-common/examples/etc/sample.kernel-img.conf)
Your message dated Fri, 28 Nov 2014 22:33:55 + with message-id e1xuu6t-0003oa...@franck.debian.org and subject line Bug#767857: fixed in kernel-package 13.014+nmu1 has caused the Debian Bug report #767857, regarding kernel-common: postinst uses /usr/share/doc content (Policy 12.3): /usr/share/doc/kernel-common/examples/etc/sample.kernel-img.conf 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.) -- 767857: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=767857 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: kernel-common Version: 13.014 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, a test with piuparts revealed that your package uses files from /usr/share/doc in its maintainer scripts which is a violation of Policy 12.3: Packages must not require the existence of any files in /usr/share/doc/ in order to function. http://www.debian.org/doc/debian-policy/ch-docs.html#s12.3 These files must be moved to /usr/share/$PACKAGE and may be symlinked from /usr/share/doc/$PACKAGE. This piuparts test prevents the installation of (most) files into /usr/share/doc with 'dpkg --path-exclude=...'. From the attached log (scroll to the bottom...): Selecting previously unselected package kernel-common. (Reading database ... 8631 files and directories currently installed.) Preparing to unpack .../kernel-common_13.014_all.deb ... Unpacking kernel-common (13.014) ... Setting up kernel-common (13.014) ... cp: cannot stat '/usr/share/doc/kernel-common/examples/etc/sample.kernel-img.conf': No such file or directory dpkg: error processing package kernel-common (--configure): subprocess installed post-installation script returned error exit status 1 Errors were encountered while processing: kernel-common Cheers, Andreas kernel-common_13.014.log.gz Description: application/gzip ---End Message--- ---BeginMessage--- Source: kernel-package Source-Version: 13.014+nmu1 We believe that the bug you reported is fixed in the latest version of kernel-package, 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 767...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Jonathan Wiltshire j...@debian.org (supplier of updated kernel-package 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: Wed, 26 Nov 2014 21:56:16 + Source: kernel-package Binary: kernel-package kernel-common Architecture: source all Version: 13.014+nmu1 Distribution: unstable Urgency: medium Maintainer: Manoj Srivastava sriva...@debian.org Changed-By: Jonathan Wiltshire j...@debian.org Description: kernel-common - common elements for generated kernel packages kernel-package - utility for building Linux kernel related Debian packages Closes: 767857 Changes: kernel-package (13.014+nmu1) unstable; urgency=medium . * Non-maintainer upload. * Move examples to /usr/share/kernel-common and symlink from /u/s/d (Closes: #767857) Checksums-Sha1: 3d8afc7a62d3d4b591028a09acbf255d46c7abe3 1702 kernel-package_13.014+nmu1.dsc 7dcb687e7f15449406a43532a1ec23a66a3104ae 319188 kernel-package_13.014+nmu1.tar.xz 59b26aaeb4b843ceb506ae965aac97e4305b443d 349634 kernel-package_13.014+nmu1_all.deb ef852c20d9bdf6af1182f0db4c418f2c34007660 131830 kernel-common_13.014+nmu1_all.deb Checksums-Sha256: caf6294565a72d3638841488c2a0ff2642c807ef0e9932f42d29b7f5ed2813ec 1702 kernel-package_13.014+nmu1.dsc 2cb6cc0b76d3f919d6a29a50571e6b09e0d2e52122b2ce49432e8f811b6535f9 319188 kernel-package_13.014+nmu1.tar.xz 02a25801debeb737cfd87498cb9c4dd06817ec90bffe74c1fab9e9e98c30a68d 349634 kernel-package_13.014+nmu1_all.deb 9557f6bac954e1b3588488d977ca1940bbe0e0fcbd057965353a4d8e8fa65e60 131830 kernel-common_13.014+nmu1_all.deb Files: 4edfd063cbc8d186606c7ac92cfac74e 1702 kernel optional kernel-package_13.014+nmu1.dsc cdf51e865634377d7233f13c3ebd1864 319188 kernel optional kernel-package_13.014+nmu1.tar.xz f054d9dcc73d35d8898dcdac011ae764 349634 kernel optional kernel-package_13.014+nmu1_all.deb 098aa8248ce88e29c1a84c0241207c59 131830 kernel optional kernel-common_13.014+nmu1_all.deb -BEGIN PGP
Bug#727800: Upstream contacted
I just emailed upstream asking for advice. There is a simple work-around, just restart akonadi. Either by using akonadictl restart or log out and back in. Diane -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#562907: missing dependency on pybluez
I think it's probably to mark this as won't fix since the project is no longer being maintained. The package is already marked to be removed from testing but I think it's better state this explicitly over keeping the bug alive. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#771113: marked as done (lintian: FTBFS on i386: binaries-from-other-arch FAILED)
Your message dated Fri, 28 Nov 2014 23:03:56 + with message-id e1xuuzw-0007pv...@franck.debian.org and subject line Bug#771113: fixed in lintian 2.5.30+deb8u3 has caused the Debian Bug report #771113, regarding lintian: FTBFS on i386: binaries-from-other-arch 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.) -- 771113: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=771113 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Source: lintian Version: 2.5.30+deb8u2 Severity: serious Justification: fails to build from source Lintian FTBFS in i386 jessie chroot: | Running binaries-from-other-arch 1.0... building... testing... FAILED | --- t/tests/binaries-from-other-arch/tags 2014-10-13 20:45:41.0 + | +++ /build/lintian-YbPqW5/lintian-2.5.30+deb8u2/debian/test-out/tests/binaries-from-other-arch/tags.binaries-from-other-arch 2014-11-26 20:37:07.731101742 + | @@ -1,4 +1,3 @@ | -E: binaries-from-other-arch: binary-from-other-architecture usr/bin/elfobject | E: binaries-from-other-arch: statically-linked-binary usr/bin/elfobject | W: binaries-from-other-arch: apparently-corrupted-elf-binary usr/bin/elfobject | W: binaries-from-other-arch: binary-without-manpage usr/bin/elfobject I believe the culprit is this part of t/tests/binaries-from-other-arch/debian/debian/dumpobj: | case $DEB_BUILD_GNU_TYPE in | i486-linux-gnu|i686-linux-gnu|x86_64-linux-gnu) The GNU triplet for i386 is i586-linux-gnu these days. -- Jakub Wilk ---End Message--- ---BeginMessage--- Source: lintian Source-Version: 2.5.30+deb8u3 We believe that the bug you reported is fixed in the latest version of lintian, 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 771...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Niels Thykier ni...@thykier.net (supplier of updated lintian 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: Fri, 28 Nov 2014 23:21:07 +0100 Source: lintian Binary: lintian Architecture: source all Version: 2.5.30+deb8u3 Distribution: unstable Urgency: medium Maintainer: Debian Lintian Maintainers lintian-ma...@debian.org Changed-By: Niels Thykier ni...@thykier.net Description: lintian- Debian package checker Closes: 771054 771113 Changes: lintian (2.5.30+deb8u3) unstable; urgency=medium . * helpers/coll/objdump-info-helper: + [NT] Apply patch from Matt Kraai that adjusts the regex used for parsing readelf output. Thanks to Martin Pitt for reporting the issues. (Closes: #771054) . * t: + [NT] Apply patch from Matt Kraai to fix test case on i386. (Closes: #771113) Checksums-Sha1: 7c32150cba5ea0081b9f06705a222a4606675985 2759 lintian_2.5.30+deb8u3.dsc 3af15c74453b69440922bc7e2c56d09e129aa1ad 1202176 lintian_2.5.30+deb8u3.tar.xz 914d09bdcaf5d3fb971947c4af0defe9a72abf49 792508 lintian_2.5.30+deb8u3_all.deb Checksums-Sha256: c4f3234dbb812af0d63673627026a8e30f626253feff0ea5cfbf48e6c1f0ef08 2759 lintian_2.5.30+deb8u3.dsc 18c408825484d7cd47e7d44a486300ccdc64229ca7501883ffc44a29d501a65d 1202176 lintian_2.5.30+deb8u3.tar.xz 50e1ffa9dcb46040e7bef89d032f1b9b4c77f2371221f200dcf966bf19942334 792508 lintian_2.5.30+deb8u3_all.deb Files: 8d2fdf7bf6b03c292ac85a5f17b487ef 2759 devel optional lintian_2.5.30+deb8u3.dsc 939e36f2905f37c5ce75195efa0d41f4 1202176 devel optional lintian_2.5.30+deb8u3.tar.xz 7cb3de792fb5bd16eab9e83ae2e9568a 792508 devel optional lintian_2.5.30+deb8u3_all.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1 iQIcBAEBCAAGBQJUePz6AAoJEAVLu599gGRCVYoP/1sjQO6Ug6+hCIEOPK0ODuJz b11q7uipa2qbToZOAGxVb66rf0UqnkqfYhLLYxe5+1c46/aB41kc42f+yZLMpjaK nWJ5M62QSQ0fYKGdiirVHHoEH5sa8Ifo0ybWu6b+W8EpD1jRYfTd/3qEoixrXMh/ y9SBevrYKIvoBNFeOwZU4u6fJFR6T/JFToi2bOfnTOHLjOTRUilK+9CY+Tgp8ggo QtVj48FkktJ7+ZqCB0JEaVGyR+FwqvfFD5HzPdD4OcYOiHCPsqxPTlYjcdVm/6rI wGh33mQXDmhVga5RCRANFIhTdY7aodwuF1byL2O0EylaKtdhKGAegy/HF/9UtFxN Ljk6BTFdjV/1Ym/kfixgd61anXl7OPbtwLaf4kVuwaauDP5oKeYAsUiPCdOOdtDh i12LJ6mf6+6Fz0vSgup6c5OFJliE8V06KUan69EuB1GR8MkC+5FDzLNgX70fNKHK 5PoEk4IRiHeUVMzjpcjIfGWK4GDTEiiymvoJ8PSMt4KKNF9hNf2q9AjHw0wFWIVJ
Bug#771054: marked as done (lintian: FTBFS: binaries-from-other-arch fails with latest binutils)
Your message dated Fri, 28 Nov 2014 23:03:56 + with message-id e1xuuzw-0007pp...@franck.debian.org and subject line Bug#771054: fixed in lintian 2.5.30+deb8u3 has caused the Debian Bug report #771054, regarding lintian: FTBFS: binaries-from-other-arch fails with latest binutils 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.) -- 771054: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=771054 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: lintian Severity: serious Justification: FTBFS Version: 2.5.30+deb8u2 Hello, With the recent binutils 2.24.90.20141124-1, one lintian test started failing: | Running binaries-from-other-arch 1.0... building... testing... FAILED | --- t/tests/binaries-from-other-arch/tags 2014-10-13 22:45:41.0 +0200 | +++ /«BUILDDIR»/lintian-2.5.30+deb8u2/debian/test-out/tests/binaries-from-other-arch/tags.binaries-from-other-arch 2014-11-26 12:15:08.758293112 +0100 | @@ -1,4 +1,3 @@ | E: binaries-from-other-arch: binary-from-other-architecture usr/bin/elfobject | E: binaries-from-other-arch: statically-linked-binary usr/bin/elfobject | -W: binaries-from-other-arch: apparently-corrupted-elf-binary usr/bin/elfobject | W: binaries-from-other-arch: binary-without-manpage usr/bin/elfobject This happens both during packge build (hence the RC level) and also during the autopkgtest. I confirm that the test works with binutils 2.24.90.2014 still. This might very well be a regression in binutils itself, or lintian's invocation of it needs to be adjusted, so please reassign if appropriate. I attach the complete build log for reference (but the above is the essential bit from it). Thanks for considering, Martin -- Martin Pitt| http://www.piware.de Ubuntu Developer (www.ubuntu.com) | Debian Developer (www.debian.org) lintian_2.5.30+deb8u2_amd64-20141126-1211.build.xz Description: Binary data signature.asc Description: Digital signature ---End Message--- ---BeginMessage--- Source: lintian Source-Version: 2.5.30+deb8u3 We believe that the bug you reported is fixed in the latest version of lintian, 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 771...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Niels Thykier ni...@thykier.net (supplier of updated lintian 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: Fri, 28 Nov 2014 23:21:07 +0100 Source: lintian Binary: lintian Architecture: source all Version: 2.5.30+deb8u3 Distribution: unstable Urgency: medium Maintainer: Debian Lintian Maintainers lintian-ma...@debian.org Changed-By: Niels Thykier ni...@thykier.net Description: lintian- Debian package checker Closes: 771054 771113 Changes: lintian (2.5.30+deb8u3) unstable; urgency=medium . * helpers/coll/objdump-info-helper: + [NT] Apply patch from Matt Kraai that adjusts the regex used for parsing readelf output. Thanks to Martin Pitt for reporting the issues. (Closes: #771054) . * t: + [NT] Apply patch from Matt Kraai to fix test case on i386. (Closes: #771113) Checksums-Sha1: 7c32150cba5ea0081b9f06705a222a4606675985 2759 lintian_2.5.30+deb8u3.dsc 3af15c74453b69440922bc7e2c56d09e129aa1ad 1202176 lintian_2.5.30+deb8u3.tar.xz 914d09bdcaf5d3fb971947c4af0defe9a72abf49 792508 lintian_2.5.30+deb8u3_all.deb Checksums-Sha256: c4f3234dbb812af0d63673627026a8e30f626253feff0ea5cfbf48e6c1f0ef08 2759 lintian_2.5.30+deb8u3.dsc 18c408825484d7cd47e7d44a486300ccdc64229ca7501883ffc44a29d501a65d 1202176 lintian_2.5.30+deb8u3.tar.xz 50e1ffa9dcb46040e7bef89d032f1b9b4c77f2371221f200dcf966bf19942334 792508 lintian_2.5.30+deb8u3_all.deb Files: 8d2fdf7bf6b03c292ac85a5f17b487ef 2759 devel optional lintian_2.5.30+deb8u3.dsc 939e36f2905f37c5ce75195efa0d41f4 1202176 devel optional lintian_2.5.30+deb8u3.tar.xz 7cb3de792fb5bd16eab9e83ae2e9568a 792508 devel optional lintian_2.5.30+deb8u3_all.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1 iQIcBAEBCAAGBQJUePz6AAoJEAVLu599gGRCVYoP/1sjQO6Ug6+hCIEOPK0ODuJz b11q7uipa2qbToZOAGxVb66rf0UqnkqfYhLLYxe5+1c46/aB41kc42f+yZLMpjaK
Bug#770982: Patch
Control: tags -1 + patch
Hi,
Here's a patch, partially extracted from upstream, that includes
dynctrl-logitech.h in libwebcam0-dev:
diff -Nru libwebcam-0.2.4/debian/libwebcam0-dev.install
libwebcam-0.2.4/debian/libwebcam0-dev.install
--- libwebcam-0.2.4/debian/libwebcam0-dev.install 2013-11-01
16:49:24.0 -0700
+++ libwebcam-0.2.4/debian/libwebcam0-dev.install 2014-11-28
15:32:56.0 -0800
@@ -1,3 +1,4 @@
+usr/include/dynctrl-logitech.h
usr/include/webcam.h
usr/lib/libwebcam.a
usr/lib/libwebcam.so
diff -Nru libwebcam-0.2.4/debian/patches/install-dynctrl-logitech.h
libwebcam-0.2.4/debian/patches/install-dynctrl-logitech.h
--- libwebcam-0.2.4/debian/patches/install-dynctrl-logitech.h 1969-12-31
16:00:00.0 -0800
+++ libwebcam-0.2.4/debian/patches/install-dynctrl-logitech.h 2014-11-28
15:29:48.0 -0800
@@ -0,0 +1,13 @@
+Index: libwebcam-0.2.4/libwebcam/CMakeLists.txt
+===
+--- libwebcam-0.2.4.orig/libwebcam/CMakeLists.txt 2013-10-31
14:47:36.0 -0700
libwebcam-0.2.4/libwebcam/CMakeLists.txt 2014-11-28 15:29:32.063070089
-0800
+@@ -103,7 +103,7 @@
+ )
+
+ install (
+- FILES ../common/include/webcam.h
++ FILES ../common/include/webcam.h ../common/include/dynctrl-logitech.h
+ DESTINATION ${CMAKE_INSTALL_PREFIX}/include
+ )
+
diff -Nru libwebcam-0.2.4/debian/patches/series
libwebcam-0.2.4/debian/patches/series
--- libwebcam-0.2.4/debian/patches/series 2013-11-01 16:49:24.0
-0700
+++ libwebcam-0.2.4/debian/patches/series 2014-11-28 15:29:13.0
-0800
@@ -0,0 +1 @@
+install-dynctrl-logitech.h
Would you like me to sponsor an upload containing it (or something
like it)?
--
Matt
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: Patch
Processing control commands: tags -1 + patch Bug #770982 [libwebcam0-dev] libwebcam0-dev: dynctrl-logitech.h is missing in libwebcam0-dev Added tag(s) patch. -- 770982: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=770982 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 package to needrestart, severity of 771348 is normal
Processing commands for cont...@bugs.debian.org: limit package needrestart Limiting to bugs with field 'package' containing at least one of 'needrestart' Limit currently set to 'package':'needrestart' severity 771348 normal Bug #771348 [needrestart] needrestart: starts not running services Severity set to 'normal' from 'critical' thanks Stopping processing here. Please contact me if you need assistance. -- 771348: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=771348 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#771387: siliconmotion graphic card driver segfault and unusable.
Package: xserver-xorg-video-siliconmotion Source: xserver-xorg-video-siliconmotion (1:1.7.7-2) Version: 1:1.7.7-2+b2 Severity: serious Tags: moreinfo Hi, The xserver-xorg-video-siliconmotion segfaults right away once I started X, and then the X is totally unuseable on my machine (mipsel, loongson-2f). ``` (==) Log file: /var/log/Xorg.0.log, Time: Sat Nov 29 11:07:18 2014 (==) Using config file: /etc/X11/xorg.conf (==) Using system config directory /usr/share/X11/xorg.conf.d (EE) (EE) Backtrace: (EE) 0: X (xorg_backtrace+0x84) [0x77e2ede4] (EE) (EE) Segmentation fault at address 0x3c4 (EE) Fatal server error: (EE) Caught signal 11 (Segmentation fault). Server aborting (EE) (EE) ``` I have read http://x.debian.net/howto/use-gdb.html and http://x.debian.net/howto/report-bugs.html but I feel hard to generate coredump/backtrace, as I'm not familiar with gdb. This issue also affects debian wheezy (even the save segfault addr). And another useful information is, someone fixed this problem and put that fixed version (1.7.6-1loongson) onto a forum, it works indeed. I can send that fix privately.[1] And then, what moreinfo should I exactly offer? P.S. the /var/log/Xorg.0.log seems doesn't help, so not attached. thanks:) [1] I tried to apply that fix for jessie, but ABI's not happy. -- Regards, C.D.Luminate -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#771387: siliconmotion graphic card driver segfault and unusable.
reassign 771387 xserver-xorg-video-siliconmotion found 771387 1:1.7.7-2+b2 forcemerge 594684 771387 thanks Hello, lumin wrote: The xserver-xorg-video-siliconmotion segfaults right away once I started X, and then the X is totally unuseable on my machine (mipsel, loongson-2f). This is https://bugs.debian.org/594684 Regards, -- Steven Chamberlain ste...@pyro.eu.org -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#771334: upgrade hosed dovecot; Couldn't parse private ssl_key: error:0906D06C:PEM routines:PEM_read_bio:no start line: Expecting: ANY PRIVATE KEY
On Fri, 28 Nov 2014, Joey Hess wrote: After upgrading to this version, I cannot connect to dovecot's imap or pop servers. The only substantive change in -7 was to comment out the ssl_cert and ssl_key entries in /etc/dovecot/conf.d/10-ssl.conf. This is so people who do not have certificates set up (e.g. in new installs) don't run into this problem. But you are upgrading from an existing working setup right? In that case dpkg should have warned you that you are upgrading a conffile. Did that not happen? Actually I just looked and it seems the configuration files are not getting marked as conffiles even though we are handling them with ucfr. Let me investigate why this is happening. -- Jaldhar H. Vyas jald...@debian.org -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#770425: Possibility of update to 4.x
Hi Nick, The security update will only be 3.6.1 with the 4.7.4-4.7.5 patches. It's difficult balancing act really but the whole purpose of the security updates is just to update for security. It's not ideal for certain situations. The proposed update went to the security team a few minutes ago and should mean an update for wordpress in wheezy will be out today. - Craig -- Craig Small (@smallsees) http://enc.com.au/ csmall at : enc.com.au Debian GNU/Linux http://www.debian.org/ csmall at : debian.org GPG fingerprint:5D2F B320 B825 D939 04D2 0519 3938 F96B DF50 FEA5 -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#771393: anacron.service should set IgnoreSIGPIPE=no
Package: anacron Version: 2.3-22 Severity: grave Justification: renders package unusable Dear Maintainer, anacron should set IgnoreSIGPIPE=no in it's systemd service file. cron already does this (see #756047) the compatibility generators too grep PIPE /run/systemd/generator.late/* Without this, simple shell scripts like yes | head fails. because the 'yes' process here never receive the 'broken pipe' signal; and goes on trashing the journal with I/O errors. Sorry to think of this so late in the freeze. Alexandre Detiste -- System Information: Debian Release: jessie/sid APT prefers testing APT policy: (500, 'testing'), (200, 'unstable'), (110, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.16.0-4-amd64 (SMP w/6 CPU cores) Locale: LANG=fr_BE.UTF-8, LC_CTYPE=fr_BE.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#764191: marked as done (eclipse: FTBFS on armel)
Your message dated Sat, 29 Nov 2014 08:16:44 +0100 with message-id 547972dc.3060...@gambaru.de and subject line Re: Bug#764191: eclipse: FTBFS on armel has caused the Debian Bug report #764191, regarding eclipse: FTBFS on armel 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.) -- 764191: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=764191 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Source: eclipse Version: 3.8.1-6 Severity: serious Justification: FTBFS Hello, Your package fails to build from source on Debian autobuilder network. Please check your package build logs at: https://buildd.debian.org/status/package.php?p=eclipsesuite=sid Full log: https://buildd.debian.org/status/fetch.php?pkg=eclipsearch=armelver=3.8.1-6stamp=1412464596 Best regards -- System Information: Debian Release: jessie/sid APT prefers unstable APT policy: (900, 'unstable'), (1, 'experimental') Architecture: i386 (i686) Foreign Architectures: armhf Kernel: Linux 3.14-2-686-pae (SMP w/4 CPU cores) Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash ---End Message--- ---BeginMessage--- On Mon, 24 Nov 2014 17:08:28 +0100 Markus Koschany a...@gambaru.de wrote: Control: block 764191 by 768505 On Tue, 18 Nov 2014 16:38:47 +0100 Niels Thykier ni...@thykier.net wrote: [...] FTR, I requested the removal of eclipse on armel and kfreebsd because of this (and kfreebsd using gcj, which is known not to work). This is https://bugs.debian.org/768505. As soon as it is resolved this bug can be closed. All armel binary packages have been removed and #768505 was closed. Hence I am going to close this bug report now. Regards, Markus signature.asc Description: OpenPGP digital signature ---End Message---
