alpine issueshttps://gitlab.alpinelinux.org/groups/alpine/-/issues2022-10-31T20:54:38Zhttps://gitlab.alpinelinux.org/alpine/cloud/alpine-cloud-images/-/issues/132Make a single "Hybrid MBR" Image Instead of Separate BIOS/UEFI2022-10-31T20:54:38ZJake Buchholz GöktürkMake a single "Hybrid MBR" Image Instead of Separate BIOS/UEFI`gptfdisk` would be the tool to do this.
In-depth analysis of the pros/cons -- https://www.rodsbooks.com/gdisk/hybrid.html
The issue that either MBR or GPT misses out on any partition changes is mostly moot in a cloud environment. It ...`gptfdisk` would be the tool to do this.
In-depth analysis of the pros/cons -- https://www.rodsbooks.com/gdisk/hybrid.html
The issue that either MBR or GPT misses out on any partition changes is mostly moot in a cloud environment. It would be extremely rare if an instance is booted with one, and then switched to another later in its lifetime.
While this is an opportunity to also address the ongoing #90 saga, if that turns out to be a bottomless rabbit hole, using `grub2` for UEFI would be good enough in the interim.https://gitlab.alpinelinux.org/alpine/cloud/alpine-cloud-images/-/issues/130Support Bare Metal Cloud Images2024-03-24T18:25:51ZJake Buchholz GöktürkSupport Bare Metal Cloud ImagesThis will probably involve using `linux-lts` instead of `linux-virt`.This will probably involve using `linux-lts` instead of `linux-virt`.https://gitlab.alpinelinux.org/alpine/aports/-/issues/13519runc 1.1.0: cgroups not configured / cannot stat /usr/local/bin/kube-rbac-proxy2022-02-21T19:56:58ZNico Schotteliusrunc 1.1.0: cgroups not configured / cannot stat /usr/local/bin/kube-rbac-proxyWhen trying to deploy kube-prometheus, the following error is shown:
```
Events:
Type Reason Age From Message
---- ------ ---- ---- -------
Normal Scheduled 16s default-scheduler...When trying to deploy kube-prometheus, the following error is shown:
```
Events:
Type Reason Age From Message
---- ------ ---- ---- -------
Normal Scheduled 16s default-scheduler Successfully assigned monitoring/node-exporter-xmp2r to server59
Normal Pulled 15s kubelet Container image "quay.io/prometheus/node-exporter:v1.3.1" already present on machine
Normal Created 14s kubelet Created container node-exporter
Normal Started 14s kubelet Started container node-exporter
Warning Failed 13s kubelet Error: container create failed: time="2022-02-13T17:19:24+01:00" level=warning msg="cannot toggle freezer: cgroups not configured for container"
time="2022-02-13T17:19:24+01:00" level=warning msg="cannot toggle freezer: cgroups not configured for container"
time="2022-02-13T17:19:24+01:00" level=warning msg="lstat : no such file or directory"
time="2022-02-13T17:19:24+01:00" level=error msg="runc create failed: unable to start container process: exec: \"/usr/local/bin/kube-rbac-proxy\": stat /usr/local/bin/kube-rbac-proxy: no such file or directory"
Normal Pulled 12s (x2 over 14s) kubelet Container image "quay.io/brancz/kube-rbac-proxy:v0.11.0" already present on machine
Warning Failed 11s kubelet Error: container create failed: time="2022-02-13T17:19:26+01:00" level=warning msg="cannot toggle freezer: cgroups not configured for container"
time="2022-02-13T17:19:26+01:00" level=warning msg="cannot toggle freezer: cgroups not configured for container"
time="2022-02-13T17:19:26+01:00" level=warning msg="lstat : no such file or directory"
time="2022-02-13T17:19:26+01:00" level=error msg="runc create failed: unable to start container process: exec: \"/usr/local/bin/kube-rbac-proxy\": stat /usr/local/bin/kube-rbac-proxy: no such file or directory"
```
I am receiving this error since running @apk upgrade -a@ today, running against edge:
```
[17:23] server59.place7:~# apk list -I | grep -e runc -e cri -e kube
udev-init-scripts-35-r0 x86_64 {udev-init-scripts} (GPL-2.0-only) [installed]
cri-o-1.23.0-r0 x86_64 {cri-o} (Apache-2.0) [installed]
runc-1.1.0-r0 x86_64 {runc} (Apache-2.0) [installed]
cri-o-openrc-1.23.0-r0 x86_64 {cri-o} (Apache-2.0) [installed]
kubeadm-1.23.3-r0 x86_64 {kubernetes} (Apache-2.0) [installed]
kubectl-1.23.3-r0 x86_64 {kubernetes} (Apache-2.0) [installed]
udev-init-scripts-openrc-35-r0 x86_64 {udev-init-scripts} (GPL-2.0-only) [installed]
kubelet-1.23.3-r0 x86_64 {kubernetes} (Apache-2.0) [installed]
cri-tools-1.23.0-r0 x86_64 {cri-tools} (Apache-2.0) [installed]
kubelet-openrc-1.23.3-r0 x86_64 {kubernetes} (Apache-2.0) [installed]
[17:24] server59.place7:~#
```https://gitlab.alpinelinux.org/alpine/tsc/-/issues/38Add Hello71(@alxu) as developer2022-06-07T06:38:36ZKevin DaudtAdd Hello71(@alxu) as developerSuggested by @ariadne: alpine/infra/gitlab-tf!10Suggested by @ariadne: alpine/infra/gitlab-tf!10https://gitlab.alpinelinux.org/alpine/aports/-/issues/13513lua-resty-http package shouldn't have a dependency on lua5.12022-05-24T06:59:45ZAlex Dowadlua-resty-http package shouldn't have a dependency on lua5.1It looks like the `lua-resty-http` package has a dependency on `lua5.1`. However, this package contains only pure-Lua scripts (no C extension). Further, these scripts are designed to be used with OpenResty's Nginx Lua module, which is ba...It looks like the `lua-resty-http` package has a dependency on `lua5.1`. However, this package contains only pure-Lua scripts (no C extension). Further, these scripts are designed to be used with OpenResty's Nginx Lua module, which is based on LuaJIT, so in practice they always execute on LuaJIT.
Am I misunderstanding something? If not, then can the dependency on `lua5.1` be removed? If anything, a dependency on `lua-resty-core` might be more appropriate.
FYA @jirutkaJakub JirutkaJakub Jirutkahttps://gitlab.alpinelinux.org/alpine/aports/-/issues/13512Update dependencies for aports that depend on the now empty util-linux package2022-08-05T10:15:45Zomniomni+alpine@hack.orgUpdate dependencies for aports that depend on the now empty util-linux packageSince v3.15 the `util-linux` package is empty and depend on nothing, a few aports depend on it and should be updated to depend on the `util-linux` sub-package(s) that contain their respective requirements.
~~v3.15:~~ Not needed for stab...Since v3.15 the `util-linux` package is empty and depend on nothing, a few aports depend on it and should be updated to depend on the `util-linux` sub-package(s) that contain their respective requirements.
~~v3.15:~~ Not needed for stable? https://gitlab.alpinelinux.org/alpine/aports/-/merge_requests/32071#note_222684
- [ ] apcupsd
- [ ] apcupsd-webif
- [ ] arch-install-scripts
- [ ] ceph-base
- [ ] cloud-utils
- [ ] fish-doc
- [ ] lxc-lvm
- [ ] openvas
- [ ] openvas-config
- [ ] safekeep
- [ ] tlp
- [ ] util-linux-dev
- [x] zram-init 7e3aeb9ea5b9641ad9d22bca728566c34e30241a
edge:
- [ ] apcupsd
- [ ] apcupsd-webif
- [ ] apt-dater
- [ ] apt-dater-lang
- [x] arch-install-scripts 0be3f28cfec91c5d8166a4e997ee36afc4c568a1
- [ ] ceph-base
- [x] cloud-utils 7c4c0e735c0e91449c384ae58310f00ae1308204
- [x] fish-doc 4a06c9986875ddf89b1ce8e5254853b971c8f81b
- [ ] kimchi
- [ ] kimchi-lang
- [ ] lxc-lvm
- [ ] openvas
- [ ] openvas-config
- [x] safekeep 1ee69994096e90629eacceabf38ec6198833de09
- [ ] scap-workbench
- [ ] tlp
- [x] zram-init 5ba4062144ca290aa0763d5acec5708101ecadb1https://gitlab.alpinelinux.org/alpine/apk-tools/-/issues/10813enhanced structured data for copyright tracking2022-12-21T19:37:22ZAriadne Conillariadne@ariadne.spaceenhanced structured data for copyright trackingAt work, we are writing a build-tool which generates APKv3 files as output. However, we would like to capture more of the copyright/license metadata than just the `license` field of `APKBUILD`.
I propose the following:
```
copyright:
...At work, we are writing a build-tool which generates APKv3 files as output. However, we would like to capture more of the copyright/license metadata than just the `license` field of `APKBUILD`.
I propose the following:
```
copyright:
- path: "[glob mask relevant to $srcdir]"
license: "[SPDX identifier, like old `license` field]"
attestations:
- "Copyright (c) 20XX foobar"
- "Copyright (c) 20XX baz"
```
An `APKBUILD` with `license="ISC"` would then map to:
```
copyright:
- path: "*"
license: "ISC"
```
If this seems agreeable, I can work on a patch next week for this. It is related to the SBOM work, see #10780.v3.1https://gitlab.alpinelinux.org/alpine/aports/-/issues/13508Fix check for some Python packages2023-07-24T08:06:56ZPatrycja Rosaalpine@ptrcnull.meFix check for some Python packagesnewapkbuild seems to add `python3 setup.py check` to new Python packages' check function - that's not actually running any tests, just checking if metadata of the package is correct (see [here](https://docs.python.org/3.10/distutils/apir...newapkbuild seems to add `python3 setup.py check` to new Python packages' check function - that's not actually running any tests, just checking if metadata of the package is correct (see [here](https://docs.python.org/3.10/distutils/apiref.html#module-distutils.command.check)), which is useful to upstream devs but not so much for distro packaging
**list of affected packages:**
main:
- [x] meson (!29489)
- [x] py3-bcrypt (!30697)
- [x] py3-cairo (!30698)
- [x] py3-certifi (1085da3c)
- [x] py3-extras (!30717)
- [x] py3-fixtures (!30721)
- [x] py3-future (!30755)
- [x] py3-lxml (!30710)
- [x] py3-monotonic (!31603)
- [x] py3-pbr (!30757)
- [x] py3-pexpect (!30756)
- [x] py3-pynacl (!30713)
- [x] py3-pytest (!30773)
- [x] py3-sphinxcontrib-websupport (3b612e0d)
- [x] py3-testtools (!30769)
- [x] py3-urllib3 (!30709)
- [x] py3-wcwidth (!30711)
- [x] scons (!30766)
- [x] speedtest-cli (!30696)
community:
- [ ] aws-cli
- [x] certbot (!30688)
- [x] cloud-init (!30874)
- [x] docker-py (!30875)
- [x] electrum (!30741)
- [ ] git-review
- [x] gvm-tools (63e49c536a7)
- [ ] mate-tweak
- [x] ospd (51a71b185540)
- [x] ospd-openvas (24ed5058fc5)
- [ ] py3-aiohttp (!36944)
- [x] py3-aiohttp-socks (!36946)
- [x] py3-aiorpcx (!36947)
- [ ] py3-aiosignal
- [x] py3-alembic
- [ ] py3-anytree (!37088)
- [ ] py3-apache-libcloud
- [x] ~~py3-argparse~~
- [ ] py3-async_generator
- [ ] py3-blist
- [ ] py3-botocore
- [ ] py3-cached-property
- [ ] py3-cheetah
- [ ] py3-construct
- [ ] py3-cx_freeze
- [ ] py3-decorator (!36970)
- [ ] py3-dialog
- [ ] py3-distutils-extra
- [ ] py3-django-oscar
- [ ] py3-django-registration
- [x] py3-dotenv (!36964)
- [ ] py3-fasteners
- [x] py3-frozenlist (!36968)
- [ ] py3-gettext (!36948)
- [x] py3-gvm (88db827bc272)
- [ ] py3-icu
- [ ] py3-josepy
- [ ] py3-jsonrpclib
- [x] py3-mechanize (!37089)
- [ ] py3-netifaces
- [ ] py3-pdfrw
- [ ] py3-prompt_toolkit
- [ ] py3-psutil
- [ ] py3-pyaes
- [ ] py3-pysocks
- [ ] py3-rpigpio
- [ ] py3-scp
- [x] py3-secretstorage (!36793)
- [x] py3-solo1 (8081e96c)
- [ ] py3-sqlalchemy-migrate
- [ ] py3-unicodecsv (!36967)
- [ ] py3-zabbix (!37098)
- [ ] scapy
- [x] terminator (!30695)
- [x] virt-manager (!30690)
- [ ] you-get
- [ ] yubikey-manager
testing:
- [ ] awslogs
- [ ] bump2version
- [ ] gaupol
- [ ] guake
- [ ] junit2html
- [ ] nyx
- [ ] openscap-daemon
- [ ] ospd-acunetix
- [ ] ospd-debsecan
- [ ] ospd-ikescan
- [ ] ospd-nmap
- [ ] ospd-paloalto
- [ ] py3-apsw
- [ ] py3-blockchain
- [ ] py3-bump2version
- [ ] py3-cchardet
- [ ] py3-fpdf
- [ ] py3-kerberos
- [ ] py3-libacl
- [ ] py3-netmiko
- [ ] py3-pam
- [ ] py3-pefile
- [ ] py3-pg_activity
- [ ] py3-pgspecial
- [ ] py3-pyautogui
- [ ] py3-pygdbmi
- [ ] py3-pyte
- [ ] py3-sphinx-theme-better
- [ ] py3-stem
- [ ] py3-terminaltables
- [ ] py3-tls_parser
- [ ] py3-ufonormalizer
- [ ] py3-xmldiff
- [ ] py3-yara
- [ ] s3cmd
- [ ] solaar
- [ ] tartube
- [ ] thefuck
- [ ] vidcutter
- [ ] volatility3https://gitlab.alpinelinux.org/alpine/aports/-/issues/13506Management agent version is not detected in Xen Orchestra2022-02-07T14:18:21ZForzaManagement agent version is not detected in Xen OrchestraHi,
I am not able to see the Management version in XCP-ng Center or in XOA using xe-guest-utilities-7.30.0-r2 on Alpine 3.14 and Alpine 3.15.
This is how it looks like from XOA:
![image](/uploads/0b7f714b6500aa390ecabcae9d23b69d/image...Hi,
I am not able to see the Management version in XCP-ng Center or in XOA using xe-guest-utilities-7.30.0-r2 on Alpine 3.14 and Alpine 3.15.
This is how it looks like from XOA:
![image](/uploads/0b7f714b6500aa390ecabcae9d23b69d/image.png)
This is how it looks like from XCP-ng Center - it fails to detect management agent:
![image](/uploads/ea0001c3833f3823e58c8f798fea79a9/image.png)
According to the developers of Xen Orchestra, there seems to be some missing strings compiled in the xe-guest-utilities: https://xcp-ng.org/forum/topic/5059/alpine-3-14-not-detected-correctly/3?_=1644241915917https://gitlab.alpinelinux.org/alpine/mkinitfs/-/issues/22mkinitfs: support multiple comma separated repositories for alpine_repo2022-02-06T21:22:11ZTobias Urdinmkinitfs: support multiple comma separated repositories for alpine_repoIn `initramfs-init.in` [1] add support to insert multiple repositories by parsing commas as separators for new lines when stdout is redirected to /etc/apk/repositories.
That way you can add both `main` and `community` repo and use `pkgs...In `initramfs-init.in` [1] add support to insert multiple repositories by parsing commas as separators for new lines when stdout is redirected to /etc/apk/repositories.
That way you can add both `main` and `community` repo and use `pkgs=` to install a package from `community` that has dependencies in `main`.
Misplaced a PR on GitHub [2].
```
diff --git a/initramfs-init.in b/initramfs-init.in
index 4f96b7c..7fd602d 100755
--- a/initramfs-init.in
+++ b/initramfs-init.in
@@ -239,7 +239,7 @@ relocate_mount() {
# find the dirs under ALPINE_MNT that are boot repositories
find_boot_repositories() {
if [ -n "$ALPINE_REPO" ]; then
- echo "$ALPINE_REPO"
+ echo "$ALPINE_REPO" | tr ',' '\n'
else
find /media/* -name .boot_repository -type f -maxdepth 3 \
| sed 's:/.boot_repository$::'
```
[1] https://git.alpinelinux.org/mkinitfs/tree/initramfs-init.in
[2] https://github.com/alpinelinux/mkinitfs/pull/56https://gitlab.alpinelinux.org/alpine/aports/-/issues/13502Port Flutter and Android Studio to musl or alpine2023-05-21T15:28:58ZMuhammad Afzal TahirPort Flutter and Android Studio to musl or alpineI am fan of alpine Linux. But unfortunately, Flutter do not support alpine.
You made alpine Linux but with out software support it will not progress much.
Please port Flutter and Android studio to Alpine (musl library).
Or just tell me h...I am fan of alpine Linux. But unfortunately, Flutter do not support alpine.
You made alpine Linux but with out software support it will not progress much.
Please port Flutter and Android studio to Alpine (musl library).
Or just tell me how can I port them to alpine.
I do not know much about Linux. I know about DE and basic terminal commands of Linux. I also know what is busybox and musl and glibc but unfortunately only their definition. They are c libararies.
I want to work for alpine. Tell me where to learn Linux and port packages to alpine.https://gitlab.alpinelinux.org/alpine/abuild/-/issues/10060Subpackage versioning2022-08-14T17:58:30ZAntoine MartinSubpackage versioningThe following discussion from aports!28195 should be addressed:
- [ ] @jirutka started a [discussion](https://gitlab.alpinelinux.org/alpine/aports/-/merge_requests/28195#note_205465): (+14 comments)
> `pkgver` should not be redefi...The following discussion from aports!28195 should be addressed:
- [ ] @jirutka started a [discussion](https://gitlab.alpinelinux.org/alpine/aports/-/merge_requests/28195#note_205465): (+14 comments)
> `pkgver` should not be redefined for subpackages. I tried that a few years ago in some aports and it didn’t work well with the build servers (I don’t remember details). However, maybe this is a good time to open a discussion about this, because this is a quite unfortunate limitation and I’d like to overcome it.
>
> /cc @ncopa, @ariadne, @kdaudt
dotnet packages require custom pkgver within subpackages, as SDK and Runtime have different versioning schemes. This is not currently supported by buildrepo or abuild as they source only global pkgver to check if there should be a rebuild of packages, or whether old packages should be purged. I implemented a mitigation from within my aports that create a symbolic link between where the APK is expected to be by abuild and buildrepo, and where it actually is. This works for most use-cases that I could test for, except for buildrepo's purging functionality. As buildrepo purges every APK that doesn't match `(name or pkg.pkgname).."-"..pkg.pkgver.."-r"..pkg.pkgrel..".apk"`, this means it deletes any subpackage with custom pkgver.
The mitigation is as follows:
```bash
scan_symlink_targets() {
local name="$1" dir="$2"
local ver=$(pkginfo_val pkgver "$dir"/.PKGINFO)
local subpkgarch=$(pkginfo_val arch "$dir"/.PKGINFO)
[ -d "$REPODEST"/${repo:?}/${subpkgarch/noarch/$CARCH} ] || mkdir -p "$REPODEST"/$repo/${subpkgarch/noarch/$CARCH}
[ "$ver" = "$pkgver-r$pkgrel" ] || ln -sf "$REPODEST"/$repo/${subpkgarch/noarch/$CARCH}/$name-$ver.apk "$REPODEST"/$repo/${subpkgarch/noarch/$CARCH}/$name-$pkgver-r$pkgrel.apk
}
```
# Problematic functions
Through my attempts at figuring out a mitigation, I identified the following problematic functions
## abuild
* `scan_symlink_targets`: when it detects symlink dependencies between subpkgs sets a hard dependency to that specific version of subpackage. Above mitigation neutralizes scan_symlink_targets, leaving the maintainer to set those dependencies explicitely
* `apk_up2date` / `abuildindex_up2date`:root cause of subpkg issues in abuild. Both functions define expected path as `"$dir"/$subpkgname-$pkgver-r$pkgrel.apk`. Since these are defined from within a for loop for each package, `$pkgver` should rather be `$subpkgver`, but no logics are in place to do so.
* `subpkg_set`: defines above `$pkgver` variable. Logics for `$subpkgver` would be implemented here.
## lua-aports
* `db:each_need_build` / purge logics (`buildrepo`): former relies on `pkg.apk_file_exists` which checks if there's a readable file at output of `get_apk_file_path`, which relies on `get_apk_file_name`. Latter also relies on `get_apk_file_name`
* `get_apk_file_name` (`buildrepo/pkg.lua`): root function of the above functions, defines `apk_file_name` as `(name or pkg.pkgname).."-"..pkg.pkgver.."-r"..pkg.pkgrel..".apk"`. `pkg.pkgver` is presumable sourced from aport's global pkgver rather than APKINDEX. If `get_apk_file_name` sourced pkg.pkgver from subpkgver, this would likely fix the issues with buildrepo. This function is thus a root-case for issues relating to subpkg versioning.
# Implementation proposal
## aports
Similar to :arch implementation within subpackages array, this would probably be a similar strategy to define pkgver for subpackages. Thus possible variables within subpackages would be `subpkgname:subpkgsplit:subpkgver:subpkgarch` rather than `subpkgname:subpkgsplit:subpkgarch`
It would then be a matter of changing the above abuild functions, implementing most of the logics in `subpkg_set`.
## Buildrepo
I know little of lua, so while I might make an attempt at an implementation, I can't even tell how `pkg.pkgver` is sourced. The only thing I can tell is that `get_apk_file_name` *seems* to be where I need to implement the logics, but then again `db:each_name` seems to also be a candidate. This is likely something that someone more lua-savy should address.https://gitlab.alpinelinux.org/alpine/aports/-/issues/13501udisksctl unable to mount /dev/mapper volumes2023-08-23T11:15:42ZDaniel Grayudisksctl unable to mount /dev/mapper volumesAn encrypted volume, whether it be a partition, or loop device cannot be mounted with `udisksctl mount -b /dev/mapper/luks-*`. I suspect this is due to missing policy kit rules. If the device is not encrypted you can mount that ie `udis...An encrypted volume, whether it be a partition, or loop device cannot be mounted with `udisksctl mount -b /dev/mapper/luks-*`. I suspect this is due to missing policy kit rules. If the device is not encrypted you can mount that ie `udisksctl mount -b /dev/disk`. Using less secure means `cryptsetup luksOpen` and `mount` methods work.
I have `/usr/lib/polkit-1/polkitd --no-debug` running and `/usr/bin/lxqt-policykit-agent` and have launched my sway session with `dbus-run-session sway`. I am using `elogind` and `eudev`.
Unlocking works, ie `udisksctl unlock -b /dev/device` encrypted container, ie:
```
# dd if=/dev/random of=test count=100000 bs=1000
# cryptsetup luksFormat test,
# cryptsetup luksOpen test test
# mkfs.ext4 /dev/mapper/test
# cryptsetup luksClose /dev/mapper/test
$ udisksctl loop-setup test
$ udisksctl unlock /dev/loop0
```
What doesn't work is:
1. `udisksctl mount -b /dev/mapper/luks-*`
When you click on an encrypted disk in Nautilus or Thunar this is the part that doesn't work either. It will ask you for the password, and as soon as provided the device will disappear from the side panel. Having a look at `udiskctl monitor` I noticed this after unlocking:
```
23:45:00.698: /org/freedesktop/UDisks2/block_devices/sdb1: org.freedesktop.UDisks2.Encrypted: Properties Changed
HintEncryptionType: LUKS
23:45:00.699: Added /org/freedesktop/UDisks2/jobs/8
org.freedesktop.UDisks2.Job:
Bytes: 0
Cancelable: true
ExpectedEndTime: 0
Objects: /org/freedesktop/UDisks2/block_devices/sdb1
Operation: encrypted-unlock
Progress: 0.0
ProgressValid: false
Rate: 0
StartTime: 1643894100696853
StartedByUID: 1000
23:45:02.776: /org/freedesktop/UDisks2/jobs/8: org.freedesktop.UDisks2.Job::Completed (true, '')
23:45:02.776: Removed /org/freedesktop/UDisks2/jobs/8
23:45:02.778: Added /org/freedesktop/UDisks2/block_devices/dm_2d0
org.freedesktop.UDisks2.Block:
Configuration: []
CryptoBackingDevice: '/org/freedesktop/UDisks2/block_devices/sdb1'
Device: /dev/dm-0
DeviceNumber: 64768
Drive: '/'
HintAuto: false
HintIconName:
HintIgnore: false
HintName:
HintPartitionable: false
HintSymbolicIconName:
HintSystem: true
Id:
IdLabel:
IdType:
IdUUID:
IdUsage:
IdVersion:
MDRaid: '/'
MDRaidMember: '/'
PreferredDevice: /dev/dm-0
ReadOnly: false
Size: 7740588032
Symlinks:
UserspaceMountOptions:
23:45:02.778: /org/freedesktop/UDisks2/block_devices/sdb1: org.freedesktop.UDisks2.Encrypted: Properties Changed
CleartextDevice: '/org/freedesktop/UDisks2/block_devices/dm_2d0'
```
Whereas when I try this on Fedora, Debian etc I see:
```
22:50:53.494: Added /org/freedesktop/UDisks2/jobs/12
org.freedesktop.UDisks2.Job:
Bytes: 0
Cancelable: true
ExpectedEndTime: 0
Objects: /org/freedesktop/UDisks2/block_devices/sde1
Operation: encrypted-unlock
Progress: 0.0
ProgressValid: false
Rate: 0
StartTime: 1643890853492936
StartedByUID: 1000
22:50:54.808: /org/freedesktop/UDisks2/jobs/12: org.freedesktop.UDisks2.Job::Completed (true, '')
22:50:54.808: Removed /org/freedesktop/UDisks2/jobs/12
22:50:54.822: Added /org/freedesktop/UDisks2/block_devices/dm_2d1
org.freedesktop.UDisks2.Block:
Configuration: []
CryptoBackingDevice: '/org/freedesktop/UDisks2/block_devices/sde1'
Device: /dev/dm-1
DeviceNumber: 64769
Drive: '/'
HintAuto: false
HintIconName:
HintIgnore: false
HintName:
HintPartitionable: false
HintSymbolicIconName:
HintSystem: true
Id: by-id-dm-name-luks-ce782db4-f9ee-4154-80e1-72c0d71b08da
IdLabel:
IdType: ext4
IdUUID: d8f0c988-446b-46db-a9f9-15db9431085b
IdUsage: filesystem
IdVersion: 1.0
MDRaid: '/'
MDRaidMember: '/'
PreferredDevice: /dev/mapper/luks-ce782db4-f9ee-4154-80e1-72c0d71b08da
ReadOnly: false
Size: 7740588032
Symlinks: /dev/disk/by-id/dm-name-luks-ce782db4-f9ee-4154-80e1-72c0d71b08da
/dev/disk/by-id/dm-uuid-CRYPT-LUKS2-7b7bdab9c4fc43afabe61240e616b5dc-luks-ce782db4-f9ee-4154-80e1-72c0d71b08da
/dev/disk/by-uuid/d8f0c988-446b-46db-a9f9-15db9431085b
/dev/mapper/luks-ce782db4-f9ee-4154-80e1-72c0d71b08da
UserspaceMountOptions:
org.freedesktop.UDisks2.Filesystem:
MountPoints:
Size: 7740588032
22:50:54.823: /org/freedesktop/UDisks2/block_devices/sde1: org.freedesktop.UDisks2.Encrypted: Properties Changed
CleartextDevice: '/org/freedesktop/UDisks2/block_devices/dm_2d1'
```
The component that seems to be blank is:
```
Id: by-id-dm-name-luks-ce782db4-f9ee-4154-80e1-72c0d71b08da
IdLabel:
IdType: ext4
IdUUID: d8f0c988-446b-46db-a9f9-15db9431085b
IdUsage: filesystem
IdVersion: 1.0
```
and instead of pointing to the /dev/mapper device
```
PreferredDevice: /dev/mapper/luks-ce782db4-f9ee-4154-80e1-72c0d71b08da
```
it points to:
```
PreferredDevice: /dev/dm-0
```
The symlinks were also missing:
```
Symlinks: /dev/disk/by-id/usb-TOSHIBA_TransMemory_000000000000000000000000-0:0-part1
/dev/disk/by-partuuid/41c05551-f39c-42db-b64e-1b36a924f573
/dev/disk/by-path/pci-0000:39:00.0-usb-0:1.3:1.0-scsi-0:0:0:0-part1
/dev/disk/by-uuid/ce782db4-f9ee-4154-80e1-72c0d71b08da
```https://gitlab.alpinelinux.org/alpine/apk-tools/-/issues/10808Progress bar flushed by script execution2022-12-21T19:37:22ZPaul SpoorenProgress bar flushed by script executionIn OpenWrt every script executes a default `post-install` script which thereby always flushes the progress bar, it's only flickering around. Would it be possible to write the package installation progress bar after printing the execution...In OpenWrt every script executes a default `post-install` script which thereby always flushes the progress bar, it's only flickering around. Would it be possible to write the package installation progress bar after printing the execution message?
```
(15/139) Installing ucode-mod-uci (0_git20220126-r1)
Executing ucode-mod-uci_0_git20220126-r1.post-install
(16/139) Installing firewall4 (0_git20220128-r1)
Executing firewall4_0_git20220128-r1.post-install
(17/139) Installing ubi-utils (2.1.4-r1)
Executing ubi-utils_2.1.4-r1.post-install
(18/139) Installing fstools (0_git20211116-r2)
Executing fstools_0_git20211116-r2.post-install
(19/139) Installing getrandom (0_git20210803-r2)
Executing getrandom_0_git20210803-r2.post-install
(20/139) Installing hostapd-common (0_git20210522-r67)
Executing hostapd-common_0_git20210522-r67.post-install
...
```v3.1https://gitlab.alpinelinux.org/alpine/aports/-/issues/13483unsupported cpio format2022-03-10T18:46:03ZJoachim Weberunsupported cpio formatHello all,
just a fwe minutes ago I fired an "apk update; apk upgrade --available" on my small vServer followed by a reboot, as it got a new kernel. But I was a little confused about the lines:
```
...
Executing mkinitfs-3.6.0-r0.trigg...Hello all,
just a fwe minutes ago I fired an "apk update; apk upgrade --available" on my small vServer followed by a reboot, as it got a new kernel. But I was a little confused about the lines:
```
...
Executing mkinitfs-3.6.0-r0.trigger
==> initramfs: creating /boot/initramfs-virt
**cpio: unsupported cpio format, use newc or crc**
**cpio: write error: Broken pipe**
Executing syslinux-6.04_pre1-r9.trigger
/boot is device /dev/vda1
OK: 198 MiB in 200 packages
...
```
Nevertheless the "OK" encouraged me to restart the box - but it didn't come up to more than energency mode.
What happened?
Thanks for reading!
-troubleticket- (Joe Weber)https://gitlab.alpinelinux.org/alpine/aports/-/issues/13480main/eudev: intermittent error after unplugging USB drive2022-01-28T23:31:18ZMogens Jensenmain/eudev: intermittent error after unplugging USB driveOn an Alpine edge x86_64 system, I noticed the following error in dmesg output, after unplugging a USB flash drive:
`udevd[2042]: inotify_add_watch(7, /dev/sda, 10) failed: No such file or directory`
The drive does not need to be mount...On an Alpine edge x86_64 system, I noticed the following error in dmesg output, after unplugging a USB flash drive:
`udevd[2042]: inotify_add_watch(7, /dev/sda, 10) failed: No such file or directory`
The drive does not need to be mounted, just inserting and removing it will generate the error, but not always, maybe 6 out of 10 times.
I don't know if this is a serious problem or just a harmless message, but it's not something I have seen before.Ariadne Conillariadne@ariadne.spaceAriadne Conillariadne@ariadne.spacehttps://gitlab.alpinelinux.org/alpine/aports/-/issues/13479lua-busted: add lua 5.4 support2023-09-05T21:47:14ZNatanael Copalua-busted: add lua 5.4 supportWould be nice with busted working with lua 5.4.
- [x] luarocks5.4
- [x] lua5.4-cliargs
- [x] lua5.4-system
- [x] lua5.4-say
- [x] lua5.4-luassert
- [x] lua5.4-mediatorWould be nice with busted working with lua 5.4.
- [x] luarocks5.4
- [x] lua5.4-cliargs
- [x] lua5.4-system
- [x] lua5.4-say
- [x] lua5.4-luassert
- [x] lua5.4-mediatorhttps://gitlab.alpinelinux.org/alpine/infra/aports-qa-bot/-/issues/23Add security tag based on commit message2022-04-23T14:26:15ZJ0WIAdd security tag based on commit messagee.g. commit contains a CVE or "security upgrade"e.g. commit contains a CVE or "security upgrade"https://gitlab.alpinelinux.org/alpine/alpine-conf/-/issues/10500Add support for syslinux EFI in setup-disk2022-04-01T09:44:36ZPhilippe SchommersAdd support for syslinux EFI in setup-diskHi,
I'd really like to be able to use `setup-disk` with `syslinux` for an EFI system.
Currently, one needs to mount the EFI partition on `/boot/efi`, and only `bootx64.efi` will be installed by `grub-efi` on that partition, keeping the ...Hi,
I'd really like to be able to use `setup-disk` with `syslinux` for an EFI system.
Currently, one needs to mount the EFI partition on `/boot/efi`, and only `bootx64.efi` will be installed by `grub-efi` on that partition, keeping the kernel and stuff out of it.
What I'd like to achieve is having the EFI partition mounted on `/boot`, so that `initramfs` and `vmlinuz` end up on the EFI partition (which is required for `syslinux` as far as I know, as the root would be on LVM).
I think this goes well in line with the Alpine philosophy.
Is this something you'd be interested in / that would get merged if I opened a PR? If so, is there something I should be mindful of?
Maybe this could be done with a `syslinux-efi` package? One thing I noticed is that installing `syslinux` automatically "pollutes" `/boot` with `.m32` and `.sys` as well as `extlinux.conf` files, which are not required for an EFI setup. Is there a way around this?https://gitlab.alpinelinux.org/alpine/aports/-/issues/13466testing/fluent-bit: segfaults on 3.15 with multiple file outputs configuration2022-01-26T13:57:33Zs-kibayashitesting/fluent-bit: segfaults on 3.15 with multiple file outputs configurationI tried fluent-bit on 3.15 armhf-build.
In case multiple file outputs configuration, segfaults were occured. (Please refer to the following configuration example and gdb dump)
When I checked 'CMakeCache.txt' after package building with...I tried fluent-bit on 3.15 armhf-build.
In case multiple file outputs configuration, segfaults were occured. (Please refer to the following configuration example and gdb dump)
When I checked 'CMakeCache.txt' after package building with original APKBUILD, '-Os -fomit-frame-pointer' was applied as GCC option. (It may be CMake's default value.)
As a test, I changed GCC option to '-O2 -fomit-frame-pointer' and tried fluent-bit rebuild, the problem of segfaults was sloved. (Please refer to the following APKBUILD modification example)
GCC's binary size optimization may be doing something wrong.
Please check this issue at the next release.
configuration example (/etc/fluent-bit/fluent-bit.conf):
```
[INPUT]
name cpu
tag cpu.local
# Read interval (sec) Default: 1
interval_sec 1
[OUTPUT]
name file
match *
path /tmp
file sample0.log
[OUTPUT]
name file
match *
path /tmp
file sample1.log
[OUTPUT]
name file
match *
path /tmp
file sample2.log
```
gdb dump (3.15 armhf-build fluent-bit original package):
```
(gdb) run -v -c /etc/fluent-bit/fluent-bit.conf
Starting program: /usr/bin/fluent-bit -v -c /etc/fluent-bit/fluent-bit.conf
Fluent Bit v1.8.9
* Copyright (C) 2019-2021 The Fluent Bit Authors
* Copyright (C) 2015-2018 Treasure Data
* Fluent Bit is a CNCF sub-project under the umbrella of Fluentd
* https://fluentbit.io
[2022/01/20 11:45:58] [ info] Configuration:
[2022/01/20 11:45:58] [ info] flush time | 5.000000 seconds
[2022/01/20 11:45:58] [ info] grace | 5 seconds
[2022/01/20 11:45:58] [ info] daemon | 0
[2022/01/20 11:45:58] [ info] ___________
[2022/01/20 11:45:58] [ info] inputs:
[2022/01/20 11:45:58] [ info] cpu
[2022/01/20 11:45:58] [ info] ___________
[2022/01/20 11:45:58] [ info] filters:
[2022/01/20 11:45:58] [ info] ___________
[2022/01/20 11:45:58] [ info] outputs:
[2022/01/20 11:45:58] [ info] file.0
[2022/01/20 11:45:58] [ info] file.1
[2022/01/20 11:45:58] [ info] file.2
[2022/01/20 11:45:58] [ info] ___________
[2022/01/20 11:45:58] [ info] collectors:
[New LWP 2837]
[New LWP 2838]
[2022/01/20 11:45:58] [ info] [engine] started (pid=2834)
[2022/01/20 11:45:58] [debug] [engine] coroutine stack size: 24576 bytes (24.0K)
[2022/01/20 11:45:58] [debug] [storage] [cio stream] new stream registered: cpu.0
[2022/01/20 11:45:58] [ info] [storage] version=1.1.5, initializing...
[2022/01/20 11:45:58] [ info] [storage] in-memory
[2022/01/20 11:45:58] [ info] [storage] normal synchronization mode, checksum disabled, max_chunks_up=128
[2022/01/20 11:45:58] [ info] [cmetrics] version=0.2.2
[2022/01/20 11:45:58] [debug] [file:file.0] created event channels: read=19 write=20
[2022/01/20 11:45:58] [debug] [file:file.1] created event channels: read=21 write=22
[2022/01/20 11:45:58] [debug] [file:file.2] created event channels: read=23 write=24
[2022/01/20 11:45:58] [debug] [router] match rule cpu.0:file.0
[2022/01/20 11:45:58] [debug] [router] match rule cpu.0:file.1
[2022/01/20 11:45:58] [debug] [router] match rule cpu.0:file.2
[2022/01/20 11:45:58] [ info] [sp] stream processor started
[2022/01/20 11:46:03] [debug] [task] created task=0x76ecc0e0 id=0 OK
Thread 2 "flb-pipeline" received signal SIGSEGV, Segmentation fault.
[Switching to LWP 2837]
0x0044f2e4 in flb_input_event_type_is_metric ()
(gdb) info threads
Id Target Id Frame
1 LWP 2834 "fluent-bit" 0x76fadc88 in __aeabi_read_tp ()
from /lib/ld-musl-armhf.so.1
* 2 LWP 2837 "flb-pipeline" 0x0044f2e4 in flb_input_event_type_is_metric ()
3 LWP 2838 "flb-logger" 0x76fadc8c in __aeabi_read_tp ()
from /lib/ld-musl-armhf.so.1
(gdb) backtrace
#0 0x0044f2e4 in flb_input_event_type_is_metric ()
#1 0x004aedd4 in ?? ()
Backtrace stopped: previous frame identical to this frame (corrupt stack?)
```
APKBUILD modification example (overwriting C_FLAGS/CXX_FLAGS):
```diff
build() {
if [ "$CBUILD" != "$CHOST" ]; then
CMAKE_CROSSOPTS="-DCMAKE_SYSTEM_NAME=Linux -DCMAKE_HOST_SYSTEM_NAME=Linux"
fi
# default CORE_STACK_SIZE=((3 * PTHREAD_STACK_MIN) / 2)=3072 is invalid
# based on https://docs.fluentbit.io/manual/administration/configuring-fluent-bit/configuration-file
# set default to 24576
cmake -B build \
-DCMAKE_INSTALL_PREFIX=/usr \
-DCMAKE_INSTALL_LIBDIR=lib \
-DCMAKE_BUILD_TYPE=None \
+ -DCMAKE_CXX_FLAGS='-O2 -fomit-frame-pointer'
+ -DCMAKE_C_FLAGS='-O2 -fomit-frame-pointer'
-DFLB_CORO_STACK_SIZE=24576 \
-DFLB_TESTS_INTERNAL=Yes \
-DFLB_TLS=Yes \
-DFLB_HTTP_SERVER=Yes \
$CMAKE_CROSSOPTS .
make -C build
}
```