For me adding the symlink will not create issues with the SONAME bump,
old binaries (ie which were not relinked) will use libaio.so.1 while
newly linked binaries will use the new soname libaio.so.1t64 as the
package maintainers expects.
I have re-started the conversation in
Actually it's not needed in the udeb package, but in the normal
libaio1t64 package.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2067501
Title:
Ubuntu noble is missing libaio.so.1 compat symlink
Public bug reported:
Hi,
Would it be possible to backport this creation of a compat symlink
libaio.so.1 in noble please:
https://git.launchpad.net/ubuntu/+source/libaio/commit/?h=applied/ubuntu/devel=e0165fd654888dac2677dfdca3a67e9c56ebcb7c
Third party tools depending on libaio, like typically
Hi,
This is not the scope of this bug, but will podman be upgraded and
follow upstream releases regularly in Ubuntu 22.04, or it will stay at
version 3.4.x during the whole lifetime of jammy ? Indeed this kind of
package is still in fast pace mode, and even Red Hat is upgrading it its
stable RHEL
Note: you can test if zstd support works (or not) by trying to use this
zstd:chunked image produced by the zstd:chunked developer in the podman
team:
docker run --rm --pull=always gscrivano/zstd-chunked:fedora whoami
Which for now fails with:
fedora: Pulling from gscrivano/zstd-chunked
Public bug reported:
Hi,
It seems the Docler/Moby team is about to release Docker 22.04 (they
have recently updated the milestone name from 21.x). This release will
bring among many other things, the support for zstd compressed images.
Zstd support is something we would like to leverage in our
Hi,
I could successfully validate that the fix works. I initially installed
the current official jammy package, it was hanging again, then I
installed your ppa repo and upgraded the packages, and it worked. See
the following relevant part of my testing (ran in Docker):
Setting up liblmdb0:amd64
Hi,
I guess to reproduce this I should find my DNS configuration and be able
to hardcode it in Docker so it works the same way for everyone. But my
environment is a corporate one, so I don't know possible it is to
reproduce this with public DNS.
Anyway,
Note: it also impacts debian:testing and debian:sid which also ship bind
9.18. Should this bug report be reported to Debian instead ?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1964686
Title:
** Tags added: jammy
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1964686
Title:
Command "host non-existent-host-name" hangs forever in Ubuntu jammy
To manage notifications about this bug go to:
Public bug reported:
Hi,
We have found that on Ubuntu jammy the command "host non-existent-host-
name" hangs for ever, while it was working with Ubuntu impish. We tested
that under Docker:
> cat Dockerfile
ARG UBUNTU_VERSION
FROM ubuntu:${UBUNTU_VERSION}
RUN apt-get update && apt-get install
11 matches
Mail list logo
