alpine issueshttps://gitlab.alpinelinux.org/groups/alpine/-/issues2022-01-31T05:58:10Zhttps://gitlab.alpinelinux.org/alpine/aports/-/issues/7798add size and package list to https://www.alpinelinux.org/downloads/ items2022-01-31T05:58:10Zalgitbotadd size and package list to https://www.alpinelinux.org/downloads/ itemsCould a size and package list to https://www.alpinelinux.org/downloads/
items?
Otherwise, you’re downloading a pig in a poke.
*(from redmine: issue id 7798, created on 2017-09-06)*Could a size and package list to https://www.alpinelinux.org/downloads/
items?
Otherwise, you’re downloading a pig in a poke.
*(from redmine: issue id 7798, created on 2017-09-06)*https://gitlab.alpinelinux.org/alpine/aports/-/issues/7801package ksh93 from at&t2021-02-09T16:30:19Zalgitbotpackage ksh93 from at&twould like to use KornShell (ksh93v, latest version) because I have many
non simple scripts using ksh93 features.
*(from redmine: issue id 7801, created on 2017-09-09)*would like to use KornShell (ksh93v, latest version) because I have many
non simple scripts using ksh93 features.
*(from redmine: issue id 7801, created on 2017-09-09)*https://gitlab.alpinelinux.org/alpine/aports/-/issues/7948add another version of pure-ftpd package with all features2019-07-12T15:28:34Zgimoh gadd another version of pure-ftpd package with all featuresPlease add another version of pure-ftpd package which, contrary to
current minimal version, has extra features enabled, e.g.: pure-ftpwho
tool, PGSQL support, LDAP support, etc.
For ref, I received those requests for my docker image:
\...Please add another version of pure-ftpd package which, contrary to
current minimal version, has extra features enabled, e.g.: pure-ftpwho
tool, PGSQL support, LDAP support, etc.
For ref, I received those requests for my docker image:
\- pure-ftpwho support: https://github.com/gimoh/docker-pureftpd/pull/3
\- PGSQL support: https://github.com/gimoh/docker-pureftpd/issues/4
- LDAP support: https://github.com/gimoh/docker-pureftpd/issues/5
*(from redmine: issue id 7948, created on 2017-10-02)*https://gitlab.alpinelinux.org/alpine/aports/-/issues/8093Raspberry Pi: Clock skew messages on startup; simple fix2019-07-12T15:29:42ZHarald BeckerRaspberry Pi: Clock skew messages on startup; simple fixThe Raspberry Pi has no hardware clock, so it throw warnings and errors
on OpenRC startup, even when using swclock service instead of hwclock.
A simple fix make OpenRC happy and let those messages vanish:
Create an empty file /etc/init...The Raspberry Pi has no hardware clock, so it throw warnings and errors
on OpenRC startup, even when using swclock service instead of hwclock.
A simple fix make OpenRC happy and let those messages vanish:
Create an empty file /etc/init.d/.use-swclock to signal usage of this
hack (just to be able to disable on systems with hardware clock).
Add the following snippet in /lib/rc/sh/init.sh, just after setting up
/proc:
if \[ -e /etc/init.d/.use-swclock \]; then
“$RC\_LIBEXECDIR/sbin/swclock” /etc/init.d
fi
… with this added, OpenRC set the system clock to the date/time of
/etc/init.d (the last modification time), then use this date to create
the /run directories. As the time of the dependency tree
/run/openrc/deptree is now not below the date of /etc/init.d we are gone
and OpenRC is happy.
The clock shall then still be set with either swclock service or an NTP
service.
The hack just make OpenRC happy and suppresses the confusing “Clock
skew” messages. As far as I can tell, it has no other impacts.
*(from redmine: issue id 8093, created on 2017-11-02)*Natanael CopaNatanael Copahttps://gitlab.alpinelinux.org/alpine/aports/-/issues/8305distributed filesystem sheepdog2021-01-09T17:23:13ZChristian Richterdistributed filesystem sheepdogIt would be very nice to use Alpine as Cluster node, as its slim and
robust. For that a distributed filesystem like “sheepdog” would be very
nice to have.
more info about the sheepdog projekt can be found here:
https://github.com/shee...It would be very nice to use Alpine as Cluster node, as its slim and
robust. For that a distributed filesystem like “sheepdog” would be very
nice to have.
more info about the sheepdog projekt can be found here:
https://github.com/sheepdog/sheepdog/wiki
sheepdog uses an underlying mechanism to communicate beteween the nodes
like corosync or zookeeper, which would need to be added as package as
well.
*(from redmine: issue id 8305, created on 2017-12-15)*https://gitlab.alpinelinux.org/alpine/aports/-/issues/8335package request: icc-profiles-free2022-08-18T13:38:04ZClément Fradet Normandpackage request: icc-profiles-freeHi Alpine Team !
We use ghostscript (package available with Alpine) with
**icc-profiles-free** (the both often work together).
We can’t run our Alpine Docker Containers in production if
icc-profiles-free isn’t available (that’s why t...Hi Alpine Team !
We use ghostscript (package available with Alpine) with
**icc-profiles-free** (the both often work together).
We can’t run our Alpine Docker Containers in production if
icc-profiles-free isn’t available (that’s why this issue is at priority
“high”)
Could you add thios package to Alpine packages ?
Thanks a lot for your help ! <3 <3 <3
Debian Stretch link :
https://packages.debian.org/source/stable/icc-profiles-free
*(from redmine: issue id 8335, created on 2017-12-20)*Timo TeräsTimo Teräshttps://gitlab.alpinelinux.org/alpine/aports/-/issues/8410mod_wsgi crashes with WSGIDaemonProcess option2019-07-12T15:32:14ZA. Klitzingmod_wsgi crashes with WSGIDaemonProcess optionI switch from Debian Jessie to Alpine v3.7 and copied the configuration
of Apache2.
Apache2 crashes after start if there is a WSGIDaemonProcess in
VirtualHost.
I stripped down to this example.
WSGIPassAuthorization On
\#WSGIScriptA...I switch from Debian Jessie to Alpine v3.7 and copied the configuration
of Apache2.
Apache2 crashes after start if there is a WSGIDaemonProcess in
VirtualHost.
I stripped down to this example.
WSGIPassAuthorization On
\#WSGIScriptAlias “/” “/opt/reviewboard/site/htdocs/reviewboard.wsgi/”
\#WSGIDaemonProcess rb
python-path=/opt/reviewboard/dist/lib/python2.7/site-packages
lang=C.UTF-8 locale=C.UTF-8
WSGIDaemonProcess rb lang=C.UTF-8
WSGIProcessGroup rb
Maybe this is an Alpine bug instead of mod\_wsgi.
/var/log/messages:
Jan 24 11:05:59 rb daemon.err /etc/init.d/apache2\[3982\]: status:
crashed
*(from redmine: issue id 8410, created on 2018-01-24)*https://gitlab.alpinelinux.org/alpine/aports/-/issues/8412xpra segfaults if codec is switched to vp9 codec2019-07-12T15:32:15ZMichael Wyrazxpra segfaults if codec is switched to vp9 codecI run xpra with xfce on alpine in docker:
https://github.com/micw/docker-alpine-xpra-xfce4-base
When I connect and switch to codec vp9, xpra segfaults.
According to xpra devs in irc, “vp9 segfaults are usually build issues”.
*(from ...I run xpra with xfce on alpine in docker:
https://github.com/micw/docker-alpine-xpra-xfce4-base
When I connect and switch to codec vp9, xpra segfaults.
According to xpra devs in irc, “vp9 segfaults are usually build issues”.
*(from redmine: issue id 8412, created on 2018-01-25)*https://gitlab.alpinelinux.org/alpine/infra/infra/-/issues/8414Central syslog server2019-07-12T16:28:47ZDaniel Isaksendisaksen@alpinelinux.orgCentral syslog serverWe should, for auditing and security purposes, set up a syslog server to
receive logs from all hosts we manage.
I propose we forward syslog from hosts to syslog-ng, possibly using
logstash and elasticsearch.
*(from redmine: issue id 8...We should, for auditing and security purposes, set up a syslog server to
receive logs from all hosts we manage.
I propose we forward syslog from hosts to syslog-ng, possibly using
logstash and elasticsearch.
*(from redmine: issue id 8414, created on 2018-01-25)*https://gitlab.alpinelinux.org/alpine/infra/infra/-/issues/8421Define mqtt (msg.alpinelinux.org) topic structure2019-07-12T16:28:49ZCarlo LandmeterDefine mqtt (msg.alpinelinux.org) topic structureWe should define a structure to use for our mqtt topics. Currently we
have:
- git/\*
- build/\*
- alert/\*
- rsync/\*
- monitoring/\*
- issues/\*
Are there any good design principles for topic structure?
*(from redmine: i...We should define a structure to use for our mqtt topics. Currently we
have:
- git/\*
- build/\*
- alert/\*
- rsync/\*
- monitoring/\*
- issues/\*
Are there any good design principles for topic structure?
*(from redmine: issue id 8421, created on 2018-01-25)*
* Relations:
* child #8468Carlo LandmeterCarlo Landmeterhttps://gitlab.alpinelinux.org/alpine/aports/-/issues/8422setup-interfaces doesn't work anymore after entering a non-existent wireless ...2019-07-12T15:32:18Zalgitbotsetup-interfaces doesn't work anymore after entering a non-existent wireless network nameSteps to reproduce:
\- Run setup-interfaces, and try to configure wlan0
\- When prompted for the wireless network name, write a non-existent
network name
- Try to run setup-interfaces again
I noticed that if I make a typo and select...Steps to reproduce:
\- Run setup-interfaces, and try to configure wlan0
\- When prompted for the wireless network name, write a non-existent
network name
- Try to run setup-interfaces again
I noticed that if I make a typo and select a non-existent wireless
network, then try to run setup-interfaces again, setup-interfaces will
stop working due to a wpa\_supplicant issue. This is the output:
`Tyoe the wireless network name to connect to: myNetwork
Type the "myNetwork" network Pre-Shared Key: <key goes here, echoed thanks to https://bugs.alpinelinux.org/issues/8068>
Successfully initialized wpa_supplicant
Line 53: invalid key_mgmt 'open'
Line 53: no key_mgmt values configured.
Line 53: failed to parse key_mgmt 'open'
Line 54: failed to parse network block.
Failed to read or parse configuration '/etc/wpa_supplicant/wpa_supplicant.conf'`
After this, setup-interfaces goes on normally. wlan0, of course, doesn’t
work. The only way to fix this is by removing the erroneous
wpa\_supplicant.conf entry:
`...
network={
ssid="typo"
key_mgmt=open
}
...`
I noticed that the wpa\_supplicant.conf also had all the previous
entries generated by running setup-interfaces every time I reboot
(thanks to bug https://bugs.alpinelinux.org/issues/8025). I’m marking
this as high priority, since it’s an obvious usability bug that affects
anyone who might make a typo when selecting the network in
setup-interfaces (which, again, has to be done on every reboot).
*(from redmine: issue id 8422, created on 2018-01-25)*https://gitlab.alpinelinux.org/alpine/infra/infra/-/issues/8429Mirror redirector2019-07-12T16:28:51ZDaniel Isaksendisaksen@alpinelinux.orgMirror redirectorIn order to fully utilize our numerous mirrors, we must create a HTTP
mirror redirector for use in \`apk\`.
I have looked into using GeoDNS for this, but considering mirrors store
alpine on different paths (i.e. /alpinelinux, /alpine-li...In order to fully utilize our numerous mirrors, we must create a HTTP
mirror redirector for use in \`apk\`.
I have looked into using GeoDNS for this, but considering mirrors store
alpine on different paths (i.e. /alpinelinux, /alpine-linux, /alpine)
this is impossible.
I will test mirrorbits for this, and keep this issue updated with
progress.
*(from redmine: issue id 8429, created on 2018-01-27)*Daniel Isaksendisaksen@alpinelinux.orgDaniel Isaksendisaksen@alpinelinux.orghttps://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/infra/-/issues/8454unified solution for infrastructure backups2019-07-12T16:28:57ZCarlo Landmeterunified solution for infrastructure backupsI created a set of scripts to unify the way to backup hosts and
containers inside our infra.
https://github.com/clandmeter/alpine-backup
*(from redmine: issue id 8454, created on 2018-01-30)*I created a set of scripts to unify the way to backup hosts and
containers inside our infra.
https://github.com/clandmeter/alpine-backup
*(from redmine: issue id 8454, created on 2018-01-30)*https://gitlab.alpinelinux.org/alpine/infra/infra/-/issues/8468MQTT authentication2022-11-06T21:22:06ZCarlo LandmeterMQTT authenticationWith the introduction of topic structure and SSL support for MQTT we
should also add ACL+authentication to mosquito.
*(from redmine: issue id 8468, created on 2018-02-02)*
* Relations:
* parent #8421With the introduction of topic structure and SSL support for MQTT we
should also add ACL+authentication to mosquito.
*(from redmine: issue id 8468, created on 2018-02-02)*
* Relations:
* parent #8421Carlo LandmeterCarlo Landmeterhttps://gitlab.alpinelinux.org/alpine/infra/aports-turbo/-/issues/39Improving package search - searching in pkgdesc2020-03-28T15:18:18ZBernhard J. M. GrünImproving package search - searching in pkgdescIt would be a nice improvement to also have a switch to enable searching
in package descriptions (pkgdesc) too on the website
https://pkgs.alpinelinux.org/packages .
*(from redmine: issue id 8489, created on 2018-02-15)*It would be a nice improvement to also have a switch to enable searching
in package descriptions (pkgdesc) too on the website
https://pkgs.alpinelinux.org/packages .
*(from redmine: issue id 8489, created on 2018-02-15)*Carlo LandmeterCarlo Landmeterhttps://gitlab.alpinelinux.org/alpine/aports/-/issues/8620Splash fails, no fb driver available during boot2019-07-12T15:33:44ZalgitbotSplash fails, no fb driver available during bootUsing the **“splash”** boot option does not work, **/dev/fb0** is not
available and it still changes to vt 16 presenting a black screen.
It’s not until the modloop is loaded by the openrc boot-service and
fbcon becomes available that it...Using the **“splash”** boot option does not work, **/dev/fb0** is not
available and it still changes to vt 16 presenting a black screen.
It’s not until the modloop is loaded by the openrc boot-service and
fbcon becomes available that it works(If I relaunch fbsplash). Adding
modules=fbcon does not work, it’s the same result with /etc/modules.
*(from redmine: issue id 8620, created on 2018-03-06)*https://gitlab.alpinelinux.org/alpine/aports/-/issues/8628DHCP requests even when cable disconnected.2019-07-12T15:33:48ZalgitbotDHCP requests even when cable disconnected.While booting, if there is no cable plugged into the ethernet port, it
still sends DHCP requests which are pointless and ass time to the
booting process. -id4rk
*(from redmine: issue id 8628, created on 2018-03-08)*While booting, if there is no cable plugged into the ethernet port, it
still sends DHCP requests which are pointless and ass time to the
booting process. -id4rk
*(from redmine: issue id 8628, created on 2018-03-08)*https://gitlab.alpinelinux.org/alpine/aports/-/issues/8629Alpine VirtualBox Guest Additions doesn't allow for writing to shared folder ...2023-05-02T01:43:51ZalgitbotAlpine VirtualBox Guest Additions doesn't allow for writing to shared folder (guest -> host)Background: I built an Alpine Vagrant box based on
https://github.com/rgl/alpine-vagrant, using the following code in the
customize/run.sh after adding the edge repositories to
/etc/apk/repositories:
apk update
apk add virtualbo...Background: I built an Alpine Vagrant box based on
https://github.com/rgl/alpine-vagrant, using the following code in the
customize/run.sh after adding the edge repositories to
/etc/apk/repositories:
apk update
apk add virtualbox-guest-additions virtualbox-guest-modules-virthardened
echo vboxguest >> /etc/modules
echo vboxsf >> /etc/modules
# Add ${BASE_USER} to the vboxsf group (needed for changing ownership of shared folders)
sed -i -r "s/vboxsf:x:([0-9]+):/vboxsf:x:\1:${BASE_USER}/" /etc/group
As a comparison, I used the official ubuntu/trusty64 Vagrant box to
verify that the host configuration isn’t the source of the issue. Here
are the two Vagrantfiles:
mc@loki:~/lab/ubuntubox$ cat Vagrantfile
Vagrant.configure("2") do |config|
config.vm.box = "ubuntu/trusty64"
config.vm.synced_folder ".", "/host"
end
mc@loki:~/lab/alpinebox$ cat Vagrantfile
Vagrant.configure("2") do |config|
config.vm.box = "alpinebox"
config.vm.synced_folder ".", "/host"
end
First, some verification that the vbox\* modules have been loaded in
each box:
mc@loki:~/lab/ubuntubox$ vagrant ssh -c "dmesg | grep vbox"
[ 4.553067] vboxvideo: module verification failed: signature and/or required key missing - tainting kernel
[ 4.553091] vboxvideo: Unknown symbol drm_open (err 0)
[ 4.553095] vboxvideo: Unknown symbol drm_poll (err 0)
[ 4.553098] vboxvideo: Unknown symbol drm_pci_init (err 0)
[ 4.553104] vboxvideo: Unknown symbol drm_ioctl (err 0)
[ 4.553107] vboxvideo: Unknown symbol drm_mmap (err 0)
[ 4.553110] vboxvideo: Unknown symbol drm_pci_exit (err 0)
[ 4.553112] vboxvideo: Unknown symbol drm_release (err 0)
[ 4.725681] vboxguest: misc device minor 57, IRQ 20, I/O port d020, MMIO at 00000000f0400000 (size 0x400000)
[ 4.725685] vboxguest: Successfully loaded version 4.3.36_Ubuntu (interface 0x00010004)
[ 11.263651] vboxvideo: Unknown symbol drm_open (err 0)
[ 11.263659] vboxvideo: Unknown symbol drm_poll (err 0)
[ 11.263665] vboxvideo: Unknown symbol drm_pci_init (err 0)
[ 11.263672] vboxvideo: Unknown symbol drm_ioctl (err 0)
[ 11.263677] vboxvideo: Unknown symbol drm_mmap (err 0)
[ 11.263681] vboxvideo: Unknown symbol drm_pci_exit (err 0)
[ 11.263686] vboxvideo: Unknown symbol drm_release (err 0)
[ 11.892856] vboxsf: Successfully loaded version 4.3.36_Ubuntu (interface 0x00010004)
Connection to 127.0.0.1 closed.
mc@loki:~/lab/alpinebox$ vagrant ssh -c "dmesg | grep vbox"
[ 5.926766] vboxguest: loading out-of-tree module taints kernel.
[ 5.930999] vboxguest: misc device minor 59, IRQ 20, I/O port d020, MMIO at 00000000f0400000 (size 0x400000)
[ 5.931000] vboxguest: Successfully loaded version 5.1.30 (interface 0x00010004)
[ 9.141127] vboxsf: Successfully loaded version 5.1.30 (interface 0x00010004)
Connection to 127.0.0.1 closed.
According to the VBox documentation, it’s necessary that the guest user
is in the vboxsf group - that doesn’t seem to be needed in the ubuntu
case though:
mc@loki:~/lab/ubuntubox$ vagrant ssh -c "id"
uid=1000(vagrant) gid=1000(vagrant) groups=1000(vagrant)
Connection to 127.0.0.1 closed.
mc@loki:~/lab/alpinebox$ vagrant ssh -c "id"
uid=1000(alpine) gid=1000(alpine) groups=10(wheel),101(docker),102(vboxsf),1000(alpine)
Connection to 127.0.0.1 closed.
On to the actual “write to host from guest” test case:
mc@loki:~/lab/ubuntubox$ vagrant ssh -c "touch /host/hello_from_guest"
Connection to 127.0.0.1 closed.
# No error
mc@loki:~/lab/alpinebox$ vagrant ssh -c "touch /host/hello_from_guest"
touch: /host/hello_from_guest: Permission denied
Connection to 127.0.0.1 closed.
I have tried all options suggested on
https://www.vagrantup.com/docs/synced-folders/basic\_usage.html:
$ for file in Vagrantfile*; do echo -e "\n$file:"; cat $file; done
Vagrantfile.synced_folder:
Vagrant.configure("2") do |config|
config.vm.box = "alpinebox"
config.vm.synced_folder ".", "/host"
end
Vagrantfile.synced_folder_owner_group:
Vagrant.configure("2") do |config|
config.vm.box = "alpinebox"
config.vm.synced_folder ".", "/host", owner: "alpine", group: "alpine"
end
Vagrantfile.synced_folder_owner_group_uid1000gid1000:
Vagrant.configure("2") do |config|
config.vm.box = "alpinebox"
config.vm.synced_folder ".", "/host", owner: "alpine", group: "alpine", mount_options: ["uid=1000", "gid=1000"]
end
Vagrantfile.synced_folder_mount_options_dmode775fmode664:
Vagrant.configure("2") do |config|
config.vm.box = "alpinebox"
config.vm.synced_folder ".", "/host", owner: "alpine", group: "alpine", mount_options: ["dmode=775,fmode=664"]
end
..but without success, i.e., the alpine guest is not able to write to
the folder mounted on the host.
Have I missed something, or is this a bug in the
virtualbox-guest-additions / virtualbox-guest-modules-virthardened
package?
And for clarity:
mc@loki:~/lab/alpinebox$ vagrant ssh -c "cat /etc/alpine-release"
3.7.0
Connection to 127.0.0.1 closed.
*(from redmine: issue id 8629, created on 2018-03-08)*https://gitlab.alpinelinux.org/alpine/aports/-/issues/8742Add mod_md sub package for new apache 2.4.332019-07-12T15:34:41ZAndy PostnikovAdd mod_md sub package for new apache 2.4.33There’s new experimental extension to deal with letsencrypt
https://httpd.apache.org/docs/2.4/mod/mod\_md.html
*(from redmine: issue id 8742, created on 2018-03-27)*There’s new experimental extension to deal with letsencrypt
https://httpd.apache.org/docs/2.4/mod/mod\_md.html
*(from redmine: issue id 8742, created on 2018-03-27)*