with the SRMs. That should all
happen tomorrow...
Noah, Ross,
Thanks for picking this one up and running with it. I really appreciate it!
Cheers,
Chris
--
Chris Boot
bo...@debian.org
using:
https://sources.debian.org/src/resolvconf/1.84/debian/resolvconf.000resolvconf.ppp.ip-up/
In my opinion the most sensible way to run pppd these days is through
some kind of abstraction layer such as NetworkManager.
Regards,
Chris
--
Chris Boot
bo...@boo.tc
and I can't remember if we've considered it
already: do the environment variables get preserved in /proc/1/environ,
even if busybox ash can't grok them? Could d-i be modified to pull them
from there?
Cheers,
Chris
--
Chris Boot
bo...@debian.org
b.com/paulusmack/ppp/commit/3c7b86229f7bd2600d74db14b1fe5b3896be3875>
> to fix FTBFS with glibc 2.28. (Closes: #916163)
Hi Chris,
Thanks for making this upload on my behalf, I really appreciate you
fitting this in around your busy DPL and Reproducible Builds work.
Cheers,
Chris
--
Chris Boot
bo...@debian.org
-linux-gnueabihf/ulogd/ulogd_inppkt_NFLOG.so"
plugin="/usr/lib/arm-linux-gnueabihf/ulogd/ulogd_inpflow_NFCT.so"
plugin="/usr/lib/arm-linux-gnueabihf/ulogd/ulogd_filter_IFINDEX.so"
Thanks,
Chris
--
Chris Boot
bo...@debian.org
signature.asc
Description: OpenPGP digital signature
code
expected to be given message size in bits rather than bytes as the new
MD4 functions expect, hence the mismatch.
I'm going to spin up a test environment to make sure it's right before I
upload. I'm also chasing a suspiciously similar sounding bug (891020)
that I'd like to squash in the sa
Package: src:linux
Followup-For: Bug #883413
Hi Ben,
Unfortunately I can still reproduce this problem on 4.15-rc8 from
experimental.
The cmdline for this boot was:
BOOT_IMAGE=/boot/vmlinuz-4.15.0-rc8-amd64
root=/dev/mapper/vg_tarquin-rootfs ro intel_iommu=on vsyscall=emulate
ike to get a response from Denys about this first but I don't have
any particular objection to patching this for Debian; I just want to
understand better why this was done upstream before simply reverting it.
We also have a new upstream release of busybox to push into unstable, so
it's tempting to roll this tweak in with that.
Cheers,
Chris
--
Chris Boot
bo...@debian.org
signature.asc
Description: OpenPGP digital signature
On 30/12/17 23:24, Chris Boot wrote:
> What makes me suspicious that these are related is that neither happens
> with a 4.13 kernel, but I get both of these cgroup-related problems with
> 4.14.
>
> I wouldn't mind trying to bisect this, but I haven't done that for many
> year
On 25/12/17 23:09, Ben Hutchings wrote:
> On Sat, 2017-12-23 at 12:42 +0000, Chris Boot wrote:
>> Severity: serious
>> Justification: kernel panic
>>
>> I experimented a little and disabled cgroupv2 on that server. Because I
>> had some issues during boot I attem
Package: rsyncrypto
Version: 1.13-1
Severity: serious
Tags: patch upstream
Justification: crash on basic functionality
Dear maintainer,
I have recently been exposed to rsyncrypto through a client of my
work's, and have encountered a crash when using rsyncrypto to refresh an
encrypted directory
ppen.
Hi Adrian, Christian,
Adrian: I'm glad someone else appears to understand my intentions with
this mechanism!
I believe I have fully documented this in debian/README.source, but
please do let me know if something is missing from there. Perhaps the
debian/rules can more explicitly point
hould make dpkg-gensymbols show its version
number and exit without producing any output. That would cause the build
to ignore changes in the symbols, which is exactly what this is there to
protect against.
Please let me know if this is causing unexpected build failures and I'll
try to help.
Best regards,
Chris
--
Chris Boot
bo...@boo.tc
g rather than actual broken
behaviour, I am reducing the severity of this bug.
Cheers,
Chris
--
Chris Boot
bo...@debian.org
Hi Kamal, Chris,
It looks like kpatch is going to be removed from stretch Real Soon Now
over this bug, which has patches attached. It would be a shame to be
lacking kpatch in stretch.
Is there something I can do to help? Would you object to an NMU to get
this fixed?
Regards,
Chris
--
Chris
Package: libresteasy-java
Version: 3.0.19-2
Severity: serious
Dear maintainer,
The META-INF/MANIFEST.MF of the JAR files in this package state that
this package depends on servlet-api-2.5.jar which has now been removed
from testing/stretch and unstable/sid:
Class-Path:
Let me see what I can do to tighten up the permissions on the initial
install. Expect an update soon.
Regards,
Chris
--
Chris Boot
bo...@debian.org
GPG: 8467 53CB 1921 3142 C56D C918 F5C8 3C05 D9CE
signature.asc
Description: OpenPGP digital signature
Package: letsencrypt.sh
Version: 0.2.0-4
Severity: grave
Tags: upstream patch
Justification: renders package unusable
Dear maintainer,
Since openssl 1.1 has migrated to stretch I am unable to renew my Let's
Encrypt certificates using letsencrypt.sh. The symptoms are:
+ Challenge is valid!
+
franco,
Thanks for the upload. Once it makes it into unstable I'll absorb your
changes into my packaging repo.
Cheers,
Chris
--
Chris Boot
deb...@bootc.net
GPG: 8467 53CB 1921 3142 C56D C918 F5C8 3C05 D9CE
signature.asc
Description: OpenPGP digital signature
2015-12-12 20:08:27.0 +
+++ unbound-1.5.7/debian/changelog 2016-02-21 15:27:15.0 +
@@ -1,3 +1,13 @@
+unbound (1.5.7-1.1) unstable; urgency=medium
+
+ [ Chris Boot ]
+ * Non-maintainer upload.
+
+ [ Robert Edmonds ]
+ * [2372c14c] Makefile.in: Pass PYTHON_CPPFLAGS
he DELAYED/7 queue. Please let me know if I should delay it
longer or remove this upload before it hits unstable. The diff for my
changes is attached.
This is a simple fix to add the two missing operations to your prerm
script as no-op entries in your case statement.
Regards,
Chris
--
C
parse(u('hello b:there c:"my friend"'))
File "whoosh/compat.py", line 45, in u
return unicode(s, "unicode_escape")
TypeError: decoding Unicode is not supported
[many more test failures snipped]
1.
https://bitbucket.org/mchaput/whoosh/commits/01b6ebe3b3a8f033111f28463b9
On 2015-12-04 23:38, Michael Biebl wrote:
> Hi
>
> Am 04.12.2015 um 10:06 schrieb Chris Boot:
>> Control: severity serious
>>
>> Hi Michael,
>>
>> I have now uploaded ppp 2.4.7-1+1 to unstable, therefore the ppp plugin
>> this package ships is now b
2.4.7-1+1 to unstable, therefore the ppp plugin
this package ships is now broken in sid. Please upload a patched version
of your package as soon as possible.
I would gladly upload an NMU myself but I cannot easily do so at the
moment (I am not yet a DD).
Regards,
Chris
--
Chris Boot
deb...@bootc.net
age as soon as possible.
I would gladly upload an NMU myself but I cannot easily do so at the
moment (I am not yet a DD).
Regards,
Chris
--
Chris Boot
deb...@bootc.net
GPG: 8467 53CB 1921 3142 C56D C918 F5C8 3C05 D9CE
21:02:00:e0:8b:d1:67:2c
HTH,
Chris
--
Chris Boot
bo...@bootc.net
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
On 17 Dec 2014, at 21:11, Chris Boot bo...@bootc.net wrote:
On 17 Dec 2014, at 13:56, Ritesh Raj Sarraf r...@debian.org wrote:
On 10/07/2014 03:54 PM, Jerome Martin wrote:
On 10/07/2014 12:21 PM, Ritesh Raj Sarraf wrote:
On Tuesday 07 October 2014 03:49 PM, Ritesh Raj Sarraf wrote
to get back in again.
Best regards,
Chris
--
Chris Boot
deb...@bootc.net
GPG: 8467 53CB 1921 3142 C56D C918 F5C8 3C05 D9CE
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
with many of the patches from
2.4.7 (including for CVE-2014-3158) but excluding the ABI breaks. I'm
planning to upload it over the weekend.
HTH,
Chris
--
Chris Boot
deb...@bootc.net
GPG: 8467 53CB 1921 3142 C56D C918 F5C8 3C05 D9CE
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ
Hi,
From my perspective, it would be nice to keep the old tcm_node and lio_node
tools around. I know that they are deprecated but there are a lot of tools
around that rely on them.
The migration from the lio-utils to targetcli startup scripts could possibly be
done by removing the init script
Package: python-rtslib
Version: 3.0+git0.86e46bc6-2
Severity: grave
Dear Maintainer,
Since upgrading targetcli, rtslib and configshell on my jessie system, I can no
longer use targetcli:
tarquin bootc # targetcli
Traceback (most recent call last):
File /usr/bin/targetcli, line 23, in module
Package: targetcli
Version: 3.0+git0.7e32595e-2
Severity: grave
Justification: renders package unusable
Dear Maintainer,
The upgrade from targetcli 2.1-1 removes all targets and makes targetcli
unusable.
1. Removing lio-utils disables/removes all targets from the kernel. This is a
serious
Package: activemq
Version: 5.6.0+dfsg1-1
Severity: grave
Dear Maintainer,
I realise the root cause of the problem may not be in the ActiveMQ packages but
I don't know enough about Java and how Java things are packaged in Debian to be
confident that I would target the right packages.
After
to upload (via my sponsor) an NMU of crmsh fixing the bug to
DELAYED/5-day. I've attached the diff of my changes.
All that needed doing was adding pkg-config to Build-Depends.
Please let me know if you would rather I withdrew the upload.
Cheers,
Chris
--
Chris Boot
deb...@bootc.net
GPG: 8467
On 22/03/14 16:12, Chris Boot wrote:
On 16/03/14 11:13, David Suárez wrote:
During a rebuild of all packages in sid, your package failed to build on
amd64.
Relevant part (hopefully):
[...]
configure: error: You need pkgconfig installed in order to build crmsh
checking for pkg-config
' branch if
you do an upload (and you feel like committing to git). I've been
keeping debian-next as a collection of commits pending the next upload,
please feel free to ignore this for now.
Thanks again,
Chris
--
Chris Boot
deb...@bootc.net
GPG: 8467 53CB 1921 3142 C56D C918 F5C8 3C05 D9CE
upload (2.0.3-1)
will run a stop in preinst as well as removing the old init script.
Thanks for bringing this to my attention.
Chris
--
Chris Boot
deb...@bootc.net
GPG: 1DE8 6AB0 1897 A330 D973 D77C 50DD 5A29 FB09
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
Package: gnupg2
Version: 2.0.21-2~deb7u1
Severity: serious
Justification: fails to build from source (but built successfully in the past)
The package has a Build-Conflicts on automake (= 1.12), which only happens to
work on sid due to automake1.11 being a package in its own right. When
rebuilding
Package: device-tree-compiler
Version: 1.4.0-2
Severity: serious
Justification: Policy 5.6.12
The source tarball device-tree-compiler_1.4.0.orig.tar.gz contains the same
source code as device-tree-compiler_1.3.0.orig.tar.gz, even though the checksums
differ. Both contain upstream GIT tag v1.3.0
On 20/08/13 10:02, Raphael Geissert wrote:
Hi again,
On 31 July 2013 17:43, Chris Boot c...@tiger-computing.co.uk wrote:
This patch isn't part of 2.7.18-5, which is currently in wheezy. We've
had to roll our own update internally that includes the patch in order
to correctly process reports
On 20/08/13 10:22, Chris Boot wrote:
On 20/08/13 10:02, Raphael Geissert wrote:
Hi again,
On 31 July 2013 17:43, Chris Boot c...@tiger-computing.co.uk wrote:
This patch isn't part of 2.7.18-5, which is currently in wheezy. We've
had to roll our own update internally that includes the patch
this be
welcome?
Best regards,
Chris
--
Chris Boot
Tiger Computing Ltd
Linux for Business
Tel: 01600 483 484
Web: http://www.tiger-computing.co.uk
Follow us on Facebook: http://www.facebook.com/TigerComputing
Registered in England. Company number: 3389961
Registered address: Wyastone Business Park
: #707538)
+
+ -- Chris Boot bo...@bootc.net Tue, 28 May 2013 15:56:31 +0100
+
ppp (2.4.5-5.1) unstable; urgency=low
* Non-maintainer upload.
reverted:
--- ppp-2.4.5/debian/patches/update_if_pppol2tp
+++ ppp-2.4.5.orig/debian/patches/update_if_pppol2tp
@@ -1,53 +0,0 @@
-diff --git a/include/linux
that this bug has been resolved upstream (albeit not in a release
just yet), what can I do to help get it into the Debian Puppet packages?
Thanks,
Chris
--
Chris Boot
bo...@bootc.net
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact
On 06/03/13 20:40, Russ Allbery wrote:
Chris Boot c...@tiger-computing.co.uk writes:
Because people seem to think this is some obscure corner case, I thought
I'd write up a very simple test case to trigger the problem:
I think you've misunderstood the comments.
Everyone understands
, but the contents of
the file remains unchanged and un-managed. In this case, this is silent
corruption as Puppet fails to enforce the content change on the file.
Best regards,
Chris
--
|Chris Boot
|Tiger Computing Ltd
|Linux for Business
|
|Tel: 033 0088 1511
|Web: http://www.tiger-computing.co.uk
--
Chris Boot
bo...@bootc.net
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Package: psmisc
Version: 22.15-2
Severity: critical
Justification: breaks unrelated software
The killall command in psmisc 22.15-2 is broken: it can't find processes
with long names. The version in 22.13-1 works fine.
I first saw this on a VM cluster which uses pacemaker and DLM.
Pacemaker's DLM
48 matches
Mail list logo
