Processed: notfound

[Debian Bug Tracking System]

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

> notfound 810881 3.10.6-1ubuntu1~xenial1
Bug #810881 {Done: Andreas Henriksson } [libtotem-plparser18] 
libtotem-plparser18: linker issue, causes grilo-plugins to FTBFS
There is no source info for the package 'libtotem-plparser18' at version 
'3.10.6-1ubuntu1~xenial1' with architecture ''
Unable to make a source version for version '3.10.6-1ubuntu1~xenial1'
No longer marked as found in versions 3.10.6-1ubuntu1~xenial1.
> thanks
Stopping processing here.

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

Bug#816387: qwtplot3d FTBFS on armel and armhf

[Gudjon I. Gudjonsson]

Hi Arto

My only solution to the problem is to exclude the arm architectures and there 
is a new version at mentors 
which I haven't got any sponsor for.

I tried to exclude patch 03_fix_ftbs and compile the package in my armhf chroot 
but without success.

I prefer to keep the arm architecture but I don't have time to fix the code.

Regards
Gudjon

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

[Ralf Treinen]

Package: ruby-amq-client,ruby-amqp
Version: ruby-amq-client/1.0.4-1
Version: ruby-amqp/1.5.1-1
Severity: serious
User: trei...@debian.org
Usertags: edos-file-overwrite

Date: 2016-03-07
Architecture: amd64
Distribution: sid

Hi,

automatic installation tests of packages that share a file and at the
same time do not conflict by their package dependency relationships has
detected the following problem:


Preconfiguring packages ...
Selecting previously unselected package libyaml-0-2:amd64.
(Reading database ... 10939 files and directories currently installed.)
Preparing to unpack .../libyaml-0-2_0.1.6-3_amd64.deb ...
Unpacking libyaml-0-2:amd64 (0.1.6-3) ...
Selecting previously unselected package gcc-5-base:amd64.
Preparing to unpack .../gcc-5-base_5.3.1-10_amd64.deb ...
Unpacking gcc-5-base:amd64 (5.3.1-10) ...
Setting up gcc-5-base:amd64 (5.3.1-10) ...
(Reading database ... 10953 files and directories currently installed.)
Preparing to unpack .../libstdc++6_5.3.1-10_amd64.deb ...
Unpacking libstdc++6:amd64 (5.3.1-10) over (4.8.2-19) ...
Processing triggers for libc-bin (2.21-9) ...
Setting up libstdc++6:amd64 (5.3.1-10) ...
Processing triggers for libc-bin (2.21-9) ...
Selecting previously unselected package libssl1.0.2:amd64.
(Reading database ... 10967 files and directories currently installed.)
Preparing to unpack .../libssl1.0.2_1.0.2g-1_amd64.deb ...
Unpacking libssl1.0.2:amd64 (1.0.2g-1) ...
Selecting previously unselected package openssl.
Preparing to unpack .../openssl_1.0.2g-1_amd64.deb ...
Unpacking openssl (1.0.2g-1) ...
Selecting previously unselected package ca-certificates.
Preparing to unpack .../ca-certificates_20160104_all.deb ...
Unpacking ca-certificates (20160104) ...
Selecting previously unselected package libffi6:amd64.
Preparing to unpack .../libffi6_3.2.1-4_amd64.deb ...
Unpacking libffi6:amd64 (3.2.1-4) ...
Selecting previously unselected package libgmp10:amd64.
Preparing to unpack .../libgmp10_2%3a6.1.0+dfsg-2_amd64.deb ...
Unpacking libgmp10:amd64 (2:6.1.0+dfsg-2) ...
Selecting previously unselected package rubygems-integration.
Preparing to unpack .../rubygems-integration_1.10_all.deb ...
Unpacking rubygems-integration (1.10) ...
Selecting previously unselected package ruby-did-you-mean.
Preparing to unpack .../ruby-did-you-mean_1.0.0-2_all.deb ...
Unpacking ruby-did-you-mean (1.0.0-2) ...
Selecting previously unselected package ruby-minitest.
Preparing to unpack .../ruby-minitest_5.8.4-2_all.deb ...
Unpacking ruby-minitest (5.8.4-2) ...
Selecting previously unselected package ruby-net-telnet.
Preparing to unpack .../ruby-net-telnet_0.1.1-2_all.deb ...
Unpacking ruby-net-telnet (0.1.1-2) ...
Selecting previously unselected package ruby-power-assert.
Preparing to unpack .../ruby-power-assert_0.2.7-1_all.deb ...
Unpacking ruby-power-assert (0.2.7-1) ...
Selecting previously unselected package ruby-test-unit.
Preparing to unpack .../ruby-test-unit_3.1.7-2_all.deb ...
Unpacking ruby-test-unit (3.1.7-2) ...
Selecting previously unselected package libruby2.3:amd64.
Preparing to unpack .../libruby2.3_2.3.0-4_amd64.deb ...
Unpacking libruby2.3:amd64 (2.3.0-4) ...
Selecting previously unselected package ruby2.3.
Preparing to unpack .../ruby2.3_2.3.0-4_amd64.deb ...
Unpacking ruby2.3 (2.3.0-4) ...
Selecting previously unselected package ruby.
Preparing to unpack .../ruby_1%3a2.3.0+1_all.deb ...
Unpacking ruby (1:2.3.0+1) ...
Selecting previously unselected package rake.
Preparing to unpack .../archives/rake_10.5.0-2_all.deb ...
Unpacking rake (10.5.0-2) ...
Selecting previously unselected package ruby-eventmachine.
Preparing to unpack .../ruby-eventmachine_1.0.7-3+b4_amd64.deb ...
Unpacking ruby-eventmachine (1.0.7-3+b4) ...
Selecting previously unselected package ruby-amq-protocol.
Preparing to unpack .../ruby-amq-protocol_1.9.2-2_all.deb ...
Unpacking ruby-amq-protocol (1.9.2-2) ...
Selecting previously unselected package ruby-amq-client.
Preparing to unpack .../ruby-amq-client_1.0.4-1_all.deb ...
Unpacking ruby-amq-client (1.0.4-1) ...
Selecting previously unselected package ruby-amqp.
Preparing to unpack .../ruby-amqp_1.5.1-1_all.deb ...
Unpacking ruby-amqp (1.5.1-1) ...
dpkg: error processing archive 
/var/cache/apt/archives/ruby-amqp_1.5.1-1_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
Processing triggers for libc-bin (2.21-9) ...
Processing triggers for man-db (2.7.5-1) ...
Errors were encountered while processing:
 /var/cache/apt/archives/ruby-amqp_1.5.1-1_all.deb
E: Sub-process /usr/bin/dpkg returned an error code (1)
cow-shell unlink .ilist: No such file or directory


This is a serious bug as it makes installation fail, and violates
sections 7.6.1 and 10.1 of the policy. An optimal solution would
consist in only one of the packages installing that file, and renaming
or removing the file in the other package. Depending on the
circumstances you might also consider Replace 

Bug#817011: ruby-domain-name: missing RubyGems integration, breaks other softwares like Vagrant

[duck]

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

Processed: retitle 815979 to dotclear: New minor releases with security fixes (CVE-2015-5651 CVE-2015-8831 CVE-2015-8832)

[Debian Bug Tracking System]

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

> retitle 815979 dotclear: New minor releases with security fixes 
> (CVE-2015-5651 CVE-2015-8831 CVE-2015-8832)
Bug #815979 [dotclear] dotclear: New minor releases with security fixes
Changed Bug title to 'dotclear: New minor releases with security fixes 
(CVE-2015-5651 CVE-2015-8831 CVE-2015-8832)' from 'dotclear: New minor releases 
with security fixes'
> thanks
Stopping processing here.

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

Bug#817008: unfulfilled dependencies

[Matthias Klose]

Package: src:android-sdk-meta
Version: 24.3.3+1
Severity: serious
Tags: sid stretch

Looking at https://tracker.debian.org/pkg/android-sdk-meta

excuses:
11 days old (needed 5 days)
android-sdk-build-tools/amd64 unsatisfiable Depends: 
android-sdk-build-tools-common (= 24.3.3+1)
android-sdk-platform-tools/amd64 unsatisfiable Depends: 
android-sdk-platform-tools-common (= 24.3.3+1)
android-sdk-build-tools/i386 unsatisfiable Depends: 
android-sdk-build-tools-common (= 24.3.3+1)
android-sdk-platform-tools/i386 unsatisfiable Depends: 
android-sdk-platform-tools-common (= 24.3.3+1)

Invalidated by dependency
Not considered
Depends: android-sdk-meta android-platform-dalvik (not considered)
Depends: android-sdk-meta android-platform-development
Depends: android-sdk-meta android-platform-frameworks-base (not considered)
Depends: android-sdk-meta android-platform-system-core (not considered)

looks like the debian/rules file didn't update

export BUILD_TOOLS_VERSION = 23.0.2
PLATFORM_TOOLS_VERSION = 23.0.0
[...]
override_dh_gencontrol:
dh_gencontrol
dh_gencontrol -pandroid-sdk-platform-tools -- 
-v$(PLATFORM_TOOLS_VERSION)+1
dh_gencontrol -pandroid-sdk-platform-tools-common -- 
-v$(PLATFORM_TOOLS_VERSION)+1

dh_gencontrol -pandroid-sdk-build-tools -- -v$(BUILD_TOOLS_VERSION)+1
dh_gencontrol -pandroid-sdk-build-tools-common -- 
-v$(BUILD_TOOLS_VERSION)+1



On the other hand, I don't see what people are trying to achieve with this 
different version setup.

Bug#816965: marked as done (fonts-mathematica: fails to install if mathematica-fonts 17 is installed)

[Debian Bug Tracking System]

Your message dated Mon, 07 Mar 2016 04:54:23 +
with message-id 
and subject line Bug#816965: fixed in mathematica-fonts 19
has caused the Debian Bug report #816965,
regarding fonts-mathematica: fails to install if mathematica-fonts 17 is 
installed
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.)


-- 
816965: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=816965
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: fonts-mathematica
Version: 18
Severity: serious

When trying to install, I get the following error message:

Preparing to unpack .../fonts-mathematica_18_all.deb ...
The license has already been accepted
Unpacking fonts-mathematica (18) ...
dpkg: error processing archive 
/var/cache/apt/archives/fonts-mathematica_18_all.deb (--unpack):
 trying to overwrite '/usr/share/mathematica-fonts/sha512-ttf', which is also 
in package mathematica-fonts 17

I assume that this is because fonts-mathematica doesn't correctly
declare Provides/Conflicts/Replaces dependencies in the control file.

   Julian

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

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

-- debconf information:
  mathematica-fonts/http_proxy:
* mathematica-fonts/accept_license: true
* mathematica-fonts/license:
--- End Message ---
--- Begin Message ---
Source: mathematica-fonts
Source-Version: 19

We believe that the bug you reported is fixed in the latest version of
mathematica-fonts, 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.
Adam Borowski  (supplier of updated mathematica-fonts 
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 05:12:43 +0100
Source: mathematica-fonts
Binary: fonts-mathematica mathematica-fonts
Architecture: source all
Version: 19
Distribution: unstable
Urgency: medium
Maintainer: Adam Borowski 
Changed-By: Adam Borowski 
Description:
 fonts-mathematica - installer for Mathematica fonts
 mathematica-fonts - transitional dummy package
Closes: 816965
Changes:
 mathematica-fonts (19) unstable; urgency=medium
 .
   * Add missing Replaces: to fix upgrades (closes: #816965).
Checksums-Sha1:
 3086de01acecfe42440f2cad5cde7e9803dec10e 1375 mathematica-fonts_19.dsc
 b7fd176707a7822556fe81e444c8d2c43db6d459 18432 mathematica-fonts_19.tar.xz
 818a7e9dd869ee8f3dc0917cf48aaa03d8b081dd 14670 fonts-mathematica_19_all.deb
 ab18fd3ffde850f1f4c257d1792c68c006036aff 3950 mathematica-fonts_19_all.deb
Checksums-Sha256:
 339d5172c5a27c55483f2531b84877b4eb0add52d3dc201e5c0d94fd4f617bb5 1375 
mathematica-fonts_19.dsc
 d30d7347a61dd6563c8408c7ebf3577341e3d46d3eaf1b21d5d0f908d5e333b4 18432 
mathematica-fonts_19.tar.xz
 edef9bb394b0067638c9510e28aea7748fe9c79d00dd39135374c4adc9e66bc9 14670 
fonts-mathematica_19_all.deb
 57b85de7de0ac33d7af8360a11eccc7fe10e1586e6c20b5e2f002d8ee5120227 3950 
mathematica-fonts_19_all.deb
Files:
 964ec7006ac7261cb7111207c5c19f54 1375 contrib/fonts extra 
mathematica-fonts_19.dsc
 7cbd3a2c2eba0e421930bc170334b8f3 18432 contrib/fonts extra 
mathematica-fonts_19.tar.xz
 561e2b6d3b1402fa2003dc6f4c98de76 14670 contrib/fonts extra 
fonts-mathematica_19_all.deb
 ebd00708935bdbb3b6cdd0cbdc65607c 3950 contrib/fonts extra 
mathematica-fonts_19_all.deb

-BEGIN PGP SIGNATURE-
Version: GnuPG v1

iQEcBAEBCAAGBQJW3QcPAAoJECw7Q2/qxoEBv6oIAK/wCFvSg8t2U2DJ+jv3lri5
Y2Wvw5kFgKHOoZISDoAE7l2EKWKgtbH82ErTWeQRVbNV6Z+YRoafwCKX2zo3VTjm
HDOQPHoGUi9+VOzbewjKZzBqHLfBGfcgIXfBorUDDS4o5cITcAkCdbIFTE3WSj63
QqKxVemmnRpx+4cfIV/vUGPy5zykeK4rrLtXm6AdT4uqWIhy+pqj3LwoXc0HxUVa
Mr6O/HG1N0jHQCSLqFKEa49aevCMllzNFCmG18343zZ0d/xyYSgc/w4115fMb2s3
qHL9axxOz+1BUGwcKShvVgho1wXX9dtzcSdKjAYzlc+ZHyMFKZWmz1AC0wd/Ae8=
=mozO
-END 

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

[Adam Borowski]

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

Bug#816076: wicd-daemon: upgrade reconfigures static ethernet interface, and kills ssh sessions.

[Andrew Vaughan]

On 7 March 2016 at 04:16, Axel Beckert  wrote:
> Hi Andrew,
>
> Andrew Vaughan wrote:
>> My home server is a headless box, administered from a vnc session tunnelled
>> over ssh.  It has no wifi adaptor, just a single ethernet port that is
>> statically configured via /etc/network/interfaces.
>
> So why are you using wicd at all? I don't see why you need wicd in
> such a setup.
>

Wicd was automatically installed because lxde recommends wicd |
network-manager-gnome.

Yes, I could just remove wicd, but that would be working around what I
view as buggy behaviour in wicd-daemon.  If relatively common
meta-packages like lxde are going to pull in services like wicd-daemon
via recommends, then those services must behave sanely if the user
never touches their config.

Network-manager-gnome is also installed because gnome-core recommends
it.  I wonder whether we have races between them?

>> This behaviour is wrong on so many levels.
>>
>> 1. A package upgrade should never bring down an existing in-use interface
>> without asking the user/admin first.
>
> I agree here mostly. It's though only a real issue if the interface
> doesn't come up again with the same IP afterwards.
>

Even if it comes up with the same ip address it is a potential data loss bug.
eg a ssh user has unsaved work in some console application, when the
connection is lost.  There is no easy way to reconnect to the console
application. This may result in data loss.

>> Wicd-daemon should not assume that just because it is installed it
>> owns all the network interfaces.
>
> I disagree here. In Debian, it's common that NetworkManager and
> similar tools manage those interfaces from /etc/network/interfaces
> which are not listed (or maybe also those which are on "auto").

Nowhere in the package description does wicd say that it will attempt
to automatically maintain an active internet connection without any
prior user/admin interaction/config.

In principle, I don't have a problem with it trying to automatically
configure interfaces that have no existing config.  But if I were to
run a virtualisation script that adds a virtual interface, then starts
a virtual machine, is wicd going to see the new interface and try to
configure that, and hence race the the startup of the virtual machine?
 If I plugin a usb wireless adaptor is it going to blindly attempt to
connect to any available wifi network, even if no wifi network has
ever been configured on this device?  If the user were to attempt to
use network-manager gnome to change an existing wifi connection, are
the 2 going to fight over which one gets to configure the
wifi-adapter?

But regardless, if it hasn't been explicitly given permission to
change network configs, then it should respect the existing config of
any interfaces that are up before it starts, or that the user or admin
configures using other tools, including whilst it is running.
Certainly installing/reinstalling/upgrading wicd-daemon shouldn't
touch any network configuration that was made with other tools,
without the admin or user having done something to give wicd
permission to manage network config.

On a related note (the following typed manually from memory, so only
approximate)

ifdown eth0

do something for 30 sec (like edit /etc/network/interfaces )

ifup eth0

error: file in use. can't bring up eth0

ifdown eth0

error: eth0 not up

Not sure whether that was network-manager or wicd that brought eth0
up, but it could be an head-scratching time for an admin who had never
noticed that they were installed.   And it should have better
integration with ifup/down, so that both tools are on the same page as
to what the interface status is and preferably what the interface
status is supposed to be.

>
>> I have been through basically the same problems with network-manager in the
>> past.  Issues like this are why so many people are hostile to that package.
>
> Indeed. That's why I'm using wicd, too. It was though worse with
> NetworkManager back then since usually, the network interface stayed
> down afterwards. That got fixed in the meanwhile, though, IIRC.
>

I remember un-installing network-manager a few times, only for
dependencies to try to pull it back in.

Andrew

Bug#817000: pymvpa2: FTBFS in stretch, build dependencies not in stretch

[Yaroslav Halchenko]

reopen 817000
thanks

And reopening since apparently it was just a tip of the transition away
from swig2.0 so I will close it whenever pymvpa2 is ready to use swig
3.x which hopefully fixes https://github.com/swig/swig/issues/563

-- 
Yaroslav O. Halchenko
Center for Open Neuroscience http://centerforopenneuroscience.org
Dartmouth College, 419 Moore Hall, Hinman Box 6207, Hanover, NH 03755
Phone: +1 (603) 646-9834   Fax: +1 (603) 646-1419
WWW:   http://www.linkedin.com/in/yarik

Processed: Re: Bug#817000: pymvpa2: FTBFS in stretch, build dependencies not in stretch

[Debian Bug Tracking System]

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

> reopen 817000
Bug #817000 {Done: Yaroslav Halchenko } [src:pymvpa2] pymvpa2: 
FTBFS in stretch, build dependencies not in stretch
Bug reopened
Ignoring request to alter fixed versions of bug #817000 to the same values 
previously set
> thanks
Stopping processing here.

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

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

[Debian Bug Tracking System]

n 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-pymvpa2-dummy : Depends: swig2.0 but it is not 
installable or
   swig (<= 3.0.5) 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 upgraded, 0 newly installed, 1 to remove and 0 not upgraded.
After this operation, 0 B of additional disk space will be used.
(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.)
Removing sbuild-build-depends-core-dummy (0.invalid.0) ...
W: No sandbox user '_apt' on the system, can not drop privileges

+--+
| Cleanup  |
+--+

Purging /<>
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...
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
E: Package build dependencies not satisfied; skipping

+--+
| Summary  |
+--+

Build Architecture: amd64
Build-Space: 0
Build-Time: 0
Distribution: stretch
Fail-Stage: install-deps
Host Architecture: amd64
Install-Time: 0
Job: pymvpa2_2.4.1-1
Machine Architecture: amd64
Package: pymvpa2
Package-Time: 0
Source-Version: 2.4.1-1
Space: 0
Status: failed
Version: 2.4.1-1

Finished at 20160306-2256
Build needed 00:00:00, 0k disc space


Thanks.
--- End Message ---
--- Begin Message ---

On Mon, 07 Mar 2016, Santiago Vila wrote:
> The following packages have unmet dependencies:
>  sbuild-build-depends-pymvpa2-dummy : Depends: swig2.0 but it is not 
> installable or
>swig (<= 3.0.5) but it is not 
> going to be installed

well -- swig2.0 was removed from testing but present in sid

my guess is that pymvpa2 pkg would eventually be autoremoved from
testing, and there is nothing for me to do about it neither now nor
later to "close" this issue.

FWIW -- can't use swig 3.x due to
https://github.com/swig/swig/issues/563 which could have been a
proper 'fix'.  But as long as swig2.0 is part of the archive, issue is
not really an issue for me to tackle.  So I will close it for now, feel
free to reopen if you feel it would be of some value (please describe of
which)

-- 
Yaroslav O. Halchenko
Center for Open Neuroscience http://centerforopenneuroscience.org
Dartmouth College, 419 Moore Hall, Hinman Box 6207, Hanover, NH 03755
Phone: +1 (603) 646-9834   Fax: +1 (603) 646-1419
WWW:   http://www.linkedin.com/in/yarik--- End Message ---

Bug#813862: [phpcpd and phploc] Parts of it aren't useless

[Julian Calaby]

Hi David,

On Mon, Mar 7, 2016 at 12:36 PM, David Prévot  wrote:
> Hi Julian,
>
> Thank you for your interest in packaged PHP utilities.
>
> On Mon, Mar 07, 2016 at 12:02:18PM +1100, Julian Calaby wrote:
>
>> I'm sorry if I'm late to the party on this, however I must point out
>> that phploc is a useful tool to analyse PHP codebases.
> […]
>> that phpcpd is a useful tool to analyse PHP codebases and I cannot
>> find any equivalents of phpcpd in the archive after a brief search.
>
> You’re not late: the packages are still in unstable. Thank you for
> pointing that, I’m therefore closing the RC-bugs and we’ll soon take
> care of making the packages ready for the PHP 7.0 transition.

Not the response I was expecting, if I'm honest.

Thanks for keeping the packages, I hope making them ready for PHP 7
isn't too much trouble.

Thanks,

-- 
Julian Calaby

Email: julian.cal...@gmail.com
Profile: http://www.google.com/profiles/julian.calaby/

Bug#813867: marked as done (Useless in Debian)

[Debian Bug Tracking System]

Your message dated Sun, 6 Mar 2016 21:36:14 -0400
with message-id <20160307013614.ga17...@mikado.tilapin.org>
and subject line Re: [phpcpd and phploc] Parts of it aren't useless
has caused the Debian Bug report #813867,
regarding Useless in Debian
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.)


-- 
813867: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=813867
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: phpdox
Version: 0.8.1.1-1
Severity: serious
Control: clone -1 -2 -3 -4 -5 -6 -7
Control: reassign -2 phploc 3.0.0-1
Control: reassign -3 phpcpd 2.0.2-1
Control: reassign -4 php-finder-facade 1.2.0-1
Control: reassign -5 php-fxsl 1.1.1-1
Control: reassign -6 php-fdomdocument 1.6.1-1
Control: reassign -7 phpunit-git 2.0.1-2

[Filled as RC by the maintainer to see this package auto-removed from
 testing if  nobody disagrees. Please, do downgrade this bug with an
 explanation if you disagree.]

This set of packages are still maintained upstream, but the initial
reason why they were introduced in Debian (as (build-)dependencies of
the PHPUnit stack) is not met anymore. PHing in Jessie still recommends
phploc and phpcpd, but the version in Stretch doesn’t.

All in all, these seven packages only (build-)depend in each other
nowadays, so unless someone sees some value in keeping (at least) one of
them in the archive, I’d prefer not to ship them in the next stable
release.

I intend to follow up with RM requests in a few months if nobody objects
(but feel free to beat me to it).

Regards

David


signature.asc
Description: PGP signature
--- End Message ---
--- Begin Message ---
Hi Julian,

Thank you for your interest in packaged PHP utilities.

On Mon, Mar 07, 2016 at 12:02:18PM +1100, Julian Calaby wrote:

> I'm sorry if I'm late to the party on this, however I must point out
> that phploc is a useful tool to analyse PHP codebases.
[…]
> that phpcpd is a useful tool to analyse PHP codebases and I cannot
> find any equivalents of phpcpd in the archive after a brief search.

You’re not late: the packages are still in unstable. Thank you for
pointing that, I’m therefore closing the RC-bugs and we’ll soon take
care of making the packages ready for the PHP 7.0 transition.

Regards

David


signature.asc
Description: PGP signature
--- End Message ---

Bug#813866: marked as done (Useless in Debian)

[Debian Bug Tracking System]

Your message dated Sun, 6 Mar 2016 21:36:14 -0400
with message-id <20160307013614.ga17...@mikado.tilapin.org>
and subject line Re: [phpcpd and phploc] Parts of it aren't useless
has caused the Debian Bug report #813866,
regarding Useless in Debian
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.)


-- 
813866: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=813866
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: phpdox
Version: 0.8.1.1-1
Severity: serious
Control: clone -1 -2 -3 -4 -5 -6 -7
Control: reassign -2 phploc 3.0.0-1
Control: reassign -3 phpcpd 2.0.2-1
Control: reassign -4 php-finder-facade 1.2.0-1
Control: reassign -5 php-fxsl 1.1.1-1
Control: reassign -6 php-fdomdocument 1.6.1-1
Control: reassign -7 phpunit-git 2.0.1-2

[Filled as RC by the maintainer to see this package auto-removed from
 testing if  nobody disagrees. Please, do downgrade this bug with an
 explanation if you disagree.]

This set of packages are still maintained upstream, but the initial
reason why they were introduced in Debian (as (build-)dependencies of
the PHPUnit stack) is not met anymore. PHing in Jessie still recommends
phploc and phpcpd, but the version in Stretch doesn’t.

All in all, these seven packages only (build-)depend in each other
nowadays, so unless someone sees some value in keeping (at least) one of
them in the archive, I’d prefer not to ship them in the next stable
release.

I intend to follow up with RM requests in a few months if nobody objects
(but feel free to beat me to it).

Regards

David


signature.asc
Description: PGP signature
--- End Message ---
--- Begin Message ---
Hi Julian,

Thank you for your interest in packaged PHP utilities.

On Mon, Mar 07, 2016 at 12:02:18PM +1100, Julian Calaby wrote:

> I'm sorry if I'm late to the party on this, however I must point out
> that phploc is a useful tool to analyse PHP codebases.
[…]
> that phpcpd is a useful tool to analyse PHP codebases and I cannot
> find any equivalents of phpcpd in the archive after a brief search.

You’re not late: the packages are still in unstable. Thank you for
pointing that, I’m therefore closing the RC-bugs and we’ll soon take
care of making the packages ready for the PHP 7.0 transition.

Regards

David


signature.asc
Description: PGP signature
--- End Message ---

Bug#813863: marked as done (Useless in Debian)

[Debian Bug Tracking System]

Your message dated Sun, 6 Mar 2016 21:36:14 -0400
with message-id <20160307013614.ga17...@mikado.tilapin.org>
and subject line Re: [phpcpd and phploc] Parts of it aren't useless
has caused the Debian Bug report #813863,
regarding Useless in Debian
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.)


-- 
813863: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=813863
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: phpdox
Version: 0.8.1.1-1
Severity: serious
Control: clone -1 -2 -3 -4 -5 -6 -7
Control: reassign -2 phploc 3.0.0-1
Control: reassign -3 phpcpd 2.0.2-1
Control: reassign -4 php-finder-facade 1.2.0-1
Control: reassign -5 php-fxsl 1.1.1-1
Control: reassign -6 php-fdomdocument 1.6.1-1
Control: reassign -7 phpunit-git 2.0.1-2

[Filled as RC by the maintainer to see this package auto-removed from
 testing if  nobody disagrees. Please, do downgrade this bug with an
 explanation if you disagree.]

This set of packages are still maintained upstream, but the initial
reason why they were introduced in Debian (as (build-)dependencies of
the PHPUnit stack) is not met anymore. PHing in Jessie still recommends
phploc and phpcpd, but the version in Stretch doesn’t.

All in all, these seven packages only (build-)depend in each other
nowadays, so unless someone sees some value in keeping (at least) one of
them in the archive, I’d prefer not to ship them in the next stable
release.

I intend to follow up with RM requests in a few months if nobody objects
(but feel free to beat me to it).

Regards

David


signature.asc
Description: PGP signature
--- End Message ---
--- Begin Message ---
Hi Julian,

Thank you for your interest in packaged PHP utilities.

On Mon, Mar 07, 2016 at 12:02:18PM +1100, Julian Calaby wrote:

> I'm sorry if I'm late to the party on this, however I must point out
> that phploc is a useful tool to analyse PHP codebases.
[…]
> that phpcpd is a useful tool to analyse PHP codebases and I cannot
> find any equivalents of phpcpd in the archive after a brief search.

You’re not late: the packages are still in unstable. Thank you for
pointing that, I’m therefore closing the RC-bugs and we’ll soon take
care of making the packages ready for the PHP 7.0 transition.

Regards

David


signature.asc
Description: PGP signature
--- End Message ---

Bug#813862: marked as done (Useless in Debian)

[Debian Bug Tracking System]

Your message dated Sun, 6 Mar 2016 21:36:14 -0400
with message-id <20160307013614.ga17...@mikado.tilapin.org>
and subject line Re: [phpcpd and phploc] Parts of it aren't useless
has caused the Debian Bug report #813862,
regarding Useless in Debian
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.)


-- 
813862: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=813862
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: phpdox
Version: 0.8.1.1-1
Severity: serious
Control: clone -1 -2 -3 -4 -5 -6 -7
Control: reassign -2 phploc 3.0.0-1
Control: reassign -3 phpcpd 2.0.2-1
Control: reassign -4 php-finder-facade 1.2.0-1
Control: reassign -5 php-fxsl 1.1.1-1
Control: reassign -6 php-fdomdocument 1.6.1-1
Control: reassign -7 phpunit-git 2.0.1-2

[Filled as RC by the maintainer to see this package auto-removed from
 testing if  nobody disagrees. Please, do downgrade this bug with an
 explanation if you disagree.]

This set of packages are still maintained upstream, but the initial
reason why they were introduced in Debian (as (build-)dependencies of
the PHPUnit stack) is not met anymore. PHing in Jessie still recommends
phploc and phpcpd, but the version in Stretch doesn’t.

All in all, these seven packages only (build-)depend in each other
nowadays, so unless someone sees some value in keeping (at least) one of
them in the archive, I’d prefer not to ship them in the next stable
release.

I intend to follow up with RM requests in a few months if nobody objects
(but feel free to beat me to it).

Regards

David


signature.asc
Description: PGP signature
--- End Message ---
--- Begin Message ---
Hi Julian,

Thank you for your interest in packaged PHP utilities.

On Mon, Mar 07, 2016 at 12:02:18PM +1100, Julian Calaby wrote:

> I'm sorry if I'm late to the party on this, however I must point out
> that phploc is a useful tool to analyse PHP codebases.
[…]
> that phpcpd is a useful tool to analyse PHP codebases and I cannot
> find any equivalents of phpcpd in the archive after a brief search.

You’re not late: the packages are still in unstable. Thank you for
pointing that, I’m therefore closing the RC-bugs and we’ll soon take
care of making the packages ready for the PHP 7.0 transition.

Regards

David


signature.asc
Description: PGP signature
--- End Message ---

Bug#813865: marked as done (Useless in Debian)

[Debian Bug Tracking System]

Your message dated Sun, 6 Mar 2016 21:36:14 -0400
with message-id <20160307013614.ga17...@mikado.tilapin.org>
and subject line Re: [phpcpd and phploc] Parts of it aren't useless
has caused the Debian Bug report #813865,
regarding Useless in Debian
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.)


-- 
813865: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=813865
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: phpdox
Version: 0.8.1.1-1
Severity: serious
Control: clone -1 -2 -3 -4 -5 -6 -7
Control: reassign -2 phploc 3.0.0-1
Control: reassign -3 phpcpd 2.0.2-1
Control: reassign -4 php-finder-facade 1.2.0-1
Control: reassign -5 php-fxsl 1.1.1-1
Control: reassign -6 php-fdomdocument 1.6.1-1
Control: reassign -7 phpunit-git 2.0.1-2

[Filled as RC by the maintainer to see this package auto-removed from
 testing if  nobody disagrees. Please, do downgrade this bug with an
 explanation if you disagree.]

This set of packages are still maintained upstream, but the initial
reason why they were introduced in Debian (as (build-)dependencies of
the PHPUnit stack) is not met anymore. PHing in Jessie still recommends
phploc and phpcpd, but the version in Stretch doesn’t.

All in all, these seven packages only (build-)depend in each other
nowadays, so unless someone sees some value in keeping (at least) one of
them in the archive, I’d prefer not to ship them in the next stable
release.

I intend to follow up with RM requests in a few months if nobody objects
(but feel free to beat me to it).

Regards

David


signature.asc
Description: PGP signature
--- End Message ---
--- Begin Message ---
Hi Julian,

Thank you for your interest in packaged PHP utilities.

On Mon, Mar 07, 2016 at 12:02:18PM +1100, Julian Calaby wrote:

> I'm sorry if I'm late to the party on this, however I must point out
> that phploc is a useful tool to analyse PHP codebases.
[…]
> that phpcpd is a useful tool to analyse PHP codebases and I cannot
> find any equivalents of phpcpd in the archive after a brief search.

You’re not late: the packages are still in unstable. Thank you for
pointing that, I’m therefore closing the RC-bugs and we’ll soon take
care of making the packages ready for the PHP 7.0 transition.

Regards

David


signature.asc
Description: PGP signature
--- End Message ---

Bug#813864: marked as done (Useless in Debian)

[Debian Bug Tracking System]

Your message dated Sun, 6 Mar 2016 21:36:14 -0400
with message-id <20160307013614.ga17...@mikado.tilapin.org>
and subject line Re: [phpcpd and phploc] Parts of it aren't useless
has caused the Debian Bug report #813864,
regarding Useless in Debian
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.)


-- 
813864: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=813864
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: phpdox
Version: 0.8.1.1-1
Severity: serious
Control: clone -1 -2 -3 -4 -5 -6 -7
Control: reassign -2 phploc 3.0.0-1
Control: reassign -3 phpcpd 2.0.2-1
Control: reassign -4 php-finder-facade 1.2.0-1
Control: reassign -5 php-fxsl 1.1.1-1
Control: reassign -6 php-fdomdocument 1.6.1-1
Control: reassign -7 phpunit-git 2.0.1-2

[Filled as RC by the maintainer to see this package auto-removed from
 testing if  nobody disagrees. Please, do downgrade this bug with an
 explanation if you disagree.]

This set of packages are still maintained upstream, but the initial
reason why they were introduced in Debian (as (build-)dependencies of
the PHPUnit stack) is not met anymore. PHing in Jessie still recommends
phploc and phpcpd, but the version in Stretch doesn’t.

All in all, these seven packages only (build-)depend in each other
nowadays, so unless someone sees some value in keeping (at least) one of
them in the archive, I’d prefer not to ship them in the next stable
release.

I intend to follow up with RM requests in a few months if nobody objects
(but feel free to beat me to it).

Regards

David


signature.asc
Description: PGP signature
--- End Message ---
--- Begin Message ---
Hi Julian,

Thank you for your interest in packaged PHP utilities.

On Mon, Mar 07, 2016 at 12:02:18PM +1100, Julian Calaby wrote:

> I'm sorry if I'm late to the party on this, however I must point out
> that phploc is a useful tool to analyse PHP codebases.
[…]
> that phpcpd is a useful tool to analyse PHP codebases and I cannot
> find any equivalents of phpcpd in the archive after a brief search.

You’re not late: the packages are still in unstable. Thank you for
pointing that, I’m therefore closing the RC-bugs and we’ll soon take
care of making the packages ready for the PHP 7.0 transition.

Regards

David


signature.asc
Description: PGP signature
--- End Message ---

Bug#813861: marked as done (Useless in Debian)

[Debian Bug Tracking System]

Your message dated Sun, 6 Mar 2016 21:36:14 -0400
with message-id <20160307013614.ga17...@mikado.tilapin.org>
and subject line Re: [phpcpd and phploc] Parts of it aren't useless
has caused the Debian Bug report #813861,
regarding Useless in Debian
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.)


-- 
813861: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=813861
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: phpdox
Version: 0.8.1.1-1
Severity: serious
Control: clone -1 -2 -3 -4 -5 -6 -7
Control: reassign -2 phploc 3.0.0-1
Control: reassign -3 phpcpd 2.0.2-1
Control: reassign -4 php-finder-facade 1.2.0-1
Control: reassign -5 php-fxsl 1.1.1-1
Control: reassign -6 php-fdomdocument 1.6.1-1
Control: reassign -7 phpunit-git 2.0.1-2

[Filled as RC by the maintainer to see this package auto-removed from
 testing if  nobody disagrees. Please, do downgrade this bug with an
 explanation if you disagree.]

This set of packages are still maintained upstream, but the initial
reason why they were introduced in Debian (as (build-)dependencies of
the PHPUnit stack) is not met anymore. PHing in Jessie still recommends
phploc and phpcpd, but the version in Stretch doesn’t.

All in all, these seven packages only (build-)depend in each other
nowadays, so unless someone sees some value in keeping (at least) one of
them in the archive, I’d prefer not to ship them in the next stable
release.

I intend to follow up with RM requests in a few months if nobody objects
(but feel free to beat me to it).

Regards

David


signature.asc
Description: PGP signature
--- End Message ---
--- Begin Message ---
Hi Julian,

Thank you for your interest in packaged PHP utilities.

On Mon, Mar 07, 2016 at 12:02:18PM +1100, Julian Calaby wrote:

> I'm sorry if I'm late to the party on this, however I must point out
> that phploc is a useful tool to analyse PHP codebases.
[…]
> that phpcpd is a useful tool to analyse PHP codebases and I cannot
> find any equivalents of phpcpd in the archive after a brief search.

You’re not late: the packages are still in unstable. Thank you for
pointing that, I’m therefore closing the RC-bugs and we’ll soon take
care of making the packages ready for the PHP 7.0 transition.

Regards

David


signature.asc
Description: PGP signature
--- End Message ---

Bug#817002: subversion: Build-Depends: swig2.0 but it is not installable in stretch

[James McCoy]

On Mon, Mar 07, 2016 at 12:10:44AM +, Santiago Vila wrote:
> 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.

That's because swig2.0 was removed from stretch.  This should be fixed
in the next svn 1.9.x release, but if that doesn't appear to be
forthcoming soon I'll backport the patches.

Cheers,
-- 
James
GPG Key: 4096R/331BA3DB 2011-12-05 James McCoy 

Bug#813862: Parts of it aren't useless

[Julian Calaby]

Hi Maintainer,

I'm sorry if I'm late to the party on this, however I must point out
that phploc is a useful tool to analyse PHP codebases.

While sloccount is also capable of counting lines of code, it's report
isn't as detailed as phploc's and it does not provide all of the same
statistics. (phploc focuses on the complexity of the codebase,
sloccount focuses on estimates of developer manhours and cost)

Thanks,

-- 
Julian Calaby

Email: julian.cal...@gmail.com
Profile: http://www.google.com/profiles/julian.calaby/

Bug#813863: Parts of it aren't useless

[Julian Calaby]

Hi Maintainer,

I'm sorry if I'm late to the party on this, however I must point out
that phpcpd is a useful tool to analyse PHP codebases and I cannot
find any equivalents of phpcpd in the archive after a brief search.

Thanks,

-- 
Julian Calaby

Email: julian.cal...@gmail.com
Profile: http://www.google.com/profiles/julian.calaby/

Bug#816997: gmsh: FTBFS in stretch, build dependencies not in stretch

[Santiago Vila]

Package: src:gmsh
Version: 2.11.0+dfsg1-2
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-7fGrLz/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 ... 14575 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: chrpath, cmake, debhelper (>= 9), default-jdk, 
freeglut3-dev, gfortran, javahelper, libann-dev, libblas-dev, libcgns-dev (>= 
3.1.3.2), libfltk1.3-dev, libgl1-mesa-dev, libgl2ps-dev, libglu1-mesa-dev, 
libjpeg-dev, liblapack-dev, libmed-dev, libmedc-dev, liboce-modeling-dev, 
liboce-ocaf-dev, liboce-visualization-dev, libpng-dev, libtet1.5-dev, 
mpi-default-bin, mpi-default-dev, oce-draw, python-dev, swig2.0, texinfo, 
texlive, zlib1g-dev
Filtered Build-Depends: chrpath, cmake, debhelper (>= 9), default-jdk, 
freeglut3-dev, gfortran, javahelper, libann-dev, libblas-dev, libcgns-dev (>= 
3.1.3.2), libfltk1.3-dev, libgl1-mesa-dev, libgl2ps-dev, libglu1-mesa-dev, 
libjpeg-dev, liblapack-dev, libmed-dev, libmedc-dev, liboce-modeling-dev, 
liboce-ocaf-dev, liboce-visualization-dev, libpng-dev, libtet1.5-dev, 
mpi-default-bin, mpi-default-dev, oce-draw, python-dev, swig2.0, texinfo, 
texlive, zlib1g-dev
dpkg-deb: building package 'sbuild-build-depends-gmsh-dummy' in 
'/<>/resolver-y1NavE/apt_archive/sbuild-build-depends-gmsh-dummy.deb'.
OK
Get:1 file:/<>/resolver-y1NavE/apt_archive ./ InRelease
Ign:1 file:/<>/resolver-y1NavE/apt_archive ./ InRelease
Get:2 file:/<>/resolver-y1NavE/apt_archive ./ Release [2119 B]
Get:2 file:/<>/resolver-y1NavE/apt_archive ./ Release [2119 B]
Get:3 file:/<>/resolver-y1NavE/apt_archive ./ Release.gpg [299 B]
Get:3 file:/<>/resolver-y1NavE/apt_archive ./ Release.gpg [299 B]
Get:4 file:/<>/resolver-y1NavE/apt_archive ./ Sources [394 B]
Get:5 file:/<>/resolver-y1NavE/apt_archive ./ Packages [719 B]
Reading package lists...
W: No sandbox user '_apt' on the system, can not drop privileges
Reading package lists...

+--+
| Install gmsh 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-gmsh-dummy : Depends: swig2.0 but it is not installable
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 upgraded, 0 newly installed, 1 to remove and 0 not upgraded.
After this operation, 0 B of additional disk space will be used.
(Reading database ... 
(Reading database ... 5%
(Reading database ... 10%
(Reading database ... 15%

Bug#816994: aegis: FTBFS in stretch, build dependencies not in stretch

[Santiago Vila]

0%
(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.)
Removing sbuild-build-depends-core-dummy (0.invalid.0) ...
W: No sandbox user '_apt' on the system, can not drop privileges

+--+
| Cleanup  |
+--+

Purging /<>
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...
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
E: Package build dependencies not satisfied; skipping

+--+
| Summary  |
+--+

Build Architecture: amd64
Build-Space: 0
Build-Time: 0
Distribution: stretch
Fail-Stage: install-deps
Host Architecture: amd64
Install-Time: 0
Job: aegis_4.24.3-3
Machine Architecture: amd64
Package: aegis
Package-Time: 0
Source-Version: 4.24.3-3
Space: 0
Status: failed
Version: 4.24.3-3

Finished at 20160306-2256
Build needed 00:00:00, 0k disc space


Thanks.

Bug#817000: pymvpa2: FTBFS in stretch, build dependencies not in stretch

[Santiago Vila]

ase ... 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.)
Removing sbuild-build-depends-core-dummy (0.invalid.0) ...
W: No sandbox user '_apt' on the system, can not drop privileges

+--+
| Cleanup  |
+--+

Purging /<>
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...
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
E: Package build dependencies not satisfied; skipping

+--+
| Summary  |
+--+

Build Architecture: amd64
Build-Space: 0
Build-Time: 0
Distribution: stretch
Fail-Stage: install-deps
Host Architecture: amd64
Install-Time: 0
Job: pymvpa2_2.4.1-1
Machine Architecture: amd64
Package: pymvpa2
Package-Time: 0
Source-Version: 2.4.1-1
Space: 0
Status: failed
Version: 2.4.1-1

Finished at 20160306-2256
Build needed 00:00:00, 0k disc space


Thanks.

Bug#817002: subversion: Build-Depends: swig2.0 but it is not installable in stretch

[Santiago Vila]

raded.
After this operation, 0 B of additional disk space will be used.
(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.)
Removing sbuild-build-depends-core-dummy (0.invalid.0) ...
W: No sandbox user '_apt' on the system, can not drop privileges

+--+
| Cleanup  |
+--+

Purging /<>
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...
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
E: Package build dependencies not satisfied; skipping

+--+
| Summary  |
+--+

Build Architecture: amd64
Build-Space: 0
Build-Time: 0
Distribution: stretch
Fail-Stage: install-deps
Host Architecture: amd64
Install-Time: 0
Job: subversion_1.9.3-2
Machine Architecture: amd64
Package: subversion
Package-Time: 0
Source-Version: 1.9.3-2
Space: 0
Status: failed
Version: 1.9.3-2

Finished at 20160306-2306
Build needed 00:00:00, 0k disc space


Thanks.

Bug#816995: fam: FTBFS in stretch with new perl: Unescaped left brace in regex is deprecated

[Santiago Vila]

Package: src:fam
Version: 2.7.0-17.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 related to the new perl, so I infer that this
would FTBFS in the general case too, 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-nfKF48/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 ... 14535 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), cdbs (>= 0.4.0.1), libtool (>= 1.5-2), 
automake1.11, autoconf
Filtered Build-Depends: debhelper (>= 7), cdbs (>= 0.4.0.1), libtool (>= 
1.5-2), automake1.11, autoconf
dpkg-deb: building package 'sbuild-build-depends-fam-dummy' in 
'/<>/resolver-QFoolj/apt_archive/sbuild-build-depends-fam-dummy.deb'.
OK
Get:1 file:/<>/resolver-QFoolj/apt_archive ./ InRelease
Ign:1 file:/<>/resolver-QFoolj/apt_archive ./ InRelease
Get:2 file:/<>/resolver-QFoolj/apt_archive ./ Release [2119 B]
Get:2 file:/<>/resolver-QFoolj/apt_archive ./ Release [2119 B]
Get:3 file:/<>/resolver-QFoolj/apt_archive ./ Release.gpg [299 B]
Get:3 file:/<>/resolver-QFoolj/apt_archive ./ Release.gpg [299 B]
Get:4 file:/<>/resolver-QFoolj/apt_archive ./ Sources [245 B]
Get:5 file:/<>/resolver-QFoolj/apt_archive ./ Packages [558 B]
Reading package lists...
W: No sandbox user '_apt' on the system, can not drop privileges
Reading package lists...

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

Installing build dependencies
Reading package lists...
Building dependency tree...
Reading state information...
The following additional packages will be installed:
  autoconf automake1.11 cdbs libsigsegv2 libtool m4
Suggested packages:
  autoconf-archive gnu-standards autoconf-doc devscripts libtool-doc gfortran
  | fortran95-compiler gcj-jdk
Recommended packages:
  libltdl-dev
The following NEW packages will be installed:
  autoconf automake1.11 cdbs libsigsegv2 libtool m4
  sbuild-build-depends-fam-dummy
0 upgraded, 7 newly installed, 0 to remove and 0 not upgraded.
Need to get 613 kB/1436 kB of archives.
After this operation, 5118 kB of additional disk space will be used.
Get:1 file:/<>/resolver-QFoolj/apt_archive ./ 
sbuild-build-depends-fam-dummy 0.invalid.0 [802 B]
Get:2 http://httpredir.debian.org/debian stretch/main amd64 automake1.11 all 
1:1.11.6-3 [537 kB]
Get:3 http://httpredir.debian.org/debian stretch/main amd64 cdbs all 0.4.130 
[76.4 kB]
debconf: delaying package configuration, since apt-utils is not installed
Fetched 613 kB in 0s (6128 kB/s)
Selecting previously unselected package libsigsegv2:amd64.
(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 ... 14535 files and directories currently installed.)
Preparing to unpack .../libsigsegv2_2.10-4+b1_amd64.deb ...
Unpacking libsigsegv2:amd64 (2.10-4+b1) ...
Selecting previously unselected package m4.
Preparing to unpack 

Bug#816998: jpathwatch: FTBFS in stretch, build dependencies not in stretch

[Santiago Vila]

depends-core-dummy (0.invalid.0) ...
W: No sandbox user '_apt' on the system, can not drop privileges

+--+
| Cleanup  |
+--+

Purging /<>
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...
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
E: Package build dependencies not satisfied; skipping

+--+
| Summary  |
+--+

Build Architecture: amd64
Build-Space: 0
Build-Time: 0
Distribution: stretch
Fail-Stage: install-deps
Host Architecture: amd64
Install-Time: 0
Job: jpathwatch_0.95-4
Machine Architecture: amd64
Package: jpathwatch
Package-Time: 0
Source-Version: 0.95-4
Space: 0
Status: failed
Version: 0.95-4

Finished at 20160306-2309
Build needed 00:00:00, 0k disc space


Thanks.

Bug#816999: presage: Build-Depends: swig2.0 (>= 2.0.4) but it is not installable in stretch

[Santiago Vila]

.. 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 ... 14574 files and directories currently installed.)
Removing sbuild-build-depends-core-dummy (0.invalid.0) ...
W: No sandbox user '_apt' on the system, can not drop privileges

+--+
| Cleanup  |
+--+

Purging /<>
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...
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
E: Package build dependencies not satisfied; skipping

+--+
| Summary  |
+--+

Build Architecture: amd64
Build-Space: 0
Build-Time: 0
Distribution: stretch
Fail-Stage: install-deps
Host Architecture: amd64
Install-Time: 0
Job: presage_0.9.1-1.1
Machine Architecture: amd64
Package: presage
Package-Time: 0
Source-Version: 0.9.1-1.1
Space: 0
Status: failed
Version: 0.9.1-1.1

Finished at 20160306-2256
Build needed 00:00:00, 0k disc space


Thanks.

Bug#816996: gmerlin: FTBFS in stretch with new perl: Unescaped left brace in regex is deprecated

[Santiago Vila]

Package: src:gmerlin
Version: 1.2.0~dfsg+1-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 related to the new perl, so I infer that this
would FTBFS in the general case too, 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-FlAtzo/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: cdbs, autotools-dev, gnulib, debhelper (>= 9~), 
dh-buildinfo, libtool, automake1.11, autoconf, devscripts, doxygen, fontconfig, 
libasound2-dev, libcddb2-dev, libcdio-paranoia-dev, libesd0-dev, libexif-dev, 
libfreetype6-dev, libgavl-dev (>= 1.4.0), libglu1-mesa-dev, libgtk2.0-dev, 
libjack-dev, libjpeg-dev, libpulse-dev, libquicktime-dev, libtiff-dev, 
libv4l-dev, libvisual-0.4-dev, libxml2-dev, libxv-dev, texinfo
Filtered Build-Depends: cdbs, autotools-dev, gnulib, debhelper (>= 9~), 
dh-buildinfo, libtool, automake1.11, autoconf, devscripts, doxygen, fontconfig, 
libasound2-dev, libcddb2-dev, libcdio-paranoia-dev, libesd0-dev, libexif-dev, 
libfreetype6-dev, libgavl-dev (>= 1.4.0), libglu1-mesa-dev, libgtk2.0-dev, 
libjack-dev, libjpeg-dev, libpulse-dev, libquicktime-dev, libtiff-dev, 
libv4l-dev, libvisual-0.4-dev, libxml2-dev, libxv-dev, texinfo
dpkg-deb: building package 'sbuild-build-depends-gmerlin-dummy' in 
'/<>/resolver-wUAk5p/apt_archive/sbuild-build-depends-gmerlin-dummy.deb'.
OK
Get:1 file:/<>/resolver-wUAk5p/apt_archive ./ InRelease
Ign:1 file:/<>/resolver-wUAk5p/apt_archive ./ InRelease
Get:2 file:/<>/resolver-wUAk5p/apt_archive ./ Release [2119 B]
Get:2 file:/<>/resolver-wUAk5p/apt_archive ./ Release [2119 B]
Get:3 file:/<>/resolver-wUAk5p/apt_archive ./ Release.gpg [299 B]
Get:3 file:/<>/resolver-wUAk5p/apt_archive ./ Release.gpg [299 B]
Get:4 file:/<>/resolver-wUAk5p/apt_archive ./ Sources [402 B]
Get:5 file:/<>/resolver-wUAk5p/apt_archive ./ Packages [707 B]
Reading package lists...
W: No sandbox user '_apt' on the system, can not drop privileges
Reading package lists...

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

Installing build dependencies
Reading package lists...
Building dependency tree...
Reading state information...
The following additional packages will be installed:
  autoconf automake automake1.11 autopoint bison cdbs devscripts dh-buildinfo
  dh-python doxygen esound-common fontconfig fontconfig-config
  fonts-dejavu-core gir1.2-atk-1.0 gir1.2-freedesktop gir1.2-gdkpixbuf-2.0
  gir1.2-glib-2.0 gir1.2-gtk-2.0 gir1.2-pango-1.0 gnulib gperf icu-devtools
  libasound2 libasound2-data libasound2-dev libasyncns0 libatk1.0-0
  libatk1.0-data libatk1.0-dev libaudiofile-dev libaudiofile1 libavahi-client3
  libavahi-common-data libavahi-common3 libavcodec-ffmpeg56 libavutil-ffmpeg54
  libbison-dev libbsd0 libcairo-gobject2 libcairo-script-interpreter2
  libcairo2 libcairo2-dev libcddb2 libcddb2-dev libcdio-cdda-dev libcdio-cdda1
  libcdio-dev libcdio-paranoia-dev libcdio-paranoia1 libcdio13 libclang1-3.6
  libcrystalhd3 libcups2 libdatrie1 libdbus-1-3 libdrm-amdgpu1 libdrm-dev
  libdrm-intel1 libdrm-nouveau2 libdrm-radeon1 libdrm2 libdv4 libedit2 libelf1
  libesd0 libesd0-dev libexif-dev libexif12 libexpat1 libexpat1-dev libfaad2
  libflac8 libfontconfig1 libfontconfig1-dev libfreetype6 libfreetype6-dev
  

Bug#817001: rdkit: Build-Depends: python-pandas but it is not installable in stretch

[Santiago Vila]

Package: src:rdkit
Version: 201503-3
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/768 B of archives.
After this operation, 0 B of additional disk space will be used.
Get:1 file:/<>/resolver-Iswa4G/apt_archive ./ 
sbuild-build-depends-core-dummy 0.invalid.0 [768 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 ... 14527 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: bison, cmake, debhelper (>> 9), dh-python, doxygen, flex, 
libboost-dev, libboost-python-dev, libboost-regex-dev, libboost-system-dev, 
libboost-thread-dev, libsqlite3-dev, python-dev, python-epydoc, python-imaging, 
python-numpy, python-pandas, python-sphinx, texlive-fonts-recommended, 
texlive-latex-base, texlive-latex-extra, texlive-latex-recommended
Filtered Build-Depends: bison, cmake, debhelper (>> 9), dh-python, doxygen, 
flex, libboost-dev, libboost-python-dev, libboost-regex-dev, 
libboost-system-dev, libboost-thread-dev, libsqlite3-dev, python-dev, 
python-epydoc, python-imaging, python-numpy, python-pandas, python-sphinx, 
texlive-fonts-recommended, texlive-latex-base, texlive-latex-extra, 
texlive-latex-recommended
dpkg-deb: building package 'sbuild-build-depends-rdkit-dummy' in 
'/<>/resolver-aImjHh/apt_archive/sbuild-build-depends-rdkit-dummy.deb'.
OK
Get:1 file:/<>/resolver-aImjHh/apt_archive ./ InRelease
Ign:1 file:/<>/resolver-aImjHh/apt_archive ./ InRelease
Get:2 file:/<>/resolver-aImjHh/apt_archive ./ Release [2119 B]
Get:2 file:/<>/resolver-aImjHh/apt_archive ./ Release [2119 B]
Get:3 file:/<>/resolver-aImjHh/apt_archive ./ Release.gpg [299 B]
Get:3 file:/<>/resolver-aImjHh/apt_archive ./ Release.gpg [299 B]
Get:4 file:/<>/resolver-aImjHh/apt_archive ./ Sources [336 B]
Get:5 file:/<>/resolver-aImjHh/apt_archive ./ Packages [663 B]
Reading package lists...
W: No sandbox user '_apt' on the system, can not drop privileges
Reading package lists...

+--+
| Install rdkit 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-rdkit-dummy : Depends: python-pandas but it is not 
installable
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 upgraded, 0 newly installed, 1 to remove and 0 not upgraded.
After this operation, 0 B of additional disk space will be used.
(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 

Bug#816210: marked as done (libldb1: Upgrade removes xine-ui, kde-runtime + 8 more (Sid Unstable))

[Debian Bug Tracking System]

Your message dated Sun, 06 Mar 2016 23:59:41 +
with message-id 
and subject line Bug#816210: fixed in samba 2:4.3.5+dfsg-2
has caused the Debian Bug report #816210,
regarding libldb1: Upgrade removes xine-ui, kde-runtime + 8 more (Sid Unstable)
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.)


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

Dear Maintainer,

First and as always, thank you to EVERYONE for your time and dedication that 
makes Debian possible!

The bug I've encountered today involves the latest upgrading of package libldb1 
via apt-get on Sid Unstable. This is the advisement received when attempting 
that upgrade:

+++ BEGIN APT-GET'S LIBLDB1 UPGRADE ADVISEMENT +++

The following packages will be REMOVED:
  kde-runtime kio-extras libsmbclient libxine2 libxine2-misc-plugins
  libxine2-plugins palapeli samba-libs vlc-plugin-samba xine-ui
The following packages will be upgraded:
  libldb1
1 upgraded, 0 newly installed, 10 to remove and 0 not upgraded.
Need to get 111 kB of archives.
After this operation, 40.3 MB disk space will be freed.

+++ END APT-GET'S LIBLDB1 UPGRADE ADVISEMENT +++

Once in a while I get lucky where installing/upgrading all other packages first 
or in a different order remedies the situation. Unfortunately that did not help 
today.

If you look at this bug report and agree with its assignment, cool. If you 
think it's something that usually should not make it to bug report status, I'll 
be happy to receive that feedback as part of the growing process in learning to 
help you all out.

The reason I say that is because I always end up cringing while determining the 
severity status of these things. I'm not well enough versed in the whole 
dependency thing to know whether xine-ui, kde-runtime, and the others being 
removed by libldb1 is an expected behavior that is very naturally remedied 
regularly in Sid Unstable. I ultimately choose that severity because, for 
example today, it doesn't appear to be a natural, expected behavior for a media 
player and game (e.g. palapeli) to be autoremoved during the *seemingly* 
unrelated update of a package being addressed by itself.

That's all I have for now. Thank you again so much for your work!

PS As an aside, I just seconds ago installed apt-rdepends with hopes that it 
proves to be a useful tool for understanding situations like this in the Future.

Cindy Sue :)
Talking Rock, GA USA


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

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

Versions of packages libldb1 depends on:
ii  libc6  2.21-9
ii  libldap-2.4-2  2.4.42+dfsg-2+b2
ii  libtalloc2 2.1.5-1
ii  libtdb11.3.8-1
ii  libtevent0 0.9.28-1

libldb1 recommends no packages.

libldb1 suggests no packages.

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: samba
Source-Version: 2:4.3.5+dfsg-2

We believe that the bug you reported is fixed in the latest version of
samba, 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.
Jelmer Vernooij  (supplier of updated samba 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: Sun, 06 Mar 2016 22:51:53 +
Source: samba
Binary: samba samba-libs samba-common samba-common-bin smbclient 
samba-testsuite registry-tools libparse-pidl-perl samba-dev python-samba 
samba-dsdb-modules samba-vfs-modules libsmbclient libsmbclient-dev winbind 
libpam-winbind libnss-winbind samba-dbg libwbclient0 libwbclient-dev ctdb
Architecture: source amd64 all
Version: 2:4.3.5+dfsg-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Samba Maintainers 

Bug#812087: [pcscd]

[Ludovic Rousseau]

On Sun, 6 Mar 2016 23:10:07 +0100 Philippe Teuwen  wrote:

Mmm activating libudev debug didn't bring much I think.

I attached one log with LIBUSB_DEBUG=99 and one with recompiled pcscd
with udev debug support.
For both I just ran pcscd with the yubikey plugged in then plugged a USB
hub that triggered the CPU to 100%

libccid1.4.22-1
libusb-1.0-0   2:1.0.20-1
udev   228-6

I'll see if I can get more from gdb...

Cheers
Phil


Thanks Philippe for the libudev trace.

hotplug_libudev.c contains an infinite for() loop.
But for each loop execution a line is logged:
0022 hotplug_libudev.c:619:HPEstablishUSBNotifications()

Since you do not get a infinite of these logs I guess the infinite loop occurs 
inside a function called in the for() loop.

I have an idea. Can you test with the proposed patch:
--- /var/folders/sg/t7kts8_n6j13n11r6_tgr36rgn/T//3ql5ya_hotplug_libudev.c  
2016-03-07 00:38:32.0 +0100
+++ src/hotplug_libudev.c   2016-03-07 00:38:08.0 +0100
@@ -621,7 +621,7 @@ static void HPEstablishUSBNotifications(
pthread_setcancelstate(PTHREAD_CANCEL_ENABLE, NULL);
 
/* wait for a udev event */

-   r = TEMP_FAILURE_RETRY(poll(, 1, -1));
+   r = poll(, 1, -1);
if (r < 0)
{
Log2(PCSC_LOG_ERROR, "select(): %s", strerror(errno));

--
Dr. Ludovic Rousseau

Bug#815451: initramfs-tools: Fails to install without busybox (Depends vs. Recommends)

[Olaf Meeuwissen]

Hi Ben,

Ben Hutchings writes:

> On Fri, 2016-03-04 at 09:03 +0900, Olaf Meeuwissen wrote:
> [...]
>> The initramfs.conf file says:
>> 
>> > 
>> > # BUSYBOX: [ y | n ]
>> > #
>> > # Use busybox if available
>> > #
>> > 
>> > BUSYBOX=y
>> Something does not make sense unless there is a typo, s/not/now/, in
>> Ben's initial comment.
>> 
>> I use the default initramfs.conf since my initial install.I upgrade to
>> initramfs-tools 0.123 and stuff breaks.You definitely have a non-clean
>> upgrade path here.
>
> On the contrary, the default initramfs.conf has changed BUSYBOX=y to
> BUSYBOX=auto. You chose not to accept that.

I don't recall doing so but that might have happened.  I don't have any
*.dpkg-new lying around anymore.

>> I'll fix my initramfs.conf manually but default setups that suddenly can
>> no longer create initramfs images is scary at best.
>> 
>> Please make the postinst modify initramfs.conf to disable busybox unless
>> available.While at it, also update the comment.
> [...]
>
> I did that too.

I grabbed a copy of the latest source and now use the initramfs.conf
that is shipped without any trouble.

Sorry for the noise,
-- 
Olaf Meeuwissen, LPIC-2   FLOSS Engineer -- EPSON AVASYS CORPORATION
   Free Software Foundation Associate Member since 2004-01-27
Support Free Software  https://my.fsf.org/donate
Join the Free Software Foundationhttps://my.fsf.org/join

Processed: tagging 816975

[Debian Bug Tracking System]

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

> tags 816975 + sid stretch
Bug #816975 [src:qutecom] qutecom: should this package be removed?
Added tag(s) stretch and sid.
> thanks
Stopping processing here.

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

Bug#816975: qutecom: should this package be removed?

[Sebastian Ramacher]

Source: qutecom
Version: 2.2.1+dfsg1-5.2
Severity: serious

quotecom seems to be dead upstream (qutecom.org is no longer reachable, last
upstream release was four years ago) and has many bugs that will become RC
soonish: #803856 (ffmpeg transition), #812163 (GCC 6) and #816812 (Qt4 WebKit
removal).

So should quotecom be removed from unstable?

Cheers
-- 
Sebastian Ramacher


signature.asc
Description: PGP signature

Bug#812087: [pcscd]

[Philippe Teuwen]

Here are some backtraces


Normal CPU usage:

Thread 5 (Thread 0x7f6365c82700 (LWP 30482)):
#0  0x7f6366196b6d in poll () at ../sysdeps/unix/syscall-template.S:81
#1  0x7f6365c92b3c in ?? () from /lib/x86_64-linux-gnu/libusb-1.0.so.0
#2  0x7f6366462284 in start_thread (arg=0x7f6365c82700) at
pthread_create.c:333
#3  0x7f636619fa4d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 4 (Thread 0x7f6365481700 (LWP 30483)):
#0  0x7f6366196b6d in poll () at ../sysdeps/unix/syscall-template.S:81
#1  0x7f6365c92b3c in ?? () from /lib/x86_64-linux-gnu/libusb-1.0.so.0
#2  0x7f6366462284 in start_thread (arg=0x7f6365481700) at
pthread_create.c:333
#3  0x7f636619fa4d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 3 (Thread 0x7f6364c80700 (LWP 30484)):
#0  0x7f6366196b6d in poll () at ../sysdeps/unix/syscall-template.S:81
#1  0x7f6365c8c0b5 in ?? () from /lib/x86_64-linux-gnu/libusb-1.0.so.0
#2  0x7f6365c8d043 in libusb_handle_events_timeout_completed () from
/lib/x86_64-linux-gnu/libusb-1.0.so.0
#3  0x7f6365c8d12f in libusb_handle_events () from
/lib/x86_64-linux-gnu/libusb-1.0.so.0
#4  0x7f6365ea9004 in ?? () from
/usr/lib/pcsc/drivers/ifd-ccid.bundle/Contents/Linux/libccid.so
#5  0x7f6365ea3853 in ?? () from
/usr/lib/pcsc/drivers/ifd-ccid.bundle/Contents/Linux/libccid.so
#6  0x004061a3 in EHStatusHandlerThread (rContext=0x177a010) at
eventhandler.c:464
#7  0x7f6366462284 in start_thread (arg=0x7f6364c80700) at
pthread_create.c:333
#8  0x7f636619fa4d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 2 (Thread 0x7f635700 (LWP 30485)):
#0  0x7f6366196b6d in poll () at ../sysdeps/unix/syscall-template.S:81
#1  0x0040e61a in HPEstablishUSBNotifications (arg=0x17a4a30) at
hotplug_libudev.c:624
#2  0x7f6366462284 in start_thread (arg=0x7f635700) at
pthread_create.c:333
#3  0x7f636619fa4d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 1 (Thread 0x7f6366c51740 (LWP 30481)):
#0  0x7f6366198963 in select () at ../sysdeps/unix/syscall-template.S:81
#1  0x00411179 in ProcessEventsServer
(pdwClientID=pdwClientID@entry=0x7ffea88638a0)
at winscard_msg_srv.c:223
#2  0x004035c1 in SVCServiceRunLoop () at pcscdaemon.c:128
#3  main (argc=, argv=) at pcscdaemon.c:685


100% CPU:



Thread 5 (Thread 0x7f1969ee2700 (LWP 30237)):
#0  0x7f196a6cabdd in recvmsg () at
../sysdeps/unix/syscall-template.S:81
#1  0x7f196aebe6ec in udev_monitor_receive_device () from
/lib/x86_64-linux-gnu/libudev.so.1
#2  0x7f1969ef2bcb in ?? () from /lib/x86_64-linux-gnu/libusb-1.0.so.0
#3  0x7f196a6c2284 in start_thread (arg=0x7f1969ee2700) at
pthread_create.c:333
#4  0x7f196a3ffa4d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 4 (Thread 0x7f19696e1700 (LWP 30238)):
#0  0x7f196a3f6b6d in poll () at ../sysdeps/unix/syscall-template.S:81
#1  0x7f1969ef2b3c in ?? () from /lib/x86_64-linux-gnu/libusb-1.0.so.0
#2  0x7f196a6c2284 in start_thread (arg=0x7f19696e1700) at
pthread_create.c:333
#3  0x7f196a3ffa4d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 3 (Thread 0x7f1968ee0700 (LWP 30239)):
#0  0x7f196a3f6b6d in poll () at ../sysdeps/unix/syscall-template.S:81
#1  0x7f1969eec0b5 in ?? () from /lib/x86_64-linux-gnu/libusb-1.0.so.0
#2  0x7f1969eed043 in libusb_handle_events_timeout_completed () from
/lib/x86_64-linux-gnu/libusb-1.0.so.0
#3  0x7f1969eed12f in libusb_handle_events () from
/lib/x86_64-linux-gnu/libusb-1.0.so.0
#4  0x7f196a109004 in ?? () from
/usr/lib/pcsc/drivers/ifd-ccid.bundle/Contents/Linux/libccid.so
#5  0x7f196a103853 in ?? () from
/usr/lib/pcsc/drivers/ifd-ccid.bundle/Contents/Linux/libccid.so
#6  0x004061a3 in EHStatusHandlerThread (rContext=0xd49010) at
eventhandler.c:464
#7  0x7f196a6c2284 in start_thread (arg=0x7f1968ee0700) at
pthread_create.c:333
#8  0x7f196a3ffa4d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 2 (Thread 0x7f1963fff700 (LWP 30240)):
#0  0x7f196a3f6b6d in poll () at ../sysdeps/unix/syscall-template.S:81
#1  0x0040e61a in HPEstablishUSBNotifications (arg=0xd73a30) at
hotplug_libudev.c:624
#2  0x7f196a6c2284 in start_thread (arg=0x7f1963fff700) at
pthread_create.c:333
#3  0x7f196a3ffa4d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 1 (Thread 0x7f196aeb1740 (LWP 30236)):
#0  0x7f196a3f8963 in select () at ../sysdeps/unix/syscall-template.S:81
#1  0x00411179 in ProcessEventsServer
(pdwClientID=pdwClientID@entry=0x7ffc0e4e4240) at winscard_msg_srv.c:223
#2  0x004035c1 in SVCServiceRunLoop () at pcscdaemon.c:128
#3  main (argc=, argv=) at pcscdaemon.c:685



So the difference is in this thread and udev indeed:


#0 0x7f196a6cabdd in recvmsg () at ../sysdeps/unix/syscall-template.S:81
#1 0x7f196aebe6ec in 

Bug#812087: [pcscd]

[Philippe Teuwen]

Mmm activating libudev debug didn't bring much I think.

I attached one log with LIBUSB_DEBUG=99 and one with recompiled pcscd
with udev debug support.
For both I just ran pcscd with the yubikey plugged in then plugged a USB
hub that triggered the CPU to 100%

libccid1.4.22-1
libusb-1.0-0   2:1.0.20-1
udev   228-6

I'll see if I can get more from gdb...

Cheers
Phil
 pcscdaemon.c:261:main() pcscd set to foreground with debug send to stdout
0024 debuglog.c:310:DebugLogSetCategory() Debug options: APDU
0076 configfile.l:281:DBGetReaderListDir() Parsing conf directory: /etc/reader.conf.d
0027 configfile.l:353:DBGetReaderList() Parsing conf file: /etc/reader.conf.d/libccidtwin
0069 configfile.l:315:DBGetReaderListDir() Skipping non regular file: .
0005 configfile.l:315:DBGetReaderListDir() Skipping non regular file: ..
0013 pcscdaemon.c:567:main() pcsc-lite 1.8.15 daemon ready.
4233 hotplug_libudev.c:294:get_driver() Looking for a driver for VID: 0x1D6B, PID: 0x0002, path: /dev/bus/usb/001/001
0056 hotplug_libudev.c:294:get_driver() Looking for a driver for VID: 0x1D6B, PID: 0x0002, path: /dev/bus/usb/001/001
0058 hotplug_libudev.c:294:get_driver() Looking for a driver for VID: 0x0C45, PID: 0x6713, path: /dev/bus/usb/001/005
0064 hotplug_libudev.c:294:get_driver() Looking for a driver for VID: 0x0C45, PID: 0x6713, path: /dev/bus/usb/001/005
0057 hotplug_libudev.c:294:get_driver() Looking for a driver for VID: 0x1D6B, PID: 0x0002, path: /dev/bus/usb/001/001
0059 hotplug_libudev.c:294:get_driver() Looking for a driver for VID: 0x1050, PID: 0x0115, path: /dev/bus/usb/001/002
0004 hotplug_libudev.c:433:HPAddDevice() Adding USB device: Yubico Yubikey NEO U2F+CCID
0026 readerfactory.c:1066:RFInitializeReader() Attempting startup of Yubico Yubikey NEO U2F+CCID 00 00 using /usr/lib/pcsc/drivers/ifd-ccid.bundle/Contents/Linux/libccid.so
0081 readerfactory.c:951:RFBindFunctions() Loading IFD Handler 3.0
0015 ifdhandler.c:1950:init_driver() Driver version: 1.4.22
0350 ifdhandler.c:1967:init_driver() LogLevel: 0x0003
0003 ifdhandler.c:1978:init_driver() DriverOptions: 0x
0079 ifdhandler.c:110:CreateChannelByNameOrChannel() Lun: 0, device: usb:1050/0115:libudev:0:/dev/bus/usb/001/002
0010 ccid_usb.c:284:OpenUSBByName() Using: /usr/lib/pcsc/drivers/ifd-ccid.bundle/Contents/Info.plist
0346 ccid_usb.c:302:OpenUSBByName() ifdManufacturerString: Ludovic Rousseau (ludovic.rouss...@free.fr)
0003 ccid_usb.c:303:OpenUSBByName() ifdProductString: Generic CCID driver
0001 ccid_usb.c:304:OpenUSBByName() Copyright: This driver is protected by terms of the GNU Lesser General Public License version 2.1, or (at your option) any later version.
libusb: debug [libusb_init] created default context
libusb: debug [libusb_init] libusb v1.0.20.11004
libusb: debug [find_usbfs_path] found usbfs at /dev/bus/usb
libusb: debug [op_init] bulk continuation flag supported
libusb: debug [op_init] zero length packet flag supported
libusb: debug [op_init] sysfs can relate devices
libusb: debug [op_init] sysfs has complete descriptors
libusb: debug [linux_udev_event_thread_main] udev event thread entering.
libusb: debug [linux_get_device_address] getting address for device: usb1 detached: 0
libusb: debug [linux_get_device_address] scan usb1
libusb: debug [linux_get_device_address] bus=1 dev=1
libusb: debug [linux_enumerate_device] busnum 1 devaddr 1 session_id 257
libusb: debug [linux_enumerate_device] allocating new device for 1/1 (session 257)
libusb: debug [linux_get_device_address] getting address for device: 1-12 detached: 0
libusb: debug [linux_get_device_address] scan 1-12
libusb: debug [linux_get_device_address] bus=1 dev=5
libusb: debug [linux_enumerate_device] busnum 1 devaddr 5 session_id 261
libusb: debug [linux_enumerate_device] allocating new device for 1/5 (session 261)
libusb: debug [linux_get_parent_info] Dev 0x110e040 (1-12) has parent 0x1103b70 (usb1) port 12
libusb: debug [linux_get_device_address] getting address for device: 1-2 detached: 0
libusb: debug [linux_get_device_address] scan 1-2
libusb: debug [linux_get_device_address] bus=1 dev=2
libusb: debug [linux_enumerate_device] busnum 1 devaddr 2 session_id 258
libusb: debug [linux_enumerate_device] allocating new device for 1/2 (session 258)
libusb: debug [linux_get_parent_info] Dev 0x1108320 (1-2) has parent 0x1103b70 (usb1) port 2
libusb: debug [linux_get_device_address] getting address for device: 1-4 detached: 0
libusb: debug [linux_get_device_address] scan 1-4
libusb: debug [linux_get_device_address] bus=1 dev=3
libusb: debug [linux_enumerate_device] busnum 1 devaddr 3 session_id 259
libusb: debug [linux_enumerate_device] allocating new device for 1/3 (session 259)
libusb: debug [linux_get_parent_info] Dev 0x1106d50 (1-4) has parent 0x1103b70 (usb1) port 4
libusb: debug [linux_get_device_address] getting address for device: 1-9 detached: 0
libusb: debug 

Bug#815838: linux-image-3.16.0-4-amd64: Boot randomly fails with "Initramfs unpacking failed", probably due to kaslr bug upstream

[Ben Hutchings]

Control: severity -1 important
Control: tag -1 moreinfo

On Wed, 24 Feb 2016 17:40:58 -0500 Blake Miner  wrote:
> Package: src:linux
> Version: 3.16.7-ckt11-1+deb8u6
> Severity: critical
> Justification: breaks the whole system
> 
> Dear Maintainer,
> 
> The operating system will boot up fine in most cases, but randomly, the 
> kernel will panic on boot-up and display
> "Initramfs unpacking failed: uncompression error"

Is your processor overclocked?  Have you run a RAM test (e.g.. memtest86+)?

> I am running this kernel (I know that it's not quite up-to-date):
> 3.16.0-4-amd64 #1 SMP Debian 3.16.7-ckt11-1+deb8u6 (2015-11-09) x86_64 
> GNU/Linux

Please re-test with the current kernel version.

> I believe that this problem is caused by a bug already fixed upstream by the 
> Linux Kernel team but not yet
> fixed in the Debian 3.16 kernel.
> 
> Please check out commit 664653016626d15d3e898aabd0785f1b785f6400
> https://github.com/torvalds/linux/commit/664653016626d15d3e898aabd0785f1b785f6400
> 
> An excerpt of the commit message is as follows:
> 
> ---
> x86, kaslr: Prevent .bss from overlaping initrd"
[...]

We don't build with kaslr, so this doesn't explain the problem.

Ben.

-- 
Ben Hutchings
When in doubt, use brute force. - Ken Thompson

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

Processed: Re: linux-image-3.16.0-4-amd64: Boot randomly fails with "Initramfs unpacking failed", probably due to kaslr bug upstream

[Debian Bug Tracking System]

Processing control commands:

> severity -1 important
Bug #815838 [src:linux] linux-image-3.16.0-4-amd64: Boot randomly fails with 
"Initramfs unpacking failed", probably due to kaslr bug upstream
Severity set to 'important' from 'critical'
> tag -1 moreinfo
Bug #815838 [src:linux] linux-image-3.16.0-4-amd64: Boot randomly fails with 
"Initramfs unpacking failed", probably due to kaslr bug upstream
Added tag(s) moreinfo.

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

Bug#804463: ckermit: FTBFS: ?wermit not found

[Sebastian Andrzej Siewior]

control: tags -1 +fixed-upstream

On 2015-11-08 19:01:29 [+], Chris West (Faux) wrote:
> make[1]: *** [override_dh_auto_install] Error 2

missing SSLv3. According to [0] the issue has been addressed upstream:

|25 Dec 2015 9.0.304 Dev.15
|§ Changes to makefile for building on Red Hat Linux EL6 on x86_64, and in
|particular for detecting the case where the ncurses lib is installed but
|ncurses.h is not (in which case C-Kermit builds without curses support).   §
|Patches from Bernard Spil: "Kermit fails to build when OpenSSL libraries built
|without SSLv3 are used (configure --no-ssl2 --nossl3). 

I haven't found any VCS of this project so I can't point here to a patch. But
the x.tar file there has it fixed.

[0] http://www.kermitproject.org/ckdaily.html

Sebastian

Processed: Re: Bug#804463: ckermit: FTBFS: ?wermit not found

[Debian Bug Tracking System]

Processing control commands:

> tags -1 +fixed-upstream
Bug #804463 [src:ckermit] ckermit: FTBFS: ?wermit not found
Added tag(s) fixed-upstream.

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

Bug#816965: fonts-mathematica: fails to install if mathematica-fonts 17 is installed

[Julian Gilbey]

Package: fonts-mathematica
Version: 18
Severity: serious

When trying to install, I get the following error message:

Preparing to unpack .../fonts-mathematica_18_all.deb ...
The license has already been accepted
Unpacking fonts-mathematica (18) ...
dpkg: error processing archive 
/var/cache/apt/archives/fonts-mathematica_18_all.deb (--unpack):
 trying to overwrite '/usr/share/mathematica-fonts/sha512-ttf', which is also 
in package mathematica-fonts 17

I assume that this is because fonts-mathematica doesn't correctly
declare Provides/Conflicts/Replaces dependencies in the control file.

   Julian

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

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

-- debconf information:
  mathematica-fonts/http_proxy:
* mathematica-fonts/accept_license: true
* mathematica-fonts/license:

Bug#815945: marked as done (sagan: FTBFS on *-i386: attempts to use 64-bit x86 assembly on 32-bit x86 arch)

[Debian Bug Tracking System]

Your message dated Sun, 06 Mar 2016 17:26:58 +
with message-id 
and subject line Bug#815945: fixed in sagan 1.0.1-0.2
has caused the Debian Bug report #815945,
regarding sagan: FTBFS on *-i386: attempts to use 64-bit x86 assembly on 32-bit 
x86 arch
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.)


-- 
815945: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=815945
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: sagan
Version: 1.0.1-0.1
Severity: serious
Justification: fails to build from source (but built successfully in the past)

Hi,

sagan FTBFS on i386 and kfreebsd-i386:

https://buildd.debian.org/status/fetch.php?pkg=sagan=kfreebsd-i386=1.0.1-0.1=1452795608
https://buildd.debian.org/status/fetch.php?pkg=sagan=i386=1.0.1-0.1=1452795303

[...]
gcc -DHAVE_CONFIG_H -I. -I..  -I.. -I/usr/include/json-c  -Wdate-time 
-D_FORTIFY_SOURCE=2  -g -O2 -fstack-protector-strong -Wformat 
-Werror=format-security -c -o sagan-strstr_sse2.o `test -f 
'parsers/sagan-strstr/strstr_sse2.S' || echo 
'./'`parsers/sagan-strstr/strstr_sse2.S
parsers/sagan-strstr/strstr_sse2.S: Assembler messages:
parsers/sagan-strstr/strstr_sse2.S:52: Error: bad register name `%rsi)'
[...]


Andreas
--- End Message ---
--- Begin Message ---
Source: sagan
Source-Version: 1.0.1-0.2

We believe that the bug you reported is fixed in the latest version of
sagan, 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.
Herbert Parentes Fortes Neto  (supplier of updated sagan 
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, 01 Mar 2016 08:32:50 -0300
Source: sagan
Binary: sagan
Architecture: source amd64
Version: 1.0.1-0.2
Distribution: unstable
Urgency: low
Maintainer: Pierre Chifflier 
Changed-By: Herbert Parentes Fortes Neto 
Description:
 sagan  - Real-time System & Event Log Monitoring System
Closes: 815945
Changes:
 sagan (1.0.1-0.2) unstable; urgency=low
 .
   * Non-maintainer upload.
   * debian/patches:
   - no-bluedot.patch renamed. no-bluedot-and-others.patch.
 Less rules, less mem usage. Doesn't run with all rules.
   * debian/rules:
   - DEB_HOST_ARCH var added. To enable '--enable-system-strstr'
 when compiling on i386. (Closes:  #815945).
Checksums-Sha1:
 bd216185368c4275e762347668967df8b7f90d87 1806 sagan_1.0.1-0.2.dsc
 11dec6b10e7761828e9723424df4255edc34b8dd 7444 sagan_1.0.1-0.2.debian.tar.xz
 872d4ec25ad917bf59558a299458158ca4c04efe 77712 sagan_1.0.1-0.2_amd64.deb
Checksums-Sha256:
 b44f6e075442d424bcb45c49d24017e5f3ee827734af3af911a9e14b801ce4a5 1806 
sagan_1.0.1-0.2.dsc
 45ac9c159d73b80d17bb25671abf659ceef7e0b5850170e95929965c9c632de8 7444 
sagan_1.0.1-0.2.debian.tar.xz
 d7014a702a02392aadf731d666908b462364940a999ae7b8689b5db447b8423b 77712 
sagan_1.0.1-0.2_amd64.deb
Files:
 bad184253ea51eecd680aecd982c7567 1806 admin extra sagan_1.0.1-0.2.dsc
 5466753b3953fa2d3eb9e864a36c7608 7444 admin extra sagan_1.0.1-0.2.debian.tar.xz
 6bf73ca6ca46f42ef0aa3787c858d506 77712 admin extra sagan_1.0.1-0.2_amd64.deb

-BEGIN PGP SIGNATURE-
Version: GnuPG v1

iQIcBAEBAgAGBQJW1ckBAAoJEN5juccE6+nvTdAP/24qDto+/zWAxiiSBO1icBYg
ve5dDZW2EtxOUocUFvZSJHzR5jy6amxkyVIoO9Sen+9fKseCHJRjW1xU2YIhscL9
uiNsr+kJ56Mt8lsIQr4F9MxS1ohI1iP6UumtIe0bQRq0k3kGsGoROvJZKdhgieVJ
fSbzQYXh6p6DocD8BJFNSi8M7ngZkBxbWOCER/ne9FweLlxXQhET184X0pyyji+D
VuEqD6ViEI8mK0e/YAB9vdDlBX7D0hFM/nsUggn4A+p3YhOcE3iai+PHRAMXm+aO
G5UYvAG32TeB//DEXkTGU9gIsRzdVr2VSD9f7093OGxZacwcz5YhhHaI/RSoaEqV
MQ4G++RKuVAvWVYOx7ltcSQCSyo5v+yKIvXhao6zDuPror5Fj+rwdD/8kKKRNeUs
kL0EoCaT9QRabmKBNG3P8RkeiBBIpHVCmk+fVgCuTCAZaPVmS8F9Oo9cl38ooL0e
BMtlVzTe7evdlKq6Ct62qa1ut3HvN3hVRu5PRBWmzwMzOaakm5KrcyPi3roVPSZ9
IwN9KbQiBcMe+QAsiuehawEEyUdybKTsBcEGI+sNAmhfHRGEiV76lJF0ROLxFbvM
yvgam4PX7tNhHTFc51uATMpWl6vUiOJKknNfRCa71lz4dCT4Da45RvHh5ivnZduw
S02qAUGbS18p7TRf5uCw
=1qu5
-END PGP SIGNATURE End Message ---

Bug#816076: wicd-daemon: upgrade reconfigures static ethernet interface, and kills ssh sessions.

[Axel Beckert]

Hi Andrew,

Andrew Vaughan wrote:
> My home server is a headless box, administered from a vnc session tunnelled
> over ssh.  It has no wifi adaptor, just a single ethernet port that is
> statically configured via /etc/network/interfaces.

So why are you using wicd at all? I don't see why you need wicd in
such a setup.

> This behaviour is wrong on so many levels.
> 
> 1. A package upgrade should never bring down an existing in-use interface
> without asking the user/admin first.

I agree here mostly. It's though only a real issue if the interface
doesn't come up again with the same IP afterwards.

> 2. I don't think I have ever actually used wicd.

See my question above. You don't need it.

> Wicd-daemon should not assume that just because it is installed it
> owns all the network interfaces.

I disagree here. In Debian, it's common that NetworkManager and
similar tools manage those interfaces from /etc/network/interfaces
which are not listed (or maybe also those which are on "auto").

The issue here seems that wicd seems to no more blacklists them. Will
have to check.

> I have been through basically the same problems with network-manager in the
> past.  Issues like this are why so many people are hostile to that package.

Indeed. That's why I'm using wicd, too. It was though worse with
NetworkManager back then since usually, the network interface stayed
down afterwards. That got fixed in the meanwhile, though, IIRC.

For now I've forwarded this issue to upstream at
https://bugs.launchpad.net/wicd/+bug/1553761

Regards, Axel
-- 
 ,''`.  |  Axel Beckert , http://people.debian.org/~abe/
: :' :  |  Debian Developer, ftp.ch.debian.org Admin
`. `'   |  4096R: 2517 B724 C5F6 CA99 5329  6E61 2FF9 CD59 6126 16B5
  `-|  1024D: F067 EA27 26B9 C3FC 1486  202E C09E 1D89 9593 0EDE

Processed: bug 816076 is forwarded to https://bugs.launchpad.net/wicd/+bug/1553761

[Debian Bug Tracking System]

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

> forwarded 816076 https://bugs.launchpad.net/wicd/+bug/1553761
Bug #816076 [wicd-daemon] wicd-daemon: upgrade reconfigures static ethernet 
interface, and kills ssh sessions.
Set Bug forwarded-to-address to 'https://bugs.launchpad.net/wicd/+bug/1553761'.
> thanks
Stopping processing here.

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

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

[Philip Rinn]

Hi Jeff and Jeffrey,

I think tessaract broke it's ABI again without taking care of renaiming the
package name and bumping SONAME :(

That's really annoying as gimagereader broke again. (See
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=794489 for reference)

Building with tessaract from unstable results in a broken binary in testing - 
same
undefined symbol as last time.

> This is the complete error messager:
>
>   gimagereader-gtk: symbol lookup error: gimagereader-gtk:
>   undefined symbol: _ZN9tesseract11TessBaseAPI13AnalyseLayoutEv

Could you please fix this? And could you take care of this properly next time - 
it
really wasts my time.

Best,
Philip



signature.asc
Description: OpenPGP digital signature

Bug#800190: marked as done (wmf: Please migrate a supported debhelper compat level)

[Debian Bug Tracking System]

Your message dated Sun, 06 Mar 2016 16:49:37 +
with message-id 
and subject line Bug#800190: fixed in wmf 1.0.5-7
has caused the Debian Bug report #800190,
regarding wmf: Please migrate a supported debhelper compat level
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.)


-- 
800190: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=800190
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: wmf
Severity: important
Usertags: deprecated-debhelper-compat-leq-3

Hi,

The package wmf is using a debhelper compat level of 3 or less
according to lintian.  These compat levels have been deprecated for
the past ~10 years and debhelper will remove support for them in the near
future (as declared in [1]).

 * Please migrate the package to a supported debhelper compat level.
   - Compat 9 is recommended
   - Compat 5 is the bare minimum (compat 4 will be removed soon as
 well)

 * If your package uses any of the following tools, please remove them
   from the rules files.  Neither of them does anything except warn
   about their deprecation.
   - dh_desktop
   - dh_scrollkeeper (deadline: January 1st 2016)
   - dh_suidregister
   - dh_undocumented

 * Please note that your package might have been flagged for using
   e.g. "DH_COMPAT=2 dh_foo ...".
   - This will still cause issues when the compat level is removed.

 * If the package has been relying on dh_install being lenient about
   missing files, please see "MIGRATING TO COMPAT 5 OR LATER" in [1].

 * Deadline: 
   - compat 1+2: November 1st 2015
   - compat 3: January 1st 2016

If you are using other deprecated debhelper features (such as omitting
the debian/compat file), please consider fixing those while you are at
it.

Thanks,
~Niels

[1] https://lists.debian.org/debian-devel/2015/09/msg00257.html
--- End Message ---
--- Begin Message ---
Source: wmf
Source-Version: 1.0.5-7

We believe that the bug you reported is fixed in the latest version of
wmf, 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 800...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Francesco Paolo Lovergine  (supplier of updated wmf 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: Sun, 06 Mar 2016 14:08:21 +0100
Source: wmf
Binary: wmf
Architecture: source amd64
Version: 1.0.5-7
Distribution: unstable
Urgency: medium
Maintainer: Francesco Paolo Lovergine 
Changed-By: Francesco Paolo Lovergine 
Description:
 wmf- Web Mail Folder
Closes: 438268 800190
Changes:
 wmf (1.0.5-7) unstable; urgency=medium
 .
   * Package revamped with modern debhelper. Previous patches are now properly
 introduced as standalone.
 (closes: #800190)
   * Removed auto-stripping at install time as present in the original upstream
 makefile
 (closes: #438268)
Checksums-Sha1:
 5e7550507559668795e7ccc0fd1fe69c02c319d2 1675 wmf_1.0.5-7.dsc
 c7cc00d061d966193be1e179de3a3a41535f6a19 6004 wmf_1.0.5-7.debian.tar.xz
 12020ac60e52c1c51e31d2d719767ce9314e18dd 73862 wmf-dbgsym_1.0.5-7_amd64.deb
 59bef29fd13cbcfec973f08d6a368d415cd51a74 46624 wmf_1.0.5-7_amd64.deb
Checksums-Sha256:
 78a330e617c5d4181d3dfe964bb7ca4ccbb88215085c8533b103392eb9ad054c 1675 
wmf_1.0.5-7.dsc
 d8edfe0762da5689a0de3f17013b45c42c40b9f98db23c1269da4a687319bc9c 6004 
wmf_1.0.5-7.debian.tar.xz
 7195ba24e83d54790eb8ea86f6c62b401722543a11bf68354b5d7f01643992aa 73862 
wmf-dbgsym_1.0.5-7_amd64.deb
 495e3585515ddb6e3b807875b115a631f61ad57d20bcb8159e4ff56097a81a5b 46624 
wmf_1.0.5-7_amd64.deb
Files:
 6c69e5aac33db0a5d5f121b57a6c6b6d 1675 web optional wmf_1.0.5-7.dsc
 2527f5a785d119cf0e5675e480e5105b 6004 web optional wmf_1.0.5-7.debian.tar.xz
 1605c822340a060857a569d1b708303e 73862 debug extra wmf-dbgsym_1.0.5-7_amd64.deb
 3ceca633cd0c37942ebfb36d2e244ac4 46624 web optional wmf_1.0.5-7_amd64.deb

-BEGIN PGP SIGNATURE-
Version: GnuPG v1

iQIcBAEBAgAGBQJW3DwKAAoJEA8CpeEWNoakkm0P/ROSKBK2bOSClJLALJLr7/GS
X/1EtH59PWL+EFqS0ZyYjehlS3nbHYeYoZIg5fueZyws4McNYLF5gkXiaxEwriNi
8+Sb0zzksiLItMMe4JjRLTT5AmuVb2SIA41NnCr2cuC/eKdx3LLcfYXwjITGDSe+

Bug#816076: wicd-daemon: upgrade reconfigures static ethernet interface, and kills ssh sessions.

[Axel Beckert]

Hi Gianfranco,

On Sat, Mar 05, 2016 at 03:51:23PM +, Gianfranco Costamagna wrote:
> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=816076

Thanks for the heads up. I seem to have missed that bug report
initially.

I noticed that interruption, too, at least once. But IIRC in my case,
network came back with the same IP IIRC since the IP was assigned
staticallt by the DHCP server. I'll forward it to upstream for now.

Kind regards, Axel
-- 
/~\  Plain Text Ribbon Campaign   | Axel Beckert
\ /  Say No to HTML in E-Mail and News| a...@deuxchevaux.org  (Mail)
 X   See http://www.nonhtmlmail.org/campaign.html | a...@noone.org (Mail+Jabber)
/ \  I love long mails: http://email.is-not-s.ms/ | http://abe.noone.org/ (Web)

Bug#800261: marked as done (athena-jot: Please migrate a supported debhelper compat level)

[Debian Bug Tracking System]

Your message dated Sun, 06 Mar 2016 16:34:43 +
with message-id 
and subject line Bug#800261: fixed in athena-jot 9.0-6
has caused the Debian Bug report #800261,
regarding athena-jot: Please migrate a supported debhelper compat level
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.)


-- 
800261: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=800261
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: athena-jot
Severity: important
Usertags: deprecated-debhelper-compat-leq-3

Hi,

The package athena-jot is using a debhelper compat level of 3 or less
according to lintian.  These compat levels have been deprecated for
the past ~10 years and debhelper will remove support for them in the near
future (as declared in [1]).

 * Please migrate the package to a supported debhelper compat level.
   - Compat 9 is recommended
   - Compat 5 is the bare minimum (compat 4 will be removed soon as
 well)

 * If your package uses any of the following tools, please remove them
   from the rules files.  Neither of them does anything except warn
   about their deprecation.
   - dh_desktop
   - dh_scrollkeeper (deadline: January 1st 2016)
   - dh_suidregister
   - dh_undocumented

 * Please note that your package might have been flagged for using
   e.g. "DH_COMPAT=2 dh_foo ...".
   - This will still cause issues when the compat level is removed.

 * If the package has been relying on dh_install being lenient about
   missing files, please see "MIGRATING TO COMPAT 5 OR LATER" in [1].

 * Deadline: 
   - compat 1+2: November 1st 2015
   - compat 3: January 1st 2016

If you are using other deprecated debhelper features (such as omitting
the debian/compat file), please consider fixing those while you are at
it.

Thanks,
~Niels

[1] https://lists.debian.org/debian-devel/2015/09/msg00257.html
--- End Message ---
--- Begin Message ---
Source: athena-jot
Source-Version: 9.0-6

We believe that the bug you reported is fixed in the latest version of
athena-jot, 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 800...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Francesco Paolo Lovergine  (supplier of updated athena-jot 
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: Sun, 06 Mar 2016 16:39:43 +0100
Source: athena-jot
Binary: athena-jot
Architecture: source amd64
Version: 9.0-6
Distribution: unstable
Urgency: medium
Maintainer: Francesco Paolo Lovergine 
Changed-By: Francesco Paolo Lovergine 
Description:
 athena-jot - print out increasing, decreasing, random, or redundant data, one
Closes: 800261
Changes:
 athena-jot (9.0-6) unstable; urgency=medium
 .
   * Package revamped to a modern style of debhelper.
 (closes: #800261)
   * Policy updated to 3.8.7.
   * Moved to quilt patch style.
Checksums-Sha1:
 f68086c03f3af9da57b9667353393355b60e925c 1675 athena-jot_9.0-6.dsc
 1e284d132fe037d60349da2bdd2db010d71befb6 3376 athena-jot_9.0-6.debian.tar.xz
 ae90e440be199827e3f645545e66efb478c9eda2 8720 athena-jot-dbgsym_9.0-6_amd64.deb
 fc30209e309fecc0eb62a5cb24df85256654a227 10290 athena-jot_9.0-6_amd64.deb
Checksums-Sha256:
 46e81209998d1b888096abf9f0370609cc38e16445547a3b11033c2fe7ffcade 1675 
athena-jot_9.0-6.dsc
 23b72ff72e363f4cb4693dda88c1313bd493f74b1a452c32f264fa1ce8f25140 3376 
athena-jot_9.0-6.debian.tar.xz
 cbd7d2998f2dfbe4d157cd78ef7074da23cdc32ebd8e844ad5039b76bb198999 8720 
athena-jot-dbgsym_9.0-6_amd64.deb
 021a5a6be288e2885c4b8eab7e2598736d5e2bcf352874aa4455a68978bf7eda 10290 
athena-jot_9.0-6_amd64.deb
Files:
 bd2b071a89f2f0b0e2c564c384da048f 1675 utils optional athena-jot_9.0-6.dsc
 c06c8a968d8d9d20df8c546e9fc26caa 3376 utils optional 
athena-jot_9.0-6.debian.tar.xz
 ffce07a265d1f0a6838b0b67c7ad3932 8720 debug extra 
athena-jot-dbgsym_9.0-6_amd64.deb
 8dbfb3a91770e7c3b0d6ae781ea76e2e 10290 utils optional 
athena-jot_9.0-6_amd64.deb

-BEGIN PGP SIGNATURE-
Version: GnuPG v1

iQIcBAEBAgAGBQJW3FY8AAoJEA8CpeEWNoakD+cP/RZ/Bwzxmpci/h4dfG2AoAD4
TElwfSYMAc9HIJ+lr3hSNXj7KHZxQUl6ANlH6wseNSQFMKBtlGcSMZC3pf5tcWGH

Bug#811172: marked as done (mercurial-git: broken SSH: Invalid command: 'g 'i t - u p l o a d - p a c k)

[Debian Bug Tracking System]

Your message dated Sun, 06 Mar 2016 16:35:55 +
with message-id 
and subject line Bug#811172: fixed in hg-git 0.8.5-1
has caused the Debian Bug report #811172,
regarding mercurial-git: broken SSH: Invalid command: 'g 'i t - u p l o a d - p 
a c k
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.)


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

Package: mercurial-git
Version: 0.8.3-1
Severity: grave

After upgrading python-dulwich to 0.12.0-1, I can't do anything over 
SSH. For example:


$ hg clone git+ssh://g...@github.com:jwilk/mwic.git
destination directory: mwic
Invalid command: 'g 'i t - u p l o a d - p a c k   ' j w i l k / m w i c . g i 
t '''
 You appear to be using ssh to clone a git:// URL.
 Make sure your core.gitProxy config option and the
 GIT_PROXY_COMMAND environment variable are NOT set.
abort: git remote error: The remote server unexpectedly closed the connection.


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

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

Versions of packages mercurial-git depends on:
ii  mercurial   3.6.2-1
ii  python-dulwich  0.12.0-1
pn  python:any  

--
Jakub Wilk
--- End Message ---
--- Begin Message ---
Source: hg-git
Source-Version: 0.8.5-1

We believe that the bug you reported is fixed in the latest version of
hg-git, 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 811...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Javi Merino  (supplier of updated hg-git 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: Sun, 06 Mar 2016 14:29:22 +
Source: hg-git
Binary: mercurial-git
Architecture: source all
Version: 0.8.5-1
Distribution: unstable
Urgency: medium
Maintainer: Python Applications Packaging Team 

Changed-By: Javi Merino 
Description:
 mercurial-git - Git plugin for Mercurial
Closes: 805756 811172
Changes:
 hg-git (0.8.5-1) unstable; urgency=medium
 .
   * New upstream version (Closes: #811172)
   * Fix "add explanatory comments in README.Debian for reST markup" by
 clarifying that it uses ReST markup.  Thanks Ben Finney
  for the patch. (Closes: #805756)
   * Improve autopkgtest to push commits from the mercurial clone to git
   * Use https for Vcs-Browser
   * Update hg-git's homepage
   * Bump standards-version to 3.9.7 (no change needed)
   * Fix mercurial-git autopkg test by redirecting stderr to stdout for
 git clone and git push
   * Blacklist test-encoding in the testsuite's autopkgtest
Checksums-Sha1:
 2ba72035d8151fbceed6b0ee0173c58b6af877d8 2011 hg-git_0.8.5-1.dsc
 89d2f79e4633bb648851518483770969bc31b297 101206 hg-git_0.8.5.orig.tar.gz
 81e08d4b42b9bbb6f4d64d9d77cec6acca3012d4 4832 hg-git_0.8.5-1.debian.tar.xz
 a2ee9eae530955dec45cfdbd27ce1764939bd296 44478 mercurial-git_0.8.5-1_all.deb
Checksums-Sha256:
 dda123c0511cb45e8919ef68fdbf22ac5614b8f8e0ae24f826b151c94f20bc24 2011 
hg-git_0.8.5-1.dsc
 3b66224119bd93d870ec1a55f07fae0191b84ff3ae810c557081cf2679bf3af4 101206 
hg-git_0.8.5.orig.tar.gz
 8decf20f94fd80a43884a704c24f565eda013cc6c197ae67f66dfb9755ffbb36 4832 
hg-git_0.8.5-1.debian.tar.xz
 0417d8a2809fbd3c0e4c48089f594a25643e4f437d0642506eb8dea6b45db51d 44478 
mercurial-git_0.8.5-1_all.deb
Files:
 4e7dd2d59c9135d66ccd0bcfd4266ea4 2011 vcs optional hg-git_0.8.5-1.dsc
 f9d18b021c458d7dbecfe527248e181b 101206 vcs optional hg-git_0.8.5.orig.tar.gz
 ff5c4e9335e1b49893b1ef9d850e9cd2 4832 vcs optional hg-git_0.8.5-1.debian.tar.xz
 3d96bec100e8d179bdc8f1f1d9106143 44478 vcs optional 
mercurial-git_0.8.5-1_all.deb

-BEGIN PGP SIGNATURE-
Version: GnuPG v1

iQIcBAEBCAAGBQJW3D/MAAoJEAe0hFJ2jTgkP48QAIjUoQpBbympimJHFzfT5day

Bug#800211: marked as done (dbf2mysql: Please migrate a supported debhelper compat level)

[Debian Bug Tracking System]

Your message dated Sun, 06 Mar 2016 16:35:05 +
with message-id 
and subject line Bug#800211: fixed in dbf2mysql 1.14a-4
has caused the Debian Bug report #800211,
regarding dbf2mysql: Please migrate a supported debhelper compat level
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.)


-- 
800211: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=800211
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: dbf2mysql
Severity: important
Usertags: deprecated-debhelper-compat-leq-3

Hi,

The package dbf2mysql is using a debhelper compat level of 3 or less
according to lintian.  These compat levels have been deprecated for
the past ~10 years and debhelper will remove support for them in the near
future (as declared in [1]).

 * Please migrate the package to a supported debhelper compat level.
   - Compat 9 is recommended
   - Compat 5 is the bare minimum (compat 4 will be removed soon as
 well)

 * If your package uses any of the following tools, please remove them
   from the rules files.  Neither of them does anything except warn
   about their deprecation.
   - dh_desktop
   - dh_scrollkeeper (deadline: January 1st 2016)
   - dh_suidregister
   - dh_undocumented

 * Please note that your package might have been flagged for using
   e.g. "DH_COMPAT=2 dh_foo ...".
   - This will still cause issues when the compat level is removed.

 * If the package has been relying on dh_install being lenient about
   missing files, please see "MIGRATING TO COMPAT 5 OR LATER" in [1].

 * Deadline: 
   - compat 1+2: November 1st 2015
   - compat 3: January 1st 2016

If you are using other deprecated debhelper features (such as omitting
the debian/compat file), please consider fixing those while you are at
it.

Thanks,
~Niels

[1] https://lists.debian.org/debian-devel/2015/09/msg00257.html
--- End Message ---
--- Begin Message ---
Source: dbf2mysql
Source-Version: 1.14a-4

We believe that the bug you reported is fixed in the latest version of
dbf2mysql, 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 800...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Francesco Paolo Lovergine  (supplier of updated dbf2mysql 
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: Sun, 06 Mar 2016 15:32:16 +0100
Source: dbf2mysql
Binary: dbf2mysql
Architecture: source amd64
Version: 1.14a-4
Distribution: unstable
Urgency: low
Maintainer: Francesco Paolo Lovergine 
Changed-By: Francesco Paolo Lovergine 
Description:
 dbf2mysql  - xBase to MySQL or vice versa
Closes: 79046 670726 800211
Changes:
 dbf2mysql (1.14a-4) unstable; urgency=low
 .
   [ Jari Aalto ]
   * Remove deprecated dpatch and upgrade to packaging format "3.0 quilt".
   * Update to Standards-Version to 3.9.3 and debhelper to 9.
   * Add build-arch and build-indep targets; use dh_prep in rules file.
   * Patches:
 - Number all files to make apply order apparent.
 - Patch 05: update with "quilt refresh" to make it apply cleanly.
   * Fix copyright-refers-to-symlink-license (Lintian).
   * Fix copyright-without-copyright-notice (Lintian).
   * Fix debian-rules-ignores-make-clean-error (Lintian).
   * Fix extended-description-is-probably-too-short (Lintian).
 (closes: #670726)
 .
   [ Francesco Paolo Lovergine ]
   * Moved to modern debhelper
 (closes: #800211 )
   * Makefile revised to be nice with dpkg environment, hardening,
 stripping, etc.
   * Build-dep revised to current mysql -dev b-d.
 (closes: #79046)
Checksums-Sha1:
 d05005b949668cab9ec31c54a89b8e16cc838d24 1684 dbf2mysql_1.14a-4.dsc
 9aa16b3e82d2d944eaf5d0f65719575cd42c8ab7 8612 dbf2mysql_1.14a-4.debian.tar.xz
 b9c0a078a219660262293946449fd16faa1cafbb 42858 
dbf2mysql-dbgsym_1.14a-4_amd64.deb
 9732e0287ce72ba265b5fa49725704d928300771 22204 dbf2mysql_1.14a-4_amd64.deb
Checksums-Sha256:
 2c17c5fba883878c7be3d6fa453b0773ed14e9dd9a175cfe0b18792a0cf0f7ea 1684 
dbf2mysql_1.14a-4.dsc
 d24f07cf1000b3b510bc05295e7a649b7608cb14b0b97d7bc98995823caeeff3 8612 
dbf2mysql_1.14a-4.debian.tar.xz
 

Processed: tagging 816626, tagging 812978, tagging 816625

[Debian Bug Tracking System]

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

> tags 816626 + wheezy jessie stretch sid
Bug #816626 [src:jasper] jasper: CVE-2016-2116: memory leak in the 
jas_iccprof_createfrombuf function
Added tag(s) wheezy, sid, jessie, and stretch.
> tags 812978 + wheezy jessie stretch sid
Bug #812978 [src:jasper] jasper: CVE-2016-2089: matrix rows_ NULL pointer 
dereference in jas_matrix_clip()
Added tag(s) stretch, sid, wheezy, and jessie.
> tags 816625 + wheezy jessie stretch sid
Bug #816625 [src:jasper] jasper: CVE-2016-1577: double free vulnerability in 
the jas_iccattrval_destroy function
Added tag(s) stretch, wheezy, sid, and jessie.
> thanks
Stopping processing here.

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

Processed: zeroc-ice: diff for NMU version 3.5.1-6.4

[Debian Bug Tracking System]

Processing control commands:

> tags 815775 + patch
Bug #815775 [zeroc-ice] Build-Depends on unavailable packages mono-gmcs 
libmono2.0-cil
Added tag(s) patch.
> tags 815775 + pending
Bug #815775 [zeroc-ice] Build-Depends on unavailable packages mono-gmcs 
libmono2.0-cil
Added tag(s) pending.

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

Bug#815775: zeroc-ice: diff for NMU version 3.5.1-6.4

[gregor herrmann]

Control: tags 815775 + patch
Control: tags 815775 + pending

Dear maintainer,

Chris Knadle has prepared an NMU for zeroc-ice (versioned as
3.5.1-6.4) and I've uploaded it to DELAYED/2. Please feel free to
tell me if I should delay it longer.

Regards.

-- 
 .''`.  Homepage https://info.comodo.priv.at/ - OpenPGP key 0xBB3A68018649AA06
 : :' : Debian GNU/Linux user, admin, and developer -  https://www.debian.org/
 `. `'  Member of VIBE!AT & SPI, fellow of the Free Software Foundation Europe
   `-   NP: Treibhaus: Joe Zawinul & Syndicate
diff -Nru zeroc-ice-3.5.1/debian/changelog zeroc-ice-3.5.1/debian/changelog
--- zeroc-ice-3.5.1/debian/changelog	2015-11-21 08:41:17.0 +0100
+++ zeroc-ice-3.5.1/debian/changelog	2016-03-06 16:22:22.0 +0100
@@ -1,3 +1,16 @@
+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.]
+
+ -- Christopher Knadle   Fri, 04 Mar 2016 21:54:19 -0500
+
 zeroc-ice (3.5.1-6.3) unstable; urgency=medium
 
   * Non-maintainer upload.
diff -Nru zeroc-ice-3.5.1/debian/control zeroc-ice-3.5.1/debian/control
--- zeroc-ice-3.5.1/debian/control	2015-11-20 05:39:06.0 +0100
+++ zeroc-ice-3.5.1/debian/control	2016-03-06 16:22:22.0 +0100
@@ -18,7 +18,6 @@
 	   ruby,
 	   libqt4-dev,
 Build-Depends-Indep: mono-devel | c-sharp-2.0-compiler,
-		 libmono2.0-cil,
 		 pkg-config,
  		 default-jdk | java-gcj-compat,
 		 libjgoodies-looks-java (>= 2.5.2),
@@ -27,7 +26,6 @@
  		 libdb5.3-java (>= 5.1.4~) | libdb-java (>= 5.1.4~),
 		 ant,
 		 ant-optional,
-		 mono-gmcs,
 	   	 cli-common-dev (>= 0.8~)
 Standards-Version: 3.9.6
 Homepage: http://www.zeroc.com/


signature.asc
Description: Digital Signature

Bug#815734: regression: ESS cannot be compiled

[Dirk Eddelbuettel]

On 6 March 2016 at 13:23, Norbert Preining wrote:
| Dear all
| 
| > BINGO -- once I add that things pass with the new texinfo.tex
| 
| Good. 
| 
| I have uploaded texinfo -5 just now, should be in the repos in
| no time.
| 
| After this, please remove the old texinfo.tex copies - we had to
| fight with outdated texinfo.tex for too often around the 4.8
| times, I try to make sure that this doesn't happen again.

Easy enough for us as doc/texinfo.tex sticks out in git.
 
| For -6 I have added a recommends on texlive-fonts-recommended, but
| this is for users and not targetting package builds. So please
| add the build-dep if necessary.

Done in the ess git repo which contains debian/.

I'll upload a new ess_15.09.2-3 with these changes too.

All good then -- so thanks all.

Dirk

-- 
http://dirk.eddelbuettel.com | @eddelbuettel | e...@debian.org

Bug#816698: subversion: FTBFS on mips, mipsel

[James McCoy]

On Fri, Mar 04, 2016 at 06:41:00PM +0100, Christian Hofstaedtler wrote:
> Your package FTBFS on the mips and mipsel buildds:
> 
> https://buildd.debian.org/status/fetch.php?pkg=subversion=mips=1.9.3-2%2Bb1=1457047589
> https://buildd.debian.org/status/fetch.php?pkg=subversion=mipsel=1.9.3-2%2Bb1=1457043167

Odd.  Both built fine in the last sourceful upload.

Cheers,
-- 
James
GPG Key: 4096R/331BA3DB 2011-12-05 James McCoy 

Processed: your mail

[Debian Bug Tracking System]

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

> tag 811172 + pending
Bug #811172 [mercurial-git] mercurial-git: broken SSH: Invalid command: 'g 'i t 
- u p l o a d - p a c k
Added tag(s) pending.
> thanks
Stopping processing here.

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

Bug#816357: marked as done (jedit: FTBFS: XThis.java:128: error: cannot find symbol [..] NotSerializableException)

[Debian Bug Tracking System]

Your message dated Sun, 6 Mar 2016 15:06:41 +0100
with message-id <56dc3971.6080...@debian.org>
and subject line Re: Bug#816357: jedit: FTBFS: XThis.java:128: error: cannot 
find symbol [..] NotSerializableException
has caused the Debian Bug report #816357,
regarding jedit: FTBFS: XThis.java:128: error: cannot find symbol [..] 
NotSerializableException
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.)


-- 
816357: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=816357
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: jedit
Version: 5.3.0+dfsg-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,

jedit fails to build from source in unstable/amd64:

  [..]

  [javac] 
/home/lamby/temp/cdt.20160301065925.cu0iTWjXkj/jedit-5.3.0+dfsg/org/gjt/sp/jedit/bsh/Primitive.java:75:
 warning: [unchecked] unchecked call to put(K,V) as a member of the raw type 
Hashtable
  [javac]   wrapperMap.put( Boolean.TYPE, Boolean.class );
  [javac] ^
  [javac]   where K,V are type-variables:
  [javac] K extends Object declared in class Hashtable
  [javac] V extends Object declared in class Hashtable
  [javac] 
/home/lamby/temp/cdt.20160301065925.cu0iTWjXkj/jedit-5.3.0+dfsg/org/gjt/sp/jedit/bsh/Primitive.java:76:
 warning: [unchecked] unchecked call to put(K,V) as a member of the raw type 
Hashtable
  [javac]   wrapperMap.put( Byte.TYPE, Byte.class );
  [javac] ^
  [javac]   where K,V are type-variables:
  [javac] K extends Object declared in class Hashtable
  [javac] V extends Object declared in class Hashtable
  [javac] 
/home/lamby/temp/cdt.20160301065925.cu0iTWjXkj/jedit-5.3.0+dfsg/org/gjt/sp/jedit/bsh/Primitive.java:77:
 warning: [unchecked] unchecked call to put(K,V) as a member of the raw type 
Hashtable
  [javac]   wrapperMap.put( Short.TYPE, Short.class );
  [javac] ^
  [javac]   where K,V are type-variables:
  [javac] K extends Object declared in class Hashtable
  [javac] V extends Object declared in class Hashtable
  [javac] 
/home/lamby/temp/cdt.20160301065925.cu0iTWjXkj/jedit-5.3.0+dfsg/org/gjt/sp/jedit/bsh/XThis.java:128:
 error: cannot find symbol
  [javac]   throw new NotSerializableException();
  [javac] ^
  [javac]   symbol:   class NotSerializableException
  [javac]   location: class XThis.Handler
  [javac] Note: Some input files additionally use or override a deprecated 
API.
  [javac] Note: Some input files additionally use unchecked or unsafe 
operations.
  [javac] 2 errors
  [javac] 100 warnings
  
  BUILD FAILED
  
/home/lamby/temp/cdt.20160301065925.cu0iTWjXkj/jedit-5.3.0+dfsg/build.xml:231: 
Compile failed; see the compiler error output for details.
  
  Total time: 5 seconds
  debian/rules:26: recipe for target 'override_dh_auto_build' failed
  make[1]: *** [override_dh_auto_build] Error 1
  make[1]: Leaving directory 
'/home/lamby/temp/cdt.20160301065925.cu0iTWjXkj/jedit-5.3.0+dfsg'
  debian/rules:12: recipe for target 'build' failed
  make: *** [build] Error 2

  [..]

The full build log is attached.


Regards,

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


jedit.5.3.0+dfsg-1.unstable.amd64.log.txt.gz
Description: Binary data
--- End Message ---
--- Begin Message ---
Version: 2.0b4-17

Closing because this is fixed in 2.0b4-17.





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

Bug#816228: Don't include in stretch

[Salvatore Bonaccorso]

To record it in #816228: A tracker page for the removal was set up as

https://release.debian.org/transitions/html/jasper-rm.html

Regards,
Salvatore

Bug#816842: marked as done (ruby-buff-extensions: FTBFS: Failure/Error: expect(hash.dig('ssl.verify')).to eql(false))

[Debian Bug Tracking System]

Your message dated Sun, 6 Mar 2016 10:26:49 -0300
with message-id <20160306132648.GB85368@sx>
and subject line Re: #816842: fixed in unstable already
has caused the Debian Bug report #816842,
regarding ruby-buff-extensions: FTBFS: Failure/Error: 
expect(hash.dig('ssl.verify')).to eql(false)
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.)


-- 
816842: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=816842
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: ruby-buff-extensions
Version: 1.0.0-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,

ruby-buff-extensions fails to build from source in unstable/amd64:

  [..]
  
  
RUBYLIB=/home/lamby/temp/cdt.20160305144911.ZiI4P04MVS/ruby-buff-extensions-1.0.0/debian/ruby-buff-extensions/usr/lib/ruby/vendor_ruby:.
 
GEM_PATH=debian/ruby-buff-extensions/usr/share/rubygems-integration/all:/home/lamby/.gem/ruby/2.3.0:/var/lib/gems/2.3.0:/usr/lib/x86_64-linux-gnu/rubygems-integration/2.3.0:/usr/share/rubygems-integration/2.3.0:/usr/share/rubygems-integration/all
 ruby2.3 -S rake -f debian/ruby-tests.rake
  /usr/bin/ruby2.3 /usr/bin/rspec --pattern ./spec/\*\*/\*_spec.rb
  Run options: include {:focus=>true}
  
  All examples were filtered out; ignoring {:focus=>true}
  ..FF.F
  
  Failures:
  
1) Buff::Extensions::Hash::DottedPaths#dig returns 'false' nested values as 
'false' and not 'nil'
   Failure/Error: expect(hash.dig('ssl.verify')).to eql(false)
 
 expected: false
  got: nil
 
 (compared using eql?)
   # ./spec/buff/extensions/hash/dotted_paths_spec.rb:94:in `block (3 
levels) in '
  
2) Buff::Extensions::Hash::DottedPaths#dig when the Hash contains the 
nested path returns the value at the dotted path
   Failure/Error: expect(subject.dig("we.found.something")).to eql(true)
 
 expected: true
  got: nil
 
 (compared using eql?)
   # ./spec/buff/extensions/hash/dotted_paths_spec.rb:57:in `block (4 
levels) in '
  
3) Buff::Extensions::Hash::DottedPaths#dig when the Hash contains symbols 
for keys returns the value at the dotted path
   Failure/Error: expect(subject.dig("we.found.something")).to 
eql(:symbol_value)
 
 expected: :symbol_value
  got: nil
 
 (compared using eql?)
   # ./spec/buff/extensions/hash/dotted_paths_spec.rb:79:in `block (4 
levels) in '
  
  Deprecation Warnings:
  
  RSpec::Core::Configuration#treat_symbols_as_metadata_keys_with_true_values= 
is deprecated, it is now set to true as default and setting it to false has no 
effect.
  
  
  If you need more of the backtrace for any of these deprecations to
  identify where to make the necessary changes, you can configure
  `config.raise_errors_for_deprecations!`, and it will turn the
  deprecation warnings into errors, giving you the full backtrace.
  
  1 deprecation warning total
  
  Finished in 0.01781 seconds (files took 0.09499 seconds to load)
  14 examples, 3 failures
  
  Failed examples:
  
  rspec ./spec/buff/extensions/hash/dotted_paths_spec.rb:87 # 
Buff::Extensions::Hash::DottedPaths#dig returns 'false' nested values as 
'false' and not 'nil'
  rspec ./spec/buff/extensions/hash/dotted_paths_spec.rb:56 # 
Buff::Extensions::Hash::DottedPaths#dig when the Hash contains the nested path 
returns the value at the dotted path
  rspec ./spec/buff/extensions/hash/dotted_paths_spec.rb:78 # 
Buff::Extensions::Hash::DottedPaths#dig when the Hash contains symbols for keys 
returns the value at the dotted path
  
  /usr/bin/ruby2.3 /usr/bin/rspec --pattern ./spec/\*\*/\*_spec.rb failed
  ERROR: Test "ruby2.3" failed. Exiting.
  dh_auto_install: dh_ruby --install 
/home/lamby/temp/cdt.20160305144911.ZiI4P04MVS/ruby-buff-extensions-1.0.0/debian/ruby-buff-extensions
 returned exit code 1
  debian/rules:15: 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
   `-


ruby-buff-extensions.1.0.0-1.unstable.amd64.log.txt.gz
Description: Binary data
--- End Message ---
--- Begin Message ---
Control: fixed -1 ruby-buff-extensions/1.0.0-3

The FTBFS you have reported does not apply to the version in
unstable, therefore closing.

-- 
 ,''`.  Christian Hofstaedtler 
: :' :  Debian 

Bug#816841: marked as done (ruby-buff-config: FTBFS: (test failure) Buff::Config::JSON#reload updates the contents of self from disk)

[Debian Bug Tracking System]

Your message dated Sun, 6 Mar 2016 10:27:52 -0300
with message-id <20160306132751.GC85368@sx>
and subject line Re: #816841: fixed in unstable already
has caused the Debian Bug report #816841,
regarding ruby-buff-config: FTBFS: (test failure) Buff::Config::JSON#reload 
updates the contents of self from disk
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.)


-- 
816841: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=816841
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: ruby-buff-config
Version: 1.0.0-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,

ruby-buff-config fails to build from source in unstable/amd64:

  [..]

  All examples were filtered out; ignoring {:focus=>true}
  ...F..F..F..F.
  
  Failures:
  
1) Buff::Config::JSON#reload updates the contents of self from disk
   Failure/Error: expect(original.job).to eql("programmer")
 
 expected: "programmer"
  got: nil
 
 (compared using eql?)
   # ./spec/buff/config/json_spec.rb:128:in `block (3 levels) in '
  
2) Buff::Config::Ruby ClassMethods .from_ruby assigns values for each 
defined attribute
   Failure/Error: expect(config[:log_level]).to eq(:info)
 
 expected: :info
  got: nil
 
 (compared using ==)
   # ./spec/buff/config/ruby_spec.rb:37:in `block (4 levels) in '
  
3) Buff::Config::Ruby#from_ruby assigns values for each defined attribute
   Failure/Error: expect(config[:log_level]).to eq(:info)
 
 expected: :info
  got: nil
 
 (compared using ==)
   # ./spec/buff/config/ruby_spec.rb:102:in `block (3 levels) in '
  
4) Buff::Config::Ruby#reload updates the contents of self from disk
   Failure/Error: expect(subject.log_level).to eq(:info)
 
 expected: :info
  got: :warn
 
 (compared using ==)
 
 Diff:
 @@ -1,2 +1,2 @@
 -:info
 +:warn
   # ./spec/buff/config/ruby_spec.rb:137:in `block (3 levels) in '
  
  Deprecation Warnings:
  
  RSpec::Core::Configuration#treat_symbols_as_metadata_keys_with_true_values= 
is deprecated, it is now set to true as default and setting it to false has no 
effect.
  
  
  If you need more of the backtrace for any of these deprecations to
  identify where to make the necessary changes, you can configure
  `config.raise_errors_for_deprecations!`, and it will turn the
  deprecation warnings into errors, giving you the full backtrace.
  
  1 deprecation warning total
  
  Finished in 0.06192 seconds (files took 0.1804 seconds to load)
  30 examples, 4 failures
  
  Failed examples:
  
  rspec ./spec/buff/config/json_spec.rb:121 # Buff::Config::JSON#reload updates 
the contents of self from disk
  rspec ./spec/buff/config/ruby_spec.rb:34 # Buff::Config::Ruby ClassMethods 
.from_ruby assigns values for each defined attribute
  rspec ./spec/buff/config/ruby_spec.rb:99 # Buff::Config::Ruby#from_ruby 
assigns values for each defined attribute
  rspec ./spec/buff/config/ruby_spec.rb:128 # Buff::Config::Ruby#reload updates 
the contents of self from disk
  
  /usr/bin/ruby2.3 /usr/bin/rspec --pattern ./spec/\*\*/\*_spec.rb failed
  ERROR: Test "ruby2.3" failed. Exiting.
  dh_auto_install: dh_ruby --install 
/home/lamby/temp/cdt.20160305144845.uRMGQfzpXR/ruby-buff-config-1.0.0/debian/ruby-buff-config
 returned exit code 1
  debian/rules:15: 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
   `-


ruby-buff-config.1.0.0-1.unstable.amd64.log.txt.gz
Description: Binary data
--- End Message ---
--- Begin Message ---
Control: fixed -1 ruby-buff-config/1.0.1-2

The FTBFS you have reported does not apply to the version in
unstable, therefore closing.

-- 
 ,''`.  Christian Hofstaedtler 
: :' :  Debian Developer
`. `'   7D1A CFFA D9E0 806C 9C4C  D392 5C13 D6DB 9305 2E03
  ` End Message ---

Bug#816843: marked as done (ruby-varia-model: FTBFS: Failure/Error: expect(subject.attributes.dig('brooke.winsor')).to eql('rhode island'))

[Debian Bug Tracking System]

Your message dated Sun, 6 Mar 2016 10:25:56 -0300
with message-id <20160306132555.GA85368@sx>
and subject line Re: #816843: fixed in unstable already
has caused the Debian Bug report #816843,
regarding ruby-varia-model: FTBFS: Failure/Error: 
expect(subject.attributes.dig('brooke.winsor')).to eql('rhode island')
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.)


-- 
816843: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=816843
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: ruby-varia-model
Version: 0.4.0-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,

ruby-varia-model fails to build from source in unstable/amd64:

[..]
  
  All examples were filtered out; ignoring {:focus=>true}
  .F...FF...FF..FF..FF..F.FF..F..F
  
  Failures:
  
1) VariaModel ClassMethods ::attribute sets a default value if :default 
option is provided
   Failure/Error: expect(subject.attributes.dig('brooke.winsor')).to 
eql('rhode island')
 
 expected: "rhode island"
  got: nil
 
 (compared using eql?)
   # ./spec/unit/varia_model_spec.rb:44:in `block (4 levels) in '
  
2) VariaModel ClassMethods ::validate_kind_of success returns an array 
where the first element is ':ok'
   Failure/Error: expect(subject.validate_kind_of(types, model, 
key).first).to eql(:ok)
 
 expected: :ok
  got: :error
 
 (compared using eql?)
 
 Diff:
 @@ -1,2 +1,2 @@
 -:ok
 +:error
   # ./spec/unit/varia_model_spec.rb:174:in `block (5 levels) in '
  
3) VariaModel ClassMethods ::validate_kind_of success returns an array 
where the second element is a blank string
   Failure/Error: expect(subject.validate_kind_of(types, model, key)[1]).to 
be_blank
 expected `"Expected attribute: 'nested.one' to be a type of: 'String', 
'Buff::Boolean'".blank?` to return true, got false
   # ./spec/unit/varia_model_spec.rb:178:in `block (5 levels) in '
  
4) VariaModel ClassMethods ::validate_required passes validation if the 
value of the attribute is false
   Failure/Error: expect(subject.validate_required(model, key).first).to 
eql(:ok)
 
 expected: :ok
  got: :error
 
 (compared using eql?)
 
 Diff:
 @@ -1,2 +1,2 @@
 -:ok
 +:error
   # ./spec/unit/varia_model_spec.rb:229:in `block (4 levels) in '
  
5) VariaModel ClassMethods ::validate_required passes validation if the 
value of the attribute is not nil
   Failure/Error: expect(subject.validate_required(model, key).first).to 
eql(:ok)
 
 expected: :ok
  got: :error
 
 (compared using eql?)
 
 Diff:
 @@ -1,2 +1,2 @@
 -:ok
 +:error
   # ./spec/unit/varia_model_spec.rb:235:in `block (4 levels) in '
  
6) VariaModel ClassMethods ::validate_required success returns an array 
where the first element is ':ok'
   Failure/Error: expect(subject.validate_required(model, key).first).to 
eql(:ok)
 
 expected: :ok
  got: :error
 
 (compared using eql?)
 
 Diff:
 @@ -1,2 +1,2 @@
 -:ok
 +:error
   # ./spec/unit/varia_model_spec.rb:254:in `block (5 levels) in '
  
7) VariaModel ClassMethods ::validate_required success returns an array 
where the second element is a blank string
   Failure/Error: expect(subject.validate_required(model, key)[1]).to 
be_blank
 expected `"A value is required for attribute: 'nested.one'".blank?` to 
return true, got false
   # ./spec/unit/varia_model_spec.rb:258:in `block (5 levels) in '
  
8) VariaModel Validations validate type returns false if it fails validation
   Failure/Error: expect(subject).not_to be_valid
 expected `#<#:0x00028a9560 
@_attributes_=#>, @errors=#>.valid?` to return false, got true
   # ./spec/unit/varia_model_spec.rb:425:in `block (4 levels) in '
  
9) VariaModel Validations validate type adds an error if it fails validation
   Failure/Error: expect(subject.errors.size).to eq(1)
 
 expected: 1
  got: 0
 
 (compared using ==)
   # ./spec/unit/varia_model_spec.rb:431:in `block (4 levels) in '
  
10) VariaModel#get_attribute 

Bug#800266: marked as done (gpw: Please migrate a supported debhelper compat level)

[Debian Bug Tracking System]

Your message dated Sun, 06 Mar 2016 12:34:16 +
with message-id 
and subject line Bug#800266: fixed in gpw 0.0.19940601-9
has caused the Debian Bug report #800266,
regarding gpw: Please migrate a supported debhelper compat level
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.)


-- 
800266: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=800266
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: gpw
Severity: important
Usertags: deprecated-debhelper-compat-leq-3

Hi,

The package gpw is using a debhelper compat level of 3 or less
according to lintian.  These compat levels have been deprecated for
the past ~10 years and debhelper will remove support for them in the near
future (as declared in [1]).

 * Please migrate the package to a supported debhelper compat level.
   - Compat 9 is recommended
   - Compat 5 is the bare minimum (compat 4 will be removed soon as
 well)

 * If your package uses any of the following tools, please remove them
   from the rules files.  Neither of them does anything except warn
   about their deprecation.
   - dh_desktop
   - dh_scrollkeeper (deadline: January 1st 2016)
   - dh_suidregister
   - dh_undocumented

 * Please note that your package might have been flagged for using
   e.g. "DH_COMPAT=2 dh_foo ...".
   - This will still cause issues when the compat level is removed.

 * If the package has been relying on dh_install being lenient about
   missing files, please see "MIGRATING TO COMPAT 5 OR LATER" in [1].

 * Deadline: 
   - compat 1+2: November 1st 2015
   - compat 3: January 1st 2016

If you are using other deprecated debhelper features (such as omitting
the debian/compat file), please consider fixing those while you are at
it.

Thanks,
~Niels

[1] https://lists.debian.org/debian-devel/2015/09/msg00257.html
--- End Message ---
--- Begin Message ---
Source: gpw
Source-Version: 0.0.19940601-9

We believe that the bug you reported is fixed in the latest version of
gpw, 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 800...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Francesco Paolo Lovergine  (supplier of updated gpw 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: Sun, 06 Mar 2016 11:48:14 +0100
Source: gpw
Binary: gpw
Architecture: source amd64
Version: 0.0.19940601-9
Distribution: unstable
Urgency: medium
Maintainer: Francesco Paolo Lovergine 
Changed-By: Francesco Paolo Lovergine 
Description:
 gpw- Trigraph Password Generator
Closes: 651510 800266
Changes:
 gpw (0.0.19940601-9) unstable; urgency=medium
 .
   * Package revamped for current times.
 (closes: #800266)
   * Applied suggested patch to avoid inconsistent bi- and trigrams
 concatenations.
 (closes: #651510)
Checksums-Sha1:
 eeca5289e08b952947f5a8d186bc35d30ed0c56f 1723 gpw_0.0.19940601-9.dsc
 efbeaad0e9f29be78eceeb00014b7497664e6744 5096 gpw_0.0.19940601-9.debian.tar.xz
 fb48b94733ce46f088db885dc40e9c709746bdcc 5220 
gpw-dbgsym_0.0.19940601-9_amd64.deb
 8edbc228e2b8fae96e26866ac7d593198daa4774 16694 gpw_0.0.19940601-9_amd64.deb
Checksums-Sha256:
 709866dd0c9f8cfca9c1f153ead755aee3b7d5ffa30bea95236e2fdd05800c77 1723 
gpw_0.0.19940601-9.dsc
 ed982655dc007169c5c55b8aea59c3a662bd7c1090ef1615fb6e9236878afa1e 5096 
gpw_0.0.19940601-9.debian.tar.xz
 48478b38d71c00f3594134ece7b52aa1678244e2fca967e3fd46cb262f95c2de 5220 
gpw-dbgsym_0.0.19940601-9_amd64.deb
 c42f24a3104e8118980e0d8268b7ef81616359398ced6be3d8ac372043c1ad08 16694 
gpw_0.0.19940601-9_amd64.deb
Files:
 97b60e5ffc93778042d427ea9d856298 1723 utils optional gpw_0.0.19940601-9.dsc
 2fe654e0c41b90b3312f1eba7952b13f 5096 utils optional 
gpw_0.0.19940601-9.debian.tar.xz
 c14db8845ed29d272c313a6cc900c9b4 5220 debug extra 
gpw-dbgsym_0.0.19940601-9_amd64.deb
 fcdd27f40dc42b7924723ff361818c38 16694 utils optional 
gpw_0.0.19940601-9_amd64.deb

-BEGIN PGP SIGNATURE-
Version: GnuPG v1

iQIcBAEBAgAGBQJW3CD+AAoJEA8CpeEWNoakHQYP/2w1511vZxmFvwEl2pTEn5Ut
8F562T4JPPeCXgn8fX2+5ujolWJrEwXLP/x63KzufArlJFfJSf6j8k30+I82wK5j

Bug#816897: sbuild --build-dep-resolver=aptitude will install packages from untrusted sources

[Ansgar Burchardt]

Package: sbuild
Version: 0.68.0-1
Severity: serious
Tags: security

sbuild --build-dep-resolver=aptitude will install packages from
untrusted sources. I'm building a backports of dune-geometry in a
freshly created jessie-backports chroot. For this I added a local apt
repository

  deb file:///srv/apt/ansgar/pub jessie-backports main

to the chroot's sources.list (there is a bind mount setup too). The
signing key was *not* installed yet (as I forgot to do so).

Building the package with

  $ /usr/bin/sbuild -j8 -d jessie-backports -A \
--build-dep-resolver=aptitude dune-geometry_2.4.1-1~bpo8+1.dsc

made apt in the chroot complain as expected:

+---
| W: GPG error: file: jessie-backports InRelease: The following signatures
| couldn't be verified because the public key is not available:
| NO_PUBKEY 4618504DFB3AD1E0
+---

But to my surprise, the aptitude solver went on to install packages from there:

+---
| aptitude -y --without-recommends -o Dpkg::Options::=--force-confold
| -o Aptitude::CmdLine::Ignore-Trust-Violations=false [...]
| install sbuild-build-depends-dune-geometry-dummy:amd64
| [...]
| The following actions will resolve these dependencies:
|
|   Install the following packages:
| 1)  libdune-common-dev [2.4.1-1~bpo8+1 ()]
| [...]
| Selecting previously unselected package libdune-common-dev:amd64.
| Preparing to unpack .../libdune-common-dev_2.4.1-1~bpo8+1_amd64.deb ...
| Unpacking libdune-common-dev:amd64 (2.4.1-1~bpo8+1) ...
| [...]
| Setting up libdune-common-dev:amd64 (2.4.1-1~bpo8+1) ...
| [...]
| Package versions: [...] libdune-common-dev_2.4.1-1~bpo8+1 [...]
+---

I'm not sure if this is an issue with sbuild calling aptitude or with
aptitude. Feel free to reassign to aptitude (aptitude 0.6.11-1+b1 was
installed in the chroot).

(This was before the dune-common backport reached the archive.)

Ansgar

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

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

Versions of packages sbuild depends on:
ii  adduser 3.113+nmu3
ii  apt-utils   1.2.4
ii  libsbuild-perl  0.68.0-1
ii  perl5.22.1-7

Versions of packages sbuild recommends:
ii  debootstrap  1.0.79
ii  fakeroot 1.20.2-1

Versions of packages sbuild suggests:
pn  deborphan  
ii  wget   1.17.1-1+b1

-- no debconf information

Bug#815377: marked as done (mariadb-10.0: newly split out plugin packages need Breaks+Replaces: mariadb-server-10.0)

[Debian Bug Tracking System]

Your message dated Sun, 06 Mar 2016 12:00:51 +
with message-id 
and subject line Bug#815377: fixed in mariadb-10.0 10.0.24-2
has caused the Debian Bug report #815377,
regarding mariadb-10.0: newly split out plugin packages need Breaks+Replaces: 
mariadb-server-10.0
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.)


-- 
815377: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=815377
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: mariadb-10.0
Version: 10.0.23-3
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed your package fails to upgrade from
'jessie'.
It installed fine in 'jessie', 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 mariadb-plugin-mroonga.
  Preparing to unpack .../mariadb-plugin-mroonga_10.0.23-3_amd64.deb ...
  Unpacking mariadb-plugin-mroonga (10.0.23-3) ...
  dpkg: error processing archive 
/var/cache/apt/archives/mariadb-plugin-mroonga_10.0.23-3_amd64.deb (--unpack):
   trying to overwrite '/usr/lib/mysql/plugin/ha_mroonga.so', which is also in 
package mariadb-server-10.0 10.0.22-0+deb8u1
  dpkg-deb: error: subprocess paste was killed by signal (Broken pipe)
  Errors were encountered while processing:
   /var/cache/apt/archives/mariadb-plugin-mroonga_10.0.23-3_amd64.deb

Similarily for mariadb-plugin-spider and mariadb-plugin-tokudb.


cheers,

Andreas


mariadb-server-10.0=10.0.22-0+deb8u1_mariadb-plugin-mroonga=10.0.23-3.log.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
Source: mariadb-10.0
Source-Version: 10.0.24-2

We believe that the bug you reported is fixed in the latest version of
mariadb-10.0, 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.
Otto Kekäläinen  (supplier of updated mariadb-10.0 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 08:38:25 +0200
Source: mariadb-10.0
Binary: libmariadbd18 libmariadbd-dev mariadb-common mariadb-client-core-10.0 
mariadb-client-10.0 mariadb-server-core-10.0 mariadb-test mariadb-test-data 
mariadb-server-10.0 mariadb-server mariadb-client mariadb-plugin-connect 
mariadb-plugin-oqgraph mariadb-plugin-tokudb mariadb-plugin-mroonga 
mariadb-plugin-spider
Architecture: source amd64 all
Version: 10.0.24-2
Distribution: unstable
Urgency: low
Maintainer: Debian MySQL Maintainers 
Changed-By: Otto Kekäläinen 
Description:
 libmariadbd-dev - MariaDB embedded database, development files
 libmariadbd18 - MariaDB embedded database
 mariadb-client - MariaDB database client (metapackage depending on the latest 
vers
 mariadb-client-10.0 - MariaDB database client binaries
 mariadb-client-core-10.0 - MariaDB database core client binaries
 mariadb-common - MariaDB common metapackage
 mariadb-plugin-connect - Connect storage engine for MariaDB
 mariadb-plugin-mroonga - Mroonga storage engine for MariaDB
 mariadb-plugin-oqgraph - OQGraph storage engine for MariaDB
 mariadb-plugin-spider - Spider storage engine for MariaDB
 mariadb-plugin-tokudb - TokuDB storage engine for MariaDB
 mariadb-server - MariaDB database server (metapackage depending on the latest 
vers
 mariadb-server-10.0 - MariaDB database server binaries
 mariadb-server-core-10.0 - MariaDB database core server files
 mariadb-test - MariaDB database regression test suite
 mariadb-test-data - MariaDB database regression test suite - data files
Closes: 815377
Changes:
 mariadb-10.0 (10.0.24-2) unstable; urgency=low
 .
   * Make new plugin packages breaks+replaces mariadb-server-10.0 as
 the files used to reside there (Closes: #815377).
   * Disable main.delayed that has been confirmed to be a false positive
 caused by built platform 

Processed: bug 815292 is forwarded to https://lists.freedesktop.org/archives/libreoffice/2016-March/073560.html

[Debian Bug Tracking System]

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

> forwarded 815292 
> https://lists.freedesktop.org/archives/libreoffice/2016-March/073560.html
Bug #815292 [src:libreoffice] libreoffice: FTBFS on i386: test failure: 
testFlipAndRotateCustomShape::Import_Export_Import
Set Bug forwarded-to-address to 
'https://lists.freedesktop.org/archives/libreoffice/2016-March/073560.html'.
> 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#812459: python3-stem: fails to upgrade from 'testing' - trying to overwrite /usr/bin/tor-prompt

[Jérémy Bobbio]

Hi Donncha,

Donncha O'Cearbhaill:
> This package is marked for autoremoval on the 8th March and the bug has
> not received a response from the package maintainer.
> 
> I've attached an NMU patch which I think will resolve this issue.

Thanks for the patch! 

> diff -Nru python-stem-1.4.1b/debian/changelog 
> python-stem-1.4.1b/debian/changelog
> --- python-stem-1.4.1b/debian/changelog   2016-01-18 14:58:04.0 
> +0100
> +++ python-stem-1.4.1b/debian/changelog   2016-03-06 00:16:13.0 
> +0100
> @@ -1,3 +1,12 @@
> +python-stem (1.4.1b-2.1) unstable; urgency=medium
> +
> +  * Non-maintainer upload.
> +  * debian/rules: Use update-alternatives to select between
> +/usr/bin/tor-prompt for the Python 2 and Python 3 packages
> +(Closes: #812459).

I don't think alternatives are the solution to this. tor-prompt as provided
by python-stem or by python3-stem should be strictly equilavent in terms
of features. I can't imagine why would someone prefer to use the
Python 2 version when someone else would prefer the Python 3 one.

I think either tor-prompt should be moved to its own package, or only
kept in python3-stem (because Python 2 will have to go away one day). We
can make python-stem Depends on python3-stem to make sure that
tor-prompty will continue to be there on upgrade.

-- 
Lunar.''`. 
lu...@debian.org: :Ⓐ  :  # apt-get install anarchism
`. `'` 
  `-   


signature.asc
Description: Digital signature

Processed: severity

[Debian Bug Tracking System]

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

> severity 808393 normal
Bug #808393 [imapfilter] imapfilter stopped working with google
Severity set to 'normal' from 'grave'
> thanks
Stopping processing here.

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

Bug#808393: severity

[Sylvestre Ledru]

severity 808393 normal
thanks

sslv3 is a deprecated technology

https://blog.mozilla.org/security/2014/10/14/the-poodle-attack-and-the-end-of-ssl-3-0/

and the package still works for most of the imap provider.


In parallel, I am going to upload a new upstream release, maybe it will
fix your problem.

Sylvestre

Bug#816882: ruby-websocket-driver: must depend on ruby-websocket-extensions

[Hleb Valoshka]

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)