Processed: tagging 778375
Processing commands for cont...@bugs.debian.org: > tags 778375 - unreproducible Bug #778375 [apt-transport-https] apt-transport-https: segfaults Removed tag(s) unreproducible. > thanks Stopping processing here. Please contact me if you need assistance. -- 778375: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=778375 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 778375
Processing commands for cont...@bugs.debian.org: > tags 778375 + patch Bug #778375 [apt-transport-https] apt-transport-https: segfaults Added tag(s) patch. > thanks Stopping processing here. Please contact me if you need assistance. -- 778375: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=778375 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#760998: Acknowledgement (network-manager: auto restarts)
Processing commands for cont...@bugs.debian.org: > severity 760998 serious Bug #760998 [network-manager] network-manager: auto restarts Severity set to 'serious' from 'normal' > thanks Stopping processing here. Please contact me if you need assistance. -- 760998: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=760998 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#778733: marked as done (bind9: CVE-2015-1349 named crash)
Your message dated Thu, 19 Feb 2015 04:33:42 + with message-id and subject line Bug#778733: fixed in bind9 1:9.9.5.dfsg-9 has caused the Debian Bug report #778733, regarding bind9: CVE-2015-1349 named crash 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.) -- 778733: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=778733 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- package: src:bind9 severity: serious tags: security A new security issue was disclosed for bind9: https://security-tracker.debian.org/tracker/CVE-2015-1349 --- End Message --- --- Begin Message --- Source: bind9 Source-Version: 1:9.9.5.dfsg-9 We believe that the bug you reported is fixed in the latest version of bind9, 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 778...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Michael Gilbert (supplier of updated bind9 package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Thu, 19 Feb 2015 03:42:21 + Source: bind9 Binary: bind9 bind9utils bind9-doc host bind9-host libbind-dev libbind9-90 libdns100 libisc95 liblwres90 libisccc90 libisccfg90 dnsutils lwresd libbind-export-dev libdns-export100 libdns-export100-udeb libisc-export95 libisc-export95-udeb libisccfg-export90 libisccfg-export90-udeb libirs-export91 libirs-export91-udeb Architecture: source all Version: 1:9.9.5.dfsg-9 Distribution: unstable Urgency: high Maintainer: LaMont Jones Changed-By: Michael Gilbert Description: bind9 - Internet Domain Name Server bind9-doc - Documentation for BIND bind9-host - Version of 'host' bundled with BIND 9.X bind9utils - Utilities for BIND dnsutils - Clients provided with BIND host - Transitional package libbind-dev - Static Libraries and Headers used by BIND libbind-export-dev - Development files for the exported BIND libraries libbind9-90 - BIND9 Shared Library used by BIND libdns-export100 - Exported DNS Shared Library libdns-export100-udeb - Exported DNS library for debian-installer (udeb) libdns100 - DNS Shared Library used by BIND libirs-export91 - Exported IRS Shared Library libirs-export91-udeb - Exported IRS library for debian-installer (udeb) libisc-export95 - Exported ISC Shared Library libisc-export95-udeb - Exported ISC library for debian-installer (udeb) libisc95 - ISC Shared Library used by BIND libisccc90 - Command Channel Library used by BIND libisccfg-export90 - Exported ISC CFG Shared Library libisccfg-export90-udeb - Exported ISC CFG library for debian-installer (udeb) libisccfg90 - Config File Handling Library used by BIND liblwres90 - Lightweight Resolver Library used by BIND lwresd - Lightweight Resolver Daemon Closes: 778733 Changes: bind9 (1:9.9.5.dfsg-9) unstable; urgency=high . * Fix CVE-2015-1349: named crash due to managed key rollover, primarily only affecting setups using DNSSEC (closes: #778733). Checksums-Sha1: 9a4ad05114af61c623ae02796cfa7a56acc015cb 4113 bind9_9.9.5.dfsg-9.dsc 604224c1589939e7e16f39a18638056838173efc 108147 bind9_9.9.5.dfsg-9.diff.gz 716541eba7020c5dc233cba0dc5c8ab859bf0590 338882 bind9-doc_9.9.5.dfsg-9_all.deb c449a163372f6984aac5e46b8f1dba0ca6d620c6 22654 host_9.9.5.dfsg-9_all.deb Checksums-Sha256: 3da08a0375b7bc2b9097b783a4eaec7e32531fd2e07316bdded805752fb06860 4113 bind9_9.9.5.dfsg-9.dsc 0a373a5926d444808f1eb84a1cb5f72ce3a0778295915875af38b93be6076442 108147 bind9_9.9.5.dfsg-9.diff.gz 0b15148952edccf48a4c2071ac825f30ff8f8069c2ba160eb37434eb7dd1eb6d 338882 bind9-doc_9.9.5.dfsg-9_all.deb 9100ea2c1ced729053f0bb3bcb2b5cb5cb78861fdfff00eaad5bbdc7c27637ad 22654 host_9.9.5.dfsg-9_all.deb Files: 184a8167a465939f18d6e43c2178f003 4113 net optional bind9_9.9.5.dfsg-9.dsc 78a09e7a1f70763574fd139923b7aa69 108147 net optional bind9_9.9.5.dfsg-9.diff.gz 04f937ae12a50b8b07ae6677d5edc3b5 338882 doc optional bind9-doc_9.9.5.dfsg-9_all.deb bed8fe2e13f70ad2445a2be412a44d08 22654 net standard host_9.9.5.dfsg-9_all.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1 iQQcBAEBCgAGBQJU5WQUAAoJELjWss0C1vRzAzIf/0H5Euk4bXc0Z938r0LYTh4w z1O2dOOQJ4G/gKe2MYizAhgMKPdAO30fqt4r7qaPblJOBQCLZx9XL4M
Processed: user debian-secur...@lists.debian.org, usertagging 778733, tagging 778733 ...
Processing commands for cont...@bugs.debian.org: > user debian-secur...@lists.debian.org Setting user to debian-secur...@lists.debian.org (was car...@debian.org). > usertags 778733 + tracked There were no usertags set. Usertags are now: tracked. > tags 778733 + upstream fixed-upstream Bug #778733 [src:bind9] bind9: CVE-2015-1349 named crash Added tag(s) upstream and fixed-upstream. > found 778733 1:9.7.3.dfsg-1 Bug #778733 [src:bind9] bind9: CVE-2015-1349 named crash Marked as found in versions bind9/1:9.7.3.dfsg-1. > fixed 778733 1:9.8.4.dfsg.P1-6+nmu2+deb7u4 Bug #778733 [src:bind9] bind9: CVE-2015-1349 named crash Marked as fixed in versions bind9/1:9.8.4.dfsg.P1-6+nmu2+deb7u4. > thanks Stopping processing here. Please contact me if you need assistance. -- 778733: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=778733 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#778712: libparted2: Breakage of RAID GPT header
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 On 02/18/2015 05:15 PM, jnqnfe wrote: >> Then you need to only manipulate md126 and ignore sdb and sdc. >> Most of what you seem to be reporting involves looking directly >> at the individual disks, which you must not do as that will >> present a partial/corrupt view of the raid array. In other >> words, if the first few sectors of the raid array map to sdb, >> then sdb will appear to have a partition table in its sector 0 >> that describes a disk that is twice the size, since this >> partition table is actually describing the raid array and not the >> individual disk. > > I am not doing anything at all to the member disks, I am only > manipulating the array (mb126) and providing the ouput of fsdisk -l > / parted -l (with unnecessary info about other disks removed). All of the error messages shown in the logs you sent so far involve the raw disks ( sdb, etc ) rather than the raid array. You certainly should not be running fdisk or parted on the raw disk, and responding to the error messages by saying it should fix the problem ( since the problem is only a result of looking at an individual disk instead of the whole array ). >> The one thing you mention that I can't write off as user error is >> "but parted is not and seems to be forcibly applying what it >> believes to be correct (ignoring the fact that it was only asked >> to display info, not modify anything)". Can you provide more >> details here? Exactly what command did you run and what changed >> before vs. after? Parted should not be modifying anything on the >> disk unless you tell it to. Normally it will throw a warning >> telling you something is wrong with the disk and ask if you want >> it to fix it and you have to answer "fix" for it to modify the >> disk. > > I did only exactly as described in my previous message, nothing > more, nothing less. You stated that parted modified the disk when you didn't tell it to, but did not show exactly what command you gave that lead to this, and more importantly, what if any, error messages parted threw and how you responded to them. -BEGIN PGP SIGNATURE- Version: GnuPG v1 iQEcBAEBCgAGBQJU5WZLAAoJENRVrw2cjl5RIEwIAKgjCMaHtYDruSejfB5I60F9 opO+FGClLTJPML6ggREF8hDM+K7eFpWCa4buWTvKUBix1oNjeLvWJVfu5XoSIQbt A+XX+YyBGjYuXXApXUV5W1A9P/beKhAGzs0anAZu6pZEirCcxQINjexjPua8PlZM PSuEppd/Bpmnw26CK/h2lrFNHJs1c9vzcnLOwMlT0ZzVXVAFFK90z8cxVo/kSvVb z5Sp5NtD/WWcdc5nTs6m1yEgs/3E/G3OB9VUF3+2c9dwXj5FXnEzAMAKN+g2ZKAO zI2TGFQpITPRkP7ij+0XpqH/YaWYLAHGbb0peIbsQHpDuBX+yT16Q3E93Sg56oU= =2m/O -END PGP SIGNATURE- -- 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#776816: Acknowledgement (firmware-realtek: fails to connect after a few suspends (or some uptime?))
Processing control commands: > severity -1 grave Bug #776816 [firmware-realtek] firmware-realtek: fails to connect after a few suspends (or some uptime?) Severity set to 'grave' from 'normal' > fixed -1 0.36+wheezy.1 Bug #776816 [firmware-realtek] firmware-realtek: fails to connect after a few suspends (or some uptime?) Marked as fixed in versions firmware-nonfree/0.36+wheezy.1. -- 776816: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=776816 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#777341: marked as done (qtbase-opensource-src: libopenvg1-mesa-dev is no longer built by mesa)
Your message dated Thu, 19 Feb 2015 04:20:19 + with message-id and subject line Bug#777341: fixed in qtbase-opensource-src 5.4.0+dfsg-5 has caused the Debian Bug report #777341, regarding qtbase-opensource-src: libopenvg1-mesa-dev is no longer built by mesa 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.) -- 777341: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=777341 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: qtbase-opensource-src Version: 5.3.2+dfsg-4 Severity: serious Tags: sid Justification: fails to build from source (but built successfully in the past) >From https://ftp-master.debian.org/cruft-report-daily.txt: * source package mesa version 10.4.2-2 no longer builds binary package(s): libegl1-mesa-drivers-dbg libopenvg1-mesa libopenvg1-mesa-dbg libopenvg1-mesa-dev on amd64,arm64,armel,armhf,i386,kfreebsd-amd64,kfreebsd-i386,mips,mipsel,powerpc,ppc64el,s390x,sparc - suggested command: dak rm -m "[auto-cruft] NBS (no longer built by mesa)" -s unstable -a amd64,arm64,armel,armhf,i386,kfreebsd-amd64,kfreebsd-i386,mips,mipsel,powerpc,ppc64el,s390x,sparc -p -R -b libegl1-mesa-drivers-dbg libopenvg1-mesa libopenvg1-mesa-dbg libopenvg1-mesa-dev - broken Build-Depends: qtbase-opensource-src: libopenvg1-mesa-dev qtbase-opensource-src will FTBFS in sid once that cruft was removed. Please stop B-D: libopenvg1-mesa-dev Andreas --- End Message --- --- Begin Message --- Source: qtbase-opensource-src Source-Version: 5.4.0+dfsg-5 We believe that the bug you reported is fixed in the latest version of qtbase-opensource-src, 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 777...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Lisandro Damián Nicanor Pérez Meyer (supplier of updated qtbase-opensource-src package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Thu, 19 Feb 2015 00:12:25 -0300 Source: qtbase-opensource-src Binary: libqt5core5a libqt5gui5 libqt5network5 libqt5opengl5 libqt5sql5 libqt5sql5-mysql libqt5sql5-odbc libqt5sql5-psql libqt5sql5-sqlite libqt5sql5-tds libqt5xml5 libqt5dbus5 libqt5test5 libqt5concurrent5 libqt5widgets5 libqt5printsupport5 qtbase5-dev qtbase5-private-dev libqt5opengl5-dev qtbase5-dev-tools qt5-qmake qtbase5-examples qtbase5-dbg qtbase5-dev-tools-dbg qtbase5-examples-dbg qt5-default qtbase5-doc-html Architecture: source amd64 all Version: 5.4.0+dfsg-5 Distribution: experimental Urgency: medium Maintainer: Debian Qt/KDE Maintainers Changed-By: Lisandro Damián Nicanor Pérez Meyer Description: libqt5concurrent5 - Qt 5 concurrent module libqt5core5a - Qt 5 core module libqt5dbus5 - Qt 5 D-Bus module libqt5gui5 - Qt 5 GUI module libqt5network5 - Qt 5 network module libqt5opengl5 - Qt 5 OpenGL module libqt5opengl5-dev - Qt 5 OpenGL library development files libqt5printsupport5 - Qt 5 print support module libqt5sql5 - Qt 5 SQL module libqt5sql5-mysql - Qt 5 MySQL database driver libqt5sql5-odbc - Qt 5 ODBC database driver libqt5sql5-psql - Qt 5 PostgreSQL database driver libqt5sql5-sqlite - Qt 5 SQLite 3 database driver libqt5sql5-tds - Qt 5 FreeTDS database driver libqt5test5 - Qt 5 test module libqt5widgets5 - Qt 5 widgets module libqt5xml5 - Qt 5 XML module qt5-default - Qt 5 development defaults package qt5-qmake - Qt 5 qmake Makefile generator tool qtbase5-dbg - Qt 5 base library debugging symbols qtbase5-dev - Qt 5 base development files qtbase5-dev-tools - Qt 5 base development programs qtbase5-dev-tools-dbg - Qt 5 base binaries debugging symbols qtbase5-doc-html - Qt 5 base HTML documentation qtbase5-examples - Qt 5 base examples qtbase5-examples-dbg - Qt 5 base examples debugging symbols qtbase5-private-dev - Qt 5 base private development files Closes: 777341 778717 Changes: qtbase-opensource-src (5.4.0+dfsg-5) experimental; urgency=medium . [ Pino Toscano ] * Replace patch hurd_opengl_incldir.diff with upstream_small-improvements-to-the-hurd-g-mkspec.patch, backport of upstream commit 8f0e84bec513ad28c3ec479053fbc59add3959e1. * Replace patch mips_more_pre-mips32.diff with u
Bug#778626: marked as done (broadcom-sta-dkms: Module build ... was skipped)
Your message dated Thu, 19 Feb 2015 07:38:03 +0400 with message-id <4523495.uRMXBuOhti@yack> and subject line Close has caused the Debian Bug report #778626, regarding broadcom-sta-dkms: Module build ... was skipped 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.) -- 778626: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=778626 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: broadcom-sta-dkms Version: 6.30.223.248-3 Severity: serious Justification: fails to build from source Dear Maintainer, *** Reporter, please consider answering these questions, where appropriate *** * What led up to the situation? Updating my system removed several packets (not your department) and disabled my wlan (that should be yours). Reinstalling the driver didn't work. * What exactly did you do (or not do) that was effective (or ineffective)? Installing broadcom-sta-dkms * What was the outcome of this action? # aptitude install broadcom-sta-dkms Die folgenden NEUEN Pakete werden zusätzlich installiert: broadcom-sta-dkms 0 Pakete aktualisiert, 1 zusätzlich installiert, 0 werden entfernt und 0 nicht aktualisiert. 0 B/2.170 kB an Archiven müssen heruntergeladen werden. Nach dem Entpacken werden 14,4 MB zusätzlich belegt sein. Vormals nicht ausgewähltes Paket broadcom-sta-dkms wird gewählt. (Lese Datenbank ... 373155 Dateien und Verzeichnisse sind derzeit installiert.) Vorbereitung zum Entpacken von .../broadcom-sta-dkms_6.30.223.248-3_all.deb ... Entpacken von broadcom-sta-dkms (6.30.223.248-3) ... broadcom-sta-dkms (6.30.223.248-3) wird eingerichtet ... Loading new broadcom-sta-6.30.223.248 DKMS files... First Installation: checking all kernels... Building only for 3.16.0-4-amd64 Module build for the currently running kernel was skipped since the kernel source for this kernel does not seem to be installed. --- My running kernelversion is: # uname -a Linux debian 3.16.0-4-amd64 #1 SMP Debian 3.16.7-ckt4-3 (2015-02-03) x86_64 GNU/Linux Some installed packages and their versions: # dpkg -l|grep linux-image ii linux-image-3.16.0-4-amd643.16.7-ckt4-3 amd64Linux 3.16 for 64-bit PCs ii linux-image-amd64 3.16+63 amd64Linux for 64-bit PCs (meta-package) # dpkg -l|grep linux-headers ii linux-headers-3.16.0-4-amd64 3.16.7-ckt4-3 amd64Header files for Linux 3.16.0-4-amd64 ii linux-headers-3.16.0-4-common 3.16.7-ckt4-3 amd64Common header files for Linux 3.16.0-4 ii linux-headers-amd64 3.16+63 amd64Header files for Linux amd64 configuration (meta-package) # dpkg -l|grep linux-source ii linux-source 3.16+63 all Linux kernel source (meta-package) ii linux-source-3.16 3.16.7-ckt4-3 all Linux kernel source for version 3.16 with Debian patches # dpkg -l|grep dkms ii broadcom-sta-dkms 6.30.223.248-3 all dkms source for the Broadcom STA Wireless driver ii dkms 2.2.0.3-2 all Dynamic Kernel Module Support Framework # dpkg -l|grep build-ess ii build-essential 11.7 amd64Informational list of build-essential packages # dpkg -l|grep kbuild ii linux-kbuild-3.16 3.16-3 amd64Kbuild infrastructure for Linux 3.16 # dpkg -l|grep wireless-t ii wireless-tools30~pre9-8 amd64Tools for manipulating Linux Wireless Extensions The source package was lying in /usr/src/ as a tar.xz. I unxz-ed and untar-ed it, but that didn't help neither. * What outcome did you expect instead? Compiling of the modules -- System Information: Debian Release: 8.0 APT prefers testing-updates APT policy: (500, 'testing-updates'), (500, 'testing') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.16.0-4-amd64 (SMP w/2 CPU cores) Locale: LANG=de_DE@euro, LC_CTYPE=de_DE@euro (charmap=ISO-8859-15) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages broadcom-sta-dkms depends on: ii dkms 2.2.0.3-2 Versions
Bug#778733: bind9: CVE-2015-1349 named crash
package: src:bind9 severity: serious tags: security A new security issue was disclosed for bind9: https://security-tracker.debian.org/tracker/CVE-2015-1349 -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#763148: Prevent migration to jessie
Hi Paul, It's more like the other way around. Because it is determined that ffmpeg won't get into Jessie, we make no effort of making it work on Jessie. You can however try cloning the source repo and manually disabling x265 support, and it should work (assuming all other dependencies are satisfied). Timothy On Wed, Feb 18, 2015 at 5:21 PM Paul Elliott wrote: > > > Just to see what the fuss was about, and because I wanted > to use ffmpeg, I grabbed the unstable source and tried to > build with "sbuild -d testing". > > I got an undefied dependancy on libx265-dev. > > Sure enough I checked debian packages and libx265-dev > is in unstable but not testing. > > I am testing, i386. > > > Could it be that ffmpeg is blocked for this other reason, > and the whole discussion on this bug is pointless? > > Best Wishes to all. > > > -- > Paul Elliott 1(512)837-1096 > pelli...@blackpatchpanel.com PMB 181, 11900 Metric Blvd > Suite J > http://www.free.blackpatchpanel.com/pme/ Austin TX 78758-3117 >
Bug#763148: Prevent migration to jessie
Just to see what the fuss was about, and because I wanted to use ffmpeg, I grabbed the unstable source and tried to build with "sbuild -d testing". I got an undefied dependancy on libx265-dev. Sure enough I checked debian packages and libx265-dev is in unstable but not testing. I am testing, i386. Could it be that ffmpeg is blocked for this other reason, and the whole discussion on this bug is pointless? Best Wishes to all. -- Paul Elliott 1(512)837-1096 pelli...@blackpatchpanel.com PMB 181, 11900 Metric Blvd Suite J http://www.free.blackpatchpanel.com/pme/ Austin TX 78758-3117 signature.asc Description: Digital signature
Bug#777722: xdg-open: another command injection vulnerability
On Wed, Feb 18, 2015 at 9:13 AM, Salvatore Bonaccorso wrote:
> Hi,
>
> On Wed, Feb 11, 2015 at 11:10:24PM +0100, Jiri Horner wrote:
>> Problem is caused by name collision in local variables, which are
>> apparently not very local in this case (maybe also dash problem?)
>
> Just an additional comment on this: It looks actually as intended that
> the initial value is inherited, the manpage state:
>
> Variables may be declared to be local to a function by using a
> local command. This should appear as the first statement of a
> function, and the syntax is
>
>local [variable | -] ...
>
> Local is implemented as a builtin command.
>
> When a variable is made local, it inherits the initial value and
> exported and readonly flags from the variable with the same name
> in the surrounding scope, if there is one. Otherwise, the
> variable is initially unset. The shell uses dynamic scoping, so
> that if you make the variable x local to function f, which then
> calls func‐ tion g, references to the variable x made inside g
> will refer to the variable x declared inside f, not to the global
> variable named x.
I think this may be a design flaw in dash; seems bash doesn't suffer
the same issue:
$ cat testme
testme() {
x=backfromthedead
local x
echo $x
}
testme
$ bash testme
$ dash testme
backfromthedead
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#776913: marked as done (flightgear-data-all: new upstream version needed by flightgear/experimental)
Your message dated Wed, 18 Feb 2015 23:25:24 +
with message-id
and subject line Bug#776913: fixed in flightgear-data 3.4.0+dfsg-0~exp1
has caused the Debian Bug report #776913,
regarding flightgear-data-all: new upstream version needed by
flightgear/experimental
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.)
--
776913: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=776913
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: flightgear-data-all
Version: 3.2.0-1~exp1
Severity: serious
Tags: experimental
User: debian...@lists.debian.org
Usertags: piuparts
Control: affects -1 flightgear
Hi,
flightgear/experimental is not installable:
The following packages have unmet dependencies:
flightgear : Depends: flightgear-data-all (>= 3.2.0~) but it is not
going to be installed
Andreas
--- End Message ---
--- Begin Message ---
Source: flightgear-data
Source-Version: 3.4.0+dfsg-0~exp1
We believe that the bug you reported is fixed in the latest version of
flightgear-data, 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 776...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Markus Wanner (supplier of updated flightgear-data 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, 18 Feb 2015 22:59:19 +0100
Source: flightgear-data
Binary: flightgear-data-base flightgear-data-ai flightgear-data-aircrafts
flightgear-data-models flightgear-data-all
Architecture: source all
Version: 3.4.0+dfsg-0~exp1
Distribution: experimental
Urgency: medium
Maintainer: Debian FlightGear Crew
Changed-By: Markus Wanner
Description:
flightgear-data-ai - FlightGear Flight Simulator -- standard AI data
flightgear-data-aircrafts - FlightGear Flight Simulator -- standard aircraft
flightgear-data-all - FlightGear Flight Simulator - virtual package
flightgear-data-base - FlightGear Flight Simulator -- base files
flightgear-data-models - FlightGear Flight Simulator -- standard models
Closes: 760077 760083 760698 766251 776913
Changes:
flightgear-data (3.4.0+dfsg-0~exp1) experimental; urgency=medium
.
[ Florent Rougon ]
* New upstream release 3.2 (Closes: #766251).
* Remove 766251.patch which is not necessary anymore.
* Adjust dependencies on flightgear.
* Drop the obsolete dummy packages fgfs-*.
* debian/rules: replace "find ... -exec {} \;" with
"find ... -execdir '{}' +" for more efficiency when calling chmod on
many files.
* Drop the obsolete debian/links file (link from
/usr/share/doc/fgfs-base/Docs to /usr/share/games/FlightGear/Docs).
.
[ Markus Wanner ]
* New upstream almost-release 3.4, tagged 3.4.0~rc99 to avoid confusion
with the eventual real 3.4.0 (Closes: #776913, #760698, #760077,
#760083).
* Drop patch translation-update-pt.diff, it got applied upstream.
* Drop references to Textures.high from d/rules. These directories
no longer exist. Add the new webgui.
* Update debian/copyright and debian/watch.
* Repack upstream's tarball: remove jquery, flot and leaflet from
webgui's 3rdparty. Also strip the unneeded copies of tzdata and the
liberation font.
* Add the necessary JavaScript dependencies, instead. Add patch
use-system-jslibs.diff to deal with the version-less jquery file
name of libjs-jquery.
* Add missing-sources for the sprintf js library.
* Bump S-V: no changes needed.
* Update the watch file.
* Use dh_link rather than the former dance in postinst/prerm. Drop
these two for flightgear-data-base.
* Drop another unnecessary LICENSE file.
Checksums-Sha1:
24efc1621dade6576f013db9d58fd970dae79884 3061
flightgear-data_3.4.0+dfsg-0~exp1.dsc
f3a060dcea357c6e083ebcbfc2caabd5d99abe67 1143853944
flightgear-data_3.4.0+dfsg.orig.tar.bz2
54412ea94df633dffd9ca4d33515a0e6389af8ad 14232
flightgear-data_3.4.0+dfsg-0~exp1.debian.tar.xz
1a2c24a3d9c07c8e8cdd17aa7b434fac933890b6 579416918
flightgear-data-base_3.4.0+dfsg-0~exp1_all.deb
98e8e4b9742fb765a9bb0c336f4724f9131e3506 191260798
flightgear-data-ai_3.4.0+dfsg-0~exp1_all.deb
d0496907e1e6879977a3fc5d30ce44a0ec83fd4f 162279396
flig
Processed: notfound 777581 in 1:3.5-9, found 777581 in 1:3.6~+rc2-2, notfound 777582 in 1:3.5-9 ...
Processing commands for cont...@bugs.debian.org: > notfound 777581 1:3.5-9 Bug #777581 [python-clang-3.6,python-clang-3.7] python-clang-3.7 and python-clang-3.6: error when trying to install together There is no source info for the package 'python-clang-3.6' at version '1:3.5-9' with architecture '' There is no source info for the package 'python-clang-3.7' at version '1:3.5-9' with architecture '' Unable to make a source version for version '1:3.5-9' No longer marked as found in versions 1:3.5-9. > found 777581 1:3.6~+rc2-2 Bug #777581 [python-clang-3.6,python-clang-3.7] python-clang-3.7 and python-clang-3.6: error when trying to install together There is no source info for the package 'python-clang-3.7' at version '1:3.6~+rc2-2' with architecture '' Marked as found in versions llvm-toolchain-3.6/1:3.6~+rc2-2. > notfound 777582 1:3.5-9 Bug #777582 [python-lldb-3.6,python-lldb-3.7] python-lldb-3.7 and python-lldb-3.6: error when trying to install together There is no source info for the package 'python-lldb-3.6' at version '1:3.5-9' with architecture '' There is no source info for the package 'python-lldb-3.7' at version '1:3.5-9' with architecture '' Unable to make a source version for version '1:3.5-9' No longer marked as found in versions 1:3.5-9. > found 777582 1:3.6~+rc2-2 Bug #777582 [python-lldb-3.6,python-lldb-3.7] python-lldb-3.7 and python-lldb-3.6: error when trying to install together There is no source info for the package 'python-lldb-3.7' at version '1:3.6~+rc2-2' with architecture '' Marked as found in versions llvm-toolchain-3.6/1:3.6~+rc2-2. > found 769146 20150108~5.7p1-1 Bug #769146 [openntpd] openntpd: fails to upgrade from 'sid' - trying to overwrite /etc/apparmor.d/usr.sbin.ntpd Marked as found in versions openntpd/20150108~5.7p1-1. > found 619370 0.1.7 Bug #619370 [apt-p2p] apt-p2p: fails to purge - command (deluser|adduser) in postrm not found Marked as found in versions apt-p2p/0.1.7. > notfound 619370 jessie/None Bug #619370 [apt-p2p] apt-p2p: fails to purge - command (deluser|adduser) in postrm not found The source jessie and version None do not appear to match any binary packages No longer marked as found in versions jessie/None. > thanks Stopping processing here. Please contact me if you need assistance. -- 619370: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=619370 769146: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=769146 777581: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=777581 777582: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=777582 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#778712: libparted2: Breakage of RAID GPT header
On Wed, 2015-02-18 at 16:35 -0500, Phillip Susi wrote: > On 2/18/2015 4:05 PM, jnqnfe wrote: > > Background = I have a 'fake-raid' RAID0 array, > > created from two HDDs using my motherboard firmware. This is not > > used for root, just data. > > FYI, unless you have to dual boot with windows, you should avoid using > fakeraid and stick with conventional linux software raid, which is > much better supported. Fine, fair enough, I am not dual booting so I may switch as you suggest. Thanks for the tip. > > sdb and sdc are the RAID members here and the RAID device is > > md126. > > Then you need to only manipulate md126 and ignore sdb and sdc. Most > of what you seem to be reporting involves looking directly at the > individual disks, which you must not do as that will present a > partial/corrupt view of the raid array. In other words, if the first > few sectors of the raid array map to sdb, then sdb will appear to have > a partition table in its sector 0 that describes a disk that is twice > the size, since this partition table is actually describing the raid > array and not the individual disk. I am not doing anything at all to the member disks, I am only manipulating the array (mb126) and providing the ouput of fsdisk -l / parted -l (with unnecessary info about other disks removed). > The one thing you mention that I can't write off as user error is "but > parted is not and seems to be forcibly applying what it believes to be > correct (ignoring the fact that it was only asked to display info, not > modify anything)". Can you provide more details here? Exactly what > command did you run and what changed before vs. after? Parted should > not be modifying anything on the disk unless you tell it to. Normally > it will throw a warning telling you something is wrong with the disk > and ask if you want it to fix it and you have to answer "fix" for it > to modify the disk. I did only exactly as described in my previous message, nothing more, nothing less. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#776137: sudo: fails to switch between sudo and sudo-ldap: chown: cannot access '/etc/sudoers': No such file or directory
On 2015-02-18 22:32, Bdale Garbee wrote: > Christian Kastner writes: > >> Bdale, once such a confirmation (or another fix) is in, how would you >> like to proceed? I could help with the RT communication again > > Sure. I'm willing to merge a patch and do uploads, but need to know > which path they want me to use since the sudo in unstable has diverged > From the one in jessie, I'm assuming it will be t-p-u again, as 1.8.10p3-1+deb8u2. The debdiff I attached is already prepared accordingly. > and there's another new upstream release I plan to upload to unstable soon'ish. Oh, I forgot: as this also affects unstable, once a second confirmation comes in that the proposed fix is good, it should be applied there, too. Regards, Christian -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#776137: sudo: fails to switch between sudo and sudo-ldap: chown: cannot access '/etc/sudoers': No such file or directory
Christian Kastner writes: > Bdale, once such a confirmation (or another fix) is in, how would you > like to proceed? I could help with the RT communication again Sure. I'm willing to merge a patch and do uploads, but need to know which path they want me to use since the sudo in unstable has diverged From the one in jessie, and there's another new upstream release I plan to upload to unstable soon'ish. Bdale signature.asc Description: PGP signature
Bug#778712: libparted2: Breakage of RAID GPT header
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 2/18/2015 4:05 PM, jnqnfe wrote: > Background = I have a 'fake-raid' RAID0 array, > created from two HDDs using my motherboard firmware. This is not > used for root, just data. FYI, unless you have to dual boot with windows, you should avoid using fakeraid and stick with conventional linux software raid, which is much better supported. > sdb and sdc are the RAID members here and the RAID device is > md126. Then you need to only manipulate md126 and ignore sdb and sdc. Most of what you seem to be reporting involves looking directly at the individual disks, which you must not do as that will present a partial/corrupt view of the raid array. In other words, if the first few sectors of the raid array map to sdb, then sdb will appear to have a partition table in its sector 0 that describes a disk that is twice the size, since this partition table is actually describing the raid array and not the individual disk. The one thing you mention that I can't write off as user error is "but parted is not and seems to be forcibly applying what it believes to be correct (ignoring the fact that it was only asked to display info, not modify anything)". Can you provide more details here? Exactly what command did you run and what changed before vs. after? Parted should not be modifying anything on the disk unless you tell it to. Normally it will throw a warning telling you something is wrong with the disk and ask if you want it to fix it and you have to answer "fix" for it to modify the disk. -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.17 (MingW32) iQEcBAEBAgAGBQJU5QWEAAoJENRVrw2cjl5RwnkH/0jvimRzKxUZjFait+KVZQgW gq2m6MVJYiDZLX3ajGZj2mxQNVu2RFqDn+YwqAWeDtrQEj/B0TXJC3RbBJpoN3Ao 5kH+lU2Z+YihRDpQMst8VGt1MVA6izcapN1uVeJOcLB2wICSGd0WcjAn8ROSnZNS o/7hXLh7dhxQZT+2HsTpmWa6pLEVvyBeQ8u2giNB0w8he75qv4/AxCFYAdVqhr4Y nNfC9zzCtcOGExu12GyigEpWUPlxUcyGsYzaQRR2hG1Vv7LKBsDBsok3qAag033E DyhyCWDj8NJk1WQIW2ZyVjhcskSyl59Oatd7X3TGSqr2L7yaHV+QAA5Cng+A9fw= =WuvR -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#768945: marked as done (busybox lzo implementation suffers from CVE-2014-4607 flaw)
Your message dated Wed, 18 Feb 2015 21:20:16 + with message-id and subject line Bug#768945: fixed in busybox 1:1.22.0-9+deb8u1 has caused the Debian Bug report #768945, regarding busybox lzo implementation suffers from CVE-2014-4607 flaw 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.) -- 768945: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=768945 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: busybox Version: 1:1.22.0-5 Severity: serious Tags: security patch upstream fixed-upstream Busybox embeds mini-lzo library implementation which suffers from CVE-2014-4607 -- integer overflow with memory corruption potential and a risk of (remote) code execution, see http://www.openwall.com/lists/oss-security/2014/06/26/20 for details. This flaw has been fixed in busybox upstream in commit a9dc7c2f59dc5e92870d2d46316ea5c1f14740e3. /mjt --- End Message --- --- Begin Message --- Source: busybox Source-Version: 1:1.22.0-9+deb8u1 We believe that the bug you reported is fixed in the latest version of busybox, 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 768...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Mehdi Dogguy (supplier of updated busybox 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: Tue, 17 Feb 2015 18:29:33 +0100 Source: busybox Binary: busybox busybox-static busybox-udeb busybox-syslogd udhcpc udhcpd Architecture: source amd64 all Version: 1:1.22.0-9+deb8u1 Distribution: jessie Urgency: medium Maintainer: Debian Install System Team Changed-By: Mehdi Dogguy Description: busybox- Tiny utilities for small and embedded systems busybox-static - Standalone rescue shell with tons of builtin utilities busybox-syslogd - Provides syslogd and klogd using busybox busybox-udeb - Tiny utilities for the debian-installer (udeb) udhcpc - Provides the busybox DHCP client implementation udhcpd - Provides the busybox DHCP server implementation Closes: 768945 Changes: busybox (1:1.22.0-9+deb8u1) jessie; urgency=medium . * Non-maintainer upload. * lzop-add-overflow-check-CVE-2014-4607.patch (Closes: #768945) Checksums-Sha1: 90923b14cd66e29dde458de8c9e045ffbd92f81a 2225 busybox_1.22.0-9+deb8u1.dsc 5b2a9a78153649e2de916b593a346781260e81a5 55332 busybox_1.22.0-9+deb8u1.debian.tar.xz 6179308501e9b63868ee9b3180aca6ed225d6739 391274 busybox_1.22.0-9+deb8u1_amd64.deb b46db401c9735e0717f68c7e35c0e5b8284211d0 840630 busybox-static_1.22.0-9+deb8u1_amd64.deb 016f8ff3d25b4beb6f980fe00157a9f4aa1b4164 175090 busybox-udeb_1.22.0-9+deb8u1_amd64.udeb 0831ffaec31bbb4b5f2dd6cc8920ad97877c1ea9 23382 busybox-syslogd_1.22.0-9+deb8u1_all.deb ea00f633101df4283e0b85c0368f91b3a8a2b0ae 21478 udhcpc_1.22.0-9+deb8u1_amd64.deb 257f1f2f0415e1cd8081a8a9f13d6f45ada9b046 24242 udhcpd_1.22.0-9+deb8u1_amd64.deb Checksums-Sha256: 8499da25792de43f8a25a10ce4fa5ef4e08654a6d54089840f66d1d172f9afa3 2225 busybox_1.22.0-9+deb8u1.dsc fbf24cd6d7b51003dbe06b897286feaccc94850a135a45e65ecdcb7a095974ef 55332 busybox_1.22.0-9+deb8u1.debian.tar.xz 0bd42544ed2a92c4d298431364de4c22ffa1db2517b8f8dc539f74a385956a99 391274 busybox_1.22.0-9+deb8u1_amd64.deb 83d809a22d765e52390c0bc352fe30e9d1ac7c82fd509e0d779d8289bfc8a53d 840630 busybox-static_1.22.0-9+deb8u1_amd64.deb 8fc4ecc2955d128106aedf8c4b64414636c840c7c384db139946eb649cb150db 175090 busybox-udeb_1.22.0-9+deb8u1_amd64.udeb 99a99d4241297fe97e8e97433bc965e729b95526f3ea8ee0f38512fa627d90e3 23382 busybox-syslogd_1.22.0-9+deb8u1_all.deb ce05c5cd4179c1e36fd33592932cba006b0db3d2f906f295f89c92116b2d9cb0 21478 udhcpc_1.22.0-9+deb8u1_amd64.deb 94e38d4d084dc0b951e0fcb5f7b6b51752dd38182748d4c382409dce171ff2f7 24242 udhcpd_1.22.0-9+deb8u1_amd64.deb Files: 6053856ca2acfae9d17f5aecb7a5dc9b 2225 utils optional busybox_1.22.0-9+deb8u1.dsc 564888c8f8be761049247c88a4cad294 55332 utils optional busybox_1.22.0-9+deb8u1.debian.tar.xz 7cadb8ed0c8219b147bc41f9f6cc5e00 391274 utils optional busybox_1.22.0-9+deb8u1_amd64.deb 276477baa2cf3671287c52834d838458 840630 shells extra busybox-static_1.22.0-9+deb8u1_amd64.deb fb6b1d25ae1fa5d64e8ed1b10950999d 175090
Bug#778712: libparted2: Breakage of RAID GPT header
Package: libparted2 Version: 3.2-6 Severity: grave libparted2 breaks my RAID GPT header! There appears to be a disagreement between parted and fdisk as to the correct size. fdisk is happy after creating a GPT partition table, but parted is not and seems to be forcibly applying what it believes to be correct (ignoring the fact that it was only asked to display info, not modify anything). Having done so however parted is still not happy and now neither is fdisk. Letting parted create the partition table just leaves both unhappy, reporting the same issues. In testing reproducibility of my issue here I deleted and recreated the array, and proceeded to test as documented below, which explains things more clearly. **Please pay particular attention to what happened at the very end of test #3, which is why I marked this as severity grave! I would appreciate a quick turnaround on this issue, so I can get on with actually using this RAID array without fear of breaking it simply by running parted -l or opening gparted. Background = I have a 'fake-raid' RAID0 array, created from two HDDs using my motherboard firmware. This is not used for root, just data. sdb and sdc are the RAID members here and the RAID device is md126. fdisk -l and parted -l output (cut down to only the devices in question) generated during this procedure is attached. Test#1 - gparted = 1) Deleted and recreated the RAID array (in MB firmware). 2) Checked fdisk -l and parted -l (see fdisk1 and parted1 output files). fdisk is happy, parted only complains about unrecognised disk labels. 3) In gparted, with device md126 selected, I asked it to create a GPT partition table. This was done with no errors reported. gparted shows warnings for both sdb and sdc. The warning for sdc is just an unrecognised disk label warning, but the warning against sdb is: "Both the primary and backup GPT tables are corrupt."! Checking fdisk -l, I see an "GPT PMBR size mismatch" error. I created the fdisk2 and parted2 files at this stage. For some reason fdisk now sees a device '/dev/sdb1', with size equal to that of the full array. I had not created any partitions yet. Test#2 - parted = 1) Deleted and recreated the RAID array (in MB firmware). 2) Checked fdisk and parted to make sure things had been reset correctly, they were. 3) Ran: sudo parted /dev/md126 mktable GPT This ran with no errors directly reported. 4) Checked parted -l, which reported the same corruption issue above (see parted3). 5) Checked fdisk -l, which reported the GPT PMBR size mismatch error as before (see fdisk3). Test#3 - fdisk = 1) Deleted and recreated the RAID array (in MB firmware). 2) Checked fdisk and parted to make sure things had been reset correctly, they were. 3) Ran: sudo fdisk /dev/md126 g (create a new empty GPT partition table) v (verify) - no errors, looked good to me w (write) - no errors: "The partition table has been altered. Calling ioctl() to re-read partition table. Syncing disks." 4) Checked fdisk -l output, which looks absolutely fine (see fdisk4). 5) Checked parted -l. This still complains about a corrupt GPT header. (See parted4). 6) Happened to check fdisk -l again, how it's reporting the GPT PMBR size mismatch error from before (See fdisk5). So it seems that the parted -l command here seems to have tried to forcibly correct the issue it was unhappy with, breaking what fdisk seemed to have done correctly. Disk /dev/sdc: 931.5 GiB, 1000204886016 bytes, 1953525168 sectors Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disk /dev/sdb: 931.5 GiB, 1000204886016 bytes, 1953525168 sectors Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disk /dev/md126: 1.8 TiB, 2000381018112 bytes, 3906994176 sectors Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 16384 bytes / 32768 bytes GPT PMBR size mismatch (3906994175 != 1953525167) will be corrected by w(rite). Disk /dev/sdc: 931.5 GiB, 1000204886016 bytes, 1953525168 sectors Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disk /dev/sdb: 931.5 GiB, 1000204886016 bytes, 1953525168 sectors Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disklabel type: dos Disk identifier: 0x Device Boot StartEndSectors Size Id Type /dev/sdb1 1 3906994175 3906994175 1.8T ee GPT Disk /dev/md126: 1.8 TiB, 2000381018112 bytes, 3906994176 sectors Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 16384 bytes / 32768 bytes Disklabel type:
Processed: Re: Bug#778655: doxygen: Doxygen should not enable markdown by default
Processing control commands: > tags -1 + moreinfo Bug #778655 [doxygen] doxygen: Doxygen should not enable markdown by default Added tag(s) moreinfo. -- 778655: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=778655 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#778655: doxygen: Doxygen should not enable markdown by default
Control: tags -1 + moreinfo Hi Ron, Duplicating a bit of our discussion here for keeping track of it. On Wed, Feb 18, 2015 at 09:58:25AM +1030, Ron wrote: > So doxygen 1.8 added support for interpreting markdown, and it does this > in all normal comment blocks before applying the normal doxygen formatting. > > Unfortunately, they also chose to enable this by default, so any package > that is building docs against this version, which didn't update the > doxyconf configuration using this version, to see that this option exists > and to turn it off if it breaks the generated documentation, is going to > run a fairly high chance of generating fairly horribly broken docs. > > A quick canary for the extent of this problem is to search for: > 'warning: unexpected command endcode' > > Which went by uncommented on (or I assume inspected) in logs such as > was posted to https://bugs.debian.org/680896 and many other places. > > This is just one fairly common way this fails horribly, resulting in > all the comments *above* a @code section being treated as code, and > the code section itself being dumped literally to the output - but > there are quite a few other ways this will generate awful unreadable > documentation when markdown syntax is inadvertently applied to an > existing codebase. Thanks for reporting this. I was not aware! > Unless we want to ship with a lot of fairly useless -doc packages, > it seems like this should probably be disabled by default, until > people have become more aware of the problem and have taken steps > to avoid it in their own source. I found a lot of build logs that > show people having this problem, but no discussion of the cause, > the impact, or the fix. I suspect a lot of people who build -doc > packages rarely or never actually read them themselves ... Flipping the default of MARKDOWN_SUPPORT in Debian won't happen for the following reasons: * Deviating from upstream is bad. Of course, this means that convincing upstream to change the default necessitates revisiting this decision. * Changing this in the doxygen package won't fix any documentation: I don't expect many packages to be uploaded after a doxygen upload and binNMUs cannot be used as most documentation resides in arch:all packages. Thus it should be easier to just fix build-rdeps of doxygen. > Fixing the ones that are already broken is probably going to be > something of a major operation in its own right, but the mood in > #d-d seemed to be that we should start by limiting the damage here > and then tackle that part separately. And this is where the moreinfo tag comes into place: The information of which packages actually are broken is missing entirely. Before this bug becomes actionable in any way, the purported damage needs to be understood. Please remove the moreinfo tag when adding an affected jessie package and explaining how it is affected. Let me add a few hints on which packages to look for. The following packages set MARKDOWN_SUPPORT=NO: hdf5 hwloc libsbml mpich openms ppl simbody witty The following packages set MARKDOWN_SUPPORT=YES: ace apophenia apt aubio bladerf boost1.54 boost1.55 casablanca clipper cmocka colobot cpl csound cupt eigen3 elektra exiv2 feel++ fflas-ffpack freecontact gazebo gdcm geographiclib givaro glfw3 gnuradio gr-fcdproplus grass gtkspellmm imagemagick libam7xxx libburn libcaca libclaw libdatrie libdebian-installer libevdev libhmsbeagle liblo libltc libopendbx libreoffice libsdl2-gfx libsidplayfp libssh libstxxl libthai linbox litl lvtk lxc mysql-workbench ns3 ogre-1.9 openmprtl orthanc pcl psocksxx python-odf qof rapidjson rivet schroot sdformat serd simgrid sord speech-tools sratom ui-gxmlcpp ui-utilcpp v4l-utils visp vlfeat websocketpp The vast majority of build-rdeps of doxygen or doxygen-latex appear to not set MARKDOWN_SUPPORT at all. Helmut -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#778697: marked as done (libparted2: error on opening with regard to RAID member devices)
Your message dated Wed, 18 Feb 2015 14:17:36 -0500 with message-id <54e4e550.1060...@ubuntu.com> and subject line Re: Bug#778697: libparted2: error on opening with regard to RAID member devices has caused the Debian Bug report #778697, regarding libparted2: error on opening with regard to RAID member devices 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.) -- 778697: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=778697 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: libparted2 Severity: grave With a 'fake RAID' RAID0 device constructed using motherboard firmware, which has a GPT partitioning table setup using fdisk (gparted failed me - see #778683), opening gparted now results in errors in relation to the RAID member disks. Specifically, I firstly get the following error regarding the first disk in the RAID array: Title: Libparted bug found! Message: Invalid argument during seek for read on /dev/sdb Clicking on 'ignore' then results in this followup message: Title: Libparted bug found! Message: The backup GPT table is corrupt, but the primary appears OK, so that will be used. fdisk seems perfectly happy with the setup. Presumably libparted is not processing the member disks as actually being part of an array. Marking as grave on the off chance of data loss with libparted not processing things properly here, and the possibility of users fiddling with things in gparted in relation to it (e.g. trying to correct the 'unrecognised partition table' status of member disks, wiping out their array. Should array members even be listed in gparted? --- End Message --- --- Begin Message --- -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 2/18/2015 1:34 PM, jnqnfe wrote: > These errors actually disappeared after a reboot :/ ... > > I guess that means I should have refreshed something, or fdisk > should have refreshed something, and thus this can be closed? I suppose if you can't reproduce it then yes, we'll close it. -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.17 (MingW32) iQEcBAEBAgAGBQJU5OVQAAoJENRVrw2cjl5RxjwH/16KndhLju1D6KSdXK46YMlf fv5dYuUIMgWvDKgfPOSJt7+gBi3N/ejMDc4VxSTpV5W0m/UBvArdEelJJm2XT4bB 0UjGqoHF5lBkfr7yq1KsiyzzCSo0m70DscSCnlahMjV1h8gtICkcDSaktSZhyhQQ 9/d+QA/EyGUrBrRdnPR+rZQPRLPvqCEsBBReG/dBTmYi68k3KMliSEid0XYHBwKA 0Ib9bDynkHs72EvU9zsNTfhLGyQhO+Jjy7y7UrjwrqzEM6AaKaDsLEYfg6CSMwSI awBf3tgTQ5/PER7RGFOgMtUOJ+Wwv/tSQSjDfetHit9M5+N1msfD+qTIPpTv8kM= =f0pn -END PGP SIGNATURE End Message ---
Processed: user debian-secur...@lists.debian.org, usertagging 777722 ...
Processing commands for cont...@bugs.debian.org: > user debian-secur...@lists.debian.org Setting user to debian-secur...@lists.debian.org (was car...@debian.org). > usertags 22 + tracked Usertags were: tracked. Usertags are now: tracked. > retitle 22 xdg-open: CVE-2015-1877: command injection vulnerability Bug #22 [xdg-utils] xdg-open: another command injection vulnerability Changed Bug title to 'xdg-open: CVE-2015-1877: command injection vulnerability' from 'xdg-open: another command injection vulnerability' > thanks Stopping processing here. Please contact me if you need assistance. -- 22: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=22 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#778697: libparted2: error on opening with regard to RAID member devices
These errors actually disappeared after a reboot :/ ... I guess that means I should have refreshed something, or fdisk should have refreshed something, and thus this can be closed? -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#776137: sudo: fails to switch between sudo and sudo-ldap: chown: cannot access '/etc/sudoers': No such file or directory
Hi, On 2015-02-07 01:02, Christian Kastner wrote: > I've looked into this now, and I believe that the --compare-versions > issue and the chown/chmod issue is all there is to this bug. I have > attached a new debdiff (v2) with fixes for both. > > I have tested this patch in a number of combinations, including (but not > limited to): > > sudo (squeeze) -> sudo (jessie) upgrade > sudo-ldap (squeeze) -> sudo-ldap (jessie) upgrade > > Works as intended. An unchanged /etc/sudoers gets replaced with the new > version, a changed sudoers will cause the user to be asked what to do. > > sudo (jessie)-> sudo (jessie+deb8u2) upgrade > sudo-ldap (jessie)-> sudo-ldap (jessie+deb8u2) upgrade > > Same result as in the previous case. > > sudo (jessie+deb8u2) -> sudo-ldap (jessie+deb8u2) switch > sudo-ldap (jessie+deb8u2) -> sudo (jessie+deb8u2) switch > > /etc/sudoers always gets carried over. There is no scenario where the > user might have to be asked, as the package versions (and the sudoers > they supply) are identical, and the user's changed version therefore > trumps the default version. did anyone get the chance to confirm my results yet? Bdale, once such a confirmation (or another fix) is in, how would you like to proceed? I could help with the RT communication again Regards, Christian -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#778699: Vidalia should not be part of Jessie
Package: vidalia Version: 0.2.21-5 Severity: serious Vidalia has been dead upstream for years, and has a crapload of bugs nobody will ever fix. The Tor Project is currently actively removing any reference to Vidalia from their website. We're not even sure if it's in good shape in Jessie, e.g. about what happens exactly on initial installation -- not sure it is configured properly to use the control socket as it should. Some people are happier with 0.3.x, but that one is itself alpha-quality software with another crapload of bugs that nobody will ever fix. Even Tails is going to ditch Vidalia soonish, and Tails is shipping its patched version anyway. So, it is the maintainers' opinion (agreed by Holger on the pkg-anonymity-tools@ mailing-list, and by Lunar on IRC) that Vidalia should not be part of the Jessie release. Cheers, -- intrigeri -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#778697: libparted2: error on opening with regard to RAID member devices
Package: libparted2 Severity: grave With a 'fake RAID' RAID0 device constructed using motherboard firmware, which has a GPT partitioning table setup using fdisk (gparted failed me - see #778683), opening gparted now results in errors in relation to the RAID member disks. Specifically, I firstly get the following error regarding the first disk in the RAID array: Title: Libparted bug found! Message: Invalid argument during seek for read on /dev/sdb Clicking on 'ignore' then results in this followup message: Title: Libparted bug found! Message: The backup GPT table is corrupt, but the primary appears OK, so that will be used. fdisk seems perfectly happy with the setup. Presumably libparted is not processing the member disks as actually being part of an array. Marking as grave on the off chance of data loss with libparted not processing things properly here, and the possibility of users fiddling with things in gparted in relation to it (e.g. trying to correct the 'unrecognised partition table' status of member disks, wiping out their array. Should array members even be listed in gparted? -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#778695: wheezy -> jessie: no gdm3 prompt, dependency loops and broken initrd
Package: upgrade-reports Severity: grave This is the third jessie upgrade I perform from jessie. The previous one was documented in #774314. It seems that the dependency loop problems are still there, and there were so many problems with the upgrade that I don't believe it would be right to release jessie as such (hence the "grave" severity). I know that I certainly can't spend the 6h i did on this workstation on all the workstations in the office. :) I followed the two-stage upgrade procedure from the install manual. My notes are here: https://wiki.koumbit.net/JessieUpgrade During the `dist-upgrade` step (after the `upgrade`), there was a failure i couldn't trace back (because i somehow got out of that ttyrec by mistake). After that, I got the following error trying to run `dist-upgrade` again: root@desktop008:/# apt-get dist-upgrade -y -o Dpkg::Options::='--force-confdef' -o Dpkg::Options::='--force-confold' Reading package lists... Done Building dependency tree Reading state information... Done You might want to run 'apt-get -f install' to correct these. The following packages have unmet dependencies: aptdaemon : Depends: python-aptdaemon (= 0.45-2) but 1.1.1-4 is installed auctex : Depends: emacs24 or emacs-snapshot but it is not installable cheese : Depends: libgnome-desktop-3-2 (>= 3.2.0) but it is not installable cups : Depends: cups-core-drivers (>= 1.7.5-10) but it is not installed Depends: cups-server-common (>= 1.7.5-10) but it is not installed Depends: cups-client (>= 1.7.5-10) but 1.5.3-5+deb7u4 is installed Depends: cups-filters (>= 1.0.24-3~) but 1.0.18-2.1+deb7u1 is installed Recommends: cups-filters (>= 1.0.42) but 1.0.18-2.1+deb7u1 is installed or foomatic-filters (>= 4.0) Recommends: cups-filters (>= 1.0.36) but 1.0.18-2.1+deb7u1 is installed or ghostscript-cups (>= 9.02~) cups-bsd : Depends: cups-client (= 1.7.5-10) but 1.5.3-5+deb7u4 is installed cups-client : Depends: libcups2 (= 1.5.3-5+deb7u4) but 1.7.5-10 is installed dpkg : Breaks: fontconfig (< 2.11.0-6.2) but 2.9.0-7.1 is installed Breaks: man-db (< 2.6.3-6) but 2.6.2-1 is installed eog : Depends: libgnome-desktop-3-2 (>= 3.2.0) but it is not installable evolution : Depends: libgnome-desktop-3-2 (>= 3.2.0) but it is not installable evolution-plugins : Depends: libgnome-desktop-3-2 (>= 3.2.0) but it is not installable foomatic-db-engine : Depends: cups-filters (>= 1.0.42) but 1.0.18-2.1+deb7u1 is installed or foomatic-filters (>= 4.0) gdm3 : Depends: libaudit0 (>= 1.7.13) but it is not installable gir1.2-freedesktop : Depends: gir1.2-glib-2.0 (= 1.32.1-1) but 1.42.0-2.2 is installed gnome-color-manager : Depends: libgnome-desktop-3-2 (>= 3.2.0) but it is not installable gnome-contacts : Depends: libgnome-desktop-3-2 (>= 3.2.0) but it is not installable gnome-control-center : Depends: libgnome-desktop-3-2 (>= 3.2.0) but it is not installable gnome-documents : Depends: libgnome-desktop-3-2 (>= 3.2.0) but it is not installable gnome-panel : Depends: libgnome-desktop-3-2 (>= 3.2.0) but it is not installable gnome-screensaver : Depends: libgnome-desktop-3-2 (>= 3.2.0) but it is not installable gnome-settings-daemon : Depends: libgnome-desktop-3-2 (>= 3.4.0) but it is not installable gnome-themes-standard : Depends: libpangocairo-1.0-0 (>= 1.14.0) but it is not installed gtk2-engines-pixbuf : Depends: libgtk2.0-0 (= 2.24.10-2) but 2.24.25-1 is installed libc-dev-bin : Depends: libc6 (< 2.14) but 2.19-13 is installed libc6-dev : Depends: libc6 (= 2.13-38+deb7u7) but 2.19-13 is installed libcairo2-dev : Depends: libcairo2 (= 1.12.2-3) but 1.14.0-2.1 is installed libcupscgi1 : Depends: libcups2 (= 1.5.3-5+deb7u4) but 1.7.5-10 is installed libcupsdriver1 : Depends: libcups2 (= 1.5.3-5+deb7u4) but 1.7.5-10 is installed libcupsimage2 : Depends: libcups2 (= 1.5.3-5+deb7u4) but 1.7.5-10 is installed libcupsmime1 : Depends: libcups2 (= 1.5.3-5+deb7u4) but 1.7.5-10 is installed libcupsppdc1 : Depends: libcups2 (= 1.5.3-5+deb7u4) but 1.7.5-10 is installed libevolution : Depends: libgnome-desktop-3-2 (>= 3.2.0) but it is not installable libgail-3-0 : Depends: libgtk-3-0 (= 3.4.2-7) but 3.14.5-1 is installed libgail18 : Depends: libgtk2.0-0 (= 2.24.10-2) but 2.24.25-1 is installed libgdk-pixbuf2.0-dev : Depends: libgdk-pixbuf2.0-0 (= 2.26.1-1) but 2.31.1-2+b1 is installed libglib2.0-bin : Depends: libglib2.0-0 (= 2.33.12+really2.32.4-5) but 2.42.1-1 is installed libglib2.0-dev : Depends: libglib2.0-0 (= 2.33.12+really2.32.4-5) but 2.42.1-1 is installed libgtk-3-0 : Depends: libpangocairo-1.0-0 (>= 1.36.7) but it is not installed libgtk-3-bin : Depends: libgtk-3-common (= 3.4.2-7) but 3.14.5-1 is installed libgtk-3-dev : Depends: libgtk-3-0 (= 3.4.2-7) but 3.14.5-1 is installed libgtk2.0-0 : Depends: libpangocairo-1.0-0 (>= 1.28.3) but it is not inst
Processed: severity of 778642 is important
Processing commands for cont...@bugs.debian.org: > severity 778642 important Bug #778642 [xfce4-power-manager-plugins] xfce4-power-manager-plugins: Serious memory leak in libxfce4powermanager.so Severity set to 'important' from 'critical' > thanks Stopping processing here. Please contact me if you need assistance. -- 778642: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=778642 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 778674
Processing commands for cont...@bugs.debian.org: > tags 778674 + confirmed Bug #778674 [apt-p2p] apt-p2p: fails to start (throws exception) Added tag(s) confirmed. > thanks Stopping processing here. Please contact me if you need assistance. -- 778674: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=778674 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#778642: [Pkg-xfce-devel] Bug#778642: xfce4-power-manager-plugins: Serious memory leak in libxfce4powermanager.so
control: severity -1 import control: tag -1 unreproducible moreinfo On mar., 2015-02-17 at 13:28 -0600, John Goerzen wrote: > Package: xfce4-power-manager-plugins > Version: 1.4.1-1 > Severity: critical > > This package has caused my system to hang on multiple occasions. Right now, > I am seeing this: > > $ ps auxww | egrep 27036\|USER > USER PID %CPU %MEMVSZ RSS TTY STAT START TIME COMMAND > jgoerzen 3262 0.0 0.0 12720 2016 pts/1S+ 13:27 0:00 grep -E > 27036|USER > jgoerzen 27036 0.0 20.3 1865132 1640052 ? Sl Jan20 8:50 > /usr/lib/x86_64-linux-gnu/xfce4/panel/wrapper > /usr/lib/x86_64-linux-gnu/xfce4/panel/plugins/libxfce4powermanager.so 3 > 23068717 power-manager-plugin Power Manager Plugin Display the battery levels > of your devices and control the brightness of your display > > Yep, using 1.6GB RAM. And this laptop has been suspended most of the time > since Jan. 20. Also: > > jgoerzen@athena:~$ free > total used free sharedbuffers cached > Mem: 80726287651112 421516 283484 3960 824748 > -/+ buffers/cache:68224041250224 > Swap:0 0 0 > jgoerzen@athena:~$ kill 27036 > jgoerzen@athena:~$ free > total used free sharedbuffers cached > Mem: 807262860264162046212 282212 3960 823860 > -/+ buffers/cache:51985962874032 > Swap:0 0 0 > There's just nothing useful for us to help you here. You could try to run it through valgrind or something like that. Regards, -- Yves-Alexis signature.asc Description: This is a digitally signed message part
Processed (with 1 errors): Re: [Pkg-xfce-devel] Bug#778642: xfce4-power-manager-plugins: Serious memory leak in libxfce4powermanager.so
Processing control commands: > severity -1 import Severity level `import' is not known. Recognized are: critical, grave, serious, important, normal, minor, wishlist, fixed. > tag -1 unreproducible moreinfo Bug #778642 [xfce4-power-manager-plugins] xfce4-power-manager-plugins: Serious memory leak in libxfce4powermanager.so Added tag(s) unreproducible and moreinfo. -- 778642: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=778642 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#778654: marked as done (FTBFS on various architectures, test-sigbus and test-utf8 failures)
Your message dated Wed, 18 Feb 2015 15:20:07 + with message-id and subject line Bug#778654: fixed in systemd 219-2 has caused the Debian Bug report #778654, regarding FTBFS on various architectures, test-sigbus and test-utf8 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.) -- 778654: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=778654 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: systemd Version: 219-1 Severity: serious The latest upstream versions FTBFS on various architectures due to failures in the test-suite: armhf: FAIL: test-sigbus i386:FAIL: test-sigbus mips:FAIL: test-utf8 powerpc: FAIL: test-utf8, FAIL: test-sigbus s390x: FAIL: test-utf8 sparc: various failures (no release arch though, has been failing for quite some time) https://buildd.debian.org/status/package.php?p=systemd&suite=experimental -- Package-specific info: -- System Information: Debian Release: 8.0 APT prefers unstable APT policy: (500, 'unstable'), (200, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.16.0-4-amd64 (SMP w/4 CPU cores) Locale: LANG=de_DE.utf8, LC_CTYPE=de_DE.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) -- no debconf information --- End Message --- --- Begin Message --- Source: systemd Source-Version: 219-2 We believe that the bug you reported is fixed in the latest version of systemd, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 778...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Martin Pitt (supplier of updated systemd package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Wed, 18 Feb 2015 15:29:42 +0100 Source: systemd Binary: systemd systemd-sysv libpam-systemd libsystemd0 libsystemd-dev libsystemd-login-dev libsystemd-daemon-dev libsystemd-journal-dev libsystemd-id128-dev udev libudev1 libudev-dev udev-udeb libudev1-udeb libgudev-1.0-0 gir1.2-gudev-1.0 libgudev-1.0-dev python3-systemd systemd-dbg Architecture: source amd64 Version: 219-2 Distribution: experimental Urgency: medium Maintainer: Debian systemd Maintainers Changed-By: Martin Pitt Description: gir1.2-gudev-1.0 - libgudev-1.0 introspection data libgudev-1.0-0 - GObject-based wrapper library for libudev libgudev-1.0-dev - libgudev-1.0 development files libpam-systemd - system and service manager - PAM module libsystemd-daemon-dev - systemd utility library (transitional package) libsystemd-dev - systemd utility library - development files libsystemd-id128-dev - systemd 128 bit ID utility library (transitional package) libsystemd-journal-dev - systemd journal utility library (transitional package) libsystemd-login-dev - systemd login utility library (transitional package) libsystemd0 - systemd utility library libudev-dev - libudev development files libudev1 - libudev shared library libudev1-udeb - libudev shared library (udeb) python3-systemd - Python 3 bindings for systemd systemd- system and service manager systemd-dbg - system and service manager (debug symbols) systemd-sysv - system and service manager - SysV links udev - /dev/ and hotplug management daemon udev-udeb - /dev/ and hotplug management daemon (udeb) Closes: 778654 Changes: systemd (219-2) experimental; urgency=medium . * Fix UTF-16 to UTF-8 conversion on big-endian machines. (Closes: #778654) * Disable new new test-sigbus, it fails on some buildds due to too old kernels. (part of #778654) * debian/README.Debian, debian/systemd.postinst: Drop setfacl call for /var/log/journal, this is now done automatically by tmpfiles.d/systemd.conf. * Drop "acl" dependency, not necessary any more with the above. * debian/tests/boot-and-services: Move to using /var/lib/machines/, /var/lib/containers is deprecated. Checksums-Sha1: 4065e96963e3847a94c3ae2ca4e83b8b1483bccd 3838 systemd_219-2.dsc 6fb622a69d1db9e0c1c1bce14695e397c6b722c7 133820 systemd_219-2.debian.tar.xz 8511552001b30dec99dfec350310733ad170c8a0 3384046 systemd_219-2_amd64.deb 245edbd0c5b2d5cb19b962f0071ba68
Processed: found 777722 in 1.0.2+cvs20100307-2
Processing commands for cont...@bugs.debian.org: > found 22 1.0.2+cvs20100307-2 Bug #22 [xdg-utils] xdg-open: another command injection vulnerability Marked as found in versions xdg-utils/1.0.2+cvs20100307-2. > thanks Stopping processing here. Please contact me if you need assistance. -- 22: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=22 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#777722: xdg-open: another command injection vulnerability
Hi, On Wed, Feb 11, 2015 at 11:10:24PM +0100, Jiri Horner wrote: > Problem is caused by name collision in local variables, which are > apparently not very local in this case (maybe also dash problem?) Just an additional comment on this: It looks actually as intended that the initial value is inherited, the manpage state: Variables may be declared to be local to a function by using a local command. This should appear as the first statement of a function, and the syntax is local [variable | -] ... Local is implemented as a builtin command. When a variable is made local, it inherits the initial value and exported and readonly flags from the variable with the same name in the surrounding scope, if there is one. Otherwise, the variable is initially unset. The shell uses dynamic scoping, so that if you make the variable x local to function f, which then calls func‐ tion g, references to the variable x made inside g will refer to the variable x declared inside f, not to the global variable named x. Regards, Salvatore -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Processed: tagging 778669
Processing commands for cont...@bugs.debian.org: > tags 778669 + security Bug #778669 [mediatomb-daemon] mediatomb allows anyone to browse and export the whole filesystem Added tag(s) security. > thanks Stopping processing here. Please contact me if you need assistance. -- 778669: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=778669 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#778674: apt-p2p: fails to start (throws exception)
Package: apt-p2p Version: 0.1.7 Severity: grave Justification: renders package unusable Hi, I wanted to test apt-p2p and noticed that it won't even start: [ ~ ] $ sudo apt-p2p [sudo] password for toma: 2015-02-18 11:47:31+0100 [-] Log opened. 2015-02-18 11:47:31+0100 [-] Loading config files: '/etc/apt-p2p/apt-p2p.conf', '/root/.apt-p2p/apt-p2p.conf', '' 2015-02-18 11:47:31+0100 [-] Successfully loaded config files: '/etc/apt-p2p/apt-p2p.conf' 2015-02-18 11:47:31+0100 [-] Starting application with uid/gid 141/65534 2015-02-18 11:47:31+0100 [-] Starting main application server 2015-02-18 11:47:31+0100 [-] Traceback (most recent call last): 2015-02-18 11:47:31+0100 [-] File "/usr/sbin/apt-p2p", line 73, in 2015-02-18 11:47:31+0100 [-] from apt_p2p.apt_p2p import AptP2P 2015-02-18 11:47:31+0100 [-] File "/usr/lib/python2.7/dist-packages/apt_p2p/apt_p2p.py", line 19, in 2015-02-18 11:47:31+0100 [-] from MirrorManager import MirrorManager 2015-02-18 11:47:31+0100 [-] File "/usr/lib/python2.7/dist-packages/apt_p2p/MirrorManager.py", line 16, in 2015-02-18 11:47:31+0100 [-] from AptPackages import AptPackages 2015-02-18 11:47:31+0100 [-] File "/usr/lib/python2.7/dist-packages/apt_p2p/AptPackages.py", line 40, in 2015-02-18 11:47:31+0100 [-] from apt.progress.old import OpProgress 2015-02-18 11:47:31+0100 [-] ImportError: No module named old Just letting you know and putting it under RC. Tomasz -- System Information: Debian Release: 8.0 APT prefers testing APT policy: (990, 'testing') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.16.0-4-amd64 (SMP w/4 CPU cores) Locale: LANG=es_ES.utf8, LC_CTYPE=es_ES.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages apt-p2p depends on: ii adduser 3.113+nmu3 ii python 2.7.8-3 ii python-apt 0.9.3.11 ii python-debian0.1.25 ii python-pysqlite2 2.6.3-3 ii python-twisted-web2 8.1.0-3 pn python:any apt-p2p recommends no packages. apt-p2p suggests no packages. -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#778668: marked as done (suricata and libhtp-dev: error when trying to install together)
Your message dated Wed, 18 Feb 2015 10:33:38 + with message-id and subject line Bug#778668: fixed in suricata 2.0.6-2 has caused the Debian Bug report #778668, regarding suricata and libhtp-dev: error when trying to install together to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 778668: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=778668 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: libhtp-dev,suricata Version: libhtp-dev/0.5.15-1 Version: suricata/2.0.6-1 Severity: serious User: trei...@debian.org Usertags: edos-file-overwrite Date: 2015-02-18 Architecture: amd64 Distribution: sid Hi, automatic installation tests of packages that share a file and at the same time do not conflict by their package dependency relationships has detected the following problem: Extracting templates from packages: 88% Extracting templates from packages: 100% Selecting previously unselected package libdb5.3:amd64. (Reading database ... 10938 files and directories currently installed.) Preparing to unpack .../libdb5.3_5.3.28-9_amd64.deb ... Unpacking libdb5.3:amd64 (5.3.28-9) ... Selecting previously unselected package libgcrypt20:amd64. Preparing to unpack .../libgcrypt20_1.6.2-4+b1_amd64.deb ... Unpacking libgcrypt20:amd64 (1.6.2-4+b1) ... Selecting previously unselected package libgmp10:amd64. Preparing to unpack .../libgmp10_2%3a6.0.0+dfsg-6_amd64.deb ... Unpacking libgmp10:amd64 (2:6.0.0+dfsg-6) ... Selecting previously unselected package libnettle4:amd64. Preparing to unpack .../libnettle4_2.7.1-5_amd64.deb ... Unpacking libnettle4:amd64 (2.7.1-5) ... Selecting previously unselected package libhogweed2:amd64. Preparing to unpack .../libhogweed2_2.7.1-5_amd64.deb ... Unpacking libhogweed2:amd64 (2.7.1-5) ... Selecting previously unselected package libffi6:amd64. Preparing to unpack .../libffi6_3.1-2+b2_amd64.deb ... Unpacking libffi6:amd64 (3.1-2+b2) ... Preparing to unpack .../libp11-kit0_0.20.7-1_amd64.deb ... Unpacking libp11-kit0:amd64 (0.20.7-1) over (0.18.5-3) ... Selecting previously unselected package libtasn1-6:amd64. Preparing to unpack .../libtasn1-6_4.2-2_amd64.deb ... Unpacking libtasn1-6:amd64 (4.2-2) ... Selecting previously unselected package libgnutls-deb0-28:amd64. Preparing to unpack .../libgnutls-deb0-28_3.3.8-5_amd64.deb ... Unpacking libgnutls-deb0-28:amd64 (3.3.8-5) ... Selecting previously unselected package libmagic1:amd64. Preparing to unpack .../libmagic1_1%3a5.22+15-1_amd64.deb ... Unpacking libmagic1:amd64 (1:5.22+15-1) ... Selecting previously unselected package libpython2.7-minimal:amd64. Preparing to unpack .../libpython2.7-minimal_2.7.9-1_amd64.deb ... Unpacking libpython2.7-minimal:amd64 (2.7.9-1) ... Selecting previously unselected package python2.7-minimal. Preparing to unpack .../python2.7-minimal_2.7.9-1_amd64.deb ... Unpacking python2.7-minimal (2.7.9-1) ... Selecting previously unselected package python-minimal. Preparing to unpack .../python-minimal_2.7.8-3_amd64.deb ... Unpacking python-minimal (2.7.8-3) ... Selecting previously unselected package mime-support. Preparing to unpack .../mime-support_3.58_all.deb ... Unpacking mime-support (3.58) ... Selecting previously unselected package libexpat1:amd64. Preparing to unpack .../libexpat1_2.1.0-6+b3_amd64.deb ... Unpacking libexpat1:amd64 (2.1.0-6+b3) ... Selecting previously unselected package libpython2.7-stdlib:amd64. Preparing to unpack .../libpython2.7-stdlib_2.7.9-1_amd64.deb ... Unpacking libpython2.7-stdlib:amd64 (2.7.9-1) ... Selecting previously unselected package python2.7. Preparing to unpack .../python2.7_2.7.9-1_amd64.deb ... Unpacking python2.7 (2.7.9-1) ... Selecting previously unselected package libpython-stdlib:amd64. Preparing to unpack .../libpython-stdlib_2.7.8-3_amd64.deb ... Unpacking libpython-stdlib:amd64 (2.7.8-3) ... Processing triggers for man-db (2.7.0.2-5) ... Setting up libpython2.7-minimal:amd64 (2.7.9-1) ... Setting up python2.7-minimal (2.7.9-1) ... Setting up python-minimal (2.7.8-3) ... Selecting previously unselected package python. (Reading database ... 11812 files and directories currently installed.) Preparing to unpack .../python_2.7.8-3_amd64.deb ... Unpacking python (2.7.8-3) ... Selecting previously unselected package libcap-ng0:amd64. Preparing to unpack .../libcap-ng0_0.7.4-2_amd64.deb ... Unpacking libcap-ng0:amd64 (0.7.4-2) ... Selecting previously unselected package libjansson4:amd64. Preparing to unpack .../libjansson4_2.7-1_amd64.deb ... Unpacking libjansson4:amd64 (2.7-1) ... Selecting previously unselected package libltdl7:amd64. Prepari
Bug#778374: [php-maint] Bug#778374: Bug#778374: [pkg-horde] Bug#778374: php5 5.6.5 fully breaks Horde packages in Debian jessie
On Tue, Feb 17, 2015, at 20:52, David Prévot wrote: > P.-S.: getting in touch with the people running ci.d.n may be worth it > to help track possible regressions in the future (by running a specific > instance of tests with a new PHP version before uploading it to stable). Thanks for the tip, that is a terrific idea! Cheers, -- Ondřej Surý Knot DNS (https://www.knot-dns.cz/) – a high-performance DNS server -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#778302: MATE: Default file browser for "Places" submenu indeterministically set to applications that are not "Caja"
Am 13.02.2015 um 12:48 schrieb Mike Gabriel: > Happy about opinions and feedback. Thanks! > I have been installing two laptops with vanilla mate + jessie, and found more similar issues. I don't know if it's worth opening new threads for each. For example, I did install vim and now plain text files are being opened with vim (!) instead of pluma. jpgs are opened with iceweasel instead of eom ... Cheers, Philipp -- 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): unarchiving 580120, reopening 580120, found 580120 in 0.12.0~svn2018-6 ..., found 580120 in 0.12.1-4
Processing commands for cont...@bugs.debian.org:
> unarchive 580120
> reopen 580120
Bug #580120 {Done: Alexander Reichle-Schmehl } [mediatomb]
mediatomb allows anyone to browse and export the whole filesystem
'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 mediatomb/0.12.0~svn2018-6.1.
> found 580120 0.12.0~svn2018-6
Bug #580120 [mediatomb] mediatomb allows anyone to browse and export the whole
filesystem
Ignoring request to alter found versions of bug #580120 to the same values
previously set
> fixed 580120 0.12.0~svn2018-6.1
Bug #580120 [mediatomb] mediatomb allows anyone to browse and export the whole
filesystem
Marked as fixed in versions mediatomb/0.12.0~svn2018-6.1.
> found 580120 0.12.1-4
Bug #580120 [mediatomb] mediatomb allows anyone to browse and export the whole
filesystem
Marked as found in versions mediatomb/0.12.1-4.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
580120: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=580120
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: unarchiving 580120
Processing commands for cont...@bugs.debian.org:
> unarchive 580120
Bug #580120 {Done: Alexander Reichle-Schmehl } [mediatomb]
mediatomb allows anyone to browse and export the whole filesystem
Unarchived Bug 580120
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
580120: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=580120
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#778669: mediatomb allows anyone to browse and export the whole filesystem
Package: mediatomb-daemon Version: 0.12.1-4 Severity: grave Tag: security This is a regression of the bug that was fixed in #580120, but somehow the patch applied got revert. Anyone can list and download all the file accessible to the mediatomb user via the daemon web interface, which is binded to 0.0.0.0 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=580120 -- Olivier Lê Thanh Duong
Bug#759530: libc-bin: ldconfig breaks a system
Hi, Could this bug be caused by a corrupt aux-cache[1] (possibly, in addition to a corrupt ld.so.cache)? A bit of google searching suggests that a broken aux-cache can cause ldconfig to seg. fault. With the ld.so.cache itself being corrupt (or sufficiently outdated?), both ldconfig and most other binaries would simply "just seg. fault" fitting the symptoms pretty well so far. It partly also fits with the removal of libjasper1, as the removed library would force ldconfig to *not* use its cache for said library. Though I cannot explain why it seems like stat itself seg. faults. Assuming my hypothesis is correct, a broken system could be restored by running[2]: $ ldconfig.real --ignore-aux-cache Failling that: $ > /var/cache/ldconfig/aux-cache $ ldconfig.real Maybe take a copy of the aux-cache before doing the "restore" command(s). This way we should be able to "re-break" the system by re-instating the old aux-cache (and possibly breaking the ld.so.cache). Thanks, ~Niels [1] /var/cache/ldconfig/aux-cache [2] Using ldconfig.real in case /bin/sh got borked by the ld.so.cache as well. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#778668: suricata and libhtp-dev: error when trying to install together
Package: libhtp-dev,suricata Version: libhtp-dev/0.5.15-1 Version: suricata/2.0.6-1 Severity: serious User: trei...@debian.org Usertags: edos-file-overwrite Date: 2015-02-18 Architecture: amd64 Distribution: sid Hi, automatic installation tests of packages that share a file and at the same time do not conflict by their package dependency relationships has detected the following problem: Extracting templates from packages: 88% Extracting templates from packages: 100% Selecting previously unselected package libdb5.3:amd64. (Reading database ... 10938 files and directories currently installed.) Preparing to unpack .../libdb5.3_5.3.28-9_amd64.deb ... Unpacking libdb5.3:amd64 (5.3.28-9) ... Selecting previously unselected package libgcrypt20:amd64. Preparing to unpack .../libgcrypt20_1.6.2-4+b1_amd64.deb ... Unpacking libgcrypt20:amd64 (1.6.2-4+b1) ... Selecting previously unselected package libgmp10:amd64. Preparing to unpack .../libgmp10_2%3a6.0.0+dfsg-6_amd64.deb ... Unpacking libgmp10:amd64 (2:6.0.0+dfsg-6) ... Selecting previously unselected package libnettle4:amd64. Preparing to unpack .../libnettle4_2.7.1-5_amd64.deb ... Unpacking libnettle4:amd64 (2.7.1-5) ... Selecting previously unselected package libhogweed2:amd64. Preparing to unpack .../libhogweed2_2.7.1-5_amd64.deb ... Unpacking libhogweed2:amd64 (2.7.1-5) ... Selecting previously unselected package libffi6:amd64. Preparing to unpack .../libffi6_3.1-2+b2_amd64.deb ... Unpacking libffi6:amd64 (3.1-2+b2) ... Preparing to unpack .../libp11-kit0_0.20.7-1_amd64.deb ... Unpacking libp11-kit0:amd64 (0.20.7-1) over (0.18.5-3) ... Selecting previously unselected package libtasn1-6:amd64. Preparing to unpack .../libtasn1-6_4.2-2_amd64.deb ... Unpacking libtasn1-6:amd64 (4.2-2) ... Selecting previously unselected package libgnutls-deb0-28:amd64. Preparing to unpack .../libgnutls-deb0-28_3.3.8-5_amd64.deb ... Unpacking libgnutls-deb0-28:amd64 (3.3.8-5) ... Selecting previously unselected package libmagic1:amd64. Preparing to unpack .../libmagic1_1%3a5.22+15-1_amd64.deb ... Unpacking libmagic1:amd64 (1:5.22+15-1) ... Selecting previously unselected package libpython2.7-minimal:amd64. Preparing to unpack .../libpython2.7-minimal_2.7.9-1_amd64.deb ... Unpacking libpython2.7-minimal:amd64 (2.7.9-1) ... Selecting previously unselected package python2.7-minimal. Preparing to unpack .../python2.7-minimal_2.7.9-1_amd64.deb ... Unpacking python2.7-minimal (2.7.9-1) ... Selecting previously unselected package python-minimal. Preparing to unpack .../python-minimal_2.7.8-3_amd64.deb ... Unpacking python-minimal (2.7.8-3) ... Selecting previously unselected package mime-support. Preparing to unpack .../mime-support_3.58_all.deb ... Unpacking mime-support (3.58) ... Selecting previously unselected package libexpat1:amd64. Preparing to unpack .../libexpat1_2.1.0-6+b3_amd64.deb ... Unpacking libexpat1:amd64 (2.1.0-6+b3) ... Selecting previously unselected package libpython2.7-stdlib:amd64. Preparing to unpack .../libpython2.7-stdlib_2.7.9-1_amd64.deb ... Unpacking libpython2.7-stdlib:amd64 (2.7.9-1) ... Selecting previously unselected package python2.7. Preparing to unpack .../python2.7_2.7.9-1_amd64.deb ... Unpacking python2.7 (2.7.9-1) ... Selecting previously unselected package libpython-stdlib:amd64. Preparing to unpack .../libpython-stdlib_2.7.8-3_amd64.deb ... Unpacking libpython-stdlib:amd64 (2.7.8-3) ... Processing triggers for man-db (2.7.0.2-5) ... Setting up libpython2.7-minimal:amd64 (2.7.9-1) ... Setting up python2.7-minimal (2.7.9-1) ... Setting up python-minimal (2.7.8-3) ... Selecting previously unselected package python. (Reading database ... 11812 files and directories currently installed.) Preparing to unpack .../python_2.7.8-3_amd64.deb ... Unpacking python (2.7.8-3) ... Selecting previously unselected package libcap-ng0:amd64. Preparing to unpack .../libcap-ng0_0.7.4-2_amd64.deb ... Unpacking libcap-ng0:amd64 (0.7.4-2) ... Selecting previously unselected package libjansson4:amd64. Preparing to unpack .../libjansson4_2.7-1_amd64.deb ... Unpacking libjansson4:amd64 (2.7-1) ... Selecting previously unselected package libltdl7:amd64. Preparing to unpack .../libltdl7_2.4.2-1.11_amd64.deb ... Unpacking libltdl7:amd64 (2.4.2-1.11) ... Selecting previously unselected package libluajit-5.1-common. Preparing to unpack .../libluajit-5.1-common_2.0.3+dfsg-3_all.deb ... Unpacking libluajit-5.1-common (2.0.3+dfsg-3) ... Selecting previously unselected package libluajit-5.1-2:amd64. Preparing to unpack .../libluajit-5.1-2_2.0.3+dfsg-3_amd64.deb ... Unpacking libluajit-5.1-2:amd64 (2.0.3+dfsg-3) ... Selecting previously unselected package libnet1:amd64. Preparing to unpack .../libnet1_1.1.6+dfsg-3_amd64.deb ... Unpacking libnet1:amd64 (1.1.6+dfsg-3) ... Selecting previously unselected package libnspr4:amd64. Preparing to unpack .../libnspr4_2%3a4.10.7-1_amd64.deb ... Unpacking libnspr4:amd64 (2:4.10.7-1) ... Selecting previously unselected package libnss3:amd64. P
