able=1 quiet appears in the above results of (2) and
> (3) despite the fact that I had deleted/removed
> GRUB_CMDLINE_LINUX_DEFAULT="ipv6.disable=1 quiet" from /etc/default/grub.
I'll need to see the full contents of /etc/default/grub and
/boot/grub/grub.cfg immediately afte
In /etc/hosts, I ensure that # does not appear in front of lines that
> mention IPv6 hosts
>
> 15. Reboot machine
>
> Result: IPv6 traffic is NOT blocked. IPv6 traffic is re-enabled
These symptoms indicate to me that the equivalent of ipv6.disable=1 is
being set somewhere else
Control: tag -1 fixed-upstream
On Tue, Dec 04, 2018 at 08:05:13PM +0100, Michael Biebl wrote:
> On Wed, 22 Aug 2018 00:40:15 +0200 Michael Biebl wrote:
> > On 8/21/18 23:50, Colin Watson wrote:
> > > Can somebody explain what it achieves, other than churn? cron still
> &
eing
older. If you don't have anything constructive to add to the report,
please don't add noise.
--
Colin Watson [cjwat...@debian.org]
on graph a bit
more would result in a significant increase of bug reports against
backports.
If I were a more active BTS admin then TBH I'd be inclined to just do
this, but since I'm pretty inactive I thought it best to ask around.
--
Colin Watson [cjwat...@debian.org]
" anyway.
I hope this verbal description is clear enough, but if not let me know
and I can probably put together a patch.
Thanks,
--
Colin Watson [cjwat...@debian.org]
, although presumably there would be compatibility
concerns with changing it.
(I noticed this because I tried to use dpkg_vendor_derives_from in
openssh, and then Jeremy Bicha pointed out to me that it broke:
https://salsa.debian.org/ssh-team/openssh/commit/2df9bff12640a33749f0f20ae806b6efac32711
quot;stdout not open for writing!\n".
Oops, thanks. Fixed upstream:
https://git.savannah.gnu.org/cgit/man-db.git/commit/?id=d272bc3e81db44100467f720689ca2992d19f976
--
Colin Watson [cjwat...@debian.org]
On Wed, Nov 14, 2018 at 05:02:08AM +, peter green wrote:
> keymapper depends on python-yapps2 which does not appear to exist, did
> you mean to depend on python-yapps?
Urgh, yes, silly mistake, sorry! Upload on its way.
--
Colin Watson
weeks ago ...
--
Colin Watson [cjwat...@debian.org]
fix.
Much appreciated, thanks! I've cancelled my NMU.
--
Colin Watson [cjwat...@debian.org]
ng an ugly implementation-detail
workaround.)
Regards,
--
Colin Watson [cjwat...@debian.org]
diff -u yapps2-2.2.1/debian/changelog yapps2-2.2.1/debian/changelog
--- yapps2-2.2.1/debian/changelog
+++ yapps2-2.2.1/debian/changelog
@@ -1,3 +1,11 @@
+yapps2 (2.2.1-2.1
ntry_point
ModuleNotFoundError: No module named 'pkg_resources'
yapps2 needs to depend on python3-pkg-resources.
Thanks,
--
Colin Watson [cjwat...@debian.org]
(man -w tfmtodit hpftodit afmtodit); do src/lexgrog "$F"; done
/usr/share/man/man1/tfmtodit.1.gz: "tfmtodit - create font files for use with
groff -Tdvi"
/usr/share/man/man1/hpftodit.1.gz: "hpftodit - create font description files
for use with groff -Tlj4"
any-amd64 any-arm64],
I think this doesn't quite work because ttf-dejavu-core installs the
relevant font file (DejaVuSans.ttf) to a different path, and it isn't
one of those that configure.ac looks in; configure.ac will need to be
patched to look in that path as wel
> No objections, thanks.
>
> Thanks. Colin - feel free to upload, bearing in mind that the window
> for getting fixes into the 9.6 point release closes this weekend.
Thanks. Uploaded.
--
Colin Watson [cjwat...@debian.org]
y later version
> right now.
> Downgrading to openssh-client 7.7p1-4 fixes the issue.
Can you post your ~/.ssh/config, editing out anything sensitive if
necessary? I can't reproduce this problem myself.
--
Colin Watson [cjwat...@debian.org]
low. I'd need more evidence to
determine that there's an endless-loop-type bug here.
--
Colin Watson [cjwat...@debian.org]
in buggy postinst scripts.
I think this bug was introduced very recently; the offending commit
appears to be 9f02cb6fae8a822092ef504f46cbdd0a4f5547c2.
--
Colin Watson [cjwat...@debian.org]
-signed-template on i386; these are still built and in use.
Thanks,
--
Colin Watson [cjwat...@debian.org]
Control: reassign -1 openssl 1.1.1-1
Control: affects -1 openssh
On Mon, Oct 29, 2018 at 12:48:32AM +0100, Bernhard Übelacker wrote:
> Am 28.10.2018 um 19:23 schrieb Colin Watson:
> > Thanks for the investigation. (Note also that the OpenSSH version in
> > question is the one tha
quot;
- LINUX_ROOT_DEVICE="ZFS=${rpool}${bootfs}"
+ LINUX_ROOT_DEVICE="ZFS=${rpool}${bootfs%/}"
;;
esac
Thanks,
--
Colin Watson [cjwat...@debian.org]
nce, then it could easily
end up confused about which is the current scan code set (see the
changes to query_mode in particular) and so end up using the wrong set,
or possibly even send a nonsense command somehow. It seems worth
testing if you can.
--
Colin Watson [cjwat...@debian.org]
iguration, but only if it's different from what's already
there".
However, I think GRUB can at least manage to delete all but one entry
from the same distributor rather than all of them, and if it finds one
remaining entry then it can modify that rather than writing a brand new
variable. As I understand it, that would probably be enough to fix this
bug?
--
Colin Watson [cjwat...@debian.org]
tboot environments on arm64, and the other
makes it impossible to boot on Intel Apollo Lake systems. The proposed
debdiff is attached.
Thanks,
--
Colin Watson [cjwat...@debian.org]
diff -Nru grub2-2.02~beta3/debian/.git-dpm grub2-2.02~beta3/debian/.git-dpm
---
difference? Unfortunately this is a little complicated
as it will require doing a local build of the Debian OpenSSH source
package in order to reduce the dependency; let me know if you need help
with setting this up.
--
Colin Watson [cjwat...@debian.org]
https://salsa.debian.org/grub-team/grub/commit/014ba384bb8ac9869f2ccd2692f8ae05641d5bec
Did I do something wrong, or is this a dpkg bug?
Thanks,
--
Colin Watson [cjwat...@debian.org]
tribution.
This is Debian Policy version |policy_version|, released on |policy_date|.
.. toctree::
- :maxdepth: 3
+ :maxdepth: 4
:numbered:
ch-scope
@@ -31,7 +31,7 @@ This is Debian Policy version |policy_version|, released on
|policy_date|.
.. toctree::
:caption: Append
depth?
diff --git a/doc/xsl/common.xsl b/doc/xsl/common.xsl
index cfa406d..6115fba 100644
--- a/doc/xsl/common.xsl
+++ b/doc/xsl/common.xsl
@@ -12,4 +12,6 @@
1
+ 3
+
Thanks,
--
Colin Watson [cjwat...@debian.org]
rts against yapps2 ...).
--
Colin Watson [cjwat...@debian.org]
er Oracle changed its license to AGPL-3 in
> version 6.0.
Over the total lifetime I'm still content with this decision. :-)
--
Colin Watson [cjwat...@debian.org]
Thanks for your patch there, which looks as
reasonable as it's likely to get - I'm having a few unrelated
difficulties getting a test environment completely working, but I'll
upload as soon as I've sorted that out.
--
Colin Watson [cjwat...@debian.org]
clue users into the fact that cabal-install works better with them? I
think at least Recommends for HTTPS support would be justified on the
modern internet.
Thanks,
--
Colin Watson [cjwat...@debian.org]
key exchange patch, which is
already a significant maintenance headache).
The author of this patch set sent it upstream here:
https://bugzilla.mindrot.org/show_bug.cgi?id=2817
I'd very much rather wait for it to be accepted there.
Thanks,
--
Colin Watson [cjwat...@debian.org]
The first exception is probably my fault somehow; I'm doing this in
spare moments so haven't worked out the details. However, the second
exception is because there is code in a Python 3 module that's using the
Python 2 print syntax.
Please could you fix the port by converting
Scanner.print_line_with_pointer to Python 3 print syntax?
Thanks,
--
Colin Watson [cjwat...@debian.org]
#x27;Running tests___')?
This is hopefully just a matter of converting the print statements in
examples/calc.g and examples/xml.g to Python 3 syntax (since yapps2
itself now inserts "from __future__ import print_function" and thus
requires parsers to use the new syntax).
--
Colin Watson [cjwat...@debian.org]
the
preparser to avoid this problem.
--
Colin Watson [cjwat...@debian.org]
y and I
don't think you need to do this. I will consider your patch but have
been busy on a project at work that has a deadline of Wednesday, so
please hold off as if this patch is wrong it will be complicated to
unwind properly. I promise I'll look at it ASAP after Wednesday.
--
Colin Watson [cjwat...@debian.org]
it/parted.git/commit/?id=ba5e0451b51c983e40afd123b6e0d3eddb55e610),
since that'll be slightly more convenient at the next upstream release
(git will automatically drop it rather than me having to resolve a
conflict). It'll be in my next upload.
--
Colin Watson [cjwat...@ubuntu.com]
t;
> we are down to two users in testing with one of them fixed in
> experimental.
Upstream committed the necessary changes to switch to the 1.1 API
earlier this month, so that should be in OpenSSH 7.9. There's usually a
release every few months, so I think we should be OK to just w
d by a change in OpenSSH, this is really a
VMware bug; I'd encourage you to report it to them.
--
Colin Watson [cjwat...@debian.org]
using VMware, or is there anything else interesting about your
network setup?
Does passing -o 'IPQoS lowdelay throughput' to ssh help?
--
Colin Watson [cjwat...@debian.org]
sort out
an interoperability issue with conch first.
--
Colin Watson [cjwat...@debian.org]
stable already requested in #906861.
Ack, as the maintainer. Thanks.
--
Colin Watson [cjwat...@debian.org]
> XUL addons are no longer supported.
Yeah, I think it's time to put this package to bed. ftpmaster, please
remove it.
Thanks,
--
Colin Watson [cjwat...@debian.org]
>
> Did you have time to look at this patch?
Can somebody explain what it achieves, other than churn? cron still
works just fine on systemd-based systems ...
--
Colin Watson [cjwat...@debian.org]
free(pkblob);
> + free(sig);
> return authenticated;
> }
>
This bit has the same memory leak problem that I noticed in Sébastien's
backport for stretch: https://bugzilla.mindrot.org/show_bug.cgi?id=2898,
but the backported fix
; Test failed: 2018-08-14 00:00:37 Tuesday
Is this consistently reproducible? I think I've seen this locally on
occasion, but it's always gone away when I tried to debug it.
--
Colin Watson [cjwat...@debian.org]
On Fri, Aug 17, 2018 at 05:46:10PM +0200, Somebody else wrote:
> On Fri, Aug 17, 2018 at 4:42 PM Colin Watson wrote:
> > No, that change was added a long time ago. The change that caused the
> > symptoms you observe was the addition of
> > debian/patches/linuxefi_disa
ode is in general
necessary to fit the generally-understood SB security model;
unfortunately your custom setup sits in a corner case that we hadn't
previously heard much about and so isn't handled right now.
--
Colin Watson [cjwat...@debian.org]
vel of course, but
you can contact us at feedb...@launchpad.net, or #launchpad on freenode.
--
Colin Watson [cjwat...@debian.org]
Hi Ben,
pagein has gone through some considerable re-working since this bug
report and I can't reproduce this issue. Do you mind re-trying with the
latest version to check if it is now fixed.
Regards,
Colin
On Tue, 20 Jun 2017 17:34:20 +0200 Ben Wiederhake
wrote:
> Package: pagein
&
> On 13 Aug 2018, at 22:29, Pierre-Elliott Bécue wrote:
>
[..]
>>
>
> Dear Colin,
>
> As this bug is not fixable by ourselves (it's not specifically a
> mailman-web bug), may I close this bug?
>
> Cheers!
>
Good morning Pierre-Elliott,
Yes,
. Either preconv needs to understand
enough about the input to avoid encoding the argument to .tm (although I
wonder what this would do if the input text were in some more exotic
encoding), or .tm needs to evaluate \[...] escapes, or we need to accept
that this debugging command will pro
rather have a single code path that does the right thing without the
need for options. I'm currently testing a patch that directly
implements restarting of partial downloads in the LWP-based code, which
should supersede this.
Thanks,
--
Colin Watson [cjwat...@debian.org]
https://lists.mindrot.org/mailman/listinfo/openssh-unix-dev) would
be a good place.
Thanks,
--
Colin Watson [cjwat...@debian.org]
t, but not all the pieces have been put together yet.
--
Colin Watson [cjwat...@debian.org]
If so, the more
details of what you're doing the better.
Philipp and Luca, if you could have a look at this in case it's a
regression in the SB work, that'd be great.
Thanks,
--
Colin Watson [cjwat...@debian.org]
to reproduce the bug so that I can experiment? My
efforts at zen-debugging this aren't really getting anywhere fast.
Thanks,
--
Colin Watson [cjwat...@debian.org]
ersion
comparison algorithm:
$ dpkg --compare-versions 1:25.2+1-8 gt 47.0 && echo yes
yes
So I think you need to go into quite a lot more detail about exactly
what is failing ...
--
Colin Watson [cjwat...@debian.org]
hat was part of what source package management features like this were
trying to reduce).
I'm aware my comments here are mostly Ubuntu-specific; this is not only
because it's what I have most experience of, but also because I'm pretty
sure that ubuntu.series is the only kind of vendor series I've ever seen
in Debian source packages. It's possible I've missed some.
--
Colin Watson [cjwat...@debian.org]
quot;libqtgui4-perl based frontend
> might need to be removed") then.
That's now fixed, so as far as debconf is concerned you can remove
qt4-perl.
--
Colin Watson [cjwat...@debian.org]
On Wed, Jul 25, 2018 at 10:23:49AM +0800, Matthias Klumpp wrote:
> 2018-07-25 5:51 GMT+08:00 Lisandro Damián Nicanor Pérez Meyer
> :
> > On Thu, 19 Jul 2018 at 14:04, Colin Watson wrote:
> >> Simple enough: once you've installed the new version, "dpkg-reconfigure
&g
the ways that Steve and others have pointed out, I don't think it's a
good use of time to try to improve the tooling.
I second Steve's opinion that, in the aggregate, this feature is
actively harmful to downstreams (notwithstanding some individual cases
where i
On Sun, Jul 22, 2018 at 11:40:40AM +0100, Colin Watson wrote:
> Do you know of a good support/bug contact for OpenVZ? I'm not familiar
> with it at all, and I think we need some idea of what the problem is
> there before we even have a clue about what a reasonable workaround in
>
is
there before we even have a clue about what a reasonable workaround in
OpenSSH might be. (Disabling the sandbox doesn't count as reasonable
here, at least not long-term.) Have you asked the hosting provider if
they know what might be going on, or if they have an upstream
pB
> %pB\%.. (press h for help or q to quit)$-R MAN_PN=ls(1) less
Sorry for the delay in getting back to you. Please could you run "sudo
strace -f -o man.trace -s 1024 man ls", and attach the resulting
man.trace file in an email to me?
--
Colin Watson [cjwat...@debian.org]
On Sat, Jul 21, 2018 at 02:22:16PM +0200, gregor herrmann wrote:
> On Sat, 21 Jul 2018 15:13:30 +0300, Niko Tyni wrote:
> > Not quite but we're close now (thanks again Colin!). The old Qt frontend
> > and the corresponding build dependency on libqtgui4-perl are still there
>
On Thu, Jul 19, 2018 at 01:43:09PM -0300, Lisandro Damián Nicanor Pérez Meyer
wrote:
> El jueves, 19 de julio de 2018 07:08:43 -03 Colin Watson escribió:
> > Sorry for dropping this on the floor for so long! I've reviewed this
> > and tested it on a Debian KDE stretch system
mmit.
Nowadays, task-kde-desktop happens to pull debconf-kde-helper in via
apper, so most people probably have it; but we should probably
explicitly add it to the task.
--
Colin Watson [cjwat...@debian.org]
bout held modifier keys. You'll probably need
to use a short but non-zero timeout and press Escape instead.
(It's possible that more recent versions of the UEFI spec have improved
this; but if so then somebody would need to implement that in GRUB, and
it w
l check whether /proc and /sys are mounted and mount them if they
aren't, rather than assuming that they must be mounted.
Thanks,
--
Colin Watson [cjwat...@ubuntu.com]
x27;s no good reason for a
pure text filter to be talking to a socket.
I'm not yet sure what the best solution is. Fiddling about with SHELL
is obviously brittle. I could change man to call groff directly rather
than nroff, which would avoid the problem, but that's also brittle
est adding a dependency on
coreutils (>= 8.24), which introduced the feature of sync(1) being used
here.
I've put all this in a merge request:
https://salsa.debian.org/kernel-team/initramfs-tools/merge_requests/6
--
Colin Watson [cjwat...@debian.org]
On Mon, Jun 11, 2018 at 12:06:33PM +0100, Tim Small wrote:
> This patch works for me, please could we get it into buster?
Sorry for having missed this for so long; I've uploaded it now.
--
Colin Watson [cjwat...@debian.org]
On Mon, Jun 11, 2018 at 08:52:11PM +0200, Andreas Metzler wrote:
> On 2018-06-11 Colin Watson wrote:
> > On Sun, Jun 10, 2018 at 04:04:13PM +0200, Andreas Metzler wrote:
> > > yes, resetting IFS to its default value in confmodule helps.
>
> > Thanks. For completeness,
On Sun, Jun 10, 2018 at 04:04:13PM +0200, Andreas Metzler wrote:
> On 2018-06-10 Colin Watson wrote:
> > On Sun, Jun 10, 2018 at 03:03:28PM +0200, Andreas Metzler wrote:
> >> I have tried debugging the issue to get a minimal testcase. I have had
> >> some success
IFS="$_db_internal_IFS"
# Disgusting, but it's the only good way to split the line,
# preserving all other whitespace.
RET="${_db_internal_line#[! ][ ]}"
(If so, that would suggest that the problem might be specifically in
variable ass
file named "-" in the current directory.
> Try "touch ./-" , then run "man man" under strace -f and look for a stat
> of "-" in the trace.
This is a bug in less. Can you file it there separately? You can
reproduce it like this:
echo | strace -otrace less
fgrep '"-"' trace
--
Colin Watson [cjwat...@debian.org]
On Mon, May 14, 2018 at 04:03:51PM +0100, Ian Jackson wrote:
> Colin Watson writes ("Re: Bug#898627: man-db: dependency loop"):
> > I've never seen this myself. I guess it's due to man-db having
> > "interest-noawait /usr/share/man" in its triggers an
it as a cycle?
In any case I don't see any way to exclude man-db itself from the file
trigger if that's not the case.
CCing the dpkg maintainers.
--
Colin Watson [cjwat...@debian.org]
On Sat, Apr 28, 2018 at 06:00:00PM +0200, Mikulas Patocka wrote:
> On Fri, 30 Mar 2018, Colin Watson wrote:
> > Hm, OK. I mean, you could always just make sure that everything man
> > needs to call matches, but I guess that's a bit fiddly. Fixed upstream,
>
nge in OpenSSH, it's in fact because
it tickled a long-standing bug in Twisted. I've filed an upstream bug
about this with a patch, and assuming reviewers don't entirely hate it I
think we should cherry-pick the patch into Debian's twisted p
On Wed, Apr 04, 2018 at 06:35:12PM +, Thorsten Glaser wrote:
> Hi Colin,
> >tglase@tglase:~ $ man ls
> >man: nroff: Bad system call
> > Manual page ls(1) line ?/? (END) (press h for help or q to quit)
>
> any progress on this? Can I disable the seccomp stuff local
Control: tag -1 fixed-upstream
On Wed, Apr 04, 2018 at 01:22:09PM +0200, Salvo Tomaselli wrote:
> Here it is
Thanks. I've fixed your bug upstream, for the upcoming man-db 2.8.3:
https://git.savannah.gnu.org/cgit/man-db.git/commit/?id=c08cb8aedb7bb647e3f1ac6b9d009c0b174f8ba1
-
etc/xpra/ssl-cert.pem --ssl=on \
+ --bind=/run/xpra/system --auth=${AUTH} --socket-dirs=/run/xpra
--socket-permissions=666 \
+ --log-dir=/var/log --pidfile=/run/xpra.pid --debug=${DEBUG}
Thanks,
--
Colin Watson [cjwat...@ubuntu.com]
eproduce the
problem, so I'd like to collect more information in order to make sure
that I've really fixed it. Could you please run "strace -f -o
/root/man.trace -s 1024 man man" in the same environment, and attach the
resulting /root/man.trace file?
Thanks,
--
Colin Watson [cjwat...@debian.org]
ved to Libs.private? But I don't know the
libedit interface in detail, and in any case this is up to the libedit
maintainers, so reassigning.
Thanks,
--
Colin Watson [cjwat...@debian.org]
Control: reassign -1 groff 1.22.3-10
On Thu, Mar 08, 2018 at 07:35:49PM -0500, Anthony DeRobertis wrote:
> Running:
>
> man -Tutf8 /usr/share/man/ja/man5/apt_preferences.5.gz
>
> starts outputting the manpage, but then at some point switches over to
> outputting an (so far as I can tell) infinit
s, but I guess that's a bit fiddly. Fixed upstream,
and will be in 2.8.3:
https://git.savannah.gnu.org/cgit/man-db.git/commit/?id=770cd67aaf711b2cded9cbc2f9e503ca0f5e73ba
--
Colin Watson [cjwat...@debian.org]
On Mon, Mar 26, 2018 at 12:50:26PM +0200, Karsten Merker wrote:
> On Mon, Mar 26, 2018 at 12:47:18AM +0100, Colin Watson wrote:
> > I think this would be clearer reversed, i.e.:
> >
> > DEB_FRONTENDS=passthrough text newt
> > UDEB_FRONTENDS=passthrough text new
#x27;re trying to keep the package contents identical regardless of build
profile, since the main build system won't handle it in this case due to
the change in *_FRONTENDS?
Thanks,
--
Colin Watson [cjwat...@debian.org]
+++ serf-1.3.9/debian/changelog 2018-03-20 12:41:54.0 +
@@ -1,3 +1,10 @@
+serf (1.3.9-5) UNRELEASED; urgency=medium
+
+ * Backport r1712790 from upstream to fix a segfault in
+serf_bucket_aggregate_prepend when prepending a bucket to an empty list.
+
+ -- Colin Watson Tue, 20 M
Control: tag -1 fixed-upstream
On Sat, Mar 10, 2018 at 01:20:49PM +0800, Paul Wise wrote:
> On Thu, 2018-03-08 at 13:38 +0000, Colin Watson wrote:
> > Hmm, this doesn't seem to show a SIGSYS, and man exited 0.
>
> I added some debugging to groff and looked at the code.
>
On Thu, Mar 08, 2018 at 09:25:05PM +0800, Paul Wise wrote:
> On Thu, 2018-03-08 at 10:03 +0000, Colin Watson wrote:
> > They aren't useful, but I'm not sure why that means I should close
> > the bug.
>
> It is a standard line to get grumpy people who don't
}
+@units = @allowed_units;
}
# If the job is disabled and is not currently running, the job is not started
or restarted.
@@ -107,5 +111,5 @@ if ($action eq "start" || $action eq "restart") {
}
exit(0);
} else {
-exec '/bin/systemctl', @ARGV;
+exec '/bin/systemctl', @units if @units;
}
Thanks,
--
Colin Watson [cjwat...@debian.org]
t means I should close the
bug. Reassigning to man-db since this is due to the seccomp filtering
there and not a bug in groff.
Could you please run:
PIPELINE_DEBUG=1 strace -f -o man.trace -s 1024 man man | head -n1
... and attach both the full output on stderr and the resulting
man.trace file?
Th
colin@quokka:~$ apt-config dump |grep Users
Unattended-Upgrade::Automatic-Reboot-WithUsers "false";
colin@quokka:~$
I logged in from another PC and ran /usr/bin/users, it showed "colin
colin" as output, so that seems OK.
/Colin
On 6 March 2018 at 11:26, Bálint Réczey wrote
colin@quokka:~$ users
colin
colin@quokka:~$ loginctl
SESSIONUID USER SEAT TTY
79 1000 colinseat0
c1112 lightdm seat0
2 sessions listed.
colin@quokka:~$ w
10:59:28 up 1 day, 8:57, 1 user, load average: 0.28
Package: unattended-upgrades
Version: 0.93.1+nmu1
Severity: normal
I have
Unattended-Upgrade::Automatic-Reboot-WithUsers "false"
in my /etc/apt/apt.conf.d/50unattended-upgrades
I have noticed several times now when I arrive at my office in the morning that
my machine has rebooted even though I w
801 - 900 of 5522 matches
Mail list logo
