| === BrAsS_mOnKeY is now known as william | ||
| === rbalint_ is now known as rbalint | ||
| RAOF | Urgh! What happened to ppa:ubuntu-lxc/lxd-stable ? | 05:29 |
|---|---|---|
| joelkrahemann | hi all | 13:01 |
| joelkrahemann | how long does a proposed package until accepted? | 13:02 |
| joelkrahemann | ^^ need | 13:02 |
| cjwatson | that depends! | 13:02 |
| cjwatson | the purpose of -proposed is to ensure consistency | 13:02 |
| cjwatson | if something isn't consistent then it will delay indefinitely | 13:02 |
| cjwatson | so you need to be specific | 13:03 |
| joelkrahemann | https://launchpad.net/ubuntu/+source/gsequencer | 13:03 |
| joelkrahemann | the current package has inconsistency but the proposed actually solves it | 13:03 |
| cjwatson | joelkrahemann: it'll have to wait until we get the build farm back up on all architectures | 13:03 |
| joelkrahemann | great! thank you | 13:03 |
| cjwatson | https://lists.ubuntu.com/archives/launchpad-announce/2018-January/thread.html | 13:03 |
| cjwatson | see also https://people.canonical.com/~ubuntu-archive/proposed-migration/update_excuses.html#gsequencer | 13:04 |
| cjwatson | (which says the same thing) | 13:04 |
| joelkrahemann | well, 1.1.4 is not affected by the issues of 1.2.1 | 13:10 |
| joelkrahemann | I have done a refactoring and did temporaly break things | 13:11 |
| joelkrahemann | but everything is fine, now | 13:11 |
| sil2100 | cjwatson: question! Do you know if merge-o-matic gets automatically updated in production as per what's in bzr? | 13:11 |
| cjwatson | reason doesn't matter, pretty much everything will stall for this | 13:11 |
| sil2100 | cjwatson: or is there a manual step of bzr pull required? | 13:11 |
| cjwatson | sil2100: manual. currently at r300 | 13:12 |
| === Trevinho_ is now known as Trevinho | ||
| cjwatson | sil2100: updated to r301 now | 13:13 |
| sil2100 | cjwatson: can I ask for a bzr pull? 301 has a stats change I wanted to have deployed for Pat and Steve next week | 13:13 |
| sil2100 | cjwatson: thank you! | 13:13 |
| * sil2100 hopes nothing explodes | 13:13 | |
| mdeslaur | xnox: could you please merge open-iscsi to fix CVE-2017-17840 pleeze? | 13:38 |
| ubottu | An issue was discovered in Open-iSCSI through 2.0.875. A local attacker can cause the iscsiuio server to abort or potentially execute code by sending messages with incorrect lengths, which (due to lack of checking) can lead to buffer overflows, and result in aborts (with overflow checking enabled) or code execution. The process_iscsid_broadcast function in iscsiuio/src/unix/isc... (http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-17840) | 13:38 |
| xnox | mdeslaur, sure! | 13:38 |
| xnox | nacc, cpaelzer, smoser - do you have strong opinions on who should be merging open-iscsi and how? | 13:39 |
| xnox | I do see https://code.launchpad.net/~usd-import-team/ubuntu/+source/open-iscsi/+git/open-iscsi around | 13:40 |
| cpaelzer | no strong opinion either way | 13:40 |
| mdeslaur | thanks xnox | 13:43 |
| cjwatson | sil2100: https://paste.ubuntu.com/26371997/ | 14:11 |
| smoser | xnox: The tests that are inplace i'm pretty happy with. | 14:16 |
| smoser | they do have false negatives due to timeouts and a few other bugs, but do a good job of ensuring what we need to work works. | 14:17 |
| xnox | yeah, and the update is small | 14:19 |
| xnox | mdeslaur, uploaded | 14:19 |
| mdeslaur | thanks xnox | 14:19 |
| cjwatson | sil2100: fixed now | 14:23 |
| bbear | hello | 16:05 |
| bbear | I would like to know if you can tell me how to build my package only on python3 (not python2). dpkg-buildpkg is failing because it tries to launch the tests for python2 (which is not supported at the moment). | 16:06 |
| nacc | xnox: i can do it | 16:09 |
| nacc | xnox: ah i see you already did :) | 16:09 |
| xnox | nacc, well, i uploaded it already. | 16:09 |
| xnox | nacc, started trying out git-ubuntu.... and gave up, plus this merge was trivial, as grab-merge merged it right anyway. | 16:10 |
| nacc | xnox: ok | 16:10 |
| nacc | xnox: did you hit a bug with git-ubuntu? | 16:10 |
| xnox | nacc, nah... i just gave up half way through the tutorial on the merge | 16:11 |
| nacc | xnox: :) | 16:11 |
| nacc | xnox: fair enough | 16:11 |
| nacc | xnox: yeah, it takes a bit of work the first time (and is annoying, admittedly for trivial merges). But makes complex merges much faster once they are done once | 16:11 |
| xnox | yeah | 16:11 |
| Laney | git rerere is good for merges | 16:13 |
| xnox | yeah | 16:13 |
| nacc | Laney: yeah, it can be. Our workflow doesn't require it, but in the general Git case it could. We don't have too many Git-merges anymore in the latest import algorithm. | 16:14 |
| === Beret- is now known as Beret | ||
| jbicha | bbear: you might want to try #debian-python on the OFTC IRC network since there may be more people to help you there | 18:47 |
| pedrocr | any chance this can get resolved? https://bugs.launchpad.net/ubuntu/+source/virtualbox/+bug/1736116 | 21:11 |
| ubottu | Launchpad bug 1736116 in virtualbox (Ubuntu) "Host with kernel 4.13 freezes when starting a VM with VirtualBox" [High,Confirmed] | 21:11 |
| pedrocr | the 4.13 HWE kernel breaks virtualbox in 16.04 LTS | 21:11 |
| pedrocr | since that's now needed to fix meltdown/spectre it would be nice if virtualbox was just upgraded to 5.1 or 5.2 as well | 21:12 |
| pedrocr | also, shouldn't the intel-microcode update be pulled? seems to be broken in some severe ways | 21:23 |
| sarnold | I believe we've decided to not pull the update since we haven't had many reports directly to us of problems; but we have scaled back plans on how widely to distribute them | 21:25 |
| sunweaver | jbicha: https://bugs.launchpad.net/ubuntu/+source/indicator-sound/+bug/1737834 | 21:27 |
| ubottu | Launchpad bug 1737834 in indicator-sound (Ubuntu) "indicator-sound fails to build, test failures" [High,New] | 21:27 |
| sunweaver | I see you have the same issues as I have... | 21:27 |
| sunweaver | https://jenkins.arctica-project.org/job/ayatana-indicator-sound.deb+nightly/target=bionic/28/console | 21:27 |
| sunweaver | jbicha: have you had time to look into it more deeply? | 21:28 |
| jbicha | no | 21:29 |
| pedrocr | sarnold: as far as I know the kernel that could use the updated hasn't been shipped yet to there's no point in taking the risk with the microcode | 21:29 |
| sunweaver | the issue is, I don't see it locally. Neither on a system nor in sbuild builds. | 21:29 |
| pedrocr | sarnold: I've just uninstalled intel-microcode completely to avoid it | 21:30 |
| sunweaver | but on my build host, I get those failures. | 21:30 |
| pedrocr | (for the HT issue I have an upgraded BIOS already doing the microcode update) | 21:30 |
| sunweaver | jbicha: nice, I can reproduce... | 21:38 |
| sunweaver | if I sbuild on my notebook, the build works. | 21:39 |
| sunweaver | if I ssh into localhost and then run the same sbuild command, I get the failure... | 21:39 |
| sunweaver | running sbuild with --purge=successful and re-visiting /tmp/pulse-daemon.log in the chroot. | 21:42 |
| sunweaver | http://paste.debian.net/1004906/ | 21:45 |
Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!