How about sources.sources? (Was: Question Regarding sources.list)
On 4/12/20, Chris Debian <csgdebian2020@gmail.com> wrote:
>
> I recently installed Debian Bullseye
>
> I am a complete beginner.
*heh!* You sound like me. That's about what I do.. Go for unstable as
a newbie. Live #LIFE large! :)
> My sources.list files is below:
>
> # See https://wiki.debian.org/SourcesList for more information.
> deb http://deb.debian.org/debian/ bullseye main
> deb-src http://deb.debian.org/debian/ bullseye main
>
> deb http://deb.debian.org/debian/ bullseye-updates main
> deb-src http://deb.debian.org/debian/ bullseye-updates main
>
> deb http://security.debian.org/debian-security/ bullseye-security main
> deb-src http://security.debian.org/debian-security/ bullseye-security main
I left that in for comparison. This is mine... except that mine is
instead created as:
/etc/apt/sources.list.d/sources.sources
DISCLAIMER: This format was originally found when something like "man
apt-get", "man apt", or "man sources.list" referenced a standalone
"man sources.sources" type deal. I can't find it just this second. I
didn't dream this up and sure don't cognitively function well enough
to have grasped what APPEARS to be describing it under "DEB822-STYLE
FORMAT" within "man sources.list".
The rest of the email now...
For this to work, you have to rename everything else (the files NOT
directories) or even delete anything else "*.list" because it doesn't
function otherwise (at least not for ME). For example, I leave my old
sources.list in place but change it to sourcesDOTlist. That's just as
a readily available fallback in case sources.sources ever starts
failing.
As of seconds ago, MY *newest* sources.sources file's contents are:
Types: deb deb-src
URIs: http://deb.debian.org/debian http://mirrors.namecheap.com/debian
Suites: bullseye
Components: main
Types: deb
URIs: http://distro.ibiblio.org/debian
Suites: bullseye
Components: main
Types: deb deb-src
URIs: http://security.debian.org/debian-security
Suites: bullseye-security
Components: main contrib non-free
The change I just made was to test drive having more than one
repository in a single line BECAUSE there's an "s" at the end of
"URIs" there. After update, things are perfect with the expected
result being the addition of appropriate new files showing up under
/var/lib/apt/lists. iBiblio has its own entry because it was failing
over deb-src for some reason.
Those don't specifically state "bullseye-updates" anywhere. I DO
remember addressing it somehow because I have "*-updates" in archived
sources.list files from various previous *suites*. Having just updated
115MB of Bullseye, SOME updates are still working just fine.
Comparing past DOTlist to present DOTsources, it looks like MY
bullseye-updates is now covered by that bullseye-security reference.
That sounds familiar'ish.
FOR ME, this layout/feature/technique didn't work pre-Bullseye.
Without exiting, rebooting, digging through other... suites.. yada, I
don't know if this is a new perk for Bullseye or needs tweaked
differently for past suites.
The fail I experienced might boil down to that necessary
bullseye-security v. bullseye-updates change. Maybe that does NOT
apply to previous suites.. or something?
My CHOICE to have "Components: main contrib non-free" for
bullseye-security "suite" is to cover my computer's... hm... just in
case I accidentally/incidentally install something not from main at
some point..
Whoever put this whole sources.sources take on this together, I LOVE
IT! Its layout is easier on my brain for comprehending it as a whole
those rare times I might need to change something. Very snazzy!
PS Easier ONCE you figure out its methodology, that is......... :)
PPS "#" comments didn't work for me previously. Just did a test drive,
and they're working fine now. FABULOUS because comments are handy for
e.g. having quick references to favorite repositories that aren't
being used at the moment.
PPPS Any outside 3rd party type packages that have been given
permission to set up their own DOTlist files... will potentially
complain that they can't find something or other yada. They're talking
about how you may or may not now (?) have to delete DOTlist files for
this TRICK (i.e. RADICAL.. COOL..) feature to work correctly.
Their data can be worked right into that same lineup within that same
single sources.sources file. Example:
Types: deb
URIs: https://deb.opera.com/opera-stable/
Suites: stable
Components: non-free
CAVEAT: You MIGHT or MIGHT NOT still have to work through granting
them permission via something like that curl/apt-key step. MAYBE. Time
and case-by-case usage will tell..
PS to that as I look at that block: IF you use Bullseye non-free, that
right there could possibly be combined into the same single block with
your Bullseye data. I only use Bullseye main so that won't work for my
own usage case.
Cindy :)
--
Cindy-Sue Causey
Talking Rock, Pickens County, Georgia, USA
* runs with birdseed *
Reply to: