Per comment #7 and
bzip2 | 1.0.8-5| jammy | source, amd64, arm64, armhf,
i386, ppc64el, riscv64, s390x
Setting that to fix released.
** Changed in: bzip2 (Ubuntu)
Status: Won't Fix => Fix Released
--
You received this bug notification because you are a member of U
** Changed in: grub-legacy-ec2 (Ubuntu)
Assignee: (unassigned) => Miriam España Acebal (mirespace)
** Changed in: ceph (Ubuntu)
Assignee: Miriam España Acebal (mirespace) => (unassigned)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
** Tags removed: server-triage-discuss
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1956166
Title:
Ubuntu 22.04 doesn't boot with xen
To manage notifications about this bug go to:
https://bugs.lau
Hi Colin,
so far I've seen it only on lgw01, but I didn't mass-submit it yet to try the
other builders.
Is there a better way than re-building/re-submitting to get onto the lcy02?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https:
** Changed in: python-xmlschema (Ubuntu)
Importance: Undecided => High
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1953363
Title:
[MIR] python-xmlschema, elementpath, importlib-resources
To ma
FYI: I've seen some shortening of the reported crashes going on.
For example in journal it was "x86_64-linux-gn" and in the build log it was
after "x86_64-linux-gnu-ld". The local (non fatal) crash I got eventually was
in "x86_64-linux-gnu-ld.bfd".
This might or might not be the same crash on LP
FYI - I wanted to look if I could make at least xen 4.16 available on
jammy as I really think a new LTS should have a newer xen, no matter how
much it is in universe :-)
But unfortunately there are awkward issues blocking further progress at
the moment, with platform dependent segfaults:
https://b
Public bug reported:
FTBFS in Jammy on LP infra:
https://launchpadlibrarian.net/580924961/buildlog_ubuntu-jammy-amd64.xen_4.16.0-1~ubuntu1~jammyppa4_BUILDING.txt.gz
https://launchpadlibrarian.net/581060687/buildlog_ubuntu-jammy-amd64.xen_4.16.0-1~ubuntu1~jammyppa6_BUILDING.txt.gz
Related PPA:
http
Assigning to Dave as discussed on #ubuntu-devel.
Thank you!
** Changed in: open-iscsi (Ubuntu)
Assignee: Christian Ehrhardt (paelzer) => Dave Jones (waveform)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
ht
You need to keep the tarball (derived by the front of the version) identical.
The following should do it:
https://code.launchpad.net/~paelzer/ubuntu/+source/cmark-gfm/+git/cmark-gfm/+ref/back-to-former
It reverts the debian/* portion as-is and the code portion as new patch in d/p/
Thereby it should
Ok, great - let me know if this worked out or if we all have missed a
dependency path :-)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1957050
Title:
[MIR] suitesparse-graphblas
To manage notifica
I tested the test of 249.5-2ubuntu2 (running autopkgtest against the dsc
file of 249.5-2ubuntu2) vs the binary systemd build in your PPA
(systemd_249.7-1ubuntu1~slyon0) + the dnsmasq from proposed.
And I got:
resolved: domain-restricted DNS servers ... ok
That means:
1. the fix is not in debian/t
Public bug reported:
I've seen that pandoc fails, example:
root@j:~# pandoc
pandoc: error while loading shared libraries: libcmark-gfm.so.0.29.0.gfm.0:
cannot open shared object file: No such file or directory
That made me wonder about this dependency and I found others like gitit:
root@j:~# g
This isn't a normal review, this is a source split, and we really have to see
what we gain/lose due to that:
- Version upgrade 5.0.5 -> 6.0 (better)
- Maintained and tracked individually (better)
- No tests (as before)
Since it is the same code as before not that much review is needed to be
repea
Bumped up the priority according to the MIR review in bug 1957050
** Changed in: suitesparse-graphblas (Ubuntu)
Importance: Low => Medium
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1958152
Titl
Note: There is only x86 and arm support (and 32 bit versions of that) in
ipxe, no need to plan for "more" architectures right now.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1890230
Title:
arm64
Hi Dimitri,
thanks for the suggestion - it isn't that we deliver "x86 on arm" instead it is
an arch-all package that - as of today - only has builds for x86. So while it
is a slight difference we "deliver x86 everywhere as intended" and the request
is to also deliver arm64.
On the ISO (also x86
Finally I found some time for this ...
Right now, we have those x86 binaries:
pkg:ipxe /usr/lib/ipxe/ipxe.efi -> /boot/ipxe.efi
pkg:grub-ipxe /boot/ipxe.efi
file /boot/ipxe.efi
#/boot/ipxe.efi: MS-DOS executable PE32+ executable (DLL) (EFI application)
x86-64, for MS Windows
As suggested t
New Collectd and UHD migrated and the NBS removals of 20.11 are done,
fully complete now.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1946856
Title:
Merge dpdk from Debian unstable for 22.04
To m
Due to the current state these won't auto-expire.
I agree with the discussion so far, and after half a year without
further insights or new ways to attack this I'd even say we close this
and if there is anything new that might help it can be re-opened. But
until then it will be off the recheck lis
Incomplete since we wait for the proper rebase for the backports as I
asked in early December.
** Changed in: qemu (Ubuntu Focal)
Status: Triaged => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launch
checks
- no translation present, but none needed for this case (user visible)?
Problems: None
** Changed in: libio-prompt-tiny-perl (Ubuntu)
Status: Confirmed => Incomplete
** Changed in: libio-prompt-tiny-perl (Ubuntu)
Assignee: Christian Ehrhardt (paelzer) => Lukas Märdian
** Tags added: server-next
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1957086
Title:
Autopkgtest systemd fail against dnsmasq 2.86 (22.04)
To manage notifications about this bug go to:
https://b
FYI: Also Fixed in jammy-release via
https://launchpad.net/ubuntu/+source/dpdk/21.11-1 which has our former
delta.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1939861
Title:
dpdk: ppc64el autopkgt
FYI: Fixed in jammy-release via
https://launchpad.net/ubuntu/+source/dpdk/21.11-1
** Changed in: dpdk (Ubuntu)
Status: New => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1946856
I'm slightly confused how DPDK 21.11 could migrate without fixing UHD, but it
did ?!
Right that was smooth_updates
https://lists.ubuntu.com/archives/ubuntu-devel/2021-December/041721.html
So the cleanup on UHD still is required, just not to get it migrating,
but towards the end of jammy to be abl
** Bug watch added: Debian Bug tracker #1001466
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1001466
** Also affects: uhd (Debian) via
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1001466
Importance: Unknown
Status: Unknown
--
You received this bug notification because
** Changed in: uhd (Ubuntu)
Status: New => In Progress
** Tags added: server-todo
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1957754
Title:
Incompatible with DPDK 21.11 - disable dpdk sup
FYI: UHD hiccup tracked in
https://bugs.launchpad.net/ubuntu/+source/uhd/+bug/1957754
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1946856
Title:
Merge dpdk from Debian unstable for 22.04
To manag
Public bug reported:
While I got positive feedback first when trying myself it was rather
clear that UHD is not compatible with DPDK 21.11 yet :-/
FTBFS on all DPDK arches:
https://launchpad.net/ubuntu/+source/uhd/4.1.0.5-1build1
Example:
/<>/host/lib/include/uhdlib/transport/dpdk/udp.hpp:61:13:
The armhf issues are resolved as well now, uploading no change rebuilds
for the remaining deps now (worked in PPA and Debian rebuild sniff
tests, so my hope is that those will work out smoothly).
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
** Tags removed: verification-needed
** Tags added: verification-done
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1925182
Title:
ERROR: Can't open /var/log/clamav/freshclam.log in append mode (che
** Tags removed: server-next
** Tags added: server-todo
** Tags added: bitesize
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1951779
Title:
tempfile command removed from debianutils
To manage not
** Also affects: ruby3.0 (Ubuntu)
Importance: Undecided
Status: New
** Changed in: ruby2.7 (Ubuntu)
Status: New => Invalid
** Changed in: ruby3.0 (Ubuntu)
Assignee: (unassigned) => Lucas Kanashiro (lucaskanashiro)
** Changed in: ruby3.0 (Ubuntu)
Importance: Undecided =>
It seems this is important for the 20.04.4 point release, so while we
try to prioritize all the cases in the queue for security review let us
set this to Critical + 20.04.4 Milestone.
** Changed in: adsys (Ubuntu)
Importance: Undecided => Critical
** Changed in: adsys (Ubuntu)
Milestone: N
** Changed in: libio-prompt-tiny-perl (Ubuntu)
Assignee: (unassigned) => Christian Ehrhardt (paelzer)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1951065
Title:
[MIR] libio-prompt-t
** Changed in: ubuntu-advantage-desktop-daemon (Ubuntu)
Assignee: (unassigned) => Lukas Märdian (slyon)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1954909
Title:
[MIR] ubuntu-advantage-deskt
** Changed in: libset-intspan-perl (Ubuntu)
Assignee: (unassigned) => Didier Roche (didrocks)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1956444
Title:
[MIR] libset-intspan-perl
To manage n
FYI - DPDK+OVS are uploaded but currently stuck in proposed due to no
more building armhf (needs an AA to resolve).
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1946856
Title:
Merge dpdk from Debia
Hi Mario,
Thanks for the request, given so much time passed I think we might want to
apply the full process of today which has much harder quality bars to pass.
Furthermore this got demoted so long ago that according to [1] no team
owns it anymore, not even for trusty or such. Therefore this won'
# FYI cleanup
# Minimal Reset (e.g. when switching dnsmasq)
killall dnsmasq
rm /tmp/dnsmasq*
dnsmasq --no-daemon --log-queries --log-facility=/tmp/dnsmasq.log
--conf-file=/dev/null --dhcp-leasefile=/tmp/dnsmasq.leases --bind-interfaces
--interface=router_eth42 --except-interface=lo
--dhcp-rang
As usual once you know what you search for the results are much better.
It turns out that it might be related to one of those reports:
- https://lists.thekelleys.org.uk/pipermail/dnsmasq-discuss/2022q1/016015.html
- https://lists.thekelleys.org.uk/pipermail/dnsmasq-discuss/2022q1/016069.html
But
Result of the repro:
#2 ipv6 fails and gets into a loop
dig @10.241.3.1 -t math.lab
#2a - Good case (dnsmasq 2.85)
root@j-dnsmasq-release:~# dig @10.241.3.1 -t math.lab
dnsmasq: query[] math.lab from 10.241.3.1
dnsmasq: config math.lab is NODATA-IPv6
; <<>> DiG 9.16.15-Ubuntu <<>>
Reproducing the case outside the systemd tests
(Commands on Ubuntu 22.04, with root permissions)
jammy-Proposed has dnsmasq 2.86 right now
apt update; apt upgrade -y; apt install dnsmasq-base
systemctl reset-failed systemd-networkd systemd-resolved
mkdir /run/systemd/resolved.conf.d
cat > /run/
Detailed Logs:
Before the test:
dnsmasq.log is identical
dnsmasq-vpn.log as well, except the version number
Good Case:
ubuntu@autopkgtest:~$ resolvectl query math.lab
math.lab: 10.241.3.3 -- link: testvpnrouter
-- Information acquired via protocol DNS in 20.8ms.
-- Data
Public bug reported:
Full log (same on all architectures):
https://autopkgtest.ubuntu.com/results/autopkgtest-jammy/jammy/arm64/s/systemd/20220106_214401_24d29@/log.gz
The test is from systemd:
https://github.com/systemd/systemd/blob/main/test/networkd-test.py#L619
Tail of the log:
```
ERROR: te
Thanky Yuang-Chen,
I first thought "Uh this request is a bit scarce", but I agree since this is
just a source split that should be fine.
Reference: Original MIR
https://bugs.launchpad.net/ubuntu/+source/fwupd/+bug/1536871
Build logs:
https://launchpadlibrarian.net/578322379/buildlog_ubuntu-jammy
While this is for CPC, Server team members work on it. Thereby I know
that while obviously we'd appreciate a faster review, this can happen
past 22.04 - but not much later. Also we have to face that the >=Focal
tasks still have some TODOs to even enter security review queue -
therefore this can't b
** Changed in: wireguard (Ubuntu)
Milestone: ubuntu-22.02 => ubuntu-22.04-feature-freeze
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1950317
Title:
[MIR] Wireguard
To manage notifications abo
** Changed in: glusterfs (Ubuntu)
Milestone: ubuntu-22.02 => ubuntu-22.04-feature-freeze
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1950321
Title:
[MIR] glusterfs
To manage notifications abo
** Changed in: python-asgiref (Ubuntu)
Milestone: ubuntu-22.02 => ubuntu-22.04-feature-freeze
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1953173
Title:
[MIR] python-asgiref
To manage notific
Hi,
in preparation for prioritizing various MIR items blocked on security review I
was setting those items of the server Team that are essential for 22.04 to
"Critical + Milestone @22.02 (=Feature Freeze)".
This is a foundation item, but I think it qualifies for the same, if you agree
I'd ask to
Backuppc and Fence agents are done quite a while ago, and since this
waited for so long we'd really appreciate getting this completed.
Nevertheless - makes me sad to say - of the many reviews blocked this is
one we could survive for a bit longer. Hence setting Prio:High and mid
year Milestone (last
Required for 22.04, setting Critical + Milestone 22.02 (FeatureFreeze)
** Changed in: wireguard (Ubuntu)
Importance: Undecided => Critical
** Changed in: wireguard (Ubuntu)
Milestone: None => ubuntu-22.02
--
You received this bug notification because you are a member of Ubuntu
Bugs, whic
Required for 22.04, setting Critical + Milestone 22.02 (FeatureFreeze)
** Changed in: glusterfs (Ubuntu)
Milestone: None => ubuntu-22.02
** Changed in: glusterfs (Ubuntu)
Importance: Undecided => Critical
--
You received this bug notification because you are a member of Ubuntu
Bugs, whic
Required for the new LTS Django in 22.04, setting Critical + Milestone
22.02 (FeatureFreeze)
** Changed in: python-asgiref (Ubuntu)
Importance: Undecided => Critical
** Changed in: python-asgiref (Ubuntu)
Milestone: None => ubuntu-22.02
--
You received this bug notification because you a
Hi Bernd,
I'm glad to heard that as we were not sure it would work well with fuse3.
As a reminder, the libs are co-installable it is "bin:fuse" vs "bin:fuse3" that
are conflicting.
So when you change that remember to also change fuse->fuse3.
In the meantime it was found that unionfs-fuse isn't se
FYI - I uploaded a revert to the open-vm-tools change to un-block image builds
for now.
But maybe this was a good wake-up call.
Please have a look at gvfs, union-fuse (here) and grub2, s390-tools, snapd,
xdg-desktop-portal in bug 1934510.
--
You received this bug notification because you are a
FYI - Uploaded a switch to fuse3 until bug 1956949 and bug 1934510 and
their deps are resolved.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1935665
Title:
open-vm-tools builds without fuse support
Indeed @Thomas, the question now it if everything from Ginggs initial
analysis is now ready to move "with it" or if we have to turn back open-
vm-tools for now until all is ready.
I have added bug tasks to the obvious ones (gvfs, unionfs-fuse) to bug 1956949.
But eventually all of the identified d
@Marco Trevisan - I subscribed you in case you want to steal the Desktop
POV to this from Didier.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1956949
Title:
CPC AWS jammy builds fail with: "fuse3
Also see
https://bugs.launchpad.net/ubuntu/+source/fuse3/+bug/1934510/comments/24
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1956949
Title:
CPC AWS jammy builds fail with: "fuse3 : Breaks: fuse"
FYI - we might have to tune that back to fuse2 until *all* dependencies
are ready, see bug 1956949 and bug 1934510
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1935665
Title:
open-vm-tools builds w
Hi,
some (qemu, open-vm-tools, fuse3 itself) started to land.
But do not do this in a rush, in bug 1956949 it was found that we need
to coordinate this more precisely to move "all at once" to avoid
conflicts between fuse <-> fuse3.
Therefore the question, would this be ready for upload now?
--
Hi,
some (qemu, open-vm-tools, fuse3 itself) started to land.
We'd need to have this fixed and ready as well now.
But do not do this in a rush, in bug 1956949 it was found that we need
to coordinate this more precisely to move "all at once" to avoid
conflicts between fuse <-> fuse3.
Therefore the
Hi,
some (qemu, open-vm-tools, fuse3 itself) started to land.
We'd need to have this fixed and ready as well now.
Right now we certainly have a release post last August, but right now we have
still a dependency to v2:
Package: snapd
Version: 2.53+21.10ubuntu1
Depends: adduser, apparmor (>= 2.10.9
Hi,
some (qemu, open-vm-tools, fuse3 itself) started to land.
We'd need to have this fixed and ready as well now.
But do not do this in a rush, in bug 1956949 it was found that we need
to coordinate this more precisely to move "all at once" to avoid
conflicts between fuse <-> fuse3.
Therefore the
: (unassigned) => Graham Inggs (ginggs)
** Changed in: open-vm-tools (Ubuntu)
Assignee: (unassigned) => Christian Ehrhardt (paelzer)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1956949
Ti
Hi Thomas,
hmm ... that might be fallout from the general move to fuse3.
See MIR bug
=> https://bugs.launchpad.net/ubuntu/+source/fuse3/+bug/1934510
And the links from there.
Ginggs did make an analysis back then if everything is ready to move:
=> https://lists.ubuntu.com/archives/ubuntu-devel/20
bin:fuse3 is now in main - thanks
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1934510
Title:
[MIR] fuse3 as a dependency of qemu 6.0 and GNOME apps
To manage notifications about this bug go to:
h
Hi John:
> and in ./debian/open-vm-tools-desktop.postinst
>
> Tested for and loaded fuse3.
There is no fuse3 kernel module.
Only the userspace changed.
$ modinfo fuse
name: fuse
filename: (builtin)
alias: devname:fuse
alias: char-major-10-229
alias: f
This bug was fixed in the package dnsmasq - 2.86-1.1
---
dnsmasq (2.86-1.1) unstable; urgency=medium
* Non-maintainer upload.
* Fix --address=/#/.. which was lost in 2.86. (closes: #995655)
-- Michael Biebl Wed, 10 Nov 2021 22:05:45 +0100
dnsmasq (2.86-1) unstable; urgenc
https://launchpad.net/ubuntu/+source/dnsmasq/2.86-1.1 built, blocked in
proposed by what looks like test issues not caused by dnsmasq.
** Changed in: dnsmasq (Ubuntu)
Status: In Progress => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which i
> Does it just need dropped from the platform seed's server component
Yes
> If so, please review:
> https://code.launchpad.net/~ubuntu-core-dev/ubuntu-seeds/+git/platform/+merge/413720
Reviewed by two now, feel free to push
--
You received this bug notification because you are a member of Ubun
** Changed in: chrony (Ubuntu)
Status: New => In Progress
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1946848
Title:
Merge chrony from Debian unstable for 22.04
To manage notifications abo
As you see in 2.85-1ubuntu2 I've reverted the last delta we had.
This is successful so far, on bug report int hat regard.
And since it also followed upstreams guidance on the overall case we will stick
to that.
There is a new version to sync now 2.86-1.1 which I'll trigger now.
** Changed in: d
Hi,
fuse3 was auto-demoted since the last update, but now open-vm-tools was changed
to use fuse3, and shows the expected component mismatch.
@Archive-Admins - please promote binary "fuse3" to main in jammy.
FYI: the bug to get fuse3 into open-vm-tools is bug 1935665
--
You received this bug not
I have updated open-vm-tools in debian and synced it to ubuntu - it uses
fuse3 now.
But (as expected) it depends not only on libfuse3 (that was already
promoted to main to easen the transition) but also on fuse3.
Hence I'd ask the Archive admins to please promote the binary "fuse3" to
resolve the
We ahve that in Jammy
snapd | 2.53+21.10ubuntu1 | jammy | source, amd64, arm64, armhf,
ppc64el, riscv64, s390x
Removing openssl task to not show this outdated update-excuse
** Tags removed: update-excuse
--
You received this bug notification because you are a member of Ubuntu
Bugs
** Changed in: dpdk (Ubuntu)
Milestone: None => ubuntu-22.02
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1946856
Title:
Merge dpdk from Debian unstable for 22.04
To manage notifications about
** Changed in: libvirt (Ubuntu)
Status: New => In Progress
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1946869
Title:
Merge libvirt from Debian unstable for 22.04
To manage notifications a
Hi Andrea,
thanks for the bug and fix.
This worked in the past with older/other qemu binaries.
I double checked my memory on this, but it indeed works.
#1 Focal with qemu 4.2
ubuntu@node-horsea:~$ uvt-simplestreams-libvirt --verbose sync --source
http://cloud-images.ubuntu.com/daily arch=armhf
Re-ping for gcc maintainers,
could we please have the default "fcf-protection" be not applied to
`-march=i486 -m16` ?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1940029
Title:
Default of fcf-pro
On Tue, Jan 4, 2022 at 9:25 PM Andreas Hasenack
<1950...@bugs.launchpad.net> wrote:
>
> I did some investigation in all of the contrib/ directories:
Thanks for that investigation, it seems most of them are unused or
really only a minor concern.
The two more interesting according to your analysis I
Thanks for the check Bryce, that confirms what I've found in my quick
look before.
At least from the archives POV only libsoup2.4-tests needs it.
And as you outlined it added "Add patch to treat tests based on php-xmlrpc as
unreliable" in 2.74.2-3.
And libsoup2.4-test are only in universe.
OTOH
Thereby the required TODOs are done AFAICS.
Feel free to add more of the recommended steps,
but until then this is New@ubuntu-security as it is waiting for the review.
** Changed in: glusterfs (Ubuntu)
Status: Incomplete => New
--
You received this bug notification because you are a membe
protection being unavailble on -march=i486 (LP: #1940029)
- d/p/u/lp-1932175-s390x-cpumodel-add-3931-and-3932.patch: add new 3931
and 3932 machines (LP: #1932175)
- d/p/u/lp-1940288-audio-Never-send-migration-section.patch: fix
migration with audio devices present (LP:
** Changed in: open-vm-tools (Ubuntu)
Assignee: Marco Trevisan (Treviño) (3v1n0) => Christian Ehrhardt
(paelzer)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1935665
Title:
open-vm-to
** Changed in: open-vm-tools (Ubuntu)
Status: Incomplete => In Progress
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1946836
Title:
Merge open-vm-tools from Debian unstable for 22.04
To man
@Bryce - while it seems this is "just a split" it also appears to be
unmaintained [1] on this page. What is the path forward here, is there
an alternative or is this no more needed, should we consider keeping it
in universe (removing it from the seeds)?
[1]: https://pecl.php.net/package/xmlrpc
**
This got auto-demoted due to the split of php -> php-xmlrpc.
Discussed in MIR bug 1956345 and once approved both have to be promoted to main
again.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/154770
This also let drop xmlrpc-epi out of main, see bug 1547700.
Once this one here is approved, both have to be promoted (again).
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1956345
Title:
[MIR] php-x
Public bug reported:
This isn't a real new MIR.
php-xmlrpc was in main as long as most history goes:
php-xmlrpc | 1:7.0+35ubuntu6 | xenial | all
php-xmlrpc | 1:7.0+35ubuntu6.1 | xenial-updates | all
php-xmlrpc | 1:7.2+60ubuntu1 | bionic | all
php-xmlrpc | 2:7.4+75
FYI - as planned (and now that cloud init is fixed) I'm planning to
upload this to Jammy without the path fix. There should be no issue with
that.
But planning ahead, there will later on be a backport of open-vm-tools 11.3.5
with that to >=Focal.
I checked
21.4-0ubuntu1~20.04.1
21.4-0ubuntu1~21.0
FYI Debian PR:
https://salsa.debian.org/vmware-packaging-team/pkg-open-vm-tools/-/merge_requests/12
PPA build: https://launchpad.net/~ci-train-ppa-service/+archive/ubuntu/4745
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bu
FYI Debian PR:
https://salsa.debian.org/vmware-packaging-team/pkg-open-vm-tools/-/merge_requests/12
PPA build: https://launchpad.net/~ci-train-ppa-service/+archive/ubuntu/4745
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bu
Patched and working fine in a test build of 11.3.5 for Debian.
Thanks to Marco and John for all the work.
trying to complete this into becoming an upload ...
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/b
*** This bug is a duplicate of bug 1946836 ***
https://bugs.launchpad.net/bugs/1946836
FYI Trying to get 11.3.5 + the compat for fuse3 in 1935665 done now.
That should be stable and fine for now.
Afterwards we can have a look if 12.0.0 (more changes) still fits in well.
I'm marking this a dup
On Mon, Dec 27, 2021 at 1:15 PM Krzysztof Gajda
<1770...@bugs.launchpad.net> wrote:
>
> Hi.
>
> This is real issue, because DKIM signing doesn't work without this fix
> (and amavisd-new marks incorrectly outbound emails as RelayedOpenRelay).
>
> Any chance to include this patch in LTS18 current upd
https://github.com/acassen/keepalived/commit/8f658000ff9fa8b67a81d29b4a73c6a3c1fc2c2b
was accepted upstream and is in
keepalived | 1:2.2.4-0.2 | jammy| source, amd64,
arm64, armhf, ppc64el, riscv64, s390x
I do not think this needs backports, setting fix released.
** C
901 - 1000 of 10121 matches
Mail list logo
