RC1 to RC2 question

extraspecialbitter · 2015-11-26 18:57:13

I'm running BL 8.2 RC1 after a flawless install from a thumbnail drive. Will the upgrade to RC2 be as simple as doing a "sudo apt-get update && sudo apt-get dist-upgrade", or is a fresh re-install advised?

Head_on_a_Stick · 2015-11-26 18:59:40

extraspecialbitter wrote:

Will the upgrade to RC2 be as simple as doing a "sudo apt-get update && sudo apt-get dist-upgrade", or is a fresh re-install advised?

I can't remember the details -- do you have the BunsenLabs repositories in /etc/apt/sources.list{.d/}?

What is the output of:

apt-cache policy

It may be that a simple `apt update && apt upgrade` is all that is needed.

nobody0 · 2015-11-26 19:36:25

extraspecialbitter wrote:

I'm running BL 8.2 RC1 after a flawless install from a thumbnail drive. Will the upgrade to RC2 be as simple as doing a "sudo apt-get update && sudo apt-get dist-upgrade", or is a fresh re-install advised?

It should be, otherwise something would be wrong. I suppose Jessie won't get broken by moving from 8.2 to 8.3, and most probably BunsenLabs scripts would stay put.

extraspecialbitter · 2015-11-27 21:48:43

@Head_on_a_stick and @ostrolek - thanks for the replies!

Head_on_a_Stick wrote:

extraspecialbitter wrote:
Will the upgrade to RC2 be as simple as doing a "sudo apt-get update && sudo apt-get dist-upgrade", or is a fresh re-install advised?
I can't remember the details -- do you have the BunsenLabs repositories in /etc/apt/sources.list{.d/}?
What is the output of:
apt-cache policy
It may be that a simple `apt update && apt upgrade` is all that is needed.

My /etc/apt/sources.list is fairly vanilla and so far untouched:

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

deb http://debian.csail.mit.edu/debian/ jessie main non-free contrib
#deb-src http://debian.csail.mit.edu/debian/ jessie main non-free contrib

deb http://security.debian.org/ jessie/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://debian.csail.mit.edu/debian/ jessie-updates main contrib non-free
#deb-src http://debian.csail.mit.edu/debian/ jessie-updates main contrib non-free

# added by bl-welcome
# Multimedia repository
deb http://www.deb-multimedia.org jessie main non-free

And I do seem to have at least one bunsen repo under /etc/apt/sources.list.d:

pablo@eltriunfo=> ls -l sources.list.d
total 12
-rw-r--r-- 1 root root  55 Nov 27 15:47 atlassian-hipchat.list
-rw-r--r-- 1 root root  57 Sep  9 03:00 bunsen.list
-rw-r--r-- 1 root root 176 Nov 27 15:49 google-chrome.list
pablo@eltriunfo=> cat sources.list.d/bunsen.list 
deb http://pkg.bunsenlabs.org/debian bunsen-hydrogen main

Lastly, the output of apt-cache policy:

pablo@eltriunfo=> apt-cache policy
Package files:
 100 /var/lib/dpkg/status
     release a=now
 500 http://dl.google.com/linux/chrome/deb/ stable/main amd64 Packages
     release v=1.0,o=Google, Inc.,a=stable,n=stable,l=Google,c=main
     origin dl.google.com
 500 http://pkg.bunsenlabs.org/debian/ bunsen-hydrogen/main amd64 Packages
     release o=bunsenlabs,n=bunsen-hydrogen,l=bunsenlabs,c=main
     origin pkg.bunsenlabs.org
 500 http://downloads.hipchat.com/linux/apt/ stable/main amd64 Packages
     release n=stable,c=main
     origin downloads.hipchat.com
 500 http://www.deb-multimedia.org/ jessie/non-free amd64 Packages
     release o=Unofficial Multimedia Packages,a=stable,n=jessie,l=Unofficial Multimedia Packages,c=non-free
     origin www.deb-multimedia.org
 500 http://www.deb-multimedia.org/ jessie/main amd64 Packages
     release o=Unofficial Multimedia Packages,a=stable,n=jessie,l=Unofficial Multimedia Packages,c=main
     origin www.deb-multimedia.org
 500 http://debian.csail.mit.edu/debian/ jessie-updates/non-free Translation-en
 500 http://debian.csail.mit.edu/debian/ jessie-updates/main Translation-en
 500 http://debian.csail.mit.edu/debian/ jessie-updates/contrib Translation-en
 500 http://debian.csail.mit.edu/debian/ jessie-updates/non-free amd64 Packages
     release o=Debian,a=stable-updates,n=jessie-updates,l=Debian,c=non-free
     origin debian.csail.mit.edu
 500 http://debian.csail.mit.edu/debian/ jessie-updates/contrib amd64 Packages
     release o=Debian,a=stable-updates,n=jessie-updates,l=Debian,c=contrib
     origin debian.csail.mit.edu
 500 http://debian.csail.mit.edu/debian/ jessie-updates/main amd64 Packages
     release o=Debian,a=stable-updates,n=jessie-updates,l=Debian,c=main
     origin debian.csail.mit.edu
 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
 500 http://security.debian.org/ jessie/updates/non-free amd64 Packages
     release v=8,o=Debian,a=stable,n=jessie,l=Debian-Security,c=non-free
     origin security.debian.org
 500 http://security.debian.org/ jessie/updates/contrib amd64 Packages
     release v=8,o=Debian,a=stable,n=jessie,l=Debian-Security,c=contrib
     origin security.debian.org
 500 http://security.debian.org/ jessie/updates/main amd64 Packages
     release v=8,o=Debian,a=stable,n=jessie,l=Debian-Security,c=main
     origin security.debian.org
 500 http://debian.csail.mit.edu/debian/ jessie/non-free Translation-en
 500 http://debian.csail.mit.edu/debian/ jessie/main Translation-en
 500 http://debian.csail.mit.edu/debian/ jessie/contrib Translation-en
 500 http://debian.csail.mit.edu/debian/ jessie/contrib amd64 Packages
     release v=8.2,o=Debian,a=stable,n=jessie,l=Debian,c=contrib
     origin debian.csail.mit.edu
 500 http://debian.csail.mit.edu/debian/ jessie/non-free amd64 Packages
     release v=8.2,o=Debian,a=stable,n=jessie,l=Debian,c=non-free
     origin debian.csail.mit.edu
 500 http://debian.csail.mit.edu/debian/ jessie/main amd64 Packages
     release v=8.2,o=Debian,a=stable,n=jessie,l=Debian,c=main
     origin debian.csail.mit.edu
Pinned packages:

hhh · 2015-11-27 22:43:19

There should be no reason to do a fresh install. The next release, which will probably not be RC2 but rather the "Official" release, will be very close to the RC1. Maybe a few differences in the Debian packages, which we'll post, and a bunch of upgrades to our Bunsen packages. We'll put together a HowTo on getting caught up without reinstalling when the ISOs are ready.

extraspecialbitter · 2015-11-27 22:54:11

hhh wrote:

There should be no reason to do a fresh install. The next release, which will probably not be RC2 but rather the "Official" release, will be very close to the RC1. Maybe a few differences in the Debian packages, which we'll post, and a bunch of upgrades to our Bunsen packages. We'll put together a HowTo on getting caught up without reinstalling when the ISOs are ready.

That's awesome news, and a testimony to the fact that the BL team is doing its level best to produce an elegantly simple distribution. I'm a long-time sysadmin who is not adverse to tinkering, but I really appreciate a distro that suits my needs right out of the box.

As an aside, today I did an "sudo apt-get update && sudo apt-get upgrade" - just because - so I might be pretty close to what might have been RC2.

hhh · 2015-11-27 23:19:42

Just realize that upgrades to bunsen-configs get written to /usr/share/bunsen/skel (view hidden files) and only automatically write themeselves to ~/ during the actual install. You'll have to manually copy files from, for example /skel/.config to ~/.config after an upgrade. This is intentional.

Though @johnraff, @damo and others are continuing to improve corenominal's and create new, elegant Openbox tools, it's not us who provide an elegant distro. That'd be Debian.

Except for their Live ISO ridiculous system beep during boot. That crap is unbelievably annoying (and flipping LOUD with some speakers) and finding a fix for it was trivial (good job, hhh *pats own back*).

damo · 2015-11-27 23:27:36

hhh wrote:

Just realize that upgrades to bunsen-configs get written to /usr/share/bunsen/skel (view hidden files) and only automatically write themeselves to ~/ during the actual install. You'll have to manually copy files from, for example /skel/.config to ~/.config after an upgrade. This is intentional.
....

How about we post a script to do the job? I know it is an easy task, but for some noobs.....

hhh · 2015-11-27 23:31:37

damo wrote:

How about we post a script to do the job? I know it is an easy task, but for some noobs.....

Pretty please... with sugar on top.

johnraff · 2015-11-29 01:44:17

damo wrote:

hhh wrote:
Just realize that upgrades to bunsen-configs get written to /usr/share/bunsen/skel (view hidden files) and only automatically write themeselves to ~/ during the actual install. You'll have to manually copy files from, for example /skel/.config to ~/.config after an upgrade. This is intentional.
....
How about we post a script to do the job? I know it is an easy task, but for some noobs.....

So what would the script be expected to do? How can it know which files the user wants to keep, and which ones can be safely overwritten, or what entries can be safely appended to existing files...

If a complete overwrite is OK then it's very easy:
delete ~/.config/bunsen/bl-setup (an empty file), logout and in again.

All overwritten files will be backed up, regardless of whether they've been changed or not, resulting in a bunch of backup files splattered all over the place. I realize this is less than optimal behaviour but the job will be done. Existing user settings will remain in the backup files if they're needed, otherwise they can be deleted.

(A rewrite of /usr/lib/bunsen/bunsen-configs/bl-user-setup to backup only files which are different is on my to-do list.)

nobody0 · 2015-11-29 09:10:01

^ Once, the user's setup is setup, no upgrade to the contents of skel, wherever it is situated, wouldn't change user's setup automatically, other than a new user's setup. So, only a new (fresh) install would make the user's setup correctly. Otherwise, the (old) user would have to add the new configs (if the user needs them) manually.

Last edited by nobody0 (2015-11-29 10:19:08)

brontosaurusrex · 2015-11-29 09:24:14

About sources.list, this looks like the new official stuff
http://httpredir.debian.org

Head_on_a_Stick · 2015-11-29 12:53:00

brontosaurusrex wrote:

About sources.list, this looks like the new official stuff
http://httpredir.debian.org

I've been using httpredir for a while now and it seems to work well for me (in London) but I think S11 has reported problems with it in South America.

Sector11 · 2015-11-29 13:03:28

^ and I'll confirm that. It wants to link me up with a debian repo here in Buenos Aires or Chile and at times update/upgrade get stuck so I have hard wired in:

deb http://ftp.us.debian.org/debian/ blah blah

Moral of the story: use what's best for you.
Is it possible that Debian is pushing http://httpredir.debian.org because it's best for them?

Take the test. Every time I go there I end up at different places, but that's the idea, most are slower than: http://ftp.us.debian.org/

pvsage · 2015-11-29 18:26:26

Sector11 wrote:

Every time I go there I end up at different places, but that's the idea

This. Distributed load across multiple servers. If you do fairly frequent updates/upgrades on stable, the slower servers shouldn't be too much of a problem, so long as it always finds a server that isn't rebuilding its database.

johnraff · 2015-11-30 03:32:56

Just so there's no misunderstanding, for those who want to re-import the settings in /usr/share/bunsen/skel and don't mind replacing their personal config files:

johnraff wrote:

If a complete overwrite is OK then it's very easy:
delete ~/.config/bunsen/bl-setup (an empty file), logout and in again.

tknomanzr · 2015-11-30 04:15:10

If you need to reset all your configs, for whatever reason, @damo's BLOB script might be a good idea to backup and restore your configs
BunsenLabs Openbox Configuration Manager

#1 2015-11-26 18:57:13

RC1 to RC2 question

#2 2015-11-26 18:59:40

Re: RC1 to RC2 question

#3 2015-11-26 19:36:25

Re: RC1 to RC2 question

#4 2015-11-27 21:48:43

Re: RC1 to RC2 question

#5 2015-11-27 22:43:19

Re: RC1 to RC2 question

#6 2015-11-27 22:54:11

Re: RC1 to RC2 question

#7 2015-11-27 23:19:42

Re: RC1 to RC2 question

#8 2015-11-27 23:27:36

Re: RC1 to RC2 question

#9 2015-11-27 23:31:37

Re: RC1 to RC2 question

#10 2015-11-29 01:44:17

Re: RC1 to RC2 question

#11 2015-11-29 09:10:01

Re: RC1 to RC2 question

#12 2015-11-29 09:24:14

Re: RC1 to RC2 question

#13 2015-11-29 12:53:00

Re: RC1 to RC2 question

#14 2015-11-29 13:03:28

Re: RC1 to RC2 question

#15 2015-11-29 18:26:26

Re: RC1 to RC2 question

#16 2015-11-30 03:32:56

Re: RC1 to RC2 question

#17 2015-11-30 04:15:10

Re: RC1 to RC2 question

Board footer