[10:16] <zaki> welcome back Kilos
[10:16] <zaki> How are you?
[10:17] <Kilos> ty zaki hope you are all well
[10:17] <Kilos> im alive still hehe
[10:17] <zaki> yea fine. :)
[10:17] <zaki> great
[10:19] <zaki> pavlushka was talking about you
[10:20] <zaki> it's nice to see you here.
[10:37] <Kilos> ty
[10:48] <Kilos> sorry i have been so scarce lads but big things been happening to me
[10:48] <Kilos> and being in another timezone so far away is rather crazy
[11:10] <zaki> hmmm
[11:31] <zaki> wb RemonShai
[11:32] <RemonShai>  ty zaki
[11:33] <zaki> hmm
[11:35] <RemonShai> how was today...?
[11:35] <zaki> fine
[11:36] <zaki> what about u?
[11:37] <RemonShai> 3fine but busy
[11:37] <zaki> hmm
[12:52] <shanto> zaki: bhai :D
[12:52] <shanto> Asen ?
[12:53] <shanto> Zaki bhai
[12:53] <shanto> zaki: bhai
[12:58] <shanto> QA: coffe on
[12:58] <QA> shanto: Huh?
[12:58] <zaki> hello shanto
[12:58] <zaki> how are you?
[12:58] <shanto> QA coffee on
[12:58]  * QA puts the kettle on
[12:59] <zaki> QA: coffee please
[12:59] <QA> zaki: Yessir
[12:59] <shanto> Ayy bhai
[12:59] <zaki> hmm
[12:59] <shanto> Ami nsab + pavel bhai er shathe asi
[12:59] <shanto> Daffodils et shamne
[13:00] <zaki> wow.
[13:00] <zaki> what are u doing ?
[13:00] <zaki> missing :(
[13:02] <shanto> Meetup
[13:02] <zaki> hmmm
[13:02] <zaki> and what is the topic?
[13:02] <QA> Coffee's ready for shanto and zaki!
[13:02] <zaki> :D
[13:02] <shanto> Fb te pic dibo :D
[13:03] <zaki> hmmm dien
[13:03] <zaki> QA: ty
[13:03] <QA> Only a pleasure zaki
[13:03] <shanto> Its pavlushka, zaki now typing
[13:03] <shanto> Hehe
[13:03] <zaki> lol
[13:03] <zaki> really?
[13:04] <zaki> how can be i sure? :p any code word?  :D
[16:12] <Nahiyan> ok
[16:23] <walrider> QA: tell zaki bhai online ashle ping dien
[16:23] <QA> walrider: Sure, I'll tell zaki on freenode
[16:27] <zaki> hello walrider
[16:27] <zaki> i got disconnected
[16:27] <walrider> zaki bhai
[16:27] <walrider> aktu help lagbe
[16:27] <zaki> tell
[16:28] <walrider> i need this xubuntu 14.04.5 amd46 iso , akhon eta to dhakacom mirror e nai ar iso ta amr urgent lagbe can you help me anyhow to get that as fast as possible ?
[16:29] <zaki> onno mirror e dekhsen?
[16:29] <walrider> onno mirror theke to reguler speed pai
[16:29] <walrider> 150 kbps
[16:29] <walrider> dhakacom e nai iso thakle 4-6 mbps paitam
[16:30] <walrider> apne to isp te asen aktu namai nia HFS e den na bhai
[16:30] <walrider> :(
[16:30] <zaki> i'm in my home right now. :D
[16:30] <walrider> :( ow assa
[16:30] <walrider> ki je kori akhon
[16:30] <walrider> :(
[16:31] <zaki> broadband connection ache na tomar? aste aste namai nao
[16:32] <zaki> japan er mirror ta fast kaj kore jantam
[16:34] <zaki> walrider: got something for you
[16:34] <zaki> are u there?
[16:34] <walrider> ho asi :O
[16:34] <walrider> den dekhi :O
[16:34] <zaki> torent ache na?
[16:35] <walrider> ho ase
[16:35] <zaki> 500 kbps porjonto paisi
[16:35] <walrider> speed reguler thakbe maybe den test kori
[16:35] <zaki> na ami 480 porjonto pailam
[16:35] <walrider> amar reguler speed 1.2kbps  150 pabo max amar jana mone
[16:35] <zaki> http://ftp-stud.hs-esslingen.de/Mirrors/cdimage.ubuntu.com/xubuntu/releases/14.04/release/xubuntu-14.04.5-desktop-amd64.iso.torrent
[16:36] <walrider> oh eta
[16:36] <walrider> eta aktu age delete korsi
[16:36] <zaki> ken?
[16:36] <walrider> 120 kbps max
[16:36] <walrider> jani na bhai bd er kono tracker nai ei torrent file e maybe er karone local peer connect kore na amar mone hoy amon ta
[16:38] <zaki> but ami to valo speed pacchi
[16:38] <zaki> local thakle eito connect korbe
[16:38] <zaki> walrider:
[16:38] <walrider> hoy na onek try korsi age bhai
[16:39] <zaki> oh
[16:39] <walrider> apner real ip na ?
[16:39] <walrider> akhon jei line e asen ?
[16:39] <zaki> na
[16:39] <walrider> port open hoy ?
[16:40] <zaki> hmm
[16:40] <walrider> apner ip ta den kindly ping test kori koto ms dekhi
[16:41] <walrider> global ip ta den
[16:41] <zaki> i'm using wifi
[16:41] <walrider> google search koren my ip
[16:41] <walrider> then ip ashbe
[16:41] <walrider> oita den
[16:42] <zaki> he he
[16:43] <zaki> real ip ta?
[16:43] <walrider> den na bhai iso ta amr dorkar :(
[16:43] <walrider> pls
[16:43] <zaki> <IP_ADDRESS>
[16:43] <walrider> akhon ki pc te asen ?
[16:43] <zaki> regular speed ei to downloa dhoi jaito etokkhone
[16:43] <zaki> hmm
[16:44] <walrider> 1 mbps parbo pc2pc
[16:44] <walrider> apne naman
[16:44] <zaki> he he
[16:44] <walrider> ami nibo apner pc theke amar pc te
[16:44] <walrider> hfs kore
[16:48] <zaki> it will take 35-40  mnt to download
[16:49] <walrider> check private msg bro
[16:52] <shanto> .
[16:53] <walrider> holo na :(
[16:55] <zaki> :|
[17:33] <zaki> wb dipraw
[17:34] <dipraw> hi zaki
[17:34] <zaki> how are you?
[17:34] <dipraw> i am quiet fine! zaki
[17:38] <zaki> oky
[18:11] <zaki> bbl
[19:35] <zaki> good night guys


[07:33] <itloft> Moin
[07:34] <itloft> Spricht hier jemand deutsch?
[07:37] <efix> Hallo
[07:37] <efix> Das clickup snap paket funktioniert nicht richtig. Hat jemand eine Idee was ich da machen kann?
 hier wird Englisch gesprochen
 903A
 RLX5
[13:29] <BluesKaj> Hi all
[15:30] <user|4> Hello, what qemu command should I use to boot kubuntu?
[15:30] <user|4> I guess `qemu-system-arm -machine virt  -cdrom kubuntu-22.10-desktop-amd64.iso` but it isn't quite working
[15:37] <arraybolt3> user|4: You're trying to boot an AMD64 ISO with an ARM emulator. That is likely to never work.
[15:38] <arraybolt3> user|4: QEMU is pretty complicated, but once you know how to use it it's not too hard. Let me see if I can give you a working command line.
[15:39] <arraybolt3> user|4:        qemu-system-x86_64 -accel kvm -cdrom kubuntu-22.10-desktop-amd64.iso -m 4G -nic user -smp 2
[15:39] <arraybolt3> That should give you relatively good performance. You'll need a system with at least 6 GB RAM to be able to run that.
[15:41] <arraybolt3> Note that this only just boots the ISO and doesn't provide a disk image to install to - doing that requires some extra work.
[15:41] <arraybolt3> You may also want to add "-vga qxl" to the end of that command if you want better graphics acceleration in the VM.
[15:51] <user|4> ah ok thx
[15:52] <user|4> Thought amd = arm XD, only used intel before
[15:53] <user|4> Wait why is the command qemu-system-x86_64? shouldn't it be something like qemu-system-amd64
[15:58] <arraybolt3> x86_64 and amd64 are the same thing, but QEMU uses the x86_64 terminology.
[17:23] <user|74> After upgrading from 20.04 -> 22.04, all my desktop icons/thumbnails are gone?!
[17:35] <cbreak> user|74: are they still in ~/Desktop ?
[17:36] <user|74> I don't have a ~/Desktop ?!
[17:37] <cbreak> that's weird
[17:40] <user|74> also all in the taskbar/panel are gone
[17:41] <user|74> https://www.bytesalad.org/owncloud/index.php/s/xH8BKu1JG6dOeAQ
[17:45] <cbreak> user|74: why do you think you have no desktop?
[17:45] <cbreak> did you chedk with ls -la ~/Desktop on a terminal?
[17:46] <user|74> yes
[17:46] <user|74> (base) marcow@feather6:~$ ls -la ~/Desktop
[17:46] <user|74> ls: cannot access '/home/marcow/Desktop': No such file or directory
[17:46] <user|74> (base) marcow@feather6:~$
[17:50] <user|74> And all the 'taskbar icons' should not be anywhere local to the user anyhow ?!
[17:51] <cbreak> some of them are local, in ~/.local/share/icons
[17:51] <cbreak> depending on how you got them
[18:05] <user|74> There is something else going on?! 'blending/merging' different images/layers?! Look at the following screen shot, the icon for the pop-up *is* found https://www.bytesalad.org/owncloud/index.php/s/QkNrwRqnUTAGrdK
[20:32] <sddasscd34> help
[22:32] <user|74> cbreak I had to replace *libqt5quick5-gles* with *libqt5quick5* and now things seem to work again. Not sure, why/how that got messed up:-(
[22:41] <user|74> https://bugs.launchpad.net/ubuntu/+source/qtbase-opensource-src-gles/+bug/1999946
[22:41] -ubottu:#kubuntu- Launchpad bug 1999946 in qtbase-opensource-src-gles (Ubuntu) "System icons missing in kubuntu 22.04.1 (after upgrade from 20.04.5)" [Undecided, New]
[23:03] <cbreak> weird
[23:26] <arrief> hello


[04:55] <blr> Would anyone happen to know if it is possible to debug-hooks both a subordinate and its parent together? Starting debugging for the second service complains that the tmux session already exists.
[09:00] <ejat> deployed horizon dashboard through juju ... may i know what is the default login n password ?
[12:09] <ejat> openstack-dashboard timeout when i tried to login
[12:09] <ejat> what should i do ?
[12:36] <ejat> marcoceppi: r u there?
[13:39] <jrwren> can I cancel a pending action?
[13:41] <jrwren> use case is: i ran `juju action do db/0 dump` which takes a while. I accidentally ran it twice. I'd like to cancel the pending job.
[13:48] <rick_h_> jrwren: I know you can see the queue, thuoght there was a cancel api
[13:48] <jrwren> rick_h_: i can't find it.
[13:49] <rick_h_> jrwren: hmm, wonder if it made the api but not the cli
[13:50] <jrwren> rick_h_: must be. cli has only do, fetch, status
[13:50] <aisrael> jrwren: rick_h_: we have a meeting next week about action 2.0 features. I'll add a cancel command to the list
[13:51] <rick_h_> aisrael: ah ok, isn't there a method to see the queue and such?
[13:51] <rick_h_> I know it was part of the spec
[13:53] <aisrael> rick_h_: `juju action status` will show you everything, pending or not, but there's no queue management afaik
[13:53] <jrwren> rick_h_: `juju action status` shows all of them.
[13:54] <rick_h_> ah ok
[13:54] <rick_h_> cool
[14:00] <thedac> jamespage: question about ceph and cinder charms. Can we specify different pools like this example http://www.sebastien-han.fr/blog/2013/04/25/ceph-and-cinder-multi-backend/
[14:01] <jamespage> thedac, I think so - let me check
[14:01] <thedac> thanks
[14:02] <jamespage> thedac, yes - the ceph pool is aligned to the service name - so
[14:02] <jamespage> juju deploy cinder-ceph cinder-ceph-sata
[14:02] <jamespage> juju deploy cinder-ceph cinder-ceph-ssd
[14:02] <jamespage> for example
[14:02] <thedac> ah, cool
[14:03] <jamespage> thedac, the trick is that the ceph charm does not support special placements (yet)
[14:03] <jamespage> thedac, so the backend pools should be pre-created in ceph by hand first - cholcombe has some stuff inflight to enhance pool management
[14:04] <firl> so I could set this up by hand manually within ceph, then have cinder-ceph relation charm take care of the relations, and use possibly what cholcombe has to link it between cinder volumes and the ceph pools?
[14:06] <jamespage> firl, kinda
[14:06] <jamespage> if I deploy: juju deploy cinder-ceph cinder-ceph-sata
[14:06] <jamespage> the backend pool must == 'cinder-ceph-sata'
[14:07] <jamespage> so if you pre-create or re-create the pool directly in ceph with the required characteristics it will work ok
[14:07] <jamespage> juju add-relation cinder-ceph-sata cinder
[14:07] <jamespage> and juju add-relation cinder-ceph-sata ceph
[14:08] <jamespage> are required of course
[14:08] <firl> so I would have 2 cinder-ceph relations
[14:08] <firl> and 2 separate ceph charms for the environment
[14:08] <firl> ?
[14:12] <coreycb> firl, here's a bundle to reference for deploying from source - http://bazaar.launchpad.net/~ost-maintainers/openstack-charm-testing/trunk/view/head:/bundles/source/default.yaml
[14:13] <firl> thanks!
[14:14] <bdx> firl:http://paste.ubuntu.com/12449099/
[14:17] <coreycb> firl, https://bugs.launchpad.net/charms/+source/nova-compute
[14:22] <firl> thedac: https://bugs.launchpad.net/charms/+bug/1497308
[14:22] <mup> Bug #1497308:  local repository for all Openstack charms <Juju Charms Collection:New> <https://launchpad.net/bugs/1497308>
[14:26] <beisner> wolverineav, https://wiki.ubuntu.com/ServerTeam/OpenStackCharms/ReleaseNotes1504
[14:33] <wolverineav> hey, neutron question - when I enable DVR, the DHCP and L3 agent are deployed on the compute node. I'd like to disable the L3 agent completely. Is there a way to do that in the neutron-api charm?
[14:33] <wolverineav> or, what would be the way to go about it?
[14:34] <coreycb> jamespage, gnuoy, any idea on this ^
[14:34] <jamespage> wolverineav, DVR enables metadata and l3-agent I think
[14:34] <jamespage> there is an extra toggle to enable dhcp as well
[14:34] <Guest90652> does juju-core 1.24.2 support CentOS7 on EC2?
[14:35] <jamespage> there is no way todo that in the charm right now, as its assummed from the charm choices you're making that you want ml2/ovs driver
[14:35] <jamespage> wolverineav, whats the use case?
[14:36] <wolverineav> jamespage, yes right. we're currently moving towards pulling the various agents into the big switch controller. the current release supports L3 and the next one will have DHCP and Metadata.
[14:37] <jamespage> wolverineav, ok - so in this case, you don't want to use the neutron-openvswitch charm - I'd suggest a neutron-bigswitch charm that dtrt for a big switch deployment
[14:37] <jamespage> as you really just want ovs right?
[14:37] <jamespage> not all of the neutron agent scaffolding around it
[14:38] <wolverineav> i'll be doing something like the ODL charm which deploys its own virtual switch. I would not be deploying the vanilla OVS
[14:39] <ejat> jamespage: openstack-dashboard charm , do i need manually change at the local_setting.py for the keystone host ?
[14:39] <jamespage> ejat, no you just add a relation to keystone
[14:39] <jamespage> wolverineav, sounds like a neutron-bigswitch charm is the right approach then
[14:39] <ejat> already did the relation
[14:40] <jamespage> wolverineav, openswitch-odl is the way forward from a frameworks perspective
[14:40] <ejat> should i change :
[14:40] <ejat> From:
[14:40] <ejat> OPENSTACK_KEYSTONE_DEFAULT_ROLE = "Member"
[14:40] <ejat> To
[14:40] <ejat> OPENSTACK_KEYSTONE_DEFAULT_ROLE = "_member_"
[14:40] <jamespage> no
[14:40] <ejat> or let as it is
[14:40] <jamespage> you should not need to change anything
[14:40] <wolverineav> jamespage, so it would be a neutron-api-bigswitch kinda thing. ah, i see
[14:40] <jamespage> wolverineav, kinda
[14:40] <jamespage> the bit for nova-compute == like openvswitch-odl charm
[14:41] <jamespage> the bit for neutron-api == like neutron-api-odl
[14:41] <wolverineav> got it
[14:41] <ejat> it cant communicate
[14:41] <ejat> on azure
[14:41] <ejat> from dashboard cant ping keystone
[14:41] <ejat> because it take the public dns
[14:42] <ejat> how to restart/reboot on of the service machine
[14:44] <ejat> jamespage: http://paste.ubuntu.com/12449394/
[14:50] <jamespage> ejat, blimey openstack ontop of azure?
[14:51] <ejat> yups ..
[14:51] <ejat> demo purpose
[14:57] <ejat> jamespage: http://picpaste.com/Screen_Shot_2015-09-18_at_10.56.08_PM-a0Td6kaK.png
[15:06] <Slugs_> I’ve followed the Ubuntu openstack single installer guide located here — http://openstack.astokes.org/guides/single-install — Every service statrts up except  for Glance - Simplestream Image Sync.  This should not hinder me from logging into to horizion but for some reason I can’t authenticate with my username as ubuntu and password I have is ‘openstack’.  I have been able to stop the container, start the container, login to the container and
[15:06] <Slugs_> check juju logs but I would like some more clairication on this to make sure I’m doing this correctly.
[15:16] <jingizu_> Hi all! When I try to juju remove a service (e.g. quantum-gateway, fundamental part of openstack) and re-deploy it to a different server (e.g. --to lxc:3)... I notice that it does remove it from juju, but the actual services themselves (i.e. all the neutron python servers on the origianl host) are still running... it's as if it just removed it from the juju
[15:16] <jingizu_> database but did not actually stop the services themselves
[15:17] <jingizu_> Of note is that the service is running on a system deployed bare-metal that is also running other juju services, so juju couldn't just tear down the lxc or tell MAAS to kill the bare metal machine altogether (Which obviously would kill the services too)
[15:22] <marcoceppi> ejat: what's your question?
[15:23] <ejat> openstack-dashboard charm
[15:23] <ejat> add-relation putting the public dns for keystone host in dashboard
[15:25] <ejat> jamespage: said i should not change anything in local_setting.py
[15:26] <jamespage> ejat, sorry - I'm not that familiar with how public dns works in azure; you should not have to change anything in settings.py normally but ymmv on anything other that MAAS (or OpenStack itself)
[15:27] <ejat> i cant login the dashboard
[15:27] <ejat> openstack.informology.my/horizon
[15:33] <ejat> login then timeout
[16:00] <firl> thedac: http://paste.ubuntu.com/12450237/
[16:10] <firl> thedac: http://paste.ubuntu.com/12450337/
 jingizu_ : on you question about removing service, you'll also have to first do remove-relation on that service (which you're trying to remove) for all its peer services. Once the removal of relation is done, the remove-service should go smoothly. there is also a --force flag that can be used.
[17:35] <jingizu_> amit213: Thanks for the reply. At this point I have managed to remove the service(s) in question. Like I mentioned, the service is no longer listed in juju status. However, the underlying programs that correspond to the service are still running... Any ideas why it would not delete said programs, configs, etc. when removing the service?
[20:38] <ennoble> with juju deployer or with the juju client add_machine call, can you specify a specific machine?
[21:02] <firl> ennoble: you can with constraints, and depending on the machined environment you can even use tags
[21:06] <ennoble> firl: I'm using maas. Is it possible to specify a specific machine my-server-1.foo? What about with the manual provider? ssh:root@my-server-that-maas-hates?
[21:07] <firl> ennoble: I don’t know anything about the manual provider. here is the tags information https://maas.ubuntu.com/docs/tags.html
[21:08] <firl> depending on how many nodes and what not, I sometimes just “acquire” the nodes in MaaS so that I don’t have things deployed to those containers
[21:08] <firl> So with juju deployer you can use the tags constraints as with the add machines
[21:08] <firl> for service units you can just do a —to
[21:09] <ennoble> firl: so you acquire the nodes in maas? add tags to them there, and then deploy to them with juju deployer?
[21:09] <firl> “acquire” nodes in maas just means that juju deployer can’t use them to pull from ( it’s a hack I use )
[21:09] <firl> but you can just add tags via the maas cli  ( in the maas gui in 1.8 ) to the physical machines and then use the deployer
[21:10] <firl> and everyone from ubuntu is probably at a party or traveling because they just finished up a summit in DC
[21:27] <nodtkn> ennoble: you can add a machine to any existing enviorment with juju add-machine ssh:ubunut@<hostname>
[22:04] <ennoble> nodtkn: thanks, I can do that, I'm wondering after I do that can I make juju deployer use it?
[22:04] <mwenning> hi, looking for a quick answer - I moved a bundle from one system to another and ran juju-deployer --config=lis-test-bundle.yaml -e maas
[22:05] <mwenning> It returned with something about must specify deployment, what did I forget?
[22:06] <mwenning> 'Deployment name must be specified'


[00:25]  * JediMaster kicks Czessi
[00:25] <cody-somerville> oh my
[00:26] <JediMaster> Any admins about that can just temporary ban him so he doesn't rejoin next time?
[00:26] <jdong> !ops ^^^
[00:26] <ubotu> Sorry, I don't know anything about ops ^^^ - try searching on http://ubotu.ubuntu-nl.org/factoids.cgi
[00:26] <jdong> !ops
[00:26] <ubotu> Help! Hobbsee, Riddell, sladen, fbond, mneptok, gnomefreak, Seveas, dholbach, elkbuntu, PriceChild, or jpatrick!
[00:26] <Hobbsee> what?
[00:26] <Pici> Czessi_
[00:26] <jdong> Hobbsee: Czessi_ excess flooding
[00:27] <ScottK2> emgent: I saw the USN.  Thanks.
[00:27] <Pici> in -bugs too
[00:27]  * Pici doesnt have ze power
[00:27] <jdong> Hobbsee: probably a bf to -ops?
[00:27] <cody-somerville> Pici, we all used to have powers but they seem to have disappeared.
[00:27] <jdong> cody-somerville: yeah I tried a couple /cs o's before giving up :)
[00:28] <cody-somerville> He is in -marketing too
[00:28] <jdong> the dynamic duo to the rescue!
[00:28]  * jdong is so gonna get killed for that one
[00:28] <JediMaster> he probably just needs to be banned for a few min so he doesn't reconnect
[00:28] <JediMaster> thanks guys =)
[00:28]  * PriceChild messages him to talk in #ubuntu-ops when ready
[00:28]  * Hobbsee hates irssi for ban stuff.
[00:29] <PriceChild> actually that's a silly idea... /me trundles on
[00:29] <jdong> Hobbsee: it's not exactly as intuitive as xchat's /cs bans.
[00:29] <Hobbsee> yeah
[00:29] <azeem> Hobbsee: http://svn.donarmstrong.com/don/trunk/home_modules/irc/.irssi/scripts/auto_bleh.pl is ok
[00:29] <Hobbsee> yeah, i just need to remember how to use it
[00:30] <azeem>  /ab <nick> reason
[00:30] <JediMaster> ahhh yess!! I've not completely automated my package building, uploading, adding the new .deb to the repos and it's all signed too, purrrfect, thanks guys for the help, reprepro did the trick nicely
[00:30] <jdong> azeem: yeah it's okay and what I use but still not as good as xchat
[00:30] <PriceChild> azeem: doesn't do forwards
[00:30] <azeem> oh well
[00:45] <ScottK2> \sh_away: There's a new gnucash version proposed for a merge/FFe.  Would you please have a look at it.
[00:48] <ScottK2> Here's something that would be useful ...
[00:48] <ScottK2> A cvs/svn wrapper that looks at what kind of respository you are in and substitues cvs/svn as needed.
[00:49] <ScottK2> I'm using cvs for the first time in about a year and I type svn command instead of cvs command a significant fraction of the time.
[01:31] <bddebian> Heya gang
[01:32] <ScottK2> Heya bddebian.
[01:32] <bddebian> Hi ScottK2
[01:32]  * ScottK2 just diss'ed you in #debian-python
[01:33] <bddebian> Yeah, so I noticed, thanks :-)
[01:59] <Hobbsee> you know, the lag to here is really not too bad, considering i'm ssh'ing to the US, then back to austraila...
[02:00]  * ajmitch is used to that
[02:01] <ScottK2> Heya ajmitch.
[02:01] <ScottK2> ajmitch: Thanks a bunch still for the return of the RC bug tracker.  I've gotten an number of good fixes in I wouldn't have otherwisel.
[02:02] <Flannel> Hey guys, do alpha/beta versions of Ubuntu have debug symbols included in them? (that get removed for the final?)
[02:03] <jdong> no
[02:03] <ajmitch> ScottK2: NP, glad it was of some help
[02:04] <ajmitch> no doubt it's probably buggy & should be improved
[02:04] <ScottK2> ajmitch: It's about a billion percent better than anything anyone else has provided.
[02:05] <Hobbsee> dear eclipse, plz stop stealing all cpu.  kthxbye.
[02:06] <ScottK2> Isn't that a feature of eclipse.     You should consider upgrading.
[02:27] <bddebian> heh
[02:27] <milli> ScottK2: well, yeah.  Will get there once Hardy is baked..  ;-)
[02:27] <bddebian> jdong: OK, what the hell is BrowserKit? :)
[02:28] <milli> ScottK2:  asciidoc deps needs to be (<< 7.1.0), and tcl8.5 -> tcl8.4, but /usr/bin/wish8.5 is hard-coded into the gitk executable, so that needs a patching.
[02:28] <milli> and there's not tk8.5 depends in control..  oops
[02:29] <milli> (source is from sid)
[02:29] <milli> and it's prolly only a big deal to me right now, so no worries.
[02:31]  * milli is installing issue tracker that has git repo browser in it and require git-core <IP_ADDRESS> or better...
[02:33] <ScottK2> How about <IP_ADDRESS> from Hardy.  I bet it actually builds.
[02:33] <ScottK2> milli: Do we want <IP_ADDRESS> for Hardy?
[02:47] <milli> ScottK2: <IP_ADDRESS> is good enough for me
[02:47] <milli> thus it's there already
[02:48] <ScottK2> OK.
[02:52]  * milli panics for a second thinking it's a Survivor night
[02:55]  * Hobbsee sees a broken getdeb system
[02:55]  * Hobbsee advises a resinstall.
[02:55] <ScottK2> Hobbsee: Isn't that redundant?
[02:56] <Hobbsee> ScottK2: system lookup error for gnome-system-monitor, after installing pidgin, etc, from getdeb.  yay.
[02:56] <Hobbsee> i'd wondered why the version sof libc6, etc, were different..
[02:56] <ScottK2> Heh.
[02:56] <ScottK2> But they don't want to get involved in packaging for Ubuntu proper because we're too picky....
[03:16] <jdong> ScottK2: you saw the transmission packages from Friday right?
[03:16] <jdong> ScottK2: essentially they will ship a single transmission package that on install will cause dpkg overwrite errors to transmission-{cli,common,gtk}
[03:16] <jdong> ScottK2: when I complained about this behavior, the response I got back was "this only happens if the user has transmission installed from Ubuntu"
[03:17]  * jdong gives up
[03:18] <ScottK2> jdong: This is Transmission upstream making their own packages?
[03:24] <jdong> ScottK2: no this is a getdeb packager
[03:24] <jdong> ScottK2: we love transmission upstream :)
[03:28] <ScottK2> Ah.
[03:28] <ScottK2> Back on getdeb.
[03:29] <ScottK2> Figures
[03:29] <ScottK2> No, I didn't see their packages.
[03:31] <jdong> ScottK2: well essentially it was a blind cdbs dh_make from the looks of it, with no regards to properly dealing with upgrades from Ubuntu packages
[03:32] <jdong> ooh! I have the diff.gz!
[03:32] <jdong> http://pastebin.ubuntu.com/5975/
[03:32] <ScottK2> By policy they don't deal with upgrades.  They saw to uninstall all getdeb packages before an upgrade.
[03:33] <ScottK2> Which is a step up from the late not so lamented Automatix that just broke later Ubuntu upgrades and blamed Ubuntu.
[04:30] <ScottK2> I just love the Launchpad design.
[04:30] <ScottK2> When you convert a bug to a question, it sets the bug status to invalid.
[04:30] <ScottK2> If the bug was already invalid, guess what?
[04:30] <ScottK2> You got it.  The bug cannot be converted back to a question.
[04:31] <Fujitsu> ScottK2: It oopses?
[04:32] <ScottK2> No.  It tells you that because the bug may be valid somewhere else, it can't be converted.
[04:32] <ScottK2> I suspect it's a default response if changing to invalid doesn't work.
[04:32] <ScottK2> Typical of Launchpad's well thought out designs.
[04:35] <nixternal> ScottK2 and Fujitsu: you know if it was open sourced we could fix that :p
[04:35]  * nixternal ducks
[04:36] <Fujitsu> nixternal: But Hobbsee's not here.
[04:36] <nixternal> oh she is, just hiding
[05:02] <Hobbsee> Fujitsu: i am now...
[05:02] <Hobbsee> ScottK2: yeah, exctly, so they use the same version number of libc6 as us.
[05:03] <Hobbsee> jdong: damn that's stupid!
[05:03] <Hobbsee> ScottK2: that's...classy
[05:04] <nixternal> I love how you come back and just comment all at once
[05:05] <jdong> lol it's a FIFO :)
[05:05] <nixternal> exactly
[05:05]  * ScottK2 followed it just fine.
[05:05]  * Hobbsee was at tute
[05:05]  * Hobbsee is still having getdeb nightmares, though :P
[05:05] <jdong> as did I. It's not any different than a laggy splitty day :)
[05:05] <nixternal> getdeb rocks!
[05:05] <jdong> Hobbsee: haha those are here to last :)
[05:05] <nixternal> bahahaha
[05:06]  * jdong writes the UpdateManagerForceOverwriteByDefault spec... :D
[05:06] <nixternal> turkey, right as I was in the middle of typing
[05:07] <ScottK2> Then it worked.
[05:07] <nixternal> anywho, #kubuntu is starting to see people go 'I tried to upgrade to hardy per the instructions on h.u.c/community but I am getting these errors'
[05:07] <nixternal> ask to see their sources.list, and guess what is in there
[05:09] <ScottK2> If getdeb would just use a PPA, they could even serve their crack out of the Canonical data center.
[05:09] <Hobbsee> nixternal: turkey, hey?
[05:09] <nixternal> NOOOOOOOOOOOOOOOOOOOoo!!!!!!!!!!!!!!!!!
[05:09] <Hobbsee> nixternal: are they getting the libc6 error, or?
[05:09] <nixternal> ;p
[05:09] <nixternal> i seen the highlight while talking to another person
[05:10] <nixternal> gahahahahaha
[05:10] <nixternal> damn, you have a TOO MUCH CRACK flag, I like that one
[05:10] <ScottK2> Cool.  First time that's ever happened to me.
[05:10]  * nixternal whistles
[05:11] <nixternal> scared them away Hobbsee!!!
[05:11] <nixternal> hahahahaha
[05:12] <nixternal> /mode +b mdomsch!*@*##dont_run_away_scared bddebian!*@*##dont_run_away_scared
[05:12] <nixternal> :p
[05:12] <nixternal> oops, forgot a b in there
[05:13] <Hobbsee> heh
[05:14] <Fujitsu> Aw, we can't all op now.
[05:14] <Fujitsu> No more crazy op-abuse wars, I guess.
[05:14] <Hobbsee> for good reason :P
[05:15] <nixternal> hehe
[05:15] <nixternal> 00:15:18 [notice(ChanServ!ChanServ@services.)] An access level of [10] is required for [OP] on #ubuntu-motu
[05:16] <nixternal> heh, anyone remember /fuckem on the BitchX client? that was the mofo of evilness right there
[05:16] <nixternal> that was about 10 years ago already...jeesh time flies when you are having fun
[05:20] <Fujitsu> nixternal: I had the pleasure of getting BitchX removed.
[05:21] <Hobbsee> Fujitsu: nwo try with yada and checkinstall.
[05:22] <Fujitsu> They're not horrifically insecure.
[05:22] <nixternal> you think?
[05:22] <nixternal> how many times was BitchX taken over by hackers and turned into a RootKit?
[05:22] <jdong> Hobbsee: alien should go though, in all seriousness
[05:23] <jdong> Hobbsee: almost always that tool is misused
[05:23] <ScottK2> Trying to do something that actually can't be done.
[05:23] <jdong> ScottK2: like compiling eclipse 3.3? :)
[05:24] <ScottK2> Not that hard
[06:01] <Hobbsee> jdong: i know.
[06:01] <Hobbsee> jdong: if only lsbrelease didn't require it...
[06:46] <warp10> Good morning
[07:12] <dholbach> good morning
[07:34] <theseinfeld> LucidFox you there?
[07:34] <LucidFox> yes
[07:34] <theseinfeld> when you have time, will you take another look at the http://revu.tauware.de/details.py?package=libdc1394-22
[07:35] <theseinfeld> please :)
[07:35] <theseinfeld> LucidFox I hope that we could get it in soon so I can focus on other packages
[07:55] <LaserJock> dholbach: how often is the 5-a-day stats page updated?
[07:56] <dholbach> LaserJock: every hour I think
[07:56] <LaserJock> ah, so it is :-)
[07:57] <dholbach> we have quite some busy Teams there :)
[07:57]  * LaserJock puts ubuntu-nevada in 2nd place today ;-)
[07:57] <dholbach> I didn't know you were in Nevada
[07:57] <LaserJock> yeah
[07:59] <LaserJock> I had a good couple days, 21 bugs
[08:05] <cody-somerville> u-u-s queue is getting big :)
[09:24] <YokoZar> dholbach: *hugs*
[09:24] <dholbach> :)))
[09:34] <cody-somerville> :)
[09:44] <\sh> hmm...hugging time?
[09:44] <\sh> YokoZar: hey congrats :)
[09:44] <\sh> yust read the good news
[09:45]  * YokoZar hugs \sh
[09:47] <cool> what are this hugs for :p
[09:49] <cody-somerville> YokoZar, is motu now
[09:51] <huats> YokoZar: congrats
[09:54] <\sh> YokoZar: go get wine rocking ;)
[10:13] <\sh> ScottK: the merge of gnucash was not correct of Fred...redone it...checking for build errors now and install stuff....but we want it in hardy...:)
[10:28] <\sh> grmpf
[10:29] <\sh> why is it so hard to get recordmydesktop and audio to run?
[10:29] <\sh> I want to capture the sound from a sound app, but it always gets my mic
[11:19] <mok0> Fujitsu: I found the bug. petsc has nothing to do with it
[11:20] <Fujitsu> mok0: Was that the openmpi upload I saw earlier?
[11:20] <mok0> Fujitsu: yes it was
[11:20] <Fujitsu> Good to hear.
[11:21] <mok0> Fujitsu: so no reason to muck more with petsc
[11:22] <mok0> Fujitsu: but for illuminator, I recommend a sync
[11:23] <mok0> Fujitsu: should I state that in bug 201962, or create a new one?
[11:23] <ubotu> Launchpad bug 201962 in scalapack "gfortran transition" [Wishlist,In progress] https://launchpad.net/bugs/201962
[11:24] <Fujitsu> mok0: Create a new one, to avoid giving the archive admins heart attacks.
[11:24] <mok0> Fujitsu: oh, we don't want that, especially now
[11:25] <Fujitsu> I'm not sure they'd like all the bugmail, or to dig through all of the tasks.
[11:25] <mok0> right. Good old LP
[11:30] <Hobbsee`> heh
[11:30]  * Hobbsee` only counted 7 mails tonight that she had no interest in, done via LP.
[11:32] <emgent> heya people
[11:33] <ScottK> \sh: I ack'ed gnucash.
[11:33] <mok0> Fujitsu: Is there a gfortran tag?
[11:33] <mok0> Fujitsu: for LP I mean
[11:34] <ScottK> YokoZar: Congratulations.
[11:34] <Fujitsu> mok0: Not that I know of, and I wouldn't advise creating any more.
[11:34] <mok0> ok
[11:35] <\sh> ScottK: thx
[11:36] <\sh> Hobbsee: would you like to ack gnucash too? (bug #205570)
[11:36] <ubotu> Launchpad bug 205570 in gnucash "[FFe] Please merge gnucash 2.2.4-1 from debian unstable" [Wishlist,New] https://launchpad.net/bugs/205570
[11:36] <Hobbsee> \sh: wasn't that already done, or is this another one?
[11:36] <ScottK> Hobbsee: This one is new yesterday.
[11:36] <ScottK> Or probably earlier today for you.
[11:37] <Hobbsee> ahh
[11:37] <\sh> man I'm doomed...how can I tell an app to use a monitor sound input device of PA
[11:38] <\sh> or to use an output device as input
[11:43] <Lamego> just wire from your speakers to your mic :P
[11:46] <\sh> Lamego: from d-a to a-d ? bad quality
[11:46] <\sh> but it must be possible to capture the "sound output"....
[11:48] <Hobbsee> \sh: done
[11:48] <\sh> well, actually I would need access to the monitor device, which PA tells me to use as input device
[11:48] <\sh> Hobbsee: gracias
[11:49] <Hobbsee> y/w
[11:57] <_ruben> hrm .. debuild -S is 'munching' my email address i used in the changelog, it changes it to username@hostname .. is there some env var i can set to prevent that or smth?
[11:58] <ScottK> _ruben: Are you sure it's debuild and not dch.
[11:59] <ScottK> _ruben: DEBEMAIL and DEBFULLNAME are probably what you're looking for.
[11:59] <persia> _ruben: $ export DEBEMAIL="Appelation Surname<EMAIL_ADDRESS>[12:00] <_ruben> ScottK: i used dch to edit changelog and the debian/changelog file has the proper email address
[12:00] <_ruben> and i think i even have DEBEMAIL exported (*double checks*)
[12:00] <ScottK> OK.  Not sure then.
[12:02] <_ruben> hrmm .. seems the changelog got altered at some point as well .. lets investigate further .. might be false alarm
[12:02] <ScottK2> Each time you run dch it'll reset it.
[12:02] <mok0> Huh? I just updated my hardy builder, and now I get this:  "configure: error: guile-config is broken"
[12:03] <_ruben> guess last time i used dch i didnt have those vars exported or smth, strange
[12:03] <_ruben> works fine now, very strange
[12:03] <mok0> _ruben: that's not strange, that's good! :-)
[12:04] <_ruben> mok0: the fact that i got it sorted is good, the fact that it somehow got messed up remains strange ;)
[12:08] <mok0> Fujitsu: AFAICS meep just needs a recompile when the dependencies (lapack, atlas, ...) have been transitioned
[12:09] <mok0> Fujitsu: However, my sbuilder still pulls in F77
[12:11] <mok0> Fujitsu: How should I mark that on the bug page?
[12:12] <Fujitsu> mok0: I'm not sure...
[12:13] <mok0> Fujitsu: I''ll just set it to "confirmed" and deassign myself
[12:13] <Fujitsu> mok0: Sounds OK.
[12:13] <cody-somerville> Fujitsu, Would you be able to help me create mdt output for Xubuntu packages?
[12:14] <Fujitsu> cody-somerville: I'll set it up with the rest of mine... but how am I to determine the list of packages?
[12:15] <cody-somerville> Fujitsu, would you be able to use our seeds?
[12:16] <Fujitsu> cody-somerville: I've not yet done anything like that. If you can give me a script that produces a list packages you want listed, I can set it all up in a couple of minutes.
[12:16] <cody-somerville> One package per line?
[12:19] <mok0> Fujitsu: Ad meep, I think g77 gets pulled in as a dependency by autotools. Have you dealt with that? I has a autoconf macro "acx_blas.m4" that does a bunch of F77 checking...
[12:19] <mok0> s/I has/It has/
[12:20] <Fujitsu> I've not dealt with it, no :(
[12:20] <mok0> Fujitsu: that makes the transition a lot more complex
[12:21] <mok0> Fujitsu: I need to patch the autobuild system and run the autotools :-(
[12:21] <Fujitsu> mok0: Hasn't Debian done this?
[12:22] <mok0> Fujitsu: hehe would be nice... I'll check
[12:27]  * ScottK2 recalls seeing an IRC comment that thr gfortran transition was done in Debian.
[12:28] <broonie> IIRC it is pretty much but not quite propagated to testing.
[12:29] <mok0> ScottK: yes, it looks like meep does not depend on f77
[12:29] <mok0> in sid
[12:43] <_ruben> is there some (simple) shortcut to have a fully prepared kernel source within your pbuilder buildroot .. right now im installing the linux-source package, copy .config file from outside root, run some make cmds, symlink to /usr/src/linux .. then do my module-assistant stuff
[12:44] <_ruben> could write a script to do so, but am wondering if i might be missing something (obvious)
[12:44] <azeem> what are you trying to do?
[12:44] <\sh> is there a channel for medibuntu?
[12:45] <azeem> \sh: uhm, /list #medibuntu
[12:47] <_ruben> azeem: compiling openswan-modules-source (recent upstream version, 2.4.12, in debian/ubuntu there's 2.4.6, but that doesnt make a diff i think)
[12:47] <azeem> _ruben: why does it need the full source and not just the headersß
[12:47] <azeem> ?
[12:48] <_ruben> azeem: it performs make commands from inside the kernel source tree .. perhaps its an old fashioned method that got stuck or smth .. dont really know
[12:50] <_ruben> hmm .. in fact .. i'll give the ubuntu version of 2.4.6 a try .. see if it behaves differently
[12:50] <mok0> I'm actually surprised that the gfortran transition got an FFE. Seems pretty late in the cycle for such a substantial change
[12:51] <Fujitsu> mok0: We were already half-way there (it was started in main), and you can't really stop half-way.
[12:51] <mok0> Fujitsu: true
[12:51] <ScottK2> That was my rationale when I supported it.
[12:51] <Fujitsu> Why it was started is beyond me.
[12:52] <mok0> Fujitsu: but there's not much time for testing, some of the packages have quite low popcon scores
[12:52] <Fujitsu> Much like the LDFLAGS and python-central changes...
[12:52] <mok0> Fujitsu: LDFLAGS change?
[12:52] <emgent> Fujitsu: are you work on bug #203456 or can i fix it for <=gutsty?
[12:52] <ubotu> Launchpad bug 203456 in horde3 "[horde3] [CVE-2008-1284] information disclosure" [High,Fix released] https://launchpad.net/bugs/203456
[12:52] <emgent> s/gutsty/gutsy/
[12:52] <_ruben> the shipped openswan-modules-source (2.4.6) fails to build as well, yet differently
[12:53] <mok0> Fujitsu: is that what screwed up libc6 at one point?
[12:53] <Fujitsu> mok0: It is.
[12:53] <Fujitsu> emgent: Go ahead.
[12:53] <Fujitsu> emgent: I'm concentrating only on Hardy at this point, so we can give it full support later.
[12:53] <mok0> Fujitsu: LDFLAGS transition passwd me by. Reference?
[12:54] <emgent> ok thanks
[12:54] <Fujitsu> mok0: the dpkg-buildpackage default was changed a couple of months ago.
[12:55]  * mok0 is glad that he's not maintaining dpkg-buildpackage :-/
[13:04] <jpatrick> azeem: no0tic.homelinux.org/~no0tic/auto_bleh.pl - consider using this version, it has more commands
[13:04] <azeem> and a l33t hostname
[13:21] <\sh> re
[13:21] <\sh> damn..my buildserver at home is off...or the provider line
[13:21] <emgent> heya \sh :)
[13:21] <emgent> use PPA :P
[13:32] <\sh> emgent: nope...too slow for me :)
[13:32] <\sh> ah back...a glitch in the matric
[13:32] <\sh> -c+x
[13:41] <emgent> :)
[13:47] <ScottK2> Hobbsee: Would you please have a look at Bug #206948
[13:47] <ubotu> Launchpad bug 206948 in phpgroupware "phpGroupWare should be included in Hardy" [Undecided,New] https://launchpad.net/bugs/206948
[13:47] <ScottK2> I think it ought to be approved so the package doesn't dissapear for one release.
[13:49] <\sh> oh damn you ajmitch  ;)
[13:50] <\sh> ScottK2: wanna step up to repackage the new version? ;9
[13:50] <Hobbsee> ScottK2: done
[13:51] <ScottK2> \sh: No.
[13:51]  * ScottK2 avoids anything to do with php.
[13:53] <Hobbsee> hi, bfiller.  who are you?
[13:53] <\sh> ScottK2: if it's only a sync...let's go for it
[13:53] <bfiller> Hobbsee: I work for Canonical in Lexington, part of Mobile Solutions Group
[13:54] <\sh> actually we should check dapper for it
[13:54] <Hobbsee> bfiller: ahhh....welcome.
[13:54] <Hobbsee> bfiller: not seen you here before
[13:54] <\sh> Hobbsee: you should join #ubuntu-mobile ;)
[13:54] <Hobbsee> \sh: i did do, for a while.
[13:54] <Hobbsee> \sh: it does look interesting
[13:54] <bfiller> Hobbsee: thanks, I've been on this channel for a while, but haven't been very active
[13:54] <ScottK2> \sh: It was a sync before.  Would you look into it?
[13:55] <\sh> ScottK2: I'll just have a look...
[13:55] <ScottK2> \sh: Thanks.
[13:55] <Hobbsee> bfiller: btw, the address is wrong on your lp page - it's irc.freenode.net, not .com
[13:56] <Hobbsee> oh wait.  maybe that works too
[13:56] <bfiller> Hobbsee: ah, thanks. I'll fix that
[13:56] <StevenK> chat.freenode.com is an alias for chat.freenode.net.
[13:57] <Hobbsee> so it is
[13:57] <\sh> ScottK2: grmpf..that looks like a piece of crap to me...well, need to look more closely this evening when I'm home.
[13:57] <\sh> btw..what happened to norsetto...did anybody see him lately?
[13:58] <ScottK2> I spoke with him briefly yesterday on IRC for the first time in quite a while.
[13:58] <ScottK2> He seems active on email, but on IRC much less.
[13:58] <ScottK2> Not sure why.
[13:59] <Hobbsee> less of a time waste?
[14:00] <\sh> ScottK2: just because I didn't see him doing motu-release work..and it's not good to have all -release stuff on your and hobbsees and sistpoties shoulders
[14:00]  * Hobbsee hasn't been doing much of it either, pretty much only when poked
[14:00] <ScottK2> He's been doing a lot with the gfortran transition.
[14:01] <\sh> ScottK2: ah behind the scenes
[14:01] <ScottK2> Here's a question: UPnP - Feature or security bug?  Bug #204928 for context.
[14:01] <ubotu> Launchpad bug 204928 in amule "[FeatureFreeze Exception] New aMule 2.2.0 pre-release snapshot and build with uPnP " [Undecided,New] https://launchpad.net/bugs/204928
[14:01] <mok0> \sh, norsetto was here yesterday
[14:01] <mok0> \sh, he's been busy with the gfortran transition
[14:03] <\sh> ScottK2: well, if it's already a feature which is only activated, it wouldn't hurt ;)
[14:03] <\sh> mok0: yeah, I just didn't see him much lately :)
[14:03] <ScottK2> \sh: Good point.
[14:04] <\sh> ScottK2: I think ffe should be filed when "new features" are applied to upstream sources...
[14:04]  * ScottK2 marks a bug invalid based on "Bug reporter is a known idiot."
[14:04] <\sh> lol
[14:05] <ScottK2> \sh: Agreed and we've had a couple of those.
[14:06] <Hobbsee> ScottK2: hah
[14:06] <afflux> ScottK2: may you write a nice stock reply for the bugteam for the idiot-case? :)
[14:07]  * ScottK2 is not a fan at all of the stock replies.  It runs decidedly counter to the computers for Humans theme of Ubuntu.
[14:07] <Exfil> i am having a problem with some of my resolution, especially my gdm login, the text is TINY TINY!, some aplications are like this aswell
[14:08] <ScottK2> Exfil: Help in #ubuntu or #ubuntu+1 for Hardy
[14:08] <Exfil> oh
[14:08] <Exfil> ok
[14:10] <emgent> i go to work, see you later people.
[14:12] <ScottK2> mok0: Are you still interested in your python-debian FFe?
[14:12] <ScottK2> If so, please update it.
[14:12] <mok0> ScottK: yes, I just haven't got around to it yet
[14:12] <ScottK2> OK.
[14:12] <mok0> ScottK: I don't think it involves much
[14:12] <mok0> ScottK: it already has 1 ack
[14:14] <ScottK2> Just provide the rest of the information and I'll ack it.
[14:16] <mok0> ScottK2: ok
[14:27] <mok0> Huh? My sbuilder says: python-debian_0.1.9.dsc: amd64 not in arch list: all -- skipping ???
[14:32] <soren> mok0: sbuild -A
[14:32] <mok0> soren: thanks!
[14:33] <mok0> soren: yep, it worked. I was looking at the config file
[14:47] <mok0> ScottK: Required info added to bug #198959
[14:47] <ubotu> Launchpad bug 198959 in python-debian "[needs-sync] python-debian_0.1.9 from Debian Sid" [Undecided,Incomplete] https://launchpad.net/bugs/198959
[14:47]  * ScottK looks
[14:49] <ScottK> mok0: Approved.  I subscribed UUS to give it a sponsor's review.
[14:49] <mok0> ScottK: Great! Another one bites the dust
[14:54] <bddebian> Heya gang
[14:56] <emgent> hi bddebian :)
[15:00] <bddebian> Hello emgent
[15:06] <\sh> ScottK2, Hobbsee: how are we dealing with bugs like bug #163906 ? should we just sync it or do we need the FFe stuff?
[15:06] <ubotu> Launchpad bug 163906 in cacao "FTBFS: cacao_0.98-2 on hardy/i386" [Undecided,Confirmed] https://launchpad.net/bugs/163906
[15:07] <\sh> well, when the infos are correct on the bug...which isn't somehow
[15:15] <RainCT> heya
[15:19] <ScottK> \sh: Since that one was a missing build-dep, why not just make a new revision adding the build-dep and upload it?
[15:19] <ScottK> Assuming that part of the bug was right....
[15:20] <\sh> ScottK: there are two FTBFS bugs :(
[15:20] <\sh> ScottK: just checking it
[15:22] <ScottK> At this point I'd say if we can just have the bug fix in a reasonably easy way we'd rather have that.
[15:22] <\sh> ScottK: well, depends what upstream changed in 0.99~rc which is in experimental...
[15:23] <\sh> ScottK: if we can cherry pick the ftbfs fixes from upstream...I agree to go with a fixed 0.98 in this cae
[15:23] <\sh> case even
[15:24]  * RainCT doesn't remember if FFe's should be requested before packaging a new version of a package or after you have it ready
[15:26] <RainCT> can someone answer? ^^
[15:27] <\sh> RainCT: depends...I'll do it every time I have a package checked, build and installed
[15:28] <ScottK> RainCT: Look at the required info for an FFe and tell me how you fill it out withouth a package ready?
[15:28] <RainCT> ScottK: yeh, but I wanted to double check before doing the work :P
[15:28] <\sh> RainCT: only non-devs are filing bugs for FFe without filling in the needed infos
[15:45] <\sh> ScottK: na no luck with the builddep
[16:04] <soren> superm1: You don't need to depend on awk.
[16:04] <Mirv> could anyone maybe upload an updated version of compizconfig-settings-manager, with patch/file from bug 204208 added?
[16:04] <soren> superm1: It's guaranteed to be installed.
[16:04] <ubotu> Launchpad bug 204208 in compizconfig-settings-manager "Finnish translation is broken (non-ASCII characters missing)" [Undecided,Confirmed] https://launchpad.net/bugs/204208
[16:05] <Mirv> the current version has so broken translation it's a bit embarassing
[16:05] <mario_limonciell> soren, doh.  yeah, I was thinking towards debian when I had it listed
[16:05] <soren> mario_limonciell: I doubt Debian needs a dependency on awk, too.
[16:05] <soren> ICBW, though.
[16:05] <mario_limonciell> soren, at least quilt does in debian
[16:06] <mario_limonciell> which is what made me think debian in general
[16:06] <mario_limonciell> doesn't break anything though to do so, next time there is a new version i'll remember to drop it, no use redoing the upload for it
[16:06] <soren> Sure, sure. It doesn't hurt.
[16:09]  * cody-somerville hugs nixternal :)
[16:10]  * nixternal hugs cody-somerville
[16:15] <cody-somerville> nixternal, so close :)
[16:15] <nixternal> hehe
[16:16] <cody-somerville> nixternal, Are you going to UDS?
[16:19] <nixternal> doesn't look like it
[16:19] <nixternal> that is uni graduation week
[16:21] <cody-somerville> Ah.
[16:29] <cody-somerville> soren, What about you? Going to UDS?
[16:29] <soren> cody-somerville: Sure.
[16:29] <soren> cody-somerville: I sort of have to :)
[16:29] <soren> cody-somerville: You?
[16:29]  * cody-somerville nods. :)
[16:29] <cody-somerville> This will be my first one.
[16:30] <soren> cody-somerville: Cool. It's good fun :)
[16:30] <\sh> especially in the evening
[16:30] <cody-somerville> hehe
[16:30] <\sh> so between 9am and 7pm ;)
[16:31] <\sh> it's hard work ;)
[16:32] <zul> soren: you dont really have to ;)
[16:32] <\sh> heading home now....bbl
[16:35] <jdstrand> emgent: uploaded horde3
[16:36] <emgent> thanks
[16:37] <emgent> other info for USN is in my post
[16:37] <emgent> see query :)
[16:37] <jdstrand> I saw that, thanks
[16:38] <jdstrand> no USN though-- universe package
[16:38] <emgent> oh ok
[18:13] <james_w> What's the protocol for an Ubuntu upload of a Debian native package?
[18:13] <james_w> how do we modify the version number?
[18:15] <james_w> ah, it appears as though it's just ubuntu1 as normal.
[18:16] <james_w> that's what happened with devscripts at least
[18:16] <sebner> james_w: already found a solution for dag2html?
[18:17] <james_w> sebner: there's been a little discussion in the ocaml team.
[18:17] <james_w> I'll give it a day or two and then push for removal.
[18:18] <sebner> k, thx
[18:34] <cody-somerville> Thanks geser :)
[19:16] <emgent> \sh: hi :)
[19:16] <emgent> DktrKranz: heya
[19:16] <DktrKranz> hey emgent
[19:17] <\sh> re
[19:28]  * \sh goes to sleep...need a lot of it...so no work today anymore
[19:36] <leonel> anyone knows what's the eta for postgresql 8.2.7 to be released as security  for gutsy   at this time it's accepted in gutsy but nor released  https://lists.ubuntu.com/archives/gutsy-changes/2008-March/010170.html
[19:36] <leonel> Thank you
[19:38] <blueyed> keescook: the security update for dspam introduced a bashism.. I'll have the debdiffs ready shortly.. Those go to -security, too, correct?
[19:38] <keescook> blueyed: yup -- I thought you had tested the dspam updates?
[19:39] <keescook> leonel: not sure, check with pitti (details should be in bug 203734)
[19:39] <ubotu> Launchpad bug 203734 in postgresql-8.2 "8.2.7 stable bug fix release" [High,Fix committed] https://launchpad.net/bugs/203734
[19:39] <blueyed> keescook: apparently not good enough..! sorry. :/
[19:40] <leonel> thanks keescook
[19:40] <jackster> hey guys
[19:40] <jackster> question, is Ubuntu 8.04 going to ship with Firefox 2 or 3?
[19:42] <jackster> because if Ubuntu 8.04 is coming out in April then it doesn't seem it'll come with a final version of Firefox 3.....
[19:42] <ssweeny> jackster, it currently ships with 3 beta 4
[19:43] <RainCT> http://packages.ubuntu.com/hardy/all/fusion-icon/filelist  does this need to be rebuilded to use the new pycentral directories
[19:43] <keescook> blueyed: heh.  well, we can get it fixed quickly.  :)
[19:43] <ssweeny> i heard a rumor that 8.04.1 point release will include the final ff3 (assuming it's out)
[19:44] <RainCT> (two "pycentral: pycentral pkginstall: not overwriting local files" errors were just reported)
[19:45] <leonel> jackster: I heard another rumor that 8.04 is released with firefox 3 beta 4 and will be easy to include  firefox 3 final when is released
[19:47] <RainCT> ah no
[19:50] <sebner> leonel: true
[21:34] <ScottK2> RainCT: The answer to your fusion-icon/python-central question is yes.
[21:38] <Zelut> is there a CLI equivalent of gdebi?
[21:39] <ScottK2> Zelut: To install a .deb file?
[21:39] <ScottK2> Zelut: dpkg -i filename.deb
[21:39] <ScottK2> It'll need sudo in front of it.
[21:40] <Zelut> ScottK2: but when that deb has unmet dependencies I would like them taken care of, which gdebi does.
[21:40] <ScottK2> Zelut: OK.  For that use sudo apt-get -f install
[21:41] <ScottK2> Two steps, but it gets you to the same place
[21:41] <Zelut> ScottK2: ahh, ok.. I suppose it would be nice if apt/aptitude had a --localinstall similar to yum.
[21:41] <Zelut> cut it down to one step and all.
[21:41] <ScottK2> It may, I've just never bothered.
[21:41] <Zelut> i've been searching for it but can't find anything.
[21:42] <Zelut> I have a co-worker bitching about yum is better (for that one reason), just trying to prove 'em wrong.
[21:44] <ScottK2> It's not an individual tool that's better or worse in my opinion, it's the packaging system.
[21:44]  * ScottK2 has used RPM based distros and doesn't plan on repeating the experience.
[21:45] <Zelut> ScottK2: +1
[21:45] <Zelut> I've yet been able to wrap my head around .deb packaging, but from what I do understand they seem more complicated, but not without merit.
[21:45] <Zelut> I've still had dependency hell with yum.. which kind of defeats the idea of yum.
[21:46] <rockstar_> Zelut, that's because debs have support for suggesting other packages to go along with the first package.
[21:47] <Zelut> rockstar_: right.  we've long had this battle at my office.  We have old-school RH guys vs these new-school Ubuntu guys.
[21:47] <Zelut> it always comes back to the package management
[21:48] <rockstar_> Man, I'm an old school Debian guy...
[21:48] <candrews> Howdy! I'm hoping someone here can re-sync revu's keyring
[21:48] <rockstar_> I don't know, packaging rpms is probably a little easier.  Debian's philosophy to the whole thing is the biggest difference.
[21:49] <Zelut> in my studying debian/ vs .spec the .rpm does seem easier, but not as robust as .deb can be.
[21:51] <ScottK2> Zelut: Debian predates Red Hat by two years if you want to compare old school.
[21:52] <Zelut> ScottK2: did not know that.  I knew they were the oldest, but didn't know it was that much of a gap.
[21:52] <slangasek> Red Hat is such an upstart
[21:52] <Zelut> unless we count SLS ;)
[21:53] <slangasek> rockstar_: and rpm packaging is crackful, I don't miss it at all :-)
[21:54] <Zelut> anyone know of any motu recipies that outline basic installing a few files, not requiring any compiling?
[21:54] <RainCT> ScottK2: it needs a rebuild? why?
[21:54] <Zelut> ie; I have a basic app that needs to put files in /usr/share/doc/app-name and another in /usr/bin, no compiling required.
[21:55] <geser> Zelut: does it have a Makefile?
[21:55] <ScottK2> RainCT: Because python-central doesn't use the pycentral directory any more.  It uses pyshared.
[21:55] <Zelut> geser: no..
[21:55] <RainCT> ScottK2: hm.. but I tried installing the .deb from the repos and here it works fine (and dpkg -L shows the pyshared directories)
[21:56] <RainCT> (although the file list on packages.ubuntu.com shows the old directories... :/)
[21:56] <Zelut> geser: I'm assuming I need to create one, but I've yet been able to find a good Makefile example using the 'install' command to place the file, which I assume is the appropriate way.
[21:56] <ScottK2> RainCT: Maybe it's been done already.
[21:57] <geser> Zelut: perhaps dh_installdirs and dh_install will help you
[21:58] <geser> Zelut: if not use mkdir and cp (or install) and create the wanted directory structure below debian/<packagename> and copy the files there
[21:58] <mario_limonciell> why even go that far?  just use a simple 2 line cdbs rules file and debian/install or debian/files to list where to put stuff
[21:59] <Zelut> mario_limonciell: because cdbs is voodoo? :)
[21:59] <mario_limonciell> bah black magic or not, it's easy
[22:00] <slangasek> until you deviate
[22:00] <geser> mario_limonciell: could you make an working example and add it to the wiki? this question was asked several times already
[22:00] <slangasek> then it's ~impossible
[22:00] <slangasek> but yes, cdbs should be adequate for this
[22:00] <mario_limonciell> the example i brought up last time i fielded this question was my ipod-convenience package
[22:01] <mario_limonciell> it installs a single script, a few symlinks, a man page and does a debconf question
[22:01] <Zelut> basically I have four file: app.sh, COPYING, Changelog and README.  I need the last three in /usr/share/doc and the first would go into /usr/bin
[22:01] <mario_limonciell> very straightforward
[22:02] <slangasek> are you trying to make a policy-compliant package?
[22:02] <Zelut> slangasek: ideally, yes, but I'll start with *a* package to learn :)
[22:02] <slangasek> depending on what COPYING is, you should not install it, but instead have a file debian/copyright which lists the copyright information and refers to /usr/share/common-licenses/
[22:03] <Zelut> COPYING is just the GPLv2.  I guess you're right, I don't really need to duplicate that.
[22:05] <slangasek> in that case, if you're using cdbs and create debian/copyright appropriately, no further handling for that is needed
[22:05] <Zelut> but, again, I have no idea what I'm doing despite going through the packaging guide a half-dozen times.
[22:05] <slangasek> then you just need debian/$package.install as mario_limonciell mentions, listing the packages and their target dirs
[22:06] <mario_limonciell> Zelut, apt-get source ipod-convenience (on a hardy box).  it is very similar to your type of package, and should be a good eye opener for what you need to do
[22:06] <mario_limonciell> it's GPL, so you can model the debian/copyright
[22:08] <Zelut> mario_limonciell: I'll give it a try. I've avoided cdbs because its voodoo but, hell, it can't hurt considering I can't get the traditional method to stick.
[22:11] <Zelut> mario_limonciell: so you've created the additional file structure and then just outlined that in the install file?
[22:11] <mario_limonciell> yeah i thought that was the easier route
[22:12] <mario_limonciell> except for docs, i list those explicitly if need be
[22:12] <mario_limonciell> man pages etc
[22:12] <mario_limonciell> putting the file structure in place this way, you don't need to change debian/install if you decide to put more stuff in ever
[22:13] <mario_limonciell> which i would imagine works around what slangasek was referring to when he said you deviate
[22:14] <slangasek> mario_limonciell: by "deviate" I mean, "need to override something that cdbs considers a sensible default but is wrong about" :)
[22:14] <mario_limonciell> ah yeah
[22:14] <RainCT> ScottK2: i'm not sure what to do... well, thanks
[22:21] <RainCT> ScottK2: I've attached a newly build .deb and asked for feedback, let's see if it really just needs a rebuild :)
[22:21] <RainCT> good night all
[22:21] <ScottK2> RainCT: Did/does another package perhaps provide some of the files that generated the errors?
[22:24] <RainCT> ScottK2: You mean if there's a conflict with another package? I don't think so..
[22:24] <RainCT> (it doesn't say what file(s) is the problem)
[22:25] <ScottK2> OK.
[22:25] <ScottK2> Just throwing out ideas.
[22:26] <slangasek> are the kde folks aware that kdepim-kde4 currently FTBFS?
[22:28] <ScottK2> slangasek: The package probably shouldn't even exist as kdepim wasn't included in KDE 4.0.  I'd vote for FTBFS as a feature
[22:28] <slangasek> ScottK2: well, it's not out-of-date binaries, it just FTBFS when I try to rebuild it to get rid of the libldap2 dependency :)
[22:28] <slangasek> can we remove it from the archive?
[22:29] <ScottK2> slangasek: I just asked about it in #kubuntu-devel.
[22:29]  * ScottK2 has been focusing on KDE3, so is not sure.
[22:29] <slangasek> ok
[22:33] <ScottK2> slangasek: Current opinion in #kubuntu-devel is it can go.  I'd suggest checking with Riddell though.
[22:33] <slangasek> ok, thanks
[22:34] <slangasek> hah, missed him by 5 minutes, grr
[22:34]  * RainCT wonders what happened with the idea to 7zip the 'Packages' files
[22:35] <jpatrick> slangasek: well, it's 4:3.97.0-0ubuntu2 which is well out of date and upstream hasn't finished up with it yet
[22:41] <blueyed> keescook: bug 207579 has (tested) fixes attached and I've reported it to Debian.
[22:41] <ubotu> Launchpad bug 207579 in dspam "dspam-3.6.8-5ubuntu1.2 cronjob fails for libdspam7-drv-mysql" [Medium,In progress] https://launchpad.net/bugs/207579
[22:44] <keescook> blueyed: okay, thanks, I'll get them published
[22:46] <Fujitsu> Didn't Debian already fix that?
[22:46] <nixternal> slangasek: you can wipe kdepim-kde4 and kphotoalbum-kde4 and not worry about a thing
[22:47] <nixternal> neither of them work
[22:47] <nixternal> kphotoalbum-kde4 was accidentally tagged for 4.0.0 release, and kdepim-kde4 is probably a 3.94 release, an alpha or beta release I am sure
[22:52] <slangasek> nixternal: well, ScottK2 says I should check with Riddell. :)
[22:53] <nixternal> slangasek: Riddell just said go ahead in -devel
[22:53] <slangasek> ok, cool
[22:53] <nixternal> both are universe anyways, Riddell is above that :p
[22:53] <nixternal> haha
[22:54] <slangasek> w00t, then I can get rid of openldap2 today \o/
[22:55] <Riddell> ack
[22:56] <slangasek> Riddell: no changes to the kubuntu-kde4 seeds needed to account for this?
[22:56] <nixternal> nope
[22:56] <slangasek> @whee
[22:57] <nixternal> haha, easy job and thanks for doing that slangasek
[22:57]  * nixternal gets to close boogs with "muhahhaha INVALID!"
[22:58] <slangasek> my pleasure, it means one less place where my name is still attached to openldap2 :)
[22:58] <nixternal> haha
[23:26] <alex_mayorga> hi, any help to fix bug 198481
[23:26] <ubotu> Launchpad bug 198481 in bluez-gnome "[needs-packaging] bluez-gnome-0.25 fixes bluetooth-applet crashed with SIGSEGV" [Medium,Confirmed] https://launchpad.net/bugs/198481
[23:26] <alex_mayorga> or help on getting on track to do it myself
[23:26] <alex_mayorga> or try at least :)
[23:59] <Amaranth> crap launchpad is going down
[23:59] <Amaranth> wait, good thing, no more compiz bug reports


[00:40] <Akiva-Thinkpad> hey guys
[00:40] <Akiva-Thinkpad> mx4 will house Ubuntu touch :)
[00:40] <Akiva-Thinkpad> coming out in december
[18:15] <genii> If anyone's wondering, Yes, I'll be at the Toronto Jam
[23:26] <Akiva-Thinkpad> global jam ftw!
[23:26] <Akiva-Thinkpad> are you guys busy with it atm?


[01:14] <Rinchen> beuno, nixternal popey have time to test something for me? proof of concept
[01:15] <Rinchen> I was thinking about our conversations about digg (and yes you too LaserJock) vs slashdot style
[01:15] <Rinchen> and found that you can configure digg to work like slashdot
[01:15] <Rinchen> with an upcoming stories queue but editors have to promote to front page
[01:16] <Rinchen> so I tried it to see if it works.
[01:16] <Rinchen> it does:  http://news.ubuntu-rocks.org/
[01:16] <Rinchen> despite what it says it's a proof of concept
[01:16] <LaserJock> hmm, interesting
[01:17] <Rinchen> it took me 5 minutes to setup
[01:17] <Rinchen> as you can tell from the basic theme
[01:17] <LaserJock> yeah, brown digg
[01:17] <LaserJock> that's pretty cool
[01:18] <LaserJock> what do you think of http://news.opensuse.org/
[01:18] <LaserJock> ?
[01:18] <LaserJock> that's basically what we're doing now
[01:18] <LaserJock> just looks maybe better
[01:18] <LaserJock> but there's votes
[01:18] <LaserJock>  and comments
[01:19] <Rinchen> I think the suse site is pretty :-)
[01:19] <LaserJock> hmmm
[01:19] <LaserJock> what if we had both?
[01:20] <LaserJock> like fridge.ubuntu.com/news was digg
[01:20] <LaserJock> with like the top 5 from there put in a sidebare on fridge.ubuntu.com
[01:20] <LaserJock> I just can't help but think of the digg stuff as being amatuerish looking
[01:21] <LaserJock> maybe I'm just getting old
[01:22] <Rinchen> amateur yes, by design.
[01:29] <LaserJock> I don't mind some amateur bits
[01:29] <LaserJock> but I rather see Fridge as a bit more professional
[08:54] <mdke> LaserJock: i guess you should ping jono about edubuntu being missing
[08:54] <Burgundavia> ugh, bloody dvd paused halfway
[08:54] <Burgundavia> no disk space, so no compiz article until tomorrow morning
[08:59] <LaserJock> mdke: hmm, yeah
[05:49] <newz2000> If I try out the iCal/google calendar fix real quick on the fridge would anyone here have some time to do testing to let me know if it needs backed out or if things look OK?
[06:11] <Rinchen> it doesn't fail for me since I use google
[06:11] <Rinchen> imbrandon, nixternal popey  might be able to help
[06:12] <popey> hello
[06:12] <newz2000> Rinchen: you're able to see fridge events in your google calendar?
[06:12] <Rinchen> newz2000, oh doh
[06:12] <Rinchen> no
[06:12] <Rinchen> I can't
[06:12] <Rinchen> did you just change that?
[06:12] <Rinchen> let me try that
[06:12] <newz2000> no, I don't want to until I know someone can test it
[06:12] <popey> i use evolution, would be good to test
[06:12] <newz2000> yes
[06:12] <newz2000> ok, if you two have a min, I'll make the change now
[06:12] <popey> ok
[06:13] <popey> tell me what to click
[06:13] <newz2000> let me get the fix in place real quick
[06:13] <Rinchen> ok
[06:13] <Rinchen> I can confirm it's not working now
[06:14] <popey> what isn't working? :)
[06:14] <Rinchen> newz2000, ping me when you're ready so my attention is ddrawn here
[06:15] <newz2000> popey, Rinchen: can you guys check to see if you can see events now from the iCal feed?
[06:15] <newz2000> popey: was your iCal feed for fridge events working before?
[06:16] <popey> dunno, i still don't know what the broken functionality was
[06:16] <newz2000> no events would show up
[06:16] <popey> http://fridge.ubuntu.com/event/ical in that?
[06:16] <newz2000> you'd add the ical feed but google cal would show now events
[06:16] <newz2000> popey: yes
[06:17] <popey> well that ical file looks good
[06:17] <newz2000> does your calendar like it?
[06:17] <Rinchen> not working here. let me readd the feed
[06:18] <popey> yes it imports to evolution
[06:18] <popey> but it looks screwy
[06:18] <popey> some meetings last two days
[06:18] <newz2000> hate to be in that meeting
[06:18] <popey> :)
[06:19] <newz2000> popey: did this just change with my update?
[06:19] <popey> dunno, i didn't try it before becasue I didn't know what was broken :S
[06:19] <popey> sorry
[06:21] <newz2000> I don't think that fixed it
[06:22] <Rinchen> readded and didn't work
[06:22] <newz2000> that's it, drupal's going into the trash, we're switching to dreamweaver
[06:22] <newz2000> ;-)
[06:25] <popey> *shudder*
[06:26] <newz2000> ok, I reverted to the old ical.inc. I'll have to research this more a little later


[01:50] <TheMuso> darkxst: Did you look in ~/.cache/upstart?
[01:54] <darkxst> TheMuso, yes, but couldnt see anything showing the actual events etc
[01:56] <TheMuso> Hrm ok, can't quite remember what your original query was and what events you are after...
[01:56] <TheMuso> So I cannot be of any more help sorry.
[01:56] <darkxst> TheMuso, gnome-shell is not getting shutdown cleanly
[01:57] <darkxst> X gets taken away, then gnome-session trys to respawn gnome-shell, which fails, fires the fail-whale and then disables all shell extensions
[01:59] <TheMuso> Ah...
[01:59] <TheMuso> No idea how upstart is supposed to do things on teardown.
[02:04] <darkxst> seems like it might be happening under unity as well, just there probably aren't any side-effects there
[02:05] <TheMuso> I was thinking the same thing actually.
[02:20] <TheMuso> darkxst: I didn't think GNOME shell used upstart user sessions.
[04:23] <darkxst> TheMuso, yeh it has ever since Unity switch over (they share gnome-session)
[13:54] <larsu> desrt: the dispose thing seems to have been reverted: https://bugzilla.gnome.org/show_bug.cgi?id=711807
[14:10] <seb128> Laney, sorry, unassigned that units bug from you, assigning it back ;-)
[14:10] <seb128> (launchpad edit conflict)
[14:12] <qengho> seb128: Do you mind uploading a few packages? Do you prefer UDD branches or debdiffs?
[14:13] <seb128> qengho, can you use the sponsoring queue?
[14:13] <larsu> desrt: sounds like this is a fairly large rework of gdbusconnection's closed state handling
[14:13] <seb128> I can pick some items from there
[14:13] <seb128> debdiff is fine
[14:14] <desrt> i want a cinnamon bun
[14:16] <desrt> a really delicious good one
[14:16] <larsu> stop teasing
[14:18] <AerialSonic> hello
[14:54] <Laney> mvo_: https://launchpad.net/~laney/+archive/ubuntu/gi BUILD ALL THE THINGS
[14:54]  * Laney whispers (also, I forgot again)
[15:43] <mvo_> Laney: woah \o/
[15:43] <mvo_> Laney: impressive, 158!
[15:44] <mvo_> Laney: need help with fixing some of them? but I guess you guess have a good handle on this from the look of it
[15:44] <Laney> mvo_: I'll merge/sync/whatever the ones that are fixed in Debian
[15:45] <Laney> if you want to loo kat the Ubuntu specific ones, feel free
[15:45] <mvo_> Laney: thanks!
[15:45] <Laney> e.g. click
[17:25] <BigWhale> Are online results in Dash now disabled by default or not?
[17:26] <willcooke> BigWhale, no
[17:26] <czajkowski> oh thank you desktop team utopic is rather nice :)
[17:26] <czajkowski> having viber work out of the box on it is rather sweet
[17:26] <willcooke> czajkowski, glad to hear it :)
[17:26] <czajkowski> willcooke: hello you!
[17:26] <BigWhale> willcooke, oh... There were news that they are disabled. Wasn't sure. Thanks. :)
[17:26] <willcooke> hihi
[17:27] <willcooke> BigWhale, it's something which we're still working out.
[17:28]  * willcooke off to a meeting
[17:32] <BigWhale> willcooke, regardless, congrats on the new release.
[17:33] <willcooke> thx BigWhale
[17:33] <BigWhale> It seems I'm scheduling another release party.
[18:54] <larsu> desrt: https://bugzilla.gnome.org/show_bug.cgi?id=721921
[18:55] <Laney> ogra_: dbus-property-service and autopilot-touch have a file conflict in utopic
[19:21] <Sweet5hark> .
[19:45]  * achiang sighs
[19:46] <achiang> lightdm (or compiz) just lost its mind, and wouldn't let me log back into a locked desktop
[19:46] <achiang> mterry: you ever seen anything like that?
[19:46] <mterry> achiang, on your desktop?
[19:46] <achiang> mterry: yes
[19:46] <mterry> achiang, what happens?  you log in and it kicks you out?
[19:47] <achiang> mterry: i'm on a dual-head setup, 14.04.1, using standard VGA (not anything fancy like hdmi or whatever)
[19:47] <mterry> achiang, 14.10 came out, didn't you hear?  :P
[19:50] <achiang> mterry: no, i walked away from machine, the lockscreen did the right thing and turned on, but refused to display a password entry box
[19:50] <achiang> mterry: it displayed "something" where i would normally see my long user name and a password entry
[19:51] <achiang> basically, a blank box
[19:51] <achiang> it was awesome
[19:52] <mterry> achiang, that sounds like a unity7 issue then -- it has an integrated lockscreen that it uses
[19:52] <mterry> achiang, I've not heard of it, but maybe seb128 has?
[19:52]  * seb128 denies knowing anything
[19:52]  * seb128 reads
[19:53] <seb128> Trevinho_, ^
[19:53] <seb128> I think Trevinho_ has fixes for some of those issues
[19:53] <seb128> it didn't make into an upload yet though
[19:54] <Trevinho_> achiang, seb128: they should have been fixed in SRU coming
[19:54] <Trevinho_> achiang: give the ubuntu-proposed repo a try
[19:54] <Trevinho_> or they are in utopic only (to be SRUed)
[20:05] <ogra_> Laney, well, ithas conflicts and replaces ...
[20:05] <ogra_> Laney, and it should not be installed on non-phone envs anyway
[20:05] <Laney> they are wrong, you missed out the 0ubuntu1 and also you didn't upload a matching version to drop the file
[20:05] <Laney> seb128: lp:~/ubuntu-system-settings/formatsize please to check
[20:05] <ogra_> where do you see that actually ? when upgrading your utopic phone with adb ?
[20:05] <Laney> don't know, willcooke showed me it
[20:06] <Laney> but you can get it if you try to install the packages together
[20:06] <Laney> so it is just a straight up bug
[20:06] <ogra_> indeed
[20:06] <ogra_> i just dont get why you would install them outside of a phone, they are useless
[20:06] <Laney> he was on desktop next
[20:06] <ogra_> it shouldnt be on there
[20:06] <Laney> doesn't matter
[20:06] <ogra_> so thats another bug
[20:07] <ogra_> can you file both and assign me ?
[20:34] <larsu> seb128: evince bug is hard
[20:34]  * larsu thinks maybe a gtk+ bug
[20:34] <seb128> larsu, upstream issue?
[20:34] <seb128> k :-/
[20:34] <larsu> maybe?!
[20:34] <seb128> Company might have an idea?
[20:34] <larsu> gtk_widget_show(popup) is definitely called
[20:34] <larsu> unlikely...
[20:34] <larsu> thinking it might be a desrt issue
[20:34] <seb128> should be easy to have a small testcase with menu + popup
[20:35] <seb128> and get desrt to try on his fedora
[20:35] <larsu> good idea
[20:51] <larsu> it is a desrt bug


[17:28] <ion> It’s awesome you can run ‘restart gdm’ from an X terminal and still have gdm come back up, as opposed to ‘service gdm restart’ back when gdm was an init.d service. :-P
[17:33] <Keybuk> :p
[17:34] <ion> Of course, setsid or screen worked as a workaround, but nevertheless.
[17:52]  * Ng curious why -n isn't the default for start/stop
[17:52] <Keybuk> because that would be wrong
[17:53] <ion> Indeed
[17:53] <Ng> I'm assuming that start is an appropriate command to use as a substitude for /etc/init.d/blah start
[17:54] <Ng> if it is, then -n should be the default because init scripts don't block forever, right? :)
[17:55] <ion> init.d scripts block until they inform you about whether the action you requested succeeded.
[17:55] <Ng> perhaps the upstart jobs for eucalyptus are just Wrong[tm], but it kinda seems like it's a bit of a gamble which services will return be to a prompt when I do start foo, and which will just wait forever
[17:55] <Keybuk> Ng: start doesn't block forever either
[17:56] <Keybuk> start only blocks until the service is *running*
[17:56] <Keybuk> and that's why -n isn't the default
[17:56] <Keybuk> start dbus
[17:56] <Keybuk> start hal
[17:56] <Keybuk> works
[17:56] <Keybuk> start -n dbus
[17:56] <Keybuk> start -n hal
[17:56] <Keybuk> doesn't
[17:56] <Keybuk> (dbus isn't yet listening when you try and start hal)
[17:56] <Ng> Keybuk: how does it determine the running state?
[17:56] <Ng> I'm just curious because I did "start eucalyptus-cloud" and I want my shell prompt back ;)
[17:56] <Keybuk> Ng: exec() caused a close-on-exec file descriptor to be closed
[17:57] <Keybuk> briefly looking here, but the eucalyptus jobs seem to have code to poll the service until it's actually running
[17:57] <Keybuk> so I assume because eucalyptus is still starting
[17:57] <Ng> hmm
[17:57] <Ng> fair enough
[17:58] <Ng> that's quite annoying, but clearly not your problem :)
[17:58] <Keybuk> if you look at /etc/init/eucalyptus-cloud.conf you'll see it has a post-start script
[17:58] <Keybuk> mdz has put that in there deliberately
[17:58] <Ng> it all starts up fine if you just let it, or at least it did in jaunty when the init scripts just forked everything off and let it sort itself out
[17:58] <Ng> but that's not your problem, so I will take my whining elsewhere. thanks :)
[18:00] <Ng> oh! there was one other tiny little whine I wanted to raise before filing a bug :)
[18:00] <Keybuk> I think you're probably supposed to use "start eucalyptus" looking at it
[18:01] <Ng> I was wondering if the output from start/stop/status could be made a little more verbose
[18:01] <wasabi_> Oh looky!
[18:01] <wasabi_> We're actually using upstart now!
[18:02] <Ng> (mainly so it would explicitly say what the current state is, atm i think it's prone to interpretation)
[18:02] <Keybuk> it does explicitly say?
[18:02] <Keybuk> warcraft scott% status dbus
[18:02] <Keybuk> dbus start/running, process 821
[18:03] <wasabi_> This is very refreshing.
[18:03] <wasabi_> To see all these .conf files.
[18:03] <wasabi_> Though somehow fsck runs twice on boot for me. Once after the file systems are mounted.
[18:03] <wasabi_> And then it fails.
[18:03] <Keybuk> wasabi_: odd.
[18:03] <Ng> Keybuk: I was thinking that just sprinkling in a few more words would make it much clearer.. "dbus is running as process 821"
[18:03] <Keybuk> Ng: the status output is intended to be grep/sedable
[18:03] <wasabi_> Guessing the mount process is kicked off by a successful fsck
[18:03] <wasabi_> And it mounts things other than the devices that was fscked
[18:04] <wasabi_> 'guessing'.
[18:04] <Keybuk> Ng: not sure I follow though, maybe I'm used to it, but it seems fairly clear
[18:04] <Keybuk> the only confusing bits come when you get post-start scripts ;)
[18:05] <Keybuk> eucalyptus-cloud start/post-start, (post-start) process 821
[18:05] <Keybuk> do you see something like that?
[18:06] <Keybuk> actually, I think that's even clear now
[18:06] <Keybuk> eucalyptus-cloud start/post-start, process 821
[18:06] <Keybuk> no?
[18:06] <ion> keybuk: How about cmd="$(eval start --sh foo)"; eval "$cmd"; printf "%s, %s\n" "$upstart_status" "$upstart_pid"? :-P
[18:06] <Ng> Keybuk: so like just now I had it stopped and it said "eucalyptus-cloud: stop/waiting"
[18:06] <Keybuk> ion: ?
[18:06] <Keybuk> Ng: right...
[18:06] <ion> Whoops, cmd="$(start --sh foo)"
[18:06] <Keybuk> Ng: that seems to be clearly "it's stopped, and I'm waiting for you tell me otherwise" ?
[18:06] <ion> An alternative to seding the start output: have it output sh commands that set environment variables
[18:07] <Keybuk> ion: dbus-send is your friend ;)
[18:07] <Ng> Keybuk: isn't it always waiting to be told something? I was wondering if maybe there could be "stopping" and "stopped"
[18:08] <Keybuk> ion:
[18:08] <Keybuk> warcraft scott% sudo dbus-send --address=unix:abstract=/com/ubuntu/upstart --type=method_call --print-reply /com/ubuntu/Upstart/jobs/dbus/_ org.freedesktop.DBus.Properties.Get string:com.ubuntu.Upstart0_6.Instance string:processes
[18:08] <Keybuk> method return sender=(null sender) -> dest=(null destination) reply_serial=1
[18:08] <Keybuk>    variant       array [
[18:08] <Keybuk>          struct {
[18:08] <Keybuk>             string "main"
[18:08] <Keybuk>             int32 821
[18:08] <Keybuk>          }
[18:08] <Keybuk>       ]
[18:08] <Keybuk> --

[18:08] <ion> I wish dbus-send could output data in format one can easily parse from a sh script. :-P
[18:08] <Keybuk> Ng: no, the only two times it's ever only waiting for commands are "waiting" and "running"
[18:09] <Keybuk> ion: you could write such a tool
[18:09] <ion> Sure
[18:09] <Keybuk> Ng: it's a bit subtle
[18:09] <Keybuk> for example
[18:09] <Keybuk> consider the state "stop/running" :)
[18:09] <Keybuk> and "start/waiting"
[18:09] <Keybuk> they do exist, they're just a bit brief
[18:09] <Ng> stop/running makes no sense to my human eyes ;)
[18:09] <Keybuk> sure
[18:09] <Keybuk> someone told the service to be stopped
[18:09] <Keybuk> but it's still running
[18:09] <Ng> I know what you mean, but I am a simple human wanting to know what my services are doing
[18:09] <ion> ng: Goal: stop, status: running
[18:09] <Ng> I'm all for a seddable/greppable interface, but maybe some extra words would help
[18:10] <Keybuk> simple humans can use the nice GUI I'll write one day ;)
[18:10] <Ng> I'm a simple human on a server :)
[18:10] <Keybuk> Ng: though if you can come up with output that makes sense, I'm all ears ;)
[18:10] <Keybuk> the problem is that words like "starting" and "stopping" are *VERY* specific in Upstart world
[18:10] <Keybuk> so having upstart use them badly would be confusing
[18:11] <Keybuk> I guess you'd want
[18:11] <Keybuk> status --dummy dbus
[18:11] <Keybuk> dbus is running
[18:11] <Keybuk> status --dummy apache
[18:11] <Keybuk> apache will be stopped
[18:11] <Keybuk> status --dummy hal
[18:11] <Keybuk> hal will be started
[18:11] <Keybuk> status --dummy obby
[18:11] <Keybuk> obby is being restarted
[18:11] <Keybuk> ?
[18:12] <Ng> that seems better, although "will be" makes me wonder what those are conditional upon
[18:12] <Keybuk> (along with "is not running", those are probably the basic meta-states)
[18:12] <ion> gdm: goal=start status=running process=42 – how about that for both humans and parsing?
[18:12] <Keybuk> Ng: if you do "start apache" (or someone else does)
[18:12] <Keybuk> then it'd be "is being restarted" :p
[18:14] <Ng> how abouy just having an option that spits out machine-readable status, otherwise plain english on the assumption that a simple human wants to know if something is broken?
[18:14] <Ng> "foo is running as process N", "foo is not running", "foo is starting", "foo is stopping" kidna thing
[18:14] <Keybuk> it depends on how much information you think the single humans want to know
[18:14] <Keybuk> I could kill both birds with one stone
[18:14]  * Keybuk has AN IDEA
[18:15] <Keybuk> how about, if it's running (and your on a suitable terminal)
[18:15] <Keybuk> the entire text is GREEN
[18:15] <Keybuk> and if it's falling over or stopped or whatever it's RED
[18:15] <Keybuk> and if it's restarting, it's ORANGE
[18:15] <Keybuk> then you can glance at the colour, and not read the scary text ;)
[18:16] <Ng> colour is good for me, I have advanced terminals and no vision defects
[18:16] <Ng> I suspect there is a middle ground that just adapts what you have to be more definitive
[18:17] <Ng> what about changing the tense of the first state bit?
[18:17] <Ng> start->started, stop->stopped
[18:17] <Ng> "stopped/waiting" seems clearer than "stop/waiting"
[18:17] <Keybuk> again, those are very specific words in upstart parlance
[18:17] <Keybuk> a job can be stop/stopped
[18:17] <Keybuk> and start/stopped
[18:17] <Keybuk> so, you'd have the very very strange output
[18:18] <Keybuk>   started/stopped
[18:18] <Keybuk> and
[18:18] <Keybuk>   stopped/started
[18:18] <Keybuk> ;)
[18:18] <Ng> start/stopped is very strange output
[18:18] <Ng> imho
[18:18] <Keybuk> actually that's very meaningful
[18:18] <Keybuk> it tells you that the service is going to be restarted, most likely as a result of a job with "... on stopped YOURJOB" in its conf
[18:18] <ion> I’m still proposing saying “this is the *goal* and this is the *status*” in the output. :-P
[18:19] <Ng> if I read a bunch of upstart docs. I hope I'm not seeming obtuse, I'm deliberately tryign to be a busy sysadmin who loves the idea of upstart, but hasn't read the docs
[18:19] <Keybuk> but yes
[18:19] <Keybuk> I do appreciate your point ;)
[18:19] <Keybuk> the current status command outputs the exact upstart goal/state combo
[18:19] <Keybuk> it should simplify that
[18:20] <Keybuk> you don't need to know the difference between start/starting, start/spawned, start/started & start/running (or stop/stopping, stop/killed, stop/stopped & stop/waiting)
[18:20] <Keybuk> not unless you're debugging anyway
[18:20] <Ng> yeah
[18:20] <Ng> I definitely want to be able to choose to see those
[18:20] <Keybuk> the simplified model actually makes this simpler anyway
[18:20] <Ng> but mostly I just want someone to hug me and tell me apache is running properly ;)
[18:20] <Keybuk> since it reduces the states to starting, started, stopping & stopped anyway
[18:21] <Keybuk> (intermediate states)
[18:21] <Keybuk> Ng: I guess you do want to know whether apache is still starting or not
[18:21] <Ng> sure
[18:22] <Ng> and by "sure" I mean "definitely, that's the kind of newfangled awesomeness I want from upstart"
[18:22] <Keybuk> could you file an upstream bug?
[18:23] <Ng> with pleasure, although it'll be the other side of hometime and dinner :)
[18:23] <Keybuk> np
[18:23] <Ng> thanks :)
[19:09] <PovAddict> can I use upstart on debian? :]
[19:14] <sadmac2> PovAddict: be our guest :)
[19:14] <sadmac2> PovAddict: they don't ship it yet (soon) but there's no reason it won't work if you want to hammer it in there yourself.
[19:50] <Keybuk> no hammer required
[19:50] <Keybuk> I believe it's as simple as apt-get install upstart
[19:51] <sadmac2> Keybuk: really? I thought they just decided to use it.
[19:52] <Keybuk> sadmac2: it's been installable for yeras
[19:52] <Keybuk> the decision was about it being the default
[19:52] <sadmac2> ahh, debian. Is there anything they won't make pluggable?
[19:53] <sadmac2> I guess if you ship two completely different kernels, shipping two init systems isn't a stretch
[20:12] <wasabi_> expect fork. What's that do?
[20:12] <wasabi_> Tracks down the pid's using ptrace?
[20:14] <wasabi_> Also... why do we still spawn recovery consoles asking for the root password?
[20:14] <wasabi_> Since we don't even set a root password.
[20:14] <wasabi_> That would seem braindead at this point.
[20:14] <ion> Huh? My recovery anything doesn’t as for root password.
[20:14] <wasabi_> root@station-1:~# sulogin
[20:14] <wasabi_> Give root password for maintenance
[20:14] <wasabi_> (or type Control-D to continue):
[20:14] <wasabi_> Oh maybe it only does it if you have one. :)
[20:15] <ion> Well, duh :-)
[20:15] <wasabi_> Brain fart from a time long past.