From bugzilla@gnome.org Sat May 5 13:49:51 2018
Return-Path:
What
Removed
Added
Status
NEW
RESOLVED
Resolution
---
FIXED
It seems to be fixed, I've received an e-mail for GtkSourceVie=
w 4.0.1.
(In reply to Piotr Dr=C4=85g from comment #5) > (In reply to Andrea Veri from comment #4) > > Please confirm/close this bug accordingly. >=20 > Thank you! I=E2=80=99ll close it for now (can=E2=80=99t really test wi= thout messy test > commits), and re-open if necessary. Just confirming that it detected a missing .vala file today, so all is righ= t.
Bug ID | 796271 |
---|---|
Summary | Crash ftpadmin install |
Classification | Infrastructure |
Product | sysadmin |
Version | unspecified |
OS | Linux |
Status | NEW |
Severity | critical |
Priority | Normal |
Component | Other |
Assignee | sysadmin-maint@gnome.bugs |
Reporter | swilmet@gnome.org |
QA Contact | sysadmin-maint@gnome.bugs |
GNOME version | --- |
``` [swilmet@master ~]$ ftpadmin install gnome-latex-3.28.1.tar.xz [22/4710] Gathering information and sorting on version: ., done Preparing installation of gnome-latex-3.28.1.tar.xz: - Checking consistency: ....., done - Checking previous tarball: ....., done - NEWS, done (diff, 12 lines) - ChangeLog, ignored (no change) - Copying tar.xz, done - Creating sha256sum, done Module: gnome-latex Version: 3.28.1 (previous version: 3.28.0) Destination: /ftp/pub/GNOME/sources/gnome-latex/3.28/ Install gnome-latex? [Y/n] Installing gnome-latex-3.28.1.tar.xz: - Moving files: ..., done - Updating LATEST-IS, done - Updating known versions, done - Removing original tarball, done Doing notifications: - Informing ftp-release-listTraceback (most recent call last):
|
```
What | Removed | Added |
---|---|---|
Status | NEW | RESOLVED |
CC | andrea.veri@gmail.com | |
Resolution | --- | FIXED |
This was related to a faulty DOAP file [1], should be fixed by now. If you want to re-run the latest step of your release please launch `ftpadmin notify module.tar.gz`. cheers, [1] https://gitlab.gnome.org/GNOME/librsvg-oci-images/commit/1c17f6ed62c7320e99f6e0d12de5d8b11db172af
Any update on whether this service is going to be used at all? There was some pressure on making this happen but then no one ever touched the service after it got provisioned. Thanks,
Bug ID | 796356 |
---|---|
Summary | List www.pango.org in SSL certificate |
Classification | Infrastructure |
Product | sysadmin |
Version | unspecified |
OS | Linux |
Status | NEW |
Severity | normal |
Priority | Normal |
Component | Certificates |
Assignee | sysadmin-maint@gnome.bugs |
Reporter | pmenzel+bugzilla.gnome.org@molgen.mpg.de |
QA Contact | sysadmin-maint@gnome.bugs |
GNOME version | --- |
Firefox shows the warning below accessing https://www.pango.org/. > www.pango.org uses an invalid security certifica= te. >=20 > The certificate is only valid for the following names: 2016.las.gnome.= org, blogs.gnome.org, bugs.gnome.org, bugzilla.gnome.org, build.gnome.org, = conference.gnome.org, download.gnome.org, etherpad.gnome.org, git.gnome.org= , gitlab-test.gnome.org, gitlab.gnome.org, gnome.org, jabber.gnome.org, l10= n.gnome.org, live.gnome.org, meetbot.gnome.org, nagios.gnome.org, odrs.gnom= e.org, office.cloud.gnome.org, opw.gnome.org, outreachy-archive.gnome.org, = outreachy.gnome.org, paste.gnome.org, people.gnome.org, projects-old.gnome.= org, projects.gnome.org, restaurant.gnome.org, sdk.gnome.org, smtp.gnome.or= g, socket.gnome.org, wiki.gnome.org, www.gnome.org It=E2=80=99d be great, if you added the domain to the certificate.
What | Removed | Added |
---|---|---|
Status | NEW | RESOLVED |
CC | andrea.veri@gmail.com | |
Resolution | --- | FIXED |
Bug ID | 796395 |
---|---|
Summary | Misleading message when committing to stable branches |
Classification | Infrastructure |
Product | sysadmin |
Version | unspecified |
OS | Linux |
Status | NEW |
Severity | normal |
Priority | Normal |
Component | Git |
Assignee | sysadmin-maint@gnome.bugs |
Reporter | mcrha@redhat.com |
QA Contact | sysadmin-maint@gnome.bugs |
GNOME version | --- |
When committing to the master branch, I get a clean response: > [evolutionews]$ git push > Counting objects: 6, done. > Delta compression using up to 8 threads. > Compressing objects: 100% (6/6), done. > Writing objects: 100% (6/6), 855 bytes | 855.00 KiB/s, done. > Total 6 (delta 5), reused 0 (delta 0) > To gitlab.gnome.org:GNOME/evolution-ews.git > 47cc16f4..4b879e48 master -> master but when I commit into the stable branch, in this case origin/gnome-3.28: > [evolutionews]$ git push > Counting objects: 6, done. > Delta compression using up to 8 threads. > Compressing objects: 100% (6/6), done. > Writing objects: 100% (6/6), 861 bytes | 861.00 KiB/s, done. > Total 6 (delta 5), reused 0 (delta 0) > remote: > remote: To create a merge request for gnome-3-28, visit: > remote: https://gitlab.gnome.org/GNOME/evolution-ews/merge_requests/new?merge_request%5Bsource_branch%5D=gnome-3-28 > remote: > To gitlab.gnome.org:GNOME/evolution-ews.git > a24562f6..d4eb2b06 gnome-3-28 -> gnome-3-28 That "remote" message is misleading, the merge request is a nonsense, because the commit just landed into the place it suggests me to do the merge request for. I do not know what logic is behind that message, but it requires to be updated. At least from my point of view.
Bug ID | 796416 |
---|---|
Summary | Can't commit to gnome-devel-docs through l10n.gnome.org |
Classification | Infrastructure |
Product | sysadmin |
Version | unspecified |
OS | Linux |
Status | NEW |
Severity | normal |
Priority | Normal |
Component | Git |
Assignee | sysadmin-maint@gnome.bugs |
Reporter | anders.jonsson@norsjovallen.se |
QA Contact | sysadmin-maint@gnome.bugs |
GNOME version | --- |
Originally filed as https://gitlab.gnome.org/GNOME/damned-lies/issues/79= , where Claude answered that I should file this here since it is about git ho= oks. When trying to commit a Swedish translation of gnome-devel-docs with l10n.gnome.org, this failed with the following error message: =E2=80=9D[Errno 1] Command: "['git', 'push', 'origin', 'master']"= , Error: remote: translations user cannot modify 'accessibility-devel-guide/sv/sv.po' To ssh://git.gnome.org/git/gnome-devel-docs ! [remote rejected] master -> m= aster (pre-receive hook declined) error: failed to push some refs to 'ssh://git.gnome.org/git/gnome-devel-docs' =E2=80=9D I have tested with both accessibility-devel-guide and platform-demos and th= ey both have the same problem.
What | Removed | Added |
---|---|---|
Status | NEW | RESOLVED |
CC | andrea.veri@gmail.com | |
Resolution | --- | FIXED |
What | Removed | Added |
---|---|---|
CC | csoriano@gnome.org |
This comes from upstream GitLab hooks. Can you report upstream and see if they have planned a way to configure that?
What | Removed | Added |
---|---|---|
Status | NEW | RESOLVED |
Resolution | --- | NOTGNOME |
Filled https://gitlab.com/gitlab-org/gitlab-ce/issues/46926
Bug ID | 796458 |
---|---|
Summary | Please disable bugbot on all channels |
Classification | Infrastructure |
Product | sysadmin |
Version | unspecified |
OS | Linux |
Status | NEW |
Severity | normal |
Priority | Normal |
Component | IRC |
Assignee | sysadmin-maint@gnome.bugs |
Reporter | mcatanzaro@gnome.org |
QA Contact | sysadmin-maint@gnome.bugs |
CC | maswan@acc.umu.se, stric@acc.umu.se |
GNOME version | --- |
bugbot is no longer interesting. Could we remove it from all channels, please? Nowadays it just posts broken links in response to gitlab-bot: gitlab-bot: Engagement bug 32 in Social-Media-and-PR "PR and call for testing for Fractional Scaling in GNOME Shell" (comments: 1) [Opened] bugbot: Bug https://bugzilla.gnome.org/show_bug.cgi?id=32 was not found.
What | Removed | Added |
---|---|---|
CC | develinthedetail@gmail.com |
For consideration: bugbot may not be _totally_ useless until all bugs are read-only. For example, for a while I have been keeping one eye on #bzbot, where bugbot shows all bug status changes. Admittedly there is not much activity after the recent migration, and I make no claim that this is actually useful. For reference, bugbot is currently on 39 channels: banshee, bugbot, bugs, bzbot, conduit, contacts, docs, documents, evolution, geary, gegl, gitg, gnome-br, gnome-builder, gnome-calculator, gnome-calendar, gnome-cz, gnome-flashback, gnome-it, gnome-mud, gnome-nl, gnome-todo, gnomefr, gtk+, gtksourceview, i18n, monodev, monodevelop, monogame, nautilus, newcomers, pdfmod, photos, pygtk, release-team, seahorse, sysadmin, vala, webhackers
What | Removed | Added |
---|---|---|
Status | NEW | RESOLVED |
CC | andrea.veri@gmail.com | |
Resolution | --- | FIXED |
I agree with you Edward, I feel we should keep bugbot around until BZ is around for historical purposes, the best solution here would be adding ignores against GitLab bots nicknames. I've just added one for gitlab-bot, please let me know if there's more of them I should include on the list.
The other problem is that most of the remaining use of Bugzilla links will be for other Bugzilla instances, e.g. bugs.webkit.org. It's always annoying when I post a Bugzilla link in #gnome-hackers and bugbot posts BS information by using the bug ID from a separate Bugzilla instance to look up some unrelated bug on GNOME Bugzilla. So I'd prefer to get rid of it anyway. Or make it ignore everything except bugzilla.gnome.org.
There's a default Bugzilla instance flag we can pass on a per channel basis, we used to set that when a new channel requested bugbot in the past. Did we miss any probably? What channel are you seeing this behavior on?