HE to Jessie upgrade

Important informations about SolydXK including releases notes, forum rules and other anouncements
User avatar
Zill
Posts: 1850
Joined: 13 Aug 2013 14:28
Location: Lincolnshire, UK

Re: HE to Jessie upgrade

Postby Zill » 12 Feb 2015 12:04

Thanks for the clarification, Gents. On the basis that "if it ain't broke don't fix it" I will leave /etc/apt/preferences.solydxk where it is for now! If I hit any problems then I know where to look. ;-)

User avatar
Zill
Posts: 1850
Joined: 13 Aug 2013 14:28
Location: Lincolnshire, UK

Re: HE to Jessie upgrade

Postby Zill » 12 Feb 2015 20:05

Just a follow-up to my upgrade from HE to Jessie in that I ran the solydfixes script (v1.8.7) today to remove all "dmo" packages and replace them with Debian equivalents where possible.

Using the command "apt-show-versions | grep dmo" I established that I started with 81 dmo packages and, after running "sudo ./solydfixes dmo", only "libdvdcss2:i386 1.3.0-dmo1" remained. I guess this remained because there is no similar package in the "official" Debian repos.

A big thank you to grizzler for all the work you have done in producing this great script. :-)

User avatar
Arjen Balfoort
Site Admin
Posts: 9282
Joined: 26 Jan 2013 19:36
Location: Netherlands
Contact:

Re: HE to Jessie upgrade

Postby Arjen Balfoort » 12 Feb 2015 21:29

It's in our repository:

Code: Select all

$ apt search libdvdcss2
p   libdvdcss2                      - Simple foundation for reading DVDs - runti
p   libdvdcss2:i386                 - Simple foundation for reading DVDs - runti
I took them from deb-multimedia.


SolydXK needs you!
Development | Testing | Translations

User avatar
Zill
Posts: 1850
Joined: 13 Aug 2013 14:28
Location: Lincolnshire, UK

Re: HE to Jessie upgrade

Postby Zill » 12 Feb 2015 22:48

This is my current system output:

Code: Select all

roger@dino:~$ apt search libdvdcss2
i   libdvdcss2                      - Simple foundation for reading DVDs - runti

roger@dino:~$ apt policy libdvdcss2
libdvdcss2:
  Installed: 1.3.0-dmo1
  Candidate: 1.3.0-dmo1
  Version table:
 *** 1.3.0-dmo1 0
        100 /var/lib/dpkg/status
     1.2.13-dmo1 0
        500 http://repository.solydxk.com/ solydxk/import i386 Packages
It looks like v1.3.0 is still installed (this was the original dmo version) but v1.2.13 is the solydxk repo version. I guess the solydfixes script might have been confused by retaining the "dmo" suffix in the solydxk package info?

User avatar
grizzler
Posts: 2171
Joined: 04 Mar 2013 15:45
Location: The Hague, NL

Re: HE to Jessie upgrade

Postby grizzler » 13 Feb 2015 06:49

No confusion as far as the script is concerned.

Removing the dmo packages that are also in the solydxk repo wouldn't really make sense. The script has a list of those packages, so it leaves them installed.

Apparently, deb-multimedia.org has provided a newer version of libdvdcss2 since Arjen copied 1.2.13 (maybe a good idea to pick up 1.3.0 now, Arjen?).
Frank

SolydX EE 64 - tracking Debian Testing

User avatar
Arjen Balfoort
Site Admin
Posts: 9282
Joined: 26 Jan 2013 19:36
Location: Netherlands
Contact:

Re: HE to Jessie upgrade

Postby Arjen Balfoort » 13 Feb 2015 09:06

grizzler wrote:Apparently, deb-multimedia.org has provided a newer version of libdvdcss2 since Arjen copied 1.2.13 (maybe a good idea to pick up 1.3.0 now, Arjen?).
Done.


SolydXK needs you!
Development | Testing | Translations

GinRin
Posts: 7
Joined: 13 Feb 2015 10:44

Re: HE to Jessie upgrade

Postby GinRin » 13 Feb 2015 10:50

The upgrade from HE to Jessie 64 bit was succesfull on my PC. However I have a little issue with the updatemanager. It is version 2.5.5. On the system tray it always gives the notification that there "are updates availabe". If there are updates they do install correctly, but the update signal is not reset after the update and I always get this message.
Is this issue known or can I fix it?
Regards, Bert

User avatar
Zill
Posts: 1850
Joined: 13 Aug 2013 14:28
Location: Lincolnshire, UK

Re: HE to Jessie upgrade

Postby Zill » 13 Feb 2015 11:12

grizzler wrote:... Removing the dmo packages that are also in the solydxk repo wouldn't really make sense. The script has a list of those packages, so it leaves them installed.
Agreed.
grizzler wrote:... Apparently, deb-multimedia.org has provided a newer version of libdvdcss2 since Arjen copied 1.2.13 (maybe a good idea to pick up 1.3.0 now, Arjen?).
Thanks for fixing this. :-)

Code: Select all

roger@dino:~$ apt policy libdvdcss2
libdvdcss2:
  Installed: 1.3.0-dmo1
  Candidate: 1.3.0-dmo1
  Version table:
 *** 1.3.0-dmo1 0
        500 http://repository.solydxk.com/ solydxk/import i386 Packages
        100 /var/lib/dpkg/status

User avatar
Arjen Balfoort
Site Admin
Posts: 9282
Joined: 26 Jan 2013 19:36
Location: Netherlands
Contact:

Re: HE to Jessie upgrade

Postby Arjen Balfoort » 13 Feb 2015 12:23

GinRin wrote:The upgrade from HE to Jessie 64 bit was succesfull on my PC. However I have a little issue with the updatemanager. It is version 2.5.5. On the system tray it always gives the notification that there "are updates availabe". If there are updates they do install correctly, but the update signal is not reset after the update and I always get this message.
Is this issue known or can I fix it?
Regards, Bert
This can have several causes.
If you upgraded by terminal, you need to at least execute the first step in the post-install section:

Code: Select all

sudo /bin/bash -c 'echo "upd=2015.01.31" > /usr/lib/solydxk/updatemanager/files/updatemanager.hist'
If you used the update manager, you need to check if there were no packages held back. Run this command to check that:

Code: Select all

sudo apt-get -f install


SolydXK needs you!
Development | Testing | Translations

GinRin
Posts: 7
Joined: 13 Feb 2015 10:44

Re: HE to Jessie upgrade

Postby GinRin » 13 Feb 2015 12:43

Schoelje wrote:
GinRin wrote:The upgrade from HE to Jessie 64 bit was succesfull on my PC. However I have a little issue with the updatemanager. It is version 2.5.5. On the system tray it always gives the notification that there "are updates availabe". If there are updates they do install correctly, but the update signal is not reset after the update and I always get this message.
Is this issue known or can I fix it?
Regards, Bert
This can have several causes.
If you upgraded by terminal, you need to at least execute the first step in the post-install section:

Code: Select all

sudo /bin/bash -c 'echo "upd=2015.01.31" > /usr/lib/solydxk/updatemanager/files/updatemanager.hist'
Well I did that. I used the terminal method and I exactly copied the last command. The update manager gives the info that the installation is correct, but still I get the message that there are updates available.

User avatar
Arjen Balfoort
Site Admin
Posts: 9282
Joined: 26 Jan 2013 19:36
Location: Netherlands
Contact:

Re: HE to Jessie upgrade

Postby Arjen Balfoort » 13 Feb 2015 12:46

Then follow up the second command to check if something is held back.


SolydXK needs you!
Development | Testing | Translations

GinRin
Posts: 7
Joined: 13 Feb 2015 10:44

Re: HE to Jessie upgrade

Postby GinRin » 13 Feb 2015 12:51

Schoelje wrote:Then follow up the second command to check if something is held back.
Nope nothing happens.

I copied the output below:
sudo apt-get -f install
Pakketlijsten worden ingelezen... Klaar
Boom van vereisten wordt opgebouwd
De statusinformatie wordt gelezen... Klaar
0 opgewaardeerd, 0 nieuw geïnstalleerd, 0 te verwijderen en 1 niet opgewaardeerd.

User avatar
grizzler
Posts: 2171
Joined: 04 Mar 2013 15:45
Location: The Hague, NL

Re: HE to Jessie upgrade

Postby grizzler » 13 Feb 2015 13:03

GinRin wrote:0 opgewaardeerd, 0 nieuw geïnstalleerd, 0 te verwijderen en 1 niet opgewaardeerd.
Eentje niet opgewaardeerd, wordt dus tegengehouden (held back).
Probeer eens (sorry: try):

Code: Select all

/usr/bin/apt list --upgradable
(You need the /usr/bin bit because that's the "official" apt, not the one in /usr/local/bin, provided by SolydXK).
Frank

SolydX EE 64 - tracking Debian Testing

GinRin
Posts: 7
Joined: 13 Feb 2015 10:44

Re: HE to Jessie upgrade

Postby GinRin » 13 Feb 2015 13:05

grizzler wrote:
GinRin wrote:0 opgewaardeerd, 0 nieuw geïnstalleerd, 0 te verwijderen en 1 niet opgewaardeerd.
Eentje niet opgewaardeerd, wordt dus tegengehouden (held back).
Probeer eens (sorry: try):

Code: Select all

/usr/bin/apt list --upgradable
It gives the following output:

Code: Select all

bert@apollo ~ $ /usr/bin/apt list --upgradable
Bezig met oplijsten... Klaar
chromium/testing 40.0.2214.91-1 i386 [opwaardeerbaar van: 37.0.2062.120-2]
N: Er is 1 bijkomende versie. Gebruik schakelaar '-a' om het te zien.
bert@apollo ~ $ /usr/bin/apt list --upgradable -a
Bezig met oplijsten... Klaar
chromium/testing 40.0.2214.91-1 i386 [opwaardeerbaar van: 37.0.2062.120-2]
chromium/now 37.0.2062.120-2 i386 [geïnstalleerd,opwaardeerbaar naar: 40.0.2214.91-1]
Well it is about chromium. It is not possible anymore to deinstall chromium. But that is another problem I think.

User avatar
grizzler
Posts: 2171
Joined: 04 Mar 2013 15:45
Location: The Hague, NL

Re: HE to Jessie upgrade

Postby grizzler » 13 Feb 2015 13:09

Does

Code: Select all

apt install chromium
give any errors?
Frank

SolydX EE 64 - tracking Debian Testing

GinRin
Posts: 7
Joined: 13 Feb 2015 10:44

Re: HE to Jessie upgrade

Postby GinRin » 13 Feb 2015 13:18

grizzler wrote:Does

Code: Select all

apt install chromium
give any errors?
Yes there were errors. I installed chromium this way and the problem is solved. This command deleted the faulty file and installed the right ones. Thank you for the solution.

Bert

GinRin
Posts: 7
Joined: 13 Feb 2015 10:44

Re: HE to Jessie upgrade

Postby GinRin » 14 Feb 2015 09:49

I have another question:
During startup of Jessie 64 bit (SolydK) I get an error saying:
"unexpectedly disconnected from boot status daemon"
Search on internet shows that this could be an error in Plymouth and that the SolydK logo should be displayed. I performed the code : /usr/sbin/plymouth-set-default-theme

and get the output: "solydk-logo".

The system starts anyway so that is not the problem.
Should the SolydK logo be displayed during startup?

User avatar
Arjen Balfoort
Site Admin
Posts: 9282
Joined: 26 Jan 2013 19:36
Location: Netherlands
Contact:

Re: HE to Jessie upgrade

Postby Arjen Balfoort » 14 Feb 2015 10:20

Please, search the forum first. There already could be an answer to your question: http://forums.solydxk.nl/viewtopic.php?f=13&t=5351


SolydXK needs you!
Development | Testing | Translations

GinRin
Posts: 7
Joined: 13 Feb 2015 10:44

Re: HE to Jessie upgrade

Postby GinRin » 14 Feb 2015 10:50

Schoelje wrote:Please, search the forum first. There already could be an answer to your question: http://forums.solydxk.nl/viewtopic.php?f=13&t=5351
Woops sorry for that. This does solves my problem. Thank you.

Tim Robberts
Posts: 5
Joined: 12 May 2014 18:10

Re: HE to Jessie upgrade

Postby Tim Robberts » 16 Mar 2015 16:43

Well when I updated everything went well till I made a minor mistake :ugeek: When I got to this screen (screenshot credit to user dirigible who I copied it from):

Image

I should have waited 60 seconds more but thought the process had frozen as I couldn't click the down arrow to pick lightdm. I click the OK button and poof the install continued but of course using KDM instead of lightdm :o

I rebooted and everything seemed fine and figured I would fix it later. Well later is now. I searched and found this post on how to change from KDM to lightdm and followed it:

http://forums.solydxk.com/viewtopic.php?f=9&t=4368

That went well but I did get this error:

Code: Select all

Tim@Tim-3 ~ $ sudo apt-get update
[sudo] password for Tim: 
<<<snip nothing odd here>>>>
Tim@Tim-3 ~ $ sudo apt-get install lightdm-gtk-greeter --no-install-recommends
Reading package lists... Done
Building dependency tree       
Reading state information... Done
lightdm-gtk-greeter is already the newest version.
lightdm-gtk-greeter set to manually installed.
The following packages were automatically installed and are no longer required:
  libavutil53 libexif12:i386 libgd3:i386 libgphoto2-6:i386 libgphoto2-port10:i386 libinput3 libjs-excanvas
  libjs-mochikit libllvm3.4 libllvm3.4:i386 libltdl7:i386 libsystemd-daemon0 libsystemd-id128-0
  libsystemd-id128-0:i386 libsystemd-journal0 libsystemd-journal0:i386 libtiff5:i386 libusb-1.0-0:i386
  libvpx1:i386 libxpm4:i386 linux-headers-3.14-2-amd64 linux-headers-3.14-2-common linux-image-3.14-2-amd64
  linux-kbuild-3.14 par2 python-cheetah python-yenc python3-packagekit tix
Use 'apt-get autoremove' to remove them.
0 upgraded, 0 newly installed, 0 to remove and 68 not upgraded.
Tim@Tim-3 ~ $ sudo apt-get install lightdm lightdm-manager solydk-lightdm-adjustments
Reading package lists... Done
Building dependency tree       
Reading state information... Done
Package solydk-lightdm-adjustments is not available, but is referred to by another package.
This may mean that the package is missing, has been obsoleted, or
is only available from another source
However the following packages replace it:
  solydk-system-adjustments

E: Package 'solydk-lightdm-adjustments' has no installation candidate
Tim@Tim-3 ~ $ sudo apt-get install lightdm lightdm-manager solydk-system-adjustments
Reading package lists... Done
Building dependency tree       
Reading state information... Done
lightdm is already the newest version.
lightdm set to manually installed.
The following packages were automatically installed and are no longer required:
  libavutil53 libexif12:i386 libgd3:i386 libgphoto2-6:i386 libgphoto2-port10:i386 libinput3 libjs-excanvas
  libjs-mochikit libllvm3.4 libllvm3.4:i386 libltdl7:i386 libsystemd-daemon0 libsystemd-id128-0
  libsystemd-id128-0:i386 libsystemd-journal0 libsystemd-journal0:i386 libtiff5:i386 libusb-1.0-0:i386
  libvpx1:i386 libxpm4:i386 linux-headers-3.14-2-amd64 linux-headers-3.14-2-common linux-image-3.14-2-amd64
  linux-kbuild-3.14 par2 python-cheetah python-yenc python3-packagekit tix
Use 'apt-get autoremove' to remove them.
The following NEW packages will be installed:
  lightdm-manager
The following packages will be upgraded:
  solydk-system-adjustments
1 upgraded, 1 newly installed, 0 to remove and 67 not upgraded.
Need to get 2,545 kB of archives.
After this operation, 297 kB of additional disk space will be used.
Do you want to continue? [Y/n] Y
Get:1 http://repository.solydxk.com/ solydxk/main lightdm-manager all 0.6.8 [30.9 kB]
Get:2 http://repository.solydxk.com/ solydxk/main solydk-system-adjustments all 2.0.7 [2,514 kB]
Fetched 2,545 kB in 6s (403 kB/s)                                                                                
Selecting previously unselected package lightdm-manager.
(Reading database ... 296040 files and directories currently installed.)
Preparing to unpack .../lightdm-manager_0.6.8_all.deb ...
Unpacking lightdm-manager (0.6.8) ...
Preparing to unpack .../solydk-system-adjustments_2.0.7_all.deb ...
Unpacking solydk-system-adjustments (2.0.7) over (2.0.6) ...
dpkg: warning: solydk-system-adjustments: config file '/etc/skel/.gtkrc-2.0-kde4' is a circular link
 (= '/etc/skel/.gtkrc-2.0')
dpkg: warning: solydk-system-adjustments: config file '/etc/skel/.gtkrc-2.0' is a circular link
 (= '/etc/skel/.gtkrc-2.0-kde4')
Processing triggers for mime-support (3.58) ...
Processing triggers for desktop-file-utils (0.22-1) ...
Processing triggers for fontconfig (2.11.0-6.3) ...
Processing triggers for solydxk-system (2.0.6) ...
Setting up lightdm-manager (0.6.8) ...
Setting up solydk-system-adjustments (2.0.7) ...
dpkg: warning: solydk-system-adjustments: config file '/etc/skel/.gtkrc-2.0' is a circular link
 (= '/etc/skel/.gtkrc-2.0-kde4')
dpkg: warning: solydk-system-adjustments: config file '/etc/skel/.gtkrc-2.0-kde4' is a circular link
 (= '/etc/skel/.gtkrc-2.0')
Generating grub configuration file ...
Found background image: grubbg.png
Found linux image: /boot/vmlinuz-3.16.0-4-amd64
Found initrd image: /boot/initrd.img-3.16.0-4-amd64
Found linux image: /boot/vmlinuz-3.16-2-amd64
Found initrd image: /boot/initrd.img-3.16-2-amd64
Found linux image: /boot/vmlinuz-3.14-2-amd64
Found initrd image: /boot/initrd.img-3.14-2-amd64
Found linux image: /boot/vmlinuz-3.11-2-amd64
Found initrd image: /boot/initrd.img-3.11-2-amd64
Found linux image: /boot/vmlinuz-3.10-3-amd64
Found initrd image: /boot/initrd.img-3.10-3-amd64
mount: unknown filesystem type 'crypto_LUKS'
done
Tim@Tim-3 ~ $ sudo dpkg-reconfigure lightdm
Even with the error everything seems to be working correctly with no problems but I am wondering if I need to fix this problem :?:

I believe the error is something to do with a symlink pointing back to its self but am unsure how to fix it :?:

I am what I would call a medium linux user at best. I have run user friendly distros in the past like Ubuntu but got very board and wanted something based on Debian instead so changed to Solydk 64 bit.

My install uses full disk encryption using LUKS.

As I am new to the forum, If this isn't the correct thread for this question could some kind person point me to the correct place to post my question?


Return to “News & Anouncements”

Who is online

Users browsing this forum: No registered users and 3 guests