Ihor Radchenko <yantar92@posteo.net> writes:

> The build is failing because plantuml has been removed from Debian
> testing:
>
> https://tracker.debian.org/pkg/plantuml

Shall we use debian/stable or remove plantuml?  I'm afraid in both
cases it might continue to fail.  Or deactivate plantuml altogether?

-- 
 Bastien Guerry

"Drew DeVault" <sir@cmpwn.com> writes:

> Hey Bastien, sorry for the wait. This is pretty high on my priorities so
> you can expect me to finalize the details within a couple of weeks.

That's great to read, thank you very much!

-- 
 Bastien Guerry

Hi Christian,

Christian Egli <christian.egli@sbs.ch> writes:

> I had my papers signed a long time ago, probably with a different
> employer, I'd be happy to try to get an updated copyright assignments.
>
> Do I just send a mail to assign@fsf.org?

You can email assign@fsf.org this form with updated information:

https://orgmode.org/request-assign-future.txt

You can CC Ihor and I and copyright-clerk-comment@fsf.org.

Bastien <bzg@gnu.org> writes:

> Salih Muhammed <lr0@gmx.com> writes:
>
>> Drew DeVault <sir@cmpwn.com> wrote:
>>
>>>I am willing to consider a patch which loosens up the content type
>>>filter such that list admins can opt-in to allowing HTML email -- IF it
>>>has a plaintext part as well and NOT by default.
>>
>> Any updates on this?
>
> I did not manage to receive an email containing both plain text and
> HTML parts on a list where I emptied the "Rejected mimetypes" field

Ihor Radchenko <yantar92@posteo.net> writes:

> It was not obvious at all from the error page that the problem is that I
> am not logged in. After logging in, I am able to access the logs.

Great, thanks for confirming.

-- 
 Bastien Guerry

Ihor Radchenko <yantar92@posteo.net> writes:

> The error I am seeing is when I tried to read the full logs upon seeing
> the build failure email. The exact URL where I am getting the error is
> https://builds.sr.ht/query/log/1201941/check/log

Yes, because only authenticated users can access this.

I'm sending the log privately now.

-- 
 Bastien Guerry

Hi Ihor,

Ihor Radchenko <yantar92@posteo.net> writes:

> "builds.sr.ht" <builds@sr.ht> writes:
>
>> worg-publish #1201941: FAILED in 5m34s
>>
>> https://builds.sr.ht/~bzg/job/1201941
>>
>> ✓ install ✓ upload ✗ check 
>
> I am trying to see what exactly went wrong, but sr.ht is not letting me
> see the complete log for some reason.

Salih Muhammed <lr0@gmx.com> writes:

> Drew DeVault <sir@cmpwn.com> wrote:
>
>>I am willing to consider a patch which loosens up the content type
>>filter such that list admins can opt-in to allowing HTML email -- IF it
>>has a plaintext part as well and NOT by default.
>
> Any updates on this?

I did not manage to receive an email containing both plain text and
HTML parts on a list where I emptied the "Rejected mimetypes" field
and added "text/*" for permitted fields, I guess there is no update
yet on this.

Simon Ser <contact@emersion.fr> writes:

> This is likely a result of [1]. It sounds like you were making use of
> the repo owner's secret and pushing with a different account.

Yes, this is it, thanks.

I subscribed to https://git.sr.ht/~sircmpwn/builds.sr.ht/refs/rss.xml

Is this the preferred way to know about such changes?

-- 
 Bastien Guerry

When pushing commits to https://git.sr.ht/~codegouvfr/documentation,
the builds are ran from https://builds.sr.ht/~bzg/ instead of being
ran from https://builds.sr.ht/~codegouvfr/.

Builds fail because secrets are not resolved:

[#1082370] 2023/10/25 10:14:55 Resolving secret bdd50953-add5-4ddb-9f34-9f0781900b7e
[#1082370] 2023/10/25 10:14:55 Processing post-failed triggers...
[#1082370] 2023/10/25 10:14:56 Sent build results email to bastien.guerry@code.gouv.fr
[#1082370] 2023/10/25 10:14:56 Build failed.

I noticed this only now and I remember things were fine two days ago.

What is going on here?  Let me know if I can help with more info.