=== Logan_ is now known as Logan
=== inaddy is now known as tinoco
=== dreamon_ is now known as dreamon
=== meetingology` is now known as meetingology
=== Ursinha_ is now known as Ursinha
=== braderhart_ is now known as braderhart
=== hikiko is now known as hikiko|ln
=== \b is now known as benonsoftware
[12:08] <estan> hi folks. i plan on nominating my https://bugs.launchpad.net/ubuntu/+source/octave/+bug/1583128 for a SRU, as soon as i've made a debdiff for the source package. i just want to ask if attaching a debdiff to the bug report is normal practice/OK?
[12:08] <ubot5> Launchpad bug 1583128 in octave (Ubuntu) "HDF5 I/O broken with integer variables" [Undecided,New]
[12:09] <estan> i've never done any Debian packaging, so i'm a bit new to all this :p
[12:10] <estan> the bug is a regression with the potential for data loss that crept into Octave 4.0.0, it's fixed upstream in 4.0.1 with a simple change, and my debdiff would add the upstream patch.
[12:15] <estan> sorry, i mean ask for it to be nominated (for 16.04 LTS that is).
=== hikiko|ln is now known as hikiko
=== Pici` is now known as Pici
[12:53] <estan> okay. i've attached the debdiff, so now officially asking for an SRU nomination for https://bugs.launchpad.net/ubuntu/+source/octave/+bug/1583128
[12:53] <ubot5> Launchpad bug 1583128 in octave (Ubuntu) "HDF5 I/O broken with integer variables" [Undecided,New]
[14:24] <nacc> estan: is it in yakkety?
[14:25] <nacc> estan: and attaching debdiffs to bug reports is definitely normal and expected
[14:31] <patcable> I just updated https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1575877 with verification results on xenial, trusty, and precise. added a debdiff for wily as well
[14:31] <ubot5> Launchpad bug 1575877 in apt (Ubuntu Wily) "no_proxy ignored if https_proxy set" [Medium,Triaged]
[14:34] <estan> nacc: hi. i got help from arges in #ubuntu-release :) it's not in yakkety, so he said he'd upload to yakkety first, before doing an SRU.
[15:23] <nacc> estan: ah great!
=== zequence_ is now known as zequence