[00:20] <Aison0> hello, is radvd somehow borked in ubuntu eoan? systemctl start radvd always says: Failed to start Router advertisement daemon for IPv6.
[00:21] <Aison0> but when I start radvd by "hand", it works (radvd -C /etc/radvd.conf -n)
[00:25] <Aison0> radvd.service: Failed to set up mount namespacing: Stale file handle
[21:36] <mybalzitch> so X11 forwarding in 19.10, does it still work for anyone else?
[21:37] <mybalzitch> AMD64


[12:04] <crimsun> (I blame gnome-menus or something ;-)
[12:07] <raphink> pfff
[12:08] <slomo> yes, let's blame seb ;)
[12:09] <raphink> lol
[12:33] <raphink> hi ogra_ibook
[06:25] <Yagisan> G'day All
[06:26] <Yagisan> If I want to redefine LD_LIBRARY_PATH so an app looks for it's libraries in a different path, it should be sufficient to put
[06:26] <Yagisan> LD_LIBRARY_PATH = /lib32 /usr/lib32 /usr/X11R6/lib32 /lib /usr/lib in debian/rules right ?
[06:28] <Lathiat> isnt it LD_LIBRARY_PATH=/lib32:/usr/lib32:/usr/X11R6/lib32....
[06:30] <Yagisan> thanks Lathiat: I'm over-tired today and doing typos in my rules files
[06:37] <Yagisan> Lathiat: that didn't seem to work. I got a FTBFS again because it tried to use the library in /usr/lib rather then /usr/lib32 :(
[06:38] <crimsun> ./configure needs it in LDFLAGS
[06:41] <Yagisan> crimsun: thank you. I need a few working test cases for my ia32-libs-universe package
[06:43] <crimsun> my guess is anything game-related
[06:45] <Lathiat> so what exactly is in ia32-libs?
[06:54] <Yagisan> sorry guys - had to leave. My daughter  jumped off the dining table trying to fly and I needed to administer first aid :(
[06:55] <crimsun> sounds like me some 20 years ago.
[06:55] <Yagisan> re: ia32-linbs-universe: currently sdl packages to get some games working, and I plan to put in whatever is needed to get wine going
[06:56] <Yagisan> crimsun, so you'd be about 22 then ?
[06:56] <Yagisan> my initial test cases are deng (not yet in ubuntu) zsnes and wine. Feel free to suggest others
[06:57] <crimsun> Yagisan: +4
[06:58] <crimsun> speaking of wine, are we going to merge it from Sid?
[07:00] <Yagisan> crimsun: I don't know, the winehq guys have popped out either 0.9.3 or 0.9.4 now in their repo
[07:00] <Yagisan> crimsun: IIRC ubuntu uses their package
[07:00] <crimsun> those are supposed to be less stable than 0.9
[07:01] <crimsun> according to Scott, who was fairly active in getting Hoary's wine up to speed
[07:01] <Yagisan> crimsun: to be honest, I have had regressions in every wine release after hoary shipped
[07:02] <crimsun> hmm.
[07:02] <Yagisan> crimsun: I mainly use it for gpl apps that are Win only, or 1 or 2 games I have form '95
[07:02] <Yagisan> crimsun: but some people need it, so I'd like to see it running on amd64
[07:03] <Yagisan> crimsun: I figured I could get some package magic working until real multiarch is done
[07:04] <crimsun> you probably want to coordinate with Tollef and Jeff on that, then
[07:04] <crimsun> I hear there are going to be some nasties in Dapper+1
[07:06] <Yagisan> oh ? I figured it would be a simple case of adding some extra 32bit libs and some patches to rules and control to get this band-aid working
[07:07] <crimsun> the band-aid will suffice for Dapper, probably, but it won't work for Dapper+1
[07:07] <crimsun> they have a much better idea of the transition than I do, though
[07:08] <Yagisan> crimsun: ok. I hope to have it ready for dapper. I'd rather not keep it around after dapper, as I'd prefer true multi-arch
[07:10] <Yagisan> crimsun: I already had siretart volunteer to test packages when ready, are you also interested ?
[07:11] <crimsun> Yagisan: I don't have an amd64 desktop, only a pbuilder some 3000 km away
[07:14] <Yagisan> crimsun: santa didn't get you one ? that's ok. santa didn't get me my ppc system for christmas either
[07:16] <crimsun> Yagisan: no, Santa brought me uninterrupted sleep instead.
[07:17] <Yagisan> crimsun: lucky you. Santa brought me a large hole in my wallet, and a severe lack of sleep since then
[07:17] <crimsun> Yagisan: :)
[07:19] <Yagisan> crimsun: It's called the "joy" of 2 under 2
[07:20] <smallfoot> hi
[07:20] <smallfoot> what is this channel about?
[07:20] <crimsun> read the topic.
[07:20] <smallfoot> and why is there is so many damn ubuntu channels?
[07:20] <smallfoot> and can you please tell that guy crimsun not unban me
[07:20] <jsgotangco> because we're so damn many?
[07:21] <smallfoot> lol
[07:21] <smallfoot> oh
[07:21] <smallfoot> ok
[07:21] <smallfoot> i guess its good idea have many chans then
[07:21] <jsgotangco> crimsun, please unban smallfoot please... :D
[07:21] <smallfoot> yeh, pwetty please
[07:21] <crimsun> sorry, can't unban him here ;)
[07:21] <smallfoot> is ubuntu the most used linux of all distros?
[07:23] <jsgotangco> err why?
[07:23] <Yagisan> wOOt! I found yet another way to make deng FTBFS
[07:23] <smallfoot> because you said to him plz unban me
[07:23] <smallfoot> deng FTBFS?
[07:23] <jsgotangco> smallfoot, you really believed that?  End of WHOIS
[07:38] <smallfoot> lololol
[07:38] <crimsun> smallfoot: rest assured that I won't (un)ban you from all channels
[07:38] <smallfoot> hmm
[07:38] <smallfoot> ok
[07:38] <smallfoot> =/
[07:39] <smallfoot> you guys should be lucky i dont have ops!!
[07:39] <smallfoot> i would ban everybody!!
[07:39] <Hobbsee> hehe @ crimsun
[07:39] <jsgotangco> hehe
[07:39] <smallfoot> Hobbsee, you have the cute
[07:39] <jsgotangco> come on let's play warcraft
[07:40] <smallfoot> yeh
[07:40] <smallfoot> tell me your guys name in warcraft
[07:40] <smallfoot> then if you dont give me all your item, my guild will hunt you!!
[07:40] <jsgotangco> yeah right
[07:41] <smallfoot> ok
[07:41] <smallfoot> mom get angry
[07:41] <lifeless> smallfoot: please take this to #warcrat or something, its off topic here
[07:41] <smallfoot> i must close computer
[07:41] <smallfoot> bye!!
[07:42] <Yagisan> this is so funny, and yet so sad
[07:42] <Yagisan> I'd say about 10 yrs
[07:42] <jsgotangco> when i started on linux, i had a lot of questions but i didnt annoy people (im pretty sure of it)
[07:43] <Yagisan> I still have lots of questions, but the best way to learn is to do it
[07:43] <Yagisan> speaking of which
[07:44] <lifeless> Yagisan: I think 10 could only be physical, not mental age.
[07:45] <Yagisan> lifeless: possibly. btw if you are who I think you are, did you get your laptop fixed from udu ?
[07:45] <lifeless> erm, @ udu - my laptop was working, but the hinge was getting worse and worse
[07:46] <lifeless> I cannot open the hinge any more at all as of about 5 months back, I bought a dell x1, still have not managed to get the manufacturer to respond to get the hoverbook fixed.
[07:46] <Yagisan> lifeless: yep - thats the one.
[07:47] <Yagisan> lifeless: I met you, IIRC your in Sydney right
[07:47] <lifeless> yes
[07:47] <lifeless> up epping way
[07:47] <jsgotangco> oh you were there?
[07:48] <Yagisan> jsgotangco: yep. It was nice - I went for proactive security
[07:48] <jsgotangco> you were at the UDU keysigning?
[07:48] <Yagisan> jsgotangco: yes - before terrible disaster struck
[07:48] <Yagisan> brb
[07:48] <jsgotangco> wow so we got to meet but didnt chat at all lol
[07:49] <Yagisan> jsgotangco: that sucks :(
[07:50] <jsgotangco> what's your full name i might have signed it
[07:51] <jsgotangco> right
[07:51] <Yagisan> lifeless: I'm down in lidcombe. perhaps one day when you're not busy, I could meet up with you for a key signing ?
[07:52] <lifeless> sure
[07:52] <lifeless> I work from home, so ;)
[07:55] <Yagisan> lifeless: heh - so do I
[07:57] <Yagisan> jsgotangco: It's funny - I've probably met most people here, yet I can't remember what they look like
[07:57] <Hobbsee> more people from sydney - oh good!
[07:58] <Yagisan> Hobbsee: so where are you ?
[07:58] <Hobbsee> around near dural
[07:59] <Yagisan> that's not too far away, a pain to get to via public transport though
[08:00] <Hobbsee> yeah, i can drive, fortunately
[08:00] <Hobbsee> actually, cherrybrook is a closer location
[08:00] <Hobbsee> hehe nice, at epping?
[08:00] <Yagisan> nope, that's lifeless. I'm at licombe
[08:01] <Hobbsee> ah, right, yep
[08:01] <Yagisan> it could be worse, eg auburn, bankstown, lakemba etc
[08:02] <Yagisan> wOOt "configure: error: C compiler cannot create executables"
[08:02] <Hobbsee> hehe true
[08:04] <Yagisan> Hobbsee: so, what are you working on now ?
[08:04] <Hobbsee> right now?  i'm a little dazed to work on this second, but i was doing a version of ksudoku earlier...
[08:05] <Yagisan> I do my best work when I'm out of it ;)
[08:05] <Hobbsee> hehe true
[08:05] <Hobbsee> i just got home from work
[08:07] <Yagisan> Hobbsee: are you are motu yet ?
[08:08] <Hobbsee> no
[08:08] <Hobbsee> i usually end up sending stuff through Riddell-awa
[08:12] <Yagisan> Hobbsee: I just send my stuff to revu, and await the "we can't have this in ubuntu, because upstream is needs to be beaten with a cluebat" comments
[08:12] <Hobbsee> hehe great
[08:12] <jsgotangco> has anyone verified http://doc.ubuntu.com/ubuntu/packagingguide/C/ch02.html if it works
[08:14] <Yagisan> jsgotangco: I just read it. there are typos and it won't work as is
[08:15] <Yagisan> jsgotangco: most of it is fine
[08:15] <Yagisan> jsgotangco: perhaps a cut & paste error from the wiki ?
[08:15] <jsgotangco> Yagisan, where is the orignial wiki entry?
[08:15] <jsgotangco> its from docbook source
[08:16] <Yagisan> jsgotangco: https://wiki.ubuntu.com/DebootstrapChroot
[08:16] <jsgotangco> ok i'll check it out
[08:17] <Yagisan> jsgotangco: the wiki one works fine
[08:17] <jsgotangco> https://wiki.ubuntu.com/PbuilderHowto doesn't apply?
[08:18] <Yagisan> jsgotangco: it does.
[08:18] <Yagisan> jsgotangco: both are useful. 1st one esp for amd64 users
[08:18] <jsgotangco> ok so i do DebootstrapChroot first right?
[08:19] <Yagisan> jsgotangco: yes
[08:19] <Yagisan> jsgotangco: wait - is this for developing packages ?
[08:20] <jsgotangco> i just want to try it out
[08:20] <jsgotangco> i assume i just change the lines that says breezy to dapper
[08:21] <jsgotangco> Yagisan, but right, for creating packages, wanted to verify the steps being done for documentation
[08:22] <Yagisan> jsgotangco: for building packages Pbuilder howto is good, but it will only build a pbuilder for your arch
[08:23] <Yagisan> jsgotangco: if you need to build a pbuilder for another arch, ie i386 on an amd64 system it is a little bit more involved
[08:24] <jsgotangco> i'll go first to debootstrap and see how it goes
[08:25] <Yagisan> jsgotangco: debootstrap will give you a chroot - good for doing test installs of your package
[08:25] <Yagisan> jsgotangco: but I strongly recommend you do the pbuilder howto to set up your build environment
[08:25] <jsgotangco> what do i do first?
[08:26] <Yagisan> jsgotangco: what is your arch ?
[08:26] <jsgotangco> 386
[08:29] <Yagisan> jsgotangco: do pbuilder first to set up a build environment
[08:29] <Yagisan> jsgotangco: do you have apt-cacher set up ?
[08:29] <jsgotangco> hmm nope
[08:31] <Yagisan> jsgotangco: If you don't have a fat pipe, then we should set one up first, then pbuilder
[08:33] <jsgotangco> should i chnage all references of breezy to dapper?
[08:33] <Yagisan> jsgotangco: ping me if you need help with apt-cacher. yes you can change breezy to dapper, or hoary for that matter
[08:34] <jsgotangco> Yagisan, got spare time now?
[08:34] <Yagisan> jsgotangco: some
[08:35] <Yagisan> jsgotangco: I installed apt-cacher on my firewall box
[08:35] <jsgotangco> ahh
[08:38] <jsgotangco> i always get perm denied on this line
[08:38] <jsgotangco> $ sudo echo APT::Get::AllowUnauthenticated 1; >  /etc/pbuilder/apt.config/apt.conf.d/allow-unauthenticated
[08:40] <Yagisan> odd. Try this sudo `echo APT::Get::AllowUnauthenticated 1; >  /etc/pbuilder/apt.config/apt.conf.d/allow-unauthenticated`
[08:40] <Yagisan> if not, I'll dcc you the file
[08:49] <jsgotangco> strange
[09:40] <jsgotangco> nice shell
[09:42] <zakame> shell?
[09:42] <jsgotangco> metawire
[09:42] <jsgotangco> heh
[09:42] <zakame> ah :)
[11:39] <Gloubiboulga> slomo_, ping
[01:11] <slomo_> Gloubiboulga: pong
[01:20] <Gloubiboulga> salut pef
[01:20] <pef> Gloubiboulga: salut :)
[01:20] <Gloubiboulga> slomo_, hello. Still around ?
[01:20] <slomo_> sure
[01:21] <Gloubiboulga> do you have time to review my package slomo_ ?
[01:21] <slomo_> hmm, later... not now ;)
[01:21] <Gloubiboulga> np
[01:21] <pef> Gloubiboulga: url ? :)
[01:22] <Gloubiboulga> pef, http://revu.tauware.de/details.py?upid=1294 merci
[01:22] <Gloubiboulga> :)
[02:24] <zakame> evening fellow MOTUs :)
[02:28] <zakame> cool, package.qa.debian.org already incorporates ubuntu patches from Keybuk :)
[02:31] <Gloubiboulga> zakame, hi
[02:32] <zakame> heya Gloubiboulga :)
[02:32] <Gloubiboulga> I have a little question for you zakame (and other MOTUs)
[02:32] <zakame> go ahead :)
[02:33] <Gloubiboulga> I'm working on a package, and the source dir contains a .bat and several backup files
[02:33] <Gloubiboulga> should I remove all this from the .orig.tar.gz ?
[02:33] <slomo_> no
[02:33] <slomo_> only when it makes the package harder or impossible
[02:33] <zakame> backup files as in .*~ and ^#.*# ?
[02:33] <Gloubiboulga> zakame, yep
[02:34] <Gloubiboulga> slomo_, ok.
[02:34] <Yagisan> Gloubiboulga: there are very few reasons you can remove something from an orig.tar.gz
[02:34] <zakame> Gloubiboulga: dpkg-source will clean them anyway on package build, so you don't have to touch them ;)
[02:34] <Yagisan> Gloubiboulga: just ignore the backup files
[02:34] <Gloubiboulga> ok, I'll ignore all this files :)
[02:34] <Gloubiboulga> thanks Masters
[02:37] <Yagisan> slomo_: could I bother you for a bit ? I'd like to dcc you a rules file, a build log & see if you can help me see what I stuffed up
[02:38] <slomo_> yes, sure... but i've to leave in ~30 minutes
[02:39] <Yagisan> thanks slomo_
[02:40] <nomed> hi all
[02:40] <nomed> is there any xubntu devel here ?
[02:40] <nomed> *xubuntu*
[02:41] <nomed> i think some packages need some changes
[02:44] <Hieronymus> nomed: just file a bug?
[02:44] <nomed> Hieronymus, it's not a bug ...
[02:45] <nomed> but for ex .. should xfdesktop be a modular pkge ?
[02:45] <nomed> xfdesktop + xfce4-menu ?
[02:45] <nomed> or should ivman be modular ?
[02:45] <nomed> like ivman-kde + ivman-xfce + ivman ?
[02:45] <nomed> and so on ..
[02:48] <Hieronymus> nomed: no idea
[02:48] <zakame> nomed: perhaps posting something about that to ubuntu-devel ML would be better
[02:48] <zakame> brb MOTUs
[02:54] <siretart> nomed: janimo is your man for xfce. I think a post to our mailing list would be the best way to reach him
[02:55] <nomed> so for xubuntu ubuntu-motu list is fine ...
[02:55] <nomed> k
[02:55] <nomed> thanks
[02:56] <siretart> sure.
[02:56] <siretart> perhaps even ubuntu-devel
[03:08] <zakame> waah nufw has so many lintian errors, and I haven't even touched it :(
[03:50] <jinty> ajmitch: ping
[03:51] <Yagisan> jinty: it's almost 4am in new zealand, it'll be a while before you get a pong
[03:52] <jinty> Yagidan: thanks;) didn't realize
[03:53] <Yagisan> no worries mate
[04:10] <zakame> Unfrgiven: ping
[04:10] <zakame> (er prolly early morning too)
[04:13] <zakame> wb raphink :)
[04:16] <raphink> zakame: do you knwo of a way to recover data ?
[04:17] <raphink> I had instaled two chroots on this machine
[04:17] <zakame> raphink: recoving as in recovering deleted files?
[04:18] <Yagisan> that was quick
[04:18] <Yagisan> raphink: what sort of data do you need recovered ?
[04:19] <raphink> zakame: any idea?
[04:20] <raphink> Yagisan: read up
[04:20] <zakame> raphink: recoving as in recovering deleted files?
[04:20] <raphink> Yagisan: I just `rm -rf /var/sidchroot' forgetting my /home was mounted on it
[04:20] <raphink> zakame: yes
[04:20] <raphink> I lost most of my docs
[04:21] <raphink> i dont' really mind about my docs
[04:21] <Yagisan> raphink: oh dear - are you still using the box ?
[04:21] <raphink> but I lost my sister's docs aswell
[04:21] <raphink> and I'm pretty sure she didn't backup anything
[04:21] <zakame> raphink: well iirc one could do some debug2fs hacking, but that's bloody :/
[04:21] <raphink> yes
[04:21] <zakame> it's basically a hit-or-miss approach
[04:22] <raphink> :s
[04:22] <raphink> I basically deleted 90% of my sister's docs and settings
[04:22] <zakame> WHOA
[04:22] <Yagisan> raphink: crap - thats not good. best chance you have of recovering data is to dd /dev/hda and pipe it somewhere, eg another box with netcat
[04:23] <zakame> and if it's in ext3... well, that's very hard :((
[04:23] <Yagisan> then you need to run pyflag over the dd image to recover the data
[04:23] <raphink> yes it's ext3
[04:23] <Yagisan> that's what I do at work, it's time consuming
[04:24] <raphink> will taht work if I boot from a live CD and run it?
[04:24] <Yagisan> but the less you use the box, the better your chances of recovering the data
[04:24] <Yagisan> raphink: pyflag IIRC is not in ubuntu :(
[04:24] <Yagisan> raphink: was /home a seperate partition ?
[04:24] <raphink> so I should just halt the system if I want to have a chance to recover?
[04:25] <raphink> Yagisan: yes
[04:25] <Yagisan> raphink: oh that's good news. do you have enough space on another partition to make an image of home ?
[04:25] <raphink> no
[04:26] <raphink> on another comp maybe
[04:26] <Yagisan> raphink: can you access that other comp with eg nfs or samba ?
[04:26] <raphink> it's not set
[04:27] <Yagisan> raphink: the less you write to /home the better your chance of recovering the data
[04:27] <raphink> yes
[04:27] <Yagisan> raphink: you can't log out, because you killed /home, you'll have a hard time logging in
[04:27] <raphink> I'll reboot with knoppix that'll be safer
[04:27] <raphink> I didn' tkill /home
[04:28] <raphink> I already rebooted since I removed the files :s
[04:28] <Yagisan> raphink: I'd set up that other box now, and dd your home partition to an image there
[04:28] <raphink> dd?
[04:28] <zakame> back
[04:29] <Yagisan> raphink: dd if=/dev/hda1 of=/mnt/savemyarse/home.img
[04:29] <zakame> disk duplicate/dump
[04:29] <Yagisan> change hda1 to what your partition was
[04:29] <raphink> yes
[04:29] <raphink> is
[04:30] <Yagisan> zakame: reminds me of work this. Did I mention I do data recovery ?
[04:31] <zakame> heya seth_k|lappy :)
[04:31] <zakame> Yagisan: w00t
[04:31] <jsgotangco> Yagisan, $$$
[04:31] <seth_k|lappy> heya zakame :) how's tricks
[04:31] <Yagisan> If he was in sydney, he could drop the box off today
[04:31] <zakame> tricks?
[04:32] <Yagisan> anyway, if he doesn't get the dd done quickly, he'll have 0 chance of recovering his data
[04:32] <Kyral> Morning MOTU
[04:33] <zakame> hi Kyral :)
[04:33] <Yagisan> G'day Kyral
[04:34] <Yagisan> I'll be heading off to bed soon. zakame no other ideas on why my rules voodoo fails ?
[04:34] <zakame> Yagisan: is this package available somewhere so I could d-l and check?
[04:34] <zakame> (I'll be in bed rsn myself ;)
[04:35] <Yagisan> zakame: I'll put the current work in progress up in just a sec
[04:36] <Yagisan> just waiting on another build to see if that helps
[04:36] <seth_k|lappy> zakame, things, work, whatever :P
[04:37] <Yagisan> zakame: you'll need to add my private repo to your list if you want the extra amd64 build deps though
[04:37] <zakame> seth_k|lappy: ah :) well, here doing some edits for DebootstrapChroot
[04:38] <zakame> k
[04:41] <raphink> hi again
[04:43] <zakame> wb raphink :)
[04:43] <raphink> Yagisan, I'm on knoppix now
[04:43] <raphink> ty zakame
[04:43] <raphink> my /home is not mounted anymore
[04:43] <raphink> so there's no risk of altering it no more
[04:43] <raphink> now what shall I do?
[04:44] <raphink> ;s
[04:45] <Yagisan> raphink: caught me just before leaving for bed
[04:45] <raphink> huhu
[04:45] <raphink> Yagisan, see my pb is that my /home is far bigger than any other partition I have here
[04:45] <Yagisan> raphink: is the other box up and running, and accessible over the network ?
[04:45] <raphink> yes
[04:46] <Yagisan> raphink: I never work on the raw partition, only images - so I can't fuck up
[04:46] <raphink> mhm
[04:46] <Yagisan> raphink: can you mount a directory on the other box ?
[04:46] <raphink> well the /home I want to work on is 107.57GB, with 26.61GB currently used
[04:46] <raphink> I can do anything on the other box, over ssh
[04:47] <Yagisan> raphink: and you will need to search 107.57GB to find that 26.61GB of data
[04:47] <raphink> yes
[04:47] <raphink> the pb is that nowhere except on /home do I have more than 100GB of HD
[04:47] <raphink> the other box is less than 60GB
[04:48] <raphink> and this one's / is about 6GB
[04:48] <raphink> and i guess it wouldn't be a a good idea to play with LVM
[04:48] <raphink> that wouldn't help recovering
[04:48] <Yagisan> raphink: wish you were here, you could drop the box off at my office
[04:48] <raphink> :s
[04:48] <Yagisan> raphink: just a sec - I'll see if I can find a live recovery cd
[04:49] <raphink> hmm
[04:49] <raphink> doesnt knoppix have some tools for that?
[04:50] <Yagisan> raphink: you need a more specialised cd, I'm afraid
[04:50] <raphink> hmmm
[04:50] <raphink> I don't know how I'm going to burn a CD with no /home
[04:50] <raphink> ;)
[04:50] <raphink> well I can burn it on the other box ;)
[04:51] <Yagisan> raphink: don't worry, your not screwed yet - you may be when your sister finds out, but not yet
[04:51] <raphink> oh no worries I called her to tell her ;)
[04:51] <raphink> she said she'd like to recover her pics
[04:51] <raphink> but apart from that heh she just had to backup her stuff ;)
[04:51] <raphink> she said it herself so no I'm not screwed ;)
[04:55] <raphink> although I'd like to recover the data ;)
[04:56] <Yagisan> raphink: http://www.remote-exploit.org/index.php/Auditor_tools
[04:56] <zakame> gn8 all :)
[04:56] <raphink> gn8 zakame
[04:57] <Yagisan> that may help you - it has ext2 recovery
[04:57] <raphink> it's ext3
[04:57] <Yagisan> zakame: night
[04:57] <Yagisan> raphink: ext3 == ext2 + journal (another file)
[04:57] <zakame> gn8 raphink , Yagisan :)
[04:58] <Yagisan> zakame: I have a link for you
[04:59] <Yagisan> zakame http://eyagi.bpa.nu/~jamie/voodoo_magic_here/
[04:59] <zakame> got it ;)
[04:59] <jsgotangco> Yagisan, those chroot and pbuilder wiki pages are quite outdated btw, zakame was very helpful in updating them, i got them working already
[04:59] <jsgotangco> thanks for the help earlier
[04:59] <zakame> no problem :)
[05:00] <zakame> wb koke
[05:00] <Yagisan> jsgotangco: your welcome, sorry I couldn't be more helpful
[05:33] <raphink> 14106624 inodes scanned, 0 deleted files found
[05:33] <raphink> :(
[05:34] <Yagisan> raphink: oh dear, you need in-depth forensics to recover you data then
[05:36] <Yagisan> raphink: http://www.e-fense.com/helix/contents.php that should have pyflag on it, but you'll need to make an image of the data
[05:36] <Yagisan> raphink: need to go now, baby waking up
[05:38] <raphink> ok
[05:39] <raphink> unfortunately I don't have any HD that is large enough to make an image of the data
[05:46] <raphink> Yagisan, I give up on recovering...
[05:46] <raphink> but I'll set up a backup system here
[05:46] <Yagisan> raphink: for future perhaps sbackup would help ?
[05:53] <raphink> sbackup Yagisan ?
[05:54] <Yagisan> raphink: Its in universe - I use it for my home box. seems like a nice backup tool
[05:56] <raphink> I'm on KDE, so i'd like a qt tool better ;)
[05:56] <raphink> I was asked to package Keep a few hours ago
[05:56] <raphink> ;:)
[05:56] <raphink> http://kde-apps.org/content/show.php?content=32984
[05:56] <raphink> this was kind of calling me it seems ;)
[05:57] <Yagisan> raphink: qt, gtk - I don't care as long as it does the job right.
[05:57] <raphink> Yagisan: actually, my idea is that there are two comps on this network, so I could backup comp 1 on comp 2 and vice versa
[05:59] <Yagisan> raphink: until gmailfs broke, I had a copy on gmailfs, one on dvd at home, and one on dvd offsite
[05:59] <raphink> hehe
[05:59] <raphink> I do care ;)
[05:59] <raphink> I think I'll be reviewing more in the next few days
[05:59] <raphink> since I can't package anymore, having deleted my private key from this comp
[05:59] <raphink> ;)
[06:00] <raphink> mhm
[06:00] <Yagisan> raphink: thats why I have at least 2 backups now
[06:01] <raphink> hehe
[06:02] <Yagisan> raphink: I also know the pain of losing /home. thats why my /home is now a 600GB RAID5 array
[06:03] <raphink> hehe
[06:03] <raphink> well heh
[06:04] <Lathiat> not raid6? :)
[06:04] <Yagisan> Lathiat: because I ran out of money at the shop, and ubuntu doesn't support my two remaining ide ports
[06:05] <Lathiat> could have been 400GB raid6 :)
[06:07] <Yagisan> Lathiat: in dapper I think my two remain ports will be supported, I'll try to go for an 800GB raid5 out of 5 200GB drives
[06:08] <Yagisan> It would be cool for a desktop box
[06:08] <Lathiat> depends if you want more space or more redundancy ig uess :)
[06:08] <Yagisan> Lathiat: If I toss the cd-rom, and get 3 drives, I can get raid6
[06:10] <Yagisan> Lathiat: how much storage do you have on your box ?
[06:10] <Lathiat> i have 2 laptops, 60G and 40G :)
[06:10] <Lathiat> i do have a box here with 5x200G in raid1+0 + hotspare tho
[06:10] <Lathiat> sadly not mine :)
[06:11] <Lathiat> raid1+0 for reasons of seek performance
[06:11] <Lathiat> in that raid1+0 allows you to do two requests at once
[06:11] <Lathiat> as opposed to raid5 where each hit read or write hits all disks
[06:12] <Lathiat> where as reads only hit 2/4
[06:12] <Lathiat> with 1+0
[06:12] <Yagisan> Lathiat: yeah, but I have an uneven number of disks, so raid 5 was the only (decent) choice
[06:12] <Lathiat> right, and common
[06:13] <Lathiat> does raid6 need an even number of drives?
[06:13] <Yagisan> Lathiat: 4 minimum
[06:13] <Yagisan> but same speed penalty as raid5
[06:14] <Lathiat> with 4 drives raid6 is basically pointless, may as well raid1+0 ?
[06:14] <Lathiat> actually, i suppose that raid6 lets two disks die
[06:14] <Lathiat> with raid1+0, it depends which disks
[06:14] <Yagisan> reading seems rather good with in-kernel raid5, writes hammer the pci bus though
[06:14] <Lathiat> if two fo the wrong disks die then yoru fooked
[06:14] <Lathiat> Yagisan: this box here has a pci-x sata card
[06:14] <Lathiat> sata_sil24 driver
[06:15] <Lathiat> i can pull 60M/s off 4 disks at once
[06:15] <Lathiat> 5th disk didnt get any faster tho
[06:15] <Lathiat> not sure where the limitation in that is
[06:15] <Yagisan> Lathiat: well, the I in raid is inexpensive, that's why we have backups, and backups of backups, and we test them too
[06:15] <Lathiat> ;)
[06:16] <Lathiat> anyway
[06:16] <Lathiat> -> bed
[06:16] <Lathiat> night :)
[06:16] <Yagisan> Lathiat: I have standard 32bit 33Mhz pci bus here
[06:16] <Yagisan> night, wow 4am already
[06:16] <Lathiat> Yagisan: yeh thatd suck a bit, this box is dual opteron :)
[06:16] <Lathiat> Wed Dec 28 01:13:48 WST 2005
[06:16] <Yagisan> Lathiat: single amd64 here
[06:16] <Lathiat> Yagisan: linux swraid kicks ass tho
[06:16] <Lathiat> leaving comment.. honest ;)
[06:17] <Yagisan> Lathiat: I was impressed, it beat pci raid cards
[06:17] <Lathiat> i know freebsd die-hards who use linux because its software raid craps all over freebsds, and in many cases outperforms hardware cards
[06:17] <Lathiat> also has the advantage of being usable over multiple controllers and even interface types, and not the need to replace the card with the same card
[06:17] <Lathiat> e.g. if your raid card dies, and you dont get the exact same or similar card, you lose all your data
[06:17] <Yagisan> :) yep
[06:18] <Lathiat> s
[06:18] <Lathiat> anyway, enjoy. night.
[06:19] <raptoid> yes  can
[06:19] <Yagisan> hmm, I make nice typos
[07:18] <\sh> ogra: ping works?
[07:19] <ogra> didnt try yet
[07:19] <ogra> i was waiting for your ok
[07:49] <\sh> new wine is coming today
[07:49] <\sh> for dapper :)
[07:54] <\sh> moins siretart
[07:56] <siretart> huhu \sh
[07:57] <steve132> hey, um I am a bit lost... I would like to help motu with a particular package, but I do not know where to start.
[08:23] <Yagisan> for all those interested, initial upload of my ia32-libs-universe work-in-progress is here http://revu.tauware.de/details.py?upid=1318
[08:25] <slomo> gn8 Yagisan :)
[09:10] <JohnnyMast> any motu around ?
[09:20] <crimsun> JohnnyMast: ?
[09:30] <cmatheson> hey guys, been using ubuntu for the past seven months or so and i want to get involved now.  what needs doing?
[09:30] <crimsun> see the merge list
[09:30] <crimsun> (topic)
[09:31] <JohnnyMast> crimsun sorry for the late reply. But i have a package on revu but there is a new version out then the one im packing. When i put a new version up with the new app version inside would it be bad ?
[09:31] <tseng> no
[09:32] <crimsun> JohnnyMast: no, just make sure to ask one of the REVU admins to remove the older
[09:32] <JohnnyMast> is one around ?
[09:33] <crimsun> JohnnyMast: ask ajmitch, siretart, or \sh about removing the older version from REVU
[09:33] <JohnnyMast> thanks for the info lads
[09:33] <JohnnyMast> okey
[09:34] <cmatheson> crimsun: anyone can merge stuff?
[09:34] <crimsun> cmatheson: yes
[09:34] <crimsun> (granted only those of us with upload privs can upload them)
[09:34] <cmatheson> crimsun: ok cool
[09:35] <cmatheson> generally what is involved in a merge (aside from re-compiling?)
[09:35] <crimsun> generally you pick a merge, use the lp.py scripts to do the launchpad magic, attach a confirmed-working debdiff against the newer debian version, and ping a MOTU
[09:36] <cmatheson> crimsun: ok, i'm gonna look into that thanks
[09:37] <crimsun> Starting with the REPORT, you should check if the newer debian packaging has incorporated ubuntu's changes. If so, you can mark the package as a sync, otherwise you'll have to inspect the -dropped diff and hand-merge.
[09:38] <cmatheson> crimsun: the REPORT is something that the MOTU gives back to me or what is that?
[09:38] <crimsun> cmatheson: no, it's in the MoM directory
[09:39] <crimsun> Each active link (merge) on http://tiber.tauware.de/~sistpoty/MoM/index.py?state=new is into the associated MoM directory
[09:39] <cmatheson> oooh, ok, i think i gotta lot of stuff to read right now
[09:53] <cmatheson> so let me make sure i have this right... i can choose any of the UNASSIGNED packages on http://tiber.tauware.de/~sistpoty/MoM/index.py?state=new and work on those, assumign i file the correct but report.  after i make a debdiff i talk to someone in here about it (and i mark the bug 'pending upload')
[09:56] <crimsun> cmatheson: essentially, yes.
[11:31] <Kyral> Oh fun
[11:32] <Kyral> I get to compare a Gentoo list against Apt
[11:32] <\sh> what?
[11:33] <\sh> what will you compare? apple and cherries?
[11:33] <Kyral> no
[11:34] <Kyral> I was given the World file from our old build and told to check it against Apt to see what is there and what isn't
[11:36] <Kyral> and its complicated by the difference categories
[11:37] <\sh> don't think about the cats :)
[11:37] <Kyral> yah well
[11:37] <Kyral> for emacs its "app-emacs/session"
[11:37] <Kyral> I saw an entry for "kde-base/kde-env"
[11:37] <\sh> yes...
[11:38] <\sh> because gentoo has a different package scheme
[11:38] <Kyral> I see KDE-Base anything I'm gonna assume its under Kubuntu-Desktop
[11:38] <\sh> no
[11:38] <Kyral> \sh: I know I used Gentoo before Ubuntu
[11:38] <\sh> kdebase in gentoo is a meta build
[11:38] <Kyral> then what is kde-env?
[11:38] <\sh> check /etc/env.d/
[11:39] <\sh> if you emerge different versions of kde then you have different kde environments
[11:39] <Kyral> I'm gonna have to got through the descriptions of these oy
[11:39] <\sh> sure :)
[11:42] <Kyral> I half a mind to make a shell script to do the first pass
[12:01] <Kyral> Maybe I shouldn't be doing this on Dapper...


[00:32] <lfaraone> wgrant: should a new method be created to replace syncSource, or can we modify the behavior of it? (if there are existing clients I don't want to break them)
[00:32] <wgrant> lfaraone: We'll be adjusting syncSource, right.
[00:34] <lfaraone> wgrant: do we send out announces for archive-admin-performed syncs? if not, why should the behavior change for motu-requested syncs?
[00:34] <wgrant> lfaraone: Except for autosyncs, yes, we do.
[00:34] <wgrant> Anyway, I should leave for uni in a couple of minutes.
[00:34] <lfaraone> wgrant: okay, and no changes file is generated for that either, right?
[05:49] <MikeChelen> is it possible to fork a project, or is there some other recommended way to contribute code to a project?
[05:49] <mwhudson> MikeChelen: generally you just push up a new branch of the project
[05:51] <MikeChelen> mwhudson: should it be done through bzr or the project page to register a branch?
[05:51] <mwhudson> MikeChelen: through bzr is easiest
[05:52] <MikeChelen> mwhudson: is there a guide for how to do that?
[05:54] <mwhudson> perhaps, but it's easy: bzr push lp:~$you/$project/$branch_name
[05:55] <mwhudson> ah, https://help.launchpad.net/Code/UploadingABranch <- MikeChelen
[05:55] <MikeChelen> ok, just have to get the authentication set up
[05:57] <MikeChelen> mwhudson: got it, thanks! should the branch name be anything in particular?
[05:58] <mwhudson> MikeChelen: generally i choose a name that will remind me later of what the branch is for (for example, if it's to fix a bug, putting the bug number in)
[05:59] <mwhudson> MikeChelen: you can request a merge proposal against the project's trunk too
[06:00] <MikeChelen> mwhudson: that is the right thing to do, if the code will hopefully be included?
[06:01] <mwhudson> MikeChelen: yes
[06:07] <MikeChelen> still figuring out bzr basics :)
[06:08] <MikeChelen> is there any way to allow download for particular packages?
[06:09] <MikeChelen> that is probably only for the main team right
[06:11] <mwhudson> MikeChelen: i don't understand, sorry
[06:12] <MikeChelen> mwhudson: it would be nice to have some way of downloading a subdirectory of the project, packaged into a .zip or other single file
[06:13] <mwhudson> oh right
[06:13] <mwhudson> yeah, that's a still unimplemented feature
[06:36] <wgrant> win 9
[06:36] <wgrant> Argh.
[08:17] <dupondje> Hi, there seems to be a little missing code when subscribing someone :)
[08:18] <dupondje> when I subscribe for example ubuntu-sponsors, its just a normal icon that gets added in front, not a star like when I refresh :)
[08:22] <BlackZ> dupondje: report it as a bug, if you think it's
[08:26] <vish> does anyone know about the new "Expired" status?
[08:27] <vish> is it available only when the bug has expired and only for the Bug control members , or for anyone ?
[08:27] <vish> and do the expired bugs show up in the searches?
[08:29] <dupondje> BlackZ: https://bugs.launchpad.net/launchpad/+bug/588162
[08:29] <BlackZ> thanks dupondje
[08:29] <dupondje> not that its very special :P
[08:29] <vish> dupondje: i can confirm that bug , it happens to all the teams ;)
[08:30] <BlackZ> well, actually I'm not sure if it's a bug
[08:30] <dupondje> well its not a bug really
[08:30] <dupondje> more a missing feature ? :)
[08:30] <BlackZ> dupondje: probably
[08:30] <dupondje> ah well
[08:30] <dupondje> if somebody feels bored :P
[08:38] <wgrant> I discovered that when I was fixing the AJAX subscription code many months ago. I decided I couldn't be bothered fixing that one.
[08:39] <wgrant> I believe there's already a bug.
[08:39]  * wgrant hunts.
[08:40] <BlackZ> wgrant: seems not
[08:41] <BlackZ> rebooting (I have some problems with the keyboard, argh!)
[08:43] <noodles775> fta: Hi... just to be sure, with bug 588044, you did copy from lucid to maverick *including* binaries?
[09:42] <fta2> noodles775, i just used the "copy" feature in the PPA, without rebuild
[09:43] <fta2> noodles775, well, actually, i don't remember. I'm sure i didn't rebuild the ffmpeg-codecs in the chromium/stable ppa
[09:45] <noodles775> fta2: ok... I've updated the bugs with a bit more info.
[10:06] <fta2> i wonder why the API is so slow...
[10:11] <fta2> noodles775, Q: is there a way to bench the api (wrt speed, num of http requests, ...)
[10:12] <fta2> because it takes ~5min to create those 5 dashboards: http://people.ubuntu.com/~fta/ppa-dashboard/    .. which i find incredibly long
[10:14] <fta2> Q: is it possible to get the "Missing build dependencies" reason using the API?  (like here: https://edge.launchpad.net/~ubuntu-mozilla-security/+archive/ppa/+build/1762412)
[10:15] <noodles775> fta2: I haven't checked if the api provides utilities itself, but I know the launchpad foundations team is currently looking at tools benchmarking in general (see the "performance dashboard" thread on launchpad-dev).
[10:15] <noodles775> s/tools/tools for/
[10:16] <noodles775> I'd assume in your case it's mostly reducing the number of round-trips?
[10:17] <fta2> i think so
[10:17]  * noodles775 looks at the missing build dependency...
[10:17] <fta2> https://dev.launchpad.net/Foundations/SystemPerformance => "The server encountered an internal error or misconfiguration and was unable to complete your request."
[10:17] <noodles775> wfm? (but yeah, very ironic :)
[10:18] <fta2> hm.. transient error, works fine now
[10:19] <noodles775> fta2: regarding the build dependency... the template is just using IBuild.dependencies which is also exported, so that should work.
[10:20] <noodles775> (you'll obviously need to only display it as a *missing* dependency if the build state is DepWait).
[10:20] <fta2> ok, thanks
[10:27] <geser> fta2: build.dependencies contains the missing dep on which the build waits
[10:28] <geser> it's successfully used for the FTBFS listing
[10:31] <geser> fta2: and with "import httplib2; httplib2.debuglevel = 1" at the beginning of your script you can at least get the LP API HTTP request shown, which you could use for counting or checking if a object is refetched too often
[10:40] <fta2> geser, already tried that, it's just showing the requests (without timing them).. and i just see there are too many
[10:41] <fta2> i wonder if this is relevant: http://code.google.com/p/httplib2/issues/detail?id=91
[12:08] <TresEquis> Just reported an issue with failing SVN imports: https://answers.launchpad.net/launchpad/+question/113078
[12:10] <jpds> TresEquis: I think that that was fixed a while ago.
[12:13] <maxb> It definitely appears to be fixed now
[12:16] <maxb> TresEquis: ^
[12:18] <TresEquis> maxb: OK, but I just saw the import fail this morning
[12:18] <jpds> TresEquis: Yes; and the configuration issue was fixed. :)
[12:18] <maxb> weekday mornings are a good time for admins to wake up and fix things :-)
[12:19] <TresEquis> OK, thanks!
[12:20] <rowinggolfer_> Are there any issues regarding ppa build system? I've pushed my sources to my ppa, and can see no evidence of it, nor have I had any mail about rejection or acceptance.
[12:21] <maxb> rowinggolfer_: 1) Is your gpg key known to launchpad? 2) Was your .changes file correctly signed? 3) Have you waited 5 minutes?
[12:22] <rowinggolfer_> maxb I've waited 16 hours.
[12:22] <rowinggolfer_> my gpg key did expire last month, but I "updated" it using the lucid gui tool.
[12:22] <rowinggolfer_> could that be te problem?
[12:23] <rowinggolfer_> if so I would have expected dput to report that...?
[12:23] <maxb> No, dput would not report this
[12:24] <rowinggolfer_> ok.
[12:24] <maxb> Search for your key on keyserver.ubuntu.com and verify that your updated key is there
[12:24] <rowinggolfer_> thanks
[12:25] <rowinggolfer_> lol... nice deafault apache screen http://keyserver.ubuntu.com/
[12:25] <maxb> Fundamentally the problem is that dput sends the files to a dumb ftp server, and they are actually processed by a separate job
[12:25] <maxb> http://keyserver.ubuntu.com:11371/ (and heh, would be nice if they put in a redirect)
[12:25] <rowinggolfer_> thanks again
[12:27] <rowinggolfer_> maxb - yeap that's my problem. many thanks
[12:28] <maxb> Do a gpg --keyserver keyserver.ubuntu.com --send-key "Your key ID"
[12:28] <maxb> I am uncertain how long it may take for Launchpad to pick it up from there
[12:34] <bilalakhtar> Hi there lp devs, what will be the new features of lp 10.05?
[12:40] <MikeGuo> hi, guys, not sure what's happen. but I found the download speed is so slowly. that's normal?
[12:41] <MikeGuo> the page always told me "please try again"
[12:41] <MikeGuo> and told me "there was a problem connecting to the Launchpad server"
[12:57] <bilalakhtar> Hi there lp devs, what will be the new features of lp 10.05?
[13:02] <matsubara> bilalakhtar, I think the easiest way to know before the release is to look at https://edge.launchpad.net/launchpad-project/+milestone/10.05. mrevell will send an announcement once the release is done with the highlights
[13:03] <bilalakhtar> matsubara: thanks
[13:05] <matsubara> np
[13:05] <rowinggolfer_> milestones are fantastic. blueprints I don't get :(
[13:23] <TresEquis> Is there any talk of hosting a per-project wiki or other TTW project documentation in LP
[13:25] <rowinggolfer_> TresEquis, https://answers.launchpad.net/launchpad-foundations/+question/36663
[13:26] <rowinggolfer_> also see this open bug https://bugs.launchpad.net/launchpad-foundations/+bug/240067
[13:31] <TresEquis> rowinggolfer_: thanks, I figured it must have come up
[13:32] <TresEquis> I haven't actually worked with the LP source yet, but do have significant relevant experience with other Python / Zope based wikis
[14:12] <rowinggolfer_> maxb - my key is now updated on the ubuntu keyserver, but as you implied launchpad doesn't know yet.
[14:12] <Joy> ok, i think i have an account in launchpad, but i'm not sure what its name is. i've tried the password recovery on one, but never got the mail. what do i do?
[14:12] <rowinggolfer_> frustrating that this error passes "silently"
[14:16] <matsubara> Joy, is this the account: https://edge.launchpad.net/~joy+launchpad? did you try the email address listed there? can you check emails are not caught by spam filters on your side?
[14:18] <Joy> can you tell me what *is* the e-mail address listed there? :))
[14:18] <Joy> Email: Log in for email information.
[14:18] <Joy> that's what i see
[14:18] <Joy> i tried<EMAIL_ADDRESS>[14:18] <Joy> and mx1.entuzijast.net got no messages for that at all
[14:19] <matsubara> Joy, doh, sorry. I thought the email was availabe to everyone (it actually is but you need to be logged in. my bad)
[14:19] <matsubara> Joy, linux.hr is the domain. ring any bells?
[14:20] <Joy> ah, ok, i'll try that then
[14:21] <matsubara> Joy, ok. let me know if you need further help
[14:21] <Joy> thanks (waiting for the mail now)
[14:21] <matsubara> np
[14:24] <Joy> [joy@griffin:~]% grep -i launchpad /var/log/exim4/mainlog
[14:24] <Joy> [joy@griffin:~]%
[14:24] <Joy> waah. :)
[14:24] <Joy> (mx1.linux.hr)
[14:30] <geser> did you try the right delimiter in your localpart?
[14:31] <Joy> well matsubara pointed to the plus
[14:31] <Joy> but then, yes, that might be an issue
[14:31] <Joy> % /usr/sbin/exim4 -bt<EMAIL_ADDRESS>[14:31] <Joy> rowinggolfer_: system_aliases for<EMAIL_ADDRESS>[14:31] <Joy> rowinggolfer_: aliases for<EMAIL_ADDRESS>[14:31] <Joy><EMAIL_ADDRESS>is undeliverable: Unrouteable address
[14:31] <Joy> rowinggolfer_: sorry, it's my irssi expanding R:
[14:31] <geser> on your LP page it's not the +
[14:32] <matsubara> Joy, I didn't want to post your email here and I assumed you knew it. it's<EMAIL_ADDRESS>[14:32] <Joy> oh, bother :)
[14:32]  * Joy should un-qmail-ize that machine one day, too
[14:33] <Joy> sorry for the confusion, although that still doesn't explain why the launchpad website didn't immediately error out
[14:33] <Joy> probably an anti-spam method?
[14:36] <Joy> 2010-06-01 15:35:51 H=adelie.canonical.com [<IP_ADDRESS>]:41420 I=[<IP_ADDRESS>]:25<EMAIL_ADDRESS>temporarily rejected RCPT<EMAIL_ADDRESS>greylisted.
[14:36] <Joy> yesssh, finally
[14:36] <Joy> thank you both
[14:36] <henninge> sinzui: ping
[14:36] <sinzui> hi henninge
[14:36] <henninge> Hi sinzui!
[14:37] <henninge> just a moment
[14:38] <henninge> sinzui: defcon is seeing that his karma is constantly decreasing although he is using LP regularly. Any idea what to look for?
[14:39] <sinzui> Very old high point work has expired after 1 year
[14:39] <henninge> so that would lead to points expiring faster than gaining new points?
[14:39] <sinzui> henninge, defcon: spec work and burst of bug triage from last year can cause a rapid decline after one year
[14:39] <rowinggolfer_> defcon - if you are demotivated - try #fedora ;)
[14:41] <sinzui> karma expires so that new contributors can quickly be ranked with old contributors.
[14:41] <henninge> defcon: you are saying that you have not worked on Launchpad that long?
[14:43] <defcon> im active since round about 2 weeks
[14:43] <defcon> before i paused ca. 1 year
[14:45] <henninge> sinzui: it went from 40 to almost 1500 and now down to 1380 within 4 days. Is that a normal fluctuation?
[14:46] <sinzui> No.
[14:47] <henninge> sinzui: should we open a bug to investigate further after the roll-out?
[14:47] <defcon> the last 4 days the karma was not calculated, although i answered a lot of question, did translation and so on
[14:48] <sinzui> defcon have you worked with branches? I know karma calculation failed a few times
[14:48] <defcon> henninge, if the translation is wrong, please correct me :D
[14:48] <defcon> sinzui, no
[14:49] <henninge> defcon: you're fine ;)
[14:50] <defcon> henninge, thanks :D
[14:51] <defcon> sinzui, the only thing i did (since karma is decreasing) i rejoined launchpad-beta-users because it was expired
[14:52] <sinzui> registry (teams and project) do not privide karma
[14:52] <defcon> ok
[14:52] <sinzui> defcon, report a bug. I need to investigate this after the release or at least when I am not talking to 5 people at the same time.
[14:53] <defcon> ok
[15:00] <rowinggolfer_> maxb, thanks for your help earlier - to confirm that my packages have now uploaded, thanks.
[15:01] <maxb> excellent :-)
[15:02] <rowinggolfer_> should I delete my "intrepid" packages now?
[15:10] <maxb> rowinggolfer_: You cannot upload new intrepid ones, but you are under no obligation to delete existing ones.
[15:10] <maxb> Your choice as maintainer of the PPA
[15:12] <rowinggolfer_> maxb... thanks again. I noticed it didn't allow the new intrepid package
[15:25] <Penguin_Guy> Hi! I'm relatively new to Launchpad, I've just started a team and have some working code at https://launchpad.net/~blobber - I just wanted the thumbs up that I'm going about this the right way and maybe some guidance on what to do next. Thanks.
[15:30] <bilalakhtar> Penguin_Guy: Is the blobber project registered in lp?
[15:31] <bilalakhtar> Penguin_Guy: ok, it isn't.
[15:31] <rowinggolfer_> Penguin_Guy, I would be concerned about the name "blobber"... it seems already to be the name of some established games owned by the likes of shockwave
[15:33] <Penguin_Guy> rowinggolfer_: You mean there may be legal issues?
[15:35] <rowinggolfer_> Penguin_Guy, yes.
[15:35] <rowinggolfer_> if your game gets 10,000,000 users... (and you never know)... you'll need to change the name for sure
[15:36] <Penguin_Guy> rowinggolfer_: Right, I'll change the name, is there anything else?
[15:36] <rowinggolfer_> nope, it looks good to me.
[15:36] <rowinggolfer_> but I know nothing.
[16:01] <maxb> Penguin_Guy: You should clarify the purpose of the team a bit. Is it for anyone and everyone, and you plan to request a mailing list? Or is it going to own Bazaar branches - in which case it shouldn't be an Open team?
[16:02] <maxb> Penguin_Guy: And it's absolutely the wrong thing to do to use +junk branches for collaborative work
[16:04] <Penguin_Guy> maxb: I was planning on starting a project for blobber, and let anyone join the project. I've used a +junk branch for now because I'm not really sure where the branch should be.
[16:04] <maxb> People do not join projects, they join teams
[16:04] <maxb> The problem with 'letting anyone join' is that anyone can join.... and delete your branch
[16:05] <Penguin_Guy> maxb: But they need to have signed the CoC first don't they?
[16:05] <maxb> No
[16:05] <maxb> The CoC only gates the ability to create a PPA
[16:08] <Penguin_Guy> macb: Ah, I'll get that changed right now.
[18:10] <vadi2> Are there plans to have launchpad use the async google analytics script? http://ur1.ca/04sx5 (it's stuck on that)
[19:13] <BadChoice> Hi
[19:13] <BadChoice> I've a problem when creating a branch..
[19:13] <BadChoice> Permission denied (publickey).
[19:14] <BadChoice> And i don't know how to solve it
[20:09] <thopiekar> hi
[20:13] <thopiekar> I am working on a application that should download a file from my bzr branch.. but these links that I can find on "view branch" page.. point at the file of the current branch.. but is there a link or a way to download always the latest file even after branch pushes?
[20:13] <thopiekar> I hope you understand what my problem is ;)
[20:34] <beuno> thopiekar, yes
[20:36] <thopiekar> I found now a snipplet with Acire that downloads the latest branch revision
[20:36] <beuno> thopiekar, use head:
[20:36] <beuno> as the revision
[20:38] <thopiekar> so this is right? http://bazaar.launchpad.net/~thopiekar/mopedix/artwork/download/head:/mopedixlogo.png-20100513112401-ksjo1e3l3gmoija7-9/mopedix-logo.png
[20:38] <thopiekar> what about the "20100513112401-ksjo1e3l3gmoija7-9"
[20:39] <beuno> that's the file-if
[20:39] <beuno> file-id
[20:39] <beuno> which is fine
[20:39] <beuno> it doesn't change
[20:39] <thopiekar> this file-id will not be changed after a push?
[20:40] <thopiekar> ahh ok :P
[20:40] <thopiekar> thanks beuno!
[21:19] <thopiekar> beuno: is there also a way to list the files of a branch without bzrlib?
[21:21] <timour> Hi, I am one of the MariaDB core developers, I pushed into an LP tree 5 hours ago, and the branch page still says:
[21:21] <timour> "
[21:21] <timour> Launchpad is processing new changes to this branch which will be available in a few minutes. Reload to see the changes.
[21:21] <timour> "
[21:21] <mwhudson> timour: are your changes present?
[21:22] <mwhudson> the message is probably lying :/
[21:22] <timour> mwhudson, how do I check this?
[21:22] <timour> mwhudson, the reason I think there is a real problem, is because our BuildBot system didn't start building.
[21:23] <timour> mwhudson, this is the branch: https://code.launchpad.net/~maria-captains/maria/5.3-subqueries
[21:24] <timour> mwhudson, perhaps if the message is lying to me (via the web page), it is lying to out BuldBot system, and that is a real problem.
[21:25] <timour> s/out/our
[21:29] <mwhudson> timour: it seems the branch is damaged somehow :/
[21:29] <timour> mwhudson, what would you suggest? delete it?
[21:29] <mwhudson> ah
[21:30] <mwhudson> timour: the branch it is stacked on, https://code.edge.launchpad.net/~maria-captains/maria/5.1, has been upgraded to 2a format
[21:31] <mwhudson> timour: you should be able to see a upgrade button on https://code.edge.launchpad.net/~maria-captains/maria/5.3-subqueries, clicking it will very likely help
[21:32] <timour> mwhudson, I heard it takes many hours to convert, would it be much faster if I just delete it, and push again?
[21:33] <timour> mwhudson, by the way, thank you for looking into this.
[21:34] <mwhudson> timour: only the revisions not in the stacked-on branch need to be converted, it shouldn't take very long
[21:34] <mwhudson> deleting and repushing will probably be faster though, indeed
[21:35] <timour> mwhudson, ok, I will try to minimize human time, so will try first upgrading.
[21:35] <maxb> remember also that delete/repush would remove people subscribed to the branch
[21:36] <timour> maxb, yes, and it will remove it from BuildBot, so I pushed the "upgrade" button.
[21:37] <timour> mwhudson, maxb: Many thanks, I hope it works. Do you have a guesstimate how long it may take? Is it going to be upgraded by tomorrow?
[21:39] <mwhudson> timour: i would guess < 1 hour
[21:40] <timour> mwhudson, I hope that this solves the problem, otherwise we will really need your help. Thank you!
[21:41] <mwhudson> timour: np, sorry the problems are so opaque
[21:43] <timour> mwhudson, now the message that the branch is being upgraded is gone, there is still an "upgrade" button, and still "Launchpad is processing new changes to this branch". I hope this is how it should work.
[21:44] <mwhudson> timour: that's suspiciously fast :/
[21:45] <mwhudson> oh right, upgrading the branches this way around doesn't work :(
[21:45] <timour> yes
[21:45] <mwhudson> timour: you could try running "bzr upgrade lp:~maria-captains/maria/5.3-subqueries" yourself, i think that will actually work
[21:46] <timour> mwhudson, and that works on the LP branch, not locally>
[21:46] <timour> ?
[21:46] <mwhudson> timour: well, all the data gets copied up ad down the pipe but yes
[21:46] <timour> I mean should I run this locally, inside my 5.3-subqueries root?
[21:48] <lifeless> mwhudson: which way around?
[21:49] <mwhudson> timour: doesn't matter
[21:50] <mwhudson> lifeless: if you use the upgrade button on the stacked-on branch first, then trying to upgrade the stacked branch the same way fails
[21:50] <mwhudson> i think
[21:50] <timour> mwhudson, ok, I started the process, let's see what happens.
[21:51] <lifeless> mwhudson: it shouldn't
[21:51] <lifeless> mwhudson: bzr doesn't care, and I'm pretty sure rockstar had tests for both ways around
[21:53] <mwhudson> lifeless: i agree it shouldn't
[21:55] <timour> mwhudson, lifeless: so now I started the upgrade process via the button, then via the command line at my box. I really wonder what the end result will be.
[21:56] <mwhudson> lifeless: looking at the code though, i wonder if upgrading any stacked branch would work, never mind the format problems :/.
[21:56] <mwhudson> timour: i don't think there will be any conflict
[21:57] <timour> mwhudson, ok, thanks for the help!
[21:57] <lifeless> :(
[21:58] <barry> i'm trying to get to my ppas through the lp api.  i seem to be able to get to one of them, but not the other.  that one gives a 404.  any ideas why?
[22:00] <barry> ah, nm.  positional argument fubar
[22:03] <lifeless> heh
[23:01] <mwhudson> timour: seems the upgrade worked, although the page isn't updated
[23:01] <mwhudson> timour: probably if you push a new revision up it will sort itself out
[23:02] <timour> mwhudson, yes, it's done, but I have nothing to push. I'll have to figure out some meaningful change.
[23:02] <mwhudson> timour: you could probably uncommit the most recent revision then push it again
[23:03] <timour> mwhudson, ok, will try that, thx.
[23:12] <timour> mwhudson, I merged from another branch and pushed. Let's see what happens. Thanks for the help! Time to sleep.
[23:13] <timour> mwhudson, it seems it worked this time.
[23:13] <mwhudson> timour: hooray
[23:13] <timour> :)
[23:32] <mtaylor> umm... I just got a key error with my ppa
[23:32] <mtaylor> did something change with signing keys?
[23:32] <mtaylor> The following signatures were invalid: BADSIG 4FEC45DD06899068 Launchpad PPA for Drizzle-developers
[23:32] <mtaylor> or rather:
[23:32] <mtaylor> W: A error occurred during the signature verification. The repository is not updated and the previous index files will be used.GPG error: http://ppa.launchpad.net lucid Release: The following signatures were invalid: BADSIG 4FEC45DD06899068 Launchpad PPA for Drizzle-developers
[23:34] <thumper> mtaylor: we added the user code to check if it is you :)
[23:34] <thumper> mtaylor: launchpad now officially hates you
[23:34] <mtaylor> thumper: awesome
[23:34] <thumper> mtaylor: but no idea sorry
[23:34] <mtaylor> thumper: gah
[23:34] <mtaylor> thumper: it _was_ working earlier today
[23:34] <thumper> I don't know of any changes
[23:35] <thumper> not to that part anyway
[23:35] <mtaylor> so it's sort of disturbing for it to just, you know, not
[23:35] <wgrant> mtaylor: You're not behind an awesome transparent proxy? Which PPA URL are you using?
[23:35] <wgrant> It hasn't changed lately.
[23:35] <mtaylor> wgrant: W: Failed to fetch http://ppa.launchpad.net/drizzle-developers/ppa/ubuntu/dists/lucid/Release
[23:35] <mtaylor> wgrant: deb http://ppa.launchpad.net/drizzle-developers/ppa/ubuntu lucid main
[23:35] <mtaylor> wgrant: I added it a while ago with add-apt-repository and I use it all the time
[23:36] <mtaylor> wgrant: and no - no proxy or any sort
[23:36] <soren> mtaylor: Works for me?
[23:36] <mtaylor> soren: gah
[23:36] <wgrant> Yeah, it's fine here too.
[23:36] <mtaylor> but did you guys already have keys associated with that PPA installed?
[23:37] <wgrant> I didn't.
[23:37] <soren> mtaylor: No, just did it for you now.
[23:37] <soren> wget -q -O - http://ppa.launchpad.net/drizzle-developers/ppa/ubuntu/dists/lucid/Release | md5sum
[23:37] <soren> 32b3a6b4571f915be2a68b86e009879a  -
[23:37] <soren> wget -q -O - http://ppa.launchpad.net/drizzle-developers/ppa/ubuntu/dists/lucid/Release.gpg | md5sum
[23:37] <soren> 0c4c8bed3a21ad3d96065c64d3a892c5  -
[23:37] <soren> You?
[23:37] <mtaylor> soren: the same
[23:37] <wgrant> mtaylor: If we had different keys, yours would complain about a missing key, not a bad sig.
[23:37] <mtaylor> ah
[23:38] <mtaylor> wgrant: ok. I just did an update from a different lucid machine that already had it and that one worked fine... so now - is my laptop just hosed
[23:38]  * mtaylor cries
[23:38] <wgrant> Eep.
[23:39] <soren> mtaylor: If you download the two and run "gpg --verify Release.gpg Release"... What then?
[23:40] <soren> Happy?
[23:40] <soren> Not so happy?
[23:40] <mtaylor> soren: Good signature from "Launchpad PPA for Drizzle-developers"
[23:40] <soren> "yay"
[23:41] <mtaylor> WEIRD
[23:41] <soren> "apt-get update" some more? :)
[23:42] <mtaylor> soren: I keep trying it


[03:05] <FloridaBSD> I think it would be nice if we could start partnering with the engineering and coputerscience deaprtments of certian wellknown universities and jinor colleges
[09:36] <BHSPitLappy> somehow I doubt that guy would get accepted into any "jinor colleges"
[23:14] <johnc4510-laptop> New UWN issue is out: https://wiki.ubuntu.com/UbuntuWeeklyNewsletter/Issue116
[23:14] <johnc4510-laptop> New UWN issue is out: https://wiki.ubuntu.com/UbuntuWeeklyNewsletter/Issue116
[23:14] <johnc4510-laptop> slipped    sorry


 Ubuntu is nice :)
[17:00] <Cantide> i can't wait for it actually 'o'
[17:47] <zeref_debian> hmmm
[18:57] <magespawn> good evening all
[18:58] <Cantide> evening~
[18:59] <nuvolari> o/ hello's
[18:59] <nuvolari> Maaz: seen kilos
[18:59] <Maaz> nuvolari: kilos was last seen 10 hours, 2 minutes and 44 seconds ago in #ubuntu-za on freenode [2013-04-03 01:57:14 PDT], and has been offline on freenode since 2013-04-03 02:12:35 PDT
[19:00] <magespawn> wow that's long ago for Kilos
[19:01] <nuvolari> yeah :-/
[19:01] <nuvolari> howdy magespawn
[19:01] <magespawn> hey nuvolari Cantide
[19:17] <Cantide> wb Kilos
[19:17] <Kilos> hi superfly magespawn inetpro and others
[19:17] <Cantide> nuvolari missed you
[19:17]  * Cantide hides
[19:17] <Kilos> hiya cantide
[19:17] <Kilos> ty
[19:17] <Cantide> :)
[19:18] <Kilos> aw hi nuvolari
[19:19] <Kilos> been busy, resting and trying to work out how to not use first 20g of a drive and still have a working os
[19:20] <superfly> hi Kilos
[19:20] <Kilos> Maaz, coffee on
[19:20]  * Maaz starts grinding coffee
[19:20] <Cantide> 20 GB just for OS ? 'o'
[19:20] <Kilos> Maaz, coffee for all
[19:20] <Maaz> Come on ya buncha geeks. Rock up with your mugs with the correct amount of sugar added already
[19:20] <magespawn> hey Kilos superfly
[19:21] <Kilos> no the drive was showing disk sleep all the time, so im guessing its where my /root was so im not using the first 20g
[19:21] <Cantide> ahhh
[19:21] <Kilos> so far so good
[19:21] <Cantide> sounds like you need a new drive :/
[19:21] <Kilos> sssshhh
[19:22] <Cantide> Maaz, please build me a time machine so that I can get 14.04 now :S
[19:22] <Kilos> cant throw 160g away so easy
[19:22] <Maaz> Cantide: I'll remember that
[19:22] <nuvolari> ah! hi oom Kilos :D
[19:22] <Cantide> haha
[19:22] <nuvolari> hoe gaan dit oom?
[19:22] <Kilos> goed dankie en jy nuvolari ?
[19:22] <nuvolari> kan nie kla nie dankie oom!
[19:22] <Cantide> i'm actually going to go to bed :p
[19:22] <Cantide> good night everyone~
[19:23] <nuvolari> night Cantide
[19:23] <Kilos> night Cantide
[19:23] <Kilos> sleep tight
[19:23] <Cantide> '-'/
[19:23] <nuvolari> jinne, oom sal ons laat worrie
[19:23] <Kilos> skuus man , dit was nie aspris nie
[19:24] <Maaz> Coffee's ready for Kilos!
[19:24] <Kilos> Maaz, ty
[19:24] <Maaz> You are welcome Kilos
[19:26] <nuvolari> hhr
[19:26] <nuvolari> die interwebs is weer op hul eie mission
[19:26] <Kilos> ai
[19:27] <Kilos> where is goosie
[19:32] <Kilos> gedink ek moet net kom oog wys en nag se nuvolari
[19:32] <Kilos> night all , sleep tight
[19:32] <nuvolari> right
[19:32] <nuvolari> so woerts warts
[19:33] <nuvolari> night oom Kilos
[19:33] <Kilos> lol
[19:33] <nuvolari> lekker slaap
[19:33] <Kilos> sal more hier wees
[19:33] <Kilos> dankie seun , jy ook
[19:50] <nuvolari> o/ I'm out
[20:20] <magespawn> good night all


[00:16] <jason_> SpamapS, I'm getting an invalid ssh key now -- I did juju status, and it told me the key had been changed (from my many reinstalls no doubt) and asked to accept or no -- I said no, meaning to cancel out and delete the known hosts file and retry, and now it's Invalid SSH key each time
[00:24] <jason_> ok, I copied all my .ssh files from the client I'd been working on to the server -- seems to have gotten me past that bit
[00:30] <jason_> juju status completed -- looks like my first system is in place
[00:52] <hazmat> jason_, woot!
[01:08] <_mup_> juju/go-store r18 committed by<EMAIL_ADDRESS>[01:08] <_mup_> Implemented URL.WithRevision.
[01:11] <jason_> hazmat, mysql deploy success, too...
[01:26] <niemeyer> jason_: ho ho
[03:58] <_mup_> juju/go-store r19 committed by<EMAIL_ADDRESS>[03:58] <_mup_> New store package with AddCharm and OpenCharm interface.
[03:58] <_mup_> The interface to the package is trivial, but internally it actually
[03:58] <_mup_> handles all the necessary logic for concurrent runs of the algorithm,
[03:58] <_mup_> including mongo-based atomic locks with expiration, multi-URL synchronous
[03:58] <_mup_> revision bumping as described in the charm specification, GridFS-based
[03:58] <_mup_> memory-friendly uploading for large files, and ponies too.
[03:58] <_mup_> Lacks documentation and sha256 handling, though.. but I need some sleep.
[04:11] <niemeyer> Night all
[06:04] <_mup_> juju/expose-retry r402 committed by<EMAIL_ADDRESS>[06:04] <_mup_> Support retrying port mgmt ops in periodic machine check
[08:21] <_mup_> Bug #872164 was filed: [Oneiric] Cannot deply services - store.juju.ubuntu.com not found <juju:New> < https://launchpad.net/bugs/872164 >
[08:48] <jamespage> morning - I took the liberty of pointing the bug reporter for bug 872164 in the right direction and marked the bug as invalid
[08:48] <_mup_> Bug #872164: [Oneiric] Cannot deply services - store.juju.ubuntu.com not found <juju:Invalid> < https://launchpad.net/bugs/872164 >
[08:52] <fwereade_> thanks jamespage, I just saw, much better response than mine
[08:52] <jamespage> fwereade_, np
[09:37] <jamespage> I think I must be missing something: should the stop hook be called when a unit is removed from a service using remove-unit?
[11:19] <rog> where can i find documentation for txaws?
[11:19] <rog> oops, LMGTFY
[12:07] <hazmat> good morning
[12:09] <hazmat> fwereade_, the docs still look out of date.. https://juju.ubuntu.com/docs/user-tutorial.html#deploying-service-units
[12:09] <hazmat> i think jimbaker mentioned yesterday they weren't regenerating
[12:15] <hazmat> jamespage, on bug 871966 when you say local juju environment you mean a local provider?
[12:15] <_mup_> Bug #871966: FQDN written to /etc/hosts causes problems for clustering systems <cloud-init (Ubuntu):Confirmed> <cassandra (juju Charms Collection):New> < https://launchpad.net/bugs/871966 >
[12:17] <hazmat> jamespage, the stop hook is not called
[12:18] <hazmat> jamespage, pretty much everything that deals with remove/destroy works one level up from the supervisor of the thing being killed
[12:18] <hazmat> with the notion that even if the thing is AWOL, the action will happen
[12:20] <rog> hazmat: hiya
[12:20] <hazmat> rog, txaws is pretty much UTSL for most questions imo
[12:22] <rog> hazmat: yeah, i discovered that. thanks.
[12:22] <rog> foundations of sand :-)
[12:24] <hazmat> rog, not really.. its well tested. but yeah.. its a consequence of using twisted, vs using the standard python library for aws (boto )
[12:24] <rog> uh huh
[12:25] <hazmat> hmm.. interesting
[12:31] <jamespage> hazmat: the comment on bug 871966 does refer to the local provider - but that provides an IP address for private-address anyway
[12:31] <_mup_> Bug #871966: FQDN written to /etc/hosts causes problems for clustering systems <cloud-init (Ubuntu):Confirmed> <cassandra (juju Charms Collection):New> < https://launchpad.net/bugs/871966 >
[12:31] <hazmat> jamespage, yup and private-address==public-address there
[12:31] <hazmat> and it shows up in juju status
[12:32] <jamespage> hazmat: I now have something that works with the local provider, and on ec2 and openstack
[12:32] <hazmat> jamespage, nice
[12:32] <hazmat> jamespage, comments about the local provider probably aren't relevant on a cloud-init bug, since the local provider doesn't use cloud-init.. fwiw
[12:33] <jamespage> hazmat: they more referred to the fix for cassandra
[12:33] <hazmat> ah.. ic. its linked
[12:33] <jamespage> yep
[12:36] <jamespage> hazmat: with regards to units leaving a service/not calling stop I was trying to figure out the best way to remove a node from a cassandra cluster
[12:36] <jamespage> because the node does not get shutdown, it remains in the ring
[12:45] <robbiew> rog: ping
[12:46] <rog> robbiew: pong
[12:46] <robbiew> rog: have you registered for UDS?
[12:46] <rog> robbiew: i think so.... but i'll just check
[12:47] <rog> robbiew: yes, i have
[12:47] <robbiew> rog: -> http://uds.ubuntu.com/register/ :)
[12:47] <rog> robbiew: i did it on 15th Sep...
[12:47] <rog> and flights all booked too
[12:48] <robbiew> rog: hmm, okay.  I'll talk to our admins then, thx
[12:49] <rog> robbiew: at any rate, i've got a confirmatiom email from marianna
[12:49] <rog> robbiew: i'll just check the web site directly
[12:50] <robbiew> rog: ah, cool
[12:50] <robbiew> nevermind then
[12:50] <robbiew> :)
[12:53] <rog> robbiew: ah, maybe i didn't register on the linaro web site. i think i only did the UDS registration.
[12:55] <hazmat> jamespage, hmm
[12:55] <hazmat> jamespage, yeah.. i guess we really should be calling stop on units
[12:56] <jamespage> hazmat: I need to deal with two scenarios - one where its a controlled removal
[12:56] <jamespage> and one where the node goes AWOL
[12:56] <hazmat> jamespage, pls file a bug
[12:56] <hazmat> i can look at that today
[12:56] <jamespage> hazmat: ack - doing now
[12:57] <hazmat> for stopping a machine its almost irrelevant, since we shutdown the machine, but for a unit if we don't call stop, there isn't any thing to keep it from continuing to run
[12:57] <hazmat> at least till all units are containers
[12:57] <hazmat> and then the container is killed
[12:57] <robbiew> rog: UDS is all you need ;0
[12:57] <robbiew> ;)
[12:58] <rog> robbiew: ok, i'll ignore the FAQ then...
[12:58] <hazmat> but we really can't do the latter on ec2, till we figure out some magical networking solution, or stop doing dynamic port management
[13:00] <hazmat> unless we assume a single unit per machine in ec2 and do a targeted forward rule per exposed port
[13:04] <_mup_> Bug #872264 was filed: stop hook does not fire when units removed from service <juju:New> < https://launchpad.net/bugs/872264 >
[13:05] <jamespage> hazmat: ^^
[13:05] <jamespage> I tried to document the two challenges I have specifically with the cassandra charm
[13:05] <hazmat> jamespage, thanks
[13:06] <jamespage> I guess they may apply to other charms that have similar ring storage methods
[13:07] <hazmat> jamespage, so on 2) and 1) the other units should both detect the removal
[13:07] <jamespage> hazmat: yes - they do
[13:07] <rog> just realised that "canonical/linaro employee" means "(canonical AND linaro) employee" not "(canonical OR linaro) employee"...
[13:07] <rog> doh
[13:11] <jamespage> hazmat: and I could use the hook on the remaining nodes to deal with both situations
[13:11] <jamespage> I would need to write it such that only one node completes the action
[13:12]  * jamespage thinks about that one
[13:15]  * SpamapS awakens.. far too early
[13:17] <niemeyer> Good morning all
[13:18] <rog> niemeyer: yo!
[13:18] <SpamapS> jamespage: I think there's another bug asking for similar functionality..
[13:19] <SpamapS> jamespage: bug 862422
[13:19] <_mup_> Bug #862422: Provide a way for services to protect units during dangerous operations <juju:Confirmed> < https://launchpad.net/bugs/862422 >
[13:20] <SpamapS> jamespage: swift is a similar ring service and has times where adding or removing is a bad idea
[13:21] <jamespage> SpamapS, agreed - it looks very similar
[13:27] <SpamapS> Does seem like the stop hook should handle this
[13:27] <jamespage> SpamapS: it would do for controlled removal
[13:28] <SpamapS> jamespage: not sure I understand the AWOL case
[13:28] <jamespage> SpamapS, thats more of a housekeeping case
[13:29] <jamespage> in cassandra if you never moved entries for nodes that had gone away ('Down' status) it gets very crufty
[13:29] <jamespage> also you want to ensure that loadbalancing etc.. get re-adjusted as the node won't be coming back
[13:29] <hazmat> jamespage, but don't you get a departed event at all other nodes when one goes AWOL?
[13:29] <jamespage> SpamapS, yes
[13:29] <jamespage> sorry - I mean hazmat
[13:30]  * hazmat checks the bug report
[13:30] <SpamapS> jamespage: yeah that should be detected in the peer relations
[13:31] <SpamapS> cassandra has a prescribed procedure for removing a dead node from the ring
[13:31] <rog> niemeyer: i'm porting the ec2 launch code and i'm not sure how goamz's AuthorizeSecurityGroup is supposed to work the way it's being used in the python code. here's a comparison: http://paste.ubuntu.com/706060/
[13:31] <jamespage> SpamapS, it does
[13:32] <SpamapS> so on departed.. you would run that procedure for the departed unit
[13:32] <hazmat> jamespage, so in the case of 1) the desire is for the actual termination of the unit to hang till the stop (which is potentially a long running op) completes?
[13:32] <hazmat> and of course to execute stop as part of 1
[13:32] <jamespage> hazmat: ideally yes
[13:33] <jamespage> SpamapS: what information is provided when the -departed hook fires about the remote service unit?
[13:33] <hazmat> jamespage, doesn't the same problem exist in reverse when adding units.. as i recall for cassandra (might be outdated), your supposed to only add a single unit at a time
[13:33] <niemeyer> rog: Looks like there's a protocol setting missing
[13:33] <hazmat> jamespage, just the unit name and that it departed
[13:33] <niemeyer> rog: Check out the docs and the implementation
[13:34] <SpamapS> hazmat: +1 for that, let stop be proactive about locally stored data
[13:34] <hazmat> SpamapS, niemeyer g'morning
[13:34] <rog> niemeyer: the python code doesn't seem to set a proto - i was just checking that it wasn't an obvious bug
[13:34]  * hazmat just up the ante on his war against rodents, bring in the exterminator
[13:34]  * SpamapS wishes the time would change, its pitch black here in LA at 6:30am :-P
[13:34] <niemeyer> rog: Maybe it has a default?
[13:34] <SpamapS> we're porting the ec2 launch code?
[13:35] <jamespage> hazmat, there is a restriction on adding units - N+N rather than N+1
[13:35] <rog> niemeyer: it seems to have two distinct modes of operation
[13:35] <rog> there's no obvious default in the python code
[13:35] <rog> i'll recheck though
[13:35] <niemeyer> rog: They're both backed by the same implementation
[13:35] <niemeyer> rog: The same API
[13:35] <niemeyer> rog: If one of them is failing, the call is different.. just figure how it's different and you'll understand the problem
[13:36] <SpamapS> hazmat: bug 862422 has a case where swift requires that nodes wait to be added until rebalance is done
[13:36] <_mup_> Bug #862422: Provide a way for services to protect units during dangerous operations <juju:Confirmed> < https://launchpad.net/bugs/862422 >
[13:37] <jamespage> SpamapS, hazmat: Cassandra has a similar requirement
[13:37] <hazmat> hmm
[13:37] <SpamapS> Its not that hard on the add-unit case though
[13:37] <SpamapS> you can error out the joined event
[13:37] <hazmat> they can't really scan for a rebalance attribute since its being set by the same hook that's doing it
[13:37] <hazmat> and the hook values are only flushed at the end of the hook
[13:37] <SpamapS> and admins will just have to resolve --retry
[13:38] <SpamapS> hazmat: the services should protect themselves
[13:38] <SpamapS> hazmat: there's somewhere that an admin has to look to see if a re-balance is going on
[13:38] <SpamapS> thats where the hook should look
[13:38] <hazmat> SpamapS, there isn't any service level logic.. atm.. its got to be what the units can coordinate among themselves
[13:39] <jamespage> so - just to flip back to my -departed thinking
[13:39] <jamespage> ATM I will need to a) detect which node needs to be removed from the ring
[13:39] <SpamapS> hazmat: yeah, I don't think preventing it is juju's problems. Handling failures gracefully should be all it needs to do.
[13:40] <jamespage> and b) elect which of the remaining units is going to execute the removal
[13:40] <jamespage> in the -departed hook
[13:40] <SpamapS> Though this does go back to the --wait argument where as an admin I'd like to get feedback from the command's intended actions.
[13:41] <hazmat> jamespage, so a leader election/detection cli api for hooks
[13:41] <jcastro> Does anyone want to volunteer to do a juju session for ubuntu openweek? https://wiki.ubuntu.com/UbuntuOpenWeek
[13:42] <rog> niemeyer: hmm, it looks like the python code is using an undocumented feature of aws.
[13:42] <jamespage> hazmat, that would be nice
[13:42] <jamespage> as it would prevent some fragile hack in the charm hook
[13:42] <hazmat> rog, that api has several different spellings, they are documented
[13:43] <jamespage> I'm doing something similar at the moment for unit bootstrapping - which it not 100% reliable
[13:43] <jamespage> when units join the peer relation
[13:43] <SpamapS> jcastro: I'm down for it.
[13:43] <jcastro> SpamapS: can you claim a block please?
[13:44] <jcastro> SpamapS: I'll do it with you if you want
[13:44] <SpamapS> Yeah at least be there to help me with the bot. ;)
[13:44] <hazmat> rog, txaws is a poor reference impl to look at.. https://github.com/boto/boto/blob/master/boto/ec2/connection.py#L1917
[13:44] <hazmat> is much better at api coverage and docs, notice right above that impl there is support for a deprecated mechanism with slightly different spelling
[13:45] <lynxman> hazmat: SpamapS: got the juju macports done and working, just a versioning question, let me paste here the versions of the python packages I'm using and let me know which ones would you deem as "need upgrading"
[13:46] <rog> hazmat: the name "SourceSecurityGroupName" is used as a parameter. i'd have thought that should be documented in http://docs.amazonwebservices.com/AWSEC2/latest/APIReference/index.html?ApiReference-query-AuthorizeSecurityGroupIngress.html
[13:46] <rog> given that seems to be the entry point.
[13:47] <lynxman> argparse (1.2.1), zookeeper (3.3.0), python-regex (0.8.0), python-txaws (0.2), pydot (1.0.25), python-argparse (1.2.1)
[13:49] <lynxman> hazmat: maybe we should upgrade txaws?
[13:51] <rog> niemeyer: looks like a new entry point is warranted. perhaps the original call would be better named AuthorizeSecurityGroupIP. hmm.
[13:51] <hazmat> rog its quite possible txaws is not targeting the latestt api
[13:52] <hazmat> rog, actually highly likely given its lack of dev
[13:52] <rog> hazmat: txaws has the call. as does boto. but the AWS documentation doesn't mention that variant AFAICS
[13:54] <rog> it looks like all the language APIs have that variant. do you know what it's actually doing? authorizing one group with the privileges of another?
[13:54] <rog> that would be my guess, but it would be nice to know for sure, so that i can choose a good name.
[13:56] <hazmat> rog, aws supports both because they have a versioned api, boto has separate implementations for each version one marked deprecated.
[13:56] <hazmat> rog, it is documented, but not under the latest version of the api docs which document the latest
[13:57] <jcastro> SpamapS: which slot do you want?
[13:57] <lynxman> hazmat: so what do you reckon :)
[13:57] <rog> hazmat: ah, so... we have to ask: what's the equivalent of that old call in the new API?
[13:58] <rog> i'll try and find the old docs
[13:58] <hazmat> lynxman, so txaws doesn't have a release with the openstack fixes atm
[13:59] <hazmat> and i should probably push out a new version of txzookeeper
[13:59] <hazmat> lynxman, give me a moment, i'll cut releases for both
[13:59] <lynxman> hazmat: cool :)
[13:59] <hazmat> lynxman, besides that.. what's python-regex?
[13:59] <hazmat> lynxman, we use the builtin re module not a third party lib
[14:00] <hazmat> unless a dep needs it like pydot..
[14:00] <hazmat> rog, it should be pretty clear from context how to translate
[14:02] <lynxman> hazmat: I can drop it as a dependency then, pydot has its own :)
[14:03] <rog> hazmat: perhaps. this page talks about a "user/group pair permission", but perhaps that's just code for "allow all IP access". http://docs.amazonwebservices.com/AmazonEC2/dg/2007-01-03/ApiReference-Query-AuthorizeSecurityGroupIngress.html
[14:04] <hazmat> lynxman, so python-txzookeeper 0.8.0 is needed as well
[14:05] <hazmat> lynxman, and zookeeper 3.3.3 .. there are definitely bug fixes in the py bindings we need
[14:05] <lynxman> hazmat: alright, I'll upgrade both then, ty
[14:06] <hazmat> lynxman, np.. the latest pypi release for txzookeper looks good, off to push out a 0.2.1 txaws release
[14:06] <lynxman> hazmat: lovely, thanks! :D
[14:17] <rog> tcp port numbers are 16 bit even with IPv6, right?
[14:18]  * niemeyer looks at rog with the eye
[14:19] <rog> ok, ok, i should know that.
[14:36] <SpamapS> jcastro: sorry, family stuff, I'll grab one in the next 2 hrs
[14:41] <rog> niemeyer: just checking: have you already written some Go code to parse environments.yaml?
[14:41] <niemeyer> rog: No, that was the first bit I suggested you could start with
[14:42] <rog> ok, cool
[14:42] <rog> (BTW the instance starting and group set up code is all working now)
[14:42] <niemeyer> rog: Please follow the existing convention in the charm package
[14:42] <niemeyer> rog: Wow, neat!
[14:42] <niemeyer> rog: How're you testing it?
[14:43] <rog> niemeyer: it's just a stub file currently, no tests written so far
[14:43] <niemeyer> rog: Heh
[14:43] <niemeyer> rog: So there's nothing..
[14:43] <rog> niemeyer: just running it and going to the aws console to check
[14:43] <niemeyer> rog: :)
[14:43] <niemeyer> rog: Please write tests with the logic, rather than retrofitting them
[14:44] <niemeyer> rog: We should follow a similar model to what was done with goamz itself
[14:44] <niemeyer> rog: Rather than the mocking craziness we have in the Python side
[14:44] <rog> niemeyer: yes, tests are the next thing i'm putting in. the code isn't even in a package yet.
[14:45] <niemeyer> rog: Ok, it's a spike then
[14:45] <rog> niemeyer: a spike?
[14:45] <niemeyer> rog: yeah, a  temporary hack to get a feeling of the problem
[14:45] <rog> niemeyer: yeah, although i've ported a lot of the logic from the original python, so it should be trivial to do it right.
[14:46] <rog> niemeyer: this is all i've got so far: http://paste.ubuntu.com/706139/
[14:48] <niemeyer> rog: Nice
[14:50] <hazmat> lynxman, latest txaws release @ http://launchpad.net/txaws/trunk/0.2/+download/txAWS-0.2.1.tar.gz
[14:50] <lynxman> hazmat: lovely, thanks :)
[14:50] <rog> niemeyer: what's the best approach to testing with ec2? actually interact with ec2 directly?
[14:53] <niemeyer> rog: No, we can follow a similar model from goamz
[14:53] <rog> ok, i'll have a look.
[14:55] <rog> niemeyer: BTW is this the only spec for the environment yaml? https://juju.ubuntu.com/docs/getting-started.html#configuring-your-environment
[14:55] <niemeyer> rog: Please read the Python code
[14:55] <rog> ok
[15:05] <lynxman> hazmat: new ports submitted, contacted one of the maintainers and it's *possible* that juju will be in the archive by next week
[15:07] <hazmat`> lynxman, sweet!
[15:26] <SpamapS> lynxman: is there an artifact somewhere where I can test and provide positive feedback to the maintainers?
[15:27] <lynxman> SpamapS: I can send you my portindex branch if you want
[15:45] <jimbaker> SpamapS, this branch should hopefully fix the problem you saw on openstack with expose failing: lp:~jimbaker/juju/expose-retry
[15:53] <SpamapS> Hah, I love this code
[15:53] <SpamapS> self.mocker.call(simulate_random_failure)
[15:53] <SpamapS> :)
[15:54] <SpamapS> jimbaker: indeed that should retry those ops. There are many others.. I think we just have to get defensive about txaws
[15:59]  * hazmat lunches
[16:00] <niemeyer> I'm off to lunch too.
[16:06] <jimbaker> SpamapS, :). we need to be defensive about txaws because it needs work and it necessarily deals with bad stuff. in general, txaws will fail early, if it has a bad payload it can't parse
[16:07] <jimbaker> for commands like destroy-environment that can be repeated, this may be ok. for agents, we need to do retries
[16:10] <jimbaker> i'm pretty certain that the provisioning agent retry mechanism (ignoring that it's a SPOF for now) seems to robust, so long as we have errbacks defined such that stuff doesn't just stop. in the case of expose, the only place where txaws can be called is that one method (open_close_ports_on_machine), so trapping there and then using the existing resync mechanism for retries would seem to suffice
[16:11] <SpamapS> Are there any operations that the provisioning agent does w/ txaws where it shouldn't retry on error?
[16:12] <SpamapS> expose/unexpose was just the most common fail we had
[16:12] <SpamapS> there were others
[16:12] <SpamapS> any time listing instances returned empty ... things were likely to just grind to a halt
[16:14] <jimbaker> SpamapS, i suspect the problem with that is seen here: http://pastebin.ubuntu.com/706206/, specifically lines 17-21
[16:15] <jimbaker> i need to check that get_machines will always raise a ProviderError if it fails
[16:16] <jimbaker> SpamapS, no, it only catches EC2Error, but txaws will raise other errors
[16:17] <SpamapS> jimbaker: yeah seems like we should be able to trust our internal libraries to always raise only ProviderError. :)
[16:18] <jimbaker> SpamapS, that's definitely not the convention we have
[16:18] <jimbaker> no catchalls
[16:18] <SpamapS> seems like catchalls at external libraries would be a good idea, but not for internal ones.
[16:18] <jimbaker> except perhaps in some twisted code where we use an errback setup, and then that does catch everything
[16:20] <jimbaker> SpamapS, yeah, i don't know. i think i can defend the existing mechanism by stating that for nonagent code, it's better to failfast, so any unknown errors bubbling up is fine
[16:22] <jimbaker> SpamapS, but if i look at periodic_machine_check, it does the right thing: it always reschedules itself, even if there's an error (equiv to inlineCallbacks with a finally)
[16:23] <jimbaker> SpamapS, so it should be resilient. and of course, if txaws is bad here, vs just getting an occasional bad payload, there's nothing that can be done anyway except to repeatedly log the problem
[16:26] <SpamapS> jimbaker: thats really what I'm wondering.. I don't know of any action the provisioning agent takes that shouldn't just be retried over and over. I will say that we need a better way than debug-log to track provisioning operations.
[16:28] <jimbaker> SpamapS, i think this would be helpful, bug 769120
[16:28] <_mup_> Bug #769120: Ensemble status shouldn't report dead units based soley on state, but also on presence. <juju:New> < https://launchpad.net/bugs/769120 >
[16:32] <hazmat> niemeyer, the doc builds on juju docs have been broken for a while.. their still referencing old ways of deploying
[16:33] <jimbaker> SpamapS, ok, i think i see one bug here however: watch_machine_changes is a watch, and it calls process_machines. so this watch would stop working if process_machines fails because of some random exception from txaws
[16:33] <niemeyer> hazmat: Can you please raise that up in #is?
[16:35] <jimbaker> SpamapS, we would still see the resync from the periodic_machine_check, but the provisioning agent wouldn't respond to changes to ZK as they happen
[16:35] <SpamapS> jimbaker: exactly!
[16:35] <jimbaker> SpamapS, cool, glad to see your evidence corresponds to what i'm seeing here :)
[16:35] <SpamapS> jimbaker: did we ever open an actual bug for this?
[16:36] <SpamapS> I suppose you can just lpad it :)
[16:37] <jimbaker> SpamapS, i'll just open it conventionally, since i don't have a branch in place to fix it
[16:37] <hazmat> niemeyer, done.. is there any one i should ping about it?
[16:38] <niemeyer> hazmat: Hmm.. #is?  Who did you ping if you're wondering about who to ping?
[16:38] <hazmat> niemeyer, i just put the message about the problem on #is.. just wondering if i should bring it to a particular person's attention on #is
[16:39] <niemeyer> hazmat: Ah, gotcha
[16:39] <niemeyer> hazmat: No, I'd just wait to see if someone there is able to help
[16:39] <niemeyer> hazmat: Otherwise mail rt
[16:39] <hazmat> niemeyer, k, thanks
[16:54] <_mup_> juju/go-store r20 committed by<EMAIL_ADDRESS>[16:54] <_mup_> Introduced revision key tracking so that we can detect whether a
[16:54] <_mup_> charm update is already the current tip across all requested URLs
[16:54] <_mup_> or not. If at least one of the URLs are out-of-date, the update
[16:54] <_mup_> will proceed and bump a revision on all of them.
[17:00] <rog> i'm off for the day. see y'all tomorrow.
[17:03] <niemeyer> rog: Cheers!
[17:05] <_mup_> Bug #872378 was filed: Provisioning agent stops watching machine changes in ZK <juju:New> < https://launchpad.net/bugs/872378 >
[17:05] <jimbaker> SpamapS, i just filed bug 872378
[17:05] <_mup_> Bug #872378: Provisioning agent stops watching machine changes in ZK <juju:New> < https://launchpad.net/bugs/872378 >
[17:05] <SpamapS> jimbaker: thanks, will confirm and mark High
[17:05] <jimbaker> SpamapS, thanks, just what i was going to ask :)
[17:06] <SpamapS> oh you did that :)
[17:06] <jimbaker> i did the high part, you can still confirm it however
[17:06] <SpamapS> need to raise a txaws bug too
[17:06] <jimbaker> i'll get the bug dance better next time
[17:06] <SpamapS> well I am pretty religious about not confirming my own bugs :)
[17:07] <jimbaker> SpamapS, it's an interesting question about txaws, but given that it's a closely related project, worth seeing their philosophy here - do they handle bad payloads or not?
[17:07] <SpamapS> no
[17:07] <SpamapS> the project expects its AWS partner to be well behaved
[17:08] <SpamapS> so there's also a nova bug to raise
[17:08] <SpamapS> as nova shouldn't be returning empty ever
[17:08] <SpamapS> heh.. we should probably have a little triage party to clean up txaws's bug list.
[17:08] <jimbaker> got it. but regardless we would still expect to see TimeoutError, so there's some class of errors txaws will likely not handle
[17:08] <SpamapS> 34 new, 72 open, 3 high..
[17:51] <_mup_> juju/go-store r21 committed by<EMAIL_ADDRESS>[17:51] <_mup_> Track sha256 and store next to the charm information so we can answer
[17:51] <_mup_> related API requests in the future.
[18:01] <_mup_> juju/go-store r22 committed by<EMAIL_ADDRESS>[18:01] <_mup_> Copied log.go from personal project (mgo).
[18:44] <jcastro> lynxman: heya, any update on the macports thing?
[18:51] <jcastro> hazmat: hey is there an easy way to tell the local provider to use my existing apt cache instead of installing all this apt-cacher-ng business?
[18:52] <hazmat> jcastro, i think he mentioned updated the portfile, he's going to ping one of the maintainers, with luck soon
[18:53] <hazmat> jcastro, sadly no
[18:55] <hazmat> jcastro, is the initial download a problem?
[18:55] <jcastro> yeah, this close to release the mirrors are hammered, I'll suffer and find something else to do
[19:05] <m_3> SpamapS: did you mention you had pending MW charm changes?
[19:06] <SpamapS> m_3: everything I had is in lp:charm/mediawiki
[19:07] <m_3> SpamapS: cool thanks
[19:09] <_mup_> juju/go-store r23 committed by<EMAIL_ADDRESS>[19:09] <_mup_> Added info/debug logging across the charm storage operations.
[19:18] <hazmat> jamespage, ping
[19:19] <hazmat> jamespage, i'm wondering how problematic it is to always kill the unit's processes on removal instead of a controlled termination via stop
[19:20] <SpamapS> hazmat: stop needs to be able to *cancel* the removal
[19:21] <hazmat> SpamapS, there's not much distinguishing a unit removal to a service removal at that level
[19:21] <SpamapS> It would be awesome if charms could prevent data loss without a --force flag by simply refusing to stop the service while it is vulnerable.
[19:21] <hazmat> and units overriding the user express commands..
[19:22] <hazmat> hmm
[19:22] <SpamapS> is this only happening on destroy-service, not on remove-unit ?
[19:22] <SpamapS> I do kind of think destroy-* should be more heavy handed
[19:22] <hazmat> SpamapS, it would happen on either one, the mechanics are the same atm
[19:23] <hazmat> SpamapS, how does the service know if its redundant or not?
[19:23] <hazmat> service unit
[19:25] <_mup_> juju/config-get r393 committed by<EMAIL_ADDRESS>[19:25] <_mup_> juju get for service config/schema inspection
[19:27] <SpamapS> hazmat: in the case of any clustered service, it will have some way to determine if removing this node is safe or not.
[19:29] <SpamapS> hazmat: stop would also be a decent place for a single node service to signal some kind of snapshot or backup.
[19:30] <SpamapS> so blocking until its done would be cool
[19:31] <hazmat> SpamapS, the converse question is how to prevent problems with problematic charms, that might for example have a broken stop... or even well meaning ones that go out of control
[19:32] <hazmat> decomissioning a node in cassandra is potentially a fairly long operation afaicr
[19:32] <hazmat> we'll need intermediary states to properly convey status to a ui
[19:32] <hazmat> ie. 'stopping'
[19:32] <hazmat> we only have nouns now.. not verbs
[19:36] <SpamapS> hazmat: --force ?
[19:36] <hazmat> sounds reasonable
[19:37] <SpamapS> hazmat: I see what you mean. Yes it would be cool if we followed upstart's model there and had a goal state, and the in-between states with hooks available for each state.
[19:37] <hazmat> SpamapS, exactly
[19:37] <hazmat> hmm.. well maybe not hooks available for each state, but at least the same re status
[19:37] <hazmat> effectively it would be a hook per verb
[19:38] <SpamapS> stop/running -> stop/hook-stop-running -> (if hook says so, stop/deferred-stop) -> stop/stopping-unit -> oblivion
[19:38] <SpamapS> Like if a hook exits 100 , that means it is running the safe stop in the background
[19:39] <SpamapS> then you can just keep trying to stop it, and getting back 100 until its done decomissioning
[19:39] <SpamapS> and you can still have a short timeout to deal with misbehaving charms
[19:39] <hazmat> i'm going to capture this discussion into the bug