| Summary: | dev-util/meson: update can break installation if version changes while building other packages (emerge --jobs) | ||
|---|---|---|---|
| Product: | Gentoo Linux | Reporter: | Pacho Ramos <pacho> |
| Component: | Current packages | Assignee: | Mike Gilbert <floppym> |
| Status: | RESOLVED CANTFIX | ||
| Severity: | normal | CC: | flow, gentoo, ionen, sam, williamh |
| Priority: | Normal | ||
| Version: | unspecified | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Package list: | Runtime testing required: | --- | |
A hack would be to crank up the >= in the eclass every time a new version comes out. Ran into the same updating a stable VM just now, was also xorg. (In reply to Sam James from comment #1) > A hack would be to crank up the >= in the eclass every time a new version > comes out. Always happy to see that bumped ASAP not to have to worry about build systems starting to use newer meson features (and needing to >= BDEPEND manually). But sounds that could realistically only be done for stable users (i.e. bump when it's stabled), still better than nothing. |
I was updating my system and it died with: >>> Install x11-base/xorg-server-21.1.3 into /var/tmp/portage/x11-base/xorg-server-21.1.3/image meson install -C /var/tmp/portage/x11-base/xorg-server-21.1.3/work/xorg-server-21.1.3-build --destdir /var/tmp/portage/x11-base/xorg-server-21.1.3/image ninja: Entering directory `/var/tmp/portage/x11-base/xorg-server-21.1.3/work/xorg-server-21.1.3-build' ninja: no work to do. ERROR: Build directory has been generated with Meson version 0.59.4, which is incompatible with the current version 0.60.3. * ERROR: x11-base/xorg-server-21.1.3::gentoo failed (install phase): * install failed * * Call stack: * ebuild.sh, line 127: Called src_install * environment, line 3404: Called meson_src_install * environment, line 2656: Called meson_install * environment, line 2595: Called die * The specific snippet of code: * "$@" || die "install failed" * * If you need support, post the output of `emerge --info '=x11-base/xorg-server-21.1.3::gentoo'`, * the complete build log and the output of `emerge -pqv '=x11-base/xorg-server-21.1.3::gentoo'`. * The complete build log is located at '/var/log/portage/x11-base:xorg-server-21.1.3:20220121-161822.log'. * For convenience, a symlink to the build log is located at '/var/tmp/portage/x11-base/xorg-server-21.1.3/temp/build.log'. * The ebuild environment file is located at '/var/tmp/portage/x11-base/xorg-server-21.1.3/temp/environment'. * Working directory: '/var/tmp/portage/x11-base/xorg-server-21.1.3/work/xorg-server-21.1.3' * S: '/var/tmp/portage/x11-base/xorg-server-21.1.3/work/xorg-server-21.1.3' * One or more packages are either masked or have missing dependencies: * * >=x11-base/xorg-server-21.1[udev] pulled in by: * (x11-base/xorg-drivers-21.1:0/0::gentoo, installed) * * The resume list contains packages that are either masked or have * unsatisfied dependencies. Please restart/continue the operation * manually, or use --skipfirst to skip the first package in the list and * any other packages that may be masked or have missing dependencies. * * The following package has failed to build, install, or execute postinst: * * (x11-base/xorg-server-21.1.3:0/21.1.3::gentoo, ebuild scheduled for merge), Log file: * '/var/log/portage/x11-base:xorg-server-21.1.3:20220121-161822.log' * I am unsure about how could we tell portage to wait until updating and installing newer meson before trying to use it to build other packages :/ But I open it for the case other people hit it Thanks