alpine-conf issueshttps://gitlab.alpinelinux.org/alpine/alpine-conf/-/issues2024-03-27T22:18:30Zhttps://gitlab.alpinelinux.org/alpine/alpine-conf/-/issues/10577setup-desktop: Add elementaryOS2024-03-27T22:18:30ZAngelo Verlain Shemasetup-desktop: Add elementaryOSelementaryOS could be added with pantheon, elementary-photos, etc..elementaryOS could be added with pantheon, elementary-photos, etc..https://gitlab.alpinelinux.org/alpine/alpine-conf/-/issues/10576setup-desktop: update list of KDE packages2024-03-20T08:22:38ZPatrycja Rosaalpine@ptrcnull.mesetup-desktop: update list of KDE packagesfor example, `kgamma5` no longer existsfor example, `kgamma5` no longer existshttps://gitlab.alpinelinux.org/alpine/alpine-conf/-/issues/10575When using disk encryption, swap is not encrypted2024-02-23T22:55:31Ztie-lingWhen using disk encryption, swap is not encryptedI am using version 3.19.1. When installing the system with
```
setup-disk -e -m sys /dev/sda
# -e for encrypted
# -m for system disk
```
The script creates an encrypted system partition and an unencrypted swap partition, mounted at b...I am using version 3.19.1. When installing the system with
```
setup-disk -e -m sys /dev/sda
# -e for encrypted
# -m for system disk
```
The script creates an encrypted system partition and an unencrypted swap partition, mounted at boot.
Wouldn't a plain-text swap partition leak the key material, and other confidential information, when the system is running? At the very least, I think we can suggest `-s 0` for no swap for this scenario and use a swap file instead.https://gitlab.alpinelinux.org/alpine/alpine-conf/-/issues/10571lbu creates apkovl overlay file, but it doesn't apply on reboot.2023-12-12T13:26:26Zxopher314lbu creates apkovl overlay file, but it doesn't apply on reboot.Admittedly I am fairly new to linux in general and am using this for a very specified task so it's entirely possible I'm missing something obvious. I've learned a lot trying to get this to work, but please bear with me.
I'm running Alp...Admittedly I am fairly new to linux in general and am using this for a very specified task so it's entirely possible I'm missing something obvious. I've learned a lot trying to get this to work, but please bear with me.
I'm running Alpine on a Raspberry Pi in Diskless mode. I've configured `lbu_backupdir=/media/mmcblk0p1/media` and when I run `lbu ci` I see that the apkovl is created in the target directory. I can extract the files from the apkovl and my changes are there, but when I reboot the pi, the overlay isn't applied.
It seems that I'm not the only person having this issue. Others have been discussing this for years. For instance: [Another thread on reddit with the same issue](https://www.reddit.com/r/AlpineLinux/comments/pa3vnc/lbu_commit_doesnt_work_when_trying_to_install_in/)
Maybe this is something that I'm fundamentally misunderstanding or the wiki isn't adequately explaining for someone who isn't a full-time linux guru, but I've been beating my head against it for three days and it feels like it just doesn't work.
Any help would be appreciated, thank you.https://gitlab.alpinelinux.org/alpine/alpine-conf/-/issues/10569setup-keymap is missing neo-bone keymap2023-12-12T17:45:13Zskye gänseblumsetup-keymap is missing neo-bone keymaphello, this is a minor issue but it’s just not a super comfy experience to start a livesystem and be unable to load the keymap i use every day (de-neo-bone) because without that i can’t type all my passwords, including my luks password t...hello, this is a minor issue but it’s just not a super comfy experience to start a livesystem and be unable to load the keymap i use every day (de-neo-bone) because without that i can’t type all my passwords, including my luks password that i kind of need in order to access my hard drive. the keymap is a bit niche but all the other linux livesystems have it (gentoo, arch, etc) so i hope this is not a very unreasonable request. i did try to convert the .map file to a binary file with loadkeys -b on my other system but it failed with an error that the search engines have never heard of and at that point i just have to admit i have absolutely no idea how any of this works and hope that one of you is smarter than i amhttps://gitlab.alpinelinux.org/alpine/alpine-conf/-/issues/10568setup-ntp: delete hwclock, add osclock2024-03-27T19:29:00Zllightcbsetup-ntp: delete hwclock, add osclock.. in the case, as described [here](https://gitlab.alpinelinux.org/alpine/aports/-/issues/11889#note_112907)?.. in the case, as described [here](https://gitlab.alpinelinux.org/alpine/aports/-/issues/11889#note_112907)?https://gitlab.alpinelinux.org/alpine/alpine-conf/-/issues/10561setup-disk ignores proxy setting in setup-alpine before it2023-05-10T02:37:16ZHenrik Riomarsetup-disk ignores proxy setting in setup-alpine before itFound in `alpine-virt-3.18.0_rc5-x86_64.iso`
Setup proxy server in `setup-alpine`
```
HTTP/FTP proxy URL? (e.g. 'http://proxy:8080', or 'none') [none] http://192.168.99.10:3128
Which NTP client to run? ('busybox', 'openntpd', 'chrony' ...Found in `alpine-virt-3.18.0_rc5-x86_64.iso`
Setup proxy server in `setup-alpine`
```
HTTP/FTP proxy URL? (e.g. 'http://proxy:8080', or 'none') [none] http://192.168.99.10:3128
Which NTP client to run? ('busybox', 'openntpd', 'chrony' or 'none') [chrony]
```
But then ignored when running `setup-disk`
```
# setup-disk -m sys /mnt
...
ERROR: zstd-libs-1.5.5-r4: network error (check Internet connection and firewall)
ERROR: kmod-30-r3: network error (check Internet connection and firewall)
ERROR: kmod-openrc-30-r3: network error (check Internet connection and firewall)
ERROR: lddtree-1.27-r0: network error (check Internet connection and firewall)
ERROR: argon2-libs-20190702-r4: network error (check Internet connection and firewall)
ERROR: device-mapper-libs-2.03.21-r2: network error (check Internet connection and firewall)
...
```
```
# cat /etc/profile.d/proxy.sh
# this file was generated with and might get overwritten by setup-proxy
export http_proxy=http://192.168.99.10:3128
export https_proxy=http://192.168.99.10:3128
export ftp_proxy=http://192.168.13.99:3128
export no_proxy=localhost
```
I guess `setup-disk` should be sourcing `/etc/profile.d/proxy.sh`
Workaround needed currently
```
test-domu:~# . /etc/profile.d/proxy.sh
test-domu:~# umount /mnt/
test-domu:~# mkfs.ext4 /dev/xvda1
test-domu:~# mount -t ext4 /dev/xvda1 /mnt
test-domu:~# setup-disk -m sys /mnt
Installing system on /dev/xvda1:
extlinux: Not a directory: /mnt/boot
100% ████████████████████████████████████████████==> initramfs: creating /boot/initramfs-virt
/boot is device /dev/xvda1
extlinux: no previous syslinux boot sector found
You might need fix the MBR to be able to boot
```https://gitlab.alpinelinux.org/alpine/alpine-conf/-/issues/10556TUI with dialog2023-03-30T01:43:12ZDrSheppardTUI with dialogTerminal user interface help newbies install alpine in interactive mode. It will also help to attract new usersTerminal user interface help newbies install alpine in interactive mode. It will also help to attract new usershttps://gitlab.alpinelinux.org/alpine/alpine-conf/-/issues/10552issues with alpine on a micro sd card2023-05-02T16:35:30ZGhost Userissues with alpine on a micro sd cardI'm trying to install alpine linux to a micro sd card through an hp elitebook 810 revolve g3, but couldn't find my home network. Other networks were still available, and I was eventually able to get through setup-alpine once I connected ...I'm trying to install alpine linux to a micro sd card through an hp elitebook 810 revolve g3, but couldn't find my home network. Other networks were still available, and I was eventually able to get through setup-alpine once I connected to my campus's public network.
I couldn't however boot into it without using an adapter and usb reader, despite the laptop having a dedicated micro sd card slot and having enabled sd card boot in the bios. I didn't have any issue booting into the live iso through the laptop's dedicated slot.https://gitlab.alpinelinux.org/alpine/alpine-conf/-/issues/10551Support gummiboot as EFI bootloader2023-02-09T16:50:10ZPatrycja Rosaalpine@ptrcnull.meSupport gummiboot as EFI bootloaderit's more lightweight than grub, is in main already and its config wouldn't be hard to implementit's more lightweight than grub, is in main already and its config wouldn't be hard to implementhttps://gitlab.alpinelinux.org/alpine/alpine-conf/-/issues/10549Make ERASE_DISK (setup-disk) via setup-alpine USEANSWERFILE2023-02-02T23:07:16ZRogério da Silva YokomizoMake ERASE_DISK (setup-disk) via setup-alpine USEANSWERFILEOn `setup-disk`, there is an option to non interactively erase disks via `ERASE_DISK=/dev/sda setup-disk -m sys /dev/sda`.
The same idea also works with `setup-alpine`.
https://gitlab.alpinelinux.org/alpine/alpine-conf/-/blob/4f5e613ab...On `setup-disk`, there is an option to non interactively erase disks via `ERASE_DISK=/dev/sda setup-disk -m sys /dev/sda`.
The same idea also works with `setup-alpine`.
https://gitlab.alpinelinux.org/alpine/alpine-conf/-/blob/4f5e613ab51fe2d630d1300335f640782752a19b/setup-disk.in#L866
It would be nice to be able to set `ERASE_DISK` via `USEANSERFILE`.
```
setup-alpine -f ANSWERS
# ANSWERS file
ERASE_DISK=/dev/sda # <---- Does not pass through from setup-alpine into setup-disk
DISKOPTS="-m sys /dev/sda"
```
Since it is possible to define `DISKOPTS` via `USEANSERFILE`, I see no reason why `ERASE_DISK` could not be exported/forwarded. I could send a patch for this.
relevant lines:
* https://gitlab.alpinelinux.org/alpine/alpine-conf/-/blob/4f5e613ab51fe2d630d1300335f640782752a19b/setup-alpine.in#L72
* https://gitlab.alpinelinux.org/alpine/alpine-conf/-/blob/4f5e613ab51fe2d630d1300335f640782752a19b/setup-alpine.in#L263https://gitlab.alpinelinux.org/alpine/alpine-conf/-/issues/10544setup-desktop: run automatically during setup-alpine2023-12-01T15:18:44ZPatrycja Rosaalpine@ptrcnull.mesetup-desktop: run automatically during setup-alpinecurrently, users have to run `setup-desktop` manually during the installation; due to insufficient documentation, this might not be immediately obvious.
as such, `setup-desktop` should be executed during the usual installation, with an ...currently, users have to run `setup-desktop` manually during the installation; due to insufficient documentation, this might not be immediately obvious.
as such, `setup-desktop` should be executed during the usual installation, with an option to not install any desktop at allhttps://gitlab.alpinelinux.org/alpine/alpine-conf/-/issues/10543setup-interfaces: allow for picking the wireless network by list index number2022-11-21T15:01:03ZPatrycja Rosaalpine@ptrcnull.mesetup-interfaces: allow for picking the wireless network by list index numbersometimes typing the full network name can be a bit annoying, it would be nice if users were presented with an indexed list, like in setup-apkrepos where you can just enter the number instead of the namesometimes typing the full network name can be a bit annoying, it would be nice if users were presented with an indexed list, like in setup-apkrepos where you can just enter the number instead of the namehttps://gitlab.alpinelinux.org/alpine/alpine-conf/-/issues/10535Add support for UEFI Secure Boot2022-09-25T18:56:10ZJakub JirutkaAdd support for UEFI Secure BootIt’s already supported in Alpine, but not in the setup scripts.
https://wiki.alpinelinux.org/wiki/UEFI_Secure_BootIt’s already supported in Alpine, but not in the setup scripts.
https://wiki.alpinelinux.org/wiki/UEFI_Secure_Boothttps://gitlab.alpinelinux.org/alpine/alpine-conf/-/issues/10534It is not possible to backup to a subdir of LBU_MEDIA.2022-09-22T23:59:21Zvinnie costanteIt is not possible to backup to a subdir of LBU_MEDIA.There are mainly two problems, one related to saving and the other to loading at boot.
The first one depends on the backup program `lbu`.
I checked and it is just a logic problem, in the actual program it is assumed that if in the file ...There are mainly two problems, one related to saving and the other to loading at boot.
The first one depends on the backup program `lbu`.
I checked and it is just a logic problem, in the actual program it is assumed that if in the file `/etc/lbu/lbu.conf` the variable `LBU_BACKUPDIR` is specified then the variable `LBU_MEDIA` is not taken into account, however this makes it impossible to have apkovl in a dir other than the root of the boot disk.
Also it seems to me that keeping both variables active causes fstab errors to appear.
My guess is that this should be the logic:
1. If I specify a disk in `LBU_MEDIA` then I am telling `lbu` that it should take care of mounting and unmounting the disk.
- 1.1 If I don't specify an `LBU_BACKUPDIR` then that means apkovl goes into the root of the dir
- 1.2 If I specify an `LBU_BACKUPDIR` then it means the dir is to be considered a subdir of the specified disk
2. I do not specify `LBU_MEDIA` and therefore a disk mount should not be handled:
- 2,1 I specify `LBU_BACKUPDIR` which is to be interpreted relative to the system root.
- 2,2 I do not specify `LBU_BACKUPDIR` then I get help printed.
I tried patching just the commit function and it worked, just I don't have the competence to patch the whole script while avoiding creating bugs.
However I still include the code part in the `cmd_commit` function to highlight the change in logic:
current official code
```sh
mnt="$LBU_BACKUPDIR"
if [ -z "$mnt" ]; then
# find what media to use
media="${1:-$LBU_MEDIA}"
[ -z "$media" ] && usage_commit "1" >&2
# mount media unless its already mounted
mnt=/media/$media
[ -d "$mnt" ] || usage "1" >&2
mount_once_rw "$mnt" || die "failed to mount $mnt"
fi
```
replacenebt code with new logic
```sh
mnt="$LBU_BACKUPDIR"
media="$LBU_MEDIA"
if ! [ -z "$media" ]; then
# mount media unless its already mounted
media="/media/$media"
[ -d "$media" ] || usage "1" >&2
mount_once_rw "$media" || die "failed to mount $media"
# set mnt directory
if ! [ -z "$mnt" ]; then
mnt="$media/$mnt"
else
mnt="$media"
fi
fi
[ -z "$mnt" ] && usage_commit "1" >&2
```
I repeat, this code works, but all the other functions have to be changed, not just the commit.
P.s.
Then there's the boot load problem, the apkovl parameter regarding local paths just seems broken to me, every value I enter doesn't work. And looking at the init for me is just too much :(
There is to say that I had created my boot disk from virtualbox and I don't know if for that reason the disk is mounted in /media/usb even if the disk is /dev/sdb, I wouldn't want that this thing create the problem.https://gitlab.alpinelinux.org/alpine/alpine-conf/-/issues/10525setup-alpine: race condition when initramfs configures network2022-08-19T11:22:54ZDaniel F. Dickinsonsetup-alpine: race condition when initramfs configures network1. The test at https://gitlab.alpinelinux.org/alpine/alpine-conf/-/blob/master/setup-alpine.in#L62 does not detect a network configured via initramfs (e.g. explicit or implicit `ip=dhcp` passed to initramfs), which means that when using ...1. The test at https://gitlab.alpinelinux.org/alpine/alpine-conf/-/blob/master/setup-alpine.in#L62 does not detect a network configured via initramfs (e.g. explicit or implicit `ip=dhcp` passed to initramfs), which means that when using a remote answerfile that the network gets reconfigured.
2. When using udhcpc (the initramfs default), bringing down the network and setup up a new one does not block so, depending on the timing things like `tzdata` download (for `setup-ntp`) can get interrupted and fail (but not fatally; if one is not watching the output one would not be immediately aware of the issue).
3. It seems to me improving test for in an existing network in `setup-interfaces` at https://gitlab.alpinelinux.org/alpine/alpine-conf/-/blob/master/setup-interfaces.in#L56 and moving to `lib-alpine.sh` might be the way to go.
4. In my testing I created what I consider a 'hackier' solution (it works, but I think it's 'messy') which is to create a sentinel file `/var/cache/misc/earlynet` with either `udhcpc` or `manual` (depending on how the the network was configured) in `initramfs-init`'s `config_ip` function and copying to the new `$sysroot` in the same location just before `pivot_root`. I then used the function below to check for the presence of a network at `setup-alpine` in place of the current line 62 check:
```
is_network_up() {
if [ -s /var/cache/misc/earlynet ]; then
case $(cat /var/cache/misc/earlynet) in
udhcpc|manual)
return 0;;
esac
elif rc-status networking --quiet status; then
return 0
fi
return 1
}
```
5. This eliminated the network race condition for me, but I'd like to know, for creating an MR, which solution you would prefer.
This was discovered will working on https://gitlab.alpinelinux.org/danielfdickinson/aports/-/merge_requests/1
Also related:
https://gitlab.alpinelinux.org/danielfdickinson/mkinitfs/-/merge_requests/1
and
https://gitlab.alpinelinux.org/alpine/mkinitfs/-/issues/26
Also, where is the best place to handle such cross-repository issues / MR sets?https://gitlab.alpinelinux.org/alpine/alpine-conf/-/issues/10524lbu pkg support specified list2022-07-13T15:45:47Z杨文 陈lbu pkg support specified listLike `lbu pkg -l mysql.lbu.list`, can used package for some apps, is this abuse the lbu ?
But backup a part of sys is still local backup, :PLike `lbu pkg -l mysql.lbu.list`, can used package for some apps, is this abuse the lbu ?
But backup a part of sys is still local backup, :Phttps://gitlab.alpinelinux.org/alpine/alpine-conf/-/issues/10523lbu support commit if any changes2022-07-13T15:42:36Z杨文 陈lbu support commit if any changes
Current workaround
```bash
[ $(lbu st | wc -c) = "0" ] && echo No changes || lbu ci
```
Better for lbu commit support changes only
Current workaround
```bash
[ $(lbu st | wc -c) = "0" ] && echo No changes || lbu ci
```
Better for lbu commit support changes only3.15https://gitlab.alpinelinux.org/alpine/alpine-conf/-/issues/10515Add chroot script2022-05-28T09:03:16ZAnjandev MomiAdd chroot scripthttps://wiki.alpinelinux.org/wiki/Chroot#Performing_the_chroot
I would be willing to submit a MR with this script so it's easier to chroot on a livecd. Will this be accepted?https://wiki.alpinelinux.org/wiki/Chroot#Performing_the_chroot
I would be willing to submit a MR with this script so it's easier to chroot on a livecd. Will this be accepted?https://gitlab.alpinelinux.org/alpine/alpine-conf/-/issues/10511lbu: support backups of multiple hosts on one device2022-05-13T06:04:11ZRoland Pabellbu: support backups of multiple hosts on one deviceI have two computers running apline and would like to use the same usb stick to save their lbu backup files. But lbu complains when there are two apkovl files present:
~~~
two:/mnt# lbu ci
The following apkovl file(s) were found:
/media...I have two computers running apline and would like to use the same usb stick to save their lbu backup files. But lbu complains when there are two apkovl files present:
~~~
two:/mnt# lbu ci
The following apkovl file(s) were found:
/media/usb/one.apkovl.tar.gz
/media/usb/two.apkovl.tar.gz
Please use -d to replace.
~~~
I understand that apkovl is the active file, since backup_apkovl() in lbu replaces "apkovl" with the date.
But I think the functionality could easily be enabled if lbu would only consider files starting with the hostname, which is true almost everywhere except in these 3 occasions in function cmd_commit():
~~~
line 453: local rmfiles=$(ls "$mnt/"*.apkovl.tar.gz* 2>/dev/null)
line 460: [ -z "$DRYRUN" ] && rm "$mnt/"*.apkovl.tar.gz*
line 463: lines=$(ls -1 "$mnt"/*.apkovl.tar.gz* 2>/dev/null)
~~~
I changed these locally to `${hostname}.*.apkovl.tar.gz` and that works as expected.
What I don't know is: Is this by design? Should there ever only be one apkovl file on any given device?