Bug#851750: kpatch: module FTBFS for Linux 4.9
Interestingly I have a similar problem on CentOS 7 when trying to
compile kpatch for kernel 4.9:
```
~/git/kpatch # uname -aLinux nas 4.9.0-1.el7.elrepo.x86_64 #1 SMP Sun
Dec 11 15:43:54 EST 2016 x86_64 x86_64 x86_64 GNU/Linux
~/git/kpatch # make
make -C kpatch-build
make[1]: Entering directory `/root/git/kpatch/kpatch-build'
make[1]: Nothing to be done for `all'.
make[1]: Leaving directory `/root/git/kpatch/kpatch-build'
make -C kpatch
make[1]: Entering directory `/root/git/kpatch/kpatch'
make[1]: Nothing to be done for `all'.
make[1]: Leaving directory `/root/git/kpatch/kpatch'
make -C kmod
make[1]: Entering directory `/root/git/kpatch/kmod'
make -C core clean
make[2]: Entering directory `/root/git/kpatch/kmod/core'
rm -f -Rf .*.o.cmd .*.ko.cmd .tmp_versions *.o *.ko *.mod.c \
Module.symvers
make[2]: Leaving directory `/root/git/kpatch/kmod/core'
make -C core
make[2]: Entering directory `/root/git/kpatch/kmod/core'
make -C /lib/modules/4.9.0-1.el7.elrepo.x86_64/build
M=/root/git/kpatch/kmod/core kpatch.ko
make[3]: Entering directory `/usr/src/kernels/4.9.0-1.el7.elrepo.x86_64'
CC [M] /root/git/kpatch/kmod/core/core.o
/root/git/kpatch/kmod/core/core.c:273:21: error: variable
‘kpatch_backtrace_ops’ has initializer but incomplete type
static const struct stacktrace_ops kpatch_backtrace_ops = {
^
/root/git/kpatch/kmod/core/core.c:274:2: error: unknown field ‘address’
specified in initializer
.address = kpatch_backtrace_address_verify,
^
/root/git/kpatch/kmod/core/core.c:274:2: warning: excess elements in
struct initializer [enabled by default]
/root/git/kpatch/kmod/core/core.c:274:2: warning: (near initialization
for ‘kpatch_backtrace_ops’) [enabled by default]
/root/git/kpatch/kmod/core/core.c:275:2: error: unknown field ‘stack’
specified in initializer
.stack = kpatch_backtrace_stack,
^
/root/git/kpatch/kmod/core/core.c:275:2: warning: excess elements in
struct initializer [enabled by default]
/root/git/kpatch/kmod/core/core.c:275:2: warning: (near initialization
for ‘kpatch_backtrace_ops’) [enabled by default]
/root/git/kpatch/kmod/core/core.c:276:2: error: unknown field
‘walk_stack’ specified in initializer
.walk_stack = print_context_stack_bp,
^
/root/git/kpatch/kmod/core/core.c:276:16: error:
‘print_context_stack_bp’ undeclared here (not in a function)
.walk_stack = print_context_stack_bp,
^
/root/git/kpatch/kmod/core/core.c:276:2: warning: excess elements in
struct initializer [enabled by default]
.walk_stack = print_context_stack_bp,
^
/root/git/kpatch/kmod/core/core.c:276:2: warning: (near initialization
for ‘kpatch_backtrace_ops’) [enabled by default]
/root/git/kpatch/kmod/core/core.c:303:21: error: variable
‘kpatch_print_trace_ops’ has initializer but incomplete type
static const struct stacktrace_ops kpatch_print_trace_ops = {
^
/root/git/kpatch/kmod/core/core.c:304:2: error: unknown field ‘stack’
specified in initializer
.stack = kpatch_print_trace_stack,
^
/root/git/kpatch/kmod/core/core.c:304:2: warning: excess elements in
struct initializer [enabled by default]
/root/git/kpatch/kmod/core/core.c:304:2: warning: (near initialization
for ‘kpatch_print_trace_ops’) [enabled by default]
/root/git/kpatch/kmod/core/core.c:305:2: error: unknown field ‘address’
specified in initializer
.address = kpatch_print_trace_address,
^
/root/git/kpatch/kmod/core/core.c:305:2: warning: excess elements in
struct initializer [enabled by default]
/root/git/kpatch/kmod/core/core.c:305:2: warning: (near initialization
for ‘kpatch_print_trace_ops’) [enabled by default]
/root/git/kpatch/kmod/core/core.c:306:2: error: unknown field
‘walk_stack’ specified in initializer
.walk_stack = print_context_stack,
^
/root/git/kpatch/kmod/core/core.c:306:16: error: ‘print_context_stack’
undeclared here (not in a function)
.walk_stack = print_context_stack,
^
/root/git/kpatch/kmod/core/core.c:306:2: warning: excess elements in
struct initializer [enabled by default]
.walk_stack = print_context_stack,
^
/root/git/kpatch/kmod/core/core.c:306:2: warning: (near initialization
for ‘kpatch_print_trace_ops’) [enabled by default]
/root/git/kpatch/kmod/core/core.c: In function
‘kpatch_verify_activeness_safety’:
/root/git/kpatch/kmod/core/core.c:327:3: error: implicit declaration of
function ‘dump_trace’ [-Werror=implicit-function-declaration]
dump_trace(t, NULL, NULL, 0, _backtrace_ops, );
^
cc1: some warnings being treated as errors
make[4]: *** [/root/git/kpatch/kmod/core/core.o] Error 1
make[3]: *** [kpatch.ko] Error 2
make[3]: Leaving directory `/usr/src/kernels/4.9.0-1.el7.elrepo.x86_64'
make[2]: *** [kpatch.ko] Error 2
make[2]: Leaving directory `/root/git/kpatch/kmod/core'
make[1]: *** [all] Error 2
make[1]: Leaving directory `/root/git/kpatch/kmod'
make: *** [build-kmod] Error 2
```
Bug#568838: Still a bug in Wheezy Jessie
This appears to still be a bug in both Wheezy and Jessie – is there any reason this patch never made it in?
Bug#768922: [Debian-ha-maintainers] pacemaker in jessie
Any progress with Pacemaker on Jessie? I've had to revert back to Wheezy but that has the much older Pacemaker 1.1.7
Bug#742689: check-mk: more CVE info
Disappointing to see Jessie was released with the check-mk package missing. This is the third package I've found to be missing since Jessie was released - I get the feeling the release was perhaps rushed? Anyway, grievances aside - is there any progress with getting this packaged for backports? -- Sam McLeod
Bug#768618: pacemaker: stopped working after upgrade to 1.1.10+git20130802-4.1
Any progress on Pacemaker for Jessie - Is there an alternative or do I have to downgrade back to Wheezy? I'm surprised to see Jessie was released with so many packages missing. -- Sam McLeod @s_mcleod[1] | smcleod.net Links: 1. https://twitter.com/s_mcleod
Bug#781128: security.debian.org: GeoDNS load balancing of Debian Security mirrors + out of date mirrors means you cant patch
I can confirm that it is indeed now available. I still think this is a bug though - out of date mirrors shouldn't be handed out. On Wed, Mar 25, 2015 at 4:34 AM -0700, Florian Weimer f...@deneb.enyo.demailto:f...@deneb.enyo.de wrote: * Sam McLeod: So the fix is just to wait for all Debian mirrors to be in sync before you can patch? We usually send out the announcement email only after the mirror sync has completed. But there can be delays, and other users might get confused if there is a security update without a matching announcement. Can you confirm that the update is now available to you?
Bug#781128: security.debian.org: GeoDNS load balancing of Debian Security mirrors + out of date mirrors means you cant patch
So the fix is just to wait for all Debian mirrors to be in sync before you can patch? On Wed, Mar 25, 2015 at 3:05 AM -0700, Florian Weimer f...@deneb.enyo.demailto:f...@deneb.enyo.de wrote: * Sam McLeod: 4) Mirror given by GeoDNS for security.debian.org was: - nashira.anu.edu.au (Located in Canberra, Australia) - Out of date and did not contain the patch. As far as I can tell, the Australian mirror is in sync now: $ wget -q -O- --header Host: security.debian.org http://gluck.debian.org/debian-security/dists/wheezy/updates/ | grep InRelease trtd valign=topimg src=/icons/unknown.gif alt=[ ]/tdtda href=InReleaseInRelease/a/tdtd align=right24-Mar-2015 21:32 /tdtd align=right101K/td/tr Either this was temporary, or the issue had a different cause. Note that mirror update is not instantaneous around the globe. In some cases, the debian-security-announce message will arrive some time before packages are available. In other cases, the message arrives afterwards.
Bug#781128: security.debian.org: GeoDNS load balancing of Debian Security mirrors + out of date mirrors means you cant patch
Package: security.debian.org Severity: grave Tags: security Justification: renders package unusable Dear Maintainer, *** Please consider answering these questions, where appropriate *** * What led up to the situation? 1) Received notification of DSA 3197-2 2) Updated apt across our servers 3) Security patch was unavailable 4) Mirror given by GeoDNS for security.debian.org was: - nashira.anu.edu.au (Located in Canberra, Australia) - Out of date and did not contain the patch. - Was not in the same city (Melbourne), or State (Victoria) as our location. * What exactly did you do (or not do) that was effective (or ineffective)? - There was no clear way to mark the mirror as out of date or to select another mirror. - We ended up having to manually edit our servers hosts file to point at another host. * What was the outcome of this action? - We were not able to obtain a security patch when it was released. * What outcome did you expect instead? - GeoDNS for security updates to only point to updated servers - GeoDNS to provide a mirror near us, rather than on the other side of the country -- System Information: Debian Release: 7.8 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 3.18.4-ix (SMP w/4 CPU cores) Locale: LANG=en_AU.UTF-8, LC_CTYPE=en_AU.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#712907: grub-installer: No longer installs automatically on a normal machine with one hard drive
I can confirm this is still a problem with Jessie. Debian installer with preseed fails to automatically select the disk to install grub to (/dev/vda). This causes the installation to stop and wait for user input when building on QEMU / KVM: https://github.com/sammcj/packer-qemu-debian-jessie/issues/1 -- Sam McLeod @s_mcleod[https://twitter.com/s_mcleod] -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#712907: grub-installer: No longer installs automatically on a normal machine with one hard drive
Confirmed working with Jessie - https://github.com/sammcj/packer-qemu-debian-jessie/commit/12a6dae01f328787dd89621d0bddc34458ac038e Build log - https://raw.githubusercontent.com/sammcj/packer-qemu-debian-jessie/master/build_output.log Thanks again Cyril.
Bug#712907: grub-installer: No longer installs automatically on a normal machine with one hard drive
Thanks Cyril, I did indeed miss that, that's great - I'll test it today. It looks like the example pressed hasn't been updated to include this feature: https://www.debian.org/releases/jessie/example-preseed.txt -- Sam McLeod @s_mcleod[https://twitter.com/s_mcleod] -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#769482: /usr/bin/pip-3.2: pip 1.1 is insecure, unsupported and does not work with most of python3
Package: python3-pip
Version: 1.1-3
Severity: serious
File: /usr/bin/pip-3.2
Tags: security
Justification: unkkown
Dear Maintainer,
* What led up to the situation?
Tried to upgrade a python package using pip-3.2 (which is pip v1.1)
* What exactly did you do (or not do) that was effective (or
ineffective)?
pip install -U docker-forklift
* What was the outcome of this action?
Exception:
Traceback (most recent call last):
File /usr/lib/python3/dist-packages/pip/basecommand.py, line 104, in main
status = self.run(options, args)
File /usr/lib/python3/dist-packages/pip/commands/install.py, line 245, in
run
requirement_set.prepare_files(finder, force_root_egg_info=self.bundle,
bundle=self.bundle)
File /usr/lib/python3/dist-packages/pip/req.py, line 1014, in prepare_files
req_to_install.assert_source_matches_version()
File /usr/lib/python3/dist-packages/pip/req.py, line 359, in
assert_source_matches_version
version = self.installed_version
File /usr/lib/python3/dist-packages/pip/req.py, line 351, in
installed_version
return self.pkg_info()['version']
File /usr/lib/python3/dist-packages/pip/req.py, line 318, in pkg_info
data = self.egg_info_data('PKG-INFO')
File /usr/lib/python3/dist-packages/pip/req.py, line 261, in egg_info_data
data = fp.read()
File /usr/lib/python3.2/encodings/ascii.py, line 26, in decode
return codecs.ascii_decode(input, self.errors)[0]
UnicodeDecodeError: 'ascii' codec can't decode byte 0xe2 in position 6265:
ordinal not in range(128)
* What outcome did you expect instead?
docker-forklift to be upgraded
* Notes:
https://github.com/kennethreitz/requests/issues/2335
https://github.com/infoxchange/docker-forklift/issues/78
https://security-tracker.debian.org/tracker/CVE-2013-1629
-- System Information:
Debian Release: 7.7
APT prefers stable-updates
APT policy: (500, 'stable-updates'), (500, 'stable')
Architecture: amd64 (x86_64)
Kernel: Linux 3.16-0.bpo.2-amd64 (SMP w/8 CPU cores)
Locale: LANG=en_AU.UTF-8, LC_CTYPE=en_AU.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Versions of packages python3-pip depends on:
ii python33.2.3-6
ii python3-pkg-resources 0.6.24-1
ii python3-setuptools 0.6.24-1
ii python3.2 3.2.3-7
Versions of packages python3-pip recommends:
ii build-essential 11.5
ii python3-dev 3.2.3-6
python3-pip 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
