On Wed May 3, 2023 at 2:39 AM CEST, Ivan - ivan at niktivan.org wrote:
> Error code: SSL_ERROR_INTERNAL_ERROR_ALERT

That's the error returned by caddy while it's fetching a certificate. Nothing
to worry about. Just try again later.

-- 
Moritz Poldrack
https://moritz.sh

Not implemented, but you could compare HEAD and origin/HEAD. If they 
differ, it's a patch series and you can just list the changed files per 
commit in between. Otherwise you can probably assume that you can do a 
rerun.

-- 
Moritz Poldrack
https://moritz.sh

On Mon Apr 17, 2023 at 12:07 AM CEST, Stefan Monnier wrote:
> Even better would be to keep this kind of data in a Git repository, so
> you can edit it on your machine and then push it to SourceHut.

I disagree, this would be a terrible solution. This would either require push
access for people to file bugs, or allow flooding the repo with bogus reports
that may or may not be removable from history.

I think a way similar to how lists handles patchset status would be better.

X-Sourcehut-Assigned-User: ~mpldr,~ferdinandyb
X-Sourcehut-Issue-Labels: bug,database,-stale (add "bug" and "database", remove "stale")
X-Sourcehut-Issue-Status: DUPLICATE

On Fri Apr 14, 2023 at 10:48 AM CEST, Marcus Kober wrote:
> Is there a hook that triggers when emails are sent?"
not yet, it's a work in progress

-- 
Moritz Poldrack
https://moritz.sh

Hi Xavier,

by default python PKGBUILDs look a bit like this[0] and it's usually better to
download the sources directly as done in that PKGBUILD. That said I am not deep
enough in the Python landscape to be able to tell what exactly has to be
packaged, but going by your makefile it would probably have to be built and then
stored in the appropriate subdirectory. Hope that helps :)

[0]: https://aur.archlinux.org/cgit/aur.git/tree/PKGBUILD?h=python-vdf
-- 
Moritz Poldrack
https://moritz.sh

Hi there,

On Sun Apr 9, 2023 at 4:21 PM CEST, 'Oscar Campos' wrote:
> I noticed that when I use aerc to apply a patchset using the command
>
>    :pipe git am 
Consider using it with -3 by default. git can be rather picky otherwise,

> The produced git commit message is missing the mail subject that
> contains the first commit line. It happens even if I use the `-k`
> flag.
Not sure what the -k is supposed to do. You'd want -m or pipe it from the
message list, then it includes the headers.

Hi,

Instead of a push-sync you could make it a pull-sync. For this you would have
to setup a small dispatch.sr.ht somewhere and have it pull the commits using
sourcehut's CI.

-- 
Moritz Poldrack
https://moritz.sh

On Fri Apr 7, 2023 at 12:07 AM CEST, metalune wrote:
> huh, is it that hard to implement? I can code but I don't know if I can do that

I don't think so, I've taken a look into it at that time, but then had a
roomba-moment, bumped into something else and went off in a different
direction.

-- 
Moritz Poldrack
https://moritz.sh

On Thu Apr 6, 2023 at 11:44 PM CEST, builds.sr.ht wrote:
> ✗ #969428 FAILED  aerc/patches/alpine-edge.yml https://builds.sr.ht/~rjarry/job/969428

Need to write a longer commit message :D

> chore: fix typos in contributing guidelines
>
> As many do not know, step-by-step is actually an adjective in its own right.
> Debugging is also written with three g and not with two.
>
> Link: https://www.merriam-webster.com/thesaurus/step-by-step
> Link: https://www.merriam-webster.com/thesaurus/debugging

--

On Thu Apr 6, 2023 at 11:42 PM CEST, metalune wrote:
> I would like to request the ability to authenticate using YubiKey FIDO2 (or FIDO for that matter) authentication support as an alternative/additional second factor to TOTP

This got the nod-of-approval 4 years ago[0], but so far nobody has sat down to actually implement it.

[0]: https://lists.sr.ht/~sircmpwn/sr.ht-discuss/%3C20180724222748.phs3dzcljkwlzb4g%40carbon.fstab.me%3E

-- 
Moritz Poldrack
https://moritz.sh