Advertising

Author Topic: I decided to upgrade to buster  (Read 1229 times)

Offline penguin

  • Full Member
  • ***
  • Posts: 119
I decided to upgrade to buster
« on: April 25, 2019, 10:22:54 pm »
I decided to upgrade to buster (from my stable XFCE Sparky 4.9 Tyche)

Based on this :
Code: [Select]
https://jjasghar.github.io/blog/2018/08/07/updating-debian-from-stretch-to-buster/
Quote
apt-get update
apt-get upgrade
apt-get dist-upgrade

Next, convert the sources.list from stretch to buster.

sed -i 's/stretch/buster/g' /etc/apt/sources.list
Update the apt cache with the new sources.

apt-get update
Update the machine fully:

apt-get upgrade
apt-get dist-upgrade
Verify that the update has succeeded:

cat /etc/debian_version
buster/sid
I’d reboot now to make sure everything comes up as expected.


Every thing went  fine :

But Sparky on the reboot applied an update and Aptus is not more available

I tried to update and get this error

Quote
sudo apt-get update
Hit:1 http://www.deb-multimedia.org buster InRelease
Hit:2 http://ftp.debian.org/debian buster InRelease                           
Hit:3 http://security.debian.org buster/updates InRelease                     
Hit:4 https://deb.opera.com/opera-stable stable InRelease                     
Hit:5 http://sparkylinux.org/repo unstable InRelease                           
Hit:6 https://download.mono-project.com/repo/debian stable-stretch InRelease   
Hit:7 https://repo.skype.com/deb stable InRelease                             
Get:8 https://mega.nz/linux/MEGAsync/Debian_9.0 ./ InRelease [1,480 B]
Err:5 http://sparkylinux.org/repo unstable InRelease
  The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 1CE63BD7D117204E
Fetched 1,480 B in 1s (1,419 B/s)
Reading package lists... Done
W: An error occurred during the signature verification. The repository is not updated and the previous index files will be used. GPG error: http://sparkylinux.org/repo unstable InRelease: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 1CE63BD7D117204E
W: Failed to fetch http://sparkylinux.org/repo/dists/unstable/InRelease  The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 1CE63BD7D117204E
W: Some index files failed to download. They have been ignored, or old ones used instead.
 


Should I remove
Quote
https://download.mono-project.com/repo/debian stable-stretch InRelease

Is this still valid the follow explanation?

Code: [Select]
https://sparkylinux.org/wiki/doku.php/repository_testing
Quote
Sparky repositories of the testing line
Sparky of the testing (rolling) line is based on and uses Debian “testing” packages.

Repository
Users of Debian “testing” branch should add Sparky testing and core repositories to get access to Sparky repos:

 sudo nano /etc/apt/sources.list.d/sparky-testing.list
and paste into the file:

 deb https://sparkylinux.org/repo testing main
 deb-src https://sparkylinux.org/repo testing main
 deb https://sparkylinux.org/repo core main
 deb-src https://sparkylinux.org/repo core main
Sparky unstable repository (optional):

 sudo nano /etc/apt/sources.list.d/sparky-unstable.list
and paste into the file:

 deb https://sparkylinux.org/repo unstable main
 deb-src https://sparkylinux.org/repo unstable main
Create a preference file:

 sudo nano /etc/apt/preferences.d/sparky
and paste into the file:

 Package: *
 Pin: release o=SparkyLinux
 Pin-Priority: 1001
Otherwise, install 'sparky-apt' 5.x package to do so.

Public key
Download the Sparky's Public Key as a “deb” package from:

https://sparkylinux.org/repo/pool/main/s/sparky-keyring/

Then install it:

 sudo dpkg -i /path/to/sparky-keyring_VERSION_all.deb
 sudo apt-get update
or get the key manually ('wget2' has to be installed):

 wget2 -O - https://sparkylinux.org/repo/sparkylinux.gpg.key | sudo apt-key add -

pavroo please, can You assist ?
« Last Edit: April 25, 2019, 11:13:37 pm by penguin »

Offline penguin

  • Full Member
  • ***
  • Posts: 119
Re: I decided to upgrade to buster
« Reply #1 on: April 25, 2019, 11:12:25 pm »
As described I installed sparky public key
Quote
Public key
Download the Sparky's Public Key as a “deb” package from:

https://sparkylinux.org/repo/pool/main/s/sparky-keyring/

Then install it:

 sudo dpkg -i /path/to/sparky-keyring_VERSION_all.deb
 sudo apt-get update

I downloaded deb keys and installed manually(i used * because sparky-keyring_VERSION_all.deb is different form sparky-keyring_20170602_all.deb) and get the follow error:

Quote
sudo dpkg -i *.deb
Selecting previously unselected package sparky-keyring.
(Reading database ... 341968 files and directories currently installed.)
Preparing to unpack sparky-keyring_20170602_all.deb ...
Unpacking sparky-keyring (20170602) ...
Setting up sparky-keyring (20170602) ...
Warning: The postinst maintainerscript of the package sparky-keyring
Warning: seems to use apt-key (provided by apt) without depending on gnupg or gnupg2.
Warning: This will BREAK in the future and should be fixed by the package maintainer(s).
Note: Check first if apt-key functionality is needed at all - it probably isn't!
Warning: apt-key should not be used in scripts (called from postinst maintainerscript of the package sparky-keyring)
OK

Now when I use sudo apt-get update I stuck on this :

Code: [Select]
sudo apt-get update
Hit:1 http://security.debian.org buster/updates InRelease
Hit:2 http://www.deb-multimedia.org buster InRelease                           
Hit:3 http://ftp.debian.org/debian buster InRelease                           
Hit:4 http://sparkylinux.org/repo unstable InRelease                           
Hit:5 https://deb.opera.com/opera-stable stable InRelease                     
Hit:6 https://repo.skype.com/deb stable InRelease                             
Hit:7 https://download.mono-project.com/repo/debian stable-stretch InRelease   
Get:8 https://mega.nz/linux/MEGAsync/Debian_9.0 ./ InRelease [1,480 B]
Fetched 1,480 B in 1s (1,239 B/s)   
Reading package lists... Done
Reading package lists... Done
Building dependency tree       
Reading state information... Done
Calculating upgrade... Done
The following packages will be REMOVED:
  sparky-grub-theme
0 upgraded, 0 newly installed, 1 to remove and 0 not upgraded.
1 not fully installed or removed.
After this operation, 65.5 kB disk space will be freed.
Do you want to continue? [Y/n] y
(Reading database ... 341970 files and directories currently installed.)
Removing sparky-grub-theme (0.1.4) ...
Generating grub configuration file ...
Found background image: /usr/share/images/desktop-base/desktop-grub.png
Found background image: /usr/share/images/desktop-base/desktop-grub.png
Found linux image: /boot/vmlinuz-4.19.0-4-amd64
Found initrd image: /boot/initrd.img-4.19.0-4-amd64
Found linux image: /boot/vmlinuz-4.9.0-8-amd64
Found initrd image: /boot/initrd.img-4.9.0-8-amd64
/etc/grub.d/bin/grubcfg_proxy: error while loading shared libraries: libcrypto.so.1.0.0: cannot open shared object file: No such file or directory
dpkg: error processing package sparky-grub-theme (--remove):
 installed sparky-grub-theme package post-removal script subprocess returned error exit status 127
Errors were encountered while processing:
 sparky-grub-theme
E: Sub-process /usr/bin/dpkg returned an error code (1)
« Last Edit: April 26, 2019, 02:15:37 pm by pavroo »

Offline paxmark1

  • Hero Member
  • *****
  • Posts: 602
Re: I decided to upgrade to buster
« Reply #2 on: April 26, 2019, 12:12:38 am »
The https://jjasghar.github.io/blog/2018/08/07/updating-debian-from-stretch-to-buster/    seems to be a decent source of information.  It is Debian specific, but should get the entire Debian portion to Buster.  keys - I leave to others.

I am biased, as my sig implies.  You do have a lot of ppa's, probably in etc/apt/sources.list.d/   
For others going from stable to buster I would recommend commenting out all ppa's that do not originate from Sparky.  You are not getting rid of them, just putting a "#" in front of it.   You can re-enable those ppas by removing the # once you have gone from stable to buster.  You can do that one at a time to see which ones have problems.   

NOTE:  ppas that are specifically for Ubuntu very often can cause problems in a dist-upgrade   

Of course again try in terminal   "sudo apt-get update"  "sudo apt-get upgrade"   and "sudo dpkg --configure -a"   Or the apt versions if you prefer apt.

Thanks for kicking the tires and finding bugs.  Others should have more info.     peace out. 

Don't make a FrankenDebian

Offline pavroo

  • Global Moderator
  • Hero Member
  • *****
  • Posts: 2027
    • SparkyLinux
Re: I decided to upgrade to buster
« Reply #3 on: April 26, 2019, 02:18:25 pm »
Looks like you have Debian buster repos enabled ok, but not enabled Sparky testing repos.
You should install 'sparky-apt' & 'sparky5-apt' packages.
Check here:
https://sparkylinux.org/wiki/doku.php/repository_testing

And, to paste a terminal output use code not quote button.
« Last Edit: April 26, 2019, 02:20:04 pm by pavroo »
Nothing is easy as it looks. Danielle Steel
Join #sparkylinux at irc.freenode.net

Offline penguin

  • Full Member
  • ***
  • Posts: 119
Re: I decided to upgrade to buster
« Reply #4 on: April 26, 2019, 05:09:53 pm »
The https://jjasghar.github.io/blog/2018/08/07/updating-debian-from-stretch-to-buster/    seems to be a decent source of information.  It is Debian specific, but should get the entire Debian portion to Buster.  keys - I leave to others.

I am biased, as my sig implies.  You do have a lot of ppa's, probably in etc/apt/sources.list.d/   
For others going from stable to buster I would recommend commenting out all ppa's that do not originate from Sparky.  You are not getting rid of them, just putting a "#" in front of it.   You can re-enable those ppas by removing the # once you have gone from stable to buster.  You can do that one at a time to see which ones have problems.   

NOTE:  ppas that are specifically for Ubuntu very often can cause problems in a dist-upgrade   

Of course again try in terminal   "sudo apt-get update"  "sudo apt-get upgrade"   and "sudo dpkg --configure -a"   Or the apt versions if you prefer apt.

Thanks for kicking the tires and finding bugs.  Others should have more info.     peace out.

I have only Opera and MegaSync that I can remove or disable easily. No other ppa.

Offline penguin

  • Full Member
  • ***
  • Posts: 119
Re: I decided to upgrade to buster
« Reply #5 on: April 26, 2019, 05:14:49 pm »
Thanks. I will try.
« Last Edit: April 26, 2019, 06:55:46 pm by penguin »

Offline penguin

  • Full Member
  • ***
  • Posts: 119
Re: I decided to upgrade to buster
« Reply #6 on: April 26, 2019, 07:54:48 pm »
I managed to install sparky-apt and sparky5-apt

but i cannot remove sparky-grub-theme

Quote
sudo apt-get upgrade
Reading package lists... Done
Building dependency tree       
Reading state information... Done
Calculating upgrade... Done
The following packages will be REMOVED:
  sparky-grub-theme
The following packages have been kept back:
  qmplay2
The following packages will be upgraded:
  ddm libaprutil1 libnma0 lightdm-gtk-greeter motionbox network-manager-gnome
  opera-stable powermgmt-base sparky-info
The following packages will be DOWNGRADED:
  base-files python-twodict
9 upgraded, 0 newly installed, 2 downgraded, 1 to remove and 2 not upgraded.
1 not fully installed or removed.
Need to get 0 B/90.9 MB of archives.
After this operation, 2,328 kB of additional disk space will be used.
Do you want to continue? [Y/n] y
Reading changelogs... Done
Preconfiguring packages ...
(Reading database ... 341988 files and directories currently installed.)
Removing sparky-grub-theme (0.1.4) ...
Generating grub configuration file ...
Found background image: /usr/share/images/desktop-base/desktop-grub.png
Found background image: /usr/share/images/desktop-base/desktop-grub.png
Found linux image: /boot/vmlinuz-4.19.0-4-amd64
Found initrd image: /boot/initrd.img-4.19.0-4-amd64
Found linux image: /boot/vmlinuz-4.9.0-8-amd64
Found initrd image: /boot/initrd.img-4.9.0-8-amd64
/etc/grub.d/bin/grubcfg_proxy: error while loading shared libraries: libcrypto.so.1.0.0: cannot open shared object file: No such file or directory
dpkg: error processing package sparky-grub-theme (--remove):
 installed sparky-grub-theme package post-removal script subprocess returned error exit status 127
Errors were encountered while processing:
 sparky-grub-theme
E: Sub-process /usr/bin/dpkg returned an error code (1)

I tried also to remove in force mode. No way

Any idea?

Offline penguin

  • Full Member
  • ***
  • Posts: 119
Re: I decided to upgrade to buster
« Reply #7 on: April 26, 2019, 08:17:33 pm »
I found solution for

/etc/grub.d/bin/grubcfg_proxy: error while loading shared libraries: libcrypto.so.1.0.0: cannot open shared object file: No such file or directory
dpkg: error processing package sparky-grub-theme (--remove):
installed sparky-grub-theme package post-removal script subprocess returned error exit status 127

In the follow link:

Code: [Select]
https://askubuntu.com/questions/1116133/ubuntu-18-04-libcrypto-so-1-0-0-cannot-open-shared-object-file-no-such-file-o
So I found the missing libcrypto-so-1-0-0 by
Quote
locate libcrypto-so-1-0-0

and copied it under /usr/lib/

and sparky-grub-theme was removed.

But seems that I can not run Aptus-Extra .

Its is shown that is installed but I cannot run also in terminal and also gdebi quit when I am trying to install a package.

Seems that other things are OK.

I will make some tests and if I will be not happy I will return to my Sparky 4 Stable by restoring image created before.




Offline pavroo

  • Global Moderator
  • Hero Member
  • *****
  • Posts: 2027
    • SparkyLinux
Re: I decided to upgrade to buster
« Reply #8 on: April 26, 2019, 08:25:43 pm »
It says that the postremove script failed during the removing process, so...
Next time, do a trick, and edit as root:
Code: [Select]
/var/lib/dpkg/info/sparky-grub-theme.postrmand comment all the lines, so should looks like that:
Code: [Select]
#set -e
#update-grub
#exit 0
Save the file and try to remove the sparky-grub-package again.
It will not try to update-grub if any problem.
Nothing is easy as it looks. Danielle Steel
Join #sparkylinux at irc.freenode.net

Offline penguin

  • Full Member
  • ***
  • Posts: 119
Re: I decided to upgrade to buster
« Reply #9 on: April 26, 2019, 08:38:17 pm »
pavroo !

For your or any other that have in mind to upgrade from Sparky fro stable to buster . Read my experience, history and feedback.
In the end I did not managed to run Sparky Aptus-Extra that was installed in my System also gdebi quits when I tried to install a deb package. Somewhere I have seen that Sparky does not support gdebi anymore ?
Others things seems that runs fine.

Meanwhile I am restoring back my Sparky 4. 8)

Offline pavroo

  • Global Moderator
  • Hero Member
  • *****
  • Posts: 2027
    • SparkyLinux
Re: I decided to upgrade to buster
« Reply #10 on: April 26, 2019, 10:08:00 pm »
GDebi doesn't work as it should, that's why I removed it and replaced by debi-tool.

Anyway, upgrading Debian/Sparky from stable up to testing is not always easy and painless, I always suggest to make a fresh installation, but it's your way.

It is good point to make backup before making big changes as you've done it so should be easy to recover an older version.
Nothing is easy as it looks. Danielle Steel
Join #sparkylinux at irc.freenode.net

Offline penguin

  • Full Member
  • ***
  • Posts: 119
Re: I decided to upgrade to buster
« Reply #11 on: April 27, 2019, 07:18:40 am »
So pavroo.

Simple question. How to upgrade safely from Sparky Stable to Buster ? It is this in your plans for next months ? Without necessity of reinstalling from scratch? Or you will stick to the 2019 plains? 4.10 would be probably the last stable Sparky ?I use XFCE desktop and I tested the latest one in my Arch, but I am not really satisfy. Some of actions in Right Click does not work anymore and seems a big lack fr actual XFCE desktop that has not an adequate menu edito(this for average user), compatible with latest XFCE menu(s). Also in Debian 10 (buster) I have noticed some new services, but I had no enough time to investigate.

I tried . People can find my feedback (experience) so they can be prepare to upgrade as I have done. As I wrote. I tested some time and enjoyed it.

I found especially only two problems that I did not like or not able to resolve properly:

gdebi (quits when you tired to install) a deb package but everyone can install manually or by your  gdeb-tool
Aptus-Extra (that was installed), not shown i Whisker Menu (XFCE desktop) and when you try to run it from Terminal instead of run asked you to (reinstall or remove)

I see that sparky-extra is a YAD application but I thing that is very easy to build by lazarus or gambas3 a appimage.
I would prefer lazarus that produce directly app image. Maybe I will have a look and make a test program if I will have YAD  text in code.

So ... IF a click a icon , lets say motionbox icon ( this links to deb package in sparky repos ?) . Download and install using Terminal Commands  ?


« Last Edit: April 27, 2019, 07:27:02 am by penguin »

Offline pavroo

  • Global Moderator
  • Hero Member
  • *****
  • Posts: 2027
    • SparkyLinux
Re: I decided to upgrade to buster
« Reply #12 on: April 27, 2019, 02:28:02 pm »
aptus-extra is not a separated application any more, it is an aptus module now, that's why you can not see it at your menu.

Anyway, when Buster become stable, I will post an instruction to upgrade Sparky 4 & 5, stay tuned.
Nothing is easy as it looks. Danielle Steel
Join #sparkylinux at irc.freenode.net

Offline penguin

  • Full Member
  • ***
  • Posts: 119
Re: I decided to upgrade to buster / gdebi quits
« Reply #13 on: July 11, 2019, 05:11:39 pm »
I found solution for

/etc/grub.d/bin/grubcfg_proxy: error while loading shared libraries: libcrypto.so.1.0.0: cannot open shared object file: No such file or directory
dpkg: error processing package sparky-grub-theme (--remove):
installed sparky-grub-theme package post-removal script subprocess returned error exit status 127

In the follow link:

Code: [Select]
https://askubuntu.com/questions/1116133/ubuntu-18-04-libcrypto-so-1-0-0-cannot-open-shared-object-file-no-such-file-o
So I found the missing libcrypto-so-1-0-0 by
Quote
locate libcrypto-so-1-0-0

and copied it under /usr/lib/

and sparky-grub-theme was removed.

But seems that I can not run Aptus-Extra .

Its is shown that is installed but I cannot run also in terminal and also gdebi quit when I am trying to install a package.

Seems that other things are OK.

I will make some tests and if I will be not happy I will return to my Sparky 4 Stable by restoring image created before.

I found why gdebi quits.


I tried to install a deg package in terminal by command sudo dpkg -i XX.deb and I get error similar to follow:

Code: [Select]
Preconfiguring packages ...
dpkg: warning: 'ldconfig' not found in PATH or not executable.
dpkg: warning: 'start-stop-daemon' not found in PATH or not executable.
dpkg: error: 2 expected programs not found in PATH or not executable.
Note: root's PATH should usually contain /usr/local/sbin, /usr/sbin and /sbin.
E: Sub-process /usr/bin/dpkg returned an error code (2)


Hmmm. Googling I found that :

https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=904988

https://mapopa.blogspot.com/2011/11/fixing-debian-sid-dpkg-warning-ldconfig.html

http://forums.debian.net/viewtopic.php?f=20&t=69093#p390860

and bummm

Code: [Select]
https://unix.stackexchange.com/questions/460478/debian-su-and-su-path-differences
explanation:

Quote

The Debian su manpage tells:

The current environment is passed to the new shell. The value of $PATH is reset to /bin:/usr/bin for normal users, or  /sbin:/bin:/usr/sbin:/usr/bin for the superuser. This may be changed with the ENV_PATH and ENV_SUPATH definitions in /etc/login.defs.

Quoting from /etc/login.defs:

# Three items must be defined:  MAIL_DIR, ENV_SUPATH, and ENV_PATH.
# If unspecified, some arbitrary (and possibly incorrect) value will
# be assumed.  All other items are optional - if not specified then
On a normal Debian system the variables are defined in/etc/login.defs :

#
# *REQUIRED*  The default PATH settings, for superuser and normal users.
#
# (they are minimal, add the rest in the shell startup files)
ENV_SUPATH      PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin
ENV_PATH        PATH=/usr/local/bin:/usr/bin:/bin:/usr/local/games:/usr/games
Testing by commenting out ENV_SUPATH reproduces partially your problem: su will not have /sbin (nor /usr/local/bin) while su - will execute the login script /etc/profile which will redefine PATH as expected for the root user.

So you should check for any alteration of /etc/login.defs and correct it, or see if an other part alters the PATH later (like a shell startup script such as some non-login bashrc script)


So ... Debian do not use anymore su as we have been used before . Now we should use su -


Seems that gdebi suffer from this bug because it refers to ENV_PATH that now is changed to ENV_SUPATH.

meanwhile the old /etc/profile ( su remains the same )

Code: [Select]
if [ "`id -u`" -eq 0 ]; then
  PATH="/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin"
else
  PATH="/usr/local/bin:/usr/bin:/bin:/usr/local/games:/usr/games"
fi

So what are possibilities or the best way to resolve this problem ?

1 -Install from command line but entering terminal by su - instead of su ?
2- Changing of ENV_PATH to /etc/login.defs
3- Using gdebi-tool offered by SparkyLinux ( pavroo tool ) > look here
Code: [Select]
https://sparkylinux.org/debitool/
Seems that : gdebi-tool works perfect. I am trying it meanwhile I writing this post to install freeoffice
Code: [Select]
https://www.softmaker.com/en/applications
« Last Edit: July 11, 2019, 05:22:59 pm by penguin »

Offline paxmark1

  • Hero Member
  • *****
  • Posts: 602
Re: I decided to upgrade to buster
« Reply #14 on: July 12, 2019, 03:18:39 am »
I skimmed, 
0.1  I am not knowledgeable about libcrypto-so...    It is not viewable via aptitude search or apt-cache.  Using locate on a sid machine I do see libcrypto.so.1.1 in /usr/lib/i386-linux-gnu   It is above my paygrade.  As always - a quick "sudo updatedb" prior to using locate gives the freshest version if you have made changes.   

1.  Using answers from the Ubuntu forum for 18.04 seems rather risky.  Especially since the specific post has several options that seem to conflict.  The portion of the code scraped from Debian testing and unstable into Ubuntu 18.04 came from Debian in late October 2017.  Due to the freeze the code that was scraped from Debian testing-Buster for Ubuntu 19.04 is similar to the code found in Buster stable due to the freeze.  But please note, several portions of Ubuntu have been diverging from Debian for years, decades almost even.  Yes you can use the Ubuntu (and Arch) forums to search for ideas when you get problems, but do not apply blindly. 

2.  Bug 904988 to me appears to not be a bug.  Been posted here, and posted numerous times on Siduction and several times very recently on Debian forums since it is hitting people who upgraded.  Do not use "su"  anymore.  Use "su - root"  (Yes I used su for years, things change).

3.  http://forums.debian.net/viewtopic.php?f=20&t=69093#p390860    Really - using 2011?  It was a glitch in sid, which was probably fixed easily, but it may have gotten to testing.  Just out of sheer curiosity I may some day see what HOAS of DrXaos may have said about that bug on the #! (CrunchBang) forums.   

4.  For the Stackexchange post the crucial line is at the end.
Quote
note: /etc/profile isn't used with su, only with su -. That was just an example. – A.B Aug 5 '18 at 10:09

To the best of my knowlege "sudo" was not affected by the bin /sbin     /usrmerge   etc changes. 

So yes, from now on always use "su - blah"    there has to be a space between the -      and the user.

Question - are you having to su - root or su - userfoo  in a gui or on the command line in a terminal.  If you are already on the command line I would just go with "dkpg -i"  and skip the gui.   



Don't make a FrankenDebian