Bug#731959: marked as done (undefined reference to `get_proc_stats')
Your message dated Sun, 18 May 2014 08:25:01 +0200 with message-id CA+7wUsxr5pM4QZkaysH_ECNGU7=qzz49djnrs3blt5+kzjf...@mail.gmail.com and subject line has caused the Debian Bug report #731959, regarding undefined reference to `get_proc_stats' 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.) -- 731959: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=731959 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: libprocps0-dev Version: 1:3.3.3-3 I am trying to port an application from squeeze to wheezy. On squeeze my application required libproc-dev, which apparently has been moved to libprocps0-dev. However there is something not clear to me, on wheezy: $ grep get_proc_stats /usr/include/proc/*.h /usr/include/proc/readproc.h:extern proc_t * get_proc_stats(pid_t pid, proc_t *p); but: $ nm -D /usr/lib/x86_64-linux-gnu/libprocps.so | grep get_ U __ctype_get_mb_cur_max c150 T get_pid_digits ac40 T get_slabinfo Is this a bug (regression) ? or am I missing something here ? For reference, on squeeze: $ grep get_proc_stats /usr/include/proc/*.h /usr/include/proc/readproc.h:extern proc_t * get_proc_stats(pid_t pid, proc_t *p); and: $ nm -D /lib/libproc-3.2.8.so | grep get_ U __ctype_get_mb_cur_max cf75 T get_pid_digits 9d29 T get_proc_stats ae4d T get_slabinfo Thanks much ! ---End Message--- ---BeginMessage--- Control: found -1 0.1~bzr28-1 Control: fixed -1 0.1~bzr33-1 This was fixed in latest upstream.---End Message---
Bug#748537: packagekit: Current packagekit version breaks jhbuild on usage of GetTid()
Package: packagekit Version: 0.8.17-2 Severity: serious Justification: Policy 7.3 My apologies if I should be reopening bug 700237 which is supposed to have closed/fixed this issue. But jhbuild 3.4.0-1 is current for all Debian distros, and this uses the GetTid() from versions of packagekit 0.8. JHBuild fixes this in a later version, but this is not even experimental at this time, so shouldn't a Breaks be added? -- System Information: Debian Release: jessie/sid APT prefers testing APT policy: (650, 'testing'), (500, 'testing-updates') Architecture: amd64 (x86_64) Kernel: Linux 3.13-1-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages packagekit depends on: ii libc6 2.18-5 ii libglib2.0-0 2.40.0-3 ii libglib2.0-bin2.40.0-3 ii libpackagekit-glib2-160.8.17-2 ii libpolkit-gobject-1-0 0.105-5 ii libsqlite3-0 3.8.4.3-3 ii libsystemd-journal0 204-8 ii libsystemd-login0 204-8 ii packagekit-backend-aptcc 0.8.17-2 ii policykit-1 0.105-5 Versions of packages packagekit recommends: ii packagekit-tools 0.8.17-2 Versions of packages packagekit suggests: pn packagekit-backend-smart none -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed (with 1 errors): forcibly merging 748513 548150
Processing commands for cont...@bugs.debian.org:
forcemerge 748513 548150
Bug #748513 [opensmtpd] opensmtpd: Opensmtpd does not start
Unable to merge bugs because:
package of #548150 is 'libpdfbox-java' not 'opensmtpd'
Failed to forcibly merge 748513: Did not alter merged bugs
Debbugs::Control::set_merged('transcript', 'GLOB(0x2214960)',
'requester', 'Ryan Kavanagh r...@debian.org', 'request_addr',
'cont...@bugs.debian.org', 'request_msgid',
'1400397317-3645-bts-...@debian.org', 'request_subject', ...) called at
/usr/local/lib/site_perl/Debbugs/Control/Service.pm line 552
eval {...} called at
/usr/local/lib/site_perl/Debbugs/Control/Service.pm line 551
Debbugs::Control::Service::control_line('line', undef, 'clonebugs',
'HASH(0x2196390)', 'limit', 'HASH(0x218c990)', 'common_control_options',
'ARRAY(0x218c9d8)', 'errors', ...) called at /usr/lib/debbugs/service line 474
thanks
Stopping processing here.
Please contact me if you need assistance.
--
548150: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=548150
748513: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=748513
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#748053: vtk6: diff for NMU version 6.0.0-7.1
Hi Anton On 2014-05-18 07:33:42, Anton Gladky wrote: Hi Sebastian, thanks a lot for the patch. As I told you before I have managed uploading a newer vtk6 version (6.1.0), which builds fine againse libav10. Sorry, seems like I didn't get a mail about that. Anyway, 6.1.0 FTBFS all over the place: https://buildd.debian.org/status/package.php?p=vtk6. Could you please take a look it? Could you please cancel your NMU? Or I think one can simply wait till it will be rejected. Sure, canceled. Cheers -- Sebastian Ramacher signature.asc Description: Digital signature
Bug#748323: blender: FTBFS on non-x86
Control: tags -1 + fixed-upstream On 2014-05-16 09:03:27, Rebecca N. Palmer wrote: Package: blender Version: 2.70-2 blender tries to compile /«PKGBUILDDIR»/intern/cycles/kernel/kernel_sse2.cpp with SSE options, which is an error on non-x86: c++: error: unrecognized command line option '-msse' c++: error: unrecognized command line option '-msse2' c++: error: unrecognized command line option '-mfpmath=sse' (full log: https://buildd.debian.org/status/fetch.php?pkg=blenderarch=armhfver=2.70-2stamp=1399859920 ) It looks like intern/cycles/SConscript is where it decides whether to do this, but I haven't tried to turn it off yet. To record our findings on IRC: this is fixed upstream in 2.70a. Cheers -- Sebastian Ramacher signature.asc Description: Digital signature
Processed: Re: Bug#748323: blender: FTBFS on non-x86
Processing control commands: tags -1 + fixed-upstream Bug #748323 [blender] blender: FTBFS on non-x86 Added tag(s) fixed-upstream. -- 748323: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=748323 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: forcibly merging 748513 748150
Processing commands for cont...@bugs.debian.org: forcemerge 748513 748150 Bug #748513 [opensmtpd] opensmtpd: Opensmtpd does not start Bug #748150 [opensmtpd] opensmtpd: OpenSSL version mismatch strikes again Severity set to 'grave' from 'important' Merged 748150 748513 thanks Stopping processing here. Please contact me if you need assistance. -- 748150: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=748150 748513: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=748513 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: Re: Bug#748322: blender: FTBFS on non-Linux
Processing control commands: tags -1 + patch Bug #748322 [blender] blender: FTBFS on non-Linux Added tag(s) patch. -- 748322: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=748322 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#748322: blender: FTBFS on non-Linux
Control: tags -1 + patch On 2014-05-16 09:02:34, Rebecca N. Palmer wrote: Package: blender Version: 2.70-2 Tags: patch blender 2.70 fails to build on kFreeBSD with /«PKGBUILDDIR»/intern/guardedalloc/intern/mallocn_intern.h:66:4: error: #error We don't know how to use malloc_usable_size on your platform It appears that this file is checking for Linux ( #if defined(__linux__) at line 54) when it should be checking for GNU libc ( __GLIBC__, https://wiki.debian.org/Debian_GNU/kFreeBSD_FAQ?highlight=%28kfreebsd%29#Q._How_do_I_detect_kfreebsd_with_preprocessor_directives_in_a_C_program.3F), though I have not tested this fix. The attached patch should be enough to fix this issue. Cheers -- Sebastian Ramacher --- blender-2.70a.orig/intern/guardedalloc/intern/mallocn_intern.h +++ blender-2.70a/intern/guardedalloc/intern/mallocn_intern.h @@ -51,7 +51,7 @@ #undef HAVE_MALLOC_STATS -#if defined(__linux__) +#if defined(__linux__) || (defined(__FreeBSD_kernel__) !defined(__FreeBSD__)) # include malloc.h # define HAVE_MALLOC_STATS #elif defined(__FreeBSD__) signature.asc Description: Digital signature
Bug#748545: Does not work - starts, but does nothing
Package: gxtuner Version: 2.1-1 Severity: critical The window regularly opens, but the program never shows any activity. Nothing is written to the terminal. The two buttons allow me to change the level of threshold and reference pitch, but nothing changes. (on the same system, at the same time and with the same connections, jmeters correctly shows the volume of the audio input, and zita-at1 even works as a rough tuner) -- System Information: Debian Release: jessie/sid APT prefers testing APT policy: (650, 'testing'), (600, 'unstable'), (500, 'oldstable-updates'), (400, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.13-1-amd64 (SMP w/2 CPU cores) Locale: LANG=it_IT.utf8, LC_CTYPE=it_IT.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages gxtuner depends on: ii libatk1.0-0 2.12.0-1 ii libc6 2.18-5 ii libcairo2 1.12.16-2 ii libfftw3-single3 3.3.4-1 ii libfontconfig12.11.0-5 ii libfreetype6 2.5.2-1 ii libgcc1 1:4.9.0-2 ii libgdk-pixbuf2.0-02.30.7-1 ii libglib2.0-0 2.40.0-3 ii libgtk2.0-0 2.24.23-1 ii libjack-jackd2-0 [libjack-0.116] 1.9.9.5+20140404git3d7c67dc~dfsg-1 ii libpango-1.0-01.36.3-1 ii libpangocairo-1.0-0 1.36.3-1 ii libpangoft2-1.0-0 1.36.3-1 ii libstdc++64.9.0-2 ii libx11-6 2:1.6.2-1 ii libzita-resampler11.3.0-2 gxtuner recommends no packages. gxtuner suggests no packages. -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#743685: marked as done (FTBFS: test failures)
Your message dated Sun, 18 May 2014 09:42:26 +
with message-id e1wlxbu-0003vv...@franck.debian.org
and subject line Bug#743685: fixed in urwid 1.2.1-2
has caused the Debian Bug report #743685,
regarding FTBFS: test failures
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.)
--
743685: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=743685
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
---BeginMessage---
Source: urwid
Version: 1.2.1-1
Severity: serious
Justification: fails to build from source (but built successfully in the past)
Dear Maintainer,
urwid 1.2.1-1 currently FTBFS on i386 and mipsel according to the buildd [1]
logs. Note that the test suite is now run against all python2 and python3
versions supported in sid (rather than just python2, as was the case with
previous versions of urwid); the test failure on i386 is a new one, and only
happens with python3.
i386 [2]:
==
FAIL: test_linefeed (urwid.tests.test_vterm.TermTest)
--
Traceback (most recent call last):
File /«PKGBUILDDIR»/build/lib.linux-i686-3.4/urwid/tests/test_vterm.py,
line 128, in test_linefeed
self.expect('hello\nworld')
File /«PKGBUILDDIR»/build/lib.linux-i686-3.4/urwid/tests/test_vterm.py,
line 120, in expect
self.assertEqual(got, what, desc)
AssertionError: b'hello' != b'hello\nworld' : Expected:
b'hello\nworld'
Got:
b'hello'
--
Ran 280 tests in 0.758s
FAILED (failures=1)
mipsel [3]:
==
FAIL: test_run (urwid.tests.test_event_loops.TwistedEventLoopTest)
--
Traceback (most recent call last):
File /«PKGBUILDDIR»/urwid/tests/test_event_loops.py, line 128, in test_run
self.assertIn(da, out)
AssertionError: 'da' not found in ['waiting', 'hello', 'clean exit']
--
Ran 289 tests in 6.329s
FAILED (failures=1)
[1] https://buildd.debian.org/status/package.php?p=urwid
[2]
https://buildd.debian.org/status/fetch.php?pkg=urwidarch=i386ver=1.2.1-1stamp=1396632579
[3]
https://buildd.debian.org/status/fetch.php?pkg=urwidarch=mipselver=1.2.1-1stamp=1396648217
Regards,
Vincent
-- System Information:
Debian Release: jessie/sid
APT prefers testing
APT policy: (700, 'testing'), (500, 'unstable'), (200, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 3.13-5-vclaptop-amd64 (SMP w/8 CPU cores; PREEMPT)
Locale: LANG=en_CA.UTF-8, LC_CTYPE=en_CA.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
---End Message---
---BeginMessage---
Source: urwid
Source-Version: 1.2.1-2
We believe that the bug you reported is fixed in the latest version of
urwid, 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 743...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Vincent Cheng vch...@debian.org (supplier of updated urwid 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, 18 May 2014 02:07:47 -0700
Source: urwid
Binary: python-urwid python3-urwid
Architecture: source amd64
Version: 1.2.1-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Python Modules Team
python-modules-t...@lists.alioth.debian.org
Changed-By: Vincent Cheng vch...@debian.org
Description:
python-urwid - curses-based UI/widget library for Python 2
python3-urwid - curses-based UI/widget library for Python 3
Closes: 743685
Changes:
urwid (1.2.1-2) unstable; urgency=medium
.
* Team upload.
* Skip vterm test suite. (Closes: #743685)
Checksums-Sha1:
184c2f453235dee6e5c7743d4ff5f338ddcb14fe 2144 urwid_1.2.1-2.dsc
dbafd9cecdce6f995de68df53c13c13a5b17b472 4928 urwid_1.2.1-2.debian.tar.xz
92da033142c04bdc5d748da42e4ebcf713ea2e7f 705020 python-urwid_1.2.1-2_amd64.deb
7840f0bdfa372dd9074164c873621cc48d8a03dc 168136 python3-urwid_1.2.1-2_amd64.deb
Checksums-Sha256:
Bug#746081: marked as done (ruby-dbi: FTBFS: ERROR: Test ruby2.1 failed: wrong number of arguments (3 for 1..2))
Your message dated Sun, 18 May 2014 09:42:04 + with message-id e1wlxby-0003mw...@franck.debian.org and subject line Bug#746081: fixed in ruby-dbi 0.4.5-3 has caused the Debian Bug report #746081, regarding ruby-dbi: FTBFS: ERROR: Test ruby2.1 failed: wrong number of arguments (3 for 1..2) 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.) -- 746081: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=746081 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Source: ruby-dbi Version: 0.4.5-2 Severity: serious Tags: jessie sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20140426 qa-ftbfs Justification: FTBFS on amd64 Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): Running tests for ruby2.1 with test file list from debian/ruby-test-files.yaml ... test/unit warning: method TC_DBI_Date#test_constructor is redefined test/unit warning: method TC_DBI_Date#test_to_date is redefined test/unit warning: method TC_DBI_Date#test_to_time is redefined test/unit warning: method TC_DBI_Date#test_to_s is redefined test/unit warning: method TC_DBI_Date#test_day is redefined test/unit warning: method TC_DBI_Date#test_mday is redefined test/unit warning: method TC_DBI_Date#test_month is redefined test/unit warning: method TC_DBI_Date#test_mon is redefined test/unit warning: method TC_DBI_Date#test_year is redefined Run options: # Running tests: F Finished tests in 0.032940s, 3309.0124 tests/s, 15330.7455 assertions/s. 1) Failure: TC_DBI_ColumnInfo#test_constructor [/«PKGBUILDDIR»/test/dbi/tc_columninfo.rb:42]: [TypeError] exception expected, not Class: ArgumentError Message: wrong number of arguments (3 for 1..2) ---Backtrace--- /«PKGBUILDDIR»/lib/dbi/columninfo.rb:63:in `method_missing' /«PKGBUILDDIR»/lib/dbi/columninfo.rb:40:in `block in initialize' /«PKGBUILDDIR»/lib/dbi/columninfo.rb:36:in `each' /«PKGBUILDDIR»/lib/dbi/columninfo.rb:36:in `initialize' /«PKGBUILDDIR»/test/dbi/tc_columninfo.rb:43:in `new' /«PKGBUILDDIR»/test/dbi/tc_columninfo.rb:43:in `block in test_constructor' /usr/lib/ruby/2.1.0/minitest/unit.rb:362:in `assert_raises' /«PKGBUILDDIR»/test/dbi/tc_columninfo.rb:42:in `test_constructor' /usr/lib/ruby/2.1.0/test/unit.rb:869:in `run_test' /usr/lib/ruby/2.1.0/minitest/unit.rb:1265:in `run' /usr/lib/ruby/2.1.0/test/unit/testcase.rb:17:in `run' /usr/lib/ruby/2.1.0/minitest/unit.rb:940:in `block in _run_suite' /usr/lib/ruby/2.1.0/minitest/unit.rb:933:in `map' /usr/lib/ruby/2.1.0/minitest/unit.rb:933:in `_run_suite' /usr/lib/ruby/2.1.0/test/unit.rb:663:in `block in _run_suites' /usr/lib/ruby/2.1.0/test/unit.rb:661:in `each' /usr/lib/ruby/2.1.0/test/unit.rb:661:in `_run_suites' /usr/lib/ruby/2.1.0/minitest/unit.rb:884:in `_run_anything' /usr/lib/ruby/2.1.0/minitest/unit.rb:1092:in `run_tests' /usr/lib/ruby/2.1.0/minitest/unit.rb:1079:in `block in _run' /usr/lib/ruby/2.1.0/minitest/unit.rb:1078:in `each' /usr/lib/ruby/2.1.0/minitest/unit.rb:1078:in `_run' /usr/lib/ruby/2.1.0/minitest/unit.rb:1066:in `run' /usr/lib/ruby/2.1.0/test/unit.rb:27:in `run' /usr/lib/ruby/2.1.0/test/unit.rb:780:in `run' /usr/lib/ruby/2.1.0/test/unit.rb:372:in `block (2 levels) in autorun' /usr/lib/ruby/2.1.0/test/unit.rb:33:in `run_once' /usr/lib/ruby/2.1.0/test/unit.rb:371:in `block in autorun' --- 109 tests, 505 assertions, 1 failures, 0 errors, 0 skips ruby -v: ruby 2.1.1p76 (2014-02-24) [x86_64-linux-gnu] ERROR: Test ruby2.1 failed: The full build log is available from: http://aws-logs.debian.net/ftbfs-logs/2014/04/26/ruby-dbi_0.4.5-2_unstable.log A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! About the archive rebuild: The rebuild was done on EC2 VM instances from Amazon Web Services, using a clean, minimal and up-to-date chroot. Every failed build was retried once to eliminate random failures. ---End Message--- ---BeginMessage--- Source: ruby-dbi Source-Version: 0.4.5-3 We believe that the bug you reported is fixed in the latest version of ruby-dbi, 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 746...@bugs.debian.org, and the maintainer will reopen the bug
Bug#748546: devede: depends on libavcodec-extra-54, which is going away
package: devede severity: serious version: 3.23.0-13-gbfd73f3-1 Hi, It seems devede depends on libavcodec-extra-54, which is going away with the libav transition. This wasn't picked up by the transition tracker 'libav10' (because there is no build-dep on libav), but the 'auto-libav' tracker shows it. https://release.debian.org/transitions/html/auto-libav.html Cheers, Ivo -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#748094: marked as done (datefudge - Is Multi-Arch: same)
Your message dated Sun, 18 May 2014 12:13:36 +0200 with message-id 537887d0.6030...@debian.org and subject line Re: Bug#748094: datefudge - Is Multi-Arch: same has caused the Debian Bug report #748094, regarding datefudge - Is Multi-Arch: same 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.) -- 748094: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=748094 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: datefudge Version: 1.20 Severity: serious datefudge is marked as Multi-Arch: same. However it contains unshareable files: | datefudge:amd64: /usr/bin/datefudge You want to use Multi-Arch: foreign (see https://wiki.ubuntu.com/MultiarchSpec#Dependencies_involving_Architecture:_all_packages) Bastian -- System Information: Debian Release: jessie/sid APT prefers testing APT policy: (990, 'testing'), (500, 'testing-updates'), (500, 'unstable'), (500, 'stable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 3.13-1-amd64 (SMP w/4 CPU cores) Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash ---End Message--- ---BeginMessage--- Robert Luberda pisze: Bastian Blank pisze: datefudge is marked as Multi-Arch: same. However it contains unshareable files: | datefudge:amd64: /usr/bin/datefudge Why do you think the file is unsharable? robert@ravel:$ find . -path '*/bin/*' -name datefudge | xargs md5sum 8c7c3a15eab410c7a8b3638480f0cf32 ./datefudge_1.20_sparc/usr/bin/datefudge 8c7c3a15eab410c7a8b3638480f0cf32 ./datefudge_1.20_s390x/usr/bin/datefudge 8c7c3a15eab410c7a8b3638480f0cf32 ./datefudge_1.20_powerpc/usr/bin/datefudge 8c7c3a15eab410c7a8b3638480f0cf32 ./datefudge_1.20_mipsel/usr/bin/datefudge 8c7c3a15eab410c7a8b3638480f0cf32 ./datefudge_1.20_mips/usr/bin/datefudge 8c7c3a15eab410c7a8b3638480f0cf32 ./datefudge_1.20_kfreebsd-i386/usr/bin/datefudge 8c7c3a15eab410c7a8b3638480f0cf32 ./datefudge_1.20_kfreebsd-amd64/usr/bin/datefudge 8c7c3a15eab410c7a8b3638480f0cf32 ./datefudge_1.20_i386/usr/bin/datefudge 8c7c3a15eab410c7a8b3638480f0cf32 ./datefudge_1.20_hurd-i386/usr/bin/datefudge 8c7c3a15eab410c7a8b3638480f0cf32 ./datefudge_1.20_armhf/usr/bin/datefudge 8c7c3a15eab410c7a8b3638480f0cf32 ./datefudge_1.20_armel/usr/bin/datefudge 8c7c3a15eab410c7a8b3638480f0cf32 ./datefudge_1.20_amd64/usr/bin/datefudge Closing the bug report. Regards, robert Regards, robert ---End Message---
Bug#739460: openscenegraph: diff for NMU version 3.2.0~rc1-5.1
Hi Reinhard, 2014-05-17 22:30 GMT+01:00 Reinhard Tartler siret...@tauware.de: Package: openscenegraph Version: 3.2.0~rc1-5 Severity: normal Tags: patch pending Dear maintainer, I've prepared an NMU for openscenegraph (versioned as 3.2.0~rc1-5.1) and uploaded it to DELAYED/02. Please feel free to tell me if I should delay it longer. The patch provided for the older bug (687332) was sent only a week ago, part of the information/testing provided based on a derivative and not Debian, with not very popular desktops/setups, and (original author said) untested and not sure if this should be considered an openscenegraph bug or an Xfce bug . The patch might fix the issue for flightgear, but it can have widespread consequences and may beak other applications within Debian or in user's systems using the library for other purposes which happen to rely on this behaviour, so it's not something to include lightly and without asking upstream, for example. The package is not unmaintained, so you should not include fixes for minor bugs unrelated to the main purpose of fixing the RC/important bugs in general. See How confident are you about your changes? in the NMU section of Developer Reference Guide. So, can you please remove that change in the NMU, if you want to keep the NMU at all? Apart from that, the NMU was reopened ~7 days ago without any explanation about the transition until ~5 days ago (Sebastian Ramacher). It would not have hurt to ask first about the plans to fix the RC bug (which we were already discussing in private and group mailing lists), or give more than 2 days period, specially if you are including more changes than for the RC bug. Cheers. -- Manuel A. Fernandez Montecelo manuel.montez...@gmail.com -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#748547: FTBFS: Unknown sequence /usr/share/topgit/tg2quilt.mk
Package: input-utils Version: 1.0-1 Severity: serious Usertags: goto-cc During a rebuild of all packages in a clean sid chroot (and cowbuilder+pbuilder) the build failed with the following error. [...] dpkg-buildpackage: host architecture amd64 fakeroot debian/rules clean dh /usr/share/topgit/tg2quilt.mk dh: Unknown sequence /usr/share/topgit/tg2quilt.mk (choose from: binary binary-arch binary-indep build build-arch build-indep clean install install-arch install-indep) dh clean dh_testdir dh_auto_clean make[1]: Entering directory '/srv/jenkins-slave/workspace/sid-goto-cc-input-utils/input-utils-1.0' Make.config:1: *** empty variable name. Stop. make[1]: Leaving directory '/srv/jenkins-slave/workspace/sid-goto-cc-input-utils/input-utils-1.0' dh_auto_clean: make -j1 distclean returned exit code 2 debian/rules:10: recipe for target 'clean' failed make: *** [clean] Error 2 The full build log is attached. Best, Michael input-utils-build-log.txt.gz Description: application/gunzip pgpodqWTbBFQY.pgp Description: PGP signature
Bug#748552: vtk6: FTBFS on powerpc and kfreebsd
Source: vtk6
Version: 6.1.0+dfsg-1
Severity: serious
Justification: fails to build from source
Hi,
your package no longer builds on the powerpc and kfreebsd buildds:
[ 1%] Building CXX object
Utilities/KWSys/vtksys/CMakeFiles/vtksys.dir/SystemInformation.cxx.o
cd /«BUILDDIR»/vtk6-6.1.0+dfsg/debian/build/Utilities/KWSys/vtksys
/usr/bin/c++ -DKWSYS_NAMESPACE=vtksys -DVTK_IN_VTK -Dvtksys_EXPORTS
-DKWSYS_BUILD_SHARED=1 -DKWSYS_CXX_HAS_ATOL=1 -DKWSYS_CXX_HAS_ATOLL=1
-DKWSYS_CXX_HAS_RLIMIT64=1 -DKWSYS_SYSTEMINFORMATION_HAS_BACKTRACE=1
-DKWSYS_SYSTEMINFORMATION_HAS_CPP_DEMANGLE=1
-DKWSYS_SYSTEMINFORMATION_HAS_DEBUG_BUILD=1
-DKWSYS_SYSTEMINFORMATION_HAS_SYMBOL_LOOKUP=1 -DKWSYS_SYS_HAS_IFADDRS_H=1
-DKWSYS_USE_LONG_LONG=1 -DSIZEOF_VOID_P=8 -g -O2 -fstack-protector
--param=ssp-buffer-size=4 -Wformat -Werror=format-security
-D_FORTIFY_SOURCE=2 -Wno-deprecated -O2 -g -DNDEBUG -Wnon-virtual-dtor
-Wno-long-long -ansi -Wcast-align -Wchar-subscripts -Wall -Wextra
-Wpointer-arith -Wformat-security -Woverloaded-virtual -Wshadow
-Wunused-parameter -fno-check-new -fno-common -fPIC
-I/«BUILDDIR»/vtk6-6.1.0+dfsg/debian/build/Utilities/KWSys
-I/«BUILDDIR»/vtk6-6.1.0+dfsg/Utilities/KWSys-o
CMakeFiles/vtksys.dir/SystemInformation.cxx.o -c
/«BUILDDIR»/vtk6-6.1.0+dfsg/Utilities/KWSys/vtksys/SystemInformation.cxx
/«BUILDDIR»/vtk6-6.1.0+dfsg/Utilities/KWSys/vtksys/SystemInformation.cxx: In
member function 'std::string
vtksys::{anonymous}::SymbolProperties::Demangle(const char*) const':
/«BUILDDIR»/vtk6-6.1.0+dfsg/Utilities/KWSys/vtksys/SystemInformation.cxx:1469:5:
error: 'abi' has not been declared
abi::__cxa_demangle(symbol, buffer, bufferLen, status);
^
/«BUILDDIR»/vtk6-6.1.0+dfsg/Utilities/KWSys/vtksys/SystemInformation.cxx: In
member function 'void
vtksys::{anonymous}::SymbolProperties::Initialize(void*)':
/«BUILDDIR»/vtk6-6.1.0+dfsg/Utilities/KWSys/vtksys/SystemInformation.cxx:1487:3:
error: 'Dl_info' was not declared in this scope
Dl_info info;
^
/«BUILDDIR»/vtk6-6.1.0+dfsg/Utilities/KWSys/vtksys/SystemInformation.cxx:1487:11:
error: expected ';' before 'info'
Dl_info info;
^
/«BUILDDIR»/vtk6-6.1.0+dfsg/Utilities/KWSys/vtksys/SystemInformation.cxx:1488:34:
error: 'info' was not declared in this scope
int ierr=dladdr(this-Address,info);
^
/«BUILDDIR»/vtk6-6.1.0+dfsg/Utilities/KWSys/vtksys/SystemInformation.cxx:1488:38:
error: 'dladdr' was not declared in this scope
int ierr=dladdr(this-Address,info);
^
/«BUILDDIR»/vtk6-6.1.0+dfsg/Utilities/KWSys/vtksys/SystemInformation.cxx: In
static member function 'static std::string
vtksys::SystemInformationImplementation::GetProgramStack(int, int)':
/«BUILDDIR»/vtk6-6.1.0+dfsg/Utilities/KWSys/vtksys/SystemInformation.cxx:3640:41:
error: 'backtrace' was not declared in this scope
int nFrames=backtrace(stackSymbols,256);
^
Utilities/KWSys/vtksys/CMakeFiles/vtksys.dir/build.make:333: recipe for
target 'Utilities/KWSys/vtksys/CMakeFiles/vtksys.dir/SystemInformation.cxx.o'
failed
make[4]: ***
[Utilities/KWSys/vtksys/CMakeFiles/vtksys.dir/SystemInformation.cxx.o] Error 1
make[4]: Leaving directory '/«BUILDDIR»/vtk6-6.1.0+dfsg/debian/build'
CMakeFiles/Makefile2:333: recipe for target
'Utilities/KWSys/vtksys/CMakeFiles/vtksys.dir/all' failed
make[3]: *** [Utilities/KWSys/vtksys/CMakeFiles/vtksys.dir/all] Error 2
See the full build logs at
https://buildd.debian.org/status/package.php?p=vtk6
Cheers,
Julien
signature.asc
Description: Digital signature
Bug#748495: Acknowledgement (Missing required dependencies)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Hi, The issue seems to go away when python3.3 or newer is installed. Thus having python3 (= 3.3) as a dependency (and not only recommendation) should fix those issues. Kind regards, Benny Baumann. -BEGIN PGP SIGNATURE- Version: GnuPG v1 iQIcBAEBCgAGBQJTeJEqAAoJEPHTXLno4S6th7sP/jxYJg/tv5YAfLSK1XKhOd1E p468ozka+xl1Py5QXkxwxnF8O8WXoiWd919XYThQNqvUbsKC7YD8ESKVxneP8gKe NeGYK2z1bzW5Ln2QQqwJHDyejVh2zPd/wOnFyPiH7MUqJwoGAJsG/Y9BJksa07Gd 4EZNUWm+DUG86gALVSCbQONxH/Szgzo2l1bInAz0ESbo65wV/k0N3f2KVxjSCVY2 74DWwAb+yUQq2QOyJWgvMFbIKIUM4ym20rU1IjnVxwaycM4hzWlqsSSZgGrVr22H lvsYVbIF6PHtW3CkzAUIqJKtMDlUuO4tdrmBnddd8ba5xNVDZ8cgvtxKVWqq5w6k qEYAyWocrs6FaseN5iAQXOTpqzy2p6Czh6WzlYmpgxbJGOM3Pk8pYUSZxTCkD6qr 0NDKUpGuPJ1RoIO81NiWLVggZsWLnJBF5+hKEfvqdHRQBSPaI81pTA4qFzJL/srE LaR9i5bEmoToK5Zch5R9+ETocSLcsL1G05Z2yTNh7AR3NwhG2kAc/MXqEk0v9mTC AGoaz3uw0IG6T8MY/7uS8AHfUbIUvgW2I+vAj0vU6WHioCQWuKgGjE/099A5T5dV abzXDzXS3Ab5jVae7PNym+H7yn4VRklLF5/ZtOIhxPCRarY0JFx/v5AhGKzuOapG XsMm+B6UNDBup2M61vMS =g4Mo -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
Processed: retitle 739460 to openscenegraph: FTBFS with libav10
Processing commands for cont...@bugs.debian.org: retitle 739460 openscenegraph: FTBFS with libav10 Bug #739460 [src:openscenegraph] FTBFS with libav10 Changed Bug title to 'openscenegraph: FTBFS with libav10' from 'FTBFS with libav10' thanks Stopping processing here. Please contact me if you need assistance. -- 739460: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=739460 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#739460: openscenegraph: diff for NMU version 3.2.0~rc1-5.1
On 18.05.2014 06:24, Manuel A. Fernandez Montecelo wrote: Hi Reinhard, 2014-05-17 22:30 GMT+01:00 Reinhard Tartler siret...@tauware.de: Package: openscenegraph Version: 3.2.0~rc1-5 Severity: normal Tags: patch pending Dear maintainer, I've prepared an NMU for openscenegraph (versioned as 3.2.0~rc1-5.1) and uploaded it to DELAYED/02. Please feel free to tell me if I should delay it longer. The patch provided for the older bug (687332) was sent only a week ago, part of the information/testing provided based on a derivative and not Debian, with not very popular desktops/setups, and (original author said) untested and not sure if this should be considered an openscenegraph bug or an Xfce bug . The patch might fix the issue for flightgear, but it can have widespread consequences and may beak other applications within Debian or in user's systems using the library for other purposes which happen to rely on this behaviour, so it's not something to include lightly and without asking upstream, for example. The package is not unmaintained, so you should not include fixes for minor bugs unrelated to the main purpose of fixing the RC/important bugs in general. See How confident are you about your changes? in the NMU section of Developer Reference Guide. So, can you please remove that change in the NMU, if you want to keep the NMU at all? Sure, I've just canceled the NMU. Apart from that, the NMU was reopened ~7 days ago without any explanation about the transition until ~5 days ago (Sebastian Ramacher). It would not have hurt to ask first about the plans to fix the RC bug (which we were already discussing in private and group mailing lists), or give more than 2 days period, specially if you are including more changes than for the RC bug. Well, that's exactly what Sebastian did in https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=739460#44, without visible response. So what are your plans regarding #739460? FYI, in https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=739079#82, proposed a timeline that allows 0-days NMUs for bugs like #739460 starting from tomorrow. Thanks for responding and keeping the bugs with up-to-date information. Reinhard -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#748557: FTBFS: mixed implicit and normal rules: deprecated syntax
Package: jikespg Version: 1.3-2 Severity: serious Usertags: goto-cc During a rebuild of all packages in a clean sid chroot (and cowbuilder+pbuilder) the build failed with the following error. dpkg-buildpackage: host architecture amd64 fakeroot debian/rules clean debian/rules:3: *** mixed implicit and normal rules: deprecated syntax make: *** No rule to make target 'clean'. Stop. dpkg-buildpackage: error: fakeroot debian/rules clean gave error exit status 2 The full build log is attached. Best, Michael jikespg-build-log.txt.gz Description: application/gunzip pgpmCqsoqEV9j.pgp Description: PGP signature
Bug#748537: packagekit: Current packagekit version breaks jhbuild on usage of GetTid()
How old is our JHBuild then?? PackageKit 0.8.x is out for about two years already. I would say that this has to be fixed in JHBuild - have you talked to it's maintainer, what does he say? Cheers, Matthias -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: Pending fixes for bugs in the libdevel-findref-perl package
Processing commands for cont...@bugs.debian.org: tag 719835 + pending Bug #719835 [libdevel-findref-perl] libdevel-findref-perl: crash in XS_Devel__FindRef_find_ on Perl 5.18 Added tag(s) pending. thanks Stopping processing here. Please contact me if you need assistance. -- 719835: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=719835 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#719835: Pending fixes for bugs in the libdevel-findref-perl package
tag 719835 + pending thanks Some bugs in the libdevel-findref-perl package are closed in revision e9e80e94d0d6d60a85334979891d18c11693fed6 in branch 'master' by gregor herrmann The full diff can be seen at http://anonscm.debian.org/gitweb/?p=pkg-perl/packages/libdevel-findref-perl.git;a=commitdiff;h=e9e80e9 Commit message: New upstream release. Fixes crash in XS_Devel__FindRef_find_ on Perl 5.18. (Closes: #719835) -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#711616: Pending fixes for bugs in the libtest-refcount-perl package
tag 711616 + pending thanks Some bugs in the libtest-refcount-perl package are closed in revision edeac8a90acb3a3d04924e983a5c5d658878e21a in branch 'master' by gregor herrmann The full diff can be seen at http://anonscm.debian.org/gitweb/?p=pkg-perl/packages/libtest-refcount-perl.git;a=commitdiff;h=edeac8a Commit message: Make build dependency and Suggests on libdevel-findref-perl versioned. Closes: #711616 -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#739460: openscenegraph: diff for NMU version 3.2.0~rc1-5.1
2014-05-18 12:10 GMT+01:00 Reinhard Tartler siret...@tauware.de: So, can you please remove that change in the NMU, if you want to keep the NMU at all? Sure, I've just canceled the NMU. Thanks. From my side, I have no objection that the NMU goes ahead if it contains only the fix for libav. I don't know if Alberto has any objection or plans to fix this himself, so please wait at least until 20th for his reply. Apart from that, the NMU was reopened ~7 days ago without any explanation about the transition until ~5 days ago (Sebastian Ramacher). It would not have hurt to ask first about the plans to fix the RC bug (which we were already discussing in private and group mailing lists), or give more than 2 days period, specially if you are including more changes than for the RC bug. Well, that's exactly what Sebastian did in https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=739460#44, without visible response. So what are your plans regarding #739460? FYI, in https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=739079#82, proposed a timeline that allows 0-days NMUs for bugs like #739460 starting from tomorrow. Thanks for responding and keeping the bugs with up-to-date information. As I said above, my only issue is that it does not apply to changes other than to fix the specific problem of the transition. We made several uploads this year, so the package maintainers are active. Also, I pointed that the reply from Sebastian was less than 5 days ago, which is not a whole lot of time all things considered (I was travelling yesterday all day, so could not reply to pending questions from Alberto, for example). And I don't have room in my computer to build OSG at the moment, which is kind of a problem to get this fixed :-) I understand the desire of getting through the transitions quickly, and I appreciate your work and others to get things running quickly and helping maintainers, though. We didn't object to your NMU to experimental, and neither I nor probably Alberto are against fixing the libav issue -- instead, we thank you for it. About plans. We were thinking if to continue with the current version (which is an ~rc1 immediately obsoleted by other changes), or upload a new version (which maybe has already support for libav10, so would not need patches). As things are now, I think that it's better not to upload a new version to not delay this transition, and just upload a fix for the libav transition. I can try to build it in another computer, but if somebody beats me to it, I will not complain. Cheers. -- Manuel A. Fernandez Montecelo manuel.montez...@gmail.com -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: Pending fixes for bugs in the libtest-refcount-perl package
Processing commands for cont...@bugs.debian.org: tag 711616 + pending Bug #711616 [src:libtest-refcount-perl] libtest-refcount-perl: FTBFS with perl 5.18: test failures Added tag(s) pending. thanks Stopping processing here. Please contact me if you need assistance. -- 711616: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=711616 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#748552: marked as done (vtk6: FTBFS on powerpc and kfreebsd)
Your message dated Sun, 18 May 2014 13:06:27 +
with message-id e1wm0nl-lg...@franck.debian.org
and subject line Bug#748552: fixed in vtk6 6.1.0+dfsg-2
has caused the Debian Bug report #748552,
regarding vtk6: FTBFS on powerpc and kfreebsd
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.)
--
748552: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=748552
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
---BeginMessage---
Source: vtk6
Version: 6.1.0+dfsg-1
Severity: serious
Justification: fails to build from source
Hi,
your package no longer builds on the powerpc and kfreebsd buildds:
[ 1%] Building CXX object
Utilities/KWSys/vtksys/CMakeFiles/vtksys.dir/SystemInformation.cxx.o
cd /«BUILDDIR»/vtk6-6.1.0+dfsg/debian/build/Utilities/KWSys/vtksys
/usr/bin/c++ -DKWSYS_NAMESPACE=vtksys -DVTK_IN_VTK -Dvtksys_EXPORTS
-DKWSYS_BUILD_SHARED=1 -DKWSYS_CXX_HAS_ATOL=1 -DKWSYS_CXX_HAS_ATOLL=1
-DKWSYS_CXX_HAS_RLIMIT64=1 -DKWSYS_SYSTEMINFORMATION_HAS_BACKTRACE=1
-DKWSYS_SYSTEMINFORMATION_HAS_CPP_DEMANGLE=1
-DKWSYS_SYSTEMINFORMATION_HAS_DEBUG_BUILD=1
-DKWSYS_SYSTEMINFORMATION_HAS_SYMBOL_LOOKUP=1 -DKWSYS_SYS_HAS_IFADDRS_H=1
-DKWSYS_USE_LONG_LONG=1 -DSIZEOF_VOID_P=8 -g -O2 -fstack-protector
--param=ssp-buffer-size=4 -Wformat -Werror=format-security
-D_FORTIFY_SOURCE=2 -Wno-deprecated -O2 -g -DNDEBUG -Wnon-virtual-dtor
-Wno-long-long -ansi -Wcast-align -Wchar-subscripts -Wall -Wextra
-Wpointer-arith -Wformat-security -Woverloaded-virtual -Wshadow
-Wunused-parameter -fno-check-new -fno-common -fPIC
-I/«BUILDDIR»/vtk6-6.1.0+dfsg/debian/build/Utilities/KWSys
-I/«BUILDDIR»/vtk6-6.1.0+dfsg/Utilities/KWSys-o
CMakeFiles/vtksys.dir/SystemInformation.cxx.o -c
/«BUILDDIR»/vtk6-6.1.0+dfsg/Utilities/KWSys/vtksys/SystemInformation.cxx
/«BUILDDIR»/vtk6-6.1.0+dfsg/Utilities/KWSys/vtksys/SystemInformation.cxx: In
member function 'std::string
vtksys::{anonymous}::SymbolProperties::Demangle(const char*) const':
/«BUILDDIR»/vtk6-6.1.0+dfsg/Utilities/KWSys/vtksys/SystemInformation.cxx:1469:5:
error: 'abi' has not been declared
abi::__cxa_demangle(symbol, buffer, bufferLen, status);
^
/«BUILDDIR»/vtk6-6.1.0+dfsg/Utilities/KWSys/vtksys/SystemInformation.cxx: In
member function 'void
vtksys::{anonymous}::SymbolProperties::Initialize(void*)':
/«BUILDDIR»/vtk6-6.1.0+dfsg/Utilities/KWSys/vtksys/SystemInformation.cxx:1487:3:
error: 'Dl_info' was not declared in this scope
Dl_info info;
^
/«BUILDDIR»/vtk6-6.1.0+dfsg/Utilities/KWSys/vtksys/SystemInformation.cxx:1487:11:
error: expected ';' before 'info'
Dl_info info;
^
/«BUILDDIR»/vtk6-6.1.0+dfsg/Utilities/KWSys/vtksys/SystemInformation.cxx:1488:34:
error: 'info' was not declared in this scope
int ierr=dladdr(this-Address,info);
^
/«BUILDDIR»/vtk6-6.1.0+dfsg/Utilities/KWSys/vtksys/SystemInformation.cxx:1488:38:
error: 'dladdr' was not declared in this scope
int ierr=dladdr(this-Address,info);
^
/«BUILDDIR»/vtk6-6.1.0+dfsg/Utilities/KWSys/vtksys/SystemInformation.cxx: In
static member function 'static std::string
vtksys::SystemInformationImplementation::GetProgramStack(int, int)':
/«BUILDDIR»/vtk6-6.1.0+dfsg/Utilities/KWSys/vtksys/SystemInformation.cxx:3640:41:
error: 'backtrace' was not declared in this scope
int nFrames=backtrace(stackSymbols,256);
^
Utilities/KWSys/vtksys/CMakeFiles/vtksys.dir/build.make:333: recipe for
target 'Utilities/KWSys/vtksys/CMakeFiles/vtksys.dir/SystemInformation.cxx.o'
failed
make[4]: ***
[Utilities/KWSys/vtksys/CMakeFiles/vtksys.dir/SystemInformation.cxx.o] Error 1
make[4]: Leaving directory '/«BUILDDIR»/vtk6-6.1.0+dfsg/debian/build'
CMakeFiles/Makefile2:333: recipe for target
'Utilities/KWSys/vtksys/CMakeFiles/vtksys.dir/all' failed
make[3]: *** [Utilities/KWSys/vtksys/CMakeFiles/vtksys.dir/all] Error 2
See the full build logs at
https://buildd.debian.org/status/package.php?p=vtk6
Cheers,
Julien
signature.asc
Description: Digital signature
---End Message---
---BeginMessage---
Source: vtk6
Source-Version: 6.1.0+dfsg-2
We believe that the bug you reported is fixed in the latest version of
vtk6, 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 748...@bugs.debian.org,
and the maintainer will reopen the bug report if
Bug#711616: marked as done (libtest-refcount-perl: FTBFS with perl 5.18: test failures)
Your message dated Sun, 18 May 2014 13:20:07 +
with message-id e1wm10z-0002b6...@franck.debian.org
and subject line Bug#711616: fixed in libtest-refcount-perl 0.07-2
has caused the Debian Bug report #711616,
regarding libtest-refcount-perl: FTBFS with perl 5.18: test failures
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.)
--
711616: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=711616
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
---BeginMessage---
Source: libtest-refcount-perl
Version: 0.07-1
Severity: important
User: debian-p...@lists.debian.org
Usertags: perl-5.18-transition
Tags: sid jessie
This package FTBFS with perl 5.18 from experimental (in a clean sbuild
session):
dh_auto_test
t/00use.t ... ok
t/01count.t .
Failed 4/8 subtests
t/02one.t ...
Failed 1/3 subtests
t/03weak.t ..
Failed 2/2 subtests
t/04reftypes.t .. ok
t/99pod.t ... ok
Test Summary Report
---
t/01count.t (Wstat: 11 Tests: 4 Failed: 0)
Non-zero wait status: 11
Parse errors: Bad plan. You planned 8 tests but ran 4.
t/02one.t (Wstat: 11 Tests: 2 Failed: 0)
Non-zero wait status: 11
Parse errors: Bad plan. You planned 3 tests but ran 2.
t/03weak.t(Wstat: 11 Tests: 0 Failed: 0)
Non-zero wait status: 11
Parse errors: Bad plan. You planned 2 tests but ran 0.
Files=6, Tests=14, 1 wallclock secs ( 0.03 usr 0.03 sys + 0.24 cusr 0.03
csys = 0.33 CPU)
Result: FAIL
--
Dominic Hargreaves | http://www.larted.org.uk/~dom/
PGP key 5178E2A5 from the.earth.li (keyserver,web,email)
---End Message---
---BeginMessage---
Source: libtest-refcount-perl
Source-Version: 0.07-2
We believe that the bug you reported is fixed in the latest version of
libtest-refcount-perl, 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 711...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
gregor herrmann gre...@debian.org (supplier of updated libtest-refcount-perl
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, 18 May 2014 14:57:48 +0200
Source: libtest-refcount-perl
Binary: libtest-refcount-perl
Architecture: source all
Version: 0.07-2
Distribution: unstable
Urgency: low
Maintainer: Debian Perl Group pkg-perl-maintain...@lists.alioth.debian.org
Changed-By: gregor herrmann gre...@debian.org
Description:
libtest-refcount-perl - Perl module to assert reference counts
Closes: 711616
Changes:
libtest-refcount-perl (0.07-2) unstable; urgency=low
.
[ Ansgar Burchardt ]
* debian/control: Convert Vcs-* fields to Git.
.
[ gregor herrmann ]
* debian/control: update {versioned,alternative} (build) dependencies.
.
[ Salvatore Bonaccorso ]
* Change search.cpan.org based URIs to metacpan.org based URIs
.
[ Axel Beckert ]
* debian/copyright: migrate pre-1.0 format to 1.0 using cme fix dpkg-
copyright
.
[ gregor herrmann ]
* Make build dependency and Suggests on libdevel-findref-perl versioned.
(Closes: #711616)
* Update years of packaging copyright.
* Move Module::Build from Build-Depends-Indep to Build-Depends.
* Declare compliance with Debian Policy 3.9.5.
Checksums-Sha1:
c71bc6ef0d39cfd09428c50905754c57fb4c75f9 2319 libtest-refcount-perl_0.07-2.dsc
205c904ff77b2f3fabccbbd4e991eb1bb10a2d3d 2436
libtest-refcount-perl_0.07-2.debian.tar.xz
d5b37a363247743c51ee2e3f0bbc5aae87526ee6 10706
libtest-refcount-perl_0.07-2_all.deb
Checksums-Sha256:
d842c51c4c504bdd09b0e3caaffce27ce2cb6ddd1d9f860eefd14ac5637bf4bf 2319
libtest-refcount-perl_0.07-2.dsc
0d75b45439a043a9e0825f188a40924064519ca1ba98cfe7e96b8d1f7ab59770 2436
libtest-refcount-perl_0.07-2.debian.tar.xz
fcaeaecb6375debce2296c005ad0a959debb2a36224fcdf510d312ecf1f3f92d 10706
libtest-refcount-perl_0.07-2_all.deb
Files:
a47925c3c3174ec7dd05617b4a7d42dd 10706 perl optional
libtest-refcount-perl_0.07-2_all.deb
46e356ce2ae109e76689e6fd40ebc22c 2319 perl optional
libtest-refcount-perl_0.07-2.dsc
7cba7502897af634c37994d736e56208 2436 perl optional
libtest-refcount-perl_0.07-2.debian.tar.xz
-BEGIN PGP SIGNATURE-
Version: GnuPG v1
Bug#719835: marked as done (libdevel-findref-perl: crash in XS_Devel__FindRef_find_ on Perl 5.18)
Your message dated Sun, 18 May 2014 13:19:47 + with message-id e1wm10f-0002uh...@franck.debian.org and subject line Bug#719835: fixed in libdevel-findref-perl 1.430-1 has caused the Debian Bug report #719835, regarding libdevel-findref-perl: crash in XS_Devel__FindRef_find_ on Perl 5.18 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.) -- 719835: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=719835 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Source: libtest-refcount-perl Version: 0.07-1 Severity: important User: debian-p...@lists.debian.org Usertags: perl-5.18-transition Tags: sid jessie This package FTBFS with perl 5.18 from experimental (in a clean sbuild session): dh_auto_test t/00use.t ... ok t/01count.t . Failed 4/8 subtests t/02one.t ... Failed 1/3 subtests t/03weak.t .. Failed 2/2 subtests t/04reftypes.t .. ok t/99pod.t ... ok Test Summary Report --- t/01count.t (Wstat: 11 Tests: 4 Failed: 0) Non-zero wait status: 11 Parse errors: Bad plan. You planned 8 tests but ran 4. t/02one.t (Wstat: 11 Tests: 2 Failed: 0) Non-zero wait status: 11 Parse errors: Bad plan. You planned 3 tests but ran 2. t/03weak.t(Wstat: 11 Tests: 0 Failed: 0) Non-zero wait status: 11 Parse errors: Bad plan. You planned 2 tests but ran 0. Files=6, Tests=14, 1 wallclock secs ( 0.03 usr 0.03 sys + 0.24 cusr 0.03 csys = 0.33 CPU) Result: FAIL -- Dominic Hargreaves | http://www.larted.org.uk/~dom/ PGP key 5178E2A5 from the.earth.li (keyserver,web,email) ---End Message--- ---BeginMessage--- Source: libdevel-findref-perl Source-Version: 1.430-1 We believe that the bug you reported is fixed in the latest version of libdevel-findref-perl, 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 719...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. gregor herrmann gre...@debian.org (supplier of updated libdevel-findref-perl 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, 18 May 2014 14:48:02 +0200 Source: libdevel-findref-perl Binary: libdevel-findref-perl Architecture: source amd64 Version: 1.430-1 Distribution: unstable Urgency: medium Maintainer: Debian Perl Group pkg-perl-maintain...@lists.alioth.debian.org Changed-By: gregor herrmann gre...@debian.org Description: libdevel-findref-perl - Perl module to find variables referring to an object Closes: 719835 Changes: libdevel-findref-perl (1.430-1) unstable; urgency=medium . * Team upload. * New upstream release. Fixes crash in XS_Devel__FindRef_find_ on Perl 5.18. (Closes: #719835) * Update years of upstream copyright. * Update license stanzas in debian/copyright. * Add a patch to fix a typo in the POD. * Declare compliance with Debian Policy 3.9.5. Checksums-Sha1: d1189d46115c42166dfbd11cd939ac9e07b2a0a5 2243 libdevel-findref-perl_1.430-1.dsc 7cb8eb08e933825e67a1f7e334e656f9400d4633 8681 libdevel-findref-perl_1.430.orig.tar.gz 64fec2b6eb3f8e7ca31659943e6b0324562a7889 2900 libdevel-findref-perl_1.430-1.debian.tar.xz 7f1b39f2778e3971fc277d2b03a25740fdf9f20d 17678 libdevel-findref-perl_1.430-1_amd64.deb Checksums-Sha256: 4e1d435af0ec7a737b1c7b05db540d6d43ed97f626db94c0a9af401e8599b5dd 2243 libdevel-findref-perl_1.430-1.dsc 20548c4854a05ff2251fb477285135e0b466312a1765a17435e2a23f93f2907e 8681 libdevel-findref-perl_1.430.orig.tar.gz df41ff19fc90d0742289f6a034bb7b9c88742ea8cbc2fd6a7e2f2d2c060073d2 2900 libdevel-findref-perl_1.430-1.debian.tar.xz 64af5d9716a41d07ce735cb55b15b31782f3443c0a1f65047d25b1d9f19d17af 17678 libdevel-findref-perl_1.430-1_amd64.deb Files: 9b65bd310cfc65782631b648989610d8 17678 perl optional libdevel-findref-perl_1.430-1_amd64.deb 54f063c3c2126d38e13e796f1afb4bd7 2243 perl optional libdevel-findref-perl_1.430-1.dsc 7dfc0ba8d8bfc798be8109ab82d0315b 8681 perl optional libdevel-findref-perl_1.430.orig.tar.gz bd859b37e78b95cb2b376c40aeef629a 2900 perl optional libdevel-findref-perl_1.430-1.debian.tar.xz -BEGIN PGP SIGNATURE- Version: GnuPG v1 iQJrBAEBCgBVBQJTeKxCThSAAB0AKGlzc3Vlci1mcHJAZ3BnLmNvbW9kby5w
Bug#739460: openscenegraph: diff for NMU version 3.2.0~rc1-5.1
On 18.05.2014 09:00, Manuel A. Fernandez Montecelo wrote:
2014-05-18 12:10 GMT+01:00 Reinhard Tartler siret...@tauware.de:
So, can you please remove that change in the NMU, if you want to keep
the NMU at all?
Sure, I've just canceled the NMU.
Thanks.
From my side, I have no objection that the NMU goes ahead if it
contains only the fix for libav. I don't know if Alberto has any
objection or plans to fix this himself, so please wait at least until
20th for his reply.
No problem.
In this case, I'm building openscenegraph with only the libav issue
(#739460) fixed to DELAYED/2-days to give Alberto time to the 20th to
react to this. Updated debdiff is attached to this email.
Best,
Reinhard
diff -Nru openscenegraph-3.2.0~rc1/debian/changelog
openscenegraph-3.2.0~rc1/debian/changelog
--- openscenegraph-3.2.0~rc1/debian/changelog 2014-04-10 15:42:37.0
-0400
+++ openscenegraph-3.2.0~rc1/debian/changelog 2014-05-18 09:24:46.0
-0400
@@ -1,3 +1,11 @@
+openscenegraph (3.2.0~rc1-5.1) unstable; urgency=low
+
+ * Non-maintainer upload.
+ * Add libav10.patch by Anton Khirnov and compile against Libav10
+(Closes: #739460)
+
+ -- Reinhard Tartler siret...@tauware.de Sat, 17 May 2014 16:52:38 -0400
+
openscenegraph (3.2.0~rc1-5) unstable; urgency=medium
* Updated standards to 3.9.5. No changes required.
diff -Nru openscenegraph-3.2.0~rc1/debian/control
openscenegraph-3.2.0~rc1/debian/control
--- openscenegraph-3.2.0~rc1/debian/control 2014-04-10 15:42:09.0
-0400
+++ openscenegraph-3.2.0~rc1/debian/control 2014-05-17 16:55:22.0
-0400
@@ -26,6 +26,7 @@
libavcodec-dev,
libswscale-dev,
libavdevice-dev,
+ libavresample-dev,
libqt4-dev,
libqt4-opengl-dev,
librsvg2-dev,
diff -Nru openscenegraph-3.2.0~rc1/debian/patches/libav10.patch
openscenegraph-3.2.0~rc1/debian/patches/libav10.patch
--- openscenegraph-3.2.0~rc1/debian/patches/libav10.patch 1969-12-31
19:00:00.0 -0500
+++ openscenegraph-3.2.0~rc1/debian/patches/libav10.patch 2014-05-17
16:49:45.0 -0400
@@ -0,0 +1,228 @@
+From: an...@khirnov.net
+To: 739...@bugs.debian.org
+Subject: Re: FTBFS with libav10
+Date: Mon, 03 Mar 2014 07:37:18 +0100
+
+Updated by Reinhard Tartler at Wed Apr 2 21:58:34 EDT 2014: Link against
libavresample
+
+--- a/OpenSceneGraph/src/osgPlugins/ffmpeg/FFmpegDecoderAudio.cpp
b/OpenSceneGraph/src/osgPlugins/ffmpeg/FFmpegDecoderAudio.cpp
+@@ -12,24 +12,16 @@
+
+ namespace osgFFmpeg {
+
+-static int decode_audio(AVCodecContext *avctx, int16_t *samples,
+- int *frame_size_ptr,
+- const uint8_t *buf, int buf_size)
++static int decode_audio(AVCodecContext *avctx, AVFrame *frame,
++const uint8_t *buf, int buf_size)
+ {
+-#if LIBAVCODEC_VERSION_MAJOR = 53 || (LIBAVCODEC_VERSION_MAJOR==52
LIBAVCODEC_VERSION_MINOR=32)
+-
+-// following code segment copied from ffmpeg's avcodec_decode_audio2()
+-// implementation to avoid warnings about deprecated function usage.
++int got_output;
+ AVPacket avpkt;
+ av_init_packet(avpkt);
+ avpkt.data = const_castuint8_t *(buf);
+ avpkt.size = buf_size;
+
+-return avcodec_decode_audio3(avctx, samples, frame_size_ptr, avpkt);
+-#else
+-// fallback for older versions of ffmpeg that don't have
avcodec_decode_audio3.
+-return avcodec_decode_audio2(avctx, samples, frame_size_ptr, buf,
buf_size);
+-#endif
++return avcodec_decode_audio4(avctx, frame, got_output, avpkt);
+ }
+
+
+@@ -40,12 +32,17 @@ FFmpegDecoderAudio::FFmpegDecoderAudio(P
+ m_context(0),
+ m_packet_data(0),
+ m_bytes_remaining(0),
+-m_audio_buffer((AVCODEC_MAX_AUDIO_FRAME_SIZE * 3) / 2),
++m_audio_buffer((192000 * 3) / 2),
+ m_audio_buf_size(0),
+ m_audio_buf_index(0),
+ m_end_of_stream(false),
+ m_paused(true),
+-m_exit(false)
++m_exit(false),
++avr(NULL),
++resample_format(-1),
++resample_rate(0),
++resample_layout(0),
++frame(NULL)
+ {
+
+ }
+@@ -72,7 +69,7 @@ void FFmpegDecoderAudio::open(AVStream *
+
+ m_frequency = m_context-sample_rate;
+ m_nb_channels = m_context-channels;
+-switch (m_context-sample_fmt)
++switch (av_get_planar_sample_fmt(m_context-sample_fmt))
+ {
+ case AV_SAMPLE_FMT_NONE:
+ throw std::runtime_error(invalid audio format
AV_SAMPLE_FMT_NONE);
+@@ -95,7 +92,7 @@ void FFmpegDecoderAudio::open(AVStream *
+ }
+
+ // Check stream sanity
+-if (m_context-codec_id == CODEC_ID_NONE)
++if (m_context-codec_id == AV_CODEC_ID_NONE)
+ throw std::runtime_error(invalid audio codec);;
+
+ // Find the decoder for the audio stream
+@@ -111,6 +108,10 @@ void FFmpegDecoderAudio::open(AVStream *
+ // Open codec
+ if
Bug#748546: marked as done (devede: depends on libavcodec-extra-54, which is going away)
Your message dated Sun, 18 May 2014 13:48:40 + with message-id e1wm1sc-0005wt...@franck.debian.org and subject line Bug#748546: fixed in devede 3.23.0-13-gbfd73f3-2 has caused the Debian Bug report #748546, regarding devede: depends on libavcodec-extra-54, which is going away 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.) -- 748546: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=748546 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- package: devede severity: serious version: 3.23.0-13-gbfd73f3-1 Hi, It seems devede depends on libavcodec-extra-54, which is going away with the libav transition. This wasn't picked up by the transition tracker 'libav10' (because there is no build-dep on libav), but the 'auto-libav' tracker shows it. https://release.debian.org/transitions/html/auto-libav.html Cheers, Ivo ---End Message--- ---BeginMessage--- Source: devede Source-Version: 3.23.0-13-gbfd73f3-2 We believe that the bug you reported is fixed in the latest version of devede, 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 748...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Reinhard Tartler siret...@tauware.de (supplier of updated devede 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, 18 May 2014 08:04:01 -0400 Source: devede Binary: devede Architecture: source all Version: 3.23.0-13-gbfd73f3-2 Distribution: unstable Urgency: low Maintainer: Debian Multimedia Maintainers pkg-multimedia-maintain...@lists.alioth.debian.org Changed-By: Reinhard Tartler siret...@tauware.de Description: devede - simple application to create Video DVDs Closes: 748546 Changes: devede (3.23.0-13-gbfd73f3-2) unstable; urgency=low . * Depend on libavcodec-extra (Closes: #748546) Checksums-Sha1: 2ccaae69c1c167172840504031ee6b5f59d7f233 1933 devede_3.23.0-13-gbfd73f3-2.dsc 3a6bd2c7c821763c27bbfb0256de1b44ff845afa 2248116 devede_3.23.0-13-gbfd73f3.orig.tar.xz 9141cea92ec367113755463a9d6a4f570fe0fbf3 9084 devede_3.23.0-13-gbfd73f3-2.debian.tar.xz a62bf43c1e70f2e1ea0cfe5eaee3bde0f2ea26f2 1977184 devede_3.23.0-13-gbfd73f3-2_all.deb Checksums-Sha256: 0990e35a4c19069945d353b67937eeb1d9ad285db17f5b64faec544c74ea61d9 1933 devede_3.23.0-13-gbfd73f3-2.dsc f84ea05de88d3e184f733eae5f30355e3f61eb348733be4c21e290615ee75c24 2248116 devede_3.23.0-13-gbfd73f3.orig.tar.xz e66cc6092ec7ac90e6a6fbcc5e0f1b9cfedaf2a30f9613a89ec6196dc847c6fe 9084 devede_3.23.0-13-gbfd73f3-2.debian.tar.xz 5f572a738445fa97d495d919c0cb7ead691b1ee11925ce363548a37333483a7e 1977184 devede_3.23.0-13-gbfd73f3-2_all.deb Files: a95222accc633e1814bcb6f88290e8d4 1977184 video optional devede_3.23.0-13-gbfd73f3-2_all.deb 75d631131faab2335d3a53200a8935dc 1933 video optional devede_3.23.0-13-gbfd73f3-2.dsc 062de6a6775a2381f1bfbc244b3e26e3 2248116 video optional devede_3.23.0-13-gbfd73f3.orig.tar.xz 6cdbfd85774d84b61e14c0818e1455e4 9084 video optional devede_3.23.0-13-gbfd73f3-2.debian.tar.xz -BEGIN PGP SIGNATURE- Version: GnuPG v1 iQGcBAEBCAAGBQJTeLa8AAoJEIuAbIZKeKRFcbcL/2UVVLCLw/ZQzALuuuIcO6uS q2gYuAaVH23GN4matXTuQQVS7ITid28w2DrJCicxMYXn9qf1uDthWa2rHtlMy8lT mkvx8vH0acP1C2oOG6HQ+WfGhr7h/n4rAL94k/v9TQBbIj0G/E8mOdpaFiQtFhnP Yvl5JdMZAwM9f297Yy+AKmRFi7J5sdWGkZfJQAlpOuuuGFwGb4HclPDu1/3/02CY NLc8EwApQSkKMHpjBdjQBLx74M5YOc6UgTlZXd3cYn6w2p9qIpVuPs8dbZiTfIeT E256DNQVgX+FQLClLdFPCmf5ntftPD1BBoeCek/2uRtiuVLfoiakbCDnyo3j2hvJ IVFR3aE1WxPWY4BZkLFZeg8LZBkNzmJo6Mer/3nS5oe6l1QCMTflMpcacudG6JT2 h5JKmDxleHzYp0gBPJ/UkI3OlWRpw9wxd0odizVhKxPmyHobnfFt1KUp/QWmvKTJ Gof6sfZ0WbpsGgJZ27/tELXkPkmgiQ2lTEqRSMb54A== =hCbH -END PGP SIGNATUREEnd Message---
Processed: retitle 739433 to performous: FTBFS with libav10
Processing commands for cont...@bugs.debian.org: retitle 739433 performous: FTBFS with libav10 Bug #739433 [performous] FTBFS with libav10 Changed Bug title to 'performous: FTBFS with libav10' from 'FTBFS with libav10' thanks Stopping processing here. Please contact me if you need assistance. -- 739433: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=739433 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: retitle 739426 to kino: FTBFS with libav10
Processing commands for cont...@bugs.debian.org: retitle 739426 kino: FTBFS with libav10 Bug #739426 [kino] FTBFS with libav10 Changed Bug title to 'kino: FTBFS with libav10' from 'FTBFS with libav10' thanks Stopping processing here. Please contact me if you need assistance. -- 739426: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=739426 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#748564: FTBFS: Failed to resolve artifact.
Package: jarjar-maven-plugin Version: 1.9-1 Severity: serious Usertags: goto-cc During a rebuild of all packages in a clean sid chroot (and cowbuilder+pbuilder) the build failed with the following error. [...] Missing: -- 1) org.ow2.asm:asm:jar:debian [...] 2) org.ow2.asm:asm-commons:jar:debian [...] -- 2 required artifacts are missing. [...] /usr/share/cdbs/1/class/maven.mk:87: recipe for target 'mvn-build' failed make: *** [mvn-build] Error 1 dpkg-buildpackage: error: debian/rules build gave error exit status 2 The full build log is attached. Best, Michael jarjar-maven-plugin-build-log.txt.gz Description: application/gunzip pgpfYxg2Nd0UE.pgp Description: PGP signature
Processed: close already fixed issues, adjust severities
Processing commands for cont...@bugs.debian.org: severity 748024 important Bug #748024 [gcc-4.9-plugin-dev] gcc-4.9-plugin-dev: gcc plugins can not build Severity set to 'important' from 'serious' close 747526 Bug #747526 [src:gcc-4.9] src:gcc-4.9: FTBFS on sparc64: update symbols Marked Bug as done close 742616 Bug #742616 [gcc-4.9] Mark libraries packages as multi arch when with_multiarch_lib=yes Marked Bug as done thanks Stopping processing here. Please contact me if you need assistance. -- 742616: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=742616 747526: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=747526 748024: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=748024 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 (with 1 errors): Reopen
Processing commands for cont...@bugs.debian.org:
reopen 746120
Bug #746120 {Done: Daniel Pocock dan...@pocock.pro} [src:jssip] jssip: FTBFS:
make[2]: java: Command not found
Bug reopened
Ignoring request to alter fixed versions of bug #746120 to the same values
previously set
owner !
Unknown command or malformed arguments to command.
thanks
Stopping processing here.
Please contact me if you need assistance.
--
746120: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=746120
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#748569: libllvm3.5: Missing symlink to libLLVM-3.5.so after install
Package: libllvm3.5 Version: 1:3.5~svn209039-1 Severity: grave Justification: causes non-serious data loss Upgrading to this version caused X Windows to crash as soon as any attempt to run an OpenGL application was made. It's possible that people could lose data when X crashes this way that they really cannot afford to lose, so maybe the severity should be changed to critical. After some investigation, I found out some extra details that I can report: 1) My desktop manager (lightdm, running Xfce on Sid) respawned and now attempts to run OpenGL programs no longer crashed X, but they failed to run. The xsession-errors log revealed that acceleration was not enabled. 2) I use the radeonsi Mesa driver for acceleration, and this requires the glamor 2D driver. The Xorg.0.log file showed that the glamor module could not locate a file -- libLLVM-3.5.0.so.1: [ 31667.925] (EE) AIGLX error: dlopen of /usr/lib/x86_64-linux-gnu/dri/swrast_dri.so failed (libLLVM-3.5.0.so.1: cannot open shared object file: No such file or directory) 3) The contents of package libllvm3.5 do seem to include a symlink matching the name of the missing file: # dpkg-deb -c libllvm3.5_1%3a3.5~svn209039-1_amd64.deb [...] -rw-r--r-- root/root 30171784 2014-05-17 08:06 ./usr/lib/x86_64-linux-gnu/libLLVM-3.5.so.1 [...] lrwxrwxrwx root/root 0 2014-05-17 08:05 ./usr/lib/x86_64-linux-gnu/libLLVM-3.5.0.so.1 - libLLVM-3.5.so This symlink is NOT present on my system after libllvm3.5 is installed by my package manager. 4) I thought another LLVM 3.5 package might contain the file that the symlink was supposed to link to, and I found that in llvm-3.5-dev: # dpkg-deb -c llvm-3.5-dev_1%3a3.5~svn209039-1_amd64.deb | grep \.so -rw-r--r-- root/root 30171656 2014-05-17 08:06 ./usr/lib/llvm-3.5/lib/libLLVM-3.5.so [...] lrwxrwxrwx root/root 0 2014-05-17 08:05 ./usr/lib/llvm-3.5/lib/libLLVM-3.5.0.so - ../../x86_64-linux-gnu/libLLVM-3.5.0.so.1 (Notice that libLLVM-3.5.0.so is supposed to be a symlink to the other symlink which ends up not being present on my system after the upgrade.) 5) Inspecting /var/log/dpkg.log, it would seem that libllvm3.5 installs before any of the other LLVM-related packages. At that time, without llvm-3.5-dev present to provide libLLVM-3.5.so, it looks like the symlink gets dropped and does not get installed. 6) As a workaround, I manually created a different symlink: # cd /usr/lib/x86_64-linux-gnu # ln -s -T libLLVM-3.5.so.1 libLLVM-3.5.0.so.1 This resulted in a fully working system, according to all of the testing I've tried so far. I do not know if this is the correct solution, but I just thought I'd mention it, since it might allow you to package libllvm3.5 in such a way that it installs correctly without depending on other packages being installed first. In any case it is very bad if someone has a previous LLVM installed with working acceleration, and then upgrading to a new version sets them up so that the moment they try to run an OpenGL program the X server dies on them! Fortunately, I am using software not available in Debian repositories (like glamor) in order to test the upstream radeonsi support (I need this for my Radeon HD 7850 GPU, which requires radeonsi for acceleration), so few other people will be affected by this bug right now. HTH, Dave Witbrodt -- System Information: Debian Release: jessie/sid APT prefers unstable APT policy: (990, 'unstable'), (350, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 3.14.4-1+dwlocal1 (SMP w/4 CPU cores; PREEMPT) Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages libllvm3.5 depends on: ii libc6 2.18-6 ii libedit2 3.1-20140213-1 ii libffi63.1~rc1+r3.0.13-12 ii libgcc11:4.9.0-3 ii libstdc++6 4.9.0-3 ii libtinfo5 5.9+20140118-1 ii multiarch-support 2.18-6 libllvm3.5 recommends no packages. libllvm3.5 suggests no packages. -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: reassign 747502 to libcatalyst-plugin-subrequest-perl
Processing commands for cont...@bugs.debian.org: reassign 747502 libcatalyst-plugin-subrequest-perl 0.20 Bug #747502 [libcatalyst-modules-perl] FTBFS: test failure in Catalyst-Plugin-SubRequest Bug reassigned from package 'libcatalyst-modules-perl' to 'libcatalyst-plugin-subrequest-perl'. No longer marked as found in versions libcatalyst-modules-perl/47. Ignoring request to alter fixed versions of bug #747502 to the same values previously set Bug #747502 [libcatalyst-plugin-subrequest-perl] FTBFS: test failure in Catalyst-Plugin-SubRequest There is no source info for the package 'libcatalyst-plugin-subrequest-perl' at version '0.20' with architecture '' Unable to make a source version for version '0.20' Marked as found in versions 0.20. thanks Stopping processing here. Please contact me if you need assistance. -- 747502: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=747502 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: closing 747502
Processing commands for cont...@bugs.debian.org: close 747502 0.20-1 Bug #747502 [libcatalyst-plugin-subrequest-perl] FTBFS: test failure in Catalyst-Plugin-SubRequest Marked as fixed in versions libcatalyst-plugin-subrequest-perl/0.20-1. Bug #747502 [libcatalyst-plugin-subrequest-perl] FTBFS: test failure in Catalyst-Plugin-SubRequest Marked Bug as done thanks Stopping processing here. Please contact me if you need assistance. -- 747502: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=747502 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#747502: closing 747502
close 747502 0.20-1 thanks Catalyst-Plugin-SubRequest is now in a separate package, libcatalyst-plugin-subrequest-perl. It contains a patch that fixes the build faiilure. Cheers, dam -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#748574: 3.14.1 does not boot on Dell server
Package: src:linux Version: 3.14.4-1 Severity: critical When trying to boot 3.14.1 It stops at the first line booting the kernel, no other message, even when trying to start without quiet. PS : since I access it through an iDrac kvm which does not transmit arrow keys nor Ctrl keys, grub is about not usable, making tests very difficult for me. Before automatically retrieved info here is the dmidecode # dmidecode 2.12 SMBIOS 2.6 present. 63 structures occupying 2953 bytes. Table at 0xBF79C000. Handle 0xDA00, DMI type 218, 11 bytes OEM-specific Type Header and Data: DA 0B 00 DA B2 00 17 00 0E 20 00 Handle 0x, DMI type 0, 24 bytes BIOS Information Vendor: Dell Inc. Version: 1.5.2 Release Date: 10/18/2010 Address: 0xF Runtime Size: 64 kB ROM Size: 4096 kB Characteristics: ISA is supported PCI is supported PNP is supported BIOS is upgradeable BIOS shadowing is allowed Boot from CD is supported Selectable boot is supported EDD is supported Japanese floppy for Toshiba 1.2 MB is supported (int 13h) 5.25/360 kB floppy services are supported (int 13h) 5.25/1.2 MB floppy services are supported (int 13h) 3.5/720 kB floppy services are supported (int 13h) 8042 keyboard services are supported (int 9h) Serial services are supported (int 14h) CGA/mono video services are supported (int 10h) ACPI is supported USB legacy is supported BIOS boot specification is supported Function key-initiated network boot is supported Targeted content distribution is supported BIOS Revision: 1.5 Handle 0x0100, DMI type 1, 27 bytes System Information Manufacturer: Dell Inc. Product Name: PowerEdge R210 Version: Not Specified Serial Number: DJKWZ4J UUID: 4C4C4544-004A-4B10-8057-C4C04F5A344A Wake-up Type: Power Switch SKU Number: Not Specified Family: Not Specified Handle 0x0200, DMI type 2, 9 bytes Base Board Information Manufacturer: Dell Inc. Product Name: 05KX61 Version: A01 Serial Number: ..CN708210B901A8. Asset Tag: Not Specified Handle 0x0300, DMI type 3, 21 bytes Chassis Information Manufacturer: Dell Inc. Type: Rack Mount Chassis Lock: Present Version: Not Specified Serial Number: DJKWZ4J Asset Tag: Not Specified Boot-up State: Safe Power Supply State: Safe Thermal State: Safe Security Status: Unknown OEM Information: 0x Height: 1 U Number Of Power Cords: Unspecified Contained Elements: 0 Handle 0x0400, DMI type 4, 40 bytes Processor Information Socket Designation: CPU1 Type: Central Processor Family: Xeon Manufacturer: Intel ID: E5 06 01 00 FF FB EB BF Signature: Type 0, Family 6, Model 30, Stepping 5 Flags: FPU (Floating-point unit on-chip) VME (Virtual mode extension) DE (Debugging extension) PSE (Page size extension) TSC (Time stamp counter) MSR (Model specific registers) PAE (Physical address extension) MCE (Machine check exception) CX8 (CMPXCHG8 instruction supported) APIC (On-chip APIC hardware supported) SEP (Fast system call) MTRR (Memory type range registers) PGE (Page global enable) MCA (Machine check architecture) CMOV (Conditional move instruction supported) PAT (Page attribute table) PSE-36 (36-bit page size extension) CLFSH (CLFLUSH instruction supported) DS (Debug store) ACPI (ACPI supported) MMX (MMX technology supported) FXSR (FXSAVE and FXSTOR instructions supported) SSE (Streaming SIMD extensions) SSE2 (Streaming SIMD extensions 2) SS (Self-snoop) HTT (Multi-threading) TM (Thermal monitor supported) PBE (Pending break enabled) Version: Intel(R) Xeon(R) CPU L3426 @ 1.87GHz Voltage: 1.2 V External Clock: 4266 MHz Max Speed: 3600 MHz Current Speed: 1866 MHz Status: Populated, Enabled Upgrade: Socket LGA1366 L1 Cache Handle: 0x0700 L2 Cache Handle: 0x0701 L3 Cache Handle: 0x0702 Serial Number: Not Specified Asset Tag: Not Specified Part Number: Not Specified Core
Bug#721776: marked as done (libprelude: FTBFS on kfreebsd (FAIL: test-poll))
Your message dated Sun, 18 May 2014 15:35:57 + with message-id e1wm381-zz...@franck.debian.org and subject line Bug#721776: fixed in libprelude 1.0.0-11.1 has caused the Debian Bug report #721776, regarding libprelude: FTBFS on kfreebsd (FAIL: test-poll) 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.) -- 721776: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=721776 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Source: libprelude Version: 1.0.0-11 Severity: serious Justification: fails to build from source (but built successfully in the past) Control: block 712615 with -1 Hi, libprelude FTBFS on the kfreebsd buildds, see the build logs at https://buildd.debian.org/status/logs.php?pkg=libpreludever=1.0.0-11%2Bb1suite=sid Cheers, Julien signature.asc Description: Digital signature ---End Message--- ---BeginMessage--- Source: libprelude Source-Version: 1.0.0-11.1 We believe that the bug you reported is fixed in the latest version of libprelude, 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 721...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Maximiliano Curia m...@debian.org (supplier of updated libprelude package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Tue, 13 May 2014 15:44:03 +0200 Source: libprelude Binary: libprelude-dev libprelude2 libprelude2-dbg libprelude-perl python-prelude Architecture: source amd64 Version: 1.0.0-11.1 Distribution: unstable Urgency: medium Maintainer: Pierre Chifflier pol...@debian.org Changed-By: Maximiliano Curia m...@debian.org Description: libprelude-dev - Security Information Management System [ Development files ] libprelude-perl - Security Information Management System [ Base library ] libprelude2 - Security Information Management System [ Base library ] libprelude2-dbg - Security Information Management System [ Debug symbols ] python-prelude - Security Information Management System [ Base library ] Closes: 721776 Changes: libprelude (1.0.0-11.1) unstable; urgency=medium . * Non-maintainer upload. (Closes: #721776) * New patch: request_REUSEADDR_before_bind.patch. * New patch: test-poll_add_sleep_after_write.patch. Checksums-Sha1: f4a71ae532ff236edc20ab71f573622687136d10 2113 libprelude_1.0.0-11.1.dsc 62771169a2949740ac9bbf1d140696f1fb1af162 7772 libprelude_1.0.0-11.1.debian.tar.xz 1a5f4be963ec690570c38ee2409d1e36f33e5fa6 348780 libprelude-dev_1.0.0-11.1_amd64.deb 6b09d53dd504faf2b017c40112d35f5a9f26d7db 747180 libprelude2_1.0.0-11.1_amd64.deb 10a92b95406abe44572aadcd5c79979b5f87041f 3230386 libprelude2-dbg_1.0.0-11.1_amd64.deb 2029af2b0a6e1669005a3b86767ce88965bb10d3 596114 libprelude-perl_1.0.0-11.1_amd64.deb c109d042456a1f7277ae8b1f31c48c00e065d957 509764 python-prelude_1.0.0-11.1_amd64.deb Checksums-Sha256: 077d0ed90c3ea33310fa0c65f09db3d47cab01da3e566d244b96bf1f5abed4d4 2113 libprelude_1.0.0-11.1.dsc e9c5406d84fe37f79f136ece69df915ee234c64b9e9ddf86c6307d8ba761d05d 7772 libprelude_1.0.0-11.1.debian.tar.xz fe886bb1c89d556e98f5ee112bf92b2bdc749f44ef4b66aabd60457f144668e0 348780 libprelude-dev_1.0.0-11.1_amd64.deb 743d4176eb3ba6f50f0185c6fdfa35855b6f6e27e136d4419632df61bb0185d2 747180 libprelude2_1.0.0-11.1_amd64.deb 92d929c4cda1e498247e123b62530ee67b6fceb9747ad558b11408dff9ffc0d0 3230386 libprelude2-dbg_1.0.0-11.1_amd64.deb 97416fb22ee01e6ee7f2af03f84fcaf59df8a743ebab39e3016104c80f64c9cd 596114 libprelude-perl_1.0.0-11.1_amd64.deb 15801b5753f2018c32938055d2b5a0bdcf8358864a72ea79b85ad8beb02335ad 509764 python-prelude_1.0.0-11.1_amd64.deb Files: d99ba2c4685c80278a98065b9e1ae2a8 348780 libdevel extra libprelude-dev_1.0.0-11.1_amd64.deb b7ed12490f95861f09c7e83ea55fca2e 747180 libs extra libprelude2_1.0.0-11.1_amd64.deb 576df143f11d9ca5f63fef05dcb27903 3230386 debug extra libprelude2-dbg_1.0.0-11.1_amd64.deb 53a9131272c5ef18f543e0cead3b5693 596114 perl extra libprelude-perl_1.0.0-11.1_amd64.deb 3bc3870354ca42483bf75fa3858bc26d 509764 python extra python-prelude_1.0.0-11.1_amd64.deb fcb1005f9939dc08f172dd65dafcbdb3 2113 libs extra libprelude_1.0.0-11.1.dsc 1cd8093c2401000dcf654b985dd5e685
Bug#748584: ardour3 builds with too many parallel processes
Package: ardour3 Version: 3.5.380~dfsg-1 Severity: serious Hi, the package ardour3 doesn't respect parallel in DEB_BUILD_OPTIONS and builds with as many parallel processes as there are CPUs. This is not so helpful on a 16-core-machine which by purpose runs two buildds in parallel with 6 core per buildd. aba@lucatelli:~$ ps -fu buildd2 | grep cc1plus | wc -l 16 aba@lucatelli:~$ ps -fu buildd2 | grep sbuild buildd2 4534 3316 0 15:28 ?00:00:07 /usr/bin/perl /usr/bin/sbuild --apt-update --no-apt-upgrade --no-apt-distupgrade [...] ardour3_3.5.380~dfsg-1 ba@lucatelli:~$ grep DEB_BUILD ~buildd2/build/current-sid DEB_BUILD_OPTIONS=parallel=6 As per policy, package should not build parallel unless indicated by DEB_BUILD_OPTIONS, and then use that setting (or still not build parallel). Please fix this, this hurts the buildd infrastructure. Andi -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#748574: 3.14.1 does not boot on Dell server
Op 2014-05-18 om 17:29 schreef Erwan David: When trying to boot 3.14.1 It stops at the first line booting the kernel, no other message, even when trying to start without quiet. Did the PowerEdge R210 boot with previous Linux kernels? If yes, what is the last known good version? Please tell more about the installation of the 3.14.1 kernel. (Was it a fresh install? Was it a update? Was there enough disk space during the update?) Regards Geert Stappers PS : since I access it through an iDrac kvm which does not transmit arrow keys nor Ctrl keys, FWIW: I think that iDRAC kvm can transmit arrow keys and ConTRoL. I can't tell how, but it is very likely that such keys are supported. That those keys have special meaning on the admin machine, is something to cope / workaround with. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#692811: What's the plan with dvswitch regarding libav / liblivemedia
Hi, How are you doing? I'm writing you to check on the dvswitch package in debian. I noticed the call for help on http://grep.be/blog/en/computer/code/Call_for_help_for_DVswitch_maintenance/,which makes me wonder what this means regarding the two currently open RC bugs #747868 and #692811. Regarding the build failure against libav10, I guess all necessary patches are already in the upstream repository: https://alioth.debian.org/plugins/scmgit/cgi-bin/gitweb.cgi?p=dvswitch/dvswitch.git Do you plan to have an upload that fixes these two issues soon? Or do you think the package needs much more work than that, and should be removed from jessie for now? Thanks for working on the package and your timely reply. -- regards, Reinhard -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#748574: 3.14.1 does not boot on Dell server
Le 18/05/2014 18:30, Geert Stappers a écrit : Op 2014-05-18 om 17:29 schreef Erwan David: When trying to boot 3.14.1 It stops at the first line booting the kernel, no other message, even when trying to start without quiet. Did the PowerEdge R210 boot with previous Linux kernels? If yes, what is the last known good version? Yes, last running version is linux-image-3.13-1-amd64 3.13.10-1 Please tell more about the installation of the 3.14.1 kernel. (Was it a fresh install? Was it a update? Was there enough disk space during the update?) Just an upgrade through aptitude upgrade Regards Geert Stappers PS : since I access it through an iDrac kvm which does not transmit arrow keys nor Ctrl keys, FWIW: I think that iDRAC kvm can transmit arrow keys and ConTRoL. I can't tell how, but it is very likely that such keys are supported. That those keys have special meaning on the admin machine, is something to cope / workaround with. Thanks, I will investigate it, I suspect it might be a java problem (and I made a wishlist that we could navigate in menu with j/k) I just wanted to warn you that testing might be difficult for me. PS: I just see someone else with similar problem on debian-users, I give him the bug number. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#747131: marked as done (mupdf: build-depends on missing libv8-dev on powerpc and s390x)
Your message dated Sun, 18 May 2014 17:18:40 + with message-id e1wm4jq-0003wb...@franck.debian.org and subject line Bug#747131: fixed in mupdf 1.4-2 has caused the Debian Bug report #747131, regarding mupdf: build-depends on missing libv8-dev on powerpc and s390x 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.) -- 747131: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=747131 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- package: mupdf version: 1.4-1 severity: serious Hi, The latest mupdf upload can't be built on powerpc, s390x, sparc and hurd, as it depends on libv8-dev, which is missing on those architectures (libv8-3.14 doesn't build on any of them). Either the build-dependency should be removed, or the outdated binaries must be removed (by filing a removal bug against ftp.debian.org). Cheers, Ivo ---End Message--- ---BeginMessage--- Source: mupdf Source-Version: 1.4-2 We believe that the bug you reported is fixed in the latest version of mupdf, 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 747...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Kan-Ru Chen (陳侃如) kos...@debian.org (supplier of updated mupdf package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Mon, 19 May 2014 00:11:11 +0800 Source: mupdf Binary: libmupdf-dev mupdf mupdf-tools Architecture: source amd64 Version: 1.4-2 Distribution: unstable Urgency: medium Maintainer: Kan-Ru Chen (陳侃如) kos...@debian.org Changed-By: Kan-Ru Chen (陳侃如) kos...@debian.org Description: libmupdf-dev - development files for the MuPDF viewer mupdf - lightweight PDF viewer mupdf-tools - commmand line tools for the MuPDF viewer Closes: 747131 Changes: mupdf (1.4-2) unstable; urgency=medium . * Disable JavaScript support on powerpc, s390x and sparc. (Closes: #747131) Checksums-Sha1: 1bcf5cbd54335343a04a6e7e60b44d5451c7 2123 mupdf_1.4-2.dsc 468095609b94b473686d58fd6c6806b285acca11 24216 mupdf_1.4-2.debian.tar.xz 0daf521d285456051c8ba1914c42b661380381db 3171574 libmupdf-dev_1.4-2_amd64.deb b42ac883e36497e4b4bcd515c2b49a3191a0932c 3053670 mupdf_1.4-2_amd64.deb a9ad391ba6487e73944fbf503854652d4a2d26dd 3192364 mupdf-tools_1.4-2_amd64.deb Checksums-Sha256: 0081bf643798ba94111eae8130d6f438319d514d8006c7dbe056902d16eb545d 2123 mupdf_1.4-2.dsc 40fad5121bb513c8ea941604688f9e56d8f8158193584f3821bf21f6fa51ea14 24216 mupdf_1.4-2.debian.tar.xz 81e8f73b860f89543e9262255fb3ed975c1c2f0bd7187eccd2fc79dda5e66d98 3171574 libmupdf-dev_1.4-2_amd64.deb c7439fb740176d19df5d96624fbd88fdad134608f6e27c5ae1dbb6f259ff3fba 3053670 mupdf_1.4-2_amd64.deb e0fcf6182c65e4043d32af8aab4114f69e38f5562421c7ea3cc9365e2ecf1475 3192364 mupdf-tools_1.4-2_amd64.deb Files: c74a32fe2c68d0fd96f8673475c745bf 3171574 libdevel optional libmupdf-dev_1.4-2_amd64.deb c5c3cdd6543289aed1e8bab7e3e2e0cc 3053670 text optional mupdf_1.4-2_amd64.deb ce7f02f97e47e7e6118623218d7fd79f 3192364 text optional mupdf-tools_1.4-2_amd64.deb 0635a6ce6ad5cb927d8332ccb6ca8d04 2123 text optional mupdf_1.4-2.dsc 4583a2fb8c39763cfd8a1403f8b72c58 24216 text optional mupdf_1.4-2.debian.tar.xz -BEGIN PGP SIGNATURE- Version: GnuPG v1 iQIcBAEBCgAGBQJTeOjEAAoJEAo5NUq25X3hsQEP/R9lmv+l/Iy9vln4umfgURns Y1H4h9Ivl2PhIZx2gPJPwv7rE/dGPdctbAYqva8Ug+DZEsxRhYAwXzOb/BUMWTK7 CYIZ3+lHknWR7o3L5gd39IwjIQZYKnCoU0SXQjMSYi7VKHupP1IRn8MCso9V7Upk UdEsGNvkrNplDMLeWwKZpMpWL27PwpJHSr+SIkfKXRMrh1YlqbBA6DAao+uZRo5S TmFAUvqRJygYbldxpx9c2sn4WVYALqXfT6chUwVc2AWxHFvuyVnyF+9YQQ0Tu0em 1m/Fh/pRuVKf+UCqN/AnVTyXaZjvZvRVNhmXFZsl6q5jxSX0P02yFQfB/xdGZjQa v8ps/0tAKitOnHmCxeLuADwK01YhNPgFYrIFOZLp40CuhVU7GUctj7n3nPWCn12N ToiAyhagwWCsIZPPFG9UsQn//i4MBgM6US6NCwdr5BCLsKkcUh28qz/DRbs1YTrb kZjC7UH0y4ihF7WhKbJy2HUqF9s1TK4ChAsGzKrLZowRat2sjXVD1hTxAJxyd424 h67cb15WiEkF0Ow7GNLq6jlp9BxyCg6vnJUV6xn3kAthgOshXZ2hoxHIzsWIpwXC 5ameC6tr/NoEkTStBQZe4Gee0N+k+D9qzDAoD9oYFl9hnIfe6zpDnFdl3jZP3nZp 7pJYkXQ9w1R+eUYHAw37 =gq2F -END PGP SIGNATUREEnd Message---
Bug#748569: libllvm3.5: Missing symlink to libLLVM-3.5.so after install
On 18/05/2014 17:04, Dave Witbrodt wrote: Package: libllvm3.5 Version: 1:3.5~svn209039-1 Severity: grave Justification: causes non-serious data loss # cd /usr/lib/x86_64-linux-gnu # ln -s -T libLLVM-3.5.so.1 libLLVM-3.5.0.so.1 I think upstream changed that recently (on my request). I will implement your workaround (probably tonight) but to be cleaner, the packages with a dependecy on llvm should be rebuilt Cheers, S -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#748569: libllvm3.5: Missing symlink to libLLVM-3.5.so after install
I think upstream changed that recently (on my request). I will implement your workaround (probably tonight) but to be cleaner, the packages with a dependecy on llvm should be rebuilt OK, I should have thought of doing the rebuilds before selecting the severity. Feel free to lower the severity I selected. There is a real bug here, however, since that symlink in libllvm3.5 actually does not get installed when the package is installed. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#748569: libllvm3.5: Missing symlink to libLLVM-3.5.so after install
On 18/05/2014 19:33, Dave Witbrodt wrote: I think upstream changed that recently (on my request). I will implement your workaround (probably tonight) but to be cleaner, the packages with a dependecy on llvm should be rebuilt OK, I should have thought of doing the rebuilds before selecting the severity. Feel free to lower the severity I selected. There is a real bug here, however, since that symlink in libllvm3.5 actually does not get installed when the package is installed. Oh, you are right. That is clearly a RC bug! Thanks for reporting S -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#745406: marked as done ([ptpd] Non free RFC / academic paper)
Your message dated Sun, 18 May 2014 18:19:10 + with message-id e1wm5fy-00036j...@franck.debian.org and subject line Bug#745406: fixed in ptpd 2.3.0-dfsg-1 has caused the Debian Bug report #745406, regarding [ptpd] Non free RFC / academic paper 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.) -- 745406: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=745406 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: ptpd Version: 2.3.0-1 Severity: serious User: debian-rele...@lists.debian.org Usertags: nonfree-doc rfc Hi! This source package contains the following files from the IETF under non-free license terms: doc/draft-ietf-tictoc-ptp-mib-01.txt Moreover the following academic paper is not licensed (and is not a draft): doc/ptpd_2005_1588_conference_paper.pdf (two authors are not mentionned in upstream maybe IEEE retains copyright) The license on RFC/I-Ds is not DFSG-free, see: * http://wiki.debian.org/NonFreeIETFDocuments * http://bugs.debian.org/199810 According to the squeeze/wheezy release policy, source packages must be DFSG-free, see: * http://release.debian.org/squeeze/rc_policy.txt * http://release.debian.org/wheezy/rc_policy.txt The severity is serious, because this violates the Debian policy: * http://www.debian.org/doc/debian-policy/ch-archive.html#s-dfsg There are (at least) three ways to fix this problem. In order of preference: 1. Ask the author of the RFC to re-license the RFC under a free license. A template for this e-mail request can be found at http://wiki.debian.org/NonFreeIETFDocuments 2. Remove the non-free material from the source, e.g., by re-packaging the upstream archive and adding 'dfsg' to the Debian package version name. 3. Move the package to non-free. General discussions are kindly requested to take place on debian-legal or debian-devel in the thread with Subject: Non-free IETF RFC/I-Ds in source packages. Thanks, ---End Message--- ---BeginMessage--- Source: ptpd Source-Version: 2.3.0-dfsg-1 We believe that the bug you reported is fixed in the latest version of ptpd, 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 745...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Roland Stigge sti...@antcom.de (supplier of updated ptpd 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, 18 May 2014 20:05:16 +0200 Source: ptpd Binary: ptpd Architecture: source amd64 Version: 2.3.0-dfsg-1 Distribution: unstable Urgency: medium Maintainer: Roland Stigge sti...@antcom.de Changed-By: Roland Stigge sti...@antcom.de Description: ptpd - Precision Time Protocol daemon Closes: 745406 Changes: ptpd (2.3.0-dfsg-1) unstable; urgency=medium . * Repackaged by removing doc/draft-ietf-tictoc-ptp-mib-01.txt and doc/ptpd_2005_1588_conference_paper.pdf due to license issues (Closes: #745406) Checksums-Sha1: 9044fd743aa3bf83e901fbcf814147f8e12e0ae3 1095 ptpd_2.3.0-dfsg-1.dsc 793eb1fdc521a0a42580ab792063d98e5dbc4751 446345 ptpd_2.3.0-dfsg.orig.tar.gz 08ee66f568eb90efa3bdbcb2c56d3afef6dc398b 4756 ptpd_2.3.0-dfsg-1.debian.tar.xz 84a43fc3c0d7396902f3bdcef64acd021194e535 91354 ptpd_2.3.0-dfsg-1_amd64.deb Checksums-Sha256: 269e2f26656e9c6cffbd1a6529267b21e5c867118798242112625709c1d6af6f 1095 ptpd_2.3.0-dfsg-1.dsc 94ae4bfda82fa2bb5ac15a16770b0db69834b9c133511fa18fba83684a10a261 446345 ptpd_2.3.0-dfsg.orig.tar.gz ac8a1f7e6975b70cf680c7f5d6fd78fc919ddbbbe38c043646599506ee44aad5 4756 ptpd_2.3.0-dfsg-1.debian.tar.xz 10eab6067913a1db5c3728d53f71e542fdb001b3b7357ddac293bacaf3d6a664 91354 ptpd_2.3.0-dfsg-1_amd64.deb Files: 3f67d0a64b2dfed2f191a0f2ec88cfa8 91354 net optional ptpd_2.3.0-dfsg-1_amd64.deb d9f2b4d95e2286c5f0b67e28055a396c 1095 net optional ptpd_2.3.0-dfsg-1.dsc bca858058d1701992b7d5cb4cfca79aa 446345 net optional ptpd_2.3.0-dfsg.orig.tar.gz 02b5cbed6e20d7760227c6bdc59e8b27 4756 net optional ptpd_2.3.0-dfsg-1.debian.tar.xz -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.15 (GNU/Linux) iD8DBQFTePbocaH/YBv43g8RAsxPAKCAzSVIJbxN7eV2RCVWMiOIsdZ/UwCaAv/W 7lnG7lLgEqfpFvt2X6VAizc= =lmpV -END PGP SIGNATUREEnd
Bug#748603: [kde-telepathy] Version from sid not installable
Source: kde-telepathy Version: 0.8.1 Severity: serious The current version of kde-telepathy in sid is not installable because the ktp-common-internals was not uploaded and all packages depend on kde-telepathy-data = 0.8.1. This is not available in sid at the moment. This makes the package unsuitable for release. --- System information. --- Architecture: amd64 Kernel: Linux 3.14-1-amd64 Debian Release: jessie/sid 500 unstablehttp.debian.net 1 experimentalhttp.debian.net -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#744708: graphite-web removed from testing
2014-05-17 14:15 GMT+02:00 Jonas Genannt jonas.gena...@capi2name.de: Hello, Hello Jonas, Do you plan to work on this issue? grahite-web has been removed from testing now. yes, but I'm very busy with my day job. It's on my todo list, will do it asap. OK. I understand, this is sometimes hard to keep a package up to date and RC-free. Good luck -- Mathieu Parent -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: debian bug 725476
Processing commands for cont...@bugs.debian.org: fixed 725476 ipmitool/1.8.14-1 Bug #725476 [ipmitool] ipmitool: FTBFS on kfreebsd The source ipmitool and version 1.8.14-1 do not appear to match any binary packages Marked as fixed in versions ipmitool/1.8.14-1. owner 725476 ! Bug #725476 [ipmitool] ipmitool: FTBFS on kfreebsd Owner recorded as Jörg Frings-Fürst deb...@jff-webhosting.net. -- Stopping processing here. Please contact me if you need assistance. -- 725476: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=725476 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#733322: marked as done (comedilib: FTBFS: calib_yacc.y:340:2: error: too many arguments to function 'calib_yyparse')
Your message dated Sun, 18 May 2014 19:33:40 + with message-id e1wm6q4-0002eb...@franck.debian.org and subject line Bug#733322: fixed in comedilib 0.10.1-1.1 has caused the Debian Bug report #733322, regarding comedilib: FTBFS: calib_yacc.y:340:2: error: too many arguments to function 'calib_yyparse' 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.) -- 733322: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=733322 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: comedilib Version: 0.10.1-1 Severity: serious Hi there, building your package fails in a up-to-date amd64 sbuild chroot: libtool: compile: x86_64-linux-gnu-gcc -std=gnu99 -DHAVE_CONFIG_H -I. -I.. -D_FORTIFY_SOURCE=2 -I../include -I../include -Wall -D_REENTRANT -DLOCALSTATEDIR=\/var/lib/libcomedi0\ -g -O2 -fstack-protector --param=ssp-buffer-size=4 -Wformat -Werror=format-security -c calib_lex.c -o libcomedi_la-calib_lex.o /dev/null 21 /bin/bash ../libtool --tag=CC --mode=compile x86_64-linux-gnu-gcc -std=gnu99 -DHAVE_CONFIG_H -I. -I.. -D_FORTIFY_SOURCE=2 -I../include -I../include -Wall -D_REENTRANT -DLOCALSTATEDIR=\\/var/lib/libcomedi0\ -g -O2 -fstack-protector --param=ssp-buffer-size=4 -Wformat -Werror=format-security -c -o libcomedi_la-calib_yacc.lo `test -f 'calib_yacc.c' || echo './'`calib_yacc.c libtool: compile: x86_64-linux-gnu-gcc -std=gnu99 -DHAVE_CONFIG_H -I. -I.. -D_FORTIFY_SOURCE=2 -I../include -I../include -Wall -D_REENTRANT -DLOCALSTATEDIR=\/var/lib/libcomedi0\ -g -O2 -fstack-protector --param=ssp-buffer-size=4 -Wformat -Werror=format-security -c calib_yacc.c -fPIC -DPIC -o .libs/libcomedi_la-calib_yacc.o calib_yacc.y: In function '_comedi_parse_calibration_file': calib_yacc.y:340:2: error: too many arguments to function 'calib_yyparse' if( calib_yyparse( priv ) ) ^ In file included from calib_yacc.y:36:0: ./calib_yacc.h:107:5: note: declared here int calib_yyparse (void); ^ ./calib_yacc.c: In function 'calib_yyparse': ./calib_yacc.c:1596:7: error: too few arguments to function 'calib_yylex' yychar = yylex (yylval); ^ In file included from calib_yacc.y:27:0: libinternal.h:148:21: note: declared here #define YY_DECL int calib_yylex(YYSTYPE *calib_lvalp, yyscan_t yyscanner) ^ calib_yacc.y:55:1: note: in expansion of macro 'YY_DECL' YY_DECL; ^ calib_yacc.y:381:73: error: 'parse_arg' undeclared (first use in this function) fprintf(stderr, input error on line %i\n, calib_yyget_lineno(priv(parse_arg)-yyscanner)); ^ calib_yacc.y:381:73: note: each undeclared identifier is reported only once for each function it appears in make[4]: *** [libcomedi_la-calib_yacc.lo] Error 1 make[4]: Leaving directory `/«PKGBUILDDIR»/lib' make[3]: *** [all] Error 2 make[3]: Leaving directory `/«PKGBUILDDIR»/lib' make[2]: *** [all-recursive] Error 1 make[2]: Leaving directory `/«PKGBUILDDIR»' make[1]: *** [all] Error 2 make[1]: Leaving directory `/«PKGBUILDDIR»' make: *** [build-arch-stamp] Error 2 dpkg-buildpackage: error: debian/rules build gave error exit status 2 Full buildlog attached. -- Andreas Moog, Berliner Str. 29, 36205 Sontra/Germany PGP-encrypted mails preferred (Key-ID: 74DE6624) PGP Fingerprint: 74CD D9FE 5BCB FE0D 13EE 8EEA 61F3 4426 74DE 6624 comedilib_0.10.1-1_amd64.build.gz Description: application/gzip signature.asc Description: OpenPGP digital signature ---End Message--- ---BeginMessage--- Source: comedilib Source-Version: 0.10.1-1.1 We believe that the bug you reported is fixed in the latest version of comedilib, 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 733...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Petter Reinholdtsen p...@debian.org (supplier of updated comedilib 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, 11 May 2014 20:52:01 +0200 Source: comedilib Binary: libcomedi-dev libcomedi0 python-comedilib Architecture: source amd64 Version: 0.10.1-1.1 Distribution: unstable Urgency: low
Bug#733059: gnome-screensaver cannot be launched by alternative gnome-session
I'm not absolutely sure that this is what the original reporter meant but I've just run into this problem when using gnome-session to launch my own i3-gnome session. My session file contains: [GNOME Session] Name=i3 Gnome session RequiredComponents=gnome-settings-daemon;gnome-screensaver;nm-applet;i3-gnome gnome-settings-daemon, nm-applet and (my) i3-gnome are launched correctly yet gnome-screensaver is not. This appears to be due to the following line in /usr/share/gnome/autostart/gnome-screensaver.desktop: AutostartCondition=GNOME3 if-session gnome-flashback (I assume that modern gnome-shell launches gnome-screensaver itself now.) If I comment the line out then gnome-screensaver is launched correctly. Perhaps there is a way to invert this condition so that gnome-screensaver is enabled except on GNOME3? Thanks. Mike. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#748495: marked as done (Missing required dependencies)
Your message dated Sun, 18 May 2014 21:49:44 +0200 with message-id 53790ed8.8030...@progress-technologies.net and subject line Re: Missing required dependencies has caused the Debian Bug report #748495, regarding Missing required dependencies to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 748495: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=748495 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: lxc-stuff Version: 1.0.3-1 Severity: serious Hi, When recommended packages are not installed by default the package fails to find at least the following dependencies: - python3 If those are not installed lxc-stuff fails to execute even simple things like lxc start container -d Even after pulling those additional dependencies I run into [1]. Kind regards, Benny Baumann [1] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=745418 -- System Information: Debian Release: wheezy/stable APT prefers stable APT policy: (900, 'stable'), (800, 'testing'), (750, 'unstable'), (700, 'experimental'), (500, 'oldstable') Architecture: amd64 (x86_64) Kernel: Linux 3.13-1-amd64 (SMP w/8 CPU cores) Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages lxc-stuff depends on: ii debconf [debconf-2.0] 1.5.53 ii lxc1.0.3-1 Versions of packages lxc-stuff recommends: ii debootstrap 1.0.60 pn irkernone Versions of packages lxc-stuff suggests: ii rsync 3.0.9-4 -- debconf information excluded ---End Message--- ---BeginMessage--- Benny Baumann be...@geshi.org wrote: When recommended packages are not installed by default in debian, recommends are installed by default. if you choose not to, then you need to take care about the effects it has. having python in recommends rather than depends in sensible here, as you can use lxc without it and i don't want to burden people with it if they don't want it, or, rather, allow them to choose not to use it with python if they don't want to. -- Address:Daniel Baumann, Donnerbuehlweg 3, CH-3012 Bern Email: daniel.baum...@progress-technologies.net Internet: http://people.progress-technologies.net/~daniel.baumann/---End Message---
Bug#628383: [kfreebsd-*] test failure: test-secmem
Apparently freebsd kernels 9.2 and later have security.bsd.unprivileged_mlock, which appears to default to permitted. http://www.freebsd.org/cgi/man.cgi?query=mlocksektion=2manpath=FreeBSD+9.2-RELEASE http://marc.info/?l=freebsd-archm=134617193210756 Is this test failure happening with kernel 9.2? I can't see that in the buildd logs. I only have a 9.0 kernel to test on... Jeff -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#628383: [kfreebsd-*] test failure: test-secmem
Hi, On 18/05/14 20:38, Jeff Epler wrote: Apparently freebsd kernels 9.2 and later have security.bsd.unprivileged_mlock, which appears to default to permitted. Ah, that is good to know. The buildds are wheezy systems with a 9.0 kernel. I'm not sure of the timetable for them to be upgraded to a jessie (probably 10.0 or 10.1) kernel. I wonder if an NMU by a DD who builds+tests on 10.0 is sensible for something like this. Regards, -- Steven Chamberlain ste...@pyro.eu.org -- 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 748600 is serious
Processing commands for cont...@bugs.debian.org: severity 748600 serious Bug #748600 [libnfs] xbmc-bin needs libnfs.so.1, libnfs1 provides libnfs.so.4 Severity set to 'serious' from 'normal' thanks Stopping processing here. Please contact me if you need assistance. -- 748600: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=748600 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#628383: [kfreebsd-*] test failure: test-secmem
Maye I misunderstood something but i think there's a reason the memory is mlocked; to avoid leaking sensitive information into swap. As far as I know, there is no gurantee, that mlocked memory will not go into swap when whole PC is suspended, even under Linux. man mlock (from Linux Programmer's Manual) Cryptographic security software often handles critical bytes like passwords or secret keys as data structures. As a result of paging, these secrets could be transferred onto a persistent swap store medium, where they might be accessible to the enemy long after the security software has erased the secrets in RAM and terminated. (But be aware that the suspend mode on laptops and some desktop computers will save a copy of the system's RAM to disk, regardless of memory locks.) We can't just kill off security by patching out the check for working mlock. Atleast not without a big fat warning dialog where the user opts out of security first. As you can see from above, there is not guaranteed security even under Linux. The FreeBSD only adds additional (allowed by POSIX) restriction, mlock needs root priviledges. It can be solved by setting setuid bit under GNU/kFreeBSD. Petr -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: jessie
Processing commands for cont...@bugs.debian.org: tags 748525 + sid jessie Bug #748525 [pangzero] Fails on launch if set to widescreen Added tag(s) sid and jessie. tags 748547 + sid jessie Bug #748547 [input-utils] FTBFS: Unknown sequence /usr/share/topgit/tg2quilt.mk Added tag(s) sid and jessie. thanks Stopping processing here. Please contact me if you need assistance. -- 748525: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=748525 748547: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=748547 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#748614: [libkolabxml0] looses information about birthdays
Package: libkolabxml0 Version: 0.8.4-5.1 Severity: grave Grave because it looses data. I've just installed a new machine and added my IMAP server and kolab agent to akonadi. It downloaded all resources but when I've started to edit some users I've noticed that the birthday was missing. Also entering it again resulted in missing birthdays (like it was never entered) on all other machines also using the same IMAP server with kolab. Checking the imap server also seemed to verify that no dates are stored inside the KolabV3 contact xml. I've also tried to change it from KolabV3 to KolabV2 format in the Kolab-Agent settings but then other data fields cannot be parsed anymore when downloading the newly stored kolab mails/xmls (for example the pictures). Interestingly the anniversary date is stored but not the birthday Reproducible: Always Steps to Reproduce: create an imap account to akonadi (using KDE systemsettings or so) add a kolab agent with the default settings (v3) using this imap server press create folders create a new contact in the activated contact folder in kaddressbook add a birthday date and save it. Now open the mail on the imap server and check for the birthday information. I think this is the easiest way to check it without another machine/account to download and parse the contact information again. Actual Results: birthday is not stored on the server Expected Results: birthday is stored on the server --- System information. --- Architecture: amd64 Kernel: Linux 3.14-1-amd64 Debian Release: jessie/sid 500 unstablehttp.debian.net --- Package information. --- Depends (Version) | Installed ==-+-= libboost-system1.54.0 | 1.54.0-5 libboost-thread1.54.0 | 1.54.0-5 libc6(= 2.14) | libcurl3-gnutls(= 7.16.2) | libgcc1 (= 1:4.1.1) | libstdc++6 (= 4.4.0) | libxerces-c3.1 | -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#748615: linux-image-3.14-0.bpo.1-amd64: the system reboot after mounting the partitions
Package: linux-image-3.14-0.bpo.1-amd64 Version: linux-image-3.14-0.bpo.1-amd64 Severity: grave Justification: causes non-serious data loss Dear Maintainer, Booting on this linux-image-3.14-0.bpo.1-amd64 kernel makes always reboot immediately after all auto fstab partitions mounted in the init processus. Kernel 3.12.20 froml Linus works fine but : [0.010403] [Firmware Bug]: AMD-Vi: IOAPIC[0] not in IVRS table [0.010483] [Firmware Bug]: AMD-Vi: No southbridge IOAPIC found [0.010514] AMD-Vi: Disabling interrupt remapping These logs appears also with 3.14 No other logs. -- System Information: Debian Release: 7.5 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.12.20 (SMP w/2 CPU cores) is NOT the faulty kernel. Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages linux-image-3.14-0.bpo.1-amd64 depends on: ii debconf [debconf-2.0] 1.5.49 ii initramfs-tools [linux-initramfs-tool] 0.115~bpo70+1 ii kmod9-3 ii linux-base 3.5 ii module-init-tools 9-3 Versions of packages linux-image-3.14-0.bpo.1-amd64 recommends: ii firmware-linux-free 3.2 Versions of packages linux-image-3.14-0.bpo.1-amd64 suggests: pn debian-kernel-handbook none ii grub-pc 1.99-27+deb7u2 pn linux-doc-3.14 none LANG=C lscpu Architecture: x86_64 CPU op-mode(s):32-bit, 64-bit Byte Order:Little Endian CPU(s):2 On-line CPU(s) list: 0,1 Thread(s) per core:2 Core(s) per socket:1 Socket(s): 1 NUMA node(s): 1 Vendor ID: AuthenticAMD CPU family:21 Model: 16 Stepping: 1 CPU MHz: 1400.000 BogoMIPS: 6787.36 Virtualization:AMD-V L1d cache: 16K L1i cache: 64K L2 cache: 1024K NUMA node0 CPU(s): 0,1 0.00] DMI: MSI MS-7721/A78M-E35 (MS-7721), BIOS V30.3 03/14/2014 -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#748569: marked as done (libllvm3.5: Missing symlink to libLLVM-3.5.so after install)
Your message dated Sun, 18 May 2014 21:25:19 + with message-id e1wm8a7-00069b...@franck.debian.org and subject line Bug#748569: fixed in llvm-toolchain-snapshot 1:3.5~svn209039-2 has caused the Debian Bug report #748569, regarding libllvm3.5: Missing symlink to libLLVM-3.5.so after install 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.) -- 748569: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=748569 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: libllvm3.5 Version: 1:3.5~svn209039-1 Severity: grave Justification: causes non-serious data loss Upgrading to this version caused X Windows to crash as soon as any attempt to run an OpenGL application was made. It's possible that people could lose data when X crashes this way that they really cannot afford to lose, so maybe the severity should be changed to critical. After some investigation, I found out some extra details that I can report: 1) My desktop manager (lightdm, running Xfce on Sid) respawned and now attempts to run OpenGL programs no longer crashed X, but they failed to run. The xsession-errors log revealed that acceleration was not enabled. 2) I use the radeonsi Mesa driver for acceleration, and this requires the glamor 2D driver. The Xorg.0.log file showed that the glamor module could not locate a file -- libLLVM-3.5.0.so.1: [ 31667.925] (EE) AIGLX error: dlopen of /usr/lib/x86_64-linux-gnu/dri/swrast_dri.so failed (libLLVM-3.5.0.so.1: cannot open shared object file: No such file or directory) 3) The contents of package libllvm3.5 do seem to include a symlink matching the name of the missing file: # dpkg-deb -c libllvm3.5_1%3a3.5~svn209039-1_amd64.deb [...] -rw-r--r-- root/root 30171784 2014-05-17 08:06 ./usr/lib/x86_64-linux-gnu/libLLVM-3.5.so.1 [...] lrwxrwxrwx root/root 0 2014-05-17 08:05 ./usr/lib/x86_64-linux-gnu/libLLVM-3.5.0.so.1 - libLLVM-3.5.so This symlink is NOT present on my system after libllvm3.5 is installed by my package manager. 4) I thought another LLVM 3.5 package might contain the file that the symlink was supposed to link to, and I found that in llvm-3.5-dev: # dpkg-deb -c llvm-3.5-dev_1%3a3.5~svn209039-1_amd64.deb | grep \.so -rw-r--r-- root/root 30171656 2014-05-17 08:06 ./usr/lib/llvm-3.5/lib/libLLVM-3.5.so [...] lrwxrwxrwx root/root 0 2014-05-17 08:05 ./usr/lib/llvm-3.5/lib/libLLVM-3.5.0.so - ../../x86_64-linux-gnu/libLLVM-3.5.0.so.1 (Notice that libLLVM-3.5.0.so is supposed to be a symlink to the other symlink which ends up not being present on my system after the upgrade.) 5) Inspecting /var/log/dpkg.log, it would seem that libllvm3.5 installs before any of the other LLVM-related packages. At that time, without llvm-3.5-dev present to provide libLLVM-3.5.so, it looks like the symlink gets dropped and does not get installed. 6) As a workaround, I manually created a different symlink: # cd /usr/lib/x86_64-linux-gnu # ln -s -T libLLVM-3.5.so.1 libLLVM-3.5.0.so.1 This resulted in a fully working system, according to all of the testing I've tried so far. I do not know if this is the correct solution, but I just thought I'd mention it, since it might allow you to package libllvm3.5 in such a way that it installs correctly without depending on other packages being installed first. In any case it is very bad if someone has a previous LLVM installed with working acceleration, and then upgrading to a new version sets them up so that the moment they try to run an OpenGL program the X server dies on them! Fortunately, I am using software not available in Debian repositories (like glamor) in order to test the upstream radeonsi support (I need this for my Radeon HD 7850 GPU, which requires radeonsi for acceleration), so few other people will be affected by this bug right now. HTH, Dave Witbrodt -- System Information: Debian Release: jessie/sid APT prefers unstable APT policy: (990, 'unstable'), (350, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 3.14.4-1+dwlocal1 (SMP w/4 CPU cores; PREEMPT) Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages libllvm3.5 depends on: ii libc6 2.18-6 ii libedit2 3.1-20140213-1 ii libffi63.1~rc1+r3.0.13-12 ii libgcc11:4.9.0-3 ii libstdc++6 4.9.0-3 ii libtinfo5 5.9+20140118-1 ii multiarch-support 2.18-6 libllvm3.5 recommends no packages. libllvm3.5 suggests no packages. -- no debconf information ---End Message--- ---BeginMessage--- Source:
Bug#748618: syslinux-themes-debian: Fails to uninstall: extlinux-update: not found
Package: syslinux-themes-debian Version: 12-3 Severity: serious Uninstalling syslinux-themes-debian fails: Removing syslinux-themes-debian (12-3) ... /var/lib/dpkg/info/syslinux-themes-debian.postrm: 15: /var/lib/dpkg/info/syslinux-themes-debian.postrm: extlinux-update: not found dpkg: error processing package syslinux-themes-debian (--remove): subprocess installed post-removal script returned error exit status 127 It seems that the extlinux package no longer (as of 3:6.03~pre1+dfsg-4) contains /usr/sbin/extlinux-update. Sami -- System Information: Debian Release: jessie/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.14.4 (SMP w/8 CPU cores; PREEMPT) Locale: LANG=en_US.UTF-8, LC_CTYPE=fi_FI.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages syslinux-themes-debian depends on: pn syslinux-themes-debian-wheezy none syslinux-themes-debian recommends no packages. syslinux-themes-debian suggests no packages. -- no debconf information signature.asc Description: Digital signature
Bug#748574: 3.14.1 does not boot on Dell server
On Sun, 2014-05-18 at 17:29 +0200, Erwan David wrote: Package: src:linux Version: 3.14.4-1 Severity: critical When trying to boot 3.14.1 It stops at the first line booting the kernel, no other message, even when trying to start without quiet. [...] Please try adding the kernel parameter 'earlyprintk=vga' to make it log to the screen earlier. Ben. -- Ben Hutchings Usenet is essentially a HUGE group of people passing notes in class. - Rachel Kadel, `A Quick Guide to Newsgroup Etiquette' signature.asc Description: This is a digitally signed message part
Processed: Re: Bug#748615: linux-image-3.14-0.bpo.1-amd64: the system reboot after mounting the partitions
Processing control commands: severity -1 important Bug #748615 [linux-image-3.14-0.bpo.1-amd64] linux-image-3.14-0.bpo.1-amd64: the system reboot after mounting the partitions Severity set to 'important' from 'grave' -- 748615: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=748615 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#748615: linux-image-3.14-0.bpo.1-amd64: the system reboot after mounting the partitions
Control: severity -1 important On Sun, 2014-05-18 at 23:22 +0200, rpnpif wrote: Package: linux-image-3.14-0.bpo.1-amd64 Version: linux-image-3.14-0.bpo.1-amd64 Severity: grave Justification: causes non-serious data loss [...] No. Ben. -- Ben Hutchings Usenet is essentially a HUGE group of people passing notes in class. - Rachel Kadel, `A Quick Guide to Newsgroup Etiquette' signature.asc Description: This is a digitally signed message part
Bug#748574: 3.14.1 does not boot on Dell server
On 05/18/2014 06:32 PM, Ben Hutchings wrote: On Sun, 2014-05-18 at 17:29 +0200, Erwan David wrote: Package: src:linux Version: 3.14.4-1 Severity: critical When trying to boot 3.14.1 It stops at the first line booting the kernel, no other message, even when trying to start without quiet. [...] Please try adding the kernel parameter 'earlyprintk=vga' to make it log to the screen earlier. Ben. I did that but no way to save it. It's a Call Trace, ending with the instruction pointer RIP 0x0. I took a picture of the screen if it would help... -- --- John Bleichert-syb...@earthlink.net The heat from below can burn your eyes out! -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#748574: 3.14.1 does not boot on Dell server
On Sun, 2014-05-18 at 20:21 -0400, John Bleichert wrote: On 05/18/2014 06:32 PM, Ben Hutchings wrote: On Sun, 2014-05-18 at 17:29 +0200, Erwan David wrote: Package: src:linux Version: 3.14.4-1 Severity: critical When trying to boot 3.14.1 It stops at the first line booting the kernel, no other message, even when trying to start without quiet. [...] Please try adding the kernel parameter 'earlyprintk=vga' to make it log to the screen earlier. Ben. I did that but no way to save it. It's a Call Trace, ending with the instruction pointer RIP 0x0. I took a picture of the screen if it would help... Yes, please send the photo to the bug as an attachment. (You may wish to scale it down, but make sure it's still legible.) Ben. -- Ben Hutchings It is easier to change the specification to fit the program than vice versa. signature.asc Description: This is a digitally signed message part
Processed: Re: Bug#748574: 3.14.1 does not boot on Dell server
Processing control commands: tag -1 upstream patch moreinfo Bug #748574 [src:linux] 3.14.1 does not boot on Dell server Added tag(s) upstream, moreinfo, and patch. -- 748574: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=748574 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#748574: 3.14.1 does not boot on Dell server
Control: tag -1 upstream patch moreinfo
On Sun, 2014-05-18 at 20:58 -0400, John Bleichert wrote:
On May 18, 2014, at 8:34 PM, Ben Hutchings b...@decadent.org.uk
wrote:
Yes, please send the photo to the bug as an attachment. (You may
wish
to scale it down, but make sure it's still legible.)
Attaching it here. Unfortunately shift+pageup and shift+pagedown did
not function so I could not get more.
They never do after a crash. But this seems to be enough information.
The page faults are ominous…
Please test whether the attached patch fixes this, following the
instructions at
http://kernel-handbook.alioth.debian.org/ch-common-tasks.html#s-common-official
Ben.
--
Ben Hutchings
It is easier to change the specification to fit the program than vice versa.
From: Lv Zheng lv.zh...@intel.com
Date: Wed, 30 Apr 2014 10:05:40 +0800
Subject: ACPICA: Tables: Fix invalid pointer accesses in
acpi_tb_parse_root_table().
Origin: https://git.kernel.org/cgit/linux/kernel/git/rafael/linux-pm.git/commit?id=d48dc067450d84324067f4472dc0b169e9af4454
Linux XSDT validation mechanism backport has introduced a regreession:
Commit: 671cc68dc61f029d44b43a681356078e02d8dab8
Subject: ACPICA: Back port and refine validation of the XSDT root table.
There is a pointer still accessed after unmapping.
This patch fixes this issue. Lv Zheng.
Fixes: 671cc68dc61f (ACPICA: Back port and refine validation of the XSDT root table.)
References: https://bugzilla.kernel.org/show_bug.cgi?id=73911
References: https://bugs.archlinux.org/task/39811
Signed-off-by: Lv Zheng lv.zh...@intel.com
Reported-and-tested-by: Bruce Chiarelli mano...@gmail.com
Reported-and-tested-by: Spyros Stathopoulos spyst...@gmail.com
Signed-off-by: Bob Moore robert.mo...@intel.com
Cc: 3.14+ sta...@vger.kernel.org # 3.14+
Signed-off-by: Rafael J. Wysocki rafael.j.wyso...@intel.com
---
drivers/acpi/acpica/tbutils.c | 7 +--
1 file changed, 5 insertions(+), 2 deletions(-)
diff --git a/drivers/acpi/acpica/tbutils.c b/drivers/acpi/acpica/tbutils.c
index a4702ee..9fb85f3 100644
--- a/drivers/acpi/acpica/tbutils.c
+++ b/drivers/acpi/acpica/tbutils.c
@@ -461,6 +461,7 @@ acpi_status __init acpi_tb_parse_root_table(acpi_physical_address rsdp_address)
u32 table_count;
struct acpi_table_header *table;
acpi_physical_address address;
+ acpi_physical_address rsdt_address;
u32 length;
u8 *table_entry;
acpi_status status;
@@ -488,11 +489,14 @@ acpi_status __init acpi_tb_parse_root_table(acpi_physical_address rsdp_address)
* as per the ACPI specification.
*/
address = (acpi_physical_address) rsdp-xsdt_physical_address;
+ rsdt_address =
+ (acpi_physical_address) rsdp-rsdt_physical_address;
table_entry_size = ACPI_XSDT_ENTRY_SIZE;
} else {
/* Root table is an RSDT (32-bit physical addresses) */
address = (acpi_physical_address) rsdp-rsdt_physical_address;
+ rsdt_address = address;
table_entry_size = ACPI_RSDT_ENTRY_SIZE;
}
@@ -515,8 +519,7 @@ acpi_status __init acpi_tb_parse_root_table(acpi_physical_address rsdp_address)
/* Fall back to the RSDT */
- address =
- (acpi_physical_address) rsdp-rsdt_physical_address;
+ address = rsdt_address;
table_entry_size = ACPI_RSDT_ENTRY_SIZE;
}
}
signature.asc
Description: This is a digitally signed message part
Processed: Re: Bug#746034: chromium 34.0.1847.116-1~deb7u1 depends on libudev0 which is no longer in the testing archive
Processing control commands: reopen 746034 Bug #746034 [chromium] chromium 34.0.1847.116-1~deb7u1 depends on libudev0 which is no longer in the testing archive Bug 746034 is not marked as done; doing nothing. -- 746034: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=746034 746330: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=746330 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: Re: Bug#746034: chromium 34.0.1847.116-1~deb7u1 depends on libudev0 which is no longer in the testing archive
Processing control commands:
reopen 746034
Bug #746034 {Done: Andreas Cadhalpun andreas.cadhal...@googlemail.com}
[chromium] chromium 34.0.1847.116-1~deb7u1 depends on libudev0 which is no
longer in the testing archive
'reopen' may be inappropriate when a bug has been closed with a version;
all fixed versions will be cleared, and you may need to re-add them.
Bug reopened
No longer marked as fixed in versions 34.0.1847.116-2.
--
746034: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=746034
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#746034: chromium 34.0.1847.116-1~deb7u1 depends on libudev0 which is no longer in the testing archive
Control: reopen 746034 thanks On 4/29/14, Andreas Cadhalpun andreas.cadhal...@googlemail.com wrote: Control: tags -1 + sid Control: forcemerge -1 746330 Hi, On 29.04.2014 13:51, Justin B Rye wrote: Andreas Cadhalpun wrote: On 27.04.2014 11:26, shirish शिरीष wrote: I cannot install the update 34.0.1847.116-1~deb7u1 because it depends on libudev0 and libudev0 is no longer in the Debian testing archive. I have marked the bug as grave as almost everybody who has removed libudev0 would not be able to install this package. I'm also affected by this. It seems the version currently in testing was build for stable. Luckily, the version from sid can be installed just fine, so I'm closing this bug with that version and tag it as only affecting jessie. Unluckily, this isn't true for everybody. If you look at https://packages.debian.org/sid/chromium or http://ftp.debian.org/debian/pool/main/c/chromium-browser/ you'll see that 34.0.1847.116-2 is only available for amd64. On the i386 architecture, that version failed to build: https://buildd.debian.org/status/package.php?p=chromium-browser so the latest available version of chromium is the misbegotten 34.0.1847.116-1~deb7u1. I know this. :-\ The FTBFS on i386 is tracked in #745794. So maybe this bug needs to be marked as still found on i386, though I don't see any mechanism for doing that. This bug is still open in testing and unstable, see e.g. the graphic in the upper right corner on [1]. But I'm tagging it as affecting sid as well now. Fixing the FTBFS on i386 is all that needs to be done. Meanwhile I see Dan Jacobson's just opened a duplicate of this bug as #746330... I'm merging the duplicate. Best regards, Andreas 1: https://bugs.debian.org/746034 Hi all, Even on amd64 there is NO 34.0.1847.116-2 . The only one which is available to install is chromium 34.0.1847.137-1 which hopefully will migrate to testing in next 2-3 days. $ apt-show-versions -a chromium chromium:amd64 33.0.1750.152-1 install ok installed chromium:amd64 34.0.1847.116-1~deb7u1 jessie debian.ec.as6453.net No testing-updates version chromium:amd64 34.0.1847.137-1unstable debian.ec.as6453.net chromium:amd64 35.0.1916.99-1 experimental debian.ec.as6453.net chromium:amd64/jessie 33.0.1750.152-1 upgradeable to 34.0.1847.116-1~deb7u1 $ uname -m x86_64 OR $ getconf LONG_BIT 64 OR $ lscpu | grep Architecture Architecture: x86_64 OR finally :- $ dpkg-architecture | grep DEB_HOST_ARCH= DEB_HOST_ARCH=amd64 I am guessing the only way forward is the one in sid/unstable :- $ aptitude show chromium=34.0.1847.137-1 | grep libudev1 4.6), libudev1 (= 183), libx11-6 (= 2:1.4.99.1), libxcomposite1 (= As per the PTS this should migrate in another 2-3 days :- http://packages.qa.debian.org/c/chromium-browser.html Looking forward to the fixed build, thank you chromium maintainers. -- Regards, Shirish Agarwal शिरीष अग्रवाल My quotes in this email licensed under CC 3.0 http://creativecommons.org/licenses/by-nc/3.0/ http://flossexperiences.wordpress.com EB80 462B 08E1 A0DE A73A 2C2F 9F3D C7A4 E1C4 D2D8 -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#743685: urwid: FTBFS: test failures
reopen 743685 thanks On Fri, May 16, 2014 at 2:59 AM, Vincent Cheng vch...@debian.org wrote: On Wed, May 14, 2014 at 9:12 AM, Dejan Latinovic dejan.latino...@imgtec.com wrote: Debian patch that removes test_vterm.py is attached. Vincent, could you please include this patch in new Debian package version? Thanks, I'll take a look at this asap. Ian: it doesn't have to be fixed in upstream right now, no, but it'd be nice to have those tests removed (or fixed?) upstream as well so we don't end up carrying this patch in Debian forever. Uploaded...but it looks like it's failing to build on mips now [1]; looks like the same test (urwid.tests.test_event_loops.TwistedEventLoopTest) that failed wth urwid/1.2.0-1. The fact that these tests don't consistently fail on mips(el) is rather annoying. Does anyone know what's going on? Regards, Vincent [1] https://buildd.debian.org/status/fetch.php?pkg=urwidarch=mipsver=1.2.1-2stamp=1400413671 -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: your mail
Processing commands for cont...@bugs.debian.org:
reopen 743685
Bug #743685 {Done: Vincent Cheng vch...@debian.org} [src:urwid] FTBFS: test
failures
'reopen' may be inappropriate when a bug has been closed with a version;
all fixed versions will be cleared, and you may need to re-add them.
Bug reopened
No longer marked as fixed in versions urwid/1.2.1-2.
thanks
Stopping processing here.
Please contact me if you need assistance.
--
743685: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=743685
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#748355: Upgrading from sysvinit/wheezy to systemd-sysv/sid impossible due to loop
On Fri, May 16, 2014 at 06:53:27PM +0200, Sven Joachim wrote: On 2014-05-16 17:33 +0200, Michael Biebl wrote: Incidentally we also discussed dropping the Conflicts from systemd-sysv and only keeping the Replaces (and this is also what sysvinit-core has done). Which has its own problems, since nothing stops the admin from shooting themselves in the foot by installing sysvinit-core without upgrading sysvinit and then removing sysvinit-core. Stopping admins from shooting themselves in the foot by running a stupid sequence of apt commands without understanding what they're doing, should not be given higher precedence than ensuring that the vast majority of our users are able to cleanly upgrade by following our standard upgrade instructions. So yes, it's a downside that this is possible when using the Replaces without Breaks or Conflicts, but it's definitely a lesser evil. -- Steve Langasek Give me a lever long enough and a Free OS Debian Developer to set it on, and I can move the world. Ubuntu Developerhttp://www.debian.org/ slanga...@ubuntu.com vor...@debian.org signature.asc Description: Digital signature
