[03:49] <patdk-lap> hello zinn!
[03:50] <patdk-lap> !baka
[03:50] <Zinn> Sorry I don't know about baka
[18:53] <James3> i have a frontemd/backend machine, and i ave just built another frontend
[18:53] <James3> im having problems getting them working atm, i have put in the db logins, and it tests ok, but mythfrontend never loads
[18:54] <James3> i was having issues with the fonts, which installing the ms truetype fonts has solved
[18:54] <James3> but mythfrontend still dies with "ICE default IO error handler doing an exit(), pid.... errno=32
[18:58] <James3> ive removed the .ICEauthority file, with no change
[19:01] <James3> ok now "Protocol version mismatch frontend=23056, backend=56"
[19:01] <James3> guess my backend needs some updates :P
[19:02] <James3> !help protocol version mismatch
[19:02] <Zinn> !help protocol version mismatch For a  complete list of my knowledge visit: http://www.baablogic.net/Zinn.cgi  Other available commands: !status, !about, !bug [bug_number].
[19:06] <rhpot1991> James3: guessing you are running mythbuntu updates on one and not another, or different versions of mythbuntu/utuntu?
[19:07] <James3> one is an old mythbuntu (the backend)
[19:07] <James3> the nw frontend is a clean install from an iso downloaded today
[19:07] <James3> ive jst updared the backend, so hopefully its solved when it finishes rebooting
[19:07] <rhpot1991> how old?
[19:08] <James3> in installing the new frontend at a different location, so i was thinking low bandwidth on the vpn xould be causing issues
[19:08] <James3> not sure lol
[19:08] <James3> 71 updates there were so we'll see in a minute :P
[19:08] <rhpot1991> dpkg -l  mythtv-frontend
[19:08] <rhpot1991> run that on each
[19:09] <James3> 0.23.0+fixes24158-0ubuntu2 now n the backed
[19:09] <tgm4883> ugh
[19:10] <tgm4883> !repos | James3
[19:10] <Zinn> James3: The Mythbuntu team provides updates for MythTV and Mythbuntu package using the Mythbuntu Repos http://mythbuntu.org/repos
[19:10] <rhpot1991> tgm4883: pay attention here, I don't recall what vesrions we have for what releases
[19:10] <tgm4883> James3, rhpot1991, he's running lucid release, which was a 0.23 pre-release
[19:11] <tgm4883> he downloaded 10.10, which shipped with 0.23.1
[19:11] <James3> is it safe upgrading the backend to 10.01?
[19:11] <rhpot1991> was waiting till he said his versions to point him at repos
[19:11] <James3> 10.10 even
[19:11] <tgm4883> yea yea 10.10
[19:11] <rhpot1991> James3: just enable our update repos on both and you can update your mythtv packages without upgrading all of ubuntu
[19:11] <rhpot1991> or if you want to upgrade everything
[19:11] <James3> ok
[19:11] <rhpot1991> new release is out in 2 days though
[19:11] <tgm4883> 23056 was the protocol version in 0.23.1
[19:12] <tgm4883> which shipped with 10.10
[19:13] <James3> 0.23, .23.1 or 0.24
[19:13] <James3> what would you recommend for a miniml admin setup lol
[19:14] <rhpot1991> depends what you want
[19:14] <rhpot1991> quicker easier upgrade 0.23.1
[19:14] <rhpot1991> latest and greatest, maybe some reconfiguring, 0.24
[19:15] <rhpot1991> I wouldn't go 0.23 at all when 0.23.1 is there
[19:15] <James3> well its 0.23.1 or 024
[19:16] <James3> the 10.10 frontend doesnt even list 0.23 anymore
[19:16] <James3> 23.1 it is then
[19:17] <James3> i guess it takes a while to load the lists
[19:18] <James3> i have "A package manager is working" on both now, but neither is listing any available updates
[19:22] <James3> ah there we go
[19:22] <James3> 44 updates on the backend
[19:23] <James3> and 20 on the frontend
[19:32] <James3> nice well i think the 0.23.1 has better codecs lol
[19:33] <James3> im quite happily watching live tv on my frontend, accessing the backend via a vpn :P
[19:33] <James3> time to take this to my mates house now
[19:33] <James3> cheers for your help guys
[19:39] <rhpot1991> no problem James3 glad you got it working again
[20:49] <ComradeHaz`> Evening all.
[20:49] <ComradeHaz`> My Myth Box won't play DVD's. When I select 'Play DVD' I get 'Please wait' and then it drops back to theoptical disk menu.
[20:50] <ComradeHaz`> The disk has been automounted in /media/<discName>
[23:28] <James3> ok another question, buti dont know 100% the details yet
[23:29] <James3> with a backend / multi frontend setup, how do i deal with the contents of mythvideo (on the backend)
[23:29] <James3> is there a way to make a frontend play content on a mythbackend,
[23:29] <James3> or do i need to manually setup the frontend, with relevant nfs mappings for example?
[23:29] <James3> i just had my mate ask me how he plays movies
[23:30] <James3> iirc they are setup in a folder mapped to mythvideo, but i have added no settings whatsoever toi the extra frontend
[23:30] <James3> ive just added the db logins, so it can connect to the backend, and manage recoridng/play live tv
[23:31] <James3> time to vnc in now :P
[23:38] <James3> nvm, deal with it in the morning (when i havent just got back from the pub :P)
[23:39] <James3> plus i get a lift back to may car (which is currently in the pub car park) so bonus :D


[00:05] <wxl> hey anyone want to test a new version of konversation i have in a ppa?
[00:05] <wxl> for yakkety
[00:07] <valorie> just post the info so people can find it!
[00:09] <wxl> konversation needs your testing in yakkety: sudo add-apt-repository ppa:wxl/kubuntu && sudo apt update && sudo apt install konversation — gives version 1.6.2-0ubuntu1ppa1 and make sure it fixes https://launchpad.net/bugs/1635911
[00:10] <valorie> thank you wxl
[00:10] <wxl> np
[00:10] <wxl> please ping me or if you've got results!
[00:10] <wxl> s/or//
[00:49] <hippybear> 0/
[01:10] <Guest60127> #ubunu
[01:11] <Guest60127> ok...way outa practice here; anyone home?
[01:20] <DarinMiller> Guest60127: What's up?
[01:22] <Guest60127> trying to get a laserjet 2100 working, real issue since mobo only had an lpt1 header (no actual port)
[01:23] <Guest60127> so I bought 2 add-on cards that are being recognized, but that's it; OS doesn't seem to see the printer beyond the card
[01:23] <DarinMiller> Does the printer showup  when you type lsusb?
[01:24] <Guest60127> not a usb printer, parallel port printer
[01:25] <Guest60127> i even disabled lpt1 in bios, so now cli doesn't recognize it anymore (good)
[01:25] <DarinMiller> Guest60127: hmm, never had to trouble shoot a parallel port printer on linux.
[01:25] <Guest60127> exactly, usually they're pretty straight-forward pnp
[01:26] <DarinMiller> what about: ls /dev/lp*
[01:27] <DarinMiller> or cat /proc/ioports | grep parport
[01:27] <Guest60127> no matter what I type in for the *, I get no such file or directory
[01:28] <DarinMiller> same output on my box, but I don't have a PP printer either....
[01:28] <Guest60127> the cat command you just gave me gave me nada
[01:29] <DarinMiller> I don't think I would be much help as I don't have similar equip. to help investigage...
[01:29] <Guest60127> thanks anyway
[08:19] <jubo2> y0 y0 y0
[08:19] <jubo2> Merry Xmas copyleftists
[08:20] <jubo2> Where do I turn off the "lock screen after N minutes inactivity" ?
[08:20] <jubo2> It somewhere confusing so I'm not finding it in the System Settings
[08:21] <efeciftci> you may search for "screen locking" in system settings, it will point you to desktop behaviour -> screen locking
[08:21] <jubo2> thanks efeciftci!
[08:21] <efeciftci> you're welcome :)
[08:23] <jubo2> The 16.04 desktop graphic was much more aesthetic than the 16.10 one.. where can I easily get the old one ?
[08:29] <acheronuk> jubo2: the wallpaper?
[08:30] <jubo2> acheronuk: yeah
[08:37] <acheronuk> jubo2: there may be somewhere easier, but here for plasma 5.6: https://cgit.kde.org/breeze.git/tree/wallpapers/Next/contents/images?h=Plasma/5.6
[08:37] <acheronuk> and here for 5.5 https://cgit.kde.org/breeze.git/tree/wallpapers/Next/contents/images?h=Plasma/5.5
[08:37] <acheronuk> the little link "plain" on the right give you a download
[08:59] <jubo2> thanks acheronuk
[09:00] <jubo2> my screen resolution matches none of those.. what should I do?
[09:02] <acheronuk> I would pick the 2 closest and try those with the 'scaled' option set. one of those would be what plasma would pick as a closest match if they were installed natively
[09:07] <jubo2> ok.. I try that at some point in time
[09:07] <jubo2> Right now waiting for some files to be copied
[11:34] <dima> Hi enybody
[12:40] <xps> why would i want to have 2 monitors and switch between them while moving the cursor?
[12:40] <xps> how do i disable that
[12:40] <xps> im going crazy here lol
[13:12] <BluesKaj> Hiyas all
[13:20] <user|86614> what are the system requirements for kubuntu?
[13:51] <ste> hello everyone
[14:09] <einszweidrei> Hello. Is there any way to get KDE 4 in Kubuntu 16.04? :(
[14:20] <BluesKaj> einszweidrei, no, but you could install 14.04LTS which is still supported. that will give you KDE4
[14:22] <BluesKaj> einszweidrei, but I'm guessing you already knew that
[14:45] <Guest42991> kubuntu is a w e s o me
[14:45] <Guest42991> switched from mate to kde. Did not like gnome 3 or xfce that much
[14:48] <BluesKaj> Guest42991, yes it is
[17:45] <BluesKaj> !mint
[19:24] <user|73863> Hi. Got Kernel panic after last update on kubuntu 16.10 x64. Any suggestions?
[19:24] <user|73863> Before it happens only for 4.8 kernel. now it finally got 4.4 kernel
[19:27] <acheronuk> user|73863: kernel issues are not really anything to do with kubuntu, or at least we don't look after that. you have a higher probability of getting help on the main ubuntu help channel
[19:29] <user|73863> Well problem is that I have ubuntu 16.04 on my work laptop and it still run 4.4 without any problem. So I belive actually something is wrong with kubuntu version.
[19:31] <acheronuk> kubuntu does not modify the kernel or init system, so it's more likely to be an issue with the hardware on that machine with that kernel version
[19:49] <user|73863> No it's not hardware problem. I'm writing int this chat right now from the mashine, but from 4.1 under opensuse.
[20:02] <acheronuk> user|73863: different distro patch and build the kernel in different ways, so that indicates not very much
[20:03] <acheronuk> remains the case that if you have an issue with that ubuntu kernel version, a better bet for help is the main ubuntu channel
[20:03] <user|73863> ok thanks
[20:04] <acheronuk> user|73863: yeah. not trying to fob you off. just point to where you may have the best chance of help, on what may be a quiet evening on IRC
[20:27] <itisme> put in a new vid card, but haven't been able to boot normally, is it best to reinstall?
[20:28] <BluesKaj> Merry Christmas to and to all a Good Night! :-)
[20:43] <DarinMiller> itisme: AMD or NVidia?
[20:44] <itisme> nvidia
[20:44] <itisme> can't find a way into a repair or recovery mode
[20:45] <DarinMiller> inetpro: hold the shift key when rebooting the PC
[20:46] <DarinMiller> sry inetpro, I meant itisme^
[20:46] <itisme> i"ll try that and see what happens
[20:47] <itisme> may be back in a few
[20:47] <DarinMiller> ok
[21:03] <itisme> no luck, is there some way I can use this installer to unlock the harddrives so I can backup a couple things and then I will reinstall, should be faster than trying to figure out exactly how to get this to repair properly
[21:41] <Trioxin> I need help. I'm stuck at update-initramfs: Generating /boot/initrd.img-4.8.0-32-generic anytime I run apt-upgrade or try to remove a kernel
[21:41] <Trioxin> initially I got these errors: https://hastebin.com/jegeyitoxi.cpp3
[21:42] <Trioxin> https://hastebin.com/idayolugub.pas
[21:42] <itisme> that didn't work either
[21:42] <Trioxin> no idea what to do
[21:45] <itisme> did anyone asnwer me after my system went weird again?  trying to figure out how to get access to backup some files from the install that goes to a black screen so I can just reinstall and go from there
[21:47] <itisme> can't figure out a way of getting rid of or getting the latest nvidia stuff to update the current install that acutally works and doesn't black screen so reinstall seems the best route
[22:03] <user|37318> hi
[22:03] <user|37318> what do i need to instal the os from the usb
[23:42] <Dienonymous> Merry Christmas, your most beautiful memories will reach your heart.


[10:39] <bazhang> the user linux sure is sparse on details
[22:13] <k1l> @comment 72224
[22:14] <k1l> i see a pattern for that shellprovider


[13:56] <zxmpi_> bad news for facebook https://m.independent.ie/world-news/facebook-to-pay-french-publishers-for-news-content-40971407.html
[14:13] <daftykins> yay
[14:13] <zxmpi_> once france gets a penny every other country will pile on
[15:38] <diddledani> so does that mean random blog owners are due money, too?
[15:38] <daftykins> heh
[15:39] <diddledani> hah "Google signed a similar framework deal with the alliance this year, but talks over licensing payments got bogged down, leading French regulators to slap Google with a hefty fine for not negotiating in good faith with publishers."
[16:51] <zxmpi_> are they paying taxes or are they taking the piss? break out the thumb screws
[16:55] <zxmpi_> first post! :-P https://www.newsweek.com/trump-truth-social-hacked-within-hours-announcement-1641137
[16:55] <daftykins> \o/
[16:56] <zxmpi_> god bless those hackers :')
[16:58] <daftykins> ah, a very loose definition of 'hack' by the looks
[16:59] <zxmpi_> well noobs have to start somewhere and sony doesn't want to play anymore :-P
[17:02] <diddledani> shoit on ipwn: https://youtu.be/FJK37_tF8WM
[17:03] <daftykins> diddledani: fun unpicking that wordpress trouble yesterday, ended up having to revert to a backup 'cause my pal's "Visual Composer" plugin going from v34 -> v40 had left it with an integrated Advanced Custom Fields addon that seemed to be barfing o0
[17:04] <diddledani> aah, visual composter
[17:04] <daftykins> :D
[17:05] <daftykins> maybe it's a trap for the free version
[20:37] <diddledani> https://www.youtube.com/watch?v=bnm8tVqMK0s


[07:29] <vila> hi all !
[08:02] <poolie> hi vila!
[08:02] <vila> poolie: hey !
[08:03] <vila> poolie: what can you tell me about our epydoc support ? I tried playing a bit with it yesterday but even with a gross hack for the lazy imports I wasn't really happy with th result (still some ~600 markup errors)
[08:04] <poolie> hm, there's a 'make apidocs' that should work
[08:04] <poolie> i can't recall if it uses epydoc or something else
[08:04] <poolie> last time i ran it, it seemed to work
[08:06] <vila> yeah, api-docs, I used that
[08:07] <vila> I don't think I will go further with it though, better invest into sphinx
[08:08] <vila> but epydoc as involved internally and the trick mwhudson used for the previous versions is now obsolete (my hack reuse it though but applied at a different place)
[08:08] <vila> not sure it's worth publishing anyway
[08:08] <vila> I should file a bug instead :)
[08:50] <vila> mgz: did you receive the mails about the failing daily builds ? https://launchpad.net/~bzr/+archive/daily/+build/2107611/+files/buildlog_ubuntu-natty-i386.bzr_2.3.0%7Ebeta4%2Bbzr5579%7Eppa3877%2B3874%7Enatty1_FAILEDTOBUILD.txt.gz mentions AttributeError: 'InstrumentedTestResult' object has no attribute 'report_error',
[08:50] <mgz> no.
[08:51] <mgz> but that's generally a knock-on error from the tests in bt.test_selftest not being written very robustly
[08:51] <mgz> the real problem will be something else.
[08:51] <vila> mgz: I'm pretty sure this is a genuine bug in the bzr implementation that is triggered only for some weird combo of python/testtools versions
[08:51]  * vila nods
[08:52] <vila> mgz: by the way, do you feel strongly about a more robust isolation for doctests ? I'm unclear about your concerns there
[08:52] <mgz> there are some other failures in that log that I've had before and filed bugs on.
[08:53] <mgz> basically, python2.7 isn't clean yet
[08:53] <vila> python itself or testtools workarounds ? Or bzr on python2.7 itself ?
[09:00] <mgz> bzr on python 2.7
[09:02] <mgz> I see the failures from bug 654731 and bug 614595 in that log, and I think I rememeber breaking those test_selftest tests, but may not have filed anything for them
[09:03] <mgz> getting a 2.7 babune instance again would be good if that's a natty expectation
[09:03] <mgz> (sorry went off to get drink, hence delay)
[09:04] <vila> mgz: I'm monitoring a natty slave for stability (far too often I need to boot from a rescue CD to unlock a broken upgrade)
[09:04] <vila> once it's stable enough, I'll add it to babune
[09:04] <mgz> cool.
[09:05] <vila> and I will propably remove the jaunty one at the same time since it has EOD for a couple of months now
[09:05] <mgz> if the daily builds failures are an issue I can work through the remaining 2.7 failures I get locally.
[09:06] <vila> mgz: it *is* an issue, how important is subjective but getting rid of it would be highly appreciated :)
[09:07] <vila> right, so the bugs you filed are probably why I felt a deja-vu effect
[09:07] <vila> the bad thing is that I thought they were fiXed not fiLed :) Damn Alzheimer
[09:07] <mgz> I squished most of them before you moved your instance back to 2.6
[09:08] <vila> you mean you have fixes for them but no submission ?
[09:09] <mgz> those two linked up there are interestingly opposite ends of why-I-didn't-fix, the doctest issue is too trivial to care about, and the gzip one is scary.
[09:11] <vila> jelmer: hi and FYI ^
[09:12] <mgz> https://bugs.launchpad.net/bzr/+bugs?field.tag=python2.7&field.status%3Alist=CONFIRMED&field.status%3Alist=FIXRELEASED
[09:12] <vila> wow, re-reading 654731... yeah scary... but so huge it makes me wonder if we really it it in production code
[09:13] <mgz> yeah, I think we don't.
[09:13] <vila> a couple of test won't hurt to make it clearer then
[09:13] <mgz> but that makes me not want to touch it at all.
[09:13] <vila> hmm, nice summary
[09:14] <vila> mgz: right, I understand the feeling, but on the other hand it's kind of a FUD issue :)
[09:14] <mgz> launchpad really needs a way of saying "any status" without that daft field.status%3Alist= every-single-status thing.
[09:14] <vila> which is a bit silly
[09:14] <vila> mgz: there are related features in the pipe if I understand correctly what jml said on his blog
[09:16] <vila> can't we close bug #635583 for bzr ?
[09:16] <vila> can't we close bug #625583 for bzr ?
[09:16] <vila> pfff
[09:16] <mgz> on his blog? or some other one? I don't recall seeing it on his.
[09:16] <vila> let me check
[09:16] <mgz> vila: if you've upgraded to testtools 0.9.7 or later, yes.
[09:17] <mgz> but not having a 2.7 slave means I've not actually noticed if it's fixed or not yet.
[09:17] <vila> ok
[09:17] <vila> I should start filing bugs for babune (make slaves configuration easier to consult)
[09:18] <vila> and do another audit to ensure I can re-start publishing the code
[09:20] <vila> but may be it's a stupied idea to try auditing my own  setup...
[09:21] <mgz> personal glue code is always a bit odd.
[09:22] <mgz> my testing stuff is all carefully licenced and available over http, but I've never bothered telling anyone about it.
[09:22] <vila> My main problem is with security issues, I tried to ensure that user and passwords weren't versioned in the babune project but hudson doesn't make it clear whether I succeeded or not
[09:22] <vila> the slaves use some ssh keys, but those are clearly versioned somewhere else (and properly gpg-encoded before that anyway)
[09:24] <vila> so that leaves only the babune accounts potentially (this is where I have doubts) exposed, or so I wish :)
[09:24] <vila> but well, this is kind of relying on security through obscurity so I may just pusblish and monitor who is connecting when
[09:25] <vila> I've made the hudson instance run under a specific account anyway to even getting access there won't buy an attacker anything interesting...
[09:25] <vila> s/to even/so even/
[09:27] <vila> shudder, natty broken again after an update :-/
[09:28] <vila> ha, may be not, one more reboot needed
[09:28] <mgz> heh.
[09:29] <vila> could be vbox related...
[09:30] <vila> the main issue these days is that 3D is not supported so Unity is out of the game, I shouldn't really care not keep insisting about using GUI on the slaves, but, well, it has been easier so far
[09:30] <vila> right, runs ok after reboot and guest additions update
[09:44] <mgz> ah yeah, I remember. the failing tests you asked about earlier were ones I broke, it's basically covered bug bug 637674
[09:45] <mgz> was being clever making the thread leak stuff work with test case instances not derived from the bzrlib TestCase, but that breaks things
[09:46] <mgz> and those three bugs look like they cover all the failures in that log.
[09:46] <vila> wow, I would need to dig to understand here, I can't do that right now :-/
[09:47] <vila> But I could probably review if needed
[09:49] <vila> mgz: http://code.mumak.net/2010/11/and-then-what.html is what I had in mind
[09:49] <vila> there was a more precise one about the bug queries but may be it was from some lp dev, not sure
[09:51] <mgz> speaking of reviewing and understanding, I need to respond on the lp:~vila/bzr/321320-isolate-doc-tests mp as I feel we crossed wires a little.
[09:51] <vila> mgz: yeah, that was my question above
[09:51] <mgz> thanks for the link, I did see that post.
[09:52] <vila> I can't find this other post I'm mentioning but from memory there will be ways to define queries, save and share them
[09:53] <mgz> launchpad is generally pretty good at urls that don't suck, bug search interface in general is a bit of a low point though.
[09:53] <vila> some will be pre-defined and easily accessed from bug pages but you'll get full control for subscription for example (the two subjects are related so maybe I'm mixing things up)
[09:54] <mgz> I'm often doing a four or five page fetch thing trying to just look for some existing bug that may or may not already be fixed on trunk
[09:55] <vila> yeah, that's very bad
[09:56] <vila> searching is sub-optimal, you often give me more precise answers than what I get when searching myself a bit outside of the ones I know
[09:59] <vila> pfew, mail backlog was heavier than usual, back to the drawing board now
[10:17] <jelmer> vila: sorry, missed that earlier
[10:17] <jelmer> vila: g'morning!
[10:17] <vila> jelmer: np, g'morning :D
[11:33] <vila> jelmer: I'm experimenting weird mail issues (some of my mail are lost), did you get the one I wrote in the 'Ready in bzr/proposed: testtools 0.9.8, fixtures 0.3.5' thread ? (To which you just replied, the thread not my email)
[11:39] <jelmer> vila: checking
[11:44] <jelmer> vila: nope, I don't see it
[11:44] <vila> :-(
[11:50] <vila> darn, who knows since when I've been talking do /dev/null without even realizing...
[11:54] <vila> OMG, found the root cause :(
[11:55] <jelmer> vila: Talking to /dev/null is better than being ignored by the rest of the world ;-)
[11:56] <vila> hehe, I was vaguely suspecting the later (but not strongly enough to investigate ;) but I wasn't talking to /dev/null either, I have a bunch of mail reports in a mailbox now so I know which ones were not sent
[11:57] <vila> oh my... yet another one where I was surprised to see no answers..
[11:58] <vila> argh ! The 2.2.2 announce did not make it ! Nobody reacted :(
[12:00] <vila> bah, no wonder gary never replied to my emails...
[12:01] <vila> the fact that I do a lot through lp didn't help...
[12:17] <maxb> Are there any guidelines for landing approved reviews to non-PQM-managed bzr projects owned by ~bzr?
[12:18]  * maxb has an approved MP for bzr-fastimport... do I just merge and push, with an [r=person] commit message?
[12:19] <jelmer> maxb: The only guidelines are to use a merge to land the changes, and properly describe what changes you're landing.
[12:19] <jelmer> maxb: We don't have a tradition of mentioning reviewers, but it does seem like a reasonable thing to do.
[12:20] <maxb> Hmm, well, it's just a single trivial revision, so if I don't mention the reviewer, I might as well just push :-)
[12:48]  * maxb sobs a bit at discovering how iffy bzr-fastimport's marks handling is
[12:53] <jelmer> maxb: you mean the fact that it hardcodes marks where any kind of revision identifier is possible?
[13:05]  * jelmer gets bombarded with mail from vila
[13:06] <vila> jelmer: sorry about that, there were 74 mails that didn't went through...
[13:06] <jelmer> np :-)
[13:34] <knighthawk> I'm a bit confused about how to use bazaar as a central repos. I think its working trees vs non working trees that is tripping me up or perhaps commit vs push
[13:43] <vila> knighthawk: or even branch vs checkout :)
[13:43] <vila> knighthawk: so, start by reading http://wiki.bazaar.canonical.com/MatthewFuller/SpotDocs/PiecesInBrief so we give the same meaning to tree, branch and repo
[13:45] <knighthawk> vila - thanks. I may have been trying to make bzr fit into my svn knowledge and so far its not working ;-)
[13:45] <vila> knighthawk: no problem, I'll help if I can
[13:46] <vila> once we are on the same page for the words to use, things will be eaiser
[13:46] <vila> easier than not making tyops at least...
[13:52] <knighthawk> thanks vila - okay reading the into now.
[13:58]  * jelmer lunches
[16:03] <dlee> Is it a bug, or known, that tags get lost on either bzr join or bzr upgrade from 0.92 to 2a?  (One or the other, not both; I assume join.)
[16:04] <vila> dlee: this rings no bell, worth filing as a bug
[16:05] <vila> dlee: I would tend to suspect join too
[16:05] <dlee> I'll need to find time to create a script to reproduce this... I have three bugs I need to do that for by now.  The others have to do with errors that block bzr join.
[16:06] <vila> ouch
[16:06] <dlee> I suspect bzr upgrade might create a root ID that is the same across multiple upgraded projects... wild guess, but what I see is that trying to join more than one tree into a common one fails on second and any subsequent trees.
[16:06] <vila> dlee: you know about the test-script command right ?
[16:07] <dlee> My apologies for the sparse info; these keep hitting me amid my job when I can't stop long enough to do a good repro. :P
[16:07] <dlee> no
[16:07] <vila> dlee: hmm, new in 2.3bn I think
[16:08] <dlee> Using 2.2.0 release here.
[16:08] <dlee> I upgrade sort of infrequently because I am responsible for upgrades for my whole office, and I like keeping versions in sync when possible.
[16:09] <vila> sure, which OS ?
[16:09] <dlee> Mostly Windows.  Also tried Cygwin port for the join blocker issues today.
[16:09] <dlee> Oh the Cygwin one is 2.1.2; I use that rarely and am the only one who uses it at all here.
[16:10] <vila> dlee: hmm, I have no idea about who is maintaining the cygwin port
[16:10] <dlee> vila: Holidays approach, and I try to tackle off-the-road projects during that time, when not playing card games or eating turkey etc. :)  So maybe I'll have a better chance at this soon.
[16:10] <vila> grr, and we lag a bit for the windows installers :-/
[16:12] <vila> dlee: so anyway, once you get a change to upgrade to 2.3, there is a test-script command that is targeted at bug reports, making it easier to write reproducing recipes
[16:13] <dlee> I'm good at shell scripts but I'll keep that in mind, gotta go now, someone is trying to work with me here. :)  Thanks for the info though.
[16:46] <fullermd> Trivial test does show join dropping tags on the floor   :(
[16:46] <vila> the source ones not the target ones I hope ?
[16:47] <fullermd> Well, source.  I didn't try target, but that would be REALLY egregious.  And probably take intention.
[16:47] <vila> :)
[16:47] <vila> by the way, I landed your smooth upgrades proposal, there is more work needed there so file bugs if you encounter problems or rough edges
[16:48] <fullermd> I did see that a couple days ago; thanks.  Now post-2.3 maybe I can move our last projects off 1.9 formats   :)
[16:49] <vila> ha ok, so you won't start using it before 2.3 is out right ?
[16:50] <fullermd> Well, I run .dev on my workstation.  But just releases everywhere else.
[16:50] <vila> ok, anyway if you do some tests, I'll be all ears
[16:51] <fullermd> Yeah, I'll probably fiddle with it.  But probably not in any situations I didn't before, so I doubt I'd turn up anything new.
[16:51] <fullermd> I'll toss together a repro script and bug for that join thing in a bit.
[16:53] <vila> cool
[16:54] <fullermd> Well, not as cool as not having to 'cuz there's no bug in the first place   :p
[16:57] <vila> I know :-/
[16:58] <vila> this one is probably there since day one
[18:02] <tgall_foo> on natty, doing a fresh bzr branch, has anyone seen an error of this form ? bzr: ERROR: d3b70ec01f6fbb6c152129e151757a28.rix is not an index of type <class 'bzrlib.btree_index.BTreeGraphIndex'>.
[18:03] <lifeless> tgall_foo: WAG - zero length file?
[18:04] <jelmer> tgall_foo: are you using XFS?
[18:04] <tgall_foo> jelmer: nope ...   am on an arm box tho
[18:04] <tgall_foo> jelmer: ext3 FWIW
[18:06] <tgall_foo> lifeless, I don't believe there are any zero length files involved ...     the repo in question is lp:~tom-gall/linaro/live-helper.config.natty.linaro-graphical-engineering
[18:07] <tgall_foo> branches fine on my maverick box
[18:07] <lifeless> tgall_foo: you're getting that over the network ?
[18:07] <tgall_foo> yes
[18:09] <lifeless> http://bazaar.launchpad.net/~tom-gall/linaro/live-helper.config.natty.linaro-graphical-engineering/.bzr/repository/indices/
[18:09] <lifeless> no inde d3b..
[18:09] <lifeless> no *index* d3b
[18:09] <lifeless> tgall_foo: whats the exact command giving the error ?
[18:10] <lifeless> bzr dump-btree http://bazaar.launchpad.net/~tom-gall/linaro/live-helper.config.natty.linaro-graphical-engineering/.bzr/repository/pack-names
[18:11] <tgall_foo> lifeless,   bzr branch lp:~tom-gall/linaro/live-helper.config.natty.linaro-graphical-engineering
[18:11] <lifeless> shows no expected index d3b...
[18:11] <lifeless> tgall_foo: ok, and what directory are you doing that in?
[18:11] <tgall_foo> it's just a dir in my home ...  ~/bzr/live-helper.configs
[18:11] <lifeless> ok
[18:12] <lifeless> can you run 'bzr info' in that dir
[18:12] <tgall_foo> sure
[18:12] <lifeless> paste the location: section
[18:13] <tgall_foo>   shared repository: .
[18:14] <lifeless> ok
[18:14] <lifeless> so its the local repository
[18:14] <lifeless> ls -lrt .bzr/repository/indices
[18:15] <tgall_foo> it's a fairly long list so I'll avoid flooding the channel ...
[18:15] <tgall_foo> http://pastebin.ubuntu.com/546665/
[18:16] <lifeless> -rw-r--r-- 1 tgall tgall  222 Nov 24 15:57 d3b70ec01f6fbb6c152129e151757a28.rix
[18:16] <lifeless> is the culprit, but indeed, its not zero-length
[18:17] <lifeless> bzr dump-btree .bzr/repository/indices/d3b70ec01f6fbb6c152129e151757a28.rix
[18:17] <tgall_foo> bzr: ERROR: d3b70ec01f6fbb6c152129e151757a28.rix is not an index of type <class 'bzrlib.btree_index.BTreeGraphIndex'>.
[18:18] <lifeless> head .bzr/repository/indices/d3b70ec01f6fbb6c152129e151757a28.rix
[18:18] <tgall_foo>     122664 |             284
[18:18] <tgall_foo> procmail                          | procmail                        | quilt (Build-Depend)                         | Ubuntu Developers<EMAIL_ADDRESS>                |t
[18:19] <lifeless> thats very much not what a bzr index looks like :)
[18:19] <tgall_foo> interesting
[18:19] <lifeless> something has gone very wrong on your file system
[18:19] <tgall_foo> that is a very scary prospect... thanks lifeless
[18:19] <lifeless> possibly thats prior content and the file wasn't flushed to disk before a reboot/kernel crash
[18:20] <lifeless> possibly thats new content scribbled over the original file (note that the file dates from nov 24th, so if you've been branching in this repo in the ~month, and it was working... then it was originally written correctly)
[18:20] <lifeless> have a look at d3b70ec01f6fbb6c152129e151757a28.iix while you are there
[18:21] <lifeless> its the same length
[18:21] <tgall_foo> well at this point everything that was here has been pushed up to lp ... so there really isn't any loss blowing it away
[18:22] <tgall_foo> very similar for the iix file :  |          545026 |            1200
[18:22] <tgall_foo> python-central                    | python-central                  | debconf (Build-Depend)                       | Ubuntu Core Developers<EMAIL_ADDRESS>[18:22] <lifeless> I humbly suggest an fsck
[18:22] <tgall_foo> I think you're right on that
[18:24] <maxb> jelmer: Do you happen to know if the list of projects using python-fastimport at https://launchpad.net/python-fastimport is reasonably complete? I wish to argue that some bits of python-fastimport are prematurely factored out implementation details of bzr-fastimport - checking whether they are in fact used elsewhere would be useful
[18:25] <jelmer> maxb: Dulwich and bzr-fastimport are the main other users that I'm aware of at the moment.
[18:26] <maxb> right
[18:39] <jelmer> maxb: Which bits specifically are you referring to?
[18:40] <mgedmin> just discovered an actual use case for bzr gcommit!
[18:40] <jelmer> hi Marius
[18:40] <jelmer> mgedmin: per-file commits?
[18:40] <mgedmin> yep
[18:40] <mgedmin> hi, jelmer
[18:41] <mgedmin> shame it stops me cold with "working tree out of date, please run bzr update"
[18:41] <mgedmin> and then has no 'reload' button, so I have to (1) write down the files names I've checked on a piece of paper, (2) close gcommit window, (3) restart gcommit
[18:41] <mgedmin> okay, I'm a bit exaggerating here
[18:41] <mgedmin> instead of (1) I did a commit in a different terminal window
[18:42] <mgedmin> gcommit helped me keep track of which files I wanted to commit
[18:42] <mgedmin> so thanks for that
[18:42]  * mgedmin guesses it is probably not appropriate to go and ask for a per-hunk commit selection pretty please with sugar on top?
[18:49] <jelmer> mgedmin: it would be appropriate and I agree it'd be nice to do, but it's also nontrivial
[18:49] <jelmer> so not very likely at this point
[18:50]  * mgedmin would take that on as a challenge, if /me had more time ...
[19:09] <lifeless> jelmer: why nontrivial?
[19:09] <lifeless> jelmer: we have merge -i after all ...
[19:25] <maxb> jelmer: reftracker and idmapfile - I've filed a bug
[20:04] <sqwishy> So, when a pull happens, it transfers the entire history, right?
[20:05] <sqwishy> Every time you pull?
[20:07] <lifeless> only the bits you don't have
[20:15] <jelmer> lifeless: hunk selection in diffs, using a GTK widget is nontrivial imho
[20:15] <jelmer> lifeless: I'd love to be proven wrong :-)
[20:22] <sqwishy> So how does a pull differ from and update? Assuming you already have a pull or a checkout a revision or two old.
[20:42] <fullermd> Pull is for updating one branch to match another.  Update is for updating a working tree to match its branch.
[21:04] <maxb> the lines do blur a bit with checkouts
[23:48] <spiv> Morning folks.


[08:59] <czajkowski> tdr112: https://twitter.com/#!/RonanKirby/status/115710418034503680
[09:47] <tdr112> czajkowski: a bit too high of a job for me , but thanks for the link
[09:50] <czajkowski> tdr112: no worries
[09:50] <ebel> suppose email costs so much now-a-days....
[09:50] <ebel> :P
[09:51] <ebel> though suppose there's a lot of M-words in that posting. :)
[12:44] <dumb1224> hi
[12:45] <ebel> hello
[12:45] <dumb1224> Hi I have a question of aptitude
[12:46] <ebel> Ask away
[12:46] <dumb1224> it asks me to remove packages not need after I removed a software called rabbitvcs
[12:46] <ebel> !ask
[12:47] <dumb1224> thnks I'm fairly new to irc
[12:47] <ebel> Nothing wrong with removing old software packages if they aren't needed anymore
[12:48] <dumb1224> aptitude asked me to also remove subversion{u} python{u} etc about 9 packages which I am using
[12:50] <ebel> hmmm
[12:51] <dumb1224> same happened if I want to remove freenx which is a remote desktop control server
[12:51] <ebel> If you go "sudo aptitude install subversion" then it should remember that you want that installed
[12:51] <dumb1224> it asked me to also remove openssh-server since its not need,,tats not right?
[12:51] <ebel> (aptitude keeps track of things that are installed when you tell it to install the package and when it's installed as a dependency from another package)
[12:52] <ebel> python should be installed by default and shouldn't be removed.
[12:52] <ebel> How did you install openssh-server?
[12:52] <dumb1224> ok...what does the {u} flag mean?
[12:52] <ebel> can't remember what {u} means, miiiiight be "needs upgrade"
[12:53] <ebel> try do an upgrade & dist-upgrade. just to be safe
[12:53] <dumb1224> it was installed before freenx, but freenx requires openssh
[12:54] <dumb1224> you mean upgrade the system to the next release?
[12:54] <ebel> no, not to the next release, just upgrade all the software
[12:54] <dumb1224> it's quite old, it's an 8.04 lts
[12:54] <dumb1224> oh
[12:55] <ebel> ah
[12:55] <ebel> maybe that's what the {u} means.
[12:55] <ebel> (things need upgrading?)
[12:55] <ebel> you can stay on 8.04
[12:55] <dumb1224> hmmmm right. how do I upgrade a package using aptitude?
[12:56] <ebel> just a normal "sudo aptitude update && sudo aptitude upgrade"
[12:56] <ebel> that'll upgrade all the software, but keep you on 8.04
[12:56] <dumb1224> right I'll give it a try
[13:00]  * ebel goes out for lunch
[13:00] <ebel> ttyl
[13:00] <dumb1224> thanks laters!


[01:37] <dilys> Merge to<EMAIL_ADDRESS>Fixed sampledata and removed an obsolete assert (patch-1025)
[02:34] <dilys> Merge to<EMAIL_ADDRESS>fix PO template creation (patch-1026)
[03:48] <dilys> Merge to<EMAIL_ADDRESS>many templates links fixes (patch-1027)
[10:48] <dilys> Merge to<EMAIL_ADDRESS>Database patches and Z3 auth workaround (patch-1028)
[11:10] <daf> SteveA: ping
[11:34] <dilys> Merge to<EMAIL_ADDRESS>Missed Interface Attributes (patch-1029)
[11:53] <carlos> stub: wait, daf just requested the merge (he forgot to do that)
[12:06] <stub> carlos: I just did the rollout. Does daf still have PQM commits going through?
[12:12] <dilys> Merge to<EMAIL_ADDRESS>little fixes (patch-1030)
[02:23] <dilys> Merge to<EMAIL_ADDRESS>bazaar renaming and initial soyuz refactoring for distribution, distrorelease (patch-1031)
[04:04] <kiko> cprov, yo
[06:26] <sabdf1> halllaauu
[06:27] <sabdf1> l
[06:27] <sabdf1> l
[06:27] <sabdf1> 1
[06:27] <sabdf1> odd
[08:05] <carlos> sabdf1: is working the wireless from the rooms?
[08:06] <elmo> carlos: is now, yep
[08:06] <sabdf1> carlos: some rooms :-)
[08:06] <carlos> elmo: ok, thanks
[08:07] <sabdf1> carlos: could you order me one too, please?
[08:10] <carlos> sabdf1: which room?
[08:10] <sabdf1> 128
[08:10] <carlos> sabdf1: and what do you want?
[08:11] <carlos> wait, I will call you when I order it
[08:11] <carlos> later
[08:11] <sabdf1> cool, thanks!
[09:03] <carlos> food!!!!!
[09:07] <elmo> dude, what room are you in???
[09:09] <carlos> 133
[10:05] <carlos> Is interesting to see that zope3 is in hoary :-)
[10:32] <sabdf1> hmm... so when we release hoary, we can start using zope3 instead of crack-of-the-day :-)
[10:34] <carlos> sabdf1: at the moment it's in universe
[10:35] <carlos> and it's not available for ppc
[10:35] <carlos> I had to compile it myself
[10:36] <carlos> grrr
[10:36] <carlos> and the dependencies are wrong
[10:36] <carlos> :-(
[10:37] <sabdf1> so, a small project then :-)
[10:38] <carlos> I suppose that this explains all:
[10:38] <carlos> EXPERIMENTAL PACKAGE. NO UPGRADE PATH FROM EARLIER VERSIONS OR
[10:38] <carlos>  TO UPCOMING VERSIONS PROVIDED UNTIL THE FINAL 3.0 RELEASE.
[10:39] <carlos> but it's a final release 3.0.0-1
[11:01] <carlos> sabdf1: ping
[11:02] <sabdf1> carlos: pong
[11:03] <carlos> sabdf1: what about adding a javascript spell checking to rosetta using something like google suggestions?
[11:04] <carlos> sabdf1: http://www.google.com/webhp?complete=1&hl=en
[11:04] <sabdf1> carlos: do you think it can be done in javascript?
[11:05] <sabdf1> i would think perhaps easier to do it on the server, and display it in the browser window, asking the user to confirm it?
[11:05] <carlos> sabdf1: it's just the idea we had to get the product list with javascript + xmlrpc
[11:05] <sabdf1> right
[11:05] <sabdf1> so the spellcheck happens on the server
[11:05] <carlos> yeah
[11:07] <carlos> I have seen several spellcheckers in javascript already but using cgi or .php files
[11:08] <sabdf1> cool
[11:08] <sabdf1> let's see if we can do that
[11:09] <carlos> ok
[11:52] <lifeless> hey guys.
[11:53] <lifeless> I have a request for  you for bazaar
[11:53] <lifeless> I have a new merge algorithm, which Works For Me (tm).
[11:54] <lifeless> on launchpad it can take up to 30 seconds to calculate where to merge from, but it is able to handle loops, tags from tags, and more, happily.
[11:54] <lifeless> (or at least, it should :)).
[11:54] <lifeless> How do you feel about that being merged into bazaar as is, before optimisation.
[11:55] <sabdf1> lifeless: correctness is more important than performance for us
[11:55] <carlos> lifeless: bazaar is really slow here already and it's a problem with the harddisk I/O
[11:55] <sabdf1> if you think it's stable, merge it in
[11:56] <carlos> so if that don't make it slower
[11:56] <carlos> it's ok for me
[11:56] <lifeless> cool. ok, I'll finish the tests for it that I'd want as minimal coverage, then merge it in. It should make workflow a lot easier for collaborating sub-teams.
[11:57] <sabdf1> lifeless: i think we want more than minimal coverage
[11:57] <lifeless> carlos: yah, I've got optimisation as a massive todo.
[11:57] <carlos> lifeless: that will be really good
[11:57] <lifeless> sabdf1: FSVO minimal. I am very pro testing, as you know.
[11:57] <sabdf1> it's not reasonable to ask the rf team to use crack-of-the-minute bazaar unless you have really, really good test coverage
[11:58] <lifeless> sabdf1: ack.
[11:58] <sabdf1> 30 secs to calculate the merge point, then how long to do the merge?
[11:59] <lifeless> 30 seconds to generate the merge point, then a standard 3-way merge, which you've said is faster than two way anyway.
[11:59] <lifeless> you can turn off the new algorithm with '--star-merge' to the merge command.
[11:59] <lifeless> I won't be merging this tonight no matter what.
[12:00] <lifeless> (just in case you are worrying :))