Paths are constant, only anchors are generated by forgejo.

I didn’t test this, but it will change the whole URL while changes are only needed in its fragment component (after the first #).

NB: global substitution s///g is not applicable here because you need to perform new substitutions in a substituted text. Both sed regexp syntaxes (basic and extended) don’t support lookarounds that could solve this issue.

As I see, you’ve already got an answer how to convert text to lower case. So I just tell you how to replace all occurrences of %20 with -. You need to repeat substitution until no matches found. For such iteration you need to use branching to label. Below is sed script with comments.

:subst                                         # label
s/(\[[^]]+\]\([^)#]*#[^)]*)%20([^)]*\))/\1-\2/ # replace the first occurrence of `%20` in the URL fragment
t subst                                        # go to the `subst` label if the substitution took place

However there are some cases when this script will fail, e. g. if there is an escaped ] character in the link text. You cannot avoid such mistakes using only simple regexps, you need a full featured markdown parser for this.

It is documented in libapt-pkg-doc (/usr/share/doc/libapt-pkg-doc/method.html/index.html).

Why you say “Linux” when you mean “Fedora”?

If I’d decide to implement something like this, I’d consider two options: local repo with file:// scheme or custom apt-transport. HTTP server is needless here. (But I’ll never do this because I prefer to rebuild packages myself if there’s no repo for my distro.)

Bank clients. Taxi aggregator clients.

What does an ordinary RHEL admin do when something does not work?

man jq

It’s just generally faster to use the terminal if you know what you’re doing.

It’s also true for other distros. Not because they have poor GUI tools but because CLI is faster than GUI if you know what you are doing.

Be careful if you buy a Samsung 8x0 SSD. They have long standing bugs that may cause data loss. They are worked around in the kernel, however you have to ensure that the workaround for your particular model exists in the kernel version you use.

Glibc preserves backward compatibility, so if you build against the oldest version you want to support, the resulting binary will work with newer ones.

However that’s definitely not what I recommend to do. Better learn packaging and build native packages for distros you are going to support. OBS can make this a bit easier, but any modern CI will also do the job.

Isn’t that video stream already compressed? Or you want to convert it using another codec/bitrate?

LOL, all Linux vendors = Red Hat.

All generalizations are false.

What kind of changes? Package installation, removal and configuration? Use apt-mark showmanual to save list of manually installed packages, dpkg --get-selections | grep 'deinstall$' to save list of removed packages, debconf --get-selections to save debconf package settings, backup files that you edited in /etc. This should be enough for restoration, wouldn’t take a long time for backup and avoid risk of filesystem inconsistency.

The standard answer: don’t backup the system, automate its deployment instead. Backup only data.

Before anyone getting on about Security I don’t give 2centa about it

So Linux is not for you. Take a look at MS DOS 4.0, its sources were published few days ago.

What is this? Looks like a website filled with info about projects unrelated to it and gathering donations for unknown purpose.

Why not use Privacy Badger to prevent usage of tracking cookies?