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
Processed: Re: ctpp2: ftbfs, and library transition is needed when GCC 5 is the default
Processing control commands: tag -1 +pending Bug #791016 [src:ctpp2] ctpp2: library transition may be needed when GCC 5 is the default Added tag(s) pending. -- 791016: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=791016 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
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#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#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#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#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#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#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#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#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#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#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
Processed: tagging 795646
Processing commands for cont...@bugs.debian.org: tags 795646 + pending Bug #795646 [src:rrdtool] rrdtool: Uses Multi-Arch: no which is not supported by the infrastructure Added tag(s) pending. thanks Stopping processing here. Please contact me if you need assistance. -- 795646: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=795646 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
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#788972: marked as done (routes: FTBFS with Sphinx 1.3: unknown theme options)
Your message dated Sun, 16 Aug 2015 09:39:04 +
with message-id e1zqupa-0008if...@franck.debian.org
and subject line Bug#788972: fixed in routes 2.2-1
has caused the Debian Bug report #788972,
regarding routes: FTBFS with Sphinx 1.3: unknown theme options
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
788972: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=788972
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
---BeginMessage---
Source: routes
Version: 2.0-1
User: python-modules-t...@lists.alioth.debian.org
Usertags: sphinx1.3
routes FTBFS with Sphinx 1.3 (which is available in experimental):
PYTHONPATH=. sphinx-build -N -q -E -b html docs/ \
debian/python-routes/usr/share/doc/python-routes/html/
[...]
Theme error:
unsupported theme option 'relbarlinkcolor' given
debian/rules:21: recipe for target 'build-docs' failed
There is a new default theme (alabaster) in Sphinx 1.3 [1], which
has a different set of options [2].
You can use the old default by explicitly specifying
“html_theme = 'classic'” in docs/conf.py.
There are also many other errors during docs build, but they
are non-fatal (but it would be nice to get them fixed anyway).
This affects the experimental version (2.1) as well.
[1]: http://sphinx-doc.org/theming.html#builtin-themes
[2]: https://pypi.python.org/pypi/alabaster#theme-options
--
Dmitry Shachnev
signature.asc
Description: OpenPGP digital signature
---End Message---
---BeginMessage---
Source: routes
Source-Version: 2.2-1
We believe that the bug you reported is fixed in the latest version of
routes, which is due to be installed in the Debian FTP archive.
A summary of the changes between this version and the previous one is
attached.
Thank you for reporting the bug, which will now be closed. If you
have further comments please address them to 788...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Piotr Ożarowski pi...@debian.org (supplier of updated routes package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Format: 1.8
Date: Sun, 16 Aug 2015 10:09:09 +0200
Source: routes
Binary: python-routes python3-routes
Architecture: source all
Version: 2.2-1
Distribution: unstable
Urgency: medium
Maintainer: Piotr Ożarowski pi...@debian.org
Changed-By: Piotr Ożarowski pi...@debian.org
Description:
python-routes - Routing Recognition and Generation Tools
python3-routes - Routing Recognition and Generation Tools for Python 3
Closes: 788972
Changes:
routes (2.2-1) unstable; urgency=medium
.
* New upstream release
- requires Sphinx = 1.3 (also closes: 788972)
- add remove_missing_todo_include_from_docs patch
* Add python{,3}-six to Build-Depends (and Depends, via dh_python*)
* debian/watch: use pypi.debian.net redirector
Checksums-Sha1:
6d12a1f66e698679e6d138e0176d40c032b41f09 2180 routes_2.2-1.dsc
b67d402659181d577e1462bfd41b3a8bd9ab746b 180011 routes_2.2.orig.tar.gz
601b0c595c71e948a0572cfb2795993230500264 5420 routes_2.2-1.debian.tar.xz
2cfb9dca1f4af0ae6445498fb84820b830c79788 81620 python-routes_2.2-1_all.deb
ef3db937d68949d1cba4a5d5ee785fac2416a09b 29270 python3-routes_2.2-1_all.deb
Checksums-Sha256:
b3c9c74b3106e10c76482af4dc2857d743958e845361b7f69f26bca09e137e07 2180
routes_2.2-1.dsc
9fa78373d63e36c3d8af6e33cfcad743f70c012c7ad6f2c3bf89ad973b9ab514 180011
routes_2.2.orig.tar.gz
ece0e8ed96d99a7876e337a4a3fdc9213cd508e66e0716a81c0badc1cba56a00 5420
routes_2.2-1.debian.tar.xz
b84498945a52ec3555df7da52db1d143aeca3f8a4185300dbc5ce6cc84d7f8b8 81620
python-routes_2.2-1_all.deb
1e1bc25525464682032e6d9b35b9023ea6104dc3250c3acb0e37a9fb94ef86bb 29270
python3-routes_2.2-1_all.deb
Files:
bdb0b28b315687b9c73e98189a25a8fd 2180 python optional routes_2.2-1.dsc
d62bb225ba7919b5470095528932648b 180011 python optional routes_2.2.orig.tar.gz
ee68e323146f1191248e49505b49c850 5420 python optional
routes_2.2-1.debian.tar.xz
c91fe5a4bdbee4f87c42c0f148d9fbde 81620 python optional
python-routes_2.2-1_all.deb
5ebd0980d1d298f9198cb8a32a59b3c3 29270 python optional
python3-routes_2.2-1_all.deb
-BEGIN PGP SIGNATURE-
Version: GnuPG v1
iQIcBAEBCgAGBQJV0FayAAoJEK728aKnRXZFpfoQAIhSm6G4dsDHsmUFgAtzhCQm
Ge9PCP1ZkNSP9islvjmzd6W/np9PtXUiW1oqe1McyrTEHjMnuavcNcZxO3Txrxvl
tUPxBGR0Fkln/IZKIvd0n3M/p4897+J7P7AYeKDoFIjyjKms0fOi8tg6ooU0o+uv
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)
Processed: fixed 795453 in 2015.1.0-4
Processing commands for cont...@bugs.debian.org: fixed 795453 2015.1.0-4 Bug #795453 [src:glance] glance: CVE-2015-5163: Glance v2 API host file disclosure through qcow2 backing file Marked as fixed in versions glance/2015.1.0-4. thanks Stopping processing here. Please contact me if you need assistance. -- 795453: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=795453 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
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#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#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#795713: marked as done (practicalxml-java: FTBFS under some locales (eg. fr_CH.UTF-8))
Your message dated Sun, 16 Aug 2015 13:14:10 +0100 with message-id 1439727250.1979272.357439313.162b5...@webmail.messagingengine.com and subject line Re: Bug#795713: Acknowledgement (practicalxml-java: FTBFS under some locales (eg. fr_CH.UTF-8)) has caused the Debian Bug report #795713, regarding practicalxml-java: FTBFS under some locales (eg. fr_CH.UTF-8) to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 795713: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=795713 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- 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
Processed: blocking bugs
Processing commands for cont...@bugs.debian.org: block 793873 by 747990 Bug #793873 [src:gcc-4.6] gcc-4.6: should not be released with stretch 793873 was not blocked by any bugs. 793873 was not blocking any bugs. Added blocking bug(s) of 793873: 747990 block 793873 by 747980 Bug #793873 [src:gcc-4.6] gcc-4.6: should not be released with stretch 793873 was blocked by: 747990 793873 was not blocking any bugs. Added blocking bug(s) of 793873: 747980 End of message, stopping processing here. Please contact me if you need assistance. -- 793873: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=793873 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
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#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.
Processed: [libtest-perl-critic-perl] lintian FTBFS with new version
Processing control commands: affects -1 lintian Bug #795716 [libtest-perl-critic-perl] [libtest-perl-critic-perl] lintian FTBFS with new version Added indication that 795716 affects lintian -- 795716: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=795716 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
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
Processed: severity of 795410 is normal
Processing commands for cont...@bugs.debian.org: severity 795410 normal Bug #795410 [postgresql-common] postgresql-common: pg_createcluster fails on clean install of postgresql Severity set to 'normal' from 'grave' thanks Stopping processing here. Please contact me if you need assistance. -- 795410: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=795410 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Re: Should xmail be removed?
Processing commands for cont...@bugs.debian.org: reassign 794323 ftp.debian.org Bug #794323 [xmail] Should xmail be removed? Bug reassigned from package 'xmail' to 'ftp.debian.org'. Ignoring request to alter found versions of bug #794323 to the same values previously set Ignoring request to alter fixed versions of bug #794323 to the same values previously set retitle 794323 RM: xmail Bug #794323 [ftp.debian.org] Should xmail be removed? Changed Bug title to 'RM: xmail' from 'Should xmail be removed?' thanks Stopping processing here. Please contact me if you need assistance. -- 794323: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=794323 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
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#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#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#795580: bookkeeper: FTBFS: Missing [..] io.netty:netty:jar:debian
affects 795580 + package zookeeper thanks I've investigated this issue and found the following: 1. Without libnetty-3.9-java installed, I can reproduce the FTBFS. 2. After installing it, bookkeeper builds successfully. It looks to me like the underlying issue is actually in zookeeper. The control file [1] for zookeeper recently [2] switched to build-depend on libnetty-3.9-java. However, the binary package libzookeeper-java still depends on the older libnetty-java. So I believe this issue would sort itself out if the dependency for libzookeeper-java was updated as well. [1] https://tracker.debian.org/media/packages/z/zookeeper/control-3.4.6-7 [2] http://anonscm.debian.org/cgit/pkg-java/zookeeper.git/commit/?id=a9aed1fe80dc24e3ab89e458a89c4ffb3938b041 -- mvh / best regards Hans Joachim Desserud http://desserud.org
Processed: Re: bookkeeper: FTBFS: Missing [..] io.netty:netty:jar:debian
Processing commands for cont...@bugs.debian.org: affects 795580 + package zookeeper Bug #795580 [src:bookkeeper] bookkeeper: FTBFS: Missing [..] io.netty:netty:jar:debian Added indication that 795580 affects package and zookeeper thanks Stopping processing here. Please contact me if you need assistance. -- 795580: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=795580 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
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#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#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.
Bug#795644: git-annex: configure eats all memory
Hi, Am Sonntag, den 16.08.2015, 12:05 +0200 schrieb Joachim Breitner: 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 think I got it: Cabal tries to infer what feature are supported by looking at the dependencies, and their flags, and mumble mumble complex search space. So while it works fine with all dependencies installed, it works less well with some missing (as on my machine, or on mips), and Cabal runs wild in the search space. The solution would be to explicitly tell Cabal what features are supported. So for example on amd64, you want $ ./Setup configure -fcryptonite -fdatabase -fnetwork-uri -f-ekg -f-asciiprogress -f-torrentparser -fdesktopnotify -ftahoe -fquvi -ffeed -ftdfa -ftestsuite -f-androidsplice -f-android -fproduction -fdns -fxmpp -fpairing webapp--fsecure -fwebapp -fassistant -fdbus -finotify -fwebdav -fs3 You can obtain that list from a successful run if you pass -v to configure, and translate this summary into the above format (prefix -f for =True, -f- for =False) Flags chosen: cryptonite=True, database=True, network-uri=True, ekg=False, asciiprogress=False, torrentparser=False, desktopnotify=True, tahoe=True, quvi=True, feed=True, tdfa=True, testsuite=True, androidsplice=False, android=False, production=True, dns=True, xmpp=True, pairing=True, webapp-secure=True, webapp=True, assistant=True, dbus=True, inotify=True, webdav=True, s3=True This means on mips, you (Richard) have to manually set some of them to false. You can probably guess which ones, e.g. webapp. It is all a bit more manual, but also more explicit: You will not accidentally lose a feature because a dependency has the wrong version or is missing, but rather the build will fail. Which is a good thing. And the error message will hopefully point you at which flag assignment is wrong. Potentially, it helps to just set one or two flags on mips, but guessing which ones are enough to avoid the problem is maybe more work than simply setting all of them. Let me know if that solves the problem on mips. 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#793326: marked as done (linux: raid0 data corruption when using trim)
Your message dated Sun, 16 Aug 2015 12:00:26 + with message-id e1zqwby-0002gj...@franck.debian.org and subject line Bug#793326: fixed in linux 4.1.5-1 has caused the Debian Bug report #793326, regarding linux: raid0 data corruption when using trim to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 793326: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=793326 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: linux Version: 4.1.2-1~exp1 The company Algolia discovered a problem when TRIM was enabled on their SSDs and documented things on their blog as they tracked it down https://blog.algolia.com/when-solid-state-drives-are-not-that-solid/ At first it was thought to be a problem with enabling TRIM on the Samsung SSDs, but with the help of Samsung the problem was eventually found to be due to a misunderstanding between raid driver and scsi/ata driver and a patch was posted http://www.spinics.net/lists/raid/msg49440.html to which Martin K. Petersen followed up with a different version http://www.spinics.net/lists/raid/msg49447.html and that patch was tested and submitted http://www.spinics.net/lists/raid/msg49468.html The bug affected raid0 and raid10 (but apparently not raid1) when TRIM was enabled. Apparently it's been around a while, it probably exists older debian releases but I have not checked. Also: as the blog June 16th update states, this bug was NOT related to queued TRIM as they didn't have that enabled, so probably unrelated to #790520. Thanks, -- Matt Taggart tagg...@debian.org ---End Message--- ---BeginMessage--- Source: linux Source-Version: 4.1.5-1 We believe that the bug you reported is fixed in the latest version of linux, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 793...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Ben Hutchings b...@decadent.org.uk (supplier of updated linux package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Sat, 15 Aug 2015 23:37:20 +0200 Source: linux Binary: linux-source-4.1 linux-doc-4.1 linux-manual-4.1 linux-support-4.1.0-2 linux-libc-dev linux-headers-4.1.0-2-all linux-headers-4.1.0-2-all-alpha kernel-image-4.1.0-2-alpha-generic-di nic-modules-4.1.0-2-alpha-generic-di nic-wireless-modules-4.1.0-2-alpha-generic-di nic-shared-modules-4.1.0-2-alpha-generic-di serial-modules-4.1.0-2-alpha-generic-di usb-serial-modules-4.1.0-2-alpha-generic-di ppp-modules-4.1.0-2-alpha-generic-di pata-modules-4.1.0-2-alpha-generic-di cdrom-core-modules-4.1.0-2-alpha-generic-di scsi-core-modules-4.1.0-2-alpha-generic-di scsi-modules-4.1.0-2-alpha-generic-di scsi-common-modules-4.1.0-2-alpha-generic-di scsi-extra-modules-4.1.0-2-alpha-generic-di loop-modules-4.1.0-2-alpha-generic-di btrfs-modules-4.1.0-2-alpha-generic-di ext4-modules-4.1.0-2-alpha-generic-di isofs-modules-4.1.0-2-alpha-generic-di jfs-modules-4.1.0-2-alpha-generic-di xfs-modules-4.1.0-2-alpha-generic-di fat-modules-4.1.0-2-alpha-generic-di md-modules-4.1.0-2-alpha-generic-di multipath-modules-4.1.0-2-alpha-generic-di usb-modules-4.1.0-2-alpha-generic-di usb-storage-modules-4.1.0-2-alpha-generic-di fb-modules-4.1.0-2-alpha-generic-di input-modules-4.1.0-2-alpha-generic-di event-modules-4.1.0-2-alpha-generic-di mouse-modules-4.1.0-2-alpha-generic-di nic-pcmcia-modules-4.1.0-2-alpha-generic-di pcmcia-modules-4.1.0-2-alpha-generic-di nic-usb-modules-4.1.0-2-alpha-generic-di sata-modules-4.1.0-2-alpha-generic-di core-modules-4.1.0-2-alpha-generic-di crc-modules-4.1.0-2-alpha-generic-di crypto-modules-4.1.0-2-alpha-generic-di crypto-dm-modules-4.1.0-2-alpha-generic-di ata-modules-4.1.0-2-alpha-generic-di nbd-modules-4.1.0-2-alpha-generic-di squashfs-modules-4.1.0-2-alpha-generic-di virtio-modules-4.1.0-2-alpha-generic-di zlib-modules-4.1.0-2-alpha-generic-di fuse-modules-4.1.0-2-alpha-generic-di srm-modules-4.1.0-2-alpha-generic-di linux-headers-4.1.0-2-common linux-image-4.1.0-2-alpha-generic linux-headers-4.1.0-2-alpha-generic linux-image-4.1.0-2-alpha-smp linux-headers-4.1.0-2-alpha-smp linux-headers-4.1.0-2-all-amd64
Bug#793931: marked as done (glueviz: /usr/lib/python2.7/dist-packages/glue/__init__.py collides with package glue-sprite)
Your message dated Sun, 16 Aug 2015 12:03:50 + with message-id e1zqwfg-0003wg...@franck.debian.org and subject line Bug#793931: fixed in glueviz 0.5.2+dfsg-1 has caused the Debian Bug report #793931, regarding glueviz: /usr/lib/python2.7/dist-packages/glue/__init__.py collides with package glue-sprite to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 793931: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=793931 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: glueviz Version: 0.4.0-1 Severity: serious User: trei...@debian.org Usertags: edos-file-overwrite Control: affects -1 + glue-sprite Hi, automatic installation tests of packages that share a file and at the same time do not conflict by their package dependency relationships has detected the following problem: Selecting previously unselected package glueviz. Preparing to unpack .../glueviz_0.4.0-1_all.deb ... Unpacking glueviz (0.4.0-1) ... dpkg: error processing archive /var/cache/apt/archives/glueviz_0.4.0-1_all.deb (--unpack): trying to overwrite '/usr/lib/python2.7/dist-packages/glue/__init__.py', which is also in package glue-sprite 0.9.4-1 dpkg-deb: error: subprocess paste was killed by signal (Broken pipe) Processing triggers for systemd (215-17+deb8u1) ... Processing triggers for mime-support (3.58) ... Errors were encountered while processing: /var/cache/apt/archives/glueviz_0.4.0-1_all.deb This is a serious bug as it makes installation fail, and violates sections 7.6.1 and 10.1 of the policy. An optimal solution would consist in only one of the packages installing that file, and renaming or removing the file in the other package. Depending on the circumstances you might also consider Replace relations or file diversions. If the conflicting situation cannot be resolved then, as a last resort, the two packages have to declare a mutual Conflict. Please take into account that Replaces, Conflicts and diversions should only be used when packages provide different implementations for the same functionality. Here is a list of files that are known to be shared by both packages (according to the Contents file for sid/amd64, which may be slightly out of sync): usr/lib/python2.7/dist-packages/glue/__init__.py Cheers, Andreas PS: for more information about the detection of file overwrite errors of this kind see https://qa.debian.org/dose/file-overwrites.html glue-sprite=0.9.4-1_glueviz=0.4.0-1.log.gz Description: application/gzip ---End Message--- ---BeginMessage--- Source: glueviz Source-Version: 0.5.2+dfsg-1 We believe that the bug you reported is fixed in the latest version of glueviz, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 793...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Josue Ortega josueort...@debian.org.gt (supplier of updated glueviz package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Sun, 16 Aug 2015 12:45:50 +0200 Source: glueviz Binary: glueviz Architecture: source all Version: 0.5.2+dfsg-1 Distribution: unstable Urgency: medium Maintainer: Debian Astronomy Maintainers debian-astro-maintain...@lists.alioth.debian.org Changed-By: Josue Ortega josueort...@debian.org.gt Description: glueviz- Linked data visualization Closes: 793931 795335 Changes: glueviz (0.5.2+dfsg-1) unstable; urgency=medium . * New upstream release: - Updated debian/copyright. - Updated debia/pathes/* - dfsg version: Removed binary file doc/tutorial_files/extinction.fits * debian/control: Removed libzmq dependency (Closes: #795335). * debian/control: Added Conflicts section in order to avoid overwrite files from glue-sprite (Closes: #793931). Checksums-Sha1: c6d4939981e5df94726f3b7cd6c89d754f3f69b8 2224 glueviz_0.5.2+dfsg-1.dsc 6fc0539a062b526acf5e423a7341c29403d926d9 10058714 glueviz_0.5.2+dfsg.orig.tar.gz 1e48f63f9cb80c2b0f48586b71b8b114b9611364 5656 glueviz_0.5.2+dfsg-1.debian.tar.xz 7ebd811d83947a6f8c83fb28892d85e81cab536e 561200 glueviz_0.5.2+dfsg-1_all.deb Checksums-Sha256: 6e638fc644dc21f7c0f99cfa20b27d1e3ad8d4786e0dc98e344f6debb9799b20 2224
Bug#795718: Don't include libav in stretch
Source: libav Severity: serious It was decided to switch to ffmpeg for stretch and it's now in testing. Please remove libav from testing (or rather from unstable unless someone wants to continue to maintain it in unstable/experimental only) Cheers, Moritz
Processed: Fails to build on release architectures
Processing control commands: severity 766631 serious Bug #766631 [turnserver] FTBFS ppc64el: Remove deprecated SVID_SOURCE Severity set to 'serious' from 'important' -- 766631: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=766631 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#795729: libpqtypes: FTBFS under some timezones (eg. GMT+12)
Source: libpqtypes
Version: 1.5.1-2
Severity: serious
Justification: fails to build from source
Dear Maintainer,
libpqtypes fails to build from source on unstable/amd64 under
some timezones (eg. TZ=/usr/share/zoneinfo/Etc/GMT+12):
[..]
debian/rules override_dh_auto_test
make[1]: Entering directory '/tmp/buildd/libpqtypes-1.5.1'
/usr/bin/make test LDFLAGS+=-L.libs
make[2]: Entering directory '/tmp/buildd/libpqtypes-1.5.1'
gcc -g -O2 -fstack-protector-strong -Wformat -Werror=format-security
-O3 -Wall -Wpointer-arith -D_GNU_SOURCE -D_REENTRANT -fsigned-char
-std=gnu99 -Wclobbered -Wempty-body -Wignored-qualifiers
-Wmissing-parameter-type -Wold-style-declaration -Woverride-init
-Wsign-compare -Wtype-limits -Wuninitialized -fomit-frame-pointer
-fno-strict-aliasing -funroll-all-loops -funit-at-a-time -Wdate-time
-D_FORTIFY_SOURCE=2 -I/usr/include/postgresql -Isrc -DHAVE_CONFIG_H \
-o test src/regression-test.c -Wl,-z,relro -L.libs -lm -lpq
-lpqtypes
src/regression-test.c: In function 'main':
src/regression-test.c:235:11: warning: variable 'ba' set but not used
[-Wunused-but-set-variable]
PGbytea ba;
^
make[2]: Leaving directory '/tmp/buildd/libpqtypes-1.5.1'
LD_LIBRARY_PATH=:.libs pg_virtualenv ./test
install: cannot change owner and permissions of
'/tmp/pg_virtualenv.2sBpjO/postgresql/9.4': Operation not permitted
Creating new cluster 9.4/regress ...
config /tmp/pg_virtualenv.2sBpjO/postgresql/9.4/regress
data /tmp/pg_virtualenv.2sBpjO/data/9.4/regress
locale C
Warning: The socket directory for owners other than 'postgres'
defaults to /tmp. You might want to change the unix_socket_directories
parameter
in postgresql.conf to a more secure directory.
port 5432
Warning: The parent /var/run/postgresql of the selected
stats_temp_directory is not writable for the cluster owner. Not adding
this
setting in postgresql.conf.
server type lookup failed: could not find 'mytype_t'
%epoch - passed
%epoch - passed
%timestamptz - FAILED
Composites Arrays: (always binary)
Testing empty array handling - passed
composite[] with nested composite and arrays passed
PQputvf
SELECT $1 + ($2 % $3) AS answer
PQputvf - passed
PQspecPrepare
PQspecPrepare - passed
Native C types: (text)
%char - passed
%char - passed
%int2 - passed
%int2 - passed
%int4 - passed
%int4 - passed
%int8 - passed
%int8 - passed
%float4 - passed
%float4 - passed
%float8 - passed
%float8 - passed
%money - passed
%money - passed
%oid - passed
%oid - passed
%bool - passed
%bool - passed
Native C types: (binary)
%char - passed
%char - passed
%int2 - passed
%int2 - passed
%int4 - passed
%int4 - passed
%int8 - passed
%int8 - passed
%float4 - passed
%float4 - passed
%float8 - passed
%float8 - passed
%money - passed
%money - passed
%oid - passed
%oid - passed
%bool - passed
%bool - passed
Variable-length types: (text)
%bpchar - passed
%varchar - passed
%text - passed
%bytea* - passed
%uuid - passed
%numeric - passed
Variable-length types: (binary)
%bpchar - passed
%varchar - passed
%text - passed
%bytea* - passed
%uuid - passed
%numeric - passed
Geometric types: (text)
%point - passed
%lseg - passed
%box - passed
%circle - passed
%path - passed
%polygon - passed
Geometric types: (binary)
%point - passed
%lseg - passed
%box - passed
%circle - passed
%path - passed
%polygon - passed
Network types: (text)
%inet - IPv4 passed
%inet - IPv6 passed
%macaddr - passed
Network types: (binary)
%inet - IPv4 passed
%inet - IPv6 passed
%macaddr - passed
Sub-class: (text)
epoch_put('0')
epoch_put('946702800')
epoch_get(text)
epoch_get(text)
Sub-class: (binary)
epoch_put('0')
epoch_put('946702800')
epoch_get(binary)
epoch_get(binary)
Date Time types: (text 'ISO, MDY')
%date - #1 passed
%date - #2 passed
%date - #3 passed
%time - #1 passed
%time - #2 passed
%time - #3 passed
%timetz - #1 passed
%timetz - #2 passed
%timetz - #3 passed
%timestamp - #1 passed
%timestamp - #2 passed
%timestamp - #3 passed
%interval - passed
%timestamptz - passed
Date Time types: (binary 'ISO, MDY')
%date - #1 passed
%date - #2 passed
%date - #3 passed
%time - #1 passed
%time - #2 passed
%time - #3 passed
%timetz - #1 passed
%timetz - #2 passed
%timetz - #3 passed
%timestamp - #1 passed
%timestamp - #2 passed
%timestamp - #3 passed
%interval - passed
%timestamptz - passed
Date Time types: (text 'Postgres, MDY')
%date - #1 passed
%date - #2 passed
%date - #3 passed
Processed: forcibly merging 785300 795649
Processing commands for cont...@bugs.debian.org:
forcemerge 785300 795649
Bug #785300 {Done: Michael Schutte mi...@debian.org} [xul-ext-pentadactyl]
xul-ext-pentadactyl: pentadactyl not compatible with iceweasel 38.0-1
Bug #795649 [xul-ext-pentadactyl] xul-ext-pentadactyl: Pentadactyl is
incompatible with Iceweasel 38.2.0
Severity set to 'serious' from 'important'
Marked Bug as done
Marked as fixed in versions dactyl/1.2~hg7166-1.
Added tag(s) confirmed.
Merged 785300 795649
thanks
Stopping processing here.
Please contact me if you need assistance.
--
785300: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=785300
795649: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=795649
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#795691: freezegun: FTBFS under some timezones (eg. GMT-14)
Source: freezegun Version: 0.3.4-1 Severity: serious Justification: fails to build from source Dear Maintainer, freezegun fails to build from source on unstable/amd64 under some timezones (eg. TZ=/usr/share/zoneinfo/Etc/GMT-14): [..] pyversions: missing debian/pyversions file, fall back to supported versions py3versions: no X-Python3-Version in control file, using supported versions for python in python2.7; do \ $python /usr/bin/nosetests tests; \ done ...F.S == FAIL: tests.test_class_import.test_import_localtime -- Traceback (most recent call last): File /usr/lib/python2.7/dist-packages/nose/case.py, line 197, in runTest self.test(*self.arg) File /tmp/buildd/freezegun-0.3.4/freezegun/api.py, line 348, in wrapper result = func(*args, **kwargs) File /tmp/buildd/freezegun-0.3.4/tests/test_class_import.py, line 76, in test_import_localtime assert struct.tm_mday == 14 AssertionError: time.struct_time(tm_year=2012, tm_mon=1, tm_mday=15, tm_hour=2, tm_min=0, tm_sec=0, tm_wday=6, tm_yday=15, tm_isdst=-1) = fake_localtime_function() assert time.struct_time(tm_year=2012, tm_mon=1, tm_mday=15, tm_hour=2, tm_min=0, tm_sec=0, tm_wday=6, tm_yday=15, tm_isdst=-1).tm_year == 2012 assert time.struct_time(tm_year=2012, tm_mon=1, tm_mday=15, tm_hour=2, tm_min=0, tm_sec=0, tm_wday=6, tm_yday=15, tm_isdst=-1).tm_mon == 1 assert time.struct_time(tm_year=2012, tm_mon=1, tm_mday=15, tm_hour=2, tm_min=0, tm_sec=0, tm_wday=6, tm_yday=15, tm_isdst=-1).tm_mday == 14 NameStmts Miss Cover Missing - freezegun 8 0 100% freezegun.api 256 1395% 19-20, 44, 56, 286, 296-298, 318-320, 363-364, 379-381 - TOTAL 264 1395% -- Ran 62 tests in 3.362s FAILED (SKIP=1, failures=1) debian/rules:16: recipe for target 'override_dh_auto_test' failed make[1]: *** [override_dh_auto_test] Error 1 make[1]: Leaving directory '/tmp/buildd/freezegun-0.3.4' debian/rules:12: recipe for target 'build' failed make: *** [build] Error 2 dpkg-buildpackage: error: debian/rules build gave error exit status 2 [..] The full build log is attached or can be viewed here: https://reproducible.debian.net/logs/unstable/amd64/freezegun_0.3.4-1.build2.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: samedi 25 juillet 2015, 10:45:28 (UTC+1400) I: pbuilder-time-stamp: 1437770728 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 I: user script /var/cache/pbuilder/build//58774/tmp/hooks/D01_modify_environment starting I: Changing hostname to test build reproducibility I: user script /var/cache/pbuilder/build//58774/tmp/hooks/D01_modify_environment finished - 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 (= 9~), dh-python, python-all (= 2.6.6-3~), python-coverage, python-dateutil, python-nose, python-setuptools, python-sure, python3-all, python3-coverage, python3-dateutil, python3-nose, python3-setuptools, python3-sure 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 dh-python; however: Package dh-python is not installed. pbuilder-satisfydepends-dummy depends on python-all (= 2.6.6-3~);
Bug#781103: marked as done (libwacom2: Needs update for 3.17 and above)
Your message dated Sun, 16 Aug 2015 10:00:21 + with message-id e1zqujl-o5...@franck.debian.org and subject line Bug#781103: fixed in libwacom 0.15-1 has caused the Debian Bug report #781103, regarding libwacom2: Needs update for 3.17 and above to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 781103: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=781103 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: libwacom2 Version: 0.8-1 Severity: normal Hi, For Linux kernel 3.17 and above libwacom needs an update. With 0.8 and 3.17+ I can use the tablet as a mouse, but applications does not read any pressure sensitivity. -- System Information: Debian Release: 8.0 APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: i386 (i686) Kernel: Linux 3.19.0-trunk-686-pae (SMP w/2 CPU cores) Locale: LANG=en_GB.utf8, LC_CTYPE=en_GB.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages libwacom2 depends on: ii libc6 2.19-17 ii libglib2.0-0 2.42.1-1 ii libgudev-1.0-0 215-12 ii libwacom-common0.8-1 ii multiarch-support 2.19-17 libwacom2 recommends no packages. libwacom2 suggests no packages. -- no debconf information ---End Message--- ---BeginMessage--- Source: libwacom Source-Version: 0.15-1 We believe that the bug you reported is fixed in the latest version of libwacom, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 781...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Timo Aaltonen tjaal...@debian.org (supplier of updated libwacom package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Sun, 16 Aug 2015 00:59:05 +0300 Source: libwacom Binary: libwacom2 libwacom-bin libwacom-common libwacom-dev libwacom2-dbg Architecture: source amd64 all Version: 0.15-1 Distribution: unstable Urgency: medium Maintainer: Timo Aaltonen tjaal...@debian.org Changed-By: Timo Aaltonen tjaal...@debian.org Description: libwacom-bin - Wacom model feature query library -- binaries libwacom-common - Wacom model feature query library (common files) libwacom-dev - Wacom model feature query library (development files) libwacom2 - Wacom model feature query library libwacom2-dbg - Wacom model feature query library (debug files) Closes: 781103 Changes: libwacom (0.15-1) unstable; urgency=medium . * New upstream release. (Closes: #781103) * control: - update my email - bump policy to 3.9.6, no changes - update vcs urls - add libwacom-bin and it's build-deps * symbols: Add a new symbol. * rules: - use --fail-missing - install to debian/tmp * gbp.conf: Added. * copyright: Exclude doc/html from the tarball. * symbols: Updated. Checksums-Sha1: 025cb091628e066c75c4ec6ee55cd5009e15b6ee 2100 libwacom_0.15-1.dsc f13d71700cfac1fe4e26a0802d8285b0ceb3259f 334743 libwacom_0.15.orig.tar.bz2 39b7cf9196d43e5065ca790dbe38e1436b8c07ed 3648 libwacom_0.15-1.debian.tar.xz bdccce39cea1ae216885f1986ceb6bdc5afbe340 5532 libwacom-bin_0.15-1_amd64.deb d4c1426f501976131ae4f6d3b229fe367ee5712e 23090 libwacom-common_0.15-1_all.deb 7c948559475f400bd9e9241fca8090c7617efb4f 50884 libwacom-dev_0.15-1_amd64.deb 548f7012259c67841d3222853e74ab2209921525 36400 libwacom2-dbg_0.15-1_amd64.deb 0ee5ddd983bf462fb9ee3dee1fdeeb0a57551da2 17102 libwacom2_0.15-1_amd64.deb Checksums-Sha256: ae6089c1934c3554517a9b0167f0c8288ba45262f9519eaf7361dab625f039f3 2100 libwacom_0.15-1.dsc fd6d4e672038e4ba653bd09d170028da24d426861c7010ae667c486eb8e693b6 334743 libwacom_0.15.orig.tar.bz2 97bedfd45e2d3311945826e9bdda4f13d90fa31c93cd01b602de63fbf672ccee 3648 libwacom_0.15-1.debian.tar.xz 1f8134804aa6f88a7c38c99cc284b3ce0c6f91c2990f9e8faba0faa7092a4e5e 5532 libwacom-bin_0.15-1_amd64.deb 63c1648e2ed2b2eda59acabe0449210abfed14e6c50609c97726edc4a512e642 23090 libwacom-common_0.15-1_all.deb dc03bbe870dea5e4f2fea3be6655e889d205c902181405b526b3a0abbb308479 50884 libwacom-dev_0.15-1_amd64.deb 355d1bb98e4fdd2cefed2808c1d28e4ac605ac4de16caf0ded284107a0d91137 36400 libwacom2-dbg_0.15-1_amd64.deb
Bug#795681: python-oslo.i18n: FTBFS under some locales (eg. fr_CH.UTF-8)
Source: python-oslo.i18n Version: 1.5.0-2 Severity: serious Justification: fails to build from source Dear Maintainer, python-oslo.i18n fails to build from source on unstable/amd64 under some locales (eg. LANG=fr_CH.UTF-8): [..] == FAIL: oslo_i18n.tests.test_fixture.PrefixLazyTranslationTest.test_default oslo_i18n.tests.test_fixture.PrefixLazyTranslationTest.test_default -- _StringException: Traceback (most recent call last): File oslo_i18n/tests/test_fixture.py, line 103, in test_default self.assertEqual(expected_msg, _translate.translate(msg1)) File /usr/lib/python2.7/dist-packages/testtools/testcase.py, line 338, in assertEqual self.assertThat(observed, matcher, message) File /usr/lib/python2.7/dist-packages/testtools/testcase.py, line 423, in assertThat raise mismatch_error MismatchError: 'oslo.i18n/en_US: fake msg1' != u'oslo.i18n/fr_CH: fake msg1' Traceback (most recent call last): _StringException: Empty attachments: stderr stdout Traceback (most recent call last): File oslo_i18n/tests/test_fixture.py, line 103, in test_default self.assertEqual(expected_msg, _translate.translate(msg1)) File /usr/lib/python2.7/dist-packages/testtools/testcase.py, line 338, in assertEqual self.assertThat(observed, matcher, message) File /usr/lib/python2.7/dist-packages/testtools/testcase.py, line 423, in assertThat raise mismatch_error MismatchError: 'oslo.i18n/en_US: fake msg1' != u'oslo.i18n/fr_CH: fake msg1' Traceback (most recent call last): _StringException: Empty attachments: stderr stdout Traceback (most recent call last): File oslo_i18n/tests/test_fixture.py, line 103, in test_default self.assertEqual(expected_msg, _translate.translate(msg1)) File /usr/lib/python2.7/dist-packages/testtools/testcase.py, line 338, in assertEqual self.assertThat(observed, matcher, message) File /usr/lib/python2.7/dist-packages/testtools/testcase.py, line 423, in assertThat raise mismatch_error MismatchError: 'oslo.i18n/en_US: fake msg1' != u'oslo.i18n/fr_CH: fake msg1' == FAIL: oslo_i18n.tests.test_fixture.PrefixLazyTranslationTest.test_extra_lang oslo_i18n.tests.test_fixture.PrefixLazyTranslationTest.test_extra_lang -- _StringException: Traceback (most recent call last): File oslo_i18n/tests/test_fixture.py, line 121, in test_extra_lang self.assertEqual(expected_msg_en_US, _translate.translate(msg1)) File /usr/lib/python2.7/dist-packages/testtools/testcase.py, line 338, in assertEqual self.assertThat(observed, matcher, message) File /usr/lib/python2.7/dist-packages/testtools/testcase.py, line 423, in assertThat raise mismatch_error MismatchError: 'oslo.i18n/en_US: fake msg1' != u'oslo.i18n/fr_CH: fake msg1' Traceback (most recent call last): _StringException: Empty attachments: stderr stdout Traceback (most recent call last): File oslo_i18n/tests/test_fixture.py, line 121, in test_extra_lang self.assertEqual(expected_msg_en_US, _translate.translate(msg1)) File /usr/lib/python2.7/dist-packages/testtools/testcase.py, line 338, in assertEqual self.assertThat(observed, matcher, message) File /usr/lib/python2.7/dist-packages/testtools/testcase.py, line 423, in assertThat raise mismatch_error MismatchError: 'oslo.i18n/en_US: fake msg1' != u'oslo.i18n/fr_CH: fake msg1' Traceback (most recent call last): _StringException: Empty attachments: stderr stdout Traceback (most recent call last): File oslo_i18n/tests/test_fixture.py, line 121, in test_extra_lang self.assertEqual(expected_msg_en_US, _translate.translate(msg1)) File /usr/lib/python2.7/dist-packages/testtools/testcase.py, line 338, in assertEqual self.assertThat(observed, matcher, message) File /usr/lib/python2.7/dist-packages/testtools/testcase.py, line 423, in assertThat raise mismatch_error MismatchError: 'oslo.i18n/en_US: fake msg1' != u'oslo.i18n/fr_CH: fake msg1' == FAIL: process-returncode process-returncode -- _StringException: returncode 1 -- Ran 70 tests in 1.701s FAILED (failures=3) debian/rules:26: recipe for target 'override_dh_auto_test' failed make[1]: *** [override_dh_auto_test] Error 1 make[1]: Leaving directory '/tmp/buildd/python-oslo.i18n-1.5.0' debian/rules:12: recipe for target 'build' failed
Bug#791250: Do you need any help for pugixml
Quoting Andreas Tille (2015-08-16 14:46:04) 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. Yes it does (after the part about you not needing to care about CDBS). (If not I'll leave the package as is for its real Maintainer who probably knows.) Thanks for your help so far. This discussion is less helpful, so we take it from here. - Jonas -- * Jonas Smedegaard - idealist Internet-arkitekt * Tlf.: +45 40843136 Website: http://dr.jones.dk/ [x] quote me freely [ ] ask before reusing [ ] keep private
Bug#777930: ksh: ftbfs with GCC-5
Oliver Kiddle writes: I queried the ast-users mailing iist and both Arch and opensuse apparently have patches for the issue. See here http://lists.research.att.com/pipermail/ast-users/2015q3/004773.html Ok, the fix for Arch-linux is usage of different version of ast-library. Source code for that is behind registration-wall of att research so I couldn't check it out. ..in practice Arch is distributing only the binary, using pkgbuild of Arch for ksh package requires registration first. So, in order to get rid of this gcc5-related bug it is possible either to patch this existing version or obtain the other (more recent?) upstream version, any opinions Oliver? -- Antti
Bug#794277: marked as done (htseq: FTBFS with Sphinx 1.3: unsupported theme option 'sidebarlinkcolor' given)
Your message dated Sun, 16 Aug 2015 10:20:08 +
with message-id e1zqv2u-0007ao...@franck.debian.org
and subject line Bug#794277: fixed in htseq 0.6.1p1-1
has caused the Debian Bug report #794277,
regarding htseq: FTBFS with Sphinx 1.3: unsupported theme option
'sidebarlinkcolor' given
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
794277: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=794277
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
---BeginMessage---
Source: htseq
Version: 0.5.4p3-2
User: python-modules-t...@lists.alioth.debian.org
Usertags: sphinx1.3
htseq FTBFS with Sphinx 1.3 (which is available in experimental):
preparing documents... Traceback (most recent call last):
[...]
File /usr/lib/python2.7/dist-packages/sphinx/builders/__init__.py, line
343, in write
self.prepare_writing(docnames)
File /usr/lib/python2.7/dist-packages/sphinx/builders/html.py, line 357,
in prepare_writing
iteritems(self.theme.get_options(self.theme_options)))
File /usr/lib/python2.7/dist-packages/sphinx/theming.py, line 176, in
get_options
raise ThemeError('unsupported theme option %r given' % option)
sphinx.errors.ThemeError: unsupported theme option 'sidebarlinkcolor' given
There is a new default theme (alabaster) in Sphinx 1.3 [1], which
has a different set of options [2].
You can use the old default by explicitly specifying
“html_theme = 'default'” in docs/conf.py.
[1]: http://sphinx-doc.org/theming.html#builtin-themes
[2]: https://pypi.python.org/pypi/alabaster#theme-options
--
Dmitry Shachnev
signature.asc
Description: OpenPGP digital signature
---End Message---
---BeginMessage---
Source: htseq
Source-Version: 0.6.1p1-1
We believe that the bug you reported is fixed in the latest version of
htseq, which is due to be installed in the Debian FTP archive.
A summary of the changes between this version and the previous one is
attached.
Thank you for reporting the bug, which will now be closed. If you
have further comments please address them to 794...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Andreas Tille ti...@debian.org (supplier of updated htseq package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Format: 1.8
Date: Sun, 16 Aug 2015 12:01:07 +0200
Source: htseq
Binary: python-htseq python-htseq-doc
Architecture: source all amd64
Version: 0.6.1p1-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Med Packaging Team
debian-med-packag...@lists.alioth.debian.org
Changed-By: Andreas Tille ti...@debian.org
Description:
python-htseq - high-throughput genome sequencing read analysis utilities
python-htseq-doc - documetation for HTSeq (high-throughput genome sequencing)
Closes: 742921 794277
Changes:
htseq (0.6.1p1-1) unstable; urgency=medium
.
[ Diane Trout ]
* Add get-orig-source to download from upstream svn.
(upstream's release process deletes source files)
* Add build-dependency on python-debian for get-orig-source
* New upstream release.
* Use upstream scripts to build and clean.
* Try to delete generated test data and setup generated files.
* Use dh_numpy to detect numpy abi version. (Closes: #742921)
* add set-matplotlib-backend.patch to avoid a missing _TkAgg matplotlib
backend.
* Add build dependency on python-matplotlib and python-pysam (for testing)
* Run upstream tests.
.
[ Andreas Tille ]
* At package build time some differences to the expected values are
occuring. Skip these tests for the moment.
* cme fix dpkg-control
* Fix watch file
* DEP5 fixes
* Fix sphinx 1.3 build issue
Closes: #794277
Checksums-Sha1:
c94e3ded77fc05b75d1a74a5fd1ee07a2025fa95 2168 htseq_0.6.1p1-1.dsc
73b817c9678bd60cf47fe8769f3cfe43aa79e955 28788264 htseq_0.6.1p1.orig.tar.xz
e7ee9a35b5ddb0cd72ba064e524f16e71f7717f5 6124 htseq_0.6.1p1-1.debian.tar.xz
db2583a091b28060675a001bc98e90d8e3b21d0c 349906
python-htseq-doc_0.6.1p1-1_all.deb
108a9ce40ad5859c8f8505a5c9a70bb0ab11f844 186968
python-htseq_0.6.1p1-1_amd64.deb
Checksums-Sha256:
05f03bfb4beb653a98ca231ec0dafc6700ce934b5a73dc970c115c0e8b5a9e5a 2168
htseq_0.6.1p1-1.dsc
0e6955f9abb8d6c3e07e0140fccf67dd25454582469bc5195a169db025945ae7 28788264
htseq_0.6.1p1.orig.tar.xz
8d11a319c9e542b2246983c1beec43838ccf76b5ed5f0d61b84cf8ef47404a8f 6124
Bug#795199: marked as done ([linux-source-4.1] linux-source-4.1.tar.xz it's a tar uncompressed archive)
Your message dated Sun, 16 Aug 2015 12:00:26 + with message-id e1zqwby-0002gp...@franck.debian.org and subject line Bug#795199: fixed in linux 4.1.5-1 has caused the Debian Bug report #795199, regarding [linux-source-4.1] linux-source-4.1.tar.xz it's a tar uncompressed archive to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 795199: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=795199 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: linux-source-4.1 Version: 4.1.3-1 Severity: normal the archive linux-source-4.1.tar.xz shipped with this package it's a tar uncompressed archive --- System information. --- Architecture: i386 Kernel: Linux 4.0.8 Debian Release: stretch/sid 500 testing http.debian.net --- Package information. --- Package's Depends field is empty. Package's Recommends field is empty. Package's Suggests field is empty. ---End Message--- ---BeginMessage--- Source: linux Source-Version: 4.1.5-1 We believe that the bug you reported is fixed in the latest version of linux, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 795...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Ben Hutchings b...@decadent.org.uk (supplier of updated linux package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Sat, 15 Aug 2015 23:37:20 +0200 Source: linux Binary: linux-source-4.1 linux-doc-4.1 linux-manual-4.1 linux-support-4.1.0-2 linux-libc-dev linux-headers-4.1.0-2-all linux-headers-4.1.0-2-all-alpha kernel-image-4.1.0-2-alpha-generic-di nic-modules-4.1.0-2-alpha-generic-di nic-wireless-modules-4.1.0-2-alpha-generic-di nic-shared-modules-4.1.0-2-alpha-generic-di serial-modules-4.1.0-2-alpha-generic-di usb-serial-modules-4.1.0-2-alpha-generic-di ppp-modules-4.1.0-2-alpha-generic-di pata-modules-4.1.0-2-alpha-generic-di cdrom-core-modules-4.1.0-2-alpha-generic-di scsi-core-modules-4.1.0-2-alpha-generic-di scsi-modules-4.1.0-2-alpha-generic-di scsi-common-modules-4.1.0-2-alpha-generic-di scsi-extra-modules-4.1.0-2-alpha-generic-di loop-modules-4.1.0-2-alpha-generic-di btrfs-modules-4.1.0-2-alpha-generic-di ext4-modules-4.1.0-2-alpha-generic-di isofs-modules-4.1.0-2-alpha-generic-di jfs-modules-4.1.0-2-alpha-generic-di xfs-modules-4.1.0-2-alpha-generic-di fat-modules-4.1.0-2-alpha-generic-di md-modules-4.1.0-2-alpha-generic-di multipath-modules-4.1.0-2-alpha-generic-di usb-modules-4.1.0-2-alpha-generic-di usb-storage-modules-4.1.0-2-alpha-generic-di fb-modules-4.1.0-2-alpha-generic-di input-modules-4.1.0-2-alpha-generic-di event-modules-4.1.0-2-alpha-generic-di mouse-modules-4.1.0-2-alpha-generic-di nic-pcmcia-modules-4.1.0-2-alpha-generic-di pcmcia-modules-4.1.0-2-alpha-generic-di nic-usb-modules-4.1.0-2-alpha-generic-di sata-modules-4.1.0-2-alpha-generic-di core-modules-4.1.0-2-alpha-generic-di crc-modules-4.1.0-2-alpha-generic-di crypto-modules-4.1.0-2-alpha-generic-di crypto-dm-modules-4.1.0-2-alpha-generic-di ata-modules-4.1.0-2-alpha-generic-di nbd-modules-4.1.0-2-alpha-generic-di squashfs-modules-4.1.0-2-alpha-generic-di virtio-modules-4.1.0-2-alpha-generic-di zlib-modules-4.1.0-2-alpha-generic-di fuse-modules-4.1.0-2-alpha-generic-di srm-modules-4.1.0-2-alpha-generic-di linux-headers-4.1.0-2-common linux-image-4.1.0-2-alpha-generic linux-headers-4.1.0-2-alpha-generic linux-image-4.1.0-2-alpha-smp linux-headers-4.1.0-2-alpha-smp linux-headers-4.1.0-2-all-amd64 kernel-image-4.1.0-2-amd64-di nic-modules-4.1.0-2-amd64-di nic-wireless-modules-4.1.0-2-amd64-di nic-shared-modules-4.1.0-2-amd64-di serial-modules-4.1.0-2-amd64-di usb-serial-modules-4.1.0-2-amd64-di ppp-modules-4.1.0-2-amd64-di pata-modules-4.1.0-2-amd64-di cdrom-core-modules-4.1.0-2-amd64-di firewire-core-modules-4.1.0-2-amd64-di scsi-core-modules-4.1.0-2-amd64-di scsi-modules-4.1.0-2-amd64-di scsi-common-modules-4.1.0-2-amd64-di scsi-extra-modules-4.1.0-2-amd64-di loop-modules-4.1.0-2-amd64-di btrfs-modules-4.1.0-2-amd64-di ext4-modules-4.1.0-2-amd64-di isofs-modules-4.1.0-2-amd64-di jfs-modules-4.1.0-2-amd64-di ntfs-modules-4.1.0-2-amd64-di xfs-modules-4.1.0-2-amd64-di
Bug#795726: ruby-omniauth-openid: FTBFS: formatters.rb:172:in `find_formatter': Formatter 'nested' unknown
Source: ruby-omniauth-openid Version: 1.0.1-2 Severity: serious Justification: fails to build from source Dear Maintainer, ruby-omniauth-openid fails to build from source on unstable/amd64: [..] generating gemspec at /tmp/buildd/ruby-omniauth-openid-1.0.1/debian/ruby-omniauth-openid/usr/share/rubygems-integration/all/specifications/omniauth-openid-1.0.1.gemspec /usr/bin/ruby2.1 /usr/bin/gem2deb-test-runner Running tests for ruby2.1 using debian/ruby-tests.rake ... RUBYLIB=/tmp/buildd/ruby-omniauth-openid-1.0.1/debian/ruby-omniauth-openid/usr/lib/ruby/vendor_ruby:. ruby2.1 -rrake -e ARGV.unshift\(\-f\,\ \debian/ruby-tests.rake\\)\;\ Rake.application.run /usr/bin/ruby2.1 /usr/bin/rspec --pattern ./spec/\*\*/\*_spec.rb /usr/lib/ruby/vendor_ruby/rspec/core/formatters.rb:172:in `find_formatter': Formatter 'nested' unknown - maybe you meant 'documentation' or 'progress'?. (ArgumentError) from /usr/lib/ruby/vendor_ruby/rspec/core/formatters.rb:140:in `add' from /usr/lib/ruby/vendor_ruby/rspec/core/configuration.rb:752:in `add_formatter' from /usr/lib/ruby/vendor_ruby/rspec/core/configuration_options.rb:114:in `block in load_formatters_into' from /usr/lib/ruby/vendor_ruby/rspec/core/configuration_options.rb:114:in `each' from /usr/lib/ruby/vendor_ruby/rspec/core/configuration_options.rb:114:in `load_formatters_into' from /usr/lib/ruby/vendor_ruby/rspec/core/configuration_options.rb:23: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-omniauth-openid-1.0.1/debian/ruby-omniauth-openid 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-omniauth-openid_1.0.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: Tue Jul 21 00:11:06 GMT+12 2015 I: pbuilder-time-stamp: 1437480666 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-rspec, ruby-rack-openid, ruby-omniauth, ruby-rack-test, ruby-webmock, ruby-safe-yaml dpkg-deb: building package 'pbuilder-satisfydepends-dummy' in '/tmp/satisfydepends-aptitude/pbuilder-satisfydepends-dummy.deb'. Selecting previously unselected package pbuilder-satisfydepends-dummy. (Reading database ... 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.7.5~); 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-rack-openid; however: Package ruby-rack-openid is not installed. pbuilder-satisfydepends-dummy depends on ruby-omniauth; however: Package ruby-omniauth is not installed. pbuilder-satisfydepends-dummy depends on ruby-rack-test; however: Package ruby-rack-test is not installed. pbuilder-satisfydepends-dummy depends on ruby-webmock; however: Package ruby-webmock is not installed. pbuilder-satisfydepends-dummy depends on ruby-safe-yaml; however: Package ruby-safe-yaml is not
Bug#795453: marked as done (glance: CVE-2015-5163: Glance v2 API host file disclosure through qcow2 backing file)
Your message dated Sun, 16 Aug 2015 13:04:10 +0200 with message-id 20150816110410.GA18365@eldamar.local and subject line Re: Bug#795453: glance: CVE-2015-5163: Glance v2 API host file disclosure through qcow2 backing file has caused the Debian Bug report #795453, regarding glance: CVE-2015-5163: Glance v2 API host file disclosure through qcow2 backing file to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 795453: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=795453 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Source: glance Version: 2015.1.0-3 Severity: grave Tags: security upstream patch fixed-upstream Hi, the following vulnerability was published for glance. CVE-2015-5163[0]: Glance v2 API host file disclosure through qcow2 backing file 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-5163 [1] http://www.openwall.com/lists/oss-security/2015/08/13/10 Regards, Salvatore ---End Message--- ---BeginMessage--- Source: glance Source-Version: 2015.1.0-4 Closing this bug, since the patch was included in the 2015.1.0-4 upload---End Message---
Bug#794132: marked as done (FTBFS: Hiera::Util Hiera::Util.microsoft_windows? should return false on posix systems)
Your message dated Sun, 16 Aug 2015 13:47:54 +0200 with message-id 20150816134754.368cb...@tanja.brachium-system.net and subject line Re: FTBFS: Hiera::Util Hiera::Util.microsoft_windows? should return false on posix systems has caused the Debian Bug report #794132, regarding FTBFS: Hiera::Util Hiera::Util.microsoft_windows? should return false on posix systems to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 794132: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=794132 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Source: hiera Version: 2.0.0-1 Severity: serious Tags: sid stretch Justification: fails to build from source User: reproducible-bui...@lists.alioth.debian.org Usertags: ftbfs Dear Maintainer, The package fails some tests: Failed examples: rspec ./spec/unit/util_spec.rb:5 # Hiera::Util Hiera::Util.posix? should return true on posix systems rspec ./spec/unit/util_spec.rb:10 # Hiera::Util Hiera::Util.posix? should return false on non posix systems rspec ./spec/unit/util_spec.rb:17 # Hiera::Util Hiera::Util.microsoft_windows? should return false on posix systems It's checking whether File::ALT_SEPARATOR is set, and, if so, it decides that we're on Windows; guessing this has changed in newer Ruby versions. Full build log: https://reproducible.debian.net/rb-pkg/unstable/amd64/hiera.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_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) ---End Message--- ---BeginMessage--- Hello, closing the bug. Had a look and it does not fail anymore. Greets, Jonas---End Message---
Bug#795625: marked as done (oldsys-preseed: FTBFS under some locales (eg. )
Your message dated Sun, 16 Aug 2015 12:21:51 +
with message-id e1zqwwh-0002c9...@franck.debian.org
and subject line Bug#795625: fixed in oldsys-preseed 3.19
has caused the Debian Bug report #795625,
regarding oldsys-preseed: FTBFS under some locales (eg.
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
795625: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=795625
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
---BeginMessage---
Source: oldsys-preseed
Version: 3.18
Severity: serious
Tags: patch
Justification: fails to build from source
Dear Maintainer,
oldsys-preseed fails to build from source on unstable/amd64 under some
locales (eg. LANG=fr_CH.UTF-8):
[..]
Running test arm/nslu2_invalid_hostname... ok
Running test arm/nslu2_static_no_dns... ---
arm/nslu2_static_no_dns.preseed 2011-05-05 10:29:52.0
+1400
+++ /tmp/fileSlf9om 2015-07-24 04:40:44.883126572 +1400
@@ -3,7 +3,7 @@
d-i netcfg/get_ipaddress string 192.168.1.77
d-i netcfg/get_netmask string 255.255.255.0
d-i netcfg/get_gateway string 192.168.1.1
-d-i netcfg/get_nameservers string 192.168.1.1
+d-i netcfg/get_nameservers string Binary file (standard input)
matches Binary file (standard input) matches Binary file (standard
input) matches
d-i netcfg/choose_interface select eth0
d-i netcfg/use_dhcp boolean true
-d-i netcfg/get_hostname string foobar
+d-i netcfg/get_domain string Binary file (standard input) matches
not ok
Running test arm/nslu2_static_no_gw... ok
Running test arm/nslu2_static_no_ip... ---
arm/nslu2_static_no_ip.preseed 2011-05-05 10:29:52.0
+1400
+++ /tmp/fileAZzknD 2015-07-24 04:40:45.407118543 +1400
@@ -3,7 +3,7 @@
d-i netcfg/get_ipaddress string 192.168.1.77
d-i netcfg/get_netmask string 255.255.255.0
d-i netcfg/get_gateway string 192.168.1.1
-d-i netcfg/get_nameservers string 213.33.99.70
+d-i netcfg/get_nameservers string Binary file (standard input)
matches Binary file (standard input) matches Binary file (standard
input) matches
d-i netcfg/choose_interface select eth0
d-i netcfg/use_dhcp boolean true
-d-i netcfg/get_hostname string foobar
+d-i netcfg/get_domain string Binary file (standard input) matches
not ok
Running test arm/nslu2_static... ok
[..]
debian/rules:11: recipe for target 'override_dh_auto_test' failed
make[1]: *** [override_dh_auto_test] Error 1
make[1]: Leaving directory '/tmp/buildd/oldsys-preseed-3.18'
debian/rules:3: recipe for target 'build' failed
make: *** [build] Error 2
dpkg-buildpackage: error: debian/rules build gave error exit status 2
[..]
The full build log is attached or can be viewed here:
https://reproducible.debian.net/logs/unstable/amd64/oldsys-preseed_3.18.build2.log.gz
This is because of grep's automagic locale detection. Patch attached.
Regards,
--
,''`.
: :' : Chris Lamb
`. `'` la...@debian.org / chris-lamb.co.uk
`-
diff --git a/functions b/functions
index a3a7d90..f770ab1 100644
--- a/functions
+++ b/functions
@@ -103,7 +103,7 @@ parse_ifconfig() {
# $1 = string
# $2 = var
get_var() {
- echo $1 | grep ^$2= | sed s/^$2=//
+ echo $1 | grep -a ^$2= | sed s/^$2=//
}
# Get the value from a string in the form of var = value from a file.
I: using fakeroot in build.
I: pbuilder: network access will be disabled during build
I: Current time: vendredi 24 juillet 2015, 04:40:15 (UTC+1400)
I: pbuilder-time-stamp: 1437662415
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
I: user script
/var/cache/pbuilder/build//33982/tmp/hooks/D01_modify_environment starting
I: Changing hostname to test build reproducibility
I: user script
/var/cache/pbuilder/build//33982/tmp/hooks/D01_modify_environment finished
- 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 (= 9), devio
Bug#795579: marked as done (python-nmap: FTBFS: ImportError: No module named nose.tools)
Your message dated Sun, 16 Aug 2015 12:22:00 +
with message-id e1zqwwq-0002hu...@franck.debian.org
and subject line Bug#795579: fixed in python-nmap 0.4.0-2
has caused the Debian Bug report #795579,
regarding python-nmap: FTBFS: ImportError: No module named nose.tools
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
795579: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=795579
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
---BeginMessage---
Source: python-nmap
Version: 0.4.0-1
Severity: serious
Justification: fails to build from source
Dear Maintainer,
python-nmap fails to build from source on unstable/amd64:
[..]
pybuild --test -i python{version} -p 2.7 --dir .
I: pybuild base:170: cd
/tmp/buildd/python-nmap-0.4.0/.pybuild/pythonX.Y_2.7/build; python2.7
-m unittest discover -v
nmap.test_nmap (unittest.loader.ModuleImportFailure) ... ERROR
==
ERROR: nmap.test_nmap (unittest.loader.ModuleImportFailure)
--
ImportError: Failed to import test module: nmap.test_nmap
Traceback (most recent call last):
File /usr/lib/python2.7/unittest/loader.py, line 254, in
_find_tests
module = self._get_module_from_name(name)
File /usr/lib/python2.7/unittest/loader.py, line 232, in
_get_module_from_name
__import__(name)
File nmap/test_nmap.py, line 8, in module
from nose.tools import assert_equals
ImportError: No module named nose.tools
--
Ran 1 test in 0.000s
FAILED (errors=1)
E: pybuild pybuild:262: test: plugin distutils failed with: exit
code=1: cd /tmp/buildd/python-nmap-0.4.0/.pybuild/pythonX.Y_2.7/build;
python2.7 -m unittest discover -v
dh_auto_test: pybuild --test -i python{version} -p 2.7 --dir .
returned exit code 13
debian/rules:6: recipe for target 'build' failed
make: *** [build] Error 25
dpkg-buildpackage: error: debian/rules build gave error exit status 2
The full build log is attached or can be viewed here:
https://reproducible.debian.net/rbuild/unstable/amd64/python-nmap_0.4.0-1.rbuild.log.gz
Regards,
--
,''`.
: :' : Chris Lamb
`. `'` la...@debian.org / chris-lamb.co.uk
`-
Starting to build python-nmap/unstable on 2015-08-15 01:31
The jenkins build log is/was available at
https://jenkins.debian.net/job/reproducible_builder_eta/24753/console
Reading package lists...
Building dependency tree...
Reading state information...
NOTICE: 'python-nmap' packaging is maintained in the 'Git' version control
system at:
git://anonscm.debian.org/collab-maint/python-nmap.git
Need to get 50.1 kB of source archives.
Get:1 http://ftp.de.debian.org/debian/ unstable/main python-nmap 0.4.0-1 (dsc)
[2049 B]
Get:2 http://ftp.de.debian.org/debian/ unstable/main python-nmap 0.4.0-1 (tar)
[45.9 kB]
Get:3 http://ftp.de.debian.org/debian/ unstable/main python-nmap 0.4.0-1 (diff)
[2180 B]
Fetched 50.1 kB in 0s (410 kB/s)
Download complete and in download only mode
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Format: 3.0 (quilt)
Source: python-nmap
Binary: python-nmap, python3-nmap
Architecture: all
Version: 0.4.0-1
Maintainer: Federico Ceratto feder...@debian.org
Uploaders: David Paleino da...@debian.org
Homepage: http://xael.org/norman/python/python-nmap/
Standards-Version: 3.9.6
Vcs-Browser: http://anonscm.debian.org/gitweb/?p=collab-maint/python-nmap.git
Vcs-Git: git://anonscm.debian.org/collab-maint/python-nmap.git
Build-Depends: debhelper (= 9~)
Build-Depends-Indep: dh-python, nmap, python-all (= 2.6.6-3~), python3-all
Package-List:
python-nmap deb python optional arch=all
python3-nmap deb python optional arch=all
Checksums-Sha1:
98ca07d1731d0497aabd8ad10fca97fd6f4a2b90 45862 python-nmap_0.4.0.orig.tar.gz
065b4e7f9716115b18058afdd16cd9d6cd844637 2180 python-nmap_0.4.0-1.debian.tar.xz
Checksums-Sha256:
cee43d5eaa2d2257dbddd4c0be585d5f8f0d81be727b10b13342f37d8ebaae75 45862
python-nmap_0.4.0.orig.tar.gz
fc4e59aa064c77c2241823d0376c1e22cb767cd594aa4dc11bee489828b3a1c3 2180
python-nmap_0.4.0-1.debian.tar.xz
Files:
2046fa63e969ae77b68e91664e97876b 45862 python-nmap_0.4.0.orig.tar.gz
34e44c85fc31c06f64119d74657815cd 2180 python-nmap_0.4.0-1.debian.tar.xz
-BEGIN PGP SIGNATURE-
Version: GnuPG v1
iQIcBAEBAgAGBQJVzb7OAAoJEG8xvET1F32qN/4QAIt8avDYZXvEBRS+QByrSZ75
oFeaSavVS/29yKZ/WOOTaOn6Ply0x5tGVWO9Iu8fLSaTWRmYg7/r3Mh3Jo52AiOW
Bug#795724: capistrano: FTBFS: Failure/Error: expect(Configuration.env.fetch(:test)).to be_true
Source: capistrano Version: 3.2.1-1 Severity: serious Justification: fails to build from source Dear Maintainer, capistrano fails to build from source on unstable/amd64: [..] Failures: 1) Capistrano::Configuration.env is a global accessor to a single instance Failure/Error: expect(Configuration.env.fetch(:test)).to be_true expected true to respond to `true?` or perhaps you meant `be true` or `be_truthy` # ./spec/lib/capistrano/configuration_spec.rb:11:in `block (3 levels) in module:Capistrano' [..] Failed examples: rspec ./spec/lib/capistrano/configuration_spec.rb:9 # Capistrano::Configuration.env is a global accessor to a single instance rspec ./spec/lib/capistrano/version_validator_spec.rb:27 # Capistrano::VersionValidator#verify with exact version valid should be true rspec ./spec/lib/capistrano/version_validator_spec.rb:86 # Capistrano::VersionValidator#verify with pessimistic versioning 1 decimal place valid should be true rspec ./spec/lib/capistrano/version_validator_spec.rb:69 # Capistrano::VersionValidator#verify with pessimistic versioning 2 decimal places valid should be true rspec ./spec/lib/capistrano/version_validator_spec.rb:51 # Capistrano::VersionValidator#verify with optimistic versioning valid should be true rspec ./spec/lib/capistrano/dsl_spec.rb:30 # Capistrano::DSL#stage_set? stage is set should be true rspec ./spec/lib/capistrano/dsl_spec.rb:37 # Capistrano::DSL#stage_set? stage is not set should be false rspec ./spec/lib/capistrano/configuration/servers_spec.rb:110 # Capistrano::Configuration::Servers adding a server can accept multiple servers with the same hostname but different ports or users rspec ./spec/integration/dsl_spec.rb:426 # Capistrano::DSL release path setting release path without a timestamp returns the release path with the current env timestamp rspec ./spec/integration/dsl_spec.rb:370 # Capistrano::DSL configuration SSHKit sets the backend pty rspec ./spec/integration/dsl_spec.rb:220 # Capistrano::DSL setting and fetching hosts when defining a host using a combination of the `server` and `role` syntax fetching servers for a role roles defined using the `server` syntax are included rspec ./spec/integration/dsl_spec.rb:224 # Capistrano::DSL setting and fetching hosts when defining a host using a combination of the `server` and `role` syntax fetching servers for a role roles defined using the `role` syntax are included rspec ./spec/integration/dsl_spec.rb:320 # Capistrano::DSL checking for presence variable is an non-empty array should be true rspec ./spec/integration/dsl_spec.rb:335 # Capistrano::DSL checking for presence variable is nil should be false rspec ./spec/integration/dsl_spec.rb:330 # Capistrano::DSL checking for presence variable exists, is not an array should be true rspec ./spec/integration/dsl_spec.rb:325 # Capistrano::DSL checking for presence variable is an empty array should be false rspec ./spec/lib/capistrano/configuration/server_spec.rb:160 # Capistrano::Configuration::Server#include? value is a symbol value matches server property with :filter should be true rspec ./spec/lib/capistrano/configuration/server_spec.rb:170 # Capistrano::Configuration::Server#include? value is a symbol value matches server property with :exclude should be false rspec ./spec/lib/capistrano/configuration/server_spec.rb:165 # Capistrano::Configuration::Server#include? value is a symbol value matches server property with :select should be true rspec ./spec/lib/capistrano/configuration/server_spec.rb:177 # Capistrano::Configuration::Server#include? value is a symbol value does not match server properly with :filter should be false rspec ./spec/lib/capistrano/configuration/server_spec.rb:182 # Capistrano::Configuration::Server#include? value is a symbol value does not match server properly with :select should be false rspec ./spec/lib/capistrano/configuration/server_spec.rb:187 # Capistrano::Configuration::Server#include? value is a symbol value does not match server properly with :exclude should be true rspec ./spec/lib/capistrano/configuration/server_spec.rb:202 # Capistrano::Configuration::Server#include? value is a proc value matches server property with :select should be true rspec ./spec/lib/capistrano/configuration/server_spec.rb:197 # Capistrano::Configuration::Server#include? value is a proc value matches server property with :filter should be true rspec ./spec/lib/capistrano/configuration/server_spec.rb:207 # Capistrano::Configuration::Server#include? value is a proc value matches server property with :exclude should be false rspec ./spec/lib/capistrano/configuration/server_spec.rb:225 # Capistrano::Configuration::Server#include? value is a proc value does not match server properly with :exclude should be true rspec
Processed: debian-installer-launcher: diff for NMU version 21+nmu1
Processing control commands: tags 784045 + patch Bug #784045 [debian-installer-launcher] debian-installer-launcher needs to depend on sudo Added tag(s) patch. tags 784045 + pending Bug #784045 [debian-installer-launcher] debian-installer-launcher needs to depend on sudo Added tag(s) pending. -- 784045: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=784045 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#784045: debian-installer-launcher: diff for NMU version 21+nmu1
Control: tags 784045 + patch
Control: tags 784045 + pending
Dear maintainer,
I've prepared an NMU for debian-installer-launcher (versioned as 21+nmu1) and
uploaded it to DELAYED/2. Please feel free to tell me if I
should delay it longer.
Thanks,
Iain.
--
e: i...@fsfe.orgw: iain.learmonth.me
x: i...@jabber.fsfe.org t: EPVPN 2105
c: 2M0STB g: IO87we
p: 1F72 607C 5FF2 CCD5 3F01 600D 56FF 9EA4 E984 6C49
diff -Nru debian-installer-launcher-21/debian/changelog debian-installer-launcher-21+nmu1/debian/changelog
--- debian-installer-launcher-21/debian/changelog 2015-07-25 17:28:50.0 +0100
+++ debian-installer-launcher-21+nmu1/debian/changelog 2015-08-16 14:20:33.0 +0100
@@ -1,3 +1,10 @@
+debian-installer-launcher (21+nmu1) unstable; urgency=medium
+
+ * Non-maintainer upload.
+ * Add sudo to Depends. (Closes: #784045)
+
+ -- Iain R. Learmonth i...@debian.org Sun, 16 Aug 2015 14:20:28 +0100
+
debian-installer-launcher (21) unstable; urgency=medium
[ Updated translations ]
diff -Nru debian-installer-launcher-21/debian/control debian-installer-launcher-21+nmu1/debian/control
--- debian-installer-launcher-21/debian/control 2015-06-20 05:43:14.0 +0100
+++ debian-installer-launcher-21+nmu1/debian/control 2015-08-16 14:18:49.0 +0100
@@ -14,7 +14,7 @@
Package: debian-installer-launcher
Section: utils
Architecture: all
-Depends: ${misc:Depends}, menu, psmisc, xterm | x-terminal-emulator
+Depends: ${misc:Depends}, menu, psmisc, xterm | x-terminal-emulator, sudo
Suggests: kexec-tools
Description: Debian Installer desktop launcher
This is a desktop launcher for Debian Installer images. It is intended to be
pgpvYc87xHoJF.pgp
Description: PGP signature
Processed: your mail
Processing commands for cont...@bugs.debian.org: tag 794987 + pending Bug #794987 [mercurial-git] mercurial-git: failed to import extension hgext.git: No module named ignore Added tag(s) pending. thanks Stopping processing here. Please contact me if you need assistance. -- 794987: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=794987 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#795716: [libtest-perl-critic-perl] lintian FTBFS with new version
On Sun, 16 Aug 2015 15:27:36 +0200, Niels Thykier wrote: If you can add more information (like what Niels hinted at on IRC), i can forward the issue upstream. The symptom is: [..] Thanks Niels! Forwarded upstream as https://github.com/Perl-Critic/Test-Perl-Critic/issues/5 now. 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
Processed: bug 795716 is forwarded to https://github.com/Perl-Critic/Test-Perl-Critic/issues/5
Processing commands for cont...@bugs.debian.org: forwarded 795716 https://github.com/Perl-Critic/Test-Perl-Critic/issues/5 Bug #795716 [libtest-perl-critic-perl] [libtest-perl-critic-perl] lintian FTBFS with new version Set Bug forwarded-to-address to 'https://github.com/Perl-Critic/Test-Perl-Critic/issues/5'. thanks Stopping processing here. Please contact me if you need assistance. -- 795716: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=795716 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#795689: libsoup2.4: FTBFS under some locales (eg. fr_CH.UTF-8)
Control: severity -1 important Hello Chris Lamb. The affected package builds fine on all official buildds, thus adjusting the severity accordingly. On Sun, Aug 16, 2015 at 10:52:12AM +0100, Chris Lamb wrote: Source: libsoup2.4 Version: 2.50.0-2 Severity: serious Justification: fails to build from source Dear Maintainer, libsoup2.4 fails to build from source on unstable/amd64 under some locales (eg. LANG=fr_CH.UTF-8): [...] This seems to be a sorting issue and the upstream build scripts already tries to set up environment to sort according to C locale, see http://sources.debian.net/src/libsoup2.4/2.50.0-2/libsoup/Makefile.am/#L315 Please feel free to investigate why this does not work as intended if building under different locales is important to you. (And ofcourse preferrably get any changes needed merged via upstream.) Regards, Andreas Henriksson
Bug#795758: libmessage-passing-perl: FTBFS under some locales (eg. fr_CH.UTF-8)
Source: libmessage-passing-perl
Version: 0.116-1
Severity: serious
Justification: fails to build from source
User: reproducible-bui...@lists.alioth.debian.org
Usertags: ftbfs locale
X-Debbugs-Cc: reproducible-bui...@lists.alioth.debian.org
Dear Maintainer,
libmessage-passing-perl fails to build from source on unstable/amd64
under
some locales (eg. LANG=fr_CH.UTF-8):
[..]
Test Summary Report
---
t/role_connectionmanager.t (Wstat: 512 Tests: 15 Failed: 2)
Failed tests: 12-13
Non-zero exit status: 2
Files=18, Tests=156, 11 wallclock secs ( 0.13 usr 0.10 sys + 4.86
cusr 0.66 csys = 5.75 CPU)
Result: FAIL
Failed 1/18 test programs. 2/156 subtests failed.
Makefile:1091: recipe for target 'test_dynamic' failed
make[1]: *** [test_dynamic] Error 255
make[1]: Leaving directory '/tmp/buildd/libmessage-passing-perl-0.116'
/usr/share/cdbs/1/class/makefile.mk:67: recipe for target
'debian/stamp-makefile-check' failed
make: *** [debian/stamp-makefile-check] Error 2
dpkg-buildpackage: error: debian/rules build gave error exit status 2
[..]
The full build log is attached or can be viewed here:
https://reproducible.debian.net/logs/unstable/amd64/libmessage-passing-perl_0.116-1.build2.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: samedi 15 août 2015, 09:43:00 (UTC+1400)
I: pbuilder-time-stamp: 1439581380
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
I: user script
/var/cache/pbuilder/build//63857/tmp/hooks/D01_modify_environment starting
I: Changing hostname to test build reproducibility
I: user script
/var/cache/pbuilder/build//63857/tmp/hooks/D01_modify_environment finished
- 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: cdbs, devscripts, perl, debhelper, dh-buildinfo, libmoo-perl,
libpackage-variant-perl, libanyevent-perl, libanyevent-handle-udp-perl,
libconfig-any-perl, libmoox-types-mooselike-perl, libmoox-options-perl,
libstring-rewriteprefix-perl, libjson-maybexs-perl, libtry-tiny-perl,
libtask-weaken-perl, libsys-hostname-long-perl, libdatetime-perl,
libnamespace-clean-perl (= 0.23), libmodule-runtime-perl (= 0.013),
libcrypt-blowfish-perl, libnet-statsd-perl, libcrypt-cbc-perl,
libcompress-bzip2-perl
dpkg-deb: building package 'pbuilder-satisfydepends-dummy' in
'/tmp/satisfydepends-aptitude/pbuilder-satisfydepends-dummy.deb'.
Selecting previously unselected package pbuilder-satisfydepends-dummy.
(Reading database ... 20246 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 cdbs; however:
Package cdbs is not installed.
pbuilder-satisfydepends-dummy depends on devscripts; however:
Package devscripts is not installed.
pbuilder-satisfydepends-dummy depends on dh-buildinfo; however:
Package dh-buildinfo is not installed.
pbuilder-satisfydepends-dummy depends on libmoo-perl; however:
Package libmoo-perl is not installed.
pbuilder-satisfydepends-dummy depends on libpackage-variant-perl; however:
Package libpackage-variant-perl is not installed.
pbuilder-satisfydepends-dummy depends on libanyevent-perl; however:
Package libanyevent-perl is not installed.
pbuilder-satisfydepends-dummy depends on libanyevent-handle-udp-perl; however:
Package libanyevent-handle-udp-perl is not installed.
pbuilder-satisfydepends-dummy depends on libconfig-any-perl; however:
Package libconfig-any-perl is not installed.
pbuilder-satisfydepends-dummy d
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:
cdbs{a} devscripts{a} dh-buildinfo{a} dh-python{a}
libalgorithm-c3-perl{a} libanyevent-handle-udp-perl{a}
libanyevent-perl{a}
Bug#795639: assword fails with Decryption error: Decryption failed
Daniel Kahn Gillmor d...@fifthhorseman.net writes: 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 ? No, that file doesn't exist. So it looks like you've located the problem. 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 ? I can't, no, because I get the same problem: mithrandir:~$ gpg2 -kv D15D313882004173 gpg: using classic trust model gpg: keydb_get_keyblock failed: Legacy key gpg: error reading key: No public key Aha. Okay, I seem to have fixed it, although I still don't really understand what happened. On a hunch, I ran: $ gpg2 --import ~/.gnupg/pubring.gpg That spat out a bunch of output (tons and tons of those legacy key messages), and then I ran: $ gpg2 --import ~/.gnupg/secring.gpg again. That prompted me for the passphrase for the private key for D15D313882004173, and then apparently successfully imported it. Now, the gpg2 command works: mithrandir:~$ gpg2 -kv D15D313882004173 gpg: using classic trust model pub rsa4096/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 rsa4096/7CE29A76E9769486 2009-05-29 [expires: 2017-09-17] sub rsa2048/7D80315C5736DE75 2010-09-17 [expires: 2016-03-20] and now assword works again. So, something weird about the automated key import process for gpg2? -- Russ Allbery (r...@debian.org) http://www.eyrie.org/~eagle/
Bug#783330: marked as done (reiserfsprogs: reiserfsck cannot be found at boot while / is reiserfs)
Your message dated Sun, 16 Aug 2015 15:26:55 + with message-id e1zqzpn-0006lw...@franck.debian.org and subject line Bug#791489: fixed in reiserfsprogs 1:3.6.24-3 has caused the Debian Bug report #791489, regarding reiserfsprogs: reiserfsck cannot be found at boot while / is reiserfs to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 791489: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=791489 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: reiserfsprogs Version: 1:3.6.24-1 Severity: normal Tags: d-i Dear Maintainer, I'm debian testing and using reiserfs as the / file system. I found there is a warning message at boot like this: Begin: Checking root file system ... fsck from util-linux 2.25.2 /sbin/fsck.reiserfs: exec: line 18: /sbin/reiserfsck: not found fsck exited with status code 2 done. Warning: File system check failed but did not detect errors I think this bug would make a dirty root file system more and more dirty. Eventually a completely broken, unusable file system. After boot I checked /sbin/fsck.reiserfs and found it is a shell script, rather than a soft-link(which is the case in Archlinux). I got a simple solution like this: Rename fsck.reiserfs or delete it, and run ln -s reiserfsck fsck.reiserfs to get a soft-link of reiserfsck, and finally run update-initramfs -u. -- System Information: Debian Release: 8.0 APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.0.0-xwp (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) Versions of packages reiserfsprogs depends on: ii libc6 2.19-18 ii libuuid1 2.25.2-6 reiserfsprogs recommends no packages. reiserfsprogs suggests no packages. -- no debconf information---End Message--- ---BeginMessage--- Source: reiserfsprogs Source-Version: 1:3.6.24-3 We believe that the bug you reported is fixed in the latest version of reiserfsprogs, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 791...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Felix Zielcke fziel...@z-51.de (supplier of updated reiserfsprogs package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Sun, 16 Aug 2015 16:49:43 +0200 Source: reiserfsprogs Binary: reiserfsprogs reiserfsprogs-udeb mkreiserfs-udeb Architecture: source Version: 1:3.6.24-3 Distribution: unstable Urgency: medium Maintainer: Felix Zielcke fziel...@z-51.de Changed-By: Felix Zielcke fziel...@z-51.de Description: mkreiserfs-udeb - User-level tools for ReiserFS filesystems (udeb) reiserfsprogs - User-level tools for ReiserFS filesystems reiserfsprogs-udeb - User-level tools for ReiserFS filesystems (udeb) Closes: 791489 Changes: reiserfsprogs (1:3.6.24-3) unstable; urgency=medium . * Add hook script to copy /sbin/reiserfsck into initramfs. (Closes: #791489) Checksums-Sha1: 6b02851c04b7cb32baea4000944154a6ffa0a189 1519 reiserfsprogs_3.6.24-3.dsc ff87461f91a68cdc1e1a2e856603c139f7dadf1d 23040 reiserfsprogs_3.6.24-3.debian.tar.xz Checksums-Sha256: 17d0639d4b1f34184de9491380501a1004a559d355b5a080c4db55f48ed0b52d 1519 reiserfsprogs_3.6.24-3.dsc be259f3182242e3973e930ff3103137c84ece34753c5d4874c2efddfda7917a3 23040 reiserfsprogs_3.6.24-3.debian.tar.xz Files: df5a0f88e5e720365b0feadb18d6ff5c 1519 admin optional reiserfsprogs_3.6.24-3.dsc bbaf61101ec320c4a5185b27cc724f3b 23040 admin optional reiserfsprogs_3.6.24-3.debian.tar.xz -BEGIN PGP SIGNATURE- iQEcBAEBCgAGBQJV0KNSAAoJEH84BcfYL7nIiFIH+QE3oF9OFpet+WvG3/qDKgw1 v9Wb28gzRlqfDpv9mMHWlL3XfZgO4I4zHyETVpdeFLV1/9V5G3F1UZLaECafNy/a B/kK+BlVV1sRbHFV7YX0GS4bUtYkAtUTpp+pAg6VBhffiEgeZ/wM5mN0Ma1slcWX bqDf8dcb+8UYk5lx+hOZjALmJluxhRLSPBqMonApTfQjfUBsiJgpZpf6aOIhPI9I qNBNEGWprAer2BdllgNdkKmCRU+dkhTfpmc53iSeUIAvbypVAVn2cKn/aSk11lMr n2on3FZ2oDHjy62o7Tp9TcRPDXPpsk0GP4vFqG7ZKUHd82yK70/ye/PFmUtyfX0= =swqh -END PGP SIGNATUREEnd Message---
Bug#783329: marked as done (reiserfsprogs: reiserfsck cannot be found at boot while / is reiserfs)
Your message dated Sun, 16 Aug 2015 15:26:55 + with message-id e1zqzpn-0006lw...@franck.debian.org and subject line Bug#791489: fixed in reiserfsprogs 1:3.6.24-3 has caused the Debian Bug report #791489, regarding reiserfsprogs: reiserfsck cannot be found at boot while / is reiserfs to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 791489: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=791489 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: reiserfsprogs Version: 1:3.6.24-1 Severity: normal Tags: d-i Dear Maintainer, I'm debian testing and using reiserfs as the / file system. I found there is a warning message at boot like this: Begin: Checking root file system ... fsck from util-linux 2.25.2 /sbin/fsck.reiserfs: exec: line 18: /sbin/reiserfsck: not found fsck exited with status code 2 done. Warning: File system check failed but did not detect errors I think this bug would make a dirty root file system more and more dirty. Eventually a completely broken, unusable file system. After boot I checked /sbin/fsck.reiserfs and found it is a shell script, rather than a soft-link(which is the case in Archlinux). I checked the latest version(1:3.6.24-2), which is still the same shell script. I got a simple solution like this: Rename fsck.reiserfs or delete it, and run ln -s reiserfsck fsck.reiserfs to get a soft-link of reiserfsck, and finally run update-initramfs -u. -- System Information: Debian Release: 8.0 APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.0.0-xwp (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) Versions of packages reiserfsprogs depends on: ii libc6 2.19-18 ii libuuid1 2.25.2-6 reiserfsprogs recommends no packages. reiserfsprogs suggests no packages. -- no debconf information---End Message--- ---BeginMessage--- Source: reiserfsprogs Source-Version: 1:3.6.24-3 We believe that the bug you reported is fixed in the latest version of reiserfsprogs, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 791...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Felix Zielcke fziel...@z-51.de (supplier of updated reiserfsprogs package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Sun, 16 Aug 2015 16:49:43 +0200 Source: reiserfsprogs Binary: reiserfsprogs reiserfsprogs-udeb mkreiserfs-udeb Architecture: source Version: 1:3.6.24-3 Distribution: unstable Urgency: medium Maintainer: Felix Zielcke fziel...@z-51.de Changed-By: Felix Zielcke fziel...@z-51.de Description: mkreiserfs-udeb - User-level tools for ReiserFS filesystems (udeb) reiserfsprogs - User-level tools for ReiserFS filesystems reiserfsprogs-udeb - User-level tools for ReiserFS filesystems (udeb) Closes: 791489 Changes: reiserfsprogs (1:3.6.24-3) unstable; urgency=medium . * Add hook script to copy /sbin/reiserfsck into initramfs. (Closes: #791489) Checksums-Sha1: 6b02851c04b7cb32baea4000944154a6ffa0a189 1519 reiserfsprogs_3.6.24-3.dsc ff87461f91a68cdc1e1a2e856603c139f7dadf1d 23040 reiserfsprogs_3.6.24-3.debian.tar.xz Checksums-Sha256: 17d0639d4b1f34184de9491380501a1004a559d355b5a080c4db55f48ed0b52d 1519 reiserfsprogs_3.6.24-3.dsc be259f3182242e3973e930ff3103137c84ece34753c5d4874c2efddfda7917a3 23040 reiserfsprogs_3.6.24-3.debian.tar.xz Files: df5a0f88e5e720365b0feadb18d6ff5c 1519 admin optional reiserfsprogs_3.6.24-3.dsc bbaf61101ec320c4a5185b27cc724f3b 23040 admin optional reiserfsprogs_3.6.24-3.debian.tar.xz -BEGIN PGP SIGNATURE- iQEcBAEBCgAGBQJV0KNSAAoJEH84BcfYL7nIiFIH+QE3oF9OFpet+WvG3/qDKgw1 v9Wb28gzRlqfDpv9mMHWlL3XfZgO4I4zHyETVpdeFLV1/9V5G3F1UZLaECafNy/a B/kK+BlVV1sRbHFV7YX0GS4bUtYkAtUTpp+pAg6VBhffiEgeZ/wM5mN0Ma1slcWX bqDf8dcb+8UYk5lx+hOZjALmJluxhRLSPBqMonApTfQjfUBsiJgpZpf6aOIhPI9I qNBNEGWprAer2BdllgNdkKmCRU+dkhTfpmc53iSeUIAvbypVAVn2cKn/aSk11lMr n2on3FZ2oDHjy62o7Tp9TcRPDXPpsk0GP4vFqG7ZKUHd82yK70/ye/PFmUtyfX0= =swqh -END PGP SIGNATUREEnd Message---
Bug#794272: marked as done (FTBFS: 'parse a valid XML document with an attribute type=boolean' and others fail)
Your message dated Sun, 16 Aug 2015 15:27:03 +
with message-id e1zqzpv-0006ny...@franck.debian.org
and subject line Bug#794272: fixed in ruby-multi-xml 0.5.5-2
has caused the Debian Bug report #794272,
regarding FTBFS: 'parse a valid XML document with an attribute type=boolean'
and others fail
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
794272: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=794272
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
---BeginMessage---
Source: ruby-multi-xml
Version: 0.5.5-1
Severity: serious
Tags: sid stretch
Justification: fails to build from source
User: reproducible-bui...@lists.alioth.debian.org
Usertags: ftbfs
Dear Maintainer,
The package fails to build:
Failures:
1) MultiXml LibXML parser behaves like a parser .parse a valid XML document
with an attribute type=boolean when true returns true
Failure/Error: expect(MultiXml.parse(xml)['tag']).to
instance_eval(be_#{boolean})
expected true to respond to `true?` or perhaps you meant `be true` or
`be_truthy`
Shared Example Group: a parser called from ./spec/multi_xml_spec.rb:37
# ./spec/parser_shared_example.rb:148:in `block (7 levels) in top
(required)'
2) MultiXml LibXML parser behaves like a parser .parse a valid XML document
with an attribute type=boolean when false returns false
Failure/Error: expect(MultiXml.parse(xml)['tag']).to
instance_eval(be_#{boolean})
expected false to respond to `false?` or perhaps you meant `be false` or
`be_falsey`
Shared Example Group: a parser called from ./spec/multi_xml_spec.rb:37
# ./spec/parser_shared_example.rb:148:in `block (7 levels) in top
(required)'
Finished in 0.44516 seconds (files took 1.03 seconds to load)
328 examples, 16 failures
Full build log:
https://reproducible.debian.net/rb-pkg/unstable/amd64/ruby-multi-xml.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_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
---End Message---
---BeginMessage---
Source: ruby-multi-xml
Source-Version: 0.5.5-2
We believe that the bug you reported is fixed in the latest version of
ruby-multi-xml, which is due to be installed in the Debian FTP archive.
A summary of the changes between this version and the previous one is
attached.
Thank you for reporting the bug, which will now be closed. If you
have further comments please address them to 794...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Jonas Genannt gena...@debian.org (supplier of updated ruby-multi-xml package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Format: 1.8
Date: Sun, 16 Aug 2015 16:38:51 +0200
Source: ruby-multi-xml
Binary: ruby-multi-xml
Architecture: source all
Version: 0.5.5-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Ruby Extras Maintainers
pkg-ruby-extras-maintain...@lists.alioth.debian.org
Changed-By: Jonas Genannt gena...@debian.org
Description:
ruby-multi-xml - generic swappable back-end for XML parsing in Ruby
Closes: 794272
Changes:
ruby-multi-xml (0.5.5-2) unstable; urgency=medium
.
* Team upload.
* bumped compat level to 9
* d/control:
- bumped standards version to 3.9.6
- wrap-sort
* patch for Rspec3 support (Closes: #794272)
Checksums-Sha1:
93a6aca63dba09d75e21f3e94a83dd06998997aa 2150 ruby-multi-xml_0.5.5-2.dsc
ecc42f1f61c7790e2d94764bd257052ca46c610b 3320
ruby-multi-xml_0.5.5-2.debian.tar.xz
f5537075830f50510d1642ffa93912f18bcc4d7e 13436 ruby-multi-xml_0.5.5-2_all.deb
Checksums-Sha256:
3168d443cff9761425d2657ff7ac578316fa8dc0b0b5781686e7b6c8533edbb7 2150
ruby-multi-xml_0.5.5-2.dsc
d41903b943f8046f639c614698a73c27308f51ebfb9fb78cc1f03c9a875a59d7 3320
ruby-multi-xml_0.5.5-2.debian.tar.xz
db4719b83d3639cf7badc53726af6852bfad2de12ece224a15bb6767e272dd90 13436
ruby-multi-xml_0.5.5-2_all.deb
Files:
22e696db13e0267486136754f18da5f2 2150 ruby optional ruby-multi-xml_0.5.5-2.dsc
f69fbd9b231f268f5253e565c5fe07d5 3320 ruby optional
ruby-multi-xml_0.5.5-2.debian.tar.xz
9f327624bf3b4fc83bbe49e11d7f6e3d 13436 ruby optional
ruby-multi-xml_0.5.5-2_all.deb
-BEGIN PGP SIGNATURE-
Bug#791489: marked as done (/sbin/reiserfsck is not included in initrd image)
Your message dated Sun, 16 Aug 2015 15:26:55 +
with message-id e1zqzpn-0006lw...@franck.debian.org
and subject line Bug#791489: fixed in reiserfsprogs 1:3.6.24-3
has caused the Debian Bug report #791489,
regarding /sbin/reiserfsck is not included in initrd image
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
791489: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=791489
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
---BeginMessage---
Package: initramfs-tools
Version: 0.120
Severity: grave
after recent upgrades, which triggered update-initramfs, i've got my system
unbootable, compalining that /sbin/reiserfsck can not be run.
i've dug into the problem, and found that binary isn't copied
by /usr/share/initramfs-tools/hooks/fsck. the latter has the following lines:
for type in $(get_fstypes | sort | uniq); do
if [ $type = 'auto' ] ; then
echo Warning: couldn't identify filesystem type for fsck hook,
ignoring.
continue
fi
+++[ $type = reiserfs ] copy_exec /sbin/reiserfsck
prog=/sbin/fsck.${type}
if [ -h $prog ]; then
link=$(readlink -f $prog)
copy_exec $link
ln -s $link ${DESTDIR}/$prog
elif [ -x $prog ] ; then
copy_exec $prog
else
echo Warning: /sbin/fsck.${type} doesn't exist, can't install
to initramfs, ignoring.
fi
done
(line marked with +++ is added by me as a fix).
the behaviour is that if fsck.$type is binary, it copies it. if it's a link, it
copies linked file too. but fsck.reiserfs is not a binary, neither a symlink.
it's a wrapper script:
#! /bin/sh
# Treat the -y flag the same way other fsck.* instances do
ADD_OPTS=
for opt
do
case $opt in
--)
break
;;
-y)
ADD_OPTS=-a
;;
esac
done
# Be sure to invoke reiserfsck quitely for booting over slow consoles
exec /sbin/reiserfsck -q $ADD_OPTS $@
so we need to modify hook script like i did to fix this. maybe we also need to
check, whether other fs utils have such wrapper scripts, so their users won't
get stuck with the similar problem.
---End Message---
---BeginMessage---
Source: reiserfsprogs
Source-Version: 1:3.6.24-3
We believe that the bug you reported is fixed in the latest version of
reiserfsprogs, which is due to be installed in the Debian FTP archive.
A summary of the changes between this version and the previous one is
attached.
Thank you for reporting the bug, which will now be closed. If you
have further comments please address them to 791...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Felix Zielcke fziel...@z-51.de (supplier of updated reiserfsprogs package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Format: 1.8
Date: Sun, 16 Aug 2015 16:49:43 +0200
Source: reiserfsprogs
Binary: reiserfsprogs reiserfsprogs-udeb mkreiserfs-udeb
Architecture: source
Version: 1:3.6.24-3
Distribution: unstable
Urgency: medium
Maintainer: Felix Zielcke fziel...@z-51.de
Changed-By: Felix Zielcke fziel...@z-51.de
Description:
mkreiserfs-udeb - User-level tools for ReiserFS filesystems (udeb)
reiserfsprogs - User-level tools for ReiserFS filesystems
reiserfsprogs-udeb - User-level tools for ReiserFS filesystems (udeb)
Closes: 791489
Changes:
reiserfsprogs (1:3.6.24-3) unstable; urgency=medium
.
* Add hook script to copy /sbin/reiserfsck into initramfs.
(Closes: #791489)
Checksums-Sha1:
6b02851c04b7cb32baea4000944154a6ffa0a189 1519 reiserfsprogs_3.6.24-3.dsc
ff87461f91a68cdc1e1a2e856603c139f7dadf1d 23040
reiserfsprogs_3.6.24-3.debian.tar.xz
Checksums-Sha256:
17d0639d4b1f34184de9491380501a1004a559d355b5a080c4db55f48ed0b52d 1519
reiserfsprogs_3.6.24-3.dsc
be259f3182242e3973e930ff3103137c84ece34753c5d4874c2efddfda7917a3 23040
reiserfsprogs_3.6.24-3.debian.tar.xz
Files:
df5a0f88e5e720365b0feadb18d6ff5c 1519 admin optional reiserfsprogs_3.6.24-3.dsc
bbaf61101ec320c4a5185b27cc724f3b 23040 admin optional
reiserfsprogs_3.6.24-3.debian.tar.xz
-BEGIN PGP SIGNATURE-
iQEcBAEBCgAGBQJV0KNSAAoJEH84BcfYL7nIiFIH+QE3oF9OFpet+WvG3/qDKgw1
v9Wb28gzRlqfDpv9mMHWlL3XfZgO4I4zHyETVpdeFLV1/9V5G3F1UZLaECafNy/a
Bug#795561: marked as done (zeal: Missing dependency libqt5sql5-sqlite)
Your message dated Sun, 16 Aug 2015 16:51:54 + with message-id e1zr1a2-rk...@franck.debian.org and subject line Bug#795561: fixed in zeal 1:0.1.1-2 has caused the Debian Bug report #795561, regarding zeal: Missing dependency libqt5sql5-sqlite to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 795561: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=795561 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: zeal Version: 1:0.1.1-1 Severity: grave Tags: patch Justification: renders package unusable Dear Maintainer, The installation of the package works without error. At runtime while trying to download new docsets, the download works well but the docsets doesn't show because of the missing dependency. The following error message comes up 6 times: QSqlDatabase: QSQLITE driver not loaded QSqlDatabase: available drivers: SQL Error: Driver not loaded Driver not loaded Installing libqt5sql5-sqlite fixes the issue. Best regards, -- Sammy Tahtah -- System Information: Debian Release: jessie/sid APT prefers trusty-updates APT policy: (500, 'trusty-updates'), (500, 'trusty-security'), (500, 'trusty') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.13.0-24-generic (SMP w/2 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages zeal depends on: ii libarchive133.1.2-7ubuntu2.1 ii libc6 2.19-0ubuntu6.6 ii libgcc1 1:4.9.1-0ubuntu1 ii libqt5core5a5.4.2+dfsg-4 ii libqt5gui5 5.4.2+dfsg-4 ii libqt5network5 5.4.2+dfsg-4 ii libqt5sql5 5.4.2+dfsg-4 ii libqt5webkit5 5.4.2+dfsg-2 ii libqt5widgets5 5.4.2+dfsg-4 ii libstdc++6 5.1.1-14 ii libx11-62:1.6.2-1ubuntu2 zeal recommends no packages. zeal suggests no packages. -- no debconf information ---End Message--- ---BeginMessage--- Source: zeal Source-Version: 1:0.1.1-2 We believe that the bug you reported is fixed in the latest version of zeal, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 795...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. ChangZhuo Chen (陳昌倬) czc...@gmail.com (supplier of updated zeal package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Mon, 17 Aug 2015 00:14:11 +0800 Source: zeal Binary: zeal zeal-dbg Architecture: source amd64 Version: 1:0.1.1-2 Distribution: unstable Urgency: medium Maintainer: ChangZhuo Chen (陳昌倬) czc...@gmail.com Changed-By: ChangZhuo Chen (陳昌倬) czc...@gmail.com Description: zeal - Simple offline API documentation browser zeal-dbg - Debug symbols for zeal Closes: 795561 795564 Changes: zeal (1:0.1.1-2) unstable; urgency=medium . * Add missing dependency libqt5sql5-sqlite. Thanks to Sammy Tahtah (Closes: #795561) * Set ZEAL_VERSION. Thanks to Sammy Tahtah (Closes: #795564) Checksums-Sha1: 33f3f3c4bc05b4a733f02ae7d21405687178130c 1936 zeal_0.1.1-2.dsc 1958a93099a213e7fb1a25d55d55018b7fa20306 3052 zeal_0.1.1-2.debian.tar.xz ec85af434530c8115261e2f7790b5c29035ab43d 3921860 zeal-dbg_0.1.1-2_amd64.deb ce9daf69a0eb656dca7c5256ae17156d43c25fc4 242104 zeal_0.1.1-2_amd64.deb Checksums-Sha256: 28c586cd11f263126ca053d162f97dd0d076b12e7be4686e76b59b3b3bb6c36b 1936 zeal_0.1.1-2.dsc 19175aa7279e5b778e313a6fb5962df44190da57cbda1679c42a018b9443b992 3052 zeal_0.1.1-2.debian.tar.xz ee92e095350199f4c84d3cbc9d736776cd4e1c0aa16c59f24a8db58994b5c443 3921860 zeal-dbg_0.1.1-2_amd64.deb 1d021a9082f11308990ff036c51d67ad9c9cd1ba4e236a5733bf18aed3fb14bb 242104 zeal_0.1.1-2_amd64.deb Files: 33309fe3d753fe359280d74a99bad5fc 1936 utils optional zeal_0.1.1-2.dsc 9503ebbec1b98749245d8edca1e3ac86 3052 utils optional zeal_0.1.1-2.debian.tar.xz 5bee3b16094ecdcfa76e78b961dc6165 3921860 debug extra zeal-dbg_0.1.1-2_amd64.deb 3fa7ac104e223a543a6c6d835f804f8c 242104 utils optional zeal_0.1.1-2_amd64.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1 iQIcBAEBCgAGBQJV0LpdAAoJELTYlw90nD9qyvwQANWQ5KmF1t2Bq6gLpCRDRW7o iMbHr+2vLM1wpDWgi5I4+VWlT+95c1bT2zeRb0meAp+np+LtJ6SrseV9Hgy5FXjK
Bug#795762: ruby-twitter-stream: FTBFS: /usr/bin/ruby2.1 /usr/bin/rspec --pattern ./spec/\*/\*_spec.rb failed
Source: ruby-twitter-stream Version: 0.1.16-1 Severity: serious Justification: fails to build from source User: reproducible-bui...@lists.alioth.debian.org Usertags: ftbfs X-Debbugs-Cc: reproducible-bui...@lists.alioth.debian.org Dear Maintainer, ruby-twitter-stream fails to build from source on unstable/amd64: [..] Failed examples: rspec ./spec/twitter/json_stream_spec.rb:25 # Twitter::JSONStream authentication should connect with basic auth credentials rspec ./spec/twitter/json_stream_spec.rb:30 # Twitter::JSONStream authentication should connect with oauth credentials rspec ./spec/twitter/json_stream_spec.rb:50 # Twitter::JSONStream on create should define default properties rspec ./spec/twitter/json_stream_spec.rb:60 # Twitter::JSONStream on create should connect to the proxy if provided rspec ./spec/twitter/json_stream_spec.rb:90 # Twitter::JSONStream on valid stream should add no params rspec ./spec/twitter/json_stream_spec.rb:95 # Twitter::JSONStream on valid stream should add custom params rspec ./spec/twitter/json_stream_spec.rb:100 # Twitter::JSONStream on valid stream should parse headers rspec ./spec/twitter/json_stream_spec.rb:106 # Twitter::JSONStream on valid stream should parse headers even after connection close rspec ./spec/twitter/json_stream_spec.rb:112 # Twitter::JSONStream on valid stream should extract records rspec ./spec/twitter/json_stream_spec.rb:117 # Twitter::JSONStream on valid stream should allow custom headers rspec ./spec/twitter/json_stream_spec.rb:122 # Twitter::JSONStream on valid stream should deliver each item rspec ./spec/twitter/json_stream_spec.rb:137 # Twitter::JSONStream on valid stream should swallow StandardError exceptions when delivering items rspec ./spec/twitter/json_stream_spec.rb:146 # Twitter::JSONStream on valid stream propagates out runtime errors when delivering items rspec ./spec/twitter/json_stream_spec.rb:154 # Twitter::JSONStream on valid stream should send correct user agent rspec ./spec/twitter/json_stream_spec.rb:212 # Twitter::JSONStream on network failure should timeout on inactivity rspec ./spec/twitter/json_stream_spec.rb:218 # Twitter::JSONStream on network failure should not reconnect on inactivity when not configured to auto reconnect rspec ./spec/twitter/json_stream_spec.rb:224 # Twitter::JSONStream on network failure should reconnect with SSL if enabled rspec ./spec/twitter/json_stream_spec.rb[1:4:4:1] # Twitter::JSONStream on network failure it should behave like network failure should reconnect on network failure rspec ./spec/twitter/json_stream_spec.rb[1:4:4:2] # Twitter::JSONStream on network failure it should behave like network failure should not reconnect on network failure when not configured to auto reconnect rspec ./spec/twitter/json_stream_spec.rb[1:4:4:3] # Twitter::JSONStream on network failure it should behave like network failure should reconnect with 0.25 at base rspec ./spec/twitter/json_stream_spec.rb[1:4:4:4] # Twitter::JSONStream on network failure it should behave like network failure should reconnect with linear timeout rspec ./spec/twitter/json_stream_spec.rb[1:4:4:5] # Twitter::JSONStream on network failure it should behave like network failure should stop reconnecting after 100 times rspec ./spec/twitter/json_stream_spec.rb[1:4:4:6] # Twitter::JSONStream on network failure it should behave like network failure should notify after reconnect limit is reached rspec ./spec/twitter/json_stream_spec.rb:240 # Twitter::JSONStream on no data received should call no data callback after no data received for 90 seconds rspec ./spec/twitter/json_stream_spec.rb[1:6:1:1] # Twitter::JSONStream on server unavailable it should behave like network failure should reconnect on network failure rspec ./spec/twitter/json_stream_spec.rb[1:6:1:2] # Twitter::JSONStream on server unavailable it should behave like network failure should not reconnect on network failure when not configured to auto reconnect rspec ./spec/twitter/json_stream_spec.rb[1:6:1:3] # Twitter::JSONStream on server unavailable it should behave like network failure should reconnect with 0.25 at base rspec ./spec/twitter/json_stream_spec.rb[1:6:1:4] # Twitter::JSONStream on server unavailable it should behave like network failure should reconnect with linear timeout rspec ./spec/twitter/json_stream_spec.rb[1:6:1:5] # Twitter::JSONStream on server unavailable it should behave like network failure should stop reconnecting after 100 times rspec ./spec/twitter/json_stream_spec.rb[1:6:1:6] # Twitter::JSONStream on server unavailable it should behave like network failure should notify after reconnect limit is reached rspec ./spec/twitter/json_stream_spec.rb:272 # Twitter::JSONStream on application failure should reconnect on application failure 10 at base rspec ./spec/twitter/json_stream_spec.rb:278 #
Bug#791771: marked as done (ruby-bdb: FTBFS; dead upstream)
Your message dated Sun, 16 Aug 2015 18:20:50 + with message-id e1zr2y6-0003wz...@franck.debian.org and subject line Bug#791771: fixed in ruby-bdb 0.6.6-2 has caused the Debian Bug report #791771, regarding ruby-bdb: FTBFS; dead upstream to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 791771: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=791771 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: ruby-bdb Version: 0.6.6-1 Severity: serious Justification: fails to build from source (but built successfully in the past) ruby-bdb currently FTBFS with ruby2.2, and only built on 2.1 due to numerous patches. It's also dead upstream. I believe we should remove it (as other distros already did). Christian ---End Message--- ---BeginMessage--- Source: ruby-bdb Source-Version: 0.6.6-2 We believe that the bug you reported is fixed in the latest version of ruby-bdb, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 791...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. David Suárez david.sephi...@gmail.com (supplier of updated ruby-bdb package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Fri, 14 Aug 2015 21:14:55 +0200 Source: ruby-bdb Binary: ruby-bdb Architecture: source Version: 0.6.6-2 Distribution: unstable Urgency: medium Maintainer: Debian Ruby Extras Maintainers pkg-ruby-extras-maintain...@lists.alioth.debian.org Changed-By: David Suárez david.sephi...@gmail.com Description: ruby-bdb - interface to Berkeley DB for Ruby Closes: 791771 Changes: ruby-bdb (0.6.6-2) unstable; urgency=medium . * Team upload . [ Lucas Nussbaum ] * Remove myself from Uploaders. . [ David Suárez ] * debian/control: + Update standards version; no changes needed. + Update Vcs-Browser to use cgit. * debian/patches: + Add 'use-rbconfig-module-instead-of-deprecated-config' patch. (Closes: #791771) + Add 'use-rhash_ifnone-macro-instead-of-deprecated-rhash' patch. Checksums-Sha1: 68d02637f06fc7433f508ca97edab4ab43c20805 2071 ruby-bdb_0.6.6-2.dsc d5c8809c844e0b97cea5d48525a3827ae765b53c 15092 ruby-bdb_0.6.6-2.debian.tar.xz Checksums-Sha256: 2d9b26f2e479edde47ce1f80240e12dd7e7376254b4cd8560f65f554a0ed8f0a 2071 ruby-bdb_0.6.6-2.dsc 70b6779fd817004ba1e900ff5b4835d7bb248916def8f9310c67f55ec47b7888 15092 ruby-bdb_0.6.6-2.debian.tar.xz Files: 0be4c164ab214c9b8a3d9be077196533 2071 ruby optional ruby-bdb_0.6.6-2.dsc 26a17658491abe18798f323d8a22cd11 15092 ruby optional ruby-bdb_0.6.6-2.debian.tar.xz -BEGIN PGP SIGNATURE- Version: GnuPG v1 iQIcBAEBCAAGBQJV0NIaAAoJEFwT1tuTBS4DgCQQAImAjxBoSv6K7cvXfajZptFI skGuAfrlKKK8pvbaX6Ek+XxR1BRfoY+aV0ibDqSwzDP1qrJetsJ/iyZ/P1z+NL3s Je/ZrqcNaWxkom5XIT3KdFX/vUH8DhuRpNJtu6xY5yc6RUcPqYBdLgnJnS7YGp+G Dq6Nd7bFOG00bC2PDogEKwRuomgKVxYJb8WnSF+5Z5y0QMMX2v+17oGe33fsF5tW du/P6CNC1YjQ8uePk2sMnsVew3r7nj8Q6wgI6kUYjYIqrTJR4ALJbyK7k5/+7AiF c/HZmsChMiW+q7ecxLSPcBIx4DzEDwIRnI0C/lxgOpKU3VRWme59kkC6Sgk/fTwG 2jMcbfLjO0ivWj48ZP9N/pIsJZMq8iKxHQoA6l0yQcNuj2Y5tvUpiL8KbsnkPpgE hOhpnDniydzur/goBa5FgmzUlDF9yMUGAKx4ZefOdfyWY802ZpWJ/vzHdIqS0A7Z ZrQl+eYHw/2LXymtP5agsuwiYBKN2jV2H4Ble7uN+6PAM209Law/DpIjgc5zNCOz XlF8/1CV+ALmsEN+CwbspOWn/RC/FROKHGWYmg78NW6hSyticn5H/p9yk5KPjOmj llEibN40MtFu4fQpikjvxPvcMbCSD8NV5tbCFtIeYTguDL4CCCDrDCEyzpRgyryO +xJ2nFrJ0pKo0sIzpH8W =bMTs -END PGP SIGNATUREEnd Message---
Bug#784045: debian-installer-launcher: diff for NMU version 21+nmu1
Hi, Iain R. Learmonth i...@debian.org (2015-08-16): Control: tags 784045 + patch Control: tags 784045 + pending Dear maintainer, I've prepared an NMU for debian-installer-launcher (versioned as 21+nmu1) and uploaded it to DELAYED/2. Please feel free to tell me if I should delay it longer. Thanks. Feel free to reschedule it for immediate acceptance. Should I be adding you to the d-i group on alioth so that you could push your changes directly there? (Feel free to keep the +nmu1 naming for now, and to step in as a regular maintainer whenever you feel like it!) Mraw, KiBi. signature.asc Description: Digital signature
Bug#795756: libsvn-hooks-perl: FTBFS: t/02-generic.t: Failed tests: 11-12
Source: libsvn-hooks-perl
Version: 1.28-1
Severity: serious
Justification: fails to build from source
User: reproducible-bui...@lists.alioth.debian.org
Usertags: ftbfs
X-Debbugs-Cc: reproducible-bui...@lists.alioth.debian.org
Dear Maintainer,
libsvn-hooks-perl fails to build from source on unstable/amd64:
[..]
Test Summary Report
---
t/02-generic.t(Wstat: 512 Tests: 13 Failed: 2)
Failed tests: 11-12
Non-zero exit status: 2
Files=21, Tests=172, 54 wallclock secs ( 0.20 usr 0.06 sys + 35.66
cusr 11.88 csys = 47.80 CPU)
Result: FAIL
Failed 1/21 test programs. 2/172 subtests failed.
Makefile:947: recipe for target 'test_dynamic' failed
make[1]: *** [test_dynamic] Error 255
make[1]: Leaving directory '/tmp/buildd/libsvn-hooks-perl-1.28'
dh_auto_test: make -j1 test TEST_VERBOSE=1 returned exit code 2
debian/rules:7: recipe for target 'build' failed
make: *** [build] Error 2
dpkg-buildpackage: error: debian/rules build gave error exit status 2
[..]
The full build log is attached or can be viewed here:
https://reproducible.debian.net/logs/unstable/amd64/libsvn-hooks-perl_1.28-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 Aug 13 11:56:34 GMT+12 2015
I: pbuilder-time-stamp: 1439510194
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 (= 8), libdata-util-perl, libjira-client-perl,
libsvn-look-perl (= 0.21), libsvn-notify-perl, liburi-perl,
libxmlrpc-lite-perl, perl, subversion
dpkg-deb: building package 'pbuilder-satisfydepends-dummy' in
'/tmp/satisfydepends-aptitude/pbuilder-satisfydepends-dummy.deb'.
Selecting previously unselected package pbuilder-satisfydepends-dummy.
(Reading database ... 20246 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 libdata-util-perl; however:
Package libdata-util-perl is not installed.
pbuilder-satisfydepends-dummy depends on libjira-client-perl; however:
Package libjira-client-perl is not installed.
pbuilder-satisfydepends-dummy depends on libsvn-look-perl (= 0.21); however:
Package libsvn-look-perl is not installed.
pbuilder-satisfydepends-dummy depends on libsvn-notify-perl; however:
Package libsvn-notify-perl is not installed.
pbuilder-satisfydepends-dummy depends on liburi-perl; however:
Package liburi-perl is not installed.
pbuilder-satisfydepends-dummy depends on libxmlrpc-lite-perl; however:
Package libxmlrpc-lite-perl is not installed.
pbuilder-satisfydepends-dummy depends on subversion; however:
Package subversion 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} libapr1{a} libaprutil1{a} libclass-inspector-perl{a}
libconvert-binhex-perl{a} libcrypt-ssleay-perl{a} libdata-util-perl{a}
libencode-locale-perl{a} libexpat1{a} libexporter-tiny-perl{a}
libfcgi-perl{a} libfile-listing-perl{a} libgnutls-deb0-28{a}
libgssapi-krb5-2{a} libhogweed4{a} libhtml-parser-perl{a}
libhtml-tagset-perl{a} libhtml-tree-perl{a} libhttp-cookies-perl{a}
libhttp-daemon-perl{a} libhttp-date-perl{a} libhttp-message-perl{a}
libhttp-negotiate-perl{a} libio-html-perl{a} libio-sessiondata-perl{a}
libio-socket-ssl-perl{a} libio-stringy-perl{a} libjira-client-perl{a}
libk5crypto3{a} libkeyutils1{a} libkrb5-3{a} libkrb5support0{a}
libldap-2.4-2{a} liblist-moreutils-perl{a} liblwp-mediatypes-perl{a}
liblwp-protocol-https-perl{a} libmailtools-perl{a} libmime-tools-perl{a}
libnet-http-perl{a} libnet-smtp-ssl-perl{a} libnet-ssleay-perl{a}
libnettle6{a} libossp-uuid-perl{a}
Bug#777887: This is being fixed upstream
Hi. Upstream maintainer here. This is fixed upstream. Albeit not in any released version yet. But notable thing is that only tests are broken on gcc 5, not actual code.
Bug#795763: ruby-pdf-reader: FTBFS: configuration.rb:656:in `block in expect_with': :stdlib is not supported (ArgumentError)
Source: ruby-pdf-reader
Version: 1.3.3-1
Severity: serious
Justification: fails to build from source
User: reproducible-bui...@lists.alioth.debian.org
Usertags: ftbfs
X-Debbugs-Cc: reproducible-bui...@lists.alioth.debian.org
Dear Maintainer,
ruby-pdf-reader fails to build from source on unstable/amd64:
[..]
/usr/bin/ruby2.1 /usr/bin/gem2deb-test-runner
Running tests for ruby2.1 using debian/ruby-tests.rake ...
RUBYLIB=/tmp/buildd/ruby-pdf-reader-1.3.3/debian/ruby-pdf-reader/usr/lib/ruby/vendor_ruby:.
ruby2.1 -rrake -e ARGV.unshift\(\-f\,\
\debian/ruby-tests.rake\\)\;\ Rake.application.run
/usr/bin/ruby2.1 /usr/bin/rspec --pattern
spec/\*\*\{,/\*/\*\*\}/\*_spec.rb
/usr/lib/ruby/vendor_ruby/rspec/core/configuration.rb:656:in `block in
expect_with': :stdlib is not supported (ArgumentError)
from
/usr/lib/ruby/vendor_ruby/rspec/core/configuration.rb:635:in
`map'
from
/usr/lib/ruby/vendor_ruby/rspec/core/configuration.rb:635:in
`expect_with'
from /tmp/buildd/ruby-pdf-reader-1.3.3/spec/spec_helper.rb:20:in
`block in top (required)'
from /usr/lib/ruby/vendor_ruby/rspec/core.rb:97:in `configure'
from /tmp/buildd/ruby-pdf-reader-1.3.3/spec/spec_helper.rb:19: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-pdf-reader-1.3.3/spec/buffer_spec.rb:3:in
`top (required)'
from
/usr/lib/ruby/vendor_ruby/rspec/core/configuration.rb:1327:in
`load'
from
/usr/lib/ruby/vendor_ruby/rspec/core/configuration.rb:1327:in
`block in load_spec_files'
from
/usr/lib/ruby/vendor_ruby/rspec/core/configuration.rb:1325:in
`each'
from
/usr/lib/ruby/vendor_ruby/rspec/core/configuration.rb:1325:in
`load_spec_files'
from /usr/lib/ruby/vendor_ruby/rspec/core/runner.rb:103: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-pdf-reader-1.3.3/debian/ruby-pdf-reader returned exit
code 1
debian/rules:18: recipe for target 'override_dh_auto_install' failed
make[1]: *** [override_dh_auto_install] Error 1
make[1]: Leaving directory '/tmp/buildd/ruby-pdf-reader-1.3.3'
debian/rules:15: recipe for target 'binary' failed
make: *** [binary] Error 2
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-pdf-reader_1.3.3-1.build1.log.gz
Regards,
--
,''`.
: :' : Chris Lamb
`. `'` la...@debian.org / chris-lamb.co.uk
`-
I: using fakeroot in build.
I: pbuilder: network access will be disabled during build
I: Current time: Mon Jul 13 21:08:49 GMT+12 2015
I: pbuilder-time-stamp: 1436864929
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.3~),
ruby-ascii85 (= 1.0.0~), ruby-rc4, ruby-afm, ruby-hashery, ruby-ttfunk
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.3.0~); however:
Package gem2deb is not installed.
Bug#795736: Regexp misquoting fails to cope with some package names
Package: dgit
Version: 1.0
Severity: serious
Tags: patch
$ dgit clone dbus-c++
canonical suite name for unstable is sid
starting new git history
downloading
http://ftp.debian.org/debian//pool/main/d/dbus-c++/dbus-c++_0.9.0-7.dsc...
last upload to archive has NO git hash
dbus-c++_0.9.0.orig.tar.gz ? at /usr/bin/dgit line 1483.
diff --git a/dgit b/dgit
index eb9a97c..b102e04 100755
--- a/dgit
+++ b/dgit
@@ -1481,7 +1481,7 @@ sub complete_file_from_dsc ($$) {
my $furl = $dscurl;
$furl =~ s{/[^/]+$}{};
$furl .= /$f;
- die $f ? unless $f =~ m/^${package}_/;
+ die $f ? unless $f =~ m/^\Q${package}\E_/;
die $f ? if $f =~ m#/#;
runcmd_ordryrun_local @curl,qw(-o),$tf,'--',$furl;
next if !act_local();
Ian.
Bug#795744: marked as done (haskell-yaml: FTBFS: can't load .so/.DLL for: [..] libHSaeson-qq-0.7.4-ghc7.8.4.so)
Your message dated Sun, 16 Aug 2015 17:43:21 +0200 with message-id 1439739801.8565.2.ca...@debian.org and subject line Re: Bug#795744: haskell-yaml: FTBFS: can't load .so/.DLL for: [..] libHSaeson-qq-0.7.4-ghc7.8.4.so has caused the Debian Bug report #795744, regarding haskell-yaml: FTBFS: can't load .so/.DLL for: [..] libHSaeson-qq-0.7.4-ghc7.8.4.so to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 795744: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=795744 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Source: haskell-yaml Version: 0.8.12-1 Severity: serious Justification: fails to build from source Tags: sid 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: Loading package haskell-src-meta-0.6.0.10 ... linking ... done. Loading package parsec-3.1.9 ... linking ... done. Loading package aeson-qq-0.7.4 ... command line: can't load .so/.DLL for: /usr/lib/haskell-packages/ghc/lib/x86_64-linux-ghc-7.8.4/aeson-qq-0.7.4/libHSaeson-qq-0.7.4-ghc7.8.4.so (libHScpphs-1.19-ghc7.8.4.so: cannot open shared object file: No such file or directory) /usr/share/cdbs/1/class/hlibrary.mk:146: recipe for target 'build-ghc-stamp' failed make: *** [build-ghc-stamp] Error 1 dpkg-buildpackage: error: debian/rules build gave error exit status 2 Full build log: https://reproducible.debian.net/rb-pkg/unstable/amd64/haskell-yaml.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) ---End Message--- ---BeginMessage--- Hi, thanks for the report. This is a corner case where our system of provides/depends fails. I scheduled a binNMU of aeson-qq, which should fix this. Thanks, 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 ---End Message---
Bug#795616: dvbcut: Illegal changelog date format
I assume you tried to build dvbcut for the current gcc transition on testing/unstable where you got an error as following. # dpkg-buildpackage Error parsing time at /usr/lib/x86_64-linux-gnu/perl/5.20/Time/Piece.pm line 469, $filehandle line 12. Yes, hence my: since dpkg-dev 1.18.2, date parsing is stricter and thus dpkg-parsechangelog, dpkg-genchanges (etc.) fail to process the file. .. :) I uploaded a changed package to mentors.debian.net and will send a RFS shortly. Thanks. Regards, -- ,''`. : :' : Chris Lamb `. `'` la...@debian.org / chris-lamb.co.uk `-
Bug#795616: dvbcut: Illegal changelog date format
Hello Chris, I am sorry for this this mistake. I assume you tried to build dvbcut for the current gcc transition on testing/unstable where you got an error as following. # dpkg-buildpackage Error parsing time at /usr/lib/x86_64-linux-gnu/perl/5.20/Time/Piece.pm line 469, $filehandle line 12. I uploaded a changed package to mentors.debian.net and will send a RFS shortly. Kind regards, Bernhard
Processed: Re: libsoup2.4: FTBFS under some locales (eg. fr_CH.UTF-8)
Processing control commands: severity -1 important Bug #795689 [src:libsoup2.4] libsoup2.4: FTBFS under some locales (eg. fr_CH.UTF-8) Severity set to 'important' from 'serious' -- 795689: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=795689 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#795322: marked as done (cryptmount: FTBFS: assumes automake-1.14)
Your message dated Sun, 16 Aug 2015 17:12:44 +0100 with message-id 20150816171244.7a8845cd@mondschein.sonatas and subject line Re: Bug#795322: cryptmount: FTBFS - fixed in version 5.1-2 has caused the Debian Bug report #795322, regarding cryptmount: FTBFS: assumes automake-1.14 to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 795322: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=795322 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Source: cryptmount Version: 5.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: ... Preparing to unpack .../automake_1%3a1.15-2_all.deb ... Unpacking automake (1:1.15-2) ... ... dh_testdir # Add here commands to compile the package. /usr/bin/make make[1]: Entering directory '/cryptmount-5.1' cd . /bin/bash /cryptmount-5.1/missing automake-1.14 --gnu --ignore-deps Makefile /cryptmount-5.1/missing: line 81: automake-1.14: command not found WARNING: 'automake-1.14' is missing on your system. You should only need it if you modified 'Makefile.am' or 'configure.ac' or m4 files included by 'configure.ac'. The 'automake' program is part of the GNU Automake package: http://www.gnu.org/software/automake It also requires GNU Autoconf, GNU m4 and Perl in order to run: http://www.gnu.org/software/autoconf http://www.gnu.org/software/m4/ http://www.perl.org/ Makefile:399: recipe for target 'Makefile.in' failed make[1]: *** [Makefile.in] Error 127 Full build log: https://reproducible.debian.net/rb-pkg/unstable/amd64/cryptmount.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) ---End Message--- ---BeginMessage--- This issue has been fixed with the recent upload of cryptmount-5.1-2, which includes an updated debhelper v7 build-system.---End Message---
Bug#791540: marked as done (FTBFS: undefined reference to symbol 'SDL_UnlockSurface')
Your message dated Sun, 16 Aug 2015 16:35:10 + with message-id e1zr0tq-0006rc...@franck.debian.org and subject line Bug#791540: fixed in gnujump 1.0.8-3 has caused the Debian Bug report #791540, regarding FTBFS: undefined reference to symbol 'SDL_UnlockSurface' to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 791540: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=791540 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: gnujump Version: 1.0.8-2 Severity: serious gnujump fails to build in unstable: sbuild (Debian sbuild) 0.64.1 (13 Oct 2013) on m400-c3n1.hlinux.usa.hp.com ... /bin/bash ../libtool --tag=CC --mode=link gcc -I/usr/include/libdrm -g -DPREFIX=\/usr\ -DDATA_PREFIX=\/usr/share/games\ -Wl,--as-needed -o gnujump game.o game-input.o game-output.o game-logic.o game-tools.o game-timer.o main.o menu.o menu-system.o records.o SDL_2dgl.o SDL_rotozoom.o setup.o SFont.o sprite.o surface.o tools.o replay.o effects-trail.o effects-blur.o -lm -lGL -lGLU -lGL -lSDL_image -lSDL_mixer libtool: link: gcc -I/usr/include/libdrm -g -DPREFIX=\/usr\ -DDATA_PREFIX=\/usr/share/games\ -Wl,--as-needed -o gnujump game.o game-input.o game-output.o game-logic.o game-tools.o game-timer.o main.o menu.o menu-system.o records.o SDL_2dgl.o SDL_rotozoom.o setup.o SFont.o sprite.o surface.o tools.o replay.o effects-trail.o effects-blur.o -lm -lGLU -lGL -lSDL_image -lSDL_mixer /usr/bin/ld: SDL_rotozoom.o: undefined reference to symbol 'SDL_UnlockSurface' //usr/lib/aarch64-linux-gnu/libSDL-1.2.so.0: error adding symbols: DSO missing from command line collect2: error: ld returned 1 exit status make[4]: *** [gnujump] Error 1 -- Martin Michlmayr Linux for HP Helion, Hewlett-Packard ---End Message--- ---BeginMessage--- Source: gnujump Source-Version: 1.0.8-3 We believe that the bug you reported is fixed in the latest version of gnujump, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 791...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Evgeni Golov evg...@debian.org (supplier of updated gnujump package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Sun, 16 Aug 2015 18:13:17 +0200 Source: gnujump Binary: gnujump gnujump-data Architecture: source all amd64 Version: 1.0.8-3 Distribution: unstable Urgency: medium Maintainer: Debian Games Team pkg-games-de...@lists.alioth.debian.org Changed-By: Evgeni Golov evg...@debian.org Description: gnujump- platform game where you have to jump up to survive gnujump-data - platform game where you have to jump up to survive - data files Closes: 778968 791540 Changes: gnujump (1.0.8-3) unstable; urgency=medium . [ Paul Wise ] * Fix build reproducibility issues due to use of imagemagick Closes: #778968 . [ Evgeni Golov ] * Fix a typo in acinclude.m4 which led to FTBFS when autoconf-archive was installed. Thanks to Martin Michlmayr t...@hp.com for reporting and James Cowgill james...@cowgill.org.uk for debugging and providing the patch. Closes: #791540 * Use dh-autoreconf instead of calling autoreconf ourself. Checksums-Sha1: 622d9167db833bc26b49e42c067a54adbca04880 2074 gnujump_1.0.8-3.dsc ab06de251df1073f1597c93295b18141b9fa2d35 6240 gnujump_1.0.8-3.debian.tar.xz 1c9ad499789e41f2f397e013af31b847439a25fe 1508050 gnujump-data_1.0.8-3_all.deb 0937a1bf83a396b8dca21cb38db2bbfead9520fb 54760 gnujump_1.0.8-3_amd64.deb Checksums-Sha256: de73657656266d82c81d56d4856839849bff2259c223c3bc42f0d6d9e6928d53 2074 gnujump_1.0.8-3.dsc 69dc1701ccf7edb0efc07787b5ef97ab4ca0e1d1fb9ab72709b00aa633dd18c8 6240 gnujump_1.0.8-3.debian.tar.xz d411a6f7e11b55cd22dffa2018fe8e2e53d1cecc291c4b45f76a2e21d55a4fd3 1508050 gnujump-data_1.0.8-3_all.deb 05f54757f3bab065f79fca3a25c2f1ab3b2bc99e7720ff4bbf38afa2cf11f675 54760 gnujump_1.0.8-3_amd64.deb Files: d6fadcbf3683aabed580cb582e7569aa 2074 games optional gnujump_1.0.8-3.dsc 3ef6904d446dc2865ec3e7810e2e1374 6240 games optional gnujump_1.0.8-3.debian.tar.xz cb2f555090d9f16ef3b4d316861f98c1 1508050 games optional gnujump-data_1.0.8-3_all.deb
Bug#784045: welcome, irl! (was: Bug#784045: debian-installer-launcher: diff for NMU version) 21+nmu1
Cyril Brulebois k...@debian.org (2015-08-16): Iain R. Learmonth i...@debian.org (2015-08-16): Control: tags 784045 + patch Control: tags 784045 + pending Dear maintainer, I've prepared an NMU for debian-installer-launcher (versioned as 21+nmu1) and uploaded it to DELAYED/2. Please feel free to tell me if I should delay it longer. Thanks. Feel free to reschedule it for immediate acceptance. Should I be adding you to the d-i group on alioth so that you could push your changes directly there? (Feel free to keep the +nmu1 naming for now, and to step in as a regular maintainer whenever you feel like it!) As discussed on IRC: welcome to the d-i group. :) Mraw, KiBi. signature.asc Description: Digital signature
Bug#795734: libnet-duo-perl: FTBFS:
Source: libnet-duo-perl
Version: 1.00-1
Severity: serious
Justification: fails to build from source
User: reproducible-bui...@lists.alioth.debian.org
Usertags: ftbfs
X-Debbugs-Cc: reproducible-bui...@lists.alioth.debian.org
Dear Maintainer,
libnet-duo-perl fails to build from source on unstable/amd64:
[..]
Test Summary Report
---
t/admin/groups.t (Wstat: 256 Tests: 20 Failed: 1)
Failed test: 13
Non-zero exit status: 1
Files=19, Tests=879, 20 wallclock secs ( 0.25 usr 0.10 sys + 18.36
cusr 0.98 csys = 19.69 CPU)
Result: FAIL
Failed 1/19 test programs. 1/879 subtests failed.
dh_auto_test: perl Build test --verbose 1 returned exit code 255
debian/rules:7: recipe for target 'build' failed
make: *** [build] Error 255
dpkg-buildpackage: error: debian/rules build gave error exit status 2
[..]
The full build log is attached or can be viewed here:
https://reproducible.debian.net/logs/unstable/amd64/libnet-duo-perl_1.00-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 01:08:36 GMT+12 2015
I: pbuilder-time-stamp: 1437138516
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 (= 9), libjson-perl, libmodule-build-perl,
libperl6-slurp-perl, libsub-install-perl, libtest-minimumversion-perl,
libtest-pod-perl, libtest-pod-coverage-perl, libtest-strict-perl,
libtest-synopsis-perl, liburi-perl, libwww-perl
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 libjson-perl; however:
Package libjson-perl is not installed.
pbuilder-satisfydepends-dummy depends on libmodule-build-perl; however:
Package libmodule-build-perl is not installed.
pbuilder-satisfydepends-dummy depends on libperl6-slurp-perl; however:
Package libperl6-slurp-perl is not installed.
pbuilder-satisfydepends-dummy depends on libsub-install-perl; however:
Package libsub-install-perl is not installed.
pbuilder-satisfydepends-dummy depends on libtest-minimumversion-perl; however:
Package libtest-minimumversion-perl is not installed.
pbuilder-satisfydepends-dummy depends on libtest-pod-perl; however:
Package libtest-pod-perl is not installed.
pbuilder-satisfydepends-dummy depends on libtest-pod-coverage-perl; however:
Package libtest-pod-coverage-perl is not installed.
pbuilder-satisfydepends-dummy depends on libtest-strict-perl; however:
Packag
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} libb-keywords-perl{a}
libclass-data-inheritable-perl{a} libclass-inspector-perl{a}
libclass-method-modifiers-perl{a} libclass-tiny-perl{a} libclone-perl{a}
libconfig-tiny-perl{a} libcpan-meta-perl{a} libdata-optlist-perl{a}
libdevel-cover-perl{a} libdevel-stacktrace-perl{a}
libdevel-symdump-perl{a} libemail-address-perl{a}
libencode-locale-perl{a} libexception-class-perl{a}
libexporter-tiny-perl{a} libfile-find-rule-perl{a}
libfile-find-rule-perl-perl{a} libfile-homedir-perl{a}
libfile-listing-perl{a} libfile-sharedir-perl{a}
libfile-sharedir-projectdistdir-perl{a} libfile-which-perl{a}
libhtml-parser-perl{a} libhtml-tagset-perl{a} libhtml-tree-perl{a}
libhttp-cookies-perl{a} libhttp-date-perl{a} libhttp-message-perl{a}
libhttp-negotiate-perl{a} libio-html-perl{a} libio-socket-ssl-perl{a}
libio-string-perl{a} libio-stringy-perl{a}
Bug#789106: FTBFS: missing build-dep on zlib: pkg-config fails
On 2015-06-18, Vagrant Cascadian wrote: onfigure:4666: checking for SSH2 configure:4673: $PKG_CONFIG --exists --print-errors libssh2 Package zlib was not found in the pkg-config search path. Perhaps you should add the directory containing `zlib.pc' to the PKG_CONFIG_PATH environment variable Package 'zlib', required by 'libssh2', not found configure:4676: $? = 1 It looks like it needs zlib1g-dev. Thanks for the report! Not sure what changed in jessie (where it builds fine) and sid (where it FTBFS), but added to Build-Depends in bzr: https://bazaar.launchpad.net/~ltsp-upstream/ltsp/libpam-sshauth/revision/102 Will include in the next upload. I'm considering weather libpam-sshauth is worth continued maintenance. The primary upstream developer, while awesome, is only active periodically... We *may* want to use this for LTSP, or we may want to explore more standardized options... At the moment, I'd like to sit on this a bit, so please no NMUs. live well, vagrant signature.asc Description: PGP signature
Bug#795741: libopengl-perl: FTBFS: undefined symbol: glResizeBuffersMESA
Package: libopengl-perl Version: 0.6704+dfsg-1 Severity: serious X-Debbugs-Cc: libgl1-mesa-...@packages.debian.org As noticed by the reproducible builds CI setup, this package fails to build on current sid. # Failed test 'require OpenGL;' # at t/00_require.t line 3. # Tried to require 'OpenGL'. # Error: Can't load '/«BUILDDIR»/libopengl-perl-0.6704+dfsg/blib/arch/auto/OpenGL/OpenGL.so' for module OpenGL: /«BUILDDIR»/libopengl-perl-0.6704+dfsg/blib/arch/auto/OpenGL/OpenGL.so: undefined symbol: glResizeBuffersMESA at /usr/lib/x86_64-linux-gnu/perl/5.20/DynaLoader.pm line 187. It looks like mesa 10.6 dropped a bunch of symbols without changing the SONAME. Copying the maintainer. Was this an intentional ABI break? On current sid, without rebuilding anything: # PERL_DL_NONLAZY=1 perl -e 'use OpenGL' Can't load '/usr/lib/x86_64-linux-gnu/perl5/5.20/auto/OpenGL/OpenGL.so' for module OpenGL: /usr/lib/x86_64-linux-gnu/perl5/5.20/auto/OpenGL/OpenGL.so: undefined symbol: glResizeBuffersMESA at /usr/lib/x86_64-linux-gnu/perl/5.20/DynaLoader.pm line 187. This is also http://sourceforge.net/p/pogl/bugs/21/ https://bugzilla.redhat.com/show_bug.cgi?id=1224294 which have the attached patch that deletes references to the removed symbols. Even with that applied, I suppose at least some Breaks entries would be in order? -- Niko Tyni nt...@debian.org From e83b9048c43cbcbdaeb287dd571ab7e277e19979 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Petr=20P=C3=ADsa=C5=99?= ppi...@redhat.com Date: Mon, 8 Jun 2015 17:06:52 +0200 Subject: [PATCH] Delete functions removed from Mesa MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit mesa-libGL between 10.6.0-0.devel.5.51e3453 and 10.6.0-0.devel.6.5a55f68 removed these functions: glWindowPos4dMESA glWindowPos4iMESA glWindowPos3iMESA glWindowPos2dMESA glWindowPos2iMESA glWindowPos3dMESA glResizeBuffersMESA https://bugzilla.redhat.com/show_bug.cgi?id=1224738 https://bugzilla.redhat.com/show_bug.cgi?id=1224294 Signed-off-by: Petr Písař ppi...@redhat.com --- pogl_gl_Vert_Multi.xs | 54 --- 1 file changed, 54 deletions(-) diff --git a/pogl_gl_Vert_Multi.xs b/pogl_gl_Vert_Multi.xs index e360e5c..4e8a010 100644 --- a/pogl_gl_Vert_Multi.xs +++ b/pogl_gl_Vert_Multi.xs @@ -359,60 +359,6 @@ glEdgeFlagPointerEXT_oga(oga) #endif -#ifdef GL_MESA_window_pos - -#// glWindowPos2iMESA($x, $y); -void -glWindowPos2iMESA(x, y) - GLint x - GLint y - -#// glWindowPos2dMESA($x, $y); -void -glWindowPos2dMESA(x, y) - GLdoublex - GLdoubley - -#// glWindowPos3iMESA($x, $y, $z); -void -glWindowPos3iMESA(x, y, z) - GLint x - GLint y - GLint z - -#// glWindowPos3dMESA($x, $y, $z); -void -glWindowPos3dMESA(x, y, z) - GLdoublex - GLdoubley - GLdoublez - -#// glWindowPos4iMESA($x, $y, $z, $w); -void -glWindowPos4iMESA(x, y, z, w) - GLint x - GLint y - GLint z - GLint w - -#// glWindowPos4dMESA($x, $y, $z, $w); -void -glWindowPos4dMESA(x, y, z, w) - GLdoublex - GLdoubley - GLdoublez - GLdoublew - -#endif - -#ifdef GL_MESA_resize_buffers - -#// glResizeBuffersMESA(); -void -glResizeBuffersMESA() - -#endif - #ifdef GL_ARB_draw_buffers #//# glDrawBuffersARB_c($n,(CPTR)buffers); -- 2.1.0
Bug#794987: marked as done (mercurial-git: failed to import extension hgext.git: No module named ignore)
Your message dated Sun, 16 Aug 2015 15:21:49 + with message-id e1zqzkr-0005t0...@franck.debian.org and subject line Bug#794987: fixed in hg-git 0.8.1-3 has caused the Debian Bug report #794987, regarding mercurial-git: failed to import extension hgext.git: No module named ignore to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 794987: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=794987 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: mercurial-git Version: 0.8.1-2 Severity: important In a repository using hg-git: $ hg status *** failed to import extension hgext.git: No module named ignore ** unknown exception encountered, please report by visiting ** http://mercurial.selenic.com/wiki/BugTracker ** Python 2.7.10 (default, Jul 1 2015, 10:54:53) [GCC 4.9.2] ** Mercurial Distributed SCM (version 3.5) ** Extensions loaded: color, graphlog, hgk, strip, mq, pager, purge, record, rebase, histedit, gpg Traceback (most recent call last): File /usr/bin/hg, line 43, in module mercurial.dispatch.run() File /usr/lib/python2.7/dist-packages/mercurial/dispatch.py, line 30, in run sys.exit((dispatch(request(sys.argv[1:])) or 0) 255) File /usr/lib/python2.7/dist-packages/mercurial/dispatch.py, line 92, in dispatch ret = _runcatch(req) File /usr/lib/python2.7/dist-packages/mercurial/dispatch.py, line 163, in _runcatch return _dispatch(req) File /usr/lib/python2.7/dist-packages/mercurial/dispatch.py, line 862, in _dispatch repo = hg.repository(ui, path=path) File /usr/lib/python2.7/dist-packages/mercurial/hg.py, line 136, in repository peer = _peerorrepo(ui, path, create) File /usr/lib/python2.7/dist-packages/mercurial/hg.py, line 123, in _peerorrepo obj = _peerlookup(path).instance(ui, path, create) File /usr/lib/python2.7/dist-packages/mercurial/hg.py, line 93, in _peerlookup return thing(path) File /usr/lib/python2.7/dist-packages/hgext/git/__init__.py, line 84, in _local p = urlcls(path).localpath() TypeError: 'NoneType' object is not callable -- System Information: Debian Release: stretch/sid APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.0.0-2-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages mercurial-git depends on: ii mercurial 3.5-1 ii python-dulwich 0.10.1-1 pn python:any none mercurial-git recommends no packages. mercurial-git suggests no packages. -- no debconf information ---End Message--- ---BeginMessage--- Source: hg-git Source-Version: 0.8.1-3 We believe that the bug you reported is fixed in the latest version of hg-git, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 794...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Javi Merino vi...@debian.org (supplier of updated hg-git package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Sun, 16 Aug 2015 10:32:47 +0100 Source: hg-git Binary: mercurial-git Architecture: source all Version: 0.8.1-3 Distribution: unstable Urgency: medium Maintainer: Python Applications Packaging Team python-apps-t...@lists.alioth.debian.org Changed-By: Javi Merino vi...@debian.org Description: mercurial-git - Git plugin for Mercurial Closes: 794987 Changes: hg-git (0.8.1-3) unstable; urgency=medium . * Add 6 patches from upstream to make mercurial-git 0.8.1 work with mercurial 3.5-1 (Closes: #794987) * Run the testsuite when building the package Checksums-Sha1: 4499d0e6d283fd05a369dabc986ba7bda992733d 1984 hg-git_0.8.1-3.dsc b38ad695f4a7156eb1cebe99290bb306e5f18be3 6696 hg-git_0.8.1-3.debian.tar.xz ba3d84d0e1ecf04fbdb4f983bfe848ff9eff9916 41612 mercurial-git_0.8.1-3_all.deb Checksums-Sha256: b2b1faf623d06eff47dc94681eeb5078cefc97a15e71821dd0c7f5498b5753d2 1984 hg-git_0.8.1-3.dsc 8d8fab18c302b5274b711d50183ad68b3371255ec1715789c17ee2aff21d1d5e 6696 hg-git_0.8.1-3.debian.tar.xz
Bug#795759: pyicu: FTBFS under some locales (eg. fr_CH.UTF-8)
Source: pyicu
Version: 1.9.2-1
Severity: serious
Justification: fails to build from source
User: reproducible-bui...@lists.alioth.debian.org
Usertags: ftbfs locale
X-Debbugs-Cc: reproducible-bui...@lists.alioth.debian.org
Dear Maintainer,
pyicu fails to build from source on unstable/amd64 under
some locales (eg. LANG=fr_CH.UTF-8):
[..]
/usr/lib/python3.4/distutils/dist.py:260: UserWarning: Unknown
distribution option: 'test_suite'
warnings.warn(msg)
set -e; \
for file in `find /tmp/buildd/pyicu-1.9.2/build -type f -name
docs.py`; do \
mv $file `dirname $file`/icu_docs.py; done
set -ex ;\
for test in `ls test/*.py`; do \
for py in 2.7 3.4; do \
(cd build/py${py%%.*}; \
PYTHONPATH=`ls -d $(pwd)/build/lib.*-$py` \
python$py $test ;\
PYTHONPATH=`ls -d $(pwd)/build/lib_d.*-$py || ls -d
$(pwd)/build/lib.*-$py-pydebug` \
python$py-dbg $test) ;\
done ;\
done
+ ls test/__init__.py test/test_BreakIterator.py test/test_Charset.py
test/test_Collator.py test/test_LayoutEngine.py
test/test_ListFormatter.py test/test_LocaleData.py
test/test_MessageFormat.py test/test_Normalizer.py test/test_Spoof.py
test/test_Transliterator.py test/test_UCS4.py test/test_UDate.py
+ cd build/py2
+ pwd
+ ls -d /tmp/buildd/pyicu-1.9.2/build/py2/build/lib.linux-x86_64-2.7
+
PYTHONPATH=/tmp/buildd/pyicu-1.9.2/build/py2/build/lib.linux-x86_64-2.7
python2.7 test/__init__.py
fontTools package not found, skipping LayoutEngine tests
.E
==
ERROR: testCoverage (test_LocaleData.TestLocaleData)
--
Traceback (most recent call last):
File /tmp/buildd/pyicu-1.9.2/build/py2/test/test_LocaleData.py,
line 176, in testCoverage
print_output(repr(ld.getDelimiter(i)))
ICUError: The requested resource cannot be found, error code: 2
--
Ran 34 tests in 0.714s
FAILED (errors=1)
debian/rules:19: recipe for target 'build-stamp' failed
make: *** [build-stamp] Error 1
dpkg-buildpackage: error: debian/rules build gave error exit status 2
[..]
The full build log is attached or can be viewed here:
https://reproducible.debian.net/logs/unstable/amd64/pyicu_1.9.2-1.build2.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: mardi 11 août 2015, 16:05:50 (UTC+1400)
I: pbuilder-time-stamp: 1439258750
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
I: user script /var/cache/pbuilder/build//2755/tmp/hooks/D01_modify_environment
starting
I: Changing hostname to test build reproducibility
I: user script /var/cache/pbuilder/build//2755/tmp/hooks/D01_modify_environment
finished
- 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 (= 5.0.37.3), python-all-dev (= 2.6.6-3~), python-all-dbg
(= 2.6.6-3~), python3-all-dev, python3-all-dbg, libicu-dev
Conflicts: python-pyicu
dpkg-deb: building package 'pbuilder-satisfydepends-dummy' in
'/tmp/satisfydepends-aptitude/pbuilder-satisfydepends-dummy.deb'.
Selecting previously unselected package pbuilder-satisfydepends-dummy.
(Reading database ... 20247 files and directories currently installed.)
Preparing to unpack .../pbuilder-satisfydepends-dummy.deb ...
Unpacking pbuilder-satisfydepends-dummy (0.invalid.0) ...
dpkg: pbuilder-satisfydepends-dummy: dependency problems, but configuring
anyway as you requested:
pbuilder-satisfydepends-dummy depends on python-all-dev (= 2.6.6-3~); however:
Package python-all-dev is not installed.
pbuilder-satisfydepends-dummy depends on python-all-dbg (= 2.6.6-3~); however:
Package python-all-dbg is not installed.
pbuilder-satisfydepends-dummy depends on python3-all-dev; however:
Package python3-all-dev is not installed.
pbuilder-satisfydepends-dummy depends on python3-all-dbg; however:
Package python3-all-dbg is not installed.
pbuilder-satisfydepends-dummy depends on libicu-dev; however:
Package
Bug#795767: netty-tcnative: FTBFS: missing org.apache.felix:maven-bundle-plugin
Source: netty-tcnative Version: 1.1.33.Fork4-1 Severity: serious Justification: fails to build from source Builds of netty-tcnative in minimal environments geared for covering only its architecture-dependent binary package have been failing: [ERROR] BUILD ERROR [INFO] [INFO] The plugin 'org.apache.felix:maven-bundle-plugin' does not exist or no valid version could be found Could you please take a look? I presume you'll want to move libmaven-bundle-plugin-java from Build-Depends-Indep to Build-Depends; I'm not sure about libmaven-antrun-plugin-java offhand. Thanks!
Processed: tagging 795756
Processing commands for cont...@bugs.debian.org: tags 795756 + confirmed Bug #795756 [src:libsvn-hooks-perl] libsvn-hooks-perl: FTBFS: t/02-generic.t: Failed tests: 11-12 Added tag(s) confirmed. thanks Stopping processing here. Please contact me if you need assistance. -- 795756: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=795756 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#795685: [Debian-med-packaging] Bug#795685: biojava4-live: FTBFS: UnknownHostException: eutils.ncbi.nlm.nih.gov
On 08/16/2015 11:28 AM, Chris West (Faux) wrote: 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 Thanks for the report. I already disabled some network tests, those ones are certainly new remote tests introduced in this release. I gonna patch this soon. -- 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) ___ Debian-med-packaging mailing list debian-med-packag...@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/debian-med-packaging -- gpg key id: 4096R/326D8438 (keyring.debian.org) Key fingerprint = 5FB4 6F83 D3B9 5204 6335 D26D 78DC 68DB 326D 8438
Processed: forcibly merging 791489 783329 783330
Processing commands for cont...@bugs.debian.org: forcemerge 791489 783329 783330 Bug #791489 [reiserfsprogs] /sbin/reiserfsck is not included in initrd image Bug #783329 [reiserfsprogs] reiserfsprogs: reiserfsck cannot be found at boot while / is reiserfs Severity set to 'grave' from 'normal' Added tag(s) d-i, sid, and jessie. Bug #783330 [reiserfsprogs] reiserfsprogs: reiserfsck cannot be found at boot while / is reiserfs Severity set to 'grave' from 'normal' Added tag(s) sid and jessie. Bug #791489 [reiserfsprogs] /sbin/reiserfsck is not included in initrd image Marked as found in versions reiserfsprogs/1:3.6.24-1. Added tag(s) d-i. Merged 783329 783330 791489 thanks Stopping processing here. Please contact me if you need assistance. -- 783329: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=783329 783330: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=783330 791489: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=791489 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#784045: marked as done (debian-installer-launcher needs to depend on sudo)
Your message dated Sun, 16 Aug 2015 15:20:30 + with message-id e1zqzja-0005kv...@franck.debian.org and subject line Bug#784045: fixed in debian-installer-launcher 21+nmu1 has caused the Debian Bug report #784045, regarding debian-installer-launcher needs to depend on sudo to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 784045: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=784045 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: debian-installer-launcher Severity: serious debian-installer-launcher uses su-to-root which is in menu and doesn't automatically pull in sudo. debian-installer-launcher however doesn't work without sudo. -- Address:Daniel Baumann, Donnerbuehlweg 3, CH-3012 Bern Email: daniel.baum...@progress-technologies.net Internet: http://people.progress-technologies.net/~daniel.baumann/ ---End Message--- ---BeginMessage--- Source: debian-installer-launcher Source-Version: 21+nmu1 We believe that the bug you reported is fixed in the latest version of debian-installer-launcher, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 784...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Iain R. Learmonth i...@debian.org (supplier of updated debian-installer-launcher package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Sun, 16 Aug 2015 14:20:28 +0100 Source: debian-installer-launcher Binary: debian-installer-launcher Architecture: source all Version: 21+nmu1 Distribution: unstable Urgency: medium Maintainer: Debian Install System Team debian-b...@lists.debian.org Changed-By: Iain R. Learmonth i...@debian.org Description: debian-installer-launcher - Debian Installer desktop launcher Closes: 784045 Changes: debian-installer-launcher (21+nmu1) unstable; urgency=medium . * Non-maintainer upload. * Add sudo to Depends. (Closes: #784045) Checksums-Sha1: d67d4a2bfd0298fb176615928226d89a41b3d5f5 1822 debian-installer-launcher_21+nmu1.dsc 3196dba92abdd2f758058dce9c41246ba4e65852 43316 debian-installer-launcher_21+nmu1.tar.xz 3604011ddce0914d2f0b53348db80eec1c6f0c54 28072 debian-installer-launcher_21+nmu1_all.deb Checksums-Sha256: 5b6beae8c412fc4a3454163ab181cc06a3e6ac9b61953cc17100b852598951f3 1822 debian-installer-launcher_21+nmu1.dsc 7807d91b155238c5f5ee2a389478c5161d47515ef325e29bf049e8a2a54701c3 43316 debian-installer-launcher_21+nmu1.tar.xz 0dc0591c17d868c927402ec03fd242d088a25c21ca26f355307d4e0f4f445244 28072 debian-installer-launcher_21+nmu1_all.deb Files: df45502441dd7df764e738de34ee5af4 1822 utils optional debian-installer-launcher_21+nmu1.dsc 0b691164575528a45e06f8f0f8585bf6 43316 utils optional debian-installer-launcher_21+nmu1.tar.xz 60eaadca94ebb848c9ec6f50a0ae2e4b 28072 utils optional debian-installer-launcher_21+nmu1_all.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1 iQIcBAEBCgAGBQJV0I5JAAoJEAdZWpwDjyGuhtwP/jn6KynNz+H0aPHXja3mOwTv EiBOQBEN7wizJsoebYz6byHIZHvkENbIFUO/PZzLSTP1iHVfH7vlZOp8TDDvmLu7 NlPs4GXG3k0o8ZGkBml4xzq0Hrgt6dfEpH0fUP1+a1XdoSug/Ox323UwJz3yFZ9f uuWAoD/EMEmmYCuutdLPCQWVfJD4ljZYQqzZBu9/YPcC/tRXypUeuydFXG8dKj2I v71lmyYuRmFmeApVAvZrk3vIy2y/fRhBeQhHv82MtrtFD8IF4GyNoxJw8gg8GH3U L5hrJMyen/+9+1qzZlve3vsXmYtRxRtJGdfwc/pDmTM1cWL1DPni/mjgSSBFiQ9W 7CiKOmPCYH3p9c+RewzJNm5R4I6f1NOju/O5CJOVaonVZyoEgWuVRH0GQZzNItCF mXbhGNS8vOR7THkgnkPG6ZlOtPDFJu13x9/FnpUh32a2RUI/HQkoHfiHACUoMRgg eF0wKzJGjOuZ8aJS5a+suDXZLMrs7jg7ni/kRfVIP2Zocun7Cxm16ormZm7OJa3G wxL4+QiuRRBomwfepubkx1YH8eXEFIDlWni4zXuhRbKoyfSbbesF3hVFncy/H9JV s+9tlSBz4PjRLwF8b0qX6UAfvJvBkIQJXuBkVl8Q9Htw+k19dzddvvOB/y3iiRfd 45dxXHydmHk6Wtte3gOO =q+6+ -END PGP SIGNATUREEnd Message---
Bug#795744: haskell-yaml: FTBFS: can't load .so/.DLL for: [..] libHSaeson-qq-0.7.4-ghc7.8.4.so
Source: haskell-yaml Version: 0.8.12-1 Severity: serious Justification: fails to build from source Tags: sid 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: Loading package haskell-src-meta-0.6.0.10 ... linking ... done. Loading package parsec-3.1.9 ... linking ... done. Loading package aeson-qq-0.7.4 ... command line: can't load .so/.DLL for: /usr/lib/haskell-packages/ghc/lib/x86_64-linux-ghc-7.8.4/aeson-qq-0.7.4/libHSaeson-qq-0.7.4-ghc7.8.4.so (libHScpphs-1.19-ghc7.8.4.so: cannot open shared object file: No such file or directory) /usr/share/cdbs/1/class/hlibrary.mk:146: recipe for target 'build-ghc-stamp' failed make: *** [build-ghc-stamp] Error 1 dpkg-buildpackage: error: debian/rules build gave error exit status 2 Full build log: https://reproducible.debian.net/rb-pkg/unstable/amd64/haskell-yaml.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#795685: marked as done (biojava4-live: FTBFS: UnknownHostException: eutils.ncbi.nlm.nih.gov)
Your message dated Sun, 16 Aug 2015 15:19:57 + with message-id e1zqzj3-0005ct...@franck.debian.org and subject line Bug#795685: fixed in biojava4-live 4.1.0+dfsg-2 has caused the Debian Bug report #795685, regarding biojava4-live: FTBFS: UnknownHostException: eutils.ncbi.nlm.nih.gov to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 795685: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=795685 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- 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) ---End Message--- ---BeginMessage--- Source: biojava4-live Source-Version: 4.1.0+dfsg-2 We believe that the bug you reported is fixed in the latest version of biojava4-live, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 795...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Olivier Sallou osal...@debian.org (supplier of updated biojava4-live package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Sun, 16 Aug 2015 16:33:47 +0200 Source: biojava4-live Binary: libbiojava4.0-java libbiojava4-java libbiojava4-java-doc Architecture: source all Version: 4.1.0+dfsg-2 Distribution: unstable Urgency: medium Maintainer: Debian Med Packaging Team debian-med-packag...@lists.alioth.debian.org Changed-By: Olivier Sallou osal...@debian.org Description: libbiojava4-java - Java API to biological data and applications (default version) libbiojava4-java-doc - [Biology] Documentation for BioJava libbiojava4.0-java -
Bug#795752: ruby-http: FTBFS: undefined method `its' for RSpec::ExampleGroups::HTTPContentType::Parse::WithTextPlain:Class (NoMethodError)
Source: ruby-http Version: 0.6.1-1 Severity: serious Justification: fails to build from source User: reproducible-bui...@lists.alioth.debian.org Usertags: ftbfs X-Debbugs-Cc: reproducible-bui...@lists.alioth.debian.org Dear Maintainer, ruby-http fails to build from source on unstable/amd64: [..] [2015-07-17 07:37:49] INFO WEBrick::HTTPProxyServer#start: pid=11508 port=8080 [2015-07-17 07:37:49] INFO WEBrick::HTTPProxyServer#start: pid=11508 port=8081 [2015-07-17 07:37:49] INFO going to shutdown ... [2015-07-17 07:37:49] INFO WEBrick::HTTPProxyServer#start done. [2015-07-17 07:37:49] INFO going to shutdown ... [2015-07-17 07:37:49] INFO WEBrick::HTTPServer#start done. [2015-07-17 07:37:49] INFO going to shutdown ... [2015-07-17 07:37:49] INFO WEBrick::HTTPProxyServer#start done. /usr/lib/ruby/vendor_ruby/rspec/core/example_group.rb:656:in `method_missing': undefined method `its' for RSpec::ExampleGroups::HTTPContentType::Parse::WithTextPlain:Class (NoMethodError) from /tmp/buildd/ruby-http-0.6.1/spec/http/content_type_spec.rb:7:in `block (3 levels) in top (required)' from /usr/lib/ruby/vendor_ruby/rspec/core/example_group.rb:363:in `module_exec' from /usr/lib/ruby/vendor_ruby/rspec/core/example_group.rb:363:in `subclass' from /usr/lib/ruby/vendor_ruby/rspec/core/example_group.rb:254:in `block in define_example_group_method' from /tmp/buildd/ruby-http-0.6.1/spec/http/content_type_spec.rb:5:in `block (2 levels) in top (required)' from /usr/lib/ruby/vendor_ruby/rspec/core/example_group.rb:363:in `module_exec' from /usr/lib/ruby/vendor_ruby/rspec/core/example_group.rb:363:in `subclass' from /usr/lib/ruby/vendor_ruby/rspec/core/example_group.rb:254:in `block in define_example_group_method' from /tmp/buildd/ruby-http-0.6.1/spec/http/content_type_spec.rb:4:in `block in top (required)' from /usr/lib/ruby/vendor_ruby/rspec/core/example_group.rb:363:in `module_exec' from /usr/lib/ruby/vendor_ruby/rspec/core/example_group.rb:363:in `subclass' from /usr/lib/ruby/vendor_ruby/rspec/core/example_group.rb:254:in `block in define_example_group_method' from /usr/lib/ruby/vendor_ruby/rspec/core/dsl.rb:43:in `block in expose_example_group_alias' from /usr/lib/ruby/vendor_ruby/rspec/core/dsl.rb:82:in `block (2 levels) in expose_example_group_alias_globally' from /tmp/buildd/ruby-http-0.6.1/spec/http/content_type_spec.rb:3:in `top (required)' from /usr/lib/ruby/vendor_ruby/rspec/core/configuration.rb:1327:in `load' from /usr/lib/ruby/vendor_ruby/rspec/core/configuration.rb:1327:in `block in load_spec_files' from /usr/lib/ruby/vendor_ruby/rspec/core/configuration.rb:1325:in `each' from /usr/lib/ruby/vendor_ruby/rspec/core/configuration.rb:1325:in `load_spec_files' from /usr/lib/ruby/vendor_ruby/rspec/core/runner.rb:103: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-http-0.6.1/debian/ruby-http 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-http_0.6.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 17 07:34:20 GMT+12 2015 I: pbuilder-time-stamp: 1437161660 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
