=== juliank is now known as Guest67436 === juliank0 is now known as juliank === rww is now known as ezri === ezri is now known as rw === rw is now known as rwd [05:05] hate that. === _salem is now known as salem_ === salem_ is now known as _salem [12:39] hi - are there any reasons why i should not rebuild cmake against the new libjsoncpp? === alecu is now known as alecu-natholiday [12:47] https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-352/+bug/1542629 [12:47] Launchpad bug 1542629 in nvidia-graphics-drivers-352 (Ubuntu) "Session crashes when second monitor is connected" [Undecided,New] [14:15] Hi, If I report a bug upstream and find that it's in Ubuntu too, should I report it on launchpad too? [17:04] Who are the people who get packages from Debian and put them in Ubuntu? [17:04] Is there a wiki page for that? [17:04] marlinc: Ubuntu developers in general, though in the majority of cases it's automatic [17:05] Ah okay, because if this package https://launchpad.net/debian/+source/phpmyadmin/4:4.5.4.1-1 :) [17:06] marlinc: We don't automatically sync from experimental [17:06] It fixes the following bug: https://bugs.launchpad.net/debian/+source/phpmyadmin/+bug/1542665 [17:06] Launchpad bug 1542665 in phpseclib (Ubuntu) "phpseclib's Crypt/Random.php's file does not contain a class" [Undecided,New] [17:06] marlinc: Usually Debian developers upload to experimental when they're not comfortable with it having a wide audience yet [17:06] Ah, that's something different then [17:06] That explains why I'm not getting the package in a Debian sid chroot [17:07] I expect we'll get that once it hits unstable (assuming we aren't in import freeze by then) [17:07] I do hope it gets released before any of the Ubuntu freezes because the phpmyadmin package is completely broken at the moment [17:07] Thanks for the explanation cjwatson [18:27] Hi, If I report a bug upstream and find that it's in Ubuntu too, should I report it on launchpad too? [18:31] damascene: if you want some action taken in Ubuntu or want to communicate with other affected Ubuntu users, then sure. Otherwise, no need, since any fix will get to Ubuntu eventually anyway. [18:35] I see, do Ubuntu developers apply some patches to an older version of a package if the upstream did not make a patch for it? [18:37] For an existing Ubuntu stable release? To fix bugs, yes: https://wiki.ubuntu.com/StableReleaseUpdates [18:37] This assumes a patch is available of course. [18:38] (and thtat I've understood your question - you didn't provide any specifics) [18:39] for example lxde-panel for RTL languages is broken, if the upstream make a fix they probably will not port it back to the version in 16.04 [18:39] this is one example [18:42] If no fix is available, then it can't be fixed by definition, unless someone makes a fix, at which point it might be a candidate for an SRU depending on the nature of the fix. [18:43] thank for explaining it [18:43] No problem. === NCommander is now known as mcasadevall === mcasadevall is now known as NCommander === rwd is now known as ezri