infra issueshttps://gitlab.alpinelinux.org/alpine/infra/infra/-/issues2019-07-18T21:16:49Zhttps://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/10593Publicise list of aports without a maintainer2023-06-07T13:27:34ZTBKPublicise list of aports without a maintainerWe currently have quite a few aports without a maintainer spread across
all branches.
One possible solution to reduce the number is to bring the issue to the
community’s attention.
An automated solution weekly/bi-weekly listing the apo...We currently have quite a few aports without a maintainer spread across
all branches.
One possible solution to reduce the number is to bring the issue to the
community’s attention.
An automated solution weekly/bi-weekly listing the aports (without a
maintainer) seeking a new home.
The list could be pushed to the website, IRC and ML for maximum
exposure.
*(from redmine: issue id 10593, created on 2019-06-20)*https://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/10484lxc-based builders seem not to have lxcfs enabled2020-04-19T13:31:02ZChloe Kudryavtsevlxc-based builders seem not to have lxcfs enabledUnder lxc, side-effects can happen when resources are limited.
As an example, see
https://build.alpinelinux.org/buildlogs/build-edge-x86/community/caddy/caddy-1.0.0-r0.log
This is caused by the container not knowing what it’s actuall...Under lxc, side-effects can happen when resources are limited.
As an example, see
https://build.alpinelinux.org/buildlogs/build-edge-x86/community/caddy/caddy-1.0.0-r0.log
This is caused by the container not knowing what it’s actually allowed
to use, and thus not having a value (in this case, defaulting to –1).
This can and will cause various failures.
*(from redmine: issue id 10484, created on 2019-05-23)*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/10223Verify / update firewall rules ipv62020-09-15T17:12:14ZKevin DaudtVerify / update firewall rules ipv6At the moment we mostly concentrated on IPv4 rules. Although awall by
default also includes ipv6 rules, we still need to verify them to see if
the rules are working properly.
*(from redmine: issue id 10223, created on 2019-04-09)*At the moment we mostly concentrated on IPv4 rules. Although awall by
default also includes ipv6 rules, we still need to verify them to see if
the rules are working properly.
*(from redmine: issue id 10223, created on 2019-04-09)*Kevin DaudtKevin Daudthttps://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/9912Writeable install images2022-07-24T02:05:31ZRichard MortierWriteable install imagesI was recently installing a set of machines, and used the provided .ISO
images on a USB stick to do so.
That worked fine, but it would’ve been nice if I could’ve customised the
image after the first install as it would’ve made each sub...I was recently installing a set of machines, and used the provided .ISO
images on a USB stick to do so.
That worked fine, but it would’ve been nice if I could’ve customised the
image after the first install as it would’ve made each subsequent
install a bit quicker.
I couldn’t do this because the ISO filesystem is read-only.
Would it be possible to provide (eg) an EXT2 or VFAT or something image
file that could be downloaded, burnt to a USB stick, and then modified
after first boot please?
*(from redmine: issue id 9912, created on 2019-01-25)*https://gitlab.alpinelinux.org/alpine/infra/infra/-/issues/9899add ntp servers for alpine2022-11-09T12:51:56ZNatanael Copaadd ntp servers for alpinewe should not use pool.ntp.org for our default ntp config, instead we
should set up our own ntp servers.
https://www.pool.ntp.org/vendors.html#vendor-zone
https://www.pool.ntp.org/vendors.html#open-source
*(from redmine: issue id 98...we should not use pool.ntp.org for our default ntp config, instead we
should set up our own ntp servers.
https://www.pool.ntp.org/vendors.html#vendor-zone
https://www.pool.ntp.org/vendors.html#open-source
*(from redmine: issue id 9899, created on 2019-01-23)*https://gitlab.alpinelinux.org/alpine/infra/infra/-/issues/9698FWD: CERT/CC needs Alpine email address & contact information for vulnerabil...2020-04-14T21:01:23ZNatanael CopaFWD: CERT/CC needs Alpine email address & contact information for vulnerability reports————— Forwarded message ————-
From: Laurie A Tyzenhaus <latyzenhaus@cert.org>
Date: qua, 21 de nov de 2018 às 18:16
Subject: CERT/CC needs Alpine email address & contact information for
vulnerability reports
Daniel Sabogal; Al...————— Forwarded message ————-
From: Laurie A Tyzenhaus <latyzenhaus@cert.org>
Date: qua, 21 de nov de 2018 às 18:16
Subject: CERT/CC needs Alpine email address & contact information for
vulnerability reports
Daniel Sabogal; Alicha CH;
CERT Coordination Center is updating their contact list and finds that
the
email address we have, alpine@bugs.alpinelinux.org, is not valid.
Please take a few minutes to reply to this email with an email address
that
the Alpine Linux security team will be reviewing. A current contact
email
address is vital to alerting vendors to the latest vulnerabilities CERT
is
researching and reporting.
Best Regards,
CERT Coordination Center
*(from redmine: issue id 9698, created on 2018-11-27)*https://gitlab.alpinelinux.org/alpine/infra/infra/-/issues/9650Implement detailed monitoring of container hosts2019-07-12T16:31:09ZKevin DaudtImplement detailed monitoring of container hostsMonitoring so far has only be done from the outside, checking that
websites and other services were available.
Now the need has risen to get monitoring of things like used disk space
as well (some hosts almost run out of disk space). Fo...Monitoring so far has only be done from the outside, checking that
websites and other services were available.
Now the need has risen to get monitoring of things like used disk space
as well (some hosts almost run out of disk space). For that to be
possible we need some kind of agent installed on the host. For Zabbix,
we have 2 options:
- SNMP
- Zabbix agent
So we need to choose what method we are going to use. One consideration
we need to take into account is security, especially for the builder
hosts.
*(from redmine: issue id 9650, created on 2018-11-16)*Kevin DaudtKevin Daudthttps://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)*