alpine issueshttps://gitlab.alpinelinux.org/groups/alpine/-/issues2020-02-03T15:15:14Zhttps://gitlab.alpinelinux.org/alpine/docker-abuild/-/issues/62make build-edge recently broke2020-02-03T15:15:14ZRasmus Thomsenoss@cogitri.devmake build-edge recently brokeSeems like ALPINE_IMG isn't being replaced, when running `make build-edge`, as such the build breaks
```
rasmus@alpine ~/P/docker-abuild> make build-edge
sed 's!%%ALPINE_TAG%%!edge!;s!%%ALPINE_REL%%!edge!' \
Dockerfile.in >| Dockerfile...Seems like ALPINE_IMG isn't being replaced, when running `make build-edge`, as such the build breaks
```
rasmus@alpine ~/P/docker-abuild> make build-edge
sed 's!%%ALPINE_TAG%%!edge!;s!%%ALPINE_REL%%!edge!' \
Dockerfile.in >| Dockerfile
DOCKER_BUILDKIT=0 docker build $DOCKER_FLAGS \
-t alpinelinux/docker-abuild:edge-x86_64 .
Sending build context to Docker daemon 184.3kB
Step 1/10 : FROM %%ALPINE_IMG%%/alpine:edge
invalid reference format: repository name must be lowercase
make: *** [Makefile:44: build-edge] Error 1
```https://gitlab.alpinelinux.org/alpine/alpine-baselayout/-/issues/4Why isn't /etc/profile.d/ loaded for a non-login shell?2020-12-04T13:18:54ZFredrik GustafssonWhy isn't /etc/profile.d/ loaded for a non-login shell?Looking into sourcing a script on shell start between different distributions seemed to be a tricky business. That is putting a shell script in /etc/profile.d/ and have it sourced on shell start.
We've found:
| Distribution | Bash(logi...Looking into sourcing a script on shell start between different distributions seemed to be a tricky business. That is putting a shell script in /etc/profile.d/ and have it sourced on shell start.
We've found:
| Distribution | Bash(login) | Bash (non-login) | Zsh (login) | Zsh (non-login) |
| ------------ | ----------- | ---------------- | ------------| --------------- |
| Debian | Yes | No | No | No |
| Ubuntu | Yes | No | No | No |
| Fedora | Yes | Yes | Yes | Yes |
| Alpine | Yes | No | Yes | No |
What's the reason for Alpine not sourcing /etc/profile.d/ when bash and zsh is not started as login shells? To me it seems as Fedora is doing the right thing here and none of the other distributions, but I admit that I might miss something here.https://gitlab.alpinelinux.org/alpine/docker-abuild/-/issues/63dabuild fails to find locally packages if /etc/apk/repositories doesn't use $...2020-02-22T12:01:33ZRasmus Thomsenoss@cogitri.devdabuild fails to find locally packages if /etc/apk/repositories doesn't use ${HOME}/packages for these reposHello,
I use a separate BTRFS subvolume for packages, so my /etc/apk/repositories looks like this:
```
http://dl-cdn.alpinelinux.org/alpine/edge/main
http://dl-cdn.alpinelinux.org/alpine/edge/community
http://dl-cdn.alpinelinux.org/alp...Hello,
I use a separate BTRFS subvolume for packages, so my /etc/apk/repositories looks like this:
```
http://dl-cdn.alpinelinux.org/alpine/edge/main
http://dl-cdn.alpinelinux.org/alpine/edge/community
http://dl-cdn.alpinelinux.org/alpine/edge/testing
/pack/alpine/repo/main
/pack/alpine/repo/community
/pack/alpine/repo/testing
```
This causes dabuild to fail to find locally built packages, since it expects that ${HOME}/packages/${REPO} is in /etc/apk/repositorieshttps://gitlab.alpinelinux.org/alpine/alpine-baselayout/-/issues/5Starting ISO image from GRUB loopback device does not work2021-01-08T23:53:07ZPaulStarting ISO image from GRUB loopback device does not workTrying to boot the [Alpine Linux ISO image][1] from GRUB using [GRUB’s loopback module][2],
loopback loop (hd0,msdos1)/home/myuser/Downloads/alpine-standard-3.12.3-x86_64.iso
set root=(loop)
configfile /boot/grub/grub.cfg
A...Trying to boot the [Alpine Linux ISO image][1] from GRUB using [GRUB’s loopback module][2],
loopback loop (hd0,msdos1)/home/myuser/Downloads/alpine-standard-3.12.3-x86_64.iso
set root=(loop)
configfile /boot/grub/grub.cfg
Alpine Linux is unable to mount the boot media, and drops the user into the initrd shell.
[1]: https://dl-cdn.alpinelinux.org/alpine/v3.12/releases/x86_64/alpine-standard-3.12.3-x86_64.iso
[2]: https://michael-prokop.at/blog/2009/05/25/boot-an-iso-via-grub2/https://gitlab.alpinelinux.org/alpine/docker-abuild/-/issues/64Please add apk fix to entrypoint.sh2020-02-22T11:14:11ZRasmus Thomsenoss@cogitri.devPlease add apk fix to entrypoint.shRight now docker-abuild blows up every time abuild is upgraded:
```
Executing abuild-3.5.0-r1.pre-upgrade
ERROR: abuild-3.5.0-r1: failed to rename usr/bin/.apk.4005a7a50cbc2894af4dab81a00a600592c369d2e2279592 to usr/bin/abuild.
Executin...Right now docker-abuild blows up every time abuild is upgraded:
```
Executing abuild-3.5.0-r1.pre-upgrade
ERROR: abuild-3.5.0-r1: failed to rename usr/bin/.apk.4005a7a50cbc2894af4dab81a00a600592c369d2e2279592 to usr/bin/abuild.
Executing busybox-1.31.1-r11.trigger
1 error; 818 MiB in 242 packages
```
Afterwards dabuild can't be used since it only throws
```
fetch http://dl-cdn.alpinelinux.org/alpine/edge/main/x86_64/APKINDEX.tar.gz
fetch http://dl-cdn.alpinelinux.org/alpine/edge/community/x86_64/APKINDEX.tar.gz
fetch http://dl-cdn.alpinelinux.org/alpine/edge/testing/x86_64/APKINDEX.tar.gz
1 error; 818 MiB in 242 packages
```https://gitlab.alpinelinux.org/alpine/mkinitfs/-/issues/6Maximising partitions at boot time2020-11-26T01:48:58ZMarkMaximising partitions at boot timeA possibly suggestion which we discussed on IRC.
Our use case is VM images which are uploaded to cloud VM providers. We build a standard image of a nominal size and LVM partition layout (eg. 8G), but wish to make available all the dis...A possibly suggestion which we discussed on IRC.
Our use case is VM images which are uploaded to cloud VM providers. We build a standard image of a nominal size and LVM partition layout (eg. 8G), but wish to make available all the disk space on the specific VM for later use by LVM.
Example steps to resize:
$ echo ,+ | sfdisk --partno 2 /dev/vda
$ lvm pvresize /dev/vda2
$ lvm lvresize +20G
However the "sfdisk" step is critical as it is the only one which cannot be done once the system is mounted, and therefore needs to be done
a) at boot time; or
b) at runtime with --force, followed by a reboot.
Boot time possibilies:
* hooks to add arbitary scripts to initramfs; eg.
/etc/mkinitfs/initramfs-hooks/{pre,post}-{lvm,mdadm,cryptsetup,zpool}.d
* first-class feature in initramfs for this case
Here are some notes from the IRC conversation:
```
<ncopa> https://gitlab.alpinelinux.org/alpine/mkinitfs/-/blob/master/initramfs-init.in
<ncopa> i think your problem is slightly trickier than it sounds
<ncopa> we have a C app nlplug-findfs
<ncopa> which will trigger coldplug, load kernel modules, and wait for the event with the specific device it is looking for
<ncopa> i think it will mount it too
<ncopa> i think you need run the resize thing before mount of rootfs, but after the disk is coldplugged
<ncopa> other thing you could do, that does not require modification of nlplug-findfs is to rename lvm and replace it with your own wrapper script
<ncopa> mv /sbin/lvm /sbin/lvm.orig
<ncopa> echo -e "#!/bin/sh\ndo-the-thing\nexec /sbin/lvm.orig" > /sbin/lvm
> There's added complication, which is some VM providers use /dev/sda, others use /dev/vda, and Xen uses /dev/xvda ... Right now Alpine handles that all dynamically as LVM finds its own partition and boot is LABEL=boot
<dne> partprobe/partx doesn't work?
> No, neither of those can re-read a partition table if devices are already in use ... unless I missing something
<ncopa> what i wonder is how initramfs should know if it should resize the parition or not
<ncopa> one option is to run hook, which is removed after first boot and initramfs image regenerated without the hook
<ncopa> other option woudl be to specify it as a boot option
<ncopa> "resize-rootfs" or similar
> Not sure about that; I think better to consider an idempotent process that just makes partitions as big as possible within some spec
> Though I do appreciate the risks of that on hardware etc.
<ncopa> how do you know that it is the last partition? the uevents may not come in order
<ncopa> when sda shows up, there are no sda1
<ncopa> that comes as a separate uevent
<ncopa> then sda2 may or may not show up
<ncopa> but you never know
<ncopa> so what im thinking is: if resize-lvm-rootfs option is set, whenever ther shows up an lvm member, try resize it
<ncopa> if its not the last parition, the resize will fail i suppose
```https://gitlab.alpinelinux.org/alpine/docker-abuild/-/issues/65Add support for rootbld2020-03-27T12:52:33ZBart RibbersAdd support for rootbld`abuild rootbld` will run the build commands in a clean root, and it does some extra things like disabling network access to the build. It would be nice to have this option in docker-abuild as well.`abuild rootbld` will run the build commands in a clean root, and it does some extra things like disabling network access to the build. It would be nice to have this option in docker-abuild as well.https://gitlab.alpinelinux.org/alpine/mkinitfs/-/issues/7Init arguments cannot contain spaces2022-08-19T11:22:54ZRyan GovostesInit arguments cannot contain spacesIt does not seem possible to send a single argument through `init_args` that contains spaces.
Even with something like `init_args="\"hello world\""`, which sets `$KOPT_init_args` to the literal string `"hello world"`, when this gets int...It does not seem possible to send a single argument through `init_args` that contains spaces.
Even with something like `init_args="\"hello world\""`, which sets `$KOPT_init_args` to the literal string `"hello world"`, when this gets interpolated into
```
exec /bin/busybox switch_root $sysroot $chart_init "$KOPT_init" $KOPT_init_args
```
it ends up being sent to the program as two arguments, `"hello` and `world"`.
This prevents doing something like `/bin/sh -c "touch /foo && exec /sbin/init"`.https://gitlab.alpinelinux.org/alpine/docker-abuild/-/issues/66unwritable ~/.abuild2020-05-18T07:21:52ZBart Ribbersunwritable ~/.abuildSince updating my docker-abuild like 2 weeks ago, I just can't use it anymore... Now everytime I run it I get `Error: unwritable ~/.abuild [drwxr-xr-x]`. If I remove the folder completely, same thing happens. If I set it to chmod 777, sa...Since updating my docker-abuild like 2 weeks ago, I just can't use it anymore... Now everytime I run it I get `Error: unwritable ~/.abuild [drwxr-xr-x]`. If I remove the folder completely, same thing happens. If I set it to chmod 777, same thing happens.https://gitlab.alpinelinux.org/alpine/infra/aports-qa-bot/-/issues/11Formalize what level should be logged from services2021-05-01T04:50:54ZLeoFormalize what level should be logged from servicesMy idea is:
## Error
Things that should be investigated and rectified.
Examples:
1. GitLab API call fails
## Warn
when something prevents expected operation but it should be fixed at the source
or there is no way to reasonably fix....My idea is:
## Error
Things that should be investigated and rectified.
Examples:
1. GitLab API call fails
## Warn
when something prevents expected operation but it should be fixed at the source
or there is no way to reasonably fix.
Examples:
1. In AutoMaintainer() the API call to get the APKBUILD works but the APKBUILD
itself has no maintainer to be extracted.
2. In AutoMaintainer() if we get more than 1 maintainer we cannot assign as
Alpine Linux does not have GitLab gold so we just abort
## Info
something happened during normal operation but it is important that the admin
knows.
Example:
1. A service started
2. A service did its job (like AutoMaintainer assigning someone as maintainer)
3. A service finishedhttps://gitlab.alpinelinux.org/alpine/mkinitfs/-/issues/12Compressed overlaytmpfs with zramctl2021-11-23T23:46:51Zomniomni+alpine@hack.orgCompressed overlaytmpfs with zramctlThis is a feature request.
This would enable you to make more use out of a RAM disk for a sysroot overlay.
Would this require the _zram-init_ package to be in the _main_ rather than the _community_ repo?
If noone beats me to it, I mig...This is a feature request.
This would enable you to make more use out of a RAM disk for a sysroot overlay.
Would this require the _zram-init_ package to be in the _main_ rather than the _community_ repo?
If noone beats me to it, I might produce a patch and MR in the future.https://gitlab.alpinelinux.org/alpine/infra/aports-turbo/-/issues/42Allow filtering out -doc, -lang, -dbg, -dev and -static subpackages2020-08-25T10:26:55ZBart RibbersAllow filtering out -doc, -lang, -dbg, -dev and -static subpackagesIt would be nice to filter out such packages as they're often not relevant to my search and fill up the search results.It would be nice to filter out such packages as they're often not relevant to my search and fill up the search results.https://gitlab.alpinelinux.org/alpine/mkinitfs/-/issues/13Add mkinitfs.conf(5) man page2021-01-15T00:39:53Zomniomni+alpine@hack.orgAdd mkinitfs.conf(5) man pageDescribe various available options, other than just `features=`.
I may pick this up in !82, but I haven't written man pages before.Describe various available options, other than just `features=`.
I may pick this up in !82, but I haven't written man pages before.https://gitlab.alpinelinux.org/alpine/infra/aports-turbo/-/issues/38Maintainer lookup by email, not name2018-01-29T17:32:49ZAriadne Conillariadne@ariadne.spaceMaintainer lookup by email, not nameIt is possible that two maintainers might have the same name if it is a common one. So we should use email addresses instead.
It is possible that two maintainers might have the same name if it is a common one. So we should use email addresses instead.
https://gitlab.alpinelinux.org/alpine/infra/aports-turbo/-/issues/9Autolink URLs in message popups on /flagged page2016-04-19T08:47:41ZPrzemysław PawełczykAutolink URLs in message popups on /flagged pageIt would be nice to have autolinking URLs in message popups, so we could simply click such link. Bells and whistles kind of thing, I guess, but would be useful for people browsing /flagged that are not maintainers (as maintainers get me...It would be nice to have autolinking URLs in message popups, so we could simply click such link. Bells and whistles kind of thing, I guess, but would be useful for people browsing /flagged that are not maintainers (as maintainers get messages in their mailboxes).
Remember to use rel="nofollow" in a tag if ever implementing that.
https://gitlab.alpinelinux.org/alpine/mkinitfs/-/issues/15fsck support2021-02-08T12:50:18ZAlex Xu (Hello71)fsck supportext* filesystem is an odd-one-out in that it supports being fscked while mounted. Other filesystems such as F2FS and FAT must be unmounted to fsck properly, or do not require fsck during normal operation, such as XFS, btrfs, ZFS, etc. Ev...ext* filesystem is an odd-one-out in that it supports being fscked while mounted. Other filesystems such as F2FS and FAT must be unmounted to fsck properly, or do not require fsck during normal operation, such as XFS, btrfs, ZFS, etc. Even the ext* fsck while ro-mounted is sketchy though; it doesn't really make sense to fsck using a filesystem that you think may be corrupt. Even when it does work, it sometimes requires reboot, which shouldn't be required if the filesystem is unmounted. This is all a legacy from before initrd/initramfs. In modern era, we should fsck from initramfs when possible, like Debian and I think most other distros.https://gitlab.alpinelinux.org/alpine/infra/aports-turbo/-/issues/2API for all packages2017-03-17T11:51:11ZCarlo LandmeterAPI for all packages*Created by: saulshanabrook*
Is there an HTTP API available to get a list of all packages?
*Created by: saulshanabrook*
Is there an HTTP API available to get a list of all packages?
https://gitlab.alpinelinux.org/alpine/infra/infra/-/issues/335OpenLDAP Authentication for Wiki, Redmine, Sandbox, ....2022-07-23T01:36:19ZKogen MantisOpenLDAP Authentication for Wiki, Redmine, Sandbox, ....Make one unified OpenLDAP user database for Wiki, Redmine, Sandbox
server…. or whatever will apply in the future.
*(from redmine: issue id 335, created on 2010-03-21)*
* Relations:
* relates #523Make one unified OpenLDAP user database for Wiki, Redmine, Sandbox
server…. or whatever will apply in the future.
*(from redmine: issue id 335, created on 2010-03-21)*
* Relations:
* relates #523Daniel Isaksendisaksen@alpinelinux.orgDaniel Isaksendisaksen@alpinelinux.orghttps://gitlab.alpinelinux.org/alpine/infra/aports-turbo/-/issues/22Aggregate flag emails to daily(?) digests2017-01-14T15:25:15ZJakub JirutkaAggregate flag emails to daily(?) digestshttps://gitlab.alpinelinux.org/alpine/infra/aports-turbo/-/issues/7Search should be case-insensitive2020-03-27T10:43:10ZCarlo LandmeterSearch should be case-insensitive*Created by: stwa*
The search is case-sensitive, it would be more intuitive if the search would be case-insensitive.
As package names are always lower-case there should not be any problems.
*Created by: stwa*
The search is case-sensitive, it would be more intuitive if the search would be case-insensitive.
As package names are always lower-case there should not be any problems.