[03:09]  * MarkDude wonders where seidos is, and if he's ok
[03:09] <MarkDude> Do one of our bots have a lastseen?
[03:42] <jtatum> oh yeah, I remember seidos
[03:43] <jtatum> didn't he change his nick to something?
[03:45] <jtatum> darth bot doesn't have a seen database enabled
[04:12] <MarkDude> He went off on a Buddhist retreat, that was last I heard
[04:12]  * MarkDude cant rememebr what he changed it to
[04:13] <MarkDude> jtatum: Geeknic Sat the 18th in Walnut Creek
[04:13] <MarkDude> And we have the dates for the a few more til August
[04:13] <MarkDude> There will be a vote for next months Geeknic location
[04:13] <MarkDude> Hopefully one in Santa Cruz also
[04:14] <jtatum> ooh, that'd be nice. walnut creek is pretty hard for us to make :(
[04:16] <MarkDude> Yep
[04:17] <MarkDude> So thats why we are doing a mix of places we know well , and allowing June to be user input helps
[04:17] <MarkDude> It needs to be either South Bay, or at most Oakand
[04:17] <MarkDude> Silicon Valley would make sense
[04:18] <MarkDude> But we will use civs poll
[04:18] <MarkDude> Is there an ical or something similar for Ubuntu Hours?
[04:19]  * MarkDude is working on FOSS calendar for BAy
[04:20] <MarkDude> https://www.google.com/calendar/ical/tuxwingsgroup%40gmail.com/public/basic.ics
[04:20] <darthrobot> Content type: [text/calendar; charset=UTF-8]
[16:24] <raevol> anyone have experience with xen?
[16:45]  * MarkDude does not. Thinks Lars Kurth - from Xen, is one of the coolest FOSS folks out there.
[16:45]  * MarkDude is sure he can direct you
[16:45] <MarkDude> :)
[16:46] <akk> I tried to run it once but didn't have the right CPU flags on any of my computers.
[16:46] <geofft> I've run Xen before.
[16:47] <geofft> What are you curious about?
[16:53] <raevol> geofft: when i create guests, they can't format their own hard drive during install
[16:54] <raevol> geofft: this is a new issue, i've been messing with my storage pools trying to add more space, and before that, everything was fine, have 2 guests running
[16:54] <raevol> those guests can write to their own disks just fine
[22:41] <akk> Why does do-release-upgrade from pangolin tell me No new release found?
[22:45] <akk> Apparently I have to use -d even to get real releases? Pfft, and then it'll only go to quetzal, not to ringtail?


[02:52] <lotuspsychje> good morning
[03:15] <guiverc> lotuspsychje, if you've got a few secs & don't mind, wanna look at https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1907920 and is it worth me responding, or would you just ignore.. (the discussion is more rant b/c OP didn't note EOL, and mirrors can drop anytime AFTER eol etc)
[03:16] <guiverc> I'm happy to respond.... just not sure it's worth it (it's a buge report, and response won't be about a bug)..
[03:17] <guiverc> s/buge/bug & other usual errors I make
[03:18] <lotuspsychje> guiverc: think you did what was right, filter and prepare better for the devs, i would let them to decide in this stage
[03:32] <guiverc> thanks ... nah I wanna forget it.. replied anyway
[03:37] <lotuspsychje> ok
[07:11] <ducasse> good morning
[08:36] <mertgor> hi people
[08:45] <lotuspsychje> hey web mertgor
[08:45] <lotuspsychje> wb
[08:46] <mertgor> lotuspsychje: How are you doing ?
[08:46] <lotuspsychje> all good here ty, and yourself?
[08:47] <mertgor> Very well just joined to the network
[08:47] <lotuspsychje> great
[08:50] <lotuspsychje> mertgor: did you find a contribute direction yet you feel you want to help with?
[08:52] <mertgor> Yes
[08:52] <mertgor> I focused on cjdns and yggdrasil projects
[08:52] <mertgor> and in general Cloud Computing
[08:52] <mertgor> Technical writing is first
[08:53] <mertgor> lotuspsychje: What is your favorite applicaton ?
[08:54] <lotuspsychje> mertgor: i run computer business at home with ubuntu LTS and samsung ssd's inside
[08:54] <mertgor> me too
[08:55] <mertgor> My favorite applicaton is GNU Emacs
[08:55] <lotuspsychje> mertgor: i always install; sudo apt install vlc preload stacer gnome-tweaks haveged hexchat qbittorrent
[08:55] <lotuspsychje> as base applications
[08:56] <mertgor> let me check qbittorent
[18:45] <lotuspsychje> jeremy31: that logic would make sense as it works on 5.4 -53
[18:45] <lotuspsychje> and lower
[18:47] <jeremy31> lotuspsychje: another Mediatek with issues on 56 but works on 54 https://forums.linuxmint.com/viewtopic.php?p=1936733#p1936733
[18:48] <jeremy31> Bug 1906770
[18:51] <lotuspsychje> gonna file a new bug jeremy31
[18:52] <jeremy31> The guy with Mint will have issues with the 5.10 kernel with the Nvidia video
[19:01] <lotuspsychje> jeremy31: bug #1907984
[19:04] <jeremy31> If the changes were made in /kernel/drivers/net/wireless/mt76 they could have affected both mt7610U and mt7612U devices
[19:05] <lotuspsychje> i filed a bug against this same dongle on 18.04 jeremy31 and HWE made it work again
[19:06] <jeremy31> Over 200 commits to mt76 upstream since July
[19:07] <lotuspsychje> jeremy31: bug #1852978
[19:08] <lotuspsychje> yikes
[19:10] <lotuspsychje> jeremy31: but that doesnt explain why the dongle works on my own laptop on -58
[19:14] <lotuspsychje> jeremy31: on my laptop; https://dpaste.com/FXJX7687P
[19:15] <lotuspsychje> weirdness
[20:45] <JanC> remember WiFi depends on both a radio chip and a networking chip, and you need drivers to support both...
[20:46] <jeremy31> JanC: I found what fixes lotus' in 58 and breaks the mt7612 https://git.launchpad.net/~ubuntu-kernel/ubuntu/+source/linux/+git/focal/commit/drivers/net/wireless/mediatek/mt76?id=03db30eca2ae095e035943305f332e2d44d3b4a4
[22:46] <jeremy31> Subscribed the ubuntu-discuss team to a couple Mediatek USB wifi bugs


[07:43] <magicaltrout> anyone around who can provide some interface writing support
[07:43] <magicaltrout> or are you all in Pasadena?
[09:08] <magicaltrout> babbageclunk: fancy explaining some interface stuff that is clearly very simple but my brain can't process?
[09:09] <babbageclunk> um, I'll have a go! Not very familiar with those bits myself yet.
[09:09] <magicaltrout> lol
[09:09] <magicaltrout> well you're my only hope... no pressure
[09:09]  * babbageclunk girds loins
[09:10] <magicaltrout> anyway my idea is pretty simple... I want to create a generic JDBC interface because a bunch of services provide JDBC connections and apps like Saiku can consume JDBC connection info
[09:10] <babbageclunk> ok
[09:10] <magicaltrout> and all jdbc connections are basically the same, username, password, class and url
[09:10] <babbageclunk> sure
[09:10] <magicaltrout> so...
[09:11] <magicaltrout> http://pastebin.com/Ewpg03nM ignore the fact this is mid munging from another interface I wrote
[09:11] <magicaltrout> I want to write the provides side of the interface
[09:11] <magicaltrout> and my idea is the charm, be it, mysql, drill, postgres etc would provide a connection string and other metadata
[09:11] <magicaltrout> but where I'm struggling is in my understanding of charms <-> interfaces
[09:12] <magicaltrout> how do I tell my interface to look up a variable from my providing charm?
[09:12] <magicaltrout> the only interface stuff I've done so far has been to get unit info etc
[09:14] <babbageclunk> Sorry, this is all new to me. So you'd subclass this to make a relation?
[09:14] <magicaltrout> hehe, well my idea was (I don't know if this is possible which I guess is half the issue), charm x provides jdbc url, password, username etc
[09:14] <magicaltrout> generic jdbc layer can look up those standard variables
[09:14] <magicaltrout> sorry s/layer/interface
[09:15] <magicaltrout> and pas them to implementing app to inject into a jdbc connection
[09:15] <magicaltrout> that way, for a bunch of jdbc providing charms there could be one standard jdbc interface that all apps could consume without hacking around the data provided over the wire in the implementing charm itself
[09:16] <babbageclunk> But is there a lifecycle step where an interface can get customised, or is it just looked up directly from some registry?
[09:17] <magicaltrout> I don't think (feel free to prove me wrong) it needs much customisation.
[09:17] <magicaltrout> so it would just look up stuff from the providing charm
[09:17] <magicaltrout> i shall draw a picture! :)
[09:17]  * magicaltrout cracks out google drawings
[09:21]  * babbageclunk reads some docs - this is probably a good time to learn about interfaces.
[09:21] <magicaltrout> here you go babbageclunk
[09:21] <magicaltrout> https://ibin.co/2uSum2mXgYHo.png
[09:21] <magicaltrout> currently most interfaces are specific to an app... interface:mysql etc
[09:21] <magicaltrout> but why not make a generic one that passes over specific variables from the providing charm?
[09:22] <magicaltrout> that way requiring charm developers don't need to look up loads of metadata or hop through chopping up unit information
[09:22] <magicaltrout> because the providing charm (the folks that know what the jdbc stuff should look like) have done it for them
[09:23] <magicaltrout> then "any jdbc compatible application" can then grok the incoming charm connection and use the metadata over the wire
[09:23] <babbageclunk> That makes sense to me. How do the app-specific interfaces get the username/password/etc info they need to convey to the requires-side of the relation?
[09:24] <babbageclunk> Wouldn't yours work in the same way?
[09:24] <magicaltrout> hold on I'll show you what I currently do
[09:25] <magicaltrout> https://gist.github.com/buggtb/7e04a90922673312ebc6ca62f57fe464
[09:26] <magicaltrout> so thats on the jdbc application side
[09:27] <magicaltrout> but this is basically where my knowledge falls down because in the mysql layer for example: https://github.com/johnsca/juju-relation-mysql/blob/master/requires.py
[09:27] <magicaltrout> self.host() etc
[09:27] <magicaltrout> https://github.com/johnsca/juju-relation-mysql/blob/master/provides.py on the provides side coming from mysql
[09:27] <magicaltrout> I dont' see how the host, port etc get set
[09:28] <magicaltrout> which confuses the hell out of me :)
[09:28] <babbageclunk> Reading...
[09:29] <babbageclunk> So they get passed into provide_database - where does that get called?
[09:29] <magicaltrout> exactly! :)
[09:29] <babbageclunk> D'oh
[09:31] <magicaltrout> well
[09:31] <babbageclunk> Starting simply, it's easy to see how you could make one charm that could require all of mysql, psql, drill, etc.
[09:31] <babbageclunk> And then provide generic jdbc
[09:32] <babbageclunk> (Hmm, actually I might be confused about that but it seems possible, right?)
[09:33] <magicaltrout> well my Saiku charm for example, could then require jdbc in metadata.yaml
[09:33] <magicaltrout> which would then accept connections from jdbc providing charms
[09:33] <magicaltrout> so yeah that seems like its possible
[09:34] <magicaltrout> and on the consuming/requiring end it should reduce complexity and repetition
[09:35] <magicaltrout> and people wonder why i get annoyed with interfaces, cory is like the bloody interface wizard, but it makes it hard for everyone else ;)
[09:35] <babbageclunk> Right. Then the question would be could you do that in a layer so that any charm that provides one of them also privides jdbc?
[09:37] <magicaltrout> okay to retort, why would I need a layer instead of an interface?
[09:37] <babbageclunk> I think I mean an interface layer - is that a thing?
[09:37] <magicaltrout> lol
[09:38] <magicaltrout> interface or layer. Layers allow you to reuse existing layered charms
[09:38] <magicaltrout> charm inheritance
[09:38] <magicaltrout> interfaces are the stuff that allow the hooks to fire
[09:38] <babbageclunk> Right, but I was reading this: https://jujucharms.com/docs/2.0/developer-layers-interfaces
[09:39] <magicaltrout> so the question would be: could you do that in an *interface* so that any charm that provides the interface can support jdbc connections
[09:40] <babbageclunk> Or rather, could you make a layer that would provide a generic interface so that the charm just provides a specific one, and includes the interface layer to magically support the generic one.
[09:41] <magicaltrout> well you'd just upgrade the charms to provide interface:jdbc and set some stuff
[09:41] <babbageclunk> Which was the bit you were asking. Sorry!
[09:41] <magicaltrout> I write the Drill charm so my plan is to test it there then if it works, submit some PR's to mysql/postgres etc
[09:43] <magicaltrout> I think its something to do with self.conversation()
[09:44] <babbageclunk> Well, conversation is the bit that pushes the connection details to the requires side.
[09:44] <babbageclunk> I think
[09:44] <magicaltrout> https://github.com/johnsca/interface-mapred-slave/blob/master/provides.py here's another one of cory's
[09:44] <magicaltrout> conv.get_local etc
[09:46] <magicaltrout> sooo
[09:49] <magicaltrout> how do I set something on the conversation I guess
[09:49] <magicaltrout> or how does it magically appear
[09:50] <babbageclunk> That's a weird one though - since it's a map reduce slave even though it's a provides interface it's getting data from the conversation and storing it. I think if you look at the requires side you'll see something equivalent to the provide_database call.
[09:51] <magicaltrout> yeah so on the requires side I need a method like
[09:51] <magicaltrout> def get_jdbc():
[09:51] <magicaltrout> which does conv.get_remote()
[09:51] <magicaltrout> or something
[09:53] <babbageclunk> Hang on, just looking at the other DB relations
[09:53] <magicaltrout> and thats part of the annoyance on that charm the only get_remote is getting the private-address
[09:53] <magicaltrout> ta
[10:05] <babbageclunk> Have you got a locally built version of the mysql charm?
[10:05] <magicaltrout> i have a zip bundle download
[10:05] <magicaltrout> its not reactive so I guess that counts
[10:06] <babbageclunk> You should be able to find the place that calls provide_database in the code?
[10:06] <magicaltrout> you'll like this
[10:06] <magicaltrout> bugg@tom-laptop2:/tmp/charm$ grep -R provide_database .
[10:06] <magicaltrout> bugg@tom-laptop2:/tmp/charm$
[10:06] <babbageclunk> typical
[10:07] <magicaltrout> lol
[10:07] <magicaltrout> told you
[10:07] <magicaltrout> this stuff cory writes is more often than not... magic
[10:07] <babbageclunk> https://github.com/johnsca/juju-relation-mysql/blob/master/docs/source/provides.rst
[10:08] <magicaltrout> ah
[10:08] <magicaltrout> so.....
[10:08] <magicaltrout> on the provides side in drill I need to decorate some method
[10:09] <babbageclunk> If something's using that code to provide mysql, somewhere it's calling provide_database (with all the info you need to make the jdbc conn details).
[10:09] <magicaltrout> to detect the connection and set the variables in a provides interface method call
[10:09] <babbageclunk> Yeah
[10:09] <magicaltrout> woop
[10:09] <magicaltrout> babbageclunk: you code grepping genius
[10:09] <babbageclunk> Sorry, I'm a bit slow today!
[10:10] <magicaltrout> hehe, this stuff really messes with my head, then you think you're on to something and find some weird bash script at the other end etc
[10:10] <magicaltrout> I don't write python well at the best of times, finding out how charms interact melts my mind
[10:10] <babbageclunk> You're right it's confusing - the config information flow in the relations isn't always from provides to requires. But I think in the case of things like DB connections it will be.
[10:11] <magicaltrout> marvelous... with this mystery half solved i'll try and implement something in drill and see what happens
[10:11] <magicaltrout> i reckon an interface with, jdbcurl, username, password, class and a place for "extra stuff" to live
[10:12] <magicaltrout> would offer enough genericisim hopefully the interface setup allows it to work how I imagine :)
[10:12] <babbageclunk> That sounds neat
[10:13] <babbageclunk> ok, great! Now I need to work out why DHCP is MIA in my MAAS
[10:13] <magicaltrout> lol
[10:13] <magicaltrout> unlucky
[10:13] <magicaltrout> I did see some stuff when I was messing with virtualbox the other day where DHCP just refused to start if you didn't set a dynamic dhcp address pool
[10:13] <magicaltrout> thats about the depth of my MAAS knowledge
[11:24] <autonomouse> Hi, I was hoping for a bit of advice, if anyone is available. I have a reactive charm and an old-style charm, and I'd like to pass some information between them. e.g. url, username and apikey from a django service to something that needs to use that service. With the newer reactive charms, I believe I am supposed to set up an interface to do this. Can anyone tell me if the old-style charm can use this interface, and if
[11:24] <autonomouse> not, what the best approach is for handling this please?
[16:25] <mbruzek> bdx
[17:05] <kwmonroe> admcleod: beisner:  https://jujucharms.com/hadoop-processing/  it takes 8 machines by default, but you can change num_units on "slave" from 3 to 1 to get it down to 6:  https://api.jujucharms.com/charmstore/v5/hadoop-processing/archive/bundle.yaml
[17:42] <jose> jcastro: thought of using summit.ubuntu.com for the summit?
[17:55] <marcoceppi> jose: no
[17:55] <marcoceppi> the schedule is small, lightweight, and constantly in flux
[17:59] <jose> gotcha, was available so thought of you
[19:24] <kwmonroe> beisner: admcleod:  http://paste.ubuntu.com/23155869/
[19:25] <admcleod> kwmonroe: thanks
[19:37] <beisner> thx kwmonroe
[20:47] <magicaltrout> nearly missed tomorrows flight..... lost passport....
[20:59] <magicaltrout> lazyPower: good news.... I have a 2nd talk.... also about docker and juju
[20:59] <magicaltrout> @jpl that is
[21:01] <lazyPower> nice!
[21:01] <lazyPower> magicaltrout - when is that?
[21:01] <magicaltrout> the week after the summit
[21:01] <lazyPower> oh wow, so soooooon :D
[21:02] <lazyPower> we'll have to sync up, make sure we're up to snuff on the latest and greatest
[21:02] <magicaltrout> yeah well,  i'm in town etc..
[21:02] <lazyPower> about that, when do you arrive for the summit?
[21:02] <magicaltrout> saturday afternoon
[21:02] <lazyPower> nice, i'll be around
[21:02] <lazyPower> i should shoot you my digits
[21:02] <magicaltrout> i'll be sat in the bar very jetlagged ;)
[21:02] <magicaltrout> ooh
[21:02] <magicaltrout> thats tomorrow
[21:03] <lazyPower> indeed
[21:03] <magicaltrout> okay tomorrow afternoon
[21:03] <magicaltrout> very jetlagged
[21:03] <magicaltrout> i left my passport in the hotel i was in last week
[21:03] <lazyPower> so sunday brunch/lunch then depending on when i roll my lazy bones out of bed
[21:03] <magicaltrout> can you believe it?!
[21:03] <lazyPower> doh
[21:03] <magicaltrout> (yes)
[21:03] <magicaltrout> need to pick it up on the way to LHR
[21:03] <lazyPower> thats a nice distraction eh?
[21:03] <magicaltrout> spent all afternoon trying to find it:)
[21:04] <magicaltrout> i have an interface question if  you have 3  mins?
[21:04] <magicaltrout> not technical,  theoretical
[21:18] <babbageclunk> IT'S A TRAP
[21:18] <magicaltrout> i saw you lurking
[21:18] <magicaltrout> i  was trying to clear up our theory from this morning :P
[21:36] <admcleod> magicaltrout: took me ~20 hours from BCN. i feel a bit weird.
[21:41] <magicaltrout> like usual then admcleod ?
[21:44] <lazyPower> magicaltrout - sure
[21:44] <lazyPower> fire away
[21:45] <babbageclunk> I mean, it's an interesting trap.
[21:45] <babbageclunk> :)
[21:56] <magicaltrout> sorry for the delay lazyPower
[21:56] <magicaltrout> okay i have this idea
[21:56]  * lazyPower listens intently
[21:56] <magicaltrout> ideally there will be a bunch of apps that can consume JDBC connections
[21:57] <lazyPower> for the clarification of kwmonroe - JDBC is just the java database adapter right? their pluggable abstraction?
[21:57] <magicaltrout> soooo I had a plan to create a generic JDBC interface, that the providing charm  could populate with the stuff required by the consuming application
[21:57] <magicaltrout> yeah, any java data app  speaks jdbc in some form
[21:57] <lazyPower> yep, similar concepts in .net, go on
[21:58] <magicaltrout> so all jdbc connections are basically the same just different details, and I'm sick as a consuming app figuring out the various interfaces and stuff you need to know to build 1 per database or data source
[21:58] <magicaltrout> so I figured why not have mysql, postgres, drill etc all suppor the the jdbc interface
[21:58] <magicaltrout> which clearly is doable
[21:59] <magicaltrout> from a consuming standpoint, is  it possible and acceptable for 1 charm to consume the same interface from  multiple sources with different deets?
[22:01] <jrwren> magicaltrout: you are going to be talking at JPL?  that is awesome!
[22:01] <magicaltrout> my employers suggested it might be a good idea
[22:01] <magicaltrout> not sure when a hacker speaking to a bunch of PhD's was a good idea
[22:01] <magicaltrout> but we shall see
[22:02] <admcleod> magicaltrout: usual would be usual. weird is different weird.
[22:03] <magicaltrout> admcleod: a bit more like the i've been up for 24 hours, its 3pm so technically to early to drink but in reality i was drinking at 9am so wtf?
[22:03] <magicaltrout> don't worry you can take the piss out of me tomorrow in the same state
[22:03] <magicaltrout> after my drive from  LAX to the Sheraton
[22:04] <admcleod> magicaltrout: yeah, but i didnt really feel jetlagged, had a great sleep, woke up fresh.. but just hit me now
[22:04] <admcleod> magicaltrout: also i would never take the piss.
[22:07] <magicaltrout> sleep?
[22:07] <magicaltrout> you slept on the plane?
[22:07] <magicaltrout> or post landing?
[22:07] <magicaltrout> I once slept from Manchester to Toronto without waking once, the flight crew were pretty impressed
[22:07] <rick_h_> magicaltrout: you all there already?
[22:08] <rick_h_> magicaltrout: it's called ambien! only way I can sleep on planes
[22:08] <magicaltrout> sadly the first homeless guy to talk to me in Tonronto was from Leeds where i'd just left
[22:08] <magicaltrout> i fly tomorrow rick_h_
[22:08] <admcleod> magicaltrout: no, landed last night
[22:08] <rick_h_> magicaltrout: ah ok
[22:08]  * rick_h_ doesn't leave until sunday
[22:08] <magicaltrout> i need a day or so to get over the lag
[22:09] <rick_h_> yea, always a good thing
[22:09] <magicaltrout> admcleod: ah, yeah i know that one
[22:09] <jrwren> i usually need a week, and then i go home and need another week to adjust.
[22:09] <magicaltrout> although when i went to vancouver for apachecon the day i landed it smacked me  so hard i left the hotel bar without paying
[22:09] <magicaltrout> had to grovel the next day ;)
[22:09] <jrwren> magicaltrout: I look forward to meeting you.
[22:09] <magicaltrout> jrwren: good job i'm there for 2 weeks then ;)
[22:11] <magicaltrout> yeah jrwren it's gonna be a blast meeting more of the US folks and the expanding charmer team
[22:12] <magicaltrout> also, its amazing how much  has changed and moved on since Ghent at the start of the year
[22:12] <magicaltrout> i blame jcastro for my continued participation in this mess! ;)
[22:14] <icey> does anybody know how to install `charms` in addition to `pycharms`, pycharms seems to overwrite charms and trusty won't install charm-tools anymore
[22:14] <rick_h_> magicaltrout: we all blame jcastro :P
[22:15] <rick_h_> icey: pycharms?
[22:15] <magicaltrout> aye
[22:15] <icey> yes (says cholcombe, he's the asker :) )
[22:15] <magicaltrout> don't blame you
[22:16] <rick_h_> icey: hmm, pycharm search only finds the editor
[22:16] <icey> rick_h_: that's the one
[22:16] <rick_h_> icey: so the charm command interferes with the editor install?
[22:17] <icey> rick_h_: backwards, apparently the editor interferes with the charm install
[22:17] <icey> he cannot install charm
[22:17] <rick_h_> icey: hmm, and he's getting charm on trusty from the stable PPA?
[22:17] <rick_h_> icey: or which PPA I guess?
[22:17] <icey> yes
[22:17] <icey> rick_h_:
[22:19] <rick_h_> hmm, there's a few python deps like pytest and path.py that are in the PPA to support charm-tools and the like. I wonder if those are interfering
[22:19] <rick_h_> icey: my short answer is try to to setup one of them in a lxc container or the like atm, I'm not sure what conflicts without figuring out where he's getting pycharm from (it's not listed in ubuntu) and so guessing there's conflicting PPA/repos stuff there
[22:20] <icey> thanks rick_h_
[22:20] <rick_h_> sorry
[22:24] <lazyPower> magicaltrout - to circle back to your interface idea
[22:24] <magicaltrout> i like the lag
[22:25] <lazyPower> i think thats a fine idea. JDBC as a generic abstraction would be great, what would be even better, is if jdbc knew how to consume the existing relations, then its a one sided update. I'm wondering if you dont make a jdbc layer, that implements the known relations, and surfaces the details appropriately
[22:25] <lazyPower> otherwise, you're facing adding JDBC interface to every [layer|charm] that needs to communicate to jdbc. I'm trying to noodle how i can save you work there
[22:25] <lazyPower> but i dont think we have considered this as a use case
[22:26] <magicaltrout> well i might upstream mysql and postgresql and hive
[22:26] <magicaltrout> its not masses of effort and saves extra layers
[22:26] <lazyPower> when you say upstream, you mean just add the - 'interface:jdbc' to those charms right?
[22:27] <lazyPower> and whatever additional bits to utilize it in the layer
[22:27] <magicaltrout> yeah and a connection  method call somewhere
[22:27] <lazyPower> right, ok.  upstreaming is such an overloaded term anymore :)
[22:27] <lazyPower> yeah, that works. I'm +1 to this, as its straight forward, and makes a ton of sense
[22:27] <magicaltrout> you know me... trying to stay hip.. ;)
[22:28] <magicaltrout> yeah, i started writing a drill interface, but then i realised apart from the values
[22:28] <magicaltrout> the keys are identical to most  other jdbc interfaces
[22:29] <magicaltrout> so the lovely babbageclunk helped me unmuddle my brain this morning and i stood up something basic in drill, but I think generic interface for regular connections, as long as in practice they work
[22:29] <magicaltrout> would make life a lot easier for requring chamrer
[22:29] <magicaltrout> charmers
[22:31] <magicaltrout> saiku, pentaho, spago can certainly implement jdbc requires, so could drill and probably zeppelin somewhere
[22:40] <marcoceppi> magicaltrout: yeah, but jdbc is a connection string format, and if you have an app that takes a JDBC connection for MySQL but won't work on cassandra, then a jdbc interface doesn't really help?
[22:41] <magicaltrout> okay so lets assume some common sense on the end of the user
[22:41] <magicaltrout> cassandra isn't a jdbc compliant database
[22:41] <magicaltrout> whilst there are adapters for it
[22:41] <magicaltrout> jdbc is a standard and if you can write SQL  you can 95% of the interrogate a database
[22:42] <magicaltrout> of course there are exceptions
[22:42] <magicaltrout> but in the scheme of things and also the charms you guys have available, those exceptions don't really count
[22:44] <magicaltrout> also
[22:45] <magicaltrout> its  not the law to implement it
[22:45] <magicaltrout> you can still do what the hell you like :)
[22:45] <marcoceppi> if you want to implement a jdbc interface and add it to mysql/maria/percona/postgresql (any others?) go for it :)
[22:45] <marcoceppi> but I thin kit'd be work discussing next week
[22:46] <magicaltrout> sure, i can always rename my test jdbc interface  drillbit and we're back to the same thing
[22:47] <magicaltrout> i just think there should be a nice way for people trying to use the stuff provided by the resources instead of trying to find unit names etc because your providing charm requires a list of ZK nodes etc
[22:51] <magicaltrout> i happen to be implementing the drill charm as well so it doesn't count as much. but I wouldn't envy someone trying to work out the jdbc url without charmers help
[22:51] <magicaltrout> so why not try and genericise it
[23:18] <marcoceppi> +1


[00:45] <Omnifrog> hahaha
[00:45] <Omnifrog> It's Not About the Nail    http://vimeo.com/66753575
[01:27] <Omnifrog_> time to start over on the laptop
[01:39] <wrst> that sounds very final Omnifrog_?
[02:16] <Omnifrog_> install is at 98%
[02:16] <Omnifrog_> oh... reboot!
[02:19] <Omnifrog_> The Opensuse net installer was pretty sweet as install disks go
[02:19] <Omnifrog_> pretty much flawless
[02:20] <Omnifrog_> the suggested partition setup was spot on
[02:21] <Omnifrog_> it ignored the NTFS partitions, /swap, and /home and chose to only format / and install to there
[02:22] <Omnifrog_> the installer also offered a variety of DE's to install
[02:22] <Omnifrog_> including xfce
[02:35] <wrst> Omnifrog_: yep I have opensuse installed on my laptop, it took place of my ubuntu install that's sorta my secondary install just in case I blow up arch
[02:39] <Omnifrog_> I used Suse up to the point they started letting MS touch their junk years back
[02:39] <Omnifrog_> it's a pretty solid distro
[02:40] <Omnifrog_> or was, as far as i know it looks like it still is
[02:40] <Omnifrog_> I assume the opensuse folks have stuck to their guns
[02:51] <wrst> yes I think it is very nice, yast is strange to me but overall its good
[02:58] <Omnifrog_> updates are taking some time
[14:18] <wrst> welcome back to dry land Omnifrog
[14:19] <Omnifrog> :o
[14:19] <Omnifrog> almost
[14:19] <Omnifrog> more rain is coming
[14:21] <wrst> yes that I hear, hopefully take some of the humidity out of the air
[14:23] <Omnifrog> and I _just_ replanted the carrot beds on Saturday :\
[14:23] <Unit193> Last night was 100%, can't sleep in that...
[14:23] <Omnifrog> I'm sure they got washed out


[03:28] <jbicha> roasted: fixed the brightness panel and the missing app lauchers (like language-selector) will be fixed shortly
[06:57] <darkxst> ricotz, ok to copy your mozjs17 and gjs over to gnome3-staging, as is?
[13:29] <roasted> nice! way to rock jbicha
[13:29] <roasted> I see that it's fixed on my end. This is great.
[13:45] <jbicha> ricotz, darkxst: oops, we're going to have to request more space if we ever want to push webkit to the staging ppa (the gnome3 ppa has space though)
[13:46] <roasted> doh, my laptop just gave out.
[13:48] <roasted> the MIA battery icon got me :P
[19:08] <timonti> Using 1st April build of Ubuntu Gnome, I am unable to upgrade to 3.8
[19:10] <timonti> anyone here?
[21:22] <tyrog> Hi
[21:23] <tyrog> jbicha: are you there? Is the gnome3 staging ppa stable now? thanks
[21:35] <jbicha> tyrog: for raring, we're still in beta
[21:36] <tyrog> jbicha: What PPAs do you recommend for people using raring at the moment?
[21:36] <tyrog> The objective is to have gnome 3.8
[21:36] <jbicha> I'm sure the GNOME 3.7.92/3.8 that we're using has more bugs than the 3.6.3 or whatever is in the regular Ubuntu respositories
[21:36] <jbicha> we recommend the GNOME3 PPA
[21:37] <jbicha> the GNOME3 Staging PPA is for those who like the bleeding edge and don't mind things being a bit broken
[21:37] <tyrog> jbicha: The normal one, staging and/or Rico's Testing PPA?
[21:37] <roasted> Is there a current bug for the printer dialog crashing upon adding a printer?
[21:37] <jbicha> the normal https://launchpad.net/~gnome3-team/+archive/gnome3/+packages?field.series_filter=raring
[21:37] <tyrog> only that one?
[21:38] <jbicha> yes
[21:38] <roasted> It doesn't make it sting any less that localhost:631 is refusing my credentials to log in <_<
[21:38] <jbicha> the ricotz testing ppa uses git snapshots which isn't what the average person needs
[21:38] <tyrog> jbicha: Gnome tweak tool doesn't work with that PPA enabled. Is it supposed not to?
[21:39] <jbicha> roasted: no idea, you're welcome to report a new bug if you can't find already reported
[21:41] <tyrog> jbicha: tweak tool not working. Is it still being worked on for gnome 3.8?
[21:45] <ricotz> tyrog, you need to provide a bit more information like that actual version while you are using several ppas "apt-cache policy gnome-tweak-tool" and pastebin the console output of running it -- 3.8.0~git20130329.30f0f84d-0ubuntu1~ suppose to work fine even without running a gnome-shell session
[21:46] <ricotz> i hope someone can help out here, g2g
[21:46] <tyrog> ricotz: Is your PPA (GNOME testing) good or better stick with gnome3 and gnome3 staging?
[21:46] <tyrog> I see, I'm using raring to have the latest stuff until final, it is a dual boot. I don't mind having some breakage here and there
[21:47] <tyrog> I just want to know if your PPA provides added value to the gnome3 staging ppa. Thanks
[21:47] <ricotz> tyrog, if you are using ricotz/testing, also better use gnome3/gnome3-staging
[21:47] <ricotz> with gnome3/gnome3 too of course
[21:48] <tyrog> ricotz: Not using ricotz (yet). But should I use it even after Ubuntu 13.04 is officially released?
[21:48] <ricotz> tyrog, as jbicha said it is more bleeding edge and doesnt fit the needs for everyone
[21:49] <tyrog> ricotz: Its the only way to get Gnome 3.8 in Ubuntu 12.10 for example. So you'd consider it safe for users with 12.10 who want to use Gnome shell 3.8?
[21:49] <ricotz> tyrog, it will get 3.9.x snapshots soon
[21:50] <ricotz> tyrog, it is not safe for everyone, things are likely to be broken
[21:51] <ricotz> alright, i really need to go, bye
[22:47] <jbicha> darkxst: did you test gnome-shell before uploading?
[22:48] <darkxst> jbicha, yes
[22:48] <darkxst> why? what is broken?
[22:49] <jbicha> darkxst: I hadn't uploaded sooner because I ran into https://bugzilla.gnome.org/show_bug.cgi?id=696981
[22:51] <darkxst> jbicha, I hit that a couple of weeks ago
[22:52] <darkxst> but then it disappeared
[22:52] <jbicha> darkxst: oh, things work ok with your upload


[00:02] <bdmurray> bug 201170
[00:04] <keescook> bdmurray: did ubotu vanish?
[00:05] <secretlondon> its not here, certainly
[00:05] <bdmurray> I quieted him because there was a second one for a while, he seems to have quit now.
[00:05] <secretlondon> neither are here
[00:06] <secretlondon> ubotu has been very lagged recently - can be 10 mins or so
[00:06] <secretlondon> but has just spoken to me ;)
[00:12] <keescook> heh
[00:13] <secretlondon> "<ubotu> Error: I am only a bot, please don't think I'm intelligent :)"
[00:13] <secretlondon> so presumably it is here somewhere
[00:14] <secretlondon> bug #201170
[00:15] <savvas> usb problems, http://bugs.launchpad.net/bugs/201643 - does anyone know which package i should add?
[00:16] <secretlondon> prob kernel without looking at the bug. we have a debugging removal devices page
[00:17] <yuriy> blueyed: yes, it probably should mention the channel, though the ubuntu page doesn't mention it either
[00:17] <yuriy> oh, now i get what your second comment meant
[00:18] <bdmurray> savvas: The kernel is correct.  I think those errors usually indicate bad cables or a device.
[00:23] <savvas> bdmurray: i didn't get them in previous kernels, the device is kingston datatraveller and just 2 months old, i take care of it pretty well, but i suppose it could break..
[00:24] <bdmurray> I might be wrong about the cable.
[00:25] <savvas> there's no cable :\
[00:25] <savvas> it's a flash disk
[00:26] <savvas> bah i'll have to go
[00:26] <savvas> bdmurray: do you think i need to send any other logs?
[00:26] <savvas> i've sent the ones that i thought important
[00:27] <bdmurray> That's normally what the kernel team looks for so it should be good to go.
[00:27] <savvas> ok thanks
[00:27] <bdmurray> I've updated the package for you too.
[00:28] <savvas> have a joyful night and don't let the ubuntu bugs bite :)
[03:09] <techno_freak> :)
[05:19] <ionstorm> https://bugs.edge.launchpad.net/ubuntu/+source/apt/+bug/201685
[05:39]  * techno_freak looks for the dupe-hunter
[08:50] <Lhademmor> I'm confirming one of the rhythmbox-bugs marked incomplete on the list. My first semi-bug contribution :D
[08:53] <techno_freak> welcome ;)
[08:55] <Lhademmor> thank you.
[08:55] <Lhademmor> Until I learn some more programming, I probably wont be of much help, thougj
[10:21] <secretlondon> bug #201673 looks like 'fun', glad I was asleep and missed it
[10:27] <hggdh> secretlondon: indeed it was fun...
[10:28] <secretlondon> it looks like it ;)
[10:30] <techno_freak> secretlondon, missed you to hunt dupes :p
[10:30] <hggdh> :-) part of being in the cutting, razor-sharp edge
[10:30] <secretlondon> techno_freak :)
[10:40] <Nightrose> what do I do with a bug that needs to be fixed by upstream and is in their bugtracker already?
[10:41] <Nightrose> link the bugs and set it to...?
[10:41] <Nightrose> hmm rather a wish than a bug
[10:41] <secretlondon> link our bug to theirs
[10:41] <secretlondon> also affects project
[10:41] <Nightrose> ok thx
[10:42] <Nightrose> that's all?
[10:42] <hggdh> also set the LP bug to "Triaged"
[10:42] <hggdh> Nightrose: ^^
[10:42] <hggdh> huh
[10:42] <secretlondon> yeah - launchpad will get the status from the bug automatically
[10:43] <hggdh> you may also add a note to the upstream bug with the LP bug URL
[10:43] <hggdh> good for cross-referencing
[10:43] <Nightrose> hggdh: I don´t think I can do that - I am in the Amarok team and can work on amarok bugs - but can´t seem to set them as triaged
[10:43] <hggdh> Nightrose: give me the bug #, and I will do it
[10:43] <Nightrose> ok sec
[10:44] <hggdh> (after setting the "also affects project")
[10:44] <Nightrose> hggdh: https://bugs.edge.launchpad.net/amarok/+bug/136520
[10:47] <hggdh> Nightrose: it is always good to add a comment on why you set the upstream bug -- this allows for the reporter, and others, to easily see why it was done. I am setting as triaged, and adding a small comment on that
[10:47] <hggdh> done
[10:47] <Nightrose> comment already added ;-)
[10:47] <Nightrose> thx
[10:47] <hggdh> oh, you already had...
[10:47] <hggdh> I am sorry
[10:48] <Nightrose> hehe no prob
[10:48] <hggdh> Nightrose: thanks for helping, BTW :-)
[10:49] <Nightrose> no prob - a lot of the Amarok devs are Kubuntu users - so we are interested in triaging these bugs
[10:49] <secretlondon> cool :)
[10:49] <Nightrose> and since today is hug day...
[10:49] <Nightrose> ;-)
[10:49] <hggdh> good... I personally use Amarok, but under Gnome
[10:49] <Nightrose> hehe we are fine with that
[10:49]  * hggdh hugs Nightrose
[10:49]  * Nightrose rehugs hggdh
[10:50]  * secretlondon hugs amarok
[10:50] <Nightrose> :p
[10:50]  * secretlondon also uses some kde apps under gnome
[10:52] <Nightrose> nixternal: damn you for taking all my nice bugs in the wiki ;-)
[10:56] <hggdh> Nightrose: (I forgot to tell you that) setting bugs to Triaged requires one to be a member of the bug-control team. You can apply for it after some time (usually a month) of bug triaging. You are welcome to, if you so want
[10:56] <hggdh> to
[10:56] <hggdh> :-)
[10:56] <Nightrose> ok thanks - will do
[11:44] <Nightrose> nixternal: sorry - I was talking crap - forget what I said :P
[11:49]  * secretlondon laughs at Nightrose
[11:49] <Nightrose> ;-)
[11:49] <secretlondon> He's a big boy, I'm sure he can take it!
[11:49] <Nightrose> haha yea
[11:50] <Nightrose> nixternal: btw I applied for eV membership on monday - now is your turn *g*
[11:54] <pedro_> folks!, today is the rhythmbox & totem hug day https://wiki.ubuntu.com/UbuntuBugDay/20080313
[11:54] <pedro_> and if you're using KDE and amarok you may want to look to https://wiki.ubuntu.com/UbuntuBugDay/20080313/KDE
[11:55] <Nightrose> pedro_: I am already on the amarok bugs ;-)
[11:55] <pedro_> lets keep this hug days rocking!
[11:55] <pedro_> Nightrose: rock on!
[12:54] <Iulian> Hey
[12:56] <pedro_> hello Iulian, how are you today?
[12:56] <pedro_> ready to squash some bugs? ;-)
[12:59] <Iulian> I'm doing fine, thanks.
[12:59] <Iulian> I am ready!
[13:00] <pedro_> rock!
[13:00] <Iulian> By the way - Happy Hug Day everyone!
[13:04] <secretlondon> :)
[13:04] <Iulian> Hi secretlondon :)
[13:04] <secretlondon> Hi Iulian :)
[13:05] <ryanakca> hurra, bugday ;)
[13:05] <pedro_> woohoo
[13:06] <pedro_> is you're running GNOME https://wiki.ubuntu.com/UbuntuBugDay/20080313
[13:06] <pedro_> or KDE https://wiki.ubuntu.com/UbuntuBugDay/20080313/KDE
[13:37] <Nightrose> can someone close https://bugs.edge.launchpad.net/ubuntu/+source/amarok/+bug/165036 please?
[13:37] <Nightrose> I think the poster got p*issed at me enough by now ;-)
[13:38] <Gnine> package fetching failed with "403 forbidden" on a few packages
[13:39] <pedro_> Gnine: libc ones?
[13:39] <pedro_> it should be fixed shortly
[13:40] <Gnine> yes.. and a couple others.. cool. roger that
[13:41] <sourcercito> Nightrose, did you report the issue upstream or just talk with the upstream developers by im or irc?
[13:41] <Nightrose> sourcercito: I am upstream
[13:41] <Gnine> on x86_64 the issue was a little more drastic
[13:41] <sourcercito> i'm asking in case there's any reference to that upstream
[13:41] <sourcercito> ok, closing it then ;)
[13:41] <Nightrose> thank you ;-)
[13:41] <sourcercito> anytime
[13:43] <hggdh> Nightrose: ugh... bad experience...
[13:44] <thekorn> happy hug day!
[13:44] <Nightrose> hggdh: well I have to deal with a lot of this so I don´t really care - sometimes people just don´t understand ;-)
[13:46] <sourcercito> thekorn, happy hug day back to you ;)
[13:49]  * pedro_ hugs the whole bugsquad
[13:49] <pedro_> how nice is the ubuntu pulse http://pulseofubuntu.tweetpeek.com/
[13:50] <pedro_> there's plenty of people in just a few days
[13:56]  * sourcercito peeking
[13:59] <Gnine> c0ol
[14:27] <Nightrose> hmm what to do with bugs like https://bugs.edge.launchpad.net/ubuntu/+source/amarok/+bug/182359 ?
[14:29] <pedro_> Nightrose: it's ok to close it as invalid
[14:30] <Nightrose> thx
[14:30] <pedro_> you're welcome
[15:07] <apachelogger_> ahoy
[15:09] <QbixAway> raise the sails!
[15:12] <afflux> morning
[15:14] <secretlondon> morning afflux
[15:14] <afflux> hi secretlondon
[15:18] <apachelogger_> Nightrose: replyto:"bugs.launchpad.net"
[15:18] <yuriy> morning
[15:18] <Nightrose> thx ;-)
[15:18]  * yuriy hugs Nightrose and apachelogger_
[15:18]  * apachelogger_ hugs yuriy and Nightrose
[15:18] <Nightrose> hey yuriy :)
[15:18] <afflux> hi yuriy
[15:19] <yuriy> hi afflux
[15:19] <afflux> uuh, I've fallen back in 5-a-day.
[15:19] <secretlondon> :(
[15:20] <afflux> I'll catch up today, I promise :P
[15:20] <secretlondon> :P
[15:20] <nixternal> Nightrose: I thought you had to be selected or something for the eV, I didn't know you could just apply
[15:21] <Nightrose> nixternal: you just have to ask someone to recommend you - I asked danimo
[15:21]  * yuriy would hug parthan/techno_freak too but doesn't see him
[15:21] <Nightrose> or rather danimo asked me
[15:21] <nixternal> ahh, nobody will recommend me :(
[15:21] <secretlondon> nixternal :(
[15:21] <Nightrose> nixternal: I am sure Riddell would - as would I once I am in ;-)
[15:22] <apachelogger_> nixternal: just ask one of the amarokers, they do everything for money
[15:22] <Nightrose> hehe
[15:22] <apachelogger_> really _everything_
[15:22] <nixternal> hahahaha, I bet
[15:22] <secretlondon> apachelogger_ photos?
[15:23] <santiago-ve> guys https://bugs.edge.launchpad.net/ubuntu/+source/amarok/+bug/120791 <-- i think it should be marked as invalid
[15:24] <santiago-ve> i made a comment there tho
[15:24] <apachelogger_> secretlondon: http://picasaweb.google.com/lh/viewPhoto?uname=apachelogger&aid=5129629037405096673&iid=5129629166254115570
[15:24] <afflux> nooo, firefox can't just crash when I'm going for bugs :(
[15:25] <secretlondon> apachelogger_, that doesn't show amarok devs doing anything for money ;)
[15:25] <apachelogger_> hm, apparently firefox has a bug which is preventing the triage of bugs
[15:25] <secretlondon> well my firefox is okay
[15:25] <afflux> probably
[15:25] <apachelogger_> secretlondon: I am getting makeup there :P
[15:25] <secretlondon> ah okay
[15:27] <Nightrose> santiago-ve: marked as invalid - thx
[15:28] <santiago-ve> https://bugs.edge.launchpad.net/ubuntu/+source/amarok/+bug/181293 this one can be marked as confirmed, i've experienced the same on kubuntu feisty 7.04
[15:28] <yuriy> santiago-ve: why don't you do it?
[15:29] <santiago-ve> yuriy, done then :p
[15:30] <yuriy> santiago-ve: don't forget to mark it off on the wiki : )
[15:30] <santiago-ve> since im new on this i dont want to do things bad xD!
[15:31] <apachelogger_> doing things wronger than me is pretty much impossible
[15:31] <yuriy> santiago-ve: on that one it would help to have some more circumstances under which the crash happens
[15:32] <yuriy> santiago-ve: also changing the title to something descriptive like "amarok crashes when doing xxx with error yyy" would be helpful
[15:33] <hggdh> santiago-ve: it might be also nice to have a backtrace with symbol resolution (i.e., without ?? in the function names)... I am not sure we can open upstream with the current BT
[15:33] <santiago-ve> gimmi a sec... i dont remember my wikilogin xD! (different machine)
[15:34] <Nightrose> well you got two people from upstream here - you can just ask ;-)
[15:35] <hggdh> Nightrose: is the stacktrace good for upstream?
[15:35] <hggdh> :-)
[15:35] <Nightrose> would be better to have more ;-)
[15:35]  * hggdh bows for Nightrose
[15:36] <Nightrose> hehe
[15:36] <santiago-ve> done, got in... so now how i mark "#181293" on the wiki?... i marked it as confirmed on LP~
[15:36] <Nightrose> santiago-ve: see the first paragraph in the wikipage
[15:42] <santiago-ve> kay
[15:43] <afflux> do we have people from rhythmbox upstream here too?
[15:44] <afflux> forwarded bug 199319 to gnome-bugs 522247
[15:44] <apachelogger_> Nightrose: bug 147616
[15:45] <pedro_> afflux: no we don't have rhythmbox/totem (they're the same) upstream this time
[15:45] <apachelogger_> Nightrose: https://bugs.edge.launchpad.net/ubuntu/+source/amarok/+bug/147616
[15:45] <apachelogger_> stupid bots
[15:45] <pedro_> haha
[15:45] <yuriy> we're spoiled :P
[15:45] <afflux> pedro_: right, it's not urgent ;)
[15:46] <pedro_> bots aren't working pretty nice ATM :-(
[15:46] <pedro_> yeah i know :-)
[15:47] <bdmurray> pedro_: I could unquiet ubotu
[15:47] <pedro_> no no!
[15:47] <afflux> what did he do?
[15:47] <bdmurray> It won't announce that just happens u-b-a
[15:47] <Pici> ty
[15:47] <Seveas> Pici, where else is it muted?
[15:47] <yuriy> i thought it just wasn't supposed to be making announcements, but still respond to people mentioning bugs
[15:47] <bdmurray> Seveas: just here because of the lag
[15:48] <pedro_> ubuntulog is our new bot?
[15:48] <pedro_> ubuntulog: wake up!
[15:48] <Seveas> ubuntulog is only for logging...
[15:48] <bdmurray> pedro_: that's the logger that goes to irclogs.ubuntu.com
[15:48] <pedro_> damn it!
[15:48] <bdmurray> bug 178058
[15:48] <LjL> Seveas: not anywhere else that i remember. i'll check it from a script
[15:48] <ubotu> Launchpad bug 178058 in ubuntu "[Hardy] Desktop Screen extends too far" [Undecided,New] https://launchpad.net/bugs/178058
[15:49] <pedro_> tick tack tick tack
[15:49] <yuriy> somebody on kde3 try bug 121071? should be easy to test
[15:49] <ubotu> Launchpad bug 121071 in amarok "With Kicker Media Control Applet, Amarok tooltip misbehaves" [Undecided,New] https://launchpad.net/bugs/121071
[15:49] <pedro_> ubotu: i love you
[15:49] <ubotu> Sorry, I don't know anything about i love you - try searching on http://ubotu.ubuntu-nl.org/factoids.cgi
[15:49] <pedro_> you don't?
[15:49] <pedro_> :-(
[15:49] <Seveas> pedro_, if launchpad is slow, ubotu is slow
[15:49] <Seveas> it fetches info from launchpad
[15:49] <bdmurray> pedro_: you could teach ubotu about love
[15:49] <pedro_> hahaha
[15:49] <Seveas> bdmurray, no robo-X-rated scenes here please ;)
[15:49] <Nightrose> apachelogger_: https://bugs.edge.launchpad.net/ubuntu/+source/amarok/+bug/178189
[15:49] <ubotu> Launchpad bug 178189 in amarok "amarokapp crashed with SIGSEGV trying to play a WMA file" [Undecided,Incomplete]
[15:50] <bdmurray> Seveas: ubotu was having connectivity issues I thought, leaving due to flooding?
[15:50] <Seveas> bdmurray, all fixed when I came back from holiday
[15:50] <bdmurray> Ah, well great!
[15:50] <pedro_> it's working nicely on u-b-announce
[15:51] <Seveas> though you might see some odd-ish behaviour and an extra bot soon
[15:51] <Seveas> I'm rewriting the bugger
[15:51] <santiago-ve> i think 144132, 155586 and 144132 are duplicates of 181293, or may be different crashes... tho i still think they're duplicates
[15:51] <Seveas> bug 144132, 155586 and 144132
[15:52] <ubotu> Launchpad bug 144132 in amarok "1.4.7 [___stripped][validity: 0.53][frames:  97][xine]" [Undecided,Incomplete] https://launchpad.net/bugs/144132
[15:52] <ubotu> Launchpad bug 155586 in amarok "1.4.7 [___stripped][validity: 0.70][frames: 151][xine]" [Undecided,Incomplete] https://launchpad.net/bugs/155586
[15:52] <bdmurray> Seveas: Are the factoids kept in the source code?
[15:52] <Seveas> bdmurray, no
[15:52] <Seveas> bdmurray, http://ubotu.ubuntu-nl.org/
[15:52] <Seveas> they're currently kept in an sqlite database, but will move to mysql
[15:53] <bdmurray> Hmm, I was trying to think an easier way to update them rather than going through them one by one.
[15:53] <Seveas> what do you want?
[15:53] <Seveas> I can run SQL foo :)
[15:55] <santiago-ve> Well gotta be away for a while~...
[15:55] <hggdh> thanks for the help, santiago-ve
[15:57] <bdmurray> It was more an idea rather than a specific need.  I'm concerned about how current some of the replies / links given are, I think I'll just review them starting from the most popular.
[15:57] <Seveas> bdmurray, the most popular tend to be accurate :)
[15:58] <apachelogger_> Nightrose: https://bugs.edge.launchpad.net/ubuntu/+source/amarok/+bug/159821
[15:58] <Seveas> bdmurray, please don't do a review now, I'll be doing that in about a weeks time anyway
[15:58] <ubotu> Launchpad bug 159821 in amarok "Installing MP3 support crashes Amarok" [Undecided,New]
[15:59] <bdmurray> Seveas: okay, thanks!
[15:59]  * secretlondon thanks seb128 for filing the python-gdata bug with debian as she was just about to
[16:00] <seb128> secretlondon: you are welcome ;-)
[16:00] <bdmurray> Is that something you do regularly?
[16:00] <secretlondon> Bug #201845 is our bug on that packaging issue :)
[16:00] <ubotu> Launchpad bug 201845 in python-gdata "python-gdata needs build-dependencies fixing" [Undecided,New] https://launchpad.net/bugs/201845
[16:00] <secretlondon> link to seb's deb bug
[16:00] <Seveas> no, but it needs to be done for the migration :)
[16:00] <seb128> secretlondon: you can close this one, I've uploaded the change to hardy before filling the debian bug
[16:00] <secretlondon> ah okay
[16:00] <seb128> secretlondon: I was looking at getting the totem youtube thing working out of the box
[16:01] <seb128> but it doesn't work correctly so I'm not sure now
[16:01] <seb128> maybe I'll do a totem-plugins-universe and move it there
[16:01] <secretlondon> ah - thanks
[16:04] <secretlondon> I've closed the bug as fix released as you've uploaded it :)
[16:14] <apachelogger_> Nightrose: 182736
[16:14] <apachelogger_> Nightrose: https://bugs.edge.launchpad.net/ubuntu/+source/rhythmbox/+bug/191475
[16:14] <ubotu> Launchpad bug 191475 in rhythmbox "[hardy] media tab in file management preferences missing applications" [Low,Fix released]
[16:16] <apachelogger_> yuriy: can you take a look at this bug?
[16:16] <apachelogger_> IMHO this shouldn't be implemented anywhere until x-content/* is part of freedesktop.org stuff
[16:17] <Nightrose> apachelogger_: https://bugs.edge.launchpad.net/ubuntu/+source/amarok/+bug/88005
[16:17] <ubotu> Launchpad bug 88005 in amarok "MASTER [apport] amarokapp crashed with SIGSEGV - malloc_consolidate ()" [High,Incomplete]
[16:17] <afflux> rhythmbox not respecting read-only files when editing tags seems like a "medium" bug to be, what do you think?
[16:17] <afflux> (bug 181742)
[16:17] <ubotu> Launchpad bug 181742 in rhythmbox "Rhythmbox does not respect file permissions" [Wishlist,Triaged] https://launchpad.net/bugs/181742
[16:24] <Nightrose> apachelogger_: https://bugs.edge.launchpad.net/ubuntu/+source/amarok/+bug/94447 and https://bugs.edge.launchpad.net/ubuntu/+source/amarok/+bug/107562
[16:24] <ubotu> Launchpad bug 94447 in amarok "Can't erase Cover used by various artists" [Undecided,Incomplete]
[16:25] <Nightrose> apachelogger_: https://bugs.edge.launchpad.net/ubuntu/+source/amarok/+bug/95441
[16:25] <ubotu> Launchpad bug 95441 in amarok "Can't retrieve lyrics with amarok when behind a proxy" [Undecided,Incomplete]
[16:27] <Nightrose> apachelogger_: https://bugs.edge.launchpad.net/ubuntu/+source/amarok/+bug/107289
[16:27] <ubotu> Launchpad bug 107289 in amarok "wrong transfer sizes with transkode" [Wishlist,Incomplete]
[16:35] <Nightrose> apachelogger_: https://bugs.edge.launchpad.net/ubuntu/+source/amarok/+bug/136522
[16:35] <ubotu> Launchpad bug 136522 in amarok "No automatic iPod sync" [Wishlist,Incomplete]
[16:41] <afflux> time for coffee!
[16:41] <apachelogger_> Nightrose: https://bugs.edge.launchpad.net/ubuntu/+source/amarok/+bug/127352
[16:41] <ubotu> Launchpad bug 127352 in amarok "Amarok mixes album names while renaming" [Undecided,New]
[16:41] <apachelogger_> afflux: good idea
[16:42]  * apachelogger_ just finishes the current bug
[16:43] <apachelogger_> Nightrose: http://bugs.kde.org/show_bug.cgi?id=156819
[16:43] <apachelogger_> wtf
[16:43] <ubotu> KDE bug 156819 in general "No automatic iPod sync" [Wishlist,Resolved: invalid]
[16:47]  * apachelogger_ takes Nightrose for a coffee
[17:13] <sbarjola> hi, this is my first day,.. how can I help?
[17:15] <james_w> hi sbarjola
[17:16] <james_w> sbarjola: this is the page for coordination of today's work: https://wiki.ubuntu.com/UbuntuBugDay/20080313
[17:18] <sbarjola> ok, then I select a bug and begin.. how can I know that no other is working on it?
[17:18] <yuriy> apachelogger_: take a look at which bug?
[17:18] <hggdh> sbarjola: you can assign it to yourself temporarily
[17:19] <hggdh> if a bug has an assignee, it should be left alone. Just make sure you unassign yourself/assign to the correct group when you are done working with it
[17:21] <apachelogger_> yuriy: the one a couple of lines above, before I highlighted you ;-)
[17:21] <yuriy> in rhythmbox?
[17:22] <yuriy> oh it's both, i see
[17:27] <yuriy> apachelogger_: i don't have gnome installed, what am i looking at here?
[17:31] <sbarjola> where I should test the bug.. hardy or that is in the bug?
[17:32] <pedro_> ideally they should be tested on hardy
[17:34] <apachelogger_> yuriy: the gnome file manager has introduce a special mimetype class (x-content) for various device types like cds and stuff
[17:34] <apachelogger_> yuriy: to be available as application for these types the application needs to list the x-content/foobar mimetype in it's desktop file
[17:35] <apachelogger_> the only problem I have with that ... is that x-content is not yet part of the freedesktop mimetype concept
[17:36] <yuriy> ok..
[17:45] <yuriy> apachelogger_: ask Riddell about it?
[17:48] <apachelogger_> yuriy: good point
[17:48] <yuriy> true though, searching fd.o for x-content turns up nothing
[17:50] <apachelogger_> yuriy: according to the related gnome bug reports, they are planing to suggest it for the next revision of the mime stuff
[18:45] <qense> hello
[18:46] <secretlondon> hi qense
[18:46] <wraund> guys i need some serious and big help
[18:46] <wraund> ubuntu@ubuntu:~$ sudo chroot /media/disk/
[18:46] <wraund> malloc: unknown:0: assertion botched
[18:46] <wraund> free: called with unallocated block argument
[18:46] <wraund> last command: (null)
[18:46] <wraund> Aborting...Aborted (core dumped)
[18:46] <wraund> ubuntu@ubuntu:~$
[18:47] <wraund> i am having to use the live disc as my main desktop went down
[18:47] <secretlondon> wraund it'll prob be the libc bug
[18:47] <bdmurray> wraund: you'll want to look at the ubuntu-devel-announce mailing list for help
[18:47] <wraund> bdmurray: cant :P
[18:47] <wraund> the machine doesnt work :P
[18:47] <wraund> secretlondon: so.... how can i fix this?
[18:47] <Nightrose> wraund: https://wiki.ubuntu.com/MOTU/Contributing
[18:47] <wraund> i doubt i can get updates as root or sudo isnt working
[18:48] <Nightrose> meh sorry wrong link
[18:48] <secretlondon> the mailing list has a workround, as does the bug afaik
[18:48] <bdmurray> wraund: https://lists.ubuntu.com/archives/ubuntu-devel-announce/2008-March/000401.html
[18:48] <Nightrose> https://launchpad.net/bugs/201673 this one
[18:48] <ubotu> Launchpad bug 201673 in glibc "REGRESSION: glibc 2.7-9ubuntu1 NSS module broken due to toolchain changes" [Critical,Fix released]
[18:48] <wraund> lemme see..
[18:48] <wraund> typical
[18:48] <wraund> firefox isnt working on the live cd atm
[18:48] <wraund> somethign about :0 xserver
[18:49] <wraund> anyway how will i be able to get and install a patch considering root and sudo dont work
[18:50] <wraund> ?
[18:50] <bdmurray> wraund: "The quickest workaround is to copy an older version of the C library
[18:50] <bdmurray> from the initramfs"
[18:50] <wraund> how
[18:50] <wraund> oh
[18:50] <wraund> please explain
[18:50] <bdmurray> It's quite lengthy
[18:51] <wraund> can you pm me step by step
[18:51] <wraund> i would be forever grateful
[18:51] <wraund> or paste a guide
[19:00] <yuriy> hmm bug 181289 sounds icky, don't really know what could be added to it either
[19:00] <ubotu> Launchpad bug 181289 in amarok "Amarok Crashes Entire System" [Undecided,New] https://launchpad.net/bugs/181289
[19:02] <Nightrose> yuriy: it is nasty yea - maybe check the amarok bug tracker? or xine bug tracker?
[19:02] <Nightrose> though I have never heard someone complaining about this
[19:07] <amon__> hi guys
[19:08] <amon__> is this the place for hardy bugs
[19:08] <amon__> ?
[19:08] <bdmurray> This is the place for Hardy bug triage and fixing of bugs.
[19:09] <bdmurray> What are you looking for?
[19:09] <amon__> sorry, i have talked too much on skype, so im not used to irc anymore, but i will try and give my best to not generate unecessary lines
[19:09] <secretlondon> hardy support is better at ubuntu+1 though
[19:10] <amon__> audio skips on my hardy setup, xmms does not work
[19:10] <amon__> at all
[19:15] <bdmurray> That sounds more like a configuration issue than a bug.
[19:16] <Gnine> !support
[19:16] <ubotu> The official ubuntu support channel is #ubuntu. Also see http://ubuntu.com/support and http://ubuntuforums.org
[19:16] <Gnine> !hardy
[19:16] <ubotu> Hardy Heron is the code name for the next release of Ubuntu (8.04-LTS), due April 2008 - For more info, see: https://wiki.ubuntu.com/HardyHeron - CONSIDER IT TO BE PRE BETA (ALPHA) SOFTWARE - Discussion and support in #ubuntu+1, NOT #ubuntu
[20:36] <wxPython> hello
[20:36] <wxPython> got a patch for a bug
[20:37] <RAOF> Awesome!
[20:37] <wxPython> i wanna post the diff file on launchpad for the approproate bug
[20:37] <wxPython> appropriate
[20:37] <wxPython> i just wanna know one little thingy
[20:37] <wxPython> oh before i go on, please visit this link
[20:38] <wxPython> http://bugzilla.gnome.org/attachment.cgi?id=107229&action=diff&context=patch&collapsed=&headers=1&format=raw
[20:38] <wxPython> this is the diff file
[20:38] <wxPython> the bug is https://launchpad.net/ubuntu/+source/gnome-panel/+bug/18361
[20:38] <ubotu> Launchpad bug 18361 in gnome-panel "Odd selection launchers/menu" [Unknown,Confirmed]
[20:39] <wxPython> i am not so familiar with Launchpad
[20:40] <RAOF> Ok.
[20:40] <jeromeg> wxPython: this patch has already been proposed in gnome bugzilla where you found it
[20:40] <wxPython> i know
[20:40] <jeromeg> as the dev who wrote it commented, it's only a workaround
[20:41] <wxPython> is the action pending now?
[20:41] <jeromeg> wxPython: I think it's better to wait for a proper fix which will be integrated upstream
[20:41] <wxPython> will the final version of Ubuntu include the gnome-panel package with that bug fixed?
[20:42] <wxPython> that's all i wanna know
[20:42] <jeromeg> wxPython: if it get fixed upstream yes
[20:42] <jeromeg> if no, I guess it won't :(
[20:42] <wxPython> :(
[20:42] <wxPython> can i beg to be fixed?
[20:42] <wxPython> :)
[20:42] <jeromeg> wxPython: but this patch has only been committed (a few hours ago)
[20:43] <jeromeg> so I would say
[20:43] <wxPython> was it not tested yet?
[20:43] <jeromeg> wait and see :)
[20:43] <jeromeg> wxPython: i guess the person who worte it tested it
[20:43] <wxPython> i sure hope he finally solved the bug
[20:43] <wxPython> cause it's nearly 3 years old
[20:44] <wxPython> and it's a visual annoyance
[20:44] <jeromeg> wxPython: :)
[20:44] <wxPython> what? :)
[20:44] <jeromeg> just smiling to the "3 year old bug"
[20:45] <wxPython> it IS
[20:45] <jeromeg> some bug get forgotten, unfortunately
[20:45] <jeromeg> wxPython: yes, yes, I know
[20:45] <jeromeg> i can only acknowledge
[20:45] <jeromeg> 2005-06-22
[20:45] <wxPython> this bug is present since Ubuntu Gutsy Alpha 4
[20:45] <wxPython> so it's reeealy old
[20:46] <jeromeg> wxPython: i think it has been here for much longer
[20:46] <wxPython> it was?
[20:46] <jeromeg> anyway
[20:46] <wxPython> someone said he had never seen this bug before until I installed Ubuntu Gutsy Alpha 4
[20:46] <jeromeg> i think it would be great if you could test the patch
[20:46] <wxPython> but it was reported waaay back then in the good old days :D
[20:46] <jeromeg> wxPython: yep :)
[20:46] <wxPython> :)
[20:48] <wxPython> okay, so after this patch is applied to the gnome-panel, the ubuntu team will update hardy with that package and we will live happily ever after without that nasty, visualy annoying bug? :)
[20:48] <jeromeg> wxPython: if it solves the bug without any regression and if the packager of gnome-panel agress, yes
[20:49] <jeromeg> wxPython: but as I said, if the patch is ok, it should be fixed upstream soon, just wait a couple of hours/days to see how the devs react
[20:51] <wxPython> jeromeg okay i will try to stay patient ;)
[20:52] <wxPython> please think positive with me ;)
[20:52] <wxPython> i hope it will be acknowledged
[20:52] <wxPython> since i don't see any other solution :)
[20:53] <jeromeg> no problem, bugs are always frustrating
[20:54] <jeromeg> sorry I got to go
[20:54] <wxPython> wait
[20:54] <wxPython> one more sec
[20:54] <jeromeg> got some homework :(
[20:54] <jeromeg> ok
[20:54] <wxPython> i have notified Vincent Untz about that patch
[20:54] <jeromeg> ok
[20:54] <wxPython> but is GNOME Panel related with the gnome-panel package for Ubuntu?
[20:55] <wxPython> are those two things realted in any way?
[20:55] <wxPython> *related
[20:55] <jeromeg> yes
[20:55] <wxPython> how come?
[20:55] <jeromeg> gnome-panel available in ubuntu is only a package to install easily GNOME Panel
[20:56] <wxPython> when you said "just wait a couple of hours/days to see how the devs react"... did you ment how would Vincent react?
[20:56] <jeromeg> Vincent and others
[20:56] <wxPython> ohð
[20:56] <wxPython> oh
[20:56] <wxPython> uhmmm
[20:56] <wxPython> but how fast would they fix the gnome panel?
[20:57] <jeromeg> wxPython: dunno :) depends on a lot of things
[20:57] <wxPython> would they alter the CVS of the gnome panel or how is this going to be done?
[20:58] <wxPython> i really don't know how this works
[20:58] <jeromeg> wxPython: i'm sorry but i really got to go, in 2 sec, if the patch is accepted, it will be commited to their SVN, and available in the next release of gnome-panel
[20:58] <wxPython> ok
[20:58] <jeromeg> but we can grab the patch for ubuntu, if the package maintainer wants to
[20:58] <wxPython> thanks for everything
[20:58] <jeromeg> no problem
[20:58] <jeromeg> see yoou
[20:58] <jeromeg> *you
[20:58] <wxPython> bye now ;)
[20:59] <jeromeg> :)
[20:59] <wxPython> be good and learn ma boy ;P
[20:59] <wxPython> oh he wait to early to see this
[20:59] <wxPython> :(
[21:02] <Nightrose> yuriy: no you are not @ https://bugs.edge.launchpad.net/ubuntu/+source/amarok/+bug/181289 - I did already :P
[21:02] <ubotu> Launchpad bug 181289 in amarok "Amarok Crashes Entire System" [Undecided,Invalid]
[21:04] <yuriy> Nightrose: yeah i saw. ninja'd by 20 seconds
[21:04] <Nightrose> hehe
[21:04]  * yuriy isn't always a fan of launchpad's concurrency handling
[21:07] <wxPython> amarok?
[21:07] <wxPython> which system does it crash?
[21:07] <wxPython> Ubuntu?
[21:07]  * yuriy is hating planet's reading of wordpress feed even more now
[21:10] <Nightrose> wxPython: yes - but it is not an amarok problem
[21:10] <wxPython> so the title is not appropriate
[21:10] <Nightrose> well it is marked invalit now
[21:10] <wxPython> it should be System crashes Amarok ;)
[21:10] <Nightrose> *invalid
[21:10] <Nightrose> so who cares
[21:11] <wxPython> invalid?
[21:11] <wxPython> meaning what?
[21:11] <wxPython> solved?
[21:11] <wxPython> ignored?
[21:11] <wxPython> what?
[21:11] <Nightrose> no meaning not valid since it is not amaroks fault
[21:11] <yuriy> wxPython: meaning not a bug in amarok, he already filed another bug against the right package
[21:13] <wxPython> oh
[21:13] <wxPython> good
[21:13] <wxPython> can you please give me the link to that bug?
[21:13] <wxPython> not the invalid one
[21:13] <Nightrose> it is linked in the invalid one
[21:13] <wxPython> i wanna read what happens
[21:13] <Nightrose> in a comment
[21:13] <wxPython> oh okay
[21:14] <wxPython> Total system freeze caused by SATA drive
[21:14] <wxPython> lol
[21:14] <wxPython> :D
[21:14] <wxPython> so there was a hardware bug in the SATA drive that caused that bug
[21:15] <wxPython> i mean a driver bug for the SATA drive, there
[21:15] <wxPython> :)
[21:15] <wxPython> so a software bug :)
[21:17] <wxPython> what the hell is this thing? http://launchpadlibrarian.net/12424626/hdparminfo.txt
[21:18] <wxPython> it is attatched to the Total system freeze caused by SATA drive  bug report
[21:18] <wxPython> is that the patch for the bug or what?
[21:19] <wxPython> oh
[21:19] <wxPython> sorry
[21:19] <wxPython> didn't read the whole bug report lol
[21:20] <wxPython> his SATA drive sucks then
[21:20] <wxPython> there's no cause for an alarm for other people
[21:20] <wxPython> he should buy a better SATA drive then ;)
[21:20] <wxPython> or ehat?
[21:20] <wxPython> or what?
[21:20] <wxPython> :)
[21:21] <wxPython> he can't even produce the debug data
[21:21] <wxPython> so this is a shame
[21:32] <wraund> is it now safe for hardy users to upgrade to libc6?
[21:32] <wxPython> yes
[21:33] <wxPython> you can try and see
[21:33] <bdmurray> at least from archive.ubuntu.com - it depends on your mirror
[21:33] <wxPython> you probably won't get the latest version yet
[21:33] <wxPython> gotta wait some more
[21:33] <wxPython> mirrors are hell :)
[21:34] <wraund> awesome
[21:34] <wxPython> wraund yup ;)
[21:34] <wraund> ill check my mirror
[21:34] <pochu> wraund: apt-cache madison libc6 to make sure
[21:35] <wraund> wraund@morpheus World of Warcraft % apt-cache madison libc6 libc6 | 2.7-9ubuntu2 | http://gb.archive.ubuntu.com hardy/main Packages glibc | 2.7-9ubuntu2 | http://gb.archive.ubuntu.com hardy/main Sources
[21:35] <wraund> wraund@morpheus World of Warcraft %
[21:35] <wraund> sorry about the paste my firefox is bugged
[21:36] <wraund> also ignore the folder ^^
[21:36] <wraund> oh hey pochu :)
[21:36] <pochu> hey hey :)
[21:37] <wraund> is my mirror updated then?
[21:37] <wraund> from that output
[21:38] <pochu> yes, ubuntu2 is the fixed package
[21:39] <wraund> kk
[21:41] <wraund> wahay my machine is stable again :)
[21:42] <wxPython> wraund nice to hear that ;)
[21:42] <wxPython> mine is not
[21:43] <wxPython> reason: using Windows XP :D
[21:43] <wxPython> can't WAIT for ubuntu 8.04 final!
[21:48] <afflux> I'm going to bed now. Good night!
[21:54] <sbarjola> where can i find the moin id?
[21:56] <bdmurray> sbarjola: in your cookies file
[22:03] <sbarjola> thanks,.. what's name has the cookie?
[22:07] <bdmurray> in my cookies.txt file I found wiki.ubuntu.com and a MOIN ID


[08:50] <MrQuist> Can someone unmute me..?
[08:50] <bazhang> MrQuist, #ubuntu is not a platform for rants/complaints etc
[08:50] <MrQuist> I know, you just told me.
[08:50] <bazhang> it's for tech support only
[08:50] <MrQuist> I just explained to you what happened.
[08:50] <bazhang> file bugs, ask for help, fine
[08:51] <bazhang> MrQuist, yes, PM is not logged, this channel is
[08:51] <MrQuist> Okidokie.
[08:52] <bazhang> no need for the UBUNTU YAY after each complaint, or complaint at all; "i'm having an issue with xyz; details details details, could someone please assist me?"
[08:53] <MrQuist> You are right.\
 I was _really_ frustrated at the moment.
 i'm sorry
[08:54] <Tm_T> MrQuist: just remember that there's no excuse for bad behaviour (:
[08:55] <MrQuist> My parents..? :P hehe i don't know
[08:55] <Myrtti> so, everything is clear?
[08:55] <MrQuist> Well, I won't randomly shout out bugs and share my frustration with the world via #ubuntu anymore.
[08:56] <bazhang> your back in right?
[08:56] <MrQuist> Yes, thank you.
[08:57] <bazhang> see you
[08:57] <MrQuist> Also<EMAIL_ADDRESS>isn't mine
[08:57] <bazhang> right
[08:57] <MrQuist> Neither are sawjig@gateway/* and @staff-247-054.wireless.adelaide.edu.au
[08:57] <bazhang> more than one person has been +q over time
[08:57] <MrQuist> I know.
[08:57] <MrQuist> Didn't know you'd -q them over time.
[10:48] <Myrtti> great! MrQuist, if everything is clear here, you can now leave this channel :-)
[12:37] <DJones> May be worth keeping an eye phoquer in #ubuntu, looks to be Mint troll/ranter
[12:43] <DJones> Sun's come out, so I'm going home to enjoy it
[13:35] <Pici> services are down :(
[14:06] <genii> In #k-ops-monitor floodbots are reporting like: <FloodBotK1> WARNING: NOTICE from FloodBotK2 - [CTCP]PING<PHONE_NUMBER>[CTCP ]      but the last 4 numbers keep changing and I don't see any users with these numbers as their names in #k or #k-unregged
[14:07] <Pici> genii: those are timestamps
[14:07] <genii> Ah, OK
[14:08] <genii> Looks like the bots are bouncing off each other again
[14:23] <genii> OK, looks like FloodBotK2 needs a restart because they can't get +o in #kubuntu and keep spamming FloodBotK1. But since they can't make it into -ops-monitor I'm not sure how to restart it.
[14:25] <genii> It's originating from <IP_ADDRESS> but I don't know who's box that is ( maybe elky )
[14:29] <genii> @comment 55463 Bot acting up
[15:53] <DJones> Is freenode having more issues? I saw that services had come back online, but still seems to be a lot of disconnects
[15:53] <bazhang> yes tons
[15:53] <bazhang> at least chanserv is back
[15:53] <DJones> ok, just gone +o in case services vanish again
[15:53] <DJones> Heh, I like christel's answer to 'does chanserv work' - Occasionaly
[15:53] <bazhang> heh yeah
[15:53] <DJones> Hmmh, to late to +o in -uk, waiting for our usual troll to start at 6pm
[16:02] <DJones> I'd suggest a few more people may need to have ops in the main channels in case chanserv goes away again
[16:03] <DJones> [Global Notice] Welcome to Splitville,  Population: Shrinking -- as you may have noticed the network is suffering under the strain of yet another DDoS  attack, we are working with our sponsors to try curb what we can and apologise for the inconvenience.
[16:03] <DJones> From Christel
[16:34] <Tm_T> mhall119: hi
[16:48] <mhall119> Tm_T: hello
[16:51] <Tm_Tr> bah, almost works
[16:51] <Tm_Tr> mhall119: I'm checking what I can do regarding -touch
[16:55] <Tm_Tr> mhall119: I took some freedom here and gave you op rights, channel owners should assign more ops there though
[16:56] <mhall119> Tm_Tr: can you tell me who the channel owners are?
[16:57] <Tm_Tr> mhall119: names oubiwann and corp186 according to chanserv
[16:57] <mhall119> hmmm, don't recognize either of them
[16:57] <Tm_Tr> same problem
[16:58] <Tm_Tr> popey is listed as contact person in the wiki, hmmm
[16:59] <genii> Probably because he had #ubuntu-phone previously
[17:16] <DJones> gah, when the network goes that crazy, my irssi machine has to be rebooted
[17:16] <Unit193> Wow.
[17:18] <DJones> Just becomes unresponsive for irssi, switch to a new screen and I can reboot etc, next time, I'll just try killing irssi, I#m guessing its the stalker.pl script trying to catch up on low memory system
[17:20]  * genii makes more coffee and hands out the mugs
[17:35] <_WolfeZ_> Hello
[17:36] <_WolfeZ_> i cant send to ubuntu cause i wasnt doing good, im sorry for that please unban me! [19:35] <DJones> Please join #ubuntu-ops to discuss your ban
[17:37] <bazhang> _WolfeZ_, why do you want #ubuntu for #debian problems
[17:37] <_WolfeZ_> bazhang: I`m not, i had a problem with booting debian on ubuntu, so i make my nick like this
[17:37] <bazhang> booting debian on ubuntu?
[17:38] <_WolfeZ_> Jeah something like that, i had a problem with my usb
[17:38] <_WolfeZ_> Im sorry my english isnt verry good im a 14 years old dutch guy!
[17:41] <bazhang> _WolfeZ_, perhaps it would be easier if you join #ubuntu-nl  for dutch speakers
[17:44] <_WolfeZ_> bazhang: I am but o ubuntu are more people
[17:45] <bazhang> _WolfeZ_, /join #ubuntu-nl for now, the quiet on you in #ubuntu wont be lifted at this time
[17:45] <Myrtti> yes but if you can't clearly explain your problem, you're not going to get any kind of help
[17:45] <_WolfeZ_> Myrtti: I can explain it, but i dont understand all the heavy words!
[17:47] <_WolfeZ_> bazhang: Oke, I understand it! It was realy stupid! But yeah I will stay in nl now!
[18:13] <cprofitt> man... this DDoS attack is causing freenode some issues today
[18:16] <bazhang> over for now it seems
[18:51] <bazhang> must be troll o'clock
[18:57] <bazhang> PC!
[18:58] <bazhang> I always added a ch sound to the Ci
[18:58] <Pici> oddly enough, people know me as pc elsewhere.
[18:58] <bazhang> bizarro
[18:58] <k1l> i pronounce it as pikki
[18:59] <bazhang> it's always been Peachy to my hearing
[18:59] <Pici> Everyone pronounces it differently it seems ;)
[18:59] <bazhang> heh k1l
[19:20] <bazhang> is Snype just offering terrible "support"
[19:30] <k1l_> snype rings my alarmclocks anyway
 try ntfs then
[19:31] <bazhang> augh
[19:34] <Snype> so i got banned
[19:34] <Snype> i was helping people and bazhang said it was all wrong
[19:34] <Snype> next thing you know he bans me
[19:34] <Snype> i dont find this appropriate
[19:34] <Snype> can someone please look into it?
[19:35] <bazhang> it was all wrong
[19:35] <Snype> no it wasnt
[19:35] <Snype> idk i just wanted to help
[19:35] <Snype> and was telling everything i knew
[19:35] <Snype> atleast i was trying bazhang
[19:35] <bazhang> thats not what is needed, or appropriate
[19:35] <Snype> you banning me on the context everything i said was wrong
[19:35] <Snype> is what is not appropriate
[19:35] <Snype> you are not valuing the gesture and the spirit
[19:35] <Snype> and i wanst even wrong in the first place
[19:35] <Myrtti> if you are trying but aren't sure what you are telling is right, correct our true, then trying is not the right thing to do. being quiet is.
[19:36] <Myrtti> or true, even
[19:36] <Snype> i am sure everything i said was correct Myrtti
[19:36] <Myrtti> sudo gedit is wrong
[19:36] <Snype> it works
[19:36] <Snype> i know gksudo is recommended
[19:36] <Snype> but not mandatory
[19:36] <jbroome> so does logging in as root, but that's not advised
[19:36] <Snype> its not a law
[19:36] <Snype> i login as root all the time
[19:37] <Myrtti> good luck then.
[19:37] <AlanBell> we have some guidelines for people who want to offer support
[19:37] <Snype> this is so going on my blog
[19:37] <Snype> you guys are killing a very important thing here
[19:37] <Snype> the attitude
[19:38] <Snype> there is no point in trying to help with such admins
[19:38] <Myrtti> please go ahead, do blog
[19:38] <k1l_> Snype: didnt i just mute you because you misbehaved?
[19:38] <Snype> no that was long ago
[19:38] <k1l_> Snype: i suggested you to re-read the guidelines.
[19:38] <Snype> and you can ban me now
[19:38] <k1l_> jun 4th is not long ago.
[19:38] <Snype> i will mother fucker @ Myrtti
[19:38] <jbroome> there's a ban active now
[19:38] <k1l_> so dont troll here or in the support channel
[19:39] <AlanBell> https://wiki.ubuntu.com/IRC/SupportersGuide
[19:39] <Myrtti> well, that was mean
[19:39] <bazhang> way past the line
[19:39] <AlanBell> that was mean
[19:39] <bazhang> trolling -ot as well I suspect
[19:40] <bazhang> "does nigus sound racist?" in #u


[05:28] -queuebot:#ubuntu-release- Unapproved: rdma-core (bionic-proposed/main) [17.1-1ubuntu0.1 => 17.1-1ubuntu0.2] (desktop-core, ubuntu-server)
[05:51] -queuebot:#ubuntu-release- New binary: rust-gtk [s390x] (eoan-proposed/universe) [0.7.0-1] (no packageset)
[05:54] -queuebot:#ubuntu-release- New binary: rust-gtk [ppc64el] (eoan-proposed/universe) [0.7.0-1] (no packageset)
[05:55] -queuebot:#ubuntu-release- New binary: rust-gtk [amd64] (eoan-proposed/universe) [0.7.0-1] (no packageset)
[05:55] -queuebot:#ubuntu-release- New binary: rust-gtk [i386] (eoan-proposed/universe) [0.7.0-1] (no packageset)
[06:00] -queuebot:#ubuntu-release- New binary: rust-gtk [arm64] (eoan-proposed/universe) [0.7.0-1] (no packageset)
[06:01] -queuebot:#ubuntu-release- New binary: rust-gtk [armhf] (eoan-proposed/universe) [0.7.0-1] (no packageset)
[06:02] -queuebot:#ubuntu-release- New: accepted rust-gtk [amd64] (eoan-proposed) [0.7.0-1]
[06:02] -queuebot:#ubuntu-release- New: accepted rust-gtk [armhf] (eoan-proposed) [0.7.0-1]
[06:02] -queuebot:#ubuntu-release- New: accepted rust-gtk [arm64] (eoan-proposed) [0.7.0-1]
[06:03] -queuebot:#ubuntu-release- New: accepted golang-github-getlantern-errors [amd64] (eoan-proposed) [0.0~git20190325.abdb3e3-1]
[06:03] -queuebot:#ubuntu-release- New: accepted rust-gtk [ppc64el] (eoan-proposed) [0.7.0-1]
[06:03] -queuebot:#ubuntu-release- New: accepted rust-gtk [i386] (eoan-proposed) [0.7.0-1]
[06:03] -queuebot:#ubuntu-release- New: accepted rust-gtk [s390x] (eoan-proposed) [0.7.0-1]
[06:36] <LocutusOfBorg> vorlon, or any other AA
[06:36] <LocutusOfBorg> old binaries left on *: libtyperep-camlp4-dev (from 113.00.00-3ubuntu2)
[06:36] <LocutusOfBorg> please cleanup NBS-proposed ^^
[06:44] <cpaelzer> @release team - I like the automatic reminders if onan SRU dep8 tests failed
[06:44] <cpaelzer> thanks!
[06:44] <cpaelzer> umm I meant SRU-Team, but the release team does a lot of good things as well - I guess my subconciousness wanted to thank them as well :-)
[07:07] <infinity> sil2100: https://bugs.launchpad.net/ubuntu/+source/glibc/+bug/1842024
[07:45] <sil2100> infinity: looking! I see the test build succeeded, I assume you checked installability already as well
[07:46] <sil2100> Ah, indeed you did
[07:47] <infinity> sil2100: Yeah.  Testing a build of gcc-9 against it too.
[08:07] <doko> \o/
[09:44] <RikMills> lintian in proposed
[09:44] <RikMills> lintian/amd64 unsatisfiable Depends: libfile-find-rule-perl
[09:44] <RikMills> lintian/amd64 unsatisfiable Depends: libio-async-loop-epoll-perl (>= 0.20)
[09:44] <RikMills> huh?
[09:44] <RikMills> oh. nvm
[09:44] <RikMills> lintian is in main. those are not
[09:44] <RikMills> :/
[09:45] -queuebot:#ubuntu-release- Unapproved: ceph (bionic-proposed/main) [12.2.12-0ubuntu<IP_ADDRESS> => 12.2.12-0ubuntu<IP_ADDRESS>] (desktop-core, ubuntu-server)
[09:45] -queuebot:#ubuntu-release- Unapproved: ceph (disco-proposed/main) [13.2.6-0ubuntu<IP_ADDRESS> => 13.2.6-0ubuntu<IP_ADDRESS>] (desktop-core, ubuntu-server)
[09:52] <LocutusOfBorg> FYI, since it is difficult to have hints for autopkgtests, I'm patching rust packages to just return true in testsuite
[09:52] <LocutusOfBorg> sad thing, they pass from neutral to fail
[10:02] <LocutusOfBorg> vorlon`, please, somebody with some time, can hint a set of packages that passed from neutral to fail?
[10:02] <LocutusOfBorg> I don't want to patch half a dozen rust packages forever
[12:39] <jsech> there is any ETA for move linux-image 4.15.0-60 (Bionic) to stable?
[12:40] <apw> jsech, that is likely a question better asked on #ubuntu-kernel
[12:40] <jsech> ok thx
[13:21] <coreycb> Hi all, I was trying to force a package to not use an eoan-proposed package by setting the depends to python3-django << 2:2.2.4-1 but that doesn't work. any tips?
[13:38] <LocutusOfBorg> coreycb, depends: python3-django (==1:1.11.22-1) ?
[13:39] <coreycb> LocutusOfBorg: i tried that as well but it still wants to pull in 2:2.2.4-1
[13:40] <coreycb> LocutusOfBorg: hmm i wonder if dh_python is overriding. let me check.
[13:41] <coreycb> LocutusOfBorg: no dh_python isn't overriding
[14:14] -queuebot:#ubuntu-release- Unapproved: ec2-hibinit-agent (bionic-proposed/main) [1.0.0-0ubuntu4~18.04.2 => 1.0.0-0ubuntu4~18.04.3] (no packageset)
[14:14] -queuebot:#ubuntu-release- Unapproved: ec2-hibinit-agent (xenial-proposed/main) [1.0.0-0ubuntu4~16.04.2 => 1.0.0-0ubuntu4~16.04.3] (no packageset)
[14:14] -queuebot:#ubuntu-release- Unapproved: ec2-hibinit-agent (disco-proposed/main) [1.0.0-0ubuntu<IP_ADDRESS> => 1.0.0-0ubuntu<IP_ADDRESS>] (no packageset)
[14:18] <rbalint> tjaalton, could you please review and hopefully accept them? ^
[14:38] <vorlon> LocutusOfBorg: do you have a list of these packages that you want hinted?
[14:46] -queuebot:#ubuntu-release- New source: python-masakariclient (eoan-proposed/primary) [5.4.0-0ubuntu1]
[14:59] <LocutusOfBorg> yes vorlon
[14:59] <vorlon> are you going to give that list to me also? ;-)
[15:00] <LocutusOfBorg> yes, let me open a pad somewhere
[15:00] -queuebot:#ubuntu-release- Unapproved: accepted ec2-hibinit-agent [source] (disco-proposed) [1.0.0-0ubuntu<IP_ADDRESS>]
[15:02] -queuebot:#ubuntu-release- Unapproved: accepted ec2-hibinit-agent [source] (bionic-proposed) [1.0.0-0ubuntu4~18.04.3]
[15:04] -queuebot:#ubuntu-release- Unapproved: accepted ec2-hibinit-agent [source] (xenial-proposed) [1.0.0-0ubuntu4~16.04.3]
[15:06] -queuebot:#ubuntu-release- New: accepted linux-signed-oracle [amd64] (disco-proposed) [5.0.0-1001.2]
[15:07] <LocutusOfBorg> vorlon, https://etherpad.openstack.org/p/hints
[15:08] <LocutusOfBorg> I'm still editing, feel free to delete from there if anything is added to hints :)
[15:27] -queuebot:#ubuntu-release- Unapproved: accepted sane-backends [source] (disco-proposed) [1.0.27-3.2ubuntu1.1]
[15:29] -queuebot:#ubuntu-release- Unapproved: accepted sane-backends [source] (bionic-proposed) [1.0.27-1~experimental3ubuntu2.2]
[15:32] -queuebot:#ubuntu-release- New binary: doris [amd64] (eoan-proposed/multiverse) [5.0.3~beta+dfsg-12] (no packageset)
[15:40] <vorlon> LocutusOfBorg: rust-num-traits: we appear to be working at cross-purposes.  You say you disabled the testsuite on i386 to get it to build, why should we be deliberately building a package that doesn't pass its tests?  I had been ripping out the reverse-dependencies of rust-num-traits instead on i386
[15:41] <vorlon> it's a numeric package and it's buggy on i386 and the testsuite shows this
[15:46] <LocutusOfBorg> vorlon, it was not a regression
[15:46] <LocutusOfBorg> testsuite has been disabled in previous release, it is a bug RC in debian, we don't care about i386...
[15:47] <LocutusOfBorg> so, eventually i386 will come back from Debian...
[15:47] <LocutusOfBorg> also I saw you removed, but rust-im was broken then
[15:47] <LocutusOfBorg> this one https://launchpad.net/ubuntu/+source/rust-im-rc
[16:09] -queuebot:#ubuntu-release- New source: python-purestorage (eoan-proposed/primary) [1.17.0-0ubuntu1]
[16:18] <vorlon> LocutusOfBorg: if it comes back on its own because Debian fixes it, fine.  That's not a reason to ignore test failures and ship known-broken stuff though.  Also, per the changelog, "ignore test results everywhere"?
[16:22] <vorlon> LocutusOfBorg: regardless, I think introducing a delta to get a package to build on i386, vs removing the i386 binaries, is a bad call given that i386 is no longer supported as a host architecture
[18:44] <tjaalton> rbalint: sorry, was off today
[19:08] -queuebot:#ubuntu-release- Unapproved: ibm-java80 (xenial-release/partner) [<IP_ADDRESS>-0ubuntu1 => <IP_ADDRESS>-0ubuntu1] (no packageset) (sync)
[19:08] -queuebot:#ubuntu-release- Unapproved: ibm-java80 (bionic-release/partner) [<IP_ADDRESS>-0ubuntu1 => <IP_ADDRESS>-0ubuntu1] (no packageset) (sync)
[19:13] <coreycb> vorlon: we're in a little bit of a pickle with python3-django. i attempted to update openstack dashboard packages with (Build-)Depends on << 2:2.2.4-1 to prevent using the version in eoan-proposed, but the builds still wants to use 2:2.2.4-1. side note: upstream may or may not land 2.2.4 support this cycle; it hasn't landed yet. have any suggestions on how to move forward? can i force BDs to use what's in
[19:13] <coreycb> eoan-release?
[19:13] <cjwatson> B-D: << basically doesn't work except at best maybe to force failures
[19:14] <cjwatson> The only way to do something like that would be to have a parallel source package with the earlier version you need
[19:14] <coreycb> cjwatson: ok thanks for confirming. i tried = as well and no luck there either.
[19:14] <cjwatson> I have no idea whether that is practical in this case
[19:15] <coreycb> cjwatson: what do you mean by parallel?
[19:15] <cjwatson> In general (notwithstanding the conversation in #ubuntu-devel at the moment ...) older versions of binary packages aren't kept around
[19:16] <cjwatson> Sometimes it's possible to have a separate older version with different source and binary *names* (not just versions) to work around this
[19:16] <cjwatson> I suspect that's pretty impractical with python3-django though
[19:17] <cjwatson> So ... yes, you're in a pickle, and it's kind of inherent to the Debian-style distribution model generally only shipping one version of things
[19:17] <coreycb> cjwatson: thanks for the explanation. certainly doesn't sound pretty.
[19:19] <cjwatson> Since the newer python-django hasn't migrated to release yet, we're not yet committed to shipping with it, of course
[19:19] <cjwatson> But I don't know how much other stuff that would hold back
[19:19] <vorlon> coreycb: right, the end goal is that by the end of the cycle, -proposed is approximately empty, and everything in the release pocket which we ship is self-hosting in terms of build/install/test
[19:20] <vorlon> in practice only "install" is hard-enforced, build+test are squishier, at least partly by design in order to avoid making it even harder than necessary to move things from proposed to release due to ordering constraints
[19:21] <vorlon> we also build against everything in -proposed because that's usually also the correct optimization (and sometimes strictly required, for transitions)
[19:22] <vorlon> coreycb: so if openstack isn't going to be compatible with python-django 2.2 by release time, then we should probably remove it from -proposed to let packages build
[19:22] <vorlon> (or you could disable any build-time tests that rely on a compatible django?)
[19:22] <cjwatson> Though check how much else that would break that's already been built against it ...
[19:23] <coreycb> vorlon: ah, so install Depends should understand << logic?
[19:23] <coreycb> vorlon: yes you said that. so maybe i can disable tests
[19:24] <coreycb> i'll look into that a bit more and also see if the upstream patches are backward compatible in case they do land.
[19:24] <vorlon> coreycb: both runtime and build-time depends "understand" << logic, it's just a question of how the archive helps you resolve unsatisfied deps
[19:24] <coreycb> vorlon: right ok
[19:24] <cjwatson> All that Depends: << is likely to do is help prevent other things from migrating when they would break you
[19:24]  * vorlon nods
[19:25] <cjwatson> It won't make it possible for django 1.11 and 2.2 to coexist in eoan
[19:26] <coreycb> cjwatson: vorlon: ok thanks for all the info. i have some homework to do and will get back to you if we need to look into keeping 1.11.
[19:27] <vorlon> coreycb: the reality is, python-django 2.2 doesn't look like it's going anywhere for eoan anyway, there are various revdeps with failing autopkgtests unrelated to openstack
[19:38] -queuebot:#ubuntu-release- New binary: haskell-criterion-measurement [amd64] (eoan-proposed/universe) [<IP_ADDRESS>-1] (no packageset)
[19:39] -queuebot:#ubuntu-release- New binary: haskell-bytestring-conversion [ppc64el] (eoan-proposed/universe) [0.3.1-6build1] (no packageset)
[19:39] -queuebot:#ubuntu-release- New binary: haskell-criterion-measurement [i386] (eoan-proposed/universe) [<IP_ADDRESS>-1] (no packageset)
[19:40] -queuebot:#ubuntu-release- New binary: haskell-libyaml [amd64] (eoan-proposed/universe) [<IP_ADDRESS>-2] (no packageset)
[19:40] -queuebot:#ubuntu-release- New binary: haskell-libyaml [i386] (eoan-proposed/universe) [<IP_ADDRESS>-2] (no packageset)
[19:42] -queuebot:#ubuntu-release- New binary: haskell-cassava-megaparsec [amd64] (eoan-proposed/universe) [2.0.0-1] (no packageset)
[19:42] -queuebot:#ubuntu-release- New binary: haskell-criterion-measurement [arm64] (eoan-proposed/universe) [<IP_ADDRESS>-1] (no packageset)
[19:42] -queuebot:#ubuntu-release- New binary: haskell-cassava-megaparsec [i386] (eoan-proposed/universe) [2.0.0-1] (no packageset)
[19:43] -queuebot:#ubuntu-release- New binary: haskell-criterion-measurement [armhf] (eoan-proposed/universe) [<IP_ADDRESS>-1] (no packageset)
[19:43] -queuebot:#ubuntu-release- New binary: haskell-libyaml [armhf] (eoan-proposed/universe) [<IP_ADDRESS>-2] (no packageset)
[19:43] -queuebot:#ubuntu-release- New binary: haskell-libyaml [arm64] (eoan-proposed/universe) [<IP_ADDRESS>-2] (no packageset)
[19:46] -queuebot:#ubuntu-release- New binary: haskell-cassava-megaparsec [arm64] (eoan-proposed/universe) [2.0.0-1] (no packageset)
[19:47] -queuebot:#ubuntu-release- New binary: haskell-cassava-megaparsec [armhf] (eoan-proposed/universe) [2.0.0-1] (no packageset)
[19:48] -queuebot:#ubuntu-release- New binary: haskell-libyaml [ppc64el] (eoan-proposed/universe) [<IP_ADDRESS>-2] (no packageset)
[19:50] <coreycb> vorlon: i wouldn't object to sticking with 1.11 this cycle
[19:50] -queuebot:#ubuntu-release- New binary: haskell-libyaml [s390x] (eoan-proposed/universe) [<IP_ADDRESS>-2] (no packageset)
[19:54] -queuebot:#ubuntu-release- New binary: haskell-cassava-megaparsec [ppc64el] (eoan-proposed/universe) [2.0.0-1] (no packageset)
[20:05] -queuebot:#ubuntu-release- New binary: haskell-cassava-megaparsec [s390x] (eoan-proposed/universe) [2.0.0-1] (no packageset)
[20:41] -queuebot:#ubuntu-release- New binary: haskell-criterion-measurement [ppc64el] (eoan-proposed/universe) [<IP_ADDRESS>-1] (no packageset)
[21:13] -queuebot:#ubuntu-release- New: accepted haskell-criterion-measurement [ppc64el] (eoan-proposed) [<IP_ADDRESS>-1]
[21:13] -queuebot:#ubuntu-release- New: accepted haskell-cassava-megaparsec [arm64] (eoan-proposed) [2.0.0-1]
[21:13] -queuebot:#ubuntu-release- New: accepted haskell-cassava-megaparsec [ppc64el] (eoan-proposed) [2.0.0-1]
[21:13] -queuebot:#ubuntu-release- New: accepted haskell-libyaml [armhf] (eoan-proposed) [<IP_ADDRESS>-2]
[21:13] -queuebot:#ubuntu-release- New: accepted haskell-libyaml [s390x] (eoan-proposed) [<IP_ADDRESS>-2]
[21:13] -queuebot:#ubuntu-release- New: accepted haskell-cassava-megaparsec [armhf] (eoan-proposed) [2.0.0-1]
[21:13] -queuebot:#ubuntu-release- New: accepted haskell-libyaml [ppc64el] (eoan-proposed) [<IP_ADDRESS>-2]
[21:13] -queuebot:#ubuntu-release- New: accepted haskell-cassava-megaparsec [s390x] (eoan-proposed) [2.0.0-1]
[21:14] -queuebot:#ubuntu-release- New: accepted haskell-cassava-megaparsec [amd64] (eoan-proposed) [2.0.0-1]
[21:14] -queuebot:#ubuntu-release- New: accepted haskell-criterion-measurement [arm64] (eoan-proposed) [<IP_ADDRESS>-1]
[21:14] -queuebot:#ubuntu-release- New: accepted haskell-libyaml [amd64] (eoan-proposed) [<IP_ADDRESS>-2]
[21:14] -queuebot:#ubuntu-release- New: accepted haskell-libyaml [i386] (eoan-proposed) [<IP_ADDRESS>-2]
[21:14] -queuebot:#ubuntu-release- New: accepted haskell-cassava-megaparsec [i386] (eoan-proposed) [2.0.0-1]
[21:14] -queuebot:#ubuntu-release- New: accepted haskell-libyaml [arm64] (eoan-proposed) [<IP_ADDRESS>-2]
[21:14] -queuebot:#ubuntu-release- New: accepted haskell-criterion-measurement [armhf] (eoan-proposed) [<IP_ADDRESS>-1]
[21:14] -queuebot:#ubuntu-release- New: accepted doris [amd64] (eoan-proposed) [5.0.3~beta+dfsg-12]
[21:14] -queuebot:#ubuntu-release- New: accepted haskell-criterion-measurement [i386] (eoan-proposed) [<IP_ADDRESS>-1]
[21:14] -queuebot:#ubuntu-release- New: accepted haskell-criterion-measurement [amd64] (eoan-proposed) [<IP_ADDRESS>-1]
[22:13] -queuebot:#ubuntu-release- Unapproved: accepted shadow [source] (disco-proposed) [1:4.5-1.1ubuntu2.1]
[22:14] -queuebot:#ubuntu-release- Unapproved: accepted shadow [source] (bionic-proposed) [1:4.5-1ubuntu2.1]
[22:15] -queuebot:#ubuntu-release- Unapproved: accepted shadow [source] (xenial-proposed) [1:4.2-3.1ubuntu5.5]
[22:52] -queuebot:#ubuntu-release- Unapproved: accepted libvirt [source] (disco-proposed) [5.0.0-1ubuntu2.5]


[00:11] <psusi> why does linux-meta only contain debian/ and debian/rules does not even look like it builds anything?
[00:13] <jgoguen> I'm getting random kernel panics on Ubuntu Intrepid, 2.6.27-9, caps lock blinks, nothing in the logs, not even Alt+SysRq keys have any effect...how else can I get enough information to either add to or create a bug report for this?
[01:52] <jgoguen> I'm getting random kernel panics on Ubuntu Intrepid, 2.6.27-9, caps lock blinks, nothing in the logs, not even Alt+SysRq keys have any effect...how else can I get enough information to either add to or create a bug report for this?
[02:43] <jgoguen> I'm getting random kernel panics on Ubuntu Intrepid, 2.6.27-9, caps lock blinks, nothing in the logs, not even Alt+SysRq keys have any effect...how else can I get enough information to either add to or create a bug report for this?
[02:45] <stgraber> 4th time you're pasting this one. Most developers are at UDS or going to UDS at the moment, I wouldn't expect an answer and asking once an hour won't help.
[02:46] <stgraber> I would suggest looking at the wiki pages for Kernel debuging, then file a bug report with all the required information (dmesg, lspci, ...)
[02:47] <jgoguen> stgraber: oh, I didn't know UDS was now...I have been on the kernel page, but all the other bugs without obvious problems in the requested files seem to be inactive, but I'll go ahead and file another one
[17:29] <glick> hello
[17:30] <glick> excuse me im following along on the community Kernel/Compile docs and im running into some problems/inconsistencies
[17:30] <glick> for example when in the kernel source directory i issue this command:
[17:30] <glick> CONCURRENCY_LEVEL=2 AUTOBUILD=1 NOEXTRAS=1 fakeroot debian/rules binary-generic
[17:31] <glick> i get the following error:
[17:31] <glick> /usr/bin/fakeroot: line 164: debian/rules: No such file or directory
[17:33] <glick> it appears that the debian subfolder is empty
[18:02] <alex_joni> glick: depends how you got the sources
[18:16] <ahmad1> I have "Multimedia audio controller: Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6 Family) AC'97 Audio Controller (rev 03)"
[18:16] <ahmad1> it is working correctly but the mic is not
[18:16] <ahmad1> can anyone guide me?
[18:19] <andersk> The first thing to check would be the capture volume: http://linux.dell.com/wiki/index.php/Ubuntu_7.10/Issues/External_Microphone_Capture_Volume_Low
[18:23] <ahmad1> andersk: thanks for ur interest, I am checking that
[18:27] <ahmad1> andersk: I don't have these tracks (Front, MUX, Digital)
[18:28] <andersk> The exact tracks vary by hardware.  I dunno; play around with whatever tracks you have.
[18:29] <ahmad1> andersk: the Capture track has a small icon "Toggle audio recording from capture", it is off
[18:30] <ahmad1> andersk: every time i toggle it and close the window, it returns off again
[18:32] <andersk> Interesting.  You could also try `alsamixer -Dhw:0 -Vcapture` (see man alsamixer)?  I'm running out of ideas, though.
[18:41] <ahmad1> andersk: the capture line is set to 100 and is written by red (the man ensures that this is the on mode)
[18:41] <ahmad1> but still nothing is recorded
[18:43] <andersk> You also have to select the appropriate capture device (for example, I have Mic, Mix, and Internal Mic) by highlighting it and pressing space.
[18:43] <andersk> I also have a Mic Boost slider that controls the volume of the mic.
[18:49] <ahmad1> andersk: I don't have boxes over these tracks and pressing space toggles one and disable the others (written in man also)
[18:49] <ahmad1> how can i save in alsamixer (i press "esc" to exit)
[18:55] <andersk> Changes don't need to be saved; they're applied immediately.
[18:56] <ahmad1> andersk: so is it kernel problem?
[18:58] <andersk> I don't know.
[18:59] <ahmad1> :-D it worked
[19:00] <ahmad1> i increses the bars over "IEC958 P"
[19:00] <ahmad1> I don't know what is that but it works
[19:01] <andersk> Great.
[19:03] <ahmad1> andersk, thnx for ur help :)
[23:11] <damianc> hello
[23:13] <damianc> anyone awake
[23:19] <damianc> hello
[23:43] <damianc> where is everyone


[01:25] <wish8> Hey guys! Im trying to launch an ubuntu-cloud image in a vm, but Im getting this error.
[01:25] <wish8> Starting serial terminal on interface serial0.
[01:25] <wish8> The issue: It stays on this screen. As if the os is not initializing.
[01:25] <wish8> The proxmox server is nested through vmware vm.
[01:25] <wish8> I have also enabled virtualization
[01:25] <wish8> image: jammy-server-cloudimg-arm64.img
[01:25] <wish8> ubuntu-20.04-minimal-cloudimg-amd64.img
[01:25] <wish8> Steps I took:
[01:25] <wish8> create 100 --memory 2048 --balloon 1 --core 3 --name ubuntu-cloud --net0 virtio,bridge=vmbr0 --serial0 socket --vga serial0 --scsihw virtio-scsi-pci --scsi0 local-lvm:vm:-100disk-0
[01:25] <wish8> Then initialized and mounted a cloudinit drive.
[01:25] <wish8> Any ideas on whats going on?
[05:35] <SuperLag> When the install is complete, the default is to reboot the machine. Is there a way I can get it to shut down, instead? I'd rather not power off hard if I don't have to. I'm installing it in a VM, and I want to disconnect the VM or it'll boot from it on the next boot, by default.