[01:07] <Eickmeyer[m]> OvenWerks: How's things?
[01:10] <OvenWerks> just got my son home from surgery
[01:10] <Eickmeyer[m]> Oh, how is he?
[01:11] <OvenWerks> I think my wife is in the philppines but have not heard from her yet :)
[01:11] <OvenWerks> he is ok, groggy of course
[01:11] <Eickmeyer[m]> Of course.
[01:13] <Eickmeyer[m]> Wanted to touch base about -controls. Where are we at with that?
[01:14] <OvenWerks> GUI looks good, I think, it is just a matter of setting variables in the config and using that to test if the device is there and set it...
[01:15] <OvenWerks> The getting my wife ready to leave has left me pretty worn out.
[01:16] <OvenWerks> emotionally if not anythingn else. But at least I am getting more sleep
[01:16] <Eickmeyer[m]> I totally get that. Just to let you know, since the tablet support is a new feature, the deadline is in one week. I do, however, understand family is first, and taking care of yourself as well.
[01:17] <OvenWerks> I know, I am hoping to get back to it before then.
[01:17] <Eickmeyer[m]> Cool.
[01:17] <Eickmeyer[m]> But, do take care of yourself and your family.
[01:17] <OvenWerks>  It will not be "complete" but what it shows should work.
[01:18] <Eickmeyer[m]> Right. I think if we at least get the "feature" in and then work the bugs out before beta freeze, I think we'll be in good shape.
[01:19] <OvenWerks> ya
[17:15] <Eickmeyer[m]> If anyone wants to check out the entries in the wallpaper contest: https://imgur.com/t/ubustucontest2020 (the ones in portrait orientation are already disqualified). @azbulutlu
[18:39] <Eickmeyer[m]> @azbulutlu: It appears as though there's some activity involving MyPaint in Debian, but they have yet to release 2.0 into Debian. Considering feature freeze/debian import freeze is in less than a week, I doubt it will make it in time. It uses libmypaint1.5 as opposed to 2.0 that gimp uses, so it'll be coinstallable. We might be able to backport it.
 Eickmeyer: with reasoning you might be able to get it in after FF
 import freeze shuts off the autosync
 but that's a release team decision not mine :P
 @teward001 [Eickmeyer: with reasoning you might be able to get it in after FF], That all depends on how quickly Debian gets it done.
 true
 though... we could diverge and JFDI
 which is how nginx came to be permanently deltaed in Server
 merging later will be a pain but
 I thought about it, but we haven't carried MyPaint in Studio since before 18.10 due to the confilct with gimp. MyPaint 2.0 removes that conflict, but I'm not 100% interested in it since we carry Krita.
 👍


[14:06] <curb320> Hi ?
[14:58] <saml> hey, what's the command that locks screen?
[14:59] <saml> when i close laptop lid and open again, it gives me login prompt. I want to know which command is giving me that login prompt so i can set up keyboard binding.
[15:28] <saml> lxsession-default lock   ;  and it's already set to C-A-l
[17:39] <lynorian> saml, you may want to look at default apps for lxsession and see what command that is set to
[17:39] <lynorian> or see what happens running lxsession-defualt lock in a terminal
[18:04] <swift110> why when i try to go to an internet site it wont work
[18:14] <wxl> swift110: all sites do not work? a particular protocol? can you ping google? are you sure you have an ip address? check your router, your internet provider, etc. tl;dr, it's unlikely to be lubuntu, unless you're setting up the machine for the first time. if you're using wireless and you have a broadcom card, that could explain that problem. if you've done all the above and can't find any clues, more details
[18:14] <wxl> are required on what version you're using, what card you have, what site you're trying to connect to, etc. etc. etc. etc.
[19:18] <taza> So, I want to install an okay Lubuntu desktop on a system with less than 4gb of available hard drive space.
[19:19] <taza> Grab the alternate install iso I presume, then boot off it. Anything special I need to do to grab it? lubuntu-core looks okay.
[19:19] <wxl> taza: then i would suggest installing with the netboot iso and installing lubuntu-core. adding only the items from -desktop that you need.
[19:20] <taza> Can I install lubuntu-core off -alternative or -desktop?
[19:20] <wxl> taza: nope. you'll get lubuntu-desktop only
[19:20] <wxl> taza: the key is that the netboot iso (aka mini iso) has taskel on it.
[19:22] <taza> Well off I go
[19:22] <taza> I mean I could probably install anything
[19:22] <wxl> yeah but with limited space, it might be good to start small and work from there
[19:22] <taza> It's an old Eee PC 701 4G, and I need to modify it into a system that can run a few command-line tools
[19:22] <wxl> oh jeez if you only need CLI you don't even need lubuntu
[19:23] <wxl> you could do it with ubuntu-core
[19:23] <taza> I'd rather have GUI just for easy Chrome use
[19:23] <wxl> ah there you go
[19:23] <wxl> so lubuntu-core + chrome and you're probably good to go
[19:24] <taza> Yerp.
[19:25] <taza> Possibly VLC. It does need to play mpeg4 files enough to verify they're functional...
[19:25] <wxl> you might be able to do with with ffmpeg
[19:25] <taza> ... I got reaaal bored of using the internal filesystem tools for managing a recording device, but I don't want to sacrifice a good system to be on location, so I dug up a 701.
[19:27] <taza> All I really need are fdisk and a way to manipulate fat32 drives over usb. The chrome and the vlc are convenience.
[19:33] <taza> Does lubuntu-core come with a tool to manage wireless networks?
[19:35] <taza> Hah, this reminds me of the days I ran Linux on a Pentium 90
[19:36] <taza> Debian with IceWM, I think
[21:37] <taza> Ah, yes. Having a system that has a 4gb integrated chip for a SSD, and upgrading it to 2gb RAM makes the installer completely confused about what the sane thing is
[21:45] <taza> It had 512mb originally, but the memory was cheap
[23:29] <taza> Uh. The lubuntu-core package doesn't come with a terminal?
[23:30] <Unit193> taza: I would *highly* recommend against just installing the meta, and instead go for the task or else you'll get unexpected results in the form of odd packages installed, and certain ones missed.
[23:30] <taza> Ahh. Through tasksel that is?
[23:30] <taza> That'd be helpful if it was in the wiki.
[23:31] <Unit193> apt-get install lubuntu-core^
[23:31] <taza> ... what?
[23:31] <Unit193> That's all you have to do, that'll install the task.
[23:32] <taza> I'm not going to install things unless I understand what they do.
[23:32] <taza> What does the ^ do and is it the same as tasksel?
[23:32] <taza> And uh, why isn't this on the wiki?
[23:32] <Unit193> Sure.  That would be the same as tasksel, yes, just without needing to install tasksel.
[23:33] <Unit193> Either way.  You can check it out with -s (simulate.)
[23:34] <taza> Except I installed lubuntu-core as the wiki says, and now tasksel says that's already selected
[23:35] <taza> Your advice goes against the wiki's advice, and doesn't seem to do anything. Are you sure you're thinking of the right thing here?
[23:36] <Unit193> Doesn't exactly "go against" it, but yes I am quite certain of what I'm talking about.
[23:36] <Unit193> Though, you could just install lxterminal.
[23:36] <taza> Then why are you giving advice that neither works nor is on the wiki?
[23:37] <Unit193> How is it not working?
[23:37] <Unit193> And you could ignore the task and just install a terminal such as lxterminal.
[23:37] <taza> I already told you.
[23:38] <taza> [02:34] <taza> Except I installed lubuntu-core as the wiki says, and now tasksel says that's already selected
[23:38] <taza> So you're giving advice that doesn't work, contradicting available documentation AND you're not reading what I say in response.
[23:38] <taza> ... that makes me kind of wary to follow any advice you give without verifying it with other sources.
[23:40] <Unit193> Right, I did say to try  apt-get install -s lubuntu-core^  I haven't heavily used tasksel and that's not what I recommended...  Again, it's not contridicting documentation, it's an alternate (and perhaps better) method.  I believe the documentation does say to use tasksel, which this equates to.  I did read it, that's not telling me very much.  And as I recommended, use -s to simulate it rather than just
[23:40] <Unit193> running it (see in --help and the manpage that's what that switch does..)
[23:40] <taza> [02:32] <Unit193> Sure.  That would be the same as tasksel, yes, just without needing to install tasksel.
[23:40] <taza> And now you're openly saying you didn't say what you said.
[23:40] <Unit193> My goodness man...
[23:41] <taza> You seem confused. Maybe you should spend more time learning how things work before trying to help people? Because I cannot say I know any more than I did before you replied.
[23:41] <taza> I still don't know how the task and the package differ, for example.
[23:41] <Unit193> OK, so install from the mini, use tasksel to install lubuntu-core.  Then install from the mini again and do what I said.  Compare the package lists, if there's something different then there...
[23:41] <taza> Is there?
[23:41] <taza> Shouldn't you know this before telling me to do something?
[23:42] <Unit193> There is functionally nothing different in that case, as I said "That would be the same as tasksel"...  Anywho, if you don't want to take my advice or would rather poke holes, I have no interest.
[23:43] <taza> The problem is I have no idea how your advice is different from what I already did.
[23:43] <taza> And you're contradicting the documentation, and yourself. And now you're getting defensive about it.
[23:44] <taza> It doesn't feel like a genuine attempt to help me at all.
[23:44] <taza> So, I've asked this twice, and I'll ask it again: What's different between the package and the task?
[23:45] <taza> And the latest tasksel documentation directly contradicts you.
[23:46] <taza> https://help.ubuntu.com/community/Tasksel
[23:46] <taza> Unit193 ^
[23:46] <taza> Seems like you're wrong and this was a waste of time for us both.
[23:48] <krytarik> taza: If you really want help, try not to troll people as much.
[23:48] <Unit193> taza: Hardly, https://help.ubuntu.com/community/Tasksel#Usage_.28alternative.29 is exactly what I was saying.  Though I do agree with your last assessment
[23:48] <taza> krytarik: I'm not trolling
[23:48] <Unit193> Anyway, have a good day sir.
[23:48] <taza> krytarik: The help page clearly states the ^ is not needed
[23:49] <taza> krytarik: "Note: The caret (^) was generally required at the end of the command in older versions of tasksel. It is not required in newer versions of tasksel."
[23:49] <krytarik> taza: Ever considered that the wiki might be incomplete or even wrong?
[23:49] <taza> Yeah, which is why I asked for the difference
[23:49] <taza> Which wasn't provided.
[23:49] <taza> If there's a difference, I expect for someone who gives me advice to do things to tell me what it is
[23:50] <taza> krytarik: I'm not trolling, I just expect to know what I'm doing in addition to being told to do something - I have no idea if they're wrong or right, and in this case, for example, the person giving me advice was wrong.
[23:51] <krytarik> The latter is just *your* conclusion.
[23:52] <taza> He contradicts multiple portions of the Wiki, and suggested a course of action that didn't work.
[23:52] <taza> There isn't space for multiple conclusions on this one. He was wrong.
[23:52] <wxl> I'm pretty sure we don't need to discuss this issue any further.
[23:52] <wxl> Is there anything else you need help with, taza?
[23:53] <taza> wxl: Possibly shortly, I'm still getting my bearings


[05:02] <lotuspsychje> good morning
[11:49] <marcoagpinto> heya
[21:21] <leftyfb> oerheks: quick, if you close your IRC client REAL quick nobody will see the password you already posted!
[21:21] <oerheks> oh, sorry for my noise 🤣


[00:02]  * sistpoty goes to bed... gn8
[00:13] <wgrant> \sh: You *really* want to wait a couple of months for Leonov. There will be a complete Python API for Launchpad then.
[00:17] <txwikinger> Is there a way to see in apt-cache policy which repo the package is found?
[00:17]  * ScottK has heard that before.
[00:18] <directhex> txwikinger, is this a trick question?
[00:18] <txwikinger> No
[00:18] <ScottK> apt-cache policy $PACKAGE |grep archive
[00:18] <directhex> that's exactly what apt-cache policy tells you
[00:19] <txwikinger> I get something like "500 http://ppa.launchpad.net hardy/main Packages"
[00:19] <txwikinger> I can have more than one ppa
[00:19] <directhex> cross-reference it against apt-cache show
[00:21] <directhex> apt-cache show mono-gac | grep $(apt-cache policy mono-gac | grep -B1 Packages | head -1 | cut -d' ' -f3) | grep Filename
[00:24] <wgrant> ScottK: It's actually happening now, though. Rather surprising, I know.
[00:54] <RAOF> ls
[00:54] <lifeless> -r--r--r-- 1 lifeless lifeless 1G
[00:54] <RAOF> Gah.
[01:03] <RAOF> Yay!  Matthew Garrett's working on suspend for nouveau.
[01:07] <wgrant> RAOF: Nice!
[01:07]  * wgrant is currently doing something very stupid - building mesa, drm, Xorg from Git to try to get DRI2 working.
[01:08] <RAOF> Don't you have an nvidia card?
[01:08]  * RAOF may be thinking of someone else.
[01:08] <wgrant> At work, yes.
[01:08] <wgrant> But my laptop is i915.
[01:09] <RAOF> But not on the system where you're trying to get dri2 working, obviously :)
[01:18] <emgent> uhm..
[01:18] <emgent> http://packages.ubuntu.com/intrepid/libaprutil1-dev
[01:18] <emgent> libdb4.6-dev Package not available
[01:18] <emgent> someone know why ?
[01:19] <emgent> package removed, or ubuntu archivies problem ? (intrepid)
[01:20] <wgrant> #  Deleted  15 hours ago  by Martin Pitt  (NBS)
[01:20] <wgrant> Ah.
[01:20] <wgrant> The new db4.6 is in binary NEW.
[01:20] <wgrant> So it will be back soon enough.
[01:21] <emgent> ok, i should fix apache2
[01:21] <wgrant> emgent: Why?
[01:22] <emgent> there is a security problem (patched) but dont build beacuse apache2 depends to libaprutil1-dev and it depends to libdb4.6-dev
[01:23] <wgrant> It's Intrepid. It can wait a couple of days.
[01:23] <emgent> sure i will do
[01:23] <emgent> i go to fix <= intrepid
[01:23] <emgent> s/=/ /
[01:24] <persia> freeflying: Feel free to take FBreader if you like: I have no explicit attachment, and am still tracking hardy.  I'll likely chase some SRU stuff before catching up on my merges, so help is welcome.
[01:26] <Laney> wgrant: Where did you get the information about the deleted package from?
[01:28] <wgrant> Laney: https://launchpad.net/ubuntu/intrepid/i386/libdb4.6-dev
[01:29] <Laney> wgrant: Ah right, I didn't know it showed that. Thanks
[01:29] <foxbuntu> could someone sync the keyring for me so I can upload my package for revu? (Thanks!)
[01:29] <wgrant> foxbuntu: Sure.
[01:30] <foxbuntu> thanks wgrant !
[01:31] <wgrant> foxbuntu: It will take several minutes - I'll tell you when it's done.
[01:31] <foxbuntu> wgrant, no problem...thanks
[01:37] <wgrant> foxbuntu: It just finished.
[01:37] <foxbuntu> wgrant, great...thanks again...time to get this uploaded :)
[01:41] <foxbuntu> wgrant, I had already tried the upload the package before and my key wasnt in there do I need to re-upload?
[01:41] <wgrant> foxbuntu: mythbuntu-apple-trailers?
[01:41] <foxbuntu> yes
[01:42] <foxbuntu> so obviously not ;)
[01:42] <wgrant> foxbuntu: No, I'll poke it through now.
[01:42] <foxbuntu> wgrant, thanks
[01:42] <wgrant> Accepting upload mythbuntu-apple-trailers from Nick Fox<EMAIL_ADDRESS>[01:42] <wgrant> It worked.
[01:43] <foxbuntu> cool...I see it now on the revu site
[01:43] <foxbuntu> thanks again for the help
[02:37] <superm1> leleobhz, i left you some feedback on revu
[02:41] <emgent> hi mario! :)
[02:41] <crimsun> ugh, new hal-info regression :/
[02:41] <emgent> hardy?
[02:42] <crimsun> hardy-proposed, yes.
[02:42] <superm1> hi emgent
[02:42] <emgent> crimsun: argh
[02:43] <superm1> regression?  you mean it's a new feature.  the behavior was wrong before right ;)
[02:43] <crimsun> well, in the haste to fix additional HPs, several HPs were broken
[02:51] <wgrant> crimsun: Didn't it get an exemption from hardy-proposed?
[02:52] <crimsun> wgrant: I think, but 20080508+git20080601-0ubuntu0.8.04 in this intsall seems to be from hardy-proposed.
[02:59] <emgent> wgrant: can you open tasks nominated in Bug #239894 ?
[03:01] <SpookyET> hi
[03:01] <SpookyET> I'm having some deb creation problem.
[03:02] <SpookyET> debian/foo/usr/bin is empty. debian/tmp/usr/bin is not
[03:06] <wgrant> emgent: No - I'm not a core-dev.
[03:14] <emgent> oh ok, np
[03:15] <emgent> I thought that the motu could also manage the tasks of the packages in main
[03:32] <emgent> I go to sleep
[03:32] <emgent> night people
[03:38] <lifeless> night
[03:47] <foxbuntu> wgrant, would you mind checking to see if my updated package was accepted?
[04:56] <superm1> foxbuntu, it's automatic
[04:57] <superm1> the cron job runs every 10 or 15 minutes or so
[04:57] <superm1> to update the package lists on revu
[05:04] <SpookyET> debian/foo/usr/bin is empty. debian/tmp/usr/bin is not
[05:04] <SpookyET> I'm having some deb creation problem.
[07:04] <\sh> good morning
[08:29] <geser> good morning
[08:29] <geser> hi \sh
[08:29] <\sh> moins geser
[10:18] <i4x> hugs 4 everyone!!
[11:03] <Kopfgeldjaeger> could somebody have a look at my debdiff in bug #227323?
[11:06] <emgent> geser: thank you for libdb4.6-dev
[11:13] <geser> Kopfgeldjaeger: if changing the Maintainer field is the only change left, then it's a sync and not a merge
[11:34] <Kopfgeldjaeger> geser: OK, I said I was unsure about that in the comment of my first Debdiff. Should i write "Sync blabla", or can this package then be synced automatically?
[11:47] <Hobbsee> ScottK: re bugs used for multiple packages, for transitions, the problem is not only just the bugmail - it's that LP falls over trying to open them most of the time.
[11:47] <Hobbsee> ScottK: so if you do want it that way, you'll need to solve both problems.
[11:50] <Hobbsee> ScottK: (you must have missed my original mail on it at the time, when it was being discussed on the ML)
[11:56] <DRebellion> Hmm... need some text-encoding advice: If a company that needs to be named in debian/copyright has a special character in its name "Mjølner Informatics", should I include that character (and thus turn the file into UTF-8 Unicode)? Or should I represent it in some other way?
[11:57] <james_w> DRebellion: the file should be UTF-8 anyway
[11:57] <james_w> s/ anyway//
[11:58] <DRebellion> james_w, it should be utf-8 or ascii to start with? I should include the character to make it utf-8?
[11:58] <james_w> if you include a non-ascii character then you should ensure your encoding is utf-8
[11:58] <DRebellion> ok
[11:59] <DRebellion> just wanted to make sure non-ascii was allowed
[14:12] <Kopfgeldjaeger> hmpf... Nathan Handler already has uploaded debdiffs for all merges I'd like to do :O
[14:18] <SpookyET> Hi. I have trouble with a deb. debian/package/usr/bin is empty. debian/tmp/usr/bin is not. I don't understand why it's not moving the files.
[14:22] <DRebellion> SpookyET, perhaps elaborate or provide more detail about the problem? It seems a bit vague at the moment.
[14:23] <SpookyET> DRebellion: The packaging is missing all files from /usr/bin
[14:24] <DRebellion> SpookyET, does the install script (try to) put files there?
[14:24] <SpookyET> But, make install is working properly. I see them in ./debian/tmp/usr/bin
[14:25] <DRebellion> make install puts them in /tmp/usr/bin?
[14:25] <DRebellion> oh right
[14:25] <SpookyET> I'm using CDBS
[14:25] <DRebellion> sorry, can't help you with cdbs
[14:27] <SpookyET> Why don't you use it
[14:28] <DRebellion> SpookyET, just never tried it
[14:28] <leleobhz> what can i do if i cant remove a file?
[14:28] <leleobhz> i explain
[14:28] <DRebellion> SpookyET, guess that's not a very good reason :P
[14:28] <leleobhz> W: handbrake source: patch-system-but-direct-changes-in-diff libhb/.depend
[14:29] <leleobhz> any target removes this file before the make and after the package creation
[14:30] <Kopfgeldjaeger> geser: ping
[14:30] <leleobhz> SpookyET: what is with cdbs?
[14:31] <SpookyET> leleobhz: scroll up
[14:31] <leleobhz> [14/06-10:18:24] < SpookyET> Hi. I have trouble with a deb. debian/package/usr/bin is empty. debian/tmp/usr/bin is not. I don't understand why it's not moving the files.
[14:32] <leleobhz> SpookyET: are you using debian/files?
[14:32] <leleobhz> DRebellion: i think its isnt a cdbs issue
[14:32] <SpookyET> leleobhz: no
[14:32] <SpookyET> am i supposed to?
[14:32] <leleobhz> i remember a package ive got this problem...
[14:33] <SpookyET> everything besides /usr/bin gets populated
[14:33] <leleobhz> SpookyET: try create a debian/dirs
[14:33] <leleobhz> with
[14:33] <leleobhz> usr/bin
[14:34] <SpookyET> leleobhz: debian/usr/bin gets created
[14:34] <leleobhz> SpookyET: i know
[14:34] <leleobhz> try do this
[14:35] <SpookyET> leleobhz: dirs is there
[14:35] <leleobhz> leleobhz@zorg:~/TRABALHO/DEVELOPMENT/COMPILACOES/UBUNTU/pacotes/handbrake-intrepid/handbrake-0.9.2$ cat debian/dirs
[14:35] <SpookyET> maybe that's what creates it
[14:35] <leleobhz> usr/bin
[14:36] <leleobhz> its a file
[14:36] <Kopfgeldjaeger> OK. I have package foo with Ubuntu changes. Now a new version is in SID and needs to be merged. But there are no further Ubuntu changes needed (because their already made upstream or by debian) except adjusting the Maintainer field. What should I do with that package?
[14:36] <SpookyET> mine is a dir
[14:36] <leleobhz> SpookyET: remove it and make it as a file
[14:36] <leleobhz> touch debian/dirs
[14:36] <Kopfgeldjaeger> s/their/they're/
[14:36] <leleobhz> echo "usr/bin" > debian/dirs
[14:36] <SpookyET> leleobhz: I have it, dude
[14:37] <leleobhz> SpookyET: and even with this it dont install into usr/bin?
[14:37] <SpookyET> leleobhz: it was there before you told me. maybe, i should remove it
[14:38] <leleobhz> give a try
[14:40] <SpookyET> leleobhz: debian/usr/bin does not get created at all
[14:40] <leleobhz> SpookyET: debian/usr/bin???
[14:40] <leleobhz> debian/packagename/usr/bin
[14:41] <SpookyET> right
[14:41] <leleobhz> and may need the tricky of debian/dirs
[14:41] <SpookyET> the dirs file created the empty dir
[14:41] <leleobhz> make a list with binary dirs and put there
[14:41] <SpookyET> it's just usr/bin
[14:41] <leleobhz> mmm
[14:41] <SpookyET> but the actual files are not moved there
[14:42] <leleobhz> how is your makefile install target?
[14:42] <SpookyET> leleobhz: it works fine  debian/tmp/usr/bin is populated
[14:42] <leleobhz> (!)
[14:43] <leleobhz> what includes have in debian/rules ?
[14:43] <SpookyET> include /usr/share/cdbs/1/rules/debhelper.mk
[14:43] <SpookyET> include /usr/share/cdbs/1/class/autotools.mk
[14:43] <SpookyET> include /usr/share/cdbs/1/class/makefile.mk
[14:44] <leleobhz> hmmmm
[14:46] <SpookyET> what about debian/files?
[14:46] <SpookyET> tell me about it
[14:47] <leleobhz> SpookyET: i really dont use it
[14:47] <leleobhz> SpookyET: but have this inside a mine
[14:48] <leleobhz> handbrake_0.9.2-0ubuntu2_i386.deb graphics extra
[14:48] <leleobhz> "debian/files" [readonly] 1L, 49C                                                               1,1           All
[14:48] <leleobhz> (last is vi comment line. not inside the file)
[14:49] <SpookyET> looks worthless
[14:49] <man-di> SpookyET: its a generated file, dont touch it on your own
[14:49] <leleobhz> :]
[14:54] <leleobhz> SpookyET: ive got this problem in past, but i cant remember how ive solved it
[14:55] <SpookyET> look at the deb
[14:56] <leleobhz> i cant remember the package name ;]
[14:58] <SpookyET> leleobhz: grep for cdbs rules
[14:59] <SpookyET> you'll find it
[14:59] <leleobhz> latter thing ;]
[15:08] <SpookyET> this is annoying
[15:08] <SpookyET> i don't get it
[15:26] <tacone> hello, I am looking after https://bugs.launchpad.net/memaker/+bug/214401. I need to force the building process to using python 2.5.  Simply setting the right dependency in debian/control  doesn't work. anyone willing to help me ?
[15:27] <leleobhz> tacone: using cdbs?
[15:27] <tacone> leleobhz: I have no clue of what cdbs is, sorry :(
[15:28] <leleobhz> include /usr/share/cdbs/1/rules/debhelper.mk
[15:28] <tacone> Build-Depends: debhelper (>= 5.0.37) ?
[15:29] <leleobhz> normal package
[15:29] <leleobhz> :]
[15:29] <leleobhz> cdbs packages must have cdbs in build-deps
[15:29] <tacone> uhm
[15:29] <SpookyET> what about my usr/bin
[15:30] <leleobhz> notting from my memory
[15:30] <tacone> leleobhz: what should I do then ? note it's a python application
[15:30] <leleobhz> this problem happened with me some YEARS ago...
[15:31] <SpookyET> mind taking a look at the files?
[15:31] <Kopfgeldjaeger> I have a package that copies my (Hardy)-/usr/share/misc/config.{sub, guess) to its main folder... So the debian debdiff looks kind of strange (I'm packaging for Intrepid).. Is this OK or what should I do with it?
[15:32] <Kopfgeldjaeger> It already copies the two files when I dpkg-buildpackage -S -sa -rfakeroot
[15:35] <tacone> wow, works ?
[15:43] <whs> Hello, I'm member of ThaiLoco willing to running a PackageJam. (even with no one of us being MOTU, I hope to see one) Does the Packaging Playbook have the translatable format available?
[15:44] <zorglu_> i have an apps using libxml2. It compile and run fine on feisty. when linked in dynamic or static. But when i do it on hardy, it run well only in dynamic link but it crashes in static linking. is that something you already seen ?
[15:45] <whs> The jam is on 6 July but we have a meeting tomorrow.
[15:48] <tacone> I am looking for submitting a patch to fix a little bug. how should I change the changelog ?
[16:02] <ryanakca> How can I make knmap not run configure twice (once at start of build, and one at the end)?
[16:07] <tacone> ok, gave up :-)
[16:24] <geser> Kopfgeldjaeger: to make the debdiff easier to review I'd remove the config.* changes from the debdiff
[16:24] <Kopfgeldjaeger> Fine. If it's that easy... :)
[16:25] <Kopfgeldjaeger> and what about my earlier question? (package with no needed ubuntu changes anymore)
[16:26] <Hobbsee> Kopfgeldjaeger: file a sync request, see info in /contributing
[16:47] <Kopfgeldjaeger> pbuilder hooks don't work for me... HOOKDIR="/etc/pbuilder/hooks" and there is the file "C10shell"...
[16:57] <ScottK> Hobbsee: The LP falls over problem is supposed to be fixed in this next release.
[17:00] <Kopfgeldjaeger> Bug #239995 should be a sync request
[17:02] <ScottK> Hobbsee: I was able to open the maintainer field bug on dogfood at UDS.
[17:02] <Kopfgeldjaeger> just like Bug #227323
[17:03] <ScottK> Kopfgeldjaeger: Then fill the bug out like a sync request (explaining why any Ubuntu changes can be dropped) and subscribe UUS.
[17:03] <ScottK> Kopfgeldjaeger: Are you sure on Poker Network?
[17:03] <ScottK> It certainly wasn't in the past.  I haven't looked at it, but that would suprise me.
[17:06] <Kopfgeldjaeger> the only changes I'm not sure about were in debian/control (Depends stuff)
[17:07] <ScottK> That's the ones that are most probably needed.
[17:07] <Kopfgeldjaeger> OK. Interesting.
[17:07] <Kopfgeldjaeger> Needed for what?
[17:08] <ScottK> IIRC (and it's been a while) there are some database library naming differences between Debian and Ubuntu.
[17:08] <ScottK> You'll see that poker network ships several control files for Ubuntu versions.
[17:11] <devfil> is dad down?
[17:11] <Kopfgeldjaeger> The control file really has changed since 1.2.0. I will look up that... But anyway it builds fine with no Dep-changes
[17:13] <ScottK> Kopfgeldjaeger: Building wasn't the problem before, it was running.
[17:13] <ScottK> Speaking of which ...
[17:13]  * ScottK runs off for a while.
[17:16] <Adri2000> devfil: it is
[17:17] <devfil> Adri2000: thanks :)
[17:18] <Adri2000> devfil: the server hosting it is down, no idea what happened and when will it come back yet
[17:19] <devfil> Adri2000: I will use MoM
[18:06] <Kopfgeldjaeger2> geser: Do you think pwman3 can be synced from Debian? The "help EOF" bug and the cElementTree stuff are fixed there
[18:07] <geser> Kopfgeldjaeger: sure
[18:44] <Kopfgeldjaeger> Could somebody have a look at my debdiff in bug #239998? (I know, I'm annoying ;) )
[18:48] <rockstar> How can I take a bzr branch and add the debian/ folder (and all files)?
[20:10] <RainCT> rockstar: what do you mean?
[20:11] <leleobhz> RainCT: can you help-me with handbrake?
[20:11] <RainCT> (uhm.. nvm, I guess you've already found out what you wanted to know by now :P)
[20:11] <RainCT> leleobhz: Sure, I can try :). What's the problem?
[20:17] <bobbo> warp10: ping
[20:17] <warp10> hi bobbo!
[20:17] <bobbo> hey :D
[20:18] <bobbo> im a bit stuck with the get-orig-source directive for bug #195196, could you try and help me?
[20:19] <warp10> bobbo: I can't try, since I am not on my own box and have not the dev tool I need, but I can help you :)
[20:20] <bobbo> warp10: ok :) http://pastebin.ubuntu.com/20198/ <-- That has the description of my problem
[20:23]  * warp10 looks
[20:26] <warp10> bobbo: looks like your problem is just renaming the directory, isn't it?
[20:26] <bobbo> warp10: yes, i know i can extract it, then just mv the directory but i cant work out a way to get the version number for the mv destination
[20:32] <warp10> bobbo: I can only find rather complex and unusal ways to achieve such a task.
[20:32] <warp10> Any other MOTU has a good idea or knows an easy way to do that?
[20:33] <devfil> bobbo: in rules you should put VERSION = <packageversion>
[20:33] <devfil> I think this is the only think you can do
[20:34] <bobbo> devfil: ok, will do, thanks alot
[20:34] <devfil> bobbo: np ;)
[20:35] <warp10> bobbo: BTW, you could ask the upstream developer to package the tarball so that it extracts in a more standardized way. Maybe he will listen to you :)
[20:35] <bobbo> warp10: yeah i was thinking about doing that at half 2 last night while trying to work out how to fix that ;)
[20:36] <warp10> bobbo: I had a similar bad adventure for my first packaging task. I have been lucky with my upstream, hope you are too!
[20:37] <bobbo> warp10: hehe, not as bad as purrr upstrem who disappear right in the middle of a conversation while you are trying to get an FFe
[20:38] <warp10> bobbo: :(
[20:42] <warp10> bobbo: BTW, adding a .desktop file to your package is an important thing for that package. Did you find and icon file for that software?
[20:42] <bobbo> warp10: yeah there was an icon in the upstream tar.gz
[20:43] <warp10> bobbo: xpm?
[20:43] <bobbo> warp10: nope only a png
[20:44] <warp10> bobbo: fair enough
[21:11] <warp10> bobbo: just seen your new diff.gz: good work with the get-orig-source, a little unusual, but it should be fine. If you contact upstream, please send him any modification you did that deserves to be included in future releases (like the .desktop file)
[21:11] <bobbo> warp10: thanks alot, ok will do :)
[21:32] <sistpoty> hi folks
[21:43] <sebner> huhu sistpoty
[21:44] <sistpoty> hi sebner:
[21:47] <norsetto> hello
[21:49] <sebner> huhu norsetto =)
[21:49] <norsetto> hi sebner
[21:50] <sebner> norsetto: some hours ago I would have needed your italian power :P
[21:50] <norsetto> sebner: you mean you had the italian exam already?
[21:51] <sebner> norsetto: no. monday in one week. I had to work on an italian text ^
[21:51] <tacone> sebner: italian is so easy :)
[21:52] <sebner> rofl
[21:52]  * sebner doesn't think so
[21:52] <sebner> or sebner just suck
[21:52]  * tacone thinks so
[21:52] <norsetto> sebner: ask tacone if he speaks italian, most probably he speaks a strange dialect that only he and his relatives understand
[21:53] <devfil_> sebner: there are a lot of italians in this chan, if you need ask :)
[21:54] <sebner> norsetto: rofl, and what help is he then for me? ^
[21:54] <sebner> devfil_: thx for the offer but not needed anymore ;)
[21:57] <tacone> norsetto: I miei genitori erano professori d'italiano entrambi. per quanto ignorante io possa essere qualcosa d'italiano lo parlo.
[21:57] <sebner> devfil_: thx for the offer but not needed anymore ;) ^
[21:58] <sebner> ah
[21:58] <sebner> xD
[21:58] <devfil> sebner: I've read :)
[21:58] <devfil> ed
[21:58] <sebner> tacone: uhh I can understand it somehow xD
[21:58] <tacone> sebner: nice sign ;-)
[21:58] <sebner> devfil: read ;)
[21:59] <sebner> tacone: hmm?
[21:59] <devfil> tacone: professori di italiano? sono spaventato...
[21:59] <tacone> sebner: my english is worse than my italian
[21:59] <norsetto> tacone: per con la lettera Maiuscola ;-)
[21:59] <tacone> devfil: norsetto: menosi ! :-D
[21:59] <sebner> tacone: np
[21:59] <sebner> ahhh
[22:00] <sebner> too many italian people
[22:00]  * sebner hides
[22:00] <devfil> ahahahaha
[22:00] <devfil> lool
[22:00] <tacone> sebner: best way to learn italian is come to italy, and party with italians :-)
[22:00] <slangasek> tacone: "#fanculo", eh?
[22:00] <sebner> norsetto: last time we spoke italian you stopped it because it's OT :P
[22:00] <tacone> slangasek: fanculo is an important opensource project. cough cough
[22:00] <devfil> sebner: party based on pizza and beer :)
[22:01] <sebner> tacone: I don't want to learn it ^
[22:01] <slangasek> tacone: heh
[22:01] <sebner> devfil: lol, is there also one named "Figlio di una buttana" ? ^
[22:01] <devfil> sebner: not buttana, but puttana :)
[22:01] <tacone> sebner: when you get to know an nice looking foreign girl.. you usually *want* to learn her mother language
[22:02] <sebner> tacone: rofl
[22:02] <sebner> devfil: ah, thx
[22:02] <norsetto> sebner: your version is actually ok in sicily (just change figlio with figghio)
[22:03] <devfil> norsetto: lol
[22:03] <sebner> hmm my italdict can't find that word
[22:03] <sebner> ^
[22:03] <devfil> sebner: and change una with na
[22:03] <tacone> norsetto: btw, I wrote you sometime ago about getting a mentor. then it seemed I need more practice before getting one. but I don't know how to practice without one.
[22:03] <sebner> some form of figlio I suppose
[22:04] <tacone> sebner: right.
[22:04] <devfil> sebner: dialect form
[22:04] <sebner> wäh
[22:04] <sebner> I don't even can speak normal italian
[22:04] <sebner> and then you come with dialect xD
[22:04] <norsetto> tacone: you hadn't had the chance to work on any bug?
[22:05] <tacone> norsetto: I tried today, but stalled about changelogs and proper reporting
[22:05] <norsetto> tacone: ok, what was the problem?
[22:05] <sebner> norsetto: is it è or é ?
[22:06] <norsetto> sebner: depends if its an open or closed vowel
[22:06]  * slangasek grins
[22:06] <sebner> norsetto: hmm? he,she,it is
[22:06] <tacone> norsetto: https://bugs.launchpad.net/ubuntu/+source/memaker/+bug/214401
[22:07] <tacone> norsetto: I didn't know how to properly modify changelog and version
[22:07] <slangasek> sebner: è
[22:07] <norsetto> tacone: ok, let me check what you did
[22:07] <tacone> norsetto: btw, afterwards, looking to other memaker related bugs, I guess my patch is not needed
[22:07] <devfil> sebner: he = lui, she = lei, it = lui, is = è
[22:07] <sebner> slangasek: next italian geek :P
[22:07] <tacone> norsetto: and my patch targets hardy, not intrepid :-(
[22:07] <sebner> devfil: I know ^^
[22:08] <norsetto> tacone: for the changelog you can simply use dch
[22:08] <slangasek> sebner: io sono geek di tutte le lingue :)
[22:08] <tacone> norsetto: I know, but I didn't dare to do it.
[22:08] <sebner> slangasek: give me some german :P
[22:08] <norsetto> tacone: try, whats the problem? If its wrong you repeat
[22:09] <devfil> slangasek: come fai a conoscere l'italiano?
[22:09] <tacone> I dind't know who to assign as mantainer. me ? ubuntu motus ?
[22:09] <norsetto> tacone: ubuntu motu, you can use update-maintainer
[22:09] <slangasek> sebner: warum? :P
[22:09] <tacone> norsetto: i don't have update-mantainer on my box, it seems.
[22:10] <sebner> slangasek: come on. ein bisschen mehr :P
[22:10] <norsetto> tacone: should be in ubuntu-dev-tools
[22:10] <tacone> I have it. but it's not there.
[22:11] <norsetto> tacone: you can also edit your changelog manually, just mind the spaces, tabs and the likes
[22:11] <tacone> too difficult for me. giving up, and going to get cigarettes.
[22:12] <norsetto> tacone: hmmm, that seems pretty strange to me
[22:12] <slangasek> devfil: ho studiato lingue Romance nella università, fa molti anni; la verità, c'è che non conosco l'italiano, ma conosco molto bene l'espagnolo e il portuguese ;)
[22:13] <tacone> norsetto: I guess I'll wait for someone to review my patch and tell me about it.
[22:13] <tacone> norsetto: truth is that I just can't find my way out of existing documentation
[22:13] <devfil> slangasek: they're much similar to italian ;)
[22:14] <norsetto> tacone: then please let us know where is the problem so that we can correct it
[22:14] <tacone> slangasek: some mistake, but understandable.
[22:14] <leleobhz> slangasek: ping
[22:14] <sebner> slangasek: your italian has the same level as mine xD
[22:15] <gaspa> slangasek: anyway, compliments. ;) for one that doesn't know italian, you're quite good...
[22:15] <norsetto> slangasek: better than many italians ...
[22:15] <sebner> rofl
[22:16] <tacone> norsetto: wiki it's just feels messy. I'll try again maybe. but it's like wasting a lot time to learn what you could have learn in minutes.
[22:16] <slangasek> sebner: ich benutze nicht die deutsche Sprache seit 15 Jahre, ich gebe dir nicht mehr ;)
[22:16] <slangasek> norsetto: heh... :)
[22:16] <slangasek> leleobhz: pong
[22:16] <sebner> slangasek: hrhr
[22:16]  * tacone brb in 15 minutes.
[22:16] <norsetto> tacone: you mean the packaging guide?
[22:16] <tacone> norsetto: I mean all.
[22:16] <leleobhz> slangasek: can i speak with you in pvt again?
[22:17] <tacone> going. see you later
[22:17]  * devfil doesn't know italian but he is italian, this is funny and scarer at the same time
[22:17] <devfil> :)
[22:18] <sebner> Il mio opinione é che anch' io posso parlare italiano un pochino. Ha nessuno la voglia di abbracciare sebner? ^^
[22:18] <slangasek> leleobhz: you can speak with me in private, but I'm not sure what you mean by "again"?
[22:19] <devfil> sebner: "La mia opinione" and "Nessuno ha"
[22:19] <slangasek> sebner: ti abbraccio!
[22:19] <sebner> devfil: -.-
[22:20] <sebner> slangasek: grazie =)
[22:20]  * sebner hugs slangasek
[22:21] <devfil> sebner: remember: in italian when you make a question use subject + verb
[22:21]  * norsetto gives sebner a bear hug
[22:21] <sebner> devfil: well I just need italian knowledge for the next few days. so I don't mind ;)
[22:21]  * sebner hugs bear norsetto ^=)
[22:23] <slangasek> cdbs question: what's the proper way to remove a file as part of the clean target if the upstream rules don't take care of it?
[22:24] <norsetto> slangasek: is that a quiz?
[22:24] <sebner> lol
[22:24] <slangasek> norsetto: it's a question on behalf of leleobhz; I don't use cdbs and don't know the runes :)
[22:25] <norsetto> slangasek, leleobhz: ah, I would just use a clean:: target and rm the file there
[22:25] <crimsun> right, clean::
[22:33] <sistpoty> short info: revu will be back up in a few minutes (rebooting for new kernel atm)(
[22:34] <norsetto> sistpoty: I can hardly wait
[22:34] <sistpoty> heh
[22:35]  * norsetto relax and has a thumblefull of "grappa alla liquerizia"
[22:38] <norsetto> sebner: that was an example of bad italian
[22:39] <slangasek> then I shouldn't feel bad at not understanding it? :)
[22:39] <sebner> norsetto: lol. I know what grappa is. liquerizia? liquid?
[22:39] <devfil> http://mail.google.com/mail/#inbox
[22:39] <devfil> sorry for the link
[22:39] <devfil> my error
[22:40] <norsetto> sebner: liquerizia is liquorice, but the correct italian would be liquirizia
[22:40] <sebner> ah
[22:41] <sebner> bad norsetto :P .... ok it's saturday
[22:42] <sebner> norsetto: hmm, what does the word " avvenne" means?
[22:42] <norsetto> sebner: it happened
[22:42] <sebner> thanks
[22:46] <sistpoty> revu is back :)
[22:48] <norsetto> Kopfgeldjaeger: any reason why u-u-s was not subscribed to your sync requests?
[22:49] <Kopfgeldjaeger> No.
[22:49] <Kopfgeldjaeger> Will subscribe u-u-s at once
[22:50] <norsetto> Kopfgeldjaeger: thanks, if you use requestsync there is an option you can use to do that automatically
[22:50] <Kopfgeldjaeger> I tried it
[22:51] <Kopfgeldjaeger> But when I start the script, I just see a blinking cursor (just like after "cat" in a shell)
[22:51] <Kopfgeldjaeger> (also compiled the newest version in Intrepid)
[22:51] <norsetto> Kopfgeldjaeger: have you checked if a bug was reported?
[22:51] <sebner> norsetto: If never tried that. I always sync them manually. I tried once and there was written "sending to Debian" so I exited
[22:52] <Kopfgeldjaeger> norsetto: Yeah, but I found nothing
[22:52] <Kopfgeldjaeger> It hangs when calling debian_component(somestr)
[22:53] <Kopfgeldjaeger> Maybe it's cause p.d.o is damn slow today
[22:54] <sistpoty> hm... an unstable chroot helps a lot :)
[23:03] <i4x> hi!!
[23:03] <i4x> santa
[23:04] <geser> sebner: requestsync doesn't send the sync request to Debian, only to LP
[23:04] <sebner> geser: wow, so I can improve my sync rate rapidly \o/
[23:05] <geser> sebner: hmm, better continue filing them manually :)
[23:05] <sebner> geser: lol, why?
[23:06] <geser> so the MOTUs have time to clear the u-u-s queue from you
[23:09] <sebner> geser: hmm, I'm not on the queue currently IIRC *but* wait until my exams are passed and Debian Import Freeze is starting. *hrhrhrhrhr*
[23:12] <geser> argh
[23:12]  * geser starts writing a python script to ACK sebner's sync requests
[23:13] <sebner> geser: O_o to be honest I've heard this sentence a few times from different people xD
[23:13] <RainCT> :)
[23:14] <RainCT> am I the only one here who doesn't understand Italian? :P
[23:14]  * LaserJock raises his hand
[23:14] <LaserJock> I .. uh.. know some English, that's it
[23:15] <geser> RainCT: no
[23:15] <Nafallo> sometimes I have difficulty understanding Italians even when they speak English :-)
[23:15]  * sistpoty only speaks computer languages *g*
[23:15] <RainCT> lol
[23:15] <Nafallo> but then again... that goes for all kind of people ;-)
[23:16] <geser> sistpoty: also whitespace?
[23:16] <sebner> sistpoty: brainfuck?
[23:16] <sistpoty> both still on my list (though I did have a look at bf some time ago)
[23:16] <sistpoty> list to learn even
[23:17] <LaserJock> \o/ for profiling
[23:17] <sistpoty> but I refuse to learn malbolge though *g*
[23:17] <LaserJock> I just cut down the running time a C app by 6 times
[23:17] <sistpoty> congrats LaserJock
[23:18] <LaserJock> it turns out division really is more computationally intensive :-)
[23:18] <LaserJock> more than multiplication that is
[23:19] <sistpoty> heh
[23:20] <RainCT> LaserJock: what do you do then? *0.x?
[23:21] <LaserJock> essentially yes
[23:21] <LaserJock> 1/x
[23:22] <sebner> gn8 folks :)
[23:22] <sistpoty> hm... and that brings you an optimization? or is x a constant in that regard?
[23:22] <sistpoty> gn8 sebner
[23:22] <LaserJock> so I was doing y/x but instead I redefined z = 1/x so that I can do y*z
[23:23] <sistpoty> and you had y/x repeatedly in there?
[23:23] <RainCT> clever :)
[23:23] <sistpoty> (still trying to find out why it wasn't optimized by the compiler in the first place)
[23:24] <LaserJock> well, I was doing y/x approximately 240k times
[23:24] <LaserJock> doing y/x 240k times versus y*z 240k times makes a lot of difference
[23:25] <sistpoty> hm... yes :)... though the compiler should really take care of this imo, though it's not really that trivial to optimize such a case
[23:26] <LaserJock> woot, and a -O3 shaved off another 20%
[23:26]  * LaserJock <3 C
[23:26] <leleobhz> Use of uninitialized value in pattern match (m//) at /usr/bin/dpkg-source line 429.
[23:26] <leleobhz> how can i fixit?
[23:27] <sistpoty> leleobhz: hm? what version of dpkg are you using/can you pastebin the complete output?
[23:31] <i4x> ppl, while installing a package.deb all the instructions will act with root permissions, right?
[23:31] <LaserJock> yep
[23:32] <leleobhz> sistpoty: http://paste.ubuntu.com/20224/
[23:33] <leleobhz> hmmm
[23:33] <i4x> so, I don't need to use 'sudo' before any instruction and 'mysql' will login by default as root, right?
[23:34] <sistpoty> leleobhz: line 105/108 might give you some clue
[23:35] <sistpoty> leleobhz: in short, all changes are done in a unified diff, hence you cannot add or change binary files, as these cannot be represented via .diff.gz
[23:36] <leleobhz> lets see
[23:37] <leleobhz> sistpoty: right! intruder files
[23:40] <LaserJock> i4x: the sudo part yes, not sure about mysql
[23:42] <Lichte> is there any reason why tcltls can't use tcl8.5 ?
[23:42] <leleobhz> now building...
[23:56] <i4x> LaserJock: can you explain me one thing? I'm trying to build a package to install some files and to run some instructions! I'm trying to do it from 'ed-0.9.deb' but I'm afraid to change some files like 'rules' and then it fail!.. do you know any examples to learn better what may or not change? thx in advance!
[23:56] <LaserJock> i4x: you might want to look at http://wiki.ubuntu.com/PackagingGuide
[23:59] <i4x> LaserJock: I'm already reading it!.. but I can't find anything better than https://wiki.ubuntu.com/PackagingGuide/Lists/DhMakeExampleFiles?highlight=(CategoryPackagingGuideList)
[23:59] <LaserJock> i4x: well, what are you wanting to do?


[05:06] <grantbow> 19
[05:06] <grantbow> mt
[06:44] <didrocks> hey mmrazik, how are you?
[06:44] <mmrazik> didrocks: morning
[06:44] <didrocks> mmrazik: yesterday, unity FTBFS on armhf in our buildds, I'm wondering, you are still building unity on armhf in jenkins, right?
[06:45] <mmrazik> didrocks: we never did due to the build times
[06:45] <mmrazik> we recently had a discussion about this with bregma
[06:45] <didrocks> mmrazik: did you put in place the improvements and checked with jibel as I told you?
[06:46] <mmrazik> didrocks: like what improvements? We are using libeatmydata, updagint the base images, etc
[06:46] <mmrazik> didrocks: there is actually something we plan to do and it is on its way
[06:47] <didrocks> mmrazik: having the pbuilder on RAM for instance, he had other tricks iirc as wwell
[06:47] <mmrazik> didrocks: pbuilder on RAM on pandas is not really an option
[06:47] <didrocks> mmrazik: ok, do you have a rough idea on when those improvements will happen?
[06:47] <mmrazik> didrocks: and we do have pbuilder on ARM btw
[06:50] <mmrazik> didrocks: ehm... I mean pbuilder on RAM
[06:50] <mmrazik> it doesn't make a huge difference, though
[06:50] <didrocks> ok
[07:22] <smspillaz> I always wondered why we couldn't just cross-compile for ARM, but given that the last time I tried to do that it was a total pain
[07:22] <smspillaz> I guess I can see why
[07:22] <smspillaz> (python being the main problem)
[07:59] <mmrazik> didrocks: can I re-run the ps-indicators-autopilot-release-testing job?
[07:59] <mmrazik> would like to try the logging
[08:00] <didrocks> mmrazik: it will dep-wait on the unity one which is running
[08:00] <didrocks> mmrazik: as there are still some install issues, do you mind if we do that a little bit later?
[08:00] <didrocks> mmrazik: I think jibel will again have to log in on the machine to see why we had this code return 2
[08:00] <mmrazik> didrocks: ok. Can I save the config  or it would be better if I don't touch that either
[08:01] <mmrazik> save the config == save the ps-indicators-autopilot-release-testing job in jenkins
[08:01] <didrocks> mmrazik: oh please do save the config :)
[08:01] <mmrazik> ok
[08:01] <didrocks> mmrazik: then, I'll tell you once we will rerun the job
[08:01] <didrocks> thanks a lot :)
[08:01] <mmrazik> didrocks: cool. thanks
[08:22] <jibel> good morning!
[08:54] <didrocks> sil2100: hey, how are you?
[08:55] <sil2100> didrocks: hey! All is well, how about you?
[08:56] <didrocks> sil2100: well, better than UTAH tbh :p
[08:56] <didrocks> or rather the UTAH state is impacting me more and more
[08:56] <didrocks> no release for a week now :/
[08:56] <sil2100> Still some more UTAH problems?
[08:56] <sil2100> WTF? Why suddenly those problems? We never had problems like those
[08:57] <didrocks> we always had problems
[08:57] <didrocks> and have to relaunch
[08:57] <didrocks> and so on
[08:57] <didrocks> but yeah, now, this went from 60 to 100% of failures on at least one of the 3 machines
[08:58] <sil2100> Woha! Ok, I'm clean! I didn't break anything ;)
[08:58] <didrocks> sil2100: heh, however, we still get some partial results
[08:58] <didrocks> sil2100: and random failure
[08:58] <didrocks> sil2100: mind having a look?
[08:58] <sil2100> didrocks: hate those - on which job?
[08:58] <didrocks> sil2100: ps-indicators-autopilot-release-testing, ati
[08:58]  * sil2100 needs to poke someone today to review his ibus fixes
[08:58] <didrocks> the only which ran :/
[08:58] <didrocks> run 122
[09:00] <didrocks> sil2100: also, if you want relatively fresh unity results:
[09:00] <didrocks> ps-unity-autopilot-release-testing/82
[09:00] <didrocks> ati and intel ran
[09:00] <sil2100> This one again, I'm starting to think it's another one of those hidden, randomly-appearing regressions, focus from the HUD is obviously broken
[09:00] <didrocks> we do have 25 and 26 tests failing
[09:01] <didrocks> sil2100: at least, if it is a regression, it's already a start that we catch those :)
[09:01] <sil2100> didrocks: I think now that it's been reproduced more than a few times in the past few builds, I think I can try patching it up
[09:02] <sil2100> didrocks: I'm also still working on the introspection-problem with preview tests
[09:02] <sil2100> That's 3 failing tests from-time-to-time
[09:05] <didrocks> sil2100: excellent :-)
[09:05] <didrocks> thanks sil2100
[09:07] <sil2100> np, hope we'll be able to resolve all problems - both AP and UTAH
[09:08] <didrocks> sil2100: I cross fingers as well
[09:28] <sil2100> hah, ok, good thing! I was able to reproduce it locally, the failing test-case
[09:28] <didrocks> sil2100: \o/
[11:24] <smspillaz> didrocks: sil2100: mmrazik: hey, do any of you guys know what the status of xorg-gtest is in the distro
[11:24] <smspillaz> I've been told that its been upgraded to 0.8, but it seems like the CI builders have 0.3
[11:25] <didrocks> smspillaz: we do have 0.7 in the distro https://launchpad.net/ubuntu/+source/xorg-gtest
[11:25] <didrocks> smspillaz: 0.3 sounds like some builders are under quantal, not raring
[11:25] <smspillaz> didrocks: ah okay
[11:26] <smspillaz> mmrazik: I know you guys are busy today, so I won't bother you too much, just something to keep on the radar: http://jenkins.qa.ubuntu.com/job/compiz-clang-ci/build=pbuilder,distribution=quantal,flavor=amd64/63/console (we should probably upgrade the builders to raring)
[11:27] <smspillaz> in the meantime, I'll add a proper version check as I see we are missing that
[11:27] <mmrazik> smspillaz: ack. Will do
[11:27] <mmrazik> its easy. let me do it right away so I don't forget
[11:27] <smspillaz> ah okay. I'll add the version check now too, since we really should be doing that on our end :)
[11:28] <mmrazik> smspillaz: should be fixed
[11:29] <smspillaz> great, thanks
[11:30] <smspillaz> didrocks: mmrazik: we should now have all the compiz tests run under CI now \o/
[11:33] <didrocks> smspillaz: sweet! :) nice work!
[11:40] <mmrazik> smspillaz: btw. do we need to run the memcheck tests also for clang/gles?
[11:40] <mmrazik> they take aaaages
[11:40] <mmrazik> (just saying:-)
[11:43] <smspillaz> mmrazik: we might need them for gles, maybe not clang
[11:44] <smspillaz> mmrazik: they do take ages though - and they are not really useful for catching regressions in branch submissions because they are run in silent mode
[11:44] <smspillaz> maybe it would be better for compiz-mbs-autolanding ?
[11:45] <mmrazik> smspillaz: I don't have any strong opinion. If you tell me we should do it only for autolanding and disable for ci then we can do it
[11:46] <mmrazik> smspillaz: the reason why I'm asking that I've a lot of ci jobs in the queue in the last two days or so
[11:46] <smspillaz> if its taking up your resources, I would be behind it
[11:46] <smspillaz> mmrazik: heh, yeah, mea culpa :p
[11:46] <mmrazik> and they were waiting just for the others to finish (we should try to run them in parallel for different MPs but that is another story)
[11:46] <smspillaz> mmrazik: hehe, maybe we should borrow google's test infrastructure :p
[11:47] <smspillaz> they have this big system which determines which tests actually need to be re-run for every change
[11:47] <smspillaz> I think chromium has something like 30k tests, so it saves them a bit :p
[11:47] <smspillaz> of course, that is very complicated :)
[12:56] <didrocks> smspillaz: Trevinho: we are getting regular compiz crashes on one intel machine where autopilot is run, the best stacktrace I could get is http://paste.ubuntu.com/1643707/ though :/
[13:02] <sil2100> ;/
[13:29] <smspillaz> didrocks: on startup or at runtime ?
[13:30] <didrocks> smspillaz: hard to know TBH, I would suspect startup/shutdown
[13:30] <didrocks> (even more shutdown TBH)
[13:30] <didrocks> it happens reliably once per multiple shutdown on that machine
[13:30] <didrocks> not sure why
[13:30] <smspillaz> didrocks: do you have the stdout ?
[13:31] <bregma> so farno one has been able to pinpoint exactly where that stacksmasher crash happens, since there is lag between the crash and the reporting and no one can repro it outside of the autobuilder
[13:31] <smspillaz> maybe unity is crashing when it gets unloaded ? *shrug*
[13:31] <didrocks> smspillaz: unfortunately not, but good point, will try to get it for next time
[13:31] <didrocks> bregma: oh?
[13:31] <smspillaz> bregma: when all else fails, printf-style debugging can help a bit
[13:31] <bregma> as far as I know
[13:31] <smspillaz> also make sure you build with -g and no optimization
[13:32] <smspillaz> (though afaict you're doing that already)
[13:32] <bregma> -ggdb3 -O0 won;t help with a stack smasher
[13:33] <bregma> problem is either (1) ABI mismatch (2) invalid function pointer  (3) local array walker
[13:33] <bregma> or, like with javascript, invalid JIT code
[13:33] <bregma> which does not apply here
[13:33] <smspillaz> didrocks: bregma: I'd suggest setting up a new job just for that machine which just loads compiz + unity and shuts down again
[13:33] <bregma> good plan
[13:34] <smspillaz> that will at least make the feedback loop a lot shorter
[13:34] <didrocks> bregma: do you have another way of reproducing it than this machine?
[13:34] <smspillaz> bregma: actually, I don't trust gnome not to pull in a JIT
[13:34] <smspillaz> ;-)
[13:34] <didrocks> because for this one, reinstalling is mandatory with the system and it's taking a lot of time
[13:34] <bregma> no one I have spoke to has been able to reproduce it
[13:34] <smspillaz> bregma: I heard that gnome is switching to another favorite language again, lol
[13:35] <bregma> of course, maybe someone has reproduced the problem and not told me
[13:35] <smspillaz> C! wait, python! wait, C#!, wait, vala! wait, javascript!
[13:35] <smspillaz> didrocks: is reinstalling /really/ mandatory ?
[13:35] <smspillaz> surely it isn;t
[13:35] <smspillaz> *isn't
[13:36] <didrocks> smspillaz: well, it is with this process, unfortunately
[13:36] <didrocks> smspillaz: as the machine is used that way and dont' really have an access to it
[13:36] <smspillaz> how can we not have access to one of our own machines?
[13:37] <didrocks> smspillaz: I can't, some can, but those people don't know how to debug/run that
[13:39] <smspillaz> this really is the joy of "it fails on CI and I don't know why"
[13:40] <didrocks> similarly, yeah
[13:40] <smspillaz> didrocks: how long does the reinstall process take ?
[13:40] <smspillaz> and for comparison, how long does the full AP take ?
[13:41] <smspillaz> a good strategy would be to grab the stdout, figure out which test its crashing on, and then create a new job for that machine which just runs the suite
[13:41] <didrocks> smspillaz: well, more strangely, if we run *all* tests, including those ones, it's not crashing
[13:41] <didrocks> smspillaz: but maybe autopilot doesn't act the same for session restart between "running just some tests or all tests"
[13:42] <didrocks> thomi should know though ^
[13:42] <smspillaz> wait, so do we know which test its crashing on?
[13:42] <smspillaz> or at least, a way to reproduce the problem which doesn't take forever ?
[13:42] <didrocks> smspillaz: well, it's taking 40 minutes in total
[13:42] <didrocks> smspillaz: with only those 89 tests running
[13:43] <didrocks> but, the session is randomly restarted
[13:43] <smspillaz> the first thing I'd suggest doing at least, would be to run compiz --debug
[13:43] <smspillaz> by "session" are you talking about X, or compiz ?
[13:43] <didrocks> smspillaz: this needs a lot of tweaking
[13:43] <didrocks> X session
[13:43] <smspillaz> so X is crashing!??
[13:43] <didrocks> smspillaz: no, compiz
[13:43] <smspillaz> wait what
[13:43] <didrocks> smspillaz: but lightdm is restarted regularly
[13:43] <didrocks> between tests
[13:43] <didrocks> from what I know
[13:43] <smspillaz> oh okay
[13:45] <didrocks> I think at next crash, I'll look for the timestamp of the .crash file
[13:45] <didrocks> at least, it will tell us if it's at the beginning of end of tests
[13:47] <smspillaz> huh? doesn't autopilot have some kind of method to handle the case where it doesn't receive a reply from dbus ?
[13:47] <didrocks> not sure
[13:47] <smspillaz> I'm pretty sure theres a dbus error that you get when the relevant client sends a SIGHUP or whatever
[13:49] <smspillaz> didrocks: what makes running compiz with --debug so difficult btw ?
[13:49] <didrocks> smspillaz: well, we need a different package and so on, because compiz is launched by the session
[13:49] <didrocks> and we need a hook to save the .xsession-errors for each session
[13:50] <smspillaz> doesn't autopilot monitor the stdout?
[13:50] <smspillaz> ohmygawd....
[13:50] <didrocks> and again, only thomi knows how and when autopilot restarts the session and the difference between "run all tests" and "a set of tests provided"
[13:50] <didrocks> smspillaz: no
[13:50] <didrocks> ok, now going to do some exercice, already 3 hours late :)
[13:51]  * smspillaz thinks we should rewrite all of the AP tests in xorg-gtest
[13:51] <smspillaz> sil2100: still around ?
[13:51] <smspillaz> (maybe you might know some more about this)
[13:53] <sil2100> smspillaz: hi!
[13:53] <sil2100> smspillaz: what's up? Some tests need rewriting ;) ?
[13:54] <smspillaz> sil2100: how hard would it be to roll a ppa to the machine with the failing AP test to run compiz with --debug and capture the stdout
[13:57] <sil2100> smspillaz: I don't think it should be that hard, but probably someone from the jenkins-maintainers would have to help out
[13:57] <smspillaz> sil2100: okay
[13:57] <smspillaz> sil2100: make it happen
[13:58] <sil2100> smspillaz: ok :) Will poke people about it then! You only need compiz --debug and the output, or something else? Should the tests run?
[13:58]  * sil2100 needs to get the context correctly
[13:58] <smspillaz> yeah keep the tests running
[13:58] <smspillaz> we just need to get
[13:58] <smspillaz> a) Which test autopilot detected that the compiz process stopped responding to dbus calls
[13:59] <smspillaz> b) The compiz stdout/stderr (eg .xsession-errors) from --debug
[13:59] <smspillaz> from there we can start to pinpoint the source of this
[15:47] <didrocks> mterry: cyphermox: hey guys, just a quick summary of the day for dailyrelease
[15:47] <didrocks> mterry: cyphermox: so, we got the UTAH new failure of the day, I debugged it and workarounded it
[15:47] <didrocks> mterry: cyphermox: unfortunately, we are still hitting another random $install issue if we run only the indicator tests
[15:48] <didrocks> with mterry's manual run of unity, I hope we can have that passing
[15:48] <didrocks> if so, I would propose:
[15:48] <didrocks> - manually publishing unity
[15:48] <didrocks> - manually publishing indicator (even if the tests didn't pass because of the installed, they are run as part of unity)
[15:48] <didrocks> - manual publishing of oif which failed for a similar random behavior
[15:49] <didrocks> so that tomorrow, we can try transitionning from the HUD
[15:49]  * didrocks spent a big part of his day debugging UTAH for upstream, not pleasant…
[15:49] <didrocks> mterry: cyphermox: wdyt?
[15:49] <cyphermox> yeah
[15:49] <cyphermox> the tests for indicators look okay enough, AFAICS
[15:49] <didrocks> (the new failure was "not enough loop device for mounting the iso")
[15:50] <cyphermox> oh boy
[15:50] <didrocks> cyphermox: yeah, seems so, if you try to agregate the results from different runs on all configs :)
[15:50] <didrocks> cyphermox: I think oif is safe already, mind a manual publishing?
[15:50] <mterry> didrocks, OK
[15:50] <didrocks> at least, this one will be done :)
[15:50] <cyphermox> ok
[15:51] <didrocks> meanwhile, misc continues to publish everyday nicely (as not UTAH/integration tests involved) :p
[15:51] <didrocks> no*
[15:51] <cyphermox> hehe
[15:51] <didrocks> andyrock: thanks for the amrhf fix btw :)
[15:52] <andyrock> np
[15:53] <cyphermox> ok starting with oif
[15:53] <cyphermox> ./cu2d-run -P oif
[15:53] <mterry> didrocks, let's just put unity in misc then!
[15:53]  * mterry is a problem solver
[15:53]  * cyphermox likes mterry's idea
[15:54] <mterry> cyphermox, watch out!  you own misc stack
[15:54] <cyphermox> didrocks: ^ confirm? ;)
[15:54] <cyphermox> ah crap you're right
[15:54] <didrocks> cyphermox: confirmed!
[15:54] <mterry> muhaha
[15:54] <didrocks> mterry: hum hum
[15:54] <didrocks> mterry: don't even start that :p
[15:54] <cyphermox> let's NOT put unity in misc ;)
[15:55] <didrocks> mterry: TBH, you just need to remove one parameter from the yaml file and republish the jobs
[15:55] <didrocks> mterry: and then, it will forget about the -check step :p
[15:55] <didrocks> not sure it's what we want though :p
[15:55] <cyphermox> didrocks: it would be fine
[15:55] <cyphermox> it's all very stable code, no?
[15:56] <cyphermox> oif publishing...
[15:56] <didrocks> cyphermox: hem hem :p
[15:56] <didrocks> we saw that everyday ;)
[16:00] <didrocks> and oif released :)
[16:04] <sil2100> \o/
[16:05] <cyphermox> yay
[16:06] <cyphermox> so now, iindicators or unity first?
[16:13] <didrocks> cyphermox: unity is rerunning with full tests
[16:13] <didrocks> cyphermox: let's see the results
[16:13] <didrocks> if ok, we can publish indicators and unity
[16:13] <didrocks> manual publishing as well
[16:14] <didrocks> (I'm finally happy to have enabled that manual publishing can bystep the status of build/check for all "prepared" source
[16:14] <didrocks> seems to be handy when I thought it wouldn't :p
[16:14] <didrocks> ok, at least, the 3 machines installed and rebooted successfully
[16:14] <didrocks> they are now running tests
[16:15] <sil2100> hmmm
[16:16] <didrocks> sil2100: shaking? :)
[16:16] <sil2100> I almost found something, but I need to jump out for practice now - I'll resume my work in the evening
[16:16] <didrocks> sil2100: sweet, do you mind having a look at the results of the unity test job once you are back?
[16:16] <sil2100> didrocks: shaking what?
[16:16] <sil2100> didrocks: no problem - both indicators and unity, right?
[16:17] <didrocks> sil2100: just thinking as I was telling "the tests are now running" that you were troubled as it means your new tests are running :p
[16:17] <didrocks> sil2100: just unity
[16:17] <didrocks> all would be run that way anyway
[16:17] <sil2100> didrocks: ok, no problem ;)
[16:17] <didrocks> thanks sil2100 :)
[16:17] <didrocks> sil2100: enjoy your exercice!
[17:18] <didrocks> mterry: cyphermox: the tests results sounds good to me on ati, and nvidia, I've a doubt on intel though
[17:18] <didrocks> mterry: cyphermox: I don't see anything weird, using the ppa, do you?
[17:18] <didrocks> (I've some intel hw)
[17:19] <cyphermox> let me double check
[17:19] <cyphermox> I'm on intel too anyway
[17:21] <didrocks> thanks :)
[17:22] <mterry> didrocks, I haven't rebooted in days
[17:22] <mterry> I'll update and restart
[17:24] <mterry> didrocks, you aren't suggesting that we ignore the threshold here and manually publish are you?  tsk tsk
[17:24] <mterry> Where's that ibus fix?  That should drop the tests nicely
[17:24] <didrocks> sil2100: ^
[17:24] <didrocks> mterry: well, it's as you wish, you are stack holders :-)
[17:25] <mterry> Hrm, not reviewed yet.  sil2100 has it waiting
[17:25] <mterry> for review that is
[17:25] <didrocks> mterry: just that knowing how all those things are fuzzy…
[17:25] <didrocks> then you decide with cyphermox if you publish indicators/unity ;)
[17:25] <mterry> didrocks, a reason to drive them to perfection!  :)  You mentioned a reason you wanted a publish checkpoint?  HUD stuff?
[17:26] <didrocks> mterry: yeah, I wanted a before, and then after HUD
[17:26] <didrocks> as we have the HUD transition
[17:26] <didrocks> and the day after that libcolumbus
[17:27] <didrocks> mterry: it's really as you feel it, maybe we shouldn't push the trigger, yeah
[17:28] <cyphermox> you're talking about unity specifically there right?
[17:28] <cyphermox> because we really should finish up publishing indicators so that we can move forward on hud
[17:31] <mterry> cyphermox, yeah unity.  The new test failures all seemed to come from dash tests
[17:31] <didrocks> cyphermox: if we are sure we don't have dep between indicators and unity publishin, I think we can (I don't see indicators tests failing in the unity suite run)
[17:31] <didrocks> mterry: I wonder why the dash failed so much on intel
[17:31] <didrocks> still a little bit on nvidia
[17:35] <mterry> didrocks, cyphermox: Is publishing indicators sufficient to not block hud?
[17:36] <mterry> cyphermox, ah, still getting crashes on the indicator tests...  :-/
[17:36] <didrocks> mterry: yeah
[17:37] <didrocks> it's sufficient
[17:37] <cyphermox> well what we really need is to ship libcolumbus and all so that we can ship hud; then do the hudectomy in indicator-appmenu, and then republish hud for libcolumbus, IIRC
[17:37] <mterry> OK, then I'd just as soon leave unity to its own devices as long as there's no pressing need for that stack specifically
[17:38] <mterry> sil2100's ibus branch should get us under threshold again (at which point, we should probably lower the threshold a bit)
[17:56] <didrocks> cyphermox: so, manual publishing for the indicators?
[17:57] <cyphermox> yeah, let's
[17:57] <cyphermox> aside from that, was libcolumbus ready to be uploaded, added to the stacks and everything?
[17:57] <didrocks> cyphermox: we need the hud first
[17:57] <didrocks> then, libcolumbus :)
[17:58] <didrocks> but IIRC, libcolumbus is ready
[17:58] <cyphermox> well, yeah, but I mean, libcolumbus can land now and hud not depend on it immediately
[17:58] <cyphermox> then it give us time for the MIR in parallel, even if it won't take so much time
[18:01] <didrocks> cyphermox: well, you need to rerun a rebuild if you do that, before the publishing
[18:02] <cyphermox> libcolumbus will be in indicators stack right?
[18:02] <cyphermox> I'm doing the publishing now, but then I'll add it to the stack and update
[18:02] <didrocks> cyphermox: sounds good to me :)
[18:03] <cyphermox> ./cu2d-run -P indicators
[18:03] <didrocks> cyphermox: I'm just leaving, but I think we won't have it landing automatically tomorrow as it will be at least in manual publishing mode :)
[18:03] <didrocks> cyphermox: yep ;)
[18:03] <didrocks> due to the new package
[18:03] <cyphermox> yeah
[18:03] <didrocks> so don't need to refresh the AA side right away
[18:03] <didrocks> I'll do that tomorrow morning
[18:03] <cyphermox> no
[18:03] <cyphermox> I'll only update the stack later
[18:03] <seb128> cyphermox, didrocks: I can NEW review if you want
[18:04] <cyphermox> seb128: ok
[18:04] <didrocks> seb128: not the issue, you need to pull on lillypilly
[18:04] <cyphermox> it won't land today anyway
[18:04] <didrocks> seb128: for the AA-side filtering
[18:04] <seb128> didrocks, I was proposing to review it  once it's in the raring NEW queue
[18:04] <seb128> didrocks, I didn't follow what you are doing out of "it's going to be uploaded in the next days" ;-)
[18:04] <didrocks> seb128: yeah, it will be marked as a sync :)
[18:05] <seb128> oh, right
[18:05] <didrocks> seb128: but once cyphermox updated the list, first, to be uploaded to the archive, we need to refresh the filtering
[18:05] <seb128> well in any case if NEW review is needed just ping me
[18:05] <didrocks> seb128: yeah, but you can do the filter refreshing as well once cyphermox will add it to the list (after this manual publishing round)
[18:05] <cyphermox> ok!
[18:05] <didrocks> seb128: on lillypilly, just log as archive admin
[18:05] <didrocks> cd cu2d
[18:06] <didrocks> cd cupstream2distro
[18:06] <didrocks> bzr pull
[18:06] <didrocks> you should see the updated yaml file once cyphermox did it :)
[18:06] <seb128> didrocks, ok, cool, good to know ;-)
[18:06]  * seb128 tomboys that
[18:11] <didrocks> seb128: https://wiki.ubuntu.com/DailyRelease/FAQ#Adding.2BAC8-removing_components_to_a_stack
[18:11] <didrocks> second part :)
[18:12] <seb128> didrocks, ahah, excellent ;-)
[18:12] <didrocks> hot from the press! :)
[20:01] <mterry> sil2100, did someone mention that last night intel had 10 new dash failures?  http://<IP_ADDRESS>:8080/job/ps-unity-autopilot-release-testing/label=autopilot-intel/lastCompletedBuild/testReport/
[20:01] <mterry> sil2100, do you know why that might be?
[20:19] <sil2100> mterry: checking
[20:20] <mterry> sil2100, thanks for rocking that ibus merge proposal too
[20:20] <mterry> I'm looking forward to that landing
[20:20] <sil2100> mterry: np! Hope it fixes the problems for good
[20:50] <sil2100> hm
[21:05] <sil2100> mterry: those failing tests... they seem to be related to the previous failing tests
[21:06] <sil2100> Not sure why now they started failing
[21:06] <sil2100> But the reason seems to be a problem while fetching the state of the preview open, I'm already looking into it regarding the previous failures
[21:06] <sil2100> mterry: if anything, I'm currently looking at two failure types (so that we don't step on eachothers toes ;) )
[21:07] <sil2100> The first thing: the dash previews having problems
[21:07] <sil2100> The second: HUD focus issues
[21:10] <mterry> sil2100, awesome, thanks!
[21:10] <mterry> One day we'll have no failures!
[22:26] <sil2100> thomi: hi! Once you're up and running, could you take a look on two of my autopilot merges for lp:unity?
[22:27] <sil2100> thomi: one regarding ibus, the second regarding a new test suite (for search)
[22:28] <sil2100> mterry: just to make sure - the testing environment for the release test jobs is single-monitor, right?
[22:44] <thomi> sil2100: sure
[22:44]  * thomi looks now
[22:44] <sil2100> \o/ Thanks :)
[22:45] <sil2100> https://code.launchpad.net/~sil2100/unity/autopilot_search_test_suite
[22:45] <sil2100> https://code.launchpad.net/~sil2100/unity/autopilot_ibus_improve


[15:53] <etsorbme8> I have an application that wants to use comport one however I don't have a comport one and want to use comport 2, is there anyway to use a command to redirect


[01:26] <mamarley> acheronuk: I have installed the Plasma 5.12 you uploaded to kubuntu-ninjas.  Everything seems to work. :)
[02:27] <ahoneybun> tsimonq2: how did you make that project page for lubuntu on github?
 @ahoneybun, What project page are you referring to?
[02:28] <ahoneybun> https://github.com/lubuntu-team
 That's just a GitHub organization.
[02:29] <ahoneybun> mm not sure how to make an org
[02:29] <ahoneybun> just a user account
 It's not a user account :)
[02:29] <ahoneybun> I know
[02:29] <ahoneybun> that's the problem
[02:30] <ahoneybun> got it
[02:32] <ahoneybun> mm and now to copy the manual over to that.
[02:34] <ahoneybun> tsimonq2: going to ask for help with this: http://cdimage.ubuntu.com/kubuntu/daily-live/current/
[02:34] <ahoneybun> updating that page
 @ahoneybun, Have you seen Lubuntu's?
[02:34] <ahoneybun> yes
 Ok
 Look at the recent commits to lp:ubuntu-cdimage
[02:35] <ahoneybun> going to have to fix Travis for the Manual first lol
 And the Launchpad mirror of cdimage-css is what's on cdimage.ubuntu.com/include
 I'll write up something more detailed after Beta 1
[02:36] <ahoneybun> cool
[02:37] <ahoneybun> yay : https://github.com/kubuntu-team/kubuntu-manual
[02:37] <ahoneybun> valorie: ^
 Fwiw, we would have lubuntu on GitHub if it wasn't already taken.
[02:48] <valorie> weeeeeeeee!
[02:48] <valorie> thanks, ahoneybun
[02:48] <ahoneybun> yep
[02:48] <ahoneybun> added you to the project as well valorie
[02:48] <ahoneybun> tsimonq2: too
[02:48] <ahoneybun> I'm working to get Travis building now
[02:48] <valorie> thank you!
[02:49] <valorie> if we can get it to mirror bi-directionally it will be awesomesauce
 I'm about to go to bed but tomorrow I can get you the script I have running on cron on Lubuntu's server
[02:51] <ahoneybun> tsimonq2: cool
[02:51] <ahoneybun> https://travis-ci.org/kubuntu-team/kubuntu-manual
[02:51] <ahoneybun> working to get it to build
[02:52] <ahoneybun> and it's building
[02:53] <ahoneybun> valorie: Not sure about the bi-directionally. Do we have a Kubuntu team other then the package stuff?
 https://paste.ubuntu.com/26516475/
[02:54] <ahoneybun> I think this is the top of the chain : https://launchpad.net/~kubuntu-dev-owner valorie
[02:55] <valorie> well, I'm not sure what you mean by top of the chain
[02:55] <ahoneybun> well that's the team that owns a lot of things
[02:55] <valorie> but being able to clone from lp OR github would be cool
 recent update broke the package?
[02:55] <ahoneybun> idk bzr kinda sucks
[02:56] <valorie> no git
[02:56] <valorie> lp git <> github
 @myfenris what am I looking for?
[02:57] <ahoneybun> valorie: I'll look into it.
 @ahoneybun, should i normal upgrade or dist-upgrade
 I've just done normal upgrade
 I THINK dist-upgrade is for upgrading releases or something
 not sure tbh
[02:59] <valorie> no: apt full-upgrade is the best
 if normal upgrade , The following packages have been kept back: …   libkf5notifications-data libkf5notifications5
[02:59] <valorie> or apt-get dist-upgrade
 maybe those 2 package still in building
[03:00] <valorie> if you want to upgrade to the next version, you do `do-release-upgrade`
 valorie: if dist-upgrade ... The following packages will be REMOVED: …   libdbusmenu-qt5 quassel-client
[03:00] <valorie> followed by -d if you want to do bionic for instance
[03:01] <valorie> yes, both dist-upgrade and full-upgrade can remove old cruft
 i mean not the distribution upgrade ... I already in bionic
[03:01] <valorie> one of the good parts of using that
 so i need to remove the quassel-client ?
[03:01] <valorie> imo one should always use dist-upgrade or full-upgrade
[03:01] <ahoneybun> valorie: all set : https://travis-ci.org/kubuntu-team/kubuntu-manual/builds/337104653
 @valorie, noted
[03:02] <valorie> nice, ahoneybun!
[03:02] <valorie> @myfenris -- the neon team won't even talk to someone using plain old upgrade
[03:03] <valorie> lol
[03:03] <valorie> they mostly use pkcon
[03:03] <ahoneybun> little confused on something though.
[03:03] <valorie> instead of apt, which didn't work for me in kubuntu
[03:03] <valorie> ahoneybun: ?
 or the quassel-client need to rebuild with latest libdbusmenu-qt?
[03:04] <ahoneybun> I'm not seeing my change local but it shows in github
[03:04] <ahoneybun> mm
 im using mamarley-ubuntu-quassel-git-bionic.list ppa for the quassel
[03:05] <valorie> @myfenris, did you not get a new ibdbusmenu-qt when you did dist-upgrade?
[03:05] <valorie> hmmm
[03:05] <valorie> it's possible that mamarley didn't bump that yet
 @valorie, got .. but im afraid of losing quassel-client :)
[03:05] <valorie> you'll need to contact them
[03:05] <valorie> ah
[03:05] <valorie> I hear you
 or i just fall back to stable version of quassel by not using ppa
[03:07] <valorie> is that a problem?
[03:07] <valorie> I don't use quassel, so.....
 im using quassel-core n client
[03:10] <valorie> I guess I would ask maamarley before making a move
 @Valoriez : thanks .. really much appreciated
[03:18] <valorie> :-)
[03:22] <mamarley> myfenris: Oh, sorry, I had forgotten about the dbusmenu thing for the quassel-git builds.  I will kick off a new set of builds now.
[03:27] <valorie> mamarley: did you get an invite to the #ubuntu-qt channel?
[03:27] <valorie> we want you there!
 \0/ thanks @mamarley .. will wait for it ..
[03:28] <mamarley> valorie: Sorry, yes, a while back, but I didn't notice it.  What's wrong, did I break something?
[03:28] <valorie> no, no
[03:28] <valorie> it's all about scheduling stuff, etc.
[03:29] <mamarley> I have joined :)
[03:30] <valorie> \o/
 https://launchpad.net/~mamarley/+archive/ubuntu/quassel-git/+build/14306701 \0/ build finished .. but when i tried to update my repo ... cant get the latest build
[03:38] <mamarley> myfenris: It hasn't published yet.  Give it a few minutes.
[03:41] <ejat> okie @mamarley :) i need to be more patience
[03:43] <valorie> don't we all!
[03:45] <ejat> https://paste.ubuntu.com/26516680/
[03:45] <ejat> \0/ thanks mamarley
[03:46] <mamarley> No problem :)
[09:25] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_discover build #355: STILL FAILING in 3 min 44 sec: https://kci.pangea.pub/job/xenial_unstable_discover/355/
[09:27] -kubuntu-ci:#kubuntu-devel- Project bionic_stable_discover build #65: FAILURE in 4 min 39 sec: https://kci.pangea.pub/job/bionic_stable_discover/65/
[09:27] -kubuntu-ci:#kubuntu-devel- Project bionic_unstable_discover build #72: FAILURE in 4 min 42 sec: https://kci.pangea.pub/job/bionic_unstable_discover/72/
[09:27] -kubuntu-ci:#kubuntu-devel- Project xenial_stable_discover build #149: FAILURE in 5 min 21 sec: https://kci.pangea.pub/job/xenial_stable_discover/149/
[09:35] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_discover build #356: STILL FAILING in 4 min 28 sec: https://kci.pangea.pub/job/xenial_unstable_discover/356/
[09:36] -kubuntu-ci:#kubuntu-devel- Project bionic_stable_discover build #66: STILL FAILING in 4 min 25 sec: https://kci.pangea.pub/job/bionic_stable_discover/66/
[09:36] -kubuntu-ci:#kubuntu-devel- Project bionic_unstable_discover build #73: STILL FAILING in 4 min 22 sec: https://kci.pangea.pub/job/bionic_unstable_discover/73/
[09:36] -kubuntu-ci:#kubuntu-devel- Project xenial_stable_discover build #150: STILL FAILING in 3 min 58 sec: https://kci.pangea.pub/job/xenial_stable_discover/150/
[09:57] -kubuntu-ci:#kubuntu-devel- Project bionic_unstable_knotifications build #65: UNSTABLE in 17 min: https://kci.pangea.pub/job/bionic_unstable_knotifications/65/
[09:58] -kubuntu-ci:#kubuntu-devel- Project mgmt_docker » linode-01 build #2042: SUCCESS in 40 sec: https://kci.pangea.pub/job/mgmt_docker/label=linode-01/2042/
[09:58] -kubuntu-ci:#kubuntu-devel- Project mgmt_docker » master build #2042: SUCCESS in 1 min 5 sec: https://kci.pangea.pub/job/mgmt_docker/label=master/2042/
[10:01] -kubuntu-ci:#kubuntu-devel- Project mgmt_docker » swy-01 build #2042: SUCCESS in 3 min 44 sec: https://kci.pangea.pub/job/mgmt_docker/label=swy-01/2042/
[10:22] -kubuntu-ci:#kubuntu-devel- Yippee, build fixed!
[10:22] -kubuntu-ci:#kubuntu-devel- Project bionic_unstable_discover build #74: FIXED in 21 min: https://kci.pangea.pub/job/bionic_unstable_discover/74/
[10:46] -kubuntu-ci:#kubuntu-devel- Yippee, build fixed!
[10:46] -kubuntu-ci:#kubuntu-devel- Project bionic_stable_discover build #67: FIXED in 15 min: https://kci.pangea.pub/job/bionic_stable_discover/67/
 @nggraham great work https://pointieststick.wordpress.com/2018/02/03/this-week-in-usability-productivity-part-4/
[13:27] <BluesKaj> Hiyas all
 Thanks @acheronuk
[15:45] -kubuntu-ci:#kubuntu-devel- Project mgmt_docker » linode-01 build #2043: SUCCESS in 43 sec: https://kci.pangea.pub/job/mgmt_docker/label=linode-01/2043/
[15:46] -kubuntu-ci:#kubuntu-devel- Project mgmt_docker » master build #2043: SUCCESS in 1 min 5 sec: https://kci.pangea.pub/job/mgmt_docker/label=master/2043/
[15:48] -kubuntu-ci:#kubuntu-devel- Project mgmt_docker » swy-01 build #2043: SUCCESS in 3 min 55 sec: https://kci.pangea.pub/job/mgmt_docker/label=swy-01/2043/
[16:49] <clivejo> mamarley: ping
[16:51] <tsimonq2alt> (empty pings solve nothing)
 tsimonq2alt: Hello!  Let me knosw if there's anything I can do to help the process along
 ok :)
 Reminds me I need to get set up on here.
 Oh I already am. Convenient.
[19:13] <ahoneybun> are we in Alpha 2?
[19:13] <tsimonq2> We didn't have a release but I'd call it that, yeah.
[19:14] <ahoneybun> well Alpha 2 is Feb 15
[19:14] <tsimonq2> No it isn't, we missed it.
[19:14] <tsimonq2> https://wiki.ubuntu.com/BionicBeaver/ReleaseSchedule
[19:14] <ahoneybun> ahh
[19:14] <ahoneybun> https://wiki.ubuntu.com/BionicBeaver/ReleaseSchedule : yea saw the 15th
[19:15] <ahoneybun> alright what about Beta 1
[19:16] <tsimonq2> Yeah we'll do that I think
[19:18] <ahoneybun> I kinda feel like adding to this page: https://wiki.ubuntu.com/BionicBeaver/ReleaseSchedule
[19:18] <ahoneybun> opps
[19:19] <tsimonq2> Why?
[19:19] <ahoneybun> https://kubuntu.org/support/
[19:19] <ahoneybun> that one
[19:19] <tsimonq2> ok ;)
[19:19] <ahoneybun> Under Community point out that 18.04 is open for new MR's
[19:25] <ahoneybun> tsimonq2: I think I don't use git tags right lol
[19:27] <tsimonq2> ahoneybun: Want me to fix your stuff? :P
[19:27] <ahoneybun> tsimonq2: or teach me. either works
[19:28] <ahoneybun> https://github.com/ahoneybun/kubuntu-manual/releases
[19:28] <ahoneybun> it's like this I thought
[19:28] <ahoneybun> make changes, tag it, commit, push
[19:46] <nauticalnexus[m]> GitHub
[19:47] <nauticalnexus[m]> You can do blogs on there now
[19:47] <ahoneybun> well the pages thing, yea.
[19:48] <nauticalnexus[m]> I found that out like 2 days ago. Open source blogging lol
[21:29] <ahoneybun> https://usercontent.irccloud-cdn.com/file/yq5rJhXS/Screenshot_20180204_142917.png
[21:29] <ahoneybun> @valorie
[21:33] <ahoneybun> tsimonq2: how are you syncing that page with cdimage.ubuntu.com?
[21:34] <tsimonq2> ahoneybun: heyy, don't steal our CSS ;)
[21:34] <nauticalnexus> lol
[21:34] <ahoneybun> tsimonq2: but the license on it is nice like that lol
[21:34] <ahoneybun> do need to add that it was forked from lubuntu of course
[21:34] <tsimonq2> ahoneybun: nah but in all seriousness, MATE asked me the same thing, my answer to them (and to Kubuntu) is that I'll write a guide after Beta 1 is released. Lubuntu's gotta be a bit exclusive. ;)
[21:34] <tsimonq2> It's all public.
[21:35] <tsimonq2> All of it.
[21:35] <ahoneybun> yep.
[21:35] <tsimonq2> But, it's jumbled :)
[21:35] <ahoneybun> better then it was though.
[21:35] <tsimonq2> If you figure out how we did it, then do it, but HOWTOs come after Beta 1
[21:37] <tsimonq2> Like I said ahoneybun, it's all public.
[22:07] <valorie> nice, ahoneybun
[22:17] <valorie> ahoneybun: still looks like it did yesterday on http://cdimage.ubuntu.com/kubuntu/daily-live/current/
[22:25] <ahoneybun> It's not been updated yet.
[22:25] <ahoneybun> The github is ready though.
[22:26] <valorie> ok
[22:26] <valorie> remember we need like http://cdimage.ubuntu.com/kubuntu/releases/17.10.1/release/ too
[23:23] <ahoneybun> Yea one thing at a time lol.