infra issueshttps://gitlab.alpinelinux.org/alpine/infra/infra/-/issues2019-07-12T16:30:19Zhttps://gitlab.alpinelinux.org/alpine/infra/infra/-/issues/9192pkgs.ao: dependencies listed multiple times2019-07-12T16:30:19ZAlexander Edlandpkgs.ao: dependencies listed multiple timeswhen a package foo links with N libraries from another package bar, bar
is listed N times in the dependency list.
example: https://pkgs.alpinelinux.org/package/edge/testing/x86\_64/mgba
*(from redmine: issue id 9192, created on 2018-0...when a package foo links with N libraries from another package bar, bar
is listed N times in the dependency list.
example: https://pkgs.alpinelinux.org/package/edge/testing/x86\_64/mgba
*(from redmine: issue id 9192, created on 2018-08-06, closed on 2018-08-20)*https://gitlab.alpinelinux.org/alpine/infra/infra/-/issues/9148'LATEST DEVELOPMENT' does not update on Alpine Linux frontpage2019-07-12T16:30:14Zalgitbot'LATEST DEVELOPMENT' does not update on Alpine Linux frontpageThe section ‘LATEST DEVELOPMENT’ on the Alpine Linux frontpage is not in
sync with https://git.alpinelinux.org/cgit/aports/log
*(from redmine: issue id 9148, created on 2018-07-29, closed on 2018-09-10)*The section ‘LATEST DEVELOPMENT’ on the Alpine Linux frontpage is not in
sync with https://git.alpinelinux.org/cgit/aports/log
*(from redmine: issue id 9148, created on 2018-07-29, closed on 2018-09-10)*https://gitlab.alpinelinux.org/alpine/infra/infra/-/issues/9134Improve the contributors/developers environment2020-01-06T13:09:55ZCarlo LandmeterImprove the contributors/developers environmentThis issue is not specifically targeted at a single item in our infra
but more general discussion thread to eventually evolve into sub tasks
to get a better environment.
Please add your issues and/or possible solutions and ill update t...This issue is not specifically targeted at a single item in our infra
but more general discussion thread to eventually evolve into sub tasks
to get a better environment.
Please add your issues and/or possible solutions and ill update this
item.
Current issues
==============
Authentication
--------------
Currently Redmine does not support proper Oauth integration. It would be
nice if we could have that implemented.
We currently have an issue open \#9081 to disable anon bug reporting.
Issues per branch
-----------------
Would be nice if we could somehow track security issues per branch see:
https://www.redmine.org/issues/1266\#change-56683
Multi Arch CI
-------------
Currently we use an external service (travis) to verify our
contributions. The limitations is that this is only available for
x86\_84.
It would be nice if we could somehow have a CI which can push jobs to
different containers in our infra on different architectures.
Most of our developers do not have access to these Archs so It would be
nice for them to send jobs to verify their contributions.
Patch queue management
----------------------
We currently have 2 queues, GitHub and Patchwork. This is by far optimal
and should be reduced to a single queue where people can contribute
to.
This will be much easier to maintain and less people will complain one
of the queues is better managed and remove questions as to which they
should contribute to.
To my knowledge the reason people use patchwork/ml is that they don’t
like to have an account on Github for privacy reasons. I think we should
support
this request and provided them with an alternative solution which means
we would have to replace both of them with a locally hosted solution.
Ideas regarding solutions
=========================
Unified solution
----------------
I’ve looked into the Open Source world to see if there is a holy grail
to work around the above mentioned issues.
After reviewing I ended up with only two solutions that seem to pack the
feature set we currently need is very active and had proper
documentation.
Both projects also have a side project which can migrate issues from
Redmine which is kind of nice to have.
### GitLab
This currently seems to be a choice for many other open source projects,
but its very hard to maintain it locally.
I started packaging the individual parts (gitlab-ce, gitaly…) but it was
very messy and i ended up with huge packages. I’ve seen Jirutka has
tried to
package it up for Gentoo but in the end stopped working on it. So in the
end I gave up because it seems to be very messy and time consuming.
### Phabricator
This application seems to be very easy to install, has only a few
dependencies so its a matter of an hour to get up and running.
Also the upgrade path is very simple and will be very easy to maintain
(if I read the documentation correctly).
The main issue we faced up till now is the workflow and the actual patch
integration in Phabricator. The only way to retrieve the patches
is to fetch the diff via the web interface or via the PHP cli. There is
no way to grab an mbox file or branch and locally apply and push it
(like we do with github).
This is one of the main issues ncopa faced when trying it out. I didn’t
look closer if this can be overcome somehow.
There is a test instance available at https://phabtest.alpinelinux.org
(the database isn’t running local so its maybe a bit slow at times).
Separate solutions
------------------
I didn’t have time yet to look into possible other solutions so any
feedback is appreciated.
*(from redmine: issue id 9134, created on 2018-07-25)*Carlo LandmeterCarlo Landmeterhttps://gitlab.alpinelinux.org/alpine/infra/infra/-/issues/9081Disable anonymous bug reporting2019-07-12T16:30:04ZCarlo LandmeterDisable anonymous bug reportingI would like to disable anonymous bug reporting.
Its currently difficult if not impossible to contact the bug author.
Also, registering would make bug reports more serious.
Example: https://bugs.alpinelinux.org/issues/9080
*(from ...I would like to disable anonymous bug reporting.
Its currently difficult if not impossible to contact the bug author.
Also, registering would make bug reports more serious.
Example: https://bugs.alpinelinux.org/issues/9080
*(from redmine: issue id 9081, created on 2018-07-13, closed on 2018-08-20)*
* Relations:
* relates #2https://gitlab.alpinelinux.org/alpine/infra/infra/-/issues/9076Remove flag button from non-edge packages on pkgs.alpinelinux.org2022-07-25T10:55:13ZSascha PaunovicRemove flag button from non-edge packages on pkgs.alpinelinux.orgSince one cannot flag packages that aren’t in the edge repos, having the
flag button doesn’t make sense there doesn’t make sense.
*(from redmine: issue id 9076, created on 2018-07-11)*Since one cannot flag packages that aren’t in the edge repos, having the
flag button doesn’t make sense there doesn’t make sense.
*(from redmine: issue id 9076, created on 2018-07-11)*https://gitlab.alpinelinux.org/alpine/infra/infra/-/issues/9072pkgs.alpinelinux.org displays old forums link2019-07-12T16:30:02ZTBKpkgs.alpinelinux.org displays old forums linkIn the top right corner the link for the old forum is still displayed
(See attached image).
The link was removed with this commit in May
https://github.com/alpinelinux/aports-turbo/commit/bd77ac84b5c780408799155804f6c519e9c0ee12
I have...In the top right corner the link for the old forum is still displayed
(See attached image).
The link was removed with this commit in May
https://github.com/alpinelinux/aports-turbo/commit/bd77ac84b5c780408799155804f6c519e9c0ee12
I have checked the page on two devices with different connections to
make sure it not displayed becaused of some old cache on my end.
*(from redmine: issue id 9072, created on 2018-07-11, closed on 2018-09-30)*
* Uploads:
* ![2018-07-11_03-09-24](/uploads/7c25835ab1f6c00a6b3cd58acae35cad/2018-07-11_03-09-24.png)https://gitlab.alpinelinux.org/alpine/infra/infra/-/issues/9071Outdated copyright notice2020-01-06T13:10:33ZTBKOutdated copyright noticeOn https://alpinelinux.org/ and https://pkgs.alpinelinux.org/packages
the footer copyright notice says 2017.
See attached file.
*(from redmine: issue id 9071, created on 2018-07-11)*
* Uploads:
* ![2018-07-11_03-02-09](/uploads/c79...On https://alpinelinux.org/ and https://pkgs.alpinelinux.org/packages
the footer copyright notice says 2017.
See attached file.
*(from redmine: issue id 9071, created on 2018-07-11)*
* Uploads:
* ![2018-07-11_03-02-09](/uploads/c79b02d159f5ab696d19f1efe5447669/2018-07-11_03-02-09.png)Carlo LandmeterCarlo Landmeterhttps://gitlab.alpinelinux.org/alpine/infra/infra/-/issues/9064[SECURITY] Password based auth is available on git.alpinelinux.org2019-07-12T16:30:01ZDave Hall[SECURITY] Password based auth is available on git.alpinelinux.orgAfter the gentoo breach I have been looking at how the various distros I
use secure their infrastructure. I know you use github as a mirror of
git.alpinelinux.org and that the build servers don’t use github.
I decided to check if git.al...After the gentoo breach I have been looking at how the various distros I
use secure their infrastructure. I know you use github as a mirror of
git.alpinelinux.org and that the build servers don’t use github.
I decided to check if git.alpinelinux.org allows any authentication
method other than keys. It turns out it allows password based auth:
\`\`\`
$ ssh -v clandmeter@git.alpinelinux.org
+OpenSSH\_7.6p1, LibreSSL 2.6.2
\[…\]
debug1: Authentications that can continue:
publickey,password,keyboard-interactive
\`\`\`
I know that tools such as fail2ban can be used to prevent brute force
attacks. At the same time it doesn’t sit well with me having password
auth enabled for public facing SSH.
Sorry if this is the wrong place for this ticket. Someone told me it was
the best place to raise it.
*(from redmine: issue id 9064, created on 2018-07-07, closed on 2018-08-20)*Carlo LandmeterCarlo Landmeterhttps://gitlab.alpinelinux.org/alpine/infra/infra/-/issues/9055Add an index.tab and index.json to the download site2021-11-12T15:08:51ZNick SchonningAdd an index.tab and index.json to the download siteSorry I’m just not looking in the right place. I checked out
http://dl-cdn.alpinelinux.org/alpine/ but couldn’t find anything like
what nodejs has for being able to easily pull relase version info. EX:
\- https://nodejs.org/dist/index.j...Sorry I’m just not looking in the right place. I checked out
http://dl-cdn.alpinelinux.org/alpine/ but couldn’t find anything like
what nodejs has for being able to easily pull relase version info. EX:
\- https://nodejs.org/dist/index.json
- https://nodejs.org/dist/index.tab
This appears to be done by a tool they wrote here
https://github.com/nodejs/nodejs-dist-indexer
The reason I’m looking for a file like this is to automate bumping
images as they are released
*(from redmine: issue id 9055, created on 2018-07-05)*Natanael CopaNatanael Copahttps://gitlab.alpinelinux.org/alpine/infra/infra/-/issues/8631Registration with Redmine fails on mobile devices2019-07-12T16:29:16ZKevin DaudtRegistration with Redmine fails on mobile devicesWhen trying to register a new account on mobile devices (IOS and
Android), users get an error: ‘Login is invalid’.
*(from redmine: issue id 8631, created on 2018-03-08, closed on 2019-04-14)*When trying to register a new account on mobile devices (IOS and
Android), users get an error: ‘Login is invalid’.
*(from redmine: issue id 8631, created on 2018-03-08, closed on 2019-04-14)*Kevin DaudtKevin Daudthttps://gitlab.alpinelinux.org/alpine/infra/infra/-/issues/8475add SSL/TLS support to Alpine MQTT infrastructure2022-10-06T21:00:48ZCarlo Landmeteradd SSL/TLS support to Alpine MQTT infrastructureWe are currently only supporting plain text MQTT and MQTT+Websockets on
msg.alpinelinux.org.
This should be extended with MQTT over SSL/TLS and Websockets over
SSL/TLS.
To migrate all infra to SSL/TLS mqtt-exec will need to be updated...We are currently only supporting plain text MQTT and MQTT+Websockets on
msg.alpinelinux.org.
This should be extended with MQTT over SSL/TLS and Websockets over
SSL/TLS.
To migrate all infra to SSL/TLS mqtt-exec will need to be updated with
SSL/TLS support.
See: https://github.com/ncopa/mqtt-exec/issues/4
*(from redmine: issue id 8475, created on 2018-02-05)*Carlo LandmeterCarlo Landmeterhttps://gitlab.alpinelinux.org/alpine/infra/infra/-/issues/8467Announce new issues on #alpine-devel2019-07-12T16:28:58ZCarlo LandmeterAnnounce new issues on #alpine-develAnnounce on both irc and matrix channel.
*(from redmine: issue id 8467, created on 2018-02-01, closed on 2018-03-13)*Announce on both irc and matrix channel.
*(from redmine: issue id 8467, created on 2018-02-01, closed on 2018-03-13)*Carlo LandmeterCarlo Landmeterhttps://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/8453Make patchwork use postgres instead of mysql2022-11-06T20:44:09ZDaniel Isaksendisaksen@alpinelinux.orgMake patchwork use postgres instead of mysqlWe should investigate the possibility of moving patchwork’s database to
postgres running on uk.a.o instead of using mysql.
Said postgresql server is running at intranet IP ending with `5.2`. You
can access it with `sudo lxc-attach -n po...We should investigate the possibility of moving patchwork’s database to
postgres running on uk.a.o instead of using mysql.
Said postgresql server is running at intranet IP ending with `5.2`. You
can access it with `sudo lxc-attach -n postgres` from uk.a.o.
*(from redmine: issue id 8453, created on 2018-01-30)*
* Relations:
* parent #8452Daniel Isaksendisaksen@alpinelinux.orgDaniel Isaksendisaksen@alpinelinux.orghttps://gitlab.alpinelinux.org/alpine/infra/infra/-/issues/8452Upgrade patchwork2019-07-17T13:57:02ZDaniel Isaksendisaksen@alpinelinux.orgUpgrade patchworkWe are currently running on patchwork 1.1.0 from early 2016, and we
should upgrade to 2.0.1\[1\].
Considering our patchwork server is running patchwork from aports\[2\],
we should be fine upgrading the package itself.
\[1\]: https://gi...We are currently running on patchwork 1.1.0 from early 2016, and we
should upgrade to 2.0.1\[1\].
Considering our patchwork server is running patchwork from aports\[2\],
we should be fine upgrading the package itself.
\[1\]: https://github.com/getpatchwork/patchwork/releases
\[2\]: https://pkgs.alpinelinux.org/package/edge/main/x86\_64/patchwork
*(from redmine: issue id 8452, created on 2018-01-30)*
* Relations:
* child #8453Daniel Isaksendisaksen@alpinelinux.orgDaniel Isaksendisaksen@alpinelinux.orghttps://gitlab.alpinelinux.org/alpine/infra/infra/-/issues/8451DNS for our intranet2020-01-06T13:11:16ZDaniel Isaksendisaksen@alpinelinux.orgDNS for our intranetIt would be nice to have a DNS server (+ forwarder?) on our intranet to
resolve names for hosts, such as wiki.intra.a.o.
I will set up a test on uk.a.o for this, using dnsmasq.
*(from redmine: issue id 8451, created on 2018-01-30)*It would be nice to have a DNS server (+ forwarder?) on our intranet to
resolve names for hosts, such as wiki.intra.a.o.
I will set up a test on uk.a.o for this, using dnsmasq.
*(from redmine: issue id 8451, created on 2018-01-30)*Carlo LandmeterCarlo Landmeterhttps://gitlab.alpinelinux.org/alpine/infra/infra/-/issues/8446Upgrade redmine to latest version2019-07-12T16:28:54ZCarlo LandmeterUpgrade redmine to latest versionWe are currently running an older version of redmine which is still
based on apk based installation.
The idea is to upgrade redmine by:
1. Install in new container (test already available)
2. Upgrade the current test install
3. chec...We are currently running an older version of redmine which is still
based on apk based installation.
The idea is to upgrade redmine by:
1. Install in new container (test already available)
2. Upgrade the current test install
3. check if current ruby deps are in aports (hint imagemagick)
4. install services currently running on redmine container
1. smtp server (postfix)
2. mqtt-exec to update local git repos for redmine
5. change dhcp server to use dhcp static ip assignment for new redmine.
6. update nginx proxy (and check config) to use new redmine
7. all that is forgotten
*(from redmine: issue id 8446, created on 2018-01-29, closed on 2018-03-13)*Kevin DaudtKevin Daudt2018-03-06https://gitlab.alpinelinux.org/alpine/infra/infra/-/issues/8428Make all third party mirrors sync from T1 mirrors2022-12-03T21:42:56ZDaniel Isaksendisaksen@alpinelinux.orgMake all third party mirrors sync from T1 mirrorsAll third party mirrors **must** synchronize from our tier 1 (dl-N)
mirrors, and **not** from master.
Therefore we must contact the admins for all third party mirrors and
notify them of this.
A list of contacts are in the git.a.o:infra...All third party mirrors **must** synchronize from our tier 1 (dl-N)
mirrors, and **not** from master.
Therefore we must contact the admins for all third party mirrors and
notify them of this.
A list of contacts are in the git.a.o:infra/mirrors repository.
*(from redmine: issue id 8428, created on 2018-01-26)*
* Relations:
* parent #8426https://gitlab.alpinelinux.org/alpine/infra/infra/-/issues/8427Make sure all dl-N mirrors have 1 Gbps+2019-07-12T16:28:51ZDaniel Isaksendisaksen@alpinelinux.orgMake sure all dl-N mirrors have 1 Gbps+In order for tiered mirrors to be feasible, all our dl-N.alpinelinux.org
mirrors **must** mirror the entire master mirror, **and** must have a
network bandwidth of 1 Gbps or more.
All third party mirrors will synchronize from our tier 1...In order for tiered mirrors to be feasible, all our dl-N.alpinelinux.org
mirrors **must** mirror the entire master mirror, **and** must have a
network bandwidth of 1 Gbps or more.
All third party mirrors will synchronize from our tier 1 mirrors (master
->T1 ->T2/3rd party)
*(from redmine: issue id 8427, created on 2018-01-26, closed on 2019-06-19)*
* Relations:
* parent #8426Carlo LandmeterCarlo Landmeterhttps://gitlab.alpinelinux.org/alpine/infra/infra/-/issues/8426Tiered mirrors2021-11-13T15:25:57ZDaniel Isaksendisaksen@alpinelinux.orgTiered mirrors*Alpine Linux has only one master server, using way more bandwidth than it should. We should therefore implement tiered mirrors.*
-----------------------------------------------------------------------------------------------------------...*Alpine Linux has only one master server, using way more bandwidth than it should. We should therefore implement tiered mirrors.*
---------------------------------------------------------------------------------------------------------------------------------
This means **only** our own mirrors will synchronize from
master.alpinelinux.org, and that third-party mirrors in turn will
synchronize from them.
Tiers will be something like this:
**“Tier 0” / master**
- master.alpinelinux.org
**Tier 1**
- dl-N.alpinelinux.org
**Tier 2**
- 3rd party mirrors
*(from redmine: issue id 8426, created on 2018-01-26)*
* Relations:
* child #8427
* child #8428
* Uploads:
* [infra.pdf](/uploads/2122b28f729a8bc47d0599b6ea0593da/infra.pdf)