infra issueshttps://gitlab.alpinelinux.org/alpine/infra/infra/-/issues2023-06-07T12:16:38Zhttps://gitlab.alpinelinux.org/alpine/infra/infra/-/issues/9924Allow selecting all arches in pkgs.alpinelinux.org2023-06-07T12:16:38ZKevin DaudtAllow selecting all arches in pkgs.alpinelinux.orgThe arch selection field by default has no arch selected, so it allows
you to search in any arch. But once you selected an arch, it’s no longer
possible to select no arch.
*(from redmine: issue id 9924, created on 2019-01-26)*The arch selection field by default has no arch selected, so it allows
you to search in any arch. But once you selected an arch, it’s no longer
possible to select no arch.
*(from redmine: issue id 9924, created on 2019-01-26)*Carlo LandmeterCarlo Landmeterhttps://gitlab.alpinelinux.org/alpine/infra/infra/-/issues/9977Flagging packages is not working, 404 instead.2023-06-07T12:16:38ZYaron ShahrabaniFlagging packages is not working, 404 instead.This is website related.
The packages interface doesn’t allow flagging, an error appears.
*(from redmine: issue id 9977, created on 2019-02-11)*This is website related.
The packages interface doesn’t allow flagging, an error appears.
*(from redmine: issue id 9977, created on 2019-02-11)*https://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/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/8424Make an inventory of the current infrastructure2022-11-06T20:43:46ZKevin DaudtMake an inventory of the current infrastructureBefore the infrastructure can be documented, we need to make an
inventory of what infrastructure is there.
*(from redmine: issue id 8424, created on 2018-01-26)*
* Relations:
* parent #8413Before the infrastructure can be documented, we need to make an
inventory of what infrastructure is there.
*(from redmine: issue id 8424, created on 2018-01-26)*
* Relations:
* parent #8413https://gitlab.alpinelinux.org/alpine/infra/infra/-/issues/8413Document the current infrastructure2022-11-06T20:41:16ZKevin DaudtDocument the current infrastructureVery little is documented about the infrastructure, making it hard for
others to help with the project.
This is a project task to make sure everything gets documented.
*(from redmine: issue id 8413, created on 2018-01-25)*
* Relation...Very little is documented about the infrastructure, making it hard for
others to help with the project.
This is a project task to make sure everything gets documented.
*(from redmine: issue id 8413, created on 2018-01-25)*
* Relations:
* child #8424https://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/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/4760size in bytes of ISOs on http://alpinelinux.org/downloads/2022-04-22T05:48:44ZScrumpy Jacksize in bytes of ISOs on http://alpinelinux.org/downloads/Can we publish the sizes in bytes of ISOs, as well as human readable?
eg:
iso size checksum
alpine-3.2.3-x86_64.iso 299 MB (313602048) sha1 | sha256 | asc
It helps for things like ver...Can we publish the sizes in bytes of ISOs, as well as human readable?
eg:
iso size checksum
alpine-3.2.3-x86_64.iso 299 MB (313602048) sha1 | sha256 | asc
It helps for things like verifying the checksums once the ISO is burned
to optical media
*(from redmine: issue id 4760, created on 2015-10-09)*Carlo LandmeterCarlo Landmeterhttps://gitlab.alpinelinux.org/alpine/infra/infra/-/issues/6377WWW IPv62022-03-28T20:29:55Zmello tronWWW IPv6Hello,
It’d be nice if the public facing web domains had functioning AAAA
records.
*(from redmine: issue id 6377, created on 2016-10-21)*Hello,
It’d be nice if the public facing web domains had functioning AAAA
records.
*(from redmine: issue id 6377, created on 2016-10-21)*Kevin DaudtKevin Daudthttps://gitlab.alpinelinux.org/alpine/infra/infra/-/issues/1846handling security issues2022-01-29T22:46:09ZPeter Kotcauerhandling security issuesIt would be nice to have an errata mailing list to inform users about
fixed security issues affecting binary packages or the core system.
Mails could include the CVE and other identifiers.
There could be place an unique id tag for thes...It would be nice to have an errata mailing list to inform users about
fixed security issues affecting binary packages or the core system.
Mails could include the CVE and other identifiers.
There could be place an unique id tag for these issues something like
ALPLSA-year:autoincrement (ALPine Linux Security Advisory).
I think one or more security officer(s) should be chosen.
There could be a security@ address where users could send security
related problems (it should have a public pgp key for sending sensitive
information encrypted).
Security officer(s) should be subscribed to distros and linux-distros
closed mailing lists.
*(from redmine: issue id 1846, created on 2013-05-03)*
* Relations:
* child #1858https://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)https://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/10406Migrate Alpine mailing lists to lists.sr.ht2020-01-06T14:19:38ZCarlo LandmeterMigrate Alpine mailing lists to lists.sr.htI want to outline the steps needed to migrate our current lists server
to a new server by using the lists software provided by sr.ht.
This is with help from @sircmpwn
The current status can be found here:
http://lists.alpinelinux.org/a...I want to outline the steps needed to migrate our current lists server
to a new server by using the lists software provided by sr.ht.
This is with help from @sircmpwn
The current status can be found here:
http://lists.alpinelinux.org/alpine-infra/0267.html
There is currently a list of items that still need to be done:
x configure & import archives for alpine/announce
x generate redirects for announce
x import subscribers for announce
x training on user invites
- configure & import archives for any sensitive lists
- freshen other lists (now outdated) archives
- generate redirects for remaining lists
- import subscribers for remaining lists
- update DNS to change lists2.a.o -> lists.a.o
- update postfix on smtp.a.o (is that what it's called?)
- update nginx config on listserv (lists2 -> lists, by renaming the file in
/etc/nginx/conf.d and updating the server_name directive therein)
- update /etc/sr.ht/config.ini (lists2 -> lists)
- reload the services (DNS server, postfix, nginx, lists.sr.ht)
[ migration complete, new lists are now live]
- import emails which came in during the migration process, if any
*(from redmine: issue id 10406, created on 2019-05-06)*Carlo LandmeterCarlo Landmeterhttps://gitlab.alpinelinux.org/alpine/infra/infra/-/issues/1858Create mailing list for security alerts2020-01-06T14:19:15ZNatanael CopaCreate mailing list for security alertsWe already have a amiling list named ‘alpine-security’. I wonder if we
should make it more clear what this list is for.
Maybe we should have a sec-errata@lists.alpinelinux.org too, where we
only post security erratas.
*(from redmine: ...We already have a amiling list named ‘alpine-security’. I wonder if we
should make it more clear what this list is for.
Maybe we should have a sec-errata@lists.alpinelinux.org too, where we
only post security erratas.
*(from redmine: issue id 1858, created on 2013-05-13)*
* Relations:
* relates #2104
* parent #1846Carlo LandmeterCarlo Landmeterhttps://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/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/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/9493improve patchwork mail routing2020-01-06T13:05:58ZCarlo Landmeterimprove patchwork mail routingCurrently mails for patchwork are routed via redmine container.
This is not very obvious and can lead into issues when changing
container locations.
It would be better if we have a single point of entry (mail.a.o) and
forward to the ...Currently mails for patchwork are routed via redmine container.
This is not very obvious and can lead into issues when changing
container locations.
It would be better if we have a single point of entry (mail.a.o) and
forward to the correct container directly via vpn.
*(from redmine: issue id 9493, created on 2018-09-30)*Carlo LandmeterCarlo Landmeterhttps://gitlab.alpinelinux.org/alpine/infra/infra/-/issues/10573migration to gitlab2020-01-06T13:02:23ZCarlo Landmetermigration to gitlabwe are currently testing a new gitlab instance at
gitlab.alpinelinux.org.
Please reply with issues found and features which are missing.
This is also a good place to start discussing how to organize git.a.o
and bugs.a.o into gitlab.
...we are currently testing a new gitlab instance at
gitlab.alpinelinux.org.
Please reply with issues found and features which are missing.
This is also a good place to start discussing how to organize git.a.o
and bugs.a.o into gitlab.
If you want a test account please email me or send a message on IRC for
a password as smtp is disabled atm for obvious reasons.
*(from redmine: issue id 10573, created on 2019-06-14)*
* Relations:
* child #10606
* child #10634
* Uploads:
* ![Screenshot_from_2019-06-14_12-03-06](/uploads/154af9d912af126b459e0740e11c7421/Screenshot_from_2019-06-14_12-03-06.png)Carlo LandmeterCarlo Landmeter