Bug#817231: rabbitvcs: All files in home folder removed

[Bastian Pranzas]

Source: rabbitvcs
Severity: critical
Justification: causes serious data loss

Dear Maintainer,

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

   * What led up to the situation?
I just wanted a quick and easy way to access my work svn from my home computer, 
so I googled and found rabbitvcs. I am running debian jessie and saw that it is 
in the repo, so I just installed it.

   * What exactly did you do (or not do) that was effective (or
 ineffective)?
I just used it a few minutes:
- I conntected to my work svn using "browse repository" or similar, which 
worked nicely
- I went to a certain directory in the repo and tried to just copy a file out 
using drag into nautilus, which did nothing
- Next thing I tried was the "export" function, so I tried that and it told me 
something like "authentication failed"
- Then I tried to check out the folder containing the file, which gave the same 
problem
(I did all steps above from the repository browser)
- Note that at no point in time did the program ask me if I want to delete or 
overwrite anything. I might have used the program wrongly, but I assumed that 
because it is "easy to use" like tortoisesvn, that I don't have to read the 
documentation to prevent data loss.

   * What was the outcome of this action?
- Then I went back to nautilus and noticed that it won't show my user folders 
anymore, my desktop wallpaper was gone, etc
- I checked if there is anything mounted over my home folder, which wasn't the 
case

   * What outcome did you expect instead?
I expected the file/folder to appear where I tried to export/check them out.

I found this using google:
http://askubuntu.com/questions/473433/rabbitsvn-deleted-all-my-folders
which is basically the same story as mine.

On the rabbitvcs homepage in the "known issues" section, in the project bug 
tracker and the user mailing list of the project I found no mention of it. I 
wanted to report it to the mailing list, but it appears I can't get the right 
to post.

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

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

Bug#817232: postinst trying to disable /etc/init.d/keyboard-setup

[Mateusz Łukasik]

Package: keyboard-configuration
Version: 1.137
Severity: grave

Dear Maintainer,

after D-U in stretch I have:

The following packages will be upgraded:
  keyboard-configuration
1 upgraded, 0 newly installed, 0 to remove and 18 not upgraded.
1 not fully installed or removed.
Need to get 0 B/747 kB of archives.
After this operation, 33.8 kB disk space will be freed.
Preconfiguring packages ...
Setting up libfdisk1:amd64 (2.27.1-4) ...
Processing triggers for libc-bin (2.21-9) ...
(Reading database ... 158941 files and directories currently installed.)
Preparing to unpack .../keyboard-configuration_1.138_all.deb ...
update-rc.d: warning /etc/init.d/keyboard-setup still exist. Terminating
dpkg: error processing archive /var/cache/apt/archives/keyboard-
configuration_1.138_all.deb (--unpack):
 subprocess new pre-installation script returned error exit status 1
Errors were encountered while processing:
 /var/cache/apt/archives/keyboard-configuration_1.138_all.deb
E: Sub-process /usr/bin/dpkg returned an error code (1)


System is running with file-rc as init.



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

Kernel: Linux 4.4.0-1-amd64 (SMP w/4 CPU cores)
Locale: LANG=pl_PL.utf8, LC_CTYPE=pl_PL.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: sysvinit (via /sbin/init)

Versions of packages keyboard-configuration depends on:
ii  debconf 1.5.58
ii  initscripts 2.88dsf-59.3
ii  liblocale-gettext-perl  1.07-1+b1

keyboard-configuration recommends no packages.

keyboard-configuration suggests no packages.

Versions of packages keyboard-configuration is related to:
ii  console-common0.7.89
ii  console-data  2:1.12-5
pn  console-tools 
pn  gnome-control-center  
ii  kbd   2.0.3-2

-- debconf information:
  keyboard-configuration/layoutcode: pl
* keyboard-configuration/variant: Polish
  keyboard-configuration/compose: No compose key
  keyboard-configuration/unsupported_options: true
  debian-installer/console-setup-udeb/title:
  keyboard-configuration/xkb-keymap: pl
  keyboard-configuration/toggle: No toggling
  keyboard-configuration/model: A4Tech KB-21
  keyboard-configuration/store_defaults_in_debconf_db: false
  keyboard-configuration/altgr: The default for the keyboard layout
  keyboard-configuration/variantcode:
  keyboard-configuration/optionscode:
  keyboard-configuration/unsupported_config_layout: true
  keyboard-configuration/unsupported_config_options: true
  keyboard-configuration/layout:
  keyboard-configuration/ctrl_alt_bksp: false
  keyboard-configuration/unsupported_layout: true
  keyboard-configuration/other:
  keyboard-configuration/switch: No temporary switch
  keyboard-configuration/modelcode: a4techKB21

Bug#817233: CVE-2016-1968

[Moritz Muehlenhoff]

Source: brotli
Severity: grave
Tags: security

Firefox fixed a buffer overflow in brotli:
https://www.mozilla.org/en-US/security/advisories/mfsa2016-30/

Please get in touch with upstream whether this also needs to be fixed
in the brotli source package in Debian.

Cheers,
Moritz

Bug#749833: scilab: Scilab include non-free codes

[Clément David]

Hi Maximiliano, Sylvestre,

Le lundi 29 février 2016 à 10:24 +0100, Sylvestre Ledru a écrit :
> Le 29/02/2016 à 09:54, Maximiliano Curia a écrit :
> > 
> > Control: block 816260 by 749833
> > 
> > Hi,
> > 
> > As a request from the release team I have removed the dependency of scilab 
> > from cantor, I'm adding this block to the corresponding bug in cantor as 
> > way 
> > to remember to reenable the backend once the problem is fixed.
> > 
> > Also, since there is a patch available upstream that's being stale for 
> > review 
> > for sometime now, wouldn't it be feasible to upload a patched scilab to 
> > experimental as a way to gather some testers/reviewers?
> > 
> > Happy hacking,
> Clément, François, could you help here?
> Thanks
> 
> Sylvestre

The current patch on the codereview is incomplete and will not provide a decent 
implementation for
now. You can provide a patched version for the 5.x family to iterate on the 
current patch
implementation. We will be happy to help you rebasing / validating it !

To conforms to the open-source licence, the problematic files will be removed 
before the 6.0.0
release. And the functionality will be present by either using a scilab 
implementation (eg. based on
the patchset) or RpolyPlusPlus [1] .

[1]: https://github.com/sweeneychris/RpolyPlusPlus

--
Clément

Processed: found 817092 in 3:4.0.5-3

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> found 817092 3:4.0.5-3
Bug #817092 [libjs-handlebars] libjs-handlebars: Minified source is non-free
Marked as found in versions libjs-handlebars/3:4.0.5-3.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
817092: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=817092
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#805095: marked as done (sflphone: Uses ALL ciphers)

[Debian Bug Tracking System]

Your message dated Wed, 09 Mar 2016 04:37:23 +
with message-id 
and subject line Bug#817196: Removed package(s) from unstable
has caused the Debian Bug report #805095,
regarding sflphone: Uses ALL ciphers
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
805095: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=805095
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: sflphone
Severity: grave
Tags: security

I just saw this in the code:
SSL_CTX_set_cipher_list(ctx, "ALL");

This enables ciphers you don't want, it might include those that
don't provide authentication or encryption.


Kurt
--- End Message ---
--- Begin Message ---
Version: 1.4.1-0.4+rm

Dear submitter,

as the package sflphone has just been removed from the Debian archive
unstable we hereby close the associated bug reports.  We are sorry
that we couldn't deal with your issue properly.

For details on the removal, please see https://bugs.debian.org/817196

The version of this package that was in Debian prior to this removal
can still be found using http://snapshot.debian.org/.

This message was generated automatically; if you believe that there is
a problem with it please contact the archive administrators by mailing
ftpmas...@ftp-master.debian.org.

Debian distribution maintenance software
pp.
Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---

Bug#804615: marked as done (sflphone: FTBFS: undefined reference to `SSLv3_server_method')

[Debian Bug Tracking System]

Your message dated Wed, 09 Mar 2016 04:37:23 +
with message-id 
and subject line Bug#817196: Removed package(s) from unstable
has caused the Debian Bug report #804615,
regarding sflphone: FTBFS: undefined reference to `SSLv3_server_method'
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
804615: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=804615
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: sflphone
Version: 1.4.1-0.4
Severity: serious
Justification: fails to build from source
Tags: sid stretch
User: reproducible-bui...@lists.alioth.debian.org
Usertags: ftbfs
X-Debbugs-CC: reproducible-bui...@lists.alioth.debian.org

Dear Maintainer,

The package fails to build, as openssl has dropped sslv3:

/sflphone-1.4.1/daemon/libs/pjproject-2.2.1/pjlib/lib/libpj-x86_64-pc-linux-gnu.a(ssl_sock_ossl.o):
 In function `init_openssl':
/sflphone-1.4.1/daemon/libs/pjproject-2.2.1/pjlib/build/../src/pj/ssl_sock_ossl.c:328:
 undefined reference to `SSLv3_server_method'
/sflphone-1.4.1/daemon/libs/pjproject-2.2.1/pjlib/lib/libpj-x86_64-pc-linux-gnu.a(ssl_sock_ossl.o):
 In function `create_ssl':
/sflphone-1.4.1/daemon/libs/pjproject-2.2.1/pjlib/build/../src/pj/ssl_sock_ossl.c:515:
 undefined reference to `SSLv3_method'
collect2: error: ld returned 1 exit status
/sflphone-1.4.1/daemon/libs/pjproject-2.2.1/build/rules.mak:122: recipe for 
target '../bin/pjlib-test-x86_64-pc-linux-gnu' failed
make[4]: *** [../bin/pjlib-test-x86_64-pc-linux-gnu] Error 1
make[4]: Leaving directory 
'/sflphone-1.4.1/daemon/libs/pjproject-2.2.1/pjlib/build'

Full build log:
https://reproducible.debian.net/rb-pkg/unstable/amd64/sflphone.html

-- System Information:
Debian Release: stretch/sid
APT prefers unstable
APT policy: (500, 'unstable')
Architecture: amd64 (x86_64)
--- End Message ---
--- Begin Message ---
Version: 1.4.1-0.4+rm

Dear submitter,

as the package sflphone has just been removed from the Debian archive
unstable we hereby close the associated bug reports.  We are sorry
that we couldn't deal with your issue properly.

For details on the removal, please see https://bugs.debian.org/817196

The version of this package that was in Debian prior to this removal
can still be found using http://snapshot.debian.org/.

This message was generated automatically; if you believe that there is
a problem with it please contact the archive administrators by mailing
ftpmas...@ftp-master.debian.org.

Debian distribution maintenance software
pp.
Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---

Bug#817012: ruby-amqp and ruby-amq-client: error when trying to install together

[Andreas Beckmann]

On 2016-03-09 05:02, Sebastien Badia wrote:
> root@986c8ab6cb31:~# dpkg -i ruby-amqp_1.5.1-3_all.deb 
> Selecting previously unselected package ruby-amqp.
> (Reading database ... 18260 files and directories currently installed.)
> Preparing to unpack ruby-amqp_1.5.1-3_all.deb ...
> Unpacking ruby-amqp (1.5.1-3) ...
> Replacing files in old package ruby-amq-client (1.0.4-1) ...
> Setting up ruby-amqp (1.5.1-3) ...
> root@986c8ab6cb31:~# apt policy ruby-amq-client
> ruby-amq-client:
>   Installed: 1.0.4-1
>   Candidate: 1.0.4-1
>   Version table:
>  *** 1.0.4-1 100
> 100 /var/lib/dpkg/status
> root@986c8ab6cb31:~# apt policy ruby-amqp  
> ruby-amqp:
>   Installed: 1.5.1-3
>   Candidate: 1.5.1-3
>   Version table:
>  *** 1.5.1-3 100
> 100 /var/lib/dpkg/status

That looks like you only have a Replaces: ruby-amq-client without a
corresponding Breaks. If you remove ruby-amqp at this point,
ruby-amq-client will still be installed, but will be missing some files,
despite of dpkg considering it as correctly installed.


Andreas

Bug#817012: ruby-amqp and ruby-amq-client: error when trying to install together

[Sebastien Badia]

On Tue, Mar 08, 2016 at 09:15:01PM (+0100), Andreas Beckmann wrote:
> Hi,
> 
> removal of the old package is not sufficient, you still need to add 
> Breaks+Replaces:

Hi!

Oh indeed, Humrf… I missed this…

It should be ok in the version -3

Thanks! And sorry for the inconvenience.

root@986c8ab6cb31:~# apt policy ruby-amq-client
ruby-amq-client:
  Installed: 1.0.4-1
  Candidate: 1.0.4-1
  Version table:
 *** 1.0.4-1 100
100 /var/lib/dpkg/status
root@986c8ab6cb31:~# dpkg -i ruby-amqp_1.5.1-3_all.deb 
Selecting previously unselected package ruby-amqp.
(Reading database ... 18260 files and directories currently installed.)
Preparing to unpack ruby-amqp_1.5.1-3_all.deb ...
Unpacking ruby-amqp (1.5.1-3) ...
Replacing files in old package ruby-amq-client (1.0.4-1) ...
Setting up ruby-amqp (1.5.1-3) ...
root@986c8ab6cb31:~# apt policy ruby-amq-client
ruby-amq-client:
  Installed: 1.0.4-1
  Candidate: 1.0.4-1
  Version table:
 *** 1.0.4-1 100
100 /var/lib/dpkg/status
root@986c8ab6cb31:~# apt policy ruby-amqp  
ruby-amqp:
  Installed: 1.5.1-3
  Candidate: 1.5.1-3
  Version table:
 *** 1.5.1-3 100
100 /var/lib/dpkg/status

Seb


signature.asc
Description: PGP signature

Bug#816210: marked as pending

[Jelmer Vernooij]

tag 816210 pending
thanks

Hello,

Bug #816210 reported by you has been fixed in the Git repository. You can
see the changelog below, and you can check the diff of the fix at:

http://git.debian.org/?p=pkg-samba/samba.git;a=commitdiff;h=098d9d3

---
commit 098d9d36bdec460a71d469021cc4eaa3c047dc0e
Author: Jelmer Vernooij 
Date:   Sun Mar 6 22:52:14 2016 +

Move strict ldb dependency to samba-dsdb-modules package, which actually 
contains the modules. Closes: #816210

diff --git a/debian/changelog b/debian/changelog
index 711e8e8..e50d051 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,10 @@
+samba (2:4.3.5+dfsg-2) UNRELEASED; urgency=medium
+
+  * Move strict ldb dependency to samba-dsdb-modules package, which
+actually contains the modules. Closes: #816210
+
+ -- Jelmer Vernooij   Sun, 06 Mar 2016 22:51:53 +
+
 samba (2:4.3.5+dfsg-1) unstable; urgency=medium
 
   * New upstream release.

Processed: Bug#816210 marked as pending

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> tag 816210 pending
Bug #816210 {Done: Jelmer Vernooij } [src:samba] libldb1: 
Upgrade removes xine-ui, kde-runtime + 8 more (Sid Unstable)
Added tag(s) pending.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
816210: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=816210
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#814167: lwjgl: (Build-)Depends on OpenJDK 7

[Michael Gilbert]

> I have switched the build-dependency to default-jdk and changed
> JAVA_HOME in debian/rules accordingly. However the package FTBFS with
> OpenJDK 8. I guess packaging the latest upstream release would be the
> best option.

2.9.3 is supposed to support building without ant.  I looked at it a
while ago, and it isn't quite that simple.

lwjgl3 is also available, but it has a huge dependency stack with
almost none of it in Debian yet.

I have less interest in lwjgl now than I used to, and I may not be
able to find the time to work on it.

Best wishes,
Mike

Bug#812087: pcscd takes 100 % cpu each time I insert a mass storage USB key

[gustavo panizzo]

Package: pcscd
Version: 1.8.15-1
Followup-For: Bug #812087

Hello

I just want to provide more information about the issue, I have an
SmartCard reader (ok, it is usb internally) and a g10 smartcard.
I can reproduce the issue plugging my phone as MTP device.

If I had my phone connected while I started pcscd when I unplug it, pcscd
takes 100% of the CPU too.



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

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

Versions of packages pcscd depends on:
ii  init-system-helpers 1.28
ii  libc6   2.19-22
ii  libccid [pcsc-ifd-handler]  1.4.22-1
ii  libpcsclite11.8.15-1
ii  libudev1228-6
ii  lsb-base9.20160110

pcscd recommends no packages.

Versions of packages pcscd suggests:
ii  systemd  228-6

-- no debconf information

Bug#817208: Cannot load library /usr/lib/kde4/kio_digikamdates.so

[Ryan Kavanagh]

Package: digikam
Version: 4:4.14.0-3
Severity: grave
Justification: renders package unusable

As of today, digikam no longer displays any pictures from my albums.

The following errors can be found in ~/.xsession-errors:

Could not open library '/usr/lib/kde4/kio_digikamdates.so'.
Cannot load library /usr/lib/kde4/kio_digikamdates.so: 
(/lib/x86_64-linux-gnu/libresolv.so.2: symbol __h_errno, version GLIBC_PRIVATE 
not defined in file libc.so.6 with link time reference)
Could not open library '/usr/lib/kde4/kio_digikamalbums.so'.
Cannot load library /usr/lib/kde4/kio_digikamalbums.so: 
(/lib/x86_64-linux-gnu/libresolv.so.2: symbol __h_errno, version GLIBC_PRIVATE 
not defined in file libc.so.6 with link time reference)

The following errors are printed to stderr:

digikam(22075): couldn't create slave: "Unable to create io-slave:
klauncher said: Error loading 'kio_digikamdates'.
"
digikam(22075)/digikam (core) Digikam::AlbumManager::slotDatesJobResult: Failed 
to list dates
digikam(22075)/digikam (core) Digikam::DNotificationWrapper: parent is null
digikam(22075): couldn't create slave: "Unable to create io-slave:
klauncher said: Error loading 'kio_digikamalbums'.
"
digikam(22075)/digikam (core) Digikam::ImageAlbumModel::slotResult: Failed to 
list url:  "Could not start process Unable to create io-slave:
klauncher said: Error loading 'kio_digikamalbums'.
."

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

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

Versions of packages digikam depends on:
ii  digikam-data4:4.14.0-3
ii  digikam-private-libs4:4.14.0-3
ii  kde-runtime 4:15.08.3-1+b1
ii  libc6   2.22-1
ii  libgcc1 1:5.3.1-11
ii  libgphoto2-62.5.9-3
ii  libgphoto2-port12   2.5.9-3
ii  libkdcraw23 4:15.08.0-1+b1
ii  libkdecore5 4:4.14.14-1+b1
ii  libkdeui5   4:4.14.14-1+b1
ii  libkexiv2-114:15.04.3-1
ii  libkhtml5   4:4.14.14-1+b1
ii  libkio5 4:4.14.14-1+b1
ii  libkipi11   4:15.08.3-1
ii  libknotifyconfig4   4:4.14.14-1+b1
ii  libkparts4  4:4.14.14-1+b1
ii  libopencv-core2.4v5 2.4.9.1+dfsg-1.3
ii  libopencv-imgproc2.4v5  2.4.9.1+dfsg-1.3
ii  libphonon4  4:4.8.3-2
ii  libqt4-dbus 4:4.8.7+dfsg-6
ii  libqt4-sql  4:4.8.7+dfsg-6
ii  libqt4-sql-sqlite   4:4.8.7+dfsg-6
ii  libqt4-xml  4:4.8.7+dfsg-6
ii  libqtcore4  4:4.8.7+dfsg-6
ii  libqtgui4   4:4.8.7+dfsg-6
ii  libsolid4   4:4.14.14-1+b1
ii  libstdc++6  5.3.1-11
ii  libthreadweaver44:4.14.14-1+b1
ii  perl5.22.1-8
ii  phonon  4:4.8.3-2

Versions of packages digikam recommends:
ii  chromium [www-browser]  49.0.2623.75-2
pn  ffmpegthumbs | mplayerthumbs
ii  google-chrome-stable [www-browser]  49.0.2623.87-1
ii  iceweasel [www-browser] 44.0.2-1
pn  kipi-plugins
ii  lynx [www-browser]  2.8.9dev8-4
ii  w3m [www-browser]   0.5.3-27

Versions of packages digikam suggests:
pn  digikam-doc 
pn  systemsettings  

-- no debconf information

-- 
|_)|_/  Ryan Kavanagh   | Debian Developer
| \| \  https://ryanak.ca/  | GPG Key 4A11C97A


signature.asc
Description: PGP signature

Bug#813571: marked as done (virtualenv: Broken dependencies)

[Debian Bug Tracking System]

Your message dated Tue, 8 Mar 2016 19:12:03 -0500
with message-id <20160308191203.4d7eb...@subdivisions.wooz.org>
and subject line 
has caused the Debian Bug report #813571,
regarding virtualenv: Broken dependencies
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
813571: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=813571
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: virtualenv
Version: 1.11.6+ds-1
Severity: grave
Justification: renders package unusable

Dear Maintainer,

I'm trying to install virtualenv on Sid. It depends on python3-virtualenv, that
depends on python-setuptools-whl *and* python-pip-whl. But python-pip-whl
(8.0.2-2) breaks python-setuptools-whl >=18.8-1, which is the version in Sid
repo. If I install python-setuptools-whl, apt-get removes python-pip-whl. So I
can't install python3-virtualenv neither python-virtualenv.

Thanks in advance.



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

Kernel: Linux 4.3.0-1-amd64 (SMP w/8 CPU cores)
Locale: LANG=es_ES.UTF-8, LC_CTYPE=es_ES.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
--- End Message ---
--- Begin Message ---
Should be resolved with python-virtualenv 15.0.0+ds-1 and python-pip 8.1.0-1


pgpyVkN46vVpO.pgp
Description: OpenPGP digital signature
--- End Message ---

Bug#813571: (no subject)

[Barry Warsaw]

I think this should now all be sorted out with python-virtualenv 15.0.0+ds-1
and python-pip 8.1.0-1.  I'm going to close this bug but if you're still
having a problem with those new versions, please reopen it.

Bug#815125: Boot failure with Debian linux 4.4.2 package

[Alexis Murzeau]

2016-03-04 14:07 GMT+01:00 Matt Fleming :
>
> It must have been a herculean effort to take photos of the screen
> while the buggy kernel booted. Thank you!
>
> I'm not really seeing anything jumping out as obviously wrong apart
> from the fact that we don't have all of EFI_CONVENTIONAL_MEMORY mapped
> in the buggy kernel.
>
> Could you try this patch?
>
> ---
>
> diff --git a/arch/x86/platform/efi/efi_64.c b/arch/x86/platform/efi/efi_64.c
> index 49e4dd4a1f58..f5e77d240ff1 100644
> --- a/arch/x86/platform/efi/efi_64.c
> +++ b/arch/x86/platform/efi/efi_64.c
> @@ -241,15 +241,6 @@ int __init efi_setup_page_tables(unsigned long 
> pa_memmap, unsigned num_pages)
> efi_scratch.use_pgd = true;
>
> /*
> -* When making calls to the firmware everything needs to be 1:1
> -* mapped and addressable with 32-bit pointers. Map the kernel
> -* text and allocate a new stack because we can't rely on the
> -* stack pointer being < 4GB.
> -*/
> -   if (!IS_ENABLED(CONFIG_EFI_MIXED))
> -   return 0;
> -
> -   /*
>  * Map all of RAM so that we can access arguments in the 1:1
>  * mapping when making EFI runtime calls.
>  */
> @@ -268,6 +259,15 @@ int __init efi_setup_page_tables(unsigned long 
> pa_memmap, unsigned num_pages)
> }
> }
>
> +   /*
> +* When making calls to the firmware everything needs to be 1:1
> +* mapped and addressable with 32-bit pointers. Map the kernel
> +* text and allocate a new stack because we can't rely on the
> +* stack pointer being < 4GB.
> +*/
> +   if (!IS_ENABLED(CONFIG_EFI_MIXED))
> +   return 0;
> +
> page = alloc_page(GFP_KERNEL|__GFP_DMA32);
> if (!page)
> panic("Unable to allocate EFI runtime stack < 4GB\n");

Thanks for you suggestion.
Unfortunately, this patch doesn't make it works, the crash still
occurs (at the same RIP and traceback).

Using /dev/mem on a running system (with kernel 4.3), the memory
around RIP (0xaa9462ee) is :
aa9462d0  sub rsp,0x28
aa9462d4  lea rdx,[rip+0x2445] # 0xaa948720
aa9462db  mov ecx,0x4
aa9462e0  call func_aa9447c0  ; call to ConvertPointer(4, & 0xaa948720)
aa9462e5  mov r11,QWORD PTR [rip+0x2434] # 0xaa948720
aa9462ec  xor eax,eax
aa9462ee  mov BYTE PTR [r11+0x1],0x1
aa9462f3  add rsp,0x28
aa9462f7  ret

The QWORD at address 0xaa948720 is 0 though on the running system.

I will try to investigate more but I'm open to any printk / patch tests.

Alexis Murzeau

Processed: qgis install fails trying to overwrite /usr/bin/qbrowser.bin

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> severity 817176 serious
Bug #817176 [qgis] qgis install fails trying to overwrite /usr/bin/qbrowser.bin
Severity set to 'serious' from 'important'
> severity 817178 serious
Bug #817178 [qgis] qgis uninstallable on unstable
Severity set to 'serious' from 'grave'
> tags 817176 confirmed
Bug #817176 [qgis] qgis install fails trying to overwrite /usr/bin/qbrowser.bin
Added tag(s) confirmed.
> tags 817178 confirmed
Bug #817178 [qgis] qgis uninstallable on unstable
Added tag(s) confirmed.
> merge 817176 817178
Bug #817176 [qgis] qgis install fails trying to overwrite /usr/bin/qbrowser.bin
Bug #817178 [qgis] qgis uninstallable on unstable
Merged 817176 817178
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
817176: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=817176
817178: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=817178
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#817178: qgis install fails trying to overwrite /usr/bin/qbrowser.bin

[Sebastiaan Couwenberg]

severity 817176 serious
severity 817178 serious
tags 817176 confirmed
tags 817178 confirmed
merge 817176 817178
thanks

Hi Ben & Stefano,

Sorry for breaking the upgrade. Unfortunately my piuparts tests didn't
catch this issue.

On 08-03-16 19:56, Ben Caradoc-Davies wrote:
> Workaround is to manually remove the diversions:
> 
> dpkg-divert --remove /usr/bin/qgis
> dpkg-divert --remove /usr/bin/qbrowser
> 
> Note that this was an upgrade from the previous qgis on unstable.

The qgis.preinst maintainer script should remove the old diversions. It
was used pre-2.8 to support multiple GRASS versions. The new GRASS
support in post 2.8 doesn't need the diversions any more.

I'm currently trying to figure out why the removal of the diversions is
not working as expected, I hope to have a fix ready soon.

On Tue, 8 Mar 2016 19:48:35 +0100 (CET) Stefano Costa wrote:
> after the failed installation I'm left with this binary:
>
> steko@spheniscus:~$ ls -l /usr/bin/qgis.bin.dpkg-new
> -rwxr-xr-x 1 root root 250 mar 8 08:10 /usr/bin/qgis.bin.dpkg-new

The .dpkg-new files should go away after the upgrade succeeds, but you
need to either remove the diversion manually (with the above dpkg-divert
commands) and continue the upgrade, or wait for the fixed version.

Kind Regards,

Bas

-- 
 GPG Key ID: 4096R/6750F10AE88D4AF1
Fingerprint: 8182 DE41 7056 408D 6146  50D1 6750 F10A E88D 4AF1

Bug#796404: marked as done (guessit: FTBFS: TypeError: load_tests() takes exactly 3 arguments (0 given))

[Debian Bug Tracking System]

Your message dated Tue, 08 Mar 2016 23:27:54 +
with message-id 
and subject line Bug#796404: fixed in guessit 0.11.0-1
has caused the Debian Bug report #796404,
regarding guessit: FTBFS:  TypeError: load_tests() takes exactly 3 arguments (0 
given)
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
796404: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=796404
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: guessit
Version: 0.10.3-1
Severity: serious
Justification: fails to build from source
User: reproducible-bui...@lists.alioth.debian.org
Usertags: ftbfs
X-Debbugs-Cc: reproducible-bui...@lists.alioth.debian.org

Dear Maintainer,

guessit fails to build from source in unstable/amd64:

  [..]

  ==
  ERROR: guessit.test.test_doctests.load_tests
  --
  Traceback (most recent call last):
File "/usr/lib/python2.7/dist-packages/nose/case.py", line 197, in
runTest
  self.test(*self.arg)
  TypeError: load_tests() takes exactly 3 arguments (0 given)
  
  --
  Ran 47 tests in 23.756s
  
  FAILED (errors=1)
  E: pybuild pybuild:262: test: plugin distutils failed with: exit
  code=1

  [..]

The full build log is attached or can be viewed here:


https://reproducible.debian.net/logs/unstable/amd64/guessit_0.10.3-1.build1.log.gz


Regards,

-- 
  ,''`.
 : :'  : Chris Lamb
 `. `'`  la...@debian.org / chris-lamb.co.uk
   `-
I: using fakeroot in build.
I: pbuilder: network access will be disabled during build
I: Current time: Fri Aug 21 06:23:04 GMT+12 2015
I: pbuilder-time-stamp: 1440181384
I: Building the build Environment
I: extracting base tarball [/var/cache/pbuilder/unstable-reproducible-base.tgz]
I: creating local configuration
I: copying local configuration
I: mounting /proc filesystem
I: mounting /run/shm filesystem
I: mounting /dev/pts filesystem
I: Mounting /dev/shm
I: Mounting /sys
I: policy-rc.d already exists
I: Installing the build-deps
 -> Attempting to satisfy build-dependencies
 -> Creating pbuilder-satisfydepends-dummy package
Package: pbuilder-satisfydepends-dummy
Version: 0.invalid.0
Architecture: amd64
Maintainer: Debian Pbuilder Team 
Description: Dummy package to satisfy dependencies with aptitude - created by 
pbuilder
 This package was created automatically by pbuilder to satisfy the
 build-dependencies of the package being currently built.
Depends: debhelper (>= 9), dh-python, python-all (>= 2.6.6-6~), 
python-babelfish, python-dateutil (>= 2.1), python-nose, python-pkg-resources, 
python-requests, python-setuptools, python-stevedore, python-yaml, python3-all, 
python3-babelfish, python3-dateutil (>= 2.1), python3-nose, 
python3-pkg-resources, python3-requests, python3-setuptools, python3-stevedore, 
python3-yaml
dpkg-deb: building package 'pbuilder-satisfydepends-dummy' in 
'/tmp/satisfydepends-aptitude/pbuilder-satisfydepends-dummy.deb'.
Selecting previously unselected package pbuilder-satisfydepends-dummy.
(Reading database ... 20247 files and directories currently installed.)
Preparing to unpack .../pbuilder-satisfydepends-dummy.deb ...
Unpacking pbuilder-satisfydepends-dummy (0.invalid.0) ...
dpkg: pbuilder-satisfydepends-dummy: dependency problems, but configuring 
anyway as you requested:
 pbuilder-satisfydepends-dummy depends on dh-python; however:
  Package dh-python is not installed.
 pbuilder-satisfydepends-dummy depends on python-all (>= 2.6.6-6~); however:
  Package python-all is not installed.
 pbuilder-satisfydepends-dummy depends on python-babelfish; however:
  Package python-babelfish is not installed.
 pbuilder-satisfydepends-dummy depends on python-dateutil (>= 2.1); however:
  Package python-dateutil is not installed.
 pbuilder-satisfydepends-dummy depends on python-nose; however:
  Package python-nose is not installed.
 pbuilder-satisfydepends-dummy depends on python-pkg-resources; however:
  Package python-pkg-resources is not installed.
 pbuilder-satisfydepends-dummy depends on python-requests; however:
  Package python-requests is not installed.
 pbuilder-satisfydepends-dummy depends on python-setuptools; however:
  Package python-setuptools is not installed.
 pbuilder-satisfydepends-
Setting up pbuilder-satisfydepends-dummy (0.invalid.0) ...
Reading package lists...
Building dependency tree...
Reading state information...

Bug#817199: transcode: should this package be removed?

[Sebastian Ramacher]

Package: transcode
Version: 3:1.1.7-9
Severity: serious
Tags: sid stretch

transcode is dead upstream since many years and it is also no longer really
maintained Debian. We just keep sticking patches on top of it. I suppose most of
its use-cases are also covered by other tools already available in Debian. Also,
support for modern containers like mp4 is still very limited. So I think it's
time to let it go.

What do you think?

Cheers
-- 
Sebastian Ramacher


signature.asc
Description: PGP signature

Bug#817057: network-manager-openconnect: Update unstable version to latest Upstream Build

[Mike Miller]

Control: severity -1 important

On Tue, Mar 08, 2016 at 08:04:42 +0100, Michael Stapelberg wrote:
> Thanks for clarifying the issue you’re seeing. I don’t think this is
> related to the D-Bus changes.
> 
> Also, to be clear: I’m not the maintainer of this package, I sponsored
> mtmiller@’s uploads, who maintains the package.

Thanks for responding for me ;)

Yikes, out of order quoting:

> On Tue, Mar 8, 2016 at 3:09 AM, Ryan Chewning  wrote:
> > On Mon, Mar 7, 2016 at 12:22 PM, Michael Stapelberg  >>>
> >>> The latest builds of networkmanager in testing/unstable no longer
> >>> support dbus. https://blogs.gnome.org/dcbw/2016/02/19/die-dbus-glib-die/
> >>>
> >>
> >> I’m only a bystander for the purpose of this bug, but “networkmanager […]
> >> no longer supports dbus” conflicts with the article you refer to, which
> >> mentions:
> >>
> >> """
> >> I cannot understate how much work this was and how much careful planning
> >> we (well, mostly Dan Winship) did to ensure we didn’t break backwards
> >> compatibility of either the utility libraries or the D-Bus interface.
> >> """
> >>
> >> The way I read this, the new networkmanager version is
> >> backwards-compatible with regards to its D-Bus interface.
> >>
> >> Can you clarify? If it turns out that it’s actually backwards-compatible,
> >> is severity: grave still justified?

My understanding is that it is backwards-compatible (e.g. I am still
able to connect via nm-openconnect on my system). However, they do seem
to have dropped support for old-style plugins in the
nm-connection-editor, possibly nm-applet. I use gnome-shell which still
allows me to create, edit, and connect to OpenConnect VPNs perfectly.

I'm downgrading to important. Request for a new version would normally
be wishlist. This package is still mostly working for users with
existing VPNs or who use gnome-shell or manage VPNs with keyfiles
manually, but not for nm-applet users.

> >>> There is an updated version of the network-manager-openconnect but it is
> >>> failing to be pulled down by uscan. Manual intervention is needed.

JFTR, manual intervention is always required. I don't know why the
tracker and udd are reporting upstream failures, uscan works locally for
me, but that's a separate issue (if I understand what you meant).

-- 
mike

Processed: Re: Bug#817057: network-manager-openconnect: Update unstable version to latest Upstream Build

[Debian Bug Tracking System]

Processing control commands:

> severity -1 important
Bug #817057 [network-manager-openconnect] network-manager-openconnect: Update 
unstable version to latest Upstream Build
Severity set to 'important' from 'grave'

-- 
817057: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=817057
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#816882: marked as done (ruby-websocket-driver: must depend on ruby-websocket-extensions)

[Debian Bug Tracking System]

Your message dated Tue, 08 Mar 2016 22:15:15 +
with message-id 
and subject line Bug#816882: fixed in ruby-websocket-driver 0.6.3-2
has caused the Debian Bug report #816882,
regarding ruby-websocket-driver: must depend on ruby-websocket-extensions
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
816882: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=816882
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: ruby-websocket-driver
Version: 0.6.3-1+b1
Severity: grave
Justification: renders package unusable

Dear Maintainer,

ruby-websocket-driver has missing dependency on ruby-websocket-extensions, so
it's impossible to use it.

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

Kernel: Linux 3.16.0-4-amd64 (SMP w/4 CPU cores)
Locale: LANG=be_BY.utf8, LC_CTYPE=be_BY.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: sysvinit (via /sbin/init)
--- End Message ---
--- Begin Message ---
Source: ruby-websocket-driver
Source-Version: 0.6.3-2

We believe that the bug you reported is fixed in the latest version of
ruby-websocket-driver, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 816...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Christian Hofstaedtler  (supplier of updated 
ruby-websocket-driver package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Tue, 08 Mar 2016 21:02:33 +
Source: ruby-websocket-driver
Binary: ruby-websocket-driver
Architecture: source
Version: 0.6.3-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Ruby Extras Maintainers 

Changed-By: Christian Hofstaedtler 
Description:
 ruby-websocket-driver - WebSocket protocol handler with pluggable I/O
Closes: 816882
Changes:
 ruby-websocket-driver (0.6.3-2) unstable; urgency=medium
 .
   * Team upload.
 .
   [ Christian Hofstaedtler ]
   * Drop old style debug package.
   * Refresh packaging using dh-make-ruby -w.
 .
   [ Cédric Boutillier ]
   * Bump debhelper compatibility level to 9
   * Use https:// in Vcs-* fields
   * Bump Standards-Version to 3.9.7 (no changes needed)
   * Run wrap-and-sort on packaging files
 .
   [ Hleb Valoshka ]
   * Add ruby-websocket-extensions to dependencies (Closes: #816882)
Checksums-Sha1:
 34a15b480f57643ae625dadad0d9226d9e1bb45d 2198 ruby-websocket-driver_0.6.3-2.dsc
 4bfd21d494758785096780d3543d41367f0b9fb3 2580 
ruby-websocket-driver_0.6.3-2.debian.tar.xz
Checksums-Sha256:
 f08e4ba7b175dfe5e2064778e2a18992338f0cd584e69063fd421b987d6244d4 2198 
ruby-websocket-driver_0.6.3-2.dsc
 f6229e5ed1c4fc2fcde7f671f00f2665a050c9c0bf278c02bd33fe8e6b026e68 2580 
ruby-websocket-driver_0.6.3-2.debian.tar.xz
Files:
 3249e40dadf88657a1419386a3958f4d 2198 ruby optional 
ruby-websocket-driver_0.6.3-2.dsc
 38835ef273cf336412a3c8d9106b2777 2580 ruby optional 
ruby-websocket-driver_0.6.3-2.debian.tar.xz

-BEGIN PGP SIGNATURE-
Version: GnuPG v1

iQIcBAEBCAAGBQJW3z6TAAoJEFwT1tuTBS4DeTAP/3fZ3vQIB5oSnUf/K4KACn9T
QctFuFGcipkheYcGjzUgCZaoZZd1sgGRmiMXt0KHX/9yxIzgDzewzIlTeBUQkUjJ
CYz9rpqlecveC93/nJi2cr9aorvfEdcxZoqS2osTp9fPbB9CFlW7k6ORADEgD8L7
8GEuTOMzhgSLPunVkurutQVKpVxvHK66SEPezYjU9PHj+k03kNPXw/XVXFmjRC2X
YxJX06EJtr+VlfPmPnQ3pBTEvlvIPSn1WRorUSuLqhDdCfVwpHyfTgnL5gvdFRcA
gNSsY1kl3lfhkGRvXHIBDLzFIOz095IOkxhcM6NB2bG5g4Q9PuzmFGMad+KIGrWB
eG8wKDjERtpV7mo7tlyPLJNK1YyBjrL0YU0DjqbY0xUDD6Z6zZPPnVRVDxDPPOXU
eQSjoSKP/UHnZpmDZ1qw2O8t4UmGlApfDJzDEPJbnIOkC9+jkK2UDTrCP6/6qs4y
Tk5s1j/piPmosggwaqCtJwWuhD1CIPAiTt2V2onnzy6G+3Af4jaL2bHgbOdc+2sv
pFeoWROpCy1nTdXnWq0k6LjDrbDoFTKUWT7Fw7VLPHjmaFO6p26C8TJdDgegLN4K
ePtTUIH5HtfKhgG1s1n8xR8VTkQU/IDeGb+UMT1ZuwUIenyS1rTAuHcFrTUtkRiZ
8Na1JvUnS4ohmZS3bRVr
=5jlu
-END PGP SIGNATURE End Message ---

Bug#816625: marked as done (jasper: CVE-2016-1577: double free vulnerability in the jas_iccattrval_destroy function)

[Debian Bug Tracking System]

Your message dated Tue, 08 Mar 2016 21:55:25 +
with message-id 
and subject line Bug#816625: fixed in jasper 1.900.1-13+deb7u4
has caused the Debian Bug report #816625,
regarding jasper: CVE-2016-1577: double free vulnerability in the 
jas_iccattrval_destroy function
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
816625: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=816625
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: jasper
Version: 1.900.1-7
Severity: grave
Tags: security upstream

Hi,

the following vulnerability was published for jasper.

CVE-2016-1577[0]:
double free vulnerability in the jas_iccattrval_destroy function

If you fix the vulnerability please also make sure to include the
CVE (Common Vulnerabilities & Exposures) id in your changelog entry.

For further information see:

[0] https://security-tracker.debian.org/tracker/CVE-2016-1577

Regards,
Salvatore
--- End Message ---
--- Begin Message ---
Source: jasper
Source-Version: 1.900.1-13+deb7u4

We believe that the bug you reported is fixed in the latest version of
jasper, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 816...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Salvatore Bonaccorso  (supplier of updated jasper package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sun, 06 Mar 2016 15:09:28 +0100
Source: jasper
Binary: libjasper1 libjasper-dev libjasper-runtime
Architecture: source amd64
Version: 1.900.1-13+deb7u4
Distribution: wheezy-security
Urgency: high
Maintainer: Roland Stigge 
Changed-By: Salvatore Bonaccorso 
Description: 
 libjasper-dev - Development files for the JasPer JPEG-2000 library
 libjasper-runtime - Programs for manipulating JPEG-2000 files
 libjasper1 - JasPer JPEG-2000 runtime library
Closes: 812978 816625 816626
Changes: 
 jasper (1.900.1-13+deb7u4) wheezy-security; urgency=high
 .
   * Non-maintainer upload by the Security Team.
   * CVE-2016-1577: Prevent double-free in jas_iccattrval_destroy()
 (Closes: #816625)
   * CVE-2016-2089: matrix rows_ NULL pointer dereference in jas_matrix_clip()
 (Closes: #812978)
   * CVE-2016-2116: Prevent jas_stream_t memory leak in
 jas_iccprof_createfrombuf() (Closes: #816626)
Checksums-Sha1: 
 2a5b39408c15fe975d5b349ce9a419cd287c 1878 jasper_1.900.1-13+deb7u4.dsc
 485ed72f72da1b2092fb4f4217580f9a34630fc3 34913 
jasper_1.900.1-13+deb7u4.debian.tar.gz
 b804f5eeb5e6cb00f2436d133145238007a12eaf 160230 
libjasper1_1.900.1-13+deb7u4_amd64.deb
 22e63a35ee293bf2c37ec271e31ec6d603b7c308 569330 
libjasper-dev_1.900.1-13+deb7u4_amd64.deb
 a6501e43744c1ea26fcac1d73a6a50bf7bca263a 27404 
libjasper-runtime_1.900.1-13+deb7u4_amd64.deb
Checksums-Sha256: 
 45322a04fbbdfdba0f58747417fd92bf07e7ffcf612695c095c02c2b87a21cbe 1878 
jasper_1.900.1-13+deb7u4.dsc
 61049f1047774db9abdc399dcc8c8eb153bba15dddc81c1b95e7e973c6765c6d 34913 
jasper_1.900.1-13+deb7u4.debian.tar.gz
 8c92d4be18de78060fa888d506c290dd5162397979d858f318508c10225e6660 160230 
libjasper1_1.900.1-13+deb7u4_amd64.deb
 32a83763556a28ca0f2dbaff434cd0710ac68952a316271213e028cdc19c4eb9 569330 
libjasper-dev_1.900.1-13+deb7u4_amd64.deb
 98118f1e51119f3cf8cdc892b021c1809e830ea56873eff16a59ed6868489490 27404 
libjasper-runtime_1.900.1-13+deb7u4_amd64.deb
Files: 
 db90675529886eb7523042aa6733604f 1878 graphics optional 
jasper_1.900.1-13+deb7u4.dsc
 dcde5273ae8c4104535af22256f1fd85 34913 graphics optional 
jasper_1.900.1-13+deb7u4.debian.tar.gz
 10f4a6e7ded8f06075694d588621a69a 160230 libs optional 
libjasper1_1.900.1-13+deb7u4_amd64.deb
 8aeb17922bcf60467da1f707dbc866b0 569330 libdevel optional 
libjasper-dev_1.900.1-13+deb7u4_amd64.deb
 afa8d77c698a502158a2d8c4fa1b3da7 27404 graphics optional 
libjasper-runtime_1.900.1-13+deb7u4_amd64.deb

-BEGIN PGP SIGNATURE-
Version: GnuPG v1

iQIcBAEBCgAGBQJW3DrJAAoJEAVMuPMTQ89Ej6kP/iFcRx8a0D5E/u7WKCYx7bYM
BrTuk51VKzMkMkd4P9mT2drmSMpBBQSslXIiQF+qfexarvpljdabSaBlzwo6dIeS
eT5q6yQxyYQRCjIkLz/au0Q9fkWFhU4WjDGD81j2BpY4DNHQmTcD1FUlORUmBFqC

Bug#815125: Boot failure with Debian linux 4.4.2 package

[Scott Ashcroft]

The patch makes no difference.
Is there anything else I can do to help figure this out?

Cheers,
Scott

Bug#816625: marked as done (jasper: CVE-2016-1577: double free vulnerability in the jas_iccattrval_destroy function)

[Debian Bug Tracking System]

Your message dated Tue, 08 Mar 2016 21:47:09 +
with message-id 
and subject line Bug#816625: fixed in jasper 1.900.1-debian1-2.4+deb8u1
has caused the Debian Bug report #816625,
regarding jasper: CVE-2016-1577: double free vulnerability in the 
jas_iccattrval_destroy function
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
816625: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=816625
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: jasper
Version: 1.900.1-7
Severity: grave
Tags: security upstream

Hi,

the following vulnerability was published for jasper.

CVE-2016-1577[0]:
double free vulnerability in the jas_iccattrval_destroy function

If you fix the vulnerability please also make sure to include the
CVE (Common Vulnerabilities & Exposures) id in your changelog entry.

For further information see:

[0] https://security-tracker.debian.org/tracker/CVE-2016-1577

Regards,
Salvatore
--- End Message ---
--- Begin Message ---
Source: jasper
Source-Version: 1.900.1-debian1-2.4+deb8u1

We believe that the bug you reported is fixed in the latest version of
jasper, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 816...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Salvatore Bonaccorso  (supplier of updated jasper package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sun, 06 Mar 2016 14:49:44 +0100
Source: jasper
Binary: libjasper1 libjasper-dev libjasper-runtime
Architecture: source
Version: 1.900.1-debian1-2.4+deb8u1
Distribution: jessie-security
Urgency: high
Maintainer: Roland Stigge 
Changed-By: Salvatore Bonaccorso 
Closes: 812978 816625 816626
Description: 
 libjasper-dev - Development files for the JasPer JPEG-2000 library
 libjasper-runtime - Programs for manipulating JPEG-2000 files
 libjasper1 - JasPer JPEG-2000 runtime library
Changes:
 jasper (1.900.1-debian1-2.4+deb8u1) jessie-security; urgency=high
 .
   * Non-maintainer upload by the Security Team.
   * CVE-2016-1577: Prevent double-free in jas_iccattrval_destroy()
 (Closes: #816625)
   * CVE-2016-2089: matrix rows_ NULL pointer dereference in jas_matrix_clip()
 (Closes: #812978)
   * CVE-2016-2116: Prevent jas_stream_t memory leak in
 jas_iccprof_createfrombuf() (Closes: #816626)
Checksums-Sha1: 
 3e5ce30f9c10320f62b00fc6fe723d81afb883a8 1955 
jasper_1.900.1-debian1-2.4+deb8u1.dsc
 3b49b1c9ea30c969f608c52e62bf2b743a9769e1 1140771 
jasper_1.900.1-debian1.orig.tar.gz
 c600341ea2cb5be9ee8665bfaf7b3a9df2555f7f 30260 
jasper_1.900.1-debian1-2.4+deb8u1.debian.tar.xz
Checksums-Sha256: 
 52e8e9c7164dad5d3e4f68ae14322b4602255eb7a02af347f97a9592d449c685 1955 
jasper_1.900.1-debian1-2.4+deb8u1.dsc
 7276e8407080d8263b39aeac8305032b0534c7df25bf02718b3944711e3c81d7 1140771 
jasper_1.900.1-debian1.orig.tar.gz
 995382b8f98a4226c0555a99a7fef938ef5ab04f646c400485cac07ddc53beb6 30260 
jasper_1.900.1-debian1-2.4+deb8u1.debian.tar.xz
Files: 
 26447f2a9ef85e3892fade8d66f84ff8 1955 graphics optional 
jasper_1.900.1-debian1-2.4+deb8u1.dsc
 d6aa5f1638d703cb03beb996b713ec6c 1140771 graphics optional 
jasper_1.900.1-debian1.orig.tar.gz
 ca96ce1cb3b096cbf4dd69c101127b21 30260 graphics optional 
jasper_1.900.1-debian1-2.4+deb8u1.debian.tar.xz

-BEGIN PGP SIGNATURE-
Version: GnuPG v1

iQIcBAEBCgAGBQJW3DkvAAoJEAVMuPMTQ89Eu1MP/Anx2AT9qP+ZWI37kQd4TwpB
urxKjSRMBAJ3ND9JrVPOM2kJ0yvTE91/nlhdK4a+0h8QCh2v398/COqToiYibH+8
W9CeeHXuEU7kDAivKJlt8S2Xl35ku4+nTFCCXtAeQvmcNxoHRpJLF/VgAmdEPpgg
jn0B103gbi/OB9oS9nZNMupY0Uq1vsHL6QBf2fTwYXdUM3r6dnTyU8TUWCx8lrDC
NIzeY8qv6t0g5zfcJhmgDwUunI1oFTlfBqRNKNkcr+weNCkhW1B8Kr9o0F/qDL/r
wFCxasaEEKZIau7KbxNVmm+Ppj8Y0jyi7OgnbDD+l/5g1TxDKR87P+GVOvnzMMEn
jBqFA9dNeXxbPdVxlYvqVXh9Aw8lkLIxlEtiFamcsRiKdNLkxrvRHWbjawSp6hqM
mI3X9rDCsy/dPyUfMDMp2pq6SevAqBzkl2hRqftyJfLG+VFQBNz4yE9g++yczIp/
jP207ME9c94HT/W7NS3Uu1tza2PjOf7PdbmF2k8rq17h2tip5qWu6w2VcRk9G6g1
y/VQ8pi6xkI3pSLO7StGtZK3YJLfdP6Og3QNJiHIlEkc6uHcyPeE6aZNKnc2J7bX
qlNFt0QDj3GY5ulCw6KvwCf2mQfYGqn1TOl4PcKAHqIEygDojZRWIC8ZkEPAsgz7
68n8+2ps2fqZOeB6rM2P
=+NQV
-END PGP SIGNATURE 

Bug#792321: Darlehen Angebot

[franczak . mariola]

Das Aspire Gelddarlehen bieten wir 3% für Business-Darlehen und persönliche 
Darlehen,

Füllen Sie das Formular aus, wenn interessiert

Vollständiger Name:
Sex:
Land:
Erforderliche Kreditbetrag :
Dauer:

Maria Enzo

Bug#814167: lwjgl: (Build-)Depends on OpenJDK 7

[Markus Koschany]

Control: tags -1 confirmed

On Mon, 08 Feb 2016 20:27:30 + Matthias Klose  wrote:
> Package: src:lwjgl
> Version: 2.7.1+dfsg-5
> Severity: serious
> User: debian-j...@lists.debian.org
> Usertags: openjdk-8-transition
> 
> The package build-depends or depends one an openjdk-7-* package,
> which is scheduled for removal for stretch.  Please do not depend
> on a specific openjdk version, but on one of the default-java,
> default-java-headless or default-jdk packages instead.
> 
> default-java defaulting to openjdk-8 on most architectures is now
> available in unstable.

I have switched the build-dependency to default-jdk and changed
JAVA_HOME in debian/rules accordingly. However the package FTBFS with
OpenJDK 8. I guess packaging the latest upstream release would be the
best option.

Markus



signature.asc
Description: OpenPGP digital signature

Processed: user debian...@lists.debian.org, usertagging 817112, found 817112 in 0.4.0-4, found 817139 in 3.3.2-3 ...

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> user debian...@lists.debian.org
Setting user to debian...@lists.debian.org (was a...@debian.org).
> usertags 817112 piuparts
There were no usertags set.
Usertags are now: piuparts.
> found 817112 0.4.0-4
Bug #817112 [libvirglrenderer-dev,libvirglrenderer0] libvirglrenderer0 and 
libvirglrenderer-dev: error when trying to install together
Marked as found in versions virglrenderer/0.4.0-4.
> found 817139 3.3.2-3
Bug #817139 [sassc,pysassc] sassc: trying to overwrite 
'/usr/share/man/man1/sassc.1.gz', which is also in package pysassc 0.9.3-1
There is no source info for the package 'pysassc' at version '3.3.2-3' with 
architecture ''
Marked as found in versions sassc/3.3.2-3.
> found 817139 0.9.3-1
Bug #817139 [sassc,pysassc] sassc: trying to overwrite 
'/usr/share/man/man1/sassc.1.gz', which is also in package pysassc 0.9.3-1
There is no source info for the package 'sassc' at version '0.9.3-1' with 
architecture ''
Marked as found in versions libsass-python/0.9.3-1.
> tags 817139 + sid
Bug #817139 [sassc,pysassc] sassc: trying to overwrite 
'/usr/share/man/man1/sassc.1.gz', which is also in package pysassc 0.9.3-1
Added tag(s) sid.
> found 816700 1.8.2-2
Bug #816700 [cups-filters] foomatic-filters-beh and cups-filters: error when 
trying to install together
Marked as found in versions cups-filters/1.8.2-2.
> affects 816700 + foomatic-filters-beh
Bug #816700 [cups-filters] foomatic-filters-beh and cups-filters: error when 
trying to install together
Added indication that 816700 affects foomatic-filters-beh
> tags 817154 + sid stretch
Bug #817154 [libnih1] libnih1: uninstallable in unstable
Added tag(s) stretch and sid.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
816700: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=816700
817112: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=817112
817139: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=817139
817154: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=817154
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Processed: Re: lwjgl: (Build-)Depends on OpenJDK 7

[Debian Bug Tracking System]

Processing control commands:

> tags -1 confirmed
Bug #814167 [src:lwjgl] lwjgl: (Build-)Depends on OpenJDK 7
Added tag(s) confirmed.

-- 
814167: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=814167
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Processed: Re: Bug#817146: gdal-bin: ogr2ogr segfault

[Debian Bug Tracking System]

Processing control commands:

> tags -1 - moreinfo
Bug #817146 [gdal-bin] gdal-bin: ogr2ogr segfault
Removed tag(s) moreinfo.
> tags -1 + confirmed upstream
Bug #817146 [gdal-bin] gdal-bin: ogr2ogr segfault
Added tag(s) upstream and confirmed.
> forwarded -1 https://trac.osgeo.org/gdal/ticket/6408
Bug #817146 [gdal-bin] gdal-bin: ogr2ogr segfault
Set Bug forwarded-to-address to 'https://trac.osgeo.org/gdal/ticket/6408'.
> severity -1 important
Bug #817146 [gdal-bin] gdal-bin: ogr2ogr segfault
Severity set to 'important' from 'grave'

-- 
817146: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=817146
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#817146: gdal-bin: ogr2ogr segfault

[Sebastiaan Couwenberg]

Control: tags -1 - moreinfo
Control: tags -1 + confirmed upstream
Control: forwarded -1 https://trac.osgeo.org/gdal/ticket/6408
Control: severity -1 important

Hi Andy,

On 08-03-16 15:14, Andy G Wood wrote:
> Reducing a much larger data set, attached argos_trip.csv which is used by 
> attached argos.xml which generates the segfault with:
> 
> ogr2ogr -a_srs WGS84 -f GeoJSON -where "ID=098530" -nln "098530" \
>   p098530.json argos.xml

Thanks for the reproducible test case.

I've forwarded this bugreport to the upstream issue tracker to help get
the segfault resolved. I'm downgrading the severity to important because
this issue because it doesn't render the package completely unusable to
everyone.

I don't have systems with GDAL 1.11 at hand any more, but with GDAL
1.10.1 on jessie your command still fails with the same error messages,
ogr2ogr just doesn't segfault:

$ ogr2ogr -a_srs WGS84 -f GeoJSON -where "ID=098530" \
-nln "098530" p098530.json argos.xml ; echo $?
ERROR 1: Type mismatch or improper type of arguments to = operator.
FAILURE: SetAttributeFilter(ID=098530) on layer 'argos_trip' failed.
1

Because the ID column is of type String, you should quote the value to
not have it interpreted as an integer:

$ ogr2ogr -a_srs WGS84 -f GeoJSON -where "ID='098530'" \
-nln "098530" p098530.json argos.xml ; echo $?
0

This doesn't trigger the type mismatch error and SetAttributeFilter()
failure, and the subsequent segfault (which should not happen either way).

Kind Regards,

Bas

-- 
 GPG Key ID: 4096R/6750F10AE88D4AF1
Fingerprint: 8182 DE41 7056 408D 6146  50D1 6750 F10A E88D 4AF1

Bug#817189: gazebo7-doc: fails to upgrade from 'testing' - trying to overwrite /usr/share/doc-base/gazebo

[Andreas Beckmann]

Package: gazebo7-doc
Version: 7.0.0+dfsg-1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed your package fails to upgrade from
'testing'.
It installed fine in 'testing', then the upgrade to 'sid' fails
because it tries to overwrite other packages files without declaring a
Breaks+Replaces relation.

See policy 7.6 at
https://www.debian.org/doc/debian-policy/ch-relationships.html#s-replaces

>From the attached log (scroll to the bottom...):

  Selecting previously unselected package gazebo7-doc.
  Preparing to unpack .../gazebo7-doc_7.0.0+dfsg-1_all.deb ...
  Unpacking gazebo7-doc (7.0.0+dfsg-1) ...
  dpkg: error processing archive 
/var/cache/apt/archives/gazebo7-doc_7.0.0+dfsg-1_all.deb (--unpack):
   trying to overwrite '/usr/share/doc-base/gazebo', which is also in package 
gazebo6-doc 6.5.0+dfsg-2
  dpkg-deb: error: subprocess paste was killed by signal (Broken pipe)
  Errors were encountered while processing:
   /var/cache/apt/archives/gazebo7-doc_7.0.0+dfsg-1_all.deb


cheers,

Andreas


gazebo6-doc=6.5.0+dfsg-2_gazebo7-doc=7.0.0+dfsg-1.log.gz
Description: application/gzip

Bug#817188: libbamtools-doc: fails to upgrade from 'testing' - trying to overwrite /usr/share/doc/libbamtools-dev/html/functions_v.html

[Andreas Beckmann]

Package: libbamtools-doc
Version: 2.4.0+dfsg-4
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed your package fails to upgrade from
'testing'.
It installed fine in 'testing', then the upgrade to 'sid' fails
because it tries to overwrite other packages files without declaring a
Breaks+Replaces relation.

See policy 7.6 at
https://www.debian.org/doc/debian-policy/ch-relationships.html#s-replaces

>From the attached log (scroll to the bottom...):

  Selecting previously unselected package libbamtools-doc.
  Preparing to unpack .../libbamtools-doc_2.4.0+dfsg-4_all.deb ...
  Unpacking libbamtools-doc (2.4.0+dfsg-4) ...
  dpkg: error processing archive 
/var/cache/apt/archives/libbamtools-doc_2.4.0+dfsg-4_all.deb (--unpack):
   trying to overwrite '/usr/share/doc/libbamtools-dev/html/functions_v.html', 
which is also in package libbamtools-dev 2.4.0+dfsg-3+b1
  dpkg-deb: error: subprocess paste was killed by signal (Broken pipe)
  Errors were encountered while processing:
   /var/cache/apt/archives/libbamtools-doc_2.4.0+dfsg-4_all.deb


cheers,

Andreas


libbamtools-dev=2.4.0+dfsg-3+b1_libbamtools-doc=2.4.0+dfsg-4.log.gz
Description: application/gzip

Bug#814177: marked as done (jalview: (Build-)Depends on OpenJDK 7)

[Debian Bug Tracking System]

Your message dated Tue, 8 Mar 2016 21:29:19 +0100
with message-id <56df361f.6050...@debian.org>
and subject line Re: jalview: (Build-)Depends on OpenJDK 7
has caused the Debian Bug report #814177,
regarding jalview: (Build-)Depends on OpenJDK 7
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
814177: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=814177
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:jalview
Version: 2.7.dfsg-4
Severity: serious
User: debian-j...@lists.debian.org
Usertags: openjdk-8-transition

The package build-depends or depends one an openjdk-7-* package,
which is scheduled for removal for stretch.  Please do not depend
on a specific openjdk version, but on one of the default-java,
default-java-headless or default-jdk packages instead.

default-java defaulting to openjdk-8 on most architectures is now
available in unstable.
--- End Message ---
--- Begin Message ---
On Mon, 08 Feb 2016 20:27:41 + Matthias Klose  wrote:
> Package: src:jalview
> Version: 2.7.dfsg-4
> Severity: serious
> User: debian-j...@lists.debian.org
> Usertags: openjdk-8-transition
> 
> The package build-depends or depends one an openjdk-7-* package,
> which is scheduled for removal for stretch.  Please do not depend
> on a specific openjdk version, but on one of the default-java,
> default-java-headless or default-jdk packages instead.
> 
> default-java defaulting to openjdk-8 on most architectures is now
> available in unstable.

Hi,

jalview neither depends or build-depends on openjdk-7-* packages. It
builds fine with OpenJDK 8. I am going to close this bug as invalid now.

Regards,

Markus



signature.asc
Description: OpenPGP digital signature
--- End Message ---

Processed: Re: ruby-amqp and ruby-amq-client: error when trying to install together

[Debian Bug Tracking System]

Processing control commands:

> found -1 1.5.1-2
Bug #817012 {Done: Sebastien Badia } [ruby-amqp] ruby-amqp and 
ruby-amq-client: error when trying to install together
Marked as found in versions ruby-amqp/1.5.1-2; no longer marked as fixed in 
versions ruby-amqp/1.5.1-2 and reopened.

-- 
817012: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=817012
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#817012: ruby-amqp and ruby-amq-client: error when trying to install together

[Andreas Beckmann]

Followup-For: Bug #817012
Control: found -1 1.5.1-2

Hi,

removal of the old package is not sufficient, you still need to add 
Breaks+Replaces:

  Selecting previously unselected package ruby-amqp.
  Preparing to unpack .../ruby-amqp_1.5.1-2_all.deb ...
  Unpacking ruby-amqp (1.5.1-2) ...
  dpkg: error processing archive 
/var/cache/apt/archives/ruby-amqp_1.5.1-2_all.deb (--unpack):
   trying to overwrite 
'/usr/lib/ruby/vendor_ruby/amq/protocol/get_response.rb', which is also in 
package ruby-amq-client 1.0.4-1
  Errors were encountered while processing:
   /var/cache/apt/archives/ruby-amqp_1.5.1-2_all.deb

Noticed on upgrade tests from testing to sid.


Andreas

Bug#817187: python-pep8: fails to upgrade from 'testing' - trying to overwrite /usr/lib/python2.7/dist-packages/pep8.py

[Andreas Beckmann]

Package: python-pep8
Version: 1.7.0-1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed your package fails to upgrade from
'testing'.
It installed fine in 'testing', then the upgrade to 'sid' fails
because it tries to overwrite other packages files without declaring a
Breaks+Replaces relation.

See policy 7.6 at
https://www.debian.org/doc/debian-policy/ch-relationships.html#s-replaces

>From the attached log (scroll to the bottom...):

  Selecting previously unselected package python-pep8.
  Preparing to unpack .../python-pep8_1.7.0-1_all.deb ...
  Unpacking python-pep8 (1.7.0-1) ...
  dpkg: error processing archive 
/var/cache/apt/archives/python-pep8_1.7.0-1_all.deb (--unpack):
   trying to overwrite '/usr/lib/python2.7/dist-packages/pep8.py', which is 
also in package pep8 1.6.2-0.1
  Errors were encountered while processing:
   /var/cache/apt/archives/python-pep8_1.7.0-1_all.deb


cheers,

Andreas


pep8=1.6.2-0.1_python-pep8=1.7.0-1.log.gz
Description: application/gzip

Bug#817186: Boobank reveals hidden password

[Bertrand Marc]

Package: weboob
version: 1.1-1
Severity: serious

Dear developper,

In the case you configure two backends with boobank, storing the login
but asking for the password (see attached configuration), boobank
reveals the second password.

when you call list, the display is messed up as both backends require a
password on the same line. To login with success, you need to enter the
first password (hidden), then validate, and enter the second password
(not hidden anymore).

Best regards,
Bertrand
[boursorama]
_module = boursorama
device = Boobank
pin_code = 
login = 
password = 
enable_twofactors = True

[banquepopulaire]
_module = banquepopulaire
website = www.ibps.loirelyonnais.banquepopulaire.fr
login = XX
password = 



signature.asc
Description: OpenPGP digital signature

Bug#812852: Fwd: Re: Vigra auf ppc64el

[Daniel Stender]

 Forwarded Message 
Subject: Re: Vigra auf ppc64el
Date: Fri, 4 Mar 2016 15:56:16 +0100
From: Ullrich Koethe 
To: Daniel Stender 
CC: Francesco Biscani 

Hallo Daniel,

unfortunately, we can't investigate this problem ourselves because we 
don't have access to a ppc system. Here are some ideas what you could try:

* Enable another set of threading primitives by passing

-DWITH_BOOST_THREAD=1

to cmake. If the error goes away, the problem might be in the threading 
bits of Vigra or (less likely) in an outdated version of std::thread.

* Remove all occurencies of threading::memory_order* in 
multi_array_chunked.hxx (or equivalently, replace them with 
threading::memory_order_seq_cst). This will force all atomic accesses to 
use sequentially consistent ordering, the most strict possibility.

* compile + run with various sanitizers. Specifically, you should look 
into the address, undefined behaviour and thread sanitizer. The first 
two can be enabled with the gcc/clang command line flags:

  -fsanitize=undefined,address

The third one with:

  -fsanitize=thread

Alternatively or in addition

   valgrind --tool=helgrind ./tests/test_executable
   valginrd --tool=drd ./tests/test_executable

might be useful.

* It would be helpful to know if the problem is deterministic or not. Do 
multiple runs of the same test produce the same errors?

Best
Francesco and Ulli

Bug#816998: marked as done (jpathwatch: FTBFS in stretch, build dependencies not in stretch)

[Debian Bug Tracking System]

Your message dated Tue, 8 Mar 2016 20:50:44 +0100
with message-id <56df2d14.8050...@debian.org>
and subject line Re: jpathwatch: FTBFS in stretch, build dependencies not in 
stretch
has caused the Debian Bug report #816998,
regarding jpathwatch: FTBFS in stretch, build dependencies not in stretch
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
816998: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=816998
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:jpathwatch
Version: 0.95-4
Severity: serious

Dear maintainer:

I tried to build this package with "dpkg-buildpackage -A"
(i.e. only architecture-independent packages), and it failed.

But the failure is build-depends related, so it has nothing to do
with the fact that I was doing "dpkg-buildpackage -A", hence
the serious severity.


[...]
Installing build dependencies
Reading package lists...
Building dependency tree...
Reading state information...
The following NEW packages will be installed:
  sbuild-build-depends-core-dummy
0 upgraded, 1 newly installed, 0 to remove and 0 not upgraded.
Need to get 0 B/770 B of archives.
After this operation, 0 B of additional disk space will be used.
Get:1 file:/<>/resolver-ouaOcq/apt_archive ./ 
sbuild-build-depends-core-dummy 0.invalid.0 [770 B]
debconf: delaying package configuration, since apt-utils is not installed
Selecting previously unselected package sbuild-build-depends-core-dummy.
(Reading database ... 
(Reading database ... 5%
(Reading database ... 10%
(Reading database ... 15%
(Reading database ... 20%
(Reading database ... 25%
(Reading database ... 30%
(Reading database ... 35%
(Reading database ... 40%
(Reading database ... 45%
(Reading database ... 50%
(Reading database ... 55%
(Reading database ... 60%
(Reading database ... 65%
(Reading database ... 70%
(Reading database ... 75%
(Reading database ... 80%
(Reading database ... 85%
(Reading database ... 90%
(Reading database ... 95%
(Reading database ... 100%
(Reading database ... 14543 files and directories currently installed.)
Preparing to unpack .../sbuild-build-depends-core-dummy.deb ...
Unpacking sbuild-build-depends-core-dummy (0.invalid.0) ...
Setting up sbuild-build-depends-core-dummy (0.invalid.0) ...
W: No sandbox user '_apt' on the system, can not drop privileges
Merged Build-Depends: debhelper (>= 9), javahelper, default-jdk (>= 2:1.8), bnd 
(>= 2.1.0), maven-repo-helper
Filtered Build-Depends: debhelper (>= 9), javahelper, default-jdk (>= 2:1.8), 
bnd (>= 2.1.0), maven-repo-helper
dpkg-deb: building package 'sbuild-build-depends-jpathwatch-dummy' in 
'/<>/resolver-fye126/apt_archive/sbuild-build-depends-jpathwatch-dummy.deb'.
OK
Get:1 file:/<>/resolver-fye126/apt_archive ./ InRelease
Ign:1 file:/<>/resolver-fye126/apt_archive ./ InRelease
Get:2 file:/<>/resolver-fye126/apt_archive ./ Release [2119 B]
Get:2 file:/<>/resolver-fye126/apt_archive ./ Release [2119 B]
Get:3 file:/<>/resolver-fye126/apt_archive ./ Release.gpg [299 B]
Get:3 file:/<>/resolver-fye126/apt_archive ./ Release.gpg [299 B]
Get:4 file:/<>/resolver-fye126/apt_archive ./ Sources [252 B]
Get:5 file:/<>/resolver-fye126/apt_archive ./ Packages [571 B]
Reading package lists...
W: No sandbox user '_apt' on the system, can not drop privileges
Reading package lists...

+--+
| Install jpathwatch build dependencies (apt-based resolver)   |
+--+

Installing build dependencies
Reading package lists...
Building dependency tree...
Reading state information...
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:

The following packages have unmet dependencies:
 sbuild-build-depends-jpathwatch-dummy : Depends: default-jdk (>= 2:1.8) but it 
is not going to be installed
E: Unable to correct problems, you have held broken packages.
apt-get failed.
Package installation failed
Reading package lists...
Building dependency tree...
Reading state information...
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
Reading package lists...
Building dependency tree...
Reading state information...
The following packages will be REMOVED:
  sbuild-build-depends-core-dummy*
0 

Bug#815125: Boot failure with Debian linux 4.4.2 package

[Scott Ashcroft]

I'm still seeing the same failure in efi_call with 4.4.4-1 and 4.5-rc4
and 4.5-rc7 from experimental on an HP x360.
It has the INSYDE Corp implementation of EFI which seems to be a common
factor. 

I'll try build the kernel with the patch suggested and test that.

Cheers,
Scott

Bug#817178: qgis uninstallable on unstable

[Ben Caradoc-Davies]

Workaround is to manually remove the diversions:

dpkg-divert --remove /usr/bin/qgis
dpkg-divert --remove /usr/bin/qbrowser

Note that this was an upgrade from the previous qgis on unstable.

Kind regards,

--
Ben Caradoc-Davies 
Director
Transient Software Limited 
New Zealand

Bug#817178: qgis uninstallable on unstable

[Ben Caradoc-Davies]

Package: qgis
Version: 2.14.0+dfsg0-1
Severity: grave
Justification: renders package unusable

Dear Maintainer,

qgis conflicts with its Recommends and cannot be installed on unstable:

Preparing to unpack .../qgis_2.14.0+dfsg0-1_amd64.deb ...
Unpacking qgis (2.14.0+dfsg0-1) ...
dpkg: error processing archive
/var/cache/apt/archives/qgis_2.14.0+dfsg0-1_amd64.deb (--unpack):
 trying to overwrite '/usr/bin/qbrowser.bin', which is the diverted version of
'/usr/bin/qbrowser' (package: qgis-provider-grass)
dpkg-deb: error: subprocess paste was killed by signal (Broken pipe)



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

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

Bug#815125: Boot failure with Debian linux 4.4.2 package

[Stijn Segers]

Hi guys,

I can confirm the latest kernel package works:

linux-image-4.4.0-1-amd64:amd64 4.4.4-1

Boots fine here.

Thank you!

Stijn Segers

Bug#788108: Processed: severity of 788108 is serious, tagging 788108

[Lisandro Damián Nicanor Pérez Meyer]

On Tuesday 08 March 2016 11:59:06 Laurent Bigonville wrote:
> Le 04/03/16 03:05, Lisandro Damián Nicanor Pérez Meyer a écrit :
> > On Monday 22 February 2016 11:45:56 Lisandro Damián Nicanor Pérez Meyer 
wrote:
> >> It was discussed in upstream's mailing list, but I'm on the phone now :(
> > 
> > According to 5.6.0's git repo:
> >   - [QTBUG-40702] Removed dependency towards libgeoclue. The plugin uses
> >   the
> >   
> > GeoClue DBus interface.
> > 
> > I'm now working to disable the support in 5.5.1 to close this bug ASAP. We
> > need to understand what we will need to depend upon for 5.6.
> > 
> > Laurent: does it rings you any bells?
> 
> For the runtime dependency, you should Depends/Recommends/Suggests the
> geoclue-2.0 package.
> 
> If your code is resilient enough and support the case where the daemon
> is not installed, I would personally go for the Recommends.

Thanks a lot Laurent!

-- 
 hmm, el enchufe hace chispas...
<-- rata ha dejado este servidor ("Leaving").
 ouch
  Visto en #lugfi, irc.freenode.net

Lisandro Damián Nicanor Pérez Meyer
http://perezmeyer.com.ar/
http://perezmeyer.blogspot.com/


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

Bug#805492: /var/lib

[Laurent Bigonville]

Le 29/02/16 03:46, Russell Coker a écrit :

On Mon, 29 Feb 2016 02:47:04 AM Laurent Bigonville wrote:

Le 28/02/16 11:05, Russell Coker a écrit :

the easiest would be to do like fedora and install the modules directly
in the /var/lib/selinux//100 store instead of copying/loading
them at installation time

Do you mean having files in the package under /var/lib?  If so that seems
like a FHS violation.  Why not just keep them under /usr/share/selinux
and symlink them?

There are a lot of packages that ships files in /var/lib.

I'm sure that you can find many ways in which there are a lot of broken
packages in Debian or in any other distribution.  That said if we have a
strong precedent in Debian for doing things a certain way it is an argument
for doing more of the same.


Are you sure you are not thinking about /var/run?

https://en.wikipedia.org/wiki/Filesystem_Hierarchy_Standard

# State information. Persistent data modified by programs as they run, e.g.,
# databases, packaging system metadata, etc.

The above section from the above URL suggests that package maintained files
aren't suitable.

The description of /usr is:
# Secondary hierarchy for read-only user data; contains the majority of
# (multi-)user utilities and applications.

For /usr/share it says:
# Architecture-independent (shared) data.

I think that /usr/share is the best place for it.  If /var/lib has symlinks
into /usr/share then files which aren't changed can be replaced by a package
upgrade while files that are modified by utilities can stay modified.

Well one could argue that the store is "Persistent data modified by 
programs as they run" and that we set defaults for this store by 
installing files from the package.


The new store format is actually the following:

/var/lib/selinux//100/... << modules shipped by the 
distribution
/var/lib/selinux//400/... << modules loaded by the user 
using semodules (the priority can be changed on the cmd line)


So by default the user shouldn't interfere with the files we are 
shipping, we could add a warning in the NEWS or README file to warn the 
user about this.


BTW, the files in this new store are not in the same format (HLL) as the 
(.pp) files shipped currently in /usr/lib/selinux, they are processed by 
a "compiler" (/usr/lib/selinux/hll/pp) and stored in the CIL format in 
/var/lib/selinux//..., so we cannot simply link the files 
from /usr/share/selinux to /var/lib/selinux

Bug#817000: marked as done (pymvpa2: FTBFS in stretch, build dependencies not in stretch)

[Debian Bug Tracking System]

Your message dated Tue, 08 Mar 2016 17:33:27 +
with message-id 
and subject line Bug#817000: fixed in pymvpa2 2.4.2-1
has caused the Debian Bug report #817000,
regarding pymvpa2: FTBFS in stretch, build dependencies not in stretch
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
817000: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=817000
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:pymvpa2
Version: 2.4.1-1
Severity: serious

Dear maintainer:

I tried to build this package with "dpkg-buildpackage -A"
(i.e. only architecture-independent packages), and it failed.

But the failure is build-depends related, so it has nothing to do
with the fact that I was doing "dpkg-buildpackage -A", hence
the serious severity.


[...]
Installing build dependencies
Reading package lists...
Building dependency tree...
Reading state information...
The following NEW packages will be installed:
  sbuild-build-depends-core-dummy
0 upgraded, 1 newly installed, 0 to remove and 0 not upgraded.
Need to get 0 B/770 B of archives.
After this operation, 0 B of additional disk space will be used.
Get:1 file:/<>/resolver-ge9Qdo/apt_archive ./ 
sbuild-build-depends-core-dummy 0.invalid.0 [770 B]
debconf: delaying package configuration, since apt-utils is not installed
Selecting previously unselected package sbuild-build-depends-core-dummy.
(Reading database ... 
(Reading database ... 5%
(Reading database ... 10%
(Reading database ... 15%
(Reading database ... 20%
(Reading database ... 25%
(Reading database ... 30%
(Reading database ... 35%
(Reading database ... 40%
(Reading database ... 45%
(Reading database ... 50%
(Reading database ... 55%
(Reading database ... 60%
(Reading database ... 65%
(Reading database ... 70%
(Reading database ... 75%
(Reading database ... 80%
(Reading database ... 85%
(Reading database ... 90%
(Reading database ... 95%
(Reading database ... 100%
(Reading database ... 14543 files and directories currently installed.)
Preparing to unpack .../sbuild-build-depends-core-dummy.deb ...
Unpacking sbuild-build-depends-core-dummy (0.invalid.0) ...
Setting up sbuild-build-depends-core-dummy (0.invalid.0) ...
W: No sandbox user '_apt' on the system, can not drop privileges
Merged Build-Depends: debhelper (>= 7.0.50~), python-all-dev (>= 2.6.6-3~), 
swig2.0 | swig (<= 3.0.5), python-numpy, python-scipy, python-nibabel, 
python-nose, python-h5py, python-lxml, libsvm-dev (>= 2.84.0), help2man, 
man2html, python-sphinx, python-numpydoc, graphviz, inkscape, imagemagick, bc, 
python-matplotlib, python-statsmodels
Merged Build-Conflicts: swig3.0 (>= 3.0.5)
Filtered Build-Depends: debhelper (>= 7.0.50~), python-all-dev (>= 2.6.6-3~), 
swig2.0 | swig (<= 3.0.5), python-numpy, python-scipy, python-nibabel, 
python-nose, python-h5py, python-lxml, libsvm-dev (>= 2.84.0), help2man, 
man2html, python-sphinx, python-numpydoc, graphviz, inkscape, imagemagick, bc, 
python-matplotlib, python-statsmodels
Filtered Build-Conflicts: swig3.0 (>= 3.0.5)
dpkg-deb: building package 'sbuild-build-depends-pymvpa2-dummy' in 
'/<>/resolver-foUw1E/apt_archive/sbuild-build-depends-pymvpa2-dummy.deb'.
OK
Get:1 file:/<>/resolver-foUw1E/apt_archive ./ InRelease
Ign:1 file:/<>/resolver-foUw1E/apt_archive ./ InRelease
Get:2 file:/<>/resolver-foUw1E/apt_archive ./ Release [2119 B]
Get:2 file:/<>/resolver-foUw1E/apt_archive ./ Release [2119 B]
Get:3 file:/<>/resolver-foUw1E/apt_archive ./ Release.gpg [299 B]
Get:3 file:/<>/resolver-foUw1E/apt_archive ./ Release.gpg [299 B]
Get:4 file:/<>/resolver-foUw1E/apt_archive ./ Sources [373 B]
Get:5 file:/<>/resolver-foUw1E/apt_archive ./ Packages [693 B]
Reading package lists...
W: No sandbox user '_apt' on the system, can not drop privileges
Reading package lists...

+--+
| Install pymvpa2 build dependencies (apt-based resolver)  |
+--+

Installing build dependencies
Reading package lists...
Building dependency tree...
Reading state information...
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:

The following packages have unmet dependencies:
 

Bug#817152: marked as done (Doesn't find JDK)

[Debian Bug Tracking System]

Your message dated Tue, 08 Mar 2016 17:31:34 +
with message-id 
and subject line Bug#817152: fixed in netbeans 8.1+dfsg2-2
has caused the Debian Bug report #817152,
regarding Doesn't find JDK
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
817152: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=817152
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: netbeans
Version: 8.1+dfsg2-1
Severity: grave

Although JDK dependency is installed (openjdk-7-jdk 7u91-2.6.3-1), when 
starting netbeans, I get the following:

$ netbeans 
Cannot find java. Please use the --jdkhome switch.
$ echo $?
2


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

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

Versions of packages netbeans depends on:
ii  default-jdk [java7-sdk]  2:1.7-52.1
ii  libnb-apisupport3-java   8.1+dfsg2-1
ii  libnb-ide14-java 8.1+dfsg2-1
ii  libnb-java5-java 8.1+dfsg2-1
ii  libnb-platform18-java8.1+dfsg1-2

netbeans recommends no packages.

netbeans suggests no packages.

-- debconf-show failed
--- End Message ---
--- Begin Message ---
Source: netbeans
Source-Version: 8.1+dfsg2-2

We believe that the bug you reported is fixed in the latest version of
netbeans, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 817...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Markus Koschany  (supplier of updated netbeans package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Tue, 08 Mar 2016 16:38:19 +0100
Source: netbeans
Binary: libnb-absolutelayout-java libnb-apisupport3-java libnb-ide14-java 
libnb-java5-java netbeans
Architecture: source all
Version: 8.1+dfsg2-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Java Maintainers 

Changed-By: Markus Koschany 
Description:
 libnb-absolutelayout-java - Java LayoutManager to allow placement in absolute 
positions
 libnb-apisupport3-java - Common NetBeans Platform Development Related 
Libraries for NetBea
 libnb-ide14-java - Common Integrated Development Environment Libraries for 
NetBeans
 libnb-java5-java - Common Java Related Libraries for NetBeans
 netbeans   - Extensible Java IDE
Closes: 816758 817152
Changes:
 netbeans (8.1+dfsg2-2) unstable; urgency=medium
 .
   * netbeans: Remove alternative dependency on java7-sdk because
 netbeans will not work correctly with OpenJDK 7 anymore since jdk8 builds
 were activated by the last upload. In addition OpenJDK 7 is going to be
 removed from Debian before the Stretch release.
 Thanks to Kevin Carney for the report. (Closes: #816758, #817152)
Checksums-Sha1:
 acfed457a707b64919f4c9aea193956731ee60a0 3627 netbeans_8.1+dfsg2-2.dsc
 0eb021339582d7336ad1d8e9cfac962db5cfa899 64416 
netbeans_8.1+dfsg2-2.debian.tar.xz
 af2838d6f1241ee2aa5a97f7bd8a216fa011a101 32108 
libnb-absolutelayout-java_8.1+dfsg2-2_all.deb
 4b349ae1ae0d164183a5e215ce61fe10270ce2fd 926532 
libnb-apisupport3-java_8.1+dfsg2-2_all.deb
 6cc0cffa5c7d71fd6795af16e155f07027c67621 14544458 
libnb-ide14-java_8.1+dfsg2-2_all.deb
 b272e27ef758f0ae0405a98299bce152375dfec8 6770498 
libnb-java5-java_8.1+dfsg2-2_all.deb
 bc41b2fa859800aca9be0a27e875aa3ff46c4f0d 610492 netbeans_8.1+dfsg2-2_all.deb
Checksums-Sha256:
 9cf8e9af93683a51bf76bb9a12b3e8770308ea75c2a67b2aeca4a01d15e36466 3627 
netbeans_8.1+dfsg2-2.dsc
 b167effbbe808887cb58744b11cfbf2470cea5c71e514811ad3df2c1336fc73d 64416 
netbeans_8.1+dfsg2-2.debian.tar.xz
 cf73a6a9ab02c0e0b2690d84fa59bc6239f972cba39e42544340b2b509cf2c1b 32108 
libnb-absolutelayout-java_8.1+dfsg2-2_all.deb
 5a7dfd5b20537bbdd566a6d24d1de1c1c9412dd9e559f3eea598f3d1812b46b9 926532 
libnb-apisupport3-java_8.1+dfsg2-2_all.deb
 

Bug#815775: marked as done (Build-Depends on unavailable packages mono-gmcs libmono2.0-cil)

[Debian Bug Tracking System]

Your message dated Tue, 08 Mar 2016 16:39:36 +
with message-id 
and subject line Bug#815775: fixed in zeroc-ice 3.5.1-6.4
has caused the Debian Bug report #815775,
regarding Build-Depends on unavailable packages mono-gmcs libmono2.0-cil
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
815775: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=815775
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: zeroc-ice
Version: 3.5.1-6.3
Severity: important

During a rebuild with ruby2.3 enabled, zeroc-ice fails to build. Please make
sure it builds against ruby2.3, which will be the Ruby version in stretch.

The full build log can be found at
https://pkg-ruby-extras.alioth.debian.org/rebuilds/ruby2.3-build-logs/zeroc-ice_3.5.1-6.3_amd64.txt
--- End Message ---
--- Begin Message ---
Source: zeroc-ice
Source-Version: 3.5.1-6.4

We believe that the bug you reported is fixed in the latest version of
zeroc-ice, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 815...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Christopher Knadle  (supplier of updated zeroc-ice 
package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Fri, 04 Mar 2016 21:54:19 -0500
Source: zeroc-ice
Binary: zeroc-ice35 ice35-translators ice35-services libicestorm35v5 
libicegrid35v5 libicebox35v5 icebox libicepatch2-35v5 libglacier2-35v5 
libfreeze35v5 libicedb35v5 ice35-slice libzeroc-ice35v5 libicessl35v5 
libiceutil35v5 libicexml35v5 libslice35v5 libzeroc-ice35-dev libzeroc-ice35-dbg 
python-zeroc-ice python3-zeroc-ice php-zeroc-ice libzeroc-ice3.5-cil 
ruby-zeroc-ice libzeroc-ice3.5-java icegrid-gui
Architecture: all source
Version: 3.5.1-6.4
Distribution: unstable
Urgency: medium
Maintainer: Francisco Moya 
Changed-By: Christopher Knadle 
Closes: 815775
Description: 
 ice35-services - Services bundled into ZeroC Ice
 ice35-slice - Slice definitions for Ice services
 ice35-translators - Slice translators to several languages
 icebox - Plugin-based meta-application for ZeroC Ice
 icegrid-gui - GUI for IceGrid service
 libfreeze35v5 - Libraries implementing a persistence framework for ZeroC Ice
 libglacier2-35v5 - Libraries implementing a firewall service for ZeroC Ice
 libicebox35v5 - Libraries implementing a plugin framework for ZeroC Ice
 libicedb35v5 - Libraries for persistent backends for ZeroC Ice
 libicegrid35v5 - Libraries implementing grid-like services for ZeroC Ice
 libicepatch2-35v5 - Libraries implementing a distribution service for ZeroC Ice
 libicessl35v5 - Ice for C++ SSL plug-in
 libicestorm35v5 - Libraries implementing an event service for ZeroC Ice
 libiceutil35v5 - Ice for C++ misc utility library
 libicexml35v5 - ZeroC Ice for C++ XML parser library
 libslice35v5 - Ice for C++ Slice parser library
 libzeroc-ice3.5-cil - Ice for C# libraries
 libzeroc-ice3.5-java - Ice for Java libraries
 libzeroc-ice35-dbg - Ice for C++ debugging symbols
 libzeroc-ice35-dev - Ice for C++ development libraries
 libzeroc-ice35v5 - Ice for C++ runtime library
 php-zeroc-ice - Ice for PHP extension
 python-zeroc-ice - Ice for Python libraries (Python 2)
 python3-zeroc-ice - Ice for Python libraries (Python 3)
 ruby-zeroc-ice - Ice for Ruby modules
 zeroc-ice35 - Internet Communications Engine
Changes:
 zeroc-ice (3.5.1-6.4) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * debian/control:
 - Remove dependencies to fix FTBFS bug:
  libmono2.0-cil,
  mono-gmcs
   (Closes: #815775)
   [Note: the Ubuntu source packages zeroc-ice upstream ships have
far fewer Build-Depends.]
Checksums-Sha1: 
 e6a67e0880fd922b81ccc6fc399a7c31d2fb0d30 3903 zeroc-ice_3.5.1-6.4.dsc
 4c9188e81df7cb954fd05e566236113faa9e3b08 51708 
zeroc-ice_3.5.1-6.4.debian.tar.xz
 6a42cd416eceb62b24cd4b6fc00a2e9f60d0f5cd 165312 ice35-slice_3.5.1-6.4_all.deb
 90b537bd4ece94f4702ad19b7eb180655b132820 854852 icegrid-gui_3.5.1-6.4_all.deb
 c249985ac5a195dcbd5053ec275a66a47e60ec0e 390056 
libzeroc-ice3.5-cil_3.5.1-6.4_all.deb
 

Processed: topmenu-gtk: diff for NMU version 0.2.1+git20151210.8c6108f-2.1

[Debian Bug Tracking System]

Processing control commands:

> tags 816308 + patch
Bug #816308 [src:topmenu-gtk] topmenu-gtk: FTBFS: configure: error: 
--enable-lxpanel-plugin was given, but test for lxpanel failed
Added tag(s) patch.
> tags 816308 + pending
Bug #816308 [src:topmenu-gtk] topmenu-gtk: FTBFS: configure: error: 
--enable-lxpanel-plugin was given, but test for lxpanel failed
Added tag(s) pending.

-- 
816308: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=816308
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#816308: topmenu-gtk: diff for NMU version 0.2.1+git20151210.8c6108f-2.1

[Raúl Benencia]

Control: tags 816308 + patch
Control: tags 816308 + pending

Dear maintainer,

This FTBFS is simply caused by a recent split of the package lxpanel into
more binary packages. In this case, the new build dependency required by
topmenu-gtk is lxpanel-dev. I've prepared an NMU with this changes
(versioned as 0.2.1+git20151210.8c6108f-2.1).

As I don't have privileges to upload it to DELAYED, I've uploaded it to the
mentors repository. Please visit the following URL:

  http://mentors.debian.net/package/topmenu-gtk

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

  dget -x 
http://mentors.debian.net/debian/pool/main/t/topmenu-gtk/topmenu-gtk_0.2.1+git20151210.8c6108f-2.1.dsc

Cheers,
Rul
diff -Nru topmenu-gtk-0.2.1+git20151210.8c6108f/debian/changelog topmenu-gtk-0.2.1+git20151210.8c6108f/debian/changelog
--- topmenu-gtk-0.2.1+git20151210.8c6108f/debian/changelog	2016-02-19 02:23:00.0 -0800
+++ topmenu-gtk-0.2.1+git20151210.8c6108f/debian/changelog	2016-03-08 07:55:42.0 -0800
@@ -1,3 +1,10 @@
+topmenu-gtk (0.2.1+git20151210.8c6108f-2.1) UNRELEASED; urgency=medium
+
+  * Non-maintainer upload.
+  * Fix FTBFS due new missing build dep lxpanel-dev (Closes: #816308)
+
+ -- Raúl Benencia   Tue, 08 Mar 2016 07:55:42 -0800
+
 topmenu-gtk (0.2.1+git20151210.8c6108f-2) unstable; urgency=medium
 
   * All over the package: whitespace-cleanup at EOL.
diff -Nru topmenu-gtk-0.2.1+git20151210.8c6108f/debian/control topmenu-gtk-0.2.1+git20151210.8c6108f/debian/control
--- topmenu-gtk-0.2.1+git20151210.8c6108f/debian/control	2016-02-19 02:11:01.0 -0800
+++ topmenu-gtk-0.2.1+git20151210.8c6108f/debian/control	2016-03-08 07:58:38.0 -0800
@@ -18,7 +18,7 @@
libwnck-3-dev,
libmate-panel-applet-dev,
xfce4-panel-dev (>= 4.8),
-   lxpanel (>= 0.8),
+   lxpanel-dev (>= 0.8),
libfm-dev (>= 1.2.3),
 Standards-Version: 3.9.6
 Homepage: https://git.javispedro.com/cgit/topmenu-gtk.git/about/


signature.asc
Description: PGP signature

Bug#812096: smc: FTBFS: configure: error: Package requirements (CEGUI-OPENGL >= 0.7.2) were not met:

[Markus Koschany]

On Wed, 20 Jan 2016 15:09:18 +0100 Chris Lamb  wrote:
> Source: smc
> Version: 1.9+git20121121-1.2
> Severity: serious
> Justification: fails to build from source
> User: reproducible-bui...@lists.alioth.debian.org
> Usertags: ftbfs
> X-Debbugs-Cc: reproducible-bui...@lists.alioth.debian.org
> 
> Dear Maintainer,
> 
> smc fails to build from source in unstable/amd64:

I had a go at this bug. SMC has to be ported to CEGUI 0.8.4. I replaced
obsolete includes but there is obviously more work to do. I am attaching
my preliminary work for now but I think it would be best to package the
latest upstream release of SMC instead.

Regards,

Markus
From: Markus Koschany 
Date: Tue, 8 Mar 2016 15:25:53 +0100
Subject: cegui 0.8.4

---
 configure.ac   |  4 ++--
 src/audio/random_sound.cpp |  2 +-
 src/core/campaign_manager.h|  4 ++--
 src/core/editor.h  |  4 ++--
 src/core/game_core.h   |  2 +-
 src/core/property_helper.h |  2 +-
 src/enemies/bosses/turtle_boss.cpp |  2 +-
 src/enemies/eato.cpp   |  2 +-
 src/enemies/flyon.cpp  |  2 +-
 src/enemies/furball.cpp|  2 +-
 src/enemies/gee.cpp|  2 +-
 src/enemies/krush.cpp  |  2 +-
 src/enemies/rokko.cpp  |  2 +-
 src/enemies/spika.cpp  |  2 +-
 src/enemies/spikeball.cpp  |  2 +-
 src/enemies/static.cpp |  2 +-
 src/enemies/thromp.cpp |  2 +-
 src/enemies/turtle.cpp |  2 +-
 src/gui/menu.cpp   |  2 +-
 src/level/level.h  |  4 ++--
 src/level/level_background.h   |  2 +-
 src/objects/bonusbox.cpp   |  2 +-
 src/objects/box.cpp|  2 +-
 src/objects/level_entry.cpp|  2 +-
 src/objects/level_exit.cpp |  2 +-
 src/objects/sprite.h   |  2 +-
 src/objects/star.cpp   |  2 +-
 src/overworld/overworld.cpp|  2 +-
 src/overworld/overworld.h  |  4 ++--
 src/overworld/world_layer.h|  4 ++--
 src/overworld/world_manager.h  |  4 ++--
 src/user/preferences.h |  4 ++--
 src/user/savegame.h|  4 ++--
 src/video/animation.cpp|  2 +-
 src/video/color.h  |  2 +-
 src/video/img_manager.cpp  |  4 ++--
 src/video/video.cpp| 22 +++---
 src/video/video.h  |  4 ++--
 38 files changed, 59 insertions(+), 59 deletions(-)

diff --git a/configure.ac b/configure.ac
index bd0b059..7f41436 100644
--- a/configure.ac
+++ b/configure.ac
@@ -72,14 +72,14 @@ AC_CHECK_LIB([SDL_ttf], [TTF_Init], ,
 	[AC_MSG_ERROR([SDL_ttf library not found])])
 
 # Check for the CEGUI library
-PKG_CHECK_MODULES([CEGUI_OPENGL], [CEGUI-OPENGL >= 0.7.2])
+PKG_CHECK_MODULES([CEGUI_OPENGL], [CEGUI-0-OPENGL >= 0.7.2])
 CPPFLAGS="$CPPFLAGS $CEGUI_OPENGL_CFLAGS"
 LIBS="$LIBS $CEGUI_OPENGL_LIBS"
 # CEGUI 0.7.5 does not install CEGUI-NULL.pc
 #PKG_CHECK_MODULES([CEGUI_NULL], [CEGUI-NULL >= 0.7.2])
 #CPPFLAGS="$CPPFLAGS $CEGUI_NULL_CFLAGS"
 #LIBS="$LIBS $CEGUI_NULL_LIBS"
-AC_CHECK_LIB([CEGUINullRenderer], [main], ,
+AC_CHECK_LIB([CEGUINullRenderer-0], [main], ,
 	[AC_MSG_ERROR([CEGUINullRenderer library not found - try building CEGUI with --enable-null-renderer])])
 
 # Check for the gettext library
diff --git a/src/audio/random_sound.cpp b/src/audio/random_sound.cpp
index 01be27d..e2225f7 100644
--- a/src/audio/random_sound.cpp
+++ b/src/audio/random_sound.cpp
@@ -22,7 +22,7 @@
 #include "../core/math/utilities.h"
 #include "../core/i18n.h"
 // CEGUI
-#include "CEGUIXMLAttributes.h"
+#include 
 #include "CEGUIWindowManager.h"
 #include "elements/CEGUIEditbox.h"
 #include "elements/CEGUICheckbox.h"
diff --git a/src/core/campaign_manager.h b/src/core/campaign_manager.h
index cb2ce4b..02c3e7e 100644
--- a/src/core/campaign_manager.h
+++ b/src/core/campaign_manager.h
@@ -20,8 +20,8 @@
 #include "../core/global_game.h"
 #include "../core/obj_manager.h"
 // CEGUI
-#include "CEGUIXMLHandler.h"
-#include "CEGUIXMLAttributes.h"
+#include 
+#include 
 
 namespace SMC
 {
diff --git a/src/core/editor.h b/src/core/editor.h
index 1cfbed5..01ed439 100644
--- a/src/core/editor.h
+++ b/src/core/editor.h
@@ -21,8 +21,8 @@
 #include "../gui/hud.h"
 #include "../video/img_settings.h"
 // CEGUI
-#include "CEGUIXMLHandler.h"
-#include "CEGUIXMLAttributes.h"
+#include 
+#include 
 #include "elements/CEGUIListbox.h"
 #include "elements/CEGUIListboxTextItem.h"
 #include "CEGUIImageset.h"
diff --git a/src/core/game_core.h b/src/core/game_core.h
index f28f942..a0194c7 100644
--- a/src/core/game_core.h
+++ b/src/core/game_core.h
@@ -20,7 +20,7 @@
 #include "../objects/sprite.h"
 #include "../core/camera.h"
 // CEGUI
-#include "CEGUIPropertyHelper.h"
+#include 
 
 namespace SMC
 {
diff --git a/src/core/property_helper.h b/src/core/property_helper.h
index c6f2033..d956398 100644
--- 

Bug#816376: Unfit upstream

[David Prévot]

Hi,

Le 08/03/2016 10:49, Sébastien Villemot a écrit :
> Le lundi 07 mars 2016 à 22:32 -0400, David Prévot a écrit :

>> But please, be aware that the enormous owncloud
>> package is only the tip of the iceberg: beyond the ~70 packages (some
>> were already removed via #816769) listed on the [DDPO], I was
>> maintaining a few more dozens on the PHP PEAR (and composer) Maintainers
>> team as well as some JavaScript packages.
> 
> Do you plan to continue maintaining those extra PHP packages?

Not if they were only used by owncloud (and I’d rather let people who
are still using the other packages left take care of their maintenance
anyway), unless they have a user-base on their own. Have a look at the
already filed “Useless in Debian” RC-bugs in the ownCloud (and PEAR)
DDPO to get an idea of the clean-up work in progress.

> I'm asking because I plan to move to a manual installation of ownCloud
> using upstream provided tarball […]. Do you think such setup will be
> viable (especially with respect to the various dependencies) on a sid
> system?

All dependencies are bundled in the upstream tarball anyway, you won’t
need to use system-wide dependencies.

Regards

David



signature.asc
Description: OpenPGP digital signature

Processed: Bug#817154: libnih1: uninstallable in unstable (was "lxc: Can not install lxc 1.1.5-1")

[Debian Bug Tracking System]

Processing control commands:

> reassign -1 libnih1
Bug #817154 [lxc] lxc: Can not install lxc 1.1.5-1
Bug reassigned from package 'lxc' to 'libnih1'.
No longer marked as found in versions 1.1.5-1.
Ignoring request to alter fixed versions of bug #817154 to the same values 
previously set
> found -1 1.0.3-4.3
Bug #817154 [libnih1] lxc: Can not install lxc 1.1.5-1
Marked as found in versions libnih/1.0.3-4.3.
> retitle -1 libnih1: uninstallable in unstable
Bug #817154 [libnih1] lxc: Can not install lxc 1.1.5-1
Changed Bug title to 'libnih1: uninstallable in unstable' from 'lxc: Can not 
install lxc 1.1.5-1'
> severity -1 serious
Bug #817154 [libnih1] libnih1: uninstallable in unstable
Severity set to 'serious' from 'normal'

-- 
817154: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=817154
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#816376: Unfit upstream

[Sébastien Villemot]

Le lundi 07 mars 2016 à 22:32 -0400, David Prévot a écrit :
> Le 07/03/2016 12:43, Sébastien Villemot a écrit :

> Reading the (recent) threads on both the maintainer and upstream lists
> should help anyone to make their mind about it (I’ll give a few
> pointers). Seeing how Debian is described in upstream staff blog posts
> and issue tracker goes further down (I don’t wish to publish some direct
> links from the BTS, but they’re not hard to find).

[...]

> > And, if you think it makes sense to orphan the package,
> > that would help prospective new maintainers in making the decision to
> > adopt the package or not.
> 
> I’m happy to give anyone write (and admin) access to our current
> infrastructure. Feel free to open an RFA or O wnpp bug on my behalf if
> you think it might help.

Thanks for providing this information. I realize that the situation is
indeed quite difficult. I won't open a wnpp bug by myself, since I
understand that you don't think it's a reasonable solution.

> But please, be aware that the enormous owncloud
> package is only the tip of the iceberg: beyond the ~70 packages (some
> were already removed via #816769) listed on the [DDPO], I was
> maintaining a few more dozens on the PHP PEAR (and composer) Maintainers
> team as well as some JavaScript packages.

Do you plan to continue maintaining those extra PHP packages?

I'm asking because I plan to move to a manual installation of ownCloud
using upstream provided tarball (I won't use the upstream provided .deb,
because if this .deb is not good for inclusion in Debian, then it can't
be good for installation on my system). Do you think such setup will be
viable (especially with respect to the various dependencies) on a sid
system?

Cheers,

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

Bug#808043: closed by Ben Hutchings <b...@decadent.org.uk> (Bug#808043: fixed in linux 4.4.4-1)

[Christian Marillat]

On 07 mars 2016 23:27, ow...@bugs.debian.org (Debian Bug Tracking System) wrote:

[...]

>* [powerpc*] Fix module linking to work with binutils 2.26 (Closes: 
> #808043):
>  - Simplify module TOC handling
>  - Fix dedotify for binutils >= 2.26

Thanks, works well now.

Christian

Bug#817146: gdal-bin: ogr2ogr segfault

[Andy G Wood]

Hi Bas,

Reducing a much larger data set, attached argos_trip.csv which is used by 
attached argos.xml which generates the segfault with:

ogr2ogr -a_srs WGS84 -f GeoJSON -where "ID=098530" -nln "098530" \
  p098530.json argos.xml

Andy.

On Tuesday 08 March 2016 14:58:47 Bas Couwenberg wrote:
> Control: tags -1 moreinfo
> 
> Hi Andy,
> 
> > Running an ogr2ogr command that had been working until the most recent
> > update in testing:
> > 
> > ogr2ogr -a_srs WGS84 -f GeoJSON -where "ID=098530" -nln "098530"
> > p098530.json argos.xml
> 
> Can you provide the data file(s) to reproduce this issue?
> 
> Kind Regards,
> 
> Bas


argos.xml
Description: XML document
ID,DIST,THEGEOM
098530,32,"LINESTRING(-72.303 -69.499, -72.295 -69.506, -72.316 -69.511, -72.343 -69.513, -72.280 -69.510, -72.269 -69.497, -72.271 -69.500, -72.322 -69.490, -72.327 -69.510, -72.317 -69.515, -72.290 -69.507, -72.300 -69.504, -72.298 -69.493, -72.297 -69.498, -72.298 -69.506, -72.308 -69.508, -72.306 -69.507, -72.306 -69.506, -72.319 -69.503, -72.305 -69.506, -72.299 -69.509, -72.342 -69.501, -72.280 -69.511, -72.279 -69.527, -72.247 -69.530, -72.206 -69.528, -72.264 -69.528, -72.242 -69.520, -72.245 -69.519)"

Bug#817153: MUA is opened with empty email

[Pierre THIERRY]

Package: reportbug-ng
Version: 1.31
Severity: grave

Contrary to reportbug and previous behaviour of reportbug-ng (if memory 
serves), now reportbug-ng opens my MUA with an empty mail instead of a 
pre-filled report with the informations I gave in reportbug-ng's UI.

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

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

Versions of packages reportbug-ng depends on:
ii  python2.7.9-1
ii  python-apt1.0.1
ii  python-debianbts  2.4
ii  python-qt44.11.4+dfsg-1+b2
pn  python:any
ii  xdg-utils 1.1.1-1
ii  xterm 320-1

reportbug-ng recommends no packages.

reportbug-ng suggests no packages.

-- debconf-show failed

Bug#817152: Doesn't find JDK

[Pierre THIERRY]

Package: netbeans
Version: 8.1+dfsg2-1
Severity: grave

Although JDK dependency is installed (openjdk-7-jdk 7u91-2.6.3-1), when 
starting netbeans, I get the following:

$ netbeans 
Cannot find java. Please use the --jdkhome switch.
$ echo $?
2


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

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

Versions of packages netbeans depends on:
ii  default-jdk [java7-sdk]  2:1.7-52.1
ii  libnb-apisupport3-java   8.1+dfsg2-1
ii  libnb-ide14-java 8.1+dfsg2-1
ii  libnb-java5-java 8.1+dfsg2-1
ii  libnb-platform18-java8.1+dfsg1-2

netbeans recommends no packages.

netbeans suggests no packages.

-- debconf-show failed

Bug#817146: gdal-bin: ogr2ogr segfault

[Bas Couwenberg]

Control: tags -1 moreinfo

Hi Andy,


Running an ogr2ogr command that had been working until the most recent
update in testing:

ogr2ogr -a_srs WGS84 -f GeoJSON -where "ID=098530" -nln "098530"
p098530.json argos.xml


Can you provide the data file(s) to reproduce this issue?

Kind Regards,

Bas

Processed: Re: Bug#817146: gdal-bin: ogr2ogr segfault

[Debian Bug Tracking System]

Processing control commands:

> tags -1 moreinfo
Bug #817146 [gdal-bin] gdal-bin: ogr2ogr segfault
Added tag(s) moreinfo.

-- 
817146: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=817146
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#802049: marked as done (cyphesis-cpp: FTBFS in sid: needs -std=c++11)

[Debian Bug Tracking System]

Your message dated Tue, 8 Mar 2016 15:54:30 +0200
with message-id 

Bug#817146: gdal-bin: ogr2ogr segfault

[Andy Wood]

Package: gdal-bin
Version: 2.0.2+dfsg-2
Severity: grave
Justification: renders package unusable

Dear Maintainer,

   * What led up to the situation?

Running an ogr2ogr command that had been working until the most recent update 
in testing:

ogr2ogr -a_srs WGS84 -f GeoJSON -where "ID=098530" -nln "098530" p098530.json 
argos.xml

   * What was the outcome of this action?

Segfault and error message.
In /var/log/syslog:

kernel: [1918421.641659] ogr2ogr[11691]: segfault at ceb3f0 ip 00ceb3f0 
sp 7fffbd837758 error 15

At command line:

ERROR 1: Type mismatch or improper type of arguments to = operator.
FAILURE: SetAttributeFilter(ID=098530) on layer 'argos_trip' failed.
Segmentation fault


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

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

Versions of packages gdal-bin depends on:
ii  libc6   2.21-9
ii  libgcc1 1:5.3.1-10
ii  libgdal20 [gdal-abi-2-0-2]  2.0.2+dfsg-2
ii  libstdc++6  5.3.1-10

gdal-bin recommends no packages.

Versions of packages gdal-bin suggests:
ii  python-gdal  2.0.2+dfsg-2

-- no debconf information

Processed: Re: Bug#720378: cctools: FTBFS on non-linux

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> severity 720378 important
Bug #720378 [src:cctools] cctools: FTBFS on non-linux
Severity set to 'important' from 'serious'
> user debian-...@lists.debian.org
Setting user to debian-...@lists.debian.org (was ste...@pyro.eu.org).
> usertags 720378 + kfreebsd
Usertags were: kfreebsd.
Usertags are now: kfreebsd.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
720378: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=720378
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#807989: marked as done (gnukhata-core-engine: fails to install: psql: ALTER: command not found)

[Debian Bug Tracking System]

Your message dated Tue, 08 Mar 2016 13:50:48 +
with message-id 
and subject line Bug#807989: fixed in gnukhata-core-engine 2.6.1-2
has caused the Debian Bug report #807989,
regarding gnukhata-core-engine: fails to install: psql: ALTER: command not found
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
807989: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=807989
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: gnukhata-core-engine
Version: 2.6.0-2
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed your package failed to install. As
per definition of the release team this makes the package too buggy for
a release, thus the severity.

>From the attached log (scroll to the bottom...):

  Selecting previously unselected package gnukhata-core-engine.
  (Reading database ... 
(Reading database ... 12312 files and directories currently installed.)
  Preparing to unpack .../gnukhata-core-engine_2.6.0-2_all.deb ...
  Unpacking gnukhata-core-engine (2.6.0-2) ...
  Processing triggers for systemd (228-2) ...
  Setting up gnukhata-core-engine (2.6.0-2) ...
  dbconfig-common: writing config to 
/etc/dbconfig-common/gnukhata-core-engine.conf
  
  Creating config file /etc/dbconfig-common/gnukhata-core-engine.conf with new 
version
  creating postgres user gnukhata:  success.
  verifying creation of user: success.
  creating database gnukhata: success.
  verifying database gnukhata exists: success.
  dbconfig-common: flushing administrative password
  Creating/updating gnukhata user account...
  Allow gnukhata user to create databases...
  psql: ALTER: command not found
  dpkg: error processing package gnukhata-core-engine (--configure):
   subprocess installed post-installation script returned error exit status 1
  Processing triggers for systemd (228-2) ...
  Errors were encountered while processing:
   gnukhata-core-engine


cheers,

Andreas


gnukhata-core-engine_2.6.0-2.log.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
Source: gnukhata-core-engine
Source-Version: 2.6.1-2

We believe that the bug you reported is fixed in the latest version of
gnukhata-core-engine, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 807...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Balasankar C  (supplier of updated 
gnukhata-core-engine package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Tue, 08 Mar 2016 18:04:43 +0530
Source: gnukhata-core-engine
Binary: gnukhata-core-engine
Architecture: source
Version: 2.6.1-2
Distribution: unstable
Urgency: medium
Maintainer: Balasankar C 
Changed-By: Balasankar C 
Description:
 gnukhata-core-engine - Free Accounting Software (Core Engine)
Closes: 807989
Changes:
 gnukhata-core-engine (2.6.1-2) unstable; urgency=medium
 .
   * Fix use-su.patch (Closes: #807989)
 - Escape quotes properly
   * Bump Standards Version (No changes)
Checksums-Sha1:
 ee24b08890ff7d71abac67b5c1cf3a4077f7428d 1695 gnukhata-core-engine_2.6.1-2.dsc
 1e0bbf0d251e222325c2ccd1cacc5a37c40530e5 71698 
gnukhata-core-engine_2.6.1.orig.tar.gz
 6ab2e413e5226bb3cafef5c8b330ef55004484a6 443620 
gnukhata-core-engine_2.6.1-2.debian.tar.xz
Checksums-Sha256:
 58b856f4aa177af473b6eeb59daa42578f65d6b8fb21a54b8ccd72fc26f24125 1695 
gnukhata-core-engine_2.6.1-2.dsc
 b4525033cad62f2bdd9e3b5702860fd4049d296e3d62686b12b1902a4be3a45b 71698 
gnukhata-core-engine_2.6.1.orig.tar.gz
 47f1bf5e51bd7470fc78766c2e7ef026a47c6870d59b07f21958569daf28a209 443620 
gnukhata-core-engine_2.6.1-2.debian.tar.xz
Files:
 6a1a0602e73ef4963240500aaa1b672c 1695 python optional 
gnukhata-core-engine_2.6.1-2.dsc
 ca7d2ba4be7f9fb74b1f2f8b07a0b0b3 71698 python optional 
gnukhata-core-engine_2.6.1.orig.tar.gz
 1cf91c98f21e5b36288653aa09b491b9 443620 python optional 
gnukhata-core-engine_2.6.1-2.debian.tar.xz

-BEGIN PGP SIGNATURE-
Version: GnuPG v1

iQEcBAEBCgAGBQJW3tY5AAoJEJbtq5sua3Fxwi0H/2RrPa0pMVqs2p/rIrQdhbaD

Bug#720378: cctools: FTBFS on non-linux

[Steven Chamberlain]

severity 720378 important
user debian-...@lists.debian.org
usertags 720378 + kfreebsd
thanks

Hi,

Sorry, I did not see this bug.  It should have been downgraded because
kfreebsd and hurd are not release architectures.

Regards,
-- 
Steven Chamberlain
ste...@pyro.eu.org


signature.asc
Description: Digital signature

Bug#817011: marked as done (ruby-domain-name: missing RubyGems integration, breaks other softwares like Vagrant)

[Debian Bug Tracking System]

Your message dated Tue, 08 Mar 2016 13:29:52 +
with message-id 
and subject line Bug#817011: fixed in ruby-domain-name 0.5.20160216-2
has caused the Debian Bug report #817011,
regarding ruby-domain-name: missing RubyGems integration, breaks other  
softwares like Vagrant
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
817011: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=817011
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---

Package: ruby-domain-name
Version: 0.5.20160216-1
Severity: grave

Quack,

I just installed Vagrant and got the trace you can find later in this 
message. After some investigation I found your package does not provide 
any gemspec file and tried to create a basic one like this in 
'/usr/share/rubygems-integration/all/specifications/domain_name-0.5.20160216.gemspec':

  Gem::Specification.new do |s|
s.name = "domain_name"
s.version = "0.5.20160216"
  end
It fixed the problem.

I'm in the team but I don't have time or tools at the moment to get into 
more details why this file is missing (I remember gem2deb to already 
have all the necessary magic and this package is using it), sorry.


Regards.

-
$ vagrant
Vagrant experienced a version conflict with some installed plugins!
This usually happens if you recently upgraded Vagrant. As part of the
upgrade process, some existing plugins are no longer compatible with
this version of Vagrant. The recommended way to fix this is to remove
your existing plugins and reinstall them one-by-one. To remove all
plugins:

rm -r ~/.vagrant.d/plugins.json ~/.vagrant.d/gems

Note if you have an alternate VAGRANT_HOME environmental variable
set, the folders above will be in that directory rather than your
user's home directory.

The error message is shown below:

Bundler could not find compatible versions for gem "domain_name":
  In Gemfile:
vagrant (= 1.8.1) was resolved to 1.8.1, which depends on
  rest-client (< 2.0, >= 1.6.0) was resolved to 1.8.0, which depends 
on
http-cookie (< 2.0, >= 1.0.2) was resolved to 1.0.2, which 
depends on

  domain_name (~> 0.5)

Could not find gem 'domain_name (~> 0.5)', which is required by gem 
'http-cookie (< 2.0, >= 1.0.2)', in any of the sources.


--
Marc Dequènes
--- End Message ---
--- Begin Message ---
Source: ruby-domain-name
Source-Version: 0.5.20160216-2

We believe that the bug you reported is fixed in the latest version of
ruby-domain-name, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 817...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Sudheesh Shetty  (supplier of updated 
ruby-domain-name package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Tue, 08 Mar 2016 02:19:59 +0530
Source: ruby-domain-name
Binary: ruby-domain-name
Architecture: source
Version: 0.5.20160216-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Ruby Extras Maintainers 

Changed-By: Sudheesh Shetty 
Description:
 ruby-domain-name - Domain Name manipulation library for Ruby
Closes: 817011
Changes:
 ruby-domain-name (0.5.20160216-2) unstable; urgency=medium
 .
   * Team upload
   * Remove git usage (Closes: #817011)
Checksums-Sha1:
 6e6ff19ede0e79689fc325f9d007b6e4c1e08f62 2171 
ruby-domain-name_0.5.20160216-2.dsc
 a54da5822998b684897202bb9f1b678144bef2b9 4612 
ruby-domain-name_0.5.20160216-2.debian.tar.xz
Checksums-Sha256:
 11375dccca5e6469301bde8e76ff55ebe94a3e3c5ac995c4673de7f6b1060671 2171 
ruby-domain-name_0.5.20160216-2.dsc
 7d44d736bbd3ab377347a70b4381870af73d8998202a323c587e3598e3259779 4612 
ruby-domain-name_0.5.20160216-2.debian.tar.xz
Files:
 48d484780180c9c48bd8578d1f50efbd 2171 ruby optional 
ruby-domain-name_0.5.20160216-2.dsc
 b04c8508712b4d8277a5e501e3f265e6 4612 ruby optional 
ruby-domain-name_0.5.20160216-2.debian.tar.xz

-BEGIN PGP SIGNATURE-
Version: GnuPG v1

iQIcBAEBCAAGBQJW3s9sAAoJEM4fnGdFEsIqbfAP/05/e5o3uLcGSLBzv03gQUgw

Bug#816376: [Pkg-owncloud-maintainers] Bug#816376: Bug#816376: Unfit upstream

[Jos Poortvliet]

On dinsdag 8 maart 2016 08:37:35 CET David Prévot wrote:
> Hi,
> 
> Le 08/03/2016 03:03, Jos Poortvliet a écrit :
> > The situation is rather sad and frustrating
> 
> OK.
> 
> > as users who decided to trust the Debian developers and took their
> > packages over ownCloud's provided packages are now stuck on a version
> > which can't trivially be upgraded to either our upstream version or
> > anything else.
> The thing is, we were working on a proper upgrade path, but upstream
> decided without even looking at it that it was “bad” (to put it mildly).
> Because of upstream reaction, we have removed our work in progress, and
> 
> now the PR crap (as in words not backed by anything) follows:
> > We would love to find a solution for them

I know that that is how you choose to look at it - and I feel there is no 
value to discuss that.

> Regards
> 
> David


-- 
Disclaimer:
Everything I do and say is based on my view of the world today. I am not 
responsible for changes in the world, nor my view on it. Everything I say is 
meant in a positive and friendly way, unless explicitly stated otherwise.
find me on blog.jospoortvliet.com

Bug#816376: [Pkg-owncloud-maintainers] Bug#816376: Bug#816376: Unfit upstream

[David Prévot]

Hi,

Le 08/03/2016 03:03, Jos Poortvliet a écrit :

> The situation is rather sad and frustrating

OK.

> as users who decided to trust the Debian developers and took their packages 
> over ownCloud's provided packages are now stuck on a version which can't 
> trivially be upgraded to either our upstream version or anything else.

The thing is, we were working on a proper upgrade path, but upstream
decided without even looking at it that it was “bad” (to put it mildly).
Because of upstream reaction, we have removed our work in progress, and
now the PR crap (as in words not backed by anything) follows:

> We would love to find a solution for them

Regards

David



signature.asc
Description: OpenPGP digital signature

Bug#817139: [Pkg-sass-devel] Bug#817139: sassc: trying to overwrite '/usr/share/man/man1/sassc.1.gz', which is also in package pysassc 0.9.3-1

[Jonas Smedegaard]

Quoting Axel Beckert (2016-03-08 13:14:54)
> Trying to install sassc with pysassc installed causes a file conflict:
> 
> Unpacking sassc (3.3.2-3) ...
> dpkg: error processing archive 
> /var/cache/apt/archives/sassc_3.3.2-3_amd64.deb (--unpack):
>  trying to overwrite '/usr/share/man/man1/sassc.1.gz', which is also in 
> package pysassc 0.9.3-1

The name "sassc" means "Sass implemented in C".

Since the package name "pysassc" seems to imply "sassc wrapper 
implemented in Python", I believe the proper fix here is for pysassc to 
not provide binary "sassc" but instead "pysassc".

...or simply drop the package pysassc, because there should be no need 
for that wrapper on systems where the real sassc is available.


 - Jonas

-- 
 * Jonas Smedegaard - idealist & Internet-arkitekt
 * Tlf.: +45 40843136  Website: http://dr.jones.dk/

 [x] quote me freely  [ ] ask before reusing  [ ] keep private


signature.asc
Description: signature

Bug#809565: marked as done (bind-dyndb-ldap: FTBFS: -Werror=date-time)

[Debian Bug Tracking System]

Your message dated Tue, 08 Mar 2016 12:34:08 +
with message-id 
and subject line Bug#809565: fixed in bind-dyndb-ldap 8.0-2
has caused the Debian Bug report #809565,
regarding bind-dyndb-ldap: FTBFS: -Werror=date-time
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
809565: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=809565
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: bind-dyndb-ldap
Version: 8.0-1
Severity: serious
Justification: fails to build from source
Tags: sid stretch
User: reproducible-bui...@lists.alioth.debian.org
Usertags: ftbfs
X-Debbugs-CC: reproducible-bui...@lists.alioth.debian.org

Dear Maintainer,

The package fails to build.  dpkg-buildflags has (since 2015-12-25)
included a new warning, which -Werror is making fatal:

libtool: compile:  gcc -DHAVE_CONFIG_H -I. -I../../src -I.. -Wdate-time 
-D_FORTIFY_SOURCE=2 -Wall -Wextra -Werror -std=gnu99 -O2 -I/usr/include 
-D_REENTRANT -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 -D_GNU_SOURCE -g -O2 
-fstack-protector-strong -Wformat -Werror=format-security -fvisibility=hidden 
-c ../../src/zone_manager.c  -fPIC -DPIC -o .libs/ldap_la-zone_manager.o
../../src/zone_manager.c: In function 'initialize_manager':
../../src/zone_manager.c:52:29: error: macro "__TIME__" might prevent 
reproducible builds [-Werror=date-time]
", compiler " __VERSION__);
 ^
../../src/zone_manager.c:52:29: error: macro "__DATE__" might prevent 
reproducible builds [-Werror=date-time]
cc1: all warnings being treated as errors
Makefile:645: recipe for target 'ldap_la-zone_manager.lo' failed
make[3]: *** [ldap_la-zone_manager.lo] Error 1
make[3]: Leaving directory '/bind-dyndb-ldap-8.0/build/src'

Full build log:
https://reproducible.debian.net/rb-pkg/unstable/amd64/bind-dyndb-ldap.html

-- System Information:
Debian Release: stretch/sid
APT prefers unstable
APT policy: (500, 'unstable')
Architecture: amd64 (x86_64)
--- End Message ---
--- Begin Message ---
Source: bind-dyndb-ldap
Source-Version: 8.0-2

We believe that the bug you reported is fixed in the latest version of
bind-dyndb-ldap, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 809...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Timo Aaltonen  (supplier of updated bind-dyndb-ldap 
package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Format: 1.8
Date: Tue, 08 Mar 2016 14:26:34 +0200
Source: bind-dyndb-ldap
Binary: bind9-dyndb-ldap
Architecture: source
Version: 8.0-2
Distribution: experimental
Urgency: medium
Maintainer: Debian FreeIPA Team 
Changed-By: Timo Aaltonen 
Description:
 bind9-dyndb-ldap - LDAP back-end plug-in for BIND
Closes: 809565 815167
Changes:
 bind-dyndb-ldap (8.0-2) experimental; urgency=medium
 .
   [ Timo Aaltonen ]
   * rules: Revert to using multiarch install path so that bind can
 find the plugin without further configuration.
   * rules, install: Install via debian/tmp.
   * control: Bump libbind-dev build-dep and bind9 dep to 9.10.3 for the
 multiarch switch.
 .
   [ Matthias Klose ]
   * fix-werror-build.diff: Fix build failure with -Werror.
 (Closes: #809565)
   * workaround-missing-headers.patch: Updated files from current bind9
 (Closes: #815167)
Checksums-Sha1:
 7d1d7958eb238bc8967550ce2b29d661d57f1da9 2067 bind-dyndb-ldap_8.0-2.dsc
 bd9138eb96e2072b88d4993a3a41438afa8aa9ed 5272 
bind-dyndb-ldap_8.0-2.debian.tar.xz
Checksums-Sha256:
 a793e614a40632edf7286b6a3700d0ef2deca48e056c99d193385cff8e538d59 2067 
bind-dyndb-ldap_8.0-2.dsc
 2a902d61c60576d1c4514a50640f9e5972a6c9962ed8f7f18a9e8655327500c6 5272 
bind-dyndb-ldap_8.0-2.debian.tar.xz
Files:
 d4dd6238ade66f4565abbdd05638e5ca 2067 net optional bind-dyndb-ldap_8.0-2.dsc
 bbc4ef15466809470a33497f52fcc351 5272 net optional 
bind-dyndb-ldap_8.0-2.debian.tar.xz

-BEGIN PGP SIGNATURE-
Version: GnuPG v1

iQIcBAEBAgAGBQJW3sUVAAoJEMtwMWWoiYTcbLgP+gMxf8eQu4HgGl5luMyEVsLD
C0QKDRkJYBYRCgtQSih/EeoXjxVbSZa6yGwynIXwnYJ7lEAPHIW9VnKGHQDj/qw6

Bug#817139: sassc: trying to overwrite '/usr/share/man/man1/sassc.1.gz', which is also in package pysassc 0.9.3-1

[Axel Beckert]

Package: sassc,pysassc
Severity: serious
Version: sassc/3.3.2-3 pysassc/0.9.3-1

Trying to install sassc with pysassc installed causes a file conflict:

Unpacking sassc (3.3.2-3) ...
dpkg: error processing archive /var/cache/apt/archives/sassc_3.3.2-3_amd64.deb 
(--unpack):
 trying to overwrite '/usr/share/man/man1/sassc.1.gz', which is also in package 
pysassc 0.9.3-1

-- System Information:
Debian Release: stretch/sid
  APT prefers unstable
  APT policy: (990, 'unstable'), (600, 'testing'), (500, 'unstable-debug'), 
(500, 'buildd-unstable'), (400, 'stable'), (110, 'experimental'), (1, 
'experimental-debug'), (1, 'buildd-experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.2.0-trunk-amd64 (SMP w/1 CPU core)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: sysvinit (via /sbin/init)

Bug#817025: marked as done (fleet: FTBFS: coreos.go:26:2: cannot find package "github.com/opencontainers/runc/libcontainer/netlink)

[Debian Bug Tracking System]

Your message dated Tue, 08 Mar 2016 11:49:51 +
with message-id 
and subject line Bug#817025: fixed in fleet 0.11.5+dfsg1-4
has caused the Debian Bug report #817025,
regarding fleet: FTBFS: coreos.go:26:2: cannot find package 
"github.com/opencontainers/runc/libcontainer/netlink
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
817025: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=817025
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: fleet
Version: 0.11.5+dfsg1-3
Severity: serious
Justification: fails to build from source
User: reproducible-bui...@lists.alioth.debian.org
Usertags: ftbfs
X-Debbugs-Cc: reproducible-bui...@lists.alioth.debian.org

Dear Maintainer,

fleet fails to build from source in unstable/amd64:

   dpkg-buildpackage -rfakeroot -D -us -uc -b
  dpkg-buildpackage: source package fleet
  dpkg-buildpackage: source version 0.11.5+dfsg1-3
  dpkg-buildpackage: source distribution unstable
  dpkg-buildpackage: source changed by Dmitry Smirnov 
   dpkg-source --before-build fleet-0.11.5+dfsg1
  dpkg-buildpackage: host architecture amd64
   fakeroot debian/rules clean
  dh clean --buildsystem=golang --with=golang,systemd --builddirectory=_build
 dh_testdir -O--buildsystem=golang -O--builddirectory=_build
 dh_auto_clean -O--buildsystem=golang -O--builddirectory=_build
 debian/rules override_dh_clean
  make[1]: Entering directory 
'/home/lamby/temp/cdt.20160307093644.V5UHlwQuzu/fleet-0.11.5+dfsg1'
  dh_clean
  ## Remove Files-Excluded (when built from checkout or non-DFSG tarball):
  rm -f -rv `perl -0nE 'say $1 if 
m{^Files\-Excluded\:\s*(.*?)(?:\n\n|Files:|Comment:)}sm;' debian/copyright`
  make[1]: Leaving directory 
'/home/lamby/temp/cdt.20160307093644.V5UHlwQuzu/fleet-0.11.5+dfsg1'
   debian/rules build
  make: 'build' is up to date.
   fakeroot debian/rules binary
  dh binary --buildsystem=golang --with=golang,systemd --builddirectory=_build
 dh_testdir -O--buildsystem=golang -O--builddirectory=_build
 dh_update_autotools_config -O--buildsystem=golang -O--builddirectory=_build
 debian/rules override_dh_auto_configure
  make[1]: Entering directory 
'/home/lamby/temp/cdt.20160307093644.V5UHlwQuzu/fleet-0.11.5+dfsg1'
  dh_auto_configure
  perl -0nE 'say $1 if 
m{^Files\-Excluded\:\s*(.*?)(?:\n\n|Files:|Comment:)}sm;' debian/copyright \
  | while read D; do D="${D##Godeps/_workspace/src/}" ; printf 
"Removing third party bundle: $D\n" ;\
  perl -pi -E 
"s{github.com/coreos/fleet/Godeps/_workspace/src/$D}{$D}msg;" `find _build/src 
-type f -name "*.go"` ;\
  done
  Removing third party bundle: code.google.com/p/go-uuid
  Removing third party bundle: github.com/coreos/etcd
  Removing third party bundle: github.com/coreos/go-semver
  Removing third party bundle: 
~Godeps/_workspace/src/github.com/coreos/go-systemd
  Removing third party bundle: github.com/docker/libcontainer
  Removing third party bundle: github.com/godbus/dbus
  Removing third party bundle: github.com/jonboulle/clockwork
  Removing third party bundle: github.com/rakyll/globalconf
  Removing third party bundle: github.com/rakyll/goini
  Removing third party bundle: golang.org/x/crypto
  Removing third party bundle: golang.org/x/net
  Removing third party bundle: google.golang.org/api/google-api-go-generator
  Removing third party bundle: google.golang.org/api/googleapi
  make[1]: Leaving directory 
'/home/lamby/temp/cdt.20160307093644.V5UHlwQuzu/fleet-0.11.5+dfsg1'
 dh_auto_build -O--buildsystem=golang -O--builddirectory=_build
go install -v github.com/coreos/fleet/fleetd 
github.com/coreos/fleet/fleetctl
  src/github.com/coreos/fleet/machine/coreos.go:26:2: cannot find package 
"github.com/opencontainers/runc/libcontainer/netlink" in any of:
/usr/lib/go/src/github.com/opencontainers/runc/libcontainer/netlink 
(from $GOROOT)

/home/lamby/temp/cdt.20160307093644.V5UHlwQuzu/fleet-0.11.5+dfsg1/_build/src/github.com/opencontainers/runc/libcontainer/netlink
 (from $GOPATH)
  dh_auto_build: go install -v github.com/coreos/fleet/fleetd 
github.com/coreos/fleet/fleetctl returned exit code 1
  debian/rules:10: recipe for target 'binary' failed
  make: *** [binary] Error 1

  [..]

The full build log is attached.


Regards,

-- 
  ,''`.
 : :'  : Chris Lamb
 `. `'`  la...@debian.org / chris-lamb.co.uk
   `-


fleet.0.11.5+dfsg1-3.unstable.amd64.log.txt.gz
Description: Binary data
--- End Message ---
--- Begin Message ---
Source: fleet
Source-Version: 

Bug#817025: Pending fixes for bugs in the fleet package

[pkg-go-maintainers]

tag 817025 + pending
thanks

Some bugs in the fleet package are closed in revision
d8d83e5c33b0c562a55cd643589b651c683f0a38 in branch 'master' by Dmitry
Smirnov

The full diff can be seen at
https://anonscm.debian.org/cgit/pkg-go/packages/fleet.git/commit/?id=d8d83e5

Commit message:

Switch to vishvananda-netlink, fixes FTBFS (Closes: #817025)

Processed: Pending fixes for bugs in the fleet package

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> tag 817025 + pending
Bug #817025 [src:fleet] fleet: FTBFS: coreos.go:26:2: cannot find package 
"github.com/opencontainers/runc/libcontainer/netlink
Added tag(s) pending.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
817025: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=817025
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#816857: gimagereader: fails to launch with "symbol lookup error"

[Philip Rinn]

Hi all,

just to keep you informed: The ABI breakage is fixed upstream now:

https://github.com/tesseract-ocr/tesseract/commit/7461b617433757105db08b3bb4fca47eee3c96d7

Best,
Philip


signature.asc
Description: PGP signature

Processed: retitle 814968 to src:hunspell] hunspell: FTBFS: various tests FAIL

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> retitle 814968 src:hunspell] hunspell: FTBFS: various tests FAIL
Bug #814968 [src:hunspell] hunspell: FTBFS: FAIL: map.test
Changed Bug title to 'src:hunspell] hunspell: FTBFS: various tests FAIL' from 
'hunspell: FTBFS: FAIL: map.test'
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
814968: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=814968
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Processed: bug 814968 is forwarded to László Németh <laszlo.nem...@collabora.com>

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> forwarded 814968 László Németh 
Bug #814968 [src:hunspell] hunspell: FTBFS: FAIL: map.test
Set Bug forwarded-to-address to 'László Németh '.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
814968: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=814968
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#817006: [PKG-OpenRC-Debian] Bug#817006: ack to NMU

[Benda Xu]

Hi Adam,

Adam Borowski  writes:

> The popcon for openrc is 83, which, assuming that 10% of users run popcon
> (a wild-ass guess) means 830 users.  I have no idea what part of this is
> unstable, but as openrc in Debian is quite experimental, I guess quite a
> bunch of such users are affected.
>
> The breakage is pretty severe -- it does match the description of "critical"
> after all.  Every affected user would have to research the fix and apply
> it manually.  Thus, I don't think it's a good idea to ignore this bug,
> especially that the fix is easy.

Okay, I will take this lesson. Thank you for your help!

>> That said, I understand theoretically your NMU is the correctly way to
>> go.  So if you intend to do so, consider this email as an ack to NMU
>> from the maintainer team.
>
> I'll upload it then.

Great!  It is in Sid now.

>> One thing to notice is that we are tracking the package at
>> 
>>   http://anonscm.debian.org/cgit/openrc/openrc.git
>> 
>> Would you mind if I ask you to prepare a commit to the master
>> corresponding to the NMU?
>
> Of course.  I don't have push rights to that repository, so two commits are
> attached to this mail (one for the fix, one for changelog).

Applied and pushed.

You could apply at

https://alioth.debian.org/projects/openrc

to get push rights.

>> BTW, if you are interested in OpenRC, you are welcomed to join the
>> maintenance team.
>
> I'm afraid I don't really know inner workings of openrc, I use it on only
> one machine (which happens to be my main desktop, but still...).  Everywhere
> else I'm on sysv-rc.

Ah-ha. Me too, desktops, laptops or newly installed servers (those I
could access the consoles).

> This said, keeping openrc viable seems important for resisting
> systemd-ization of Debian so I probably should help in _some_ way.

Agreed.

>> 1. 0.20.4-1 was uploaded in a hurry to keep itself in testing.  The pts
>> system lied and we did not make it.  divert should not have existed in
>> OpenRC.
>
> It can be removed in some time, after the affected systems are fixed.

Okay.


Also I would like to thank Andreas for pointing this out.

Yours,
Benda

Bug#788108: Processed: severity of 788108 is serious, tagging 788108

[Laurent Bigonville]

Le 04/03/16 03:05, Lisandro Damián Nicanor Pérez Meyer a écrit :

On Monday 22 February 2016 11:45:56 Lisandro Damián Nicanor Pérez Meyer wrote:

It was discussed in upstream's mailing list, but I'm on the phone now :(

According to 5.6.0's git repo:

  - [QTBUG-40702] Removed dependency towards libgeoclue. The plugin uses the
GeoClue DBus interface.

I'm now working to disable the support in 5.5.1 to close this bug ASAP. We
need to understand what we will need to depend upon for 5.6.

Laurent: does it rings you any bells?

For the runtime dependency, you should Depends/Recommends/Suggests the 
geoclue-2.0 package.


If your code is resilient enough and support the case where the daemon 
is not installed, I would personally go for the Recommends.

Bug#725629: vice: sometimes FTBFS: error while opening "src/arch/win32/res.rc.po.c" for reading: No such file or directory

[Graham Inggs]

Hi Maintainer

This problem still occurs from time to time.

See build logs of:

2.4.dfsg+2.4.20-1 on hurd-i386
https://buildd.debian.org/status/fetch.php?pkg=vice=hurd-i386=2.4.dfsg%2B2.4.20-1=1431810973

2.4.dfsg+2.4.24-2 on kfreebsd-amd64
https://buildd.debian.org/status/fetch.php?pkg=vice=kfreebsd-amd64=2.4.dfsg%2B2.4.24-2=1454237493

2.4.dfsg+2.4.25-1 on kfreebsd-i386
https://buildd.debian.org/status/fetch.php?pkg=vice=kfreebsd-i386=2.4.dfsg%2B2.4.25-1=1455382728

Regards
Graham

Bug#814976: marked as done (whitedune: FTBFS: dune1.rc.c:1392: syntax error)

[Debian Bug Tracking System]

Your message dated Tue, 08 Mar 2016 10:07:26 +
with message-id 
and subject line Bug#814976: fixed in whitedune 0.30.10-2.1
has caused the Debian Bug report #814976,
regarding whitedune: FTBFS: dune1.rc.c:1392: syntax error
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
814976: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=814976
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: whitedune
Version: 0.30.10-2
Severity: serious
Justification: fails to build from source
User: reproducible-bui...@lists.alioth.debian.org
Usertags: ftbfs
X-Debbugs-Cc: reproducible-bui...@lists.alioth.debian.org

Dear Maintainer,

whitedune fails to build from source in unstable/amd64:

  [..]

  sed 's../.' < dune.rc > dune1.rc.c
  x86_64-linux-gnu-g++ -E dune1.rc.c > dune2.rc.c 
  grep -v '//' dune2.rc.c > dune3.rc.c
  if swt/rc/rc < dune3.rc.c > resource.c ; then echo > /dev/null; else rm  
resource.c ; exit 1 ; fi
  dune1.rc.c:1392: syntax error
  Makefile:772: recipe for target 'resource.c' failed
  make[3]: *** [resource.c] Error 1
  make[3]: Leaving directory 
'/home/lamby/temp/cdt.20160217094002.tEG6aPBGFU/whitedune-0.30.10/src'
  Makefile:568: recipe for target 'target' failed
  make[2]: *** [target] Error 2
  make[2]: Leaving directory 
'/home/lamby/temp/cdt.20160217094002.tEG6aPBGFU/whitedune-0.30.10/src'
  Makefile:5: recipe for target 'dune' failed
  make[1]: *** [dune] Error 2
  make[1]: Leaving directory 
'/home/lamby/temp/cdt.20160217094002.tEG6aPBGFU/whitedune-0.30.10'
  debian/rules:39: recipe for target 'build-stamp' failed
  make: *** [build-stamp] Error 2

  [..]

The full build log is attached.


Regards,

-- 
  ,''`.
 : :'  : Chris Lamb
 `. `'`  la...@debian.org / chris-lamb.co.uk
   `-


whitedune.0.30.10-2.unstable.amd64.log.txt.gz
Description: Binary data
--- End Message ---
--- Begin Message ---
Source: whitedune
Source-Version: 0.30.10-2.1

We believe that the bug you reported is fixed in the latest version of
whitedune, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 814...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Raúl Benencia  (supplier of updated whitedune package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Mon, 07 Mar 2016 07:56:28 -0800
Source: whitedune
Binary: whitedune whitedune-docs
Architecture: source all
Version: 0.30.10-2.1
Distribution: unstable
Urgency: medium
Maintainer: Debian Multimedia Maintainers 

Changed-By: Raúl Benencia 
Description:
 whitedune  - graphical VRML97/X3D viewer, editor, 3D modeller and animation to
 whitedune-docs - documentation for whitedune
Closes: 814976
Changes:
 whitedune (0.30.10-2.1) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * Fix FTBFS due new binary matching behavior on grep (Closes: #814976)
Checksums-Sha1:
 cf7402ef71466278b38c668e5f9c5fd21d9e11c5 2201 whitedune_0.30.10-2.1.dsc
 5640d2b2f2c9f8822f6b337bf64de29a8dec6d39 9312 
whitedune_0.30.10-2.1.debian.tar.xz
 e447cb110fa68a4d3eaa0339933d4488c93f7520 6342958 
whitedune-docs_0.30.10-2.1_all.deb
Checksums-Sha256:
 f860b77e8fc922be2b2f585c67cbbf0f05680e766296f9a174fba359443ee311 2201 
whitedune_0.30.10-2.1.dsc
 3de13f8f0ebf765d27219fb23cfc88f5c3f0ab5fa057987c685ee4ba879fe2a0 9312 
whitedune_0.30.10-2.1.debian.tar.xz
 623bb0a98f2a3108cae79a5deee5498d78b01f201dd75cbf8596933d0498bb5d 6342958 
whitedune-docs_0.30.10-2.1_all.deb
Files:
 50ac986fa5f4b41e1d7d9493e4dd44b5 2201 graphics optional 
whitedune_0.30.10-2.1.dsc
 fa967983265945d192b72c26eaac5463 9312 graphics optional 
whitedune_0.30.10-2.1.debian.tar.xz
 50d3e5cd633e244b35b243243c1ad77b 6342958 doc optional 
whitedune-docs_0.30.10-2.1_all.deb

-BEGIN PGP SIGNATURE-
Version: GnuPG v1

iQIcBAEBCAAGBQJW3pJfAAoJEGny/FFupxmTdHEP/0fXCo8GN1/QuhUTC8U8kG71
yIzRb11U4RA637lCbSNtJ6rhPjg0j5SmAk3MpnLSb0h897OxHZxU3Toy8Hq0QhDA
RXAZXC2lAzrOc93UKwuZ09Tcw2YGRMqqERe2ueBs5XdSHm6xs4KY/hTdSTdSn6gc
cBRXh+IrZDRn6BK8IUQ1Bq6SC8aPwWG4B2nlBBFeAS3QXy2j9ONav7PNBYmmwkN8

Processed: vice: sometimes FTBFS: error while opening "src/arch/win32/res.rc.po.c" for reading: No such file or directory

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> unarchive 725629
Bug #725629 {Done: László Böszörményi (GCS) } [src:vice] vice: 
sometimes FTBFS: error while opening "src/arch/win32/res.rc.po.c" for reading: 
No such file or directory
Bug #756916 {Done: László Böszörményi (GCS) } [src:vice] vice: 
sometimes FTBFS: error while opening "src/arch/win32/res.rc.po.c" for reading: 
No such file or directory
Unarchived Bug 725629
Unarchived Bug 756916
> found 725629 vice/2.4.dfsg+2.4.20-1
Bug #725629 {Done: László Böszörményi (GCS) } [src:vice] vice: 
sometimes FTBFS: error while opening "src/arch/win32/res.rc.po.c" for reading: 
No such file or directory
Bug #756916 {Done: László Böszörményi (GCS) } [src:vice] vice: 
sometimes FTBFS: error while opening "src/arch/win32/res.rc.po.c" for reading: 
No such file or directory
Marked as found in versions vice/2.4.dfsg+2.4.20-1 and reopened.
Marked as found in versions vice/2.4.dfsg+2.4.20-1 and reopened.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
725629: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=725629
756916: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=756916
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#817006: marked as done (openrc: dangling diversion of /usr/sbin/{invoke,update}-rc.d)

[Debian Bug Tracking System]

Your message dated Tue, 08 Mar 2016 09:53:54 +
with message-id 
and subject line Bug#817006: fixed in openrc 0.20.4-2.1
has caused the Debian Bug report #817006,
regarding openrc: dangling diversion of /usr/sbin/{invoke,update}-rc.d
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
817006: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=817006
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: openrc
Version: 0.20.4-2
Severity: critical
Justification: breaks unrelated software


I'm afrad the removal of diversions of /usr/sbin/{invoke,update}-rc.d
without undiverting them breaks anything that uses those scripts.  This
makes many packages uninstallable:
.--===
Setting up virtualbox (5.0.16-dfsg-2) ...
/var/lib/dpkg/info/virtualbox.postinst: 34: 
/var/lib/dpkg/info/virtualbox.postinst: update-rc.d: not found
dpkg: error processing package virtualbox (--configure):
 subprocess installed post-installation script returned error exit status 127
Setting up exim4-base (4.86.2-2) ...
/var/lib/dpkg/info/exim4-base.postinst: 88: 
/var/lib/dpkg/info/exim4-base.postinst: update-rc.d: not found
dpkg: error processing package exim4-base (--configure):
 subprocess installed post-installation script returned error exit status 127
`--===

Another casualty is logrotate:
.--===
/etc/cron.daily/logrotate:
logrotate_script: 2: logrotate_script: invoke-rc.d: not found
error: error running non-shared postrotate script for /var/log/syslog of 
'/var/log/syslog
'
logrotate_script: 2: logrotate_script: invoke-rc.d: not found
error: error running shared postrotate script for '/var/log/mail.info
`--===

I dared not to try to reboot to see if this makes the system unbootable as
well, which might be the case.


As noted by Andreas Hendriksson in #811708, you need to undivert on all
systems that had 0.20.4-1 installed, but not on those upgraded from jessie
or those who installed 0.20.4-2 anew.  The version check proposed by Andreas
won't work, as an upgrade to 0.20.4-2 removes such information.  Thus, we'd
need to check whether such a diversion exists and was created by openrc
rather than as an action by the sysadmin.

Thus, I propose guarding it with:
if [ "$(dpkg-divert --list /usr/sbin/invoke-rc.d)" = "diversion of 
/usr/sbin/invoke-rc.d to /usr/sbin/invoke-rc.d.init-system-helpers by openrc" ]


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

Kernel: Linux 4.4.1-x32 (SMP w/6 CPU cores)
Locale: LANG=C.UTF-8, LC_CTYPE=C.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: sysvinit (via /sbin/init)

Versions of packages openrc depends on:
ii  insserv  1.14.0-5.3
ii  libaudit11:2.4.5-1+b1
ii  libc62.21-9
ii  libeinfo10.20.4-2
ii  libpam0g 1.1.8-3.2
ii  librc1   0.20.4-2
ii  libselinux1  2.4-3+b1

Versions of packages openrc recommends:
ii  init-system-helpers  1.29

Versions of packages openrc suggests:
pn  policycoreutils  

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: openrc
Source-Version: 0.20.4-2.1

We believe that the bug you reported is fixed in the latest version of
openrc, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 817...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Adam Borowski  (supplier of updated openrc package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Tue, 08 Mar 2016 05:17:44 +0100
Source: openrc
Binary: openrc openrc-dbg librc1 librc1-dbg librc-dev libeinfo1 libeinfo1-dbg 
libeinfo-dev
Architecture: source
Version: 0.20.4-2.1
Distribution: unstable
Urgency: medium
Maintainer: OpenRC Debian Maintainers 
Changed-By: Adam Borowski 

Bug#817124: librarian-puppet requires 'rsync' gem but it doesn't exist

[Vincent Bernat]

Package: librarian-puppet
Version: 2.2.1-1
Severity: grave

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Hi!

After the latest update of librarian-puppet, just running it triggers this 
error:

/usr/lib/ruby/2.3.0/rubygems/core_ext/kernel_require.rb:55:in `require': cannot 
load such file -- rsync (LoadError)
from /usr/lib/ruby/2.3.0/rubygems/core_ext/kernel_require.rb:55:in 
`require'
from /usr/lib/ruby/vendor_ruby/librarian/puppet/util.rb:1:in `'
from /usr/lib/ruby/2.3.0/rubygems/core_ext/kernel_require.rb:55:in 
`require'
from /usr/lib/ruby/2.3.0/rubygems/core_ext/kernel_require.rb:55:in 
`require'
from /usr/lib/ruby/vendor_ruby/librarian/puppet/source/local.rb:1:in 
`'
[...]

There doesn't seem to be any gem available for this in Debian.

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

Kernel: Linux 4.4.0-1-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
Init: systemd (via /run/systemd/system)

Versions of packages librarian-puppet depends on:
ii  puppet-common   3.8.5-1
ii  ruby1:2.3.0+1
ii  ruby-json   1.8.3-1+b2
ii  ruby-librarian  0.1.2-1
ii  ruby2.1 [ruby-interpreter]  2.1.5-4
ii  ruby2.2 [ruby-interpreter]  2.2.4-1
ii  ruby2.3 [ruby-interpreter]  2.3.0-4

librarian-puppet recommends no packages.

librarian-puppet suggests no packages.

- -- no debconf information

-BEGIN PGP SIGNATURE-
Version: GnuPG v1

iQIcBAEBCAAGBQJW3p1xAAoJEJWkL+g1NSX5QIAP/iv78RKifK7DP0JHcBSG30T3
9w+bKTVz/KiacomnJ8Grgf/QQQ0CNpfviDZX+/EjkZxzLjhfDEK3kAwFwDYoZP4Z
EX5VhqcmqDmAQJrRYCey5FEI9PNiGxNXZQcz2yiO9r/QqQr2HDJg5ZcYylnEIA0x
mxvjQ77KW6FbuSmKQmhY1PSyGwVAr4gHfuuh/icjFf3u6LzDWWvAi/2uHhu/XpTu
ZIStil5U2oaWIOO0+9PCkNh7Qn4Rjfxg4hEYxLmQsVGmq9rPiQbgpgM/N5Dz9eks
xIc7RoaHhWZxIgT+JE0tzCa9oEZi+ag8ZU2y3JKM1wj+A7q7BXLOgYiRiKXdPqE0
PDFQKISWfNd4NDKYahJI4YpgidOmURMKsOEolIcgZ0vB3mCv3f2rEGqfSdb5O8Kf
aNP5Kmpgjwfynd8RtEzPxFPutqey9DIiQTLou/aGcEvx2HbMov8UdU5RQEh1kp6r
nevRskZMb7n1JSBtBKhjPqzHT7xg1YLGJHanURO3glbAn3McZbk+5kPvWh85pQ1p
ZkjjuAbgRua11qdpumzsdA3h9f/f8px3yMCja36LH6LWnHwBc6J6fP3czGyO/PaH
1F2Ek35w9dswiVPevTI6GQUgVqQ0Eekq2w8xPvRqtKJzuG5/L/goURlwEmKh2BJl
V9Bdic3wzEhB2U05vzpP
=r44l
-END PGP SIGNATURE-

Processed: tagging 815292

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> # 
> http://anonscm.debian.org/cgit/pkg-openoffice/libreoffice.git/commit/?id=e3430f742f8c0e572af50051da836e3d9877338f
> tags 815292 + pending
Bug #815292 [src:libreoffice] libreoffice: FTBFS on i386: test failure: 
testFlipAndRotateCustomShape::Import_Export_Import
Added tag(s) pending.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
815292: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=815292
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#771241: still not available in jessie?

[Luca Olivetti]

I'm having this issue in jessie with 3:5.06-2+deb8u1.
Looking at the changelog it seems this fix hasn't been backported.

Bug#814976: whitedune: diff for NMU version 0.30.10-2.1

[Sebastian Ramacher]

On 2016-03-07 23:22:58, Raúl Benencia wrote:
> Control: tags 814976 + patch
> Control: tags 814976 + pending
> 
> Dear maintainer,
> 
> This bug is caused by a recent update on grep. This update modified a bit
> the heuristic used for determining when the given input is binary.
> 
> I've prepared an NMU for whitedune (versioned as 0.30.10-2.1). As I don't
> have privileges to upload it to DELAYED, I've uploaded it to the mentors
> repository.
> 
> To access further information about this package, please visit the
> following URL:
> 
>   http://mentors.debian.net/package/whitedune
> 
> 
> Alternatively, one can download the package with dget using this command:
> 
>   dget -x 
> http://mentors.debian.net/debian/pool/main/w/whitedune/whitedune_0.30.10-2.1.dsc

Thank you, uploaded.

Cheers
-- 
Sebastian Ramacher


signature.asc
Description: PGP signature

Bug#814976: marked as pending

[Sebastian Ramacher]

tag 814976 pending
thanks

Hello,

Bug #814976 reported by you has been fixed in the Git repository. You can
see the changelog below, and you can check the diff of the fix at:

http://git.debian.org/?p=pkg-multimedia/whitedune.git;a=commitdiff;h=13dc236

---
commit 13dc236a9ac4f19c9814be77288da32c8d6657d7
Author: Raúl Benencia 
Date:   Mon Mar 7 07:56:28 2016 -0800

Imported Debian patch 0.30.10-2.1

diff --git a/debian/changelog b/debian/changelog
index 7cf0f85..d96ef00 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,10 @@
+whitedune (0.30.10-2.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Fix FTBFS due new binary matching behavior on grep (Closes: #814976)
+
+ -- Raúl Benencia   Mon, 07 Mar 2016 07:56:28 -0800
+
 whitedune (0.30.10-2) unstable; urgency=medium
 
   * Team upload.

Bug#817011: vagrant: domain_name gem not found

[Antonio Terceiro]

Control: done -1
Control: affects 817011 + vagrant

On Mon, Mar 07, 2016 at 12:10:33PM -0500, Guy Hughes wrote:
> Package: vagrant
> Version: 1.8.1+dfsg-1
> Severity: grave
> Justification: renders package unusable
> 
> Dear Maintainer,
> 
> Until #817011 on ruby-domain-name is fixed by the maintainer, vagrant
> does not work without a manual fix (gemspec file) available in the bts
> report.[1] See below.
> 
> I'm reporting this against your package for the benefit of others,
> especially those using virtualbox from sid.

Thanks for your concern, but creating duplicate bugs on affected
packages is not useful as there is nothing to be fixed on them.

The BTS has a feature to say that a bug affects other packages, what is
what I am doing now.


signature.asc
Description: PGP signature

Processed (with 1 error): Re: Bug#817011: vagrant: domain_name gem not found

[Debian Bug Tracking System]

Processing control commands:

> done -1
Unknown command or malformed arguments to command.

> affects 817011 + vagrant
Bug #817011 [ruby-domain-name] ruby-domain-name: missing RubyGems integration, 
breaks other  softwares like Vagrant
Added indication that 817011 affects vagrant

-- 
817011: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=817011
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Processed: Bug#814976 marked as pending

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> tag 814976 pending
Bug #814976 [src:whitedune] whitedune: FTBFS: dune1.rc.c:1392: syntax error
Ignoring request to alter tags of bug #814976 to the same tags previously set
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
814976: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=814976
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#817041: librem0: Missing run-time dependency on libre0

[Vasudev Kamath]

Guillem Jover  writes:

> Package: librem0
> Version: 0.4.7-1
> Severity: serious
>
> Hi!
>
> This package provides a shared library that is not self-contained, and
> it is missing a run-time dependency on libre0, as it uses some of its
> symbols. The library should link against all libraries it uses directly,
> because otherwise it is pushing an internal implementation detail towards
> its users.
>
> A very simple example to illustrate:
>
>   $ echo 'int main() { return 0; }' >rem.c
>   $ gcc -o rem rem.c -lrem
>   [ lots of undefined references to missing symbols… ]

Oh.. That is new, let me check. Upstream ships hand written make file
but I guess it has to do something with we fiddling with Makefile to
build it properly for Debian.

>
> I guess there's just a «-lre» missing somewhere in the build system.

Thanks I will check on this.


> (I found this while trying to build a local baresip package, so thanks
> for trying to get that in Debian. :)

Ah cool. We were working on packaging baresip, some initial work is here
¹. Again custom Makefile is making our life bit hard to build it
properly. 

¹ http://anonscm.debian.org/cgit/pkg-voip/baresip.git

Processed: reopening 817011, closing 817059

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> reopen 817011
Bug #817011 [ruby-domain-name] ruby-domain-name: missing RubyGems integration, 
breaks other  softwares like Vagrant
Bug 817011 is not marked as done; doing nothing.
> close 817059
Bug #817059 [vagrant] vagrant: domain_name gem not found
Marked Bug as done
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
817011: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=817011
817059: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=817059
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#817059: reopening 817011, closing 817059

[Antonio Terceiro]

reopen 817011 
close 817059 
thanks

fixing my confusion from ealier. #817011 is the actual problem, while #817059 is
the duplicate that has been filed on vagrant.

Bug#817006: ack to NMU

[Adam Borowski]

On Tue, Mar 08, 2016 at 04:31:24PM +0900, Benda Xu wrote:
> Basically, my taking to this bug is to ignore it, leaving the users to
> fix the breakage by
> 
>   dpkg-divert --remove /usr/sbin/invoke-rc.d
>   dpkg-divert --remove /usr/sbin/update-rc.d
> 
> manually.  
> 
> 0.20.4-1 lasted only 10days.  Only few users would be affected.

The popcon for openrc is 83, which, assuming that 10% of users run popcon
(a wild-ass guess) means 830 users.  I have no idea what part of this is
unstable, but as openrc in Debian is quite experimental, I guess quite a
bunch of such users are affected.

The breakage is pretty severe -- it does match the description of "critical"
after all.  Every affected user would have to research the fix and apply
it manually.  Thus, I don't think it's a good idea to ignore this bug,
especially that the fix is easy.

> That said, I understand theoretically your NMU is the correctly way to
> go.  So if you intend to do so, consider this email as an ack to NMU
> from the maintainer team.

I'll upload it then.

> One thing to notice is that we are tracking the package at
> 
>   http://anonscm.debian.org/cgit/openrc/openrc.git
> 
> Would you mind if I ask you to prepare a commit to the master
> corresponding to the NMU?

Of course.  I don't have push rights to that repository, so two commits are
attached to this mail (one for the fix, one for changelog).

> BTW, if you are interested in OpenRC, you are welcomed to join the
> maintenance team.

I'm afraid I don't really know inner workings of openrc, I use it on only
one machine (which happens to be my main desktop, but still...).  Everywhere
else I'm on sysv-rc.  This said, keeping openrc viable seems important for
resisting systemd-ization of Debian so I probably should help in _some_ way.

> 1. 0.20.4-1 was uploaded in a hurry to keep itself in testing.  The pts
> system lied and we did not make it.  divert should not have existed in
> OpenRC.

It can be removed in some time, after the affected systems are fixed.


Meow!
-- 
A tit a day keeps the vet away.
>From b4653519c5109967be09976e1fbf431316d07dcf Mon Sep 17 00:00:00 2001
From: Adam Borowski 
Date: Tue, 8 Mar 2016 05:19:25 +0100
Subject: [PATCH 1/2] Remove dangling diverts introduced by 0.20.4-1.

---
 debian/openrc.postinst | 13 +
 1 file changed, 13 insertions(+)

diff --git a/debian/openrc.postinst b/debian/openrc.postinst
index 4d09a68..cd0284e 100644
--- a/debian/openrc.postinst
+++ b/debian/openrc.postinst
@@ -2,6 +2,19 @@
 
 set -e
 
+# Remove diverts made by 0.20.4-1
+if [ "$(dpkg-divert --list /usr/sbin/invoke-rc.d)" = \
+ "diversion of /usr/sbin/invoke-rc.d to /usr/sbin/invoke-rc.d.init-system-helpers by openrc" ]
+	then dpkg-divert --package openrc --remove --rename \
+		--divert /usr/sbin/invoke-rc.d.init-system-helpers /usr/sbin/invoke-rc.d
+fi
+if [ "$(dpkg-divert --list /usr/sbin/update-rc.d)" = \
+ "diversion of /usr/sbin/update-rc.d to /usr/sbin/update-rc.d.init-system-helpers by openrc" ]
+	then dpkg-divert --package openrc --remove --rename \
+		--divert /usr/sbin/update-rc.d.init-system-helpers /usr/sbin/update-rc.d
+fi
+
+
 if [ "${1}" = "configure" ] ; then
 	echo "Add existing services ..."
 
-- 
2.7.0

>From 26d115187fdb7d64cd0569ade30421216d210714 Mon Sep 17 00:00:00 2001
From: Adam Borowski 
Date: Tue, 8 Mar 2016 05:20:10 +0100
Subject: [PATCH 2/2] release 0.20.4-2.1 into sid.

---
 debian/changelog | 7 +++
 1 file changed, 7 insertions(+)

diff --git a/debian/changelog b/debian/changelog
index 15aaae8..8e5269d 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,10 @@
+openrc (0.20.4-2.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Remove diversions to update-rc.d + invoke-rc.d (Closes: #817006).
+
+ -- Adam Borowski   Tue, 08 Mar 2016 05:17:44 +0100
+
 openrc (0.20.4-2) unstable; urgency=high
 
   * Bump standard to 3.9.7.
-- 
2.7.0