Infrastructure | ftp.gnome.org: Firefox and Google Chrome marking all recent source archives as malware (#477)

2020-11-02 Thread andrewnz-nz
andrewnz-nz created an issue: https://gitlab.gnome.org/Infrastructure/Infrastructure/-/issues/477 As above, Firefox and Google Chrome are marking all recent source archives as malware and by default stopping downloads. I started a bug report here for Firefox but as Google Chrome is doing

Re: Infrastructure | ftp.gnome.org: Firefox and Google Chrome marking all recent source archives as malware (#477)

2020-11-02 Thread andrewnz-nz
andrewnz-nz commented: The URLVoid shows reports from about 20 websites that report unsafe URLs. The only 'detection'/issue with gnome.org or ftp.gnome.org is on the VirusTotal report, just one by 'CRDF' ( https://threatcenter.crdf.fr/ )

Re: Infrastructure | ftp.gnome.org: Firefox and Google Chrome marking all recent source archives as malware (#477)

2020-11-02 Thread andrewnz-nz
andrewnz-nz commented: The actual address of a source archive that's blocked by Chrome and Firefox (I'm in New Zealand) is from https://laotzu.ftp.acc.umu.se Which is on no blacklist and has no detections, not even the one ftp.gnome.org has. -- Reply to this email directly or view it on

Re: Infrastructure | ftp.gnome.org: Firefox and Google Chrome marking all recent source archives as malware (#477)

2020-11-02 Thread andrewnz-nz
andrewnz-nz commented: ![Screenshot_20201103-134806](/uploads/a82958d1c932b26cde9a04ac882c4d8e/Screenshot_20201103-134806.png) I don't know if Firefox or Chrome actually refer to this websites URL black list but this all I could find in regards to ftp.gnome.org having a less than perfect

Re: Infrastructure | Set up documentation status tracker (#431)

2020-11-02 Thread Bartłomiej Piotrowski
Bartłomiej Piotrowski commented: @shaunm Any preferences about the domain it should be deployed at? -- Reply to this email directly or view it on GitLab: https://gitlab.gnome.org/Infrastructure/Infrastructure/-/issues/431#note_951141 You're receiving this email because of your account on

Re: Infrastructure | gnome-build-meta keeps producing corrupt ostree objects (#446)

2020-11-02 Thread Bartłomiej Piotrowski
Issue was closed by Bartłomiej Piotrowski 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

Re: Infrastructure | gnome-build-meta keeps producing corrupt ostree objects (#446)

2020-11-02 Thread Bartłomiej Piotrowski
Bartłomiej Piotrowski commented: At least now everything seems to be installable for both x86_64 and aarch64. I will be landing some safe guards here and there this week. -- Reply to this email directly or view it on GitLab:

Re: Infrastructure | gnome-build-meta keeps producing corrupt ostree objects (#446)

2020-11-02 Thread Bartłomiej Piotrowski
Bartłomiej Piotrowski commented: https://gitlab.gnome.org/GNOME/gnome-build-meta/-/merge_requests/917 -- Reply to this email directly or view it on GitLab: https://gitlab.gnome.org/Infrastructure/Infrastructure/-/issues/446#note_951233 You're receiving this email because of your account on

Infrastructure | Error when pushing to gexiv2 due to lack of a DOAP category (#476)

2020-11-02 Thread Olav Vitters
Olav Vitters created an issue: https://gitlab.gnome.org/Infrastructure/Infrastructure/-/issues/476 I got the following error after pushing to gexiv2: ``` $ git push Enumerating objects: 7, done. Counting objects: 100% (7/7), done. Delta compression using up to 4 threads Compressing objects: