Skel_Eloren 2017-01-26 22:53:53
Does anyone know how to configure fonts and colours for notification-daemon?
cri1 2017-01-26 23:23:03
hi, any mozilla developers here?
cri1 2017-01-26 23:24:07
I was wondering why there are FF 45.7.0 packages for stable and unstable, but not for testing
darxmurf 2017-01-26 23:33:45
talking about that, I'm wondering why icedove is crashing all the time
darxmurf 2017-01-26 23:33:57
in testing
babilen 2017-01-26 23:34:33
darxmurf: works fine here on sid (same version)
cri1 2017-01-26 23:34:43
https://qa.debian.org/excuses.php?package=firefox-esr
cri1 2017-01-26 23:35:00
says "Too young, only 2 of 10 days old "
darxmurf 2017-01-26 23:35:17
babilen: you don't have random crashes ?
babilen 2017-01-26 23:35:22
No
cri1 2017-01-26 23:35:25
do we have to wait 10 days to get a security update to testing?
babilen 2017-01-26 23:35:36
cri1: Just pull it from unstable
darxmurf 2017-01-26 23:35:38
like middle of wriiting a mail
darxmurf 2017-01-26 23:35:47
hum, weird
babilen 2017-01-26 23:36:32
darxmurf: Well, that doesn't invalidate the crashes you experience .. but I haven't had problems. Don't really use it as my main MUA though
cri1 2017-01-26 23:36:39
babilen: yeah, I was considering that, but I'd like to understand if it's a temporary problem or some weird policy
babilen 2017-01-26 23:36:50
cri1: What exactly?
cri1 2017-01-26 23:37:17
the fact that there are packages for stable and unstable, but testing must wait 10 days
babilen 2017-01-26 23:37:25
It's pretty normal for packages to wait in unstable before they transition to testing
darxmurf 2017-01-26 23:37:31
babilen: ah, mine is open the whole day
flokuehn 2017-01-26 23:37:41
l:D
flokuehn 2017-01-26 23:37:56
sorry. wrong window
babilen 2017-01-26 23:38:26
cri1: https://debian-handbook.info/browse/stable/sect.release-lifecycle.html might clarify the way 'testing' is used. Please note that testing is simply a tool used to prepare the next stable release and that it is not meant to be used by users really
babilen 2017-01-26 23:38:47
darxmurf: Well, mine is too .. but sees little action as I mostly use mutt
cri1 2017-01-26 23:39:27
babilen: I thought that testing would get security updates as soon as stable does
babilen 2017-01-26 23:39:34
Not at all
cri1 2017-01-26 23:39:54
babilen: so what's the use of having this in sources.list http://security.debian.org/debian-security stretch/updates
babilen 2017-01-26 23:40:31
There might be some security uploads, but mostly they are done by uploading a fixed package to unstable and letting it transition in due course. That's one of the reasons why I personally consider tracking only testing to be a viable setup.
babilen 2017-01-26 23:40:53
err
babilen 2017-01-26 23:41:01
*to NOT be a viable setup
babilen 2017-01-26 23:41:28
Either way .. this is probably a better topic for #debian-next on irc.oftc.net
cri1 2017-01-26 23:41:37
babilen: ok, thanks for the explanation (BTW i must use testing because X crashes with the kernel in stable)
babilen 2017-01-26 23:41:55
You can get a backported kernel -- /msg dpkg bdo kernel
babilen 2017-01-26 23:41:59
dpkg: tell cri1 -about tum
babilen 2017-01-26 23:42:09
Ah .. you are tracking stretch, not testing
babilen 2017-01-26 23:42:15
dpkg: tell cri1 -about ssm
cri1 2017-01-26 23:42:34
babilen: testing != stretch ???
babilen 2017-01-26 23:42:45
That's a more sensible setup IMHO that copes better during transitions, package removals and also allows you to easily grab packages from sid whenever you have to
babilen 2017-01-26 23:43:42
cri1: It is now, but as soon as stretch is released stretch will be stable and there'll be a new testing (buster)
cri1 2017-01-26 23:44:00
ah sure
babilen 2017-01-26 23:44:03
So it makes a *huge* difference if you use "stretch" or "testing" in your sources.list
