STICKY: How to upgrade a Wheezy image to Jessie (both defunct and replaced versions of Raspbian)

[chewy74]

Thanks for the help.

The apt-get update output

Code: Select all

[email protected] ~ $ sudo apt-get update
Hit http://ftp.us.debian.org jessie Release.gpg
Hit http://ftp.us.debian.org jessie Release
Hit http://security.debian.org jessie/updates Release.gpg
Hit http://raspberrypi.collabora.com wheezy Release.gpg
Hit http://archive.raspberrypi.org jessie Release.gpg
Hit http://security.debian.org jessie/updates Release
Hit http://ftp.us.debian.org jessie/main Sources
Hit http://raspberrypi.collabora.com wheezy Release
Hit http://archive.raspberrypi.org jessie Release
Hit http://ftp.us.debian.org jessie/contrib Sources
Hit http://security.debian.org jessie/updates/main Sources
Hit http://ftp.us.debian.org jessie/non-free Sources
Get:1 http://httpredir.debian.org jessie-updates Release.gpg [1,554 B]
Get:2 http://archive.mene.za.net jessie Release.gpg [198 B]
Hit http://ftp.us.debian.org jessie/main armhf Packages
Hit http://security.debian.org jessie/updates/contrib Sources
Hit http://raspberrypi.collabora.com wheezy/rpi armhf Packages
Hit http://archive.raspberrypi.org jessie/main Sources
Hit http://ftp.us.debian.org jessie/contrib armhf Packages
Hit http://ftp.us.debian.org jessie/non-free armhf Packages
Hit http://security.debian.org jessie/updates/non-free Sources
Get:3 http://archive.mene.za.net jessie Release [3,095 B]
Hit http://archive.raspberrypi.org jessie/main armhf Packages
Hit http://ftp.us.debian.org jessie/contrib Translation-en
Hit http://security.debian.org jessie/updates/main armhf Packages
Hit http://ftp.us.debian.org jessie/main Translation-en
Hit http://ftp.us.debian.org jessie/non-free Translation-en
Get:4 http://archive.mene.za.net jessie/contrib armhf Packages [9,002 B]
Get:5 http://httpredir.debian.org jessie-updates Release [127 kB]
Hit http://security.debian.org jessie/updates/contrib armhf Packages
Hit http://security.debian.org jessie/updates/non-free armhf Packages
Hit http://security.debian.org jessie/updates/contrib Translation-en
Hit http://security.debian.org jessie/updates/main Translation-en
Hit http://security.debian.org jessie/updates/non-free Translation-en
Get:6 http://httpredir.debian.org jessie-updates/main Sources [2,296 B]
Get:7 http://httpredir.debian.org jessie-updates/contrib Sources [32 B]
Get:8 http://httpredir.debian.org jessie-updates/non-free Sources [32 B]
Get:9 http://httpredir.debian.org jessie-updates/main armhf Packages [3,420 B]
Ign http://raspberrypi.collabora.com wheezy/rpi Translation-en_US
Ign http://archive.raspberrypi.org jessie/main Translation-en_US
Get:10 http://httpredir.debian.org jessie-updates/contrib armhf Packages [32 B]
Ign http://raspberrypi.collabora.com wheezy/rpi Translation-en
Ign http://archive.raspberrypi.org jessie/main Translation-en
Get:11 http://httpredir.debian.org jessie-updates/non-free armhf Packages [32 B]
Ign http://archive.mene.za.net jessie/contrib Translation-en_US
Get:12 http://httpredir.debian.org jessie-updates/contrib Translation-en [14 B]
Ign http://archive.mene.za.net jessie/contrib Translation-en
Get:13 http://httpredir.debian.org jessie-updates/main Translation-en [2,506 B]
Get:14 http://httpredir.debian.org jessie-updates/non-free Translation-en [14 B]
Fetched 149 kB in 25s (5,885 B/s)
Reading package lists... Done

But here's the apt-get policy output

Code: Select all

[email protected] ~ $ apt-cache policy
Package files:
 100 /var/lib/dpkg/status
     release a=now
 -10 http://archive.raspberrypi.org/debian/ jessie/main armhf Packages
     release o=Raspberry Pi Foundation,a=stable,n=jessie,l=Raspberry Pi Foundation,c=main
     origin archive.raspberrypi.org
 -10 http://archive.mene.za.net/raspbian/ jessie/contrib armhf Packages
     release o=Mene,n=jessie,l=Mene,c=contrib
     origin archive.mene.za.net
 500 http://raspberrypi.collabora.com/ wheezy/rpi armhf Packages
     release o=Collabora,n=wheezy,l=Collabora Raspberry Pi graphics enablement,c=rpi
     origin raspberrypi.collabora.com
 500 http://security.debian.org/ jessie/updates/non-free Translation-en
 500 http://security.debian.org/ jessie/updates/main Translation-en
 500 http://security.debian.org/ jessie/updates/contrib Translation-en
 -10 http://security.debian.org/ jessie/updates/non-free armhf Packages
     release v=8,o=Debian,a=stable,n=jessie,l=Debian-Security,c=non-free
     origin security.debian.org
 -10 http://security.debian.org/ jessie/updates/contrib armhf Packages
     release v=8,o=Debian,a=stable,n=jessie,l=Debian-Security,c=contrib
     origin security.debian.org
 -10 http://security.debian.org/ jessie/updates/main armhf Packages
     release v=8,o=Debian,a=stable,n=jessie,l=Debian-Security,c=main
     origin security.debian.org
 500 http://httpredir.debian.org/debian/ jessie-updates/non-free Translation-en
 500 http://httpredir.debian.org/debian/ jessie-updates/main Translation-en
 500 http://httpredir.debian.org/debian/ jessie-updates/contrib Translation-en
 500 http://httpredir.debian.org/debian/ jessie-updates/non-free armhf Packages
     release o=Debian,a=stable-updates,n=jessie-updates,l=Debian,c=non-free
     origin httpredir.debian.org
 500 http://httpredir.debian.org/debian/ jessie-updates/contrib armhf Packages
     release o=Debian,a=stable-updates,n=jessie-updates,l=Debian,c=contrib
     origin httpredir.debian.org
 500 http://httpredir.debian.org/debian/ jessie-updates/main armhf Packages
     release o=Debian,a=stable-updates,n=jessie-updates,l=Debian,c=main
     origin httpredir.debian.org
 500 http://ftp.us.debian.org/debian/ jessie/non-free Translation-en
 500 http://ftp.us.debian.org/debian/ jessie/main Translation-en
 500 http://ftp.us.debian.org/debian/ jessie/contrib Translation-en
 -10 http://ftp.us.debian.org/debian/ jessie/non-free armhf Packages
     release v=8.2,o=Debian,a=stable,n=jessie,l=Debian,c=non-free
     origin ftp.us.debian.org
 -10 http://ftp.us.debian.org/debian/ jessie/contrib armhf Packages
     release v=8.2,o=Debian,a=stable,n=jessie,l=Debian,c=contrib
     origin ftp.us.debian.org
 -10 http://ftp.us.debian.org/debian/ jessie/main armhf Packages
     release v=8.2,o=Debian,a=stable,n=jessie,l=Debian,c=main
     origin ftp.us.debian.org
Pinned packages:

So I'm not sure what else to do... Can I force the upgrade somehow?

There is no "force". If your packages list is correct the upgrade will happen.
Could you show the output that you get when you run "sudo apt-get update"? You seem to have missed that out when you posted.

Also, show the output of "apt-cache policy" (sudo not required for apt-cache).

[rpdom]

You've got something in /etc/apt/preferences.d/ that is pinning the jessie entries to priority -10, which means "don't use this".

Code: Select all

 -10 http://archive.raspberrypi.org/debian/ jessie/main armhf Packages
     release o=Raspberry Pi Foundation,a=stable,n=jessie,l=Raspberry Pi Foundation,c=main
     origin archive.raspberrypi.org

Perhaps you added something to be able to install a package from jessie while you were still running wheezy?
Take that out and run the update/upgrade again.

[gkreidl]

I don't see a raspbian archive, just stock debian in sources.

[ShiftPlusOne]

The given instructions (and this thread in general) are for the last official wheezy image release. If your sources look like that, you should know enough of what you're doing to get the install you want.

[chewy74]

Dammit, I forgot about that. I pinned jessie repo to get an updated transmission install way back. I thought I had removed it all.

Everything is updating now. Thanks for your help my friend.

You've got something in /etc/apt/preferences.d/ that is pinning the jessie entries to priority -10, which means "don't use this".

Code: Select all

 -10 http://archive.raspberrypi.org/debian/ jessie/main armhf Packages
     release o=Raspberry Pi Foundation,a=stable,n=jessie,l=Raspberry Pi Foundation,c=main
     origin archive.raspberrypi.org

Perhaps you added something to be able to install a package from jessie while you were still running wheezy?
Take that out and run the update/upgrade again.

[bartgrefte]

Has anyone written down the location where the old configuration files were backed up? I remember seeing a popup about that after the upgrade, forgot to write down the location.

Looks like vsftpd also replaced some settings I made before the upgrade...

[ShiftPlusOne]

Has anyone written down the location where the old configuration files were backed up? I remember seeing a popup about that after the upgrade, forgot to write down the location.

Looks like vsftpd also replaced some settings I made before the upgrade...

Same directory, with the extension .dpkg-old (or something similar, I don't remember off the top of my head)

[bartgrefte]

Got it, thanks

Turns out "write_enable=YES" got commented during the upgrade, causing 550 permission errors when I tried to do anything (rm/create/mv/cp).

[JarJarGeek]

I'll post my method in a new thread as it relates to creating a new image as opposed to upgrading ; but I had real difficulties with the Wheezy / Jessie upgrade. I would recommend backing up any files you have on your wheezy card and starting with a fresh Jessie .img ; a lot quicker and pain free. What I wanted was a ' light Jessie ' that would would fit on a 4Gb card as some of the clubs / schools I'm involved with have a few ModelB / 4Gb setups ; removing wolfram / Libreoffice was part of my plan. Anyways gave up on update path after a few crashes / failed attempts and managed to create a 4Gb Jessie with MineCraftPi / Sonic-Pi / Scratch etc , figured Wolfram and word processing wasn't going to be essential in that package

[manuti]

Dammit, I forgot about that. I pinned jessie repo to get an updated transmission install way back. I thought I had removed it all.

Everything is updating now. Thanks for your help my friend.

Please can you explain the changes you made to revert this situation?
I'm stuck in the same point.
Thanks.

[diederik]

I pinned jessie repo to get an updated transmission install way back. I thought I had removed it all.

Please can you explain the changes you made to revert this situation?

Check in /etc/apt/preferences and/or /etc/apt/preferences.d/ because that's where apt-pinnings are stored.

[e-raser]

Hi,

I followed the instructions (also big thanks for the hint regarding nginx/php-fpm/fastcgi !) but it seems some things are not finally okay so far (sorted from 1 = small issue to 3 = big trouble):

1) How can I check if I´m already using the new GUI (GTK+3)?
2) Could not "cp /usr/share/themes/PiX ~/.themes -ax" because there is no theme "PiX"! How can I fix this?
3) I have three cron´s running at boot time (in fact a load more, but those 3 are the only one not working). Everyone´s doing a specific thing, but the only pattern I could detect is: They all are network related.
- job 1 should mount a CIFS share,
- job 2 should start the tightvncserver and
- job 3 run´s a CURL at PushingBox.com.
They are ALL not working. Running manually when the system has started is fine. What can I check? Timeouts for network etc.?

[e-raser]

Update:

• #3 fixed by adding line "auto eth0" in /etc/network/interfaces. Found hint in comment in http://serendipity.ruwenzori.net/index. ... up-on-boot
• Still need help on #1 and #2 !

[igelkun]

erm, don't you think it might be worth mentioning that this upgrade might render your pi unbootable because of the change to /etc/fstab (see https://www.debian.org/releases/stable/ ... s-incompat)? I'd love to spare others the pain I had to endure this morning...

[rm53]

...
I followed the additional steps (most of them) in the OP. One didn't work:

Code: Select all

cp –ax /usr/share/themes/PiX ~/.themes

You must use:

Code: Select all

cp /usr/share/themes/PiX ~/.themes -ax

instead.
...

Could someone please explain this?
I used Unix-like systems since decades and never happened to see a "cp" backwards-syntax working.
I just opened the man page of cp on my Pi to be sure: It tells the usual usage pattern:

Code: Select all

cp [options] arguments

,
with several variants of the arguments depending if they are single filenames or directories, but never does the options follow the args.
This puzzles me really hard. Can somebody please explain this?

[jojopi]

Could someone please explain this?

POSIX says that options must precede other arguments, and many non-GNU systems require that. However, GNU getopt normally permits options to appear anywhere. The special argument "--" can be used to indicate that all remaining arguments are not options.

Of course it makes no difference to the behaviour whether "-ax" is specified first or last. The problem in the first post of this thread was that two of the options were spelled with a Unicode en dash "–" instead of an ASCII hyphen "-". So copy-pasting those options will fail, but re-typing them will work.

[e-raser]

Nice Linux/Unix theory stuff talk - but the real problem is: The folder simply does not exist! Please focus on this

[e-raser]

To be more specific on my question #1:
I have e.g. Synaptics Package Manager which is almost completely black when running. It worked (nice new GUI) for some time meanwhile, but after a few reboots -> back to "defect GUI"

Second new UI problem:
I don´t have the wicd and clipit plugins anymore on lxpanel. They are not listed as plugins when trying to configure lxpanel. Content of plugins folder:

Code: Select all

[email protected]:~$ sudo ls -l /usr/lib/arm-linux-gnueabihf/lxpanel/plugins
insgesamt 380
-rw-r--r-- 1 root root 21924 Nov 21 14:41 batt.so
-rw-r--r-- 1 root root  9632 Nov 21 14:41 cpufreq.so
-rw-r--r-- 1 root root 13724 Nov 21 14:41 cpu.so
-rw-r--r-- 1 root root  9632 Nov 21 14:41 deskno.so
-rw-r--r-- 1 root root 62940 Nov 21 14:41 dhcpcdui.so
-rw-r--r-- 1 root root  9688 Nov 21 14:41 kbled.so
-rw-r--r-- 1 root root 17884 Nov 21 14:41 monitors.so
-rw-r--r-- 1 root root 30112 Nov 21 14:41 netstat.so
-rw-r--r-- 1 root root 59456 Nov 21 14:41 netstatus.so
-rw-r--r-- 1 root root 13728 Nov 21 14:41 thermal.so
-rw-r--r-- 1 root root 26020 Nov 21 14:41 volumealsa.so
-rw-r--r-- 1 root root 42492 Nov 21 14:41 weather.so
-rw-r--r-- 1 root root 38300 Nov 21 14:41 xkb.so

You can see both problems on this screenshot attached:

[e-raser]

Update: wicd and clipit issue resolved. Turned out they are combined to a plugin called "tray":

Code: Select all

Plugin {
  type=tray
  Config {
  }
}

Very obscure. Also the ejecter-plugin not showing up. Anyway, one problem left (the GUI one).

[gkreidl]

@e-raser:
The black background bug is seen in all applications that use GTK+3 (kweb3, for example). Some window themes are somehow broken. I suppose you are using Clearlooks. Run lxappearance and select another theme, Adwaita or PIX do work.

[e-raser]

@gkreidl:
1) No I was using Mist.
2) I don´t have the PIX, which is one of my problems posted above... How to install it?
3) Same on Clearlooks, so you were right.
4) Using Adwaita for the moment, working with my "black application(s)" - thx!

[e-raser]

Update: wicd and clipit issue resolved. Turned out they are combined to a plugin called "tray":

Code: Select all

Plugin {
  type=tray
  Config {
  }
}

Very obscure. Also the ejecter-plugin not showing up. Anyway, one problem left (the GUI one).

Update: And gone away after a reboot. The config (/home/pi/.config/lxpanel/LXDE/panel) has not been changed; but the tray plugin (aka "notification center"?) isn´t available anymore.

Problem even getting worse: Applications starting in tray are not showing up there anymore... horrible!

• When doing a "lxpanelctl restart" all the missed apps are visible for half a second. Then lxpanel get´s loaded and finally everything missing (wicd, clipit, other apps starting minimized to tray) is away again.
• When killing all lxpanels (sudo lxpanel exit, then checking via top/htop) and running "lxpanel" from a cli, a lxpanel with a completely other setting is shown: e.g. the wicd+clipit and my other "start minimized to tray-applications". I assume because it is using a standard profile. Starting with "lxpanel -p LXDE &" I get my profile with the missing parts. Output says:

  Code: Select all

  Xlib:  extenstion "RANDR" missing on display ":10.0".
  
  ** (lxpanel:5918): WARNING **: XDG_TEMPLATES_DIR is set to invalid path, ignoring it
  ** (lxpanel:5918): WARNING **: lxpanel: can´t load volumealsa plugin
  ** (lxpanel:5918): WARNING **: lxpanel: can´t load ejecter plugin
  ** (lxpanel:5918): WARNING **: lxpanel: tray: another systray already running
  ** (lxpanel:5918): WARNING **: lxpanel: can´t load tray plugin
  

  ==> Where (which file) can I check the XDG_TEMPLATES_DIR setting? Or is this the wrong direction?

Any ideas?

[e-raser]

Can anyone meanwhile please post me the content of "/usr/lib/arm-linux-gnueabihf/lxpanel/plugins" ?

Code: Select all

sudo ls -lha /usr/lib/arm-linux-gnueabihf/lxpanel/plugins

[Kratos]

Sure, here. Please note that I have configured the panel to my liking a bit, although I'm not sure if that will change the output.

Code: Select all

[email protected] ~ $ sudo ls -lha /usr/lib/arm-linux-gnueabihf/lxpanel/plugins
total 392K
drwxr-xr-x 2 root root 4.0K Sep 24 09:02 .
drwxr-xr-x 3 root root 4.0K Sep 24 09:02 ..
-rw-r--r-- 1 root root  22K Sep  3 07:35 batt.so
-rw-r--r-- 1 root root 9.4K Sep  3 07:35 cpufreq.so
-rw-r--r-- 1 root root  14K Sep  3 07:35 cpu.so
-rw-r--r-- 1 root root 9.4K Sep  3 07:35 deskno.so
-rw-r--r-- 1 root root  62K Sep  3 07:35 dhcpcdui.so
-rw-r--r-- 1 root root  18K Sep  3 07:35 ejecter.so
-rw-r--r-- 1 root root 9.5K Sep  3 07:35 kbled.so
-rw-r--r-- 1 root root  14K Sep  3 07:35 monitors.so
-rw-r--r-- 1 root root  26K Sep  3 07:35 netstat.so
-rw-r--r-- 1 root root  55K Sep  3 07:35 netstatus.so
-rw-r--r-- 1 root root  14K Sep  3 07:35 thermal.so
-rw-r--r-- 1 root root  26K Sep  3 07:35 volumealsa.so
-rw-r--r-- 1 root root  42K Sep  3 07:35 weather.so
-rw-r--r-- 1 root root  34K Sep  3 07:35 xkb.so
[email protected] ~ $ 

I hope this helps!

Kratos

[e-raser]

Thanks! It helped a lil bit... made a comparison; I´m only missing the ejecter.so.
Can you send it over to me? Would save me a lot of time (downloading Raspbian Jessie image, installing it in a VM, grabbing the file, ...)

Anyway, I´m making no progress on this...
I think I will take a deeper look at
http://sourceforge.net/projects/lxde/fi ... 0panel%29/
http://sourceforge.net/p/lxde/bugs/
...but I´m pretty sure they´ll react like "Oh, you´ve got a problem with a customized version of our lxpanel? Go talk to your customizers (Raspbian)!"