ShiftPlusOne
Raspberry Pi Engineer & Forum Moderator
Raspberry Pi Engineer & Forum Moderator
Posts: 5333
Joined: Fri Jul 29, 2011 5:36 pm
Location: The unfashionable end of the western spiral arm of the Galaxy

(New) Official nightly full and cutdown/headless images

Thu May 21, 2015 1:43 pm

In order to reduce the amount of work required to get new releases out, we now have new nightly images. Although we've had nightly images for quite a while, the new images can be taken and uploaded as a stable releases with minimal additional work. This can help us get releases out more frequently, avoiding the situation where users need to get months worth of updates after installing. Finally, it lets us make small incremental changes and allow people to get move involved in the direction of releases by testing and providing feedback.

These images can be found at http://nightly.raspberrypi.org/nightlyimages-v2/

DATE-raspbian-wheezy-1.zip is the normal, full image. It includes the latest firmware, which won't be upgraded using apt-get until a newer version is released as stable. It also has packages installed from the 'staging' component of the repo, which are things we may want to open up for testing but not force on everybody just yet.

DATE-raspbian-wheezy-1-noX.zip is the same as above, but does not have any X11/GUI packages or customizations installed (spindle stage 3).

The firmware in these images is installed from http://nightly.raspberrypi.org/nightlyfirmware-v2/ and then the repo is removed before exporting the image.
The images are built using this tool https://github.com/RPi-Distro/nightly , which is based on the work done by plugwash earlier.

To answer a few question I expect to pop up...

Will these be in NOOBS and/or on the download page?
The plan is to add the latest builds to NOOBS online installs. Right now, the output of spindle for NOOBS does not match what the deployment tool expects, so there's some work to do there. I don't think the nightly images will be on the download page, but a cutdown image will eventually appear alongside the full release.

Can you add/remove <thing> to/from the cutdown image?
Probably not. In order to reduce maintenance time and effort, the image must come from an earlier spindle stage. Changes made to that stage will propagate to the full image, which we don't want to change too much.

What about Jessie?
Working on it. We're not in a rush to get jessie out before it's ready and quite a few bugs have been caught already. We also can't simply switch to the jessie release in raspbian without updating our packages, or things end up horribly broken. We really need to go over each package individually and decide what to do with it (remove, recompile, modify or move straight across). It will be ready when it's ready. When we're a bit further along, jessie images will probably be added as well.

Information on the previous nightlies:
viewtopic.php?f=66&t=80023

Edit: I've hidden the old nightlies to see if anyone is relying on them. If they're not needed, I'll remove the '-v2' from the new ones.

paulie
Posts: 260
Joined: Thu Jan 19, 2012 6:51 pm

Re: (New) Official nightly full and cutdown/headless images

Thu May 21, 2015 8:54 pm

ShiftPlusOne wrote:
What about Jessie?
Working on it. We're not in a rush to get jessie out before it's ready and quite a few bugs have been caught already. We also can't simply switch to the jessie release in raspbian without updating our packages, or things end up horribly broken. We really need to go over each package individually and decide what to do with it (remove, recompile, modify or move straight across). It will be ready when it's ready. When we're a bit further along, jessie images will probably be added as well.

Information on the previous nightlies:
viewtopic.php?f=66&t=80023
Can I request a change to a package for Jessie?
I installed xastir last year, and noticed that it didn't have support for festival (text to speech) compiled in.

I was able to compile from source myself, to get voice announcement of new stations, but it would be nice to have 'out of the box'.

How about a thread for such change requests for Jessie? Necessary?/not necessary? Your thoughts please...
It has been my custom to use Xeyes

ShiftPlusOne
Raspberry Pi Engineer & Forum Moderator
Raspberry Pi Engineer & Forum Moderator
Posts: 5333
Joined: Fri Jul 29, 2011 5:36 pm
Location: The unfashionable end of the western spiral arm of the Galaxy

Re: (New) Official nightly full and cutdown/headless images

Thu May 21, 2015 9:16 pm

paulie, there are two separate repos here. There's upstream raspbian, which has had jessie support for ages and tracks debian as closely as possible. On top of that, we put our own repo, which doesn't have anything to do with the xasir package. In theory, we could add a custom version, but there needs to be a good reason that will benefit a lot of people. Just adding packages because a handful of people need them mostly results in extra maintenance time.

plugwash
Forum Moderator
Forum Moderator
Posts: 3263
Joined: Wed Dec 28, 2011 11:45 pm

Re: (New) Official nightly full and cutdown/headless images

Fri May 22, 2015 12:32 am

Any particular reason for using new distribution and repository urls rather than just continuing with the existing ones?

ShiftPlusOne
Raspberry Pi Engineer & Forum Moderator
Raspberry Pi Engineer & Forum Moderator
Posts: 5333
Joined: Fri Jul 29, 2011 5:36 pm
Location: The unfashionable end of the western spiral arm of the Galaxy

Re: (New) Official nightly full and cutdown/headless images

Fri May 22, 2015 9:29 am

plugwash wrote:Any particular reason for using new distribution and repository urls rather than just continuing with the existing ones?
Nope, just being careful. I don't know how many people were using nightlies and in what way, so it didn't seem right to go changing things there. The plan is to run the old and new images side by side for a bit, so that people get enough warning and a chance to object.

typhoon
Posts: 78
Joined: Sat Jan 28, 2012 8:04 am

Re: (New) Official nightly full and cutdown/headless images

Mon May 25, 2015 8:16 pm

How much cutdown is one of these noX images compared to something made with raspbian-ua-netinst?
Removing packages from a full image was an hassle, so I used raspbian-ua-netinst and right now I'm running fine.
So I'm wondering about the differencies. What would be the output od dpkg -l? Are there any other differencies?

ShiftPlusOne
Raspberry Pi Engineer & Forum Moderator
Raspberry Pi Engineer & Forum Moderator
Posts: 5333
Joined: Fri Jul 29, 2011 5:36 pm
Location: The unfashionable end of the western spiral arm of the Galaxy

Re: (New) Official nightly full and cutdown/headless images

Mon May 25, 2015 9:24 pm

The following commands generate the 'fingerprint' archive. So you can compare DATE-raspbian-wheezy-1-fingerprint.tar and DATE-raspbian-wheezy-1-fingerprint-noX.tar

Code: Select all

dpkg --get-selections > dpkg_selections
dpkg -l > dpkg_l
apt-mark showauto > apt-mark_showauto
debconf-get-selections > debconf_selections
Looking at dpkg_l, I get a diff that looks something like this (after a little cleanup):

Code: Select all

1a2,3
> alsa-base
> alsa-utils
5a8,9
> aspell
> aspell-en
12a17
> blt
17a23
> cgroup-bin
20a27
> consolekit
25a33,35
> cups-bsd
> cups-client
> cups-common
28a39,41
> dbus-x11
> dconf-gsettings-backend:armhf
> dconf-service
31a45,46
> debian-reference-common
> debian-reference-en
32a48,51
> desktop-base
> desktop-file-utils
> dhcpcd5
> dictionaries-common
33a53
> dillo
41a62,64
> epiphany-browser
> epiphany-browser-data
> esound-common
51a75,81
> fontconfig
> fontconfig-config
> fonts-droid
> fonts-freefont-ttf
> fonts-roboto
> freepats
> fuse
53a84
> galculator
59a91,93
> gconf-service
> gconf2
> gconf2-common
62a97,111
> gettext-base
> ghostscript
> gir1.2-glib-2.0
> git
> git-core
> git-man
> gksu
> glib-networking:armhf
> glib-networking-common
> glib-networking-services
> gnome-desktop3-data
> gnome-icon-theme
> gnome-icon-theme-symbolic
> gnome-themes-standard:armhf
> gnome-themes-standard-data
64a114
> gpicview
66a117,135
> gsettings-desktop-schemas
> gsfonts
> gsfonts-x11
> gstreamer0.10-alsa:armhf
> gstreamer0.10-plugins-base:armhf
> gstreamer1.0-alsa:armhf
> gstreamer1.0-libav:armhf
> gstreamer1.0-omx
> gstreamer1.0-plugins-bad:armhf
> gstreamer1.0-plugins-base:armhf
> gstreamer1.0-plugins-good:armhf
> gstreamer1.0-x:armhf
> gtk2-engines:armhf
> gvfs:armhf
> gvfs-backends
> gvfs-common
> gvfs-daemons
> gvfs-fuse
> gvfs-libs:armhf
68a138
> hicolor-icon-theme
69a140,143
> idle
> idle-python2.7
> idle-python3.2
> idle3
82a157,160
> iso-codes
> jackd
> jackd2
> java-common
87a166
> leafpad
88a168,169
> lesstif2:armhf
> libaa1:armhf
95a177,188
> libarchive12:armhf
> libasound2:armhf
> libaspell15
> libasprintf0c2:armhf
> libass4:armhf
> libasyncns0:armhf
> libatasmart4:armhf
> libatk-bridge2.0-0:armhf
> libatk1.0-0:armhf
> libatk1.0-data
> libatlas3-base
> libatspi2.0-0:armhf
96a190,193
> libaudio2:armhf
> libaudiofile1:armhf
> libaudit0
> libavahi-client3:armhf
99a197,204
> libavahi-glib1:armhf
> libavahi-gobject0:armhf
> libavc1394-0:armhf
> libavcodec53:armhf
> libavcodec54:armhf
> libavformat54:armhf
> libavutil51:armhf
> libavutil52:armhf
100a206
> libblas3
101a208,209
> libbluetooth3:armhf
> libbluray1:armhf
111a220,222
> libcaca0:armhf
> libcairo-gobject2:armhf
> libcairo2:armhf
112a224,230
> libcdio-cdda1
> libcdio-paranoia1
> libcdio13
> libcdparanoia0
> libcgroup1
> libchromaprint0:armhf
> libck-connector0:armhf
113a232
> libcolord1:armhf
114a234,236
> libcroco3:armhf
> libcups2:armhf
> libcupsimage2:armhf
115a238
> libcurl3-gnutls:armhf
116a240
> libcwiid1
117a242
> libdatrie1:armhf
119a245,249
> libdbus-glib-1-2:armhf
> libdc1394-22:armhf
> libdca0
> libdconf0:armhf
> libdevmapper-event1.02.1:armhf
120a251,252
> libdirac-encoder0:armhf
> libdirectfb-1.2-9:armhf
122a255,260
> libdrm-nouveau1a:armhf
> libdrm-radeon1:armhf
> libdrm2:armhf
> libdv4:armhf
> libdvdnav4
> libdvdread4
123a262,263
> libenca0
> libenchant1c2a
125a266,267
> liberror-perl
> libesd0:armhf
126a269
> libexif12:armhf
127a271
> libfaad2:armhf
128a273,274
> libfftw3-3:armhf
> libfile-copy-recursive-perl
129a276,287
> libflac8:armhf
> libflite1:armhf
> libfltk1.3:armhf
> libfluidsynth1:armhf
> libfm-data
> libfm-extra4:armhf
> libfm-gtk-data
> libfm-gtk4:armhf
> libfm-modules:armhf
> libfm4:armhf
> libfontconfig1:armhf
> libfontenc1:armhf
131a290,291
> libfribidi0:armhf
> libfuse2:armhf
132a293
> libgconf-2-4:armhf
133a295
> libgd2-xpm:armhf
134a297,300
> libgdk-pixbuf2.0-0:armhf
> libgdk-pixbuf2.0-common
> libgdu0
> libgeoclue0
135a302,309
> libgfortran3:armhf
> libgif4
> libgirepository-1.0-1
> libgksu2-0
> libgl1-mesa-dri:armhf
> libgl1-mesa-glx:armhf
> libglade2-0
> libglapi-mesa:armhf
137a312,313
> libglu1-mesa:armhf
> libgme0
138a315,317
> libgnome-desktop-3-2
> libgnome-keyring-common
> libgnome-keyring0:armhf
141a321,327
> libgphoto2-2:armhf
> libgphoto2-port0:armhf
> libgpm2:armhf
> libgraphite2-2.0.0
> libgs9
> libgs9-common
> libgsm1:armhf
143a330,349
> libgstreamer-plugins-bad1.0-0:armhf
> libgstreamer-plugins-base0.10-0:armhf
> libgstreamer-plugins-base1.0-0:armhf
> libgstreamer0.10-0:armhf
> libgstreamer1.0-0:armhf
> libgtk-3-0:armhf
> libgtk-3-bin
> libgtk-3-common
> libgtk2.0-0:armhf
> libgtk2.0-bin
> libgtk2.0-common
> libgtop2-7
> libgtop2-common
> libgudev-1.0-0:armhf
> libharfbuzz-icu0:armhf
> libharfbuzz0a:armhf
> libhunspell-1.3-0:armhf
> libice6:armhf
> libicu48:armhf
> libid3tag0
145a352,356
> libiec61883-0
> libijs-0.35
> libilmbase6
> libimlib2
> libimobiledevice2
149a361,365
> libjack-jackd2-0:armhf
> libjasper1:armhf
> libjavascriptcoregtk-3.0-0:armhf
> libjbig0:armhf
> libjbig2dec0
150a367
> libjson0:armhf
151a369
> libkate1
156a375,377
> liblapack3
> liblcms1:armhf
> liblcms2-2:armhf
157a379
> liblightdm-gobject-1-0
158a381
> libltdl7:armhf
159a383
> liblvm2app2.2:armhf
161a386
> libmad0
162a388,393
> libmenu-cache1
> libmikmod2:armhf
> libmimic0
> libmms0:armhf
> libmng1:armhf
> libmodplug1
163a395,396
> libmozjs10d
> libmp3lame0:armhf
165a399,400
> libmpg123-0:armhf
> libmtdev1:armhf
167a403
> libnettle4:armhf
174a411,412
> libnotify4:armhf
> libnspr4:armhf
175a414,439
> libnss3:armhf
> libobrender27
> libobt0
> libofa0
> libogg0:armhf
> libopenal-data
> libopenal1:armhf
> libopencore-amrnb0:armhf
> libopencore-amrwb0:armhf
> libopencv-calib3d2.4
> libopencv-contrib2.4
> libopencv-core2.4
> libopencv-features2d2.4
> libopencv-flann2.4
> libopencv-highgui2.4
> libopencv-imgproc2.4
> libopencv-legacy2.4
> libopencv-ml2.4
> libopencv-objdetect2.4
> libopencv-photo2.4
> libopencv-stitching2.4
> libopencv-ts2.4
> libopencv-video2.4
> libopencv-videostab2.4
> libopenexr6
> libopenjpeg2:armhf
176a441,442
> libopus0
> liborc-0.4-0:armhf
181a448,455
> libpango-1.0-0:armhf
> libpango1.0-0:armhf
> libpangocairo-1.0-0:armhf
> libpangoft2-1.0-0:armhf
> libpangox-1.0-0:armhf
> libpangoxft-1.0-0:armhf
> libpaper-utils
> libpaper1:armhf
182a457,458
> libpci3:armhf
> libpciaccess0:armhf
185a462,463
> libpixman-1-0:armhf
> libplist1
187a466,469
> libpolkit-agent-1-0:armhf
> libpolkit-backend-1-0:armhf
> libpolkit-gobject-1-0:armhf
> libpoppler19:armhf
188a471,472
> libportaudio2:armhf
> libportmidi0
189a474,475
> libproxy0:armhf
> libpulse0:armhf
190a477,485
> libqscintilla2-8
> libqt4-dbus:armhf
> libqt4-network:armhf
> libqt4-svg:armhf
> libqt4-xml:armhf
> libqtcore4:armhf
> libqtdbus4:armhf
> libqtgui4:armhf
> libqtwebkit4:armhf
194a490
> libraw1394-11:armhf
196a493,494
> librsvg2-2:armhf
> librsvg2-common:armhf
197a496,497
> libruby1.9.1
> libsamplerate0:armhf
199a500,509
> libsbc1:armhf
> libschroedinger-1.0-0:armhf
> libsclang1
> libscsynth1
> libsdl-image1.2:armhf
> libsdl-mixer1.2:armhf
> libsdl-ttf2.0-0:armhf
> libsdl1.2debian:armhf
> libsecret-1-0:armhf
> libsecret-common
203a514,515
> libsgutils2-2
> libshout3:armhf
206a519,527
> libsm6:armhf
> libsmbclient:armhf
> libsmpeg0:armhf
> libsndfile1:armhf
> libsoundtouch0:armhf
> libsoup-gnome2.4-1:armhf
> libsoup2.4-1:armhf
> libspandsp2
> libspeex1:armhf
207a529
> libsrtp0
208a531
> libssh-4:armhf
210a534
> libstartup-notification0
213a538
> libswscale2:armhf
215a541,542
> libtag1-vanilla:armhf
> libtag1c2a:armhf
218a546
> libtdb1:armhf
221a550,553
> libthai-data
> libthai0:armhf
> libtheora0:armhf
> libtiff4:armhf
224a557
> libts-0.0-0:armhf
227a561
> libusbmuxd1
232a567,579
> libva1:armhf
> libvisual-0.4-0:armhf
> libvisual-0.4-plugins:armhf
> libvo-aacenc0:armhf
> libvo-amrwbenc0:armhf
> libvorbis0a:armhf
> libvorbisenc2:armhf
> libvorbisfile3:armhf
> libvpx1:armhf
> libvte-common
> libvte9
> libwavpack1:armhf
> libwayland0:armhf
233a581,583
> libwebkitgtk-3.0-0:armhf
> libwebkitgtk-3.0-common
> libwebp2:armhf
234a585,590
> libwildmidi-config
> libwildmidi1:armhf
> libwnck-3-0
> libwnck-3-common
> libwnck-common
> libwnck22
237a594,596
> libx11-xcb1:armhf
> libx264-123:armhf
> libx264-130:armhf
240a600,606
> libxaw7:armhf
> libxcb-glx0:armhf
> libxcb-render0:armhf
> libxcb-shape0:armhf
> libxcb-shm0:armhf
> libxcb-util0:armhf
> libxcb-xfixes0:armhf
241a608,610
> libxcomposite1:armhf
> libxcursor1:armhf
> libxdamage1:armhf
243a613,625
> libxfce4ui-1-0
> libxfce4util-bin
> libxfce4util-common
> libxfce4util4
> libxfconf-0-2
> libxfixes3:armhf
> libxfont1
> libxft2:armhf
> libxi6:armhf
> libxinerama1:armhf
> libxkbcommon0:armhf
> libxkbfile1:armhf
> libxklavier16
244a627
> libxmu6:armhf
245a629,645
> libxp6:armhf
> libxpm4:armhf
> libxrandr2:armhf
> libxrender1:armhf
> libxres1:armhf
> libxslt1.1:armhf
> libxss1:armhf
> libxt6:armhf
> libxtst6:armhf
> libxv1:armhf
> libxvidcore4:armhf
> libxxf86dga1:armhf
> libxxf86vm1:armhf
> libyaml-0-2:armhf
> libzbar0
> lightdm
> lightdm-gtk-greeter
252a653,668
> lxappearance
> lxde
> lxde-common
> lxde-core
> lxde-icon-theme
> lxinput
> lxmenu-data
> lxpanel
> lxpanel-data
> lxpolkit
> lxrandr
> lxsession
> lxsession-edit
> lxshortcut
> lxtask
> lxterminal
258a675,676
> menu
> menu-xdg
259a678
> minecraft-pi
272a692,693
> netsurf-common
> netsurf-gtk
274a696,700
> nuscratch
> obconf
> omxplayer
> openbox
> openresolv
279a706
> oracle-java8-jdk
282a710,712
> pciutils
> pcmanfm
> penguinspuzzle
285a716,717
> pipanel
> pistore
287a720,722
> policykit-1
> poppler-data
> poppler-utils
289a725,728
> pypy-setuptools
> pypy-upstream
> pypy-upstream-dev
> pypy-upstream-doc
290a730,733
> python-dbus
> python-dbus-dev
> python-gi
> python-minecraftpi
291a735,739
> python-numpy
> python-picamera
> python-pifacecommon
> python-pifacedigitalio
> python-pygame
292a741,743
> python-serial
> python-support
> python-tk
294a746,762
> python3
> python3-minecraftpi
> python3-minimal
> python3-numpy
> python3-picamera
> python3-pifacecommon
> python3-pifacedigital-scratch-handler
> python3-pifacedigitalio
> python3-pygame
> python3-rpi.gpio
> python3-serial
> python3-tk
> python3.2
> python3.2-minimal
> qdbus
> qjackctl
> raspberrypi-artwork
295a764,765
> raspberrypi-net-mods
> raspberrypi-ui-mods
300a771,772
> rpi-update
> rsync
301a774
> ruby1.9.1
302a776
> scratch
306a781,785
> smartsim
> smbclient
> sonic-pi
> squeak-plugins-scratch
> squeak-vm
309a789,791
> supercollider
> supercollider-common
> supercollider-server
315a798
> tcl8.5
316a800,801
> timidity
> tk8.5
318a804,805
> tsconf
> ttf-dejavu-core
321a809
> udisks
322a811,812
> update-inetd
> usbmuxd
327a818
> weston
330a822,823
> wolfram-engine
> wpagui
331a825,830
> x11-common
> x11-utils
> x11-xkb-utils
> x11-xserver-utils
> x2x
> xarchiver
332a832,838
> xdg-utils
> xfce-keyboard-shortcuts
> xfce4-mixer
> xfconf
> xfonts-encodings
> xfonts-utils
> xinit
334a841,849
> xpdf
> xserver-common
> xserver-xorg
> xserver-xorg-core
> xserver-xorg-input-all
> xserver-xorg-input-evdev
> xserver-xorg-input-synaptics
> xserver-xorg-video-fbdev
> xserver-xorg-video-fbturbo
335a851,852
> zenity
> zenity-common

leecade
Posts: 1
Joined: Mon May 25, 2015 6:19 pm

Re: (New) Official nightly full and cutdown/headless images

Tue May 26, 2015 2:31 am

Looking forward Jessie

User avatar
Douglas6
Posts: 4453
Joined: Sat Mar 16, 2013 5:34 am
Location: Chicago, IL

Re: (New) Official nightly full and cutdown/headless images

Tue May 26, 2015 3:32 am

leecade wrote:Looking forward [to] Jessie
Be careful what you wish for.

typhoon
Posts: 78
Joined: Sat Jan 28, 2012 8:04 am

Re: (New) Official nightly full and cutdown/headless images

Tue May 26, 2015 9:20 am

Thanks, that info will be handy.

typhoon
Posts: 78
Joined: Sat Jan 28, 2012 8:04 am

Re: (New) Official nightly full and cutdown/headless images

Tue May 26, 2015 4:51 pm

I noticed the cutdown image still has a size around 4GB, mostly empty space.
Could it be possible to have the FS reduced to 1GB or 2GB and provide the option to expand them later with rpi-config?
I suppose this could be done after the image is built so it shouldn't be too much of an issue.

ShiftPlusOne
Raspberry Pi Engineer & Forum Moderator
Raspberry Pi Engineer & Forum Moderator
Posts: 5333
Joined: Fri Jul 29, 2011 5:36 pm
Location: The unfashionable end of the western spiral arm of the Galaxy

Re: (New) Official nightly full and cutdown/headless images

Tue May 26, 2015 5:05 pm

Maybe if someone sends a pull request here https://github.com/RPi-Distro/nightly

typhoon
Posts: 78
Joined: Sat Jan 28, 2012 8:04 am

Re: (New) Official nightly full and cutdown/headless images

Tue May 26, 2015 6:06 pm

mmm, shouldn't be better make a suggestion on https://github.com/RPi-Distro/spindle?
I understand that's what is used to build the image(s).
I wouldn't know how to do it so I can only "ask" or "suggest", sadly.

ShiftPlusOne
Raspberry Pi Engineer & Forum Moderator
Raspberry Pi Engineer & Forum Moderator
Posts: 5333
Joined: Fri Jul 29, 2011 5:36 pm
Location: The unfashionable end of the western spiral arm of the Galaxy

Re: (New) Official nightly full and cutdown/headless images

Tue May 26, 2015 6:18 pm

Since I've only recently inherited spindle maintenance, I'm a little reluctant to change things without knowing why they were done the way they are. Alex has a script in there to shrink an image, but it's not used when exporting the image for some reason. Maybe he found that something fails in a subtle way, or maybe there's another reason that it's desirable to have an image of a predefined size.

The 'nightly' script uses spindle and could be modified to shrink the image as well.

typhoon
Posts: 78
Joined: Sat Jan 28, 2012 8:04 am

Re: (New) Official nightly full and cutdown/headless images

Tue May 26, 2015 6:30 pm

I was "examining" the spinde git and noticed the shrink_image script, which does shrink the image, so I suppose it should be only a matter of using it in nightly.
Now, I don't have any idea about why it's not used as a cutdown image is fine with 1GB.
Excluding imaging to the SD faster (which is a trivial matter), it would make the cutdown image installable on smaller SD cards.
Well, it's just an idea, if it's a problem nevermind, scrap it.
But I'd like to know the reason why shrink_image script is not used (I suppose it wouldn't make sense on a stock image?).

ShiftPlusOne
Raspberry Pi Engineer & Forum Moderator
Raspberry Pi Engineer & Forum Moderator
Posts: 5333
Joined: Fri Jul 29, 2011 5:36 pm
Location: The unfashionable end of the western spiral arm of the Galaxy

Re: (New) Official nightly full and cutdown/headless images

Tue May 26, 2015 6:33 pm

typhoon wrote:But I'd like to know the reason why shrink_image script is not used
Me too

Htaborda
Posts: 21
Joined: Sun Apr 12, 2015 1:08 am
Location: Amsterdam

Re: (New) Official nightly full and cutdown/headless images

Sun May 31, 2015 12:07 pm

Please hurry the Jessie version. Pointless discussions aside, there's a lot of outdated packages in Wheezy (transmission, boinc, fail2ban, etc...) that have much more recent versions in Jessie. And I believe installing select packages from other repos is a recipe for disaster....

ShiftPlusOne
Raspberry Pi Engineer & Forum Moderator
Raspberry Pi Engineer & Forum Moderator
Posts: 5333
Joined: Fri Jul 29, 2011 5:36 pm
Location: The unfashionable end of the western spiral arm of the Galaxy

Re: (New) Official nightly full and cutdown/headless images

Sun May 31, 2015 4:39 pm

Htaborda wrote:Please hurry the Jessie version.
The only way it's going to speed up is if people volunteer to tweak spindle a little and do some testing.

I think I have almost all the packages sorted out, so now it's a matter of creating and testing images.

One thing I haven't had a look at is whether setting locales and keymaps in raspi-config (and setting the OS 'flavour' in NOOBS) works 100% of the time. Systemd has moved some of the settings to different files, but uses the old ones as a fallback. If something changes the locales using the new files, it will probably override the old files. I've added an init system check and sorted out the rest of raspi-config, but there are the little things to worry about.

If you just want to use Jessie, you can. Just don't use the raspberrypi.org repo yet.

ibrahimansari
Posts: 82
Joined: Sat Aug 16, 2014 8:22 am

Re: (New) Official nightly full and cutdown/headless images

Wed Jun 03, 2015 11:43 am

Htaborda wrote:Please hurry the Jessie version. Pointless discussions aside, there's a lot of outdated packages in Wheezy (transmission, boinc, fail2ban, etc...) that have much more recent versions in Jessie. And I believe installing select packages from other repos is a recipe for disaster....
Yup, I am waiting for Jessie, because libreoffice, clementine, etc. are necessary but they're obsolete in wheezy.
I is the master of Linux, Windows and the computer realms.
But always with a Pi(e). ;)

User avatar
DougieLawson
Posts: 34114
Joined: Sun Jun 16, 2013 11:19 pm
Location: Basingstoke, UK
Contact: Website

Re: (New) Official nightly full and cutdown/headless images

Wed Jun 03, 2015 4:25 pm

ibrahimansari wrote: Yup, I am waiting for Jessie, because libreoffice, clementine, etc. are necessary but they're obsolete in wheezy.
With a bit of messing about with /etc/apt/preferences

Code: Select all

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 an update to /etc/apt/sources.list

Code: Select all

deb http://mirrordirector.raspbian.org/raspbian/ wheezy main contrib non-free rpi
deb http://mirrordirector.raspbian.org/raspbian/ jessie main contrib non-free rpi
apt-get update && apt-get install foobar-jessie-package-thing
will install a Jessie package rather than the Wheezy version. I've done that to get MariaDB installed instead of MySQL.
Microprocessor, Raspberry Pi & Arduino Hacker
Mainframe database troubleshooter
MQTT Evangelist
Twitter: @DougieLawson

2012-18: 1B*5, 2B*2, B+, A+, Z, ZW, 3Bs*3, 3B+

Any DMs sent on Twitter will be answered next month.

ShiftPlusOne
Raspberry Pi Engineer & Forum Moderator
Raspberry Pi Engineer & Forum Moderator
Posts: 5333
Joined: Fri Jul 29, 2011 5:36 pm
Location: The unfashionable end of the western spiral arm of the Galaxy

Re: (New) Official nightly full and cutdown/headless images

Wed Jun 03, 2015 4:35 pm

I would advise against messing with sources.list unless you understand the entirety of Dougie's post and the risks.

User avatar
Lombra
Posts: 67
Joined: Tue Sep 16, 2014 12:41 am
Location: Sweden

Re: (New) Official nightly full and cutdown/headless images

Mon Jun 08, 2015 9:21 pm

Seems to be no images available on that link at the moment.

How stable could one expect a nightly noX image to be compared to say, a future one from the downloads page? (which is still some time off then?)

ShiftPlusOne
Raspberry Pi Engineer & Forum Moderator
Raspberry Pi Engineer & Forum Moderator
Posts: 5333
Joined: Fri Jul 29, 2011 5:36 pm
Location: The unfashionable end of the western spiral arm of the Galaxy

Re: (New) Official nightly full and cutdown/headless images

Mon Jun 08, 2015 10:34 pm

There's a bit of a disk space issue and I cleared out older images after backing them up. One should start building tonight and be ready in the morning (GMT).

As far as stability goes, the plan is pretty much to just take one of these images and pop it on the download page as a release once in a while (whether or not there have been any major changes). It's the same an up to date install after running rpi-update and some package updates queued up for the next release. The firmware folk don't push firmware they think might be problematic, but there may be an occasional snafu. The firmware is still managed by apt and if we do a stable firmware release, you'll get that update normally. Same goes for the other packages. I test things before throwing them in the repo (outside of the 'untested' component). If there's something I've missed, hopefully you'd point it out, we'd fix it, you'd run apt-get upgrade and would be good to go. So in a way, the more people use these images, the less likely there are to be undiscovered problems.

I'd have no hesitation using these images myself.
Lombra wrote:which is still some time off then?
I'm pretty much done with my side of things for the next release, but have underestimated how much work needs to be done by some of the other folk. A bit of a lesson in parallelising things a bit more in the future.

User avatar
Lombra
Posts: 67
Joined: Tue Sep 16, 2014 12:41 am
Location: Sweden

Re: (New) Official nightly full and cutdown/headless images

Mon Jun 15, 2015 1:01 am

Ok, thanks. Am I right in thinking I could use apt-get upgrade to revert to the latest stable stuff if I wanted to? Would I be wasting my time? Would there be remnants of the "unstable" stuff, or any potential conflicts?

ShiftPlusOne
Raspberry Pi Engineer & Forum Moderator
Raspberry Pi Engineer & Forum Moderator
Posts: 5333
Joined: Fri Jul 29, 2011 5:36 pm
Location: The unfashionable end of the western spiral arm of the Galaxy

Re: (New) Official nightly full and cutdown/headless images

Mon Jun 15, 2015 4:31 am

Lombra wrote:Ok, thanks. Am I right in thinking I could use apt-get upgrade to revert to the latest stable stuff if I wanted to? Would I be wasting my time? Would there be remnants of the "unstable" stuff, or any potential conflicts?

Code: Select all

aptitude search '~o'
That will show you the packages which are not from any current repo. You can then run apt-get install --reinstall on the ones you want to downgrade.

I can't guarantee that there won't be anything left behind though. Some config files may end up changed, or perhaps something in the image creation process itself has changed, which you wouldn't be able to automatically undo, for example. That's a little more on the paranoid side though. I wouldn't commit or upload something which hasn't been tested or isn't going to end up in stable image eventually. There may also be large changes which are a little trickier to undo (like the recent network setup change).

Having said that, stick to the actual releases if you don't want to help with testing. My motivation for these images is to get feedback, make upcoming changes available for testing to more people and reduce my workload (by automating as much as possible). They're not meant for general use.

Return to “Raspbian”