I find it hard to see if I need an upgrade of my Peppermint or not. Below is the System info from my installation but I find no place where you list the Kernel/build version on the latest updated ISO. Why is this or am I just looking at all wrong places? Normally a file would say a version number?
Secondly, is an ISO update via a USB stick the only upgrade possibility? Can’t the Update Manager do an update like the one released 1st of July? Currently my update manager says that system is updated and on PepTools it just say
Checking Codeberg for updates
Applying updates
And then nothing more happens. Should it?
System info:
OS: PeppermintOS x86_64
Host: Surface Pro 4 124
Kernel: 5.10.0-23-amd64
Thanks
Dan
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Cavy is correct there is no need to rush the upgrade if all is working well unless you just want to. but I think to answer your question you can run in terminal lsb_release -a
That will display this
The reason for that is to show where you stand for the Debian release
The Release is the Debian base version
The Codename is the name of that release.
The above example... yes the system is running bullseye version11.7
That is how you can determine the exact version of your OS base
Hope that helps
Last edit: Peppermint OS 2023-07-10
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Anonymous
-
2023-07-09
Hi Dan, welcome to Planet Peppermint.
There is no immediate rush to upgrade your system, which is relatively straight forward, affair. In that you follow the Debian method: https://wiki.debian.org/DebianUpgrade to ensure all steps are correctly followed.
As when to edit the /etc/apt/sources.list and /etc/apt/sources.list.d/multimedia.list files, etc. Below is my sources.list from testing machine Bookworm when I upgraded on the 6th January this year.
# This system was installed using PeppermintOS removable media# (e.g. netinst, live or single CD). The matching "deb cdrom"# entries were removed at the end of the installation process.# For information about how to configure apt package sources,# see the sources.list(5) manual.# Main Repo - main contrib non-freedebhttp://deb.debian.org/debian/bookwormmaincontribnon-freenon-free-firmware#deb-src http://deb.debian.org/debian/ bookworm main contrib non-free non-free-firmware# Security Repo - main contrib non-freedebhttp://security.debian.org/bookworm-securitymaincontribnon-free#deb-src http://security.debian.org/ bookworm-security main contrib non-free# Updates Repo - main contrib non-freedebhttp://deb.debian.org/debianbookworm-updatesmaincontribnon-free#deb-src http://deb.debian.org/debian bookworm-updates main# Proposed Updates Repo - main contrib non-free#deb http://deb.debian.org/debian/ bookworm-proposed-updates main contrib non-free#deb-src http://deb.debian.org/debian/ bookworm-proposed-updates main contrib non-free# bookworm-backports, previously on backports.debian.orgdebhttp://deb.debian.org/debian/bookworm-backportsmaincontribnon-free
Following all upgrade instructions will upgrade your computer system from Bullseye to Bookworm, but it will not convert to the new Peppermint themed boot splash, our new branding image along with the new red, green and blue themes and icon sets. If you would like to have these items you will have install them yourself, from our repos. TBA soon.
The other thing to bear in mind it will break the Welcome screen and Pephub, we currently testing a script to repair manually upgraded machines. Presently the scripts are working, but fail to launch the either, but I'm able launch them via terminal command. It's back to the drawing board.
Also in tandem to this script we have tested a GUI upgrade tool for users who would rather not attempt a manual upgrade, again, there a minor bug to overcome. Once we solve this issue we will notify all members.
You can either wait for the GUI upgrade tool, or do a manual upgrade, then wait the repair script to fix the Weclome screen and Pephub. The choice is yours.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I have one, I am still testing it, it looks like this.
Basically you would put in bookworm.
Then it would set up all your sources to the repos.
And the start the upgrade via the terminal, You would still need to watch it, because this tool is more like a help you get started, with the standard debian upgrade.
As the upgrade progressed the "debian" upgrade does ask you many questions.
Then after all that upgrade is done, I have another tool to correct the Peptools...
Generally it works....but its not that easy gui tool that one would expect.
That is the reason I have not released this yet, as I am still refining things and looking at trying to make it more GUI friendly
Not much help to your question, but that is the sate of my progress, for the moment
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
So let's say it can't be used from "bullseye to bookworm"?
If this is the case, will it be necessary to update manually? But I guess something peppermint will be broken...
Last edit: Simone Zappa 2024-03-25
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Anonymous
-
2024-03-25
Hi Simone,
You are correct with your assumption that something breaks during the upgrade from Bullseye to Bookworm. It breaks the link to the Pep-Hub and Welcome and they no longer launch.
Instructions for a manual upgrade: https://wiki.debian.org/DebianUpgrade requires you to edit several system files, replacing bullseye with bookworm.
Your sources.list file should read as per this example below.
# This system was installed using PeppermintOS removable media# (e.g. netinst, live or single CD). The matching "deb cdrom"# entries were removed at the end of the installation process.# For information about how to configure apt package sources,# see the sources.list(5) manual.debhttp://deb.debian.org/debianbookwormmainnon-free-firmwaredeb-srchttp://deb.debian.org/debianbookwormmainnon-free-firmwaredebhttp://deb.debian.org/debian-security/bookworm-securitymainnon-free-firmwaredeb-srchttp://deb.debian.org/debian-security/bookworm-securitymainnon-free-firmwaredebhttp://deb.debian.org/debianbookworm-updatesmainnon-free-firmwaredeb-srchttp://deb.debian.org/debianbookworm-updatesmainnon-free-firmware
Depending on how confident you are to edit the necessary files via CLI (command line), open a terminal and type this command pkexec thunar and enter your password when prompted. This will open Thunar in root mode, now be diligent and carefully navigate to each file and edit them, with the necessary alterations and save these amendments.
/etc/apt/sources.list
/etc/apt/sources.list.d/multimedia.list
/etc/apt/sources.list.d/peppermint.list
Please read the instructions carefully or as my carpenter friend tells me, measure twice and cut once.
There is a rudimentary fix, for the Pephub and Welcome screen, where both can be launched by typing hub into a terminal and pressing enter will launch it. See screenshot, if interested I can send the necessary files to you.
I would like to communicate, that I tried to pass and bookworm, following: https://wiki.debian.org/DebianUpgrade
It was a disaster, the terminal command "hub" didn't work, the Grub was corrupt, it didn't allow me to see the other operating systems present.
I have always given "N" maintaining the default configurations, when requested from the terminal. Then with "Boot-repair" the Peppermint partition also disappeared (?)
I solved everything by going back to "Bullseye" and resetting everything and now it works. Luckily I had made a copy of the partition previously.
Bottom line: very bad experience with Debian...
I'll keep "Bullseye" for a while and then I'll see if I can leave peppermint permanently. Unless some automaticity takes over.
By the way, when will I get to keep "Bullseye" again?
When will support for "Bullseye" end?
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
/etc/apt $ lsb_release -a
Distributor ID: Peppermint
Description: PeppermintOS
Release: 11.7
Codename: bullseye
I could go either way...debian upgrade or clean install. Peppermint is installed on an older MacBook which is not my main machine. I've used it and like it, but have not tweaked it extensively. I'm leaning toward a clean install just to get everything. My main addition is NFS (Network File System) and I could get a record of everything else with dpkg -l > pkg_list Any thoughts, issues?
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
rayzer is on point....i am working on fixing the peppermint tools....
Although you can fix them manually. I should write a wiki for that process. thats a very minor thing
If you follow these steps: https://wiki.debian.org/DebianUpgrade
You will upgrade fine...infact that is what I did. So.... if you are not key on the "new branding" I would say just upgrade, that process does not bring in any of the new branding, I am not a fan of reinstalling unless I have big issues....LOL I myself prefer upgrades LOL
If you want the new themes and pep tools we can help you get those.
Just make sure to do a backup ;)
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
i did the upgrade a while back, it breaks some peppermint stuff but works fine otherwise. bookworm base has been solid so far, running it on 4 different installs across multiple distros.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I too prefer upgrades, but Peppermint-10 was minimally tweaked, so I did wipe & install. This went fine, but after restarting, the other distros on the Mac were not seen. In/etc/default/grub a line needs to be added: GRUB_DISABLE_OS_PROBER=false and then update-grubafter that all was well.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hi, i have a big problem. I had installed peppermintOS and all went smooth. It worked very good, until i hit the update button on the screen. The update wanted to change the kernel from linux-image-6.1.0-09-amd64 to linux-image-6.1.0-10-amd64. It had a negative message and i stopped the update process. now my package manager is defect, because it cant change automaticly.
I have some error messages for you:
It seems, it cant delete the new kernel, which is not installed. I am still on the old kernel.
I cant install new software, because synaptic first want to delete the new kernel and it stuck.
Commit Log for Mon Aug 7 11:11:51 2023
Die folgenden Pakete wurden entfernt:
linux-headers-6.1.0-10-amd64
linux-headers-amd64
linux-image-6.1.0-10-amd64
btw. this computer is no raspbery pi !
stefan@stefan-krux:~$ uname -a
Linux stefan-krux 6.1.0-9-amd64 #1 SMP PREEMPT_DYNAMIC Debian 6.1.27-1 (2023-05-08) x86_64 GNU/Linux
Intel(R) Core(TM) i7 CPU
No LSB modules are available.
Distributor ID: Peppermint
Description: PeppermintOS
Release: n/a
Codename: bookworm
Maybe someone has an idea, to fix this dpkg problem? That would be great, because i dont want to reinstall it again.
Stefan
Last edit: Stefan Z 2023-08-08
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hi,
I find it hard to see if I need an upgrade of my Peppermint or not. Below is the System info from my installation but I find no place where you list the Kernel/build version on the latest updated ISO. Why is this or am I just looking at all wrong places? Normally a file would say a version number?
Secondly, is an ISO update via a USB stick the only upgrade possibility? Can’t the Update Manager do an update like the one released 1st of July? Currently my update manager says that system is updated and on PepTools it just say
Checking Codeberg for updates
Applying updates
And then nothing more happens. Should it?
System info:
OS: PeppermintOS x86_64
Host: Surface Pro 4 124
Kernel: 5.10.0-23-amd64
Thanks
Dan
Cavy is correct there is no need to rush the upgrade if all is working well unless you just want to. but I think to answer your question you can run in terminal
lsb_release -aThat will display this
The reason for that is to show where you stand for the Debian release
The Release is the Debian base version
The Codename is the name of that release.
The above example... yes the system is running bullseye version11.7
That is how you can determine the exact version of your OS base
Hope that helps
Last edit: Peppermint OS 2023-07-10
Hi Dan, welcome to Planet Peppermint.
There is no immediate rush to upgrade your system, which is relatively straight forward, affair. In that you follow the Debian method: https://wiki.debian.org/DebianUpgrade to ensure all steps are correctly followed.
As when to edit the
/etc/apt/sources.listand/etc/apt/sources.list.d/multimedia.listfiles, etc. Below is my sources.list from testing machine Bookworm when I upgraded on the 6th January this year.Following all upgrade instructions will upgrade your computer system from Bullseye to Bookworm, but it will not convert to the new Peppermint themed boot splash, our new branding image along with the new red, green and blue themes and icon sets. If you would like to have these items you will have install them yourself, from our repos. TBA soon.
The other thing to bear in mind it will break the Welcome screen and Pephub, we currently testing a script to repair manually upgraded machines. Presently the scripts are working, but fail to launch the either, but I'm able launch them via terminal command. It's back to the drawing board.
Also in tandem to this script we have tested a GUI upgrade tool for users who would rather not attempt a manual upgrade, again, there a minor bug to overcome. Once we solve this issue we will notify all members.
You can either wait for the GUI upgrade tool, or do a manual upgrade, then wait the repair script to fix the Weclome screen and Pephub. The choice is yours.
Is there any news on "a GUI update tool" to allow upgrading from BullSeye to Bookworm?
I'm anxiously awaiting this.
I have one, I am still testing it, it looks like this.
Basically you would put in bookworm.
Then it would set up all your sources to the repos.
And the start the upgrade via the terminal, You would still need to watch it, because this tool is more like a help you get started, with the standard debian upgrade.
As the upgrade progressed the "debian" upgrade does ask you many questions.
Then after all that upgrade is done, I have another tool to correct the Peptools...
Generally it works....but its not that easy gui tool that one would expect.
That is the reason I have not released this yet, as I am still refining things and looking at trying to make it more GUI friendly
Not much help to your question, but that is the sate of my progress, for the moment
Is there any news?
not for immediate release, this has started to be built into the xDaily GUI.... that we working on for the up coming releases
So let's say it can't be used from "bullseye to bookworm"?
If this is the case, will it be necessary to update manually? But I guess something peppermint will be broken...
Last edit: Simone Zappa 2024-03-25
Hi Simone,
You are correct with your assumption that something breaks during the upgrade from Bullseye to Bookworm. It breaks the link to the Pep-Hub and Welcome and they no longer launch.
Instructions for a manual upgrade: https://wiki.debian.org/DebianUpgrade requires you to edit several system files, replacing
bullseyewithbookworm.Your sources.list file should read as per this example below.
Depending on how confident you are to edit the necessary files via CLI (command line), open a terminal and type this command
pkexec thunarand enter your password when prompted. This will open Thunar in root mode, now be diligent and carefully navigate to each file and edit them, with the necessary alterations and save these amendments./etc/apt/sources.list/etc/apt/sources.list.d/multimedia.list/etc/apt/sources.list.d/peppermint.listPlease read the instructions carefully or as my carpenter friend tells me, measure twice and cut once.
There is a rudimentary fix, for the Pephub and Welcome screen, where both can be launched by typing
hubinto a terminal and pressing enter will launch it. See screenshot, if interested I can send the necessary files to you.I would like to communicate, that I tried to pass and bookworm, following:
https://wiki.debian.org/DebianUpgrade
It was a disaster, the terminal command "hub" didn't work, the Grub was corrupt, it didn't allow me to see the other operating systems present.
I have always given "N" maintaining the default configurations, when requested from the terminal. Then with "Boot-repair" the Peppermint partition also disappeared (?)
I solved everything by going back to "Bullseye" and resetting everything and now it works. Luckily I had made a copy of the partition previously.
Bottom line: very bad experience with Debian...
I'll keep "Bullseye" for a while and then I'll see if I can leave peppermint permanently. Unless some automaticity takes over.
By the way, when will I get to keep "Bullseye" again?
When will support for "Bullseye" end?
/etc/apt $ lsb_release -aDistributor ID: Peppermint
Description: PeppermintOS
Release: 11.7
Codename: bullseye
I could go either way...debian upgrade or clean install. Peppermint is installed on an older MacBook which is not my main machine. I've used it and like it, but have not tweaked it extensively. I'm leaning toward a clean install just to get everything. My main addition is NFS (Network File System) and I could get a record of everything else with
dpkg -l > pkg_listAny thoughts, issues?rayzer is on point....i am working on fixing the peppermint tools....
Although you can fix them manually. I should write a wiki for that process. thats a very minor thing
If you follow these steps:
https://wiki.debian.org/DebianUpgrade
You will upgrade fine...infact that is what I did. So.... if you are not key on the "new branding" I would say just upgrade, that process does not bring in any of the new branding, I am not a fan of reinstalling unless I have big issues....LOL I myself prefer upgrades LOL
If you want the new themes and pep tools we can help you get those.
Just make sure to do a backup ;)
i did the upgrade a while back, it breaks some peppermint stuff but works fine otherwise. bookworm base has been solid so far, running it on 4 different installs across multiple distros.
I too prefer upgrades, but Peppermint-10 was minimally tweaked, so I did wipe & install. This went fine, but after restarting, the other distros on the Mac were not seen. In
/etc/default/gruba line needs to be added:GRUB_DISABLE_OS_PROBER=falseand thenupdate-grubafter that all was well.Hi, i have a big problem. I had installed peppermintOS and all went smooth. It worked very good, until i hit the update button on the screen. The update wanted to change the kernel from linux-image-6.1.0-09-amd64 to linux-image-6.1.0-10-amd64. It had a negative message and i stopped the update process. now my package manager is defect, because it cant change automaticly.
I have some error messages for you:
It seems, it cant delete the new kernel, which is not installed. I am still on the old kernel.
I cant install new software, because synaptic first want to delete the new kernel and it stuck.
Commit Log for Mon Aug 7 11:11:51 2023
Die folgenden Pakete wurden entfernt:
linux-headers-6.1.0-10-amd64
linux-headers-amd64
linux-image-6.1.0-10-amd64
Stefan
Stefan - This should correct your issue.
https://sourceforge.net/p/peppermintos/pil/11/
If you have any questions let us know
btw. this computer is no raspbery pi !
stefan@stefan-krux:~$ uname -a
Linux stefan-krux 6.1.0-9-amd64 #1 SMP PREEMPT_DYNAMIC Debian 6.1.27-1 (2023-05-08) x86_64 GNU/Linux
Intel(R) Core(TM) i7 CPU
No LSB modules are available.
Distributor ID: Peppermint
Description: PeppermintOS
Release: n/a
Codename: bookworm
Maybe someone has an idea, to fix this dpkg problem? That would be great, because i dont want to reinstall it again.
Stefan
Last edit: Stefan Z 2023-08-08