[00:00] <cjwatson> But you need to search for "final:" first so that you skip the sequence where it tries every package individually
[00:00] <cjwatson> BTW for people with ubuntu-archive@snakefruit access, "chdist apt-get 14.09-proposed-armhf install foo" etc. should work
[00:00] <cjwatson> (can't actually install, but you can have it simulate and then say no)
[00:01] <infinity> That gets back to the weird langpack issue but yeah, also ubuntu-system-settings : Depends: libupower-glib1
[00:01] <infinity> Is something dire with langpacks in -rtm?
[00:02] <cjwatson> The most confusing thing is generally that proposed-migration simulates the migration as if all NBS binaries were removed, which you probably know, but it does require telling apt-get that it can't use those ones
[00:03] <infinity> Is rtm just broken in general, even?  Wow.  Drilling down makes it worse, not better. ;)
[00:04] <cjwatson> ubuntu-rtm/14.09 does have some uninstallables; I never quite cleared all the chains there
[00:04] <cjwatson> It's usually not particularly terrible
[00:04]  * sil2100 just cares for touch in ubuntu-rtm and just wants a new upower there
[00:04] <infinity> Oh, no, I'm mostly just trying to install conflicting things.
[00:05] <infinity> The langpack thing still looks like a bit of a mess, though.
[00:05] <sil2100> Yeah, it actually conflicts with the touch langpacks too
[00:06] <infinity> Right.
[00:06] <infinity> So, removing all the conflicts and paring down a bit, I get left with your ubuntu-system-settings dep.
[00:06] <infinity> I think that's all you need to fix here.
[00:06] <sil2100> YESSSSS
[00:06] <sil2100> That's the best thing I heard today
[00:07] <sil2100> It's still building though
[00:07] <infinity> But we'll know for sure after it's done. :P
[00:07] <infinity> I'm smarter than a computer at some things, but not at doing this.
[00:08] <infinity> Future note to self, desktop-next and touch aren't actually coinstallable.
[00:08] <cjwatson> It would be nice to get britney's interactive hint inspector thing going at some point.
[00:08] <infinity> Cause hey, who would want to try that?
[00:08] <infinity> *sigh*
[00:08] <cjwatson> Might actually work already, I just haven't tried it.
[00:10] <infinity> cjwatson: Well, remember a couple of years ago when someone tried to lump release infrastructure and launchpad into the same pile and give it all to one (very small) group of developers?
[00:10] <infinity> cjwatson: Congrats, you can take britney with you when you go. ;)
[00:11] <cjwatson> haha
[00:12] <cjwatson> I just spent a day merging a year's worth of upstream development into it so that you lot would find it easier to figure out :P
[00:13] <infinity> cjwatson: A day well spent in your self-interest, as it turns out.
[00:17] <cjwatson> hah
[00:39]  * sil2100 keeps his fingers crossed
[01:12] <sil2100> SUCCESS!
[01:13] <sil2100> infinity: thanks for explaining and checking this for me
[01:13] <sil2100> In your FACE upower!
[01:14] <infinity> Heh.
[01:39] <sil2100> infinity: just a quick question... you don't happen to have the permissions and knowledge to build ubuntu-rtm images?
[01:40] <sil2100> Since I suppose slangasek is still in my timezone
[01:42] <infinity> sil2100: I almost certainly have the permissions, but I have not the knowledge.
[01:50] <sil2100> Sadly, I can't find anyone mentioning the exact steps anywhere, and there doesn't seem to be anyone with the right knowledge available
[01:50] <sil2100> hm, and we disabled the cron job doing ubuntu-rtm auto-builds too
[01:51] <sil2100> infinity: don't want to be more of a burden, but maybe you could check what the disabled cronjob was doing? I have no access anywhere there so I can only guess what's going on
[01:53] <sil2100> Already poked rsalveti, but he also seems to be away already
[02:01] <infinity> sil2100: So, it was cronned, then disabled, and people have been running it by hand?
[02:01] <infinity> sil2100: If so, I've probably found it.
[02:02] <sil2100> infinity: we generally have a build once a day, but ogra_ and the others have been also running it manually (somehow) to trigger builds
[02:02] <sil2100> I suppose it's by using the same method
[02:02] <infinity> sil2100: Well, I'll run the obvious thing, and if it turns out I was wrong, someone can yell at me. :P
[02:03] <sil2100> Nooo, no one will yell at you for sure, I doubt there's much that can be broken here - besides generating a broken image, which for the -proposed channel is considered 'acceptable' ;p
[02:03] <sil2100> Thanks!
[02:05] <sil2100> Ok, I need to really EOD now, thanks again for all the help
[02:05] <sil2100> o/
[02:05] <sil2100> (if you'll have trouble building the image then just drop that, I guess this could also wait till ogra_ wakes up)
[02:06] <sil2100> It was anyway just to have an image with just the upower bits, in cases it would break anything
[02:06] <sil2100> But it's well tested on touch since a long time
[02:06] <sil2100> o/
[22:26] <bdmurray> slangasek - https://code.launchpad.net/~brian-murray/ubuntu-archive-tools/sponsors-notification/+merge/244513