infra issueshttps://gitlab.alpinelinux.org/alpine/infra/infra/-/issues2022-03-28T20:29:55Zhttps://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/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/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/10634Migration steps from Redmine to Gitlab2019-07-18T21:16:49ZCarlo LandmeterMigration steps from Redmine to GitlabSetup alpine-docker-gitlab
==========================
Docker
------
1. Clone: https://github.com/clandmeter/alpine-docker-gitlab
2. Use a docker-compose file like https://tpaste.us/Bo7b
3. Generate secrets by exec contrib/secrets.sh...Setup alpine-docker-gitlab
==========================
Docker
------
1. Clone: https://github.com/clandmeter/alpine-docker-gitlab
2. Use a docker-compose file like https://tpaste.us/Bo7b
3. Generate secrets by exec contrib/secrets.sh
4. Start docker containers with docker-compose up (keep it in the
foreground to see if something goes wrong)
5. See console for root password or look it up in the secrets files
6. modify unicorn.rb and set process to threads+1
7. restart docker-compose but in the background
Gitlab
------
1. Login to gitlab as root
2. Create alpine Group
3. Create aports project
4. Set group/project writable for users
5. Add a SSH key to the root user (we need it to push aports)
6. Create an API for the root user for migration
7. git push aports with mirror option
Redmine
-------
1. Create api key for admin users on redmine
Migration
---------
### Installation of migrator
1. clone https://github.com/johan-smits/redmine-gitlab-migrator
2. Follow readme to install python application
### Users
1. Generate a users.txt file from the script on mysql db server
(`ssh root`alpine-db.nld3.alpin.pw sh /root/get-redmine-users.sh@)
2. migrate all bugs users to gitlab
- Script https://tpaste.us/baLW
- this makes all of them admins
### Milestones
1. Use migrator from
https://github.com/johan-smits/redmine-gitlab-migrator
2. migrate-rg roadmap —no-verify \\
—redmine-key “$redmine\_api\_key” \\
—gitlab-key “$gitlab\_api\_key” \\
“$redmine\_uri” “$gitlab\_uri”
### Issues
1. Use migrator from
https://github.com/johan-smits/redmine-gitlab-migrator
2. migrate-rg issues —debug —no-verify —keep-id \\
—redmine-key $redmine\_api\_key \\
—gitlab-key $gitlab\_api\_key \\
$redmine\_uri $gitlab\_uri
3. debug is to make it output something when its pre processing
Cleanup
-------
1. Reset all admin privs by setting admin=false in db for all users
except admin
Configuration
-------------
1. TODO
*(from redmine: issue id 10634, created on 2019-06-28)*
* Relations:
* parent #10573Carlo LandmeterCarlo Landmeterhttps://gitlab.alpinelinux.org/alpine/infra/infra/-/issues/10628mirrors.alpinelinux.org: missing v3.9 and v3.10 status2019-07-12T16:32:54ZAleksey Mmirrors.alpinelinux.org: missing v3.9 and v3.10 statusI already sent pull request for v3.9 almost 3 weeks ago, but looks like
it went unnoticed.
Updated it to include v3.10 today. Hope I’m using right place to report
this time.
See https://github.com/alpinelinux/alpine-mirror-status/pul...I already sent pull request for v3.9 almost 3 weeks ago, but looks like
it went unnoticed.
Updated it to include v3.10 today. Hope I’m using right place to report
this time.
See https://github.com/alpinelinux/alpine-mirror-status/pull/1 for
proposed patch.
*(from redmine: issue id 10628, created on 2019-06-28, closed on 2019-06-28)*https://gitlab.alpinelinux.org/alpine/infra/infra/-/issues/10606Redmine and git project/repo conversion/migration to Gitlab2019-07-18T21:17:09ZCarlo LandmeterRedmine and git project/repo conversion/migration to Gitlabwe currently have a specific setup on both Redmine and git.a.o.
### Redmine projects
- AConf
- Alpine Linux
- Alpine Build tools (abuild)
- Alpine Documentation
- Alpine Infrastructure
- Alpine Package Keepe...we currently have a specific setup on both Redmine and git.a.o.
### Redmine projects
- AConf
- Alpine Linux
- Alpine Build tools (abuild)
- Alpine Documentation
- Alpine Infrastructure
- Alpine Package Keeper (apk-tools)
- Alpine Security
- Alpine Setup Scripts
- AWall
- Squark
### git.a.o repos
- Alpine Projects
- repos
- Docks
- repos
- ACF
- repos
- Hosted
- repos
- user
- user repos
### Namespace conversion for projects with source code (git repo):
- projects/alpine =>alpine/aports
- projects/abuild =>alpine/abuild
- projects/apk-tools =>alpine/apk-tools
- projects/alpine-conf =>alpine/alpine-conf
- projects/awall =>alpine/awall
### Namespace conversion for projects without source code (git repo)
These would have a single README.md explaining these projects have
issues only
- projects/alpine-infra =>alpine/infra/general
- projects/alpinedoc =>alpine/docs/general
- projects/alpine-security =>alpine/security/general
### Docs (git repos)
These have no projects on redmine and can be converted to similar Gitlab
namespacing:
- alpine/docs/repository
### Hosted (git repos)
Need to check under which namespace to move these
### ACF
There are a lot of repos on git.a.o and we have mixed the issues within
the alpine (aports) namespace.
We have to discus with Ted Trask how to handle this.
### AConf
I think we can skip migrating Aconf, this project seems empty on
redmine.
### Squark
This seems like an old project. Probably easier to just keep it on
git.a.o
### User repos
We can allow users to migrate their repositories into gitlab or just
keep them on git.a.o.
*(from redmine: issue id 10606, created on 2019-06-23)*
* Relations:
* parent #10573Carlo 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 Landmeterhttps://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/10033Cannot watch issue in bug tracker2019-07-12T16:31:48ZalgitbotCannot watch issue in bug trackerWhen I tried to watch an issue in this bug tracker, I’ve got
https://bugs.alpinelinux.org/watchers/watch?object\_id=8665&object\_type=issue
\`\`\`
Page not found
The page you were trying to access doesn’t exist or has been removed.
...When I tried to watch an issue in this bug tracker, I’ve got
https://bugs.alpinelinux.org/watchers/watch?object\_id=8665&object\_type=issue
\`\`\`
Page not found
The page you were trying to access doesn’t exist or has been removed.
Back
\`\`\`
Issue in question: https://bugs.alpinelinux.org/issues/8665
I’m don’t know if I should report it here bug don’t know where else.
*(from redmine: issue id 10033, created on 2019-02-25, closed on 2019-05-25)*https://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/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/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/9247Improve mirror monitoring2019-07-12T16:30:26ZKevin DaudtImprove mirror monitoringCurrently mirror monitoring only includes checking if the mirror is
alive. Improve monitoring so that we can see if a mirror behind for a
long period.
*(from redmine: issue id 9247, created on 2018-08-16, closed on 2018-09-30)*Currently mirror monitoring only includes checking if the mirror is
alive. Improve monitoring so that we can see if a mirror behind for a
long period.
*(from redmine: issue id 9247, created on 2018-08-16, closed on 2018-09-30)*Kevin DaudtKevin Daudthttps://gitlab.alpinelinux.org/alpine/infra/infra/-/issues/9198images/ missing from boot.a.o2019-07-12T16:30:21ZGhost Userimages/ missing from boot.a.oThe links in the “Image” section are leading into 404’s, it worked
previously.
*(from redmine: issue id 9198, created on 2018-08-07, closed on 2018-08-20)*The links in the “Image” section are leading into 404’s, it worked
previously.
*(from redmine: issue id 9198, created on 2018-08-07, closed on 2018-08-20)*Carlo LandmeterCarlo Landmeterhttps://gitlab.alpinelinux.org/alpine/infra/infra/-/issues/9194Problems with dl-cdn.alpinelinux.org: redirect to https via Squid (results in...2019-07-12T16:30:20ZDaniel HahlerProblems with dl-cdn.alpinelinux.org: redirect to https via Squid (results in 404)1. I have noticed that “curl -I
http://dl-cdn.alpinelinux.org/alpine/v3.8/main/x86\_64/APKINDEX.tar.g
z” redirects to
“https://dl-cdn.alpinelinux.org/alpine/v3.8/main/x86\_64/APKINDEX.tar.gz”,
but only when using a local Squid http cac...1. I have noticed that “curl -I
http://dl-cdn.alpinelinux.org/alpine/v3.8/main/x86\_64/APKINDEX.tar.g
z” redirects to
“https://dl-cdn.alpinelinux.org/alpine/v3.8/main/x86\_64/APKINDEX.tar.gz”,
but only when using a local Squid http cache!
The redirection target results in a 404 then.
2. When trying to access https://dl-cdn.alpinelinux.org in general, you
will get a certificate error:
% curl
https://dl-cdn.alpinelinux.org/alpine/v3.8/main/x86\_64/APKINDEX.tar.gz
curl: (51) SSL: no alternative certificate subject name matches target
host name ‘dl-cdn.alpinelinux.org’
3. On https://wiki.alpinelinux.org/wiki/Alpine\_Linux:Mirrors there is a
link to http://rsync.alpinelinux.org/alpine/MIRRORS.txt, which appears
to redirect to https://dl-cdn.alpinelinux.org/alpine/MIRRORS.txt (404).
The most puzzling part is 1. though - it appears to really be related to
using Squid, even with
“forwarded\_for transparent” and “via off”.
I’ve tried to look at what happens with
https://github.com/yinqiwen/gsnova between dl-cdn and Squid to some
mixed avail - I think without “forwarded\_for transparent” and “via off”
it would still redirect, but with those options enabled (to hide that
Squid is used) it worked better (it does not redirect to https/404), but
resulted in i/o timeout, e.g. “apk update” fails:
fetch
http://dl-cdn.alpinelinux.org/alpine/v3.8/main/x86\_64/APKINDEX.tar.gz
ERROR: http://dl-cdn.alpinelinux.org/alpine/v3.8/main: BAD signature
I’ve used the following to use gsnova as parent proxy:
cache\_peer 127.0.0.1 parent 23128 0 no-query no-digest
never\_direct allow all
*(from redmine: issue id 9194, created on 2018-08-06, closed on 2018-08-07)*https://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)*