=== vorian is now known as v [03:13] When a sync request is processed, do the Ubuntu builders do a build or is the binary package copied? [03:15] looks like source from the wikipage, " This will ask Launchpad to copy the source package publication entry from its import of Debian." [03:16] so we trust that the binaries that were pushed to debian can be properly rebuilt in Ubuntu, or we fix it when it doesn't [03:57] mfisch: Only the source is copied. [03:57] It's then rebuilt and then if it doesn't build someone should fix it. [03:58] Ubuntu makes no claim and has never attempted strict binary compatibility with Debian. [03:59] ScottK: thanks [03:59] You're welcome. === broder_ is now known as broder === bigon_ is now known as bigon [07:09] good morning! :) === iulian_ is now known as iulian [09:09] infinity, Can you merge xscreensaver. It will take you 0.1 seconds to fix the conflict [09:09] Noskcaj10: Sure can. [09:10] thanks [10:06] When i use "quilt push" and get a hunk error, why does the patch still take place? === jdstrand_ is now known as jdstrand [16:04] Do we have documented when and how a package moves out of -proposed? Is it strictly time based? === chuck_ is now known as zul === wendar_ is now known as wendar [17:23] mfisch: https://lists.ubuntu.com/archives/ubuntu-devel-announce/2012-October/000989.html [17:23] It's not time based at all. [18:22] ScottK: Thanks, I'll read through that [18:53] ScottK: are the test results viewable for the packages? [18:55] mfisch: The relevant places to start are http://people.canonical.com/~ubuntu-archive/proposed-migration/update_excuses.html and http://people.canonical.com/~ubuntu-archive/proposed-migration/update_output.txt when trying to figure out why something didn't migrate. [18:56] And once it passes these tests, it lands in saucy, with no delay? No time for people on -proposed to try it? [18:56] No. People should not be running proposed. [18:56] It's for robots only. [18:56] Ah yes, that other discussion [18:57] When I started using Ubuntu I had an issue with Unity and was recommended to enable proposed, this was in the Oneiric timeframe [18:57] This is a recent change. [18:57] ScottK: but proposed can be used by people testing SRUs, IIRC [18:58] Yes. This is only for the development series. [18:58] Right [18:58] for the SRU I did they waited for user feedback on the bug [18:58] Yes. That's required. [18:58] Thanks ScottK I'm going to check again to see if this is covered in the wiki and if not, perhaps find a place for it [18:58] Every SRU is tested in proposed before it's released to updates. [20:32] is saucy part of the libgd2 transition that's going on in Debian? [20:34] I know there's ongoing Debian testing with the libgd2, and the nginx packages are now using libgd2-dev|libgd2-noxpm-dev as part of the transitioning, but is that transitioning in Saucy as well? [20:34] or do i not have to worry about this? [20:46] TheLordOfTime: http://people.canonical.com/~ubuntu-archive/transitions/libgd2.html [20:47] that... doesn't answer my question [20:47] my question is which release(s) are going to be affected by the transition, saucy and onwards? [20:47] iulian: ^ [20:49] The link I've given you lists all the transitions that are happening in Saucy right now. [20:53] but that ***wasn't my question*** [20:53] I don't understand your question then, sorry. [20:55] my question is "Which release is the transition happening in" but i guess saucy since the link's there [20:55] I did say that, didn't I? [20:56] iulian: i'm a little frazzled, i might be misreading [20:56] (happens from time to time) [20:56] guess i'll have to fix this FTBFS then >.> [20:56] before i can fix the PPA for nginx [20:56] (since apparently nginx returns as "good") === Zic is now known as Guest81623