alpine issueshttps://gitlab.alpinelinux.org/groups/alpine/-/issues2021-07-29T17:34:39Zhttps://gitlab.alpinelinux.org/alpine/aports/-/issues/9860Adding ngx_http_geoip2_module to Nginx (version 1 DBs are no longer available...2021-07-29T17:34:39ZJoão Pedro BoavidaAdding ngx_http_geoip2_module to Nginx (version 1 DBs are no longer available upstream)Hello,
Earlier this year, MaxMind stopped providing the legacy databases (used
by package geoip) and it is no longer possible to use Nginx’s geoip
modules (unless one saved copies of the old databases). However, it
seems ngx\_http\_geoi...Hello,
Earlier this year, MaxMind stopped providing the legacy databases (used
by package geoip) and it is no longer possible to use Nginx’s geoip
modules (unless one saved copies of the old databases). However, it
seems ngx\_http\_geoip2\_module handles version 2, and that very few
changes would be needed to include it in the nginx package.
Would this be a reasonable addition?
I’m not sure it really counts as a bug (it’s more that something was
deprecated upstream), but it would be really nice to have it officially
available, and although I don’t know enough to make an actual pull
request, I tried to gather all the info I could to make it easier to
evaluate.
The module requires libmaxminddb (which is already available) and people
who intend to use the data files can obtain/update them by running
/etc/periodic/weekly/libmaxminddb.
The module itself is https://github.com/leev/ngx\_http\_geoip2\_module,
the author is at Cloudflare, and there are commits by people from Nginx
and MaxMind. The license is the same as Nginx’s. This is also the module
Nginx recommends for its Plus subscribers.
I think geoip and libmaxminddb don’t interact, so adding libmaxminddb
shouldn’t break anything for people who have the legacy data files and
keep using geoip.
As far as I can tell (I have no experience generating packages or
anything like that, so I’m doing some guesswork on how the build process
uses the config files), the changes would be all on
https://git.alpinelinux.org/aports/tree/main/nginx/APKBUILD:
- add libmaxminddb-dev or libmaxminddb (I think the first is what’s
needed for the module compilation) to makedepends
- some \_add\_module entries like this
_add_module "http-geoip2" "3.2" "https://github.com/leev/ngx_http_geoip2_module"
_add_module "stream-geoip2" "3.2" "https://github.com/leev/ngx_http_geoip2_module"
(it is the same repo for both modules, and both .so files need to be
added to the \_extra\_flags list of —add-dynamic-module)
- the sha sum for the modules
84b26955234e29dbfbf2431b652fcc453c5e86b95f837296df4f3d6c730e3e0773223dae890eebfc9b5763f46082bde6f38d6505b8bf78133b89e7297016cc5d nginx-http-geoip2-module-3.2.tar.gz
84b26955234e29dbfbf2431b652fcc453c5e86b95f837296df4f3d6c730e3e0773223dae890eebfc9b5763f46082bde6f38d6505b8bf78133b89e7297016cc5d nginx-stream-geoip2-module-3.2.tar.gz
Again, I’m mostly guessing, and I’ve had no chance to figure the details
of the build process.
Would this be a reasonable update?
Thanks,
João Pedro Boavida
*(from redmine: issue id 9860, created on 2019-01-16)*https://gitlab.alpinelinux.org/alpine/aports/-/issues/9859openssh: add CLI line editing to sftp client2019-07-23T11:16:03ZMilan P. Stanićopenssh: add CLI line editing to sftp clientCLI line editing and tab completion is quite useful in sftp for users
who uses it daily
I posted simple patch to openssh which add dependency to libedit and
—with-libedit configure build option
Patch is here: https://patchwork.alpine...CLI line editing and tab completion is quite useful in sftp for users
who uses it daily
I posted simple patch to openssh which add dependency to libedit and
—with-libedit configure build option
Patch is here: https://patchwork.alpinelinux.org/patch/4414/
*(from redmine: issue id 9859, created on 2019-01-16, closed on 2019-03-16)*https://gitlab.alpinelinux.org/alpine/aports/-/issues/9858Support for plain text NHRP Network ID2019-07-12T15:43:31ZJesse DavisSupport for plain text NHRP Network IDHello,
I’ve successfully configured Alpine-virt (alpine 4.14.89-0-virt) with
the Quagga-nhrpd plugin (Quagga 1.2.4)
Attempting to register with an existing Cisco-based NHRP implementation
fails as the Cisco NHRP Network-id is not a num...Hello,
I’ve successfully configured Alpine-virt (alpine 4.14.89-0-virt) with
the Quagga-nhrpd plugin (Quagga 1.2.4)
Attempting to register with an existing Cisco-based NHRP implementation
fails as the Cisco NHRP Network-id is not a numeric format, instead it
is a plain text value (MMXIII).
It appears the Quagga NHRP implementation support only numeric NHRP
network IDs in the range <1-4294967295>.
Is there any way to patch or work-around this existing feature, in order
to support plain text NHRP network IDs…?
Thanks in advance for any information provided,
Jesse
*(from redmine: issue id 9858, created on 2019-01-15)*Timo TeräsTimo Teräshttps://gitlab.alpinelinux.org/alpine/aports/-/issues/9857[Package Request] php7-igbinary2019-07-23T11:16:04ZMichael Aldridge[Package Request] php7-igbinaryigbinary is needed for certain cache software access protocols. It can
be found on github: https://github.com/igbinary/igbinary/
Tentatively assigned to Valery Kartel to keep all of php7 under the same
maintainer.
*(from redmine: issu...igbinary is needed for certain cache software access protocols. It can
be found on github: https://github.com/igbinary/igbinary/
Tentatively assigned to Valery Kartel to keep all of php7 under the same
maintainer.
*(from redmine: issue id 9857, created on 2019-01-15, closed on 2019-03-27)*Valery KartelValery Kartelhttps://gitlab.alpinelinux.org/alpine/aports/-/issues/9856Enabling CONFIG_CGROUP_BPF in kernel2020-02-20T18:40:05ZMartin RuskoEnabling CONFIG_CGROUP_BPF in kernelHi,
is it possible to enable CONFIG\_CGROUP\_BPF in Alpine’s kernel, please?
It depends on CONFIG\_BPF\_SYSCALL which is also not set as of 3.9\_rc1.
Without these the ‘ip vrf exec’ command fails with following error:
router:~# ip ...Hi,
is it possible to enable CONFIG\_CGROUP\_BPF in Alpine’s kernel, please?
It depends on CONFIG\_BPF\_SYSCALL which is also not set as of 3.9\_rc1.
Without these the ‘ip vrf exec’ command fails with following error:
router:~# ip link add VRF_A type vrf table 200
router:~# ip link set dev VRF_A up
[... assigning some interfaces to vrf here ...]
router:~# ip vrf exec VRF_A ping 1.2.3.4
Failed to load BPF prog: 'Function not implemented'
Kernel compiled with CGROUP_BPF enabled?
router:~#
It would be great if it made it into 3.9 released kernel, if it’s not
too late. Thanks!
*(from redmine: issue id 9856, created on 2019-01-14)*3.12.0https://gitlab.alpinelinux.org/alpine/aports/-/issues/9855Missing dependencies for composer2019-07-14T23:03:51ZKevin DaudtMissing dependencies for composerComposer does not run out-of-the box currently. When installing
composer, it complains about the iconv function missing.
After installing php7-iconv, it returns a lot of errors like:
PHP Notice: iconv(): Wrong charset, conversion f...Composer does not run out-of-the box currently. When installing
composer, it complains about the iconv function missing.
After installing php7-iconv, it returns a lot of errors like:
PHP Notice: iconv(): Wrong charset, conversion from `ASCII' to `UTF-8//IGNORE' is not allowed in ..
This is solved by installing php7-mbstring.
*(from redmine: issue id 9855, created on 2019-01-14)*Natanael CopaNatanael Copahttps://gitlab.alpinelinux.org/alpine/aports/-/issues/9853lxdm does not restart, scritp are broken2023-02-07T15:07:40ZPICCORO Lenz McKAYlxdm does not restart, scritp are brokenthe lxdm package have buggy and uncomplete implementation..
if try to stop, does not property grab the status of proc:
<code class="text">
root@alpine:~/alpineinstalls/recetas$ rc-service lxdm restart
* Stopping lxdm ...
...the lxdm package have buggy and uncomplete implementation..
if try to stop, does not property grab the status of proc:
<code class="text">
root@alpine:~/alpineinstalls/recetas$ rc-service lxdm restart
* Stopping lxdm ...
* start-stop-daemon: 1 process refused to stop
* Failed to stop lxdm [ !! ]
* ERROR: lxdm failed to stop
root@alpine:~/alpineinstalls/recetas$ rc-service lxdm stop
* Stopping lxdm ...
* start-stop-daemon: 1 process refused to stop
* Failed to stop lxdm [ !! ]
* ERROR: lxdm failed to stop
</code>
as a suggestion must track all the recent patches in sf git lxde
repository and winbuntu patches to resolve it
*(from redmine: issue id 9853, created on 2019-01-13)*Ariadne Conillariadne@ariadne.spaceAriadne Conillariadne@ariadne.spacehttps://gitlab.alpinelinux.org/alpine/aports/-/issues/9851Package request: libde2652019-07-23T11:16:06ZNatanael CopaPackage request: libde265https://github.com/strukturag/libde265
Needed by imagemagick for HEIC support
*(from redmine: issue id 9851, created on 2019-01-10, closed on 2019-06-19)*
* Relations:
* parent #9555
* Changesets:
* Revision 075593cfef8e4df6056ea...https://github.com/strukturag/libde265
Needed by imagemagick for HEIC support
*(from redmine: issue id 9851, created on 2019-01-10, closed on 2019-06-19)*
* Relations:
* parent #9555
* Changesets:
* Revision 075593cfef8e4df6056ea7de388137a68335ea69 by Natanael Copa on 2019-06-17T12:27:21Z:
```
main/libde265: move from testing
needed by imagemagick
fixes #9851
```3.10.0https://gitlab.alpinelinux.org/alpine/aports/-/issues/9838package request : add several Microchip microcontrollers tools2021-07-29T17:06:11ZHugo Amorospackage request : add several Microchip microcontrollers toolspicprog http://hyvatti.fi/~jaakko/pic/picprog.html PIC16, PIC12 and
PIC18 microcontroller programmer for Linux and Windows/Cygwin.
gputils https://gputils.sourceforge.io GPUTILS is a collection of tools
for the Microchip ™ PIC microcon...picprog http://hyvatti.fi/~jaakko/pic/picprog.html PIC16, PIC12 and
PIC18 microcontroller programmer for Linux and Windows/Cygwin.
gputils https://gputils.sourceforge.io GPUTILS is a collection of tools
for the Microchip ™ PIC microcontrollers.
gpsim http://gpsim.sourceforge.net gpsim is a full-featured software
simulator for Microchip PIC microcontrollers.
sdcc http://sdcc.sourceforge.net SDCC is a retargettable, optimizing
Standard C (ANSI C89, ISO C99, ISO C11) compiler suite
*(from redmine: issue id 9838, created on 2019-01-09)*https://gitlab.alpinelinux.org/alpine/aports/-/issues/9837libjpeg-turbo has a different license than the original one's in Alpine world...2019-07-23T11:16:21ZDaisuke Miyakawalibjpeg-turbo has a different license than the original one's in Alpine world (GPL v.s. non-GPL, rather BSD-like)Package info shows GPL
https://pkgs.alpinelinux.org/package/edge/main/x86\_64/libjpeg-turbo
While the original license seems BSD-like, while a bit complicated.
https://github.com/libjpeg-turbo/libjpeg-turbo/blob/master/LICENSE.md
I...Package info shows GPL
https://pkgs.alpinelinux.org/package/edge/main/x86\_64/libjpeg-turbo
While the original license seems BSD-like, while a bit complicated.
https://github.com/libjpeg-turbo/libjpeg-turbo/blob/master/LICENSE.md
I’m not sure why GPL is selected in Alpine and got interested.
*(from redmine: issue id 9837, created on 2019-01-09, closed on 2019-03-05)*
* Changesets:
* Revision f47923b5f7d199694385595ec9c649290c423155 by Natanael Copa on 2019-01-09T09:49:46Z:
```
main/libjpeg-turbo: fix license information
ref #9837
```
* Revision ea571248622765c7b51ba6f6bc16497edff71dd4 by Natanael Copa on 2019-01-09T09:53:12Z:
```
main/libjpeg-turbo: fix license information
fixes #9837
(cherry picked from commit f47923b5f7d199694385595ec9c649290c423155)
```3.8.3https://gitlab.alpinelinux.org/alpine/aports/-/issues/9835[3.7] py-django: Content spoofing via URL path in default 404 page (CVE-2019-...2020-01-18T00:12:52ZAlicha CH[3.7] py-django: Content spoofing via URL path in default 404 page (CVE-2019-3498)Django before versions 1.11.18, 2.0.10 and 2.1.5 is vulnerable to
content spoofing via crafted URL in the default 404 page.
An attacker could craft a malicious URL that could make spoofed content
appear on the default page generated
...Django before versions 1.11.18, 2.0.10 and 2.1.5 is vulnerable to
content spoofing via crafted URL in the default 404 page.
An attacker could craft a malicious URL that could make spoofed content
appear on the default page generated
by the django.views.defaults.page\_not\_found() view.
### Fixed In Version:
python-django 1.11.18, python-django 2.0.10, python-django 2.1.5
### References:
https://www.djangoproject.com/weblog/2019/jan/04/security-releases/
### Patch:
https://github.com/django/django/commit/1cd00fcf52d089ef0fe03beabd05d59df8ea052a
*(from redmine: issue id 9835, created on 2019-01-09, closed on 2019-02-19)*
* Relations:
* parent #9832
* Changesets:
* Revision efea0b2841657c90aec0a76835d84fbc2ed2cfb9 on 2019-02-04T11:27:46Z:
```
main/py-django: security upgrade to 1.11.18 (CVE-2019-3498)
Fixes #9835
```3.7.2Natanael CopaNatanael Copahttps://gitlab.alpinelinux.org/alpine/aports/-/issues/9831[Package request] ProxySQL2021-01-09T17:24:06ZKévin Guignard[Package request] ProxySQLProxySQL is a high-performance MySQL/MariaDB proxy with a GPL license.
https://github.com/sysown/proxysql
*(from redmine: issue id 9831, created on 2019-01-08)*ProxySQL is a high-performance MySQL/MariaDB proxy with a GPL license.
https://github.com/sysown/proxysql
*(from redmine: issue id 9831, created on 2019-01-08)*https://gitlab.alpinelinux.org/alpine/aports/-/issues/9830wget is broken2019-07-23T11:16:28ZRep Hwget is broken$ wget https://alpinelinux.org/
Connecting to alpinelinux.org (147.75.101.119:443)
ssl\_client: alpinelinux.org: TLS connect failed
*(from redmine: issue id 9830, created on 2019-01-06, closed on 2019-05-04)*
* Changesets:
* Rev...$ wget https://alpinelinux.org/
Connecting to alpinelinux.org (147.75.101.119:443)
ssl\_client: alpinelinux.org: TLS connect failed
*(from redmine: issue id 9830, created on 2019-01-06, closed on 2019-05-04)*
* Changesets:
* Revision a374181d8547ed5bc42a2ce8f90de95a332ea68f on 2019-01-06T14:20:48Z:
```
main/libtls-standalone: depend on ca-certificates-cacert
Openssl does not ship a bundled cert by default which libressl did.
ca-certificates-cacert provides all mozilla certificates in favour of
installing ca-certificates completely.
fixes #9830
```https://gitlab.alpinelinux.org/alpine/aports/-/issues/9829apache2-proxy requires slotmem_shm_module to start2019-07-23T11:16:29ZPaul Gauretapache2-proxy requires slotmem_shm_module to startOn a fresh edge install, after adding apache2-proxy Apache fails to
start with the following in the error.log
\[Fri Jan 04 17:29:41.833353 2019\] \[lbmethod\_heartbeat:notice\] \[pid
374\] AH02281: Failed to lookup provider ‘shm’ for ‘s...On a fresh edge install, after adding apache2-proxy Apache fails to
start with the following in the error.log
\[Fri Jan 04 17:29:41.833353 2019\] \[lbmethod\_heartbeat:notice\] \[pid
374\] AH02281: Failed to lookup provider ‘shm’ for ‘slotmem’. Maybe you
need to load mod\_slotmem\_shm?
\[Fri Jan 04 17:29:41.835355 2019\] \[mpm\_prefork:notice\] \[pid 374\]
AH00163: Apache/2.4.37 (Unix) OpenSSL/1.1.1a configured — resuming
normal operations
This can be fixed either by:
\- Commenting the proxy\_balancer\_module entry in ldap.conf, or
- Loading mod\_slotmem\_shm in ldap.conf
*(from redmine: issue id 9829, created on 2019-01-04, closed on 2019-05-04)*
* Changesets:
* Revision aa1a70d7d2f26ebf2ed0a4efa2e7cd82853d4420 by Kaarle Ritvanen on 2019-02-01T17:01:05Z:
```
main/apache2: fix mod_proxy default configuration
fixes #9829
```
* Revision f2000237b1b40697ed9119528e29faf41646bb39 by Kaarle Ritvanen on 2019-02-01T17:04:37Z:
```
main/apache2: fix mod_proxy default configuration
fixes #9829
```https://gitlab.alpinelinux.org/alpine/aports/-/issues/9828Suggest packaging acme.sh for Lets Encrypt2019-07-23T11:16:30ZPaul GauretSuggest packaging acme.sh for Lets EncryptRationale :
\- Alpine has a number of acme clients already packaged.
\- However certbot has many dependencies (incl. python2) and acme-client
is based on unmaintained code (
https://github.com/kristapsdz/acme-client-portable ).
\- Bot...Rationale :
\- Alpine has a number of acme clients already packaged.
\- However certbot has many dependencies (incl. python2) and acme-client
is based on unmaintained code (
https://github.com/kristapsdz/acme-client-portable ).
\- Both dehydrated ( https://github.com/lukas2511/dehydrated ) and
acme.sh ( https://github.com/Neilpang/acme.sh ) could be good candidates
for Alpine, but dehydrated depends on bash.
- acme.sh is well tested on Alpine by its developer (even provides an
Alpine based Docker image)
I’m still too new to Alpine to do this myself, but packaging should be
easy, only requires the acme.sh script itself and the optional ‘dnsapi’
scripts. Depends on openssl and curl.
*(from redmine: issue id 9828, created on 2019-01-04, closed on 2019-05-03)*
* Changesets:
* Revision 3422802dfe8e0eb140d61c7cdc4e7c4184c7d7b9 by Francesco Colista on 2019-01-08T08:29:44Z:
```
testing/acme.sh: new aport. Fixes #9828
```https://gitlab.alpinelinux.org/alpine/aports/-/issues/9827virt alpine kernel with no pl2303 module2020-01-18T00:12:52ZChris Schuvirt alpine kernel with no pl2303 moduleHi !
i have installed apline linux on an virtualbox and i use the virtual
alpine kernel !
but with this kernel i have not the Pl2303 serial usb module ! with the
vanilla kernel ist works out of the box !
Prolific PL2303 USB - Serial a...Hi !
i have installed apline linux on an virtualbox and i use the virtual
alpine kernel !
but with this kernel i have not the Pl2303 serial usb module ! with the
vanilla kernel ist works out of the box !
Prolific PL2303 USB - Serial adapter
/lib/modules/\`uname -r\`/kernel/drivers/usb/serial/pl2303.ko
How can i use the module and compile the kernel for the virt kernel
->i cannot understand the wiki ->the howto build costum kernel !
Thanks !
kind regards
*(from redmine: issue id 9827, created on 2019-01-04, closed on 2019-01-07)*https://gitlab.alpinelinux.org/alpine/aports/-/issues/9826Can't boot linux-vanilla on armhf2019-08-12T20:17:49ZPaul GauretCan't boot linux-vanilla on armhfI can’t boot the Alpine linux kernel on my armhf boards (tested on
Cubieboard and OrangePI Plus with similar results).
Sample u-boot session below, messages stop after “Starting kernel” and
board requires a hard reset:
----------------...I can’t boot the Alpine linux kernel on my armhf boards (tested on
Cubieboard and OrangePI Plus with similar results).
Sample u-boot session below, messages stop after “Starting kernel” and
board requires a hard reset:
------------------------------------------------------------------------
=>setenv bootargs earlyprintk console=ttyS0,115200
root=/dev/mmcblk0p2 rw rootwait
=>env set fdt\_high ffffffff
=>fatload mmc 0 0x46000000 vmlinuz-vanilla
3834368 bytes read in 310 ms (11.8 MiB/s)
=>fatload mmc 0 0x49000000
linux-4.19.13-0-vanilla-sun4i-a10-cubieboard.dtb
22448 bytes read in 4 ms (5.4 MiB/s)
=>bootz 0x46000000 - 0x49000000
\#\# Flattened Device Tree blob at 49000000
Booting using the fdt blob at 0x49000000
Using Device Tree in place at 49000000, end 490087af
Starting kernel …
------------------------------------------------------------------------
Building from the same kernel version with a default configuration
(multi\_v7\_defconfig) generates a working kernel.
------------------------------------------------------------------------
make ARCH=arm CROSS\_COMPILE=arm-linux-gnueabihf- multi\_v7\_defconfig
make <s>j 5 ARCH=arm CROSS\_COMPILE=arm-linux-gnueabihf</s>
LOADADDR=0x40008000 zImage dtbs
make <s>j 5 ARCH=arm CROSS\_COMPILE=arm-linux-gnueabihf</s> modules
make <s>j 5 ARCH=arm CROSS\_COMPILE=arm-linux-gnueabihf</s>
INSTALL\_MOD\_PATH=output modules\_install
------------------------------------------------------------------------
*(from redmine: issue id 9826, created on 2019-01-03)*https://gitlab.alpinelinux.org/alpine/aports/-/issues/9825The cargo binary reports wrong version in edge2020-01-18T00:12:52ZBatbold DashzevegThe cargo binary reports wrong version in edge$ apk add cargo rust
Installing rust (1.31.1-r1)
Installing cargo (1.31.1-r1)
$ cargo -V
cargo 1.31.0 \# should print 1.31.1
$ rustc -V
rustc 1.31.1
$ cargo build
Segmentation fault
*(from redmine: issue id 9825, created o...$ apk add cargo rust
Installing rust (1.31.1-r1)
Installing cargo (1.31.1-r1)
$ cargo -V
cargo 1.31.0 \# should print 1.31.1
$ rustc -V
rustc 1.31.1
$ cargo build
Segmentation fault
*(from redmine: issue id 9825, created on 2019-01-02, closed on 2019-06-19)*3.10.0https://gitlab.alpinelinux.org/alpine/aports/-/issues/9821Upgrading to Edge fails miserably on alpine-virt builds2019-07-23T11:16:36ZJohn DoeUpgrading to Edge fails miserably on alpine-virt buildsIf you start with a base install of an alpine-virt\* build, subsequently
following the instructions at https://wiki.alpinelinux.org/wiki/Edge
bricks your install
Leaves it in an ubootable state:
error: premature end of file /boot/vmli...If you start with a base install of an alpine-virt\* build, subsequently
following the instructions at https://wiki.alpinelinux.org/wiki/Edge
bricks your install
Leaves it in an ubootable state:
error: premature end of file /boot/vmlinuz-virt
error: you need to load the kernel first
Press any key to continue
*(from redmine: issue id 9821, created on 2019-01-01, closed on 2019-06-19)*3.10.0https://gitlab.alpinelinux.org/alpine/aports/-/issues/9815Firefox: tidy-up for Alpine 3.9 release2020-01-18T00:12:52ZRep HFirefox: tidy-up for Alpine 3.9 releaseHello folks.
I have a few comments on Firefox state on Alpine and suggestions for
tidying up.
First, package firefox-esr (52.9.0 on Alpine) lives in community but
firefox (62.0.3 on Alpine) lives in testing.
Well, firefox should be ...Hello folks.
I have a few comments on Firefox state on Alpine and suggestions for
tidying up.
First, package firefox-esr (52.9.0 on Alpine) lives in community but
firefox (62.0.3 on Alpine) lives in testing.
Well, firefox should be in community too. The packages are very similar
besides the rust/cargo dependency and both have been shown to work.
When you go to firefox.com, the default is Alpine’s @testing version.
OK, second point.
For Alpine release 3.9 it would be great if those packages could be
upgraded.
firefox-esr is already on version 60 upstream and firefox is on version
64.
firefox-esr needs to stay low because rust on Alpine is x64 only for
now.
I think the latest firefox that didn’t need rust was firefox 53.
firefox on the other hand can be upgraded all the way to version 64.
That’s it…
Just an idea to get firefox in shape to the 3.9 release.
Even more important now then ever.
*(from redmine: issue id 9815, created on 2018-12-31, closed on 2019-01-10)*3.9.0