On 17/02/2025 14:17, Emilio Pozuelo Monfort wrote:
Go ahead.
I have uploaded 2.5.2-1+1 to unstable. I'll give you a shout in a day or
two to start issuing binNMUs of the rdeps, unless you get there before me.
Thanks,
Chris
--
Chris Boot
bo...@debian.org
Package: release.debian.org
Severity: normal
X-Debbugs-Cc: p...@packages.debian.org
Control: affects -1 + src:ppp
User: release.debian@packages.debian.org
Usertags: transition
Hello Release Team friends,
I have uploaded ppp 2.5.2-1+1~exp1 to experimental today, and have been
testing it locall
team again on the bug shortly.
https://release.debian.org/transitions/html/auto-upperlimit-ppp.html
https://release.debian.org/transitions/html/ppp-2.5.1.html
Cheers,
Chris
--
Chris Boot
bo...@debian.org
Hi,
On 22/11/2024 15:30, Chris Boot wrote:
On 22/11/2024 14:45, Chris Boot wrote:
I'll try to run a few rebuilds this weekend and upload.
I have now successfully rebuilt all the level-1 rdeps in a local test
environment, and then uploaded 2.5.1-1+1 to sid.
Please could you trigger b
On 22/11/2024 14:45, Chris Boot wrote:
I'll try to run a few rebuilds this weekend and upload.
I have now successfully rebuilt all the level-1 rdeps in a local test
environment, and then uploaded 2.5.1-1+1 to sid.
Cheers,
Chris
--
Chris Boot
bo...@debian.org
On 22/11/2024 10:10, Emilio Pozuelo Monfort wrote:
On 12/10/2024 23:23, Sebastian Ramacher wrote:
Control: tags -1 confirmed
Control: forwarded -1 https://release.debian.org/transitions/html/
ppp-2.5.1.html
On 2024-10-10 16:58:47 +0100, Chris Boot wrote:
Package: release.debian.org
Severity
nt of network.target.
I welcome your thoughts.
Cheers,
Chris
--
Chris Boot
bo...@debian.org
Source: nrpe-ng
Version: 0.2.0-1.3
Severity: serious
Tags: upstream
I abandoned this project upstream over 2 years ago. This package should
not be part of Trixie without someone else taking over upstream (and
Debian) maintenance.
Modern versions of nrpe resolve most of the issues that inspired th
Package: src:linux
Version: 6.11.4-1
Severity: important
Tags: ipv6
Hi,
I upgraded a couple of systems from linux-image-6.11.2-amd64 to
linux-image-6.11.4-amd64 and after rebooting the systems' firewalls fail
to start.
The problem can be reproduced very simply:
# ip6tables -w -t mangle -A fooX9
Package: release.debian.org
Severity: normal
X-Debbugs-Cc: p...@packages.debian.org
Control: affects -1 + src:ppp
User: release.debian@packages.debian.org
Usertags: transition
Hello Release Team friends,
I have uploaded ppp 2.5.1-1+1~exp1 to experimental today, and have been
testing it locall
Control: severity -1 serious
Control: tags -1 ftbfs
X-Debbugs-Cc: pkg-utopia-maintain...@lists.alioth.debian.org
On 12/01/2024 21:13, Bastian Germann wrote:
On Sun, 26 Nov 2023 11:21:56 + Chris Boot wrote:
I'm preparing to upload ppp-2.5.0 to unstable, and
network-manager-fortis
Control: severity -1 serious
Control: tags -1 ftbfs
On 26/11/2023 13:06, Christoph Biedl wrote:
Chris Boot wrote...
[...]
I'll upgrade the bug to RC when I upload ppp-2.5.0 to unstable.
Okay, just let me know when it's a good time to upload an updated
pptpd package.
Hi Christ
On 26/11/2023 11:36, Chris Boot wrote:
On 26/11/2023 10:56, Chris Boot wrote:
Any way to reduce possible breakage, or to detect and fix it before
the transition starts? Like rebuilding rdeps, or checking rdep
autopkgtests?
I'll go an do some rebuilds now and see how they go. If any bre
Package: crmsh
Version: 4.5.0-1
Severity: important
Hi,
When I try to put a node into standby using "crm node standby", I see
the following stack trace and the node doesn't go into standby:
Traceback (most recent call last):
File "/usr/sbin/crm", line 53, in
rc = main.run()
^
Source: mesa
Version: 23.2.1-1
Severity: normal
Tags: upstream
Dear Maintainer,
I have been debugging a problem that appears in Kitty, the terminal
emulator. It uses OpenGL directly, and its windows/buffers use sRGB
colour space. The issue is that colours are too dark; black and white
are correct
On 26/11/2023 10:56, Chris Boot wrote:
Any way to reduce possible breakage, or to detect and fix it before
the transition starts? Like rebuilding rdeps, or checking rdep
autopkgtests?
I'll go an do some rebuilds now and see how they go. If any breakage
occurs it will be obvious at build
Source: network-manager-sstp
Version: 1.3.1-2
Severity: important
Tags: patch upstream
Hi Eivind,
This is the same issue as sstp-client. I'm preparing to upload ppp-2.5.0
to unstable, and network-manager-sstp fails to build with the updated
pppd plugin API in ppp-2.5.0. I see there are patches in
Source: network-manager-fortisslvpn
Version: 1.4.0-1
Severity: important
Tags: upstream patch
Dear Maintainer,
I'm preparing to upload ppp-2.5.0 to unstable, and
network-manager-fortisslvpn fails to build with the updated pppd plugin
API in ppp-2.5.0. I see there is a patch[1] in the GNOME GitLab
Source: sstp-client
Version: 1.0.18-1
Severity: important
Tags: upstream
Hi Eivind,
I'm preparing to upload ppp-2.5.0 to unstable, and sstp-clientfails to
build with the updated pppd plugin API in ppp-2.5.0. I see you already
have a new upstream release of sstp-client which appears to fix these
i
ebian/changelog
index 3e5aae3f64ab..164fdbc6c664 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,9 @@
+pptpd (1.4.0-13) UNRELEASED; urgency=medium
+
+ * Fix build failures with ppp 2.5.0. (Closes: XXX)
+
+ -- Chris Boot Sun, 26 Nov 2023 10:48:24 +
+
pptpd (1.4.0-12) unstable;
[re-sending to include the bug, oops]
On 24/11/2023 15:52, Emilio Pozuelo Monfort wrote:
On 23/11/2023 11:54, Chris Boot wrote:
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: transition
X-Debbugs-Cc: p...@packages.debian.org
Control: affects
cause breakage (dh_movetousr is a
+ no-op pre-trixie).
+
+ -- Chris Boot Fri, 24 Nov 2023 17:13:53 +
diff --git a/debian/changelog b/debian/changelog
index 838d7d7a6f1b..1d31a473a3b5 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,12 @@
+rtl-sdr (0.6.0-5.1) UNRELEASED; urgency=m
port-dev (>= 0.1.0).
@@ -15,6 +16,11 @@ libsigrok (0.5.2-5) UNRELEASED; urgency=medium
+ libsigrok-dev: Drop versioned constraint on libzip-dev (>= 0.10) in
Depends.
+ [ Chris Boot ]
+ * DEP17: Install udev rules into /usr, with (M10) protective diversion
+against possibl
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: transition
X-Debbugs-Cc: p...@packages.debian.org
Control: affects -1 + src:ppp
Hello Release Team friends,
I uploaded ppp-2.5.0-1+1 to experimental back in September, and I think
it's time to unle
d in the ulogd2-pcap package, which is separate in order to
avoid the dependency on libpcap. It was this way even with ulogd 1.x.
Cheers,
Chris
--
Chris Boot
bo...@debian.org
ust delete
those files, either.
I had a scout around other common packages and very few remove the users
they create for this reason.
Regards,
Chris
--
Chris Boot
bo...@debian.org
is an rsync bug/regression. Hopefully it can be
fixed soon; I see Samuel is active in the upstream issue.
I've just tried rsync 3.2.6-3 from experimental and can confirm that
ftpsync now works correctly again with that version.
Cheers,
Chris
--
Chris Boot
bo...@debian.org
Package: ftpsync
Version: 20180513+nmu1
Severity: important
Hi all,
I discussed this a few days ago in #debian-ftp; I think the bug is
probably in rsync but ftpsync is how I ran across it.
My mirror syncs against free.hands.com / ftp.uk.debian.org. With rsync
3.2.5-1 my mirror fails to sync: sta
On 09/04/2022 16:54, Chris Boot wrote:
On 09/04/2022 14:26, Timo Aaltonen wrote:
Timo Aaltonen kirjoitti 9.4.2022 klo 16.01:
[...]
The reason if fails is probably that libldb got a new version and
sssd needs a rebuild. Could you try building the current package
against current samba?
oh
licit-function-declaration -Winit-self \
-Wmissing-include-dirs \
-fno-strict-aliasing \
- -std=gnu99
+ -std=gnu11
endif
CMOCKA_CFLAGS = -fno-lto
Thanks for maintaining sssd.
Cheers,
Chris
--
Chris Boot
bo...@debian.org
both:
* scd: Support longer data for ssh-agent authentication with openpgp
cards. [T5682]
This corresponds to the following GnuPG bug:
https://dev.gnupg.org/T5682
Please update GnuPG to 2.2.33 or 2.3.4.
Thanks,
Chris
--
Chris Boot
bo...@debian.org
tness (see #995833).
Yes, we probably do want to do that. I was going to vimdiff the configs
to see what we might need to change and harmonise between them. And
thanks for pointing out CONFIG_DESKTOP, though, I wasn't aware of it.
Cheers,
Chris
--
Chris Boot
bo...@debian.org
heers,
Chris
--
Chris Boot
bo...@debian.org
nd open an s-p-u bug 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
On 06/08/2021 02:47, Ross Vandegrift wrote:
Hi Chris,
On Thu, Jul 29, 2021 at 10:24:22AM +0100, Chris Boot wrote:
In the sudoers file there is a duplicate includedir
statement; at the end of the file you will find the following contents:
"""
# See sudoers(5) for more informati
Package: cloud.debian.org
Severity: important
Dear Maintainer,
I built a couple of instances using the bullseye test image
(debian-11-amd64-daily-20210728-717, or ami-0311ee36441c551b3 in
eu-west-2). In the sudoers file there is a duplicate includedir
statement; at the end of the file you will fi
Control: notfound -1 1.9.6-1~exp1
On 01/04/2021 11:33, Marc Haber wrote:
On Wed, Mar 17, 2021 at 05:39:28PM +, Chris Boot wrote:
If a Cmnd_Alias (others may also be affected) is defined twice, the
error message produced is misleading:
$ cat >test <
Cmnd_Alias BUG_TEST = /bi
Package: sudo
Version: 1.9.5p2-3
Severity: normal
Dear Maintainer,
If a Cmnd_Alias (others may also be affected) is defined twice, the
error message produced is misleading:
$ cat >test < Cmnd_Alias BUG_TEST = /bin/true
> Cmnd_Alias BUG_TEST = /bin/true
> EOF
$ visudo -c -f test
test:2:32: Alias
..)
It's very much not ready yet and is lacking documentation, but in my
brief testing it does appear to work.
Please let me know what you think, and what it might take to get this in
reprepro properly.
Cheers,
Chris
--
Chris Boot
bo...@debian.org
not fixed in Buster, but
the bug will be closed with a particular version so it will show as
unfixed in Buster (but should be fine for Bullseye).
Cheers,
Chris
--
Chris Boot
bo...@debian.org
fixed for bullseye; I'm sorry I wasn't aware of the transition.
Best regards,
Chris
--
Chris Boot
bo...@debian.org
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: transition
Hi release team folks,
There has been a new upstream release of ppp (2.4.9). I know this is
very soon after my upload of 2.4.8 and its transition, but I'm also both
aware of the transiti
On Sat, 2 Jan 2021, at 12:35, 積丹尼 Dan Jacobson wrote:
> # cat /etc/resolv.conf
> # MADE BY ME in /root/bin/openpppd
> nameserver 168.95.192.1
> nameserver 168.95.1.1
> # ls -l /etc/resolv.conf
> lrwxrwxrwx 1 root root 39 08-09 02:29 /etc/resolv.conf ->
> ../run/systemd/resolve/stub-resolv.conf
>
Control: tags -1 pending
On 31/12/2020 00:40, Michael Biebl wrote:
During the upgrade of ppp I noticed this:
[...]
This looks like a forgotten set -x
Hi Michael,
Ugh. That's exactly what it is, sorry. I've lined up a commit to fix
this for the next upload.
Thanks,
Chris
--
On 01/01/2021 13:24, 積丹尼 Dan Jacobson wrote:
"CB" == Chris Boot writes:
CB> I don't know why you think this bug is 'grave'. This does not make your
CB> system unusable (and you've found a workaround), does not cause data
CB> loss, and is not a security
eference, resolvconf does this 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
On 25/12/2020 14:38, Sebastian Ramacher wrote:
Please go ahead.
Uploaded.
--
Chris Boot
bo...@debian.org
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: transition
Hi release team folks,
There has been a version of ppp in experimental since 2020-02-15. I've
got a very slightly revised version that I'd like to upload over the
holidays (mostly just c
Package: rsync
Version: 3.2.2-1
Severity: important
Hi Paul,
rsync no longer accepts --bwlimit=0 as a valid option:
$ rsync --bwlimit=0
rsync: --bwlimit value is too small: 0
rsync error: syntax or usage error (code 1) at main.c(1694)
[client=3.2.2]
However, the man page states "A value of zero
Source: request-tracker4
Version: 4.4.3-2
Severity: normal
Hi Dominic,
We're running into a few minor issues with RT 4.4.3. In particular,
we're looking at migrating from MySQL/MariaDB to PostgreSQL for a number
of reasons, and the export/import process has some issues fixed in
4.4.4.
More speci
enabled debug and didn't see anything in the log about routing.
> Here's the relevant part of the log, after authentication
> (log is in reverse order)
No, ppp doesn't negotiate a default route, it's up to each end to add
one as required. Hence the defaultroute / nodefaultroute options for pppd.
Cheers,
Chris
--
Chris Boot
bo...@debian.org
On 04/08/2019 17:29, Bastian Blank wrote:
> On Sat, Aug 03, 2019 at 03:06:39PM +0100, Chris Boot wrote:
>> - Which checksums should we include? Our Apt repos use MD5 and SHA-256,
>> and our ISOs use MD5, SHA-1, SHA-256 and SHA-512. I'd be inclined to
>> suggest SHA-256 an
On 03/08/2019 11:06, Chris Boot wrote:
> On 25/07/2019 00:00, Thomas Goirand wrote:
>> On the secret files found here:
>> http://cloud.debian.org/cdimage/cloud/
>>
>> there's a json file attached. Unfortunately, there's no SHA512, and of
>> course, no GPG
to be hex strings, effectively the same
as the first column of the output from sha1sum, sha256sum, sha512sum,
etc... from coreutils.
- Should we also generate the relevant SHA1SUM / SHA256SUM / SHA512SUM /
etc... files as might be consumed by the coreutils tools?
- Should we GPG-sign the manifests,
hairport-sync, though stupidly I didn't
document why that was.
Sorry about this, will upload a fixed version as soon as I can.
Cheers,
Chris
--
Chris Boot
bo...@debian.org
a package, it would be entirely possible for telnetd to be included
in it. There is no timeline for the introduction of such a package and
every chance it might not happen, though.
Best regards,
Chris
--
Chris Boot
bo...@debian.org
signature.asc
Description: OpenPGP digital signature
t
would be an alternative route for you to explore to introduce this
functionality in Debian.
Best regards,
Chris
--
Chris Boot
bo...@debian.org
signature.asc
Description: OpenPGP digital signature
DAEMON_ARGS="--daemon ${DAEMON_ARGS}"
+
+ # Continue with the standard do_start_cmd() implementation
+ do_start_cmd
}
Thanks,
Chris
--
Chris Boot
bo...@debian.org
signature.asc
Description: OpenPGP digital signature
Package: ghostscript
Version: 9.26a~dfsg-0+deb9u3
Severity: important
Tags: security
Dear maintainers & security folks,
The 9.26a~dfsg-0+deb9u3 update has broken printing of PDFs on a number
of systems that we maintain. The PDF files are printed simply using "lp
-d$printer foo.pdf". This results
Source: mediawiki
Version: 1:1.31.1-4
Severity: normal
Tags: patch upstream
Dear maintainers,
MediaWiki 1.31.1 appears to have some incompatibilities with PHP 7.3
which is in Buster. Uploading files, such as images, leads to a
UploadStashBadPathException presented on the web interface, and the
se
--
Chris Boot
bo...@debian.org
27;ve also had a thought, 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
github.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
rge/reinstall could well fix it, just double-check you haven't
ended up with *both* /bin/busybox and /usr/bin/busybox. You should have
only the former and should be able to safely remove /usr/bin/busybox,
assuming /bin/busybox is not a symlink anymore.
Best regards,
Chris
--
Chris Boot
bo...@debian.org
/usr/bin/busybox and the binary in
there. Do you have any idea where that came from?
Cheers,
Chris
--
Chris Boot
bo...@debian.org
On 25/10/2018 10:46, Arturo Borrero Gonzalez wrote:
> On Thu, 25 Oct 2018 at 11:39, Chris Boot wrote:
>>> So, in this case, perhaps the proper fix is for ferm to don't hardcode
>>> binary paths.
>>
>> Perhaps, but in that case a list of broken packages is
, and (versioned) Breaks added to
iptables to make sure that people's systems are not broken by this.
It's also going to need a NEWS.Debian entry if there isn't one already
(I haven't checked) because people will have written scripts which
hard-code the old paths.
Cheers,
Chris
Package: reportbug-gtk
Version: 7.5.0
Severity: normal
Hi,
reportbug-gtk is currently Priority: standard, so new installations will
always receive it as long as the "standard system utilities" option is
selected in the Debian Installer, even if no desktop is selected. That
means that all the GTK
Thanks for taking care of this for me, much appreciated.
Best regards,
Chris
--
Chris Boot
bo...@debian.org
signature.asc
Description: OpenPGP digital signature
buster/sid.
Please find a patch attached in case it's useful.
Best regards,
Chris
--
Chris Boot
bo...@debian.org
diff --git a/debian/postinst b/debian/postinst
index 9951cc715140..79686b01145a 100644
--- a/debian/postinst
+++ b/debian/postinst
@@ -9,6 +9,7 @@ if test -d /sys/class &
upstream it should go pretty fast.
>
> Please try the attached quick patch for fence_scsi and let us know
> if there are still some issues with that agent.
Hi Valentin,
Yes, the patch does appear to allow the fence_scsi agent to work. Thank you.
Best regards,
Chris
--
Chris Boot
bo...@d
Package: fence-agents
Version: 4.2.0-1
Severity: important
Tags: upstream
Dear maintainer(s),
Some fencing agents, notably fence_scsi (which I wish to use), do not
work with Python3:
fence_scsi: https://github.com/ClusterLabs/fence-agents/issues/206
fence_apc_snmp: https://github.com/ClusterLabs
ot;/usr/lib/arm-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
Control: forcemerge 891413 -1
On 25/02/18 21:22, Alexander Elbs wrote:
> On Sun, Feb 25, 2018 at 08:17:54PM +0000, Chris Boot wrote:
>> On 25/02/18 14:19, Alexander Elbs wrote:
>>> On Sun, Feb 25, 2018 at 12:17:28AM +, Chris Boot wrote:
>>>>
>>>> sstp
h. The old MD4 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)
tha
On 25/02/18 14:19, Alexander Elbs wrote:
> On Sun, Feb 25, 2018 at 12:17:28AM +0000, Chris Boot wrote:
>>
>> sstp-client isn't in Debian so there's a limit to how much I can help,
>> but did you try rebuilding the sstp-client packages against the latest
>&g
a limit to how much I can help,
but did you try rebuilding the sstp-client packages against the latest
ppp-dev?
The new version deliberately breaks ABI for plugins, but there are
mechanisms for dealing with that in Debian. Any compiled ppp plugins
will need to be rebuilt against the new versio
Control: notfound -1 poppler/0.26.5-2+deb8u1
Control: found -1 poppler/0.26.5-2+deb8u3
Control: notfound -1 poppler/0.48.0-2+deb9u2
On 19/02/18 12:48, Chris Boot wrote:
> I will follow up this bug with a PDF that exhibits the problem and a
> couple of screenshots of the issue in a few m
.
libpoppler64 on stretch does not exhibit the problem. This appears to be
restricted to jessie.
I will follow up this bug with a PDF that exhibits the problem and a
couple of screenshots of the issue in a few minutes.
Best regards,
Chris
--
Chris Boot
bo...@debian.org
On 17/02/18 08:03, Emilio Pozuelo Monfort wrote:
> Control: tags -1 confirmed
>
> On 11/02/18 22:04, Chris Boot wrote:
>> Package: release.debian.org
>> Severity: normal
>> User: release.debian@packages.debian.org
>> Usertags: transition
>>
>> Hi r
On 11/02/18 21:04, Chris Boot wrote:
> Note that connman seems to be a package to newly depend on ppp-dev and
> builds a pppd plugin but it doesn't use my dh_ppp helper. I will be
> filing a bug against that package (including a patch) shortly. Even
> without said patch a binNMU i
On 11/02/18 21:38, Chris Boot wrote:
[snip]
> I have prepared a patch for this issue which I will attach to this bug
> once it is submitted and I have a bug number to add to the changelog.
For ease I have created a Merge Request on Salsa:
https://salsa.debian.org/debian/connman/merge_requ
Package: src:connman
Severity: important
Dear Maintainer,
I am the maintainer of ppp and am planning an upload of a new version of
ppp which breaks the pppd plugin ABI. The new version is currently in
experimental, and connman builds fine against this new version, but the
ppp plugin included in t
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: transition
Hi release team folks,
I have just uploaded a new version of ppp to experimental. That upload
requires packages that build pppd plugins to be rebuilt due to a change
in the pppd ABI. I w
or not. Whether this is done by asking for a
password anyway or by some other means is up for debate.
Is this what you meant?
If so I will bring it up for discussion on the busybox-users mailing list.
Best regards,
Chris
--
Chris Boot
bo...@debian.org
signature.asc
Description: OpenPGP digital signature
C library, as broken.
To facilitate this busybox-static always prefers to run its own applets,
including dpkg, rather than the system-supplied binaries; if your system
is sufficiently broken that you are running busybox ash, it's a safe
assumption that your system tools are also hosed.
Th
at gcc points
at gcc-7 (>= 7.2.0-1~) in sid and, as far as I can tell, it also applies
to m68k.
To me this is really a gcc bug, and the fix belongs there. busybox has a
real interest in remaining small on several architectures, and I really
don't believe a workaround like this belong
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
scsi_mod.use_blk_mq
shouldn't have to care and the kernel should do the right
thing for me.
Chris
--
Chris Boot
bo...@debian.org
e 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
t here unless someone who is actually involved in
maintaining this stuff (and who knows how it works) steps up to help.
HTH,
Chris
--
Chris Boot
bo...@debian.org
signature.asc
Description: OpenPGP digital signature
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
seems at least related somehow.
HTH,
Chris
--
Chris Boot
bo...@debian.org
Package: src:linux
Version: 4.14.7-1
Followup-For: Bug #883413
Dear kernel maintainers,
This problem is still occuring with the latest 4.14 upload. Once this
warning has happened, prolonged operation leads to spurious OOM kills of
system processes which makes the system unusable.
Best regards,
C
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 tr
Package: src:linux
Version: 4.14.2-1
Severity: important
Tags: upstream
Hi kernel maintainers,
I've just switched to the 4.14 kernel and pretty quickly hit a strange
(to me) sequence of WARN_ON_ONCE() followed by NUT's upsd getting killed
by the OOM killer despite it not being in a restricted cgr
Package: src:shairport-sync
Severity: minor
Tags: patch upstream security
Owner: bo...@debian.org
Forwarded: https://github.com/mikebrady/shairport-sync/issues/619
I'm raising this bug as the maintainer of shairport-sync for tracking
this security issue in shairport-sync. The bug does NOT affect t
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
that should 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
1 - 100 of 254 matches
Mail list logo