[00:05] <blueyed> Any hint on bug 255150 ?
[00:05] <blueyed> the modules in -updates are more recent than the kernel.. is the kernel supposed to ever enter -updates?
[00:06] <wgrant> That particular one won't, no.
[00:06] <wgrant> The ABI is already 21.
[00:06] <wgrant> So they need to be rebuilt again.
[00:07] <wgrant> And an archive admin should have noticed that that wasn't a good idea.
[00:07] <blueyed> there is a rebuild for -21 already.. but when will it go to updates?
[00:07] <blueyed> wgrant: pitti is subscribed and being poked
[00:08] <wgrant> Archive admins need to know to copy them both when the kernel update is published. It's the only way this is going to ever work.
[00:11] <blueyed> ok, I've updated bug 260722 accordingly.
[00:11] <blueyed> but the question remains: if it takes more than a few days, the current messup should get fixed probably. there's one dupe a day now for the proposed/updates mismatch.
[00:12] <wgrant> Aren't the -19 modules still published?
[00:13] <wgrant> Ah, no.
[00:13] <wgrant> Hm, actually, yes they are - I was looking at the wrong name.
[00:13] <wgrant> So where's the problem?
[00:13] <wgrant> virtualbox-ose-modules-2.6.24-19-generic |     24.0.4 | hardy-updates/universe | amd64, i386
[00:49] <blueyed> wgrant: they are published, but IIRC the meta package depends on -20 already (and -20 is published, too).
[00:50] <wgrant> blueyed: Oh, right, forgot about the metapackage.
[02:54] <amikrop> How do we create the .deb out of the source package?
[02:55] <Elbrus> amikrop: there are several ways. I use pdebuild
[02:55] <amikrop> Elbrus: which is the standard one?
[02:55] <Elbrus> amikrop: but there is I believe also dpkg-buildpackage (probably the standard, but I am not sure)
[02:56] <amikrop> ok
[02:56] <amikrop> thanks :)
[02:57] <cody-somerville> !pbuilder
[02:58] <Elbrus> !pdebuild
[02:59] <Elbrus> ok, pdebuild works on top of pbuilder, so a non-root can run it I believe
[03:06] <persia> StevenK: When you have a chance, would you mind pushing the no-change rebuilds against libbluetooth-dev to the ~bluetooth PPA?
[03:07] <StevenK> persia: Ew
[03:08] <persia> StevenK: Don't worry about versioning, it's just that with uploads of some of it frozen until beta, I think it would be better to toss it somewhere for wider testing.
[03:11] <persia> StevenK: Alternately, do you have a better suggestion for testing?  I can build locally, but I'm not sure everyone can.
[03:11] <StevenK> persia: Hold on, I'll sorting out a list so I can sign and upload
[03:12] <persia> StevenK: OK.  Sorry to keep poking you with slightly distasteful things today :)
[03:18] <StevenK> persia: Uploaded.
[03:19] <persia> StevenK: Thanks.  I'll try to run through the whole suite later.
[03:20] <persia> And of course, if anyone else feels like testing the new bluetooth stack to see if it has fewer regressions against hardy than the current stack in intrepid, help is welcome.  Please comment on bug #276343 with any discovered regressions.
[03:20] <persia> (or bug #274950 for core BlueZ regressions)
[03:48] <Hobbsee> jono: contentless pong?
[03:49]  * wgrant contentless-pingfloods Hobbsee.
[03:49]  * Hobbsee puts wgrant out with the rubbish, ready for the rubbish truck.
[03:49] <wgrant> It's already been, I'm afraid. You'll have to wait a week.
[03:51] <Hobbsee> it just left then.
[03:51]  * ajmitch watches wgrant decompose with the rest for the next week
[03:53]  * wgrant decomposes entertainingly.
[03:53]  * persia stacks up bleachers
[04:09] <Elbrus> I am working on a package that has a configure dependency in the clean rule. Isn't that strange? That way you will always end up with a large diff because your Makefiles will be touched, right???
[04:10] <persia> Elbrus: Some maintainers like to set things up that way so that the Makefiles never change on the buildds.
[04:11] <persia> Personally, I don't like it, but it's not something you should disable unless you have a good reason.
[04:11] <ScottK-laptop> Good day all.
[04:11] <Elbrus> persia: so how to prevent the Makefiles to end up in the .diff.gz??
[04:12] <TheMuso> Hey ScottK-laptop.
[04:12] <ScottK-laptop> Hobbsee: I took the plunge and my laptop is running KDE4 Intrepid now.  It's not too bad.
[04:12] <ScottK-laptop> heya TheMuso
[04:12] <ScottK-laptop> Considering I absolutely hate anything new, that's high praise from me.
[04:12] <persia> Elbrus: Don't.  They live in the diff.gz.
[04:12] <Elbrus> and I try to get rid of a debian/files in the source tar.gz, but rm -f debian/files in clean-patched doesn't work
[04:13] <Hobbsee> ScottK-laptop: i hope it's bug-free.
[04:13] <Elbrus> persia: ok.
[04:13] <persia> Elbrus: If you're preparing a package from scratch, you don't want to do it this way.  If you're editing an existing package, you don't want to change this.
[04:13] <Hobbsee> ScottK-laptop: seeing as i think a lot may switch from ubuntu.
[04:13] <ScottK-laptop> Elbrus: You can't patch a file to disappear.  The most you can do is make one empty.
[04:13] <StevenK> ScottK-laptop: Is the reverse also true?
[04:13] <ScottK-laptop> Hobbsee: It's certainly not bug free, but it's not too bad.
[04:13] <Hobbsee> ScottK-laptop: oh good.
[04:13] <Elbrus> the debian/files prevents the package from building on i386
[04:13] <ScottK-laptop> Most of the stuff I use seems to work and isn't exceptionally crashy.
[04:15] <Elbrus> ScottK-laptop: so should I just provide an empty debian/files and ignore the lintian warning?
[04:15] <StevenK> Elbrus: Um, ew
[04:15] <StevenK> Elbrus: Including an empty debian/files will make dpkg hate you
[04:16] <Elbrus> s/warning/error
[04:16] <Elbrus> StevenK: so how do I work around this issue?
[04:18] <Elbrus> StevenK: it contains: lazarus_0.9.1beta-0cvs20040530-0_i386.deb development optional
[04:18] <Elbrus> StevenK: the package is version 0.9.24-0-12
[04:18] <StevenK> Not according to that, it isn't
[04:18] <ScottK-laptop> Elbrus: Generally you'll have to repack the orig.tar.gz.
[04:20] <Elbrus> ScottK-laptop: ok, just means that syncing from debian does not work... Is it possible that dpkg previously was not so picky?
[04:20] <StevenK> debian/files is in the .diff.gz?
[04:20] <StevenK> If so, the clean rule needs to be fixed
[04:21] <Elbrus> StevenK: debian/files is in lazarus_0.9.24-0.orig.tar.gz
[04:21] <StevenK> Errrrr
[04:21] <RAOF> Ewww
[04:21] <StevenK> What RAOF said
[04:21] <wgrant> Urrrrgh.
[04:22] <StevenK> Files under debian/ do not belong in an .orig
[04:22] <RAOF> _Especially_ files generated during the build process of a Debian package!
[04:23] <persia> Removing such files in debian/clean (at the *very* top, before anything else) is usually a good idea.
[04:23] <wgrant> Where is upstream, and can I break into the MOTU weapon store before visiting them?
[04:24] <persia> Such action should be immediately followed by a clear complaint to upstream about the appropriate practices of software releases.
[04:24] <persia> wgrant: Were you not issued a key to the armoury already?
[04:24] <wgrant> persia: Unfortunately not.
[04:25]  * persia looks for the "How to be a well behaved upstream" page on the wiki
[04:25]  * RAOF still needs to write it.
[04:25] <Elbrus> persia: my clean starts like clean: patch configure clean-patched unpatch
[04:25]  * StevenK jingles the keys to the ubuntu-archive weapons locker
[04:25] <Elbrus> persia: where should I put the rm -f
[04:25]  * wgrant robs StevenK.
[04:26] <persia> Elbrus: -rm -f under clean: in debian/rules
[04:26]  * StevenK notes the keys self-destruct after leaving his person
[04:26] <Elbrus> persia: but aren't the patch etc not first applied?
[04:26] <StevenK> Elbrus: That's a bad clean rule
[04:26] <wgrant> StevenK: I'll just grab Hobbsee's instead.
[04:26] <persia> https://wiki.ubuntu.com/UpstreamGuide
[04:27] <StevenK> Elbrus: clean: clean-patched unpatch
[04:27] <persia> Elbrus: You want to delete that file before you do *anything* else, unconditionally, and always.
[04:29] <persia> RAOF: Since most of the "How to be a good upstream" page is already written, and it seemed to be on your TODO list, would you mind adding the "Don't including packaging data for Debian, Fedora, Slackware, Gentoo, or other distributions in your release tarballs.  why?" section?
[04:43] <fabrice_sp> Hi. To solve Bug #271016, I'm trying to build taskjuggler against KDE 4, but it fails in configure saying that KDE libraries are not there. Are there guidelines on what to do to migrate an app from KDE 3.5 to KDE 4?
[04:45] <Elbrus> fabrice_sp: http://techbase.kde.org/Development/Tutorials/KDE4_Porting_Guide
[04:46] <fabrice_sp> Thanks Elbrus. Let's try that as this package strongly depends on libkcal
[04:52]  * NCommander plays with pam
[04:56] <ScottK> NCommander: kde4bindings is calling you.
[04:57]  * ScottK figures causing one nightmare tonight is enough and goes to bed.
[04:58] <NCommander> Ack
[04:58]  * NCommander duct tapes ScottK to a wall
[05:26] <uniscript> is there a document somewhere that describes how to add menu items, icons and mimetypes (perhaps multiple documents) when creating a package?
[05:38] <fabrice_sp> Hi uniscript. You can begin with debian policy (http://www.debian.org/doc/debian-policy/index.html#contents). There is specific content for menu and mime
[06:32] <Hobbsee> jono: repong?
[06:32] <jono> hey Hobbsee - I mentioned earlier - I sorted it out, no worries
[06:32] <Hobbsee> jono: oh, okay.
[06:33] <jono> :)
[06:35]  * Elbrus goes to bed and continues with repacking lazarus tomorrow
[06:48] <dholbach> good morning
[06:52] <iulian> Morning Daniel.
[06:53] <dholbach> hi iulian!
[07:24] <porthose> If a kind Universe Sponsor has some time, could you please have a look at Bug #248216.  Thanks :)
[07:27] <dholbach> porthose: what do you think about testing if the directory exists and removing it only then instead of removing the rmdir call?
[07:28] <porthose> Ok sounds good
[07:28] <porthose> will rework things
[07:28] <dholbach> great
[07:28] <dholbach> ping me once you changed it and I'll give it a go
[07:28] <porthose> sure will thanks :)
[07:28] <dholbach> anytime
[07:34]  * iulian wonders if the archive admins will close the bugs from the list before Beta Release.
[07:36] <slangasek> "the list"?
[07:37] <iulian> slangasek: https://bugs.edge.launchpad.net/~ubuntu-archive
[07:41] <slangasek> mostly not.  Is there a specific bug on the list that should be addressed before beta?
[07:45] <iulian> slangasek: bug 274276. Some users already mailed the upstream saying that the current version doesn't work. The fixed version is already in Debian so all we need is to sync with. For Ubuntu users I have set up a PPA with the fixed version but I'd like to see it fixed in the repo too because I'm sure that we don't want useless packages in the archive.
[07:47] <slangasek> that could be done, because it's not on the critical path for beta; but /because/ it's not on the critical path for beta, it's also probably not a priority for the archive admins over the next two days...
[07:51]  * Hobbsee wonders why htey don't just manually sync it
[07:56] <porthose> dholbach: ping  New deb.diff for Bug #248216 :)
[07:56] <dholbach> porthose: will take a look at it in a bit
[07:57] <iulian> slangasek: Ah, OK, I didn't know that they will look at sync requests after the Beta is released.
[07:57] <porthose> Thanks :)
[07:58]  * NCommander sets the Shadows on vorian 
[07:58] <NCommander> argh
[07:58] <NCommander> Autocomplete screws me over again
[08:31] <dholbach> porthose: replied
[08:33] <porthose> Thanks will make those changes :)
[08:39] <dholbach> ROCK
[08:40] <BugMaN> hi dholbach, you see our photos from ubuntu-it meeting ?
[08:42] <dholbach> BugMaN: in your blog? yeah - looks like you got a lot of people together
[08:43] <BugMaN> dholbach: yep :)
[09:05] <porthose> dholbach:  changes made :)  Bug #248216
[09:33] <dholbach> porthose: updated
[09:39] <porthose> dholbach: Thanks :)
[09:40] <dholbach> anytime
[09:41] <huats> morning everyone :)
[09:41] <huats> hey dholbach and porthose
[09:44] <dholbach> hiya huats
[09:52] <porthose> huats: hi ya huats
[09:54] <porthose> g'night all
[10:03] <bmm> This must be the most commen question ever, but: I did a dput revu ccbuild_1.5.7_source.changes and have "Successfully.." lines in my .upload file. What could have gone wrong?
[10:04] <bmm> (Oh, I uploaded yesterday, so it did have some time to update)
[10:09] <bmm> Oh, wait. Maybe merging my accounts was needed _before_ I upload a new package. I'll try again. Thanx!
[10:11] <wgrant> bmm: You should just have needed to log in.
[10:11] <bmm> wgrant: hmm... then maybe something else went wrong. I've done a new upload by removing my .upload and doing dput on the source.changes again.
[10:11] <wgrant> bmm: I can reprocess the existing upload if you want.
[10:11] <wgrant> I'll see what goes wrong.
[10:13] <bmm> wgrant: Cool. The new dput was done minutes ago, so it may take some time to show up. Maybe this second one will be successfull. The full package name is ccbuild and it's a new upstream 1.5.7
[10:13] <wgrant> bmm: That worked.
[10:13] <bmm> wgrant: Cool, thanx!
[10:13] <wgrant> bmm: I just reprocessed the existing upload, and it worked fine.
[10:13] <wgrant> New upstream versions shouldn't be on REVU.
[10:14] <bmm> ah, must have been some kind of thing with the login or merge. I've been out of revu for quite some time ;)
[10:14] <bmm> Ah.. new policies. I'm feeling old already :P Where should they go, where can I read up on the new way to handle this?
[10:15] <wgrant> Well, firstly... why do we want this new upstream version?
[10:16] <bmm> wgrant: It supports spaces instead of tabs in the configuration file, which is a new feature people like
[10:16] <wgrant> We're well past FF, so we need a good reason.
[10:16] <wgrant> That doesn't sound like a particularly compelling nor safe new feature.
[10:16] <bmm> wgrant: Oh, I'm not pushing this for intrepid.
[10:16] <bmm> Sorry for that
[10:16] <wgrant> Ah.
[10:16] <wgrant> You'll need to wait for Jaunty to open, then.
[10:16] <wgrant> But https://wiki.ubuntu.com/PackagingGuide/Recipes/PackageUpdate is the documentation you want.
[10:17] <bmm> wgrant: I just got a new version and decided to get the package quality tested again. I'm thinking about moving it to debian, but for that I decided to first go through revu again.
[10:17] <bmm> wgrant: np, I'll wait :D
[10:43] <k0p> james_w, there?
[10:45] <james_w> hey k0p
[10:46] <k0p> james_w, yeah, there're a mistake in upstream.
[10:50] <james_w> k0p: cool, have you notified them?
[10:50] <k0p> james_w, in some minutes it will be fix.
[10:51] <james_w> k0p: cool, point me to the commit in trac and I will upload :-)
[10:53] <k0p> james_w, http://trac.umitproject.org/changeset/3743
[10:54] <james_w> k0p: uploaded, thanks for your contribution
[10:55] <k0p> thanks for your help too. And now
[10:55] <k0p> ?
[10:55] <k0p> It will be apply on universe?
[10:56] <james_w> it will hit the queue in a moment, and then someone will click the button to approve it shortly, it will be built, and then be available
[10:56] <k0p> ok :)
[10:56] <k0p> need I do something more?
[10:57] <k0p> in LP or something else?
[10:58] <james_w> k0p: no, it should all be automatic
[10:58] <k0p> ok :)
[10:58] <k0p> thanks.
[10:58] <k0p> now I have to go
[10:58] <k0p> Cya later. :)
[10:58] <james_w> bye
[12:17] <amarillion> Hey
[12:17] <amarillion> I think I fixed a bug in avant-window-navigator. Could somebody guide me with submitting the patch?
[12:18] <amarillion> I'm trying to create a debdiff but the diff I get contains way more than what I changed
[12:26] <amarillion> Here is what I did:
[12:27] <amarillion> sudo apt-get build-dep avant-window-navigator; apt-get source avant-window-navigator
[12:27] <amarillion> ... fix bug ...
[12:27] <amarillion> debuild -b
[12:27] <amarillion> test
[12:27] <amarillion> debuild -S
[12:27] <amarillion> debdiff *.dsc
[12:27] <amarillion> but the resulting diff contains way more changes than I made
[12:29] <azeem> what kind of changes?
[12:29] <amarillion> Well, I added one line to the code
[12:29] <amarillion> And I updated debian/changelog
[12:29] <amarillion> This is the way I should do it, right?
[12:30] <azeem> sure, what kind of changes are there /additionally/ than to what you expect?
[12:33] <amarillion> Is there a place where I can paste it?
[12:34] <azeem> paste.ubuntu.com, I guess
[12:34] <amarillion> nm, it's here: http://pastebin.bafserv.com/2690
[12:34] <amarillion> The changes I made are only line 6-11 and 247-8
[12:36] <azeem> looks like the rest are generated source files with some hashes in it
[12:37] <amarillion> Hmm so it's not my debdiff usage, the package is just not cleaning up after itself?
[12:37] <amarillion> I'll can edit the patch manually I guess
[12:38] <azeem> I'm not sure what those .desktop changes are about, check debian/rules whether it is mucking with that
[12:41] <amarillion> It doesn't look like. I'm not sure though, it's cdbs and I'm not at all familiar with that
[13:13] <amarillion> ok, I just solved it by doing it all again without building the binary, so it doesn't get messed up. Thanks for the help azeem
[13:23] <weboide> Hi, I don't really know if that'd be the place to ask, but I don't really know what to do, I did a package-update following the ubuntu wiki tutorial, and now I don't know if I should just post my .diff.gz as attachment to the bug report.
[14:04] <slytherin> superm1: just a quick note. do we plan to analyze rebuilds of any KDE packages related to bluetooth?
[14:18] <nxvl> for FFe de i need 1 or 2 ACK's?
[14:21] <james_w> nxvl: two
[14:23] <nxvl> james_w: thnks
[14:48] <superm1> slytherin, who normally handles the KDE stuff?
[15:01] <slytherin> superm1: no idea.
[15:02] <superm1> slytherin, we should have taken care of all packages that needed libbluetooth though
[15:02] <superm1> slytherin, so anything left would be userspace app
[15:03] <slytherin> hmm, what about indirect rdepends i.e. some kde app which depends on libbtctl
[15:03] <slytherin> oops, I meant reverse-builde-depends
[15:06] <directhex> do userspace apps change?
[15:26] <superm1> slytherin, well it certainly wouldn't hurt to investigate
[15:26] <superm1> slytherin, but the highest priority stuff is taken care of at least
[15:30] <norsetto> devfil_: around?
[15:30] <devfil_> norsetto: yes
[15:30] <devfil_> what's up?
[15:31] <norsetto> devfil_: can you check bug 273677?
[15:31] <norsetto> devfil_: what you did for wxwidgets2.8 also works here but I don't think its the good solution
[15:33] <devfil_> norsetto: so, what do you think is the best solution that we should adopt?
[15:35] <norsetto> devfil_: no idea, we should ask to somebody who is knowledgeable about pycentral
[15:36] <norsetto> devfil_: the problem is that pycentral changed dir to /usr/share/pyshared, so, what is hardcoded in debian/rules doesn't work anymore
[15:36] <norsetto> devfil_: also, what I'm afraid of, is that what you did will break the alternative system
[15:36] <devfil_> norsetto: maybe building bitpim with wxwidgets2.8 is the best solution to do as it seems quite stable
[15:37] <norsetto> devfil_: well, the problem is also on other apps, not just bitpim, and its because of wxwidgets2.6
[15:37] <norsetto> devfil_: so, we have to correct the root cause, not the symptoms ...
[15:38] <norsetto> devfil_: what we could do in intrepid is see if we can transition to wxwidget2.8 and drop 2.6 alltogether
[15:38] <norsetto> devfil_: I mean, in jaunty
[15:39] <devfil_> norsetto: is too late, we will do it in jaunty
[15:43] <devfil_> norsetto: at least we can install upstream wx.pth
[15:45] <norsetto> devfil_: upstream wx.pth is exactly the same as the one we are supposed to install, its the install location the problem, and the way we install it now I think break the alternative system
[15:46] <devfil_> norsetto: uhm then we can try to patch sources in order to use wx.version(2.6) instead of import wx
[15:46] <norsetto> devfil_: asking to doko would be the best, he is unfortunately always rather busy
[15:47] <norsetto> devfil_: nope, we have to solve it in wxwidgets, 2.8 included
[15:48] <devfil_> norsetto: in 2.8 the bug is fixed, I've fixed it time ago
[15:48] <norsetto> devfil_: yes, but its not fixed correctly (IMO)
[15:49] <devfil_> norsetto: why?
[15:49] <norsetto> devfil_: because of what I said already, that we are breaking the alternative system, the correct way is to change the hardcoded path in a pycentral compatible way
[15:51] <devfil_> norsetto: in 2.8 symlinks were the problem (as I remember right), there were no changes to other things
[15:52] <norsetto> devfil_: the way this package was made, was relying on pycentral installing things in certain places. pycentral changed those places, so we just have to follow suit
[15:53] <norsetto> devfil_: just find out where pycentral installs the pth files, and use that; to my knowledge it should be /usr/share/pyshared now
[15:55] <devfil_> norsetto: yes, it is
[15:56] <norsetto> devfil_: ok, lets try to modify the symlinks linking from /usr/lib/python2.[4,5]/site-packages/wx.pth so that they point there now and see if that works
[15:57] <norsetto> devfil_: you might jave to revert other changes you may have done to that rules though
[16:13] <amikrop> Hello. Can anybody suggest my a Python package that uses distutils and cdbs, and another which uses distutils and debhelper, to study?
[16:32] <amikrop> So, any python packages that use distutils and cdbs, or distutils and debhelper?
[16:40] <soren> amikrop: Plenty.
[16:42] <amikrop> soren: could you refer the names of some? :)
[16:42] <soren> amikrop: virt-manager
[16:43] <soren> amikrop: storm.
[16:43] <amikrop> soren: thank you
[16:43] <soren> amikrop: vm-builder
[16:43] <amikrop> soren: ok, thanks. but how could I search on my own for such packages?
[16:44] <soren> amikrop: Look through the Sources file in the archive for stuff that depends on cdbs and looks pythony.
[16:46] <amikrop> soren: aha :-)
[17:06] <ScottK> amikrop: stepic is a distutils/debhelper package and pyspf is a distutils/cdbs one that I've packaged.
[17:20] <norsetto> james_w: yes, its amd64
[17:20] <bddebian> Heya gang
[17:20] <norsetto> Heya bddebian
[17:21] <bddebian> Hi norsetto
[17:21]  * norsetto go have a snack
[17:22] <james_w> norsetto: thanks
[17:30] <norsetto> james_w: how can I make the url of a file which is hosted on bzr? Say, I have a branch called lp:~norsetto/+junk/main and there is a file foo in there
[17:32] <james_w> norsetto: I think there is a bug open saying you can't use lp: syntax to point to files within a branch. You have to expand the lp: bit first, and then add the file on to the end
[17:32] <james_w> norsetto: or are you interested in getting the loggerhead (web viewer) url of the file?
[17:33] <norsetto> like https://code.edge.launchpad.net/~norsetto/+junk/main/foo ? no, no, the loggerhead I see, its the real file I need
[17:34] <iulian> Hi
[18:12] <slytherin> superm1: there?
[18:13] <slytherin> persia: superm1: I just upgraded the bluez packages. But it seems service not started after the upgrade. Any idea where I can look for errors?
[18:13] <slytherin> The reason I think service is not started is because the applet didn't reappear in panel.
[18:44]  * ethana2 is inquiring on the status of GIMP 2.6 in backport repositories for ubuntu 8.04.1
[18:47] <ScottK> ethana2: It needs to get into Intrepid first.
[18:49] <slytherin> ethana2: GIMP is in main. you should probably be asking on #ubuntu-devel and you are unlikely to get an answer there as most of them are busy with intrepid beta preparation. :-)
[18:50] <jdong> yeah it's a bit too late.
[18:51] <slytherin> If I need to fix two packages to fix a bug, one of the packages in universe and other in main, should I do that through single bug?
[18:51] <slytherin> I mean single bug on launchpad?
[19:01] <nxvl> DktrKranz: you look like you want to give me the 2nd ACK on Bug #274173
[19:02] <Nafallo> Terminator!
[19:02]  * Nafallo looks for Ng
[19:03] <nxvl> Nafallo: :D
[19:12] <DktrKranz> nxvl, done ;)
[19:29] <ethana2> Oh yeah, quick note--  Inkscape isn't in main, but GIMP is?
[19:30] <ethana2> GIMP is on it's way to being more powerful than photoshop
[19:30] <ethana2> it's not exactly a toy anymore
[19:30] <ethana2> ....never underestimate the value of toys.
[19:30]  * ethana2 out
[19:30] <slytherin> ethana2: inkscape is in main
[19:37] <nxvl> DktrKranz: \o/
[19:37] <k0p> hi all
[19:37] <k0p> james_w, are you there?
[19:38]  * nxvl HUGS DktrKranz 
[19:40] <DktrKranz> yay! my yarssr is back! \o/
[19:46] <superm1> slytherin, you have to reboot, or restart bluetooth-applet manually
[19:47] <slytherin> superm1: I did. Nothing works for me, even pairing doesn't work. Can't figure out what is wrong.
[19:48] <k0p> hi DktrKranz :)
[19:48] <nxvl> nixternal: you are planning to attend to UDS/FossCamp?
[19:48] <DktrKranz> heya k0p
[19:48] <superm1> slytherin, check if bluetoothd is running
[19:49] <superm1> slytherin, and what upgrade process did you come from/to ?
[19:49] <slytherin> superm1: I upgraded from intrepid. bluetoothd is running.
[19:49] <superm1> is bluetooth-applet running?
[19:49]  * nxvl waves on huats 
[19:50] <huats> :)
[19:50] <superm1> slytherin, if it is running, try this.  stop the bluetooth service (/etc/init.d/bluetooth stop), and then start bluetoothd like this: sudo bluetoothd -nd
[19:50] <superm1> see that it registers the devices right
[19:51] <superm1> i just tested off an intrepid daily in live mode by adding the ppa a few hours ago with no issues...
[19:51] <slytherin> superm1: I know. It is working for everyone except for me. I am now trying what you told me
[19:52] <slytherin> superm1: http://paste.ubuntu.com/52940/
[19:54] <superm1> slytherin, hum looks clean..
[19:54] <superm1> slytherin, okay with that in one terminal
[19:54] <superm1> slytherin, run bluetooth-applet under gdb
[19:55] <superm1> https://wiki.ubuntu.com/Backtrace
[19:55] <superm1> follow that for running it under gdb
[19:55] <superm1> make sure to kill any other running instances of it
[19:56] <nixternal> nxvl: yes, I should be at both
[19:56] <nxvl> nixternal: so i will finally meet you!
[19:56] <superm1> nixternal, really?
[19:56] <nixternal> you act like that is a good thing... superm1 knows me, he will tell you meeting me is the worst thing one could ever do :)
[19:57] <nixternal> superm1: yes really...you going?
[19:57] <superm1> nixternal, not sure yet
[19:57] <superm1> i'm hoping so
[19:57] <superm1> at least for UDS
[19:57] <nixternal> I am going to FOSSCamp for KDE and Cleversafe, and going to UDS to start whipping people into shape
[19:57] <slytherin> superm1: I haven't seen any crash. It is just that nothing works.
[19:57] <nxvl> nixternal: nah! i meet persia and suvived :D
[19:57] <nixternal> pressing for a REAL APPLIANCE DISTRO!!
[19:57]  * nxvl HUGS persia 
[19:57] <nixternal> ya, I would be scared crapless to meet persia, he scares the hell out of me online
[19:57] <nixternal> ;)
[19:57] <superm1> i still think it was hilarious when we met persia and had no idea it was him for a bit
[19:58] <superm1> slytherin, that's really awfully odd
[19:58] <superm1> slytherin, this coming from a device that was working before i take it?
[19:58] <superm1> slytherin, what if you try to do a reset with hcitool?
[19:59] <slytherin> superm1: at least some part working.
[19:59] <nxvl> superm1: i was waiting for a japaneese looking guy, then saw him in the "internal" irc channel, ask him if he was already at the hotel, and then a guy come to my side and said "yes"
[20:00] <slytherin> superm1: here is log when initiating pairing from PC - http://paste.ubuntu.com/52942/
[20:01] <slytherin> damn, netsplit again
[20:11] <slytherin> superm1: pairing initiated from phone worked and device is bonded. But I can not send files in any direction. Even obex browsing from nautilus doesn't work. Meanwhile I saw this error in gdb session - g_object_unref: assertion `G_IS_OBJECT (object)' failed.
[20:29] <slytherin> RAOF: are you there? You offered to help test dvd playback fixes.
[20:54] <superm1> slytherin, well seeing a few of those in the gdb session isn't detrimental
[20:54] <superm1> slytherin, are you only experimenting with the phone?
[20:55] <superm1> slytherin, or input devices too?
[22:02] <goshawk> if someone has free time
[22:02] <goshawk> can he review http://revu.ubuntuwire.com/details.py?package=dsss ?
[23:08] <superm1> ScottK, do you have bluetooth devices in any of your machines?  slytherin had brought up a point related to bug 274950 that we should have some KDE folk weigh in, and nixternal recommended asking you
[23:14] <nixternal> superm1: you could also ask sispoty if he was around :)
[23:15] <nixternal> I have a few pints calling me from the Elephant and Castle pub on Lake and Wabash
[23:15] <superm1> i suppose I could also pass a testing request to ubuntu-devel
[23:48] <ogra> superm1, i have a GPS reciever, a heaset and will get a freedom keyboard tomorros and was planning to do some BT tesing after beta
[23:48] <ogra> (since i'm intrested in working BT for the ubuntu-mobile image)
[23:49] <superm1> ogra, well please do use that PPA for now then, the intent is to bring all that in after beta provided no big regressions are seen
[23:49] <ogra> i will
[23:49] <superm1> ogra, the gnome stack appears to be in good shape
[23:49] <ogra> but not today anymore (1am here)
[23:50] <superm1> ogra, as for your headset, after you pair, you won't see a proper ALSA "card", but rather another "device"
[23:50] <ogra> well, the current setup sucks
[23:50] <ogra> even my n800 works better
[23:50] <superm1> so it won't show up in apps that show cards
[23:50] <superm1> but for example aplay can use aplay -D headset FILE
[23:50] <superm1> or mplayer has -ao=device=headset
[23:50] <superm1> or similar
[23:50] <ogra> well, i would be happy to see *any* dveice at al
[23:50] <ogra> l
[23:50] <superm1> :)
[23:51] <ogra> i cant even pair with anything with the current BT in intrepid