=== Ursinha is now known as Ursinha-afk === Ursinha-afk is now known as Ursinha === yofel_ is now known as yofel === pedro_ is now known as Guest11825 === Guest11825 is now known as pedro_ === pedro_ is now known as Guest67914 [16:51] I'm working through getting an SRU for bliss 0.72-4. I made (and closed) a bug https://bugs.launchpad.net/ubuntu/+source/bliss/+bug/1087771 . It seems the next step is to find a "bug-supervisor" ? Is this the right place for that? [16:51] Launchpad bug 1087771 in bliss (Ubuntu) "omitting BLISS_USE_GMP causes mysterious failures" [Undecided,Fix released] [16:54] bremner: nominated for 12.04 (precise) and 12.10 (quantal). A release team member will need to approve that. [16:55] thanks [16:57] bremer: btw, does upstream know that their license headers mention "foobar"? [16:57] "You should have received a copy of the GNU General Public License along with Foobar." [16:58] bremner: ^^ (sorry for typo) [16:59] bremner: tasks approved, can you please make it clear which diff applies to which release (precise has -2, quantal -3) [16:59] mitya57: release team doesn't need to approve tasks, an Ubuntu dev does (SRU team does review in queue) [16:59] *Ubuntu dev that can upload said package [17:01] micahg: sorry, I meant "~ubuntu-drivers" [17:01] that's just one option [17:26] micahg: I attached seperate debdiffs for the two versions. [17:29] bremner: you probably want to collapse the changelogs and change the version to whatever it was in the release with ubuntu0.1 on the end of it (standard SRU versining) [17:29] and target $RELEASE-proposed [17:30] alternatively, add a changelog on top with ~ubuntuXX.XX.1 where XX.XX is the numeric version of the release and close the SRU bug in the top changelog [17:31] I supppose close the SRU bug in either case? [17:32] any preferences between the two versions? I suppose version 2 sounds slightly better to me. [17:36] bremner: yes, the SRU bug should be in the changelog (LP: #XXXXXX) regardless, and since we're probably taking all the changes, either should be fine (I like the second in this scenario as well) === hggdh_ is now known as hggdh