| === hikiko is now known as hikiko|off | ||
| rbasak | Is there a link somewhere that I can point people to when their system breaks because of having yakkety-proposed enabled? | 13:39 |
|---|---|---|
| ogra_ | rbasak, perhaps https://wiki.ubuntu.com/Testing/EnableProposed ? | 13:40 |
| rbasak | ogra_: I feel I need the opposite: that development -proposed is wrong, how to turn it off, and why. | 13:41 |
| ogra_ | well, that wiki has a section that sets up pinning in a way that normal upgrades will not be pulled from -proposed | 13:41 |
| ogra_ | (i wonder why we dont ship that config snippet by default actually) | 13:42 |
| ogra_ | with that you actually need "apt install $package/$release-proposed" to get anything at all from there | 13:42 |
| rbasak | That's not necessarily what we want for users who are prepared to test proposed for us in a _stable_ release. | 13:43 |
| rbasak | It's fine not to pin in that case. | 13:43 |
| rbasak | OTOH, in the development release, users should pretty much *never* have the proposed pocket enabled, so no need for pinning there at all. | 13:43 |
| ogra_ | well, you will always run into the prob that users forget to turn it off after testing | 13:43 |
| ogra_ | the pinning would be a safety net | 13:44 |
| rbasak | There's another use case though. | 13:44 |
| rbasak | "As an Ubuntu power user, I'd like to contribute to Ubuntu by testing proposed SRUs before they are released to the general public" | 13:44 |
| rbasak | That's what the check box in enabling proposed is for. | 13:45 |
| ogra_ | not really ... | 13:45 |
| rbasak | Well OK, but it's one of the use cases at least. | 13:45 |
| ogra_ | the box is "use it if a developer tells you so in a bug report to verify a bug fix ... and do not forget to turn it off again" | 13:46 |
| rbasak | If we want to pin out proposed by default, we need to fix the instructions so that users can still do that, and also fix the instructions so users can override the pin to verify a particular SRU. | 13:46 |
| ogra_ | but yeah, there are these people that run proposed permanently | 13:46 |
| ogra_ | (and complain that their system falls apart occasionally :P ) | 13:46 |
| rbasak | IMHO, all Ubuntu devs should be doing so if on a stable release. | 13:46 |
| ogra_ | not so sure ... i for one perfer to have a stable system for doing my work :) | 13:47 |
| ogra_ | (i have multiple machines though and one does actually run proposed) | 13:47 |
| ogra_ | anyway, i think the above is the only page we have for proposed ... IMHO there should definitely be more warnings on it though | 13:48 |
| ogra_ | i.e. some inro paragraph that actually explains a bit more in detail what proposed is and who should use it when | 13:49 |
| ogra_ | *intro | 13:49 |
| rbasak | FTR, I found an askubuntu question and linked to that. This is bug 1617963. | 13:58 |
| ubot5` | bug 1617963 in heimdal (Ubuntu) "package libasn1-8-heimdal:amd64 1.7~git20160703+dfsg-1 failed to install/upgrade: package libasn1-8-heimdal:amd64 1.7~git20160703+dfsg-1 cannot be configured because libasn1-8-heimdal:i386 is at a different version (1.7~git20150920+dfsg-4ubuntu1)" [Undecided,Invalid] https://launchpad.net/bugs/1617963 | 13:58 |
| ogra_ | ah, neat | 14:03 |
| === bschaefer_ is now known as bschaefer | ||
Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!