@puneetse@ahkok
I’m using autospec and it’s creating a spec file that says I shouldn’t edit it, but I need to add flags to the configure command in that file.
In the autospec directory, create a file named configure with the flags to be added and run make autospec again. If the package built fine, you should see those flags in the newly generated spec file.
That’s correct. One reason for that is a security model of all content, down to the file level, being signed and verified from creation to delivery. If bundles from two sources were to be installed that end-to-end verification mechanism would have to take a compromise.
Error: Failed to run command in container: failed to execute docker run --runtime=runc -i --network=host --rm --workdir /home/clr/mixer --entrypoint mixer -v /home/clr/mixer:/home/clr/mixer clearlinux/mixer:29 build update --native: exit status 137
You can add --native to bypass the docker situation. Mixer used docker at one point in time to overcome a limitation with format bumps.
Alternatively, update your Clear Linux install. The newest version of mixer-tools just so happens to deprecate that docker functionality altogether: Releases · clearlinux/mixer-tools · GitHub
Updated my clearlinux to the latest version and now I’m getting a different error. I’ve tried creating a brand new mixer dir and doing mixer init without changing any config.
Always ends with: 2019/11/14 02:26:48 ERROR: Couldn't build bundles: Error building bundles: rpm2archive cmd failed with exit status 1
Full log below:
clr@clr-a55532d214e54fdc904c66be7514d95b~/mixer $ mixer init
Initializing mix version 10 from upstream version 31630
Fetching upstream bundles from https://github.com/clearlinux/clr-bundles/archive/31630.tar.gz
Adding bundle "os-core" from upstream bundles
Adding bundle "os-core-update" from upstream bundles
Adding bundle "bootloader" from upstream bundles
Adding bundle "kernel-native" from upstream bundles
clr@clr-a55532d214e54fdc904c66be7514d95b~/mixer $ mixer build all
Directory walk started
Directory walk done - 0 packages
Temporary output repo path: ./.repodata/
Preparing sqlite DBs
Pool started (with 5 workers)
Pool finished
Generating certificate for signature validation...
Building bundles...
=> BUILD BUNDLES
Adding bundle "hardware-uefi" from upstream bundles
Bundle "bootloader" already in mix; skipping
Adding bundle "linux-firmware" from upstream bundles
Adding bundle "linux-firmware-extras" from upstream bundles
Adding bundle "qemu-guest-additions" from upstream bundles
Bundle "os-core" already in mix; skipping
Adding bundle "os-core-plus" from upstream bundles
Adding bundle "os-core-webproxy" from upstream bundles
Bundle "os-core" already in mix; skipping
Adding bundle "libglib" from upstream bundles
Adding bundle "p11-kit" from upstream bundles
Adding bundle "syslinux" from upstream bundles
Bundle "os-core" already in mix; skipping
Bundle "libglib" already in mix; skipping
Bundle "bootloader" already in mix; skipping
Bundle "linux-firmware" already in mix; skipping
Bundle "linux-firmware-extras" already in mix; skipping
Adding bundle "libstdcpp" from upstream bundles
Bundle "libglib" already in mix; skipping
Adding bundle "findutils" from upstream bundles
Creating bundles for version 10 based on Clear Linux 31630
Preparing new /home/clr/mixer/update/image/10
and dnf config: /home/clr/mixer/.yum-mix.conf
Packager command-line: dnf --config=/home/clr/mixer/.yum-mix.conf -y --releasever=31630
Resolving packages using 6 workers
processing hardware-uefi
processing libstdcpp
processing os-core-plus
processing linux-firmware-extras
processing qemu-guest-additions
processing libglib
... done with linux-firmware-extras
processing p11-kit
... done with os-core-plus
processing os-core
... done with libstdcpp
processing syslinux
... done with hardware-uefi
processing kernel-native
... done with qemu-guest-additions
processing linux-firmware
... done with libglib
processing os-core-update
... done with p11-kit
processing os-core-webproxy
... done with syslinux
processing findutils
... done with os-core
processing bootloader
... done with kernel-native
... done with linux-firmware
... done with os-core-update
... done with os-core-webproxy
... done with findutils
... done with bootloader
Resolving files using 6 workers
processing bootloader
Bundle bootloader 5 files
processing qemu-guest-additions
Bundle qemu-guest-additions 5 files
processing os-core-plus
processing libstdcpp
Bundle libstdcpp 5 files
processing os-core
Bundle os-core 5 files
processing libglib
Bundle libglib 5 files
processing linux-firmware-extras
processing hardware-uefi
Bundle os-core-plus 5 files
processing linux-firmware
Bundle linux-firmware 5 files
processing os-core-update
processing p11-kit
Bundle hardware-uefi 5 files
processing os-core-webproxy
Bundle os-core-webproxy 5 files
processing kernel-native
Bundle p11-kit 5 files
Bundle kernel-native 5 files
Bundle linux-firmware-extras 5 files
processing syslinux
Bundle syslinux 5 files
processing findutils
Bundle findutils 5 files
Bundle os-core-update 5 files
Cleaning DNF cache before full install
Installing all bundles to full chroot
TIMINGS
BUILD BUNDLES 0s
TOTAL: 0s
2019/11/14 02:26:48 ERROR: Couldn't build bundles: Error building bundles: rpm2archive cmd failed with exit status 1
No! there is no “if it’s not here, then get it from there”. You’re not “overlaying” the OS with another OS. You are creating a new OS that has whatever you choose from it, plus your local things. If you choose to omit something, your downstream installations can’t get it.