Bug#776899: unblock: linux/3.16.7-ckt4-2
Control: retitle -1 unblock: linux/3.16.7-ckt4-3 The -3 version additionally fixes some regressions for arm64 (#776957) and x86 in 3.16.7-ckt4, and a few older issues: - Remotely triggered memory corruption in sctp (CVE-2015-1421) - Regression in Xen memory hotplug starting with 3.13 (#776448) - FTBFS on sh4 (#775611) Ben. -- Ben Hutchings Hoare's Law of Large Problems: Inside every large problem is a small problem struggling to get out. signature.asc Description: This is a digitally signed message part
Bug#776964: Headers installed by zsh-dev packages miss critical pieces
04.02.2015, 01:58, Frank Terbeck f...@bewatermyfriend.org:
Hey there!
ZyX wrote:
[...]
To use zsh headers in some module at least `config.h` file is needed
Finally, someone who actually wants to use zsh's facilities to load
third party modules. Yay. ;)
in addition to those already present in the package. `config.h` files
contains defines guessed by ./configure script and including it prior
to `zsh.h` is the only sane variant to include `zsh.h` (insane variant
is using module’s own configure script which will create those
defines). Without `config.h` including `zsh.h` will fail due to
missing defines, and even if it was not failing it would make #include
zsh.h do the wrong thing because of the bits like
[...]
I agree.
(configure.h-driven definition of zlong and zulong which has the potential
of breaking ABI compatibility in some cases).
In addition to this file it is good to have a patched `zsh.mdh` file
which glues together all zsh includes and is a single entry point.
Patch needed to include this file in the distribution may be performed
with the following script:
for file in Src/{zsh.mdh,*.h} ; do
We'd probably want to do that in a POSIX compatible way, so we'd refrain
from using brace expansion but that's just cosmetics.
sed -i 's@\.\./config\.h@config.h@' $file
sed -i 's@#\(\s*\)include \([^]\+\)@#\1include
zsh/\2@' $file
Sed's -i option requires GNU sed. But then, I don't know if debian even
ships another version of sed. ...I think it doesn't; but I also don't
know about the policy with respect to non-POSIX features in packaging.
done
. I am doing this in a Gentoo ebuild and the result works just fine.
Yeah, I think this could work.
Do you think it would make sense to include the other header files with
zsh-dev as well? Like zshterm.h etc?
In my ebuild I am simply doins all *.h files from Src, passed throught these
filters, so zshterm.h gets caught as well. But I think that all of them are
#included by zsh.mdh, at least zshterm.h does (zsh.mdh includes zsh_system.h
and that includes zshterm.h). Did not know you do not do the same thing (I
mean, adding Src/*.h).
Regards, Frank
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#777024: gmediarender segfaults on startup on armel, raspbian and possiblly other architectures if gstreamer1.0-plugins-bad is installed.
package: gstreamer1.0-plugins-bad version: 1.4.3-2 severity: grave tags: patch We received a report in raspbian, that gmediarender was segfaulting on startup. Further investigation by the original reporter showed that it only happened if gstreamer1.0-plugins-bad was installed. https://bugs.launchpad.net/raspbian/+bug/1392850 The reporter took it to upstream who tracked the problem down to an incorrect call to a variadic function. https://bugzilla.gnome.org/show_bug.cgi?id=740191 http://cgit.freedesktop.org/gstreamer/gst-plugins-bad/commit/?id=3e1d7630187dd96b137553aec2c6edb60c213682 AIUI this has the potential to crash on most 32-bit architectures (on 64-bit architectures I belive alignment requirements will mask the problem), whether it actually crashes depends on what happens to be on the stack/in the registers at the time. My tests have shown that this does not appear to crash on debian armhf at the moment but it does appear to crash on debian armel. While working on this issue I also ran into an unrepresentable changes to source error caused by incomplete cleanup in your clean target. So I fixed that too. Debdiff attatched, no intent to nmu P.S. theres some noise in the debdiff, looks like your clean target needs further work. diff -Nru gst-plugins-bad1.0-1.4.4/debian/changelog gst-plugins-bad1.0-1.4.4/debian/changelog --- gst-plugins-bad1.0-1.4.4/debian/changelog 2014-11-11 12:40:17.0 + +++ gst-plugins-bad1.0-1.4.4/debian/changelog 2015-02-03 22:25:43.0 + @@ -1,3 +1,18 @@ +gst-plugins-bad1.0 (1.4.4-2+rpi2) jessie-staging; urgency=medium + + * Really apply the patch to fix gmediarender segfault. + * Remove win32/common/config.h-new in clean target to prevent +unrepresentable changes to source error when building a second time. + + -- Peter Michael Green plugw...@raspbian.org Tue, 03 Feb 2015 22:10:57 + + +gst-plugins-bad1.0 (1.4.4-2+rpi1) jessie-staging; urgency=medium + + * Apply upstream patch to fix gmediarendered segfault on startup +(LP: 1392850) + + -- Peter Michael Green plugw...@raspbian.org Fri, 26 Dec 2014 14:24:44 + + gst-plugins-bad1.0 (1.4.4-2) unstable; urgency=medium * Upload to unstable. diff -Nru gst-plugins-bad1.0-1.4.4/debian/libgstreamer-plugins-bad1.0-0.install gst-plugins-bad1.0-1.4.4/debian/libgstreamer-plugins-bad1.0-0.install --- gst-plugins-bad1.0-1.4.4/debian/libgstreamer-plugins-bad1.0-0.install 1970-01-01 00:00:00.0 + +++ gst-plugins-bad1.0-1.4.4/debian/libgstreamer-plugins-bad1.0-0.install 2014-12-26 15:22:08.0 + @@ -0,0 +1,10 @@ +debian/tmp/usr/lib/*/libgstphotography-1.0.so.* +debian/tmp/usr/lib/*/libgstbadbase-1.0.so.* +debian/tmp/usr/lib/*/libgstbadvideo-1.0.so.* +debian/tmp/usr/lib/*/libgstbasecamerabinsrc-1.0.so.* +debian/tmp/usr/lib/*/libgstgl-1.0.so.* +debian/tmp/usr/lib/*/libgstinsertbin-1.0.so.* +debian/tmp/usr/lib/*/libgstcodecparsers-1.0.so.* +debian/tmp/usr/lib/*/libgstmpegts-1.0.so.* +debian/tmp/usr/lib/*/libgsturidownloader-1.0.so.* +debian/tmp/usr/lib/arm-linux-gnueabihf/libgstwayland-1.0.so.* diff -Nru gst-plugins-bad1.0-1.4.4/debian/libgstreamer-plugins-bad1.0-dev.install gst-plugins-bad1.0-1.4.4/debian/libgstreamer-plugins-bad1.0-dev.install --- gst-plugins-bad1.0-1.4.4/debian/libgstreamer-plugins-bad1.0-dev.install 1970-01-01 00:00:00.0 + +++ gst-plugins-bad1.0-1.4.4/debian/libgstreamer-plugins-bad1.0-dev.install 2014-12-26 15:22:08.0 + @@ -0,0 +1,3 @@ +debian/tmp/usr/include +debian/tmp/usr/lib/*/pkgconfig +debian/tmp/usr/lib/*/*.so diff -Nru gst-plugins-bad1.0-1.4.4/debian/patches/fix-segfault-varargs.patch gst-plugins-bad1.0-1.4.4/debian/patches/fix-segfault-varargs.patch --- gst-plugins-bad1.0-1.4.4/debian/patches/fix-segfault-varargs.patch 1970-01-01 00:00:00.0 + +++ gst-plugins-bad1.0-1.4.4/debian/patches/fix-segfault-varargs.patch 2015-02-03 22:12:57.0 + @@ -0,0 +1,21 @@ +commit 3e1d7630187dd96b137553aec2c6edb60c213682 +Author: Tim-Philipp Müller t...@centricular.com +Date: Sat Nov 15 21:59:48 2014 + + +dvbbasebin: fix possible crash by passing 64 bits for 64-bit queue property + +https://bugzilla.gnome.org/show_bug.cgi?id=740191 + +Index: gst-plugins-bad1.0-1.4.4/sys/dvb/dvbbasebin.c +=== +--- gst-plugins-bad1.0-1.4.4.orig/sys/dvb/dvbbasebin.c gst-plugins-bad1.0-1.4.4/sys/dvb/dvbbasebin.c +@@ -417,7 +417,7 @@ dvb_base_bin_init (DvbBaseBin * dvbbaseb + dvbbasebin-tsparse = gst_element_factory_make (tsparse, NULL); + + g_object_set (dvbbasebin-buffer_queue, max-size-buffers, 0, +- max-size-bytes, 0, max-size-time, 0, NULL); ++ max-size-bytes, 0, max-size-time, (guint64) 0, NULL); + + gst_bin_add_many (GST_BIN (dvbbasebin), dvbbasebin-dvbsrc, + dvbbasebin-buffer_queue, dvbbasebin-tsparse, NULL); diff -Nru gst-plugins-bad1.0-1.4.4/debian/patches/series
Bug#777027: fpc: fp-compiler-2.6.0 prevents upgrade of binutils
Package: fpc
Version: 2.6.4+dfsg-4
Severity: serious
Tags: patch
User: debian...@lists.debian.org
Usertags: piuparts
Hi,
during a test with piuparts I noticed your package prevents binutils
from being upgraded automatically.
It installed fine in 'wheezy', but during the upgrade to 'jessie'
apt prefers to keep the obsolete fp-compiler-2.6.0 installed and
holds back the wheezy version of binutils.
fp-compiler-2.6.0 has Breaks: binutils-gold, but in jessie binutils-gold
is a virtual package provided by binutils. fp-compiler-2.6.4 no longer
cares about binutils-gold.
From the attached log (scroll to the bottom...):
20 fp-units-rtl-2.6.0 [ amd64 ] 2.6.0-9 ( devel )
20 fp-units-rtl-2.6.4 [ amd64 ] none - 2.6.4+dfsg-4 ( devel )
15 fp-compiler-2.6.0 [ amd64 ] 2.6.0-9 ( devel )
15 fp-compiler-2.6.4 [ amd64 ] none - 2.6.4+dfsg-4 ( devel )
4 binutils [ amd64 ] 2.22-8 - 2.24.90.20141023-1 ( devel )
-1 fpc-2.6.0 [ amd64 ] 2.6.0-9 ( devel )
Starting 2
Investigating (0) fp-compiler-2.6.0 [ amd64 ] 2.6.0-9 ( devel )
Broken fp-compiler-2.6.0:amd64 Conflicts on binutils-gold [ amd64 ] none
( none )
Considering binutils:amd64 4 as a solution to fp-compiler-2.6.0:amd64 15
Added binutils:amd64 to the remove list
Fixing fp-compiler-2.6.0:amd64 via keep of binutils:amd64
Try to Re-Instate (0) binutils:amd64
Done
The following NEW packages will be installed:
[...]
The following packages have been kept back:
binutils
The following packages will be upgraded:
[...]
239 upgraded, 108 newly installed, 0 to remove and 1 not upgraded.
Adding the Breaks to fp-units-rtl-2.6.4 is sufficient since it has
a higher score than fp-compiler-2.6.0 (20 vs. 15).
In all my piuparts upgrade tests with the changes from the attached
patch binutils was always upgraded.
cheers,
Andreas
diff -Nru fpc-2.6.4+dfsg/debian/changelog fpc-2.6.4+dfsg/debian/changelog
--- fpc-2.6.4+dfsg/debian/changelog 2014-10-13 21:19:22.0 +0200
+++ fpc-2.6.4+dfsg/debian/changelog 2015-02-04 05:35:57.0 +0100
@@ -1,3 +1,10 @@
+fpc (2.6.4+dfsg-5) UNRELEASED; urgency=medium
+
+ * fp-units-rtl-2.6.4: Add Breaks: fp-compiler-2.6.0 which otherwise would
+prevent upgrading binutils. (Closes: #xx)
+
+ -- Andreas Beckmann a...@debian.org Wed, 04 Feb 2015 05:35:25 +0100
+
fpc (2.6.4+dfsg-4) unstable; urgency=low
* Let Select manually be translatable in debconf questions and update
diff -Nru fpc-2.6.4+dfsg/debian/control fpc-2.6.4+dfsg/debian/control
--- fpc-2.6.4+dfsg/debian/control 2014-09-27 19:36:19.0 +0200
+++ fpc-2.6.4+dfsg/debian/control 2015-01-29 04:44:28.0 +0100
@@ -149,7 +149,7 @@
Depends: ${misc:Depends}
Recommends: fp-compiler-2.6.4 (= ${binary:Version})
Provides: fp-units-rtl, fpc-abi-2.6.4
-Breaks: fp-units-rtl (= 2.4.0-3)
+Breaks: fp-units-rtl (= 2.4.0-3), fp-compiler-2.6.0
Replaces: fp-units-rtl (= 2.4.0-3)
Description: Free Pascal - runtime libraries
The Free Pascal Compiler is an Object Pascal compiler supporting both Delphi
diff -Nru fpc-2.6.4+dfsg/debian/control.in fpc-2.6.4+dfsg/debian/control.in
--- fpc-2.6.4+dfsg/debian/control.in 2014-09-27 19:36:01.0 +0200
+++ fpc-2.6.4+dfsg/debian/control.in 2015-01-29 04:44:20.0 +0100
@@ -149,7 +149,7 @@
Depends: ${misc:Depends}
Recommends: fp-compiler${PACKAGESUFFIX} (= ${binary:Version})
Provides: fp-units-rtl, fpc-abi${PACKAGESUFFIX}
-Breaks: fp-units-rtl (= 2.4.0-3)
+Breaks: fp-units-rtl (= 2.4.0-3), fp-compiler-2.6.0
Replaces: fp-units-rtl (= 2.4.0-3)
Description: Free Pascal - runtime libraries
The Free Pascal Compiler is an Object Pascal compiler supporting both Delphi
fpc_2.6.4+dfsg-4.log.gz
Description: application/gzip
Bug#776948: [Pkg-postgresql-public] Bug#776948: RM: pgtune -- ROM; upstream dead, and bad advise to be used today
On Wednesday, February 04, 2015 12:33:02 Stuart Bishop wrote: On 3 February 2015 at 21:01, Christoph Berg christoph.b...@credativ.de wrote: Package: ftp.debian.org Severity: normal Hi, pgtune hasn't seen a new upstream release since about the medieval ages, and the last git commit isn't very current either. The postgresql.conf it produces is worse than the defaults in some aspects, so people are rather harmed than helped by this tool. Let's get rid of it, in unstable and jessie. It doesn't have any rdeps. Please remove pgtune. I'm still using it to set 'best practice' defaults based on hardware specs. Yes, some of the recommendations are bogus and none of the maintainers interested in fixing it. However it does give me a starting point which I can then fix (capping shared_buffers to 8GB is the critical one). Without pgtune, I'd need to rewrite pgtune rather than my current approach of fixing its failures. Are you willing to take over maintenance? If it's dead upstream and unmaintained in Debian (the removal bug equates to the current maintainer declining to further maintain it and stating removal is better than it being unmaintained in Debian) then it should be removed. If so, you've got about 10 days to get it fixed in Testing or it'll be removed. If not, then it should go and you can keep your own local package for your purposes. Scott K FTP Assistant signature.asc Description: This is a digitally signed message part.
Bug#774794: Debian Bug#774794: Re: dpkg: Add breaks for new trigger cycles
[ CCing gconf maintainers. ] Hi! On Tue, 2015-02-03 at 10:19:29 +0100, Andreas Beckmann wrote: On 2015-02-03 07:12, Niels Thykier wrote: That said, I have no status on the cycles mentioned by Andreas Beckmann (CC'ed) in this bug report. If they are still relevant, we should have bugs for them. I can still reproduce these problems, not sure which package to be blamed for and whether its trigger cycles or something different. The debian-security-support and doc-base instances are just missing Breaks in dpkg, which I've added. The only remaining problem is the gconf2 one, which from a cursory check looks suspiciously like the dbus problem. (Sorry for not having checked that one before, it looked like something else, because it's not really a trigger cycle.) Andreas, if you have such system readily available, it would be nice to know if apt-get can get out of that state or if it gets stuck there. And to the gconf maintainers, does its trigger really need to be synchronous (i.e. do trigggering packages need to await the trigger processing)? Or in other words do those other triggering packages require the trigger to be processed to be able to consider themselves configured and able to satisfy dependencies? Thanks, Guillem -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#777028: libxml2: #include unicode/ucnv.h not found (unicode/ucnv.h)
Source: libxml2 Version: 2.9.2+dfsg1-3 Severity: serious Control: affects -1 kde4libs Hi, The kde4libs package FTBFS with the following error on mipsel[1]: make -f kjs/CMakeFiles/kjs.dir/build.make kjs/CMakeFiles/kjs.dir/build In file included from /usr/include/libxml2/libxml/parser.h:810:0, from ../../kdoctools/xslt.h:4, from ../../kdoctools/meinproc_simple.cpp:4: /usr/include/libxml2/libxml/encoding.h:31:26: fatal error: unicode/ucnv.h: No such file or directory #include unicode/ucnv.h ^ compilation terminated. This seems to becaused by a libxml2 header requiring a header that does not exist *OR* (more likely) it did not have a dependency for. This issue is currently blocking an RC bug in kde4libs from migrating to testing. Even if the patched version of libxml2 is not targeted for jessie, please consider prioritising this fix. Thanks, ~Niels [1] https://buildd.debian.org/status/fetch.php?pkg=kde4libsarch=mipselver=4%3A4.14.2-5stamp=1422755284 -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#755722: systemd must sync systemclock to RTC on shutdown
On Wednesday 04 February 2015 01:41:14, Michael Biebl wrote: Am 31.01.2015 um 10:19 schrieb Stefan Fritsch: severity 755722 serious retitle 755722 systemd must sync systemclock to RTC on shutdown thanks Systemd must make sure that the system clock does not go backwards, which causes all kinds of problems, with file systems and with other software. To achieve that, systemd has to sync the system time to RTC on shutdown. Upstream's argument that the system time may not be more accurate is completely unrelated to this issue. Upstream argues, that whoever changes the clock, should also make sure to sync that to the RTC if so desired. E.g. if you change the time using the builtin timedatectl command, it will make sure the RTC is synced. There is also natural drift between the system clock and the RTC. Who is supposed to account for that? On a system with an uptime of several months, the drift may be large enough to cause the time to go backwards at a reboot. NB: Upstream should try not to break existing software. The sysv init script compatibility is mostly moot if the init scripts need to be adjusted because of semantic changes. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#777027: fpc: fp-compiler-2.6.0 prevents upgrade of binutils
On 04/02/15 05:05, Andreas Beckmann wrote: Package: fpc Version: 2.6.4+dfsg-4 Severity: serious Please provide a justification for the severity. Adding the Breaks to fp-units-rtl-2.6.4 is sufficient It's also wrong. The conflict between the freepascal 2.6.0 packages in Debian wheezy and the binutils in Debian jessie has nothing to do with freepascal 2.6.4. I am strongly opposed to adding wrong information to package control fields simply because apt chooses to hold back a package without it. I'm not at all convinced this needs fixing but if it really does need fixing i'd much rather see it fixed by a stable update to make the freepascal 2.6.0 packages in wheezy compatible with jessie's binutils. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#777005: R: Bug#777005: boinc-client: memory and priority idea
Hi Alessando, can you please forward this on boinc-dev mail list? thanks Gianfranco -- Il mer 4 feb 2015 00:44 CET, Alessandro Barbieri ha scritto: Package: boinc-client Version: 7.4.23+dfsg-1 Severity: wishlist Tags: upstream Dear Maintainer, when a WU is waiting for memory can the manager run a lower priority WU (that uses less memory) instead of waiting and not using all cores? -- Package-specific info: -- Contents of /etc/default/boinc-client: # This file is /etc/default/boinc-client, it is a configuration file for the # /etc/init.d/boinc-client init script. # Set this to 1 to enable and to 0 to disable the init script. ENABLED=1 # Set this to 1 to enable advanced scheduling of the BOINC core client and # all its sub-processes (reduces the impact of BOINC on the system's # performance). SCHEDULE=1 # The BOINC core client will be started with the permissions of this user. BOINC_USER=boinc # This is the data directory of the BOINC core client. BOINC_DIR=/var/lib/boinc-client # This is the location of the BOINC core client, that the init script uses. # If you do not want to use the client program provided by the boinc-client # package, you can specify here an alternative client program. #BOINC_CLIENT=/usr/local/bin/boinc BOINC_CLIENT=/usr/bin/boinc # Here you can specify additional options to pass to the BOINC core client. # Type 'boinc --help' or 'man boinc' for a full summary of allowed options. #BOINC_OPTS=--allow_remote_gui_rpc BOINC_OPTS= # Scheduling options # Set SCHEDULE=0 if prefering to run with upstream default priority # settings. # Nice levels. When systems are truly busy, e.g. because of too many active # scientific applications started by the boinc client, there is a chance for # the boinc client not to be granted sufficient opportunity to check for # scientific applications to be alive and make the (wrong) decision to # terminate the scientific app. This is particularly an issue with many # apps started in parallel on modern multi-core systems and extra overheads # for the download and uploads of files with the project servers. Another # concern is the latency for scientific applications to communicate with the # graphics card, which should be low. All such values should be set and # controled from within the BOINC client. The Debian init script also sets # extra constrains via chrt on real time performance and via ionice on # I/O performance, which is beyond the regular BOINC client. It then was # too easy to use that code to also constrain minimal nice levels. We still # think about how to best distinguish GPU applications from regular apps. BOINC_NICE_CLIENT=10 BOINC_NICE_APP_DEFAULT=19 #BOINC_NICE_APP_GPU=5# not yet used # ionice classes. See manpage of ionice (1) in the util-linux package. BOINC_IONICE_CLIENT=3# idle #BOINC_IONICE_APP_DEFAULT=3 # idle, not yet used #BOINC_IONICE_APP_GPU=2 # best effort, not yet used -- System Information: Debian Release: 8.0 APT prefers testing APT policy: (650, 'testing'), (500, 'testing-updates'), (500, 'testing-proposed-updates'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.16.0-4-amd64 (SMP w/4 CPU cores) Locale: LANG=it_IT.UTF-8, LC_CTYPE=it_IT.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages boinc-client depends on: ii adduser3.113+nmu3 ii ca-certificates20141019 ii debconf [debconf-2.0] 1.5.55 ii libboinc7 7.4.23+dfsg-1 ii libc6 2.19-13 ii libcurl3 7.38.0-4 ii libgcc11:4.9.1-19 ii libstdc++6 4.9.1-19 ii python 2.7.8-2 ii zlib1g 1:1.2.8.dfsg-2+b1 boinc-client recommends no packages. Versions of packages boinc-client suggests: pn boinc-amd-opencl none ii boinc-manager 7.4.23+dfsg-2exp1 ii boinc-nvidia-cuda 7.4.23+dfsg-2exp1 ii x11-xserver-utils 7.7+3+b1 -- Configuration Files: /etc/boinc-client/cc_config.xml changed: cc_config log_flags file_xfer1/file_xfer sched_ops1/sched_ops task1/task android_debug0/android_debug app_msg_receive0/app_msg_receive app_msg_send0/app_msg_send async_file_debug0/async_file_debug benchmark_debug0/benchmark_debug checkpoint_debug0/checkpoint_debug coproc_debug0/coproc_debug cpu_sched0/cpu_sched cpu_sched_debug0/cpu_sched_debug cpu_sched_status0/cpu_sched_status dcf_debug0/dcf_debug disk_usage_debug0/disk_usage_debug file_xfer_debug0/file_xfer_debug gui_rpc_debug0/gui_rpc_debug heartbeat_debug0/heartbeat_debug http_debug0/http_debug http_xfer_debug0/http_xfer_debug mem_usage_debug0/mem_usage_debug network_status_debug0/network_status_debug notice_debug0/notice_debug
Bug#777026: openscenegraph: fails to upgrade from 'wheezy': apt prefers to hold the old package version
Package: openscenegraph
Version: 3.2.1-5
Severity: serious
Tags: patch
User: debian...@lists.debian.org
Usertags: piuparts
Hi,
during a test with piuparts I noticed your package fails to upgrade from
'wheezy'.
It installed fine in 'wheezy', then the upgrade to 'jessie' fails
because apt prefers to keep the old version instead of upgrading it.
From the attached log (scroll to the bottom...):
Starting 2
Investigating (0) libgdal1h [ amd64 ] none - 1.10.1+dfsg-8+b3 ( libs )
Broken libgdal1h:amd64 Breaks on libgdal1 [ amd64 ] 1.9.0-3.1 ( libs )
(= 1.10.0-0~)
Considering libgdal1:amd64 -1 as a solution to libgdal1h:amd64 -1
Holding Back libgdal1h:amd64 rather than change libgdal1:amd64
Investigating (1) libopenscenegraph100 [ amd64 ] none - 3.2.1-5 ( libs )
Broken libopenscenegraph100:amd64 Depends on libgdal1h [ amd64 ] none -
1.10.1+dfsg-8+b3 ( libs ) (= 1.8.0)
Considering libgdal1h:amd64 -1 as a solution to libopenscenegraph100:amd64 0
Holding Back libopenscenegraph100:amd64 rather than change libgdal1h:amd64
Investigating (2) openscenegraph [ amd64 ] 3.0.1-4 - 3.2.1-5 ( devel )
Broken openscenegraph:amd64 Depends on libopenscenegraph100 [ amd64 ] none
- 3.2.1-5 ( libs )
Considering libopenscenegraph100:amd64 0 as a solution to
openscenegraph:amd64 0
Holding Back openscenegraph:amd64 rather than change
libopenscenegraph100:amd64
Try to Re-Instate (3) openscenegraph:amd64
Done
The following NEW packages will be installed:
[...]
The following packages have been kept back:
openscenegraph
The following packages will be upgraded:
[...]
212 upgraded, 107 newly installed, 0 to remove and 1 not upgraded.
So we need to push apt a little bit to prefer libgdal1h over libgdal1,
this can be done by adding a Breaks: libgdal1 to libopenscenegraph100.
Patch attached, upgrade path verified in piuparts.
The similar problem exists in libopenscenegraph-dev, this will be fixed
by the patch, too.
cheers,
Andreas
diff -Nru openscenegraph-3.2.1/debian/changelog openscenegraph-3.2.1/debian/changelog
--- openscenegraph-3.2.1/debian/changelog 2014-10-31 12:14:46.0 +0100
+++ openscenegraph-3.2.1/debian/changelog 2015-01-28 23:33:12.0 +0100
@@ -1,3 +1,11 @@
+openscenegraph (3.2.1-6) UNRELEASED; urgency=medium
+
+ * libopenscenegraph100: Add Breaks: libgdal1 for smooth upgrades from
+wheezy. A little incentive that helps apt to take the right decision
+between libgdal1 and libgdal1h. (Closes: #xx)
+
+ -- Andreas Beckmann a...@debian.org Wed, 28 Jan 2015 17:45:57 +0100
+
openscenegraph (3.2.1-5) unstable; urgency=medium
* Update fix for correctly loading plugins on platforms other than amd64.
diff -Nru openscenegraph-3.2.1/debian/control openscenegraph-3.2.1/debian/control
--- openscenegraph-3.2.1/debian/control 2014-10-31 11:32:05.0 +0100
+++ openscenegraph-3.2.1/debian/control 2015-01-28 23:30:25.0 +0100
@@ -87,6 +87,7 @@
Multi-Arch: same
Depends: ${misc:Depends},
${shlibs:Depends}
+Breaks: libgdal1
Description: 3D scene graph, shared libs
A portable, high level graphics toolkit for the development of high performance
graphics applications such as flight simulators, games, virtual reality or
Bug#776991: [Pkg-openldap-devel] Bug#776991: slapd: crash in valueReturnFilter cleanup
Control: tags -1 + fixed-upstream
This is fixed upstream in git master now.
http://www.openldap.org/devel/gitweb.cgi?p=openldap.git;a=commitdiff;h=2f1a2dd329b91afe561cd06b872d09630d4edb6a
Test case: ldapsearch -E 'mv=(cn={*)(sn=*)'
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#761487: okular: PDF prints are stretched and misplaced
Package: okular Version: 4:4.14.2-2 Followup-For: Bug #761487 Dear Maintainer, *** Reporter, please consider answering these questions, where appropriate *** Printing this PDF file with Okular to an HP Officeject Pro 8000 a809 results in the bottom third of the pages being blank. http://www.achievemore.com.au/pdf/PO_statement_of_health_2013.pdf when run from the command line, Okular showed: okular(8073)/kdecore (KConfigSkeleton) KCoreConfigSkeleton::writeConfig: okular(8073)/kdecore (KConfigSkeleton) KCoreConfigSkeleton::writeConfig: okular(8073)/kdecore (KConfigSkeleton) KCoreConfigSkeleton::writeConfig: okular(8073)/kdecore (KConfigSkeleton) KCoreConfigSkeleton::writeConfig: okular(8073)/kdecore (KConfigSkeleton) KCoreConfigSkeleton::writeConfig: okular(8073) BackendLoader::init: /usr/lib/x86_64-linux-gnu/kde4/plugins This backend is only for XRandR 1.1, your version is: 1 . 4 okular(8073) KMimeTypePrivate::ensureXmlDataLoaded: Missing comment field in application/gnuradio-grc.xml QPrinter::setPaperSize: Illegal paper size 30 I will probably install Evince to get around this issue. *** End of the template - remove these template lines *** -- System Information: Debian Release: 8.0 APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing'), (500, 'stable'), (500, 'oldstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 3.19.0-rc7+ (SMP w/4 CPU cores; PREEMPT) Locale: LANG=en_AU.UTF-8, LC_CTYPE=en_AU.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Init: sysvinit (via /sbin/init) Versions of packages okular depends on: ii kde-runtime 4:4.14.2-2 ii libc6 2.19-14 ii libfreetype62.5.2-2 ii libjpeg62-turbo 1:1.3.1-11 ii libkactivities6 4:4.13.3-1 ii libkdecore5 4:4.14.2-5 ii libkdeui5 4:4.14.2-5 ii libkexiv2-114:4.14.2-1 ii libkio5 4:4.14.2-5 ii libkparts4 4:4.14.2-5 ii libkprintutils4 4:4.14.2-5 ii libkpty44:4.14.2-5 ii libokularcore5 4:4.14.2-2 ii libphonon4 4:4.8.0-4 ii libpoppler-qt4-40.26.5-2 ii libqca2 2.0.3-6 ii libqimageblitz4 1:0.0.6-4 ii libqmobipocket1 4:4.14.2-1 ii libqt4-dbus 4:4.8.6+git64-g5dc8b2b+dfsg-2+b1 ii libqt4-declarative 4:4.8.6+git64-g5dc8b2b+dfsg-2+b1 ii libqt4-svg 4:4.8.6+git64-g5dc8b2b+dfsg-2+b1 ii libqt4-xml 4:4.8.6+git64-g5dc8b2b+dfsg-2+b1 ii libqtcore4 4:4.8.6+git64-g5dc8b2b+dfsg-2+b1 ii libqtgui4 4:4.8.6+git64-g5dc8b2b+dfsg-2+b1 ii libsolid4 4:4.14.2-5 ii libspectre1 0.2.7-3 ii libstdc++6 5-20150121-1 ii phonon 4:4.8.0-4 ii zlib1g 1:1.2.8.dfsg-2+b1 okular recommends no packages. Versions of packages okular suggests: ii ghostscript9.06~dfsg-2 ii jovie 4:4.14.2-1 ii okular-extra-backends 4:4.14.2-2 ii poppler-data 0.4.7-1 ii texlive-binaries 2014.20140926.35254-6 ii unrar 1:5.2.5-1 -- debconf-show failed -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#776948: [Pkg-postgresql-public] Bug#776948: RM: pgtune -- ROM; upstream dead, and bad advise to be used today
On 3 February 2015 at 21:01, Christoph Berg christoph.b...@credativ.de wrote: Package: ftp.debian.org Severity: normal Hi, pgtune hasn't seen a new upstream release since about the medieval ages, and the last git commit isn't very current either. The postgresql.conf it produces is worse than the defaults in some aspects, so people are rather harmed than helped by this tool. Let's get rid of it, in unstable and jessie. It doesn't have any rdeps. Please remove pgtune. I'm still using it to set 'best practice' defaults based on hardware specs. Yes, some of the recommendations are bogus and none of the maintainers interested in fixing it. However it does give me a starting point which I can then fix (capping shared_buffers to 8GB is the critical one). Without pgtune, I'd need to rewrite pgtune rather than my current approach of fixing its failures. -- Stuart Bishop stuart.bis...@canonical.com -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#769362: telepathy not capitalized in extended description
Hello, What do you think about this re-written description? Description: Shared data for all the KDE Telepathy components This package contains KDE Telepathy shared data. . These various data files are used by nearly all the different KDE Telepathy components, and include files such as icons and translations. I think I was confused reading the Debian policy suggestion that the synopsis line should not repeat the package name and thought that applied to the extended description as well. Diane -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#623271: Adoption of slides
retitle 623271 ITA: slides -- Python-based Slide Maker owner 623271 ! thanks On 04/02/15 16:15, Paul Wise wrote: On Wed, Feb 4, 2015 at 1:10 PM, Riley Baird wrote: Okay, thanks. I had assumed that there was some form of special process for orphaned packages. Nothing special for the sponsorship side of things no. Rest of the adopting stuff is documented here: https://www.debian.org/doc/manuals/developers-reference/pkgs.html#adopting https://www.debian.org/devel/wnpp/#l3 Great! I've changed the bug to an ITA and created a git repo for the Debian packaging: https://gitorious.org/slides_debian/slides_debian -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#777029: libapache2-mod-authn-yubikey: Typo in description
Package: libapache2-mod-authn-yubikey Version: 1.0-1.1 Severity: minor The package description contains a typo: technlogy - technology -- System Information: Debian Release: 8.0 APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 3.13-1-amd64 (SMP w/1 CPU core) Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: sysvinit (via /sbin/init) Versions of packages libapache2-mod-authn-yubikey depends on: ii apache2-bin [apache2-api-20120211] 2.4.10-9 ii libc6 2.19-14 ii libcurl37.38.0-4 libapache2-mod-authn-yubikey recommends no packages. libapache2-mod-authn-yubikey suggests no packages. -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#773764: network-manager-strongswan: bug in config file means strongswan unrecognised
Using Strongswan on Wheezy I created an common IPsec gateway for all kinds of road warrior setups in our company: Linux, Windows, MacOS, iphones and Android phones. It is surely not perfect (yet), but it works well. And now the Debian Laptops cannot be migrated to Jessie due to missing IPsec support in Jessie's network manager. This is embarrassing. Harri -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#675345: gnome-shell: Same bug with version 3.14.2-3+b1.
Package: gnome-shell Version: 3.14.2-3+b1 Followup-For: Bug #675345 Dear Maintainer, I have this same bug with 3.14.2-3+b1 version. I am not sure if this is the same bug, but It has the same symptoms. I have noticed that gnome-shell freezes randomly when my android phone is mounted using mtp libraries. When it is freezed, if a unplug the mobile it start working again. Thanks Packages involved: $ dpkg -l |grep mtp [8:29:01] ii libmtp-common 1.1.8-1 all Media Transfer Protocol (MTP) common files ii libmtp-runtime1.1.8-1+b1 amd64Media Transfer Protocol (MTP) runtime tools ii libmtp9:amd64 1.1.8-1+b1 amd64Media Transfer Protocol (MTP) library -- System Information: Debian Release: 8.0 APT prefers testing-updates APT policy: (500, 'testing-updates'), (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 3.16.0-4-amd64 (SMP w/4 CPU cores) Locale: LANG=eu_ES.UTF-8, LC_CTYPE=eu_ES.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages gnome-shell depends on: ii dconf-gsettings-backend [gsettings-backend] 0.22.0-1 ii evolution-data-server3.12.9~git20141128.5242b0-2+b1 ii gir1.2-accountsservice-1.0 0.6.37-3+b1 ii gir1.2-atspi-2.0 2.14.0-1 ii gir1.2-caribou-1.0 0.4.15-1 ii gir1.2-clutter-1.0 1.20.0-1 ii gir1.2-freedesktop 1.42.0-2.2 ii gir1.2-gcr-3 3.14.0-2 ii gir1.2-gdesktopenums-3.0 3.14.1-1 ii gir1.2-gdm3 3.14.1-3 ii gir1.2-gkbd-3.0 3.6.0-1 ii gir1.2-glib-2.0 1.42.0-2.2 ii gir1.2-gnomebluetooth-1.03.14.0-2 ii gir1.2-gnomedesktop-3.0 3.14.1-1 ii gir1.2-gtk-3.0 3.14.5-1 ii gir1.2-ibus-1.0 1.5.9-1 ii gir1.2-mutter-3.03.14.2-1 ii gir1.2-networkmanager-1.00.9.10.0-5 ii gir1.2-nmgtk-1.0 0.9.10.0-2 ii gir1.2-pango-1.0 1.36.8-3 ii gir1.2-polkit-1.00.105-8 ii gir1.2-soup-2.4 2.48.0-1 ii gir1.2-telepathyglib-0.120.24.1-1 ii gir1.2-telepathylogger-0.2 0.8.1-1 ii gir1.2-upowerglib-1.00.99.1-3.1 ii gjs 1.42.0-1 ii gnome-backgrounds3.14.1-1 ii gnome-icon-theme-symbolic3.12.0-1 ii gnome-settings-daemon3.14.2-2 ii gnome-shell-common 3.14.2-3 ii gnome-themes-standard3.14.2.2-1 ii gsettings-desktop-schemas3.14.1-1 ii libatk-bridge2.0-0 2.14.0-2 ii libatk1.0-0 2.14.0-1 ii libc62.19-13 ii libcairo21.14.0-2.1 ii libcanberra-gtk3-0 0.30-2.1 ii libcanberra0 0.30-2.1 ii libclutter-1.0-0 1.20.0-1 ii libcogl-pango20 1.18.2-3 ii libcogl201.18.2-3 ii libcroco30.6.8-3+b1 ii libdbus-glib-1-2 0.102-1 ii libecal-1.2-16 3.12.9~git20141128.5242b0-2+b1 ii libedataserver-1.2-183.12.9~git20141128.5242b0-2+b1 ii libgcr-base-3-1 3.14.0-2 ii libgdk-pixbuf2.0-0 2.31.1-2+b1 ii libgirepository-1.0-11.42.0-2.2 ii libgjs0e [libgjs0-libmozjs-24-0] 1.42.0-1 ii libglib2.0-0 2.42.1-1 ii libgstreamer1.0-01.4.4-2 ii libgtk-3-0 3.14.5-1 ii libical1a1.0-1.3 ii libjson-glib-1.0-0 1.0.2-1 ii libmozjs-24-024.2.0-2 ii libmutter0e 3.14.2-1 ii libnm-glib4 0.9.10.0-5 ii libnm-util2 0.9.10.0-5 ii libpango-1.0-0 1.36.8-3 ii libpangocairo-1.0-0 1.36.8-3 ii libpolkit-agent-1-0 0.105-8 ii libpolkit-gobject-1-0
Bug#777030: audacity: crashes on startup (debug info included)
Package: audacity Version: 2.0.6-2 Hello, I would like to report the following startup issue, on the multi-card system that I'm having here: $ audacity (Audacity:27901): Gtk-WARNING **: gtk_disable_setlocale() must be called before gtk_init() ALSA lib confmisc.c:1286:(snd_func_refer) Unable to find definition 'cards.ALS4000.pcm.front.0:CARD=0' ALSA lib conf.c:4259:(_snd_config_evaluate) function snd_func_refer returned error: Datei oder Verzeichnis nicht gefunden ALSA lib conf.c:4738:(snd_config_expand) Evaluate error: Datei oder Verzeichnis nicht gefunden ALSA lib pcm.c:2239:(snd_pcm_open_noupdate) Unknown PCM front ALSA lib pcm.c:2239:(snd_pcm_open_noupdate) Unknown PCM cards.pcm.rear ALSA lib pcm.c:2239:(snd_pcm_open_noupdate) Unknown PCM cards.pcm.center_lfe ALSA lib pcm.c:2239:(snd_pcm_open_noupdate) Unknown PCM cards.pcm.side ALSA lib confmisc.c:1286:(snd_func_refer) Unable to find definition 'cards.ALS4000.pcm.surround51.0:CARD=0' ALSA lib conf.c:4259:(_snd_config_evaluate) function snd_func_refer returned error: Datei oder Verzeichnis nicht gefunden ALSA lib conf.c:4738:(snd_config_expand) Evaluate error: Datei oder Verzeichnis nicht gefunden ALSA lib pcm.c:2239:(snd_pcm_open_noupdate) Unknown PCM surround21 ALSA lib confmisc.c:1286:(snd_func_refer) Unable to find definition 'cards.ALS4000.pcm.surround51.0:CARD=0' ALSA lib conf.c:4259:(_snd_config_evaluate) function snd_func_refer returned error: Datei oder Verzeichnis nicht gefunden ALSA lib conf.c:4738:(snd_config_expand) Evaluate error: Datei oder Verzeichnis nicht gefunden ALSA lib pcm.c:2239:(snd_pcm_open_noupdate) Unknown PCM surround21 ALSA lib confmisc.c:1286:(snd_func_refer) Unable to find definition 'cards.ALS4000.pcm.surround40.0:CARD=0' ALSA lib conf.c:4259:(_snd_config_evaluate) function snd_func_refer returned error: Datei oder Verzeichnis nicht gefunden ALSA lib conf.c:4738:(snd_config_expand) Evaluate error: Datei oder Verzeichnis nicht gefunden ALSA lib pcm.c:2239:(snd_pcm_open_noupdate) Unknown PCM surround40 ALSA lib confmisc.c:1286:(snd_func_refer) Unable to find definition 'cards.ALS4000.pcm.surround51.0:CARD=0' ALSA lib conf.c:4259:(_snd_config_evaluate) function snd_func_refer returned error: Datei oder Verzeichnis nicht gefunden ALSA lib conf.c:4738:(snd_config_expand) Evaluate error: Datei oder Verzeichnis nicht gefunden ALSA lib pcm.c:2239:(snd_pcm_open_noupdate) Unknown PCM surround41 ALSA lib confmisc.c:1286:(snd_func_refer) Unable to find definition 'cards.ALS4000.pcm.surround51.0:CARD=0' ALSA lib conf.c:4259:(_snd_config_evaluate) function snd_func_refer returned error: Datei oder Verzeichnis nicht gefunden ALSA lib conf.c:4738:(snd_config_expand) Evaluate error: Datei oder Verzeichnis nicht gefunden ALSA lib pcm.c:2239:(snd_pcm_open_noupdate) Unknown PCM surround50 ALSA lib confmisc.c:1286:(snd_func_refer) Unable to find definition 'cards.ALS4000.pcm.surround51.0:CARD=0' ALSA lib conf.c:4259:(_snd_config_evaluate) function snd_func_refer returned error: Datei oder Verzeichnis nicht gefunden ALSA lib conf.c:4738:(snd_config_expand) Evaluate error: Datei oder Verzeichnis nicht gefunden ALSA lib pcm.c:2239:(snd_pcm_open_noupdate) Unknown PCM surround51 ALSA lib pcm.c:2239:(snd_pcm_open_noupdate) Unknown PCM cards.pcm.surround71 ALSA lib confmisc.c:1286:(snd_func_refer) Unable to find definition 'cards.ALS4000.pcm.iec958.0:CARD=0,AES0=4,AES1=130,AES2=0,AES3=2' ALSA lib conf.c:4259:(_snd_config_evaluate) function snd_func_refer returned error: Datei oder Verzeichnis nicht gefunden ALSA lib conf.c:4738:(snd_config_expand) Evaluate error: Datei oder Verzeichnis nicht gefunden ALSA lib pcm.c:2239:(snd_pcm_open_noupdate) Unknown PCM iec958 ALSA lib confmisc.c:1286:(snd_func_refer) Unable to find definition 'cards.ALS4000.pcm.iec958.0:CARD=0,AES0=4,AES1=130,AES2=0,AES3=2' ALSA lib conf.c:4259:(_snd_config_evaluate) function snd_func_refer returned error: Datei oder Verzeichnis nicht gefunden ALSA lib conf.c:4738:(snd_config_expand) Evaluate error: Datei oder Verzeichnis nicht gefunden ALSA lib pcm.c:2239:(snd_pcm_open_noupdate) Unknown PCM spdif ALSA lib confmisc.c:1286:(snd_func_refer) Unable to find definition 'cards.ALS4000.pcm.iec958.0:CARD=0,AES0=4,AES1=130,AES2=0,AES3=2' ALSA lib conf.c:4259:(_snd_config_evaluate) function snd_func_refer returned error: Datei oder Verzeichnis nicht gefunden ALSA lib conf.c:4738:(snd_config_expand) Evaluate error: Datei oder Verzeichnis nicht gefunden ALSA lib pcm.c:2239:(snd_pcm_open_noupdate) Unknown PCM spdif ALSA lib pcm.c:2239:(snd_pcm_open_noupdate) Unknown PCM cards.pcm.hdmi ALSA lib pcm.c:2239:(snd_pcm_open_noupdate) Unknown PCM cards.pcm.hdmi ALSA lib pcm.c:2239:(snd_pcm_open_noupdate) Unknown PCM cards.pcm.modem ALSA lib pcm.c:2239:(snd_pcm_open_noupdate) Unknown PCM cards.pcm.modem ALSA lib pcm.c:2239:(snd_pcm_open_noupdate) Unknown PCM cards.pcm.phoneline ALSA lib pcm.c:2239:(snd_pcm_open_noupdate) Unknown PCM cards.pcm.phoneline ALSA lib
Bug#748485: audacity: steals window manager focus frequently
Hi, comment from an interested user: it might be useful to have this report become fully and easily reproducible, by amending a simple yet nicely documented test case (automated execution script etc.). And yeah, I fully support your complaint about undesirable app behaviour. Thanks, Andreas Mohr -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#776929: tinydyndns: please make the build reproducible
Source: tinydyndns
Version: 0.4.2.debian1-1
Severity: wishlist
Tags: patch
User: reproducible-bui...@lists.alioth.debian.org
Usertags: timestamps
X-Debbugs-Cc: reproducible-bui...@lists.alioth.debian.org
Hi,
While working on the reproducible builds effort [1], we have noticed
that tinydyndns could not be built reproducibly.
The attached patch removes timetsamps from the build system. Once
applied, tinydyndns can be built reproducibly in our current
experimental
framework.
[1]: https://wiki.debian.org/ReproducibleBuilds
Regards,
--
,''`.
: :' : Chris Lamb
`. `'` la...@debian.org / chris-lamb.co.uk
`-
diff -urNad tinydyndns.orig/tinydyndns-0.4.2.debian1/debian/implicit
tinydyndns/tinydyndns-0.4.2.debian1/debian/implicit
--- tinydyndns.orig/tinydyndns-0.4.2.debian1/debian/implicit2015-02-03
11:44:57.480939460 +
+++ tinydyndns/tinydyndns-0.4.2.debian1/debian/implicit 2015-02-03
11:58:32.987197367 +
@@ -35,7 +35,7 @@
debian/$*/usr/share/doc/$*/changelog'
@test -s debian/$*/usr/share/doc/$*/changelog || \
sh -cx 'rm -f debian/$*/usr/share/doc/$*/changelog'
- @gzip -9 debian/$*/usr/share/doc/$*/changelog*
+ @gzip -9n debian/$*/usr/share/doc/$*/changelog*
%.deb-docs-docs: %.deb-docs-base
@for i in `cat debian/$*.docs 2/dev/null || :`; do \
if test -d $$i; then \
@@ -54,7 +54,7 @@
@if test -r debian/$*.NEWS.Debian; then \
sh -cx 'install -m0644 debian/$*.NEWS.Debian \
debian/$*/usr/share/doc/$*/NEWS.Debian \
- gzip -9 debian/$*/usr/share/doc/$*/NEWS.Debian'; \
+ gzip -9n debian/$*/usr/share/doc/$*/NEWS.Debian'; \
fi
%.deb-docs-examples: %.deb-docs-docs
@rm -rf debian/$*/usr/share/doc/$*/examples
diff -urNad tinydyndns.orig/tinydyndns-0.4.2.debian1/debian/rules
tinydyndns/tinydyndns-0.4.2.debian1/debian/rules
--- tinydyndns.orig/tinydyndns-0.4.2.debian1/debian/rules 2015-02-03
11:44:57.480939460 +
+++ tinydyndns/tinydyndns-0.4.2.debian1/debian/rules2015-02-03
11:58:20.894690398 +
@@ -46,7 +46,7 @@
install -d -m0755 '$(DIR)'/usr/share/man/man8
for i in *.8; do \
install -m0644 $$i '$(DIR)'/usr/share/man/man8/ \
- gzip -9 '$(DIR)'/usr/share/man/man8/$${i##*/} || exit 1; \
+ gzip -9n '$(DIR)'/usr/share/man/man8/$${i##*/} || exit 1; \
done
# changelog
rm -f changelog ln -s package/CHANGES changelog
Bug#776933: maildirsync: please make the build reproducible
Source: maildirsync Version: 1.2-1.1 Severity: wishlist Tags: patch User: reproducible-bui...@lists.alioth.debian.org Usertags: timestamps X-Debbugs-Cc: reproducible-bui...@lists.alioth.debian.org Hi, While working on the reproducible builds effort [1], we have noticed that maildirsync could not be built reproducibly. The attached patch removes timestamps from the build system. Once applied, maildirsync can be built reproducibly in our current experimental framework. [1]: https://wiki.debian.org/ReproducibleBuilds Regards, -- ,''`. : :' : Chris Lamb `. `'` la...@debian.org / chris-lamb.co.uk `- diff -urNad maildirsync.orig/maildirsync-1.2/debian/rules maildirsync/maildirsync-1.2/debian/rules --- maildirsync.orig/maildirsync-1.2/debian/rules 2015-02-03 12:12:34.423081240 + +++ maildirsync/maildirsync-1.2/debian/rules2015-02-03 12:13:16.117038074 + @@ -35,7 +35,7 @@ dh_installchangelogs Changes dh_installdocs dh_installexamples - cd contrib tar -cf - mailbalance-0.2.0 | gzip -9 ../debian/maildirsync/usr/share/doc/maildirsync/examples/mailbalance-0.2.0.tar.gz + cd contrib tar -cf - mailbalance-0.2.0 | gzip -9n ../debian/maildirsync/usr/share/doc/maildirsync/examples/mailbalance-0.2.0.tar.gz dh_installman dh_link dh_compress
Bug#776934: dh-make-php: please make the build reproducible
Source: dh-make-php Version: 0.4.0 Severity: wishlist Tags: patch User: reproducible-bui...@lists.alioth.debian.org Usertags: timestamps X-Debbugs-Cc: reproducible-bui...@lists.alioth.debian.org Hi, While working on the reproducible builds effort [1], we have noticed that dh-make-php could not be built reproducibly. The attached patch removes timestamps from the build system. Once applied, dh-make-php can be built reproducibly in our current experimental framework. [1]: https://wiki.debian.org/ReproducibleBuilds Regards, -- ,''`. : :' : Chris Lamb `. `'` la...@debian.org / chris-lamb.co.uk `- diff -urNad dh-make-php.orig/dh-make-php-0.4.0/Makefile dh-make-php/dh-make-php-0.4.0/Makefile --- dh-make-php.orig/dh-make-php-0.4.0/Makefile 2015-02-03 12:12:15.158176514 + +++ dh-make-php/dh-make-php-0.4.0/Makefile 2015-02-03 12:12:53.871994237 + @@ -10,12 +10,12 @@ dh-make-pecl.1.gz: man/dh-make-pecl.xml $(XP) $(DB2MAN) $ rm -f dh-make-pecl.1.gz - gzip -9 dh-make-pecl.1 + gzip -9n dh-make-pecl.1 dh-make-pear.1.gz: man/dh-make-pear.xml $(XP) $(DB2MAN) $ rm -f dh-make-pear.1.gz - gzip -9 dh-make-pear.1 + gzip -9n dh-make-pear.1 install: install-bin install-share install-man
Bug#768269: appdata-tools and appstream-util: error when trying to install together
2015-02-03 12:38 GMT+01:00 Andreas Beckmann a...@debian.org: Followup-For: Bug #768269 Control: found -1 0.3.2-2 Hi, during a test with piuparts I noticed your package fails to upgrade from 'sid' to 'experimental'. It installed fine in 'sid', then the upgrade to 'experimental' fails because it tries to overwrite other packages files without declaring a Breaks+Replaces relation. Oh crap, thanks for noticing this! I will upload a fixed version soon (maybe today, if I manage to do that) Cheers, Matthias -- Debian Developer | Freedesktop-Developer I welcome VSRE emails. See http://vsre.info/ -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#776943: unblock: vmdebootstrap/0.5-2
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: unblock
Please unblock package vmdebootstrap
This release fixes a serious bug when images larger than ~1GB created
with the default arguments wouldn't boot, what brought the package into
a non-releasable state in the maintainers' opinion.
The debdiff against the version currently in testing is attached.
unblock vmdebootstrap/0.5-2
-- System Information:
Debian Release: 8.0
APT prefers buildd-unstable
APT policy: (500, 'buildd-unstable'), (500, 'unstable'), (500, 'testing'),
(1, 'experimental')
Architecture: amd64 (x86_64)
Kernel: Linux 3.16.0-4-amd64 (SMP w/4 CPU cores)
Locale: LANG=pt_BR.UTF-8, LC_CTYPE=pt_BR.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
--
Antonio Terceiro terce...@debian.org
diff -Nru vmdebootstrap-0.5/debian/changelog vmdebootstrap-0.5/debian/changelog
--- vmdebootstrap-0.5/debian/changelog 2014-11-16 13:27:52.0 -0200
+++ vmdebootstrap-0.5/debian/changelog 2015-02-02 18:38:32.0 -0200
@@ -1,3 +1,13 @@
+vmdebootstrap (0.5-2) unstable; urgency=medium
+
+ * Backport patches from upstream master branch to fix creation of images
+larger than 1GB that use extlinux (the default). Closes: #774588
+. In debian/patches/:
+ - 0001-fix-creation-of-extlinux-configuration.patch
+ - 0002-add-mbr-back-to-support-extlinux-and-check-for-insta.patch
+
+ -- Antonio Terceiro terce...@debian.org Mon, 02 Feb 2015 18:38:22 -0200
+
vmdebootstrap (0.5-1) unstable; urgency=medium
* New upstream bug fix release for Jessie.
diff -Nru vmdebootstrap-0.5/debian/patches/0001-fix-creation-of-extlinux-configuration.patch vmdebootstrap-0.5/debian/patches/0001-fix-creation-of-extlinux-configuration.patch
--- vmdebootstrap-0.5/debian/patches/0001-fix-creation-of-extlinux-configuration.patch 1969-12-31 21:00:00.0 -0300
+++ vmdebootstrap-0.5/debian/patches/0001-fix-creation-of-extlinux-configuration.patch 2015-02-02 18:38:32.0 -0200
@@ -0,0 +1,52 @@
+From 3a77e8b1178fcf49dd290659320dc736a1dfceef Mon Sep 17 00:00:00 2001
+From: Neil Williams codeh...@debian.org
+Date: Mon, 2 Feb 2015 16:38:50 -0200
+Subject: [PATCH 1/2] fix creation of extlinux configuration
+
+This change is a backport of 545b3e5065fa1f57540cb01255d911d3c5ef2f96
+
+Signed-off-by: Antonio Terceiro terce...@debian.org
+---
+ vmdebootstrap | 19 +--
+ 1 file changed, 13 insertions(+), 6 deletions(-)
+
+diff --git a/vmdebootstrap b/vmdebootstrap
+index 24e38d0..74627e2 100755
+--- a/vmdebootstrap
b/vmdebootstrap
+@@ -521,8 +521,9 @@ class VmDebootstrap(cliapp.Application):
+
+ conf = os.path.join(rootdir, 'extlinux.conf')
+ logging.debug('configure extlinux %s' % conf)
+-f = open(conf, 'w')
+-f.write('''
++kserial = 'console=ttyS0,115200' if self.settings['serial-console'] else ''
++extserial = 'serial 0 115200' if self.settings['serial-console'] else ''
++msg = '''
+ default linux
+ timeout 1
+
+@@ -534,10 +535,16 @@ append initrd=%(initrd)s root=UUID=%(uuid)s ro %(kserial)s
+ 'kernel': kernel_image,
+ 'initrd': initrd_image,
+ 'uuid': uuid,
+-'kserial':
+-'console=ttyS0,115200' if self.settings['serial-console'] else '',
+-'extserial': 'serial 0 115200' if self.settings['serial-console'] else '',
+-})
++'kserial': kserial,
++'extserial': extserial,
++}
++logging.debug(extlinux config:\n%s, msg)
++
++# python multiline string substitution is just ugly.
++# use an external file or live with the mangling, no point in
++# mangling the string to remove spaces just to keep it pretty in source.
++f = open(conf, 'w')
++f.write(msg)
+ f.close()
+
+ self.runcmd(['extlinux', '--install', rootdir])
+--
+2.1.4
+
diff -Nru vmdebootstrap-0.5/debian/patches/0002-add-mbr-back-to-support-extlinux-and-check-for-insta.patch vmdebootstrap-0.5/debian/patches/0002-add-mbr-back-to-support-extlinux-and-check-for-insta.patch
--- vmdebootstrap-0.5/debian/patches/0002-add-mbr-back-to-support-extlinux-and-check-for-insta.patch 1969-12-31 21:00:00.0 -0300
+++ vmdebootstrap-0.5/debian/patches/0002-add-mbr-back-to-support-extlinux-and-check-for-insta.patch 2015-02-02 18:38:32.0 -0200
@@ -0,0 +1,48 @@
+From 087a1e23eb451d8fc33bd04b1e417b56f0d71692 Mon Sep 17 00:00:00 2001
+From: Neil Williams codeh...@debian.org
+Date: Mon, 2 Feb 2015 16:50:09 -0200
+Subject: [PATCH 2/2] add mbr back to support extlinux and check for
+ installation of mbr.
+
+Signed-off-by: Antonio Terceiro terce...@debian.org
+---
+ vmdebootstrap | 9 +++--
+ 1 file changed, 7 insertions(+), 2 deletions(-)
+
+diff --git a/vmdebootstrap b/vmdebootstrap
+index 74627e2..67caa84 100755
+--- a/vmdebootstrap
b/vmdebootstrap
+@@ -108,7
Bug#776945: reportbug: traceback on checking for openjdk versions
Package: reportbug Version: 6.4.4+deb7u1 Severity: normal Hi, I have trouble reporting a bug against openjdk-7-jdk: $ reportbug -b openjdk-7-jdk *** Welcome to reportbug. Use ? for help at prompts. *** Note: bug reports are publicly archived (including the email address of the submitter). Detected character set: UTF-8 Please change your locale if this is incorrect. Using 'Toni Mueller supp...@oeko.net' as your from address. Getting status for openjdk-7-jdk... Verifying package integrity... Checking for newer versions at madison, incoming.debian.org and http://ftp-master.debian.org/new.html Traceback (most recent call last): File /usr/bin/reportbug, line 2206, in module main() File /usr/bin/reportbug, line 1080, in main return iface.user_interface() File /usr/bin/reportbug, line 1601, in user_interface http_proxy=self.options.http_proxy, arch=arch) File /usr/lib/pymodules/python2.7/reportbug/checkversions.py, line 216, in check_available comparison = compare_versions(version, avail[dist]) File /usr/lib/pymodules/python2.7/reportbug/checkversions.py, line 91, in compare_versions return debian_support.version_compare(upstream, current) File /usr/lib/python2.7/dist-packages/debian/debian_support.py, line 268, in version_compare return cmp(Version(a), Version(b)) File /usr/lib/python2.7/dist-packages/debian/debian_support.py, line 172, in __init__ super(AptPkgVersion, self).__init__(version) File /usr/lib/python2.7/dist-packages/debian/debian_support.py, line 91, in __init__ self.full_version = version File /usr/lib/python2.7/dist-packages/debian/debian_support.py, line 117, in __setattr__ self._set_full_version(str(value)) File /usr/lib/python2.7/dist-packages/debian/debian_support.py, line 96, in _set_full_version raise ValueError(Invalid version string %r % version) ValueError: Invalid version string '7u75-2.5.4-1~deb7u1 7u71-2.5.3-2~deb7u1 7u65-2.5.1-5~deb7u1 7u65-2.5.1-2~deb7u1 7u55-2.4.7-1~deb7u1 7u25-2.3.10-1~deb7u1' $ Cheers, --Toni++ -- Package-specific info: ** Environment settings: EDITOR=vi DEBEMAIL=t...@debian.org EMAIL=supp...@oeko.net INTERFACE=text ** /home/toni/.reportbugrc: reportbug_version 3.12 mode advanced ui text realname Toni Mueller email supp...@oeko.net -- System Information: Debian Release: 7.8 APT prefers stable APT policy: (990, 'stable'), (90, 'testing'), (70, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 3.16.0-0.bpo.4-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages reportbug depends on: ii apt 0.9.7.9+deb7u7 ii python2.7.3-4+deb7u1 ii python-reportbug 6.4.4+deb7u1 reportbug recommends no packages. Versions of packages reportbug suggests: pn claws-mail none ii debconf-utils 1.5.49 ii debsums 2.0.52+deb7u1 ii dlocate 1.02 ii emacs23-bin-common 23.4+1-4 ii file5.11-2+deb7u6 ii gnupg 1.4.12-7+deb7u6 ii postfix [mail-transport-agent] 2.9.6-2 ii python-gtk2 2.24.0-3+b1 pn python-gtkspell none ii python-urwid1.0.1-2 ii python-vte 1:0.28.2-5 ii xdg-utils 1.1.0~rc1+git20111210-6+deb7u1 Versions of packages python-reportbug depends on: ii apt 0.9.7.9+deb7u7 ii python2.7.3-4+deb7u1 ii python-debian 0.1.21 ii python-debianbts 1.11 ii python-support1.0.15 python-reportbug suggests no packages. -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#775595: RFS: pyuca/1.0-1 [ITP] -- Python Unicode sorting library
... looking for a sponsor for my package of ... of course DS -- http://qa.debian.org/developer.php?login=debian%40danielstender.com 4096R/DF5182C8 46CB1CA89EA3B74376761DB915E09AF4DF5182C8 -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#776957: Panic at boot on arm64 systems
Package: src:linux Version: 3.16.7-ckt4-2 Severity: grave Tags: patch upstream The latest upstream stable kernel pull is broken on arm64. The system panics during early boot in arch_timer setup. The cause is simple. Commit 0b46b8a718c6e90910a1b1b0fe797be3c167e186 was pulled into stable, but a later fix d6ad36913083d683aad4e02e53580c995f1a6ede was missed and is necessary. Ian has already taken this patch; please upload a fixed linux ASAP. Cheers, Steve -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#776953: exmh: please make the build reproducible
Source: exmh Version: 1:2.8.0-4 Severity: wishlist Tags: patch User: reproducible-bui...@lists.alioth.debian.org Usertags: timestamps X-Debbugs-Cc: reproducible-bui...@lists.alioth.debian.org Hi, While working on the reproducible builds effort [1], we have noticed that exmh could not be built reproducibly. The attached patch removes timestamps from the build system. Once applied, exmh can be built reproducibly in our current experimental framework. [1]: https://wiki.debian.org/ReproducibleBuilds Regards, -- ,''`. : :' : Chris Lamb `. `'` la...@debian.org / chris-lamb.co.uk `- diff -urNad exmh.orig/exmh-2.8.0/debian/rules exmh/exmh-2.8.0/debian/rules --- exmh.orig/exmh-2.8.0/debian/rules 2015-02-03 14:23:26.659868533 + +++ exmh/exmh-2.8.0/debian/rules2015-02-03 14:23:56.829250370 + @@ -74,7 +74,7 @@ # man pages $(INSTALL_DATA) exmh.l $(DSTDIR)/usr/share/man/man1/exmh.1 - -gzip -9fr $(DSTDIR)/usr/share/man/man1 + -gzip -9frn $(DSTDIR)/usr/share/man/man1 # html documentation goes into html dir, extras go into misc subdir # others go into main docs area @@ -85,7 +85,7 @@ $(INSTALL_DATA) debian/copyright $(DSTDIR)/usr/share/doc/exmh/copyright $(INSTALL_DATA) debian/changelog $(DSTDIR)/usr/share/doc/exmh/changelog.Debian $(INSTALL_DATA) exmh.CHANGES $(DSTDIR)/usr/share/doc/exmh/changelog - gzip -9 $(DSTDIR)/usr/share/doc/exmh/changelog* + gzip -9n $(DSTDIR)/usr/share/doc/exmh/changelog* $(INSTALL_DATA) debian/README.debian $(DSTDIR)/usr/share/doc/exmh $(INSTALL_DATA) exmh.README $(DSTDIR)/usr/share/doc/exmh/README
Bug#776955: elida: please make the build reproducible
Source: elida Version: 0.4+nmu1 Severity: wishlist Tags: patch User: reproducible-bui...@lists.alioth.debian.org Usertags: timestamps X-Debbugs-Cc: reproducible-bui...@lists.alioth.debian.org Hi, While working on the reproducible builds effort [1], we have noticed that elida could not be built reproducibly. The attached patch removes timestamps from the build system. Once applied, elida can be built reproducibly in our current experimental framework. [1]: https://wiki.debian.org/ReproducibleBuilds Regards, -- ,''`. : :' : Chris Lamb `. `'` la...@debian.org / chris-lamb.co.uk `- diff -urNad elida.orig/elida-0.4+nmu1/debian/rules elida/elida-0.4+nmu1/debian/rules --- elida.orig/elida-0.4+nmu1/debian/rules 2015-02-03 14:25:23.205205769 + +++ elida/elida-0.4+nmu1/debian/rules 2015-02-03 14:25:36.781827322 + @@ -28,8 +28,8 @@ install -m 0644 elidad.1 $T/usr/share/man/man1 install -m 0644 debian/changelog $T/usr/share/doc/$P/changelog install -m 0644 README $T/usr/share/doc/$P - gzip -9 $T/usr/share/man/man1/* - gzip -9 $T/usr/share/doc/$P/* + gzip -9n $T/usr/share/man/man1/* + gzip -9n $T/usr/share/doc/$P/* install -m 0644 debian/copyright $T/usr/share/doc/$P dpkg-gencontrol -isp chown -R root.root $T
Bug#776956: diploma: please make the build reproducible
Source: diploma Version: 1.2.11 Severity: wishlist Tags: patch User: reproducible-bui...@lists.alioth.debian.org Usertags: timestamps X-Debbugs-Cc: reproducible-bui...@lists.alioth.debian.org Hi, While working on the reproducible builds effort [1], we have noticed that diploma could not be built reproducibly. The attached patch removes timestamps from the build system. Once applied, diploma can be built reproducibly in our current experimental framework. [1]: https://wiki.debian.org/ReproducibleBuilds Regards, -- ,''`. : :' : Chris Lamb `. `'` la...@debian.org / chris-lamb.co.uk `- diff -urNad diploma.orig/diploma-1.2.11/debian/rules diploma/diploma-1.2.11/debian/rules --- diploma.orig/diploma-1.2.11/debian/rules2015-02-03 14:26:57.453520417 + +++ diploma/diploma-1.2.11/debian/rules 2015-02-03 14:28:52.574788868 + @@ -15,7 +15,7 @@ dh_testdir # Add here commands to compile the package. - $(MAKE) + GZIP=-n $(MAKE) touch build-stamp
Bug#771205: libgtk-3-0: Scale bug in gtk which affect a lot gnome applications
Scaling margins on printing from Gtk is not a release-critical issue in Debian. Only to clarify, it is impossible to print landscape pdfs in Debian Jessie with Evince. It is *not* only a scaling problem, because Evince/gtk scale as soon I print a landscape document. Samuel
Bug#774994: O: libhx -- C library providing queue, tree, I/O and utility functions
retitle 774994 ITA: libhx -- C library providing queue, tree, I/O and utility functions owner 774994 ! thanks Hi, I want to adopt this package. CU Jörg -- New: GPG Fingerprint: 63E0 075F C8D4 3ABB 35AB 30EE 09F8 9F3C 8CA1 D25D GPG key (long) : 09F89F3C8CA1D25D GPG Key: 8CA1D25D CAcert Key S/N : 0E:D4:56 Old (revoked since 2014-12-31): pgp Fingerprint: 7D13 3C60 0A10 DBE1 51F8 EBCB 422B 44B0 BE58 1B6E pgp Key: BE581B6E Jörg Frings-Fürst D-54526 Niederkail Threema: SYR8SJXB IRC: j_...@freenode.net j_...@oftc.net My wish list: - Please send me a picture from the nature at your home. signature.asc Description: This is a digitally signed message part
Bug#776958: RFP: mate-tweak -- MATE desktop tweak tool
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Package: wnpp Severity: wishlist Owner: Vangelis Mouhtsis vange...@gnugr.org * Package name: mate-tweak Version : 3.4.1~15.04-1 Upstream Author : Martin Wimpress c...@ubuntu-mate.org * URL : https://bitbucket.org/flexion/mate-tweak/ * License : GPL Programming Lang: Python Description : MATE desktop tweak tool Configures some aspects of the MATE desktop, including: * Appearance * Extensions * Fonts * Setup apps * Workspaces * Peripheral devices . This package will be maintained by the Debian MATE Packaging Team. -BEGIN PGP SIGNATURE- Version: GnuPG v1 iQEcBAEBAgAGBQJU0OmAAAoJEGaW2W7vxiDhvZEH/R0QHRBm0w32EWKoK8FDNEDh 6TFJZIBcoaMwyfTo/hh8i58OQVZPBXPlHg1bTgNhT1uU+UHU1gDLwOQJk5VkAk87 j2X5y5IolNRlFZbjS+5KIwPgUHIeWM75HnqXJjSE0/02e3vvsNdvOsm4qWRJekPY bScdLG27bEcNPsHd1+YpvsZk0eFb10y2xtzYIiu1qSOa3/OO6e2+rwxKfT9Qapqg 99kOtIrSeNk+yxoBVFSH3DMr+SerE4uJjDS+8mDB8HmcfHYtaFtbOlTZRJnQ5Mue Nv6kkKldOzgTV+EiJv7/lrfp+dUrZnZstlkvVBT4xQcBJCwVdc/YLvwiXTrzpY0= =Z67r -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#776954: lintian: warn about /etc/bash_completion.d
Package: lintian Version: 2.5.30+deb8u3 Severity: normal Hi! Maybe it's time for lintian to warn about the old bash-completion location -- if only to get a more consistent location (and consistency with other linuxes which also seem to use the /usr/share location). Quoting README.Debian: bash-completion for Debian -- Completions are kept in /usr/share/bash-completion/completions. /etc/bash_completion.d/ is being kept for compatibility reasons; but will disappear in future. If you're a package maintainer, you're encouraged to use dh_bash-completion(1), which will take care of installing third-party completions into the appropriate directory. -- David Paleino da...@debian.org Sun, 10 Apr 2011 15:33:19 +0200 As the old location seems to still be quite popular probably a low-priority tag is the right thing for now Christoph -- System Information: Debian Release: 8.0 APT prefers testing APT policy: (990, 'testing'), (500, 'unstable'), (500, 'stable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.16.0-4-amd64 (SMP w/6 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages lintian depends on: ii binutils 2.24.90.20141023-1 ii bzip2 1.0.6-7+b2 ii diffstat 1.58-1 ii file 1:5.20-2 ii gettext0.19.3-2 ii hardening-includes 2.6 ii intltool-debian0.35.0+20060710.1 ii libapt-pkg-perl0.1.29+b2 ii libarchive-zip-perl1.39-1 ii libclass-accessor-perl 0.34-1 ii libclone-perl 0.37-1+b1 ii libdpkg-perl 1.17.23 ii libemail-valid-perl1.195-1 ii libfile-basedir-perl 0.03-1 ii libipc-run-perl0.92-1 ii liblist-moreutils-perl 0.33-2+b1 ii libparse-debianchangelog-perl 1.2.0-1.1 ii libtext-levenshtein-perl 0.11-1 ii libtimedate-perl 2.3000-2 ii liburi-perl1.64-1 ii man-db 2.7.0.2-5 ii patchutils 0.3.3-1 ii perl [libdigest-sha-perl] 5.20.1-4 ii t1utils1.38-3+b1 Versions of packages lintian recommends: pn libperlio-gzip-perl none ii perl5.20.1-4 ii perl-modules [libautodie-perl] 5.20.1-4 Versions of packages lintian suggests: pn binutils-multiarch none ii dpkg-dev 1.17.23 ii libhtml-parser-perl3.71-1+b3 ii libtext-template-perl 1.46-1 ii libyaml-perl 1.13-1 ii xz-utils 5.1.1alpha+20120614-2+b3 -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#776007: CVE-2015-1430: buffer overrun in acknowledge.c(gi)
Hi, Moritz Mühlenhoff wrote: On Tue, Jan 27, 2015 at 12:34:09PM +0100, Axel Beckert wrote: I hadn't checked the status in jessie yet, but I just did and you're right: Wheezy/Squeeze is not affected. JFTR: This now has been confirmed on the upstream mailing list. The bug has been introduced upstream with release 4.3.4. For details see http://lists.xymon.com/archive/2015-February/040936.html and http://sourceforge.net/p/xymon/code/6691/tree//trunk/web/acknowledge.c?diff=516c17fd34309d2eb14bcb64:6690 Regards, Axel -- ,''`. | Axel Beckert a...@debian.org, http://people.debian.org/~abe/ : :' : | Debian Developer, ftp.ch.debian.org Admin `. `' | 4096R: 2517 B724 C5F6 CA99 5329 6E61 2FF9 CD59 6126 16B5 `-| 1024D: F067 EA27 26B9 C3FC 1486 202E C09E 1D89 9593 0EDE -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#770016: Clarify network access for building packages in main
On 31/01/15 at 20:47 +0100, Bill Allombert wrote: On Mon, Nov 24, 2014 at 10:21:27AM +0100, Lucas Nussbaum wrote: On 23/11/14 at 21:13 +0100, Bill Allombert wrote: Was there a lot of failure ? No What severity did you use for the bug report ? serious So in practice, this is already handled as a RC bug. Good. Are you in favor of the patch above ? In general, yes. So are you willing to second it ? yeah, I second this version: + For packages in the main archive, no required targets + may attempt network access. even if I would prefer something that did not restrict to main, and said something like: No packages may rely on network access to be available during the execution of required targets. Lucas signature.asc Description: Digital signature
Bug#776959: linux-image-3.16.0-4-amd64: [regression] sd card reader in retina macbook pro no longer working
Package: src:linux
Version: 3.16.7-ckt2-1
Severity: important
after upgrading from 3.13 where the built-in sd card worked perfectly,
there is no longer even any kernel events or anything remotely indicating
that the apple sd card reader is recognised.
i note that there is a similar bug
https://lists.debian.org/debian-kernel/2014/09/msg00170.html
however this is for an entirely different laptop.
l.
-- Package-specific info:
** Version:
Linux version 3.16.0-4-amd64 (debian-ker...@lists.debian.org) (gcc version
4.8.3 (Debian 4.8.3-16) ) #1 SMP Debian 3.16.7-ckt2-1 (2014-12-08)
** Command line:
BOOT_IMAGE=/boot/vmlinuz-3.16.0-4-amd64
root=UUID=2b2a5854-dfd8-444c-87d0-a3c6eb140939 ro quiet
** Tainted: PBWO (4641)
* Proprietary module has been loaded.
* System has hit bad_page.
* Taint on warning.
* Out-of-tree module has been loaded.
** Kernel log:
[916674.465753] ata1.00: status: { DRDY }
[916674.465756] ata1: hard resetting link
[916675.190264] ata1: SATA link up 1.5 Gbps (SStatus 113 SControl 310)
[916675.190730] ata1.00: unexpected _GTF length (8)
[916675.191273] ata1.00: unexpected _GTF length (8)
[916675.191338] ata1.00: configured for UDMA/33
[916675.191403] ata1: EH complete
[916689.005059] ata1.00: exception Emask 0x10 SAct 0x20 SErr 0x404
action 0xe frozen
[916689.005063] ata1.00: irq_stat 0x8040, connection status changed
[916689.005066] ata1: SError: { CommWake DevExch }
[916689.005069] ata1.00: failed command: READ FPDMA QUEUED
[916689.005074] ata1.00: cmd 60/08:a8:00:4a:a5/00:00:00:00:00/40 tag 21 ncq
4096 in
[916689.005074] res 40/00:a4:00:10:78/00:00:0c:00:00/40 Emask 0x10
(ATA bus error)
[916689.005076] ata1.00: status: { DRDY }
[916689.005080] ata1: hard resetting link
[916689.729644] ata1: SATA link up 1.5 Gbps (SStatus 113 SControl 310)
[916689.730082] ata1.00: unexpected _GTF length (8)
[916689.730600] ata1.00: unexpected _GTF length (8)
[916689.730666] ata1.00: configured for UDMA/33
[916689.730717] ata1: EH complete
** Model information
sys_vendor: Apple Inc.
product_name: MacBookPro11,1
product_version: 1.0
chassis_vendor: Apple Inc.
chassis_version: Mac-189A3D4F975D5FFC
bios_vendor: Apple Inc.
bios_version: MBP111.88Z.0138.B03.1310291227
board_vendor: Apple Inc.
board_name: Mac-189A3D4F975D5FFC
board_version: MacBookPro11,1
** Loaded modules:
rtsx_usb
wl(PO)
cp210x
ftdi_sio
snd_usb_audio
snd_usbmidi_lib
snd_seq_midi
snd_seq_midi_event
snd_rawmidi
cfg80211
sr9700
dm9601
usbnet
mii
snd_hrtimer
snd_seq_dummy
rfcomm
bnep
cpufreq_powersave
cpufreq_stats
cpufreq_userspace
cpufreq_conservative
binfmt_misc
uinput
nfsd
auth_rpcgss
oid_registry
nfs_acl
nfs
lockd
fscache
sunrpc
tun
nls_utf8
nls_cp437
vfat
fat
fuse
firewire_sbp2
firewire_core
crc_itu_t
loop
kaweth
ecb
btusb
bluetooth
6lowpan_iphc
rfkill
iTCO_wdt
iTCO_vendor_support
hid_generic
usbserial
wacom
hid_apple
joydev
usbhid
hid
bcm5974
x86_pkg_temp_thermal
intel_powerclamp
intel_rapl
coretemp
efi_pstore
kvm_intel
kvm
crct10dif_pclmul
crc32_pclmul
ghash_clmulni_intel
evdev
applesmc
input_polldev
aesni_intel
aes_x86_64
lrw
gf128mul
glue_helper
ablk_helper
cryptd
efivars
sbs
i2c_i801
lpc_ich
mfd_core
snd_hda_codec_cirrus
snd_hda_codec_generic
sbshc
snd_hda_intel
snd_hda_controller
snd_hda_codec
i915
snd_hwdep
snd_pcm
snd_seq
snd_seq_device
snd_timer
video
apple_bl
battery
drm_kms_helper
drm
i2c_algo_bit
i2c_core
ac
snd
mei_me
processor
mei
thermal_sys
soundcore
button
ext4
crc16
mbcache
jbd2
md_mod
dm_mirror
dm_region_hash
dm_log
dm_mod
sg
sd_mod
crc_t10dif
crct10dif_common
usb_storage
crc32c_intel
ahci
libahci
libata
scsi_mod
xhci_hcd
usbcore
usb_common
** Network interface configuration:
auto lo
iface lo inet loopback
allow-hotplug eth0
iface eth0 inet dhcp
auto mytap
iface mytap inet static
address 10.0.3.1
netmask 255.255.255.0
vde2-switch -t mytap
allow-hotplug usb0
iface usb0 inet static
address 10.20.0.1
netmask 255.255.255.0
** Network status:
*** IP interfaces and addresses:
1: lo: LOOPBACK,UP,LOWER_UP mtu 65536 qdisc noqueue state UNKNOWN group
default
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
inet 127.0.0.1/8 scope host lo
valid_lft forever preferred_lft forever
inet6 ::1/128 scope host
valid_lft forever preferred_lft forever
2: mytap: BROADCAST,MULTICAST,UP,LOWER_UP mtu 1500 qdisc pfifo_fast state UP
group default qlen 500
link/ether 32:d8:e1:96:1f:94 brd ff:ff:ff:ff:ff:ff
inet 10.0.3.1/24 brd 10.0.3.255 scope global mytap
valid_lft forever preferred_lft forever
inet6 fe80::30d8:e1ff:fe96:1f94/64 scope link
valid_lft forever preferred_lft forever
5: tun0: POINTOPOINT,MULTICAST,NOARP,UP,LOWER_UP mtu 1500 qdisc pfifo_fast
state UNKNOWN group default qlen 100
link/none
inet 10.8.0.199 peer 10.8.0.200/32 scope global tun0
valid_lft forever preferred_lft forever
6: tun1: POINTOPOINT,MULTICAST,NOARP,UP,LOWER_UP mtu 1500 qdisc pfifo_fast
state UNKNOWN group default qlen 100
Bug#776905: Please consider adding libudev-dev as build-dependency
Package: util-linux Version: 2.25.2-4.2 Could you please consider adding libudev-dev to the build-dependencies of util-linux. This will enable lsblk to show the LABEL and PARTLABEL information when running as a non-root user. I ran into this issue when checking the lsblk output as non-root and noticed that it won't display the parition label (e.g. $ lsblk --ascii --output NAME,LABEL --pairs will show a empty label. But $ sudo lsblk --ascii --output NAME,LABEL --pairs will show the label (if you have a label :) Adding the build-dependency fixes this. Thanks for considering, Michael -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#628546: Fwd: uswsusp: uses deprecated ioctl, please update
Package: uswsusp Version: 1.0+20110509-3 Followup-For: Bug #628546 Dear Maintainer, This bug seems to lack a found version; this should fix that. I get this message from the kernel whenever I resume my system from disk, too: , | [435073.232971] PM: restore of devices complete after 1488.637 msecs | [435073.255281] Restarting kernel threads ... done. | [435073.255415] snapshot_ioctl: ioctl '4004330c' is deprecated and will be removed soon, update your suspend-to-disk utilities | [435073.255493] Restarting tasks ... done. | [435073.21] PM: Basic memory bitmaps freed ` This seems to come from the platform_finish() function in swsusp.h. -- System Information: Debian Release: 7.8 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 uswsusp depends on: ii debconf [debconf-2.0] 1.5.49 ii libc6 2.13-38+deb7u7 ii libgcrypt111.5.0-5+deb7u2 ii liblzo2-2 2.06-1+deb7u1 ii libpci31:3.1.9-6 ii libx86-1 1.1+ds1-10 Versions of packages uswsusp recommends: ii initramfs-tools 0.109.1 ii mount2.20.1-5.3 uswsusp suggests no packages. -- debconf information: * uswsusp/compress: true * uswsusp/compute_checksum: false uswsusp/create_RSA_key: false uswsusp/no_snapshot: * uswsusp/snapshot_device: * uswsusp/suspend_loglevel: 6 uswsusp/RSA_key_file: /etc/uswsusp.key uswsusp/no_swap: * uswsusp/max_loglevel: 5 * uswsusp/resume_device: /dev/dm-1 uswsusp/resume_offset: * uswsusp/shutdown_method: platform * uswsusp/encrypt: false * uswsusp/splash: false * uswsusp/early_writeout: true * uswsusp/image_size: 1858691809 uswsusp/RSA_key_bits: 1024 uswsusp/continue_without_swap: true -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#776658: lintian: Memory consumption of harness and html_reports
On 2015-02-02 22:13, Niels Thykier wrote: I got a patch series to implement this (see also [BRANCH]). I have also managed to do a few tests on lilburn.debian.org with no issues. The commit messages are at the bare minimum - apologise for that. Review/remarks welcome. With the rewrite: * harness now uses ~16MB (rather than 700ish MB). This was possibly a bit too short. The slightly longer version: * The primary harness process only uses ~16MB. * The sub-process running Lintian ends up using ~450MB. So the lintian run now have ~250MB extra memory free. * The html_reports tree will have ~700MB extra memory. ~Niels -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#775180: analysis
On 03/02/15 09:31, Holger Levsen wrote: Hi Daniel, On Dienstag, 3. Februar 2015, Daniel Pocock wrote: Is there a DSA contact who looks after ullmann.d.o? filing DSA tickets is the way to go... Or do you have sudo access? I notice nobody replied to the DSA ticket to apt-get install vpim. when did you file this ticket? It was Saturday -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#775180: analysis
On 03/02/15 at 09:22 +0100, Daniel Pocock wrote: On 03/02/15 08:55, Lucas Nussbaum wrote: Hi Daniel, On 31/01/15 at 11:09 +0100, Daniel Pocock wrote: On 30/01/15 16:20, Christophe Siraut wrote: Hi Daniel, If my proposed solution seems reasonable I'll go ahead and code it (...) It seems perfectly reasonable to me. I just want to mention that while we started refactoring DMD in order to provide RSS, YAML and JSON, we did not finish isolating the data from the presentation. In consequence you might end up with HTML code in calendar tasks, please fix or fill bugs if it happens. (There should be no HTML in dmd-data.rb nor in dmd.cgi; data should be parsed in dmd-data.rb only; dmd.cgi should be a lot simpler) I've done the following: - initial implementation using the feeditems array - requested to join collab-qa on alioth so I can push this, otherwise somebody else can apply it - sent an RT request (#5713) to DSA to install the vpim package on ullmann I've reverted the change as it broke bugs.cgi (probably due to the missing dep). Please revert the revert once the change is ready to be deployed. Is there a DSA contact who looks after ullmann.d.o? Or do you have sudo access? I notice nobody replied to the DSA ticket to apt-get install vpim. No, a ticket is the correct way to make progress here Lucas -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#770811: openvpn: openVPN tmp-dir missing
I'll add this just in case it'll be helpful for someone: when using chroot, ovenpvn can't access /etc/localtime file and can't get correct timezone, so you need to mount this file in chroot as well: mkdir /etc/openvpn/etc touch /etc/openvpn/etc/localtime mount --bind /etc/localtime /etc/openvpn/etc/localtime And write this changes in your /etc/fstab: echo /etc/localtime /etc/openvpn/etc/localtime none bind /etc/fstab -- Regards, Polotnyanko Nikita Sergeevich mailto:pboxw...@gmail.com -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#775180: analysis
On 03/02/15 08:55, Lucas Nussbaum wrote: Hi Daniel, On 31/01/15 at 11:09 +0100, Daniel Pocock wrote: On 30/01/15 16:20, Christophe Siraut wrote: Hi Daniel, If my proposed solution seems reasonable I'll go ahead and code it (...) It seems perfectly reasonable to me. I just want to mention that while we started refactoring DMD in order to provide RSS, YAML and JSON, we did not finish isolating the data from the presentation. In consequence you might end up with HTML code in calendar tasks, please fix or fill bugs if it happens. (There should be no HTML in dmd-data.rb nor in dmd.cgi; data should be parsed in dmd-data.rb only; dmd.cgi should be a lot simpler) I've done the following: - initial implementation using the feeditems array - requested to join collab-qa on alioth so I can push this, otherwise somebody else can apply it - sent an RT request (#5713) to DSA to install the vpim package on ullmann I've reverted the change as it broke bugs.cgi (probably due to the missing dep). Please revert the revert once the change is ready to be deployed. Is there a DSA contact who looks after ullmann.d.o? Or do you have sudo access? I notice nobody replied to the DSA ticket to apt-get install vpim. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#775180: analysis
Hi Daniel, On Dienstag, 3. Februar 2015, Daniel Pocock wrote: Is there a DSA contact who looks after ullmann.d.o? filing DSA tickets is the way to go... Or do you have sudo access? I notice nobody replied to the DSA ticket to apt-get install vpim. when did you file this ticket? cheers, Holger signature.asc Description: This is a digitally signed message part.
Bug#776926: openafs-modules-dkms: fails to build module for linux-headers-3.16.0-4-amd64: error: 'struct dentry' has no member named 'd_alias'
Package: openafs-modules-dkms Version: 1.6.10-3 Severity: serious Justification: fails to build from source User: debian...@lists.debian.org Usertags: piuparts openafs-modules-dkms fails to build a module for the current kernel in sid: Selecting previously unselected package openafs-modules-dkms. (Reading database ... 45386 files and directories currently installed.) Preparing to unpack .../openafs-modules-dkms_1.6.10-3_all.deb ... Unpacking openafs-modules-dkms (1.6.10-3) ... Setting up openafs-modules-dkms (1.6.10-3) ... Loading new openafs-1.6.10 DKMS files... First Installation: checking all kernels... dpkg: warning: version '*-*' has bad syntax: version number does not start with digit It is likely that 3.16.0-4-amd64 belongs to a chroot's host Building initial module for 3.16.0-4-amd64 Error! Bad return status for module build on kernel: 3.16.0-4-amd64 (x86_64) Consult /var/lib/dkms/openafs/1.6.10/build/make.log for more information. make.olg ends with CC [M] /var/lib/dkms/openafs/1.6.10/build/src/libafs/MODLOAD-3.16.0-4-amd64-SP/afs_daemons.o /var/lib/dkms/openafs/1.6.10/build/src/libafs/MODLOAD-3.16.0-4-amd64-SP/afs_daemons.c: In function 'afs_CheckRootVolume': /var/lib/dkms/openafs/1.6.10/build/src/libafs/MODLOAD-3.16.0-4-amd64-SP/afs_daemons.c:403:24: error: 'struct dentry' has no member named 'd_alias' list_del_init(dp-d_alias); ^ /var/lib/dkms/openafs/1.6.10/build/src/libafs/MODLOAD-3.16.0-4-amd64-SP/afs_daemons.c:404:19: error: 'struct dentry' has no member named 'd_alias' list_add(dp-d_alias, (AFSTOV(vcp)-i_dentry)); ^ /var/lib/dkms/openafs/1.6.10/build/src/libafs/MODLOAD-3.16.0-4-amd64-SP/afs_daemons.c:404:7: warning: passing argument 2 of 'list_add' from incompatible pointer type [enabled by default] list_add(dp-d_alias, (AFSTOV(vcp)-i_dentry)); ^ In file included from /usr/src/linux-headers-3.16.0-4-common/include/linux/wait.h:6:0, from /var/lib/dkms/openafs/1.6.10/build/src/afs/sysincludes.h:124, from /var/lib/dkms/openafs/1.6.10/build/src/libafs/MODLOAD-3.16.0-4-amd64-SP/afs_daemons.c:19: /usr/src/linux-headers-3.16.0-4-common/include/linux/list.h:60:20: note: expected 'struct list_head *' but argument is of type 'struct hlist_head *' static inline void list_add(struct list_head *new, struct list_head *head) ^ /usr/src/linux-headers-3.16.0-4-common/scripts/Makefile.build:262: recipe for target '/var/lib/dkms/openafs/1.6.10/build/src/libafs/MODLOAD-3.16.0-4-amd64-SP/afs_daemons.o' failed make[6]: *** [/var/lib/dkms/openafs/1.6.10/build/src/libafs/MODLOAD-3.16.0-4-amd64-SP/afs_daemons.o] Error 1 /usr/src/linux-headers-3.16.0-4-common/Makefile:1350: recipe for target '_module_/var/lib/dkms/openafs/1.6.10/build/src/libafs/MODLOAD-3.16.0-4-amd64-SP' failed make[5]: *** [_module_/var/lib/dkms/openafs/1.6.10/build/src/libafs/MODLOAD-3.16.0-4-amd64-SP] Error 2 Makefile:181: recipe for target 'sub-make' failed make[4]: *** [sub-make] Error 2 Makefile:8: recipe for target 'all' failed make[3]: *** [all] Error 2 make[3]: Leaving directory '/usr/src/linux-headers-3.16.0-4-amd64' FAILURE: make exit code 2 Makefile.afs:241: recipe for target 'openafs.ko' failed make[2]: *** [openafs.ko] Error 1 make[2]: Leaving directory '/var/lib/dkms/openafs/1.6.10/build/src/libafs/MODLOAD-3.16.0-4-amd64-SP' Makefile:138: recipe for target 'linux_compdirs' failed make[1]: *** [linux_compdirs] Error 2 make[1]: Leaving directory '/var/lib/dkms/openafs/1.6.10/build/src/libafs' Makefile:13: recipe for target 'all' failed make: *** [all] Error 2 Andreas DKMS make.log for openafs-1.6.10 for kernel 3.16.0-4-amd64 (x86_64) Tue Feb 3 11:04:47 UTC 2015 checking for a BSD-compatible install... /usr/bin/install -c checking whether build environment is sane... yes /var/lib/dkms/openafs/1.6.10/build/build-tools/missing: Unknown `--is-lightweight' option Try `/var/lib/dkms/openafs/1.6.10/build/build-tools/missing --help' for more information configure: WARNING: 'missing' script is too old or missing checking for a thread-safe mkdir -p... /bin/mkdir -p checking for gawk... no checking for mawk... mawk checking whether make sets $(MAKE)... yes checking whether make supports nested variables... yes checking for gcc... gcc checking whether the C compiler works... yes checking for C compiler default output file name... a.out checking for suffix of executables... checking whether we are cross compiling... no checking for suffix of object files... o checking whether we are using the GNU C compiler... yes checking whether gcc accepts -g... yes checking for gcc option to accept ISO C89... none needed checking whether gcc understands -c and -o together... yes checking for style of include used by make... GNU checking dependency style of gcc... none checking build system type... x86_64-unknown-linux-gnu checking host system type... x86_64-unknown-linux-gnu checking how to run the C
Bug#768133: evince won't print landscape PDFs
Hi all, 2015-02-03 2:52 GMT+01:00 Chris Kuehl cku...@ocf.berkeley.edu: Hi all, Just wanted to provide some additional context on this bug. The current version of evince in jessie/sid will not print landscape PDFs (at least, none that I've tried). Instead, the pages print blank. It's possible to print the pages by un-checking ``Auto-rotate and center'' (which is checked by default), but as expected, the page will be oriented and positioned incorrectly, making the print basically unusable. I haven't found a way to workaround the bug without resorting to something like Okular or command-line tools. An evince developer (Carlos Garcia Campos) states on 2015-01-28 in the upstream bug [1] [2] [3]: Having a proper fix for this is taking more time than I expected, so I've just reverted the patch that introduced this regression in both branches until we find a proper solution in both Evince and GTK+. This is now fixed, use bug #734788 for new discussions or patches to the centering option when having a manual scale. There is also a Fedora bug report [4], where the maintainer reverted the commit which caused it. So, it seems the best step forward is to follow upstream and Fedora, and revert this commit. I've attached a debdiff which reverts it, and tested it in our busy computer lab for the past few days successfully. Is there any opposition to marking this bug as release-critical? I know it's late in the freeze, but I think PDF printing using the default PDF viewer on the default DE with the default settings should not be broken in jessie, especially since we have an easy fix by reverting the commit which caused it. I'm not sure the current severity is appropriate? I create another bug report [1] since there a more gtk applications affected and set it to grave. But it was drop down to important and not release critical [2]. As you write I think it is not a good idea to have a broken landscape printout with the default DE and Viewer in Debian Jessie. Samuel [1] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=771205 [2] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=771205#21 I'm happy to help with additional testing. Many thanks, Chris P.S. An easy way to test is to install `printer-driver-cups-pdf`, which will show the behavior. ``Print to PDF'' in Evince seems to not. There is a PDF attached to Samuel's first email in this thread which can be used as a test case. [1] Upstream bug report https://bugzilla.gnome.org/show_bug.cgi?id=739723 [2] Upstream revert commit: https://git.gnome.org/browse/evince/commit/?id=69b474fce1a87a0839e1f541f1297492e47c7c31 [3] Commit which was blamed and reverted by upstream and Fedora: https://git.gnome.org/browse/evince/commit/?id=ae7a5715131613955a37419b5da1d6d9f3c1cb1d [4] Fedora bug report: https://git.gnome.org/browse/evince/commit/?id=69b474fce1a87a0839e1f541f1297492e47c7c31
Bug#769569: Problem still exists on kernel 3.18
Hello, I just want to inform you that this problem still exists on kernel 3.18 (linux-image-3.18.0-trunk-amd64). Thus it's safe to say this is most likely X or even GNOME bug. Please inform me if you have any additional ideas on how to isolate the origin of this problem. Or if you want me to do any additional debugging. Looking forward to your reply, Adnan
Bug#776912: debootstrap circular depends/pre-depends between sytemd-sysv and systemd
Am 03.02.2015 um 11:59 schrieb Ansgar Burchardt: Hi Marin, please remember to also send replies to the bug report (I've not forwarded your message). The debootstrap log looks a bit more scary than I think it should, but I'll take a look at only the systemd error: On 02/03/2015 11:22 AM, Martin Wuertele wrote: Setting up systemd (215-10) ... Failed to open /dev/urandom: Function not implemented dpkg: error processing package systemd (--configure): subprocess installed post-installation script returned error exit status 1 I think this comes from systemd-machine-id-setup which is called in systemd's postinst: core/machine-id-setup.c:140 (in generate): r = sd_id128_randomize(buf); libsystemd/sd-id128/sd-id128.c:216: r = dev_urandom(t, sizeof(t)); shared/util.c:2371-2373: fd = open(/dev/urandom, O_RDONLY|O_CLOEXEC|O_NOCTTY); if (fd 0) return errno == ENOENT ? -ENOSYS : -errno; To make sure, could you try running systemd-machine-id-setup in the chroot? And check if /dev/urandom is present in the chroot? I might be missing something obvious, but where is the supposed dependency cycle between systemd-sysv and systemd? -- 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#768269: appdata-tools and appstream-util: error when trying to install together
Followup-For: Bug #768269 Control: found -1 0.3.2-2 Hi, during a test with piuparts I noticed your package fails to upgrade from 'sid' to 'experimental'. It installed fine in 'sid', then the upgrade to 'experimental' fails because it tries to overwrite other packages files without declaring a Breaks+Replaces relation. See policy 7.6 at https://www.debian.org/doc/debian-policy/ch-relationships.html#s-replaces From the attached log (scroll to the bottom...): Selecting previously unselected package appstream-util. Preparing to unpack .../appstream-util_0.3.2-2_amd64.deb ... Unpacking appstream-util (0.3.2-2) ... dpkg: error processing archive /var/cache/apt/archives/appstream-util_0.3.2-2_amd64.deb (--unpack): trying to overwrite '/usr/bin/appdata-validate', which is also in package appdata-tools 0.1.7-3 Preparing to unpack .../appdata-tools_0.3.2-2_all.deb ... Unpacking appdata-tools (0.3.2-2) over (0.1.7-3) ... Processing triggers for libgdk-pixbuf2.0-0:amd64 (2.31.1-2+b1) ... Processing triggers for libglib2.0-0:amd64 (2.42.1-1) ... Errors were encountered while processing: /var/cache/apt/archives/appstream-util_0.3.2-2_amd64.deb cheers, Andreas appdata-tools_0.3.2-2.log.gz Description: application/gzip
Bug#776912: debootstrap circular depends/pre-depends between sytemd-sysv and systemd
Control: retitle -1 systemd: missing /dev/urandom makes postinst fail Hi, On 02/03/2015 11:59 AM, Ansgar Burchardt wrote: On 02/03/2015 11:22 AM, Martin Wuertele wrote: Setting up systemd (215-10) ... Failed to open /dev/urandom: Function not implemented dpkg: error processing package systemd (--configure): subprocess installed post-installation script returned error exit status 1 I think this comes from systemd-machine-id-setup which is called in systemd's postinst: core/machine-id-setup.c:140 (in generate): r = sd_id128_randomize(buf); libsystemd/sd-id128/sd-id128.c:216: r = dev_urandom(t, sizeof(t)); shared/util.c:2371-2373: fd = open(/dev/urandom, O_RDONLY|O_CLOEXEC|O_NOCTTY); if (fd 0) return errno == ENOENT ? -ENOSYS : -errno; To make sure, could you try running systemd-machine-id-setup in the chroot? And check if /dev/urandom is present in the chroot? Martin confirmed that systemd tried to open /dev/urandom which is not present on purpose and that the source seems to be systemd-machine-id-setup (but did not CC the bug report). Ansgar -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#776959: linux-image-3.16.0-4-amd64: [regression] sd card reader in retina macbook pro no longer working
On Tue, Feb 3, 2015 at 7:58 PM, Ben Hutchings b...@decadent.org.uk wrote: Control: tag -1 important On Tue, 2015-02-03 at 15:39 +, lkcl wrote: Package: src:linux Version: 3.16.7-ckt2-1 Severity: important after upgrading from 3.13 where the built-in sd card worked perfectly, there is no longer even any kernel events or anything remotely indicating that the apple sd card reader is recognised. i note that there is a similar bug https://lists.debian.org/debian-kernel/2014/09/msg00170.html however this is for an entirely different laptop. [...] And a different device ID. yeh. Which driver is being used in 3.13? well... as rebooting the machine to find out would be too disruptive (termination of dozens of long-running programs) i can't directly find out immediately, so i did some investigation. according to these: https://usb-ids.gowdy.us/read/UD/05ac https://wiki.debian.org/InstallingDebianOn/Apple/MacBookPro/11-1#lsusb it should be 0a5c:8406 (i have the same hardware as on the debian page) but what's startling is that the expected usb device is... *entirely missing* from lsusb. i mean it's _gone_. so this is going to have to be something that i will need to schedule a reboot when it is convenient to do so, and find out if it reappears under 3.13. but before i do that, what i'm doing to do is an s2disk, and make sure that the power adaptor is not plugged in at the time (it causes *massive* EMI spiking which causes me to get electric shocks off of the aluminium casing if i touch a well-earthed ground point, and causes the logs to be filled up every second with SATA hard resets). give me a few minutes i'll make a report with the findings. l. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#632255: kmail: Kmail does not start properly or close/minimise to the system tray
On Sun, 11 Jan 2015 15:28:17 +0100 Sandro =?ISO-8859-1?Q?Knau=DF?= b...@sandroknauss.de wrote: tag 632255 +moreinfo thanks For my sins I forgot about this... It is working okay in current stable and testing. I can't remember how long I had to put up with it, but it's okay now... Hey, I'm using curent version 4:4.14.2. When you start KMail it starts to run automatically on login from a saved session, you can see it in ps aux but nothing appears on the screen. kmail ( or better say i use kontact) it starts with the session and is visible und usable for me out of the box. I don't have to kill it before being usable. If you close the application it vanishes - it doesn't close to the system tray like it use to, but it is still running, which you can veryify with ps. If I close the application is closes to system tray ( still runnig) and can be opend from the system tray again. So I would tag it as WORKSFORME. Is it still an issue for you? Regads, sandro -- Adam Trickett Overton, HANTS, UK This would of course be likely to trigger a real constitutional crisis, but as this Government has done so much to destroy the constitution already, it seems only reasonable for other people to be allowed to join in. -- John Lettice, The Register 2006-01-17 -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#776996: [Pkg-xfce-devel] Bug#776996: xfce4-session: wallpaper does not display until refreshed
control: tag -1 unreproducible moreinfo On mar., 2015-02-03 at 16:45 -0500, Benjamin Kaduk wrote: After upgrading from 4.10.1-9 to 4.10.1-10 (I think), along with other updates in sid, when I run 'startx' I am presented with a mostly black screen. I have the menu bar at the top and the launcher buttons at the bottom of the screen, as well as any saved windows that were restarted. The wallpaper is not rendered until I refresh the display, for example by moving a window in front of it. Doing so leaves the wallpaper visible in the portions of the screen that were once covered by the window being moved. The icons which are on the desktop are not rendered; that part of the screen is also black. This is not a particular usability issue, but I figured I would report my experience just in case. There appears to be something on a timeout (perhaps a minute or two in length) that eventually causes the entire screen to be refreshed, or at least it makes the black parts of the screen that should be wallpaper/desktop get rendered properly. That doesn't look at all related to xfce4-session. The desktop is supposedly rendered by xfdesktop4, so you might want to investigate there, but without knowing what actually changed during that update, it's impossible to investigate. Also, xfce4-session 4.10.1-10 is in sid since Jan 11 and testing since Jan 17 so either your don't upgrade regularly, or it's something else. Regards, -- Yves-Alexis signature.asc Description: This is a digitally signed message part
Bug#776901: python-django-extensions: new upstream version available and python3 support
On 3 February 2015 at 13:46, Brian May b...@debian.org wrote: Please can you package the latest upstream version (1.5.0), and also please can you package the Python 3 package (upstream supports Python 3). Do you have any objections to making this package maintained by the Debian Python Modules team? Thanks -- Brian May b...@debian.org
Bug#776996: [Pkg-xfce-devel] Bug#776996: xfce4-session: wallpaper does not display until refreshed
On Tue, 3 Feb 2015, Yves-Alexis Perez wrote: control: tag -1 unreproducible moreinfo Thanks. I rather suspect that this will get closed due to lack of energy on my part, but we'll see... That doesn't look at all related to xfce4-session. The desktop is supposedly rendered by xfdesktop4, so you might want to investigate there, but without knowing what actually changed during that update, it's impossible to investigate. Thank you for the pointer; I'm sorry I guessed wrong. (Would reporting against the xfce4 metapackage have been a better or worse idea, for future reference?) Also, xfce4-session 4.10.1-10 is in sid since Jan 11 and testing since Jan 17 so either your don't upgrade regularly, or it's something else. Now that you mention it, I bet I did not actually restart X on the preceding several updates, so the listed versions are unlikely to be the relevant ones. I will see if I can dig up some useful information, but feel free to close in a few weeks if nothing shows up. -Ben -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#770016: Clarify network access for building packages in main
On Tue, Feb 03, 2015 at 04:27:56PM +0100, Lucas Nussbaum wrote: yeah, I second this version: + For packages in the main archive, no required targets + may attempt network access. even if I would prefer something that did not restrict to main, and said something like: No packages may rely on network access to be available during the execution of required targets. I have no problem removing the restriction to the main archive. (non free is always an exception to policy anyway). However as I understand, your wording still allow to use network access if it is available (which I find dangerous). Maybe The execution of a required target must not attempt network access. Henrique, did Lucas answers about the archive rebuild address your objections ? Cheers, -- Bill. ballo...@debian.org Imagine a large red swirl here. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#776982: pancakes all across the sky
Package: bugs.debian.org Control: retitle -1 add summit.debconf.org pseudo-package -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#776997: systemd-sysv's shutdown can not handle all parameters / arguments
Package: systemd-sysv Version: 215-10 Severity: important Dear Maintainer, *** Reporter, please consider answering these questions, where appropriate *** * What led up to the situation? Try to force a fsck after reboot by typing # shutdown -r -F now (is valid with normal shutdown and described in manpage) * What was the outcome of this action? systemctl told me it is an unhandled option: Code should not be reached 'Unhandled option' at .../src/systemctl/systemctl.c:6316, function shutdown_parse_argv(). Aborting. Abgebrochen * What outcome did you expect instead? System should reboot and perform a fsck without any errors ! -- System Information: Debian Release: 8.0 APT prefers testing-updates APT policy: (500, 'testing-updates'), (500, 'testing') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.16.0-4-amd64 (SMP w/4 CPU cores) Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages systemd-sysv depends on: ii systemd 215-10 systemd-sysv recommends no packages. systemd-sysv suggests no packages. -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#776913: flightgear-data-all: new upstream version needed by flightgear/experimental
On 2015-02-03 14:14, Rebecca N. Palmer wrote: If you urgently want 3.2, dropping the 3.2 flightgear-data upstream into the 3.0.0-1 (not -2) packaging will probably work, but this has not been tested. The only thing I needed was this bug report, so that piuparts can mark the uninstallable flightgear package in experimental as that's a known bug. Andreas -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#750697: PEAR: Timestamp in registry files prevent reproducible builds
user reproducible-bui...@lists.alioth.debian.org usertags toolchain thanks This can be done by changing the _lastmodified element of the array before serializing. See also: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=776138 Also, I think this bug should be filed against the main PHP/PEAR package, not pkg-php-tools as that's where the serialisation happens. I went to patch the former but it became a little invasive; multiple places to change etc. Regards, -- ,''`. : :' : Chris Lamb `. `'` la...@debian.org / chris-lamb.co.uk `- -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#776969: tcpwatch-httpproxy: please make the build reproducible
Source: tcpwatch-httpproxy Version: 1.3b-3 Severity: wishlist Tags: patch User: reproducible-bui...@lists.alioth.debian.org Usertags: timestamps X-Debbugs-Cc: reproducible-bui...@lists.alioth.debian.org Hi, While working on the reproducible builds effort [1], we have noticed that tcpwatch-httpproxy could not be built reproducibly. The attached patch removes timestamps from the build system. Once applied, tcpwatch-httpproxy can be built reproducibly in our current experimental framework. [1]: https://wiki.debian.org/ReproducibleBuilds Regards, -- ,''`. : :' : Chris Lamb `. `'` la...@debian.org / chris-lamb.co.uk `- diff -urNad tcpwatch-httpproxy.orig/tcpwatch-httpproxy-1.3b/debian/rules tcpwatch-httpproxy/tcpwatch-httpproxy-1.3b/debian/rules --- tcpwatch-httpproxy.orig/tcpwatch-httpproxy-1.3b/debian/rules 2015-02-03 16:41:09.847226467 + +++ tcpwatch-httpproxy/tcpwatch-httpproxy-1.3b/debian/rules 2015-02-03 16:42:47.715498699 + @@ -27,7 +27,7 @@ install -m 644 debian/copyright $(I_DIR)/share/doc/$(PACKAGE) #install -m 644 debian/changelog $(I_DIR)/share/doc/$(PACKAGE)/changelog.Debian # gzip -9 $(I_DIR)/share/doc/$(PACKAGE)/changelog $(I_DIR)/share/doc/$(PACKAGE)/changelog.Debian - gzip -9 $(I_DIR)/share/doc/$(PACKAGE)/changelog + gzip -9n $(I_DIR)/share/doc/$(PACKAGE)/changelog dh_installman debian/*.1 unpack: unpack-stamp
Bug#776477: tomcat7: fails to switch from tomcat6 to tomcat7 on upgrades
Le 03/02/2015 17:37, Andreas Beckmann a écrit : now that it migrated, tomcat6 removal has smoothened this upgrade path, thus closing. Great, thank you for confirming Andreas. Emmanuel Bourg -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#776968: uruk: please make the build reproducible
Hi Chris, Thanks, will get to it. Will be fixed in next upload. (In the mean time, feel free to NMU; I like reproducable builds.) Bye, Joost On Tue, Feb 03, 2015 at 04:41:44PM +, Chris Lamb wrote: Source: uruk Version: 20140627-1 Severity: wishlist Tags: patch User: reproducible-bui...@lists.alioth.debian.org Usertags: timestamps X-Debbugs-Cc: reproducible-bui...@lists.alioth.debian.org Hi, While working on the reproducible builds effort [1], we have noticed that uruk could not be built reproducibly. The attached patch removes timestamps from the build system. Once applied, uruk can be built reproducibly in our current experimental framework. [1]: https://wiki.debian.org/ReproducibleBuilds Regards, -- ,''`. : :' : Chris Lamb `. `'` la...@debian.org / chris-lamb.co.uk `- diff -urNad uruk.orig/uruk-20140627/debian/rules uruk/uruk-20140627/debian/rules --- uruk.orig/uruk-20140627/debian/rules 2015-02-03 16:39:59.872172541 + +++ uruk/uruk-20140627/debian/rules 2015-02-03 16:40:26.965354892 + @@ -70,8 +70,8 @@ cp -a debian/README $(docdir)/README.Debian cp -a debian/TODO $(docdir)/TODO.Debian cp -a ChangeLog $(docdir)/changelog - cd $(docdir) gzip -9 changelog changelog.Debian ChangeLog.2003 NEWS.Debian - gzip -r9 debian/$(package)/usr/share/man + cd $(docdir) gzip -9n changelog changelog.Debian ChangeLog.2003 NEWS.Debian + gzip -r9n debian/$(package)/usr/share/man mkdir debian/$(package)/DEBIAN # # generate md5sums. pathnames should not have leading /. # # conffiles should be excluded. for now, assume conffiles are precisely -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#724344: ITP: bdsync -- bdsync is a fast block device synchronizing tool
On Thu, 09 Oct 2014 12:06:07 +0200 (CEST) maxigas maxi...@anargeek.net
wrote:
From: intrigeri intrig...@debian.org
Subject: Re: Bug#724344: ITP: bdsync -- bdsync is a fast block device
synchronizing tool
Date: Thu, 09 Oct 2014 11:50:49 +0200
Hi maxigas,
did you really intend to file this bug as an ITP (intent to package),
or instead as a RFP (request for package)?
yes, i actually made the package. but then i found out about the licence
exception which has to be done for openssl and decided to try porting the
software to gnutls. afair it uses only a single function call to the crypto
library.
then my patch did not work and i am still looking for somebody with enough C
knowledge to help fixing it. :)
--
maxigas, kiberpunk
FA00 8129 13E9 2617 C614 0901 7879 63BC 287E D166
http://research.metatron.ai/
People the switches!
Hi maxigas,
I was searching for bdsync package in Debian and stumbled across this
bug report.
I created a patch to switch from openssl to gnutls. Following authors
simple building approach I created a new make target named
bdsync-gnutls which builds the alternative version. Migrating the
project to autotools building system might be a better solution but I
believe it is a bit too intrusive.
The gnutls version of bdsync is binary compatible with openssl version.
You could use gnutls version on local machine and openssl version on
remote machine or vice versa.
If you need any more help or have any suggestions please let me know.
Modified bdsync version is also available on github:
https://github.com/fln/bdsync
I hope this patch will help you to create bdsync Debian package.
--
Fln
From 768d7ecbb95c46af88c3bdad94193d71ea281815 Mon Sep 17 00:00:00 2001
From: Julius Kriukas git...@fln.lt
Date: Tue, 3 Feb 2015 18:10:40 +0200
Subject: [PATCH] libgnutls as alternative to openssl
---
Makefile | 3 ++
bdsync.c | 143 +++
2 files changed, 119 insertions(+), 27 deletions(-)
diff --git a/Makefile b/Makefile
index 50084a5..36ecbac 100644
--- a/Makefile
+++ b/Makefile
@@ -1,5 +1,8 @@
bdsync: bdsync.c
cc -Wall -g -o bdsync bdsync.c -lcrypto
+bdsync-gnutls: bdsync.c
+ cc -Wall -g -o $@ $ -lgnutls -DHAVE_GNUTLS
+
tar:
./maketar.sh
diff --git a/bdsync.c b/bdsync.c
index 35cf7c7..bf1a26c 100644
--- a/bdsync.c
+++ b/bdsync.c
@@ -57,7 +57,12 @@
#include unistd.h
#include getopt.h
#include string.h
-#include openssl/evp.h
+#ifdef HAVE_GNUTLS
+ #include gnutls/gnutls.h
+ #include gnutls/crypto.h
+#else
+ #include openssl/evp.h
+#endif
#include netdb.h
#include sys/socket.h
#include stdarg.h
@@ -184,23 +189,38 @@ void verbose (int level, char * format, ...)
struct cs_state {
char *name;
off64_tnxtpos;
+#ifdef HAVE_GNUTLS
+gnutls_hash_hd_t ctx;
+#else
EVP_MD_CTX *ctx;
+#endif
inthashsize;
};
struct cs_state *init_checksum (const char *checksum)
{
+#ifdef HAVE_GNUTLS
+gnutls_digest_algorithm_t md;
+gnutls_hash_hd_t ctx;
+#else
const EVP_MD*md;
EVP_MD_CTX *ctx;
+#endif
int hs;
struct cs_state *state;
verbose (2, init_checksum: checksum: %s\n, checksum);
+#ifdef HAVE_GNUTLS
+md = gnutls_digest_get_id (checksum);
+hs = gnutls_hash_get_len (md);
+gnutls_hash_init(ctx, md);
+#else
md = EVP_get_digestbyname (checksum);
hs = EVP_MD_size (md);
ctx = EVP_MD_CTX_create();
EVP_DigestInit_ex (ctx, md, NULL);
+#endif
if (!md) {
verbose (0, Bad checksum %s\n, checksum);
exit (1);
@@ -254,8 +274,11 @@ int update_checksum (struct cs_state *state, off64_t pos, int fd, off64_t len, u
, (long long)nrd, (int)blen);
exit (1);
}
-
+#ifdef HAVE_GNUTLS
+gnutls_hash(state-ctx, fbuf, blen);
+#else
EVP_DigestUpdate (state-ctx, fbuf, blen);
+#endif
state-nxtpos += blen;
len -= blen;
@@ -274,7 +297,11 @@ int update_checksum (struct cs_state *state, off64_t pos, int fd, off64_t len, u
verbose (3, update_checksum: checksum: pos=%lld, len=%d\n
, (long long) state-nxtpos, len);
+#ifdef HAVE_GNUTLS
+gnutls_hash(state-ctx, buf, len);
+#else
EVP_DigestUpdate (state-ctx, buf, len);
+#endif
state-nxtpos += len;
@@ -1085,8 +1112,11 @@ const char *get_string (char **msgbuf, size_t *msglen)
return ret;
};
-
+#ifdef HAVE_GNUTLS
+int parse_digests (char *msgbuf, size_t msglen, int *saltsize, unsigned char **salt, gnutls_digest_algorithm_t *dg_md, struct cs_state **cs_state)
+#else
int parse_digests (char *msgbuf, size_t msglen, int *saltsize, unsigned char **salt, const EVP_MD **dg_md, struct cs_state **cs_state)
+#endif
{
char *tmp;
const char *digest, *checksum;
@@ -1118,7 +1148,11 @@ int parse_digests (char *msgbuf, size_t msglen, int *saltsize, unsigned char **s
exit (1);
}
Bug#776960: gnome-themes: Clearlooks No Color
Package: gnome-themes Version: 2.30.2-1 Severity: minor Dear Maintainer, For a while now on my Debian Testing machine clearlooks has been missing its usual blue color on the top window border. Now it is white. I have actually been experiencing this bug since last summer, but at first it was switching between blue and white. Now it is always white. I thought others might have been experiencing this bug as well and with time it would have been fixed. Thanks, Josh -- System Information: Debian Release: 8.0 APT prefers testing-updates APT policy: (500, 'testing-updates'), (500, 'testing') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.16.0-4-amd64 (SMP w/8 CPU cores) Locale: LANG=es_CO.utf8, LC_CTYPE=es_CO.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages gnome-themes depends on: ii gtk2-engines 1:2.20.2-3 ii gtk2-engines-pixbuf 2.24.25-1 ii librsvg2-common 2.40.5-1 Versions of packages gnome-themes recommends: ii dmz-cursor-theme 0.4.4 Versions of packages gnome-themes suggests: pn gnome-themes-extras none -- no debconf information
Bug#776961: linux-image-3.16.0-4-amd64: [regression] pulseaudio not starting up after installing linux-image-3.16
Package: src:linux
Version: 3.16.7-ckt2-1
Severity: important
for a system which had a complex (working) audio setup with the 3.13 kernel,
skype can no longer see any devices with pulseaudio - at all. checking
for the pulseaudio daemon, it is no longer started up.
no other packages were installed, upgraded or modified as part of the
linux kernel upgrade from 3.13 to 3.16.
-- Package-specific info:
** Version:
Linux version 3.16.0-4-amd64 (debian-ker...@lists.debian.org) (gcc version
4.8.3 (Debian 4.8.3-16) ) #1 SMP Debian 3.16.7-ckt2-1 (2014-12-08)
** Command line:
BOOT_IMAGE=/boot/vmlinuz-3.16.0-4-amd64
root=UUID=2b2a5854-dfd8-444c-87d0-a3c6eb140939 ro quiet
** Tainted: PBWO (4641)
* Proprietary module has been loaded.
* System has hit bad_page.
* Taint on warning.
* Out-of-tree module has been loaded.
** Kernel log:
[916674.465756] ata1: hard resetting link
[916675.190264] ata1: SATA link up 1.5 Gbps (SStatus 113 SControl 310)
[916675.190730] ata1.00: unexpected _GTF length (8)
[916675.191273] ata1.00: unexpected _GTF length (8)
[916675.191338] ata1.00: configured for UDMA/33
[916675.191403] ata1: EH complete
[916689.005059] ata1.00: exception Emask 0x10 SAct 0x20 SErr 0x404
action 0xe frozen
[916689.005063] ata1.00: irq_stat 0x8040, connection status changed
[916689.005066] ata1: SError: { CommWake DevExch }
[916689.005069] ata1.00: failed command: READ FPDMA QUEUED
[916689.005074] ata1.00: cmd 60/08:a8:00:4a:a5/00:00:00:00:00/40 tag 21 ncq
4096 in
[916689.005074] res 40/00:a4:00:10:78/00:00:0c:00:00/40 Emask 0x10
(ATA bus error)
[916689.005076] ata1.00: status: { DRDY }
[916689.005080] ata1: hard resetting link
[916689.729644] ata1: SATA link up 1.5 Gbps (SStatus 113 SControl 310)
[916689.730082] ata1.00: unexpected _GTF length (8)
[916689.730600] ata1.00: unexpected _GTF length (8)
[916689.730666] ata1.00: configured for UDMA/33
[916689.730717] ata1: EH complete
[916787.493843] usbcore: registered new interface driver rtsx_usb
** Model information
sys_vendor: Apple Inc.
product_name: MacBookPro11,1
product_version: 1.0
chassis_vendor: Apple Inc.
chassis_version: Mac-189A3D4F975D5FFC
bios_vendor: Apple Inc.
bios_version: MBP111.88Z.0138.B03.1310291227
board_vendor: Apple Inc.
board_name: Mac-189A3D4F975D5FFC
board_version: MacBookPro11,1
** Loaded modules:
rtsx_usb
wl(PO)
cp210x
ftdi_sio
snd_usb_audio
snd_usbmidi_lib
snd_seq_midi
snd_seq_midi_event
snd_rawmidi
cfg80211
sr9700
dm9601
usbnet
mii
snd_hrtimer
snd_seq_dummy
rfcomm
bnep
cpufreq_powersave
cpufreq_stats
cpufreq_userspace
cpufreq_conservative
binfmt_misc
uinput
nfsd
auth_rpcgss
oid_registry
nfs_acl
nfs
lockd
fscache
sunrpc
tun
nls_utf8
nls_cp437
vfat
fat
fuse
firewire_sbp2
firewire_core
crc_itu_t
loop
kaweth
ecb
btusb
bluetooth
6lowpan_iphc
rfkill
iTCO_wdt
iTCO_vendor_support
hid_generic
usbserial
wacom
hid_apple
joydev
usbhid
hid
bcm5974
x86_pkg_temp_thermal
intel_powerclamp
intel_rapl
coretemp
efi_pstore
kvm_intel
kvm
crct10dif_pclmul
crc32_pclmul
ghash_clmulni_intel
evdev
applesmc
input_polldev
aesni_intel
aes_x86_64
lrw
gf128mul
glue_helper
ablk_helper
cryptd
efivars
sbs
i2c_i801
lpc_ich
mfd_core
snd_hda_codec_cirrus
snd_hda_codec_generic
sbshc
snd_hda_intel
snd_hda_controller
snd_hda_codec
i915
snd_hwdep
snd_pcm
snd_seq
snd_seq_device
snd_timer
video
apple_bl
battery
drm_kms_helper
drm
i2c_algo_bit
i2c_core
ac
snd
mei_me
processor
mei
thermal_sys
soundcore
button
ext4
crc16
mbcache
jbd2
md_mod
dm_mirror
dm_region_hash
dm_log
dm_mod
sg
sd_mod
crc_t10dif
crct10dif_common
usb_storage
crc32c_intel
ahci
libahci
libata
scsi_mod
xhci_hcd
usbcore
usb_common
** Network interface configuration:
auto lo
iface lo inet loopback
allow-hotplug eth0
iface eth0 inet dhcp
auto mytap
iface mytap inet static
address 10.0.3.1
netmask 255.255.255.0
vde2-switch -t mytap
allow-hotplug usb0
iface usb0 inet static
address 10.20.0.1
netmask 255.255.255.0
** Network status:
*** IP interfaces and addresses:
1: lo: LOOPBACK,UP,LOWER_UP mtu 65536 qdisc noqueue state UNKNOWN group
default
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
inet 127.0.0.1/8 scope host lo
valid_lft forever preferred_lft forever
inet6 ::1/128 scope host
valid_lft forever preferred_lft forever
2: mytap: BROADCAST,MULTICAST,UP,LOWER_UP mtu 1500 qdisc pfifo_fast state UP
group default qlen 500
link/ether 32:d8:e1:96:1f:94 brd ff:ff:ff:ff:ff:ff
inet 10.0.3.1/24 brd 10.0.3.255 scope global mytap
valid_lft forever preferred_lft forever
inet6 fe80::30d8:e1ff:fe96:1f94/64 scope link
valid_lft forever preferred_lft forever
5: tun0: POINTOPOINT,MULTICAST,NOARP,UP,LOWER_UP mtu 1500 qdisc pfifo_fast
state UNKNOWN group default qlen 100
link/none
inet 10.8.0.199 peer 10.8.0.200/32 scope global tun0
valid_lft forever preferred_lft forever
6: tun1: POINTOPOINT,MULTICAST,NOARP,UP,LOWER_UP mtu 1500 qdisc pfifo_fast
state UNKNOWN group default qlen 100
Bug#776965: llvm-toolchain-3.6: FTBFS on hurd-i386
On 03/02/2015 17:37, Svante Signell wrote: Source: llvm-toolchain-3.6 Version: 1:3.6~+rc2-1 Severity: important Tags: patch User: debian-h...@lists.debian.org Usertags: hurd Hello, Currently llvmtoolchain-3.6 (~+rc1-1 and ~+rc2-1) fails to build from source due to usage of a reserved identifier in C/C++11/POSIX.1, see e.g.: Oh, excellent, I tried in the past but the undef failed. I am going to upload a new -2 in the next few hours. Thanks! S -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#776974: debian-installer: Did not detect Intel RST RAID Disk
Package: installation-reports Boot method: USB stick Image version: http://cdimage.debian.org/cdimage/jessie_di_rc1/amd64/iso-cd/debian-jessie-DI-rc1-amd64-netinst.iso Date: Tue Feb 3 10:41:43 CST 2015 Machine: Supermicro motherboard with Intel RST Processor: Intel Xeon E5620 Memory: 100 GB Partitions: Never got that far Base System Installation Checklist: [O] = OK, [E] = Error (please elaborate below), [ ] = didn't try it Initial boot: [O] Detect network card:[O] Configure network: [O] Detect CD: [O] Load installer modules: [O] Detect hard drives: [E] Partition hard drives: [ ] Install base system:[ ] Clock/timezone setup: [ ] User/password setup:[ ] Install tasks: [ ] Install boot loader:[ ] Overall install:[ ] Comments/Problems: The Intel RST RAID 5 Disk doesn't show up in the partition menu at all. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#776975: vmdebootstrap: default to armmp kernel variant on armhf.
Package: vmdebootstrap Version: 0.6-1 Severity: wishlist Tags: patch Thanks for maintaining vmdebootstrap! For Jessie systems at least, the default kernel for armhf should be set to armmp. Attached should be a patch to make this the default behavior, and a second patch to remove explicitly setting the kernel variant for several examples, which would be redundant. FWIW, cubietruck could probably default to linux-image-armmp-lpae rather than the default, though should be compatible with linux-image-armmp. live well, vagrant From 9e0f43722a54c2547d7b47bea01d9aa65f897ee7 Mon Sep 17 00:00:00 2001 From: Vagrant Cascadian vagr...@debian.org Date: Tue, 3 Feb 2015 08:54:28 -0800 Subject: [PATCH 1/2] Default to armmp kernel for armhf architecture. --- vmdebootstrap | 2 ++ 1 file changed, 2 insertions(+) diff --git a/vmdebootstrap b/vmdebootstrap index a9127ae..446fcaa 100755 --- a/vmdebootstrap +++ b/vmdebootstrap @@ -423,6 +423,8 @@ class VmDebootstrap(cliapp.Application): # pylint: disable=too-many-public-meth if not self.settings['no-kernel']: if self.settings['arch'] == 'i386': kernel_arch = '486' +elif self.settings['arch'] == 'armhf': +kernel_arch = 'armmp' else: kernel_arch = self.settings['arch'] kernel_image = 'linux-image-%s' % kernel_arch -- 2.1.4 From b771828b37b68913c00ba0d881a5d8f5ef6fb39f Mon Sep 17 00:00:00 2001 From: Vagrant Cascadian vagr...@debian.org Date: Tue, 3 Feb 2015 08:54:53 -0800 Subject: [PATCH 2/2] Drop calls to --no-kernel and --package for several armhf examples. --- examples/beagleboneblack.sh | 2 -- examples/cubietruck.sh | 2 -- examples/wandboard6q.sh | 2 -- 3 files changed, 6 deletions(-) diff --git a/examples/beagleboneblack.sh b/examples/beagleboneblack.sh index 7fd44b2..8fba046 100755 --- a/examples/beagleboneblack.sh +++ b/examples/beagleboneblack.sh @@ -13,9 +13,7 @@ sudo vmdebootstrap \ --enable-dhcp \ --configure-apt \ --no-extlinux \ - --no-kernel \ --package u-boot \ - --package linux-image-armmp \ --distribution sid \ --serial-console-command '/sbin/getty -L ttyO0 115200 vt100' \ --customize beagleboneblack-customise.sh \ diff --git a/examples/cubietruck.sh b/examples/cubietruck.sh index 395b032..f1c05e7 100755 --- a/examples/cubietruck.sh +++ b/examples/cubietruck.sh @@ -13,8 +13,6 @@ sudo vmdebootstrap \ --foreign /usr/bin/qemu-arm-static \ --enable-dhcp \ --configure-apt \ - --no-kernel \ - --package linux-image-armmp \ --distribution sid \ --serial-console-command /sbin/getty -L ttyS0 115200 vt100 \ --customize cubietruck-customise.sh \ diff --git a/examples/wandboard6q.sh b/examples/wandboard6q.sh index 38c05a7..ed064f3 100755 --- a/examples/wandboard6q.sh +++ b/examples/wandboard6q.sh @@ -19,8 +19,6 @@ sudo ./vmdebootstrap \ --configure-apt \ --no-extlinux \ --grub \ - --no-kernel \ - --package linux-image-armmp \ --distribution sid \ --serial-console-command /sbin/getty -L ttymxc0 115200 vt100 \ --customize ./examples/wandboard-customise.sh \ -- 2.1.4 -- System Information: Debian Release: 8.0 APT prefers testing APT policy: (500, 'testing'), (120, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386, armhf Kernel: Linux 3.16.0-4-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages vmdebootstrap depends on: ii debootstrap1.0.66 ii extlinux 3:6.03+dfsg-4 ii kpartx 0.5.0-5 ii mbr1.1.11-5+b1 ii parted 3.2-6 ii python 2.7.8-2 ii python-cliapp 1.20140719-1 ii python2.7 2.7.8-11 ii qemu-utils 1:2.1+dfsg-11 Versions of packages vmdebootstrap recommends: ii grub2-common 2.02~beta2-20 ii qemu-system 1:2.1+dfsg-11 ii qemu-user-static 1:2.1+dfsg-11 ii squashfs-tools1:4.2+20130409-2 Versions of packages vmdebootstrap suggests: pn u-boot:armhf none -- no debconf information signature.asc Description: PGP signature
Bug#776966: fgetty: please make the build reproducible
Source: fgetty Version: 0.6-5 Severity: wishlist Tags: patch User: reproducible-bui...@lists.alioth.debian.org Usertags: timestamps X-Debbugs-Cc: reproducible-bui...@lists.alioth.debian.org Hi, While working on the reproducible builds effort [1], we have noticed that fgetty could not be built reproducibly. The attached patch removes timestamps from the build system. Once applied, fgetty can be built reproducibly in our current experimental framework. [1]: https://wiki.debian.org/ReproducibleBuilds Regards, -- ,''`. : :' : Chris Lamb `. `'` la...@debian.org / chris-lamb.co.uk `- diff -urNad fgetty.orig/fgetty-0.6/debian/implicit fgetty/fgetty-0.6/debian/implicit --- fgetty.orig/fgetty-0.6/debian/implicit 2015-02-03 16:33:08.470230508 + +++ fgetty/fgetty-0.6/debian/implicit 2015-02-03 16:36:00.197717193 + @@ -35,7 +35,7 @@ debian/$*/usr/share/doc/$*/changelog' @test -s debian/$*/usr/share/doc/$*/changelog || \ sh -cx 'rm -f debian/$*/usr/share/doc/$*/changelog' - @gzip -9 debian/$*/usr/share/doc/$*/changelog* + @gzip -9n debian/$*/usr/share/doc/$*/changelog* %.deb-docs-docs: %.deb-docs-base @for i in `cat debian/$*.docs 2/dev/null || :`; do \ if test -d $$i; then \ @@ -54,7 +54,7 @@ @if test -r debian/$*.NEWS.Debian; then \ sh -cx 'install -m0644 debian/$*.NEWS.Debian \ debian/$*/usr/share/doc/$*/NEWS.Debian \ - gzip -9 debian/$*/usr/share/doc/$*/NEWS.Debian'; \ + gzip -9n debian/$*/usr/share/doc/$*/NEWS.Debian'; \ fi %.deb-docs-examples: %.deb-docs-docs @rm -rf debian/$*/usr/share/doc/$*/examples diff -urNad fgetty.orig/fgetty-0.6/debian/rules fgetty/fgetty-0.6/debian/rules --- fgetty.orig/fgetty-0.6/debian/rules 2015-02-03 16:33:08.470230508 + +++ fgetty/fgetty-0.6/debian/rules 2015-02-03 16:35:49.709259784 + @@ -43,7 +43,7 @@ install -d -m0755 '$(DIR)'/usr/share/man/man8 install -m0644 fgetty.8 debian/checkpassword.8 \ '$(DIR)'/usr/share/man/man8/ - gzip -9 '$(DIR)'/usr/share/man/man8/*.8 + gzip -9n '$(DIR)'/usr/share/man/man8/*.8 # lintian overrides install -m0755 -d '$(DIR)'/usr/share/lintian/overrides install -m0644 debian/fgetty.lintian \
Bug#776965: llvm-toolchain-3.6: FTBFS on hurd-i386
Source: llvm-toolchain-3.6 Version: 1:3.6~+rc2-1 Severity: important Tags: patch User: debian-h...@lists.debian.org Usertags: hurd Hello, Currently llvmtoolchain-3.6 (~+rc1-1 and ~+rc2-1) fails to build from source due to usage of a reserved identifier in C/C++11/POSIX.1, see e.g.: http://stackoverflow.com/questions/228783/what-are-the-rules-about-using-an-underscore-in-a-c-identifier Other restrictions might apply. For example, the POSIX standard reserves a lot of identifiers that are likely to show up in normal code: *Names beginning with a capital 'E' followed a digit or uppercase letter *may be used for additional error code names. http://www.gnu.org/software/libc/manual/html_node/Reserved-Names.html Some additional classes of identifier names are reserved for future extensions to the C language or the POSIX.1 environment. While using these names for your own purposes right now might not cause a problem, they do raise the possibility of conflict with future versions of the C or POSIX standards, so you should avoid these names. ... Names beginning with a capital ‘E’ followed a digit or uppercase letter may be used for additional error code names. See Error Reporting. http://docs.oracle.com/cd/E19205-01/819-5265/bjaky/index.html Sun Studio 12: C User's Guide 6.8.3 Names Reserved for Expansion In addition to all the names explicitly reserved, the 1990 ISO/IEC C standard also reserves (for implementations and future standards) names matching certain patterns: Table 6–3 Names Reserved for Expansion errno.h E[0-9A-Z].* ISO/IEC 9899:TC3 Committee Draft — September 7, 2007 WG14/N1256 http://www.open-std.org/jtc1/sc22/wg14/www/docs/n1256.pdf page 166: 7.1.3 Reseved Identifiers The attached patch hurd.diff fixes that by renaming EIOIO to E_IOIO. The already included patch: hurd-EIEIO-undef.diff is non-functional and should be removed. Since this is a standard violation, this patch should be submitted upstream. Test summary from the build is: Expected Passes: 7892 Expected Failures : 14 Unsupported Tests : 23 Unexpected Failures: 16 Additionally the patch debian_rules.diff adds an option to help2man: --no-discard-stderr to get output even if --help is written to stderr. This changes is made unconditionally, but could be modified of course if it causes problems for other architectures. Thanks! Index: llvm-toolchain-3.6-3.6~+rc1/lib/Target/PowerPC/PPCInstrInfo.td === --- llvm-toolchain-3.6-3.6~+rc1.orig/lib/Target/PowerPC/PPCInstrInfo.td +++ llvm-toolchain-3.6-3.6~+rc1/lib/Target/PowerPC/PPCInstrInfo.td @@ -3134,7 +3134,7 @@ def ISYNC : XLForm_2_ext19, 150, 0, 0, def ICBI : XForm_1a31, 982, (outs), (ins memrr:$src), icbi $src, IIC_LdStICBI, []; -def EIEIO : XForm_24_eieio31, 854, (outs), (ins), +def E_IEIO : XForm_24_eieio31, 854, (outs), (ins), eieio, IIC_LdStLoad, []; def WAIT : XForm_24_sync31, 62, (outs), (ins i32imm:$L), --- a/debian/rules.orig 2015-01-14 19:45:58.0 +0100 +++ b/debian/rules 2015-02-02 03:15:49.0 +0100 @@ -256,7 +256,7 @@ CMDS=llvm-dwarfdump llvm-mc llvm-mcmarkup llvm-objdump llvm-rtdyld llvm-size llvm-tblgen llvm-ranlib macho-dump lldb clang-format clang-modernize clang clang-tblgen clang-check clang-tidy clang-apply-replacements pp-trace; \ for f in $$CMDS; do \ echo Generating manpage of $$f; \ - LD_LIBRARY_PATH=$(DEB_INST)/usr/lib/llvm-$(LLVM_VERSION)/lib/ help2man --version-string=$(LLVM_VERSION) $(TARGET_BUILD)/Release/bin/$$f debian/man/$$f-$(LLVM_VERSION).1; \ + LD_LIBRARY_PATH=$(DEB_INST)/usr/lib/llvm-$(LLVM_VERSION)/lib/ help2man --no-discard-stderr --version-string=$(LLVM_VERSION) $(TARGET_BUILD)/Release/bin/$$f debian/man/$$f-$(LLVM_VERSION).1; \ done override_dh_auto_install:
Bug#776967: erc: please make the build reproducible
Source: erc
Version: 5.3-1
Severity: wishlist
Tags: patch
User: reproducible-bui...@lists.alioth.debian.org
Usertags: timestamps
X-Debbugs-Cc: reproducible-bui...@lists.alioth.debian.org
Hi,
While working on the reproducible builds effort [1], we have noticed
that erc could not be built reproducibly.
The attached patch removes timestamps from the build system. Once
applied, erc can be built reproducibly in our current experimental
framework.
[1]: https://wiki.debian.org/ReproducibleBuilds
Regards,
--
,''`.
: :' : Chris Lamb
`. `'` la...@debian.org / chris-lamb.co.uk
`-
diff -urNad erc.orig/erc-5.3/debian/rules erc/erc-5.3/debian/rules
--- erc.orig/erc-5.3/debian/rules 2015-02-03 16:32:49.337396735 +
+++ erc/erc-5.3/debian/rules2015-02-03 16:36:11.030189763 +
@@ -63,7 +63,7 @@
install -m 0644 debian/scripts/startup.${PACKAGE} \
${PKGDIR}/etc/emacs/site-start.d/50${PACKAGE}.el
## Compress stuff
- gzip -9f ${PKGDIR}${DOCDIR}/changelog.Debian \
+ gzip -9fn ${PKGDIR}${DOCDIR}/changelog.Debian \
${PKGDIR}${DOCDIR}/changelog \
${PKGDIR}${DOCDIR}/NEWS
## Fix permissions
Bug#776968: uruk: please make the build reproducible
Source: uruk Version: 20140627-1 Severity: wishlist Tags: patch User: reproducible-bui...@lists.alioth.debian.org Usertags: timestamps X-Debbugs-Cc: reproducible-bui...@lists.alioth.debian.org Hi, While working on the reproducible builds effort [1], we have noticed that uruk could not be built reproducibly. The attached patch removes timestamps from the build system. Once applied, uruk can be built reproducibly in our current experimental framework. [1]: https://wiki.debian.org/ReproducibleBuilds Regards, -- ,''`. : :' : Chris Lamb `. `'` la...@debian.org / chris-lamb.co.uk `- diff -urNad uruk.orig/uruk-20140627/debian/rules uruk/uruk-20140627/debian/rules --- uruk.orig/uruk-20140627/debian/rules2015-02-03 16:39:59.872172541 + +++ uruk/uruk-20140627/debian/rules 2015-02-03 16:40:26.965354892 + @@ -70,8 +70,8 @@ cp -a debian/README $(docdir)/README.Debian cp -a debian/TODO $(docdir)/TODO.Debian cp -a ChangeLog $(docdir)/changelog - cd $(docdir) gzip -9 changelog changelog.Debian ChangeLog.2003 NEWS.Debian - gzip -r9 debian/$(package)/usr/share/man + cd $(docdir) gzip -9n changelog changelog.Debian ChangeLog.2003 NEWS.Debian + gzip -r9n debian/$(package)/usr/share/man mkdir debian/$(package)/DEBIAN # # generate md5sums. pathnames should not have leading /. # # conffiles should be excluded. for now, assume conffiles are precisely
Bug#776910: apt: upgrade from wheezy to jessie breaks in the middle
W dniu 03.02.2015 o 15:17, David Kalnischkies pisze: Control: tag -1 - newcomer Hi Rafal, On Tue, Feb 03, 2015 at 10:20:26AM +0100, Rafal Pietrak wrote: My guess is that some limit on number of errors was taken into account unneceserly during an upgrade - upgrades are expected to rise trancient errors. Your report seems to error into the total opposite unfortunately by not mentioning a single error. Upgrading is a tricky business and basically OK. I can see it looks that way. different for everyone (as which packages you have installed can vary widely as you have ~3 to choose from). Your report is hence as actionable as a weather report saying: It is going to rain tomorrow somewhere on earth. That isn't really telling me much about if I should carry an umbrella around or not on my adventure around my little patch of dirt. For this, as well as here, we need details, details, details to actually do something about it. But my crystalball tells me that you might mean #776063 as dpkg shows in this context a too many errors message (litmus test: the word dbus was printed all over the place, right?). It might, but I don't think so. 1. in my case there was no such thing a long trail of lines with dbus word in them. 2. I do _vaguely_ remember last line above the shell prompt (after upgrade stopped) saying: too many errors (after quite long running upgrade). 3. to my surprise, apt-get -f install; apt-get dist-upgrade did help ... to some extend: the upgrade finished without next stop, but the system is not actually usable (I've filed two more bugreports regarding that). 4. the entire process/failure resembles what I've experiences while upgrading to wheezy some two years ago: at that time, I didn't have correct cpufreq-control and the upgrade did overheated the system, which rebooted during the process. After that I did numerous manual pushing of the upgrade, and (again _vaguely_ ) remember finding some apt-max-errors, which I've (remember) increasing then, which helped a lot. 5. I'm filing this bugreport, because this time there was no reboot-in-the middle, so I'd expect, the apt-max-errors (if it really exists - I cannot find it now) is truely too low for an average system I'd imagine, that upgrade from one major release to another should set it temporarly to infinity ;7, but may be not. If not we need at the very least the actual error message(s). The current system state (/var/lib/dpkg/status) as well as the state before the upgrade (the /var/backups/dpkg.status* file dated before the update) could also be helpful. The pervious dpkg.status is gone, sorry. But current dpkg.status is c.a. 4.5MB. Is it all right to upload it anyway? On a more general note: Try not to guess in bugreports. You are the eyewitness, you know the facts. I am the guy on jury duty who has to come up with a coherent story of what happened and why. I know its tempting to add evidence as a witness, but that can spoil the whole process. Yes, It is tempting :) In that case I should say, that I've only witnessed an unexpected and unprovoked single break during the upgrade. Which was fully mended by only running apt -f install followed by a single apt-get dist-upgrade. Yet, the system (although reported by apt-get as fully up to date) is not fully functional. Best regards David Kalnischkies P.S.: The 'newcomer' tag is for maintainers to indicate bitsized bugs which a newcomer to the project/package can try to tackle to get started. I wouldn't recommend these sort of upgrade bugs as a starting point… and we certainly don't need to label bugs from newcomers as such (which I guess is what you meant it to mean) as a bug is a bug, it isn't worse just because a longtime contributor reported it. Ups. (I thought it defines the reporting person). Sorry for misleading tag. -R -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#776963: please document that /etc/default/tmpfs is ignored with systemd
Package: initscripts Version: 2.88dsf-58 Severity: important On jessie, with systemd as init, configuring /tmp as tmpfs via /etc/default/tmpfs no longer works. Please document that fact prominently in that file. Bonus points for pointing the admin to alternative ways of achieving what she wants. Cheers, weasel -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#769805: ming: FTBFS on current sid: swf4compiler.tab.c:3535:7: error: lvalue required as left operand of assignment
On Sun, Nov 16, 2014 at 04:52:01PM +0100, intrig...@debian.org wrote: I tried to test my fix for #752629, but couldn't build the package with pbuilder in a sid chroot: While trying to let the package use autoreconf (to really fix FTBFS on arm64, among others) and I noted I can build the current package without any issues, in a clean sid chroot. Might you retry? -- regards, Mattia Rizzolo GPG Key: 4096R/B9444540 http://goo.gl/I8TMB more about me: http://mapreri.org Launchpad User: https://launchpad.net/~mapreri Ubuntu Wiki page: https://wiki.ubuntu.com/MattiaRizzolo signature.asc Description: Digital signature
Bug#776962: xul-ext-flashblock: clicking does not unblock flash on youtube
Package: xul-ext-flashblock Version: 1.5.18-1 Severity: important Dear Maintainer, flashblock will not properly work on youtube.com (since maybe a month or two ago). Clicking the video frame (showing the typical flashblock icon) to enable flash there will have no effect, whereas in most other scenarios unblocking flash will still work. (However, I have noticed that the click tends to often propagate *within* the flash applet or gets caught by client javascript maybe, something that also did not use to happen before.) Not sure if it's incompatibility of flashblock with new iceweasel or a change in the way youtube does things - in the latter case, flashblock should still try to work that around, and I'm setting the severity above normal since youtube is a pretty common site for people all across the userbase to visit. -- System Information: Debian Release: 8.0 APT prefers testing APT policy: (990, 'testing'), (500, 'unstable'), (500, 'stable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.16.0-4-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=cs_CZ.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) xul-ext-flashblock depends on no packages. Versions of packages xul-ext-flashblock recommends: ii iceweasel 31.4.0esr-1 xul-ext-flashblock suggests no packages. -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#776925: markdown: please make the build reproducible
Hi, On Tue, Feb 03, 2015 at 11:00:03AM +, Chris Lamb wrote: While working on the reproducible builds effort [1], we have noticed that markdown could not be built reproducibly. The attached patch removes timestamps from the build system. Once applied, markdown can be built reproducibly in our current experimental framework. Thanks for the information and patch. I'll upload a patched version to experimental now and upload a patched version to unstable once jessie is released. -- Matt -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#776964: Headers installed by zsh-dev packages miss critical pieces
Package: zsh-dev
Version: 5.0.7-5
Severity: important
X-Debbugs-CC: a...@debian.org
To use zsh headers in some module at least `config.h` file is needed in
addition to those already present in the package. `config.h` files contains
defines guessed by ./configure script and including it prior to `zsh.h` is the
only sane variant to include `zsh.h` (insane variant is using module’s own
configure script which will create those defines). Without `config.h` including
`zsh.h` will fail due to missing defines, and even if it was not failing it
would make #include zsh.h do the wrong thing because of the bits like
#ifdef ZSH_64_BIT_TYPE
typedef ZSH_64_BIT_TYPE zlong;
#ifdef ZSH_64_BIT_UTYPE
typedef ZSH_64_BIT_UTYPE zulong;
#else
typedef unsigned zlong zulong;
#endif
#else
typedef long zlong;
typedef unsigned long zulong;
#endif
(configure.h-driven definition of zlong and zulong which has the potential of
breaking ABI compatibility in some cases).
In addition to this file it is good to have a patched `zsh.mdh` file which
glues together all zsh includes and is a single entry point. Patch needed to
include this file in the distribution may be performed with the following
script:
for file in Src/{zsh.mdh,*.h} ; do
sed -i 's@\.\./config\.h@config.h@' $file
sed -i 's@#\(\s*\)include \([^]\+\)@#\1include zsh/\2@'
$file
done
. I am doing this in a Gentoo ebuild and the result works just fine.
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#776971: ming: FTBFS on arm64
Source: ming Version: 0.4.5-1.2 Severity: important Tags: patch Dear maintainer, the current version of ming FTBFS on arm64, altough it does some retooling foo. Using dh-autoreconf is rather simple, and it fixes this FTBFS, and, more important, and helps you keeping you package sane in case of new architectures. It seems ming uses an rather old version of autofoo, perhaps you can poke upstream to update their build system. Anyway, below there is a simple working patch. If you want, I can prepare a full NMU. diff -u ming-0.4.5/debian/control ming-0.4.5/debian/control --- ming-0.4.5/debian/control +++ ming-0.4.5/debian/control @@ -2,7 +2,7 @@ Section: libs Priority: optional Maintainer: Stuart R. Anderson ander...@netsweng.com -Build-Depends: debhelper (= 5.0.37.2), docbook-to-man, swig, python-all-dev (= 2.7.3), libgif-dev, libpng-dev, libz-dev, perl (= 5.10.0), autotools-dev, flex, bison, libfreetype6-dev, ttf-dejavu, ttf-opensymbol, php5-dev, php5-cli, automake, autoconf2.59, quilt, chrpath +Build-Depends: debhelper (= 5.0.37.2), docbook-to-man, swig, python-all-dev (= 2.7.3), libgif-dev, libpng-dev, libz-dev, perl (= 5.10.0), flex, bison, libfreetype6-dev, ttf-dejavu, ttf-opensymbol, php5-dev, php5-cli, automake, autoconf2.59, quilt, chrpath, dh-autoreconf Standards-Version: 3.9.3 Homepage: http://www.libming.net/ diff -u ming-0.4.5/debian/rules ming-0.4.5/debian/rules --- ming-0.4.5/debian/rules +++ ming-0.4.5/debian/rules @@ -32,6 +32,7 @@ configure: configure-stamp configure-stamp: + dh_autoreconf dh_testdir $(MAKE) -f /usr/share/quilt/quilt.make patch @@ -116,6 +117,7 @@ $(MAKE) -f /usr/share/quilt/quilt.make unpatch + dh_autoreconf_clean dh_clean install: build -- System Information: Debian Release: 8.0 APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Foreign Architectures: i386, arm64, armel, armhf, s390x Kernel: Linux 3.16.0-4-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) -- regards, Mattia Rizzolo GPG Key: 4096R/B9444540 http://goo.gl/I8TMB more about me: http://mapreri.org Launchpad User: https://launchpad.net/~mapreri Ubuntu Wiki page: https://wiki.ubuntu.com/MattiaRizzolo signature.asc Description: Digital signature
Bug#776970: softcatala-spell: please make the build reproducible
Source: softcatala-spell Version: 0.20111230b-7 Severity: wishlist Tags: patch User: reproducible-bui...@lists.alioth.debian.org Usertags: timestamps X-Debbugs-Cc: reproducible-bui...@lists.alioth.debian.org Hi, While working on the reproducible builds effort [1], we have noticed that softcatala-spell could not be built reproducibly. The attached patch removes timestamps from the build system. Once applied, softcatala-spell can be built reproducibly in our current experimental framework. [1]: https://wiki.debian.org/ReproducibleBuilds Regards, -- ,''`. : :' : Chris Lamb `. `'` la...@debian.org / chris-lamb.co.uk `- diff -urNad softcatala-spell.orig/softcatala-spell-0.20111230b/debian/rules softcatala-spell/softcatala-spell-0.20111230b/debian/rules --- softcatala-spell.orig/softcatala-spell-0.20111230b/debian/rules 2015-02-03 16:39:53.415890812 + +++ softcatala-spell/softcatala-spell-0.20111230b/debian/rules 2015-02-03 16:42:21.670361628 + @@ -20,7 +20,7 @@ # -- icatalan ispell dictionary install -m 644 catalan-i.aff $(TMP_BUILD)/catala.aff - gzip --best -c catalan-i.dic $(TMP_BUILD)/catala.mwl.gz + gzip --best -cn catalan-i.dic $(TMP_BUILD)/catala.mwl.gz # -- wcatalan wordlist. # catalan.hash is needed first for wcatalan expansion. @@ -44,11 +44,11 @@ LANG=C sort $(TMP_BUILD)/ca_ES.dic | \ grep -v -e ^[a-zA-Z]*[0-9] -e '\.' | \ - prezip -s -c | gzip --best -c $(TMP_BUILD)/ca-common.cwl.gz + prezip -s -c | gzip --best -cn $(TMP_BUILD)/ca-common.cwl.gz LANG=C sort catalan-valencian-extra-a.dic | \ grep -v -e ^[a-zA-Z]*[0-9] -e '\.' | \ - prezip -s -c | gzip --best -c $(TMP_BUILD)/ca-valencia-mes.cwl.gz + prezip -s -c | gzip --best -cn $(TMP_BUILD)/ca-valencia-mes.cwl.gz # Catalan common echo add ca-common.rws $(TMP_BUILD)/ca-general.multi
Bug#776972: fastforward: please make the build reproducible
Source: fastforward Version: 1:0.51-3 Severity: wishlist Tags: patch User: reproducible-bui...@lists.alioth.debian.org Usertags: timestamps X-Debbugs-Cc: reproducible-bui...@lists.alioth.debian.org Hi, While working on the reproducible builds effort [1], we have noticed that fastforward could not be built reproducibly. The attached patch removes timestamps from the build system. Once applied, fastforward can be built reproducibly in our current experimental framework. [1]: https://wiki.debian.org/ReproducibleBuilds Regards, -- ,''`. : :' : Chris Lamb `. `'` la...@debian.org / chris-lamb.co.uk `- diff -urNad fastforward.orig/fastforward-0.51/debian/implicit fastforward/fastforward-0.51/debian/implicit --- fastforward.orig/fastforward-0.51/debian/implicit 2015-02-03 16:45:37.610917861 + +++ fastforward/fastforward-0.51/debian/implicit2015-02-03 16:47:14.931169230 + @@ -35,7 +35,7 @@ debian/$*/usr/share/doc/$*/changelog' @test -s debian/$*/usr/share/doc/$*/changelog || \ sh -cx 'rm -f debian/$*/usr/share/doc/$*/changelog' - @gzip -9 debian/$*/usr/share/doc/$*/changelog* + @gzip -9n debian/$*/usr/share/doc/$*/changelog* %.deb-docs-docs: %.deb-docs-base @for i in `cat debian/$*.docs 2/dev/null || :`; do \ if test -d $$i; then \ @@ -54,7 +54,7 @@ @if test -r debian/$*.NEWS.Debian; then \ sh -cx 'install -m0644 debian/$*.NEWS.Debian \ debian/$*/usr/share/doc/$*/NEWS.Debian \ - gzip -9 debian/$*/usr/share/doc/$*/NEWS.Debian'; \ + gzip -9n debian/$*/usr/share/doc/$*/NEWS.Debian'; \ fi %.deb-docs-examples: %.deb-docs-docs @rm -rf debian/$*/usr/share/doc/$*/examples diff -urNad fastforward.orig/fastforward-0.51/debian/rules fastforward/fastforward-0.51/debian/rules --- fastforward.orig/fastforward-0.51/debian/rules 2015-02-03 16:45:37.610917861 + +++ fastforward/fastforward-0.51/debian/rules 2015-02-03 16:47:02.242614881 + @@ -62,7 +62,7 @@ done mv -f '$(DIR)'/usr/share/man/man1/newaliases.1 \ '$(DIR)'/usr/share/man/man1/qmail-newaliases.1 - gzip -9 '$(DIR)'/usr/share/man/man1/*.1 + gzip -9n '$(DIR)'/usr/share/man/man1/*.1 # changelog rm -f changelog ln -s CHANGES changelog
Bug#776973: integrit: please make the build reproducible
Source: integrit Version: 4.1-1 Severity: wishlist Tags: patch User: reproducible-bui...@lists.alioth.debian.org Usertags: timestamps X-Debbugs-Cc: reproducible-bui...@lists.alioth.debian.org Hi, While working on the reproducible builds effort [1], we have noticed that integrit could not be built reproducibly. The attached patch removes timestamps from the build system. Once applied, integrit can be built reproducibly in our current experimental framework. [1]: https://wiki.debian.org/ReproducibleBuilds Regards, -- ,''`. : :' : Chris Lamb `. `'` la...@debian.org / chris-lamb.co.uk `- diff -urNad integrit.orig/integrit-4.1/debian/implicit integrit/integrit-4.1/debian/implicit --- integrit.orig/integrit-4.1/debian/implicit 2015-02-03 16:46:00.383912592 + +++ integrit/integrit-4.1/debian/implicit 2015-02-03 16:47:39.892259827 + @@ -35,7 +35,7 @@ debian/$*/usr/share/doc/$*/changelog' @test -s debian/$*/usr/share/doc/$*/changelog || \ sh -cx 'rm -f debian/$*/usr/share/doc/$*/changelog' - @gzip -9 debian/$*/usr/share/doc/$*/changelog* + @gzip -9n debian/$*/usr/share/doc/$*/changelog* %.deb-docs-docs: @for i in `cat debian/$*.docs 2/dev/null || :`; do \ if test -d $$i; then \ @@ -54,7 +54,7 @@ @if test -r debian/$*.NEWS.Debian; then \ sh -cx 'install -m0644 debian/$*.NEWS.Debian \ debian/$*/usr/share/doc/$*/NEWS.Debian \ - gzip -9 debian/$*/usr/share/doc/$*/NEWS.Debian'; \ + gzip -9n debian/$*/usr/share/doc/$*/NEWS.Debian'; \ fi %.deb-docs-examples: @rm -rf debian/$*/usr/share/doc/$*/examples diff -urNad integrit.orig/integrit-4.1/debian/rules integrit/integrit-4.1/debian/rules --- integrit.orig/integrit-4.1/debian/rules 2015-02-03 16:46:00.387912764 + +++ integrit/integrit-4.1/debian/rules 2015-02-03 16:47:32.067917954 + @@ -82,11 +82,11 @@ # man install -d -m0755 '$(DIR)'/usr/share/man/man1 install -m0644 doc/*.1 '$(DIR)'/usr/share/man/man1/ - gzip -9 '$(DIR)'/usr/share/man/man1/*.1 + gzip -9n '$(DIR)'/usr/share/man/man1/*.1 # info install -d -m0755 '$(DIR)'/usr/share/info install -m0644 doc/integrit.info '$(DIR)'/usr/share/info/ - gzip -9 '$(DIR)'/usr/share/info/*.info + gzip -9n '$(DIR)'/usr/share/info/*.info # lintian overrides install -d -m0755 '$(DIR)'/usr/share/lintian/overrides install -m0644 debian/integrit.lintian \
Bug#776927: trscripts: please make the build reproducible
Source: trscripts Version: 1.16 Severity: wishlist Tags: patch User: reproducible-bui...@lists.alioth.debian.org Usertags: timestamps X-Debbugs-Cc: reproducible-bui...@lists.alioth.debian.org Hi, While working on the reproducible builds effort [1], we have noticed that trscripts could not be built reproducibly. The attached patch removes timestamps from the build system. Once applied, trscripts can be built reproducibly in our current experimental framework. [1]: https://wiki.debian.org/ReproducibleBuilds Regards, -- ,''`. : :' : Chris Lamb `. `'` la...@debian.org / chris-lamb.co.uk `- diff -urNad trscripts.orig/trscripts-1.16/debian/rules trscripts/trscripts-1.16/debian/rules --- trscripts.orig/trscripts-1.16/debian/rules 2015-02-03 11:41:31.056242730 + +++ trscripts/trscripts-1.16/debian/rules 2015-02-03 11:41:45.712860589 + @@ -38,7 +38,7 @@ install -d debian/tmp/usr/share/doc/$(package) cp debian/copyright debian/tmp/usr/share/doc/$(package) cp debian/changelog debian/tmp/usr/share/doc/$(package)/changelog - gzip -9v debian/tmp/usr/share/doc/$(package)/changelog + gzip -9vn debian/tmp/usr/share/doc/$(package)/changelog cp debian/README.Debian debian/tmp/usr/share/doc/$(package)/ cp README debian/tmp/usr/share/doc/$(package)/ install -d debian/tmp/usr/share/doc/$(package)/source
Bug#776938: sendfile: please make the build reproducible
Source: sendfile
Version: 2.1b.20080616-5.3
Severity: wishlist
Tags: patch
User: reproducible-bui...@lists.alioth.debian.org
Usertags: timestamps
X-Debbugs-Cc: reproducible-bui...@lists.alioth.debian.org
Hi,
While working on the reproducible builds effort [1], we have noticed
that sendfile could not be built reproducibly.
The attached patch removes timestamps from the build system. Once
applied, sendfile can be built reproducibly in our current experimental
framework.
[1]: https://wiki.debian.org/ReproducibleBuilds
Regards,
--
,''`.
: :' : Chris Lamb
`. `'` la...@debian.org / chris-lamb.co.uk
`-
diff -urNad sendfile.orig/sendfile-2.1b.20080616/debian/rules
sendfile/sendfile-2.1b.20080616/debian/rules
--- sendfile.orig/sendfile-2.1b.20080616/debian/rules 2015-02-03
12:28:47.920416967 +
+++ sendfile/sendfile-2.1b.20080616/debian/rules2015-02-03
12:30:46.609981152 +
@@ -69,13 +69,13 @@
$(installdoc) doc/README{,.too,.fetchfile}
debian/tmp/usr/share/doc/$(package)
$(installdoc) doc/ChangeLog
debian/tmp/usr/share/doc/$(package)/changelog
$(installdoc) doc/features debian/tmp/usr/share/doc/$(package)/
- gzip -9f
debian/tmp/usr/share/doc/$(package)/{changelog.Debian,changelog,README{,.too,.fetchfile},features}
+ gzip -9fn
debian/tmp/usr/share/doc/$(package)/{changelog.Debian,changelog,README{,.too,.fetchfile},features}
$(installdoc) doc/LIESMICH{,.auch,.neu,.entwickler,.spool}
debian/tmp/usr/share/doc/$(package)/german
$(installdoc) doc/doc.txt debian/tmp/usr/share/doc/$(package)
$(installdoc) doc/{doku.txt,vorteile}
debian/tmp/usr/share/doc/$(package)/german
- gzip -9f
debian/tmp/usr/share/doc/$(package)/german/LIESMICH{,.auch,.neu,.entwickler}
- gzip -9f debian/tmp/usr/share/doc/$(package)/doc.txt
- gzip -9f debian/tmp/usr/share/doc/$(package)/german/{doku.txt,vorteile}
+ gzip -9fn
debian/tmp/usr/share/doc/$(package)/german/LIESMICH{,.auch,.neu,.entwickler}
+ gzip -9fn debian/tmp/usr/share/doc/$(package)/doc.txt
+ gzip -9fn debian/tmp/usr/share/doc/$(package)/german/{doku.txt,vorteile}
#
$(installbin) -d debian/tmp/usr/bin
$(installbin) $(STRIP)
src/{sendfile,receive,sendmsg,utf7encode,fetchfile,wlock} debian/tmp/usr/bin
@@ -95,7 +95,7 @@
$(installdoc) doc/wlock.1 debian/tmp/usr/share/man/man1
$(installdoc) doc/sendfiled.8 debian/tmp/usr/share/man/man8
$(installdoc) doc/fetchfile.7 debian/tmp/usr/share/man/man7
- gzip -9f debian/tmp/usr/share/man/man?/*
+ gzip -9fn debian/tmp/usr/share/man/man?/*
cd debian/tmp/usr/share/man/man1 ln -s utf7encode.1.gz
utf7decode.1.gz
#
$(installbin) -d debian/tmp/etc/cron.weekly
Bug#776947: nut: Default ups.conf should have maxretry setting above examples section
Package: nut Version: 2.7.1-1 Severity: normal Tags: patch User: ubuntu-de...@lists.ubuntu.com Usertags: origin-ubuntu vivid ubuntu-patch *** /tmp/tmpvfdwEw/bug_body In Ubuntu, the attached patch was applied to achieve the following: Default/sample ups.conf has maxretry setting at end. Above that are examples and an empty line. Uncommenting any of the examples or merging with older configs are likely to end up with a broken config file, since the parser will interpret existing maxretries to be inside driver definition. Included patch follows conventions used in other nut config files. * debian/patches/0006-ups-conf-reorder.patch: Move maxretry setting above Examples section, closer to the outside of a driver definition comment. (LP: #1405822) Thanks for considering the patch. -- System Information: Debian Release: jessie/sid APT prefers utopic-updates APT policy: (500, 'utopic-updates'), (500, 'utopic-security'), (500, 'utopic-proposed'), (500, 'utopic'), (100, 'utopic-backports') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.16.0-30-generic (SMP w/4 CPU cores) Locale: LANG=en_CA.UTF-8, LC_CTYPE=en_CA.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash diff -Nru nut-2.7.1/debian/changelog nut-2.7.1/debian/changelog diff -Nru nut-2.7.1/debian/patches/0006-ups-conf-maxretry.patch nut-2.7.1/debian/patches/0006-ups-conf-maxretry.patch --- nut-2.7.1/debian/patches/0006-ups-conf-maxretry.patch 2013-11-24 14:58:03.0 -0500 +++ nut-2.7.1/debian/patches/0006-ups-conf-maxretry.patch 2015-02-03 08:23:00.0 -0500 @@ -25,10 +25,15 @@ # # These directives are common to all drivers that support ups.conf: # -@@ -102,3 +120,6 @@ +@@ -78,7 +96,10 @@ # - # To find out if your driver supports any extra settings, start it with - # the -h option and/or read the driver's documentation. + # Anything else is passed through to the hardware-specific part of + # the driver. +-# + +# Set maxretry to 3 by default, this should mitigate race with slow devices: +maxretry = 3 ++ + # Examples + # + #
Bug#776948: RM: pgtune -- ROM; upstream dead, and bad advise to be used today
Package: ftp.debian.org Severity: normal Hi, pgtune hasn't seen a new upstream release since about the medieval ages, and the last git commit isn't very current either. The postgresql.conf it produces is worse than the defaults in some aspects, so people are rather harmed than helped by this tool. Let's get rid of it, in unstable and jessie. It doesn't have any rdeps. Please remove pgtune. Christoph -- c...@df7cb.de | http://www.df7cb.de/ signature.asc Description: Digital signature
Bug#776776: Bug in resolvconf?
The dnssec-trigger daemon sets the immutability attribute on a file /etc/resolv.conf which it writes out. Evidently, dnssec-trigger is not resolvconf-compatible. The immediate, straightforward solution is for the dnssec-trigger package to Conflict with the resolvconf package. At least this should be done for jessie. The next thing to do is to look at the possibility of making dnssec-trigger resolvconf-compatible. To be resolvconf-compatible, dnssec-trigger should not write to /etc/resolv.conf directly. Instead dnssec-trigger, or more probably unbound itself, should do something like the following after the local unbound process is started. echo nameserver 127.0.0.1 | resolvconf -a lo.unbound And the following before the process is stopped. resolvconf -d lo.unbound When 127.* is one of the nameserver addresses resolvconf by default doesn't list any further addresses. So once the above has been done it may not be necessary to change the resolvconf package. However, if necessary it would also be possible to change the resolvconf package so that, for example, it gives the lo.unbound record special treatment. -- Thomas -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#776949: fake: please make the build reproducible
Source: fake Version: 1.1.11-1 Severity: wishlist Tags: patch User: reproducible-bui...@lists.alioth.debian.org Usertags: timestamps X-Debbugs-Cc: reproducible-bui...@lists.alioth.debian.org Hi, While working on the reproducible builds effort [1], we have noticed that fake could not be built reproducibly. The attached patch removes timestamps from the build system. Once applied, fake can be built reproducibly in our current experimental framework. [1]: https://wiki.debian.org/ReproducibleBuilds Regards, -- ,''`. : :' : Chris Lamb `. `'` la...@debian.org / chris-lamb.co.uk `- diff -urNad fake.orig/fake-1.1.11/debian/rules fake/fake-1.1.11/debian/rules --- fake.orig/fake-1.1.11/debian/rules 2015-02-03 14:03:24.100663560 + +++ fake/fake-1.1.11/debian/rules 2015-02-03 14:05:36.626760453 + @@ -37,14 +37,14 @@ install -c -m 644 AUTHORS $(CURDIR)/debian/tmp/usr/share/doc/fake/ install -c -m 644 ChangeLog \ $(CURDIR)/debian/tmp/usr/share/doc/fake/changelog - gzip --best $(CURDIR)/debian/tmp/usr/share/doc/fake/changelog + gzip --best -n $(CURDIR)/debian/tmp/usr/share/doc/fake/changelog install -c -m 644 docs/redundant_linux.txt \ $(CURDIR)/debian/tmp/usr/share/doc/fake/ - gzip --best \ + gzip --best -n \ $(CURDIR)/debian/tmp/usr/share/doc/fake/redundant_linux.txt install -c -m 644 docs/arp_fun.txt \ $(CURDIR)/debian/tmp/usr/share/doc/fake/ - gzip --best $(CURDIR)/debian/tmp/usr/share/doc/fake/arp_fun.txt + gzip --best -n $(CURDIR)/debian/tmp/usr/share/doc/fake/arp_fun.txt dh_movefiles --source=debian/tmp
Bug#776930: vpim: please make the build reproducible
Source: vpim
Version: 0.695-1.1
Severity: wishlist
Tags: patch
User: reproducible-bui...@lists.alioth.debian.org
Usertags: timestamps
X-Debbugs-Cc: reproducible-bui...@lists.alioth.debian.org
Hi,
While working on the reproducible builds effort [1], we have noticed
that vpim could not be built reproducibly.
The attached patch removes timestamps from the build system. Once
applied, vpim can be built reproducibly in our current experimental
framework.
[1]: https://wiki.debian.org/ReproducibleBuilds
Regards,
--
,''`.
: :' : Chris Lamb
`. `'` la...@debian.org / chris-lamb.co.uk
`-
diff -urNad vpim.orig/vpim-0.695/debian/rules vpim/vpim-0.695/debian/rules
--- vpim.orig/vpim-0.695/debian/rules 2015-02-03 12:00:42.204612210 +
+++ vpim/vpim-0.695/debian/rules2015-02-03 12:01:20.718225482 +
@@ -77,7 +77,7 @@
$(installbin) -d debian/tmp/usr/lib/mime/packages
$(installdoc) debian/mailcap debian/tmp/usr/lib/mime/packages/$(package)
#
- gzip -9f debian/tmp/usr/share/doc/$(package)/changelog{,.Debian}
+ gzip -9fn debian/tmp/usr/share/doc/$(package)/changelog{,.Debian}
#
rm debian/tmp/usr/lib/ruby/*/plist.rb
rm debian/tmp/usr/lib/ruby/*/atom.rb
Bug#772029: [Reproducible-builds] Bug#772029: debbindiff: please avoid hardcoded use of VIm
Hi, Jonas Smedegaard wrote: Quoting Jérémy Bobbio (2014-12-04 16:15:02) Jonas Smedegaard: I am not a VIm user, however, and its hardcoded use of that editor is strongly discouraging for me (no, I do not use emacs either). Please consider recoding¹ to not rely on VIm-specific features, to appeal also to users of other interactive editors. Feel free to provide another way to generate HTML diffs in a reasonable amount of time (Python html diff is out of the picture) which are readable. I've looked a bit before hacking the current solution and nothing worked out. Thanks for the challenge! :-) That's CHALLENGE ACCEPTED! nowadays. ;-) If you have notes about the stuff you've already investigated (apart from http://technogems.blogspot.com/2011/09/generate-side-by-side-diffs-in-html.html that I've already found in the README) then please do share. Else I'll try work from what I can guess based on current code. I didn't test it, but there's also libhtml-diff-perl. Maybe that's of use. There are also other not yet packaged perl modules with similar functionality: https://metacpan.org/pod/HTML::Differences https://metacpan.org/pod/Text::Diff::HTML https://metacpan.org/pod/Text::Diff::FormattedHTML I actually already started to package Text::Diff::HTML a while ago (https://bugs.debian.org/721245, https://anonscm.debian.org/cgit/pkg-perl/attic/libtext-diff-html-perl.git) as I expected that I'd need it. But then my usage case vanished. In case of interest, I can resurrect that effort. (Or package any of the other perl modules. I think Jonas would do that as well. :-) The issues I have are a) pulling in 28.8MB on my system, and b) introducing an editor that messes with system priorities among editors. Yeah, here, too... Regards, Axel -- ,''`. | Axel Beckert a...@debian.org, http://people.debian.org/~abe/ : :' : | Debian Developer, ftp.ch.debian.org Admin `. `' | 4096R: 2517 B724 C5F6 CA99 5329 6E61 2FF9 CD59 6126 16B5 `-| 1024D: F067 EA27 26B9 C3FC 1486 202E C09E 1D89 9593 0EDE -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#776931: support for comparing rpm files
package: debbindiff severity: wishlist Hi, it would be great if debbindiff could also compare rpm files, filing this bug to discuss the requirements and changes etc. Not sure if debbindiff should become a pkgbindiff or rpmbindiff should be a link to /usr/bin/debbindiff... :) cheers, Holger signature.asc Description: This is a digitally signed message part.
Bug#765285: Upstream info
Upstream had a quick look at patch bu it may not fit. The patch seems to fine fine when 1 core is used, but not when getting multiple core. They will have further look at this In the meanwhile, let's keep failing archs removed.
Bug#776940: cvs-mailcommit: please make the build reproducible
Source: cvs-mailcommit Version: 1.19-2 Severity: wishlist Tags: patch User: reproducible-bui...@lists.alioth.debian.org Usertags: timestamps X-Debbugs-Cc: reproducible-bui...@lists.alioth.debian.org Hi, While working on the reproducible builds effort [1], we have noticed that cvs-mailcommit could not be built reproducibly. The attached patch removes timestamps from the build system. Once applied, cvs-mailcommit can be built reproducibly in our current experimental framework. [1]: https://wiki.debian.org/ReproducibleBuilds Regards, -- ,''`. : :' : Chris Lamb `. `'` la...@debian.org / chris-lamb.co.uk `- diff -urNad cvs-mailcommit.orig/cvs-mailcommit-1.19/debian/rules cvs-mailcommit/cvs-mailcommit-1.19/debian/rules --- cvs-mailcommit.orig/cvs-mailcommit-1.19/debian/rules2015-02-03 12:40:22.756818920 + +++ cvs-mailcommit/cvs-mailcommit-1.19/debian/rules 2015-02-03 12:40:56.434379350 + @@ -55,14 +55,14 @@ $(installbin) -d debian/tmp/usr/share/doc/$(package) $(installdoc) debian/changelog debian/tmp/usr/share/doc/$(package)/changelog.Debian $(installdoc) debian/copyright debian/tmp/usr/share/doc/$(package) - gzip -9f debian/tmp/usr/share/doc/$(package)/changelog.Debian + gzip -9fn debian/tmp/usr/share/doc/$(package)/changelog.Debian # $(installbin) -d debian/tmp/usr/bin $(installbin) cvs-mailcommit debian/tmp/usr/bin/ # $(installbin) -d debian/tmp/usr/share/man/man1 $(installdoc) cvs-mailcommit.1 debian/tmp/usr/share/man/man1/ - gzip -9 debian/tmp/usr/share/man/man?/* + gzip -9n debian/tmp/usr/share/man/man?/* # # dpkg-shlibdeps debian/tmp/usr/bin/* dpkg-gencontrol -isp
Bug#776942: bglibs: please make the build reproducible
Source: bglibs Version: 1.106-1.1 Severity: wishlist Tags: patch User: reproducible-bui...@lists.alioth.debian.org Usertags: timestamps X-Debbugs-Cc: reproducible-bui...@lists.alioth.debian.org Hi, While working on the reproducible builds effort [1], we have noticed that bglibs could not be built reproducibly. The attached patch removes timestamps from the build system. Once applied, bglibs can be built reproducibly in our current experimental framework. [1]: https://wiki.debian.org/ReproducibleBuilds Regards, -- ,''`. : :' : Chris Lamb `. `'` la...@debian.org / chris-lamb.co.uk `- diff -urNad bglibs.orig/bglibs-1.106/debian/implicit bglibs/bglibs-1.106/debian/implicit --- bglibs.orig/bglibs-1.106/debian/implicit2015-02-03 12:38:25.991401818 + +++ bglibs/bglibs-1.106/debian/implicit 2015-02-03 12:42:47.827534539 + @@ -35,7 +35,7 @@ debian/$*/usr/share/doc/$*/changelog' @test -s debian/$*/usr/share/doc/$*/changelog || \ sh -cx 'rm -f debian/$*/usr/share/doc/$*/changelog' - @gzip -9 debian/$*/usr/share/doc/$*/changelog* + @gzip -9n debian/$*/usr/share/doc/$*/changelog* %.deb-docs-docs: %.deb-docs-base @for i in `cat debian/$*.docs 2/dev/null || :`; do \ if test -d $$i; then \ @@ -54,7 +54,7 @@ @if test -r debian/$*.NEWS.Debian; then \ sh -cx 'install -m0644 debian/$*.NEWS.Debian \ debian/$*/usr/share/doc/$*/NEWS.Debian \ - gzip -9 debian/$*/usr/share/doc/$*/NEWS.Debian'; \ + gzip -9n debian/$*/usr/share/doc/$*/NEWS.Debian'; \ fi %.deb-docs-examples: %.deb-docs-docs @rm -rf debian/$*/usr/share/doc/$*/examples diff -urNad bglibs.orig/bglibs-1.106/debian/rules bglibs/bglibs-1.106/debian/rules --- bglibs.orig/bglibs-1.106/debian/rules 2015-02-03 12:38:25.991401818 + +++ bglibs/bglibs-1.106/debian/rules2015-02-03 12:42:40.431192034 + @@ -60,7 +60,7 @@ # libbg-dev rm -rf '$(DIR)' '$(DIR)'-dev $(MAKE) install install_prefix='$(DIR)'-dev/ - gzip -f -9 '$(DIR)'-dev/usr/share/man/man1/*.1 + gzip -f -9n '$(DIR)'-dev/usr/share/man/man1/*.1 rm -f '$(DIR)'-dev/usr/lib/bglibs/*.la ln -s . '$(DIR)'-dev/usr/lib/bglibs/lib ln -s ../../include/bglibs '$(DIR)'-dev/usr/lib/bglibs/include
Bug#776928: unblock: debian-installer-netboot-images/20150107
Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: unblock x-debbugs-cc: debian-b...@lists.debian.org Hi, please unblock debian-installer-netboot-images/201501078 as the version currently in testing is unusable with jessie. $ debdiff debian-installer-netboot-images_20130613+deb7u2.b4.dsc debian-installer-netboot-images_20150107.dsc|diffstat debian/README |2 - debian/changelog| 54 +--- debian/compat |2 - debian/control | 48 +++ debian/control.in |2 - debian/lintian-overrides.in |5 debian/rules|9 --- get-images.sh | 17 - 8 files changed, 60 insertions(+), 79 deletions(-) debian-installer-netboot-images (20150107) unstable; urgency=low * Update to 20150107 images. [ Dmitrijs Ledkovs ] * Bump debhelper compat level to 9. [ Didier Raboud ] * Update architectures' list, distribution codename and major version for Jessie (Closes: #766960) * Add a kfreebsd netboot directory postfix special-case * Add new matching lintian overrides * Move to one-digit versioning, aka from '-7.0-' to '-8-' [ Cyril Brulebois ] * Update README to document fancy .bN suffix for d-i-n-i when d-i has +bN. * Add a check in get-images.sh to detect wrong binNMU versioning. -- Didier Raboud o...@debian.org Thu, 29 Jan 2015 10:34:48 +0100 Full diff attached for your convinience... cheers, Holger diff -Nru debian-installer-netboot-images-20130613+deb7u2.b4/debian/changelog debian-installer-netboot-images-20150107/debian/changelog --- debian-installer-netboot-images-20130613+deb7u2.b4/debian/changelog 2015-01-05 23:59:30.0 +0100 +++ debian-installer-netboot-images-20150107/debian/changelog 2015-01-29 10:35:32.0 +0100 @@ -1,53 +1,23 @@ -debian-installer-netboot-images (20130613+deb7u2.b4) wheezy; urgency=low +debian-installer-netboot-images (20150107) unstable; urgency=low - * Update to 20130613+deb7u2+b4 images, from proposed-updates. + * Update to 20150107 images. - -- Adam D. Barratt a...@adam-barratt.org.uk Mon, 05 Jan 2015 21:23:44 + + [ Dmitrijs Ledkovs ] + * Bump debhelper compat level to 9. -debian-installer-netboot-images (20130613+deb7u2.b3) wheezy; urgency=low + [ Didier Raboud ] + * Update architectures' list, distribution codename and major version +for Jessie (Closes: #766960) + * Add a kfreebsd netboot directory postfix special-case + * Add new matching lintian overrides + * Move to one-digit versioning, aka from '-7.0-' to '-8-' - * Update to 20130613+deb7u2+b3 images, from proposed-updates. - - -- Adam D. Barratt a...@adam-barratt.org.uk Mon, 13 Oct 2014 20:08:24 +0100 - -debian-installer-netboot-images (20130613+deb7u2.b2) wheezy; urgency=low - - * Update to 20130613+deb7u2+b2 images, from proposed-updates. - - -- Adam D. Barratt a...@adam-barratt.org.uk Thu, 10 Jul 2014 05:44:50 +0100 - -debian-installer-netboot-images (20130613+deb7u2.b1) wheezy; urgency=low - - * Update to 20130613+deb7u2+b1 images, from proposed-updates. - - -- Adam D. Barratt a...@adam-barratt.org.uk Thu, 24 Apr 2014 19:17:24 +0100 - -debian-installer-netboot-images (20130613+deb7u1.b2) wheezy; urgency=low - - * Update to 20130613+deb7u1+b2 images, from proposed-updates. - - -- Adam D. Barratt a...@adam-barratt.org.uk Wed, 05 Feb 2014 20:24:42 + - -debian-installer-netboot-images (20130613+deb7u1.b1) wheezy; urgency=low - - * Update to 20130613+deb7u1+b1 images, from proposed-updates. - - -- Adam D. Barratt a...@adam-barratt.org.uk Thu, 12 Dec 2013 19:03:39 + - -debian-installer-netboot-images (20130613+deb7u1) wheezy; urgency=low - - * Update to 20130613+deb7u1 images, from wheezy-proposed-updates. + [ Cyril Brulebois ] * Update README to document fancy .bN suffix for d-i-n-i when d-i has +bN. * Add a check in get-images.sh to detect wrong binNMU versioning. - -- Cyril Brulebois k...@debian.org Fri, 11 Oct 2013 01:10:36 +0200 - -debian-installer-netboot-images (20130613) wheezy; urgency=low - - * Update to 20130613 images, from wheezy-proposed-updates. - - -- Cyril Brulebois k...@debian.org Fri, 14 Jun 2013 11:48:42 +0200 + -- Didier Raboud o...@debian.org Thu, 29 Jan 2015 10:34:48 +0100 debian-installer-netboot-images (20130430) unstable; urgency=low diff -Nru debian-installer-netboot-images-20130613+deb7u2.b4/debian/compat debian-installer-netboot-images-20150107/debian/compat --- debian-installer-netboot-images-20130613+deb7u2.b4/debian/compat 2014-07-09 23:31:41.0 +0200 +++ debian-installer-netboot-images-20150107/debian/compat 2014-08-28 20:29:50.0 +0200 @@ -1 +1 @@ -7 +9 diff -Nru debian-installer-netboot-images-20130613+deb7u2.b4/debian/control debian-installer-netboot-images-20150107/debian/control ---
Bug#776913: flightgear-data-all: new upstream version needed by flightgear/experimental
This is an intentionally abandoned transition: a serious bug delayed the (upstream) release of 3.2 past (Ubuntu and Debian) freezes, and 3.4 is due before the next Ubuntu freeze (LP#1414379). If you urgently want 3.2, dropping the 3.2 flightgear-data upstream into the 3.0.0-1 (not -2) packaging will probably work, but this has not been tested. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
