Tracking Debian testing/unstable with BunsenLabs

MAC the Bloody · 2015-10-07 05:42:39

Update: Things are still working well here. I have several things that need a java runtime environment to work. When I proceeded to install the openjdk-7 version I was warned about several bugs. After reading the bug reports I determined that some would not effect me and some might, but I decided to install.

Freenet, YaCy, i2p, and the Tor browser bundle are all working properly. The system is using about 1 Gig less Ram than it did to run all this stuff on Mint, but is also using noticably more CPU cycles. Despite that, everything seems to be functioning well after a couple of days with all that stuff running.

So far so good. No problems in real world usage. Yay BunSid!

tknomanzr · 2015-10-07 06:14:24

Gdebi is also not working for me. Not that I use it all that much, given dpkg -i works just as well.

dolly · 2015-10-07 09:29:42

I have "inherited" a hd from a friend where I am thinking of installing "Hydrogen" and do an upgrade to unstable. Do I need to do any further changes other than to set my source list to unstable instead of jessie?

tknomanzr · 2015-10-07 10:23:18

That is all that is needed atm. you should probably also get apt-listbugs.

dolly · 2015-10-07 10:58:55

Thank you for the swift reply teknomanzr. @admins - are there any thoughts of creating a help/support section for testing/unstable?

MAC the Bloody · 2015-10-07 11:07:46

@dolly Debian recommended proceedure is to install as little software as possible before upgrading. Then upgrade to testing before upgrading to Sid.

What I did was as follows.
Install Hydrogen.
Skip the welcome script.
Update and dist upgrade manually.
Install apt-fast to speed things up for the following upgrades.
Changes sources to testing, then update and dist-upgrade.
Reboot, then change to Sid and update, dist-upgrade again.
Reboot into Sid.
Checked that the system was working ok and then, and only then, started installing the extra things I needed-wanted.

Last edited by MAC the Bloody (2015-10-07 11:58:02)

dolly · 2015-10-07 11:47:14

Thanks for the explanation Anaconda. Will do an install and try it out. Time to cross fingers.

MAC the Bloody · 2015-10-07 12:00:56

@tknomanzr Are you sure gdebi is not working? If I try to call "gdebi" from the alt menu nothing happens. If I call gdebi-gtk it works. It also works for me through the right click dialogue in thunar on *.deb packages.

dolly · 2015-10-08 11:05:38

Fingers uncrossed, for now.

mrneilypops · 2015-10-08 17:11:26

@Anaconda

Then upgrade to testing before upgrading to Sid.

Is there a reason why you upgrade to Sid through Testing?
I have always upgraded Debian from Stable to Sid by simply updating /etc/apt/sources.list on a pure Debian install.

Cheers
Neil

dolly · 2015-10-08 18:01:59

I wondered about that too. But I did it like that. First to testing, then to Sid. The jump to testing from stable showed a lot of upgrades. However from testing to Sid it were not so many.

mrneilypops · 2015-10-08 18:45:49

@dolly
Yep...interesting...I just wondered if there is some advantage to using the ->testing -> sid route...
Maybe I am missing something...always possible

Head_on_a_Stick · 2015-10-08 18:52:48

mrneilypops wrote:

I just wondered if there is some advantage to using the ->testing -> sid route...

It is the recommended approach as it keeps the version jumps as low as possible.
https://www.debian.org/doc/manuals/debi … de_upgrade

dolly · 2015-10-08 21:07:41

Thanks for the illuminating link Head_on_a_stick

KrunchTime · 2015-10-09 06:38:37

Hmm...I've always upgraded directly from stable to unstable as well. Good info to know for the future, though. Thank you to both Anaconda and HoaS for the enlightenment. I can also vouch for Anaconda's suggestion to install as little software as possible before upgrading from stable to testing/unstable.

dolly wrote:

The jump to testing from stable showed a lot of upgrades. However from testing to Sid it were not so many.

You would have seen as many upgrades, maybe more, had you went from Stable to Unstable/Sid. Testing and Unstable/Sid are somewhat close as far as package versions.

Last edited by KrunchTime (2015-10-09 06:49:14)

hhh · 2015-10-09 07:08:49

I'm going direct (ha! waldorf to jessie to sid) because it's early in the release cycle, so screw it. Still...

686 upgraded, 0 newly installed, 0 to remove and 268 not upgraded.
Need to get 333 MB of archives.
After this operation, 47.3 MB of additional disk space will be used.
Do you want to continue? [Y/n]

Dang, that's a bunch. 8o

hhh · 2015-10-09 07:27:45

Python Numpy, the least respected member of the pythons.

mrneilypops · 2015-10-09 10:25:06

@Head_on_a_Stick
Thanks for the doc...interesting.

For pure Debian Sid I have been using the Debian 'mini' cd in recent times that has an 'expert' option to directly install Sid.

Use netboot "mini.iso" image. You will find it on any of the Debian mirrors under debian/dists/unstable/main/installer-*/current/images/netboot/mini.iso. During the installation choose "Advanced options" -> "Expert install". In the step "Choose a mirror of the Debian archive" choose version "sid - unstable".

Last edited by mrneilypops (2015-10-09 10:27:19)

dolly · 2015-10-09 12:02:01

Oooops, bugs on the loose today it seems. Better watch out so you don't catch the flu.

serious bugs of xserver-xorg-core (2:1.17.2-1.1 → 2:1.17.2-3) <Outstanding>
 b1 - #798097 - Restarting logind kills Xserver
serious bugs of libpam-systemd (226-4 → 227-1) <Pending Upload>
 b2 - #801354 - boot and services fail with "Connection timed out"
serious bugs of systemd (226-4 → 227-1) <Pending Upload>
 b3 - #801361 - [systemd] attempts to unmount filesystems at end of boot, INCLUDING ROOT

nobody0 · 2015-10-09 12:24:02

CrunchStretch here http://crunchbang.org/forums/viewtopic. … 80#p440380 , the last screeny in the old forum. Maybe, I'd move it to Sid

#21 2015-10-07 05:42:39

Re: Tracking Debian testing/unstable with BunsenLabs

#22 2015-10-07 06:14:24

Re: Tracking Debian testing/unstable with BunsenLabs

#23 2015-10-07 09:29:42

Re: Tracking Debian testing/unstable with BunsenLabs

#24 2015-10-07 10:23:18

Re: Tracking Debian testing/unstable with BunsenLabs

#25 2015-10-07 10:58:55

Re: Tracking Debian testing/unstable with BunsenLabs

#26 2015-10-07 11:07:46

Re: Tracking Debian testing/unstable with BunsenLabs

#27 2015-10-07 11:47:14

Re: Tracking Debian testing/unstable with BunsenLabs

#28 2015-10-07 12:00:56

Re: Tracking Debian testing/unstable with BunsenLabs

#29 2015-10-08 11:05:38

Re: Tracking Debian testing/unstable with BunsenLabs

#30 2015-10-08 17:11:26

Re: Tracking Debian testing/unstable with BunsenLabs

#31 2015-10-08 18:01:59

Re: Tracking Debian testing/unstable with BunsenLabs

#32 2015-10-08 18:45:49

Re: Tracking Debian testing/unstable with BunsenLabs

#33 2015-10-08 18:52:48

Re: Tracking Debian testing/unstable with BunsenLabs

#34 2015-10-08 21:07:41

Re: Tracking Debian testing/unstable with BunsenLabs

#35 2015-10-09 06:38:37

Re: Tracking Debian testing/unstable with BunsenLabs

#36 2015-10-09 07:08:49

Re: Tracking Debian testing/unstable with BunsenLabs

#37 2015-10-09 07:27:45

Re: Tracking Debian testing/unstable with BunsenLabs

#38 2015-10-09 10:25:06

Re: Tracking Debian testing/unstable with BunsenLabs

#39 2015-10-09 12:02:01

Re: Tracking Debian testing/unstable with BunsenLabs

#40 2015-10-09 12:24:02

Re: Tracking Debian testing/unstable with BunsenLabs

Board footer