@Paride Thanks for your help and explanations. Yeah I know what multi-
arch does although I didn't know about 'Multi-Arch: foreign' - so thank
you very much for the pointers.
@Christian I have uploaded the updated package to mentors on Sunday. It
was prepared on Ubuntu, though, I guess it is
FYI the re-upload of a fuse3 open-vm-tools happened yesterday and it migrated
to jammy-release.
Any issues with the images?
--
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
@aakef - while I said unionfs-fuse might not be a blocker I'd still
recommend to upload the change switching to fuse3. On comment #12 it
seemed you are close. Any chance to get this done or did unexpected
blockers show up while trying?
The unionfs-fuse task here is assigned to Graham; @ginggs -
FYI according to
https://people.canonical.com/~ubuntu-archive/germinate-output/ubuntu.jammy/rdepends/ALL/fuse
https://people.canonical.com/~ubuntu-archive/germinate-output/ubuntu.jammy/rdepends/ALL/fuse3
This should no more be an issue now, so open-vm-tools will switch to
fuse3 again in the next
Good catch, I filed a separate bug for ntfs-3g:
https://bugs.launchpad.net/ubuntu/+source/ntfs-3g/+bug/1957756
and mentioned it in the MIR bug LP: #1934510.
** No longer affects: ntfs-3g (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
** Also affects: ntfs-3g (Ubuntu)
Importance: Undecided
Status: New
--
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"
To
It was pointed out on IRC that ntfs-3g Pre-Depends on fuse which should
probably be changed
--
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 :
This bug was fixed in the package gvfs - 1.48.1-2ubuntu5
---
gvfs (1.48.1-2ubuntu5) jammy; urgency=medium
* debian/patches/new-meson-build.patch:
- don't use positional arguments in the 18n merge function, fix the
build with the new meson version
-- Sebastien Bacher
** Changed in: gvfs (Ubuntu)
Status: New => Fix Committed
--
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"
To manage
@Bernd "not being seeded" means that unionfs-fuse isn't in the set of
packages that define what goes into the Ubuntu 'main' component. In
summary this is done by choosing some "seed" packages and computing
their (build-)dependency tree, see [1,2] if you want to know more.
Automatic syncing of
** Changed in: gvfs (Ubuntu)
Assignee: Didier Roche (didrocks) => Sebastien Bacher (seb128)
--
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
This bug was fixed in the package open-vm-tools - 2:11.3.5-1ubuntu2
---
open-vm-tools (2:11.3.5-1ubuntu2) jammy; urgency=medium
* d/control, d/rules: go back to fuse3 until all other
packages are ready (LP: #1956949)
-- Christian Ehrhardt Mon, 10 Jan
2022 14:44:22 +0100
**
Hi Christian,
I will actually just prepare an upload to debian (via mentors) and then
let that get pulled into ubuntu. I don't know what "unionfs-fuse isn't
seeded (anymore)" means - automatic pulling from debian is not done
anymore or something else?
--
You received this bug notification
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
I will prepare an upload of unionfs-fuse that switches to libfuse3
during the next days.
--
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 :
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
** Changed in: launchpad-buildd
Status: New => Invalid
--
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"
To manage
@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"
#1 - Package: gvfs-fuse
This build for Desktop already switched to the version3 as you see in
"libfuse3-3 (>= 3.2.3)".
But it still depends on the v2 user-tools. That mismatch needs to be resolved
for 22.04 and it will need to switch to fuse3.
I'm adding a src:gvfs task for that to switch to
The gvfs one is just an error in the revert of the delta we have to not
use fuse3 yet, gvfs-fuse should depends on fuse3 now as it does in
Debian, desktop will fix that one
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
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:
=>
That installation by launchpad-buildd happens in the container that
livecd-rootfs runs in, not in the chroot that livecd-rootfs is busy
building. If you look more closely at the build log you can see it
succeeding earlier on. We may indeed have to update launchpad-buildd to
use fuse3, but it's
It's launchpad-buildd that installs fuse:
https://git.launchpad.net/launchpad-
buildd/tree/lpbuildd/target/build_livefs.py#n89
** Also affects: launchpad-buildd
Importance: Undecided
Status: New
** Changed in: fuse3 (Ubuntu)
Status: New => Invalid
--
You received this bug
Sounds like something is trying to pull fuse on the image?
--
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"
To manage
25 matches
Mail list logo
