Processed: Re: Bug#763011: doxygen: uses libclang but does not find it
Processing control commands: reassign -1 libclang1-3.5 Bug #763011 [doxygen] doxygen: uses libclang but does not find it Bug reassigned from package 'doxygen' to 'libclang1-3.5'. No longer marked as found in versions doxygen/1.8.7-3. Ignoring request to alter fixed versions of bug #763011 to the same values previously set forcemerge 762959 -1 Bug #762959 [libclang1-3.5] ABI break: missing libclang.so.1 Bug #762994 [libclang1-3.5] doxygen: makes xbmc FTBFS Bug #763011 [libclang1-3.5] doxygen: uses libclang but does not find it Added indication that 763011 affects doxygen Marked as found in versions llvm-toolchain-3.5/1:3.5-2. Bug #762994 [libclang1-3.5] doxygen: makes xbmc FTBFS Merged 762959 762994 763011 -- 762959: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=762959 762994: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=762994 763011: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=763011 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#763011: doxygen: uses libclang but does not find it
Control: reassign -1 libclang1-3.5 Control: forcemerge 762959 -1 On Sat, Sep 27, 2014 at 06:47:08AM +0200, Samuel Thibault wrote: Apparently doxygen uses libclang, and depends on it, but it does not seem to be finding it. Perhaps it needs a binNMU? Please file the bug against the correct package next time and check for duplicates. Helmut -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#762974: marked as done (kmod fails to install on Jessie)
Your message dated Sat, 27 Sep 2014 06:19:02 + with message-id e1xxlls-0006ir...@franck.debian.org and subject line Bug#762974: fixed in kmod 18-3 has caused the Debian Bug report #762974, regarding kmod fails to install on Jessie 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.) -- 762974: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=762974 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: kmod Severity: serious Justification: Dependencies appear to be incomplete X-Debbugs-CC: unclejacks...@gmail.com thanks Heyya Marco, hope you're well, From a bare Jessie docker image: | $ docker run -it --rm debian:testing | # apt-get update apt-get -y install busybox-static kmod | ... | Setting up kmod (18-2) ... | Can't locate autodie.pm in @INC (you may need to install the autodie module) (@INC contains: /etc/perl /usr/local/lib/x86_64-linux-gnu/perl/5.20.0 /usr/local/share/perl/5.20.0 /usr/lib/x86_64-linux-gnu/perl5/5.20 /usr/share/perl5 /usr/lib/x86_64-linux-gnu/perl/5.20 /usr/share/perl/5.20 /usr/local/lib/site_perl .) at -e line 4. | BEGIN failed--compilation aborted at -e line 4. | dpkg: error processing package kmod (--configure): | subprocess installed post-installation script returned error exit status 2 | ... Appears to be very reproducable. Should be reproducable with docker.io and the stock Jessie image (or in a debootstrap chroot, I'd wager) Not sure what's causing this, but it's likely a missing depends or conflicts or something. Thanks so much for working on kmod! Paul -- .''`. Paul Tagliamonte paul...@debian.org | Proud Debian Developer : :' : 4096R / 8F04 9AD8 2C92 066C 7352 D28A 7B58 5B30 807C 2A87 `. `'` http://people.debian.org/~paultag `- http://people.debian.org/~paultag/conduct-statement.txt signature.asc Description: Digital signature ---End Message--- ---BeginMessage--- Source: kmod Source-Version: 18-3 We believe that the bug you reported is fixed in the latest version of kmod, 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 762...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Marco d'Itri m...@linux.it (supplier of updated kmod 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: Sat, 27 Sep 2014 08:01:49 +0200 Source: kmod Binary: kmod module-init-tools libkmod2 libkmod-dev libkmod2-udeb Architecture: source i386 all Version: 18-3 Distribution: unstable Urgency: high Maintainer: Marco d'Itri m...@linux.it Changed-By: Marco d'Itri m...@linux.it Description: kmod - tools for managing Linux kernel modules libkmod-dev - libkmod development files libkmod2 - libkmod shared library libkmod2-udeb - libkmod shared library (udeb) module-init-tools - transitional dummy package (module-init-tools to kmod) Closes: 762974 Changes: kmod (18-3) unstable; urgency=high . * postinst: do not use autodie. (Closes: #762974) * postinst: do not create an empty etc-modules-parameters.conf. Checksums-Sha1: 3b033c03bc6b9cb6136d79cbfc6e565f72e05d2b 1865 kmod_18-3.dsc 09da5aa682b96d7a25a71395da03d96aa7a25fea 10468 kmod_18-3.debian.tar.xz 8ab60720130e8c611545258ca7e651e2af32e813 93494 kmod_18-3_i386.deb 24c124bb963781a98b1e18642f1ed3cf1b3c09a9 2008 module-init-tools_18-3_all.deb db1f906a71ec9c2666921a0ca3ba338a2847f6ca 51846 libkmod2_18-3_i386.deb de86e7ab2215d4003d39c88bd35a88e2278bb6ad 4142 libkmod-dev_18-3_i386.deb c879e95ff9b985df00e244809b87abc7b638ffc4 54092 libkmod2-udeb_18-3_i386.udeb Checksums-Sha256: f16ef133e00db0fa360dcfb0d4723afc31e3803141b5f864e4df6a8b810eaeea 1865 kmod_18-3.dsc 7a55a9d2c97913cdfde6e29d2784b5b82c7fdad6581d466b4aa571eef3270ea2 10468 kmod_18-3.debian.tar.xz 92b9c5c41dc0321de6adf63c8062145f4e13a821c5d4a36b960965d9481825be 93494 kmod_18-3_i386.deb 33ed214b1bc470697b068d812cd8dccdcaca9d8706f287dfee924643984425c1 2008 module-init-tools_18-3_all.deb 57db112761fd4a7b6961161a2c40fea02ffd21b07c72979943a2109b41b54489 51846 libkmod2_18-3_i386.deb d620139dcb917010942b23bbe9bd1ac208fca1898c0b7ad06e852069513a0045 4142 libkmod-dev_18-3_i386.deb c3d41b7dd53848321c594dcc4217050fd33b35ac8bfd9c3a93df23501a8fb801
Bug#762901: marked as done (python-clang-3.6 and python-clang-3.5: error when trying to install together)
Your message dated Sat, 27 Sep 2014 06:22:04 + with message-id e1xxloo-0007sd...@franck.debian.org and subject line Bug#762901: fixed in llvm-toolchain-3.5 1:3.5-3 has caused the Debian Bug report #762901, regarding python-clang-3.6 and python-clang-3.5: error when trying to install together 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.) -- 762901: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=762901 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: python-clang-3.5,python-clang-3.6 Version: python-clang-3.5/1:3.5-2 Version: python-clang-3.6/1:3.6~svn218446-1 Severity: serious User: trei...@debian.org Usertags: edos-file-overwrite Date: 2014-09-26 Architecture: amd64 Distribution: sid Hi, automatic installation tests of packages that share a file and at the same time do not conflict by their package dependency relationships has detected the following problem: Selecting previously unselected package libdb5.3:amd64. (Reading database ... 10877 files and directories currently installed.) Preparing to unpack .../libdb5.3_5.3.28-6_amd64.deb ... Unpacking libdb5.3:amd64 (5.3.28-6) ... Selecting previously unselected package libexpat1:amd64. Preparing to unpack .../libexpat1_2.1.0-6_amd64.deb ... Unpacking libexpat1:amd64 (2.1.0-6) ... Selecting previously unselected package libffi6:amd64. Preparing to unpack .../libffi6_3.1-2_amd64.deb ... Unpacking libffi6:amd64 (3.1-2) ... Selecting previously unselected package libpython2.7-minimal:amd64. Preparing to unpack .../libpython2.7-minimal_2.7.8-7_amd64.deb ... Unpacking libpython2.7-minimal:amd64 (2.7.8-7) ... Selecting previously unselected package python2.7-minimal. Preparing to unpack .../python2.7-minimal_2.7.8-7_amd64.deb ... Unpacking python2.7-minimal (2.7.8-7) ... Selecting previously unselected package mime-support. Preparing to unpack .../mime-support_3.56_all.deb ... Unpacking mime-support (3.56) ... Selecting previously unselected package libpython2.7-stdlib:amd64. Preparing to unpack .../libpython2.7-stdlib_2.7.8-7_amd64.deb ... Unpacking libpython2.7-stdlib:amd64 (2.7.8-7) ... Selecting previously unselected package python2.7. Preparing to unpack .../python2.7_2.7.8-7_amd64.deb ... Unpacking python2.7 (2.7.8-7) ... Selecting previously unselected package python-minimal. Preparing to unpack .../python-minimal_2.7.8-1_amd64.deb ... Unpacking python-minimal (2.7.8-1) ... Selecting previously unselected package libpython-stdlib:amd64. Preparing to unpack .../libpython-stdlib_2.7.8-1_amd64.deb ... Unpacking libpython-stdlib:amd64 (2.7.8-1) ... Selecting previously unselected package python. Preparing to unpack .../python_2.7.8-1_amd64.deb ... Unpacking python (2.7.8-1) ... Selecting previously unselected package python-clang-3.5. Preparing to unpack .../python-clang-3.5_1%3a3.5-2_amd64.deb ... Unpacking python-clang-3.5 (1:3.5-2) ... Selecting previously unselected package python-clang-3.6. Preparing to unpack .../python-clang-3.6_1%3a3.6~svn218446-1_amd64.deb ... Unpacking python-clang-3.6 (1:3.6~svn218446-1) ... dpkg: error processing archive /var/cache/apt/archives/python-clang-3.6_1%3a3.6~svn218446-1_amd64.deb (--unpack): trying to overwrite '/usr/lib/python2.7/dist-packages/clang/enumerations.py', which is also in package python-clang-3.5 1:3.5-2 Processing triggers for man-db (2.7.0.1-1) ... Errors were encountered while processing: /var/cache/apt/archives/python-clang-3.6_1%3a3.6~svn218446-1_amd64.deb E: Sub-process /usr/bin/dpkg returned an error code (1) This is a serious bug as it makes installation fail, and violates sections 7.6.1 and 10.1 of the policy. An optimal solution would consist in only one of the packages installing that file, and renaming or removing the file in the other package. Depending on the circumstances you might also consider Replace relations or file diversions. If the conflicting situation cannot be resolved then, as a last resort, the two packages have to declare a mutual Conflict. Please take into account that Replaces, Conflicts and diversions should only be used when packages provide different implementations for the same functionality. Here is a list of files that are known to be shared by both packages (according to the Contents file for sid/amd64, which may be slightly out of sync): /usr/lib/python2.7/dist-packages/clang/__init__.py /usr/lib/python2.7/dist-packages/clang/cindex.py /usr/lib/python2.7/dist-packages/clang/enumerations.py This bug has been filed against both packages. If you, the maintainers of the two packages in question, have agreed on which of the
Bug#762902: marked as done (python-lldb-3.4 and lldb-3.3: error when trying to install together)
Your message dated Sat, 27 Sep 2014 06:20:32 + with message-id e1xxlmu-0007ir...@franck.debian.org and subject line Bug#762902: fixed in llvm-toolchain-3.4 1:3.4.2-10 has caused the Debian Bug report #762902, regarding python-lldb-3.4 and lldb-3.3: error when trying to install together 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.) -- 762902: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=762902 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: lldb-3.3,python-lldb-3.4 Version: lldb-3.3/1:3.3-16 Version: python-lldb-3.4/1:3.4.2-9 Severity: serious User: trei...@debian.org Usertags: edos-file-overwrite Date: 2014-09-26 Architecture: amd64 Distribution: sid Hi, automatic installation tests of packages that share a file and at the same time do not conflict by their package dependency relationships has detected the following problem: Selecting previously unselected package libdb5.3:amd64. (Reading database ... 10877 files and directories currently installed.) Preparing to unpack .../libdb5.3_5.3.28-6_amd64.deb ... Unpacking libdb5.3:amd64 (5.3.28-6) ... Selecting previously unselected package libbsd0:amd64. Preparing to unpack .../libbsd0_0.7.0-2_amd64.deb ... Unpacking libbsd0:amd64 (0.7.0-2) ... Selecting previously unselected package libedit2:amd64. Preparing to unpack .../libedit2_3.1-20140620-2_amd64.deb ... Unpacking libedit2:amd64 (3.1-20140620-2) ... Selecting previously unselected package libgmp10:amd64. Preparing to unpack .../libgmp10_2%3a6.0.0+dfsg-6_amd64.deb ... Unpacking libgmp10:amd64 (2:6.0.0+dfsg-6) ... Selecting previously unselected package libisl10:amd64. Preparing to unpack .../libisl10_0.12.2-2_amd64.deb ... Unpacking libisl10:amd64 (0.12.2-2) ... Selecting previously unselected package libcloog-isl4:amd64. Preparing to unpack .../libcloog-isl4_0.18.2-1_amd64.deb ... Unpacking libcloog-isl4:amd64 (0.18.2-1) ... Selecting previously unselected package libexpat1:amd64. Preparing to unpack .../libexpat1_2.1.0-6_amd64.deb ... Unpacking libexpat1:amd64 (2.1.0-6) ... Selecting previously unselected package libffi6:amd64. Preparing to unpack .../libffi6_3.1-2_amd64.deb ... Unpacking libffi6:amd64 (3.1-2) ... Selecting previously unselected package libllvm3.3:amd64. Preparing to unpack .../libllvm3.3_1%3a3.3-16_amd64.deb ... Unpacking libllvm3.3:amd64 (1:3.3-16) ... Selecting previously unselected package libpython2.7-minimal:amd64. Preparing to unpack .../libpython2.7-minimal_2.7.8-7_amd64.deb ... Unpacking libpython2.7-minimal:amd64 (2.7.8-7) ... Selecting previously unselected package mime-support. Preparing to unpack .../mime-support_3.56_all.deb ... Unpacking mime-support (3.56) ... Selecting previously unselected package libpython2.7-stdlib:amd64. Preparing to unpack .../libpython2.7-stdlib_2.7.8-7_amd64.deb ... Unpacking libpython2.7-stdlib:amd64 (2.7.8-7) ... Selecting previously unselected package libpython2.7:amd64. Preparing to unpack .../libpython2.7_2.7.8-7_amd64.deb ... Unpacking libpython2.7:amd64 (2.7.8-7) ... Selecting previously unselected package python2.7-minimal. Preparing to unpack .../python2.7-minimal_2.7.8-7_amd64.deb ... Unpacking python2.7-minimal (2.7.8-7) ... Selecting previously unselected package python2.7. Preparing to unpack .../python2.7_2.7.8-7_amd64.deb ... Unpacking python2.7 (2.7.8-7) ... Selecting previously unselected package python-minimal. Preparing to unpack .../python-minimal_2.7.8-1_amd64.deb ... Unpacking python-minimal (2.7.8-1) ... Selecting previously unselected package libpython-stdlib:amd64. Preparing to unpack .../libpython-stdlib_2.7.8-1_amd64.deb ... Unpacking libpython-stdlib:amd64 (2.7.8-1) ... Selecting previously unselected package python. Preparing to unpack .../python_2.7.8-1_amd64.deb ... Unpacking python (2.7.8-1) ... Selecting previously unselected package libjsoncpp0. Preparing to unpack .../libjsoncpp0_0.6.0~rc2-3_amd64.deb ... Unpacking libjsoncpp0 (0.6.0~rc2-3) ... Selecting previously unselected package libffi-dev:amd64. Preparing to unpack .../libffi-dev_3.1-2_amd64.deb ... Unpacking libffi-dev:amd64 (3.1-2) ... Selecting previously unselected package binfmt-support. Preparing to unpack .../binfmt-support_2.1.5-1_amd64.deb ... Unpacking binfmt-support (2.1.5-1) ... Selecting previously unselected package llvm-3.3-runtime. Preparing to unpack .../llvm-3.3-runtime_1%3a3.3-16_amd64.deb ... Unpacking llvm-3.3-runtime (1:3.3-16) ... Selecting previously unselected package llvm-3.3. Preparing to unpack .../llvm-3.3_1%3a3.3-16_amd64.deb ... Unpacking llvm-3.3 (1:3.3-16) ... Selecting previously
Bug#763016: Crash when establishing connection with Skype
Package: pidgin-skype
Version: 20130613+svn660+dfsg-1
Severity: grave
Tags: patch
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Hi!
Since some time, pidgin-skype is unable to establish communication
with Skype and crashes when it tries to. This is 100% reproducible on
my setup. This bug seems to be already reported upstream:
https://code.google.com/p/skype4pidgin/issues/detail?id=239
Here is a backtrace:
#0 0x74764077 in __GI_raise (sig=sig@entry=6) at
../nptl/sysdeps/unix/sysv/linux/raise.c:56
resultvar = 0
pid = 28522
selftid = 28522
#1 0x74765458 in __GI_abort () at abort.c:89
save_stage = 2
act = {
__sigaction_handler = {
sa_handler = 0x5622f2b0,
sa_sigaction = 0x5622f2b0
},
sa_mask = {
__val = {140737307444736, 93825003648256, 140737351949831, 5, 0,
44, 140737294589224, 0, 93825003648256, 93825000110608, 140737351975717, 44,
140737295450653, 44, 140737308113920, 0}
},
sa_flags = -189974640,
sa_restorer = 0x7541bce0
}
sigs = {
__val = {32, 0 repeats 15 times}
}
#2 0x753bb95d in g_mutex_unlock_slowpath (mutex=optimized out,
prev=optimized out) at
/build/glib2.0-Dv_k6u/glib2.0-2.42.0/./glib/gthread-posix.c:1327
No locals.
#3 0x753bc38e in g_mutex_unlock (mutex=optimized out) at
/build/glib2.0-Dv_k6u/glib2.0-2.42.0/./glib/gthread-posix.c:1350
prev = optimized out
#4 0x753bc5ce in g_cond_wait_until (cond=0x56037500,
mutex=0x55cd7a10, end_time=optimized out) at
/build/glib2.0-Dv_k6u/glib2.0-2.42.0/./glib/gthread-posix.c:1442
now = {
tv_sec = 273990,
tv_nsec = 37210622
}
span = {
tv_sec = 9,
tv_nsec = 85378
}
sampled = 0
res = optimized out
#5 0x7534a8ca in g_cond_timed_wait (cond=optimized out,
mutex=optimized out, abs_time=abs_time@entry=0x7fffbfa0) at
/build/glib2.0-Dv_k6u/glib2.0-2.42.0/./glib/deprecated/gthread-deprecated.c:1578
end_time = optimized out
#6 0x7fffe5207fbc in skype_send_message
(message_format=message_format@entry=0x7fffe520fc7c NAME %s) at
skype_messaging.c:235
next_message_num = 1
cur_message_num = 0
message = 0x561cc3e0 \340\304\034VUU
return_msg = optimized out
args = {{
gp_offset = 8,
fp_offset = 48,
overflow_arg_area = 0x7fffc090,
reg_save_area = 0x7fffbfd0
}}
condition_result = optimized out
endtime = {
tv_sec = 1411799860,
tv_usec = 220479
}
#7 0x7fffe5209efd in skype_login_part2 (acct=0x55e2dbd0,
acct@entry=error reading variable: value has been optimized out) at
libskype.c:1747
reply = optimized out
gc = 0x561765e0
missedmessagestimout = 0
#8 0x75378613 in g_timeout_dispatch (source=0x5622f2b0,
callback=optimized out, user_data=optimized out) at
/build/glib2.0-Dv_k6u/glib2.0-2.42.0/./glib/gmain.c:4520
timeout_source = 0x5622f2b0
again = optimized out
#9 0x75377b6d in g_main_dispatch (context=0x5586ccf0) at
/build/glib2.0-Dv_k6u/glib2.0-2.42.0/./glib/gmain.c:3111
dispatch = 0x75378600 g_timeout_dispatch
prev_source = 0x0
was_in_call = 0
user_data = 0x55e2dbd0
callback = 0x7fffe5209eb0 skype_login_part2
cb_funcs = optimized out
cb_data = 0x561cc7d0
need_destroy = optimized out
source = 0x5622f2b0
current = 0x56063fc0
i = 12
#10 g_main_context_dispatch (context=context@entry=0x5586ccf0) at
/build/glib2.0-Dv_k6u/glib2.0-2.42.0/./glib/gmain.c:3710
No locals.
#11 0x75377f48 in g_main_context_iterate (context=0x5586ccf0,
block=block@entry=1, dispatch=dispatch@entry=1, self=optimized out) at
/build/glib2.0-Dv_k6u/glib2.0-2.42.0/./glib/gmain.c:3781
max_priority = 0
timeout = 0
some_ready = 1
nfds = optimized out
allocated_nfds = 8
fds = 0x55d551e0
#12 0x75378272 in g_main_loop_run (loop=0x561b9360) at
/build/glib2.0-Dv_k6u/glib2.0-2.42.0/./glib/gmain.c:3975
__FUNCTION__ = g_main_loop_run
#13 0x76615bc7 in gtk_main () from
/usr/lib/x86_64-linux-gnu/libgtk-x11-2.0.so.0
No symbol table info available.
#14 0x5558f0d1 in main (argc=1, argv=0x7fffe6c8) at
/build/pidgin-lGhYHj/pidgin-2.10.9/./pidgin/gtkmain.c:933
opt_help = -15680
opt_version = 1439729824
opt_config_dir_arg = 0x0
accounts = 0x0
sigset = {
__val = {82950, 0 repeats 15 times}
}
errmsg = '\000' repeats 760 times...
signal_channel = 0x0
signal_status = G_IO_STATUS_ERROR
error = 0x0
opt = 0
Processed: tagging 763012
Processing commands for cont...@bugs.debian.org: tags 763012 - security Bug #763012 [bash] bash: 'dpkg --purge bash' should work, rather than give this: Removed tag(s) security. thanks Stopping processing here. Please contact me if you need assistance. -- 763012: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=763012 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#763012: marked as done (bash: 'dpkg --purge bash' should work, rather than give this:)
Your message dated Sat, 27 Sep 2014 09:11:53 +0200 with message-id f16074c648595e9c21274693c439382c.squir...@aphrodite.kinkhorst.nl and subject line Re: Bug#763012: bash: 'dpkg --purge bash' should work, rather than give this: has caused the Debian Bug report #763012, regarding bash: 'dpkg --purge bash' should work, rather than give this: 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.) -- 763012: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=763012 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: bash Version: 4.2+dfsg-0.1+deb7u3 Severity: critical Tags: security Justification: breaks the whole system Dear Maintainer, Please consider allowing the following to work in (some) situations: # dpkg --purge bash dpkg: error processing bash (--purge): This is an essential package - it should not be removed. Errors were encountered while processing: bash -- System Information: Debian Release: 7.6 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 3.17.0-rc1+ (SMP w/2 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages bash depends on: ii base-files 7.1wheezy6 ii dash 0.5.7-3 ii debianutils 4.3.2 ii libc62.13-38+deb7u4 ii libtinfo55.9-10 Versions of packages bash recommends: ii bash-completion 1:2.0-1 Versions of packages bash suggests: pn bash-doc none -- no debconf information ---End Message--- ---BeginMessage--- Hi Troy, On Sat, September 27, 2014 06:56, Troy Benjegerdes wrote: Package: bash Version: 4.2+dfsg-0.1+deb7u3 Severity: critical Tags: security Justification: breaks the whole system Dear Maintainer, Please consider allowing the following to work in (some) situations: # dpkg --purge bash dpkg: error processing bash (--purge): This is an essential package - it should not be removed. Errors were encountered while processing: bash So what, besides the fact it's never really been tested until I just did it,is the problem with running an unbashed debian system? This is expected behaviour because bash is part of the essential set. You may read more about the essential set in Debian Policy, but in short these are packages that are ensured to be present on any Debian system. Although the recent advent of new shells has changed this a bit, this was surely an obviously correct thing to do in the early days. One consequence of that is that packages making use of bash do not declare an explicit dependency on it. This means that you can indeed uninstall it and no packages will need to be removed. However, of the 10.000's packages in Debian there are probably thousands that use a !/bin/bash script somewhere which will then immediately break. Essential or not, there will always be large numbers of Debian systems that are going to require bash, so it will always be a top priority of Debian to address any security issues in it immediately. Removing bash from the essential set is a herculean task, not impossible, but definitely not something that needs to be tracked in an RC bug. If you want to take on that work, you'd probably better start a discussion on debian-devel. Cheers, Thijs---End Message---
Processed: forcibly merging 762838 762755
Processing commands for cont...@bugs.debian.org: forcemerge 762838 762755 Bug #762838 [bind9] [bind9] Crash after update: “mem.c:1321: REQUIRE(ptr != ((void *)0)) failed, back trace” Bug #762876 [bind9] named assertion failure in bind9 1:9.9.5.dfsg-4.1 in mem.c Bug #762755 [bind9] bind 9.9.5-4.1: assertion failure Severity set to 'grave' from 'important' Bug #762876 [bind9] named assertion failure in bind9 1:9.9.5.dfsg-4.1 in mem.c Merged 762755 762838 762876 thanks Stopping processing here. Please contact me if you need assistance. -- 762755: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=762755 762838: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=762838 762876: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=762876 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 762838 762805
Processing commands for cont...@bugs.debian.org: forcemerge 762838 762805 Bug #762838 [bind9] [bind9] Crash after update: “mem.c:1321: REQUIRE(ptr != ((void *)0)) failed, back trace” Bug #762755 [bind9] bind 9.9.5-4.1: assertion failure Bug #762876 [bind9] named assertion failure in bind9 1:9.9.5.dfsg-4.1 in mem.c Bug #762805 [bind9] bind9 process crashes within a few minutes of restarting Severity set to 'grave' from 'important' Bug #762755 [bind9] bind 9.9.5-4.1: assertion failure Bug #762876 [bind9] named assertion failure in bind9 1:9.9.5.dfsg-4.1 in mem.c Merged 762755 762805 762838 762876 thanks Stopping processing here. Please contact me if you need assistance. -- 762755: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=762755 762805: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=762805 762838: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=762838 762876: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=762876 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 762838 762800
Processing commands for cont...@bugs.debian.org: forcemerge 762838 762800 Bug #762838 [bind9] [bind9] Crash after update: “mem.c:1321: REQUIRE(ptr != ((void *)0)) failed, back trace” Bug #762755 [bind9] bind 9.9.5-4.1: assertion failure Bug #762805 [bind9] bind9 process crashes within a few minutes of restarting Bug #762876 [bind9] named assertion failure in bind9 1:9.9.5.dfsg-4.1 in mem.c Bug #762800 [bind9] bind9 crashes Severity set to 'grave' from 'normal' Bug #762755 [bind9] bind 9.9.5-4.1: assertion failure Bug #762805 [bind9] bind9 process crashes within a few minutes of restarting Bug #762876 [bind9] named assertion failure in bind9 1:9.9.5.dfsg-4.1 in mem.c Merged 762755 762800 762805 762838 762876 thanks Stopping processing here. Please contact me if you need assistance. -- 762755: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=762755 762800: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=762800 762805: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=762805 762838: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=762838 762876: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=762876 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#763013: marked as done (isc-dhcp-client depends on /bin/bash, not /bin/sh)
Your message dated Sat, 27 Sep 2014 09:17:47 +0200 with message-id 201409270917.47741.th...@debian.org and subject line Re: isc-dhcp-client depends on /bin/bash, not /bin/sh has caused the Debian Bug report #763013, regarding isc-dhcp-client depends on /bin/bash, not /bin/sh 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.) -- 763013: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=763013 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: isc-dhcp-client Version: 4.2.2.dfsg.1-5+deb70u6 Severity: critical Tags: patch Justification: breaks the whole system Remove dependency on bash. Fixes ifup/ifdown with dhcp on unbashed-system. Also see bug 763012 --- dhclient-script.bad 2014-09-27 00:21:48.377145358 -0500 +++ /sbin/dhclient-script 2014-09-27 00:15:31.508982652 -0500 @@ -1,4 +1,4 @@ -#!/bin/bash +#!/bin/sh # dhclient-script for Linux. Dan Halbert, March, 1997. # Updated for Linux 2.[12] by Brian J. Murrell, January 1999. -- System Information: Debian Release: 7.6 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 3.2.0-4-amd64 (SMP w/2 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages isc-dhcp-client depends on: ii debianutils 4.3.2 ii iproute 20120521-3+b3 ii isc-dhcp-common 4.2.2.dfsg.1-5+deb70u6 ii libc62.13-38+deb7u4 isc-dhcp-client recommends no packages. Versions of packages isc-dhcp-client suggests: ii avahi-autoipd 0.6.31-2 pn resolvconf none -- no debconf information ---End Message--- ---BeginMessage--- Hi Troy, Severity: critical Tags: patch Justification: breaks the whole system Remove dependency on bash. Fixes ifup/ifdown with dhcp on unbashed-system. This is not a critical bug since using bash does not 'break the whole system'. The patch is also not correct because this script is marked /bin/bash for a reason, because it's not fully posix compliant and therefore will not run with just any /bin/sh. It's a valid request for the script to be modified to change its interpreter, it's already filed at #762923. Maybe you can help develop a tested patch for that to move it forward. Cheers, Thijs---End Message---
Bug#763018: /etc/cron.monthly/ieee-data: cron job modifies files shipped in the package
Package: ieee-data Version: 20140828.1 Severity: serious I got a warning from debsums that the following files in ieee-data had been modified. Packages should not modify files shipped in the deb. These files should be moved to /usr and the maintainer scripts should copy the files to /var if the files in /var are not present or are older than the files in /usr. This is so that people who disable the cron job for privacy reasons can still get updates. The maintainer scripts should also remove the files from /var when the package is removed/purged. pabs@chianamo ~ $ dpkg -L ieee-data | grep /var /var /var/lib /var/lib/ieee-data /var/lib/ieee-data/oui.txt /var/lib/ieee-data/.lastupdate /var/lib/ieee-data/iab.txt pabs@chianamo ~ $ sudo debsums -s ieee-data debsums: changed file /var/lib/ieee-data/.lastupdate (from ieee-data package) debsums: changed file /var/lib/ieee-data/iab.txt (from ieee-data package) debsums: changed file /var/lib/ieee-data/oui.txt (from ieee-data package) -- System Information: Debian Release: jessie/sid APT prefers testing APT policy: (900, 'testing'), (800, 'unstable'), (700, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 3.16-2-amd64 (SMP w/4 CPU cores) Locale: LANG=en_AU.UTF-8, LC_CTYPE=en_AU.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages ieee-data depends on: ii curl 7.38.0-1 ii libwww-perl 6.08-1 ii wget 1.15-1+b1 ieee-data recommends no packages. ieee-data suggests no packages. -- no debconf information -- debsums errors found: debsums: changed file /var/lib/ieee-data/.lastupdate (from ieee-data package) debsums: changed file /var/lib/ieee-data/iab.txt (from ieee-data package) -- bye, pabs https://wiki.debian.org/PaulWise signature.asc Description: This is a digitally signed message part
Processed: Re: Bug#763019: doxygen fails to run on armel, armhf, i386, mipsel, powerpc, ppc64el and s390x
Processing control commands: reassign -1 libclang1-3.5 Bug #763019 [doxygen] doxygen fails to run on armel, armhf, i386, mipsel, powerpc, ppc64el and s390x Bug reassigned from package 'doxygen' to 'libclang1-3.5'. No longer marked as found in versions doxygen/1.8.8-3. Ignoring request to alter fixed versions of bug #763019 to the same values previously set forcemerge 762959 -1 Bug #762959 [libclang1-3.5] ABI break: missing libclang.so.1 Bug #762994 [libclang1-3.5] doxygen: makes xbmc FTBFS Bug #763011 [libclang1-3.5] doxygen: uses libclang but does not find it Bug #763019 [libclang1-3.5] doxygen fails to run on armel, armhf, i386, mipsel, powerpc, ppc64el and s390x Severity set to 'serious' from 'important' Added indication that 763019 affects doxygen Marked as found in versions llvm-toolchain-3.5/1:3.5-2. Bug #762994 [libclang1-3.5] doxygen: makes xbmc FTBFS Bug #763011 [libclang1-3.5] doxygen: uses libclang but does not find it Merged 762959 762994 763011 763019 -- 762959: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=762959 762994: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=762994 763011: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=763011 763019: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=763019 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#763010: marked as done (xchat-guile: debian/control still depends on guile-1.8)
Your message dated Sat, 27 Sep 2014 09:25:25 +0200 with message-id 20140927072525.ga18...@capsaicin.mamane.lu and subject line Re: Bug#763010: xchat-guile: debian/control still depends on guile-1.8 has caused the Debian Bug report #763010, regarding xchat-guile: debian/control still depends on guile-1.8 to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 763010: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=763010 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: xchat-guile Version: 0.3-3 Severity: serious I suspect this was just overlooked in the 2.0 migration. Thanks -- Rob Browning rlb @defaultvalue.org and @debian.org GPG as of 2011-07-10 E6A9 DA3C C9FD 1FF8 C676 D2C4 C0F0 39E9 ED1B 597A GPG as of 2002-11-03 14DD 432F AE39 534D B592 F9A0 25C8 D377 8C7E 73A4 ---End Message--- ---BeginMessage--- Version: 0.3-4 Forgot to close in changelog: xchat-guile (0.3-4) unstable; urgency=low * depend on Guile 2.0 instead of Guile 1.8 * Bump up Standards-Version * Remove dependency on obsolete hardening-includes (was already using dpkg-buildflags) -- Lionel Elie Mamane lmam...@debian.org Sat, 27 Sep 2014 08:51:37 +0200---End Message---
Bug#763010: xchat-guile: debian/control still depends on guile-1.8
On Fri, Sep 26, 2014 at 10:41:15PM -0500, Rob Browning wrote: Package: xchat-guile Version: 0.3-3 Severity: serious I suspect this was just overlooked in the 2.0 migration. Thank you for your bug report. Indeed, this dependency was left there, but xchat-guile was already using guile 2.0. It turns out it doesn't even need the guile-2.0 package (which contains the command-line interface interpreter) since it uses the library directly. -- Lionel -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#721421: libdevel-bt-perl: FTBFS on armel, hurd-i386, kfreebsd-amd64
tag 721421 patch thanks On Fri, Sep 26, 2014 at 11:12:06PM +0300, Niko Tyni wrote: The problem apparently happens when the timeout in the select loop (one second) triggers before execvp() has been called. I can reproduce a similar race on my x86_64 machine by inserting a sleep(1) call right before the execvp() call. I still haven't got to the bottom of it, but it looks like the gdb output is lost somewhere with select() timeouting (and returning zero) on subsequent calls too even though gdb has happily written to the pipe. Further investigation with strace shows that the fd_set passed into select() becomes empty if execvp() happens after the first select() call. I was able to reproduce this with gdb replaced by a trivial program that just prints to stdout (which greatly helped debugging.) So I suppose the execvp() call somehow invalidates the fd set? I haven't found an explanation for this observed behaviour. The closest thing I was able to find was this in the select_tut(2) Linux manual page (on Debian sid if that matters): 11. Since select() modifies its file descriptor sets, if the call is being used in a loop, then the sets must be reinitialized before each call. Reinitializing the set in the loop fixes it and seems to be the correct thing to do anyway. Patch attached, this makes it work for me on both mips and amd64. -- Niko Tyni nt...@debian.org From 88d953d71051fe45a4983f1cce9810f7ae942c56 Mon Sep 17 00:00:00 2001 From: Niko Tyni nt...@debian.org Date: Sat, 27 Sep 2014 10:35:27 +0300 Subject: [PATCH] Reinitialize the fd set in the select loop This fixes test failures on slow hosts. It looks like execvp() happening in the child after the first select() call invalidates the set. Quoting the Linux select_tut(2) manual page: 11. Since select() modifies its file descriptor sets, if the call is being used in a loop, then the sets must be reinitialized before each call. Bug-Debian: https://bugs.debian.org/721421 --- bt.xs | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/bt.xs b/bt.xs index 6b9fed6..f892c8c 100644 --- a/bt.xs +++ b/bt.xs @@ -88,9 +88,6 @@ stack_trace (char **args) _exit(0); } -FD_ZERO(fdset); -FD_SET(out_fd[0], fdset); - write(in_fd[1], thread apply all backtrace\n, 27); write(in_fd[1], quit\n, 5); @@ -105,6 +102,9 @@ stack_trace (char **args) tv.tv_sec = 1; tv.tv_usec = 0; +FD_ZERO(fdset); +FD_SET(out_fd[0], fdset); + sel = select(FD_SETSIZE, fdset, NULL, NULL, tv); if (sel == -1) break; -- 2.1.1
Processed: Re: Bug#762520: Bug report about the package clearlooks-phenix-theme 5.0.2-1 (unstable)
Processing control commands: severity -1 normal Bug #762520 [clearlooks-phenix-theme] clearlooks-phenix-theme: theme is completely broken since the last GTK update Severity set to 'normal' from 'grave' -- 762520: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=762520 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#762520: Bug report about the package clearlooks-phenix-theme 5.0.2-1 (unstable)
Control: severity -1 normal Hello, I've uploaded 5.0.2-2, it should fix most of the issues. I'm aware of colours not fully matching, minor glitches with scrollbars and pop-over menus, but this is all I can do for now. I'm reducing severity to normal as the package should be useful now (even though bug not fixed yet). -- Cheers, Andrew signature.asc Description: PGP signature
Bug#762984: initramfs-tools: Alert! /dev/vg0/usr does not exist
On Fri, 26 Sep 2014 22:03:29 +0200 Elimar Riesebieter riese...@lxtec.de wrote: Package: initramfs-tools Version: 0.117 Severity: normal LVM2 running on top of RAID1. Running /usr on a separate raid partition is not recognized too. Verified that on an other System: Alert! /dev/md5 does not exist Elimar -- what IMHO then? IMHO - Inhalation of a Multi-leafed Herbal Opiate ;) --posting from alex in debian-user-- -- 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 762999 is important
Processing commands for cont...@bugs.debian.org: severity 762999 important Bug #762999 [xorg] xorg: X fails to initialize - no screens found Severity set to 'important' from 'serious' thanks Stopping processing here. Please contact me if you need assistance. -- 762999: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=762999 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#762740: [Pkg-utopia-maintainers] Bug#762740: No network devices available
Control: severity -1 important Control: tags -1 moreinfo Am 26.09.2014 um 14:52 schrieb Michal Hocko: On Wed, Sep 24, 2014 at 10:31:41PM +0200, Michal Hocko wrote: Package: network-manager Version: 0.9.4.0-10 Severity: serious Hi, it seems that network-manager stopped being able to handle my lan and wlan devices properly after last series of updates (which don't seem to be directly related to the nm packages). Although I can get connected to both wired and wireless (to the system wide saved networks) nm-applet (network-manager-gnome package) claims that there are No network devices available so it doesn't give me access to neither of the saved networks nor to the saved VPN configurations. What kind of desktop environment is that? How do you start it? Is that problem reproducible after a reboot or after you've re-logged in? Michael -- Why is it that all of the instruments seeking intelligent life in the universe are pointed away from Earth? signature.asc Description: OpenPGP digital signature
Processed: Re: [Pkg-utopia-maintainers] Bug#762740: No network devices available
Processing control commands: severity -1 important Bug #762740 [network-manager] No network devices available Severity set to 'important' from 'serious' tags -1 moreinfo Bug #762740 [network-manager] No network devices available Added tag(s) moreinfo. -- 762740: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=762740 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#762275: Solution
Hi, I also have the same (or similar) problem. This is what I found. The solution that worked for me is at the end of the mail. # dpkg -i /var/cache/apt/archives/systemd_215-4_amd64.deb (Reading database ... 729731 files and directories currently installed.) Preparing to unpack .../systemd_215-4_amd64.deb ... Unpacking systemd (215-4) over (215-4) ... Setting up systemd (215-4) ... dpkg: error processing package systemd (--install): subprocess installed post-installation script returned error exit status 1 Processing triggers for dbus (1.8.6-2) ... Processing triggers for man-db (2.6.7.1-1) ... Errors were encountered while processing: systemd # dpkg -i -D2 /var/cache/apt/archives/systemd_215-4_amd64.deb (Reading database ... 729731 files and directories currently installed.) Preparing to unpack .../systemd_215-4_amd64.deb ... D02: fork/exec /var/lib/dpkg/info/systemd.prerm ( upgrade 215-4 ) D02: fork/exec /var/lib/dpkg/tmp.ci/preinst ( upgrade 215-4 ) Unpacking systemd (215-4) over (215-4) ... D02: fork/exec /var/lib/dpkg/info/systemd.postrm ( upgrade 215-4 ) D02: process_archive info installed /var/lib/dpkg/tmp.ci/postinst as /var/lib/dpkg/info/systemd.postinst D02: process_archive info installed /var/lib/dpkg/tmp.ci/md5sums as /var/lib/dpkg/info/systemd.md5sums D02: process_archive info installed /var/lib/dpkg/tmp.ci/conffiles as /var/lib/dpkg/info/systemd.conffiles D02: process_archive info installed /var/lib/dpkg/tmp.ci/triggers as /var/lib/dpkg/info/systemd.triggers D02: process_archive info installed /var/lib/dpkg/tmp.ci/preinst as /var/lib/dpkg/info/systemd.preinst D02: process_archive info installed /var/lib/dpkg/tmp.ci/prerm as /var/lib/dpkg/info/systemd.prerm D02: process_archive info installed /var/lib/dpkg/tmp.ci/postrm as /var/lib/dpkg/info/systemd.postrm D02: process_archive tmp.ci script/file '..' contains dot D02: process_archive tmp.ci script/file '/var/lib/dpkg/tmp.ci/control' is control D02: process_archive tmp.ci script/file '.' contains dot Setting up systemd (215-4) ... D02: fork/exec /var/lib/dpkg/info/systemd.postinst ( configure 208-8 ) dpkg: error processing package systemd (--install): subprocess installed post-installation script returned error exit status 1 Processing triggers for dbus (1.8.6-2) ... D02: fork/exec /var/lib/dpkg/info/dbus.postinst ( triggered /usr/share/dbus-1/system-services /etc/dbus-1/system.d ) Processing triggers for man-db (2.6.7.1-1) ... D02: fork/exec /var/lib/dpkg/info/man-db.postinst ( triggered /usr/share/man ) Errors were encountered while processing: systemd # sh -x /var/lib/dpkg/info/systemd.postinst configure 208-8 + set -e + [ configure = triggered ] + dpkg --compare-versions 208-8 lt 214-1 + systemctl enable getty@tty1.service + systemctl enable remote-fs.target + dpkg --compare-versions 208-8 lt 204-1 + dpkg --compare-versions 208-8 lt 33-1 + dpkg --compare-versions 208-8 lt 204-9 + dpkg --compare-versions 208-8 lt 204-8 + dpkg --compare-versions 208-8 lt 40-1 + systemd-machine-id-setup + addgroup --quiet --system systemd-journal After running 'delgroup systemd-journal', it was possible install the package. -Michal -- 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 757605 757821
Processing commands for cont...@bugs.debian.org: forcemerge 757605 757821 Bug #757605 [remmina] libfreerdp1: changes to soname cause remmina RDP plugin to fail Bug #757608 [remmina] FTBFS: needs newer git-snapshot to compile with freerdp=1.1.0 Bug #757926 [remmina] ABI changes in libfreerdp1 makes other software break Unable to merge bugs because: package of #757821 is 'remmina-plugin-rdp' not 'remmina' Failed to forcibly merge 757605: Did not alter merged bugs thanks Stopping processing here. Please contact me if you need assistance. -- 757605: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=757605 757608: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=757608 757821: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=757821 757926: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=757926 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: severity of 763005 is serious
Processing commands for cont...@bugs.debian.org: severity 763005 serious Bug #763005 [installation-guide-amd64] installation-guide-amd64: website for wheezy leads to jessie installation guide Severity set to 'serious' from 'normal' thanks Stopping processing here. Please contact me if you need assistance. -- 763005: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=763005 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#762275: Solution
Am 27.09.2014 um 13:08 schrieb Michal Sojka: + addgroup --quiet --system systemd-journal After running 'delgroup systemd-journal', it was possible install the package. With the amount of information from the original bug submitter, it's hard to tell if this is the same issue as yours. In your case, you apparently had an existing systemd-journal group, which was not a system group, so addgroup errors out. This is not a bug in the Debian package. Most likely you had created that group yourself in the past. Michael -- Why is it that all of the instruments seeking intelligent life in the universe are pointed away from Earth? signature.asc Description: OpenPGP digital signature
Bug#721421: libdevel-bt-perl: FTBFS on armel, hurd-i386, kfreebsd-amd64
On Sat, Sep 27, 2014 at 9:48 AM, Niko Tyni nt...@debian.org wrote: tag 721421 patch thanks On Fri, Sep 26, 2014 at 11:12:06PM +0300, Niko Tyni wrote: The problem apparently happens when the timeout in the select loop (one second) triggers before execvp() has been called. I can reproduce a similar race on my x86_64 machine by inserting a sleep(1) call right before the execvp() call. I still haven't got to the bottom of it, but it looks like the gdb output is lost somewhere with select() timeouting (and returning zero) on subsequent calls too even though gdb has happily written to the pipe. Further investigation with strace shows that the fd_set passed into select() becomes empty if execvp() happens after the first select() call. I was able to reproduce this with gdb replaced by a trivial program that just prints to stdout (which greatly helped debugging.) So I suppose the execvp() call somehow invalidates the fd set? I haven't found an explanation for this observed behaviour. The closest thing I was able to find was this in the select_tut(2) Linux manual page (on Debian sid if that matters): 11. Since select() modifies its file descriptor sets, if the call is being used in a loop, then the sets must be reinitialized before each call. Reinitializing the set in the loop fixes it and seems to be the correct thing to do anyway. Patch attached, this makes it work for me on both mips and amd64. Right, that is definitely a bug. Haven't used select in such a long time that I had looked over that insanity. Leon
Processed: Re: Bug#753773: consolekit: FTBFS on kfreebsd-any
Processing commands for cont...@bugs.debian.org: reassign 753773 src:kfreebsd-kernel-headers Bug #753773 [src:consolekit] consolekit: FTBFS on kfreebsd-any Bug reassigned from package 'src:consolekit' to 'src:kfreebsd-kernel-headers'. No longer marked as found in versions consolekit/0.4.6-5. Ignoring request to alter fixed versions of bug #753773 to the same values previously set affects 753773 consolekit Bug #753773 [src:kfreebsd-kernel-headers] consolekit: FTBFS on kfreebsd-any Added indication that 753773 affects consolekit found 753773 kfreebsd-kernel-headers/9.2~8 Bug #753773 [src:kfreebsd-kernel-headers] consolekit: FTBFS on kfreebsd-any Marked as found in versions kfreebsd-kernel-headers/9.2~8. fixed 753773 kfreebsd-kernel-headers/10.0-7 Bug #753773 [src:kfreebsd-kernel-headers] consolekit: FTBFS on kfreebsd-any The source kfreebsd-kernel-headers and version 10.0-7 do not appear to match any binary packages Marked as fixed in versions kfreebsd-kernel-headers/10.0-7. close 753773 Bug #753773 [src:kfreebsd-kernel-headers] consolekit: FTBFS on kfreebsd-any Marked Bug as done user debian-...@lists.debian.org Setting user to debian-...@lists.debian.org (was ste...@pyro.eu.org). usertags 753773 + kfreebsd There were no usertags set. Usertags are now: kfreebsd. thanks Stopping processing here. Please contact me if you need assistance. -- 753773: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=753773 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#753773: consolekit: FTBFS on kfreebsd-any
reassign 753773 src:kfreebsd-kernel-headers affects 753773 consolekit found 753773 kfreebsd-kernel-headers/9.2~8 fixed 753773 kfreebsd-kernel-headers/10.0-7 close 753773 user debian-...@lists.debian.org usertags 753773 + kfreebsd thanks Hi, This was a problem in kfreebsd-kernel-headers fixed long ago. Built successfully when given back for rebuild. 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
Bug#760638: fixed in flashplugin-nonfree 1:3.2+wheezy1
Hello, (reportbug is still borken per Bug #758619 so this will have to do; I can provide more information on my system if necessary.) I ran into this problem today both with flashplugin-nonfree:i386=1:3.5 and =1:3.6 because I have ca-certificates=20140325 installed but set it to ask me for each certificate. And the one that I needed, mozilla/UTN_USERFirst_Hardware_Root_CA.crt was not activated. I can reproduce this by deactivating it again and then: --- # dpkg-reconfigure flashplugin-nonfree ERROR: wget failed to download http://people.debian.org/~bartm/flashplugin-nonfree/D5C0FC14/get-upstream-version.pl.gz.pgp More information might be available at: http://wiki.debian.org/FlashPlayer # wget http://people.debian.org/~bartm/flashplugin-nonfree/D5C0FC14/get-upstream-version.pl.gz.pgp --2014-09-27 13:54:57-- http://people.debian.org/~bartm/flashplugin-nonfree/D5C0FC14/get-upstream-version.pl.gz.pgp Resolving people.debian.org (people.debian.org)... 5.153.231.30, 2001:41c8:1000:21::21:30 Connecting to people.debian.org (people.debian.org)|5.153.231.30|:80... connected. HTTP request sent, awaiting response... 301 Moved Permanently Location: https://people.debian.org/~bartm/flashplugin-nonfree/D5C0FC14/get-upstream-version.pl.gz.pgp [following] --2014-09-27 13:54:57-- https://people.debian.org/~bartm/flashplugin-nonfree/D5C0FC14/get-upstream-version.pl.gz.pgp Connecting to people.debian.org (people.debian.org)|5.153.231.30|:443... connected. ERROR: The certificate of ‘people.debian.org’ is not trusted. ERROR: The certificate of ‘people.debian.org’ hasn't got a known issuer. # dpkg-reconfigure ca-certificates […] │[*] mozilla/UTN_USERFirst_Hardware_Root_CA.crt […] […] Processing triggers for ca-certificates (20140325) ... Updating certificates in /etc/ssl/certs... 1 added, 0 removed; done. Running hooks in /etc/ca-certificates/update.d Adding debian:UTN_USERFirst_Hardware_Root_CA.pem done. done. # wget http://people.debian.org/~bartm/flashplugin-nonfree/D5C0FC14/get-upstream-version.pl.gz.pgp --2014-09-27 13:57:14-- http://people.debian.org/~bartm/flashplugin-nonfree/D5C0FC14/get-upstream-version.pl.gz.pgp Resolving people.debian.org (people.debian.org)... 5.153.231.30, 2001:41c8:1000:21::21:30 Connecting to people.debian.org (people.debian.org)|5.153.231.30|:80... connected. HTTP request sent, awaiting response... 301 Moved Permanently Location: https://people.debian.org/~bartm/flashplugin-nonfree/D5C0FC14/get-upstream-version.pl.gz.pgp [following] --2014-09-27 13:57:14-- https://people.debian.org/~bartm/flashplugin-nonfree/D5C0FC14/get-upstream-version.pl.gz.pgp Connecting to people.debian.org (people.debian.org)|5.153.231.30|:443... connected. HTTP request sent, awaiting response... 200 OK Length: 1881 (1.8K) [application/pgp-encrypted] Saving to: ‘get-upstream-version.pl.gz.pgp’ 100%[===] 1'881 --.-K/s in 0s 2014-09-27 13:57:15 (14.9 MB/s) - ‘get-upstream-version.pl.gz.pgp’ saved [1881/1881] # dpkg-reconfigure flashplugin-nonfree # --- (works) I found out which certificate I needed by checking the information in Chromium. (Less security-savvy) users should be made aware which certificate needs to be activated for the install/update to work. In particular, they should be told by the flashplugin-nonfree configure script *why* wget (could have) failed to download the required file. Or that information should be added to https://wiki.debian.org/FlashPlayer#Troubleshooting. This bug being already closed and apt-listbugs being silent about it, I was completely unaware that something went wrong during aptitude upgrade (this package was not the only one), and suddenly found myself without *any* Flash Player plugin (in Chromium). Regards, PointedEars -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#760038: latest upgrade fixed problem
Dear Maintainer, Yesterday I did an apt-get dist-upgrade for Jessie which fixed the problem. Ian
Bug#762083: marked as done (Error: Could not import pdfshuffler Cause: No module named pyPdf)
Your message dated Sat, 27 Sep 2014 13:04:14 + with message-id e1xxrfa-0004wk...@franck.debian.org and subject line Bug#762083: fixed in pdfshuffler 0.6.0-6 has caused the Debian Bug report #762083, regarding Error: Could not import pdfshuffler Cause: No module named pyPdf 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.) -- 762083: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=762083 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: pdfshuffler Version: 0.6.0-5 Severity: grave The program will not start. ajk@teralehti:~$ pdfshuffler Error: Could not import pdfshuffler Cause: No module named pyPdf ajk@teralehti:~$ -- System Information: Debian Release: jessie/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'oldstable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.16-1-amd64 (SMP w/2 CPU cores) Locale: LANG=fi_FI.UTF-8, LC_CTYPE=fi_FI.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages pdfshuffler depends on: ii python 2.7.8-1 ii python-gtk2 2.24.0-4 ii python-poppler 0.12.1-8.1 ii python-pypdf1.23-1 pdfshuffler recommends no packages. pdfshuffler suggests no packages. -- no debconf information ---End Message--- ---BeginMessage--- Source: pdfshuffler Source-Version: 0.6.0-6 We believe that the bug you reported is fixed in the latest version of pdfshuffler, 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 762...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Jeremy Lainé jeremy.la...@m4x.org (supplier of updated pdfshuffler 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: Sat, 27 Sep 2014 14:41:33 +0200 Source: pdfshuffler Binary: pdfshuffler Architecture: source all Version: 0.6.0-6 Distribution: unstable Urgency: medium Maintainer: Python Applications Packaging Team python-apps-t...@lists.alioth.debian.org Changed-By: Jeremy Lainé jeremy.la...@m4x.org Description: pdfshuffler - merge, split and re-arrange pages from PDF documents Closes: 762083 Changes: pdfshuffler (0.6.0-6) unstable; urgency=medium . * Fall back to PyPDF2 if pyPdf is not found (Closes: #762083). * Fix Attempt to unlock mutex that was not locked error. * Update to Standards version 3.9.6, no changes required. * Add myself to uploaders. Checksums-Sha1: a6f4fd601c98fcee3ff3bc099e00d0176ba3beb6 2036 pdfshuffler_0.6.0-6.dsc f0d379cbecab680f2be844903d4c37a8838f3cc8 4105 pdfshuffler_0.6.0-6.debian.tar.gz d4026412e93dfb6418f7e1719fc72ccd1a61c29d 37656 pdfshuffler_0.6.0-6_all.deb Checksums-Sha256: 5d610b8c983f36e852d2fe0dccf2c1d409d8f462ffab70cdf43491e634b15a44 2036 pdfshuffler_0.6.0-6.dsc 6975e38b6b514dc228edbb9ca76ac25e981a7b1a36f2cfc768be999d5c98ceef 4105 pdfshuffler_0.6.0-6.debian.tar.gz 91d696b547844f4e4cf1a468eae86456d598631dcb09a68594fc17554360724b 37656 pdfshuffler_0.6.0-6_all.deb Files: ea9d41f7cd7af4d6b7c64d44e81a8632 2036 x11 optional pdfshuffler_0.6.0-6.dsc 1fff699cc72de6589880c1f21218c2fc 4105 x11 optional pdfshuffler_0.6.0-6.debian.tar.gz b29cf79d9f2fafcd5c51fe71215164e1 37656 x11 optional pdfshuffler_0.6.0-6_all.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1 iQIcBAEBAgAGBQJUJrLKAAoJENLPZJIaziaH7vkQAMP7GXeVGrbTmUzZRcfJsyF7 eUnoEDU50ai4swiKXCbUEy6dKDkFIgIgGMqaID08kskkrrmvsIR9rrBqgBfjBydj F1atqy7Je8x3kfm29yziuDsFIUW+kIvo01TIKaqZpqTVLGYPo9fepYOtVRr32cxQ 4Th2QLAxDUOA4w7kkWg55etPG+pmMIewJn7hxOGYXGXoaFDT2XU1hNsoYvHg5J0T V8yGx8FtiuB8xYWevp3/LWLIbJ7xGRECC4ciiJxd9OWmyPjUQz0I4Upnl8cKITlK 25oIFWBlzJ/EGE/1OzewBCJJeGTo0YHoNsqWU+s2tnBhxYpPqo1YG1LEbrAp/UcH 1iYa/nnEPcmXEx8AXtRmZ5Ywj6l6T6kEytNYJIClv+HLGh5jGXubromrNwt4cO5n guNrl97koNeJvg3DQcvV8vdx0miRORmqY4ZkQd5KqXoWltkDHgy4RhxwEhIY7koz Me/yanGfTGftcoCZGebpZjENtDiNIdumt2TcULNdUQwpKHn89zRgm0S9RhorU/ei 2/ubwgnOpAy8zCBwQNohXlw8V0Ljsw+AMX3si1R7nFRYOT5R3/NSrBR/bB3NJDfO uR0DVvnfMGnKs+6++KeHCLiUyzmO36Wr8aV/a9orARG2GpEOQclFULSCkGH65+h5 n0bTzhYJ2UWSlb85tpEJ =zn1+ -END PGP SIGNATUREEnd Message---
Bug#762275: Solution
On Sat, Sep 27 2014, Michael Biebl wrote: Am 27.09.2014 um 13:08 schrieb Michal Sojka: + addgroup --quiet --system systemd-journal After running 'delgroup systemd-journal', it was possible install the package. With the amount of information from the original bug submitter, it's hard to tell if this is the same issue as yours. In your case, you apparently had an existing systemd-journal group, which was not a system group, so addgroup errors out. This is not a bug in the Debian package. Most likely you had created that group yourself in the past. Yes, that's right. It's a annoying that --quiet suppress the error message in this case. -Michal -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#763042: linux-image-3.16-2: davfs2 broken with 3.16
Package: src:linux Version: 3.16.3-2 Severity: grave File: linux-image-3.16-2 Justification: causes non-serious data loss Dear Maintainer, since upgrade to 3.16-1, I cannot save files on davfs2 mounted resources. The problem affects only some editors: mcedit, libreoffice writer Does not affect vi and gedit. Files smaller than 21 kylobytes are not affected. Symptoms: open file, edit, save: editor reports that it cannot save file. After quitting editor the file on filesystem has zero size (data is lost if not saved as to another location) Rolling back to 3.14-2 eliminates the problem. 3.16-1 and 3.16-2 do behave in the same way. -- Package-specific info: ** Version: Linux version 3.16-2-amd64 (debian-ker...@lists.debian.org) (gcc version 4.8.3 (Debian 4.8.3-11) ) #1 SMP Debian 3.16.3-2 (2014-09-20) ** Command line: root=/dev/sda1 ip=172.31.251.4::172.31.251.1:255.255.255.0:desktop:eth0:none initrd=linux/initrd.img-3.16-2-amd64 BOOT_IMAGE=linux/vmlinuz-3.16-2-amd64 ** Tainted: PO (4097) * Proprietary module has been loaded. * Out-of-tree module has been loaded. ** Kernel log: [ 31.244783] systemd[1]: Listening on Journal Socket (/dev/log). [ 31.244845] systemd[1]: Starting Syslog Socket. [ 31.245157] systemd[1]: Listening on Syslog Socket. [ 31.245219] systemd[1]: Starting udev Control Socket. [ 31.245529] systemd[1]: Listening on udev Control Socket. [ 31.245592] systemd[1]: Starting udev Kernel Socket. [ 31.245901] systemd[1]: Listening on udev Kernel Socket. [ 31.245964] systemd[1]: Starting Journal Socket. [ 31.246280] systemd[1]: Listening on Journal Socket. [ 31.246348] systemd[1]: Starting System Slice. [ 31.246764] systemd[1]: Created slice System Slice. [ 31.246830] systemd[1]: Starting File System Check on Root Device... [ 31.247471] systemd[1]: Starting system-getty.slice. [ 31.247965] systemd[1]: Created slice system-getty.slice. [ 31.248070] systemd[1]: Mounting Huge Pages File System... [ 31.248629] systemd[1]: Starting udev Coldplug all Devices... [ 31.249315] systemd[1]: Mounting Debug File System... [ 31.905826] systemd[1]: Starting Create list of required static device nodes for the current kernel... [ 31.948218] systemd[1]: Started Set Up Additional Binary Formats. [ 32.708201] systemd[1]: Starting Load Kernel Modules... [ 32.708914] systemd[1]: Mounting POSIX Message Queue File System... [ 32.709555] systemd[1]: Starting Journal Service... [ 32.710491] systemd[1]: Started Journal Service. [ 35.302487] lp: driver loaded but no devices found [ 35.586178] ppdev: user-space parallel port driver [ 36.173568] fuse init (API version 7.23) [ 36.520604] it87: Found IT8720F chip at 0x290, revision 8 [ 36.520671] it87: VID is disabled (pins used for GPIO) [ 36.520730] it87: Routing internal VCCH to in7 [ 36.520784] it87: Beeping is supported [ 37.400326] systemd-udevd[215]: starting version 215 [ 42.276880] EXT4-fs (sda1): re-mounted. Opts: errors=remount-ro [ 43.143077] systemd-journald[196]: Received request to flush runtime journal from PID 1 [ 44.465482] input: Power Button as /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0C:00/input/input2 [ 44.465559] ACPI: Power Button [PWRB] [ 44.465689] input: Power Button as /devices/LNXSYSTM:00/LNXPWRBN:00/input/input3 [ 44.465758] ACPI: Power Button [PWRF] [ 44.465952] tsc: Marking TSC unstable due to TSC halts in idle [ 44.466010] ACPI: acpi_idle registered with cpuidle [ 44.466133] Switched to clocksource hpet [ 44.863795] shpchp: Standard Hot Plug PCI Controller Driver version: 0.4 [ 45.989660] ACPI Warning: SystemIO range 0x0428-0x042f conflicts with OpRegion 0x042c-0x042d (\GP2C) (20140424/utaddress-258) [ 45.989825] ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver [ 45.989921] lpc_ich: Resource conflict(s) found affecting gpio_ich [ 46.023282] input: PC Speaker as /devices/platform/pcspkr/input/input5 [ 46.038468] i801_smbus :00:1f.3: SMBus using PCI Interrupt [ 46.115239] psmouse serio1: alps: Unknown ALPS touchpad: E7=10 00 64, EC=10 00 64 [ 46.285536] [drm] Initialized drm 1.1.0 20060810 [ 46.670658] input: ImPS/2 Generic Wheel Mouse as /devices/platform/i8042/serio1/input/input4 [ 47.069855] iTCO_vendor_support: vendor-support=0 [ 47.451968] iTCO_wdt: Intel TCO WatchDog Timer Driver v1.11 [ 47.452097] iTCO_wdt: Found a ICH10DO TCO device (Version=2, TCOBASE=0x0460) [ 47.452290] iTCO_wdt: initialized. heartbeat=30 sec (nowayout=0) [ 47.492073] snd_hda_intel :01:00.1: Disabling MSI [ 47.492135] snd_hda_intel :01:00.1: Handle VGA-switcheroo audio client [ 47.492714] snd_hda_intel :00:1b.0: irq 51 for MSI/MSI-X [ 47.776057] floppy0: no floppy controllers found [ 47.812853] sound hdaudioC0D2: autoconfig: line_outs=4 (0x14/0x15/0x16/0x17/0x0) type:line [ 47.812926] sound hdaudioC0D2:speaker_outs=0
Bug#726661: Does not permit login as root from version 1:6.2p2-6
All, Thank you Paul, indeed it helped me, as I too ran into this issue in a fresh Jessie install. I didn't have to downgrade OpenSSH, however, just edit PermitRootLogin as you did. So am I right to conclude that this bug actually concerns the change that changes PermitRootLogin to without-password? I think changing this default makes sense from a security perspective as it provides the best compromise between securing a default install versus the desire to log in as root directly. However, I recognise that there are people that are using password-based root login who may be surprised by this change. The proper solution therefore may be to add a NEWS.Debian entry so everyone is informed about this change, and a release notes item at that. If those are added, this bug could be closed. Colin, what do you think? Cheers, Thijs signature.asc Description: This is a digitally signed message part.
Bug#762830: marked as done (cinnamon-menus: FTBFS: cp: cannot stat 'debian/tmp/usr/lib/girepository-1.0': No such file or directory)
Your message dated Sat, 27 Sep 2014 13:48:35 + with message-id e1xxsmv-0001vd...@franck.debian.org and subject line Bug#762830: fixed in cinnamon-menus 2.2.0-3 has caused the Debian Bug report #762830, regarding cinnamon-menus: FTBFS: cp: cannot stat 'debian/tmp/usr/lib/girepository-1.0': No such file or directory to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 762830: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=762830 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: cinnamon-menus Version: 2.2.0-2 Severity: serious Tags: patch pending Hi guys, gobject-introspection in unstable has moved the variable 'typelibdir' to point to a subdirectory of /usr/lib/$(DEB_HOST_MULTIARCH). Packages which respect this need to be updated to install files in the new location, or else they FTBFS. cinnamon-menus is in this position. I've prepared an NMU for cinnamon-menus (versioned as 2.2.0-2.1) and uploaded it to DELAYED/10. Please feel free to tell me if I should delay it longer, or cancel or supersede the upload if you want. Cheers, -- Iain Lane [ i...@orangesquash.org.uk ] Debian Developer [ la...@debian.org ] Ubuntu Developer [ la...@ubuntu.com ] diff -Nru cinnamon-menus-2.2.0/debian/changelog cinnamon-menus-2.2.0/debian/changelog --- cinnamon-menus-2.2.0/debian/changelog 2014-07-16 10:30:24.0 +0100 +++ cinnamon-menus-2.2.0/debian/changelog 2014-09-25 15:20:11.0 +0100 @@ -1,3 +1,10 @@ +cinnamon-menus (2.2.0-2.1) unstable; urgency=medium + + * Non-maintainer upload. + * Install typelib files in multiarch libdir. + + -- Iain Lane i...@orangesquash.org.uk Thu, 25 Sep 2014 15:20:11 +0100 + cinnamon-menus (2.2.0-2) unstable; urgency=medium * Release to unstable. diff -Nru cinnamon-menus-2.2.0/debian/gir1.2-cmenu-3.0.install cinnamon-menus-2.2.0/debian/gir1.2-cmenu-3.0.install --- cinnamon-menus-2.2.0/debian/gir1.2-cmenu-3.0.install 2014-07-16 10:30:24.0 +0100 +++ cinnamon-menus-2.2.0/debian/gir1.2-cmenu-3.0.install 2014-09-25 15:16:25.0 +0100 @@ -1 +1 @@ -usr/lib/girepository-1.0 +usr/lib/*/girepository-1.0 signature.asc Description: Digital signature ---End Message--- ---BeginMessage--- Source: cinnamon-menus Source-Version: 2.2.0-3 We believe that the bug you reported is fixed in the latest version of cinnamon-menus, 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 762...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Margarita Manterola ma...@debian.org (supplier of updated cinnamon-menus 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: Sat, 27 Sep 2014 15:04:07 +0200 Source: cinnamon-menus Binary: libcinnamon-menu-3-0 libcinnamon-menu-3-0-dbg libcinnamon-menu-3-dev gir1.2-cmenu-3.0 Architecture: source amd64 Version: 2.2.0-3 Distribution: unstable Urgency: medium Maintainer: Debian Cinnamon Team pkg-cinnamon-t...@lists.alioth.debian.org Changed-By: Margarita Manterola ma...@debian.org Description: gir1.2-cmenu-3.0 - GObject introspection data for the Cinnamon menu library libcinnamon-menu-3-0 - Cinnamon implementation of the freedesktop menu specification libcinnamon-menu-3-0-dbg - Cinnamon implementation of the freedesktop menu specification libcinnamon-menu-3-dev - Cinnamon implementation of the freedesktop menu specification Closes: 762830 Changes: cinnamon-menus (2.2.0-3) unstable; urgency=medium . [ Fabio Fantoni ] * Install typelib files in multiarch libdir. (Closes: #762830) Thanks to Iain Lane. . [ Margarita Manterola ] Checksums-Sha1: 46298148f154807e909903f65de8f9d6fdeefe9f 2491 cinnamon-menus_2.2.0-3.dsc ee1da9346f8a2cf2e20d5534fcf3ef7ae8476abd 3612 cinnamon-menus_2.2.0-3.debian.tar.xz 11c25f5c2a7be3c1e9f67f612bac957c4e35a914 83070 libcinnamon-menu-3-0_2.2.0-3_amd64.deb 7e43b388cb5ffcee6c8746ef726f7684f11ead03 159534 libcinnamon-menu-3-0-dbg_2.2.0-3_amd64.deb 5bc186ab56a7b2b75ba6240c6b676a49639b91a2 48648 libcinnamon-menu-3-dev_2.2.0-3_amd64.deb f779602dd75c50d0344c9d588f798b8bf28dff12 45570
Bug#762275: Solution
Am 27.09.2014 um 15:09 schrieb Michal Sojka: Yes, that's right. It's a annoying that --quiet suppress the error message in this case. Agreed. I think quiet should suppress non-fatal warnings/errors only, but not messages which will cause it to exit with non-zero return code. We added --quiet only because users were concerned / confused when they saw messages as reported in #759175, which are non-fatal. Michal, do you mind filing a bug report against adduser? -- Why is it that all of the instruments seeking intelligent life in the universe are pointed away from Earth? signature.asc Description: OpenPGP digital signature
Bug#762275: Solution
Am 27.09.2014 um 15:58 schrieb Michael Biebl: Am 27.09.2014 um 15:09 schrieb Michal Sojka: Yes, that's right. It's a annoying that --quiet suppress the error message in this case. Agreed. I think quiet should suppress non-fatal warnings/errors only, but not messages which will cause it to exit with non-zero return code. We added --quiet only because users were concerned / confused when they saw messages as reported in #759175, which are non-fatal. Michal, do you mind filing a bug report against adduser? Especially since man adduser(8) has: --quiet Suppress informational messages, only show warnings and errors. So that clearly sounds like a bug. -- Why is it that all of the instruments seeking intelligent life in the universe are pointed away from Earth? signature.asc Description: OpenPGP digital signature
Bug#762591: freerdp: FTBFS on several arches: test suite errors
On 23/09/14 15:44, Emilio Pozuelo Monfort wrote: Source: freerdp Version: 1.1.0~git20140921.1.440916e+dfsg1-1 Severity: serious See https://buildd.debian.org/status/logs.php?pkg=freerdpver=1.1.0~git20140921.1.440916e%2Bdfsg1-1 Any news on this? The freeze is approaching and you introduced a library transition after the transition freeze, so unless this is fixed RSN we'll have to look at disabling RDP support from the rdeps (I already checked vlc and vinagre) so they are not blocked on this and we can remove this from Jessie if the bugs aren't fixed. Emilio -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#726661: Does not permit login as root from version 1:6.2p2-6
On Sat, 2014 Sep 27 15:40+0200, Thijs Kinkhorst wrote: So am I right to conclude that this bug actually concerns the change that changes PermitRootLogin to without-password? I believe that's the real issue, yes. I think changing this default makes sense from a security perspective as it provides the best compromise between securing a default install versus the desire to log in as root directly. I won't argue that, but I don't see anything in openssh-server's package scripts addressing the case of a system with a root user + password but no regular user (i.e. root is the only login available). That's a valid outcome of debian-installer, and a typical scenario for me when creating a Linux VM image, and is how I ended up posting here. However, I recognise that there are people that are using password- based root login who may be surprised by this change. The proper solution therefore may be to add a NEWS.Debian entry so everyone is informed about this change, and a release notes item at that. If those are added, this bug could be closed. Is there anything that can be done about the unhelpful auth.log messages? Package documentation is good, and the permit-root-login debconf question also helps there, but a user who is trying to diagnose the issue via syslog could use better hints as to what's going on. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: libcitygml: FTBFS with new openscenegraph
Processing control commands: block 756478 by -1 Bug #756478 [release.debian.org] transition: openscenegraph 756478 was not blocked by any bugs. 756478 was not blocking any bugs. Added blocking bug(s) of 756478: 763047 -- 756478: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=756478 763047: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=763047 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#763047: libcitygml: FTBFS with new openscenegraph
Source: libcitygml
Version: 0.14+svn134-1+3p2p0
Severity: serious
Control: block 756478 by -1
On 24/09/14 23:51, Jonathan Wiltshire wrote:
There's a FTBFS in libcitygml because it can't cope with openscenegraph being
multiarched. Patch attached (although I have my doubts about that technique in
the first place), please file a bug and get it fixed.
As explained above your package now FTBFS. Patch from Jonathan Wiltshire
attached.
Emilio
diff -Nru libcitygml-0.14+svn134/debian/gencontrol libcitygml-0.14+svn134/debian/gencontrol
--- libcitygml-0.14+svn134/debian/gencontrol 2014-02-01 07:03:45.0 +
+++ libcitygml-0.14+svn134/debian/gencontrol 2014-09-24 22:47:14.0 +0100
@@ -1,4 +1,4 @@
-LIBOSG_SHARE=`dpkg --get-selections | grep libopenscenegraph[0-9]*\s*install | awk '{print $1}'`
+LIBOSG_SHARE=`dpkg --get-selections | grep libopenscenegraph[0-9]*:[[:alnum:]]*\s*install | awk '{print $1}'`
LIBOSG_VERSION=`dpkg -l $LIBOSG_SHARE | grep ^ii\s*$LIBOSG_SHARE | sed 's/-/ /' | awk '{print $3}'`
TMP1=`echo $LIBOSG_VERSION | awk -F '.' '{print $1}'`
TMP2=`echo $LIBOSG_VERSION | awk -F '.' '{print $2}'`
diff -Nru libcitygml-0.14+svn134/debian/openscenegraph-plugin-citygml-shared.install libcitygml-0.14+svn134/debian/openscenegraph-plugin-citygml-shared.install
--- libcitygml-0.14+svn134/debian/openscenegraph-plugin-citygml-shared.install 2014-02-01 07:03:45.0 +
+++ libcitygml-0.14+svn134/debian/openscenegraph-plugin-citygml-shared.install 2014-09-24 22:46:42.0 +0100
@@ -1 +1 @@
-usr/lib/osgPlugins-*/*.so
+usr/lib/*/osgPlugins-*/*.so
diff -Nru libcitygml-0.14+svn134/debian/openscenegraph-plugin-citygml-static.install libcitygml-0.14+svn134/debian/openscenegraph-plugin-citygml-static.install
--- libcitygml-0.14+svn134/debian/openscenegraph-plugin-citygml-static.install 2014-02-01 07:03:45.0 +
+++ libcitygml-0.14+svn134/debian/openscenegraph-plugin-citygml-static.install 2014-09-24 22:46:53.0 +0100
@@ -1 +1 @@
-usr/lib/osgPlugins-*/*.a
+usr/lib/*/osgPlugins-*/*.a
Bug#763013: closed by Thijs Kinkhorst th...@debian.org (Re: isc-dhcp-client depends on /bin/bash, not /bin/sh)
I will follow up with #763013, it's an obvious duplicate. I had an unusable system after removing bash because of dhclient. Although there is probably some other case where dhclient-script does not work correctly, using /bin/sh instead got me an operational desktop system. I find the risk of breakage over scripts that require /bin/bash is far easier to manage than the risk of a new 0-day remote bash exploit worm. On Sat, Sep 27, 2014 at 07:21:06AM +, Debian Bug Tracking System wrote: This is an automatic notification regarding your Bug report which was filed against the isc-dhcp-client package: #763013: isc-dhcp-client depends on /bin/bash, not /bin/sh It has been closed by Thijs Kinkhorst th...@debian.org. Their explanation is attached below along with your original report. If this explanation is unsatisfactory and you have not received a better one in a separate message then please contact Thijs Kinkhorst th...@debian.org by replying to this email. -- 763013: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=763013 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems Date: Sat, 27 Sep 2014 09:17:47 +0200 From: Thijs Kinkhorst th...@debian.org To: 763013-d...@bugs.debian.org Subject: Re: isc-dhcp-client depends on /bin/bash, not /bin/sh X-Spam-Status: No, score=-6.0 required=4.0 tests=BAYES_00,FROMDEVELOPER, MURPHY_DRUGS_REL8,RCVD_IN_DNSWL_NONE autolearn=ham version=3.3.2-bugs.debian.org_2005_01_02 Hi Troy, Severity: critical Tags: patch Justification: breaks the whole system Remove dependency on bash. Fixes ifup/ifdown with dhcp on unbashed-system. This is not a critical bug since using bash does not 'break the whole system'. The patch is also not correct because this script is marked /bin/bash for a reason, because it's not fully posix compliant and therefore will not run with just any /bin/sh. It's a valid request for the script to be modified to change its interpreter, it's already filed at #762923. Maybe you can help develop a tested patch for that to move it forward. Cheers, Thijs Date: Sat, 27 Sep 2014 00:23:56 -0500 From: Troy Benjegerdes troy-debb...@7el.us To: Debian Bug Tracking System sub...@bugs.debian.org Subject: isc-dhcp-client depends on /bin/bash, not /bin/sh X-Spam-Status: No, score=-10.6 required=4.0 tests=BAYES_00,FOURLA,HAS_PACKAGE, MURPHY_DRUGS_REL8,RCVD_IN_PBL,RCVD_IN_SORBS_DUL,RDNS_DYNAMIC, XMAILER_REPORTBUG,X_DEBBUGS_CC autolearn=ham version=3.3.2-bugs.debian.org_2005_01_02 X-Mailer: reportbug 6.4.4 Package: isc-dhcp-client Version: 4.2.2.dfsg.1-5+deb70u6 Severity: critical Tags: patch Justification: breaks the whole system Remove dependency on bash. Fixes ifup/ifdown with dhcp on unbashed-system. Also see bug 763012 --- dhclient-script.bad 2014-09-27 00:21:48.377145358 -0500 +++ /sbin/dhclient-script 2014-09-27 00:15:31.508982652 -0500 @@ -1,4 +1,4 @@ -#!/bin/bash +#!/bin/sh # dhclient-script for Linux. Dan Halbert, March, 1997. # Updated for Linux 2.[12] by Brian J. Murrell, January 1999. -- System Information: Debian Release: 7.6 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 3.2.0-4-amd64 (SMP w/2 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages isc-dhcp-client depends on: ii debianutils 4.3.2 ii iproute 20120521-3+b3 ii isc-dhcp-common 4.2.2.dfsg.1-5+deb70u6 ii libc62.13-38+deb7u4 isc-dhcp-client recommends no packages. Versions of packages isc-dhcp-client suggests: ii avahi-autoipd 0.6.31-2 pn resolvconf none -- no debconf information -- Troy Benjegerdes t...@7el.us 7 elements earth::water::air::fire::mind::spirit::soulgrid.coop Never pick a fight with someone who buys ink by the barrel, nor try buy a hacker who makes money by the megahash -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#763013: [pkg-dhcp-devel] Bug#762923: Bug#763013 closed by Thijs Kinkhorst th...@debian.org (Re: isc-dhcp-client depends on /bin/bash, not /bin/sh)
Hi Troy, Troy Benjegerdes wrote: I had an unusable system after removing bash because of dhclient. Bash is an Essential package. You're on yourself if you remove that (or any other Essential) package. Being an Essential package means that this package is guaranteed to be installed and no package needing bash needs to declare a dependency explicitly. The current bash issue though raises the demand for making bash a non-essential package, so maybe making the bash package non-essential should become a release goal for Jessie+1. Regards, Axel -- ,''`. | Axel Beckert a...@debian.org, http://people.debian.org/~abe/ : :' : | Debian Developer, ftp.ch.debian.org Admin `. `' | 1024D: F067 EA27 26B9 C3FC 1486 202E C09E 1D89 9593 0EDE `-| 4096R: 2517 B724 C5F6 CA99 5329 6E61 2FF9 CD59 6126 16B5 -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#762186: pyPdf = PyPDF2 transition breakage
Recently the pypdf2 source package, was uploaded to unstable, and forcibly took over the python-pypdf binary package. The problem is that pypdf2 does not provide a pyPdf module, but PyPDF2 which broke all the reverse dependencies. I would suggest: - pypdf2 be changed to provide a python-pypdf2 and python3-pypdf2 module - the last version of python-pypdf be re-uploaded - encouraging python-pypdf's reverse dependencies be patched to allow python-pypdf | python-pypdf2 Cheers, Jeremy -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: cloning 762870, reassign -1 to klibc-utils ..., block 762870 with -1
Processing commands for cont...@bugs.debian.org: clone 762870 -1 Bug #762870 [initramfs-tools] initramfs-tools: fails to boot after upgrade from 0.116 to 0.117 Bug 762870 cloned as bug 763049 reassign -1 klibc-utils 2.0.4-1 Bug #763049 [initramfs-tools] initramfs-tools: fails to boot after upgrade from 0.116 to 0.117 Bug reassigned from package 'initramfs-tools' to 'klibc-utils'. No longer marked as found in versions initramfs-tools/0.117. Ignoring request to alter fixed versions of bug #763049 to the same values previously set Bug #763049 [klibc-utils] initramfs-tools: fails to boot after upgrade from 0.116 to 0.117 Marked as found in versions klibc/2.0.4-1. retitle -1 klibc-utils: readlink does not implement -f option Bug #763049 [klibc-utils] initramfs-tools: fails to boot after upgrade from 0.116 to 0.117 Changed Bug title to 'klibc-utils: readlink does not implement -f option' from 'initramfs-tools: fails to boot after upgrade from 0.116 to 0.117' block 762870 with -1 Bug #762870 [initramfs-tools] initramfs-tools: fails to boot after upgrade from 0.116 to 0.117 762870 was not blocked by any bugs. 762870 was not blocking any bugs. Added blocking bug(s) of 762870: 763049 thanks Stopping processing here. Please contact me if you need assistance. -- 762870: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=762870 763049: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=763049 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#763050: geany: Does not start, Attempt to unlock mutex that was not locked instead
Package: geany Version: 1.24.1+dfsg-1 Severity: grave Justification: renders package unusable Dear Maintainer, When I try to start geany, it does not start, instead I get the message: Attempt to unlock mutex that was not locked -- System Information: Debian Release: jessie/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.16-2-amd64 (SMP w/12 CPU cores) Locale: LANG=de_CH.UTF-8, LC_CTYPE=de_CH.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages geany depends on: ii geany-common 1.24.1+dfsg-1 ii libatk1.0-0 2.14.0-1 ii libc62.19-11 ii libcairo21.12.16-5 ii libfontconfig1 2.11.0-6.1 ii libfreetype6 2.5.2-2 ii libgcc1 1:4.9.1-15 ii libgdk-pixbuf2.0-0 2.30.8-1 ii libglib2.0-0 2.42.0-1 ii libgtk2.0-0 2.24.24-1 ii libpango-1.0-0 1.36.7-1 ii libpangocairo-1.0-0 1.36.7-1 ii libpangoft2-1.0-01.36.7-1 ii libstdc++6 4.9.1-15 ii multiarch-support2.19-11 geany recommends no packages. Versions of packages geany suggests: pn doc-base none ii libvte9 1:0.28.2-5 -- 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#763047: libcitygml: FTBFS with new openscenegraph
Control: tags -1 pending Hi Emilio, On 09/27/2014 04:12 PM, Emilio Pozuelo Monfort wrote: On 24/09/14 23:51, Jonathan Wiltshire wrote: There's a FTBFS in libcitygml because it can't cope with openscenegraph being multiarched. Patch attached (although I have my doubts about that technique in the first place), please file a bug and get it fixed. As explained above your package now FTBFS. Patch from Jonathan Wiltshire attached. Thanks for forwarding the patch. I've applied it in git and prepared a new build, it's available on mentors and currently waiting for sponsorship (#763051). Kind Regards, Bas -- GPG Key ID: 4096R/E88D4AF1 Fingerprint: 8182 DE41 7056 408D 6146 50D1 6750 F10A E88D 4AF1 -- 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#763047: libcitygml: FTBFS with new openscenegraph
Processing control commands: tags -1 pending Bug #763047 [src:libcitygml] libcitygml: FTBFS with new openscenegraph Added tag(s) pending. -- 763047: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=763047 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#763054: pcre3: FTBFS on hurd because of stack size problem
Source: pcre3 Severity: serious Tags: patch Justification: fails to build from source Dear Maintainer, The package fails to build on hurd because the pthread stack size in only 2024 kb instead of the 8192 kb that linux has. Would it be a good idea to use the heap instead of the stack to fix this? The attached jit-test file that replaces your already existing jit-test file in the debian/ folder sends --disable-stack-for-recursion to the configure script on hurd systems. -- System Information: Debian Release: jessie/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.14-1-amd64 (SMP w/4 CPU cores) Locale: LANG=is_IS.utf8, LC_CTYPE=is_IS.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash #!/bin/sh arch=$(dpkg-architecture -qDEB_HOST_GNU_TYPE) os=$(dpkg-architecture -qDEB_HOST_ARCH_OS) $arch-gcc debian/jit-test.c -o/dev/null if [ $? -eq 0 ]; then echo --enable-jit fi if [ $os = 'hurd' ]; then echo --disable-stack-for-recursion fi
Processed: Re: Bug#763054: pcre3: FTBFS on hurd because of stack size problem
Processing commands for cont...@bugs.debian.org: severity 763054 important Bug #763054 [src:pcre3] pcre3: FTBFS on hurd because of stack size problem Severity set to 'important' from 'serious' thanks Stopping processing here. Please contact me if you need assistance. -- 763054: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=763054 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#762275: Solution
On Sat, Sep 27 2014, Michael Biebl wrote: Am 27.09.2014 um 15:09 schrieb Michal Sojka: Yes, that's right. It's a annoying that --quiet suppress the error message in this case. Agreed. I think quiet should suppress non-fatal warnings/errors only, but not messages which will cause it to exit with non-zero return code. We added --quiet only because users were concerned / confused when they saw messages as reported in #759175, which are non-fatal. Michal, do you mind filing a bug report against adduser? No problem, it's at https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=763055 -Michal -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#763013: [pkg-dhcp-devel] Bug#762923: Bug#763013 closed by Thijs Kinkhorst th...@debian.org (Re: isc-dhcp-client depends on /bin/bash, not /bin/sh)
On Sat, Sep 27, 2014 at 04:33:28PM +0200, Axel Beckert wrote: Hi Troy, Troy Benjegerdes wrote: I had an unusable system after removing bash because of dhclient. Bash is an Essential package. You're on yourself if you remove that (or any other Essential) package. Being an Essential package means that this package is guaranteed to be installed and no package needing bash needs to declare a dependency explicitly. The current bash issue though raises the demand for making bash a non-essential package, so maybe making the bash package non-essential should become a release goal for Jessie+1. So far my biggest problem removing bash is the dire warnings from dpkg/apt about how essential bash is, and the reality is changing to /bin/sh solved the one serious problem I had. I would argue that unessentializing bash should be a release-critical bug for Jessie, not Jessie+1. If that's not possible, then at least make it a little easier to remove and provide docs to sysadmins on what to expect and at least prevent bash from being auto-reinstalled at the next apt-get upgrade. Migrating users login shells from /bin/bash would be a slightly different story. I'm thinking 'bash-noroot' that exits if started as root or any of the common system accounts would be a reasonable compromise? -- Troy Benjegerdes t...@7el.us 7 elements earth::water::air::fire::mind::spirit::soulgrid.coop Never pick a fight with someone who buys ink by the barrel, nor try buy a hacker who makes money by the megahash -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#759956: marked as done (drawtiming: FTBFS: dh_auto_test: make -j1 check returned exit code 2)
Your message dated Sat, 27 Sep 2014 15:51:05 + with message-id e1xxuh3-0005nn...@franck.debian.org and subject line Bug#759956: fixed in graphicsmagick 1.3.20-3 has caused the Debian Bug report #759956, regarding drawtiming: FTBFS: dh_auto_test: make -j1 check returned exit code 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.) -- 759956: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=759956 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Source: drawtiming Version: 0.7.1-5 Severity: serious Tags: jessie sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20140830 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): make[3]: Entering directory '/«PKGBUILDDIR»/samples' + ../src/drawtiming -o sample.gif ./sample.txt + ../src/drawtiming -o statement1.gif ./statement1.txt + ../src/drawtiming -x 1.5 -o memory.gif ./memory.txt caught Magick++ exception: Magick: Non-conforming drawing primitive definition (text) reported by magick/render.c:3022 (DrawImage) FAIL: runsamples.sh === 1 of 1 tests failed === make[3]: *** [check-TESTS] Error 1 Makefile:177: recipe for target 'check-TESTS' failed make[3]: Leaving directory '/«PKGBUILDDIR»/samples' make[2]: *** [check-am] Error 2 Makefile:277: recipe for target 'check-am' failed make[2]: Leaving directory '/«PKGBUILDDIR»/samples' make[1]: *** [check-recursive] Error 1 Makefile:224: recipe for target 'check-recursive' failed make[1]: Leaving directory '/«PKGBUILDDIR»' dh_auto_test: make -j1 check returned exit code 2 The full build log is available from: http://aws-logs.debian.net/ftbfs-logs/2014/08/30/drawtiming_0.7.1-5_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. The build was done with DEB_BUILD_OPTIONS=parallel=4, so if your packaging tries to support this, it might be a good idea to explore whether this might be the cause of the failure. ---End Message--- ---BeginMessage--- Source: graphicsmagick Source-Version: 1.3.20-3 We believe that the bug you reported is fixed in the latest version of graphicsmagick, 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 759...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Laszlo Boszormenyi (GCS) g...@debian.org (supplier of updated graphicsmagick 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: Sat, 27 Sep 2014 07:37:31 + Source: graphicsmagick Binary: graphicsmagick libgraphicsmagick3 libgraphicsmagick1-dev libgraphicsmagick++3 libgraphicsmagick++1-dev libgraphics-magick-perl graphicsmagick-imagemagick-compat graphicsmagick-libmagick-dev-compat graphicsmagick-dbg Architecture: source amd64 all Version: 1.3.20-3 Distribution: unstable Urgency: medium Maintainer: Laszlo Boszormenyi (GCS) g...@debian.org Changed-By: Laszlo Boszormenyi (GCS) g...@debian.org Description: graphicsmagick - collection of image processing tools graphicsmagick-dbg - format-independent image processing - debugging symbols graphicsmagick-imagemagick-compat - image processing tools providing ImageMagick interface graphicsmagick-libmagick-dev-compat - image processing libraries providing ImageMagick interface libgraphics-magick-perl - format-independent image processing - perl interface libgraphicsmagick++1-dev - format-independent image processing - C++ development files libgraphicsmagick++3 - format-independent image processing - C++ shared library libgraphicsmagick1-dev - format-independent image processing - C development files libgraphicsmagick3 - format-independent image processing - C shared library Closes: 759956 Changes: graphicsmagick (1.3.20-3) unstable; urgency=medium . * Use upstream fix for AnnotateImage() return value (closes:
Bug#763018: marked as done (/etc/cron.monthly/ieee-data: cron job modifies files shipped in the package)
Your message dated Sat, 27 Sep 2014 15:51:44 + with message-id e1xxuhg-0005ak...@franck.debian.org and subject line Bug#763018: fixed in ieee-data 20140927.1 has caused the Debian Bug report #763018, regarding /etc/cron.monthly/ieee-data: cron job modifies files shipped in the package 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.) -- 763018: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=763018 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: ieee-data Version: 20140828.1 Severity: serious I got a warning from debsums that the following files in ieee-data had been modified. Packages should not modify files shipped in the deb. These files should be moved to /usr and the maintainer scripts should copy the files to /var if the files in /var are not present or are older than the files in /usr. This is so that people who disable the cron job for privacy reasons can still get updates. The maintainer scripts should also remove the files from /var when the package is removed/purged. pabs@chianamo ~ $ dpkg -L ieee-data | grep /var /var /var/lib /var/lib/ieee-data /var/lib/ieee-data/oui.txt /var/lib/ieee-data/.lastupdate /var/lib/ieee-data/iab.txt pabs@chianamo ~ $ sudo debsums -s ieee-data debsums: changed file /var/lib/ieee-data/.lastupdate (from ieee-data package) debsums: changed file /var/lib/ieee-data/iab.txt (from ieee-data package) debsums: changed file /var/lib/ieee-data/oui.txt (from ieee-data package) -- System Information: Debian Release: jessie/sid APT prefers testing APT policy: (900, 'testing'), (800, 'unstable'), (700, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 3.16-2-amd64 (SMP w/4 CPU cores) Locale: LANG=en_AU.UTF-8, LC_CTYPE=en_AU.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages ieee-data depends on: ii curl 7.38.0-1 ii libwww-perl 6.08-1 ii wget 1.15-1+b1 ieee-data recommends no packages. ieee-data suggests no packages. -- no debconf information -- debsums errors found: debsums: changed file /var/lib/ieee-data/.lastupdate (from ieee-data package) debsums: changed file /var/lib/ieee-data/iab.txt (from ieee-data package) -- bye, pabs https://wiki.debian.org/PaulWise signature.asc Description: This is a digitally signed message part ---End Message--- ---BeginMessage--- Source: ieee-data Source-Version: 20140927.1 We believe that the bug you reported is fixed in the latest version of ieee-data, 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 763...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Luciano Bello luci...@debian.org (supplier of updated ieee-data 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: Sat, 27 Sep 2014 16:15:24 +0200 Source: ieee-data Binary: ieee-data Architecture: source all Version: 20140927.1 Distribution: unstable Urgency: high Maintainer: Luciano Bello luci...@debian.org Changed-By: Luciano Bello luci...@debian.org Description: ieee-data - OUI and IAB listings Closes: 763015 763018 Changes: ieee-data (20140927.1) unstable; urgency=high . * Cron jobs is quiet. Closes: #763015 * The files are now shipped to /usr/share/ieee-data. Closes: #763018 * Copyright notes updated. Checksums-Sha1: a01abc35b017d49f9152e302a9188df3987d9e59 1623 ieee-data_20140927.1.dsc b0e76b0eefcf62ed9215dae9f30a8eb3dffdf48a 804440 ieee-data_20140927.1.tar.xz e14ca516903e077ae783ef67d34ffae8bd678a68 805792 ieee-data_20140927.1_all.deb Checksums-Sha256: 46702f166a66a960320dba95ff93dae2aa4ff098f58b3a7f4903cccb2c3711f6 1623 ieee-data_20140927.1.dsc 4bdab7f06b4cf0fc4316de3ce8c565a0d5a06deb2b846b2c90e6d9d611a25a2a 804440 ieee-data_20140927.1.tar.xz 76d1749a29f15c73c68b6ff4379d6509a38cb8180caddfe3a196a56e2297d2f2 805792 ieee-data_20140927.1_all.deb Files: 649c52524b694cd519561a80c9df226b 805792 net optional ieee-data_20140927.1_all.deb c30cfeb7d246f4f89057c2f66267cb60 1623 net optional ieee-data_20140927.1.dsc 1ea6c2495f76d173a7030ef5f4dffcc7 804440 net optional ieee-data_20140927.1.tar.xz -BEGIN PGP SIGNATURE- Version: GnuPG v1
Processed: Re: Bug#762275: error while upgrading
Processing control commands: severity -1 important Bug #762275 [systemd] error while upgrading Severity set to 'important' from 'grave' -- 762275: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=762275 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#762275: error while upgrading
Control: severity -1 important
Hi Joseph,
Am 20.09.2014 um 22:46 schrieb Michael Biebl:
While attempting to upgrade systemd this morning, dpkg errored out with the
following message:
(Reading database ... 328123 files and directories currently installed.)
Preparing to unpack .../systemd_215-4_i386.deb ...
Unpacking systemd (215-4) over (208-8) ...
dpkg: warning: unable to delete old directory
'/etc/systemd/system/multi-user.target.wants': Directory not empty
This is a harmless warning and not an error which would cause dpkg to
error out.
Did you get any additional error messages?
Since I haven't received any further feedback from you and the existing
information is insufficient to diagnose the bug report, I'm going to
downgrade the severity. It's not even clear which package exactly failed.
If you have time to further help debugging this, please add set -x to
the failing maintainer script in /var/lib/dpkg/info/$pkg.{postinst,preinst}
and report back with the output.
--
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?
signature.asc
Description: OpenPGP digital signature
Bug#762837: marked as done (nemo: cp: cannot stat 'debian/tmp/usr/lib/girepository-1.0/Nemo-3.0.typelib': No such file or directory)
Your message dated Sat, 27 Sep 2014 15:56:02 + with message-id e1xxulq-00064y...@franck.debian.org and subject line Bug#762837: fixed in nemo 2.2.4-2 has caused the Debian Bug report #762837, regarding nemo: cp: cannot stat 'debian/tmp/usr/lib/girepository-1.0/Nemo-3.0.typelib': No such file or directory to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 762837: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=762837 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: nemo Version: 2.2.4-1 Severity: serioues Tags: patch pending Greetings, gobject-introspection in unstable has moved the variable 'typelibdir' to point to a subdirectory of /usr/lib/$(DEB_HOST_MULTIARCH). Packages which respect this need to be updated to install files in the new location, or else they FTBFS. mate-panel is in this position. I've prepared an NMU for nemo (versioned as 2.2.4-1.1) and uploaded it to DELAYED/10. Please feel free to tell me if I should delay it longer, or to supersede it yourself, or whatever. Thanks, -- Iain Lane [ i...@orangesquash.org.uk ] Debian Developer [ la...@debian.org ] Ubuntu Developer [ la...@ubuntu.com ] diff -Nru nemo-2.2.4/debian/changelog nemo-2.2.4/debian/changelog --- nemo-2.2.4/debian/changelog 2014-08-13 13:18:16.0 +0100 +++ nemo-2.2.4/debian/changelog 2014-09-25 16:03:58.0 +0100 @@ -1,3 +1,10 @@ +nemo (2.2.4-1.1) unstable; urgency=medium + + * Non-maintainer upload. + * Install typelib file into multiarch libdir. + + -- Iain Lane i...@orangesquash.org.uk Thu, 25 Sep 2014 16:03:58 +0100 + nemo (2.2.4-1) unstable; urgency=medium [ Fabio Fantoni ] diff -Nru nemo-2.2.4/debian/gir1.2-nemo-3.0.install nemo-2.2.4/debian/gir1.2-nemo-3.0.install --- nemo-2.2.4/debian/gir1.2-nemo-3.0.install 2014-08-13 13:18:16.0 +0100 +++ nemo-2.2.4/debian/gir1.2-nemo-3.0.install 2014-09-25 16:03:29.0 +0100 @@ -1 +1 @@ -usr/lib/girepository-1.0/Nemo-3.0.typelib +usr/lib/*/girepository-1.0/Nemo-3.0.typelib ---End Message--- ---BeginMessage--- Source: nemo Source-Version: 2.2.4-2 We believe that the bug you reported is fixed in the latest version of nemo, 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 762...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Margarita Manterola ma...@debian.org (supplier of updated nemo 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: Sat, 27 Sep 2014 15:49:17 +0200 Source: nemo Binary: nemo nemo-dbg libnemo-extension1 libnemo-extension-dev gir1.2-nemo-3.0 nemo-data Architecture: source amd64 all Version: 2.2.4-2 Distribution: unstable Urgency: low Maintainer: Debian Cinnamon Team pkg-cinnamon-t...@lists.alioth.debian.org Changed-By: Margarita Manterola ma...@debian.org Description: gir1.2-nemo-3.0 - libraries for nemo components - gir bindings libnemo-extension-dev - Nemo component system facilities (development files) libnemo-extension1 - Nemo component system facilities nemo - File manager and graphical shell for Cinnamon nemo-data - File manager and graphical shell for Cinnamon (data files) nemo-dbg - File manager and graphical shell for Cinnamon (Debugging symbols) Closes: 762837 Changes: nemo (2.2.4-2) unstable; urgency=low . * Install typelib into multiarch libdir. (Closes: #762837) Thanks to Iain Lane for the fix. Checksums-Sha1: 6bb0be4222e01140baa6037774f7d369278474e4 2843 nemo_2.2.4-2.dsc 339a846533168c22cefb5519e4df801bd7f9e6b8 9240 nemo_2.2.4-2.debian.tar.xz f23a8348eb0360fe9df4738e6f13401bcaeed168 886268 nemo_2.2.4-2_amd64.deb 65c287d33f17364a1005019505997e42e670e44a 2978304 nemo-dbg_2.2.4-2_amd64.deb ec90e1e507166b5a8760a6e06de45846c41b1986 218100 libnemo-extension1_2.2.4-2_amd64.deb b3834f62bf22d3029096df6ec48e24a7ae4bb76a 23 libnemo-extension-dev_2.2.4-2_amd64.deb a8823d51cb17c77b00654172549c3c51a45a1fd0 210170 gir1.2-nemo-3.0_2.2.4-2_amd64.deb 0d3c216cb4ccfd7a438dd29f005101f7bdda6344 232880 nemo-data_2.2.4-2_all.deb Checksums-Sha256:
Bug#762146: marked as done (Upgrade To Sid From Beta D-I Breaks systemd, udev, and cron)
Your message dated Sat, 27 Sep 2014 16:54:41 + with message-id e1xxvgb-0006e9...@franck.debian.org and subject line Bug#762146: fixed in systemd 215-5 has caused the Debian Bug report #762146, regarding Upgrade To Sid From Beta D-I Breaks systemd, udev, and cron 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.) -- 762146: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=762146 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: udev Version: 215-4 Severity: grave Installed Beta 1 D-I amd64 netinst without mirror or standard utils in preparation for dist-upgrade to Sid using aptitude with sources.list: deb ftp://debian.csail.mit.edu/debian/ sid main udev and aptitude reported replacing 208-6. udev fails first during configure after systemd incurs systemd-journald.service watchdog timeout! Next systemd fails to configure, then cron does the same. At the conclusion of dist-upgrade, all three are broken and reportbug cannot be force installed. In single, used aptitude to uninstall systemd-sysv and install systemd-shim, enabling all other updates to install nominally. Platform is a virtual machine under current Sid using qemu and kvm on a quad-core Intel. That system incurred a similar outcome from its daily update roughly 12 hours previously and recovered with the same remediation used for the virtual machine. -- not cent from sell May the LORD God bless you exceedingly abundantly! Dave_Craig__ So the universe is not quite as you thought it was. You'd better rearrange your beliefs, then. Because you certainly can't rearrange the universe. __--from_Nightfall_by_Asimov/Silverberg_ signature.asc Description: Digital signature ---End Message--- ---BeginMessage--- Source: systemd Source-Version: 215-5 We believe that the bug you reported is fixed in the latest version of systemd, 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 762...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Michael Biebl bi...@debian.org (supplier of updated systemd 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: Sat, 27 Sep 2014 17:49:47 +0200 Source: systemd Binary: systemd systemd-sysv libpam-systemd libsystemd0 libsystemd-dev libsystemd-login0 libsystemd-login-dev libsystemd-daemon0 libsystemd-daemon-dev libsystemd-journal0 libsystemd-journal-dev libsystemd-id128-0 libsystemd-id128-dev udev libudev1 libudev-dev udev-udeb libudev1-udeb libgudev-1.0-0 gir1.2-gudev-1.0 libgudev-1.0-dev python3-systemd systemd-dbg Architecture: source amd64 Version: 215-5 Distribution: unstable Urgency: medium Maintainer: Debian systemd Maintainers pkg-systemd-maintain...@lists.alioth.debian.org Changed-By: Michael Biebl bi...@debian.org Description: gir1.2-gudev-1.0 - libgudev-1.0 introspection data libgudev-1.0-0 - GObject-based wrapper library for libudev libgudev-1.0-dev - libgudev-1.0 development files libpam-systemd - system and service manager - PAM module libsystemd-daemon-dev - systemd utility library (transitional package) libsystemd-daemon0 - systemd utility library (deprecated) libsystemd-dev - systemd utility library - development files libsystemd-id128-0 - systemd 128 bit ID utility library (deprecated) libsystemd-id128-dev - systemd 128 bit ID utility library (transitional package) libsystemd-journal-dev - systemd journal utility library (transitional package) libsystemd-journal0 - systemd journal utility library (deprecated) libsystemd-login-dev - systemd login utility library (transitional package) libsystemd-login0 - systemd login utility library (deprecated) libsystemd0 - systemd utility library libudev-dev - libudev development files libudev1 - libudev shared library libudev1-udeb - libudev shared library (udeb) python3-systemd - Python 3 bindings for systemd systemd- system and service manager systemd-dbg - system and service manager (debug symbols) systemd-sysv - system and service manager - SysV links udev - /dev/ and hotplug management daemon udev-udeb - /dev/ and hotplug management daemon (udeb)
Bug#763078: ghc no longer builds working executables on armel, armhf
Package: ghc, llvm Version: 7.6.3-16 Severity: serious It seems that ./Setup configure segfaults: (sid_armhf-dchroot)joeyh@harris:/tmp/git-annex-5.20140926$ ./dist/setup/setup configure Segmentation fault https://buildd.debian.org/status/fetch.php?pkg=git-annexarch=armelver=5.20140926stamp=1411825516 This segfault is reproducible (happened on armel and armhs buildds and then I reproduced it on harris.debian.org). git-annex built ok last week. Even worse, main = print hello is miscompiled on armhf: (sid_armhf-dchroot)joeyh@harris:/tmp$ ghc --make test [1 of 1] Compiling Main ( test.hs, test.o ) You are using a new version of LLVM that hasn't been tested yet! We will try though... Linking test ... ./test (sid_armhf-dchroot)joeyh@harris:/tmp$ ./test Illegal instruction And the same simple program no longer works on armel either: (sid_armel-dchroot)joeyh@abel:~/tmp$ ghc --make test [1 of 1] Compiling Main ( test.hs, test.o ) You are using a new version of LLVM that hasn't been tested yet! We will try though... Linking test ... (sid_armel-dchroot)joeyh@abel:~/tmp$ ./test test: schedule: re-entered unsafely. Perhaps a 'foreign import unsafe' should be 'safe'? (sid_armel-dchroot)joeyh@abel:~/tmp$ echo $? 1 I think that this was cuased by the introduction of llvm-3.5, while ghc etc was built using llvm-3.4. -- see shy jo signature.asc Description: Digital signature
Bug#740942: [samba] /etc/init.d/samba forbit systemd shutdown system
I have the same problem in the stop of the computer, infringe 5 minutes. For the record, Systemd launches to the starting up of Samba 4 services(departments): samba, samba-ad-dc, nmbd, smbd. In the stop(ruling) it should stop all these services, if we look at the script of /etc/init.d/samba its stop samba-ad-ac, smbd, nmbd. In a Konsole i do an : portable:/usr/share/man# time systemctl stop samba real5m0.350s user0m0.000s sys 0m0.000s As time show : 5 minutes wait portable:/usr/share/man# systemctl status samba ● samba.service - LSB: ensure Samba daemons are started (nmbd and smbd) Loaded: loaded (/etc/init.d/samba) Active: failed (Result: timeout) since sam. 2014-09-27 18:26:04 CEST; 46s ago Process: 31126 ExecStop=/etc/init.d/samba stop (code=killed, signal=TERM) sept. 27 18:26:04 portable samba[31126]: Stopping samba-ad-dc (via systemctl): samba-ad-dc.service portable:/usr/share/man# systemctl status samba-ad-dc ● samba-ad-dc.service - LSB: start Samba daemons for the AD DC Loaded: loaded (/etc/init.d/samba-ad-dc) Active: inactive (dead) since sam. 2014-09-27 18:26:05 CEST; 1min 55s ago Process: 31764 ExecStop=/etc/init.d/samba-ad-dc stop (code=exited, status=0/SUCCESS) It shows that : samba and samba-ad-dc are stopped But portable:/usr/share/man# systemctl status smbd ● smbd.service - LSB: start Samba SMB/CIFS daemon (smbd) Loaded: loaded (/etc/init.d/smbd) Active: active (running) since sam. 2014-09-27 11:50:21 CEST; 6h ago CGroup: /system.slice/smbd.service ├─1732 /usr/sbin/smbd -D └─1746 /usr/sbin/smbd -D sept. 27 11:50:21 portable smbd[1724]: [2014/09/27 11:50:21.658274, 0] ../source3/param/loadparm.c:3155(lp_do_parameter) sept. 27 11:50:21 portable smbd[1724]: Ignoring unknown parameter password level sept. 27 11:50:21 portable smbd[1724]: [2014/09/27 11:50:21.658774, 0] ../source3/param/loadparm.c:3155(lp_do_parameter) sept. 27 11:50:21 portable smbd[1724]: Ignoring unknown parameter share modes sept. 27 11:50:21 portable smbd[1724]: [2014/09/27 11:50:21.658899, 0] ../source3/param/loadparm.c:3155(lp_do_parameter) sept. 27 11:50:21 portable smbd[1724]: Ignoring unknown parameter share modes sept. 27 11:50:21 portable smbd[1724]: [2014/09/27 11:50:21.659245, 0] ../source3/param/loadparm.c:3155(lp_do_parameter) sept. 27 11:50:21 portable smbd[1724]: Ignoring unknown parameter share modes sept. 27 11:50:21 portable smbd[1694]: Starting SMB/CIFS daemon: smbd. sept. 27 11:50:24 portable smbd[1732]: [2014/09/27 11:50:24.239602, 0] ../lib/util/become_daemon.c:136(daemon_ready) portable:/usr/share/man# systemctl status nmbd ● nmbd.service - LSB: start Samba NetBIOS nameserver (nmbd) Loaded: loaded (/etc/init.d/nmbd) Active: active (running) since sam. 2014-09-27 11:49:56 CEST; 6h ago CGroup: /system.slice/nmbd.service └─1034 /usr/sbin/nmbd -D sept. 27 11:49:56 portable nmbd[1033]: [2014/09/27 11:49:56.510769, 0] ../source3/param/loadparm.c:3067(lp_set_enum_parm) sept. 27 11:49:56 portable nmbd[1033]: WARNING: Ignoring invalid value 'share' for parameter 'security' sept. 27 11:49:56 portable nmbd[1033]: [2014/09/27 11:49:56.579792, 0] ../source3/param/loadparm.c:3155(lp_do_parameter) sept. 27 11:49:56 portable nmbd[1033]: Ignoring unknown parameter password level sept. 27 11:49:56 portable nmbd[1034]: [2014/09/27 11:49:56.581992, 0] ../source3/nmbd/nmbd_subnetdb.c:250(create_subnets) sept. 27 11:49:56 portable nmbd[920]: Starting NetBIOS name server: nmbd. sept. 27 11:49:56 portable nmbd[1034]: create_subnets: No local IPv4 non- loopback interfaces ! sept. 27 11:49:56 portable nmbd[1034]: [2014/09/27 11:49:56.582973, 0] ../source3/nmbd/nmbd_subnetdb.c:251(create_subnets) sept. 27 11:49:56 portable nmbd[1034]: create_subnets: Waiting for an interface to appear ... sept. 27 11:50:46 portable nmbd[1034]: [2014/09/27 11:50:46.586911, 0] ../lib/util/become_daemon.c:136(daemon_ready) portable:/usr/share/man# But smbd and nmbd services are still Active. If i do in a Konsole : systemctl stop smbd or nmbd its stop correctly. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#763078: confirmed llvm change broke ghc
Confirmed that installing llvm-3.4 and putting /usr/lib/llvm-3.4/bin first in PATH before running ghc lets it build working executables on armel and armhf. This is certianly a bug in ghc. It should not depend on llvm, but on the llvm-$ver it was built against, and it should use the toolchain from that specific version of llvm. This could also be be considered a bug in llvm. Changing the dependency package to use llvm-3.5 less than a week before the slushy freeze is perhaps not the best idea? I think llvm should be prevented from migration to testing until this is sorted out in ghc and/or lvm, so I am leaving this bug assigned to both packages. There's also the worry of what happens if the autobuilders have built any haskell libraries using the new llvm on armel/hf. If there's been an ABI break in the code generated by llvm, that seems like it could get messy fast. -- see shy jo, off to work around this in order to get a security fix into testing signature.asc Description: Digital signature
Bug#754354: Something holds dentry-related mutex forever in Wheezy amd64 kernel
I compiled my own version of the Debian 3.2.60-1+deb7u3 kernel with
CONFIG_LOCKDEP and panic on hung task enabled.
From the crash dump:
[25202.156175] INFO: task nfsd:3247 blocked for more than 900 seconds.
[25202.162565] echo 0 /proc/sys/kernel/hung_task_timeout_secs disables this
message.
[25202.170432] nfsdD 88080aa0eca8 0 3247 2 0x
[25202.170444] 88080a8e19f0 0046 0006
8808
[25202.170458] 88080aa0e9c0 88080a8e1fd8 88080a8e1fd8
001d4040
[25202.170472] 88040e9926c0 88080aa0e9c0 8138d6da
0001a04c47dd
[25202.170488] Call Trace:
[25202.170504] [8138d6da] ? __mutex_lock_common+0x236/0x379
[25202.170531] [a04c47dd] ? fh_lock_nested+0x4d/0x61 [nfsd]
[25202.170542] [8138cda2] schedule+0x55/0x57
[25202.170552] [8138d6e7] __mutex_lock_common+0x243/0x379
[25202.170569] [a04c47dd] ? fh_lock_nested+0x4d/0x61 [nfsd]
[25202.170581] [8138d8dc] mutex_lock_nested+0x2a/0x31
[25202.170598] [a04c47dd] fh_lock_nested+0x4d/0x61 [nfsd]
[25202.170610] [810140f5] ? sched_clock+0x9/0xd
[25202.170626] [a04c50fe] nfsd_lookup_dentry+0x196/0x227 [nfsd]
[25202.170646] [a04cef7f] nfsd4_secinfo.part.15+0x26/0x9e [nfsd]
[25202.170666] [a04cf044] nfsd4_secinfo+0x4d/0x5b [nfsd]
[25202.170688] [a04ce105] nfsd4_proc_compound+0x265/0x43e [nfsd]
[25202.170703] [a04c181d] nfsd_dispatch+0xe2/0x1c8 [nfsd]
[25202.170734] [a03759c1] svc_process_common+0x2cf/0x4d0 [sunrpc]
[25202.170759] [a0375de0] svc_process+0x118/0x136 [sunrpc]
[25202.170773] [a04c10eb] nfsd+0xeb/0x131 [nfsd]
[25202.170796] [a04c1000] ? 0xa04c0fff
[25202.170806] [81065c75] kthread+0xa3/0xab
[25202.170815] [81396584] kernel_thread_helper+0x4/0x10
[25202.170823] [8138f074] ? retint_restore_args+0x13/0x13
[25202.170830] [81065bd2] ? __init_kthread_worker+0x53/0x53
[25202.170837] [81396580] ? gs_change+0x13/0x13
[25202.170842] 1 lock held by nfsd/3247:
[25202.170845] #0: (sb-s_type-i_mutex_key#13){+.+.+.}, at:
[a04c47dd] fh_lock_nested+0x4d/0x61 [nfsd]
[25202.170870] Kernel panic - not syncing: hung_task: blocked tasks
I'm no expert at interpreting lockdep output but I think this is saying
that nfsd is taking a nested lock and then deadlocks trying to take it
again (which presumably shouldn't happen because it is nested.)
Mike.
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#762984: initramfs-tools: Alert! /dev/vg0/usr does not exist
Control: tag -1 moreinfo On Fri, 26 Sep 2014 22:03:29 +0200 Elimar Riesebieter riese...@lxtec.de wrote: Package: initramfs-tools Version: 0.117 Severity: normal LVM2 running on top of RAID1. /usr is separated on an extra volume. [...] You also wrote: Running /usr on a separate raid partition is not recognized too. Verified that on an other System: Alert! /dev/md5 does not exist Is / on RAID and/or LVM? I suspect we may not correctly handle some cases where /usr requires a RAID or VG that / does not. Ben. -- Ben Hutchings The two most common things in the universe are hydrogen and stupidity. signature.asc Description: This is a digitally signed message part
Processed: Re: initramfs-tools: Alert! /dev/vg0/usr does not exist
Processing control commands: tag -1 moreinfo Bug #762984 [initramfs-tools] initramfs-tools: Alert! /dev/vg0/usr does not exist Added tag(s) moreinfo. -- 762984: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=762984 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#755643: Re: Bug#755643: mumble-django: Please ensure it works with Django 1.7
Hi, On Fri, 26 Sep 2014, Michael Ziegler wrote: I'm sorry for the delay. Using ./manage.py runserver the new version I packaged in svn works fine and is theoretically ready to be uploaded, but there seems to be something wrong with the Apache config because I ran into some obscure bug when testing it. If the problem is with Apache, it's probably not introduced with Django 1.7. Are you sure that the Apache problem is not related to Apache 2.4 and that the current package doesn't already suffer from it? Did the apache config change between 2.10 and 2.11? If the current package already has the problem, then it's not a regression and uploading the new version now doesn't forbid you to fix the problem in a few days... and doesn't put users in a worst situation than currently. Cheers, -- Raphaël Hertzog ◈ Debian Developer Discover the Debian Administrator's Handbook: → http://debian-handbook.info/get/ -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#761562: osmosis: FTBFS: Execution failed for task ':osmosis-osm-binary:compileJava'.
Control: tags -1 pending Hi David, Supporting protobuf 2.6.0 in osmosis turned out to be easier than expected, running protoc and storing the generated source as a patch. I've updated the osmosis package to include this patch and some fixes from the upstream git repo. The fixed package is available on mentors, and currently waiting for sponsorship (#763101). Kind Regards, Bas -- GPG Key ID: 4096R/E88D4AF1 Fingerprint: 8182 DE41 7056 408D 6146 50D1 6750 F10A E88D 4AF1 -- 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#761562: osmosis: FTBFS: Execution failed for task ':osmosis-osm-binary:compileJava'.
Processing control commands: tags -1 pending Bug #761562 [src:osmosis] osmosis: FTBFS: Execution failed for task ':osmosis-osm-binary:compileJava'. Added tag(s) pending. -- 761562: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=761562 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#761114: #732391 possibly fixed by patch for #761114
Hi, Since network-manager-0.9.10.0-2.1 I have been unable to reproduce #732391 (or whatever my problem was, if not an example of #732391). Can others please test? In particular, can the OP please test? CCing #761114 since AFAIK the patch to fix it was the only difference between 0.9.10.0-2 and 0.9.10.0-2.1. -Keshav -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#762984: initramfs-tools: Alert! /dev/vg0/usr does not exist
On Sat, 27 Sep 2014 20:05:07 +0100 Ben Hutchings b...@decadent.org.uk wrote: Control: tag -1 moreinfo On Fri, 26 Sep 2014 22:03:29 +0200 Elimar Riesebieter riese...@lxtec.de wrote: Package: initramfs-tools Version: 0.117 Severity: normal LVM2 running on top of RAID1. /usr is separated on an extra volume. [...] You also wrote: Running /usr on a separate raid partition is not recognized too. Verified that on an other System: Alert! /dev/md5 does not exist Is / on RAID and/or LVM? I suspect we may not correctly handle some cases where /usr requires a RAID or VG that / does not. ## System 1: /dev/mapper/vg0-burn /burn /dev/mapper/vg0-home /home /dev/mapper/vg0-root / /dev/mapper/vg0-source /source /dev/mapper/vg0-tmp /tmp /dev/mapper/vg0-usr /usr /dev/mapper/vg0-var /var /dev/mapper/vg0-working /working /dev/md5 /boot where the volume group resides on a RAID1 /dev/md5 is a RAID1 as well Alert! /dev/vg0/usr does not exist ## System 2: /dev/md5 /boot /dev/md6 / /dev/md7 /usr /dev/md8 /var /dev/md9 /tmp /dev/md10 /burn /dev/md11 /source /dev/md12 /working where all partitions are configured as RAID1 Alert! /dev/md5 does not exist -- Elimar -- Experience is something you don't get until just after you need it! -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#762959: ABI break: missing libclang.so.1
Hi, * Sylvestre Ledru (sylves...@debian.org) [140927 20:10]: On 26/09/2014 17:52, Helmut Grohne wrote: Package: libclang1-3.5 Version: 1:3.5-2 Severity: serious Control: affects -1 doxygen Dear clang maintainers, I noticed that installing doxygen in a fresh sid chroot results in an unusable binary: $ doxygen doxygen: error while loading shared libraries: libclang.so.1: cannot open shared object file: No such file or directory $ I am sorry about that. I have a build running which should fix that. I will let you know later today. Helmut pointed out on IRC that the symlink from from libclang-3.5.so.1 to /usr/lib/`dpkg-architecture -qDEB_BUILD_MULTIARCH`/libclang.so.1 is missing if the package libclang1 is installed. My investigation pointed to the fact that the file installed in /usr/lib/(arch)/libclang-3.5.so.1 has now the soname libclang-3.5.so and not anymore libclang.so.1. So the ldconfig-call in postinst doesn't create the symlink from libclang.so.1 to libclang-3.5.so.1 anymore. The probably best fix for that would be to go back to the previous soname if there is no strong reason against. Otherwise changing soname means that a new library package should be created, but as we are already past transition time for the next release, that would be better early in the next cycle. (If a new library package is created, binNMUs are possible to replace the binary packages with links to the new library package. As it is now, any package built against libclang1 will become unusable in testing if it migrates on its own, and has wrong and broken dependencies.) Andi -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#728223: marked as done (dime: FTBFS on kFreeBSD: libtool can't build shared libraries)
Your message dated Sat, 27 Sep 2014 21:19:48 +
with message-id e1xxzpa-0002xp...@franck.debian.org
and subject line Bug#728223: fixed in dime 0.20111205-1
has caused the Debian Bug report #728223,
regarding dime: FTBFS on kFreeBSD: libtool can't build shared libraries
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.)
--
728223: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=728223
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
---BeginMessage---
Source: dime
Version: 0.20030921-4
Severity: serious
Justification: fails to build from source (but built successfully in the past)
Thanks for the prompt fix to #728212! Linux and Hurd builds now
succeed, but kFreeBSD builds are still failing, as libtool (presumably
an old version) doesn't know how to build shared libraries there:
checking dynamic linker characteristics... no
checking if libtool supports shared libraries... no
checking whether to build shared libraries... no
dh_install -a -O--parallel -O--builddirectory=build
dh_install: libdime1 missing files (usr/lib/*/libdime.so.1.0.0), aborting
make: *** [binary-arch] Error 2
Could you please look into this error as well?
Thanks!
---End Message---
---BeginMessage---
Source: dime
Source-Version: 0.20111205-1
We believe that the bug you reported is fixed in the latest version of
dime, 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 728...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
A. Maitland Bottoms bott...@debian.org (supplier of updated dime package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Format: 1.8
Date: Fri, 26 Sep 2014 23:35:38 -0400
Source: dime
Binary: dime libdime1 libdime-dev libdime-doc
Architecture: source amd64 all
Version: 0.20111205-1
Distribution: unstable
Urgency: low
Maintainer: A. Maitland Bottoms bott...@debian.org
Changed-By: A. Maitland Bottoms bott...@debian.org
Description:
dime - DXF Import, Manipulation, and Export programs
libdime-dev - DXF Import, Manipulation, and Export library - devel
libdime-doc - DXF Import, Manipulation, and Export library - devel
libdime1 - DXF Import, Manipulation, and Export library
Closes: 558854 727358 728223
Changes:
dime (0.20111205-1) unstable; urgency=low
.
* upstream updates
Now using BSD license
* minimal patch to build on kfreebsd (Closes: #728223)
* links correctly (Closes: #558854)
* update config.{guess,sub} files --with autotools_dev (Closes: #727358)
Checksums-Sha1:
70531ea9bc9d52249debb1e59c14e0ad563d3e82 1938 dime_0.20111205-1.dsc
bf94bb0e421ecd6e8e4ee183ce182d841e38fa5d 540721 dime_0.20111205.orig.tar.bz2
8183a9bfbd0f5b663c69016e403e8ecf508bfbcd 42668 dime_0.20111205-1.debian.tar.xz
21046c43cee189e51b9640c0819157b3f8273b20 8084 dime_0.20111205-1_amd64.deb
9aa30a4a29c6d5ea06e24a637889d604ad6efb1a 98636 libdime1_0.20111205-1_amd64.deb
f75408b949b7efcee7a09277b58a855866b7c462 24104
libdime-dev_0.20111205-1_amd64.deb
3710069395f625c0b391ec722f3d501a48f72b8d 255570
libdime-doc_0.20111205-1_all.deb
Checksums-Sha256:
0d7e88f143d70eb1eed9fdfee535310e2668def8659c8da75dba91ab2e0fcc21 1938
dime_0.20111205-1.dsc
a5f1738d4b2c1f17a0f8f06ceabecd9c5be41cbb092b30033cede7af78eec5ce 540721
dime_0.20111205.orig.tar.bz2
e7ab2241fc181d3e75985038a771651314c0e48836332714094ef2142929087b 42668
dime_0.20111205-1.debian.tar.xz
34ea2365e9d5fdc83b4c4a7e6bd47705f659669549e1eafa923427b8190c0ff1 8084
dime_0.20111205-1_amd64.deb
6386884faa0a296a5a5a61e311b60b34d5f13245aa0e46f9d103c55b498dfa7f 98636
libdime1_0.20111205-1_amd64.deb
df08ed1d934057cf16f9e60ddeaff7f6b4a39122c7feea5541f9cca589b77b69 24104
libdime-dev_0.20111205-1_amd64.deb
ed3ebf8e03361a916bfdc2a20dbeb8dcbcf89cbf96a91dec7c6fdcd56f31b062 255570
libdime-doc_0.20111205-1_all.deb
Files:
c6c5a552e670fe07aaa29588914890be 8084 graphics optional
dime_0.20111205-1_amd64.deb
fb394321df48282efdbe0013b0236751 98636 libs optional
libdime1_0.20111205-1_amd64.deb
7a985bbcc6a71ab8dfff153d577ca3bf 24104 libdevel optional
libdime-dev_0.20111205-1_amd64.deb
b4db2f5578b0d90f4639fc14c1ed8623 255570 doc optional
libdime-doc_0.20111205-1_all.deb
Bug#763047: marked as done (libcitygml: FTBFS with new openscenegraph)
Your message dated Sat, 27 Sep 2014 21:23:46 +
with message-id e1xxzt0-0003gn...@franck.debian.org
and subject line Bug#763047: fixed in libcitygml 0.14+svn134-1+3p2p1
has caused the Debian Bug report #763047,
regarding libcitygml: FTBFS with new openscenegraph
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.)
--
763047: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=763047
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
---BeginMessage---
Source: libcitygml
Version: 0.14+svn134-1+3p2p0
Severity: serious
Control: block 756478 by -1
On 24/09/14 23:51, Jonathan Wiltshire wrote:
There's a FTBFS in libcitygml because it can't cope with openscenegraph being
multiarched. Patch attached (although I have my doubts about that technique in
the first place), please file a bug and get it fixed.
As explained above your package now FTBFS. Patch from Jonathan Wiltshire
attached.
Emilio
diff -Nru libcitygml-0.14+svn134/debian/gencontrol libcitygml-0.14+svn134/debian/gencontrol
--- libcitygml-0.14+svn134/debian/gencontrol 2014-02-01 07:03:45.0 +
+++ libcitygml-0.14+svn134/debian/gencontrol 2014-09-24 22:47:14.0 +0100
@@ -1,4 +1,4 @@
-LIBOSG_SHARE=`dpkg --get-selections | grep libopenscenegraph[0-9]*\s*install | awk '{print $1}'`
+LIBOSG_SHARE=`dpkg --get-selections | grep libopenscenegraph[0-9]*:[[:alnum:]]*\s*install | awk '{print $1}'`
LIBOSG_VERSION=`dpkg -l $LIBOSG_SHARE | grep ^ii\s*$LIBOSG_SHARE | sed 's/-/ /' | awk '{print $3}'`
TMP1=`echo $LIBOSG_VERSION | awk -F '.' '{print $1}'`
TMP2=`echo $LIBOSG_VERSION | awk -F '.' '{print $2}'`
diff -Nru libcitygml-0.14+svn134/debian/openscenegraph-plugin-citygml-shared.install libcitygml-0.14+svn134/debian/openscenegraph-plugin-citygml-shared.install
--- libcitygml-0.14+svn134/debian/openscenegraph-plugin-citygml-shared.install 2014-02-01 07:03:45.0 +
+++ libcitygml-0.14+svn134/debian/openscenegraph-plugin-citygml-shared.install 2014-09-24 22:46:42.0 +0100
@@ -1 +1 @@
-usr/lib/osgPlugins-*/*.so
+usr/lib/*/osgPlugins-*/*.so
diff -Nru libcitygml-0.14+svn134/debian/openscenegraph-plugin-citygml-static.install libcitygml-0.14+svn134/debian/openscenegraph-plugin-citygml-static.install
--- libcitygml-0.14+svn134/debian/openscenegraph-plugin-citygml-static.install 2014-02-01 07:03:45.0 +
+++ libcitygml-0.14+svn134/debian/openscenegraph-plugin-citygml-static.install 2014-09-24 22:46:53.0 +0100
@@ -1 +1 @@
-usr/lib/osgPlugins-*/*.a
+usr/lib/*/osgPlugins-*/*.a
---End Message---
---BeginMessage---
Source: libcitygml
Source-Version: 0.14+svn134-1+3p2p1
We believe that the bug you reported is fixed in the latest version of
libcitygml, 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 763...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Bas Couwenberg sebas...@xs4all.nl (supplier of updated libcitygml package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Format: 1.8
Date: Sat, 27 Sep 2014 16:39:53 +0200
Source: libcitygml
Binary: libcitygml0 libcitygml0-dev libcitygml0-bin
openscenegraph-plugin-citygml-shared openscenegraph-plugin-citygml-static
Architecture: source amd64
Version: 0.14+svn134-1+3p2p1
Distribution: unstable
Urgency: medium
Maintainer: Debian GIS Project pkg-grass-de...@lists.alioth.debian.org
Changed-By: Bas Couwenberg sebas...@xs4all.nl
Description:
libcitygml0 - Open source C++ library for parsing CityGML files
libcitygml0-bin - Utils of libcitygml - citygml2vrml and citygmltest
libcitygml0-dev - Static and header files of libcitygml
openscenegraph-plugin-citygml-shared - libcitygml OpenSceneGraph plugin
(shared version)
openscenegraph-plugin-citygml-static - libcitygml OpenSceneGraph plugin
(static version)
Closes: 763047
Changes:
libcitygml (0.14+svn134-1+3p2p1) unstable; urgency=medium
.
* Team upload.
* Apply patch from Jonathan Wiltshire to fix FTBFS with OpenSceneGraph 3.2.1.
(closes: #763047)
Checksums-Sha1:
5a590af045550398d6ab546179f8c16a9f050f9b 2402
libcitygml_0.14+svn134-1+3p2p1.dsc
a9a18b990fcb793ef2469a137adc2a9bec314f12 41232
libcitygml_0.14+svn134.orig.tar.xz
Bug#763013: [pkg-dhcp-devel] Bug#762923: Bug#763013 closed by Thijs Kinkhorst th...@debian.org (Re: isc-dhcp-client depends on /bin/bash, not /bin/sh)
Hi Troy, Troy Benjegerdes wrote: On Sat, Sep 27, 2014 at 04:33:28PM +0200, Axel Beckert wrote: Troy Benjegerdes wrote: I had an unusable system after removing bash because of dhclient. [...] So far my biggest problem removing bash is the dire warnings from dpkg/apt about how essential bash is, Guess why there are these warnings? I would argue that unessentializing bash should be a release-critical bug for Jessie, not Jessie+1. I wrote release-goal for Jessie+1, not release-critical bug. That's a completely different thing. Please read https://www.debian.org/Bugs/Developer#severities, https://wiki.debian.org/ReleaseGoals and https://www.debian.org/doc/debian-policy/ch-binary.html#s3.8 before trying to continue this discussion. About removing bash from the list of Essential packages, please have a look at https://wiki.debian.org/Proposals/RemoveBashFromEssential which lists what at least needs to be fixed before we can proceed. Regards, Axel -- ,''`. | Axel Beckert a...@debian.org, http://people.debian.org/~abe/ : :' : | Debian Developer, ftp.ch.debian.org Admin `. `' | 1024D: F067 EA27 26B9 C3FC 1486 202E C09E 1D89 9593 0EDE `-| 4096R: 2517 B724 C5F6 CA99 5329 6E61 2FF9 CD59 6126 16B5 -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#758972: Mojarra update 2.2.8
On Wed, Sep 17, 2014 at 11:37:35AM +0200, Markus Koschany wrote: Could you push your changes to Git please? I pushed a branch named 2.2.8 to the git repo. This branch is nowhere near to be uploaded. To build it, you will need to add javaee-api-7.0.jar to the classpath. However, this is FTBFS for me. It would be great if you can try to build it. However, as I said previously 2.2.8 introduces a new dependency on Java EE 6/7 APIs but I found out some issues with the APIs source licensing. According to http://central.maven.org/maven2/javax/javaee-api/7.0/javaee-api-7.0.pom that code is dual licensed under GPLv2 and CDDL. However there are some .java files in the source with confidential clauses and some weird non-free disclaimers. Maybe those disclaimers are outdated, I have to confirm this and if everything is OK, then get that package in the archive. I have written a new debian/copyright file and pushed it to experimental. Maybe you can use it as a starting point for the final release. I can confirm what you wrote. There is at least jsf-ri/systest-per-webapp/process-as-jspx/src/java/Blink.java which is non-free according to its license terms. I believe the other clauses are O.K. They are licensed under the GPL-2 with classpath exception or the CDDL and some files contain code fragments once licensed under Apache 2.0 Oh, I was talking about JavaEE API 7.0 source code. That Blink.java file can be removed from sources if needed. If you need some help, please feel free to ping me. Yep, I need help with this because I have not much free time in the last weeks and freeze deadline is approaching. Let me know if we can meet on irc, or we can continue via email as usual. I'll be working on this package (and the JavaEE one) this weekend. -- Miguel Landaeta, nomadium at debian.org secure email with PGP 0x6E608B637D8967E9 available at http://miguel.cc/key. Faith means not wanting to know what is true. -- Nietzsche signature.asc Description: Digital signature
Bug#761562: marked as done (osmosis: FTBFS: Execution failed for task ':osmosis-osm-binary:compileJava'.)
Your message dated Sat, 27 Sep 2014 21:51:42 +
with message-id e1xxzu2-0007ei...@franck.debian.org
and subject line Bug#761562: fixed in osmosis 0.43.1-2
has caused the Debian Bug report #761562,
regarding osmosis: FTBFS: Execution failed for task
':osmosis-osm-binary:compileJava'.
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.)
--
761562: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=761562
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
---BeginMessage---
Source: osmosis
Version: 0.43.1-1
Severity: serious
Tags: jessie sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20140913 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):
make[1]: Entering directory '/«PKGBUILDDIR»'
gradle --offline --no-daemon \
--gradle-user-home debian/gradle-user-home \
--project-prop osmosisBuildType=RELEASE \
assemble
:osmosis-core:generateJavaSources
warning: [options] bootstrap class path not set in conjunction with -source
1.6
Note:
/«PKGBUILDDIR»/osmosis-core/src/main/java/org/openstreetmap/osmosis/core/container/v0_6/EntityContainerBuilder.java
uses or overrides a deprecated API.
Note: Recompile with -Xlint:deprecation for details.
1 warning
:osmosis-core:compileJava
:osmosis-core:generateResources
:osmosis-core:processResources
:osmosis-core:classes
:osmosis-core:jar
warning: [options] bootstrap class path not set in conjunction with -source
1.6
1 warning
:osmosis-set:compileJava
:osmosis-set:processResources
:osmosis-set:classes
:osmosis-set:jar
warning: [options] bootstrap class path not set in conjunction with -source
1.6
1 warning
:osmosis-xml:compileJava
:osmosis-xml:processResources
:osmosis-xml:classes
:osmosis-xml:jar
warning: [options] bootstrap class path not set in conjunction with -source
1.6
1 warning
:osmosis-replication:compileJava
:osmosis-replication:processResources
:osmosis-replication:classes
:osmosis-replication:jar
warning: [options] bootstrap class path not set in conjunction with -source
1.6
1 warning
:osmosis-apidb:compileJava
:osmosis-apidb:processResources
:osmosis-apidb:classes
:osmosis-apidb:jar
:osmosis-core:javadoc
:osmosis-set:javadoc
:osmosis-xml:javadoc
:osmosis-replication:javadoc
:osmosis-apidb:javadoc
:osmosis-apidb:javadocJar
:osmosis-apidb:sourcesJar
:osmosis-apidb:signArchives SKIPPED
:osmosis-apidb:assemble
warning: [options] bootstrap class path not set in conjunction with -source
1.6
1 warning
:osmosis-areafilter:compileJava
:osmosis-areafilter:processResources
:osmosis-areafilter:classes
:osmosis-areafilter:jar
:osmosis-areafilter:javadoc
:osmosis-areafilter:javadocJar
:osmosis-areafilter:sourcesJar
:osmosis-areafilter:signArchives SKIPPED
:osmosis-areafilter:assemble
:osmosis-core:javadocJar
:osmosis-core:sourcesJar
:osmosis-core:signArchives SKIPPED
:osmosis-core:assemble
warning: [options] bootstrap class path not set in conjunction with -source
1.6
1 warning
:osmosis-dataset:compileJava
:osmosis-dataset:processResources
:osmosis-dataset:classes
:osmosis-dataset:jar
:osmosis-dataset:javadoc
:osmosis-dataset:javadocJar
:osmosis-dataset:sourcesJar
:osmosis-dataset:signArchives SKIPPED
:osmosis-dataset:assemble
warning: [options] bootstrap class path not set in conjunction with -source
1.6
1 warning
:osmosis-extract:compileJava
:osmosis-extract:processResources
:osmosis-extract:classes
:osmosis-extract:jar
:osmosis-extract:javadoc
:osmosis-extract:javadocJar
:osmosis-extract:sourcesJar
:osmosis-extract:signArchives SKIPPED
:osmosis-extract:assemble
warning: [options] bootstrap class path not set in conjunction with -source
1.6
1 warning
:osmosis-hstore-jdbc:compileJava
:osmosis-hstore-jdbc:processResources
:osmosis-hstore-jdbc:classes
:osmosis-hstore-jdbc:jar
:osmosis-hstore-jdbc:javadoc
:osmosis-hstore-jdbc:javadocJar
:osmosis-hstore-jdbc:sourcesJar
:osmosis-hstore-jdbc:signArchives SKIPPED
:osmosis-hstore-jdbc:assemble
warning: [options] bootstrap class path not set in conjunction with -source
1.6
/«PKGBUILDDIR»/osmosis-osm-binary/gen-src/main/java/org/openstreetmap/osmosis/osmbinary/Osmformat.java:578:
error: method parseUnknownField in class BuilderMessageType,BuilderType
cannot be applied to given types;
if (!parseUnknownField(input, extensionRegistry, tag)) {
^
required: CodedInputStream,CodedOutputStream,ExtensionRegistryLite,int
found:
Processed: geographiclib blocked by doxygen bug
Processing commands for cont...@bugs.debian.org: block 762485 with 762959 Bug #762485 [src:geographiclib] geographiclib: FTBFS on 32-bit architectures: symbols not quite as expected 762485 was not blocked by any bugs. 762485 was not blocking any bugs. Added blocking bug(s) of 762485: 763019, 763011, 762959, and 762994 thanks Stopping processing here. Please contact me if you need assistance. -- 762485: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=762485 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#763115: guile-2.0 FTBFS on armhf
Package: guile-2.0
Version: 2.0.11+1-5
Severity: serious
Hi,
guile-2.0 now FTBFS on armhf:
CC libguile_2.0_la-regex-posix.lo
In file included from vm.c:668:0:
vm-engine.c: In function 'vm_regular_engine':
vm-engine.c:168:1: error: r7 cannot be used in asm here
}
^
CC guile-guile.o
flex -t ./c-tokenize.lex c-tokenize.c || { rm c-tokenize.c; false; }
GEN c-tokenize.o
GEN guile_filter_doc_snarfage
make[4]: *** [libguile_2.0_la-vm.lo] Error 1
make[4]: *** Waiting for unfinished jobs
Makefile:3190: recipe for target 'libguile_2.0_la-vm.lo' failed
(I thought we already had a bit of discussion about that last weekend,
but failing to find the bug report I submit this one now.)
Andi
--
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 763042 is normal
Processing commands for cont...@bugs.debian.org: # write fails with error, so not data loss severity 763042 normal Bug #763042 [src:linux] linux-image-3.16-2: davfs2 broken with 3.16 Severity set to 'normal' from 'grave' thanks Stopping processing here. Please contact me if you need assistance. -- 763042: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=763042 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#752220: automx: Some sources are not included in your package
Control: tag -1 + pending
Hi,
Bastien ROUCARIES wrote:
src/foundation-scss/javascripts/vendor/custom.modernizr.js
src/html/js/vendor/custom.modernizr.js
The source for those two is available at
http://modernizr.com/downloads/modernizr-2.6.2.js
This is a false positiv, you should override lintian warning
src/html/js/foundation.min.js
Indeed, the sources are at src/html/js/foundation/.
I've just uploaded a non-maintainer upload to DELAYED/2. It adds
modernizr-2.6.2.js to debian/missing-sources and contains according
some lintian overrides. Full debdiff attached.
Feel free to tell me if I should delay it longer or sponsor an
alternative upload. But keep in mind that the freeze is approaching
very quickly and fixing this issue shouldn't be delayed much longer.
Regards, Axel
--
,''`. | Axel Beckert a...@debian.org, http://people.debian.org/~abe/
: :' : | Debian Developer, ftp.ch.debian.org Admin
`. `' | 1024D: F067 EA27 26B9 C3FC 1486 202E C09E 1D89 9593 0EDE
`-| 4096R: 2517 B724 C5F6 CA99 5329 6E61 2FF9 CD59 6126 16B5
diff -Nru automx-0.10.0/debian/changelog automx-0.10.0/debian/changelog
--- automx-0.10.0/debian/changelog 2013-12-03 20:26:42.0 +0100
+++ automx-0.10.0/debian/changelog 2014-09-28 00:36:47.0 +0200
@@ -1,3 +1,11 @@
+automx (0.10.0-2.1) unstable; urgency=low
+
+ * Non-maintainer upload
+ * Add modernizr-2.6.2.js to debian/missing-sources. (Closes: #752220)
+ * Add lintian overrides for source-is-missing false positives.
+
+ -- Axel Beckert a...@debian.org Sun, 28 Sep 2014 00:34:27 +0200
+
automx (0.10.0-2) unstable; urgency=low
* Fixed control fields, added Vcs field
diff -Nru automx-0.10.0/debian/missing-sources/modernizr-2.6.2.js
automx-0.10.0/debian/missing-sources/modernizr-2.6.2.js
--- automx-0.10.0/debian/missing-sources/modernizr-2.6.2.js 1970-01-01
01:00:00.0 +0100
+++ automx-0.10.0/debian/missing-sources/modernizr-2.6.2.js 2014-07-05
16:02:26.0 +0200
@@ -0,0 +1,1393 @@
+/*!
+ * Modernizr v2.6.2
+ * www.modernizr.com
+ *
+ * Copyright (c) Faruk Ates, Paul Irish, Alex Sexton
+ * Available under the BSD and MIT licenses: www.modernizr.com/license/
+ */
+
+/*
+ * Modernizr tests which native CSS3 and HTML5 features are available in
+ * the current UA and makes the results available to you in two ways:
+ * as properties on a global Modernizr object, and as classes on the
+ * html element. This information allows you to progressively enhance
+ * your pages with a granular level of control over the experience.
+ *
+ * Modernizr has an optional (not included) conditional resource loader
+ * called Modernizr.load(), based on Yepnope.js (yepnopejs.com).
+ * To get a build that includes Modernizr.load(), as well as choosing
+ * which tests to include, go to www.modernizr.com/download/
+ *
+ * AuthorsFaruk Ates, Paul Irish, Alex Sexton
+ * Contributors Ryan Seddon, Ben Alman
+ */
+
+window.Modernizr = (function( window, document, undefined ) {
+
+var version = '2.6.2',
+
+Modernizr = {},
+
+/*cssclasses*/
+// option for enabling the HTML classes to be added
+enableClasses = true,
+/*cssclasses*/
+
+docElement = document.documentElement,
+
+/**
+ * Create our modernizr element that we do most feature tests on.
+ */
+mod = 'modernizr',
+modElem = document.createElement(mod),
+mStyle = modElem.style,
+
+/**
+ * Create the input element for various Web Forms feature tests.
+ */
+inputElem /*inputelem*/ = document.createElement('input')
/*inputelem*/ ,
+
+/*smile*/
+smile = ':)',
+/*smile*/
+
+toString = {}.toString,
+
+// TODO :: make the prefixes more granular
+/*prefixes*/
+// List of property values to set for css tests. See ticket #21
+prefixes = ' -webkit- -moz- -o- -ms- '.split(' '),
+/*prefixes*/
+
+/*domprefixes*/
+// Following spec is to expose vendor-specific style properties as:
+// elem.style.WebkitBorderRadius
+// and the following would be incorrect:
+// elem.style.webkitBorderRadius
+
+// Webkit ghosts their properties in lowercase but Opera Moz do not.
+// Microsoft uses a lowercase `ms` instead of the correct `Ms` in IE8+
+// erik.eae.net/archives/2008/03/10/21.48.10/
+
+// More here: github.com/Modernizr/Modernizr/issues/issue/21
+omPrefixes = 'Webkit Moz O ms',
+
+cssomPrefixes = omPrefixes.split(' '),
+
+domPrefixes = omPrefixes.toLowerCase().split(' '),
+/*domprefixes*/
+
+/*ns*/
+ns = {'svg': 'http://www.w3.org/2000/svg'},
+/*ns*/
+
+tests = {},
+inputs = {},
+attrs = {},
+
+classes = [],
+
+slice = classes.slice,
+
+featureName, // used in testing loop
+
+
+/*teststyles*/
+// Inject element with style element and some CSS rules
+injectElementWithStyles = function( rule, callback, nodes, testnames ) {
+
+ var style, ret, node, docOverflow,
+
Processed: Re: Bug#752220: automx: Some sources are not included in your package
Processing control commands: tag -1 + pending Bug #752220 [automx] automx] Some sources are not included in your package Added tag(s) pending. -- 752220: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=752220 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#758972: Mojarra update 2.2.8
On Sat, Sep 27, 2014 at 06:44:47PM -0300, Miguel Landaeta wrote: Yep, I need help with this because I have not much free time in the last weeks and freeze deadline is approaching. Looking more closely at this I noticed the only package in Debian depending on mojarra packages is libspring-java. libspring-java build-depends only on libjsf-api-java. mojarra also provides libjsf-impl-java but there are not packages in Debian depending on this package. I already checked javax.faces 2.2 API and is compatible with 2.0 and libspring-java build doesn't break with the new mojarra version, so I'm going to upload a new mojarra package very soon but only providing the API. Given the deadlines and since this solution doesn't break anything available in Debian I think is a good approach. I'm going to combine our two branches and prepare the new upload. -- Miguel Landaeta, nomadium at debian.org secure email with PGP 0x6E608B637D8967E9 available at http://miguel.cc/key. Faith means not wanting to know what is true. -- Nietzsche signature.asc Description: Digital signature
Processed: forcibly merging 678696 616689 633024 718533 742962 752381
Processing commands for cont...@bugs.debian.org: forcemerge 678696 616689 633024 718533 742962 752381 Bug #678696 [initramfs-tools] Event based block device handling (fixes USB and nested devices problem) Bug #707286 [initramfs-tools] linux-image-3.8-1-amd64: makes system unbootable Bug #712984 [initramfs-tools] linux-image-3.9-1-amd64: Unable to find LVM volume system/root Bug #712999 [initramfs-tools] linux-image-3.9-1-amd64: Unable to find LVM volume Bug #742962 [initramfs-tools] fails to mount root when root is on lvm. Severity set to 'serious' from 'normal' Marked as found in versions initramfs-tools/0.113, initramfs-tools/0.98.8, initramfs-tools/0.112, initramfs-tools/0.99, initramfs-tools/0.106, initramfs-tools/0.109.1, initramfs-tools/0.98.7, and initramfs-tools/0.115~bpo70+1. Added tag(s) patch. Bug #752381 [initramfs-tools] initramfs-tools: does not activate logical volume before trying to mount root filesystem on LVM Severity set to 'serious' from 'important' Marked as found in versions initramfs-tools/0.113, initramfs-tools/0.98.8, initramfs-tools/0.112, initramfs-tools/0.99, initramfs-tools/0.106, initramfs-tools/0.109.1, and initramfs-tools/0.98.7. Added tag(s) patch. Bug #616689 [initramfs-tools] Root-on-LVM setup fails often due to timing issues Severity set to 'serious' from 'important' Removed indication that 616689 affects src:linux-2.6 and linux-2.6 Marked as found in versions initramfs-tools/0.113, initramfs-tools/0.112, initramfs-tools/0.99, initramfs-tools/0.106, initramfs-tools/0.109.1, and initramfs-tools/0.115~bpo70+1. Added tag(s) patch. Bug #678696 [initramfs-tools] Event based block device handling (fixes USB and nested devices problem) Marked as found in versions initramfs-tools/0.113, initramfs-tools/0.98.8, initramfs-tools/0.99, initramfs-tools/0.98.7, and initramfs-tools/0.115~bpo70+1. Marked as found in versions initramfs-tools/0.113, initramfs-tools/0.98.8, initramfs-tools/0.99, initramfs-tools/0.98.7, and initramfs-tools/0.115~bpo70+1. Marked as found in versions initramfs-tools/0.113, initramfs-tools/0.98.8, initramfs-tools/0.99, initramfs-tools/0.98.7, and initramfs-tools/0.115~bpo70+1. Marked as found in versions initramfs-tools/0.98.8, initramfs-tools/0.99, initramfs-tools/0.98.7, and initramfs-tools/0.115~bpo70+1. Bug #633024 [initramfs-tools] initramfs-tools: Race condition when root filesystem is on a LV and mdadm array Severity set to 'serious' from 'important' Marked as found in versions initramfs-tools/0.113, initramfs-tools/0.98.8, initramfs-tools/0.112, initramfs-tools/0.106, initramfs-tools/0.109.1, initramfs-tools/0.98.7, and initramfs-tools/0.115~bpo70+1. Added tag(s) patch. Bug #718533 [initramfs-tools] linux-image-3.10-1-amd64 fails to boot with RAID5 Severity set to 'serious' from 'important' Marked as found in versions initramfs-tools/0.98.8, initramfs-tools/0.112, initramfs-tools/0.99, initramfs-tools/0.106, initramfs-tools/0.109.1, initramfs-tools/0.98.7, and initramfs-tools/0.115~bpo70+1. Added tag(s) patch. Bug #707286 [initramfs-tools] linux-image-3.8-1-amd64: makes system unbootable Bug #712984 [initramfs-tools] linux-image-3.9-1-amd64: Unable to find LVM volume system/root Bug #712999 [initramfs-tools] linux-image-3.9-1-amd64: Unable to find LVM volume Merged 616689 633024 678696 707286 712984 712999 718533 742962 752381 thanks Stopping processing here. Please contact me if you need assistance. -- 616689: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=616689 633024: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=633024 678696: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=678696 707286: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=707286 712984: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=712984 712999: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=712999 718533: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=718533 742962: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=742962 752381: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=752381 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: tagging 678696
Processing commands for cont...@bugs.debian.org: # attached patch causes regressions, so a new patch is needed tags 678696 - patch Bug #678696 [initramfs-tools] Event based block device handling (fixes USB and nested devices problem) Bug #616689 [initramfs-tools] Root-on-LVM setup fails often due to timing issues Bug #633024 [initramfs-tools] initramfs-tools: Race condition when root filesystem is on a LV and mdadm array Bug #707286 [initramfs-tools] linux-image-3.8-1-amd64: makes system unbootable Bug #712984 [initramfs-tools] linux-image-3.9-1-amd64: Unable to find LVM volume system/root Bug #712999 [initramfs-tools] linux-image-3.9-1-amd64: Unable to find LVM volume Bug #718533 [initramfs-tools] linux-image-3.10-1-amd64 fails to boot with RAID5 Bug #742962 [initramfs-tools] fails to mount root when root is on lvm. Bug #752381 [initramfs-tools] initramfs-tools: does not activate logical volume before trying to mount root filesystem on LVM Removed tag(s) patch. Removed tag(s) patch. Removed tag(s) patch. Removed tag(s) patch. Removed tag(s) patch. Removed tag(s) patch. Removed tag(s) patch. Removed tag(s) patch. Removed tag(s) patch. thanks Stopping processing here. Please contact me if you need assistance. -- 616689: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=616689 633024: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=633024 678696: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=678696 707286: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=707286 712984: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=712984 712999: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=712999 718533: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=718533 742962: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=742962 752381: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=752381 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: tagging 762984
Processing commands for cont...@bugs.debian.org: tags 762984 - moreinfo Bug #762984 [initramfs-tools] initramfs-tools: Alert! /dev/vg0/usr does not exist Removed tag(s) moreinfo. thanks Stopping processing here. Please contact me if you need assistance. -- 762984: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=762984 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#762236: parted: [kfreebsd] use of kern.geom.debugflags is unsafe
On Mon, Sep 22, 2014 at 09:11:22AM -0400, Phillip Susi wrote: As for the performance implications, yes, parted should not be using O_RDWR when it do doesn't need it and does take care not to on linux. It does? linux_open appears to just open read-write, and only falls back to read-only if a read-write mount fails. I can't find anything special that arranges to do read-only mounts when write support isn't needed. Can you point me to the bit I'm missing? Thanks, -- Colin Watson [cjwat...@debian.org] -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#746126: Patch to fix build issue
Control: tag -1 + pending Hi Keith and Johannes, Johannes Brandstätter wrote: the provided debdiff fixes the build issue for me. Apparently cairo-5c is now needed to build the package. Johannes: Thanks for the investigation and debdiff. I've sponsored your NMU and uploaded it to DELAYED/4. Keith: Feel free to tell me if I should increase or decrease the delay of the NMU. Regards, Axel -- ,''`. | Axel Beckert a...@debian.org, http://people.debian.org/~abe/ : :' : | Debian Developer, ftp.ch.debian.org Admin `. `' | 1024D: F067 EA27 26B9 C3FC 1486 202E C09E 1D89 9593 0EDE `-| 4096R: 2517 B724 C5F6 CA99 5329 6E61 2FF9 CD59 6126 16B5 signature.asc Description: Digital signature
Processed: Re: Bug#746126: Patch to fix build issue
Processing control commands: tag -1 + pending Bug #746126 [src:ricochet] ricochet: FTBFS: buiild errors Added tag(s) pending. -- 746126: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=746126 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#746126: Patch to fix build issue
Hi Keith, Axel Beckert wrote: Johannes Brandstätter wrote: the provided debdiff fixes the build issue for me. Apparently cairo-5c is now needed to build the package. After the upload I noticed the following: While the upload will fix the bug filed against ricochet, it won't help propagating ricochet to testing as one of it's dependencies isn't in testing either: cairo-5c FTBFS due to test suite failures: https://bugs.debian.org/708459 Unfortunately I have no idea how to fix that. I though think that those two issues are not related and will hence leave the NMU in the DELAYED queue. Regards, Axel -- ,''`. | Axel Beckert a...@debian.org, http://people.debian.org/~abe/ : :' : | Debian Developer, ftp.ch.debian.org Admin `. `' | 1024D: F067 EA27 26B9 C3FC 1486 202E C09E 1D89 9593 0EDE `-| 4096R: 2517 B724 C5F6 CA99 5329 6E61 2FF9 CD59 6126 16B5 -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#762230: marked as done (lilypond: debian/rules sets HOME=/tmp)
Your message dated Sun, 28 Sep 2014 00:34:59 + with message-id e1xy2s3-0004kl...@franck.debian.org and subject line Bug#762230: fixed in lilypond 2.18.2-3 has caused the Debian Bug report #762230, regarding lilypond: debian/rules sets HOME=/tmp 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.) -- 762230: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=762230 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Source: lilypond Version: 2.18.2-2 Severity: grave Tags: security This package's debian/rules sets HOME set to /tmp in debian/rules. But HOME is supposed to be writable only by trusted users, whereas /tmp is world-writable. For example, python2.7 (which debian/rules indirectly runs) loads code from $HOME/.local/lib/python2.7/site-packages/. -- Jakub Wilk ---End Message--- ---BeginMessage--- Source: lilypond Source-Version: 2.18.2-3 We believe that the bug you reported is fixed in the latest version of lilypond, 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 762...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Don Armstrong d...@debian.org (supplier of updated lilypond package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Fri, 26 Sep 2014 11:43:19 -0700 Source: lilypond Binary: lilypond lilypond-data lilypond-doc lilypond-doc-pdf lilypond-doc-html lilypond-doc-html-cs lilypond-doc-html-de lilypond-doc-html-es lilypond-doc-html-fr lilypond-doc-html-hu lilypond-doc-html-it lilypond-doc-html-ja lilypond-doc-html-nl lilypond-doc-html-zh lilypond-doc-pdf-de lilypond-doc-pdf-es lilypond-doc-pdf-fr lilypond-doc-pdf-hu lilypond-doc-pdf-it lilypond-doc-pdf-nl Architecture: source amd64 all Version: 2.18.2-3 Distribution: sid Urgency: high Maintainer: Don Armstrong d...@debian.org Changed-By: Don Armstrong d...@debian.org Description: lilypond - program for typesetting sheet music lilypond-data - LilyPond music typesetter (data files) lilypond-doc - LilyPond Documentation in info format (and meta package) lilypond-doc-html - LilyPond HTML Documentation lilypond-doc-html-cs - LilyPond HTML Documentation in Czech lilypond-doc-html-de - LilyPond HTML Documentation in German lilypond-doc-html-es - LilyPond HTML Documentation in Spanish lilypond-doc-html-fr - LilyPond HTML Documentation in French lilypond-doc-html-hu - LilyPond HTML Documentation in Hungarian lilypond-doc-html-it - LilyPond HTML Documentation in Italian lilypond-doc-html-ja - LilyPond HTML Documentation in Japanese lilypond-doc-html-nl - LilyPond HTML Documentation in Dutch lilypond-doc-html-zh - LilyPond HTML Documentation in Chinese lilypond-doc-pdf - LilyPond PDF Documentation lilypond-doc-pdf-de - LilyPond PDF Documentation in German lilypond-doc-pdf-es - LilyPond PDF Documentation in Spanish lilypond-doc-pdf-fr - LilyPond PDF Documentation in French lilypond-doc-pdf-hu - LilyPond PDF Documentation in Hungarian lilypond-doc-pdf-it - LilyPond PDF Documentation in Italian lilypond-doc-pdf-nl - LilyPond PDF Documentation in Dutch Closes: 760794 762230 Changes: lilypond (2.18.2-3) unstable; urgency=high . * Revert previous patch (no parallel); the issue was actually running tests on architecture independent builds which had not built any of the documentation. (Closes: #760794) * Stop setting HOME to /tmp in debian/rules. (Closes: #762230) Checksums-Sha1: b88cb224a29d126716d9a73e694403c9b0aea953 3796 lilypond_2.18.2-3.dsc 9d9e731b00f67b28033e9d89b0c3d4c0afedc12b 42780 lilypond_2.18.2-3.debian.tar.xz 701c50cc73a9f07b927216ba6cdf9afdb81a3d1b 1451864 lilypond_2.18.2-3_amd64.deb 00c9632c24f9f32b11539c1fe1eca0429598af43 1545166 lilypond-data_2.18.2-3_all.deb f9773cd60752ed25834d6c23345a8f9511fa7294 15489838 lilypond-doc_2.18.2-3_all.deb 1e46a371a0ba5a7702ec7287fa9c0f096c4435f1 47756556 lilypond-doc-pdf_2.18.2-3_all.deb ad3691c422cc49bb898b3bf9100a757bf58648ff 8630586 lilypond-doc-html_2.18.2-3_all.deb 7b41250c5378d9ce4cf3246bfdd87294109d73d6 1430168 lilypond-doc-html-cs_2.18.2-3_all.deb fbab393ef22a0aabecada0d410987ab575119186 1644520 lilypond-doc-html-de_2.18.2-3_all.deb
Bug#760794: marked as done (lilypond: FTBFS on powerpc and mips)
Your message dated Sun, 28 Sep 2014 00:34:59 + with message-id e1xy2s3-0004kf...@franck.debian.org and subject line Bug#760794: fixed in lilypond 2.18.2-3 has caused the Debian Bug report #760794, regarding lilypond: FTBFS on powerpc and mips 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.) -- 760794: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=760794 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: src:lilypond Version: 2.18.2-1 Tags: patch The latest lilypond upload fail to build on powerpc and mips. The build log available from URL: https://buildd.debian.org/status/logs.php?pkg=lilypondarch=powerpc . It is not clear to me exactly what is failing or how, but I was able to reproduce the build failure on the porter box partch.debian.org. Running 'debian/rules build' after the failure completed the build without any errors. Perhaps there is some race in the build? I then tried to remove the parallell setup in the build rules, and this fixed the build. As the build took 120 minutes, I did not try again. So this might solve the problem, or just reduce the chance. I do not know, but suggest to apply it to a new upload. diff -ru lilypond-2.18.2/debian/rules lilypond-2.18.2-pere/debian/rules --- lilypond-2.18.2/debian/rules2014-05-01 21:17:31.0 +0200 +++ lilypond-2.18.2-pere/debian/rules 2014-09-07 23:22:18.659823059 +0200 @@ -29,12 +29,12 @@ endif DOC_OPTIONS := WEB_TARGETS=offline -ifneq (,$(filter parallel=%,$(DEB_BUILD_OPTIONS))) - DOC_OPTIONS := $(DOC_OPTIONS) CPU_COUNT=$(firstword $(patsubst parallel=%,%,$(filter parallel=%,$(DEB_BUILD_OPTIONS -endif +#ifneq (,$(filter parallel=%,$(DEB_BUILD_OPTIONS))) +# DOC_OPTIONS := $(DOC_OPTIONS) CPU_COUNT=$(firstword $(patsubst parallel=%,%,$(filter parallel=%,$(DEB_BUILD_OPTIONS +#endif %: - dh $@ --parallel --with autotools-dev --with python2 --with quilt + dh $@ --with autotools-dev --with python2 --with quilt ## we need to nuke the parser files, because if there is a mistmatch The failing lilypond installation is blocking Debian Edu from installing in Jessie. It is a dependency of rosegarden and pulled in on all desktop installations in Debian Edu - which are currently uninstallable. Please help us fix it. :) -- Happy hacking Petter Reinholdtsen ---End Message--- ---BeginMessage--- Source: lilypond Source-Version: 2.18.2-3 We believe that the bug you reported is fixed in the latest version of lilypond, 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 760...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Don Armstrong d...@debian.org (supplier of updated lilypond package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Fri, 26 Sep 2014 11:43:19 -0700 Source: lilypond Binary: lilypond lilypond-data lilypond-doc lilypond-doc-pdf lilypond-doc-html lilypond-doc-html-cs lilypond-doc-html-de lilypond-doc-html-es lilypond-doc-html-fr lilypond-doc-html-hu lilypond-doc-html-it lilypond-doc-html-ja lilypond-doc-html-nl lilypond-doc-html-zh lilypond-doc-pdf-de lilypond-doc-pdf-es lilypond-doc-pdf-fr lilypond-doc-pdf-hu lilypond-doc-pdf-it lilypond-doc-pdf-nl Architecture: source amd64 all Version: 2.18.2-3 Distribution: sid Urgency: high Maintainer: Don Armstrong d...@debian.org Changed-By: Don Armstrong d...@debian.org Description: lilypond - program for typesetting sheet music lilypond-data - LilyPond music typesetter (data files) lilypond-doc - LilyPond Documentation in info format (and meta package) lilypond-doc-html - LilyPond HTML Documentation lilypond-doc-html-cs - LilyPond HTML Documentation in Czech lilypond-doc-html-de - LilyPond HTML Documentation in German lilypond-doc-html-es - LilyPond HTML Documentation in Spanish lilypond-doc-html-fr - LilyPond HTML Documentation in French lilypond-doc-html-hu - LilyPond HTML Documentation in Hungarian lilypond-doc-html-it - LilyPond HTML Documentation in Italian lilypond-doc-html-ja - LilyPond HTML Documentation in Japanese lilypond-doc-html-nl - LilyPond HTML Documentation in Dutch lilypond-doc-html-zh -
Bug#756916: vice: FTBFS[kfreebsd-amd64,powerpc]: error while opening src/arch/win32/res.rc.po.c for reading: No such file or directory
unarchive 725629 reopen 725629 = notfixed 725629 vice/2.4.dfsg+2.4.6-1 retitle 725629 vice: sometimes FTBFS: error while opening src/arch/win32/res.rc.po.c for reading: No such file or directory retitle 756916 vice: sometimes FTBFS: error while opening src/arch/win32/res.rc.po.c for reading: No such file or directory forcemerge 756916 725629 thanks Hi, This bug is the same as http://bugs.debian.org/725629, apparently not really fixed. That was seen on s390, and this has happened more recently on powerpc too: https://buildd.debian.org/status/logs.php?pkg=vicearch=powerpc I think it it is some kind of Makefile parallelism issue. Compare successful case: https://buildd.debian.org/status/fetch.php?pkg=vicearch=kfreebsd-amd64ver=2.4.dfsg%2B2.4.6-2stamp=1400020850 | Making all in po | make[2]: Entering directory '/«BUILDDIR»/vice-2.4.dfsg+2.4.6/po' | gcc -I.. -I../intl -g -O3 -Wall -Wno-inline ./intl2po.c -o intl2po | ( if test 'x.' != 'x.'; then \ | posrcprefix='../'; \ | else \ | posrcprefix=../; \ | fi; \ | rm -f POTFILES-t POTFILES \ | (sed -e '/^#/d' -e '/^[ ]*$/d' \ | -e s@.*@ $posrcprefix @ ./POTFILES.in \ | | sed -e '$s/\\$//') POTFILES-t \ | chmod a-w POTFILES-t \ | mv POTFILES-t POTFILES ) | cd .. \ |CONFIG_FILES=po/Makefile.in CONFIG_HEADERS= \ |/bin/sh ./config.status | config.status: creating po/Makefile.in | config.status: executing depfiles commands | config.status: executing default-1 commands | ./intl2po win32 ../src/arch/win32/res.rc ../src/arch/win32/res.rc.po.c .. .. with the failure case: https://buildd.debian.org/status/fetch.php?pkg=vicearch=kfreebsd-amd64ver=2.4.dfsg%2B2.4.7-1stamp=1406758769 | Making all in po | make[2]: Entering directory '/«BUILDDIR»/vice-2.4.dfsg+2.4.7/po' | gcc -I.. -I../intl -g -O3 -Wall -Wno-inline ./intl2po.c -o intl2po | ( if test 'x.' != 'x.'; then \ | posrcprefix='../'; \ | else \ | posrcprefix=../; \ | fi; \ | rm -f POTFILES-t POTFILES \ | (sed -e '/^#/d' -e '/^[ ]*$/d' \ | -e s@.*@ $posrcprefix @ ./POTFILES.in \ | | sed -e '$s/\\$//') POTFILES-t \ | chmod a-w POTFILES-t \ | mv POTFILES-t POTFILES ) | PATH=../src:$PATH /usr/bin/xgettext --default-domain=vice --directory=.. --directory=.. \ | --add-comments --keyword=_ --keyword=N_ \ | --files-from=./POTFILES.in \ | -o ./vice.pot | /usr/bin/xgettext: error while opening src/arch/win32/res.rc.po.c for reading: No such file or directory so it seems intl2po must happen before xgettext? 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 (with 1 errors): Re: Bug#756916: vice: FTBFS[kfreebsd-amd64,powerpc]: error while opening src/arch/win32/res.rc.po.c for reading: No such file or directory
Processing commands for cont...@bugs.debian.org:
unarchive 725629
Bug #725629 {Done: Laszlo Boszormenyi (GCS) g...@debian.org} [vice] Please
give back vice on s390
Unarchived Bug 725629
reopen 725629 =
Bug #725629 {Done: Laszlo Boszormenyi (GCS) g...@debian.org} [vice] Please
give back vice on s390
'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 vice/2.4.dfsg+2.4.6-1.
notfixed 725629 vice/2.4.dfsg+2.4.6-1
Bug #725629 [vice] Please give back vice on s390
Ignoring request to alter fixed versions of bug #725629 to the same values
previously set
retitle 725629 vice: sometimes FTBFS: error while opening
src/arch/win32/res.rc.po.c for reading: No such file or directory
Bug #725629 [vice] Please give back vice on s390
Changed Bug title to 'vice: sometimes FTBFS: error while opening
src/arch/win32/res.rc.po.c for reading: No such file or directory' from
'Please give back vice on s390'
retitle 756916 vice: sometimes FTBFS: error while opening
src/arch/win32/res.rc.po.c for reading: No such file or directory
Bug #756916 [src:vice] vice: FTBFS on kfreebsd-amd64: error while opening
src/arch/win32/res.rc.po.c for reading: No such file or directory
Changed Bug title to 'vice: sometimes FTBFS: error while opening
src/arch/win32/res.rc.po.c for reading: No such file or directory' from
'vice: FTBFS on kfreebsd-amd64: error while opening
src/arch/win32/res.rc.po.c for reading: No such file or directory'
forcemerge 756916 725629
Bug #756916 [src:vice] vice: sometimes FTBFS: error while opening
src/arch/win32/res.rc.po.c for reading: No such file or directory
Unable to merge bugs because:
package of #725629 is 'vice' not 'src:vice'
Failed to forcibly merge 756916: Did not alter merged bugs
thanks
Stopping processing here.
Please contact me if you need assistance.
--
725629: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=725629
756916: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=756916
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#756916: vice: FTBFS[kfreebsd-amd64,powerpc]: error while opening src/arch/win32/res.rc.po.c for reading: No such file or directory
Processing commands for cont...@bugs.debian.org: reassign 725629 src:vice Bug #725629 [vice] vice: sometimes FTBFS: error while opening src/arch/win32/res.rc.po.c for reading: No such file or directory Bug reassigned from package 'vice' to 'src:vice'. No longer marked as found in versions vice/2.4.dfsg-1. Ignoring request to alter fixed versions of bug #725629 to the same values previously set found 725629 vice/2.4.dfsg-1 Bug #725629 [src:vice] vice: sometimes FTBFS: error while opening src/arch/win32/res.rc.po.c for reading: No such file or directory Marked as found in versions vice/2.4.dfsg-1. forcemerge 756916 725629 Bug #756916 [src:vice] vice: sometimes FTBFS: error while opening src/arch/win32/res.rc.po.c for reading: No such file or directory Bug #725629 [src:vice] vice: sometimes FTBFS: error while opening src/arch/win32/res.rc.po.c for reading: No such file or directory Marked as found in versions vice/2.4.dfsg+2.4.7-1. Bug #756916 [src:vice] vice: sometimes FTBFS: error while opening src/arch/win32/res.rc.po.c for reading: No such file or directory Marked as found in versions vice/2.4.dfsg-1. Merged 725629 756916 thanks Stopping processing here. Please contact me if you need assistance. -- 725629: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=725629 756916: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=756916 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#759930: marked as done (bup: FTBFS: dh_auto_test: make -j1 test returned exit code 2)
Your message dated Sun, 28 Sep 2014 02:48:56 +0200 with message-id 20140928004856.ga1...@sym.noone.org and subject line Re: Bug#759930: bup: FTBFS: dh_auto_test: make -j1 test returned exit code 2 has caused the Debian Bug report #759930, regarding bup: FTBFS: dh_auto_test: make -j1 test returned exit code 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.) -- 759930: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=759930 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Source: bup Version: 0.25-1 Severity: serious Tags: jessie sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20140830 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): make[1]: Entering directory '/«PKGBUILDDIR»' rm -f lib/bup/_version.py lib/bup/_version.py.new ./debian/gen_version_py.sh lib/bup/_version.py.new mv lib/bup/_version.py.new lib/bup/_version.py rm -f bup ln -s main.py bup t/configure-sampledata --setup ./wvtestrun make PYTHON=python runtests Testing all in make PYTHON=python runtests: ! lib/bup/t/tbloom.py test_bloom: . 0.072s ok ! lib/bup/t/tclient.py test_server_split_with_indexes: 0.759s ok ! lib/bup/t/tclient.py test_multiple_suggestions: ... 0.894s ok ! lib/bup/t/tclient.py test_dumb_client_server: ... 0.493s ok ! lib/bup/t/tclient.py test_midx_refreshing: . 0.827s ok ! lib/bup/t/tclient.py test_remote_parsing: . 0.003s ok ! lib/bup/t/tgit.py testmangle: . 0.001s ok ! lib/bup/t/tgit.py testencode: .. 0.001s ok ! lib/bup/t/tgit.py testpacks: 0.533s ok ! lib/bup/t/tgit.py test_pack_name_lookup: . 1.868s ok ! lib/bup/t/tgit.py test_long_index: ... 0.001s ok ! lib/bup/t/tgit.py test_check_repo_or_die: ... 0.003s ok ! lib/bup/t/thashsplit.py test_rolling_sums: . 0.003s ok ! lib/bup/t/thelpers.py test_parse_num: .. 0.001s ok ! lib/bup/t/thelpers.py test_detect_fakeroot: . 0.000s ok ! lib/bup/t/thelpers.py test_path_components: . 0.000s ok ! lib/bup/t/thelpers.py test_stripped_path_components: .. 0.001s ok ! lib/bup/t/thelpers.py test_grafted_path_components: ... 0.016s ok ! lib/bup/t/tindex.py index_basic: . 0.001s ok ! lib/bup/t/tindex.py index_writer: 0.000s ok ! lib/bup/t/tindex.py index_negative_timestamps: .. 0.000s ok ! lib/bup/t/tindex.py index_dirty: . 0.014s ok ! lib/bup/t/tmetadata.py test_clean_up_archive_path: .
Processed: notfound 759930 in 0.25-1
Processing commands for cont...@bugs.debian.org:
notfound 759930 0.25-1
Bug #759930 {Done: Axel Beckert a...@debian.org} [src:bup] bup: FTBFS:
dh_auto_test: make -j1 test returned exit code 2
No longer marked as found in versions bup/0.25-1.
thanks
Stopping processing here.
Please contact me if you need assistance.
--
759930: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=759930
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): severity of 749730 is minor, tagging 754931, tagging 757875, tagging 735047, tagging 746157 ...
Processing commands for cont...@bugs.debian.org:
severity 749730 minor
Bug #749730 [nvidia-xconfig] nvidia-xconfig: xorg-server package reference
warning/error
Severity set to 'minor' from 'normal'
tags 754931 + pending
Bug #754931 [nvidia-support] nvidia-support: typos in swedish debconf
Added tag(s) pending.
tags 757875 + pending
Bug #757875 [nvidia-support] [INTL:tr] Turkish debconf template translation for
nvidia-support
Added tag(s) pending.
tags 735047 - moreinfo
Bug #735047 {Done: Andreas Beckmann a...@debian.org} [glx-alternative-fglrx]
fglrx-driver: openGL applications segfaults on igpu configuration
Removed tag(s) moreinfo.
tags 746157 + moreinfo
Bug #746157 [fglrx-legacy-driver] fglrx-legacy-driver: fglrx-legacy does not
install due to broken dependencies
Added tag(s) moreinfo.
severity 746157 important
Bug #746157 [fglrx-legacy-driver] fglrx-legacy-driver: fglrx-legacy does not
install due to broken dependencies
Severity set to 'important' from 'serious'
tags 684654 + upstream wontfix - moreinfo
Bug #684654 [fglrx-legacy-driver] [fglrx-legacy-driver] Xorg shows blank screen
with fglrx legacy driver
Bug #684655 [fglrx-legacy-driver] [fglrx-legacy-driver] Xorg shows blank screen
with fglrx legacy driver
Added tag(s) upstream and wontfix.
Added tag(s) upstream and wontfix.
Bug #684654 [fglrx-legacy-driver] [fglrx-legacy-driver] Xorg shows blank screen
with fglrx legacy driver
Bug #684655 [fglrx-legacy-driver] [fglrx-legacy-driver] Xorg shows blank screen
with fglrx legacy driver
Removed tag(s) moreinfo.
Removed tag(s) moreinfo.
found 684654 8.97.100.7-1
Bug #684654 [fglrx-legacy-driver] [fglrx-legacy-driver] Xorg shows blank screen
with fglrx legacy driver
Bug #684655 [fglrx-legacy-driver] [fglrx-legacy-driver] Xorg shows blank screen
with fglrx legacy driver
Marked as found in versions fglrx-legacy-driver/8.97.100.7-1.
Marked as found in versions fglrx-legacy-driver/8.97.100.7-1.
tags 708496 = wheezy
Bug #708496 [src:nana] nana: Please get rid of install-info call in maint-script
Added tag(s) wheezy; removed tag(s) sid and jessie.
tags 756824 + moreinfo
Bug #756824 [nvidia-driver] nvidia-driver: lost display the temperature of the
GPU
Added tag(s) moreinfo.
tags 731265 + pending
Bug #731265 [nvidia-glx] Optimus from Nvidia does not works
Added tag(s) pending.
tags 749018 + pending
Bug #749018 [bumblebee-nvidia] bumblebee-nvidia: nvidia uvm problem
Added tag(s) pending.
reassign 749018 nvidia-alternative
Bug #749018 [bumblebee-nvidia] bumblebee-nvidia: nvidia uvm problem
Bug reassigned from package 'bumblebee-nvidia' to 'nvidia-alternative'.
No longer marked as found in versions bumblebee/3.2.1-5.
Ignoring request to alter fixed versions of bug #749018 to the same values
previously set
affects 749018 + bumblebee-nvidia
Bug #749018 [nvidia-alternative] bumblebee-nvidia: nvidia uvm problem
Added indication that 749018 affects bumblebee-nvidia
merge 754108 749703
Bug #754108 [nvidia-kernel-source] nvidia-kernel-3.14-0.bpo.1-amd64: loading
module nvidia-current fails with Unknown symbol acpi_os_wait_events_complete
Unable to merge bugs because:
package of #749703 is 'nvidia-kernel-dkms' not 'nvidia-kernel-source'
Failed to merge 754108: Did not alter merged bugs
thanks
Stopping processing here.
Please contact me if you need assistance.
--
684654: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=684654
684655: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=684655
708496: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=708496
731265: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=731265
735047: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=735047
746157: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=746157
749018: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=749018
749703: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=749703
749730: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=749730
754108: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=754108
754931: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=754931
756824: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=756824
757875: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=757875
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#759910: marked as done (ruby-ogginfo: FTBFS: ERROR: Test ruby2.1 failed: Running tests for ruby2.1 with test file list from debian/ruby-test-files.yaml ...)
Your message dated Sun, 28 Sep 2014 01:19:44 + with message-id e1xy39m-0002im...@franck.debian.org and subject line Bug#759910: fixed in ruby-ogginfo 0.7.2-1 has caused the Debian Bug report #759910, regarding ruby-ogginfo: FTBFS: ERROR: Test ruby2.1 failed: Running tests for ruby2.1 with test file list from debian/ruby-test-files.yaml ... 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.) -- 759910: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=759910 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Source: ruby-ogginfo Version: 0.6.12-1 Severity: serious Tags: jessie sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20140830 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 ... Run options: # Running tests: Encoding standard input to /«PKGBUILDDIR»/test/test.ogg at quality 0.00 Encoding [ 0m00s so far] | Encoding [ 0m00s so far] / Encoding [ 0m00s so far] - Encoding [ 0m00s so far] \ Encoding [ 0m00s so far] | Encoding [ 0m00s so far] / Encoding [ 0m00s so far] - Encoding [ 0m00s so far] \ Encoding [ 0m00s so far] | Encoding [ 0m00s so far] / Encoding [ 0m00s so far] - Encoding [ 0m00s so far] \ Encoding [ 0m00s so far] | Encoding [ 0m00s so far] / Encoding [ 0m00s so far] - Encoding [ 0m00s so far] \ Encoding [ 0m00s so far] | Encoding [ 0m00s so far] / 3000+0 records in 3000+0 records out 3072000 bytes (3.1 MB) copied, 0.454548 s, 6.8 MB/s Done encoding file /«PKGBUILDDIR»/test/test.ogg File length: 0m 17.0s Elapsed time: 0m 00.5s Rate: 37.5366 Average bitrate: 67.4 kb/s Segmentation fault Warning: Speex is only optimized for 8, 16 and 32 kHz. It will still work at 44100 Hz but your mileage may vary Encoding 44100 Hz audio using ultra-wideband (sub-band CELP) mode (stereo) 3000+0 records in 3000+0 records out 3072000 bytes (3.1 MB) copied, 0.568604 s, 5.4 MB/s F.. Finished tests in 1.176247s, 9.3518 tests/s, 22.1042 assertions/s. 1) Failure: OggInfoTest#test_big_tags [/«PKGBUILDDIR»/test/test_ruby-ogginfo.rb:200]: cannot generate /«PKGBUILDDIR»/test/test.ogg, tests cannot be fully performed 11 tests, 26 assertions, 1 failures, 0 errors, 0 skips ruby -v: ruby 2.1.2p95 (2014-05-08) [x86_64-linux-gnu] ERROR: Test ruby2.1 failed: The full build log is available from: http://aws-logs.debian.net/ftbfs-logs/2014/08/30/ruby-ogginfo_0.6.12-1_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. The build was done with DEB_BUILD_OPTIONS=parallel=4, so if your packaging tries to support this, it might be a good idea to explore whether this might be the cause of the failure. ---End Message--- ---BeginMessage--- Source: ruby-ogginfo Source-Version: 0.7.2-1 We believe that the bug you reported is fixed in the latest version of ruby-ogginfo, 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 759...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. David Suárez david.sephi...@gmail.com (supplier of updated ruby-ogginfo 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: Wed, 24 Sep 2014 20:18:09 +0200 Source: ruby-ogginfo Binary: ruby-ogginfo Architecture: source all Version: 0.7.2-1 Distribution: unstable Urgency: low Maintainer: Debian Ruby Extras Maintainers pkg-ruby-extras-maintain...@lists.alioth.debian.org Changed-By: David Suárez david.sephi...@gmail.com Description: ruby-ogginfo - Ruby library for accessing low-level information on ogg
Bug#760719: marked as done (collectd: ftbfs on kfreebsd)
Your message dated Sun, 28 Sep 2014 01:18:45 + with message-id e1xy38p-0002b9...@franck.debian.org and subject line Bug#760719: fixed in collectd 5.4.1-4 has caused the Debian Bug report #760719, regarding collectd: ftbfs on 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.) -- 760719: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=760719 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- package: collectd version: 5.4.1-3.1 severity: serious Hi, The latest upload of collectd FTBFS on kfreebsd, blocking migration to testing: https://buildd.debian.org/status/package.php?p=collectdsuite=unstable Cheers, Ivo ---End Message--- ---BeginMessage--- Source: collectd Source-Version: 5.4.1-4 We believe that the bug you reported is fixed in the latest version of collectd, 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 760...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Sebastian Harl tok...@debian.org (supplier of updated collectd 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, 28 Sep 2014 01:59:14 +0200 Source: collectd Binary: collectd-core collectd collectd-utils collectd-dbg collectd-dev libcollectdclient-dev libcollectdclient1 Architecture: source amd64 all Version: 5.4.1-4 Distribution: unstable Urgency: medium Maintainer: Sebastian Harl tok...@debian.org Changed-By: Sebastian Harl tok...@debian.org Description: collectd - statistics collection and monitoring daemon collectd-core - statistics collection and monitoring daemon (core system) collectd-dbg - statistics collection and monitoring daemon (debugging symbols) collectd-dev - statistics collection and monitoring daemon (development files) collectd-utils - statistics collection and monitoring daemon (utilities) libcollectdclient-dev - client library for collectd's control interface (development file libcollectdclient1 - client library for collectd's control interface Closes: 760719 Changes: collectd (5.4.1-4) unstable; urgency=medium . * debian/rules: - Disable preprocessor warnings on kfreebsd to work around an error resulting from a redefined macro in PostgreSQL's pg_config_manual.h; thanks to Ivo De Decker for reporting this (Closes: #760719). * debian/control, debian/rules: - Disable the 'java' plugin on sparc for now. It fails to build. Checksums-Sha1: e99d43c2785ea74e97ab5f6fc791947ec5053db8 2741 collectd_5.4.1-4.dsc 82718515744d485507f17d8bf385c294a69c92bf 78231 collectd_5.4.1-4.diff.gz a819e762dcb38999209bd7b2a31e3e40b17943d5 774852 collectd-core_5.4.1-4_amd64.deb c94339d49323e9dd922c725c14b2c2b64b4d22cf 86226 collectd_5.4.1-4_amd64.deb 6a2d29d141419ec5b6b8cc32c33f03b56c6f995a 100600 collectd-utils_5.4.1-4_amd64.deb 84ad6dcf2f4657fcdef73b1476ea86d8688890bd 998324 collectd-dbg_5.4.1-4_amd64.deb c0ffc5c9cf09a25398c779db2cb2a48e7b8f2301 80294 libcollectdclient-dev_5.4.1-4_amd64.deb 73ad3db6451e04bf141c1b085720168526dae187 89690 libcollectdclient1_5.4.1-4_amd64.deb 7d628a81b81ccbecbdc4a74356b042caa3a77927 115578 collectd-dev_5.4.1-4_all.deb Checksums-Sha256: d657d1f6f0bf659e4520f428e1e8bfe22145720ef005d20f36aa0da4a5bb 2741 collectd_5.4.1-4.dsc 5a0670c32301eeed00ed6a3e43c1b047cd55536b3238df0ceb8662f093749778 78231 collectd_5.4.1-4.diff.gz 1f4ba3e50b1d418b3294e374efb1b35085c7c57a264daa830576f1c0ce8ea01a 774852 collectd-core_5.4.1-4_amd64.deb 98be2360b03a9a29bca35f2182dcf672c14df3ee2179abcac51c8d16c9abb41c 86226 collectd_5.4.1-4_amd64.deb f1fc6be900d2859315dcf0ea03d2f7f5095b0f1d1590c0a474cf52a09200d45e 100600 collectd-utils_5.4.1-4_amd64.deb 14f61e8df41d0adf633c0b04c18d9f35ffd3cba9f68108c4d104262551f4eb5d 998324 collectd-dbg_5.4.1-4_amd64.deb 29d28d3e494235bba942e7becaff042bbf88030d3b9c671422b227ce7e71bdb0 80294 libcollectdclient-dev_5.4.1-4_amd64.deb 63623cc2eb39ea05cab5e7eda56634d82976dd179debb4c8e4a063ed5728b6be 89690 libcollectdclient1_5.4.1-4_amd64.deb 065d963895a4f844f8408ea74844088eea95562e3093d1a5ed9ca82957eb2193 115578 collectd-dev_5.4.1-4_all.deb Files: 34bb8543b492a1d49ed7881075c0a502 774852 utils optional collectd-core_5.4.1-4_amd64.deb
