ive made a complete mess of my /etc/apt/sources.list and /etc/apt/sources.list.d #apt #repository #source #kali

https://askubuntu.com/q/1565264/612

ive made a complete mess of my /etc/apt/sources.list and /etc/apt/sources.list.d

What have you tried: alot thats got me in an even more of a mess What is the error: └─$ sudo apt update[sudo] password for mark:Hit:1 kali-bleeding-edge InReleaseHit:2 kali-experimental InRelease...

Ask Ubuntu

----------------

🛠️ Tool: Missing README in GitHub Repository
===================

The repository Antonlovesdnb/bc96210121b9222373436f8d8f21e3ec returns a single, explicit indicator: "README not found - fetching original page." The available metadata from the source input is limited to the repository identifier and that error/notice string. No README content, descriptive documentation, or additional file listings were provided in the input.

Observed facts
• Repository identifier: Antonlovesdnb/bc96210121b9222373436f8d8f21e3ec
• Status message: "README not found - fetching original page"
• No README content returned in the provided input

Implications based on the observed input
• The only verifiable item from the supplied data is absence of README content and the presence of the repository name/ID. There are no further artifacts, file lists, code snippets, or metadata included in the source to analyze.

Technical gaps in the source
• No file tree or manifest data was included in the input.
• No commit history, contributor list, release tags, or binary/artifact references were supplied.
• No indicators (hashes, URLs beyond the repo name, file names) are present to perform follow-up correlation.

What the input reports (not inferred)
• The input explicitly reports a missing README for the named repository and a fetch attempt message. No other statements or technical details were provided by the source.

Summary

The supplied content documents a repository-level observation: a GitHub repository (Antonlovesdnb/bc96210121b9222373436f8d8f21e3ec) where the README file could not be retrieved and the listing shows "README not found - fetching original page." Beyond that single status message and the repository identifier, the input contains no further concrete artifacts or technical details for analysis.

🔹 github #repository #tool #readme #metadata

🔗 Source: https://gist.github.com/Antonlovesdnb/bc96210121b9222373436f8d8f21e3ec

Splunk Health Check

Splunk Health Check. GitHub Gist: instantly share code, notes, and snippets.

Gist
📬 Grimmory hat BookLore abgelöst: eine E-Book-Verwaltung ohne Cloud-Zwang
#EBooks #Softwareentwicklung #BookLore #Calibre #Docker #Grimmory #MariaDB #Repository #Umbrel https://sc.tarnkappe.info/f92026
Grimmory hat BookLore abgelöst: eine E-Book-Verwaltung ohne Cloud-Zwang

Grimmory ist eine Open-Source-Software zur Verwaltung der eigenen digitalen Bibliothek, die man auf dem NAS oder Server selbst hostet.

TARNKAPPE.INFO
Projektkoordinator*in und Repository-Manager*in für DataPublication.nrw

Vollzeit, befristet, EG 13, Kennziffer: 2026/179

Universität Bonn

How to resolve "Key is stored in legacy trusted.gpg keyring" and migrate to DEB822 .sources format in Ubuntu 24.04/26.04? #apt #updates #2404 #repository #gnupg

https://askubuntu.com/q/1565006/612

How to resolve "Key is stored in legacy trusted.gpg keyring" and migrate to DEB822 .sources format in Ubuntu 24.04/26.04?

Ever since upgrading to the latest LTS, I am getting the following warning every time I run sudo apt update: W: http://ppa.launchpad.net/.../ubuntu/dists/noble/InRelease: Key is stored in legacy tr...

Ask Ubuntu

"Planning is understood to [promote trust in repositories] but [...] despite the importance assigned to succession planning in certification standards for trustworthy digital #repositories (TDRs), there is little in-depth guidance on how to design and implement such plans."

Hope for the best, plan for the worst: Reducing risks associated with #repository cessation https://doi.org/10.2218/ijdc.v20i1.1091 #TDRs #DigitalLibraries #DigitalCuration #OpenData #OpenResearch #digipres

Hope for the best, plan for the worst: Reducing risks associated with repository cessation: ABC | International Journal of Digital Curation

GANZ FRISCH: Falls zwischen Talks über Repositories und Infrastruktur auch Zeit für einen Blick auf neue Jobs ist:
📢 Die UB Tübingen sucht Verstärkung für ihre Repository- und Publikationsservices.

Vielleicht sitzt die zukünftige Kolleg:in ja gerade im Publikum.

#DSpacePT26 #OpenAccess #Repository #OpenScience

[ Blog ] Proxmox VE 8 to 9 upgrade guide

The release of version 9, introduces new features and significant improvements making the #Proxmox VE 8 to 9 upgrade worthwhile.

By upgrading, you gain access to the latest features, critical security patches, and performance optimizations.

 
Prerequisites for Proxmox VE 8 to 9 upgrade
Before proceeding with http://rviv.ly/EvMkWF #debian #repository #aggiornamento

We at @fiz_karlsruhe are delighted to have been able to support the ANTSCAN team in publishing their 2225 datasets on #RADAR4KIT.

The data was uploaded, annotated, and
published via the RADAR REST API. An external review step completed the publication process.

➡️ https://radar.kit.edu/radar/en/search?query=antscan

https://social.kit.edu/@KIT_Karlsruhe/116176855620080507

#researchdata #OpenScience #repository #rdm #FAIRdata