Bug#769508: apt-transport-spacewalk: package removal fails
Package: apt-transport-spacewalk Version: 1.0.6-4 Severity: serious User: debian...@lists.debian.org Usertags: instest-20141113 instest Hi, While testing the installation of all packages in sid, I ran into the following problem: Reading package lists... Building dependency tree... Reading state information... Starting pkgProblemResolver with broken count: 0 Starting 2 pkgProblemResolver with broken count: 0 Done The following packages were automatically installed and are no longer required: gir1.2-glib-2.0 libdbus-glib-1-2 libfribidi0 libgirepository-1.0-1 libgudev-1.0-0 libnewt0.52 libnl-3-200 libnl-route-3-200 libpython2.7 python-cffi python-cryptography python-dbus python-dbus-dev python-dmidecode python-ethtool python-gi python-gobject python-gudev python-libxml2 python-newt python-openssl python-pkg-resources python-ply python-pycparser python-rhn python-six python-support rhn-client-tools rhnsd Use 'apt-get autoremove' to remove them. The following packages will be REMOVED: apt-transport-spacewalk 0 upgraded, 0 newly installed, 1 to remove and 0 not upgraded. After this operation, 92.2 kB disk space will be freed. (Reading database ... 11717 files and directories currently installed.) Removing apt-transport-spacewalk (1.0.6-4) ... + set -e + which pyclean + pyclean -p apt-transport-spacewalk + set -e + hook=/etc/apt/apt.conf.d/50spacewalk + mv /etc/apt/apt.conf.d/50spacewalk /etc/apt/apt.conf.d/50spacewalk.disabled + exit 0 sh: 1: /usr/lib/apt-spacewalk/post_invoke.py: not found E: Problem executing scripts DPkg::Post-Invoke '/usr/lib/apt-spacewalk/post_invoke.py' E: Sub-process returned an error code The full build log is available from: http://aws-logs.debian.net/ftbfs-logs/2014/11/13/apt-transport-spacewalk.log It is reproducible by installing your package in a clean chroot, using the debconf Noninteractive frontend, and priority: critical. This test was carried out using about 50 AMD64 nodes of the Grid'5000 platform. Internet was not accessible from the nodes. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#769507: sks: package purge (after dependencies removal) fails
Package: sks Version: 1.1.5-2 Severity: serious User: debian...@lists.debian.org Usertags: instest-20141113 instest Hi, While testing the installation of all packages in sid, I ran into the following problem: -- Removing all dependencies: OK Reading package lists... Building dependency tree... Reading state information... Starting pkgProblemResolver with broken count: 0 Starting 2 pkgProblemResolver with broken count: 0 Done The following packages will be REMOVED: bsd-mailx cron db-util db5.3-util exim4 exim4-base exim4-config exim4-daemon-light ifupdown iproute2 isc-dhcp-client isc-dhcp-common libatm1 libbsd0 libdns-export100 libffi6 libgmp10 libgnutls-deb0-28 libhogweed2 libirs-export91 libisc-export95 libisccfg-export90 liblockfile-bin liblockfile1 libnettle4 libp11-kit0 libpopt0 libtasn1-6 libxtables10 logrotate netbase psmisc 0 upgraded, 0 newly installed, 32 to remove and 0 not upgraded. After this operation, 13.7 MB disk space will be freed. (Reading database ... 9361 files and directories currently installed.) Removing bsd-mailx (8.1.2-0.20140825cvs-1) ... + set -e + [ remove = remove ] + update-alternatives --remove mailx /usr/bin/bsd-mailx Removing logrotate (3.8.7-1+b1) ... + set -e + [ remove = purge ] + exit 0 Removing exim4 (4.84-3) ... + set -e + [ remove = purge ] Removing exim4-daemon-light (4.84-3) ... + set -e + [ -n ] + [ -x /etc/init.d/exim4 ] + [ -n ] + command -v invoke-rc.d + invoke-rc.d exim4 stop invoke-rc.d: policy-rc.d denied execution of stop. + [ -n ] + set -e + [ remove = purge ] Removing exim4-base (4.84-3) ... + set -e + [ -e /usr/share/debconf/confmodule ] + . /usr/share/debconf/confmodule + [ ! ] + PERL_DL_NONLAZY=1 + export PERL_DL_NONLAZY + [ ] + exec /usr/share/debconf/frontend /var/lib/dpkg/info/exim4-base.postrm remove + set -e + [ -e /usr/share/debconf/confmodule ] + . /usr/share/debconf/confmodule + [ ! 1 ] + [ -z ] + exec + [ ] + exec + DEBCONF_REDIR=1 + export DEBCONF_REDIR + export debconfavailable=yes + [ -n ] + [ -x /etc/init.d/exim4 ] + [ -n ] + command -v invoke-rc.d + invoke-rc.d exim4 stop invoke-rc.d: policy-rc.d denied execution of stop. + [ -n ] + rm -f /var/lib/exim4/berkeleydbvers.txt + [ remove = purge ] Removing cron (3.0pl1-127) ... + set -e + [ -x /etc/init.d/cron ] + invoke-rc.d cron stop invoke-rc.d: policy-rc.d denied execution of stop. + set -e + dpkg-maintscript-helper rm_conffile /etc/cron.monthly/standard 3.0pl1-113 -- remove + dpkg-maintscript-helper rm_conffile /etc/cron.daily/standard 3.0pl1-124 -- remove + [ remove = purge ] + [ remove = purge ] + [ -d /run/systemd/system ] + [ remove = remove ] + [ -x /usr/bin/deb-systemd-helper ] + deb-systemd-helper mask cron.service + [ remove = purge ] Removing db-util (5.3.0) ... Removing db5.3-util (5.3.28-6) ... Removing exim4-config (4.84-3) ... + set -e + [ -n ] + [ remove = purge ] Removing ifupdown (0.7.49) ... + set -e + dpkg-maintscript-helper rm_conffile /etc/init.d/ifupdown-clean 0.7~beta1 ifupdown -- remove + dpkg-maintscript-helper rm_conffile /etc/init.d/ifupdown 0.7~+ ifupdown -- remove + dpkg-maintscript-helper rm_conffile /etc/default/ifupdown 0.7~+ ifupdown -- remove + set -e + dpkg-maintscript-helper rm_conffile /etc/init.d/ifupdown-clean 0.7~beta1 ifupdown -- remove + dpkg-maintscript-helper rm_conffile /etc/init.d/ifupdown 0.7~+ ifupdown -- remove + dpkg-maintscript-helper rm_conffile /etc/default/ifupdown 0.7~+ ifupdown -- remove + [ remove = purge ] + [ -d /run/systemd/system ] Removing isc-dhcp-client (4.3.1-5) ... + [ remove = purge ] Removing iproute2 (3.16.0-2) ... Removing isc-dhcp-common (4.3.1-5) ... Removing libatm1:amd64 (1:2.5.1-1.5) ... + set -e + [ remove = remove ] + ldconfig Removing libbsd0:amd64 (0.7.0-2) ... + set -e + [ remove = remove ] + ldconfig Removing libirs-export91 (1:9.9.5.dfsg-5) ... + set -e + [ remove = remove ] + ldconfig + [ remove = remove ] + ldconfig Removing libdns-export100 (1:9.9.5.dfsg-5) ... + set -e + [ remove = remove ] + ldconfig + [ remove = remove ] + ldconfig Removing libgnutls-deb0-28:amd64 (3.3.8-3) ... + set -e + [ remove = remove ] + ldconfig Removing libp11-kit0:amd64 (0.20.7-1) ... + set -e + [ remove = remove ] + ldconfig Removing libffi6:amd64 (3.1-2) ... + set -e + [ remove = remove ] + ldconfig Removing libhogweed2:amd64 (2.7.1-3) ... + set -e + [ remove = remove ] + ldconfig Removing libgmp10:amd64 (2:6.0.0+dfsg-6) ... + set -e + [ remove = remove ] + ldconfig Removing libisccfg-export90 (1:9.9.5.dfsg-5) ... + set -e + [ remove = remove ] + ldconfig + [ remove = remove ] + ldconfig Removing libisc-export95 (1:9.9.5.dfsg-5) ... + set -e + [ remove = remove ] + ldconfig + [ remove = remove ] + ldconfig Removing liblockfile1:amd64 (1.09-6) ... + set -e + [ remove = remove ] + ldconfig Removing liblockfile-bin (1.09-6) ... Removing
Bug#769509: cl-webactions: installation fails
Package: cl-webactions Version: 1.2.42+cvs.2010.02.08-dfsg-1.1 Severity: serious User: debian...@lists.debian.org Usertags: instest-20141113 instest Hi, While testing the installation of all packages in sid, I ran into the following problem: Reading package lists... Building dependency tree... Reading state information... Starting pkgProblemResolver with broken count: 0 Starting 2 pkgProblemResolver with broken count: 0 Done The following extra packages will be installed: cl-acl-compat cl-aserve cl-htmlgen cl-ppcre cl-puri Recommended packages: cl-ptester The following NEW packages will be installed: cl-acl-compat cl-aserve cl-htmlgen cl-ppcre cl-puri cl-webactions 0 upgraded, 6 newly installed, 0 to remove and 0 not upgraded. Need to get 628 kB of archives. After this operation, 1996 kB of additional disk space will be used. Get:1 http://localhost:/debian/ jessie/main cl-ppcre all 2.0.3-1 [102 kB] Get:2 http://localhost:/debian/ jessie/main cl-puri all 20101006-1 [23.1 kB] Get:3 http://localhost:/debian/ jessie/main cl-acl-compat all 1.2.42+cvs.2010.02.08-dfsg-1.1 [62.5 kB] Get:4 http://localhost:/debian/ jessie/main cl-htmlgen all 1.2.42+cvs.2010.02.08-dfsg-1.1 [21.2 kB] Get:5 http://localhost:/debian/ jessie/main cl-aserve all 1.2.42+cvs.2010.02.08-dfsg-1.1 [394 kB] Get:6 http://localhost:/debian/ jessie/main cl-webactions all 1.2.42+cvs.2010.02.08-dfsg-1.1 [24.5 kB] Fetched 628 kB in 0s (4684 kB/s) Selecting previously unselected package cl-ppcre. (Reading database ... 8665 files and directories currently installed.) Preparing to unpack .../cl-ppcre_2.0.3-1_all.deb ... Unpacking cl-ppcre (2.0.3-1) ... Selecting previously unselected package cl-puri. Preparing to unpack .../cl-puri_20101006-1_all.deb ... Unpacking cl-puri (20101006-1) ... Selecting previously unselected package cl-acl-compat. Preparing to unpack .../cl-acl-compat_1.2.42+cvs.2010.02.08-dfsg-1.1_all.deb ... Unpacking cl-acl-compat (1.2.42+cvs.2010.02.08-dfsg-1.1) ... Selecting previously unselected package cl-htmlgen. Preparing to unpack .../cl-htmlgen_1.2.42+cvs.2010.02.08-dfsg-1.1_all.deb ... Unpacking cl-htmlgen (1.2.42+cvs.2010.02.08-dfsg-1.1) ... Selecting previously unselected package cl-aserve. Preparing to unpack .../cl-aserve_1.2.42+cvs.2010.02.08-dfsg-1.1_all.deb ... Unpacking cl-aserve (1.2.42+cvs.2010.02.08-dfsg-1.1) ... Selecting previously unselected package cl-webactions. Preparing to unpack .../cl-webactions_1.2.42+cvs.2010.02.08-dfsg-1.1_all.deb ... Unpacking cl-webactions (1.2.42+cvs.2010.02.08-dfsg-1.1) ... Dpkg hook: enabling sh trace for /var/lib/dpkg/info/adduser.postinst Dpkg hook: enabling sh trace for /var/lib/dpkg/info/apt.postinst Dpkg hook: enabling sh trace for /var/lib/dpkg/info/base-files.postinst Dpkg hook: enabling sh trace for /var/lib/dpkg/info/base-passwd.postinst Dpkg hook: enabling sh trace for /var/lib/dpkg/info/bash.postinst Dpkg hook: enabling sh trace for /var/lib/dpkg/info/bsdutils.postinst Dpkg hook: enabling sh trace for /var/lib/dpkg/info/cl-acl-compat.postinst Dpkg hook: enabling sh trace for /var/lib/dpkg/info/cl-aserve.postinst Dpkg hook: enabling sh trace for /var/lib/dpkg/info/cl-htmlgen.postinst Dpkg hook: enabling sh trace for /var/lib/dpkg/info/dash.postinst Dpkg hook: enabling sh trace for /var/lib/dpkg/info/debconf.postinst Dpkg hook: enabling sh trace for /var/lib/dpkg/info/debian-archive-keyring.postinst Dpkg hook: enabling sh trace for /var/lib/dpkg/info/debianutils.postinst Dpkg hook: enabling sh trace for /var/lib/dpkg/info/dmsetup.postinst Dpkg hook: enabling sh trace for /var/lib/dpkg/info/dpkg.postinst Dpkg hook: enabling sh trace for /var/lib/dpkg/info/e2fslibs:amd64.postinst Dpkg hook: enabling sh trace for /var/lib/dpkg/info/findutils.postinst Dpkg hook: enabling sh trace for /var/lib/dpkg/info/gnupg.postinst Dpkg hook: enabling sh trace for /var/lib/dpkg/info/init-system-helpers.postinst Dpkg hook: enabling sh trace for /var/lib/dpkg/info/initscripts.postinst Dpkg hook: enabling sh trace for /var/lib/dpkg/info/less.postinst Dpkg hook: enabling sh trace for /var/lib/dpkg/info/libacl1:amd64.postinst Dpkg hook: enabling sh trace for /var/lib/dpkg/info/libapt-inst1.5:amd64.postinst Dpkg hook: enabling sh trace for /var/lib/dpkg/info/libapt-pkg4.12:amd64.postinst Dpkg hook: enabling sh trace for /var/lib/dpkg/info/libattr1:amd64.postinst Dpkg hook: enabling sh trace for /var/lib/dpkg/info/libaudit1:amd64.postinst Dpkg hook: enabling sh trace for /var/lib/dpkg/info/libblkid1:amd64.postinst Dpkg hook: enabling sh trace for /var/lib/dpkg/info/libbz2-1.0:amd64.postinst Dpkg hook: enabling sh trace for /var/lib/dpkg/info/libc-bin.postinst Dpkg hook: enabling sh trace for /var/lib/dpkg/info/libc6:amd64.postinst Dpkg hook: enabling sh trace for /var/lib/dpkg/info/libcap2:amd64.postinst Dpkg hook: enabling sh trace for /var/lib/dpkg/info/libcomerr2:amd64.postinst
Bug#769512: cl-aserve: installation fails
Package: cl-aserve Version: 1.2.42+cvs.2010.02.08-dfsg-1.1 Severity: serious User: debian...@lists.debian.org Usertags: instest-20141113 instest Hi, While testing the installation of all packages in sid, I ran into the following problem: Reading package lists... Building dependency tree... Reading state information... Starting pkgProblemResolver with broken count: 0 Starting 2 pkgProblemResolver with broken count: 0 Done The following extra packages will be installed: cl-acl-compat cl-htmlgen cl-ppcre cl-puri Suggested packages: cl-webactions Recommended packages: cl-ptester The following NEW packages will be installed: cl-acl-compat cl-aserve cl-htmlgen cl-ppcre cl-puri 0 upgraded, 5 newly installed, 0 to remove and 0 not upgraded. Need to get 603 kB of archives. After this operation, 1881 kB of additional disk space will be used. Get:1 http://localhost:/debian/ jessie/main cl-ppcre all 2.0.3-1 [102 kB] Get:2 http://localhost:/debian/ jessie/main cl-puri all 20101006-1 [23.1 kB] Get:3 http://localhost:/debian/ jessie/main cl-acl-compat all 1.2.42+cvs.2010.02.08-dfsg-1.1 [62.5 kB] Get:4 http://localhost:/debian/ jessie/main cl-htmlgen all 1.2.42+cvs.2010.02.08-dfsg-1.1 [21.2 kB] Get:5 http://localhost:/debian/ jessie/main cl-aserve all 1.2.42+cvs.2010.02.08-dfsg-1.1 [394 kB] Fetched 603 kB in 0s (6163 kB/s) Selecting previously unselected package cl-ppcre. (Reading database ... 8665 files and directories currently installed.) Preparing to unpack .../cl-ppcre_2.0.3-1_all.deb ... Unpacking cl-ppcre (2.0.3-1) ... Selecting previously unselected package cl-puri. Preparing to unpack .../cl-puri_20101006-1_all.deb ... Unpacking cl-puri (20101006-1) ... Selecting previously unselected package cl-acl-compat. Preparing to unpack .../cl-acl-compat_1.2.42+cvs.2010.02.08-dfsg-1.1_all.deb ... Unpacking cl-acl-compat (1.2.42+cvs.2010.02.08-dfsg-1.1) ... Selecting previously unselected package cl-htmlgen. Preparing to unpack .../cl-htmlgen_1.2.42+cvs.2010.02.08-dfsg-1.1_all.deb ... Unpacking cl-htmlgen (1.2.42+cvs.2010.02.08-dfsg-1.1) ... Selecting previously unselected package cl-aserve. Preparing to unpack .../cl-aserve_1.2.42+cvs.2010.02.08-dfsg-1.1_all.deb ... Unpacking cl-aserve (1.2.42+cvs.2010.02.08-dfsg-1.1) ... Dpkg hook: enabling sh trace for /var/lib/dpkg/info/adduser.postinst Dpkg hook: enabling sh trace for /var/lib/dpkg/info/apt.postinst Dpkg hook: enabling sh trace for /var/lib/dpkg/info/base-files.postinst Dpkg hook: enabling sh trace for /var/lib/dpkg/info/base-passwd.postinst Dpkg hook: enabling sh trace for /var/lib/dpkg/info/bash.postinst Dpkg hook: enabling sh trace for /var/lib/dpkg/info/bsdutils.postinst Dpkg hook: enabling sh trace for /var/lib/dpkg/info/cl-acl-compat.postinst Dpkg hook: enabling sh trace for /var/lib/dpkg/info/cl-aserve.postinst Dpkg hook: enabling sh trace for /var/lib/dpkg/info/cl-htmlgen.postinst Dpkg hook: enabling sh trace for /var/lib/dpkg/info/dash.postinst Dpkg hook: enabling sh trace for /var/lib/dpkg/info/debconf.postinst Dpkg hook: enabling sh trace for /var/lib/dpkg/info/debian-archive-keyring.postinst Dpkg hook: enabling sh trace for /var/lib/dpkg/info/debianutils.postinst Dpkg hook: enabling sh trace for /var/lib/dpkg/info/dmsetup.postinst Dpkg hook: enabling sh trace for /var/lib/dpkg/info/dpkg.postinst Dpkg hook: enabling sh trace for /var/lib/dpkg/info/e2fslibs:amd64.postinst Dpkg hook: enabling sh trace for /var/lib/dpkg/info/findutils.postinst Dpkg hook: enabling sh trace for /var/lib/dpkg/info/gnupg.postinst Dpkg hook: enabling sh trace for /var/lib/dpkg/info/init-system-helpers.postinst Dpkg hook: enabling sh trace for /var/lib/dpkg/info/initscripts.postinst Dpkg hook: enabling sh trace for /var/lib/dpkg/info/less.postinst Dpkg hook: enabling sh trace for /var/lib/dpkg/info/libacl1:amd64.postinst Dpkg hook: enabling sh trace for /var/lib/dpkg/info/libapt-inst1.5:amd64.postinst Dpkg hook: enabling sh trace for /var/lib/dpkg/info/libapt-pkg4.12:amd64.postinst Dpkg hook: enabling sh trace for /var/lib/dpkg/info/libattr1:amd64.postinst Dpkg hook: enabling sh trace for /var/lib/dpkg/info/libaudit1:amd64.postinst Dpkg hook: enabling sh trace for /var/lib/dpkg/info/libblkid1:amd64.postinst Dpkg hook: enabling sh trace for /var/lib/dpkg/info/libbz2-1.0:amd64.postinst Dpkg hook: enabling sh trace for /var/lib/dpkg/info/libc-bin.postinst Dpkg hook: enabling sh trace for /var/lib/dpkg/info/libc6:amd64.postinst Dpkg hook: enabling sh trace for /var/lib/dpkg/info/libcap2:amd64.postinst Dpkg hook: enabling sh trace for /var/lib/dpkg/info/libcomerr2:amd64.postinst Dpkg hook: enabling sh trace for /var/lib/dpkg/info/libcryptsetup4:amd64.postinst Dpkg hook: enabling sh trace for /var/lib/dpkg/info/libdb5.3:amd64.postinst Dpkg hook: enabling sh trace for /var/lib/dpkg/info/libdebconfclient0:amd64.postinst Dpkg hook: enabling sh trace for
Bug#769510: sugar-moon-activity: not installable
Package: sugar-moon-activity Version: 11-1.1 Severity: serious User: debian...@lists.debian.org Usertags: instest-20141113 instest Hi, While testing the installation of all packages in sid, I ran into the following problem: Reading package lists... Building dependency tree... Reading state information... Starting pkgProblemResolver with broken count: 2 Starting 2 pkgProblemResolver with broken count: 2 Investigating (0) sugar-moon-activity [ amd64 ] none - 11-1.1 ( x11 ) Broken sugar-moon-activity:amd64 Depends on python-sugar-0.86 [ amd64 ] none ( none ) Broken sugar-moon-activity:amd64 Depends on python-sugar-0.88 [ amd64 ] none - 0.88.0-4 ( python ) Considering python-sugar-0.88:amd64 2 as a solution to sugar-moon-activity:amd64 Re-Instated python-sugar-0.88:amd64 Broken sugar-moon-activity:amd64 Depends on python-sugar-toolkit-0.86 [ amd64 ] none ( none ) Broken sugar-moon-activity:amd64 Depends on python-sugar-toolkit-0.88 [ amd64 ] none - 0.88.1-4 ( python ) Considering python-sugar-toolkit-0.88:amd64 3 as a solution to sugar-moon-activity:amd64 Re-Instated python-sugar-toolkit-0.88:amd64 Investigating (0) python-sugar-0.98 [ amd64 ] none - 0.98.0-1 ( python ) Broken python-sugar-0.98:amd64 Conflicts on python-sugar [ amd64 ] none ( none ) Conflicts//Breaks against version 0.96.0-1 for python-sugar-0.96 but that is not InstVer, ignoring Considering python-sugar-0.88:amd64 2 as a solution to python-sugar-0.98:amd64 11 Added python-sugar-0.88:amd64 to the remove list Conflicts//Breaks against version 0.84.2-4 for python-sugar-0.84 but that is not InstVer, ignoring Fixing python-sugar-0.98:amd64 via keep of python-sugar-0.88:amd64 Investigating (0) python-sugar-toolkit-0.98 [ amd64 ] none - 0.98.1-1 ( python ) Broken python-sugar-toolkit-0.98:amd64 Conflicts on python-sugar-toolkit [ amd64 ] none ( none ) Conflicts//Breaks against version 0.96.3-1 for python-sugar-toolkit-0.96 but that is not InstVer, ignoring Considering python-sugar-toolkit-0.88:amd64 3 as a solution to python-sugar-toolkit-0.98:amd64 5 Added python-sugar-toolkit-0.88:amd64 to the remove list Conflicts//Breaks against version 0.84.17-1 for python-sugar-toolkit-0.84 but that is not InstVer, ignoring Fixing python-sugar-toolkit-0.98:amd64 via keep of python-sugar-toolkit-0.88:amd64 Investigating (0) sugar-presence-service-0.88 [ amd64 ] none - 0.88.0-3.1 ( x11 ) Broken sugar-presence-service-0.88:amd64 Depends on python-sugar-toolkit-0.88 [ amd64 ] none - 0.88.1-4 ( python ) Considering python-sugar-toolkit-0.88:amd64 3 as a solution to sugar-presence-service-0.88:amd64 -1 Holding Back sugar-presence-service-0.88:amd64 rather than change python-sugar-toolkit-0.88:amd64 Investigating (1) sugar-moon-activity [ amd64 ] none - 11-1.1 ( x11 ) Broken sugar-moon-activity:amd64 Depends on python-sugar-0.86 [ amd64 ] none ( none ) Broken sugar-moon-activity:amd64 Depends on python-sugar-0.88 [ amd64 ] none - 0.88.0-4 ( python ) Considering python-sugar-0.88:amd64 2 as a solution to sugar-moon-activity:amd64 Broken sugar-moon-activity:amd64 Depends on python-sugar-toolkit-0.86 [ amd64 ] none ( none ) Broken sugar-moon-activity:amd64 Depends on python-sugar-toolkit-0.88 [ amd64 ] none - 0.88.1-4 ( python ) Considering python-sugar-toolkit-0.88:amd64 3 as a solution to sugar-moon-activity:amd64 Done Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming. The following information may help to resolve the situation: The following packages have unmet dependencies: sugar-moon-activity : Depends: python-sugar-0.86 but it is not installable or python-sugar-0.88 but it is not going to be installed Depends: python-sugar-toolkit-0.86 but it is not installable or python-sugar-toolkit-0.88 but it is not going to be installed E: Unable to correct problems, you have held broken packages. The full build log is available from: http://aws-logs.debian.net/ftbfs-logs/2014/11/13/sugar-moon-activity.log It is reproducible by installing your package in a clean chroot, using the debconf Noninteractive frontend, and priority: critical. This test was carried out using about 50 AMD64 nodes of the Grid'5000 platform. Internet was not accessible from the nodes. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#769395: [Ceph-maintainers] Bug#769395: ceph-dkms: module FTBFS for kernel 3.16.0-4
On Thu, 13 Nov 2014 15:27:30 Gaudenz Steinlin wrote: Is this package still usefull? Perhaps it is not too useful right now but I'm planning to update it for kernel 3.16 eventually... Both the ceph filesystem module and the rbd module are included in the upstream kernel and AFAICS regularly updated. I would never needed ceph-dkms in first place if Ceph were maintained in kernel well enough... Maybe it's better to just remove this package. What's the rush? ceph-dkms is in experimental only... Feel free to request removal if you find ceph-dkms still outdated six months from now. In any case by that time most likely I will not be using Ceph any more... On Thu, 13 Nov 2014 10:29:22 Ken Dreyer wrote: I was wondering the same. Could Debian users just rely on the kernel module in the main kernel package? That's pretty much the current situation -- we have ceph-dkms only in experimental so when needed we could test fixes promptly (or rapidly deploy hot-fixes when necessary). I tried to rely on kernel modules in main kernel package and failed miserably -- as consequence I had to make ceph-dkms to test and deploy critical fixes. We do not encourage ceph-dkms and it is available only to advanced users who know about experimental suite. Package even have a note that it is not suitable for release... -- All the best, Dmitry Smirnov GPG key : 4096R/53968D1B --- It is a fine thing to be honest, but it is also very important to be right. -- Winston Churchill signature.asc Description: This is a digitally signed message part.
Bug#769513: cl-htmlgen: installation fails
Package: cl-htmlgen Version: 1.2.42+cvs.2010.02.08-dfsg-1.1 Severity: serious User: debian...@lists.debian.org Usertags: instest-20141113 instest Hi, While testing the installation of all packages in sid, I ran into the following problem: Reading package lists... Building dependency tree... Reading state information... Starting pkgProblemResolver with broken count: 0 Starting 2 pkgProblemResolver with broken count: 0 Done The following extra packages will be installed: cl-ppcre cl-puri Recommended packages: cl-ptester The following NEW packages will be installed: cl-htmlgen cl-ppcre cl-puri 0 upgraded, 3 newly installed, 0 to remove and 0 not upgraded. Need to get 147 kB of archives. After this operation, 688 kB of additional disk space will be used. Get:1 http://localhost:/debian/ jessie/main cl-ppcre all 2.0.3-1 [102 kB] Get:2 http://localhost:/debian/ jessie/main cl-puri all 20101006-1 [23.1 kB] Get:3 http://localhost:/debian/ jessie/main cl-htmlgen all 1.2.42+cvs.2010.02.08-dfsg-1.1 [21.2 kB] Fetched 147 kB in 0s (1621 kB/s) Selecting previously unselected package cl-ppcre. (Reading database ... 8665 files and directories currently installed.) Preparing to unpack .../cl-ppcre_2.0.3-1_all.deb ... Unpacking cl-ppcre (2.0.3-1) ... Selecting previously unselected package cl-puri. Preparing to unpack .../cl-puri_20101006-1_all.deb ... Unpacking cl-puri (20101006-1) ... Selecting previously unselected package cl-htmlgen. Preparing to unpack .../cl-htmlgen_1.2.42+cvs.2010.02.08-dfsg-1.1_all.deb ... Unpacking cl-htmlgen (1.2.42+cvs.2010.02.08-dfsg-1.1) ... Dpkg hook: enabling sh trace for /var/lib/dpkg/info/adduser.postinst Dpkg hook: enabling sh trace for /var/lib/dpkg/info/apt.postinst Dpkg hook: enabling sh trace for /var/lib/dpkg/info/base-files.postinst Dpkg hook: enabling sh trace for /var/lib/dpkg/info/base-passwd.postinst Dpkg hook: enabling sh trace for /var/lib/dpkg/info/bash.postinst Dpkg hook: enabling sh trace for /var/lib/dpkg/info/bsdutils.postinst Dpkg hook: enabling sh trace for /var/lib/dpkg/info/cl-htmlgen.postinst Dpkg hook: enabling sh trace for /var/lib/dpkg/info/dash.postinst Dpkg hook: enabling sh trace for /var/lib/dpkg/info/debconf.postinst Dpkg hook: enabling sh trace for /var/lib/dpkg/info/debian-archive-keyring.postinst Dpkg hook: enabling sh trace for /var/lib/dpkg/info/debianutils.postinst Dpkg hook: enabling sh trace for /var/lib/dpkg/info/dmsetup.postinst Dpkg hook: enabling sh trace for /var/lib/dpkg/info/dpkg.postinst Dpkg hook: enabling sh trace for /var/lib/dpkg/info/e2fslibs:amd64.postinst Dpkg hook: enabling sh trace for /var/lib/dpkg/info/findutils.postinst Dpkg hook: enabling sh trace for /var/lib/dpkg/info/gnupg.postinst Dpkg hook: enabling sh trace for /var/lib/dpkg/info/init-system-helpers.postinst Dpkg hook: enabling sh trace for /var/lib/dpkg/info/initscripts.postinst Dpkg hook: enabling sh trace for /var/lib/dpkg/info/less.postinst Dpkg hook: enabling sh trace for /var/lib/dpkg/info/libacl1:amd64.postinst Dpkg hook: enabling sh trace for /var/lib/dpkg/info/libapt-inst1.5:amd64.postinst Dpkg hook: enabling sh trace for /var/lib/dpkg/info/libapt-pkg4.12:amd64.postinst Dpkg hook: enabling sh trace for /var/lib/dpkg/info/libattr1:amd64.postinst Dpkg hook: enabling sh trace for /var/lib/dpkg/info/libaudit1:amd64.postinst Dpkg hook: enabling sh trace for /var/lib/dpkg/info/libblkid1:amd64.postinst Dpkg hook: enabling sh trace for /var/lib/dpkg/info/libbz2-1.0:amd64.postinst Dpkg hook: enabling sh trace for /var/lib/dpkg/info/libc-bin.postinst Dpkg hook: enabling sh trace for /var/lib/dpkg/info/libc6:amd64.postinst Dpkg hook: enabling sh trace for /var/lib/dpkg/info/libcap2:amd64.postinst Dpkg hook: enabling sh trace for /var/lib/dpkg/info/libcomerr2:amd64.postinst Dpkg hook: enabling sh trace for /var/lib/dpkg/info/libcryptsetup4:amd64.postinst Dpkg hook: enabling sh trace for /var/lib/dpkg/info/libdb5.3:amd64.postinst Dpkg hook: enabling sh trace for /var/lib/dpkg/info/libdebconfclient0:amd64.postinst Dpkg hook: enabling sh trace for /var/lib/dpkg/info/libdevmapper1.02.1:amd64.postinst Dpkg hook: enabling sh trace for /var/lib/dpkg/info/libgc1c2:amd64.postinst Dpkg hook: enabling sh trace for /var/lib/dpkg/info/libgcc1:amd64.postinst Dpkg hook: enabling sh trace for /var/lib/dpkg/info/libgcrypt20:amd64.postinst Dpkg hook: enabling sh trace for /var/lib/dpkg/info/libgdbm3:amd64.postinst Dpkg hook: enabling sh trace for /var/lib/dpkg/info/libgpg-error0:amd64.postinst Dpkg hook: enabling sh trace for /var/lib/dpkg/info/libkmod2:amd64.postinst Dpkg hook: enabling sh trace for /var/lib/dpkg/info/liblzma5:amd64.postinst Dpkg hook: enabling sh trace for /var/lib/dpkg/info/libmount1:amd64.postinst Dpkg hook: enabling sh trace for /var/lib/dpkg/info/libncurses5:amd64.postinst Dpkg hook: enabling sh trace for /var/lib/dpkg/info/libncursesw5:amd64.postinst Dpkg hook:
Bug#769511: netscript-2.4: installation fails
Package: netscript-2.4 Version: 5.4.5 Severity: serious User: debian...@lists.debian.org Usertags: instest-20141113 instest Hi, While testing the installation of all packages in sid, I ran into the following problem: Reading package lists... Building dependency tree... Reading state information... Starting pkgProblemResolver with broken count: 0 Starting 2 pkgProblemResolver with broken count: 0 Done Suggested packages: whereami dnsmasq resolvconf wpasupplicant wicd quagga radvd bird The following packages will be REMOVED: ifupdown The following NEW packages will be installed: netscript-2.4 0 upgraded, 1 newly installed, 1 to remove and 0 not upgraded. Need to get 53.3 kB of archives. After this operation, 114 kB of additional disk space will be used. Get:1 http://localhost:/debian/ jessie/main netscript-2.4 all 5.4.5 [53.3 kB] Fetched 53.3 kB in 0s (875 kB/s) (Reading database ... 9039 files and directories currently installed.) Removing ifupdown (0.7.49) ... + set -e + dpkg-maintscript-helper rm_conffile /etc/init.d/ifupdown-clean 0.7~beta1 ifupdown -- remove + dpkg-maintscript-helper rm_conffile /etc/init.d/ifupdown 0.7~+ ifupdown -- remove + dpkg-maintscript-helper rm_conffile /etc/default/ifupdown 0.7~+ ifupdown -- remove + set -e + dpkg-maintscript-helper rm_conffile /etc/init.d/ifupdown-clean 0.7~beta1 ifupdown -- remove + dpkg-maintscript-helper rm_conffile /etc/init.d/ifupdown 0.7~+ ifupdown -- remove + dpkg-maintscript-helper rm_conffile /etc/default/ifupdown 0.7~+ ifupdown -- remove + [ remove = purge ] + [ -d /run/systemd/system ] Selecting previously unselected package netscript-2.4. (Reading database ... 9010 files and directories currently installed.) Preparing to unpack .../netscript-2.4_5.4.5_all.deb ... Unpacking netscript-2.4 (5.4.5) ... Dpkg hook: enabling sh trace for /var/lib/dpkg/info/netscript-2.4.postinst Dpkg hook: enabling sh trace for /var/lib/dpkg/info/netscript-2.4.postrm Dpkg hook: enabling sh trace for /var/lib/dpkg/info/netscript-2.4.preinst Setting up netscript-2.4 (5.4.5) ... + set -e + deb-systemd-helper unmask netscript.service + deb-systemd-helper --quiet was-enabled netscript.service + deb-systemd-helper enable netscript.service + deb-systemd-helper debian-installed netscript.service + deb-systemd-helper unmask netscript.service + deb-systemd-helper --quiet was-enabled netscript.service + deb-systemd-helper enable netscript.service + deb-systemd-helper update-state netscript.service + [ -x /etc/init.d/netscript ] + update-rc.d netscript start 35 0 6 . start 40 S . update-rc.d: warning: start and stop actions are no longer supported; falling back to defaults insserv: There is a loop between service networking and netscript if started insserv: loop involving service netscript at depth 4 insserv: loop involving service networking at depth 3 insserv: loop involving service procps at depth 2 insserv: loop involving service mountnfs at depth 8 insserv: loop involving service mountall at depth 6 insserv: loop involving service urandom at depth 7 insserv: There is a loop between service networking and netscript if started insserv: exiting now without changing boot order! update-rc.d: error: insserv rejected the script header + exit 1 dpkg: error processing package netscript-2.4 (--configure): subprocess installed post-installation script returned error exit status 1 Errors were encountered while processing: netscript-2.4 E: Sub-process /usr/bin/dpkg returned an error code (1) The full build log is available from: http://aws-logs.debian.net/ftbfs-logs/2014/11/13/netscript-2.4.log It is reproducible by installing your package in a clean chroot, using the debconf Noninteractive frontend, and priority: critical. This test was carried out using about 50 AMD64 nodes of the Grid'5000 platform. Internet was not accessible from the nodes. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#769515: dpkg memory leak v2
Package: dpkg Version: 1.17.21-14-gc195 Severity: normal (I hope I got that right this time!) In dpkg-deb/info.c line 80: dbuf = mkdtemp(path_make_temp_template(dpkg-deb)); In the path_make_temp_template([..]) function. dbuf is never freed. And: in dpkg-deb/extract.c decompress_filter(decompressor, p1[0], p2_out, _(decompressing archive member)); which calls varbuf_vprintf(desc, desc_fmt, args); which calls varbuf_grow(v, needed + 1); WHICH CALLS v-buf = m_realloc(v-buf, v-size); is never freed. Thanks, -- -- Joshua Rogers https://internot.info/ signature.asc Description: OpenPGP digital signature
Bug#769514: emacs-calfw-howm: installation fails
Package: emacs-calfw-howm Version: 1.3+git20141005-1 Severity: serious User: debian...@lists.debian.org Usertags: instest-20141113 instest Hi, While testing the installation of all packages in sid, I ran into the following problem: Reading package lists... Building dependency tree... Reading state information... Starting pkgProblemResolver with broken count: 0 Starting 2 pkgProblemResolver with broken count: 0 Done The following extra packages will be installed: adwaita-icon-theme dconf-gsettings-backend dconf-service emacs-calfw emacs24 emacs24-bin-common emacs24-common emacsen-common fontconfig fontconfig-config fonts-dejavu-core gconf-service gconf2-common glib-networking glib-networking-common glib-networking-services gsettings-desktop-schemas hicolor-icon-theme howm imagemagick-common libasound2 libasound2-data libatk-bridge2.0-0 libatk1.0-0 libatk1.0-data libatspi2.0-0 libavahi-client3 libavahi-common-data libavahi-common3 libcairo-gobject2 libcairo2 libcolord2 libcroco3 libcups2 libdatrie1 libdbus-1-3 libdbus-glib-1-2 libdconf1 libexpat1 libffi6 libfftw3-double3 libfontconfig1 libfreetype6 libfribidi0 libgconf-2-4 libgd3 libgdk-pixbuf2.0-0 libgdk-pixbuf2.0-common libgif4 libglib2.0-0 libgmp10 libgnutls-deb0-28 libgomp1 libgpm2 libgraphite2-3 libgssapi-krb5-2 libgtk-3-0 libgtk-3-bin libgtk-3-common libharfbuzz0b libhogweed2 libice6 libjasper1 libjbig0 libjpeg62-turbo libjson-glib-1.0-0 libjson-glib-1.0-common libk5crypto3 libkeyutils1 libkrb5-3 libkrb5support0 liblcms2-2 libldap-2.4-2 liblockfile-bin liblockfile1 liblqr-1-0 libltdl7 libm17n-0 libmagickcore-6.q16-2 libmagickwand-6.q16-2 libnettle4 libotf0 libp11-kit0 libpango-1.0-0 libpangocairo-1.0-0 libpangoft2-1.0-0 libpixman-1-0 libpng12-0 libproxy1 librest-0.7-0 librsvg2-2 librsvg2-common libsasl2-2 libsasl2-modules-db libsm6 libsoup-gnome2.4-1 libsoup2.4-1 libsqlite3-0 libtasn1-6 libthai-data libthai0 libtiff5 libvpx1 libwayland-client0 libwayland-cursor0 libx11-6 libx11-data libxau6 libxcb-render0 libxcb-shm0 libxcb1 libxcomposite1 libxcursor1 libxdamage1 libxdmcp6 libxext6 libxfixes3 libxft2 libxi6 libxinerama1 libxkbcommon0 libxml2 libxpm4 libxrandr2 libxrender1 libxt6 m17n-db shared-mime-info ucf x11-common xkb-data Suggested packages: org-mode elscreen emacs24-common-non-dfsg emacs24-el ruby libasound2-plugins alsa-utils cups-common libfftw3-bin libfftw3-dev libgd-tools gnutls-bin gpm krb5-doc krb5-user gvfs libjasper-runtime liblcms2-utils m17n-docs libmagickcore-6.q16-2-extra librsvg2-bin gawk Recommended packages: at-spi2-core colord dbus libglib2.0-data xdg-user-dirs krb5-locales ghostscript gsfonts libsasl2-modules xml-core The following NEW packages will be installed: adwaita-icon-theme dconf-gsettings-backend dconf-service emacs-calfw emacs-calfw-howm emacs24 emacs24-bin-common emacs24-common emacsen-common fontconfig fontconfig-config fonts-dejavu-core gconf-service gconf2-common glib-networking glib-networking-common glib-networking-services gsettings-desktop-schemas hicolor-icon-theme howm imagemagick-common libasound2 libasound2-data libatk-bridge2.0-0 libatk1.0-0 libatk1.0-data libatspi2.0-0 libavahi-client3 libavahi-common-data libavahi-common3 libcairo-gobject2 libcairo2 libcolord2 libcroco3 libcups2 libdatrie1 libdbus-1-3 libdbus-glib-1-2 libdconf1 libexpat1 libffi6 libfftw3-double3 libfontconfig1 libfreetype6 libfribidi0 libgconf-2-4 libgd3 libgdk-pixbuf2.0-0 libgdk-pixbuf2.0-common libgif4 libglib2.0-0 libgmp10 libgnutls-deb0-28 libgomp1 libgpm2 libgraphite2-3 libgssapi-krb5-2 libgtk-3-0 libgtk-3-bin libgtk-3-common libharfbuzz0b libhogweed2 libice6 libjasper1 libjbig0 libjpeg62-turbo libjson-glib-1.0-0 libjson-glib-1.0-common libk5crypto3 libkeyutils1 libkrb5-3 libkrb5support0 liblcms2-2 libldap-2.4-2 liblockfile-bin liblockfile1 liblqr-1-0 libltdl7 libm17n-0 libmagickcore-6.q16-2 libmagickwand-6.q16-2 libnettle4 libotf0 libp11-kit0 libpango-1.0-0 libpangocairo-1.0-0 libpangoft2-1.0-0 libpixman-1-0 libpng12-0 libproxy1 librest-0.7-0 librsvg2-2 librsvg2-common libsasl2-2 libsasl2-modules-db libsm6 libsoup-gnome2.4-1 libsoup2.4-1 libsqlite3-0 libtasn1-6 libthai-data libthai0 libtiff5 libvpx1 libwayland-client0 libwayland-cursor0 libx11-6 libx11-data libxau6 libxcb-render0 libxcb-shm0 libxcb1 libxcomposite1 libxcursor1 libxdamage1 libxdmcp6 libxext6 libxfixes3 libxft2 libxi6 libxinerama1 libxkbcommon0 libxml2 libxpm4 libxrandr2 libxrender1 libxt6 m17n-db shared-mime-info ucf x11-common xkb-data 0 upgraded, 132 newly installed, 0 to remove and 0 not upgraded. Need to get 60.1 MB of archives. After this operation, 224 MB of additional disk space will be used. Get:1 http://localhost:/debian/ jessie/main libgmp10 amd64 2:6.0.0+dfsg-6 [253 kB] Get:2 http://localhost:/debian/ jessie/main libnettle4 amd64 2.7.1-3 [175 kB] Get:3 http://localhost:/debian/ jessie/main libhogweed2 amd64 2.7.1-3 [125 kB] Get:4 http://localhost:/debian/
Bug#747568: rtkit-daemon.service:32] Unknown lvalue 'ControlGroup'
Am Freitag, den 14.11.2014, 00:08 -0300 schrieb Felipe Sateler: Ha! It works! The problem seems to be one of units: the rtkit-test program wrongly set RTTIME to 3 orders of magnitude higher than the max timeout allowed by rtkit-daemon. So, I have been on a goose chase all this time :/. On the bright side, we now know rtkit is not broken under systemd :) Great job, Felipe, thanks for looking into this! - Fabian -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#769515: Another
And just one more before I'm done... dpkg-deb/build.c m= m_malloc(strlen(dir) + sizeof(DEBEXT)); m is never freed. Thanks, -- -- Joshua Rogers https://internot.info/ signature.asc Description: OpenPGP digital signature
Bug#768022: mercurial: 3.2 has been released
Hi Faheem, On Tue, Nov 11, 2014 at 06:04:55PM +0530, Faheem Mitha wrote: On Thu, 6 Nov 2014, Javi Merino wrote: On Tue, Nov 04, 2014 at 02:58:31PM +0530, Faheem Mitha wrote: Package: mercurial Version: 3.1.2-1~bpo70+1 Severity: wishlist Dear Maintainer, Hi Faheem, Please consider packaging 3.2. I can build it myself, but the Debian patches have changed enough since the last release that they are no longer trivial to re-sync. If you could just refresh the patches, that would be helpful. Thanks. It's not as easy as refreshing the patches as you have seen. I'm working on it and I hope to upload it before Sunday. It will go to experimental though. I missed your email. I just saw it now. It looks like you have just uploaded to experimental. I've seen that you are using the backported version. As Jessie will release with 3.1.2, wheezy-backports will stay with 3.1.2. I can upload 3.2 (well, 3.2.1, which shall be uploaded soon) to wheezy-backports-sloppy if you are interested in it. If you need help with the Debian packaging, let the community know. There are people who can help. The package is team-maintained, I'm just the most regular uploader. Other people have uploaded mercurial when I was unavailable. So yes, I know there is a community and no, I'm not *the* maintainer but *a* maintainer. Cheers, Javi signature.asc Description: Digital signature
Bug#763164: (no subject)
The same here, this bug is very important for us, we massively use _ in our bash functions in all our procedures, another shellshock patch would be greatly appreciated ;) -- --- Mathieu POURCEL Technicien systèmes et réseaux LEGOS - UMR 5566 Bureau 41 / D033 Observatoire Midi-Pyrénées 14, avenue Edouard Belin 31400 Toulouse tel : : +33 (0)5 61 33 29 41 fax : : +33 (0)5 61 25 32 05 -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#758973: [fontconfig-config] Stop breaking user configuration in /etc/fonts/conf.d/ after every upgrade
Control: tags -1 + moreinfo On Sat, Aug 23, 2014 at 01:36:55PM +0200, Vedran Fura?? wrote: Every time I change fontconfig configuration by removing symlinks in /etc/fonts/conf.d/ you return it back after upgrade. This is /etc and you should preserve local changes during package upgrades per policy (10.7.3). Looking at the fontconfig-config config and postinst script, one can see that fontconfig-config does in principle take care of this issue by preseeding the debconf questions with tests for those symlinks. I therefore ask you to add more detail to this bug. Can you point out which file you were trying to remove? When doing so, please Cc me and remove the moreinfo tag added in this mail. Thanks Helmut -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#766299: [pkg-x2go-devel] Bug#766299: nxproxy: BIG-REQUESTS patch builds but fails at runtime
Hi Paul, On Do 13 Nov 2014 23:33:03 CET, Mike Gabriel wrote: Dear Paul, On Mi 12 Nov 2014 21:22:51 CET, Paul Szabo wrote: Dear Mike, My current patches, for BIG-REQUESTS and Generic Event Extension, below. With these, nxproxy works well. (Though, once a crash was observed, unfortunately not trapped or de-bugged, yet...) Some other patches, that make nxproxy more useful in my environment, below also (hoping others find them, or those ideas, useful also). --- I compared the efficiency of the various compressors, recorded network traffic generated when using plain uncompressed X11 traffic, ssh -C, dxpc and nxproxy, showing kBytes received and transmitted: Whatplain ssh dxpcnxproxy texworks 6828R 4816T2342R 1240T 3050R 4718T 2535R 429T libreoffice 2055R 199T1205R 130T 1145R 140T 1230R 131T matlab 51691R 1508T2096R 311T 2122R 303T 1894R 232T mathematica5 2508R 1004T1473R 522T 1354R 384T 1307R 312T mathematica933271R 5767T4118R 858T 3465R 4943T 4581R 808T and a certain youtube video in kBytes/sec (approx): Whatplain ssh dxpcnxproxy youtube 22000R 510T 16000R 300T ? 17000R 410T I wonder if it is worthwhile to persist with nxproxy, or maybe should try to use ssh -C in some automated way. Cheers, Paul Paul Szabo p...@maths.usyd.edu.au http://www.maths.usyd.edu.au/u/psz/ School of Mathematics and Statistics University of SydneyAustralia big-requests and generic-events patch applied upstream [1]. Once the nightly builds of nx-libs are through, you can obtain bin:packages at [2] Thanks a lot!!! Mike Unfortunately, your patch does not build cleanly (FTBFS!). https://jenkins.x2go.org:8443/view/NX/job/nx-libs+nightly+debian-sid/63/console Any idea why? Mike -- DAS-NETZWERKTEAM mike gabriel, herweg 7, 24357 fleckeby fon: +49 (1520) 1976 148 GnuPG Key ID 0x25771B31 mail: mike.gabr...@das-netzwerkteam.de, http://das-netzwerkteam.de freeBusy: https://mail.das-netzwerkteam.de/freebusy/m.gabriel%40das-netzwerkteam.de.xfb pgp2ME2R0hZ1J.pgp Description: Digitale PGP-Signatur
Bug#769448: [Pkg-zsh-devel] Bug#769450: zsh-static unsets $USERNAME
tag 354633 + confirmed retitle 354633 zsh-static: %n in prompt expansion no longer set as root with 4.3.0-dev-5-1 retitle 354631 zsh-static: error in compaudit with 4.3.0-dev-5-1 as root forcemerge 354631 354633 769448 769450 thanks Hi, Vincent Lefevre wrote: On 2014-11-14 01:46:40 +0100, Axel Beckert wrote: [...] And USE_GETPWUID is not set in the static build. It's disabled in debian/rules: STATICFLAGS += --disable-dynamic-nss This is probably the way how https://bugs.debian.org/207218 (changes in libc cause zsh-static to immediately segfault) was fixed. The ChangeLog says: Run dpkg-shlibdebs on /lib/libnss_files.so.* for zsh-static to help avoid segfaults due to continually-changing glibc NSS ABI. Yep. That's how I got the idea to look at --disable-dynamic-nss. But if the NSS ABI changes in an incompatible manner, the soname should change, i.e. this was probably a bug in libc6. Indeed. But see below, that's no bug in libc6 as the SONAME does change. Additionally, that mentioned dpkg-shlibdebs call is no more there. But there's no other changelog entry which mentions dpkg-shlibdebs again. Maybe this one from 4.3.0-dev-4-3 is the one where it got removed again: * For zsh-static, don't link against anything that requires NSS. I wonder if #207218 would reappear nowadays, if we remove that line above from debian/rules. Removing that line definitely solves this issue, I just tried it. Does this mean that zsh-static wouldn't really be a static build because using the dynamic NSS library? That's another question I wondered about, too. At least that's no more the case: → ldd /bin/zsh-static not a dynamic executable Even not with disabling that line: → ldd obj-static/Src/zsh not a dynamic executable But then again I found https://bugs.debian.org/354631 and https://bugs.debian.org/354633 already reported back in 2006. It's currently blocked by https://bugs.debian.org/471208 (libncurses5: ncurses+dietlibc) since Clint's plan seems to have been to use the NSS routines from dietlibc for the static build. But I don't expect this to happen anytime soon. In #354631 is stated that the compaudit:$linenumber: unknown group issue first shows up in compaudit:107: unknown group. Actually I think it was already present in 4.3.0-dev-4-3 uploaded one day before, because that's the one this changelog entry: For zsh-static, don't link against anything that requires NSS. It also claims that this only happens as root. But at least on Wheezy I also get it as normal user. But I suspect that only happens because the reporter likely uses zsh-static as root, but only zsh as user. A strong indication for this is at https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=354633#20 In https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=354631#27 Clint writes: [...] the problem is that user/group lookups are disabled in the -static build because glibc's NSS ABI is unstable and static binaries still need to load NSS modules dynamically. If we re-enable lookups, then zsh-static will segfault on any major libc upgrade. I don't know what the best solution here is. That IMHO explains well why a statically complied binary still needs dynamically linked libraries -- which may change their ABI _with_ an SONAME bump, so no bug in libc6, but zsh-static should likely depend on libc6 (= $current_glibc_upstream_version), libc6 ( $next_glibc_upstream_version) if we remove STATICFLAGS += --disable-dynamic-nss from debian/rules. So I'm no more sure if removing that line is really a good idea. OTOH: We are thinking about dropping the zsh-static package after Jessie anyways. Popcon's vote is around 25 and such issues don't seem to have bothered people too much since 2006. So if anyone wants to keep zsh-static and is reading this, please _tell_ us! Regards, Axel -- ,''`. | Axel Beckert a...@debian.org, http://people.debian.org/~abe/ : :' : | Debian Developer, ftp.ch.debian.org Admin `. `' | 1024D: F067 EA27 26B9 C3FC 1486 202E C09E 1D89 9593 0EDE `-| 4096R: 2517 B724 C5F6 CA99 5329 6E61 2FF9 CD59 6126 16B5 -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#769516: ITP: liberasurecode -- support of multiple erasure code backends
Package: wnpp Severity: wishlist Owner: Thomas Goirand z...@debian.org * Package name: liberasurecode Version : 0.9.10 Upstream Author : Eric Lambert eric_lamb...@xyratex.com * URL : https://bitbucket.org/tsg-/liberasurecode * License : BSD-style Programming Lang: C Description : support of multiple erasure code backends Liberasurecode is an erasure code library which can support multiple erasure code 'backends'. The repository includes a Jerasure for Reed-Solomon implementation. This library is a dependency of PyECLib, which will be soon a dependency for OpenStack swift. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#747568: rtkit-daemon.service:32] Unknown lvalue 'ControlGroup'
Hi again, Am Freitag, den 14.11.2014, 00:08 -0300 schrieb Felipe Sateler: Ha! It works! The problem seems to be one of units: the rtkit-test program wrongly set RTTIME to 3 orders of magnitude higher than the max timeout allowed by rtkit-daemon. I assume you are refering to this line rlim.rlim_cur = rlim.rlim_max = 1ULL; /* 100ms */ in which it sets the limit to 100 million microseconds, which is 100 seconds, though the comment suggests that it is supposed to be 100 miliseconds. I think this is a severe bug, since it makes the tests fail 100% cases. Are you going to report it upstream? And why didn't you include the fix in the package that you just requested a freeze exception for? Thanks again! - Fabian -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#768022: mercurial: 3.2 has been released
On Fri, 14 Nov 2014, Javi Merino wrote: Hi Faheem, I've seen that you are using the backported version. As Jessie will release with 3.1.2, wheezy-backports will stay with 3.1.2. I can upload 3.2 (well, 3.2.1, which shall be uploaded soon) to wheezy-backports-sloppy if you are interested in it. Sure, I'm interested, and I expect other people are too. I think the Mercurial project has itself considered providing Debian backports, but that hasn't happened so far, presumably due to a lack of manpower. If you need help with the Debian packaging, let the community know. There are people who can help. The package is team-maintained, I'm just the most regular uploader. Other people have uploaded mercurial when I was unavailable. So yes, I know there is a community and no, I'm not *the* maintainer but *a* maintainer. Cheers, Ok. I don't know the current situation of the team. Just saying. Regards, Faheem -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#761986: Me too!
Great...I think, but I am confused (well, I guess I've always been). Can you send over a log when running a replay session. * Use the debian xnee * Use the touchpad * Replay (something) like this: cnee --replay --file xnee_debian_touchpad.xns --verbose -e touchpadd.err the important thind is to use the --verbose option /h On Mon, Nov 10, 2014 at 03:13:22PM -0800, Dima Kogan wrote: Henrik Sandklef h...@sandklef.com writes: Can you run the same command you had problem with: cnee --record --mouse -o /tmp/xnee.xns --first-last --smp and use a mouse instead of the Touchpad. This is really not likely the cause, but I would like to make sure. That's it! Currently my laptop is on a docking station, so both a touchpad and a USB mouse are available. Recording events from the USB mouse works just fine, but recording events from the touchpad requires --force-core-replay, as described previously. This is both with the stock xnee and with the one you sent a few days ago. I'm attaching 4 xnee recordings, showing all combinations of (USB,touchpad) and (debian cnee,patched cnee). -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#769517: netsurf-gtk: netsurf shows 2 ssl windows for 1 certificate and crashes
Package: netsurf-gtk Version: 3.2+dfsg-2+b1 Severity: important When I tried netsurf to look at planet.debian.org today it brings up 2 SSL certificate problem windows for the same certificate. If I reject on the first then the 2nd one goes blank. If I then click Accept or Reject then netsurf aborts with the message below $ netsurf netsurf: desktop/tree.c:239: treeview_test_mouse_action: Assertion `ssl_current_session != ((void *)0) Can't use sslcert window after sslcert_viewer_fini()' failed. Aborted Regards, Daniel -- System Information: Debian Release: jessie/sid APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.16-3-amd64 (SMP w/2 CPU cores) Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages netsurf-gtk depends on: ii libc62.19-13 ii libcairo21.14.0-2.1 ii libcurl3 7.38.0-3 ii libexpat12.1.0-6+b2 ii libgdk-pixbuf2.0-0 2.31.1-2+b1 ii libglib2.0-0 2.42.0-2 ii libgtk2.0-0 2.24.25-1 ii libjpeg62-turbo 1:1.3.1-10 ii libmozjs185-1.0 1.8.5-1.0.0+dfsg-4.3 ii libpango-1.0-0 1.36.8-2 ii libpangocairo-1.0-0 1.36.8-2 ii libpng12-0 1.2.50-2+b1 ii librsvg2-2 2.40.5-1 ii libssl1.0.0 1.0.1j-1 ii netsurf-common 3.2+dfsg-2 ii zlib1g 1:1.2.8.dfsg-2 Versions of packages netsurf-gtk recommends: ii mime-support 3.57 netsurf-gtk suggests no packages. -- no debconf information signature.asc Description: Digital signature
Bug#769518: libgl1-mesa-dri: Failed to open BO for returned DRI2 buffer (1680x1050, dri2 back buffer, named 18)
Package: libgl1-mesa-dri Version: 10.3.2-1 Severity: normal Dear Maintainer, While trying to view a movie full-screen I got a segfault using mpv. Installing the -dbg packages it seems to be within the i915 driver itself. I've had multiples freeze since I moved to jessie BTW (eg. using lightspark as SWF plugin). Steps: $ mpv movie.mp4 [...] [stream] Video (+) --vid=1 (*) (h264) [stream] Audio (+) --aid=1 --alang=eng (*) (aac) File tags: major_brand: isom minor_version: 512 compatible_brands: isomiso2avc1mp41 encoder: Lavf55.12.100 [New Thread 0x7fffe0827700 (LWP 32051)] [New Thread 0x7fffdbfff700 (LWP 32052)] [New Thread 0x7fffd949d700 (LWP 32053)] [New Thread 0x7fffd8c9c700 (LWP 32054)] [New Thread 0x7fffd3fff700 (LWP 32055)] [New Thread 0x7fffd37fe700 (LWP 32056)] [New Thread 0x7fffd2ffd700 (LWP 32057)] [New Thread 0x7fffd27fc700 (LWP 32058)] AO: [pulse] 44100Hz stereo 2ch float VO: [opengl] 852x480 = 852x480 yuv420p Failed to open BO for returned DRI2 buffer (1680x1050, dri2 back buffer, named 18). This is likely a bug in the X Server that will lead to a crash soon. Program received signal SIGSEGV, Segmentation fault. [Switching to Thread 0x7fffdbfff700 (LWP 32052)] brw_meta_fast_clear (brw=brw@entry=0x7fffd4097a08, fb=fb@entry=0x7fffd40fa900, buffers=buffers@entry=2, partial_clear=partial_clear@entry=false) at ../../../../../../../src/mesa/drivers/dri/i965/brw_meta_fast_clear.c:447 447 ../../../../../../../src/mesa/drivers/dri/i965/brw_meta_fast_clear.c: No such file or directory. (gdb) bt #0 brw_meta_fast_clear (brw=brw@entry=0x7fffd4097a08, fb=fb@entry=0x7fffd40fa900, buffers=buffers@entry=2, partial_clear=partial_clear@entry=false) at ../../../../../../../src/mesa/drivers/dri/i965/brw_meta_fast_clear.c:447 #1 0x7fffdb3c2a48 in brw_clear (ctx=0x7fffd4097a08, mask=2) at ../../../../../../../src/mesa/drivers/dri/i965/brw_clear.c:246 #2 0x55637269 in gl_video_render_frame (p=0x7fffd40fded0) at ../video/out/gl_video.c:1614 #3 0x5563c354 in draw_image (vo=optimized out, mpi=0x56370e00) at ../video/out/vo_opengl.c:167 #4 0x55639fa3 in render_frame (vo=0x5631de90) at ../video/out/vo.c:581 #5 vo_thread (ptr=0x5631de90) at ../video/out/vo.c:679 #6 0x76ac20a4 in start_thread (arg=0x7fffdbfff700) at pthread_create.c:309 #7 0x700b3ccd in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:111 -- Package-specific info: glxinfo: name of display: :0 display: :0 screen: 0 direct rendering: Yes server glx vendor string: SGI server glx version string: 1.4 server glx extensions: GLX_ARB_create_context, GLX_ARB_create_context_profile, GLX_ARB_create_context_robustness, GLX_ARB_fbconfig_float, GLX_ARB_framebuffer_sRGB, GLX_ARB_multisample, GLX_EXT_create_context_es2_profile, GLX_EXT_framebuffer_sRGB, GLX_EXT_import_context, GLX_EXT_texture_from_pixmap, GLX_EXT_visual_info, GLX_EXT_visual_rating, GLX_INTEL_swap_event, GLX_MESA_copy_sub_buffer, GLX_OML_swap_method, GLX_SGIS_multisample, GLX_SGIX_fbconfig, GLX_SGIX_pbuffer, GLX_SGIX_visual_select_group, GLX_SGI_swap_control client glx vendor string: Mesa Project and SGI client glx version string: 1.4 client glx extensions: GLX_ARB_create_context, GLX_ARB_create_context_profile, GLX_ARB_create_context_robustness, GLX_ARB_fbconfig_float, GLX_ARB_framebuffer_sRGB, GLX_ARB_get_proc_address, GLX_ARB_multisample, GLX_EXT_buffer_age, GLX_EXT_create_context_es2_profile, GLX_EXT_fbconfig_packed_float, GLX_EXT_framebuffer_sRGB, GLX_EXT_import_context, GLX_EXT_texture_from_pixmap, GLX_EXT_visual_info, GLX_EXT_visual_rating, GLX_INTEL_swap_event, GLX_MESA_copy_sub_buffer, GLX_MESA_multithread_makecurrent, GLX_MESA_query_renderer, GLX_MESA_swap_control, GLX_OML_swap_method, GLX_OML_sync_control, GLX_SGIS_multisample, GLX_SGIX_fbconfig, GLX_SGIX_pbuffer, GLX_SGIX_visual_select_group, GLX_SGI_make_current_read, GLX_SGI_swap_control, GLX_SGI_video_sync GLX version: 1.4 GLX extensions: GLX_ARB_create_context, GLX_ARB_create_context_profile, GLX_ARB_create_context_robustness, GLX_ARB_fbconfig_float, GLX_ARB_framebuffer_sRGB, GLX_ARB_get_proc_address, GLX_ARB_multisample, GLX_EXT_create_context_es2_profile, GLX_EXT_framebuffer_sRGB, GLX_EXT_import_context, GLX_EXT_texture_from_pixmap, GLX_EXT_visual_info, GLX_EXT_visual_rating, GLX_INTEL_swap_event, GLX_MESA_copy_sub_buffer, GLX_MESA_multithread_makecurrent, GLX_MESA_query_renderer, GLX_MESA_swap_control, GLX_OML_swap_method, GLX_OML_sync_control, GLX_SGIS_multisample, GLX_SGIX_fbconfig, GLX_SGIX_pbuffer, GLX_SGIX_visual_select_group, GLX_SGI_make_current_read, GLX_SGI_swap_control, GLX_SGI_video_sync OpenGL vendor string: Intel Open Source Technology Center OpenGL renderer string: Mesa DRI Intel(R) Sandybridge Desktop OpenGL core profile version string: 3.1 (Core Profile) Mesa 10.3.2
Bug#769518: Acknowledgement (libgl1-mesa-dri: Failed to open BO for returned DRI2 buffer (1680x1050, dri2 back buffer, named 18))
Dear maintainer, Feel free to merge with #764757. Since the stacktrace was not identical, I believe the two bugs are distincts. Regards -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#570623: reprepro: please add multiple version management
What is the status of this project? It looks complete so what is needed to have this merged? Let me know how I can help!
Bug#769519: ITP: python-pyeclib -- interface for implementing erasure codes
Package: wnpp Severity: wishlist Owner: Thomas Goirand z...@debian.org * Package name: python-pyeclib Version : 0.9.10 Upstream Author : Kevin Greenan kmgre...@gmail.com * URL : https://bitbucket.org/kmgreen2/pyeclib * License : BSD-2-clause Programming Lang: C, Python Description : interface for implementing erasure codes This library provides a simple Python interface for implementing erasure codes. To obtain the best possible performance, the underlying erasure code algorithms are written in C. . This library makes use of Jerasure for Reed-Solomon and provides its own flat XOR-based erasure code encoder and decoder. Currently, it implements a specific class of HD Combination Codes (see Flat XOR-based erasure codes in storage systems: Constructions, efficient recovery, and tradeoffs in IEEE MSST 2010). These codes are well-suited to archival use-cases, have a simple construction and require a minimum number of participating disks during single-disk reconstruction (think XOR-based LRC code). This will soon be a dependency in Swift when they will implement erasure code. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#763043: x86 emulation does not work on arm host
Excerpts from Michael Tokarev's message of Fri Nov 14 08:43:32 +0100 2014: 11.11.2014 17:07, Michal Suchanek wrote: Excerpts from Michael Tokarev's message of Tue Nov 11 14:16:23 +0100 2014: 11.11.2014 13:18, Michal Suchanek wrote: [] So, to rehash, do I understand it right that you're having probs with running x86 binaries on arm, when using -user-binfmt but not when using -user-static ? I am having problem running x86 binaries on arm with either package. Aha. That is entirely different thing. Retitling the bugreport accordingly. Please correct me if I'm wrong. That's not entirely true. It only fails for static binaries and I happened to have a statically linked application. I am able to run full x86 wine at racing snail speed. Probably because it's dynamically linked. Does it help if you invoke qemu-x86_64[-static] to run your non-working executables, like, say, qemu-x86_64 /usr/bin/cdebootstrap-static ? # qemu-x86_64 /usr/bin/cdebootstrap-static /usr/bin/cdebootstrap-static: missing suite argument Try `/usr/bin/cdebootstrap-static --help' for more information. # cdebootstrap-static -bash: /usr/bin/cdebootstrap-static: cannot execute binary file: Exec format error This way we'll know if it is binfmt registration which is broken or qemu. It might sure be some missing binfmt bits. [] # unrar /? qemu: uncaught target signal 11 (Segmentation fault) - core dumped Segmentation fault # apt-get install cdebootstrap-static:amd64 # cdebootstrap-static /? -bash: /usr/bin/cdebootstrap-static: cannot execute binary file What is the version of unrar and cdebootstrap-static? I want to reproduce the problem so that it's possible to go from here. Just whatever was in the archive: ii cdebootstrap-static 0.6.3 amd64 Bootstrap a Debian system - static binary ii unrar 1:5.0.10-1 amd64 Unarchiver for .rar files (non-free version) Please note that x86 qemu user target is one of less tested targets, because it is rather uncommon to run x86 hw on non-x86 platform, usually it is the opposite. If somebody was using the emulation bug like this would not exist. The emulation also does not work that well - the unrar binary is crashing in the emulation and presumably just runs normally on x86. CPU is Allwinner A13 sun5i ARM Cortex A8 ARMv7, armhf architecture: # dpkg-architecture DEB_BUILD_ARCH=armhf DEB_BUILD_ARCH_BITS=32 DEB_BUILD_ARCH_CPU=arm DEB_BUILD_ARCH_ENDIAN=little DEB_BUILD_ARCH_OS=linux DEB_BUILD_GNU_CPU=arm DEB_BUILD_GNU_SYSTEM=linux-gnueabihf DEB_BUILD_GNU_TYPE=arm-linux-gnueabihf DEB_BUILD_MULTIARCH=arm-linux-gnueabihf DEB_HOST_ARCH=armhf DEB_HOST_ARCH_BITS=32 DEB_HOST_ARCH_CPU=arm DEB_HOST_ARCH_ENDIAN=little DEB_HOST_ARCH_OS=linux DEB_HOST_GNU_CPU=arm DEB_HOST_GNU_SYSTEM=linux-gnueabihf DEB_HOST_GNU_TYPE=arm-linux-gnueabihf DEB_HOST_MULTIARCH=arm-linux-gnueabihf DEB_TARGET_ARCH=armhf DEB_TARGET_ARCH_BITS=32 DEB_TARGET_ARCH_CPU=arm DEB_TARGET_ARCH_ENDIAN=little DEB_TARGET_ARCH_OS=linux DEB_TARGET_GNU_CPU=arm DEB_TARGET_GNU_SYSTEM=linux-gnueabihf DEB_TARGET_GNU_TYPE=arm-linux-gnueabihf DEB_TARGET_MULTIARCH=arm-linux-gnueabihf # cat /proc/cpuinfo Processor : ARMv7 Processor rev 2 (v7l) BogoMIPS : 298.17 Features : swp half thumb fastmult vfp edsp neon vfpv3 tls CPU implementer : 0x41 CPU architecture: 7 CPU variant : 0x3 CPU part : 0xc08 CPU revision : 2 Hardware : sun5i Revision : Serial: Thanks Michal -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#768922: pacemaker: stopped working after upgrade to 1.1.10+git20130802-4.1
Pacemaker was compiled in unstable to a newer version of libqb0 (0.14 or 0.17). In testing/jessie there's only libqb0 (0.11). I'm not (at least not intentionally) pulling in packages from unstable. Both pacemaker and libcrmcommon3 seem to be from testing/jessie: # apt-cache policy libcrmcommon3 pacemaker libcrmcommon3: Installed: 1.1.10+git20130802-4.1 Candidate: 1.1.10+git20130802-4.1 Version table: *** 1.1.10+git20130802-4.1 0 500 http://ftp.us.debian.org/debian/ jessie/main amd64 Packages 100 /var/lib/dpkg/status pacemaker: Installed: 1.1.10+git20130802-4.1 Candidate: 1.1.10+git20130802-4.1 Version table: *** 1.1.10+git20130802-4.1 0 500 http://ftp.us.debian.org/debian/ jessie/main amd64 Packages 100 /var/lib/dpkg/status From /var/lib/dpkg/status: Package: libcrmcommon3 Status: install ok installed Priority: optional Section: libs Installed-Size: 346 Maintainer: Debian HA Maintainers debian-ha-maintain...@lists.alioth.debian.org Architecture: amd64 Source: pacemaker Version: 1.1.10+git20130802-4.1 Replaces: libcrmcommon2, pacemaker (= 1.0.9.1+hg15626-2) Depends: libbz2-1.0, libc6 (= 2.17), libglib2.0-0 (= 2.28.0), libgnutls-deb0-28 (= 3.3.0), libltdl7 (= 2.4.2), libpam0g (= 0.99.7.1), libpils2 (= 1.0.12~rc1+hg2777), libplumb2 (= 1.0.12~rc1+hg2777), libqb0, libuuid1 (= 2.16), libxml2 (= 2.7.4), libxslt1.1 (= 1.1.25) Conflicts: libcrmcommon2, pacemaker (= 1.0.9.1+hg15626-2) Description: Pacemaker libraries - common CRM This package contains some of the libraries provided by and needed for the pacemaker cluster manager. You need to install them if you intend to run pacemaker. Specifically, this package contains the common CRM library. Homepage: http://clusterlabs.org/ Could it be possible that something in testing (pacemaker or a dependency) was compiled against the newer version of libqb0? After all, the issue surfaced when I apt-get upgraded pacemaker. fix would be to add a libqb0 (=0.14) as dependency in package libcrmcommon3. This seems to be the cleaner fix. Looking at the libcrmcommon3 dependencies, libqb0 is the only non-version-numbered dependency. Can this fix be implemented? Additionally, jessie's libqb0 would need to be upgraded to =0.14. Frank -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#768730: [Debian-med-packaging] Bug#768730: [lu...@lucas-nussbaum.net: Bug#768730: python-mne: FTBFS in jessie: Tests failures]
hi, FYI here is a clean commit that should fix the problem: https://github.com/mne-tools/mne-python/commit/b9d4df78db7aaeda1feb58c18b0071934de2361e otherwise the patch attached skips the tests (quick fix). Hope this helps Alex On Tue, Nov 11, 2014 at 7:16 AM, Andreas Tille andr...@fam-tille.de wrote: On Mon, Nov 10, 2014 at 06:05:36PM -0500, Yaroslav Halchenko wrote: On Mon, 10 Nov 2014, Andreas Tille wrote: On Mon, Nov 10, 2014 at 12:51:39PM -0500, Yaroslav Halchenko wrote: amount of changes from 0.8.4 to 0.8.6 seems to be miniscule and just a bug fix so we could demand unblock for this one I'll take the bet that this will fail. I personally would not try to stress test the patience of the release team. ;-) well -- the changes are indeed miniscule (if I got it right) and just a bugfix anyways I guess -- I bet RT can swallow this one To my experience over several releases it does not matter at all how small the upstream bugfixes might be. Freeze means only RC bugs will be fixed. Your only chance to get this through is if you file an RC bug which is fixed by the diff between 0.8.4 to 0.8.6 - but I doubt that this is rectified. The release team is following the rules very strictly so I think you will loose your bet. BTW, I would concentrate on the question why the tests that passed before are failing now. Kind regards Andreas. -- http://fam-tille.de skip_failing_tests.patch Description: Binary data
Bug#767677: [Android-tools-devel] Bug#767677: android-permissions: fails to install: useradd: group '1004' does not exist
This is an unusual package because it should only ever been installed in a Debian chroot that is running on an Android device. I cannot think of any other instance that makes sense to install this package. So if anyone can think of better tests to enforce that, that would be good. Also, piuparts provides a valuable service, so it makes sense to make this package work with piuparts. So it might just be a matter of tweaking the script to make it piuparts-compatible. .hc -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#769129: unblock: busybox/1:1.22.0-10
On Tue, Nov 11, 2014 at 20:02:35 +0300, Michael Tokarev wrote: So this was a bit preliminary (following the notify the release team early rule too aggressively) -- this very Built-Using generation was broken due to an error on my part (trivial) and due to bug in dpkg, #588505. I just uploaded new release fixing this, 1:1.22.0-11, will see how it goes first, and will ping this bug if everything is okay. (Yes, I verified the fixed release builds on kfreebsd-amd64 where the problematic release failed). FWIW I don't believe build-conflicts on libc achieve anything, so I'm unhappy with -13. Cheers, Julien signature.asc Description: Digital signature
Bug#767554: python-persistent and python-zodb: error when trying to install together
Barry Warsaw ba...@debian.org writes: On Nov 12, 2014, at 05:50 PM, Arnaud Fontaine wrote: From upstream point of view, ZODB3 (aka python-zodb in Debian) used to include persistent, BTrees, ZODB and ZEO modules. However, since ZODB3 3.11.0a1, upstream has split it up into 4 distinct packages (one for each module), bump the version to 4.0 and made ZODB3 a metapackage depending on all of them. It looks like Debian still has zodb 3.9.7, right? Unfortunately, yes. As of fixing this RC bug for Jessie: Among the four, only persistent package is currently available in Debian, so there is no way to get rid of ZODB3 (at least for Jessie). Barry: If persistent = 4.0 Debian package is useful on its own to anyone (and thus should not be removed From testing), then can I add a Conflict on both packages and upload them to fix this bug? IIRC, I needed to update python-persistent for the Python 3 zope.component transition, as it's a build-dep. There are no other reverse dependencies that I know of. I think a Conflicts is the right way to handle this for now, given where we are in the Jessie release cycle. Arnaud, thanks for handling this! If that's ok with you, I'm going to upload both packages to fix this bug: * python-persistent: Conflicts: python-zodb ( 3.11.0~) * python-zodb: Conflicts: python-persistent Cheers, -- Arnaud Fontaine signature.asc Description: PGP signature
Bug#765484: [Openjdk] Bug#765484: qdox: FTBFS (hangs) on armhf.
Hello, 2014-11-13 5:22 GMT+01:00 Matthias Klose d...@debian.org: Using openjdk-7-jre 7u65-2.5.2-4, (but works using openjdk-7-jre 7u55-2.4.7-1) [..] does this work with jamvm or pure zero? It uses default-jdk, which pulls in openjdk-7-jre-headless, which seems to be pure zero VM. Note, it used to work with openjdk-7-jre (7u55-2.4.7-1) I was trying jamvm, but at the moment, I have been unable to make the package build with it. Regards, -- Héctor Orón -.. . -... .. .- -. -.. . ...- . .-.. --- .--. . .-. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#763043: x86 emulation does not work on arm host
14.11.2014 12:35, Michal Suchanek wrote: [] # qemu-x86_64 /usr/bin/cdebootstrap-static /usr/bin/cdebootstrap-static: missing suite argument Try `/usr/bin/cdebootstrap-static --help' for more information. # cdebootstrap-static -bash: /usr/bin/cdebootstrap-static: cannot execute binary file: Exec format error Aha. So it is just the binfmt registration problem -- the magic strings. I'll take a look at this. [] Please note that x86 qemu user target is one of less tested targets, because it is rather uncommon to run x86 hw on non-x86 platform, usually it is the opposite. If somebody was using the emulation bug like this would not exist. The emulation also does not work that well - the unrar binary is crashing in the emulation and presumably just runs normally on x86. There are *many* issues with user-mode emulation in qemu today. For one, threaded applications does not work (they work sometimes by pure luck), because qemu does not even try to implement multi-threaded support, but in modern world, lots of non-multithreaded apps uses clone() or some thread primitives internally behind the scenes, so many even non-MT apps doesn't work. Implementing mt mode in qemu means major redesign of whole thing. This is probably a reason why unrar is crashing. Also, qemu does not implement many system calls, especially more modern ones. So it is not that simple -- if someone was using, it would work -- no, not at all, things are much more complex, someone should actually do the work. CPU is Allwinner A13 sun5i ARM Cortex A8 ARMv7, armhf architecture: # dpkg-architecture DEB_BUILD_ARCH=armhf Ok, thank you. I'll see if I can fix the magic strings -- after that, static executables should work. Thanks, /mjt -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#584472: FOP and OpenType
Trunk FOP version now supports OpenType fonts. Please consider to update package. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#754121: aiccu fails to start with systemd
Severity: important Lowering severity to important. Causing a package for removal because somebody decided on a new init system that is not backwards compatible is not a critical thing. Also, you can always start AICCU simply by typing 'aiccu start' which is what the init script does. I'll install a VM over the weekend and check what the heck is wrong with this and resolve it properly. It would be extremely useful if you can actually provide logs and other details btw. Greets, Jeroen -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#769335: otrs2: fails to upgrade from 'wheezy': /usr/share/dbconfig-common/scripts/otrs2/upgrade/pgsql/3.2.1 exited with non-zero status
= dbconfig creates and handle database.pm and it is generated with the following values: dbc_generate_include_owner=otrs:www-data dbc_generate_include_perms=0640 = Can't locate /etc/otrs/database.pm: Permission denied at /usr/share/otrs/Kernel/Config.pm line 27. = line 26 checks for the existance of database.pm. if it exists (-f) then a require is executed in line 27, which is the case here, but you have got wrong permissions? which ones? = this whole issue is not triggered in my manual wheezy-jessie upgrade process = and again, dbconfig-common handles this file, but I think the bug is in your testing suite/piuparts We had a bug in dbconfig-common exactly in this area. It might be that this bug is a duplicate of bug 767248 that was fixed recently. Paul signature.asc Description: OpenPGP digital signature
Bug#766114: fixed in fso-deviced 0.12.0-3
On Tue, Nov 11, 2014 at 21:21:08 +, Sebastian Reichel wrote: fso-deviced (0.12.0-3) unstable; urgency=low . * Provide systemd service file * Build without -fstack-protector-strong, since it breaks the binary if build with -O2 (Closes: #766114) Hi Sebastian, the dh-systemd addition is not appropriate for jessie at this time. Could we please have the RC bugfix without the unrelated change? Thanks, Julien signature.asc Description: Digital signature
Bug#767774: dpkg: File descriptor 20 (/dev/pts/2) leaked on vgs invocation
I'm not sure I understood the state of this bug report. I'm seeing the same issue and can reproduce the behaviour shown by Niechta. This is a plain Jessie install, so apt is 1.0.9.3; not the experimental one. Do you consider the bug fixed in 1.1 and we wait until it trickles down into Jessie, or shall we set up a VM with mixed distributions to verify something? Regards, - lars. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#769070: Please close
This bug was due to a configuration error, missing a file in /etc/ld.so.conf.d -- Joel Roth -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#767370: does not start debconf, displays debconf commands and waits for input
On Thu, November 13, 2014 22:49, Thomas Liske wrote: tag 767370 upstream,fixed-upstream thanks Hi Thijs, needrestart did not find any kernel images which triggers this special bug. There was a divison by zero triggered by calculating the progressbar length. needrestart did not die since the linux specific stuff was running in an eval block. needrestart was not started in verbose mode so it does not report the error message (divsion by zero) of the eval call. While dieing in the eval block the stdout/stdin fd's were left screwed up... resulting in the debconf commands on the tty. In verbose mode the bug was not triggered since verbose mode disables the progressbar stuff. Thanks. Good that it was found. This is a Xen domU which indeed does not have any linux-* packages installed since it runs the host kernel. Can we have a targeted fix for this in unstable that fits the jessie unfreeze policy? Cheers, Thijs -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#769129: unblock: busybox/1:1.22.0-10
14.11.2014 12:42, Julien Cristau wrote:
FWIW I don't believe build-conflicts on libc achieve anything, so I'm
unhappy with -13.
I'm not happy with it either, but why do you say it does not achieve
anything? Why do you say so, is this control field ignored?
At any rate I changed that to build-depend on libc-dev-bin (2.19-13 | 2.19).
Can you say something about the FTBFS on hurd-i386 with the new test of
getpwnam() (not)working, as seen in the buildd logs? It sigsegvs on the
following one-line program:
int main(void) { return getpwnam(root) ? 0 : 1; }
cc -static test.c
Should I do anything with it? The same happens on exodar.debian.net too
(hurd-i386 porterbox) -- this small program segfaults there.
I'd like to address this prob before uploading -14 :)
Thanks,
/mjt
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#768816: fwbuilder crashes in libqtgui
tags 768816 unreproducible thanks Hello, Could you provide the backtrace? I cannot reproduce this issue on amd64 thanks S -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#769521: sosreport: Starting with v3.2, archives are created with read permissions for everyone
Package: sosreport Version: 3.2-1 Severity: grave Tags: security Justification: user security hole Dear Maintainer, sosreport 3.2 now creates the tar archive in /tmp with group and world readable. -- System Information: Debian Release: jessie/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 3.16-2-amd64 (SMP w/2 CPU cores) Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages sosreport depends on: ii python3-six 1.8.0-1 pn python3:any none sosreport recommends no packages. sosreport suggests no packages. -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#769520: dpkg-dev: debuild clean fails to first apply patches to source in quilt 3.0 format
Package: dpkg-dev Version: 1.17.21 Severity: wishlist Dear Maintainer, NOTE: This is being run inside a jessie chroot on a wheezy system. The subject line says it all. I noticed today that if the patches in debian/patches are not applied, then debuild clean does not apply them, and if a patch is required to run clean successfully, then clean fails. Included is the clean section of debian/rules for my example package, and also the output of running 'debuild clean' with and without patches applied. I think that debuild clean (or to be precise, the underlying dpkg-buildpackage) command should apply the patches before running any command, and presumably unapply it afterwards. I don't see a downside to this. Regards, Faheem Mitha ### section of debian/rules dealing with clean ### override_dh_auto_clean: find . -name *.pyc -delete find . -name symbols_scraped_inc.h -delete find . -name _symbolTableAfterBuild.txt -delete rm -rf debian/build rm -rf src/lisp/build rm -f src/core/a rm -f src/core/b rm -f src/main/taa.sh rm -f src/main/clasp_gc.ccBackup rm -f src/main/clasp_gc.telemetry.cc rm -f bin/config.log rm -f boost_build_v2/b2 rm -f boost_build_v2/engine/bin.macosxx86_64/b2 rm -f boost_build_v2/bin/config.log rm -f boost_build_v2/bjam rm -f boost_build_v2/bootstrap.log rm -f boost_build_v2/engine/bin.linuxx86_64/b2 rm -f boost_build_v2/engine/bin.linuxx86_64/bjam rm -f boost_build_v2/engine/bootstrap/jam0 rm -f src/core/_symbolTableAfterBuild.txt rm -f src/core/registerClasses.log rm -f src/core/symbols_scraped_inc.h rm -f src/llvmo/_symbolTableAfterBuild.txt rm -f src/llvmo/symbols_scraped_inc.h rm -f src/mpip/bin/boehm/clang-linux-3.6.0/release/link-static/mpip_scrape_flag.h rm -f src/main/image_test_prepass.bc rm -f src/asttooling/registerClasses.log rm -f src/cffi/registerClasses.log rm -f src/clbind/registerClasses.log rm -f src/gctools/registerClasses.log rm -f src/llvmo/registerClasses.log rm -f src/serveEvent/registerClasses.log rm -f src/sockets/registerClasses.log make clean ### Just running debuild clean (jessiechroot)faheem@orwell:/usr/local/src/clasp-llvm/clasp-llvm-0.1$ debuild clean dh clean dh_testdir debian/rules override_dh_auto_clean make[1]: Entering directory '/usr/local/src/clasp-llvm/clasp-llvm-0.1' find . -name *.pyc -delete find . -name symbols_scraped_inc.h -delete find . -name _symbolTableAfterBuild.txt -delete rm -rf debian/build rm -rf src/lisp/build rm -f src/core/a rm -f src/core/b rm -f src/main/taa.sh rm -f src/main/clasp_gc.ccBackup rm -f src/main/clasp_gc.telemetry.cc rm -f bin/config.log rm -f boost_build_v2/b2 rm -f boost_build_v2/engine/bin.macosxx86_64/b2 rm -f boost_build_v2/bin/config.log rm -f boost_build_v2/bjam rm -f boost_build_v2/bootstrap.log rm -f boost_build_v2/engine/bin.linuxx86_64/b2 rm -f boost_build_v2/engine/bin.linuxx86_64/bjam rm -f boost_build_v2/engine/bootstrap/jam0 rm -f src/core/_symbolTableAfterBuild.txt rm -f src/core/registerClasses.log rm -f src/core/symbols_scraped_inc.h rm -f src/llvmo/_symbolTableAfterBuild.txt rm -f src/llvmo/symbols_scraped_inc.h rm -f src/mpip/bin/boehm/clang-linux-3.6.0/release/link-static/mpip_scrape_flag.h rm -f src/main/image_test_prepass.bc rm -f src/asttooling/registerClasses.log rm -f src/cffi/registerClasses.log rm -f src/clbind/registerClasses.log rm -f src/gctools/registerClasses.log rm -f src/llvmo/registerClasses.log rm -f src/serveEvent/registerClasses.log rm -f src/sockets/registerClasses.log make clean make[2]: Entering directory '/usr/local/src/clasp-llvm/clasp-llvm-0.1' makefile:1: local.config: No such file or directory make[2]: *** No rule to make target 'local.config'. Stop. make[2]: Leaving directory '/usr/local/src/clasp-llvm/clasp-llvm-0.1' debian/rules:14: recipe for target 'override_dh_auto_clean' failed make[1]: *** [override_dh_auto_clean] Error 2 make[1]: Leaving directory '/usr/local/src/clasp-llvm/clasp-llvm-0.1' debian/rules:11: recipe for target 'clean' failed make: *** [clean] Error 2 debuild: fatal error at line 1346: couldn't exec fakeroot debian/rules: ## ## Applying patches first, then running debuild clean ## (jessiechroot)faheem@orwell:/usr/local/src/clasp-llvm/clasp-llvm-0.1$
Bug#769490: patch
Hi Thanks. If you want to NMU you are more than welcome to do so. / Ola Inguza Technology AB Sent from a phone Den 14 nov 2014 01:30 skrev dann frazier da...@debian.org: tags 769490 + patch thanks
Bug#769129: unblock: busybox/1:1.22.0-10
On Fri, Nov 14, 2014 at 13:02:04 +0300, Michael Tokarev wrote:
14.11.2014 12:42, Julien Cristau wrote:
FWIW I don't believe build-conflicts on libc achieve anything, so I'm
unhappy with -13.
I'm not happy with it either, but why do you say it does not achieve
anything? Why do you say so, is this control field ignored?
Its only effect is to get that package removed if it's installed.
Somehow removing libc doesn't seem like a good idea.
At any rate I changed that to build-depend on libc-dev-bin (2.19-13 |
2.19).
Can you say something about the FTBFS on hurd-i386 with the new test of
getpwnam() (not)working, as seen in the buildd logs? It sigsegvs on the
following one-line program:
int main(void) { return getpwnam(root) ? 0 : 1; }
cc -static test.c
No, I can't.
Cheers,
Julien
signature.asc
Description: Digital signature
Bug#769510: sugar-moon-activity: not installable
Control: severity -1 important Lucas Nussbaum lu...@lucas-nussbaum.net (2014-11-14): While testing the installation of all packages in sid, I ran into the following problem: Reading package lists... Building dependency tree... Reading state information... Starting pkgProblemResolver with broken count: 2 Starting 2 pkgProblemResolver with broken count: 2 Investigating (0) sugar-moon-activity [ amd64 ] none - 11-1.1 ( x11 ) Broken sugar-moon-activity:amd64 Depends on python-sugar-0.86 [ amd64 ] none ( none ) Broken sugar-moon-activity:amd64 Depends on python-sugar-0.88 [ amd64 ] none - 0.88.0-4 ( python ) Considering python-sugar-0.88:amd64 2 as a solution to sugar-moon-activity:amd64 Re-Instated python-sugar-0.88:amd64 Broken sugar-moon-activity:amd64 Depends on python-sugar-toolkit-0.86 [ amd64 ] none ( none ) Broken sugar-moon-activity:amd64 Depends on python-sugar-toolkit-0.88 [ amd64 ] none - 0.88.1-4 ( python ) Considering python-sugar-toolkit-0.88:amd64 3 as a solution to sugar-moon-activity:amd64 Re-Instated python-sugar-toolkit-0.88:amd64 Investigating (0) python-sugar-0.98 [ amd64 ] none - 0.98.0-1 ( python ) Broken python-sugar-0.98:amd64 Conflicts on python-sugar [ amd64 ] none ( none ) Conflicts//Breaks against version 0.96.0-1 for python-sugar-0.96 but that is not InstVer, ignoring Considering python-sugar-0.88:amd64 2 as a solution to python-sugar-0.98:amd64 11 Added python-sugar-0.88:amd64 to the remove list Conflicts//Breaks against version 0.84.2-4 for python-sugar-0.84 but that is not InstVer, ignoring Fixing python-sugar-0.98:amd64 via keep of python-sugar-0.88:amd64 Investigating (0) python-sugar-toolkit-0.98 [ amd64 ] none - 0.98.1-1 ( python ) Broken python-sugar-toolkit-0.98:amd64 Conflicts on python-sugar-toolkit [ amd64 ] none ( none ) Conflicts//Breaks against version 0.96.3-1 for python-sugar-toolkit-0.96 but that is not InstVer, ignoring Considering python-sugar-toolkit-0.88:amd64 3 as a solution to python-sugar-toolkit-0.98:amd64 5 Added python-sugar-toolkit-0.88:amd64 to the remove list Conflicts//Breaks against version 0.84.17-1 for python-sugar-toolkit-0.84 but that is not InstVer, ignoring Fixing python-sugar-toolkit-0.98:amd64 via keep of python-sugar-toolkit-0.88:amd64 Investigating (0) sugar-presence-service-0.88 [ amd64 ] none - 0.88.0-3.1 ( x11 ) Broken sugar-presence-service-0.88:amd64 Depends on python-sugar-toolkit-0.88 [ amd64 ] none - 0.88.1-4 ( python ) Considering python-sugar-toolkit-0.88:amd64 3 as a solution to sugar-presence-service-0.88:amd64 -1 Holding Back sugar-presence-service-0.88:amd64 rather than change python-sugar-toolkit-0.88:amd64 Investigating (1) sugar-moon-activity [ amd64 ] none - 11-1.1 ( x11 ) Broken sugar-moon-activity:amd64 Depends on python-sugar-0.86 [ amd64 ] none ( none ) Broken sugar-moon-activity:amd64 Depends on python-sugar-0.88 [ amd64 ] none - 0.88.0-4 ( python ) Considering python-sugar-0.88:amd64 2 as a solution to sugar-moon-activity:amd64 Broken sugar-moon-activity:amd64 Depends on python-sugar-toolkit-0.86 [ amd64 ] none ( none ) Broken sugar-moon-activity:amd64 Depends on python-sugar-toolkit-0.88 [ amd64 ] none - 0.88.1-4 ( python ) Considering python-sugar-toolkit-0.88:amd64 3 as a solution to sugar-moon-activity:amd64 Done Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming. The following information may help to resolve the situation: The following packages have unmet dependencies: sugar-moon-activity : Depends: python-sugar-0.86 but it is not installable or python-sugar-0.88 but it is not going to be installed Depends: python-sugar-toolkit-0.86 but it is not installable or python-sugar-toolkit-0.88 but it is not going to be installed E: Unable to correct problems, you have held broken packages. I can reproduce this in testing: | # apt-get install sugar-moon-activity … | The following packages have unmet dependencies: | sugar-moon-activity : Depends: python-sugar-0.86 but it is not installable or | python-sugar-0.88 but it is not going to be installed |Depends: python-sugar-toolkit-0.86 but it is not installable or | python-sugar-toolkit-0.88 but it is not going to be installed | E: Unable to correct problems, you have held broken packages. but specifying python-sugar-0.88 and python-sugar-toolkit-0.88 on the apt-get install command line makes apt find a solution: | # apt-get install python-sugar-0.88 python-sugar-toolkit-0.88 sugar-moon-activity … | 0 upgraded, 410 newly installed, 0 to remove and 0 not
Bug#769069: systemd: Failed to start Login Service
Unfortunately I don't see a smoking gun in your log. It looks as though the system might have been having performance issues in general: On 13/11/14 23:36, Paul Menzel wrote: Nov 11 07:45:44 asrock-e350m1 systemd[1]: Looping too fast. Throttling execution a little. which might have contributed to timeouts, possibly? Nov 11 07:45:33 asrock-e350m1 systemd-remount-fs[385]: mount: /usr not mounted or bad option Nov 11 07:45:33 asrock-e350m1 systemd-remount-fs[385]: In some cases useful info is found in syslog - try Nov 11 07:45:33 asrock-e350m1 systemd-remount-fs[385]: dmesg | tail or so. I don't know whether this is related but it doesn't look great. Is this a known problem that you have subsequently fixed? Nov 11 07:46:16 asrock-e350m1 NetworkManager[942]: info caught signal 15, shutting down normally. Nov 11 07:46:16 asrock-e350m1 avahi-daemon[929]: Got SIGTERM, quitting. ... Nov 11 07:46:52 asrock-e350m1 NetworkManager[942]: info startup complete Nov 11 07:46:52 asrock-e350m1 NetworkManager[942]: info exiting (success) Any idea why these might have happened? They both use libdbus, so getting disconnected from D-Bus with exit-on-disconnect enabled would cause an _exit(1) rather than the raise(SIGTERM) you'd get from GDBus. It looks vaguely as though *everything* on the system bus might have been failing to connect to it? Did you / do you have any unusual systemd or dbus configuration in use? If you can't reproduce this, then I don't think we'll be able to work out what is going on from that log, sorry. S -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#769490: patch
Hi Dann Sorry. I thought this was a fix for the problem you reported on tightvncserver. You are welcome to NMU, but only if you have verified that it does not crash at start first. :-) // Ola On Fri, Nov 14, 2014 at 11:12 AM, Ola Lundqvist o...@inguza.com wrote: Hi Thanks. If you want to NMU you are more than welcome to do so. / Ola Inguza Technology AB Sent from a phone Den 14 nov 2014 01:30 skrev dann frazier da...@debian.org: tags 769490 + patch thanks -- --- Inguza Technology AB --- MSc in Information Technology / o...@inguza.comAnnebergsslingan 37\ | o...@debian.org 654 65 KARLSTAD| | http://inguza.com/Mobile: +46 (0)70-332 1551 | \ gpg/f.p.: 7090 A92B 18FE 7994 0C36 4FE4 18A1 B1CF 0FE5 3DD9 / ---
Bug#769522: mirror submission for mirror.datarnd.net
Package: mirrors Severity: wishlist Submission-Type: new Site: mirror.datarnd.net Aliases: mirror.datarnd.net Type: leaf Archive-architecture: ALL amd64 armel armhf hurd-i386 i386 kfreebsd-amd64 kfreebsd-i386 mips mipsel powerpc s390x sparc Archive-http: /debian/ Backports-http: /debian-backports/ CDImage-http: /debian-cd/ IPv6: yes Archive-upstream: ftp.icm.edu.pl Backports-upstream: ftp.icm.edu.pl CDImage-upstream: ftp.icm.edu.pl Updates: four Maintainer: https://globalnetwork.pl n...@datarnd.net Country: PL Poland Location: Poland Sponsor: DATA RnD Sp. z o.o. http://datarnd.com -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#769129: unblock: busybox/1:1.22.0-10
14.11.2014 13:12, Julien Cristau wrote: On Fri, Nov 14, 2014 at 13:02:04 +0300, Michael Tokarev wrote: 14.11.2014 12:42, Julien Cristau wrote: FWIW I don't believe build-conflicts on libc achieve anything, so I'm unhappy with -13. I'm not happy with it either, but why do you say it does not achieve anything? Why do you say so, is this control field ignored? Its only effect is to get that package removed if it's installed. Somehow removing libc doesn't seem like a good idea. Well, so it is clear that building will not succeed if only old glibc is installed. Note the amd64 build log for example: current build-conflict causes the buildd to upgrade libc6, because it has 2.12-11 installed which conflicts with building busybox, so the condition is actually working. https://buildd.debian.org/status/fetch.php?pkg=busyboxarch=amd64ver=1%3A1.22.0-13stamp=1415831665 But it is ugly at least, I agree with that. Thanks, /mjt -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#762462: glassfish server support
Hi, Last september you said [1] you would drop the glassfish-appserv package in an upload. Is this action still on your todo-list ? [1]: https://lists.debian.org/debian-lts/2014/09/msg00036.html Regards, -- Jonathan Dupart -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#769499: syslog-ng-core fails to enable systemd service unit
On 14/11/14 03:50, Sam Hartman wrote: # Automatically added by dh_installinit if [ -x /etc/init.d/syslog-ng ]; then update-rc.d syslog-ng defaults 10 90 /dev/null || exit $? fi # End automatically added section That should be enough to enable syslog-ng.service, because Debian's update-rc.d knows that /etc/init.d/foo in sysvinit corresponds to foo.service in systemd, and keeps their enabledness states in sync. If syslog-ng needs other units to be enabled, *those* might need to be enabled explicitly, but I don't see any others in the source package? S -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#769524: astyle: astyle reports unchanged but adds a newline to the output
Package: astyle
Version: 2.04-1
Severity: normal
Dear Maintainer,
With astyle 2.04:
$ astyle test.h
Unchanged /tmp/astyle-test/test.h
$ astyle test.h test.h.out 2 /dev/null
$ diff -s test.h test.h.out
11a12
Compared to astyle 2.03:
$ astyle test.h
Unchanged /tmp/astyle-test/test.h
$ astyle test.h test.h.out 2 /dev/null
$ diff -s test.h test.h.out
Files test.h and test.h.out are identical
test.h
=
#ifndef D_Test_H
#define D_Test_H
class Test : IDevice
{
public:
explicit Test();
virtual ~Test();
};
#endif // D_Test_H
astyle.rc
mode=c
style=k/r
indent=spaces=4
indent-classes
indent-switches
indent-preprocessor
convert-tabs
lineend=linux
-- System Information:
Debian Release: jessie/sid
APT prefers unstable
APT policy: (500, 'unstable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 3.17-2.slh.7-aptosid-amd64 (SMP w/8 CPU cores; PREEMPT)
Locale: LANG=en_GB.utf8, LC_CTYPE=en_GB.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Versions of packages astyle depends on:
ii libc6 2.19-13
ii libstdc++6 4.9.2-1
astyle recommends no packages.
astyle suggests no packages.
-- no debconf information
~
This email message is for the sole use of the intended recipient(s) and may
contain confidential and privileged information of Cameron and its Operating
Divisions. Any unauthorized use or disclosure is prohibited. If you are not the
intended recipient, please contact the sender by reply email and delete and
destroy all copies of the original message inclusive of any attachments.
~
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#769523: owfs-common: tries to access nonexisting /etc/modprobe/libow-*-*.conf
Package: owfs-common Version: 2.9p8-5 Severity: normal While upgrading, I got these messages: Vorbereitung zum Entpacken von .../owfs-common_2.9p8-5_all.deb ... ls: Zugriff auf /etc/modprobe.d/libow-*-*.conf nicht möglich: Datei oder Verzeichnis nicht gefunden Entpacken von owfs-common (2.9p8-5) über (2.9p8-4) ... (meaning: could not access /etc/modprobe.d/libow-*-*.conf, no such file or directory) In /etc/modprobe.d, there is only one 'owfs-common.conf', no libow-*.conf. If the nonexistance of any libow-*.conf file is OK, then I'd expect the upgrade scripts to not print any error messages and should silently cope with this situation. -- System Information: Debian Release: jessie/sid APT prefers testing-updates APT policy: (500, 'testing-updates'), (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 3.14-2-amd64 (SMP w/2 CPU cores) Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages owfs-common depends on: ii ucf 3.0030 owfs-common recommends no packages. owfs-common suggests no packages. -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#769525: nwchem: FTBFS on arm64
Source: nwchem Version: 6.5+r26243-3 It failed to build on arm64: http://buildd.debian.org/status/package.php?p=nwchemsuite=sid The error was: gfortran -c -m64 -ffast-math -Warray-bounds -fdefault-integer-8 -O2 -g -fno-aggressive-loop-optimizations -I. -I/«BUILDDIR»/nwchem-6.5+r26243/src/include -I/«BUILDDIR»/nwchem-6.5+r26243/src/tools/install/include -DLINUX -DGCC4 -DGCC46 -DGFORTRAN -DGFORTRAN -DCHKUNDFLW -DGCC4 -DGCC46 -DEXT_INT -DLINUX -DLINUX64 -DPARALLEL_DIAG basis.F gfortran: error: unrecognized command line option '-m64' At line 1761 of src/config/makefile.h there is code to avoid setting -m64 for arm64: ifeq ($(_CPU),aarch64) DONTHAVEM64OPT=Y endif However, I don't think _CPU has been set at this point. A simple fix is to add this (which also appears elsewhere in the file) immediately before the test: _CPU = $(shell uname -m ) -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#769526: xlshlt: xslhlt should use configuration file provided by package by default
Package: xlshlt
Version: xslhlt
Severity: minor
Tags: patch
Dear Maintainer,
xslhlt package provides the standard configuration file
/usr/share/xslthl/highlighters/xslthl-config.xml within. But unfortunately I
always have to set filename explicitly by java command-line option
«-Dxslthl.config» because xslhlt searches this file in a current directory by
default.
This behaviour is acceptable for general jar package, but in Debian system it
is better to use system-wide configuration file (/usr/share/xslthl/highlighters
/xslthl-config.xml) by default.
This way eliminates inconvenient point with setting command-line argument for
Java applications.
-- System Information:
Debian Release: jessie/sid
APT prefers testing
APT policy: (500, 'testing'), (500, 'stable'), (102, 'unstable'), (101,
'experimental')
Architecture: amd64 (x86_64)
Kernel: Linux 3.16-3-amd64 (SMP w/4 CPU cores)
Locale: LANG=ru_RU.UTF-8, LC_CTYPE=ru_RU.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash
--- a/src/main/java/net/sf/xslthl/Config.java
+++ b/src/main/java/net/sf/xslthl/Config.java
@@ -408,9 +408,11 @@
logger.config(No config file specified, falling back to default behavior);
if (System.getProperty(CONFIG_PROPERTY) != null) {
configFilename = System.getProperty(CONFIG_PROPERTY);
-} else {
+} else if (new File(xslthl-config.xml).isFile()) {
configFilename = xslthl-config.xml;
-}
+} else {
+configFilename = /usr/share/xslthl/highlighters/xslthl-config.xml;
+}
}
logger.info(String.format(Loading Xslthl configuration from %s,
Bug#769527: racoon generates a wrong policy for transport mode over NAT.
Package: racoon Version: 1:0.8.0-14 Severity: normal Dear Maintainer, I tried to configure racoon with 'generate_polity on' for transport mode over NAT, but racoon generated a policy with a peer address behind NAT and transport mode did not work at all. Tunnel mode was OK so I changed the configuration to use tunnel mode just for 1-to-1 IPSec communication. I do not know if IPSec transport mode should work with NAT-Traversal, but the policy generation is still broken. If it cannot generate a working policy, it should fail in negotiation without generating a wrong one. -- System Information: Debian Release: 7.7 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable') Architecture: i386 (i686) Kernel: Linux 3.2.0-4-686-pae (SMP w/1 CPU core) Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968) Shell: /bin/sh linked to /bin/dash Versions of packages racoon depends on: ii adduser3.113+nmu3 ii debconf [debconf-2.0] 1.5.49 ii ipsec-tools1:0.8.0-14 ii libc6 2.13-38+deb7u6 ii libcomerr2 1.42.5-1.1 ii libgssapi-krb5-2 1.10.1+dfsg-5+deb7u2 ii libk5crypto3 1.10.1+dfsg-5+deb7u2 ii libkrb5-3 1.10.1+dfsg-5+deb7u2 ii libldap-2.4-2 2.4.31-1+nmu2 ii libpam0g 1.1.3-7.1 ii libssl1.0.01.0.1e-2+deb7u13 ii perl 5.14.2-21+deb7u2 racoon recommends no packages. racoon suggests no packages. -- Configuration Files: /etc/racoon/psk.txt [Errno 13] Permission denied: u'/etc/racoon/psk.txt' /etc/racoon/racoon.conf changed [not included] -- debconf information: * racoon/config_mode: direct -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#768519: nautilus does not start from dash when it handles the desktop
Control: tags 768519 + fixed-upstream Control: forwarded 768519 https://bugzilla.gnome.org/show_bug.cgi?id=738280 On 11/11/14 14:33, Andreas Henriksson wrote: I'm pretty confident the reason nautilus doesn't start when handling the desktop is because it's already running. I think this may have been fixed in Nautilus 3.14.1 by commit 2780ce8790fc application: Restore --new-window functionality which goes on to say: In case of no further arguments, open home folder. Commit 4e192481 application: minimal port to handle_local_options() removed this, presumably accidentally. It makes clicking the Files from favorites do nothing if Nautilus is already running (and it always is running in classic mode as it handles desktop). https://bugzilla.gnome.org/show_bug.cgi?id=738280 Regards, S -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#767213: flexpart: FTBFS on ppc64el with relocation truncated to fit:, R_PPC64_TOC16_HA against `.bss'
That patch, flexpart_mcmodel.patch, would fix the FTBFS on arm64, too. (So, if you're thinking of making it conditional on the architecture in some way, test for arm64 as well as ppc64el.) -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#768220: dupe of #722665?
* Timo Aaltonen: This sounds more like a dupe of #722665 where the fault is that libjackson-json-java never should've had the symlink called jackson-core-java... Which package should provide the versionless .jar file? Is the versionless .jar file needed at all? Was any of libjackson-json-java's reverse dependencies[1] broken when the versionless .jar was removed from the package? epubcheck seems to be fine because it has /share/java/jackson-core-asl.jar, /usr/share/java/jackson-mapper-asl.jar in its classpath. Would any of libjackson2-core-java's reverse dependencies[2] break if we removed the versionless .jar from the package? At least mediathekview would break. I think things should be left as they are, only proper Breaks/Replaces as suggested by the submitter should be added. I will upload a fixed package tonight. Renaming the versionless jar symlink in -core would break other software (dogtag-pki for instance). dogtag-pki is a curious case: pki-server depends on parts of both Jackson 1.x and 2.x. Is this actually correct? Cheers, -Hilko [1] libspring-web-java libresteasy-java libspring-web-java libjasperreports-java epubcheck pki-server [2] sikulix mediathekview libjackson2-module-jaxb-annotations-java libjackson2-jaxrs-providers-java libjackson2-dataformat-yaml libjackson2-dataformat-smile libjackson2-dataformat-cbor libjackson2-databind-java libjackson2-core-java-doc liblog4j2-java -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#769520: dpkg-dev: debuild clean fails to first apply patches to source in quilt 3.0 format
On Fri, 14 Nov 2014, Faheem Mitha wrote: The subject line says it all. I noticed today that if the patches in debian/patches are not applied, then debuild clean does not apply them, and if a patch is required to run clean successfully, then clean fails. Included is the clean section of debian/rules for my example package, and also the output of running 'debuild clean' with and without patches applied. I think that debuild clean (or to be precise, the underlying dpkg-buildpackage) command should apply the patches before running any command, and presumably unapply it afterwards. I don't see a downside to this. dpkg-buildpackage is not called when you run debuild clean. The manual page clearly indicates that it calls debian/rules target directly. And your log doesn't show any message of dpkg-buildpackage. In general, opting to call a specific target doesn't do any build preparation work. It's the same if you do dpkg-buildpackage --target=clean. I'm not sure this can be considered as a bug. It behaves as documented. Cheers, -- Raphaël Hertzog ◈ Debian Developer Support Debian LTS: http://www.freexian.com/services/debian-lts.html Learn to master Debian: http://debian-handbook.info/get/ -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#768519: nautilus does not start from dash when it handles the desktop
On 14/11/14 10:44, Simon McVittie wrote: I think this may have been fixed in Nautilus 3.14.1 by commit 2780ce8790fc It seems that commit is not sufficient, there's another one before 3.14.1 that fixes it further. S -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#769271: metamonger: FTBFS in jessie/i386: Tests failures
Control: severity -1 important Control: tag -1 moreinfo Lucas Nussbaum lu...@lucas-nussbaum.net (2014-11-12): Source: metamonger Version: 0.20141008-1 Severity: serious Tags: jessie sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20141112 qa-ftbfs Justification: FTBFS in jessie on i386 Hi, During a rebuild of all packages in jessie (in a jessie chroot, not a sid chroot), your package failed to build on i386. Relevant part (hopefully): # Looks like you failed 9 tests of 14. t/200-no-dereference.t .. Dubious, test returned 9 (wstat 2304, 0x900) Failed 9/14 subtests t/500-fix-84ee7f6b65.t .. ok Test Summary Report --- t/200-no-dereference.t(Wstat: 2304 Tests: 14 Failed: 9) Failed tests: 3, 6, 8-14 Non-zero exit status: 9 Files=19, Tests=724, 11 wallclock secs ( 0.14 usr 0.10 sys + 9.10 cusr 2.18 csys = 11.52 CPU) Result: FAIL Failed 1/19 test programs. 9/724 subtests failed. make[1]: *** [test_dynamic] Error 255 Makefile:767: recipe for target 'test_dynamic' failed The full build log is available from: http://aws-logs.debian.net/ftbfs-logs/2014/11/12/metamonger_0.20141008-1_jessie-i386.log A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! About the archive rebuild: The rebuild was done on EC2 VM instances from Amazon Web Services, using a clean, minimal and up-to-date chroot. Every failed build was retried once to eliminate random failures. I seem to be unable to reproduce this issue, either in various devel chroots or under sbuild. I tried the usual suspects, like setting HOME to a non-existing directory, or existing but not writable. Without success. Mraw, KiBi. signature.asc Description: Digital signature
Bug#769528: systemd: ifup@ services failing if no /run/network directory
Package: systemd Version: 215-5 Severity: normal If networking.service wasn't activated (due to, for instance, no symlink in /etc/init.d/networking not having start symlinks in any /etc/rc*.d/), then there is no /run/network directory created. However, systemd still instantiate and starts ifup@*.service units, which are failing due to the lack of /run/network directory. Consequence is that the system is seen as being in degraded mode. We can make ifup@ template have a Conditional Path on /run/network. Example of $ sudo systemctl status ifup@wlan0.service ● ifup@wlan0.service - ifup for wlan0 Loaded: loaded (/lib/systemd/system/ifup@.service; static) Active: failed (Result: exit-code) since ven. 2014-11-14 08:53:56 CET; 2h 53min ago Main PID: 652 (code=exited, status=1/FAILURE) nov. 14 08:53:56 tidus ifup[652]: /sbin/ifup: failed to open lockfile /run/network/.ifstate.lock: No such file or directory nov. 14 08:53:56 tidus ifup[653]: /sbin/ifup: failed to open lockfile /run/network/.ifstate.lock: No such file or directory nov. 14 08:53:56 tidus systemd[1]: ifup@wlan0.service: main process exited, code=exited, status=1/FAILURE nov. 14 08:53:56 tidus systemd[1]: ifup@wlan0.service: control process exited, code=exited status=1 nov. 14 08:53:56 tidus ifdown[664]: /sbin/ifdown: failed to open lockfile /run/network/.ifstate.lock: No such file or directory nov. 14 08:53:56 tidus systemd[1]: ifup@wlan0.service: control process exited, code=exited status=1 nov. 14 08:53:56 tidus systemd[1]: Failed to start ifup for wlan0. nov. 14 08:53:56 tidus systemd[1]: Unit ifup@wlan0.service entered failed state. -- System Information: Debian Release: jessie/sid APT prefers vivid-updates APT policy: (500, 'vivid-updates'), (500, 'vivid-security'), (500, 'vivid') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.16.0-24-generic (SMP w/4 CPU cores) Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#769529: libgazebo-dev: arch-dependent file in Multi-Arch: same package
Package: libgazebo-dev Version: 3.0.0+dfsg-3 Severity: important User: multiarch-de...@lists.alioth.debian.org Usertags: multiarch libgazebo-dev is marked as Multi-Arch: same, but the following file is architecture-dependent: /usr/include/gazebo-3.0/gazebo/test/test_config.h An example diff between i386 and amd64 is attached. -- Jakub Wilk diff -ur libgazebo-dev_3.0.0+dfsg-3_i386/usr/include/gazebo-3.0/gazebo/test/test_config.h libgazebo-dev_3.0.0+dfsg-3_amd64/usr/include/gazebo-3.0/gazebo/test/test_config.h --- libgazebo-dev_3.0.0+dfsg-3_i386/usr/include/gazebo-3.0/gazebo/test/test_config.h 2014-11-13 19:45:34.0 +0100 +++ libgazebo-dev_3.0.0+dfsg-3_amd64/usr/include/gazebo-3.0/gazebo/test/test_config.h 2014-11-13 19:48:20.0 +0100 @@ -1,6 +1,6 @@ -#define TEST_INTEGRATION_PATH /build/gazebo-7iodgn/gazebo-3.0.0+dfsg/test/integration -#define TEST_REGRESSION_PATH /build/gazebo-7iodgn/gazebo-3.0.0+dfsg/test/regression -#define TEST_UNIT_PATH /build/gazebo-7iodgn/gazebo-3.0.0+dfsg/test/unit -#define TEST_PATH /build/gazebo-7iodgn/gazebo-3.0.0+dfsg/test -#define PROJECT_SOURCE_PATH /build/gazebo-7iodgn/gazebo-3.0.0+dfsg -#define PROJECT_BINARY_PATH /build/gazebo-7iodgn/gazebo-3.0.0+dfsg/obj-i586-linux-gnu +#define TEST_INTEGRATION_PATH /build/gazebo-EIYM8G/gazebo-3.0.0+dfsg/test/integration +#define TEST_REGRESSION_PATH /build/gazebo-EIYM8G/gazebo-3.0.0+dfsg/test/regression +#define TEST_UNIT_PATH /build/gazebo-EIYM8G/gazebo-3.0.0+dfsg/test/unit +#define TEST_PATH /build/gazebo-EIYM8G/gazebo-3.0.0+dfsg/test +#define PROJECT_SOURCE_PATH /build/gazebo-EIYM8G/gazebo-3.0.0+dfsg +#define PROJECT_BINARY_PATH /build/gazebo-EIYM8G/gazebo-3.0.0+dfsg/obj-x86_64-linux-gnu
Bug#769530: racoon generates a broken policy for transport mode over NAT.
Package: racoon Version: 1:0.8.0-14 Severity: normal Dear Maintainer, *** Please consider answering these questions, where appropriate *** * What led up to the situation? * What exactly did you do (or not do) that was effective (or ineffective)? * What was the outcome of this action? * What outcome did you expect instead? *** End of the template - remove these lines *** Content-Type: text/plain; charset=us-ascii MIME-Version: 1.0 Content-Transfer-Encoding: 7bit From: kazs...@corundum.minerals.linuxfront.com To: Debian Bug Tracking System sub...@bugs.debian.org Subject: racoon generates a wrong policy for transport mode over NAT. Bcc: kazs...@corundum.minerals.linuxfront.com Package: racoon Version: 1:0.8.0-14 Severity: minor Dear Maintainer, I tried to configure racoon with 'generate_polity on' for transport mode over NAT, but racoon generated a policy with a peer address behind NAT and transport mode did not work at all. Tunnel mode was OK so I changed the configuration to use tunnel mode just for 1-to-1 IPSec communication. I do not know if IPSec transport mode should work with NAT-Traversal, but the policy generation is still broken. If it cannot generate a working policy, it should fail in negotiation without generating a broken one. -- System Information: Debian Release: 7.7 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable') Architecture: i386 (i686) Kernel: Linux 3.2.0-4-686-pae (SMP w/1 CPU core) Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968) Shell: /bin/sh linked to /bin/dash Versions of packages racoon depends on: ii adduser3.113+nmu3 ii debconf [debconf-2.0] 1.5.49 ii ipsec-tools1:0.8.0-14 ii libc6 2.13-38+deb7u6 ii libcomerr2 1.42.5-1.1 ii libgssapi-krb5-2 1.10.1+dfsg-5+deb7u2 ii libk5crypto3 1.10.1+dfsg-5+deb7u2 ii libkrb5-3 1.10.1+dfsg-5+deb7u2 ii libldap-2.4-2 2.4.31-1+nmu2 ii libpam0g 1.1.3-7.1 ii libssl1.0.01.0.1e-2+deb7u13 ii perl 5.14.2-21+deb7u2 racoon recommends no packages. racoon suggests no packages. -- Configuration Files: /etc/racoon/psk.txt [Errno 13] Permission denied: u'/etc/racoon/psk.txt' /etc/racoon/racoon.conf changed [not included] -- debconf information: * racoon/config_mode: direct -- System Information: Debian Release: 7.7 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable') Architecture: i386 (i686) Kernel: Linux 3.2.0-4-686-pae (SMP w/1 CPU core) Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968) Shell: /bin/sh linked to /bin/dash Versions of packages racoon depends on: ii adduser3.113+nmu3 ii debconf [debconf-2.0] 1.5.49 ii ipsec-tools1:0.8.0-14 ii libc6 2.13-38+deb7u6 ii libcomerr2 1.42.5-1.1 ii libgssapi-krb5-2 1.10.1+dfsg-5+deb7u2 ii libk5crypto3 1.10.1+dfsg-5+deb7u2 ii libkrb5-3 1.10.1+dfsg-5+deb7u2 ii libldap-2.4-2 2.4.31-1+nmu2 ii libpam0g 1.1.3-7.1 ii libssl1.0.01.0.1e-2+deb7u13 ii perl 5.14.2-21+deb7u2 racoon recommends no packages. racoon suggests no packages. -- Configuration Files: /etc/racoon/psk.txt [Errno 13] Permission denied: u'/etc/racoon/psk.txt' /etc/racoon/racoon.conf changed [not included] -- debconf information: * racoon/config_mode: direct -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#769531: unblock: xmlrpc-c/1.33.14-0.2
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: unblock
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Please unblock package xmlrpc-c
xmlrpc-c was uploaded yesterday (via DELAYED/2) to fix RC bug 760377
which is about missing information in d/copyright. While investigating
the issue I found a spurious license violation (the file with the
conflicting license is unused) and to prevent it from accidentely
being used, I remove it during the clean target. Also one of the
packages was missing dependencies on libraries, which are now added by
${shlibs:Depends}.
Please find the debdiff against the current version in testing attached.
unblock xmlrpc-c/1.33.14-0.2
- -- System Information:
Debian Release: 7.7
APT prefers stable
APT policy: (500, 'stable'), (99, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 3.2.0-4-amd64 (SMP w/1 CPU core)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.12 (GNU/Linux)
iQEcBAEBCAAGBQJUZeEUAAoJEJxcmesFvXUKY2oIAIzTVA41T4sJGemRSjiXbBg/
fqQ7lQuo2ze3gRfWIadJo8U/lW5DiFxbQdHdqofcuBiFu/o/usrBrCnlPD4j9Bs5
tHj1iE/ckEO/rwCiZtpQQ2qDOFelF6jGGltaw16bnUmaJK8OZIoTr8xm6BSTy6wY
C2k+A4reB3PzWNwRP9NS56/Xq68cLX4b/9c7+KmGq/vIFXnWammX9jY0XEbkNhG2
cPllrH7jyHZzf/NODe8C4/owmGPBOlQ0nbGmAbplKrjzPKlIs/phvcgPuv8ax1UA
bbjjpQvSDtph2V5tqAuRMfFuaXMuinxN43hzjf47yhXyL9HgrQKCgur1Sz8u9xE=
=oF+/
-END PGP SIGNATURE-
diff -u xmlrpc-c-1.33.14/debian/changelog xmlrpc-c-1.33.14/debian/changelog
--- xmlrpc-c-1.33.14/debian/changelog
+++ xmlrpc-c-1.33.14/debian/changelog
@@ -1,3 +1,13 @@
+xmlrpc-c (1.33.14-0.2) unstable; urgency=medium
+
+ * Non-maintainer upload.
+ * Document missing license (Closes: #760377)
+ * Clean unused code to prevent conflicting licenses
+ * Add ${shlibs:Depends} to depends of xmlrpc-api-utils to prevent
+several missing dependencies (Thanks lintian)
+
+ -- Paul Gevers elb...@debian.org Sat, 08 Nov 2014 20:53:51 +0100
+
xmlrpc-c (1.33.14-0.1) unstable; urgency=low
* Non-maintainer upload.
diff -u xmlrpc-c-1.33.14/debian/control xmlrpc-c-1.33.14/debian/control
--- xmlrpc-c-1.33.14/debian/control
+++ xmlrpc-c-1.33.14/debian/control
@@ -76,6 +76,7 @@
Architecture: any
Section: devel
Depends: ${misc:Depends},
+ ${shlibs:Depends},
libxmlrpc-c++8 (= ${binary:Version}),
libxmlrpc-core-c3 (= ${binary:Version}),
libc6-dev,
diff -u xmlrpc-c-1.33.14/debian/copyright xmlrpc-c-1.33.14/debian/copyright
--- xmlrpc-c-1.33.14/debian/copyright
+++ xmlrpc-c-1.33.14/debian/copyright
@@ -14,15 +14,23 @@
directory lib/abyss and parts of the file src/xmlrpc_abyss.c, and the
Python 1.5.2 license applies to parts of the file src/xmlrpc_base64.c.
-And as for the tools/ directory, you'll have to examine the licenses on
-your own.
+The file tools/turbocharger/mod_gzip.c is covered by the Apache license, and
+the file tools/perl_packetsocket/PacketSocket.pm is created by Bryan
+Henderson, San Jose CA who contributed it to the public domain. The files
+lib/util/getoptx.c and lib/util/getoptx.h are licensed under the GNU
+General Public License version 1 (or higher),
+Due to the above, it is our understanding (see bug 760377) that the
+resulting binaries are effectively licensed under GPL-1+.
- XML-RPC C Library License
+
+ XML-RPC C Library License (BSD-3-clause)
-
Copyright (C) 2001 by First Peer, Inc. All rights reserved.
Copyright (C) 2001 by Eric Kidd. All rights reserved.
+Copyright (C) 2002 by j...@ourexchange.net. All rights reserved.
+Copyright (C) 2005 by Steven A. Bone, sb...@pobox.com. All rights reserved.
Redistribution and use in source and binary forms, with or without
modification, are permitted provided that the following conditions
@@ -73,7 +81,7 @@
SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
- ABYSS Web Server License
+ ABYSS Web Server License (BSD-3-clause)
Copyright (C) 2000 by Moez Mahfoudh mm...@bigfoot.com. All rights reserved.
@@ -135,0 +144,81 @@
+
+
+ GNU General Public License version 1 (GPL-1+)
+ -
+
+Copyright (C) 1989 Free Software Foundation, Inc.
+
+This program is free software; you can redistribute it and/or modify
+it under the terms of the GNU General Public License as published by
+the Free Software Foundation; either version 1, or (at your option)
+any later version.
+
+This program is distributed in the hope that it will be useful,
+but WITHOUT ANY WARRANTY; without even the implied warranty of
+MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
+GNU General Public License for more details.
+
+You should have received a copy of the GNU General
Bug#769528: Git patch adding ConditionPath on /run/network
Add a ConditionPathIsDirectory on /run/network from ifup@ unit. From 1f747abf9d8351ae4174926255b9b82fccfe6ce2 Mon Sep 17 00:00:00 2001 From: Didier Roche didro...@ubuntu.com Date: Fri, 14 Nov 2014 11:55:24 +0100 Subject: [PATCH] debian/ifup@.service: add a network ConditionPath Add a ConditionPath on /run/network in case autogenerated networking.service didn't need to start and so, didn't create this directory. Starting an ifup service without this directory was resulting in the unit failing. (Closes: # 769528) --- debian/changelog | 7 +++ debian/ifup@.service | 1 + 2 files changed, 8 insertions(+) diff --git a/debian/changelog b/debian/changelog index 49d9328..4215821 100644 --- a/debian/changelog +++ b/debian/changelog @@ -1,5 +1,6 @@ systemd (215-6) UNRELEASED; urgency=medium + [ Martin Pitt ] * Cherry-pick upstream patch to fix udev crash in link_config_get(). * Cherry-pick upstream patch to fix tests in limited schroot environments. * Add d/p/Add-env-variable-for-machine-ID-path.patch: Allow specifying an @@ -22,6 +23,12 @@ systemd (215-6) UNRELEASED; urgency=medium required so that tools like systemd-rfkill can be used with SysVinit or upstart scripts, too. (LP: #1387282) + [ Didier Roche ] + * debian/ifup@.service: add a ConditionPath on /run/network in case +autogenerated networking.service didn't need to start (and thus, didn't +create that directory). Starting an ifup service without this directory was +resulting in the unit failing. (Closes: # 769528) + -- Martin Pitt mp...@debian.org Sun, 12 Oct 2014 17:29:00 +0200 systemd (215-5) unstable; urgency=medium diff --git a/debian/ifup@.service b/debian/ifup@.service index c7b2736..7198314 100644 --- a/debian/ifup@.service +++ b/debian/ifup@.service @@ -3,6 +3,7 @@ Description=ifup for %I After=local-fs.target networking.service Before=network.target BindsTo=sys-subsystem-net-devices-%i.device +ConditionPathIsDirectory=/run/network DefaultDependencies=no [Service] -- 2.1.3
Bug#769203: unblock: angular.js/1.2.26-1
Control: tag -1 moreinfo On Wed, Nov 12, 2014 at 07:15:46 +0100, Laszlo Boszormenyi (GCS) wrote: Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: unblock Hi Release Team, Please unblock angular.js and let it migrate to Jessie. It's more than a month (34 days) ago in Sid. Didn't migrate in time as Thomas Goirand blocked it with too tight dependency in python-xstatic-angular. He eased that, but the freeze started then. The package doesn't have any bugs. 826 files changed, 86403 insertions(+), 13105 deletions(-) That doesn't sound reasonable at this stage. Cheers, Julien signature.asc Description: Digital signature
Bug#769204: unblock: d3/3.4.13-2
Control: tag -1 moreinfo On Wed, Nov 12, 2014 at 07:15:57 +0100, Laszlo Boszormenyi (GCS) wrote: Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: unblock Hi Release Team, Please unblock D3, which fixes RC bug #768719 [1], missing build dependency in Jessie. I just removed it as it's needed for self-test only and was not working anyway. The debdiff is against the Sid version. It couldn't migrate since 23 days due to too tight dependency in python-xstatic-d3 . Thomas eased that since then even if it needs an unblock as well. Debdiffs attached. I don't think this is suitable, sorry. My preferred solution right now is to remove d3/3.4.11-1 flower/0.7.0+dfsg-1 python-mne/0.8.4+dfsg-1 python-mpld3/0.3git+20140910dfsg-1 python-xstatic-d3/3.4.11-1 rickshaw/1.5.0.dfsg-1 ruby-sidekiq/3.2.6~dfsg-1 ntopng/1.2.1+dfsg1-1.1 python-xstatic-rickshaw/1.5.0.2-2. Cheers, Julien signature.asc Description: Digital signature
Bug#769533: rmdir: failed to remove ‘/etc/xdg/midori/extensions/libadblock.so’: No such file or directory
Package: midori Version: 0.4.3+dfsg-0.2 Severity: minor Setting up midori (0.4.3+dfsg-0.2) ... rmdir: failed to remove ‘/etc/xdg/midori/extensions/libadblock.so’: No such file or directory Therefore should first test first. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#769532: vpxenc manpage
Package: vpx-tools Version: 1.3.0-3 I have written this vpcenc manpage: https://gist.github.com/darealshinji/4ca99394f2c7f151a5c5 You can add it to your package if you want. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#769534: phabricator: fails to install: Usage Exception: Specify a value to set the key 'mysql.user' to.
Package: phabricator Version: 0~git20141101-1 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed your package failed to install. As per definition of the release team this makes the package too buggy for a release, thus the severity. From the attached log (scroll to the bottom...): Selecting previously unselected package phabricator. (Reading database ... 12507 files and directories currently installed.) Preparing to unpack .../phabricator_0~git20141101-1_all.deb ... Unpacking phabricator (0~git20141101-1) ... Setting up phabricator (0~git20141101-1) ... Creating config file /etc/apache2/conf-available/phabricator.conf with new version Creating config file /etc/lighttpd/conf-available/20-phabricator.conf with new version Creating config file /etc/nginx/sites-available/phabricator.conf with new version adduser: Warning: The home directory `/var/lib/phabricator' does not belong to the user you are currently creating. Set 'mysql.host' in local configuration. Usage Exception: Specify a value to set the key 'mysql.user' to. dpkg: error processing package phabricator (--configure): subprocess installed post-installation script returned error exit status 77 Errors were encountered while processing: phabricator cheers, Andreas phabricator_0~git20141101-1.log.gz Description: application/gzip
Bug#767774: dpkg: File descriptor 20 (/dev/pts/2) leaked on vgs invocation
On Fri, Nov 14, 2014 at 10:58:02AM +0100, Lars Hanke wrote: I'm not sure I understood the state of this bug report. The bugreport wasn't closed, so there exists no version which fixed the bug or otherwise this version would have closed it (or someone would have closed it with a version tag in case the version already released). I'm seeing the same issue and can reproduce the behaviour shown by Niechta. This is a plain Jessie install, so apt is 1.0.9.3; not the experimental one. No, Guillem was just using a new (unrelated) feature to show this bug. He could equally well setup an archive containing his testpackage, update with this archive configured and finally install the package. His instructions are just a 'compressed' way of reproducing this bug. It might not be totally clear from his message alone, but in context: He is the dpkg maintainer, who reassigned a bug initially reported against dpkg to apt with instructions on how to reproduce it with apt, but not with dpkg to show that the reassign is in fact correct. Do you consider the bug fixed in 1.1 and we wait until it trickles down into Jessie, or shall we set up a VM with mixed distributions to verify something? Well, nothing tickles down to Jessie anymore as it is frozen. Assuming a fix materializes now, such a fix would need to be backported to the version currently in jessie and you would need to convience the release team to accept this change. For me: While this looks like a bug we should fix, it isn't a bug we would need to fix to release jessie as you can survive it. I at least value other bugs far higher on the should-be-fixed-for-jessie scale which are hard enough to find time and energy to fix and advertise properly already. So, tl;dr: bug status: open, no owner, no patch, no timeline. aka: Ready to be picked up by someone willing to work on it. Best regards David Kalnischkies signature.asc Description: Digital signature
Bug#741064: upstream fix
It appears that the upstream fix is https://www.kernel.org/pub/linux/daemons/autofs/v5/patches-5.0.9/autofs-5.0.8-fix-ipv6-libtirpc-getport-proto-not-set.patch and is in 5.0.9. BTW, could you please increase the severity of the bug? Regards, Pavel -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#769271: metamonger: FTBFS in jessie/i386: Tests failures
Lucas, can you reproduce? If yes, can I get a full log and/or interactive access? Are you doing anything special with permissions, eatmydata, or the like? Thanks to both of you, Richard Sent by mobile; excuse my brevity.
Bug#741064: upstream fix
Control: severity -1 important 14.11.2014 14:20, Pavel Cahyna wrote: It appears that the upstream fix is https://www.kernel.org/pub/linux/daemons/autofs/v5/patches-5.0.9/autofs-5.0.8-fix-ipv6-libtirpc-getport-proto-not-set.patch Wow, a bug fixed upstream in autofs. Quite a rare case. and is in 5.0.9. BTW, could you please increase the severity of the bug? Sure, why not -- is `important' enough? I'd like to make it RC so autofs is removed from debian finally, as it is just too broken. /mjt -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#762462: glassfish server support
Le 14/11/2014 11:15, Jonathan Dupart a écrit : Is this action still on your todo-list ? Hi Jonathan, Yes I'll do it. Emmanuel Bourg -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#769448: [Pkg-zsh-devel] Bug#769450: zsh-static unsets $USERNAME
Hi, On 2014-11-14 09:47:48 +0100, Axel Beckert wrote: In https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=354631#27 Clint writes: [...] the problem is that user/group lookups are disabled in the -static build because glibc's NSS ABI is unstable and static binaries still need to load NSS modules dynamically. Isn't it possible to get this NSS code in the static binary instead of having to load modules dynamically? If we re-enable lookups, then zsh-static will segfault on any major libc upgrade. I don't know what the best solution here is. That IMHO explains well why a statically complied binary still needs dynamically linked libraries -- which may change their ABI _with_ an SONAME bump, so no bug in libc6, So, if the libc6 version is incorrect, the module cannot be found because of the SONAME bump. So, one should get a clean error with a meaningful error message instead of a segfault in such a case. but zsh-static should likely depend on libc6 (= $current_glibc_upstream_version), libc6 ( $next_glibc_upstream_version) if we remove STATICFLAGS += --disable-dynamic-nss from debian/rules. IMHO there are two better solutions, but this would need some change in the glibc packaging: 1. The dynamic modules are provided by a separate package, whose name depends on the ABI (which is typically done for usual libraries, where different versions are co-installable). The advantage is that libc6 and zsh-static upgrades could be done independently for the user (very useful in case of blocking bugs). 2. If this is not possible, glibc could provide a virtual package associated with the ABI, so that zsh-static could directly depend on the ABI itself. So I'm no more sure if removing that line is really a good idea. OTOH: We are thinking about dropping the zsh-static package after Jessie anyways. Popcon's vote is around 25 and such issues don't seem to have bothered people too much since 2006. So if anyone wants to keep zsh-static and is reading this, please _tell_ us! Removing zsh-static would be better than keeping a buggy one, in particular one that isn't really static. -- Vincent Lefèvre vinc...@vinc17.net - Web: https://www.vinc17.net/ 100% accessible validated (X)HTML - Blog: https://www.vinc17.net/blog/ Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon) -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#763043: x86 emulation does not work on arm host
Control: reassign -1 src:qemu Control: retitle -1 wrong some magic strings in binfmt registration Control: tag -1 confirmed [] # qemu-x86_64 /usr/bin/cdebootstrap-static /usr/bin/cdebootstrap-static: missing suite argument Try `/usr/bin/cdebootstrap-static --help' for more information. # cdebootstrap-static -bash: /usr/bin/cdebootstrap-static: cannot execute binary file: Exec format error Aha. So it is just the binfmt registration problem -- the magic strings. I'll take a look at this. So the problem is quite interesting. There's a field in ELF header, byte #7, ELF_OSABI. All at least x86 binaries so far had this field = 0, which means OSABI_SYSV. But static libraries produced by recent gcc/binutils has this field = 3, which means OSABI_GNU (with GNU extensions as comment says). And this OSABI=3 variant is not handled by our binfmt magic/mask pair. Now, this field (ELF_OSABI) is a enumeration, and we need to allow either 0 or 3 in there, but not other variants, since this will result in qemu trying to execute some clearly different-ABI binaries. A somewhat too intrusive fix for a freeze, but I'll try. Thanks, /mjt -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#750201: icedove: this version breaks calendar-exchange-provider
Hello, there is a new upstream version of calendar-exchange-provider available (3.2.2) https://github.com/Ericsson/exchangecalendar/releases It builds and works with icedove 31.2 esr. Kind regards Mechtilde signature.asc Description: OpenPGP digital signature
Bug#695218: i386-dbg is now documented
Control: fixed -1 1:3.10.0-2 On 2014-11-14 10:22:15 +0100, Mathieu Malaterre wrote: Control: fixed -1 1:3.10.0-2 The bug is marked as closed, but still not marked as fixed. It seems that Control: does not work with -done. Let's try again without -done (now useless as the bug is already closed). -- Vincent Lefèvre vinc...@vinc17.net - Web: https://www.vinc17.net/ 100% accessible validated (X)HTML - Blog: https://www.vinc17.net/blog/ Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon) -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#769535: shinken: service shinken-arbiter works on all daemon
Package: shinken Version: 2.0.3-3 Severity: normal Dear Maintainer, service shinken-arbiter act on all deamons, not only the arbiter. While with service shinken-arbiter: service shinken-arbiter status Checking status of scheduler scheduler RUNNING (pid 27127) .. ok Checking status of poller poller RUNNING (pid 27161) .. ok Checking status of reactionner reactionner RUNNING (pid 27198) .. ok Checking status of broker broker RUNNING (pid 27235) .. ok Checking status of arbiter arbiter RUNNING (pid 27265) .. ok this is only annoying, the restart command should not restart all daemons: # service shinken-arbiter restart Restarting scheduler .. ok Restarting poller .. ok Restarting reactionner .. ok Restarting broker .. ok Restarting arbiter Doing config check .. ok .. ok But besides that: Huge thanks for bringing shinken 2 into debian ! Greetings Hermann -- System Information: Debian Release: 7.7 APT prefers stable APT policy: (500, 'stable'), (25, 'unstable') Architecture: sparc (sparc64) Kernel: Linux 3.12.6 (SMP w/1 CPU core) Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968) Shell: /bin/sh linked to /bin/dash Versions of packages shinken depends on: ii shinken-common 2.0.3-3 pn shinken-mod-auth-cfg-password none ii shinken-mod-pickle-retention-file-generic 1.4.1-2 ii shinken-mod-webui [shinken-mod-sqlitedb] 1.0-1 shinken recommends no packages. Versions of packages shinken suggests: pn shinken-doc none -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#769536: bareos-database-common: circular dependency hell
Package: bareos-database-common Version: 14.2.1+20141017gitc6c5b56-3 Severity: important Hello Bareos Packaging Team, There is a circular dependency between bareos-database-common, bareos-database-mysql, bareos-database-postgresql and bareos-database-sqlite3: bareos-database-common: Depends: bareos-database-postgresql (= 14.2.1+20141017gitc6c5b56-3)| bareos-database-mysql (= 14.2.1+20141017gitc6c5b56-3)| bareos-database-sqlite3 (= 14.2.1+20141017gitc6c5b56-3) bareos-database-mysql :Depends: bareos-database-common (= 14.2.1+20141017gitc6c5b56-3) bareos-database-postgresql :Depends: bareos-database-common (= 14.2.1+20141017gitc6c5b56-3) bareos-database-sqlite3:Depends: bareos-database-common (= 14.2.1+20141017gitc6c5b56-3) Complex circular dependencies are known to cause problems during upgrade, so we should try to avoid them. See threads http://lists.debian.org/debian-devel/2005/06/msg02111.html http://lists.debian.org/debian-devel/2005/11/msg01101.html Cheers, -- Bill. ballo...@debian.org Imagine a large red swirl here. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#769537: gcc-h8300-hms: FTBFS on arm64
Source: gcc-h8300-hms Version: 1:3.4.6+dfsg2-2 It failed to build on arm64: http://buildd.debian.org/status/package.php?p=gcc-h8300-hmssuite=sid The error was: /«BUILDDIR»/gcc-h8300-hms-3.4.6+dfsg2/builddir-h8300-hitachi-coff/gcc/../../gcc/emit-rtl.c:571:(.text+0xfd4): relocation truncated to fit: R_AARCH64_ADR_PREL_PG_HI21 against symbol `fixed_regs' defined in COMMON section in libbackend.a(regclass.o) collect2: error: ld returned 1 exit status You could probably fix this by infiltrating the option -mcmodel=large, as has been suggested for flexpart, for example: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=767213 -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#768463: FTBFS: Failed autobuilding of package
Control: severity -1 important Control: tag -1 moreinfo unreproducible On Tue, Nov 11, 2014 at 17:55:21 +, Jonathan Wiltshire wrote: The fix for this bug is not suitable for Jessie. Please prepare a targetted fix and seek permission to upload it through testing-proposed-uploads, or revert your upload with a targetted fix instead. Actually I can't reproduce this in a jessie chroot, kadu_1.1-1 seems to build ok. Cheers, Julien signature.asc Description: Digital signature
Bug#769528: systemd: ifup@ services failing if no /run/network directory
Control: tag -1 pending Bonjour Didier, Didier Roche [2014-11-14 11:51 +0100]: If networking.service wasn't activated (due to, for instance, no symlink in /etc/init.d/networking not having start symlinks in any /etc/rc*.d/), then there is no /run/network directory created. However, systemd still instantiate and starts ifup@*.service units, which are failing due to the lack of /run/network directory. Consequence is that the system is seen as being in degraded mode. We can make ifup@ template have a Conditional Path on /run/network. Thanks! Applied with some minor whitespace/changelog adjustments: http://anonscm.debian.org/cgit/pkg-systemd/systemd.git/commit/?id=e8bc109667 Martin -- Martin Pitt| http://www.piware.de Ubuntu Developer (www.ubuntu.com) | Debian Developer (www.debian.org) signature.asc Description: Digital signature
Bug#769538: kernel-package: fails with: Missing file: arch/sparc/boot/zImage
Package: kernel-package Version: 12.036+nmu3 Severity: normal Dear Maintainer, i create my the kernel as usual with the command: make-kpkg -j4 kernel_image --initrd --append_to_version -mar the make-kpkg exits with this Missing file error. Its corrent , the file was not created by make-kpkg. I think the creation process of the zImage has failed. -- System Information: Debian Release: 7.7 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable') Architecture: sparc (sparc64) Kernel: Linux 3.14.11-mar (SMP w/1 CPU core) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages kernel-package depends on: ii binutils 2.22-8 ii build-essential11.5 ii debianutils4.3.2 ii file 5.11-2+deb7u6 ii gettext0.18.1.1-9 ii make 3.81-8.2 ii module-init-tools 9-3 ii po-debconf 1.0.16+nmu2 ii util-linux 2.20.1-5.3 Versions of packages kernel-package recommends: ii cpio 2.11+dfsg-0.1 Versions of packages kernel-package suggests: pn btrfs-tools none ii bzip2 1.0.6-4 pn docbook-utils none ii e2fsprogs 1.42.5-1.1 ii grub2 2.02~beta2-10 ii initramfs-tools [linux-initramfs-tool] 0.109.1 pn jfsutilsnone ii libncurses5-dev [libncurses-dev]5.9-10 pn linux-source | kernel-sourcenone pn mcelog none pn oprofilenone pn pcmciautils none ii ppp 2.4.5-5.1+b1 ii procps 1:3.3.3-3 pn quota none pn reiserfsprogs none pn squashfs-tools none ii udev175-7.2 pn xfsprogsnone pn xmlto none -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#613609: (no subject)
control: tags -1 + pending I commited a fix on collab-maint, after talking to Pierre Chifflier. So it should be in next release. signature.asc Description: OpenPGP digital signature
Bug#769271: metamonger: FTBFS in jessie/i386: Tests failures
On 14/11/14 at 12:20 +0100, Richard Hartmann wrote: Lucas, can you reproduce? yes If yes, can I get a full log there was one in the bug report: http://aws-logs.debian.net/ftbfs-logs/2014/11/12/metamonger_0.20141008-1_jessie-i386.log and/or interactive access? sure. just give me your ssh pub key. Then you will need to execute the command at the top of the log to see it yourself: DC-Sbuild-call: su user -c 'sbuild -n -A -s --force-orig-source --apt-update -d jessie -v --arch i386 metamonger_0.20141008-1' Are you doing anything special with permissions, eatmydata, or the like? not that I'm aware of. Lucas -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#769539: must install instead of update on first install
Package: gummiboot Version: 45-2 Severity: normal Tags: patch The attached patch fixes the following issues: - On first install, gummiboot must be invoked with install instead of update. Up until now the user has to manually run gummiboot install after first installing this package. Looking at src/setup/setup.c, it seems okay to always invoke gummiboot with install regardless if the package is installed for the first time or upgraded: If gummiboot is already installed it will simply be overwritten. - On removing the package, gummiboot is not removed from the EFI partition. - gummiboot offers the option --no-variables which prevents changes to the EFI boot order. One example where this option comes in handy is a dual-boot Mac on which the user wants to continue booting OS X by default. The patch makes this option configurable. I've set the priority to critical because changing the boot order can break the system. As always, there's more than one way to do it, so feel free to make any modifications you deem necessary. Let me know if there are questions on why I did something one way or the other. Kind regards, Lukas From 86049f859bbd5b90415c34cd8badd57a2b7b24bc Mon Sep 17 00:00:00 2001 From: Lukas Wunner lu...@wunner.de Date: Fri, 14 Nov 2014 12:41:11 +0100 Subject: [PATCH] Invoke gummiboot with install instead of update in postinst so that it gets copied to EFI partition on first installation of the package Remove gummiboot from EFI partition on package removal Make changing the EFI variables a user-configurable option Signed-off-by: Lukas Wunner lu...@wunner.de --- debian/gummiboot.config| 10 ++ debian/gummiboot.postinst | 17 + debian/gummiboot.prerm | 25 + debian/gummiboot.templates | 21 + 4 files changed, 69 insertions(+), 4 deletions(-) create mode 100644 debian/gummiboot.config create mode 100644 debian/gummiboot.prerm create mode 100644 debian/gummiboot.templates diff --git a/debian/gummiboot.config b/debian/gummiboot.config new file mode 100644 index 000..4971056 --- /dev/null +++ b/debian/gummiboot.config @@ -0,0 +1,10 @@ +#!/bin/sh +set -e + +. /usr/share/debconf/confmodule +db_version 2.0 + +db_input critical gummiboot/change-efivars || true +db_go + +exit 0 diff --git a/debian/gummiboot.postinst b/debian/gummiboot.postinst index 02fb99e..5bffac1 100644 --- a/debian/gummiboot.postinst +++ b/debian/gummiboot.postinst @@ -4,15 +4,24 @@ set -e . /etc/default/gummiboot +. /usr/share/debconf/confmodule + +if [ $1 = configure \ +-o $1 = abort-deconfigure \ +-o $1 = abort-remove ]; then + +db_version 2.0 +db_get gummiboot/change-efivars +if [ $RET != true ]; then +echo Not changing EFI boot variables, retaining existing boot order. 2 +efivars=--no-variables +fi -if [ $1 = configure -a $2 = ]; then for kernel in /boot/vmlinuz-*; do update-gummiboot $(echo $kernel | cut -f2- -d-) done -fi +gummiboot install $efivars --path=$GUMMIBOOT_EFI || : -if [ $1 = configure ]; then -gummiboot update --path=$GUMMIBOOT_EFI || : fi #DEBHELPER# diff --git a/debian/gummiboot.prerm b/debian/gummiboot.prerm new file mode 100644 index 000..d4d26b0 --- /dev/null +++ b/debian/gummiboot.prerm @@ -0,0 +1,25 @@ +#!/bin/sh +# prerm script for gummiboot + +set -e + +. /etc/default/gummiboot +. /usr/share/debconf/confmodule + +if [ $1 = deconfigure -o $1 = remove ]; then + +db_version 2.0 +db_get gummiboot/change-efivars +if [ $RET != true ]; then +echo Not changing EFI boot variables, retaining existing boot order. 2 +efivars=--no-variables +fi + +MACHINE_ID=$(cat /etc/machine-id) + +rm -r $GUMMIBOOT_EFI/loader/ $GUMMIBOOT_EFI/$MACHINE_ID/ || : +gummiboot remove $efivars --path=$GUMMIBOOT_EFI || : + +fi + +#DEBHELPER# diff --git a/debian/gummiboot.templates b/debian/gummiboot.templates new file mode 100644 index 000..9f9f385 --- /dev/null +++ b/debian/gummiboot.templates @@ -0,0 +1,21 @@ +Template: gummiboot/change-efivars +Type: boolean +Default: true +Description: Should gummiboot change the EFI boot variables on installation? + Normally when gummiboot is installed, it creates an entry in the EFI boot + variables and adds it to the top of the boot order list. Disabling this + feature retains the existing boot order. + . + E.g. on an Apple Macintosh, if you would like to continue booting OS X + by default, you need to disable this feature. (Hold down the option key + on startup whenever you want to load gummiboot instead.) +Description-de.UTF-8: Soll gummiboot die EFI Boot Variablen Àndern? + Normalerweise wird bei Installation von gummiboot ein Eintrag in den EFI + Boot Variablen erstellt und an den Anfang der Bootreihenfolge gesetzt. + Schalten Sie diese Funktion aus wenn Sie die bisherige Bootreihenfolge + beibehalten möchten. + . + Wenn Sie z.B. einen Apple Macintosh
Bug#763043: x86 emulation does not work on arm host
Control: tag -1 + patch pending So the problem is quite interesting. There's a field in ELF header, byte #7, ELF_OSABI. All at least x86 binaries so far had this field = 0, which means OSABI_SYSV. But static libraries produced by recent gcc/binutils has this field = 3, which means OSABI_GNU (with GNU extensions as comment says). And this OSABI=3 variant is not handled by our binfmt magic/mask pair. Now, this field (ELF_OSABI) is a enumeration, and we need to allow either 0 or 3 in there, but not other variants, since this will result in qemu trying to execute some clearly different-ABI binaries. A somewhat too intrusive fix for a freeze, but I'll try. For now I just extended the mask to allow either 0, 1, 2 or 3 in this (ELF_OSABI) field. You can do it locally -- in /var/lib/binfmts/qemu-x86_64, change 7th byte (counting from 0) in the mask (the string which starts with \xff\xff...) from 0xff to 0xfb and re-run /etc/init.d/binfmt-support. After that, your static x86 binaries should at least try to work in qemu. Note again the bytes are counted from 0, not from 1. It should look like this: \xff\xff\xff\xff\xff\xfe\xfe\xfb\xff\xff\xff\xff\xff\xff\xff\xff\xfe\xff\xff\xff 0 1 2 3 4 5 6 7 ^^ Since I don't have access to arm box where I can verify this, can you please try this for me and tell if it fixes this issue? Thanks, /mjt -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#768930: unblock: pynag and syslog-nagios-bridge
On 14/11/14 12:33, Julien Cristau wrote: On Tue, Nov 11, 2014 at 22:05:49 +0100, Niels Thykier wrote: On 2014-11-11 19:24, Clint Byrum wrote: Excerpts from Daniel Pocock's message of 2014-11-11 00:59:36 -0800: On 11/11/14 06:05, Clint Byrum wrote: [...] I think we should unblock 0.9.1. Release team have been a bit reluctant to unblock whole new versions without any justification at all In this case though, maybe they can accept that there was a good reason why it wasn't in testing before the freeze: [...] The upload only missed being in testing by 3 days, and fixes a number of issues. We don't want to ship with an old API. Seems like an easy unblock this early in the freeze. Honestly, no - the arguments present are really not all that interesting. In fact, they are a-dime-a-dozen right now. In particular, my argument for rejecting pynag/0.9.1 is that the diff is simply too large to reasonably comprehend. I've added rm hints for both packages. Hi Julien, I had offered to NMU the fix against pynag 0.8.9 and was just waiting for Clint to respond to that Please do not remove the packages Regards, Daniel -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#769540: unblock: pidgin/2.10.10-1.1
Package: release.debian.org Severity: normal Tags: patch User: release.debian@packages.debian.org Usertags: unblock Hey there! I have just uploaded an NMU for Pidgin which fixes a login issue with MSN which occurred after Microsoft changed the application ID that the client needs to send in order to be able to retrieve the contact list. The current version of Pidgin in Jessie no longer allows users to sign on to MSN which makes the MSN part of Pidgin unusable. I have therefore deemed this bug to be release-critical, tagged it as such, made the NMU and am requesting an unblock now. Please find the attached debdiff for the changes of my NMU. Cheers, Adrian unblock pidgin/2.10.10-1.1 -- System Information: Debian Release: 7.7 APT prefers stable APT policy: (500, 'stable'), (99, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.2.0-4-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) (ignored: LC_ALL set to en_US.UTF-8) Shell: /bin/sh linked to /bin/dash diff -Nru pidgin-2.10.10/debian/changelog pidgin-2.10.10/debian/changelog --- pidgin-2.10.10/debian/changelog 2014-10-20 03:01:31.0 +0200 +++ pidgin-2.10.10/debian/changelog 2014-11-14 11:18:12.0 +0100 @@ -1,3 +1,11 @@ +pidgin (2.10.10-1.1) unstable; urgency=medium + + * Non-maintainer upload. + * Add debian/patches/0001-update-msn-application-id.patch to update the +MSN_APPLICATION_ID sent when signing in to MSN (Closes: #769491). + + -- John Paul Adrian Glaubitz glaub...@physik.fu-berlin.de Fri, 14 Nov 2014 10:48:05 +0100 + pidgin (2.10.10-1) unstable; urgency=high * Imported Upstream version 2.10.10 diff -Nru pidgin-2.10.10/debian/patches/0001-update-msn-application-id.patch pidgin-2.10.10/debian/patches/0001-update-msn-application-id.patch --- pidgin-2.10.10/debian/patches/0001-update-msn-application-id.patch 1970-01-01 01:00:00.0 +0100 +++ pidgin-2.10.10/debian/patches/0001-update-msn-application-id.patch 2014-11-14 11:06:58.0 +0100 @@ -0,0 +1,33 @@ +Description: Update the MSN_APPLICATION_ID to fix MSN login issues + Microsoft recently updated the MSN_APPLICATION_ID that the client + sends to the server in order to identify its version. The old ID + used is the application ID of Windows Live Messenger 2008 (8.5) + which Microsoft apparently no longer supports. When the client + attempts to retrieve the contact list, the server will reject + the request. This patch fixes the issue by updating the + MSN_APPLICATION_ID sent by Pidgin. + . +--- +The information above should follow the Patch Tagging Guidelines, please +checkout http://dep.debian.net/deps/dep3/ to learn about the format. Here +are templates for supplementary fields that you might want to add: + +Origin: upstream, https://hg.pidgin.im/pidgin/main/diff/f6a91e6c77a4/libpurple/protocols/msn/contact.h +Bug: (none) +Bug-Debian: https://bugs.debian.org/769491 +Bug-Ubuntu: (none) +Forwarded: (already fixed upstream) +Reviewed-By: John Paul Adrian Glaubitz glaub...@physik.fu-berlin.de +Last-Update: 2014-11-14 + +--- pidgin-2.10.10.orig/libpurple/protocols/msn/contact.h pidgin-2.10.10/libpurple/protocols/msn/contact.h +@@ -60,7 +60,7 @@ typedef enum + #include session.h + #include soap.h + +-#define MSN_APPLICATION_ID CFE80F9D-180F-4399-82AB-413F33A1FA11 ++#define MSN_APPLICATION_ID 484AAC02-7F59-41B7-9601-772045DCC569 + + #define MSN_CONTACT_SERVER local-bay.contacts.msn.com + diff -Nru pidgin-2.10.10/debian/patches/series pidgin-2.10.10/debian/patches/series --- pidgin-2.10.10/debian/patches/series 2014-01-25 17:57:00.0 +0100 +++ pidgin-2.10.10/debian/patches/series 2014-11-14 10:59:53.0 +0100 @@ -0,0 +1 @@ +0001-update-msn-application-id.patch
Bug#769203: unblock: angular.js/1.2.26-1
Hi Julien, On Fri, Nov 14, 2014 at 12:05 PM, Julien Cristau jcris...@debian.org wrote: On Wed, Nov 12, 2014 at 07:15:46 +0100, Laszlo Boszormenyi (GCS) wrote: Please unblock angular.js and let it migrate to Jessie. It's more than a month (34 days) ago in Sid. Didn't migrate in time as Thomas Goirand blocked it with too tight dependency in python-xstatic-angular. He eased that, but the freeze started then. The package doesn't have any bugs. 826 files changed, 86403 insertions(+), 13105 deletions(-) That doesn't sound reasonable at this stage. If I see only those numbers then I have to agree with you. :( On the other hand I can only rephrase the situation: - in the archive for more than a month, - no bugreport against the package, - only blocked by the too tight dependency in python-xstatic-angular that Thomas corrected too late, - v1.2 is a bugfix only branch, the development happens in the v1.3 one, - if you see the changes from 1.2.24 to 1.2.26[1][2], you see that three bugs were fixed, - one of those is a typo fix[3] which affects _all_ locales and they had to be regenerated[4] and this (non code change) makes the diff too large. Please reconsider its inclusion into Jessie. Thanks, Laszlo/GCS [1] https://github.com/angular/angular.js/blob/master/CHANGELOG.md#1.2.25 [2] https://github.com/angular/angular.js/blob/master/CHANGELOG.md#1.2.26 [3] https://github.com/angular/angular.js/commit/1b6d74cc9f7f7b7bd529abe6ce612de3ae661601 [4] https://github.com/angular/angular.js/commit/06c76694ac9b2280594712e6a4b46a1d5987d098 -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#769541: ams: please add the 'Atte-Jensen-instrumentpatches' to the Ams package
Package: ams Version: 1:2.1.1-1kxstudio1 Severity: normal Dear Maintainer, Could you please add extra instumentpatches to the AMS package? The patches are made by Atte Andre Jensen (atteATyoumail.dk ) and are interesting for other users. -- System Information: Debian Release: jessie/sid APT prefers trusty-updates APT policy: (500, 'trusty-updates'), (500, 'trusty-security'), (500, 'trusty'), (100, 'trusty-backports') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.17.1-031701-generic (SMP w/2 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages ams depends on: ii cmt 1:1.16-1kxstudio1 ii libasound21.0.27.2-3ubuntu7 ii libc6 2.19-0ubuntu6.3 ii libgcc1 1:4.9.1-0ubuntu1 ii libjack-jackd2-0 1:1.9.10-1~trusty1 ii libqt4-opengl 4:4.8.5+git192-g085f851+dfsg-2ubuntu4 ii libqtcore44:4.8.5+git192-g085f851+dfsg-2ubuntu4 ii libqtgui4 4:4.8.5+git192-g085f851+dfsg-2ubuntu4 ii libstdc++64.8.2-19ubuntu1 ii mcp-plugins 1:0.4.0-2kxstudio1 ii swh-plugins 0.4.15+1-7kxstudio1 Versions of packages ams recommends: ii amb-plugins 1:0.8.1-4kxstudio1 ii rev-plugins 1:0.7.1-1kxstudio2 ii vco-plugins 1:0.3.0-2kxstudio1 ams suggests no packages. -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#769518: Full steps to get a segfault
Full steps: $ wget http://mirrorblender.top-ix.org/peach/bigbuckbunny_movies/big_buck_bunny_480p_h264.mov $ sudo apt-get install mpv $ mpv big_buck_bunny_480p_h264.mov - press 'f' to get full screen - press hold right-arrow key to fast-forward It should take down your whole X session if you do that twice in a row. 2cts -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#769543: xen-utils-common: missing xen-init-name
Package: xen-utils-common Version: 4.4.1-3 I use xen, and I start some domains using symlinks in /etc/xen/auto. On startup, the file /etc/init.d/xendomains is supposed to start them. It does start the domains, but it also throws out a bunch of errors: /etc/init.d/xendomains: line 135: domains: bad array subscript The culprit is this line in /etc/init.d/xendomains: /usr/lib/xen-common/bin/xen-init-name $1 2/dev/null Seems like xen-init-name is missing in action. Am I missing a package? Is the package missing a file? Thanks, Marc -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
