alpine issueshttps://gitlab.alpinelinux.org/groups/alpine/-/issues2021-06-28T16:51:56Zhttps://gitlab.alpinelinux.org/alpine/aports/-/issues/12804mkimg: standard image to boot on Intel/AMD devices2021-06-28T16:51:56ZKasper Kmkimg: standard image to boot on Intel/AMD devicesStandard image is not bootable as Extended, which is by design.
Since Extended includes a lot more stuff than to just make it boot with ramfs on baremetal, it would be nice to include Intel/AMD microcodes in the Standard image.Standard image is not bootable as Extended, which is by design.
Since Extended includes a lot more stuff than to just make it boot with ramfs on baremetal, it would be nice to include Intel/AMD microcodes in the Standard image.https://gitlab.alpinelinux.org/alpine/abuild/-/issues/10033Add script to automatically rebuild packages depending on a specific .so2021-10-13T20:46:27ZSören TempelAdd script to automatically rebuild packages depending on a specific .soWhat comes up a lot on IRC is people asking how to rebuild packages on soname version bumps. I think several developers have scripts in their `~/bin` for this purpose. Maybe it makes sense to add one of them to abuild itself to make it m...What comes up a lot on IRC is people asking how to rebuild packages on soname version bumps. I think several developers have scripts in their `~/bin` for this purpose. Maybe it makes sense to add one of them to abuild itself to make it more obvious/easier for people to automate package rebuilds.
Thoughts?
I personally have the following script from @ncopa in my `~/bin`:
```shell
#!/bin/sh
prog=$0
usage() {
cat <<EOF
rebuilds and commits packages since given commit
list of packages is read from stdin
usage: $prog: <since commit> <commit message>
example:
apk search -r --origin --exact -q foo-libs | $prog affadeadbeef 'rebuild against foo-libs-1.0'
EOF
exit 1
}
skip_noarch=false
dryrun=false
ignore_error=false
while getopts "nac" opt; do
case $opt in
n) dryrun=true;;
a) skip_noarch=true;;
c) ignore_error=true;;
esac
done
shift $(($OPTIND - 1))
[ $# -lt 2 ] && usage
since=$1
shift
msg=$1
shift
echo "reading packages from stdin..."
pkgs=$(while read i; do echo ${i##*/}; done)
echo "considering: $pkgs"
dirs=
for dir in $(ap builddirs $pkgs); do
if $skip_noarch && grep -q '^arch=.*noarch' $dir/APKBUILD; then
echo "skipping due to noarch: $dir"
continue
fi
changes=$(git log --format=oneline ${since}.. -- $dir)
[ -n "$changes" ] && continue
dirs="$dirs $dir"
done
echo "Rebuilding: $dirs" | tr ' ' '\n'
if $dryrun; then
exit 0
fi
for dir in $dirs; do
name=${dir##*/}
repodir=${dir%/*}
repo=${repodir##*/}
cd $dir
apkgrel -g -a ./APKBUILD
git add APKBUILD \
&& git commit -m "$repo/$name: $msg" \
|| { if ! $ignore_error; then exit 1; fi; }
done
```https://gitlab.alpinelinux.org/alpine/aports/-/issues/12796Major upgrade of Ceph version is not mentioned in the 3.14.0 release notes2022-05-03T21:40:11ZAlain van HoofMajor upgrade of Ceph version is not mentioned in the 3.14.0 release notesThe upgrade of the Ceph packages from 15.x to 16.x is not mentioned in the SIGNIFICANT UPDATES part of the release notes. It has impact (high) in Ceph installations. So next time when a major Ceph version is upgraded, can it be put it in...The upgrade of the Ceph packages from 15.x to 16.x is not mentioned in the SIGNIFICANT UPDATES part of the release notes. It has impact (high) in Ceph installations. So next time when a major Ceph version is upgraded, can it be put it in the SIGNIFICANT UPDATES part of the release notes?Duncan BellamyDuncan Bellamyhttps://gitlab.alpinelinux.org/alpine/aports/-/issues/12792JRE/JDK 11 malfunctions on aarch642021-07-08T20:50:09ZJesse ChanJRE/JDK 11 malfunctions on aarch64`openjdk11` does not work properly on aarch64 platform.
It stuck randomly, seemingly related to network functions.
I observe the issue while trying to port Bazel to Alpine Linux (!22578).
Very interestingly, checks have been disabled...`openjdk11` does not work properly on aarch64 platform.
It stuck randomly, seemingly related to network functions.
I observe the issue while trying to port Bazel to Alpine Linux (!22578).
Very interestingly, checks have been disabled on the platform for a long while due to "These get stuck on the builders :/". (b039d1012b3676731ed179778f2732f7beebd611)
`openjdk13` is the first version that does not "stuck". `openjdk8` probably works as well given that the old Bazel aport uses it, and there was a successful aarch64 Bazel build.
Further investigation is needed, but here is all the info I have at the moment.
cc: @bratkartoffelSimon Fsimon-alpine@fraho.euSimon Fsimon-alpine@fraho.euhttps://gitlab.alpinelinux.org/alpine/aports/-/issues/12787Package request: npm-current2021-08-20T00:59:34ZLauri SvanPackage request: npm-currentAlpine Linux already packages Node.js 16.x as `nodejs-current`. While this is great, it is little to no use without having the associated package manager `npm`, which currently has the base `nodejs` (e.g. version 14) as a dependency.
Th...Alpine Linux already packages Node.js 16.x as `nodejs-current`. While this is great, it is little to no use without having the associated package manager `npm`, which currently has the base `nodejs` (e.g. version 14) as a dependency.
The suggestion is to build Node.js 16.x linked version as `npm-current`. The naming would be consistent with the other package and could easily be updated in tandem with updating `nodejs-current`
Node.js 16 is will be the actively maintained version starting next fall, https://nodejs.org/en/about/releases/ and I think it would be good if alpine packages were prepared for that.https://gitlab.alpinelinux.org/alpine/council/-/issues/6Setting up a legal entity2023-01-24T18:01:00ZCarlo LandmeterSetting up a legal entityThe question has came up multiple times in our meetings. The question is do we really need it?
This issue is to track anything related to setting up an entity.The question has came up multiple times in our meetings. The question is do we really need it?
This issue is to track anything related to setting up an entity.https://gitlab.alpinelinux.org/alpine/aports/-/issues/12783testing/guile-reader: missing /usr/lib/libguile-reader.so2024-03-26T13:20:46ZGeorge Hopkinstesting/guile-reader: missing /usr/lib/libguile-reader.so`guile-reader` does not ship with the symlink `/usr/lib/libguile-reader.so` which is needed for Guile to load the library:
```text
In unknown file:
4 (primitive-load-path "system/reader" #<procedure 7f148d…>)
In system/reader....`guile-reader` does not ship with the symlink `/usr/lib/libguile-reader.so` which is needed for Guile to load the library:
```text
In unknown file:
4 (primitive-load-path "system/reader" #<procedure 7f148d…>)
In system/reader.scm:
64:0 3 (_)
In unknown file:
2 (load-extension "/usr/lib/libguile-reader" "scm_reader_…")
In system/foreign-library.scm:
183:4 1 (load-foreign-library _ #:extensions _ # _ #:search-path …)
In ice-9/boot-9.scm:
1685:16 0 (raise-exception _ #:continuable? _)
ice-9/boot-9.scm:1685:16: In procedure raise-exception:
In procedure load-foreign-library: file: "/usr/lib/libguile-reader", message: "file not found"
```
Temporary fix: `ln -s libguile-reader.so.1 /usr/lib/libguile-reader.so`Sören TempelSören Tempelhttps://gitlab.alpinelinux.org/alpine/abuild/-/issues/10032abuild silently fails if $builddir does not exist2021-06-17T19:24:49ZNewbyteabuild silently fails if $builddir does not existCurrently, if `$builddir` is set to a directory that does not exist, abuild silently fails and keeps using the default build directory. This is confusing as you might not always realise that you have made a typo and end up spending time ...Currently, if `$builddir` is set to a directory that does not exist, abuild silently fails and keeps using the default build directory. This is confusing as you might not always realise that you have made a typo and end up spending time trying to debug something that makes no sense. It would be preferable if abuild failed and said that `$builddir` does not exist.
Another similar issue is that abuild also silently fails if `$builddir` points to a file (and not a directory).https://gitlab.alpinelinux.org/alpine/infra/aports-turbo/-/issues/44Consider making the default package search fuzzy (not exact)2024-03-12T06:56:05ZValentinConsider making the default package search fuzzy (not exact)On most websites search is by default fuzzy, including other distro's package search pages like https://archlinux.org/packages/ and https://www.debian.org/distrib/packages . This is different from https://pkgs.alpinelinux.org/packages w...On most websites search is by default fuzzy, including other distro's package search pages like https://archlinux.org/packages/ and https://www.debian.org/distrib/packages . This is different from https://pkgs.alpinelinux.org/packages where the default is exact.
The website does tell you this when you hover over the field with the mouse but it is easy to miss and not everyone uses the mouse to navigate. If you do miss it then you might end up thinking the package you are looking or does not exist or you miss interesting related packages.
For example if I search for `gdb` on alpine I only see the `gdb` package but not `gdb-doc`. In the other linked searches it shows similar names by default.
To me it would feel better if the search was by default something like `*gdb*` with the results ordered by some kind of similarity metric so that the exact match `gdb` still shows up first.
I understand that this is a subjective preference. I still want to give this feedback as it might confuse other new users.https://gitlab.alpinelinux.org/alpine/aports/-/issues/12751Module request: snd-cs42362021-11-05T17:11:44ZBrian WhiteModule request: snd-cs4236I've recently installed Alpine on some old hardware that has some onboard audio. Unfortunately while Alpine has kernel modules for other Cirrus Logic chipsets, snd-cs4236 is not one of them and is what my motherboard uses. I know the aud...I've recently installed Alpine on some old hardware that has some onboard audio. Unfortunately while Alpine has kernel modules for other Cirrus Logic chipsets, snd-cs4236 is not one of them and is what my motherboard uses. I know the audio works well under Linux (using buildroot for example), so it'd be great to have this available in Alpine out of the box.https://gitlab.alpinelinux.org/alpine/aports/-/issues/12749main/syslog-ng: logrotate skipped because of dual entry for /var/log/messages2021-09-18T14:49:00ZJohn Longemain/syslog-ng: logrotate skipped because of dual entry for /var/log/messagesThe file /etc/logrotate.d/syslog-ng contains the line /var/log/messages. Because this file is also included in the default /etc/logrotate.conf, logrotate will throw an error and skip the syslog-ng file.
The solution is to comment / remo...The file /etc/logrotate.d/syslog-ng contains the line /var/log/messages. Because this file is also included in the default /etc/logrotate.conf, logrotate will throw an error and skip the syslog-ng file.
The solution is to comment / remove the line in either of both files.https://gitlab.alpinelinux.org/alpine/aports/-/issues/12748Unexpected behavior of usbmuxd+udev2021-06-12T08:08:21ZKasper KUnexpected behavior of usbmuxd+udevI have installed Alpine Linux desktop (xorg+dwm) on a laptop (baremetal). After installing `usbmuxd` and `libimobiledevice-progs` packages, I get the following behavior:
* boot the system, (notice that usbmuxd was already running right ...I have installed Alpine Linux desktop (xorg+dwm) on a laptop (baremetal). After installing `usbmuxd` and `libimobiledevice-progs` packages, I get the following behavior:
* boot the system, (notice that usbmuxd was already running right after the boot) attach iPhone via USB and run `idevice_id -l`, it does not list the device.
* kill usbmuxd process, reattach iPhone, a new instance of usbmuxd will automatically spin up. At this point run `idevice_id -l` and it lists the device.
So after the boot, I have to kill usbmuxd (once), and it detects one or more iPhone just fine until the next boot.
It seems like a timing problem that [the udev rule](https://github.com/libimobiledevice/usbmuxd/blob/5e484e18f1383b5a0bd6c353ab1d668b03e4ffab/udev/39-usbmuxd.rules.in#L7) runs usbmuxd process earlier at the point where it is expecting certain kernel module to be loaded, then usbmuxd does not reattempt to inspect the system and stays alive.
If someone has better insights what is going on or best place to fix it, please chime in. :)
ps - on systemd-based OS, usbmuxd uses [service](https://github.com/libimobiledevice/usbmuxd/blob/5e484e18f1383b5a0bd6c353ab1d668b03e4ffab/systemd/usbmuxd.service.in) instead of the udev rule. Maybe we can ditch the udev rule and add openrc initd script for it to resolve this?https://gitlab.alpinelinux.org/alpine/apk-tools/-/issues/10747When a package stops replacing a file, that file gets uninstalled completely ...2022-12-21T18:50:51ZBart RibbersWhen a package stops replacing a file, that file gets uninstalled completely rather than switching back to the version of the original providing packageIn postmarketOS we are currently overwriting `/etc/sudoers` from sudo in one of our packages but we want to stop doing that in [pmaports!2181](https://gitlab.com/postmarketOS/pmaports/-/merge_requests/2181). However while testing this ch...In postmarketOS we are currently overwriting `/etc/sudoers` from sudo in one of our packages but we want to stop doing that in [pmaports!2181](https://gitlab.com/postmarketOS/pmaports/-/merge_requests/2181). However while testing this change we noticed that rather than the file being either reverted back to what sudo itself provides or just being left there, it would get uninstalled instead.
This seems strange, seeing there is still a package on the system that provides (and needs!) that file, it's just the original providing package again. To "fix" it we need to reinstall sudo to let it put it's own file back again, but of course we can't tell all our users to manually run `apk fix sudo` after a random system upgrade.v3.1https://gitlab.alpinelinux.org/alpine/aports/-/issues/127243.13 asterisk agi dump html segfault2021-06-10T13:32:43Z杨文 陈3.13 asterisk agi dump html segfault```bash
asterisk -fc
agi dump html agi.html
```
asterisk under alpine is not very stable, a lot crash, but this one is very easy to reproduce.```bash
asterisk -fc
agi dump html agi.html
```
asterisk under alpine is not very stable, a lot crash, but this one is very easy to reproduce.Timo TeräsTimo Teräshttps://gitlab.alpinelinux.org/alpine/council/-/issues/3Document the governance structure2023-06-16T00:17:39ZKevin DaudtDocument the governance structureWe need to make sure that the decided governance structure is properly documented so that it's clear for everyone.
This can probably be documented in the [governance handbook](https://gitlab.alpinelinux.org/alpine/docs/governance)We need to make sure that the decided governance structure is properly documented so that it's clear for everyone.
This can probably be documented in the [governance handbook](https://gitlab.alpinelinux.org/alpine/docs/governance)Natanael CopaNatanael Copahttps://gitlab.alpinelinux.org/alpine/alpine-conf/-/issues/10482hidden or unbroadcasted ssid in setup-alpine2022-11-18T15:06:54ZKasper Khidden or unbroadcasted ssid in setup-alpineDuring setup-alpine, if we try to connect to a hidden network, it fails due to this condition:
https://gitlab.alpinelinux.org/alpine/alpine-conf/-/blob/e2965a2d5d90297741fd37a1090fe49bc411c65b/setup-interfaces.in#L211
`Invalid SSID: ..`...During setup-alpine, if we try to connect to a hidden network, it fails due to this condition:
https://gitlab.alpinelinux.org/alpine/alpine-conf/-/blob/e2965a2d5d90297741fd37a1090fe49bc411c65b/setup-interfaces.in#L211
`Invalid SSID: ..`
It should allow us to connect with the hidden network's SSID and use `scan_ssid=1` under the hood for wpa_supplicant.conf.https://gitlab.alpinelinux.org/alpine/infra/aports-qa-bot/-/issues/20Backport bot2022-04-23T21:23:00ZJ0WIBackport botCopy from https://gitlab.alpinelinux.org/alpine/infra/infra/-/issues/10714
Would be great to have a bot (similar to [this](https://github.com/rullzer/backportbot)) to create backport MRs from GitLab comments.
The bot should create a ne...Copy from https://gitlab.alpinelinux.org/alpine/infra/infra/-/issues/10714
Would be great to have a bot (similar to [this](https://github.com/rullzer/backportbot)) to create backport MRs from GitLab comments.
The bot should create a new branch based on the requested stable branch, chery-pick the commits from the MR and create a MR if the commits apply. Maybe it could also have some heuristic to solve trivial conflicts, like `pkgrel` bump or fetching intermediate commits.https://gitlab.alpinelinux.org/alpine/aports/-/issues/12694nginx: Issues with Alpine Latest version 3.12 and 3.132021-05-26T15:41:59ZTausif1509nginx: Issues with Alpine Latest version 3.12 and 3.13There is some issues with the Alpine latest version (3.12 and 3.13) which fails to read all the nginx variables.There is some issues with the Alpine latest version (3.12 and 3.13) which fails to read all the nginx variables.Jakub JirutkaJakub Jirutkahttps://gitlab.alpinelinux.org/alpine/aports/-/issues/12690feat:metasploit-framework2022-08-18T12:59:35ZTux Da Penguinfeat:metasploit-frameworkMetasploit Framework is a Ruby-based, modular penetration testing platform that enables you to write, test, and execute exploit code.
**source**: [https://github.com/rapid7/metasploit-framework](https://github.com/rapid7/metasploit-fram...Metasploit Framework is a Ruby-based, modular penetration testing platform that enables you to write, test, and execute exploit code.
**source**: [https://github.com/rapid7/metasploit-framework](https://github.com/rapid7/metasploit-framework)
**homepage**: [www.metasploit.com](https://www.metasploit.com/)
**depends**:`ruby-irb ruby subversion ruby-dev libpcap-dev postgresql postgresql-dev`
**installation**:
( `wget http://downloads.metasploit.com/data/releases/framework-latest.tar.bz2`
`tar -jxf framework-latest.tar.bz2`
`sudo mkdir -p /opt/metasploit4`
`sudo cp -a msf3/ /opt/metasploit4/msf`
`sudo chown root:root -R /opt/metasploit4/msf`
`sudo ln -sf /opt/metasploit4/msf/msf* /usr/local/bin/` )https://gitlab.alpinelinux.org/alpine/aports/-/issues/12686feat: munin-async2021-05-24T15:43:15Zbrknkfrfeat: munin-asyncPlease include `munin-async` into `munin-node` or include it as separate package. `munin-async` is an asynchronous proxy for munin-node which heavily reduces the load of munin, see http://guide.munin-monitoring.org/en/latest/node/async.h...Please include `munin-async` into `munin-node` or include it as separate package. `munin-async` is an asynchronous proxy for munin-node which heavily reduces the load of munin, see http://guide.munin-monitoring.org/en/latest/node/async.html.
I manually installed the files `munin-async` (the helper) and `munin-asyncd` (the daemon) under /usr/sbin and created a simple startup script for it and it seems to work just very fine.
```
#!/sbin/openrc-run
# munin-asyncd init.d file for alpine linux.
name="munin-async"
description="Asynchronous proxy for munin-node"
pidfile=/run/munin/${name}.pid
command=/usr/sbin/munin-asyncd
command_user="munin-async:munin-async"
command_background=true
depend() {
need net
use munin-node
after firewall
}
start_pre() {
checkpath -d -o munin-async:munin-async -m755 /var/lib/munin-async
}
```
Could you do that @stwa?Stefan WagnerStefan Wagner