aports issueshttps://gitlab.alpinelinux.org/alpine/aports/-/issues2019-07-12T15:32:18Zhttps://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/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/6804Please don't add 3rd-party compiling arguments for binary nginx server2021-07-27T14:18:03ZWei CuiPlease don't add 3rd-party compiling arguments for binary nginx serveralpine &lt;= 3.4 don’t have this issue.
For alpine = 3.5, when running ‘nginx -V’, output contains
‘—add-dynamic-module=/home/buildozer/aports/main/nginx/src/ngx\_devel\_kit-0.3.0
—add-dynamic-module=/home/buildozer/aports/main/nginx/sr...alpine <= 3.4 don’t have this issue.
For alpine = 3.5, when running ‘nginx -V’, output contains
‘—add-dynamic-module=/home/buildozer/aports/main/nginx/src/ngx\_devel\_kit-0.3.0
—add-dynamic-module=/home/buildozer/aports/main/nginx/src/echo-nginx-module-0.60
—add-dynamic-module=/home/buildozer/aports/main/nginx/src/ngx-fancyindex-0.4.1
—add-dynamic-module=/home/buildozer/aports/main/nginx/src/headers-more-nginx-module-0.31
—add-dynamic-module=/home/buildozer/aports/main/nginx/src/lua-nginx-module-0.10.6
—add-dynamic-module=/home/buildozer/aports/main/nginx/src/nchan-1.0.4
—add-dynamic-module=/home/buildozer/aports/main/nginx/src/nginx-upload-progress-module-0.9.2
—add-dynamic-module=/home/buildozer/aports/main/nginx/src/nginx-rtmp-module-1.1.10’
This really bugs nginx module developers because these additional
arguments will prevent nginx in alpine-3.5 package to load other dynamic
module for compatibility protection.
Removing above arguments wouldn’t fail to build modules from alpine
repository such as nginx-upload-progress-module-0.9.2,
nginx-rtmp-module-1.1.10, .. So it is safe to remove them.
If ‘nginx -V’ no longer contains any ‘—add-dynamic-module’, this issue
will be regarded as fixed.
*(from redmine: issue id 6804, created on 2017-02-02)*Jakub JirutkaJakub Jirutka