Jordan Petridis commented:
ack :thumbsup:
--
Reply to this email directly or view it on GitLab:
https://gitlab.gnome.org/Infrastructure/Infrastructure/-/issues/728#note_1309204
You're receiving this email because of your account on gitlab.gnome.org
Jordan Petridis created an issue:
https://gitlab.gnome.org/Infrastructure/Infrastructure/-/issues/701
I stumbled upon this repo today, https://gitlab.gnome.org/GNOME/gnome-hello
Apart from translations the repo hasn't been touched in ages and it doesn't
seem relevant anymore according
Jordan Petridis commented on a discussion:
https://gitlab.gnome.org/Infrastructure/Infrastructure/-/issues/564#note_1266008
ah hmm, looks like we missed that. Any idea if genius is active and its
planning on porting?
Though there isn't something terribly wrong with depending on an "arc
Jordan Petridis created an issue:
https://gitlab.gnome.org/Infrastructure/Infrastructure/-/issues/589
See https://gitlab.gnome.org/GNOME/librsvg/-/issues/749
We'd like to deploy an instance for librsvg too, assuming sysadmins ack the
request, I can deploy another one on openshift
Jordan Petridis commented:
Can't reproduce even on a clean vm.
--
Reply to this email directly or view it on GitLab:
https://gitlab.gnome.org/Infrastructure/Infrastructure/-/issues/585#note_1126269
You're receiving this email because of your account on gitlab.gnome.org
Jordan Petridis created an issue:
https://gitlab.gnome.org/Infrastructure/Infrastructure/-/issues/568
The reposiroty is currently under
https://gitlab.gnome.org/chergert/gnome-text-editor
This is a candidate for a default/core app in future releases, and it kinda
belongs in the GNOME
Jordan Petridis created an issue:
https://gitlab.gnome.org/Infrastructure/Infrastructure/-/issues/564
Maintainer gave up on the modules, and we are going to port projects that
depend on them.
https://gitlab.gnome.org/GNOME/amtk/-/commit/34a1171298808e5d9bd50540ee194b8be35bce9d
https
Jordan Petridis commented:
Deployment created, looks like its working. You can start using it.
--
Reply to this email directly or view it on GitLab:
https://gitlab.gnome.org/Infrastructure/Infrastructure/-/issues/558#note_1074529
You're receiving this email because of your account
Reassigned Issue 558
https://gitlab.gnome.org/Infrastructure/Infrastructure/-/issues/558
Assignee changed to Jordan Petridis
--
Reply to this email directly or view it on GitLab:
https://gitlab.gnome.org/Infrastructure/Infrastructure/-/issues/558
You're receiving this email because of your
Jordan Petridis commented on a discussion:
https://gitlab.gnome.org/Infrastructure/Infrastructure/-/issues/518#note_1024011
The aarch64 runner is a special unicorn
```
[0KRunning with gitlab-runner 13.2.4 (264446b2)
```
--
Reply to this email directly or view it on GitLab:
https
Jordan Petridis commented:
Everything is working really nicely and its almost mutter is almost ready to
start using thanks to Jonas \o/
https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/1549
I stumbled upon the mesa marge config and though I will drop a link here for
future ref
Jordan Petridis commented:
People report that it started happening again
https://paste.gnome.org/pfjfeompn
```
$ flatpak install org.gnome.Sdk/x86_64/master --reinstall --verbose
--ostree-verbose --user -y
F: Opening user flatpak installation at path /home/ivans/.local/share/flatpak
Issue was reopened by Jordan Petridis
Issue 446: https://gitlab.gnome.org/Infrastructure/Infrastructure/-/issues/446
--
Reply to this email directly or view it on GitLab:
https://gitlab.gnome.org/Infrastructure/Infrastructure/-/issues/446
You're receiving this email because of your account
Reassigned Issue 465
https://gitlab.gnome.org/Infrastructure/Infrastructure/-/issues/465
Assignee changed to Bartłomiej Piotrowski
--
Reply to this email directly or view it on GitLab:
https://gitlab.gnome.org/Infrastructure/Infrastructure/-/issues/465
You're receiving this email because
Jordan Petridis commented:
This looks like to be one of the runners going out of space not the repo itself.
> Runner: gcc179-flatpak (donated by OSU Open Source Lab) (#200)
--
Reply to this email directly or view it on GitLab:
https://gitlab.gnome.org/Infrastructure/Infrastruct
Jordan Petridis commented on a discussion:
https://gitlab.gnome.org/Infrastructure/Infrastructure/-/issues/456#note_933379
Let's move it to Teams/releng for now and give access to the repo to Tobias.
--
Reply to this email directly or view it on GitLab:
https://gitlab.gnome.org
Jordan Petridis created an issue:
https://gitlab.gnome.org/Infrastructure/Infrastructure/-/issues/464
Hi,
Couple days ago we where discussing using a merge-bot to automate various
things in from the workflow of Shell maintainers. The main features the bot
provides is automating the merge
Jordan Petridis created an issue:
https://gitlab.gnome.org/Infrastructure/Infrastructure/-/issues/456
We would like to raise the awareness of the Nightly images in hopes we get more
people testing pre-released gnome. Thus @bertob cooked up a static webpage
with a fancy button to the .iso
Jordan Petridis commented:
installing 3.38 with `--no-static-deltas` bypassed the error
`flatpak install -y org.gnome.Sdk//3.38 --no-static-deltas`
--
Reply to this email directly or view it on GitLab:
https://gitlab.gnome.org/Infrastructure/Infrastructure/-/issues/446#note_924651
You're
Jordan Petridis created an issue:
https://gitlab.gnome.org/Infrastructure/Infrastructure/-/issues/446
Similar to $406 seems
Did a clean install and found the following issues
org.gnome.Sdk//3.38
```
Error: While pulling runtime/org.gnome.Sdk/x86_64/3.38 from remote flathub:
Invalid
Issue was closed by Jordan Petridis
Issue #409: https://gitlab.gnome.org/Infrastructure/Infrastructure/-/issues/409
--
Reply to this email directly or view it on GitLab:
https://gitlab.gnome.org/Infrastructure/Infrastructure/-/issues/409
You're receiving this email because of your account
Jordan Petridis commented:
This was fixed by purging the CAS cache I think
--
Reply to this email directly or view it on GitLab:
https://gitlab.gnome.org/Infrastructure/Infrastructure/-/issues/409#note_907011
You're receiving this email because of your account on gitlab.gnome.org
Jordan Petridis commented on a discussion:
https://gitlab.gnome.org/Infrastructure/Infrastructure/-/issues/407#note_902182
ack, I am not using it.
--
Reply to this email directly or view it on GitLab:
https://gitlab.gnome.org/Infrastructure/Infrastructure/-/issues/407#note_902182
You're
Jordan Petridis created an issue:
https://gitlab.gnome.org/Infrastructure/Infrastructure/-/issues/408
We have merged the following repos to their non-sys counterparts in the same
group. Would be nice to archive them.
https://gitlab.gnome.org/World/Rust/libhandy-sys-rs
https
Jordan Petridis created an issue:
https://gitlab.gnome.org/Infrastructure/Infrastructure/-/issues/391
It has been completely replaced and the infrastructure that was using it
decommissioned. Its not useful for anything anymore.
https://gitlab.gnome.org/GNOME/gnome-apps-nightly
--
Reply
Jordan Petridis commented on a discussion:
https://gitlab.gnome.org/Infrastructure/Infrastructure/-/issues/376#note_882612
Thanks, created a discourse thread.
https://discourse.gnome.org/t/rfc-default-to-main-branch-name-for-new-repos-in-gitlab-gnome-org/3948
--
Reply to this email
Jordan Petridis created an issue:
https://gitlab.gnome.org/Infrastructure/Infrastructure/-/issues/386
The release-team would like to start distributing VMs with each release (at
least .0 releases) so we can showcase things and use it in the PressKit send to
engagement*/news folks
Jordan Petridis commented:
Looking at the repository and the requirements I think there might be a
reasonable solution that doesn't involve us maintaining a custom executor.
Looks like the way they are testing their setup so far is running podman on
host and giving it access to the a big
Jordan Petridis created an issue:
https://gitlab.gnome.org/Infrastructure/Infrastructure/-/issues/376
Since gitlab 13.2 its possible to set the default branch name for new
repositories created through the GUI.
It would be nice to move away from `master` and instead set it to `main
Jordan Petridis commented on a discussion:
https://gitlab.gnome.org/Infrastructure/Infrastructure/-/issues/343#note_859892
There isn't any specific image used, custom images are kinda
encouraged/necessary. Since you want podman you'd probably want something like
`registry.fedoraproject.org
Jordan Petridis created an issue:
https://gitlab.gnome.org/Infrastructure/Infrastructure/-/issues/345
Would be nice to have Nightly http server and the flatmanager status to
status.gnome.org to have the outages documented
--
Reply to this email directly or view it on GitLab:
https
Jordan Petridis commented:
Will there be anything special needed for doing the first release of the
project, or is it going to be like usual module releases?
Also @bilelmoussaoui do you have ftp access for doing releases?
--
Reply to this email directly or view it on GitLab:
https
Jordan Petridis created an issue:
https://gitlab.gnome.org/Infrastructure/Infrastructure/issues/232
Looks like this is a new feature in 12.6 release.
https://docs.gitlab.com/ee/user/group/#disabling-group-mentions
--
Reply to this email directly or view it on GitLab:
https
Jordan Petridis commented on a discussion:
https://gitlab.gnome.org/Infrastructure/Infrastructure/issues/133#note_644257
3.30 was built by buildstream, I believe was the first release to do so. There
was a 3.30beta backup plan built there but never made it online.
--
Reply to this email
Jordan Petridis commented on a discussion:
https://gitlab.gnome.org/Infrastructure/Infrastructure/issues/133#note_517417
>From my point of view there are 2 parts to the nightlies. First one was CI
>testing and making sure that all the flatpaks are buildable, this was really
>valu
Jordan Petridis commented:
> We already build the core apps in gnome-build-meta, and buildstream already
> supports generating flatpaks. Are there any obstacles to using buildstream
> for the flatpaks of the core apps?
Its kinda weird, cause what we will end up publishing will be
Jordan Petridis commented:
> apps should individually setup their CI
I a agree with that, but as I understand it, this proposal is about setting up
the nightly repo so not every app have to do that and the Flathub infra is for
beta/rc software, not for nightlies.
--
Reply to this em
Jordan Petridis commented:
> Is it okay to use a single repo instead of gnome-nightly/gnome-apps-nightly
> split?
yes, flathub is also a single repo, the gnome-nightly repo is fairly old and at
the time it might had made sense to have them split, but that's no longer the
Jordan Petridis commented:
> I don't suppose there is a way I can blacklist that host until this is fixed,
> is there?
While you can't blacklist a runner afaik, you could whitelist all the rest of
them
--
View it on GitLab:
https://gitlab.gnome.org/Infrastructure/Infrastructure/iss
39 matches
Mail list logo
