jessie added to main raspbian archive

[plugwash]

jessie has now been added to the main raspbian archive.

Enjoy!

[redhawk]

what is jessie??

Richard S.

[plugwash]

jessie is the codename for the next version of debian/raspbian currently in "testing" (and will be for some time).

[malakai]

I can't wait. I will just pretend I didn't read this and come back in a few months.

[shuckle]

So how can it be used? I bet apt-get update will not find it?

[rpdom]

So how can it be used? I bet apt-get update will not find it?

Edit your /etc/apt/sources.list

Change all lines that have "wheezy" to "jessie".

sudo apt-get update
sudo apt-get upgrade
sudo apt-get dist-upgrade

[frh_rpi]

Hi,
you can also use the 2 distributions at the same time thanks to apt pinning

in /etc/apt/sources.list
deb http://mirrordirector.raspbian.org/raspbian/ wheezy main contrib non-free rpi
deb http://archive.raspbian.org/raspbian wheezy main contrib non-free rpi
# Source repository to add
deb-src http://archive.raspbian.org/raspbian wheezy main contrib non-free rpi

deb http://mirrordirector.raspbian.org/raspbian/ jessie main contrib non-free rpi
deb http://archive.raspbian.org/raspbian jessie main contrib non-free rpi
# Source repository to add
deb-src http://archive.raspbian.org/raspbian jessie main contrib non-free rpi

create /etc/apt/preferences and, if you want to track jessie, put inside
Package: *
Pin: release n=jessie
Pin-Priority: 900

Package: *
Pin: release n=wheezy
Pin-Priority: 300

Package: *
Pin: release o=Raspbian
Pin-Priority: -10

Or, if you want to stick to wheezy
Package: *
Pin: release n=wheezy
Pin-Priority: 900

Package: *
Pin: release n=jessie
Pin-Priority: 300

Package: *
Pin: release o=Raspbian
Pin-Priority: -10

and then do apt-get upgrade

You will also be able to choose what version of a package you want by using:
apt-get install -t jessie <package>

Greetings all

[plugwash]

So anyone running raspbian jessie yet?

[rpdom]

So anyone running raspbian jessie yet?

I wasn't planning to switch over to Jessie yet. I'm giving it a chance to settle down, after the Debian release of Wheezy as Stable. I like to keep all my systems (PCs and Pis) on the same version.

However, now that you've mentioned it, I will upgrade one Pi and see how it goes

[Anonymous]

Curious to see how it goes. Any real benefits over stable save for being bleeding edge?

[rpdom]

Ok Pi upgraded.

I had a problem with python3-numpy, where it spat out a load of messages

Code: Select all

Preparing to replace python3-numpy 1:1.6.2-1.2 (using .../python3-numpy_1%3a1.7.1-2_armhf.deb) ...
Traceback (most recent call last):
  File "/usr/bin/py3clean", line 32, in <module>
    from debpython import files as dpf
EOFError: EOF read where not expected
dpkg: warning: subprocess old pre-removal script returned error exit status 1
dpkg: trying script from the new package instead ...
Traceback (most recent call last):
  File "/usr/bin/py3clean", line 32, in <module>
    from debpython import files as dpf
EOFError: EOF read where not expected
dpkg: error processing /var/cache/apt/archives/python3-numpy_1%3a1.7.1-2_armhf.deb (--unpack):
 subprocess new pre-removal script returned error exit status 1
Traceback (most recent call last):
  File "/usr/bin/py3compile", line 34, in <module>
    from debpython.version import SUPPORTED, debsorted, vrepr, \
EOFError: EOF read where not expected
dpkg: error while cleaning up:
 subprocess installed post-installation script returned error exit status 1
Errors were encountered while processing:
 /var/cache/apt/archives/python3-numpy_1%3a1.7.1-2_armhf.deb
E: Sub-process /usr/bin/dpkg returned an error code (1)

This seems to have happened to a few people using Ubuntu too, os it's not a Raspbian specific problem.

Someone suggested deleting the contents of /usr/share/python3/debpython/__pycache__ so I did that and ran the dist-upgrade again and it worked.

[Anonymous]

Ok Pi upgraded.

I had a problem with python3-numpy, where it spat out a load of messages

Code: Select all

Preparing to replace python3-numpy 1:1.6.2-1.2 (using .../python3-numpy_1%3a1.7.1-2_armhf.deb) ...
Traceback (most recent call last):
  File "/usr/bin/py3clean", line 32, in <module>
    from debpython import files as dpf
EOFError: EOF read where not expected
dpkg: warning: subprocess old pre-removal script returned error exit status 1
dpkg: trying script from the new package instead ...
Traceback (most recent call last):
  File "/usr/bin/py3clean", line 32, in <module>
    from debpython import files as dpf
EOFError: EOF read where not expected
dpkg: error processing /var/cache/apt/archives/python3-numpy_1%3a1.7.1-2_armhf.deb (--unpack):
 subprocess new pre-removal script returned error exit status 1
Traceback (most recent call last):
  File "/usr/bin/py3compile", line 34, in <module>
    from debpython.version import SUPPORTED, debsorted, vrepr, \
EOFError: EOF read where not expected
dpkg: error while cleaning up:
 subprocess installed post-installation script returned error exit status 1
Errors were encountered while processing:
 /var/cache/apt/archives/python3-numpy_1%3a1.7.1-2_armhf.deb
E: Sub-process /usr/bin/dpkg returned an error code (1)

This seems to have happened to a few people using Ubuntu too, os it's not a Raspbian specific problem.

Someone suggested deleting the contents of /usr/share/python3/debpython/__pycache__ so I did that and ran the dist-upgrade again and it worked.

Say what? You can run Ubuntu on a Pi?

[rpdom]

Say what? You can run Ubuntu on a Pi?

Not properly. But a few people seem to have managed to get it to work on a PC , and they use python too...

[Anonymous]

Say what? You can run Ubuntu on a Pi?

Not properly. But a few people seem to have managed to get it to work on a PC , and they use python too...

So how has your Pi been running with the new image? Any noticeable improvements?

[hifi]

If you want to test out jessie with a minimal install, raspbian-ua-netinst can certainly help you with that. It is not an official way to install Raspbian but should do the job quite well for power users who want less than the full SD image.

While jessie is currently not available in cdebootstrap suites it can still be used as the target release for raspbian-ua-netinst with clever scripting in the installer configuration script.

Example installer-config.txt to install the server preset jessie:

Code: Select all

release=jessie

cat >>/usr/share/cdebootstrap-static/suites <<EOF
Suite: jessie
Config: generic
Keyring: debian-archive-keyring.gpg
EOF

Please take note that the default apt sources list has the official raspberrypi.org repository which does not yet have jessie dist and will cause 404 errors on apt-get update. It should be possible to change the raspberrypi.org repo to use wheezy instead by manually adjusting /etc/apt/sources.list by hand.

For more information, full documentation and installer downloads,check out https://github.com/hifi/raspbian-ua-netinst

[plugwash]

BTW adding jessie to the main archive caused a massive traffic spike, I was expecting a spike but not one this big (the week after I added jessie to the main archive is marked as "week 26" on the graph.

[rpdom]

BTW adding jessie to the main archive caused a massive traffic spike, I was expecting a spike but not one this big

Perhaps a lot of people had their sources.list pointing at "testing" instead of "wheezy" and upgraded without realising?

[jackokring]

Just started the upgrade. Looks like it will take a while. Any news on Qt 5.1, and is it included as a built package? Just checking, as the packages from twolife.be uninstalled qtcreator.

[plugwash]

Perhaps a lot of people had their sources.list pointing at "testing" instead of "wheezy" and upgraded without realising?

I suspect it was more that we just seem to have a crazy number of mirrors nowadays.

Any news on Qt 5.1

It looks like so far QT5 is still only in experimental.

[jackokring]

Ok with an external / and full SD /boot it works excepting the CTRL+D needed to get past the file not found error on /boot. Hopefully this is the start of a launch a different machine code file option.

EDIT: One more thing, the kernel firmware is still the rpi-update latest. So this may be related to the init ramdisk content.

EDIT2: False alarm, just needed a noauto in fstab on the unplugged media volume.

Jessie? It's big.

[hifi]

Latest raspbian-ua-netinst has full jessie support out of box now. You just need to set the release to jessie as described earlier but do not need the cat hack anymore.

Example installer-config.txt to install the server preset jessie:

Code: Select all

release=jessie

Thanks to plugwash for patching the Raspbian cdebootstrap package until upstream (Debian) does it for theirs.

[Jahangir]

First really thanks to port Jessie on the Rpi. Second I didn't see any other thread talking about it then I post this "report" here.

It seems the last version of Perl is missing from the repository index.

When I wanted to do an upgrade with aptitude it tells me :

Code: Select all

The following packages have unmet dependencies:
 libnet-ssleay-perl : Depends: perl (>= 5.18.1-3) but 5.14.2-21+rpi2 is installed.
                      Depends: perlapi-5.18.1 which is a virtual package.
 liblocale-gettext-perl : PreDepends: perl-base (>= 5.18.1-3) but 5.14.2-21+rpi2 is installed.
                          PreDepends: perlapi-5.18.1 which is a virtual package.
 libalgorithm-diff-xs-perl : Depends: perl (>= 5.18.1-3) but 5.14.2-21+rpi2 is installed.
                             Depends: perlapi-5.18.1 which is a virtual package.
 libhtml-parser-perl : Depends: perl (>= 5.18.1-3) but 5.14.2-21+rpi2 is installed.
                       Depends: perlapi-5.18.1 which is a virtual package.
 libtext-charwidth-perl : Depends: perl-base (>= 5.18.1-3) but 5.14.2-21+rpi2 is installed.
                          Depends: perlapi-5.18.1 which is a virtual package.
 libossp-uuid-perl : Depends: perl (>= 5.18.1-3) but 5.14.2-21+rpi2 is installed.
                     Depends: perlapi-5.18.1 which is a virtual package.
 libxml-parser-perl : Depends: perl (>= 5.18.1-3) but 5.14.2-21+rpi2 is installed.
                      Depends: perlapi-5.18.1 which is a virtual package.
 libsocket-perl : Depends: perl (>= 5.18.1-3) but 5.14.2-21+rpi2 is installed.
                  Depends: perlapi-5.18.1 which is a virtual package.
 libtext-iconv-perl : Depends: perl-base (>= 5.18.1-3) but 5.14.2-21+rpi2 is installed.
                      Depends: perlapi-5.18.1 which is a virtual package.
 libjson-xs-perl : Depends: perl (>= 5.18.1-3) but 5.14.2-21+rpi2 is installed.
                   Depends: perlapi-5.18.1 which is a virtual package.
 libclone-perl : Depends: perl (>= 5.18.1-3) but 5.14.2-21+rpi2 is installed.
                 Depends: perlapi-5.18.1 which is a virtual package.

in the "Packages" file you can see it's saying 5.14, but when going manually on the server http://mirrordirector.raspbian.org/rasp ... in/p/perl/ I see that the 5.18 is available.

I also checked the debian repository : http://packages.debian.org/jessie/perl and it's clearly stating that the last version of perl is the 5.18 for Jessie.

Can you update the repository index to correct this ?
Thanks.

[plugwash]

Unfortunately due to design limitations in the tools that handle migration between jessie-staging and jessie some packages have migrated from jessie-staging to jessie before things were really ready.

The only real way out of this now is to complete the transition to the new perl but that is going to take a while. Rebuiling hundreds of packages simply takes time.

[Jahangir]

No problem, I completely understand. In every case, having the 5.14 or the 5.18 doesn't made any differences for me.
I just wanted to report the "wrong" index.

[plugwash]

perl has now migrated from jessie-staging to jessie but you may still find some packages perl related packages are uninstallable for a few more days.