Re: Upgrading to Bullseye?
On 5/27/21, Greg Wooledge <greg@wooledge.org> wrote:
> On Thu, May 27, 2021 at 08:30:16AM -0700, latincom wrote:
>> Thank you
>>
>> Here is the mistake:
>>
>> deb http://security.debian.org/debian-security bullseye-security main
>> contrib non-free
>>
>> deb http://security.debian.org/debian-security buster/updates main
>> contrib
>> non-free
>
> Yes, the format for the security line is changing in bullseye. The new
> format should be less confusing (no more "is it foo-updates or foo/updates"
> questions) in the long run, but there will obviously be some initial
> confusion during the transition.
Speaking of Bullseye and transitions, "man sources.list" is now again
listing dot sources files. It did so a while back just long enough for
me to stumble on it then the extended reference seemed to disappear.
Today's "man sources.list" has two references under the
"SOURCES.LIST.D" and "DEB822-STYLE FORMAT" headings.
One caveat is that third party vendors will need to be advised on how
to sniff out a User's CHOICE toward that format. They will need to
adjust what they do accordingly. Once they figure it out the first
time, it's not an ongoing changing deal. It's just going to take them
adding one or more additional lines of code that have a checkpoint for
dot sources files.
Warnings about duplicate entries for any package after a User updates
apt or apt-get is the sign that tweak needs addressed by the TRUSTED
outside/third party vendor. That complaint will occur because the
vendor doesn't know to sniff the User's dot sources file(s) for their
own repositories in the same way vendors already take a poke at our
longstanding dot list files (based on personal experience).
Cindy :)
--
Cindy-Sue Causey
Talking Rock, Pickens County, Georgia, USA
* runs with birdseed *
Reply to: