Output of this command:
xvfb-run -a strace -f -s 500 -o bla make
TEST_FILES=t/06190_Dialog_Scan_Image_Sane.t test > works.txt 2>&1
the strace output I discarded
** Attachment added: "works.txt"
Output of this command:
xvfb-run -a make TEST_FILES=t/06190_Dialog_Scan_Image_Sane.t test >
fails.txt 2>&1
** Attachment added: "fails.txt"
https://bugs.launchpad.net/ubuntu/+source/gscan2pdf/+bug/1860592/+attachment/5322204/+files/fails.txt
--
You received this bug notification because
To more easily reproduce this, without having to run the whole test
suite until you get to test 06190, run:
xvfb-run -a make TEST_FILES=t/06190_Dialog_Scan_Image_Sane.t test
from inside the deb source package directory.
--
You received this bug notification because you are a member of Ubuntu
Hello Christian, thanks for filing this bug in Ubuntu.
I think your point number 2 has been discussed many times in the past,
and it's one of the opinionated differences between debian systems and,
say fedora ones. In debian, the opinion is that services should be
running with sensible defaults
Bugs last updated on 2020-01-20 (Monday)
Date range identified as: "Tuesday triage"
Found 10 bugs
LP: #1812822 - +(In Progress) [qemu] - Guest crashed when
detaching the ovs interface device
No action needed
LP: #1854529 - *+(In Progress) [ndctl] - DEP8 tests to
satisfy MIR
Just adding a comment to refresh our "60 days timeout" timer, as this
bug was not dropped and is being worked on.
--
You received this bug notification because you are a member of Ubuntu
Server, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1845506
Title:
Libvirt
Was the sru for disco released before eoan's?
--
You received this bug notification because you are a member of Ubuntu
Server, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1851091
Title:
Fresh Eoan upgrade fails to boot dom0 with message "decoding failed"
(kernel
** Tags added: server-triage-discuss
--
You received this bug notification because you are a member of Ubuntu
Server, which is subscribed to postfix in Ubuntu.
https://bugs.launchpad.net/bugs/1860315
Title:
Default installation should be Local Only
To manage notifications about this bug go
# bind9 & friends, due to openssl
I have a few uploads of mine stuck on the openssl migration: bind9,
bind-dyndb-ldap, debian-installer, isc-dhcp.
## openssl
Looking at openssl, krb5/i386[1] called my attention again, since I
fixed an i386 problem recently. But this time I don't know what to do.
** Changed in: ndctl (Ubuntu)
Assignee: Rafael David Tinoco (rafaeldtinoco) => Andreas Hasenack
(ahasenack)
--
You received this bug notification because you are a member of Ubuntu
Server, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1854529
Title:
DEP8 te
Going through my triage backlog, from the holidays
Bugs last updated on 2019-12-16 (Monday)
Date range identified as: "Tuesday triage"
Found 18 bugs
LP: #1847157 - *+(Fix Committed) [open-vm-tools] - memory leaks in
open-vm-tools
- package vanished from the sru report and upload queues, added a
Still in our queue.
--
You received this bug notification because you are a member of Ubuntu
Server, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1850933
Title:
after upgrade 19.04 to 19.10, apache serves php code
To manage notifications about this bug go to:
Thanks for filing this bug in Ubuntu.
During an upgrade, services are restarted, and if it turns out the new
version doesn't like the old config, it will fail to restart. I think
this is indeed what happened here, given the output of testparm that is
attached to this report:
WARNING: The
Just to be clear, the smb.conf config file you attached already
registers as invalid even in the samba version you started your upgrade
from (eoan: 4.10.7)
--
You received this bug notification because you are a member of Ubuntu
Server, which is subscribed to samba in Ubuntu.
Bugs last updated between 2020-01-10 (Friday) and 2020-01-12 (Sunday) inclusive
Date range identified as: "Monday triage"
Found 17 bugs
Worth commenting on:
LP: #1838046 - (Triaged)[autofs] - Autofs with CIFS
prevents laptop suspend
- added a comment detailing what I think the
Upstream committed more changes in this area, I have to check out what
the latest patches look like. Upstream's intention I think was to switch
wrappers to the krb5 one, which would then call smbspool if no krb5 auth
is involved.
--
You received this bug notification because you are a member of
Thanks for the confirmation, Günter. We don't have identified a fix yet,
what's pending is to try with the latest version of autofs, currently
5.1.6 in Ubuntu Focal. After that, if the bug is still happening, try
patches from
Another variable in this equation, of course, is cifs itself: the
kernel, and/or cifs-utils, the userland package.
--
You received this bug notification because you are a member of Ubuntu
Server, which is subscribed to autofs in Ubuntu.
https://bugs.launchpad.net/bugs/1838046
Title:
Autofs
If I understood this correctly, the bionic task is then invalid? Setting
to "incomplete" for now.
** Changed in: grub-legacy-ec2 (Ubuntu Bionic)
Status: Confirmed => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Server, which is subscribed to the bug
Thanks for filing this bug in Ubuntu.
This is the error:
dic 16 13:19:16 gustavo-net mysqld[17036]: 2019-12-16T16:19:16.596897Z 0
[ERROR] Can't start server: Bind on TCP/IP port: Address already in use
dic 16 13:19:16 gustavo-net mysqld[17036]: 2019-12-16T16:19:16.596910Z 0
[ERROR] Do you
I'm just going through my old triage backlog and saw this update. Did
you update both ends of the vpn connection, server and client, and still
get the incorrect dns update?
--
You received this bug notification because you are a member of Ubuntu
Server, which is subscribed to the bug report.
What's the status of this? I don't see open-vm-tools in the SRU report
(https://people.canonical.com/~ubuntu-archive/pending-sru.html), nor do
I see this package in the bionic unapproved queue
(https://launchpad.net/ubuntu/bionic/+queue?queue_state=1_text
=open-vm-tools), nor disco. And disco is
I just uploaded new bind9 to focal, it's still building, but I didn't
mention this bug in d/changelog. I'll close it manually once it's
published.
** Changed in: bind9 (Ubuntu)
Status: Triaged => In Progress
--
You received this bug notification because you are a member of Ubuntu
Server,
** Merge proposal unlinked:
https://code.launchpad.net/~ahasenack/ubuntu/+source/bind9/+git/bind9/+merge/377604
--
You received this bug notification because you are a member of Ubuntu
Server, which is subscribed to bind9 in Ubuntu.
https://bugs.launchpad.net/bugs/1856211
Title:
Oops, back pedalling on this:
doko: I'm taking advantage of you reintroducing python-mako (py2),
to build haproxy with it (not a runtime dep). Is that why you reintroduced it,
or are other packages needing it?
ahasenack, ginggs: I just removed python2-scipy, so it's not needed for
that
python-marko (py2) was reinstated, using it.
** Changed in: haproxy (Ubuntu)
Status: New => In Progress
** Changed in: haproxy (Ubuntu)
Assignee: (unassigned) => Andreas Hasenack (ahasenack)
** Changed in: haproxy (Ubuntu)
Importance: Undecided => High
--
You received
** Tags added: update-excuse
** Tags added: ftbfs
--
You received this bug notification because you are a member of Ubuntu
Server, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1859685
Title:
google-cloud-print-connector FTBFS (focal)
To manage notifications about
** Merge proposal unlinked:
https://code.launchpad.net/~ahasenack/ubuntu/+source/bind9/+git/bind9/+merge/377604
--
You received this bug notification because you are a member of Ubuntu
Server, which is subscribed to bind9 in Ubuntu.
https://bugs.launchpad.net/bugs/1856211
Title:
** Merge proposal unlinked:
https://code.launchpad.net/~ahasenack/ubuntu/+source/bind9/+git/bind9/+merge/377604
--
You received this bug notification because you are a member of Ubuntu
Server, which is subscribed to bind9 in Ubuntu.
https://bugs.launchpad.net/bugs/1856211
Title:
I'm updating bind9 to 9.14, which was mentioned in the upstream bug
report in the phrase "With 9.14 the problem should be much less
prominent", for which I asked for clarification.
--
You received this bug notification because you are a member of Ubuntu
Server, which is subscribed to bind9 in
Hello,
I believe your record has an incorrect syntax. It should be:
@ IN CAA issue
where is a number. Hence the complain from the tool that
character position 14 is not a valid number.
The line you used gives an error already when reloading the zone, with
the same message.
Can you please
Confirmed fixed in the new version I'm preparing, I'll include a mention
of this bug in its d/changelog.
--
You received this bug notification because you are a member of Ubuntu
Server, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1856367
Title:
systemd-resolvd
It's a force-badtest across the board:
ubuntu-release:force-badtest notary/0.6.1~ds1-4
revno: 4077
committer: Steve Langasek
branch nick: hints-ubuntu
timestamp: Wed 2019-11-13 15:35:28 -0800
message:
badtest notary
--
You received this bug notification because you are a member of Ubuntu
= Bugs touched on Monday (2020-01-13) =
Bugs last updated on 2020-01-13 (Monday)
Date range identified as: "Tuesday triage"
Found 14 bugs
LP: #1583688 - +(Confirmed) [libvirt]- libvirt-sock not
recreated on service restart
- incomplete, couldn't reproduce it with current version of
This was fixed in 4.9.2-0ubuntu6:
xen (4.9.2-0ubuntu6) focal; urgency=medium
* Build-depend on python2-dev.
* Depend on python2.
* Build using python2.
* Build-depend on lmodern.
-- Matthias Klose Mon, 13 Jan 2020 14:51:35 +0100
** Changed in: xen (Ubuntu)
Status: Confirmed
Hi,
libxen-4.9 is used at runtime, and contains the dynamic library. libxen-
dev is used for development and contains the header files (*.h), the
dynamic library .so link, and the static library. That's how it is
supposed to be. Just adding /usr/includexenstat.h to libxen-4.9 wouldn't
work, as
Hello,
After ua attach and after esm is enabled, the esm credentials are stored
in /etc/apt/auth.conf.d/90ubuntu-advantage. You need apt 1.0.1ubuntu2.23
or higher in order to make use of this file, and the ubuntu-advantage-
tools package's Depends field has that correctly set.
a) which version
No new info at the moment, bug still in our queue.
--
You received this bug notification because you are a member of Ubuntu
Server, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1712589
Title:
Apache2 mod-wsgi segfault on double reload
To manage notifications about
Passing by ack'ing that this bug is still valid and in our queue.
--
You received this bug notification because you are a member of Ubuntu
Server, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1673357
Title:
Munin core plugin "if_" doesn't work
To manage
That version is present in disco, eoan and focal
grub-ipxe | 1.0.0+git-20190109.133f4c4-0ubuntu2| disco| all
grub-ipxe | 1.0.0+git-20190109.133f4c4-0ubuntu2| eoan | all
grub-ipxe | 1.0.0+git-20190109.133f4c4-0ubuntu2| focal| all
Rafael, I think
# Tuesday triage (bugs touched on the previous Monday)
## 2020-01-07 (Tuesday triage)
14 bugs, of which just one was "new"
LP: #1858374 - (New)[ipxe] - add --id=ipxe to
easly identify ipxe menu entry
1 server-next not touched in 60 days:
LP: #1673357 - (Triaged)
mysql_upgrade: Got error: 2002: Can't connect to local MySQL server
through socket '/var/run/mysqld/mysqld.sock' (2) while connecting to the
MySQL server
Please take a look at the mysql log file in /var/log/mysql (IIRC), see
if it has hints about mysql didn't start.
--
You received this bug
There is no /etc/systemd file shipped with the openssh-server deb
package. That directory is reserved for local overrides. The package
ships the systemd service files correctly in /lib/systemd/service.
--
You received this bug notification because you are a member of Ubuntu
Server, which is
>From the dpkg history log, it looks like you are mixing mariadb and
mysql. I'm not sure transitioning from one to the other is supported,
and in any case it's asking for trouble in my opinion. I suggest you
pick one of the two.
For your current machine, I also suggest the following to try to fix
** Tags added: update-excuse
--
You received this bug notification because you are a member of Ubuntu
Server, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1828228
Title:
corosync fails to start in unprivileged containers - autopkgtest
failure
To manage
** Tags added: update-excuse
--
You received this bug notification because you are a member of Ubuntu
Server, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1855943
Title:
net-snmp merge for focal (v5.8)
To manage notifications about this bug go to:
** Tags added: update-excuse
--
You received this bug notification because you are a member of Ubuntu
Server, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1855568
Title:
pcs depends on python3-tornado (>= 6) but it won't be installed
To manage notifications about
** Tags added: update-excuse
--
You received this bug notification because you are a member of Ubuntu
Server, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1852122
Title:
ocfs2-tools is causing kernel panics in Ubuntu Focal
(Ubuntu-5.4.0-9.12)
To manage
Hello,
On Fri, Jan 10, 2020 at 5:11 AM Christian Ehrhardt
wrote:
> - rdkit 201909.1-1 completed in Debian to bring postgresql-12-rdkit
> The old delta was just forcing it to test pg-11
> Can be synced IMHO
> @Andreas do you agree?
Yes, but it is failing in debian ci, so we might
** Changed in: squid (Ubuntu)
Assignee: (unassigned) => Andreas Hasenack (ahasenack)
** Changed in: squid (Ubuntu)
Status: New => In Progress
--
You received this bug notification because you are a member of Ubuntu
Server, which is subscribed to squid in Ubuntu.
Public bug reported:
Removing autopkgtest-satdep:amd64 because I can't find pygopherd:amd64
pygopherd was removed in focal:
Removed from disk on 2020-01-02.
Removal requested on 2020-01-02.
Deleted on 2020-01-02 by Steve Langasek
(From Debian) RoQA; python2, not in testing;
** Also affects: pcs (Ubuntu)
Importance: Undecided
Status: New
** Changed in: pcs (Ubuntu)
Status: New => In Progress
** Changed in: pcs (Ubuntu)
Assignee: (unassigned) => Rafael David Tinoco (rafaeldtinoco)
--
You received this bug notification because you are a member
which will the case with 9.16 when it comes out.
All that being said, I'm about to merge 9.11.14, which will have the fix
mentioned in comment #2
** Changed in: bind9 (Ubuntu)
Assignee: (unassigned) => Andreas Hasenack (ahasenack)
--
You received this bug notification because you are
Hello,
On Mon, Jan 6, 2020 at 10:04 PM Bryce Harrington
wrote:
> * nut: Argparse is flagging an error from specifying --xsltproc-opts
> multiple times (I think?) which perhaps may be a behavioral change
> from either py2 to py3, or else from optparse to argparse.
> - "error: argument
Public bug reported:
$ sudo apt-get build-dep ./
sudo: setrlimit(RLIMIT_CORE): Operation not permitted
Note, using directory './' to get the build dependencies
Reading package lists... Done
Building dependency tree
Reading state information... Done
Some packages could not be installed.
Public bug reported:
haproxy runs debian/dconv/haproxy-dconv.py when building its
documentation. That script is py2, and requires python2 and python-
marko.
python-marko is gone and is an NBS currently. The src:marko package now
only builds the python3 version, so we need to convert
Hello all,
On Mon, Jan 6, 2020 at 10:07 AM Bryce Harrington
wrote:
>
> New Version in Debian Unstable
> --
> high bind9 1:9.11.14+dfsg-1
> 1:9.11.5.P4+dfsg-5.1ubuntu5
I'm glad you got it working. The page at https://ubuntu.com/advantage
should also have enough information to let you have the attachment
token.
I'll close the bug, thanks for getting back to us.
** Changed in: ubuntu-advantage-tools (Ubuntu)
Status: New => Invalid
--
You received this
It's just the release notes task of this bug that is marked as fixed,
meaning the release notes got an entry about this known problem.
On Wed, Jan 1, 2020, 15:34 Gerald Hopf wrote:
> Why is this tagged as fixed when obviously it was never fixed?
>
> --
> You received this bug notification
Hello,
the "ua" command is available in ubuntu-advantage-tools package from the
trusty-updates pocket, which at the moment is version 19.6~ubuntu14.04.3
You probably have an older version installed, where the ESM support was
via "enable-esm user:pass" command.
** Changed in:
Thanks for filing this bug in Ubuntu.
You seem to have an invalid configuration setting in your
/etc/samba/smb.conf:
$ testparm ./smb.conf
WARNING: The "syslog" option is deprecated
WARNING: Ignoring invalid value 'server' for parameter 'security'
Load smb config files from ./smb.conf
WARNING:
** Bug watch added: Debian Bug tracker #946643
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=946643
** Also affects: bind9 (Debian) via
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=946643
Importance: Unknown
Status: Unknown
--
You received this bug notification because
Hi,
On Thu, Dec 12, 2019 at 2:10 PM Steve Langasek
wrote:
> Many tests need changes to annotate their dependencies as to whether they
> need a version of the package that matches the target arch or not. In the
> case of bind9, it looks like the problematic dependency chain is bind9 ->
>
)
Importance: Medium
Assignee: Andreas Hasenack (ahasenack)
Status: In Progress
--
You received this bug notification because you are a member of Ubuntu
Server, which is subscribed to bind9 in Ubuntu.
https://bugs.launchpad.net/bugs/1856211
Title:
bind9utils: drop har
That NAS seems pretty old, you might have to live with the configuration
change to downgrade the protocol to SMB1. Maybe you can ssh into it and
find out what samba version it's running, and tweak its config manually.
I find it weird that samba, even from 2011, would reject SMB2
connections, or
On Wed, Dec 11, 2019 at 9:22 PM Bryce Harrington
wrote:
> ###
> ### bind9 (Andreas) ###
> ###
>
> bind9 blocking netbase (5.6 to 5.8) for 5 days
> Regressions
> bind9/1:9.11.5.P4+dfsg-5.1ubuntu4: i386 (log, history)
>
> * bind9
Hello,
I just tried apt operations on a fresh eoan (ubuntu 19.10) system, with
ua installed (but not attached, which is the default), and it works just
fine. The hook also just exits 0 when called directly:
root@e1:~# /usr/lib/ubuntu-advantage/apt-esm-hook
root@e1:~# echo $?
0
I also installed
Has anybody engaged with upstream, as suggested by david in comment #15?
Filing a bug with Debian would also help, as we are carrying the same
package with no ubuntu modifications.
--
You received this bug notification because you are a member of Ubuntu
Server, which is subscribed to rsync in
Most bugs were triaged already. Got a spam bug, the usual mysql
restart error due to something else already listening on its socket,
and a clamav update request without proper justification.
Here I requested again that an upstream discussion be started:
LP: #1528921 - (Confirmed) [rsync]
Hello!
Ubuntu won't just update versions in a stable release without proper
justification, as there is always a risk that a new version also
introduces new bugs. We prefer to patch specific problems instead.
This page outlines the requirements for updating a stable release:
Hello,
you are not describing a bug in the apache2 package or software,
therefore I'll mark this bug as invalid.
** Changed in: apache2 (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Server, which is subscribed to apache2 in
Hello, thanks for filing this bug in Ubuntu.
You seem to have another mysql process/server already running, maybe it
was installed by some other means other than the deb package from
Ubuntu?
2019-12-09T13:27:34.937052Z 0 [Note] Server hostname (bind-address):
'127.0.0.1'; port: 3306
Link to the diff: https://github.com/sosreport/sos/pull/1772/files
--
You received this bug notification because you are a member of Ubuntu
Server, which is subscribed to sosreport in Ubuntu.
https://bugs.launchpad.net/bugs/1842495
Title:
Grafana support on Ubuntu
To manage notifications
In what rsync version and ubuntu release did you see it, @stooneb?
--
You received this bug notification because you are a member of Ubuntu
Server, which is subscribed to rsync in Ubuntu.
https://bugs.launchpad.net/bugs/1528921
Title:
rsync hangs on select(5, [], [4], [], {60, 0}
To manage
** Changed in: multipath-tools (Ubuntu)
Status: New => Triaged
** Changed in: multipath-tools (Ubuntu)
Importance: Undecided => Medium
--
You received this bug notification because you are a member of Ubuntu
Server, which is subscribed to multipath-tools in Ubuntu.
Please retry on a more recent Ubuntu release, at least xenial (16.04)
and preferably bionic (18.04) or even eoan (19.10). I'll mark the bug
incomplete until there is an update.
In particular, 16.04 and later are using systemd, not sysv, which is a
big change in boot ordering.
** Changed in:
Regarding the dbus error, I have never seen that before. I'll try to get
a 20.04 desktop running.
--
You received this bug notification because you are a member of Ubuntu
Server, which is subscribed to samba in Ubuntu.
https://bugs.launchpad.net/bugs/1855758
Title:
error when connecting to
I'm not sure we can add that to the package. There is a world-wide
effort to get rid of the SMB1 protocol. Even modern windows machines
have it disabled by default I think.
You are probably better off in changing the configuration of your NAS to
support more modern protocols. Have you inspected
A patch is expected. I just added the info to the bug to show what is
going on.
--
You received this bug notification because you are a member of Ubuntu
Server, which is subscribed to samba in Ubuntu.
https://bugs.launchpad.net/bugs/1849859
Title:
smb printing fails
To manage notifications
Samba 4.11.x disabled SMB1 by default both for the client and the server
(https://www.samba.org/samba/history/samba-4.11.0.html):
SMB1 is disabled by default
---
The defaults of 'client min protocol' and 'server min protocol'
have been changed to SMB2_02.
This means
Für das druckproblem, ja
--
You received this bug notification because you are a member of Ubuntu
Server, which is subscribed to samba in Ubuntu.
https://bugs.launchpad.net/bugs/1849859
Title:
smb printing fails
To manage notifications about this bug go to:
Upstream work which might help, although it's about using the smbspool
krb5 wrapper, it also has changes to the smbspool binary:
https://gitlab.com/samba-team/samba/merge_requests/961
** Summary changed:
- error when connecting to smb server
+ smb printing fails
--
You received this bug
On Mon, Dec 9, 2019 at 10:08 AM Bryce Harrington
wrote:
>
> New Version in Debian Unstable
I carded autofs, net-snmp, cifs-utils (this last one to get back on
top of debian, because we diverged).
But feel free to "steal" them if I don't get to them in time and you
have spare cycles.
--
A new bug please, I'm focusing on the printing case for this one.
--
You received this bug notification because you are a member of Ubuntu
Server, which is subscribed to samba in Ubuntu.
https://bugs.launchpad.net/bugs/1849859
Title:
error when connecting to smb server
To manage
Hello,
the /var/log/ubuntu-advantage.log file will have more details, but:
**
do not just attach it to this bug, as it contains private data! In particular,
YOUR UA CREDENTIALS are in that file!
**
Inspect it, look for backtraces or other informative
13 bugs, plus 2 in the not-touched-in-NNN-days category.
Some comments:
LP: #1854395 - (New)[apache2]- apachectl
configtest segmentation fault
I also couldn't reproduce the above one, but it strikes me as odd to
have both nss and ssl installed for ssl support in apache, and
This came up in our "untouched in 180 days" bug triage. I found
https://github.com/christgau/wsdd/issues/19 where someone apparently
packaged this, but not conforming to the debian policy (as stated by the
author), and no ITP bug yet. I found a debian WNPP bug
I'm a bit wary of mixing sssd and samba/winbind together like this. But
sounds like alternatives would be an option?
--
You received this bug notification because you are a member of Ubuntu
Server, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1844173
Title:
*** This bug is a duplicate of bug 1612517 ***
https://bugs.launchpad.net/bugs/1612517
2019-12-02T18:42:45.437945Z 0 [ERROR] [MY-77] [Server]
/usr/sbin/mysqld: Error while setting value
*** This bug is a duplicate of bug 1612517 ***
https://bugs.launchpad.net/bugs/1612517
The config option NO_AUTO_CREATE_USER is not part of the default config,
and therefore won't be taken care of during the upgrade to mysql 8. You
should remove it manually and then retry the installation
** Changed in: haproxy (Ubuntu)
Assignee: (unassigned) => Andreas Hasenack (ahasenack)
** Description changed:
Upstream haproxy has the concept of an LTS release, and a stable (non-
LTS) release. Currently, these are (see table at
http://www.haproxy.org/):
stable: 2.1.x
sta
, we will merge it manually into ubuntu.
1. https://lists.ubuntu.com/archives/ubuntu-
devel/2019-December/040853.html
** Affects: haproxy (Ubuntu)
Importance: Medium
Assignee: Andreas Hasenack (ahasenack)
Status: In Progress
** Tags: ahasenack
--
You received this bug
** Merge proposal unlinked:
https://code.launchpad.net/~ahasenack/ubuntu/+source/talloc/+git/talloc/+merge/376296
--
You received this bug notification because you are a member of Ubuntu
Server, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1440381
Title:
please
This is fixed actually, the failing test in 8.0.18 is another one.
8.0.17 is what failed with the lz4 error.
** Changed in: mysql-8.0 (Ubuntu)
Status: Triaged => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Server, which is subscribed to mysql-8.0
If the test just wants to check if lz4 exists and runs, then its output
should be redirected to /dev/null, maybe that's the best fix here?
--
You received this bug notification because you are a member of Ubuntu
Server, which is subscribed to mysql-8.0 in Ubuntu.
mysql in focal already has a fix for this:
- --exec lz4 -V 2> $LZ4_EXEC_LOG
+ --exec lz4 -V > $LZ4_EXEC_LOG 2>&1
But that just makes sure we get the lz4 version in the log file,
regardless of the lz4 version.
But this is odd, since the result file doesn't have that string, so it
will never
In eoan it's in stderr, with 1.9.1-1:
andreas@nsnx:~$ lz4 -V
*** LZ4 command line interface 64-bits v1.9.1, by Yann Collet ***
andreas@nsnx:~$ lz4 -V 2>/dev/null
andreas@nsnx:~$ lz4 -V > /dev/null
*** LZ4 command line interface 64-bits v1.9.1, by Yann Collet ***
andreas@nsnx:~$
In
Hi Dustin,
can you nack the MP please?
--
You received this bug notification because you are a member of Ubuntu
Server, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1843729
Title:
byobu ftbfs in eoan
To manage notifications about this bug go to:
On Mon, Dec 2, 2019 at 1:57 PM Bryce Harrington
wrote:
> New Version in Experimental
> --
> low haproxy 2.1.0-2 2.0.10-1
Let's not update this, as the 2.0 x
ssword
>
>
> This line must have this form if we want print works.
>
> I hope you will find this information useful.
>
>
> Greetings
>
> El jue., 28 nov. 2019 a las 20:10, Andreas Hasenack ()
> escribió:
>
> > *** This bug is a duplicate of bug 1849859 ***
>
301 - 400 of 3671 matches
Mail list logo
