Bug#791869: lvm2: updating src:lvm2 from 2.02.111-2.2 to 2.02.122-1 breaks booting, mounting LVs other than / fails
Hi
On 2015-08-01, Stefan Lippers-Hollmann wrote:
On 2015-07-31, Michael Biebl wrote:
[...]
Bastian built the lvm2 on amd64 on a non-systemd system, it seems. This
results in /lib/udev/rules.d/69-lvm-metad.rules lookin like this:
...
ENV{SYSTEMD_READY}=1
RUN+=/sbin/lvm pvscan --background --cache --activate ay --major $major
--minor $minor, ENV{LVM_SCANNED}=1
...
If you build lvm2 on a systemd system, those rules look like
...
ENV{SYSTEMD_READY}=1
ACTION!=remove, ENV{LVM_PV_GONE}==1, RUN+=/bin/systemd-run
/sbin/lvm pvscan --cache $major:$minor, GOTO=lvm_end
ENV{SYSTEMD_ALIAS}=/dev/block/$major:$minor
ENV{ID_MODEL}=LVM PV $env{ID_FS_UUID_ENC} on /dev/$name
ENV{SYSTEMD_WANTS}=lvm2-pvscan@$major:$minor.service
If I replace /lib/udev/rules.d/69-lvm-metad.rules with the attached
file, my problems with LVM on top of RAID1 are gone. Can you copy the
attached file to /etc/udev/rules.d/ and test if that fixes your problem?
Just an update for the situation with lvm2 2.02.126-2:
- all affected systems are running the amd64 architecture
- all systems are up to date Debian unstable/main
using initramfs-tools 0.120:
- most systems are broken with lvm2 2.02.126-2, to varying degrees.
the problem is apparently timing sensitive, systems using a SSD
for the system paths (with their dedicated volume group) are less
likely to fail booting, but occassionally they still do break.
- doing a local bin-NMU of lvm2 2.02.126-2, in order to update
/lib/udev/rules.d/69-lvm-metad.rules with the changes pointed out
by Michael Biebl helps me on all non-mdadm == lvm2-only systems.
Not a single failed boot on these systems so far.
- lvm2 (2.02.126-2) on top of mdadm (RAID1) fails reliably for me,
regardless of the bin-NMU for 69-lvm-metad.rules or staying on
the plain lvm2 2.02.126-2; I'm aware of #793631 and just mention
it because the update to lvm2 2.02.126-2 doesn't appear to make
a difference.
using dracut 040+1-1:
- all lvm-only systems are booting fine, no local bin-NMU needed.
- the mdadm(RAID1)+lvm2 system is also booting reliably, no local
bin-NMU needed.
- no issues found with the current lvm2 and dracut (but I obviously
don't need any special initramfs hooks/ scripts)
Regards
Stefan Lippers-Hollmann
pgp69W1HNJxku.pgp
Description: Digitale Signatur von OpenPGP
Bug#794440: xsd: Not build due to no codesynthesis/cli package in debian archive
Source: xsd Version: 4.0.0-1 Severity: serious Justification: fails to build from source (but built successfully in the past) Dear maintainer: cli is needed when building this package. But no package contains codesynthesis/cli Thanks -- System Information: Debian Release: stretch/sid APT prefers unstable APT policy: (990, 'unstable'), (500, 'work'), (500, 'testing-updates'), (500, 'testing'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.1.0-trunk-amd64 (SMP w/2 CPU cores) Locale: LANG=zh_CN.UTF-8, LC_CTYPE=zh_CN.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#794320: marked as done (main option prdr_enable unknown)
Your message dated Sun, 02 Aug 2015 06:03:57 + with message-id e1zlmnj-kn...@franck.debian.org and subject line Bug#794320: fixed in exim4 4.86-2 has caused the Debian Bug report #794320, regarding main option prdr_enable unknown 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.) -- 794320: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=794320 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: exim4-config Version: 4.86-1 Severity: serious After updating an old testing system I get this: Setting up exim4-config (4.86-1) ... 2015-08-01 15:04:52 Exim configuration error in line 140 of /var/lib/exim4/config.autogenerated.tmp: main option prdr_enable unknown Invalid new configfile /var/lib/exim4/config.autogenerated.tmp, not installing /var/lib/exim4/config.autogenerated.tmp to /var/lib/exim4/config.autogenerated dpkg: error processing package exim4-config (--configure): subprocess installed post-installation script returned error exit status 1 Errors were encountered while processing: exim4-config prdr_enable is indeed contained in /etc/exim4/conf.d/main/02_exim4-config_options -- Package-specific info: Exim version 4.82_1-5b7a7c0-XX #3 built 22-Jul-2014 16:32:17 Copyright (c) University of Cambridge, 1995 - 2013 (c) The Exim Maintainers and contributors in ACKNOWLEDGMENTS file, 2007 - 2013 Berkeley DB: Berkeley DB 5.3.28: (September 9, 2013) Support for: crypteq iconv() IPv6 GnuTLS move_frozen_messages DKIM Lookups (built-in): lsearch wildlsearch nwildlsearch iplsearch cdb dbm dbmjz dbmnz dnsdb dsearch nis nis0 passwd Authenticators: cram_md5 plaintext Routers: accept dnslookup ipliteral manualroute queryprogram redirect Transports: appendfile/maildir/mailstore autoreply lmtp pipe smtp Fixed never_users: 0 Size of off_t: 8 Configuration file is /var/lib/exim4/config.autogenerated # /etc/exim4/update-exim4.conf.conf # # Edit this file and /etc/mailname by hand and execute update-exim4.conf # yourself or use 'dpkg-reconfigure exim4-config' # # Please note that this is _not_ a dpkg-conffile and that automatic changes # to this file might happen. The code handling this will honor your local # changes, so this is usually fine, but will break local schemes that mess # around with multiple versions of the file. # # update-exim4.conf uses this file to determine variable values to generate # exim configuration macros for the configuration file. # # Most settings found in here do have corresponding questions in the # Debconf configuration, but not all of them. # # This is a Debian specific file dc_eximconfig_configtype='smarthost' dc_other_hostnames='' dc_local_interfaces='127.0.0.1 ; ::1' dc_readhost='' dc_relay_domains='' dc_minimaldns='false' dc_relay_nets='' dc_smarthost='mail.wrar.name' CFILEMODE='644' dc_use_split_config='false' dc_hide_mailname='false' dc_mailname_in_oh='true' dc_localdelivery='mail_spool' mailname:sabine.wrar.name -- System Information: Debian Release: stretch/sid APT prefers testing APT policy: (990, 'testing'), (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.8.0-wrar-sabine-1+ (SMP w/4 CPU cores; PREEMPT) Locale: LANG=ru_RU.UTF-8, LC_CTYPE=ru_RU.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages exim4-config depends on: ii adduser3.113+nmu3 ii debconf [debconf-2.0] 1.5.57 exim4-config recommends no packages. exim4-config suggests no packages. -- Configuration Files: /etc/exim4/passwd.client [Errno 13] Отказано в доступе: u'/etc/exim4/passwd.client' -- debconf information excluded ---End Message--- ---BeginMessage--- Source: exim4 Source-Version: 4.86-2 We believe that the bug you reported is fixed in the latest version of exim4, 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 Metzler ametz...@debian.org (supplier of updated exim4 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, 02 Aug 2015 07:40:24 +0200 Source: exim4 Binary:
Processed: bug 794369 is forwarded to https://github.com/habnabit/txsocksx/issues/9
Processing commands for cont...@bugs.debian.org: forwarded 794369 https://github.com/habnabit/txsocksx/issues/9 Bug #794369 [python-txsocksx] python-txsocksx: broken by twisted 15.x internal API changes Set Bug forwarded-to-address to 'https://github.com/habnabit/txsocksx/issues/9'. thanks Stopping processing here. Please contact me if you need assistance. -- 794369: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=794369 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: devscripts: licensecheck: CVE-2015-5705: argument injection vulnerability
Processing control commands:
retitle 794260 devscripts: licensecheck: CVE-2015-5704: shell injection
vulnerability
Bug #794260 {Done: James McCoy james...@debian.org} [devscripts] devscripts:
licensecheck chokes on files containing space
Changed Bug title to 'devscripts: licensecheck: CVE-2015-5704: shell injection
vulnerability' from 'devscripts: licensecheck chokes on files containing space'
--
794260: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=794260
794365: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=794365
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#794361: marked as done (FTBFS with GCC5)
Your message dated Sun, 2 Aug 2015 09:18:16 +0200 with message-id 20150802071815.gl22...@dorei.kerker.die-welt.net and subject line Re: Bug#794361: FTBFS with GCC5 has caused the Debian Bug report #794361, regarding FTBFS with GCC5 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.) -- 794361: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=794361 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: sysdig Version: 0.1.101-2 Severity: serious Tags: upstream Justification: fails to build from source (but built successfully in the past) While prparing 0.1.102, I noticed that it will not build on current unstable. This also applies to 0.1.101-2 as in the archive. Build log: Linking CXX executable csysdig cd /tmp/buildd/sysdig-0.1.101/obj-x86_64-linux-gnu/userspace/sysdig /usr/bin/cmake -E cmake_link_script CMakeFiles/csysdig.dir/link.txt --verbose=1 /usr/bin/c++ -g -O2 -fstack-protector-strong -Wformat -Werror=format-security -D_FORTIFY_SOURCE=2 -D_FORTIFY_SOURCE=2 -Wall -ggdb --std=c++0x -Wl,-z,relro CMakeFiles/csysdig.dir/fields_info.cpp.o CMakeFiles/csysdig.dir/csysdig.cpp.o -o csysdig -rdynamic ../libsinsp/libsinsp.a -lncurses -lform ../libscap/libscap.a -lz -ljsoncpp -lluajit-5.1 -ldl .../libsinsp/libsinsp.a(container.cpp.o): In function `sinsp_container_manager::parse_docker(sinsp_container_info*)': /tmp/buildd/sysdig-0.1.101/userspace/libsinsp/container.cpp:339: undefined reference to `Json::Reader::parse(std::__cxx11::basic_stringchar, std::char_traitschar, std::allocatorchar const, Json::Value, bool)' /tmp/buildd/sysdig-0.1.101/userspace/libsinsp/container.cpp:346: undefined reference to `Json::Value::asString[abi:cxx11]() const' /tmp/buildd/sysdig-0.1.101/userspace/libsinsp/container.cpp:347: undefined reference to `Json::Value::asString[abi:cxx11]() const' /tmp/buildd/sysdig-0.1.101/userspace/libsinsp/container.cpp:353: undefined reference to `Json::Value::asString[abi:cxx11]() const' /tmp/buildd/sysdig-0.1.101/userspace/libsinsp/container.cpp:360: undefined reference to `Json::Value::getMemberNames[abi:cxx11]() const' /tmp/buildd/sysdig-0.1.101/userspace/libsinsp/container.cpp:371: undefined reference to `Json::Value::operator[](std::__cxx11::basic_stringchar, std::char_traitschar, std::allocatorchar const)' /tmp/buildd/sysdig-0.1.101/userspace/libsinsp/container.cpp:378: undefined reference to `Json::Value::asString[abi:cxx11]() const' /tmp/buildd/sysdig-0.1.101/userspace/libsinsp/container.cpp:379: undefined reference to `Json::Value::asString[abi:cxx11]() const' .../libsinsp/libsinsp.a(event.cpp.o): In function `sinsp_evt::render_fd_json(Json::Value*, long, char const**, sinsp_evt::param_fmt)': /tmp/buildd/sysdig-0.1.101/userspace/libsinsp/event.cpp:584: undefined reference to `Json::Value::Value(std::__cxx11::basic_stringchar, std::char_traitschar, std::allocatorchar const)' /tmp/buildd/sysdig-0.1.101/userspace/libsinsp/event.cpp:595: undefined reference to `Json::Value::Value(std::__cxx11::basic_stringchar, std::char_traitschar, std::allocatorchar const)' .../libsinsp/libsinsp.a(event.cpp.o): In function `sinsp_evt::get_param_as_json(unsigned int, char const**, sinsp_evt::param_fmt)': /tmp/buildd/sysdig-0.1.101/userspace/libsinsp/event.cpp:890: undefined reference to `Json::Value::Value(std::__cxx11::basic_stringchar, std::char_traitschar, std::allocatorchar const)' /tmp/buildd/sysdig-0.1.101/userspace/libsinsp/event.cpp:908: undefined reference to `Json::Value::Value(std::__cxx11::basic_stringchar, std::char_traitschar, std::allocatorchar const)' /tmp/buildd/sysdig-0.1.101/userspace/libsinsp/event.cpp:950: undefined reference to `Json::Value::Value(std::__cxx11::basic_stringchar, std::char_traitschar, std::allocatorchar const)' .../libsinsp/libsinsp.a(event.cpp.o):/tmp/buildd/sysdig-0.1.101/userspace/libsinsp/event.cpp:964: more undefined references to `Json::Value::Value(std::__cxx11::basic_stringchar, std::char_traitschar, std::allocatorchar const)' follow .../libsinsp/libsinsp.a(eventformatter.cpp.o): In function `sinsp_evt_formatter::tostring(sinsp_evt*, std::__cxx11::basic_stringchar, std::char_traitschar, std::allocatorchar *)': /tmp/buildd/sysdig-0.1.101/userspace/libsinsp/eventformatter.cpp:270: undefined reference to `Json::FastWriter::write[abi:cxx11](Json::Value const)' collect2: error: ld returned 1 exit status userspace/sysdig/CMakeFiles/csysdig.dir/build.make:120: recipe for target 'userspace/sysdig/csysdig' failed make[3]: *** [userspace/sysdig/csysdig] Error 1 Regards Evgeni -- System Information:
Bug#794363: torbrowser-launcher: TypeError: _getEndpoint() takes exactly 4 arguments (2 given)
Package: torbrowser-launcher
Version: 0.2.0-1
Severity: serious
Justification: doesn't start
Usertags: crash
torbrowser-launcher crashes on startup for me, it looks like the APIs
for twisted have changed recently when 15.x reached testing:
https://packages.qa.debian.org/t/twisted/news/20150731T163916Z.html
https://packages.qa.debian.org/t/twisted/news/20150725T172059Z.html
https://packages.qa.debian.org/t/twisted/news/20150309T094947Z.html
https://raw.githubusercontent.com/twisted/twisted/releases/release-15.0.0-7335/NEWS
pabs@chianamo ~ $ which-pkg-broke torbrowser-launcher | tail
python-twisted-web Fri Jul 31 12:47:58 2015
python-twisted-loreFri Jul 31 12:48:01 2015
python-twisted-mailFri Jul 31 12:48:05 2015
python-twisted-names Fri Jul 31 12:48:09 2015
python-twisted-newsFri Jul 31 12:48:11 2015
python-twisted-runner Fri Jul 31 12:48:14 2015
python-twisted-words Fri Jul 31 12:48:16 2015
python-twisted-conch Fri Jul 31 12:48:34 2015
python-twisted Fri Jul 31 12:48:36 2015
libsqlite3-0:amd64 Sat Aug 1 12:13:16 2015
pabs@chianamo ~ $ torbrowser-launcher
Tor Browser Launcher
By Micah Lee, licensed under MIT
version 0.2.0
https://github.com/micahflee/torbrowser-launcher
Updating over Tor
Checking for update
Downloading
https://www.torproject.org/projects/torbrowser/RecommendedTBBVersions
Traceback (most recent call last):
File /usr/bin/torbrowser-launcher, line 30, in module
torbrowser_launcher.main()
File /usr/lib/python2.7/dist-packages/torbrowser_launcher/__init__.py, line
69, in main
app = Launcher(common, url_list)
File /usr/lib/python2.7/dist-packages/torbrowser_launcher/launcher.py, line
130, in __init__
self.build_ui()
File /usr/lib/python2.7/dist-packages/torbrowser_launcher/launcher.py, line
284, in build_ui
self.start(None)
File /usr/lib/python2.7/dist-packages/torbrowser_launcher/launcher.py, line
293, in start
self.run_task()
File /usr/lib/python2.7/dist-packages/torbrowser_launcher/launcher.py, line
310, in run_task
self.download('update check', self.common.paths['update_check_url'],
self.common.paths['update_check_file'])
File /usr/lib/python2.7/dist-packages/torbrowser_launcher/launcher.py, line
469, in download
None)
File /usr/lib/python2.7/dist-packages/twisted/web/client.py, line 1926, in
request
deferred = self._agent.request(method, uri, headers, bodyProducer)
File /usr/lib/python2.7/dist-packages/twisted/web/client.py, line 1559, in
request
endpoint = self._getEndpoint(parsedURI)
TypeError: _getEndpoint() takes exactly 4 arguments (2 given)
-- System Information:
Debian Release: stretch/sid
APT prefers testing
APT policy: (900, 'testing'), (860, 'testing-proposed-updates'), (850,
'buildd-testing-proposed-updates'), (800, 'unstable'), (790,
'buildd-unstable'), (700, 'experimental'), (690, 'buildd-experimental')
Architecture: amd64 (x86_64)
Kernel: Linux 4.0.0-2-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_AU.utf8, LC_CTYPE=en_AU.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
Versions of packages torbrowser-launcher depends on:
ii gnupg1.4.19-3
ii python 2.7.9-1
ii python-gtk2 2.24.0-4
ii python-lzma 0.5.3-2+b1
ii python-parsley 1.2-1
ii python-psutil2.1.1-1+b1
ii python-twisted 15.2.1-1
ii python-txsocksx 1.13.0.3-1
ii tor 0.2.6.10-1
ii wmctrl 1.07-7
torbrowser-launcher recommends no packages.
Versions of packages torbrowser-launcher suggests:
pn apparmor none
ii python-pygame 1.9.1release+dfsg-10+b1
-- no debconf information
--
bye,
pabs
https://wiki.debian.org/PaulWise
signature.asc
Description: This is a digitally signed message part
Processed: merge
Processing commands for cont...@bugs.debian.org: forcemerge 793791 794363 Bug #793791 [torbrowser-launcher] torbrowser-launcher: Fail to start TypeError: _getEndpoint() takes exactly 4 arguments (2 given) Bug #794363 [torbrowser-launcher] torbrowser-launcher: TypeError: _getEndpoint() takes exactly 4 arguments (2 given) Bug #794363 [torbrowser-launcher] torbrowser-launcher: TypeError: _getEndpoint() takes exactly 4 arguments (2 given) Merged 793791 794363 thanks Stopping processing here. Please contact me if you need assistance. -- 793791: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=793791 794363: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=794363 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#794359: FTBFS: port tests to rspec 3 for updating to 1.5.2
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
package: ruby-redis-namespce
version: 1.4.1-2
severity: serious
log from pbuilder run with rspec 3, for 1.4.1-2
┌───
───┐
│ Run tests for ruby2.1 from debian/ruby-tests.rake
│
└───
───┘
RUBYLIB=/tmp/buildd/ruby-redis-namespace-1.4.1/debian/ruby-redis-namespa
ce/usr/lib/ruby/vendor_ruby:.
rake2.1 -f debian/ruby-tests.rake
/usr/bin/ruby2.1 /usr/bin/rspec --pattern ./spec/\*\*/\*_spec.rb
...FFF...FFFF...
...
Failures:
1) redis should be able to use a namespace with setbit
Failure/Error: @namespaced.exists('virgin_key').should be_true
expected true to respond to `true?` or perhaps you meant `be
true` or `be_truthy`
# ./spec/redis_spec.rb:119:in `block (2 levels) in top (required)
'
2) redis should be able to use a namespace with mapped_msetnx
Failure/Error: @namespaced.mapped_msetnx('foo'='1000',
'bar'='2000').should be_false
expected false to respond to `false?` or perhaps you meant `be
false` or `be_falsey`
# ./spec/redis_spec.rb:155:in `block (2 levels) in top (required)
'
3) redis should be able to use a namespace with hashes
Failure/Error: @namespaced.hsetnx('foonx','nx',10).should be_true
expected true to respond to `true?` or perhaps you meant `be
true` or `be_truthy`
# ./spec/redis_spec.rb:176:in `block (2 levels) in top (required)
'
4) redis redis 2.6 commands should namespace bitcount FIXED
Expected pending 'awaiting implementaton of command in redis gem'
to fail. No Error was raised.
# ./spec/redis_spec.rb:355
5) redis redis 2.6 commands should namespace bitop FIXED
Expected pending 'awaiting implementaton of command in redis gem'
to fail. No Error was raised.
# ./spec/redis_spec.rb:359
6) redis redis 2.6 commands should namespace dump FIXED
Expected pending 'awaiting implementaton of command in redis gem'
to fail. No Error was raised.
# ./spec/redis_spec.rb:363
7) redis redis 2.6 commands should namespace restore FIXED
Expected pending 'awaiting implementaton of command in redis gem'
to fail. No Error was raised.
# ./spec/redis_spec.rb:410
Deprecation Warnings:
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-redis-namespace-1.4.1/spec/redis_spec.rb:26: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.
1 deprecation warning total
Finished in 1.7 seconds (files took 1.83 seconds to load)
79 examples, 7 failures
Failed examples:
rspec ./spec/redis_spec.rb:117 # redis should be able to use a
namespace with setbit
rspec ./spec/redis_spec.rb:153 # redis should be able to use a
namespace with mapped_msetnx
rspec ./spec/redis_spec.rb:161 # redis should be able to use a
namespace with hashes
rspec ./spec/redis_spec.rb:355 # redis redis 2.6 commands should
namespace bitcount
rspec ./spec/redis_spec.rb:359 # redis redis 2.6 commands should
namespace bitop
rspec ./spec/redis_spec.rb:363 # redis redis 2.6 commands should
namespace dump
rspec ./spec/redis_spec.rb:410 # redis redis 2.6 commands should
namespace restore
/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-redis-namespace-1.4.1/debian/ruby-redis-namespace
returned exit code 1
debian/rules:23: recipe for target 'override_dh_auto_install' failed
make[1]: *** [override_dh_auto_install] Error 1
make[1]: Leaving directory '/tmp/buildd/ruby-redis-namespace-1.4.1'
debian/rules:15: recipe for target 'binary' failed
make: *** [binary] Error 2
log for 1.5.2
┌───
───┐
│ Run tests for ruby2.1 from debian/ruby-tests.rake
│
└───
───┘
RUBYLIB=/home/pravi/forge/debian/git/pkg-ruby-extras/ruby-redis-namespac
e/debian/ruby-redis-namespace/usr/lib/ruby/vendor_ruby:.
rake2.1 -f debian/ruby-tests.rake
/usr/bin/ruby2.1 /usr/bin/rspec --pattern ./spec/\*\*/\*_spec.rb
/usr/lib/ruby/vendor_ruby/rspec/core/example_group.rb:656:in
`method_missing': undefined method `its' for
RSpec::ExampleGroups::RedisNamespace::Deprecated1XBehaviour:Class
(NoMethodError)
from
/home/pravi/forge/debian/git/pkg-ruby-extras/ruby-redis-namespace/spec/d
eprecation_spec.rb:20:in
`block
Bug#794361: FTBFS with GCC5
Package: sysdig Version: 0.1.101-2 Severity: serious Tags: upstream Justification: fails to build from source (but built successfully in the past) While prparing 0.1.102, I noticed that it will not build on current unstable. This also applies to 0.1.101-2 as in the archive. Build log: Linking CXX executable csysdig cd /tmp/buildd/sysdig-0.1.101/obj-x86_64-linux-gnu/userspace/sysdig /usr/bin/cmake -E cmake_link_script CMakeFiles/csysdig.dir/link.txt --verbose=1 /usr/bin/c++ -g -O2 -fstack-protector-strong -Wformat -Werror=format-security -D_FORTIFY_SOURCE=2 -D_FORTIFY_SOURCE=2 -Wall -ggdb --std=c++0x -Wl,-z,relro CMakeFiles/csysdig.dir/fields_info.cpp.o CMakeFiles/csysdig.dir/csysdig.cpp.o -o csysdig -rdynamic ../libsinsp/libsinsp.a -lncurses -lform ../libscap/libscap.a -lz -ljsoncpp -lluajit-5.1 -ldl .../libsinsp/libsinsp.a(container.cpp.o): In function `sinsp_container_manager::parse_docker(sinsp_container_info*)': /tmp/buildd/sysdig-0.1.101/userspace/libsinsp/container.cpp:339: undefined reference to `Json::Reader::parse(std::__cxx11::basic_stringchar, std::char_traitschar, std::allocatorchar const, Json::Value, bool)' /tmp/buildd/sysdig-0.1.101/userspace/libsinsp/container.cpp:346: undefined reference to `Json::Value::asString[abi:cxx11]() const' /tmp/buildd/sysdig-0.1.101/userspace/libsinsp/container.cpp:347: undefined reference to `Json::Value::asString[abi:cxx11]() const' /tmp/buildd/sysdig-0.1.101/userspace/libsinsp/container.cpp:353: undefined reference to `Json::Value::asString[abi:cxx11]() const' /tmp/buildd/sysdig-0.1.101/userspace/libsinsp/container.cpp:360: undefined reference to `Json::Value::getMemberNames[abi:cxx11]() const' /tmp/buildd/sysdig-0.1.101/userspace/libsinsp/container.cpp:371: undefined reference to `Json::Value::operator[](std::__cxx11::basic_stringchar, std::char_traitschar, std::allocatorchar const)' /tmp/buildd/sysdig-0.1.101/userspace/libsinsp/container.cpp:378: undefined reference to `Json::Value::asString[abi:cxx11]() const' /tmp/buildd/sysdig-0.1.101/userspace/libsinsp/container.cpp:379: undefined reference to `Json::Value::asString[abi:cxx11]() const' .../libsinsp/libsinsp.a(event.cpp.o): In function `sinsp_evt::render_fd_json(Json::Value*, long, char const**, sinsp_evt::param_fmt)': /tmp/buildd/sysdig-0.1.101/userspace/libsinsp/event.cpp:584: undefined reference to `Json::Value::Value(std::__cxx11::basic_stringchar, std::char_traitschar, std::allocatorchar const)' /tmp/buildd/sysdig-0.1.101/userspace/libsinsp/event.cpp:595: undefined reference to `Json::Value::Value(std::__cxx11::basic_stringchar, std::char_traitschar, std::allocatorchar const)' .../libsinsp/libsinsp.a(event.cpp.o): In function `sinsp_evt::get_param_as_json(unsigned int, char const**, sinsp_evt::param_fmt)': /tmp/buildd/sysdig-0.1.101/userspace/libsinsp/event.cpp:890: undefined reference to `Json::Value::Value(std::__cxx11::basic_stringchar, std::char_traitschar, std::allocatorchar const)' /tmp/buildd/sysdig-0.1.101/userspace/libsinsp/event.cpp:908: undefined reference to `Json::Value::Value(std::__cxx11::basic_stringchar, std::char_traitschar, std::allocatorchar const)' /tmp/buildd/sysdig-0.1.101/userspace/libsinsp/event.cpp:950: undefined reference to `Json::Value::Value(std::__cxx11::basic_stringchar, std::char_traitschar, std::allocatorchar const)' .../libsinsp/libsinsp.a(event.cpp.o):/tmp/buildd/sysdig-0.1.101/userspace/libsinsp/event.cpp:964: more undefined references to `Json::Value::Value(std::__cxx11::basic_stringchar, std::char_traitschar, std::allocatorchar const)' follow .../libsinsp/libsinsp.a(eventformatter.cpp.o): In function `sinsp_evt_formatter::tostring(sinsp_evt*, std::__cxx11::basic_stringchar, std::char_traitschar, std::allocatorchar *)': /tmp/buildd/sysdig-0.1.101/userspace/libsinsp/eventformatter.cpp:270: undefined reference to `Json::FastWriter::write[abi:cxx11](Json::Value const)' collect2: error: ld returned 1 exit status userspace/sysdig/CMakeFiles/csysdig.dir/build.make:120: recipe for target 'userspace/sysdig/csysdig' failed make[3]: *** [userspace/sysdig/csysdig] Error 1 Regards Evgeni -- System Information: Debian Release: stretch/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'stable'), (500, 'oldstable'), (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 sysdig depends on: ii libc62.19-19 ii libgcc1 1:5.1.1-14 ii libjsoncpp0 0.10.2-4 ii libluajit-5.1-2 2.0.3+dfsg-3 ii libncurses5 5.9+20150516-2 ii libstdc++6 5.1.1-14 ii libtinfo55.9+20150516-2 ii zlib1g 1:1.2.8.dfsg-2+b1 Versions of packages sysdig recommends: ii sysdig-dkms 0.1.101-2 sysdig suggests no packages. -- no debconf information --
Processed: severity of 793791 is serious, forcibly merging 793791 794363
Processing commands for cont...@bugs.debian.org: severity 793791 serious Bug #793791 [torbrowser-launcher] torbrowser-launcher: Fail to start TypeError: _getEndpoint() takes exactly 4 arguments (2 given) Severity set to 'serious' from 'normal' forcemerge 793791 794363 Bug #793791 [torbrowser-launcher] torbrowser-launcher: Fail to start TypeError: _getEndpoint() takes exactly 4 arguments (2 given) Bug #794363 [torbrowser-launcher] torbrowser-launcher: TypeError: _getEndpoint() takes exactly 4 arguments (2 given) Set Bug forwarded-to-address to 'https://github.com/micahflee/torbrowser-launcher/issues/192'. Added tag(s) upstream. Merged 793791 794363 thanks Stopping processing here. Please contact me if you need assistance. -- 793791: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=793791 794363: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=794363 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#794367: python-twisted-web: internal API changes broke 3 packages, please add appropriate breaks
Package: python-twisted-web Version: 15.2.1-1 Severity: serious The recent internal API changes in python-twisted-web in testing (twisted 15.2.1-1) broke torbrowser-launcher (#793791), txsocksx[1], python-scrapy[2]. python-scrapy is fixed in Debian, txsocksx is fixed upstream but not in a release and torbrowser-launcher isn't fixed yet. The release team would like python-twisted-web to have the appropriate Breaks to prevent the new python-twisted-web from being installed with packages broken by this. Probably the appropriate breaks is like this: Breaks: torbrowser-launcher (= 0.2.0-1~), python-scrapy ( 1.0.0-1~), txsocksx ( 1.13.0.4-1~) 1. https://github.com/habnabit/txsocksx/issues/9 2. https://github.com/scrapy/scrapy/issues/1034 -- bye, pabs https://wiki.debian.org/PaulWise signature.asc Description: This is a digitally signed message part
Bug#794369: python-txsocksx: broken by twisted 15.x internal API changes
Package: python-txsocksx Version: 1.13.0.3-1 Severity: serious The twisted internal API recently changed in Debian testing and that breaks python-txsocksx[1]. Please get upstream to release 1.13.0.4 so that can be uploaded to Debian. If you fix it before the next upstream release, please ask the twisted maintainer via #794367 to set the Breaks to the fixed version instead of 1.13.0.4-1~ as I suggested. 1. https://github.com/habnabit/txsocksx/issues/9 -- System Information: Debian Release: stretch/sid APT prefers testing APT policy: (900, 'testing'), (860, 'testing-proposed-updates'), (850, 'buildd-testing-proposed-updates'), (800, 'unstable'), (790, 'buildd-unstable'), (700, 'experimental'), (690, 'buildd-experimental') Architecture: amd64 (x86_64) Kernel: Linux 4.0.0-2-amd64 (SMP w/4 CPU cores) Locale: LANG=en_AU.utf8, LC_CTYPE=en_AU.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages python-txsocksx depends on: ii python 2.7.9-1 ii python-parsley 1.2-1 ii python-twisted 14.0.2-3 python-txsocksx recommends no packages. python-txsocksx suggests no packages. -- no debconf information -- bye, pabs https://wiki.debian.org/PaulWise signature.asc Description: This is a digitally signed message part
Bug#794334: ea-utils: /usr/bin/alc already used by amule-utils-gui
Hi, I just learned that there is a name space conflicts with the new package ea-utils and amule-utils-gui. I know that we are working according to a first comes first served basis and thus ea-utils would be responsible to rename this file. However, I would like to ask you anyway whether there is any chance to deal with this name space conflict from the amule-utils side. Kind regards Andreas. On Sat, Aug 01, 2015 at 05:09:32PM +0200, Andreas Beckmann wrote: Package: ea-utils Version: 1.1.2+dfsg-1 Severity: serious User: trei...@debian.org Usertags: edos-file-overwrite Control: affects -1 + amule-utils-gui 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 ea-utils. Preparing to unpack .../ea-utils_1.1.2+dfsg-1_amd64.deb ... Unpacking ea-utils (1.1.2+dfsg-1) ... dpkg: error processing archive /var/cache/apt/archives/ea-utils_1.1.2+dfsg-1_amd64.deb (--unpack): trying to overwrite '/usr/share/man/man1/alc.1.gz', which is also in package amule-utils-gui 2.3.1+git1a369e47-3 dpkg-deb: error: subprocess paste was killed by signal (Broken pipe) Errors were encountered while processing: /var/cache/apt/archives/ea-utils_1.1.2+dfsg-1_amd64.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/bin/alc usr/share/man/man1/alc.1.gz 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 ___ Debian-med-packaging mailing list debian-med-packag...@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/debian-med-packaging -- http://fam-tille.de -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#793888: ui-gxmlcpp includes autogenerated files that cannot be rebuilt from source
On Sa, 2015-08-01 at 19:46 +0200, Johannes Schauer wrote: Hi, (...) I reported it like that because I was not able to recreate ./configure and aclocal.m4 from source. When I deleted both files and tried to regenerate them, I ran into an error and I also got an error when I tried to rebuild with `dh --with autoreconf`. This made me believe that ./configure and aclocal.m4 can *not* be built from source. so this does not work even _with_ ui-auto installed? Thx, S -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#768032: Can you please publish the workaround?
Hi, I am having this problem too. Can you please publish the steps to resolve under the bug? Thanks, Pete Miller -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#791072: icu: library transition may be needed when GCC 5 is the default
On 2 August 2015 at 14:32, László Böszörményi (GCS) g...@debian.org wrote: Control: tags -1 -help On Sun, Aug 2, 2015 at 1:59 PM, Matthias Klose d...@debian.org wrote: On 08/02/2015 01:44 PM, László Böszörményi (GCS) wrote: Then we can start the icu transition separately. sorry, you don't understand. all the libstdc++ follow-up transitions will depend on each other. I know this. Still it looked smoother if we do the GCC 5 transition and when things are settled then do the ICU one. your patch for icu 52 looks ok, but again, it will break all rdepends now, which could be avoided with icu 55. OK, 55.1 is in the building and last tests. In addition to that: libicu52 | 52.1-11 | sid | any Must be removed from sid, as these are binary incompatible with: libicu52 | 52.1-10 | stretc | any -- Regards, Dimitri. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#794372: FTBFS: undefined reference to Glib::filename_display_basename
Source: gigedit Version: 0.2.0-1 Severity: serious Tags: sid stretch Justification: fails to build from source (but built successfully in the past) User: reproducible-bui...@lists.alioth.debian.org Usertags: ftbfs Dear Maintainer, The package fails to build: .../../src/gigedit/.libs/libgigedit.so: undefined reference to `Glib::filename_display_basename(std::__cxx11::basic_stringchar, std::char_traitschar, std::allocatorchar const)' .../../src/gigedit/.libs/libgigedit.so: undefined reference to `Glib::str_has_suffix(std::__cxx11::basic_stringchar, std::char_traitschar, std::allocatorchar const, std::__cxx11::basic_stringchar, std::char_traitschar, std::allocatorchar const)' .../../src/gigedit/.libs/libgigedit.so: undefined reference to `RIFF::File::File(std::__cxx11::basic_stringchar, std::char_traitschar, std::allocatorchar const)' .../../src/gigedit/.libs/libgigedit.so: undefined reference to `Glib::ustring::operator=(std::__cxx11::basic_stringchar, std::char_traitschar, std::allocatorchar const)' .../../src/gigedit/.libs/libgigedit.so: undefined reference to `Glib::ustring::ustring(std::__cxx11::basic_stringchar, std::char_traitschar, std::allocatorchar const)' .../../src/gigedit/.libs/libgigedit.so: undefined reference to `Gtk::SelectionData::set(std::__cxx11::basic_stringchar, std::char_traitschar, std::allocatorchar const, int, unsigned char const*, int)' .../../src/gigedit/.libs/libgigedit.so: undefined reference to `Glib::build_filename(std::__cxx11::basic_stringchar, std::char_traitschar, std::allocatorchar const, std::__cxx11::basic_stringchar, std::char_traitschar, std::allocatorchar const)' .../../src/gigedit/.libs/libgigedit.so: undefined reference to `Gtk::SelectionData::get_target[abi:cxx11]() const' .../../src/gigedit/.libs/libgigedit.so: undefined reference to `Glib::path_get_dirname(std::__cxx11::basic_stringchar, std::char_traitschar, std::allocatorchar const)' .../../src/gigedit/.libs/libgigedit.so: undefined reference to `Glib::path_get_basename(std::__cxx11::basic_stringchar, std::char_traitschar, std::allocatorchar const)' .../../src/gigedit/.libs/libgigedit.so: undefined reference to `Glib::path_is_absolute(std::__cxx11::basic_stringchar, std::char_traitschar, std::allocatorchar const)' collect2: error: ld returned 1 exit status Makefile:552: recipe for target 'gigedit' failed Full build log: https://reproducible.debian.net/rb-pkg/unstable/amd64/gigedit.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) -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#794376: FTBFS: undefined reference to `boost::program_options::detail::cmdline::cmdline'
Source: fracplanet Version: 0.4.0-3 Severity: serious Tags: sid Justification: fails to build from source (but built successfully in the past) User: reproducible-bui...@lists.alioth.debian.org Usertags: ftbfs Dear Maintainer, The package fails to build: obj/fracplanet.o: In function `boost::program_options::basic_command_line_parserchar::extra_parser(boost::function1std::pairstd::__cxx11::basic_stringchar, std::char_traitschar, std::allocatorchar , std::__cxx11::basic_stringchar, std::char_traitschar, std::allocatorchar , std::__cxx11::basic_stringchar, std::char_traitschar, std::allocatorchar const)': /usr/include/boost/program_options/detail/parsers.hpp:77: undefined reference to `boost::program_options::detail::cmdline::set_additional_parser(boost::function1std::pairstd::__cxx11::basic_stringchar, std::char_traitschar, std::allocatorchar , std::__cxx11::basic_stringchar, std::char_traitschar, std::allocatorchar , std::__cxx11::basic_stringchar, std::char_traitschar, std::allocatorchar const)' obj/fracplanet.o: In function `std::vectorstd::__cxx11::basic_stringchar, std::char_traitschar, std::allocatorchar , std::allocatorstd::__cxx11::basic_stringchar, std::char_traitschar, std::allocatorchar boost::program_options::to_internalstd::__cxx11::basic_stringchar, std::char_traitschar, std::allocatorchar (std::vectorstd::__cxx11::basic_stringchar, std::char_traitschar, std::allocatorchar , std::allocatorstd::__cxx11::basic_stringchar, std::char_traitschar, std::allocatorcharconst)': /usr/include/boost/program_options/detail/convert.hpp:79: undefined reference to `boost::program_options::to_internal(std::__cxx11::basic_stringchar, std::char_traitschar, std::allocatorchar const)' obj/fracplanet.o: In function `boost::program_options::basic_command_line_parserchar::basic_command_line_parser(int, char const* const*)': /usr/include/boost/program_options/detail/parsers.hpp:43: undefined reference to `boost::program_options::detail::cmdline::cmdline(std::vectorstd::__cxx11::basic_stringchar, std::char_traitschar, std::allocatorchar , std::allocatorstd::__cxx11::basic_stringchar, std::char_traitschar, std::allocatorcharconst)' obj/fracplanet.o: In function `main': /tmp/buildd/fracplanet-0.4.0/fracplanet.cpp:47: undefined reference to `boost::program_options::options_description::options_description(std::__cxx11::basic_stringchar, std::char_traitschar, std::allocatorchar const, unsigned int, unsigned int)' obj/parameters_render.o: In function `ParametersRender::options()': /tmp/buildd/fracplanet-0.4.0/parameters_render.cpp:28: undefined reference to `boost::program_options::options_description::options_description(std::__cxx11::basic_stringchar, std::char_traitschar, std::allocatorchar const, unsigned int, unsigned int)' collect2: error: ld returned 1 exit status Makefile:186: recipe for target 'fracplanet' failed Full build log: https://reproducible.debian.net/rb-pkg/unstable/amd64/fracplanet.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) -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#794375: FTBFS: pry/cli.rb: undefined method `new' for Slop:Module (NoMethodError)
Source: cucumber Version: 2.0.0-2 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: /usr/bin/ruby2.1 /usr/bin/rspec --pattern ./spec/\*\*/\*_spec.rb -r json /usr/lib/ruby/vendor_ruby/pry/cli.rb:100:in `top (required)': undefined method `new' for Slop:Module (NoMethodError) 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/pry.rb:150: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/cucumber-2.0.0/spec/spec_helper.rb:9: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/cucumber-2.0.0/spec/cucumber/cli/configuration_spec.rb:1: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 -r json failed ERROR: Test ruby2.1 failed. Exiting. Full build log: https://reproducible.debian.net/rb-pkg/unstable/amd64/cucumber.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) -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#794102: OK
After new upgrades and removing ~/.xsession, session starts and I have window decorations. There are other issues (I cannot put pidgin or kwallet in tray. I lost my hotkeys and cannot add new ones). I think it's due to migration in progress (4.12-4.14). KDE in stretch is broken. But that's another story. I will just wait new versions to be available. Merci, Benoit -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#794298: asciinema: broken, Unable to upload
Hi, asciinema developer here. First, many thanks to Gustavo for packaging asciinema for Debian. I really appreciate that. The reason why 0.9.8 was deprecated is that it’s almost 2 years old release which uses unsafe http (not https) URL for uploading recordings. This version doesn’t save the recording to the filesystem before uploading and as you noticed the recording is lost when then upload fails for any reason. It also doesn’t consult the API about possible deprecations before starting recording. These issues (https, saving to tmp file) has been addressed in 0.9.9 (the latest version is 1.1.1 btw). Versions 0.9.8 also use documented, open format for the recordings. I have just re-enabled support for 0.9.8 on the server side to fix this problem, but I’d like to stop supporting it in the near future (unsafe http connection is the #1 reason). Is there a chance to update this Debian package to the latest upstream version in not so distant future? Marcin Kulik On Fri, 31 Jul 2015 23:04:19 + (UTC) Daniel Shahaf wrote: Package: asciinema Version: 0.9.8-1 Severity: grave Tags: upstream Justification: renders package unusable Dear Maintainer, asciinema cannot upload new recordings: % asciinema -c /bin/true ~ Asciicast recording finished. ~ Do you want to upload it? [Y/n] y ~ Uploading... ~ Upload failed: Your client version is no longer supported. Please upgrade to the latest version. I expected the upload to succeed. Moreover, if the asciinema client is too old to upload, then either that should be reported prior to starting the recorded command, or the recorded session should be saved in a file that the error message names; doing neither causes user effort (the recorded session) to be lost. I'm on jessie/stable, however, Carsten Hey (carsten@d.o) reproduced this in sid. Cheers, Daniel -- System Information: Debian Release: 8.1 APT prefers stable APT policy: (990, 'stable'), (500, 'testing-updates'), (500, 'stable-updates'), (200, 'unstable'), (200, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 3.16.0-4-amd64 (SMP w/2 CPU cores) Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages asciinema depends on: ii python3 3.4.2-2 ii python3-requests 2.4.3-6 pn python3:any asciinema recommends no packages. asciinema suggests no packages. -- debconf-show failed -- Marcin
Bug#741642: mkvmlinuz: How to easily use mkvmlinuz/38 on Jessie?
On 07/22/2015 11:47 AM, intervenant0 gilles charabot wrote: Dear Maintainer, To avoid the consequences of the bug#741642, I want to use mkvmlinuz/38, but it isn't inside Jessie repository and isn't yet inside jessie-backports repository and when I tried to download the patch with : # cd /usr/sbin # wget https://bugs.debian.org/cgi-bin/bugreport.cgi?msg=40;att=1;bug=741642;filename=mkvmlinuz-run-parts-fix.patch I have nothing new inside /usr/sbin to apply patch. If possible can you backports mkvmlinuz/38 to Jessie, so upgrade Wheezy to Jessie be more easier for me and others. Hi Gilles, Watch bug #793556 for progress on inclusion of this bugfix into Jessie.[0] In the meantime you can download mkvmlinuz[1] version 38 and install it on your machine before upgrading to Jessie to secure smooth upgrade. Milan [0] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=793556 [1] http://ftp.fr.debian.org/debian/pool/main/m/mkvmlinuz/mkvmlinuz_38_powerpc.deb signature.asc Description: OpenPGP digital signature
Bug#791072: icu: library transition may be needed when GCC 5 is the default
On 08/02/2015 01:44 PM, László Böszörményi (GCS) wrote: Control: tags -1 help Hi Matthias, On Sun, Aug 2, 2015 at 12:18 AM, László Böszörményi (GCS) g...@debian.org wrote: Pretty please upload the version from experimental to unstable. It would be a bigger transition as the API changed. Needs testing if all packages can be built with the new, 55.1 version. Will do that in the morning. Midnight is passed here. :-| I have building the dependency level 1 [1] and github-backup, hardinfo, haskell-hledger-web and icedove built fine with icu-55.1 . But ledger has build-dependency on libboost-date-time-dev which is transitively marked broken by libstdc++6 . if you want to do test builds for icu 55, then you have to do it in testing now. Thus please check my previously attached patch[2] if it covers everything needed for the gcc-5 transition. Then we can start the icu transition separately. sorry, you don't understand. all the libstdc++ follow-up transitions will depend on each other. your patch for icu 52 looks ok, but again, it will break all rdepends now, which could be avoided with icu 55. I contacted you and Dimitri two weeks ago to prepare for the icu and boost transitions; and my understanding was that you would prepare for icu 55. it's disappointing to see the progress on this. so either way, upload your fixed 52, or 55, but please do it. Matthias -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#791072: icu: library transition may be needed when GCC 5 is the default
Control: tags -1 -help On Sun, Aug 2, 2015 at 1:59 PM, Matthias Klose d...@debian.org wrote: On 08/02/2015 01:44 PM, László Böszörményi (GCS) wrote: Then we can start the icu transition separately. sorry, you don't understand. all the libstdc++ follow-up transitions will depend on each other. I know this. Still it looked smoother if we do the GCC 5 transition and when things are settled then do the ICU one. your patch for icu 52 looks ok, but again, it will break all rdepends now, which could be avoided with icu 55. OK, 55.1 is in the building and last tests. Regards, Laszlo/GCS -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: Re: Bug#791072: icu: library transition may be needed when GCC 5 is the default
Processing control commands: tags -1 -help Bug #791072 [src:icu] icu: library transition may be needed when GCC 5 is the default Removed tag(s) help. -- 791072: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=791072 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#791072: icu: library transition may be needed when GCC 5 is the default
On Sun, Aug 2, 2015 at 4:16 PM, Matthias Klose d...@debian.org wrote: On 08/02/2015 03:32 PM, László Böszörményi (GCS) wrote: OK, 55.1 is in the building and last tests. ok, I uploaded an icu 52 built using g++-4.9 to undo the breakage in unstable. Please let this build and enter the archive, before you upload icu 55. I've uploaded icu/55.1-3 to Sid before your mail. While it's not yet accepted, it's not in the UploadQueue anymore and I can't remove it. I also sent a removal request for 52.1-11 and 52.1-11.1 to ftp-master. OK. Laszlo/GCS -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#794102: marked as done ([kde-full] Windows frames disappears!!!!)
Your message dated Sun, 02 Aug 2015 10:44 -0400 with message-id 2275044.XLMBsbU8jO@kitterma-e6430 and subject line Re: Bug#794102: OK has caused the Debian Bug report #794102, regarding [kde-full] Windows frames disappears 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.) -- 794102: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=794102 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: kde-full Version: 5:84 Severity: critical --- Please enter the report below this line. --- Hi, after the last upgrade session the applications in my KDE Plasma has lost the windows frames. Even if I use alt-tab it is not possible to switch from an application to another one. The only way to get the access to KDE menu' is closing all the applications. I have try to delete rm $HOME/.kde* -Rf without resolving the problem. I have updated the system setting application (icon) because the previous was not executable. KDE openbox works fine with my previous settings. Please write me if you think I can provide you informations. Thanks for your work Marco Righi --- System information. --- Architecture: amd64 Kernel: Linux 4.0.0-2-amd64 Debian Release: stretch/sid 500 testing-updates ftp.it.debian.org 500 testing www.deb-multimedia.org 500 testing security.debian.org 500 testing ftp.it.debian.org 500 testing apt.jenslody.de 500 stable-updates ftp.it.debian.org 500 stable security.debian.org 500 stable repo.wuala.com 500 stable ftp.it.debian.org 500 stable dl.google.com 500 stable apt.spideroak.com 500 sid linux.dropbox.com 500 debian packages.linuxmint.com --- Package information. --- Package's Depends field is empty. Package's Recommends field is empty. Package's Suggests field is empty. ---End Message--- ---BeginMessage--- On Sunday, August 02, 2015 12:16:11 PM Benoit Friry wrote: After new upgrades and removing ~/.xsession, session starts and I have window decorations. There are other issues (I cannot put pidgin or kwallet in tray. I lost my hotkeys and cannot add new ones). I think it's due to migration in progress (4.12-4.14). KDE in stretch is broken. But that's another story. I will just wait new versions to be available. Thanks. Closing the bug then. Scott K---End Message---
Bug#792070: marked as done (FTBFS: Writer tests give: Segmentation fault)
Your message dated Sun, 02 Aug 2015 12:19:21 + with message-id e1zlseb-s8...@franck.debian.org and subject line Bug#792070: fixed in rapidjson 0.12~git20141031-2 has caused the Debian Bug report #792070, regarding FTBFS: Writer tests give: Segmentation fault 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.) -- 792070: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=792070 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Source: rapidjson Version: 0.12~git20141031-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: [--] 20 tests from Writer [ RUN ] Writer.Compact [ OK ] Writer.Compact (0 ms) [ RUN ] Writer.Root [ OK ] Writer.Root (0 ms) [ RUN ] Writer.Int Segmentation fault debian/rules:41: recipe for target 'override_dh_auto_test' failed make[1]: *** [override_dh_auto_test] Error 139 make[1]: Leaving directory '/tmp/buildd/rapidjson-0.12~git20141031' I managed to rebuild the tests in the debug configuration, and they pass fine. I didn't manage to rebuild the whole package in release mode with debug information, so I can't give you a useful backtrace. It happens on both builders I care about. Here are the full build logs from one of them: https://reproducible.debian.net/rb-pkg/unstable/amd64/rapidjson.html -- System Information: Debian Release: stretch/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 3.19.0-22-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: rapidjson Source-Version: 0.12~git20141031-2 We believe that the bug you reported is fixed in the latest version of rapidjson, 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 792...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Rene Engelhard r...@debian.org (supplier of updated rapidjson 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, 02 Aug 2015 11:45:01 + Source: rapidjson Binary: rapidjson-dev rapidjson-doc Architecture: source all Version: 0.12~git20141031-2 Distribution: unstable Urgency: medium Maintainer: Rene Engelhard r...@debian.org Changed-By: Rene Engelhard r...@debian.org Description: rapidjson-dev - fast JSON parser/generator for C++ with SAX/DOM style API rapidjson-doc - fast JSON parser/generator for C++ (API documentation) Closes: 792070 Changes: rapidjson (0.12~git20141031-2) unstable; urgency=medium . * build-depend on g++-5 to work around segfault in the tests (closes: #792070) Checksums-Sha1: 0f08af009b9164e717e11fb6ad8aa9a4cb30edf9 1889 rapidjson_0.12~git20141031-2.dsc c9ce8d9fd36386abf3c0a0c7814f88f122f3db37 4688 rapidjson_0.12~git20141031-2.debian.tar.xz f896f38cad89535d475ed6975237c23a2c07906e 54576 rapidjson-dev_0.12~git20141031-2_all.deb e8863e84f27b7e83bcc72f745348d6e4fc94873e 484406 rapidjson-doc_0.12~git20141031-2_all.deb Checksums-Sha256: 178efb144bf538469e2871b2be037ba6892f3a456dc32c4844e700af4ec6a480 1889 rapidjson_0.12~git20141031-2.dsc e5d2b6b435c786cd26ef44902aafc8380bc0266c73838e6e7f1b5b6fe79235b0 4688 rapidjson_0.12~git20141031-2.debian.tar.xz a51fd1c810d9a4d0ab1b5641a4c81652d3ceb6cbd0db65e99e2273de403ead86 54576 rapidjson-dev_0.12~git20141031-2_all.deb 373302fee3edac532aad9784af1e91d14540c923e546a4a4027dd6b350a4920a 484406 rapidjson-doc_0.12~git20141031-2_all.deb Files: 6aa00b5a763f914a22455ae11d809470 1889 libs optional rapidjson_0.12~git20141031-2.dsc 80daf9cec57c0feaa6a568dc3b85a9af 4688 libs optional rapidjson_0.12~git20141031-2.debian.tar.xz 092f3a29f0748fa6dc279848923eff6c 54576 libdevel optional rapidjson-dev_0.12~git20141031-2_all.deb 0460572dbce03689250b12c6be12c7a4 484406 doc optional rapidjson-doc_0.12~git20141031-2_all.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1 iQIcBAEBAgAGBQJVvgePAAoJEAqgRXHQPj5wi7QQAKejyo+SH/CL05IH5b6eKVsV
Bug#777862: gbsplay: diff for NMU version 0.0.91-1.1
On Sat, Aug 01, 2015 at 10:40:53PM +0200, Sebastian Ramacher wrote: It looks like gbsplay 0.0.92-1 was never uploaded to the archive. Could you please merge 0.9.92-2 into the changelog entry for 0.9.92-1? I got an upload error on my first try (signed with the wrong GPG key) and I was not able to overwrite my upload with a fixed package, so I created the -2 version. I've merged -2 into -1 and here are the files: http://www.cgarbs.de/tmp/gbsplay_0.0.92-1.diff.gz http://www.cgarbs.de/tmp/gbsplay_0.0.92-1.dsc http://www.cgarbs.de/tmp/gbsplay_0.0.92-1_i386.build http://www.cgarbs.de/tmp/gbsplay_0.0.92-1_i386.changes http://www.cgarbs.de/tmp/gbsplay_0.0.92-1_i386.deb http://www.cgarbs.de/tmp/gbsplay_0.0.92-1_source.changes http://www.cgarbs.de/tmp/gbsplay_0.0.92.orig.tar.gz lintian also reports W: gbsplay: copyright-refers-to-versionless-license-file usr/share/common-licenses/GPL That's a problem. Upstream does not say _which_ GPL version in the README: | gbsplay - A Gameboy sound player | | (C) 2003-2006,2008 by Tobias Diedrich ranma+gbsp...@tdiedrich.de | Christian Garbs mi...@cgarbs.de | Maximilian Rehkopf ota...@gmx.net | Vegard Nossum vegar...@ifi.uio.no | | Licensed under GNU GPL. So I don't know what to do :-/ lintian also reports W: gbsplay hardening-no-relro but I don't know how to fix that. I've already temporarily removed all CFLAGS and LDFLAGS settings from debian/rules so that the build system can automatically set default values for hardening, but that did not work. And regarding X: gbsplay: binary-file-built-without-LFS-support gbsplay is an 8bit hardware emulator. If anybody handles large files with it, he's doing something very wrong :-) (it's only an experimental lintian warning anyways) Regards, Christian -- Christian.Garbs.http://www.cgarbs.de Code, der zum Verständnis Dokumentation braucht, ist meistens Käse. Na ja, sowas kann man wenigstens noch essen. In Verbindung mit Spaghetti-Code ist das doch was Feines. Wirklich unschön wäre Maschinenkot. [Wilfried Krueger in dcsn] signature.asc Description: Digital signature
Bug#791072: icu: library transition may be needed when GCC 5 is the default
On 08/02/2015 03:32 PM, László Böszörményi (GCS) wrote: Control: tags -1 -help On Sun, Aug 2, 2015 at 1:59 PM, Matthias Klose d...@debian.org wrote: On 08/02/2015 01:44 PM, László Böszörményi (GCS) wrote: Then we can start the icu transition separately. sorry, you don't understand. all the libstdc++ follow-up transitions will depend on each other. I know this. Still it looked smoother if we do the GCC 5 transition and when things are settled then do the ICU one. your patch for icu 52 looks ok, but again, it will break all rdepends now, which could be avoided with icu 55. OK, 55.1 is in the building and last tests. ok, I uploaded an icu 52 built using g++-4.9 to undo the breakage in unstable. Please let this build and enter the archive, before you upload icu 55. I also sent a removal request for 52.1-11 and 52.1-11.1 to ftp-master. Matthias -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#793594: marked as done (kannel: fails to install: chown: cannot access '/var/run/kannel': No such file or directory)
Your message dated Sun, 02 Aug 2015 09:35:24 + with message-id e1zlpfw-0005x4...@franck.debian.org and subject line Bug#793594: fixed in kannel 1.4.3-4 has caused the Debian Bug report #793594, regarding kannel: fails to install: chown: cannot access '/var/run/kannel': No such file or directory 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.) -- 793594: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=793594 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: kannel Version: 1.4.3-3 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed your package failed to install. As per definition of the release team this makes the package too buggy for a release, thus the severity. From the attached log (scroll to the bottom...): Selecting previously unselected package kannel. (Reading database ... (Reading database ... 9966 files and directories currently installed.) Preparing to unpack .../kannel_1.4.3-3_i386.deb ... Unpacking kannel (1.4.3-3) ... Processing triggers for systemd (222-2) ... Setting up kannel (1.4.3-3) ... Warning: The home dir /usr/lib/kannel you specified can't be accessed: No such file or directory Adding system user `kannel' (UID 150) ... Adding new user `kannel' (UID 150) with group `nogroup' ... Not creating home directory `/usr/lib/kannel'. changed ownership of '/var/log/kannel' from root:root to kannel:root chown: cannot access '/var/run/kannel': No such file or directory dpkg: error processing package kannel (--configure): subprocess installed post-installation script returned error exit status 1 Processing triggers for systemd (222-2) ... Errors were encountered while processing: kannel cheers, Andreas kannel_1.4.3-3.log.gz Description: application/gzip ---End Message--- ---BeginMessage--- Source: kannel Source-Version: 1.4.3-4 We believe that the bug you reported is fixed in the latest version of kannel, 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. Jonas Smedegaard d...@jones.dk (supplier of updated kannel 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, 02 Aug 2015 09:16:46 +0200 Source: kannel Binary: kannel kannel-extras kannel-docs kannel-dev Architecture: source amd64 all Version: 1.4.3-4 Distribution: unstable Urgency: medium Maintainer: Debian Kannel maintainers pkg-kannel-de...@lists.alioth.debian.org Changed-By: Jonas Smedegaard d...@jones.dk Description: kannel - WAP and SMS gateway kannel-dev - WAP and SMS gateway headers and development files kannel-docs - WAP and SMS gateway documentation kannel-extras - WAP and SMS gateway extras Closes: 793594 Changes: kannel (1.4.3-4) unstable; urgency=medium . * Fix postrm script to not fail if package dirs were already gone. * Drop broken pid file juggling in postinst script (handled in init script). Closes: Bug#793594. Thanks to Andreas Beckmann. * Enable support for Redis and FreeTDS. Build-depend on libhiredis-dev freetds-dev. * Drop patch 32: Alpha no longer a supported architecture. * Bump debhelper compatibility level to 9. * Fix lintian overrides. * Override lintian regarding build-depending unversioned on debhelper. Checksums-Sha1: 3f85d509946001190c1b2672eacda15d2fe4fa08 2379 kannel_1.4.3-4.dsc 32df45fa14f6aa841c79cc729d43c7ec5d7c377b 11536 kannel_1.4.3-4.debian.tar.xz 36be37058431a515a5bbbae605b63c41bb5b39b8 664452 kannel-dev_1.4.3-4_amd64.deb cd17d5e2f23cf966f44c25047d527ef650ddaf93 4024822 kannel-docs_1.4.3-4_all.deb c261db28a4667acced725c4bf791ffeec467b496 1424786 kannel-extras_1.4.3-4_amd64.deb 3465ba1192467b8bc5928aed7ab3b707414dba0c 679478 kannel_1.4.3-4_amd64.deb Checksums-Sha256: 83a91a9664a7efe95d4b9b8dc601888915d5cf7d05d04ae8351d0aa23198d2d4 2379 kannel_1.4.3-4.dsc 59ed21f95b04ac5612962958d5b771798e945168f0e640929ebf6447f95108b6 11536 kannel_1.4.3-4.debian.tar.xz 0ec37f979b30e8190b6b9c9834e3135b6c38d548019028d1bd5acd7d95f9d143 664452 kannel-dev_1.4.3-4_amd64.deb
Bug#794374: FTBFS: undefined reference to `Exiv2::Metadatum::print[abi:cxx11](Exiv2::ExifData const*) const'
Source: geeqie Version: 1:1.2-3 Severity: serious Tags: sid stretch Justification: fails to build from source (but built successfully in the past) User: reproducible-bui...@lists.alioth.debian.org Usertags: ftbfs Dear Maintainer, The package fails to build: exiv2.o: In function `exif_add_value_to_glist': /tmp/buildd/geeqie-1.2/src/exiv2.cc:985: undefined reference to `Exiv2::Metadatum::print[abi:cxx11](Exiv2::ExifData const*) const' exiv2.o: In function `exif_item_get_data_as_text': /tmp/buildd/geeqie-1.2/src/exiv2.cc:752: undefined reference to `Exiv2::Metadatum::print[abi:cxx11](Exiv2::ExifData const*) const' exiv2.o: In function `_ExifDataOriginal::_ExifDataOriginal(char*)': /tmp/buildd/geeqie-1.2/src/exiv2.cc:188: undefined reference to `Exiv2::ImageFactory::open(std::__cxx11::basic_stringchar, std::char_traitschar, std::allocatorchar const)' /tmp/buildd/geeqie-1.2/src/exiv2.cc:188: undefined reference to `Exiv2::ImageFactory::open(std::__cxx11::basic_stringchar, std::char_traitschar, std::allocatorchar const)' exiv2.o: In function `exif_get_item': /tmp/buildd/geeqie-1.2/src/exiv2.cc:486: undefined reference to `Exiv2::ExifKey::ExifKey(std::__cxx11::basic_stringchar, std::char_traitschar, std::allocatorchar const)' /tmp/buildd/geeqie-1.2/src/exiv2.cc:493: undefined reference to `Exiv2::IptcKey::IptcKey(std::__cxx11::basic_stringchar, std::char_traitschar, std::allocatorchar const)' /tmp/buildd/geeqie-1.2/src/exiv2.cc:500: undefined reference to `Exiv2::XmpKey::XmpKey(std::__cxx11::basic_stringchar, std::char_traitschar, std::allocatorchar const)' Full build log: https://reproducible.debian.net/rb-pkg/unstable/amd64/geeqie.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) -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#794372: Oh, the transition!
I have been reminded that there's a nasty C++ transition going on, so these might be transient (i.e. fixed when the upstream libraries are done transitioning). Feel free to close as invalid, drop priority, or whatever! -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#791072: icu: library transition may be needed when GCC 5 is the default
On 2 August 2015 at 12:59, Matthias Klose d...@debian.org wrote: On 08/02/2015 01:44 PM, László Böszörményi (GCS) wrote: Control: tags -1 help Hi Matthias, On Sun, Aug 2, 2015 at 12:18 AM, László Böszörményi (GCS) g...@debian.org wrote: Pretty please upload the version from experimental to unstable. It would be a bigger transition as the API changed. Needs testing if all packages can be built with the new, 55.1 version. Will do that in the morning. Midnight is passed here. :-| I have building the dependency level 1 [1] and github-backup, hardinfo, haskell-hledger-web and icedove built fine with icu-55.1 . But ledger has build-dependency on libboost-date-time-dev which is transitively marked broken by libstdc++6 . if you want to do test builds for icu 55, then you have to do it in testing now. Thus please check my previously attached patch[2] if it covers everything needed for the gcc-5 transition. Then we can start the icu transition separately. sorry, you don't understand. all the libstdc++ follow-up transitions will depend on each other. your patch for icu 52 looks ok, but again, it will break all rdepends now, which could be avoided with icu 55. I contacted you and Dimitri two weeks ago to prepare for the icu and boost transitions; and my understanding was that you would prepare for icu 55. it's disappointing to see the progress on this. so either way, upload your fixed 52, or 55, but please do it. This is urgent, as everything linked against icu is now broken in unstable. One shouldn't not break abi, without a bump of package name / libraries. The consensus was to have 55 with new libstdc, and continue to have 52 with old libstdc. -- Regards, Dimitri. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: severity of 794374 is normal
Processing commands for cont...@bugs.debian.org: severity 794374 normal Bug #794374 [src:geeqie] FTBFS: undefined reference to `Exiv2::Metadatum::print[abi:cxx11](Exiv2::ExifData const*) const' Severity set to 'normal' from 'serious' thanks Stopping processing here. Please contact me if you need assistance. -- 794374: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=794374 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#771870: marked as done (bareos-database-common: fails to install: bareos-database-common.config: /usr/sbin/bareos-dbcheck: not found)
Your message dated Sun, 02 Aug 2015 18:19:19 + with message-id e1zlxqx-yo...@franck.debian.org and subject line Bug#771870: fixed in bareos 14.2.5-1 has caused the Debian Bug report #771870, regarding bareos-database-common: fails to install: bareos-database-common.config: /usr/sbin/bareos-dbcheck: not found to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 771870: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=771870 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: bareos-database-common Version: 14.2.1+20141017gitc6c5b56-4 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed your package failed to install. As per definition of the release team this makes the package too buggy for a release, thus the severity. From the attached log (scroll to the bottom...): Selecting previously unselected package bareos-database-common. (Reading database ... 9220 files and directories currently installed.) Preparing to unpack .../bareos-database-common_14.2.1+20141017gitc6c5b56-4_amd64.deb ... Unpacking bareos-database-common (14.2.1+20141017gitc6c5b56-4) ... Setting up bareos-database-common (14.2.1+20141017gitc6c5b56-4) ... /var/lib/dpkg/info/bareos-database-common.config: 1: /var/lib/dpkg/info/bareos-database-common.config: /usr/sbin/bareos-dbcheck: not found Warning: failed to get dbname from config, using default value bareos, see /tmp/bareos-config.11958.log /var/lib/dpkg/info/bareos-database-common.config: 1: /var/lib/dpkg/info/bareos-database-common.config: /usr/sbin/bareos-dbcheck: not found Warning: failed to get dbuser from config, using default value bareos, see /tmp/bareos-config.11958.log (config) dbc_go() bareos-database-common configure. dbc_config() bareos-database-common configure. dbc_set_dbtype_defaults() . dbc_register_debconf() . dbc_read_package_config() . dbc_preseed_package_debconf() . dbc_get_admin_pass() . dpkg: error processing package bareos-database-common (--configure): subprocess installed post-installation script returned error exit status 10 Errors were encountered while processing: bareos-database-common (Recommends are not installed, DEBIAN_FRONTEND=noninteractive) cheers, Andreas bareos-database-common_14.2.1+20141017gitc6c5b56-4.log.gz Description: application/gzip ---End Message--- ---BeginMessage--- Source: bareos Source-Version: 14.2.5-1 We believe that the bug you reported is fixed in the latest version of bareos, 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 771...@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 bareos 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, 02 Aug 2015 19:46:11 +0200 Source: bareos Binary: bareos bareos-bconsole bareos-client bareos-common bareos-database-common bareos-database-postgresql bareos-database-mysql bareos-database-sqlite3 bareos-database-tools bareos-dbg bareos-devel bareos-director bareos-filedaemon bareos-storage bareos-storage-fifo bareos-storage-tape bareos-tools bareos-bat bareos-director-python-plugin bareos-filedaemon-python-plugin bareos-storage-python-plugin bareos-traymonitor Architecture: source amd64 Version: 14.2.5-1 Distribution: unstable Urgency: medium Maintainer: Bareos Packaging Team pkg-bareos-de...@lists.alioth.debian.org Changed-By: Evgeni Golov evg...@debian.org Description: bareos - Backup Archiving Recovery Open Sourced - metapackage bareos-bat - Backup Archiving Recovery Open Sourced - Bareos Admin Tool (BAT) bareos-bconsole - Backup Archiving Recovery Open Sourced - text console bareos-client - Backup Archiving Recovery Open Sourced - client metapackage bareos-common - Backup Archiving Recovery Open Sourced - common files bareos-database-common - Backup Archiving Recovery Open Sourced - common catalog files bareos-database-mysql - Backup Archiving Recovery Open Sourced - MySQL backend bareos-database-postgresql - Backup Archiving Recovery Open Sourced - PostgreSQL backend
Bug#788543: marked as done (bareos-sd will silently corrupt backups when using multi-volume disk-based jobs)
Your message dated Sun, 02 Aug 2015 18:19:19 + with message-id e1zlxqx-ya...@franck.debian.org and subject line Bug#788543: fixed in bareos 14.2.5-1 has caused the Debian Bug report #788543, regarding bareos-sd will silently corrupt backups when using multi-volume disk-based jobs 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.) -- 788543: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=788543 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: bareos Version: 14.2.1+20141017gitc6c5b56-4 Severity: critical Justification: causes serious data loss In March 2015 bareos fixed a bug which caused silent corruption of backups when the following conditions are met: * backups are written to disk (tape backups are not affected) * autolabelling is enabled * a backup spans over multiple volumes * the additional volumes are newly created and labeled during the backup. Bug: https://bugs.bareos.org/view.php?id=437 Announcement: http://www.bareos.com/en/company_news/items/Bareos-14.2.4-published.html Fix for 14.2: https://github.com/bareos/bareos/commit/263240eaa911563a8468ecdaf7d4957201b41426 Given that the above conditions are met in most bareos installations I've tagged this as critical. While I'm at it I'd like to point out that Joerg Steffens, an upstream maintainer, employee and/or partner of bareos.com and co-maintainer of this package in Debian, hasn't found the time to inform the Debian community of this issue, lest providing a patched package. best, Michael ---End Message--- ---BeginMessage--- Source: bareos Source-Version: 14.2.5-1 We believe that the bug you reported is fixed in the latest version of bareos, 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. Evgeni Golov evg...@debian.org (supplier of updated bareos 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, 02 Aug 2015 19:46:11 +0200 Source: bareos Binary: bareos bareos-bconsole bareos-client bareos-common bareos-database-common bareos-database-postgresql bareos-database-mysql bareos-database-sqlite3 bareos-database-tools bareos-dbg bareos-devel bareos-director bareos-filedaemon bareos-storage bareos-storage-fifo bareos-storage-tape bareos-tools bareos-bat bareos-director-python-plugin bareos-filedaemon-python-plugin bareos-storage-python-plugin bareos-traymonitor Architecture: source amd64 Version: 14.2.5-1 Distribution: unstable Urgency: medium Maintainer: Bareos Packaging Team pkg-bareos-de...@lists.alioth.debian.org Changed-By: Evgeni Golov evg...@debian.org Description: bareos - Backup Archiving Recovery Open Sourced - metapackage bareos-bat - Backup Archiving Recovery Open Sourced - Bareos Admin Tool (BAT) bareos-bconsole - Backup Archiving Recovery Open Sourced - text console bareos-client - Backup Archiving Recovery Open Sourced - client metapackage bareos-common - Backup Archiving Recovery Open Sourced - common files bareos-database-common - Backup Archiving Recovery Open Sourced - common catalog files bareos-database-mysql - Backup Archiving Recovery Open Sourced - MySQL backend bareos-database-postgresql - Backup Archiving Recovery Open Sourced - PostgreSQL backend bareos-database-sqlite3 - Backup Archiving Recovery Open Sourced - SQLite backend bareos-database-tools - Backup Archiving Recovery Open Sourced - database tools bareos-dbg - Backup Archiving Recovery Open Sourced - debugging symbols bareos-devel - Backup Archiving Recovery Open Sourced - development files bareos-director - Backup Archiving Recovery Open Sourced - director daemon bareos-director-python-plugin - Backup Archiving Recovery Open Sourced - director-python-plugin bareos-filedaemon - Backup Archiving Recovery Open Sourced - file daemon bareos-filedaemon-python-plugin - Backup Archiving Recovery Open Sourced - filedaemon-python-plugin bareos-storage - Backup Archiving Recovery Open Sourced - storage daemon bareos-storage-fifo - Backup Archiving Recovery Open Sourced - storage daemon FIFO back bareos-storage-python-plugin - Backup Archiving
Bug#792847: marked as done (libcupt4-dev: fails to upgrade from 'testing' - trying to overwrite /usr/include/cupt/common.hpp)
Your message dated Sun, 02 Aug 2015 17:04:06 + with message-id e1zlwga-0006cc...@franck.debian.org and subject line Bug#792847: fixed in cupt 2.9.2 has caused the Debian Bug report #792847, regarding libcupt4-dev: fails to upgrade from 'testing' - trying to overwrite /usr/include/cupt/common.hpp 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.) -- 792847: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=792847 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: libcupt4-dev Version: 2.9.1 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed your package fails to upgrade from 'testing'. It installed fine in 'testing', then the upgrade to 'sid' fails because it tries to overwrite other packages files without declaring a Breaks+Replaces relation. See policy 7.6 at https://www.debian.org/doc/debian-policy/ch-relationships.html#s-replaces From the attached log (scroll to the bottom...): Selecting previously unselected package libcupt4-dev. Preparing to unpack .../libcupt4-dev_2.9.1_amd64.deb ... Unpacking libcupt4-dev (2.9.1) ... dpkg: error processing archive /var/cache/apt/archives/libcupt4-dev_2.9.1_amd64.deb (--unpack): trying to overwrite '/usr/include/cupt/common.hpp', which is also in package libcupt3-dev 2.8.4 Errors were encountered while processing: /var/cache/apt/archives/libcupt4-dev_2.9.1_amd64.deb cheers, Andreas libcupt3-dev=2.8.4_libcupt4-dev=2.9.1.log.gz Description: application/gzip ---End Message--- ---BeginMessage--- Source: cupt Source-Version: 2.9.2 We believe that the bug you reported is fixed in the latest version of cupt, 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 792...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Eugene V. Lyubimkin jac...@debian.org (supplier of updated cupt 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, 02 Aug 2015 18:44:22 +0300 Source: cupt Binary: cupt-dbg libcupt4-0 libcupt-common libcupt4-dev libcupt4-doc cupt libcupt4-0-downloadmethod-curl libcupt4-0-downloadmethod-wget Architecture: source amd64 all Version: 2.9.2 Distribution: unstable Urgency: medium Maintainer: Cupt developers cupt-de...@lists.alioth.debian.org Changed-By: Eugene V. Lyubimkin jac...@debian.org Description: cupt - flexible package manager -- console interface cupt-dbg - flexible package manager -- debugging symbols libcupt-common - flexible package manager -- runtime library (support files) libcupt4-0 - flexible package manager -- runtime library libcupt4-0-downloadmethod-curl - flexible package manager -- libcurl download method libcupt4-0-downloadmethod-wget - flexible package manager -- wget download method libcupt4-dev - flexible package manager -- development files libcupt4-doc - flexible package manager -- library documentation Closes: 792847 Changes: cupt (2.9.2) unstable; urgency=medium . * cmakelists: - Temporarily added a compiler switch to use old C++11 ABI. To be removed when Boost libraries (which we link to) get rebuilt with new C++11 ABI. - Removed some obsolete/unneeded include directories. * debian: - control: - Added forgotten Conflicts between libcupt4-dev and libcupt3-dev. (Closes: #792847) - cupt.bash-completion: - Added to use dh_bash-completion instead of manual file copying. Checksums-Sha1: 02a57a314684be17b07b90499bd88001d6b445d7 2238 cupt_2.9.2.dsc 4e53e013c70ce8ea5b1b0f87159b19012406f10c 424861 cupt_2.9.2.tar.gz fe2ce9e3c20276494b96cf2892db77622a6a0f27 10572074 cupt-dbg_2.9.2_amd64.deb e4cc5a7883c7cf97cb9357c36cf259c07b322ec4 374710 cupt_2.9.2_amd64.deb 612cb08ddfe241ef9db2f1cb06a2db867ff1167b 81338 libcupt-common_2.9.2_all.deb b9834180b5a65bdc569cddbcd15e1503796424da 50488 libcupt4-0-downloadmethod-curl_2.9.2_amd64.deb 89e23a1dfce426e924d80d66c913a3f36b4a3c49 52080 libcupt4-0-downloadmethod-wget_2.9.2_amd64.deb 17f0b7a80edaa2340126e4bc948e2a840de83e95 556632 libcupt4-0_2.9.2_amd64.deb e7f58f93c5369713759bcc13b384ccd2cd993040 57608 libcupt4-dev_2.9.2_amd64.deb
Processed: block 794344 with 794309
Processing commands for cont...@bugs.debian.org: block 794344 with 794309 Bug #794344 [release.debian.org] transition: python-sqlalchemy 794344 was blocked by: 794353 794352 794354 794355 794344 was not blocking any bugs. Added blocking bug(s) of 794344: 794309 thanks Stopping processing here. Please contact me if you need assistance. -- 794344: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=794344 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#794402: libproxy: library transition is needed when GCC 5 is the default
Package: src:libproxy
Version: 0.4.11-4
Severity: serious
Tags: sid stretch patch confirmed
User: debian-...@lists.debian.org
Usertags: libstdc++-cxx11
confirmed, see
https://people.debian.org/~doko/logs/gcc5-20150701/libproxy_0.4.11-4_unstable_gcc5.log
cmake should binNMUed immediately after this upload.
the qt5 stack depends on this, so it is important to get this done soon.
Background [1]: libstdc++6 introduces a new ABI to conform to the
C++11 standard, but keeps the old ABI to not break existing binaries.
Packages which are built with g++-5 from experimental (not the one
from testing/unstable) are using the new ABI. Libraries built from
this source package export some of the new __cxx11 or B5cxx11 symbols,
and dropping other symbols. If these symbols are part of the API of
the library, then this rebuild with g++-5 will trigger a transition
for the library.
What is needed:
- Rebuild the library using g++/g++-5 from experimental. Note that
most likely all C++ libraries within the build dependencies need
a rebuild too. You can find the log for a rebuild in
https://people.debian.org/~doko/logs/gcc5-20150701/
Search for BEGIN GCC CXX11 in the log.
- Decide if the symbols matching __cxx11 or B5cxx11 are part of the
library API, and are used by the reverse dependencies of the
library.
- If there are no symbols matching __cxx11 or B5cxx11 in the symbols
forming the library API, you should close this issue with a short
explanation.
- If there are no reverse dependencies, it should be the package
maintainers decision if a transition is needed. However this might
break software which is not in the Debian archive, and built
against these packages.
- If a library transition is needed, please prepare for the change.
Rename the library package, append v5 to the name of the package
(e.g. libfoo2 - libfoo2v5). Such a change can be avoided, if you
have a soversion bump and you upload this version instead of the
renamed package. Prepare a patch and attach it to this issue (mark
this issue with patch), so that it is possible to NMU such a
package. We'll probably have more than hundred transitions
triggered. Then reassign the issue to release.debian.org and
properly tag it as a transition issue, by sending an email to
cont...@bugs.debian.org:
user release.debian@packages.debian.org
usertag this issue + transition
block this issue by 790756
reassign this issue release.debian.org
- If unsure if a transition is needed, please tag the issue with help
to ask for feedback from other Debian developers.
The libstdc++6 transition will be a large one, and it will come with a
lot of pain. Please help it by preparing the follow-up transitions.
[1] https://wiki.debian.org/GCC5#libstdc.2B-.2B-_ABI_transition
diff -Nru libproxy-0.4.11/debian/changelog libproxy-0.4.11/debian/changelog
--- libproxy-0.4.11/debian/changelog2013-11-03 13:34:44.0 +0100
+++ libproxy-0.4.11/debian/changelog2015-08-02 18:17:26.0 +0200
@@ -1,3 +1,12 @@
+libproxy (0.4.11-4.1) unstable; urgency=medium
+
+ * Non maintainer upload.
+ * Rename library libproxy1 - libproxy1v5, needed as a follow-up transition
+for the libstdc++6 ABI changes (patch by Sebastien Bacher).
+Addresses: #.
+
+ -- Matthias Klose d...@debian.org Sun, 02 Aug 2015 18:11:31 +0200
+
libproxy (0.4.11-4) unstable; urgency=low
* Upload to unstable
diff -Nru libproxy-0.4.11/debian/control libproxy-0.4.11/debian/control
--- libproxy-0.4.11/debian/control 2013-11-03 13:43:09.0 +0100
+++ libproxy-0.4.11/debian/control 2015-08-02 18:20:15.0 +0200
@@ -10,6 +9,7 @@
Uploaders: Debian GNOME Maintainers
pkg-gnome-maintain...@lists.alioth.debian.org, Laurent Bigonville
bi...@debian.org
Build-Depends-Indep: cli-common-dev (= 0.5.7~), mono-devel (= 2.4.3)
Build-Depends: debhelper (= 9),
+ g++ (= 4:5.2),
gnome-pkg-tools,
netbase,
cmake,
@@ -29,12 +29,14 @@
Vcs-Browser:
http://anonscm.debian.org/viewvc/pkg-gnome/packages/unstable/libproxy/
Homepage: http://code.google.com/p/libproxy/
-Package: libproxy1
+Package: libproxy1v5
Architecture: any
Multi-Arch: same
Pre-Depends: ${misc:Pre-Depends}
Depends: ${shlibs:Depends},
${misc:Depends}
+Conflicts: libproxy1
+Replaces: libproxy1
Description: automatic proxy configuration management library (shared)
libproxy is a lightweight library which makes it easy to develop
applications proxy-aware with a simple and stable API.
@@ -46,7 +48,7 @@
Multi-Arch: same
Depends: ${shlibs:Depends},
${misc:Depends},
- libproxy1 (= ${binary:Version})
+ libproxy1v5 (= ${binary:Version})
Description: automatic proxy configuration management library (GSettings
plugin)
libproxy is a lightweight library which makes it easy to develop
applications proxy-aware with a simple and stable API.
@@
Processed: reassign 794352 to openstack-trove
Processing commands for cont...@bugs.debian.org: reassign 794352 openstack-trove Bug #794352 [src:python-trove] python-trove: Uninstallable due to python-alchemy version Warning: Unknown package 'src:python-trove' Bug reassigned from package 'src:python-trove' to 'openstack-trove'. No longer marked as found in versions python-trove/2015.1.0-3. Ignoring request to alter fixed versions of bug #794352 to the same values previously set thanks Stopping processing here. Please contact me if you need assistance. -- 794352: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=794352 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#793855: marked as done (DoS, Shibboleth SP software crashes on well-formed but invalid XML (CVE-2015-0851))
Your message dated Sun, 02 Aug 2015 17:47:48 + with message-id e1zlxms-0003z0...@franck.debian.org and subject line Bug#793855: fixed in xmltooling 1.5.3-2+deb8u1 has caused the Debian Bug report #793855, regarding DoS, Shibboleth SP software crashes on well-formed but invalid XML (CVE-2015-0851) 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.) -- 793855: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=793855 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Source: xmltooling Version: 1.3.3-2 Severity: serious Tags: security patch upstream Shibboleth Service Provider software contains a code path with an uncaught exception that can be triggered by an unauthenticated attacker by supplying well-formed but schema-invalid XML in the form of SAML metadata or SAML protocol messages. The result is a crash and so causes a denial of service. Updated versions of OpenSAML-C (V2.5.5) and XMLTooling-C (V1.5.5) are available that correct this bug. This vulnerability has been assigned CVE-2015-0851. Please mention the CVE ID in changelog when fixing this issue. References: * Bulletin http://shibboleth.net/community/advisories/secadv_20150721.txt * Fixing commit (xmltooling) https://git.shibboleth.net/view/?p=cpp-xmltooling.git;a=commitdiff;h=2d795c731e6729309044607154978696a87fd900 Cheers, Luca ---End Message--- ---BeginMessage--- Source: xmltooling Source-Version: 1.5.3-2+deb8u1 We believe that the bug you reported is fixed in the latest version of xmltooling, 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. Ferenc Wagner wf...@niif.hu (supplier of updated xmltooling 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, 19 Jul 2015 19:06:38 +0200 Source: xmltooling Binary: libxmltooling6 libxmltooling-dev xmltooling-schemas libxmltooling-doc Architecture: source amd64 all Version: 1.5.3-2+deb8u1 Distribution: jessie-security Urgency: high Maintainer: Debian Shib Team pkg-shibboleth-de...@lists.alioth.debian.org Changed-By: Ferenc Wagner wf...@niif.hu Description: libxmltooling-dev - C++ XML parsing library with encryption support (development) libxmltooling-doc - C++ XML parsing library with encryption support (API docs) libxmltooling6 - C++ XML parsing library with encryption support (runtime) xmltooling-schemas - XML schemas for XMLTooling Closes: 793855 Changes: xmltooling (1.5.3-2+deb8u1) jessie-security; urgency=high . * Apply security fix from 1.5.5 for CVE-2015-0851 DoS (Closes: #793855): Shibboleth SP software crashes on well-formed but invalid XML Checksums-Sha1: ec0640f0130928fc7f4c713c0b1f315c4611dba4 2386 xmltooling_1.5.3-2+deb8u1.dsc b8498a8dafe18bf612a6651ab7af662add5c2a68 675350 xmltooling_1.5.3.orig.tar.gz 0758ce1a029e28aba1bb8d28733d4ca5641bc77b 9740 xmltooling_1.5.3-2+deb8u1.debian.tar.xz 6de6123be03ad5aa0f166eb97eb071e653772056 592426 libxmltooling6_1.5.3-2+deb8u1_amd64.deb 9411a7181425d89fe342e7dd6ad35be8bfe30bc0 71508 libxmltooling-dev_1.5.3-2+deb8u1_amd64.deb eb8a19085a30707e33a07733e01d32b9523bd3ef 15908 xmltooling-schemas_1.5.3-2+deb8u1_all.deb ac6e067f681bc8cfe3007efef49548154661e60e 473782 libxmltooling-doc_1.5.3-2+deb8u1_all.deb Checksums-Sha256: 6f8e3ca5b1173bd53067fe3519dad03cf2422161a32bbb13f6982e0ada1e69a3 2386 xmltooling_1.5.3-2+deb8u1.dsc 90e453deb738574b04f1f1aa08ed7cc9d8746bcbf93eb59f401a6e38f2ec9574 675350 xmltooling_1.5.3.orig.tar.gz 48ae589d4bc43d6510d888e87250ea65678e4217aa10d522748eaddf7aaec529 9740 xmltooling_1.5.3-2+deb8u1.debian.tar.xz 3c27b530491df78b49d3590422a64e02bf89ebd3b3a9925d211e680cc4f8b6b5 592426 libxmltooling6_1.5.3-2+deb8u1_amd64.deb 5c038d7a41279599ed717197ad82c2d534e3c4c2d0303b638e045039f3076149 71508 libxmltooling-dev_1.5.3-2+deb8u1_amd64.deb 263a3118af38f370b8f1b80fde28833a9bc7ec3f15b1da60a57a14467c61a9c7 15908 xmltooling-schemas_1.5.3-2+deb8u1_all.deb 864a9acb9e4d6bb1350a780a23714b87f6dd2dca9a00e93bcbd69664649acaf1 473782 libxmltooling-doc_1.5.3-2+deb8u1_all.deb Files: bd0afd52bd75eff40abcd75c2de66d29 2386 libs extra
Bug#794298: asciinema: broken, Unable to upload
Marcin Kulik wrote on Sun, Aug 02, 2015 at 14:42:18 +0200: These issues (https, saving to tmp file) has been addressed in 0.9.9 (the latest version is 1.1.1 btw). Versions 0.9.8 also use documented, open format for the recordings. Thank you for the prompt response and fix, Marcin! I look forward to 0.9.9. I have just re-enabled support for 0.9.8 on the server side to fix this problem, but I’d like to stop supporting it in the near future (unsafe http connection is the #1 reason). Is there a chance to update this Debian package to the latest upstream version in not so distant future? I don't know; I'm not familiar with Debian's policies. Cheers, Daniel Marcin Kulik -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#741642: mkvmlinuz: How to easily use mkvmlinuz/38 on Jessie?
Le 2015-08-02 15:17, Milan Kupcevic a écrit : On 07/22/2015 11:47 AM, intervenant0 gilles charabot wrote: Dear Maintainer, To avoid the consequences of the bug#741642, I want to use mkvmlinuz/38, but it isn't inside Jessie repository and isn't yet inside jessie-backports repository and when I tried to download the patch with : # cd /usr/sbin # wget https://bugs.debian.org/cgi-bin/bugreport.cgi?msg=40;att=1;bug=741642;filename=mkvmlinuz-run-parts-fix.patch I have nothing new inside /usr/sbin to apply patch. If possible can you backports mkvmlinuz/38 to Jessie, so upgrade Wheezy to Jessie be more easier for me and others. Hi Gilles, Watch bug #793556 for progress on inclusion of this bugfix into Jessie.[0] In the meantime you can download mkvmlinuz[1] version 38 and install it on your machine before upgrading to Jessie to secure smooth upgrade. Milan [0] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=793556 [1] http://ftp.fr.debian.org/debian/pool/main/m/mkvmlinuz/mkvmlinuz_38_powerpc.deb Thanks for mkvmlinuz_38_powerpc.deb for wheezy Best regards -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#794378: missing license in debian/copyright
Package: libusb Version: 2:0.1.12-26 Severity: serious User: alteh...@debian.org Usertags: ftp X-Debbugs-CC: ftpmas...@ftp-master.debian.org thanks Dear Maintainer, according to libusb-0.1.12/LICENSE the files usb.h.in and/or usb.h may be licensed under the BSD license. Please mention that in your debian/copyright. Thanks! Thorsten -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#791072: icu: library transition may be needed when GCC 5 is the default
Control: tags -1 help Hi Matthias, On Sun, Aug 2, 2015 at 12:18 AM, László Böszörményi (GCS) g...@debian.org wrote: Pretty please upload the version from experimental to unstable. It would be a bigger transition as the API changed. Needs testing if all packages can be built with the new, 55.1 version. Will do that in the morning. Midnight is passed here. :-| I have building the dependency level 1 [1] and github-backup, hardinfo, haskell-hledger-web and icedove built fine with icu-55.1 . But ledger has build-dependency on libboost-date-time-dev which is transitively marked broken by libstdc++6 . Thus please check my previously attached patch[2] if it covers everything needed for the gcc-5 transition. Then we can start the icu transition separately. Thanks, Laszlo/GCS [1] https://release.debian.org/transitions/html/auto-icu.html [2] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=791072#19 -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#792070: FTBFS: Writer tests give: Segmentation fault
Hi, On Tue, Jul 28, 2015 at 10:01:46PM +0200, Rene Engelhard wrote: On Fri, Jul 10, 2015 at 09:18:25PM +, Chris West (Faux) wrote: [--] 20 tests from Writer [ RUN ] Writer.Compact [ OK ] Writer.Compact (0 ms) [ RUN ] Writer.Root [ OK ] Writer.Root (0 ms) [ RUN ] Writer.Int Segmentation fault debian/rules:41: recipe for target 'override_dh_auto_test' failed make[1]: *** [override_dh_auto_test] Error 139 make[1]: Leaving directory '/tmp/buildd/rapidjson-0.12~git20141031' Yeah, same here :/ [...] When I build here I see [237033.938824] unittest_releas[19831]: segfault at 2e20e29 ip 004d0405 sp 7fff27d24d60 error 4 in unittest_release_native_gmake[40+164000] in dmesg. Interestingly it seems it works when built with gcc 5... Regards, Rene -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: Re: Bug#791072: icu: library transition may be needed when GCC 5 is the default
Processing control commands: tags -1 help Bug #791072 [src:icu] icu: library transition may be needed when GCC 5 is the default Added tag(s) help. -- 791072: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=791072 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#794334: [Pkg-amule-devel] Bug#794334: ea-utils: /usr/bin/alc already used by amule-utils-gui
On Sun, Aug 2, 2015 at 6:59 AM, Andreas Tille ti...@debian.org wrote: I just learned that there is a name space conflicts with the new package ea-utils and amule-utils-gui. I know that we are working according to a first comes first served basis and thus ea-utils would be responsible to rename this file. However, I would like to ask you anyway whether there is any chance to deal with this name space conflict from the amule-utils side. what do you propose? I dont see any indications of 'alc' in ea-tools home page: https://code.google.com/p/ea-utils/ (if it's not important to advertise it..) as of now, I think the new package has to adapt to the status quo. Regards, -- Sandro Tosi (aka morph, morpheus, matrixhasu) My website: http://matrixhasu.altervista.org/ Me at Debian: http://wiki.debian.org/SandroTosi -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#794334: [Pkg-amule-devel] Bug#794334: ea-utils: /usr/bin/alc already used by amule-utils-gui
Hi Sandro, On Sun, Aug 02, 2015 at 01:02:54PM +0100, Sandro Tosi wrote: On Sun, Aug 2, 2015 at 6:59 AM, Andreas Tille ti...@debian.org wrote: I just learned that there is a name space conflicts with the new package ea-utils and amule-utils-gui. I know that we are working according to a first comes first served basis and thus ea-utils would be responsible to rename this file. However, I would like to ask you anyway whether there is any chance to deal with this name space conflict from the amule-utils side. what do you propose? I dont see any indications of 'alc' in ea-tools home page: https://code.google.com/p/ea-utils/ (if it's not important to advertise it..) as of now, I think the new package has to adapt to the status quo. Yes, this is what I assumed but I wanted to make sure with you that this is the case. Thanks for your quick answer. Tim, my proposed solution would be to rename /usr/bin/alc from ea-utils to ea-utils-alc and provide a symlink /usr/lib/debian-med/bin/alc If qiime is using alc it should adapt the PATH accordingly. What do you think about this? Kind regards Andreas. -- http://fam-tille.de -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#777862: marked as done (gbsplay: ftbfs with GCC-5)
Your message dated Sun, 02 Aug 2015 15:34:54 + with message-id e1zlvhq-00026b...@franck.debian.org and subject line Bug#777862: fixed in gbsplay 0.0.92-1 has caused the Debian Bug report #777862, regarding gbsplay: ftbfs with GCC-5 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.) -- 777862: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=777862 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: src:gbsplay Version: 0.0.91-1 Severity: normal Tags: sid stretch User: debian-...@lists.debian.org Usertags: ftbfs-gcc-5 Please keep this issue open in the bug tracker for the package it was filed for. If a fix in another package is required, please file a bug for the other package (or clone), and add a block in this package. Please keep the issue open until the package can be built in a follow-up test rebuild. The package fails to build in a test rebuild on at least amd64 with gcc-5/g++-5, but succeeds to build with gcc-4.9/g++-4.9. The severity of this report may be raised before the stretch release. The full build log can be found at: http://people.debian.org/~doko/logs/gcc5-20150205/gbsplay_0.0.91-1_unstable_gcc5.log The last lines of the build log are at the end of this report. To build with GCC 5, either set CC=gcc-5 CXX=g++-5 explicitly, or install the gcc, g++, gfortran, ... packages from experimental. apt-get -t experimental install g++ Common build failures are C11 as the default C mode, new warnings resulting in build failures with -Werror turned on, or new/dropped symbols in Debian symbols files. For other C/C++ related build failures see the porting guide at http://gcc.gnu.org/gcc-5/porting_to.html [...] CC gbhw.c -o gbhw.o CC gbs.c -o gbs.o gbs.c: In function 'gbs_init': gbs.c:106:2: warning: dereferencing type-punned pointer will break strict-aliasing rules [-Wstrict-aliasing] REGS16_W(gbcpu_regs, PC, 0x0050); /* playercode entry point */ ^ gbs.c:107:2: warning: dereferencing type-punned pointer will break strict-aliasing rules [-Wstrict-aliasing] REGS16_W(gbcpu_regs, SP, gbs-stack); ^ gbs.c:108:2: warning: dereferencing type-punned pointer will break strict-aliasing rules [-Wstrict-aliasing] REGS16_W(gbcpu_regs, HL, gbs-load - 0x70); ^ gbs.c: In function 'gbs_write': gbs.c:332:2: warning: ignoring return value of 'write', declared with attribute warn_unused_result [-Wunused-result] write(fd, gbs-buf, newlen); ^ gbs.c: In function 'gbs_open': gbs.c:358:2: warning: ignoring return value of 'read', declared with attribute warn_unused_result [-Wunused-result] read(fd, buf, st.st_size); ^ CC cfgparser.c -o cfgparser.o CC crc32.c -o crc32.o CC impulsegen.c -o impulsegen.o CC gbsplay.c -o gbsplay.o In file included from gbsplay.c:27:0: util.h:11:13: warning: inline function 'rand_long' declared but never defined inline long rand_long(long max); ^ CC util.c -o util.o CC plugout.c -o plugout.o CC plugout_devdsp.c -o plugout_devdsp.o CC plugout_nas.c -o plugout_nas.o CC plugout_stdout.c -o plugout_stdout.o CC plugout_midi.c -o plugout_midi.o ar r libgbs.a gbcpu.o gbhw.o gbs.o cfgparser.o crc32.o impulsegen.o ar: creating libgbs.a CC gbsinfo.c -o gbsinfo.o touch libgbs gcc -o gbsplay gbsplay.o util.o plugout.o plugout_devdsp.o plugout_nas.o plugout_stdout.o plugout_midi.o libgbs.a -Wl,-O1 -lm -fstack-protector -laudio -lm gbsplay.o: In function `get_next_subsong': gbsplay.c:(.text+0x32a): undefined reference to `rand_long' gbsplay.o: In function `main': gbsplay.c:(.text.startup+0x9d1): undefined reference to `rand_long' collect2: error: ld returned 1 exit status make[1]: *** [gbsplay] Error 1 Makefile:331: recipe for target 'gbsplay' failed make[1]: Leaving directory '/«PKGBUILDDIR»' make: *** [build-stamp] Error 2 debian/rules:22: recipe for target 'build-stamp' failed dpkg-buildpackage: error: debian/rules build gave error exit status 2 ---End Message--- ---BeginMessage--- Source: gbsplay Source-Version: 0.0.92-1 We believe that the bug you reported is fixed in the latest version of gbsplay, 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 777...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Christian Garbs deb...@cgarbs.de (supplier of updated gbsplay package) (This message was generated automatically at their request; if you believe that there is a
Bug#791072: marked as done (icu: library transition may be needed when GCC 5 is the default)
Your message dated Sun, 02 Aug 2015 15:36:06 + with message-id e1zlvj0-0002uv...@franck.debian.org and subject line Bug#791072: fixed in icu 55.1-3 has caused the Debian Bug report #791072, regarding icu: library transition may be needed when GCC 5 is the default 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.) -- 791072: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=791072 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: src:icu Version: 52.1-9 Severity: important Tags: sid stretch User: debian-...@lists.debian.org Usertags: libstdc++-cxx11 Background [1]: libstdc++6 introduces a new ABI to conform to the C++11 standard, but keeps the old ABI to not break existing binaries. Packages which are built with g++-5 from experimental (not the one from testing/unstable) are using the new ABI. Libraries built from this source package export some of the new __cxx11 or B5cxx11 symbols, and dropping other symbols. If these symbols are part of the API of the library, then this rebuild with g++-5 will trigger a transition for the library. What is needed: - Rebuild the library using g++/g++-5 from experimental. Note that most likely all C++ libraries within the build dependencies need a rebuild too. You can find the log for a rebuild in https://people.debian.org/~doko/logs/gcc5-20150701/ Search for BEGIN GCC CXX11 in the log. - Decide if the symbols matching __cxx11 or B5cxx11 are part of the library API, and are used by the reverse dependencies of the library. - If there are no symbols matching __cxx11 or B5cxx11 in the symbols forming the library API, you should close this issue with a short explanation. - If there are no reverse dependencies, it should be the package maintainers decision if a transition is needed. However this might break software which is not in the Debian archive, and built against these packages. - If a library transition is needed, please prepare for the change. Rename the library package, append v5 to the name of the package (e.g. libfoo2 - libfoo2v5). Such a change can be avoided, if you have a soversion bump and you upload this version instead of the renamed package. Prepare a patch and attach it to this issue (mark this issue with patch), so that it is possible to NMU such a package. We'll probably have more than hundred transitions triggered. Then reassign the issue to release.debian.org and properly tag it as a transition issue, by sending an email to cont...@bugs.debian.org: user release.debian@packages.debian.org usertag this issue + transition block this issue by 790756 reassign this issue release.debian.org - If unsure if a transition is needed, please tag the issue with help to ask for feedback from other Debian developers. The libstdc++6 transition will be a large one, and it will come with a lot of pain. Please help it by preparing the follow-up transitions. [1] https://wiki.debian.org/GCC5#libstdc.2B-.2B-_ABI_transition ---End Message--- ---BeginMessage--- Source: icu Source-Version: 55.1-3 We believe that the bug you reported is fixed in the latest version of icu, 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. Laszlo Boszormenyi (GCS) g...@debian.org (supplier of updated icu 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, 02 Aug 2015 14:13:05 +0200 Source: icu Binary: libicu55 libicu55-dbg libicu-dev icu-devtools icu-doc Architecture: source amd64 all Version: 55.1-3 Distribution: unstable Urgency: high Maintainer: Laszlo Boszormenyi (GCS) g...@debian.org Changed-By: Laszlo Boszormenyi (GCS) g...@debian.org Description: icu-devtools - Development utilities for International Components for Unicode icu-doc- API documentation for ICU classes and functions libicu-dev - Development files for International Components for Unicode libicu55 - International Components for Unicode libicu55-dbg - International Components for Unicode Closes: 791072 Changes: icu (55.1-3) unstable;
Bug#793745: [PATCH] I'm seeing it too.
Since I run a pool server, I have a customized config. That means that
I have the pool servers commented out, and the comment on the rlimit
command says it's not needed in that case, so I left it out of my config.
And ran into the same problem.
Really, ntpd should make calls like getpwuid() before calling mlock,
This requires breaking -u option processing has to be broken into
two phases (since you can't mlock after changing uid), but it's not that
hard. Appended is a (working for me) patch to do just that.
The mlockall() fails because it exceeds the available limit, but ntpd
just logs the error and continues. In the original, earlier location
it succeeds, but then later allocations fail due to the same limit.
diff -ru ntp-4.2.8p3+dfsg.orig/ntpd/ntpd.c ntp-4.2.8p3+dfsg/ntpd/ntpd.c
--- ntp-4.2.8p3+dfsg.orig/ntpd/ntpd.c 2015-08-01 22:46:20.0 -0400
+++ ntp-4.2.8p3+dfsg/ntpd/ntpd.c2015-08-02 14:53:20.879051191 -0400
@@ -792,37 +792,6 @@
*/
getconfig(argc, argv);
- if (do_memlock) {
-# if defined(HAVE_MLOCKALL)
- /*
-* lock the process into memory
-*/
- if (!HAVE_OPT(SAVECONFIGQUIT)
- 0 != mlockall(MCL_CURRENT|MCL_FUTURE))
- msyslog(LOG_ERR, mlockall(): %m);
-# else /* !HAVE_MLOCKALL follows */
-# ifdef HAVE_PLOCK
-# ifdef PROCLOCK
- /*
-* lock the process into memory
-*/
- if (!HAVE_OPT(SAVECONFIGQUIT) 0 != plock(PROCLOCK))
- msyslog(LOG_ERR, plock(PROCLOCK): %m);
-# else /* !PROCLOCK follows */
-#ifdef TXTLOCK
- /*
-* Lock text into ram
-*/
- if (!HAVE_OPT(SAVECONFIGQUIT) 0 != plock(TXTLOCK))
- msyslog(LOG_ERR, plock(TXTLOCK) error: %m);
-#else /* !TXTLOCK follows */
- msyslog(LOG_ERR, plock() - don't know what to lock!);
-#endif /* !TXTLOCK */
-# endif /* !PROCLOCK */
-# endif /* HAVE_PLOCK */
-# endif/* !HAVE_MLOCKALL */
- }
-
loop_config(LOOP_DRIFTINIT, 0);
report_event(EVNT_SYSRESTART, NULL, NULL);
initializing = FALSE;
@@ -931,6 +900,49 @@
exit (-1);
}
}
+ }
+# endif /* HAVE_DROPROOT */
+
+ /*
+* DROPROOT is divided into two phases. Gathering information
+* is done before locking us into memory, since /etc/nsswitch.conf
+* can mess with our address space. Actually dropping privileges
+* is done after. (We can chroot() before, since the mlock()
+* system call doesn't depend on that.)
+*/
+ if (do_memlock) {
+# if defined(HAVE_MLOCKALL)
+ /*
+* lock the process into memory
+*/
+ if (!HAVE_OPT(SAVECONFIGQUIT)
+ 0 != mlockall(MCL_CURRENT|MCL_FUTURE))
+ msyslog(LOG_ERR, mlockall(): %m);
+# else /* !HAVE_MLOCKALL follows */
+# ifdef HAVE_PLOCK
+# ifdef PROCLOCK
+ /*
+* lock the process into memory
+*/
+ if (!HAVE_OPT(SAVECONFIGQUIT) 0 != plock(PROCLOCK))
+ msyslog(LOG_ERR, plock(PROCLOCK): %m);
+# else /* !PROCLOCK follows */
+#ifdef TXTLOCK
+ /*
+* Lock text into ram
+*/
+ if (!HAVE_OPT(SAVECONFIGQUIT) 0 != plock(TXTLOCK))
+ msyslog(LOG_ERR, plock(TXTLOCK) error: %m);
+#else /* !TXTLOCK follows */
+ msyslog(LOG_ERR, plock() - don't know what to lock!);
+#endif /* !TXTLOCK */
+# endif /* !PROCLOCK */
+# endif /* HAVE_PLOCK */
+# endif/* !HAVE_MLOCKALL */
+ }
+
+# ifdef HAVE_DROPROOT
+ if (droproot) {
# ifdef HAVE_SOLARIS_PRIVS
if ((lowprivs = priv_str_to_set(LOWPRIVS, ,, NULL)) == NULL) {
msyslog(LOG_ERR, priv_str_to_set() failed:%m);
Only in ntp-4.2.8p3+dfsg/ntpd: ntpd.c.orig
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#793745: [pkg-ntp-maintainers] Bug#793745: [PATCH] I'm seeing it too.
On Sun, Aug 02, 2015 at 03:22:27PM -0400, sacrificial-spam-addr...@horizon.com wrote: Since I run a pool server, I have a customized config. That means that I have the pool servers commented out, and the comment on the rlimit command says it's not needed in that case, so I left it out of my config. Maybe the comment is a little misleading. There have been various reports over the past few year about the rlimit breaking things, but ussually dieing after a few hours of running or something like that. With the pool command it just doesn't start (for me). Maybe other see different kinds of error like the getpwuid() fail instead. Kurt -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#794102: closed by Scott Kitterman deb...@kitterman.com (Re: Bug#794102: OK)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Dear Scott, configuration does not have ~/.xsession and the error persist. Why do you have close the bug without a check? Please ask to me if you need more information to manage the bug. Meanwhile I use XFce that seems a little bit more stable and has not this kind of problem. Thanks Marco Righi Il 02/08/2015 16:48, Debian Bug Tracking System ha scritto: This is an automatic notification regarding your Bug report which was filed against the kwin package: #794102: [kde-full] Windows frames disappears It has been closed by Scott Kitterman deb...@kitterman.com. Their explanation is attached below along with your original report. If this explanation is unsatisfactory and you have not received a better one in a separate message then please contact Scott Kitterman deb...@kitterman.com by replying to this email. - -- Think Marco, think different web site:http://www.di.unipi.it/~righi/ -BEGIN PGP SIGNATURE- Version: GnuPG v2 iEYEARECAAYFAlW+k20ACgkQ4+L/eCZYK/yOOgCcCMlLb5hmI4JhtvIpjxirr3+V NXoAn0CI+/mJoRyLUKeLcoBTz9XyEpSE =RNU6 -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#794102: closed by Scott Kitterman deb...@kitterman.com (Re: Bug#794102: OK)
On August 2, 2015 6:02:21 PM EDT, Marco Righi marco.ri...@gmail.com wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Dear Scott, configuration does not have ~/.xsession and the error persist. Why do you have close the bug without a check? Please ask to me if you need more information to manage the bug. https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=794102#44 makes it seem like this particular bug is resolved. What specifically is still wrong with window decorations, which is the topic of this bug? Scott K -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#794278: marked as done (madness: FTBFS on mipsel)
Your message dated Sun, 02 Aug 2015 22:49:34 + with message-id e1zm24u-0006mf...@franck.debian.org and subject line Bug#794278: fixed in madness 0.10-2 has caused the Debian Bug report #794278, regarding madness: FTBFS on mipsel 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.) -- 794278: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=794278 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Source: madness Severity: serious Justification: fails to build from source Dear maintainer, madness seems to FTBFS on mipsel [0]. Apart of this bug, I've opened an upstream issue as well [1]. I reproduced the issue locally in my mipsel machine. Will keep this bug updated with news as they happen. Best regards. [0] https://buildd.debian.org/status/fetch.php?pkg=madnessarch=mipselver=0.10-1stamp=1437866412 [1] https://github.com/m-a-d-n-e-s-s/madness/issues/148 ---End Message--- ---BeginMessage--- Source: madness Source-Version: 0.10-2 We believe that the bug you reported is fixed in the latest version of madness, 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. Michael Banck mba...@debian.org (supplier of updated madness 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: Mon, 03 Aug 2015 00:42:51 +0200 Source: madness Binary: libmadness-dev Architecture: source Version: 0.10-2 Distribution: unstable Urgency: medium Maintainer: Debichem Team debichem-de...@lists.alioth.debian.org Changed-By: Michael Banck mba...@debian.org Description: libmadness-dev - Numerical Environment for Scientific Simulation (development file Closes: 794278 Changes: madness (0.10-2) unstable; urgency=medium . * debian/copyright: Updated for previously missed gtest code, thanks to Thorsten Alteholz. * debian/control (Vcs-Browser, Vcs-Svn): Fixed URLs. * debian/rules (override_dh_auto_test): Skip tests if nocheck is set in $(DEB_BUILD_OPTIONS). * debian/control (Description): Fix typo. * debian/patches/cmake_config.patch: New patch, fixes the CMake config file and installs it to the expected directory. * debian/patches/non_intel_asm_fix.patch: New patch, works around unportable assembler code, taken from upstream commit f679f8f5 (Closes: #794278). * debian/rules (override_dh_auto_clean): Remove files generated by autogen.sh. Checksums-Sha1: b1b523d46cf70683fea56d0f0327a083e2adc565 1980 madness_0.10-2.dsc 751b26f17ff9a866d97aaa327b350de7f5a53f22 4260 madness_0.10-2.debian.tar.xz Checksums-Sha256: e78d16b8e4d977ed3fa42d4c3560cee7ea4bf543f6ba303a9994d3d6e556c000 1980 madness_0.10-2.dsc 838e9b2c09eeac05f0eb642e6a1eb4dd40cafd4d585530fdf0fdfa2160d53076 4260 madness_0.10-2.debian.tar.xz Files: 2c3c161c09ac2571f7a4831a9df905bd 1980 libdevel optional madness_0.10-2.dsc 2fbba1c49f0213449018f0e10ca32890 4260 libdevel optional madness_0.10-2.debian.tar.xz -BEGIN PGP SIGNATURE- Version: GnuPG v1 iQIcBAEBAgAGBQJVvp0QAAoJENxoaie0NIGwMq0P/jDjpTx8prlcjWTYPV3L3BRw wUQPcQTc+XaciI5bGTo3pYUMLGyvDli9rsZ3xdwWeTG5tdS/pq0nFRkN4ZNM+9aJ gawin/MxvsCid8GGtpGGxu+EMFiC47khVlTmOYF4XI776hl/718Nk/8zo1fKheH8 Bv/CbEcgK7jTuV0XSIBKQQzjyLoRWMobHzuwBvziEouio+QsUBrPxBDWwrfnBLTo KryiseE/mwxyRy2Mor36FRg9yTWsHKji9LHM8ibOIXYOb66oD9CpRQwHdTiLHPYj 08C7oE5rSb88qjaFWmZqawzvQlz+V5coHeoCyepLjFswRmj1O2Q8/Iws3mLUN+e7 E7OI4VQJl3ZKiehDVzQ8fJ/GdhyUwWYQEluuygyl5sIsgH9Y3jUKWY4ZIELxK2tA OtN8Px4e2shHjTafyl9AELmLP7CcPZHaunkr69Xsszbgsu23k5TgmDD7JwbEkNsa IqqVfLMCI4q7MXVrBu19Pxax4rpBDPuCaFxeEtRx6sWo/CQXltPwyzv+DNSL93BV jx/MGoffkjXVHiOFHtZXnat3HDNWuDIHcBNL8sYBktSKs64i71xH4TXBZD5rSqRV ltGW5K8iueEyqVWt0w/WQvqJRKPe5vfqwuC4elMAwK7YY73FatyJLjyeAz13x5gP GCsQjym5pLOsSIfsGsd5 =9Zli -END PGP SIGNATUREEnd Message---
Processed: Re: Bug#793608: linux: update Recommends of linux on armel/sh4 due to package renamed
Processing control commands: severity -1 serious Bug #793608 [linux] linux: update Depends of linux on armel/sh4 due to package renamed Severity set to 'serious' from 'normal' tag -1 jessie sid Bug #793608 [linux] linux: update Depends of linux on armel/sh4 due to package renamed Added tag(s) jessie and sid. found -1 3.16.7-ckt11-1 Bug #793608 [linux] linux: update Depends of linux on armel/sh4 due to package renamed There is no source info for the package 'linux' at version '3.16.7-ckt11-1' with architecture '' Unable to make a source version for version '3.16.7-ckt11-1' Marked as found in versions 3.16.7-ckt11-1. found -1 4.0.8-2 Bug #793608 [linux] linux: update Depends of linux on armel/sh4 due to package renamed There is no source info for the package 'linux' at version '4.0.8-2' with architecture '' Unable to make a source version for version '4.0.8-2' Marked as found in versions 4.0.8-2. -- 793608: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=793608 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#793888: ui-gxmlcpp includes autogenerated files that cannot be rebuilt from source
Control: severity -1 important Hi, Quoting Stephan Sürken (2015-08-02 10:24:24) On Sa, 2015-08-01 at 19:46 +0200, Johannes Schauer wrote: I reported it like that because I was not able to recreate ./configure and aclocal.m4 from source. When I deleted both files and tried to regenerate them, I ran into an error and I also got an error when I tried to rebuild with `dh --with autoreconf`. This made me believe that ./configure and aclocal.m4 can *not* be built from source. so this does not work even _with_ ui-auto installed? currently, ui-gxmlcpp doesn't build at all: https://qa.debian.org/dose/debcheck/src_unstable_main/1438491604/packages/ui-gxmlcpp.html#6f35b7a5db3b524f612e0ace6da69b31 so instead I used a snaphsot from July 1 2015 and then built in a clean chroot with `dh --with autoreconf` and additional build dependencies on dh-autoreconf and ui-auto. To my surprise, the package was then buildable. This was strange because I could swear I tried the exact same thing before reporting the bug and only re-did it now to get the error log (which I should've done initially). So with autoreconf and when build depending on ui-auto, the package indeed successfully builds (at least with the archive of July 1 2015) and thus I'm adjusting the severity. Thanks! cheers, josch signature.asc Description: signature
Processed: Re: Bug#793888: ui-gxmlcpp includes autogenerated files that cannot be rebuilt from source
Processing control commands: severity -1 important Bug #793888 [src:ui-gxmlcpp] ui-gxmlcpp includes autogenerated files that cannot be rebuilt from source Severity set to 'important' from 'serious' -- 793888: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=793888 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#784743: updated patch
Tags: patch The perl patching command given by Edmund results in this change: --- debian/patches/linker-specific-changes.orig 2011-11-19 16:45:51.0 +1100 +++ debian/patches/linker-specific-changes 2015-08-03 14:16:16.518331208 +1000 @@ -65,7 +65,7 @@ grtv00.o : $(DRVDIR)/imdef.h pgxwin.o : $(DRVDIR)/pgxwin.h -pndriv.o : ./png.h ./pngconf.h ./zlib.h ./zconf.h -+pndriv.o : /usr/include/png.h /usr/include/pngconf.h /usr/include/zlib.h /usr/include/zconf.h ++pndriv.o : x2driv.o figdisp_comm.o: $(DRVDIR)/commands.h zconf.h moved from /usr/include/ to /usr/include/arch-os-compiler/ e.g. /usr/include/x86_64-linux-gnu/zconf.h. I think what is needed here is a revised version of debian/patches/linker-specific-changes which I have attached to this message. -- Description: correct linker variables This patch set sets all the linker-specific variables correctly --- Last-Update: 2011-11-18 Index: pgplot5-5.2.2/makemake === --- pgplot5-5.2.2.orig/makemake +++ pgplot5-5.2.2/makemake @@ -658,6 +658,8 @@ CPGPLOT_LIB=$CPGPLOT_LIB # SHARED_LIB=$SHARED_LIB SHARED_LD=$SHARED_LD +SHARED_LD_PGPLOT_OPTS=$SHARED_LD_PGPLOT_OPTS +SHARED_LD_CPGPLOT_OPTS=$SHARED_LD_CPGPLOT_OPTS # # The libraries that the shared PGPLOT library depends upon. # This is for systems that allow one to specify what libraries @@ -667,6 +669,7 @@ SHARED_LD=$SHARED_LD # libraries when they link their executables. # SHARED_LIB_LIBS=$SHARED_LIB_LIBS +SHARED_LIB_CPGPLOT_LIBS=$SHARED_LIB_CPGPLOT_LIBS # # Ranlib command if required # @@ -806,7 +809,8 @@ grexec.o: grexec.f # libraries. #--- -lib : libpgplot.a $(SHARED_LIB) +#lib : libpgplot.a $(SHARED_LIB) +lib : libpgplot.a libpgplot.a : $(PG_ROUTINES) $(PG_NON_STANDARD) $(GR_ROUTINES) \ $(DISPATCH_ROUTINE) $(DRIVERS) $(SYSTEM_ROUTINES) @@ -816,6 +820,16 @@ libpgplot.a : $(PG_ROUTINES) $(PG_NON_ST $(DRIVERS) $(SYSTEM_ROUTINES) | sort | uniq` $(RANLIB) libpgplot.a +#shared: $(PG_ROUTINES) $(PG_NON_STANDARD) $(GR_ROUTINES) \ +# $(DISPATCH_ROUTINE) $(DRIVERS) $(SYSTEM_ROUTINES) +# $(SHARED_LD) + +shared: $(PG_ROUTINES) $(PG_NON_STANDARD) \ + $(GR_ROUTINES) $(DISPATCH_ROUTINE) $(DRIVERS) $(SYSTEM_ROUTINES) + $(SHARED_LD) $(SHARED_LD_PGPLOT_OPTS) `ls $(PG_ROUTINES) \ + $(PG_NON_STANDARD) $(GR_ROUTINES) $(DISPATCH_ROUTINE) \ + $(DRIVERS) $(SYSTEM_ROUTINES) | sort | uniq` $(SHARED_LIB_LIBS) + EOD # Emit the shared library dependency if requested. @@ -824,7 +838,7 @@ if test -n $SHARED_LIB -a -n $SHARED_ cat makefile \EOD $(SHARED_LIB): $(PG_ROUTINES) $(PG_NON_STANDARD) \ $(GR_ROUTINES) $(DISPATCH_ROUTINE) $(DRIVERS) $(SYSTEM_ROUTINES) - $(SHARED_LD) `ls $(PG_ROUTINES) \ + $(SHARED_LD) $(SHARED_LD_PGPLOT_OPTS) `ls $(PG_ROUTINES) \ $(PG_NON_STANDARD) $(GR_ROUTINES) $(DISPATCH_ROUTINE) \ $(DRIVERS) $(SYSTEM_ROUTINES) | sort | uniq` $(SHARED_LIB_LIBS) EOD @@ -1019,13 +1033,15 @@ EOD cat makefile \EOD +DEB_HOST_MULTIARCH=$(shell dpkg-architecture -qDEB_HOST_MULTIARCH) + # Miscellaneous include files required by drivers griv00.o : $(DRVDIR)/gadef.h $(DRVDIR)/gmdef.h $(DRVDIR)/gphdef.h grivas.o : $(DRVDIR)/gadef.h grtv00.o : $(DRVDIR)/imdef.h pgxwin.o : $(DRVDIR)/pgxwin.h -pndriv.o : ./png.h ./pngconf.h ./zlib.h ./zconf.h +pndriv.o : /usr/include/png.h /usr/include/pngconf.h /usr/include/zlib.h /usr/include/$(DEB_HOST_MULTIARCH)/zconf.h x2driv.o figdisp_comm.o: $(DRVDIR)/commands.h @@ -1039,6 +1055,8 @@ cpg: libcpgplot.a cpgplot.h cpgdemo @echo 'will be needed.' @echo ' ' +cpg-shared: libcpgplot.so + pgbind: $(SRC)/cpg/pgbind.c $(CCOMPL) $(CFLAGC) $(SRC)/cpg/pgbind.c -o pgbind @@ -1050,6 +1068,13 @@ libcpgplot.a cpgplot.h: $(PG_SOURCE) pgb $(RANLIB) libcpgplot.a rm -f cpg*.o +libcpgplot.so: $(PG_SOURCE) pgbind + ./pgbind $(PGBIND_FLAGS) -w $(PG_SOURCE) + $(CCOMPL) -c $(CFLAGC) cpg*.c + rm -f cpg*.c + $(SHARED_LD) $(SHARED_LD_CPGPLOT_OPTS) cpg*.o $(SHARED_LIB_CPGPLOT_LIBS) + rm -f cpg*.o + cpgdemo: cpgplot.h $(SRC)/cpg/cpgdemo.c libcpgplot.a $(CCOMPL) $(CFLAGD) -c -I. $(SRC)/cpg/cpgdemo.c $(FCOMPL) -o cpgdemo cpgdemo.o $(CPGPLOT_LIB) $(LIBS)
Processed: limit source to pjproject, tagging 793972, tagging 793051, tagging 793097
Processing commands for cont...@bugs.debian.org: limit source pjproject Limiting to bugs with field 'source' containing at least one of 'pjproject' Limit currently set to 'source':'pjproject' tags 793972 + pending Bug #793972 [src:pjproject] src:pjproject: should use SP800-90 compliant DRBG, not libsrtp crypto_get_random() Added tag(s) pending. tags 793051 + pending Bug #793051 [pjproject] missing license in debian/copyright Added tag(s) pending. tags 793097 + pending Bug #793097 [libpjproject-dev] libpjproject-dev: arch-dependent files in Multi-Arch: same package Added tag(s) pending. thanks Stopping processing here. Please contact me if you need assistance. -- 793051: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=793051 793097: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=793097 793972: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=793972 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#794102: closed by Scott Kitterman deb...@kitterman.com (Re: Bug#794102: OK)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 I have not windows frames (each process is in a windows without any type of border) and I can not switch from a process to another one using ALT-TAB combination. Il 03/08/2015 00:38, Scott Kitterman ha scritto: On August 2, 2015 6:02:21 PM EDT, Marco Righi marco.ri...@gmail.com wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Dear Scott, configuration does not have ~/.xsession and the error persist. Why do you have close the bug without a check? Please ask to me if you need more information to manage the bug. https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=794102#44 makes it seem like this particular bug is resolved. What specifically is still wrong with window decorations, which is the topic of this bug? Scott K - -- Think Marco, think different web site:http://www.di.unipi.it/~righi/ -BEGIN PGP SIGNATURE- Version: GnuPG v2 iEYEARECAAYFAlW+phUACgkQ4+L/eCZYK/wC2ACeI6NgsvvMyfb7eXaLaJkw2Zlj tAQAnRhTHsLli2Of/ex7cb2pivMl8LOm =/7Yq -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#793745: [pkg-ntp-maintainers] Bug#793745: [PATCH] I'm seeing it too.
Maybe the comment is a little misleading. How about # Preventing ntpd from swapping (with mlockall()) reduces time delays, # but resource limits (ulimit -l) cause out-of-meory errors that lead to # ntpd quitting with strange (or no) error messages. Particular trouble # spots are the -u option (depending on /etc/nsswitch.conf) and the pool # command (which does DNS lookups at run time). It's more reliable with # this disabled. # # Note that the busier your NTP server, the less swapping is a concern # in the first place. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#777862: gbsplay: diff for NMU version 0.0.91-1.1
On Sun, 02 Aug 2015 15:36:24 +0200, Christian Garbs wrote: W: gbsplay: copyright-refers-to-versionless-license-file usr/share/common-licenses/GPL That's a problem. Upstream does not say _which_ GPL version in the README: | gbsplay - A Gameboy sound player | | (C) 2003-2006,2008 by Tobias Diedrich ranma+gbsp...@tdiedrich.de | Christian Garbs mi...@cgarbs.de | Maximilian Rehkopf ota...@gmx.net | Vegard Nossum vegar...@ifi.uio.no | | Licensed under GNU GPL. So I don't know what to do :-/ In my understanding, no spcific GPL version means each GPL version means GPL-1+, and a pointer to usr/share/common-licenses/GPL-1. 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 `- NP: Bruce Springsteen: Further On (Up the Road) signature.asc Description: Digital Signature
Bug#794298: asciinema: broken, Unable to upload
On Sun, Aug 02, 2015 at 02:42:18 +0200, Marcin Kulik wrote: These issues (https, saving to tmp file) has been addressed in 0.9.9 (the latest version is 1.1.1 btw). Versions 0.9.8 also use documented, open format for the recordings. I have just re-enabled support for 0.9.8 on the server side to fix this problem, but I’d like to stop supporting it in the near future (unsafe http connection is the #1 reason). great, thanks Is there a chance to update this Debian package to the latest upstream version in not so distant future? the package is too old for 2 reasons - not long ago jessie was released, before that we were in freeze - 0.9.8 is the latest python version of asciinema. I never packaged a go application for debian before, it is on my TODO list but it will take more time (it is a new thing for me) Daniel, I'm sorry you found the program does not work, I haven't use it in a while so I wasn't aware of the breakage. Marcin, could you release a last python version, a patch is fine too, which uses https? I could upload that right away while I work on packaging the latest version -- Marcin -- 1AE0 322E B8F7 4717 BDEA BF1D 44BB 1BA7 9F6C 6333 keybase: http://keybase.io/gfa -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#794102: closed by Scott Kitterman deb...@kitterman.com (Re: Bug#794102: OK)
On August 2, 2015 7:21:57 PM EDT, Marco Righi marco.ri...@gmail.com wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 I have not windows frames (each process is in a windows without any type of border) and I can not switch from a process to another one using ALT-TAB combination. OK. I hadn't noticed the comment I referenced wasn't from the original reporter. Please make sure your system is fully upgraded and restart your KDE session. If the problem persists, please reopen the bug and let us know what versions of kwin-x11 and plasma-workspace you have installed. Scott K -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: affects 789452, found 794044 in 0.9.7-5, found 771085 in 3.14.2-2 ...
Processing commands for cont...@bugs.debian.org: affects 789452 + python-qt4-dbg Bug #789452 [sip4] python-qt4-dbg: unhandled symlink to directory conversion: /usr/share/doc/PACKAGE Added indication that 789452 affects python-qt4-dbg found 794044 0.9.7-5 Bug #794044 [python-migrate-doc] python-migrate-doc: fails to upgrade from 'testing' - trying to overwrite /usr/share/man/man1/migrate-repository.1.gz Marked as found in versions migrate/0.9.7-5. found 771085 3.14.2-2 Bug #771085 [gdm3] gdm3: unowned symlink after purge (policy 6.8, 10.8): /etc/systemd/system/display-manager.service Marked as found in versions gdm3/3.14.2-2. reassign 794359 ruby-redis-namespace 1.4.1-2 Bug #794359 [ruby-redis-namespce] FTBFS: port tests to rspec 3 for updating to 1.5.2 Warning: Unknown package 'ruby-redis-namespce' Bug reassigned from package 'ruby-redis-namespce' to 'ruby-redis-namespace'. No longer marked as found in versions 1.4.1-2. Ignoring request to alter fixed versions of bug #794359 to the same values previously set Bug #794359 [ruby-redis-namespace] FTBFS: port tests to rspec 3 for updating to 1.5.2 Marked as found in versions ruby-redis-namespace/1.4.1-2. thanks Stopping processing here. Please contact me if you need assistance. -- 771085: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=771085 789452: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=789452 794044: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=794044 794359: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=794359 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#794438: Partition manager does not launch
Package: partitionmanager Version: 1.0.3-2.1 Severity: grave Dear Maintainer, * What led up to the situation? I recently updated my KDE desktop to plasma5 which entails a lot of changes, lots of things not working yet, including this one. partitionmanager errors out saying that root password incorrect. This is a false positive, root password is correct. I tested it on other programs that depend on it, like Synaptic Package Manager. * What exactly did you do (or not do) that was effective (or ineffective)? I just launched partition manager from an icon in my desktop * What was the outcome of this action? http://i.imgur.com/79Qrvl7.png * What outcome did you expect instead? A normal launch like in plasma4 -- System Information: Debian Release: stretch/sid APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.0.0-2-amd64 (SMP w/8 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages partitionmanager depends on: ii kde-runtime 4:4.14.2-2 ii libblkid1 2.26.2-6 ii libc6 2.19-19 ii libgcc1 1:5.1.1-14 ii libkdecore5 4:4.14.2-5 ii libkdeui5 4:4.14.2-5 ii libkio5 4:4.14.2-5 ii libparted-fs-resize0 3.2-7 ii libparted23.2-7 ii libqtcore44:4.8.7+dfsg-1 ii libqtgui4 4:4.8.7+dfsg-1 ii libstdc++65.1.1-14 ii libuuid1 2.26.2-6 partitionmanager recommends no packages. -- *Carlos Kosloff* Office: (954) 283-8828 Cell: (954) 464-8822 Fax: (888) 854-5440
