=== dendrobates is now known as dendro-afk === nhandler_ is now known as nhandler === sikon is now known as lucidfox === bladernr_ is now known as bladernr_afk [02:21] slangasek, smb i'd appreciate your thoughts on my most recent comments in bug 898373 . [02:21] Launchpad bug 898373 in cloud-init (Ubuntu) "fsck.ext3: Device or resource busy while trying to open /dev/xvda2" [High,Confirmed] https://launchpad.net/bugs/898373 [02:21] it seems that cloud-init actually could be causing the fsck race, but i'm not sure how to avoid it. === nhandler_ is now known as nhandler === JackyAlcine_ is now known as JackyAlcine === pp7 is now known as malkauns [04:43] Does anyone happen to have a high-level guide to understand what a GNU/Linux "service" is, and the attendant concerns for someone needing to write one? [04:45] MrBusiness: that's a pretty broad question, what are you trying to do? [04:45] Well, let me see if I can put it into words [04:46] I've been assigned to convert some manner of program into a service. I see that much of what constitutes a service appears to be a set of commonly accepted scripting interfaces, as outlined in /etc/init.d/skeleton, at least assuming I have not already erred in my understanding. [04:47] Now, that said, I also notice that in order for these things to work, the services usually write their PID to a file upon launching so that the appropriate PID can be interacted with during later service calls to that process. [04:47] MrBusiness: hold on [04:47] Which gives me cause to wonder: if I wanted to variations on the same binary running as separate services, does this imply that I would need some sort of advanced logic with which to distinguish them and their respective PID identification files? [04:48] MrBusiness: so if I were writing a new service, I would use upstart, not the old sysv stuff [04:48] MrBusiness: look in /etc/init for examples, and here: http://upstart.ubuntu.com/ [04:48] Is upstart based on the same sort of thing that came out of RedHat, or is it specific to Ubuntu? [04:49] MrBusiness: I do not know the origins, I do know that Ubuntu uses it [04:49] MrBusiness: and so did webOS [04:49] If you're talking about old-style (init.d) services, you may be interested in start-stop-daemon, especially with --pidfile and --make-pidfile [04:50] hmm, ok [04:50] Well, that's helpful. At this point, I guess I need to figure out just what it is that I'll be interacting with. [04:50] the last service I wrote watched a directory using inotify and responded to changes there [04:50] there are dozens of ways to talk to your service of cours [04:51] I see. That's somewhat less than reassuring, but so it goes. [04:51] upstart (Ubuntu), systemd (Red Hat), etc. are relatively similar at a high level -- you write a config file describing the service that init uses, instead of a shell script [04:51] and yes, the init.d style is just a shell script with conventions. [04:52] Ah, ok. That's probably what I'm dealing with here then. [04:52] MrBusiness: you said it's a program, so how do you communicate with it now? [04:52] at the moment, the only methods of communicating with it are defining its startup parameters [04:53] after that, it just sits around doing its business periodically [04:54] MrBusiness: so it runs on a schedule? [04:54] yes [04:54] Does it perhaps then just want to be called periodically by cron, rather than being a daemon itself? [04:55] RAOF: not a bad plan. [04:55] No, because it was designed to run continuously. There are parts that run as cron jobs, but those parts are not being registered as services. [04:55] Ok. [04:56] MrBusiness: do you need to change those start-up parameters while the code is running now? [04:56] Part of what these things do is watch directories, and I don't really have control over their requirements. I was told to make them into services, and so I am attempting, as best I can, to carry out that order, whether it ultimately comes to good or ill. [04:56] MrBusiness: http://www.netzmafia.de/skripten/unix/linux-daemon-howto.html seems like a reasonable HOWTO for the nuts and bolts of converting something to a daemon. [04:56] No, I don't need to change them. I just need to get them installed and running as proper services. [04:56] MrBusiness: I wonder if all you need to do is make a simple upstart script and fire it up [04:57] Yeah. If they're already daemonising properly you should just be able to write a very simple upstart script. [04:57] Might be. I'm working from some legacy code to do this. I haven't quite described what is, in my view, the really onerous aspect of the thing, but it's difficult for me to describe it. [04:57] Let me see if I can explain it [04:57] MrBusiness: my last service was a python script that I wanted running when the system started [04:58] MrBusiness: I just put command-line args inside the upstart job, you could use a conf file or gsettings to change params too [04:58] One common thing I see in most services is that typically they tend to refer to a daemon process, of which there is typically only a single instance executing on a given system. [04:58] I don't think that is a reasonable assumption for the processes I am attempting to convert into services. [04:59] In fact, I am certain that there may be multiple instances of these processes, each running to perform similar tasks, but on different locations [04:59] and that each must be considered its own service [05:00] MrBusiness: so you have upstart fire-up either N jobs or have a wrapper that reads a conf file and fires up N instances [05:00] So, this sounds more like a deployment problem, rather than related to Ubuntu development ... [05:00] MrBusiness: you can put actual shell scripts into upstart so you could read a conf file in there [05:00] Perhaps it is. Should I be in some kind of #deployment channel? [05:00] MrBusiness: Perhaps rather than talking about terminology (service, process, etc) we start talking about *behaviour*. What do you need to change in their behaviour? Do you need the ability to monitor them with “status $SERVICENAME”? Do you need them to be started on boot? Do you need them to be restarted when they crash? [05:01] MrBusiness: upstart will restart crashed services, which is nice [05:02] let me think for a minute [05:02] #upstart might be a better channel for this, indeed. [05:03] MrBusiness: may I suggest that if you truly have N processes watching a bunch of directories that you write a wrapper (python would be easy) to do all the watching (started by upstart) and fire up your program based on what directory changed? [05:03] RAOF: agreed. hopefully we gave him enough to consider [05:05] mfisch, a nice idea, but unfortunately beyond my power to enact at this point [05:05] I don't have sufficient control of the requirements. it sounds to me like I get to watch this thing blow up in my face. rather than spend anymore time on it, I think I'll just update my resume. [05:06] Gotta know when to hold 'em, gotta know when to fold 'em. [05:12] MrBusiness: I obviously don't have a good grasp of your requirements, but nothing so far sounds particularly difficult; drop by #upstart and I'm sure we can set you up with something. [05:12] alrighty [05:13] Only one thing about it though, is that I'm not even certain that I'll have upstart available to me. I may be rolling with the init.d methods, because that may be the only thing available on the target environment. [05:17] Depending on what you need, www.supervisord.org (‘supervisor’ package in Ubuntu) might be helpful. [06:05] Good morning === aalex-home_ is now known as aalex === tkamppeter_ is now known as tkamppeter === aalex is now known as aalex-home [07:46] good morning [08:17] do packages that have not passed the NEW queue need a FFE if they are not accepted before FF? [08:21] tjaalton: no, usually we count the upload date [08:21] pitti: ok, good [08:21] NEW processing seems to be a bit on the slow side these days [08:21] no wonder, everyone trying to squeeze things through ;) === jodh is now known as jhunt [10:10] Who did the MoM pages again ? :) [10:10] cjohnston: ? [10:10] cjwatson :) [10:16] dupondje: launchpad.net/merge-o-matic [10:17] tumbleweed: https://merges.ubuntu.com/ is stuck it seems :) [10:17] not updated since 10/02 [10:18] SpamapS: yes, MoM is crashing at the moment; thanks for noting that, I'll take a look [10:19] dupondje: ^ there you go, then :) [10:20] indeed ;) [10:20] * cjwatson was going through scrollback ... [10:20] ValueError: process failed 2: dpkg-source -x gexiv2_0.3.1-1.dsc /srv/patches.ubuntu.com/unpacked/g/gexiv2/0.3.1-1 [10:22] I think I'll just nuke that - the .orig checksum in Debian's .dsc is wrong, but there's a subsequent version which unpacks properly [10:22] it was in experimental anyway [10:23] will need to wait until the current run has finished though [10:23] dak accepted a .dsc with an incorrect checksum? [10:24] it's dated a while back [10:24] actually I think what happened is that it was correct at the time, but it was removed from experimental and then a new version was uploaded later with a different orig ... [10:25] yeah, looks likely [10:25] which dak should have caught in principle but evidently hadn't retained the information [10:25] * cjwatson pokes DktrKranz with a spoon [10:25] evil reusing of version numbers [10:28] huh? [10:31] $ grep '^ .\{32\} .*orig' gexiv2_0.3.1-*.dsc [10:31] gexiv2_0.3.1-1.dsc: 50d15e0f84c799fccea9aa7c28fd971a 29525 gexiv2_0.3.1.orig.tar.gz [10:31] gexiv2_0.3.1-2.dsc: fc2a438af67af7c9f27bbe0c19b31c98 30155 gexiv2_0.3.1.orig.tar.gz [10:32] should've been 0.3.1+, really (but too late now) [10:42] hhm, right [10:44] so I now need to convince merges.ubuntu.com that it's never heard of 0.3.1-1 and that those aren't the droids it's looking for [10:45] apt-get install alzheimer [10:45] :) === _salem is now known as salem_ [11:52] does debootstrap honour http_proxy or is there a trick to it ? [11:53] it should just honour it [11:53] I mean it just calls out to wget [11:53] it doesn't have any specific proxy code [11:56] cjwatson, ahh thanks, seems there is a sudo zapping those variables ... sigh [11:59] apw: set the proxy system-wide in control-center -> network -> proxy [12:00] that'll write it into /etc/environment instead of just your local session gsettings [12:06] Anyone with some C++/Qt clue fancy making packagesearch build? I've tried backporting the obvious patch (from http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=639076) from upstream svn but it still fails, and even after I fix up some silly missing-translation bits in upstream svn the current tip fails to build in different ways in both precise and unstable. [12:06] Debian bug 639076 in src:packagesearch "packagesearch: FTBFS: keymaker.h:64:10: error: a template-id may not appear in a using-declaration" [Serious,Open] [12:06] I'm on the verge of just removing the binaries from the archive (since they're keeping old libept1 in place) but thought maybe some Qty person might care. [12:30] Riddell: do you know whether/how I can supply extra cmake build options (-DWITH_FFMPEG=OFF) in a standard dh7 debian/rules? [12:30] hello [12:31] anyone to answers some questions about iso generation? there is nobody on #ubuntu-iso :-/ [12:32] pitti: you need to override dh_configure or whatever it is [12:32] /usr/share/perl5/Debian/Debhelper/Buildsystem/cmake.pm doesn't say something obvious [12:32] override_dh_auto_configure: dh_auto_configure -Skde -- -DCMAKE_USE_RELATIVE_PATHS=ON [12:32] pitti: something like that? [12:32] Riddell: nice, thanks! trying that [12:33] Lost most my compiz key bindings with the latest upgrade; anyone else experience this? === MacSlow is now known as MacSlow|lunch [12:39] I would like to use more than one repository in addition to the ubuntu one when generating a CD [12:39] Riddell: worked like a charm === TeTeT_ is now known as TeTeT [12:45] pitti: now you just need to persuade all the canonical and gnome developers to do the right thing and change to cmake :) [12:46] -ENOTENOUGHMAGIC :) [12:49] Riddell, it's not friday, no trolling! ;-) [12:59] is there a repository for infinality font patches, or should I get the source and compile it with these patches? === MacSlow|lunch is now known as MacSlow [13:58] I seem to have a package that FTBFS using fakeroot, but works under real root. I can pin down the cause further, but has anybody seen anything like this before? Any advice? === dduffey_afk is now known as dduffey [14:04] rbasak: not unheard of; can you narrow that down a bit? [14:10] I think it might be a build-dep that provides an executable that segfaults unless it's root. Testing that hypothesis now. [14:29] ev: there? [14:29] m4n1sh: hi [14:29] hello Evan [14:30] how's it going? [14:30] I am trying to integrate diagnostics in alm [14:30] the thing is that there are two files [14:30] one is about panel intergation [14:30] but also contains lots of Panel plumbing code [14:31] ev: since you have written the code, if you can quickly tell me which all thing is g-c-c specific [14:31] sot that I can quickly integrate it. Need to get this release out by tomorrow. [14:32] m4n1sh: preferences-panel.c contains the g-c-c bits. whoopsie_daisy_preferences_panel_init is the entry point. [14:32] okay [14:33] checking [14:34] ev: under canonical contributor agreement? [14:34] m4n1sh: that's a good question. [14:34] if that codebase is under whoopsie then I think it can apply [14:34] but if I take it and keep it under acitivity-log-manager repo [14:35] then it should not apply [14:35] not a lawyer, but I guess that can be the case [14:36] just checking [14:36] okay === Ursinha_ is now known as Guest56696 [14:49] m4n1sh: I'm checking with the right authorities :). I wouldn't worry too much about getting it merged in today. The code already exists in the archive, and I think moving it from being its own page to being a GtkNotebook page is more of a UI freeze issue than a feature freeze one. [14:50] yes [14:50] even I think so [14:50] Especially given that we may be blocked on this contributor agreement issue for a few days. [14:50] can you confirm with the release team [14:50] about whether it falls with UI freeze or feature freeze [14:51] ev: even I feel it to be a UI freeze one, but if you can check out with anyone in release team, it would be great [14:51] sure [14:51] please update me once you have confirmed === bladernr_afk is now known as bladernr_ === dendro-afk is now known as dendrobates [15:00] ev: I have a feeling that FF applies to this because whoopsie is not enabled by default [15:00] m4n1sh: whoopsie will be enabled just as soon as I finish making the changes requested in its security review [15:00] it is in main? [15:00] MIR done? [15:03] m4n1sh: there's a MIR, which will be approved once the changes requested by the security team are made (I'm in the midst of that now) [15:03] great [15:03] excellent [15:03] once that's done, I just need to seed it and it will be running by default [15:03] :) [15:04] m4n1sh: cjwatson (of the release team) suggests it is not a feature freeze matter. [15:04] so by all means, release what you have :) [15:05] not this particular part of it. [15:05] release yesterday itself [15:05] Didier uploaded it [15:05] I uploaded it yesterday since I was not sure if I could complete this one [15:05] cjwatson: thanks for clarifying [15:27] cjwatson, I just updated my notebook and got a libc6 error - now I have packages with umnet dependencies - Do I follow the running -f instructions or do I need to do something else? [15:29] akgraner: can I see the exact error messages [15:29] can't give advice without that [15:30] cjwatson, sure one sec I'll get them to you - they are on a different machine than the one I am using for xchat. [15:34] It looks as though someone on #ubuntu+1 has a similar issue?: "can anyone help me fix broken apt? E: Internal Error, No file name for libc6" [15:38] arand: well, once again, would need more details than that ... [15:38] release, architecture, whether multiarch is enabled, full transcript of upgrade attempt, ... [15:40] cjwatson, dropped it to you in a pm along with what I did when and the point at which I was advised to contact you. [15:41] cjwatson: "I'm on P, amd64, with multiarch" which is the upgrade log file to look for? [15:42] cjwatson: "term.log: http://paste.ubuntu.com/841833/" === dendrobates is now known as dendro-afk [15:52] arand: bizarre. 'sudo dpkg --configure -a' might help [15:52] Having trouble seeing why apt got the ordering wrong in the first instance there. [15:52] * cjwatson notes that there is nearly a day's gap between the first error there and the attempt that apparently led to this report [15:53] cjwatson, yah definitely [15:53] too busy to deal with apt most of the time [15:54] so usually i just leave it broken until i need to fix it :P [15:58] cjwatson, hey that seems to have fixed it [15:59] that + apt-get -f install [15:59] ok [15:59] thank you [15:59] sadly hard to work back to the cause at this point [16:00] next time, assuming you were using update-manager, 'ubuntu-bug update-manager' should attach a state tarball to the bug that would be enough to let us reconstruct the initial state [16:00] nice [16:00] thanks [16:19] does anyone have a suggestion for a particular person who might be a good candidate to review the lowlatency kernel in REVU (http://revu.ubuntuwire.com/p/linux-lowlatency)? [16:19] luke y has already advocated it, so we just need one more person [16:21] can I have some list-moderation on ubuntu-devel-announce please? [16:25] tumbleweed: done [16:26] thanks [16:27] cjwatson: MoM is still broken? === sgnb` is now known as sgnb [16:32] dupondje: it's running [16:32] took a while because it had been down for a while [16:33] cool :) === bladernr_ is now known as bladernr_afk [17:05] mm cjwatson I note some errors in the MoM pages [17:05] python-drizzle for example gives 1.0-2ubuntu1 as current version [17:05] while 1.0-3 got uploaded weeks ago [17:05] same for samba4 [17:21] apw: hey, around? [17:22] didrocks, hi [17:22] cjwatson: Hi - could I trouble you to bump the priority on the 2 [17:22] builds here: https://launchpad.net/~jamesodhunt/+archive/upstart-testing ? [17:23] apw: I'm wonering if you know of any kernel issues which can be stated as "after a period of lot of writing on disk (even swapping maybe), the CPU usage is going crazy" [17:23] jhunt: I don't see any builds there right now? [17:23] didrocks, is that continious writing? [17:23] apw: no, the writting ended [17:23] but yeah, I has some continious one [17:24] right now, my CPU usage is between 60% and 80% on my 2 cores, and if I look at htop, the sum of what is >1% should be at 20% max [17:24] cjwatson: sorry - wrong ppa. should be https://launchpad.net/~jamesodhunt/+archive/upstart-job-logging [17:24] seems everytime I swapped, I get this [17:24] didrocks, the only diskio and cpu usage issue i have heard of is a possible issue xfs when the cache gets full [17:24] didrocks, otherwise no i am not seeing the same herre on anything [17:24] seems that seb128 got something similar somethimes [17:25] jhunt: done [17:25] apw: I have such a behavior once a day at least, which forces me to reboot, anyway I can ensre that the CPU usage comes from some kernel threads? [17:25] cjwatson: thanks! [17:25] didrocks, get the machine up to date, and if it is reproducible lets get a bug filed please with a good description of your reproduce by [17:25] didrocks, and include w [17:25] jhunt: I like that changelog! [17:25] didrocks, and include a ps -ef with the bad processes listed please [17:26] apw: well, I'm up to date and getting that for now some weeks :) [17:27] didrocks, yep and we had a pile of stable updates in the last kernel which was just the last day or two, so i want to make sure its not already fixed by that [17:27] Any Jockey devs in here? [17:27] apw: ok, let me check I have the latest and greatest [17:46] smoser: ah; this cloud script that's looking inside disks certainly fits the bill [17:47] apw, ogasawara: I binNEWed the new kernel, finally built on armel; can you please upload -meta? [17:47] pitti: yep, will upload right now [17:47] ogasawara: cheers! === bkerensa_ is now known as bkerensa [17:55] slangasek: hey, I seem to remember you knowing a bit about lvm2 and udev ;) I upgraded two of my servers to Precise and noticed a "sh -c /sbin/lvm vgscan; /sbin/lvm vgchange -a y" and it's child "vgchange -a -y" apparently spawned by udev but never exitting as expected. It's not causing any problem on these machines though but looked weird. [17:55] slangasek: a very quick LP search gave me bug 802626 as a potential candidate for that weirdness [17:56] stgraber: yes, the bug is still outstanding; there's a proposed fix from hallyn that I haven't managed to find time to review yet === dju_ is now known as dju === maxb is now known as Guest79372 [18:04] stgraber: yeah, that one's annoying isn't it :) [18:05] hallyn: well, in my case it's only annoying when running "ps aux" on my all new server ;) it doesn't actually prevent anything from starting or cause any other issue that I could see [18:05] interesting [18:06] I have 3 PVs and 3 VGs on that machine, 1 of them is on RAID1 and contains the root LV, the two others are currently empty (no LV at all) [18:08] my other server has hardware RAID (HP) but also has 3 PVs (3 RAID volumes) and 3 VGs, though in this case, they all have LVs and are all used === mchro- is now known as mchro === zimmerle` is now known as zimmerle === nhandler_ is now known as nhandler [18:35] barry: in case you haven't seen, sphinx has a bug fix in unstable as well as needs and MIR (or something done) for python-whoosh === deryck is now known as deryck[lunch] [18:43] akgraner: ping [18:43] m_3 pong [18:46] barry, congrats! === bladernr_afk is now known as bladernr_ [18:52] barry: congrats on the dmb election! === jtaylor_ is now known as jtaylor [18:56] %rfs [19:05] broder: thanks! === pdimitrov is now known as pr0ggie === tobin is now known as joshuaAFK === deryck[lunch] is now known as deryck === tomreyn_ is now known as tomreyn === gord_ is now known as gord [19:53] who owns nm-applet, the below cannot be right [19:53] 2942 apw 20 0 6815m 1.7g 3080 S 2 43.3 21:56.80 nm-applet [19:55] bug /930491 [19:55] bug 930491 [19:55] ah, bot is awol [19:57] apw, cyphermox [19:57] though I guess he could try to blame it on indicators,dx [19:59] apw: I'm aware of it, trying to track it down [20:13] barry: Is it you or doko that's supposed to do the lucid update for dh_python2? === salem_ is now known as _salem [20:23] ScottK: doko [20:24] Sigh. doko: Can we get this done? It's really causing problems. === emma_ is now known as em === em is now known as emma === emma is now known as em === mbarnett` is now known as mbarnett [20:54] smoser: would you by chance be willing to test the latest ppa upstart build, to confirm that the logging support works as intended in the various cloud configurations? https://launchpad.net/~jamesodhunt/+archive/upstart-job-logging [21:00] slangasek, i can look tomorrow. is there a doc on what i'm supposed to see ? is it writing to /var/log/upstart.log ? [21:00] slangasek: is migrating packages to multiarch something that requires a feature freeze exception or is it just a normal bug? === parasight_ is now known as parasight [21:16] YokoZar: FFe [21:16] smoser: /var/log/upstart/, one logfile per job that outputs [21:16] smoser: http://www.theorangenotebook.com/2012/02/call-for-testing-upstart-14.html === dendro-afk is now known as dendrobates [21:35] hey, I need a place to host a small file for transmission SRU - so called blocklist (a list of ip ranges that BT client does not allow connecting to and rejects connections from) [21:36] kklimonda: what does modern transmission use if the project isn't hosting the file anymore? [21:36] (and can the sru switch to doing that instead) [21:37] broder: they have changed UI providing a way to set custom url instead [21:37] cyphermox, may also explain didrocks symptoms [21:37] kklimonda: is there a default? [21:37] broder: no, it's set to example.com [21:37] or something like that [21:37] cyphermox, mine is growing slowly but surely too: [21:37] 2942 apw 20 0 7165m 1.7g 3116 S 2 45.6 23:09.04 nm-applet [21:37] kklimonda: it sounds like it's not actually mandatory anymore. can we just disable the blocklist? [21:38] broder: but blocklists just don't work in 10.04 [21:38] broder: there is no "initial" list so there is no way to use this feature anymore :) [21:39] (it has never been mandatory, but it's a very popular feature of BT clients and we got some reports of it not working) [21:39] i see [21:40] kklimonda: I'm not sure why we'd need to host a file? There doesn't need to be a default blocklist (and, in fact, there isn't...) [21:41] infinity: but in 10.04 there is no way to change the blocklist url [21:41] infinity: it's hardcoded to http://update.transmissionbt.com/level1 in code, and the url is gone :) [21:41] kklimonda: Which is unfortunate, but "oh well"? [21:42] kklimonda: If you know what was in that file, you could just ship a copy with the package on-disk, and point to that. [21:42] infinity: hmm, that may work [21:42] kklimonda: But, really, there will be a new LTS in a couple of months, and it seems remarkably unlikely that the intersection of "people who torrent", "people who care about blocklists" and "people who run old releases" is very large. === dendrobates is now known as dendro-afk [21:47] infinity: yeah, it's still a bug though and us not fixing it for package in main sucks a little === jussio1 is now known as jussi [22:41] slangasek: cjwatson: I just read https://bugs.launchpad.net/ubuntu/+source/libidl/+bug/931388 and it's worrying me because I used depends: wine1.4:any in the new wine1.4 packages as part of multiarching. Will I need to do the dummy-package-with arch:all workaround? [22:41] Launchpad bug 931388 in libidl (Ubuntu) "overenthusiastic adoption of "Depends: cpp:any" syntax" [High,Triaged] [22:42] (relatedly, wine1.4 is still half in the queue because wine1.2 and wine1.3 aren't yet deleted from the archive) [22:42] YokoZar: I don't know what workaround you're proposing, but you aren't meant to be using :any yet in depends [22:42] slangasek: the workaround is at the bottom of this page: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=641614 [22:42] Debian bug 641614 in libidl "please convert to multiarch" [Normal,Open] [22:44] YokoZar: ah; ugly, but yes, that would do it === dduffey is now known as dduffey_afk [23:09] YokoZar,slangasek: as I said in the Debian bug, I haven't tested that workaround yet, and it's mostly instinct [23:10] YokoZar,slangasek: if that approach works, I think it might be worth documenting in MultiarchSpec for the time being; I forgot this problem myself when talking to TREllis about the libidl implementation [23:10] yeah, I've only eyeballed it; I don't see any reason it wouldn't work [23:10] cjwatson: is the wine upgrade case different from the libidl case as wine already requires a new packagename? [23:11] YokoZar: that doesn't make any difference [23:11] cjwatson: slangasek: regardless, I'll have to test it anyway. [23:11] YokoZar: it's still entirely possible that lucid's apt will be called upon to parse it [23:11] or for that matter germinate [23:15] cjwatson: Are you implying Wine will be pulled in by germinate :D [23:15] I think it is dangerous to take approaches that are known to fail [23:26] d'oh! for the life of me i can't figure out why sometimes bzr seems bound when it shouldn't be [23:29] (oh well, that forced me to not pussyfoot around for another month fearing to commit :) [23:37] TheMuso`: is the current plan alsa 1.0.25 for precise or sticking with 1.0.24? wasn't really clear to me from blueprints