The correct way to upgrade to Stretch?

RogerH · 2016-09-06 14:55:34

This is already done on my machine, and it doesn't seem broken, but here's what I did.

Updated my sources.list to use Stretch instead of Jessie:

# 

# deb cdrom:[Debian GNU/Linux 8 _Jessie_ - Official Snapshot amd64 LIVE/INSTALL Binary 20160706-02:22]/ jessie contrib main non-free

# deb cdrom:[Debian GNU/Linux 8 _Jessie_ - Official Snapshot amd64 LIVE/INSTALL Binary 20160706-02:22]/ jessie contrib main non-free

deb http://httpredir.debian.org/debian stretch main non-free contrib
#deb-src http://httpredir.debian.org/debian jessie main non-free contrib

deb http://security.debian.org/ stretch/updates main contrib non-free
#deb-src http://security.debian.org/ jessie/updates main contrib non-free

# jessie-updates, previously known as 'volatile'
deb http://httpredir.debian.org/debian stretch-updates main contrib non-free
#deb-src http://httpredir.debian.org/debian jessie-updates main contrib non-free

deb http://repo.linrunner.de/debian stretch main

I then did a

sudo apt-get update

then

sudo apt-get dist-upgrade

and rebooted. So far, so good, although when I go to Preferences > Appearance there is only one theme (Raleigh) installed. Did I do this right?

damo · 2016-09-06 15:04:25

Explanation in this HowTo: BL/jessie stable to stretch/sid

It is a good ol' gtk2 issue

osteoboon · 2016-09-12 22:17:35

Hi all.

My first post here. Thanks to all who have continued CrunchBang as BL. It looks pretty neat. I read the forum rules, and I searched for an answer to my question below, but found none.

So it seems pretty clear from several posts on this or related subjects that upgrading from Jessie to Stretch within BL is discouraged. I understand some people (like the OP) are doing it anyway, but as much as possible, I'd like to stay within the bounds of the official BL recommendations, so I'm very reluctant to upgrade to Stretch.

That said, however, I'd also very much like to install sucrose (the SugarOS interface) in BL, and I know it's not available due to some communication issues which arose during Debian's freeze for Jessie.

So my question is, is there a rough estimate on when BL will move from Jessie sources to Stretch sources? If it is likely to be within the next 6 months, then I'm inclined to wait patiently. But if it's likely to be more than 8 months, then I'm thinking that maybe I should do what the original poster in this thread did; just bite the bullet and try upgrading BL to Stretch (and do it now, immediately after installing BL rather than doing weeks or months worth of work in BL first, at which point I would first do a backup before attempting the upgrade to Stretch).

All I really want is to have sucrose installed in my official BL running on a 13" Mid-2012 Macbook Air. If there's any way to do that (short of upgrading Jessie to Stretch) while keeping all other aspects of BL preserved, then I'd like to do that. I did configure jessie-backports, but sucrose is apparently not in that repository (E: Unable to locate package sucrose).

Again, thanks very much to everyone who continued CrunchBang as BL, and thanks in advance for any suggestions here!

Last edited by osteoboon (2016-09-12 23:30:29)

damo · 2016-09-13 00:01:36

is there a rough estimate on when BL will move from Jessie sources to Stretch sources?

It depends on the Debian timetable - so it will be whenever Stretch becomes Stable.

Have you tried backporting it yourself?

tynman · 2016-09-13 02:57:45

Looking at the SugarOS website (http://wiki.sugarlabs.org/go/Debian) it looks like it should install just fine onto a Debian/Jessie/Stable system -- aside from the fact that you need to install it from the Debian/Stretch/Testing repositories. But whether that would "...keep[...] all other aspects of BL preserved..." or trash your BL installation is a question no one can answer without trying it.

On the same web page, it say the SugarOS is a "desktop". It's hard to know what they mean by that exactly ("desktop" is an ambiguous term). I infer that if you installed in alongside BL, you would end up with two "desktops", (1) the "BL desktop" based on Openbox, and (2) an alternate desktop based on SugarOS, such that when you boot your computer you would have to choose one desktop or the other in the LightDM login screen. That sounds viable to me, but that's just a guess, I have no idea what would actually happen.

damo · 2016-09-13 04:02:49

tynman wrote:

Looking at the SugarOS website (http://wiki.sugarlabs.org/go/Debian) it looks like it should install just fine onto a Debian/Jessie/Stable system -- aside from the fact that you need to install it from the Debian/Stretch/Testing repositories. But whether that would "...keep[...] all other aspects of BL preserved..." or trash your BL installation is a question no one can answer without trying it.
....

I think those instructions would be disastrous for BunsenLabs. I just tried it in a VM, with --simulate, and it would upgrade the whole system, as well as removing bunsen-themes, amongst other packages. Assuming you fixed any breakages, it would now be a Testing system, not Stable with extra packages from Stretch.

Whoever wrote that Installation page needs shooting!

EDIT: I built a backported package, which wouldn't install without errors on BL. Using 'sudo apt-get -f install' would remove a bunch of stuff, and install a load of gnome packages. No thanks!

Last edited by damo (2016-09-13 04:17:46)

ohnonot · 2016-09-13 04:59:01

damo wrote:

Whoever wrote that Installation page needs shooting!

indeed:

someone who needs shooting, over at sugar labs wrote:

install Debian Jessie in the usual way, see debian.org,
change /etc/apt/sources.list to use the Debian Stretch testing release,
sudo sed -i 's/jessie/stretch/g' /etc/apt/sources.list
update the package lists,
sudo apt update

wtf?
why tell people to install jessie in the first place???

Head_on_a_Stick · 2016-09-13 06:39:19

Rather than converting to stretch (not advised btw), you could try https://wiki.debian.org/SimpleBackportCreation

EDIT: Sorry damo!

Last edited by Head_on_a_Stick (2016-09-13 18:28:01)

pvsage · 2016-09-13 08:57:59

^ Looks like Damo's already tested that and noted potential consequences.

To answer the OP's question in the thread title: Sticky: Tracking Debian testing/unstable with BunsenLabs.

nycace36 · 2017-01-18 21:45:55

Apparently, the announcement of Debian Installer Stretch RC 1 release came out several days ago; see https://lists.debian.org/debian-devel-a … 00004.html.

In light of this, am wondering what additional suggestions to the above (if possible, briefly!) are appropriate for "correctly" upgrading BL Jessie to the current Stretch ??

Sure, I've seen most of the Sticky: Tracking Debian testing/unstable with BunsenLabs.

Thanks.

Head_on_a_Stick · 2017-01-18 23:11:58

nycace36 wrote:

"correctly" upgrading BL Jessie to the current Stretch ??

I don't know about upgrading but I have a stretch-based BunsenLabs system on my laptop:

https://forums.bunsenlabs.org/viewtopic … 804#p43804

I installed it by first laying down a basic (CLI-only) stretch system using the debootstrap(8) command and this guide:

https://www.debian.org/releases/stable/ … 03.html.en

The RC1 installer could also be used but it may not work as consistently as debootstrap(8)

Once the stretch system was installed, I downloaded and ran the bunsen-netinstall script, instructions here:

https://github.com/BunsenLabs/bunsen-netinstall

I changed pkg-norecs to https://gist.github.com/Head-on-a-Stick … c86ca3720b and commented out bunsen-themes from pkg-recs and the installation went through just fine.

YMMV

KrunchTime · 2017-01-22 23:24:37

Tracking Debian Unstable under BL on two different machines here without any major issues, although I performed the installs using johnraff's manual netinstall instructions.

Last edited by KrunchTime (2017-01-22 23:25:18)

johnraff · 2017-01-23 08:49:40

You can now save a little time and effort by using the netinstall "helium-dev" branch. App lists etc already edited. The theme, though, is currently set to "Arc" which looks quite different from Bunsen. Just a placeholder till we get a Bunsen theme that works with GTK3 on Stretch. Other things will be broken for sure. This is just for testing and development atm.

Head_on_a_Stick · 2017-01-24 22:36:25

johnraff wrote:

The theme, though, is currently set to "Arc"

I think that gtk2-engines-pixbuf needs to be added to pkg-norecs for the Arc theme to work properly.

Also, the `synclient` command won't work without xserver-xorg-input-synaptics and that won't work unless an Xorg configuration file is used to prefer synaptics over libinput.

If we switch to libinput then xinput(1) could be used in the autostart file instead of `synclient` but the syntax is machine-dependent:

https://wiki.archlinux.org/index.php/Li … figuration

EDIT: correction: if the synaptics driver is installed then that is actually loaded in preference over libinput, which is nice

Anyway, this should probably go in a new thread...

Last edited by Head_on_a_Stick (2017-01-24 22:42:30)

johnraff · 2017-01-27 04:35:07

Head_on_a_Stick wrote:

this should probably go in a new thread...

Please.
In the Dev section I think.

I'll put tweaks like that into the helium-dev installer asap so we can see how they work out.
Of course, feel free to continue sending PR's directly to GitHub, especially if you think they don't need a lot of discussion first.

huuhaa · 2017-02-18 14:17:59

Any new information about recommended way to upgrade?

Head_on_a_Stick · 2017-02-18 22:30:20

huuhaa wrote:

Any new information about recommended way to upgrade?

There is a draft version of the stretch release notes that could be used as a reference for upgrading the Debian packages:

https://www.debian.org/releases/stretch … ng.en.html

However, we currently have no stretch-specific BunsenLabs packages — the standard jessie-based versions would have to be used for now.

huuhaa · 2017-02-19 17:10:57

Head_on_a_Stick wrote:

There is a draft version of the stretch release notes that could be used as a reference for upgrading the Debian packages:
https://www.debian.org/releases/stretch … ng.en.html
However, we currently have no stretch-specific BunsenLabs packages — the standard jessie-based versions would have to be used for now.

So basicly by quick glance you change your sources.list (and other sorces.list also, like the ones in /etc/apt/sourced.list.d/ folder) from jessie to stretch, but that has said to be bad idea in this thread.. Sure that link contains s***load of other things to do also. Too bad if there's no quick and easy way to do it. There's always a "danger" to end up to be distrohopper once again, doesen't require any more work after all.

But if I do all that, will my Bunsen themes etc be removed, or can I reinstall the same which are used with jessie?

PS. Sorry for stupid questions, but this seems far more complex than normal upgade of debian stable to non-stable (which I have done in history, but maybe incorrect way but working results)

Head_on_a_Stick · 2017-02-19 17:18:42

huuhaa wrote:

this seems far more complex than normal upgade of debian stable to non-stable

I can assure you that the technique is very similar to that which was advised by debian.org for the wheezy to jessie transition:

https://www.debian.org/releases/stable/ … ng.en.html

I agree that the process does look quite complicated and involved but surely it is better to be safe than sorry, no?

EDIT: it is very important to note that stretch is still in the *testing* branch of Debian and any `dist-upgrade`s for "production" machinery should probably not be attempted until after the official release of Debian 9.0

Last edited by Head_on_a_Stick (2017-02-19 17:20:54)

huuhaa · 2017-02-19 20:00:32

Head_on_a_Stick wrote:

I can assure you that the technique is very similar to that which was advised by debian.org for the wheezy to jessie transition:
https://www.debian.org/releases/stable/ … ng.en.html
I agree that the process does look quite complicated and involved but surely it is better to be safe than sorry, no?
EDIT: it is very important to note that stretch is still in the *testing* branch of Debian and any `dist-upgrade`s for "production" machinery should probably not be attempted until after the official release of Debian 9.0

Thanks! I will backup my data, I don't have to disable pinning since I haven't pin anything... Basicly I just backup my "critical" data and try to do basic update as I'm used to before. If I end up breaking anything, I have the mirror where to find the quilty one. But I might ask for your help for something if things seems to be fixable but just can't figure it out.

Anyway thanks for everything so far.

Edit: Everything went ok. Just some themes changed (firefox & teminal etc all has blue top bar, I don't remember what the color was before but quess it was dark or gray....).

Edit 2: Also menus seems to be almost white now with black text in it, while those used to be dark with white text. Hopefully there will be bunsen settings package for stretch (or similar) available soon to fix these issues.

BTW. Why would apt-get autoremove want to remove such a lot amount of packages?

Last edited by huuhaa (2017-02-20 07:47:07)

#1 2016-09-06 14:55:34

The correct way to upgrade to Stretch?

#2 2016-09-06 15:04:25

Re: The correct way to upgrade to Stretch?

#3 2016-09-12 22:17:35

Re: The correct way to upgrade to Stretch?

#4 2016-09-13 00:01:36

Re: The correct way to upgrade to Stretch?

#5 2016-09-13 02:57:45

Re: The correct way to upgrade to Stretch?

#6 2016-09-13 04:02:49

Re: The correct way to upgrade to Stretch?

#7 2016-09-13 04:59:01

Re: The correct way to upgrade to Stretch?

#8 2016-09-13 06:39:19

Re: The correct way to upgrade to Stretch?

#9 2016-09-13 08:57:59

Re: The correct way to upgrade to Stretch?

#10 2017-01-18 21:45:55

Re: The correct way to upgrade to Stretch?

#11 2017-01-18 23:11:58

Re: The correct way to upgrade to Stretch?

#12 2017-01-22 23:24:37

Re: The correct way to upgrade to Stretch?

#13 2017-01-23 08:49:40

Re: The correct way to upgrade to Stretch?

#14 2017-01-24 22:36:25

Re: The correct way to upgrade to Stretch?

#15 2017-01-27 04:35:07

Re: The correct way to upgrade to Stretch?

#16 2017-02-18 14:17:59

Re: The correct way to upgrade to Stretch?

#17 2017-02-18 22:30:20

Re: The correct way to upgrade to Stretch?

#18 2017-02-19 17:10:57

Re: The correct way to upgrade to Stretch?

#19 2017-02-19 17:18:42

Re: The correct way to upgrade to Stretch?

#20 2017-02-19 20:00:32

Re: The correct way to upgrade to Stretch?

Board footer