Anyone running BL with Sid/Unstable repos enabled? Any issues so far?
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.
@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)
Last edited by KrunchTime (2015-07-11 00:17:18)
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)
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.
Jean Vanier wrote "Being Human" and "A Short History of Progress" by Ronald Wright. Gotta love the Massey Lectures.
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.
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.
Last edited by KrunchTime (2015-07-13 01:01:48)