=== Pici is now known as Guest59733 === Guest59733 is now known as Pici === doko_ is now known as doko [14:43] What's the process of syncing or pocket-copying stuff from oneiric-updates into precise? [14:43] does it happen automatically at some point? if not, don't we risk losing ubuntu-specific changes from oneiric-updates and oneiric-proposed? [14:48] mdeslaur, usually they are copied to -updates and $newserie at the same time [14:48] mdeslaur, when $newserie still has the same version [14:48] seb128: that's not currently happening [14:48] mdeslaur, example? [14:48] https://launchpad.net/ubuntu/+source/xorg-server [14:49] mdeslaur, it's not in -updates yet? [14:49] seb128: 2:1.10.4-1ubuntu4.1 is in oneiric -updates, but only 2:1.10.4-1ubuntu4 is in P [14:50] mdeslaur, seems like this one was not copied, but it comes from security, not proposed [14:50] seb128: so the automatic copy is done by the SRU process, but it's not being done by the security update process? [14:50] mdeslaur, I was speaking about proposed->updates, I would assume security updates should be handled the same way [14:51] mdeslaur, it's not automatic I think [14:51] it's an archive admin best practice [14:51] mdeslaur, this one was maybe an oversight [14:51] hmm...our stuff gets copied to -updates with an automatic script IIRC [14:51] no AA to blame [14:51] ok, so maybe that script needs fixing [14:52] for proposed->updates it's done manually and the archive admin runs the command to copy to $nextversion as well usually [14:53] I don't think we can do it automatically [14:53] jdstrand: why not? [14:53] at least not simply-- it is really only at the beginning of the dev release where we want to do this. we really want to build on the new toolchain later on [14:54] well, what's the AA best practice? do you stop copying at some point? [14:54] I only do it when I am asked to [14:55] I wasn't asked, so it didn't happen [14:55] I also didn't think about it with the USNs [14:55] mdeslaur, seems it depends of the people [14:55] I like better to upload things once that to upload twice with 2 revision to 2 series [14:55] so we've got an issue here, where we may be losing ubuntu-specific fixes once people start merging from debian [14:55] mdeslaur: I've made a note to discuss this as part of our dev release update process at UDS [14:55] i.e for desktop we usually upload the sru and pocket copy [14:56] seb128: but only early on, no? [14:56] jdstrand, it doesn't last long before $nextversion > $stable yes [14:56] like once we start on merges that time is over [14:56] mdeslaur: that was the 'not simply' part I was thinking about. we need to be smart about the versions [14:56] we usually do 1 or 2 weeks for SRU, then the merges [14:56] * jdstrand nods [14:56] jdstrand, so yes, it's usually between release and UDS [14:56] then after than we reduce the number of SRU and uploads to unstable then backport [14:57] mdeslaur, right, we might be losing fixes and we do loose some (i.e it's already happened in the past) [14:57] but pocket copies will not fix that [14:57] one way to "fix" it, is to not move things to -updates until the fix is in $unstable [14:58] which I guess is fine for SRUs but less for security [14:58] any way we do it is fine, as long as we have a process that works and is consistent for everyone [14:59] right [14:59] let's discuss it at UDS, thanks for pointing it [14:59] I was under the mistaken impression that O stuff gets copied automatically to P, which was a wrong assumption [14:59] right [15:00] ok, thanks seb128, jdstrand [15:03] np [20:35] Hi, can I get a pocket copy of wireshark 1.2.11-6+squeeze4build0.10.10.1 from maverick-security to maverick-updates? [20:44] I can do that [20:45] sbeattie: done [20:54] jdstrand: thanks.