You are not logged in.
I'm curious, since I'm desperate to get a version of Bunsenlabs that is 100% functional on a newer debian release such as testing or unstable, I'm wondering what it would take. Id be happy to personally take on raising a bounty for it. What would be needed to help get something like this in the works?
I've tried simply upgrading to it but have found too many breaks.
Thanks
Offline
These threads may be of use:
BL/jessie stable to stretch/sid
Tracking Debian testing/unstable with BunsenLabs
To directly answer your question, what it will take is a bit of patience! BunsenLabs Helium will be ready when Debian Stretch becomes the next Stable.
BL was always designed to be based on Stable, so if you want to make your own BunSid then have a look at those threads. The onus would be on you to maintain it when package upgrades come through though. There are issues with gtk themes, libav etc which need to be worked around.
You could also have a look at @mrneillypop's sidboX (Debian Sid + Openbox), and add the BL scripts and whichever applications you need.
Be Excellent to Each Other...
The Bunsenlabs Lithium Desktop » Here
FORUM RULES and posting guidelines «» Help page for forum post formatting
Artwork on DeviantArt «» BunsenLabs on DeviantArt
Offline
100% functional on a newer debian release such as testing or unstable
Debian testing/unstable are *not* (and will never be) releases, they are development branches.
As such, they are designed to break -- that is their purpose, to uncover bugs for the next Debian release (ie, Debian stable).
Thus, anybody who takes your money is a fraudster
The current Debian testing (stretch) will be released as Debian 9 sometime next year:
Offline
newer
Just out of curiosity, why? What would you gain compared to using stable?
Offline
What would be needed to help get something like this in the works? I've tried simply upgrading to it but have found too many breaks.
Many hours of very hard work.
Offline
... Debian testing/unstable are *not* (and will never be) releases, they are development branches.
As such, they are designed to break -- that is their purpose, to uncover bugs for the next Debian release (ie, Debian stable).
Wise words indeed!
It always amazes me how many users fail to grasp this basic Debian principle.
Offline