Dear Mahdi,

scdoc is packaged in Fedora - you can install it using your system's
package manager:

	dnf install scdoc

Best,

-- 
Timo

Hi Haowen,

> 1.
> I see that in Fedora deprecated images are not removed from the repo. Should
> we keep those? If so, for how long?

That's on Drew's side, and such policy probably apply to any OS
flavor. Such images are not refreshed anymore and upstream stopped to
maintain them - the only use is not to break CI pipelines that use a
specific release, but I'm not sure if we want to do that.

> 2.
> In man.sr.ht, Fedora 34 is said to be updated weekly but in crontab it's
> updated monthly. Which one should I fix?

Hi Drew, Haowen,

Thank you both for taking this up quickly!

@drew there's some action required on the admin side to fix the F36
deployment: [1].

[1] https://builds.sr.ht/~sircmpwn/job/620454#task-deploy

Cheers,

-- 
Timothée

Hello everyone,

I wish to pass over the maintenance of the Fedora image to another
community member. I do not have that much use for it anymore, and am
disengaing from non-very-important-to-me maintainship as I'm slowly
moving away from IT engineering into agriculture. Turns out I find
farming ways more meaningful and exiting than IT :-)

I'll stay around, but do not expect high bandwith from me.

Cheers,

-- 
Timothée

Hello there,

I'm the Fedora image maintainer - here's a few hints for you:

* You don't need to build from rocky linux. You can start from the
  Fedora image and tell DNF to use the rocky linux repository instead of
  the Fedora ones.
* You don't necessarly need to setup meta and build locally - I just
  test the images with qemu.
* Rocky Linux is a rebuild of RHEL, which is based on Fedora. You might
  even be able to use the script as-it modulo repository URL.

Feel free to contact me directly if you need him - I'm quarantined for a
few more days so I have some spare time at hand...

> Any special deployment steps to get the new images into circulation?

Not forgetting to deploy the new cronttab.

-- 
Timothée

> My idea is to build a search service following the philosophy of
> sr.ht of independent services that will have its own API that may
> be triggered from a build job. list and todo will require specific
> hooks.

Why not implement it as a feature of hub.sr.ht first? That's where
projects are grouped - I wonder if yet another service is not a bit
overkill / premature. Do we need arbitrary search across arbitrary
groups of projects?

-- 
Timothée

I added support for LDAP at some point, which was reverted due to a
licensing issue witht the python 'ldap' module. I didn't have the
time/incentive to rewrite it against yet-another-ldap-python module
which is properly licensed. Ping me if you want more details / the
actual links.

It would work with active directory (modulo 10 lines of code).

-- 
Timothée

> Is the branching anyhow relates to the recent GPG check failures?
> https://builds.sr.ht/~njs/trio/pulls/fedora.yml

I think so.

> GPG check works again in `dnf install` after `dnf update --nogpgcheck`
> so I suspect there is some issue with the current image,
> although I thought daily update should prevent this from happening.

Looks like daily rebuilds are not happening [1].

I suspect Drew forgot to deploy the updated crontab [2]. @Drew can you
take a look?

Great, thanks! Note that we'll have to update this again in a few days
since Fedora 34 will be branched from Rawhide (Rawhide will become
Fedora 35) on 2021-02-09.