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
Jessie to Stretch upgrade
Jessie to Stretch upgrade
Few days ago I upgraded Jessie to Stretch.I do not have any problems and everything is running smoothly. Before upgrading I had my system updated and I did not have any extra repos enabled.I had only google chrome and I disabled it before upgrading.In synaptics I did not have a single (local or obsolete) package. However after upgrading I have some packages in the obsolete section.I am not sure about removing them if safe or not.Since I have not installed anything from outside and I did not have any of those before upgrading is it safe to remove them?
Re: Jessie to Stretch upgrade
ceylan@debian-~$ aptitude search '~o'
i A alsa-base - dummy package to ease purging of obsolete
i A cpp-4.8 - GNU C preprocessor
i A cpp-4.9 - GNU C preprocessor
i A gcc-4.8 - GNU C compiler
i gcc-4.8-base - GCC, the GNU Compiler Collection (base pac
i A gcc-4.9 - GNU C compiler
i gcc-4.9-base - GCC, the GNU Compiler Collection (base pac
i libapt-inst1.5 - deb package format runtime library
i libapt-pkg4.12 - package management runtime library
i A libasan0 - AddressSanitizer -- a fast memory error de
i A libasan1 - AddressSanitizer -- a fast memory error de
i libboost-iostreams1.55.0 - Boost.Iostreams Library
i libdns-export100 - Exported DNS Shared Library
i A libgcc-4.8-dev - GCC support library (development files)
i A libgcc-4.9-dev - GCC support library (development files)
i libgnutls-deb0-28 - GNU TLS library - main runtime library
i libhogweed2 - low level cryptographic library (public-ke
i libicu52 - International Components for Unicode
i libirs-export91 - Exported IRS Shared Library
i libisc-export95 - Exported ISC Shared Library
i libisccfg-export90 - Exported ISC CFG Shared Library
i A libisl10 - manipulating sets and relations of integer
i libjson-c2 - JSON manipulation library - shared library
i liblognorm1 - Log normalizing library
i libnettle4 - low level cryptographic library (symmetric
i libprocps3 - library for accessing process information
i libpsl0 - Library for Public Suffix List (shared lib
i libreadline6 - GNU readline and history libraries, run-ti
i libssl1.0.0 - Secure Sockets Layer toolkit - shared libr
i A libtxc-dxtn-s2tc0 - Texture compression library for Mesa
i libxtables10 - netfilter xtables library
i A python-gtkspell - Python bindings for the GtkSpell library
i python-reportbug - Python modules for interacting with bug tr
i python-support - automated rebuilding support for Python mo
ceylan@debian-$
i A alsa-base - dummy package to ease purging of obsolete
i A cpp-4.8 - GNU C preprocessor
i A cpp-4.9 - GNU C preprocessor
i A gcc-4.8 - GNU C compiler
i gcc-4.8-base - GCC, the GNU Compiler Collection (base pac
i A gcc-4.9 - GNU C compiler
i gcc-4.9-base - GCC, the GNU Compiler Collection (base pac
i libapt-inst1.5 - deb package format runtime library
i libapt-pkg4.12 - package management runtime library
i A libasan0 - AddressSanitizer -- a fast memory error de
i A libasan1 - AddressSanitizer -- a fast memory error de
i libboost-iostreams1.55.0 - Boost.Iostreams Library
i libdns-export100 - Exported DNS Shared Library
i A libgcc-4.8-dev - GCC support library (development files)
i A libgcc-4.9-dev - GCC support library (development files)
i libgnutls-deb0-28 - GNU TLS library - main runtime library
i libhogweed2 - low level cryptographic library (public-ke
i libicu52 - International Components for Unicode
i libirs-export91 - Exported IRS Shared Library
i libisc-export95 - Exported ISC Shared Library
i libisccfg-export90 - Exported ISC CFG Shared Library
i A libisl10 - manipulating sets and relations of integer
i libjson-c2 - JSON manipulation library - shared library
i liblognorm1 - Log normalizing library
i libnettle4 - low level cryptographic library (symmetric
i libprocps3 - library for accessing process information
i libpsl0 - Library for Public Suffix List (shared lib
i libreadline6 - GNU readline and history libraries, run-ti
i libssl1.0.0 - Secure Sockets Layer toolkit - shared libr
i A libtxc-dxtn-s2tc0 - Texture compression library for Mesa
i libxtables10 - netfilter xtables library
i A python-gtkspell - Python bindings for the GtkSpell library
i python-reportbug - Python modules for interacting with bug tr
i python-support - automated rebuilding support for Python mo
ceylan@debian-$
Re: Jessie to Stretch upgrade
Try it will only remove packages not needed any longer.
Code: Select all
sudo apt-get autoremove
-
- Posts: 1454
- Joined: 2015-08-30 20:14
Re: Jessie to Stretch upgrade
If you don't have sudo enabled, login as root and type:
in terminal.
Code: Select all
apt-get install -f
Re: Jessie to Stretch upgrade
Giving the above command result is:
Reading package lists... Done
Building dependency tree
Reading state information... Done
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
Reading package lists... Done
Building dependency tree
Reading state information... Done
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
Re: Jessie to Stretch upgrade
From your list of packages, I picked the ones with a name that does not end in a number, i.e., ‘alsa-base’, ‘python-gtkspell’, ‘python-reportbug’, ‘python-support’.
Here’s what the ‘apt-cache’ command has to say about them (on my Debian Testing system):
From this output, I conclude that ‘python-reportbug’ is no longer present in the Debian repositories, and that it can be safely purged.
The other three—‘alsa-base’, ‘python-gtkspell’, and ‘python-support’—are “purely virtual”. In other words, they do not exist as actual packages, but they merely define a logical name, representing a function that other packages may provide. If they are considered “obsolete”, then none of your installed packages will provide their function, and they should be safe to purge as well.
If I were you, I would try to purge these packages—e.g.:This command should not mark any other packages for deletion, and it should therefore purge the packages without further ado. (Should the command ever want to purge any further packages, then it will ask you for confirmation—and the safe answer would then be “N”. It would, however, be strange if this were to happen in this case.)
If you want to be absolutely sure that nothing bad will happen to your system, then you may attempt a “dry run” first:This command will tell you what it wants to do, but it won’t take any real action.
The package names that end in a number are probably replaced with new ones that end in a higher number. For instance, on my system:You will probably get both ‘libhogweed2’ and ‘libhogweed4’ on your system, and you can then safely purge the ‘libhogweed2’ package—and similarly for the other packages that are marked “obsolete”.
Here’s what the ‘apt-cache’ command has to say about them (on my Debian Testing system):
Code: Select all
$ apt-cache show 'alsa-base' 'python-gtkspell' 'python-reportbug' 'python-support'
N: Can't select versions from package 'alsa-base' as it is purely virtual
N: Can't select versions from package 'python-gtkspell' as it is purely virtual
N: Unable to locate package python-reportbug
N: Can't select versions from package 'python-support' as it is purely virtual
N: No packages found
The other three—‘alsa-base’, ‘python-gtkspell’, and ‘python-support’—are “purely virtual”. In other words, they do not exist as actual packages, but they merely define a logical name, representing a function that other packages may provide. If they are considered “obsolete”, then none of your installed packages will provide their function, and they should be safe to purge as well.
If I were you, I would try to purge these packages—e.g.:
Code: Select all
# apt-get purge 'alsa-base' 'python-gtkspell' 'python-reportbug' 'python-support'
If you want to be absolutely sure that nothing bad will happen to your system, then you may attempt a “dry run” first:
Code: Select all
# apt-get --dry-run purge 'alsa-base' 'python-gtkspell' 'python-reportbug' 'python-support'
The package names that end in a number are probably replaced with new ones that end in a higher number. For instance, on my system:
Code: Select all
apt-cache pkgnames 'libhogweed'
libhogweed4
Last edited by luvr on 2017-08-11 14:31, edited 2 times in total.
- None1975
- df -h | participant
- Posts: 1404
- Joined: 2015-11-29 18:23
- Location: Russia, Kaliningrad
- Has thanked: 46 times
- Been thanked: 70 times
Re: Jessie to Stretch upgrade
Did you try? The following command displays a list of all removed packages that may have configuration files left on the system (if any). By the way, it is look like dummy packages....
Code: Select all
# dpkg -l | awk '/^rc/ { print $2 }'
OS: Debian 12.4 Bookworm / DE: Enlightenment
Debian Wiki | DontBreakDebian, My config files on github
Debian Wiki | DontBreakDebian, My config files on github
Re: Jessie to Stretch upgrade
i libdns-export100 - Exported DNS Shared Library
i libirs-export91 - Exported IRS Shared Library
i libisc-export95 - Exported ISC Shared Library
i libisccfg-export90 - Exported ISC CFG Shared Library
i A libtxc-dxtn-s2tc0 - Texture compression library for Mesa
After removing other packages(which had newer versions) These are the only ones left in the obsolete area
i libirs-export91 - Exported IRS Shared Library
i libisc-export95 - Exported ISC Shared Library
i libisccfg-export90 - Exported ISC CFG Shared Library
i A libtxc-dxtn-s2tc0 - Texture compression library for Mesa
After removing other packages(which had newer versions) These are the only ones left in the obsolete area
Re: Jessie to Stretch upgrade
Exactly how much of your life are you willing to waste on this?
Surely you have something more consequential to worry about. (And if not, maybe consider volunteering in the pediatric ward of your local hospital.)
Surely you have something more consequential to worry about. (And if not, maybe consider volunteering in the pediatric ward of your local hospital.)
Re: Jessie to Stretch upgrade
If you go to the Debian package search site you could look up those packages. If you did you would see that the first four are not part of Stretch and the last, libtxc-dxtn-s2tc0 is a virtual package provided by: libtxc-dxtn-s2tc in Stretch.ceylan wrote:After removing other packages(which had newer versions) These are the only ones left in the obsolete area
Most of those packages are less than one megabyte. dasein's point about how much time do you want to use to save a couple of Megs on your system does make sense these days when modern systems generally have multiple Gigs of free space and you state that your system is running well. Nothing wrong with wanting to do housekeeping on your system as long as you aren't trying to get someone else to figure it out for you.
Re: Jessie to Stretch upgrade
Thanks for all the answers,But one last thing: libtxc-dxtn-s2tc is not installed.
Re: Jessie to Stretch upgrade
In that case, since your system doesn't need libtxc-dxtn-s2t in Stretch, it would seem logical that you also don't need the libtxc-dxtn-s2tc0 that was left over from your Jessie install. I think you could have figured that out for yourself.ceylan wrote:Thanks for all the answers,But one last thing: libtxc-dxtn-s2tc is not installed.
Re: Jessie to Stretch upgrade
Or, alternatively, you could run apt-cache policy on them:Thorny wrote:If you go to the Debian package search site you could look up those packages.
Code: Select all
$ apt-cache policy PACKAGE-NAME
I once took such a detailed look at the list of packages that had become obsolete, or about which the apt logs had recorded some weird message, after I migrated my system from Debian stable to testing. Though such an action isn’t in any way critical, I did find it quite instructive at the time.Nothing wrong with wanting to do housekeeping on your system as long as you aren't trying to get someone else to figure it out for you.
Re: Jessie to Stretch upgrade
Sure, there are other alternate ways too. If you have aptitude installed you could query it for "why" regarding a specific package, for example. Another topic you might investigate.ceylan wrote:I am learning a lot.Thank you.I was afraid to break the system.
Make sure you keep a good backup of your system, you need to protect any data you would not want to lose and make sure you know how to restore it. Then if you break your system by trying something while you are learning, you are protected. This has never been optional advice, it's just that many treat it so.
Re: Jessie to Stretch upgrade
Nicely said.Thorny wrote:This has never been optional advice, it's just that many treat it so.
Re: Jessie to Stretch upgrade
I backup my system every week .It is not for software but hardware can fail too