Bug#773263: Additional CVE ID
Also http://subversion.apache.org/security/CVE-2014-8108-advisory.txt Cheers, Moritz -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#773266: assumes DEB_HOST_GNU_TYPE==DEB_HOST_MULTIARCH: completely breaks i386
Source: dpkg-cross
Version: 2.6.11
Tags: patch
User: helm...@debian.org
Usertags: rebootstrap
dpkg-cross assumes that DEB_HOST_GNU_TYPE == DEB_HOST_MULTIARCH. Thus it
queries for the former and then uses that triplet to look for libraries
in /usr/lib. Unfortunately for i386 this assumption is violated. Thus
i386 packages end up being emptied.
I am attaching a patch that adds the distinction and produces reasonable
packages when operating on i386. This patch is crafted in a way that it
even applies after applying #771497 and #772045 (extra hunk header).
Helmut
diff -Nru dpkg-cross-2.6.11/debian/changelog
dpkg-cross-2.6.11+nmu1/debian/changelog
--- dpkg-cross-2.6.11/debian/changelog 2013-05-24 21:28:56.0 +0200
+++ dpkg-cross-2.6.11+nmu1/debian/changelog 2014-12-15 10:48:28.0
+0100
@@ -1,3 +1,11 @@
+dpkg-cross (2.6.11+nmu1) UNRELEASED; urgency=low
+
+ * Non-maintainer upload.
+ * DEB_HOST_GNU_TYPE and DEB_HOST_MULTIARCH are not necessarily equal.
+(Closes: #-1)
+
+ -- Helmut Grohne hel...@subdivi.de Mon, 15 Dec 2014 10:47:58 +0100
+
dpkg-cross (2.6.11) unstable; urgency=low
* Upload changes from experimental to unstable.
diff -Nru dpkg-cross-2.6.11/dpkg-cross dpkg-cross-2.6.11+nmu1/dpkg-cross
--- dpkg-cross-2.6.11/dpkg-cross2013-05-24 21:28:22.0 +0200
+++ dpkg-cross-2.6.11+nmu1/dpkg-cross 2014-12-15 10:41:35.0 +0100
@@ -14,7 +14,8 @@
@keepdeps $dpkg_statfile $progname $debname $anyway $cross2cross $crosstype
$crossdir $crosslib $crosslib64 $crosslib32 $crossinc $data $len
$retval $dpkg_cmd $mode $pkg @exlist $conffile $removedeps $keepdeps
-$DPKGCROSSVERSION $keep_temp $msg $multiarchpackage $multiarch $multiarchconv);
+$DPKGCROSSVERSION $keep_temp $msg $multiarchpackage $multiarch
+$multiarchtriplet $multiarchconv);
setlocale(LC_MESSAGES, );
textdomain(dpkg-cross);
@@ -723,6 +724,8 @@
my $config = get_config;
$crosstype = `CC= dpkg-architecture -f -a$arch -qDEB_HOST_GNU_TYPE 2
/dev/null`;
chomp ($crosstype);
+ $multiarchtriplet = `CC= dpkg-architecture -f -a$arch
-qDEB_HOST_MULTIARCH 2 /dev/null`;
+ chomp ($multiarchtriplet);
$crossinc = $$config{'crossinc'};
$crossdir = $$config{'crossdir'};
$crosslib = $$config{'crosslib'};
@@ -729,7 +732,7 @@
$crosslib64 = $$config{'crosslib64'};
$crosslib32 = $$config{'crosslib32'};
# add extra regexp component for multiarch packages
- if ($multiarchpackage) { $multiarch=\Q$crosstype/\E } else
{$multiarch=};
+ if ($multiarchpackage) { $multiarch=\Q$multiarchtriplet/\E } else
{$multiarch=};
# Now process regular files ...
open(PIPE, find $src/ -type f -print |) or goto fail;
@@ -738,8 +741,8 @@
s/^$src//;
/^DEBIAN/ next;
# if we have library files on multiarch paths, treat deb like a
multiarch package
- if (m:^(/usr)?/lib/\Q$crosstype/\E:) {
- $multiarch=\Q$crosstype/\E
+ if (m:^(/usr)?/lib/\Q$multiarchtriplet/\E:) {
+ $multiarch=\Q$multiarchtriplet/\E
}
# special support for generated cache data
if (m:(/etc/dpkg-cross/cross-config.d/($arch)?/.*):) {
Bug#771215: git-buildpackage: please merge support for gbp pq-rpm
On Fri, 2014-12-05 at 15:50 +0100, Guido Günther wrote:
Hi Markus,
On Tue, Dec 02, 2014 at 04:47:58PM +0200, Markus Lehtonen wrote:
Hello,
On Fri, 2014-11-28 at 14:55 +0100, Guido Günther wrote:
On Fri, Nov 28, 2014 at 12:11:01PM +0200, Markus Lehtonen wrote:
[..snip..]
If you're willing to wait for few days I could look into this and
provide
a patchset with minimal pq-rpm implementation (i.e. all the new cmdline
options, even configurable branch names, removed). What I'd like to have
there are the unit tests.
That would be awesome! I'd be great to have a second tool merged.
The attached series implements an initial version of the pq-rpm tool.
The first four patches (0001-0004) are required to make the actual
pq-rpm tool to work correctly. The next four patches (0005-0008) are
requirements for the unit tests. The last patch finally implements
gbp-pq-rpm tool itself.
This series (plus some additional features) is also available in
feature/pq-rpm branch in my Github repository:
git clone git://github.com/marquiz/git-buildpackage-rpm.git -b
feature/pq-rpm
I had a look at this branch an it looks great. I'd feel more
comfortable if we'd had a unit test for dump_tree with recursive
though (af39e32692ebedb4316b28851e10f737bf176105) - can you add that,
I can pull in the rest then.
You can find a patch with updated unit tests attached. I also updated
and rebased my feature/pq-rpm branch in Github.
Thanks,
Markus
From 3f19f417727004ce1d3f8a800451201b528efe77 Mon Sep 17 00:00:00 2001
From: Markus Lehtonen markus.lehto...@linux.intel.com
Date: Tue, 17 Sep 2013 15:13:40 +0300
Subject: [PATCH] buildpackage/dump_tree: add 'recursive' option
For selecting whether to dump all the files recursively or just the top
level directory of the tree.
Signed-off-by: Markus Lehtonen markus.lehto...@linux.intel.com
---
gbp/scripts/common/buildpackage.py | 12 +---
tests/04_test_submodules.py| 15 +--
2 files changed, 22 insertions(+), 5 deletions(-)
diff --git a/gbp/scripts/common/buildpackage.py b/gbp/scripts/common/buildpackage.py
index 0522cd6..2e53b78 100644
--- a/gbp/scripts/common/buildpackage.py
+++ b/gbp/scripts/common/buildpackage.py
@@ -101,13 +101,19 @@ def git_archive_single(treeish, output, prefix, comp_type, comp_level, comp_opts
#{ Functions to handle export-dir
-def dump_tree(repo, export_dir, treeish, with_submodules):
+def dump_tree(repo, export_dir, treeish, with_submodules, recursive=True):
dump a tree to output_dir
output_dir = os.path.dirname(export_dir)
prefix = sanitize_prefix(os.path.basename(export_dir))
+if recursive:
+paths = []
+else:
+paths = ['%s' % nam for _mod, typ, _sha, nam in
+repo.list_tree(treeish) if typ == 'blob']
pipe = pipes.Template()
-pipe.prepend('git archive --format=tar --prefix=%s %s' % (prefix, treeish), '.-')
+pipe.prepend('git archive --format=tar --prefix=%s %s -- %s' %
+ (prefix, treeish, ' '.join(paths)), '.-')
pipe.append('tar -C %s -xf -' % output_dir, '-.')
top = os.path.abspath(os.path.curdir)
try:
@@ -115,7 +121,7 @@ def dump_tree(repo, export_dir, treeish, with_submodules):
if ret:
raise GbpError(Error in dump_tree archive pipe)
-if with_submodules:
+if recursive and with_submodules:
if repo.has_submodules():
repo.update_submodules()
for (subdir, commit) in repo.get_submodules(treeish):
diff --git a/tests/04_test_submodules.py b/tests/04_test_submodules.py
index 4b07220..a18f8b5 100644
--- a/tests/04_test_submodules.py
+++ b/tests/04_test_submodules.py
@@ -22,6 +22,7 @@ SUBMODULES = []
SUBMODULE_NAMES = [test_submodule, sub module]
TMPDIR = None
TESTFILE_NAME = testfile
+TESTDIR_NAME = testdir
class Submodule(object):
Class representing remote repo for Git submodule
@@ -57,6 +58,8 @@ def test_empty_has_submodules():
def _add_dummy_data(repo, msg):
Commit dummy data to a Git repository
shutil.copy(.git/HEAD, TESTFILE_NAME)
+os.mkdir(TESTDIR_NAME)
+shutil.copy(TESTFILE_NAME, os.path.join(TESTDIR_NAME, TESTFILE_NAME))
repo.add_files('.', force=True)
repo.commit_all(msg)
@@ -99,8 +102,16 @@ def test_dump_tree():
os.mkdir(dumpdir)
ok_(buildpackage.dump_tree(REPO, dumpdir, master, True))
ok_(os.path.exists(os.path.join(dumpdir, TESTFILE_NAME)))
+ok_(os.path.exists(os.path.join(dumpdir, TESTDIR_NAME, TESTFILE_NAME)))
ok_(os.path.exists(os.path.join(dumpdir, SUBMODULES[0].name,
TESTFILE_NAME)))
+# No submodules or subdirs if recursive is False
+dumpdir = TMPDIR.join(dump2)
+os.mkdir(dumpdir)
+ok_(buildpackage.dump_tree(REPO, dumpdir, master, True, False))
+ok_(os.path.exists(os.path.join(dumpdir, TESTFILE_NAME)))
+ok_(not os.path.exists(os.path.join(dumpdir,
Bug#704069: davical: ldap user entry attribute 'modifyTimestamp' not correctly mapped to internal attribute 'modified'
Hi Bernd, you wrote in Debian bug #704069 (https://bugs.debian.org/704069): The davical authentication hook for ldap makes use of drivers_ldap.php which is also responsible to sync users from ldap to davical. While doing so the timestamp from 'modifyTimestamp' of the ldap entry should be used for the internal attribute 'modified'. Unfortunately the example configuration in /etc/davical/config.php uses 'mapping_field' = array( ..., updated = 'modifyTimestamp', ...) and not 'modified' which leads to warnings in apache logs and propably the corresponding field not being updated The file you're talking about is config/example-config.php in git and currently shipped in the davical Debian package as /usr/share/doc/davical/examples/davical-conf.php/example-config.php.gz I've been searching wiki.davical.org a bit, and it seems our LDAP documentation is a mess. If you're in a position to help us clean that up, correct misunderstandings and consolidate duplicate information in one place that would greatly be appreciated! http://wiki.davical.org/w/Configuration/Authentication_Settings/LDAP_groups documents 'updated' for the group_mapping_filed array http://wiki.davical.org/index.php/Synology_DS211 documents 'modified' for mapping_field, and 'updated' for group_mapping_field http://wiki.davical.org/w/Configuration_settings documents 'updated' for mapping_field http://wiki.davical.org/w/Configuration/Authentication_Settings documents 'updated' for both mapping_field and group_mapping_field http://wiki.davical.org/index.php/Configuration/Authentication_Settings/LDAP_Examples documents 'modified' for mapping_field, and has an interesting comment at the end of the format_updated array: 'S' = array(12,2)), // map LDAP modifyTimestamp field to SQL updated field http://wiki.davical.org/w/Configuration/Authentication_Settings has an explanation of the parameters: mapping_fieldAn array of DAViCal field names vs. their LDAP mappings group_mapping_field An array of DAViCal field names vs. their LDAP mappings format_updated An array, keyed on Y, m, d, H, M and S with the values being arrays of (start,length) for substring operations on the DAViCal 'updated' field sourced from LDAP. Now, I wonder if that field is called 'modified' or 'updated' in DAViCal, or perhaps it was renamed but not in all places?? (This mail is partly for documentation so others can pick up where I'll have to leave this issue for now) Florian -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#773216: Fixed in upstream git
Attached patch from upstream git repo fixes the bridge assert and
brctl commands no longer crash NetworkManager.
As a side note, how about disabling all asserts?
They are a debug and test feature and should not be used as error handling
in production builds?
-Mikko
commit c9b9229c2e7de2bbb12e493a868921b7a788ee92
Author: Jiří Klimeš jkli...@redhat.com
Date: Wed Sep 24 16:02:37 2014 +0200
core: do not assert when a device is enslaved externally
Test case:
# ip link add name BR type bridge
# brctl addif BR eth0
Monitoring external master/slave changes was intruduced by
08e0cfb484dfc6aa6342871158ffe752c7c50f03.
diff --git a/src/devices/nm-device.c b/src/devices/nm-device.c
index 28fd128..4a5eb18 100644
--- a/src/devices/nm-device.c
+++ b/src/devices/nm-device.c
@@ -2950,8 +2950,6 @@ act_stage3_ip4_config_start (NMDevice *self,
g_assert (connection);
method = nm_utils_get_ip_config_method (connection,
NM_TYPE_SETTING_IP4_CONFIG);
- if (priv-master)
- g_assert_cmpstr (method, ==,
NM_SETTING_IP4_CONFIG_METHOD_DISABLED);
if ( strcmp (method, NM_SETTING_IP4_CONFIG_METHOD_MANUAL) != 0
priv-is_master
@@ -3956,8 +3954,6 @@ act_stage3_ip6_config_start (NMDevice *self,
g_assert (connection);
method = nm_utils_get_ip_config_method (connection,
NM_TYPE_SETTING_IP6_CONFIG);
- if (priv-master)
- g_assert_cmpstr (method, ==,
NM_SETTING_IP6_CONFIG_METHOD_IGNORE);
if ( strcmp (method, NM_SETTING_IP6_CONFIG_METHOD_MANUAL) != 0
priv-is_master
diff --git a/src/nm-active-connection.c b/src/nm-active-connection.c
index 30e319b..130b522 100644
--- a/src/nm-active-connection.c
+++ b/src/nm-active-connection.c
@@ -365,11 +365,11 @@ device_master_changed (GObject *object,
return;
if (!nm_device_get_master (device))
return;
+ if (!nm_active_connection_get_master (self))
+ return;
g_signal_handlers_disconnect_by_func (device, G_CALLBACK
(device_master_changed), self);
master = nm_active_connection_get_master (self);
- g_assert (master);
-
master_state = nm_active_connection_get_state (master);
if (master_state = NM_ACTIVE_CONNECTION_STATE_DEACTIVATING) {
/* Master failed before attaching the slave */
Bug#772543: python-psutil: severak filehandle leaks
Just to let you know that the current version upstream is not enough to solve the problem. I copied their version in the jessie release, backported it to wheezy and tried it. After less than 24h, the system is stuck again, The problem can be traced to: @wrap_exceptions def threads(self): Where there is still an open that does not close properly: 2014-12-16 09:21:21,185 - com.barco.mgs.TeamMgrM56094 - INFO - start - Received request to start a team sid T10621 - wid W90616 2014-12-16 09:21:21,185 - com.barco.mgs.TeamMgrM56094 - ERROR - start - [' File /usr/lib/pymodules/python2.7/Mgs2/Team/TeamMgr.py, line 831, in start\nlimit = status.cpu_percent\n', ' File /usr/lib/pymodules/python2.7/Mgs2/SystemStatusBase.py, line 346, in cpu_percent\n', ' File /usr/lib/pymodules/python2.7/Mgs2/SystemStatusBase.py, line 349, in get_cpu_percent\n', ' File /usr/lib/python2.7/dist-packages/psutil/__init__.py, line 1509, in cpu_percent\n_last_cpu_times = cpu_times()\n', ' File /usr/lib/python2.7/dist-packages/psutil/__init__.py, line 1439, in cpu_times\nreturn _psplatform.cpu_times()\n', ' File /usr/lib/python2.7/dist-packages/psutil/_pslinux.py, line 215, in cpu_times\nwith open(\'/proc/stat\', \'rb\') as f:\n'] 2014-12-16 09:21:21,186 - com.barco.mgs.TeamMgrM56094 - ERROR - start - [Errno 24] Too many open files: '/proc/stat' 2014-12-16 09:21:21,186 - com.barco.mgs.TeamMgrM56094 - ERROR - start - Error during worker creation [Errno 24] Too many open files: '/proc/stat' ...snip... rtsp_mgs. 26609 29136root txt unknown /proc/26609/task/29136/exe (readlink: Permission denied) rtsp_mgs. 26609 29136root NOFD /proc/26609/task/29136/fd (opendir: Permission denied) rtsp_mgs. 26609 29144root cwd unknown /proc/26609/task/29144/cwd (readlink: Permission denied) rtsp_mgs. 26609 29144root rtd unknown /proc/26609/task/29144/root (readlink: Permission denied) rtsp_mgs. 26609 29144root txt unknown /proc/26609/task/29144/exe (readlink: Permission denied) rtsp_mgs. 26609 29144root NOFD /proc/26609/task/29144/fd (opendir: Permission denied) rtsp_mgs. 26609 29147root cwd unknown /proc/26609/task/29147/cwd (readlink: Permission denied) rtsp_mgs. 26609 29147root rtd unknown /proc/26609/task/29147/root (readlink: Permission denied) rtsp_mgs. 26609 29147root txt unknown /proc/26609/task/29147/exe (readlink: Permission denied) rtsp_mgs. 26609 29147root NOFD /proc/26609/task/29147/fd (opendir: Permission denied) rtsp_mgs. 26609 29148root cwd unknown /proc/26609/task/29148/cwd (readlink: Permission denied) rtsp_mgs. 26609 29148root rtd unknown /proc/26609/task/29148/root (readlink: Permission denied) rtsp_mgs. 26609 29148root txt unknown /proc/26609/task/29148/exe (readlink: Permission denied) rtsp_mgs. 26609 29148root NOFD /proc/26609/task/29148/fd (opendir: Permission denied) rtsp_mgs. 26609 29149root cwd unknown /proc/26609/task/29149/cwd (readlink: Permission denied) rtsp_mgs. 26609 29149root rtd unknown /proc/26609/task/29149/root (readlink: Permission denied) rtsp_mgs. 26609 29149root txt unknown /proc/26609/task/29149/exe (readlink: Permission denied) rtsp_mgs. 26609 29149root NOFD /proc/26609/task/29149/fd (opendir: Permission denied) rtsp_mgs. 26609 29152root cwd unknown /proc/26609/task/29152/cwd (readlink: Permission denied) rtsp_mgs. 26609 29152root rtd unknown /proc/26609/task/29152/root (readlink: Permission denied) rtsp_mgs. 26609 29152root txt unknown /proc/26609/task/29152/exe (readlink: Permission denied) rtsp_mgs. 26609 29152root NOFD /proc/26609/task/29152/fd (opendir: Permission denied) rtsp_mgs. 26609 29153root cwd unknown /proc/26609/task/29153/cwd (readlink: Permission denied) rtsp_mgs. 26609 29153root rtd unknown /proc/26609/task/29153/root (readlink: Permission denied) rtsp_mgs. 26609 29153root txt unknown /proc/26609/task/29153/exe (readlink: Permission denied) rtsp_mgs. 26609 29153root NOFD /proc/26609/task/29153/fd (opendir: Permission denied) rtsp_mgs. 26609 29155root cwd unknown /proc/26609/task/29155/cwd (readlink: Permission denied) rtsp_mgs. 26609 29155root rtd unknown /proc/26609/task/29155/root (readlink: Permission denied) rtsp_mgs. 26609 29155root txt unknown /proc/26609/task/29155/exe (readlink: Permission denied) rtsp_mgs. 26609 29155root NOFD /proc/26609/task/29155/fd (opendir: Permission denied) rtsp_mgs. 26609 29157root cwd unknown /proc/26609/task/29157/cwd (readlink: Permission denied) rtsp_mgs. 26609 29157root rtd unknown /proc/26609/task/29157/root (readlink: Permission denied) rtsp_mgs. 26609 29157root txt unknown
Bug#772946: [Fwd: Re: [UPDATED] grub2 2.02~beta2-18: Please update debconf PO translation for the package grub2]
---BeginMessage---
HI Ian,
You can find fixed translation attached to this mail.
Thanks and best regards,
Dooteo
Jatorrizko mezua: lr., 2014-12-13 20:37 +, egilea: Ian Campbell
Hi,
You are noted as the last translator of the debconf translation for
grub2.
Thank you to those of you who have already submitted translation updates.
It has been brought to my attention that the phrase EFI removable path in
the
previous English version is confusing and wrong and should really be EFI
removable media path. Therefore I am sending out an updated po file (see
attached) with this fixed.
I'm afraid this will have marked any existing translations as fuzzy.
Please send the updated file to me, or submit it as a wishlist bug against
grub2. If you have already translated this template and the above change does
not invalidate your translation then please let me know and I will un-fuzz it
for you.
At the same time some minor tweaks have been made to the English grammar. I
think these should not affect translations.
The complete wdiff for the English updates vs last time is:
8--
Template: grub2/force_efi_extra_removable
Type: boolean
Default: false
_Description: Force extra installation to the EFI removable {+media+} path?
Some EFI-based systems are buggy and do not handle new bootloaders correctly.
If you force {+an+} extra installation of GRUB to the EFI removable
{+media+} path, [-it-]
{+this+} should
[-make sure-] {+ensure+} that this system will boot Debian correctly despite
such a
problem. However, [-this-] {+it+} may remove the ability to boot any other
operating
systems that also depend on this path. If so, you will need to [-ensure-]
{+make sure+} that
GRUB is configured successfully to be able {+to+} boot any other OS
installations
correctly.
8--
The deadline for receiving the updated translation is still
Sun, 21 Dec 2014 19:58:50 +.
Thanks in advance, and sorry for the inconvenience.
Ian.
# Basque translation for grub2
# Copyright (C) YEAR THE PACKAGE'S COPYRIGHT HOLDER
# This file is distributed under the same license as the PACKAGE package.
#
# Piarres Beobide p...@beobide.net, 2008.
# Iñaki Larrañaga Murgoitio doo...@zundan.com, 2008, 2009, 2010.
# Iñaki Larrañaga Murgoitio doo...@zundan.com, 2011, 2014.
msgid
msgstr
Project-Id-Version: grub2_2.02~beta2-18\n
Report-Msgid-Bugs-To: gr...@packages.debian.org\n
POT-Creation-Date: 2014-12-13 20:23+\n
PO-Revision-Date: 2014-12-16 09:10+0100\n
Last-Translator: Iñaki Larrañaga Murgoitio doo...@zundan.com\n
Language-Team: Basque debian-l10n-bas...@lists.debian.org\n
Language: eu\n
MIME-Version: 1.0\n
Content-Type: text/plain; charset=UTF-8\n
Content-Transfer-Encoding: 8bit\n
X-Generator: Lokalize 1.4\n
Plural-Forms: nplurals=2; plural=(n != 1);\n
#. Type: boolean
#. Description
#: ../grub-pc.templates.in:2001
msgid Chainload from menu.lst?
msgstr Kargatu menu.lst fitxategitik?
#. Type: boolean
#. Description
#: ../grub-pc.templates.in:2001
msgid GRUB upgrade scripts have detected a GRUB Legacy setup in /boot/grub.
msgstr
GRUB eguneratzeko script-ek GRUB zahar baten konfigurazioa aurkitu dute /
boot/grub-en.
#. Type: boolean
#. Description
#: ../grub-pc.templates.in:2001
msgid
In order to replace the Legacy version of GRUB in your system, it is
recommended that /boot/grub/menu.lst is adjusted to load a GRUB 2 boot image
from your existing GRUB Legacy setup. This step can be automatically
performed now.
msgstr
Sistemako GRUB zaharraren bertsioa behar bezala ordezkatzeko, gomendagarria
da /boot/grub/menu.lst doitzea GRUB 2 dagoeneko instalatuta duzun GRUB
zaharraren bidez kargatzeko. Urrats hau automatikoki egin daiteke orain.
#. Type: boolean
#. Description
#: ../grub-pc.templates.in:2001
msgid
It's recommended that you accept chainloading GRUB 2 from menu.lst, and
verify that the new GRUB 2 setup works before it is written to the MBR
(Master Boot Record).
msgstr
Gomendagarria da GRUB 2 menu.lst bidez kargatzea onartzea, eta GRUB 2-ren
konfigurazioak zure beharrak betetzen dituela egiaztatzea MBRan (Master Boot
Record) idatzi aurretik.
#. Type: boolean
#. Description
#: ../grub-pc.templates.in:2001
msgid
Whatever your decision, you can replace the old MBR image with GRUB 2 later
by issuing the following command as root:
msgstr
Berdin dio zer erabakitzen duzun, MBRren irudi zaharra GRUB 2rekin ordeztu
dezakezu supererabiltzaile (root) gisa honako komandoa exekutatuz:
#. Type: multiselect
#. Description
#. Type: multiselect
#. Description
#: ../grub-pc.templates.in:3001 ../grub-pc.templates.in:4001
msgid GRUB install devices:
msgstr GRUB instalatzeko gailuak:
#. Type: multiselect
#. Description
#: ../grub-pc.templates.in:3001
msgid
The grub-pc package is being upgraded. This menu allows you to select which
devices you'd like grub-install to be automatically run for, if any.
msgstr
grub-pc paketea
Bug#773267: Provide a means to query fsck whether it would run a routine check
Package: util-linux Version: 2.25.2-3 Severity: wishlist File: /sbin/fsck Tags: upstream In the context of #773035, I am looking for a way to figure out whether a reboot *now* would be likely to cause lengthy fsck routine checks, e.g. due to the maximal mount count or days since last check being reached on ext-filesystems. I'd like to avoid parsing debug2fs or tune2fs output and comparing numbers or timestamps in the text output, like /usr/lib/update-notifier/update-motd-fsck-at-reboot seems to be doing on Ubuntu. Instead, I'd really like to just ask fsck. fsck -A -t ext2,ext3,ext4,… -N is already very helpful showing me which filesystem-specific commands it would run, but each of those is run unconditionally on the filesystem and determines by itself whether a check is needed. There is the -n option, and it does seem that the sought information could be parsed from the output, but invoking fsck -n on a mounted filesystem is quite unreliable and it'd be a hack too. So instead, I envision a call such as: fsck -A -t ext2,ext3,ext4,… -q or fsck -q /dev/mapper/vg-root and it would exit 0 if a routine check was not going to happen, and exit non-zero if a check would now happen (possibly encoding the reason in the exit code). -V output could also be provided. Thanks for your consideration. -- System Information: Debian Release: jessie/sid APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 3.17-1-amd64 (SMP w/8 CPU cores) Locale: LANG=en_NZ, LC_CTYPE=en_NZ.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages util-linux depends on: ii initscripts2.88dsf-58 ii libblkid1 2.25.2-3 ii libc6 2.19-13 ii libmount1 2.25.2-3 ii libncurses55.9+20140913-1 ii libpam0g 1.1.8-3.1 ii libselinux12.3-2 ii libslang2 2.3.0-2 ii libsmartcols1 2.25.2-3 ii libtinfo5 5.9+20140913-1 ii libuuid1 2.25.2-3 ii lsb-base 4.1+Debian13+nmu1 ii tzdata 2014j-1 ii zlib1g 1:1.2.8.dfsg-2 util-linux recommends no packages. Versions of packages util-linux suggests: ii dosfstools 3.0.27-1 ii kbd 1.15.5-2 pn util-linux-locales none -- debconf-show failed -- .''`. martin f. krafft madduck@d.o @martinkrafft : :' : proud Debian developer `. `'` http://people.debian.org/~madduck `- Debian - when you have better things to do than fixing systems digital_signature_gpg.asc Description: Digital signature (see http://martin-krafft.net/gpg/sig-policy/999bbcc4/current)
Bug#772983: kirkwood kernel image is too big
On Sun, 2014-12-14 at 19:26 +, Ben Hutchings wrote:
I think it would be better to add an unconditional warning, rather than
an error, when there is 1% free space left. I realise this will be
easy to ignore but it's still better than an unnecessary failure.
OK, makes sense. Here's what I'm currently running with, I'll push it
along with the size reduction stuff.
Ian.
commit 42c4d12d02edbf8ca065d4d21f8fdc668ec095cc
Author: Ian Campbell i...@debian.org
Date: Mon Dec 15 21:25:38 2014 +
[armel] Warn if image size leaves less than 1% spare capacity in the flash.
This allows some slack for growth over the lifetime of a stable release.
diff --git a/debian/bin/buildcheck.py b/debian/bin/buildcheck.py
index 38241df..8cad299 100755
--- a/debian/bin/buildcheck.py
+++ b/debian/bin/buildcheck.py
@@ -172,6 +172,8 @@ class CheckImage(object):
self.dir = dir
self.arch, self.featureset, self.flavour = arch, featureset, flavour
+self.changelog = Changelog(version=VersionLinux)[0]
+
self.config_entry_build = config.merge('build', arch, featureset,
flavour)
self.config_entry_image = config.merge('image', arch, featureset,
flavour)
@@ -204,7 +206,20 @@ class CheckImage(object):
out.write('Image too large (%d %d)! Refusing to continue.\n' %
(size, value))
return 1
-out.write('Image fits (%d = %d). Continuing.\n' % (size, value))
+# 1% overhead is desirable in order to cope with growth
+# through the lifetime of a stable release. Warn if this is
+# not the case.
+usage = (float(size)/value) * 100.0
+out.write('Image size %d/%d, using %.2f%%. ' % (size, value, usage))
+if size value:
+sys.write('Too large. Refusing to continue.\n')
+return 1
+elif usage = 99.0:
+out.write('Under 1%% space in %s. ' % self.changelog.distribution)
+else:
+out.write('Image fits. ')
+out.write('Continuing.\n')
+
return 0
diff --git a/debian/changelog b/debian/changelog
index 6492cda..ae58576 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -14,6 +14,9 @@ linux (3.16.7-ckt2-2) UNRELEASED; urgency=medium
OMAP5_DSS_HDMI, DISPLAY_ENCODER_TPD12S015, DISPLAY_CONNECTOR_HDMI,
USB_DWC3_OMAP, EXTCON_PALMAS, TI_EMIF and DDR.
Based on a patch from Chen Baozi (Closes: #772953)
+ * [armel] Change configuration to reduce kernel image size
+- Warn if image size leaves less than 1% spare capacity in the flash. This
+ allows some slack for growth over the lifetime of a stable release.
-- Ben Hutchings b...@decadent.org.uk Sat, 13 Dec 2014 11:45:48 +
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#616614: /usr/bin/dpkg-deb: Please support --fsys-tarfile - to mean stdin
Control: tag -1 patch Hi, please find attached a simple patch which enables this functionality by assigning STDIN_FILENO to the file descriptor instead of trying to open it if the filename is equal to -. The tricky part is, that the archive filename is not an argument to the --ctrl-tarfile or --fsys-tarfile argument as it could be interpreted from the dpkg-deb man page. Instead, the archive filename is a positional argument and since there can be no positional argument starting with a minus character, it must be given after a -- like this: dpkg-deb --ctrl-tarfile -- - I added a note about this into the man page. Thanks! cheers, josch diff --git a/dpkg-deb/extract.c b/dpkg-deb/extract.c index 2c92940..00683f9 100644 --- a/dpkg-deb/extract.c +++ b/dpkg-deb/extract.c @@ -124,7 +124,10 @@ extracthalf(const char *debar, const char *dir, bool header_done; enum compressor_type decompressor = COMPRESSOR_TYPE_GZIP; - arfd = open(debar, O_RDONLY); + if (strcmp(debar, -) == 0) +arfd = STDIN_FILENO; + else +arfd = open(debar, O_RDONLY); if (arfd 0) ohshite(_(failed to read archive `%.255s'), debar); if (fstat(arfd, stab)) diff --git a/man/dpkg-deb.1 b/man/dpkg-deb.1 index c5038ec..9fa2aea 100644 --- a/man/dpkg-deb.1 +++ b/man/dpkg-deb.1 @@ -43,6 +43,12 @@ with whatever options you want to pass to will spot that you wanted .B dpkg\-deb and run it for you. +.PP +.B dpkg\-deb +can also read the archive from standard input if the archive name is given as +single minus character. Note, that this argument must be interpreted as a +positional argument and must thus be specified after a separating \-\- +(without the quotes). . .SH COMMANDS .TP
Bug#773268: uci2wb: FTBFS with ld --as-needed
Package: uci2wb
Version: 2.0-1
Severity: normal
Tags: patch
User: ubuntu-de...@lists.ubuntu.com
Usertags: origin-ubuntu vivid ubuntu-patch
Dear Maintainer,
In Ubuntu, we use ld --as-needed by default in the toolchain, and you package
fails to build from source with that option enabled because of the way
libraries are linked.
Even though Debian doesn't use ld --as-needed by default, it is a good idea to
make this change so that (1) we don't have to maintain a delta and (2) you
don't need to change anything in case Debian makes this default in the future.
You can read more about this option here:
https://wiki.debian.org/ToolChain/DSOLinking#Only_link_with_needed_libraries
In Ubuntu, the attached patch was applied to achieve the following:
* debian/patches/as-needed.patch: Put libraries after objects to fix FTBFS
with ld --as-needed.
Thanks for considering the patch.
Logan Rosen
-- System Information:
Debian Release: jessie/sid
APT prefers vivid-updates
APT policy: (500, 'vivid-updates'), (500, 'vivid-security'), (500, 'vivid'),
(100, 'vivid-backports')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 3.16.0-25-generic (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
diff -Nru uci2wb-2.0/debian/patches/as-needed.patch uci2wb-2.0/debian/patches/as-needed.patch
--- uci2wb-2.0/debian/patches/as-needed.patch 1969-12-31 19:00:00.0 -0500
+++ uci2wb-2.0/debian/patches/as-needed.patch 2014-12-16 03:01:37.0 -0500
@@ -0,0 +1,11 @@
+--- a/Makefile
b/Makefile
+@@ -10,7 +10,7 @@
+ all: ${ALL}
+
+ uci2wb: UCI2WB.c
+- $(CC) $(CFLAGS) $(LDFLAGS) $(CPPFLAGS) UCI2WB.c -o uci2wb
++ $(CC) $(CFLAGS) $(CPPFLAGS) UCI2WB.c -o uci2wb $(LDFLAGS)
+
+ install: ${ALL}
+ install -d -m0755 $(DESTDIR)/usr/games
diff -Nru uci2wb-2.0/debian/patches/series uci2wb-2.0/debian/patches/series
--- uci2wb-2.0/debian/patches/series 1969-12-31 19:00:00.0 -0500
+++ uci2wb-2.0/debian/patches/series 2014-12-16 03:00:46.0 -0500
@@ -0,0 +1 @@
+as-needed.patch
Bug#767554: Bug#769853: /769854: unblock: python-persistent and python-zodb
Hi,
Julien Cristau jcris...@debian.org writes:
On Fri, Dec 12, 2014 at 12:44:08 +0900, Arnaud Fontaine wrote:
I have attached the debdiff with the packages currently in unstable,
would you consider unblocking these changes if I upload the packages to
unstable?
Yes, I would.
Thanks! I have just uploaded both packages to unstable. Compared to my
previous debdiff, I have just merged the work done by Gediminas for the
next version of ZODB (basically only patch filenames are different and
the changelog entry has been modified accordingly), but the content of
python-zodb binary package is exactly the same.
I have attached debdiffs for both packages in case of.
Adam D. Barratt a...@adam-barratt.org.uk writes:
Control: tags 769854 + confirmed moreinfo
Control: tags 769853 + confirmed moreinfo
If the upload can be made soon, that should be fine. Please remove the
moreinfo tags once the packages are in unstable.
Done.
Cheers,
--
Arnaud Fontaine
diff -Nru python-persistent-4.0.8/debian/changelog python-persistent-4.0.8/debian/changelog
--- python-persistent-4.0.8/debian/changelog 2014-11-14 18:30:25.0 +0900
+++ python-persistent-4.0.8/debian/changelog 2014-12-10 17:41:09.0 +0900
@@ -1,3 +1,13 @@
+python-persistent (4.0.8-3) unstable; urgency=medium
+
+ * Team upload.
+ * Revert change in previous upload in favor of removing persistent
+module from python-zodb and make it depend upon this package (with
+upstream ACK). Closes: #767554.
++ d/control: Add Breaks/Replaces against python-zodb 1:3.9.7-4~.
+
+ -- Arnaud Fontaine ar...@debian.org Wed, 10 Dec 2014 17:33:13 +0900
+
python-persistent (4.0.8-2) unstable; urgency=medium
* Team upload.
diff -Nru python-persistent-4.0.8/debian/control python-persistent-4.0.8/debian/control
--- python-persistent-4.0.8/debian/control 2014-11-14 18:31:01.0 +0900
+++ python-persistent-4.0.8/debian/control 2014-12-10 17:37:40.0 +0900
@@ -22,7 +22,8 @@
Package: python-persistent
Architecture: any
Depends: ${misc:Depends}, ${python:Depends}, ${shlibs:Depends}
-Conflicts: python-zodb ( 3.11.0~)
+Breaks: python-zodb ( 1:3.9.7-4~)
+Replaces: python-zodb ( 1:3.9.7-4~)
Description: Automatic persistence for Python objects
This package contains a generic persistence implementation for Python. It
forms the core protocol for making objects interact transparently with
diff -Nru zodb-3.9.7/debian/changelog zodb-3.9.7/debian/changelog
--- zodb-3.9.7/debian/changelog 2014-11-17 12:10:50.0 +0900
+++ zodb-3.9.7/debian/changelog 2014-12-16 17:16:27.0 +0900
@@ -1,3 +1,29 @@
+zodb (1:3.9.7-4) unstable; urgency=medium
+
+ * Team upload.
+ * Revert change in previous upload in favor of removing persistent
+module from this package and make it depend upon python-persistent
+(with upstream ACK). Closes: #767554.
++ d/control: Add Depends against python-persistent.
++ d/rules: Delete persistent module from final package.
++ d/p/persistent-module-4.x-compat.patch: persistent 4.x uses bytes
+ instead of repr() but ZODB 4.0.0a4 still uses repr() which is
+ incompatible.
++ d/tests/all: Remove persistent from the list of tests being ran.
++ d/tests/control: zope.testing.doctest has been removed in
+ python-zope.testing 4.0.0 and tests cannot be ran anymore. So update
+ Depends accordingly even though 4.0.0~ is only in stable instead of
+ backporting many patches. Fix this issue properly when packing NUR
+ after the release of Jessie.
+ * d/p/test-spurious-failure-under-python27.patch: Fix python2.7 tests.
+
+ [ Gediminas Paulauskas ]
+ * d/p/new-transaction.patch: Fix test failure with new transaction.
+ * d/p/testUtils.patch: Fix test failure with python2.7 (= 2.7.6).
+ * d/tests: Switch to zope.testrunner.
+
+ -- Arnaud Fontaine ar...@debian.org Tue, 16 Dec 2014 17:12:06 +0900
+
zodb (1:3.9.7-3) unstable; urgency=medium
* Team upload.
@@ -237,4 +263,3 @@
* Initial release (Closes: #158552, #159072, #188435)
-- Fabio Tranchitella kob...@debian.org Thu, 18 Aug 2005 21:49:17 +
-
diff -Nru zodb-3.9.7/debian/control zodb-3.9.7/debian/control
--- zodb-3.9.7/debian/control 2014-11-17 12:09:52.0 +0900
+++ zodb-3.9.7/debian/control 2014-12-16 16:40:16.0 +0900
@@ -19,13 +19,12 @@
Depends: ${pydeb:Depends},
${python:Depends},
${misc:Depends},
- ${shlibs:Depends}
+ ${shlibs:Depends},
+ python-persistent
Provides: ${pydeb:Provides},
${python:Provides},
- python-persistent
Suggests: ${pydeb:Suggests}
-Conflicts: zope3,
- python-persistent
+Conflicts: zope3
Description: Zope Object Database (ZODB)
The Zope Object Database is an object-oriented database for Python that
provides a high-degree of transparency. Applications can take advantage of
diff -Nru zodb-3.9.7/debian/patches/new-transaction.patch
Bug#773170: [Pkg-sysvinit-devel] Bug#773170: insserv: refuses to start postfix at boot because dnsmasq is disabled
Control: reassign -1 postfix [Salvo Tomaselli] Dear Maintainer, insserv refuses to start postfix at boot, because I have configured dnsmasq to be disabled. Hi. As insserv is not involved at all during boot, I suspect this bug is misfiled. Perhaps it is a problem with postfix or dnsmasq dependencies (should be soft, not hard) or with systemd refusing to start. My prime suspect would be postfix, so I pass this bug over to the postfix maintainers for a closer look. If postfix do not require dnsmasq (but should be startet after it if it exist) it should only use should-start instead of require-start in its init.d script. -- Happy hacking Petter Reinholdtsen -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#773269: Computer crash when installing cups-daemon 1.7.5-10
Package: cups-daemon Version: 1.7.5-10 Severity: important Dear Maintainer, Installing the newest cups* (version 1.7.5-10) packages from Sid I get a computer crash (needing hard reboot) when apt-get install cups-daemon has been stopping the cups service using systemctl. Systemctl stop cups.service itself doesn't produce a crash. The bug is reproducible, even when the cups service is disabled and not running. -- System Information: Debian Release: jessie/sid + experimental Architecture: amd64 (x86_64) Kernel: Linux debian 3.18-0 amd6 Systemd: 218-1 Kind regards, Jos van Wolput -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#773270: qt4-x11: FTBFS on powerpcspe: .pch/release-shared/QtDesignerComponents: No such file or directory
Source: qt4-x11
Version: 4:4.8.6+git64-g5dc8b2b+dfsg-2
Severity: wishlist
Tags: patch
User: debian-powerpc...@breakpoint.cc
Usertags: powerpcspe
Hi!
The build of qt4-x11 on powerpcspe fails like this:
...
/«BUILDDIR»/qt4-x11-4.8.6+git64-g5dc8b2b+dfsg/bin/uic
../taskmenu/tablewidgeteditor.ui -o .uic/release-shared/ui_tablewidgeteditor.h
g++ -O2 -fstack-protector-strong -Wformat -Werror=format-security
-D_FORTIFY_SOURCE=2 -I/usr/include/freetype2 -gstabs -O2 -D_REENTRANT
-fvisibility=hidden -fvisibility-inlines-hidden -Wall -W -fPIC
-DQT_STATICPLUGIN -DQDESIGNER_COMPONENTS_LIBRARY -DQT_NO_DEBUG -DQT_SCRIPT_LIB
-DQT_XML_LIB -DQT_GUI_LIB -DQT_CORE_LIB -D_LARGEFILE64_SOURCE
-D_LARGEFILE_SOURCE -DQT_SHARED -I../../../../../mkspecs/linux-g++ -I.
-I../../../../../include/QtDesigner -I../../../../../include/QtCore
-I../../../../../include/QtGui -I../../../../../include/QtXml
-I../../../../../include/QtScript -I../../../../../include -I. -I..
-I../../lib/components -I../../lib/sdk -I../../lib/extension -I../../lib/uilib
-I../../lib/shared -I../propertyeditor -I../../../../shared/qtpropertybrowser
-I../../../../shared/qtgradienteditor -I../../../../shared/findwidget
-I../objectinspector -I../signalsloteditor -I../formeditor -I../widgetbox
-I../buddyeditor -I../taskmenu -I../propertyeditor -I../taskmenu
-I../../../../shared/qt
propertybrowser -I../tabordereditor -I.moc/release-shared
-I.uic/release-shared -x c++-header -c lib_pch.h -o
.pch/release-shared/QtDesignerComponents.gch/c++
cc1plus: warning: the stabs debug format cannot be used with pre-compiled
headers [-Wdeprecated]
g++ -c -include .pch/release-shared/QtDesignerComponents -O2
-fstack-protector-strong -Wformat -Werror=format-security -D_FORTIFY_SOURCE=2
-I/usr/include/freetype2 -gstabs -O2 -D_REENTRANT -fvisibility=hidden
-fvisibility-inlines-hidden -Wall -W -fPIC -DQT_STATICPLUGIN
-DQDESIGNER_COMPONENTS_LIBRARY -DQT_NO_DEBUG -DQT_SCRIPT_LIB -DQT_XML_LIB
-DQT_GUI_LIB -DQT_CORE_LIB -D_LARGEFILE64_SOURCE -D_LARGEFILE_SOURCE
-DQT_SHARED -I../../../../../mkspecs/linux-g++ -I.
-I../../../../../include/QtDesigner -I../../../../../include/QtCore
-I../../../../../include/QtGui -I../../../../../include/QtXml
-I../../../../../include/QtScript -I../../../../../include -I. -I..
-I../../lib/components -I../../lib/sdk -I../../lib/extension -I../../lib/uilib
-I../../lib/shared -I../propertyeditor -I../../../../shared/qtpropertybrowser
-I../../../../shared/qtgradienteditor -I../../../../shared/findwidget
-I../objectinspector -I../signalsloteditor -I../formeditor -I../widgetbox
-I../buddyeditor -I../taskmenu -I..
/propertyeditor -I../taskmenu -I../../../../shared/qtpropertybrowser
-I../tabordereditor -I.moc/release-shared -I.uic/release-shared -o
.obj/release-shared/qdesigner_components.o qdesigner_components.cpp
In file included from command-line:0:0:
/usr/include/stdc-predef.h:59:1: fatal error:
.pch/release-shared/QtDesignerComponents: No such file or directory
#endif
^
compilation terminated.
make[7]: *** [.obj/release-shared/qdesigner_components.o] Error 1
...
The attached patch fixes this by doing as on powerpc.
Thanks in advance,
Roland
-- System Information:
Debian Release: 7.0
APT prefers unreleased
APT policy: (500, 'unreleased'), (500, 'unstable')
Architecture: powerpcspe (ppc)
Kernel: Linux 3.9.0-dirty (SMP w/2 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) (ignored: LC_ALL
set to en_GB.UTF-8)
Shell: /bin/sh linked to /bin/dash
diff -ruN test/qt4-x11-4.8.6+git64-g5dc8b2b+dfsg/debian/control qt4-x11-4.8.6+git64-g5dc8b2b+dfsg/debian/control
--- test/qt4-x11-4.8.6+git64-g5dc8b2b+dfsg/debian/control 2014-08-23 19:48:58.0 +0200
+++ qt4-x11-4.8.6+git64-g5dc8b2b+dfsg/debian/control 2014-12-15 11:13:31.166543900 +0100
@@ -10,7 +10,7 @@
Timo Jyrinki t...@debian.org
Build-Depends: debhelper (= 9),
dpkg-dev (= 1.16.1),
- firebird-dev [amd64 armel i386 ia64 kfreebsd-amd64 kfreebsd-i386 mips mipsel powerpc s390 sh4 sparc],
+ firebird-dev [amd64 armel i386 ia64 kfreebsd-amd64 kfreebsd-i386 mips mipsel powerpc powerpcspe s390 sh4 sparc],
flex,
freetds-dev,
libasound2-dev [linux-any],
@@ -205,7 +205,7 @@
libqt4-dev package.
Package: libqt4-sql-ibase
-Architecture: amd64 armel i386 ia64 kfreebsd-amd64 kfreebsd-i386 mips mipsel powerpc s390 sh4 sparc
+Architecture: amd64 armel i386 ia64 kfreebsd-amd64 kfreebsd-i386 mips mipsel powerpc powerpcspe s390 sh4 sparc
Multi-Arch: same
Pre-Depends: ${misc:Pre-Depends}
Depends: ${misc:Depends}, ${shlibs:Depends}
diff -ruN test/qt4-x11-4.8.6+git64-g5dc8b2b+dfsg/debian/rules qt4-x11-4.8.6+git64-g5dc8b2b+dfsg/debian/rules
--- test/qt4-x11-4.8.6+git64-g5dc8b2b+dfsg/debian/rules 2014-08-23 17:27:36.0 +0200
+++ qt4-x11-4.8.6+git64-g5dc8b2b+dfsg/debian/rules 2014-12-15 11:13:44.182643703 +0100
@@ -82,7 +82,7 @@
endif
endif
Bug#773213: Bug filed to upstream too
Since upstream git repo has the same problem I filed a bug there too: https://bugzilla.gnome.org/show_bug.cgi?id=741587 -Mikko -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#448209: xsane: turn off the bulb/light between scans
Hello, no answer since 2007. So i close this bug. Thank you for spending your time helping to make Debian better with this bug report. If the bug still occurs please file a new bug against sane-backends. CU Jörg -- New: GPG Fingerprint: 63E0 075F C8D4 3ABB 35AB 30EE 09F8 9F3C 8CA1 D25D GPG key (long) : 09F89F3C8CA1D25D GPG Key: 8CA1D25D CAcert Key S/N : 0E:D4:56 Old (will be revoked after 2014-12-31): pgp Fingerprint: 7D13 3C60 0A10 DBE1 51F8 EBCB 422B 44B0 BE58 1B6E pgp Key: BE581B6E Jörg Frings-Fürst D-54526 Niederkail Threema: SYR8SJXB IRC: j_...@freenode.net j_...@oftc.net signature.asc Description: This is a digitally signed message part
Bug#767356: xserver-xorg-core: segfaults when starting on an AMD APU at glamor_set_screen_pixmap from within radeon_drv (Failed to create fbo, incomplete attachment)
On 12.12.2014 17:48, Wim Lewis wrote: Package: xserver-xorg-core Version: 2:1.16.2.901-1 Followup-For: Bug #767356 Dear Maintainer, Xorg segfaults with a backtrace at startup on my AMD desktop with integrated (Radeon KAVERI) graphics. This looks like the same problem as Yaroslav Halchenko's report in bug #767356. I've attached a more detailed backtrace. I had this problem in 1.16.1.901 in testing, upgraded to 1.16.2.901 from unstable, no apparent change. There is discussion of what looks like the same bug at: https://www.libreoffice.org/bugzilla/show_bug.cgi?id=84186 Let's continue there. I just added a suggestion for getting more information. -- Earthling Michel Dänzer | http://www.amd.com Libre software enthusiast | Mesa and X developer -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#772543: python-psutil: severak filehandle leaks
patch. Testing it now. On 16 December 2014 at 09:22, Marc Leeman marc.lee...@gmail.com wrote: Just to let you know that the current version upstream is not enough to solve the problem. I copied their version in the jessie release, backported it to wheezy and tried it. After less than 24h, the system is stuck again, The problem can be traced to: @wrap_exceptions def threads(self): Where there is still an open that does not close properly: 2014-12-16 09:21:21,185 - com.barco.mgs.TeamMgrM56094 - INFO - start - Received request to start a team sid T10621 - wid W90616 2014-12-16 09:21:21,185 - com.barco.mgs.TeamMgrM56094 - ERROR - start - [' File /usr/lib/pymodules/python2.7/Mgs2/Team/TeamMgr.py, line 831, in start\nlimit = status.cpu_percent\n', ' File /usr/lib/pymodules/python2.7/Mgs2/SystemStatusBase.py, line 346, in cpu_percent\n', ' File /usr/lib/pymodules/python2.7/Mgs2/SystemStatusBase.py, line 349, in get_cpu_percent\n', ' File /usr/lib/python2.7/dist-packages/psutil/__init__.py, line 1509, in cpu_percent\n_last_cpu_times = cpu_times()\n', ' File /usr/lib/python2.7/dist-packages/psutil/__init__.py, line 1439, in cpu_times\nreturn _psplatform.cpu_times()\n', ' File /usr/lib/python2.7/dist-packages/psutil/_pslinux.py, line 215, in cpu_times\nwith open(\'/proc/stat\', \'rb\') as f:\n'] 2014-12-16 09:21:21,186 - com.barco.mgs.TeamMgrM56094 - ERROR - start - [Errno 24] Too many open files: '/proc/stat' 2014-12-16 09:21:21,186 - com.barco.mgs.TeamMgrM56094 - ERROR - start - Error during worker creation [Errno 24] Too many open files: '/proc/stat' ...snip... rtsp_mgs. 26609 29136root txt unknown /proc/26609/task/29136/exe (readlink: Permission denied) rtsp_mgs. 26609 29136root NOFD /proc/26609/task/29136/fd (opendir: Permission denied) rtsp_mgs. 26609 29144root cwd unknown /proc/26609/task/29144/cwd (readlink: Permission denied) rtsp_mgs. 26609 29144root rtd unknown /proc/26609/task/29144/root (readlink: Permission denied) rtsp_mgs. 26609 29144root txt unknown /proc/26609/task/29144/exe (readlink: Permission denied) rtsp_mgs. 26609 29144root NOFD /proc/26609/task/29144/fd (opendir: Permission denied) rtsp_mgs. 26609 29147root cwd unknown /proc/26609/task/29147/cwd (readlink: Permission denied) rtsp_mgs. 26609 29147root rtd unknown /proc/26609/task/29147/root (readlink: Permission denied) rtsp_mgs. 26609 29147root txt unknown /proc/26609/task/29147/exe (readlink: Permission denied) rtsp_mgs. 26609 29147root NOFD /proc/26609/task/29147/fd (opendir: Permission denied) rtsp_mgs. 26609 29148root cwd unknown /proc/26609/task/29148/cwd (readlink: Permission denied) rtsp_mgs. 26609 29148root rtd unknown /proc/26609/task/29148/root (readlink: Permission denied) rtsp_mgs. 26609 29148root txt unknown /proc/26609/task/29148/exe (readlink: Permission denied) rtsp_mgs. 26609 29148root NOFD /proc/26609/task/29148/fd (opendir: Permission denied) rtsp_mgs. 26609 29149root cwd unknown /proc/26609/task/29149/cwd (readlink: Permission denied) rtsp_mgs. 26609 29149root rtd unknown /proc/26609/task/29149/root (readlink: Permission denied) rtsp_mgs. 26609 29149root txt unknown /proc/26609/task/29149/exe (readlink: Permission denied) rtsp_mgs. 26609 29149root NOFD /proc/26609/task/29149/fd (opendir: Permission denied) rtsp_mgs. 26609 29152root cwd unknown /proc/26609/task/29152/cwd (readlink: Permission denied) rtsp_mgs. 26609 29152root rtd unknown /proc/26609/task/29152/root (readlink: Permission denied) rtsp_mgs. 26609 29152root txt unknown /proc/26609/task/29152/exe (readlink: Permission denied) rtsp_mgs. 26609 29152root NOFD /proc/26609/task/29152/fd (opendir: Permission denied) rtsp_mgs. 26609 29153root cwd unknown /proc/26609/task/29153/cwd (readlink: Permission denied) rtsp_mgs. 26609 29153root rtd unknown /proc/26609/task/29153/root (readlink: Permission denied) rtsp_mgs. 26609 29153root txt unknown /proc/26609/task/29153/exe (readlink: Permission denied) rtsp_mgs. 26609 29153root NOFD /proc/26609/task/29153/fd (opendir: Permission denied) rtsp_mgs. 26609 29155root cwd unknown /proc/26609/task/29155/cwd (readlink: Permission denied) rtsp_mgs. 26609 29155root rtd unknown /proc/26609/task/29155/root (readlink: Permission denied) rtsp_mgs. 26609 29155root txt unknown /proc/26609/task/29155/exe (readlink: Permission denied) rtsp_mgs. 26609 29155root NOFD /proc/26609/task/29155/fd (opendir: Permission denied) rtsp_mgs. 26609 29157root cwd unknown /proc/26609/task/29157/cwd (readlink: Permission denied)
Bug#772975: Processed: reassign 772975 to php5-apc
Control: reassign -1 php-apc I didn't mean php5-apcu, I meant php-apc from stable :) O. On Mon, Dec 15, 2014, at 21:51, Andrei POPESCU wrote: reassign 772975 php5-apcu thanks On Lu, 15 dec 14, 15:00:11, Debian Bug Tracking System wrote: Processing commands for cont...@bugs.debian.org: reassign 772975 php5-apc Bug #772975 [php5-fpm] Random Segfault(11) php5-fpm when Overload Bug reassigned from package 'php5-fpm' to 'php5-apc'. Warning: Unknown package 'php5-apc' ^^^ Assuming you meant php5-apcu. 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 Email had 1 attachment: + signature.asc 1k (application/pgp-signature) -- Ondřej Surý ond...@sury.org Knot DNS (https://www.knot-dns.cz/) – a high-performance DNS server -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#522083: xsane: No suggestion of user not being in required group scanner
Hello, no answer since 2009. And the permissions are from sane-backends. So I close this bug. Thank you for spending your time helping to make Debian better with this bug report. If the bug still occurs please file a new bug against sane-backends. CU Jörg -- New: GPG Fingerprint: 63E0 075F C8D4 3ABB 35AB 30EE 09F8 9F3C 8CA1 D25D GPG key (long) : 09F89F3C8CA1D25D GPG Key: 8CA1D25D CAcert Key S/N : 0E:D4:56 Old (will be revoked after 2014-12-31): pgp Fingerprint: 7D13 3C60 0A10 DBE1 51F8 EBCB 422B 44B0 BE58 1B6E pgp Key: BE581B6E Jörg Frings-Fürst D-54526 Niederkail Threema: SYR8SJXB IRC: j_...@freenode.net j_...@oftc.net signature.asc Description: This is a digitally signed message part
Bug#397515: does not play well with xinerama
Hello, Debian 4.0 is currently unsupported. So I close this bug. Thank you for spending your time helping to make Debian better with this bug report. If the bug still occurs please file a new one. CU Jörg -- New: GPG Fingerprint: 63E0 075F C8D4 3ABB 35AB 30EE 09F8 9F3C 8CA1 D25D GPG key (long) : 09F89F3C8CA1D25D GPG Key: 8CA1D25D CAcert Key S/N : 0E:D4:56 Old (will be revoked after 2014-12-31): pgp Fingerprint: 7D13 3C60 0A10 DBE1 51F8 EBCB 422B 44B0 BE58 1B6E pgp Key: BE581B6E Jörg Frings-Fürst D-54526 Niederkail Threema: SYR8SJXB IRC: j_...@freenode.net j_...@oftc.net signature.asc Description: This is a digitally signed message part
Bug#771274: Follow-up on blkid command injection issue (Bug#771274: fixed in util-linux 2.25.2-4)
Hello Salvatore Bonaccorso. On Mon, Dec 15, 2014 at 08:50:19PM +0100, Salvatore Bonaccorso wrote: Hi Andreas, Sorry, I cannot check it right now myself, but could you have a look at http://www.openwall.com/lists/oss-security/2014/12/15/3 . Apparently the initial patch had an issue, and there is also a followup on this. Thanks for your followup. I cherry-picked the actual upstream commit (read: karel zaks version) and did not use the patch submitted for review (read: sebastians version). This should mean that the fix made by Karel Zak should be included in our package. (Anyone digging deeper into this would ofcourse be appreciated.) 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#416264: should not restore window size/position
Hello, Debian 4.0 is currently unsupported. So I close this bug. Thank you for spending your time helping to make Debian better with this bug report. If the bug still occurs please file a new one. CU Jörg -- New: GPG Fingerprint: 63E0 075F C8D4 3ABB 35AB 30EE 09F8 9F3C 8CA1 D25D GPG key (long) : 09F89F3C8CA1D25D GPG Key: 8CA1D25D CAcert Key S/N : 0E:D4:56 Old (will be revoked after 2014-12-31): pgp Fingerprint: 7D13 3C60 0A10 DBE1 51F8 EBCB 422B 44B0 BE58 1B6E pgp Key: BE581B6E Jörg Frings-Fürst D-54526 Niederkail Threema: SYR8SJXB IRC: j_...@freenode.net j_...@oftc.net signature.asc Description: This is a digitally signed message part
Bug#252580: xsane: the image viewer does not remember the directory
Hello, Debian 4.0/5.0 is currently unsupported. So I close this bug. Thank you for spending your time helping to make Debian better with this bug report. If the bug still occurs please file a new one. CU Jörg -- New: GPG Fingerprint: 63E0 075F C8D4 3ABB 35AB 30EE 09F8 9F3C 8CA1 D25D GPG key (long) : 09F89F3C8CA1D25D GPG Key: 8CA1D25D CAcert Key S/N : 0E:D4:56 Old (will be revoked after 2014-12-31): pgp Fingerprint: 7D13 3C60 0A10 DBE1 51F8 EBCB 422B 44B0 BE58 1B6E pgp Key: BE581B6E Jörg Frings-Fürst D-54526 Niederkail Threema: SYR8SJXB IRC: j_...@freenode.net j_...@oftc.net signature.asc Description: This is a digitally signed message part
Bug#311198: xsane: Sometimes, one forgets whether's one has scanned or not.
Hello, Debian 3.1 is currently unsupported. So I close this bug. Thank you for spending your time helping to make Debian better with this bug report. If the bug still occurs please file a new one. CU Jörg -- New: GPG Fingerprint: 63E0 075F C8D4 3ABB 35AB 30EE 09F8 9F3C 8CA1 D25D GPG key (long) : 09F89F3C8CA1D25D GPG Key: 8CA1D25D CAcert Key S/N : 0E:D4:56 Old (will be revoked after 2014-12-31): pgp Fingerprint: 7D13 3C60 0A10 DBE1 51F8 EBCB 422B 44B0 BE58 1B6E pgp Key: BE581B6E Jörg Frings-Fürst D-54526 Niederkail Threema: SYR8SJXB IRC: j_...@freenode.net j_...@oftc.net signature.asc Description: This is a digitally signed message part
Bug#574821: Multipage: Support for Djvu, OCR
Hello, no answer since 2010. So I close this bug. Thank you for spending your time helping to make Debian better with this bug report. If the bug still occurs please file a new one. CU Jörg -- New: GPG Fingerprint: 63E0 075F C8D4 3ABB 35AB 30EE 09F8 9F3C 8CA1 D25D GPG key (long) : 09F89F3C8CA1D25D GPG Key: 8CA1D25D CAcert Key S/N : 0E:D4:56 Old (will be revoked after 2014-12-31): pgp Fingerprint: 7D13 3C60 0A10 DBE1 51F8 EBCB 422B 44B0 BE58 1B6E pgp Key: BE581B6E Jörg Frings-Fürst D-54526 Niederkail Threema: SYR8SJXB IRC: j_...@freenode.net j_...@oftc.net signature.asc Description: This is a digitally signed message part
Bug#383535: xsane: mention rebooting with scanner already on
Hello, answered in 2006. So I close this bug. Thank you for spending your time helping to make Debian better with this bug report. If the bug still occurs please file a new one. CU Jörg -- New: GPG Fingerprint: 63E0 075F C8D4 3ABB 35AB 30EE 09F8 9F3C 8CA1 D25D GPG key (long) : 09F89F3C8CA1D25D GPG Key: 8CA1D25D CAcert Key S/N : 0E:D4:56 Old (will be revoked after 2014-12-31): pgp Fingerprint: 7D13 3C60 0A10 DBE1 51F8 EBCB 422B 44B0 BE58 1B6E pgp Key: BE581B6E Jörg Frings-Fürst D-54526 Niederkail Threema: SYR8SJXB IRC: j_...@freenode.net j_...@oftc.net signature.asc Description: This is a digitally signed message part
Bug#773271: libpoppler46: Greek letter \mu not displayed in evince or xpdf
Package: libpoppler46 Version: 0.26.5-2 Severity: normal Example pdf: http://www.atmos-meas-tech.net/6/2169/2013/amt-6-2169-2013.pdf Throughout this document, the greek letter \mu is not shown, just white space instead. See e.g. page 2177, right column, bottom line: about 4 rad should be about 4 μrad. This can be seen (or rather not seen) in evince and xpdf. It works in older versions of evince (wheezy's evince 3.4 works), and it works in iceweasel's build-in pdf viewer. thanks for considering Florian -- System Information: Debian Release: 8.0 APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.16.0-4-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) (ignored: LC_ALL set to en_US.UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages libpoppler46 depends on: ii libc6 2.19-13 ii libfontconfig1 2.11.0-6.3 ii libfreetype6 2.5.2-2 ii libjpeg62-turbo1:1.3.1-11 ii liblcms2-2 2.6-3+b3 ii libopenjpeg5 1:1.5.2-3 ii libpng12-0 1.2.50-2+b2 ii libstdc++6 4.9.1-19 ii libtiff5 4.0.3-10+b4 ii multiarch-support 2.19-13 Versions of packages libpoppler46 recommends: ii poppler-data 0.4.7-1 libpoppler46 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#408170: xsane: lineart scaling ugly
Hello, xsane 0.991-* is currently unsupported. So I close this bug. Thank you for spending your time helping to make Debian better with this bug report. If the bug still occurs please file a new one. CU Jörg -- New: GPG Fingerprint: 63E0 075F C8D4 3ABB 35AB 30EE 09F8 9F3C 8CA1 D25D GPG key (long) : 09F89F3C8CA1D25D GPG Key: 8CA1D25D CAcert Key S/N : 0E:D4:56 Old (will be revoked after 2014-12-31): pgp Fingerprint: 7D13 3C60 0A10 DBE1 51F8 EBCB 422B 44B0 BE58 1B6E pgp Key: BE581B6E Jörg Frings-Fürst D-54526 Niederkail Threema: SYR8SJXB IRC: j_...@freenode.net j_...@oftc.net signature.asc Description: This is a digitally signed message part
Bug#773272: xapian-omega: Missing dependencies libhtml-parser-perl and libemail-outlook-message-perl
Package: xapian-omega Version: 1.2.12-1 Severity: normal Dear Maintainer, Missing dependencies; the binary /usr/lib/xapian-omega/bin/outlookmsg2html did not correctly work, until I manually installed the missing dependencies libemail-outlook-message-perl and libhtml-parser-perl. -- System Information: Debian Release: 7.7 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 3.2.0-4-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages xapian-omega depends on: ii libc62.13-38+deb7u6 ii libgcc1 1:4.7.2-5 ii libmagic15.11-2+deb7u6 ii libpcre3 1:8.30-5 ii libstdc++6 4.7.2-5 ii libxapian22 1.2.12-2 Versions of packages xapian-omega recommends: ii apache2 2.2.22-13+deb7u3 ii apache2-mpm-prefork [httpd-cgi] 2.2.22-13+deb7u3 Versions of packages xapian-omega suggests: ii antiword 0.37-8 ii catdoc 0.94.4-1.1 pn catdvi none pn djvulibre-bin none ii ghostscript9.05~dfsg-6.3+deb7u1 ii libemail-outlook-message-perl 0.911-1 ii libhtml-parser-perl3.69-2 ii libwpd-tools 0.9.4-3 ii libwps-tools 0.2.7-1 ii perl 5.14.2-21+deb7u2 ii poppler-utils [xpdf-utils] 0.18.4-6 pn rpmnone ii unrtf 0.19.3-1.1+b1 ii unzip 6.0-8 -- 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#764915: [DAViCal-devel] Bug#764915: davical: trying to push a event before 1900 results in response 500
On Tue, 16 Dec 2014 08:49:38 +0100 Florian Schlichting f...@debian.org
wrote:
Hi Florian,
trying to push a event started befor 1900 results in a database
error and therefor in a 500 response to the client.
could you say a little more about your patch, making it easier for me
to understand why it is effective on those particular dates (and does
it have effects on more current dates?), whether it's a change that
might need to be made in other parts of the code as well?
The underlaying database refuses to accept 18961224 as date while
19011224 works out pretty well. My works for me changes 18961224
or 19011224 into 18961224T00Z or 19011224T00Z which both
are accepted as dates.
A workaround patch is attached.
Why is it a workaround, what would be the proper solution?
Better: It is a works for me. It may wash your windows,
mend your fences, mow your lawn...
diff --git a/inc/caldav-PUT-functions.php
b/inc/caldav-PUT-functions.php index a1c9e3d..3f1b7d4 100644
--- a/inc/caldav-PUT-functions.php
+++ b/inc/caldav-PUT-functions.php
@@ -1278,12 +1278,16 @@ function write_resource( DAVResource
$resource, $caldav_data, DAVResource $colle if ( $first-GetType()
== 'VTODO' ) $due = $first-GetPValue('DUE');
$calitem_params[':due'] = $due; $dtstart =
$first-GetPValue('DTSTART');
- if ( empty($dtstart) ) $dtstart = $due;
+ if ( empty($dtstart) ) $dtstart = $due;
+ if (preg_match(/^[0-9][0-9][0-9][0-9][01][0-9][0-3][0-9]$/,
$dtstart))
+ $dtstart = $dtstart . T00Z;
$calitem_params[':dtstart'] = $dtstart;
$dtend = $first-GetPValue('DTEND');
if ( isset($dtend) $dtend != '' ) {
dbg_error_log( 'PUT', ' DTEND: %s, DTSTART: %s, DURATION:
%s', $dtend, $dtstart, $first-GetPValue('DURATION') );
+if (preg_match(/^[0-9][0-9][0-9][0-9][01][0-9][0-3][0-9]$/,
$dtend))
+ $dtend = $dtend . T00Z;
$calitem_params[':dtend'] = $dtend;
$dtend = ':dtend';
}
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#773273: error when using SYMPHONY libraries in testing/unstable with clang
Package: coinor-libsymphony3 Version: 5.6.1-1 When using the SYMPHONY libraries in testing/unstable with clang, I run into errors like usr/lib/x86_64-linux-gnu/libSym.so.3: undefined symbol: omp_get_thread_num because clang currently does not support OpenMP. Would it be possible for the time being to actually build the SYMPHONY libraries with OpenMP support disabled (i.e., configuring with --disable-openmp)? Kind regards, Markus Mayer -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#773238: [Pkg-xfce-devel] Bug#773238: xfce4-panel: notification-area broken?
On lun., 2014-12-15 at 21:59 +0100, oggesjolin wrote: Package: xfce4-panel Version: 4.8.6-4 Severity: normal Dear Maintainer, For reasons unknown, Dropbox icon does not show in the notification area panel- plugin, other running applications show (wicd/spotify/xchat) Try with a different panel size. It might just be that dropbox doesn't ship correct icon size. You can also strace the panel plugin (systray.so) to check if there's any obvious error. I tried add a new 'notification-area', and noticed it was greyed out. Seems I can no longer add a 'notification-area' to any panel. Well, yes, multiple systray / notification area don't make any sense. Regards, -- Yves-Alexis signature.asc Description: This is a digitally signed message part
Bug#772708: ssl handshake fail with http proxy and talk.google.com 443 port config
I wanted to send to the bug and not to you directly, sorry for the inconvenence On Tue, Dec 16, 2014 at 11:08 AM, Javier Barroso javibarr...@gmail.com wrote: Thank you very much On Sat, Dec 13, 2014 at 5:07 PM, Ari Pollak a...@debian.org wrote: Fix is here: https://developer.pidgin.im/ticket/16473 If you need to use old-style SSL with 2.10.11, you must configure the 'NSS preferences' plugin and enable again the 'TLS_RSA_WITH_RC4_128 (0x0005)' cipher suite. This is probably insecure and you should migrate to a more recent setup. Could be this added to NEWS or README at /usr/share/doc/pidgin ? Thanks ! -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#773274: installation-reports: parted_server segfault
Package: installation-reports Version: 20141216-00:08 When attempting an install using a daily image, I ran into a case where parted_server segfaults with the following: parted_server[29651]: segfault at 8 ip 0040b4b1 sp 7fff5d7c54c0 error 4 in parted_server[40+12000] I tried it several times and attempted to distill it down to the simplest case I could. To repeat: 1) create a partition and mark it for encryption 2) configure encryption, set it up (don't erase to save time, but that doesn't matter), finish encryption 3) mark newly created encrypted volume as for LVM 4) configure LVM, create a volume group and a logical volume, finish The menu will freeze at Detecting filesystems and the above error is in syslog. Setting up LVM on a non-encrypted disk works just fine, I didn't see the problem unless it was encrypted. Thanks, -- Matt Taggart tagg...@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#773217: GIMIAS code source
Dear GIMIAS team, Thanks very much for releasing GIMIAS as open source software. I am trying to access the GIMIAS source code, it appears as if the source code tarball are not accessible anymore from the files section in sourceforge.net. I also tried doing an svn checkout from the official website: http://wiki.gimias.org/mediawiki/HowToBuildGimias_1_6_InWindows_Step_1 However it fails: $ svn list https://svn.gimias.org/svn/toolkit/gimias/stable/GIMIAS_1_6 Authentication realm: https://svn.gimias.org:443 VisualSVN Server Password for 'mathieu': Authentication realm: https://svn.gimias.org:443 VisualSVN Server Username: Password for '': Authentication realm: https://svn.gimias.org:443 VisualSVN Server Username: Password for '': svn: E215004: Unable to connect to a repository at URL 'https://svn.gimias.org/svn/toolkit/gimias/stable/GIMIAS_1_6' svn: E215004: No more credentials or we tried too many times. Authentication failed It looks as if there is a typo in the wiki page, the SVN may in fact be located at: $ svn list https://svn.gimias.org/repos/toolkit/gimias/stable/GIMIAS_1_6/ CTestConfig.cmake Data/ Resources/ src/ thirdParty/ However I can only make the `list` and `cat` command work, the checkout command always fails: $ svn co https://svn.gimias.org/repos/toolkit/gimias/stable/GIMIAS_1_6/ Authentication realm: https://svn.gimias.org:443 GIMIAS SVN Server Password for 'mathieu': Authentication realm: https://svn.gimias.org:443 GIMIAS SVN Server Username: Password for '': Authentication realm: https://svn.gimias.org:443 GIMIAS SVN Server Username: Password for '': svn: E215004: No more credentials or we tried too many times. Authentication failed Using: $ svn --version svn, version 1.8.10 (r1615264) compiled Nov 11 2014, 05:50:14 on x86_64-pc-linux-gnu For some reason I can use an older version of svn to do the checkout (vn, version 1.6.17), however this is quite an old version and I can no longer use it at work. Could you please check the svn server side configuration as to why recent svn client are not accepted anymore (anonymous login) Thanks much ! -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#753809: ginkgocadx: will not display studies
Hi Karsten, On Wed, Nov 26, 2014 at 11:40:02PM +0100, Karsten Hilbert wrote: Is there any news regarding this bug ? It is rather serious: Because of this bug Ginkgo CADx is rather useless for serious clinical care on Debian. I admit I feel helpless about this issue. However, if you think that this issue is serious than you should tag the bug that way to make more people aware of it. The consequence would be that ginkgocadx will not be released with Jessie if it will not be fixed. I keep upstream in CC (Carlos, feel free to read the whole story here [1]). Kind regards Andreas. [1] https://bugs.debian.org/753809 -- http://fam-tille.de -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#725402: debian-handbook: Minor style and readability enhancements
Control: tag -1 + moreinfo Hello Carey, sorry for the delay in getting back to you... On Sat, 05 Oct 2013, Carey wrote: A number of minor suggested updates for English language version. These are to improve readability/style only and are not corrections to content. Your bug report doesn't contain any attachment. Do you still have those suggested updates somewhere? Cheers, -- Raphaël Hertzog ◈ Debian Developer Support Debian LTS: http://www.freexian.com/services/debian-lts.html Learn to master Debian: http://debian-handbook.info/get/ -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#773275: dh-make: fails to create native package with --defaultless
Package: dh-make Version: 1.20140617 Severity: important Hi, native packages cannot be created with --defaultless option. Steps to reproduce: mkdir /tmp/example-package-1.0 cd /tmp/example-package-1.0 dh_make -c mit -s -n -p example-package_1.0 -y -d Output: [...] Date : Tue, 16 Dec 2014 10:50:58 + Package Name : example-package Version : 1.0 License : mit Type of Package : Single Default debian and package class templates will not be applied. Currently there is no top level Makefile. This may require additional tuning. Cannot find rules file for rules format dh7. -- Benjamin Drung System Developer ProfitBricks GmbH - The IaaS-Company Greifswalder Str. 207 D - 10405 Berlin Mail: benjamin.dr...@profitbricks.com Fax: +49 30 577 008 598 URL: http://www.profitbricks.com Sitz der Gesellschaft: Berlin. Registergericht: Amtsgericht Charlottenburg, HRB 125506 B. Geschäftsführer: Andreas Gauger, Achim Weiss. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#773158: nautilus-dropbox: no notification icon is shown
On Mon, Dec 15, 2014 at 02:33:35PM +0900, Norbert Preining wrote: [...] Any suggestion how to debug this behaviour? No idea. I believe the part that generates the notification area icon/indicator applet icon thing is within the closed source portion of dropbox. -- Kind regards, Loong Jin signature.asc Description: Digital signature
Bug#753809: ginkgocadx: will not display studies
On Tue, Dec 16, 2014 at 11:48 AM, Andreas Tille andr...@an3as.eu wrote: Hi Karsten, On Wed, Nov 26, 2014 at 11:40:02PM +0100, Karsten Hilbert wrote: Is there any news regarding this bug ? It is rather serious: Because of this bug Ginkgo CADx is rather useless for serious clinical care on Debian. I admit I feel helpless about this issue. However, if you think that this issue is serious than you should tag the bug that way to make more people aware of it. The consequence would be that ginkgocadx will not be released with Jessie if it will not be fixed. I keep upstream in CC (Carlos, feel free to read the whole story here [1]). Here is the only technical information in this bug report: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=753809#15 [...] We found many issues in GDCM 2.x which is provided with debian bundled ITK version. [...] AFAIR ITK/GDCM upstream has been fairly reluctant to apply patches. [...] What exactly do you expect from me ? Please stop CCing me on FUDs. I've happily applied patch for better integration of current ITK and GDCM see recent changelog, so stop saying things like fairly reluctant, or at least include the context. As for the so-called many issues in GDCM 2.x, please include actual details to reproduce them. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#773276: usbredir: missed debug packages
Source: usbredir Severity: important Hi, debug packages are missed, than is impossible debug a crash with gdb using usbredir from packages. Can you add debug packages please? Thanks for any reply and sorry for my bad english. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#768156: general: dpkg frontend inconsistent
reassign 768156 dpkg,ucf thanks On Mittwoch, 5. November 2014, Julien Cristau wrote: On Wed, Nov 5, 2014 at 17:53:50 +0100, Holger Levsen wrote: On Mittwoch, 5. November 2014, Michal Suchanek wrote: I was upgrading my system and several times I was asked for installing a new configuration file. Sometimes the question is posed in teletype style frontend sometimes in colour character terminal TUI style frontend. which tool did you use (how) to upgrade? Pretty sure this is ucf vs dpkg's conffile prompt. reassigning, so this can be sorted out between those two packages. signature.asc Description: This is a digitally signed message part.
Bug#773140: unblock: rabbitmq-server/3.3.5-1.1
rabbitmq-server maintainers, are there any other RC bugs that you're planning to file on the package? No other RC bugs. I submitted https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=773259, which I hope has an appropriate severity of important. I've asked a couple developers their opinion on whether rabbitmq-server attempting to use SSLv3 [1] would be a bug. Rabbit's method to verify SSLv3 is disabled [2] uses s_client with the -ssl3 option which no longer works [3]. I believe this is a non-issue since SSLv3 is disabled in Jessie [4], but I would appreciate a confirmation. I apologize for the late bugs and 3.4.1-1 debacle, I had some terrible misunderstandings. -Blair 1. https://groups.google.com/forum/#!topic/rabbitmq-users/jk45xOPqeGY 2. https://gist.github.com/michaelklishin/3f47bae850bdd9f1a79a 3. https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=766297 4. https://lists.debian.org/debian-release/2014/11/msg00690.html -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#765076: general: No way to have a clean chroot for building packages
control: reassign -1 debootstrap control: retitle -1 variant=buildd should not install init systems Hi, On Montag, 13. Oktober 2014, Joey Hess wrote: It seems reasonable for debootstrap --variant=buildd to omit any init systems, if it doesn't already. seems reasonable indeed, reassigning accordingly. cheers, Holger signature.asc Description: This is a digitally signed message part.
Bug#691983: debian-handbook: eleventh chapter should suggest a more general tool for generating SSL certs
Hi, On Wed, 31 Oct 2012, Francesco Poli (wintermute) wrote: I don't know of anything good. Feel free to file a new bug once you've found the tool that we should recommend here! Couldn't it be /usr/lib/ssl/misc/CA.pl (from package openssl), as suggested by section 11.7.3.3.1. Configuring the Server [1] for the LDAP server configuration? easy-rsa has been split in its own package in jessie so I guess that we will keep documenting easy-rsa and mention that it has its own package now. Cheers, -- Raphaël Hertzog ◈ Debian Developer Support Debian LTS: http://www.freexian.com/services/debian-lts.html Learn to master Debian: http://debian-handbook.info/get/ -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#773277: RFS: libatf/0.21-1 [ITP #766576]
Package: sponsorship-requests Severity: wishlist Dear mentors, I am looking for a sponsor for my package libatf * Package name: libatf Version : 0.21-1 Upstream Author : Julio Merino j...@julipedia.org * URL : https://github.com/jmmv/atf * License : BSD Section : libs It builds those binary packages: libatf - Automated Test Framework libraries libatf-dev - Automated Test Framework -- development files To access further information about this package, please visit the following URL: http://mentors.debian.net/package/libatf Alternatively, one can download the package with dget using this command: dget -x http://mentors.debian.net/debian/pool/main/liba/libatf/libatf_0.21-1.dsc Changes since last upload: None, this is my first upload. -- Craig
Bug#712281: xsane: Preview window empty/unusable
tags 712281 + moreinfo thanks Hello, xsane release 0.999-1 now in unstable. Please can you check whether the same bug still exists? CU Jörg -- New: GPG Fingerprint: 63E0 075F C8D4 3ABB 35AB 30EE 09F8 9F3C 8CA1 D25D GPG key (long) : 09F89F3C8CA1D25D GPG Key: 8CA1D25D CAcert Key S/N : 0E:D4:56 Old (will be revoked after 2014-12-31): pgp Fingerprint: 7D13 3C60 0A10 DBE1 51F8 EBCB 422B 44B0 BE58 1B6E pgp Key: BE581B6E Jörg Frings-Fürst D-54526 Niederkail Threema: SYR8SJXB IRC: j_...@freenode.net j_...@oftc.net signature.asc Description: This is a digitally signed message part
Bug#736588: debian-handbook: gendered language used when referring to subjects
On Sat, 25 Jan 2014, Raphael Hertzog wrote: Some authors express concern that this is ambiguous as 'they' and 'theirs' are often used as plural pronouns. In this case, a short explanation of the inclusive language in the foreword can help. If you're accepting patches, I'm happy to sort this out. It'd be largely a sed script followed by spot-checking the diff. I do accept patches, but those fixes are often better done by rewriting the sentence, either using a synonym to avoid the pronoun or by using passive voice. http://www.herodios.com/pronouns.html FWIW we're starting to work on the jessie version of the handbook, so now is the good time to consider submitting such patches... Cheers, -- Raphaël Hertzog ◈ Debian Developer Support Debian LTS: http://www.freexian.com/services/debian-lts.html Learn to master Debian: http://debian-handbook.info/get/ -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#769375: RFS: lightmdeditor/1.0-2 [ITP]
Hi Tobi, I have re-uploaded the package. The respective dsc file can be found at: http://mentors.debian.net/debian/pool/main/l/lightmdeditor/lightmdeditor_1.0.3-1.dsc In this I have fixed lot of things. Things done: *I have changed upstream versioning to make it more debian compatible. *I have included a watch file. *Fixed lintian errors relating control file, .desktop file *I have added self made icons as well just like you suggested. Things not yet done: Building images from high res svg to png at build time. I am certain I will find an efficient way to do this too. I am sorry for all the trouble but I am new to debian packaging and this is the first time I am doing it. I have read online documentation but I felt it's a bit confusing for beginners. Thank you for all the help. Regards, Bhavyanshu Parasher
Bug#773278: RFS: liblutok/0.4-1 [ITP #675626]
Package: sponsorship-requests Severity: wishlist Dear mentors, I am looking for a sponsor for my package liblutok * Package name: liblutok Version : 0.4-1 Upstream Author : Julio Merino j...@julipedia.org * URL : https://github.com/jmmv/lutok * License : BSD Section : libs It builds those binary packages: liblutok - lightweight C++ API for Lua liblutok-dev - library for lightweight C++ API for Lua -- development files To access further information about this package, please visit the following URL: http://mentors.debian.net/package/liblutok Alternatively, one can download the package with dget using this command: dget -x http://mentors.debian.net/debian/pool/main/libl/liblutok/liblutok_0.4-1.dsc Changes since the last upload: None, this is my first upload. Regards, Craig Rodrigues
Bug#772342: debian-edu-config: mounting homedirs via NFS doesn't work reliably
[Holger Levsen] Hi Wolfgang, thanks for confirming! Yes. Great to have it confirmed that there is a race condition involving nslcd, autofs and network-manager. The fact that it is hidden when network-manager is quicker is not really comforting, as it can trigger at any time if there is a slow dhcp server or some other problem related to the network. Did you manage to figure out if nslcd could be told to wait until the network is up? Did you try to restart it in the dhclient hook when the network is up? I suspect the latter is required to get a robust setup when machines change IP address, and the former is required to ensure nslcd always work after boot. -- Happy hacking Petter Reinholdtsen -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#773279: RFS: kyua/0.11-1 [ITP #766577]
Package: sponsorship-requests Severity: wishlist Dear mentors, I am looking for a sponsor for my package kyua * Package name: kyua Version : 0.11-1 Upstream Author : Julio Merino j...@julipedia.org * URL : https://github.com/jmmv/kyua * License : BSD Section : devel It builds those binary packages: kyua - Testing framework for infrastructure software To access further information about this package, please visit the following URL: http://mentors.debian.net/package/kyua Alternatively, one can download the package with dget using this command: dget -x http://mentors.debian.net/debian/pool/main/k/kyua/kyua_0.11-1.dsc Changes since the last upload: None, this is my first upload. Regards, Craig Rodrigues
Bug#773230: asterisk: CVE-2014-9374
On Mon, Dec 15, 2014 at 09:26:41PM +0100, Salvatore Bonaccorso wrote: Source: asterisk Version: 1:11.13.0~dfsg-1 Severity: important Tags: security upstream fixed-upstream Hi, the following vulnerability was published for asterisk. CVE-2014-9374[0]: | Double free vulnerability in the WebSocket Server (res_http_websocket | module) in Asterisk Open Source 11.x before 11.14.2, 12.x before 12.7.2, | and 13.x before 13.0.2 and Certified Asterisk 11.6 before 11.6-cert9 | allows remote attackers to cause a denial of service (crash) by sending | a zero length frame after a non-zero length frame. No description was found (try on a search engine) If you fix the vulnerability please also make sure to include the CVE (Common Vulnerabilities Exposures) id in your changelog entry. For further information see: [0] https://security-tracker.debian.org/tracker/CVE-2014-9374 Upstream's page: http://downloads.asterisk.org/pub/security/AST-2014-019.html 1.8 doesn't have websocket support and thus is not vulnrable. Patches for this and the previous issues is now finally commited to git (branch wheezy). Sadly I'll have to use t-p-u as Unstable has a Asterisk 13 due to my miscalculation. -- 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#773274: parted_server segfault
I spent some more time repeating the bug and realized I was missing a detail and I also distilled the test further. Here are the new steps: 1) create two partitions, mark them both for encryption, accept their encryption settings 2) run Configure encrypted volumes, create the 2 volumes, finish 3) After returning from #2, mark the first encrypted volume as for LVM, leave the second to it's default of ext4 4) Configure LVM, create vg, mark the first encrypted volume as a pv, finish. It attempts to go back to the partitioner and then the partman_server segfault happens with the menu hung on Detecting file systems. Also, I determined a few other things * It's not necessary to create an lvol, just the vg with the encrypted pv is enough. * Encryption settings don't seem to matter * I tried erasing the partition contents in case something in them was causing problems Hopefully that is clear and someone is able to repeat the bug, let me know if I need to explain more or if you have questions. Thanks, -- Matt Taggart tagg...@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#773280: openvpn-auth-radius: invalid `route add' command on route without gateway
Package: openvpn-auth-radius
Version: 2.1-4
Severity: wishlist
Dear Maintainer,
In our system radius return routes like '10.128.0.0/24'.
This response was prepared several VPN servers than should to register at this
route
and connected party should be the gateway.
I fix the source than if worked correctly for me.
Perhaps it is deemed right in principle.
--- UserAcct.cpp.old2014-12-16 13:20:37.699467727 +0300
+++ UserAcct.cpp2014-12-16 13:30:57.367678753 +0300
@@ -699,7 +699,11 @@
strncat(routestring, / ,1);
strncat(routestring, framednetmask_cidr, 2);
strncat(routestring, gw , 4);
- strncat(routestring, framedgw, 16);
+if (framedgw[0] != '\0')
+strncat(routestring, framedgw, 16);
+else
+strncat(routestring, this-getFramedIp().c_str(),
this-getFramedIp().size());
+
if (framedmetric[0]!='\0')
{
strncat(routestring, metric , 8);
@@ -853,7 +857,11 @@
strncat(routestring, / ,1);
strncat(routestring, framednetmask_cidr, 2);
strncat(routestring, gw , 4);
- strncat(routestring, framedgw, 16);
+if (framedgw[0] != '\0')
+strncat(routestring, framedgw, 16);
+else
+strncat(routestring, this-getFramedIp().c_str(),
this-getFramedIp().size());
+
if (framedmetric[0]!='\0')
{
strncat(routestring, metric , 8);
-- System Information:
Debian Release: 7.7
APT prefers stable-updates
APT policy: (500, 'stable-updates'), (500, 'stable')
Architecture: amd64 (x86_64)
Kernel: Linux 3.2.0-4-amd64 (SMP w/1 CPU core)
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#773237: dovecot-core: Should not use UCF for 10-ssl.conf
Quoting policy: These two styles of configuration file handling must not be mixed, for that way lies madness: `dpkg' will ask about overwriting the file every time the package is upgraded. No it won't because after -6 the file will be managed by ucf. [...] You are right that dpkg will not ask you about updating the file, because the file is not a conffile in the dpkg sense. But I was not quoting policy for the conffile mechanism itself but for the consequences of using it: The UCF mechanism works in exactly the same way as dpkg conffile mechanism, so instead of dpkg asking about this file over and over again on upgrades, we will have a *UCF* prompt asking about this file over and over again on upgrades. There is not a paragraph in policy speaking about UCF yet, but the spirit of policy is clearly violated by having 10.ssl.conf as a UCF-managed file. If you have modified 10-ssl.conf then you will get a debconf dialog on upgrades where you are given the opportunity to accept the new version, keep the old version or merge differences just as if it is a dpkg-managed conffile. If you haven't modified it, you will get the packages version just as if it is a dpkg-managed conffile. I am sorry but I fail to see your objection here. My objection is that policy says that the conffile mechanism is only appropriate for files having a default that may work for everybody, and the rationale is that if most people need to modify it, then most people will get prompted on upgrades over and over again. Since UCF and the conffile mechanism behaves in the same way when the file is not the default, it should naturally follow that the UCF mechanism is not appropriate either, unless there is a default which works for most people. The current default disables SSL, which is insecure. We can't honestly claim that an insecure default will work for most people. [...] I hope I have satisfactorily explained why this isn't a bug at all. I am closing it. Actually, you have not. Policy says prompting should be reduced to a minimum. By using UCF on a file not having a good default that will work for most people, this package is not following policy at all. As I said in the initial report, I will not discuss about this being RC or not, this is up to you, but based on current policy, this is still a bug. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#773281: apt does not resolve equal (=) dependencies correctly
Package: apt
Version: 1.0.9.4
Severity: important
Hi,
the following bug is a major burden when working with Debian repositories that
contain multiple versions of one package. Image following example:
You have two packages named A and B. A in version 1 depends on B in version 1.
Apt will automatically install B=1 when you install A=1.
Now assume you have A available in version 1 and 2 and B in version 1 and 2. If
A and B are currently not installed, apt will try to install B=2 when you want
to install A=1. This fails of cause because of the package dependencies. This is
probably a bug in apt as it sees version 2 for B as the best install candidate
even if the dependency says different.
Steps to reproduce:
===
#!/bin/sh
set -e
mkdir /tmp/alpha-1.0 cd /tmp/alpha-1.0
dh_make -c mit -s -n -p alpha_1.0 -y
sed -i 's/^Depends: /Depends: beta (= ${binary:Version})/' debian/control
debuild -b
dch -v 2.0 'Bump version'
cd ../alpha-2.0
debuild -b
mkdir /tmp/beta-1.0 cd /tmp/beta-1.0
dh_make -c mit -s -n -p beta_1.0 -y
debuild -b
dch -v 2.0 'Bump version'
cd ../beta-2.0
debuild -b
cd /tmp
apt-ftparchive packages . | gzip Packages.gz
echo deb file:///tmp/ ./ /etc/apt/sources.list
apt-get update
apt-get install alpha=1.0
===
Apt throws following error message instead of installing alpha=1.0 and beta=1.0:
Reading package lists... Done
Building dependency tree
Reading state information... Done
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:
The following packages have unmet dependencies:
alpha : Depends: beta (= 1.0) but 2.0 is to be installed
E: Unable to correct problems, you have held broken packages.
--
Benjamin Drung
System Developer
ProfitBricks GmbH - The IaaS-Company
Greifswalder Str. 207
D - 10405 Berlin
Mail: benjamin.dr...@profitbricks.com
Fax: +49 30 577 008 598
URL: http://www.profitbricks.com
Sitz der Gesellschaft: Berlin.
Registergericht: Amtsgericht Charlottenburg, HRB 125506 B.
Geschäftsführer: Andreas Gauger, Achim Weiss.
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#773205: libatomic-ops-dev: FTBFS on mips64el
Hi,
There was a small mistake in the previous patch so here's a new one.
The only change is to remove the include of
'../loadstore/acquire_release_volatile.h' because in most mips64
processors, use of volatile variables does not have acquire/release
semantics. I also don't think that this is an absolute requirement of
any mips processor (according to the ISA manuals I've found), so I've
removed it for both mips32 and mips64 just to be safe.
Thanks,
James
From 9a876e1fbc85d84ffce52a27f628484d4e7b64d2 Mon Sep 17 00:00:00 2001
From: James Cowgill james...@cowgill.org.uk
Date: Tue, 16 Dec 2014 11:42:26 +
Subject: [PATCH] Use LLD / SCD instructions on mips64
---
src/atomic_ops/sysdeps/gcc/mips.h | 56 +--
1 file changed, 30 insertions(+), 26 deletions(-)
diff --git a/src/atomic_ops/sysdeps/gcc/mips.h b/src/atomic_ops/sysdeps/gcc/mips.h
index a891de6..f3796ea 100644
--- a/src/atomic_ops/sysdeps/gcc/mips.h
+++ b/src/atomic_ops/sysdeps/gcc/mips.h
@@ -15,26 +15,33 @@
* FIXME: This should probably make finer distinctions. SGI MIPS is
* much more strongly ordered, and in fact closer to sequentially
* consistent. This is really aimed at modern embedded implementations.
- * It looks to me like this assumes a 32-bit ABI. -HB
*/
#include ../all_aligned_atomic_load_store.h
-#include ../loadstore/acquire_release_volatile.h
-
#include ../test_and_set_t_is_ao_t.h
/* Data dependence does not imply read ordering. */
#define AO_NO_DD_ORDERING
+#ifdef __mips64
+# define AO_MIPS_SET_ISA .set mips3\n
+# define AO_MIPS_LL_1(args)lld args \n
+# define AO_MIPS_SC(args) scd args \n
+#else
+# define AO_MIPS_SET_ISA .set mips2\n
+# define AO_MIPS_LL_1(args)ll args \n
+# define AO_MIPS_SC(args) sc args \n
+# define AO_T_IS_INT
+#endif
+
#ifdef AO_ICE9A1_LLSC_WAR
/* ICE9 rev A1 chip (used in very few systems) is reported to */
/* have a low-frequency bug that causes LL to fail. */
/* To workaround, just issue the second 'LL'. */
-# define AO_MIPS_LL_FIX(args_str) \
- llargs_str \n
+# define AO_MIPS_LL(args) AO_MIPS_LL_1(args) AO_MIPS_LL_1(args)
#else
-# define AO_MIPS_LL_FIX(args_str)
+# define AO_MIPS_LL(args) AO_MIPS_LL_1(args)
#endif
AO_INLINE void
@@ -42,7 +49,7 @@ AO_nop_full(void)
{
__asm__ __volatile__(
.set push \n
- .set mips2 \n
+ AO_MIPS_SET_ISA
.set noreorder \n
.set nomacro\n
sync\n
@@ -60,13 +67,13 @@ AO_fetch_and_add(volatile AO_t *addr, AO_t incr)
__asm__ __volatile__(
.set push\n
- .set mips2\n
+ AO_MIPS_SET_ISA
.set noreorder\n
.set nomacro\n
- 1: ll %0, %2\n
- AO_MIPS_LL_FIX(%0, %2)
+ 1:
+ AO_MIPS_LL(%0, %2)
addu %1, %0, %3\n
- sc %1, %2\n
+ AO_MIPS_SC(%1, %2)
beqz %1, 1b\n
nop\n
.set pop
@@ -85,13 +92,13 @@ AO_test_and_set(volatile AO_TS_t *addr)
__asm__ __volatile__(
.set push\n
- .set mips2\n
+ AO_MIPS_SET_ISA
.set noreorder\n
.set nomacro\n
- 1: ll %0, %2\n
- AO_MIPS_LL_FIX(%0, %2)
+ 1:
+ AO_MIPS_LL(%0, %2)
move %1, %3\n
- sc %1, %2\n
+ AO_MIPS_SC(%1, %2)
beqz %1, 1b\n
nop\n
.set pop
@@ -114,14 +121,14 @@ AO_test_and_set(volatile AO_TS_t *addr)
__asm__ __volatile__(
.set push \n
- .set mips2 \n
+AO_MIPS_SET_ISA
.set noreorder \n
.set nomacro\n
-1: ll %0, %1 \n
-AO_MIPS_LL_FIX(%0, %1)
+1:
+AO_MIPS_LL(%0, %1)
bne %0, %4, 2f \n
move %0, %3 \n
- sc %0, %1 \n
+AO_MIPS_SC(%0, %1)
.set pop\n
beqz%0, 1b \n
li %2, 1 \n
@@ -142,14 +149,14 @@ AO_fetch_compare_and_swap(volatile AO_t *addr, AO_t old, AO_t new_val)
__asm__ __volatile__(
.set push\n
- .set mips2\n
+ AO_MIPS_SET_ISA
.set noreorder\n
.set nomacro\n
- 1: ll %0, %2\n
- AO_MIPS_LL_FIX(%0, %2)
+ 1:
+ AO_MIPS_LL(%0, %2)
bne %0, %4, 2f\n
move %1, %3\n
- sc %1, %2\n
+ AO_MIPS_SC(%1, %2)
beqz %1, 1b\n
nop\n
.set pop\n
@@ -167,6 +174,3 @@ AO_fetch_compare_and_swap(volatile AO_t *addr, AO_t old, AO_t new_val)
/* CAS primitives with acquire, release and full semantics are */
/* generated automatically (and AO_int_... primitives are */
/* defined
Bug#773280: openvpn-auth-radius: invalid `route add' command on route without gateway
Hello! In our system radius return routes like '10.128.0.0/24'. This response was prepared several VPN servers than should to register at this route and connected party should be the gateway. I fix the source than if worked correctly for me. Perhaps it is deemed right in principle. Can you please be more verbosive? Which Radius Attribute are you referring to? Do you have a example config of your Radius Server, where you set the attribute. Can you please provide the resulting route string with and without your patch including logfiles? Greetings Torge signature.asc Description: Message signed with OpenPGP using GPGMail
Bug#773282: mariadb-server-10.0: init script returns failure on success
Package: mariadb-server-10.0 Version: 10.0.15-2 Severity: normal Upgrading from 10.0.15-1 to -2: Setting up mariadb-server-10.0 (10.0.15-2) ... [ ok ] Stopping MariaDB database server: mysqld. [ ok ] Starting MariaDB database server: mysqld. invoke-rc.d: initscript mysql, action start failed. dpkg: error processing package mariadb-server-10.0 (--configure): subprocess installed post-installation script returned error exit status 1 Hmm. # service mysql restart; echo $? [ ok ] Stopping MariaDB database server: mysqld. [ ok ] Starting MariaDB database server: mysqld. 1 The problem lies with line 122: /etc/mysql/debian-start no longer outputs anything (at least for me), so the expression evaluates to 1, hence the statement (because of ), hence the script (because this is the last statement). Shell scripting is such a pain... Using if (which returns 0) or appending || true does the trick. -- System Information: Debian Release: 8.0 APT prefers unstable APT policy: (500, 'unstable') Architecture: i386 (x86_64) Foreign Architectures: amd64 Kernel: Linux 3.16.0-4-amd64 (SMP w/3 CPU cores) Locale: LANG=en_CA.UTF-8, LC_CTYPE=en_CA.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: sysvinit (via /sbin/init) Versions of packages mariadb-server-10.0 depends on: ii adduser 3.113+nmu3 ii debconf [debconf-2.0] 1.5.55 ii libaio1 0.3.110-1 ii libc6 2.19-13 ii libdbi-perl 1.631-3+b1 ii libpam0g 1.1.8-3.1 ii libstdc++64.9.2-8 ii lsb-base 4.1+Debian13+nmu1 ii mariadb-client-10.0 10.0.15-2 ii mariadb-common10.0.15-2 ii mariadb-server-core-10.0 10.0.15-2 ii passwd1:4.2-3 ii perl 5.20.1-3 ii psmisc22.21-2 ii zlib1g1:1.2.8.dfsg-2+b1 Versions of packages mariadb-server-10.0 recommends: ii libhtml-template-perl 2.95-1 Versions of packages mariadb-server-10.0 suggests: ii bsd-mailx [mailx] 8.1.2-0.20140825cvs-1 pn mariadb-test none pn tinyca none -- Configuration Files: /etc/init.d/mysql changed [not included] -- debconf information: mariadb-server-10.0/really_downgrade: false mysql-server-10.0/postrm_remove_databases: false * mysql-server/password_mismatch: mysql-server/error_setting_password: mysql-server/no_upgrade_when_using_ndb: mysql-server-10.0/nis_warning: * mariadb-server/oneway_migration: true -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#708764: python3-usb also built
The pyusb source package now also builds python3-usb and therefore also closes #749908: http://mentors.debian.net/package/pyusb In total it closes 3 bug reports if it's uploaded: #708764, #749908 and #712206. Regards, Ruben -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#773189: [Pkg-libvirt-maintainers] Bug#773189: libvirt-daemon: Haswell microcode update breaks CPU detection
On Mon, Dec 15, 2014 at 06:56:19PM +0100, intrigeri wrote: hi, Chris Boot wrote (15 Dec 2014 12:39:52 GMT) : The intel-microcode 3.20140913.1 update disables TSX-NI (transactional memory instructions). When a server running libvirt is rebooted with this update, libvirt no longer considers the machine to have a Haswell CPU: dietrich ~ # virsh capabilities | grep -A1 'archx86_64' archx86_64/arch modelSandyBridge/model This causes a problem as any VMs that require a Haswell CPU, which would have worked previously, now fail to start altogether. Commenting out the two cpuinfo flags relevant to TSX-NI from /usr/share/libvirt/cpu_map.xml fixes this for me: FWIW, I've been suffering from the symptoms of that issue for a few weeks. I guessed it was caused by that microcode update, but had no time to report it. *If* that's a regression since Wheezy, I think it would qualify as RC, since VMs that started just fine previously now fail to come up at boot. The workaround (in the package) is tiny, and makes sense to me: if Intel themselves now consider that Haswell CPUs have no TSX-NI, then libvirt's view of what's a Haswell CPU should be updated. OTOH, the user-side workaround (copy host CPU model) is easy enough too, although a bit painful to discover initially for many users I guess. Shall we ask the release team if they would happily unblock this change for Jessie? I think we should. I've submitted it upstream to get some feadback and make this a safe change and thanks to both of you! Cheers, -- Guido -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#773065: selecting target via dpkg-buildpackage --target-arch
Control: tags -1 + moreinfo On 12/13/2014 10:55 PM, Helmut Grohne wrote: Package: src:gcc-4.9 Version: 4.9.2-7 Tags: patch User: helm...@debian.org Usertags: rebootstrap X-Debbugs-Cc: debian-cr...@lists.debian.orgj Please allow selecting the target architecture using dpkg-buildpackage --target-arch again. This ability was removed in 4.9.2-7 when #768167 was fixed. I am attaching a diff that enables target selection via: * dpkg-buildpackage --target-arch * debian/target * DEB_GCC_TARGET please verify your patch using an old dpkg from wheezy, using native builds and the supported cross builds and attach the four compressed build logs. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#773283: fetch-crl error: Invalid meta-data directory /etc/grid-security/certificates
Package: fetch-crl
Version: 3.0.15-1
Severity: normal
After installing fetch-crl, I got the following error from cron:
Subject: Cron root@ypig [ ! -f /var/lock/fetch-crl-cron ] || ( [ -f
/etc/default/fetch-crl ] . /etc/default/fetch-crl ;
/usr/sbin/fetch-crl -q -r 360 )
X-Cron-Env: SHELL=/bin/sh
X-Cron-Env: HOME=/root
X-Cron-Env: PATH=/usr/bin:/bin
X-Cron-Env: LOGNAME=root
Invalid meta-data directory /etc/grid-security/certificates
The directory /etc/grid-security doesn't exist.
The error comes from:
# sanity check on configuration
$cnf-{_}-{statedir} and ! -d $cnf-{_}-{statedir} and
die Invalid state directory . $cnf-{_}-{statedir} . \n;
$cnf-{_}-{infodir} and ! -d $cnf-{_}-{infodir} and
die Invalid meta-data directory .$cnf-{_}-{infodir}.\n;
I suppose that the directory should automatically be created if
it doesn't exist.
-- System Information:
Debian Release: 8.0
APT prefers unstable
APT policy: (500, 'unstable'), (500, 'testing'), (500, 'stable'), (1,
'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 3.16.0-4-amd64 (SMP w/8 CPU cores)
Locale: LANG=POSIX, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: sysvinit (via /sbin/init)
Versions of packages fetch-crl depends on:
ii libwww-perl 6.08-1
ii openssl 1.0.1j-1
ii perl 5.20.1-3
fetch-crl recommends no packages.
fetch-crl 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#728529: smartmontools throws errors even after the binNMU
Control: found -1 2.24.90.20141128-1 Control: notfound -1 2.24.90.20141209-1 well, the rebuild was done using binutils_2.24.90.20141128-1 (at least on amd64). so it doesn't say anything. Please file a proper binNMU, or reopen the old one. On 12/15/2014 12:59 AM, Kamaraju Kusumanchi wrote: found 728529 2.24.90.20141209-1 thanks I still see this problem in smartmontools even after recompiling it against the latest binutils package. You can see the binNMU request in https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=772798 . root@hogwarts:~# smartctl -i /dev/sda Inconsistency detected by ld.so: dl-version.c: 224: _dl_check_map_versions: Assertion `needed != ((void *)0)' failed! root@hogwarts:~# dpkg -l binutils smartmontools libselinux1 | grep ^ii ii binutils 2.24.90.20141209-1 amd64GNU assembler, linker and binary utilities ii libselinux1:amd64 2.3-2 amd64SELinux runtime shared libraries ii libselinux1:i386 2.3-2 i386 SELinux runtime shared libraries ii smartmontools 6.3+svn4002-2+b1 amd64control and monitor storage systems using S.M.A.R.T. regards -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#772798: binNMU with outdated binutils
Control: reopen -1 according to the amd64 build log, the binNMU was done using 2.24.90.20141128-1 please do another binNMU using the requested version. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#773169: unblock: syncevolution/1.4.99.4-3
Hi, I forgot to attach a debdiff in the bugreport. Sorry for that. Now it's attached. Regards, Tino diff -Nru syncevolution-1.4.99.4/debian/changelog syncevolution-1.4.99.4/debian/changelog --- syncevolution-1.4.99.4/debian/changelog 2014-10-26 14:43:18.0 +0100 +++ syncevolution-1.4.99.4/debian/changelog 2014-12-04 22:46:12.0 +0100 @@ -1,3 +1,9 @@ +syncevolution (1.4.99.4-3) unstable; urgency=medium + + * Use TLS instead of SSLv3 in SyncML server script (Closes: #772040) + + -- Tino Mettler tino+deb...@tikei.de Thu, 04 Dec 2014 22:44:49 +0100 + syncevolution (1.4.99.4-2) unstable; urgency=medium * Fix FTBFS on kfreebsd due to missing SOCK_CLOEXEC diff -Nru syncevolution-1.4.99.4/debian/patches/0001-Fix-FTBFS-on-kfreebsd-due-to-missing-SOCK_CLOEXEC.patch syncevolution-1.4.99.4/debian/patches/0001-Fix-FTBFS-on-kfreebsd-due-to-missing-SOCK_CLOEXEC.patch --- syncevolution-1.4.99.4/debian/patches/0001-Fix-FTBFS-on-kfreebsd-due-to-missing-SOCK_CLOEXEC.patch 2014-10-26 14:13:38.0 +0100 +++ syncevolution-1.4.99.4/debian/patches/0001-Fix-FTBFS-on-kfreebsd-due-to-missing-SOCK_CLOEXEC.patch 2014-12-04 22:46:46.0 +0100 @@ -47,5 +47,5 @@ GuardFD childfd(fds[1]); -- -2.0.1 +2.1.3 diff -Nru syncevolution-1.4.99.4/debian/patches/0002-Use-TLS-instead-of-SSLv3-in-SyncML-server-script.patch syncevolution-1.4.99.4/debian/patches/0002-Use-TLS-instead-of-SSLv3-in-SyncML-server-script.patch --- syncevolution-1.4.99.4/debian/patches/0002-Use-TLS-instead-of-SSLv3-in-SyncML-server-script.patch 1970-01-01 01:00:00.0 +0100 +++ syncevolution-1.4.99.4/debian/patches/0002-Use-TLS-instead-of-SSLv3-in-SyncML-server-script.patch 2014-12-04 22:46:46.0 +0100 @@ -0,0 +1,30 @@ +From 7d2802314406b0d6218bd04889667e38710b414d Mon Sep 17 00:00:00 2001 +From: Tino Mettler tino+deb...@tikei.de +Date: Thu, 4 Dec 2014 17:11:22 +0100 +Subject: [PATCH] Use TLS instead of SSLv3 in SyncML server script + +This fixes a potential security risk. It also avoids connection problems +with clients that don't support SSLv3 anymore, like the syncevolution SyncML +client itself. + +Closes: #772040 +--- + test/syncevo-http-server.py | 2 +- + 1 file changed, 1 insertion(+), 1 deletion(-) + +diff --git a/test/syncevo-http-server.py b/test/syncevo-http-server.py +index 57210ae..6c14088 100755 +--- a/test/syncevo-http-server.py b/test/syncevo-http-server.py +@@ -40,7 +40,7 @@ timeout=10 + + class ChainedOpenSSLContextFactory(ssl.DefaultOpenSSLContextFactory): + def __init__(self, privateKeyFileName, certificateChainFileName, +- sslmethod = SSL.SSLv3_METHOD): ++ sslmethod = SSL.TLSv1_METHOD): + + @param privateKeyFileName: Name of a file containing a private key + @param certificateChainFileName: Name of a file containing a certificate chain +-- +2.1.3 + diff -Nru syncevolution-1.4.99.4/debian/patches/series syncevolution-1.4.99.4/debian/patches/series --- syncevolution-1.4.99.4/debian/patches/series 2014-10-26 14:13:38.0 +0100 +++ syncevolution-1.4.99.4/debian/patches/series 2014-12-04 22:46:46.0 +0100 @@ -1,2 +1,3 @@ # debian/source/git-patches exported from git by quilt-patches-deb-export-hook 0001-Fix-FTBFS-on-kfreebsd-due-to-missing-SOCK_CLOEXEC.patch +0002-Use-TLS-instead-of-SSLv3-in-SyncML-server-script.patch
Bug#772826: watchdog fails to upgrade
On Dec 16, Michael Meskes wrote:
What happens if you stop watchdog, does the process go away? Or if you happen
to reboot, does that change things? I'm wondering if the old process stays in
the way and thus may need to be killed manually. I have it that before, that
processes do not disappear despite being stopped via systemctl.
No, the process is stopped properly. systemctl start and stop
work as expected, only systemctl restart fails.
Stop / start:
# systemctl status watchdog
● watchdog.service - watchdog daemon
Loaded: loaded (/lib/systemd/system/watchdog.service; enabled)
Active: active (running) since Thu 2014-12-11 14:44:09 CET; 4 days ago
Main PID: 30954 (watchdog)
CGroup: /system.slice/watchdog.service
└─30954 /usr/sbin/watchdog
Dec 11 14:44:09 grappa watchdog[30954]: starting daemon (5.14):
Dec 11 14:44:09 grappa watchdog[30954]: int=1s realtime=yes sync=no soft=no
mla=0 mem=0
Dec 11 14:44:09 grappa watchdog[30954]: ping: no machine to check
Dec 11 14:44:09 grappa watchdog[30954]: file: no file to check
Dec 11 14:44:09 grappa watchdog[30954]: pidfile: no server process to check
Dec 11 14:44:09 grappa watchdog[30954]: interface: no interface to check
Dec 11 14:44:09 grappa watchdog[30954]: temperature: no sensors to check
Dec 11 14:44:09 grappa watchdog[30954]: test=none(0) repair=none(0)
alive=/dev/watchdog heartbeat=none to=root no_act=no force=no
Dec 11 14:44:09 grappa watchdog[30954]: cannot set timeout 60 (errno = 22 =
'Invalid argument')
Dec 11 14:44:09 grappa watchdog[30954]: hardware watchdog identity: INTCAMT
# ps ax|grep watchdog
10 ?S 0:01 [watchdog/0]
11 ?S 0:02 [watchdog/1]
28719 pts/4S+ 0:00 grep watchdog
30954 ?SLs0:17 /usr/sbin/watchdog
# systemctl stop watchdog
# systemctl status watchdog
● watchdog.service - watchdog daemon
Loaded: loaded (/lib/systemd/system/watchdog.service; enabled)
Active: inactive (dead) since Tue 2014-12-16 13:32:38 CET; 7s ago
Process: 28726 ExecStopPost=/bin/sh -c [ $run_wd_keepalive != 1 ] || false
(code=exited, status=1/FAILURE)
Main PID: 30954 (code=exited, status=0/SUCCESS)
Dec 11 14:44:09 grappa watchdog[30954]: file: no file to check
Dec 11 14:44:09 grappa watchdog[30954]: pidfile: no server process to check
Dec 11 14:44:09 grappa watchdog[30954]: interface: no interface to check
Dec 11 14:44:09 grappa watchdog[30954]: temperature: no sensors to check
Dec 11 14:44:09 grappa watchdog[30954]: test=none(0) repair=none(0)
alive=/dev/watchdog heartbeat=none to=root no_act=no force=no
Dec 11 14:44:09 grappa watchdog[30954]: cannot set timeout 60 (errno = 22 =
'Invalid argument')
Dec 11 14:44:09 grappa watchdog[30954]: hardware watchdog identity: INTCAMT
Dec 16 13:32:33 grappa watchdog[30954]: stopping daemon (5.14)
Dec 16 13:32:38 grappa systemd[1]: watchdog.service: control process exited,
code=exited status=1
Dec 16 13:32:38 grappa systemd[1]: Unit watchdog.service entered failed state.
# ps ax|grep watchdog
10 ?S 0:01 [watchdog/0]
11 ?S 0:02 [watchdog/1]
28746 pts/4S+ 0:00 grep watchdog
# systemctl start watchdog
# systemctl status watchdog
● watchdog.service - watchdog daemon
Loaded: loaded (/lib/systemd/system/watchdog.service; enabled)
Active: active (running) since Tue 2014-12-16 13:32:59 CET; 20s ago
Process: 28726 ExecStopPost=/bin/sh -c [ $run_wd_keepalive != 1 ] || false
(code=exited, status=1/FAILURE)
Process: 28756 ExecStart=/bin/sh -c [ $run_watchdog != 1 ] || exec
/usr/sbin/watchdog $watchdog_options (code=exited, status=0/SUCCESS)
Process: 28753 ExecStartPre=/bin/sh -c [ -z ${watchdog_module} ] || [
${watchdog_module} = none ] || /sbin/modprobe $watchdog_module
(code=exited, status=0/SUCCESS)
Main PID: 28758 (watchdog)
CGroup: /system.slice/watchdog.service
└─28758 /usr/sbin/watchdog
Dec 16 13:32:59 grappa watchdog[28758]: starting daemon (5.14):
Dec 16 13:32:59 grappa watchdog[28758]: int=1s realtime=yes sync=no soft=no
mla=0 mem=0
Dec 16 13:32:59 grappa watchdog[28758]: ping: no machine to check
Dec 16 13:32:59 grappa watchdog[28758]: file: no file to check
Dec 16 13:32:59 grappa watchdog[28758]: pidfile: no server process to check
Dec 16 13:32:59 grappa watchdog[28758]: interface: no interface to check
Dec 16 13:32:59 grappa watchdog[28758]: temperature: no sensors to check
Dec 16 13:32:59 grappa watchdog[28758]: test=none(0) repair=none(0)
alive=/dev/watchdog heartbeat=none to=root no_act=no force=no
Dec 16 13:32:59 grappa watchdog[28758]: cannot set timeout 60 (errno = 22 =
'Invalid argument')
Dec 16 13:32:59 grappa watchdog[28758]: hardware watchdog identity: INTCAMT
# ps ax|grep watchdog
10 ?S 0:01 [watchdog/0]
11 ?S 0:02 [watchdog/1]
28758 ?SLs0:00 /usr/sbin/watchdog
28762 pts/4
Bug#773252: systemd-timesyncd syncs time about once per minute
Am 16.12.2014 um 04:45 schrieb Jos van Wolput: Package: systemd Version: 215-8 and 218-1 Severity: normal Dear Maintainer, Systemd-timesyncd syncs time about once per 60 seconds. What makes you think systemd-timesync syncs the clock once every 60 seconds? -- 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#773284: Please configure server to run as non-root by default
Package: bcfg2-server Version: 1.3.5-1 Severity: normal Subject says it all, here are the docs: http://docs.bcfg2.org/server/configuration.html#running-as-a-non-root-user -- System Information: Debian Release: 8.0 APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 3.17-1-amd64 (SMP w/8 CPU cores) Locale: LANG=en_NZ, LC_CTYPE=en_NZ.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: sysvinit (via /sbin/init) -- .''`. martin f. krafft madduck@d.o @martinkrafft : :' : proud Debian developer `. `'` http://people.debian.org/~madduck `- Debian - when you have better things to do than fixing systems digital_signature_gpg.asc Description: Digital signature (see http://martin-krafft.net/gpg/sig-policy/999bbcc4/current)
Bug#772665: produces broken cross compiler packages for mips64el
Waoo, great work.
Now I understand what it is for.
Looong Looong ago, something may make libn32blabla depend on
lib64blabla in control,
so this snap of code exits.
Now we don't have this problem, all libn32blabla depends on
Depends: gcc-4.9-base (= ${gcc:Version}), ${dep:libcbiarch},
${shlibs:Depends}, ${misc:Depends}
No lib64blabla in them, so we should remove these codes.
On Tue, Dec 16, 2014 at 3:34 PM, Helmut Grohne hel...@subdivi.de wrote:
On Wed, Dec 10, 2014 at 09:54:01AM +0100, Matthias Klose wrote:
I can't remember. please ask the Debian mips maintainers. I assume, extending
the expression to entirely remove empty fields should work around this for
now.
I did X-Debbugs-Cc the submission to debian-mips@l.d.o. So now I did
some archeology:
* The affected code was inserted in the gcc-4.4 era.
* It is inserted in SVN revision 4707.
* The commit message closes #594540.
Unfortunately the bug report is rather scarce on details, but it appears
to be talking about library packages. So I went ahead and restricted the
match to lib$biarch. The immediate effect is that it no longer matches
mips64el and thus leaves the Recommends on libc alone. Thus the stage1
becomes installable. I did not notice any excess dependencies.
I could not verify further stages as the stage2 build fails linking the
n32 libc.so, because it insists on linking the 64 one. The latter may be
an error in my build environment.
Nevertheless, I am attaching a patch for what I believe to be the
correct solution.
Helmut
--
YunQiang Su
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#773274: installation-reports: parted_server segfault
Matt Taggart tagg...@debian.org (2014-12-16): Package: installation-reports Version: 20141216-00:08 When attempting an install using a daily image, I ran into a case where parted_server segfaults with the following: parted_server[29651]: segfault at 8 ip 0040b4b1 sp 7fff5d7c54c0 error 4 in parted_server[40+12000] I tried it several times and attempted to distill it down to the simplest case I could. To repeat: 1) create a partition and mark it for encryption 2) configure encryption, set it up (don't erase to save time, but that doesn't matter), finish encryption 3) mark newly created encrypted volume as for LVM 4) configure LVM, create a volume group and a logical volume, finish The menu will freeze at Detecting filesystems and the above error is in syslog. Setting up LVM on a non-encrypted disk works just fine, I didn't see the problem unless it was encrypted. Please specify the image you used, and please attach your syslog. (https://www.debian.org/releases/stable/amd64/ch05s04.html.en#problem-report etc.) KiBi. signature.asc Description: Digital signature
Bug#757388: debian-handbook: various comments on the French, wheezy edition
Hello Cyril, thanks for your feedback. On Thu, 07 Aug 2014, Cyril Brulebois wrote: - I think it'd be fair to remove Joey as d-i coordinator, myself as X coordinator, and probably mention Steve by name as debian-cd guy. Will do for the Jessie update. - “mandataire à antémémoire” is really awful. As a former l10n guy I understand you're trying to stick to toubonnais-approved terms but I felt hit by a truck with that one. Amusingly enough “serveurs proxy/cache” appear a few pages later. ;) Will consider it. :) - I mentioned on IRC I wasn't sure about /dev/hd* vs. /dev/sd* but squeeze release notes indeed mention “5.1.1. Migration of disk drivers from IDE to PATA subsystem” so I'm now convinced it happened that long ago. ;) I'm not sure what you're suggesting here... possibly that we might want to stop documenting the fact that /dev/hdX used to be for IDE disks ? - There's linux-headers-* and linux-image-* but no linux-images-*. Fixed in wheezy/master, thanks. - Spotted another typo: “plus personne de maintient SWAT” (de→ne). That was already fixed in git. - There's a section about rsync where dirvish suddenly pops up. Maybe I missed something but I guess you wanted to have a dirvish section starting with an rsync description instead? Not really, we start by explaining how rsync can help do backups and then we introduce a tool that helps you achieve the scheme we just described. I don't see anything wrong in the progression of the explanation. - chromium is no longer exactly the new kid on the block. - virtualbox is no longer in main (after wheezy). Both noted for the jessie update. - I think the Firefox issue is misrepresented: isn't that about trademark and not about non-free licensing? It's a combination of both IIRC. The official logo is non-free, thus we want to replace the logo. However if you replace the logo you no longer have the right to call it Firefox (due to trademarks). (There are also other problems with the trademark such as the obligation to get our changes vetted by Mozilla) - in the debsums part, apt-get --reinstall -d install can be replaced with apt-get download, which is a bit more straightforward than the option dance (I guess it was borrowed from aptitude). debsums will go away in the jessie update, now we have dpkg --verify instead. I only skimmed through the book (didn't reach the end yet) but I really like the style/approach you used. Thanks, that seems to be a very nice reference book (heh, that's its purpose!), even for longtime Debian members. :) Thanks for your feedback and your kind words! Cheers, -- Raphaël Hertzog ◈ Debian Developer Support Debian LTS: http://www.freexian.com/services/debian-lts.html Learn to master Debian: http://debian-handbook.info/get/ -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#773155: gimp: toolbar appears with garbage all the time
Could you attach a screenshot? Also, what X video driver are you using?
Bug#773285: unattended-upgrades unblock request
Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: unblock Hi release team, I would like to ask for allow unattended-upgrades 0.83.3 into testing. Version 0.83 has a regression when it sends out the summary mail of the completed upgrade. The full changelog: unattended-upgrades (0.83.3) unstable; urgency=medium [ Alexandre Detiste ] * add Raspbian template [ Michael Vogt ] * Attach all dpkg log to the summary mail on minimal-upgrades-steps mode (closes: #759693) -- Michael Vogt m...@debian.org Wed, 10 Dec 2014 21:36:34 +0100 unattended-upgrades (0.83.2) unstable; urgency=medium [ Martin-Éric Racine ] * debian/changelog: - updated to the DEP-5 format [ Alexandre Detiste ] * Fix spurious newlines -- Michael Vogt m...@debian.org Wed, 26 Nov 2014 10:19:48 +0100 unattended-upgrades (0.83.1) unstable; urgency=medium * unattended-upgrade: - fix regression and only send out the most recent dpkg log part when sending the summary mail (closes: #759693) * README.md: - improve documentation * debian/control: - update Vcs-Bzr location -- Michael Vogt m...@debian.org Mon, 24 Nov 2014 11:09:41 +0100 Thanks for your consideration, Michael signature.asc Description: Digital signature
Bug#773252: systemd-timesyncd syncs time about once per minute
Am 16.12.2014 um 14:07 schrieb Michael Biebl: Am 16.12.2014 um 04:45 schrieb Jos van Wolput: Package: systemd Version: 215-8 and 218-1 Severity: normal Dear Maintainer, Systemd-timesyncd syncs time about once per 60 seconds. What makes you think systemd-timesync syncs the clock once every 60 seconds? I just studied the code and timesyncd starts with a minimal 32 second interval (NTP_POLL_INTERVAL_MIN_SEC) which is increased until it reaches the maximum 2048 second polling interval (NTP_POLL_INTERVAL_MAX_SEC). It seems to use an exponential like back-off algorithm as shown by the journal Dez 16 14:07:41 pluto systemd-timesyncd[12409]: interval/delta/delay/jitter/drift 32s/+0.253s/0.028s/0.000s/+500ppm Dez 16 14:08:13 pluto systemd-timesyncd[12409]: interval/delta/delay/jitter/drift 64s/-0.005s/0.025s/0.002s/+460ppm Dez 16 14:09:17 pluto systemd-timesyncd[12409]: interval/delta/delay/jitter/drift 128s/-0.022s/0.040s/0.008s/+373ppm Dez 16 14:11:25 pluto systemd-timesyncd[12409]: interval/delta/delay/jitter/drift 128s/-0.053s/0.024s/0.050s/+165ppm Dez 16 14:13:33 pluto systemd-timesyncd[12409]: interval/delta/delay/jitter/drift 256s/+0.030s/0.124s/0.055s/+165ppm (ignored) Dez 16 14:17:50 pluto systemd-timesyncd[12409]: interval/delta/delay/jitter/drift 256s/-0.056s/0.026s/0.052s/+55ppm Dez 16 14:22:06 pluto systemd-timesyncd[12409]: interval/delta/delay/jitter/drift 512s/-0.012s/0.025s/0.050s/+43ppm Dez 16 14:30:38 pluto systemd-timesyncd[12409]: interval/delta/delay/jitter/drift 1024s/+0.046s/0.149s/0.059s/+43ppm (ignored) roughly 30s - 1m, 1m - 2m, 2m - 4m, 4m - 8m ... This looks like a sensible approach to me. -- 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#773286: qemu-kvm: attemt to attach block device fails Bus 'pci.0' does not support hotplugging
Package: qemu-kvm Version: 1.1.2+dfsg-6+deb7u6 Severity: normal Dear Maintainer, * What led up to the situation? Tried to add a new disk to a running kvm guest * What exactly did you do (or not do) that was effective (or ineffective)? Using the virsh attach-device command I tried to add a new disk * What was the outcome of this action? # virsh attach-device cedric.CalvaEDI.COM zz.xml error: Failed to attach device from zz.xml error: internal error unable to execute QEMU command 'device_add': Bus 'pci.0' does not support hotplugging * What outcome did you expect instead? Happiness. The running vm looks like: /usr/bin/kvm -S -M pc-1.1 -enable-kvm -m 8192 -smp 1,sockets=1,cores=1,threads=1 -name cedric.CalvaEDI.COM -uuid 99cfca83-cf28-ce9b-86a4-947debc202b5 -nographic -no-user-config -nodefaults -chardev socket,id=charmonitor,path=/var/lib/libvirt/qemu/cedric.CalvaEDI.COM.monitor,server,nowait -mon chardev=charmonitor,id=monitor,mode=control -rtc base=utc -no-shutdown -no-acpi -device piix3-usb-uhci,id=usb,bus=pci.0,addr=0x1.0x2 -drive file=/dev/disk/by-id/md-name-cedric:root,if=none,id=drive-virtio-disk0,format=raw,cache=none -device virtio-blk-pci,scsi=off,bus=pci.0,addr=0x4,drive=drive-virtio-disk0,id=virtio-disk0,bootindex=1 -drive file=/dev/disk/by-id/md-name-belgic:archive,if=none,id=drive-virtio-disk1,format=raw -device virtio-blk-pci,scsi=off,bus=pci.0,addr=0x5,drive=drive-virtio-disk1,id=virtio-disk1 -drive file=/dev/disk/by-id/md-name-belgic:backups,if=none,id=drive-virtio-disk2,format=raw -device virtio-blk-pci,scsi=off,bus=pci.0,addr=0x6,drive=drive-virtio-disk2,id=vir! tio-disk2 -netdev tap,fd=20,id=hostnet0,vhost=on,vhostfd=21 -device virtio-net-pci,netdev=hostnet0,id=net0,mac=00:16:3e:65:2d:8e,bus=pci.0,addr=0x3 -chardev pty,id=charserial0 -device isa-serial,chardev=charserial0,id=serial0 -device virtio-balloon-pci,id=balloon0,bus=pci.0,addr=0x7 Or, in libvirt xml format: domain type='kvm' id='3' namecedric.CalvaEDI.COM/name uuid99cfca83-cf28-ce9b-86a4-947debc202b5/uuid memory unit='KiB'8388608/memory currentMemory unit='KiB'4194304/currentMemory vcpu placement='static'1/vcpu os type arch='x86_64' machine='pc-1.1'hvm/type boot dev='hd'/ /os clock offset='utc' adjustment='reset'/ on_poweroffdestroy/on_poweroff on_rebootrestart/on_reboot on_crashrestart/on_crash devices emulator/usr/bin/kvm/emulator disk type='block' device='disk' driver name='qemu' type='raw' cache='none'/ source dev='/dev/disk/by-id/md-name-cedric:root'/ target dev='vda' bus='virtio'/ alias name='virtio-disk0'/ address type='pci' domain='0x' bus='0x00' slot='0x04' function='0x0'/ /disk disk type='block' device='disk' driver name='qemu' type='raw'/ source dev='/dev/disk/by-id/md-name-belgic:archive'/ target dev='vdb' bus='virtio'/ alias name='virtio-disk1'/ address type='pci' domain='0x' bus='0x00' slot='0x05' function='0x0'/ /disk disk type='block' device='disk' driver name='qemu' type='raw'/ source dev='/dev/disk/by-id/md-name-belgic:backups'/ target dev='vdc' bus='virtio'/ alias name='virtio-disk2'/ address type='pci' domain='0x' bus='0x00' slot='0x06' function='0x0'/ /disk controller type='usb' index='0' alias name='usb0'/ address type='pci' domain='0x' bus='0x00' slot='0x01' function='0x2'/ /controller interface type='bridge' mac address='00:16:3e:65:2d:8e'/ source bridge='calvaedi'/ target dev='vnet0'/ model type='virtio'/ alias name='net0'/ address type='pci' domain='0x' bus='0x00' slot='0x03' function='0x0'/ /interface serial type='pty' source path='/dev/pts/0'/ target port='0'/ alias name='serial0'/ /serial console type='pty' tty='/dev/pts/0' source path='/dev/pts/0'/ target type='serial' port='0'/ alias name='serial0'/ /console memballoon model='virtio' alias name='balloon0'/ address type='pci' domain='0x' bus='0x00' slot='0x07' function='0x0'/ /memballoon /devices seclabel type='none'/ /domain The device I tried to add looks like: disk type='block' device='disk' driver name='qemu' type='raw' cache='none'/ source dev='/dev/disk/by-id/md-name-cedric:new'/ target dev='vdd' bus='virtio'/ /disk The error in libvirtd.log is: 2014-12-16 13:22:50.831+: 5305: error : qemuMonitorJSONCheckError:342 : internal error unable to execute QEMU command 'device_add': Bus 'pci.0' does not support hotplugging 2014-12-16 13:22:50.832+: 5305: warning : qemuDomainAttachPciDiskDevice:255 : qemuMonitorAddDevice failed on file=/dev/disk/by-id/md-name-cedric:new,if=none,id=drive-virtio-disk3,format=raw,cache=none (virtio-blk-pci,scsi=off,bus=pci.0,addr=0xb,drive=drive-virtio-disk3,id=virtio-disk3) From strace it seems that the commands
Bug#772826: watchdog fails to upgrade
Hi Michael, here are my results from purging and reinstalling watchdog. There are some messages during the installation: /run/udev or .udevdb or .udev presence implies active udev. Aborting MAKEDEV invocation. update-rc.d: warning: start and stop actions are no longer supported; falling back to defaults Not sure if that means anything, but to me it sounds like an obsolete mechanism is used somewhere. I don't know what the intended behavior for /etc/default/watchdog is now. The changelog states: Changed rules file to make sure default file doesn't come back. But the package installation still references /etc/default/watchdog: Configuring watchdog Please specify whether stopping watchdog should start wd_keepalive to keep on triggering the watchdog device. This can be changed later by editing /etc/default/watchdog. Start wd_keepalive after stopping watchdog? And the file is recreated on package installation. At least the package database is cleaned up as expected by purging and reinstalling watchdog. I also have found out what causes systemctl restart watchdog to fail. When I disable run_wd_keepalive in /etc/default/watchdog anything works as expected (at least as far as I can see). But when I enable run_wd_keepalive the restart fails as reported before. Is restarting watchdog with wd_keepalive as a temporary replacement not supported? Regards Uwe PS: Sorry for not testing the reboot now, it's my desktop system and I have too many windows open at the moment. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#773252: systemd-timesyncd syncs time about once per minute
On 12/16/2014 09:07 PM, Michael Biebl wrote: What makes you think systemd-timesync syncs the clock once every 60 seconds? Even every 32 seconds! The systemd journal and the output of systemctl status systemd-timesyncd.service: systemd-timesyncd.service - Network Time Synchronization Loaded: loaded (/lib/systemd/system/systemd-timesyncd.service; disabled) Active: active (running) since Tue, 16 Dec 2014 21:21:56 +0800; 8min ago Docs: man:systemd-timesyncd.service(8) Main PID: 24099 (systemd-timesyn) Status: Using Time Server 202.112.10.36:123 (0.debian.pool.ntp.org). Dec 16 21:24:42 debian systemd-timesyncd[24099]: interval/delta/delay/jitter/drift 64s/+0.030s/0.192s/0.043s/+500ppm Dec 16 21:25:47 debian systemd-timesyncd[24099]: interval/delta/delay/jitter/drift 32s/+0.194s/0.095s/0.154s/+500ppm Dec 16 21:26:19 debian systemd-timesyncd[24099]: interval/delta/delay/jitter/drift 32s/+0.084s/0.111s/0.142s/+500ppm Dec 16 21:26:51 debian systemd-timesyncd[24099]: interval/delta/delay/jitter/drift 32s/+0.060s/0.098s/0.132s/+500ppm Dec 16 21:27:23 debian systemd-timesyncd[24099]: interval/delta/delay/jitter/drift 32s/+0.066s/0.101s/0.134s/+500ppm Dec 16 21:27:56 debian systemd-timesyncd[24099]: interval/delta/delay/jitter/drift 32s/+0.063s/0.095s/0.133s/+500ppm Dec 16 21:28:28 debian systemd-timesyncd[24099]: interval/delta/delay/jitter/drift 32s/+0.058s/0.081s/0.053s/+500ppm Dec 16 21:29:00 debian systemd-timesyncd[24099]: interval/delta/delay/jitter/drift 32s/+0.075s/0.100s/0.054s/+500ppm Dec 16 21:29:32 debian systemd-timesyncd[24099]: interval/delta/delay/jitter/drift 32s/+0.087s/0.133s/0.054s/+500ppm Dec 16 21:30:05 debian systemd-timesyncd[24099]: interval/delta/delay/jitter/drift 32s/+0.126s/0.088s/0.030s/+500ppm -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#773287: openrc: Please enable SELinux support
Source: openrc Version: 0.13.1-4 Severity: wishlist Tags: patch User: selinux-de...@lists.alioth.debian.org Usertags: selinux selinux-aware Hello, Could it be possible to enable openrc selinux support? The attached patch should achieve this. Cheers, Laurent Bigonville -- System Information: Debian Release: 8.0 APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.16.0-4-amd64 (SMP w/8 CPU cores) Locale: LANG=fr_BE.utf8, LC_CTYPE=fr_BE.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) diff -Nru openrc-0.13.1/debian/control openrc-0.13.1/debian/control --- openrc-0.13.1/debian/control 2014-10-26 17:34:13.0 +0100 +++ openrc-0.13.1/debian/control 2014-12-16 14:39:56.0 +0100 @@ -5,7 +5,7 @@ Uploaders: Roger Leigh rle...@debian.org, Thomas Goirand z...@debian.org, Benda Xu hero...@gentoo.org, Ritesh Raj Sarraf r...@debian.org -Build-Depends: debhelper (= 9) +Build-Depends: debhelper (= 9), libselinux1-dev [linux-any] Standards-Version: 3.9.5 Homepage: http://www.gentoo.org/proj/en/base/openrc/ Vcs-Git: git://anonscm.debian.org/openrc/openrc.git diff -Nru openrc-0.13.1/debian/rules openrc-0.13.1/debian/rules --- openrc-0.13.1/debian/rules 2014-10-26 17:34:13.0 +0100 +++ openrc-0.13.1/debian/rules 2014-12-16 14:43:24.0 +0100 @@ -23,6 +23,10 @@ export LIBEXECDIR = /lib/rc #export OS = Linux +ifeq (linux,$(DEB_HOST_ARCH_OS)) +export MKSELINUX = yes +endif + %: dh $@
Bug#773288: tracker.debian.org: please display descriptions and maintainers for pseudo-packages
Package: tracker.debian.org Severity: wishlist The pages for pseudo-packages do not display the official descriptions and maintainers for them, for example: https://tracker.debian.org/pkg/tracker.debian.org There are plain text files with maintainers and descriptions here: https://bugs.debian.org/pseudopackages/pseudo-packages.description https://bugs.debian.org/pseudopackages/pseudo-packages.maintainers I don't know if distro-tracker supports translations but if so, the official translations of the pseudo-package descriptions are here: https://anonscm.debian.org/viewvc/webwml/webwml/bulgarian/Bugs/pseudo-packages.translated-description?view=co https://anonscm.debian.org/viewvc/webwml/webwml/chinese/Bugs/pseudo-packages.translated-description?view=co https://anonscm.debian.org/viewvc/webwml/webwml/finnish/Bugs/pseudo-packages.translated-description?view=co https://anonscm.debian.org/viewvc/webwml/webwml/french/Bugs/pseudo-packages.translated-description?view=co https://anonscm.debian.org/viewvc/webwml/webwml/german/Bugs/pseudo-packages.translated-description?view=co https://anonscm.debian.org/viewvc/webwml/webwml/italian/Bugs/pseudo-packages.translated-description?view=co https://anonscm.debian.org/viewvc/webwml/webwml/japanese/Bugs/pseudo-packages.translated-description?view=co https://anonscm.debian.org/viewvc/webwml/webwml/norwegian/Bugs/pseudo-packages.translated-description?view=co https://anonscm.debian.org/viewvc/webwml/webwml/polish/Bugs/pseudo-packages.translated-description?view=co https://anonscm.debian.org/viewvc/webwml/webwml/portuguese/Bugs/pseudo-packages.translated-description?view=co https://anonscm.debian.org/viewvc/webwml/webwml/russian/Bugs/pseudo-packages.translated-description?view=co https://anonscm.debian.org/viewvc/webwml/webwml/spanish/Bugs/pseudo-packages.translated-description?view=co https://anonscm.debian.org/viewvc/webwml/webwml/ukrainian/Bugs/pseudo-packages.translated-description?view=co -- bye, pabs https://wiki.debian.org/PaulWise signature.asc Description: This is a digitally signed message part
Bug#773289: [mysql-workbench] Cannot add columns in EER editor
Package: mysql-workbench Version: 6.1.7+dfsg-1 Severity: important --- Please enter the report below this line. --- Dear maintainers: It seems there is no way to add columns after a new table has been created using the (visual) EER editor. Issue is always reproducible this way, even editing the sakila sample schema. Regards, Antonio --- System information. --- Architecture: amd64 Kernel: Linux 3.16-2-amd64 Debian Release: jessie/sid 700 stable dl.google.com 650 testing security.debian.org 650 testing ftp.es.debian.org 500 sid linux.dropbox.com --- Package information. --- Depends (Version) | Installed =-+-=== libatkmm-1.6-1 (= 2.22.1) | 2.22.7-2.1 libc6 (= 2.14) | libcairo2 (= 1.12.0) | libctemplate2 | libgcc1 (= 1:4.1.1) | libgdk-pixbuf2.0-0 (= 2.22.0) | libgl1-mesa-glx | OR libgl1 | libglib2.0-0 (= 2.35.9) | libglibmm-2.4-1c2a (= 2.40.0) | libgnome-keyring0 (= 2.22.2) | libgtk2.0-0 (= 2.24.0) | libgtkmm-2.4-1c2a (= 1:2.24.0) | liblua5.1-0 | libmysqlclient18 (= 5.5.24+dfsg-1) | libmysqlcppconn7 (= 1.1.3) | libodbc1 (= 2.3.1) | libpango-1.0-0 (= 1.18.0) | libpangocairo-1.0-0 (= 1.14.0) | libpangomm-1.4-1 (= 2.27.1) | libpcre3 (= 8.10) | libpcrecpp0 (= 7.7) | libpython2.7 (= 2.7) | libsigc++-2.0-0c2a (= 2.2.0) | libstdc++6 (= 4.9) | libtinyxml2.6.2 | libuuid1 (= 2.16) | libvsqlitepp3 (= 0.3.13) | libx11-6 | libxml2 (= 2.7.4) | libzip2 (= 0.10) | python:any (= 2.6.6-7~) | python2.7 | mysql-workbench-data (= 6.1.7+dfsg-1) | virtual-mysql-client | python-mysql.connector | python-paramiko | python-pexpect | python-pyodbc (= 2.1.8) | python-pysqlite2 | Recommends (Version) | Installed =-+-=== ttf-bitstream-vera | 1.10-8 mysql-utilities | 1.3.5-2 Suggests (Version) | Installed -+-=== gnome-keyring | 3.14.0-1+b1 -- ** Antonio Marcos López Alonso Servicio de Informática y Telecomunicaciones Instituto de Productos Naturales y Agrobiología (IPNA-CSIC) mailto:a...@ipna.csic.es (+34) 922 260 190 (Ext. 237) *** -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#773290: unblock: squid3/3.4.8-5
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: unblock
Please unblock package squid3
This versione fixes serious bug #773032, which affects upgrades from wheezy to
jessie when no change has been made to the original configuration file.
diff -Nru squid3-3.4.8/debian/changelog squid3-3.4.8/debian/changelog
--- squid3-3.4.8/debian/changelog 2014-12-05 10:46:41.0 +0100
+++ squid3-3.4.8/debian/changelog 2014-12-16 14:33:14.0 +0100
@@ -1,3 +1,11 @@
+squid3 (3.4.8-5) unstable; urgency=medium
+
+ [ Luigi Gangitano lu...@debian.org ]
+ * debian/squid3.{pre,post}inst
+- Moved ACL manager fix to postinst (Closes: #773032)
+
+ -- Luigi Gangitano lu...@debian.org Tue, 16 Dec 2014 13:43:03 +0100
+
squid3 (3.4.8-4) unstable; urgency=medium
[ Luigi Gangitano lu...@debian.org ]
diff -Nru squid3-3.4.8/debian/squid3.postinst
squid3-3.4.8/debian/squid3.postinst
--- squid3-3.4.8/debian/squid3.postinst 2014-12-05 10:46:41.0 +0100
+++ squid3-3.4.8/debian/squid3.postinst 2014-12-16 14:33:14.0 +0100
@@ -62,8 +62,28 @@
echo Creating Squid HTTP proxy 3.x spool directory
structure
squid3 -z
fi
+
+ #
+ # Remove obsolete manager ACL definition.
+ # It will halt upgrade with fatal error if left.
+ #
+ if test -f /etc/squid3/squid.conf dpkg --compare-versions
$2 lt '3.4' grep -q ^[[:blank:]]*acl manager /etc/squid3/squid.conf ;
then
+ echo Filtering squid.conf manager ACL.
+ cp /etc/squid3/squid.conf
/etc/squid3/squid.conf.pre_3.4_upgrade
+ sed -e s/^\([ \t]*acl manager.*\)/# \1 # Commented out
on upgrade to 3.4/ /etc/squid3/squid.conf.pre_3.4_upgrade
/etc/squid3/squid.conf
+ fi
+ ;;
+ abort-upgrade)
+ #
+ # Revert the automated configuration changes we may have done
+ #
+ if test -f /etc/squid3/squid.conf.pre_3.4_upgrade; then
+ echo Removing squid.conf changes.
+ mv /etc/squid3/squid.conf.pre_3.4_upgrade
/etc/squid3/squid.conf
+ fi
+ exit 0
;;
- abort-upgrade|abort-remove|abort-deconfigure)
+ abort-remove|abort-deconfigure)
;;
*)
#
diff -Nru squid3-3.4.8/debian/squid3.preinst squid3-3.4.8/debian/squid3.preinst
--- squid3-3.4.8/debian/squid3.preinst 2014-12-05 10:46:41.0 +0100
+++ squid3-3.4.8/debian/squid3.preinst 2014-12-16 14:33:14.0 +0100
@@ -4,24 +4,8 @@
case $1 in
upgrade|install-upgrade)
- #
- # Remove obsolete manager ACL definition.
- # It will halt upgrade with fatal error if left.
- #
- if test -f /etc/squid3/squid.conf dpkg --compare-versions
$2 lt '3.4.8-3' grep -q ^[[:blank:]]*acl manager /etc/squid3/squid.conf
; then
- echo Filtering squid.conf manager ACL.
- cp /etc/squid3/squid.conf
/etc/squid3/squid.conf.pre_3.4_upgrade
- sed -e s/^\([ \t]*acl manager.*\)/# \1 # Commented out
on upgrade to 3.4/ /etc/squid3/squid.conf.pre_3.4_upgrade
/etc/squid3/squid.conf
- fi
;;
abort-upgrade)
- #
- # Revert the automated configuration changes we may have done
- #
- if test -f /etc/squid3/squid.conf.pre_3.4_upgrade; then
- echo Removing squid.conf changes.
- mv /etc/squid3/squid.conf.pre_3.4_upgrade
/etc/squid3/squid.conf
- fi
exit 0
;;
esac
unblock squid3/3.4.8-5
-- System Information:
Debian Release: 8.0
APT prefers unstable
APT policy: (500, 'unstable')
Architecture: i386 (i686)
Foreign Architectures: amd64
Kernel: Linux 3.16.0-4-686-pae (SMP w/2 CPU cores)
Locale: LANG=it_IT.UTF-8, LC_CTYPE=it_IT.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash
Init: sysvinit (via /sbin/init)
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#773291: Unable to inherit groups from user
Package: python-daemon Version: 1.5.5-1 Severity: normal It seems impossible to daemonise a programme with python-daemon without overwriting additional groups defined for the user that should run the daemon. For instance, I am trying to run bcfg2-server, which does self.context = daemon.DaemonContext(uid=self.setup['daemon_uid'], gid=self.setup['daemon_gid'], …) and the user to use is uid=105(bcfg2) gid=111(bcfg2) groups=111(bcfg2),110(ssl-cert) but even if I do not pass the gid value to DaemonContext, then then process is unable to read this file: -rw-r- 1 root ssl-cert 1704 Dec 16 14:08 /etc/ssl/private/ssl-cert-snakeoil.key -- System Information: Debian Release: 8.0 APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 3.17-1-amd64 (SMP w/8 CPU cores) Locale: LANG=en_NZ, LC_CTYPE=en_NZ.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: sysvinit (via /sbin/init) -- .''`. martin f. krafft madduck@d.o @martinkrafft : :' : proud Debian developer `. `'` http://people.debian.org/~madduck `- Debian - when you have better things to do than fixing systems digital_signature_gpg.asc Description: Digital signature (see http://martin-krafft.net/gpg/sig-policy/999bbcc4/current)
Bug#772994: Might I take this package
Hi! I see you've taken up quite a number of wnpp packages recently - thanks for dealing with these :) I'd be quite interested in taking over the PCRE3 package, though, so would you mind if I took this one instead of you? Regards, Matthew -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#773252: systemd-timesyncd syncs time about once per minute
On 12/16/2014 09:31 PM, Michael Biebl wrote: Am 16.12.2014 um 14:07 schrieb Michael Biebl: Am 16.12.2014 um 04:45 schrieb Jos van Wolput: Package: systemd Version: 215-8 and 218-1 Severity: normal Dear Maintainer, Systemd-timesyncd syncs time about once per 60 seconds. What makes you think systemd-timesync syncs the clock once every 60 seconds? I just studied the code and timesyncd starts with a minimal 32 second interval (NTP_POLL_INTERVAL_MIN_SEC) which is increased until it reaches the maximum 2048 second polling interval (NTP_POLL_INTERVAL_MAX_SEC). It seems to use an exponential like back-off algorithm as shown by the journal Dez 16 14:07:41 pluto systemd-timesyncd[12409]: interval/delta/delay/jitter/drift 32s/+0.253s/0.028s/0.000s/+500ppm Dez 16 14:08:13 pluto systemd-timesyncd[12409]: interval/delta/delay/jitter/drift 64s/-0.005s/0.025s/0.002s/+460ppm Dez 16 14:09:17 pluto systemd-timesyncd[12409]: interval/delta/delay/jitter/drift 128s/-0.022s/0.040s/0.008s/+373ppm Dez 16 14:11:25 pluto systemd-timesyncd[12409]: interval/delta/delay/jitter/drift 128s/-0.053s/0.024s/0.050s/+165ppm Dez 16 14:13:33 pluto systemd-timesyncd[12409]: interval/delta/delay/jitter/drift 256s/+0.030s/0.124s/0.055s/+165ppm (ignored) Dez 16 14:17:50 pluto systemd-timesyncd[12409]: interval/delta/delay/jitter/drift 256s/-0.056s/0.026s/0.052s/+55ppm Dez 16 14:22:06 pluto systemd-timesyncd[12409]: interval/delta/delay/jitter/drift 512s/-0.012s/0.025s/0.050s/+43ppm Dez 16 14:30:38 pluto systemd-timesyncd[12409]: interval/delta/delay/jitter/drift 1024s/+0.046s/0.149s/0.059s/+43ppm (ignored) roughly 30s - 1m, 1m - 2m, 2m - 4m, 4m - 8m ... This looks like a sensible approach to me. After half an hour I stll get an interval of 32. it doesn't increase exponentialy: Dec 16 21:24:42 debian systemd-timesyncd[24099]: interval/delta/delay/jitter/drift 64s/+0.030s/0.192s/0.043s/+500ppm Dec 16 21:25:47 debian systemd-timesyncd[24099]: interval/delta/delay/jitter/drift 32s/+0.194s/0.095s/0.154s/+500ppm Dec 16 21:26:19 debian systemd-timesyncd[24099]: interval/delta/delay/jitter/drift 32s/+0.084s/0.111s/0.142s/+500ppm . Dec 16 22:01:01 debian systemd-timesyncd[24099]: interval/delta/delay/jitter/drift 32s/+0.065s/0.116s/0.018s/+500ppm Dec 16 22:01:33 debian systemd-timesyncd[24099]: interval/delta/delay/jitter/drift 32s/+0.065s/0.110s/0.017s/+500ppm Dec 16 22:02:05 debian systemd-timesyncd[24099]: interval/delta/delay/jitter/drift 32s/+0.062s/0.104s/0.015s/+500ppm Dec 16 22:02:38 debian systemd-timesyncd[24099]: interval/delta/delay/jitter/drift 32s/+0.062s/0.097s/0.005s/+500ppm Dec 16 22:03:10 debian systemd-timesyncd[24099]: interval/delta/delay/jitter/drift 32s/+0.110s/0.097s/0.019s/+500ppm -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#773237: dovecot-core: Should not use UCF for 10-ssl.conf
On Tue, 16 Dec 2014, Santiago Vila wrote: My objection is that policy says that the conffile mechanism is only appropriate for files having a default that may work for everybody, and the rationale is that if most people need to modify it, then most people will get prompted on upgrades over and over again. The package has to ship some kind of default or the server will not start. As you say there isn't a default which will satisfy everyone so we expect it to be changed by many users. But with normal operation of dpkg, new versions of the package will silently overwrite the changes. The only way to prevent this is to make it a conffile. The current default disables SSL, which is insecure. We can't honestly claim that an insecure default will work for most people. Sure it will. You will be able to receive IMAP and POP3 mail which is what an imapd/pop3d does. As a best practice you _should_ do IMAP/POP3 over SSL but it is not required. And I fully agree that in this day and age the more encryption working out of the box the better. But this has to be done right because half-assed security is worse than no security at all. There are many different scenarios: self-signed certificate versus purchased from a CA, different locations, different expiration policies etc. The previous code was not accounting for all of this properly. So the only configuration the package can ship which will definitely work for all people is SSL disabled. Atleast now a security-minded user knows where he stands and can harden the package the way he wants. I encourage you to work on a centralized SSL cert handling facility for Debian that not only dovecot but all server packages can use. I will gladly use it. -- Jaldhar H. Vyas jald...@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#773267: Provide a means to query fsck whether it would run a routine check
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 reassign 773267 e2fsprogs thanks On 12/16/2014 3:36 AM, martin f krafft wrote: Package: util-linux Version: 2.25.2-3 Severity: wishlist File: /sbin/fsck Tags: upstream In the context of #773035, I am looking for a way to figure out whether a reboot *now* would be likely to cause lengthy fsck routine checks, e.g. due to the maximal mount count or days since last check being reached on ext-filesystems. I'd like to avoid parsing debug2fs or tune2fs output and comparing numbers or timestamps in the text output, like /usr/lib/update-notifier/update-motd-fsck-at-reboot seems to be doing on Ubuntu. Instead, I'd really like to just ask fsck. fsck -A -t ext2,ext3,ext4,… -N is already very helpful showing me which filesystem-specific commands it would run, but each of those is run unconditionally on the filesystem and determines by itself whether a check is needed. The mount count fsck is specific to ext2 ( for that matter, it is at this point, a silly anachronism that many people disable.. iirc it is disabled by default these days on ubuntu ) so there is no reason to generalize it to fsck. I'm reassigning to e2fsprogs so they can consider adding something to e2fsck but my guess is they will say to just use tune2fs. -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.17 (MingW32) iQEcBAEBAgAGBQJUkD9QAAoJENRVrw2cjl5RfYQIAKSh8ys5NInZZukS2M9TCuhC VldRdW+xse1xyIwp4RbhFQ/yuhTvdo9fDBXsG+eDKLKD/gTwRjDPd0XZQjZB9fyv dz357+iLG4RCY0P7UI9j3j+G38DRtWUR8wR4HnglcCaBUHUirXbZ5LPosklHXLLE NMR5f/oOSRVYN1F8h5K7JdKVaiMujVAbGsckWa+gU4/QySJ4TSR3gn/0wm6891cS sl8W0KG7vjSsRAaExdIAmgdZwOsjW+5jZ2bGTzYl+aAUb5iLgE/F9EZikc4W2uaG qPe3+klny4dkuZGpEZuOU35w/r6njBiIbqe0U9VsACkmZ5Kg8nShKPyvWoUznBM= =dA03 -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#773292: dochelp's zsh completion not working
Package: dochelp
Version: 0.1.2+b1
Severity: normal
When trying dochelp's zsh completion feature, it instead
gives me an error message when I press the [Tab] key:
% dochelp [TAB]
_arguments:comparguments:312: invalid argument: (--list){--list}[List
available documents]
Tested while running under zsh (5.0.7-5).
Thanks!
Anthony
-- System Information:
Debian Release: 8.0
APT prefers unstable
APT policy: (500, 'unstable'), (500, 'stable'), (500, 'oldstable'), (1,
'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 3.16.0-4-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_CA.utf8, LC_CTYPE=en_CA.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
Versions of packages dochelp depends on:
ii libc6 2.19-13
ii libjs-jquery 1.7.2+dfsg-3.2
ii libpcre3 2:8.35-3.3
dochelp recommends no packages.
dochelp 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#773293: kde-plasma-desktop: Can't install kde-plasma-desktop non-interactively due to kdm configuration dialog
Source: kde-plasma-desktop Severity: important Dear Maintainer, I am trying to install kde-plasma-desktop non-interactively (i.e. from a script). kde-plasma-desktop pulls in both lightdm and kdm packages, both of which want to be the default display manager. I am using debconf-set-selections to set the shared/default-x-display-manager question for both kdm and lightdm before running apt-get, to avoid interaction. Unfortunately the dialog is still presented to choose kdm or lightdm. If I use DEBIAN_FRONTEND=non-interactive apt-get install I avoid the interaction, but the configuration database values are overwritten to prefer kdm. -- 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-40-generic (SMP w/1 CPU core) Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968) 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#773294: tracker.debian.org: add support for the vcswatch service
Package: tracker.debian.org
Severity: wishlist
Please add support for the vcswatch service:
* an action item for packages with an error or unreleased changes
* a link in the right column for packages mentioned in the data
URLs to package status:
https://qa.debian.org/cgi-bin/vcswatch?package=%{package}
A data export is available here:
https://qa.debian.org/data/vcswatch/vcswatch.json.gz
--
bye,
pabs
https://wiki.debian.org/PaulWise
signature.asc
Description: This is a digitally signed message part
Bug#771154: plink: New major upstream version of plink
Hi Bob On Thu, Nov 27, 2014 at 08:31:29AM +0100, Bob Dybian wrote: Package: plink Severity: wishlist Dear Maintainer, Plink2 [1] was just presented at the annual meeting of the American Society of Human Genetics 2014 [2]. Plink2 is a comprehensive update of plink with new algorithms and new methods, faster and less memory consumer than the first plink. As it was not totally compatible with first plink [1], I propose to create a new package to permit the cohabitation of these two versions (like for bowtie and bowtie2). If you agree, I will submit it [3] on Alioth. In case you might wait for a confirmation and wondering why nobody is sending one: Usually there is no reason at all to stop anybody from working so you can simply enject your packaging without asking. Just ping the list if you need a sponsor. For this actual case I wonder whether plink2 would be a drop in replacement we can provide instead of the old pling (which means the interface is compatible and the test suite if there is any creates the same results) or whether you think plink and plink2 should be provided in parallel. Kind regards and thanks for your work on this Andreas. -- http://fam-tille.de -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#773238: [Pkg-xfce-devel] Bug#773238: xfce4-panel: notification-area broken?
It is a confirmed problem with Dropbox latest update. Thank you for replying. /o On Tue, 16 Dec 2014 11:18:03 +0100 Yves-Alexis Perez cor...@debian.org wrote: On lun., 2014-12-15 at 21:59 +0100, oggesjolin wrote: Package: xfce4-panel Version: 4.8.6-4 Severity: normal Dear Maintainer, For reasons unknown, Dropbox icon does not show in the notification area panel- plugin, other running applications show (wicd/spotify/xchat) Try with a different panel size. It might just be that dropbox doesn't ship correct icon size. You can also strace the panel plugin (systray.so) to check if there's any obvious error. I tried add a new 'notification-area', and noticed it was greyed out. Seems I can no longer add a 'notification-area' to any panel. Well, yes, multiple systray / notification area don't make any sense. Regards, -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#773267: Provide a means to query fsck whether it would run a routine check
also sprach Phillip Susi ps...@ubuntu.com [2014-12-16 15:18 +0100]: The mount count fsck is specific to ext2… No other filesystems have routine checks that could run during startup? I seem to remember XFS had those too… If it's only ext2,3,4, then by all means. But if there are others, then I guess it should be generalised. -- .''`. martin f. krafft madduck@d.o @martinkrafft : :' : proud Debian developer `. `'` http://people.debian.org/~madduck `- Debian - when you have better things to do than fixing systems although occasionally there is something to be said for solitude. -- special agent dale cooper digital_signature_gpg.asc Description: Digital signature (see http://martin-krafft.net/gpg/sig-policy/999bbcc4/current)
Bug#773295: ITP: zetacoin -- P2P network based digital currency with fast confirmations
Package: wnpp Severity: wishlist Owner: Daniel Morante dan...@morante.net Package name: zetacoin Version : 0.9.2.4 Upstream Author : Giskard unknown URL : http://www.zetacoin.com/ License : (MIT/X) Programming Lang: (C, C++) Description : P2P network based digital currency with fast confirmations -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#773007: Doesn't work on i386, crashes also
On Mon, Dec 15, 2014 at 01:38:34PM -0600, D. Jared Dominguez wrote: Hrmph. There was a 32-bit issue in 0.9.0-1 that was supposed to be fixed in 0.9.0-2: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=764797 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=764796 Any chance you can test with efibootmgr from unstable? I've looked at the changes upstream and don't see anything that seems like it'd be relevant to efibootmgr -v segfaulting. However, about efibootmgr -c -d /dev/sda -o 1 -w -L debian -l \EFI\debian\grubia32.efi failing, these changes are in unstable's efibootmgr and might be relevant: 8c725c629f2ead41532c4b908e9c713187a7f564 - Make -o's behavior actually match the documented behavior. b857ce058d6f7fa3fa47c839bc86de243cd1fd4e - Make all the other places we're parsing also do a better job. Once you test against unstable's efibootmgr, Peter Jones (upstream) can help us try to triage this bug more. Same behaviour using current upstream head - see the comments in upstream's issue tracker: https://github.com/vathpela/efibootmgr/issues/21 https://github.com/vathpela/efivar/issues/11 Relatedly, there are a bunch of fixes since 0.9.0-2. Actually, all changes since then are bug fixes. How hard would it be at this point in the game to get an exception to pull 0.11.0 into testing? Depends on how big they are, I guess, and how important they look. There are serious issues here, but not all of the changes are just serious bugfixes AFAICS? -- Steve McIntyre, Cambridge, UK.st...@einval.com Into the distance, a ribbon of black Stretched to the point of no turning back -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#773296: tracker.debian.org: add support for package l10n status
Package: tracker.debian.org
Severity: wishlist
Tags: l10n
Please add support for package l10n status:
* an action item when the data export indicates a todo item
* a link l10n in the right column with the completeness stats
The data export is available here:
http://i18n.debian.org/l10n-pkg-status/pkglist
The URLs for l10n status reports are in the data export but are:
http://i18n.debian.org/l10n-pkg-status/${hash}/${package}.html
The old PTS code has support for parsing this and displaying it.
--
bye,
pabs
https://wiki.debian.org/PaulWise
signature.asc
Description: This is a digitally signed message part
Bug#773237: dovecot-core: Should not use UCF for 10-ssl.conf
On Tue, Dec 16, 2014 at 09:14:11AM -0500, Jaldhar H. Vyas wrote: On Tue, 16 Dec 2014, Santiago Vila wrote: My objection is that policy says that the conffile mechanism is only appropriate for files having a default that may work for everybody, and the rationale is that if most people need to modify it, then most people will get prompted on upgrades over and over again. The package has to ship some kind of default or the server will not start. As you say there isn't a default which will satisfy everyone so we expect it to be changed by many users. But with normal operation of dpkg, new versions of the package will silently overwrite the changes. The only way to prevent this is to make it a conffile. The only way? That's simply *not* true! It is perfectly allowed *not* to ship a configuration file inside the .deb and instead create it in the postinst, only if it does not exist. Please see /var/lib/dpkg/info/base-files.postinst for examples, where the install_from_default shell function is used to create files from the defaults, only the very first time the package is installed. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
