[08:34] any archive admins around? [08:35] tseliot: I'm sort of here (at a conference) [08:36] stgraber: I have some packages approved for an SRU but the binaries are stuck in NEW (precise-proposed) [08:36] tseliot: ah, ok, I'll take a quick look then [08:37] stgraber: nvidia-prime, fglrx-pxpress, nvidia-graphics-drivers-319, nvidia-graphics-drivers-319-updates, nvidia-graphics-drivers-304, nvidia-graphics-drivers-304-updates, nvidia-graphics-drivers-173-updates, nvidia-settings-319, nvidia-settings-319-updates, nvidia-settings-304, nvidia-settings-304-updates, nvidia-persistenced, fglrx-installer-updates, fglrx-installer-experimental-13 [08:38] stgraber: nvidia-prime and fglrx-pxpress belong in main, the nvdia and fglrx drivers in restricted, nvidia-settings* in main (same as nvidia-persistenced) [08:41] tseliot: hmm, fglrx-pxpress is in universe in saucy [08:42] stgraber: I have a MIR for that, let me find the bug report... [08:43] tseliot: hmm, I'm not fond of the idea of promoting this in the LTS before it's done in the dev release... [08:44] stgraber: I guess the MIR hasn't been approved yet. Using universe should be ok for now, I'll have the packages moved as soon as the MIR is approved [08:44] ok, accepting to universe for now then [08:46] thanks [08:46] didrocks: please have a look at bug #1204820 when you can [08:46] Launchpad bug 1204820 in nvidia-prime (Ubuntu) "[MIR] nvidia-prime & fglrx-pxpress" [Undecided,New] https://launchpad.net/bugs/1204820 [08:48] tseliot: all done [08:48] stgraber: excellent, thanks! [08:49] (restarting queuebot as it didn't notice) [08:55] tseliot: looks both good. is anything build-dep on them or will you add them to the support seed? [08:56] didrocks: nothing really depends on them now [08:56] tseliot: ok, please add them to the support seed then [08:56] then, once pushed, I'll promote them [08:58] didrocks: I'm not sure how to do that or why [08:58] tseliot: if we don't do that, nothing will pin them in main [08:58] and so someone will demote them [09:00] didrocks: ok, so maybe either supported-hardware-common or supported-hardware-desktop? [09:01] tseliot: oh, I don't know those, I'm sued to "supported" in bzr+ssh://bazaar.launchpad.net/~ubuntu-core-dev/ubuntu-seeds/ubuntu.saucy/, but if there is anything else [09:01] tseliot: just push to the one which makes sense and give me a sign so that I do the promotion [09:02] didrocks: ok, shall I do that for precise too? (the packages are also in precise-proposed) [09:02] tseliot: yeah [09:02] didrocks: ok, good [09:03] tseliot: but wait for it to be out of proposed to remember me to promote it there as well [09:03] (the override is lost between proposed and update if it's the same than proposed -> release) [09:03] didrocks: ok [09:14] didrocks: ok, I've just committed revision 2152 for saucy, so the two packages should be pinned [09:14] tseliot: thanks! promoting [09:15] didrocks: great, thanks! [09:16] tseliot: yw, done :) [09:17] :) [09:24] tseliot: ok, I'll promote it in precise too then [09:25] stgraber: ok, thanks [09:27] tseliot: done [09:27] stgraber: great, thanks again :) [09:35] stgraber: BTW, is nvidia-persistenced in saucy? [09:35] tseliot: doesn't look like it [09:36] stgraber: it was reviewed by cjwatson, then I applied his changes, reuploaded but it was never reviewed or approved again [12:06] infinity, are you ready to promote linux 3.11 ? [12:53] stgraber: still around? [12:55] tseliot: yeah [12:55] stgraber: I don't see fglrx-installer-experimental-13 in precise-proposed [12:56] (same bug report) [12:56] i.e. 1198942 [12:57] tseliot: I only processed the new binaries this morning, not new sources. fglrx-installer-experimental-13 is a new source pending review in precise-proposed [12:57] (so is nvidia-persistenced apparently) [12:57] stgraber: oh, so they haven't been approved yet [12:57] right [12:58] ok, I should probably ask slangasek about that then [12:58] tseliot: is fglrx-installer-experimental-13 mostly an identical copy from saucy? if so, I can confirm that part and let it in based on that, otherwise I don't think I've got the time to do a full New review of it [12:59] stgraber: fglrx-installer-experimental-13 is the same as fglrx and fglrx-updates in saucy [12:59] tseliot: note that cjwatson, doko, slangasek and I are all at Debconf this week, so it may be difficult for us to find enough time in a row to do a full New review [13:00] oh [13:00] tseliot: ok, I'll grab the saucy source and do a diff, if they seem sufficiently identical (just obvious packaging changes), I'll let it in and then let its binaries in too [13:00] stgraber: thanks a lot === barry` is now known as barry_ === barry_ is now known as barry [13:16] ae8f805e52508dd2fde55be3dc7dffd1 fglrx-installer-updates_13.101.orig.tar.gz [13:16] 12ae4dc15542382eb0c119729af6fd70 ../precise/fglrx-installer-experimental-13_13.101.orig.tar.gz [13:16] tseliot: ^ [13:18] ok, they're actually identical except for the precise one being shifted one level (no top level fglrx-installer in that tarball) [13:21] -PATCH_MATCH[0]="^3.[10-11]" [13:21] +PATCH_MATCH[0]="^3.[10]" [13:21] tseliot: ^ is that going to be a problem once we backport the saucy kernel to precise? [13:23] tseliot: debian/pxpress also indicates some code that's in precise but not in saucy (_find_process function and code to call dpkg --configure -a) [13:24] tseliot: is fglrx-installer-experimental-13 already in saucy? [13:24] besides that the rest seems mostly identical to saucy's [13:24] ah, so it is [13:24] stgraber: thanks for tending :) [13:24] slangasek: as fglrx-installer-updates, yes === medberry is now known as med_ [13:48] stgraber: that would be a problem for 12.04.4, it shouldn't be for 12.04.3 (Which won't ship 3.11) [13:48] stgraber: that part of code (debian/pxpress) is only used when called from jockey and there's no jockey in saucy [13:49] slangasek: no, but the same driver is in fglrx and fglrx-updates (it only has a different name) [13:55] tseliot: ok, thanks for the answers. I'll let it in now (the rest indeed is a copy + rename) [13:55] stgraber: right, thanks [14:01] stgraber, do you have time to promote Saucy linux from -proposed ? [14:02] That isn't a manual task [14:02] Except in that it needs some problem resolved [14:02] let me check what we're missing, is that just d-i? [14:02] stgraber, it might be, but I'm not sure. [14:03] d-i's missing (Adam was going to do it today, I thought), and I think it's also mysteriously hung up on an autopkgtest [14:03] * cjwatson fires up the VPN [14:03] hmm, indeed, stuck on autopkgtest [14:03] Spuriously - I think I'll force it [14:03] cjwatson, it is a major transition from 3.10 to 3.11 [14:04] I know [14:04] But proposed-migration doesn't care about that :) [14:05] I'll sort out d-i [14:07] cjwatson: will you also do the seed changes? [14:08] Yes [14:08] It looks like there's a mess around linphone/sipwitch that needs ucommon ported to a newer GNUtls (not done upstream yet). [14:08] Way beyond me to sort out. [14:16] we can clear up the linphone situation by removing ucommon 6 from Debian since it may take a while for the Debian maintainer to get around to fixing http://bugs.debian.org/716855 [14:16] Debian bug 716855 in libucommon-dev "libucomon-dev: Dependency on libgnutls28-dev makes sflphone unbuildable" [Important,Open] [14:16] *remove ucommon from -proposed and then rebuild sipwitch [14:16] Except ucommon doesn't build with libgnutls-dev [14:17] Oh. [14:17] * ScottK tries. [14:18] I've so far been unsuccessful at convincing the Debian maintainer that it's a big problem [14:19] Lovely. [14:29] jbicha: The current sipwitch in proposed doesn't build with the older ucommon. So I think both have to go. Trying that now. [14:30] Nope. That fails on the newer libexosip. [14:32] ScottK: oh :( [14:32] I think the whole lot needs to go. [14:33] if we cared enough, we could add a ucommon5 source package... [14:37] No, I don't think that would do it. [14:38] sipwitch depends ucommon >= 6 [14:48] ScottK: I mean have both ucommon and ucommon5 so that packages could build with whichever one they need...but I didn't test that either [15:26] Cleared out. [15:54] Doesn't seem to have made anything worse. === Ursinha-afk is now known as Ursinha [16:01] rtg: Yeahp, I'll get it shoved along after my morning meeting. [16:02] infinity, too late, cjwatson already gave it the nudge it needed [16:03] rtg: Oh. So he did. [16:04] infinity, he updated d-i, and I just received emails that all have been promoted [16:05] * infinity nods. [16:05] now, I'm gonna upload -rc5. [16:05] I just twiddled the seeds to match, since I didn't get to mucking with making that all work automagically over the weekend. [16:11] ta, I had it uncommitted for when it landed === Ursinha-afk is now known as Ursinha