Michael Catanzaro commented:
Please, wait for https://gitlab.gnome.org/Teams/Circle/-/issues/98 to be
resolved first. I see there a couple issues to be resolved first.
--
Reply to this email directly or view it on GitLab:
https://gitlab.gnome.org/Infrastructure/Infrastructure/-/issues/735
Issue was closed by Michael Catanzaro
Issue #735: https://gitlab.gnome.org/Infrastructure/Infrastructure/-/issues/735
--
Reply to this email directly or view it on GitLab:
https://gitlab.gnome.org/Infrastructure/Infrastructure/-/issues/735
You're receiving this email because of your account
Reassigned Issue 735
https://gitlab.gnome.org/Infrastructure/Infrastructure/-/issues/735
Assignee changed from Michael Catanzaro to Unassigned
--
Reply to this email directly or view it on GitLab:
https://gitlab.gnome.org/Infrastructure/Infrastructure/-/issues/735
You're receiving
Michael Catanzaro commented:
What on Earth is happening here...?
Ole, the chances of getting new software into GNOME/ is pretty low unless it is
going to be part of GNOME core. This looks like a useful extra app, and Circle
is the right place for those. Is there some reason you don't feel
Michael Catanzaro commented:
Out of curiosity, how does this project compare to Shortwave?
--
Reply to this email directly or view it on GitLab:
https://gitlab.gnome.org/Infrastructure/Infrastructure/-/issues/731#note_1316104
You're receiving this email because of your account
Michael Catanzaro commented:
He Ole, I suggest you apply for Circle, see: https://circle.gnome.org/.
Historically the GNOME/ namespace allowed pretty much anything, but I'm not
sure that's the case anymore, and your app seems like a perfect fit for Circle.
--
Reply to this email directly
Reassigned Issue 731
https://gitlab.gnome.org/Infrastructure/Infrastructure/-/issues/731
Assignee changed from Michael Catanzaro to Unassigned
--
Reply to this email directly or view it on GitLab:
https://gitlab.gnome.org/Infrastructure/Infrastructure/-/issues/731
You're receiving
Michael Catanzaro commented:
Ack. Christopher was the last maintainer for this app.
--
Reply to this email directly or view it on GitLab:
https://gitlab.gnome.org/Infrastructure/Infrastructure/-/issues/730#note_1313382
You're receiving this email because of your account on gitlab.gnome.org
Michael Catanzaro commented:
OK Sebastien... good luck, hope you are able to find something else that you
enjoy. And thanks for letting us know that you're safe!
--
Reply to this email directly or view it on GitLab:
https://gitlab.gnome.org/Infrastructure/Infrastructure/-/issues/700
Michael Catanzaro commented:
One more thing: if you just wanted to move gspell from gitlab.gnome.org to
github.com, of course that would be sad, but that seems reasonable because you
developed gspell yourself and it doesn't have any other maintainers. We don't
allow core elements (like
Michael Catanzaro commented:
ack
--
Reply to this email directly or view it on GitLab:
https://gitlab.gnome.org/Infrastructure/Infrastructure/-/issues/701#note_1279253
You're receiving this email because of your account on gitlab.gnome.org
Michael Catanzaro commented:
> Michael, what about Enchant, it is also developed on GitHub, outside the
> gnome.org infrastructure, or the GNU libc, or the Linux kernel? Which GNOME
> all depends on.
I don't see how it's relevant? I'm not aware of any request to archiv
Michael Catanzaro commented:
> From my perspective, it's fine to archive the copy of gspell in GNOME's
> GitLab.
FWIW I do not agree. We have several active projects depending on gspell:
```
elements/core/evince.bst:- core-deps/gspell.bst
elements/core/gedit.bst:- core-deps/gspe
Michael Catanzaro commented on a discussion:
https://gitlab.gnome.org/Infrastructure/Infrastructure/-/issues/677#note_1266305
If the maintainer wants to keep the repo open in anticipation of potential
future changes, how about we move it to World and remove it from l10n? The main
goal here
Michael Catanzaro commented:
Probably safe to archive it.
--
Reply to this email directly or view it on GitLab:
https://gitlab.gnome.org/Infrastructure/Infrastructure/-/issues/671#note_1266302
You're receiving this email because of your account on gitlab.gnome.org
Michael Catanzaro commented:
Looks like it's some set of nautilus extensions that we don't use? We can
probably archive it. Let's check with @antoniof since he'd be more likely to
know exactly what this is.
--
Reply to this email directly or view it on GitLab:
https://gitlab.gnome.org
Michael Catanzaro commented:
Well we have about two more months before fedora:latest breaks. If we don't
have a new docker release by then, then we will have a real problem. (In the
meantime, I think it's OK to tell people not to use f35 or rawhide.)
--
Reply to this email directly
Michael Catanzaro created an issue:
https://gitlab.gnome.org/Infrastructure/Infrastructure/-/issues/667
In https://gitlab.gnome.org/GNOME/gnome-desktop/-/merge_requests/119 we see the
following CI failure:
```
Error: Error downloading packages:
Curl error (6): Couldn't resolve host name
Michael Catanzaro commented:
Any updates on this?
--
Reply to this email directly or view it on GitLab:
https://gitlab.gnome.org/Infrastructure/Infrastructure/-/issues/98#note_1257759
You're receiving this email because of your account on gitlab.gnome.org
Michael Catanzaro commented:
Andrea says: I should have removed the spam filters at
https://mail.gnome.org/mailman/admin/security-list/privacy/spam which were
configured to hold mails rather than reject them. Sigh
--
Reply to this email directly or view it on GitLab:
https
Michael Catanzaro commented:
Final steps:
* I unsubscribed Andre, Tobi, and SUSE, so no more subscribers.
* I changed the list admin to be nore...@gnome.org, because Mailman is buggy
and asks us to approve spam mails despite the rule to automatically reject all
mails.
--
Reply
Michael Catanzaro commented:
Well it's dying in a slightly different place, but clearly ftpadmin is still
broken, and it's still the `self._init_doap()` that's failing, so I'll reopen
this.
--
Reply to this email directly or view it on GitLab:
https://gitlab.gnome.org/Infrastructure
Issue was reopened by Michael Catanzaro
Issue 638: https://gitlab.gnome.org/Infrastructure/Infrastructure/-/issues/638
--
Reply to this email directly or view it on GitLab:
https://gitlab.gnome.org/Infrastructure/Infrastructure/-/issues/638
You're receiving this email because of your account
Michael Catanzaro commented:
I set up an autoresponder for security-l...@gnome.org, and configured the list
to reject all mails.
@av briefly deleted secur...@gnome.org, but we decided to bring it back,
pointing to security-l...@gnome.org, so that it will benefit from our
autoresponder. I
Issue was closed by Michael Catanzaro
Issue #645: https://gitlab.gnome.org/Infrastructure/Infrastructure/-/issues/645
--
Reply to this email directly or view it on GitLab:
https://gitlab.gnome.org/Infrastructure/Infrastructure/-/issues/645
You're receiving this email because of your account
Michael Catanzaro commented:
@ebassi and myself have been given temporary control over this list. Current
members are:
* @aklapper
* @tobiasmue
* secur...@suse.de
Nobody else has been receiving the mails for an unknown amount of time
(approximately nine months is my guess).
I
Michael Catanzaro created an issue:
https://gitlab.gnome.org/Infrastructure/Infrastructure/-/issues/645
Hi, it seems the secur...@gnome.org mailing list is still operational. This is
a significant oversight because nobody from GNOME Security has been monitoring
this list since release-t
Michael Catanzaro commented:
@jbrummer finally got a CI run scheduled on a Canonical runner again, and
unfortunately it's still broken:
https://gitlab.gnome.org/jbrummer/epiphany/-/jobs/1445946
@jjardon has requested that we define a special tag for the Canonical runners
for now, so
Issue was reopened by Michael Catanzaro
Issue 644: https://gitlab.gnome.org/Infrastructure/Infrastructure/-/issues/644
--
Reply to this email directly or view it on GitLab:
https://gitlab.gnome.org/Infrastructure/Infrastructure/-/issues/644
You're receiving this email because of your account
Issue was closed by Michael Catanzaro
Issue #644: https://gitlab.gnome.org/Infrastructure/Infrastructure/-/issues/644
--
Reply to this email directly or view it on GitLab:
https://gitlab.gnome.org/Infrastructure/Infrastructure/-/issues/644
You're receiving this email because of your account
Michael Catanzaro commented:
Still not sure as my test jobs all got scheduled on OSU runners. Will reopen if
I see this again.
--
Reply to this email directly or view it on GitLab:
https://gitlab.gnome.org/Infrastructure/Infrastructure/-/issues/644#note_1245123
You're receiving this email
Michael Catanzaro commented:
> please let us know whether the SIGKILL is still there.
I'm not sure. Unfortunately every job I schedule now gets picked up by an OSU
runner for some reason. Bad luck.
--
Reply to this email directly or view it on GitLab:
https://gitlab.gnome.
Michael Catanzaro created an issue:
https://gitlab.gnome.org/Infrastructure/Infrastructure/-/issues/644
Hi, recently Epiphany CI has started crashing with SIGILL, e.g. as in
https://gitlab.gnome.org/GNOME/epiphany/-/merge_requests/994#note_1244310, but
only when run on Canonical's CI
Michael Catanzaro commented:
Suffice to say that it's processing the HTML of the 404 page and complaining
that it's not XML, instead of the doap file that it expects to be seeing.
--
Reply to this email directly or view it on GitLab:
https://gitlab.gnome.org/Infrastructure/Infrastructure
Michael Catanzaro commented:
Problem is ftpadmin depends on https://gitlab.gnome.org/repositories.doap which
has somehow become a 404 page, presumably after a recent GitLab update?
--
Reply to this email directly or view it on GitLab:
https://gitlab.gnome.org/Infrastructure/Infrastructure
Michael Catanzaro created an issue:
https://gitlab.gnome.org/Infrastructure/Infrastructure/-/issues/638
Looks like ftpadmin is able to successfully install releases, but then dies
when trying to send announcement mails:
```
$ ftpadmin install glib-networking-2.68.2.tar.xz
Gathering
Michael Catanzaro commented:
Unfortunately I agree that without an error message, it's a Google bug and
there's nothing we can do here. _Maybe_ there is something with our ICS file
that Google Calendar doesn't like, but we would need an error message to figure
out what
--
Reply
Michael Catanzaro commented:
ack
--
Reply to this email directly or view it on GitLab:
https://gitlab.gnome.org/Infrastructure/Infrastructure/-/issues/605#note_1188348
You're receiving this email because of your account on gitlab.gnome.org
Michael Catanzaro commented:
tbh I'm not sure why we've gotten into a situation where NetworkManager itself
is hosted on freedesktop.org but all its plugins are hosted by GNOME. Seems
confusing for things to be split in two separate places. But this *does* seem
to be the right place
Michael Catanzaro commented:
> Sure, I'll handle the wiki.
Note to future self: be careful before volunteering for wiki maintenance,
because you have to move and redirect every subpage manually
--
Reply to this email directly or view it on GitLab:
https://gitlab.gnome.
Michael Catanzaro commented:
> should https://wiki.gnome.org/Apps/Empathy be moved to Attic as well?
Sure, I'll handle the wiki.
And I'll hope that @xclaesse was not about to say "wait I am about to push a
bunch of commits reviving Empathy!" Anyway, that seems unlikely, so i
Michael Catanzaro created an issue:
https://gitlab.gnome.org/Infrastructure/Infrastructure/-/issues/584
Hi, I think it's time to archive https://gitlab.gnome.org/GNOME/empathy since
development has clearly ended long long ago.
CC @xclaesse
--
Reply to this email directly or view
Michael Catanzaro commented:
I've seen several more jobs failing. And we've had this same problem several
times in the past, too. It seems like our monitoring setup is insufficient.
--
Reply to this email directly or view it on GitLab:
https://gitlab.gnome.org/Infrastructure
Michael Catanzaro created an issue:
https://gitlab.gnome.org/Infrastructure/Infrastructure/-/issues/573
https://gitlab.gnome.org/GNOME/epiphany/-/jobs/1284161 has failed with an error
that looks like the runner is out of disk space:
error: Writing content object: min-free-space-percent '3
Michael Catanzaro commented on a discussion:
https://gitlab.gnome.org/Infrastructure/Infrastructure/-/issues/564#note_1086095
Hi @swilmet, can I ask why did you do this? I'm not sure what's going on here,
but frankly it feels like sabotage, forcing us to remove these dependencies
from gedit
Michael Catanzaro commented:
ack
--
Reply to this email directly or view it on GitLab:
https://gitlab.gnome.org/Infrastructure/Infrastructure/-/issues/568#note_1084602
You're receiving this email because of your account on gitlab.gnome.org
Michael Catanzaro commented:
(CC @tpopela: newly-unwanted packages)
--
Reply to this email directly or view it on GitLab:
https://gitlab.gnome.org/Infrastructure/Infrastructure/-/issues/564#note_1079242
You're receiving this email because of your account on gitlab.gnome.org
Michael Catanzaro created an issue:
https://gitlab.gnome.org/Infrastructure/Infrastructure/-/issues/559
Epiphany CI is failing with:
```
$ flatpak build-update-repo --generate-static-deltas repo/
Updating appstream branch
error: Writing content object: min-free-space-percent '3%' would
Michael Catanzaro created an issue:
https://gitlab.gnome.org/Infrastructure/Infrastructure/-/issues/558
Hi, could we please get a Marge bot configured for Epiphany? It would be nice
to be able to approve multiple MRs at once without each one conflicting with
the other.
(Honestly, I wonder
Michael Catanzaro created an issue:
https://gitlab.gnome.org/Infrastructure/Infrastructure/-/issues/549
The link https://help.gnome.org/misc/release-notes/stable (which is in the
footer of www.gnome.org) points to the 3.36 release notes currently.
--
Reply to this email directly or view
Michael Catanzaro commented:
It might look nicer if we register separate top-level domains for each project.
E.g. https://libsoup.org/ or https://gtk.org/.
--
Reply to this email directly or view it on GitLab:
https://gitlab.gnome.org/Infrastructure/Infrastructure/-/issues/486
Michael Catanzaro created an issue:
https://gitlab.gnome.org/Infrastructure/Infrastructure/-/issues/548
Hi, it seems our ical release schedule at
https://www.gnome.org/start/unstable/schedule.ics has broken somehow. That is
supposed to redirect to
https://static.gnome.org/calendars
Issue was closed by Michael Catanzaro
Issue #543: https://gitlab.gnome.org/Infrastructure/Infrastructure/-/issues/543
--
Reply to this email directly or view it on GitLab:
https://gitlab.gnome.org/Infrastructure/Infrastructure/-/issues/543
You're receiving this email because of your account
Michael Catanzaro commented:
Done.
--
Reply to this email directly or view it on GitLab:
https://gitlab.gnome.org/Infrastructure/Infrastructure/-/issues/543#note_1063184
You're receiving this email because of your account on gitlab.gnome.org
Michael Catanzaro created an issue:
https://gitlab.gnome.org/Infrastructure/Infrastructure/-/issues/543
When releasing glib-networking 2.68.0 today I noticed this error when running
`ftpadmin install`:
```
Triggering ftp.gnome.org updatesudo: PAM account management error: System error
Michael Catanzaro commented:
[Docker runner failures are still occurring as of 14:02
UTC.](https://gitlab.gnome.org/GNOME/gnome-build-meta/-/jobs/1122547)
--
Reply to this email directly or view it on GitLab:
https://gitlab.gnome.org/Infrastructure/Infrastructure/-/issues/518#note_1023995
Michael Catanzaro commented:
Another one: https://gitlab.gnome.org/GNOME/gnome-build-meta/-/jobs/1122546
--
Reply to this email directly or view it on GitLab:
https://gitlab.gnome.org/Infrastructure/Infrastructure/-/issues/518#note_1023990
You're receiving this email because of your
Michael Catanzaro commented:
We are still getting docker failures:
https://gitlab.gnome.org/GNOME/gnome-build-meta/-/jobs/1122546
--
Reply to this email directly or view it on GitLab:
https://gitlab.gnome.org/Infrastructure/Infrastructure/-/issues/518#note_1023987
You're receiving
Michael Catanzaro commented:
Hm, we are having a high number of docker failures too:
* https://gitlab.gnome.org/GNOME/gnome-build-meta/-/jobs/1121647
* https://gitlab.gnome.org/GNOME/gnome-build-meta/-/jobs/1122546
* https://gitlab.gnome.org/GNOME/gnome-build-meta/-/jobs/1122546
So maybe
Michael Catanzaro created an issue:
https://gitlab.gnome.org/Infrastructure/Infrastructure/-/issues/518
Since last night, we've had a large number of gnome-build-meta CI failures when
downloading tarballs from download.gnome.org. I suspect a problem with
download.gnome.org, although
Michael Catanzaro commented:
I don't think we have any plans to move projects that already exist under
GNOME/ to Circle. That would be pretty disruptive.
I see Michael is listed in the [project's
doap](https://gitlab.gnome.org/GNOME/moserial/-/blob/master/moserial.doap) so
he must have
Michael Catanzaro created an issue:
https://gitlab.gnome.org/Infrastructure/Infrastructure/-/issues/496
Looks like we are downloading a new alpine container from Docker whenever we
run the CI? We need to host the container on gitlab.gnome.org instead.
```
ERROR: Preparation failed: Error
Michael Catanzaro commented on a discussion:
https://gitlab.gnome.org/Infrastructure/Infrastructure/-/issues/488#note_971815
Nobody is going to be able to figure that out
--
Reply to this email directly or view it on GitLab:
https://gitlab.gnome.org/Infrastructure/Infrastructure
Michael Catanzaro commented on a discussion:
https://gitlab.gnome.org/Infrastructure/Infrastructure/-/issues/467#note_945145
> Both Bart and Andrea as well as Emmanuele expressed concerns about anyone
> being able to create a :gnome.org Matrix ID. I’m guessing the threat
Michael Catanzaro created an issue:
https://gitlab.gnome.org/Infrastructure/Infrastructure/-/issues/465
It looks like the gnome-nightly repo is out of disk space, according to
https://gitlab.gnome.org/GNOME/epiphany/-/jobs/938268:
```
error: Writing content object: min-free-space-percent
Issue was closed by Michael Catanzaro
Issue #450: https://gitlab.gnome.org/Infrastructure/Infrastructure/-/issues/450
--
Reply to this email directly or view it on GitLab:
https://gitlab.gnome.org/Infrastructure/Infrastructure/-/issues/450
You're receiving this email because of your account
Michael Catanzaro commented:
Actually never mind, screw this, maybe nothing actually needs that. Let's just
leave it at 3.37 forever and see if anybody complains. That is the last
odd-numbered unstable series, after all.
I think we can manually link to the current schedule instead
Michael Catanzaro created an issue:
https://gitlab.gnome.org/Infrastructure/Infrastructure/-/issues/450
Hi, please redirect https://www.gnome.org/start/unstable to point to
https://wiki.gnome.org/Forty for the new release cycle. Thanks!
/cc @averi @barthalion
--
Reply to this email
Michael Catanzaro commented:
I've edited the milestone.
--
Reply to this email directly or view it on GitLab:
https://gitlab.gnome.org/Infrastructure/Infrastructure/-/issues/441#note_921986
You're receiving this email because of your account on gitlab.gnome.org
Issue was closed by Michael Catanzaro
Issue #441: https://gitlab.gnome.org/Infrastructure/Infrastructure/-/issues/441
--
Reply to this email directly or view it on GitLab:
https://gitlab.gnome.org/Infrastructure/Infrastructure/-/issues/441
You're receiving this email because of your account
Michael Catanzaro commented:
@akitouni, have you fixed everything here? Is it OK to close this?
--
Reply to this email directly or view it on GitLab:
https://gitlab.gnome.org/Infrastructure/Infrastructure/-/issues/427#note_912977
You're receiving this email because of your account
Michael Catanzaro commented:
[The repo is corrupted
again.](https://gitlab.gnome.org/GNOME/gnome-build-meta/-/jobs/902802)
```
Job failed: InternalError: Command "flatpak" "build-commit-from"
"--timestamp=NOW" "--no-update-summary" "--untrusted
Michael Catanzaro created an issue:
https://gitlab.gnome.org/Infrastructure/Infrastructure/-/issues/427
I guess this is a follow-up to #425. I've never seen this sort of CI failure
before:
https://gitlab.gnome.org/GNOME/epiphany/-/jobs/900979
```
| Job failed: InternalError: Command
Michael Catanzaro created an issue:
https://gitlab.gnome.org/Infrastructure/Infrastructure/-/issues/425
Looks like the `progress` CI runner has run out of disk space:
https://gitlab.gnome.org/GNOME/epiphany/-/jobs/898261
--
Reply to this email directly or view it on GitLab:
https
Michael Catanzaro commented:
Hm, it would not qualify for GNOME group under the new policy because it is not
core. If #333 takes effect as proposed, then all the evolution repos except
evolution-data-server (which is core) would move elsewhere. I've heard talk of
grandfathering in existing
Michael Catanzaro created an issue:
https://gitlab.gnome.org/Infrastructure/Infrastructure/-/issues/409
flatmgr-finish has always been pretty unreliable, but now I don't think it's
working at all. Just over the weekend, we have:
* https://gitlab.gnome.org/GNOME/gnome-build-meta/-/jobs
Michael Catanzaro created an issue:
https://gitlab.gnome.org/Infrastructure/Infrastructure/-/issues/407
The release-team mailing list keeps receiving spam to be moderated, even though
I've configured mailman to reject all postings. E.g. from today:
```
As list administrator, your
Michael Catanzaro commented:
> Is it something that Release Team should be handling?
I don't know. Do all devs have permission to create global milestones? If not,
we surely don't either: release team doesn't have any special permissions on
GitLab.
I think we have consensus that the n
Michael Catanzaro commented:
Looks like I do have permission to edit global milestones.
--
Reply to this email directly or view it on GitLab:
https://gitlab.gnome.org/Infrastructure/Infrastructure/-/issues/404#note_899817
You're receiving this email because of your account
Michael Catanzaro created an issue:
https://gitlab.gnome.org/Infrastructure/Infrastructure/-/issues/406
vino is obsoleted by gnome-remote-desktop. It contains a bundled copy of
libvncserver from 2004 and that is not great because libvncserver receives a
lot of remote code execution CVEs
Michael Catanzaro commented:
Release team already approved this for core, so it should move to GNOME/.
--
Reply to this email directly or view it on GitLab:
https://gitlab.gnome.org/Infrastructure/Infrastructure/-/issues/405#note_899412
You're receiving this email because of your account
Michael Catanzaro created an issue:
https://gitlab.gnome.org/Infrastructure/Infrastructure/-/issues/401
Please archive gnome-continuous:
* https://gitlab.gnome.org/GNOME/gnome-continuous
* https://gitlab.gnome.org/GNOME/gnome-continuous-yocto
* https://gitlab.gnome.org/GNOME/gnome
Michael Catanzaro commented:
No! My bad! Not your bad!!!
Thanks ;)
--
Reply to this email directly or view it on GitLab:
https://gitlab.gnome.org/Infrastructure/Infrastructure/-/issues/393#note_96
You're receiving this email because of your account on gitlab.gnome.org
Michael Catanzaro commented:
Hmmm, you created a GitLab "Project" because that's what I asked for so of
course it's what you created:
> Hi, release team would like to request creation of a
> https://gitlab.gnome.org/Teams/Releng project
But unfortunately you can't trust me
Issue was reopened by Michael Catanzaro
Issue 393: https://gitlab.gnome.org/Infrastructure/Infrastructure/-/issues/393
--
Reply to this email directly or view it on GitLab:
https://gitlab.gnome.org/Infrastructure/Infrastructure/-/issues/393
You're receiving this email because of your
Michael Catanzaro created an issue:
https://gitlab.gnome.org/Infrastructure/Infrastructure/-/issues/393
Hi, release team would like to request creation of a
https://gitlab.gnome.org/Teams/Releng project for us to use for various
purposes.
--
Reply to this email directly or view
Michael Catanzaro created an issue:
https://gitlab.gnome.org/Infrastructure/Infrastructure/-/issues/392
We had some discussion in the libcroco repo regarding a security vulnerability
that has drawn considerable attention
(https://gitlab.gnome.org/GNOME/libcroco/-/issues/8). Discussion has
Michael Catanzaro commented on a discussion:
https://gitlab.gnome.org/Infrastructure/Infrastructure/-/issues/380#note_877529
Right, I see now a dozen emails about me being made maintainer of everything
where I'm listed in the doap.
--
Reply to this email directly or view it on GitLab
Michael Catanzaro commented:
> Is this an error?
Yeah I assume it has happened to everyone.
--
Reply to this email directly or view it on GitLab:
https://gitlab.gnome.org/Infrastructure/Infrastructure/-/issues/380#note_877516
You're receiving this email because of your acco
Michael Catanzaro commented:
Maybe the script doesn't realize we've migrated to GitLab? Somehow I can still
commit things:
https://gitlab.gnome.org/GNOME/epiphany/-/commit/c05aabef3ef3f72ba42918d5ad30cdfa84a91d79,
so that's good, but the script seems to have also removed my ftpadmin access
Michael Catanzaro commented:
https://gitlab.com/gitlab-org/gitlab/-/issues/231353
--
Reply to this email directly or view it on GitLab:
https://gitlab.gnome.org/Infrastructure/Infrastructure/-/issues/377#note_873560
You're receiving this email because of your account on gitlab.gnome.org
Michael Catanzaro created an issue:
https://gitlab.gnome.org/Infrastructure/Infrastructure/-/issues/377
As of today, I'm now sometimes receiving four duplicate email notifications
from GitLab when it has something to mail me about, instead of the one mail I
would expect. This issue only
Michael Catanzaro commented:
Thanks!
--
Reply to this email directly or view it on GitLab:
https://gitlab.gnome.org/Infrastructure/Infrastructure/-/issues/370#note_870856
You're receiving this email because of your account on gitlab.gnome.org
Michael Catanzaro commented:
> I find it hard to believe you don't know security implications of granting
> `SYS_PTRACE` to CI which runs completely arbitrary loads, not to mention
> runners no longer run with `--privileged` after it was reported it breaks
> glib test s
Michael Catanzaro commented:
BTW, the error message:
```
==277==LeakSanitizer has encountered a fatal error.
==277==HINT: For debugging, try setting environment variable
LSAN_OPTIONS=verbosity=1:log_threads=1
==277==HINT: LeakSanitizer does not work under ptrace (strace, gdb, etc
Michael Catanzaro created an issue:
https://gitlab.gnome.org/Infrastructure/Infrastructure/-/issues/370
For the past couple of months, we've needed privileged runners to run tests
with asan. It seems to be a regression caused by changes to the container
system the CI runs in. It means
Michael Catanzaro created an issue:
https://gitlab.gnome.org/Infrastructure/Infrastructure/-/issues/344
This project is obsolete and contains at least one unfixed sandbox hole. Please
archive it.
--
Reply to this email directly or view it on GitLab:
https://gitlab.gnome.org
Michael Catanzaro commented:
ACK!
--
Reply to this email directly or view it on GitLab:
https://gitlab.gnome.org/Infrastructure/Infrastructure/-/issues/337#note_846629
You're receiving this email because of your account on gitlab.gnome.org
Michael Catanzaro commented:
Sorry, I guess we only need to worry about additions to core. The goal of
figuring out core app changes before the reorg would be to avoid moving apps
out of GNOME/ and then right back into GNOME/ shortly after. That only affects
proposed additions
Michael Catanzaro commented:
Let's make an attempt to resolve at least some of the issues in
https://gitlab.gnome.org/GNOME/gnome-build-meta/-/issues/150 before proceeding
with this. Currently that's blocked on
https://pagure.io/fedora-workstation/issue/125 to make sure upstream changes
1 - 100 of 140 matches
Mail list logo
