Bug#760388: marked as done (pepperflashplugin-nonfree: modifies conffiles of another package (policy 10.7.3): /etc/chromium/default)
Your message dated Wed, 22 Oct 2014 07:35:21 + with message-id e1xgqs1-0001eu...@franck.debian.org and subject line Bug#760388: fixed in pepperflashplugin-nonfree 1.8 has caused the Debian Bug report #760388, regarding pepperflashplugin-nonfree: modifies conffiles of another package (policy 10.7.3): /etc/chromium/default 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.) -- 760388: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=760388 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: pepperflashplugin-nonfree Version: 1.5 Severity: serious Justification: §10.7.3: conffiles must not be modified by maintainer scripts Hi! The postinst for pepperflashplugin-nonfree runs update-pepperflashplugin-nonfree which modifies /etc/chromium/default. This file is (a) a conffile and conffiles must not be modified from maintainer scripts [§10.7.3] and (b) is a conffile owned by another package and modifying the files of another package is not permitted [§10.7.4]. As a result of modifying a conffile, the admin is also then given unnecessary prompts to deal with changes to this conffile in future package upgrades which must not happen [§10.7.3]. (This also happens with the version in wheezy-backports.) An abridged installation log is as follows: # apt-get install debsums chromium [...] # debsums -a -s # apt-get install pepperflashplugin-nonfree [...] Preparing to unpack .../pepperflashplugin-nonfree_1.5_amd64.deb ... Unpacking pepperflashplugin-nonfree (1.5) ... Setting up pepperflashplugin-nonfree (1.5) ... --2014-09-03 09:28:47-- http://dl.google.com/linux/chrome/deb/pool/main/g/google-chrome-stable/google-chrome-stable_37.0.2062.94-1_amd64.deb Resolving dl.google.com (dl.google.com)... 203.5.76.212, 203.5.76.211, 203.5.76.219, ... Connecting to dl.google.com (dl.google.com)|203.5.76.212|:80... connected. HTTP request sent, awaiting response... 200 OK Length: 49195682 (47M) [application/x-debian-package] Saving to: '/tmp/pepperflashplugin-nonfree.e2KEPs3Sun/google-chrome-stable_37.0.2062.94-1_amd64.deb' [...] 2014-09-03 09:29:01 (3.55 MB/s) - '/tmp/pepperflashplugin-nonfree.e2KEPs3Sun/google-chrome-stable_37.0.2062.94-1_amd64.deb' saved [49195682/49195682] # debsums -a -s debsums: changed file /etc/chromium/default (from chromium package) cheers Stuart ---End Message--- ---BeginMessage--- Source: pepperflashplugin-nonfree Source-Version: 1.8 We believe that the bug you reported is fixed in the latest version of pepperflashplugin-nonfree, 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 760...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Bart Martens ba...@debian.org (supplier of updated pepperflashplugin-nonfree 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, 22 Oct 2014 07:49:22 +0200 Source: pepperflashplugin-nonfree Binary: pepperflashplugin-nonfree Architecture: source amd64 Version: 1.8 Distribution: unstable Urgency: medium Maintainer: Bart Martens ba...@debian.org Changed-By: Bart Martens ba...@debian.org Description: pepperflashplugin-nonfree - Pepper Flash Player - browser plugin Closes: 760388 Changes: pepperflashplugin-nonfree (1.8) unstable; urgency=medium . * Removed support for /etc/chromium/default. Closes: #760388. + etc-chromium-default.txt: Removed. + debian/etc/chromium.d/pepperflashplugin-nonfree: Added. + debian/dirs: Added etc/chromium.d/. + debian/install: add file in etc/chromium.d/. + update-pepperflashplugin-nonfree: Removed dealing with /etc/chromium/default and /etc/chromium.d. + debian/control: Conflicts: chromium ( 37.0.2062.120-4). This package doesn't really conflict with these old versions of chromium, but it makes explicit that pepperflashplugin-nonfree isn't useful for versions of chromium still using /etc/chromium/default, as agreed on debian-release on Sun, 12 Oct 2014 15:38:03 +0200. Checksums-Sha1: 465a0d28da2d1a1e92b830ec5323d2cd338d4546 1556 pepperflashplugin-nonfree_1.8.dsc 0d577b71a201082bfdf54368186fe221461088e8 9880 pepperflashplugin-nonfree_1.8.tar.xz
Bug#766169: Same here: missing window decoration on kde
On Tuesday 21 October 2014 22:29:41 Diederik de Haas wrote:
I upgraded with aptitude safe-upgrade and that turned out to be not enough.
By doing an aptitude full-upgrade, the packages libegl1-nvidia and
libnvidia- eglcore got installed and that fixed the problem for me.
Had an interesting upgrade experience just now. Don't know if it is expected or
not.
I'm using Sid on amd64 with i386 as foreign architecture.
# aptitude safe-upgrade
Resolving dependencies...
The following packages will be REMOVED:
libegl1-nvidia{u} libnvidia-eglcore{u}
The following packages will be upgraded:
gir1.2-glib-2.0 glx-alternative-mesa glx-alternative-nvidia glx-diversions
libcairo-gobject2 libcairo2 libgirepository-1.0-1 libldap-2.4-2 libnvidia-ml1
libtheora0
libtheora0:i386 nvidia-kernel-dkms
12 packages upgraded, 0 newly installed, 2 to remove and 5 not upgraded.
Need to get 6279 kB of archives. After unpacking 44.8 MB will be freed.
Do you want to continue? [Y/n/?]
Get: 1 http://ftp.nl.debian.org/debian/ sid/main libldap-2.4-2 amd64 2.4.40-2
[217 kB]
Get: 2 http://ftp.nl.debian.org/debian/ sid/contrib glx-alternative-mesa amd64
0.5.1 [3488 B]
Get: 3 http://ftp.nl.debian.org/debian/ sid/contrib glx-alternative-nvidia
amd64 0.5.1 [3804 B]
Get: 4 http://ftp.nl.debian.org/debian/ sid/contrib glx-diversions amd64 0.5.1
[9432 B]
Get: 5 http://ftp.nl.debian.org/debian/ sid/main libcairo2 amd64 1.14.0-1 [742
kB]
Get: 6 http://ftp.nl.debian.org/debian/ sid/main libcairo-gobject2 amd64
1.14.0-1 [304 kB]
Get: 7 http://ftp.nl.debian.org/debian/ sid/non-free libnvidia-ml1 amd64
340.46-3 [410 kB]
Get: 8 http://ftp.nl.debian.org/debian/ sid/main libtheora0 i386 1.1.1+dfsg.1-4
[164 kB]
Get: 9 http://ftp.nl.debian.org/debian/ sid/main libtheora0 amd64
1.1.1+dfsg.1-4 [171 kB]
Get: 10 http://ftp.nl.debian.org/debian/ sid/non-free nvidia-kernel-dkms amd64
340.46-3 [4020 kB]
Get: 11 http://ftp.nl.debian.org/debian/ sid/main libgirepository-1.0-1 amd64
1.42.0-2.1 [95.7 kB]
Get: 12 http://ftp.nl.debian.org/debian/ sid/main gir1.2-glib-2.0 amd64
1.42.0-2.1 [141 kB]
Fetched 6279 kB in 1s (3556 kB/s)
...
Current status: 5 updates [-14]
# aptitude full-upgrade
The following NEW packages will be installed:
libegl1-nvidia{a} libgles1-nvidia{a} libgles2-nvidia{a} libnvidia-eglcore{a}
The following packages will be upgraded:
libgl1-nvidia-glx{b} nvidia-alternative nvidia-driver nvidia-vdpau-driver
xserver-xorg-video-nvidia
The following partially installed packages will be configured:
libnvidia-ml1
5 packages upgraded, 4 newly installed, 0 to remove and 0 not upgraded.
Need to get 19.2 MB of archives. After unpacking 44.7 MB will be used.
The following packages have unmet dependencies:
libgl1-nvidia-glx : Breaks: libgl1-nvidia-glx:i386 (!= 340.46-3) but 340.46-2
is installed.
libgl1-nvidia-glx:i386 : Breaks: libgl1-nvidia-glx (!= 340.46-2) but 340.46-3
is to be installed.
The following actions will resolve these dependencies:
Remove the following packages:
1) libgl1-nvidia-glx:i386
2) libgl1-nvidia-glx-i386:i386
Leave the following dependencies unresolved:
3) nvidia-driver recommends libgl1-nvidia-glx-i386
Accept this solution? [Y/n/q/?]
The following NEW packages will be installed:
libegl1-nvidia{a} libgles1-nvidia{a} libgles2-nvidia{a} libnvidia-eglcore{a}
The following packages will be REMOVED:
libgl1-nvidia-glx:i386{a} libgl1-nvidia-glx-i386:i386{a}
The following packages will be upgraded:
libgl1-nvidia-glx nvidia-alternative nvidia-driver nvidia-vdpau-driver
xserver-xorg-video-nvidia
The following partially installed packages will be configured:
libnvidia-ml1
5 packages upgraded, 4 newly installed, 2 to remove and 0 not upgraded.
Need to get 19.2 MB of archives. After unpacking 3478 kB will be used.
Do you want to continue? [Y/n/?]
Get: 1 http://ftp.nl.debian.org/debian/ sid/non-free libnvidia-eglcore amd64
340.46-3 [7000 kB]
Get: 2 http://ftp.nl.debian.org/debian/ sid/non-free libegl1-nvidia amd64
340.46-3 [281 kB]
Get: 3 http://ftp.nl.debian.org/debian/ sid/non-free nvidia-driver amd64
340.46-3 [513 kB]
Get: 4 http://ftp.nl.debian.org/debian/ sid/non-free xserver-xorg-video-nvidia
amd64 340.46-3 [2534 kB]
Get: 5 http://ftp.nl.debian.org/debian/ sid/non-free nvidia-vdpau-driver amd64
340.46-3 [966 kB]
Get: 6 http://ftp.nl.debian.org/debian/ sid/non-free nvidia-alternative amd64
340.46-3 [131 kB]
Get: 7 http://ftp.nl.debian.org/debian/ sid/non-free libgl1-nvidia-glx amd64
340.46-3 [7467 kB]
Get: 8 http://ftp.nl.debian.org/debian/ sid/non-free libgles1-nvidia amd64
340.46-3 [145 kB]
Get: 9 http://ftp.nl.debian.org/debian/ sid/non-free libgles2-nvidia amd64
340.46-3 [148 kB]
Fetched 19.2 MB in 4s (4117 kB/s)
--
GPG: 0x138E41915C7EFED6
signature.asc
Description: This is a digitally signed message part.
Processed: Re: Bug#764272: Intend to NMU for #764272: gobject-introspection: tests/*.c #include config.h which is missing
Processing control commands:
reopen -1
Bug #764272 {Done: intrigeri intrig...@debian.org} [gobject-introspection]
gobject-introspection: tests/*.c #include config.h which is missing
'reopen' may be inappropriate when a bug has been closed with a version;
all fixed versions will be cleared, and you may need to re-add them.
Bug reopened
No longer marked as fixed in versions gobject-introspection/1.42.0-2.1.
notfixed -1 1.42.0-2.1
Bug #764272 [gobject-introspection] gobject-introspection: tests/*.c #include
config.h which is missing
Ignoring request to alter fixed versions of bug #764272 to the same values
previously set
forwarded -1 https://bugzilla.gnome.org/show_bug.cgi?id=738989
Bug #764272 [gobject-introspection] gobject-introspection: tests/*.c #include
config.h which is missing
Changed Bug forwarded-to-address to
'https://bugzilla.gnome.org/show_bug.cgi?id=738989' from
'https://bugzilla.gnome.org/show_bug.cgi?id=737275'
--
764272: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=764272
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#764272: Intend to NMU for #764272: gobject-introspection: tests/*.c #include config.h which is missing
Control: reopen -1 Control: notfixed -1 1.42.0-2.1 Control: forwarded -1 https://bugzilla.gnome.org/show_bug.cgi?id=738989 Hi, I'm very sorry, I had improperly tested that the upstream commit I've cherry-picked in my NMU was enough to fix the problem for libglib-object-introspection-perl... and it isn't: that commit only fixes the problem in tests/scanner/regress.c, which makes the libglib-object-introspection-perl test suite build process go a bit further, but more tests/*.c are affected, including tests/gimarshallingtests.c, and the build breaks a bit further. The attached patch changes tests/gimarshallingtests.c in the same way as the aforementioned upstream commit did for tests/regress.c. This time, I've more carefully verified that it indeed allows running libglib-object-introspection-perl's test suite. I've reported this more general problem upstream, and submitted my new patch there. Should I NMU again with this new patch applied? Sorry again for the burden :( Cheers, -- intrigeri --- a/tests/gimarshallingtests.c +++ b/tests/gimarshallingtests.c @@ -2,7 +2,10 @@ *vim: tabstop=4 shiftwidth=4 expandtab */ +/* This file gets installed, so we can't assume config.h is available */ +#ifdef HAVE_CONFIG_H #include config.h +#endif #include gimarshallingtests.h
Processed: found 764272 in 1.42.0-2.1
Processing commands for cont...@bugs.debian.org: found 764272 1.42.0-2.1 Bug #764272 [gobject-introspection] gobject-introspection: tests/*.c #include config.h which is missing Marked as found in versions gobject-introspection/1.42.0-2.1. thanks Stopping processing here. Please contact me if you need assistance. -- 764272: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=764272 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#760476: gnutls28 3.3.8-3
Thanks, it seems I am correct. Cups closes all open descriptors. I don't know what I can do in gnutls to fix that. That looks like that should be addressed in cups. On 22 October 2014 09:40:01 CEST, Christophe Ségui christophe.se...@math.univ-toulouse.fr wrote: Here is the trace of cups in start phase. Bests Christophe On 21/10/2014 22:50, Nikos Mavrogiannopoulos wrote: On Tue, 21 Oct 2014 11:58:21 +0200 =?UTF-8?B?Q2hyaXN0b3BoZSBTw6lndWk=?= read(3, 0x7fff63334f20, 16) = -1 EINVAL (Invalid argument) write(2, gnutls[2]: Failed to read /dev/u..., 57) = 57 write(2, gnutls[3]: ASSERT: rnd.c:142\n, 29) = 29 write(2, gnutls[3]: ASSERT: rnd.c:329\n, 29) = 29 Thank you. The log shows that indeed reading from /dev/urandom fails. Unfortunately the strace does not start from an early stage, so I cannot see what happens with file descriptor 3 which is supposed to be /dev/urandom. What I see though is that fd 3 is also used in epoll_ctl(), and I suspect that cups has some code that closes all open descriptors. If that's the case it will disrupt gnutls' usage of /dev/urandom the way we see here. regards, Nikos -- Sent fron my mobile. Please excuse my brevity. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: fixed 759932 in 3.2.2-1
Processing commands for cont...@bugs.debian.org:
fixed 759932 3.2.2-1
Bug #759932 {Done: Wilmer van der Gaast wil...@gaast.net} [src:bitlbee]
bitlbee: FTBFS: /bin/sh: 1: cannot create init/bitlbee.service: Directory
nonexistent
Bug #760053 {Done: Wilmer van der Gaast wil...@gaast.net} [src:bitlbee]
bitlbee: FTBFS - cannot create init/bitlbee.service: Directory nonexistent
Marked as fixed in versions bitlbee/3.2.2-1.
Marked as fixed in versions bitlbee/3.2.2-1.
thanks
Stopping processing here.
Please contact me if you need assistance.
--
759932: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=759932
760053: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=760053
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#764272: Intend to NMU for #764272: gobject-introspection: tests/*.c #include config.h which is missing
On 22/10/14 10:14, intrigeri wrote: Control: reopen -1 Control: notfixed -1 1.42.0-2.1 Control: forwarded -1 https://bugzilla.gnome.org/show_bug.cgi?id=738989 Hi, I'm very sorry, I had improperly tested that the upstream commit I've cherry-picked in my NMU was enough to fix the problem for libglib-object-introspection-perl... and it isn't: that commit only fixes the problem in tests/scanner/regress.c, which makes the libglib-object-introspection-perl test suite build process go a bit further, but more tests/*.c are affected, including tests/gimarshallingtests.c, and the build breaks a bit further. The attached patch changes tests/gimarshallingtests.c in the same way as the aforementioned upstream commit did for tests/regress.c. This time, I've more carefully verified that it indeed allows running libglib-object-introspection-perl's test suite. I've reported this more general problem upstream, and submitted my new patch there. Should I NMU again with this new patch applied? Yes. Thanks, Emilio -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#764318: don't see any way out of the libjpeg issue :( ?
$ sudo aptitude install libjpeg8 libjpeg8-dev libdirectfb-dev
The following NEW packages will be installed:
libjpeg-dev{ab} libjpeg62-turbo-dev{ab}
The following packages will be upgraded:
libjpeg8 libjpeg8-dev{b}
2 packages upgraded, 2 newly installed, 0 to remove and 3 not upgraded.
Need to get 505 kB/841 kB of archives. After unpacking 2,879 kB will be used.
The following packages have unmet dependencies:
libjpeg8-dev : Conflicts: libjpeg62-dev but it is not going to be installed.
libjpeg62-turbo-dev : Conflicts: libjpeg8-dev but 8d1-2 is to be installed.
libjpeg-dev : Conflicts: libjpeg8-dev but 8d1-2 is to be installed.
The following actions will resolve these dependencies:
Remove the following packages:
1) fp-units-multimedia-2.6.4
2) fpc
3) fpc-2.6.4
4) liballegro-image5-dev
5) libdirectfb-dev
6) libgd-dev
7) libsdl-gfx1.2-dev
8) libsdl-image1.2-dev
9) libsdl-mixer1.2-dev
10) libsdl-net1.2-dev
11) libsdl-pango-dev
12) libsdl-sge-dev
13) libsdl-sound1.2-dev
14) libsdl-stretch-dev
15) libsdl-ttf2.0-dev
16) libsdl1.2-dev
17) libtiff5-dev
Keep the following packages at their current version:
18) libjpeg-dev [Not Installed]
19) libjpeg62-turbo-dev [Not Installed]
Leave the following dependencies unresolved:
20) liballegro5-dev recommends liballegro-image5-dev
21) fp-units-castle-game-engine recommends fpc
22) fp-units-gfx-2.6.4 recommends libgd-dev
23) lazarus-1.2.4 recommends fpc
24) lazarus-ide-1.2.4 recommends fpc
25) lazarus-ide-gtk2-1.2.4 recommends fpc
26) lazarus-ide-qt4-1.2.4 recommends fpc
27) lcl-1.2.4 recommends fpc
28) lcl-gtk2-1.2.4 recommends fpc
29) lcl-nogui-1.2.4 recommends fpc
30) lcl-units-1.2.4 recommends fpc
Accept this solution? [Y/n/q/?] q
Abandoning all efforts to resolve these dependencies.
Abort.
As can be seen lot of packages will be removed if I go down this path .
Looking for guidance.
--
Regards,
Shirish Agarwal शिरीष अग्रवाल
My quotes in this email licensed under CC 3.0
http://creativecommons.org/licenses/by-nc/3.0/
http://flossexperiences.wordpress.com
EB80 462B 08E1 A0DE A73A 2C2F 9F3D C7A4 E1C4 D2D8
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#766319: libavifile-0.7c2: Uninstallable (not BinNMU-safe)
Package: libavifile-0.7c2 Version: 1:0.7.48~20090503.ds-16 Severity: serious Hi, libavifile-0.7c2 version 0.7.48~20090503.ds-16+b2 is currently uninstallable as it has been BinNMUed, but seems not BinNMU-safe: The following packages have unmet dependencies: libavifile-0.7c2 : Depends: libavifile-0.7-common (= 1:0.7.48~20090503.ds-16+b2) but 1:0.7.48~20090503.ds-16 is to be installed libavifile-0.7-common is Architecture: all and the dependency on it in libavifile-0.7c2 should not contain the BinNMU suffix. # apt-cache policy libavifile-0.7c2 libavifile-0.7-common libavifile-0.7c2: Installed: 1:0.7.48~20090503.ds-16 Candidate: 1:0.7.48~20090503.ds-16+b2 Version table: 1:0.7.48~20090503.ds-16+b2 0 500 http://debian.ethz.ch/mirror/debian/ sid/main i386 Packages *** 1:0.7.48~20090503.ds-16 0 500 http://debian.ethz.ch/mirror/debian/ testing/main i386 Packages 100 /var/lib/dpkg/status libavifile-0.7-common: Installed: 1:0.7.48~20090503.ds-16 Candidate: 1:0.7.48~20090503.ds-16 Version table: *** 1:0.7.48~20090503.ds-16 0 500 http://debian.ethz.ch/mirror/debian/ sid/main i386 Packages 500 http://debian.ethz.ch/mirror/debian/ testing/main i386 Packages 100 /var/lib/dpkg/status -- System Information: Debian Release: jessie/sid APT prefers unstable APT policy: (990, 'unstable'), (600, 'testing'), (500, 'buildd-unstable'), (400, 'stable'), (110, 'experimental'), (1, 'buildd-experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.17-rc5-amd64 (SMP w/1 CPU core) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#766319: libavifile-0.7c2: Uninstallable (not BinNMU-safe)
Control: forcemerge 765148 766319 Control: retitle 765148 libavifile-0.7c2: Uninstallable (not BinNMU-safe) Hi again, Axel Beckert wrote: libavifile-0.7c2 version 0.7.48~20090503.ds-16+b2 is currently uninstallable as it has been BinNMUed, but seems not BinNMU-safe: Of course I checked for existing bugs for this issue, but the only other RC bug seemed an FTBFS. Actually it was just not properly titled. Hence merging. Yavor: Next time you merge such bugs, please make sure that the shown bug is properly titled. TIA! Regards, Axel -- ,''`. | Axel Beckert a...@debian.org, http://people.debian.org/~abe/ : :' : | Debian Developer, ftp.ch.debian.org Admin `. `' | 1024D: F067 EA27 26B9 C3FC 1486 202E C09E 1D89 9593 0EDE `-| 4096R: 2517 B724 C5F6 CA99 5329 6E61 2FF9 CD59 6126 16B5 -- 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#766319: libavifile-0.7c2: Uninstallable (not BinNMU-safe)
Processing control commands: reassign -1 src:avifile 1:0.7.48~20090503.ds-16 Bug #766319 [libavifile-0.7c2] libavifile-0.7c2: Uninstallable (not BinNMU-safe) Bug reassigned from package 'libavifile-0.7c2' to 'src:avifile'. No longer marked as found in versions avifile/1:0.7.48~20090503.ds-16. Ignoring request to alter fixed versions of bug #766319 to the same values previously set Bug #766319 [src:avifile] libavifile-0.7c2: Uninstallable (not BinNMU-safe) Marked as found in versions avifile/1:0.7.48~20090503.ds-16. forcemerge 765669 -1 Bug #765669 [src:avifile] avifile: not binNMU safe Bug #765148 [src:avifile] cynthiune.app: FTBFS: build-dependency not installable: libavifile-0.7-dev (= 1:0.7.48~20090503.ds) Bug #766319 [src:avifile] libavifile-0.7c2: Uninstallable (not BinNMU-safe) Added tag(s) sid, pending, jessie, and patch. Bug #765148 [src:avifile] cynthiune.app: FTBFS: build-dependency not installable: libavifile-0.7-dev (= 1:0.7.48~20090503.ds) Merged 765148 765669 766319 -- 765148: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=765148 765669: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=765669 766319: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=766319 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#766319: libavifile-0.7c2: Uninstallable (not BinNMU-safe)
Processing control commands: forcemerge 765148 766319 Bug #765148 [src:avifile] cynthiune.app: FTBFS: build-dependency not installable: libavifile-0.7-dev (= 1:0.7.48~20090503.ds) Bug #765669 [src:avifile] avifile: not binNMU safe Bug #766319 [src:avifile] libavifile-0.7c2: Uninstallable (not BinNMU-safe) Bug #765669 [src:avifile] avifile: not binNMU safe Bug #766319 [src:avifile] libavifile-0.7c2: Uninstallable (not BinNMU-safe) Merged 765148 765669 766319 retitle 765148 libavifile-0.7c2: Uninstallable (not BinNMU-safe) Bug #765148 [src:avifile] cynthiune.app: FTBFS: build-dependency not installable: libavifile-0.7-dev (= 1:0.7.48~20090503.ds) Bug #765669 [src:avifile] avifile: not binNMU safe Bug #766319 [src:avifile] libavifile-0.7c2: Uninstallable (not BinNMU-safe) Changed Bug title to 'libavifile-0.7c2: Uninstallable (not BinNMU-safe)' from 'cynthiune.app: FTBFS: build-dependency not installable: libavifile-0.7-dev (= 1:0.7.48~20090503.ds)' Changed Bug title to 'libavifile-0.7c2: Uninstallable (not BinNMU-safe)' from 'avifile: not binNMU safe' Ignoring request to change the title of bug#766319 to the same title -- 765148: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=765148 765669: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=765669 766319: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=766319 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#766319: libavifile-0.7c2: Uninstallable (not BinNMU-safe)
Control: reassign -1 src:avifile 1:0.7.48~20090503.ds-16 Control: forcemerge 765669 -1 On 2014-10-22 11:05:17, Axel Beckert wrote: Package: libavifile-0.7c2 Version: 1:0.7.48~20090503.ds-16 Severity: serious Hi, libavifile-0.7c2 version 0.7.48~20090503.ds-16+b2 is currently uninstallable as it has been BinNMUed, but seems not BinNMU-safe: The following packages have unmet dependencies: libavifile-0.7c2 : Depends: libavifile-0.7-common (= 1:0.7.48~20090503.ds-16+b2) but 1:0.7.48~20090503.ds-16 is to be installed libavifile-0.7-common is Architecture: all and the dependency on it in libavifile-0.7c2 should not contain the BinNMU suffix. This issue is already tracked in #765669. Merging. Cheers -- Sebastian Ramacher signature.asc Description: Digital signature
Bug#766319: libavifile-0.7c2: Uninstallable (not BinNMU-safe)
Hi Sebastian, Sebastian Ramacher wrote: This issue is already tracked in #765669. Yeah, noticed it after sending the bug. But #765669 is not correctly titled (FTBFS). Merging. Did that just now, too, so it likely will be ignored. But I also triggered a retitling, so it's still good for something. Regards, Axel -- ,''`. | Axel Beckert a...@debian.org, http://people.debian.org/~abe/ : :' : | Debian Developer, ftp.ch.debian.org Admin `. `' | 1024D: F067 EA27 26B9 C3FC 1486 202E C09E 1D89 9593 0EDE `-| 4096R: 2517 B724 C5F6 CA99 5329 6E61 2FF9 CD59 6126 16B5 -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#766322: circular dependencies causes dpkg --configure -a to go into a tight loop
Package: dpkg Version: 1.17.19 Severity: critical Justification: breaks unrelated software Dear Maintainer, The problem is manifest when I run the command dpkg --configure -a. Doing this, the command produces no output but I see that it running flat-out on a single core, consuming 100% of that core's CPU. I attempted to diagnose the problem using gdb, but there's no symbolic/debug data in the dpkg command and no package that provide this missing data. Enabling debug output, I can see some activity from dpkg. Adding -D40 to the command yields a stream of two-line outputs like: D40: checking dependencies of [package] (- none) D40: ok 1 msgs where [package] is the name of a package. Initially the package names ([package] above) cover many packages, but in successive output lines, the package sgml-base:all comes to dominate until almost all lines are: D40: checking dependencies of sgml-base:all (- none) D40: ok 1 msgs If I filter out these two specific lines: dpkg --configure -D40 -a 21 | egrep -v sgml-base:all|ok 1 msgs I see packages other than sgml-base:all are still mentioned, but the rate at which they appear decreases. After a few seconds the rate of other package names appearing is (~5 Hz). After a minute or so, the average rate drops to (~1 Hz). Running the command with debug set to 440 (-D440), I see that these sgml- base:all has a dependency on perl. I've captured the output for a few seconds (some 780,000 lines) and will try to attach this to the bug as a compressed file. I noticed that both perl and perl-modules are not configured and that they have a circular dependency. Because of this, both perl and perl-modules must be configured at the same time: zitpcx6184:~# dpkg --configure perl dpkg: dependency problems prevent configuration of perl: perl depends on perl-modules (= 5.20.1-2); however: Package perl-modules is not configured yet. dpkg: error processing package perl (--configure): dependency problems - leaving unconfigured Errors were encountered while processing: perl zitpcx6184:~# zitpcx6184:~# dpkg --configure perl-modules dpkg: dependency problems prevent configuration of perl-modules: perl-modules depends on perl (= 5.20.1-1); however: Package perl is not configured yet. dpkg: error processing package perl-modules (--configure): dependency problems - leaving unconfigured Errors were encountered while processing: perl-modules zitpcx6184:~# zitpcx6184:~# dpkg --configure perl-modules perl Setting up perl-modules (5.20.1-2) ... Setting up perl (5.20.1-2) ... zitpcx6184:~# After configuring perl and perl-modules, dpkg --configure -a worked as expected. My suspicion is that the circular dependency between perl and perl-modules confused dpkg so it couldn't compute the dependency graph. HTH, Paul. -- System Information: Debian Release: jessie/sid APT prefers unstable APT policy: (990, 'unstable') Architecture: i386 (i686) Kernel: Linux 3.16-2-686-pae (SMP w/2 CPU cores) Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages dpkg depends on: ii libbz2-1.0 1.0.6-7 ii libc62.19-11 ii liblzma5 5.1.1alpha+20120614-2 ii libselinux1 2.3-2 ii tar 1.27.1-2 ii zlib1g 1:1.2.8.dfsg-2 dpkg recommends no packages. Versions of packages dpkg suggests: ii apt 1.0.9.3 -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: The inittab interface - Re: Bug#766187: runit: Fails to install runit after fresh install of jessie beta2
Processing commands for cont...@bugs.debian.org: severity 766187 grave Bug #766187 [runit] runit: Fails to install runit after fresh install of jessie beta2 Severity set to 'grave' from 'important' quit Stopping processing here. Please contact me if you need assistance. -- 766187: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=766187 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#766048: marked as done (dash 0.5.8-1 (experimental): build failures with several packages)
Your message dated Wed, 22 Oct 2014 09:20:46 + with message-id e1xgs62-0007ll...@franck.debian.org and subject line Bug#766048: fixed in dash 0.5.8-2 has caused the Debian Bug report #766048, regarding dash 0.5.8-1 (experimental): build failures with several packages 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.) -- 766048: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=766048 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: dash Version: 0.5.8-1 Severity: grave A rebuild of the archive with dash version 0.5.8-1 from experimental shows several build failures. Thanks to David Suárez for his support, see here for the rebuild results: http://aws-logs.debian.net/ftbfs-logs/dash/ Regards, Gerrit. ---End Message--- ---BeginMessage--- Source: dash Source-Version: 0.5.8-2 We believe that the bug you reported is fixed in the latest version of dash, 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 766...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Gerrit Pape p...@smarden.org (supplier of updated dash 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: Mon, 20 Oct 2014 17:46:03 + Source: dash Binary: dash ash Architecture: all source Version: 0.5.8-2 Distribution: experimental Urgency: medium Maintainer: Gerrit Pape p...@smarden.org Changed-By: Gerrit Pape p...@smarden.org Description: ash- compatibility package for dash dash - POSIX-compliant shell Closes: 766048 Changes: dash (0.5.8-2) experimental; urgency=medium . * debian/rules: pass --disable-lineno option to configure (thx Sven Joachim, closes: #766048). Checksums-Sha1: 4112488a4f8f1463da35fb3d8dc88d59f5b30208 1102 dash_0.5.8-2.dsc 94616e3edc84ec709ef3fd8b043f9b17fe496625 41715 dash_0.5.8-2.diff.gz 59e04db25530bccf30db2699a9fd505744e1df3d 30126 ash_0.5.8-2_all.deb Checksums-Sha256: bda57136cdb4812781ff0402594029a4a41313dbf31019c7e8af295418baf4f2 1102 dash_0.5.8-2.dsc 00168a934864c26cae9a51367fe7ea013ece2d4844ff8bd6893fc00a8fa7b38c 41715 dash_0.5.8-2.diff.gz 49dee3beb2fd43e33872c0a12dd77afa6eec0dd5b070df92fb548f9f86e0c896 30126 ash_0.5.8-2_all.deb Files: 8ca7426231c2a539794361bcf4dc0dd6 1102 shells optional dash_0.5.8-2.dsc 01e36e658d3e5b33fdb5629807db110a 41715 shells optional dash_0.5.8-2.diff.gz 29aacb42151ff38d94db3c6a1dcf2701 30126 shells optional ash_0.5.8-2_all.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1 iEYEARECAAYFAlRHaasACgkQGJoyQbxwpv+xxQCgnNcEF8GTfVsRtKAmNzp2lq/O DWEAnjfvrczopw7jPONWP6phOeSq5ib5 =tQ0a -END PGP SIGNATUREEnd Message---
Processed: tagging 764272
Processing commands for cont...@bugs.debian.org: tags 764272 - fixed-upstream Bug #764272 [gobject-introspection] gobject-introspection: tests/*.c #include config.h which is missing Removed tag(s) fixed-upstream. thanks Stopping processing here. Please contact me if you need assistance. -- 764272: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=764272 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#765288: marked as done (hubicfuse: FTBFS on kfreebsd-*: #error On FreeBSD API version 25 or greater must be used)
Your message dated Wed, 22 Oct 2014 09:22:33 + with message-id e1xgs7l-0007nr...@franck.debian.org and subject line Bug#765288: fixed in hubicfuse 1.1.0-2 has caused the Debian Bug report #765288, regarding hubicfuse: FTBFS on kfreebsd-*: #error On FreeBSD API version 25 or greater must be used 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.) -- 765288: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=765288 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Source: hubicfuse Version: 1.1.0-1 Severity: serious Justification: fails to build from source hubicfuse failed to build on kfreebsd-* with: | gcc -g -O2 -fstack-protector-strong -Wformat -Werror=format-security -I/usr/include/libxml2 -D_FILE_OFFSET_BITS=64 -I/usr/include/fuse -I/usr/include/json-c -o hubicfuse cloudfsapi.c cloudfuse.c -lxml2 -lcurl -lfuse -pthread -lssl -lcrypto -ljson-c | In file included from /usr/include/fuse/fuse.h:26:0, | from cloudfsapi.c:21: | /usr/include/fuse/fuse_common.h:474:8: error: #error On FreeBSD API version 25 or greater must be used | # error On FreeBSD API version 25 or greater must be used | ^ | make[1]: *** [hubicfuse] Error 1 See https://buildd.debian.org/status/fetch.php?pkg=hubicfusearch=kfreebsd-amd64ver=1.1.0-1stamp=1411982875 for a full build log. Cheers -- Sebastian Ramacher signature.asc Description: Digital signature ---End Message--- ---BeginMessage--- Source: hubicfuse Source-Version: 1.1.0-2 We believe that the bug you reported is fixed in the latest version of hubicfuse, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 765...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Sylvestre Ledru sylves...@debian.org (supplier of updated hubicfuse 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, 22 Oct 2014 10:04:59 +0200 Source: hubicfuse Binary: hubicfuse Architecture: source amd64 Version: 1.1.0-2 Distribution: unstable Urgency: medium Maintainer: Sylvestre Ledru sylves...@debian.org Changed-By: Sylvestre Ledru sylves...@debian.org Description: hubicfuse - Support for mounting Hubic drive Closes: 765288 Changes: hubicfuse (1.1.0-2) unstable; urgency=medium . * Fix the Kfreebsd FTBFS. Thanks to Steven Chamberlain (Closes: #765288) Checksums-Sha1: d46e9017db9ca4891d430895a23fb5885d3e0017 1944 hubicfuse_1.1.0-2.dsc bee715bfa44558ec0c538a74cf87931c19ead13a 2532 hubicfuse_1.1.0-2.debian.tar.xz b8c5f4fb5e4275d030d53b90be5282af381918ae 14204 hubicfuse_1.1.0-2_amd64.deb Checksums-Sha256: 807ae63464b8345d33504457cb69f4bcc2107a626d9d0b64427c2dd19b4741b0 1944 hubicfuse_1.1.0-2.dsc 1eed117f9551a121493d57cf7f36e6d17d82b69db712825051d97411cf217217 2532 hubicfuse_1.1.0-2.debian.tar.xz 20008a972989e5d4f7ff2a2dd33b30c7c661579f73a031c793e69896c9854f87 14204 hubicfuse_1.1.0-2_amd64.deb Files: c3648fbd54bf9eddffdc699f0d44154c 1944 utils optional hubicfuse_1.1.0-2.dsc b6918361f1dcb65da5911a35ee41dffb 2532 utils optional hubicfuse_1.1.0-2.debian.tar.xz e6ec96cc1d34a3ed43e6c0b507890f3f 14204 utils optional hubicfuse_1.1.0-2_amd64.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1 iQIcBAEBCAAGBQJUR2woAAoJEH5lKNp1LxvhTIgP/2hmlpON0I7uoVvf+BCXf8WU CQUGskYmMTTqfMoSPuHusQSsHRnE41Sk3dCiPvfWuna54xL9plZo/IlxiR5Gr+Qm 3rZ+PmMRKHHDXn6GbABufB7LJ9UrwgdJXaz95z0fw+yBrir5+cs1KRLFD4uA70sf RAjUvSfQN61I2G2GzWaGxFuxXhIzp+tVnrAqHmgNjLTLBOxHi4QVgSI3gxVzIY0U LmDj1zqQFkY42nn3DHuBzK6wBwgIjrRgLtHWNIx1f5LCspQlw8XX5qKya9DvJWpx QSfqTdMZFUPSPsouEzCi9tpmJ2VHp7DxbXqY9L1ejJDNM6xUg1WaAVc/cmsV4dA0 AfCjmRYhGqXP4VFQ9nZfiSG1Z93jD9c4cHNLSGUNKrB5NEmoEtOs0cC4qJ2SB1wJ I/R4f60YV6SAny1Wi0V0tMk1RRlzSq1dNsMaaa7ibn0hlw7RtdfCr+xF/+1SG8fU XOUE9hpj938tBAfCfh2s/tUM8/U3OZpyMtsJvevAuZDlODAGLxVF8NzBUyEofOkQ 5eZC/5w6cCwYWf6q85EwjI2YiDCiBysTHazsOAL34l+4lJKaTQekWf32edKWPx1+ 1gpaQLhu1eiyxkRdfbywm3Km5JUpsU0MaKNciDu1k7Cdz8DYUt8MdHOz8sPykan4 Fpz6ayPWYtU3HOnGM8gX =3Vc+ -END PGP SIGNATUREEnd Message---
Bug#765822: marked as done (src:mame: Please change build dependency to libjpeg-dev (libjpeg-turbo transition))
Your message dated Wed, 22 Oct 2014 09:26:04 +
with message-id e1xgsba-rg...@franck.debian.org
and subject line Bug#765822: fixed in mame 0.154-3.1
has caused the Debian Bug report #765822,
regarding src:mame: Please change build dependency to libjpeg-dev
(libjpeg-turbo transition)
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.)
--
765822: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=765822
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
---BeginMessage---
Package: src:mame
Version: 0.146-5
Severity: serious
Justification: libjpeg-turbo transition
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Dear maintainer(s),
Debian is transitioning from IJG JPEG library (src:libjpeg8) to
libjpeg-turbo implementation (src:libjpeg-turbo)[1] of libjpeg62 API
with decode from memory buffer interface (jpeg_mem_{src,dest}).
Your package cannot be transitioned automatically as it explicitly
build depends on specific API/ABI (libjpeg8-dev) and this build
dependency needs to be changed to libjpeg-dev. In most if not all
cases this should be sufficient to build against libjpeg-turbo.
I am in process of testing each package in question to compile against
libjpeg-turbo and I will provide a suitable patch for each package
when I will succeed.
On the other hand please note that the winter^Wfreeze is coming and
if your package is not updated in due time it might be NMUed by the
release team (or by me with the full ack of release team).
That also means that if you are OK with NMU then please respond to
this bug report and I will prepare and upload the recompiled packages
for you.
Cheers,
Ondrej
1. The full Technical Committee decision can be found here:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=717076#235
- -- System Information:
Debian Release: jessie/sid
APT prefers testing
APT policy: (990, 'testing'), (700, 'unstable')
Architecture: amd64 (x86_64)
Kernel: Linux 3.2.0-4-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_DK.UTF-8, LC_CTYPE=en_DK.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
-BEGIN PGP SIGNATURE-
Version: GnuPG v1
iQJ8BAEBCgBmBQJUQm82XxSAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w
ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXQzMEI5MzNEODBGQ0UzRDk4MUEyRDM4RkIw
Qzk5QjcwRUY0RkNCQjA3AAoJEAyZtw70/LsHiaEQAO7W2dGW62zejewaLGbaP3dy
ZjpPhQMEnwJcggpFwsdsrtULobHc9AAoU+n7A98gGPNKKKMKvKQiKtngTfwbvHRM
yrK8v2cnfgt8RZJI+amBOanjT8Pqg6yFYl/uXSi+NUWuIvsaV9vBhiA7dO45z3HW
ROyqlyInrC/4mUGGSTwWCnpRoAGTaSLz11TbONoHIlDvB5V02KkGlApfm1mYaQPk
kFBJ3xckSfmoWJcGrVAGTofztP6sDVW7CgS+UpjynewooojzzAHXuJXyhZPGkJkM
pjubKUam3mHnw6kg3MYL9tjp731UwrUILgAgudgCIfiFwV/0kog3M5qlD7HaCJat
2MDrHqy9q3KxiISmK6ScfFcGw25wP5k9RsplLttOWgQTsIFaSNOVNpW+gwZ3GQnV
SlVHoI/Vp/CyvPY4fQPSPB/D3b0WjagTox2/gj28JWJUuGll4P82hYpqvjqnktX3
PcLzyNN2XWDuRwF5Rhhn5tYXVhmiiQ4IEfVHYuR+He7hJceLfPsbmjr/49zX21XX
DSZKlIsSIr4jT+JOKqpZqLKTcgbNhMHuoqIA4+uaJoYRm7lqyX25CGqZjd4HfhTj
Ti13niJ7+LfdQEahHq5AVMntF8sPa25I89Iy/dZff0FQwcYECH1POXJhfe/SZpfy
1UY5TKX2YYAKGK8bfUau
=Cj0g
-END PGP SIGNATURE-
---End Message---
---BeginMessage---
Source: mame
Source-Version: 0.154-3.1
We believe that the bug you reported is fixed in the latest version of
mame, which is due to be installed in the Debian FTP archive.
A summary of the changes between this version and the previous one is
attached.
Thank you for reporting the bug, which will now be closed. If you
have further comments please address them to 765...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Andreas Barth a...@ayous.org (supplier of updated mame 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, 21 Oct 2014 21:54:14 +
Source: mame
Binary: mame mame-tools mess mess-data
Architecture: source ppc64el all
Version: 0.154-3.1
Distribution: unstable
Urgency: medium
Maintainer: Debian Games Team pkg-games-de...@lists.alioth.debian.org
Changed-By: Andreas Barth a...@ayous.org
Description:
mame - Multiple Arcade Machine Emulator (MAME)
mame-tools - Tools for MAME and MESS
mess - Multi Emulator Super System (MESS)
mess-data - Data files for the Multi Emulator Super System (MESS)
Closes: 765822
Changes:
mame (0.154-3.1) unstable; urgency=medium
.
* Non-maintainer upload.
* Change dependency to libjpeg-dev. Closes: #765822
Checksums-Sha1:
d576e67b87e71b98e1411442bf6016486f07223e 1724
Bug#766319: libavifile-0.7c2: Uninstallable (not BinNMU-safe)
Axel Beckert wrote: Yavor: Next time you merge such bugs, please make sure that the shown bug is properly titled. TIA! Apologies; I'll be more careful in the future. -- 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 764253 is serious
Processing commands for cont...@bugs.debian.org: severity 764253 serious Bug #764253 [system-config-printer] system-config-printer: Creates millions of ppd symlinks Bug #764472 [system-config-printer] cups creates millions of temporary files when printing Severity set to 'serious' from 'important' Severity set to 'serious' from 'important' thanks Stopping processing here. Please contact me if you need assistance. -- 764253: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=764253 764472: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=764472 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#764272: Intend to NMU for #764272: gobject-introspection: tests/*.c #include config.h which is missing
Hi again, Emilio Pozuelo Monfort wrote (22 Oct 2014 08:48:23 GMT) : On 22/10/14 10:14, intrigeri wrote: Should I NMU again with this new patch applied? Yes. Done. Attached updated `svn diff`, that combines both NMUs. Cheers, -- intrigeri Index: debian/changelog === --- debian/changelog (revision 43727) +++ debian/changelog (working copy) @@ -1,3 +1,20 @@ +gobject-introspection (1.42.0-2.2) unstable; urgency=medium + + * Non-maintainer upload. + * Dont_unconditionally_include_config.h_in_gimarshallingtests.c.patch: +new patch, similar to the one applied in the last upload, that fixed +the same problem in regress.c only (Closes: #764272) + + -- intrigeri intrig...@debian.org Wed, 22 Oct 2014 11:20:04 +0200 + +gobject-introspection (1.42.0-2.1) unstable; urgency=medium + + * Non-maintainer upload. + * Dont_unconditionally_include_config.h_in_regress.c.patch: new patch, +cherry-picked from upstream (Closes: #764272) + + -- intrigeri intrig...@debian.org Tue, 21 Oct 2014 22:09:08 +0200 + gobject-introspection (1.42.0-2) unstable; urgency=medium * dh_girepository: Add a versioned dependency on libgirepository-1.0-1 Index: debian/patches/Dont_unconditionally_include_config.h_in_gimarshallingtests.c.patch === --- debian/patches/Dont_unconditionally_include_config.h_in_gimarshallingtests.c.patch (revision 0) +++ debian/patches/Dont_unconditionally_include_config.h_in_gimarshallingtests.c.patch (working copy) @@ -0,0 +1,19 @@ +Author: intrigeri intrig...@debian.org +Bug: https://bugzilla.gnome.org/show_bug.cgi?id=738989 +Bug-Debian: https://bugs.debian.org/764272 +Origin: vendor, https://bugzilla.gnome.org/attachment.cgi?id=289106 +Subject: Don't unconditionally include config.h in gimashallingtests.c + +--- a/tests/gimarshallingtests.c b/tests/gimarshallingtests.c +@@ -2,7 +2,10 @@ + *vim: tabstop=4 shiftwidth=4 expandtab + */ + ++/* This file gets installed, so we can't assume config.h is available */ ++#ifdef HAVE_CONFIG_H + #include config.h ++#endif + + #include gimarshallingtests.h + Index: debian/patches/Dont_unconditionally_include_config.h_in_regress.c.patch === --- debian/patches/Dont_unconditionally_include_config.h_in_regress.c.patch (revision 0) +++ debian/patches/Dont_unconditionally_include_config.h_in_regress.c.patch (working copy) @@ -0,0 +1,27 @@ +From 578eebd54bd9f2b1677922680701c454f489c895 Mon Sep 17 00:00:00 2001 +From: Matthias Clasen mcla...@redhat.com +Date: Fri, 10 Oct 2014 11:36:23 -0400 +Bug: https://bugzilla.gnome.org/show_bug.cgi?id=737275 +Bug-Debian: https://bugs.debian.org/764272 +Origin: https://git.gnome.org/browse/gobject-introspection/commit/?id=578eebd54bd9f2b1677922680701c454f489c895 +Subject: Don't unconditionally include config.h in regress.c + +This is an installed file, so we can't assume that config.h +will be around. + +diff --git a/tests/scanner/regress.c b/tests/scanner/regress.c +index 3d3cfdd..8a0652f 100644 +--- a/tests/scanner/regress.c b/tests/scanner/regress.c +@@ -1,5 +1,8 @@ + /* -*- mode: C; c-file-style: gnu; indent-tabs-mode: nil; -*- */ ++/* This file gets installed, so we can't assume config.h is available */ ++#ifdef HAVE_CONFIG_H + #include config.h ++#endif + + #include string.h + #include stdlib.h +-- +cgit v0.10.1 + Index: debian/patches/series === --- debian/patches/series (revision 43727) +++ debian/patches/series (working copy) @@ -1,2 +1,4 @@ #needed only until all packages are moved to mutliarch paths pre_multiarch_compat +Dont_unconditionally_include_config.h_in_regress.c.patch +Dont_unconditionally_include_config.h_in_gimarshallingtests.c.patch
Bug#764272: marked as done (gobject-introspection: tests/*.c #include config.h which is missing)
Your message dated Wed, 22 Oct 2014 09:52:02 + with message-id e1xgsai-w7...@franck.debian.org and subject line Bug#764272: fixed in gobject-introspection 1.42.0-2.2 has caused the Debian Bug report #764272, regarding gobject-introspection: tests/*.c #include config.h which is missing 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.) -- 764272: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=764272 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: gobject-introspection Version: 1.42.0-2 Control: affects -1 libglib-object-introspection-perl X-Debbugs-Cc: libglib-object-introspection-p...@packages.debian.org, intrig...@debian.org The libglib-object-introspection-perl package recently started skipping its test suite because it can't build test libraries. Adding some debugging into Makefile.PL shows it's trying to do this: % gcc -shared -fPIC -g \ -I/usr/include/cairo -I/usr/include/glib-2.0 -I/usr/lib/x86_64-linux-gnu/glib-2.0/include -I/usr/include/pixman-1 -I/usr/include/freetype2 -I/usr/include/libpng12 -I/usr/include/cairo -I/usr/include/pixman-1 -I/usr/include/freetype2 -I/usr/include/libpng12 -I/usr/include/glib-2.0 -I/usr/lib/x86_64-linux-gnu/glib-2.0/include -pthread -I/usr/include/glib-2.0 -I/usr/lib/x86_64-linux-gnu/glib-2.0/include \ /usr/share/gobject-introspection-1.0/tests/regress.c \ -lcairo -lcairo-gobject -lcairo -lgobject-2.0 -lglib-2.0 -lgio-2.0 -lgobject-2.0 -lglib-2.0 \ -o libregress.so /usr/share/gobject-introspection-1.0/tests/regress.c:2:20: fatal error: config.h: No such file or directory #include config.h ^ compilation terminated. It looks like /usr/share/gobject-introspection-1.0/tests/*.c have acquired #include config.h between 1.40.0-2 and 1.42.0-2, and I can't see config.h in the package. I assume this not intentional? -- Niko Tyni nt...@debian.org ---End Message--- ---BeginMessage--- Source: gobject-introspection Source-Version: 1.42.0-2.2 We believe that the bug you reported is fixed in the latest version of gobject-introspection, 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 764...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. intrigeri intrig...@debian.org (supplier of updated gobject-introspection 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: Wed, 22 Oct 2014 11:29:07 CEST Source: gobject-introspection Binary: libgirepository-1.0-1 libgirepository1.0-dev libgirepository1.0-doc gobject-introspection gir1.2-glib-2.0 gir1.2-freedesktop Architecture: source all amd64 Version: 1.42.0-2.2 Distribution: unstable Urgency: medium Maintainer: Debian GNOME Maintainers pkg-gnome-maintain...@lists.alioth.debian.org Changed-By: intrigeri intrig...@debian.org Description: gir1.2-freedesktop - Introspection data for some FreeDesktop components gir1.2-glib-2.0 - Introspection data for GLib, GObject, Gio and GModule gobject-introspection - Generate interface introspection data for GObject libraries libgirepository-1.0-1 - Library for handling GObject introspection data (runtime library) libgirepository1.0-dev - Library for handling GObject introspection data (development file libgirepository1.0-doc - Library for handling GObject introspection data (documentation) Closes: 764272 Changes: gobject-introspection (1.42.0-2.2) unstable; urgency=medium . * Non-maintainer upload. * Dont_unconditionally_include_config.h_in_gimarshallingtests.c.patch: new patch, similar to the one applied in the last upload, that fixed the same problem in regress.c only (Closes: #764272) Checksums-Sha256: 93ea9071f61d4b2280fb20f306eac3c64b4cd4272492e38655d2c451f9c86e4a 2856 gobject-introspection_1.42.0-2.2.dsc e529aa1de821dc37805ddfecd9c2032662c43a5f55510f854fa9c4e0fb45dc86 19868 gobject-introspection_1.42.0-2.2.debian.tar.xz Checksums-Sha1: 900cbf00509e06b0d65ac74aedf33b6da9e03ca2 2856 gobject-introspection_1.42.0-2.2.dsc 902af2312f9ebd28aec727ed75fc60f53f637648 19868 gobject-introspection_1.42.0-2.2.debian.tar.xz Files:
Bug#708561: marked as done (barcode: libbarcode is compiled without -fPIC option making it unusable in shared libs)
Your message dated Wed, 22 Oct 2014 09:51:53 + with message-id e1xgsa9-t9...@franck.debian.org and subject line Bug#708561: fixed in barcode 0.98+debian-9.1 has caused the Debian Bug report #708561, regarding barcode: libbarcode is compiled without -fPIC option making it unusable in shared libs 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.) -- 708561: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=708561 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: barcode Version: 0.98+debian-9 Severity: normal Dear Maintainer, libbarcode isn't compiled using -fPIC making it impossible to use within shared libraries (at least on 64bit systems). Adding -fPIC to the CFLAGS entry in Makefile.in fixes the problem and shouldn't do any harm for other use cases. Regards, Peter -- System Information: Debian Release: 7.0 APT prefers stable APT policy: (500, 'stable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.2.0-4-amd64 (SMP w/6 CPU cores) Locale: LANG=de_DE.utf8, LC_CTYPE=de_DE.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages barcode depends on: ii install-info 4.13a.dfsg.1-10 ii libc6 2.13-38 barcode recommends no packages. barcode suggests no packages. -- no debconf information ---End Message--- ---BeginMessage--- Source: barcode Source-Version: 0.98+debian-9.1 We believe that the bug you reported is fixed in the latest version of barcode, 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 708...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Hilko Bengen ben...@debian.org (supplier of updated barcode 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: Mon, 20 Oct 2014 11:04:37 +0200 Source: barcode Binary: barcode barcode-dbg Architecture: source amd64 Version: 0.98+debian-9.1 Distribution: unstable Urgency: medium Maintainer: Hilko Bengen ben...@debian.org Changed-By: Hilko Bengen ben...@debian.org Description: barcode- Utility and library for barcode generation barcode-dbg - Utility and library for barcode generation (debug) Closes: 708561 Changes: barcode (0.98+debian-9.1) unstable; urgency=medium . * Non-maintainer upload * build with -fPIC (Closes: #708561) Checksums-Sha1: 6ae003237250917bd96e12d936467c129a7b227b 1159 barcode_0.98+debian-9.1.dsc 54299541ca6cbf4b705cf13869016d3ddeaf5bb0 8436 barcode_0.98+debian-9.1.diff.gz 2f1583cc0eb41a0c329553c142821657912e9b31 58004 barcode_0.98+debian-9.1_amd64.deb 0aa4ef4aa4239a3e6f9a65309b3bc0d93a387362 12656 barcode-dbg_0.98+debian-9.1_amd64.deb Checksums-Sha256: 1242ac93b1a93a31c84419d04030fcabc4ca2fc7f570f5e6c6a4800555387b3a 1159 barcode_0.98+debian-9.1.dsc 7fe4441fc75a24ccb6b08102d32eb927accf71951b6c6a63be87aadafdb1d837 8436 barcode_0.98+debian-9.1.diff.gz 0acfa6181b5ba30c17be61ad0fbedb571f830039fa3c2e595b3b5971f777c63f 58004 barcode_0.98+debian-9.1_amd64.deb cf22bf6b55257ca671184be6126b44eaf37c2d812820832cc216a5564a1e47c3 12656 barcode-dbg_0.98+debian-9.1_amd64.deb Files: 67a9c68ce222fbe4bb251f06e14be70d 1159 graphics optional barcode_0.98+debian-9.1.dsc 03685b94bcf6ee688a764aa355ac6b2c 8436 graphics optional barcode_0.98+debian-9.1.diff.gz 2da9ba79e7dae453ef89cdaa7f18c298 58004 graphics optional barcode_0.98+debian-9.1_amd64.deb 35b68fbd85319e6c4fec8618d2c2f2aa 12656 debug extra barcode-dbg_0.98+debian-9.1_amd64.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1 iEYEARECAAYFAlRE0rIACgkQUCgnLz/SlGgb/gCgxTTe5ixGx53z8wC5Qowr/EyX aAgAnRd0fS1dglPDbS4wQbCseKR+z02l =PoNN -END PGP SIGNATUREEnd Message---
Bug#764318: don't see any way out of the libjpeg issue :( ?
On Wed, Oct 22, 2014 at 02:22:51PM +0530, shirish शिरीष wrote:
$ sudo aptitude install libjpeg8 libjpeg8-dev libdirectfb-dev
The following NEW packages will be installed:
libjpeg-dev{ab} libjpeg62-turbo-dev{ab}
The following packages will be upgraded:
libjpeg8 libjpeg8-dev{b}
2 packages upgraded, 2 newly installed, 0 to remove and 3 not upgraded.
Need to get 505 kB/841 kB of archives. After unpacking 2,879 kB will be used.
The following packages have unmet dependencies:
libjpeg8-dev : Conflicts: libjpeg62-dev but it is not going to be installed.
libjpeg62-turbo-dev : Conflicts: libjpeg8-dev but 8d1-2 is to be installed.
libjpeg-dev : Conflicts: libjpeg8-dev but 8d1-2 is to be installed.
The following actions will resolve these dependencies:
Remove the following packages:
1) fp-units-multimedia-2.6.4
2) fpc
3) fpc-2.6.4
4) liballegro-image5-dev
5) libdirectfb-dev
6) libgd-dev
7) libsdl-gfx1.2-dev
8) libsdl-image1.2-dev
9) libsdl-mixer1.2-dev
10) libsdl-net1.2-dev
11) libsdl-pango-dev
12) libsdl-sge-dev
13) libsdl-sound1.2-dev
14) libsdl-stretch-dev
15) libsdl-ttf2.0-dev
16) libsdl1.2-dev
17) libtiff5-dev
Keep the following packages at their current version:
18) libjpeg-dev [Not Installed]
19) libjpeg62-turbo-dev [Not Installed]
Leave the following dependencies unresolved:
20) liballegro5-dev recommends liballegro-image5-dev
21) fp-units-castle-game-engine recommends fpc
22) fp-units-gfx-2.6.4 recommends libgd-dev
23) lazarus-1.2.4 recommends fpc
24) lazarus-ide-1.2.4 recommends fpc
25) lazarus-ide-gtk2-1.2.4 recommends fpc
26) lazarus-ide-qt4-1.2.4 recommends fpc
27) lcl-1.2.4 recommends fpc
28) lcl-gtk2-1.2.4 recommends fpc
29) lcl-nogui-1.2.4 recommends fpc
30) lcl-units-1.2.4 recommends fpc
Accept this solution? [Y/n/q/?] q
Abandoning all efforts to resolve these dependencies.
Abort.
As can be seen lot of packages will be removed if I go down this path .
Looking for guidance.
I suggest you first do either
apt-get install libjpeg-dev
or
apt-get remove libjpeg8-dev
and then proceed.
Cheers,
--
Bill. ballo...@debian.org
Imagine a large red swirl here.
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#760476: gnutls28 3.3.8-3
On Wed, Oct 22, 2014 at 10:39 AM, Nikos Mavrogiannopoulos n.mavrogiannopou...@gmail.com wrote: Thanks, it seems I am correct. Cups closes all open descriptors. I don't know what I can do in gnutls to fix that. That looks like that should be addressed in cups. The best that I can think of is having a function to check whether a particular fd is in use by gnutls (and that could be ported to 3.3.10 if it is to be used by cups). I don't see how that can be solved transparently to an application. https://gitorious.org/gnutls/gnutls/commit/2c12530bacc89485e807ec18ae455f4e190b383f regards, Nikos -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#764318: libjpeg-progs still needs conflict with libjpeg-turbo-progs
Control: clone -1 -2 Control: reassign -2 libjpeg-turbo-progs/1:1.3.1-3 Control: fixed -2 libjpeg-turbo-progs/1:1.3.1-6 Control: reassign -1 libjpeg-progs/1:9a-2 It looks like it's necessary for the new libjpeg-progs to include a conflict with libjpeg-turbo-progs, since at the moment APT tries to install them in the wrong order. On my system at the moment: wraith:/home/bjh21# dpkg -l 'libjpeg*progs' Desired=Unknown/Install/Remove/Purge/Hold | Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend |/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad) ||/ Name Version Architecture Description +++-==---= ii libjpeg-progs 1:1.3.1-3all Programs for manipulating JPEG fi ii libjpeg-turbo- 1:1.3.1-3i386 Programs for manipulating JPEG fi Both libjpeg-progs 1:9a-2 and libjpeg-turbo-progs 1:1.3.1-6 are available to APT, but it chooses to upgrade libjpeg-progs and keep back libjpeg-turbo-progs: wraith:/home/bjh21# apt-get dist-upgrade Reading package lists... Done Building dependency tree Reading state information... Done Calculating upgrade... Done The following packages have been kept back: libjpeg-turbo-progs The following packages will be upgraded: libjpeg-progs 1 upgraded, 0 newly installed, 0 to remove and 1 not upgraded. 65 not fully installed or removed. Need to get 0 B/82.6 kB of archives. After this operation, 121 kB of additional disk space will be used. Do you want to continue? [Y/n] (Reading database ... 246510 files and directories currently installed.) Preparing to unpack .../libjpeg-progs_1%3a9a-2_i386.deb ... Unpacking libjpeg-progs (1:9a-2) over (1:1.3.1-3) ... dpkg: error processing archive /var/cache/apt/archives/libjpeg-progs_1%3a9a-2_i386.deb (--unpack): trying to overwrite '/usr/share/man/man1/exifautotran.1.gz', which is also in package libjpeg-turbo-progs 1:1.3.1-3 Errors were encountered while processing: /var/cache/apt/archives/libjpeg-progs_1%3a9a-2_i386.deb E: Sub-process /usr/bin/dpkg returned an error code (1) APT needs to be told that the new libjpeg-progs can't coexist with libjpeg-turbo-progs 1:1.3.1-3, which I think requires adding a Conflicts: header to libjpeg-progs (or use of alternatives). I've tried to re-organise this bug report to reflect the fact that changes were needed to both packages. I've reassigned 764318 back to libjpeg-progs alone, while there's a new clone to represent the (fixed) lack of a Conflicts: header in libjpeg-turbo-progs. According to the BTS documentation, it's only appropriate to have a bug assigned to two packages if it can be fixed by a change to either one of those packages. In this case, it appears that changes to both packages were required. -- Ben Harris, University of Cambridge Information Services. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed (with 4 errors): libjpeg-progs still needs conflict with libjpeg-turbo-progs
Processing control commands: clone -1 -2 Bug #764318 [libjpeg-progs,libjpeg-turbo-progs] libjpeg-progs: trying to overwrite '/usr/share/man/man1/djpeg.1.gz', also in libjpeg-turbo-progs Bug #764322 [libjpeg-progs,libjpeg-turbo-progs] libjpeg-progs: trying to overwrite '/usr/share/man/man1/djpeg.1.gz', also in libjpeg-turbo-progs Bug #765667 [libjpeg-progs,libjpeg-turbo-progs] [libjpeg-progs] Conflicts with libjpeg-turbo-progs Bug #765790 [libjpeg-progs,libjpeg-turbo-progs] libjpeg-progs: It can not overwrite a manpage Failed to clone 764318: Bug is marked as being merged with others. Use an existing clone. reassign -2 libjpeg-turbo-progs/1:1.3.1-3 Unknown command or malformed arguments to command. fixed -2 libjpeg-turbo-progs/1:1.3.1-6 Failed to add fixed on -2: The 'bug' parameter (-2) to Debbugs::Control::set_fixed did not pass regex check reassign -1 libjpeg-progs/1:9a-2 Unknown command or malformed arguments to command. -- 764318: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=764318 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#764318: libjpeg-progs still needs conflict with libjpeg-turbo-progs
On Wed, Oct 22, 2014 at 11:12:24AM +0100, Ben Harris wrote: Control: clone -1 -2 Control: reassign -2 libjpeg-turbo-progs/1:1.3.1-3 Control: fixed -2 libjpeg-turbo-progs/1:1.3.1-6 Control: reassign -1 libjpeg-progs/1:9a-2 It looks like it's necessary for the new libjpeg-progs to include a conflict with libjpeg-turbo-progs, since at the moment APT tries to install them in the wrong order. On my system at the moment: Both libjpeg-progs 1:9a-2 and libjpeg-turbo-progs 1:1.3.1-6 are available to APT, but it chooses to upgrade libjpeg-progs and keep back libjpeg-turbo-progs: Hello Ben, since the broken libjpeg-turbo-progs/1:1.3.1-3 was never part of a stable release, this is not strictly necessary: it does not break the wheezy to jessie upgrade. Just remove it before perfomring the upgrade. Since we are very close to the freeze, I would rather dispense with uploading a work around for the libjpeg-turbo-progs/1:1.3.1-3 breakage. Cheers, -- Bill. ballo...@debian.org Imagine a large red swirl here. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: Well, that didn't work
Processing commands for cont...@bugs.debian.org: # This bug looks like it applies separately to libjpeg-progs and # libjpeg-turbo-progs. Unmerge the clone that was created for # libjpeg-turbo-progs and assign each bug to only one package. unmerge 764322 Bug #764322 [libjpeg-progs,libjpeg-turbo-progs] libjpeg-progs: trying to overwrite '/usr/share/man/man1/djpeg.1.gz', also in libjpeg-turbo-progs Bug #764318 [libjpeg-progs,libjpeg-turbo-progs] libjpeg-progs: trying to overwrite '/usr/share/man/man1/djpeg.1.gz', also in libjpeg-turbo-progs Bug #765667 [libjpeg-progs,libjpeg-turbo-progs] [libjpeg-progs] Conflicts with libjpeg-turbo-progs Bug #765790 [libjpeg-progs,libjpeg-turbo-progs] libjpeg-progs: It can not overwrite a manpage Disconnected #764322 from all other report(s). reassign 764322 libjpeg-turbo-progs 1:1.3.1-3 Bug #764322 [libjpeg-progs,libjpeg-turbo-progs] libjpeg-progs: trying to overwrite '/usr/share/man/man1/djpeg.1.gz', also in libjpeg-turbo-progs Bug reassigned from package 'libjpeg-progs,libjpeg-turbo-progs' to 'libjpeg-turbo-progs'. No longer marked as found in versions libjpeg-turbo-progs/1:1.3.1-3 and libjpeg-progs/1:9a-2. No longer marked as fixed in versions libjpeg-turbo-progs/1:1.3.1-6. Bug #764322 [libjpeg-turbo-progs] libjpeg-progs: trying to overwrite '/usr/share/man/man1/djpeg.1.gz', also in libjpeg-turbo-progs Marked as found in versions libjpeg-turbo/1:1.3.1-3. fixed 764322 1:1.3.1-6 Bug #764322 [libjpeg-turbo-progs] libjpeg-progs: trying to overwrite '/usr/share/man/man1/djpeg.1.gz', also in libjpeg-turbo-progs Marked as fixed in versions libjpeg-turbo/1:1.3.1-6. reassign 764318 libjpeg-progs 1:9a-2 Bug #764318 [libjpeg-progs,libjpeg-turbo-progs] libjpeg-progs: trying to overwrite '/usr/share/man/man1/djpeg.1.gz', also in libjpeg-turbo-progs Bug #765667 [libjpeg-progs,libjpeg-turbo-progs] [libjpeg-progs] Conflicts with libjpeg-turbo-progs Bug #765790 [libjpeg-progs,libjpeg-turbo-progs] libjpeg-progs: It can not overwrite a manpage Bug reassigned from package 'libjpeg-progs,libjpeg-turbo-progs' to 'libjpeg-progs'. Bug reassigned from package 'libjpeg-progs,libjpeg-turbo-progs' to 'libjpeg-progs'. Bug reassigned from package 'libjpeg-progs,libjpeg-turbo-progs' to 'libjpeg-progs'. No longer marked as found in versions libjpeg-turbo-progs/1:1.3.1-3 and libjpeg-progs/1:9a-2. No longer marked as found in versions libjpeg-turbo-progs/1:1.3.1-3 and libjpeg-progs/1:9a-2. No longer marked as found in versions libjpeg-turbo-progs/1:1.3.1-3 and libjpeg-progs/1:9a-2. No longer marked as fixed in versions libjpeg-turbo-progs/1:1.3.1-6. No longer marked as fixed in versions libjpeg-turbo-progs/1:1.3.1-6. No longer marked as fixed in versions libjpeg-turbo-progs/1:1.3.1-6. Bug #764318 [libjpeg-progs] libjpeg-progs: trying to overwrite '/usr/share/man/man1/djpeg.1.gz', also in libjpeg-turbo-progs Bug #765667 [libjpeg-progs] [libjpeg-progs] Conflicts with libjpeg-turbo-progs Bug #765790 [libjpeg-progs] libjpeg-progs: It can not overwrite a manpage Marked as found in versions libjpeg9/1:9a-2. Marked as found in versions libjpeg9/1:9a-2. Marked as found in versions libjpeg9/1:9a-2. -- Stopping processing here. Please contact me if you need assistance. -- 764318: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=764318 764322: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=764322 765667: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=765667 765790: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=765790 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#764318: libjpeg-progs still needs conflict with libjpeg-turbo-progs
On Wed, 22 Oct 2014, Bill Allombert wrote: On Wed, Oct 22, 2014 at 11:12:24AM +0100, Ben Harris wrote: Control: clone -1 -2 Control: reassign -2 libjpeg-turbo-progs/1:1.3.1-3 Control: fixed -2 libjpeg-turbo-progs/1:1.3.1-6 Control: reassign -1 libjpeg-progs/1:9a-2 It looks like it's necessary for the new libjpeg-progs to include a conflict with libjpeg-turbo-progs, since at the moment APT tries to install them in the wrong order. On my system at the moment: Both libjpeg-progs 1:9a-2 and libjpeg-turbo-progs 1:1.3.1-6 are available to APT, but it chooses to upgrade libjpeg-progs and keep back libjpeg-turbo-progs: Hello Ben, since the broken libjpeg-turbo-progs/1:1.3.1-3 was never part of a stable release, this is not strictly necessary: it does not break the wheezy to jessie upgrade. Just remove it before perfomring the upgrade. Since we are very close to the freeze, I would rather dispense with uploading a work around for the libjpeg-turbo-progs/1:1.3.1-3 breakage. OK. Now I have to work out how to undo what I just did to the BTS... -- Ben Harris, University of Cambridge Information Services. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: closing 764322
Processing commands for cont...@bugs.debian.org: close 764322 Bug #764322 [libjpeg-turbo-progs] libjpeg-progs: trying to overwrite '/usr/share/man/man1/djpeg.1.gz', also in libjpeg-turbo-progs Marked Bug as done thanks Stopping processing here. Please contact me if you need assistance. -- 764322: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=764322 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: I've been persuaded I was wrong
Processing commands for cont...@bugs.debian.org:
# This will not be worked around in libjpeg-progs
reassign 764318 libjpeg-turbo-progs
Bug #764318 [libjpeg-progs] libjpeg-progs: trying to overwrite
'/usr/share/man/man1/djpeg.1.gz', also in libjpeg-turbo-progs
Bug #765667 [libjpeg-progs] [libjpeg-progs] Conflicts with libjpeg-turbo-progs
Bug #765790 [libjpeg-progs] libjpeg-progs: It can not overwrite a manpage
Bug reassigned from package 'libjpeg-progs' to 'libjpeg-turbo-progs'.
Bug reassigned from package 'libjpeg-progs' to 'libjpeg-turbo-progs'.
Bug reassigned from package 'libjpeg-progs' to 'libjpeg-turbo-progs'.
No longer marked as found in versions libjpeg9/1:9a-2.
No longer marked as found in versions libjpeg9/1:9a-2.
No longer marked as found in versions libjpeg9/1:9a-2.
Ignoring request to alter fixed versions of bug #764318 to the same values
previously set
Ignoring request to alter fixed versions of bug #765667 to the same values
previously set
Ignoring request to alter fixed versions of bug #765790 to the same values
previously set
forcemerge 764322 764318
Bug #764322 {Done: Ondřej Surý ond...@debian.org} [libjpeg-turbo-progs]
libjpeg-progs: trying to overwrite '/usr/share/man/man1/djpeg.1.gz', also in
libjpeg-turbo-progs
Bug #765667 [libjpeg-turbo-progs] [libjpeg-progs] Conflicts with
libjpeg-turbo-progs
Marked Bug as done
Marked Bug as done
Marked Bug as done
Marked as fixed in versions libjpeg-turbo/1:1.3.1-6.
Marked as fixed in versions libjpeg-turbo/1:1.3.1-6.
Marked as fixed in versions libjpeg-turbo/1:1.3.1-6.
Marked as found in versions libjpeg-turbo/1:1.3.1-3.
Marked as found in versions libjpeg-turbo/1:1.3.1-3.
Marked as found in versions libjpeg-turbo/1:1.3.1-3.
Bug #764318 {Done: Ondřej Surý ond...@debian.org} [libjpeg-turbo-progs]
libjpeg-progs: trying to overwrite '/usr/share/man/man1/djpeg.1.gz', also in
libjpeg-turbo-progs
Bug #765790 {Done: Ondřej Surý ond...@debian.org} [libjpeg-turbo-progs]
libjpeg-progs: It can not overwrite a manpage
Merged 764318 764322 765667 765790
affects 764318 +libjpeg-progs
Bug #764318 {Done: Ondřej Surý ond...@debian.org} [libjpeg-turbo-progs]
libjpeg-progs: trying to overwrite '/usr/share/man/man1/djpeg.1.gz', also in
libjpeg-turbo-progs
Bug #764322 {Done: Ondřej Surý ond...@debian.org} [libjpeg-turbo-progs]
libjpeg-progs: trying to overwrite '/usr/share/man/man1/djpeg.1.gz', also in
libjpeg-turbo-progs
Bug #765667 {Done: Ondřej Surý ond...@debian.org} [libjpeg-turbo-progs]
[libjpeg-progs] Conflicts with libjpeg-turbo-progs
Bug #765790 {Done: Ondřej Surý ond...@debian.org} [libjpeg-turbo-progs]
libjpeg-progs: It can not overwrite a manpage
Added indication that 764318 affects libjpeg-progs
Added indication that 764322 affects libjpeg-progs
Added indication that 765667 affects libjpeg-progs
Added indication that 765790 affects libjpeg-progs
--
Stopping processing here.
Please contact me if you need assistance.
--
764318: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=764318
764322: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=764322
765667: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=765667
765790: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=765790
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#766322: circular dependencies causes dpkg --configure -a to go into a tight loop
severity 766322 serious merge 766322 766242 thanks Hi, This seems to be the same than #766242. Adjusting severity and merging. Cheers, -- Clément (nodens) -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: Re: circular dependencies causes dpkg --configure -a to go into a tight loop
Processing commands for cont...@bugs.debian.org: severity 766322 serious Bug #766322 [dpkg] circular dependencies causes dpkg --configure -a to go into a tight loop Severity set to 'serious' from 'critical' merge 766322 766242 Bug #766322 [dpkg] circular dependencies causes dpkg --configure -a to go into a tight loop Bug #766242 [dpkg] dpkg: consumes all available RAM and crashes, during configure phase Merged 766242 766322 thanks Stopping processing here. Please contact me if you need assistance. -- 766242: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=766242 766322: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=766322 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#756155: How to fix ckeditor
Hello, ckeditor from testing/sid is currently not working. It seems that the build failed to include all the necessary JS snipsets. I see several options here: 1. Go back to the older working version (3.7 I think). This has the major drawback of maintaining this security-wise during jessie lifetime. 2. Use the not-minified and not-closur-ified version. This will be slow 3. Package ckbuilder, and use it. This is a big work, and probably won't pass NEW before the freeze -10days 4. Fix the current build to behave more like ckbuilder... Any help is welcome! 5. Use the already minified version from upstream. This is probably not DFSG-friendly IMO, 1 and 5 should be avoided and I don't know how to take option 4. I will try to go option 2, and upload to some delayed queue so that it doesn't enter in sid before 2014-10-26. I have tried option 3 without success from now (some jars in uptsream are not in debian already, ...) Thoughts ? -- Mathieu -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#766231: marked as done (sympow: FTBFS - floating-point precision test/check failure)
Your message dated Wed, 22 Oct 2014 12:05:09 + with message-id e1xguf7-0003og...@franck.debian.org and subject line Bug#766231: fixed in sympow 1.023-2 has caused the Debian Bug report #766231, regarding sympow: FTBFS - floating-point precision test/check failure 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.) -- 766231: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=766231 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: sympow Version: 1.023-1 Severity: serious Justification: fails to build from source It appears that the floating-point test/check machinery fails for some architectures: this test/check must be harddened. Thanks, Jerome -- System Information: Debian Release: Wheezy* APT prefers stable-updates APT policy: (990, 'stable-updates'), (990, 'stable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.13.10-amd64-mbp62 (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 Versions of packages sympow depends on: ii libc62.13-38+deb7u6 ii pari-gp 2.7.2-1 ii sympow-data 1.023-1 sympow recommends no packages. sympow suggests no packages. -- no debconf information ---End Message--- ---BeginMessage--- Source: sympow Source-Version: 1.023-2 We believe that the bug you reported is fixed in the latest version of sympow, 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 766...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Jerome Benoit calcu...@rezozer.net (supplier of updated sympow 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, 22 Oct 2014 02:06:21 + Source: sympow Binary: sympow sympow-data Architecture: source amd64 all Version: 1.023-2 Distribution: unstable Urgency: medium Maintainer: Debian Science Maintainers debian-science-maintain...@lists.alioth.debian.org Changed-By: Jerome Benoit calcu...@rezozer.net Description: sympow - mathematical program for SYMmetric POWer elliptic curve L-functio sympow-data - mathematical program for SYMmetric POWer elliptic curve L-functio Closes: 766231 Changes: sympow (1.023-2) unstable; urgency=medium . * Debianization: - debian/control: - Homepage field, refresh; - debian/patches/: - floating-point rounding precision setup, harden (Closes: #766231); Checksums-Sha1: 1ac0fe25dacee688215d141c1c0af4c309bcc6e9 1681 sympow_1.023-2.dsc 42e48b4f41358e4180c73b9f417f53e9a1f15242 23836 sympow_1.023-2.debian.tar.xz e6d8a1933df8d826142afaf27f01ed10f2c5b62d 107314 sympow_1.023-2_amd64.deb c1ee6545f46e62aaecb37e1b26406871f6afa481 8491796 sympow-data_1.023-2_all.deb Checksums-Sha256: 839f98c89c0c4ead57fd50c43c794911e38c160b41f3e5da944d9c3929480f8b 1681 sympow_1.023-2.dsc e9e9cbf9ebf3529688be49bf25e84af2db9e43aa8779f08e199646c914918215 23836 sympow_1.023-2.debian.tar.xz cc9e285e37d0cd26f748af874dc34b8ba779bd9bc2c76123bd6ef75ebefdc070 107314 sympow_1.023-2_amd64.deb 1ebb678cb0fa03ce03bbaa4d073ad54f9b8ce4c1bdab5942424decfe8e17eee4 8491796 sympow-data_1.023-2_all.deb Files: 4f9379fa38336b4c68fc08dc6898baa0 1681 math optional sympow_1.023-2.dsc 911ed46ccf5d00dfaa9300efe7c0c898 23836 math optional sympow_1.023-2.debian.tar.xz 169150ee2c44856a8d7ed50d692cbe55 107314 math optional sympow_1.023-2_amd64.deb e513405e4ecf98836ba64c9d39d456ea 8491796 math optional sympow-data_1.023-2_all.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1 iQEcBAEBCAAGBQJUR5tdAAoJEImvgrc5zSF6LcoIAJ9YN8ZvhOMCZqxOsLbeLf/s XF7jq2PBbCvHRsMpSNs/HIHuMLnn2WfF/7gEJC2fCa3y96UU1SGhCH8qaWMpNV8v lBQKTAqOXBgRjKHoZalr4WwGP6+VFKLmxC3DEuLE5ZW89ywXKP91UHGnduFN72zC ghvdvvBmfj1gHKPCmPkvh87etQgi+lUJxccdENNDxt8rW03JsjRkbZEiefT/5jGH RqIXbaEoPkZtHJylgSHZV99/kSS6RPU848JJ7b0Fwg2cVCI5wvdghcK/jjWWmqbP z1Lry4uUYl8955dTZXxkY8mGDAEfdvPAd9n3MPjJS3rL1mKOpY/tCWvxlu7tyoo= =JiVo -END PGP SIGNATUREEnd Message---
Bug#717129: marked as done (Hue: VIDIOC_G_CTRL failed: Invalid argument)
Your message dated Wed, 22 Oct 2014 12:08:28 + with message-id e1xguik-0004ro...@franck.debian.org and subject line Bug#766046: Removed package(s) from unstable has caused the Debian Bug report #717129, regarding Hue: VIDIOC_G_CTRL failed: Invalid argument 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.) -- 717129: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=717129 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: setpwc Version: 1.2-3.1 Severity: important Dear Maintainer, setpwc gives warning, error and wrong information on my Wheezy 64 bit system: root@MultiServer:~# uname -a Linux MultiServer 3.2.0-2-amd64 #1 SMP Sat May 12 23:08:28 UTC 2012 x86_64 GNU/Linux root@MultiServer:~# cat /sys/module/pwc/version 10.0.15 root@MultiServer:~# setpwc -p setpwc v1.2, (C) 2003-2006 by folk...@vanheusden.com Error while doing ioctl VIDIOCGCAP: Invalid argument Current device: Warning: this might not be a Philips compatible webcam! VIDIOCPWCPROBE returns: Philips 740 webcam - 740 Serial number: 0169C5588301 Error while doing ioctl VIDIOCGWIN: Invalid argument Resolution (x, y): 1, 0 Offset: 0, 1 Error while doing ioctl VIDIOCGPICT: Invalid argument Brightness: 12840 Hue: 64 Colour: 0 Contrast: 0 Whiteness: 0 Palette: Unknown! (0) Compression preference: 1 Automatic gain control: -1 Whitebalance mode: auto Blinking of LED is not supported by the combination of your webcam and the driver. Sharpness: 33287 Backlight compensation mode: off Anti-flicker mode: on Noise reduction mode: 1 Pan/tilt range is not supported by the combination of your webcam and the driver. Get pan/tilt position is not supported by the combination of your webcam and the driver. The same version of setpwc works correctly on Lenny 32 bit system: # uname -a Linux HomeServer 2.6.26-2-686 #1 SMP Wed Feb 10 08:59:21 UTC 2010 i686 GNU/Linux # cat /sys/module/pwc/version 10.0.13 # setpwc -p setpwc v1.2, (C) 2003-2006 by folk...@vanheusden.com Current device: Philips 740 webcam VIDIOCPWCPROBE returns: Philips 740 webcam - 740 Serial number: 01696B9F0101 Resolution (x, y): 640, 480 Offset: 0, 0 Framerate: 10 Brightness: 32256 Hue: 65535 Colour: 32768 Contrast: 64512 Whiteness: 63488 Palette: YUV 4:2:0 Planar Compression preference: 1 Automatic gain control: -7410 Whitebalance mode: auto Blinking of LED is not supported by the combination of your webcam and the driver. Sharpness: -1 Backlight compensation mode: on Anti-flicker mode: off Noise reduction mode: 1 Pan/tilt range is not supported by the combination of your webcam and the driver. Get pan/tilt position is not supported by the combination of your webcam and the driver. The same version of setpwc works correctly on Squeeze 32 bit system: AlarmServer:~# uname -a Linux AlarmServer 2.6.32-5-686 #1 SMP Mon Jan 16 16:04:25 UTC 2012 i686 GNU/Linux AlarmServer:~# cat /sys/module/pwc/version 10.0.13 AlarmServer:~# setpwc -p setpwc v1.2, (C) 2003-2006 by folk...@vanheusden.com Current device: Philips 740 webcam VIDIOCPWCPROBE returns: Philips 740 webcam - 740 Serial number: 0169C5588301 Resolution (x, y): 160, 120 Offset: 0, 0 Framerate: 10 Brightness: 32256 Hue: 65535 Colour: 32768 Contrast: 32768 Whiteness: 43008 Palette: YUV 4:2:0 Planar Compression preference: 1 Automatic gain control: -2502 Whitebalance mode: auto Blinking of LED is not supported by the combination of your webcam and the driver. Sharpness: -1 Backlight compensation mode: on Anti-flicker mode: off Noise reduction mode: 1 Pan/tilt range is not supported by the combination of your webcam and the driver. Get pan/tilt position is not supported by the combination of your webcam and the driver. In all the above 3 tests I used the same type of Philips USB camera. I suspect it could be a pwc driver issue, but I could not verify it. The issue could relate to version 10.0.15 of pwc driver or only to the amd64 build. Please check the issue and apply correction! Please contact me if you need more information. Regards, Laszlo BORTEL -- System Information: Debian Release: wheezy/sid APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 3.2.0-2-amd64 (SMP w/2 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages setpwc depends on: ii libc6 2.13-32 setpwc recommends no packages. setpwc suggests no packages. -- no debconf information ---End Message--- ---BeginMessage--- Version: 1.3-1+rm Dear submitter, as the package setpwc has just been removed from the
Bug#765669: marked as done (libavifile-0.7c2: Uninstallable (not BinNMU-safe))
Your message dated Wed, 22 Oct 2014 12:19:13 +
with message-id e1xgusj-au...@franck.debian.org
and subject line Bug#765669: fixed in avifile 1:0.7.48~20090503.ds-16.1
has caused the Debian Bug report #765669,
regarding libavifile-0.7c2: Uninstallable (not BinNMU-safe)
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.)
--
765669: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=765669
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
---BeginMessage---
Source: avifile
Version: 1:0.7.48~20090503.ds-16
Severity: serious
Your package is still not binNMU safe:
onscripter build-depends on:
- libavifile-0.7-dev
libavifile-0.7-dev depends on:
- libavifile-0.7c2 (= 1:0.7.48~20090503.ds-16+b2)
libavifile-0.7c2 depends on missing:
- libavifile-0.7-common (= 1:0.7.48~20090503.ds-16+b2)
This is making various packages unbuildable (e.g. onscripter or vxl).
Emilio
---End Message---
---BeginMessage---
Source: avifile
Source-Version: 1:0.7.48~20090503.ds-16.1
We believe that the bug you reported is fixed in the latest version of
avifile, which is due to be installed in the Debian FTP archive.
A summary of the changes between this version and the previous one is
attached.
Thank you for reporting the bug, which will now be closed. If you
have further comments please address them to 765...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Ondřej Surý ond...@debian.org (supplier of updated avifile 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, 20 Oct 2014 13:27:50 +0200
Source: avifile
Binary: libavifile-0.7-common libavifile-0.7c2 libavifile-0.7-dev
libavifile-0.7-bin
Architecture: source all
Version: 1:0.7.48~20090503.ds-16.1
Distribution: unstable
Urgency: medium
Maintainer: Ying-Chun Liu (PaulLiu) paul...@debian.org
Changed-By: Ondřej Surý ond...@debian.org
Description:
libavifile-0.7-bin - toolkit for libavifile
libavifile-0.7-common - toolkit for libavifile
libavifile-0.7-dev - development header files for libavifile
libavifile-0.7c2 - shared libraries for AVI read/writing
Closes: 765669
Changes:
avifile (1:0.7.48~20090503.ds-16.1) unstable; urgency=medium
.
* Make the package binNMUable (Closes: #765669)
+ Use = ${source:Version} instead of = ${source:Version}
+ Remove the dh_linkdoc any-all relation that doesn't work and add
maintscript(s) to change symlink to docs
Checksums-Sha1:
37b818e38e4585abfaa318dfe5392b98a352df30 2383
avifile_0.7.48~20090503.ds-16.1.dsc
a96a36708b6bad851962568b7f6b13e25477eeef 28360
avifile_0.7.48~20090503.ds-16.1.debian.tar.xz
cc1b57bda63464f8841b891a9b7cdf7f7cad111d 83862
libavifile-0.7-common_0.7.48~20090503.ds-16.1_all.deb
Checksums-Sha256:
d9eea60edca61c61aa466c51e8d6f337e01848e846e587246089328189669444 2383
avifile_0.7.48~20090503.ds-16.1.dsc
976616105443b25d02cb09199ae9a24ad3349970dfe26c6bc8e79744b9c822be 28360
avifile_0.7.48~20090503.ds-16.1.debian.tar.xz
d08134928210c9778efb132007a5f8d9d7ea8a1115898f564271f2955539938a 83862
libavifile-0.7-common_0.7.48~20090503.ds-16.1_all.deb
Files:
d37107a74005bbe80955f2ad1b8bbc03 2383 libs optional
avifile_0.7.48~20090503.ds-16.1.dsc
522532cf1baa9aa26db194ce7f60780e 28360 libs optional
avifile_0.7.48~20090503.ds-16.1.debian.tar.xz
121d55d3ac9c5ff92984170b8c88e7f3 83862 misc optional
libavifile-0.7-common_0.7.48~20090503.ds-16.1_all.deb
-BEGIN PGP SIGNATURE-
Version: GnuPG v1
iQJ8BAEBCgBmBQJURPRZXxSAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w
ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXQzMEI5MzNEODBGQ0UzRDk4MUEyRDM4RkIw
Qzk5QjcwRUY0RkNCQjA3AAoJEAyZtw70/LsHrzQP/iZLK2TPfRLTZgD3Nffawyuq
9Nr1uVZVWTGclNWNtjt0+spDauF/e1HLI1Vxd4/znZhDJ7WfexHrCd2IBiWaCDVC
ZTV521ucbOT9k1UqShzIYhZ3faoh2sIbCfE0ZdpHVXZEsstfUHM1FqZ3TEDfJHbl
QpI8uPzaPAUZGlDgzFXSCPSTEDMqaS0cAWCyJ6Hd3/YVJQ50s8E3nDFZ5HZ7IH+0
TnzujbKwhCeoYB3r+S3fsaRESoO9ZkpJzifhwW10NL7wx9KQz7Gw1yKv7CyiOJlf
QAjV/eQlA0ssszf5sOVKZZj8T8mMGAuv27/N4w0kCkKG67WYE5AThtMuCLguUi93
oyhbAT7q+4/BnDOf9BUuleEy8jELy6lkabvr0+gc6103TmrhAbwjeMaOn5dTX2Gd
bFHVayZDbyaiSr4A+CMGcw0zfZgSrAOhzeuyPJBgQF1YE1OB9k0Muf+DpVpU+F8W
rcZroxxn0nVSvGiLSuMqvB000jTXtojp+Adll09MJi75tvs7XSjOS5zp8VDE8cIt
v17sGeokBFJ8uhEkV92RUrg2uPzRcY32MHd0VpbkIfoIaO7bExN0cLVki2I515Zc
Y/WSHLmkqpU6XC1rP/grQcbllBXMUEgE2IkQuv8vbWnxrcs81EBHO08C4qGHYxO3
eoE4UI2I8FESxYCu12Iy
=Md2G
-END PGP SIGNATUREEnd Message---
Bug#765148: marked as done (libavifile-0.7c2: Uninstallable (not BinNMU-safe))
Your message dated Wed, 22 Oct 2014 12:19:13 +
with message-id e1xgusj-au...@franck.debian.org
and subject line Bug#765669: fixed in avifile 1:0.7.48~20090503.ds-16.1
has caused the Debian Bug report #765669,
regarding libavifile-0.7c2: Uninstallable (not BinNMU-safe)
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.)
--
765669: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=765669
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
---BeginMessage---
Source: cynthiune.app
Version: 0.9.5-14
Severity: serious
Tags: jessie sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20141012 qa-ftbfs
Justification: FTBFS on amd64
Hi,
During a rebuild of all packages in sid, your package failed to build on
amd64.
Relevant part (hopefully):
┌──┐
│ Install cynthiune.app build dependencies (apt-based resolver)
│
└──┘
Installing build dependencies
Reading package lists...
Building dependency tree...
Reading state information...
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:
The following packages have unmet dependencies:
sbuild-build-depends-cynthiune.app-dummy : Depends: libavifile-0.7-dev (=
1:0.7.48~20090503.ds) but it is not going to be installed
E: Unable to correct problems, you have held broken packages.
apt-get failed.
The full build log is available from:
http://aws-logs.debian.net/ftbfs-logs/2014/10/12/cynthiune.app_0.9.5-14_unstable.log
A list of current common problems and possible solutions is available at
http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!
About the archive rebuild: The rebuild was done on EC2 VM instances from
Amazon Web Services, using a clean, minimal and up-to-date chroot. Every
failed build was retried once to eliminate random failures.
---End Message---
---BeginMessage---
Source: avifile
Source-Version: 1:0.7.48~20090503.ds-16.1
We believe that the bug you reported is fixed in the latest version of
avifile, which is due to be installed in the Debian FTP archive.
A summary of the changes between this version and the previous one is
attached.
Thank you for reporting the bug, which will now be closed. If you
have further comments please address them to 765...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Ondřej Surý ond...@debian.org (supplier of updated avifile 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, 20 Oct 2014 13:27:50 +0200
Source: avifile
Binary: libavifile-0.7-common libavifile-0.7c2 libavifile-0.7-dev
libavifile-0.7-bin
Architecture: source all
Version: 1:0.7.48~20090503.ds-16.1
Distribution: unstable
Urgency: medium
Maintainer: Ying-Chun Liu (PaulLiu) paul...@debian.org
Changed-By: Ondřej Surý ond...@debian.org
Description:
libavifile-0.7-bin - toolkit for libavifile
libavifile-0.7-common - toolkit for libavifile
libavifile-0.7-dev - development header files for libavifile
libavifile-0.7c2 - shared libraries for AVI read/writing
Closes: 765669
Changes:
avifile (1:0.7.48~20090503.ds-16.1) unstable; urgency=medium
.
* Make the package binNMUable (Closes: #765669)
+ Use = ${source:Version} instead of = ${source:Version}
+ Remove the dh_linkdoc any-all relation that doesn't work and add
maintscript(s) to change symlink to docs
Checksums-Sha1:
37b818e38e4585abfaa318dfe5392b98a352df30 2383
avifile_0.7.48~20090503.ds-16.1.dsc
a96a36708b6bad851962568b7f6b13e25477eeef 28360
avifile_0.7.48~20090503.ds-16.1.debian.tar.xz
cc1b57bda63464f8841b891a9b7cdf7f7cad111d 83862
libavifile-0.7-common_0.7.48~20090503.ds-16.1_all.deb
Checksums-Sha256:
d9eea60edca61c61aa466c51e8d6f337e01848e846e587246089328189669444 2383
avifile_0.7.48~20090503.ds-16.1.dsc
976616105443b25d02cb09199ae9a24ad3349970dfe26c6bc8e79744b9c822be 28360
avifile_0.7.48~20090503.ds-16.1.debian.tar.xz
d08134928210c9778efb132007a5f8d9d7ea8a1115898f564271f2955539938a 83862
Bug#766319: marked as done (libavifile-0.7c2: Uninstallable (not BinNMU-safe))
Your message dated Wed, 22 Oct 2014 12:19:13 +
with message-id e1xgusj-au...@franck.debian.org
and subject line Bug#765669: fixed in avifile 1:0.7.48~20090503.ds-16.1
has caused the Debian Bug report #765669,
regarding libavifile-0.7c2: Uninstallable (not BinNMU-safe)
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.)
--
765669: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=765669
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
---BeginMessage---
Package: libavifile-0.7c2
Version: 1:0.7.48~20090503.ds-16
Severity: serious
Hi,
libavifile-0.7c2 version 0.7.48~20090503.ds-16+b2 is currently
uninstallable as it has been BinNMUed, but seems not BinNMU-safe:
The following packages have unmet dependencies:
libavifile-0.7c2 : Depends: libavifile-0.7-common (=
1:0.7.48~20090503.ds-16+b2) but 1:0.7.48~20090503.ds-16 is to be installed
libavifile-0.7-common is Architecture: all and the dependency on it in
libavifile-0.7c2 should not contain the BinNMU suffix.
# apt-cache policy libavifile-0.7c2 libavifile-0.7-common
libavifile-0.7c2:
Installed: 1:0.7.48~20090503.ds-16
Candidate: 1:0.7.48~20090503.ds-16+b2
Version table:
1:0.7.48~20090503.ds-16+b2 0
500 http://debian.ethz.ch/mirror/debian/ sid/main i386 Packages
*** 1:0.7.48~20090503.ds-16 0
500 http://debian.ethz.ch/mirror/debian/ testing/main i386 Packages
100 /var/lib/dpkg/status
libavifile-0.7-common:
Installed: 1:0.7.48~20090503.ds-16
Candidate: 1:0.7.48~20090503.ds-16
Version table:
*** 1:0.7.48~20090503.ds-16 0
500 http://debian.ethz.ch/mirror/debian/ sid/main i386 Packages
500 http://debian.ethz.ch/mirror/debian/ testing/main i386 Packages
100 /var/lib/dpkg/status
-- System Information:
Debian Release: jessie/sid
APT prefers unstable
APT policy: (990, 'unstable'), (600, 'testing'), (500, 'buildd-unstable'),
(400, 'stable'), (110, 'experimental'), (1, 'buildd-experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 3.17-rc5-amd64 (SMP w/1 CPU core)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
---End Message---
---BeginMessage---
Source: avifile
Source-Version: 1:0.7.48~20090503.ds-16.1
We believe that the bug you reported is fixed in the latest version of
avifile, which is due to be installed in the Debian FTP archive.
A summary of the changes between this version and the previous one is
attached.
Thank you for reporting the bug, which will now be closed. If you
have further comments please address them to 765...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Ondřej Surý ond...@debian.org (supplier of updated avifile 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, 20 Oct 2014 13:27:50 +0200
Source: avifile
Binary: libavifile-0.7-common libavifile-0.7c2 libavifile-0.7-dev
libavifile-0.7-bin
Architecture: source all
Version: 1:0.7.48~20090503.ds-16.1
Distribution: unstable
Urgency: medium
Maintainer: Ying-Chun Liu (PaulLiu) paul...@debian.org
Changed-By: Ondřej Surý ond...@debian.org
Description:
libavifile-0.7-bin - toolkit for libavifile
libavifile-0.7-common - toolkit for libavifile
libavifile-0.7-dev - development header files for libavifile
libavifile-0.7c2 - shared libraries for AVI read/writing
Closes: 765669
Changes:
avifile (1:0.7.48~20090503.ds-16.1) unstable; urgency=medium
.
* Make the package binNMUable (Closes: #765669)
+ Use = ${source:Version} instead of = ${source:Version}
+ Remove the dh_linkdoc any-all relation that doesn't work and add
maintscript(s) to change symlink to docs
Checksums-Sha1:
37b818e38e4585abfaa318dfe5392b98a352df30 2383
avifile_0.7.48~20090503.ds-16.1.dsc
a96a36708b6bad851962568b7f6b13e25477eeef 28360
avifile_0.7.48~20090503.ds-16.1.debian.tar.xz
cc1b57bda63464f8841b891a9b7cdf7f7cad111d 83862
libavifile-0.7-common_0.7.48~20090503.ds-16.1_all.deb
Checksums-Sha256:
d9eea60edca61c61aa466c51e8d6f337e01848e846e587246089328189669444 2383
avifile_0.7.48~20090503.ds-16.1.dsc
976616105443b25d02cb09199ae9a24ad3349970dfe26c6bc8e79744b9c822be 28360
avifile_0.7.48~20090503.ds-16.1.debian.tar.xz
d08134928210c9778efb132007a5f8d9d7ea8a1115898f564271f2955539938a 83862
libavifile-0.7-common_0.7.48~20090503.ds-16.1_all.deb
Files:
Bug#766347: libjpeg-dev: uninstallable: Conflicts: libjpeg62-dev
Package: libjpeg-dev
Version: 1:1.3.1-9
Severity: grave
Justification: renders package unusable
[ odyx@ and debian-wb-team@ x-d-cc, please keep them in the loop? ]
Hi,
spotted by Didier, looking at cups build attempts:
| The following packages have unmet dependencies:
| sbuild-build-depends-cups-dummy : Depends: libjpeg-dev
|Depends: libtiff-dev
| E: Unable to correct problems, you have held broken packages.
tiff didn't change, but libtiff5-dev (providing libtiff-dev) depends on
libjpeg-dev, so there's probably a single issue at play here. Since
libjpeg-turbo was installed a few minutes before that, let's check…
Trying to install libjpeg-dev from buildd-unstable:
| $ sudo apt-get install libjpeg-dev=1:1.3.1-9 libjpeg62-turbo-dev=1:1.3.1-9
libjpeg62-turbo=1:1.3.1-9
[…]
| Some packages could not be installed. This may mean that you have
| requested an impossible situation or if you are using the unstable
| distribution that some required packages have not yet been created
| or been moved out of Incoming.
| The following information may help to resolve the situation:
|
| The following packages have unmet dependencies:
| libjpeg-dev : Conflicts: libjpeg62-dev
Checking:
| Package: libjpeg-dev
| Depends: libjpeg62-turbo-dev (= 1:1.3.1-9)
| Conflicts: libjpeg62-dev, libjpeg7-dev, libjpeg8-dev, libjpeg9-dev
+
| Package: libjpeg62-turbo-dev
| Provides: libjpeg-dev, libjpeg62-dev
= can't work.
I guess the Drop dummy transitional libjpeg62{,-dev,-dbg} packages
part didn't go particularly well.
Mraw,
KiBi.
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#766349: Some times sign with S/MIME failed
Package: kmail Version: 4:4.14.1-1 Severity: critical -- System Information: Debian Release: jessie/sid APT prefers testing-updates APT policy: (500, 'testing-updates'), (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 3.16-2-amd64 (SMP w/6 CPU cores) Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages kmail depends on: ii kde-runtime 4:4.14.1-1+b1 ii kdepim-runtime4:4.14.1-1 ii kdepimlibs-kio-plugins4:4.14.1-1 ii libakonadi-calendar4 4:4.14.1-1 ii libakonadi-contact4 4:4.14.1-1 ii libakonadi-kde4 4:4.14.1-1 ii libakonadi-kmime4 4:4.14.1-1 ii libakonadiprotocolinternals1 1.13.0-2 ii libc6 2.19-11 ii libcalendarsupport4 4:4.14.1-1 ii libfollowupreminder4 4:4.14.1-1 ii libgcc1 1:4.9.1-16 ii libgpgme++2 4:4.14.1-1 ii libgrantlee-core0 0.4.0-2 ii libincidenceeditorsng44:4.14.1-1 ii libkabc4 4:4.14.1-1 ii libkalarmcal2 4:4.14.1-1 ii libkcalcore4 4:4.14.1-1 ii libkcalutils4 4:4.14.1-1 ii libkcmutils4 4:4.14.1-1+b1 ii libkdecore5 4:4.14.1-1+b1 ii libkdepim44:4.14.1-1 ii libkdeui5 4:4.14.1-1+b1 ii libkio5 4:4.14.1-1+b1 ii libkleo4 4:4.14.1-1 ii libkmanagesieve4 4:4.14.1-1 ii libkmime4 4:4.14.1-1 ii libknewstuff3-4 4:4.14.1-1+b1 ii libknotifyconfig4 4:4.14.1-1+b1 ii libkontactinterface4a 4:4.14.1-1 ii libkparts44:4.14.1-1+b1 ii libkpgp4 4:4.14.1-1 ii libkpimidentities44:4.14.1-1 ii libkpimtextedit4 4:4.14.1-1 ii libkpimutils4 4:4.14.1-1 ii libkprintutils4 4:4.14.1-1+b1 ii libksieveui4 4:4.14.1-1 ii libktnef4 4:4.14.1-1 ii libmailcommon44:4.14.1-1 ii libmailimporter4 4:4.14.1-1 ii libmailtransport4 4:4.14.1-1 ii libmessagecomposer4 4:4.14.1-1 ii libmessagecore4 4:4.14.1-1 ii libmessagelist4 4:4.14.1-1 ii libmessageviewer4 4:4.14.1-1 ii libpimcommon4 4:4.14.1-1 ii libqt4-dbus 4:4.8.6+git64-g5dc8b2b+dfsg-2+b1 ii libqt4-network4:4.8.6+git64-g5dc8b2b+dfsg-2+b1 ii libqt4-xml4:4.8.6+git64-g5dc8b2b+dfsg-2+b1 ii libqtcore44:4.8.6+git64-g5dc8b2b+dfsg-2+b1 ii libqtgui4 4:4.8.6+git64-g5dc8b2b+dfsg-2+b1 ii libqtwebkit4 2.3.4.dfsg-2 ii libsendlater4 4:4.14.1-1 ii libsolid4 4:4.14.1-1+b1 ii libstdc++64.9.1-16 ii libtemplateparser44:4.14.1-1 ii perl 5.20.1-1 Versions of packages kmail recommends: ii gnupg-agent 2.0.26-3 ii gnupg22.0.26-3 ii pinentry-gtk2 [pinentry-x11] 0.8.3-2 Versions of packages kmail suggests: ii bogofilter 1.2.4+dfsg1-3 pn clamav | f-prot-installer none ii kaddressbook 4:4.14.1-1 ii kleopatra 4:4.14.1-1 ii procmail 3.22-22 -- 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
Processed: Re: Bug#764287: marked as done (GRUB before 2.02 doesn't support ZFS lz4 compression)
Processing commands for cont...@bugs.debian.org:
# no longer an issue; grub 2.02 migrated to jessie
fixed 764287 partman-zfs/38
Bug #764287 {Done: Christian Perrier bubu...@debian.org} [partman-zfs] GRUB
before 2.02 doesn't support ZFS lz4 compression
Marked as fixed in versions partman-zfs/38.
thanks
Stopping processing here.
Please contact me if you need assistance.
--
764287: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=764287
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#764253: system-config-printer: Creates millions of ppd symlinks
Hi OdyX, On 22.10.2014 11:24, Didier 'OdyX' Raboud wrote: Le mardi, 21 octobre 2014, 20.09:08 Andreas Cadhalpun a écrit : Thus I think there are two bugs here: * cups should not create files with wrong permissions in /etc/cups/ppd Upstream seems to think differently; see http://cups.org/str.php?L4500 and https://bugzilla.redhat.com/show_bug.cgi?id=1150917#c6 I'm therefore planning to add the patch proposed in STR: #4500 to make sure symlinks are only returned when they are readable, this should help right? Yes, this helps a lot, thanks! Now cups copies the ppd file to /tmp instead of creating a symlink. (By the way, the cups test suite hangs in pbuilder, printing endless lines of: Waiting for scheduler to become ready...) * scp-dbus-service should not start an infinite loop creating millions of symlinks in /tmp just because the permissions in /etc/cups/ppd are wrong This should definitively be fixed in system-config-printer anyway. Indeed this should be fixed, because starting an infinite loop is a rather bad failure mode. Best regards, Andreas -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#754692: libqb: sometimes FTBFS: testsuite races
retitle 754692 libqb: sometimes FTBFS: testsuite races user debian-...@lists.debian.org usertags 754692 - kfreebsd thanks Hi, The test failures are not always repeatable on kfreebsd. Different tests can fail each time. The ipc.test failure was also seen on the first build attempt on linux-mipsel: https://buildd.debian.org/status/fetch.php?pkg=libqbarch=mipselver=0.17.0-2stamp=1394039751 Please cat tests/test-suite.log to stdout, or alter the packaging so that `make check` runs with VERBOSE=1; that will give more detail in the buildd logs if it fails. Thanks, 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
Processed: Re: Bug#754692: libqb: sometimes FTBFS: testsuite races
Processing commands for cont...@bugs.debian.org: retitle 754692 libqb: sometimes FTBFS: testsuite races Bug #754692 [src:libqb] libqb: FTBFS on kfreebsd-*: test suite failures Changed Bug title to 'libqb: sometimes FTBFS: testsuite races' from 'libqb: FTBFS on kfreebsd-*: test suite failures' user debian-...@lists.debian.org Setting user to debian-...@lists.debian.org (was ste...@pyro.eu.org). usertags 754692 - kfreebsd There were no usertags set. Usertags are now: . thanks Stopping processing here. Please contact me if you need assistance. -- 754692: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=754692 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: Some times sign with S/MIME failed
Processing commands for cont...@bugs.debian.org: retitle 766349 Kmail: Some times sign with S/MIME failed Bug #766349 [kmail] Some times sign with S/MIME failed Changed Bug title to 'Kmail: Some times sign with S/MIME failed' from 'Some times sign with S/MIME failed' thanks Stopping processing here. Please contact me if you need assistance. -- 766349: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=766349 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#766347: marked as done (libjpeg-dev: uninstallable: Conflicts: libjpeg62-dev)
Your message dated Wed, 22 Oct 2014 13:49:56 +
with message-id e1xgwiw-w5...@franck.debian.org
and subject line Bug#766347: fixed in libjpeg-turbo 1:1.3.1-10
has caused the Debian Bug report #766347,
regarding libjpeg-dev: uninstallable: Conflicts: libjpeg62-dev
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
766347: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=766347
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
---BeginMessage---
Package: libjpeg-dev
Version: 1:1.3.1-9
Severity: grave
Justification: renders package unusable
[ odyx@ and debian-wb-team@ x-d-cc, please keep them in the loop? ]
Hi,
spotted by Didier, looking at cups build attempts:
| The following packages have unmet dependencies:
| sbuild-build-depends-cups-dummy : Depends: libjpeg-dev
|Depends: libtiff-dev
| E: Unable to correct problems, you have held broken packages.
tiff didn't change, but libtiff5-dev (providing libtiff-dev) depends on
libjpeg-dev, so there's probably a single issue at play here. Since
libjpeg-turbo was installed a few minutes before that, let's check…
Trying to install libjpeg-dev from buildd-unstable:
| $ sudo apt-get install libjpeg-dev=1:1.3.1-9 libjpeg62-turbo-dev=1:1.3.1-9
libjpeg62-turbo=1:1.3.1-9
[…]
| Some packages could not be installed. This may mean that you have
| requested an impossible situation or if you are using the unstable
| distribution that some required packages have not yet been created
| or been moved out of Incoming.
| The following information may help to resolve the situation:
|
| The following packages have unmet dependencies:
| libjpeg-dev : Conflicts: libjpeg62-dev
Checking:
| Package: libjpeg-dev
| Depends: libjpeg62-turbo-dev (= 1:1.3.1-9)
| Conflicts: libjpeg62-dev, libjpeg7-dev, libjpeg8-dev, libjpeg9-dev
+
| Package: libjpeg62-turbo-dev
| Provides: libjpeg-dev, libjpeg62-dev
= can't work.
I guess the Drop dummy transitional libjpeg62{,-dev,-dbg} packages
part didn't go particularly well.
Mraw,
KiBi.
---End Message---
---BeginMessage---
Source: libjpeg-turbo
Source-Version: 1:1.3.1-10
We believe that the bug you reported is fixed in the latest version of
libjpeg-turbo, 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 766...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Ondřej Surý ond...@debian.org (supplier of updated libjpeg-turbo 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: Wed, 22 Oct 2014 15:13:59 +0200
Source: libjpeg-turbo
Binary: libjpeg-dev libjpeg62-turbo-dev libjpeg62-turbo libjpeg62-turbo-dbg
libturbojpeg1 libturbojpeg1-dbg libturbojpeg1-dev libjpeg-turbo-progs
libjpeg-turbo-progs-dbg
Architecture: source all
Version: 1:1.3.1-10
Distribution: unstable
Urgency: medium
Maintainer: Debian TigerVNC Packaging Team
pkg-tigervnc-de...@lists.alioth.debian.org
Changed-By: Ondřej Surý ond...@debian.org
Description:
libjpeg-dev - Development files for the JPEG library [dummy package]
libjpeg-turbo-progs - Programs for manipulating JPEG files
libjpeg-turbo-progs-dbg - Programs for manipulating JPEG files (debugging
symbols)
libjpeg62-turbo - libjpeg-turbo JPEG runtime library
libjpeg62-turbo-dbg - Debugging symbols for the libjpeg-turbo JPEG library
libjpeg62-turbo-dev - Development files for the libjpeg-turbo JPEG library
libturbojpeg1 - TurboJPEG runtime library - SIMD optimized
libturbojpeg1-dbg - TurboJPEG runtime library - SIMD optimized (debugging
symbols)
libturbojpeg1-dev - Development files for the TurboJPEG library
Closes: 766347
Changes:
libjpeg-turbo (1:1.3.1-10) unstable; urgency=medium
.
* Drop extra and conflicting Provides (Closes: #766347)
Checksums-Sha1:
fa29b4d5d6f2723848a8885aff10887dc8920b08 2822 libjpeg-turbo_1.3.1-10.dsc
10ce9ad56642a1f5a539052f7cff37996b665ca0 77588
libjpeg-turbo_1.3.1-10.debian.tar.xz
cf8851d35cc8088f8666749367a106526a0ca339 48708 libjpeg-dev_1.3.1-10_all.deb
Checksums-Sha256:
995f919e5b50f2d261fc7148c6ebbe9ad7dd22a0b16752b7b12ad56d32d29b29 2822
libjpeg-turbo_1.3.1-10.dsc
c0c28a0464711ef8976e7935afa00f22a615756bf346780202ed0e6db5d5 77588
Bug#766359: gnome-shell: gdm shows a black screen when upgrading to 3.14.1-1
Package: gnome-shell Version: 3.14.0-1 Severity: grave Justification: renders package unusable Dear Maintainer, I tried upgrading gnome-shell on 2 machines at my home. One is a desktop with a core 2 duo and nvidia gpu, the other one is a notebook with a core i5 and intel hd 4000. After upgrading to the current version on unstable (3.14.1-1) and restarting the computer, I was presented to a black screen. On the logs it looked like everything went ok, but I could not see anything. The only way to interact with my system was to go to tty1 and use the console from there. I tried upgrading both gdm3 packages to the current version on unstable too, but with no luck. The only thing that fixed the problem was when I downgraded gnome-shell back to 3.14.0-1. I didn't even had to downgrade gdm3. If you need any more information or want me to test anything, just ask and I gladly will :) -- System Information: Debian Release: jessie/sid APT prefers testing APT policy: (900, 'testing'), (500, 'unstable'), (100, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.16-2-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages gnome-shell depends on: ii dconf-gsettings-backend [gsettings-backend] 0.22.0-1 ii evolution-data-server3.12.6-1.1 ii gir1.2-accountsservice-1.0 0.6.37-3+b1 ii gir1.2-atspi-2.0 2.14.0-1 ii gir1.2-caribou-1.0 0.4.15-1 ii gir1.2-clutter-1.0 1.20.0-1 ii gir1.2-freedesktop 1.42.0-2 ii gir1.2-gcr-3 3.14.0-2 ii gir1.2-gdesktopenums-3.0 3.14.0-1 ii gir1.2-gdm3 3.14.1-1 ii gir1.2-gkbd-3.0 3.6.0-1 ii gir1.2-glib-2.0 1.42.0-2 ii gir1.2-gnomebluetooth-1.03.14.0-1 ii gir1.2-gnomedesktop-3.0 3.14.0-1 ii gir1.2-gtk-3.0 3.14.1-1 ii gir1.2-ibus-1.0 1.5.8-3 ii gir1.2-mutter-3.03.14.1-1 ii gir1.2-networkmanager-1.00.9.10.0-3 ii gir1.2-nmgtk-1.0 0.9.10.0-2 ii gir1.2-pango-1.0 1.36.8-2 ii gir1.2-polkit-1.00.105-7 ii gir1.2-soup-2.4 2.48.0-1 ii gir1.2-telepathyglib-0.120.24.1-1 ii gir1.2-telepathylogger-0.2 0.8.1-1 ii gir1.2-upowerglib-1.00.99.1-3 ii gjs 1.42.0-1 ii gnome-backgrounds3.14.0-1 ii gnome-icon-theme-symbolic3.12.0-1 ii gnome-settings-daemon3.14.0-2 ii gnome-shell-common 3.14.0-1 ii gnome-themes-standard3.14.0-1 ii gsettings-desktop-schemas3.14.0-1 ii libatk-bridge2.0-0 2.14.0-2 ii libatk1.0-0 2.14.0-1 ii libc62.19-11 ii libcairo21.12.16-5 ii libcanberra-gtk3-0 0.30-2.1 ii libcanberra0 0.30-2.1 ii libclutter-1.0-0 1.20.0-1 ii libcogl-pango20 1.18.2-2 ii libcogl201.18.2-2 ii libcroco30.6.8-3 ii libdbus-glib-1-2 0.102-1 ii libecal-1.2-16 3.12.6-1.1 ii libedataserver-1.2-183.12.6-1.1 ii libgcr-base-3-1 3.14.0-2 ii libgdk-pixbuf2.0-0 2.31.1-2+b1 ii libgirepository-1.0-11.42.0-2 ii libgjs0e [libgjs0-libmozjs-24-0] 1.42.0-1 ii libglib2.0-0 2.42.0-2 ii libgstreamer1.0-01.4.3-1 ii libgtk-3-0 3.14.1-1 ii libical1 1.0-1 ii libjson-glib-1.0-0 1.0.2-1 ii libmozjs-24-024.2.0-2 ii libmutter0e 3.14.0-1 ii libnm-glib4 0.9.10.0-3 ii libnm-util2 0.9.10.0-3 ii libpango-1.0-0 1.36.8-2 ii libpangocairo-1.0-0 1.36.8-2 ii libpolkit-agent-1-0 0.105-7 ii libpolkit-gobject-1-00.105-7 ii libpulse-mainloop-glib0 5.0-13 ii libpulse0
Bug#766349: Kmail: Some times sign with S/MIME failed
found 766349 + kdepim/4:4.14.2-1 thanks Hi, also found in kdepim/4:4.14.2-1 CU Jörg -- pgp Fingerprint: 7D13 3C60 0A10 DBE1 51F8 EBCB 422B 44B0 BE58 1B6E pgp Key: BE581B6E CAcert Key S/N: 0E:D4:56 Jörg Frings-Fürst D-54526 Niederkail Threema-ID: SYR8SJXB IRC: j_...@freenode.net, j_...@oftc.net signature.asc Description: This is a digitally signed message part.
Processed: found
Processing commands for cont...@bugs.debian.org: found 698375 3.1.8-1.2 Bug #698375 [gfs2-utils,redhat-cluster-suite] gfs2-utils: fails to upgrade from wheezy: insserv: script gfs2-utils: service gfs2 already provided! There is no source info for the package 'gfs2-utils' at version '3.1.8-1.2' with architecture '' Marked as found in versions redhat-cluster/3.1.8-1.2. thanks Stopping processing here. Please contact me if you need assistance. -- 698375: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=698375 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: Debian bug #766349
Processing commands for cont...@bugs.debian.org: found 766349 kdepim/4:4.14.2-1 Bug #766349 [kmail] Kmail: Some times sign with S/MIME failed Marked as found in versions kdepim/4:4.14.2-1. thanks Stopping processing here. Please contact me if you need assistance. -- 766349: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=766349 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 763134
Processing commands for cont...@bugs.debian.org: tags 763134 + pending Bug #763134 [acpi-support-base] acpi-support-base: /usr/share/acpi-support/power-funcs broken from line 24 if consolekit installed and no dbus running Ignoring request to alter tags of bug #763134 to the same tags previously set thanks Stopping processing here. Please contact me if you need assistance. -- 763134: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=763134 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#766362: libvirt-daemon-system: fails to install
Hi, Holger Levsen wrote (22 Oct 2014 14:06:05 GMT) : BEGIN failed--compilation aborted at /usr/bin/deb-systemd-helper line 85. ... which is shipped by the init-system-helpers package, that depends on perl-modules, that ships File::Path. The attached log shows that init-system-helpers and libvirt-daemon-system are unpacked before perl-modules is upgraded, but after perl itself was upgraded, so with the new @INC set up, it doesn't look anymore for modules in the place where Wheezy's perl-modules ships File::Path (/usr/share/perl/5.14.2). This feels like a bug in init-system-helpers or perl, rather than in libvirt-daemon-system. Let's start with the Perl option: Niko, Dom, any idea? Cheers, -- intrigeri -- 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#763922: torque: CVE-2014-3684: non-root users able to kill any process on any node in a job
Processing control commands: tags -1 + patch Bug #763922 [src:torque] torque: CVE-2014-3684: non-root users able to kill any process on any node in a job Added tag(s) patch. -- 763922: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=763922 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#763922: torque: CVE-2014-3684: non-root users able to kill any process on any node in a job
Control: tags -1 + patch
Attached is a preliminary patch for this issue.
Regards,
Salvatore
Description: CVE-2014-3684: non-root users able to kill any process on any node in a job
limit tm_adopt() to only adopt a session id that is owned by the
calling user.
.
Within a TORQUE Resource Manager job, the tm_adopt() TORQUE library
call enables a user-built executable calling tm_adopt() to adopt any
session id (and its child processes) regardless of the session id owner
on any node within a job. When a job that includes the executable
calling tm_adopt() exits, the adopted processes are killed along with
the job processes during normal job cleanup. This can enable a non-root
user to kill processes he/she doesn't own including root-owned ones on
any node in a job.
Origin: backport, https://github.com/adaptivecomputing/torque/commit/f2f4c950f3d461a249111c8826da3beaafccace9
Bug-Debian: https://bugs.debian.org/763922
Bug-RedHat: https://bugzilla.redhat.com/show_bug.cgi?id=1149044
Forwarded: not-needed
Author: Chad Vizino cviz...@adaptivecomputing.com
Reviewed-by: Salvatore Bonaccorso car...@debian.org
Last-Update: 2014-10-21
--- a/src/cmds/pbs_track.c
+++ b/src/cmds/pbs_track.c
@@ -232,6 +232,12 @@ int main(
break;
+ case TM_EPERM:
+
+fprintf(stderr, pbs_track: permission denied: %s (%d)\n,
+pbse_to_txt(rc),
+rc);
+
default:
/* Unexpected error occurred */
--- a/src/include/tm.h
+++ b/src/include/tm.h
@@ -195,7 +195,7 @@ int tm_register(tm_whattodo_t *what,
/*
* DJH 15 Nov 2001.
* Generic out-of-band task adoption call for tasks parented by
- * another job management system. Minor security hole?
+ * another job management system.
* Cannot be called with any other tm call.
* 26 Feb 2002. Allows id to be jobid (adoptCmd = TM_ADOPT_JOBID)
* or some altid (adoptCmd = TM_ADOPT_ALTID)
--- a/src/include/tm_.h
+++ b/src/include/tm_.h
@@ -133,6 +133,7 @@ typedef unsigned int tm_task_id;
#define TM_EBADENVIRONMENT 17005
#define TM_ENOTFOUND 17006
#define TM_BADINIT 17007
+#define TM_EPERM 17008
#define TM_TODO_NOP 5000 /* Do nothing (the nodes value may be new) */
#define TM_TODO_CKPT 5001 /* Checkpoint what and continue it */
--- a/src/lib/Libifl/tm.c
+++ b/src/lib/Libifl/tm.c
@@ -84,6 +84,7 @@
#define _XOPEN_SOURCE
#define _XOPEN_SOURCE_EXTENDED 1
+#include stdbool.h
#include stdio.h
#include stdlib.h
#include unistd.h
@@ -94,6 +95,7 @@
#include errno.h
#include assert.h
#include sys/types.h
+#include sys/stat.h
#include sys/socket.h
#include sys/time.h
#include netinet/in.h
@@ -173,6 +175,31 @@ static event_info *event_hash[EVENT_HASH
static int event_count = 0;
/*
+ * check if the owner of this process matches the owner of pid
+ * returns TRUE if so, FALSE otherwise
+ */
+bool ispidowner(pid_t pid)
+ {
+ charpath[MAXPATHLEN];
+ struct stat sbuf;
+
+ /* build path to pid */
+ snprintf(path, sizeof(path), /proc/%d, pid);
+
+ /* do the stat */
+ /* if it fails, assume not owner */
+ if (stat(path, sbuf) != 0)
+return(FALSE);
+
+ /* see if caller is the owner of pid */
+ if (getuid() != sbuf.st_uid)
+return(FALSE);
+
+ /* caller is owner */
+ return(TRUE);
+ }
+
+/*
** Find an event number or return a NULL.
*/
static event_info *
@@ -1648,8 +1675,8 @@ err:
* some mpiruns simply use rsh to start remote processes - no AMS
* tracking or management facilities are available.
*
- * This function allows any task (session) to be adopted into a PBS
- * job. It is used by:
+ * This function allows any task (session) owned by the owner
+ * of the job to be adopted into a PBS job. It is used by:
* - adopter (which is in turn used by our pvmrun)
* - our rmsloader wrapper (a home-brew replacement for RMS'
*rmsloader that does some work and then exec()s the real
@@ -1683,7 +1710,8 @@ err:
* the mom. Returns TM_ENOTFOUND if the mom couldn't find a job
* with the given RMS resource id. Returns TM_ESYSTEM or
* TM_ENOTCONNECTED if there was some sort of comms error talking
- * to the mom
+ * to the mom. Returns TM_EPERM if an attempt was made to adopt
+ * a session not owned by the owner of the job.
*
* Side effects:
* Sets the tm_* globals to fake values if tm_init() has never
@@ -1701,6 +1729,10 @@ int tm_adopt(char *id, int adoptCmd, pid
sid = getsid(pid);
+ /* do not adopt a sid not owned by caller */
+ if (!ispidowner(sid))
+return(TM_EPERM);
+
/* Must be the only call to call to tm and
must only be called once */
Bug#766370: login[5797]: segfault at ip sp error 14 in librt-2.19.so
Package: libc6 Version: 2.19-11 Severity: critical Justification: breaks the whole system, you can not login as root, also with sudo. -- System Information: Debian Release: jessie/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 3.12.8-031208-generic (SMP w/2 CPU cores) Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages libc6 depends on: ii libgcc1 1:4.9.1-18 libc6 recommends no packages. Versions of packages libc6 suggests: ii debconf [debconf-2.0] 1.5.53 pn glibc-doc none ii locales2.19-11 -- debconf-show failed -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: bug 755328 is forwarded to https://rt.cpan.org/Ticket/Display.html?id=85950
Processing commands for cont...@bugs.debian.org: forwarded 755328 https://rt.cpan.org/Ticket/Display.html?id=85950 Bug #755328 [src:libgraph-writer-graphviz-perl] libgraph-writer-graphviz-perl: FTBFS: Tests failures Set Bug forwarded-to-address to 'https://rt.cpan.org/Ticket/Display.html?id=85950'. thanks Stopping processing here. Please contact me if you need assistance. -- 755328: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=755328 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#765818: simgear: FTBFS[kfreebsd]: wrong usage of GL/glxext.h
Control: reassign -1 src:simgear Control: found -1 3.0.0-5 Control: merge -1 765932 These are both the same kfreebsd FTBFS; this (#765818) patch looks better, but I haven't tried either. -- 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: simgear: FTBFS[kfreebsd]: wrong usage of GL/glxext.h
Processing control commands: reassign -1 src:simgear Bug #765818 [simgear] simgear: FTBFS[kfreebsd]: wrong usage of GL/glxext.h Bug reassigned from package 'simgear' to 'src:simgear'. No longer marked as found in versions 3.0.0-5. Ignoring request to alter fixed versions of bug #765818 to the same values previously set found -1 3.0.0-5 Bug #765818 [src:simgear] simgear: FTBFS[kfreebsd]: wrong usage of GL/glxext.h Marked as found in versions simgear/3.0.0-5. merge -1 765932 Bug #765818 [src:simgear] simgear: FTBFS[kfreebsd]: wrong usage of GL/glxext.h Unable to merge bugs because: blocks of #765932 is '' not '754988' Failed to merge 765818: Did not alter merged bugs -- 765818: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=765818 765932: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=765932 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: retry failed merge
Processing commands for cont...@bugs.debian.org: block 754988 by 765932 Bug #754988 [release.debian.org] transition: libjpeg-turbo 754988 was blocked by: 765818 754988 was not blocking any bugs. Added blocking bug(s) of 754988: 765932 merge 765818 765932 Bug #765818 [src:simgear] simgear: FTBFS[kfreebsd]: wrong usage of GL/glxext.h Bug #765932 [src:simgear] src:simgear: GL_GLEXT_LEGACY is defined but, GLX_GLEXT_LEGACY is not Merged 765818 765932 End of message, stopping processing here. Please contact me if you need assistance. -- 754988: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=754988 765818: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=765818 765932: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=765932 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#755328: marked as done (libgraph-writer-graphviz-perl: FTBFS: Tests failures)
Your message dated Wed, 22 Oct 2014 15:50:31 + with message-id e1xgybd-dg...@franck.debian.org and subject line Bug#755328: fixed in libgraph-writer-graphviz-perl 0.11-2 has caused the Debian Bug report #755328, regarding libgraph-writer-graphviz-perl: FTBFS: 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.) -- 755328: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=755328 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Source: libgraph-writer-graphviz-perl Version: 0.11-1nmu1 Severity: serious Tags: jessie sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20140718 qa-ftbfs Justification: FTBFS on amd64 Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): make[1]: Entering directory '/«PKGBUILDDIR»' PERL_DL_NONLAZY=1 /usr/bin/perl -MExtUtils::Command::MM -e test_harness(0, 'inc', 'blib/lib', 'blib/arch') t/*.t t/0.use.t . ok # Failed test at t/1.simple.t line 23. # Looks like you failed 1 test of 1. t/1.simple.t .. Dubious, test returned 1 (wstat 256, 0x100) Failed 1/1 subtests # Failed test at t/2.ioall.t line 32. # Looks like you failed 1 test of 2. Failed 2/3 test programs. 2/4 subtests failed. t/2.ioall.t ... Dubious, test returned 1 (wstat 256, 0x100) Failed 1/2 subtests Test Summary Report --- t/1.simple.t (Wstat: 256 Tests: 1 Failed: 1) Failed test: 1 Non-zero exit status: 1 t/2.ioall.t (Wstat: 256 Tests: 2 Failed: 1) Failed test: 2 Non-zero exit status: 1 Files=3, Tests=4, 1 wallclock secs ( 0.04 usr 0.02 sys + 0.60 cusr 0.19 csys = 0.85 CPU) Result: FAIL make[1]: *** [test_dynamic] Error 1 Makefile:742: recipe for target 'test_dynamic' failed make[1]: Leaving directory '/«PKGBUILDDIR»' dh_auto_test: make -j1 test returned exit code 2 The full build log is available from: http://aws-logs.debian.net/ftbfs-logs/2014/07/18/libgraph-writer-graphviz-perl_0.11-1nmu1_unstable.log A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! About the archive rebuild: The rebuild was done on EC2 VM instances from Amazon Web Services, using a clean, minimal and up-to-date chroot. Every failed build was retried once to eliminate random failures. ---End Message--- ---BeginMessage--- Source: libgraph-writer-graphviz-perl Source-Version: 0.11-2 We believe that the bug you reported is fixed in the latest version of libgraph-writer-graphviz-perl, 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 755...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. gregor herrmann gre...@debian.org (supplier of updated libgraph-writer-graphviz-perl 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: Wed, 22 Oct 2014 17:32:07 +0200 Source: libgraph-writer-graphviz-perl Binary: libgraph-writer-graphviz-perl Architecture: source all Version: 0.11-2 Distribution: unstable Urgency: low Maintainer: Debian Perl Group pkg-perl-maintain...@lists.alioth.debian.org Changed-By: gregor herrmann gre...@debian.org Description: libgraph-writer-graphviz-perl - GraphViz Writer for Graph object Closes: 755328 Changes: libgraph-writer-graphviz-perl (0.11-2) unstable; urgency=low . [ Salvatore Bonaccorso ] * Change Vcs-Git to canonical URI (git://anonscm.debian.org) * Change search.cpan.org based URIs to metacpan.org based URIs . [ Axel Beckert ] * debian/copyright: migrate pre-1.0 format to 1.0 using cme fix dpkg- copyright . [ gregor herrmann ] * Ack NMU, thanks Ian. Import Ian's commits as quilt patches. . [ Salvatore Bonaccorso ] * Update Vcs-Browser URL to cgit web frontend . [ gregor herrmann ] * Update Ian's changes to the test suite. Graphviz dot output has changed again, and textually comparing formatted strings is fragile. So switch from dot format to plain format. Update test utility function accordingly. (Closes: #755328) * debian/copyright: update information for debian/*. * Mark package as
Bug#746082: marked as done (libalog: FTBFS: error: aws-net-std__gnat.adb must be compiled)
Your message dated Wed, 22 Oct 2014 16:00:12 + with message-id e1xgyka-0001sg...@franck.debian.org and subject line Bug#746082: fixed in libalog 0.5.0-1 has caused the Debian Bug report #746082, regarding libalog: FTBFS: error: aws-net-std__gnat.adb must be compiled 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.) -- 746082: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=746082 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Source: libalog Version: 0.4.1-2 Severity: serious Tags: jessie sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20140426 qa-ftbfs Justification: FTBFS on amd64 Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): make[2]: Entering directory `/«PKGBUILDDIR»' ar rv obj/lib/libglue.a obj/full/lib/dynamic/glue_syslog.o r - obj/full/lib/dynamic/glue_syslog.o gcc-4.6 -c -g -gnatygAdISuxo -gnatVa -gnat05 -gnatwal -gnatf -fstack-check -gnato -I- -gnatA /«PKGBUILDDIR»/tests/runner_full.adb gcc-4.6 -c -g -gnatygAdISuxo -gnatVa -gnat05 -gnatwal -gnatf -fstack-check -gnato -I- -gnatA /«PKGBUILDDIR»/tests/facility_tests.adb gcc-4.6 -c -g -gnatygAdISuxo -gnatVa -gnat05 -gnatwal -gnatf -fstack-check -gnato -I- -gnatA /«PKGBUILDDIR»/tests/facility_tests-pgsql.adb gcc-4.6 -c -g -gnatygAdISuxo -gnatVa -gnat05 -gnatwal -gnatf -fstack-check -gnato -I- -gnatA /«PKGBUILDDIR»/tests/facility_tests-smtp.adb gcc-4.6 -c -g -gnatygAdISuxo -gnatVa -gnat05 -gnatwal -gnatf -fstack-check -gnato -I- -gnatA /«PKGBUILDDIR»/tests/facility_tests-xmpp.adb gcc-4.6 -c -g -gnatygAdISuxo -gnatVa -gnat05 -gnatwal -gnatf -fstack-check -gnato -I- -gnatA /«PKGBUILDDIR»/src/alog.ads gcc-4.6 -c -g -gnatygAdISuxo -gnatVa -gnat05 -gnatwal -gnatf -fstack-check -gnato -I- -gnatA /«PKGBUILDDIR»/src/alog-facilities.adb gcc-4.6 -c -g -gnatygAdISuxo -gnatVa -gnat05 -gnatwal -gnatf -fstack-check -gnato -I- -gnatA /«PKGBUILDDIR»/src/alog-facilities-file_descriptor.adb gcc-4.6 -c -g -gnatygAdISuxo -gnatVa -gnat05 -gnatwal -gnatf -fstack-check -gnato -I- -gnatA /«PKGBUILDDIR»/src/alog-facilities-pgsql.adb gcc-4.6 -c -g -gnatygAdISuxo -gnatVa -gnat05 -gnatwal -gnatf -fstack-check -gnato -I- -gnatA /«PKGBUILDDIR»/src/alog-log_request.adb gcc-4.6 -c -g -gnatygAdISuxo -gnatVa -gnat05 -gnatwal -gnatf -fstack-check -gnato -I- -gnatA /«PKGBUILDDIR»/src/alog-facilities-smtp.adb gcc-4.6 -c -g -gnatygAdISuxo -gnatVa -gnat05 -gnatwal -gnatf -fstack-check -gnato -I- -gnatA /«PKGBUILDDIR»/src/alog-facilities-xmpp.adb gcc-4.6 -c -g -gnatygAdISuxo -gnatVa -gnat05 -gnatwal -gnatf -fstack-check -gnato -I- -gnatA /«PKGBUILDDIR»/src/alog-policy_db.adb gcc-4.6 -c -g -gnatygAdISuxo -gnatVa -gnat05 -gnatwal -gnatf -fstack-check -gnato -I- -gnatA /«PKGBUILDDIR»/src/alog-maps.adb gnatbind -shared -E -I- -x /«PKGBUILDDIR»/obj/full/runner_full.ali error: aws-net-std__gnat.adb must be compiled error: (/usr/lib/ada/adalib/aws/aws-net-std__gnat.ali is obsolete and read-only) error: g-socket.adb must be compiled error: (/usr/lib/gcc/x86_64-linux-gnu/4.6/adalib/g-socket.ali is obsolete and read-only) error: g-soliop.ads must be compiled error: (/usr/lib/gcc/x86_64-linux-gnu/4.6/adalib/g-soliop.ali is obsolete and read-only) error: g-socthi.adb must be compiled error: (/usr/lib/gcc/x86_64-linux-gnu/4.6/adalib/g-socthi.ali is obsolete and read-only) error: g-sothco.adb must be compiled error: (/usr/lib/gcc/x86_64-linux-gnu/4.6/adalib/g-sothco.ali is obsolete and read-only) error: g-soccon.ads must be compiled error: (/usr/lib/gcc/x86_64-linux-gnu/4.6/adalib/g-soccon.ali is obsolete and read-only) gnatmake: *** bind failed. make[2]: *** [build_tests] Error 4 The full build log is available from: http://aws-logs.debian.net/ftbfs-logs/2014/04/26/libalog_0.4.1-2_unstable.log A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! About the archive rebuild: The rebuild was done on EC2 VM instances from Amazon Web Services, using a clean, minimal and up-to-date chroot. Every failed build was retried once to eliminate random failures. ---End Message--- ---BeginMessage--- Source: libalog Source-Version: 0.5.0-1 We believe that the bug you reported is fixed in the latest version of libalog, 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
Bug#755077: marked as done (libalog: increase gnat version in dependencies)
Your message dated Wed, 22 Oct 2014 16:00:12 +
with message-id e1xgyka-0001sm...@franck.debian.org
and subject line Bug#755077: fixed in libalog 0.5.0-1
has caused the Debian Bug report #755077,
regarding libalog: increase gnat version in dependencies
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
755077: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=755077
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
---BeginMessage---
Package: libalog
Version: 0.4.1-2
Severity: normal
Tags: patch
User: debian-powe...@lists.debian.org
Usertags: ppc64el
Dear Maintainer,
This package depends on an old gnat version. Currently it doesn't build on
ppc64el because ppc64el support started on GCC/GNAT 4.8, so, I would like if
you can increase the gnat version on the dependencies, to a more recent version.
I am providing a patch that would do it for you.
On the other side, if you want to continue to use the current gnat version, you
can do something like:
-Depends: gnat-4-6
+Depends: gnat-4.6 [!ppc64el] | gnat-4.8 [ppc64el]
Thank you,
Breno
Index: libalog-0.4.1/debian/control
===
--- libalog-0.4.1.orig/debian/control
+++ libalog-0.4.1/debian/control
@@ -4,7 +4,7 @@ Priority: optional
Maintainer: Adrian-Ken Rueegsegger k...@codelabs.ch
Uploaders: Reto Buerki r...@codelabs.ch
DM-Upload-Allowed: yes
-Build-Depends: debhelper (= 8), gnat, gnat-4.6, libahven3-dev,
+Build-Depends: debhelper (= 8), gnat, gnat-4.8, libahven3-dev,
libaws2.10.2-dev, libapq-postgresql3.2.0-dev, asciidoc, source-highlight, quilt
Standards-Version: 3.9.3
Homepage: http://www.codelabs.ch/alog/
@@ -13,7 +13,7 @@ Vcs-Browser: http://git.codelabs.ch/?p=a
Package: libalog0.4.1-base
Architecture: any
-Depends: ${shlibs:Depends}, ${misc:Depends}, gnat-4.6
+Depends: ${shlibs:Depends}, ${misc:Depends}, gnat-4.8
Conflicts: libalog0.4.1-full
Replaces: libalog0.4.1-full
Description: Logging framework for Ada (base)
@@ -23,7 +23,7 @@ Description: Logging framework for Ada (
Package: libalog0.4.1-full
Architecture: any
-Depends: ${shlibs:Depends}, ${misc:Depends}, gnat-4.6
+Depends: ${shlibs:Depends}, ${misc:Depends}, gnat-4.8
Conflicts: libalog0.4.1-base
Replaces: libalog0.4.1-base
Description: Logging framework for Ada (full)
@@ -34,7 +34,7 @@ Description: Logging framework for Ada (
Package: libalog0.4.1-base-dev
Section: libdevel
Architecture: any
-Depends: ${misc:Depends}, libalog0.4.1-base (= ${binary:Version}), gnat, gnat-4.6
+Depends: ${misc:Depends}, libalog0.4.1-base (= ${binary:Version}), gnat, gnat-4.8
Conflicts: libalog0.4.1-full-dev
Replaces: libalog0.4.1-full-dev
Description: Logging framework for Ada (development)
@@ -48,7 +48,7 @@ Package: libalog0.4.1-full-dev
Section: libdevel
Architecture: any
Depends: ${misc:Depends}, libalog0.4.1-full (= ${binary:Version}), gnat,
- gnat-4.6, libaws2.10.2-dev, libapq-postgresql3.2.0-dev
+ gnat-4.8, libaws2.10.2-dev, libapq-postgresql3.2.0-dev
Conflicts: libalog0.4.1-base-dev
Replaces: libalog0.4.1-base-dev
Description: Logging framework for Ada (development)
---End Message---
---BeginMessage---
Source: libalog
Source-Version: 0.5.0-1
We believe that the bug you reported is fixed in the latest version of
libalog, 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 755...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Adrian-Ken Rueegsegger k...@codelabs.ch (supplier of updated libalog package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Format: 1.8
Date: Thu, 16 Oct 2014 14:41:55 +0200
Source: libalog
Binary: libalog0.5.0 libalog1-dev libalog-dbg libalog-doc
Architecture: source amd64 all
Version: 0.5.0-1
Distribution: unstable
Urgency: medium
Maintainer: Adrian-Ken Rueegsegger k...@codelabs.ch
Changed-By: Adrian-Ken Rueegsegger k...@codelabs.ch
Description:
libalog-dbg - Logging framework for Ada (debug)
libalog-doc - Logging framework for Ada (documentation)
libalog0.5.0 - Logging framework for Ada
libalog1-dev - Logging framework for Ada (development)
Closes: 746082 755077 76
Changes:
libalog (0.5.0-1) unstable; urgency=medium
.
Bug#764444: marked as done (libalog: build-depends on cruft package libaws2.10.2-dev)
Your message dated Wed, 22 Oct 2014 16:00:12 + with message-id e1xgyka-0001ss...@franck.debian.org and subject line Bug#76: fixed in libalog 0.5.0-1 has caused the Debian Bug report #76, regarding libalog: build-depends on cruft package libaws2.10.2-dev to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 76: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=76 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Source: libalog Version: 0.4.1-2 Severity: serious User: trei...@debian.org Usertags: edos-uninstallable Affects: libaws2.10.2 Hello, libalog build-depends on libaws2.10.2-dev. However, this package is no longer build from source libaws. -Ralf. ---End Message--- ---BeginMessage--- Source: libalog Source-Version: 0.5.0-1 We believe that the bug you reported is fixed in the latest version of libalog, 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 764...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Adrian-Ken Rueegsegger k...@codelabs.ch (supplier of updated libalog package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Thu, 16 Oct 2014 14:41:55 +0200 Source: libalog Binary: libalog0.5.0 libalog1-dev libalog-dbg libalog-doc Architecture: source amd64 all Version: 0.5.0-1 Distribution: unstable Urgency: medium Maintainer: Adrian-Ken Rueegsegger k...@codelabs.ch Changed-By: Adrian-Ken Rueegsegger k...@codelabs.ch Description: libalog-dbg - Logging framework for Ada (debug) libalog-doc - Logging framework for Ada (documentation) libalog0.5.0 - Logging framework for Ada libalog1-dev - Logging framework for Ada (development) Closes: 746082 755077 76 Changes: libalog (0.5.0-1) unstable; urgency=medium . * Imported upstream version 0.5.0 * Remove obsolete DM-Upload-Allowed from debian/control * Drop 'full' packages as upstream has removed that functionality * Update patches * Update binary package names * Update package descriptions in debian/control * Update to Standards-Version 3.9.6 * Update Build-Depends in debian/control * Enable dpkg-buildflags hardening options * Make -dbg package compliant to Debian Ada Policy * Transition to gnat-4.9 compiler (Closes: #746082, #755077, #76) * Update ahven Build-Depends to libahven4-dev * Update copyright information * Update to debhelper 9 * Simplify debian/rules file * Declare NUM_CPUS variable in debian/rules * Override dh_compress and dh_auto_test targets * Update debian/*.install files * Add debian/watch file * Add libalog-doc package * Add minimal run time test for installed package * Decouple the aliversion from the soversion Checksums-Sha1: 7684813d4908012427af269cdc6582b4271489fb 2081 libalog_0.5.0-1.dsc fdbee3b4c85c441fe4bc96cfa72e25c0d1d9a0e6 81947 libalog_0.5.0.orig.tar.gz 6a534049804b6b35cba27e1d2dfd88e6de99064d 4656 libalog_0.5.0-1.debian.tar.xz fa377e2e7bc1c393ff3b3d1c2ff2b57f803c7e3b 106286 libalog0.5.0_0.5.0-1_amd64.deb 72f9f69103fe67b9e92bb96b852bc54d1196 136136 libalog1-dev_0.5.0-1_amd64.deb 3f8d033d8c1bff9e29318ebf61994824a7d38d46 211858 libalog-dbg_0.5.0-1_amd64.deb 73bee10f110d36888336a55ed3390d3fb2f10aa9 32550 libalog-doc_0.5.0-1_all.deb Checksums-Sha256: 16e1646bc4f06e0bec8956aebb502680189ed4ef8b7dd976a3dc6f72051d6e5b 2081 libalog_0.5.0-1.dsc 0398e6c6790f8fa61e2c52d5fd0b2838e596f202911918748f6987026ae92c43 81947 libalog_0.5.0.orig.tar.gz f17dddfc1982eba744e8128de591a223482a1eef10cdb3672741bf9feb761255 4656 libalog_0.5.0-1.debian.tar.xz 627f901af5d648df76e1e271bfade350cd770eeb01d3b2ccd7e76f07d1b190cf 106286 libalog0.5.0_0.5.0-1_amd64.deb 01dbff894110665ca819e116d9a24db74977352bde2ccf23df9d798163c60d43 136136 libalog1-dev_0.5.0-1_amd64.deb d4f98e16565b7a7a9b3a8b681f94d1d2ff85faef6f2a0ac6c76c8ee37aa3ac74 211858 libalog-dbg_0.5.0-1_amd64.deb eb85dd1e4cba35b6845e8f2cdc3c35c434ae1313931e39a9047585ea0a4a7bcc 32550 libalog-doc_0.5.0-1_all.deb Files: 1b69331e7d9c99e4d996eb4d17789978 2081 libs optional libalog_0.5.0-1.dsc 31bc98387853c2248a62139863316007 81947 libs optional libalog_0.5.0.orig.tar.gz
Bug#766374: X Server not available after upgrade on 21 Oct.
Package: xserver-xorg Version: 1:7.7+7 Severity: grave -- System Information: Debian Release: jessie/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 3.16-3-amd64 (SMP w/2 CPU cores) Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash * What led up to the situation? ran dist-upgrade on 21 Oct. * What exactly did you do (or not do) that was effective (or ineffective)? Started gdm3 service * What was the outcome of this action? Instead of the gdm3 greeter there was an error message: Oh no! Something has gone wrong. A problem has occurred and the system can't recover. Please log out and try again. and a log-out-button. The mouse pointer was not visible. * What outcome did you expect instead? gdm3 greeter shows and you can log in -- Output from syslog: Oct 22 14:37:46 cohg gnome-session[770]: (gnome-session-failed:895): Gdk-WARNING **: gnome-session-failed: Fatal IO error 11 (Die Ressource ist zur Zeit nicht verfügbar) on X server :0. Oct 22 14:37:46 cohg org.a11y.Bus[776]: g_dbus_connection_real_closed: Remote peer vanished with error: Underlying GIOStream returned 0 bytes on an async read (g-io-error-quark, 0). Exiting. Oct 22 14:37:46 cohg org.a11y.atspi.Registry[839]: XIO: fatal IO error 11 (Resource temporarily unavailable) on X server :0 Oct 22 14:37:46 cohg gdm-Xorg-:0[4452]: Errors from xkbcomp are not fatal to the X server -- Package-specific info: X server symlink status: lrwxrwxrwx 1 root root 13 May 1 2012 /etc/X11/X - /usr/bin/Xorg -rwxr-xr-x 1 root root 2397280 Sep 22 23:49 /usr/bin/Xorg Diversions concerning libGL are in place diversion of /usr/lib/arm-linux-gnueabihf/libGL.so.1.2.0 to /usr/lib/mesa-diverted/arm-linux-gnueabihf/libGL.so.1.2.0 by glx-diversions diversion of /usr/lib/libGL.so.1 to /usr/lib/mesa-diverted/libGL.so.1 by glx-diversions diversion of /usr/lib/arm-linux-gnueabihf/libGLESv2.so.2.0.0 to /usr/lib/mesa-diverted/arm-linux-gnueabihf/libGLESv2.so.2.0.0 by glx-diversions diversion of /usr/lib/libGLESv2.so.2 to /usr/lib/mesa-diverted/libGLESv2.so.2 by glx-diversions diversion of /usr/lib/arm-linux-gnueabihf/libGL.so to /usr/lib/mesa-diverted/arm-linux-gnueabihf/libGL.so by glx-diversions diversion of /usr/lib/x86_64-linux-gnu/libGLESv1_CM.so.1.1.0 to /usr/lib/mesa-diverted/x86_64-linux-gnu/libGLESv1_CM.so.1.1.0 by glx-diversions diversion of /usr/lib/arm-linux-gnueabihf/libGLESv1_CM.so to /usr/lib/mesa-diverted/arm-linux-gnueabihf/libGLESv1_CM.so by glx-diversions diversion of /usr/lib/i386-linux-gnu/libGLESv2.so.2 to /usr/lib/mesa-diverted/i386-linux-gnu/libGLESv2.so.2 by glx-diversions diversion of /usr/lib/x86_64-linux-gnu/libGLESv2.so.2 to /usr/lib/mesa-diverted/x86_64-linux-gnu/libGLESv2.so.2 by glx-diversions diversion of /usr/lib/arm-linux-gnueabihf/libGL.so.1.2 to /usr/lib/mesa-diverted/arm-linux-gnueabihf/libGL.so.1.2 by glx-diversions diversion of /usr/lib/libGLESv1_CM.so.1.1.0 to /usr/lib/mesa-diverted/libGLESv1_CM.so.1.1.0 by glx-diversions diversion of /usr/lib/i386-linux-gnu/libGLESv1_CM.so.1 to /usr/lib/mesa-diverted/i386-linux-gnu/libGLESv1_CM.so.1 by glx-diversions diversion of /usr/lib/x86_64-linux-gnu/libGLESv1_CM.so to /usr/lib/mesa-diverted/x86_64-linux-gnu/libGLESv1_CM.so by glx-diversions diversion of /usr/lib/arm-linux-gnueabihf/libGLESv1_CM.so.1.1.0 to /usr/lib/mesa-diverted/arm-linux-gnueabihf/libGLESv1_CM.so.1.1.0 by glx-diversions diversion of /usr/lib/libGL.so.1.2.0 to /usr/lib/mesa-diverted/libGL.so.1.2.0 by glx-diversions diversion of /usr/lib/libGLESv2.so to /usr/lib/mesa-diverted/libGLESv2.so by glx-diversions diversion of /usr/lib/libGL.so.1.2 to /usr/lib/mesa-diverted/libGL.so.1.2 by glx-diversions diversion of /usr/lib/i386-linux-gnu/libGLESv1_CM.so.1.1.0 to /usr/lib/mesa-diverted/i386-linux-gnu/libGLESv1_CM.so.1.1.0 by glx-diversions diversion of /usr/lib/x86_64-linux-gnu/libGL.so.1.2.0 to /usr/lib/mesa-diverted/x86_64-linux-gnu/libGL.so.1.2.0 by glx-diversions diversion of /usr/lib/arm-linux-gnueabihf/libGLESv2.so to /usr/lib/mesa-diverted/arm-linux-gnueabihf/libGLESv2.so by glx-diversions diversion of /usr/lib/libGL.so to /usr/lib/mesa-diverted/libGL.so by glx-diversions diversion of /usr/lib/arm-linux-gnueabihf/libGLESv2.so.2 to /usr/lib/mesa-diverted/arm-linux-gnueabihf/libGLESv2.so.2 by glx-diversions diversion of /usr/lib/x86_64-linux-gnu/libGL.so.1.2 to /usr/lib/mesa-diverted/x86_64-linux-gnu/libGL.so.1.2 by glx-diversions diversion of /usr/lib/i386-linux-gnu/libGLESv2.so to /usr/lib/mesa-diverted/i386-linux-gnu/libGLESv2.so by glx-diversions diversion of /usr/lib/libGLESv1_CM.so to /usr/lib/mesa-diverted/libGLESv1_CM.so by glx-diversions diversion of /usr/lib/i386-linux-gnu/libGL.so.1.2.0 to /usr/lib/mesa-diverted/i386-linux-gnu/libGL.so.1.2.0 by glx-diversions diversion of /usr/lib/i386-linux-gnu/libGL.so to
Bug#764253: system-config-printer: Creates millions of ppd symlinks
I have forwarded this report to Tim Waugh from Red Hat, original author of system-config-printer and he has answered me the following: -- can you check this ppdcache.py problem mentioned here? I've committed a change which should stop the looping by failing the call on IOError. https://git.fedorahosted.org/cgit/system-config-printer.git/commit/?h=1.4.xid=9a81dd1de3afaf30eec92045429029103823b577 And why is scp-dbus-service doing something when a job is printed? You're in a better position to find that out. It doesn't do that for me. Run scp-dbus-service --debug before printing, and see which D-Bus call it receives. Or watch dbus-monitor --session. By the way, you know about CUPS STR #4500, right..? https://cups.org/str.php?L4500 -- For the two bugs you mentioned there are fixes now: Thus I think there are two bugs here: * cups should not create files with wrong permissions in /etc/cups/ppd CUPS STR #4500: https://cups.org/str.php?L4500 * scp-dbus-service should not start an infinite loop creating millions of symlinks in /tmp just because the permissions in /etc/cups/ppd are wrong https://git.fedorahosted.org/cgit/system-config-printer.git/commit/?h=1.4.xid=9a81dd1de3afaf30eec92045429029103823b577 The only strange thing is that scp-dbus-service gets triggered by simply printing. So can you please try what Tim suggests: -- Run scp-dbus-service --debug before printing, and see which D-Bus call it receives. Or watch dbus-monitor --session. -- and post your results here? Thanks. Till -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#763006: marked as done (gnome-do: Crashes at start)
Your message dated Wed, 22 Oct 2014 16:19:41 + with message-id e1xgydr-0003op...@franck.debian.org and subject line Bug#763006: fixed in gnome-do 0.95.2-1 has caused the Debian Bug report #763006, regarding gnome-do: Crashes at start 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.) -- 763006: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=763006 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: gnome-do Version: 0.95.1-1+b1 Severity: grave Justification: renders package unusable Dear Maintainer, After some recent upgrades in unstable (glib?), gnome-do no longer starts, it just crashes instantly. [Error 04:36:11.644] [PluginManager] Encountered error loading plugin: TargetInvocationException Exception has been thrown by the target of an invocation. Attempt to unlock mutex that was not locked Stacktrace: at unknown 0x at (wrapper managed-to-native) Gtk.Clipboard.gtk_clipboard_wait_is_text_available (intptr) 0x at Gtk.Clipboard.WaitIsTextAvailable () 0x00017 at Do.Universe.SelectedTextItem.UpdateSelection (object,System.EventArgs) 0x00033 at Do.Platform.AbstractApplicationService.OnSummoned () 0x0002d at Do.Platform.ApplicationService.ApplicationServicem__0 (object,System.EventArgs) 0x00013 at Do.Core.Controller.OnSummoned () 0x0002d at Do.Core.Controller.Summon () 0x00023 at Do.Do.Main (string[]) 0x001e3 at (wrapper runtime-invoke) Module.runtime_invoke_void_object (object,intptr,intptr,intptr) 0x Native stacktrace: /usr/bin/cli() [0x4b4146] /lib/x86_64-linux-gnu/libpthread.so.0(+0xf8d0) [0x7f3cb33f88d0] /lib/x86_64-linux-gnu/libc.so.6(gsignal+0x37) [0x7f3cb3076077] /lib/x86_64-linux-gnu/libc.so.6(abort+0x148) [0x7f3cb3077458] /lib/x86_64-linux-gnu/libglib-2.0.so.0(+0x8d95d) [0x7f3cabb2b95d] /usr/lib/x86_64-linux-gnu/libgtk-x11-2.0.so.0(gtk_clipboard_wait_for_contents+0x6a) [0x7f3ca6bff2aa] /usr/lib/x86_64-linux-gnu/libgtk-x11-2.0.so.0(gtk_clipboard_wait_is_text_available+0x22) [0x7f3ca6bff722] [0x4082a90b] Debug info from gdb: [New LWP 11167] [New LWP 11166] [New LWP 11165] [Thread debugging using libthread_db enabled] Using host libthread_db library /lib/x86_64-linux-gnu/libthread_db.so.1. 0x7f3cb33f84c9 in __libc_waitpid (pid=pid@entry=11168, stat_loc=stat_loc@entry=0x7fffb299198c, options=options@entry=0) at ../sysdeps/unix/sysv/linux/waitpid.c:40 40 ../sysdeps/unix/sysv/linux/waitpid.c: No such file or directory. Id Target Id Frame 4Thread 0x7f3cb1125700 (LWP 11165) cli 0x7f3cb30763f2 in do_sigsuspend (set=0x982c80 suspend_signal_mask) at ../sysdeps/unix/sysv/linux/sigsuspend.c:31 3Thread 0x7f3ca4a53700 (LWP 11166) gdbus 0x7f3cb311e0ed in poll () at ../sysdeps/unix/syscall-template.S:81 2Thread 0x7f3c9ee96700 (LWP 11167) gnome-do sem_wait () at ../nptl/sysdeps/unix/sysv/linux/x86_64/sem_wait.S:85 * 1Thread 0x7f3cb3f0a780 (LWP 11164) gnome-do 0x7f3cb33f84c9 in __libc_waitpid (pid=pid@entry=11168, stat_loc=stat_loc@entry=0x7fffb299198c, options=options@entry=0) at ../sysdeps/unix/sysv/linux/waitpid.c:40 Thread 4 (Thread 0x7f3cb1125700 (LWP 11165)): #0 0x7f3cb30763f2 in do_sigsuspend (set=0x982c80 suspend_signal_mask) at ../sysdeps/unix/sysv/linux/sigsuspend.c:31 #1 __GI___sigsuspend (set=set@entry=0x982c80 suspend_signal_mask) at ../sysdeps/unix/sysv/linux/sigsuspend.c:45 #2 0x005d1d0c in suspend_thread (context=0x7f3cb1124980, info=0x7f3cac0008c0) at sgen-os-posix.c:113 #3 suspend_handler (sig=optimized out, siginfo=optimized out, context=0x7f3cb1124980) at sgen-os-posix.c:131 #4 signal handler called #5 sem_wait () at ../nptl/sysdeps/unix/sysv/linux/x86_64/sem_wait.S:84 #6 0x0062e0e6 in mono_sem_wait (sem=sem@entry=0x982680 finalizer_sem, alertable=alertable@entry=1) at mono-semaphore.c:119 #7 0x005a93b4 in finalizer_thread (unused=unused@entry=0x0) at gc.c:1073 #8 0x0058bccb in start_wrapper_internal (data=0x106adc0) at threads.c:643 #9 start_wrapper (data=0x106adc0) at threads.c:688 #10 0x00622bad in thread_start_routine (args=args@entry=0xfef3a8) at wthreads.c:294 #11 0x00632a65 in inner_start_thread (arg=0x106ac60) at mono-threads-posix.c:49 #12 0x7f3cb33f10a4 in start_thread (arg=0x7f3cb1125700) at pthread_create.c:309 #13 0x7f3cb3126c2d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:111 Thread 3 (Thread 0x7f3ca4a53700 (LWP 11166)): #0 0x7f3cb311e0ed in poll () at
Bug#753203: marked as done (isdnutils: FTBFS: main.c:1300:11: error: assignment to expression with array type)
Your message dated Wed, 22 Oct 2014 16:49:04 + with message-id e1xgz5s-0008ct...@franck.debian.org and subject line Bug#753203: fixed in isdnutils 1:3.25+dfsg1-3.5 has caused the Debian Bug report #753203, regarding isdnutils: FTBFS: main.c:1300:11: error: assignment to expression with array type 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.) -- 753203: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=753203 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Source: isdnutils Version: 1:3.25+dfsg1-3.4 Severity: serious Tags: jessie sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20140628 qa-ftbfs Justification: FTBFS on amd64 Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): gcc -O2 -fomit-frame-pointer -Wall -DREQ_SYSOPTIONS=0 -DIPPP_FILTER -DHAVE_PCAP_BPF_H -g -O2 -fstack-protector --param=ssp-buffer-size=4 -Wformat -Werror=format-security -c -o main.o main.c In file included from pathnames.h:7:0, from main.c:65: config.h:75:0: warning: HAVE_PCAP_BPF_H redefined #define HAVE_PCAP_BPF_H /**/ ^ command-line:0:0: note: this is the location of the previous definition main.c: In function 'vfmtmsg': main.c:1300:11: error: assignment to expression with array type a = va_arg(args, va_list); ^ make[3]: *** [main.o] Error 1 The full build log is available from: http://aws-logs.debian.net/ftbfs-logs/2014/06/28/isdnutils_3.25+dfsg1-3.4_unstable.log A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! About the archive rebuild: The rebuild was done on EC2 VM instances from Amazon Web Services, using a clean, minimal and up-to-date chroot. Every failed build was retried once to eliminate random failures. ---End Message--- ---BeginMessage--- Source: isdnutils Source-Version: 1:3.25+dfsg1-3.5 We believe that the bug you reported is fixed in the latest version of isdnutils, 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 753...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Andreas Beckmann a...@debian.org (supplier of updated isdnutils 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: Mon, 20 Oct 2014 18:20:53 +0200 Source: isdnutils Binary: isdnutils-base isdnutils-xtools ipppd isdnlog isdnlog-data isdnutils-doc isdnvbox isdnvboxclient isdnvboxserver capiutils pppdcapiplugin Architecture: source all Version: 1:3.25+dfsg1-3.5 Distribution: unstable Urgency: medium Maintainer: Rolf Leggewie f...@rolf.leggewie.biz Changed-By: Andreas Beckmann a...@debian.org Description: capiutils - ISDN utilities - tools for CAPI-capable cards ipppd - ISDN utilities - PPP daemon isdnlog- ISDN utilities - connection logger isdnlog-data - ISDN utilities - connection logger data isdnutils-base - ISDN utilities - minimal set isdnutils-doc - ISDN utilities - documentation isdnutils-xtools - ISDN utilities - graphical tools isdnvbox - ISDN utilities - answering machine dependency package isdnvboxclient - ISDN utilities - answering machine client isdnvboxserver - ISDN utilities - answering machine server pppdcapiplugin - ISDN utilities - pppd plug-in for CAPI support Closes: 696829 701580 706024 737537 746503 753203 Changes: isdnutils (1:3.25+dfsg1-3.5) unstable; urgency=medium . * Non-maintainer upload. * use-va_copy.patch: Use va_copy() instead of va_list assignment. (Closes: #753203) * isdnlog-data: Set to Multi-Arch: foreign. (Closes: #706024) * Drop unused Build-Depends: lsb-release. (Closes: #737537) * Use canonical Vcs-* URLs. * Remove obsolete /etc/init.d/isdnutils from squeeze. Forgotten for one release don't try to rename it to /etc/init.d/isdnutils-base now. (Closes: #696829) * isdnvboxserver.postinst: Add missing quoting. (Closes: #701580) * d/clean: Cleanup generated files to fix building twice in a row. (Closes: #746503) * verbose-build.patch: Disable non-verbose build rules. Checksums-Sha1:
Bug#766169: libEGL.so.1 don't get installed
Hi, I have installed nvidia-driver 340.46-2, but not libegl1-nvidia. The new glx-alternatives fixes the issue for me. kwin and GTK based stuff is running again without any obvious problems. I only had to restore my KDE config out of a backup, because it had been massively damaged during login without running kwin. Best Regards Thanks for the fast fix Martin Hans Am 21.10.2014 um 23:57 schrieb Andreas Beckmann: On 2014-10-21 22:05, Martin Hans wrote: I can confirm this issue, too. you have nvidia-driver 340.46-2 installed?, but not libegl1-nvidia? Andreas -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#766092: systemd: Boot hangs indefinitely
Control: tags -1 moreinfo On Tue, 21 Oct 2014 04:46:45 +0200 Michael Biebl bi...@debian.org wrote: Am 21.10.2014 um 02:19 schrieb Marcelo Laia: On 21/10/14 at 01:07am, Michael Biebl wrote: How long did you wait? no limit! Indefinitely Could you check your /tmp (and /var/tmp) directory if it contains a large amount of symlinks (created by cups) or files. Thomas, Marcelo, can you please answer that question? I did some tests today, creating 1 million test files in /tmp (/tmp being on a ext4 file system). Even on my fast SSD, an ls -l /tmp took quite a bit of time. During boot, the systemd-tmpfiles job needed about 2 mins to clean up the directory. I also tested booting with sysvinit, and it took about the same time to clean up /tmp. Therefor I don't suspect a bug in systemd, but it rather looks like and ineffeciency/limitation of the file system when dealing with huge amount of files in one directory. If you even had more files in /tmp and maybe you have an HDD, it's very well possible, that systemd-tmpfiles will need several minutes. That's why I wanted to know, how long you let the systemd-tmpfiles job run. You might be affected by [1]. We also heard reports that google chrome beta was responsible for creating a huge amount of tmp files. Michael [1] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=764253 -- Why is it that all of the instruments seeking intelligent life in the universe are pointed away from Earth? signature.asc Description: OpenPGP digital signature
Processed: Re: Bug#766092: systemd: Boot hangs indefinitely
Processing control commands: tags -1 moreinfo Bug #766092 [systemd] systemd: Boot hangs indefinitely Added tag(s) moreinfo. -- 766092: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=766092 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#766362: libvirt-daemon-system: fails to install
On Wed, 22 Oct 2014 16:58:03 +0200, intrigeri wrote: Holger Levsen wrote (22 Oct 2014 14:06:05 GMT) : BEGIN failed--compilation aborted at /usr/bin/deb-systemd-helper line 85. ... which is shipped by the init-system-helpers package, that depends on perl-modules, that ships File::Path. The attached log shows that init-system-helpers and libvirt-daemon-system are unpacked before perl-modules is upgraded, but after perl itself was upgraded, so with the new @INC set up, it doesn't look anymore for modules in the place where Wheezy's perl-modules ships File::Path (/usr/share/perl/5.14.2). Jenkins? Oh, no, piuparts. Almost :) Still, this somehow reminds me of the equally mysterious #766260. 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: Peter Ratzenbeck: That Time Of Night signature.asc Description: Digital Signature
Bug#766092: systemd: Boot hangs indefinitely
Am 22.10.2014 um 19:08 schrieb Michael Biebl: If you even had more files in /tmp and maybe you have an HDD, it's very well possible, that systemd-tmpfiles will need several minutes. That's why I wanted to know, how long you let the systemd-tmpfiles job run. Case in point: A user at [1] reported, that he had about 2 million files in /tmp and it took several hours to clean that up: * systemd-tmpfiles-setup.service hung like forever during boot * booting from a live system showed that 'ls ./tmp' hangs * 'ls -U ./tmp | wc -l' showed nearly 2 million files in tmp * 'find ./tmp -type l -delete' took several hours to delete the links Cheers, Michael [1] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=764253#22 -- Why is it that all of the instruments seeking intelligent life in the universe are pointed away from Earth? signature.asc Description: OpenPGP digital signature
Bug#753668: How to fix ckeditor
Hello,
I attach the patches of my upcoming upload.
I don't know gitpkg and the correct workflow (I mostly use gbp).
Regards
2014-10-22 13:24 GMT+02:00 Mathieu Parent math.par...@gmail.com:
Hello,
ckeditor from testing/sid is currently not working. It seems that the
build failed to include all the necessary JS snipsets.
I see several options here:
1. Go back to the older working version (3.7 I think). This has the
major drawback of maintaining this security-wise during jessie
lifetime.
2. Use the not-minified and not-closur-ified version. This will be slow
3. Package ckbuilder, and use it. This is a big work, and probably
won't pass NEW before the freeze -10days
4. Fix the current build to behave more like ckbuilder... Any help is welcome!
5. Use the already minified version from upstream. This is probably
not DFSG-friendly
IMO, 1 and 5 should be avoided and I don't know how to take option 4.
I will try to go option 2, and upload to some delayed queue so that it
doesn't enter in sid before 2014-10-26. I have tried option 3 without
success from now (some jars in uptsream are not in debian already,
...)
Thoughts ?
--
Mathieu
--
Mathieu
From 427a268ed4699cfcb01b69a651a18b82a79b15de Mon Sep 17 00:00:00 2001
From: Mathieu Parent math.par...@gmail.com
Date: Wed, 22 Oct 2014 18:30:35 +0200
Subject: [PATCH 1/2] Install complete core sources instead of broken
closure-compiled one (Closes: #753668, #756155)
---
debian/ckeditor.install | 1 +
debian/control | 3 +--
debian/rules| 19 ---
3 files changed, 2 insertions(+), 21 deletions(-)
diff --git a/debian/ckeditor.install b/debian/ckeditor.install
index 1ca4275..e146064 100644
--- a/debian/ckeditor.install
+++ b/debian/ckeditor.install
@@ -1,5 +1,6 @@
*.css /usr/share/javascript/ckeditor
*.js /usr/share/javascript/ckeditor
+core /usr/share/javascript/ckeditor
adapters /usr/share/javascript/ckeditor
lang /usr/share/javascript/ckeditor
plugins /usr/share/javascript/ckeditor
diff --git a/debian/control b/debian/control
index f9448aa..bc25cf8 100644
--- a/debian/control
+++ b/debian/control
@@ -3,8 +3,7 @@ Section: web
Priority: optional
Maintainer: Frank Habermann lordla...@lordlamer.de
Uploaders: Bastien Roucariès roucaries.bastien+deb...@gmail.com
-Build-Depends: debhelper (= 9.0~),
-closure-compiler
+Build-Depends: debhelper (= 9.0~)
Standards-Version: 3.9.5
Homepage: http://ckeditor.com
Vcs-Browser: http://anonscm.debian.org/gitweb/?p=collab-maint/ckeditor.git
diff --git a/debian/rules b/debian/rules
index 8934235..ab16558 100755
--- a/debian/rules
+++ b/debian/rules
@@ -6,28 +6,9 @@ export CK_BASE = core/ckeditor_base
%:
dh $@
-override_dh_auto_build:
- dh_auto_build
-
- # manually build ckeditor.js from core/ckeditor_base.min.js
- closure-compiler --js ${CK_BASE}.js --js_output_file ${CK_BASE}.min.js
- sed -e '/^\/\/[[:space:]]*AUTOGENERATED by debian/{r core/ckeditor_base.min.js' -e 'h;}' \
- -e '$${x;/./{x;q0};x;q1}' 'ckeditor.js' ckeditor.js.inc
-
-
-override_dh_clean:
- dh_clean
- test ! -f ${CK_BASE}.min.js || rm -rf ${CK_BASE}.min.js
- test ! -f ckeditor.js.inc || rm -rf ckeditor.js.inc
-
override_dh_install:
dh_install
- # manually override ckeditor.js from core/ckeditor_base.min.js
- cp -f ckeditor.js.inc debian/ckeditor/usr/share/javascript/ckeditor/ckeditor.js
-
- # remove internal file
- find debian/ckeditor/usr/share/javascript/ckeditor -type f -name '_*' | xargs rm -f
# remove build file
find debian/ckeditor/usr/share/javascript/ckeditor -type f -name 'build-config.js' | xargs rm -f
# remove extra LICENSE.md
--
2.1.1
From c2887156bb9f9a87bc89ad970adcb4cca59fd9a3 Mon Sep 17 00:00:00 2001
From: Mathieu Parent math.par...@gmail.com
Date: Wed, 22 Oct 2014 18:43:20 +0200
Subject: [PATCH 2/2] Changelog for previous commit
---
debian/changelog | 8
1 file changed, 8 insertions(+)
diff --git a/debian/changelog b/debian/changelog
index 22173de..9479f30 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,11 @@
+ckeditor (4.4.4+dfsg1-1.1) unstable; urgency=medium
+
+ * Non-maintainer upload.
+ * Install complete core sources instead of broken closure-compiled one
+(Closes: #753668, #756155)
+
+ -- Mathieu Parent sath...@debian.org Wed, 22 Oct 2014 18:43:11 +0200
+
ckeditor (4.4.4+dfsg1-1) unstable; urgency=high
* New upstream release.
--
2.1.1
Bug#764253: system-config-printer: Creates millions of ppd symlinks
Hi Till, On 22.10.2014 18:14, Till Kamppeter wrote: I have forwarded this report to Tim Waugh from Red Hat, original author of system-config-printer and he has answered me the following: [...] Thanks for forwarding this upstream. For the two bugs you mentioned there are fixes now: Thus I think there are two bugs here: * cups should not create files with wrong permissions in /etc/cups/ppd CUPS STR #4500: https://cups.org/str.php?L4500 Yes, this fixes the cups side of the problem. * scp-dbus-service should not start an infinite loop creating millions of symlinks in /tmp just because the permissions in /etc/cups/ppd are wrong https://git.fedorahosted.org/cgit/system-config-printer.git/commit/?h=1.4.xid=9a81dd1de3afaf30eec92045429029103823b577 I can confirm that this prevents the infinite loop. The temporary files are still left behind in /tmp upon failure, but as long as that are not millions, it doesn't matter. The only strange thing is that scp-dbus-service gets triggered by simply printing. So can you please try what Tim suggests: -- Run scp-dbus-service --debug before printing, and see which D-Bus call it receives. Or watch dbus-monitor --session. -- and post your results here? Thanks. There is a DBus call explicitly starting this service: method call sender=:1.37 - dest=org.freedesktop.DBus serial=4 path=/org/freedesktop/DBus; interface=org.freedesktop.DBus; member=StartServiceByName string org.fedoraproject.Config.Printing This is caused by the scp applet: /usr/share/system-config-printer/applet.py If this applet is not running, scp-dbus-service is not started upon printing. Best regards, Andreas -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#766394: libfishsound: FTBFS on s390, block propagation to testing next stable release
Package: libfishsound Version: 1.0.0-3 Severity: serious The test suite fail to work on s390x, blocking the build from succeeding on this architecture. This block the current version in unstable from entering testing. The log from the build failure can be seen on URL: https://buildd.debian.org/status/logs.php?pkg=libfishsoundarch=s390x . This is the relevant part: make[5]: Entering directory '/«PKGBUILDDIR»/src/tests' PASS: comment-test PASS: noop PASS: encdec-comments FAIL: encdec-audio make[6]: Entering directory '/«PKGBUILDDIR»/src/tests' make[6]: Nothing to be done for 'all'. make[6]: Leaving directory '/«PKGBUILDDIR»/src/tests' Testsuite summary for # TOTAL: 4 # PASS: 3 # SKIP: 0 # XFAIL: 0 # FAIL: 1 # XPASS: 0 # ERROR: 0 See src/tests/test-suite.log make[5]: *** [test-suite.log] Error 1 -- Happy hacking Petter Reinholdtsen -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#766395: emacs/gnus: Uses s_client to for SSL.
Package: emacs23 Severity: serious Tags: security Hi, It has come to my attention that Gnus is using s_client to set up SSL connections to retrieve email. Please stop using that. s_client is a debug tool, it does not set up a secure connection, it ignores all errors and just continues. It also doesn't do checks it should be doing. This is all documented behaviour. Please get rid of all documentation, configurations and examples that tell you how to set it up using s_client. I've also seen examples adding -ssl2 and -ssl3 which is really really broken. Kurt -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: cloning 766395, reassign -1 to emacs24
Processing commands for cont...@bugs.debian.org: clone 766395 -1 Bug #766395 [emacs23] emacs/gnus: Uses s_client to for SSL. Bug 766395 cloned as bug 766397 reassign -1 emacs24 Bug #766397 [emacs23] emacs/gnus: Uses s_client to for SSL. Bug reassigned from package 'emacs23' to 'emacs24'. Ignoring request to alter found versions of bug #766397 to the same values previously set Ignoring request to alter fixed versions of bug #766397 to the same values previously set thanks Stopping processing here. Please contact me if you need assistance. -- 766395: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=766395 766397: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=766397 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#764666: marked as done (ccache: Trigger cycle causes dpkg to fail processing)
Your message dated Wed, 22 Oct 2014 19:48:42 + with message-id e1xh1ti-00075l...@franck.debian.org and subject line Bug#764666: fixed in ccache 3.1.10-1 has caused the Debian Bug report #764666, regarding ccache: Trigger cycle causes dpkg to fail processing 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.) -- 764666: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=764666 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: ccache Version: 3.1.9-1 Severity: serious Hi! This package introduces a trigger cycle, that while it might currently not be visible in most cases it will suddenly make dpkg abort (as per the spec) once #671711 is fixed in dpkg 1.17.17 to be uploaded later today. The problem is that ccache, installs interests on /usr/lib/gcc which is provided by (say) gcc-4.9. Then ccache depends on libc6, depends on libgcc1, depends on libc6 and gcc-4.9-base. And gcc-4.9 depends on gcc-4.9-base and libc6 among others. When several of those are unpacked on the same run, and the trigger gets activated dpkg cannot proceed due to the trigger cycle and needs to bail out, which is not a very nice upgrade path. The solution to the above is to simply switch the triggers to their noawait variants. In this case from «interest» to «interest-noawait». Thanks, Guillem ---End Message--- ---BeginMessage--- Source: ccache Source-Version: 3.1.10-1 We believe that the bug you reported is fixed in the latest version of ccache, 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 764...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Joel Rosdahl j...@debian.org (supplier of updated ccache 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, 22 Oct 2014 21:20:54 +0200 Source: ccache Binary: ccache Architecture: source amd64 Version: 3.1.10-1 Distribution: unstable Urgency: medium Maintainer: Y Giridhar Appaji Nag app...@debian.org Changed-By: Joel Rosdahl j...@debian.org Description: ccache - Compiler cache for fast recompilation of C/C++ code Closes: 764666 Changes: ccache (3.1.10-1) unstable; urgency=medium . * Update Vcs-git and Vcs-Browser to use anonscm.debian.org * New upstream release 3.1.10 * Switch to interest-noawait dpkg triggers (closes: #764666) * Bump Standards-Version to 3.9.6 (no changes) Checksums-Sha1: fac339a9f5c29f7f37662754e24d660cb99c7f9d 1920 ccache_3.1.10-1.dsc 06264d5838622f30d36a1e4b9f1469c85b7d2c3b 240932 ccache_3.1.10.orig.tar.xz 0c534e33b72155f2af89c85b7ec793cf741c200c 10620 ccache_3.1.10-1.debian.tar.xz 0f604bb77f3f93b38af4e56159b61402c7b9112c 90778 ccache_3.1.10-1_amd64.deb Checksums-Sha256: ff210cbe91616ccc7af434be30a837c365ca5fa81b08e65bbbda28cc0a31bfa4 1920 ccache_3.1.10-1.dsc 88439f43d3b426ab435afdf69a808511bada4de3a8a9527426bc4fbf6cb02857 240932 ccache_3.1.10.orig.tar.xz e463a56308a1a4467c1a08c929079c1398881a8994835526c67a2a9af2c696d7 10620 ccache_3.1.10-1.debian.tar.xz a72ad711c732e60457511c646ff3fe5e6e12bc1537f53b0522c41651e8edc032 90778 ccache_3.1.10-1_amd64.deb Files: 3f96521faabe761abff05106d5e4d8b2 1920 devel optional ccache_3.1.10-1.dsc 20cd43818f84e3208fb4859e9679060e 240932 devel optional ccache_3.1.10.orig.tar.xz b53293675e0d411aaf2bc330913271fa 10620 devel optional ccache_3.1.10-1.debian.tar.xz 9b9af518e1cae1de8975dbf3abcdc06d 90778 devel optional ccache_3.1.10-1_amd64.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1 iQIcBAEBCAAGBQJUSAVhAAoJEJlt2gdVlK24rGkP/0h8fIXafuriAo5GfMPhrm/E robaXcZDrtqk6n+lydTKQrB4i4sQhMvxvHUqi7CnkjvOxl54AwIbUCaA/1obg1hI a0+j5I/Vnr7Fd9TAx7SErqAiRQwse2tvc2sOgmBpUZDn/qpLb7yDHZwQe5NKbDyU oDfgQB7Y68PjUb4hc340Odl27EAgykaEAUYhHs9bSJTWtaVF+F9tlZ7MVSb/OM75 UgWT40FLSCmvtxStlhzHL6CRPOiIlCpSRArGEVgLEripep6tDo62+lmuPzh1zwIr AxxHUpwNRch8FFVwp+370eIimRVhEpOka9bS4ptfr0klb6VgtWtbRDYXx4z758pJ xHnJuQCO9EVHmgoqG2hn+NznjoTQAhgJWfcYO4aDY1mOKqrXsmfNZOOPKRMYtU24 PsHkCyyRKrO1E82IEkUJbPZ2rOSe2kiPF1N/6YlBXA9XF8UPZ3WYXAUMXZZzDoYn IHOTFtqnQEg4T/+rQZpOKOABOOixz8DhAE31ZQx7p7qQYHxwsKiIDfIs8YwjbGYz XwT6fMemF1QAr2sr3QL0v42q3jUimbQbr/UxBgoAkzZwiz9XyZCKZAHivafocRvV
Bug#766397: Bug#766395: emacs/gnus: Uses s_client to for SSL.
[When possible, please preserve the -forwarded address in any replies.] The following issue was just reported against emacs23 in Debian, and from a quick glance, it looks like 24.4 still uses s_client, so if this is a problem, it's perhaps still relevant. Kurt Roeckx k...@roeckx.be writes: It has come to my attention that Gnus is using s_client to set up SSL connections to retrieve email. Please stop using that. s_client is a debug tool, it does not set up a secure connection, it ignores all errors and just continues. It also doesn't do checks it should be doing. This is all documented behaviour. Please get rid of all documentation, configurations and examples that tell you how to set it up using s_client. I've also seen examples adding -ssl2 and -ssl3 which is really really broken. Thanks -- Rob Browning rlb @defaultvalue.org and @debian.org GPG as of 2011-07-10 E6A9 DA3C C9FD 1FF8 C676 D2C4 C0F0 39E9 ED1B 597A GPG as of 2002-11-03 14DD 432F AE39 534D B592 F9A0 25C8 D377 8C7E 73A4 -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#766397: marked as forwarded (emacs/gnus: Uses s_client to for SSL.)
Your message dated Wed, 22 Oct 2014 15:02:17 -0500 with message-id 87zjcnj2k6@trouble.defaultvalue.org has caused the report #766397, regarding emacs/gnus: Uses s_client to for SSL. to be marked as having been forwarded to the upstream software author(s) emacs-de...@gnu.org (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.) -- 766397: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=766397 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- [When possible, please preserve the -forwarded address in any replies.] The following issue was just reported against emacs23 in Debian, and from a quick glance, it looks like 24.4 still uses s_client, so if this is a problem, it's perhaps still relevant. Kurt Roeckx k...@roeckx.be writes: It has come to my attention that Gnus is using s_client to set up SSL connections to retrieve email. Please stop using that. s_client is a debug tool, it does not set up a secure connection, it ignores all errors and just continues. It also doesn't do checks it should be doing. This is all documented behaviour. Please get rid of all documentation, configurations and examples that tell you how to set it up using s_client. I've also seen examples adding -ssl2 and -ssl3 which is really really broken. Thanks -- Rob Browning rlb @defaultvalue.org and @debian.org GPG as of 2011-07-10 E6A9 DA3C C9FD 1FF8 C676 D2C4 C0F0 39E9 ED1B 597A GPG as of 2002-11-03 14DD 432F AE39 534D B592 F9A0 25C8 D377 8C7E 73A4---End Message---
Bug#766397: Bug#766395: emacs/gnus: Uses s_client to for SSL.
Rob Browning r...@defaultvalue.org writes: The following issue was just reported against emacs23 in Debian, and from a quick glance, it looks like 24.4 still uses s_client, so if this is a problem, it's perhaps still relevant. Oh, and the link (for the emacs24 bug cloned from the emacs23 bug) is here: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=766397 Thanks -- Rob Browning rlb @defaultvalue.org and @debian.org GPG as of 2011-07-10 E6A9 DA3C C9FD 1FF8 C676 D2C4 C0F0 39E9 ED1B 597A GPG as of 2002-11-03 14DD 432F AE39 534D B592 F9A0 25C8 D377 8C7E 73A4 -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#766397: Bug#766395: emacs/gnus: Uses s_client to for SSL.
[When possible, please preserve the -forwarded address in any replies.] The following issue was just reported against emacs23 in Debian, and from a quick glance, it looks like 24.4 still uses s_client, so if this is a problem, it's perhaps still relevant. AFAIK, nowadays Emacs only use s_client if it was not linked against libgnutls (and it can use gnutls-cli instead as well, tho I don't know which of s_client or gnutls-cli is given preference if both are found). Stefan -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: tagging 765838
Processing commands for cont...@bugs.debian.org: tags 765838 + security Bug #765838 [evolution-data-server] Evolution is not able to use TLSv1 or higher (only SSLv3) Added tag(s) security. thanks Stopping processing here. Please contact me if you need assistance. -- 765838: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=765838 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#766397: Bug#766395: emacs/gnus: Uses s_client to for SSL.
Rob Browning r...@defaultvalue.org writes: [When possible, please preserve the -forwarded address in any replies.] The following issue was just reported against emacs23 in Debian, and from a quick glance, it looks like 24.4 still uses s_client, so if this is a problem, it's perhaps still relevant. Kurt Roeckx k...@roeckx.be writes: It has come to my attention that Gnus is using s_client to set up SSL connections to retrieve email. Please stop using that. That only happens if you use :stream ssl. Use :stream tls or :stream starttls instead. Andreas. -- Andreas Schwab, sch...@linux-m68k.org GPG Key fingerprint = 58CA 54C7 6D53 942B 1756 01D3 44D5 214B 8276 4ED5 And now for something completely different. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#740509: marked as done (ifconfig: ioctl(SIOCGIFINFO_IN6): No such device or address)
Your message dated Wed, 22 Oct 2014 21:23:47 + with message-id e1xh3nj-0004of...@franck.debian.org and subject line Bug#740509: fixed in glibc 2.19-12 has caused the Debian Bug report #740509, regarding ifconfig: ioctl(SIOCGIFINFO_IN6): No such device or address 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.) -- 740509: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=740509 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: freebsd-net-tools Version: 9.2+ds1-1+b1 Severity: critical Control: found -1 10.0-3 On this system, ifconfig is unable to bring up network when running on a 10.0 kernel (this happens with 10.0 debian kernels and with kfreebsd-downloader too). The problem appears to be somehow related to ipv6: $ sudo ifconfig -a : flags=8802BROADCAST,SIMPLEX,MULTICAST ifconfig: ioctl(SIOCGIFINFO_IN6): No such device or address : flags=0 ifconfig: ioctl(SIOCGIFINFO_IN6): No such device or address : flags=0 ifconfig: ioctl(SIOCGIFINFO_IN6): No such device or address : flags=8008LOOPBACK,MULTICAST ifconfig: ioctl(SIOCGIFINFO_IN6): No such device or address -- System Information: Debian Release: 7.4 APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: kfreebsd-i386 (i386) Kernel: kFreeBSD 10.0-1-686 Locale: LANG=ca_AD.UTF-8, LC_CTYPE=ca_AD.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages freebsd-net-tools depends on: ii libbsd00.6.0-1 ii libc0.12.18-3 ii libexpat1 2.1.0-4 ii libfreebsd-glue-0 0.2.16 ii libipx29.2+ds2-4 ii libjail1 9.2+ds2-4 ii libkvm610.0-4 ii libmemstat39.2+ds2-4 ii libnetgraph4 9.2+ds2-4 ii libsbuf6 9.2+ds2-4 ii libutil-freebsd-9 9.2+ds2-4 ---End Message--- ---BeginMessage--- Source: glibc Source-Version: 2.19-12 We believe that the bug you reported is fixed in the latest version of glibc, 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 740...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Aurelien Jarno aure...@debian.org (supplier of updated glibc 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, 22 Oct 2014 20:01:11 +0200 Source: glibc Binary: libc-bin libc-dev-bin glibc-doc glibc-source locales locales-all nscd multiarch-support libc6 libc6-dev libc6-dbg libc6-pic libc6-udeb libc6.1 libc6.1-dev libc6.1-dbg libc6.1-pic libc6.1-udeb libc0.3 libc0.3-dev libc0.3-dbg libc0.3-pic libc0.3-udeb libc0.1 libc0.1-dev libc0.1-dbg libc0.1-pic libc0.1-udeb libc6-i386 libc6-dev-i386 libc6-sparc libc6-dev-sparc libc6-sparc64 libc6-dev-sparc64 libc6-s390 libc6-dev-s390 libc6-amd64 libc6-dev-amd64 libc6-powerpc libc6-dev-powerpc libc6-ppc64 libc6-dev-ppc64 libc6-mips32 libc6-dev-mips32 libc6-mipsn32 libc6-dev-mipsn32 libc6-mips64 libc6-dev-mips64 libc0.1-i386 libc0.1-dev-i386 libc6-x32 libc6-dev-x32 libc6-i686 libc6-xen libc0.1-i686 libc0.3-i686 libc0.3-xen libc6.1-alphaev67 libc6-loongson2f libnss-dns-udeb libnss-files-udeb Architecture: source all amd64 Version: 2.19-12 Distribution: unstable Urgency: medium Maintainer: Aurelien Jarno aure...@debian.org Changed-By: Aurelien Jarno aure...@debian.org Description: glibc-doc - GNU C Library: Documentation glibc-source - GNU C Library: sources libc-bin - GNU C Library: Binaries libc-dev-bin - GNU C Library: Development binaries libc0.1- GNU C Library: Shared libraries libc0.1-dbg - GNU C Library: detached debugging symbols libc0.1-dev - GNU C Library: Development Libraries and Header Files libc0.1-dev-i386 - GNU C Library: 32bit development libraries for AMD64 libc0.1-i386 - GNU C Library: 32bit shared libraries for AMD64 libc0.1-i686 - GNU C Library: Shared libraries [i686 optimized] libc0.1-pic - GNU C Library: PIC archive library libc0.1-udeb - GNU C Library: Shared libraries - udeb (udeb) libc0.3- GNU C Library: Shared libraries libc0.3-dbg - GNU C Library: detached debugging symbols libc0.3-dev - GNU C Library: Development Libraries and Header Files libc0.3-i686 - GNU C Library: Shared libraries [i686 optimized]
Bug#765882: marked as done (freebsd-net-tools: ifconfig ioctl siocaifaddr)
Your message dated Wed, 22 Oct 2014 21:23:47 + with message-id e1xh3nj-0004of...@franck.debian.org and subject line Bug#740509: fixed in glibc 2.19-12 has caused the Debian Bug report #740509, regarding freebsd-net-tools: ifconfig ioctl siocaifaddr 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.) -- 740509: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=740509 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: freebsd-net-tools Version: jessie/sid Severity: important Dear Maintainer, *** Reporter, please consider answering these questions, where appropriate *** I saw a bug report of this same problem from feb, claiming it was fixed in the latest package, it isnt or the problem is something else but either way,the network is completely dead after an upgrade to jessie on Kfreebsd, the network shows up using ifconfig, but it has no IP4 address, and when I restart the network it says it cant bring it up, but it is up, I tried adding a static address , and that didnt work either, so the box is dead you cant fix things with out internet. *** End of the template - remove these template lines *** -- 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.16-2-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash ---End Message--- ---BeginMessage--- Source: glibc Source-Version: 2.19-12 We believe that the bug you reported is fixed in the latest version of glibc, 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 740...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Aurelien Jarno aure...@debian.org (supplier of updated glibc 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, 22 Oct 2014 20:01:11 +0200 Source: glibc Binary: libc-bin libc-dev-bin glibc-doc glibc-source locales locales-all nscd multiarch-support libc6 libc6-dev libc6-dbg libc6-pic libc6-udeb libc6.1 libc6.1-dev libc6.1-dbg libc6.1-pic libc6.1-udeb libc0.3 libc0.3-dev libc0.3-dbg libc0.3-pic libc0.3-udeb libc0.1 libc0.1-dev libc0.1-dbg libc0.1-pic libc0.1-udeb libc6-i386 libc6-dev-i386 libc6-sparc libc6-dev-sparc libc6-sparc64 libc6-dev-sparc64 libc6-s390 libc6-dev-s390 libc6-amd64 libc6-dev-amd64 libc6-powerpc libc6-dev-powerpc libc6-ppc64 libc6-dev-ppc64 libc6-mips32 libc6-dev-mips32 libc6-mipsn32 libc6-dev-mipsn32 libc6-mips64 libc6-dev-mips64 libc0.1-i386 libc0.1-dev-i386 libc6-x32 libc6-dev-x32 libc6-i686 libc6-xen libc0.1-i686 libc0.3-i686 libc0.3-xen libc6.1-alphaev67 libc6-loongson2f libnss-dns-udeb libnss-files-udeb Architecture: source all amd64 Version: 2.19-12 Distribution: unstable Urgency: medium Maintainer: Aurelien Jarno aure...@debian.org Changed-By: Aurelien Jarno aure...@debian.org Description: glibc-doc - GNU C Library: Documentation glibc-source - GNU C Library: sources libc-bin - GNU C Library: Binaries libc-dev-bin - GNU C Library: Development binaries libc0.1- GNU C Library: Shared libraries libc0.1-dbg - GNU C Library: detached debugging symbols libc0.1-dev - GNU C Library: Development Libraries and Header Files libc0.1-dev-i386 - GNU C Library: 32bit development libraries for AMD64 libc0.1-i386 - GNU C Library: 32bit shared libraries for AMD64 libc0.1-i686 - GNU C Library: Shared libraries [i686 optimized] libc0.1-pic - GNU C Library: PIC archive library libc0.1-udeb - GNU C Library: Shared libraries - udeb (udeb) libc0.3- GNU C Library: Shared libraries libc0.3-dbg - GNU C Library: detached debugging symbols libc0.3-dev - GNU C Library: Development Libraries and Header Files libc0.3-i686 - GNU C Library: Shared libraries [i686 optimized] libc0.3-pic - GNU C Library: PIC archive library libc0.3-udeb - GNU C Library: Shared libraries - udeb (udeb) libc0.3-xen - GNU C Library: Shared libraries [Xen version] libc6 - GNU C Library: Shared libraries libc6-amd64 - GNU C Library: 64bit Shared libraries for AMD64
Bug#760450: marked as done (libc6-prof is unusable)
Your message dated Wed, 22 Oct 2014 21:23:47 +
with message-id e1xh3nj-0004od...@franck.debian.org
and subject line Bug#760450: fixed in glibc 2.19-12
has caused the Debian Bug report #760450,
regarding libc6-prof is unusable
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.)
--
760450: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=760450
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
---BeginMessage---
Package: libc6-prof
Version: 2.19-10
Severity: grave
The library from libc6-prof package is unusable.
I'm compiling the simple example program:
int main(void)
{
return sleep(3);
}
If I follow directly the suggestion from the README.Debian, I get the
following error:
$ gcc -g -pg test.c -static-libgcc -lc_p
/usr/bin/ld: dynamic STT_GNU_IFUNC symbol `strcmp' with pointer equality
in
`/usr/lib/gcc/x86_64-linux-gnu/4.9/../../../x86_64-linux-gnu/libc_p.a(strcmp.op)'
can not be used when making an executable; recompile with -fPIE and
relink with -pie
collect2: error: ld returned 1 exit status
I was able to make executable using one of the following compile lines:
$ gcc -g -pg test.c -nodefaultlibs -lc_p -lgcc_eh -lc_p
or
$ gcc -g -pg test.c -nodefaultlibs -Wl,--start-group -lc_p -lgcc_eh
-Wl,--end-group
However the resulting executable segfaults:
$ ./a.out
Segmentation fault
$ valgrind --quiet ./a.out
==1440== Invalid read of size 4
==1440==at 0x459DBB: __mcount_internal (in /tmp/tt/t/a.out)
==1440==by 0x4347D3: mcount (in /tmp/tt/t/a.out)
==1440==by 0x400F48: ??? (in /tmp/tt/t/a.out)
==1440==by 0xFFF000387: ???
==1440== Address 0x18 is not stack'd, malloc'd or (recently) free'd
==1440==
==1440==
==1440== Process terminating with default action of signal 11 (SIGSEGV)
==1440== Access not within mapped region at address 0x18
==1440==at 0x459DBB: __mcount_internal (in /tmp/tt/t/a.out)
==1440==by 0x4347D3: mcount (in /tmp/tt/t/a.out)
==1440==by 0x400F48: ??? (in /tmp/tt/t/a.out)
==1440==by 0xFFF000387: ???
==1440== If you believe this happened as a result of a stack
==1440== overflow in your program's main thread (unlikely but
==1440== possible), you can try to increase the size of the
==1440== main thread stack using the --main-stacksize= flag.
==1440== The main thread stack size used in this run was 8388608.
Segmentation fault
-- System Information:
Debian Release: jessie/sid
APT prefers testing
APT policy: (500, 'testing')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 3.14-1-amd64 (SMP w/8 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Versions of packages libc6-prof depends on:
ii libc6 2.19-10
libc6-prof recommends no packages.
libc6-prof suggests no packages.
-- no debconf information
---End Message---
---BeginMessage---
Source: glibc
Source-Version: 2.19-12
We believe that the bug you reported is fixed in the latest version of
glibc, 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 760...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Aurelien Jarno aure...@debian.org (supplier of updated glibc 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, 22 Oct 2014 20:01:11 +0200
Source: glibc
Binary: libc-bin libc-dev-bin glibc-doc glibc-source locales locales-all nscd
multiarch-support libc6 libc6-dev libc6-dbg libc6-pic libc6-udeb libc6.1
libc6.1-dev libc6.1-dbg libc6.1-pic libc6.1-udeb libc0.3 libc0.3-dev
libc0.3-dbg libc0.3-pic libc0.3-udeb libc0.1 libc0.1-dev libc0.1-dbg
libc0.1-pic libc0.1-udeb libc6-i386 libc6-dev-i386 libc6-sparc libc6-dev-sparc
libc6-sparc64 libc6-dev-sparc64 libc6-s390 libc6-dev-s390 libc6-amd64
libc6-dev-amd64 libc6-powerpc libc6-dev-powerpc libc6-ppc64 libc6-dev-ppc64
libc6-mips32 libc6-dev-mips32 libc6-mipsn32 libc6-dev-mipsn32 libc6-mips64
libc6-dev-mips64 libc0.1-i386 libc0.1-dev-i386 libc6-x32 libc6-dev-x32
libc6-i686 libc6-xen libc0.1-i686 libc0.3-i686 libc0.3-xen libc6.1-alphaev67
libc6-loongson2f libnss-dns-udeb libnss-files-udeb
Architecture: source all amd64
Version: 2.19-12
Distribution: unstable
Urgency:
Bug#762404: marked as done (glibc: FTBFS[kfreebsd] tst-execstack fails; expected behaviour)
Your message dated Wed, 22 Oct 2014 21:23:47 + with message-id e1xh3nj-0004op...@franck.debian.org and subject line Bug#762404: fixed in glibc 2.19-12 has caused the Debian Bug report #762404, regarding glibc: FTBFS[kfreebsd] tst-execstack fails; expected behaviour 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.) -- 762404: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=762404 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: glibc Version: 2.19.11 Severity: serious User: debian-...@lists.debian.org Usertags: kfreebsd Hi, During a test rebuild for kfreebsd 10.1 transition, I noticed that glibc fails to build from source already on kfreebsd 10.0: Encountered regressions that don't match expected failures (debian/testsuite-checking/expected-results-x86_64-kfreebsd-gnu-libc): tst-execstack-needed.out, Error 1 tst-execstack.out, Error 1 tst-execstack-prog.out, Error 1 TEST tst-execstack-needed.out: DSO called ok (local 0x7fffd2b0, trampoline 0x7fffd2b1) TEST tst-execstack.out: executable stacks allowed DSO called ok (local 0x7fffd290, trampoline 0x7fffd291) executable stacks allowed threads waiting DSO called ok (local 0x7fffd200, trampoline 0x7fffd201) Stack address remains the same: 0x7fffe000 TEST tst-execstack-prog.out: DSO called ok (local 0x7fffd2c0, trampoline 0x7fffd2c1) That shows kfreebsd-amd64; it fails similarly on kfreebsd-i386. This is actually by design. The test program is killed due to a new default setting of: kern.elf64.nxstack: 1 kern.elf32.nxstack: 1 Similar to SElinux enforcement of allow_execstack=0 - something the test program checks for and knows how to handle. So I suggest the test could be fixed for any version of kfreebsd by checking the appropriate sysctl. The Debian buildds run a 9.0 kernel with nxstack=0 so are not affected *yet*, but the package will start to FTBFS as soon as they are updated to a jessie kernel, which would of course be a problem for future s-p-u and jessie-security. (Hence the severity). Thanks. -- System Information: Debian Release: jessie/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'stable') Architecture: kfreebsd-amd64 (x86_64) Kernel: kFreeBSD 9.0-2-amd64-xenhvm-ipsec 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--- Source: glibc Source-Version: 2.19-12 We believe that the bug you reported is fixed in the latest version of glibc, 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. Aurelien Jarno aure...@debian.org (supplier of updated glibc 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, 22 Oct 2014 20:01:11 +0200 Source: glibc Binary: libc-bin libc-dev-bin glibc-doc glibc-source locales locales-all nscd multiarch-support libc6 libc6-dev libc6-dbg libc6-pic libc6-udeb libc6.1 libc6.1-dev libc6.1-dbg libc6.1-pic libc6.1-udeb libc0.3 libc0.3-dev libc0.3-dbg libc0.3-pic libc0.3-udeb libc0.1 libc0.1-dev libc0.1-dbg libc0.1-pic libc0.1-udeb libc6-i386 libc6-dev-i386 libc6-sparc libc6-dev-sparc libc6-sparc64 libc6-dev-sparc64 libc6-s390 libc6-dev-s390 libc6-amd64 libc6-dev-amd64 libc6-powerpc libc6-dev-powerpc libc6-ppc64 libc6-dev-ppc64 libc6-mips32 libc6-dev-mips32 libc6-mipsn32 libc6-dev-mipsn32 libc6-mips64 libc6-dev-mips64 libc0.1-i386 libc0.1-dev-i386 libc6-x32 libc6-dev-x32 libc6-i686 libc6-xen libc0.1-i686 libc0.3-i686 libc0.3-xen libc6.1-alphaev67 libc6-loongson2f libnss-dns-udeb libnss-files-udeb Architecture: source all amd64 Version: 2.19-12 Distribution: unstable Urgency: medium Maintainer: Aurelien Jarno aure...@debian.org Changed-By: Aurelien Jarno aure...@debian.org Description: glibc-doc - GNU C Library: Documentation glibc-source - GNU C Library: sources libc-bin - GNU C Library: Binaries libc-dev-bin - GNU C Library: Development binaries libc0.1- GNU C Library: Shared libraries libc0.1-dbg - GNU C Library: detached debugging symbols libc0.1-dev - GNU C Library: Development
Bug#762195: marked as done (libc6: libpthread: hardware-assisted lock elision hazardous on x86)
Your message dated Wed, 22 Oct 2014 21:23:47 + with message-id e1xh3nj-0004oj...@franck.debian.org and subject line Bug#762195: fixed in glibc 2.19-12 has caused the Debian Bug report #762195, regarding libc6: libpthread: hardware-assisted lock elision hazardous on x86 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.) -- 762195: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=762195 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: libc6 Version: 2.19-0experimental0 Severity: grave Justification: causes non-serious data loss libpthread-2.19 has HLE (hardware-assisted lock elision) support. Unfortunately, on Intel-based x86 processors, the use of HLE is currently hazardous. Summary: Use of HLE on all current Intel Haswell processors (the only x86 processors with HLE support so far) can cause unpredictable system behaviour, including the possibility of hangs and memory corruption. Updating the microcode on these Intel Haswell processors when Intel TSX is in use by libpthread will cause running processes linked to libpthread to be killed with SIGILL. This issue is, AFAIK, impossible to work around in the kernel. Since glibc uses the cpuid instruction directly, the kernel cannot prevent libpthreads from attempting to use Intel TSX. Non-free will work around the microcode update issue by enforcing that all microcode updates be done in the initramfs (i.e. require a reboot to apply, and require initramfs). Unfortunately, this is not going to be enough as most users don't have intel-microcode installed in their Intel-based systems, and therefore would still be at risk of data loss or data corruption due to erratum HSD136. Please disable hardware-assisted lock elision (HLE) on X86/X86-64 Intel Haswell Processors in libpthreads. Details: On unpatched Intel processors, HLE will hit erratum HSD136: HSD136. Software Using Intel® TSX May Result in Unpredictable System Behavior Problem: Under a complex set of internal timing condit ions and system events, software using the Intel TSX (Transactional Synchronization Ex tensions) instructions may result in unpredictable system behavior. (Erratum description from: Desktop 4th Generation Intel Core Processor Family Specification Update, June 2013, #328899-001). This erratum is serious enough for Intel to take the PR hit and withdraw the feature on all Haswell cores, including the just-launched Haswell-EP E5v3 Xeons. (ref: http://www.anandtech.com/show/8376/intel-disables-tsx-instructions-erratum-found-in-haswell-haswelleep-broadwelly ). On patched Intel processors, Intel TSX will be disabled by the microcode. When disabled, any Intel TSX instructions will generate an illegal opcode trap. Intel TSX support supposedly can be re-enabled *during system boot* by the UEFI firmware through an undisclosed method. Unfortunately, the act of updating the microcode will immediately disable Intel TSX, causing all running processors linked to libpthread-2.19 to trap and crash with SIGILL: [ 43.606830] microcode: CPU0 sig=0x306c3, pf=0x2, revision=0x1a [ 43.608466] microcode: CPU0 updated to revision 0x1c, date = 2014-07-03 [ 43.608494] microcode: CPU1 sig=0x306c3, pf=0x2, revision=0x1a [ 43.609327] microcode: CPU1 updated to revision 0x1c, date = 2014-07-03 [ 43.609352] do_trap: 267 callbacks suppressed [ 43.609354] traps: rs:main Q:Reg[1343] trap invalid opcode ip:7f32abd0b7ab sp:7f32a9062848 error:0 [ 43.609355] microcode: CPU2 sig=0x306c3, pf=0x2, revision=0x1a [ 43.609358] in libpthread-2.19.so[7f32abcfa000+18000] [ 43.610204] microcode: CPU2 updated to revision 0x1c, date = 2014-07-03 [ 43.610225] microcode: CPU3 sig=0x306c3, pf=0x2, revision=0x1a [ 43.611081] microcode: CPU3 updated to revision 0x1c, date = 2014-07-03 [ 43.611507] traps: systemd[1] trap invalid opcode ip:7f844f84a7ab sp:7fff2ccf7e28 error:0 in libpthread-2.19.so[7f844f839000+18000] [...] Ref: https://bugs.launchpad.net/intel/+bug/1370352 It is unknown at this time what will happen on future microcode updates. It is entirely possible that the act of updating the microcode will always reset Intel TSX to its default disabled state, regardless of whether the BIOS had force-enabled it or not at boot. This is the reason why I will drop support for microcode updates outside of the initramfs in non-free. Therefore, due to erratum HSD136 and the lack of widespread use of microcode updates, libpthread-2.19 must stop using HLE on the problematic Intel processors. Here's the data required for the blacklist: CPUID signature : family :
Bug#766394: marked as done (libfishsound: FTBFS on s390, block propagation to testing next stable release)
Your message dated Wed, 22 Oct 2014 21:24:14 + with message-id e1xh3oa-00055w...@franck.debian.org and subject line Bug#766394: fixed in libfishsound 1.0.0-4 has caused the Debian Bug report #766394, regarding libfishsound: FTBFS on s390, block propagation to testing next stable release 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.) -- 766394: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=766394 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: libfishsound Version: 1.0.0-3 Severity: serious The test suite fail to work on s390x, blocking the build from succeeding on this architecture. This block the current version in unstable from entering testing. The log from the build failure can be seen on URL: https://buildd.debian.org/status/logs.php?pkg=libfishsoundarch=s390x . This is the relevant part: make[5]: Entering directory '/«PKGBUILDDIR»/src/tests' PASS: comment-test PASS: noop PASS: encdec-comments FAIL: encdec-audio make[6]: Entering directory '/«PKGBUILDDIR»/src/tests' make[6]: Nothing to be done for 'all'. make[6]: Leaving directory '/«PKGBUILDDIR»/src/tests' Testsuite summary for # TOTAL: 4 # PASS: 3 # SKIP: 0 # XFAIL: 0 # FAIL: 1 # XPASS: 0 # ERROR: 0 See src/tests/test-suite.log make[5]: *** [test-suite.log] Error 1 -- Happy hacking Petter Reinholdtsen ---End Message--- ---BeginMessage--- Source: libfishsound Source-Version: 1.0.0-4 We believe that the bug you reported is fixed in the latest version of libfishsound, 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 766...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Petter Reinholdtsen p...@debian.org (supplier of updated libfishsound 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, 22 Oct 2014 22:57:21 +0200 Source: libfishsound Binary: libfishsound1 libfishsound1-dev libfishsound1-dbg Architecture: source amd64 Version: 1.0.0-4 Distribution: unstable Urgency: low Maintainer: Debian Xiph.org Maintainers pkg-xiph-ma...@lists.alioth.debian.org Changed-By: Petter Reinholdtsen p...@debian.org Description: libfishsound1 - simple API that wraps Xiph.Org audio codecs libfishsound1-dbg - simple API that wraps Xiph.Org audio codecs (debugging informatio libfishsound1-dev - simple API that wraps Xiph.Org audio codecs (development files) Closes: 766394 Changes: libfishsound (1.0.0-4) unstable; urgency=low . [ Martin Steghöfer ] * Format patches for gbp-pq. * Fix incompatible flac callback types (Closes: #766394). Thank you Ron Lee for the tip on how to fix the s390x build problem. Checksums-Sha1: 91d96f66178a8b484037437dcbb2019a905a2763 1563 libfishsound_1.0.0-4.dsc 810ddb9e2659fbebf57e61e6269a50b16c228a0a 5636 libfishsound_1.0.0-4.debian.tar.xz 1c4080217035686b0a5c6fe3e495e8fddee81c27 21056 libfishsound1_1.0.0-4_amd64.deb 234059e6e16def2b3b17b54a77aca1df80bd440a 38840 libfishsound1-dev_1.0.0-4_amd64.deb d68d01cd5900cae1c9c67c028fd4c277354616fb 42340 libfishsound1-dbg_1.0.0-4_amd64.deb Checksums-Sha256: c2fe34edffa36a72c77808ccebcaea8add7be1550992951c5a58ad0b081f2824 1563 libfishsound_1.0.0-4.dsc f876064da9c21381f4601561627ec2d7198a12d4db5c7cf720e4a9c7f9b1b15c 5636 libfishsound_1.0.0-4.debian.tar.xz 02c9319183380477682e459877312ef23c7105011cd939be3aaa8f3978b278d0 21056 libfishsound1_1.0.0-4_amd64.deb ab3b4e0ac3a8a27212a1d257a8df56a855d721502bf3142650a5eaf582412895 38840 libfishsound1-dev_1.0.0-4_amd64.deb 54867b185b6bd70e6b25b85c01f6d6c963c17aed0570f28818ee648a676754d9 42340 libfishsound1-dbg_1.0.0-4_amd64.deb Files: a17b693be5b8518769808c6efb2fd9e7 1563 sound optional libfishsound_1.0.0-4.dsc c332f96ea8ac3cef792d4f11c75640d4 5636 sound optional libfishsound_1.0.0-4.debian.tar.xz dd531c06ef574a1e73fcc64b87d5c39f 21056 libs optional libfishsound1_1.0.0-4_amd64.deb
Bug#766251: flightgear fails to start with *** stack smashing detected ***
The debian/patches/series mechanism won't patch DOS-line-ending files
such as Effects/model-combined-transparent.eff, so the attached manually
applies the patch in debian/rules instead.
It also downgrades -ai, -aircrafts to Recommends as suggested earlier; I
have quickly tested that FlightGear works without these, but nothing
beyond that. (This is independent of the bug fix, but if we're going to
do it, we should probably do it when we're uploading it anyway.)
diff --git a/debian/changelog b/debian/changelog
index fe90b25..b856dbc 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,10 @@
+flightgear-data (3.0.0-2) UNRELEASED; urgency=medium
+
+ * Fix type mismatch crash. Closes: #766251.
+ * Downgrade -ai, -aircrafts to Recommends.
+
+ -- Rebecca N. Palmer rebecca_pal...@zoho.com Wed, 22 Oct 2014 18:27:01
+0100
+
flightgear-data (3.0.0-1) unstable; urgency=low
[ Markus Wanner ]
diff --git a/debian/control b/debian/control
index 817ed1d..23e0e00 100644
--- a/debian/control
+++ b/debian/control
@@ -64,10 +64,10 @@ Package: flightgear-data-all
Architecture: all
Depends:
flightgear-data-base (= 3.0.0~),
- flightgear-data-ai (= 3.0.0~),
- flightgear-data-aircrafts (= 3.0.0~),
flightgear-data-models (= 3.0.0~),
${misc:Depends}
+Recommends: flightgear-data-ai (= 3.0.0~),
+ flightgear-data-aircrafts (= 3.0.0~)
Description: FlightGear Flight Simulator - virtual package
FlightGear is a free and highly sophisticated flight simulator.
.
diff --git a/debian/patches/766251.patch b/debian/patches/766251.patch
new file mode 100644
index 000..da2d905
--- /dev/null
+++ b/debian/patches/766251.patch
@@ -0,0 +1,19 @@
+Description: Fix type mismatch crash in SGExpression
+
+(This patch is applied in debian/rules rather than debian/patches/series,
+as the latter can't patch a DOS-line-ending file)
+
+Author: Rebecca N. Palmer rebecca_pal...@zoho.com
+Forwarded: not-needed
+Bug-Debian: https://bugs.debian.org/766251
+--- flightgear-data-3.0.0.orig/Effects/model-combined-transparent.eff
flightgear-data-3.0.0/Effects/model-combined-transparent.eff
+@@ -12,7 +12,7 @@ and fallback to plain transparency when
+ and
+ equal
+
float-property/sim/rendering/shaders/model/float-property
+- value type=int0/value
++ value type=float0/value
+ /equal
+ or
+ less-equal
diff --git a/debian/rules b/debian/rules
index 0be03d6..f7f272f 100755
--- a/debian/rules
+++ b/debian/rules
@@ -11,6 +11,8 @@ override_dh_auto_install:
dh_installdirs -pflightgear-data-aiusr/share/games/flightgear
dh_installdirs -pflightgear-data-aircrafts usr/share/games/flightgear
dh_installdirs -pflightgear-data-modelsusr/share/games/flightgear
+#apply patch (can't use debian/patches/series as it can't patch a
DOS-line-ending file)
+ patch -p1 --binary debian/patches/766251.patch
# Contents of flightgear-data-base
cp -av \
@@ -96,6 +98,8 @@ override_dh_auto_install:
$(CURDIR)/debian/flightgear-data-ai/usr/share/games/flightgear/AI/Aircraft/A330-MRTT/COPYING
\
$(CURDIR)/debian/flightgear-data-base/usr/share/games/flightgear/ATC/Chatter/BR/LICENCE.txt
\
$(CURDIR)/debian/flightgear-data-base/usr/share/games/flightgear/Aircraft/Generic/Engines/LICENSE
+#clean up
+ patch -p1 -R --binary debian/patches/766251.patch
Processed: limit source to glib-networking, tagging 762588
Processing commands for cont...@bugs.debian.org: limit source glib-networking Limiting to bugs with field 'source' containing at least one of 'glib-networking' Limit currently set to 'source':'glib-networking' tags 762588 + pending Bug #762588 [glib-networking] glib-networking: sometimes FTBFS: testsuite race conditions Ignoring request to alter tags of bug #762588 to the same tags previously set thanks Stopping processing here. Please contact me if you need assistance. -- 762588: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=762588 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: limit source to glib-networking, tagging 762588
Processing commands for cont...@bugs.debian.org: limit source glib-networking Limiting to bugs with field 'source' containing at least one of 'glib-networking' Limit currently set to 'source':'glib-networking' tags 762588 + pending Bug #762588 [glib-networking] glib-networking: sometimes FTBFS: testsuite race conditions Added tag(s) pending. thanks Stopping processing here. Please contact me if you need assistance. -- 762588: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=762588 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#762588: marked as done (glib-networking: sometimes FTBFS: testsuite race conditions)
Your message dated Wed, 22 Oct 2014 22:03:57 + with message-id e1xh40b-0002tn...@franck.debian.org and subject line Bug#762588: fixed in glib-networking 2.42.0-2 has caused the Debian Bug report #762588, regarding glib-networking: sometimes FTBFS: testsuite race conditions 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.) -- 762588: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=762588 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: glib-networking Version: 2.41.92-2 Severity: serious User: debian-...@lists.debian.org Usertags: kfreebsd Hi, glib-networking has failed 4 attempts to build on kfreebsd-amd64 due to testsuite errors. Firstly, please `export VERBOSE=1` before running `make check`. There is much more detail recorded about failures than is currently output in the build log. I was able to reproduce issues locally about 15% of the time, suggesting a race condition, in three different tests: /tls/connection/client-auth-rehandshake: ** GLib-Net:ERROR:connection.c:413:on_client_connection_close_finish: assertion failed (error == NULL): Error closing socket: Connection reset by peer (g-io-error-quark, 0) Aborted /tls/connection/read-time-out-then-write: ** GLib-Net:ERROR:connection.c:217:on_server_close_finish: assertion failed (error == NULL): Error closing socket: Connection reset by peer (g-io-error-quark, 0) Aborted /tls/connection/close-during-handshake: ** GLib-Net:ERROR:connection.c:215:on_server_close_finish: assertion failed: (error != NULL) Aborted Thanks. -- System Information: Debian Release: jessie/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'stable') Architecture: kfreebsd-amd64 (x86_64) Kernel: kFreeBSD 9.0-2-amd64-xenhvm-ipsec 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--- Source: glib-networking Source-Version: 2.42.0-2 We believe that the bug you reported is fixed in the latest version of glib-networking, 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. Emilio Pozuelo Monfort po...@debian.org (supplier of updated glib-networking 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, 22 Oct 2014 23:41:04 +0200 Source: glib-networking Binary: glib-networking glib-networking-services glib-networking-common glib-networking-dbg glib-networking-tests Architecture: source all amd64 Version: 2.42.0-2 Distribution: unstable Urgency: medium Maintainer: Debian GNOME Maintainers pkg-gnome-maintain...@lists.alioth.debian.org Changed-By: Emilio Pozuelo Monfort po...@debian.org Description: glib-networking - network-related giomodules for GLib glib-networking-common - network-related giomodules for GLib - data files glib-networking-dbg - network-related giomodules for GLib - debugging symbols glib-networking-services - network-related giomodules for GLib - D-Bus services glib-networking-tests - network-related giomodules for GLib - installed tests Closes: 762588 Changes: glib-networking (2.42.0-2) unstable; urgency=medium . * debian/patches/01_connection_test.patch: + Disable tls/connection tests. They are racy and so unreliable. Closes: #762588. * debian/rules: + Set VERBOSE so we get more information when a test fails. Checksums-Sha1: 43f49be5ec196e308920bd07198cc30f1415530b 2661 glib-networking_2.42.0-2.dsc 6f54b0fa70dfee42e4a0226353268401ba100efa 6000 glib-networking_2.42.0-2.debian.tar.xz e55e1b4f6c3fd0e69949e434001b6bd2d4f6d68d 52128 glib-networking-common_2.42.0-2_all.deb 2a19cd8a86b9e1c7b26ee448aa21dec9e0696226 51900 glib-networking_2.42.0-2_amd64.deb c42a1862120b4e5a975f01cb94ddca025afe9f91 16986 glib-networking-services_2.42.0-2_amd64.deb 873aca6e68a45783e3c7e5b2e95b71f06bf31ad6 209354 glib-networking-dbg_2.42.0-2_amd64.deb 7bc7996163e4b2f2b60dab733e205926cad333ae 66256 glib-networking-tests_2.42.0-2_amd64.deb Checksums-Sha256: 67225118b74c8d5bc9385eeb6347ddbf4bc0297290a5d31a1addf1d29b990889 2661
Bug#766419: python3-requests: Version 2.4 of python-requests / python3-requests breaks virtualenv.
Package: python3-requests Version: 2.4.3-1 Severity: critical Justification: breaks unrelated software Dear Maintainer, The new version of python3-requests/python-requests (2.4.3) breaks pip which in turn breaks virtualenv (see bug #766261). The request.compat module used to export a IncompleteRead module which virtualenv uses. But this symbol is no longer defined there and thus any package relying on it is prone to break. Temporarily removing this package from unstable or uploading a version of the package that is patched so it exports the symbol in question again, seems advisable considering the amount of reverse dependency this package has (a quick grep in /usr/lib/python3/dist-package show no other package on my system but I have only a few of those reverse dependencies installed). Looking at pip source code on [1], it seems this symbol is no longer used so you may also want to coordinate with the pip maintainer (there are no newer release of pip, as of today). Thanks in advance, Nicolas. [1]: https://github.com/pypa/pip (depends on requests 2.4.1 cached in _vendor sub-directory) -- System Information: Debian Release: jessie/sid APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'unstable'), (500, 'testing'), (500, 'stable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.16-2-amd64 (SMP w/4 CPU cores) Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages python3-requests depends on: ii ca-certificates 20141019 ii python3-chardet 2.3.0-1 ii python3-urllib3 1.9.1-2 pn python3:any none python3-requests recommends no packages. Versions of packages python3-requests suggests: pn python3-ndg-httpsclient none pn python3-openssl none ii python3-pyasn1 0.1.7-1 -- 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
