/srv/irclogs.ubuntu.com/2014/05/21/#ubuntu-devel.txt

mterryLaney, did you drop the filtering_out_users patch from accountsservice on purpose?00:18
* Logan_ pokes siretart 03:30
Logan_can we sync libav?03:30
Logan_our only delta can be dropped03:32
=== wgrant changed the topic of #ubuntu-devel to: Launchpad offline 06:00 - 06:30 UTC | Trusty Final released! | Archive: Open | Devel of Ubuntu (not support or app devel) | build failures -> http://qa.ubuntuwire.com/ftbfs/ | #ubuntu for support and discussion of lucid -> trusty | #ubuntu-app-devel for app development on Ubuntu http://wiki.ubuntu.com/UbuntuDevelopment | See #ubuntu-bugs for http://bit.ly/lv8soi | Patch Pilots:
pittiGood morning04:10
pittimapreri: well, it's always office hours somewhere on the world :) (I'm in Germany)04:11
Unit193Howdy.04:11
pittihey Unit19304:11
pittixnox: oh BTW, yesterday I figured out the trouble with the py3 AP porting; so once the next autopilot lands in utopic, I'll update shotwell, autopilot-gtk, and ubuntu-system-settings-online-accounts to python304:21
pittixnox: I have the patches already more or less, they just need the autopilot3-sandbox-run04:21
Logan_hey pitti :)04:30
pittihey Logan_, how are you?04:30
Logan_doing well, you?04:30
pittiquite fine, thanks04:31
pittiapw: I did the same for linux-exynos5 and also restricted the test to armhf (it will always fail on x86); files are again on http://people.canonical.com/~pitti/tmp/linux-autopkgtest/04:50
tvosspitti, ping06:07
=== wgrant changed the topic of #ubuntu-devel to: Trusty Final released! | Archive: Open | Devel of Ubuntu (not support or app devel) | build failures -> http://qa.ubuntuwire.com/ftbfs/ | #ubuntu for support and discussion of lucid -> trusty | #ubuntu-app-devel for app development on Ubuntu http://wiki.ubuntu.com/UbuntuDevelopment | See #ubuntu-bugs for http://bit.ly/lv8soi | Patch Pilots:
Logan_doko: FYI, you filed a bunch of dh-autoreconf bugs in Debian twice06:47
Logan_I'm merging them as I come across them06:47
pittitvoss: sorry, missed your ping; hello07:03
tvosspitti, hey there :) sorry, forgot what I meant to ask you :)07:03
pittitvoss: heh - contentless pings FTL :/07:07
tvosspitti, fair07:07
geserdholbach: Hi, re bug #1320612: it looks like your german locale slipped into the test suite. Based on the failure log I guess it could be fixed by setting the locale to "en_US" (like the previous test) but is it worth an additional Ubuntu delta?07:30
ubottubug 1320612 in python-babel (Ubuntu) "Merge python-babel 1.3+dfsg.1-3" [Undecided,Triaged] https://launchpad.net/bugs/132061207:30
dholbachgeser, hum... wouldn't this affect users of a non-English Debian session as well?07:31
geseronly when running the test-suite I guess07:32
geserof course I would forward this to Debian or upstream07:32
dholbachgeser, sure... I meant users of a non-English Debian session who are trying to run a build07:33
dholbachgeser, if you want, I can try to build it again locally with LC_ALL=C and see if that works07:33
dholbachbut it sounds like a bug to me to expect en_US in the testsuite07:34
geseryes, I'll try to fix it and forward it to Debian. Should this block the merge for now?07:35
dholbachgeser, no, I'll do another test build now07:35
dholbachthanks07:35
dholbachgeser, hum07:38
dholbachgeser, 2ubuntu1 builds fine, 3ubuntu1 won't build, even not with LC_ALL=C07:39
dholbachah of course - "Runs the unit test on build (Closes: #727616)" :)07:39
geserdholbach: hmm, why does my pbuilder have no problem in building this package?07:42
dholbachI have no idea07:44
geserI'll try to reproduce this myself and fix the locale issue in the test suite07:46
dholbachgeser, it seems to be the LANG and LANGUAGE environment variables07:50
geserdholbach: it's already fixed upstream: https://github.com/mitsuhiko/babel/commit/2eb475f835375c1b3b7fefcb7d8aad7047d7fda708:11
dholbachgeser, great!08:24
=== _salem is now known as salem_
Mirvis there a way to get PPA builders spit out all the changed symbols instead of stopping at the first library?09:05
xnoxMirv: i think that got implemented  in Debian, not sure if we have that merged yet.09:07
cjwatsonThat wouldn't be a property of PPA builders; it's dh_shlibdeps or thereabouts09:08
Mirvxnox: ok, well good to know09:08
Mirvyeah, not related to PPA09:09
MirvI'll check dh_shlibdeps' current status09:09
cjwatsonWorst case you could pass some permissive -c option to dpkg-gensymbols and then apply logic to the output09:09
LaneyIt's in dh_makeshlibs09:09
cjwatsonEr yeah that09:10
LaneyLooks like 9.2014022709:10
LaneyWhich we should have in trusty and utopic, going by the versions09:10
xnoxLaney: only utopic, no? trusty is so 201309:11
Laneyoh yes09:11
Laneyha, I just saw the 0227 at the end09:11
Laneys/0//09:11
Mirvhmm, so it should actually already work but doesn't for me09:14
Mirvunsurprisingly it was the pkg-kde's Qt developer asking for the feature09:14
=== salem_ is now known as _salem
=== _salem is now known as salem_
=== salem_ is now known as _salem
cjwatsonlool: looks like that worked for fakeroot, btw10:52
cjwatsonerr, echan, but whatever10:52
cjwatsonxnox: Could you merge php5?  php-geoip is waiting for it, and probably anything else that uses dh-php5.11:25
xnoxack.11:26
=== MacSlow is now known as MacSlow|lunch
cjwatsonta11:27
=== jono is now known as Guest41797
=== vrruiz_ is now known as rvr
=== _salem is now known as salem_
RiddellElv1313: yo, still need me to look at sflphone?12:18
RiddellElv1313: I've uploaded to trusty and utopic, please add a test case to clearly describe how to test for the fix12:27
=== sil2100_ is now known as sil2100
=== MacSlow|lunch is now known as MacSlow
zbenjamincjwatson: ping, can we get a pkcon local_uninstall? I'm writing a debug helper script for the SDK that is going to take a click package, install it , run a hook from it, and uninstall it to leave a clean device13:25
zbenjamincjwatson: but i have no root priviledges at that point13:26
cjwatsonzbenjamin: https://lists.launchpad.net/ubuntu-appstore-developers/msg00553.html13:26
cjwatsonzbenjamin: "pkcon remove"13:27
zbenjamincjwatson: awesomeeee thanke :)13:27
cjwatsonJust note the bit at the end of that mail about the particular form of the argument you need to pass to pkcon remove13:27
zbenjamincjwatson: ok so thats packagename;packageversion; ? whats the all? the target arch?13:29
cjwatsonyes13:30
zbenjamincjwatson: so if i have a fat package, how would that look like? only armhf for a armhf device?13:31
cjwatsonIIRC it's not checked so you can just always shove "all" in that slot, I think13:31
zbenjaminah good i'll try that13:31
cjwatsonI think for a fat package it would strictly be "multi", but whatever13:32
zbenjaminyeah i can put that in once we are there13:33
cjwatsonstrictly it would match the filename, so com.ubuntu.test_1.3_all.click => all13:34
cjwatson(well, even more strictly it would match what "dpkg-deb -f foo.click Architecture" says)13:35
pittivila, ev: writing tests for the debci worker is fun :) (creating 100 requests, 30 workers, killing two thirds of the workers, and making sure that all requests still arrive)13:43
ev\o/13:43
evpitti: next step: test that chaos in production13:44
pittihttp://anonscm.debian.org/gitweb/?p=users/mpitt/debci.git;a=commitdiff;h=3c03eec13:44
dobeywho can i beg/bribe to accept some SRUs into their respective -proposed pockets?13:44
evwhoa, ruby?13:44
pittiev: well, not quite the next step (still need to implement the swift up/download and the health monitor), but getting closer13:44
evheh, indeed13:45
pittiev: Antonio wrote some parts of it in ruby (most things are in sh), he's the ruby maintainer13:45
evah13:45
pittiev: not that happy, but as long as it's mostly test helpers and RSS generators I can live with it13:45
evthat's a shame :-P13:45
pittiev: but the implementation of the worker is absurdly simple, I really like that AMQP stuff (http://anonscm.debian.org/gitweb/?p=users/mpitt/debci.git;a=blob;f=bin/debci-worker)13:47
=== pete-woods is now known as pete-woods-lunch
pittithe actual core logic is like 3 lines, the rest is just prettyness13:48
evnice13:48
Elv1313Riddell: Hi, thanks. what kind of test do you want? It is an integration problem (in Akonadi), so it is not really possible to create an unit test without re-creating the contact topology that cause the freeze13:53
Elv1313Maybe I can ask the 2 users that had it to test the new package?13:53
* Laney wows at the number of tests python-defaults has triggered13:53
mterryLaney, did you drop the filtering_out_users patch from accountsservice on purpose?13:54
Laneymterry: it's upstream now, no?13:57
RiddellElv1313: a manual test is needed "install sflphone and akonadi, start sflphone, check e-mail, notice freeze, repeat with new version, freeze will not occur" that sort of thing14:00
Elv1313ok14:00
zbenjamincjwatson: works perfectly14:01
vilapitti: nice14:02
mterryLaney, parts of it, but not the login.defs support14:02
vilapitti: I'm not sure how you assert how many requests are processed when many are killed though14:03
pittivila: if I submit N requests I should get N results, as long as at least one worker is still running14:04
vilapitti: oh, that's the one or two14:04
pittivila: i. e. if a worker dies in the middle of a test, the AMQP request should go back to the queue as it won't get ack'ed14:04
vilapitti: so worse case you have duplicates ?14:05
pittivila: no, the 1 or 2 is how many result directories you get (as the dir gets created when the test starts)14:05
pittivila: right, worst case is you get two results, when it crashes after it wrote the "exitcode" file but before ack'ing the request14:06
pittivila: I can probably refine that a bit to remove an incomplete result directory (when there's no exit code), still on my list14:06
Elv1313Riddell: done14:06
cjwatsonzbenjamin: great14:07
vilapitti: ack14:08
vilaev: that confirms that we either need to stop using prefetch_count=1 or have the worker commit suicide to fix bug #132020514:09
ubottubug 1320205 in Ubuntu CI Engine "nacking a rabbit message is not enough to have another consumer get it" [High,Triaged] https://launchpad.net/bugs/132020514:09
RiddellElv1313: lovely, now we just need a friendly archive admin to review and accept the trusty SRU, try batting your eyelids at ScottK14:09
Elv1313thanks14:09
Laneymterry: that wasn't part of the patch, this is new upstream behaviour14:09
Laneyis it causing a problem?14:09
mterryLaney, no we used to support login.defs in our patch, but upstream doesn't.  So dropping the patch means dropping support for login.defs14:10
mterryLaney, (to define a MIN_UID for considering which users are human)14:11
mterryor UID_MIN, can't remember which way  :)14:11
Laneysec, just got a phone call14:12
brendandcjwatson, how is click chroot create supposed to be run?14:12
brendandcjwatson, click chroot create -a i386 gives option errors14:13
brendandcjwatson, not particularly helpful ones14:13
cjwatsonclick chroot -f ubuntu-sdk-14.04 -a i386 create14:14
cjwatsonorder matters (perhaps unhelpfully)14:14
cjwatsonthat is, the subcommand name needs to come after the options to the chroot command14:14
cjwatson(oh and the whole thing needs to run under sudo)14:15
Laneymterry: okay, the patch added login.defs and went upstream14:17
Laneymterry: we had that in the previous AS in ubuntu14:17
Laneyand now in this release they've dropped that support14:17
cjwatsonargh, python multiprocessing is basically the worst14:17
mterryLaney, ah interesting...  do they say why?14:18
Laneyso yes indeed the minimum UID is specified in configure14:18
Laneybut I think it should be okay14:18
cjwatsonagonisingly confusing errors14:18
Laneymterry: fragile and broken or wording to that effect14:18
Laneyif necessary we could bring it back as a configure option I guess14:18
mterryLaney, why should it be OK?  The touch images use users at 1000 and 1001 and we were relying on that support to not show them in the greeter14:18
Laneywhat were we doing?14:19
Laneywait14:19
Laneythat has a different login.defs?14:19
=== ValicekB_ is now known as ValicekB
mterryLaney, on Ubuntu Touch images, we set UID_MIN in login.defs to 100214:21
mterryLaney, there are radio and system users at 1000 and 1001 used by android14:21
dobeySRUs are such a pain to do :(14:21
Laneybah14:22
Laneymterry: okay I guess we can revert this then :/14:22
Laneydo you want to upload that?14:22
Laneyba13b59c14:22
mterryLaney, sure I can do that14:23
LaneyI'll see about making it configurable14:23
pkernAlso a UID_MAX of 60000 is funny, especially if it's compiled into the binary and not overridable.14:24
=== salem_ is now known as _salem
Laneythe new behaviour doesn't consider a maximum14:25
pkernYay.14:27
=== _salem is now known as salem_
Laneyand under the old one login.defs was able to override it14:28
Laneyho hum14:28
=== Ursinha is now known as Ursinha-afk
=== Ursinha-afk is now known as Ursinha
evvila: can you add that to the bug report? That pitti has confirmed this14:46
pittisorry, what did I confirm?14:51
vilapitti: that killing a worker that is processing a message puts that message back onto the queue so another worker picks it up14:52
pittivila: yes, as long as it doesn't get ack'ed yet; isn't that the whole point of it?14:52
vilapitti: yes, but we thought that *nacking* a message will have the same effect but it doesn't14:53
vilapitti: the worker has to die14:53
pittivila: ah; it sounds like it should, but I haven't played around with that yet14:53
vilapitti: all your workers are on the same host right ?14:57
pittivila: for the test suite, yes (not in production, of course)14:57
vilapitti: yup, that was the question indeed14:57
pittiah, I figured out how to run rabbitmq-server in a test suite as my user14:58
pittivila: oh, does that matter?14:58
vilapitti: not sure, but I can imagine that the behavior may be different when different hosts are involved14:58
pittivila: I hope not..14:59
vilapitti: I mean, at least when thinking about failures, a host dieing with a single worker is not the same as a host dieing with multiple workers :)15:00
pittivila: ah, of course; I meant, it's hopefully transparent wrt. queue ack/nack handling15:00
vilapitti: yes, me too15:01
=== pete-woods-lunch is now known as pete-woods
=== ted is now known as tedg
xnoxslangasek: pitti: what is "fastboot" mode in the boot initscripts?! was that ever supported with mountall?15:29
pittixnox: I'm afraid I never heard of it15:34
pittixnox: I thought "fast boot" was "upstartification in lucid"15:34
slangasekxnox: I don't know anything about fastboot as regards initscripts15:35
xnoxack.15:35
xnoxpitti: slangasek: should the re-introduced scripts actually just be lsb-headers, source init-functions and otherwise empty?15:36
pittixnox: I don't think it hurts that much to just take the debian ones, to make merges easier; there's no other waste than a few kB of hard disk, is there?15:38
* pitti needs to run out now, cu tomorrow15:39
xnoxpitti: slangasek: pushed updates to sysvinit merge proposal. And responded to a bunch of comments.15:47
=== roadmr is now known as roadmr_afk
slangasekxnox: I much prefer the re-introduced scripts be as close as possible to the Debian ones, for future merging16:33
xnoxslangasek: ok.16:35
=== salem_ is now known as _salem
=== sz0 is now known as sz0`
=== sz0` is now known as sz0
=== roadmr_afk is now known as roadmr
xnoxis launchpad being sad, or is it me? (code hosting / branch scanning?!)17:50
roadmrit was a bit slow about an hour ago, took about 10 minutes to produce a diff18:05
bdmurraymvo: bug 1320683 is surely because of phased updates18:06
ubottubug 1320683 in update-manager (Ubuntu) "Update manager does not show all available updates" [Undecided,Confirmed] https://launchpad.net/bugs/132068318:06
bdmurraymvo: you can see the status of packages phasing at http://people.canonical.com/~ubuntu-archive/phased-updates.html18:07
sarnoldbdmurray: ah, thanks. I'd forgotten about that entirely.18:09
bdmurraysarnold: no problem18:10
=== _salem is now known as salem_
=== sz0 is now known as sz0`
=== salem_ is now known as _salem
=== sz0` is now known as sz0
lamontRiddell: you around by chance?19:05
lamontor xnox19:05
xnoxlamont: hi!19:06
=== sz0 is now known as sz0`
lamontI have sflphone questions, and your name is on it19:07
=== sz0` is now known as sz0
xnoxlamont: only marginally =) go on =)19:08
lamontit believes in binding to the IP address of the default gateway, rather than the IP address associated with the route to the server... I wish to fix that, and it's a rather large codebase... hoping for a pointer19:11
lamonts/of/associated with/19:11
lamontxnox: ^^19:12
lamontor I an pester msp later19:12
xnoxlamont: wow. definitely beyond what i've done with sflphone.19:14
lamontxnox: no worries19:17
=== sz0 is now known as sz0`
mterrypitti, do you know much about how the volume up/down events are handled in Ubuntu Touch?19:32
=== cyphermox_ is now known as cyphermox
lamontxnox: and figured out how to do it, though there is a bug19:45
=== sz0` is now known as sz0
lamontxnox: gnome/src/config/accountconfigdialog.c line 1048... help me understand "CONFIG_LOCAL_INTERFACE" there?19:58
lamontwhich is more of a dbus question thananything else19:59
xnoxlamont: that does look wrong.20:03
dobeyxnox: can you approve things to go into -proposed for SRUs?20:04
xnoxdobey: no. you want ~ubuntu-sru20:05
xnox(loop up their team on launchpad to see who is in it)20:05
xnoxlamont: what is account_lookup?20:06
* xnox presume calling into gnome account settings api.20:06
dobeyinfinity: can you accept some things to -proposed for me?20:06
xnoxlamont: and i guess you want to make sure CONFIG_PUBLISHED_SAMEAS_LOCAL is false.20:06
dobeystgraber, slangasek: ^^ or one of you can accept stuff to -proposed for these SRUs for me?20:07
xnoxdobey: it's typically useful to mention which package you are after, and for which of the stable series....20:08
xnoxthere 68 unapproved requests at the moment20:09
lamontxnox: yeah it sure looks like it wants a bug20:09
dobeyubuntuone-client and ubuntuone-storage-protocol for saucy and precise20:09
stgraberanyway, I'm off till Monday and on a pretty sucky internet so I won't do any queue review until I'm back some place with better connectivity (that may very well be on Monday in Malta)20:09
dobeystgraber: ok, thanks. didn't know you were away. enjoy20:10
xnoxlamont: so the full line is all withing sflphone configuration of the account (and it's properties).20:11
lamontok20:11
xnoxlamont: that's not really stock dbus api or anything, just a bunch of functions that sfphone wraps.20:11
infinitydobey: I'll have a look.20:12
dobeyinfinity: thanks20:12
lamontxnox: what I want is for it to pick the IP address of the interface I override, and not the default-gateway interface20:12
xnoxlamont: right, that dbus call is defined in ./daemon/src/client/dbus/configurationmanager-introspec.xml20:14
xnoxlamont: which takes you to getAddrFromInterfaceName C++ method20:14
xnoxwhich is defined as20:15
xnoxreturn SipTransport::getInterfaceAddrFromName(interface);20:15
xnoxline 107 in ./daemon/src/sip/siptransport.cpp20:16
xnoxlamont: i think you'll need to fix that function ^20:16
xnoxcause that's where it computes the value it uses, in a cryptic way...20:17
xnoxlamont: does that help at all?!20:17
infinitydobey: Why the en_US.UTF-8 requirement for tests on saucy?20:21
dobeyinfinity: becasue some of the cert files have non-ascii names, and the default locale is that weird ANSI thing that only does ascii, which breaks python encode/decode stuff20:24
infinitydobey: Ahh.  C.UTF-8 would probably do the trick without making you need a langpack build-dep.20:25
infinitydobey: But I this works too.  *shrug*20:25
infinitydobey: Was just curious.20:25
dobeymaybe. we were already doing the en_US.UTF-8 bit elsewhere though, so i just copied that20:26
infinityTÜBİTAK_UEKAE_Kök_Sertifika_Hizmet_Sağlayıcısı_-_Sürüm_3.pem20:26
infinityWow.20:26
dobeyyeah20:26
infinityKay, explanation accepted. :)20:26
infinitydobey: The only followup, then, is why not the same patch for precise, in case ca-certs gets updated there with similar consequences?20:27
dobeyi thought i did do the en_US thing on precise too20:27
lamontxnox: that may help.  C++ may not.20:27
infinityNot in this upload.  If you did, it was a previous one.20:27
* infinity looks.20:28
xnoxlamont: that function, is pure C by the looks of it thought.20:28
dobeyhuh. well, i did it like a month ago, so i don't remember exactly20:28
dobeyif i didn't do it on precise, it was because the tests didn't fail when i did the test build, most likely20:28
infinityOh.  precise might not run a testsuite at all.20:29
dobeyoh or that20:29
infinityIt doesn't have the override with ./tun-tests20:29
dobeyprecise is quite old, yeah20:29
infinitySo, yeah.20:29
infinityAlrighty.  Acceptiferating.20:29
dobeythanks20:29
infinitydobey: Also, this isn't carte blanche to be annoying, but when you have deadlines like the U1 shutdown in 10 days, bugging people earlier wouldn't be a bad thing.20:30
dobeyinfinity: i have been bugging :(20:30
infinitydobey: Oh.  You should have bugged me.  And maybe included the "hey, there's a deadline" bit.  Oh well.20:30
infinitydobey: As it stands now, I think I'm going to ask you guys to verify the crap out of those u1-client uploads as best you can, so we can phase them to 100% when we release, and hope they get out to most people ASAP.20:31
lamontxnox: wondering if maybe that's getting called with DEFAULT_INTERFACE20:31
xnoxlamont: hm. not sure. if you file a bug CC / subscribe me on it. for me to have a look, when i'm bored on a connection flight.20:32
xnoxlamont: cause i'm deep in async upstart code at the moment and hope to get this done before EOW.20:33
infinitydobey: And poke me personally when it's verified, I think the client one is worthy of an early release if you've tested it well.20:35
lamontxnox: sure20:35
xnoxlamont: the argument that should be called, should be whatever was stored in the account key, no?!20:36
dobeyinfinity: sure20:36
infinitydobey: Oh, except https://bugs.launchpad.net/ubuntu/+source/ubuntuone-client/+bug/1306225/comments/3 isn't very promising...20:36
ubottuLaunchpad bug 1306225 in Ubuntu One Client "The user should be informed about the u1 file service shutdown" [Critical,In progress]20:37
dobeyinfinity: thanks much20:37
infinitydobey: Is there no way to get that working at runtime instead of shutdown?20:37
dobeyinfinity: yeah, though at this point i'm thinking it's worth it to just release the update anyway, given how close june 1 is. the "not connecting" bit is going to be more important by the time we could get a new upload to fix the notification on precise (i have no idea why the notification is behaving that way on precise. it might be a much larger problem)20:38
dobeytrying to test on saucy right now. just waiting for the archive to get updated so apt will work20:38
lamontioctl(13, SIOCGIFADDR, {ifr_name="tun0", ifr_addr={AF_INET, inet_addr("10.172.126.2")}}) = 020:38
lamonthrmpf20:38
=== pbn_ is now known as pbn
xnoxlamont: cheat =) debugging c++ with strace =)))))20:39
lamontxnox: I was doing thatbefore I looked at the source20:39
lamontbecause that's how I roll20:39
xnox=)))))20:39
xnoxs/roll/troll/ ?!20:39
Riddelllamont: Elv1313 is the sflphone man, try tracking him down if you have questions20:39
mdeslaurmvo: can you confirm there's nothing to do with apt in bug 1016643?20:40
ubottubug 1016643 in apt (Ubuntu Quantal) "add-apt-repository downloads gpg key in an insecure fashion" [High,Triaged] https://launchpad.net/bugs/101664320:40
mdeslaur(/me is closing ancient bugs...)20:40
lamontxnox: and now I can't getit to fail20:43
lamontRiddell: thanks.  here or deban?20:44
lamontdebian20:44
Riddelllamont: upstream20:47
lamontamusingly, I can't actually reproduce the bug20:50
lamontthings do, in fact, seem to work as expected.20:50
dobeyturns out that setting your clock 2 weeks forward really screws up some things20:51
dobeybah20:52
dobeywhat a bother :(21:08
dobeyinfinity: https://bugs.launchpad.net/ubuntuone-client/+bug/1306225/comments/5 doesn't look good :(21:14
ubottuLaunchpad bug 1306225 in Ubuntu One Client "The user should be informed about the u1 file service shutdown" [Critical,In progress]21:14
infinitydobey: Is that something you can turn around a quick(ish) fix for?  I'm happy to be responsive and process that one quickly if you can.21:15
dobeyinfinity: well, i haven't been able to do so in the ~15 minutes i've been poking at it (trying to get it to exit cleanly anyway). maybe i can if i just try to make it not ever connect, and leave the process running and acting normally like a disconnected client21:16
dobeyinfinity: so i managed to make a patch that makes it not connect, but keep the process alive and working otherwise normally, for 13.10, but 12.04 code is a bit different so i'll have to make a different patch for it21:41
infinitydobey: Alright.  Keep me in the loop.  I'm around most of the evening if you're working late, or tomorrow if not.21:42
infinity(Need to run out soon to visit a post office and remind myself how to send paper through the air, though.  Weird backward-ass lawyer people)21:43
dobeyinfinity: yeah. i need to go now. i'll probably need to finish this up in the morning, so ping me when you hop on-line tomorrow21:44
=== michagogo_ is now known as michagogo
=== ubott2 is now known as ubottu
=== sraue_ is now known as sraue
=== mnepton is now known as mneptok
=== Trevinho_ is now known as Trevinho
=== dkessel_ is now known as dkessel
=== Sarvatt_ is now known as Sarvatt
=== xymox_ is now known as xymox
=== TheMuso` is now known as TheMuso

Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!