Hello,
sorry for the delay in response, I got pretty sick in the meantime.
Now that I'm feeling better:

Kenny Levinsen <kl@kl.wtf> writes:
> Are you sure this is the cause? Why in the world would pinentry need to
> poke at the TTY?

That is a very good question with a complicated answer.
The following is coming from my experience (i.o.w. I did not investigate
gpg codebase), so the details might be wrong, but the general picture
should be accurate.

The main problem is that current GPG works in client-server mode;

Hi list,
I was having trouble getting pinentry (from gnupg) working on my Artix
machine. After a debugging session, I have found out that the trouble is
that the TTY I'm currently on is not owned by me, but by root.
On that tty, I was logged in using greetd (with tuigreet greeter).

I have switched to another tty which was still running agetty,
logged in and I was sucessfully able to use pinentry; the tty was also
owned by my user.

So it seems to me that using greetd, I'm not given the ownership of the
tty and that breaks pinentry. I'm not sure whether this is actually a
bug in greetd, tuigreet or if I have anything else (PAM?) misconfigured.

That looks exactly as the thing I was looking for :)

Thanks a lot, Stacy!
--
Jan Staněk – Khardix

Hi list,
I'll be setting up a new machine in the near future,
and I'm planning to try non-systemd distro.
While I'm really happy with alpine and openrc on my server,
on my workstation I'm used to have several daemons (mpd, gpg-agent, …)
being managed by user-level systemd services.

I was looking around, but did not find any popular alternative to it.
Most of the init systems/service managers deal only with system-level
stuff; nothing on the user level.

Is anyone aware of such a service manager they would reccomend?
Failing that, what are best practices/guidelines to launching stuff like
gpg agent on login?

Kind of talking from the top of my head here, so I might be wrong,
but the `**` syntax for nested directory glob
is definitely not part of a POSIX shell.

If you need to list all go files in all subdirectories,
find is indeed your friend. This is untested, but roughly

$ test -z "$(find -name '*.go' -type f | xargs gofmt -l)"

should be equivalent to what you intended to do.

Hope this helps!
--
Jan Staněk – Khardix

Ahojte,
Báře se dneska podařilo ulovit termín fyzioterapie,
což znamená, že na půl šestou spíše nestíhá.
Budeme proto dneska začínat později, odhadem tak v šest.

Stále je možno dorazit už na půl na pokec a případné dořešování věcí
přede hrou :)

Těším se večer!
--
Jan Staněk – Khardix

Razzi Abuissa <razzi@abuissa.net> writes:
> Is there a workflow to finalize repo creation from the command line?

You can specify the details as push options:

git push \
    -o visibility=public -o description='Some description here.' \
    $url

HTH!
--
Jan Staněk – Khardix

Toto je testovací vlákno pro ověření správného nastavení e-mailového
klienta.
--
Jan Staněk – Khardix

Hi, I thought I will chime in with my 2 cents.

Mehdi Sadeghi <mehdi@mehdix.org> writes:
> Oh, sorry for the vague statement. I meant putting picture on thing
> like resumes is common practice. However, from the last FOSDEM
> keysigning I can certainly remember keys with photos.

I think there is some confusion on the intended usage of the keys here.

When *you* distribute your keys to others
(as attachment, via keyserver, etc.),
feel free to include whatever
(within reason – don't be rude and hog other people's harddrive space).
These keys can become quite large even without photos

Kévin Le Gouguec <kevin.legouguec@gmail.com> writes:
> Lars Ingebrigtsen wrote a pretty extensive guide on the subject a year
> ago:
>
> https://lars.ingebrigtsen.no/2020/03/25/so-you-want-to-run-your-own-mail-server/

Thanks, I will check it out.

> (And a pretty extensive automated setup script to boot.)

That is usually something I want to avoid.
I get that it is intended to save time, but when I do something,
I like knowing why I'm doing something
(which has the added benefit of usually knowing where to look