On 2/10/20 3:55 am, Ross Vandegrift wrote:
> On Thu, Oct 01, 2020 at 05:16:36PM +0200, tkoeck wrote:
>> is there an AMI image ID that is always the recent one?
>
> Instead of hardcoding an AMI somewhere, you can search to find the
> current release. With awscli, try something like this:
> $ aws e
Package: command-not-found
Version: 18.04.5-1
Followup-For: Bug #916783
Tags: patch
This patch seems to be working for me:
--- a/CommandNotFound/db/creator.py
+++ b/CommandNotFound/db/creator.py
@@ -88,6 +88,7 @@ class DbCreator:
"%s does not require an update (inputs unchanged)"
On Wed, Jan 16, 2019 at 11:43:57AM +0100, Aurelien Jarno wrote:
> I don't think the patch is correct. Debconf is not a registry, the
> canonical location for the configuration is the configuration files, not
> the debconf database. Quoting debconf-devel(7):
>
> "The issue to watch out for here is
Package: tzdata
Version: 2018i-0+deb9u1
Followup-For: Bug #704089
Dear Maintainer,
This is still a problem 4 years later, and I unexpectedly found myself
spending time to track it down when doing configuration
management. Can we please get the above patch applied *before* the
Buster soft-freeze o
I'm hitting a rather significant memory leak too. My HDD started
trashing and my machine became incredibly slow. At this point I
noticed xfce4-sensors-plugin was using about 2Gb of RAM.
$ uptime
11:15:14 up 51 days, 18:10, 1 user, load average: 3.30, 3.91, 3.68
$ top
PID USER PR NI
Package: monitoring-plugins-common
Version: 2.2-3
Severity: normal
Dear Maintainer,
*** Reporter, please consider answering these questions, where appropriate ***
* What led up to the situation?
I have a postfix installation where main.cf is configured like so:
-rw-r- 1 root root 2013 A
Package: euca2ools
Version: 3.3.1-1
Severity: normal
Tags: patch
Dear Maintainer,
* What led up to the situation?
Upgrading to Stretch, which upgraded python-requests (currently to
2.12.4-1).
* What exactly did you do (or not do) that was effective (or
ineffective)?
I tried to bundl
On Sun, Feb 05, 2017 at 08:56:58PM +0100, Thomas Goirand wrote:
> On 02/03/2017 04:15 AM, Adam Bolte wrote:
> > On closer inspection, the error from netstat is different. I missed
> > the "Reason: [Errno 2] No such file or directory: 'netstat'" line from
>
On closer inspection, the error from netstat is different. I missed
the "Reason: [Errno 2] No such file or directory: 'netstat'" line from
the original report, so I'm seeing a different bug.
If the netstat command isn't doing anything critical (as implied by
cloud-init otherwise working just fine
On Thu, Feb 02, 2017 at 02:22:12PM +0100, Thomas Goirand wrote:
> I don't see how Jessie would be affected, as there, net-base is
> still an essential package.
You are correct, and it certainly is installed into the AMIs in
question. I think the suggested cause is incorrect.
From the debug log:
I'm also confirming this issue exists in the jessie-backports package
version 0.7.7~bzr1156-1~bpo8+1. It's not fatal (networking still
works), but certainly something I noticed when creating new EC2 AMIs.
-Adam
signature.asc
Description: Digital signature
On 20/11/16 15:13, Raphaël Halimi wrote:
> Control: retitle -1 systemd-shim not fully compatible with systemd
> 232 Control: affects -1 policykit-1 policykit-1-gnome mate-polkit
>
> Le 20/11/2016 à 04:21, Adam Bolte a écrit : Right. I retitled the bug
> to more precisely describe t
It took about an hour to find this bug report, since I was looking for
changes related to consolekit, polkit, pam, etc. I've been using using
sysvinit-core to avoid systemd issues (systemd doesn't even boot for me
for some reason I don't care to investigate), so it didn't immediately
occur to me to
Is this a duplicate of #780392?
signature.asc
Description: Digital signature
This issue also affects rsyslog. I hit this when I upgraded a bunch of
servers, including an rsyslog server from wheezy to jessie.
There are still a few wheezy servers that have yet to be upgraded, but
now they are unable to send their logs to the jessie rsyslog server
due to what appears to be th
Hi believe I'm running into the same issue.
$ apt-cache policy lightdm cgmanager policykit-1 systemd-shim systemd
libpam-systemd sysvinit-core libvirt-daemon-system | grep -E -A1
'^[^[:space:]]+' | grep -v '^--$'
lightdm:
Installed: 1.10.3-3
cgmanager:
Installed: 0.33-2+deb8u2
policykit-1:
Insta
On Tue, 24 Mar 2015 05:27:54 +0100 Christoph Anton Mitterer
wrote:
> Just to add some more details:
> - The big difference from CDEmu to loopback is, that CDEmu actually
> emulates a CD drive (with all it's commands and interfaces), while the
> loopback method only makes an ISO image mountable
On Tue, 24 Mar 2015 05:27:54 +0100 Christoph Anton Mitterer
wrote:
> Just to add some more details:
> - The big difference from CDEmu to loopback is, that CDEmu actually
> emulates a CD drive (with all it's commands and interfaces), while
> the loopback method only makes an ISO image mountable
Package: libgcr-3-1
Version: 3.8.2-4
Severity: normal
Dear Maintainer,
The Online Accounts menu in gnome-control-center isn't working. The console
output includes the following:
libgcr-3.so.1: cannot open shared object file: No such file or directory
Failed to load module: /usr/lib/control-cente
Worked like a charm. I also posted more detailed instructions on how to
downgrade to 1.10.4 on my blog, in case anyone else is still stuck on
this.
http://systemsaviour.com/?p=514
Cheers,
Adam
signature.asc
Description: This is a digitally signed message part
20 matches
Mail list logo
