aports issueshttps://gitlab.alpinelinux.org/alpine/aports/-/issues2019-07-12T15:48:46Zhttps://gitlab.alpinelinux.org/alpine/aports/-/issues/10547after install on ssd on reboot sysroot failed2019-07-12T15:48:46Zmartin lolliniafter install on ssd on reboot sysroot failedInstalling alpine in a eeepc netbook and running alpine iso from a
sdcard then execute setup-alpine, last, install \[sys\] to ssd disk to
/dev/sdb.
Reboot and get this sysroot failed. More Details on error.jpg.
The UUID is /dev/sda3 ...Installing alpine in a eeepc netbook and running alpine iso from a
sdcard then execute setup-alpine, last, install \[sys\] to ssd disk to
/dev/sdb.
Reboot and get this sysroot failed. More Details on error.jpg.
The UUID is /dev/sda3 not /dev/sda1 that is the boot partition.
I try changing UUID in extlinux.conf without positive effect.
*(from redmine: issue id 10547, created on 2019-06-09)*
* Uploads:
* ![error](/uploads/e1179e5e98ef129af350017d06eb13bc/error.jpeg)
* ![blkidemergencyconsole](/uploads/0220ab274335e2ca44ec5e50c3abd3a1/blkidemergencyconsole.jpeg) blkid command on emergency console
* ![blkidfromsdcard](/uploads/5949d7c1a7dd2f9281803e7f78b62738/blkidfromsdcard.jpeg) blkid command from console booting from sdcard
* ![kernelpanic](/uploads/d5621daab266883bf2493b6ccb223395/kernelpanic.jpeg) exit command from emergency consoleNatanael CopaNatanael Copahttps://gitlab.alpinelinux.org/alpine/aports/-/issues/10527update-kernel script -- mounting /media/usb failed2021-01-14T05:54:24ZLubos Dolezalupdate-kernel script -- mounting /media/usb failed# update-kernel
%<...
mount: mounting /dev/sda1 on /media/usb failed: Resource busy
The situation is probably associated with the transition modloop to
overlayfs.
Detailed output and other details: https://pastebin.com/raw/NEaH...# update-kernel
%<...
mount: mounting /dev/sda1 on /media/usb failed: Resource busy
The situation is probably associated with the transition modloop to
overlayfs.
Detailed output and other details: https://pastebin.com/raw/NEaHuSNU
*(from redmine: issue id 10527, created on 2019-05-31)*Natanael CopaNatanael Copahttps://gitlab.alpinelinux.org/alpine/aports/-/issues/10385kernel option apkovl is not working2023-05-09T14:24:06Zalgitbotkernel option apkovl is not workingCheck **initramfs-init.in** file:
- **unpack\_apkovl** is called before setting **$repofile**
That’s why booting is crashes with filed to install openssl package
*(from redmine: issue id 10385, created on 2019-05-01)*Check **initramfs-init.in** file:
- **unpack\_apkovl** is called before setting **$repofile**
That’s why booting is crashes with filed to install openssl package
*(from redmine: issue id 10385, created on 2019-05-01)*3.19.0Natanael CopaNatanael Copahttps://gitlab.alpinelinux.org/alpine/aports/-/issues/10351cephfs mount with secretfile2019-08-14T14:08:49ZMatthias Neugebauercephfs mount with secretfileWhen using the secretfile option for cephfs mounts:
mount -t ceph <source> /mnt -o name=myuser,secretfile=/etc/ceph/secret.key,noatime,_netdev
The following error is returned
mount: /mnt: wrong fs type, bad option, bad supe...When using the secretfile option for cephfs mounts:
mount -t ceph <source> /mnt -o name=myuser,secretfile=/etc/ceph/secret.key,noatime,_netdev
The following error is returned
mount: /mnt: wrong fs type, bad option, bad superblock on <source>, missing codepage or helper program, or other error.
dmesg shows:
libceph: bad option at 'secretfile=/etc/ceph/secret.key'
I already installed ceph-base. Mounting with mount.ceph directly works
without problems.
*(from redmine: issue id 10351, created on 2019-04-26)*https://gitlab.alpinelinux.org/alpine/aports/-/issues/10320dovecot init.d discovers the pidfile variable in a way that blocks on a low e...2019-07-12T15:47:12ZHenrik Riomardovecot init.d discovers the pidfile variable in a way that blocks on a low entropy systemFrom console
* /run/lock: creating directory
* /run/lock: correcting owner
* Mounting xenfs ... [ ok ]
[ 3.798024] random: doveconf: getrandom without GRND_NONBLOCK while crng not ready
[ 259.681214] random: c...From console
* /run/lock: creating directory
* /run/lock: correcting owner
* Mounting xenfs ... [ ok ]
[ 3.798024] random: doveconf: getrandom without GRND_NONBLOCK while crng not ready
[ 259.681214] random: crng init done
* Caching service dependencies ... [ ok ]
* Remounting /dev according to fstab ... [ ok ]
Note: that GRND\_NONBLOCK printout is from a patched kernel
From dovecot init.d script
cfgfile=/etc/dovecot/dovecot${instance:+.$instance}.conf
pidfile=$(doveconf -c $cfgfile -h base_dir 2>/dev/null)/master.pid
command=/usr/sbin/dovecot
command_args=${instance:+-c $cfgfile}
Commit that introduced the fault
commit:7307d5b5eb03b045960b5cf85bd98af3f7a9ab54
kernel patch used to find what cases the boot hang:
<@@ -2055,6 +2055,9 @@
if (!crng_ready()) {
if (flags & GRND_NONBLOCK)
return -EAGAIN;
+ printk(KERN_NOTICE "random: %s: getrandom without "
+ "GRND_NONBLOCK while crng not ready\n",
+ current->comm);
ret = wait_for_random_bytes();
if (unlikely(ret))
return ret;
*(from redmine: issue id 10320, created on 2019-04-23)*https://gitlab.alpinelinux.org/alpine/aports/-/issues/10267nmtui can not configure wlan02024-03-19T16:16:23Zxrsnmtui can not configure wlan0I’m using the NetworkManager. I installed the package networkmanager and
started the service. The service is working perfectly since a few
months. Wifi works and connection are established automatically.
But since the beginning it was n...I’m using the NetworkManager. I installed the package networkmanager and
started the service. The service is working perfectly since a few
months. Wifi works and connection are established automatically.
But since the beginning it was not possible to use nmtui to configure my
wlan0 interface, only eth0 and lo. I also added my user to the groups
plugdev and netdev and restarted.
nmcli -d:
DEVICE TYPE STATE CONNECTION
eth0 ethernet unavailable —
wlan0 wifi unavailable —
lo loopback unmanaged —
Currently I use wpa\_supplicant to configure my wifi.
*(from redmine: issue id 10267, created on 2019-04-16)*Natanael CopaNatanael Copahttps://gitlab.alpinelinux.org/alpine/aports/-/issues/10205Can't locate Mail/SpamAssassin/CompiledRegexps/body_0.pm2019-07-12T15:46:21ZJohn DoeCan't locate Mail/SpamAssassin/CompiledRegexps/body_0.pmmail.err spamd\[4515\]: Can’t locate
Mail/SpamAssassin/CompiledRegexps/body\_0.pm in
`INC (you may need to install the Mail::SpamAssassin::CompiledRegexps::body_0 module) (`INC
contains: /var/lib/spamassassin/compiled/5.026/3.004002 /var...mail.err spamd\[4515\]: Can’t locate
Mail/SpamAssassin/CompiledRegexps/body\_0.pm in
`INC (you may need to install the Mail::SpamAssassin::CompiledRegexps::body_0 module) (`INC
contains: /var/lib/spamassassin/compiled/5.026/3.004002 /var/lib/spama
*(from redmine: issue id 10205, created on 2019-04-06)*https://gitlab.alpinelinux.org/alpine/aports/-/issues/10154watchman 4.9.0-r2 does not create a states directory for watchman on installa...2019-07-12T15:45:56ZViraj Trivediwatchman 4.9.0-r2 does not create a states directory for watchman on installationI tried using the watchman package from the Alpine Repository with
Docker https://pkgs.alpinelinux.org/package/edge/testing/x86/watchman
And I get error when I am running watchman.
$ watchman --foreground --logfile=/dev/stdout
...I tried using the watchman package from the Alpine Repository with
Docker https://pkgs.alpinelinux.org/package/edge/testing/x86/watchman
And I get error when I am running watchman.
$ watchman --foreground --logfile=/dev/stdout
2019-03-23T05:47:33,674: [] while computing sockname: failed to create /var/run/watchman/root-state: No such file or directory
ERROR: Job failed: exit code 1
Similar to this issue https://github.com/facebook/watchman/issues/640.
Which I fixed by creating the missing directory manually. Is it supposed
to be like that? Or the Alpine Installation should be generating that
Package? Since the build log of the alpine package did log the state
directory
https://build.alpinelinux.org/buildlogs/build-edge-x86/testing/watchman/watchman-4.9.0-r2.log
. Shouldn’t it be creating directory post installing the package.
*(from redmine: issue id 10154, created on 2019-03-25)*Natanael CopaNatanael Copahttps://gitlab.alpinelinux.org/alpine/aports/-/issues/10031ssl_client cannot handle inappropriate OCSP2020-04-23T14:09:38ZMagicloud Magicloudsssl_client cannot handle inappropriate OCSPThe root cause may be on server side. But as for modern browser, it
falls back to CRL to make things work. ssl\_client just fails.
This even occurs with github, so it is annoying.
Connecting to gist.githubusercontent.com (151.101.1...The root cause may be on server side. But as for modern browser, it
falls back to CRL to make things work. ssl\_client just fails.
This even occurs with github, so it is annoying.
Connecting to gist.githubusercontent.com (151.101.108.133:443)
ssl_client: gist.githubusercontent.com: ocsp verify failed: ocsp response not current
wget: error getting response: Connection reset by peer
*(from redmine: issue id 10031, created on 2019-02-25)*3.9.7https://gitlab.alpinelinux.org/alpine/aports/-/issues/9888vis: Search unexpectedly wraps to file head2022-01-21T22:35:16ZWolfgang Corcoran-Mathevis: Search unexpectedly wraps to file headIn Alpine’s version of the vis editor (v0.5 +curses +lua +acl), using
n/N to skip
between search results frequently causes the cursor to jump to the first
occurrence
of the pattern *in the file*, rather than the next match after the
...In Alpine’s version of the vis editor (v0.5 +curses +lua +acl), using
n/N to skip
between search results frequently causes the cursor to jump to the first
occurrence
of the pattern *in the file*, rather than the next match after the
cursor. This
behavior seems to occur most reliably when the pattern contains a
multibyte (i.e.
non-ASCII) character.
Steps to reproduce:
1. Open a file containing multibyte characters and move the cursor to
somewhere near the middle of the file.
2. Search for a multibyte character with the / command, e.g. /“
3. Use ‘n’ to skip forward to the next match.
Result: The search should skip to the first occurrence of the search
pattern
in the entire file.
After discussion on the editor’s IRC channel, it seems that this bug is
present
only in vis builds compiled on Alpine (i.e. both the packaged version
and new
builds from source). It is not present on glibc systems and OpenBSD, to
list two
other systems on which the above steps were tried.
*(from redmine: issue id 9888, created on 2019-01-21)*https://gitlab.alpinelinux.org/alpine/aports/-/issues/9826Can't boot linux-vanilla on armhf2019-08-12T20:17:49ZPaul GauretCan't boot linux-vanilla on armhfI can’t boot the Alpine linux kernel on my armhf boards (tested on
Cubieboard and OrangePI Plus with similar results).
Sample u-boot session below, messages stop after “Starting kernel” and
board requires a hard reset:
----------------...I can’t boot the Alpine linux kernel on my armhf boards (tested on
Cubieboard and OrangePI Plus with similar results).
Sample u-boot session below, messages stop after “Starting kernel” and
board requires a hard reset:
------------------------------------------------------------------------
=>setenv bootargs earlyprintk console=ttyS0,115200
root=/dev/mmcblk0p2 rw rootwait
=>env set fdt\_high ffffffff
=>fatload mmc 0 0x46000000 vmlinuz-vanilla
3834368 bytes read in 310 ms (11.8 MiB/s)
=>fatload mmc 0 0x49000000
linux-4.19.13-0-vanilla-sun4i-a10-cubieboard.dtb
22448 bytes read in 4 ms (5.4 MiB/s)
=>bootz 0x46000000 - 0x49000000
\#\# Flattened Device Tree blob at 49000000
Booting using the fdt blob at 0x49000000
Using Device Tree in place at 49000000, end 490087af
Starting kernel …
------------------------------------------------------------------------
Building from the same kernel version with a default configuration
(multi\_v7\_defconfig) generates a working kernel.
------------------------------------------------------------------------
make ARCH=arm CROSS\_COMPILE=arm-linux-gnueabihf- multi\_v7\_defconfig
make <s>j 5 ARCH=arm CROSS\_COMPILE=arm-linux-gnueabihf</s>
LOADADDR=0x40008000 zImage dtbs
make <s>j 5 ARCH=arm CROSS\_COMPILE=arm-linux-gnueabihf</s> modules
make <s>j 5 ARCH=arm CROSS\_COMPILE=arm-linux-gnueabihf</s>
INSTALL\_MOD\_PATH=output modules\_install
------------------------------------------------------------------------
*(from redmine: issue id 9826, created on 2019-01-03)*https://gitlab.alpinelinux.org/alpine/aports/-/issues/9809snappy/leveldb: Install .a files2021-11-24T14:47:19ZGhost Usersnappy/leveldb: Install .a filesI’m statically compiling a program with a dependency on leveldb in
Alpine Linux.
It seems that the .a files of leveldb (and snappy, its dependency) are
not installed, so compilation fails with cannot find -lsnappy or cannot
find -llevel...I’m statically compiling a program with a dependency on leveldb in
Alpine Linux.
It seems that the .a files of leveldb (and snappy, its dependency) are
not installed, so compilation fails with cannot find -lsnappy or cannot
find -lleveldb.
*(from redmine: issue id 9809, created on 2018-12-28)*https://gitlab.alpinelinux.org/alpine/aports/-/issues/9653Trying to install desktop causes "ip ioctl 0x8913 failed No such device" errro2023-07-25T07:09:36ZJan CostermansTrying to install desktop causes "ip ioctl 0x8913 failed No such device" errroThis may or may not be the same issue as this one
https://bugs.alpinelinux.org/issues/9079.
The proposed fix does not resolve the issue in my case:
<code class="text">
echo "rc_need=udev-settle" > /etc/conf.d/networking && lbu ...This may or may not be the same issue as this one
https://bugs.alpinelinux.org/issues/9079.
The proposed fix does not resolve the issue in my case:
<code class="text">
echo "rc_need=udev-settle" > /etc/conf.d/networking && lbu ci
</code>
I am using a bootable USB installation on an old laptop (x86 CPU)
Part I. Setting up the bootable usb (this part may not be relevant for
the bug)
1. Create an install usb from alpine-standard-3.8.1-x86.iso
2. setup-alpine
3. prepare the second usb using fdisk, mkdosfs and setup-bootable
Part II. Booting the new bootable USB (run-from-ram)
1. setup-alpine
- I set up wlan0 (eth0 is not configured)
- I use the USB to store the apkovl
2. Save changes
<code class="text">
lbu commit
</code>
3. When rebooting, I have to
- run wpa\_supplicant
<code class="text">
/etc/wpa_supplicantwpa_supplicant -B -i wlan0 -c /etc/wpa_supplicant/wpa_supplicant.conf
</code>
<!-- -->
- and restart networking
<code class="text">
/etc/init.d/networking restart
</code>
4. But when installing a desktop and rebooting, I cannot get the network
up anymore
<code class="text">
setup-xorg-base
</code>
5. On reboot you’ll see “ip ioctl 0x8913 failed No such device” and ip
link show will now no longer show wlan0 even in down state as mentioned
by bug \#9079.
I didn’t try this on Alpine Edge (yet)
*(from redmine: issue id 9653, created on 2018-11-18)*Natanael CopaNatanael Copahttps://gitlab.alpinelinux.org/alpine/aports/-/issues/9510mkinitfs network feature depends on busybox-initscripts.2019-07-12T15:40:45ZMagicloud Magicloudsmkinitfs network feature depends on busybox-initscripts.If I had a container dedicated for generating ramdisk, this package
won’t be installed.
And mkinitfs won’t report any errors but generating a unbootable (no
DHCP) ramdisk.
*(from redmine: issue id 9510, created on 2018-10-05)*If I had a container dedicated for generating ramdisk, this package
won’t be installed.
And mkinitfs won’t report any errors but generating a unbootable (no
DHCP) ramdisk.
*(from redmine: issue id 9510, created on 2018-10-05)*https://gitlab.alpinelinux.org/alpine/aports/-/issues/9439pingu route-table 0 does not work (#9438 assigned to wrong person)2019-07-12T15:40:12ZRyan Campopingu route-table 0 does not work (#9438 assigned to wrong person)According to pingu.conf:
define a route table to use. If unset it will be picked auto.
Setting this to 0 means do not manage routes for this interface
route-table 10
Setting this to zero results in
\[/etc/init.d\]\# service pingu...According to pingu.conf:
define a route table to use. If unset it will be picked auto.
Setting this to 0 means do not manage routes for this interface
route-table 10
Setting this to zero results in
\[/etc/init.d\]\# service pingu start \* Starting pingu …
pingu4057: Invalid route table 0
and the routes are still changed.
*(from redmine: issue id 9439, created on 2018-09-20)*
* Relations:
* duplicates #9438Natanael CopaNatanael Copahttps://gitlab.alpinelinux.org/alpine/aports/-/issues/9364packages that set wrong permissions of /var/tmp2021-11-28T06:50:09ZNatanael Copapackages that set wrong permissions of /var/tmpThere are a few packages that change the permission of `/var/tmp`:
nginx
roundcubemail-openrc
nextcloud-initscript
Permission should be world writable (1777), but the above packages
changes it to 0755.
We have 3 options to fix th...There are a few packages that change the permission of `/var/tmp`:
nginx
roundcubemail-openrc
nextcloud-initscript
Permission should be world writable (1777), but the above packages
changes it to 0755.
We have 3 options to fix this:
1) forbid packages to create anything under `/var/tmp`
2) make abuild error if package set wrong permission under `/var/tmp`
(the above packages will need to manually set the permissions of the
intermediate /var/tmp directory)
3) find some way to exclude intermediate directories from apk so
permissions are not modified.
*(from redmine: issue id 9364, created on 2018-08-30)*
* Relations:
* relates #9246
* relates #2966
* relates #10258
* Changesets:
* Revision 7a6d59536dfe5ea1fbc343993d894d119c701ab1 by Natanael Copa on 2018-09-03T13:23:22Z:
```
main/nginx: fix permissions of /var/tmp
Permissions of /var/tmp should be 1777. Due to limitation in apk/abuild
we need to explicitly set the permissions of intermediate directories
that should not have default.
ref #9364
```
* Revision 822016ff762fd502e594da3d7aa2756d3ce8cb1e by Natanael Copa on 2018-09-10T07:25:31Z:
```
main/nginx: fix permissions of /var/tmp
Permissions of /var/tmp should be 1777. Due to limitation in apk/abuild
we need to explicitly set the permissions of intermediate directories
that should not have default.
ref #9364
(cherry picked from commit 7a6d59536dfe5ea1fbc343993d894d119c701ab1)
```
* Revision 8ded1028a7bcdabc411b39367920a61f7919fdd6 by Natanael Copa on 2019-06-21T10:20:45Z:
```
Revert "main/nginx: move /var/lib/nginx/tmp to /var/tmp/nginx"
FHS-3.0 says that /var/tmp should survive reboots, but for it is common
practice to ignore FHS for security reasons and wipe dirs that are world
writable.
There is no good reason to store nginx data under a world writable
directory, so move it back to /var/lib/nginx/tmp. Other distros does
something similar.
fixes #9246
fixes #10258
ref #9364
This reverts commit d6d624a149ca62af8679baf9cc99ce1354c190f0.
```https://gitlab.alpinelinux.org/alpine/aports/-/issues/9327postfix-cdb please2019-07-12T15:39:17ZJohn Doepostfix-cdb pleaseSubject says it all. You guys have exim-cdb but no postfix-cdb in your
packages. ;-(
postmap cdb:virtual
postmap: fatal: unsupported dictionary type: cdb. Is the postfix-cdb package installed?
make: *** [Makefile:6: virtual....Subject says it all. You guys have exim-cdb but no postfix-cdb in your
packages. ;-(
postmap cdb:virtual
postmap: fatal: unsupported dictionary type: cdb. Is the postfix-cdb package installed?
make: *** [Makefile:6: virtual.cdb] Error 1
*(from redmine: issue id 9327, created on 2018-08-22)*https://gitlab.alpinelinux.org/alpine/aports/-/issues/9015Create separate group for i2c buses in /dev2021-01-09T17:23:01ZalgitbotCreate separate group for i2c buses in /devI suggest to create new group (i.e. i2c) and make i2c bus devices belong
to that group with udev rule like
```
KERNEL=="i2c-[0-9]*", GROUP="i2c", MODE="0660"
```
There are tools like ddcutil (change monitor settings via command line)
w...I suggest to create new group (i.e. i2c) and make i2c bus devices belong
to that group with udev rule like
```
KERNEL=="i2c-[0-9]*", GROUP="i2c", MODE="0660"
```
There are tools like ddcutil (change monitor settings via command line)
which requires access to i2c buses, but are useful in everyday activitiy
of a non-root users.
*(from redmine: issue id 9015, created on 2018-06-15)*https://gitlab.alpinelinux.org/alpine/aports/-/issues/8852LXD/Vanilla - Exposing host folder to guest not working2020-11-14T15:13:37ZSteve ParrisLXD/Vanilla - Exposing host folder to guest not workingExposing a host folder to the guest container with the built-in lxd
function (device add) doesn’t work properly. The folder doesn’t show up
if the folder gets added when the container is stopped. The folder shows
up for one session if th...Exposing a host folder to the guest container with the built-in lxd
function (device add) doesn’t work properly. The folder doesn’t show up
if the folder gets added when the container is stopped. The folder shows
up for one session if the container is already running. It does work
properly on another system (ArchLinux x64). I’ve contacted upstream but
stgraber currently is not at the office for some time providing only
limited support. I’ve created a thread in [official support
forum](https://discuss.linuxcontainers.org/t/mapped-folder-doesnt-show-up-in-container/1540)
as well.
Steps to reproduce:
<code class="text">
lxc init images:alpine/edge alpine
lxc config set alpine security.privileged false
printf "uid 0 0\ngid 0 0" | lxc config set alpine raw.idmap -
lxc config device add alpine myboot disk source=/boot path=/hostboot
lxc start alpine
lxc exec alpine -- ls /hostboot
</code>
/etc/subuid:
root:1000000:65536
/etc/subgid:
root:1000000:65536
lxd-3.0.0-r3
Alpine edge i686
Linux alpine 4.14.37-0-vanilla \#1-Alpine SMP Thu Apr 26 11:44:01 UTC
2018 i686 Linux
*(from redmine: issue id 8852, created on 2018-04-29)*https://gitlab.alpinelinux.org/alpine/aports/-/issues/8851gox package request. (Gox is a simple, no-frills tool for Go cross compilation)2019-07-12T15:35:27ZMichael Lawrencegox package request. (Gox is a simple, no-frills tool for Go cross compilation)https://github.com/mitchellh/gox.git
Gox is a simple, no-frills tool for Go cross compilation that behaves a
lot like standard go build. Gox will parallelize builds for multiple
platforms. Gox will also build the cross-compilation toolc...https://github.com/mitchellh/gox.git
Gox is a simple, no-frills tool for Go cross compilation that behaves a
lot like standard go build. Gox will parallelize builds for multiple
platforms. Gox will also build the cross-compilation toolchain for you.
normally in Gentoo dev-go/gox emerge and done…
alpine docker works , gentoo arm64 qemu not so much. anycase , I have
gentoo catylst as a seed builder … , for a few other toys… gox would be
useful for building a few arm64 golang tools.
*(from redmine: issue id 8851, created on 2018-04-28)*