Bug#813008: pacemaker-remote: The dummy RA belongs to the pacemaker package

[Ferenc Wágner]

Package: pacemaker-remote
Severity: normal

The pacemaker_remoted daemon runs on "remote" nodes instead of Pacemaker
proper, but the ocf:pacemaker:remote RA is built into crmd running on
"local" nodes.  /usr/lib/ocf/resource.d/pacemaker/remote is a dummy RA
script providing metadata for this built-in RA, thus it should be packaged
together with it.  The same goes for its man page.

Bug#813007: Fix container detection (running-in-container is an Ubuntu-ism)

[Martin Pitt]

Package: grub2
Version: 2.02~beta2-35
Tags: patch
User: ubuntu-de...@lists.ubuntu.com
Usertags: origin-ubuntu ubuntu-patch xenial

Hello,

grub2 currently tries to call running-in-container in its postinst and
zz-update-grub. This script is an Ubuntu-ism and going away (see
https://launchpad.net/bugs/1539016), and thus container detection does
not work under Debian.

Please use systemd-detect-virt --container instead, which works under
any init system (despite the name). running-in-container is just an
(overly complicated) wrapper around systemd-detect-virt.

debdiff attached.

Thanks for considering,

Martin

-- 
Martin Pitt| http://www.piware.de
Ubuntu Developer (www.ubuntu.com)  | Debian Developer  (www.debian.org)
diff -Nru grub2-2.02~beta2/debian/changelog grub2-2.02~beta2/debian/changelog
--- grub2-2.02~beta2/debian/changelog   2016-01-22 12:02:11.0 +0100
+++ grub2-2.02~beta2/debian/changelog   2016-01-28 14:30:23.0 +0100
@@ -1,3 +1,10 @@
+grub2 (2.02~beta2-35ubuntu1) xenial; urgency=medium
+
+  * debian/postinst.in, debian/kernel/zz-update-grub: Call systemd-detect-virt
+instead of the Ubuntu specific running-in-container wrapper. (LP: #1539016)
+
+ -- Martin Pitt   Thu, 28 Jan 2016 14:25:14 +0100
+
 grub2 (2.02~beta2-35) unstable; urgency=medium
 
   * Apply the arm64 -mpc-relative-literal-loads workaround in configure
diff -Nru grub2-2.02~beta2/debian/kernel/zz-update-grub 
grub2-2.02~beta2/debian/kernel/zz-update-grub
--- grub2-2.02~beta2/debian/kernel/zz-update-grub   2016-01-22 
12:00:21.0 +0100
+++ grub2-2.02~beta2/debian/kernel/zz-update-grub   2016-01-28 
14:27:16.0 +0100
@@ -3,8 +3,8 @@
 
 which update-grub >/dev/null 2>&1 || exit 0
 
-if type running-in-container >/dev/null 2>&1 && \
-   running-in-container >/dev/null; then
+if type systemd-detect-virt >/dev/null 2>&1 &&
+   systemd-detect-virt --quiet --container; then
exit 0
 fi
 
diff -Nru grub2-2.02~beta2/debian/postinst.in 
grub2-2.02~beta2/debian/postinst.in
--- grub2-2.02~beta2/debian/postinst.in 2016-01-22 12:00:21.0 +0100
+++ grub2-2.02~beta2/debian/postinst.in 2016-01-28 14:30:22.0 +0100
@@ -296,7 +296,7 @@
 
 running_in_container()
 {
-  type running-in-container >/dev/null 2>&1 && running-in-container >/dev/null
+  type systemd-detect-virt >/dev/null 2>&1 && systemd-detect-virt --quiet 
--container
 }
 
 run_grub_install()


signature.asc
Description: Digital signature

Bug#813020: please multiarchify the library packages

[Matthias Klose]

On 28.01.2016 17:03, Thomas Schmitt wrote:

Hi,

i am the Uploader who maintains the ./debian repository of
libburn, libisofs, and libisoburn (not the Maintainer who uploads).

When i took over, i asked for advise about "Multi-Arch:" and
"Pre-Depends:"
   https://lists.debian.org/debian-mentors/2015/09/msg00403.html

I got clear statements not to use them from Niels Thykier, Jakub Wilk,
and Santiago Vila:
   https://lists.debian.org/debian-mentors/2015/09/msg00408.html
   https://lists.debian.org/debian-mentors/2015/09/msg00409.html
   https://lists.debian.org/debian-mentors/2015/09/msg00416.html
Wookey had some mild scruples:
   https://lists.debian.org/debian-mentors/2015/09/msg00419.html

So we would have to discuss the topic again on debian-mentors
before i noob will override the opinion of the experts.


all these comments are about the Pre-Depends field. and I can't see anything 
that explicitly forbids this at this point of time. This attribute doesn't hurt 
for now, hundreds of packages still have it. I think nobody questions to make 
library packages M-A same.


Matthias

Bug#813016: openvdb: add direct build-dependency on libglu

[James Cowgill]

Source: openvdb
Version: 3.1.0-2
Severity: normal

Hi,

Recently GLFW3 dropped its GLU requirement upstream so that you can use
it without GLU being installed. I would also like to drop the
dependency in libglfw3-dev, but openvdb failes to build when I do this
since it uses GLU headers.

Please directly build-depend on 'libglu1-mesa-dev | libglu1-dev' so I
can drop the dependency.

Thanks,
James

signature.asc
Description: This is a digitally signed message part

Bug#807229: [Debichem-devel] Bug#807229: votca-tools: diff for NMU version 1.2.4-1.1

[Michael Banck]

Hi,

On Tue, Jan 26, 2016 at 10:42:36AM +, Mattia Rizzolo wrote:
> I've prepared an NMU for votca-tools (versioned as 1.2.4-1.1) and
> uploaded it to DELAYED/2. Please feel free to tell me if I
> should delay it longer.

Well, thanks for fixing that bug, but there's an upload for the GCC5
transition waiting in NEW, not sure what happens with that now.

I was ill the last few days, so missed your message.


Michael

Bug#813025: O: libmowgli

[Andrew Shadura]

Package: wnpp
Severity: normal

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

I'm hereby orphaning libmowgli.

- -- 
Cheers,
  Andrew

-BEGIN PGP SIGNATURE-
Version: GnuPG v1

iQEcBAEBAgAGBQJWqjK4AAoJEJ1bI/kYT6UUx04H/1ypvx6kU27wvI6w5Jsy3q+2
JBTRPwl7VdIjb7Rj8tV68NF9aVS+8RiE4EzNRcYS4vIkgId4uJledYuK4P3v7X9p
3jlHCI2XRxr+cTL8Bxkn07g3Pkqy7wu/uhdl7lTmzEQ/6Pr8dJJSmG7trtwxtzqM
kzfPX986bENEJalyN1g2E9R/W/K1nKAHrigr8hMPG8akFCIgXIgAHJcA1Sr2Bh/c
YLkk/CzSJvDuyhMO++0+11bcMpRdyONRrloexAuNfY9vc2+Nrrhpp4y2lo/ACUQL
QK/OlwJoETklygbF77kmG5GNWPpLHq+xLi7wgjOTSTyXtyO2w1QYTGWVV9zpuZk=
=gPl0
-END PGP SIGNATURE-

Bug#811497: Unclean shutdown after switch from sysvinit-core to systemd-sysv

[Michael Biebl]

Control: retitle -1 Unclean shutdown after switch from sysvinit-core to 
systemd-sysv

After further investigation, it shows that the unclean shutdown
also happens if systemd-shim is not installed. Having systemd-shim installed
only leads to the 30s timeout on reboot.

I suspect this is a bug in sysvinit, which fails to shutdown properly
 once it has been deleted.

-- 
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#813024: O: libixp

[Andrew Shadura]

Package: wnpp
Severity: normal

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

I'm orphaning the libixp package, since I do not use it any longer.

- -- 
Cheers,
  Andrew

-BEGIN PGP SIGNATURE-
Version: GnuPG v1

iQEcBAEBAgAGBQJWqjJRAAoJEJ1bI/kYT6UUKT8H/0YQMSX5V9LZWL2j5w7Ys1Mz
Ng8S3zhXBEUT4bbCVwkQHZ8aaEdtKUJ5NgK5rdUa49giYBOQ4BSyXAfS4qXtRgG/
puERqKr+a8ZfJndknka8BJtEyDxm+qakZskX2+HPz5k9dc6d4AdixVZGQHBploOF
f1l3zrFDM/E5rurPJhUiCt/bQT/TAtSkO51GSClvFkvRS+P1JUJnB9fY7wnQqNdd
YrdFQh0HZFDbV6yQpPalMuHyyLv7z1WW8NWC6SrZyboi73zOATURlUb30n6rKC9+
RT17WbkgOBovyq09PSQ6V+4824qUBTumCV7QdW65qppFLsa45TfpdOw8AgWfixQ=
=fU6f
-END PGP SIGNATURE-

Bug#813028: python-markdown: FTBFS: (failed test) testHighlightLinesWithColon (tests.test_extensions.TestCodeHilite)

[Chris Lamb]

Source: python-markdown
Version: 2.6.5-1
Severity: serious
Justification: fails to build from source
User: reproducible-bui...@lists.alioth.debian.org
Usertags: ftbfs
X-Debbugs-Cc: reproducible-bui...@lists.alioth.debian.org

Dear Maintainer,

python-markdown fails to build from source in unstable/amd64:

  [..]
  
  ==
  FAIL: testHighlightLinesWithColon (tests.test_extensions.TestCodeHilite)
  --
  Traceback (most recent call last):
File 
"/home/lamby/temp/cdt.20160128164608.xbU26qfoyC/python-markdown-2.6.5/tests/test_extensions.py",
 line 213, in testHighlightLinesWithColon
  ''
  AssertionError: u'#line 
1\n#line 1\n#line 1
  ?-
  + #line 1
  - #line 2
  ? -
  + #line 2
  - #line 3
  ?  -
  + #line 3

   >> begin captured logging << 
  MARKDOWN: DEBUG: Successfuly imported extension module 
"markdown.extensions.codehilite".
  MARKDOWN: DEBUG: Successfully loaded extension 
"markdown.extensions.codehilite.CodeHiliteExtension".
  - >> end captured logging << -
  
  ==
  FAIL: testLinenumsFalse (tests.test_extensions.TestCodeHilite)
  --
  Traceback (most recent call last):
File 
"/home/lamby/temp/cdt.20160128164608.xbU26qfoyC/python-markdown-2.6.5/tests/test_extensions.py",
 line 139, in testLinenumsFalse
  ''
  AssertionError: u'# A Code 
Comment\n< [truncated]... != u'# A Code Comment\n# A Code Comment
  ?-
  + # A Code Comment

   >> begin captured logging << 
  MARKDOWN: DEBUG: Successfully loaded extension 
"markdown.extensions.codehilite.CodeHiliteExtension".
  - >> end captured logging << -
  
  ==
  FAIL: testLinenumsNoneWithColon (tests.test_extensions.TestCodeHilite)
  --
  Traceback (most recent call last):
File 
"/home/lamby/temp/cdt.20160128164608.xbU26qfoyC/python-markdown-2.6.5/tests/test_extensions.py",
 line 192, in testLinenumsNoneWithColon
  ''
  AssertionError: u'# A Code 
Comment\n< [truncated]... != u'# A Code Comment\n# A Code Comment
  ?-
  + # A Code Comment

   >> begin captured logging << 
  MARKDOWN: DEBUG: Successfully loaded extension 
"markdown.extensions.codehilite.CodeHiliteExtension".
  - >> end captured logging << -
  
  ==
  FAIL: Test Fenced Code with Highlighted Lines.
  --
  Traceback (most recent call last):
File 
"/home/lamby/temp/cdt.20160128164608.xbU26qfoyC/python-markdown-2.6.5/tests/test_extensions.py",
 line 377, in testFencedLanguageAndHighlightLines
  ''
  AssertionError: u'#line 1 [truncated]... != u'#line 1\ 
[truncated]...
  - #line 
1
  ?  -
  + #line 
1
  - #line 2
  ?  -
  + #line 2
  - #line 3
  ? -
  + #line 3

   >> begin captured logging << 
  MARKDOWN: DEBUG: Successfuly imported extension module 
"markdown.extensions.fenced_code".
  MARKDOWN: DEBUG: Successfully loaded extension 
"markdown.extensions.fenced_code.FencedCodeExtension".
  MARKDOWN: DEBUG: Successfully loaded extension 
"markdown.extensions.codehilite.CodeHiliteExtension".
  MARKDOWN: DEBUG: Successfuly imported extension module 
"markdown.extensions.fenced_code".
  MARKDOWN: DEBUG: Successfully loaded extension 
"markdown.extensions.fenced_code.FencedCodeExtension".
  - >> end captured logging << -
  
  --
  Ran 270 tests in 1.356s
  
  FAILED (SKIP=1, failures=4)
  E: pybuild pybuild:274: test: plugin custom failed with: exit code=1: 
python2.7 
/home/lamby/temp/cdt.20160128164608.xbU26qfoyC/python-markdown-2.6.5/run-tests.py
 --verbose
  dh_auto_test: pybuild --test --test-nose -i python{version} -p 2.7 --dir . 
returned exit code 13
  debian/rules:15: recipe for target 'override_dh_auto_test' failed
  make[1]: *** [override_dh_auto_test] Error 25
  make[1]: Leaving directory 
'/home/lamby/temp/cdt.20160128164608.xbU26qfoyC/python-markdown-2.6.5'
  debian/rules:8: recipe for target 'build' failed
  make: *** [build] Error 2

  

Bug#812860: /usr/bin/uscan: [uscan] failure to download and verify package.tar.xz with package.sign

[Osamu Aoki]

Hi,

On Wed, Jan 27, 2016 at 11:36:52AM +0100, Uwe Kleine-König wrote:
> Package: devscripts
> Version: 2.15.10
> Severity: normal
> File: /usr/bin/uscan
> Control: user adn+...@diwi.org
> Control: usertag -1 + uscan
> 
> Hello,
> 
> I started experimenting with uscan's pgp mechanism to verfiy the
> signature of rt-tests. You can reproduce my tests using:
> 
>   debcheckout rt-tests
>   cd rt-tests
>   echo  > debian/watch 'version=4'
>   echo >> debian/watch
>   echo >> debian/watch 'opts="pgpsigurlmangle=s%.xz$%.sign%, decompress" 
> \'
>   echo >> debian/watch 
> 'http://www.kernel.org/pub/linux/utils/rt-tests/rt-tests-(.*)\.tar\.xz'
... 
> where the problem seems to be that uscan decompresses the archive but in
> the same go removes the tar.xz for mk-origtargz.
> 
> Without decompress in the options the signature verification obviously
> fails.

You are right.  uscan should keep the compressed file when decompressing
it for the signature verification.

> Is this just me using uscan in a wrong way, or is there something fishy
> with uscan? In the first case an example would be great.

No it is uscan problem I created.

Osamu

Bug#813030: zipl-installer: remove obsolete portname

[Hendrik Brueckner]

Package: zipl-installer
Version: 0.0.38
Severity: minor
Tags: d-i patch

Hi,

this a small patch to remove the portname attribute.  The attribute
is obsolete and cannot be changed anymore.  Further it will be removed
in a future kernel version.

See also the attached patch.


Thanks and kind regards,
  Hendrik
>From 912031a56bb9271a0e8b4bbb90118bb6ae7fc72e Mon Sep 17 00:00:00 2001
From: Hendrik Brueckner 
Date: Fri, 20 Nov 2015 11:09:23 +0100
Subject: [PATCH 1/4] qeth: remove portname

The portname attribute is no longer necessary and will be removed soon.
See also upstream kernel commit:

commit 239ff408ddd8fa7a19c53ed247daec855ff11ea2
Author: Ursula Braun 
Date:   Fri Sep 18 16:06:50 2015 +0200

qeth: move OSA portname into deprecated status

An OSA-Express port name was required to identify a shared OSA port.
All operating system instances that shared the port had to use the
same port name. This requirement no longer applies.

Signed-off-by: Ursula Braun 
Signed-off-by: David S. Miller 

Signed-off-by: Hendrik Brueckner 
---
 debian/po/templates.pot | 17 -
 debian/s390-netdevice.templates | 15 ---
 netdevice.c | 28 
 3 files changed, 4 insertions(+), 56 deletions(-)

diff --git a/debian/po/templates.pot b/debian/po/templates.pot
index f6bae74..dabf4e2 100644
--- a/debian/po/templates.pot
+++ b/debian/po/templates.pot
@@ -166,7 +166,6 @@ msgid ""
 "The configured parameters are:\n"
 " channels = ${device0}, ${device1}, ${device2}\n"
 " port = ${port}\n"
-" portname = ${portname}\n"
 " layer2   = ${layer2}"
 msgstr ""
 
@@ -190,22 +189,6 @@ msgstr ""
 #. Description
 #. :sl5:
 #: ../s390-netdevice.templates:10001
-msgid "Portname:"
-msgstr ""
-
-#. Type: string
-#. Description
-#. :sl5:
-#: ../s390-netdevice.templates:10001
-msgid ""
-"Please enter the portname of your OSA-Express card. This name must be 1 to 8 "
-"characters long and must be equal on all systems accessing the same card."
-msgstr ""
-
-#. Type: string
-#. Description
-#. :sl5:
-#: ../s390-netdevice.templates:10001
 msgid ""
 "Leave it empty if you want to use HiperSockets. This parameter is required "
 "for cards with microcode level 2.10 or later or when you want to share a "
diff --git a/debian/s390-netdevice.templates b/debian/s390-netdevice.templates
index aa641f2..39fc0b7 100644
--- a/debian/s390-netdevice.templates
+++ b/debian/s390-netdevice.templates
@@ -64,7 +64,6 @@ _Description: Do you accept this configuration?
  The configured parameters are:
   channels = ${device0}, ${device1}, ${device2}
   port = ${port}
-  portname = ${portname}
   layer2   = ${layer2}
 
 Template: s390-netdevice/qeth/no
@@ -74,20 +73,6 @@ _Description: No OSA-Express QDIO cards / HiperSockets
  No OSA-Express QDIO cards / HiperSockets were detected. If you are running
  VM please make sure that your card is attached to this guest.
 
-Template: s390-netdevice/qeth/portname
-Type: string
-# :sl5:
-_Description: Portname:
- Please enter the portname of your OSA-Express card. This name must be 1 to
- 8 characters long and must be equal on all systems accessing the same
- card.
- .
- Leave it empty if you want to use HiperSockets. This parameter is
- required for cards with microcode level 2.10 or later or when you want to
- share a card.
- .
- The name will automatically be converted to uppercase.
-
 Template: s390-netdevice/qeth/port
 Type: string
 Default: 0
diff --git a/netdevice.c b/netdevice.c
index a4e1aea..6ddece9 100644
--- a/netdevice.c
+++ b/netdevice.c
@@ -60,7 +60,6 @@ struct device
struct channel *channels[3];
bool layer2;
int port;
-   char portname[32];
} qeth;
struct
{
@@ -109,7 +108,6 @@ enum state
GET_QETH_DEVICE,
GET_QETH_LAYER2,
GET_QETH_PORT,
-   GET_QETH_PORTNAME,
GET_IUCV_DEVICE,
GET_IUCV_PEER,
CONFIRM_CTC,
@@ -479,27 +477,13 @@ static enum state_wanted get_qeth_port (void)
return WANT_NEXT;
 }
 
-static enum state_wanted get_qeth_portname_iucv_peer (enum state state)
+static enum state_wanted get_iucv_peer (void)
 {
-   const char *template = NULL;
char *ptr, *tmp;
int ret, i, j;
 
-   switch (state)
-   {
-   case GET_QETH_PORTNAME:
-   template = TEMPLATE_PREFIX "qeth/portname";
-   tmp = device_current->qeth.portname;
-   break;
-   case GET_IUCV_PEER:
-   template = TEMPLATE_PREFIX "iucv/peer";
-   tmp = device_current->iucv.peername;
-   break;
-   default:
-   return WANT_ERROR;
-   }

Bug#437407: closed by Arturo Borrero Gonzalez <arturo.borrero.g...@gmail.com> ()

[積丹尼 Dan Jacobson]

> "B" == Debian Bug Tracking System  writes:

B> I don't understand this bug report.

B> The iptables package doesn't ship any file under /etc (at least, recently)

B> Closing this bug now.

# ls -l /etc/default/iptables
-rw-r--r-- 1 root root 3274 2002-09-20  /etc/default/iptables
# head /etc/default/iptables
# /etc/init.d/iptables defaults file

# INTRODUCTION: First thing first, I must warn you. The iptables
# init.d setup and iptables tools themselves are VERY much capable
# of locking you out of network services. This includes remote and
# grep ^\\w /etc/default/iptables
enable_ipv6=false
enable_autosave=false
enable_save_counters=true
# rm /etc/default/iptables

Bug#807190: closed by Andrei Zavada <johnhom...@gmail.com> (Bug#807190: fixed in cnrun 2.0.3-1)

[andrei zavada]

Mattia (cc Yaroslav):

Yaroslav does the uploads for me, actually, so I believe he could be
of some help here. Honestly, I only know my part in the process, and
that is to add a changelog entry, mark it 'experimental', run debuild
and hand the dsc over to my trusty sponsor Yaroslav.

As for the repo, upstream is pushing to both
cnrun.alioth.debian.org/~hmmr-guest/public_git/cnrun.git and
git.debian.org/git/debian-med/cnrun.git. The Vsc-Git tag in
debian/control points to git://anonscm.debian.org/cnrun/cnrun.git. Is
the suggestion to remove cnrun from debian-med?

Cheers,
Andrei


On 28 January 2016 at 16:26, Mattia Rizzolo  wrote:
> Dear maintainer,
>
> On Tue, Jan 12, 2016 at 09:51:54PM +, Debian Bug Tracking System wrote:
>>  cnrun (2.0.3-1) experimental; urgency=low
>>  .
>>* Build with gsl-2.0 (Closes: #807190).
>>* New upstream version (skipping the buggy 2.0.2).
>
>
> This needs to be fixed also for unstable, where the actual development
> happens, so the transition can eventually end.
> Can you please either upload this to unstable or update the unstable
> version to change the build-dependency?
>
> I'm also happy to do an NMU if you feel you don't have time to do this.
>
>
> BTW, can I ask why the git repository of this package is under the
> debian-med namesapce whilst this package is not team maintained?
>
> --
> regards,
> Mattia Rizzolo
>
> GPG Key: 66AE 2B4A FCCF 3F52 DA18  4D18 4B04 3FCD B944 4540  .''`.
> more about me:  http://mapreri.org  : :'  :
> Launchpad user: https://launchpad.net/~mapreri  `. `'`
> Debian QA page: https://qa.debian.org/developer.php?login=mattia  `-

Bug#812992: claws-mail: Sorting by date in "threaded view" does not work, probably bug #3407

[Florian Zieboll]

On Thu, 28 Jan 2016 16:40:47 +0100
Ricardo Mones  wrote:

> It is. 

Yes, it works :) 
Exact patch is attached.
2812c2812
< 		 sort_by[SORT_BY_DATE])) {
---
> 		 sort_by[SORT_BY_DATE] && type == S_COL_DATE)) {


pgpP68qVyOzO8.pgp
Description: OpenPGP digital signature

Bug#623865: iptables may want to modprobe; should have a dependency

[Arturo Borrero Gonzalez]

Control: tags -1 pending

Hi,

the next upload will contain kmod as Suggests.

best regards.

-- 
Arturo Borrero González

Bug#812708: Similar issue with "GTE CyberTrust Global Root"

[Peter Dahlberg]

Hi,

There seems to be a similar looking issue because of the removed "GTE 
CyberTrust Global Root".

jessie:

$ openssl s_client -connect pictureis24-a.akamaihd.net:443
CONNECTED(0003)
depth=2 C = IE, O = Baltimore, OU = CyberTrust, CN = Baltimore CyberTrust Root
verify error:num=20:unable to get local issuer certificate
verify return:0
---
Certificate chain
 0 s:/C=US/ST=MA/L=Cambridge/O=Akamai Technologies Inc./CN=a248.e.akamai.net
   i:/C=NL/L=Amsterdam/O=Verizon Enterprise Solutions/OU=Cybertrust/CN=Verizon 
Akamai SureServer CA G14-SHA2
 1 s:/C=NL/L=Amsterdam/O=Verizon Enterprise Solutions/OU=Cybertrust/CN=Verizon 
Akamai SureServer CA G14-SHA2
   i:/C=IE/O=Baltimore/OU=CyberTrust/CN=Baltimore CyberTrust Root
 2 s:/C=IE/O=Baltimore/OU=CyberTrust/CN=Baltimore CyberTrust Root
   i:/C=US/O=GTE Corporation/OU=GTE CyberTrust Solutions, Inc./CN=GTE 
CyberTrust Global Root
---

testing:

 % openssl s_client -connect pictureis24-a.akamaihd.net:443
CONNECTED(0003)
depth=2 C = IE, O = Baltimore, OU = CyberTrust, CN = Baltimore CyberTrust Root
verify return:1
depth=1 C = NL, L = Amsterdam, O = Verizon Enterprise Solutions, OU = 
Cybertrust, CN = Verizon Akamai SureServer CA G14-SHA2
verify return:1
depth=0 C = US, ST = MA, L = Cambridge, O = Akamai Technologies Inc., CN = 
a248.e.akamai.net
verify return:1
---
Certificate chain
 0 s:/C=US/ST=MA/L=Cambridge/O=Akamai Technologies Inc./CN=a248.e.akamai.net
   i:/C=NL/L=Amsterdam/O=Verizon Enterprise Solutions/OU=Cybertrust/CN=Verizon 
Akamai SureServer CA G14-SHA2
 1 s:/C=NL/L=Amsterdam/O=Verizon Enterprise Solutions/OU=Cybertrust/CN=Verizon 
Akamai SureServer CA G14-SHA2
   i:/C=IE/O=Baltimore/OU=CyberTrust/CN=Baltimore CyberTrust Root
 2 s:/C=IE/O=Baltimore/OU=CyberTrust/CN=Baltimore CyberTrust Root
   i:/C=US/O=GTE Corporation/OU=GTE CyberTrust Solutions, Inc./CN=GTE 
CyberTrust Global Root
---

Kind regards,
Peter

Bug#813020: please multiarchify the library packages

[Thomas Schmitt]

Hi,

i am the Uploader who maintains the ./debian repository of
libburn, libisofs, and libisoburn (not the Maintainer who uploads).

When i took over, i asked for advise about "Multi-Arch:" and
"Pre-Depends:"
  https://lists.debian.org/debian-mentors/2015/09/msg00403.html

I got clear statements not to use them from Niels Thykier, Jakub Wilk,
and Santiago Vila:
  https://lists.debian.org/debian-mentors/2015/09/msg00408.html
  https://lists.debian.org/debian-mentors/2015/09/msg00409.html
  https://lists.debian.org/debian-mentors/2015/09/msg00416.html
Wookey had some mild scruples:
  https://lists.debian.org/debian-mentors/2015/09/msg00419.html

So we would have to discuss the topic again on debian-mentors
before i noob will override the opinion of the experts.


Have a nice day :)

Thomas

Bug#813014: ez-ipupdate: Missing package from mirrors

[Lorenzo Milesi]

Package: ez-ipupdate
Version: 3.0.11b8-13.3_mips
Severity: important


The package for mips arch is missing from all the mirrors


-- System Information:
Debian Release: 6.0.7
  APT prefers oldoldstable
  APT policy: (500, 'oldoldstable')
Architecture: mips (mips64)

Kernel: Linux 2.6.32.13-UBNT (SMP w/2 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=ANSI_X3.4-1968) 
(ignored: LC_ALL set to C)
Shell: /bin/sh linked to /bin/bash

Bug#807190: closed by Andrei Zavada <johnhom...@gmail.com> (Bug#807190: fixed in cnrun 2.0.3-1)

[Mattia Rizzolo]

Dear maintainer,

On Tue, Jan 12, 2016 at 09:51:54PM +, Debian Bug Tracking System wrote:
>  cnrun (2.0.3-1) experimental; urgency=low
>  .
>* Build with gsl-2.0 (Closes: #807190).
>* New upstream version (skipping the buggy 2.0.2).


This needs to be fixed also for unstable, where the actual development
happens, so the transition can eventually end.
Can you please either upload this to unstable or update the unstable
version to change the build-dependency?

I'm also happy to do an NMU if you feel you don't have time to do this.


BTW, can I ask why the git repository of this package is under the
debian-med namesapce whilst this package is not team maintained?

-- 
regards,
Mattia Rizzolo

GPG Key: 66AE 2B4A FCCF 3F52 DA18  4D18 4B04 3FCD B944 4540  .''`.
more about me:  http://mapreri.org  : :'  :
Launchpad user: https://launchpad.net/~mapreri  `. `'`
Debian QA page: https://qa.debian.org/developer.php?login=mattia  `-


signature.asc
Description: PGP signature

Bug#813010: caja: Shift-Del behaviour is wrong when renaming files

[John Paul Adrian Glaubitz]

On 01/28/2016 03:11 PM, Dark Penguin wrote:
> When renaming files in Caja, pressing Shift+Del does not "cut the name";
> instead, it works as if you wanted to "permanently delete" the file.
> Ctrl+X works as expected, however.

Meh, you people are really nitpicky. I would have expected that
Shift+Del will actually delete the file, not cut the text here.

> This buggy behaviour is present in Caja 1.8.2 in the current Jessie, but
> not in Caja 1.8.2 in LMDE2.

I think it's arguable whether this is a bug or not. But in any case,
this is up to the MATE upstream developers what the expected behavior
of Shift+Del is in this case.

In fact, you should not test any other Linux distribution, but download
caja in source from the upstream website, compile it yourself and test
how the vanilla version behaves.

If the upstream version behaves as the Debian package, it's an upstream
bug. If not, they probably changed behavior upstream and caja just
needs to be updated in Debian. I highly doubt that someone intentionally
changed this behavior in Debian.

Adrian

-- 
 .''`.  John Paul Adrian Glaubitz
: :' :  Debian Developer - glaub...@debian.org
`. `'   Freie Universitaet Berlin - glaub...@physik.fu-berlin.de
  `-GPG: 62FF 8A75 84E0 2956 9546  0006 7426 3B37 F5B5 F913

Bug#813034: manpage still mentions limit on console size

[Josh Triplett]

Package: conspy
Version: 1.13-1+b1
Severity: normal

The manpage still says: "Conspy does not handle displays larger than
16000 characters (eg 200 rows x 80 columns)."

But the conspy changelog indicates that conspy no longer has this
limitation.

-- System Information:
Debian Release: stretch/sid
  APT prefers unstable
  APT policy: (500, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.4.0-trunk-amd64 (SMP w/4 CPU cores)
Locale: LANG=C.UTF-8, LC_CTYPE=C.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Bug#755160: Segfault when starting new system instance in a systemd-nspawn environment

[Michael Biebl]

Hi Christoph

On Sat, 19 Jul 2014 00:03:23 +0200 Michael Biebl  wrote:
> Am 18.07.2014 13:56, schrieb Christoph Berg:
> > Package: systemd
> > Version: 204-14
> > Severity: normal
> > 
> > Hi,
> > 
> > my host system is jessie. In my sid-amd64 chroot which I entered using
> > systemd-nspawn, I tried to start a new systemd --system instance:
> > 
> > $ sudo systemd-nspawn -D /srv/src/chroot/sid-amd64
> > Spawning namespace container on /srv/src/chroot/sid-amd64 (console is 
> > /dev/pts/4).
> > Init process in the container running as PID 27787.
> > /etc/localtime is not a symlink, not updating container timezone.
> > 
> > (sid-amd64)root@sid-amd64:~# apt-get install systemd
> > [...]
> > Setting up libsystemd-daemon0:amd64 (208-6) ...
> > Setting up libsystemd-journal0:amd64 (208-6) ...
> > Setting up libsystemd-login0:amd64 (208-6) ...
> > Setting up acl (2.2.52-1) ...
> > Setting up libcap2-bin (1:2.22-2) ...
> > Setting up libdevmapper1.02.1:amd64 (2:1.02.85-2) ...
> > Setting up libcryptsetup4:amd64 (2:1.6.4-4) ...
> > Setting up systemd (208-6) ...
> 
> I wonder if this is related to the version mismatch, i.e. v204 vs v208.

I tried the other way around: host systemd is sid (v228), chroot is
jessie (v215).
I didn't experience any segfaults. Could you try if you can reproduce
the issue with current versions for systemd?

Regards,
Michael


-- 
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?



signature.asc
Description: OpenPGP digital signature

Bug#813037: flashcache: will not build against mainline 4.4 based kernels

[Andy Whitcroft]

Source: flashcache
Version: 3.1.3+git20150701-2
Severity: normal

Dear Maintainer,

The mainline 4.4 kernel removes the target specific ioctl hooks that the
flashcache implmentation uses to hold its pid white/black list
manipulation ioctls.  Upstream do not care about out of tree drivers and
therefore are not interested in reinstating this call.

In Ubuntu we are mitiating this via a kernel patch which introduces a
new target_ioctl and modifications to flashcache to use those.

This is as much as anything heads up about the issue.

-apw

-- System Information:
Debian Release: stretch/sid
  APT prefers xenial-updates
  APT policy: (500, 'xenial-updates'), (500, 'xenial-security'), (500, 
'xenial'), (100, 'xenial-backports')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.3.0-5-generic (SMP w/4 CPU cores)
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Bug#813026: Please upload 0.7.1 because is part of an important memory leak/crash bugfix

[Fabio Fantoni]

Source: usbredir
Severity: important

Please update packages to 0.7.1 (released 3 months ago) because is a 
part for fix an important bug:
https://bugzilla.redhat.com/show_bug.cgi?id=1264156 - big memory leak 
and crash when usb data transmission is higher that available network 
bandwidth.


Thanks for any reply and sorry for my bad english.

Bug#813032: RM: fonts-droid -- NBS; no longer included upstream

[Adam Borowski]

Package: ftp.debian.org
Severity: normal

Hi!
Please decruft fonts-droid [all], no longer built by src:fonts-android.
It has been dropped in 1:6.0.0r26-1.

Bug#813033: qeth: ask for relative OSA port number

[Hendrik Brueckner]

Package: s390-netdevice
Version: 0.0.38
Severity: important
Tags: d-i patch

Hi,

below is another patch for the s390-netdevice regarding qeth device
configuration.  Some cards require the specification of the relative
port number on the OSA card.   Ths s390-netdevice has template and
state information for this attribute but lacks the actual
implementation.

The attached patch will let the user specify the relative OSA port
number.  The setting can also be preseeded if necessary.


Thanks and kind regards,
  Hendrik
>From 439483cd533d865d96a8c8119b221e9a56f25925 Mon Sep 17 00:00:00 2001
From: Hendrik Brueckner 
Date: Fri, 20 Nov 2015 12:57:36 +0100
Subject: [PATCH 2/4] qeth: ask for the relative OSA port number

Let the user specify the port number because this is required for
particular OSA cards.

Reported-by: Elisabeth Puritscher 
Signed-off-by: Hendrik Brueckner 
---
 netdevice.c | 20 ++--
 1 file changed, 18 insertions(+), 2 deletions(-)

diff --git a/netdevice.c b/netdevice.c
index 6ddece9..6905c2d 100644
--- a/netdevice.c
+++ b/netdevice.c
@@ -638,6 +638,22 @@ static enum state_wanted write_sysfs (void)
syslog (LOG_ERR, "Can't write ccwgroup device attribute 
layer2");
return WANT_ERROR;
}
+
+   /* Set the relative port number.
+* Valid port numbers are 0 (default) or 1
+*/
+   if (device_current->qeth.port)
+   {
+   attr = sysfs_get_device_attr (device, "portno");
+   if (attr)
+   {
+   if (sysfs_write_attribute (attr, "1", 1) < 0)
+   {
+   syslog (LOG_ERR, "Could not write 
device attribute portno");
+   return WANT_ERROR;
+   }
+   }
+   }
}
 
attr = sysfs_get_device_attr (device, "online");
@@ -703,6 +719,7 @@ static enum state_wanted write_qeth (void)
 
if (device_current->qeth.layer2)
fprintf (config, "QETH_OPTIONS=(layer2)\n");
+   fprintf (config, "QETH_PORTNO=%d", device_current->qeth.port);
 
fclose (config);
 
@@ -837,8 +854,7 @@ int main (int argc __attribute__ ((unused)), char *argv[] 
__attribute__ ((unused
state = GET_QETH_LAYER2;
break;
case GET_QETH_LAYER2:
-   /* state = GET_QETH_PORT; */
-   state = CONFIRM_QETH;
+   state = GET_QETH_PORT;
break;
case GET_QETH_PORT:
state = CONFIRM_QETH;
-- 
2.7.0.rc3

Bug#812992: claws-mail: Sorting by date in "threaded view" does not work, probably bug #3407

[Ricardo Mones]

control: severity -1 normal
control: tags -1 jessie
control: fixed -1 3.12.0-1

Hi Florian,

On Thu, Jan 28, 2016 at 01:30:03PM +0100, Florian Zieboll wrote:
> Package: claws-mail
> Version: 3.11.1-3+deb8u1
> Severity: important
> 
> It seems that claws-mail bug #3407 is active in Debian Jessie (fixed 
> upstream):
> 
> http://lists.claws-mail.org/pipermail/users/2015-March/012588.html

It is. Thanks for reporting,
-- 
  Ricardo Mones 
  ~
  The world will end in 5 minutes. Please log out.Unknown



signature.asc
Description: Digital signature

Bug#810324: Hint chevrons are actionable

[Christophe Siraut]

control: tags -1 patch

Here is a patch for indicating chevrons are actionable, using a pointing
hand cursor and coloring chevrons in blue.

Cheers,
Christophe
>From 9e66996255322ff12abef1d30fd404e5c4731c32 Mon Sep 17 00:00:00 2001
From: Christophe Siraut 
Date: Thu, 28 Jan 2016 16:24:36 +0100
Subject: [PATCH] css: hint chevrons are actionable (closes #810324)

---
 distro_tracker/core/static/css/style.css | 7 +++
 distro_tracker/core/templates/core/panels/action-needed.html | 2 +-
 2 files changed, 8 insertions(+), 1 deletion(-)

diff --git a/distro_tracker/core/static/css/style.css b/distro_tracker/core/static/css/style.css
index 7087910..7405a77 100644
--- a/distro_tracker/core/static/css/style.css
+++ b/distro_tracker/core/static/css/style.css
@@ -289,3 +289,10 @@ ul.inline > li {
 label {
   cursor: pointer;
 }
+
+.chevron {
+  padding-left: 5px;
+  padding-right: 5px;
+  cursor: pointer;
+  color: #0275D8;
+}
diff --git a/distro_tracker/core/templates/core/panels/action-needed.html b/distro_tracker/core/templates/core/panels/action-needed.html
index 6bdb100..427d648 100644
--- a/distro_tracker/core/templates/core/panels/action-needed.html
+++ b/distro_tracker/core/templates/core/panels/action-needed.html
@@ -9,7 +9,7 @@
 	
 		
 	
-- 
2.7.0.rc3

Bug#813010: caja: Shift-Del behaviour is wrong when renaming files

[Dark Penguin]

And, no, it's not only up to the developers to figure what causes the
bug. Both Mate and Debian are community-driven, so if you find a bug
you would like to get fixed as a user, you should help developers
with some testing which helps locate the issue.

The more information you provide, the faster can others fix your
problem. Remember, many people here don't get paid for fixing these
things, so they might as well say that they don't care about a bug if
it takes too much effort to debug and fix it.


Yes, I know; and I absolutely agree - when reporting a bug, I make sure 
to test everything I can think of that I would do if I was the project 
developer. Actually, I like fixing UI problems myself, and I would do it 
if I could, but I'm not yet good enough to deal with things like this...


What I meant is, "it's there in Debian, it's not there in Mint; the only 
people who can find out exactly where it all went wrong is the Debian 
people". Also, the bug report page for Debian said something like, "if 
you're unsure, don't send the report upstream; maybe it's only there in 
Debian - we'll direct it upstream if we have to".



> Could you please test caja upstream and report back? Linux Mint is
> not upstream, the MATE project is.
>
> And if it turns out that the bug is still present upstream, then
> you're barking up the wrong tree as Debian just packages most
> upstream software, we don't develop it.
>
> Also, if turns out to be an upstream bug, then you should yell at the
> Linux Mint people to fix it.

I'm extremely sorry, but it seems that I've provided some wrong 
information. I've just tested it again. The bug IS there in Linux Mint 
Debian Edition 2; however, it is NOT there in Linux Mint 17.3 . (I mixed 
up different Mint distros.) So the problem is upstream, anyway, and it's 
not with Caja - it's with something else that's different between Debian 
and Ubuntu.



--
darkpenguin

Bug#802545: systemd: postinst may not have run correctly on upgrades from jessie

[Michael Biebl]

Hi Andreas

On Wed, 21 Oct 2015 00:05:37 +0200 Andreas Beckmann  wrote:

> # error while comparing the chroots (after removing the package to be tested 
> + dependencies)
> 1m19.7s ERROR: FAIL: After purging files have disappeared:
>   /etc/dbus-1/system.d/org.freedesktop.machine1.conf.dpkg-remove   not 
> owned
>   /etc/systemd/system/halt.target.wants/   not owned
>   /etc/systemd/system/halt.target.wants/hwclock-save.service -> 
> /lib/systemd/system/hwclock-save.service   not owned
>   /etc/systemd/system/poweroff.target.wants/   not owned
>   /etc/systemd/system/poweroff.target.wants/hwclock-save.service -> 
> /lib/systemd/system/hwclock-save.service   not owned
>   /etc/systemd/system/reboot.target.wants/ not owned

Could you re-run the tests with an up-to-date testing?
I wonder whether we actually need the versioned Depends on dpkg or if
the upgrade from jesse -> stretch is actually fine now.

So all we would need to do is to cleanup the state for our
testing/unstable users.

The attached patch should be sufficient I guess.

Regards,
Michael

-- 
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?
diff --git a/debian/systemd.maintscript b/debian/systemd.maintscript
index 44697bd..ddb96ae 100644
--- a/debian/systemd.maintscript
+++ b/debian/systemd.maintscript
@@ -2,5 +2,5 @@ rm_conffile /etc/bash_completion.d/systemctl-bash-completion.sh 204-1~
 rm_conffile /etc/bash_completion.d/systemd-bash-completion.sh 204-1~
 mv_conffile /etc/systemd/systemd-logind.conf /etc/systemd/logind.conf 204-1~
 mv_conffile /etc/systemd/systemd-journald.conf /etc/systemd/journald.conf 204-1~
-rm_conffile /etc/dbus-1/system.d/org.freedesktop.machine1.conf 224-2~
+rm_conffile /etc/dbus-1/system.d/org.freedesktop.machine1.conf 228-5~
 rm_conffile /etc/X11/xinit/xinitrc.d/50-systemd-user.sh 228-3~
diff --git a/debian/systemd.postinst b/debian/systemd.postinst
index 8d1f106..ab48565 100644
--- a/debian/systemd.postinst
+++ b/debian/systemd.postinst
@@ -141,7 +141,7 @@ if [ -n "$2" ]; then
 fi
 
 # Cleanup hwclock-save.service, which was shipped in jessie.
-if dpkg --compare-versions "$2" lt-nl "219-8"; then
+if dpkg --compare-versions "$2" lt-nl "228-5~"; then
for t in reboot halt poweroff ; do
rm -f /etc/systemd/system/${t}.target.wants/hwclock-save.service
rmdir --ignore-fail-on-non-empty /etc/systemd/system/${t}.target.wants 2> /dev/null || true


signature.asc
Description: OpenPGP digital signature

Bug#810814: libgnutls26: Encrypted LDAP connection doesn't work after libgnutls26 update

[Wolfgang Karall-Ahlborn]

Package: libgnutls26
Followup-For: Bug #810814

Hi,

I can confirm that the addition of 'SECURE256' in the cipher suites
configuration seems to be the problem, switching from

olcTLSCipherSuite: SECURE256:!ARCFOUR-128:!3DES-CBC:-VERS-SSL3.0

to

olcTLSCipherSuite: NORMAL:!ARCFOUR-128:!3DES-CBC:-VERS-SSL3.0

worked for me, but is of course not ideal.

Debugging with gnutls-cli yields the same results as in the related
Ubuntu bug report

https://bugs.launchpad.net/ubuntu/+source/gnutls26/+bug/1534230

i.e. 'SECURE256' doesn't work, while 'SECURE256:+SIGN-ALL' does work
with gnutls-cli (but unfortunately the +SIGN-ALL doesn't help when
configuring slapd's olcTLSCipherSuite).

Cheers
Wolfgang

-- System Information:
Debian Release: stretch/sid
  APT prefers unstable
  APT policy: (500, 'unstable')
Architecture: i386 (i686)

Kernel: Linux 4.2.0-1-686-pae (SMP w/4 CPU cores)
Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash
Init: sysvinit (via /sbin/init)

Versions of packages libgnutls26 depends on:
ii  libc6  2.19-22
pn  libgcrypt11
ii  libp11-kit00.23.1-3
ii  libtasn1-6 4.7-2
ii  multiarch-support  2.19-22
ii  zlib1g 1:1.2.8.dfsg-2+b1

libgnutls26 recommends no packages.

libgnutls26 suggests no packages.

Bug#802888: Same issue in upstream bugtracker

[Benoit Friry]

Same issue in upstream bugtracker:
https://github.com/balabit/syslog-ng/issues/121

Bug#803531: systemd: timeout mounting /home (btrfs) at boot

[Michael Biebl]

Hi Brian

Am 22.01.2016 um 04:52 schrieb Brian May:
> Brian May  writes:
> 
>> Oh, except I note that you used /dev/sdb1 and/dev/sdb2 on the same
>> harddisk. I used seperate harddisks for both. Wonder if that matters?
> 
> I had a look again at reproducing this on a KVM, in Debian testing. I
> used separate harddisks for both. However, unable to see any problems.

Is this still reproducible with (systemd v215 from) jessie?

Should we close the bug report until/unless we have a proper way to
reprodce the issue?


-- 
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#785149: grub-installer: NVMe boot drives not supported

[Lennart Sorensen]

On Wed, Jan 27, 2016 at 09:52:51PM -0500, Z G wrote:
> Following up on Jeremy's question above, does Debian 8.3.0 (image as of
> early 2016) include a fix?
> 
> Alternatively, could someone (Matteo?) indicate the steps to fix this
> during the install process? Not sure if you're patching the installer code
> and recompiling during the install process or something else.

I tried with the stretch installer in late December, and that worked
on NVMe (which is good since this was a few weeks after it was supposed
to have been fixed).  I tested on a Samsung 950 Pro 256GB M.2 on an
Asus Z170-A.

It did not occur to me to test the jessie installer since I simply
assumed it didn't do NVMe.  Also I was under the impression that there
are issues with the graphics in the skylake CPUs that needed a 4.3+
kernel, which ruled out Jessie for that machine.

According to
http://www.poweredbyjeff.com/2015/10/29/Intel-750-SSD-in-Debian-Jessie/ it
needs a backported grub and kernel to work properly in Jessie.  Not sure.
It does have steps that is says works.

Of course if the kernel has some issues with NVMe, then I suspect getting
jessie fixed isn't that likely, but at least backports for the kernel
is still an option then.

-- 
Len Sorensen

Bug#813023: flash-kernel: quoting error with bootargs in generic U-Boot boot script

[Jérémy Bobbio]

Package: flash-kernel
Version: 3.56
Tag: patch

Hi!

There's a small quoting mistake in the generic U-Boot script. It
probably hasn't been noticed so far because the default
LINUX_KERNEL_CMDLINE doesn't contain spaces. See the attached patch.

While, I am at it, I wonder if it would not make more sense to
reverse the order when setting that variable so it reads:

setenv bootargs "@@LINUX_KERNEL_CMDLINE@@ ${bootargs}"

That way, it's possible to override the default command line by doing
something like:

setenv bootargs console=ttyAMA0,115200
boot

-- 
Lunar.''`. 
lu...@debian.org: :Ⓐ  :  # apt-get install anarchism
`. `'` 
  `-   
From 8d87ea9e4adcc48e4bffa0ff3a378fc3e417afe4 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?J=C3=A9r=C3=A9my=20Bobbio?= 
Date: Thu, 28 Jan 2016 16:14:28 +0100
Subject: [PATCH] Properly quote LINUX_KERNEL_CMDLINE in U-Boot generic boot
 script

Otherwise we get an error as soon as LINUX_KERNEL_CMDLINE contains spaces.
---
 bootscript/all/bootscr.uboot-generic | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/bootscript/all/bootscr.uboot-generic b/bootscript/all/bootscr.uboot-generic
index c318be5..1c3f129 100644
--- a/bootscript/all/bootscr.uboot-generic
+++ b/bootscript/all/bootscr.uboot-generic
@@ -25,7 +25,7 @@ if test -n "${console}"; then
   setenv bootargs "${bootargs} console=${console}"
 fi
 
-setenv bootargs ${bootargs} @@LINUX_KERNEL_CMDLINE@@
+setenv bootargs "${bootargs} @@LINUX_KERNEL_CMDLINE@@"
 @@UBOOT_ENV_EXTRA@@
 
 if test -z "${fk_kvers}"; then
-- 
2.1.4



signature.asc
Description: Digital signature

Bug#813010: caja: Shift-Del behaviour is wrong when renaming files

[John Paul Adrian Glaubitz]

> It may be that Mint "fixed" this already, but I think it's been more than a 
> year already - why is it still not in Debian?! So I think it's a problem with 
> something other than Caja itself - some Debian-specific hotkey-snatching 
> subsystems or something. Maybe this problem was never even there in Mint. 
> Either way, it's up to the developers to find out why is there a problem with 
> Debian, but not with Mint.

Could you please test caja upstream and report back? Linux Mint is not 
upstream, the MATE project is.

And if it turns out that the bug is still present upstream, then you're barking 
up the wrong tree as Debian just packages most upstream software, we don't 
develop it.

Also, if turns out to be an upstream bug, then you should yell at the Linux 
Mint people to fix it.

And, no, it's not only up to the developers to figure what causes the bug. Both 
Mate and Debian are community-driven, so if you find a bug you would like to 
get fixed as a user, you should help developers with some testing which helps 
locate the issue.

The more information you provide, the faster can others fix your problem. 
Remember, many people here don't get paid for fixing these things, so they 
might as well say that they don't care about a bug if it takes too much effort 
to debug and fix it.

Adrian

Bug#813018: please multiarchify the library packages

[Matthias Klose]

On 28.01.2016 16:12, Michael Biebl wrote:

Control: tags -1 = moreinfo

Am 28.01.2016 um 15:44 schrieb Matthias Klose:

Package: src:totem
Version: 3.16.1-1
Tags: patch
User: d...@debian.org
Usertags: multiarch

patch at
http://launchpadlibrarian.net/235558205/totem_3.18.1-1ubuntu2_3.18.1-1ubuntu3.diff.gz


+# don't configure with --libdir, but move the files manually, because
+# other locations in /usr/lib/ must not change.
+common-install-impl::
+   mkdir -p debian/tmp/usr/lib/$(DEB_HOST_MULTIARCH)
+   mv debian/tmp/usr/lib/*.a debian/tmp/usr/lib/*.so* \
+   debian/tmp/usr/lib/girepository-1.0 debian/tmp/usr/lib/pkgconfig \
+   debian/tmp/usr/lib/$(DEB_HOST_MULTIARCH)
+

I assume you are concerned that there are other packages installing
plugins into /usr/lib/totem/plugins?


yes.


If so, I think the right fix here is, to use
--libdir=usr/lib/$(DEB_HOST_MULTIARCH) and patch totem to look at old
and new path.


sure you can do that, but this doesn't affect the multiarch status of the 
library packages.  I'm not aware that you would need the plugin packages for 
e.g. cross-building.

Bug#813018: please multiarchify the library packages

[Michael Biebl]

Control: tags -1 = moreinfo

Am 28.01.2016 um 15:44 schrieb Matthias Klose:
> Package: src:totem
> Version: 3.16.1-1
> Tags: patch
> User: d...@debian.org
> Usertags: multiarch
> 
> patch at
> http://launchpadlibrarian.net/235558205/totem_3.18.1-1ubuntu2_3.18.1-1ubuntu3.diff.gz

+# don't configure with --libdir, but move the files manually, because
+# other locations in /usr/lib/ must not change.
+common-install-impl::
+   mkdir -p debian/tmp/usr/lib/$(DEB_HOST_MULTIARCH)
+   mv debian/tmp/usr/lib/*.a debian/tmp/usr/lib/*.so* \
+   debian/tmp/usr/lib/girepository-1.0 debian/tmp/usr/lib/pkgconfig \
+   debian/tmp/usr/lib/$(DEB_HOST_MULTIARCH)
+

I assume you are concerned that there are other packages installing
plugins into /usr/lib/totem/plugins?
If so, I think the right fix here is, to use
--libdir=usr/lib/$(DEB_HOST_MULTIARCH) and patch totem to look at old
and new path.

Michael

-- 
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?



signature.asc
Description: OpenPGP digital signature

Bug#813029: hplip: Can't apt-get install hplip because of python<3.5 dependance

[Édouard Gilbert]

Package: hplip
Severity: important

Dear Maintainer,

*** Reporter, please consider answering these questions, where appropriate ***

   * What led up to the situation?

Trying to install the hplip tools with apt-get install hplip.

   * What exactly did you do (or not do) that was effective (or
 ineffective)?

apt-get update, upgrade, dist-upgrade

   * What was the outcome of this action?

I have an up-to-date system.

   * What outcome did you expect instead?

Successful instllation of hplip at one point or another.



-- System Information:
Distributor ID: Raspbian
Description:Raspbian GNU/Linux testing (stretch)
Release:testing
Codename:   stretch
Architecture: armv6l

Kernel: Linux 4.1.16+
Locale: LANG=, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages hplip depends on:
ii  adduser3.113+nmu3
ii  coreutils  8.23-4
ii  cups   2.1.2-2
pn  hplip-data 
ii  libc6  2.21-6
ii  libcups2   2.1.2-2
ii  libdbus-1-31.10.6-1
ii  libhpmud0  3.15.11+repack0-1
ii  libsane1.0.25-2
pn  libsane-hpaio  
ii  libsnmp30  5.7.3+dfsg-1+b2
ii  libssl1.0.01.0.1k-3+deb8u2
ii  libusb-1.0-0   2:1.0.20-1
ii  lsb-base   9.20160110+rpi1
ii  policykit-10.105-14.1
ii  printer-driver-hpcups  3.15.11+repack0-1
ii  python 2.7.11-1
pn  python-dbus
ii  python-gobject-2   2.28.6-12
pn  python-imaging 
pn  python-pexpect 
pn  python-reportlab   
ii  wget   1.17.1-1

Versions of packages hplip recommends:
ii  avahi-daemon  0.6.32~rc+dfsg-1
pn  printer-driver-postscript-hp  
ii  sane-utils1.0.25-2

Versions of packages hplip suggests:
pn  hplip-doc  
pn  hplip-gui  
pn  python-notify  
pn  system-config-printer  

Bug#813015: mlpy: FTBFS: error: unbalanced parenthesis

[Mattia Rizzolo]

Source: mlpy
Version: 2.2.0~dfsg1-3
Severity: serious


Dear maintainer,

you package currently fails to build from source:

PYTHONPATH=/build/mlpy-2.2.0~dfsg1/build/lib.linux-x86_64-2.7 /usr/bin/make -C 
docs html latex
make[1]: Entering directory '/build/mlpy-2.2.0~dfsg1/docs'
mkdir -p build/html build/doctrees
sphinx-build -b html -d build/doctrees   source build/html
Running Sphinx v1.3.4
loading pickled environment... not yet created
building [mo]: targets for 0 po files that are out of date
building [html]: targets for 17 source files that are out of date
updating environment: 17 added, 0 changed, 0 removed
reading sources... [  5%] classification
reading sources... [ 11%] clustering

Exception occurred:
  File "/usr/lib/python2.7/re.py", line 251, in _compile
raise error, v # invalid expression
error: unbalanced parenthesis
The full traceback has been saved in /tmp/sphinx-err-9SC3Xq.log, if you want to 
report the issue to the developers.
Please also report this if it was a user error, so that a better error message 
can be provided next time.
A bug report can be filed in the tracker at 
. Thanks!
Makefile:29: recipe for target 'html' failed
make[1]: *** [html] Error 1
make[1]: Leaving directory '/build/mlpy-2.2.0~dfsg1/docs'
debian/rules:18: recipe for target 'doc-stamp' failed
make: *** [doc-stamp] Error 2
dpkg-buildpackage: error: debian/rules build gave error exit status 2

-- 
regards,
Mattia Rizzolo

GPG Key: 66AE 2B4A FCCF 3F52 DA18  4D18 4B04 3FCD B944 4540  .''`.
more about me:  http://mapreri.org  : :'  :
Launchpad user: https://launchpad.net/~mapreri  `. `'`
Debian QA page: https://qa.debian.org/developer.php?login=mattia  `-


signature.asc
Description: PGP signature

Bug#812663: debian-policy: FTBFS - nsgmls: Command not found

[Bill Allombert]

On Mon, Jan 25, 2016 at 09:17:40PM +0100, Bill Allombert wrote:
> On Mon, Jan 25, 2016 at 07:00:51PM +, Michael Tautschnig wrote:
> > Package: debian-policy
> > Version: 3.9.6.1
> > Severity: serious
> > Usertags: goto-cc
> > 
> > During a rebuild of all Debian packages in a clean sid chroot (using 
> > cowbuilder
> > and pbuilder) the build failed with the following error.
> > 
> > [...]
> > make[1]: Entering directory 
> > '/srv/jenkins-slave/workspace/sid-goto-cc-debian-policy/debian-policy-3.9.6.1'
> > nsgmls -wall -gues policy.sgml
> > make[1]: nsgmls: Command not found
> > Makefile:17: recipe for target 'policy.sgml.validate' failed
> > make[1]: *** [policy.sgml.validate] Error 127
> > 
> > 
> > The full build log is attached; please do let me know if the problem is
> > unreproducible, in which case I shall try to investigate further.
> 
> No, I can reproduce it by uninstalling sp.
> 
> There is two issues:
> - First debian-policy should build-depends directy on sp since the main
>   Makefile call nsgmls
> - Second it might be a good time to migrate to openjade and opensp.

I have applied change 8923e88 that does that. I will upload soon.

Cheers,
-- 
Bill. 

Imagine a large red swirl here. 

Bug#813011: please multiarchify the library packages

[Matthias Klose]

Package: src:libgnomekbd
Version: 3.6.0-1
Tags: patch
User: d...@debian.org
Usertags: multiarch

patch at
http://launchpadlibrarian.net/235553111/libgnomekbd_3.6.0-1ubuntu1_3.6.0-1ubuntu2.diff.gz

Bug#813007: Fix container detection (running-in-container is an Ubuntu-ism)

[Martin Pitt]

Hey Ian,

Ian Campbell [2016-01-28 16:38 +]:
> Will it always be installed or is a Depends needed?

ATM you can change installs to remove systemd, and on some arches
(Hurd, BSD) the systemd package isn't even available (on those it
doesn't matter though, as there are no containers either). The patch
should be robust against systemd-detect-virt not existing.

That said, systemd is part of debootstrap and installed on almost all
machines and containers these days. So this patch changes it from
"container detection is broken everywhere because running-in-container
does not exist anywhere" to "it works in most environments except
where you try hard to get rid of it".

Martin
-- 
Martin Pitt| http://www.piware.de
Ubuntu Developer (www.ubuntu.com)  | Debian Developer  (www.debian.org)

Bug#813042: libopenmpi1.10: file conflict with libopenmpi1.6

[Ralf Treinen]

Here is a list of files that are known to be shared by both packages
(according to the Contents file for sid/amd64, which may be
slightly out of sync):

  /usr/lib/libmpi_cxx.so.1
  /usr/lib/libmpi_f77.so.1
  /usr/lib/libmpi_f77.so.1.0.7
  /usr/lib/libmpi_f90.so.1
  /usr/lib/libmpi_f90.so.1.3.0
  /usr/lib/libompitrace.so.0
  /usr/lib/libompitrace.so.0.0.0
  /usr/lib/openmpi/lib/libompitrace.so.0.0.0
  /usr/lib/openmpi/lib/mpi.mod
  /usr/lib/openmpi/lib/openmpi/libompi_dbg_msgq.so
  /usr/lib/openmpi/lib/openmpi/mca_allocator_basic.so
  /usr/lib/openmpi/lib/openmpi/mca_allocator_bucket.so
  /usr/lib/openmpi/lib/openmpi/mca_bml_r2.so
  /usr/lib/openmpi/lib/openmpi/mca_btl_openib.so
  /usr/lib/openmpi/lib/openmpi/mca_btl_self.so
  /usr/lib/openmpi/lib/openmpi/mca_btl_sm.so
  /usr/lib/openmpi/lib/openmpi/mca_btl_tcp.so
  /usr/lib/openmpi/lib/openmpi/mca_coll_basic.so
  /usr/lib/openmpi/lib/openmpi/mca_coll_hierarch.so
  /usr/lib/openmpi/lib/openmpi/mca_coll_inter.so
  /usr/lib/openmpi/lib/openmpi/mca_coll_self.so
  /usr/lib/openmpi/lib/openmpi/mca_coll_sm.so
  /usr/lib/openmpi/lib/openmpi/mca_coll_tuned.so
  /usr/lib/openmpi/lib/openmpi/mca_crs_none.so
  /usr/lib/openmpi/lib/openmpi/mca_dpm_orte.so
  /usr/lib/openmpi/lib/openmpi/mca_ess_env.so
  /usr/lib/openmpi/lib/openmpi/mca_ess_hnp.so
  /usr/lib/openmpi/lib/openmpi/mca_ess_singleton.so
  /usr/lib/openmpi/lib/openmpi/mca_ess_slurm.so
  /usr/lib/openmpi/lib/openmpi/mca_ess_tool.so
  /usr/lib/openmpi/lib/openmpi/mca_grpcomm_bad.so
  /usr/lib/openmpi/lib/openmpi/mca_io_romio.so
  /usr/lib/openmpi/lib/openmpi/mca_iof_hnp.so
  /usr/lib/openmpi/lib/openmpi/mca_iof_orted.so
  /usr/lib/openmpi/lib/openmpi/mca_iof_tool.so
  /usr/lib/openmpi/lib/openmpi/mca_mpool_sm.so
  /usr/lib/openmpi/lib/openmpi/mca_odls_default.so
  /usr/lib/openmpi/lib/openmpi/mca_oob_tcp.so
  /usr/lib/openmpi/lib/openmpi/mca_osc_pt2pt.so
  /usr/lib/openmpi/lib/openmpi/mca_plm_rsh.so
  /usr/lib/openmpi/lib/openmpi/mca_plm_slurm.so
  /usr/lib/openmpi/lib/openmpi/mca_pml_bfo.so
  /usr/lib/openmpi/lib/openmpi/mca_pml_cm.so
  /usr/lib/openmpi/lib/openmpi/mca_pml_ob1.so
  /usr/lib/openmpi/lib/openmpi/mca_pstat_linux.so
  /usr/lib/openmpi/lib/openmpi/mca_pubsub_orte.so
  /usr/lib/openmpi/lib/openmpi/mca_ras_gridengine.so
  /usr/lib/openmpi/lib/openmpi/mca_ras_loadleveler.so
  /usr/lib/openmpi/lib/openmpi/mca_ras_slurm.so
  /usr/lib/openmpi/lib/openmpi/mca_rcache_vma.so
  /usr/lib/openmpi/lib/openmpi/mca_rmaps_rank_file.so
  /usr/lib/openmpi/lib/openmpi/mca_rmaps_resilient.so
  /usr/lib/openmpi/lib/openmpi/mca_rmaps_round_robin.so
  /usr/lib/openmpi/lib/openmpi/mca_rmaps_seq.so
  /usr/lib/openmpi/lib/openmpi/mca_rml_oob.so
  /usr/lib/openmpi/lib/openmpi/mca_routed_binomial.so
  /usr/lib/openmpi/lib/openmpi/mca_routed_direct.so
  /usr/lib/openmpi/lib/openmpi/mca_routed_radix.so
  /usr/lib/openmpi/lib/openmpi/mca_shmem_mmap.so
  /usr/lib/openmpi/lib/openmpi/mca_shmem_posix.so
  /usr/lib/openmpi/lib/openmpi/mca_shmem_sysv.so
  /usr/lib/openmpi/lib/openmpi/mca_vprotocol_pessimist.so

-Ralf.

Bug#813074: ITP: identity4c -- UFP Identity C library

[Richard Levenberg]

Package: wnpp
Severity: wishlist
Owner: Richard Levenberg 

* Package name: identity4c
  Version : 1.0
  Upstream Author : Richard Levenberg 
* URL : https://github.com/ufpidentity/identity4c
* License : GPL2+
  Programming Lang: C
  Description : UFP Identity C library

 This is the C library for integration with UFP Identity.

Bug#813073: ITP: pam-ufpidentity -- UFP Identity PAM module

[Richard Levenberg]

Package: wnpp
Severity: wishlist
Owner: Richard Levenberg 

* Package name: pam-ufpidentity
  Version : 1.0
  Upstream Author : Richard Levenberg 
* URL : https://github.com/ufpidentity/pam_ufpidentity
* License : GPL2+
  Programming Lang: C
  Description : UFP Identity PAM module

 This is the PAM library for using UFP Identity. To configure make sure
 you read https://www.ufp.com/identity/integration.html to get started
creating
 a certificate. Make sure to create an ASCII representable secret key. Then
 configure PAM normally with more details found in INSTALL

Bug#813075: [python-xattr] Upgrade python-xattr to version >= 0.7.5

[Rahul Amaram]

Package: python-xattr
Version: 0.6.4-3
Severity: important

--- Please enter the report below this line. ---
calendarserver 7.0 depends on python-xattr (>= 0.7.5) for successful 
migration of data from older calendarserver versions. Request the 
maintainer to upgrade python-xattr to the latest version as this is a 
blocker for pushing the new version of calendarserver.


--- System information. ---
Architecture: amd64
Kernel: Linux 4.3.0-1-amd64

Debian Release: stretch/sid
500 stable deb.opera.com
500 oldstable packages.x2go.org
500 all liveusb.info
1000 testing security.debian.org
1000 testing httpredir.debian.org

--- Package information. ---
Package's Depends field is empty.

Package's Recommends field is empty.

Package's Suggests field is empty.

Bug#812562: ITP: jscience -- Java science library (algebra, matrices, physical models)

[Andreas Tille]

Hi Wookey,

On Thu, Jan 28, 2016 at 11:23:28PM +, Wookey wrote:
> 
> Yes. It doesn't seem to change very often, so shouldn't be much
> work. I don't actually know any Java to speak of, so if anything
> difficult comes up I'll have to ask for help :-)

I guess we are sitting in the same boot of Java uneducated people.  I
have made (and I'm currently making) very good experiences to throw
problems to debian-j...@lists.debian.org.
 
> I've already hit an issue with the jscience -> geoapi -> jscience
> bootstrap. (jscience builds agains the geoapi.jar it comes with, but
> not against the libgeoapi-java package I've made, and I don't understand
> what's wrong). I'll send a more detailed mail when I have a little
> time to explain the problem.

As I said - ask the Java experts (at least in CC).  They are very
helpful.

Kind regards

 Andreas.

-- 
http://fam-tille.de

Bug#775155: Should provide -cc alternative

[Sebastian Reichel]

Package: src:gcc-defaults
Followup-For: Bug #775155

Hi,

It seems, that the transition from cross-gcc-defaults to gcc-defaults
removed support for the alternatives entries.

-- Sebastian

Bug#812935: openjdk-7-jdk: Missing openjdk-7_7u95-2.6.4-1 build on amd64 for Debian unstable

[Vincent Lefevre]

Control: reassign -1 src:openjdk-7

I'm reassigning the bug to the source package for more accurate
visibility (personally I don't have the openjdk-7-jdk binary package
installed, just openjdk-7-jre, which is affected by the same problem).

On 2016-01-28 09:23:33 +0100, Kurt Roeckx wrote:
> I did an other upload of the .deb files, hopefully that should
> solve it.

https://buildd.debian.org/status/package.php?p=openjdk-7=unstable
now says "Installed" for amd64 (while it was "Uploaded" before). So,
things have improved.

-- 
Vincent Lefèvre  - Web: 
100% accessible validated (X)HTML - Blog: 
Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon)

Bug#811219: transition: netcdf

[Julien Cristau]

On Thu, Jan 28, 2016 at 05:25:22 +0100, Sebastiaan Couwenberg wrote:

> Can we fix this once and for all, or do we have to rely on hints to
> migrate netcdf packages every time?
> 
Yes, please feel free to get the reverse deps of the remaining cruft
fixed or removed.

Cheers,
Julien

Bug#813027: libpng1.6: diff for NMU version 1.6.20-3

[Gianfranco Costamagna]

Package: libpng1.6
Version: 1.6.20-2
Severity: important


Dear maintainer,
I have prepared a bunch of fixes for libpng1.6, they should just modernize the 
packaging, while fixing 

some probably serious issues the package have (explaining the important 
severity) during upgrade cycles

(circular dependencies)


I won't probably upload it on experimental, but I would appreciate if you could 
ack the changes

you can see a build here
http://debomatic-amd64.debian.net/distribution#experimental/libpng1.6/1.6.20-3/buildlog
or find a debdiff attached to this email

summary of the changes:

* Switch to dh-autoreconf
* Remove libpng16-devtools circular dependency, recommend it instead.
* Fix duplicate description lintian warning
* Fix copyright lintian warnings
* Remove copyright.in file
* Use new plain dh calls in rules file
* Remove some old lintian overrides.

the package should behave exactly in the same way, I did a debdiff to both 
changes files and they look the same
(except for the removed lintian overrides)

also build logs seems to be almost identical.

thanks,

Gianfranco


debdiff
Description: Binary data


libpng1.6_1.6.20-2.debian.tar.xz
Description: application/xz

Bug#813010: caja: Shift-Del behaviour is wrong when renaming files

[John Paul Adrian Glaubitz]

On Jan 28, 2016, at 4:17 PM, John Paul Adrian Glaubitz 
 wrote:
> 
> Also, if turns out to be an upstream bug, then you should yell at the Linux 
> Mint people to fix it.

Oops, I meant to say "yell at them for not upstreaming their fix".

In any case, my point is, this is free software developed by the community. So 
you should help as much as possible fixing the issue.

Adrian

Bug#813010: caja: Shift-Del behaviour is wrong when renaming files

[Dark Penguin]

The next problem is to find the bugtracker for MATE. Unsurprisingly, 
googling "bugs mate" yield unwanted and graphic results. %)



--
darkpenguin

Bug#810324: Hint chevrons are actionable

[Christophe Siraut]

control: tags -1 patch

Here is a patch for indicating chevrons are actionable, using a pointing
hand cursor and coloring chevrons in blue.

Cheers,
Christophe

Bug#807229: [Debichem-devel] Bug#807229: votca-tools: diff for NMU version 1.2.4-1.1

[Michael Banck]

On Thu, Jan 28, 2016 at 02:43:45PM +, Mattia Rizzolo wrote:
> On Thu, Jan 28, 2016 at 03:35:11PM +0100, Michael Banck wrote:
> > On Tue, Jan 26, 2016 at 10:42:36AM +, Mattia Rizzolo wrote:
> > > I've prepared an NMU for votca-tools (versioned as 1.2.4-1.1) and
> > > uploaded it to DELAYED/2. Please feel free to tell me if I
> > > should delay it longer.
> > 
> > Well, thanks for fixing that bug, but there's an upload for the GCC5
> > transition waiting in NEW, not sure what happens with that now.
> 
> oh, well...
> 
> That's what will happen: once that upload will be ACCEPTed a build will
> be tried, and (given that the most probably the old gsl will still be
> here as cruft, most probably), it'll be built again with the old
> version.
> 
> If I were you I'd do another upload on top of what is NEW switching the
> build-dep, so once it'll be accepted there will be no need to fix this
> again (also note that if you don't fix this in a subsequent upload or
> incorporate the NMU the versioning tracking of the BTS will think this
> is still open, and hold the testing migration).
> 
> If you do so I'd be happy to ask the ftp team to have a look at this
> package.  2+ months for a binNEW is quite a lot...
> 
> I don't mind my NMU being overwritten or not incorporated, but this
> needs to be eventually fixed somehow :)

Right - though right now I still have a cold so not doing a lot of work
currently.


Michael

Bug#138409: dpkg-dev: please add support for .buildinfo files

[Guillem Jover]

Hi!

On Tue, 2016-01-05 at 14:32:51 +0100, Jérémy Bobbio wrote:
> Control: retitle -1 dpkg-dev: please add support for .buildinfo files
> Control: tag -1 + patch

> The attached patch will enable dpkg-buildpackage to create .buildinfo
> files as specified on the Debian wiki [1]. They have two main purposes:
> 
>  * recording information about the system environment used during a
>particular build—versions of the build dependencies installed, system
>architecture, etc. for easier forensics/debugging;
>  * describe how to recreate (partially or in full) the original
>environment when trying to reproduce a particular build.
> 
> Since Guillem's preliminary review in February 2015 [2], the
> specification has slightly elvolved to be a bit more relaxed and the
> code have been improved.

Cool, thanks!

> One of the main change is that `.buildinfo` should now be named with an
> arbitrary identifier. By default this defaults to $HOSTNAME-$TIMESTAMP
> but can be set to an arbitrary value by the `--buildinfo-identifier`
> command line flag.

Hmmm, leaking the hostname seems slightly privacy-concerning? If the
information therein is not relevant I'd rather use something like an
UUID (although that would require increasing the pseudo-build-essential
set), or just hashing the hostname-timestamp with something like md5
or sha1 or similar.

> To address privacy concerns, the Build-Path field is now only included
> when either the build path starts by `/build/` or
> `--always-include-path` has been specified on the command line of
> `dpkg-genbuildinfo`.

Thanks!

> .buildinfo files are now accepted (although discarded) by the Debian
> archive [3]. This change should thus not affect Debian developpers in
> their daily work.

Ah perfect, thanks for pushing for this. I'm planning on including
most of the patches that look fine for 1.18.5 or .6 ideally.

I've some pending changes I'll be committing to master or a separate
branch, that I'd like to be tested on the reproducible setup (ideally
against the already generated and pre-existing reproducible binaries),
if that's possible, I'll ask about that when those land, I just need
to finish up fewm more unit tests.

Here's a quick review:

> From 7b6d953f834b1e8800d3f8af4570d57d86e5c592 Mon Sep 17 00:00:00 2001
> From: =?UTF-8?q?J=C3=A9r=C3=A9my=20Bobbio?= 
> Date: Fri, 6 Nov 2015 12:17:39 +
> Subject: [PATCH] Add support for .buildinfo files

> diff --git a/man/dpkg-buildpackage.1 b/man/dpkg-buildpackage.1
> index 13770ba..54cee7b 100644
> --- a/man/dpkg-buildpackage.1
> +++ b/man/dpkg-buildpackage.1
> @@ -317,6 +322,12 @@ The source package version (without the epoch).
>  The upstream version.
>  .RE
>  .TP
> +.BI \-\-buildinfo-identifier= identifier
> +By default, \fBdpkg\-buildpackage\fP put the system hostname and the

“puts”, but perhaps better “uses foo and bar to create the quux
filename”.

> +current time in the name of the \fB.buildinfo\fP file. An arbitrary
> +identifier can be specified as a replacement (since dpkg 1.18.5).

I'd probably describe first what the option actually does, so that the
version when it got intruduced makes sense to what it refers to. And
then how does that diverges from the default.

And please, place new sentences on a new line. (I should probably
update the "coding-style" about that.)

> It must
> +contain only alphanumeric characters and hyphens.
> +.TP
>  .BI \-p sign-command
>  When \fBdpkg\-buildpackage\fP needs to execute GPG to sign a source
>  control (\fB.dsc\fP) file or a \fB.changes\fP file it will run

> diff --git a/man/dpkg-genbuildinfo.1 b/man/dpkg-genbuildinfo.1
> new file mode 100644
> index 000..77f2a76
> --- /dev/null
> +++ b/man/dpkg-genbuildinfo.1
> @@ -0,0 +1,98 @@

> +.BI \-\-always\-include\-path
> +By default, the \fBBuild-Path\fR field will only be written if the current
> +directory starts with \fB/build/\fR. Specify this option to always write
> +a \fBBuild-Path\fR field when generating the \fB.buildinfo\fR.

Missing escaped dash in field names.

> diff --git a/scripts/Dpkg/Control/Types.pm b/scripts/Dpkg/Control/Types.pm
> index 09e12d1..ad6e11b 100644
> --- a/scripts/Dpkg/Control/Types.pm
> +++ b/scripts/Dpkg/Control/Types.pm
> @@ -51,16 +52,17 @@ between Dpkg::Control and Dpkg::Control::Fields.
>  
>  use constant {
>  CTRL_UNKNOWN => 0,
> -CTRL_INFO_SRC => 1,  # First control block in debian/control
> -CTRL_INFO_PKG => 2,  # Subsequent control blocks in debian/control
> -CTRL_INDEX_SRC => 4, # Entry in repository's Packages files
> -CTRL_INDEX_PKG => 8, # Entry in repository's Sources files
> -CTRL_PKG_SRC => 16,  # .dsc file of source package
> -CTRL_PKG_DEB => 32,  # DEBIAN/control in binary packages
> -CTRL_FILE_CHANGES => 64, # .changes file
> -CTRL_FILE_VENDOR => 128, # File in $Dpkg::CONFDIR/origins
> -CTRL_FILE_STATUS => 256, # $Dpkg::ADMINDIR/status
> -CTRL_CHANGELOG => 512,   # Output of 

Bug#437407: [Pkg-netfilter-devel] Bug#437407: closed by Arturo Borrero Gonzalez <arturo.borrero.g...@gmail.com> ()

[積丹尼 Dan Jacobson]

> "ABG" == Arturo Borrero Gonzalez  writes:

ABG> I guess that files is a leftover from an older iptables package.

I guess that must be the case.

ABG> Could you please run dpkg -S /etc/default/iptables ?

# dpkg -S /etc/default/iptables
dpkg-query: no path found matching pattern /etc/default/iptables

ABG> Your system seems to hold that file since 2002, which is 14 years...

And probably a lot of other people's systems have it still there too.
Even now with
# apt-cache policy $@
iptables:
  Installed: 1.6.0-2
installed.

So you might want to clean it up for them one day.

Bug#314915: gifshuffle -- GIF colourmap steganography program

[Gustavo Soares de Lima]

Control: reopen -314915

Hi. This is an interesting program.I will be working to package it.

Gustavo Soares de Lima

Bug#808821: asymptote: failing to build on mips

[Julian Gilbey]

On Wed, Jan 27, 2016 at 07:39:47PM +0900, Norbert Preining wrote:
> On Wed, 27 Jan 2016, Julian Gilbey wrote:
> > It's now been fixed upstream with a patch for the compiler bug, see
> > https://sourceforge.net/p/asymptote/bugs/202/
> 
> Thanks Julian, one question - as far as *I* read John's answer,
> the *last* diff is *not* needed for us, right?
> 
> > I don't know when there will be a new asymptote version released with
> > this patch; perhaps you could apply this patch to the Debian package
> > in the meantime?
> 
> Already added the first two diffs and buildin gnow

Well, it's still failing on three.asy on mips.  Might be worth
including the other part of the patch and then trying again?  Or just
doing a manual build on mips with this patch and seeing.

Ho hum.

   Julian

Bug#813042: libopenmpi1.10: file conflict with libopenmpi1.6

[Sebastian Ramacher]

Package: libopenmpi1.10
Version: 1.10.2-1
Severity: grave

libopenmi1.10 and libopenmpi1.6 both contain /usr/lib/openmpi/lib/mpi.mod
without proper package relationships, so libopenmi1.10 fails to install:

Unpacking libopenmpi1.10 (1.10.2-1) ...
dpkg: error processing archive 
/var/cache/apt/archives/libopenmpi1.10_1.10.2-1_amd64.deb (--unpack):
 trying to overwrite '/usr/lib/openmpi/lib/mpi.mod', which is also in package 
libopenmpi1.6 1.6.5-11
dpkg-deb: error: subprocess paste was killed by signal (Broken pipe)

Cheers
-- 
Sebastian Ramacher


signature.asc
Description: PGP signature

Bug#752589: scowl: Please mark packages as Multi-Arch: foreign

[Don Armstrong]

On Mon, 18 Jan 2016, Wookey wrote:
> As explained by David, #666772 isn't getting fixed anytime soon.
> Indeed the consensus is that we are not going to use that expedient
> aproximation. Instead, individual packages will be marked as
> appropriate. So please apply the patch provided and upload.

I'm reworking the packaging of scowl currently, but once that's fixed
up, I'll make this upload.


-- 
Don Armstrong  http://www.donarmstrong.com

Where I sleep at night, is this important compared to what I read
during the day? What do you think defines me? Where I slept or what I
did all day?
 -- Thomas Van Orden of Van Orden v. Perry

Bug#813043: please multiarchify the libhpmud library packages

[Matthias Klose]

Package: src:hplip
Version: 3.15.11+repack0-1
Tags: patch
User: d...@debian.org
Usertags: multiarch

patch at
http://launchpadlibrarian.net/235584730/hplip_3.15.11+repack0-1_3.15.11+repack0-1ubuntu1.diff.gz

Bug#437407: [Pkg-netfilter-devel] Bug#437407: closed by Arturo Borrero Gonzalez <arturo.borrero.g...@gmail.com> ()

[Arturo Borrero Gonzalez]

On 28 January 2016 at 18:12, 積丹尼 Dan Jacobson  wrote:
>> "B" == Debian Bug Tracking System  writes:
>
> B> I don't understand this bug report.
>
> B> The iptables package doesn't ship any file under /etc (at least, recently)
>
> B> Closing this bug now.
>
> # ls -l /etc/default/iptables
> -rw-r--r-- 1 root root 3274 2002-09-20  /etc/default/iptables
> # head /etc/default/iptables
> # /etc/init.d/iptables defaults file
>
> # INTRODUCTION: First thing first, I must warn you. The iptables
> # init.d setup and iptables tools themselves are VERY much capable
> # of locking you out of network services. This includes remote and
> # grep ^\\w /etc/default/iptables
> enable_ipv6=false
> enable_autosave=false
> enable_save_counters=true
> # rm /etc/default/iptables
>

I guess that files is a leftover from an older iptables package.

Could you please run dpkg -S /etc/default/iptables ?

Your system seems to hold that file since 2002, which is 14 years...

-- 
Arturo Borrero González

Bug#787473: systemd: Segfault while adding a new job

[Michael Biebl]

Hi Tino

On Sat, 22 Aug 2015 13:13:20 +0200 Tino  wrote:
> Hi everyone,
> 
> it has been one month since the last crash. I wanted to check if
> everything is ok today and right in to moment i tried to access systemd,
> it crashed. Unfortunately, it received an ABRT signal right after the
> SEGV, which had overwritten the core dump. So i couldn't figure out
> where the SEGV was comming from. I compared the ps faux of the crashed
> system with the rebooted one and there was no difference except PID 1
> (which is usually /sbin/init). Since systemd was crashing right in the
> moment of the "systemctl" command, the origin of the SEGV should be
> systemd, right?
> 
> I don't know if the problem of these SEGV is still the same with version
> 221-1. At least the system is somewhat stable if i don't touch anything.

It's been a while.
Are you still running into this issue?

-- 
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#810946: manage bugs

[Gert Wollny]

Control: reassign 810946 libinsighttoolkit4-dev 
Control: severity 810946 important 
Control: forward  810946 https://issues.itk.org/jira/browse/ITK-3409
Control: merge 810946 810044
Control: thanks 

This is actually an issue between libinsighttoolkit4-dev  and dcmtk, as
reported in #810044, and a workaround is in place. 

Best, 
Gert 

Bug#760610: aptitude: duplicate entries in (reverse) dependencies list

[Manuel A. Fernandez Montecelo]

Control: tags -1 + pending


Hi Rogier,

2014-09-06 00:34 Rogier:

Package: aptitude
Version: 0.6.11-1
Severity: minor

Dear Maintainer,

For some packages, aptitude may list a (reverse) dependency multiple times
in the dependency list. This happens when two or more dependencies directly
or indirectly resolve to the same package.

Example:
About 700-800 (estimated) packages depend on debconf. Currently, the majority
use the following dependency declaration:
Depends: [...] debconf (>= 0.5) | debconf-2.0 [...]
As the package 'debconf' actually provides 'debconf-2.0' as well, aptitude ends
up including debconf twice in the list of dependencies.

For the reverse dependencies, the same holds: For instance, the reverse 
dependency
list of debconf includes almost all packages twice, and some three times 
because of
this. This results in a list of about 1600 reverse dependencies for debconf.

Packages that end up being listed three times in debconf's reverse dependency 
list,
seem to have the following dependency declaration:
Depends: [...] debconf, [...] debconf (>= 0.5) | debconf-2.0 [...]
(based on a sample of a few packages that I checked)

It would be nice if, where possible, identical packages were not listed multiple
times in (reverse) dependency lists.


Thanks for the report.

I think that the case of the reverse-dependencies is the really
problematic one.

The "direct" dependencies are often much less, for one; and the
alternative dependencies are not always virtual packages so they're
quite evident, or there is only one extra item listed (so having 4
instead of 3 is not that bad and also very apparent why it happens), or
the dependency is on one virtual package with many different package
names, in which which are also quite apparent what's going on.

Examples:

   --\ sbuild | xdeb | pdebuild-cross (UNSATISFIED)
 p sbuild 0.68.0-1
 p sbuild 0.68.0-1.0~exp1
 p xdeb 0.6.6
  
   --\ awk

 i gawk 1:4.1.3+dfsg-0.1
 p gawk:i386 1:4.1.3+dfsg-0.1
 i A   mawk 1.3.3-17
 p mawk:i386 1.3.3-17
 p original-awk 2012-12-20-5
 p original-awk:i386 2012-12-20-5
   
   --\ phonon-backend-vlc | phonon-backend

 p phonon-backend-gstreamer 4:4.8.2-2
 p phonon-backend-null 4:4.8.3-2
 i phonon-backend-vlc 0.8.2-1
 i phonon-backend-vlc 0.8.2-1
   
   --\ Suggests (2)

 --\ default-mta | mail-transport-agent
 p citadel-mta 9.01-1+b1
 p courier-mta 0.75.0-10
 p dma 0.9-1+b1
 p dma:i386 0.9-1+b1
 p esmtp-run 1.2-12
 p exim4-daemon-heavy 4.86-7+b2
 p exim4-daemon-heavy 4.87~RC3-1
 p exim4-daemon-light 4.86-7+b2
 p exim4-daemon-light 4.86-7+b2
 p exim4-daemon-light 4.87~RC3-1
 p exim4-daemon-light 4.87~RC3-1
 p masqmail 0.3.4-1
 i msmtp-mta 1.6.3-1
 p nullmailer 1:1.13-1+b1
 p opensmtpd 5.7.3p1-1
 p postfix 2.11.3-1+b1
 p qmail-run 2.0.2+nmu1
 p sendmail-bin 8.15.2-3
 p ssmtp 2.64-8
 


Avoiding to add versions to the trees is relatively quite costly in
general for relatively little gain, in my opinion (in computing
run-time, as well as implementation+maintenance time).  Comparing pkg
name and version is not enough -- there can be cases of multiple
repositories with same pkg name and version, but other different
fields/origin URL/etc, but this is rare, so we would be doing lots of
computations all the time only for a some cases where package is
repeated because of the overlapping dependency.

If this had to change perhaps it would make sense to change it like the
next example.  But showing dependencies like the above is quite
stablished and central part in aptitude, and probably people prefer it
that way, because there are few or no complaints about this.

Hypotetical examples:

   --\ phonon-backend-vlc | phonon-backend
 --\ phonon-backend-vlc
 i phonon-backend-vlc 0.8.2-1
 --\ phonon-backend
 p phonon-backend-gstreamer 4:4.8.2-2
 p phonon-backend-null 4:4.8.3-2
 i phonon-backend-vlc 0.8.2-1

   --\ awk
 --\ gawk
 i gawk 1:4.1.3+dfsg-0.1
 p gawk:i386 1:4.1.3+dfsg-0.1
 --\ mawk
 i A   mawk 1.3.3-17
 p mawk:i386 1.3.3-17
 --\ original-awk
 p original-awk 2012-12-20-5
 p original-awk:i386 2012-12-20-5
   
However, as I said, people probably prefer the current way because in

the vast majority of cases this is not a problem, and showing the extra
branch/nodes makes it longer, more bulky and less "clean" -- perhaps
more annoying than the repeated entries.  I actually prefer the examples
far above of "phonon" and "awk" than these hypotetical ones below.


Now, I think that the case of reverse dependencies is more problematic,
not only because of special cases like "debconf" with hundreds of
dependencies repeated, but because one never knows if the dependency is
specifically exactly on the package that we are looking at, or in a
provided package (and if there are alternatives, so e.g. one can
uninstall the current package and keep 

Bug#807190: closed by Andrei Zavada <johnhom...@gmail.com> (Bug#807190: fixed in cnrun 2.0.3-1)

[Mattia Rizzolo]

On Thu, Jan 28, 2016 at 07:21:59PM +0200, andrei zavada wrote:
> As for the repo, upstream is pushing to both
> cnrun.alioth.debian.org/~hmmr-guest/public_git/cnrun.git and
> git.debian.org/git/debian-med/cnrun.git. The Vsc-Git tag in
> debian/control points to git://anonscm.debian.org/cnrun/cnrun.git. Is
> the suggestion to remove cnrun from debian-med?

I only looked at Vcs-Browser, actually.
Anyway, in the experimental package:

Vcs-Git: git://anonscm.debian.org/cnrun/cnrun.git
Vcs-Browser: http://anonscm.debian.org/gitweb/?p=debian-med/cnrun.git;a=summary

which seems quite weird to me.

1) the repository pointed by Vcs-Git does not exist
2) That url implies the existance of a cnrun project at alioth, which I
   can't find

If the repository you actually use is the one pointed by Vcs-Git,
Vcs-Browser should be the browser of that one, not of another one.

Then you're talking about a alioth:~hmmr-guest/public_git/cnrun.git,
which does have stuff.  Though

1) it's somehow (don't know why) exported through cgit
2) it's not a "standard" git-buildpackage repository (but that's OKish)

Things gets weird and weird (from my PoV, at least), when I accidentally
find another git repository under the pkg-exppsy (that I don't even know
what it's) namespace...


I think it would be nice to clarify this situation...


> 
> Cheers,
> Andrei
> 
> 
> On 28 January 2016 at 16:26, Mattia Rizzolo  wrote:
> > Dear maintainer,
> >
> > On Tue, Jan 12, 2016 at 09:51:54PM +, Debian Bug Tracking System wrote:
> >>  cnrun (2.0.3-1) experimental; urgency=low
> >>  .
> >>* Build with gsl-2.0 (Closes: #807190).
> >>* New upstream version (skipping the buggy 2.0.2).
> >
> >
> > This needs to be fixed also for unstable, where the actual development
> > happens, so the transition can eventually end.
> > Can you please either upload this to unstable or update the unstable
> > version to change the build-dependency?
> >
> > I'm also happy to do an NMU if you feel you don't have time to do this.
> >
> >
> > BTW, can I ask why the git repository of this package is under the
> > debian-med namesapce whilst this package is not team maintained?
> >
> > --
> > regards,
> > Mattia Rizzolo
> >
> > GPG Key: 66AE 2B4A FCCF 3F52 DA18  4D18 4B04 3FCD B944 4540  .''`.
> > more about me:  http://mapreri.org  : :'  :
> > Launchpad user: https://launchpad.net/~mapreri  `. `'`
> > Debian QA page: https://qa.debian.org/developer.php?login=mattia  `-

-- 
regards,
Mattia Rizzolo

GPG Key: 66AE 2B4A FCCF 3F52 DA18  4D18 4B04 3FCD B944 4540  .''`.
more about me:  http://mapreri.org  : :'  :
Launchpad user: https://launchpad.net/~mapreri  `. `'`
Debian QA page: https://qa.debian.org/developer.php?login=mattia  `-


signature.asc
Description: PGP signature

Bug#813040: dbconfig-mysql: error or warning message during upgrade

[Paul Gevers]

Control: tags -1 moreinfo

On 28-01-16 19:02, Guy Durrieu wrote:
> When upgrading my debian install (sid/stretch) I got the following
> message :
> 
> "MySQL database support detected, but apparently missing Depends on
> dbconfig-
> mysql packages. Please report this issue to the package maintainer.."
> 
> That's done.

Good. Out of curiosity, which bug number?

> Having a sight to my install, dbconfig-mysql actually isn't installed,
> and when I ask to install it, the package "dbconfig-no-thanks" need to
> be uninstalled.

dbconfig-mysql and dbconfig-no-thanks conflict on purpose, so can't be
installed together. But are you now saying that you saw the message
above while dbconfig-no-thanks is installed? That is a severe bug, as
dbconfig-no-thanks is supposed to prevent dbconfig-common from doing
anything (including emitting the warning you see above.

> Is it now necessary to do so ?

Yes, unless you don't want dbconfig-common support.Than you should leave
dbconfig-no-thanks installed and leave dbconfig-mysql uninstalled.

How and why did you install dbconfig-no-thanks in the first place?

Paul



signature.asc
Description: OpenPGP digital signature

Bug#813038: deborphan: Misinterprets 'Package-Type' field

[Liam O'Toole]

Package: deborphan
Version: 1.7.28.8-0.1
Severity: normal

Dear Maintainer,

The output of deborphan contains a spurious entry when a package contains the
'Package-Type' field in /var/lib/dpkg/status. The python-paramiko package, for
example contains the following field:

Package-Type: deb

As a result, the output of 'deborphan -a' contains the following:

main/python   deb:all

Of course, the package 'deb' does not exist. Therefore the output is
misleading. A likely explanation is that deborphan searches for '^Package' when
looking for package names and does not consider the extra characters before the
colon.

-- System Information:
Debian Release: 8.3
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'stable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 3.16.0-4-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_IE.UTF-8, LC_CTYPE=en_IE.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages deborphan depends on:
ii  libc6  2.19-18+deb8u2

Versions of packages deborphan recommends:
ii  apt   1.0.9.8.2
ii  dialog1.2-20140911-1
ii  gettext-base  0.19.3-2

deborphan suggests no packages.

-- no debconf information

Bug#809923: New package proposal: nordlicht

[Sebastian Ramacher]

On 2016-01-28 09:20:37, Peter Spiess-Knafl wrote:
> Hi Sebastian!
> 
> I migrated the repository to pkg-multimedia and applied the required
> changes to d/control.
> 
> Once the upload is done, I will sign off the appropriate git-tag.

Uploaded, thanks!

Cheers
-- 
Sebastian Ramacher


signature.asc
Description: PGP signature

Bug#812989: don't assume SSE2 instructions on i386

[Stig Sandbeck Mathisen]

Control: tags -1 + confirmed

Matthias Klose  writes:

> the configury assumes the availability of SSE2 instructions on i386
> when using a triplet or cpu starting with i686, which it shouldn't.
>
> patch at
> http://launchpadlibrarian.net/235541334/jemalloc_3.6.0-9_3.6.0-9ubuntu1.diff.gz

Hello,

Thanks for reporting a bug, and thanks for the patch.

This looks a bit like the issue discussed at
https://github.com/jemalloc/jemalloc/issues/52 in the upstream bug
tracker.

That issue mentions using a few options for ./configure,
"--build=i386-pc-linux-gnu" and "--host=i386-pc-linux-gnu".  Do you
think using that in debian/rules would also solve the issue?

-- 
Stig Sandbeck Mathisen

Bug#807200: freefem++: diff for NMU version 3.38.1-1.1

[Dimitrios Eftaxiopoulos]

Hello Mattia,
Thanks for your interest and your help regarding the maintenance of freefem++. 

I plan to build and upload the new upstream version 3.43 during the next few 
days and I will update  the B-D to GSL-2.

Best regards
Dimitris

Στις Tuesday 26 of January 2016 11:45:20 γράψατε:
> Control: tags 807200 + pending
> 
> Dear maintainer,
> 
> I've prepared an NMU for freefem++ (versioned as 3.38.1-1.1) and
> uploaded it to DELAYED/2. Please feel free to tell me if I
> should delay it longer.
> 
> Regards.

Bug#813053: json evil license problem

[Bastien ROUCARIES]

severity: serious
user: debian...@lists.debian.org
usertags: json-evil-license
package: icedove
version: 38.5.0-1

Hi,

mozilla/dom/system/gonk/tests/marionette/ril_jshint/jshint.js

is licenced under evil licence...

Please repack and notify archive.debian.org in order to remove old package.

Bastien

Bug#813054: Evil licence

[Bastien ROUCARIES]

severity: serious
user: debian...@lists.debian.org
usertags: json-evil-license
package: iceweasel
version: 44.0-1

Hi,

mozilla/dom/system/gonk/tests/marionette/ril_jshint/jshint.js

is licenced under evil licence...

Please repack and notify archive.debian.org in order to remove old package.

Bug#812397: l10n: Minor grammatical correction in msgids

[Manuel A. Fernandez Montecelo]

Control: tags -1 + pending


Hi Morten,

2016-01-23 10:05 Morten Bo Johansen:

Package: aptitude
Version: 0.7.5-3
Severity: minor
Tags: patch l10n

Dear Maintainer,

Patch attached for a minor glitch in two msgids in the file,
"cmdline_action.cc".


Thanks for the report.

I asked native speakers and they prefer the current form (without -ing)
than your proposed change.

However, they think that both are somewhat wrong (even if the original
was written by a native English speaker, AFAIK) and they suggested
another one, which I applied:

 _("Couldn't find any package whose name is \"%s\", but there are %zu packages which contain 
\"%s\" in their name:\n"),


Cheers.
--
Manuel A. Fernandez Montecelo 

Bug#775458: [Pkg-clamav-devel] Bug#775112: systemd: repeatedly tries to start clamav

[Michael Biebl]

Control: forwarded -1 https://github.com/systemd/systemd/issues/2467

Hi Andreas!

Am 08.05.2015 um 16:19 schrieb Andreas Cadhalpun:
> A quick reproducer for the problem:
> # cat < /etc/systemd/system/test.socket
> [Socket]
> ListenStream=/run/test.ctl
> EOF
> # cat < /etc/systemd/system/test.service
> [Unit]
> Requires=test.socket
> ConditionPathExistsGlob=/tmp/nonexistent
> 
> [Service]
> ExecStart=/bin/true
> EOF
> # systemctl daemon-reload
> # systemctl start test.socket
> # echo a | nc -U /run/test.ctl
> 
> The last command hangs indefinitely and systemd starts eating 100 % CPU
> time of one core, while producing GBs of log messages.

Thanks for the reproducer, I can still trigger this issue with v228. So
I've forwarded it upstream. Marking the bug accordingly.

Feel free to follow up on the upstream bug report.

Regards,
Michael
-- 
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?



signature.asc
Description: OpenPGP digital signature

Bug#813058: RFP: scudcloud -- ScudCloud is a non official desktop client for Slack

[Pierre Rudloff]

Package: wnpp
Severity: wishlist

* Package name: scudcloud
  Version : 1.5
  Upstream Author : Rael Gugelmin Cunha 
* URL : https://github.com/raelgc/scudcloud
* License : MIT License
  Programming Lang: Python
  Description : ScudCloud is a non official desktop client for Slack

ScudCloud is a non official desktop client for Slack. Slack (http://slack.com)
is a platform for team communication.

The official Slack client is not open source, so I guess it makes sense to have
an alternative client in Debian.

Bug#813060: libopenmpi-dev: mpif90 linker problems

[Torquil Macdonald Sørensen]

Package: libopenmpi-dev
Version: 1.10.2-1
Followup-For: Bug #813060

Forgot to mention: to get 1.10 installed I hade to use dpkg --force-overwrite,
so maybe that's related to this problem?

-- System Information:
Debian Release: stretch/sid
  APT prefers unstable
  APT policy: (990, 'unstable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.3.0-1-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages libopenmpi-dev depends on:
ii  libc6   2.21-7
ii  libhwloc-dev1.11.2-2
ii  libhwloc5   1.11.2-2
ii  libibverbs-dev  1.1.8-1.1
ii  libopenmpi1.10  1.10.2-1
ii  openmpi-common  1.10.2-1

libopenmpi-dev recommends no packages.

libopenmpi-dev suggests no packages.

-- no debconf information

Bug#138409: dpkg-dev: please add support for .buildinfo files

[Guillem Jover]

Hi!

zOn Thu, 2016-01-28 at 19:01:59 +0100, Holger Levsen wrote:
> On Donnerstag, 28. Januar 2016, Guillem Jover wrote:
> > Hmmm, leaking the hostname seems slightly privacy-concerning? If the
> > information therein is not relevant I'd rather use something like an
> > UUID (although that would require increasing the pseudo-build-essential
> > set), or just hashing the hostname-timestamp with something like md5
> > or sha1 or similar.
> 
> yeah, "something / anything" is fine. dak / the archive software can rename 
> it 
> anyway, as it likes.

Ah ok, perfect then.

> (I'd be in favor of naming the first accepted buildinfo 
> file of the archive just "" so that it's predictable…

I'm not sure how we'd use a sequential number in a distributed manner
starting with 0s though? :9

> > I've some pending changes I'll be committing to master or a separate
> > branch, that I'd like to be tested on the reproducible setup (ideally
> > against the already generated and pre-existing reproducible binaries),
> > if that's possible, I'll ask about that when those land, I just need
> > to finish up fewm more unit tests.
> 
> That's possible, though not (yet nor in near future) against pre-existing 
> binaries. (We lack the code for that.)
> 
> What we can do easily, is build and upload dpkg to our repo and use it to 
> build the whole Debian archive on amd64, which roughly takes 8 days for both 
> sid+stretch, and thus roughly 4 days for one suite, if we disable building 
> the 
> other. (Which we can definitly do, especially if we don't disable building of 
> new versions in that other suite…)

Oh ok, that's a bit unfortunate, it would be nice to be able to catch
any possible regressions in the generated binaries, and it would also
show how to use reproducible builds to see that nothing has actually
changed, even after implementation changes in the toolchain.

On Thu, 2016-01-28 at 19:02:53 +0100, Holger Levsen wrote:
> +many thanks for your thorough review! :-)

No problem!

Regards,
Guillem

Bug#804854: systemd: FTBFS if using libeatmydata

[Michael Biebl]

Control: tags -1 + moreinfo

Hi Laurent

On Thu, 12 Nov 2015 13:02:40 +0100 Laurent Bigonville 
wrote:
> I'm using libeatmydata in sbuild on my machine, and it FTBFS due to the
> postbuild check that looks for libs in /usr

I'm using eatmydata (105-1) as well (with pbuilder/cowbuilder), but I
can't reproduce your problem.

Does this build failure rely on a special setup and if so, how can we
reproduce it?

-- 
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#813040: dbconfig-mysql: error or warning message during upgrade

[Guy Durrieu]

Le 28/01/2016 20:32, Paul Gevers a écrit :

Control: tags -1 moreinfo

On 28-01-16 19:02, Guy Durrieu wrote:

When upgrading my debian install (sid/stretch) I got the following
message :

"MySQL database support detected, but apparently missing Depends on
dbconfig-
mysql packages. Please report this issue to the package maintainer.."

That's done.

Good. Out of curiosity, which bug number?


Don't understand the question... There were no more information than the 
message itself, which appeared twice: one at the beginning of the 
upgrade process, one when upgrading phpmyadmin...



Having a sight to my install, dbconfig-mysql actually isn't installed,
and when I ask to install it, the package "dbconfig-no-thanks" need to
be uninstalled.

dbconfig-mysql and dbconfig-no-thanks conflict on purpose, so can't be
installed together. But are you now saying that you saw the message
above while dbconfig-no-thanks is installed?

Yes, that's what happened.

That is a severe bug, as
dbconfig-no-thanks is supposed to prevent dbconfig-common from doing
anything (including emitting the warning you see above.


Well, mySQL still works anyway :)


Is it now necessary to do so ?

Yes, unless you don't want dbconfig-common support.Than you should leave
dbconfig-no-thanks installed and leave dbconfig-mysql uninstalled.

How and why did you install dbconfig-no-thanks in the first place?


As far as I know, this was done the first time I installed LAMP, a while 
ago. I didn't specifically require dbconfig-no-thanks, I suppose it came 
with all the stuff. Until today, I wasn't aware there were possible 
alternatives, and my question was about what is the right thing to do (I 
only use mySQL and don't clearly see the advantages of installing 
dbconfig-mysql).



Paul



Thanks for your help !

Regards.

-- GD.

Bug#812989: don't assume SSE2 instructions on i386

[Matthias Klose]

On 28.01.2016 19:35, Stig Sandbeck Mathisen wrote:


Control: tags -1 + confirmed

Matthias Klose  writes:


the configury assumes the availability of SSE2 instructions on i386
when using a triplet or cpu starting with i686, which it shouldn't.

patch at
http://launchpadlibrarian.net/235541334/jemalloc_3.6.0-9_3.6.0-9ubuntu1.diff.gz


Hello,

Thanks for reporting a bug, and thanks for the patch.

This looks a bit like the issue discussed at
https://github.com/jemalloc/jemalloc/issues/52 in the upstream bug
tracker.

That issue mentions using a few options for ./configure,
"--build=i386-pc-linux-gnu" and "--host=i386-pc-linux-gnu".  Do you
think using that in debian/rules would also solve the issue?


well, you can see that in the build log. I didn't check if this would have other 
effects.

Bug#813056: RFP: climb -- A Composer version manager tool

[Pierre Rudloff]

Package: wnpp
Severity: wishlist

* Package name: climb
  Version : 0.8.1
  Upstream Author :  Vincent Klaiber 
* URL : https://github.com/vinkla/climb
* License : MIT License
  Programming Lang: PHP
  Description : A Composer version manager tool

Bug#803531: systemd: timeout mounting /home (btrfs) at boot

[Michael Biebl]

Am 28.01.2016 um 23:11 schrieb Brian May:
> Michael Biebl  writes:
> 
>> That sounded like you can no longer reproduce the issue with testing.
> 
> Sorry, will try to clarify what I meant.
> 
> I tried to reproduce the problem inside a VM, but I couldn't reproduce
> the problem inside the VM.
> 
> The problem still occurs on my physical box.
> 
> I speculate (without any evidence) that maybe my harddisks a bit slow to
> initialise, and initially both have SYSTEMD_READY=0. Then when the drive
> comes ready, udev removes SYSTEMD_READY, but only on one of the
> partitions. With it being somewhat random which partition this is.

Btw, this sound like a duplicate of

https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=747629


-- 
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#767411: This bug is not really fixed

[Francesco Poli]

Control: reopen -1
Control: notfixed -1 openmpi/1.10.2-1

Hello,
I think this bug report (filed against package torque) should not have
been closed by an upload of package openmpi.

The fact that torque support has been dropped in openmpi does not mean
that the issues in torque are solved.

I am therefore reopening the bug report.

Bye.


-- 
 http://www.inventati.org/frx/
 There's not a second to spare! To the laboratory!
. Francesco Poli .
 GnuPG key fpr == CA01 1147 9CD2 EFDF FB82  3925 3E1C 27E1 1F69 BFFE


pgpyYp740E2xE.pgp
Description: PGP signature

Bug#813059: mingw32: Incorrect value for IP_ADD_MEMBERSHIP=5, should be 12. setsockopt does not work.

[Leif Asbrink]

Package: mingw32
Version: 4.9.1-19+14.3
Severity: normal

Dear Maintainer,

*** Reporter, please consider answering these questions, where appropriate ***

   * What led up to the situation?
My program compiles correctly under Debian wheezy and also on many other
systems. Fedora, Windows XP etc. Debian jessie and sid do not work.
They also do not work when I try to generate 64 bit  code.
The progarm fails when setsockopt is called with IPPROTO_IP and 
IP_ADD_MEMBERSHIP. The reported error is 10042, WSAENOPROTOOPT

   * What exactly did you do (or not do) that was effective (or
 ineffective)?
I replaced IP_ADD_MEMBERSHIP with its correct numerical value = 12

   * What was the outcome of this action?
The program works correctly. 

   * What outcome did you expect instead?

*** End of the template - remove these template lines ***


-- System Information:
Debian Release: stretch/sid
  APT prefers unstable
  APT policy: (500, 'unstable'), (500, 'stable')
Architecture: amd64 (x86_64)

Kernel: Linux 4.3.0-1-amd64 (SMP w/16 CPU cores)
Locale: LANG=en_GB.utf8, LC_CTYPE=en_GB.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages mingw32 depends on:
ii  dpkg1.18.4
ii  g++-mingw-w64-i686  5.3.1-3+16+b1
ii  gcc-mingw-w64-base  5.3.1-3+16+b1
ii  gcc-mingw-w64-i686  5.3.1-3+16+b1
ii  mingw32-binutils2.25-5+5.2+deb8u1

mingw32 recommends no packages.

mingw32 suggests no packages.

-- no debconf information

Bug#138409: [Reproducible-builds] Bug#138409: dpkg-dev: please add support for .buildinfo files

[Guillem Jover]

Hi!

On Thu, 2016-01-28 at 19:36:25 +0100, Jérémy Bobbio wrote:
> Guillem Jover:
> > I've some pending changes I'll be committing to master or a separate
> > branch, that I'd like to be tested on the reproducible setup (ideally
> > against the already generated and pre-existing reproducible binaries),
> > if that's possible, I'll ask about that when those land, I just need
> > to finish up fewm more unit tests.
> > 
> > Here's a quick review: […]
> 
> Thanks for the review! Just so I can organize my work, are your pending
> changes related to the .buildinfo?

Nope, they are for the sorted file lists, and ar member stuff.

> I can spend the next days improving the patch with your remarks, but I'd
> rather not duplicate your work. :)

Sure, go ahead. :)

Thanks,
Guillem

Bug#810921: RFS: rep-gtk/1:0.90.8.2-1 [ITA] -- GTK+ binding for librep

[Jose M Calhariz]

Sorry for taking a long time to reply, adding my delay I had email
problems. 


On Thu, Jan 14, 2016 at 12:13:29AM +, Mattia Rizzolo wrote:
> On Wed, Jan 13, 2016 at 07:12:38PM +, Jose M Calhariz wrote:
> >  * Package name: rep-gtk
> 
> ok, let the party begin! :)
> 
> * you removed a old transition package.
>   + \o/ yay less cruft in the archive!
>   + FYI, I confirmed by `dak rm -Rbn rep-gtk-gnome` that it is a leaf
> package.
>   + also please remove debian/rep-gtk-gnome.NEWS

Done

> * debian/control:
>   + a version costriction in a Suggest is really useless.  As in, you
> have no assurances *at all* that it'll be followed.
> But then, you build-dep on librep >= $version, so you'll get a
> depends on that version, so not all might be lost :)
> tl;dr: you don't need to do anything here, but be aware that
> versioned Suggests are meaningless.
>   + the build-dep on autotools-dev is useless, please remove it.

Done

>   + I still get vcs-field-not-canonical by lintian.  indeed Vcs-Git is
> wrong (there is a /git/ too much in the middle).  otherwise, you
> might want to use https:// for Vcs-Git too instead of the dumb
> git://.  As you prefer.

Done

>   + I have a extended-description-is-probably-too-short, please fix.

I don't know what to add to the description so requested the help of
Upstream.

> * debian/changelog:
>   + 2 trailing whitespaces at line 4.

Done

>   + "remove upstream debian directory" ???  what's this?
>   + "New localization of files for package rep-gtk." and this?
>   + "Replace sed command by dh_listpackages." this is not there anymore
>   + "Merge the packaging work of Christopher Roy Bratusek." be more
> verbose in this.  short dh, compat 9, dep5, blablabla

Done

>   + s/read ability/readability/ maybe?

Done

>   + mention the removal of rep-gtk-gnome.

Done

>   + you need to target experimental, unstable won't be able to satisfy
> the dependency on librep until the transition start (where you'll
> need to re-upload the packages on unstable.  actually it would be
> enough to have them ready, bug given that there are a lot of
> changes, and you are a sponsored person where there are reviews
> going on, better have them in experimental, and re-upload them in
> unstable later).

Done

> * debian/rules:
>   + override_dh_configure is unneed.  as I said with librep, those flags
> are already exported in compat 9.
> - also , there is trailing whitespace here, but if you remove the
>   whole line...
>   + override_dh_install just to call dh_install ? ;)

Need to cleanup gtk.la as is needed because of
https://bugs.debian.org/684443

>   + override_dh_installexamples => be aware you can also write the
> directory name in debian/examples (up to you if you prefer small
> files in debian/ or lines in d/rules)

No preference, so I am going for lines in d/rules

>   + don't DH_VERBOSE need to be exported to work?
> * you're building static libraries.  Do you really need them?  In Debian
>   we don't like static libraries.  Given that this is a standard autofoo
>   package, --disable-static to configure should do the trick.
>   + this will also get rid of unstripped-static-library and
> non-empty-dependency_libs-in-la-file lintian tags.

See https://bugs.debian.org/684443

> * something to say about https://bugs.debian.org/680449 ?
> 

No longer makes sense with the new version.  When this rep-gtk and
sawfish hit experimental I will ask user to try again.

Kind regards
Jose M Calhariz

-- 
--
Cerveja? Serve já!


signature.asc
Description: Digital signature

Bug#803531: systemd: timeout mounting /home (btrfs) at boot

[Michael Biebl]

Am 28.01.2016 um 20:46 schrieb Brian May:
> Michael Biebl  writes:
> 
>> Is this still reproducible with (systemd v215 from) jessie?
>>
>> Should we close the bug report until/unless we have a proper way to
>> reprodce the issue?
> 
> The problem first started with Jessie. As I have said I can still
> reproduce this on testing.

Oh sorry, then I must have misunderstood you.

> I had a look again at reproducing this on a KVM, in Debian testing. I
> used separate harddisks for both. However, unable to see any problems.

That sounded like you can no longer reproduce the issue with testing.


Regards,
Michael
-- 
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?



signature.asc
Description: OpenPGP digital signature

Bug#812562: ITP: jscience -- Java science library (algebra, matrices, physical models)

[Andreas Tille]

Hi Wookey,

since you are just maintaining several packages in Debian Science I
assume you will do so with this package as well.  I'm just forwarding
the ITP to the list.

Kind regards

   Andreas.

On Mon, Jan 25, 2016 at 03:45:32AM +, Wookey wrote:
> Package: wnpp
> Severity: wishlist
> Owner: Wookey 
> 
> * Package name: jscience
>   Version : 4.3.1
>   Upstream Author : 2007 JScience (http://jscience.org/)
> * URL : http://jscience.org/
> * License : JScience
>   Programming Lang: Java
>   Description : Java science library (algebra, matrices, physical models)
> 
>  JScience library provides a comprehensive Java library for the
>  scientific community. It contains the following modules:
>  .
>  * Units of Measurement services.
>  * A coordinates module compliant with OGC/ISO specifications
>for the development and deployment of geographic applications.
>  * A rigourous mapping of mathematical structures (e.g. Group,
>Ring, Field, VectorSpace ) to Java interfaces.
>  * A linear algebra module, which includes a first parameterized
>matrix class capable of resolving linear system of equations
>involving any kind of elements.
>  * A functions module for symbolic calculations and analysis.
>  * Support for exact or arbitrary precision measurements
>  * Support for Standard, Relativistic, High-Energy, Quantum and
>Natural physical models.
>  * A monetary module for precision-guaranteed calculations and
>currencies conversions.
> 
> I am packaging this because it is needed by the current release of
> caveconverter for calculating hulls. And it seems like quite a
> generally useful java package. 
> 
> This package depends recursively(!) on geoapi (http://www.geoapi.org/
> ). Presumably that recursiveness is not a good enough reason to just
> put geoapi in the same source package, and build them together, so I
> should file an ITP for that too (and ideally put in staged builds so
> they can easily be built)?
> 
> There was #24 filed about this in 2009, and closed in 2011. 
> 
> 

-- 
http://fam-tille.de

Bug#812563: ITP: geoapi -- Set of Java interfaces for geospatial applications

[Andreas Tille]

Hi Wookey,

I'm not sure whether Debian Science or Debian GIS is the better
maintenance team.  Just forwarding the ITP to both lists.

Kind regards

Andreas.

On Mon, Jan 25, 2016 at 03:58:15AM +, Wookey wrote:
> Package: wnpp
> Severity: wishlist
> Owner: Wookey 
> 
> * Package name: geoapi
>   Version : 3.0.0
>   Upstream Author : 2003-2011 Open Geospatial Consortium, Inc.
> * URL : http://www.geoapi.org
> * License : geoapi (BSDish)
>   Programming Lang: Java
>   Description : Set of Java interfaces for geospatial applications
> 
>  geoapi is a set of java bindings provided for geospatial applications
>  by the GeoAPI project. They are neutral, interface-only APIs derived
>  from OGC/ISO Standards.
>  .
>  The interfaces developed by the GeoAPI project include many of the
>  data structures and manipulation methods needed for geographic
>  information system applications. GeoAPI 3.0 defines a core set of
>  interfaces for metadata handling, for geodetic referencing,
>  projection and conversion, and is a standard of the Open Geospatial
>  Consortium (OGC).
>  .
>  The GeoAPI interfaces closely follow the ISO 19100 series standards:
>  ISO 19115: Metadata, ISO 19111: Referencing by coordinates, ISO
>  19123: Coverage. GeoAPI provides an interpretation and adaptation of
>  these standards to match the expectations of Java programmers.
> 
> 
> This is being packaged as it is closely tied to jscience.
> jscience needs geoapi to build (org.opengis.*)
> 
> geoapi need javax.measure.utils from jscience to build.
> 
> 

-- 
http://fam-tille.de

Bug#812625: RFA: guitarix -- Rock guitar amplifier for Jack

[Víctor Cuadrado Juan]

owner !
thanks

I happily adopt it, under the Multimedia Team.

Thanks for your contributions to this package all this time.

Cheers,

-- 
Víctor Cuadrado juan
--
E-Mail: , OpenPGP-Key-ID: 0xA2591E231E251F36
Key fingerprint: E3C5 114C 0C5B 4C49 BA03  0991 A259 1E23 1E25 1F36
My signed E-Mails are trustworthy.



signature.asc
Description: OpenPGP digital signature

Bug#159584: reverse dependency list should show actual dependency

[Manuel A. Fernandez Montecelo]

Control: tags -1 + pending


Hi Andreas,

2002-09-04 13:23 Andreas Bombe:

Package: aptitude
Version: 0.2.11.1-3
Severity: wishlist

When showing the reverse dependencies aptitude only shows the package
names and versions.  This makes it difficult to see whether the reverse
depends really requires that exact package or if it's just one
alternative.  You have to enter every package description to find out.

It would be immediately visible if there was a way to display the
dependency leading to the reverse depends in the list.


I changed this to show it in this way:

 --\ Packages which depend on iceweasel (480)
 --- Depends (348)
 --\ Depends on provided gnome-www-browser (1)
 p cinnamon-desktop-environment 2.8.0
 --\ Depends on provided www-browser (69)
 p bibus-doc-en 1.5.2-4
 p browser-plugin-packagekit 1.0.11-1
 p c-cpp-reference 2.0.2-8
 p cppreference-doc-en-html 20151129+dfsg0-1
 p drgeo-doc 1.5-7
 p fish 2.2.0-3
 p fsl-5.0-core 5.0.8-5
 p gimp-help-ca 2.8.2-0.1
 p gimp-help-de 2.8.2-0.1
 p gimp-help-el 2.8.2-0.1
 p gimp-help-en 2.8.2-0.1
 p gimp-help-es 2.8.2-0.1
 p gimp-help-fr 2.8.2-0.1
 p gimp-help-it 2.8.2-0.1
 p gimp-help-ja 2.8.2-0.1
 p gimp-help-ko 2.8.2-0.1
 [...]
 --- Recommends (30)
 --- Recommends on provided www-browser (67)
 --- Suggests (34)
 --- Suggests on provided www-browser (125)
 --- Enhances (66)
 --- Conflicts (2)
  


It doesn't help for all cases with alternatives, but at least if one
sees that the dependency is on a provided package, one can easily find
if there are other alternatives that might fit the bill.

For example, if there is any package installed which "Depends" on
iceweasel (like "iceweasel-l10-ms" or "xul-ext-blah"), probably cannot
be uninstalled, but if the only ones installed are those depending on
"www-browser" provided by iceweasel, one can substitute iceweasel for
another browser.

Showing the OR dependencies and alternatives is quite difficult to
implement in the way that things work, that's probably why the bug has
been unfixed for 13+ years, and quite might be quite computationally
intensive for packages with hundreds of rev-deps, so I think that this
is an acceptable fix.


Cheers.
--
Manuel A. Fernandez Montecelo 

Bug#813040: dbconfig-mysql: error or warning message during upgrade

[Guy Durrieu]

Le 28/01/2016 23:13, Guy Durrieu a écrit :


Well, mySQL still works anyway :)



My mistake. mySQL still works, but phpmyadmin doesn't  (blank window). I 
tried to install dbconfig-mysql and to reinstall phpmyadmin. No error, 
but still doesn't work.


-- GD.

Bug#775459: log if a condition prevents starting a unit

[Michael Biebl]

Control: forwarded -1 https://github.com/systemd/systemd/issues/2468
Control: severity -1 wishlist

Hi Andreas

>>> So systemd will not start clamav-daemon, if the databases are absent
>>> (and if it did, clamd would fail to start).
>>> But these conditions should probably also be in the socket, so that the
>>> socket is not created, if no databases are present.
>>
>> It should log the reason why it doesn't start.
> 
> It should, so I've made another clone.

I've forwarded your request upstream. Please followup there if you have
further input on this matter.

Regards,
Michael

-- 
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?



signature.asc
Description: OpenPGP digital signature

Bug#811019: anacron not running

[Stephen Paul Weber]

I am fairly certain I also have this bug (on jessie).  My system does not 
have a /etc/systemd/system/anacron.service file -- should I create one?


This is at very least a documentation bug in /etc/default/anacron

--
Stephen Paul Weber, @singpolyma
See  for how I prefer to be contacted
edition right joseph

Bug#808802: #808802 synaptic: Can't drop privileges for downloading as file '/var/lib/apt/lists/partial/ftp.fr.debian.org_debian_dists_testing_InRelease'

[Tsu Jan]

I was wrong. The problem still persists :(

Bug#813045: rarcrack: Recommend unrar (for much faster processing)

[Pierre Rudloff]

Hello,

It seems rarcrack is faster *without* unrar, so we should not recommend it.

Regards,

Le 28/01/2016 21:40, Petr Vorel a écrit :
> please add to Recommends unrar - for much faster processing rar archives.
> Speed without unrar:
> Probing: '2qmzV' [1984 pwds/sec]
> Speed with unrar:
> Probing: '2qmAz' [13 pwds/sec]

Bug#812884: gscan2pdf: Changing the resolution is not persistant

[Jeffrey Ratcliffe]

I see that you are using Ubuntu, not Debian. Please install the latest
version from the PPA[1]. If you can still reproduce the bug, start
gscan2pdf from the command line with the --log=log option, open the
scan dialog, quit, and post the log file.

[1] https://launchpad.net/~jeffreyratcliffe/+archive/ubuntu/ppa