aports issueshttps://gitlab.alpinelinux.org/alpine/aports/-/issues2020-05-25T16:23:28Zhttps://gitlab.alpinelinux.org/alpine/aports/-/issues/11576community/dzone: test failures2020-05-25T16:23:28ZKevin Daudtcommunity/dzone: test failuresdzone fails to build due to build failures:
```
=========================== short test summary info ============================
FAILED test_dzonegit.py::test_get_head - AssertionError: assert '4b825dc642cb...
FAILED test_dzonegit.py::t...dzone fails to build due to build failures:
```
=========================== short test summary info ============================
FAILED test_dzonegit.py::test_get_head - AssertionError: assert '4b825dc642cb...
FAILED test_dzonegit.py::test_check_whitespace_errors - dzonegit.HookExceptio...
FAILED test_dzonegit.py::test_get_altered_files - subprocess.CalledProcessErr...
FAILED test_dzonegit.py::test_check_updated_zones - subprocess.CalledProcessE...
FAILED test_dzonegit.py::test_post_receive - subprocess.CalledProcessError: C...
========================= 5 failed, 16 passed in 1.13s =========================
```3.12.0Jakub JirutkaJakub Jirutkahttps://gitlab.alpinelinux.org/alpine/aports/-/issues/7870ln: /boot/boot: Operation not permitted2020-05-27T08:53:22ZNazar Mokrynskyiln: /boot/boot: Operation not permittedMy system is UEFI-based and /boot is a separate ESP partition:
/dev/sda1 on /boot type vfat (rw,relatime,fmask=0022,dmask=0022,codepage=437,iocharset=utf8,shortname=mixed,errors=remount-ro,discard)
When upgrading kernels I get a wa...My system is UEFI-based and /boot is a separate ESP partition:
/dev/sda1 on /boot type vfat (rw,relatime,fmask=0022,dmask=0022,codepage=437,iocharset=utf8,shortname=mixed,errors=remount-ro,discard)
When upgrading kernels I get a warning \`ln: /boot/boot: Operation not
permitted\`:
localhost:~# apk upgrade
(1/2) Upgrading xen-libs (4.8.1-r4 -> 4.8.2-r0)
(2/2) Upgrading linux-hardened@edge-main (4.9.49-r0 -> 4.9.50-r0)
Executing busybox-1.26.2-r6.trigger
Executing kmod-23-r1.trigger
Executing mkinitfs-3.1.0-r1.trigger
==> initramfs: creating /boot/initramfs-hardened
ln: /boot/boot: Operation not permitted
Executing syslinux-6.04_pre1-r1.trigger
OK: 588 MiB in 134 packages
localhost:~# ls -lh /boot
total 20032
drwxr-xr-x 3 root root 4.0K Jul 21 02:46 EFI
-rwxr-xr-x 1 root root 3.9M Sep 14 12:19 System.map-hardened
-rwxr-xr-x 1 root root 161.2K Sep 14 12:19 config-hardened
-rwxr-xr-x 1 root root 454 Sep 14 12:36 extlinux.conf
-rwxr-xr-x 1 root root 422 Sep 14 11:55 extlinux.conf.old
-rwxr-xr-x 1 root root 10.9M Sep 19 11:05 initramfs-hardened
-rwxr-xr-x 1 root root 177.7K Sep 19 11:06 libcom32.c32
-rwxr-xr-x 1 root root 23.1K Sep 19 11:06 libutil.c32
-rwxr-xr-x 1 root root 11.4K Sep 19 11:06 mboot.c32
-rwxr-xr-x 1 root root 25.9K Sep 19 11:06 menu.c32
-rwxr-xr-x 1 root root 26.4K Sep 19 11:06 vesamenu.c32
-rwxr-xr-x 1 root root 4.3M Sep 14 12:19 vmlinuz-hardened
Not sure where it comes from, but it happens since I’ve started using
Alpine Linux.
I’m on 3.6 stable with kernel from Edge.
*(from redmine: issue id 7870, created on 2017-09-19)*3.12.0https://gitlab.alpinelinux.org/alpine/aports/-/issues/11357clang 10 cant compile trivial C code on x862020-05-27T12:56:15ZMikeclang 10 cant compile trivial C code on x86Alpine, latest edge, x86. Trivial code.
x64 all ok.
```
$ cat main.c
#include <stdio.h>
int main(void) {
printf("mike\n");
return 0;
}
$ gcc -Wall -Wextra main.c && ./a.out
mike
$ rm a.out
$ clang -Wall -Wextra main.c ...Alpine, latest edge, x86. Trivial code.
x64 all ok.
```
$ cat main.c
#include <stdio.h>
int main(void) {
printf("mike\n");
return 0;
}
$ gcc -Wall -Wextra main.c && ./a.out
mike
$ rm a.out
$ clang -Wall -Wextra main.c && ./a.out
-ash: ./a.out: not found
$ file a.out
a.out: ELF 32-bit LSB shared object, Intel 80386, version 1 (SYSV), dynamically linked, interpreter /lib/ld-musl-i586.so.1, with debug_info, not stripped
$ clang -v | head -1
Alpine clang version 10.0.0 (git://git.alpinelinux.org/aports c22d125b0a21ab5215b997b7113a9e3169242505)
Target: i586-alpine-linux-musl
Thread model: posix
InstalledDir: /usr/bin
Found candidate GCC installation: /usr/bin/../lib/gcc/i586-alpine-linux-musl/9.3.0
Found candidate GCC installation: /usr/lib/gcc/i586-alpine-linux-musl/9.3.0
Selected GCC installation: /usr/bin/../lib/gcc/i586-alpine-linux-musl/9.3.0
Candidate multilib: .;@m32
Selected multilib: .;@m32
```3.12.0Rasmus Thomsenoss@cogitri.devRasmus Thomsenoss@cogitri.devhttps://gitlab.alpinelinux.org/alpine/aports/-/issues/11591Alpine 3.12 checklist2020-05-30T09:02:54ZKevin DaudtAlpine 3.12 checklist* [x] check that kernel version are in sync (eg linux-lts and linux-rpi)
* [x] check that raspberrypi-bootloader is up-to-date
* [x] create new milestone https://gitlab.alpinelinux.org/alpine/aports/-/milestones
* [x] change milestone to...* [x] check that kernel version are in sync (eg linux-lts and linux-rpi)
* [x] check that raspberrypi-bootloader is up-to-date
* [x] create new milestone https://gitlab.alpinelinux.org/alpine/aports/-/milestones
* [x] change milestone to version-next on all unresolved issues
* [x] set version in main/alpine-base. see git log for commit message format
* [x] `git tag -a <version>`
* [x] before git push, verify that builders are idle. don’t push until they are
* [x] `git push && git push --tags`
* [x] For new stable branch
* [x] create new remote stable branch: `git checkout -b 3.12-stable && git push --set-upstream origin 3.12-stable`
on each builder do:
* [x] `cd ~/aports && git fetch origin && git checkout -b 3.12-stable -t origin/3.12-stable`
* [x] `sudo sed -i -e 's/git_branch=master/git_branch=3.12-stable/' /etc/conf.d/mqtt-exec.aports-build`
* [x] Wait til build server is idle
* [x] reboot
* [x] update this doc (replace 3.12-stable with 3.12-stable)
* [x] write release notes and publish on alpinelinux.org
* [x] update https://wiki.alpinelinux.org/wiki/Alpine_Linux:Releases
* [x] verify that builders complete the release build successfully (check if release is uploaded to dl-master)
* [x] sign releases
* [x] make docker image release PR
* [x] update topic in IRC channels
* [x] send release announcement to mailto:~alpine/announce@lists.alpinelinux.org with BCC distro@distrowatch.org
* [x] post a tweet (https://tweetdeck.twitter.com)3.12.0https://gitlab.alpinelinux.org/alpine/aports/-/issues/11009Problem with logrotate config for rsyslog2021-09-18T14:49:00ZHenrik RiomarProblem with logrotate config for rsyslogThe file `/etc/logrotate.d/rsyslog` has issues that causes nightly error mails to be sent
From the cron mail for `/etc/periodic/daily/logrotate`
```log
error: rsyslog:1 duplicate log entry for /var/log/messages
error: found error in fil...The file `/etc/logrotate.d/rsyslog` has issues that causes nightly error mails to be sent
From the cron mail for `/etc/periodic/daily/logrotate`
```log
error: rsyslog:1 duplicate log entry for /var/log/messages
error: found error in file rsyslog, skipping
error: stat of /var/log/boot.log failed: No such file or directory
```
There are two issues:
1. nothing seems to create `/var/log/boot.log` and it is expected to be present
1. It lists `/var/log/messages` that is already listed in `/etc/logrotate.conf`3.12.0Henrik RiomarHenrik Riomarhttps://gitlab.alpinelinux.org/alpine/aports/-/issues/5278Enable CONFIG_USB_GADGET in kernel config2022-02-13T17:11:42ZScrumpy JackEnable CONFIG_USB_GADGET in kernel confighttps://www.kernel.org/doc/htmldocs/gadget/
It’s handy for connecting embedded devices or microbaord to your USB
port, thethering, TCP/IP over USB etc.
*(from redmine: issue id 5278, created on 2016-03-15)*https://www.kernel.org/doc/htmldocs/gadget/
It’s handy for connecting embedded devices or microbaord to your USB
port, thethering, TCP/IP over USB etc.
*(from redmine: issue id 5278, created on 2016-03-15)*3.12.0https://gitlab.alpinelinux.org/alpine/aports/-/issues/11001remove patch from busybox built-ins2022-06-29T11:28:03Zrofl0rremove patch from busybox built-insbusybox patch is a prototype, it works only when the patch to be applied requires zero fuzz.
therefore it is broken as this means as soon as you update the version of package to be applied to it will cause an error, or if you have multip...busybox patch is a prototype, it works only when the patch to be applied requires zero fuzz.
therefore it is broken as this means as soon as you update the version of package to be applied to it will cause an error, or if you have multiple patches that touch the same file.
alpine developers are quite aware of the brokenness, that's why the real patch program is in deps for abuild.
removing patch from busybox has the following advantages:
- shaving off 10-20KB from minimal docker image
- people maintaing projects that require a working patch program don't need to add a configure check "checking whether patch works ... no, broken alpine patch which doesn't support fuzz detected"
note that alpine is the only distro i'm aware of that has the broken busybox patch in its base install.
additionally patch is a developer's tool with zero relation to POSIX tools mandated in a base install (i.e. it's not a coreutils-league program). having it built into busybox is roughly equivalent to adding and enabling tcc (tiny C Compiler) to busybox. the result will be to have a semi-working developer tool nobody serious will use in the base install.3.12.0