- 03 Jun, 2022 2 commits
-
-
Anton Midyukov authored
Fix for commit c11a9ca11b550ed916999fe2fa45def59bc94e22 Reported by andy@
-
Anton Midyukov authored
Fix 'warning: fgrep is obsolescent; using grep -F'
-
- 12 May, 2022 1 commit
-
-
Anton Midyukov authored
Fix 'warning: egrep is obsolescent; using grep -E'
-
- 11 Apr, 2022 3 commits
-
-
Anton Midyukov authored
This will save time on identify the causes.
-
Anton Midyukov authored
-
Anton Midyukov authored
-
- 05 Apr, 2022 1 commit
-
-
Michael Shigorin authored
There's a race condition (TOCTOU) between losetup --find and applying the obtained path after additional dd in between; twice awful as *at least* running both losetups closely would reduce the window significantly, and reading the manpage properly back then would eliminate this. Reported-by: Anton Midyukov <antohami@altlinux.org> Suggested-by: Gleb F-Malinovskiy <glebfm@altlinux.org>
-
- 04 Dec, 2021 3 commits
-
-
Michael Shigorin authored
...just to have it handy when it's in need next time.
-
Michael Shigorin authored
"-a arch" is not requisite either; and having bunches of empty lines in the resulting pkglists that are user visible at least within the conventional installer's alterator-pkg (groups selection) module wouldn't be nice. I chose to sacrifice empty-line separators for clarity; the really good cleanup would save *single* empty lines between chunks of non-empty ones (not at the pkglist's start or end); feel free to implement that as well.
-
Michael Shigorin authored
This has been clearly lacking while making the previous commit but the implementation isn't that clear so let it be a separate step. The problem requiring the change in subsequent processors is that these relied upon "@arch" as a flag to be inspected, and "pkg@!arch1,arch2" on arch2 needs to take out *all* of that fragment *including* arch1 mention as well. Part of the cause is difference in handling: "positive" multi-match would explode its "client" line into multiple lines to filter down the pipeline, while "negative" multi-match *has* to keep that line on a similarly single line (otherwise we'd end up with N-1 of those slipping past the filter for particular architecture thus defeating the whole purpose of "negative" matching semantics): $ echo 'pkg@!E2K,mipsel,riscv64' | sed -r ':loop; s/^((([^@]+@!)[^,]+)+),([a-zA-Z0-9_]+)/\1@!\4/; t loop' pkg@!E2K@!mipsel@!riscv64 I've tried my best to test this specific change but it still might introduce a regression in some corner case; feel free to report; looks like there's a space for improvement in m-p's automated tests department as well. So now we can do: pkg@!ARCHES1,ARCHES2,arch3,arch4 and have pkg excluded on arches mentioned; the previous approach could only offer explicit whitelists (not that it was entirely wrong but then again, we have both ExclusiveArch and ExcludeArch rpmtags in our spec files).
-
- 23 Nov, 2021 1 commit
-
-
Michael Shigorin authored
This has been inspired by a few commits that cared for package availability reasons on a particular architecture; the problem at hand is that pkglists might need to include groups of packages that are (un)available on groups of arches, and tackling that with plain pkg@arch just results in combinatorial explosion of that matrix. Arches are handled one-by-one with a few hardcoded macro substitutions. Exploding a "pkg@arch1,arch2" string into a set of: pkg@arch1 pkg@arch2 with subsequent archdep pruning would do the trick; so here's another sed oneliner that does just that: $ echo 'pkg@X86,ARM,ppc64le' | sed -r ':loop; s/^((([^@]+@)[^,]+)+),([^,]+)/\1\n\3\4/; t loop' pkg@X86 pkg@ARM pkg@ppc64le See-also: 9601a9e7 See-also: 5581dc91 See-also: http://stackoverflow.com/a/55781741/561921
-
- 22 Nov, 2021 1 commit
-
-
Anton Midyukov authored
This space is reserved for installation U-Boot.
-
- 04 Sep, 2021 1 commit
-
-
Dmitriy Terekhin authored
Parameter "legacyboot" causes an error: parted: invalid token: legacyboot
-
- 23 Aug, 2021 6 commits
-
-
Anton Midyukov authored
-
Anton Midyukov authored
There is little use, but a lot of noise.
-
Anton Midyukov authored
-
Anton Midyukov authored
-
Anton Midyukov authored
Unavailable metapackages will be removed from the list. A warning will be displayed in the log.
-
Anton Midyukov authored
-
- 23 Jul, 2021 3 commits
-
-
Anton Midyukov authored
Booting from extlinux.conf is preferred over booting in EFI mode.
-
Anton Midyukov authored
This space can be used by single board for u-boot.
-
Anton Midyukov authored
The @META suffix is used to expand the metapackage into a list. apt asks for the dependencies of such a package and adds them to the package list after this metapackage.
-
- 28 Apr, 2021 1 commit
-
-
Michael Shigorin authored
The missing glob resulted in disk images properly partitioned only for e2kv3 ("e2k" for historical reasons in ALT), and v4+ ones only got a single ext4 partition that wouldn't work with current MCST's Boot code.
-
- 01 Feb, 2021 1 commit
-
-
Anton Midyukov authored
-
- 25 Jan, 2021 1 commit
-
-
Anton Midyukov authored
os-probe finds loopback devices.
-
- 26 Nov, 2020 1 commit
-
-
Anton Midyukov authored
While this argument can only have one "EFI" value. Thus, the problem of building an image for Raspberry Pi on armh, where there is no grub-efi, was solved.
-
- 09 Sep, 2020 1 commit
-
-
Anton Midyukov authored
extlinux.conf is not tied to the u-boot bootloader and always needed replace Label with the UUID if the file exist.
-
- 15 Jul, 2020 2 commits
-
-
Anton Midyukov authored
-
Anton Midyukov authored
Since the main goal for aarch64 and armh for us is Raspberry Pi, it is always worth creating a fat32 partition for these arches. At least for now.
-
- 22 May, 2020 1 commit
-
-
Anton Midyukov authored
For Raspberry Pi needed to build grub-efi + MBR images.
-
- 07 Apr, 2020 3 commits
-
-
Anton Midyukov authored
-
Anton Midyukov authored
tar2fs does not run in hasher and without qemu. This causes build problems for an architecture other than the host.
-
Anton Midyukov authored
If build is performed on a system with EFI Secure Boot enabled, then grub will not boot even on EFI without Secure Boot. This problem is caused by the use of the --removable option, which is not compatible with option --uefi-secure-boot the current grub. Option --uefi-secure-boot is enabled automatically if the system is booted in EFI Secure Boot mode.
-
- 03 Apr, 2020 1 commit
-
-
Anton Midyukov authored
-
- 01 Nov, 2019 1 commit
-
-
Anton Midyukov authored
There are use cases when having this common knob would be desirable.
-
- 31 Oct, 2019 1 commit
-
-
Michael Shigorin authored
I've long wanted to have this nice helper around in m-p too but might have set the bar too high. The "prorper integration" idea was to have the script check just those pkglists which are relevant for a given image IIRC. Let's toss it in to begin.
-
- 23 Oct, 2019 1 commit
-
-
Michael Shigorin authored
This code started breeding within pkg.in/*/Makefile, and it was lacking both E2K (as a generic alias, not just "e2k or e2kv4") _and_ the ability to negate selection, as in "everywhere but not on any e2k"). Let's fix all of that at once, and parallelize sed execution as well; my tests with 1000-line file containing "a b c d@!E2K e@e2k f g@!X86 h i@IA32" lines show roughly 3x higher CPU load and lower execution time (~0.3 sec vs ~0.9 sec on 801-PC). And turn that code snippet into a proper filter with inline edit capability (I've dropped the exit trap as failing to mv signals a disaster anyway).
-
- 23 Sep, 2019 1 commit
-
-
Anton Midyukov authored
This commit fixes duplication of root device entry in /etc/fstab and changes LABEL=ROOT entry with the proper one if found. Apparently this didn't hurt qemu images much though...
-
- 19 Aug, 2019 2 commits
-
-
Gleb Fotengauer-Malinovskiy authored
-
Anton Midyukov authored
This allows one not to hope that only the packages of the desired loader will be installed.
-