Bug#755869: openjdk-8-source: src.zip location depends on build architecture
Package: openjdk-8-source Severity: normal same problem as described in #749648 but for openjdk 8 -- System Information: Debian Release: 7.6 APT prefers proposed-updates APT policy: (500, 'proposed-updates'), (500, 'stable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.14-0.bpo.1-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/dash -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#754114: #754114: pgadmin3 crashes - Debug: Adding duplicate image handler for 'PNG file'
Package: pgadmin3 Followup-For: Bug #754114 Control: retitle -1 pgadmin3: crash in the database maintenance dialog Hi, I am able to reproduce the crash. Some times right clicking on a database and selecting 'Maintenance' works as expected showing the maintenance dialog, but clicking on the 'Messages' tab makes pgadmin3 crash. Other times it is enough to show the maintenance dialog and hover the mouse around it without clicking anywhere. The «Debug: Adding duplicate image handler for 'PNG file'» message appears right after pgadmin is started so perhaps it is not relevant to the crash. Here's a backtrace from gdb with all -dbg packages installed when the crash is produced by clicking on the 'Messages' tab: -8--- Program received signal SIGSEGV, Segmentation fault. 0x76a40ff9 in wxCursor::GetCursor() const () from /usr/lib/x86_64-linux-gnu/libwx_gtk2u_core-3.0.so.0 (gdb) bt #0 0x76a40ff9 in wxCursor::GetCursor() const () from /usr/lib/x86_64-linux-gnu/libwx_gtk2u_core-3.0.so.0 #1 0x76a74b73 in wxWindow::GTKUpdateCursor(bool, bool) () from /usr/lib/x86_64-linux-gnu/libwx_gtk2u_core-3.0.so.0 #2 0x76a76cef in wxWindow::GTKHandleRealized() () from /usr/lib/x86_64-linux-gnu/libwx_gtk2u_core-3.0.so.0 #3 0x721f53b8 in g_closure_invoke (closure=0x1bc33a0, return_value=0x0, n_param_values=1, param_values=0x7fffcec0, invocation_hint=0x7fffce60) at /tmp/buildd/glib2.0-2.40.0/./gobject/gclosure.c:768 #4 0x72206d3d in signal_emit_unlocked_R (node=node@entry=0x1064420, detail=detail@entry=0, instance=instance@entry=0x1a8c4c0, emission_return=emission_return@entry=0x0, instance_and_params=instance_and_params@entry=0x7fffcec0) at /tmp/buildd/glib2.0-2.40.0/./gobject/gsignal.c:3551 #5 0x7220ea29 in g_signal_emit_valist (instance=optimized out, signal_id=optimized out, detail=optimized out, var_args=var_args@entry=0x7fffd048) at /tmp/buildd/glib2.0-2.40.0/./gobject/gsignal.c:3307 #6 0x7220ece2 in g_signal_emit (instance=instance@entry=0x1a8c4c0, signal_id=optimized out, detail=detail@entry=0) at /tmp/buildd/glib2.0-2.40.0/./gobject/gsignal.c:3363 #7 0x72d9b4e4 in IA__gtk_widget_realize ( widget=widget@entry=0x1a8c4c0) at /build/gtk+2.0-zztKf7/gtk+2.0-2.24.24/gtk/gtkwidget.c:3554 #8 0x72d9b6d8 in IA__gtk_widget_map (widget=0x1a8c4c0) at /build/gtk+2.0-zztKf7/gtk+2.0-2.24.24/gtk/gtkwidget.c:3428 #9 0x72ce1f9e in gtk_scrolled_window_forall (container=0x1b0e530, include_internals=1, callback=0x72c0a040 gtk_container_map_child, callback_data=0x0) at /build/gtk+2.0-zztKf7/gtk+2.0-2.24.24/gtk/gtkscrolledwindow.c:1082 #10 0x72c0cf3f in gtk_container_map (widget=0x1b0e530) at /build/gtk+2.0-zztKf7/gtk+2.0-2.24.24/gtk/gtkcontainer.c:2684 #11 0x721f55e7 in _g_closure_invoke_va (closure=0x10641f0, return_value=0x0, instance=0x1b0e530, args=0x7fffd368, n_params=0, param_types=0x0) at /tmp/buildd/glib2.0-2.40.0/./gobject/gclosure.c:831 #12 0x7220e088 in g_signal_emit_valist (instance=0x1b0e530, signal_id=optimized out, detail=0, var_args=var_args@entry=0x7fffd368) at /tmp/buildd/glib2.0-2.40.0/./gobject/gsignal.c:3215 #13 0x7220ece2 in g_signal_emit (instance=instance@entry=0x1b0e530, signal_id=optimized out, detail=detail@entry=0) at /tmp/buildd/glib2.0-2.40.0/./gobject/gsignal.c:3363 #14 0x72d9b6ae in IA__gtk_widget_map (widget=widget@entry=0x1b0e530) at /build/gtk+2.0-zztKf7/gtk+2.0-2.24.24/gtk/gtkwidget.c:3430 #15 0x72d9b844 in IA__gtk_widget_set_child_visible (widget=0x1b0e530, is_visible=optimized out) at /build/gtk+2.0-zztKf7/gtk+2.0-2.24.24/gtk/gtkwidget.c:7553 #16 0x72c9f145 in gtk_notebook_real_switch_page (notebook=0x19b22e0, child=optimized out, page_num=optimized out) at /build/gtk+2.0-zztKf7/gtk+2.0-2.24.24/gtk/gtknotebook.c:6161 #17 0x721f53b8 in g_closure_invoke (closure=0x1a4d690, return_value=0x0, n_param_values=3, param_values=0x7fffd620, invocation_hint=0x7fffd5c0) at /tmp/buildd/glib2.0-2.40.0/./gobject/gclosure.c:768 #18 0x72206afb in signal_emit_unlocked_R (node=node@entry=0x1a4df90, detail=detail@entry=0, instance=instance@entry=0x19b22e0, emission_return=emission_return@entry=0x0, instance_and_params=instance_and_params@entry=0x7fffd620) at /tmp/buildd/glib2.0-2.40.0/./gobject/gsignal.c:3589 #19 0x7220ea29 in g_signal_emit_valist (instance=optimized out, signal_id=optimized out, detail=optimized out, var_args=var_args@entry=0x7fffd7d8) at /tmp/buildd/glib2.0-2.40.0/./gobject/gsignal.c:3307 #20 0x7220ece2 in g_signal_emit (instance=optimized out, signal_id=optimized out, detail=optimized out) at
Bug#755870: unattended-upgrades: Allow inclusion of apt-listchanges output in logs and mail
Package: unattended-upgrades Version: 0.82.8 Severity: wishlist Tags: patch Dear Maintainer, I would like to have: - the output of apt-listchanges for the upgraded packages in my unattended-upgrades mails - the output of apt-listchanges for all other packages in an apt-listchanges mail This permit to know why a package was automatically upgraded directly in unattended-upgrades mail. I provide a patch to override “APT_LISTCHANGES_FRONTEND” only when apt-listchanges email address is configured and no sendmail is found, there is no need to force it to none otherwise. Regards. From a1026d1e2b3806c5830c7b309dcc93bc61eafe3f Mon Sep 17 00:00:00 2001 From: Daniel Dehennin daniel.dehen...@baby-gnu.org Date: Thu, 24 Jul 2014 07:40:24 +0200 Subject: [PATCH] Remove useless override of apt-listchanges frontend MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Configuring apt-listchanges frontend to text must permit to get apt-listchanges ouptut in unattended-upgrades logs and mail. * unattended-upgrade (setup_apt_listchanges): Override “APT_LISTCHANGES_FRONTEND” only when apt-listchanges email address is configured and no sendmail exists. --- unattended-upgrade | 24 ++-- 1 file changed, 14 insertions(+), 10 deletions(-) diff --git a/unattended-upgrade b/unattended-upgrade index 16b8cde..e98ce4b 100755 --- a/unattended-upgrade +++ b/unattended-upgrade @@ -37,7 +37,7 @@ import signal import string import subprocess import sys - +import configparser from email.message import Message from gettext import gettext as _ @@ -670,15 +670,19 @@ def wrap(t, width=70, subsequent_indent=): def setup_apt_listchanges(conf=/etc/apt/listchanges.conf): - deal with apt-listchanges -# apt-listchanges will always send a mail if there is a mail address -# set in the config regardless of the frontend used, so set it to -# mail if we have a sendmail and to none if not (as it appears to -# not check if sendmail is there or not), debian bug #579733 -if os.path.exists(SENDMAIL_BINARY): -os.environ[APT_LISTCHANGES_FRONTEND] = mail -else: -os.environ[APT_LISTCHANGES_FRONTEND] = none +deal with apt-listchanges + +apt-listchanges will always send a mail if there is a mail address +set in the config regardless of the frontend used, so force it to +none if we don't have a sendmail (as it appears to not check if +sendmail is there or not), debian bug #579733 + + +config = configparser.ConfigParser() +config.read(conf) +if apt in config and config[apt].get(email_address): +if not os.path.exists(SENDMAIL_BINARY): +os.environ[APT_LISTCHANGES_FRONTEND] = none def _send_mail_using_mailx(to_address, subject, body): -- 2.0.1 -- System Information: Debian Release: jessie/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing'), (90, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 3.15-trunk-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 unattended-upgrades depends on: ii apt1.0.6 ii apt-utils 1.0.6 ii debconf [debconf-2.0] 1.5.53 ii init-system-helpers1.19 ii lsb-base 4.1+Debian13 ii lsb-release4.1+Debian13 ii python33.4.1-1 ii python3-apt0.9.3.8 ii ucf3.0030 ii xz-utils 5.1.1alpha+20120614-2 unattended-upgrades recommends no packages. Versions of packages unattended-upgrades suggests: ii bsd-mailx 8.1.2-0.20131005cvs-1 ii exim4-daemon-light [mail-transport-agent] 4.82.1-1+b1 -- debconf information: * unattended-upgrades/enable_auto_updates: false -- Daniel Dehennin Récupérer ma clef GPG: gpg --recv-keys 0xCC1E9E5B7A6FE2DF Fingerprint: 3E69 014E 5C23 50E8 9ED6 2AAD CC1E 9E5B 7A6F E2DF signature.asc Description: PGP signature
Bug#680264: nodm: ConsoleKit fails to recognize the current session as local
TL;DR: no such luck here. lightdm seems to work better. On Wed, Jul 04, 2012 at 08:23:06PM +0200, Emanuele Aina wrote: tag 680264 patch thanks Stacking a pam_ck_connector.so with x11 support after enabling session auditing with pam_loginuid.so and before the one in common-session (which has the nox11 flag set) fixes the issue. I'd just like to report that this patch does not work for me. I tried getting a nodm user to be able to mount a USB storage device through udisks (on Wheezy). nodm's user fails to work. Lightdm seems to work well. I also tried copying lightdm's autologin pam file to nodm, but no luck there. -- Emanuele diff --git a/debian/nodm.pam b/debian/nodm.pam index 77ad6f6..6f68f35 100644 --- a/debian/nodm.pam +++ b/debian/nodm.pam @@ -18,7 +18,13 @@ session required pam_env.so readenv=1 envfile=/etc/default/locale # # (Replaces the use of /etc/limits in old login) sessionrequired pam_limits.so -# Standard Un*x account and session +# Standard Un*x account @include common-account @include common-password + +# Enable ConsoleKit integration +session optional pam_loginuid.so +session optional pam_ck_connector.so + +# Standard Un*x session @include common-session And here is lightdm-autologin pam file: # egrep -v '^(#|$)' /etc/pam.d/lightdm-autologin authrequisite pam_nologin.so authrequiredpam_env.so readenv=1 authrequiredpam_env.so readenv=1 envfile=/etc/default/locale authrequiredpam_permit.so @include common-account session [success=ok ignore=ignore module_unknown=ignore default=bad] pam_selinux.so close session requiredpam_limits.so session requiredpam_loginuid.so @include common-session session [success=ok ignore=ignore module_unknown=ignore default=bad] pam_selinux.so open @include common-password I use systemd. Also: ii libpam-ck-conn 0.4.5-3.1armhf ii libpam-systemd 44-11+deb7u4 armhf -- Tzafrir Cohen icq#16849755 jabber:tzafrir.co...@xorcom.com +972-50-7952406 mailto:tzafrir.co...@xorcom.com http://www.xorcom.com -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#755855: RFS: liblaxjson/1.0.2-1 [ITP] -- relaxed JSON streaming parser C library
❦ 23 juillet 2014 15:41 -0700, Andrew Kelley superjo...@gmail.com : Package: sponsorship-requests Severity: wishlist Dear mentors, I am looking for a sponsor for my package liblaxjson: * Package name : liblaxjson Version : 1.0.2-1 Upstream Author : Andrew Kelley superjo...@gmail.com * URL : https://github.com/andrewrk/liblaxjson * License : Expat Section : libs Hi Andrew! In debian/control, use debhelper = 9. 9.0.0 never was a debhelper version. In debian/control, Vcs-Git is obviously incorrect (mismatch with Vcs-Browser). Please, make liblaxjson1 multiarch-enabled. See: https://wiki.debian.org/Multiarch On top of debian/rules, remove comments saying this is a sample file. This is not anymore. You can remove the whole notice. In debian/rules, you point to check if dh_installchangelogs would handle CHANGELOG.md automatically. Please, check. From the source code of dh_installchangelogs, it should find CHANGELOG.md without any help. -- Debian package sponsoring guidelines: http://vincent.bernat.im/en/debian-package-sponsoring.html signature.asc Description: PGP signature
Bug#755871: doesn't prompt for keyboard layout when installing over serial konsole
Package: kbd-chooser Version: 1.67 when installing serial console, kbd-chooser is run but doesn't prompt for a keyboard layout. eventhough when installing over serial, the remote machine has the keyboard that is used to enter things during installation, i'd still like to configure the target systems keyboard. -- Address:Daniel Baumann, Donnerbuehlweg 3, CH-3012 Bern Email: daniel.baum...@progress-technologies.net Internet: http://people.progress-technologies.net/~daniel.baumann/ -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#755873: gsql: New/Open/Save buttons do nothing
Package: gsql Version: 0.2.2-1.2+b1 Severity: important -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 The buttons and menu entries for opening and asving sessions do absolutely nothing. Before a conenction is made, they throw: ** (gsql:32717): CRITICAL **: on_file_open_activate: assertion 'GSQL_IS_SESSION (session)' failed ** (gsql:32717): CRITICAL **: on_file_new_sql_activate: assertion 'GSQL_IS_SESSION (session)' failed which is somewhat obvious, but not rendered in the UI. The assertion failures vanish once a connection is made, but the buttons remain useless otherwise. - -- System Information: Debian Release: jessie/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 3.14-1-amd64 (SMP w/6 CPU cores) Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages gsql depends on: ii gconf-service 3.2.6-2 ii gconf2 3.2.6-2 ii gsql-postgresql-engine 0.2.2-1.2+b1 ii libart-2.0-22.3.21-2 ii libatk1.0-0 2.12.0-1 ii libbonobo2-02.32.1-3 ii libbonoboui2-0 2.24.5-2 ii libc6 2.19-7 ii libcairo2 1.12.16-2 ii libfontconfig1 2.11.0-5 ii libfreetype62.5.2-1 ii libgconf-2-43.2.6-2 ii libgdk-pixbuf2.0-0 2.30.7-1 ii libglade2-0 1:2.6.4-2 ii libglib2.0-02.40.0-3 ii libgnome2-0 2.32.1-5 ii libgnomecanvas2-0 2.30.3-2 ii libgnomeui-02.24.5-3 ii libgnomevfs2-0 1:2.24.4-6 ii libgsql00.2.2-1.2+b1 ii libgtk2.0-0 2.24.24-1 ii libgtksourceview2.0-0 2.10.5-1 ii libice6 2:1.0.9-1 ii libnotify4 0.7.6-2 ii liborbit2 1:2.14.19-0.3 ii libpango1.0-0 1.36.3-1 ii libpopt01.16-8 ii libsm6 2:1.2.2-1 ii libxml2 2.9.1+dfsg1-4 ii menu2.1.47 Versions of packages gsql recommends: ii gsql-plugins 0.2.2-1.2+b1 gsql suggests no packages. - -- no debconf information -BEGIN PGP SIGNATURE- Version: GnuPG v1 iQJOBAEBCAA4BQJT0KrhMRpodHRwczovL3d3dy5kb21pbmlrLWdlb3JnZS5kZS9n cGctcG9saWN5LnR4dC5hc2MACgkQt5o8FqDE8pYbJw/+OrQCpBxa3fM1y6WHGzbJ zuDi2cBO/V0q2AcRj1cmDBSgl5x7TjSNJVPW2qrxZx+rYNRWbg6dTWEmJq06yR0f LF3zYJ/EAdRMGC1nSMFEi5mr71QUgXJ5LYFBHxnWP+/lhLAK2nDP1aXyWfU2Wevf 8NEIoL3dQ+yCzzcK8RIgQlQamwOeyLIuD5I2tFWmVqCzDmNHG/1mQvc8lskg0MW0 QoPBherh0ck17GsnDGCMASebK6AnPmsxBUGPpzImZuij65/ho88KwbNSpkiYhb5E kMdqSujaNFjDk2ps1uvfpgBTXsToSRHw46dBSMSK+NPb6hcw9eYzM2yvGDVS1Ri5 eQ2F3Tp/LPppqLutsQ1p574Nww8ERSXPb5b/amOQILy7OrXe0wIaPD6THkmQz3n1 IuEk8kFgsnQYIvRdahZ3N8ywU5vcEs3J0b0MF6X1SnOP77pxZHHpWHYKLCcgoS07 h/ELS72lP6YRvvxdmqTDql6hvXAdsNRPD4TS9di39j+yavggLp0NnR7e5qUvOoNj JEvnLru9JVZFv0ZMFJ/mR3LhNOkOknNBmLbA9A4D3n+qBLfErr0iyHy7jER3f1xe yoFu6TTN5fYcQw8Jdlqr+HhwOuroSsGDIwp87F3FRmeL4HVOUe7hos5fbJY+PACK JZTW0Wadm/4Rq4UnNAh2IS0= =6q3D -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#755846: libroar2: no multiarch possible
control -1 severity serious Raising the severity to 'serious' since this bug breaks a couple of reverse dependencies. libopenal1 depends on libroar-compat2 and a 32 bits libopenal1 is required for wine, for example. Thus, this bug prevents the co-installation of 32 and 64 bit OpenAL applications! Please add Multi-Arch support for roar as soon as possible! Adrian -- .''`. John Paul Adrian Glaubitz : :' : Debian Developer - glaub...@debian.org `. `' Freie Universitaet Berlin - glaub...@physik.fu-berlin.de `-GPG: 62FF 8A75 84E0 2956 9546 0006 7426 3B37 F5B5 F913 -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#755539: transition: hdf5
On 21/07/14 23:59, Gilles Filippini wrote: Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: transition Dear Release Team, The last hdf5 release package in experimental (1.8.13+docs-2) introduced a soname bump (7 - 8) due to the MPIPOSIX API removal, plus significant path changes to allow the co-installation of the different flavors (serial, mpich, openmpi) of the library. Almost all affected source packages need to be adapted to acknowledge the new paths for the hdf5 headers and libraries, depending on the flavor of the library used for the build. For most of them the fix is trivial and consists in adding proper --with-hdf5 configure option or setting C[PP]FLAGS and LDFLAGS at configure step. For example, with cmake build system: include /usr/share/mpi-default-dev/debian_defaults export CMAKE_INCLUDE_PATH=/usr/include/hdf5/$(ARCH_DEFAULT_MPI_IMPL) export CMAKE_LIBRARY_PATH=/usr/lib/$(DEB_HOST_MULTIARCH)/hdf5/$(ARCH_DEFAULT_MPI_IMPL) With configure scripts: --with-hdf5=/usr/lib/$(DEB_HOST_MULTIARCH)/hdf5/serial or --with-hdf5-include=/usr/include/hdf5/serial --with-hdf5-lib=/usr/lib/$(DEB_HOST_MULTIARCH)/hdf5/serial Other trivial cases: export CPPFLAGS += -I/usr/include/hdf5/serial export LDFLAGS += -Wl,-L/usr/lib/$(DEB_HOST_MULTIARCH)/hdf5/serial Affected packages are: adios armadillo aster cdo cmor code-saturne dolfin (not in testing) exodusii flann gdal getdp (not in testing) gmsh gnudatalanguage (not in testing) gpiv gpivtools grads h5py h5utils hdf-eos5 insighttoolkit4 jhdf libcgns libgpiv libmatio libpdl-io-hdf5-perl (not in testing) libvigraimpex magics++ mathgl med-fichier meep meep-lam4 meep-mpich2 meep-mpi-default meep-openmpi minc mpb ncl netcdf nexus oasis3 octave octave-bim octave-msh ovito paraview petsc pygpiv pytables python-shogun r-cran-hdf5 ruby-hdfeos5 salome-kernel scilab shogun silo-llnl slepc (not in testing) stimfit syrthes tessa (not in testing) vtk vtk6 xdmf xmds2 (not in testing) yorick-hdf5 I've tested a build against hdf5 1.8.13+docs-2 for all of them. Here are the cases where the fix is not trivial: FTBFS in sid: gnudatalanguage (blocked by plplot which is in a really bad state) cmor (missing build-deps in debian/control) Use deprecated MPIPOSIX API: h5py silo-llnl Minor patch to the build system needed: hdf-eos5 jhdf libpdl-io-hdf5-perl r-cran-hdf5 ruby-hdfeos5 scilab syrthes Really weird build system (ymake) ncl There are also some cases where the build dependency on libhdf5-*dev seems useless: magics++ oasis3 slepc Now that I've achieved all these test builds I think it is time to request a transition slot. Have you filed bugs for the packages that need changes? Can those changes to the build system happen *before* the new hdf5 is uploaded, or do they need to happen after that? Emilio -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#755874: gobject-introspection: [patch] use multi-arch pathes for the .typelib files
Package: gobject-introspection
Version: 1.40.0-1ubuntu0.1
Severity: wishlist
Tags: patch
Hello,
to install a cross build environment it would be great if the typelibs
could be co-installed in a multiarch environment. Right now all
foo-dev packages depend on gir1.2-foo. So when trying to install foo-dev
for cross-building that won't work because the gir1.2-foo is not
multi-arch ready. The attached patch moves gobject-introspection to
multiarch triplet pathes, adds compatiblity for the old path and
updates dh_girepository to look at both the new and old path.
This part could probably do with a review of someone more familiar
with perl than I am :)
With this change most packages that ship a gir1.2-* package need a small
change to their debian/gir1.2-foo.install file:
- usr/lib/girepository-1.0/*
+ usr/lib/*/girepository-1.0/*
Without they will fail to build.
Here is a draft announcement:
Dear developers,
we would like to move the gnome introspection typelib data from
/usr/lib/girepository-1.0 to /usr/lib/triplet/girepository-1.0
so that we can install them in parallel on a multiarch system.
A updated version of gobject-introspection is ready in experimental that will
look into the new multiarch path and have the old path as a fallback.
But because the pkg-config libdir is now also a multiarch path most
gir1.2-* packages need adjustments to their debian/install file(s).
The change is straightforward, just change your debian/install file:
- usr/lib/girepository-1.0/*
+ usr/lib/*/girepository-1.0/*
because the typelib files are now in e.g. /usr/lib/x86_64-linux-gnu.
Thanks,
Thanks for your consideration!
Michael
-- 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.13.0-32-generic (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Versions of packages gobject-introspection depends on:
ii build-essential11.6ubuntu6
ii libc6 2.19-0ubuntu6
ii libffi63.1~rc1+r3.0.13-12
ii libgirepository-1.0-1 1.40.0-1ubuntu0.1
ii libglib2.0-0 2.40.0-2
ii python-mako0.9.1-1
ii python2.7 2.7.6-8
pn python:any none
gobject-introspection recommends no packages.
gobject-introspection suggests no packages.
-- no debconf information
diff -Nru gobject-introspection-1.40.0/debian/dh_girepository gobject-introspection-1.40.0/debian/dh_girepository
--- gobject-introspection-1.40.0/debian/dh_girepository 2011-12-01 22:22:10.0 +0100
+++ gobject-introspection-1.40.0/debian/dh_girepository 2014-07-23 17:07:14.0 +0200
@@ -75,8 +75,12 @@
my $bin_version = $dh{VERSION};
my @archpackages = getpackages(arch);
+my $triplet = `dpkg-architecture -qDEB_HOST_MULTIARCH`;
+chomp $triplet;
+my $typelib_multiarch_path = /usr/lib/$triplet/girepository-1.0;
my $typelib_path = /usr/lib/girepository-1.0;
-my @typelibdirs = (@ARGV, $typelib_path);
+
+my @typelibdirs = (@ARGV, $typelib_path, $typelib_multiarch_path);
my $gir_path = /usr/share/gir-1.0;
my @girdirs = (@ARGV, $gir_path);
my $arch_triplet = `dpkg-architecture -qDEB_HOST_MULTIARCH`;
@@ -146,28 +150,31 @@
sub require_typelib {
my $req = shift;
my $package = shift;
-my $fullpath = $typelib_path/$req;
+my $fullpath = ;
+foreach my $typelibdir (@typelibdirs) {
+$fullpath = $typelibdir/$req;
-verbose_print (Dependency: $req);
-foreach my $girdir (@girdirs) {
-if (-f tmpdir($package).$girdir/$req) {
-verbose_print( found in the same package);
-return;
+verbose_print (Dependency: $req);
+foreach my $girdir (@girdirs) {
+if (-f tmpdir($package).$girdir/$req) {
+verbose_print( found in the same package);
+return;
+}
}
-}
-foreach my $otherpkg (@archpackages) {
-if (-f tmpdir($otherpkg).$fullpath) {
-verbose_print ( found in $otherpkg);
-error(Dependency on $otherpkg with a different format than $format) unless $otherpkg =~ /^gir$format/;
-addsubstvar ($package, gir:Depends, $otherpkg, = $bin_version);
-return;
+foreach my $otherpkg (@archpackages) {
+if (-f tmpdir($otherpkg).$fullpath) {
+verbose_print ( found in $otherpkg);
+error(Dependency on $otherpkg with a different format than $format) unless $otherpkg =~ /^gir$format/;
+addsubstvar ($package, gir:Depends, $otherpkg, = $bin_version);
+return;
+}
}
-}
-foreach my $privpath (@privdirs) {
-if (-f $privpath/$req) {
-verbose_print ( found in $privpath);
-$fullpath = $privpath/$req;
-
Bug#755855: RFS: liblaxjson/1.0.2-1 [ITP] -- relaxed JSON streaming parser C library
On Wed, Jul 23, 2014 at 11:26 PM, Vincent Bernat ber...@debian.org wrote: ❦ 23 juillet 2014 15:41 -0700, Andrew Kelley superjo...@gmail.com : Package: sponsorship-requests Severity: wishlist Dear mentors, I am looking for a sponsor for my package liblaxjson: * Package name : liblaxjson Version : 1.0.2-1 Upstream Author : Andrew Kelley superjo...@gmail.com * URL : https://github.com/andrewrk/liblaxjson * License : Expat Section : libs Hi Andrew! Thank you for taking the time to review this package, I very much appreciate it. In debian/control, use debhelper = 9. 9.0.0 never was a debhelper version. Done. In debian/control, Vcs-Git is obviously incorrect (mismatch with Vcs-Browser). Fixed. Please, make liblaxjson1 multiarch-enabled. See: https://wiki.debian.org/Multiarch Done. I used a GNUInstallDirs patch and did not submit it upstream because of https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=739876 On top of debian/rules, remove comments saying this is a sample file. This is not anymore. You can remove the whole notice. Done. In debian/rules, you point to check if dh_installchangelogs would handle CHANGELOG.md automatically. Please, check. From the source code of dh_installchangelogs, it should find CHANGELOG.md without any help. Oops. I actually did check and discovered that the override was necessary. I have now removed the comment. Thanks again. If you want to have another look, I have uploaded 1.0.2-2: http://mentors.debian.net/debian/pool/main/libl/liblaxjson/liblaxjson_1.0.2-2.dsc
Bug#755855: RFS: liblaxjson/1.0.2-1 [ITP] -- relaxed JSON streaming parser C library
❦ 24 juillet 2014 00:10 -0700, Andrew Kelley superjo...@gmail.com : Thanks again. If you want to have another look, I have uploaded 1.0.2-2: http://mentors.debian.net/debian/pool/main/libl/liblaxjson/liblaxjson_1. 0.2-2.dsc Seems fine. Please, reupload as 1.0.2-1 (just remove any changelog entry, only keep the initial one, we don't need details). -- Debian package sponsoring guidelines: http://vincent.bernat.im/en/debian-package-sponsoring.html signature.asc Description: PGP signature
Bug#755875: nginx-extras: consider adopting ngx_lua patch for building against luajit
Package: nginx-extras Version: 1.6.0-1 Severity: normal Dear nginx maintainers, I would like you to seriously consider adopting the following patch. Basically it consists on switching over ngx_lua module on nginx-extras in favor of luaJIT as Lua interpreter. LuaJIT is a totally lua-compatible implementation that aims for, between others, boosting performance on intensive CPU operations (like arithmetics) by enabling calling external C code, and ends up building just-in-time code to be loaded into ngx_lua stack. Independently of this, there is a way larger extension support on LuaJIT than regular Lua, that includes, for example, FFI built-in support. This extends Nginx through ngx_lua into a whole new universe of features that regular Lua interpreter alone lacks. If it provides any help, as while developing my own apps on top of ngx_lua, I migrated with no changes at all from lua5.1 to luajit5.1 implementation, just to serve the purpose of adopting missing features on external modules that depended on, for example, FFI support. Mostly all third-party ngx_lua modules out there are using it and even the major nginx-modules provider and OpenResty maintainer fully explains[1] his decision on why switching over to luaJIT for building ngx_lua. This is the reason why I upgraded this bug report severity to normal instead of an expected wishlist one, since I consider switching over to luajit as Lua interpreter would extremely enhance user experience. Thanks in advance. Cheers, Dererk 1. https://groups.google.com/forum/#!topic/openresty-en/Fd370Ly3Upg -- BOFH excuse #342: HTTPD Error 4004 : very old Intel cpu - insufficient processing power diff -ruN nginx-1.6.0.orig/debian/changelog nginx-1.6.0/debian/changelog --- nginx-1.6.0.orig/debian/changelog 2014-04-24 13:23:46.0 -0300 +++ nginx-1.6.0/debian/changelog 2014-07-24 03:50:55.018594460 -0300 @@ -1,3 +1,11 @@ +nginx (1.6.0-2) unstable; urgency=medium + + * debian/modules/nginx-lua: ++ Switching over to luajit as lua interpreter (Closes: #). ++ Reflect this on debian/control. + + -- Ulises Vitulli der...@debian.org Thu, 24 Jul 2014 03:48:25 -0300 + nginx (1.6.0-1) unstable; urgency=medium [ Christos Trochalakis ] diff -ruN nginx-1.6.0.orig/debian/control nginx-1.6.0/debian/control --- nginx-1.6.0.orig/debian/control 2014-04-24 13:23:46.0 -0300 +++ nginx-1.6.0/debian/control 2014-07-24 03:00:27.348014153 -0300 @@ -15,7 +15,7 @@ libexpat-dev, libgd2-dev | libgd2-noxpm-dev, libgeoip-dev, - liblua5.1-dev, + libluajit-5.1-dev, libmhash-dev, libpam0g-dev, libpcre3-dev, diff -ruN nginx-1.6.0.orig/debian/modules/nginx-lua/config nginx-1.6.0/debian/modules/nginx-lua/config --- nginx-1.6.0.orig/debian/modules/nginx-lua/config 2014-04-24 13:23:46.0 -0300 +++ nginx-1.6.0/debian/modules/nginx-lua/config 2014-07-24 03:48:10.816586362 -0300 @@ -131,9 +131,9 @@ ngx_feature=Lua library in /usr/ ngx_feature_path=/usr/include/lua5.1 if [ $NGX_RPATH = YES ]; then -ngx_feature_libs=-R/usr/lib -L/usr/lib -lm -llua5.1 +ngx_feature_libs=-R/usr/lib -L/usr/lib -lm -lluajit-5.1 else -ngx_feature_libs=-L/usr/lib -lm -llua5.1 +ngx_feature_libs=-L/usr/lib -lm -lluajit-5.1 fi . auto/feature fi signature.asc Description: OpenPGP digital signature
Bug#755844: libudev.so.0.13.0: Re: libudev.so.0.13.0: applications crash in libudev (under memory pressure?)
Apparently there are two versions of libudev linked in. Upgrading libudev-dev so it references libudev.so.1 resolves the problem. I am not sure if linking symbols from two different versions of libudev should be prevented in some way. Thanks Michal Excerpts from Michal Suchanek's message of Thu Jul 24 07:08:25 +0200 2014: Package: libudev0 Version: 175-7.2 Followup-For: Bug #755844 Attaching valgrind log of piglit test that 100% reproducibly crashes in libudev. git://anongit.freedesktop.org/piglit -- System Information: Debian Release: 7.6 APT prefers testing APT policy: (910, 'testing'), (900, 'stable'), (500, 'testing'), (410, 'unstable'), (400, 'experimental'), (300, 'saucy-updates'), (300, 'saucy-security'), (300, 'saucy-proposed'), (300, 'saucy-backports'), (300, 'saucy') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.15-trunk-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/bash Versions of packages libudev0:amd64 depends on: ii libc6 2.19-7 ii multiarch-support 2.13-38+deb7u3 libudev0:amd64 recommends no packages. libudev0:amd64 suggests no packages. -- no debconf information ==10336== Memcheck, a memory error detector ==10336== Copyright (C) 2002-2013, and GNU GPL'd, by Julian Seward et al. ==10336== Using Valgrind-3.9.0 and LibVEX; rerun with -h for copyright info ==10336== Command: bin/max-texture-size ==10336== ==10336== Invalid write of size 4 ==10336==at 0x9CED8CC: udev_set_log_priority (in /lib/x86_64-linux-gnu/libudev.so.0.13.0) ==10336==by 0xAF2E90D: udev_new (in /lib/x86_64-linux-gnu/libudev.so.1.4.0) ==10336==by 0x51F20E6: ??? (in /usr/lib/x86_64-linux-gnu/libGL.so.1.2.0) ==10336==by 0x51F23A7: ??? (in /usr/lib/x86_64-linux-gnu/libGL.so.1.2.0) ==10336==by 0x51EDD6C: ??? (in /usr/lib/x86_64-linux-gnu/libGL.so.1.2.0) ==10336==by 0x51C9F23: ??? (in /usr/lib/x86_64-linux-gnu/libGL.so.1.2.0) ==10336==by 0x51C687A: ??? (in /usr/lib/x86_64-linux-gnu/libGL.so.1.2.0) ==10336==by 0x51C6A4F: glXQueryExtensionsString (in /usr/lib/x86_64-linux-gnu/libGL.so.1.2.0) ==10336==by 0x5FBC4D0: wrapped_glXQueryExtensionsString (glx_wrappers.h:120) ==10336==by 0x5FBC58E: glx_display_set_extensions (glx_display.c:55) ==10336==by 0x5FBC6C0: glx_display_connect (glx_display.c:103) ==10336==by 0x5FB6EE1: waffle_display_connect (waffle_display.c:41) ==10336== Address 0xabc57f0 is not stack'd, malloc'd or (recently) free'd ==10336== ==10336== Invalid read of size 1 ==10336==at 0x9CEDFB3: ??? (in /lib/x86_64-linux-gnu/libudev.so.0.13.0) ==10336==by 0x9CED8FD: udev_set_log_priority (in /lib/x86_64-linux-gnu/libudev.so.0.13.0) ==10336==by 0xAF2E90D: udev_new (in /lib/x86_64-linux-gnu/libudev.so.1.4.0) ==10336==by 0x51F20E6: ??? (in /usr/lib/x86_64-linux-gnu/libGL.so.1.2.0) ==10336==by 0x51F23A7: ??? (in /usr/lib/x86_64-linux-gnu/libGL.so.1.2.0) ==10336==by 0x51EDD6C: ??? (in /usr/lib/x86_64-linux-gnu/libGL.so.1.2.0) ==10336==by 0x51C9F23: ??? (in /usr/lib/x86_64-linux-gnu/libGL.so.1.2.0) ==10336==by 0x51C687A: ??? (in /usr/lib/x86_64-linux-gnu/libGL.so.1.2.0) ==10336==by 0x51C6A4F: glXQueryExtensionsString (in /usr/lib/x86_64-linux-gnu/libGL.so.1.2.0) ==10336==by 0x5FBC4D0: wrapped_glXQueryExtensionsString (glx_wrappers.h:120) ==10336==by 0x5FBC58E: glx_display_set_extensions (glx_display.c:55) ==10336==by 0x5FBC6C0: glx_display_connect (glx_display.c:103) ==10336== Address 0xabc57e8 is not stack'd, malloc'd or (recently) free'd ==10336== ==10336== Invalid read of size 8 ==10336==at 0x9CEDFBC: ??? (in /lib/x86_64-linux-gnu/libudev.so.0.13.0) ==10336==by 0x9CED8FD: udev_set_log_priority (in /lib/x86_64-linux-gnu/libudev.so.0.13.0) ==10336==by 0xAF2E90D: udev_new (in /lib/x86_64-linux-gnu/libudev.so.1.4.0) ==10336==by 0x51F20E6: ??? (in /usr/lib/x86_64-linux-gnu/libGL.so.1.2.0) ==10336==by 0x51F23A7: ??? (in /usr/lib/x86_64-linux-gnu/libGL.so.1.2.0) ==10336==by 0x51EDD6C: ??? (in /usr/lib/x86_64-linux-gnu/libGL.so.1.2.0) ==10336==by 0x51C9F23: ??? (in /usr/lib/x86_64-linux-gnu/libGL.so.1.2.0) ==10336==by 0x51C687A: ??? (in /usr/lib/x86_64-linux-gnu/libGL.so.1.2.0) ==10336==by 0x51C6A4F: glXQueryExtensionsString (in /usr/lib/x86_64-linux-gnu/libGL.so.1.2.0) ==10336==by 0x5FBC4D0: wrapped_glXQueryExtensionsString (glx_wrappers.h:120) ==10336==by 0x5FBC58E: glx_display_set_extensions (glx_display.c:55) ==10336==by 0x5FBC6C0: glx_display_connect (glx_display.c:103) ==10336== Address 0xabc57d8 is 8 bytes after a block of size 80 alloc'd ==10336==at 0x4C2A5B0: calloc (vg_replace_malloc.c:618) ==10336==by 0xAF2E772: udev_new (in /lib/x86_64-linux-gnu/libudev.so.1.4.0) ==10336==by 0x51F20E6:
Bug#755855: RFS: liblaxjson/1.0.2-1 [ITP] -- relaxed JSON streaming parser C library
On Thu, Jul 24, 2014 at 12:19 AM, Vincent Bernat ber...@debian.org wrote: Seems fine. Please, reupload as 1.0.2-1 (just remove any changelog entry, only keep the initial one, we don't need details). Done. I realized this just after I dispatched that email to you. Regards, Andrew
Bug#755855: RFS: liblaxjson/1.0.2-1 [ITP] -- relaxed JSON streaming parser C library
* Vincent Bernat ber...@debian.org, 2014-07-24, 08:26: In debian/rules, you point to check if dh_installchangelogs would handle CHANGELOG.md automatically. Please, check. From the source code of dh_installchangelogs, it should find CHANGELOG.md without any help. True, although this feature was added in debhelper 9.20130921, so bumping version in Build-Depends might be worthwhile. And of course, -k is not the default, so if you want to keep the original changelog name, the override is still necessary. I'd use priority optional, not extra. -- Jakub Wilk -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#745771: util-linux: Please enable audit support
Hello! Some notes/to-be-investigated on enabling audit support in util-linux. The audit support seems to only affect the hwclock and login binaries/utilities (in v2.25). In debian the login utility is not built/used from util-linux, so in practise only hwclock is affected. I found this message about audit support in hwclock (from 7 years ago): If you compile --with-audit the hwclock tool reports changes in sys/hw clock to audit system. The real long-term and final solution is probably add hooks for /dev/rtc to kernel, but it's not implemented yet. Maybe the /dev/rtc hooks has appeared since? There's also this administrative detail to investigate: The util-linux package is Priority: required The libaudit1 package is Priority: optional Should libaudit1 priority be raised to required first? Regards, Andreas Henriksson -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#755876: buzztard-bsl: not installable in sid
Package: buzztard-bsl Version: 0.6.0-1 Severity: grave User: trei...@debian.org Usertags: edos-uninstallable Tags: sid Hi, buzztard-bsl is no longer installable in sid on any architecture since 2014-05-21. The reason is that it depends on buzztard, which doesn't exist in sid (but does exist in wheezy). -Ralf. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#755878: nordugrid-arc: FTBFS on hurd-i386
Source: nordugrid-arc Version: 4.1.0-1 User: trei...@debian.org Usertags: edos-uninstallable Hello, nordugrid-arc fails to compile on hurd-i386, see: https://buildd.debian.org/status/fetch.php?pkg=nordugrid-arcarch=hurd-i386ver=4.1.0-1stamp=1399115257 As a consequence, we are left on hurd-i386 with a stale libarccommon2 package that is not installable since it depends on libdb5.1++. -Ralf -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#755776: dictionaries-common: [INTL:sk] Slovak po-debconf translation
Thanks, Christian. Virtaal was too eager and I was too quick. Regards, ~~helix84 -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#755877: Bad rerender in Gnome (sometimes i see strange shapes insead of right view)
Package: xserver-xorg-video-intel Version: 2:2.21.15-2+b2 Severity: serious Problem occurs sometimes, typical when must be refresh / redraw full sreen (switch view in gnome-shell), after unlock screen etc. -- Package-specific info: X server symlink status: lrwxrwxrwx 1 root root 13 Dec 28 2013 /etc/X11/X - /usr/bin/Xorg -rwxr-xr-x 1 root root 2356320 Jul 18 00:25 /usr/bin/Xorg VGA-compatible devices on PCI bus: -- 00:02.0 VGA compatible controller [0300]: Intel Corporation 82945G/GZ Integrated Graphics Controller [8086:2772] (rev 02) /etc/X11/xorg.conf does not exist. /etc/X11/xorg.conf.d does not exist. /etc/modprobe.d contains no KMS configuration files. Kernel version (/proc/version): --- Linux version 3.14-1-amd64 (debian-ker...@lists.debian.org) (gcc version 4.8.3 (Debian 4.8.3-4) ) #1 SMP Debian 3.14.12-1 (2014-07-11) Xorg X server log files on system: -- -rw-r--r-- 1 root root 8227 Feb 28 17:42 /var/log/Xorg.4.log -rw-r--r-- 1 root root 8227 Feb 28 17:42 /var/log/Xorg.5.log -rw-r--r-- 1 root root 38425 Mar 7 08:43 /var/log/Xorg.3.log -rw-r--r-- 1 root root 38791 May 1 17:22 /var/log/Xorg.2.log -rw-r--r-- 1 root root 45236 Jul 13 13:28 /var/log/Xorg.1.log -rw-r--r-- 1 root root 51503 Jul 23 22:53 /var/log/Xorg.0.log Contents of most recent Xorg X server log file (/var/log/Xorg.0.log): - [21.349] X.Org X Server 1.15.1 Release Date: 2014-04-13 [21.349] X Protocol Version 11, Revision 0 [21.349] Build Operating System: Linux 3.13-1-amd64 x86_64 Debian [21.349] Current Operating System: Linux asus 3.14-1-amd64 #1 SMP Debian 3.14.9-1 (2014-06-30) x86_64 [21.349] Kernel command line: BOOT_IMAGE=/boot/vmlinuz-3.14-1-amd64 root=UUID=566f9e50-43c2-4caa-b015-9af4c53a415b ro quiet [21.349] Build Date: 15 April 2014 06:58:36PM [21.349] xorg-server 2:1.15.1-1 (http://www.debian.org/support) [21.349] Current version of pixman: 0.32.4 [21.349]Before reporting problems, check http://wiki.x.org to make sure that you have the latest version. [21.349] Markers: (--) probed, (**) from config file, (==) default setting, (++) from command line, (!!) notice, (II) informational, (WW) warning, (EE) error, (NI) not implemented, (??) unknown. [21.349] (==) Log file: /var/log/Xorg.0.log, Time: Wed Jul 23 11:19:42 2014 [21.417] (==) Using system config directory /usr/share/X11/xorg.conf.d [21.472] (==) No Layout section. Using the first Screen section. [21.472] (==) No screen section available. Using defaults. [21.472] (**) |--Screen Default Screen Section (0) [21.472] (**) | |--Monitor default monitor [21.473] (==) No monitor specified for screen Default Screen Section. Using a default monitor configuration. [21.473] (==) Automatically adding devices [21.473] (==) Automatically enabling devices [21.473] (==) Automatically adding GPU devices [21.512] (WW) The directory /usr/share/fonts/X11/cyrillic does not exist. [21.512]Entry deleted from font path. [21.529] (==) FontPath set to: /usr/share/fonts/X11/misc, /usr/share/fonts/X11/100dpi/:unscaled, /usr/share/fonts/X11/75dpi/:unscaled, /usr/share/fonts/X11/Type1, /usr/share/fonts/X11/100dpi, /usr/share/fonts/X11/75dpi, built-ins [21.529] (==) ModulePath set to /usr/lib/xorg/modules [21.529] (II) The server relies on udev to provide the list of input devices. If no devices become available, reconfigure udev or disable AutoAddDevices. [21.529] (II) Loader magic: 0x7f0641236d40 [21.529] (II) Module ABI versions: [21.529]X.Org ANSI C Emulation: 0.4 [21.529]X.Org Video Driver: 15.0 [21.529]X.Org XInput driver : 20.0 [21.529]X.Org Server Extension : 8.0 [21.530] (II) xfree86: Adding drm device (/dev/dri/card0) [21.531] (--) PCI:*(0:0:2:0) 8086:2772:1043:817a rev 2, Mem @ 0xdfe0/524288, 0xe000/268435456, 0xdfe8/262144, I/O @ 0x8000/8 [21.531] Initializing built-in extension Generic Event Extension [21.531] Initializing built-in extension SHAPE [21.531] Initializing built-in extension MIT-SHM [21.531] Initializing built-in extension XInputExtension [21.531] Initializing built-in extension XTEST [21.531] Initializing built-in extension BIG-REQUESTS [21.531] Initializing built-in extension SYNC [21.531] Initializing built-in extension XKEYBOARD [21.532] Initializing built-in extension XC-MISC [21.532] Initializing built-in extension SECURITY [21.532] Initializing built-in extension XINERAMA [21.532] Initializing built-in extension XFIXES [21.532] Initializing built-in extension RENDER [21.532] Initializing built-in extension RANDR [21.532] Initializing
Bug#755879: ITP: ruby-rouge -- Pure-Ruby syntax highlighter compatible with pygments
Package: wnpp Owner: Youhei SASAKI uwab...@gfd-dennou.org Severity: wishlist * Package name: ruby-rouge Version : 1.5.1 Upstream Author : Jay Adkisson. * URL or Web page : https://github.com/jneen/rouge * License : Expat Description : Pure-Ruby syntax highlighter compatible with pygments Rouge is a pure-ruby syntax highlighter. It can highlight over 60 languages, and output HTML or ANSI 256-color text. Its HTML output is compatible with stylesheets designed for pygments. --- Youhei SASAKI uwab...@gfd-dennou.org uwab...@debian.or.jp GPG fingerprint: 4096/RSA: 66A4 EA70 4FE2 4055 8D6A C2E6 9394 F354 891D 7E07 -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#751407: wide-dhcpv6-server: server sends reply from random UDP port
Hello, On Thu, Jun 12, 2014 at 07:43:37AM -0700, Mihai Hanor wrote: The issue: After a client sends an information-request message, the server replies not from port 547, but from a random UDP port. I'm not sure if it's really a bug and I don't know what the standard says about this, but, at least, the dibbler-server does reply from UDP port 547. I've installed the 20080615-12 version, by downloading the unstable sources of wide-dhcpv6 and compiling them on my wheezy machine, for the fixes related to the wide-dhcpv6-client. There's no improvement when using the stable, official build. RFC3315 only states the following, in section 5.2. UDP Ports: ``Clients listen for DHCP messages on UDP port 546. Servers and relay agents listen for DHCP messages on UDP port 547.'' There is no obligation for the server to send its reply to an information-request message with its source port set to 547. Thank you, Best regards, -- Jeremie /* ``Those of you who think they know everything are very annoying to those of us who do.'' -- Unknown */ signature.asc Description: Digital signature
Bug#755880: bind9: db.root needs update c.root-servers.net got AAAA record
Package: bind9 Version: 1:9.10.0.dfsg~rc2-1 Severity: normal Dear Maintainer, the root zone file has been updated on June 2, 2014. c.root-servers.net now has the IPv6 address 2001:500:2::C. As always the new root zone is available at ftp://ftp.internic.net/domain/named.root I think that bind9 should get updated accordingly. Regards, Matthias -- System Information: Debian Release: jessie/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 3.14-1-amd64 (SMP w/8 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 bind9 depends on: ii adduser3.113+nmu3 ii bind9utils 1:9.10.0.dfsg~rc2-1 ii debconf [debconf-2.0] 1.5.53 ii init-system-helpers1.19 ii libbind9-140 1:9.10.0.dfsg~rc2-1 ii libc6 2.19-7 ii libcap21:2.24-2 ii libcomerr2 1.42.11-2 ii libdns142 1:9.10.0.dfsg~rc2-1 ii libgeoip1 1.6.2-1 ii libgssapi-krb5-2 1.12.1+dfsg-4 ii libirs141 1:9.10.0.dfsg~rc2-1 ii libisc142 1:9.10.0.dfsg~rc2-1 ii libisccc1401:9.10.0.dfsg~rc2-1 ii libisccfg140 1:9.10.0.dfsg~rc2-1 ii libk5crypto3 1.12.1+dfsg-4 ii libkrb5-3 1.12.1+dfsg-4 ii liblwres1401:9.10.0.dfsg~rc2-1 ii libssl1.0.01.0.1h-3 ii libxml22.9.1+dfsg1-4 ii lsb-base 4.1+Debian13 ii net-tools 1.60-26 ii netbase5.2 bind9 recommends no packages. Versions of packages bind9 suggests: pn bind9-docnone ii dnsutils 1:9.9.5.dfsg-4 ii openresolv [resolvconf] 3.5.2-1 pn ufw none -- debconf information excluded -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#724383: grub: diff for NMU version 0.97-67.1
On Sun, Jul 20, 2014 at 07:11:10PM -0400, Eric Dorland wrote: I've prepared an NMU for grub (versioned as 0.97-67.1) and uploaded it to DELAYED/10. Please feel free to tell me if I should delay it longer. I'd completely forgotten about this bug. Thanks, and sorry for the extra work! I've uploaded what I had sitting in bzr as 0.97-68 now. -- Colin Watson [cjwat...@debian.org] -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#755809: xorg.conf.5 man page mentions an incorrect Enable option for Monitors
Julien Cristau, 2014-07-23 16:10+0200: I believe this patch is wrong. How so? I would be happy to provide an updated patch if you tell me what you think is wrong in it. -- ,--. : /` ) ن Tanguy Ortoloxmpp:tan...@ortolo.eu | `-'Debian Developer irc://irc.oftc.net/Tanguy \_ signature.asc Description: Digital signature
Bug#755860: RFP: mrrescue -- Fully FLOSS retro-inspired platformer
Control: reassign -1 wnpp On Jo, 24 iul 14, 01:11:53, J. Vitorino wrote: Package: mrrescue Severity: wishlist I found this fully FLOSS game named Mr Rescue. It's a retro inspired platformer featuring randomly generated levels in which the player controls a fireman attempting to save civilians from burning buildings. The game was built using the love2d engine so it should be fairly easy to pack. The code is licensed under the zlib license and all assets are available under CC-BY-SA 3.0, thus making it elligible for the main repos. The game itself is simple, but quite entertaining and very polished. I believe it would make a fine addition to Debian games library. Official game page: http://tangramgames.dk/games/mrrescue/ Source code (github): https://github.com/SimonLarsen/mrrescue Cheers J. -- http://wiki.debian.org/FAQsFromDebianUser Offtopic discussions among Debian users and developers: http://lists.alioth.debian.org/mailman/listinfo/d-community-offtopic http://nuvreauspam.ro/gpg-transition.txt signature.asc Description: Digital signature
Bug#755860: RFP: mrrescue -- Fully FLOSS retro-inspired platformer
Control: reassign -1 wnpp On Jo, 24 iul 14, 01:11:53, J. Vitorino wrote: Package: mrrescue Severity: wishlist I found this fully FLOSS game named Mr Rescue. It's a retro inspired platformer featuring randomly generated levels in which the player controls a fireman attempting to save civilians from burning buildings. The game was built using the love2d engine so it should be fairly easy to pack. The code is licensed under the zlib license and all assets are available under CC-BY-SA 3.0, thus making it elligible for the main repos. The game itself is simple, but quite entertaining and very polished. I believe it would make a fine addition to Debian games library. Official game page: http://tangramgames.dk/games/mrrescue/ Source code (github): https://github.com/SimonLarsen/mrrescue Cheers J. -- http://wiki.debian.org/FAQsFromDebianUser Offtopic discussions among Debian users and developers: http://lists.alioth.debian.org/mailman/listinfo/d-community-offtopic http://nuvreauspam.ro/gpg-transition.txt signature.asc Description: Digital signature
Bug#755871: doesn't prompt for keyboard layout when installing over serial konsole
Daniel Baumann, le Thu 24 Jul 2014 08:30:25 +0200, a écrit : when installing serial console, kbd-chooser is run but doesn't prompt for a keyboard layout. eventhough when installing over serial, the remote machine has the keyboard that is used to enter things during installation, i'd still like to configure the target systems keyboard. I don't know when the discussion happened (if any), but from the source code it seems that it was made on purpose to avoid a seemingly useless question. Samuel -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#755872: maint-guide.fr: French documentation translation
Control: reassign -1 maint-guide-fr On Jo, 24 iul 14, 08:41:09, Jean-Paul Guillonneau wrote: Package: maint-guide.fr Version: N/A Severity: wishlist Tags: patch l10n ... *** /home/jp/traductions/git/maint-guide/patch-translate.txt Please find attached the French documentation translation, proofread by the debian-l10n-french mailing list contributors. This file should be put as fr.po in the appropriate place in your package build tree. Hi Jean-Paul, I'm reassigning your report to the correct package, but please mind the attached .po is unusable, at least for me. Could you please look into it and resend it attached to this bug? Kind regards, Andrei -- http://wiki.debian.org/FAQsFromDebianUser Offtopic discussions among Debian users and developers: http://lists.alioth.debian.org/mailman/listinfo/d-community-offtopic http://nuvreauspam.ro/gpg-transition.txt signature.asc Description: Digital signature
Bug#755881: base: System Power Management: System re-enters Suspend-to-RAM after waking up
Package: base Severity: normal Dear Maintainer, I encounter this error for several days now (I think since the upgrade to 3.13 amd64 kernel). I often use suspend to ram by directly executing the command (as root) echo mem /sys/power/state. When resuming the system (by pressing the power button), the screen comes active and everything looks normal for a few seconds, but then the system suspends-to-ram automatically once more. Resuming a second time immediately after that leaves the system in normal working mode. It seems to me that 'dmesg' does not report anything unusual. Also, the problem does not arise everytime I suspend the laptop. (I am using a HP elitebook 8440w. ) -- System Information: Debian Release: jessie/sid APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.14-1-amd64 (SMP w/4 CPU cores) -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#755808:
Am 2014-07-24 00:50, schrieb Scott Kitterman: What is the non-working configuration? This means: the new hosts A sends a non-signed email from domain.com to the existing host B that also belongs to domain.com = opendmarc on host B dies silently. I had enabled signing on host A, now it can send emails to host B. Olaf -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#755568: , Resolved
This problem seems to have been resolved by a further upgrade to current testing: Start-Date: 2014-07-23 07:26:21 Commandline: apt-get -f -t testing dist-upgrade Wireless connectivity now works very well again. I have no idea which was the crucial package, but I'm relieved and grateful, Jim -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#755882: octave: statistics() does not work because of skewness and kurtosis
Package: octave Version: 3.8.1-3 Severity: normal signature() and kurtosis() have changed their calling convntions, but statistics.m has not been updated. Here is a patch: --- /usr/share/octave/3.8.1/m/statistics/base/statistics.m~ 2014-05-10 11:24:38.0 +0200 +++ /usr/share/octave/3.8.1/m/statistics/base/statistics.m 2014-07-24 09:46:43.197972678 +0200 @@ -61,7 +61,7 @@ function stats = statistics (x, dim) emp_inv = quantile (x, [0.25; 0.5; 0.75], dim, 7); stats = cat (dim, min (x, [], dim), emp_inv, max (x, [], dim), mean (x, dim), - std (x, [], dim), skewness (x, dim), kurtosis (x, dim)); + std (x, [], dim), skewness (x, [], dim), kurtosis (x, [], dim)); endfunction -- System Information: Debian Release: jessie/sid APT prefers testing APT policy: (990, 'testing'), (500, 'testing-proposed-updates'), (101, 'unstable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.12-1-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=it_IT.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages octave depends on: ii default-jre-headless 2:1.7-52 ii libamd2.3.1 1:4.2.1-3 ii libarpack2 3.1.5-3 ii libatlas3-base [liblapack.so.3] 3.10.2-1 ii libblas3 [libblas.so.3] 1.2.20110419-7 ii libc62.19-7 ii libcamd2.3.1 1:4.2.1-3 ii libccolamd2.8.0 1:4.2.1-3 ii libcholmod2.1.2 1:4.2.1-3 ii libcolamd2.8.0 1:4.2.1-3 ii libcxsparse3.1.2 1:4.2.1-3 ii libfftw3-double3 3.3.4-1 ii libfftw3-single3 3.3.4-1 ii libfltk-gl1.31.3.2-5 ii libfltk1.3 1.3.2-5 ii libfontconfig1 2.11.0-5 ii libfreetype6 2.5.2-1 ii libgcc1 1:4.9.1-1 ii libgl1-mesa-glx [libgl1] 10.2.3-1 ii libglpk364.54-1 ii libglu1-mesa [libglu1] 9.0.0-2 ii libgomp1 4.9.1-1 ii libgraphicsmagick++3 1.3.18-4 ii libgraphicsmagick3 1.3.18-4 ii liblapack3 [liblapack.so.3] 3.5.0-2 ii liboctave2 3.8.1-3 ii libqhull62012.1-5 ii libqrupdate1 1.1.2-1 ii libqscintilla2-112.8.3+dfsg-2 ii libqt4-network 4:4.8.6+dfsg-2 ii libqtcore4 4:4.8.6+dfsg-2 ii libqtgui44:4.8.6+dfsg-2 ii libstdc++6 4.9.1-1 ii libumfpack5.6.2 1:4.2.1-3 ii libx11-6 2:1.6.2-2 ii octave-common3.8.1-3 ii texinfo 5.2.0.dfsg.1-4 Versions of packages octave recommends: ii gnuplot-x11 4.6.5-9 ii libatlas3-base 3.10.2-1 ii pstoedit3.62-1 Versions of packages octave suggests: ii octave-doc 3.8.1-3 ii octave-htmldoc 3.8.1-3 ii octave-info 3.8.1-3 -- 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#755883: gnome-control-center: 'display' module shows error dialog after clicking apply
Package: gnome-control-center Version: 1:3.8.3-7+b2 Severity: important Dear Maintainer, After upgrading my testing distro on 2014-07-32 I'm unable to change display configuration through standard gnome dialog. I don't know witch packages are responsible for regression. The apt log from this day is in attachment. After running this upgrade and restarting computer when I try to click apply button in `gnome-control-center display` I get a dialog with: Failed to apply configuration: %s GDBus.Error:org.freedesktop.DBus.Error.UnknownMethod: No such method 'ApplyConfiguration' PS. I hope I'm reporting this to correct place, in correct form etc. Best Regards, Marek Rusinowski -- System Information: Debian Release: jessie/sid APT prefers testing APT policy: (900, 'testing'), (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.14-1-amd64 (SMP w/8 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages gnome-control-center depends on: ii accountsservice0.6.37-2 ii apg2.2.3.dfsg.1-2 ii colord 1.2.1-1 ii desktop-file-utils 0.22-1 ii gnome-control-center-data 1:3.8.3-7 ii gnome-desktop3-data3.12.2-2 ii gnome-icon-theme 3.12.0-1 ii gnome-icon-theme-symbolic 3.12.0-1 ii gnome-menus3.8.0-2 ii gnome-settings-daemon 3.12.2-1 ii gsettings-desktop-schemas 3.12.2-1 ii libaccountsservice00.6.37-2 ii libatk1.0-02.12.0-1 ii libc6 2.19-7 ii libcairo2 1.12.16-2 ii libcanberra-gtk3-0 0.30-2 ii libcanberra0 0.30-2 ii libcheese-gtk233.12.2-1 ii libcheese7 3.12.2-1 ii libclutter-gtk-1.0-0 1.5.2-2 ii libcolord-gtk1 0.1.25-1.1+b1 ii libcolord2 1.2.1-1 ii libcups2 1.7.4-1 ii libdbus-glib-1-2 0.102-1 ii libfontconfig1 2.11.0-5 ii libgdk-pixbuf2.0-0 2.30.7-1 ii libgl1-mesa-glx [libgl1] 10.2.3-1 ii libglib2.0-0 2.40.0-3 ii libgnome-bluetooth11 3.8.1-3 ii libgnome-desktop-3-7 3.8.4-2 ii libgoa-1.0-0b 3.12.2-1 ii libgoa-backend-1.0-1 3.12.2-1 ii libgtk-3-0 3.12.2-1+b1 ii libgtop2-7 2.28.5-2 ii libibus-1.0-5 1.5.7-1 ii libkrb5-3 1.12.1+dfsg-4 ii libmm-glib01.2.0-1 ii libnm-glib-vpn10.9.10.0-1 ii libnm-glib40.9.10.0-1 ii libnm-gtk0 0.9.10.0-2 ii libnm-util20.9.10.0-1 ii libpango-1.0-0 1.36.3-1 ii libpangocairo-1.0-01.36.3-1 ii libpolkit-gobject-1-0 0.105-6 ii libpulse-mainloop-glib05.0-2 ii libpulse0 5.0-2 ii libpwquality1 1.2.3-1 ii libsmbclient 2:4.1.9+dfsg-1 ii libsocialweb-client2 0.25.20-6 ii libupower-glib10.9.23-2+b2 ii libwacom2 0.8-1 ii libx11-6 2:1.6.2-2 ii libxi6 2:1.7.2-1 ii libxml22.9.1+dfsg1-4 Versions of packages gnome-control-center recommends: ii cups-pk-helper 0.2.5-2 ii gkbd-capplet 3.6.0-1 ii gnome-online-accounts 3.12.2-1 ii gnome-user-guide 3.12.2-1 ii gnome-user-share 3.8.3-1 ii iso-codes 3.55-1 ii mesa-utils 8.2.0-1 ii mousetweaks3.12.0-1 ii network-manager-gnome 0.9.10.0-2 ii ntp1:4.2.6.p5+dfsg-3 ii policykit-1-gnome 0.105-2 ii rygel 0.22.2-2 ii system-config-printer 1.4.3-4 Versions of packages gnome-control-center suggests: ii gnome-screensaver3.6.1-1+b1 ii gstreamer1.0-pulseaudio 1.2.4-1 ii libcanberra-gtk-module 0.30-2 ii libcanberra-gtk3-module 0.30-2 ii x11-xserver-utils7.7+3 ii xscreensaver 5.26-1 -- no debconf information *** /home/p2004a/apt_2014-07-23.log Start-Date: 2014-07-23 10:00:30 Commandline: apt-get -y upgrade Upgrade: gettext-base:amd64 (0.18.3.2-3, 0.18.3.2-4), libstdc++-4.8-dev:amd64 (4.8.3-4, 4.8.3-5), libasan0:amd64 (4.8.3-4, 4.8.3-5), gcc-4.8-base:amd64 (4.8.3-4, 4.8.3-5), gcc-4.8-base:i386 (4.8.3-4, 4.8.3-5), texlive-lang- polish:amd 64 (2014.20140626-1, 2014.20140717-1), libxdamage-dev:amd64 (1.1.4-1, 1.1.4-2), libxfixes3:amd64 (5.0.1-1, 5.0.1-2), libxfixes3:i386 (5.0.1-1, 5.0.1-2), libgettextpo-dev:amd64 (0.18.3.2-3, 0.18.3.2-4), gcc-4.8-multilib:amd64 (4.8.3-4 , 4.8.3-5), libx32gcc-4.8-dev:amd64 (4.8.3-4, 4.8.3-5), cpp-4.8:amd64 (4.8.3-4, 4.8.3-5), libgettextpo0:amd64 (0.18.3.2-3, 0.18.3.2-4), python-pil:amd64 (2.4.0-2, 2.5.1-1), lib32gcc-4.8-dev:amd64 (4.8.3-4, 4.8.3-5), libasprintf- dev:a md64 (0.18.3.2-3, 0.18.3.2-4), maxima:amd64 (5.33.0-3, 5.33.0-11), xserver-
Bug#755884: ITP: r-bioc-variantannotation -- BioConductor annotation of genetic variants
Package: wnpp Severity: wishlist Owner: Andreas Tille ti...@debian.org * Package name: r-bioc-variantannotation Version : 1.10.1 Upstream Author : Valerie Obenchain, Martin Morgan, Michael Lawrence * URL : http://bioconductor.org/packages/release/bioc/html/VariantAnnotation.html * License : Artistic-2.0 Programming Lang: R Description : BioConductor annotation of genetic variants This BioConductor package provides R functions to annotate variants, compute amino acid coding changess and to predict coding outcomes. Remark: This package is maintained by the Debian Med team as another precondition to upgrade all BioCOnductor packages at svn://anonscm.debian.org/debian-med/trunk/packages/R/r-bioc-variantannotation/trunk/ -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#745771: util-linux: Please enable audit support
Le Thu, 24 Jul 2014 09:40:46 +0200, Andreas Henriksson andr...@fatal.se a écrit : Hello! Hello Andreas! Some notes/to-be-investigated on enabling audit support in util-linux. The audit support seems to only affect the hwclock and login binaries/utilities (in v2.25). In debian the login utility is not built/used from util-linux, so in practise only hwclock is affected. Maybe we should investigate switching some binaries like su and login from shadow to util-linux? Apparently RHEL/Centos/Fedora is building them from util-linux. But there are probably some differences between them. I found this message about audit support in hwclock (from 7 years ago): If you compile --with-audit the hwclock tool reports changes in sys/hw clock to audit system. The real long-term and final solution is probably add hooks for /dev/rtc to kernel, but it's not implemented yet. Maybe the /dev/rtc hooks has appeared since? I'll ask to the linux-audit mailing list, they should know about this, but quickly trying hwclock --set --date 10:40 doesn't show anything in the audit logs ATM. There's also this administrative detail to investigate: The util-linux package is Priority: required The libaudit1 package is Priority: optional Should libaudit1 priority be raised to required first? It probably should be the case as systemd is also depending against libaudit and it will become require (or at least standard) soon I guess. Cheers, Laurent Bigonville -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#755885: util-linux: Investigating building setpriv executable
Source: util-linux Version: 2.24.2-1 Severity: wishlist Hi, ATM, the setpriv is not built, we could investigate if we want it in Debian. This executable will add a dependency against libcap-ng. setpriv manpage states: Sets or queries various Linux privilege settings that are inherited across execve(2). Cheers, Laurent Bigonville -- System Information: Debian Release: jessie/sid APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.14-1-amd64 (SMP w/8 CPU cores) Locale: LANG=fr_BE.utf8, LC_CTYPE=fr_BE.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#754930: Possible solution
I had the exactly same bug and today I saw that I have some fglrx packages with dpkg -l *fglrx* So I purged all of them with aptitude purge ... and after reboot it works again with aceleration. Hope it helps you. -- Agur: Javier Ortega Conde (Malkavian) MetaUniversidad: servicios de educación onlinehttp://metauniversidad.com
Bug#755886: RM: bedtools [armel] -- ROM; Build-dep unavailable
Package: ftp.debian.org Severity: normal Dear FTP team, please remove bedtools on armel. It build-depends on samtools, which does not build on armel. This problem prevents migration of the latest version of bedtools to Jessie. Have a nice day, -- Charles Plessy Debian Med packaging team http://www.debian.org/devel/debian-med Tsurumi, Kanagawa, Japan -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#755474: will contact upstream
Hi, I will contact upstream and see what he thinks about it, maybe S would be a better option. Regards, Martijn van Brummelen -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#755362: fixed in sysdig 0.1.86-1
Control: reopen -1 Hi! Evgeni Golov evg...@debian.org (2014-07-24): sysdig (0.1.86-1) unstable; urgency=medium . * New upstream release + Does not FTBFS on !Linux anymore Closes: #755362 * Rebuild manpage using pandoc, instead of shipping the prebuilt version * Ship all upstream Zsh files The first item makes it build again but the last one makes it fail again: | make[1]: Entering directory '/«PKGBUILDDIR»' | dh_install --list-missing | cp: cannot stat 'debian/tmp/usr/share/zsh': No such file or directory | dh_install: cp -a debian/tmp/usr/share/zsh debian/sysdig//usr/share/ returned exit code 1 | make[1]: *** [override_dh_install] Error 2 | debian/rules:29: recipe for target 'override_dh_install' failed https://buildd.debian.org/status/package.php?p=sysdigsuite=sid Mraw, KiBi. signature.asc Description: Digital signature
Bug#755473: confirmed
Hi, Ah I see what you mean thanks. I will contact upstream about it. Regards, Martijn van Brummelen -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#755887: ITP: adderall -- a miniKanren implementation in Hy
Package: wnpp Severity: wishlist Owner: Gergely Nagy alger...@madhouse-project.org * Package name: adderall Version : 0.1.2 Upstream Author : Gergely Nagy alger...@madhouse-project.org * URL : https://github.com/algernon/adderall * License : LGPL Programming Lang: Hy Description : a miniKanren implementation in Hy This is a dependency of Hydiomatic, a Hy code transformer. But it's useful in its own right too. I've yet to come up with a reasonable long description, though. The module will be packaged under the umbrella of pkg-hy, along with its dependency (monaxhyd) and Hydiomatic. Binary packages created will likely be called python-hy-adderall and python3-hy-adderall. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#755848: preseed d-i netcfg/hostname does not set hostname
d-i preseed/early_command string kill-all-dhcp; netcfg when using priority=critical
Bug#751453: AppArmor profiles are, well, slightly suboptimal
Hi, for the record, I submitted a pull request upstream about it: https://github.com/micahflee/torbrowser-launcher/pull/111 Cheers, -- intrigeri -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#755776: dictionaries-common: [INTL:sk] Slovak po-debconf translation
On Thu, Jul 24, 2014 at 09:58:19AM +0200, helix84 wrote:
Thanks, Christian. Virtaal was too eager and I was too quick.
Thanks for the translation.
Due to a misunderstanding at my side a template was still marked as
non-translatable.
I am attaching an updated sk.po file including your changes, after Christian
review, with that template enabled for translation. I'd greatly appeciate if
you could handle it too.
I apologize for the inconveniences.
Regards,
--
Agustin
# Slovak translation of dictionaries-common debconf templates.
# Copyright (C) YEAR THE PACKAGE'S COPYRIGHT HOLDER
# This file is distributed under the same license as the dictionaries-common
package.
# Peter KLFMANiK Mann peter.m...@tuke.sk, 2011.
# Ivan Masár heli...@centrum.sk, 2012, 2014.
msgid
msgstr
Project-Id-Version: dictionaries-common_debian_sk\n
Report-Msgid-Bugs-To: dictionaries-com...@packages.debian.org\n
POT-Creation-Date: 2014-07-24 11:53+0200\n
PO-Revision-Date: 2014-07-23 10:23+0200\n
Last-Translator: Ivan Masár heli...@centrum.sk\n
Language-Team: Slovak debian-l10n-slo...@lists.debian.org\n
Language: sk\n
MIME-Version: 1.0\n
Content-Type: text/plain; charset=UTF-8\n
Content-Transfer-Encoding: 8bit\n
#. Type: error
#. Description
#. TRANSLATORS: DO NOT TRANSLATE variable names such as ${question}
#: ../dictionaries-common.templates:2001
msgid Possible debconf database corruption
msgstr
#. Type: error
#. Description
#. TRANSLATORS: DO NOT TRANSLATE variable names such as ${question}
#: ../dictionaries-common.templates:2001
msgid
The setting for \${question}\ is missing, but packages providing
candidates are installed: \${class_packages}\.
msgstr
#. Type: error
#. Description
#. TRANSLATORS: DO NOT TRANSLATE variable names such as ${question}
#: ../dictionaries-common.templates:2001
msgid
This may be due to corruption in the debconf database. See \/usr/share/doc/
dictionaries-common/README.problems\ on \Debconf database corruption\.
msgstr
#. Type: error
#. Description
#. TRANSLATORS: DO NOT TRANSLATE variable names such as ${question}
#: ../dictionaries-common.templates:2001
msgid
In this case, running \/usr/share/debconf/fix_db.pl\ can help to put the
debconf database in a consistent state.
msgstr
#. Type: error
#. Description
#. TRANSLATORS: DO NOT TRANSLATE variable names such as ${question}
#: ../dictionaries-common.templates:2001
msgid
Some questions are likely to be asked after this message in order to leave
the dictionaries system in a (provisionally) working state.
msgstr
#. Type: error
#. Description
#. TRANSLATORS: DO NOT TRANSLATE variable names such as ${value}
#: ../dictionaries-common.templates:3001
msgid Invalid configuration value for default dictionary
msgstr Neplatná konfiguračná hodnota pre predvoleného slovníka
#. Type: error
#. Description
#. TRANSLATORS: DO NOT TRANSLATE variable names such as ${value}
#: ../dictionaries-common.templates:3001
msgid
An invalid value has been found for a configuration setting for dictionaries-
common. \${value}\ does not correspond to any installed package on the
system.
msgstr
Bola zistená neplatná hodnota konfiguračnej voľby dictionaries-common.
„${value}“ nezodpovedá žiadnemu balíku nainštalovanému v systéme.
#. Type: error
#. Description
#. TRANSLATORS: DO NOT TRANSLATE variable names such as ${value}
#: ../dictionaries-common.templates:3001
msgid
This is usually caused by previous problems during package installation,
where the package providing \${value}\ was selected for installation but
finally not installed because of errors in other packages.
msgstr
Toto je zvyčajne spôsobené predchádzajúcimi problémami počas inštalácie
balíkov, kedy bol na inštaláciu vybraný balík poskytujúci „${value}“, ale
nakoniec sa nenainštaloval kvôli chybám v iných balíkoch.
#. Type: error
#. Description
#. TRANSLATORS: DO NOT TRANSLATE variable names such as ${value}
#: ../dictionaries-common.templates:3001
msgid
To fix this error, reinstall (or install) the package that provides
\${value}\. Then, if you don't want that package on this system, remove
it, which will also delete this configuration setting. A menu of choices
will be shown after this message in order to leave the system in a working
state until you fix the problem.
msgstr
Aby ste túto chybu opravili, preinštalujte alebo nainštalujte balík, ktorý
poskytuje „${value}“. Ak tento balík vo vašom systéme nepotrebujete,
odstráňte ho, čo tiež odstráni túto konfiguračnú voľbu. Menu, ktoré sa
zobrazí po tejto správe, sa pokúsi dovtedy ponechať systém vo funkčnom stave.
#. Type: error
#. Description
#. TRANSLATORS: DO NOT TRANSLATE variable names such as ${value}
#: ../dictionaries-common.templates:3001
msgid
This error message can also appear during ispell dictionary or wordlist
renaming (e.g.: wenglish - wamerican). In this case it is harmless and
everything will be fixed after you select your default in the menu(s) shown
after this message.
msgstr
Táto chybová správa sa môže
Bug#755888: acpi-support-base: does alarming things with su and dbus-send
Package: acpi-support-base Version: 0.142-2 Severity: important As a D-Bus maintainer upstream and in Debian, I was alarmed to see this security notification for the bug fixed in acpi-support 0.142-2: CESG discovered a root escalation flaw in the acpi-support package. An unprivileged user can inject the DBUS_SESSION_BUS_ADDRESS environment variable to run arbitrary commands as root user via the policy-funcs script. My first thought was: What on earth is acpi-support doing on individual users' session buses anyway? The system bus is the place for system services to communicate. So I looked at the diff between acpi-support 0.142-1 and 0.142-2. That particular vulnerability turned out to be in CheckPolicy, which appears to be intended to answer the question: does acpi-support need to handle this particular event, or has someone else taken responsibility? In order to answer that, it appears to be rummaging in /proc/$pid/environ to find users' DBUS_SESSION_BUS_ADDRESSes, then using su and dbus-send from shell script to probe their sessions. This seems rather error-prone. Other parts of acpi-support inject events into users' X11 sessions by fishing their DISPLAY and XAUTHORITY out of random processes' environments, su'ing to the appropriate user and running shell commands. I realise that the vulnerability is not *directly* related to those practices, but still... Here are some recommendations, with low hanging fruit first: * Probe for HasLogindAndSystemd1Manager first, before even looking for the X11 user. This check can be done at a purely system-wide level, without involving yourself with individual users. Also, systemd-logind is meant to be installed by default in Debian 8, and is increasingly depended-on by desktop environments anyway, so this check will often succeed, short-circuiting the scarier logic. * Consider checking only for the presence of systemd-logind, not for its ability to shut down. That would be significantly simpler, and in the unlikely event that systemd-logind is running but the sysadmin has explicitly configured it to not do power management, it seems undesirable for acpi-support to jump in and do it instead. * Modern GNOME relies on systemd-logind for suspend/hibernate/shutdown, so don't dbus-send to it, and perhaps don't check for its processes either; either systemd-logind will do the job, or GNOME won't. Also, as with systemd-logind, in the unlikely event that the logged-in user has explicitly configured GNOME to not load the Power plugin, it seems undesirable for acpi-support to jump in and do it. * I believe modern KDE relies on systemd-logind too; I don't use it, but the KDE maintainers would know. * KDE no longer appears to have dcop, so avoid /usr/bin/dcop --user $XUSER; if you want to support obsolete KDE, avoid that anyway, unless dcop has been audited and is specifically safe for root to use like this. * Does acpi-support do anything on systems where CheckPolicy succeeds? If not, and the intention is for it to be what's installed by people who don't install GNOME, KDE, systemd, etc. and prefer to run fvwm or something, perhaps it should not be part of the laptop task, or that task should depend on systemd-sysv | acpi-support or some such, since Debian 8 is presumably going to install systemd-sysv by default anyway? * I would strongly recommend that system services follow a model where the system service exists only at system level and does not do su, X11, interact with the session bus, etc., and it is up to the user session to connect to the system bus and ask to be notified by system services. However, I recognise that there's a bit of a chicken/egg situation here: the major desktop environments do already use that design, with things like upower and systemd-logind as the system service with which they communicate, leaving acpi-support to try to support environments where the user session doesn't have any support for doing that. 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#755775: [Pkg-sysvinit-devel] Bug#755775: sysv-rc: invoke-rc.d ignores required-stop
Hi, Am 23.07.2014 um 17:12 schrieb Petter Reinholdtsen: You seem to have misunderstood the behavour of invoke-rc.d. It do not start/stop anything else than the script you specify, and do not parse the LSB style init.d script headers. Why do you believe it should do something else? you're right, it is not state anywhere that it actually would be doing so. On the other hand, Debian Policy Manual Section 9.3.3 states that packages should call invoke-rc.d to start/stop services in preinst, postinst and so on and [1] tells about declaring dependencies. As not satisfying these already declared dependencies breaks the applications, and as long as not all packages should implement their own Required-Stop / Required-Start parsing, it seemed natural to me that invoke-rc.d would do this. Is this discussion obsoleted by systemd adoption in the next debian release? Regards, M. Braun [1] https://wiki.debian.org/LSBInitScripts -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#755890: debian-policy: Some directory anf files from etc have unknown package pattern
Package: debian-policy Severity: normal Hi This is the directory and files wo package dependency: /etc/.java /etc/environment /etc/.pwd.lock /etc/subgid /etc/subuid Comamnd is dpkg -S files_on_siscussion -- System Information: Debian Release: jessie/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.14-2-amd64 (SMP w/2 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#755889: pnp4nagios: Small error in README.Debian about Incinga htpasswd.users
Package: pnp4nagios Version: 0.6.16-2 Severity: minor In /usr/share/doc/pnp4nagios/README.Debian: --- quote -- Installation with Icinga If you use Icinga you also have to change /etc/pnp4nagios/apache.conf and replace the line AuthUserFile /etc/icinga/htpasswd.users with AuthUserFile /etc/icinga/htpasswd.users. quote - The first AuthUserFile ... should be changed to /etc/nagios3/htpasswd.users -- System Information: Debian Release: 7.6 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.2.0-4-amd64 (SMP w/2 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#755846: libroar2: no multiarch possible
flum, upstream speaking, On Thu, 2014-07-24 at 08:54 +0200, John Paul Adrian Glaubitz wrote: libopenal1 depends on libroar-compat2 and a 32 bits libopenal1 is required for wine, for example. Thus, this bug prevents the co-installation of 32 and 64 bit OpenAL applications! Please add Multi-Arch support for roar as soon as possible! I thought Debian decided to render RoarAudio useless by droping all dependencies to it? Anyway: 'roar-config --list-path' prints a list of paths it knows about. It may be a good hint to see what directories need to be taken into account (e.g. plugin directories). It may also be useful to check if the multi arch enabled plugin set the right paths. There is no reqirement for the listed binaries (bin-*) to be the same arch or something as libroar. They just need to be runable by libroar by simply calling one of the exec-family's functions. If there is anything that needs to be done upstream* please open a ticket at http://bts.keep-cool.org/ and/or inform us (via roarau...@lists.keep-cool.org). Thank you for your work and have a nice day! * There are plans for a release soon anyway. -- Philipp. (Rah of PH2) signature.asc Description: This is a digitally signed message part
Bug#531412: kdeinit4 calls ssh-add but adds no identities
Hi, Afaik, ssh-add is not called by kdeinit4 directly, but it can be called indirectly by kwallet or some other program in the autostart. If you can still reproduce the issue, please check the SSH_AGENT_PID environment of your ssh-add. Something like this: http://www.unicom.com/blog/entry/612 should work. Happy hacking, -- By definition, when you are investigating the unknown, you do not know what you will find -- The Ultimate Principle Saludos /\/\ /\ `/ signature.asc Description: Digital signature
Bug#755786: dictionaries-common: translation update
On Wed, Jul 23, 2014 at 12:41:07PM +0300, Anatoly Krasner wrote:
Package: dictionaries-common
Version: 1.23.8
Severity: wishlist
Tags: l10n
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hello,
If I used reportbug correctly then a he.po file should be
attached. It's a Hebrew updated translation for po-debconf.
Thanks for the translation.
Due to a misunderstanding at my side a template was still marked as
non-translatable.
I am attaching an updated he.po file including your changes, with that
template enabled for translation. I'd greatly appeciate if you could
handle it too.
I apologize for the inconveniences.
Regards,
--
Agustin
# Translators, if you are not familiar with the PO format, gettext
# documentation is worth reading, especially sections dedicated to
# this format, e.g. by running:
# info -n '(gettext)PO Files'
# info -n '(gettext)Header Entry'
# Some information specific to po-debconf are available at
# /usr/share/doc/po-debconf/README-trans
# or http://www.debian.org/intl/l10n/po-debconf/README-trans
# Developers do not need to manually edit POT or PO files.
# fr33domlover fr33domlo...@riseup.net, 2014.
#
msgid
msgstr
Project-Id-Version: dictionaries-common VERSION\n
Report-Msgid-Bugs-To: dictionaries-com...@packages.debian.org\n
POT-Creation-Date: 2014-07-24 11:53+0200\n
PO-Revision-Date: 2014-07-23 12:06+0300\n
Last-Translator: fr33domlover fr33domlo...@riseup.net\n
Language-Team: עברית \n
Language: en\n
MIME-Version: 1.0\n
Content-Type: text/plain; charset=UTF-8\n
Content-Transfer-Encoding: 8bit\n
Plural-Forms: nplurals=2; plural=(n != 1);\n
#. Type: error
#. Description
#. TRANSLATORS: DO NOT TRANSLATE variable names such as ${question}
#: ../dictionaries-common.templates:2001
msgid Possible debconf database corruption
msgstr
#. Type: error
#. Description
#. TRANSLATORS: DO NOT TRANSLATE variable names such as ${question}
#: ../dictionaries-common.templates:2001
msgid
The setting for \${question}\ is missing, but packages providing
candidates are installed: \${class_packages}\.
msgstr
#. Type: error
#. Description
#. TRANSLATORS: DO NOT TRANSLATE variable names such as ${question}
#: ../dictionaries-common.templates:2001
msgid
This may be due to corruption in the debconf database. See \/usr/share/doc/
dictionaries-common/README.problems\ on \Debconf database corruption\.
msgstr
#. Type: error
#. Description
#. TRANSLATORS: DO NOT TRANSLATE variable names such as ${question}
#: ../dictionaries-common.templates:2001
msgid
In this case, running \/usr/share/debconf/fix_db.pl\ can help to put the
debconf database in a consistent state.
msgstr
#. Type: error
#. Description
#. TRANSLATORS: DO NOT TRANSLATE variable names such as ${question}
#: ../dictionaries-common.templates:2001
msgid
Some questions are likely to be asked after this message in order to leave
the dictionaries system in a (provisionally) working state.
msgstr
#. Type: error
#. Description
#. TRANSLATORS: DO NOT TRANSLATE variable names such as ${value}
#: ../dictionaries-common.templates:3001
msgid Invalid configuration value for default dictionary
msgstr ערך שגוי עבור מילון ברירת המחדל
#. Type: error
#. Description
#. TRANSLATORS: DO NOT TRANSLATE variable names such as ${value}
#: ../dictionaries-common.templates:3001
msgid
An invalid value has been found for a configuration setting for dictionaries-
common. \${value}\ does not correspond to any installed package on the
system.
msgstr
נמצא ערך שגוי בהגדרות של dictionaries-common. \${value}\ אינו מתאים לאף
חבילה המותקנת על־גבי המערכת.
#. Type: error
#. Description
#. TRANSLATORS: DO NOT TRANSLATE variable names such as ${value}
#: ../dictionaries-common.templates:3001
msgid
This is usually caused by previous problems during package installation,
where the package providing \${value}\ was selected for installation but
finally not installed because of errors in other packages.
msgstr
הדבר בדרך כלל נגרם על־ידי בעיות בזמן התקנת החבילות, בהן החבילה שמספקת
\${value}\ נבחרה להתקנה, אך לא הותקנה עקב שגיאות בחבילות אחרות.
#. Type: error
#. Description
#. TRANSLATORS: DO NOT TRANSLATE variable names such as ${value}
#: ../dictionaries-common.templates:3001
msgid
To fix this error, reinstall (or install) the package that provides
\${value}\. Then, if you don't want that package on this system, remove
it, which will also delete this configuration setting. A menu of choices
will be shown after this message in order to leave the system in a working
state until you fix the problem.
msgstr
על־מנת לתקן את השגיאה, יש להתקין (לראשונה או מחדש) את החבילה שמספקת את
\${value}\. לאחר מכן, אם החבילה אינה רצויה עוד, ניתן להסיר אותה, מה שגם
יסיר את ההגדרות של debconf. לאחר הודעה זו יוצג תפריט אפשרויות על־מנת להשאיר
את המערכת במצב שמיש עד לתיקון השגיאה.
#. Type: error
#. Description
#. TRANSLATORS: DO NOT TRANSLATE variable names such as ${value}
#: ../dictionaries-common.templates:3001
msgid
This error message can also appear during ispell
Bug#755808:
On Thursday, July 24, 2014 10:28:52 Olaf Zaplinski wrote: Am 2014-07-24 00:50, schrieb Scott Kitterman: What is the non-working configuration? This means: the new hosts A sends a non-signed email from domain.com to the existing host B that also belongs to domain.com = opendmarc on host B dies silently. I had enabled signing on host A, now it can send emails to host B. Please attach /etc/opendmarc.conf for the host that was dieing silently. Scott K -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#755072: perf-tools instead of iosnoop
I figured I'd package the whole perf-tools suite instead of just iosnoop. The corresponding ITP for perf-tools (renamed to perf-tools-unstable in the mantime) is #755838, and the first version has been uploaded to NEW. Once it enters sid, I'll simply close ##755072. Cheers, --Seb -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#755891: git-rebase examples should avoid 2nd positional argument
Package: git Version: 1:1.7.2.5-3 Severity: minor Nearly all of the examples in git-rebase(1) supply the second positional argument `branch'. This is unhelpful because specifying `branch' is not usually what is wanted. I think this is probably because the examples were intended not as recipes for users to adapt, but as illustrations of git rebase's behaviour - and the railway diagrams are slightly easier if they can be written without regard to the question of what the current branch is. But IMO this is unhelpful because examples in manpages are mostly used by people as recipes, rather than illustrations. Particularly, examples found in manpages like git-rebase(1). I have just encountered a user who got into trouble because they used the examples as recipes, and when adapting them substituted `HEAD' for the 2nd positional parameter to avoid having to write out the name of the current branch. (Of course this left them with a detached HEAD, leaving what was their current branch unrewritten.) I would propose the following changes to the manpage: * In each example railway diagram, mark the current branch (eg with * like `git branch') does. * Whenever a single rune is given with two positional arguments, put the second one in [ ] to indicate that it is optional. If this is likely to meet with approval I will prepare a patch. Thanks, Ian. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#755838: ITP: perf-tools -- DTrace-like tools for linux
On Jul/24, Ben Hutchings wrote: If it stays in testing, it will go into the next stable and you then need to support some arbitrary version for ~3 years. OK, I initially thought it was the mention about the caveats in the package's description that led to your request. About the arbitrary version, I plan on asking upstream to tag his source tree at a commit he considers stable-ish, so the resulting packaged version doesn't look like a plain arbitrary snapshot. Cheers, --Seb -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#755776: dictionaries-common: [INTL:sk] Slovak po-debconf translation
Updated translation attached.
Regards,
~~helix84
# Slovak translation of dictionaries-common debconf templates.
# Copyright (C) YEAR THE PACKAGE'S COPYRIGHT HOLDER
# This file is distributed under the same license as the dictionaries-common package.
# Peter KLFMANiK Mann peter.m...@tuke.sk, 2011.
# Ivan Masár heli...@centrum.sk, 2012, 2014.
msgid
msgstr
Project-Id-Version: dictionaries-common_debian_sk\n
Report-Msgid-Bugs-To: dictionaries-com...@packages.debian.org\n
POT-Creation-Date: 2014-07-24 11:53+0200\n
PO-Revision-Date: 2014-07-24 12:35+0200\n
Last-Translator: Ivan Masár heli...@centrum.sk\n
Language-Team: Slovak debian-l10n-slo...@lists.debian.org\n
Language: sk\n
MIME-Version: 1.0\n
Content-Type: text/plain; charset=UTF-8\n
Content-Transfer-Encoding: 8bit\n
#. Type: error
#. Description
#. TRANSLATORS: DO NOT TRANSLATE variable names such as ${question}
#: ../dictionaries-common.templates:2001
msgid Possible debconf database corruption
msgstr Možné poškodenie databázy debconf
#. Type: error
#. Description
#. TRANSLATORS: DO NOT TRANSLATE variable names such as ${question}
#: ../dictionaries-common.templates:2001
msgid
The setting for \${question}\ is missing, but packages providing
candidates are installed: \${class_packages}\.
msgstr
Nastavenie „${question}“ chýba, ale sú nainštalované balíky poskytujúce
kandidátov: „${class_packages}“.
#. Type: error
#. Description
#. TRANSLATORS: DO NOT TRANSLATE variable names such as ${question}
#: ../dictionaries-common.templates:2001
msgid
This may be due to corruption in the debconf database. See \/usr/share/doc/
dictionaries-common/README.problems\ on \Debconf database corruption\.
msgstr
Mohlo to spôsobiť poškodenie databázy debconf. Informácie o poškodení
databázy debconf nájdete v súbore „/usr/share/doc/dictionaries-
common/README.problems“.
#. Type: error
#. Description
#. TRANSLATORS: DO NOT TRANSLATE variable names such as ${question}
#: ../dictionaries-common.templates:2001
msgid
In this case, running \/usr/share/debconf/fix_db.pl\ can help to put the
debconf database in a consistent state.
msgstr
V tomto prípade môže spustenie „/usr/share/debconf/fix_db.pl“ pomôcť opraviť
databázu debconf do konzistentného stavu.
#. Type: error
#. Description
#. TRANSLATORS: DO NOT TRANSLATE variable names such as ${question}
#: ../dictionaries-common.templates:2001
msgid
Some questions are likely to be asked after this message in order to leave
the dictionaries system in a (provisionally) working state.
msgstr
Je pravdepodobné, že po tejto správe vás Debconf vyzve zodpovedať niektoré
otázky s cieľom zachovať systém slovníkov v (dočasne) funkčnom stave.
#. Type: error
#. Description
#. TRANSLATORS: DO NOT TRANSLATE variable names such as ${value}
#: ../dictionaries-common.templates:3001
msgid Invalid configuration value for default dictionary
msgstr Neplatná konfiguračná hodnota pre predvoleného slovníka
#. Type: error
#. Description
#. TRANSLATORS: DO NOT TRANSLATE variable names such as ${value}
#: ../dictionaries-common.templates:3001
msgid
An invalid value has been found for a configuration setting for dictionaries-
common. \${value}\ does not correspond to any installed package on the
system.
msgstr
Bola zistená neplatná hodnota konfiguračnej voľby dictionaries-common.
„${value}“ nezodpovedá žiadnemu balíku nainštalovanému v systéme.
#. Type: error
#. Description
#. TRANSLATORS: DO NOT TRANSLATE variable names such as ${value}
#: ../dictionaries-common.templates:3001
msgid
This is usually caused by previous problems during package installation,
where the package providing \${value}\ was selected for installation but
finally not installed because of errors in other packages.
msgstr
Toto je zvyčajne spôsobené predchádzajúcimi problémami počas inštalácie
balíkov, kedy bol na inštaláciu vybraný balík poskytujúci „${value}“, ale
nakoniec sa nenainštaloval kvôli chybám v iných balíkoch.
#. Type: error
#. Description
#. TRANSLATORS: DO NOT TRANSLATE variable names such as ${value}
#: ../dictionaries-common.templates:3001
msgid
To fix this error, reinstall (or install) the package that provides
\${value}\. Then, if you don't want that package on this system, remove
it, which will also delete this configuration setting. A menu of choices
will be shown after this message in order to leave the system in a working
state until you fix the problem.
msgstr
Aby ste túto chybu opravili, preinštalujte alebo nainštalujte balík, ktorý
poskytuje „${value}“. Ak tento balík vo vašom systéme nepotrebujete,
odstráňte ho, čo tiež odstráni túto konfiguračnú voľbu. Menu, ktoré sa
zobrazí po tejto správe, sa pokúsi dovtedy ponechať systém vo funkčnom stave.
#. Type: error
#. Description
#. TRANSLATORS: DO NOT TRANSLATE variable names such as ${value}
#: ../dictionaries-common.templates:3001
msgid
This error message can also appear during ispell dictionary or wordlist
renaming (e.g.: wenglish - wamerican). In this case it is harmless and
Bug#755892: restart doesn't work (server is terminated)
Package: mini-httpd Version: 1.19-9.3 Severity: important flum, when the mini-httpd is restarted by logrotate (or manually) there is a race condition preventing it from starting again. To mee it seems that the problem is that mini-httpd can not bind to the port if there are any active HTTP connections while the server is restarted. This results in the server to be stopped but not restarted. The initscript should check if the start command within the restart succeeded and handle the case if it doesn't. I'm looking forward to see a fix soon and thank you already for taking care of this problem. Have a nice day! -- Philipp. (Rah of PH2) -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#733113: gnome-shell-extensions: Alternative status menu fails to display an Hibernate entry
Control: tag -1 + moreinfo Hi, since #733112 is now gone, I suspect this bug can't be reproduced anymore. Correct? Cheers, -- intrigeri -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#755865: dictionaries-common: [INTL:th] Thai debconf translation update
Quoting Theppitak Karoonboonyanan (t...@debian.org): Package: dictionaries-common Version: 1.23.9 Severity: wishlist Tags: l10n, patch Dear Maintainer, Please update Thai debconf translation with the attached PO. Thanks. Hello Thep, Since then, an untranslatable template was turned to translated which added 5 strings to translate. Would you mind completing the attached file? th.po Description: application/gettext signature.asc Description: Digital signature
Bug#755893: Smart Card IO fails to detect any card terminals
Package: openjdk-7-jre-headless
Version: 7u65-2.5.1-3
Severity: normal
Dear Maintainer,
The smartcardio package no longer works with this upload. Java is no
longer able to detect any card readers. Below is a test program and
the output with the current and previous version. It looks like Java
is no longer able to load or initialize the libpcsclite library.
== Output with version 7u65-2.5.1-2 ==
TerminalFactory for type PC/SC from provider SunPCSC
2 card terminals
== Output with version 7u65-2.5.1-3 ==
TerminalFactory for type None from provider None
0 card terminals
== CardTerminals.java ==
import javax.smartcardio.*;
public class CardTerminals {
public static void main (String args[]) throws Exception {
TerminalFactory tf = TerminalFactory.getDefault();
System.out.println(tf);
System.out.format(%d card terminals\n, tf.terminals().list().size());
}
}
-- System Information:
Debian Release: jessie/sid
APT prefers unstable
APT policy: (500, 'unstable'), (500, 'testing'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 3.14-1-amd64 (SMP w/4 CPU cores)
Locale: LANG=nl_BE.UTF-8, LC_CTYPE=nl_BE.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Versions of packages openjdk-7-jre-headless:amd64 depends on:
ii ca-certificates-java 20140324
ii java-common 0.52
ii libc6 2.19-7
ii libcups2 1.7.4-2
ii libfontconfig12.11.0-5
ii libfreetype6 2.5.2-1
ii libgcc1 1:4.9.1-1
ii libglib2.0-0 2.40.0-3
ii libjpeg8 8d1-1
ii libkrb5-3 1.12.1+dfsg-5
ii liblcms2-22.6-3
ii libnss3 2:3.16.3-1
ii libpcsclite1 1.8.11-3
ii libstdc++64.9.1-1
ii multiarch-support 2.19-7
ii tzdata-java 2014e-1
ii zlib1g1:1.2.8.dfsg-1
Versions of packages openjdk-7-jre-headless:amd64 recommends:
ii icedtea-7-jre-jamvm 7u65-2.5.1-3
Versions of packages openjdk-7-jre-headless:amd64 suggests:
ii fonts-dejavu-extra 2.34-1
pn fonts-indicnone
pn fonts-ipafont-gothic none
pn fonts-ipafont-mincho none
ii libnss-mdns0.10-6
pn sun-java6-fontsnone
pn ttf-wqy-microhei | ttf-wqy-zenhei 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#755509: RM: elilo -- RoQA; Orphaned since a year, replaced by better options
On Monday, July 21, 2014 22:45:33 Bob Bib wrote: If it hasn't been orphaned, it would be rather pointless to remove it, as the latest upstream version (3.16) is just a year old (2013-03-29): http://sourceforge.net/projects/elilo/files/elilo/elilo-3.16/ (while in Debian currently has v3.14 2011-01-13). Meanwhile, gummiboot is quite new in Debian (April 2014). EFI LILO fans should probably have a word here :) In any case, it will have to be dropped from DI before it can be removed. # Broken Build-Depends: debian-installer: elilo Please remove the moreinfo tag after issues around this are resolved. Scott K -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#755861: RM: bluez-hcidump -- ROM; obsolete, replaced by bluez5
On Thursday, July 24, 2014 09:15:54 Nobuhiro Iwamatsu wrote: Package: ftp.debian.org Severity: normal Dear ftpmasters, Please remove bluez-hcidump from unstable, this was merged into bluez version 5, it has been replaced by bluez version 5. Does this mean both source and binary packages should be removed? Source has already been removed from Unstable. Please remove the moreinfo tag after this question is answered. Scott K -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#755895: [INTL:sv] Swedish strings for dictionaries-common debconf
package: dictionaries-common severity: wishlist tags: patch l10n Please consider to add this file to translation of debconf. -- brother http://sis.bthstuden.se sv.po Description: Binary data
Bug#749591: New upstream version available
I've just tried and sqlitebrowser (from https://github.com/sqlitebrowser/sqlitebrowser) is trivially debianizable with dh_make (and dh $@ --buildsystem=cmake). Why not pick up the new version and leave the refactoring of qhexedit and antlr for later? Íve pretty sure users would appreciate the new version, it's much better than what Debian has. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#755791: dictionaries-common: [INTL:eo] Esperanto po-debconf translation
On Wed, Jul 23, 2014 at 07:55:54AM -0300, Felipe E. F. de Castro wrote:
Package: dictionaries-common
Version: 1.23.8
Severity: wishlist
Tags: patch
Dear Maintainer,
Please update the Esperanto translation, see the po-file attached.
Thanks for the translation.
Due to a misunderstanding at my side a template was still marked as
non-translatable.
I am attaching an updated eo.po file including your changes, with that
template enabled for translation. I'd greatly appeciate if you could
handle it too.
I apologize for the inconveniences.
Regards,
--
Agustin
# Translation to Esperanto
# Copyright (C) 2007, 2011, 2014 Free Software Foundation, Inc.
# Serge Leblanc serge.lebl...@wanadoo.fr, 2007.
# Felipe Castro fef...@gmail.com, 2011, 2014.
msgid
msgstr
Project-Id-Version: dictionaries-common\n
Report-Msgid-Bugs-To: dictionaries-com...@packages.debian.org\n
POT-Creation-Date: 2014-07-24 11:53+0200\n
PO-Revision-Date: 2014-07-23 07:05-0300\n
Last-Translator: Felipe Castro fef...@gmail.com\n
Language-Team: Esperanto debian-l10n-espera...@lists.debian.org\n
Language: eo\n
MIME-Version: 1.0\n
Content-Type: text/plain; charset=UTF-8\n
Content-Transfer-Encoding: 8bit\n
#. Type: error
#. Description
#. TRANSLATORS: DO NOT TRANSLATE variable names such as ${question}
#: ../dictionaries-common.templates:2001
msgid Possible debconf database corruption
msgstr
#. Type: error
#. Description
#. TRANSLATORS: DO NOT TRANSLATE variable names such as ${question}
#: ../dictionaries-common.templates:2001
msgid
The setting for \${question}\ is missing, but packages providing
candidates are installed: \${class_packages}\.
msgstr
#. Type: error
#. Description
#. TRANSLATORS: DO NOT TRANSLATE variable names such as ${question}
#: ../dictionaries-common.templates:2001
msgid
This may be due to corruption in the debconf database. See \/usr/share/doc/
dictionaries-common/README.problems\ on \Debconf database corruption\.
msgstr
#. Type: error
#. Description
#. TRANSLATORS: DO NOT TRANSLATE variable names such as ${question}
#: ../dictionaries-common.templates:2001
msgid
In this case, running \/usr/share/debconf/fix_db.pl\ can help to put the
debconf database in a consistent state.
msgstr
#. Type: error
#. Description
#. TRANSLATORS: DO NOT TRANSLATE variable names such as ${question}
#: ../dictionaries-common.templates:2001
msgid
Some questions are likely to be asked after this message in order to leave
the dictionaries system in a (provisionally) working state.
msgstr
#. Type: error
#. Description
#. TRANSLATORS: DO NOT TRANSLATE variable names such as ${value}
#: ../dictionaries-common.templates:3001
msgid Invalid configuration value for default dictionary
msgstr Malvalida agordo-valoro por apriora vortaro
#. Type: error
#. Description
#. TRANSLATORS: DO NOT TRANSLATE variable names such as ${value}
#: ../dictionaries-common.templates:3001
msgid
An invalid value has been found for a configuration setting for dictionaries-
common. \${value}\ does not correspond to any installed package on the
system.
msgstr
Malvalida valoro estis trovata por difina agordo por dictionaries-common.
\${value}\ ne korespondas al iu ajn instalita pako en la sistemo.
#. Type: error
#. Description
#. TRANSLATORS: DO NOT TRANSLATE variable names such as ${value}
#: ../dictionaries-common.templates:3001
msgid
This is usually caused by previous problems during package installation,
where the package providing \${value}\ was selected for installation but
finally not installed because of errors in other packages.
msgstr
Tio ordinare okazas pro antaŭaj malfacilaĵoj dum instalo de pako,kie la pako
provizanta \${value}\ estis elektata por instalo sed finfine ne estis
instalata pro eraroj en aliaj pakoj.
#. Type: error
#. Description
#. TRANSLATORS: DO NOT TRANSLATE variable names such as ${value}
#: ../dictionaries-common.templates:3001
msgid
To fix this error, reinstall (or install) the package that provides
\${value}\. Then, if you don't want that package on this system, remove
it, which will also delete this configuration setting. A menu of choices
will be shown after this message in order to leave the system in a working
state until you fix the problem.
msgstr
Por korektigi tiun ĉi eraron, bonvolu reinstali (aŭ instali) la pakon kiu
provizas \${value}\. Tiam, se vi ne plu volas uzi tiun ĉi pakon en via
sistemo, forigu ĝin, kio ankaŭ forigos ties agordan datumaron. La montrota
menuo post tiu ĉi mesaĝo ebligos lasi la sistemon en uzebla stato ĝis kiam
vi riparos la problemon.
#. Type: error
#. Description
#. TRANSLATORS: DO NOT TRANSLATE variable names such as ${value}
#: ../dictionaries-common.templates:3001
msgid
This error message can also appear during ispell dictionary or wordlist
renaming (e.g.: wenglish - wamerican). In this case it is harmless and
everything will be fixed after you select your default in the menu(s) shown
after this message.
msgstr
Tiu ĉi erar-mesaĝo ankaŭ povos aperi kiam vortaro
Bug#708070: enable x32 support for the amd64 kernels
I was just hit by bug https://bugs.debian.org/736659 after installing gcc-multilib and later rebuilding my initramfs. I don't think this situation of having several x32 packages on the archive (which other packages depend on) while the official debian kernel don't supports x32 at all is sustainable in the long run. Please consider enabling CONFIG_X86_X32 on 3.14 and superior. Thanks signature.asc Description: OpenPGP digital signature
Bug#752045: [BTS#752045] templates://dictionaries-common/{dictionaries-common.templates} : Final update for English review
On Wed, Jul 23, 2014 at 07:39:12PM +0200, Agustin Martin wrote: 2014-07-19 8:21 GMT+02:00 Christian PERRIER bubu...@debian.org: Dear Debian maintainer, On Monday, June 23, 2014, I notified you of the beginning of a review process concerning debconf templates for dictionaries-common. The debian-l10n-english contributors have now reviewed these templates, and the final proposed changes are attached to this update to the original bug report. Please review the suggested changes, and if you have any objections, let me know in the next 3 days. However, please try to avoid uploading dictionaries-common with these changes right now. The second phase of this process will begin on Tuesday, July 22, 2014, when I will coordinate updates to translations of debconf templates. Sorry, I was very busy with the end of the term and could not read your message in depth until today, once translators started sending changes. I even thought I was the one who should ask translators for updates. Looking at the translations I noticed that first template was not being translated. It was temporarily left as untranslatable in the uploaded packages to have the question available, but translators not start working on it until consensus was reached, and it got unnoticed as non-translatable. Changed it to translatable, added a dot at end of sentence and changed type to error. I also missed that templates to be removed were still there, removed. Changes attached, both full templates file and diff against final version. I am contacting translators for already received bug reports with an updated xx.po file. Christian, I see that you already contacted Thep for the Thai translation. I already did for sk.po, he.po and eo.po. I am about to do it for sv.po Again, I apologize for the inconvenience. I will try to keep caring of this until I go some days in vacation. It was my misunderstanding and my lack of time, it is my work to try to sort this out. Regards, -- Agustin -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#755897: ITP: alfred -- Almighty Lightweight Fact Remote Exchange Daemon
Package: wnpp Severity: wishlist Owner: Stefen Moeller steffen_moel...@gmx.de * Package name: alfred * URL : http://www.open-mesh.org/projects/open-mesh/wiki/Alfred * License : GPL Programming Lang: C Description : Almighty Lightweight Fact Remote Exchange Daemon A.L.F.R.E.D. gathers status information in networks with dynamically chaing topologies, e.g. a Wifi mesh with mobile clients. It is a user space daemon for distributing arbitrary local information over the same mesh/network in a decentralized fashion. This data can be anything which appears to be useful - originally designed to replace the batman-adv visualization (vis), you may distribute hostnames, phone books, administration information, DNS information, the local weather forecast ... . Users may insert information by using the alfred binary on the command line, or use custom written programs to communicate with alfred directly through unix sockets. Once the local data is received, the alfred daemon takes care of distributing this information to other alfred servers on other nodes somewhere in the network. As addressing scheme IPv6 link-local multicast addresses are used which do not require any manual configuration. A user can request data from alfred, and will receive the information available from all alfred servers in the network. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#755896: cinnamon-settings-daemon: Power management and Battery life applet not working
Package: cinnamon-settings-daemon Version: 2.2.4.repack-1 Severity: normal Dear Maintainer, *** Reporter, please consider answering these questions, where appropriate *** Following updating from self-compiled cinnamon 2.2.9 to the debian repos 2.2.14-2 I found that the previously working battery management settings was no longer reporting my batteries charge in it and the power applet was no longer there. upower is version 0.99.0 and seems to be working fine. This is possibly linked to upstream bug https://github.com/linuxmint/Cinnamon/issues/3068 *** End of the template - remove these template lines *** -- System Information: Debian Release: jessie/sid APT prefers testing-updates APT policy: (500, 'testing-updates'), (500, 'testing') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.14-1-amd64 (SMP w/8 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 cinnamon-settings-daemon depends on: ii dconf-gsettings-backend [gsettings-backend] 0.20.0-2 ii gsettings-desktop-schemas3.12.2-1 ii libc62.19-7 ii libcairo21.12.16-2 ii libcanberra-gtk3-0 0.30-2 ii libcanberra0 0.30-2 ii libcinnamon-desktop4 2.2.3-2 ii libcolord2 1.2.1-1 ii libcups2 1.7.4-1 ii libdbus-glib-1-2 0.102-1 ii libfontconfig1 2.11.0-5 ii libgdk-pixbuf2.0-0 2.30.7-1 ii libglib2.0-0 2.40.0-3 ii libgnomekbd8 3.6.0-1 ii libgtk-3-0 3.12.2-1+b1 ii libgudev-1.0-0 208-6 ii liblcms2-2 2.6-3 ii libnotify4 0.7.6-2 ii libnspr4 2:4.10.6-1 ii libnss3 2:3.16.3-1 ii libpango-1.0-0 1.36.3-1 ii libpolkit-gobject-1-00.105-6 ii libpulse-mainloop-glib0 5.0-2 ii libpulse05.0-2 ii librsvg2-2 2.40.2-1 ii libsystemd-login0208-6 ii libupower-glib2 0.99.0-3 ii libwacom20.8-1 ii libx11-6 2:1.6.2-2 ii libxext6 2:1.3.2-1 ii libxfixes3 1:5.0.1-2 ii libxi6 2:1.7.2-1 ii libxklavier165.2.1-1 ii libxtst6 2:1.2.2-1 ii nemo-data2.2.3-2 Versions of packages cinnamon-settings-daemon recommends: ii pulseaudio 5.0-2 Versions of packages cinnamon-settings-daemon suggests: ii cinnamon [x-window-manager] 2.2.14-2 ii cinnamon-screensaver 2.2.3 ii metacity [x-window-manager] 1:2.34.13-1 ii muffin [x-window-manager]2.2.6-2 ii x11-xserver-utils7.7+3 ii xfwm4 [x-window-manager] 4.10.1-2 -- 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#755561: berusky2: FTBFS on mips*: undefined reference to `mmalloc'
Hello, I have investigated this a little bit more This seems not to be a compile issue. The reason for build failure on mips/mipsel is improper usage of inline functions. For example in a file: src/age/graph/mesh.cpp a functions mmalloc is used. Declaration of mmalloc function is included from src/age/utils/mem_alloc.h, but a definition of the mentioned function is in src/komat/mmalloc.h. mmalloc.h is not visible to mesh.cpp, and during compilation of mesh.cpp it is not possible to inline mmalloc function. So, object file mesh.o is created, but implementation of mmalloc function is missing. This is the reason of an error: mesh.cpp:59: undefined reference to `mmalloc' durign linking of berusky2on mips/mipsel with gcc-4.9. Using gcc-4.8 on mips, in some other object file (in this case Berusky3d_light.o) it seems that compiler decided not to inline mmalloc function. As a result, during creating of berusky2, linker is capable to resolve mmalloc symbol, because Berusky3d_light.o contains implementation of mmalloc function. In ./komat/Berusky3d_light.cpp definition of mmalloc function is visible from src/komat/mmalloc.h The same situation happens on amd64 with gcc-4.9, but in other object file: Keyframe.o. The point is that we could not guarantee that inline function mmalloc would not be inlined in some cases. For mesh.cpp which is not aware of mmalloc definition, implementation of mmalloc during linking is needed. Of course, we could use -fno-inline flag but, this seems to be wrong solution to me. The same usage of mmalloc function without a definition visible, is noticed in files: age/utils/mem_alloc.cpp age/graph/gext.cpp age/utils/utils.cpp The solution could be to include mmalloc.h in mem_alloc.h, so the definition of mmalloc function will be visible in all files where mmalloc function is used. The patch that contains this solution is attached. Could you please consider to include it? Best Regards, Dejan diff -uNr berusky2-0.10.orig/src/komat/mmalloc.h berusky2-0.10/src/komat/mmalloc.h --- berusky2-0.10.orig/src/komat/mmalloc.h 2013-03-03 23:38:39.0 + +++ berusky2-0.10/src/komat/mmalloc.h 2014-07-24 12:22:36.0 + @@ -32,6 +32,7 @@ #include stdlib.h #include string.h #include assert.h +#include mmalloc.h #ifdef __cplusplus extern C
Bug#755808:
file is attached.# This is a basic configuration that can easily be adapted to suit a standard
# installation. For more advanced options, see opendkim.conf(5) and/or
# /usr/share/doc/opendmarc/examples/opendmarc.conf.sample.
## AuthservID (string)
## defaults to MTA name
#
# AuthservID name
AuthservID binky.tuxfriends.net
## BaseDirectory (string)
## default (none)
##
## If set, instructs the filter to change to the specified directory using
## chdir(2) before doing anything else. This means any files referenced
## elsewhere in the configuration file can be specified relative to this
## directory. It's also useful for arranging that any crash dumps will be
## saved to a specific location.
#
# BaseDirectory /var/run/opendmarc
## ChangeRootDirectory (string)
## default (none)
##
## Requests that the operating system change the effective root directory of
## the process to the one specified here prior to beginning execution.
## chroot(2) requires superuser access. A warning will be generated if
## UserID is not also set.
#
# ChangeRootDirectory /var/chroot/opendmarc
## ForensicReports { true | false }
## default false
##
# ForensicReports false
ForensicReports true
ForensicReportsOnNone true
## IgnoreHosts path
## default (internal)
##
# IgnoreHosts /usr/local/etc/opendmarc/ignore.hosts
IgnoreHosts /etc/opendmarc.ignore.hosts
## IgnoreMailFrom domain[,...]
## default (none)
##
# IgnoreMailFrom example.com
## PidFile path
## default (none)
##
## Specifies the path to a file that should be created at process start
## containing the process ID.
##
#
PidFile /var/run/opendmarc.pid
## RejectFailures { true | false }
## default false
##
## Socket socketspec
## default (none)
##
## Specifies the socket that should be established by the filter to receive
## connections from sendmail(8) in order to provide service. socketspec is
## in one of two forms: local:path, which creates a UNIX domain socket at
## the specified path, or inet:port[@host] or inet6:port[@host] which creates
## a TCP socket on the specified port for the appropriate protocol family.
## If the host is not given as either a hostname or an IP address, the
## socket will be listening on all interfaces. This option is mandatory
## either in the configuration file or on the command line. If an IP
## address is used, it must be enclosed in square brackets.
#
# Socket inet:8893@localhost
Socket inet6:8893@[::1]
## SoftwareHeader { true | false }
## default false
##
## Causes the filter to add a DMARC-Filter header field indicating the
## presence of this filter in the path of the message from injection to
## delivery. The product's name, version, and the job ID are included in
## the header field's contents.
#
# SoftwareHeader false
## Syslog { true | false }
## default false
##
## Log via calls to syslog(3) any interesting activity.
#
# Syslog false
Syslog true
## SyslogFacility facility-name
## default mail
##
## Log via calls to syslog(3) using the named facility. The facility names
## are the same as the ones allowed in syslog.conf(5).
#
# SyslogFacility mail
## TemporaryDirectory path
## default /var/tmp
##
## Specifies the directory in which temporary files should be written.
#
# TemporaryDirectory /var/tmp
## TrustedAuthservIDs string
## default HOSTNAME
##
## Specifies one or more authserv-id values to trust as relaying true
## upstream DKIM and SPF results. The default is to use the name of
## the MTA processing the message. To specify a list, separate each entry
## with a comma. The key word HOSTNAME will be replaced by the name of
## the host running the filter as reported by the gethostname(3) function.
#
# TrustedAuthservIDs HOSTNAME
## UMask mask
## default (none)
##
## Requests a specific permissions mask to be used for file creation. This
## only really applies to creation of the socket when Socket specifies a
## UNIX domain socket, and to the HistoryFile and PidFile (if any); temporary
## files are normally created by the mkstemp(3) function that enforces a
## specific file mode on creation regardless of the process umask. See
## umask(2) for more information.
#
UMask 0002
## UserID user[:group]
## default (none)
##
## Attempts to become the specified userid before starting operations.
## The process will be assigned all of the groups and primary group ID of
## the named userid unless an alternate group is specified.
#
# UserID opendmarc
HistoryFile /var/run/opendmarc/history.dat
## MilterDebug (integer)
## default 0
##
## Sets the debug level to be requested from the milter library.
#
MilterDebug 0
RejectFailures true
CopyFailuresTo postmas...@tuxfriends.net
IgnoreMailFrom
oz42.eu,spamtrap.eu.org,tuxfriends.net,zaplinski.de,binky.tuxfriends.net
Bug#755890: marked as done (debian-policy: Some directory anf files from etc have unknown package pattern)
On Thu, Jul 24, 2014 at 10:30:29AM +, Debian Bug Tracking System wrote: Hi This is the directory and files wo package dependency: /etc/.java /etc/environment /etc/.pwd.lock /etc/subgid /etc/subuid Comamnd is dpkg -S files_on_siscussion Dear Corcodel, this is expected: packages can create configuration files through their maintainer scripts. I do not think this is the case for any of the files in the above list, except maybe /etc/environment. Corcodel, could you clarify your enquiry ? 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#755561: berusky2: FTBFS on mips*: undefined reference to `mmalloc'
Sorry, i sent a wrong patch. Here is a good one. In previous patch I accidentally included mmalloc.h in mmalloc.h :)diff -uNr berusky2-0.10.orig/src/age/utils/mem_alloc.h berusky2-0.10/src/age/utils/mem_alloc.h --- berusky2-0.10.orig/src/age/utils/mem_alloc.h 2013-03-03 23:38:40.0 + +++ berusky2-0.10/src/age/utils/mem_alloc.h 2014-07-24 13:35:08.0 + @@ -36,6 +36,7 @@ #include unistd.h #include limits.h #include log.h +#include mmalloc.h #define MMALLOC_DEBUG 1
Bug#755803: Bug#755895: [INTL:sv] Swedish strings for dictionaries-common debconf
On Thu, Jul 24, 2014 at 01:17:13PM +0200, Martin Bagge wrote: package: dictionaries-common severity: wishlist tags: patch l10n Please consider to add this file to translation of debconf. Thanks a lot for the updated translation. I was about to mail you the updated sv.po when I noticed your mail. I am merging both bug reports about the sv translation. I apologize for the inconveniences caused by a misunderstanding at my side. Regards, -- Agustin -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#755898: smstools: Great delays before messages are processed
Package: smstools Severity: important Version: 3.1.14-1 Tags: patch On a monitoring system with otherwie heavy I/O load (due to a large number of RRDs being updated on a regular basis), it was noticed that sending of a generated SMS was delayed for hours. Attaching gdb and strace to the stalled daemon revealed that it was stuck in a sync(2) call. Investigation of the source code showed that smsd makes frequent use of lock files as part of operations that involve reading from spool files and moving files around in its spool directories. After creating lock files, sync(2) is called which causes the kernel to write buffered file metadata modifications *for all filesystems*. This can have significatnt negative effects on overall filesystem performance. Lock files have no use after a system reboot and there seems to be no other part of smstools that is interested in the lock files' contents, therefore it is unclear why sync operation is needed at all. Even if it was important to preserve the lock file contents across system crashes, fsync(2) or fdatasync(2) would be the right calls to use. I suggest simply removing the sync() call from lockfile() in src/locking.c (that's why I set the patch tag.) As a quick and easy workaround here we have overridden the sync(2) call on the affected system by running smsd with the eatmydata shared library preloaded. This has solved our latency issue. Cheers, -Hilko -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#755561: berusky2: FTBFS on mips*: undefined reference to `mmalloc'
On 24.07.2014 13:30, Dejan Latinovic wrote: Hello, I have investigated this a little bit more This seems not to be a compile issue. [...] The solution could be to include mmalloc.h in mem_alloc.h, so the definition of mmalloc function will be visible in all files where mmalloc function is used. The patch that contains this solution is attached. Could you please consider to include it? Hi Dejan, thanks for your patch! I will forward it to the developer of Berusky2. Just saw your second e-mail. I wanted to point out the same to you. :) Thanks again Cheers, Markus signature.asc Description: OpenPGP digital signature
Bug#755899: src:pth: update libtool.m4 and configure to fix FTBFS on ppc64el
Package: src:pth
Version: 2.0.7-19
Severity: normal
Tags: patch
Dear Maintainer,
While trying to build pth on ppc64el, it failed, due to missing entry
about powerpc64le in libtool.m4 and configure files.
Please consider this patch to fulfill that need.
Thanks in advance,
Erwan.
-- System Information:
Debian Release: jessie/sid
APT prefers unstable
APT policy: (500, 'unstable')
Architecture: ppc64el (ppc64le)
Kernel: Linux 3.13-1-powerpc64le (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
--- a/debian/patches/powerpc64le.diff 1970-01-01 00:00:00.0 +
+++ b/debian/patches/powerpc64le.diff 2013-12-21 18:07:29.0 +
@@ -0,0 +1,56 @@
+Index: b/configure
+===
+--- a/configure
b/configure
+@@ -4383,7 +4383,10 @@
+ x86_64-*linux*)
+ LD=${LD-ld} -m elf_i386
+ ;;
+-ppc64-*linux*|powerpc64-*linux*)
++ powerpc64le-*)
++ LD=${LD-ld} -m elf32lppclinux
++ ;;
++ powerpc64-*)
+ LD=${LD-ld} -m elf32ppclinux
+ ;;
+ s390x-*linux*)
+@@ -4399,7 +4402,10 @@
+ x86_64-*linux*)
+ LD=${LD-ld} -m elf_x86_64
+ ;;
+-ppc*-*linux*|powerpc*-*linux*)
++ powerpcle-*)
++ LD=${LD-ld} -m elf64lppc
++ ;;
++ powerpc-*)
+ LD=${LD-ld} -m elf64ppc
+ ;;
+ s390*-*linux*)
+Index: b/libtool.m4
+===
+--- a/libtool.m4
b/libtool.m4
+@@ -533,7 +533,10 @@
+ x86_64-*linux*)
+ LD=${LD-ld} -m elf_i386
+ ;;
+-ppc64-*linux*|powerpc64-*linux*)
++ powerpc64le-*)
++ LD=${LD-ld} -m elf32lppclinux
++ ;;
++ powerpc64-*)
+ LD=${LD-ld} -m elf32ppclinux
+ ;;
+ s390x-*linux*)
+@@ -549,7 +552,10 @@
+ x86_64-*linux*)
+ LD=${LD-ld} -m elf_x86_64
+ ;;
+-ppc*-*linux*|powerpc*-*linux*)
++ powerpcle-*)
++ LD=${LD-ld} -m elf64lppc
++ ;;
++ powerpc-*)
+ LD=${LD-ld} -m elf64ppc
+ ;;
+ s390*-*linux*)
--- 2.0.7-19/debian/patches/series 2013-07-08 12:35:38.0 +
+++ 2.0.7-19ubuntu1/debian/patches/series 2013-12-21 18:04:39.0 +
@@ -5,3 +5,4 @@
05-linux_3.patch
06-ldflags.patch
07-test_uctx_fix.patch
+powerpc64le.diff
Bug#755900: gnuplot.info has multiple copies of some nodes!
Package: gnuplot-doc Version: 4.6.0-8 /usr/share/info/gnuplot.info.gz contains multiple copies of (at least) the tgif node (as `tgif' 4.1.0.58 and `tgif_' 4.1.0.59) and the x11 node (as `x11' 4.1.0.68 and `x11_' 4.1.0.69) and the xlib node (as `xlib' 4.1.0.70 and `xlib_' 4.1.0.71). Ian. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#755901: pythonqt: Some Qt classes are not available in python
Source: pythonqt Version: 2.1.0~svn247-1 Severity: normal Dear Maintainer, Some of the Qt classes are not available in python when using the debian package. For example, the PythonQt.QtUiTools.QUiLoader class is missing. CMakeLists.txt defines a PythonQt_Wrap_QtAll option that defaults to OFF. The description is Make all Qt components available in python. I imagine setting this to ON could help with this (though xmlpatterns classes are forcefully excluded). Cheers, Florian -- System Information: Debian Release: jessie/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 3.14-2-amd64 (SMP w/1 CPU core) Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#755791: dictionaries-common: [INTL:eo] Esperanto po-debconf translation
Ok, no problem, here is an up-to-date translation for it.
Kind regards,
Felipe Castro
2014-07-24 8:16 GMT-03:00 Agustin Martin agmar...@debian.org:
On Wed, Jul 23, 2014 at 07:55:54AM -0300, Felipe E. F. de Castro wrote:
Package: dictionaries-common
Version: 1.23.8
Severity: wishlist
Tags: patch
Dear Maintainer,
Please update the Esperanto translation, see the po-file attached.
Thanks for the translation.
Due to a misunderstanding at my side a template was still marked as
non-translatable.
I am attaching an updated eo.po file including your changes, with that
template enabled for translation. I'd greatly appeciate if you could
handle it too.
I apologize for the inconveniences.
Regards,
--
Agustin
# Translation to Esperanto
# Copyright (C) 2007, 2011, 2014 Free Software Foundation, Inc.
# Serge Leblanc serge.lebl...@wanadoo.fr, 2007.
# Felipe Castro fef...@gmail.com, 2011, 2014.
msgid
msgstr
Project-Id-Version: dictionaries-common\n
Report-Msgid-Bugs-To: dictionaries-com...@packages.debian.org\n
POT-Creation-Date: 2014-07-24 11:53+0200\n
PO-Revision-Date: 2014-07-24 09:11-0300\n
Last-Translator: Felipe Castro fef...@gmail.com\n
Language-Team: Esperanto debian-l10n-espera...@lists.debian.org\n
Language: eo\n
MIME-Version: 1.0\n
Content-Type: text/plain; charset=UTF-8\n
Content-Transfer-Encoding: 8bit\n
X-Generator: Poedit 1.5.4\n
#. Type: error
#. Description
#. TRANSLATORS: DO NOT TRANSLATE variable names such as ${question}
#: ../dictionaries-common.templates:2001
msgid Possible debconf database corruption
msgstr Ebla misrompo en la datumbazo debconf
#. Type: error
#. Description
#. TRANSLATORS: DO NOT TRANSLATE variable names such as ${question}
#: ../dictionaries-common.templates:2001
msgid The setting for \${question}\ is missing, but packages providing candidates are installed: \${class_packages}\.
msgstr Mankas difino por \${question}\, sed pakoj provizantaj kandidatojn estas instalitaj: \${class_packages}\.
#. Type: error
#. Description
#. TRANSLATORS: DO NOT TRANSLATE variable names such as ${question}
#: ../dictionaries-common.templates:2001
msgid This may be due to corruption in the debconf database. See \/usr/share/doc/dictionaries-common/README.problems\ on \Debconf database corruption\.
msgstr Tio ĉi povas esti pro misrompo en la datumbazo debconf. Konsultu \/usr/share/doc/dictionaries-common/README.problems\ pri \Debconf database corruption\.
#. Type: error
#. Description
#. TRANSLATORS: DO NOT TRANSLATE variable names such as ${question}
#: ../dictionaries-common.templates:2001
msgid In this case, running \/usr/share/debconf/fix_db.pl\ can help to put the debconf database in a consistent state.
msgstr En tiu ĉi okazo, lanĉo de \/usr/share/debconf/fix_db.pl\ povas helpi porti la datumbazon debconf al koĥera stato.
#. Type: error
#. Description
#. TRANSLATORS: DO NOT TRANSLATE variable names such as ${question}
#: ../dictionaries-common.templates:2001
msgid Some questions are likely to be asked after this message in order to leave the dictionaries system in a (provisionally) working state.
msgstr Kelkaj demandoj probable estos farataj post tiu ĉi mesaĝo por lasi la vortar-sistemon en (provizore) funkcianta stato.
#. Type: error
#. Description
#. TRANSLATORS: DO NOT TRANSLATE variable names such as ${value}
#: ../dictionaries-common.templates:3001
msgid Invalid configuration value for default dictionary
msgstr Malvalida agord-valoro por apriora vortaro
#. Type: error
#. Description
#. TRANSLATORS: DO NOT TRANSLATE variable names such as ${value}
#: ../dictionaries-common.templates:3001
msgid An invalid value has been found for a configuration setting for dictionaries-common. \${value}\ does not correspond to any installed package on the system.
msgstr Malvalida valoro estis trovata por difina agordo por dictionaries-common. \${value}\ ne korespondas al iu ajn instalita pako en la sistemo.
#. Type: error
#. Description
#. TRANSLATORS: DO NOT TRANSLATE variable names such as ${value}
#: ../dictionaries-common.templates:3001
msgid This is usually caused by previous problems during package installation, where the package providing \${value}\ was selected for installation but finally not installed because of errors in other packages.
msgstr Tio ordinare okazas pro antaŭaj malfacilaĵoj dum instalo de pako,kie la pako provizanta \${value}\ estis elektata por instalo sed finfine ne estis instalata pro eraroj en aliaj pakoj.
#. Type: error
#. Description
#. TRANSLATORS: DO NOT TRANSLATE variable names such as ${value}
#: ../dictionaries-common.templates:3001
msgid To fix this error, reinstall (or install) the package that provides \${value}\. Then, if you don't want that package on this system, remove it, which will also delete this configuration setting. A menu of choices will be shown after this message in order to leave the system in a working state until you fix the problem.
msgstr Por korektigi tiun ĉi eraron, bonvolu reinstali (aŭ instali) la pakon
Bug#755902: pkg-config-multi-arch-wrong-dir: arm-linux-gnueabi wrongfully matches arm-linux-gnueabihf
Package: lintian
Version: 2.5.25
Severity: normal
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Dear Maintainer,
building a package on armhf I noticed that lintian wrongfully reports the
following contents as a match for pkg-config-multi-arch-wrong-dir:
prefix=/usr
exec_prefix=${prefix}
libdir=${exec_prefix}/lib/arm-linux-gnueabihf
includedir=${prefix}/include
Name: rabbitmq-c
Description: An AMQP 0-9-1 client library
Version: 0.5.0
URL: https://github.com/alanxz/rabbitmq-c
Requires.private: openssl
Libs: -L${libdir} -lrabbitmq
Libs.private: rt;-lpthread
CFlags: -I${includedir}
The message is:
usr/lib/arm-linux-gnueabihf/pkgconfig/librabbitmq.pc full text contains
architecture specific dir arm-linux-gnueabi
It seems that the regex matching for arm-linux-gnueabi also matches
arm-linux-gnueabihf at the libdir=... line.
I'd propose to extend all the regex with something like $(?:\/|$) at the end
to only match full paths.
Cheers,
Michael
- -- System Information:
Debian Release: jessie/sid
APT prefers unstable
APT policy: (500, 'unstable'), (1, 'experimental')
Architecture: armhf (armv7l)
Kernel: Linux 3.16-rc5-armmp (SMP w/4 CPU cores)
Locale: LANG=en_DK.utf8, LC_CTYPE=en_DK.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Versions of packages lintian depends on:
ii binutils 2.24.51.20140709-1
ii bzip2 1.0.6-5
ii diffstat 1.58-1
ii file 1:5.19-1
ii gettext0.18.3.2-4
ii hardening-includes 2.5
ii intltool-debian0.35.0+20060710.1
ii libapt-pkg-perl0.1.29+b1
ii libarchive-zip-perl1.37-2
ii libclass-accessor-perl 0.34-1
ii libclone-perl 0.37-1
ii libdpkg-perl 1.17.10
ii libemail-valid-perl1.194-1
ii libfile-basedir-perl 0.03-1
ii libipc-run-perl0.92-1
ii liblist-moreutils-perl 0.33-2
ii libparse-debianchangelog-perl 1.2.0-1
ii libtext-levenshtein-perl 0.09-1
ii libtimedate-perl 2.3000-2
ii liburi-perl1.64-1
ii man-db 2.6.7.1-1
ii patchutils 0.3.3-1
ii perl [libdigest-sha-perl] 5.18.2-7
ii t1utils1.37-2
Versions of packages lintian recommends:
ii libautodie-perl 2.25-1
ii libperlio-gzip-perl 0.18-3
ii perl-modules [libautodie-perl] 5.18.2-7
Versions of packages lintian suggests:
pn binutils-multiarch none
ii dpkg-dev 1.17.10
ii libhtml-parser-perl3.71-1+b1
pn libtext-template-perl none
pn libyaml-perl none
ii xz-utils 5.1.1alpha+20120614-2
- -- no debconf information
-BEGIN PGP SIGNATURE-
Version: GnuPG v1
iQIcBAEBCgAGBQJT0PjyAAoJEGlMre9Rx7W2I3MQAJTq3hYpswYBKwryqY+ieG4w
C9qjLovCixdEaSbXN30NZtfBoE/gpl1sE+t5ZY5PbKavkF0rmRQVUT25H9uYFBK/
i3Hv98z0auJp8+rZ9fLAjBoykaAsjF514rf+KuTf924TX+6wOlKCD67SRsI9SboC
mQ4WAMr4woBp0+zFdLRk8l8+3DcDxeWHWaZZZlScMIs8cpq8PpCOIxl9M99EX2s1
HNHfRpGsXCnaFjQ5BT07u7gV4jj3HT4ixbVkKnKQYaLzt7XacXL+JWrpD8ztu7kA
xcwrvSqwCFcgIUhBxIsqNE+q25jyqerqAtWSNbiAxbA1J5awCP1Qy5G0kYRYKs1B
7x/2tVTvrmANqwAeuVTHq9UJmSWVRLAj8A21kvUEI7MRZrb6A/c8X3drYDECYd/Q
9Gg+kaqchkQKd1wgSdsHOmc2PQAtfXRl/aLeYwfFkGDYnJgVwMxFxZzkHE0MulpZ
arLPJwPE8/jv/aKYj4EZVmZSs09Rbr0uWIPXwzSlc1K8WObK70nZqzLxCVWkv8LU
raSI5capklV64KjLOJiZOQoISYWt3YJPTMVai6PKkxXrlXoIfTDTq/ZeHRq9BDwi
hEXzLjU6rTRsxNhTJ+ResztWJcehMKiQwq8iJWqncHB6JThwabqI0bpIfKH6mTdt
omywZdUWOtPJC2mjkq2y
=DA9b
-END PGP SIGNATURE-
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#755904: libpam-systemd: error in log after upgrade
Package: libpam-systemd Version: 208-6 Severity: minor Dear Maintainer, After upgrade, I get lots of error in auth.log: Jul 24 11:45:17 host sshd[23128]: pam_systemd(sshd:session): Failed to create session: Invalid argument I think I encountered the same behaviour previously, and it was solved by rebooting. I have not seen any correlated issue. Thanks, Benoit -- System Information: Debian Release: jessie/sid APT prefers testing APT policy: (990, 'testing'), (500, 'unstable'), (500, 'stable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.14-1-amd64 (SMP w/4 CPU cores) Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages libpam-systemd depends on: ii libc6 2.19-7 ii libcap21:2.22-1.2 ii libdbus-1-31.8.6-1 ii libpam-runtime 1.1.8-3 ii libpam0g 1.1.8-3 ii multiarch-support 2.19-7 ii systemd208-6 ii systemd-sysv 208-6 libpam-systemd recommends no packages. libpam-systemd 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#755903: Have to invoke gnuplot with two copies of same input file
Package: gnuplot Version: 4.6.0-8 $ gnuplot contrib.runes $ wc -l contrib.ps 595 contrib.ps $ gnuplot contrib.runes contrib.runes $ wc -l contrib.ps 765 contrib.ps $ cat contrib.runes set terminal epscairo size 5.0, 3.5 set output 'contrib.ps' set xrange [1311264120:1405958544] set yrange [0:800] set xdata time set timefmt %s set style fill solid 0.5 plot 'contrib.gnuplot' using 1:2 with boxes title 'osstest loc by author date' $ The output file from the first invocation does not actually contain the graph data. I have searched the whole manual for the word `output' and nothing seems to suggest what I'm doing anything wrong. I have seen similar effects with other `set terminal' options. While I haven't reproduced that systematically, I don't think this is simply a bug in the epscairo terminal driver. The file contrib.gnuplot is attached, as are the two .ps files. Ian. 1260748800 442 1263427200 726 1266105600 529 1268524800 186 1271199600 1819 1273791600 470 127647 6 1279062000 97 1281740400 204 1284418800 660 1287010800 1062 1289692800 2315 1292284800 2418 1294963200 430 1297641600 177 1300060800 103 1302735600 421 1308006000 43 1310598000 129 1313276400 376 1315954800 97 1318546800 4 1323820800 18 1326499200 48 1329177600 207 1331683200 88 1334358000 250 133695 197 1339628400 2 1342220400 2 1344898800 5 1350169200 23 1352851200 1931 1355443200 3 136080 135 1363219200 581 1365894000 477 1368486000 2 1371164400 6 1373756400 2 1376434800 1 1379113200 6 1381705200 569 1384387200 428 1386979200 201 1389657600 230 1392336000 667 1394755200 316 139743 539 1400022000 495 1402700400 677 1405292400 771 1407970800 212 t.ps Description: PostScript document u.ps Description: PostScript document
Bug#755890: marked as done (debian-policy: Some directory anf files from etc have unknown package pattern)
Le Thu, Jul 24, 2014 at 01:43:32PM +0200, Bill Allombert a écrit : On Thu, Jul 24, 2014 at 10:30:29AM +, Debian Bug Tracking System wrote: This is the directory and files wo package dependency: /etc/.java /etc/environment /etc/.pwd.lock /etc/subgid /etc/subuid Comamnd is dpkg -S files_on_siscussion this is expected: packages can create configuration files through their maintainer scripts. I do not think this is the case for any of the files in the above list, except maybe /etc/environment. Hi Bill, Codesesarch to the rescue: * http://codesearch.debian.net/search?q=%2Fetc%2F.java java-common_0.52/debian/java-common.postinst:7 case $1 in configure) [ -d /etc/.java ] || mkdir -m 755 /etc/.java [ -d /etc/.java/.systemPrefs ] || mkdir -m 755 /etc/.java/.systemPrefs if [ ! -f /etc/.java/.systemPrefs/.system.lock ]; then * http://codesearch.debian.net/search?q=%2Fetc%2Fsubgid shadow_1:4.2-2/debian/changelog:76 * Update documentation of UMASK: Explain that USERGROUPS_ENAB will modify this default for UPGs. (Closes: #583971) * login.postinst: install a default /etc/subuid and /etc/subgid * fix installation of setuid/setgid/newuidmap/newgid/map man pages shadow_1:4.2-2/debian/login.postinst:36 fi if [ ! -e /etc/subgid ]; then touch /etc/subgid chown root:root /etc/subgid For /etc/.pwd.lock, it does not seem to be created at installation time, but the file is not unknown to glibc and pam, and the Policy does not mandate that /etc shall be read-only. * http://codesearch.debian.net/search?q=%2Fetc%2F.pwd.lock glibc_2.19-7/shadow/lckpwdf.c:32 /* Name of the lock file. */ #define PWD_LOCKFILE /etc/.pwd.lock /* How long to wait for getting the lock before returning with an pam_1.1.8-3/modules/pam_unix/lckpwdf.-c:33 #endif #define LOCKFILE /etc/.pwd.lock #define TIMEOUT 15 Cheers, -- Charles -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#755904: libpam-systemd: error in log after upgrade
Hi, Am 24.07.2014 14:10, schrieb Benoit Friry: Package: libpam-systemd Version: 208-6 Severity: minor Dear Maintainer, After upgrade, I get lots of error in auth.log: Jul 24 11:45:17 host sshd[23128]: pam_systemd(sshd:session): Failed to create session: Invalid argument Is systemd-logind running? What's the output of loginctl before and after you login via ssh? Could you edit /etc/pam.d/common-session and append a debug=true to the session optional pam_systemd.so line This should give you a more verbose log. Do you get anything in the journal? Specifically by systemd-logind? You can filter it via journalctl --unit systemd-logind.service Michael -- Why is it that all of the instruments seeking intelligent life in the universe are pointed away from Earth? signature.asc Description: OpenPGP digital signature
Bug#755905: segfaults after update
Package: iceweasel
Version: 31.0-1
Hi,
Since I've updated the Iceweasel 31, it segfaults all the time. Here's
one of the traces I've got, but I'm unsure if it's the right one, as
typing cont didn't terminate the process.
--
Cheers,
Andrew
Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread 0xa2dffb40 (LWP 28756)]
0xb4e46df3 in readByte (this=optimized out) at /build/iceweasel-3vlBEX/iceweasel-31.0/js/src/jit/CompactBuffer.h:57
57 /build/iceweasel-3vlBEX/iceweasel-31.0/js/src/jit/CompactBuffer.h: No such file or directory.
(gdb) bt full
#0 0xb4e46df3 in readByte (this=optimized out) at /build/iceweasel-3vlBEX/iceweasel-31.0/js/src/jit/CompactBuffer.h:57
No locals.
#1 readVariableLength (this=optimized out) at /build/iceweasel-3vlBEX/iceweasel-31.0/js/src/jit/CompactBuffer.h:40
val = 0
shift = 0
#2 readUnsigned (this=optimized out) at /build/iceweasel-3vlBEX/iceweasel-31.0/js/src/jit/CompactBuffer.h:72
No locals.
#3 read (this=synthetic pointer) at /build/iceweasel-3vlBEX/iceweasel-31.0/js/src/jit/x86/Assembler-x86.cpp:66
No locals.
#4 js::jit::Assembler::TraceJumpRelocations (trc=0xa30b9204, code=0xa2b942b8, reader=...)
at /build/iceweasel-3vlBEX/iceweasel-31.0/js/src/jit/x86/Assembler-x86.cpp:86
iter = {reader_ = {
buffer_ = 0x9f272418 \004\225\b\363\n=\f\001\024_\026\251\026W\032\361\034\035\036e\036\311\036%\\375\\253$\355$w\237\t(G(w(\341(K,\225,!.\177\060\311\060\341\062\347\070\023:[:\277:;c\263@}B\343BWD\aHQH]J\341J?N\211N\aV_X\251X\365\\=^\245`\377`\261r\333r\atKt\221t\337t9v#x\315|\033~i~\317~o\200\363\200W\202\227\202M\204G\210\207\212{\214\375\214��\377\220\275\222!\226��\261\230\357\230L\230g\002y\002\273\002\323\002\205\004\017\006M\006+\b\305\b\251\n{\f\223\f\335\f\375\f)\016\177\016\227\016\065\020\021\022)\022\211...,
end_ = 0x9f2724b5 L\230g\002y\002\273\002\323\002\205\004\017\006M\006+\b\305\b\251\n{\f\223\f\335\f\375\f)\016\177\016\227\016\065\020\021\022)\022\211\022\061\024\025\026\r\032\331\034\005\036M\036\261\036\333 \345\\223$\a[\225\361[(\001,\267,Q.50+292\313\062Q4o4!6\247\066\275\066\311\066\341\066\035\070\203\070\243\070\317\070\373\070C:\247:?\361\367@eB\221B\313B\207D\275F\203H\225H\327H\vJwJ\021L\365L\003P\031P%PcP9ROR[R\231R\233T7V\025X7ZUZkZwZ\265Z\277\\\335\\%^[`3b_b\247b\357b\005d\021d_d...}, offset_ = optimized out}
#5 0xb4d8d944 in js::jit::JitCode::trace (this=0xa2b942b8, trc=0xa30b9204) at /build/iceweasel-3vlBEX/iceweasel-31.0/js/src/jit/Ion.cpp:733
start = optimized out
reader = {
buffer_ = 0x9f272417 \311\004\225\b\363\n=\f\001\024_\026\251\026W\032\361\034\035\036e\036\311\036%\\375\\253$\355$w\237\t(G(w(\341(K,\225,!.\177\060\311\060\341\062\347\070\023:[:\277:;c\263@}B\343BWD\aHQH]J\341J?N\211N\aV_X\251X\365\\=^\245`\377`\261r\333r\atKt\221t\337t9v#x\315|\033~i~\317~o\200\363\200W\202\227\202M\204G\210\207\212{\214\375\214��\377\220\275\222!\226��\261\230\357\230L\230g\002y\002\273\002\323\002\205\004\017\006M\006+\b\305\b\251\n{\f\223\f\335\f\375\f)\016\177\016\227\016\065\020\021\022)\022...,
end_ = 0x9f2724b5 L\230g\002y\002\273\002\323\002\205\004\017\006M\006+\b\305\b\251\n{\f\223\f\335\f\375\f)\016\177\016\227\016\065\020\021\022)\022\211\022\061\024\025\026\r\032\331\034\005\036M\036\261\036\333 \345\\223$\a[\225\361[(\001,\267,Q.50+292\313\062Q4o4!6\247\066\275\066\311\066\341\066\035\070\203\070\243\070\317\070\373\070C:\247:?\361\367@eB\221B\313B\207D\275F\203H\225H\327H\vJwJ\021L\365L\003P\031P%PcP9ROR[R\231R\233T7V\025X7ZUZkZwZ\265Z\277\\\335\\%^[`3b_b\247b\357b\005d\021d_d...}
trc = 0xa30b9204
this = 0xa2b942b8
#6 0xb4cdec05 in MarkChildren (code=0xa2b942b8, trc=0xa30b9204) at /build/iceweasel-3vlBEX/iceweasel-31.0/js/src/gc/Marking.cpp:1290
No locals.
#7 js::GCMarker::processMarkStackOther (this=0xa30b9204, tag=5, addr=2730050232) at /build/iceweasel-3vlBEX/iceweasel-31.0/js/src/gc/Marking.cpp:1461
No locals.
#8 0xb4ce1c43 in processMarkStackTop (budget=..., this=0xa30b9204) at /build/iceweasel-3vlBEX/iceweasel-31.0/js/src/gc/Marking.cpp:1499
vp = optimized out
end = optimized out
obj = optimized out
addr = optimized out
tag = optimized out
#9 js::GCMarker::drainMarkStack (this=0xa30b9204, budget=...) at /build/iceweasel-3vlBEX/iceweasel-31.0/js/src/gc/Marking.cpp:1608
No locals.
---Type return to continue, or q return to quit---
#10 0xb4ecadae in DrainMarkStack (phase=optimized out, sliceBudget=..., rt=optimized out) at /build/iceweasel-3vlBEX/iceweasel-31.0/js/src/jsgc.cpp:3841
No locals.
#11 IncrementalCollectSlice (rt=0x9f2724b5, rt@entry=0xa30b9000, budget=0, reason=JS::gcreason::DOM_WORKER, gckind=js::GC_SHRINK)
at /build/iceweasel-3vlBEX/iceweasel-31.0/js/src/jsgc.cpp:4404
sliceBudget = {deadline = 9223372036854775807, counter = 2147482532, static CounterReset = 1000, static Unlimited = 0}
copy = {runtime = 0xa30b9000}
slice =
Bug#755906: ITP: toposort -- topological sort algorithm in Python
Package: wnpp Owner: Luca Falavigna dktrkr...@debian.org Severity: wishlist * Package name: toposort Version : 1.0 Upstream Author : Eric V. Smith * URL : https://bitbucket.org/ericvsmith/toposort * License : Apache-2.0 Programming Lang: Python Description : topological sort algorithm in Python In computer science, a topological sort (sometimes abbreviated topsort or toposort) or topological ordering of a directed graph is a linear ordering of its vertices such that for every directed edge uv from vertex u to vertex v, u comes before v in the ordering. This package provides this algorithm for Python. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#755907: pax-utils: lddtree shows wrong libraries for 32-bits objects on a 64-bit machine
Package: pax-utils
Version: 0.2.3-2
Severity: important
Dear Maintainer,
I have been trying to use lddtree on a 32-bits binary (executable or library is
irrelevant) but the output is completely wrong.
Unlike ldd which displays the correct 32-bits dependencies, lddtree shows the
64-bits versions of them making it unusable for these kind of objects.
Here are simple repro steps:
$ cat main.c
int main(void)
{
return 0;
}
$ cc -m32 main.c -o 32.out
$ file 32.out
32.out: ELF 32-bit LSB executable, Intel 80386, version 1 (SYSV), dynamically
linked (uses shared libs), for GNU/Linux 2.6.32,
BuildID[sha1]=b566e1cb538e8bdfe845a0d5ca659109f7a810df, not stripped
$ ldd 32.out
linux-gate.so.1 (0xf777f000)
libc.so.6 = /lib32/libc.so.6 (0xf75a8000)
/lib/ld-linux.so.2 (0xf778)
$ lddtree 32.out
32.out = ./32.out (interpreter = /lib/ld-linux.so.2)
libc.so.6 = /lib/x86_64-linux-gnu/libc.so.6
ld-linux-x86-64.so.2 = /lib/x86_64-linux-gnu/ld-linux-x86-64.so.2
-- System Information:
Debian Release: jessie/sid
APT prefers unstable
APT policy: (990, 'unstable'), (980, 'stable-updates'), (980, 'testing'),
(970, 'stable'), (90, 'experimental')
Architecture: amd64 (x86_64)
Kernel: Linux 3.14-1-amd64 (SMP w/4 CPU cores)
Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Versions of packages pax-utils depends on:
ii libc62.19-7
ii libcap2 1:2.24-1
pax-utils recommends no packages.
Versions of packages pax-utils suggests:
pn paxctl none
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#748994: (no subject)
hi Guillem, On 07/23/2014 10:52 PM, Guillem Jover wrote: Hi! On Wed, 2014-07-23 at 16:22:44 -0300, Breno Leitao wrote: Did you get a chance to look at this defect? libbsd is still failing to build on ppc64el, as you can see in the following build log: http://ftp.unicamp.br/pub/ppc64el/debian/buildd-upstream/build_logs/logs/libbsd_0.6.0-2_ppc64el.build This package (libbsd) is currently the major offender for ppc64el, since a lot of packages depends on it. The previous one, openssl(Bug#745657). just accepted the ppc64el patches earlier today. I would really appreciate if you can submit a newer version with this problem fixed. Sorry I dropped the ball on this, I'm in the process to finish the new upstream release, so hopefully I'll have a new version during this week, also uploaded to Debian. No worries, that works. Thank you! -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#755908: dbconfig-common: fails to purge active PostgreSQL database
Package: dbconfig-common Version: 1.8.47+nmu1 Severity: normal Hi, I’m working on packaging a web application that uses PostgreSQL (well, will do once I finish converting it from SQLite2 to it). When I 'apt-get purge packagename', dbconfig-common tries to remove the database (as I tell it to), but fails to do that. I discovered the reason for this is that I cannot purge the database manually “the easy way” either: postgres=# DROP DATABASE simkolab; ERROR: database simkolab is being accessed by other users DETAIL: There is 1 other session using the database. Some related reading: - http://stackoverflow.com/a/5109190/2171120 - http://stackoverflow.com/a/7489673/2171120 The reason here is that Apache has not yet been restarted/reloaded and that one of its children is holding the connection open. I’m currently trying to shuffle the dbc_go call in postrm in between do_webserver_config() / apache2_invoke disconf and the rest of the cleanup, but that means duplicating it, etc. It would be really nice if dbconfig-common could be patched to tear down a database using the method shown in the above SO link: 1) REVOKE CONNECT ON DATABASE dbname FROM PUBLIC, username; 2) SELECT pg_terminate_backend(procpid) FROM pg_stat_activity WHERE -- don't kill my own connection! procpid pg_backend_pid() -- don't kill the connections to other databases AND datname = 'database_name' ; -- for psql 8.4 to 9.1 -- in psql 9.2 the column procpid was renamed to pid 3) DROP DATABASE dbname; Might be useful to have the psql maintainers say something to this as well; perhaps there’s an easier way? -- System Information: Debian Release: jessie/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.14-2-amd64 (SMP w/2 CPU cores) Locale: LANG=C, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/lksh Versions of packages dbconfig-common depends on: ii debconf [debconf-2.0] 1.5.53 ii ucf3.0030 dbconfig-common recommends no packages. Versions of packages dbconfig-common suggests: ii postgresql-client-9.3 [postgresql-client] 9.3.4-2 -- debconf information: dbconfig-common/db/basepath: * dbconfig-common/remember-admin-pass: false * dbconfig-common/remote-questions-default: false dbconfig-common/db/dbname: dbconfig-common/purge: false dbconfig-common/mysql/admin-user: root dbconfig-common/internal/skip-preseed: false dbconfig-common/pgsql/authmethod-admin: ident dbconfig-common/internal/reconfiguring: false dbconfig-common/install-error: abort dbconfig-common/dbconfig-upgrade: true dbconfig-common/upgrade-error: abort dbconfig-common/missing-db-package-error: abort dbconfig-common/passwords-do-not-match: dbconfig-common/remote/port: dbconfig-common/db/app-user: dbconfig-common/mysql/method: unix socket dbconfig-common/upgrade-backup: true dbconfig-common/database-type: dbconfig-common/remove-error: abort dbconfig-common/remote/host: dbconfig-common/pgsql/changeconf: false dbconfig-common/pgsql/no-empty-passwords: dbconfig-common/pgsql/admin-user: postgres dbconfig-common/dbconfig-remove: true dbconfig-common/pgsql/method: unix socket dbconfig-common/dbconfig-reinstall: false dbconfig-common/pgsql/manualconf: dbconfig-common/pgsql/no-user-choose-other-method: dbconfig-common/dbconfig-install: true dbconfig-common/pgsql/authmethod-user: dbconfig-common/pgsql/revertconf: false dbconfig-common/remote/newhost: -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#753887: qemu-system-x86 - Two ide-hd/-cd devices are assigned to the same bus
Control: severity -1 wishlist Control: tag -1 + confirmed upstream 05.07.2014 23:08, Bastian Blank wrote: Package: qemu-system-x86 Version: 2.0.0+dfsg-6+b1 Severity: normal qemu allows definition of several devices with type ide-hd or ide-cd. All of them are assigned to the same bus, which can only hold one device at a time. Fails: | -device ide-cd,drive=ide0 | -device ide-cd,drive=ide1 Works: | -device ide-cd,drive=ide0,bus=ide0 | -device ide-cd,drive=ide1,bus=ide1 I'm highly skeptical that upstream will try to fix this. These (including -hda -cdrom etc) are shortcuts for simple cases, more complex cases should use more complete definitions, and everyone is moved to libvirt anyway, which specifies everything explicitly. 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#755518: laptop-mode-tools: USB Autosuspend + LVM2 filesystems = failed boot
On Wed, 23 Jul 2014, Ritesh Raj Sarraf wrote: On 07/22/2014 07:55 PM, Matthew Gabeler-Lee wrote: Changing the last line of /lib/udev/lmt-udev from: ) to: ) /dev/null /dev/null 21 detaches from those pipes, fixing the problem and producing a normal boot. One fact that it never broke with the traditional SysV init justifies that the problem lies in systemd. Maybe. I could try putting sysvinit back on this system to see what happens. I think it will still cause problems there, but the severetiy may be lower. The sysvinit scripts still wait for udev to settle, which would still trip on this. The result, I think, would be a 2 minute delay in the boot process, and then a race to see if udev could catch up and create the device nodes before the init scripts try to mount the filesystems. If this race is lost, I believe sysvinit would drop into an emergency recovery shell, whereas systemd tries to limp along, and does mount the filesystems when they show up (though many other aspects of startup fail and stay failed). systemd does have new ideas, which may be good for us, but they expect changes in all other programs. If that is the case here, and the changes are not going to break elsewhere, I may look into it. I think the core of the problem here is not really with systemd, but with the interaction between udev and LMT. I suppose you could consider udev part of systemd to some extent now, but ... Give me your thoughts... How should this be fixed. LMT (laptop-mode-tools) gets triggered on kernel events. Now those events could come through udev or anyone else. In your case, it is through udev. Will increasing the timeout for lmt-udev solve the problem ? Can you run some tests and conclude that ? Actually, decreasing the timeout would help the boot process at the expense of LMT not getting to process the devices at boot. Increasing the timeout would not help, might make things worse. The core of the problem, I think, is that lmt-udev is clearly intending to detach itself from the udev daemon that spawns it, but is failing to do so. I think the strategy it uses may have worked with prior versions of udev, but changes in udev mean that the strategy is no longer sufficient. I don't think those changes in udev were accidental, I think they were deliberate design choices, so I don't think it can be called a bug in udev. I think the change I mentioned earlier (and quoted above) is a correct and proper solution. It accomplishes the intent of detaching lmt-udev from the spawning udev instance, allows udev and the rest of the boot process (systemd or sysvinit) to continue normally, and allows LMT to process the devices present at boot once /usr is mounted and the LMT programs are available. The only risk to it would be if there was error output from the script that normally would be captured and logged by udev, this would prevent that. It looks like LMT is designed to log to syslog directly, so if there are errors they wouldn't be going to stdout/stderr anyways. Given that udev didn't capture stdout/stderr before, and LMT logs on its own, I think this risk can be ignored. -- -Matt Reality is that which, when you stop believing in it, doesn't go away. -- Philip K. Dick GPG pubkey fingerprint: A57F B354 FD30 A502 795B 9637 3EF1 3F22 A85E 2AD1 -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#755905: Acknowledgement (segfaults after update)
Yet more stacktraces.
--
Cheers,
Andrew
Program received signal SIGSEGV, Segmentation fault.
js::jit::JitRuntime::patchIonBackedges (this=0xb725af80, rt=0xb0254000, target=js::jit::JitRuntime::BackedgeLoopHeader)
at /build/iceweasel-3vlBEX/iceweasel-31.0/js/src/jit/Ion.cpp:412
412 in /build/iceweasel-3vlBEX/iceweasel-31.0/js/src/jit/Ion.cpp
(gdb) bt full
#0 js::jit::JitRuntime::patchIonBackedges (this=0xb725af80, rt=0xb0254000, target=js::jit::JitRuntime::BackedgeLoopHeader)
at /build/iceweasel-3vlBEX/iceweasel-31.0/js/src/jit/Ion.cpp:412
iter = optimized out
#1 0xb4e31068 in js::jit::InterruptCheck (cx=0x9f1feda0) at /build/iceweasel-3vlBEX/iceweasel-31.0/js/src/jit/VMFunctions.cpp:523
No locals.
#2 0xb03a333e in ?? ()
No symbol table info available.
#3 0xb039c8ca in ?? ()
No symbol table info available.
#4 0xb4d04b93 in EnterBaseline (cx=0x1f, cx@entry=0x9f1feda0, data=...) at /build/iceweasel-3vlBEX/iceweasel-31.0/js/src/jit/BaselineJIT.cpp:124
pcc = {cx = 0x1f, oldCompartment = optimized out}
activation = {js::Activation = {cx_ = 0x9f1feda0, compartment_ = 0x79dfb4c0, prev_ = 0xbfe1c4e8, savedFrameChain_ = 0, hideScriptedCallerCount_ = 0,
kind_ = js::Activation::Jit}, prevIonTop_ = 0x0, prevJitJSContext_ = 0x0, firstFrameIsConstructing_ = false, active_ = true, rematerializedFrames_ = {
impl = {js::TempAllocPolicy = {cx_ = 0x9f1feda0}, hashShift = 32, entryCount = 0, gen = 0, removedCount = 0, table = 0x0, entered = {No data fields},
mutationCount = {No data fields}, static sMinCapacityLog2 = optimized out, static sMinCapacity = optimized out,
static sMaxInit = optimized out, static sMaxCapacity = optimized out, static sHashBits = optimized out,
static sAlphaDenominator = optimized out, static sMinAlphaNumerator = optimized out, static sMaxAlphaNumerator = optimized out,
static sFreeKey = optimized out, static sRemovedKey = optimized out, static sCollisionBit = optimized out}}}
#5 0xb4d2a077 in js::jit::EnterBaselineAtBranch (cx=0x9f1feda0, fp=0xae50f138, pc=0x9bf691c8 \343\201V)
at /build/iceweasel-3vlBEX/iceweasel-31.0/js/src/jit/BaselineJIT.cpp:209
data = {jitcode = 0x9e2f5514 \277, osrFrame = 0xae50f138, calleeToken = 0x87d0be40, maxArgv = 0xae50f118, maxArgc = 4, numActualArgs = 2,
osrNumStackValues = 6, scopeChain = {js::RootedBaseJSObject* = {No data fields}, stack = 0x9f1fedac, prev = 0xbfe1c40c, ptr = 0x0},
result = {js::RootedBaseJS::Value = {js::MutableValueOperationsJS::RootedJS::Value = {js::ValueOperationsJS::RootedJS::Value = {No data fields}, No data fields}, No data fields}, stack = 0x9f1fedd0, prev = 0xbfe1c480, ptr = {data = {asBits = 18446743528248705026, s = {payload = {i32 = 2, u32 = 2,
boo = 2, str = 0x2, obj = 0x2, ptr = 0x2, why = JS_NO_ITER_VALUE, word = 2, uintptr = 2}, tag = JSVAL_TAG_INT32},
asDouble = -nan(0xfff810002), asPtr = 0x2}}}, constructing = false}
status = optimized out
thisv = {js::RootedBaseJS::Value = {js::MutableValueOperationsJS::RootedJS::Value = {js::ValueOperationsJS::RootedJS::Value = {No data fields}, No data fields}, No data fields}, stack = 0x9f1fedd0, prev = 0xbfe1c278, ptr = {data = {asBits = 18446743532543672320, s = {payload = {i32 = 0, u32 = 0,
boo = 0, str = 0x0, obj = 0x0, ptr = 0x0, why = JS_ELEMENTS_HOLE, word = 0, uintptr = 0}, tag = JSVAL_TAG_UNDEFINED},
asDouble = -nan(0xfff82), asPtr = 0x0}}}
#6 0xb4f8b24c in Interpret (cx=0x63a52164, cx@entry=0x9f1feda0, state=...) at /build/iceweasel-3vlBEX/iceweasel-31.0/js/src/vm/Interpreter.cpp:1713
maybeOsr = (unknown: 1671766372)
status = 1671766372
rootValue0 = {js::RootedBaseJS::Value = {js::MutableValueOperationsJS::RootedJS::Value = {js::ValueOperationsJS::RootedJS::Value = {No data fields}, No data fields}, No data fields}, stack = 0x9f1fedd0, prev = 0xbfe1c950, ptr = {data = {asBits = 18446743528248705104, s = {payload = {i32 = 80,
u32 = 80, boo = 80, str = 0x50, obj = 0x50, ptr = 0x50, why = 80, word = 80, uintptr = 80}, tag = JSVAL_TAG_INT32},
asDouble = -nan(0xfff810050), asPtr = 0x50}}}
rootFunction0 = {js::RootedBaseJSFunction* = {No data fields}, stack = 0x9f1fedac, prev = 0xbfe1c400, ptr = 0x7c92c440}
rootValue1 = {js::RootedBaseJS::Value = {js::MutableValueOperationsJS::RootedJS::Value = {js::ValueOperationsJS::RootedJS::Value = {No data fields}, No data fields}, No data fields}, stack = 0x9f1fedd0, prev = 0xbfe1c470, ptr = {data = {asBits = 18446743528248705025, s = {payload = {i32 = 1,
u32 = 1, boo = 1, str = 0x1, obj = 0x1, ptr = 0x1, why = JS_NATIVE_ENUMERATE, word = 1, uintptr = 1}, tag = JSVAL_TAG_INT32},
asDouble = -nan(0xfff810001), asPtr = 0x1}}}
rootString0 = {js::RootedBaseJSString* =
Bug#755909: pangox-compat: please use autoreconf to build
Source: pangox-compat Version: 0.0.2-4 Severity: normal Tags: patch User: debian-de...@lists.debian.org Usertags: autoreconf User: debian-powe...@lists.debian.org Usertags: ppc64el Dear Maintainer, The package pangox-compat fails to build from source on ppc64el. Including dh-autoreconf to debian/rules fixes that so the package builds successfully. The patch attached contains the modification aforementioned. Thanks and regards. Fernando -- System Information: Debian Release: jessie/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: ppc64el (ppc64le) Kernel: Linux 3.13-1-powerpc64le (SMP w/4 CPU cores) Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash diff -Nru pangox-compat-0.0.2/debian/control pangox-compat-0.0.2/debian/control --- pangox-compat-0.0.2/debian/control 2013-05-23 14:20:12.0 + +++ pangox-compat-0.0.2/debian/control 2014-07-24 13:02:21.0 + @@ -11,7 +11,7 @@ Build-Depends: debhelper (= 8.1.3), cdbs (= 0.4.93), gnome-pkg-tools (= 0.11), - autotools-dev, + dh-autoreconf, libx11-dev, libglib2.0-dev (= 2.34.0), libpango1.0-dev (= 1.32.5-3~), diff -Nru pangox-compat-0.0.2/debian/control.in pangox-compat-0.0.2/debian/control.in --- pangox-compat-0.0.2/debian/control.in 2013-05-23 13:56:25.0 + +++ pangox-compat-0.0.2/debian/control.in 2014-07-24 13:02:04.0 + @@ -6,7 +6,7 @@ Build-Depends: debhelper (= 8.1.3), cdbs (= 0.4.93), gnome-pkg-tools (= 0.11), - autotools-dev, + dh-autoreconf, libx11-dev, libglib2.0-dev (= 2.34.0), libpango1.0-dev (= 1.32.5-3~), diff -Nru pangox-compat-0.0.2/debian/rules pangox-compat-0.0.2/debian/rules --- pangox-compat-0.0.2/debian/rules 2013-04-09 17:41:12.0 + +++ pangox-compat-0.0.2/debian/rules 2014-07-24 13:01:43.0 + @@ -1,6 +1,7 @@ #!/usr/bin/make -f include /usr/share/cdbs/1/rules/debhelper.mk +include /usr/share/cdbs/1/rules/autoreconf.mk include /usr/share/cdbs/1/rules/utils.mk include /usr/share/cdbs/1/class/gnome.mk include /usr/share/gnome-pkg-tools/1/rules/uploaders.mk
Bug#755908: [Pkg-postgresql-public] Bug#755908: dbconfig-common: fails to purge active PostgreSQL database
Re: Thorsten Glaser 2014-07-24 20140724125642.24221.68250.report...@tglase-nb.lan.tarent.de postgres=# DROP DATABASE simkolab; ERROR: database simkolab is being accessed by other users DETAIL: There is 1 other session using the database. Some related reading: - http://stackoverflow.com/a/5109190/2171120 - http://stackoverflow.com/a/7489673/2171120 The reason here is that Apache has not yet been restarted/reloaded and that one of its children is holding the connection open. I’m currently trying to shuffle the dbc_go call in postrm in between do_webserver_config() / apache2_invoke disconf and the rest of the cleanup, but that means duplicating it, etc. It would be really nice if dbconfig-common could be patched to tear down a database using the method shown in the above SO link: 1) REVOKE CONNECT ON DATABASE dbname FROM PUBLIC, username; 2) SELECT pg_terminate_backend(procpid) FROM pg_stat_activity WHERE -- don't kill my own connection! procpid pg_backend_pid() -- don't kill the connections to other databases AND datname = 'database_name' ; -- for psql 8.4 to 9.1 -- in psql 9.2 the column procpid was renamed to pid 3) DROP DATABASE dbname; Might be useful to have the psql maintainers say something to this as well; perhaps there’s an easier way? That's about the best you can do from the DB side. Christoph -- c...@df7cb.de | http://www.df7cb.de/ -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#755905: segfaults after update
Hi, On 24 July 2014 15:14, Sylvestre Ledru sylves...@mozilla.com wrote: Since I've updated the Iceweasel 31, it segfaults all the time. Here's one of the traces I've got, but I'm unsure if it's the right one, as typing cont didn't terminate the process. Do you have a way/URL to reproduce it in a regular way? No, it segfaults at any URL. -- Cheers, Andrew -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#755905: segfaults after update
On 24/07/2014 14:43, Andrew Shadura wrote: Package: iceweasel Version: 31.0-1 Hi, Since I've updated the Iceweasel 31, it segfaults all the time. Here's one of the traces I've got, but I'm unsure if it's the right one, as typing cont didn't terminate the process. Do you have a way/URL to reproduce it in a regular way? Thanks S -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
