https://launchpad.net/~ahasenack/+archive/ubuntu/squid-
smp-1815852/+packages has test packages for cosmic with both fixes
(#1816006 and #1815852).
** Description changed:
+ [Impact]
+
+ * An explanation of the effects of the bug on users and
+
+ * justification for backporting the fix to
https://launchpad.net/~ahasenack/+archive/ubuntu/squid-
smp-1815852/+packages has test packages for cosmic with both fixes now
(#1816006 and #1815852).
--
You received this bug notification because you are a member of Ubuntu
Server, which is subscribed to the bug report.
** Changed in: ipmitool (Ubuntu)
Assignee: Jörg Frings-Fürst (jff-de) => Andreas Hasenack (ahasenack)
** Changed in: ipmitool (Ubuntu)
Status: Triaged => In Progress
** Changed in: ipmitool (Ubuntu)
Importance: Critical => High
--
You received this bug notification because you
** Changed in: squid (Ubuntu Cosmic)
Status: Triaged => In Progress
** Changed in: squid (Ubuntu Cosmic)
Assignee: (unassigned) => Andreas Hasenack (ahasenack)
--
You received this bug notification because you are a member of Ubuntu
Server, which is subscribed to the bug report.
** Description changed:
[Impact]
Squid doesn't work if "workers" is set in squid.conf.
[Test Case]
* install squid
sudo apt update && sudo apt install squid -y
* apply workaround for #1816006
sudo mkdir -p /var/run/squid
sudo chown proxy:proxy /var/run/squid
* confirm
Haw, here is a ppa with test packages for this bug:
sudo add-apt-repository ppa:ahasenack/squid-smp-1815852
It doesn't yet have the fix for the /var/run/squid missing directory,
I'll bring that back into cosmic next.
** Description changed:
[Impact]
-
- * An explanation of the effects of
** Description changed:
+ [Impact]
+
+ * An explanation of the effects of the bug on users and
+
+ * justification for backporting the fix to the stable release.
+
+ * In addition, it is helpful, but not required, to include an
+explanation of how the upload fixes this bug.
+
+ [Test
Package with that patch building in this PPA:
https://launchpad.net/~ahasenack/+archive/ubuntu/ipmitool-
segfault-1817307
Completely untested
** Changed in: ipmitool (Ubuntu)
Status: New => In Progress
** Changed in: ipmitool (Ubuntu)
Status: In Progress => Triaged
--
You
I'm seeing errors like these in your logs:
2019-02-22T22:01:48.488648Z 0 [ERROR] InnoDB: Unable to lock ./ibdata1 error: 11
2019-02-22T22:01:48.488703Z 0 [Note] InnoDB: Check that you do not already have
another mysqld process using the same InnoDB data or log files.
Maybe you have a stale mysql
With the patch being:
https://github.com/pjdhpe/ipmitool/commit/815aae70cf8dc9f0e1ba1923fc4ec3cc16d0d2f1
Can you easily test that? Do you need a package?
--
You received this bug notification because you are a member of Ubuntu
Server, which is subscribed to ipmitool in Ubuntu.
I wonder if it's this upstream bug:
https://github.com/ipmitool/ipmitool/issues/72
** Bug watch added: github.com/ipmitool/ipmitool/issues #72
https://github.com/ipmitool/ipmitool/issues/72
--
You received this bug notification because you are a member of Ubuntu
Server, which is subscribed
The latest release in the 3.6.x series seems to be 3.6.16. Almost all
releases since 3.6.10 list changes to the management plugin, but I
didn't spot anything obvious. Here are the release notes for each:
https://github.com/rabbitmq/rabbitmq-server/releases/tag/rabbitmq_v3_6_16
Regarding python-django-piston, there is no change yet. Upstream issue
unanswered (https://bitbucket.org/jespern/django-piston/issues/231
/switch-to-oauthlib), and no new upstream release since a long time.
rmadison shows ubuntu has had version 0.2.3 since precise, all the way
up to disco.
--
13 matches
Mail list logo
