BL Under Sid/Unstable

KrunchTime · 2015-06-21 22:06:04

Anyone running BL with Sid/Unstable repos enabled? Any issues so far?

Sector11 · 2015-06-21 22:43:03

Pop in "apt-listbugs" and do:

apt-get update
apt-get dist-upgrade

daily or at least once ever couple of days and you should be fine. Better than testing IMHO.

If you find something with bugs - put it on hold - unhold it every now and then to see if it's fixed if no back on hold.

Two biggies to watch for are xorg and python - don't mess with them - bugs - hold-em. And that's not the Texas card game either.

Now I'd think is a good time since "stable" is relatively new and testing and sid ar not that far off.

Just MHO.

KrunchTime · 2015-06-21 23:34:22

@Sector11: Thank you, but I was looking more for the experiences of other users who may already be using BL tracking Sid/Unstable and I've experienced Xorg bug warnings on my Wally install tracking Sid/Unstable. I held the packages back for a couple of weeks, tried again, and everything was fine.

Last edited by KrunchTime (2015-06-21 23:36:24)

Sector11 · 2015-06-21 23:40:10

OOPS! So sorry.

spacex · 2015-07-10 23:52:47

KrunchTime wrote:

@Sector11: Thank you, but I was looking more for the experiences of other users who may already be using BL tracking Sid/Unstable and I've experienced Xorg bug warnings on my Wally install tracking Sid/Unstable. I held the packages back for a couple of weeks, tried again, and everything was fine.

I haven't yet, but I have with TweakOS, and have no issue with Sid there, so I can't see why there would be any with Bunsen. But I'll try tomorrow. I'm waiting for my sid-based live-build to complete, so I can't do much right now. I'll give it a go. What is most useful for the project? Doing it from the live-cd version, or the netinstall? I have both of them installed.

KrunchTime · 2015-07-11 00:17:05

spacex wrote:

What is most useful for the project? Doing it from the live-cd version, or the netinstall? I have both of them installed.

I don't think it matters, although I'm partial to netinstalls now after using them for my last four install experiences.

Last edited by KrunchTime (2015-07-11 00:17:18)

spacex · 2015-07-11 00:38:26

KrunchTime wrote:

spacex wrote:
What is most useful for the project? Doing it from the live-cd version, or the netinstall? I have both of them installed.
I don't think it matters, although I'm partial to netinstalls now after using them for my last four install experiences.

Ok, I'll try that tomorrow. It's 2.37 AM here, so it's a little bit late to start on it now

spacex · 2015-07-11 14:53:46

Ok. Going for it now. Have changed sources to Sid, and installed "apt-listbugs".

Ok, apt-listbugs gives this report:

Retrieving bug reports... Done
Parsing Found/Fixed information... Done
grave bugs of gstreamer1.0-libav (→ 1.4.4-2) <Outstanding>
 b1 - #767423 - tracker-extract SIGSEGV
grave bugs of iceweasel (31.8.0esr-1~deb8u1 → 38.1.0esr-2) <Outstanding>
 b2 - #788708 - iceweasel: GStreamer causes segmentation fault
serious bugs of bash-completion (1:2.1-4 → 1:2.1-4.1) <Outstanding>
 b3 - #785271 - dh_bash-completion script/file list autodetection fails hiding bugs which can become RC
serious bugs of liblognorm2 (→ 1.1.1-1) <Outstanding>
 b4 - #788852 - liblognorm2: removal of liblognorm2 makes files disappear from liblognorm1
serious bugs of openssl (1.0.1k-3+deb8u1 → 1.0.2d-1) <Outstanding>
 b5 - #768476 - openssl: Removes symbol without SONAME bump
   Merged with: 768522 769023 770278 770605 771169 771993 781094 781929 787712
grave bugs of libxml2 (2.9.1+dfsg1-5 → 2.9.2+dfsg1-3) <Forwarded>
 b6 - #766884 - libxml2: "validity error : ID ... already defined" errors with xmllint --noent
grave bugs of iceweasel (31.8.0esr-1~deb8u1 → 38.1.0esr-2) <Forwarded>
 b7 - #790498 - iceweasel: upgrading from jessie makes all passwords in the password manager invalid
serious bugs of libgtk2-perl (2:1.2492-4 → 2:1.2495-1) <Forwarded>
 b8 - #790532 - FTBFS: Failed 1/228 test programs
serious bugs of udev (215-17+deb8u1 → 222-1) <Resolved in some Version>
 b9 - #787364 - ifup@.service does not start any more with systemd 220 (Fixed: systemd/220-3)
   Merged with: 787263
Summary:
 bash-completion(1 bug), libxml2(1 bug), udev(1 bug), liblognorm2(1 bug), openssl(1 bug), gstreamer1.0-libav(1 bug), iceweasel(2 bugs), libgtk2-perl(1 bug)
Are you sure you want to install/upgrade the above packages? [Y/n/?/...]

OK, I'm going for it anyway, will report back later....

Update. Turned out just fine. I had to reboot 3 times to get a wifi-connection. That's the only thing I've noticed this far. Could be a coincidense, as my laptop does this sometimes, when I reboot from another distro. Or related to bug9(b9). Don't know yet. Will have to test a few more times to see.

OK. tried rebooting again, and no wifi. The tried again and got reported as connected but didn't work. Then rebooted once more, and then it worked. So I get a working wifi every three times I boot. It seems that if I wait a little at the grub-screen and at the lightdm-login, it is a better chanche to have a working wifi when I'm up. This is a very fast ssd. Too fast it seems

I haven't checked which version of systemd I have.

OK, systemd-version 222-1 and openssl 1.0.2d-1. So it should be fine, but I still have some kind of network-issue. Will research it more.

Last edited by spacex (2015-07-11 19:52:58)

paxmark1 · 2015-07-11 15:09:55

definitely go with openssl 1.02-d1 and systemd-222 should work, real pita for some with systemd-220 awhile back wicd and ceni also lost wifi capabilities with sysemd-220 but have it back with 221 and 222.

I don't have experience with the other bugs.

Sector11 · 2015-07-11 17:24:04

I would have said no and put the apps on hold ... something from my running SID for a while.

alias hld='echo "alias hld = sudo apt-mark hold app_name app_name" ; sudo apt-mark hold'

then run dist-upgrade again and let all the good ones update ...

Every couple of days look for the held packages:

alias shld='echo "alias shld = apt-mark showhold" ; apt-mark showhold'

and unhold them all or one by one

alias unhld='echo "alias unhld = sudo apt-mark unhold app_name app_name" ; sudo apt-mark unhold'

and check with an update/dist-upgrade again. If they pass great, if not - back on hold.

If on hold too long ask what others have done.

Aliases in action:

 11 Jul 15 | 14:20:07 ~
    $ hld geany conky-all thunar
alias hld = sudo apt-mark hold app_name app_name
[sudo] password for sector11: 
geany set on hold.
conky-all set on hold.
thunar set on hold.
 
 11 Jul 15 | 14:20:38 ~
    $ shld
alias shld = apt-mark showhold
conky-all
geany
thunar
 
 11 Jul 15 | 14:20:51 ~
    $ unhld geany thunar conky-all
alias unhld = sudo apt-mark unhold app_name app_name
Canceled hold on geany.
Canceled hold on thunar.
Canceled hold on conky-all.
 
 11 Jul 15 | 14:21:59 ~
    $

spacex · 2015-07-11 19:55:45

@Sector11

Yes, but the whole point of this was to test Bunsen on Sid, and then I can't wait or put packages on hold. I knew the risk, and it doesn't matter at all if the whole install gets borked or broken. It's just a testinstall anyway

But I assume that I will be able to fix the network-issue, so all in all, I will say that the upgrade went just fine.

Sector11 · 2015-07-11 20:52:13

Incorporating "grave" and "serious" bugs of Debian apps that are NOT Bunsen specific means you are not really testing Bunsen but testing Debian8

None of the bug you show have anything to do with Bunsen but they do have to do with Debian.

hold and unhold are SID's best friends to keep SID running properly.

spacex · 2015-07-11 23:44:52

Sector11 wrote:

Incorporating "grave" and "serious" bugs of Debian apps that are NOT Bunsen specific means you are not really testing Bunsen but testing Debian8
None of the bug you show have anything to do with Bunsen but they do have to do with Debian.
hold and unhold are SID's best friends to keep SID running properly.

Yes, if you create a production-system, surely it is. But grave and serious bugs doesn't mean that it will effect all users in all hardware-configurations, so it kind of depends whether you want to take the risk or not. Actually, playing it safe with Sid, kind of contradicts the whole purpose of Sid. Which is to install it with bugs and all, and then help to fix it. If everyone played it safe, then Sid pretty much would be left in a stand still mode...

As for Bunsen, obviously it includes the whole compilation as such, and not only the Bunsen-configs. As with my release. If things doesn't work properly with Debian, I don't say that it has to do with Debian, so I'll just have to wait for it to be fixed. Nope, obviously I look for the solutions myself. Always. I'm not waiting for Debian to solve anything, and if I'm not able to fix the Debian-issue, then I work around it. Waiting and holding isn't for me. I do this for fun and entertainment, and putting myself in difficult situations with lots of issues, is actually where all the fun is.

Bunsen is OS number 8 on this PC, and I have it installed twice. To play with it. Bunsen is in alpha-state or sub-alpha state. Being afraid of wrecking a install at this time is meaningless, as there will be lots more happening, and the fact that it isn't the finished build yet. So people will be reinstalling Bunsen many more times in the next month or so.

Therefore, don't even think of using Bunsen as your main OS and production system at this point. Install it to test and play with it, without any worry about wrecking anything, and if you keep holding stuff for to long, then it also could potentially become a issue later. Unless there are something major that will make your system unusable, just go for it. The fixes will come soon, and in the meantime, work around it.

So you see, we approach Sid in a totally different manner. I have no interest of staying safe with Sid. I'm not using Sid because I have hardware that needs it. I use it because I get issues. And I do want issues. The more, the merrier. Nothing is more boring than something that just works. Actually, a computer without issues are completely useless to me.

But obviously, with 8 different OS and distros on one computer, there will always be some of them who are functional

KrunchTime · 2015-07-13 00:57:04

Sector11 wrote:

I would have said no and put the apps on hold ... something from my running SID for a while...

Good advice.

Sector11 wrote:

Incorporating "grave" and "serious" bugs of Debian apps that are NOT Bunsen specific means you are not really testing Bunsen but testing Debian8
None of the bug you show have anything to do with Bunsen but they do have to do with Debian.
hold and unhold are SID's best friends to keep SID running properly.

I have to agree with Sector11 on this one. My interest in running a Sidified BL is whether and how doing so might affect the pipemenus, scripts, and themes. Debian packages changing are a given.

Last edited by KrunchTime (2015-07-13 01:01:48)

KrunchTime · 2015-07-25 07:57:16

I installed BL on another partition earlier this week and changed the repos to Unstable; no problems so far.

CrunchBang Linux

SEARCH

#1 2015-06-21 22:06:04

BL Under Sid/Unstable

#2 2015-06-21 22:43:03

Re: BL Under Sid/Unstable

#3 2015-06-21 23:34:22

Re: BL Under Sid/Unstable

#4 2015-06-21 23:40:10

Re: BL Under Sid/Unstable

#5 2015-07-10 23:52:47

Re: BL Under Sid/Unstable

#6 2015-07-11 00:17:05

Re: BL Under Sid/Unstable

#7 2015-07-11 00:38:26

Re: BL Under Sid/Unstable

#8 2015-07-11 14:53:46

Re: BL Under Sid/Unstable

#9 2015-07-11 15:09:55

Re: BL Under Sid/Unstable

#10 2015-07-11 17:24:04

Re: BL Under Sid/Unstable

#11 2015-07-11 19:55:45

Re: BL Under Sid/Unstable

#12 2015-07-11 20:52:13

Re: BL Under Sid/Unstable

#13 2015-07-11 23:44:52

Re: BL Under Sid/Unstable

#14 2015-07-13 00:57:04

Re: BL Under Sid/Unstable

#15 2015-07-25 07:57:16

Re: BL Under Sid/Unstable

Board footer