Huh, I guess Ubuntu patched Unattended Upgrades to change the config format.
Try "cloudsmith/caddy/stable:any-version";
Huh, I guess Ubuntu patched Unattended Upgrades to change the config format.
Try "cloudsmith/caddy/stable:any-version";
You’re right with the origin. codename
or n
in short form is any-version
. ${distro_codename}
won’t match that, as it contains the codename for your distro release, like bookworm
for Debian 12.
With any-version
the repo owner’s basically saying you can install this regardless of your distro version or they handle it on their end somehow.
Try just using the origin instead, like this.
"origin=cloudsmith/caddy/stable";
Unattended Upgrades only checks and updates programs in repos it knows about. As you found out, you’ll need to add the custom repository to the Origins pattern in 50unattended-upgrades.
You can find a list of all repositories and their data using apt policy
Here are the custom repositories I have on one of my servers:
500 https://repo.zabbix.com/zabbix/7.0/debian bookworm/main all Packages
release v=12,o=Zabbix,a=zabbix,n=bookworm,l=zabbix,c=main,b=all
origin repo.zabbix.com
500 https://repo.zabbix.com/zabbix/7.0/debian bookworm/main amd64 Packages
release v=12,o=Zabbix,a=zabbix,n=bookworm,l=zabbix,c=main,b=amd64
origin repo.zabbix.com
500 https://pkgs.tailscale.com/stable/debian bookworm/main all Packages
release o=Tailscale,n=bookworm,l=Tailscale,c=main,b=all
origin pkgs.tailscale.com
500 https://pkgs.tailscale.com/stable/debian bookworm/main amd64 Packages
release o=Tailscale,n=bookworm,l=Tailscale,c=main,b=amd64
origin pkgs.tailscale.com
500 https://deb.nodesource.com/node_20.x nodistro/main amd64 Packages
release o=. nodistro,a=nodistro,n=nodistro,l=. nodistro,c=main,b=amd64
origin deb.nodesource.com
Look at the line starting with release
and search for a combination that uniquely identifies the Caddy repository.
The output above is using the short form keywords, while the examples in 50unattended-upgrades use the long form. It’s fine to use either.
One special case is the site
keyword. This is the URL coming after origin
in the output above and might be confusing.
Keywords
// a,archive,suite (eg, "stable")
// c,component (eg, "main", "contrib", "non-free")
// l,label (eg, "Debian", "Debian-Security")
// o,origin (eg, "Debian", "Unofficial Multimedia Packages")
// n,codename (eg, "jessie", "jessie-updates")
// site (eg, "http.debian.net")
Based on the apt policy
output above, here’s what I use to enable automatic updates for these repositories.
Using origin
and codename
follows the standard Debian repos and I’d recommend using that if possible.
Node doesn’t provide a reasonable repo file, so I had to set site
based on the URL behind origin
in apt policy
"site=deb.nodesource.com"; //Nodesource repository
"origin=Zabbix,codename=${distro_codename}"; //Zabbix Agent repository
"origin=Tailscale,codename=${distro_codename}"; //Tailscale repository
Without docker you still just copy your files from Windows to Linux, though you have to find the right directories for that. Jellyfin can be installed directly on Debian. Just add their repo and go
Never used Shopify unfortunately, so I can’t help you with that.
The way I tag media is using MediaElch. It requires manually going through each series and identifying it, but with your proper naming it should give decent suggestions already.
If some metadata is missing for single episodes, try changing the metadata provider, sometimes one or the other just has bad/incomplete data.
If you only need file syncing, there are better options than Nextcloud. But Nextcloud is the only real option if you want to create a full suite of replacements for office365 or google thanks to the large plugin ecosystem.
I’d never heard of Transsion before, so I took a quick look on Wikipedia.
TLDR:
They sell mostly inexpensive phones in poorer regions.
Features of their phones are targeted for those regions, like Africa, where they have special features to calibrate camera exposure for darker skin, retain dual SIM and support many local languages.
Get a cheap VPS and set up a VPN of your choice.
I don’t know of any project that already supports that AI processor. You’d still be using the CPU and GPU at the moment.
You mean just not caring or something else?
Thing is, you can’t just do that as a registered corporation, even if you’re from another country.
A lot of the stuff you get on nhentai is sometimes questionable. Like 12y/o looking sister questionable.
And what exactly did nhentai figure out that Pornhub didn’t?
I can really recommend XCP-ng. For me it strikes a pretty good balance of features and ease of use.
You mean to tell me nhentai is your model porn site?
Using whatever works better for the current project is doing Hybrid Cloud. Now your boss can brag about how modern the infrastructure is.
And 2d, who self host on a server/VPS they rented somewhere.
An active fork (last I checked) would be hyfetch.
ISPs were already required to block the sites. I don’t think an additional block on the Cisco side would change anything in that case.
Apparently Cisco operates a popular DNS resolver? Never heard of that before.
And definitely don’t learn how to use a VPN. Or set up Unbound or Bind or PowerDNS Recursive…
KDEConnect?
So basically Apple wants to kill the filesystem on Mac as well.