Bug#742310: ITP: python-oslotest -- OpenStack test framework

[Thomas Goirand]

Package: wnpp
Severity: wishlist
Owner: Thomas Goirand 

* Package name: python-oslotest
  Version : 0.1
  Upstream Author : OpenStack developers 
* URL : https://github.com/openstack/oslo.test
* License : Apache-2.0
  Programming Lang: Python
  Description : OpenStack test framework

 OpenStack test framework that provides base classes and fixtures for creating
 unit and functional tests.


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#720096: rsyslog ignores rotated log file

[Harald Dunkel]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

That would give me weekly rotatation of /var/log/syslog, doesn't it?
I didn't touch the packaged rotation config file of rsyslog, but
having different rotation parameters would surely be an advantage.

I would suggest to check if one of the SIGHUPs sent to rsyslog
in the worst case might get lost.

-BEGIN PGP SIGNATURE-
Version: GnuPG v1

iQEcBAEBCAAGBQJTLS8bAAoJEAqeKp5m04HLGe4H/R5h6UrZzOPhoF1TRrKuNzrx
RviZkhAQXgpAq8pO3UOq6YuPQ0Z10xz1um0IFzDhP3gBi8+7zj3w3WJaTVYZ/AFJ
BtZJkC5+BH0S6MBsnl23OdYI3mrIdJDfaj95W6QUG4XslnS4U7k65xsfasEMQR1f
sRQI0mD0/gbdQAoXlwXFdg6R8z7OeAa+ZTpJl6nj5xJpFJ1KYZCmQH8f6gxWo16g
t6TkwBJ+zTY+awMMySZSc3+B0qFoeHCuIpyqPdfqMvKM40GZVNgGooNijVZZHDC9
xpiXmojTlpOrc4/Ztv6j4yQsUuxELbF/U6uy8Bf2QTUPdFFESiZvJwHLmDKNx1Q=
=hJlX
-END PGP SIGNATURE-


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#701962: libsodium packaging

[GCS]

Hi Raúl,

On Fri, Mar 21, 2014 at 11:32 PM, Raúl Sánchez  wrote:
>   Latest advice from Alessandro was very specific, I updated package on my
> repository and reply him privately shortly after his email. I'd say package is
> in good shape and you can take it from either mentors or my repository [0]
>
>   [0] http://trismegisto.no-ip.org/hg/libsodium-debian
 Cool! Your debian/copyright looks much better now. I've to check it.

>   It's also my intention to move my repo to debian hosting, but no sooner
> there's a real need to do so.
 That would be when the package is accepted into the archive. But as
far as I may get commit access to your repository, it's not strictly
needed.

>   As I think I mentioned before, I have no plans to push this into the archive
> until I see a new upstream release.
 Are you in contact with upstream? Any ETA when s/he will have a new release?

>   I'm curious about what you think the package is missing (beside upstream
> release).
 I've some small changes over your packaging[1].

>   If you really think [1] is really important I may try a refreshed upstream
> snapshot + mentors upload.
 It's needed before the package is included in Debian. In general, it
would be nice to have the latest git snapshot of upstream source if
there's no stable release until then.

Regards,
Laszlo/GCS
[1] dget -x 
http://www.barcikacomp.hu/gcs/libsodium_0.4.5+git20140313.dbe51e8ff8-1.dsc


--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#742309: RFS: libvarnam/3.1.3-1

[Navaneeth K N]

Package: sponsorship-requests
Severity: normal

  Package: sponsorship-requests
  Severity: normal

  Dear mentors,

  I am looking for a sponsor for my package "libvarnam"

 * Package name: libvarnam
   Version : 3.1.3-1
   Upstream Author : Navaneeth K N 
 * URL : http://varnamproject.com
 * License : MIT
   Section : libs

  It builds those binary packages:

libvarnam  - Varnam 3 shared library
libvarnam-dev - Varnam 3 development files
varnamc- Commandline interface to libvarnam

  To access further information about this package, please visit the following
URL:

  http://mentors.debian.net/package/libvarnam

  Alternatively, one can download the package with dget using this command:

dget -x
http://mentors.debian.net/debian/pool/main/libv/libvarnam/libvarnam_3.1.3-1.dsc

  More information about libvarnam can be obtained from
http://www.varnamproject.com.

  Changes since the last upload:

  libvarnam (3.1.3-1) stable; urgency=low

* varnam_init_from_lang will make the suggestions directory
* Fixed varnam_init_from_lang() to set errors correctly
* Adding MultiArch directories to varnamc search path
* Added uninstall target
* MultiArch support to the build system
* Added manpages for varnamc

  Regards,
   Navaneeth K N



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

Kernel: Linux 3.11.0-18-generic (SMP w/2 CPU cores)
Locale: LANG=en_IN, LC_CTYPE=en_IN (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#742207: [PATCH] Update the handling of colour output for more use-cases.

[Paul Wise]

Disable colours when stdout is not a terminal by default.

Add an option to enable colours when stdout is not a terminal.

Fixes: https://bugs.debian.org/742207
---
 codespell.py | 8 ++--
 1 file changed, 6 insertions(+), 2 deletions(-)

diff --git a/codespell.py b/codespell.py
index fdbd5cb..1fd8409 100755
--- a/codespell.py
+++ b/codespell.py
@@ -189,9 +189,13 @@ class FileOpener:
 def parse_options(args):
 parser = OptionParser(usage=USAGE, version=VERSION)
 
+parser.set_defaults(colors = sys.stdout.isatty())
 parser.add_option('-d', '--disable-colors',
-action = 'store_true', default = False,
+action = 'store_false', dest = 'colors',
 help = 'Disable colors even when printing to terminal')
+parser.add_option('-c', '--enable-colors',
+action = 'store_true', dest = 'colors',
+help = 'Enable colors even when not printing to 
terminal')
 parser.add_option('-w', '--write-changes',
 action = 'store_true', default = False,
 help = 'write changes in place if possible')
@@ -478,7 +482,7 @@ def main(*args):
 
 build_dict(options.dictionary)
 colors = TermColors();
-if options.disable_colors:
+if not options.colors:
 colors.disable()
 
 if options.summary:
-- 
1.9.0


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#742308: openssh: [INTL:ru] Russian debconf templates translation

[Yuri Kozlov]

Package: openssh
Version: 1:6.6p1-1
Severity: wishlist
Tags: l10n patch

Dear Maintainer,
*** Please consider answering these questions, where appropriate ***

   * What led up to the situation?
   * What exactly did you do (or not do) that was effective (or
 ineffective)?
   * What was the outcome of this action?
   * What outcome did you expect instead?

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

Russian debconf templates translation is attached.

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

Kernel: Linux 3.2.0-4-amd64 (SMP w/4 CPU cores)
Locale: LANG=ru_RU.UTF-8, LC_CTYPE=ru_RU.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash


ru.po.gz
Description: GNU Zip compressed data

Bug#736119: fix

[David Gilman]

Here's a patch that fixes the problem.
-- 
David Gilman  :DG<
http://gilslotd.com
>From 10ffc72bea237b71823c7f684cbfb2b8a0512be8 Mon Sep 17 00:00:00 2001
From: David Gilman 
Date: Sat, 22 Mar 2014 00:34:17 -0500
Subject: [PATCH] fix indentation in documentation

---
 doc/source/library/apt_pkg.rst | 110 -
 1 file changed, 55 insertions(+), 55 deletions(-)

diff --git a/doc/source/library/apt_pkg.rst b/doc/source/library/apt_pkg.rst
index d6ffaf4..44686d2 100644
--- a/doc/source/library/apt_pkg.rst
+++ b/doc/source/library/apt_pkg.rst
@@ -743,94 +743,94 @@ Resolving Dependencies with :class:`ProblemResolver`
 
 pkg.has_provides and not pkg.has_versions
 
-.. attribute:: id
+   .. attribute:: id
 
-The ID of the package. This can be used to store information about
-the package. The ID is an int value.
+   The ID of the package. This can be used to store information about
+   the package. The ID is an int value.
 
-.. attribute:: name
+   .. attribute:: name
 
-This is the name of the package.
+   This is the name of the package.
 
-.. attribute:: provides_list
+   .. attribute:: provides_list
 
-A list of all package versions providing this package. Each element
-of the list is a triplet, where the first element is the name of the
-provided package, the second element the provided version (empty
-string), and the third element the version providing this package
-as a :class:`Version` object.
+   A list of all package versions providing this package. Each element
+   of the list is a triplet, where the first element is the name of the
+   provided package, the second element the provided version (empty
+   string), and the third element the version providing this package
+   as a :class:`Version` object.
 
-.. attribute:: rev_depends_list
+   .. attribute:: rev_depends_list
 
-An iterator of :class:`Dependency` objects for dependencies on this
-package. The returned iterator is implemented by the class
-:class:`DependencyList`:
+   An iterator of :class:`Dependency` objects for dependencies on this
+   package. The returned iterator is implemented by the class
+   :class:`DependencyList`:
 
-.. class:: DependencyList
+   .. class:: DependencyList
 
-A simple list-like type for representing multiple dependency
-objects in an efficient manner; without having to generate
-all Dependency objects in advance.
+   A simple list-like type for representing multiple dependency
+   objects in an efficient manner; without having to generate
+   all Dependency objects in advance.
 
-.. describe:: list[index]
+   .. describe:: list[index]
 
-Return the item at the position *index* in the list.
+   Return the item at the position *index* in the list.
 
-.. method:: __len__()
+   .. method:: __len__()
 
-The length of the list. This method should not be used
-irectly, instead Python's built-in function :func:`len`
-should be used.
+   The length of the list. This method should not be used
+   irectly, instead Python's built-in function :func:`len`
+   should be used.
 
-.. attribute:: section
+   .. attribute:: section
 
-The section of the package, as specified in the record. The list of
-possible sections is defined in the Policy. This is a string.
+   The section of the package, as specified in the record. The list of
+   possible sections is defined in the Policy. This is a string.
 
-.. attribute:: version_list
+   .. attribute:: version_list
 
-A list of :class:`Version` objects for all versions of this package
-available in the cache.
+   A list of :class:`Version` objects for all versions of this package
+   available in the cache.
 
-**States**:
+   **States**:
 
-.. attribute:: selected_state
+   .. attribute:: selected_state
 
-The state we want it to be, ie. if you mark a package for installation,
-this is :attr:`apt_pkg.SELSTATE_INSTALL`.
+   The state we want it to be, ie. if you mark a package for installation,
+   this is :attr:`apt_pkg.SELSTATE_INSTALL`.
 
-See :ref:`SelStates` for a list of available states.
+   See :ref:`SelStates` for a list of available states.
 
-.. attribute:: inst_state
+   .. attribute:: inst_state
 
-The state the currently installed version is in. This is normally
-:attr:`apt_pkg.INSTSTATE_OK`, unless the installation failed.
+   The state the currently installed version is in. This is normally
+   :attr:`apt_pkg.INSTSTATE_OK`, unless the installation failed.
 
-See :ref:`InstStates` for a list of available states.
+   See :ref:

Bug#742047: nmh: send calls spost with -mhlproc, which spost does not recognize

[Alexander Zangerl]

On Tue, 18 Mar 2014 11:50:15 -0400, Norman Ramsey writes:
>Please check the patch, and if you believe in it, adopt it and pass it
>upstream. 

applied; upload is in the works. upstream has removed the separate spost
since the 1.5 release (its functionality was incorporated into the 
one and only post), so passing the change on won't be overly useful.

regards
az


-- 
Alexander Zangerl + GPG Key 0xB963BD5F (or 0x42BD645D) + http://snafu.priv.at/
Fachbegriffe der Informatik, Debugging:
 Der Mythos vom deterministischen System. -- Lutz Donnerhacke


signature.asc
Description: Digital Signature

Bug#742306: mesa: libwayland-egl1-mesa dependency unsatisfiable on kfreebsd-any

[Mike Miller]

Source: mesa
Version: 10.1.0-3
Severity: normal

Dear Maintainer,

The unstable version of libegl1-mesa-drivers is uninstallable on
kfreebsd-any because of an unsatisfiable

  Depends: libwayland-egl1-mesa (= 10.1.0-3)

This appears to be due to the following git commit:
  
http://anonscm.debian.org/gitweb/?p=pkg-xorg/lib/mesa.git;a=commitdiff;h=3d2e8e66ce9c5c07a73f45ef01b9ade475ef5a13

in which this library package is introduced and built for linux-any, but
is added to the Depends of libegl1-mesa-drivers without any arch
restriction. This dependency should probably be restricted to apply to
linux architectures only.

Thanks,

-- 
mike


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#742305: lvm2: watchfile with signature verification

[David Gilman]

Package: lvm2
Version: 2.02.104-2
Severity: normal
Tags: patch

I've attached a patch which does the following:

- adds a watchfile
- adds upstream's public key so uscan can verify signatures
- fixes the Vcs-Svn field in debian/control (the url was slightly off)

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

Kernel: Linux 3.13-1-amd64 (SMP w/1 CPU core)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) (ignored: LC_ALL 
set to en_US.UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages lvm2 depends on:
ii  dmsetup   2:1.02.83-2
ii  init-system-helpers   1.18
ii  initscripts   2.88dsf-51
ii  libc6 2.18-4
ii  libdevmapper-event1.02.1  2:1.02.83-2
ii  libdevmapper1.02.12:1.02.83-2
ii  libreadline5  5.2+dfsg-2
ii  libudev1  204-8
ii  lsb-base  4.1+Debian12

lvm2 recommends no packages.

Versions of packages lvm2 suggests:
pn  thin-provisioning-tools  

-- no debconf information
Index: debian/control
===
--- debian/control	(revision 968)
+++ debian/control	(working copy)
@@ -6,7 +6,7 @@
 Build-Depends: dpkg-dev (>= 1.16.1~), debhelper (>= 8.1.3~), dh-systemd, automake, libcman-dev (>> 2), libcorosync-dev, libdlm-dev (>> 2), libreadline-gplv2-dev, libselinux1-dev, libudev-dev, openais-dev, pkg-config
 Standards-Version: 3.9.1
 Homepage: http://sources.redhat.com/lvm2/
-Vcs-Svn: svn://svn.debian.org/pkg-lvm/lvm2/trunk/
+Vcs-Svn: svn://svn.debian.org/svn/pkg-lvm/lvm2/trunk/
 Vcs-Browser: http://svn.debian.org/wsvn/pkg-lvm/lvm2/trunk/
 
 Package: lvm2
Index: debian/upstream/signing-key.asc
===
--- debian/upstream/signing-key.asc	(revision 0)
+++ debian/upstream/signing-key.asc	(working copy)
@@ -0,0 +1,390 @@
+-BEGIN PGP PUBLIC KEY BLOCK-
+Version: SKS 1.1.3
+
+mQGiBEAeeEERBADMj5KARh++lgyn6haaj0v28aSV6NEFPhOGNumJQ8buB5UmFX/VoHlkLf07
+d/1F01P/5z+ad9ujJxxNWIOVA6B+K1zjI0wUd2T5iCu/JRacLBYG0B1+oceGiPhvLkHZlNuL
+ZAeAFCthKfRpSFWEYE5DnNsHupVaHBMJhxE1b9G09wCg/01MIY3p0V94YFvuOSyjbDEn2oMD
+/2kZz3t2WLYyUCB8BMg6JCyIXVAfCpTuZXVZipEe/vdHPtTfqtwcK2Fm/wndKbty/wMm1szy
+xGy4yXNykLc3Ly5uIaoJcKZcfkdiuIXXIf55wS0EIhrBykZHqFhuP8fK63zl7SdWjE1c4Yib
+eIuCWFTlZcPS+M/RKmvp3dMPrWZ0BADLsxd8F9YwuD+6OuJU/haRh61fZoTRtDjhH+N92Ibz
+1FwRKqZnZ5EWwLtT25BqlXvIYG3Zxg57Cuz5CKugDGo/xEr2XwXqRAdG8hh4FcrhbvBnsKLo
+/JpacjH/zYgZ5zyGoN12hu+Wwjxgq7E+K7YIW9l6gz8JvM6Q3gp8ZYZ4a7QiQWxhc2RhaXIg
+RyBLZXJnb24gPGFna0ByZWRoYXQuY29tPohFBBMRAgAGBQJA3vzGAAoJEClPqklB2VpK0OoA
+oMh4z9FVCHf2+f8tZ80H9lQjsAu2AJjF64ty8fLk3Jyon1lT1BXagL5SiEUEExECAAYFAkD8
+QMkACgkQdKozh3+HUO5kQgCfeSHeDjKTpaSCa3cKpFSlwFTFL6gAmIGgEq+aizCZvB6KHN3L
+p+TosTaIRQQTEQIABgUCQSKeqAAKCRCf7gTl01MRFQHXAJiWqVfg/V7FK6kXddDdnOV47+4p
+AJ0ZtWJf99UXbsQk7W8kPhCZ6mLm8IhFBBMRAgAGBQJBQb+yAAoJEOu9/Z+XFhuTmgcAl2bJ
+aTFuopHci4gVo0llnP0aBDIAniuVTWm72g6kGbXAlPambsZlMuH1iEYEEBECAAYFAkAeexcA
+CgkQxTtbRvSTu0V56wCghTWL+uT+szDAiU06N8xaulc5+jIAnilNUnMxIJlWxvi3NJM93Oa5
+wCgniEYEEBECAAYFAkDf6dYACgkQ1DyzBZX+yjSoNACfWBk9TG0hMaxD/MxCxz+XTAlA7VIA
+nip9WiJvTLvt8IQdlb08ECyeO6fxiEYEEBECAAYFAkDf7WAACgkQ9ijrk0dDIGzyTACgw9pF
+A6/8xYzslg/DpxfUO8SKwmsAn0QGYdwohgUVLqc2d8LHgkw9zWcGiEYEEBECAAYFAkDghLUA
+CgkQTZFdXToxYe2S5ACfaSwUuTaZCvMlHxd30uUaJ7Wfzi8AoKDvS+yLSOwuJbRJWjgmlxny
+4cH+iEYEEBECAAYFAkDisxAACgkQR47eFMOy/N7L5gCfZ+VBL6xkfmd4IxuOrkUCfq6glX4A
+n1HBbgmXMCSn9payOidJs0sCHD96iEYEEBECAAYFAkEC364ACgkQLPrIaE/xBZBaXwCcDsfS
+1kg0fPRB6FiWfhZjbaRQbcgAoK6Sw1NOQEfvS1Bx6rdhmwFjwZ1EiEYEEBECAAYFAkED1A8A
+CgkQriZpaaIa1PlT/gCg0XYOGNbyp8se7z6YCs7yvzZ2PqMAoMoKrvunJWUm3UEfkBAVhCFi
+/rvOiEYEEBECAAYFAkEFKxIACgkQoZoDG785uj1dMQCZAZns/SG9h8oAhiYnXyng3gAwQkEA
+n0WijpQuq5PztImXqLw6i3p95qKwiEYEEBECAAYFAkEGIMkACgkQ3aHJRGAHDPcnZwCgiYrO
+cifV2Sxa53me+ePHlgeFcU8An15IMZ6mVsDKF+ZcYLVmG2dRRQ0OiEYEEBECAAYFAkEKrN0A
+CgkQWTaspVOQWgHA3wCgkq9K+vp25l/RA7W6+a8f5+vLr28AnRWNks9xJ+AxySh7SLKfqGPO
+TxkjiEYEEBECAAYFAkESC54ACgkQm8RmNn5+yG5QSgCcCWEhHy+AWhPEZ/UDfICZCik3dMoA
+oNZmlk/ElBWg//3C5F/6A6ztlhwFiEYEEBECAAYFAkEXWpMACgkQ0Ewl/uDglgHzJgCgwvcK
+bOYesLIr5a24QzKTQwx1Ee8AoKLsSBJbj/3CFoSPFtaW2qXkPIiBiEYEEBECAAYFAkEZWYAA
+CgkQYzuFKFF44qV4fQCgrdJuLt8djHT0ru+bxHR2DJmqSGcAoKaw6uY4vxpr/tRzdSCygx9Y
+YiDiiEYEEBECAAYFAkEaDMsACgkQsmftqy3Ycf4dcACfXBOib5Pawc1QYMOYV7pM8lttRRsA
+niXSj1ePEi4YhE8IhWq8lHxHWrRniEYEEBECAAYFAkEgtIIACgkQKRs727/VN8tWkwCeMFKb
+vjc4tWZTosw0Ki/UYn1huNwAoJPmFphTF0m4k3iAAMtBZ91cZfKoiEYEEBECAAYFAkErc6IA
+CgkQ1vr63ZUvP/9tOACg9vMmp/A6MlJ87+eM4Kf4ErDP+EcAoLs0dsRXUocFHPMj+zhDV7NT
+qMv1iEYEEBECAAYFAkE6Rx0ACgkQCmLlNDenkUlbxQCfezsDjKFQutsgHP064Orka4eAIu8A
+oJHvtLJ+Kj/qTPy1VMHiQvWTiWK+iEYEEBECAAYFAkFCeTkACgkQ+wPnfyoZ1wfWTACeOZMa
+GjX0I1+J6IiI1/CCmJ4lH5oAnjcoBFb1QUilIiFSgMMm9nL6Jp+qiEYEEBECAAYFAkIei8AA
+CgkQIJm2TL8VSQvVDQCgtQaNGMR0Bx1y/4Va+CIz+233r+UAoITU1v+Xj58d0fPqt0m5PbY+
+fEoLiEYEEBECAAYFAkIfczUACgkQNLbGuU6oShJqEwCffkDRlUGgrQBJzAciUFdDJMknsfEA
+nigDg0

Bug#741875: aptitude: [INTL-it] Updated Italian translation of aptitude po4a docs

[Daniel Hartwig]

Control: tags -1 + pending

On 17 March 2014 03:34, Beatrice Torracca  wrote:
> Package: aptitude
> Version: 0.6.10-1
> Severity: wishlist
> Tags: l10n patch
>
> Hello!
>
> This is the updated .po file with the Italian translation of aptitude
> po4a docs (aptitude-doc-it and man pages).
>
> I did (try to) subit a similar bug several hours ago, but I think I made
> some mistake. I do apologize in advance if this bug gets "duplicated".
>
> Please include the updated translation in your next upload.
>

Thank you.


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#741719: binutils-avr: diff for NMU version 2.23.1-2.1

[Eric Dorland]

tags 741719 + pending
thanks

Dear maintainer,

I've prepared an NMU for binutils-avr (versioned as 2.23.1-2.1) and
uploaded it to DELAYED/10. Please feel free to tell me if I
should delay it longer.

Regards.

-- 
Eric Dorland 
ICQ: #61138586, Jabber: ho...@jabber.com

diff -Nru binutils-avr-2.23.1/debian/changelog binutils-avr-2.23.1/debian/changelog
--- binutils-avr-2.23.1/debian/changelog	2013-10-23 03:37:18.0 -0400
+++ binutils-avr-2.23.1/debian/changelog	2014-03-21 21:58:33.0 -0400
@@ -1,3 +1,11 @@
+binutils-avr (2.23.1-2.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Drop unnecessary build deps on autoconf and automake1.9. (Closes:
+#741719)
+
+ -- Eric Dorland   Fri, 21 Mar 2014 21:58:12 -0400
+
 binutils-avr (2.23.1-2) unstable; urgency=low
 
   * Remove duplicated source
diff -Nru binutils-avr-2.23.1/debian/control binutils-avr-2.23.1/debian/control
--- binutils-avr-2.23.1/debian/control	2013-07-07 05:00:30.0 -0400
+++ binutils-avr-2.23.1/debian/control	2014-03-21 21:57:19.0 -0400
@@ -3,7 +3,7 @@
 Priority: extra
 Maintainer: Hakan Ardo 
 Standards-Version: 3.0.1.1
-Build-Depends: autoconf (>= 2.13), automake1.9, bison, flex, gettext, texinfo, binutils (>= 2.9.5.0.12), gcc (>= 2.95.2), debhelper (>= 5), tar (>= 1.13.18), bzip2, findutils(>=4.2.31)
+Build-Depends: bison, flex, gettext, texinfo, binutils (>= 2.9.5.0.12), gcc (>= 2.95.2), debhelper (>= 5), tar (>= 1.13.18), bzip2, findutils(>=4.2.31)
 
 Package: binutils-avr
 Section: devel


signature.asc
Description: Digital signature

Bug#741051: krb5-config's krb5.conf template is crufty

[Russ Allbery]

Sam Hartman  writes:

> I wonder if we can support /etc/krb5.conf.d.  I guess the big question
> is whether Heimdal supports that.

I just checked, and so far as I can tell, it does not.

-- 
Russ Allbery (r...@debian.org)   


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#726872: Lock screen does nothing

[Erik de Castro Lopo]

althaser wrote:

> Could you please still reproduce this issue with newer gnome-shell version
> like 3.8.4-5+b1 ?
> 
> I'm running 3.8.4-5+b1 here and lock is working fine here. I don't even
> have gnome-screensaver installed.

I no longer use gnome-shell. Free free to close this if no one else can
reproduce it.

Cheers,
Erik
-- 
--
Erik de Castro Lopo
http://www.mega-nerd.com/


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#726872: Lock screen does nothing

[Erik de Castro Lopo]

althaser wrote:

> Could you please still reproduce this issue with newer gnome-shell version
> like 3.8.4-5+b1 ?
> 
> I'm running 3.8.4-5+b1 here and lock is working fine here. I don't even
> have gnome-screensaver installed.

I no longer use gnome-shell. Free free to close this if no one else can
reproduce it.

Cheers,
Erik
-- 
--
Erik de Castro Lopo
http://www.mega-nerd.com/


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#723656: bug 723656 - xen hvc0/ipmi console hangs

[Todd Fleisher]

I have this happening in Ubuntu precise also. When I upgraded from 12.04.1 to 
12.04.4 it looks like my ipmi/serial/hvc0 console stopped working and the last 
message is: (XEN) Platform timer is 14.318MHz HPET

From /etc/default/grub:
GRUB_DEFAULT="Xen 4.1-amd64"
GRUB_HIDDEN_TIMEOUT=0
GRUB_HIDDEN_TIMEOUT_QUIET=true
GRUB_TIMEOUT=10
GRUB_DISTRIBUTOR=`lsb_release -i -s 2> /dev/null || echo Debian`
GRUB_CMDLINE_LINUX_DEFAULT=""
GRUB_CMDLINE_LINUX="console=tty1 console=hvc0 earlyprintk=xen"
GRUB_CMDLINE_XEN="loglvl=all guest_loglvl=all com1=115200,8n1,0x2f8,5 
console=tty1,com1"


Package: xen-hypervisor-4.1-amd64
State: installed
Automatically installed: no
Version: 4.1.5-0ubuntu0.12.04.3
Priority: optional
Section: universe/kernel
Maintainer: Ubuntu Developers 
Architecture: amd64
Uncompressed Size: 808 k
Recommends: xen-utils-4.1
Suggests: xen-docs-4.1
Provides: xen-hypervisor, xen-hypervisor-4.1, xen-hypervisor-amd64
Description: Xen Hypervisor on AMD64
 The hypervisor is the "core" for XEN itself.  It gets booted by the boot 
loader and controls cpu
 and memory, sharing them between your administrative domain (Domain 0) and the 
virtual guest
 systems. 
 
 In order to boot a XEN system along with this package you also need a kernel 
specifically crafted
 to work as the Domain 0, mediating hardware access for XEN itself.


--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#742245: how-can-i-help should have --gift interface esp. for newbies.

[shirish शिरीष]

in-line :-

On 3/22/14, Tomasz Nitecki  wrote:
> Hey,



> It is an interesting idea. In version 5 I've added an option to filter
> out selected types of opportunities (requested in #738169). You can
> filter everything but 'gift bugs' by using that (man how-can-i-help for
> details). Unfortunately, this option requires someone to configure it to
> make it work that way. So that is not entirely what you are asking for.

I saw the man-page. For newbies, they might  or might not discover the
man-page.

> How about we add '--' or '--show:' option that would
> limit output to selected types? It won't need much more work, but it
> will be more usable for everyone.

That's exactly what I need.  Also document it in how-can-i-help --help
which would probably be run by bunch of newbie number of times so the
easier it is, the more likely that people would start with something
as they would be more focussed on fixing a certain type of bug/s.

>
>> This way a newbie contributor can start in a jiffy. Also it should
>> have some difference in the bandwidth used as well.
>
> how-can-i-help uses (downloads and caches) static dump file that
> contains all the opportunities, so the bandwidth usage will remain
> unchanged regardless of the options used. However, making new
> contributor life easier is always most welcome :)
>
>
>> I did two invocations but neither worked :-
>>
>> $how-can-i-help --gift
>> $how-can-i-help | grep gift
>> In fact the first one showed me the following :-
>>
>> $ how-can-i-help --gift
>> /usr/bin/how-can-i-help:71:in `': invalid option: --gift
>> (OptionParser::InvalidOption)
>
> The first one is simply unsupported. The second one would require us to
> place 'gift' marker on each line and that would be redundant in normal
> operation mode.
>
>
> Regards,
> T.

-- 
  Regards,
  Shirish Agarwal  शिरीष अग्रवाल
  My quotes in this email licensed under CC 3.0
http://creativecommons.org/licenses/by-nc/3.0/
http://flossexperiences.wordpress.com
065C 6D79 A68C E7EA 52B3  8D70 950D 53FB 729A 8B17


--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#717076: libjpeg draft resolution

[Russ Allbery]

Kurt Roeckx  writes:

> My understanding is that the point of virtual packages is so that
> several *can* provide it.  But you're now telling 1 package that it
> can't do that, while you instead could say only one (other) package can
> do it in this case.

That's one use of virtual packages.  However, that's not the primary use
of virtual packages for -dev packages.  As a general rule, we do not want
multiple packages in the archive providing the same -dev package name,
because that leads to nondeterministic builds for any package that
Build-Depends on the virtual -dev package name, and nondeterministic
builds are bad.

Rather, for -dev packages, it's more typical to have a virtual package
with a single provider at any given point.  This is a simpler version of
the mechanism used by, e.g., gcc-defaults or boost-defaults, avoiding
maintaining as separate source package when there's no need to provide
additional supporting files like symlinks.  It allows multiple versions of
the package to be in the archive at the same time but one of them
designated as the "default" version, using the virtual package Provides,
for the purposes of building other packages.  This allows packages that
actually need a specific version to Build-Depend on that specific version,
while moving most of the archive to a new version by moving the Provides
and then scheduling binNMUs.

-- 
Russ Allbery (r...@debian.org)   


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#741930: reportbug: add current init system information

[Michael Biebl]

Am 21.03.2014 22:19, schrieb Sandro Tosi:

> a proper way to retrieve the init running is provided :)> 

- systemd
The canonical check for systemd being PID 1 is
[ -d /run/systemd/system ]
See also man 3 sd_booted and [0]

- upstart
For upstart the canonical check is defined in /lib/lsb/init-functions as
init_is_upstart() which checks for initctl and parses the output of the
"initctl version"



Michael

[0] http://cgit.freedesktop.org/systemd/systemd/commit/?id=66e411811b8090

-- 
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#717076: libjpeg draft resolution

[Kurt Roeckx]

On Fri, Mar 21, 2014 at 11:38:15PM +, Ian Jackson wrote:
> In general I worry that your interpretation of resolution texts
> focuses far too much on the exact words used, and far too little on
> the substance of the underlying issues.
> 
> In this particular case we have two packages both of which want to
> claim the libjpeg-dev virtual package name, which for technical
> reasons ought to be provided by only one of them.  Clearly this is a
> question of overlapping jurisdictions.

My understanding is that the point of virtual packages is so that
several *can* provide it.  But you're now telling 1 package that
it can't do that, while you instead could say only one (other)
package can do it in this case.

The difference in my view is that you decide between how a set of
related packages should interact with each other or that you
prevent 1 package from following the normal rules.  I have no
problem interpreting the first case as falling under 6.1(2),
but I'm not yet sure about the second.

> The fact that the resolution to this matter of overlapping
> jurisdictions will result in specific changes having to be made to one
> or more packages does not mean that the decision is about overruling
> the maintainer of the "losing" package.  _Any_ decision about
> overlapping jurisdictions will necessarily involve directing that
> certain changes be made to one or more packages which their respective
> maintainers will not be happy with.
>
> I.e. your interpretation as I understand it so far entirely
> eviscerates the TC's power to rule in case of overlapping
> jurisdictions.  In your view as you have presented it here it appears
> the TC could say something vague and abstract with 1:1 but if we
> actually want the losing maintainer to give up the virtual package
> name we will need to vote again with 3:1.

I have to guess that as ussual we don't understand each other yet,
and probably have a different way of looking at things.  And I
guess I'm ussually going to try suggesting things so that it's
unlikely that people doubt that you do have the power to do
something.

As ussual this was not an official interpreatation of the constituion
yet and I do welcome discussions about such topics, so that we can
find a consensus what it says in case of doubt.


Kurt


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#624122: Hash Sum mismatch

[david]

On Fri, Mar 21, 2014 at 08:53:23PM +0100, Johannes Stezenbach wrote:
> I'm also seeing the Hash Sum mismatch often since about a week ago,
> maybe since "[UPGRADE] apt:amd64 0.9.16 -> 0.9.16.1" (sid) but I did not
> downgrade to confirm.  However, it seems the issue is caused
> by xz decompressor truncating the files.  For example:

I botched liblzma support in 0.9.16, which has a bug (already fixed in
git) truncating xz compressed files¹, which will let you end up with this
error message as well, as an uncomplete file is obviously not matching
the expected hashsum – so also not related to the issue initially
discribed, just another way of seeing the same error message.

¹ only certain files – aka those containing 4096 bytes of lzma/xz
content which produce no output by themselves and need at least another
round of 4096 input bytes…


Of course non of our testcases triggered this, many xz in the archive
are fine as well and pdiffs usually take care of hidding all instances
which would trigger it… I love these kind of bugs… sorry about that.


Best regards

David Kalnischkies


signature.asc
Description: Digital signature

Bug#734814: libapache2-mpm-itk: can no longer set group to one that the user does not belong to

[brian m. carlson]

On Mon, Feb 03, 2014 at 09:09:06PM +0100, Steinar H. Gunderson wrote:
> On Fri, Jan 10, 2014 at 10:13:45PM +, brian m. carlson wrote:
> > Let me provide you with a testcase.  I can't quite get it to hang in the
> > same way, but I definitely get the same error message, so hopefully this
> > will help.  I'll try to get all the steps right here, but I may have
> > forgotten some.  Feel free to substitute bmc for some other user.
> 
> That's a very complicated test case. :-) Do you think you could try to narrow
> it down a bit?
> 
> So as far as I can see, in the case that doesn't involve git and whatnot,
> this works just like it should.

Okay.  Here's what the issue is.  If the main vhost defaults to (or is
explicitly set to) the default user of www-data, and a LocationMatch
region sets it to a different value and a CGI runs under it, the error
will occur.  That seems to be what triggers it for me.  If you set the
main vhost to the same user as the LocationMatch region, it works just
fine.

-- 
brian m. carlson / brian with sandals: Houston, Texas, US
+1 832 623 2791 | http://www.crustytoothpaste.net/~bmc | My opinion only
OpenPGP: RSA v4 4096b: 88AC E9B2 9196 305B A994 7552 F1BA 225C 0223 B187


signature.asc
Description: Digital signature

Bug#738811: handbrake: crashes after source DVD is selected

[Reinhard Tartler]

On Fri, Mar 21, 2014 at 10:48 AM, Christoph Berg  wrote:
> Re: Fabian Greffrath 2014-02-25 
> <1393319738.4516.0.ca...@kff50.ghi.rwth-aachen.de>
>> Am Dienstag, den 25.02.2014, 09:51 +0100 schrieb Jan Korous:
>> > That's funny. I didn't notice this option. As soon as I unchecked the
>> > box (and started using libdvdread) it works. So the problem was in
>> > dvdnav actually (or at least according to the checker box label).
>>
>> Let's hope new new releases currently prepared at VLC bring some
>> improvement.
>
> As I just wrote in #700541, I was having trouble encoding DVDs with
> 0.9.9+dfsg-2~2.gbpa4c3e9. The problem rather resembles this bug,
> though: it just crashes after reading the DVD. That's fixed with
> 0.9.9+svn6032+dfsg1-1.

did you test with both "dvdnav" and "libdvdread"?

Reinhard


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#742287: Gitg -> SIGSEGV

[Dmitry Smirnov]

Hi Federico,

At the moment I can only recommend to use gitg-0.2.7 from backports.

Thank you.

-- 
Regards,
 Dmitry Smirnov
 GPG key : 4096R/53968D1B

---

If forty million people say a foolish thing it does not become a wise one.
-- W. Somerset Maugham, 1901


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

Bug#740893: libjs-jquery-hotkeys regression (was: python-coverage regression)

[Ben Finney]

On 21-Mar-2014, Thomi Richards wrote:
> I hope you don't mind my pinging you like this.

No problem, you're doing so in my capacity as a Debian package maintainer,
so this address is fine for that.

> I've discovered a regression in python-coverage packages in Ubuntu
> Trusty, and narrowed the problem down to a the jquery.hotkeys package in
> Debian. I filed a bug here:
> 
> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=740893

Right, I think that bug report is correct. I'm replying onto that bug
report to keep the discussion where it (IMO) belongs for now.

> ...and was hoping I could bring this to your attention, with the hopes of
> getting it fixed in time for the Trusty release.

Isn't the problem best fixed by reverting the ‘libjs-jquery-hotkeys’
package to the working “0.8” version? The newer version breaks dependent
packages, so the right place to apply pressure it seems to me is by
rejecting that newer code from Debian until it works again.

> I'm not sure what the best solution is. I've identified the last revision
> of that package that worked well with coverage.py. One option is to
> revert the debian package, but presumably those changes were made for a
> reason, and I'd hate to break other projects. Another option is to use
> the vendorised libraries in upstart coverage.py.

Sure. It's easy for me to identify the location for a solution in a package
which I'm not really involved with, so my position is not the only one to
consider.

> Please let me know if I can do anything to help out.

Have you got any feedback from the Debian package maintainer of
‘libjs-jquery-hotkeys’ to find out whether rolling back to version “0.8” is
feasible?

Have you worked with that package maintainer to report the bug upstream (it
is the package maintainer's responsibility)? Has the upstream developer 

-- 
 \ “Too many pieces of music finish too long after the end.” —Igor |
  `\   Stravinskey |
_o__)  |
Ben Finney 


signature.asc
Description: Digital signature

Bug#717076: libjpeg draft resolution

[Andreas Barth]

* Ian Jackson (ijack...@chiark.greenend.org.uk) [140322 00:39]:
> (resending because of some 8-bit header damage)
> 
> Kurt Roeckx writes ("Bug#717076: libjpeg draft resolution"):
> > So if you really want to prevent using a supermajority, I suggest
> > you write is so that you at least don't mention the other package
> > by name but make it more general.
> 
> Seriously ?
> 
> > I also suggest you don't mention the name libjpeg-dev directly but
> > instead use words to describe it so that it still applies when it
> > needs to be renamed for whatever reason.

> In this particular case we have two packages both of which want to
> claim the libjpeg-dev virtual package name, which for technical
> reasons ought to be provided by only one of them.  Clearly this is a
> question of overlapping jurisdictions.

IMHO this is even one of the examples of the constitution for
overlapping jurisdiction:
| for example, [...] about who should be the maintainer for a package



Andi


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#733362: gstreamer0.10: FTBFS: grammar.tab.c:1819:7: error: too few arguments to function 'priv_gst_parse_yylex'

[Tobias Hansen]

tag 733362 + patch fixed-upstream
forwarded 733362 https://bugzilla.gnome.org/show_bug.cgi?id=706462
thanks

Should be fixed by the upstream patch in
https://bugzilla.gnome.org/show_bug.cgi?id=706462

See also
https://bugzilla.gnome.org/show_bug.cgi?id=705401
which has the same compile error as reported here and is marked as
duplicate of 706462.


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#717076: libjpeg draft resolution

[Ian Jackson]

(resending because of some 8-bit header damage)

Kurt Roeckx writes ("Bug#717076: libjpeg draft resolution"):
> So if you really want to prevent using a supermajority, I suggest
> you write is so that you at least don't mention the other package
> by name but make it more general.

Seriously ?

> I also suggest you don't mention the name libjpeg-dev directly but
> instead use words to describe it so that it still applies when it
> needs to be renamed for whatever reason.

I think this is contrary to the requirement that the resolution be
clear.  Given that I think we're not going to be short a 3:1 majority
on this, I doubt it really matters in this case, but I'm disappointed.

In general I worry that your interpretation of resolution texts
focuses far too much on the exact words used, and far too little on
the substance of the underlying issues.

In this particular case we have two packages both of which want to
claim the libjpeg-dev virtual package name, which for technical
reasons ought to be provided by only one of them.  Clearly this is a
question of overlapping jurisdictions.

The fact that the resolution to this matter of overlapping
jurisdictions will result in specific changes having to be made to one
or more packages does not mean that the decision is about overruling
the maintainer of the "losing" package.  _Any_ decision about
overlapping jurisdictions will necessarily involve directing that
certain changes be made to one or more packages which their respective
maintainers will not be happy with.

I.e. your interpretation as I understand it so far entirely
eviscerates the TC's power to rule in case of overlapping
jurisdictions.  In your view as you have presented it here it appears
the TC could say something vague and abstract with 1:1 but if we
actually want the losing maintainer to give up the virtual package
name we will need to vote again with 3:1.

Please reconsider.

Thanks,
Ian.


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#742303: basenji: Crashes on adding a new volume to the catalog

[Guillermo Espertino]

Package: basenji
Version: 1.0.1-3
Severity: grave
Justification: renders package unusable

Dear Maintainer,

The current version of basenji in debian testing repos crashes every time I try
to add a new volume to the catalog, rendering the program useless.
I tried deleting the preferences directory and starting a new catalog, but it
keeps crashing.
The program also crashes when I try to enter to the preferences.

The previous version worked fine, no crashes.



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

Kernel: Linux 3.13-1-amd64 (SMP w/4 CPU cores)
Locale: LANG=es_AR.utf8, LC_CTYPE=es_AR.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages basenji depends on:
ii  libc6   2.18-4
ii  libdbus-glib2.0-cil 0.6.0-1
ii  libdbus2.0-cil  0.8.0-1
ii  libglib2.0-02.38.2-5
ii  libglib2.0-cil  2.12.10-5
ii  libgnome-desktop-2-17   2.32.1-2
ii  libgtk2.0-0 2.24.22-1
ii  libgtk2.0-cil   2.12.10-5
ii  libmono-cairo4.0-cil3.0.6+dfsg2-11
ii  libmono-corlib4.5-cil   3.0.6+dfsg2-11
ii  libmono-posix4.0-cil3.0.6+dfsg2-11
ii  libmono-sharpzip4.84-cil3.0.6+dfsg2-11
ii  libmono-sqlite4.0-cil   3.0.6+dfsg2-11
ii  libmono-system-core4.0-cil  3.0.6+dfsg2-11
ii  libmono-system-data4.0-cil  3.0.6+dfsg2-11
ii  libmono-system-xml4.0-cil   3.0.6+dfsg2-11
ii  libmono-system4.0-cil   3.0.6+dfsg2-11
ii  librsvg2-common 2.40.0-1
ii  libtaglib2.1-cil2.1.0.0-3
ii  mono-runtime3.0.6+dfsg2-11
ii  udisks  1.0.5-1

basenji recommends no packages.

basenji suggests no packages.

-- no debconf information


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#731350: gnome-shell: Numlock not properly working since 3.8

[althaser]

Hey Steven,

I am running gnome-shell-3.8.4-5+b1 here and I have numlockx installed but
I can't reproduce this issue.

Could you please still reproduce it with 3.8.4-5+b1 ?

cheers,
althaser

Bug#730401: gnome-shell: clock with date and seconds is wrong when you, lock the screen

[althaser]

Hey Davide,

I am using gnome-shell 3.8.4-5+b1 and I can't reproduce this issue here.

Do you still have the issue ?

cheers,
althaser

Bug#726939: Laptop function keys for LCD backlight not working

[althaser]

Hey Erik,

Do you have backlight driver running ?

I have a samsung laptop and my backlight keys is working fine due to
samsung_laptop module.

running gnome-shell-3.8.4-5+b1 here.

cheers,
althaser

Bug#685506: Problem with *.zip archives

[Joachim Breitner]

Hi,

Am Freitag, den 21.03.2014, 23:31 +0100 schrieb Andreas Tille:
> So, we actually are using the same command with different results which
> is really strange.

so starting in an empty directory (maybe that makes a difference), if
you do

$ apt-get source mothur
$ cd mothur-1.33.0+dfsg/
$ path-to-current/devscripts/scripts/uscan.pl --force-download --repack 
--repack-compression xz
$ tar taf ../Mothur.1.33.3.tar.xz|wc -l
$ tar taf ../mothur_1.33.3+dfsg.orig.tar.xz|wc -l

what do you get?

Greetings,
Joachim


-- 
Joachim "nomeata" Breitner
Debian Developer
  nome...@debian.org | ICQ# 74513189 | GPG-Keyid: 4743206C
  JID: nome...@joachim-breitner.de | http://people.debian.org/~nomeata


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

Bug#742295: sopwith: segmentation fault in single player mode (S)

[Kenneth Pronovici]

On Fri, Mar 21, 2014 at 5:15 PM, Markus Koschany  wrote:
> On 21.03.2014 22:26, Jesse Smith wrote:
>> So far I have not been able to reproduce the bug, however I suspect I
>> know what the problem is. The Sopwith makefile includes a flag for
>> optimization (-O2).  Recent versions of the GCC compiler (version 4.7,
>> 4.8) have changed the way code gets optimized and I have seen it cause a
>> couple of games to crash at start-up.
>
> Thank you very much for your quick response. You are right, the optimization 
> is causing this
> problem. On Debian -O2 is the default optimization flag and gcc 4.8 still the 
> default compiler.
> With your Makefile and without any additional compiler flags, I can't 
> reproduce a crash either.
>
> The solution for Debian is to add this line to debian/rules:
>
> export DEB_BUILD_OPTIONS=noopt
>
> and sopwith will be built with -O0 optimization. I can confirm that this 
> solves the issue.

I'll put together a new package this weekend.

KEN


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#373734: Debian #373734 Re: pgf: Typos in user guide

[Hilmar Preusse]

tags 373734 + fixed-upstream
# fixed in CVS up there
reassign 373734 texlive-pictures-doc
stop

On 19.03.14 Francesco Poli (invernom...@paranoici.org) wrote:

> OK, I've just re-read the relevant part of section _Extended Color
> Support_ ...
> 
> It's definitely possible that you are right: the correct fix could be
> 
> s/foo.!50!white!25!black/foo.!25!white!25!black/
> 
Bug manipulation.

Hilmar
-- 
sigmentation fault


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#742263: squeeze-pu: package lcms2/2.2+git20110628-2.2+deb7u1

[Thomas Weber]

On Fri, Mar 21, 2014 at 04:24:24PM +, Adam D. Barratt wrote:
> Control: tags -1 = wheezy confirmed
> Control: retitle -1 wheezy-pu: package lcms2/2.2+git20110628-2.2+deb7u1
> 
> On 2014-03-21 12:21, Thomas Weber wrote:
> >Package: release.debian.org
> >Severity: normal
> >Tags: squeeze
> 
> I don't think that's what you meant. ;-)

Oops, copy'n paste error. 

> [...]
> >please accept an upload of lcms2 2.2+git20110628-2.2+deb7u1 to
> >wheezy-proposed
> >updates.
> >The update fixes a minor security issue in stable (#714529,
> >CVE-2013-4160). DSA considers the issue to be not worth a security
> >update:
> 
> The security team are not DSA... in any case, please go ahead.

Oh my, that was not my day when writing the bug report.

Thanks for the green light, nonetheless. 

Thomas


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#726872: Lock screen does nothing

[althaser]

Hey,

Could you please still reproduce this issue with newer gnome-shell version
like 3.8.4-5+b1 ?

I'm running 3.8.4-5+b1 here and lock is working fine here. I don't even
have gnome-screensaver installed.

cheers,
althaser

Bug#726574: Moving and resizing windows is hitching

[althaser]

Hey dAgeCKo,

Could you please still reproduce this issue with newer gnome-shell version
like 3.8.4-5+b1 ?

cheers,
althaser

Bug#712947: gnome-shell: Long delay before power down happens

[Alan Chandler]

On 21/03/14 21:06, althaser wrote:

Hey,

Could you please still reproduce this issue with newer gnome-shell 
version like 3.8.4-5+b1 ?


cheers,
althaser




Unfortunately at the moment I need to run Debian Stable on my desktop so 
difficult to do.  I have been running Debian stable for about 6 months 
and have had no occurence of this problem at that version 3.4.2-7




--
Alan Chandler
http://www.chandlerfamily.org.uk


--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#373734: Debian #373734 Re: pgf: Typos in user guide

[Hilmar Preusse]

tags 373734 + fixed-upstream
# fixed in CVS up there
reassign 373734 texlive-pictures-doc
stop

On 19.03.14 Francesco Poli (invernom...@paranoici.org) wrote:

> OK, I've just re-read the relevant part of section _Extended Color
> Support_ ...
> 
> It's definitely possible that you are right: the correct fix could be
> 
> s/foo.!50!white!25!black/foo.!25!white!25!black/
> 
Bug manipulation.

Hilmar
-- 
sigmentation fault


signature.asc
Description: Digital signature

Bug#742295: sopwith: segmentation fault in single player mode (S)

[Jesse Smith]

> 

> Thank you very much for your quick response. You are right, the
> optimization is causing this problem. On Debian -O2 is the default
> optimization flag and gcc 4.8 still the default compiler. With your
> Makefile and without any additional compiler flags, I can't
> reproduce a crash either.
> 
> The solution for Debian is to add this line to debian/rules:
> 
> export DEB_BUILD_OPTIONS=noopt
> 
> and sopwith will be built with -O0 optimization. I can confirm that
> this solves the issue.
> 


That is great, thank you for testing. Since this bug will likely
affect other distributions with recent versions of GCC I will release
an update this weekend that removes the optimizations. We don't really
need to optimize a 30 year old game anyway, everyone's hardware is up
to the task.

Jesse


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#726380: gnome-shell: hitting corner activation points is almost impossibe in dual-monitor setups

[althaser]

Hey Tollef,

are you refering to notification area ? if so it doesnt need the
lower-right corner to show it up, a fast move with mouse at the bottom on
the primary screen it will show up the notification area, or as a
workaround winkey+m.

cheers,
althaser

Bug#701962: libsodium packaging

[Raúl Sánchez Siles]

  Hi László:

El Jueves, 20 de marzo de 2014 16:05:34 László Böszörményi escribió:
> Hi Raúl,
> 
> How is the libsodium packaging stand? You got advices from Alessandro
> Ghedini almost a month ago, but I don't see any reply from you.

  Latest advice from Alessandro was very specific, I updated package on my 
repository and reply him privately shortly after his email. I'd say package is 
in good shape and you can take it from either mentors or my repository [0]

  [0] http://trismegisto.no-ip.org/hg/libsodium-debian

  It's also my intention to move my repo to debian hosting, but no sooner 
there's a real need to do so.

> It would be good to have it updated (due to removed bashism[1]) and
> uploaded to Debian. May I finish the packaging based on your work?
> Make you the maintainer / uploader (based on your wish) while I'd take
> the other position.

  As I think I mentioned before, I have no plans to push this into the archive 
until I see a new upstream release. This said, feel free to take/use/modify 
what's already done, it's free software after all, I'm also open for a 
(preferably mercurial) collab-maint repository .

  I'm curious about what you think the package is missing (beside upstream 
release).

  If you really think [1] is really important I may try a refreshed upstream 
snapshot + mentors upload.

> 
> Regards,
> Laszlo/GCS
> [1]
> https://github.com/jedisct1/libsodium/commit/9b82685f142ca392cc0d4774e33be6
> 570b2139f3


  Regards,

-- 
 Raúl Sánchez Siles
->Proud Debian user<-
Linux registered user #416098

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

Bug#735156: [Icedove] no mail notifications

[Carsten Schoenert]

Hello Francesco,

On Fri, Mar 21, 2014 at 10:56:06PM +0100, Francesco Muzio wrote:
> But the problem is a regression. On a modern desktop environment any
> notification are showed on a centralized manager. Older version of Iceweasel
> (and Icedove <= 17) do this.

It depends on the point of view. There will be reasons why Mozilla has
removed the notification support via libnotify.

> I don't know the details but on new versions of mozilla software lack the
> libnotify support.
> this bug affect also thunderbird on ubuntu
> https://bugzilla.mozilla.org/show_bug.cgi?id=853104#c18

That's the point and the URL you posted is helpfull for fixing this bug
report. But we have to discuss if we use the Ubuntu fix or if it maybe
breaks somthing, I would say it's o.k. to take the patch from there.

> Trying to fade any doubt: when you say "The notification works here on Gnome
> 3 and KDE." you mean that the notification of a new mail arrived is showed,
> on KDE, in the same position and with same style like a notification of
> completed copy of a big file on the filesystem ?
> 
> On my machine the answer is no. Icedove 24 (unlike 17 and 10) shows in
> autonomous way its notifications.

You are right, I mean the standalone notification from Icedove about new
mails that are arrived. (For me this is enough.)

Regards
Carsten


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#685506: Problem with *.zip archives

[Andreas Tille]

Hi Joachim,

On Fri, Mar 21, 2014 at 11:27:16PM +0100, Joachim Breitner wrote:
> > debian/rules get-orig-source
> > 
> > (which does the same as you above).  BTW, I personally see no point in
> > keeping a non-stripped archive - it is perfectly fine to have only the
> > result of the stripped download.
> > 
> > No idea how I can help you reproducing the behaviour at my side.
> 
> In debian/rules I see no call to “repack”, that might be the reason; but
> I won’t look into the details (what happens with which flags, and why)
> today.

Ahh - you are right, I used the following local change:

$ svn diff
Index: rules
===
--- rules   (Revision 16448)
+++ rules   (Arbeitskopie)
@@ -36,4 +36,4 @@
 # Alternatively you can use
 #  . debian/get-orig-source
 get-orig-source:
-   uscan --verbose --force-download --repack-compression xz
+   uscan --verbose --force-download --repack --repack-compression xz


This also became necessary with the current devscripts implementation.
My original code realised that since some files were removed a
repackaging is simply *required* and thus this option was redundant.

So, we actually are using the same command with different results which
is really strange.

Kind regards

   Andreas.


-- 
http://fam-tille.de


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#685506: Problem with *.zip archives

[Joachim Breitner]

Hi,

Am Freitag, den 21.03.2014, 23:24 +0100 schrieb Andreas Tille:
> Hmmm, that's strange.  At my side the orig.tar.xz is a symlink to the
> other file.  I'm using
> 
> debian/rules get-orig-source
> 
> (which does the same as you above).  BTW, I personally see no point in
> keeping a non-stripped archive - it is perfectly fine to have only the
> result of the stripped download.
> 
> No idea how I can help you reproducing the behaviour at my side.

In debian/rules I see no call to “repack”, that might be the reason; but
I won’t look into the details (what happens with which flags, and why)
today.

Greetings,
Joachim


-- 
Joachim "nomeata" Breitner
Debian Developer
  nome...@debian.org | ICQ# 74513189 | GPG-Keyid: 4743206C
  JID: nome...@joachim-breitner.de | http://people.debian.org/~nomeata


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

Bug#685506: Problem with *.zip archives

[Andreas Tille]

Hi,

On Fri, Mar 21, 2014 at 10:42:35PM +0100, Joachim Breitner wrote:
> Did you check Mothur.1.33.3.tar.xz or mothur_1.33.3+dfsg.orig.tar.xz – a
> mistake I also did earlier today:

see below ...
 
> $ apt-get source mothur
> Paketlisten werden gelesen... Fertig
> Abhängigkeitsbaum wird aufgebaut.   
> Statusinformationen werden eingelesen Fertig
> HINWEIS: »mothur«-Paketierung wird betreut im »Svn«-Versionsverwaltungssystem 
> auf:
> svn://anonscm.debian.org/debian-med/trunk/packages/mothur/trunk/
> Es müssen 918 kB an Quellarchiven heruntergeladen werden.
> Holen: 1 http://http.debian.net/debian/ sid/main mothur 1.33.0+dfsg-1 (dsc) 
> [2.103 B]
> Holen: 2 http://http.debian.net/debian/ sid/main mothur 1.33.0+dfsg-1 (tar) 
> [902 kB]
> Holen: 3 http://http.debian.net/debian/ sid/main mothur 1.33.0+dfsg-1 (diff) 
> [13,9 kB]
> Es wurden 918 kB in 0 s geholt (1.095 kB/s). 
> dpkg-source: Information: mothur wird nach mothur-1.33.0+dfsg extrahiert
> dpkg-source: Information: mothur_1.33.0+dfsg.orig.tar.xz wird entpackt
> dpkg-source: Information: mothur_1.33.0+dfsg-1.debian.tar.xz wird entpackt
> dpkg-source: Information: makefile.patch wird angewandt
> dpkg-source: Information: no_lcurses.patch wird angewandt
> dpkg-source: Information: drop_sse_option.patch wird angewandt
> dpkg-source: Information: catchall_fix.patch wird angewandt
> dpkg-source: Information: build_without_tty.patch wird angewandt
> dpkg-source: Information: uchime_link_dynamically wird angewandt
> dpkg-source: Information: uchime_hardening.patch wird angewandt
> dpkg-source: Information: spelling.patch wird angewandt
> /tmp $ cd mothur-1.33.0+dfsg/
> /tmp/mothur-1.33.0+dfsg $ ~/build/devscripts/devscripts/scripts/uscan.pl 
> --verbose --force-download --repack --repack-compression xz
> -- Scanning for watchfiles in .
> -- Found watchfile in ./debian
> -- In debian/watch, processing watchfile line:
>opts=dversionmangle=s/(\+dfsg|[~\+]repack)// 
> http://www.mothur.org/wiki/Download_mothur
> /w/images/.*/.*/Mothur\.([\d\.]+)\.zip
> -- Found the following matching hrefs:
>  /w/images/6/65/Mothur.1.33.3.zip (1.33.3)
>  /w/images/9/99/Mothur.1.32.1.zip (1.32.1)
>  /w/images/b/bc/Mothur.1.31.2.zip (1.31.2)
>  /w/images/d/d3/Mothur.1.30.2.zip (1.30.2)
>  /w/images/a/a5/Mothur.1.29.2.zip (1.29.2)
>  /w/images/6/68/Mothur.1.28.0.zip (1.28.0)
>  /w/images/c/cb/Mothur.1.27.0.zip (1.27.0)
>  /w/images/2/20/Mothur.1.26.0.zip (1.26.0)
>  /w/images/7/7b/Mothur.1.25.1.zip (1.25.1)
>  /w/images/0/09/Mothur.1.24.1.zip (1.24.1)
>  /w/images/3/33/Mothur.1.23.1.zip (1.23.1)
>  /w/images/4/4b/Mothur.1.22.2.zip (1.22.2)
>  /w/images/6/64/Mothur.1.21.1.zip (1.21.1)
>  /w/images/4/42/Mothur.1.20.3.zip (1.20.3)
>  /w/images/0/08/Mothur.1.19.4.zip (1.19.4)
>  /w/images/9/96/Mothur.1.18.1.zip (1.18.1)
>  /w/images/9/9b/Mothur.1.17.3.zip (1.17.3)
>  /w/images/8/8c/Mothur.1.16.1.zip (1.16.1)
>  /w/images/a/a5/Mothur.1.15.0.zip (1.15.0)
>  /w/images/2/2d/Mothur.1.14.0.zip (1.14.0)
>  /w/images/0/05/Mothur.1.13.0.zip (1.13.0)
>  /w/images/4/4d/Mothur.1.12.3.zip (1.12.3)
>  /w/images/b/b9/Mothur.1.11.0.zip (1.11.0)
>  /w/images/6/64/Mothur.1.10.0.zip (1.10.0)
>  /w/images/e/e5/Mothur.1.9.0.zip (1.9.0)
>  /w/images/e/ea/Mothur.1.8.0.zip (1.8.0)
>  /w/images/e/e8/Mothur.1.6.0.zip (1.6.0)
>  /w/images/7/7a/Mothur.1.4.2.zip (1.4.2)
>  /w/images/f/f3/Mothur.1.3.0.zip (1.3.0)
>  /w/images/a/a9/Mothur.1.2.0.zip (1.2.0)
>  /w/images/3/33/Mothur.1.1.0.zip (1.1.0)
> Newest version on remote site is 1.33.3, local version is 1.33.0+dfsg
>  (mangled local version number 1.33.0)
>  => Forcing download as requested
> -- Downloading updated package Mothur.1.33.3.zip
> -- Repacking from zip to .tar.xz
> -- Successfully downloaded updated package Mothur.1.33.3.tar.xz
> and removed 156 files from it in mothur_1.33.3+dfsg.orig.tar.xz
> -- Scan finished
> $ tar taf ../Mothur.1.33.3.tar.xz|wc -l
> 961
> $ tar taf ../mothur_1.33.3+dfsg.orig.tar.xz|wc -l
> 805

Hmmm, that's strange.  At my side the orig.tar.xz is a symlink to the
other file.  I'm using

debian/rules get-orig-source

(which does the same as you above).  BTW, I personally see no point in
keeping a non-stripped archive - it is perfectly fine to have only the
result of the stripped download.

No idea how I can help you reproducing the behaviour at my side.

Kind regards

 Andreas.

-- 
http://fam-tille.de


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#726310: gnome-shell: ALtGr dead keys are not dead after upgrade

[althaser]

Hey Norbert,

Could you please still reproduce this issue with newer gnome-shell version
like 3.8.4-5+b1 ?

It works fine here with 3.8.4-5+b1.

cheers,
althaser

Bug#742262: file: buggy magic: Regression in recognition of Perl scripts

[Christoph Biedl]

Christoph Biedl wrote...

> The recent security update in wheezy introduced a regression in the
> recognition of some Perl scripts. Technically, this update backported
> an upstream regression so this is an issue in both wheezy (5.11) and
> jessie (5.17).

About jessie, upstream has fixed that in the meantime (in
FILE5_17-57-gafe6b9f), the next upload of the file package will
contain that commit.

Christoph


signature.asc
Description: Digital signature

Bug#742295: sopwith: segmentation fault in single player mode (S)

[Markus Koschany]

Control: tags -1 patch

On 21.03.2014 22:26, Jesse Smith wrote:
> So far I have not been able to reproduce the bug, however I suspect I
> know what the problem is. The Sopwith makefile includes a flag for
> optimization (-O2).  Recent versions of the GCC compiler (version 4.7,
> 4.8) have changed the way code gets optimized and I have seen it cause a
> couple of games to crash at start-up.

Thank you very much for your quick response. You are right, the optimization is 
causing this
problem. On Debian -O2 is the default optimization flag and gcc 4.8 still the 
default compiler.
With your Makefile and without any additional compiler flags, I can't reproduce 
a crash either.

The solution for Debian is to add this line to debian/rules:

export DEB_BUILD_OPTIONS=noopt

and sopwith will be built with -O0 optimization. I can confirm that this solves 
the issue.

Regards,

Markus

From 4cbe01514c2f23d790a99c5bf93af12c4df9b9af Mon Sep 17 00:00:00 2001
From: Markus Koschany 
Date: Fri, 21 Mar 2014 23:11:40 +0100
Subject: [PATCH] noopt

---
 debian/rules | 1 +
 1 file changed, 1 insertion(+)

diff --git a/debian/rules b/debian/rules
index 58070e9..862987c 100755
--- a/debian/rules
+++ b/debian/rules
@@ -2,6 +2,7 @@
 
 # Set to enable verbose output from debhelper
 #export DH_VERBOSE=1
+export DEB_BUILD_OPTIONS=noopt
 
 install_dir = $(CURDIR)/debian/tmp
 
-- 
1.9.1



signature.asc
Description: OpenPGP digital signature

Bug#742265: addendum

[Christoph Biedl]

severity 742262 important
merge 742262 742265
tags 742262 confirmed
thanks

René Bleisch wrote...

> I guess its somewhat related to the fix of Bug 703993
> (https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=703993),

Correct.

> which had something to do with awks "BEGIN{ }".
> Is there now a mechanism like "if file contains BEGIN{...}$ then its
> an awk-file" ?
> This would then be wrong, because perl also uses a BEGIN{...} block

It's a bit more complicated: The fix for the above issue also
influenced the order patterns are checked. As a result, the awk
pattern is now checked *before* the Perl pattern. I'll try to have
that fixed by another upgrade.

For the time being, apply the patch below and rebuild the file
package. Only /usr/share/file/magic.mgc needs to be replaced. I'd be
glad if you could confirm this fixes the regression.

Re-using the old magic from 5.11-2+deb7u1 as suggested in the list is
a bad idea when checking files from unknown sources, so do this as a
last resort only.

Oh, and from your other mail:

> In the meantime, I found out, that another person also submitted a bug
> report about the same issue nearly at the same time
> (Bug 742262, https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=742262).
>
> We are both users of FAI, which is affected by this.

This is not entirely accurate ... Robert Schüttler told me in IRC
about the FAI mailing list thread, I filed this bug against my own
package so this is documented and people have a chance to learn about
it. You were faster :)

Sorry for the hassle, will check more thoroughly next time.

Christoph
diff --git a/debian/patches/DSA-2873-1-regression.patch b/debian/patches/DSA-2873-1-regression.patch
new file mode 100644
index 000..01ae3f1
--- /dev/null
+++ b/debian/patches/DSA-2873-1-regression.patch
@@ -0,0 +1,10 @@
+--- a/magic/Magdir/commands
 b/magic/Magdir/commands
+@@ -50,6 +50,7 @@
+ 0	string/wt	#!\ /usr/bin/awk	awk script text executable
+ !:mime	text/x-awk
+ 0	regex		=^\\s{0,100}BEGIN\\s{0,100}[{]	awk script text
++!:strength - 12
+ 
+ # AT&T Bell Labs' Plan 9 shell
+ 0	string/wt	#!\ /bin/rc	Plan 9 rc shell script text executable
diff --git a/debian/patches/series b/debian/patches/series
index f652245..167d7d7 100644
--- a/debian/patches/series
+++ b/debian/patches/series
@@ -4,3 +4,4 @@
 CVE-2014-1943.patch
 limit-repetitions-in-awk-detection.patch
 CVE-2014-2270.patch
+DSA-2873-1-regression.patch


signature.asc
Description: Digital signature

Bug#742302: libconfig-model-dpkg-perl: Please do not remove g++-multilib from control files

[Andreas Tille]

Package: libconfig-model-dpkg-perl
Severity: important

Hi,

I'm happily using `cme fix dpkg-control` for all my packages and usually
this is very helpful.  However, as you can read in bug #742285 this can
lead to the removal of needed packages - in this case g++-multilib.
Please make sure that this package is not removed.

Kind regards and thanks for the great help cme is providing (usually)

  Andreas.


-- System Information:
Debian Release: 7.4
  APT prefers stable
  APT policy: (501, 'stable'), (90, 'testing')
Architecture: i386 (i686)

Kernel: Linux 2.6.36-xenU-4814-i386 (SMP w/1 CPU core)
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#719646: gnome-shell: Activities panel (and SUPER shortcut) too wide for screen size

[althaser]

Hey Pierre,

Could you please still reproduce this issue with newer gnome-shell version
like 3.8.4-5+b1 ?

cheers,
althaser

Bug#721471: gnome-shell: Closing window w/Ctl-w causes 'w's to be printed in underlying window (receiving focus).

[althaser]

Hey Cabney,

Could you please still reproduce this issue with newer gnome-shell version
like 3.4.2-7+deb7u1 or 3.8.4-5+b1 ?

cheers,
althaser

Bug#735156: [Icedove] no mail notifications

[Francesco Muzio]

for my icedove mail.biff.show_alert has a true value and the 
notifications works


But the problem is a regression. On a modern desktop environment any 
notification are showed on a centralized manager. Older version of 
Iceweasel (and Icedove <= 17) do this.


I don't know the details but on new versions of mozilla software lack 
the libnotify support.

this bug affect also thunderbird on ubuntu
https://bugzilla.mozilla.org/show_bug.cgi?id=853104#c18

Trying to fade any doubt: when you say "The notification works here on 
Gnome 3 and KDE." you mean that the notification of a new mail arrived 
is showed, on KDE, in the same position and with same style like a 
notification of completed copy of a big file on the filesystem ?


On my machine the answer is no. Icedove 24 (unlike 17 and 10) shows in 
autonomous way its notifications.



--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#742301: awstats: Browser and OS stats not sorted by count

[Ralf G. R. Bergs]

Package: awstats
Version: 7.2+dfsg-1
Severity: normal

Dear Maintainer,

the browser and operating system statistics are not sorted by
decreasing number of occurrences, as in Advanced Web Statistics 7.0
(build 1.971). So for example for the browsers, if you only show the
first ten (random) browsers you get a completely meaningless statistics:

GaleonNo 0 6 0%
CurlYes 0 57 0%
NetscapeNo 0 579 0%
MultiZillaNo 0 1 0%
eCatchNo 0 9 0%
BonEcho (Firefox 2.0 development)No 0 2 0%
iBrowseNo 0 11 0%
w3mNo 0 2 0%
Minefield (Firefox 3.0 development)No 0 29 0%
BlackBerry (PDA/Phone browser)No 0 11 0%

To make it useful these two statistics should be sorted again by
decreasing number of occurrences.

Kind regards,

Ralf

-- System Information:
Debian Release: jessie/sid
  APT prefers testing
  APT policy: (500, 'testing')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 3.12-1-amd64 (SMP w/8 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages awstats depends on:
ii  perl  5.18.2-2+b1

Versions of packages awstats recommends:
ii  coreutils   8.21-1
ii  libnet-xwhois-perl  0.90-4

Versions of packages awstats suggests:
ii  apache2  2.4.7-1
ii  apache2-bin [httpd]  2.4.7-1
ii  libgeo-ipfree-perl   1.140470-1
ii  libnet-dns-perl  0.68-1.2
ii  libnet-ip-perl   1.26-1
ii  liburi-perl  1.60-1

-- Configuration Files:
/etc/awstats/awstats.conf.local changed [not included]

-- no debconf information


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#717593: Can't install gnome shell extensions from extensions.gnome.org because of root privilege

[althaser]

forwarded 717593 https://bugzilla.gnome.org/show_bug.cgi?id=704509
kthxbye

Hey William,

It seems to be an issue on that specific extension.

Have you tried to install another one ?

It works fine here with 3.8.4-5+b1.

cheers,
althaser

Bug#710635: pynac: FTBFS: ld: cannot find -lz

[Tobias Hansen]

That soname thing sounds a bit familiar. Maybe I forgot about it too.
Take your time. :)

Cheers,
Tobias

Am 21.03.2014 22:39, schrieb Julien Puydt:
> 
> I updated the git in something like october when it was released, but I
> don't remember if it was something ready to RFS or not. I think upstream
> broke the soname numbering, and promised to be more serious later on...
> 
> I'll not have the time to check before something like two weeks...
> 
> Snark on #debian-science


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#742300: byobu: incorrect dependencies on python interpreter and modules

[Sébastien Villemot]

Package: byobu
Version: 5.70-1
Severity: serious

Dear Maintainer,

If one has:
- both python and python3 interpreters installed
- python3-newt module installed
- but python-newt module *not* installed

Then byobu-config fails to start, despite the fact that package dependencies
are fulfilled.

The reason is that the script chooses to use the python (2.7) interpreter
(because it has higher precedence than python3). But then it does not find the
python-newt module, and crashes.

My understanding is that you would like to express the following dependency
relationship: (python && python-newt) || (python3 && python3-newt), but this is
not possible with our dependency system.

The simplest fix seems to remove the python3 dependencies, and have simply:
Depends: python, python-newt, ...

Another option is to improve the autodetection of the python interpreter
version, by checking if the newt package is present for that version.

Cheers,

-- 
 .''`.Sébastien Villemot
: :' :Debian Developer
`. `' http://www.dynare.org/sebastien
  `-  GPG Key: 4096R/381A7594


signature.asc
Description: Digital signature

Bug#742299: RM: hal [linux-any] -- ROM; RC buggy, deprecated, should not be released with jessie

[Michael Biebl]

Package: ftp.debian.org
Severity: normal

Hi,

please remove HAL from unstable/testing.
It's no longer function on Linux due to [0] and should not be released
with jessie (at least for linux-any). On !linux-any, hal is still used
by Xorg, so we can't remove it just yet completely.
While there is some progress to port xserver-xorg to devd [1] it's not
clear if/when this work will be uploaded to unstable.

So I at least want to make sure hal is not released with jessie on Linux
and no longer available on sid.

Once the package has been removed on jessie/sid, I'll make an upload
marking the package kfreebsd-any / hurd-any.

All reverse dependencies of hal on Linux have been notified for a long
time [2], are RC buggy and thus removed from testing already.


[0] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=705489
[1] https://lists.debian.org/debian-bsd/2014/02/msg1.html
[2] 
https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=halectomy;users=pkg-utopia-maintain...@lists.alioth.debian.org


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#710635: pynac: FTBFS: ld: cannot find -lz

[Julien Puydt]

Hi,

Le 21/03/2014 10:19, Tobias Hansen a écrit :

Hi Julien,

pynac 0.3.1 was released now.

Cheers,
Tobias


I updated the git in something like october when it was released, but I 
don't remember if it was something ready to RFS or not. I think upstream 
broke the soname numbering, and promised to be more serious later on...


I'll not have the time to check before something like two weeks...

Snark on #debian-science


--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#716748: gnome-shell: black background in overview (and desktop)

[althaser]

Hey,

Could you please still reproduce this issue with newer gnome-shell version
like 3.8.4-5+b1 ?

cheers,
althaser

Bug#742298: build dependency libx86emu-dev missing on mips, mipsel, powerpc, s390x and sparc

[Michael Biebl]

Source: hwinfo
Version: 21.0-1
Severity: serious

The package can not be built on 
mips, mipsel, powerpc, s390x and sparc
since the build dependency libx86emu-dev is missing on those
architectures. See [0]


[0] https://buildd.debian.org/status/package.php?p=hwinfo


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

Kernel: Linux 3.13-1-amd64 (SMP w/4 CPU cores)
Locale: LANG=de_DE.utf8, LC_CTYPE=de_DE.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#685506: Problem with *.zip archives

[Joachim Breitner]

Hi,

Am Freitag, den 21.03.2014, 22:19 +0100 schrieb Andreas Tille:
> Hm, I guess something remains wrong.  While uscan says:
> 
> Newest version on remote site is 1.33.3, local version is 1.33.0+dfsg
>  (mangled local version number 1.33.0)
>  => Forcing download as requested
> -- Downloading updated package Mothur.1.33.3.zip
> -- Repacking from zip to .tar.xz
> -- Successfully downloaded updated package Mothur.1.33.3.tar.xz
> and removed 134 files from it in mothur_1.33.3+dfsg.orig.tar.xz
> -- Scan finished
> 
> 
> the files that need to be removed are remaining inside the package.
> (all *.o files are there, __MACOSX dir remained).

Did you check Mothur.1.33.3.tar.xz or mothur_1.33.3+dfsg.orig.tar.xz – a
mistake I also did earlier today:

$ apt-get source mothur
Paketlisten werden gelesen... Fertig
Abhängigkeitsbaum wird aufgebaut.   
Statusinformationen werden eingelesen Fertig
HINWEIS: »mothur«-Paketierung wird betreut im »Svn«-Versionsverwaltungssystem 
auf:
svn://anonscm.debian.org/debian-med/trunk/packages/mothur/trunk/
Es müssen 918 kB an Quellarchiven heruntergeladen werden.
Holen: 1 http://http.debian.net/debian/ sid/main mothur 1.33.0+dfsg-1 (dsc) 
[2.103 B]
Holen: 2 http://http.debian.net/debian/ sid/main mothur 1.33.0+dfsg-1 (tar) 
[902 kB]
Holen: 3 http://http.debian.net/debian/ sid/main mothur 1.33.0+dfsg-1 (diff) 
[13,9 kB]
Es wurden 918 kB in 0 s geholt (1.095 kB/s). 
dpkg-source: Information: mothur wird nach mothur-1.33.0+dfsg extrahiert
dpkg-source: Information: mothur_1.33.0+dfsg.orig.tar.xz wird entpackt
dpkg-source: Information: mothur_1.33.0+dfsg-1.debian.tar.xz wird entpackt
dpkg-source: Information: makefile.patch wird angewandt
dpkg-source: Information: no_lcurses.patch wird angewandt
dpkg-source: Information: drop_sse_option.patch wird angewandt
dpkg-source: Information: catchall_fix.patch wird angewandt
dpkg-source: Information: build_without_tty.patch wird angewandt
dpkg-source: Information: uchime_link_dynamically wird angewandt
dpkg-source: Information: uchime_hardening.patch wird angewandt
dpkg-source: Information: spelling.patch wird angewandt
/tmp $ cd mothur-1.33.0+dfsg/
/tmp/mothur-1.33.0+dfsg $ ~/build/devscripts/devscripts/scripts/uscan.pl 
--verbose --force-download --repack --repack-compression xz
-- Scanning for watchfiles in .
-- Found watchfile in ./debian
-- In debian/watch, processing watchfile line:
   opts=dversionmangle=s/(\+dfsg|[~\+]repack)// 
http://www.mothur.org/wiki/Download_mothur
/w/images/.*/.*/Mothur\.([\d\.]+)\.zip
-- Found the following matching hrefs:
 /w/images/6/65/Mothur.1.33.3.zip (1.33.3)
 /w/images/9/99/Mothur.1.32.1.zip (1.32.1)
 /w/images/b/bc/Mothur.1.31.2.zip (1.31.2)
 /w/images/d/d3/Mothur.1.30.2.zip (1.30.2)
 /w/images/a/a5/Mothur.1.29.2.zip (1.29.2)
 /w/images/6/68/Mothur.1.28.0.zip (1.28.0)
 /w/images/c/cb/Mothur.1.27.0.zip (1.27.0)
 /w/images/2/20/Mothur.1.26.0.zip (1.26.0)
 /w/images/7/7b/Mothur.1.25.1.zip (1.25.1)
 /w/images/0/09/Mothur.1.24.1.zip (1.24.1)
 /w/images/3/33/Mothur.1.23.1.zip (1.23.1)
 /w/images/4/4b/Mothur.1.22.2.zip (1.22.2)
 /w/images/6/64/Mothur.1.21.1.zip (1.21.1)
 /w/images/4/42/Mothur.1.20.3.zip (1.20.3)
 /w/images/0/08/Mothur.1.19.4.zip (1.19.4)
 /w/images/9/96/Mothur.1.18.1.zip (1.18.1)
 /w/images/9/9b/Mothur.1.17.3.zip (1.17.3)
 /w/images/8/8c/Mothur.1.16.1.zip (1.16.1)
 /w/images/a/a5/Mothur.1.15.0.zip (1.15.0)
 /w/images/2/2d/Mothur.1.14.0.zip (1.14.0)
 /w/images/0/05/Mothur.1.13.0.zip (1.13.0)
 /w/images/4/4d/Mothur.1.12.3.zip (1.12.3)
 /w/images/b/b9/Mothur.1.11.0.zip (1.11.0)
 /w/images/6/64/Mothur.1.10.0.zip (1.10.0)
 /w/images/e/e5/Mothur.1.9.0.zip (1.9.0)
 /w/images/e/ea/Mothur.1.8.0.zip (1.8.0)
 /w/images/e/e8/Mothur.1.6.0.zip (1.6.0)
 /w/images/7/7a/Mothur.1.4.2.zip (1.4.2)
 /w/images/f/f3/Mothur.1.3.0.zip (1.3.0)
 /w/images/a/a9/Mothur.1.2.0.zip (1.2.0)
 /w/images/3/33/Mothur.1.1.0.zip (1.1.0)
Newest version on remote site is 1.33.3, local version is 1.33.0+dfsg
 (mangled local version number 1.33.0)
 => Forcing download as requested
-- Downloading updated package Mothur.1.33.3.zip
-- Repacking from zip to .tar.xz
-- Successfully downloaded updated package Mothur.1.33.3.tar.xz
and removed 156 files from it in mothur_1.33.3+dfsg.orig.tar.xz
-- Scan finished
$ tar taf ../Mothur.1.33.3.tar.xz|wc -l
961
$ tar taf ../mothur_1.33.3+dfsg.orig.tar.xz|wc -l
805

Gruß,
Joachim
-- 
Joachim "nomeata" Breitner
Debian Developer
  nome...@debian.org | ICQ# 74513189 | GPG-Keyid: 4743206C
  JID: nome...@joachim-breitner.de | http://people.debian.org/~nomeata


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

Bug#734095: bash-completion: Please replace 'grep' with 'command grep' within several functions.

[David Paleino]

tags 734095 upstream fixed-upstream
thanks

On Fri, 21 Mar 2014 22:27:22 +0100, Tomasz Nowiński wrote:

> Hi,
> 
> This bugs came back in version 2.1-3!

It never disappeared in 2.1-2.

Simply, the bug has been fixed upstream, while not in the Debian package...
yet. :)

Kindly,
David

-- 
 . ''`.   Debian developer | http://wiki.debian.org/DavidPaleino
 : :'  : Linuxer #334216 --|-- http://www.hanskalabs.net/
 `. `'`  GPG: 1392B174 | http://deb.li/dapal
   `-   2BAB C625 4E66 E7B8 450A C3E1 E6AA 9017 1392 B174


--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#742297: FTBFS on armhf: Missing symbols

[Michael Biebl]

Source: hwinfo
Version: 21.0-1
Severity: serious

hwinfo fails to build on armhf:
  numid2str@Base 21.0
  parse_id@Base 21.0
- probe_all@Base 21.0
+#MISSING: 21.0-1# probe_all@Base 21.0
  (arch=i386)probe_elsa@Base 21.0
  (arch=i386)probe_elsa_adr@Base 21.0
  probe_module@Base 21.0
@@ -262,4 +262,4 @@
  unload_module@Base 21.0
  update_irq_usage@Base 21.0
  vend_id2str@Base 21.0
- vm_read_segofs16@Base 21.0
+#MISSING: 21.0-1# vm_read_segofs16@Base 21.0
dh_makeshlibs: failing due to earlier errors
make: *** [binary-arch] Error 2


Full build log at [0]


[0] 
https://buildd.debian.org/status/fetch.php?pkg=hwinfo&arch=armhf&ver=21.0-1&stamp=1395428827


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

Kernel: Linux 3.13-1-amd64 (SMP w/4 CPU cores)
Locale: LANG=de_DE.utf8, LC_CTYPE=de_DE.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#742296: abcm2ps: New version 7.7.2 available

[Anselm Lingnau]

Ferran Jorba wrote:

> 7.x series of abcm2ps is already considered stable, and 7.7.2 is the current
> stable release.  Please consider packaging it for Debian.

I'll take care of that in the very near future. Thanks!

Anselm
-- 
Anselm Lingnau, Mainz/Mogontiacum, Germany  ling...@debian.org
There still hasn't been a word invented for people like me, whose main
experience when presented with this issue is an overwhelming, mind-blowing,
intergalactic sense of having more interesting things to think about.
-- Ben Goldacre explains why he doesn't believe in God


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#700639: icedove: Assertion failure: pRec->state != _PR_PID_REAPED, at uxproces.c:521 (SIGABRT)

[Carsten Schoenert]

On Fri, Mar 21, 2014 at 05:18:27PM -0400, Daniel Kahn Gillmor wrote:
> On 03/21/2014 05:08 PM, Carsten Schoenert wrote:
> > I have no clue, my last crash is months ago. I would say I have a
> > moderate amount of mails, sometimes 10-20 mails on other days up to 60.
> > But I don't use News, RSS or Chat on this.
> 
> i don't use news, rss, or chat either, but i think i have an order of
> magnitude more mail than you :(

On work I use the Thunderbird mobile version, there are often more than
100 mails per day and it works, but this the Windows version. :(

> how many accounts are you connected to at once?  depending on the day,
> i'm connected to 3, 4, or 5 accounts concurrently.

This depends on the PC/laptop, but it's very similar. On some PC only
three, but there are also five accounts configured.

But o.k., on the weekend in the upcomming week we meet us on the
Groupware Meeting in the Linuxhotel Essen Germany, I think Guido with a
significant more skills on GDB log reading and understanding will take a
deeper look at your logs. I hope he have a idea to get it.

Regards
Carsten


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#742292: xindy: FTBFS on kfreebsd

[Agustin Martin]

2014-03-21 20:56 GMT+01:00 Ivo De Decker :
> package: xindy
> version: 2.4-1.3
> severity: serious
>
>
> Hi,
>
> It seems xindy 2.4-1.3 doesn't build on kfreebsd, preventing migration to
> testing:
>
> https://buildd.debian.org/status/package.php?p=xindy

Seems a problem with clisp itself, which also does not build on
kfreebsd, see #740487.

Regards,

-- 
Agustin


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#741930: reportbug: add current init system information

[Sandro Tosi]

Ok, I think we need a wider audience - what d-d thinks about it? bonus
points if - in case we come out to add init info to every bug report -
a proper way to retrieve the init running is provided :)

cheers,
Sandro

On Fri, Mar 21, 2014 at 10:15 PM, Yves-Alexis Perez  wrote:
> On Fri, Mar 21, 2014 at 10:00:12PM +0100, Sandro Tosi wrote:
>> Hello Yves-Alexis
>>
>> On Mon, Mar 17, 2014 at 12:00 PM, Yves-Alexis Perez  
>> wrote:
>> > with the appearance of multiple init systems, it might be helpful to
>> > know about the currently running init system in the information
>> > collected by reportbug.
>> >
>> > A quick idea would be to report the result of:
>> >
>> > readlink /proc/1/exe
>> >
>> > but that won't work if /proc is mounted with hidepid. I'm unsure about
>> > other ways though.
>>
>> I thought about it a bit, and i'm not sure it's an information every
>> bug report should have. I suspect there are few packages which are
>> directly impacted by the possible different init system Debian has,
>> and it's probably more useful if such packages write a bugscript to
>> retrieve the init which is running on the machine and attach it to the
>> report.
>>
>> what do you think?
>
> Well, a *lot* stuff can actually change behavior depending on the init
> system, especially during transition time. Especially desktop
> environment and stuff handling permissions through policykit and
> logind/consolekit, but not only.
>
> If every package starts shipping a bugscript it'll be unmanageable.
>
> Regards,
> --
> Yves-Alexis Perez



-- 
Sandro Tosi (aka morph, morpheus, matrixhasu)
My website: http://matrixhasu.altervista.org/
Me at Debian: http://wiki.debian.org/SandroTosi


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#734095: [Bash-completion-devel] Bug#734095: bash-completion: Please replace 'grep' with 'command grep' within several functions.

[Tomasz Nowiński]

Hi,

This bugs came back in version 2.1-3!

$ grep '\'(command |\.)grep'
/usr/share/bash-completion/completions/c++:cc  --version 2>/dev/null 
| grep -q 'GCC\|Debian' && complete -F _gcc cc  || :
/usr/share/bash-completion/completions/c++:c++ --version 2>/dev/null 
| grep -q 'GCC\|Debian' && complete -F _gcc c++ || :
/usr/share/bash-completion/completions/cc:cc  --version 2>/dev/null 
| grep -q 'GCC\|Debian' && complete -F _gcc cc  || :
/usr/share/bash-completion/completions/cc:c++ --version 2>/dev/null 
| grep -q 'GCC\|Debian' && complete -F _gcc c++ || :
/usr/share/bash-completion/completions/colormake:local reset=$( 
set +o | grep -F posix ); set +o posix # for <(...)
/usr/share/bash-completion/completions/dict:# it down with grep 
if $cur looks like something that's safe to embed
/usr/share/bash-completion/completions/g++:cc  --version 2>/dev/null 
| grep -q 'GCC\|Debian' && complete -F _gcc cc  || :
/usr/share/bash-completion/completions/g++:c++ --version 2>/dev/null 
| grep -q 'GCC\|Debian' && complete -F _gcc c++ || :
/usr/share/bash-completion/completions/g77:cc  --version 2>/dev/null 
| grep -q 'GCC\|Debian' && complete -F _gcc cc  || :
/usr/share/bash-completion/completions/g77:c++ --version 2>/dev/null 
| grep -q 'GCC\|Debian' && complete -F _gcc c++ || :
/usr/share/bash-completion/completions/gcc:cc  --version 2>/dev/null 
| grep -q 'GCC\|Debian' && complete -F _gcc cc  || :
/usr/share/bash-completion/completions/gcc:c++ --version 2>/dev/null 
| grep -q 'GCC\|Debian' && complete -F _gcc c++ || :
/usr/share/bash-completion/completions/gcj:cc  --version 2>/dev/null 
| grep -q 'GCC\|Debian' && complete -F _gcc cc  || :
/usr/share/bash-completion/completions/gcj:c++ --version 2>/dev/null 
| grep -q 'GCC\|Debian' && complete -F _gcc c++ || :
/usr/share/bash-completion/completions/gmake:local reset=$( set 
+o | grep -F posix ); set +o posix # for <(...)
/usr/share/bash-completion/completions/gnumake:local reset=$( 
set +o | grep -F posix ); set +o posix # for <(...)
/usr/share/bash-completion/completions/gpc:cc  --version 2>/dev/null 
| grep -q 'GCC\|Debian' && complete -F _gcc cc  || :
/usr/share/bash-completion/completions/gpc:c++ --version 2>/dev/null 
| grep -q 'GCC\|Debian' && complete -F _gcc c++ || :
/usr/share/bash-completion/completions/lintian:tags=$( grep -e ^Tag 
/usr/share/lintian/checks/*.desc | cut -d\  -f2 )
/usr/share/bash-completion/completions/lintian: match=$(grep -nE "^Tag: 
$item$" /usr/share/lintian/checks/*.desc \
/usr/share/bash-completion/completions/lintian:checks=$(grep -e 
^Check-Script -e ^Abbrev \
/usr/share/bash-completion/completions/lintian: match=$(grep -nE 
"^(Check-Script|Abbrev): $item$" \
/usr/share/bash-completion/completions/lintian: todisable=$(grep -e 
^Check-Script -e ^Abbrev $match | \
/usr/share/bash-completion/completions/lintian:infos=$(grep -e 
^Collector /usr/share/lintian/collection/*.desc \
/usr/share/bash-completion/completions/lintian: match=$( grep -nE 
"^Collector: $item$" \
/usr/share/bash-completion/completions/lintian-info:tags=$( grep -e 
^Tag /usr/share/lintian/checks/*.desc | cut -d\  -f2 )
/usr/share/bash-completion/completions/lintian-info: match=$(grep -nE 
"^Tag: $item$" /usr/share/lintian/checks/*.desc \
/usr/share/bash-completion/completions/lintian-info: checks=$(grep -e 
^Check-Script -e ^Abbrev \
/usr/share/bash-completion/completions/lintian-info: match=$(grep -nE 
"^(Check-Script|Abbrev): $item$" \
/usr/share/bash-completion/completions/lintian-info: todisable=$(grep -e 
^Check-Script -e ^Abbrev $match | \
/usr/share/bash-completion/completions/lintian-info: infos=$(grep -e 
^Collector /usr/share/lintian/collection/*.desc \
/usr/share/bash-completion/completions/lintian-info: match=$( grep -nE 
"^Collector: $item$" \
/usr/share/bash-completion/completions/make:local reset=$( set 
+o | grep -F posix ); set +o posix # for <(...)
/usr/share/bash-completion/completions/pkgadd: pkginst_list=$(strings 
$(dequote $device) | grep "^PKG=" | sort -u | cut -d= -f2)
/usr/share/bash-completion/completions/pmake:local reset=$( set 
+o | grep -F posix ); set +o posix # for <(...)
/usr/share/bash-completion/completions/rdict:# it down with grep 
if $cur looks like something that's safe to embed
/usr/share/bash-completion/completions/slackpkg:# options list is based 
on `grep '\-.*\=.*)' /usr/sbin/slackpkg | cut -f1 -d\)`

/usr/share/bash-completion/completions/slackpkg: grep "^$cur" ) )
/usr/share/bash-completion/completions/slackpkg: grep "^$cur" ) )



On 06.01.2014 16:51, Ville Skyttä wrote:

Fixed upstream:
http://anonscm.debian.org/gitweb/?p=bash-completion/bash-completion.git;a=commitdiff;h=93ee009
http://anonscm.debian.org/gitweb/?p=bash-completion/bash-completion.git;a=commitdiff;h=e3edf7a



--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact

Bug#735156: [Icedove] no mail notifications

[Carsten Schoenert]

Hello Francesco,

On Fri, Mar 21, 2014 at 09:23:34PM +0100, Francesco Muzio wrote:
> I use KDE 4.11 on testing branch and I can confirm this bug for the latest
> version of icedove (24.3.0-2) available

I can't confirm this. I'm running the same here and notifications
running well. Something to see in the error console?

You have notifcation enabled? You can check this on the terminal by 
$ grep mail.biff.show_alert /path/to/prefs.js

If you get nothing then it should be enabled. But you can do also system
wide settings in /etc/icedove/pref/icedove.js that will override your
local settings.

See also
http://email.about.com/od/mozillathunderbirdtips/fl/How-to-Get-New-Mail-Alerts-from-Mozilla-Thunderbird.htm

Regards
Carsten


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#708123: [grub-pc] grub2 (2.00-14) fails to install on RAID arrays (rescue, boot is broken)

[Branko Mikic]

I can reproduce the bug described in #5. I've upgraded from wheezy to 
jessie and have a MB-fakeraid (RAID 0) installed via dmraid 1.0.0.rc16-5 
package.


root@welanduz:~# uname -a
Linux welanduz 3.13-1-amd64 #1 SMP Debian 3.13.5-1 (2014-03-04) x86_64 
GNU/Linux


root@welanduz:~# lspci | grep RAID
00:11.0 RAID bus controller: Advanced Micro Devices, Inc. [AMD/ATI] 
SB7x0/SB8x0/SB9x0 SATA Controller [Non-RAID5 mode] (rev 40)


 Grub used to work without errors. My fakeraid partitions where visible 
in the gnome-disk tool and mounting eg. NTFS wasn't a problem. Until the 
upgrade to jessie and the new grub package:


ii  grub-common2.00-22amd64
ii  grub-pc2.00-22amd64
ii  grub-pc-bin2.00-22amd64
ii  grub2-common   2.00-22amd64

Booting different OSes still works but the fakeraid partitions aren't 
recongnized by gnome-disk anymore although the fakeraid appears to be there:


root@welanduz:~# dmsetup info /dev/mapper/pdc_cjdgacajh*
Name:  pdc_cjdgacajh
State: ACTIVE
Read Ahead:256
Tables present:LIVE
Open count:2
Event number:  0
Major, minor:  254, 0
Number of targets: 1
UUID: DMRAID-pdc_cjdgacajh

Name:  pdc_cjdgacajh1
State: ACTIVE
Read Ahead:256
Tables present:LIVE
Open count:0
Event number:  0
Major, minor:  254, 2
Number of targets: 1
UUID: DMRAID-pdc_cjdgacajh1

Name:  pdc_cjdgacajh2
State: ACTIVE
Read Ahead:256
Tables present:LIVE
Open count:0
Event number:  0
Major, minor:  254, 1
Number of targets: 1
UUID: DMRAID-pdc_cjdgacajh2

root@welanduz:~# ll /dev/mapper/
total 0
crw--- 1 root root  10, 236 Mar 21 20:54 control
brw-rw 1 root disk 254,   0 Mar 21 20:54 pdc_cjdgacajh
brw-rw 1 root disk 254,   2 Mar 21 20:54 pdc_cjdgacajh1
brw-rw 1 root disk 254,   1 Mar 21 20:54 pdc_cjdgacajh2

root@welanduz:~# ll /dev/disk/by-id/ | grep dm
lrwxrwxrwx 1 root root 10 Mar 21 20:54 dm-name-pdc_cjdgacajh -> ../../dm-0
lrwxrwxrwx 1 root root 10 Mar 21 20:54 dm-name-pdc_cjdgacajh1 -> ../../dm-2
lrwxrwxrwx 1 root root 10 Mar 21 20:54 dm-name-pdc_cjdgacajh2 -> ../../dm-1
lrwxrwxrwx 1 root root 10 Mar 21 20:54 dm-uuid-DMRAID-pdc_cjdgacajh -> 
../../dm-0
lrwxrwxrwx 1 root root 10 Mar 21 20:54 dm-uuid-DMRAID-pdc_cjdgacajh1 -> 
../../dm-2
lrwxrwxrwx 1 root root 10 Mar 21 20:54 dm-uuid-DMRAID-pdc_cjdgacajh2 -> 
../../dm-1


and is mountable at console (mount -tntfs ...) but updating grub fails:

root@welanduz:~# update-grub2
Generating grub.cfg ...
Found background image: /usr/share/images/desktop-base/desktop-grub.png
Found linux image: /boot/vmlinuz-3.13-1-amd64
Found initrd image: /boot/initrd.img-3.13-1-amd64
Found linux image: /boot/vmlinuz-3.2.0-4-amd64
Found initrd image: /boot/initrd.img-3.2.0-4-amd64
grub-probe: error: unknown filesystem.
grub-probe: error: unknown filesystem.
Found Windows 7 (loader) on /dev/mapper/pdc_cjdgacajh1
/usr/sbin/grub-probe: error: unknown filesystem.
done

user.log has some errors:

root@welanduz:~# cat /var/log/user.log | grep dmraid
Mar 18 20:34:45 welanduz dmraid-activate: ERROR: Cannot retrieve RAID 
set information for pdc_cjdgacajh
Mar 18 20:34:45 welanduz dmraid-activate: ERROR: Cannot retrieve RAID 
set information for pdc_cjdgacajh
Mar 18 20:35:16 welanduz dmraid-activate: ERROR: Cannot retrieve RAID 
set information for pdc_cjdgacajh
Mar 18 20:35:16 welanduz dmraid-activate: ERROR: Cannot retrieve RAID 
set information for pdc_cjdgacajh
Mar 18 20:35:42 welanduz dmraid-activate: ERROR: Cannot retrieve RAID 
set information for pdc_cjdgacajh
Mar 18 20:35:42 welanduz dmraid-activate: ERROR: Cannot retrieve RAID 
set information for pdc_cjdgacajh
Mar 20 19:43:04 welanduz dmraid-activate: ERROR: Cannot retrieve RAID 
set information for pdc_cjdgacajh
Mar 20 19:43:04 welanduz dmraid-activate: ERROR: Cannot retrieve RAID 
set information for pdc_cjdgacajh


I don't know how i would setup a VM forcing use of dmraid with 
MB-fakeraids probably that's a reason for not appearing in that scenario.


root@welanduz:~# grub-probe -vv -t fs /boot/grub/ 2>&1 | cat >~/grub.log

grub-probe: info: Looking for /dev/sdc1.
grub-probe: info: /dev/sdc is a parent of /dev/sdc1.
grub-probe: info: /dev/sdc1 starts from 2048.
grub-probe: info: opening the device hd0.
grub-core/kern/disk.c:230: Opening `hd0'...
grub-probe: info: the size of hd0 is 250069680.
grub-core/kern/disk.c:230: Opening `hd0'...
grub-probe: info: the size of hd0 is 250069680.
grub-core/disk/diskfilter.c:135: Scanning for DISKFILTER devices on disk hd0
grub-probe: info: Scanning for DISKFILTER devices on disk hd0.
grub-probe: info: Scanning for mdraid1x devices on disk hd0.
grub-core/kern/emu/hostdisk.c:1024: opening the device `/dev/sdc' in 
open_device()

grub-core/kern/emu/hostdisk.c:1001: reusing open device `/dev/sdc'
grub-core/kern/emu/hostdisk.c:10

Bug#714551: gnome-shell: In overview mode, search field, app menu, workspaces, are not visible

[althaser]

Hey,

Could you please still reproduce this issue with newer gnome-shell version
like 3.8.4-5+b1 ?

cheers,
althaser

Bug#712948: gnome-shell: Cancelling Power Off Dialog prevents it reappearing

[althaser]

Hey,

Could you please still reproduce this issue with newer gnome-shell version
like 3.8.4-5+b1 ?

cheers,
althaser

Bug#700639: icedove: Assertion failure: pRec->state != _PR_PID_REAPED, at uxproces.c:521 (SIGABRT)

[Daniel Kahn Gillmor]

On 03/21/2014 05:08 PM, Carsten Schoenert wrote:
> I have no clue, my last crash is months ago. I would say I have a
> moderate amount of mails, sometimes 10-20 mails on other days up to 60.
> But I don't use News, RSS or Chat on this.

i don't use news, rss, or chat either, but i think i have an order of
magnitude more mail than you :(

how many accounts are you connected to at once?  depending on the day,
i'm connected to 3, 4, or 5 accounts concurrently.

--dkg



signature.asc
Description: OpenPGP digital signature

Bug#685506: Problem with *.zip archives

[Andreas Tille]

Hi Joachim,

On Fri, Mar 21, 2014 at 04:59:49PM +0100, Joachim Breitner wrote:
> Hi,
> 
> Am Freitag, den 21.03.2014, 14:17 +0100 schrieb Andreas Tille:
> > > > BTW, we should create a mothur-Package like test-case.  I just tested
> > > > your last commit and I can not get the __MACOSX go away. :-(
> > > 
> > > My suggestion was not implemented until now. Please try again. 
> > 
> > H, I can not confirm.  Did you tried the mothur package?
> 
> No, not until now. My code happened to add a "./" in front of every
> path, but that package excludes ".*", so all files were removed. Fixed
> and covered by the test suite.

Hm, I guess something remains wrong.  While uscan says:

Newest version on remote site is 1.33.3, local version is 1.33.0+dfsg
 (mangled local version number 1.33.0)
 => Forcing download as requested
-- Downloading updated package Mothur.1.33.3.zip
-- Repacking from zip to .tar.xz
-- Successfully downloaded updated package Mothur.1.33.3.tar.xz
and removed 134 files from it in mothur_1.33.3+dfsg.orig.tar.xz
-- Scan finished


the files that need to be removed are remaining inside the package.
(all *.o files are there, __MACOSX dir remained).

Kind regards

 Andreas.

-- 
http://fam-tille.de


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#742296: abcm2ps: New version 7.7.2 available

[Ferran Jorba]

Package: abcm2ps
Version: 6.6.17-1
Severity: wishlist
Tags: upstream

Dear Maintainer,

7.x series of abcm2ps is already considered stable, and 7.7.2 is the current
stable release.  Please consider packaging it for Debian.

Thanks for your work,

Ferran



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

Kernel: Linux 3.11-0.bpo.2-amd64 (SMP w/4 CPU cores)
Locale: LANG=ca_AD.UTF-8, LC_CTYPE=ca_AD.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages abcm2ps depends on:
ii  libc6  2.13-38+deb7u1

abcm2ps recommends no packages.

abcm2ps suggests no packages.

-- no debconf information


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#741930: reportbug: add current init system information

[Yves-Alexis Perez]

On Fri, Mar 21, 2014 at 10:00:12PM +0100, Sandro Tosi wrote:
> Hello Yves-Alexis
> 
> On Mon, Mar 17, 2014 at 12:00 PM, Yves-Alexis Perez  wrote:
> > with the appearance of multiple init systems, it might be helpful to
> > know about the currently running init system in the information
> > collected by reportbug.
> >
> > A quick idea would be to report the result of:
> >
> > readlink /proc/1/exe
> >
> > but that won't work if /proc is mounted with hidepid. I'm unsure about
> > other ways though.
> 
> I thought about it a bit, and i'm not sure it's an information every
> bug report should have. I suspect there are few packages which are
> directly impacted by the possible different init system Debian has,
> and it's probably more useful if such packages write a bugscript to
> retrieve the init which is running on the machine and attach it to the
> report.
> 
> what do you think?

Well, a *lot* stuff can actually change behavior depending on the init
system, especially during transition time. Especially desktop
environment and stuff handling permissions through policykit and
logind/consolekit, but not only.

If every package starts shipping a bugscript it'll be unmanageable.

Regards,
-- 
Yves-Alexis Perez


signature.asc
Description: Digital signature

Bug#742245: how-can-i-help should have --gift interface esp. for newbies.

[Lucas Nussbaum]

On 21/03/14 at 20:43 +0100, Tomasz Nitecki wrote:
> > This way a newbie contributor can start in a jiffy. Also it should
> > have some difference in the bandwidth used as well.
> 
> how-can-i-help uses (downloads and caches) static dump file that
> contains all the opportunities, so the bandwidth usage will remain
> unchanged regardless of the options used. However, making new
> contributor life easier is always most welcome :)

Note that the main reason to download a file with all (Debian-wide)
opportunities is to avoid risking leaking the list of installed
packages. That way, the comparison happens locally on the user's
machine.

Lucas


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#712947: gnome-shell: Long delay before power down happens

[althaser]

Hey,

Could you please still reproduce this issue with newer gnome-shell version
like 3.8.4-5+b1 ?

cheers,
althaser

Bug#729203: Intent to package FFmpeg

[Cyborg Ethly Alpha {My Research Desk}]

https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=729203#588

"I intend to be in the packaging team and Alexander Strasser as well.
Other co-maintainers are still welcome."

I'm interested in becoming a co-maintainer.

Daniel (aka Cyborg Alpha)

-- 
>From My Research Desk :)


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#700639: icedove: Assertion failure: pRec->state != _PR_PID_REAPED, at uxproces.c:521 (SIGABRT)

[Carsten Schoenert]

Hello,

On Fri, Mar 21, 2014 at 04:29:25PM -0400, Daniel Kahn Gillmor wrote:
> I'm not sure what i should do with this information.

nothing special, I'm allready was thinking that the changed linker flags
will not be the solution.
Unfortunately such bugs are hard to find unless we are unable to provoke
such a behavior of Icedove. I was asking you to see if this ugly bug is
allready on the table.

> I can re-run my MUA under debug mode again for a while if it would be
> useful to get another backtrace.  would that be helpful? 

Maybe, we are glad to have currently get the 24.3.0 into testing and
Christoph can provide a new upload with the resent released 24.4.0 maybe
this weekend. With this we would leave in afew days the version 17 in
stable-security and have only one version all over.  I thought the
backtrace with a current version will probably better than searching and
comparing with an older version because the original source has changed.

> I'm surprised that I am the only one seeing this.  Do other icedove
> users not have my mail volume or something?  maybe i happen to be
> talking to servers with particular bugs?  or too many servers
> concurrently?

I have no clue, my last crash is months ago. I would say I have a
moderate amount of mails, sometimes 10-20 mails on other days up to 60.
But I don't use News, RSS or Chat on this.

> If icedove was a simpler program, i think it would be more
> straightforward to diagnose; but at the moment, i'm mystified by this
> ongoing problem.

Indeed, Mozilla is forcing their FirefoxOS and only 4-5 persons working
on Thunderbird (as told on the Fosdem this year). And this persons
doesn't really "working" on new special features. Most of the work is
code cleanup and addaptions on the other changes depended on Firefox,
xulrunner, nss and so on.

Icedove has hugh blob on source files and the internal structure is hard
to understand.

Thanks for your feedback!

Regards
Carsten


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#570141: Specific Homepage entry for abandoned software

[Bill Allombert]

On Tue, Feb 16, 2010 at 07:29:28PM -0500, Jonathan Yu wrote:
> Hi,
> 
> > I would like to propose the following extension to "5.6.23.", the
> > "Homepage" header line:
> >
> > ---
> > If no homepage exists, e.g. because the software is abandoned and
> > vanished off the net, "None" can be specified.
> > ---
> 
> While I see the point in having something like this, perhaps some
> standard page (hosted on the Debian servers somewhere) informing users
> that the software has been abandoned (and perhaps pointing to a Google
> cache/Web Archive cache of the original site, or other relevant
> information) would provide more benefit.
> 
> In general, I think it's a good idea to move away from
> abandoned/unsupported software -- if you wish to continue supporting
> abandoned software, you should fork it/adopt the project upstream.

Nowadays, software homepage almost never disappear. Developers have little
incentive to delete the homepage of their abandonned projects, and major code
hosting website (sourceforge, etc.) almost never remove dead projects.  So the
absence of a webpage is not a good indicator whether a project is dead or
alive (it is more likely the software never add a webpage).

And that do not seem to be Moritz intent, though the bug title might induce
to think otherwise.

Cheers,
-- 
Bill. 

Imagine a large red swirl here. 


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#741930: reportbug: add current init system information

[Sandro Tosi]

Hello Yves-Alexis

On Mon, Mar 17, 2014 at 12:00 PM, Yves-Alexis Perez  wrote:
> with the appearance of multiple init systems, it might be helpful to
> know about the currently running init system in the information
> collected by reportbug.
>
> A quick idea would be to report the result of:
>
> readlink /proc/1/exe
>
> but that won't work if /proc is mounted with hidepid. I'm unsure about
> other ways though.

I thought about it a bit, and i'm not sure it's an information every
bug report should have. I suspect there are few packages which are
directly impacted by the possible different init system Debian has,
and it's probably more useful if such packages write a bugscript to
retrieve the init which is running on the machine and attach it to the
report.

what do you think?

Regards,

-- 
Sandro Tosi (aka morph, morpheus, matrixhasu)
My website: http://matrixhasu.altervista.org/
Me at Debian: http://wiki.debian.org/SandroTosi


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#712803: gnome-shell: Shutdown button in dialog does not work; must wait full 60 seconds

[Matt Spraggs]

Hey Althaser,

Really sorry, I no longer use Gnome or Debian!

Best,

Matt


On 21 March 2014 20:34, althaser  wrote:

> Hey Matthew,
>
> Could you please still reproduce this issue with newer gnome-shell version
> like 3.8.4-5+b1 ?
>
> cheers,
> althaser
>

Bug#742272: ITP: ocserv -- OpenConnect VPN Server

[Mike Miller]

On Fri, Mar 21, 2014 at 21:52:40 +0800, Liang Guo wrote:
>Package name: ocserv
> Version: 0.3.2
> Upstream Author: Nikos Mavrogiannopoulos 
> URL: http://www.infradead.org/openconnect/
> License: GPLv2
> Description: OpenConnect VPN Server

As maintainer of the OpenConnect client, I have been playing around
with my own local packaging of ocserv for some time now but hadn't
gotten around to filing an ITP yet. This will be great to get into the
Debian archive, thanks for offering to work on this. Let me know if
you need help packaging or testing ocserv.

-- 
mike


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#742279: "implicitly converted to pointer" warnings on 64bit architectures

[Eugeniy Meshcheryakov]

Hi,

I need more info about this. Is this about version 6.6.3-1? Version
6.3.3-1 was not packaged.

Also don't see those warnings when compiling on my machine (amd64). Are you
using sid?

Regards,
Eugeniy Meshcheryakov

21 березня 2014 о 16:28 +0100 Matthias Klose написав(-ла):
> Package: swi-prolog
> Version: 6.3.3-1
> Severity: serious
> 
> Seen at least on amd64:
> 
> Function `tgetstr' implicitly converted to pointer at pl-term.c:192
> Function `tgoto' implicitly converted to pointer at pl-term.c:262
> 
> Our automated build log filter detected the problem(s) above that will
> likely cause your package to segfault on architectures where the size of
> a pointer is greater than the size of an integer, such as ia64 and amd64.
> 
> This is often due to a missing function prototype definition.
> 
> Since use of implicitly converted pointers is always fatal to the application
> on ia64, they are errors.  Please correct them for your next upload.
> 
> More information can be found at:
> http://wiki.debian.org/ImplicitPointerConversions


signature.asc
Description: Digital signature

Bug#742295: sopwith: segmentation fault in single player mode (S)

[Markus Koschany]

Package: sopwith
Version: 1.8.1-4
Severity: normal

Dear maintainer,

when I try to play in single player mode (S key), the game crashes
with a segmentation fault.

This behaviour is reproducible by pressing the key combination S N or
S E. I can reproduce it on amd64 and i386.

However single player against the computer (C) appears to work as intended.

Regards,

Markus

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

Kernel: Linux 3.13-1-686-pae (SMP w/2 CPU cores)
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages sopwith depends on:
ii  libc62.18-4
ii  libsdl1.2debian  1.2.15-9

sopwith recommends no packages.

sopwith suggests no packages.

-- no debconf information


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#712803: gnome-shell: Shutdown button in dialog does not work; must wait full 60 seconds

[althaser]

Hey Matthew,

Could you please still reproduce this issue with newer gnome-shell version
like 3.8.4-5+b1 ?

cheers,
althaser

Bug#700639: icedove: Assertion failure: pRec->state != _PR_PID_REAPED, at uxproces.c:521 (SIGABRT)

[Daniel Kahn Gillmor]

On 03/21/2014 03:49 PM, Carsten Schoenert wrote:
> it's some time gone after this mail from you. The current Icedove
> version 24.3.0-2 has a fixed LDFLAGS variable. We had include
> '-Wl,--as-needed' which broke libraries dependencies while linking. So
> maybe theese crashes are also possibly gone.

alas, no.  I had a segfault crash again earlier today, with 24.3.0-2 :(

> On the other hand the code line and function that shown in the gdb logs
> are from the nspr thing and normaly should't depend on the fixed linker
> option I think.
> 
> mozilla/nsprpub/pr/src/md/unix/uxproces.c
> 
> 507 static void
> 508 ProcessReapedChildInternal(pid_t pid, int status)
> 509 {
> 510 pr_PidRecord *pRec;
> 511 
> 512 pRec = FindPidTable(pid);
> 513 if (NULL == pRec) {
> 514 pRec = PR_NEW(pr_PidRecord);
> 515 pRec->pid = pid;
> 516 pRec->state = _PR_PID_REAPED;
> 517 pRec->exitStatus = ExtractExitStatus(status);
> 518 pRec->reapedCV = NULL;
> 519 InsertPidTable(pRec);
> 520 } else {
> 521 PR_ASSERT(pRec->state != _PR_PID_REAPED);< 
> 522 if (_PR_PID_DETACHED == pRec->state) {
> 523 PR_ASSERT(NULL == pRec->reapedCV);
> 524 DeletePidTable(pRec);
> 525 PR_DELETE(pRec);
> 526 } else {
> 527 PR_ASSERT(_PR_PID_WAITING == pRec->state);
> 528 PR_ASSERT(NULL != pRec->reapedCV);
> 529 pRec->exitStatus = ExtractExitStatus(status);
> 530 pRec->state = _PR_PID_REAPED;
> 531 PR_NotifyCondVar(pRec->reapedCV);
> 532 }
> 533 }
> 534 }
> 
> As far as I can see the PR_ASSERT comes from
> mozilla/nsprpub/pr/include/prlog.h, but this header is for debugging
> stuff.
> 
> 206 #define PR_ASSERT(_expr) \
> 207 ((_expr)?((void)0):PR_Assert(# _expr,__FILE__,__LINE__))

I'm not sure what i should do with this information.

I can re-run my MUA under debug mode again for a while if it would be
useful to get another backtrace.  would that be helpful?  I'm surprised
that I am the only one seeing this.  Do other icedove users not have my
mail volume or something?  maybe i happen to be talking to servers with
particular bugs?  or too many servers concurrently?

If icedove was a simpler program, i think it would be more
straightforward to diagnose; but at the moment, i'm mystified by this
ongoing problem.

--dkg




signature.asc
Description: OpenPGP digital signature

Bug#314427: hsql-postgresql imports

[Nick Rudnick]

Hi all,

this weekend, finally, I have plenty of time to adapt hsql-postgresql.

Thanks to everybody from my side, too. :-)


2014-03-21 20:27 GMT+01:00 Joachim Breitner :

> Hi,
>
> Am Montag, den 17.03.2014, 11:05 +0100 schrieb Christoph Berg:
> > The OIDs of the exposed datatypes won't ever change, so B-D on
> > postgresql-server-dev-all is safe even if -9.3 will be replaced by
> > -9.4 or later in the future.
>
> thanks. I added the B-D.
>
> > What worries me, though, is this:
> >
> > Build-Conflicts:
> >  postgresql-server-dev-8.3,
> >  postgresql-server-dev-8.4
> >
> > haskell-hsql-postgresql (1.7.3-2) unstable; urgency=low
> >
> >   * Make postgresql-server-dev-8.[34] a Build-Conflicts (Closes: 559583)
> > If this package is present at build-time, the resulting ghc-pkg info
> will
> > reference a directory from it in Includes, causing the installation
> to
> > fail (see #471786). But if it is not, everything goes well and we
> have one
> > dependency less.
> >
> >  -- Joachim Breitner   Sat, 05 Dec 2009 17:10:34
> +0100
> >
> > I cannot reproduce the problem here with postgresql-server-dev-9.3
> > installed - the deps of the resulting .debs are the same, but I didn't
> > look into the package for file references in there.
>
> Installing the new package will yield a warning
> Warning: include-dirs: /usr/include/postgresql/9.3/server doesn't exist or
> isn't a directory
> but not an error any more, so I think this is fine.
>
> Uploading right now.
>
> Thanks for your help, Christoph,
> Joachim
>
>
> --
> Joachim "nomeata" Breitner
> Debian Developer
>   nome...@debian.org | ICQ# 74513189 | GPG-Keyid: 4743206C
>   JID: nome...@joachim-breitner.de | http://people.debian.org/~nomeata
>

Bug#742294: Breaks Iceweasel 28

[Stéphane Glondu]

Package: xul-ext-treestyletab
Version: 0.14.2013112901-1
Severity: serious

Dear Maintainer,

This extension is broken with Iceweasel 28. The left panel is all
grey.

Worse, with this extension installed, Iceweasel's tab functionnality
seems completely broken. In particular, it is not possible to directly
get to the add-ons page to disable it. I had to directly ask for
about:addons from the command line to disable it.

Cheers,

-- 
Stéphane

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

Kernel: Linux 3.13-1-amd64 (SMP w/8 CPU cores)
Locale: LANG=fr_FR.utf8, LC_CTYPE=fr_FR.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages xul-ext-treestyletab depends on:
ii  iceweasel  28.0-1

xul-ext-treestyletab recommends no packages.

xul-ext-treestyletab suggests no packages.

-- no debconf information


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#624122: Hash Sum mismatch

[Johannes Stezenbach]

I'm also seeing the Hash Sum mismatch often since about a week ago,
maybe since "[UPGRADE] apt:amd64 0.9.16 -> 0.9.16.1" (sid) but I did not
downgrade to confirm.  However, it seems the issue is caused
by xz decompressor truncating the files.  For example:

# ls -l /var/lib/apt/lists/partial/
-rw-r--r-- 1 root root  7067192 Mar 21 15:05 
ftp.de.debian.org_debian_dists_unstable_main_source_Sources
-rw-rw-rw- 1 root root 11841536 Mar 21 15:05 
ftp.de.debian.org_debian_dists_unstable_main_source_Sources.decomp.FAILED
# xzcat ftp.de.debian.org_debian_dists_unstable_main_source_Sources > 
ftp.de.debian.org_debian_dists_unstable_main_source_Sources.d
# ls -l ftp.de.debian.org_debian_dists_unstable_main_source_Sources.d
-rw-r--r-- 1 root root 32434409 Mar 21 20:34 
ftp.de.debian.org_debian_dists_unstable_main_source_Sources.d
# sha1sum *
6701076d9d340be45b39be5ac212d69b3e3db34b  
ftp.de.debian.org_debian_dists_unstable_main_source_Sources
50eec7dd53aa1b6b45f360a67418f0253c5e99ec  
ftp.de.debian.org_debian_dists_unstable_main_source_Sources.d
a0d54d0ed700a9ec8a27b47f45b3bff18c2177b9  
ftp.de.debian.org_debian_dists_unstable_main_source_Sources.decomp.FAILED

# grep 6701076d9d340be45b39be5ac212d69b3e3db34b 
../ftp.de.debian.org_debian_dists_unstable_InRelease
 6701076d9d340be45b39be5ac212d69b3e3db34b  7067192 main/source/Sources.xz
# grep 50eec7dd53aa1b6b45f360a67418f0253c5e99ec 
../ftp.de.debian.org_debian_dists_unstable_InRelease
 50eec7dd53aa1b6b45f360a67418f0253c5e99ec 32434409 main/source/Sources

And diffing the two decompressed files shows the .decomp.FAILED
is just truncated.

FWIW, I do not have APT::Get::List-Cleanup "false" but I do
have Acquire::PDiffs "false".

HTH,
Johannes


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#735156: (no subject)

[Francesco Muzio]

I use KDE 4.11 on testing branch and I can confirm this bug for the 
latest version of icedove (24.3.0-2) available



--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#742226: linux-image-3.13-1-amd64: Internet banking fails to detect Java with Debian kernels

[Gurvan Huiban]

Dear maintainer

> > I believe that one of the patch applied on Debian kernel interferes
> > with the relationship between the Browser and Java when running the
> > Internet banking applet.
> 
> We don't patch very much, so my suspicion is that this is purely
> triggered by the version number (only 2 dotted components).
> 
> > Could you please investigated?
> 
> So there's an easy way to check this.  Try quitting Iceweasel and then
> restarting it with the command:
> 
> setarch x86_64 --uname-2.6 iceweasel

You are right: with the command above, the Java applet works perfectly.

Hence I believe the bug lies in the applet (should be more permissive with the 
kernel numbering) and not in the kernel.

As far as I am concerned, the bug can be closed. Thank you. I will (try to) 
open a bug with the bank

Gurvan

PS. How did you get the idea that the problem was related to the kernel 
version number?


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#742293: libpoppler44: rebuild against libopenjpg5?

[Patrice Duroux]

Package: libpoppler44
Version: 0.24.5-2
Severity: wishlist


Dear Maintainers,

I don't known where to address this wish so I am pointing this to you.
It happens that sometimes experimental packages are not built against libraries
targeted in transitional process while their unstable counterparts have already
made a step forward. For instance, this is the case for libpoppler44
[0.24.5-2_amd64]
that depends on libopenjpg2 whereas libpoppler37 [0.22.5-4+b1_amd64] already
depends on libopenjpg5 and has been uploaded earlier in the archive.

Many regards,
Patrice



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

Kernel: Linux 3.14-rc7-amd64 (SMP w/4 CPU cores)
Locale: LANG=fr_FR.utf8, LC_CTYPE=fr_FR.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages libpoppler44 depends on:
ii  libc6  2.18-4
ii  libfontconfig1 2.11.0-5
ii  libfreetype6   2.5.2-1
ii  libjpeg8   8d-2
ii  liblcms2-2 2.5-1
ii  libopenjpeg2   1.3+dfsg-4.7+b1
ii  libpng12-0 1.2.50-1
ii  libstdc++6 4.8.2-16
ii  libtiff5   4.0.3-8
ii  multiarch-support  2.18-4

Versions of packages libpoppler44 recommends:
ii  poppler-data  0.4.6-5

libpoppler44 suggests no packages.

-- no debconf information


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#742291: glances: Missing dependency on python3-pkg-resources?

[Carsten Kosthorst]

Package: glances
Version: 1.7.4-1
Severity: important

Dear Maintainer,

   * What led up to the situation?
Starting glances.

   * What exactly did you do (or not do) that was effective (or
 ineffective)?
ck@one:~$ glances

   * What was the outcome of this action?
Traceback (most recent call last):
  File "/usr/bin/glances", line 5, in 
from pkg_resources import load_entry_point
ImportError: No module named 'pkg_resources'

   * What outcome did you expect instead?
Well... glances. ;)

Installing python3-pkg-resources fixed this.

-- System Information:
Debian Release: jessie/sid
  APT prefers testing
  APT policy: (500, 'testing')
Architecture: amd64 (x86_64)

Kernel: Linux 3.12-1-amd64 (SMP w/4 CPU cores)
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash

Versions of packages glances depends on:
ii  adduser 3.113+nmu3
ii  lsb-base4.1+Debian12
ii  python3 3.3.4-1
ii  python3-psutil  1.2.1-1+b1
pn  python3:any 

Versions of packages glances recommends:
pn  python3-jinja2  

glances suggests no packages.

-- no debconf information


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#717076: libjpeg draft resolution

[Kurt Roeckx]

On Thu, Mar 20, 2014 at 05:37:01PM +, Colin Watson wrote:
> 
> To the Project Secretary: Ian raised the point that he feels that option
> A should not require 3:1.  The "Provides: libjpeg-dev" here is
> essentially a technical device to ensure that packages can declare
> Build-Depends: libjpeg-dev and that we get consistent results across the
> archive without having to make hundreds of changes to individual
> packages.  Ian's opinion is that this is a simple case of overlapping
> jurisdiction (essentially, maintainership of a package, albeit a virtual
> one, under 6.1(2)), and therefore does not require a supermajority.
> 
> Could you please interpret the constitution for us?  Does option A
> require 3:1, or only a simple majority (perhaps with some trivial
> rewording)?  Thanks.

The text says that you're using your power to decide something
under 6.1(4).  I can't see how that doesn't require a 3:1 majority.

The text is also saying what a specific package should do, and
that does sound a lot like overriding a maintainer.

So if you really want to prevent using a supermajority, I suggest
you write is so that you at least don't mention the other package
by name but make it more general.

I also suggest you don't mention the name libjpeg-dev directly but
instead use words to describe it so that it still applies when it
needs to be renamed for whatever reason.


Kurt


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#742292: xindy: FTBFS on kfreebsd

[Ivo De Decker]

package: xindy
version: 2.4-1.3
severity: serious


Hi,

It seems xindy 2.4-1.3 doesn't build on kfreebsd, preventing migration to
testing:

https://buildd.debian.org/status/package.php?p=xindy

Cheers,

Ivo


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org