Scheduled Maintenance: We are aware of an issue with Google, AOL, and Yahoo services as email providers which are blocking new registrations. We are trying to fix the issue and we have several internal and external support tickets in process to resolve the issue. Please see: viewtopic.php?t=158230
Hallvor wrote: ↑2023-06-06 11:56
Yes, to be clear: Everyone should carefully read the release notes linked in the second post above. It is not a massive text, and it contains lots of useful info on how the system works.
The Debian developers are true masters of flawless dist-upgrades, but even masters need a helping hand if you have done special configurations to your system.
Speaking of which, we are working on the press release now. For those who have read the entire release notes, is there anything you think should be added to the press release?
While most people will read the release notes, a lot will not, the press release informs everyone of some of the major changes...which makes more people read the actual release notes. So is there anything critical that any of you think should be added? Bear in mind the press release is just a quick summary not a lot of detail.
"The advice given above is all good, and just because a new message has appeared it does not mean that a problem has arisen, just that a new gremlin hiding in the hardware has been exposed." - FreewheelinFrank
I *believe* both are valid. Out of curiosity I did try both ways and for that cursory glance saw no immediate difference. The '*' is there for pattern matching which may be why it is recommended.
sunrat wrote: ↑2023-06-06 23:04
Also noted a couple of typos:
bookwoorm - several times
immeidate
Thank you, and with due credit of course:
announcements master c83200b Donald Norwood en/drafts/bookworm-release.wml * typo corrections care of sunrat @ forums.d.o * https://deb.li/oxM4
Typo perfectionish.
"The advice given above is all good, and just because a new message has appeared it does not mean that a problem has arisen, just that a new gremlin hiding in the hardware has been exposed." - FreewheelinFrank
dpkg-query -l '*' is different from dpkg-query -l. It seems to add packages that are provided or replaced by installed packages (Provides: and Replaces: fields in the package description) with Desired action: u (Unknown) Package status: n (Not-installed).
I can't see any difference between dpkg --get-selections '*' and dpkg --get-selections. Probably the behavior has changed since it has been documented.
However, it is still documented as such in man 1 dpkg:
--get-selections [package-name-pattern...]
Get list of package selections, and write it to stdout. Without a pattern, non-installed packages (i.e. those which have been previously purged) will not be shown.
I'm not even sure that it was well documented as the behavior we can witness in dpkg-query has nothing to do with purged packages (and, to my knowledge, there is no database of purged packages).
Hallvor wrote: ↑2023-06-06 11:56
Yes, to be clear: Everyone should carefully read the release notes linked in the second post above. It is not a massive text, and it contains lots of useful info on how the system works.
fabien wrote: ↑2023-06-07 10:49
(and, to my knowledge, there is no database of purged packages).
I haven't checked, but there are "residual configurations" that show as "deinstall" in the "selections" list. I'd already built this into my herder.tk! The '*' will filter those I believe.
Also in mind is the status change of the repository from testing to stable (and also stable to old-stable) has in the past caused synaptic to error. That seems to be fixed.
#> dpkg --get-selections '*' | grep "^vrms"
vrms install
#> dpkg -l '*' | grep "vrms"
ii vrms 1.27 all virtual Richard M. Stallman
#> apt -V remove vrms
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
The following packages will be REMOVED:
vrms (1.27)
0 upgraded, 0 newly installed, 1 to remove and 0 not upgraded.
After this operation, 44.0 kB disk space will be freed.
Do you want to continue? [Y/n]
(Reading database ... 183883 files and directories currently installed.)
Removing vrms (1.27) ...
Processing triggers for man-db (2.9.4-2) ...
#> dpkg --get-selections '*' | grep "^vrms"
vrms deinstall
#> dpkg -l '*' | grep "vrms"
rc vrms 1.27 all virtual Richard M. Stallman
#> apt -V purge vrms
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
The following packages will be REMOVED:
vrms* (1.27)
0 upgraded, 0 newly installed, 1 to remove and 0 not upgraded.
After this operation, 0 B of additional disk space will be used.
Do you want to continue? [Y/n]
(Reading database ... 183873 files and directories currently installed.)
Purging configuration files for vrms (1.27) ...
#> dpkg --get-selections '*' | grep "deinstall$"
#> dpkg --get-selections | grep "deinstall$"
#> dpkg -l '*' | grep "vrms"
#> dpkg-query -l '*' | grep "vrms"
#> dpkg --get-selections '*' | grep "^rc"
#> dpkg-query -l '*' | grep "^rc"
#> dpkg -l '*' | mawk 'NR>5{if (!/^ii|^un/){print}}' ### lines not starting with "ii" or "un"
It is recommended to purge all remaining configuration files before upgrading to a new version of Debian.
dpkg-query -l '*' is different from dpkg-query -l. It seems to add packages that are provided or replaced by installed packages (Provides: and Replaces: fields in the package description) with Desired action: u (Unknown) Package status: n (Not-installed).
I can't see any difference between dpkg --get-selections '*' and dpkg --get-selections. Probably the behavior has changed since it has been documented.
However, it is still documented as such in man 1 dpkg:
--get-selections [package-name-pattern...]
Get list of package selections, and write it to stdout. Without a pattern, non-installed packages (i.e. those which have been previously purged) will not be shown.
I'm not even sure that it was well documented as the behavior we can witness in dpkg-query has nothing to do with purged packages (and, to my knowledge, there is no database of purged packages).
Great catch. Cannot believe how old that bug report is.
Typo perfectionish.
"The advice given above is all good, and just because a new message has appeared it does not mean that a problem has arisen, just that a new gremlin hiding in the hardware has been exposed." - FreewheelinFrank
urdrwho10 wrote: ↑2023-06-02 13:10
Hm? I think back when I used Mint it was easier to upgrade. Such as "Launch the System Upgrade by clicking on “Edit->Upgrade to Linux Mint 21.1 Vera”.
Debian has to have an easier way then manually reading multiple chapters of Upgrades from Debian 11. I'm in a mode of trying to simplify all things in life.
N: Repository 'Debian bookworm' changed its 'non-free component' value from 'non-free' to 'non-free non-free-firmware'
N: More information about this can be found online in the Release notes at: https://www.debian.org/releases/bookworm/amd64/release-notes/ch-information.html#non-free-split
We need change in apt sources the value "non-free" to "non-free-firmware"?
N: Repository 'Debian bookworm' changed its 'non-free component' value from 'non-free' to 'non-free non-free-firmware'
N: More information about this can be found online in the Release notes at: https://www.debian.org/releases/bookworm/amd64/release-notes/ch-information.html#non-free-split
We need change in apt sources the value "non-free" to "non-free-firmware"?
Did you read the Release notes? It is explained there.
Basically, non-free firmware is moved to non-free-firmware. Other non-free software such as nvidia-driver is still in non-free.
“ computer users can be divided into 2 categories:
Those who have lost data
...and those who have not lost data YET ”Remember toBACKUP!
N: Repository 'Debian bookworm' changed its 'non-free component' value from 'non-free' to 'non-free non-free-firmware'
N: More information about this can be found online in the Release notes at: https://www.debian.org/releases/bookworm/amd64/release-notes/ch-information.html#non-free-split
We need change in apt sources the value "non-free" to "non-free-firmware"?
Did you read the Release notes? It is explained there.
Basically, non-free firmware is moved to non-free-firmware. Other non-free software such as nvidia-driver is still in non-free.
I saw it, but I didn't see that difference on the nvidia in non-free and the new ones. When upgrading, I did not get this notification and did not make the change. I got the notification a few hours later.
techsavvy wrote: ↑2023-06-12 00:25
"non-free-firmware" doesn't work on a Pi3B+ upgrade, so one should retain "non-free" on that hardware.
So from what I gather, for one hardware it should be "non-free-firmware" and for other hardware "non-free" as above.
In my case, I use amd, both for cpu and gpu, after the notice to add "-firmware" and do an update, amd firmware updated.