Bug#780676: Unable to purge
On Ma, 17 mar 15, 18:36:30, Erwan David wrote: Package: birdie Version: 1.1-5.1 Severity: normal There is no such package in Debian, please report any issues to where you obtained it from. Kind regards, Andrei -- http://wiki.debian.org/FAQsFromDebianUser Offtopic discussions among Debian users and developers: http://lists.alioth.debian.org/mailman/listinfo/d-community-offtopic http://nuvreauspam.ro/gpg-transition.txt signature.asc Description: Digital signature
Bug#795668: ITP: libdist-zilla-plugin-test-eol-perl -- Author tests making sure correct line endings are used
Package: wnpp Owner: intrigeri intrig...@debian.org Severity: wishlist X-Debbugs-CC: debian-de...@lists.debian.org, debian-p...@lists.debian.org * Package name: libdist-zilla-plugin-test-eol-perl Version : 0.18 Upstream Author : Florian Ragwitz r...@debian.org, Caleb Cushing xenoterrac...@gmail.com, Karen Etheridge et...@cpan.org * URL : https://metacpan.org/release/Dist-Zilla-Plugin-Test-EOL * License : Artistic or GPL-1+ Programming Lang: Perl Description : Author tests making sure correct line endings are used This is an extension of LDist::Zilla::Plugin::InlineFiles, providing the file Fxt/author/eol.t, a standard LTest::EOL test. The package will be maintained under the umbrella of the Debian Perl Group.
Bug#795677: ruby-hitimes: Non-determinstic FTBFS due to unreliable timing benchmarks in tests
Source: ruby-hitimes
Version: 1.2.1-2
Severity: serious
Justification: fails to build from source
Dear Maintainer,
ruby-hitimes non-deterministically fails to build from source due to
unreliable
timing benchmarks in tests:
[..]
7) Hitimes::TimedValueMetric can measure a block of code from an
instance
Failure/Error: t.duration.should be_within(0.004).of(0.15)
expected 0.156623768 to be within 0.004 of 0.15
# ./spec/timed_value_metric_spec.rb:125:in `block (2 levels) in
top (required)'
Deprecation Warnings:
Requiring `rspec/autorun` when running RSpec via the `rspec` command
is deprecated. Called from
/tmp/buildd/ruby-hitimes-1.2.1/spec/spec_helper.rb:7:in `top
(required)'.
Using `should` from rspec-expectations' old `:should` syntax without
explicitly enabling the syntax is deprecated. Use the new `:expect`
syntax or explicitly enable `:should` with `config.expect_with(:rspec)
{ |c| c.syntax = :should }` instead. Called from
/tmp/buildd/ruby-hitimes-1.2.1/spec/hitimes_spec.rb:8:in `block (2
levels) in top (required)'.
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.
2 deprecation warnings total
Finished in 7.67 seconds (files took 1.1 seconds to load)
130 examples, 7 failures
Failed examples:
rspec ./spec/timed_metric_spec.rb:69 # Hitimes::TimedMetric keeps
track of the max value
rspec ./spec/timed_metric_spec.rb:140 # Hitimes::TimedMetric#to_hash
has the right sum
rspec ./spec/timed_value_metric_spec.rb:53 # Hitimes::TimedValueMetric
calculates the rate of the counts
rspec ./spec/timed_value_metric_spec.rb:59 # Hitimes::TimedValueMetric
calculates the stddev of the durations
rspec ./spec/timed_value_metric_spec.rb:76 # Hitimes::TimedValueMetric
keeps track of the max value
rspec ./spec/timed_value_metric_spec.rb:88 # Hitimes::TimedValueMetric
keeps track of the sum of squares value
rspec ./spec/timed_value_metric_spec.rb:122 #
Hitimes::TimedValueMetric can measure a block of code from an instance
/usr/bin/ruby2.1 /usr/bin/rspec --pattern ./spec/\*\*/\*_spec.rb
failed
ERROR: Test ruby2.1 failed. Exiting.
dh_auto_install: dh_ruby --install
/tmp/buildd/ruby-hitimes-1.2.1/debian/ruby-hitimes returned exit code
1
debian/rules:15: recipe for target 'binary' failed
make: *** [binary] Error 1
dpkg-buildpackage: error: fakeroot debian/rules binary gave error exit
status 2
[..]
The full build log is attached or can be viewed here:
https://reproducible.debian.net/logs/unstable/amd64/ruby-hitimes_1.2.1-2.build1.log.gz
Regards,
--
,''`.
: :' : Chris Lamb
`. `'` la...@debian.org / chris-lamb.co.uk
`-
I: using fakeroot in build.
I: pbuilder: network access will be disabled during build
I: Current time: Thu Jul 30 11:32:44 GMT+12 2015
I: pbuilder-time-stamp: 1438299164
I: Building the build Environment
I: extracting base tarball [/var/cache/pbuilder/unstable-reproducible-base.tgz]
I: creating local configuration
I: copying local configuration
I: mounting /proc filesystem
I: mounting /run/shm filesystem
I: mounting /dev/pts filesystem
I: Mounting /dev/shm
I: Mounting /sys
I: policy-rc.d already exists
I: Installing the build-deps
- Attempting to satisfy build-dependencies
- Creating pbuilder-satisfydepends-dummy package
Package: pbuilder-satisfydepends-dummy
Version: 0.invalid.0
Architecture: amd64
Maintainer: Debian Pbuilder Team pbuilder-ma...@lists.alioth.debian.org
Description: Dummy package to satisfy dependencies with aptitude - created by
pbuilder
This package was created automatically by pbuilder to satisfy the
build-dependencies of the package being currently built.
Depends: debhelper (= 7.0.50~), gem2deb (= 0.7.4~), ruby-rspec, ruby-simplecov
dpkg-deb: building package 'pbuilder-satisfydepends-dummy' in
'/tmp/satisfydepends-aptitude/pbuilder-satisfydepends-dummy.deb'.
Selecting previously unselected package pbuilder-satisfydepends-dummy.
(Reading database ... 20233 files and directories currently installed.)
Preparing to unpack .../pbuilder-satisfydepends-dummy.deb ...
Unpacking pbuilder-satisfydepends-dummy (0.invalid.0) ...
dpkg: pbuilder-satisfydepends-dummy: dependency problems, but configuring
anyway as you requested:
pbuilder-satisfydepends-dummy depends on gem2deb (= 0.7.4~); however:
Package gem2deb is not installed.
pbuilder-satisfydepends-dummy depends on ruby-rspec; however:
Package ruby-rspec is not installed.
pbuilder-satisfydepends-dummy depends on ruby-simplecov; however:
Package ruby-simplecov is not installed.
Setting up pbuilder-satisfydepends-dummy (0.invalid.0) ...
Reading package lists...
Building dependency tree...
Reading state information...
Initializing package
Bug#791016: ctpp2: ftbfs, and library transition is needed when GCC 5 is the default
Control: tag -1 +pending Err. I forgot that being a DM I can't upload package with new packaes. So I will wait for some one to upload the package for me. Changes are already on collab-maint repo. Cheers, signature.asc Description: PGP signature
Bug#756253: Upgrade from 2.02~beta2-10 to 2.02~beta2-11 left grub unbootable
Am Mittwoch, den 21.01.2015, 00:58 + schrieb Steve McIntyre: On Wed, Jan 21, 2015 at 06:55:05AM +0900, Mike Hommey wrote: On Tue, Jan 20, 2015 at 01:44:37PM +, Steve McIntyre wrote: The automatic setup of grub-install calling efibootmgr won't be touching the grub entry at all - it's set up to only play with debian entries. So that should be safe. Was it always a debian entry? As far back as I remember, yes. But then comes the second thing: when I reboot, the debian entry is lost. Poof, disappeared. And I do wonder if the initial problem is not related to that. That is still happening? Can you successfully re-create it each time? It happens reliably. efibootmgr displays it, but after a reboot, it's gone. OK, now that's just *weird* and suggests a firmware bug to me. I'd be tempted to try and create an exact copy with another name and see how that works, but I'm struggling to understand what's going on here now! Is still a problem or got it somehow solved?
Bug#772795: grub installation fails on a fakeraid/sataraid/dmraid system
Am Donnerstag, den 11.12.2014, 12:49 +0530 schrieb Pirate Praveen: package: grub-pc version: 1.99-27+deb7u2 severity: critical I had to spend a lot of time researching on the internet to finally find this https://wiki.debian.org/DebianInstaller/SataRaid and install grub manually. This was wheezy 7.7.0 DVD 1. I don't know if debian installer can detect a sataraid system and load dm-raid module manually (I'll open another bug for that). But grub installation should not fail when dmraid=true. Instead of suggesting to install on /dev/mapper grub should choose the correct devise like /dev/mapper/isw_bdfjhfbiei_Volume1 when dmraid=true is present in the kernel command line. Server model is Dell PowerEdge T20 and SATA controller is Intel C226 chipset. Is this still a problem with jessie or got it solved?
Bug#712953: sysvinit: System Restarts Instead of Powering Off
I have ran into a similar issue. My Lenovo Flex 15-2 is currently running Debian Jessie amd64 Stable Release. When I issue the shutdown command either via the menus in gnome or gym, it goes through the process of shutting down and powers off. Approximately 5 seconds later, the laptop powers back up and continues with the booting process via grub. Mind you the computer has not been touched since issuing the shutdown command. The only way I have been able to get the laptop to shutdown and power down successfully is by having a USB mouse connected. I’m thinking that the installation has some corrupted files and I am thinking that I just need to do a clean wipe and reinstall, but I’m hoping that it’s something much simpler. I ask for advice to which direction to go as I am a novice.
Bug#795656: python-imaplib2: wrong substitution variable for python3-imaplib2 Depends
tags 795656 + confirmed pending
thanks
On 16/08/15 03:02, Logan Rosen wrote:
Package: python-imaplib2
Version: 2.42-1
Severity: normal
Hi Ulises,
I wanted to let you know that the Depends field for python3-imaplib2 uses
${python:Depends} instead of ${python3:Depends}, which means that it is not
properly depending upon the necessary packages for the Python 3 module.
Hi Logan!
Definitely missed that. Much appreciated!
Cheers,
Dererk
--
BOFH excuse #163:
no any key on keyboard
signature.asc
Description: OpenPGP digital signature
Bug#795665: dgit doesn't work with symlinked tarballs
On 16/08/15 09:39, Andrew Shadura wrote: $ ls ../blkreplay_1.0.orig.tar.gz -l lrwxrwxrwx 1 andrew andrew 21 Aug 16 09:30 ../blkreplay_1.0.orig.tar.gz - blkreplay-v1.0.tar.gz $ git reset --hard HEAD is now at ad6cd93 Update the changelog. $ dgit build dpkg-buildpackage: source package blkreplay dpkg-buildpackage: source version 1.0-3 dpkg-buildpackage: source distribution unstable dpkg-buildpackage: source changed by Andrew Shadura andre...@debian.org dpkg-buildpackage: host architecture i386 fakeroot debian/rules clean dh clean --with autoreconf dh_testdir dh_auto_clean dh_autoreconf_clean dh_clean Format `3.0 (quilt)', checking/updating patch stack blkreplay_1.0.orig.tar.gz No such file or directory at /usr/bin/dgit line 2612. $ Also, with dgit 1.2 I have this: $ git reset --hard HEAD is now at ad6cd93 Update the changelog. $ git diff $ dgit build length() used on @ARGV (did you mean scalar(@ARGV)?) at /usr/bin/dgit line 3164. Format `3.0 (quilt)', checking/updating patch stack blkreplay_1.0.orig.tar.gz No such file or directory at /usr/bin/dgit line 2786. -- Cheers, Andrew signature.asc Description: OpenPGP digital signature
Bug#792864: ITA: node-minimist -- Argument options parsing for Node.js
Control: retitle 792864 RFA: node-minimist -- Argument options parsing for Node.js Control: owner 792864 ! I am happy to become an uploader for node-minimist and maintain the package within the Debian Javascript Team. Regards, Ross signature.asc Description: OpenPGP digital signature
Bug#773787: hot: hot.hs:74:51-71: Non-exhaustive patterns in lambda
Hi, Am Sonntag, den 16.08.2015, 08:05 + schrieb Clint Adams: On Tue, Dec 23, 2014 at 11:04:15AM +0100, Joachim Breitner wrote: I get $ cat ../build-exp/haskell-auto-update_0.1.2-1_amd64.changes|hot dearmor hot (hopenpgp-tools) 0.13 Copyright (C) 2012-2014 Clint Adams hot comes with ABSOLUTELY NO WARRANTY. This is free software, and you are welcome to redistribute it under certain conditions. hot: hot.hs:74:51-71: Non-exhaustive patterns in lambda with the attached file. You just want it to output the binary signature packet? it’s been a while, but I believe I wanted the PGP signature removed, so that grep-dctrl would process the file. Greetings, Joachim -- Joachim nomeata Breitner Debian Developer nome...@debian.org | ICQ# 74513189 | GPG-Keyid: F0FBF51F JID: nome...@joachim-breitner.de | http://people.debian.org/~nomeata signature.asc Description: This is a digitally signed message part
Bug#795659: pagekite: please make the build reproducible
Hi,
Updated patch attached so it does not FTBFS if SOURCE_DATE_EPOCH env is
not set. Thanks to Val Lorentz.
Regards,
--
,''`.
: :' : Chris Lamb
`. `'` la...@debian.org / chris-lamb.co.uk
`-
diff --git a/pagekite/compat.py b/pagekite/compat.py
index fe3da9e..2537953 100755
--- a/pagekite/compat.py
+++ b/pagekite/compat.py
@@ -50,7 +50,7 @@ try:
import datetime
ts_to_date = datetime.datetime.fromtimestamp
def ts_to_iso(ts=None):
-return datetime.datetime.fromtimestamp(ts).isoformat()
+return datetime.datetime.utcfromtimestamp(ts).isoformat()
except ImportError:
ts_to_date = str
ts_to_iso = str
diff --git a/pagekite/manual.py b/pagekite/manual.py
index 5ff20f1..13399c7 100755
--- a/pagekite/manual.py
+++ b/pagekite/manual.py
@@ -2,6 +2,7 @@
The program manual!
+import os
import re
import time
@@ -447,7 +448,7 @@ def MAN(pname=None):
.TH PAGEKITE 1 %s https://pagekite.net/; Awesome Commands
.nh
.ad l
-) % ts_to_iso(time.time()).split('T')[0]
+) % ts_to_iso(float(os.environ.get('SOURCE_DATE_EPOCH',
time.time(.split('T')[0]
for h, section, text in MANUAL_TOC:
man += ('.%s %s\n\n%s\n\n'
) % (h, h == 'SH' and section.upper() or section,
Bug#795652: ITP: kubernetes -- cluster manager for Docker containers
On Sunday 16 August 2015 10:41:40 Paul R. Tagliamonte wrote: Could we team maintain this in the Docker packaging team? Absolutely. I'm looking forward to work together with you. :) I'm not a member yet but I've just sent join request through Alioth. Anyway I'm planning to put packaging to collab-maint if you don't mind... -- All the best, Dmitry Smirnov. --- For every complex problem there is an answer that is clear, simple, and wrong. -- H. L. Mencken signature.asc Description: This is a digitally signed message part.
Bug#795679: set-crontab-perl: FTBFS with perl 5.22 in experimental (MakeMaker changes)
Source: set-crontab-perl Version: 1.02-1 Severity: important User: debian-p...@lists.debian.org Usertags: perl-5.22-transition makemaker-prefix Tags: sid stretch This package FTBFS with perl 5.22.0-2, which removed support for a long- obsolete way of overriding PREFIX when calling 'make install' with ExtUtils::MakeMaker, as described in the lintian tag debian-rules-makemaker-prefix-is-deprecated[1] and the Debian Perl policy[2]: /usr/bin/make install PREFIX=/«PKGBUILDDIR»/debian/libset-crontab-perl/usr; \ make[1]: Entering directory '/«PKGBUILDDIR»' Manifying 1 pod document ERROR: Can't create '/usr/share/man/man3' Do not have write permissions on '/usr/share/man/man3' The fix is to use DESTDIR instead of PREFIX; please see the lintian `description for examples. Alternatively, newer versions of debhelper can automatically call make install with the correct arguments when using the dh7 style rules files. This bug will become release critical nearer the time of the perl 5.22 migration, expected during the (northern hemisphere) summer. Cheers, Dominic. [1] https://lintian.debian.org/tags/debian-rules-makemaker-prefix-is-deprecated.html [2] https://www.debian.org/doc/packaging-manuals/perl-policy/ch-module_packages.html#s-vendor_install
Bug#791257: qscintilla2: library transition may be needed when GCC 5 is the default
On Sat, Aug 15, 2015 at 22:05:51 -0400, Scott Kitterman wrote: Please let me know when I can go ahead. Go ahead. Cheers, Julien signature.asc Description: Digital signature
Bug#795664: ruby-handlebars-assets: FTBFS: uninitialized constant MiniTest::Test (NameError)
Source: ruby-handlebars-assets Version: 0.20.1-5 Severity: serious Justification: fails to build from source Dear Maintainer, ruby-handlebars-assets fails to build from source on unstable/amd64: [..] ┌──┐ │ Run tests for ruby2.1 from debian/ruby-tests.rake │ └──┘ RUBYLIB=/tmp/buildd/ruby-handlebars-assets-0.20.1/debian/ruby-handlebars-assets/usr/lib/ruby/vendor_ruby:. rake2.1 -f debian/ruby-tests.rake /usr/lib/ruby/2.1.0/minitest/unit.rb:26:in `const_missing': uninitialized constant MiniTest::Test (NameError) from /tmp/buildd/ruby-handlebars-assets-0.20.1/test/handlebars_assets/compiling_test.rb:4:in `module:HandlebarsAssets' from /tmp/buildd/ruby-handlebars-assets-0.20.1/test/handlebars_assets/compiling_test.rb:3:in `top (required)' from /usr/lib/ruby/2.1.0/rubygems/core_ext/kernel_require.rb:55:in `require' from /usr/lib/ruby/2.1.0/rubygems/core_ext/kernel_require.rb:55:in `require' from /usr/lib/ruby/2.1.0/rake/rake_test_loader.rb:15:in `block in main' from /usr/lib/ruby/2.1.0/rake/rake_test_loader.rb:4:in `select' from /usr/lib/ruby/2.1.0/rake/rake_test_loader.rb:4:in `main' rake aborted! Command failed with status (1): [ruby -Ilib:test -I/usr/lib/ruby/2.1.0 /usr/lib/ruby/2.1.0/rake/rake_test_loader.rb test/handlebars_assets/compiling_test.rb test/handlebars_assets/hamlbars_test.rb test/handlebars_assets/slimbars_test.rb test/handlebars_assets/tilt_handlebars_test.rb ] Tasks: TOP = default = test (See full trace by running task with --trace) ERROR: Test ruby2.1 failed. Exiting. dh_auto_install: dh_ruby --install /tmp/buildd/ruby-handlebars-assets-0.20.1/debian/tmp returned exit code 1 debian/rules:15: recipe for target 'binary' failed make: *** [binary] Error 1 dpkg-buildpackage: error: fakeroot debian/rules binary gave error exit status 2 [..] The full build log is attached or can be viewed here: https://reproducible.debian.net/logs/unstable/amd64/ruby-handlebars-assets_0.20.1-5.build1.log.gz Regards, -- ,''`. : :' : Chris Lamb `. `'` la...@debian.org / chris-lamb.co.uk `- I: using fakeroot in build. I: pbuilder: network access will be disabled during build I: Current time: Thu Jul 30 13:02:58 GMT+12 2015 I: pbuilder-time-stamp: 1438304578 I: Building the build Environment I: extracting base tarball [/var/cache/pbuilder/unstable-reproducible-base.tgz] I: creating local configuration I: copying local configuration I: mounting /proc filesystem I: mounting /run/shm filesystem I: mounting /dev/pts filesystem I: Mounting /dev/shm I: Mounting /sys I: policy-rc.d already exists I: Installing the build-deps - Attempting to satisfy build-dependencies - Creating pbuilder-satisfydepends-dummy package Package: pbuilder-satisfydepends-dummy Version: 0.invalid.0 Architecture: amd64 Maintainer: Debian Pbuilder Team pbuilder-ma...@lists.alioth.debian.org Description: Dummy package to satisfy dependencies with aptitude - created by pbuilder This package was created automatically by pbuilder to satisfy the build-dependencies of the package being currently built. Depends: debhelper (= 7.0.50~), gem2deb (= 0.7.5~), ruby-slim, ruby-execjs, ruby-tilt, ruby-multi-json, ruby-sprockets, ruby-haml, libjs-handlebars (= 2:0.20.1~), libjs-handlebars.runtime (= 2:0.20.1~) dpkg-deb: building package 'pbuilder-satisfydepends-dummy' in '/tmp/satisfydepends-aptitude/pbuilder-satisfydepends-dummy.deb'. Selecting previously unselected package pbuilder-satisfydepends-dummy. (Reading database ... 20233 files and directories currently installed.) Preparing to unpack .../pbuilder-satisfydepends-dummy.deb ... Unpacking pbuilder-satisfydepends-dummy (0.invalid.0) ... dpkg: pbuilder-satisfydepends-dummy: dependency problems, but configuring anyway as you requested: pbuilder-satisfydepends-dummy depends on gem2deb (= 0.7.5~); however: Package gem2deb is not installed. pbuilder-satisfydepends-dummy depends on ruby-slim; however: Package ruby-slim is not installed. pbuilder-satisfydepends-dummy depends on ruby-execjs; however: Package ruby-execjs is not installed. pbuilder-satisfydepends-dummy depends on ruby-tilt; however: Package ruby-tilt is not installed. pbuilder-satisfydepends-dummy depends on ruby-multi-json; however: Package ruby-multi-json is not installed. pbuilder-satisfydepends-dummy depends on ruby-sprockets; however: Package ruby-sprockets is not installed. pbuilder-satisfydepends-dummy depends on ruby-haml; however: Package ruby-haml is not installed. pbuilder-satisfydepends-dummy depends on libjs-handlebars (= 2:0.20.1~); however: Package libjs-handlebars is not installed.
Bug#795666: vagrant: Vagrant 1.7.2 not compatible with Virtualbox 5
Package: vagrant Version: 1:1.7.4 Severity: important Dear Maintainer, * What led up to the situation? The current version of Virtualbox is not compatible with Vagrant. I get this: The provider 'virtualbox' that was requested to back the machine 'default' is reporting that it isn't usable on this system. The reason is shown below: Vagrant has detected that you have a version of VirtualBox installed that is not supported. Please install one of the supported versions listed below to use Vagrant: 4.0, 4.1, 4.2, 4.3 The provider 'virtualbox' that was requested to back the machine 'default' is reporting that it isn't usable on this system. The reason is shown below: Vagrant has detected that you have a version of VirtualBox installed that is not supported. Please install one of the supported versions listed below to use Vagrant: 4.0, 4.1, 4.2, 4.3 * What exactly did you do (or not do) that was effective (or ineffective)? I tried: sudo apt-get purge virtualbox-dkms ; sudo apt-get install virtualbox-dkms as well as, sudo apt-get install linux-headers-$(uname -r) to make sure I had the kernel headers ... I did. In the end I just got the deb package from upstream (version 1.7.4). So I suppose this bug is in two parts a wishlist item and compatiblilty issue. Please can you upgrade to the latest vagrant package. Kind Regards Brent Clark -- System Information: Debian Release: stretch/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.1.0-1-amd64 (SMP w/4 CPU cores) Locale: LANG=en_ZA.UTF-8, LC_CTYPE=en_ZA.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) -- Configuration Files: /etc/bash_completion.d/vagrant f892ce45189973fad3399f5f15d9bc8b [Errno 2] No such file or directory: u'/etc/bash_completion.d/vagrant f892ce45189973fad3399f5f15d9bc8b' -- no debconf information
Bug#795665: dgit doesn't work with symlinked tarballs
Package: dgit Version: 1.0 Severity: normal How to reproduce: Clone git://git.collabora.com/git/blkreplay, checkout master. $ pwd /home/andrew/maintain/blkreplay $ rm -f ../blkreplay_1.0.orig.tar.gz ../blkreplay-v1.0.tar.gz $ uscan --verbose --force -- Scanning for watchfiles in . -- Found watchfile in ./debian -- In debian/watch, processing watchfile line: opts=filenamemangle=s/.*\/(.*)$/blkreplay-$1/i,uversionmangle=s/-rc(\d*)/~rc$1/ https://github.com/schoebel/blkreplay/tags /schoebel/blkreplay/archive/v(\d.*).tar.gz -- Found the following matching hrefs: /schoebel/blkreplay/archive/v1.0.tar.gz (1.0) /schoebel/blkreplay/archive/v1.0-rc8.tar.gz (1.0~rc8) /schoebel/blkreplay/archive/v1.0-rc7.tar.gz (1.0~rc7) /schoebel/blkreplay/archive/v1.0-rc6.tar.gz (1.0~rc6) /schoebel/blkreplay/archive/v1.0-rc5.tar.gz (1.0~rc5) /schoebel/blkreplay/archive/v1.0-rc4.tar.gz (1.0~rc4) /schoebel/blkreplay/archive/v1.0-rc3.tar.gz (1.0~rc3) /schoebel/blkreplay/archive/v1.0-rc2.tar.gz (1.0~rc2) Newest version on remote site is 1.0, local version is 1.0 = Package is up to date Newest version on remote site is 1.0, local version is 1.0 = Forcing download as requested -- Downloading updated package blkreplay-v1.0.tar.gz -- Checking for common possible upstream OpenPGP signatures -- Successfully downloaded updated package blkreplay-v1.0.tar.gz -- Successfully symlinked ../blkreplay-v1.0.tar.gz to ../blkreplay_1.0.orig.tar.gz. -- Scan finished $ ls ../blkreplay_1.0.orig.tar.gz -l lrwxrwxrwx 1 andrew andrew 21 Aug 16 09:30 ../blkreplay_1.0.orig.tar.gz - blkreplay-v1.0.tar.gz $ git reset --hard HEAD is now at ad6cd93 Update the changelog. $ dgit build dpkg-buildpackage: source package blkreplay dpkg-buildpackage: source version 1.0-3 dpkg-buildpackage: source distribution unstable dpkg-buildpackage: source changed by Andrew Shadura andre...@debian.org dpkg-buildpackage: host architecture i386 fakeroot debian/rules clean dh clean --with autoreconf dh_testdir dh_auto_clean dh_autoreconf_clean dh_clean Format `3.0 (quilt)', checking/updating patch stack blkreplay_1.0.orig.tar.gz No such file or directory at /usr/bin/dgit line 2612. $ -- System Information: Debian Release: stretch/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'stable'), (1, 'experimental') Architecture: i386 (i686) Kernel: Linux 4.0.0-1-686-pae (SMP w/4 CPU cores) Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8) (ignored: LC_ALL set to en_GB.UTF-8) Shell: /bin/sh linked to /bin/mksh Init: sysvinit (via /sbin/init) Versions of packages dgit depends on: ii ca-certificates20141019 ii coreutils 8.23-4 ii curl 7.42.1-2 ii devscripts 2.15.4 ii dpkg-dev 1.17.22 ii dput-ng [dput] 1.9 ii git [git-core] 1:2.1.4-2.1 ii git-core 1:2.1.4-2.1 ii libdigest-sha-perl 5.95-2 ii libdpkg-perl 1.17.22 ii libjson-perl 2.90-1 ii libwww-perl6.08-1 ii perl [libdigest-sha-perl] 5.20.2-4 ii realpath 8.23-4 Versions of packages dgit recommends: ii openssh-client [ssh-client] 1:6.7p1-6 Versions of packages dgit suggests: pn sbuild none -- no debconf information
Bug#790991: transition: cal3d (libcal3d12v5)
2015-08-16 0:43 GMT+01:00 Simon McVittie s...@debian.org: retitle 790991 transition: cal3d (libcal3d12v5) severity 790991 normal reassign 790991 release.debian.org user release.debian@packages.debian.org usertags 790991 + transition forwarded 790991 https://release.debian.org/transitions/html/auto-cal3d.html thanks On Fri, 14 Aug 2015 at 15:54:38 +0100, Manuel A. Fernandez Montecelo wrote: Uploaded changes to experimental. As Julien clarified in https://lists.debian.org/debian-release/2015/08/msg00426.html, I believe this is ready for upload to unstable whenever you want. There are only two reverse dependencies. crystalspace is not in testing and FTBFS anyway, so I think that one can be disregarded. soya has no other C++ build-dependencies, so it is probably ready to be queued up as soon as the updated cal3d gets to unstable: nmu soya_0.15~rc1-10 . ALL . -m 'Rebuild with libcal3d12v5' dw soya_0.15~rc1-10 . ALL . -m 'libcal3d12v5' Thanks, I am a bit behind on my reading of the mailing lists. Uploaded to unstable now. -- Manuel A. Fernandez Montecelo manuel.montez...@gmail.com
Bug#795667: Suppress hardening-{no-relro,no-fortify-functions}
Package: lintian
Version: 2.5.33
Severity: normal
Tags: patch
From the patch description:
[PATCH] Suppress hardening-{no-relro,no-fortify-functions} for Go binaries.
The Go compiler (gc) does not currently support these features, so don’t
warn about them on _every_ binary which is implemented in Go.
-- System Information:
Debian Release: stretch/sid
APT prefers testing
APT policy: (990, 'testing')
Architecture: amd64 (x86_64)
Kernel: Linux 4.0.0-2-amd64 (SMP w/8 CPU cores)
Locale: LANG=de_DE.UTF-8, 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 lintian depends on:
ii binutils 2.25-10
ii bzip2 1.0.6-8
ii diffstat 1.58-1
ii file 1:5.22+15-2
ii gettext0.19.4-1
ii hardening-includes 2.7
ii intltool-debian0.35.0+20060710.2
ii libapt-pkg-perl0.1.29+b2
ii libarchive-zip-perl1.48-1
ii libclass-accessor-perl 0.34-1
ii libclone-perl 0.38-1
ii libdpkg-perl 1.18.1
ii libemail-valid-perl1.196-1
ii libfile-basedir-perl 0.07-1
ii libipc-run-perl0.94-1
ii liblist-moreutils-perl 0.413-1
ii libparse-debianchangelog-perl 1.2.0-4
ii libtext-levenshtein-perl 0.12-1
ii libtimedate-perl 2.3000-2
ii liburi-perl1.64-1
ii man-db 2.7.0.2-5
ii patchutils 0.3.4-1
ii perl [libdigest-sha-perl] 5.20.2-6
ii t1utils1.38-4
ii xz-utils 5.1.1alpha+20120614-2.1
Versions of packages lintian recommends:
ii dpkg1.18.1
pn libperlio-gzip-perl none
ii perl5.20.2-6
ii perl-modules [libautodie-perl] 5.20.2-6
Versions of packages lintian suggests:
pn binutils-multiarch none
ii dpkg-dev 1.18.1
ii libhtml-parser-perl3.71-2
ii libtext-template-perl 1.46-1
pn libyaml-perl none
-- no debconf information
From 87e1d19a9cb2dfdfd1b23108bdff89d264102a3c Mon Sep 17 00:00:00 2001
From: Michael Stapelberg stapelb...@debian.org
Date: Sun, 16 Aug 2015 09:52:24 +0200
Subject: [PATCH] Suppress hardening-{no-relro,no-fortify-functions} for Go
binaries.
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit
The Go compiler (gc) does not currently support these features, so don’t
warn about them on _every_ binary which is implemented in Go.
---
checks/binaries.pm | 5 +
1 file changed, 5 insertions(+)
diff --git a/checks/binaries.pm b/checks/binaries.pm
index 1ad6282..3542611 100644
--- a/checks/binaries.pm
+++ b/checks/binaries.pm
@@ -547,6 +547,11 @@ sub run {
if ($flags) {
foreach my $t (@{$info-hardening_info-{$fname}}) {
my $tag = hardening-$t;
+# Binaries built by the Go compiler do not support all
+# hardening measures.
+next if ($t eq 'no-relro' ||
+ $t eq 'no-fortify-functions')
+ $built_with_golang;
tag $tag, $file if $flags-{$tag};
}
}
--
2.1.4
Bug#794483: wget: German translation: format string written to console
tags 794483 + moreinfo thanks Hello Simon, Am Montag, den 03.08.2015, 16:47 +0200 schrieb Simon Richter: after fetching a file from FTP with the -c option, I was shown the message Die Datei »%s« ist geholt worden. This appears to be an error in the translation, apparently fixed up to avoid dereferencing an invalid pointer. I tried to reproduce your report but I couldn't. Can you give to an example? --8-- $ wget -c ftp://cdimage.debian.org/debian-cd/current/multi-arch/iso-cd/debian-8.1.0-amd64-i386-netinst.iso --2015-08-16 10:27:03-- ftp://cdimage.debian.org/debian-cd/current/multi-arch/iso-cd/debian-8.1.0-amd64-i386-netinst.iso = »debian-8.1.0-amd64-i386-netinst.iso« Auflösen des Hostnamens »cdimage.debian.org (cdimage.debian.org)« … 2001:6b0:e:2018::165, 2001:6b0:e:2018::173, 130.239.18.173, ... Verbindungsaufbau zu cdimage.debian.org (cdimage.debian.org)|2001:6b0:e:2018::165|:21 … verbunden. Anmelden als anonymous … Angemeldet! == SYST ... fertig.== PWD ... fertig. == TYPE I ... fertig. == CWD (1) /debian-cd/current/multi-arch/iso-cd ... fertig. == SIZE debian-8.1.0-amd64-i386-netinst.iso ... 581959680 == EPSV ... fertig.== REST 326482088 ... fertig. == RETR debian-8.1.0-amd64-i386-netinst.iso ... fertig. Länge: 581959680 (555M), 255477592 (244M) sind noch übrig (unmaßgeblich) debian-8.1.0-amd64- 100%[=] 555,00M 4,53MB/s in 44s 2015-08-16 10:27:48 (5,48 MB/s) - »debian-8.1.0-amd64-i386-netinst.iso« gespeichert [581959680] $ wget -c ftp://cdimage.debian.org/debian-cd/current/multi-arch/iso-cd/debian-8.1.0-amd64-i386-netinst.iso --2015-08-16 10:32:17-- ftp://cdimage.debian.org/debian-cd/current/multi-arch/iso-cd/debian-8.1.0-amd64-i386-netinst.iso = »debian-8.1.0-amd64-i386-netinst.iso« Auflösen des Hostnamens »cdimage.debian.org (cdimage.debian.org)« … 2001:6b0:e:2018::173, 2001:6b0:e:2018::165, 130.239.18.165, ... Verbindungsaufbau zu cdimage.debian.org (cdimage.debian.org)|2001:6b0:e:2018::173|:21 … verbunden. Anmelden als anonymous … Angemeldet! == SYST ... fertig.== PWD ... fertig. == TYPE I ... fertig. == CWD (1) /debian-cd/current/multi-arch/iso-cd ... fertig. == SIZE debian-8.1.0-amd64-i386-netinst.iso ... 581959680 Die Datei ist bereits geholt worden. 2015-08-16 10:32:17 (0,00 B/s) - »debian-8.1.0-amd64-i386-netinst.iso« gespeichert [581959680] --8-- -- Noël Köthe noel debian.org Debian GNU/Linux, www.debian.org signature.asc Description: This is a digitally signed message part
Bug#795678: ruby-rspec-longrun: FTBFS: undefined method `cyan' for class `RSpec::Longrun::Formatter' (NameError)
Source: ruby-rspec-longrun
Version: 1.0.1-1
Severity: serious
Justification: fails to build from source
Dear Maintainer,
ruby-rspec-longrun fails to build from source on unstable/amd64:
[..]
┌──┐
│ Run tests for ruby2.1 from debian/ruby-tests.rake
│
└──┘
RUBYLIB=/tmp/buildd/ruby-rspec-longrun-1.0.1/debian/ruby-rspec-longrun/usr/lib/ruby/vendor_ruby:.
rake2.1 -f debian/ruby-tests.rake
/usr/bin/ruby2.1 /usr/bin/rspec --pattern
spec/\*\*\{,/\*/\*\*\}/\*_spec.rb
/tmp/buildd/ruby-rspec-longrun-1.0.1/lib/rspec/longrun/formatter.rb:55:in
`alias_method': undefined method `cyan' for class
`RSpec::Longrun::Formatter' (NameError)
from
/tmp/buildd/ruby-rspec-longrun-1.0.1/lib/rspec/longrun/formatter.rb:55:in
`alias_missing_method'
from
/tmp/buildd/ruby-rspec-longrun-1.0.1/lib/rspec/longrun/formatter.rb:59:in
`class:Formatter'
from
/tmp/buildd/ruby-rspec-longrun-1.0.1/lib/rspec/longrun/formatter.rb:6:in
`module:Longrun'
from
/tmp/buildd/ruby-rspec-longrun-1.0.1/lib/rspec/longrun/formatter.rb:4:in
`module:RSpec'
from
/tmp/buildd/ruby-rspec-longrun-1.0.1/lib/rspec/longrun/formatter.rb:3:in
`top (required)'
from
/usr/lib/ruby/2.1.0/rubygems/core_ext/kernel_require.rb:55:in
`require'
from
/usr/lib/ruby/2.1.0/rubygems/core_ext/kernel_require.rb:55:in
`require'
from
/tmp/buildd/ruby-rspec-longrun-1.0.1/lib/rspec/longrun.rb:2:in
`top (required)'
from
/usr/lib/ruby/2.1.0/rubygems/core_ext/kernel_require.rb:55:in
`require'
from
/usr/lib/ruby/2.1.0/rubygems/core_ext/kernel_require.rb:55:in
`require'
from
/usr/lib/ruby/vendor_ruby/rspec/core/configuration.rb:1280:in
`block in requires='
from
/usr/lib/ruby/vendor_ruby/rspec/core/configuration.rb:1280:in
`each'
from
/usr/lib/ruby/vendor_ruby/rspec/core/configuration.rb:1280:in
`requires='
from
/usr/lib/ruby/vendor_ruby/rspec/core/configuration_options.rb:109:in
`block in process_options_into'
from
/usr/lib/ruby/vendor_ruby/rspec/core/configuration_options.rb:108:in
`each'
from
/usr/lib/ruby/vendor_ruby/rspec/core/configuration_options.rb:108:in
`process_options_into'
from
/usr/lib/ruby/vendor_ruby/rspec/core/configuration_options.rb:21:in
`configure'
from /usr/lib/ruby/vendor_ruby/rspec/core/runner.rb:102:in
`setup'
from /usr/lib/ruby/vendor_ruby/rspec/core/runner.rb:89:in `run'
from /usr/lib/ruby/vendor_ruby/rspec/core/runner.rb:74:in `run'
from /usr/lib/ruby/vendor_ruby/rspec/core/runner.rb:42:in
`invoke'
from /usr/bin/rspec:4:in `main'
/usr/bin/ruby2.1 /usr/bin/rspec --pattern
spec/\*\*\{,/\*/\*\*\}/\*_spec.rb failed
ERROR: Test ruby2.1 failed. Exiting.
dh_auto_install: dh_ruby --install
/tmp/buildd/ruby-rspec-longrun-1.0.1/debian/ruby-rspec-longrun
returned exit code 1
debian/rules:15: recipe for target 'binary' failed
make: *** [binary] Error 1
dpkg-buildpackage: error: fakeroot debian/rules binary gave error exit
status 2
[..]
The full build log is attached or can be viewed here:
https://reproducible.debian.net/logs/unstable/amd64/ruby-rspec-longrun_1.0.1-1.build1.log.gz
Regards,
--
,''`.
: :' : Chris Lamb
`. `'` la...@debian.org / chris-lamb.co.uk
`-
I: using fakeroot in build.
I: pbuilder: network access will be disabled during build
I: Current time: Fri Jul 24 18:52:58 GMT+12 2015
I: pbuilder-time-stamp: 1437807178
I: Building the build Environment
I: extracting base tarball [/var/cache/pbuilder/unstable-reproducible-base.tgz]
I: creating local configuration
I: copying local configuration
I: mounting /proc filesystem
I: mounting /run/shm filesystem
I: mounting /dev/pts filesystem
I: Mounting /dev/shm
I: Mounting /sys
I: policy-rc.d already exists
I: Installing the build-deps
- Attempting to satisfy build-dependencies
- Creating pbuilder-satisfydepends-dummy package
Package: pbuilder-satisfydepends-dummy
Version: 0.invalid.0
Architecture: amd64
Maintainer: Debian Pbuilder Team pbuilder-ma...@lists.alioth.debian.org
Description: Dummy package to satisfy dependencies with aptitude - created by
pbuilder
This package was created automatically by pbuilder to satisfy the
build-dependencies of the package being currently built.
Depends: debhelper (= 7.0.50~), gem2deb (= 0.5.0~), ruby-rspec-core (= 2.10~)
dpkg-deb: building package 'pbuilder-satisfydepends-dummy' in
'/tmp/satisfydepends-aptitude/pbuilder-satisfydepends-dummy.deb'.
Selecting
Bug#795644: git-annex: configure eats all memory
Hi, I had a quick tired look yesterday, and I observed that it happens on my machine as well (so it is not mips-specific). It happened when just running ghc --make Setup; ./Setup configure directly, it happened with dpkg-buildpackage -d, but not within sbuild, which creates a clean environment. Furthermore it happend both with and without the libghc -cabal-dev package installed. So it must be something about the environment (environment variables, other packages installed etc.) that causes this. I wonder if the configure is doing something like traversing the whole filesystem which could cause it to do so much more work? Greetings, Joachim -- Joachim nomeata Breitner Debian Developer nome...@debian.org | ICQ# 74513189 | GPG-Keyid: F0FBF51F JID: nome...@joachim-breitner.de | http://people.debian.org/~nomeata signature.asc Description: This is a digitally signed message part
Bug#795614: [PATCH] fix false-positive spelling-error-in-binary affecting many Go binaries
On Sun, Aug 16, 2015 at 10:11 AM, Niels Thykier ni...@thykier.net wrote:
On 2015-08-15 21:59, Michael Stapelberg wrote:
Package: lintian
Version: 2.5.33
Severity: normal
Tags: patch
From the patch description:
[PATCH] spelling-error-in-binary: ignore ang/and
The Go stdlib html/ package contains the string ang; (for the ang;
entity). Every program which directly or indirectly imports the html/
package will hence end up with an unuseful spelling-error-in-binary
lintian warning.
[...]
Hi Michael,
Thanks for the patch.
I was wondering, have you tried something like?
$ git diff
diff --git a/lib/Lintian/Check.pm b/lib/Lintian/Check.pm
index 4b08fae..0b11477 100644
--- a/lib/Lintian/Check.pm
+++ b/lib/Lintian/Check.pm
@@ -301,6 +301,7 @@ sub check_spelling {
$text =~ s/(\w-)\s*\n\s*/$1/;
$text =~ tr/\r\n \t/ /s;
$text =~ s/\s++/ /g;
+$text =~ s/\[a-zA-Z0-9_-]+\;//g; # Ignore XML entities
strip($text);
for my $word (split(' ', $text)) {
AFAICT, it should strip out all XML entities (untested though), which
should be a more generic solution. Does this work for you?
I think your patch does indeed strip out XML entities, but it doesn’t
quite work for our use-case: note that the string that’s found in the
binary is “ang;”, not “ang;”.
--
Best regards,
Michael
Bug#757015: iceweasel: Bookmark folders still broken
Package: iceweasel
Version: 38.2.0esr-1~stretch
Followup-For: Bug #757015
Dear Maintainer,
I can confirm this bug persists in Testing. Whether I sync with Firefox Sync
or import bookmarks manually from an html file, my bookmark folders don't
appear in the bookmarks menu. They do, however, show up in the Bookmarks
Library, though they don't have folder icons next to them.
The bookmarks still exist inside the folders when I click on them in the
Library, and I can still access them with auto-complete in the address bar,
just not through the menu.
Do any maintaners know why powerpc users are seemingly the only ones hit by
this bug?
Regards,
Dan
-- Package-specific info:
-- Extensions information
Name: Default theme
Location:
/usr/lib/iceweasel/browser/extensions/{972ce4c6-7e08-4474-a285-3208198ce6fd}
Package: iceweasel
Status: enabled
Name: uBlock Origin
Location: ${PROFILE_EXTENSIONS}/ublo...@raymondhill.net.xpi
Status: enabled
-- Plugins information
-- Addons package information
ii iceweasel 38.2.0esr-1~ powerpc Web browser based on Firefox
-- System Information:
Debian Release: stretch/sid
APT prefers testing
APT policy: (500, 'testing'), (1, 'experimental')
Architecture: powerpc (ppc)
Kernel: Linux 4.1.0-1-powerpc
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
Versions of packages iceweasel depends on:
ii debianutils 4.5.1
ii fontconfig2.11.0-6.3
ii libasound21.0.29-1
ii libatk1.0-0 2.16.0-2
ii libc6 2.19-19
ii libcairo2 1.14.2-2
ii libdbus-1-3 1.8.20-1
ii libdbus-glib-1-2 0.102-1
ii libevent-2.0-52.0.21-stable-2
ii libffi6 3.2.1-3
ii libfontconfig12.11.0-6.3
ii libfreetype6 2.5.2-4
ii libgcc1 1:5.1.1-14
ii libgdk-pixbuf2.0-02.31.5-1
ii libglib2.0-0 2.44.1-1.1
ii libgtk2.0-0 2.24.28-1
ii libhunspell-1.3-0 1.3.3-3
ii libnspr4 2:4.10.8-2
ii libnss3 2:3.19.2-1
ii libpango-1.0-01.36.8-3
ii libsqlite3-0 3.8.11.1-1
ii libstartup-notification0 0.12-4
ii libstdc++65.1.1-14
ii libvpx2 1.4.0-4
ii libx11-6 2:1.6.3-1
ii libxcomposite11:0.4.4-1
ii libxdamage1 1:1.1.4-2+b1
ii libxext6 2:1.3.3-1
ii libxfixes31:5.0.1-2+b2
ii libxrender1 1:0.9.8-1+b1
ii libxt61:1.1.4-1+b1
ii procps2:3.3.10-2
ii zlib1g1:1.2.8.dfsg-2+b1
Versions of packages iceweasel recommends:
ii gstreamer1.0-libav 1.4.5-3
ii gstreamer1.0-plugins-good 1.4.5-2
Versions of packages iceweasel suggests:
pn fonts-mathjax none
pn fonts-oflb-asana-math none
pn fonts-stix | otf-stix none
ii libcanberra0 0.30-2.1
pn libgnomeui-0 none
ii libgssapi-krb5-2 1.13.2+dfsg-2
pn mozplugger none
-- no debconf information
Bug#795639: assword fails with Decryption error: Decryption failed
On Sun 2015-08-16 02:55:43 +0200, Russ Allbery wrote: Daniel Kahn Gillmor d...@fifthhorseman.net writes: does this succeed with gpg2 --decrypt as well, or just gpg --decrypt? Aha. Here's a problem: mithrandir:~/private/db$ gpg2 --decrypt personal gpg: error reading keyblock: Legacy key gpg: keydb_get_keyblock failed: Legacy key gpg: encrypted with RSA key, ID 7CE29A76E9769486 gpg: decryption failed: No secret key I have no idea what that means, and Google was not particularly enlightening. do you see files listed when you look at the GnuPG 2.1 secret key storage: ls -l ~/.gnupg/private-keys-v1.d/*.key Yes. ok, so the keygrip for 0x7CE29A76E9769486 is FD1DA474D3DF3C728C54F9E479EDFC5BBE2E14EA (via gpg2 --with-keygrip --list-keys 7CE29A76E9769486) do you see ~/.gnupg/private-keys-v1.d/FD1DA474D3DF3C728C54F9E479EDFC5BBE2E14EA.key ? Depending on the output of the above, maybe you can try importing your secret keyring again: gpg2 --import ~/.gnupg/secring.gpg (this should have been imported automatically for you upon your first use of gpg 2.1 after the upgrade) I get a lot more legacy key errors, and this weird error that I don't understand: gpg: key D15D313882004173: no valid user IDs gpg: this may be caused by a missing self-signature gpg: keydb_get_keyblock failed: Legacy key gpg: key D15D313882004173: failed to re-lookup public key That key definitely has a self-signature. It's the same key I use for Debian. mithrandir:~/private/db$ gpg -kv D15D313882004173 pub 4096R/D15D313882004173 2009-05-29 [expires: 2017-09-17] uid [ultimate] Russ Allbery ea...@eyrie.org uid [ultimate] Russ Allbery r...@stanford.edu uid [ultimate] Russ Allbery r...@debian.org uid [ revoked] Russ Allbery ea...@windlord.stanford.edu uid [ultimate] Russ Allbery r...@cs.stanford.edu sub 4096R/7CE29A76E9769486 2009-05-29 [expires: 2017-09-17] sub 2048R/7D80315C5736DE75 2010-09-17 [expires: 2016-03-20] I agree with you that this key clearly has valid self-sigs. it does in my copy as well. can you show the same output from gpg2 as well as gpg ? Also: does it show up in the output of: gpg2 --list-secret-keys sorry for the hassle, and thanks for the quick debugging responses. --dkg
Bug#795672: [neurodebian-desktop] Add dependency on reportbug-ng
Package: neurodebian-desktop Version: 0.37.2 Severity: normal --- Please enter the report below this line. --- I would like to recommend people to report bugs with a convenient tool. Hence, I'd prefer to have reportbug-ng be available and refer to it in the documentation. This bug is actually filed with reportbug-ng. While it is not extremely more convenient, it is more convenient. --- System information. --- Architecture: amd64 Kernel: Linux 3.16-2-amd64 Debian Release: stretch/sid 650 testing security.debian.org 650 testing http.debian.net 500 stretch neuro.debian.net 500 stable dl.google.com 500 dataneuro.debian.net --- Package information. --- Depends (Version) | Installed =-+-=== ssh-askpass-gnome | OR ssh-askpass | 1:1.2.4.1-9 desktop-base | 8.0.2 gnome-icon-theme | 3.12.0-1 neurodebian-popularity-contest| 0.37.2 Package's Recommends field is empty. Package's Suggests field is empty. -- Michael Hanke http://mih.voxindeserto.de
Bug#795671: O: gwrite -- simple GTK+ HTML5 rich text editor
Package: wnpp Severity: normal I'm no longer a user of gwrite for quite some time, and the upstream seems not updating anymore, thus orphaning. Thanks, Aron
Bug#795669: O: cliofetion -- open source command line implementation of Fetion protocol
Package: wnpp Severity: normal I'm no longer a user of cliofetion for quite some time, and the upstream seems not updating anymore, thus orphaning. Thanks, Aron
Bug#795670: O: gmlive -- live video frontend for mplayer
Package: wnpp Severity: normal I'm no longer a user of cliofetion for quite some time, and the upstream seems not updating anymore, thus orphaning. Thanks, Aron
Bug#795673: nmu: google-glog_0.3.4-0.1
Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: binnmu nmu google-glog_0.3.4-0.1 . ALL . unstable . -m Previous upload was not built against proper libgflags-dev. -- System Information: Debian Release: stretch/sid APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 4.1.0-1-amd64 (SMP w/4 CPU cores) Locale: LANG=es_US.UTF-8, LC_CTYPE=es_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: sysvinit (via /sbin/init)
Bug#791314: xqilla gcc 5 transition
On Sat, Aug 15, 2015 at 16:36:25 +0300, Tommi Vainikainen wrote: FYI, xqilla 2.3.0-3 with libxqilla6 renamed to libxqilla6v5 compiled with gcc 5 is now in sid. xqilla has two reverse dependencies related to transition as listed here https://release.debian.org/transitions/html/auto-xqilla.html Both of those are libraries, and both of them are RC-buggy. IMO they should either be removed or somebody should look after them (including checking if they break ABI with g++ 5). Cheers, Julien signature.asc Description: Digital signature
Bug#795659: pagekite: please make the build reproducible
Source: pagekite
Version: 0.5.6d-4
Severity: wishlist
Tags: patch
User: reproducible-bui...@lists.alioth.debian.org
Usertags: timestamps
X-Debbugs-Cc: reproducible-bui...@lists.alioth.debian.org
Hi,
While working on the reproducible builds effort [1], we have noticed
that pagekite could not be built reproducibly.
The attached patch removes (timezone-varying) build time timestamps from
the build system. Once applied, pagekite can be built reproducibly in
our
reproducible toolchain.
[1]: https://wiki.debian.org/ReproducibleBuilds
Regards,
--
,''`.
: :' : Chris Lamb
`. `'` la...@debian.org / chris-lamb.co.uk
`-
--- a/pagekite/compat.py2015-08-16 08:48:19.910479441 +0200
--- b/pagekite/compat.py2015-08-16 08:57:27.007924014 +0200
@@ -50,7 +50,7 @@
import datetime
ts_to_date = datetime.datetime.fromtimestamp
def ts_to_iso(ts=None):
-return datetime.datetime.fromtimestamp(ts).isoformat()
+return datetime.datetime.utcfromtimestamp(ts).isoformat()
except ImportError:
ts_to_date = str
ts_to_iso = str
--- a/pagekite/manual.py2015-08-16 08:48:19.910479441 +0200
--- b/pagekite/manual.py2015-08-16 08:54:12.769916889 +0200
@@ -2,6 +2,7 @@
The program manual!
+import os
import re
import time
@@ -447,7 +448,7 @@
.TH PAGEKITE 1 %s https://pagekite.net/; Awesome Commands
.nh
.ad l
-) % ts_to_iso(time.time()).split('T')[0]
+) % ts_to_iso(int(os.environ['SOURCE_DATE_EPOCH'])).split('T')[0]
for h, section, text in MANUAL_TOC:
man += ('.%s %s\n\n%s\n\n'
) % (h, h == 'SH' and section.upper() or section,
Bug#795660: virtualbox-ext-pack: License terms shouldn't be marked as translatable in the debconf screen
Package: virtualbox-ext-pack Severity: normal Tags: l10n patch The recently uploaded version of this package intruduced 20 translatable strings for the debconf template that displays the license. Apart from discussin whether using debconf to make users accept licenses is both a good idea and valid (which I don't think it is), the license terms shouldn't be marked for translation. The attached patch does this by marking the template synopsis to be the only translatable string. -- System Information: Debian Release: stretch/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.1.0-1-amd64 (SMP w/4 CPU cores) Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) --- virtualbox-ext-pack/virtualbox-ext-pack.old/debian/templates 2015-08-16 08:55:49.007278910 +0200 +++ virtualbox-ext-pack/virtualbox-ext-pack/debian/templates 2015-08-16 08:57:39.405687858 +0200 @@ -1,6 +1,7 @@ Template: virtualbox-ext-pack/license Type: boolean Default: true +#flag:translate:1 _Description: Do you accept the terms of this license? VirtualBox Personal Use and Evaluation License (PUEL) .
Bug#735932: [grub2-common] Computer does not boot
Am Montag, den 13.10.2014, 15:54 +0100 schrieb Colin Watson: On Wed, Jan 29, 2014 at 05:54:40PM +0100, Vincent Barichard wrote: I had the same issue, and I succeeded to recover by using a live cd and a chroot environment. In the chroot environment I reinstalled grub with : grub-install - -removable It updates the file in EFI/boot/ instead of EFI/debian. I hope it will help. This may well be a quite different issue from that of the original reporter, who has so far not indicated whether they were using BIOS or UEFI. Your issue is #708430. Hi Marco, is this still a problem? If so, could you please provide more information? Like the above question if this is BIOS or EFI
Bug#795608: krdc: Package uninstallable?
Quoting Diederik de Haas (didi.deb...@cknow.org): On Saturday 15 August 2015 20:03:35 Christian Perrier wrote: (reporting as important because I'm unsure about the ongoing transition to Plasma 5) That is likely the cause. I wouldn't be surprised if it would work if you also had the testing repos in your /etc/apt/sources.list Sadly, no. I know nearly nothing about KDE/Plasma things, I'm just a user, herebut if there is anything I can do to help fixing the issue, I'd be happy to do it (including rebuilding the package or whatever could be needed). -- signature.asc Description: Digital signature
Bug#795662: python-passlib: FTBFS: ImportError: No module named django
Source: python-passlib
Version: 1.6.1-1.3
Severity: serious
Justification: fails to build from source
Dear Maintainer,
python-passlib fails to build from source on unstable/amd64:
[..]
==
ERROR: Failure: ImportError (No module named django)
--
Traceback (most recent call last):
File /usr/lib/python2.7/dist-packages/nose/loader.py, line 420, in
loadTestsFromName
addr.filename, addr.module)
File /usr/lib/python2.7/dist-packages/nose/importer.py, line 47,
in importFromPath
return self.importFromDir(dir_path, fqname)
File /usr/lib/python2.7/dist-packages/nose/importer.py, line 94,
in importFromDir
mod = load_module(part_fqname, fh, filename, desc)
File
/tmp/buildd/python-passlib-1.6.1/.pybuild/pythonX.Y_2.7/build/passlib/ext/django/models.py,
line 9, in module
from django import VERSION
ImportError: No module named django
==
ERROR: Failure: AttributeError (missing attribute: '__file__')
--
Traceback (most recent call last):
File /usr/lib/python2.7/dist-packages/nose/plugins/manager.py,
line 154, in generate
for r in result:
File /usr/lib/python2.7/dist-packages/nose/plugins/doctests.py,
line 238, in loadTestsFromModule
module_file = src(module.__file__)
File
/tmp/buildd/python-passlib-1.6.1/.pybuild/pythonX.Y_2.7/build/passlib/registry.py,
line 35, in __getattr__
raise AttributeError(missing attribute: %r % (attr,))
AttributeError: missing attribute: '__file__'
==
FAIL: Doctest: passlib.context.CryptContext
--
Traceback (most recent call last):
File /usr/lib/python2.7/doctest.py, line 2226, in runTest
raise self.failureException(self.format_failure(new.getvalue()))
AssertionError: Failed doctest test for passlib.context.CryptContext
File
/tmp/buildd/python-passlib-1.6.1/.pybuild/pythonX.Y_2.7/build/passlib/context.py,
line 1515, in CryptContext
--
File
/tmp/buildd/python-passlib-1.6.1/.pybuild/pythonX.Y_2.7/build/passlib/context.py,
line 1526, in passlib.context.CryptContext
Failed example:
ctx = CryptContext(schemes=[...])
Exception raised:
Traceback (most recent call last):
File /usr/lib/python2.7/doctest.py, line 1315, in __run
compileflags, 1) in test.globs
File doctest passlib.context.CryptContext[0], line 1
ctx = CryptContext(schemes=[...])
^
SyntaxError: invalid syntax
begin captured logging
[..]
- end captured logging -
==
FAIL: Doctest: passlib.context.CryptContext.copy
--
Traceback (most recent call last):
File /usr/lib/python2.7/doctest.py, line 2226, in runTest
raise self.failureException(self.format_failure(new.getvalue()))
AssertionError: Failed doctest test for
passlib.context.CryptContext.copy
File
/tmp/buildd/python-passlib-1.6.1/.pybuild/pythonX.Y_2.7/build/passlib/context.py,
line 1633, in copy
--
File
/tmp/buildd/python-passlib-1.6.1/.pybuild/pythonX.Y_2.7/build/passlib/context.py,
line 1648, in passlib.context.CryptContext.copy
Failed example:
ctx2 = custom_app_context.copy(default=md5_crypt)
Exception raised:
Traceback (most recent call last):
File /usr/lib/python2.7/doctest.py, line 1315, in __run
compileflags, 1) in test.globs
File doctest passlib.context.CryptContext.copy[2], line 1,
in module
ctx2 = custom_app_context.copy(default=md5_crypt)
NameError: name 'custom_app_context' is not defined
--
File
/tmp/buildd/python-passlib-1.6.1/.pybuild/pythonX.Y_2.7/build/passlib/context.py,
line 1651, in passlib.context.CryptContext.copy
Failed example:
ctx1.default_scheme()
Expected:
sha256_crypt
Got:
'sha256_crypt'
--
File
/tmp/buildd/python-passlib-1.6.1/.pybuild/pythonX.Y_2.7/build/passlib/context.py,
line 1653, in passlib.context.CryptContext.copy
Failed example:
ctx2.default_scheme()
Exception raised:
Traceback (most recent call last):
File
Bug#795663: ruby-timecop: FTBFS under some timezones
Source: ruby-timecop
Version: 0.7.3-1
Severity: serious
Tags: patch
Justification: fails to build from source
Dear Maintainer,
ruby-timecop fails to build from source on unstable/amd64 under some
timezones (eg. TZ=/usr/share/zoneinfo/Etc/GMT+12):
[..]
┌──┐
│ Run tests for ruby2.1 from debian/ruby-tests.rb
│
└──┘
RUBYLIB=/tmp/buildd/ruby-timecop-0.7.3/debian/ruby-timecop/usr/lib/ruby/vendor_ruby:.
ruby2.1 debian/ruby-tests.rb
./test/timecop_without_date_but_with_time_test.rb
MiniTest::Unit::TestCase is now Minitest::Test. From
./test/timecop_without_date_but_with_time_test.rb:3:in `main'
Run options: --seed 23950
# Running:
.
Finished in 0.019255s, 51.9351 runs/s, 0. assertions/s.
1 runs, 0 assertions, 0 failures, 0 errors, 0 skips
./test/time_stack_item_test.rb
MiniTest::Unit::TestCase is now Minitest::Test. From
./test/time_stack_item_test.rb:7:in `main'
Run options: --seed 64273
# Running:
..F.
Finished in 0.085731s, 326.6023 runs/s, 816.5057 assertions/s.
1) Failure:
TestTimeStackItem#test_timezones_apply_dates
[./test/time_stack_item_test.rb:187]:
Expected: Thu, 03 Jan 2013
Actual: Wed, 02 Jan 2013
28 runs, 70 assertions, 1 failures, 0 errors, 0 skips
debian/ruby-tests.rb:3:in `block in main': unhandled exception
from debian/ruby-tests.rb:1:in `each'
from debian/ruby-tests.rb:1:in `main'
ERROR: Test ruby2.1 failed. Exiting.
dh_auto_install: dh_ruby --install
/tmp/buildd/ruby-timecop-0.7.3/debian/ruby-timecop returned exit code
1
debian/rules:4: recipe for target 'binary' failed
make: *** [binary] Error 1
dpkg-buildpackage: error: fakeroot debian/rules binary gave error exit
status 2
[..]
The full build log is attached or can be viewed here:
https://reproducible.debian.net/logs/unstable/amd64/ruby-timecop_0.7.3-1.build1.log.gz
Adding `export TZ=UTC` to debian/rules fixes this for me.
Regards,
--
,''`.
: :' : Chris Lamb
`. `'` la...@debian.org / chris-lamb.co.uk
`-
I: using fakeroot in build.
I: pbuilder: network access will be disabled during build
I: Current time: Thu Jul 30 12:24:33 GMT+12 2015
I: pbuilder-time-stamp: 1438302273
I: Building the build Environment
I: extracting base tarball [/var/cache/pbuilder/unstable-reproducible-base.tgz]
I: creating local configuration
I: copying local configuration
I: mounting /proc filesystem
I: mounting /run/shm filesystem
I: mounting /dev/pts filesystem
I: Mounting /dev/shm
I: Mounting /sys
I: policy-rc.d already exists
I: Installing the build-deps
- Attempting to satisfy build-dependencies
- Creating pbuilder-satisfydepends-dummy package
Package: pbuilder-satisfydepends-dummy
Version: 0.invalid.0
Architecture: amd64
Maintainer: Debian Pbuilder Team pbuilder-ma...@lists.alioth.debian.org
Description: Dummy package to satisfy dependencies with aptitude - created by
pbuilder
This package was created automatically by pbuilder to satisfy the
build-dependencies of the package being currently built.
Depends: debhelper (= 7.0.50~), gem2deb (= 0.3.0~), ruby-mocha,
ruby-activesupport, ruby-tzinfo, ruby-minitest
dpkg-deb: building package 'pbuilder-satisfydepends-dummy' in
'/tmp/satisfydepends-aptitude/pbuilder-satisfydepends-dummy.deb'.
Selecting previously unselected package pbuilder-satisfydepends-dummy.
(Reading database ... 20233 files and directories currently installed.)
Preparing to unpack .../pbuilder-satisfydepends-dummy.deb ...
Unpacking pbuilder-satisfydepends-dummy (0.invalid.0) ...
dpkg: pbuilder-satisfydepends-dummy: dependency problems, but configuring
anyway as you requested:
pbuilder-satisfydepends-dummy depends on gem2deb (= 0.3.0~); however:
Package gem2deb is not installed.
pbuilder-satisfydepends-dummy depends on ruby-mocha; however:
Package ruby-mocha is not installed.
pbuilder-satisfydepends-dummy depends on ruby-activesupport; however:
Package ruby-activesupport is not installed.
pbuilder-satisfydepends-dummy depends on ruby-tzinfo; however:
Package ruby-tzinfo is not installed.
pbuilder-satisfydepends-dummy depends on ruby-minitest; however:
Package ruby-minitest is not installed.
Setting up pbuilder-satisfydepends-dummy (0.invalid.0) ...
Reading package lists...
Building dependency tree...
Reading state information...
Initializing package states...
Writing extended state information...
Building tag database...
The following NEW packages will be installed:
ca-certificates{a} devscripts{a} dh-python{a} gem2deb{a}
gem2deb-test-runner{a} libexpat1{a} libgmp-dev{a} libgmpxx4ldbl{a}
libmpdec2{a} libpython3-stdlib{a} libpython3.4-minimal{a}
libpython3.4-stdlib{a} libruby2.1{a} libruby2.2{a} libssl1.0.0{a}
libyaml-0-2{a} mime-support{a}
Bug#795614: [PATCH] fix false-positive spelling-error-in-binary affecting many Go binaries
On 2015-08-15 21:59, Michael Stapelberg wrote:
Package: lintian
Version: 2.5.33
Severity: normal
Tags: patch
From the patch description:
[PATCH] spelling-error-in-binary: ignore ang/and
The Go stdlib html/ package contains the string ang; (for the ang;
entity). Every program which directly or indirectly imports the html/
package will hence end up with an unuseful spelling-error-in-binary
lintian warning.
[...]
Hi Michael,
Thanks for the patch.
I was wondering, have you tried something like?
$ git diff
diff --git a/lib/Lintian/Check.pm b/lib/Lintian/Check.pm
index 4b08fae..0b11477 100644
--- a/lib/Lintian/Check.pm
+++ b/lib/Lintian/Check.pm
@@ -301,6 +301,7 @@ sub check_spelling {
$text =~ s/(\w-)\s*\n\s*/$1/;
$text =~ tr/\r\n \t/ /s;
$text =~ s/\s++/ /g;
+$text =~ s/\[a-zA-Z0-9_-]+\;//g; # Ignore XML entities
strip($text);
for my $word (split(' ', $text)) {
AFAICT, it should strip out all XML entities (untested though), which
should be a more generic solution. Does this work for you?
Thanks,
~Niels
Bug#795652: ITP: kubernetes -- cluster manager for Docker containers
Could we team maintain this in the Docker packaging team? Cheers! Thanks for your work! Paul On Sun, Aug 16, 2015 at 4:50 AM, Dmitry Smirnov only...@debian.org wrote: Package: wnpp Severity: wishlist X-Debbugs-CC: debian-de...@lists.debian.org Package name: kubernetes Version: 1.0.3 Upstream Author: Google License: Apache-2.0 URL: http://kubernetes.io/ Description: cluster manager for Docker containers Kubernetes is an open source orchestration system for Docker containers. It handles scheduling onto nodes in a compute cluster and actively manages workloads to ensure that their state matches the users declared intentions. Using the concepts of labels and pods, it groups the containers which make up an application into logical units for easy management and discovery. -- :wq
Bug#792866: RFA: node-tmp
Control: retitle 792866 ITA: node-tmp Control: owner 792866 ! I am happy to adopt this package and maintain it within the Debian Javascipt Team. Regards, Ross signature.asc Description: OpenPGP digital signature
Bug#795674: steam: Can't type in russian
Package: steam Version: 1.0.0.50-5 Severity: normal Dear Maintainer, Last update of steam package prevents me from typing in russian in chat and forums. Deleting # use C locale (bug #764311) export LANG=C lines from /usr/games/steam solves this problem. ~$ locale -a C C.UTF-8 en_US.utf8 POSIX ru_RU.utf8 -- System Information: Debian Release: stretch/sid APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.1.0-1-amd64 (SMP w/4 CPU cores) Locale: LANG=ru_RU.utf8, LC_CTYPE=ru_RU.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages steam depends on: ii debconf [debconf-2.0] 1.5.57 ii libc6 2.19-19 ii libgl1-mesa-dri 10.6.3-1 ii libgl1-mesa-glx 10.6.3-1 ii libstdc++65.1.1-14 ii libtxc-dxtn-s2tc0 [libtxc-dxtn0] 0~git20131104-1.1 ii libudev1 224-1 ii libx11-6 2:1.6.3-1 ii libxinerama1 2:1.1.3-1+b1 ii xfce4-terminal [x-terminal-emulator] 0.6.3-1+b2 ii xterm [x-terminal-emulator] 318-2 ii xz-utils 5.1.1alpha+20120614-2.1 Versions of packages steam recommends: ii fonts-liberation 1.07.4-1 ii zenity3.16.3-1 steam suggests no packages. -- debconf information: steam/purge: * steam/question: I AGREE * steam/license:
Bug#795675: fuse-zip: Source repository location changed, version 0.4.1 is available
Package: fuse-zip Version: 0.4.0-1 Severity: wishlist Tags: upstream Hello! fuse-zip project is now hosted at https://bitbucket.org/agalanin/fuse-zip because of GoogleCode shutdown. Also version 0.4.1 is available. This version includes a fix for 'subdir' FUSE module support. -- System Information: Debian Release: 8.1 APT prefers stable APT policy: (990, 'stable'), (500, 'stable-updates'), (500, 'oldstable-updates'), (500, 'oldstable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.16.0-4-amd64 (SMP w/2 CPU cores) Locale: LANG=ru_RU.UTF-8, LC_CTYPE=ru_RU.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: sysvinit (via /sbin/init) Versions of packages fuse-zip depends on: ii libc6 2.19-18 ii libfuse22.9.3-15+deb8u1 ii libgcc1 1:4.9.2-10 ii libstdc++6 4.9.2-10 ii libzip2 0.11.2-1.2 ii zlib1g 1:1.2.8.dfsg-2+b1 fuse-zip recommends no packages. fuse-zip suggests no packages. -- no debconf information
Bug#795676: ruby-text-table: Non-deterministic FTBFS due to unreliable timing benchmarks in tests
Source: ruby-text-table
Version: 1.2.3-2
Severity: serious
Justification: fails to build from source
Dear Maintainer,
ruby-text-table can non-deterministic FTBFS due to using unreliable
timing benchmarks in tests:
[..]
1) Text::Table performance is linear relative to row count
Failure/Error: time.should_not base * 12
expected not: 0.015996084
got: 0.022761029
# ./spec/integration/performance_spec.rb:9:in `block (2 levels)
in top (required)'
[..]
The code itself (spec/integration/performance_spec.rb):
require 'spec_helper'
require 'benchmark'
describe Text::Table, 'performance' do
it 'is linear relative to row count' do
base = time_to_render_num_of_rows 30
time = time_to_render_num_of_rows 300
time.should_not base * 12
end
def time_to_render_num_of_rows(num)
GC.start
Benchmark.realtime do
Text::Table.new(:rows = Array.new(num)).to_s
end
end
end
What can happen is that if ``time_to_render_num_of_rows 300`` takes a
long time to run (eg. sudden high load, suspend, etc. etc.), the test
incorrectly concludes that the algorithm is not linear and the build
fails.
The test is completely unreliable anyway -- if
``time_to_render_num_of_rows 30`` runs relatively /fast/ for some reason
(CPU throttling disabled, whatever) and the algorithm is polynomial, the
test will incorrectly *pass*. So, basically, it's garbage.
The full build log is attached or can be viewed here:
https://reproducible.debian.net/logs/unstable/amd64/ruby-text-table_1.2.3-2.build1.log.gz
Regards,
--
,''`.
: :' : Chris Lamb
`. `'` la...@debian.org / chris-lamb.co.uk
`-
I: using fakeroot in build.
I: pbuilder: network access will be disabled during build
I: Current time: Thu Jul 30 12:21:41 GMT+12 2015
I: pbuilder-time-stamp: 1438302101
I: Building the build Environment
I: extracting base tarball [/var/cache/pbuilder/unstable-reproducible-base.tgz]
I: creating local configuration
I: copying local configuration
I: mounting /proc filesystem
I: mounting /run/shm filesystem
I: mounting /dev/pts filesystem
I: Mounting /dev/shm
I: Mounting /sys
I: policy-rc.d already exists
I: Installing the build-deps
- Attempting to satisfy build-dependencies
- Creating pbuilder-satisfydepends-dummy package
Package: pbuilder-satisfydepends-dummy
Version: 0.invalid.0
Architecture: amd64
Maintainer: Debian Pbuilder Team pbuilder-ma...@lists.alioth.debian.org
Description: Dummy package to satisfy dependencies with aptitude - created by
pbuilder
This package was created automatically by pbuilder to satisfy the
build-dependencies of the package being currently built.
Depends: debhelper (= 7.0.50~), gem2deb (= 0.3.0~), ruby-rspec, rake
dpkg-deb: building package 'pbuilder-satisfydepends-dummy' in
'/tmp/satisfydepends-aptitude/pbuilder-satisfydepends-dummy.deb'.
Selecting previously unselected package pbuilder-satisfydepends-dummy.
(Reading database ... 20233 files and directories currently installed.)
Preparing to unpack .../pbuilder-satisfydepends-dummy.deb ...
Unpacking pbuilder-satisfydepends-dummy (0.invalid.0) ...
dpkg: pbuilder-satisfydepends-dummy: dependency problems, but configuring
anyway as you requested:
pbuilder-satisfydepends-dummy depends on gem2deb (= 0.3.0~); however:
Package gem2deb is not installed.
pbuilder-satisfydepends-dummy depends on ruby-rspec; however:
Package ruby-rspec is not installed.
pbuilder-satisfydepends-dummy depends on rake; however:
Package rake is not installed.
Setting up pbuilder-satisfydepends-dummy (0.invalid.0) ...
Reading package lists...
Building dependency tree...
Reading state information...
Initializing package states...
Writing extended state information...
Building tag database...
The following NEW packages will be installed:
ca-certificates{a} devscripts{a} dh-python{a} gem2deb{a}
gem2deb-test-runner{a} libexpat1{a} libgmp-dev{a} libgmpxx4ldbl{a}
libmpdec2{a} libpython3-stdlib{a} libpython3.4-minimal{a}
libpython3.4-stdlib{a} libruby2.1{a} libruby2.2{a} libssl1.0.0{a}
libyaml-0-2{a} mime-support{a} openssl{a} python3{a} python3-chardet{a}
python3-debian{a} python3-minimal{a} python3-pkg-resources{a}
python3-six{a} python3.4{a} python3.4-minimal{a} rake{a} ruby{a}
ruby-all-dev{a} ruby-diff-lcs{a} ruby-minitest{a} ruby-power-assert{a}
ruby-rspec{a} ruby-rspec-core{a} ruby-rspec-expectations{a}
ruby-rspec-mocks{a} ruby-rspec-support{a} ruby-setup{a} ruby-test-unit{a}
ruby-thread-order{a} ruby2.1{a} ruby2.1-dev{a} ruby2.2{a} ruby2.2-dev{a}
rubygems-integration{a}
0 packages upgraded, 45 newly installed, 0 to remove and 0 not upgraded.
Need to get 18.3 MB of archives. After unpacking 75.6 MB will be used.
Writing extended state information...
Get: 1 http://ftp.de.debian.org/debian/ unstable/main libmpdec2 amd64 2.4.1-1
[85.7 kB]
Get: 2 http://ftp.de.debian.org/debian/ unstable/main
Bug#795659: pagekite: please make the build reproducible
On Sunday 16 August 2015 02:14 PM, Chris Lamb wrote: Hi, Updated patch attached so it does not FTBFS if SOURCE_DATE_EPOCH env is not set. Thanks to Val Lorentz. I was just going to point out that. Thanks for the update :) Thank you for the patch. I was thinking of making my package builds reproducible but didn't get around to it. I will test the patch and get a new release uploaded. I will also make a effort to upstream the patch as it does not seem intrusive. -- Sunil signature.asc Description: OpenPGP digital signature
Bug#795656: python-imaplib2: wrong substitution variable for python3-imaplib2 Depends
Package: python-imaplib2
Version: 2.42-1
Severity: normal
Hi Ulises,
I wanted to let you know that the Depends field for python3-imaplib2 uses
${python:Depends} instead of ${python3:Depends}, which means that it is not
properly depending upon the necessary packages for the Python 3 module.
Thanks for maintaining this package!
Logan
-- System Information:
Debian Release: jessie/sid
APT prefers trusty-updates
APT policy: (500, 'trusty-updates'), (500, 'trusty-security'), (500,
'trusty'), (100, 'trusty-backports')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 3.8.0-36-generic (SMP w/1 CPU core)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Bug#795657: libapache2-mod-nss: CVE-2015-3277: incorrect multi-keyword mode cipherstring parsing
Source: libapache2-mod-nss Version: 1.0.11-1 Severity: important Tags: security upstream Hi, the following vulnerability was published for libapache2-mod-nss, introduced with the update to 1.0.11. CVE-2015-3277[0]: incorrect multi-keyword mode cipherstring parsing The vulnerable code was added in 1.0.11[1] afaict. If you fix the vulnerability please also make sure to include the CVE (Common Vulnerabilities Exposures) id in your changelog entry. For further information see: [0] https://security-tracker.debian.org/tracker/CVE-2015-3277 [1] https://git.fedorahosted.org/cgit/mod_nss.git/commit/?id=2d1650900f4d47dc43400d826c0f7e1a7c5229b8 [2] https://bugzilla.redhat.com/show_bug.cgi?id=1238324 Could you please double-check this? Regards, Salvatore
Bug#791070: htmlcxx: library transition may be needed when GCC 5 is the default
On Sun, Aug 16, 2015 at 00:32:50 +0100, Simon McVittie wrote: retitle 791070 transition: htmlcxx (g++-5) forwarded 791070 https://release.debian.org/transitions/html/auto-htmlcxx.html thanks On Fri, 14 Aug 2015 at 22:34:49 +0200, Stephen Kitt wrote: Thanks for the info, I'll upload an NMU in the near future. This has reached unstable and built everywhere except mips. The build-dependencies of the only reverse dependency have all started their transitions. Release team, please consider: nmu lgogdownloader_2.24-1 . ALL . -m 'Rebuild with libhtmlcxx3v5' dw lgogdownloader_2.24-1 . mips . -m 'libhtmlcxx3v5' mips is built now; binNMU scheduled. Cheers, Julien signature.asc Description: Digital signature
Bug#752381: initramfs-tools: does not activate logical volume before trying to mount root filesystem on LVM
Am Montag, den 23.06.2014, 10:42 +0200 schrieb Martin Steigerwald: What did I do: Today I installed backports version of open-vm-dkms and upgraded to most recent 3.14 backport kernel from a previous version of it I installed due to using BTRFS with skinny meta data on one partition. Current results: After this the machine failed to boot. It didn´t find the root filesystem by its UUID. I typed vgchange -ay in initramfs and then Ctrl-D and then it booted. This used to work without manual interaction before. Hi Martin, is there still something to do for us grub2 maintainers or is it solved? I'm a bit confused with the control mails from Ben Hutchings. Cheers, Felix
Bug#773787: hot: hot.hs:74:51-71: Non-exhaustive patterns in lambda
On Tue, Dec 23, 2014 at 11:04:15AM +0100, Joachim Breitner wrote: I get $ cat ../build-exp/haskell-auto-update_0.1.2-1_amd64.changes|hot dearmor hot (hopenpgp-tools) 0.13 Copyright (C) 2012-2014 Clint Adams hot comes with ABSOLUTELY NO WARRANTY. This is free software, and you are welcome to redistribute it under certain conditions. hot: hot.hs:74:51-71: Non-exhaustive patterns in lambda with the attached file. You just want it to output the binary signature packet?
Bug#795645: libbotan-1.10-0: library transition needed now that GCC 5 is the default
Now that I am on my computer instead of the phone with unfixed security errors (just a random rant on Android security), I can add a previous bug number: #790987 Cheers, Ondrej On Sun, Aug 16, 2015, at 08:10, Ondřej Surý wrote: Hi Scott, as far as I know I already prepared the transition and reassigned it to release.d.o. Is this something new or just an oversight? Ondřej On August 16, 2015 12:52:36 AM GMT+02:00, Scott Kitterman deb...@kitterman.com wrote: Package: libbotan-1.10-0 Version: 1.10.8-2 Severity: important Background [1]: libstdc++6 introduces a new ABI to conform to the C++11 standard, but keeps the old ABI to not break existing binaries. Packages which are built with g++-5 from experimental (not the one from testing/unstable) are using the new ABI. Libraries built from this source package export some of the new __cxx11 or B5cxx11 symbols, and dropping other symbols. If these symbols are part of the API of the library, then this rebuild with g++-5 will trigger a transition for the library. What is needed (note: this is the standard libstdc++6 bug template with some updates/additions): - Rebuild the library using g++/g++-5 from experimental. Note that most likely all C++ libraries within the build dependencies need a rebuild too. You can find the log for a rebuild in https://people.debian.org/~doko/logs/gcc5-20150701/ Search for BEGIN GCC CXX11 in the log. https://people.debian.org/~doko/logs/gcc5-20150701/botan1.10_1.10.8-2_unstable_gcc5.log - Decide if the symbols matching __cxx11 or B5cxx11 are part of the library API, and are used by the reverse dependencies of the library. - If there are no symbols matching __cxx11 or B5cxx11 in the symbols forming the library API, you should close this issue with a short explanation. - If there are no reverse dependencies, it should be the package maintainers decision if a transition is needed. However this might break software which is not in the Debian archive, and built against these packages. - If a library transition is needed, please prepare for the change. Rename the library package, append v5 to the name of the package (e.g. libfoo2 - libfoo2v5). Such a change can be avoided, if you have a soversion bump and you upload this version instead of the renamed package. Prepare a patch and attach it to this issue (mark this issue with patch), so that it is possible to NMU such a package. We'll probably have more than hundred transitions triggered. Then reassign the issue to release.debian.org and properly tag it as a transition issue, by sending an email to cont...@bugs.debian.org: user release.debian@packages.debian.org usertag this issue + transition block this issue by 790756 reassign this issue release.debian.org - If unsure if a transition is needed, please tag the issue with help to ask for feedback from other Debian developers. The libstdc++6 transition will be a large one, and it will come with a lot of pain. Please help it by preparing the follow-up transitions. [1] https://wiki.debian.org/GCC5#libstdc.2B-.2B-_ABI_transition Additional information: A transition is needed. Ovito will FTBFS unless both botan1.10 and qscintilla2 are updated (I discovered this preparing the qscintilla2 transition). -- Ondřej Surý -- Ondřej Surý ond...@sury.org Knot DNS (https://www.knot-dns.cz/) – a high-performance DNS server
Bug#795645: libbotan-1.10-0: library transition needed now that GCC 5 is the default
Hi Scott, as far as I know I already prepared the transition and reassigned it to release.d.o. Is this something new or just an oversight? Ondřej On August 16, 2015 12:52:36 AM GMT+02:00, Scott Kitterman deb...@kitterman.com wrote: Package: libbotan-1.10-0 Version: 1.10.8-2 Severity: important Background [1]: libstdc++6 introduces a new ABI to conform to the C++11 standard, but keeps the old ABI to not break existing binaries. Packages which are built with g++-5 from experimental (not the one from testing/unstable) are using the new ABI. Libraries built from this source package export some of the new __cxx11 or B5cxx11 symbols, and dropping other symbols. If these symbols are part of the API of the library, then this rebuild with g++-5 will trigger a transition for the library. What is needed (note: this is the standard libstdc++6 bug template with some updates/additions): - Rebuild the library using g++/g++-5 from experimental. Note that most likely all C++ libraries within the build dependencies need a rebuild too. You can find the log for a rebuild in https://people.debian.org/~doko/logs/gcc5-20150701/ Search for BEGIN GCC CXX11 in the log. https://people.debian.org/~doko/logs/gcc5-20150701/botan1.10_1.10.8-2_unstable_gcc5.log - Decide if the symbols matching __cxx11 or B5cxx11 are part of the library API, and are used by the reverse dependencies of the library. - If there are no symbols matching __cxx11 or B5cxx11 in the symbols forming the library API, you should close this issue with a short explanation. - If there are no reverse dependencies, it should be the package maintainers decision if a transition is needed. However this might break software which is not in the Debian archive, and built against these packages. - If a library transition is needed, please prepare for the change. Rename the library package, append v5 to the name of the package (e.g. libfoo2 - libfoo2v5). Such a change can be avoided, if you have a soversion bump and you upload this version instead of the renamed package. Prepare a patch and attach it to this issue (mark this issue with patch), so that it is possible to NMU such a package. We'll probably have more than hundred transitions triggered. Then reassign the issue to release.debian.org and properly tag it as a transition issue, by sending an email to cont...@bugs.debian.org: user release.debian@packages.debian.org usertag this issue + transition block this issue by 790756 reassign this issue release.debian.org - If unsure if a transition is needed, please tag the issue with help to ask for feedback from other Debian developers. The libstdc++6 transition will be a large one, and it will come with a lot of pain. Please help it by preparing the follow-up transitions. [1] https://wiki.debian.org/GCC5#libstdc.2B-.2B-_ABI_transition Additional information: A transition is needed. Ovito will FTBFS unless both botan1.10 and qscintilla2 are updated (I discovered this preparing the qscintilla2 transition). -- Ondřej Surý
Bug#794277: htseq: FTBFS with Sphinx 1.3: unsupported theme option 'sidebarlinkcolor' given
On Sat, 15 Aug 2015 20:32:09 +0300, Dmitry Shachnev wrote:
Attached is a patch against packaging git master to fix this.
Really attaching the patch now :)
--
Dmitry ShachnevFrom 6f87290cb168fe51d9658a77844acf48aed971bc Mon Sep 17 00:00:00 2001
From: Dmitry Shachnev mity...@gmail.com
Date: Sat, 15 Aug 2015 20:27:32 +0300
Subject: [PATCH] Explicitly specify theme name for Sphinx (closes: #794277).
---
debian/changelog | 3 +++
debian/patches/series | 1 +
debian/patches/use_default_theme.patch | 15 +++
3 files changed, 19 insertions(+)
create mode 100644 debian/patches/use_default_theme.patch
diff --git a/debian/changelog b/debian/changelog
index 8c35c66..6f67c4a 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -18,6 +18,9 @@ htseq (0.6.1p1-1) UNRELEASED; urgency=medium
occuring. Skip these tests for the moment.
* cme fix dpkg-control
+ [ Dmitry Shachnev ]
+ * Explicitly specify theme name for Sphinx (closes: #794277).
+
-- Andreas Tille ti...@debian.org Sat, 25 Oct 2014 00:11:26 +0200
htseq (0.5.4p3-2) unstable; urgency=low
diff --git a/debian/patches/series b/debian/patches/series
index aebdf5e..2a75a1f 100644
--- a/debian/patches/series
+++ b/debian/patches/series
@@ -2,3 +2,4 @@ set-matplotlib-backend.patch
fix_version.patch
add_sphinx_man_pages.patch
skip_tests_with_rounding_differences.patch
+use_default_theme.patch
diff --git a/debian/patches/use_default_theme.patch b/debian/patches/use_default_theme.patch
new file mode 100644
index 000..422d647
--- /dev/null
+++ b/debian/patches/use_default_theme.patch
@@ -0,0 +1,15 @@
+Description: use default/classic HTML theme
+Author: Dmitry Shachnev mity...@debian.org
+Forwarded: no
+Last-Update: 2015-08-15
+
+--- a/doc/conf.py
b/doc/conf.py
+@@ -198,6 +198,7 @@
+ 'Simon Anders', '1'),
+ ]
+
++html_theme = 'default'
+ html_theme_options = {
+ sidebarbgcolor: #00,
+ sidebarlinkcolor: #FFFEFF,
--
2.5.0
signature.asc
Description: OpenPGP digital signature
Bug#795684: tagcloud: FTBFS with perl 5.22 in experimental (MakeMaker changes)
Source: tagcloud Version: 1.4-1.1 Severity: important User: debian-p...@lists.debian.org Usertags: perl-5.22-transition makemaker-prefix Tags: sid stretch This package FTBFS with perl 5.22.0-2, which removed support for a long- obsolete way of overriding PREFIX when calling 'make install' with ExtUtils::MakeMaker, as described in the lintian tag debian-rules-makemaker-prefix-is-deprecated[1] and the Debian Perl policy[2]: /usr/bin/make install PREFIX=`pwd`/debian/tagcloud/usr make[1]: Entering directory '/«PKGBUILDDIR»' ERROR: Can't create '/usr/bin' Do not have write permissions on '/usr/bin' at -e line 1. make[1]: *** [pure_vendor_install] Error 13 Makefile:726: recipe for target 'pure_vendor_install' failed The fix is to use DESTDIR instead of PREFIX; please see the lintian `description for examples. Alternatively, newer versions of debhelper can automatically call make install with the correct arguments when using the dh7 style rules files. This bug will become release critical nearer the time of the perl 5.22 migration, expected during the (northern hemisphere) summer. Cheers, Dominic. [1] https://lintian.debian.org/tags/debian-rules-makemaker-prefix-is-deprecated.html [2] https://www.debian.org/doc/packaging-manuals/perl-policy/ch-module_packages.html#s-vendor_install
Bug#791141: libmusicbrainz3: library transition may be needed when GCC 5 is the default
On Sun, Aug 2, 2015 at 17:43:20 +0200, Sebastian Ramacher wrote: A transition is needed for libmusicbrainz3. I have uploaded an NMU to rename the libmusicbrainz3-6 to libmusicbrainz3-6v5 to experimental. Hi, any particular reason you're changing the library's SONAME instead of leaving it alone and adding Conflicts/Replaces on the old package, which seems to be the more usual pattern? Thanks, Julien signature.asc Description: Digital signature
Bug#795683: vcheck: FTBFS with perl 5.22 in experimental (MakeMaker changes)
Source: vcheck Version: 1.2.1-7 Severity: important User: debian-p...@lists.debian.org Usertags: perl-5.22-transition makemaker-prefix Tags: sid stretch This package FTBFS with perl 5.22.0-2, which removed support for a long- obsolete way of overriding PREFIX when calling 'make install' with ExtUtils::MakeMaker, as described in the lintian tag debian-rules-makemaker-prefix-is-deprecated[1] and the Debian Perl policy[2]: /usr/bin/make install PREFIX=/«PKGBUILDDIR»//usr make[2]: Entering directory '/«PKGBUILDDIR»' Manifying 1 pod document ERROR: Can't create '/usr/bin' Do not have write permissions on '/usr/bin' at -e line 1. make[2]: *** [pure_vendor_install] Error 13 Makefile:730: recipe for target 'pure_vendor_install' failed make[2]: Leaving directory '/«PKGBUILDDIR»' The fix is to use DESTDIR instead of PREFIX; please see the lintian `description for examples. Alternatively, newer versions of debhelper can automatically call make install with the correct arguments when using the dh7 style rules files. This bug will become release critical nearer the time of the perl 5.22 migration, expected during the (northern hemisphere) summer. Cheers, Dominic. [1] https://lintian.debian.org/tags/debian-rules-makemaker-prefix-is-deprecated.html [2] https://www.debian.org/doc/packaging-manuals/perl-policy/ch-module_packages.html#s-vendor_install
Bug#795513: libreoffice-calc: xorg crashes when I click the TT icon
retitle 795513 StylesFormatting crashing X tag 795513 + moreinfo reassign 795513 libreoffice-core found 795513 1:5.0.1~rc1-2 Hi, On Fri, Aug 14, 2015 at 04:14:59PM -0400, Jason Woofenden wrote: Xorg is going down when I click the TT (overlapping capital Ts) icon to the right of the cells in localc. I found the same icon elsewhere in menus with the text Styles and Formatting. I get the same reaction when I click the Styles and Formatting menu item under the Format menu (though it has a different icon there). Hrm. Doesn't crash here in uptodate sid (though on amd64, but that shouldn't make a difference whether X crashes or not) localc's output says: X IO Error xorg.log says: Fatal server error: [ 664.110] (EE) EXA: malloc failed for size -7076128 bytes [ 664.110] (EE) [ 664.110] (EE) I don't see anything like this either (intel...). Just to rule it out - do you also see it on some other system which does not use ati (what you seem to use if I read your provided Xorg log right) Of course, Lo shouldn't crash X anyways, but... Regards, Rene
Bug#795685: biojava4-live: FTBFS: UnknownHostException: eutils.ncbi.nlm.nih.gov
Source: biojava4-live Version: 4.1.0+dfsg-1 Severity: serious Justification: fails to build from source Tags: sid stretch User: reproducible-bui...@lists.alioth.debian.org Usertags: ftbfs X-Debbugs-CC: reproducible-bui...@lists.alioth.debian.org Dear Maintainer, The package fails to build without networking, which we believe is a policy violation. Ubuntu may have a patch, as they also enforce this: [junit] Running org.biojava.nbio.core.sequence.loader.GenbankProxySequenceReaderTest [junit] Testsuite: org.biojava.nbio.core.sequence.loader.GenbankProxySequenceReaderTest [junit] Tests run: 16, Failures: 0, Errors: 8, Skipped: 0, Time elapsed: 0.095 sec [junit] Tests run: 16, Failures: 0, Errors: 8, Skipped: 0, Time elapsed: 0.095 sec [junit] - Standard Error - [junit] SLF4J: Failed to load class org.slf4j.impl.StaticLoggerBinder. [junit] SLF4J: Defaulting to no-operation (NOP) logger implementation [junit] SLF4J: See http://www.slf4j.org/codes.html#StaticLoggerBinder for further details. [junit] - --- [junit] [junit] Testcase: testProteinSequenceFactoring[0] took 0.038 sec [junit] Caused an ERROR [junit] eutils.ncbi.nlm.nih.gov [junit] java.net.UnknownHostException: eutils.ncbi.nlm.nih.gov [junit] at java.net.AbstractPlainSocketImpl.connect(AbstractPlainSocketImpl.java:178) ... [junit] at sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLConnection.java:1301) [junit] at org.biojava.nbio.core.sequence.loader.GenbankProxySequenceReader.getEutilsInputStream(GenbankProxySequenceReader.java:141) [junit] at org.biojava.nbio.core.sequence.loader.GenbankProxySequenceReader.getBufferedInputStream(GenbankProxySequenceReader.java:109) [junit] at org.biojava.nbio.core.sequence.loader.GenbankProxySequenceReader.init(GenbankProxySequenceReader.java:83) [junit] at org.biojava.nbio.core.sequence.loader.GenbankProxySequenceReaderTest.testProteinSequenceFactoring(GenbankProxySequenceReaderTest.java:84) [junit] [junit] Testcase: testFeatures[0] took 0 sec [junit] Testcase: testProteinSequenceFactoring[1] took 0.001 sec [junit] Caused an ERROR [junit] eutils.ncbi.nlm.nih.gov [junit] java.net.UnknownHostException: eutils.ncbi.nlm.nih.gov -- System Information: Debian Release: stretch/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 3.19.0-23-generic (SMP w/8 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system)
Bug#795686: ITP: xserver-xorg-video-amdgpu -- X.Org X server -- AMDGPU video driver
Package: wnpp Severity: wishlist Owner: Timo Aaltonen tjaal...@debian.org X-Debbugs-Cc: debian-de...@lists.debian.org * Package name: xserver-xorg-video-amdgpu Version : 0.0.01~git20150807 Upstream Author : Advanced Micro Devices, Inc. * URL : http://www.x.org * License : MIT/X Programming Lang: C Description : X.Org X server -- AMDGPU video driver This package provides the 'amdgpu' driver for the AMD Radeon cards. The following chip families should be supported: Bonaire, Hawaii, Kaveri, Kabini, Mullins, Iceland, Tonga, Carrizo. . More information about X.Org can be found at: URL:http://www.X.org . This package is built from the X.org xf86-video-amdgpu driver module.
Bug#795644: git-annex: configure eats all memory
Hi, Am Sonntag, den 16.08.2015, 09:45 +0200 schrieb Joachim Breitner: I had a quick tired look yesterday, and I observed that it happens on my machine as well (so it is not mips-specific). It happened when just running ghc --make Setup; ./Setup configure directly, it happened with dpkg-buildpackage -d, but not within sbuild, which creates a clean environment. Furthermore it happend both with and without the libghc -cabal-dev package installed. So it must be something about the environment (environment variables, other packages installed etc.) that causes this. I wonder if the configure is doing something like traversing the whole filesystem which could cause it to do so much more work? I am debugging this by passing +RTS -M300M to Setup configure, to make it abort when it starts eating too much memory. The problem seems to be in Cabal, namely mappend and simplifyCondTree in Distribution.PackageDescription.Configuration. See the attached heap profile and profile file. I obtained these by unpacking the Cabal source and building Setup with $ ghc -O -fforce-recomp --make Setup.hs -rtsopts -prof -auto-all -caf-all -i../haskell-cabal-1.22.1.1/ and then running $ ./Setup configure +RTS -M300M -hc -p -xc (-xc unfortunately does not fire with out-of-heap exceptions) No further conclusion so far. Greetings, Joachim -- Joachim nomeata Breitner Debian Developer nome...@debian.org | ICQ# 74513189 | GPG-Keyid: F0FBF51F JID: nome...@joachim-breitner.de | http://people.debian.org/~nomeata Setup.pdf Description: Adobe PDF document Setup.prof.xz Description: application/xz signature.asc Description: This is a digitally signed message part
Bug#795692: O: openfetion -- open source client implementation of Fetion protocol
Package: wnpp Severity: normal I'm no longer a user of cliofetion for quite some time, and the upstream seems not updating anymore, thus orphaning. Thanks, Aron
Bug#791141: transition: libmusicbrainz3 (GCC 5)
On Sun, Aug 16, 2015 at 11:26:51 +0200, Julien Cristau wrote:
any particular reason you're changing the library's SONAME instead of
leaving it alone and adding Conflicts/Replaces on the old package, which
seems to be the more usual pattern?
Indeed, the standard practice here is to change the binary package name, but
not to change the library soname without upstream coordination because this
will make the Debian binary incompatible with any other third-party binaries
built against the new C++ ABI using upstream sources rather than the Debian
package.
If you want an soname change, this should be done via upstream, not via a
Debian patch to the upstream build system in an NMU.
I'm uploading a new NMU with the attached patch, which brings
libmusicbrainz3 in line with best practices for this transition.
Thanks,
--
Steve Langasek Give me a lever long enough and a Free OS
Debian Developer to set it on, and I can move the world.
Ubuntu Developerhttp://www.debian.org/
slanga...@ubuntu.com vor...@debian.org
diff -u libmusicbrainz3-3.0.2/debian/changelog
libmusicbrainz3-3.0.2/debian/changelog
--- libmusicbrainz3-3.0.2/debian/changelog
+++ libmusicbrainz3-3.0.2/debian/changelog
@@ -1,3 +1,12 @@
+libmusicbrainz3 (3.0.2-2.5) unstable; urgency=medium
+
+ * Non-maintainer upload.
+ * Revert changes to upstream SONAME is previous NMU. The g++5 transition
+should not change upstream sonames without coordination.
+Closes: #791141.
+
+ -- Steve Langasek vor...@debian.org Sun, 16 Aug 2015 09:41:05 +
+
libmusicbrainz3 (3.0.2-2.4) unstable; urgency=medium
* Non-maintainer upload.
diff -u libmusicbrainz3-3.0.2/debian/control
libmusicbrainz3-3.0.2/debian/control
--- libmusicbrainz3-3.0.2/debian/control
+++ libmusicbrainz3-3.0.2/debian/control
@@ -9,6 +9,8 @@
Section: libs
Architecture: any
Depends: ${shlibs:Depends}, ${misc:Depends}
+Conflicts: libmusicbrainz3-6
+Replaces: libmusicbrainz3-6
Description: library to access the MusicBrainz.org database
MusicBrainz is a community music metadatabase that attempts to create a
comprehensive music information site.
reverted:
--- libmusicbrainz3-3.0.2/debian/patches/gcc-5.patch
+++ libmusicbrainz3-3.0.2.orig/debian/patches/gcc-5.patch
@@ -1,18 +0,0 @@
-Description: Bump SONAME for GCC 5 transition
-Author: Sebastian Ramacher sramac...@debian.org
-Last-Update: 2015-08-02
-
libmusicbrainz3-3.0.2.orig/CMakeLists.txt
-+++ libmusicbrainz3-3.0.2/CMakeLists.txt
-@@ -15,8 +15,8 @@
- MATH(EXPR musicbrainz3_SOVERSION_MINOR ${musicbrainz3_SOVERSION_AGE})
- MATH(EXPR musicbrainz3_SOVERSION_PATCH ${musicbrainz3_SOVERSION_REVISION})
-
--SET(musicbrainz3_VERSION
${musicbrainz3_SOVERSION_MAJOR}.${musicbrainz3_SOVERSION_MINOR}.${musicbrainz3_SOVERSION_PATCH})
--SET(musicbrainz3_SOVERSION ${musicbrainz3_SOVERSION_MAJOR})
-+SET(musicbrainz3_VERSION
${musicbrainz3_SOVERSION_MAJOR}v5.${musicbrainz3_SOVERSION_MINOR}.${musicbrainz3_SOVERSION_PATCH})
-+SET(musicbrainz3_SOVERSION ${musicbrainz3_SOVERSION_MAJOR}v5)
-
- SET(CMAKE_MODULE_PATH ${CMAKE_SOURCE_DIR}/cmake/modules)
- FIND_PACKAGE(Neon REQUIRED)
-
signature.asc
Description: Digital signature
Bug#795687: reportbug: Syntax changes in wb nmu command
Package: reportbug Version: 6.6.3 Severity: normal Dear Maintainer, The nmu command had a syntax change which stopped using ALL (as an alias for all architectures) in favour of ANY which makes more sense for us, especially if we start auto-building arch:all packages. I beleive this patch is enough to make reportbug show the new syntax of nmu: diff --git a/reportbug/debbugs.py b/reportbug/debbugs.py index 05b99b0..272a651 100644 --- a/reportbug/debbugs.py +++ b/reportbug/debbugs.py @@ -505,7 +505,7 @@ def handle_debian_release(package, bts, ui, fromaddr, timeout, online=True, http if tag == 'binnmu': reason = ui.get_string(binNMU changelog entry: ) subject = nmu: %s_%s % (package, version) -body= nmu %s_%s . %s . %s . -m \%s\\n % (package, version, archs or ALL, suite, reason) +body= nmu %s_%s . %s . %s . -m \%s\\n % (package, version, archs or ANY, suite, reason) elif tag == 'transition': subject = 'transition: %s' % (package) body= '(please explain about the transition: impacted packages, reason, ...\n' \ Regards, -- Package-specific info: -- System Information: Debian Release: 8.1 APT prefers stable APT policy: (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 3.16.0-4-amd64 (SMP w/2 CPU cores) Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (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) Versions of packages reportbug depends on: ii apt 1.0.9.8 ii python2.7.9-1 ii python-reportbug 6.6.3 pn python:anynone reportbug recommends no packages. Versions of packages reportbug suggests: pn claws-mail none pn debconf-utils none pn debsums none pn dlocate none ii emacs24-bin-common 24.4+1-5 ii file1:5.22+15-2 ii gnupg 1.4.18-7 ii postfix [mail-transport-agent] 2.11.3-1 pn python-gtk2 none pn python-gtkspell none pn python-urwidnone pn python-vte none pn xdg-utils none Versions of packages python-reportbug depends on: ii apt 1.0.9.8 ii python-debian 0.1.27 ii python-debianbts 1.12 pn python:anynone python-reportbug suggests no packages. -- no debconf information -- Mehdi
Bug#795688: commando: FTBFS: failing test: Doctest: commando.conf.AutoProp
Source: commando Version: 0.3.4-1.1 Severity: serious Justification: fails to build from source Tags: sid stretch User: reproducible-bui...@lists.alioth.debian.org Usertags: ftbfs X-Debbugs-CC: reproducible-bui...@lists.alioth.debian.org Dear Maintainer, The package fails to build: dh_auto_test -O--buildsystem=pybuild I: pybuild base:170: cd /commando-0.3.4/.pybuild/pythonX.Y_2.7/build; python2.7 -m nose --with-doctest F == FAIL: Doctest: commando.conf.AutoProp -- Traceback (most recent call last): File /usr/lib/python2.7/doctest.py, line 2226, in runTest raise self.failureException(self.format_failure(new.getvalue())) AssertionError: Failed doctest test for commando.conf.AutoProp File /commando-0.3.4/.pybuild/pythonX.Y_2.7/build/commando/conf.py, line 124, in AutoProp -- File /commando-0.3.4/.pybuild/pythonX.Y_2.7/build/commando/conf.py, line 141, in commando.conf.AutoProp Failed example: 'test' Expected: p.source_dir = 'xyz' p.source_dir Got: 'test' -- File /commando-0.3.4/.pybuild/pythonX.Y_2.7/build/commando/conf.py, line 144, in commando.conf.AutoProp Failed example: 'xyz' Expected nothing Got: 'xyz' -- Ran 1 test in 0.018s FAILED (failures=1) Full build log: https://reproducible.debian.net/rb-pkg/unstable/amd64/commando.html -- System Information: Debian Release: stretch/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 3.19.0-23-generic (SMP w/8 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system)
Bug#760315: ITP: mesos -- Cluster manager for sharing distributed application frameworks
On 16.08.2015 05:02, Dmitry Smirnov wrote: Hi Daniel, It is great to see that you are working on packaging Mesos. For some time already I was also fiddling with its packaging but was (and still) reluctant to take over the RFS... It seems that Mesos have systematic issues with versioning of the libraries from libmesos all the way down to libprocess and libgmock. Because of this it might be best to refrain from packaging standalone libprocess and use its bundled copy (statically linked or installed to private location) until this problem is fixed upstream. My Mesos packaging is in very early draft stage but I might be able to contribute few things if you consider working in public repository (i.e. at collab-maint, etc.). Also due to burden of bundled upstream dependencies I recommend to use shallow (debian/* only) repository layout like the one that KDE team uses: https://pkg-kde.alioth.debian.org/gitguidelines.html Thank you. Hi Dmitry, I going to fix a couple of smaller packages from my WNPP stack before, but I am very interested in this. Thank you for the pointer on the libraries issue here, I'll keep that mind when I get into it, probably I'll approach you on this again, then. Yes, great, if you would like to share your preliminary work that would be very much welcome! I'll keep that in deb/copyright. And ... yes, I'm all right with a repo outline like this, let's do it that way. Greetings, Daniel -- http://www.danielstender.com/blog/ 4096R/DF5182C8 46CB 1CA8 9EA3 B743 7676 1DB9 15E0 9AF4 DF51 82C8
Bug#794774: libstdc++6: Breaks: libboost-date-time1.55.0, but isn't that package fixed now?
On 8 August 2015 at 01:01, jnqnfe jnq...@gmail.com wrote: Further searching has indeed suggested that boost 1.55 is still broken and will remain so (e.g. the bug #793222 discussion), and thus I can see that 1.57/1.58 is needed as you say. In fact 1.58 is available and it's actually just a couple of libreoffice dependencies specifically targeting 1.55 that are causing the hold up in upgrade installation currently (at least here on my systems). It is indeed unfortunate that packages for the gcc5 transition were pushed to unstable before libreoffice was made ready for it, and worse that this has resulted in security implications for Sid users. I must request that those responsible please tread more carefully in future (no disrespect intended, and do I really appreciate the free time and effort put into these projects). While there may sadly be no specific commitment for keeping unstable secure, it has been my impression that the record for pushing security fixes there is pretty strong. I am sure that many Debian users run Sid in order to have a much more up to date collection of application packages than you get from stable (testing does not seem suitable for normal use, since security updates are frequently delayed due to unstable-testing transitions). It would be very much appreciated if devs/maintainers would please keep this in mind in order to not cause problems like this for such users. there is no easy way to do 4k source package transition, without breaking anything, in near instant time... we did stage many of the large abi transitions in experimental, but not all maintainers co-ordinated to do so. Waiting on such a high-level package as libreoffice, falls somewhere between impractical and impossible, as a lot of things have to transition before one can even attempt to validate libreoffice compatibility with the new world order. Debian is not the first one to do this transition, and libreoffice upstream and/or other distributions surely have addressed any /libreoffice/ specific issues that would prevent libreoffice from transitioning by now. As a boost maintainer, I requested said breaks to be put in place. Placing such a breaks is the only sensible way to prevent broken partial upgrades leading to complete runtime breakage. (i.e. runtime exceptions thrown across abi boundaries) Preventing ABI incompatible installations in sid, is higher priority for me, then publishing security fixes of leaf/high-order packages, especially since e.g. release team set the #debian-devel irc channel topic to: Broken: insert your favorite libstdc++6 related breakage Please help with binNMU / transitioning packages in the chain, that lead up to your package, if you want your package to be buildable/installable as soon as possible. libreoffice will not get any preferential treatment in transitions like this, and demanding for such treatment in this or future transitions is counter-productive. Ultimately release team can remove anything from testing to keep transitions flowing, and that may as well be libreoffice as much as any other package, based on release team criteria for e.g. rc bugs and auto-removals. Ditto security uploads to sid, do not trump ongoing transitions. If what you care about is testing, rather than sid, you might be able to file request with release team to use e.g. testing-proposed-updates for a security fix targeting testing, bypassing britney migration unstable. But I do still want to emphasise, that help with the current mass transition would be preferred, as that would be the collaborative least net-effort to get things done. Do you see what I mean? Regards, Dimitri. On Sat, 2015-08-08 at 00:35 +0200, Matthias Klose wrote: Control: severity -1 important On 08/07/2015 09:11 PM, jnqnfe wrote: Control: severity -1 critical Control: tag -1 + security This dependency issue is now blocking installation of security updates on Sid (which many people use instead of stable, whether they should or not), specifically the emergency patch to iceweasel (CVE-2015-4495) in version 38.1.1esr-1. this is unfortunate, however there never was and is any commitment of unstable getting security fixes. The issue is not fixed by any upload of boost1.55 built with GCC 4.9, and it won't build with GCC 5. An update to 1.57 or 1.58 is required. If you need to have such an update in testing, then you should ask for an upload to testing. -- Regards, Dimitri.
Bug#795713: practicalxml-java: FTBFS under some locales (eg. fr_CH.UTF-8)
Source: practicalxml-java Version: 1.1.17-1 Severity: serious Justification: fails to build from source Dear Maintainer, practicalxml-java fails to build from source on unstable/amd64 under some locales (eg. LANG=fr_CH.UTF-8): [..] Running net.sf.practicalxml.converter.bean.TestXml2BeanConverter Tests run: 64, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.188 sec - in net.sf.practicalxml.converter.bean.TestXml2BeanConverter Running net.sf.practicalxml.converter.bean.TestBeanConverter Tests run: 28, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 0.15 sec FAILURE! - in net.sf.practicalxml.converter.bean.TestBeanConverter testDateConversions(net.sf.practicalxml.converter.bean.TestBeanConverter) Time elapsed: 0.027 sec ERROR! net.sf.practicalxml.converter.ConversionException: unable to parse: Thu Aug 29 13:12:27 GMT+14:00 2013 at net.sf.practicalxml.converter.bean.Xml2BeanConverter.parseDateDefault(Xml2BeanConverter.java:515) at net.sf.practicalxml.converter.bean.Xml2BeanConverter.tryConvertAsDate(Xml2BeanConverter.java:281) at net.sf.practicalxml.converter.bean.Xml2BeanConverter.convertWithoutCast(Xml2BeanConverter.java:154) at net.sf.practicalxml.converter.bean.Xml2BeanConverter.convertChildren(Xml2BeanConverter.java:459) at net.sf.practicalxml.converter.bean.Xml2BeanConverter.tryConvertAsBean(Xml2BeanConverter.java:329) at net.sf.practicalxml.converter.bean.Xml2BeanConverter.convertWithoutCast(Xml2BeanConverter.java:158) at net.sf.practicalxml.converter.bean.Xml2BeanConverter.convert(Xml2BeanConverter.java:107) at net.sf.practicalxml.converter.BeanConverter.convertToJava(BeanConverter.java:114) at net.sf.practicalxml.converter.BeanConverter.convertToJava(BeanConverter.java:96) at net.sf.practicalxml.converter.bean.TestBeanConverter.testDateConversions(TestBeanConverter.java:488) Caused by: java.text.ParseException: Unparseable date: Thu Aug 29 13:12:27 GMT+14:00 2013 at java.text.DateFormat.parse(DateFormat.java:357) at net.sf.practicalxml.converter.bean.Xml2BeanConverter.parseDateDefault(Xml2BeanConverter.java:510) ... 31 more Running net.sf.practicalxml.converter.internal.TestTypeUtils Tests run: 6, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.001 sec - in net.sf.practicalxml.converter.internal.TestTypeUtils Running net.sf.practicalxml.converter.internal.TestJavaStringConversions Tests run: 21, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.005 sec - in net.sf.practicalxml.converter.internal.TestJavaStringConversions Running net.sf.practicalxml.converter.internal.TestJsonUtils Tests run: 12, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.002 sec - in net.sf.practicalxml.converter.internal.TestJsonUtils Running net.sf.practicalxml.converter.internal.TestConversionUtils Tests run: 2, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0 sec - in net.sf.practicalxml.converter.internal.TestConversionUtils Running net.sf.practicalxml.TestXsiUtil Tests run: 2, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0 sec - in net.sf.practicalxml.TestXsiUtil Running net.sf.practicalxml.xpath.TestAbstractFunction Tests run: 13, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.027 sec - in net.sf.practicalxml.xpath.TestAbstractFunction Running net.sf.practicalxml.xpath.TestXPathWrapperFactory Tests run: 8, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.056 sec - in net.sf.practicalxml.xpath.TestXPathWrapperFactory Running net.sf.practicalxml.xpath.TestSimpleNamespaceResolver Tests run: 7, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.003 sec - in net.sf.practicalxml.xpath.TestSimpleNamespaceResolver Running net.sf.practicalxml.xpath.TestNamespaceResolver Tests run: 11, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.008 sec - in net.sf.practicalxml.xpath.TestNamespaceResolver Running net.sf.practicalxml.xpath.function.TestXsiBoolean Tests run: 9, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.022 sec - in net.sf.practicalxml.xpath.function.TestXsiBoolean Running net.sf.practicalxml.xpath.function.TestUppercase Tests run: 7, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.016 sec - in net.sf.practicalxml.xpath.function.TestUppercase Running net.sf.practicalxml.xpath.function.TestLowercase Tests run: 7, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.016 sec - in net.sf.practicalxml.xpath.function.TestLowercase Running net.sf.practicalxml.xpath.TestFunctionResolver Tests run: 10, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.008 sec - in net.sf.practicalxml.xpath.TestFunctionResolver Running net.sf.practicalxml.xpath.TestXPathWrapper Tests run: 18, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.085 sec - in
Bug#794214: Info received (SVGDOMImplementation moved into package org.apache.batik.anim.dom)
Patch for third parties should be as simple as: - import org.apache.batik.dom.svg.SVGDOMImplementation; + import org.apache.batik.anim.dom.SVGDOMImplementation;
Bug#795641: lintian: [PATCH] fix common license false positives in new-style copyright files
Control: tags -1 - moreinfo
On 2015-08-16 00:13, Rafael Kitover wrote:
Package: lintian
Version: 2.5.35
Severity: normal
This patch fixes lack-of-common-license-reference false positives in
new-style copyright files when a license refers to one of these common
licenses.
It includes a test for this against all common licenses.
All testsuite tests pass.
The patch is against the debcheckout of lintian.
[...]
Hi,
Thanks for looking in to this.
I do have some concerns with the implementation, see below interleaved.
0001-fix-common-lic.-false-pos.-in-new-style-copyright.patch
From 441f44c5be0fe70d9a86b3ee0cec49430b0c2a9d Mon Sep 17 00:00:00 2001
From: Rafael Kitover rkito...@gmail.com
Date: Sat, 15 Aug 2015 17:50:34 -0400
Subject: [PATCH] fix common lic. false pos. in new-style copyright
Fix false positives for lack of common license references in new-style
copyright files when a license refers to another license, by trying to
parse the file and then checking both the names of the licenses and the
texts.
Add new test for references to common licenses as well.
The test suite passes with these changes.
---
[...]
diff --git a/checks/copyright-file.pm b/checks/copyright-file.pm
index c6e35ef..09b664e 100644
--- a/checks/copyright-file.pm
+++ b/checks/copyright-file.pm
[...]
@@ -373,6 +426,45 @@ sub check_cross_link {
return;
}
+# Checks the name and text of every license in the file against given name
and
+# text check coderefs, if the file is in the new format, if the file is in
the
+# old format only runs the text coderef against the whole file.
+sub check_names_texts {
This is called multiple times. Each time it opens and parses the
copyright file at least once each.
I would like to see this done smarter and less wastefully. Please note
that we have some very large copyright files or/and source packages
producing many binaries with a copyright file in each of them.
Have you looked at the performance of this check on some packages?
Lintian has a few built-in options to help you here:
$ lintian --help=extended | grep perf
--perf-debug turn on performance debugging
--perf-output X send performance logging to file (...)
+my ($name_check, $text_check, $file) = @_;
+
+local $@;
+eval {
+foreach my $paragraph (read_dpkg_control($file)) {
(First read of the file.)
+next
+ unless (keys %$paragraph == 1)
+ ((keys %$paragraph)[0] =~ /^license$/i);
^
Please use exists($paragraph-{'license'}) instead.
+
+my ($license_name, $license_text)
+ = (values %$paragraph)[0] =~ /^([^\r\n]+)\r?\n(.*)\z/s;
+
+my $matches = do {
+local $_ = $license_name || '';
+$name_check-($_);
$name_check is always a single regex. Consider passing it as a qr// and
do a normal regex check here instead of calling a separate sub. This
would also avoid the local $_, which is somewhat expensive.
+ }
+ do {
+local $_ = $license_text || '';
+$text_check-($_);
+ };
If we could avoid the subroutine + local $_; here too that would be nice
as well.
+
+die 'MATCH' if $matches;
+}
+};
+if ($@)
+{ # match or parse error: copyright not in new format, just check text
+return 1 if $@ =~ /^MATCH/;
+
+local $_ = slurp_entire_file($file);
(Second read of the file.)
+return $text_check-($_);
+}
+
+return; # did not match anything
+}
+
1;
# Local Variables:
diff --git
a/t/tests/copyright-file-non-common-license/debian/debian/control.in
b/t/tests/copyright-file-non-common-license/debian/debian/control.in
new file mode 100644
index 000..e80822d
--- /dev/null
+++ b/t/tests/copyright-file-non-common-license/debian/debian/control.in
@@ -0,0 +1,94 @@
+Source: {$source}
+Priority: extra
+Section: {$section}
+Maintainer: {$author}
+Standards-Version: {$standards_version}
+Build-Depends: debhelper (= 9)
+
+Package: copyright-mentions-apache
+Architecture: all
+Depends: $\{shlibs:Depends\}, $\{misc:Depends\}
+Description: checks against common license false positive for Apache
+ Tests against common license false positive for Apache.
+ .
+ This is a test package designed to exercise some feature or tag of
+ Lintian. It is part of the Lintian test suite and may do very odd
+ things. It should not be installed like a regular package. It may
+ be an empty package.
+
+Package: copyright-mentions-apache2
+Architecture: all
+Depends: $\{shlibs:Depends\}, $\{misc:Depends\}
+Description: checks against common license false positive for Apache (2)
+ Tests against
Bug#795717: ruby-thor: FTBFS: ArgumentError: wrong number of arguments (0 for 1+)
Source: ruby-thor
Version: 0.19.1-1
Severity: serious
Justification: fails to build from source
Dear Maintainer,
ruby-thor fails to build from source on unstable/amd64:
[..]
┌──┐
│ Run tests for ruby2.1 from debian/ruby-tests.rake
│
└──┘
RUBYLIB=/tmp/buildd/ruby-thor-0.19.1/debian/ruby-thor/usr/lib/ruby/vendor_ruby:.
rake2.1 -f debian/ruby-tests.rake
/usr/bin/ruby2.1 /usr/bin/rspec --pattern ./spec/\*_spec.rb
..WARNING: Using the `raise_error` matcher without
providing a specific error or message risks false positives, since
`raise_error` will match when Ruby raises a `NoMethodError`,
`NameError` or `ArgumentError`, potentially allowing the expectation
to pass without even executing the method you are intending to call.
Instead consider providing a specific error class or message. This
message can be supressed by setting:
`RSpec::Expectations.configuration.warn_about_potential_false_positives
= false`. Called from
/tmp/buildd/ruby-thor-0.19.1/spec/actions_spec.rb:124:in `block (4
levels) in top (required)'.
.F...WARNING:
Using the `raise_error` matcher without providing a specific error or
message risks false positives, since `raise_error` will match when
Ruby raises a `NoMethodError`, `NameError` or `ArgumentError`,
potentially allowing the expectation to pass without even executing
the method you are intending to call. Instead consider providing a
specific error class or message. This message can be supressed by
setting:
`RSpec::Expectations.configuration.warn_about_potential_false_positives
= false`. Called from
/tmp/buildd/ruby-thor-0.19.1/spec/group_spec.rb:31:in `block (3
levels) in top (required)'.
...**...
Pending: (Failures listed here are expected and do not affect your
suite's status)
1) The library itself has no malformed whitespace
# Temporarily skipped with xit
# ./spec/quality_spec.rb:51
2) The library itself uses double-quotes consistently in specs
# Temporarily skipped with xit
# ./spec/quality_spec.rb:64
Failures:
1) Thor::Command#run runs a command by calling a method in the given
instance
Failure/Error: expect(dub).to receive(:can_has).and_return {
|*args| args }
ArgumentError:
wrong number of arguments (0 for 1+)
# ./spec/command_spec.rb:61:in `block (3 levels) in top
(required)'
Finished in 2.44 seconds (files took 0.75741 seconds to load)
331 examples, 1 failure, 2 pending
Failed examples:
rspec ./spec/command_spec.rb:59 # Thor::Command#run runs a command by
calling a method in the given instance
/usr/bin/ruby2.1 /usr/bin/rspec --pattern ./spec/\*_spec.rb failed
ERROR: Test ruby2.1 failed. Exiting.
dh_auto_install: dh_ruby --install
/tmp/buildd/ruby-thor-0.19.1/debian/ruby-thor returned exit code 1
debian/rules:15: recipe for target 'binary' failed
make: *** [binary] Error 1
dpkg-buildpackage: error: fakeroot debian/rules binary gave error exit
status 2
[..]
The full build log is attached or can be viewed here:
https://reproducible.debian.net/logs/unstable/amd64/ruby-thor_0.19.1-1.build1.log.gz
Regards,
--
,''`.
: :' : Chris Lamb
`. `'` la...@debian.org / chris-lamb.co.uk
`-
I: using fakeroot in build.
I: pbuilder: network access will be disabled during build
I: Current time: Thu Jul 23 07:33:12 GMT+12 2015
I: pbuilder-time-stamp: 1437679992
I: Building the build Environment
I: extracting base tarball [/var/cache/pbuilder/unstable-reproducible-base.tgz]
I: creating local configuration
I: copying local configuration
I: mounting /proc filesystem
I: mounting /run/shm filesystem
I: mounting /dev/pts filesystem
I: Mounting /dev/shm
I: Mounting /sys
I: policy-rc.d already exists
I: Installing the build-deps
- Attempting to satisfy build-dependencies
- Creating pbuilder-satisfydepends-dummy package
Package: pbuilder-satisfydepends-dummy
Version: 0.invalid.0
Architecture: amd64
Maintainer: Debian Pbuilder Team pbuilder-ma...@lists.alioth.debian.org
Description: Dummy package to satisfy dependencies with aptitude - created by
pbuilder
This package was created automatically by pbuilder to satisfy the
build-dependencies of the package being currently built.
Depends: debhelper (= 7.0.50~), gem2deb (= 0.3.0~), ruby-rspec (= 2.13.0~),
ruby-diff-lcs, bundler, rake
dpkg-deb: building package 'pbuilder-satisfydepends-dummy' in
Bug#794444: python3-networkx should conflict with python3-pygraphviz
control: reassign -1 python3-pygraphviz control: forwarded -1 https://github.com/pygraphviz/pygraphviz/issues/65 On Mon, Aug 3, 2015 at 7:52 AM, Johannes Schauer jo...@debian.org wrote: Package: python3-networkx Version: 1.9.1-1 Severity: normal Hi, python3-networkx is able to use python3-pygraphviz as wells as python3-pydot for drawing dot graphs. If both are installed, then the former will be used. Unfortunately it seems that python3-pygraphviz is unable to render graphs with vertex attributes which makes it unfit for drawing all but the most trivial graphs. so this is a bug in pygraphviz Since the presence of python3-pygraphviz will make python3-networkx use it over python3-pydot (which does not suffer from this problem), I suggest that python3-networkx conflicts with python3-pygraphviz until the problem is either fixed in networkx or pygraphviz upstream. To test the problem yourself, try to do the following with python3-pygraphviz installed: python3 -c 'import networkx as nx; G=nx.Graph();G.add_node(1,foo=bar);nx.write_dot(G, out)' The command will never terminate. It on the other hand immediately finishes (as expected) if python3-pygraphviz is not installed but python3-pydot is. This bug is causing problems with my package botch which depends on python3-networkx for graph drawing. Instead of botch conflicting with python3-pygraphviz, I'd like to see this conflict in python3-networkx itself. you might want to read https://www.debian.org/doc/debian-policy/ch-relationships.html#s-conflicts as this is not a case where Conflicts is to be used. Regards, -- Sandro Tosi (aka morph, morpheus, matrixhasu) My website: http://matrixhasu.altervista.org/ Me at Debian: http://wiki.debian.org/SandroTosi
Bug#795716: [libtest-perl-critic-perl] lintian FTBFS with new version
Package: libtest-perl-critic-perl Version: 1.03-1 Severity: serious control: affects -1 lintian Sid version FTBFS whereas testing work fine see https://jenkins.debian.net/job/lintian-tests_sid/ Bastien signature.asc Description: This is a digitally signed message part.
Bug#791250: Do you need any help for pugixml
Quoting Andreas Tille (2015-08-16 13:15:53) On Sat, Aug 15, 2015 at 11:04:31PM +0530, Vasudev Kamath wrote: do you see any chance to fix this soonish or do you need help. I'd volunteer to inject a fix into collab-maint git or upload NMU if you want me to. If you can that would be great!. I'm already working on ctpp2 so I'm not sure if I would manage pugixml this week itself. (I can get free time for Debian mostly on weekends.) Could some of you (ping Jonas?) please double check what I commited to Git? I think it fixed things up to debian/control.in but I have no idea by what magic you create debian/control. It is not created when trying $ debian/rules debian/control sed -e 's/__LIBPKGNAME__/libpugixml1/g' -e 's/__LIBPKGNAMEv5__/libpugixml1v5/g' debian/control.in.in debian/control.in Please either enlighten me how to create debian/control or may be you simply create it and the result should work. Please read README.source. - Jonas -- * Jonas Smedegaard - idealist Internet-arkitekt * Tlf.: +45 40843136 Website: http://dr.jones.dk/ [x] quote me freely [ ] ask before reusing [ ] keep private
Bug#795721: CVE-2015-3259 CVE-2015-3340 CVE-2015-4163 CVE-2015-4164
Source: xen Severity: important Tags: security These Xen vulnerabilities are unfixed in unstable: CVE-2015-4164: http://xenbits.xen.org/xsa/advisory-136.html CVE-2015-4163: http://xenbits.xen.org/xsa/advisory-134.html CVE-2015-3340: http://xenbits.xen.org/xsa/advisory-132.html CVE-2015-3259: http://xenbits.xen.org/xsa/advisory-137.html Cheers, Moritz
Bug#794323: Should xmail be removed?
reassign 794323 ftp.debian.org retitle 794323 RM: xmail thanks On Sat, Aug 01, 2015 at 01:31:37PM +0200, Moritz Muehlenhoff wrote: Package: xmail Severity: serious The last upstream release in was 2010, that's also when the last maintainer upload occured. It has longstanding RC bugs and already missed jessie. popcon is marginal and we have many good mail servers in Debian as alternatives. If anyone disgrees with the removal, please bring the package in shape, otherwise let's reassign this bug to ftp.debian.org for removal. No objections in two weeks, reassigning. Cheers, Moritz
Bug#548399: could you package projectlibre ?
It seems we can download a source code snapshot here : http://sourceforge.net/p/projectlibre/code/ci/master/tarball?path=/projectlibre_core/src
Bug#644897:
Bug#791250: Do you need any help for pugixml
On Sun, Aug 16, 2015 at 02:20:08PM +0200, Jonas Smedegaard wrote: $ debian/rules debian/control sed -e 's/__LIBPKGNAME__/libpugixml1/g' -e 's/__LIBPKGNAMEv5__/libpugixml1v5/g' debian/control.in.in debian/control.in Please either enlighten me how to create debian/control or may be you simply create it and the result should work. Please read README.source. Sorry this does not explain how to create d/control. Your hint says I should ignore what you crafted with probably good reasons I'd like to understand. I can not imagine you want me to edit control.in.in and control manually so why not uncovering the trick. (If not I'll leave the package as is for its real Maintainer who probably knows.) Thanks Andreas. -- http://fam-tille.de
Bug#795728: ruby-docker-api: FTBFS: undefined method `color_enabled=' for #RSpec::Core::Configuration:0x00000000ee72a8
Source: ruby-docker-api
Version: 1.10.10-1
Severity: serious
Justification: fails to build from source
Dear Maintainer,
ruby-docker-api fails to build from source on unstable/amd64:
[..]
Running tests for ruby2.1 using debian/ruby-tests.rb...
RUBYLIB=/tmp/buildd/ruby-docker-api-1.10.10/debian/ruby-docker-api/usr/lib/ruby/vendor_ruby:.
ruby2.1 debian/ruby-tests.rb
/tmp/buildd/ruby-docker-api-1.10.10/spec/spec_helper.rb:13:in `block
in top (required)': undefined method `color_enabled=' for
#RSpec::Core::Configuration:0xee72a8 (NoMethodError)
from /usr/lib/ruby/vendor_ruby/rspec/core.rb:97:in `configure'
from
/tmp/buildd/ruby-docker-api-1.10.10/spec/spec_helper.rb:10:in
`top (required)'
from
/usr/lib/ruby/2.1.0/rubygems/core_ext/kernel_require.rb:55:in
`require'
from
/usr/lib/ruby/2.1.0/rubygems/core_ext/kernel_require.rb:55:in
`require'
from debian/ruby-tests.rb:3:in `block in main'
from debian/ruby-tests.rb:3:in `each'
from debian/ruby-tests.rb:3:in `main'
Loading simplecov-html failed, install ruby-simplecov-html
ERROR: Test ruby2.1 failed. Exiting.
dh_auto_install: dh_ruby --install
/tmp/buildd/ruby-docker-api-1.10.10/debian/ruby-docker-api returned
exit code 1
debian/rules:15: recipe for target 'binary' failed
make: *** [binary] Error 1
dpkg-buildpackage: error: fakeroot debian/rules binary gave error exit
status 2
[..]
The full build log is attached or can be viewed here:
https://reproducible.debian.net/logs/unstable/amd64/ruby-docker-api_1.10.10-1.build1.log.gz
Regards,
--
,''`.
: :' : Chris Lamb
`. `'` la...@debian.org / chris-lamb.co.uk
`-
I: using fakeroot in build.
I: pbuilder: network access will be disabled during build
I: Current time: Fri Jul 17 14:05:46 GMT+12 2015
I: pbuilder-time-stamp: 1437185146
I: Building the build Environment
I: extracting base tarball [/var/cache/pbuilder/unstable-reproducible-base.tgz]
I: creating local configuration
I: copying local configuration
I: mounting /proc filesystem
I: mounting /run/shm filesystem
I: mounting /dev/pts filesystem
I: Mounting /dev/shm
I: Mounting /sys
I: policy-rc.d already exists
I: Installing the build-deps
- Attempting to satisfy build-dependencies
- Creating pbuilder-satisfydepends-dummy package
Package: pbuilder-satisfydepends-dummy
Version: 0.invalid.0
Architecture: amd64
Maintainer: Debian Pbuilder Team pbuilder-ma...@lists.alioth.debian.org
Description: Dummy package to satisfy dependencies with aptitude - created by
pbuilder
This package was created automatically by pbuilder to satisfy the
build-dependencies of the package being currently built.
Depends: debhelper (= 7.0.50~), gem2deb (= 0.6.1~), ruby-rspec,
ruby-simplecov, ruby-excon (= 0.28), ruby-archive-tar-minitar
dpkg-deb: building package 'pbuilder-satisfydepends-dummy' in
'/tmp/satisfydepends-aptitude/pbuilder-satisfydepends-dummy.deb'.
Selecting previously unselected package pbuilder-satisfydepends-dummy.
(Reading database ... 20236 files and directories currently installed.)
Preparing to unpack .../pbuilder-satisfydepends-dummy.deb ...
Unpacking pbuilder-satisfydepends-dummy (0.invalid.0) ...
dpkg: pbuilder-satisfydepends-dummy: dependency problems, but configuring
anyway as you requested:
pbuilder-satisfydepends-dummy depends on gem2deb (= 0.6.1~); however:
Package gem2deb is not installed.
pbuilder-satisfydepends-dummy depends on ruby-rspec; however:
Package ruby-rspec is not installed.
pbuilder-satisfydepends-dummy depends on ruby-simplecov; however:
Package ruby-simplecov is not installed.
pbuilder-satisfydepends-dummy depends on ruby-excon (= 0.28); however:
Package ruby-excon is not installed.
pbuilder-satisfydepends-dummy depends on ruby-archive-tar-minitar; however:
Package ruby-archive-tar-minitar is not installed.
Setting up pbuilder-satisfydepends-dummy (0.invalid.0) ...
Reading package lists...
Building dependency tree...
Reading state information...
Initializing package states...
Writing extended state information...
Building tag database...
The following NEW packages will be installed:
ca-certificates{a} devscripts{a} dh-python{a} gem2deb{a}
gem2deb-test-runner{a} libexpat1{a} libgmp-dev{a} libgmpxx4ldbl{a}
libmpdec2{a} libpython3-stdlib{a} libpython3.4-minimal{a}
libpython3.4-stdlib{a} libruby2.1{a} libruby2.2{a} libssl1.0.0{a}
libyaml-0-2{a} mime-support{a} openssl{a} python3{a} python3-chardet{a}
python3-debian{a} python3-minimal{a} python3-pkg-resources{a}
python3-six{a} python3.4{a} python3.4-minimal{a} ruby{a} ruby-all-dev{a}
ruby-archive-tar-minitar{a} ruby-diff-lcs{a} ruby-excon{a}
ruby-minitest{a} ruby-multi-json{a} ruby-power-assert{a} ruby-rspec{a}
ruby-rspec-core{a} ruby-rspec-expectations{a} ruby-rspec-mocks{a}
ruby-rspec-support{a} ruby-setup{a} ruby-simplecov{a} ruby-test-unit{a}
Bug#795645: libbotan-1.10-0: library transition needed now that GCC 5 is the default
Then I just missed it. I'll close this when I'm not on my phone. Sorry for the confusion. Scott K On August 16, 2015 4:39:46 AM EDT, Ondřej Surý ond...@sury.org wrote: Now that I am on my computer instead of the phone with unfixed security errors (just a random rant on Android security), I can add a previous bug number: #790987 Cheers, Ondrej On Sun, Aug 16, 2015, at 08:10, Ondřej Surý wrote: Hi Scott, as far as I know I already prepared the transition and reassigned it to release.d.o. Is this something new or just an oversight? Ondřej On August 16, 2015 12:52:36 AM GMT+02:00, Scott Kitterman deb...@kitterman.com wrote: Package: libbotan-1.10-0 Version: 1.10.8-2 Severity: important Background [1]: libstdc++6 introduces a new ABI to conform to the C++11 standard, but keeps the old ABI to not break existing binaries. Packages which are built with g++-5 from experimental (not the one from testing/unstable) are using the new ABI. Libraries built from this source package export some of the new __cxx11 or B5cxx11 symbols, and dropping other symbols. If these symbols are part of the API of the library, then this rebuild with g++-5 will trigger a transition for the library. What is needed (note: this is the standard libstdc++6 bug template with some updates/additions): - Rebuild the library using g++/g++-5 from experimental. Note that most likely all C++ libraries within the build dependencies need a rebuild too. You can find the log for a rebuild in https://people.debian.org/~doko/logs/gcc5-20150701/ Search for BEGIN GCC CXX11 in the log. https://people.debian.org/~doko/logs/gcc5-20150701/botan1.10_1.10.8-2_unstable_gcc5.log - Decide if the symbols matching __cxx11 or B5cxx11 are part of the library API, and are used by the reverse dependencies of the library. - If there are no symbols matching __cxx11 or B5cxx11 in the symbols forming the library API, you should close this issue with a short explanation. - If there are no reverse dependencies, it should be the package maintainers decision if a transition is needed. However this might break software which is not in the Debian archive, and built against these packages. - If a library transition is needed, please prepare for the change. Rename the library package, append v5 to the name of the package (e.g. libfoo2 - libfoo2v5). Such a change can be avoided, if you have a soversion bump and you upload this version instead of the renamed package. Prepare a patch and attach it to this issue (mark this issue with patch), so that it is possible to NMU such a package. We'll probably have more than hundred transitions triggered. Then reassign the issue to release.debian.org and properly tag it as a transition issue, by sending an email to cont...@bugs.debian.org: user release.debian@packages.debian.org usertag this issue + transition block this issue by 790756 reassign this issue release.debian.org - If unsure if a transition is needed, please tag the issue with help to ask for feedback from other Debian developers. The libstdc++6 transition will be a large one, and it will come with a lot of pain. Please help it by preparing the follow-up transitions. [1] https://wiki.debian.org/GCC5#libstdc.2B-.2B-_ABI_transition Additional information: A transition is needed. Ovito will FTBFS unless both botan1.10 and qscintilla2 are updated (I discovered this preparing the qscintilla2 transition). -- Ondřej Surý -- Ondřej Surý ond...@sury.org Knot DNS (https://www.knot-dns.cz/) – a high-performance DNS server
Bug#795716: [libtest-perl-critic-perl] lintian FTBFS with new version
On Sun, 16 Aug 2015 14:17:14 +0200, Bastien ROUCARIÈS wrote: Package: libtest-perl-critic-perl Version: 1.03-1 Severity: serious control: affects -1 lintian Sid version FTBFS whereas testing work fine see https://jenkins.debian.net/job/lintian-tests_sid/ That's not an actionable bug report. If you can add more information (like what Niels hinted at on IRC), i can forward the issue upstream. Cheers, gregor -- .''`. Homepage: http://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 `- signature.asc Description: Digital Signature
Bug#795716: [libtest-perl-critic-perl] lintian FTBFS with new version
On Sun, 16 Aug 2015 15:20:53 +0200 gregor herrmann gre...@debian.org
wrote:
On Sun, 16 Aug 2015 14:17:14 +0200, Bastien ROUCARIÈS wrote:
Package: libtest-perl-critic-perl
Version: 1.03-1
Severity: serious
control: affects -1 lintian
Sid version FTBFS whereas testing work fine see
https://jenkins.debian.net/job/lintian-tests_sid/
That's not an actionable bug report.
If you can add more information (like what Niels hinted at on IRC), i
can forward the issue upstream.
Cheers,
gregor
--
.''`. Homepage: http://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
`-
The symptom is:
$ perl -Ilib t/scripts/01-critic/docs-examples.t
1..1
# Subtest: Critic all code in doc/examples/checks
ok - Test::Perl::Critic for
doc/examples/checks/my-vendor/another-check.pm
ok - Test::Perl::Critic for doc/examples/checks/my-vendor/some-check.pm
1..2
not ok 1 - No tests run for subtest Critic all code in doc/examples/checks
# Failed test 'No tests run for subtest Critic all code in
doc/examples/checks'
# at t/scripts/01-critic/docs-examples.t line 47.
# Looks like you failed 1 test of 1.
We run the all_critic_ok in a subtest like so:
# all_critic_ok emits its own plan, so run it in a subtest
# so we can just count it as one test.
subtest Critic all code in $arg = sub {
all_critic_ok($arg);
};
This seems to be broken by upstream, which is now running all the
critic_ok tests in a subprocess (via mce_grep). This means that
all_critic_ok in total do 0 tests!
Thanks,
~Niels
Bug#795682: O: pygccxml -- specialized XML reader reads the output from gccxml
Package: wnpp Severity: normal I'm no longer a user of pygccxml for quite some time and is not really motivated to continue maintaining it, thus orphaning. Thanks, Aron
Bug#792736: gtk+3.0 fails to build twice in a row
Control: tag -1 + patch
The following patch fixes the problem:
Index: debian/changelog
===
--- debian/changelog(revision 45647)
+++ debian/changelog(working copy)
@@ -1,8 +1,12 @@
gtk+3.0 (3.16.6-2) UNRELEASED; urgency=medium
+ [ Simon McVittie ]
* d/p/073-Use-AC_USE_SYSTEM_EXTENSIONS-to-get-_GNU_SOURCE-_XOP.patch:
remove, applied upstream in 3.13 and no longer listed in series
+ [ Uwe Kleine-König ]
+ * remove debian/{build,install} in clean target (Closes: 792736)
+
-- Simon McVittie s...@debian.org Wed, 05 Aug 2015 12:07:50 +0100
gtk+3.0 (3.16.6-1) unstable; urgency=medium
Index: debian/rules
===
--- debian/rules(revision 45647)
+++ debian/rules(working copy)
@@ -156,6 +156,7 @@
touch debian/control.in
rm -f $(call dh_subst_files,$(DEB_ALL_PACKAGES))
rm -f testsuite/reftests/*.ui.known_fail
+ rm -rf debian/build debian/install
pre-build::
# Mark reftests with known failures as non-fatal
I'm a bit unsure though if the fix is right as is or if it's cdbs which
should clean up automatically.
Best regards
Uwe
Bug#795643: RFS: graywolf/0.1.2-2
BuiltSignedUploaded, thanks for your contribution to Debian! Thanks a lot Gianfranco! I really appreciate it. It seems like Andreas was exactly 10 minutes before you though ;) So thanks a lot to both of you! I might wait longer before adding it to Andreas' SoB next time, but this time I was thinking that the upload was quite urgent. Best regards, Ruben
Bug#773787: hot: hot.hs:74:51-71: Non-exhaustive patterns in lambda
On Sun, Aug 16, 2015 at 10:28:58AM +0200, Joachim Breitner wrote: it’s been a while, but I believe I wanted the PGP signature removed, so that grep-dctrl would process the file. Okay, I think that would be a good feature as a different subcommand.
Bug#795695: O: pidgin-openfetion -- Fetion protocol plugin for libpurple
Package: wnpp Severity: normal I'm no longer a user of cliofetion for quite some time, and the upstream seems not updating anymore, thus orphaning. Thanks, Aron
Bug#795698: multiverse-core: FTBFS with gradle 2.5
Source: multiverse-core
Version: 0.7.0-3
Severity: important
Tags: patch
I would like to upload gradle 2.5 to unstable. multiverse-core is one
of the packages that is blocking this.
Apparently this package uses a removed gradle method, mavenRepo, which causes
it to fail to build from source.
We could either replace mavenRepo with maven but I think removing the
whole repository paragraph in gradle.build is also a safe solution
because it is unused anyway.
Attached is patch that works for me.
Markus
From: Markus Koschany a...@gambaru.de
Date: Sun, 16 Aug 2015 09:50:27 +
Subject: mavenRepo
---
build.gradle | 8
1 file changed, 8 deletions(-)
diff --git a/build.gradle b/build.gradle
index 6667789..bd48828 100644
--- a/build.gradle
+++ b/build.gradle
@@ -47,14 +47,6 @@ project(':multiverse-core') {
title = Multiverse Core $version
}
-repositories {
-mavenRepo(url: localMavenRepo)
-mavenCentral()
-mavenRepo(url: 'http://download.java.net/maven/2/')
-mavenRepo(url: 'https://maven.atlassian.com/content/groups/public')
-mavenRepo(url: 'http://snapshots.repository.codehaus.org')
-}
-
dependencies {
testCompile group: 'junit', name: 'junit', version: '4.10'
testCompile group: 'org.mockito', name: 'mockito-all', version: '1.9.0'
Bug#795699: mcabber: Please package version 1.0.0
Package: mcabber Version: 1.0.0 Severity: minor Dear Maintainer, mcabber 1.0.0 has been released on 2015/06/28. Would you please consider packaging it? Kind regards Daniel
Bug#777844: etsf-io: ftbfs with GCC-5
I'm fortran-illiterate but by digging through commands used by ./configure in sid I was finally able to extract understandable error message, saying use netcdf 1 Fatal Error: Cannot read module file 'netcdf.mod' opened at (1), because it was created by a different version of GNU Fortran compilation terminated. By obtaining source of netcfg, compiling and installing that in SID made this package to successfully build too so this package is not errorneus and listed in https://release.debian.org/transitions/html/auto-netcdf.html for a reason. -- Antti Järvinen
Bug#791250: Do you need any help for pugixml
Hi, On Sat, Aug 15, 2015 at 11:04:31PM +0530, Vasudev Kamath wrote: do you see any chance to fix this soonish or do you need help. I'd volunteer to inject a fix into collab-maint git or upload NMU if you want me to. If you can that would be great!. I'm already working on ctpp2 so I'm not sure if I would manage pugixml this week itself. (I can get free time for Debian mostly on weekends.) Could some of you (ping Jonas?) please double check what I commited to Git? I think it fixed things up to debian/control.in but I have no idea by what magic you create debian/control. It is not created when trying $ debian/rules debian/control sed -e 's/__LIBPKGNAME__/libpugixml1/g' -e 's/__LIBPKGNAMEv5__/libpugixml1v5/g' debian/control.in.in debian/control.in Please either enlighten me how to create debian/control or may be you simply create it and the result should work. Hope this helps Andreas. -- http://fam-tille.de
Bug#795702: ITP: ruby-asetus -- configuration library with YAML/JSON/TOML backends
Package: wnpp Severity: wishlist Owner: Jonas Genannt jonas.gena...@capi2name.de -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 * Package name: ruby-asetus Version : 0.0.3 Upstream Author : Saku Ytti s...@ytti.fi * URL : https://github.com/ytti/asetus * License : Apache 2.0 Programming Lang: Ruby Description : configuration library with YAML/JSON/TOML backends Asetus is a ruby library that provides a easy method to acccess configuration files. Available backends are: - YAML - JSON - TOML Maintained by the Ruby Team -BEGIN PGP SIGNATURE- Version: GnuPG v1 iQIcBAEBCAAGBQJV0HMGAAoJEPBM7/YBbP/QNawP/2nQ1/EZbCWIxsERGJ5s46dM hvjdqg+ppS0TCJMi589RQInAXREI8Eg89m5v5G0S7Qx5xqmGTAkkCWARlowQ6uhv zl193TV67Lmq/6wZSZsE33ldgJq+ODM9pRv4jv+OQ9zJ1X+zBuu4dazqEZZFbH8g Dipwc6dr0Cog7CFI4+jVykbc4StZTYrPIBrP9NwY4V30eo8ATuJCTqW0G/dRU/qU fw3r9Ao2k9R1J7NUUaUAVCMgMpzJbliAh2gBR7gs1qRn0tK9m3NOuMHwe9niYJxN f+7vNgtox3SVisiKX856mO+48p6Xd3+7579jXXm9U5d/AQhxKzNSJ0mMAIaI9ND9 bdH023rFMTxMMIS0SUvYD6e1owt4ECOCefsG6XDV1+m3ViW1M+RQQg3wi4bTRtAB U3Ism/qWKfGRmn5b8tvK8RHi8rkDlNUAEzJH/B8VdskczNiLaf5jVZyCjrgPslVV K6kzoysnrZ9BXZcGqD7NQow/R9jYSeaiuPvkO+JXDg3rO7GpyD6Evmd997wifkCH LeDCVYhqAOery2UFvnIn+Q1c+8kpm9Mawc5z/DLpamRtQ2ePBcoBxd0OGSrogRdW KVQ8zltOfiXEiNI3vYkoaGArKrPJI3IEx/b+kbwDqdcZKlTdFwIvp7nR8lEVwj2A 8msjQzY6I1VXbJFIYsp8 =ycF1 -END PGP SIGNATURE-
Bug#795701: ITP: trojita -- Fast Qt IMAP e-mail client.
Package: wnpp Severity: wishlist X-Debbugs-CC: debian-de...@lists.debian.org --- Please fill out the fields below. --- Package name: trojita Version: 0.5 Upstream Author: Jan Kundrát j...@flaska.net URL: http://trojita.flaska.net License: GPL-2+ Description: Fast Qt IMAP e-mail client. Trojita is a Qt IMAP e-mail client which: * Enables you to access your mail anytime, anywhere. * Does not slow you down. If we can improve the productivity of an e-mail user, we better do. * Respects open standards and facilitates modern technologies. We value the vendor-neutrality that IMAP provides and are committed to be as interoperable as possible. * Is efficient — be it at conserving the network bandwidth, keeping memory use at a reasonable level or not hogging the system's CPU. * Can be used on many platforms. One UI is not enough for everyone, but our IMAP core works fine on anything from desktop computers to cell phones and big ERP systems. * Plays well with the rest of the ecosystem. We don't like reinventing wheels, but when the existing wheels quite don't fit the tracks, we're not afraid of making them work.
Bug#795705: scribus: Missing Desktop menu entry
Package: scribus Version: 1.4.5+dfsg1-1 Severity: minor Dear Maintainer, After installing Scribus, no entry appear in Desktop menu (at least for xfce menu) under the Graphics section, nor anywhere else. Thanks. -- System Information: Debian Release: stretch/sid APT prefers testing APT policy: (500, 'testing') Architecture: i386 (i686) Kernel: Linux 4.1.0-1-686-pae (SMP w/2 CPU cores) Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages scribus depends on: ii ghostscript9.16~dfsg-2 ii libc6 2.19-19 ii libcairo2 1.14.2-2 ii libcups2 2.0.3-10 ii libfontconfig1 2.11.0-6.3 ii libfreetype6 2.5.2-4 ii libgcc11:5.1.1-14 ii libhunspell-1.3-0 1.3.3-3 ii libhyphen0 2.8.8-2 ii libjpeg62-turbo1:1.4.1-1 ii liblcms2-2 2.6-3+b3 ii libpodofo0.9.0 0.9.0-1.2+b2 ii libpython2.7 2.7.10-3 ii libqt4-network 4:4.8.7+dfsg-1 ii libqt4-xml 4:4.8.7+dfsg-1 ii libqtcore4 4:4.8.7+dfsg-1 ii libqtgui4 4:4.8.7+dfsg-1 ii libstdc++6 5.1.1-14 ii libtiff5 4.0.3-13 ii libxml22.9.1+dfsg1-5 ii python-tk 2.7.9-1 ii scribus-data 1.4.5+dfsg1-1 ii zlib1g 1:1.2.8.dfsg-2+b1 Versions of packages scribus recommends: ii cups-bsd 2.0.3-10 ii fonts-dejavu 2.35-1 ii fonts-liberation 1.07.4-1 ii hyphen-sh [hyphen-hyphenation-patterns] 1:3.3.0-4 ii icc-profiles-free2.0.1+dfsg-1 ii xfonts-scalable 1:1.0.3-1.1 Versions of packages scribus suggests: pn icc-profiles none pn scribus-docnone pn scribus-template none pn texlive-latex-recommended none -- no debconf information
Bug#795704: RFS: mlucas/14.1-dfsg1 [ITP] -- program to perform Lucas-Lehmer test on a Mersenne number
Package: sponsorship-requests Severity: wishlist Dear mentors, I am looking for a sponsor for my package mlucas * Package name: mlucas Version : 14.1-dfsg1 Upstream Author : * URL : http://hogranch.com/mayer/README.html * License: GPL-2+ Section : math It builds those binary packages: mlucas - program to perform Lucas-Lehmer test on a Mersenne number To access further information about this package, please visit the following URL: http://mentors.debian.net/package/mlucas Alternatively, one can download the package with dget using this command: dget -x http://mentors.debian.net/debian/pool/main/m/mlucas/mlucas_14.1-dfsg1.dsc Changes since the last upload: mlucas (14.1-dfsg1) UNRELEASED; urgency=low * Initial release (Closes: #786656) -- Alex Vong alexvong1...@gmail.com Sun, 02 Aug 2015 03:13:37 +0800 Cheers, Alex Vong
Bug#795707: prerotate path argument includes olddir
Package: logrotate
Version: 3.8.1-4
When olddir and prerotate are set, the absolute path to the log
file passed to prerotate includes the olddir.
$ cat test-sdk
/tmp/sdk/message.log.2015-08-15 {
olddir rotated
rotate 0
dateext
dateformat
daily
missingok
notifempty
nocreate
nocompress
nosharedscripts
prerotate
echo $1
exit 1
endscript
}
$ logrotate -f -v test-sdk
reading config file test-sdk
olddir is now rotated
Handling 1 logs
rotating pattern: /tmp/sdk/message.log.2015-08-15 forced from command
line (no old logs will be kept)
olddir is rotated, empty log files are not rotated, old logs are removed
considering log /tmp/sdk/message.log.2015-08-15
log needs rotating
rotating log /tmp/sdk/message.log.2015-08-15, log-rotateCount is 0
Converted '' - ''
dateext suffix ''
glob pattern ''
glob finding old rotated logs failed
running prerotate script
/tmp/sdk/rotated/message.log.2015-08-15
error: error running non-shared prerotate script for
/tmp/sdk/message.log.2015-08-15 of '/tmp/sdk/message.log.2015-08-15 '
I suggest that the absolute path to the log file passed to prerotate
doesn't include the olddir.
postrotate includes the olddir.
--
mandi, Marco
Bug#794214: org.apache.batik.dom.svg.SVGDOMImplementation
On Sun, Aug 16, 2015 at 1:53 PM, Erich Schubert er...@debian.org wrote: Hi, ELKI now tries to load the class dynamically, from different packages. I don't know if this is the proper way to get the DOM implementation, but it was the only one I got working. It is not yet fixed in the Debian package. We're in the process of preparing the next release. Maybe a simple compatibility hack would be to include two copies of the class, in both the old and the new location, but that bears the danger of people continuing to use the old location... I wish there was a well-documented solution. For reference: http://stackoverflow.com/a/30250306/136285
Bug#795708: /usr/bin/ogg123: ogg123: Metadata_block_picture comments spew base64 all over the screen
Package: vorbis-tools Version: 1.4.0-6 Severity: normal File: /usr/bin/ogg123 Ogg Vorbis files have the possibility to include cover art as base64 encoded Metadata_block_picture[1] comments. ogg123 appear to display these Metadata_block_picture comments the same way as any regular text comment. The result being a screen full of base64 encoding, blocking out any other comments. [1]: https://wiki.xiph.org/VorbisComment#METADATA_BLOCK_PICTURE -- System Information: Debian Release: stretch/sid APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 4.1.0-1-amd64 (SMP w/4 CPU cores) Locale: LANG=sv_SE.UTF-8, LC_CTYPE=sv_SE.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages vorbis-tools depends on: ii libao4 1.1.0-3 ii libc62.19-19 ii libcurl3-gnutls 7.44.0-1 ii libflac8 1.3.1-4 ii libogg0 1.3.2-1 ii libspeex11.2~rc1.2-1 ii libvorbis0a 1.3.4-2 ii libvorbisenc21.3.4-2 ii libvorbisfile3 1.3.4-2 vorbis-tools recommends no packages. vorbis-tools suggests no packages. -- no debconf information
Bug#795709: mozc: allow parallel building
Package: src:mozc Tags: patch mozc's d/rules file now hard codes jobs=1, which makes the build slow on architectures that come with many cores but not powerful enough per core (arm, mips, etc). This patch adds the check of Debian's standard environmental variable DEB_BUILD_OPTIONS for the numbers of concurrent jobs to be used. Regards, Aron From c53ba7d1a5865baf313a17bbd8460c3c8c9d27ba Mon Sep 17 00:00:00 2001 From: Aron Xu a...@debian.org Date: Sun, 16 Aug 2015 19:52:16 +0800 Subject: [PATCH] Allow parallel building --- debian/rules | 9 +++-- 1 file changed, 7 insertions(+), 2 deletions(-) diff --git a/debian/rules b/debian/rules index 719915e..19e75c7 100755 --- a/debian/rules +++ b/debian/rules @@ -9,6 +9,11 @@ LDFLAGS:=$(shell dpkg-buildflags --get LDFLAGS) -Wl,--as-needed DEB_BUILD_MULTIARCH :=$(shell dpkg-architecture -qDEB_BUILD_MULTIARCH) +NUMJOBS=1 +ifneq (,$(filter parallel=%,$(DEB_BUILD_OPTIONS))) + NUMJOBS = $(patsubst parallel=%,%,$(filter parallel=%,$(DEB_BUILD_OPTIONS))) +endif + # clear XDG_CONFIG_DIRS for qtchooser unexport XDG_CONFIG_DIRS @@ -28,7 +33,7 @@ CHANGELOG_VARS := $(shell dpkg-parsechangelog | \ SOURCE_VERSION := $(call vafilt,$(CHANGELOG_VARS),Version) %: - dh $@ + dh $@ --parallel override_dh_auto_configure: GYP_DEFINES=use_libprotobuf=1 python build_mozc.py gyp \ @@ -36,7 +41,7 @@ override_dh_auto_configure: --build_base=$(BUILD_DIR) override_dh_auto_build: - V=1 python build_mozc.py build $(TARGETS) -c Release --jobs=1 + V=1 python build_mozc.py build $(TARGETS) -c Release --jobs=$(NUMJOBS) override_dh_auto_clean: python build_mozc.py clean -- 2.1.4
Bug#795710: Perl warning about length @ARGV
Package: dgit Versio: 1.2 Severity: serious Andrew Shadura writes (Bug#795665: dgit doesn't work with symlinked tarballs): Also, with dgit 1.2 I have this: $ git reset --hard HEAD is now at ad6cd93 Update the changelog. $ git diff $ dgit build length() used on @ARGV (did you mean scalar(@ARGV)?) at /usr/bin/dgit line 3164. Format `3.0 (quilt)', checking/updating patch stack blkreplay_1.0.orig.tar.gz No such file or directory at /usr/bin/dgit line 2786.
