hi,


following sourcehut docs I wanted to attach a file to my git annotation 
under refs tab. It worked for my first annotation, however attaching the 
same file name to the *next* git annotation fails: "A file by this name 
was already uploaded." Is this a bug or expected? I just did a force 
push and force push --tags if that matters.


mehdi

So far it had worked well with my work email from office 365.

Hi there,

For what's worth it, my mail server runs on Heztner for the past two years. It's postfix/dovecot/rspamd without reverse dns. Emails get delivered everywhere except gmx.de sofar, since they need a mandatory reverse dns record which I can't set unless I recreate my server with a newly ordered IP from Heztner.

Cheers,
Mehdi

Wish you a prosperous future in the Netherlands. Good luck, Mehdi

On 5/16/21 13:35, Sol Fisher Romanoff wrote:
> I'd like to hack on sourcehut a bit and contribute to it, but I don't yet have a
> server to deploy it on. I'm not very familiar with using this kind of software
> and the Hacking on Sourcehut [1] page isn't very beginner-friendly.
> 
> Can somebody assist me with setting it up on my local machine? I have a 
feeling
> it's a very simple process that I'm missing.
> 
> [1]: https://man.sr.ht/hacking.md
> 

I guess the Hacking document expects you to figure out everything for 
yourself. However there is value in not figuring everything out by trial

On Tue, Apr 27, 2021 at 09:11:43AM -0400, Drew DeVault wrote:
> Do you have multiple sr.ht accounts? SSH keys need to be *globally*
> unique.

Yes, that was it. I have a second account which I plan to delete when the
functionality is there. Meanwhile I use it for testing.

Thanks.

All,

I was about to push from a new system to git.sr.ht and tried to add my
ssh public key to meta. It was rejected with a message that it already
exists in https://meta.sr.ht/~mehdix.keys, except that it doesn't.

I checked the code below to see what happens upon adding:
https://git.sr.ht/~sircmpwn/meta.sr.ht/tree/master/item/metasrht/types/sshkey.py#L35

I tried the snippet with the keys and the definitely have different fingerprints.
So it looks fine. If I'm not mistaken, a cache somewhere has kept my ssh-key
around. I vaguely remember that I might have added and removed the same
key in the past. Below is the public key I tried to add:

---
 LICENSE | 0
 1 file changed, 0 insertions(+), 0 deletions(-)
 create mode 100644 LICENSE

diff --git a/LICENSE b/LICENSE
new file mode 100644
index 0000000..e69de29
-- 
2.30.0

> pictures in GPG keys are common in the EU, it certainly isn't in my bubble (Germany).

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.

btw, I'm in the same bubble!

I have also multiple uids and was planning to add a photo. This is I'd guess a common practice in EU.

How is the current size limit calculated? Are there technical difficulties in increasing the limit? Does having a photo  contradicts any of sr.ht goals?