[00:00] <pavolzetor> I would love to test it in unittest
[06:27] <dpm> good morning all
[07:06] <dholbach> good morning
[07:14] <markus_> hi all: I added my app blubVolley, to developer.ubuntu.com and it needed 8 days to go through approvement and I don't see it in the "Software center" before next week. However will updating my app need the same approvement steps and need that much time too?!
[07:23] <dpm> hi markus_, is yours a commercial app?
[07:23] <markus_> yesss!
[07:23] <markus_> @dpm yesss!
[07:24] <dpm> markus_, in that case, it should be approved soon. I believe the commercial packagers have been busy with submissions lately. I'd recommend pinging zoopster when he's online in a few hours time. As per the question, new updates should take less time than the initial approval
[07:25] <markus_> kk, thank u!
[07:25] <markus_> have a nice day
[08:07] <jokerdino> bug 100000
[08:07] <ubot2> Launchpad bug 100000 in launchpad "There are still too many bug reports" [Undecided,Invalid] https://launchpad.net/bugs/100000
[08:08] <jokerdino> yay twobottux is keeping quiet on bugs.


[16:07] <bluca> andersson1234: hi, seems like we are losing result reports again since the queue got unclogged
[16:07] <bluca> eg this PR shows all pending https://github.com/systemd/systemd/pull/32521
[16:07] <bluca> but only the s390x jobs show in the queue, nothing else either running/queued https://autopkgtest.ubuntu.com/running#pkg-systemd-upstream
[16:08] <bluca> and the s390x queue is still long so sounds like it's expected that's queued, and the others are empty so it sounds to me they did run
[16:08] <bluca> it's intermittent too
[16:08] <bluca> most PRs show all the results, it's just a few that don't
[16:08] <Skia> bluca: we have had some issues with some jobs being lost in case of worker restart
[16:08] <Skia> that's something we want to fix, because it's pretty bad
[16:09] <Skia> I guess that's a good occasion to see about that documentation I just updated, telling us how to retrigger test in the infra? :D
[16:10] <bluca> ah thanks, if it's a known issue then no problem, just wanted to be sure
[16:10] <Skia> btw, do you think it would be possible to only trigger autopkgtest on relevant code changes? I had my documentation PR triggering some tests, but that would be totally irrelevant, and although it's quite fine on amd64, on s390x we don't have much workers
[16:12] <Skia> also, we should see to implement a way of dropping the queued test requests when they are no longer needed, like the documentation MR just got merged, so I guess we could drop the related tests, especially if they haven't been scheduled to run yet
[16:14] <bluca> yeah I had a WIP patch but never manage to make it work
[16:15] <bluca> as it's not trivial, need to do some git-tery stuff
[16:15] <bluca> but I do want to get back to that
[16:15] <Skia> oh great, that would be nice!
[16:15] <bluca> for cancelling jobs yeah that would be great, but I don't think I can do it on my side?
[16:15] <bluca> the infra side should notice that a new request was for a PR that is already queued/running and take care of that
[16:16] <bluca> from the PR ID
[16:16] <Skia> well, as of now, not really, but we have a way to drop tests as admins, so you could always come up and say "hey, please drop tests for PR #123"
[16:16] <Skia> you're talking about removing duplicates, right?
[16:16] <bluca> yes
[16:16] <bluca> but we get too many PRs and they get too many updates to do that by hand
[16:17] <Skia> yes I know
[16:17] <Skia> we usually only do that for big packages in Ubuntu, where we can potentially drop hundreds of jobs at once
[16:18] <Skia> removing duplicates is a topic we've already talked about
[16:18] <bluca> for example, given s390x is all backed up, feel free to drop all pending jobs from our queue
[16:18] <Skia> oh, really?
[16:18] <Skia> that would certainly help :-)
[16:19] <bluca> yeah it's fine
[16:19] <Skia> done, thanks, that will help the s390x infra :D
[16:23] <Skia> I'm still getting familiar with that part of the system. Do you have a pointer to where your side triggers the test requests?
[16:23] <Skia> bluca: ^
[16:24] <bluca> it's only visible to admins, but it's pretty simple, it's a github webhook
[16:24] <bluca> let me fetch the config
[16:24] <Skia> okay thanks, don't bother I imagine what it looks like
[16:24] <bluca> https://autopkgtest.ubuntu.com/request.cgi?release=noble&arch=amd64&package=systemd-upstream&build-git=https%3A%2F%2Fsalsa.debian.org%2Fsystemd-team%2Fsystemd.git%23debian%2Fmaster&ppa=upstream-systemd-ci/systemd-ci&env=CFLAGS=-O0%3BDEB_BUILD_PROFILES=pkg.systemd.upstream%3BTEST_UPSTREAM=1%3BCONFFLAGS_UPSTREAM=--werror%20-Dslow-tests%3Dtrue
[16:24] <bluca> that's the URL
[16:25] <Skia> thanks
[16:25] <bluca> and only the "pull request" type of event is enabled
[16:25] <Skia> ok
[16:25] <bluca> application/json content type
[16:25] <Skia> hehe, I'm not sure that does anything, that endpoint is dump af, and is incapable of returning json :D
[16:26] <bluca> that's the only thing we have on our side - and if there's anything else I need to click on to enable for cancelling duplicates or something, let me know
[16:26] <Skia> we want to add it though
[16:27] <Skia> for now, there isn't anything neither of us can do about that. I need to put some thoughts to what a cancellation mechanism would look like, then get to coding
[16:47] <andersson1234> Sorry I missed this! I was afk for a little while whilst you both spoke. There's work currently in review allowing people to kill running tests from the webpage - we could look at expanding access to that for upstream systemd maintainers if you'd like. We can also definitely consider and triage a "cancellation" mechanism, but I think it requires some thought and discussion
[16:48] <andersson1234> Skia: are we certain the jobs were *lost* with the systemd unit restarts? It's my belief the message should go back into the queue.
[16:50] <andersson1234> bluca: also, you mentioned only triggering CI for *required* changes, the bash detailed here may be of use to you https://git.launchpad.net/qa-jenkins-jobs/tree/jobs/autopkgtest-cloud/jobs.yaml#n74 even if it is quite trivial
[16:51] <andersson1234> it's a jenkins job, where we build our docs, but only want to do so for changes to specific files. So somewhat similar to what you describe
[17:10] <bluca> thanks for the ref
[17:11] <bluca> yeah being able to kill tests from the webpage would be a nice addition


[15:59] <liushuyu> o/
[15:59] <cpete> o/
[15:59] <Skia> o/
[16:00] <ginggs> o/
[16:00] <schopin> \o
[16:00] <mateus-morais> o/
[16:00] <dbungert> o/
[16:01] <juliank> o/
[16:01] <ogayot> o/
[16:01] <juliank> #startmeeting Weekly Ubuntu Foundations team
[16:01] <meetingology> Meeting started at 16:01:20 UTC.  The chair is juliank.  Information about MeetBot at https://wiki.ubuntu.com/meetingology
[16:01] <meetingology> Available commands: action, commands, idea, info, link, nick
[16:01] <juliank> #topic Lightning rounds
[16:01] <pushkarnk> o/
[16:01] <juliank> #link https://discourse.ubuntu.com/t/foundations-team-updates-thursday-18-january-2024/
[16:03] <zhsj> o/
[16:03] <mkukri> o/
[16:04] <adrien> \o
[16:05] <bdmurray> "lost some time learning that a tab after the filename in patches is needed when the filename contains spaces" that sounds awful
[16:06] <ravikant_> o/
[16:07]  * vorlon waves
[16:07] <mclemenceau_> o/
[16:08] <schopin> bdmurray: yeah I scratched my head vigorously when upils came to me on that one.
[16:10] <bdmurray> Could somebody elaborate on it?
[16:10] <vorlon> why would you have a tab after a filename in a patch
[16:10] <vorlon> sorry
[16:10] <vorlon> why would you have content after a filename in a patch
[16:10] <cpete> why does the filename contain spaces?
[16:10] <vorlon> because it's legal
[16:11] <schopin> because patch(1) is weird that way?
[16:11] <bdmurray> even cpete is old enough to know don't use spaces in a filename
[16:11] <vorlon> I guell diff $oldfile $newfile means you have to have a delimeter
[16:11] <schopin> if you don't have the \t it won't be able to parse the filename correctly if it has spaces in it.
[16:11] <vorlon> oh you mean a filename with nothing after it except a magic \t ?!
[16:12] <schopin> Yes.
[16:12] <vorlon> and you ended up with a patch where you had to manually add this?
[16:12] <schopin> https://bugs.launchpad.net/ubuntu/+source/patch/+bug/862280
[16:12] -ubottu:#ubuntu-meeting- Launchpad bug 862280 in patch (Ubuntu) "Patch cannot handle spaces in filenames" [Undecided, Confirmed]
[16:12] <vorlon> hngh
[16:12] <juliank> OK um let's move on?
[16:12] <juliank> #topic Release incoming bugs
[16:12] <juliank> #link http://reports.qa.ubuntu.com/reports/rls-mgr/rls-nn-incoming-bug-tasks.html#foundations-bugs
[16:12] <schopin> Combine that with people using fancy editors that will remove trailing whitespace automatically...
[16:13] <bdmurray> Who would do that?
[16:13] <dbungert> sounds like a text editor bug
[16:13] <juliank> doko raised bug 2049686 and assigned it to the security team
[16:13] -ubottu:#ubuntu-meeting- Bug 2049686 in dpkg (Ubuntu) "dpkg-buildflags: emit build flags for negated features" [High, Confirmed] https://launchpad.net/bugs/2049686
[16:13] <juliank> I'm not sure why it's also tagged incoming
[16:14] <juliank> This seems like work we need to do and not the security team?
[16:15] <juliank> Well I pinged doko on the bug for more info
[16:15] <juliank> We can revisit it next week?
[16:15] <juliank> bug 1838372
[16:15] -ubottu:#ubuntu-meeting- Bug 1838372 in apport (Ubuntu) "'ubuntu-bug -w' doesn't work under wayland" [Wishlist, Triaged] https://launchpad.net/bugs/1838372
[16:16] <juliank> so we said this probably isn't possible under wayland but I don't think anyone had some spare time and interest to check?
[16:17] <schopin> We should probably create a spike card and untag.
[16:18] <juliank> creating one
[16:18] <juliank> FR-6347
[16:18] <vorlon> but also I don't think that's noble-critical
[16:19] <vorlon> or noble-realistic
[16:19] <juliank> it's also not targeted to noble, so I guess it's ok
[16:19] <juliank> And I dropped the tag
[16:20] <juliank> bug 2049529
[16:20] -ubottu:#ubuntu-meeting- Bug 2049529 in shadow (Ubuntu) "Extra ZFS-related log line with `useradd -m -R /path`" [Undecided, New] https://launchpad.net/bugs/2049529
[16:20] <juliank> I remember similar bug elsewhere (but don't remember where) and I believe we should probably fix that
[16:20] <vorlon> agree
[16:21] <juliank> targeted and tagged todo
[16:21] <Skia> that would be great! ♥
[16:21] <juliank> bug 2049540
[16:21] -ubottu:#ubuntu-meeting- Bug 2049540 in initramfs-tools (Ubuntu) "hundreds of differences in module list between initramfs-tools version 0.142ubuntu10 and version 0.142ubuntu11" [Undecided, New] https://launchpad.net/bugs/2049540
[16:22] <vorlon> yes
[16:22] <juliank> so yes, targeted and tagged todo
[16:22] <vorlon> dracut-install was meant to be a drop-in replacement for previous initramfs-tools behavior so this should be treated as critical
[16:23] <juliank> I'm setting importance to high
[16:23] <juliank> #link http://reports.qa.ubuntu.com/reports/rls-mgr/rls-mm-incoming-bug-tasks.html#foundations-bugs
[16:24] <juliank> We still only have bugs in the queue that are actually for desktop, so skipping
[16:24] <juliank> http://reports.qa.ubuntu.com/reports/rls-mgr/rls-jj-incoming-bug-tasks.html#foundations-bugs is empty
[16:24] <juliank> http://reports.qa.ubuntu.com/reports/rls-mgr/rls-ff-incoming-bug-tasks.html#foundations-bugs is empty
[16:24] <juliank> #topic Team proposed-migration report
[16:24] <juliank> #link https://ubuntu-archive-team.ubuntu.com/proposed-migration/update_excuses_by_team.html#foundations-bugs
[16:25] <adrien> I didn't finish libxcrypt (or libcryptx?) and ruby but it's in progress
[16:25] <danilogondolfo> browsers crashing in 3... 2... 1...
[16:25] <juliank> so vorlon I assigned I think 3 items last week in alphabetical order increasing, so we gotta kind of go backwards or something to make it fair :)
[16:25] <vorlon> heh
[16:25] <vorlon> well 2 weeks ago is the last time I assigned anything
[16:25] <vorlon> let's see here
[16:26] <dbungert> textmode browsers can give better results when the proposed-migration report gets this long
[16:26] <bdmurray> dbungert: a what?
[16:26] <adrien> heh, update_excuses_by_team seems to require much more memory than update_excuses
[16:26] <dbungert> bdmurray: like links or w3m
[16:27] <vorlon> python-werkzeug looks like last week was moved from slyon to pushkarnk
[16:27] <vorlon> pushkarnk: is this still in progress?
[16:27] <pushkarnk> vorlon: I have 2 MPs under review
[16:28] <vorlon> ok
[16:28] <vorlon> debconf is assigned to enr0n - you ok to keep that?
[16:29] <enr0n> vorlon: yes - I triggered a retry earlier in the week but never saw a result, so I tried again
[16:30] <vorlon> sorry, browser crashed (uh because of that page's memory usage probably), taking a minute to get back in order here
[16:31] <bdmurray> enr0n: and it was queued again when you retried it?
[16:31] <juliank> still need to sort out python-apt and apt it's a bit messy right now
[16:31] <enr0n> bdmurray: yes
[16:31] <vorlon> netplan.io vs wpa: ogayot was working on this and raised an MP against britney to badtest it which I rejected
[16:31] <vorlon> ogayot: are you still working on this?
[16:32] <ogayot> vorlon: yes, I'm still working on it, with slyon's help too
[16:32] <vorlon> ok
[16:32] <vorlon> libxcrypt: adrien: are you ok to keep this?
[16:33] <adrien> yeah
[16:33] <adrien> I solved it locally, I need to do an MR
[16:33] <vorlon> apt vs systemd: I don't see this one mentioned as currently assigned
[16:33] <vorlon> so I guess that brings us to the new stuff
[16:33] <adrien> btw, it's impacting ncurses too I think (it's purely in ruby, and everything ruby3.1 will fail)
[16:36] <vorlon> ok, apt vs systemd. enr0n you uploaded systemd, do you want to follow up on this or do you want someone else to take it?
[16:37] <vorlon> looks like there are a good number of autopkgtests needing sorted for systemd, not just apt
[16:37] <enr0n> vorlon: I am working on another systemd upload (real failures in systemd's tests), so yes consider that with me
[16:37] <vorlon> ok
[16:37] <vorlon> enr0n: I assume systemd-hwe is similar, since it's your upload and it's your autopkgtests that are failing
[16:38] <enr0n> vorlon: yes, systemd-hwe needs the new systemd
[16:38] <vorlon> but doesn't declare a versioned dependency on it?
[16:39] <juliank> heh I said the same thing but I don't remember wehre
[16:39] <vorlon> (if it needs the new systemd at runtime and you declare a versioned dependency for this the autopkgtests would just dtrt I think; and also it would dtrt on the user's system...)
[16:39] <vorlon> gnutls28, I'll take; just some autopkgtests to chase on ppc64el it looks like
[16:39] <schopin> Wouldn't the autopkgtests just end up with all-proposed?
[16:40] <vorlon> um and then the perl transition
[16:40] <vorlon> so I'm not going to try to dig through here to find things to assign out
[16:40] <juliank> heh
[16:40] <vorlon> juliank: back to you :)
[16:41] <enr0n> it's just for autopkgtest; the path to a test binary changed
[16:41] <juliank> I still am sorting out apt and python-apt, enr0n are you planning any ubuntu-release-upgrader upload?
[16:41] <vorlon> enr0n: ok
[16:41] <enr0n> juliank: no nothing planned at the moment
[16:41] <juliank> Otherwise I can go and upload a version that adapts to the new deb822 ordering changes in python-apt myself
[16:41] <juliank> ack
[16:41] <juliank> #topic AOB
[16:42] <tsimonq2> I know I'm not a part of this meeting, but https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/2039873 is something that's been going on for a while. My suggestion would be to ask Foundations to help. Either way, now you know. *bows back out*
[16:42] -ubottu:#ubuntu-meeting- Launchpad bug 2039873 in lxc (Ubuntu) "liblxc-dev was built with LXC_DEVEL=1 in Ubuntu 22.04 and later releases" [Undecided, Confirmed]
[16:42] <bdmurray> I'll be out tomorrow afternoon in case anyone notices
[16:42] <juliank> The lxc stuff is being discussed with server team
[16:42] <tsimonq2> <3
[16:43] <juliank> So deb822 ubuntu.sources will be relatively forcefully merged by python-apt and not very good at preserving local layout changes - if it can merge two paragraphs together, it will
[16:43] <juliank> You can give them separate comments and it won't
[16:44] <juliank> We need to revisit a deb822 native experience that is better at preserving layout, ultimately the experience would be worse with the current API without that level of merging
[16:45] <juliank> (because it needs to split up entries some times, and you then want them to not remain split if you undo your change, you know)
[16:45] <adrien> vorlon: I didn't have time to dig in the exim/gnutls one yet but it can/should be for me
[16:46] <adrien> (but I don't have a ppc64el machine which might be annoying for reproducing the issue)
[16:47] <vorlon> adrien: oh ok
[16:47] <juliank> Oh we've been silent for a minute, not counting vorlon's oh ok, so I guess we can call it
[16:47] <juliank> #endmeeting
[16:47] <meetingology> Meeting ended at 16:47:45 UTC.  Minutes at https://ubottu.com/meetingology/logs/ubuntu-meeting/2024/ubuntu-meeting.2024-01-18-16.01.moin.txt
[16:55] <pushkarnk> bfn \o
[17:03] <arraybolt3> sarnold: where did you vanish to :P the Matrix Council meeting is active


[11:44] <fiesh> so I created /etc/systemd/network/netplan-override.network.d/override.conf containing
[11:44] <fiesh> [Match]
[11:44] <fiesh> doesn't help :-(
[11:44] <fiesh> Name=*
[11:45] <fiesh> [Link]
[11:45] <fiesh> ActivationPolicy=always-up
[12:00] <fiesh> https://bugs.launchpad.net/ubuntu/+source/netplan.io/+bug/1928583
[12:01] <fiesh> honestly, I feel that the default behavior for static routes should be to survive carrier losses... sounds dangerous otherwise


[20:46] <RyanB94> hello
[20:46] <RyanB94> This is the Ubuntu Studio IRC Channel?
[20:46] <studio-user989> yes mai friend
[20:47] <RyanB94> thank you, just I tried
[20:47] <studio-user989> no problem, buddy. have a nice day
[20:47] <RyanB94> thank you see you soon.
[20:47] <RyanB94> @ChanServ
[20:50] <RyanB94> Is anybody there?
[20:52] <OvenWerks> where is there?
[20:52] <RyanB94> here, I said
[20:52] <RyanB94> Hi OvenWerks
[20:52] <RyanB94> I have a question
[20:53] <OvenWerks> Ask first :)
[20:54] <RyanB94> Do I need to use private drivers to have a nice performance with the programs like KDENLive or Pitivi?
[20:56] <aleb> What do you mean private drivers?
[20:56] <krytarik> Proprietary.
[21:23] <jedi__> hello
[21:32] <RyanB94> thank you guys
[21:32] <RyanB94> Linux Forever
[21:44] <OvenWerks> sorry guys I got called away after I got started...


[20:39] <MohamedAlaa98> Hello guys
[20:39] <MohamedAlaa98> ashams: hi
[20:40] <ashams> Hi MohamedAlaa98 :D
[20:40] <ashams> h r u doing?
[20:40] <MohamedAlaa98> Fine
[20:40] <MohamedAlaa98> and u?
[20:40] <ashams> fine, thnx God
[20:42] <MohamedAlaa98> Isn't there any meetings in the future
[20:43] <MohamedAlaa98> ?
[20:43] <ashams> yep, I'm sure there will be a meeting in the coming week or the one after isA
[20:43] <ashams> you mean on IRC?
[20:43] <MohamedAlaa98> yes
[20:43] <ashams> I can't say so, we need to have some thing to discuss to have a meting
[20:45] <MohamedAlaa98> ok, i'm waiting impatiently :D
[20:46] <ashams> I hope it'll be soon :D
[20:46] <MohamedAlaa98> ok, i'm still wating :D ,i'm very excited!
[20:47] <MohamedAlaa98> ok, i'm still waiting, i'm very excited!
[20:47] <MohamedAlaa98> ok, i'm still waiting, i'm very excited!
[20:47] <ashams> hahaha :D
[20:47] <ashams> you'll be posting it around 1 million times :P :D
[20:48] <sarhan> why just 1 million?
[20:48] <MohamedAlaa98> pidgin little bit hanging
[20:48] <ashams> well, I didn't like to say 2, but if you wish, it's ok
[20:48] <ashams> MohamedAlaa98, 2 million times ya man :P
[20:49] <MohamedAlaa98> elpidgin mehanig shewaya
[20:49] <MohamedAlaa98> mesh ana
[20:50] <ashams> ok, let's make it 3 :P
[20:53] <MohamedAlaa98> We have to make a meeting every week like other loco teams.
[20:54] <MohamedAlaa98> do you agree with me?
[20:54] <ashams> yes, totally
[20:55] <ashams> maybe, we can make sections
[20:55] <MohamedAlaa98> how?
[20:55] <ashams> like: ubuntu-eg updates, community updates, latest activity or proposals and so on
[20:58] <MohamedAlaa98> Hmmmm, nice idea
[20:58] <ashams> do you want ti suggest it to the mailing list?
[20:58] <ashams> it*
[20:59] <MohamedAlaa98> sure!
[21:00] <ashams> cool, thanks :D
[21:00] <MohamedAlaa98> but it's yours
[21:00] <MohamedAlaa98> ?
[21:00] <ashams> no man, it's yours, you suggested the meeting
[21:01] <ashams> I'm just your wing man :D
[21:04] <MohamedAlaa98> sorry, pidgin exited unexpectedly
[21:04] <ashams> not a problem :D
[21:04] <MohamedAlaa98> did you write something?
[21:05] <ashams> nope
[21:05] <ashams> :)
[21:06] <MohamedAlaa98> you was talking about suggesting sections on mailing list
[21:07] <MohamedAlaa98> do you want me to suggest this
[21:09] <MohamedAlaa98> hello?
[21:40] <ashams> MohamedAlaa98, hey, sorry, I was away
[21:40] <ashams> yes, I hope you can
[21:40] <MohamedAlaa98> np :)
[21:40] <MohamedAlaa98> ok
[21:42] <MohamedAlaa98> have you read this page before? http://en.windows7sins.org/
[21:42] <ashams> yep, I guess so
[21:42] <ashams> It's gr8 by all means :D
[21:43] <MohamedAlaa98> cool isn't ?
[21:43] <ashams> sure
[21:43] <ashams> it's like amovement from FSF
[21:44] <MohamedAlaa98> I've received it by mail
[21:44] <MohamedAlaa98> yes
[21:44] <ashams> cool


[02:05] <head_victim> blahdeblah & other Brisbanites : just thought I'd let you know I went into to humbug yesterday afternoon for the first time ever. I wasn't there long really only went to drop off the CDs for use in O week this week at the uni. I have given them a bit of an intro to what we are and what we do and they were even willing to put the team business cards into the CD sleeves. They are interested in collaboration with other Unix/Linux grou
[02:05] <head_victim> ps in the area as well so I was thinking we should organise a Ubuntu-AU envoy there one meeting and give a short presentation on who we are and what we do and how best to work together.
[02:09] <Phlosten> an envoy? sounds all UN like
[02:11] <head_victim> Phlosten: Heh well before I went there last night their previous efforts were directed towards a previous team member who didn't really offer much assistance.
[03:42] <gggs> my fat32 partition seems to change its name every time I reboot, breaking my symlinks, any way to stop it?
[03:44] <dns53> you mounting it by uuid or device name?
[03:47] <gggs> gnome (auto); I just select `85GB filesystem' and it mounts
[03:49] <gggs> should I add it to /etc/fstab ?
[03:52] <dns53> probably, use blkid to find a uuid and use that to mount your partition
[04:02] <gggs> if it's already mounted, can I take the mount config & give it a permanent descriptor?
[04:20] <dns53> well you just add another entry to your /ect/fstab,       UUID=b8c1b682-1acf-4403-be2b-de549ea14f03 /mountpoint vfat defaults 0 0    and that should automatically mount it on boot
[04:23] <gggs> oh thanks, I'm reading through the fstab manpage now
[04:24] <gggs> must've been an issue with a changing label & therefore different mountpoints
[04:25] <dns53> well you could use LABEL=xxxx instead but uuid works better as it is more likely to be unique
[04:26] <gggs> would the UUID change if I resized the partition?
[04:26] <dns53> it would
[04:29] <gggs> ah, then that'd be why
[04:41] <gggs> nice, mounted to the right place! one last question on fstab, my mount options are "rw,nosuid,nodev,uhelper=udisks,uid=1000,gid=1000,shortname=mixed,dmask=0077,utf8=1,flush", do I need the uhelper/flush/* options
[04:44] <gggs> seems rather complex for an old & simple fs like FAT
[04:47] <dns53> well you are setting the user id and file permissions, you might not need the flush options
[04:51] <gggs> mount manpage says flush `will try to flush the disk more early than normal' (?), nothing in there about nodev, uhelper, or shortname
[04:57] <dns53> shortname is a vfat option, originally you could only have 8 + 3 character file names so they added 255 character file names to windows 95, probably not needed as an option as it should be the default
[04:59] <dns53> flush suggests not to buffer things into memory, probably safer but if you shut down things normally it does not matter
[05:06] <gggs> ok, thanks


[17:46] <rzr> hi
[17:46] <rzr> look for this device : http://linuxdevices.com/news/NS9710143183.html


[00:03] <liveuser> Has anyone looked at http:.//www.kubuntu.org recently?
[00:07] <shadeslayer> liveuser: whats the issue?
[00:09] <yofel> is it me or is that download button HUGE
[00:09] <yofel> and misaligned
[00:10] <shadeslayer> well ... there's some weird issue with CSS
[00:10] <shadeslayer> and there's no way we can align it
[00:10] <shadeslayer> or, lemme ask someone who might know how to fix it
[00:11] <yofel> sure, I'm clueless how one edits that
[00:11] <shadeslayer> i've already talked to Riddell about this before
[00:11] <shadeslayer> when we had the 10.10 download banner
[00:12] <shadeslayer> it was misaligned then as well
[00:13] <yofel> was the banner always that large? I rarely look at the front page
[00:14] <shadeslayer> nope
[00:14] <shadeslayer> well
[00:14] <shadeslayer> the banner itself is large this time
[00:16] <yofel> shadeslayer: why do I get the feeling this doesn't look good: http://people.ubuntu.com/~yofel/pics/drupal.png
[00:17] <shadeslayer> uh
[00:17] <shadeslayer> 0.o
[00:17] <shadeslayer> i have no idea what that means for us
[00:17] <shadeslayer> ->drupal n00b
[00:18] <yofel> me neither
[00:18] <yofel> that's why I don't want to do more than look at it...
[00:18] <shadeslayer> heh
[00:24] <shadeslayer> btw, i think we should release this as a SRU : https://projects.kde.org/projects/kde/kdelibs/repository/revisions/3bbd4496bc8a01e80df61763bfd0347e8ba7f09a/diff
[00:24] <shadeslayer> imo its a important security fix
[00:28] <yofel> ack from me at least
[00:33] <shadeslayer> ScottK: apachelogger https://projects.kde.org/projects/kde/kdelibs/repository/revisions/3bbd4496bc8a01e80df61763bfd0347e8ba7f09a/diff << SRU'able ?
[00:40] <ScottK> shadeslayer: SRU or security update.  Not sure which.  I bet micahg has an opinion.
[00:40] <shadeslayer> alright
[00:41] <shadeslayer> heh, its a miracle this even came to my attention :P
[00:42] <shadeslayer> if its a security update, it'll be better to update packager as well
[00:51] <liveuser> shadeslayer: fixed I guess. When I went there is just said OK
[00:51] <shadeslayer> liveuser: what was the issue anyways?
[00:51] <shadeslayer> s/it'll/i'll
[01:00] <liveuser> shadeslayer: There was no page. Just a plain file that said ok
[01:00] <shadeslayer> heh
[01:01] <liveuser> ok guess that's cool now
[01:11] <micahg> ScottK: shadeslayer: IMHO, that's a security enhancement, not a vulnerability, so it wouldn't qualify for -security, but you can ask mdeslaur in the morning to be sure
[01:12] <shadeslayer> micahg: where can we find him?
[01:12] <shadeslayer> ubuntu-devel ?
[01:12] <micahg> shadeslayer: #ubuntu-hardened after 12:30 UTC
[01:12] <shadeslayer> alright
[01:12]  * shadeslayer idles
[05:27] <shadeslayer> apachelogger: ping ping ping
[05:51] <shadeslayer> yofel: poke
[07:14] <seaLne> has anyone seen gimp seg faulting on kubuntu but not apparently on ubuntu?
[07:14] <seaLne> in natty
[07:16] <ulysses> seaLne: change the GTK theme in the System Settings, not the oxygen-gtk
[07:18] <shadeslayer> seaLne: yes
[07:18] <shadeslayer> seaLne: apachelogger has the bug iirc
[07:18] <shadeslayer> but me and yofel can't reproduce it for some reason
[07:20] <seaLne> great thanks
[07:53] <bulldog98> has someone tested the packages in kubuntu-ppa/staging? (oneiric)
[08:24] <yofel> morning
[08:24] <yofel> shadeslayer: pong
[08:24] <shadeslayer> yofel: i haz CSS fixes for kubuntu.org
[08:24] <shadeslayer> any ideas how to apply?
[08:25] <shadeslayer> i kept searching for quite a bit, can't figure out where to applu
[08:25] <shadeslayer> *apply
[08:25] <shadeslayer> oh and i'm sleep deprived so i'm a bit scared to meddle around on the website
[08:26] <yofel> nope, I'm clueless about how to edit the frontpage
[08:27] <shadeslayer> here's the fixed HTML : http://paste.kde.org/81919/
[08:33] <yofel> shadeslayer: which parts did you edit?
[08:34] <yofel> oh, finally found the front page html
[08:38] <shadeslayer> yofel: just run a diff xD
[08:39] <shadeslayer> and it-s fixed up the CSS
[08:44] <yofel> ok, let's see...
[08:47] <shadeslayer> basically fix div id frontpage-promo, div class frontpage-text iirc
[08:49] <yofel> right, I had the get the full source though since drupal changes the formatting of the page source when showing it :/
[08:50] <shadeslayer> @_@
[08:50] <yofel> so I had a huge diff at first
[08:50] <yofel> anyway, applied
[08:50] <yofel> looks better
[08:50] <shadeslayer> where did you fix it?
[08:51] <shadeslayer> looks better indeed
[08:52] <valorie> yay!
[08:53] <valorie> thanks, you two
[08:53] <shadeslayer> yofel: dude, where did you commit it?
[08:53] <shadeslayer> could use with a bit of fixing tho
[08:54] <yofel> you go to administer -> content management -> content, then somewhere in the list you'll find the Homepage and can edit it
[08:55] <yofel> drupal is confusing...
[09:26] <yofel> bbl
[10:10]  * bulldog98 just found an mistake in kdepim packaging (fixing that now)
[10:12] <bulldog98> I put a lib into to packages, which isn’t going to work
[10:15] <jussi> whoops :D
[10:16] <bulldog98> jussi: jea and I found 3 others in that package, too good that the version number was 0ubuntu0~ppa5
[10:18]  * bulldog98 lets launchpad build a corrected version. Could someone please verify that it’s ok, since I need quite long to download the packages
[10:23] <sheytan> bulldog98 will you make a ppa with 4.6 pim for natty?:)
[10:25] <bulldog98> sheytan: runtime is already in staging
[10:25] <bulldog98> for natty
[10:25] <bulldog98> I need to verify, that kdepim’s ok to install, then I’ll bump the version number to 0ubuntu1~ppa1 and backport it to natty
[10:26] <sheytan> ok, thanks :)
[10:27] <bulldog98> sheytan: If you could try to install kdepim in an oneiric pbuilder if you have sufficent internet connection speed I’d be glad, cause I have 56 kB/s
[10:27] <bulldog98> currently it’s still building
[10:29] <sheytan> bulldog98 Sorry, i'm at work on winshit
[10:30] <bulldog98> sheytan: ok no problem
[10:31]  * bulldog98 ’ll push natty packages now, if they arenot installable I’ll update them later
[10:46] <apachelogger> what what
[10:46] <apachelogger> do we have kdepim yet? ^^
[10:47] <bulldog98> apachelogger: we have it in staging, but we need to test that (install wise)
[10:48] <apachelogger> scary
[10:48] <apachelogger> bulldog98: kubuntu-ppa/staging?
[10:48] <bulldog98> apachelogger: yes
[10:48] <bulldog98> runtime is ok, but I need to test the kdepim package, if there are override conflicts
[10:49] <apachelogger> bulldog98: for natty?
[10:49] <bulldog98> apachelogger: oneiric and natty are building atm
[10:49] <apachelogger> bleh
[10:49]  * apachelogger wants to test :P
[10:50] <bulldog98> apachelogger: https://launchpad.net/~kubuntu-ppa/+archive/staging/+build/2567472
[10:51] <apachelogger> that is going to take forever
[10:52] <bulldog98> oneiric build at 86%
[10:52] <bulldog98> apachelogger: about 1h
[10:54]  * apachelogger builds kdelibs on arm
[10:54] <bulldog98> apachelogger: natty needs longer, I have to fix a dependency
[10:54] <apachelogger> meh
[10:55] <bulldog98> why isn’t kde-sc-dev-latest 4.6.3 avaidable for staging?
[10:55] <apachelogger> cause natty shipped with .2
[10:56] <bulldog98> apachelogger: is updates enabled in backports (kubuntu-ppas)?
[10:59]  * bulldog98 now has to upload a new backport
[11:00] <wstephenson> hi. what is the name of the xz package on kubuntu?
[11:01] <bulldog98> shadeslayer: btw why have you set kde-sc-dev-latest to 4.6.3 in kdepim?
[11:01] <wstephenson> a user is getting "dpkg-deb (subprocess): unable to execute data (xz): No such file or directory" so i want to make sure that xz is present
[11:01] <bulldog98> !search xz
[11:01] <bulldog98> !info xz
[11:02] <wstephenson> does kubuntu have a command-not-found tool that knows which package it is in?
[11:02] <Tm_T> ye, should have
[11:02] <bulldog98> !info xz-utils
[11:02] <wstephenson> bingo, thanks
[11:03] <bulldog98> wstephenson: apt-cache search helps :)
[11:03] <Tm_T> wajig search <3
[11:03] <wstephenson> bulldog98: i don't have kubuntu booted atm, just replying to a mail.
[11:03] <bulldog98> wstephenson: ok that’s a point for you :)
[11:04] <Tm_T> wstephenson: and hi, long time no see
[11:05] <bulldog98> apachelogger: are you on natty?
[11:06] <wstephenson> hi Tm_T :)
[11:08] <wstephenson> bulldog98: the OBS builds packages for various kubuntu versions, but as the basic packages of a distribution evolve, we have to keep the OBS config up to date, by adding eg xz-utils to be able to install build requirements compressed using it.
[11:09] <bulldog98> wstephenson: ah ok that sounds good
[11:09] <bulldog98> apachelogger: why does dh_shlibdeps takes that long?
[11:10] <wstephenson> ok, cheerio
[11:21] <bulldog98> apachelogger: should I copy the kdepim-runtime stuff over to backports now?
[11:39] <apachelogger> bulldog98: experimental first
[11:40] <apachelogger> IMHO
[11:40] <apachelogger> also needs more testing
[11:40] <apachelogger> more more more more testing
[11:41] <shadeslayer> hey apachelogger
[11:41] <shadeslayer> apachelogger: have you heard of the HP Touchpad?
[11:42] <shadeslayer> from my preliminary inspection, it looks like a) webos has root access , b) we can dual boot OS's with webos
[11:42] <shadeslayer> http://www.webos-internals.org/wiki/Main_Page << loads of info here
[11:44] <apachelogger> dubdubdub
[11:44] <apachelogger> ole!
[11:44] <shadeslayer> i'm going to download the new SDK
[11:45] <shadeslayer> or the current SDK that is
[11:45] <shadeslayer> and poke around the emulator
[11:45] <bulldog98> apachelogger: runtime building in experimental
[11:45] <shadeslayer> apachelogger: http://www.precentral.net/webos-and-shr-dual-booted-pre
[11:47] <bulldog98> apachelogger: if a libary moved from one package to an other, do I have to set Replaces or Conflicts?
[11:49] <apachelogger> yes
[11:49] <debfx> bulldog98: Replaces and Breaks
[11:49] <bulldog98> ok thanks
[11:50] <bulldog98> <= 4..5.96 or << 4.5.96 ?
[11:53] <bulldog98> if version 4.5.96-0ubuntu0~ppa1 breaks?
[11:53] <bulldog98> debfx, apachelogger: ?
[11:54] <debfx> bulldog98: << 4.5.96
[11:54] <debfx> though if it has an epoch you need to include it
[11:54] <bulldog98> debfx: ok thanks
[11:54] <bulldog98> debfx: that’s clear
[12:09] <didrocks> hey, can I got access to ~kubuntu-ppa ? I want to update qt-at-spi in the experimental ppa before pushing to oneiric.
[12:12] <apachelogger> you should become kubuntu-dev/member/ninja :P
[12:13] <apachelogger> oh, nice, jr is only superlord of kubuntu-ppa
[12:13] <apachelogger> #mgmtfail
[12:13] <apachelogger> didrocks: you are now ninja, thus should have access to the ppa
[12:15] <bulldog98> !help ninjas
[12:15] <bulldog98> rotf
[12:18] <shadeslayer> ^_^
[12:18] <didrocks> apachelogger: \o/ excellent, thanks a lot :)
[12:18] <shadeslayer> you probably need !ninjas or ~ninjas
[12:18] <bulldog98> !ninjas
[12:18] <bulldog98> ok that works
[12:19] <shadeslayer> now why do you need them ninjas?
[12:19] <didrocks> just waiting for next refresh so that the bot can see me? :)
[12:19] <bulldog98> apachelogger, bulldog98, debfx, JontheEchidna, Lex79, maco, neversfelde, nhandler, Quintasan, rgreening, Riddell, ScottK, stalcup, txwikinger, yofel: sorry guys was just a test
[12:19] <bulldog98> didrocks: I think that is handled manualy
[12:19] <shadeslayer> didrocks: nah, its handled manually
[12:19] <shadeslayer> also
[12:19] <didrocks> oh ok :)
[12:19] <shadeslayer> apachelogger: am i not a ninja anymore? :(
[12:20] <debfx> oh please someone exclude me from the spamming list
[12:20] <shadeslayer> hehe
[12:20] <shadeslayer> debfx: oh btw : https://projects.kde.org/projects/kde/kdelibs/repository/revisions/3bbd4496bc8a01e80df61763bfd0347e8ba7f09a/diff : might be important
[12:20] <apachelogger> shadeslayer: no, dunno, how would I know?
[12:20]  * shadeslayer is trying to figure out if that should go into security or updates
[12:21] <shadeslayer> apachelogger: ubottu doesn't think i'm a ninja
[12:21] <bulldog98> apachelogger: the builds for kdepim are ready (alrought it will complain of override)
[12:21] <didrocks> so, the new qt-at-spi is still quite crashy (seems to need to backport some qt patches from 4.8), but at least, the basics work :)
[12:21] <shadeslayer> bulldog98: iirc the bump for kde-sc-dev was probably in debian, but i don't really remember
[12:21] <didrocks> but still better in an experimental ppa for now
[12:22] <apachelogger> brr
[12:22] <bulldog98> shadeslayer: could be
[12:22] <apachelogger> icecream could do with some improvements
[12:22] <apachelogger> WRT xcompiling
[12:22] <apachelogger> there is pita all around
[12:22] <shadeslayer> maybe i should sleep now
[12:23] <shadeslayer> i've been up for 52 hours
[12:23] <bulldog98> apachelogger: in fact I never got icecream running properly
[12:23] <bulldog98> shadeslayer: defently you need sleep
[12:23] <shadeslayer> bulldog98: the only problem being, i can't sleep
[12:23] <shadeslayer> i'm not sleepy
[12:24] <bulldog98> shadeslayer: I haven’t really sleeped yesterday (trough doing kdepim stuff) :)
[12:24] <shadeslayer> bulldog98: at times i also sleep for 18 hours at a stretch
[12:24] <shadeslayer> yeah KDE PIM is a pita
[12:24] <bulldog98> ok
[12:24] <bulldog98> shadeslayer: it should be splitted up into smaller parts, so it’s easier to build
[12:25] <shadeslayer> you mean like seprate tarball for kmail/etc etc
[12:25] <bulldog98> shadeslayer: yes
[12:25] <shadeslayer> ah
[12:25] <shadeslayer> agreed
[12:25] <didrocks> shadeslayer: you are accumulating sleep need for more efficient and longer days? :-)
[12:25] <bulldog98> that would be awesome
[12:25] <shadeslayer> it's too big
[12:25] <shadeslayer> didrocks: lol
[12:25] <apachelogger> bulldog98: did you backport akonadi for natty?
[12:25] <apachelogger> cause I really think you should
[12:26] <bulldog98> apachelogger: no haven’t done that
[12:27] <bulldog98> but I’m doing that atm
[12:28] <bulldog98> !info mysql-server-core-5.1
[12:29] <bulldog98> apachelogger: pushed that to staging
[12:37]  * shadeslayer puts his SRU hat on
[12:37] <shadeslayer> debfx: i'm going to SRU this for ubuntu : https://projects.kde.org/projects/kde/kdelibs/repository/revisions/3bbd4496bc8a01e80df61763bfd0347e8ba7f09a/diff
[12:37] <shadeslayer> maybe debian would want it too
[12:38] <bulldog98> shadeslayer: oneiric, too?
[12:38] <shadeslayer> not needed
[12:38] <shadeslayer> bulldog98: its fixed in 4.7
[12:38] <shadeslayer> oh wait
[12:38] <shadeslayer> it needs to be in oneiric first
[12:39] <shadeslayer> only then can it go into natty
[12:39] <shadeslayer> well ... 4.7 is going to take time
[12:39] <debfx> shadeslayer: why hasn't upstream backported it to 4.6?
[12:40] <shadeslayer> dunno
[12:40] <debfx> hm the new string might be a problem
[12:41] <bulldog98> debfx: yes it’s gone be a problem, cause the is a langpack update going on
[12:41] <shadeslayer> hmmm
[12:41] <shadeslayer> debfx: how do i handle this then?
[12:41] <shadeslayer> imo its a important security enhancement
[12:42] <bulldog98> shadeslayer: ask in<EMAIL_ADDRESS>for a string exeption an backport it to 4.6
[12:43] <shadeslayer> ok
[12:44] <debfx> I'd get in contact with the committer, maybe he already has plans to backport it
[12:44] <bulldog98> oh right that’s the other thing I forgot to mention :)
[12:44] <shadeslayer> yeah i'm CC'ing him in the mail
[12:45] <shadeslayer> or should i just contact the committer first?
[12:46] <shadeslayer> oh
[12:46] <bulldog98> shadeslayer: maybe you should contact him first in private about that
[12:46] <shadeslayer>     CCMAIL<EMAIL_ADDRESS>[12:46] <shadeslayer> it's already been CC'd
[12:46] <shadeslayer> but i guess thats for KDE 4.7 ?
[12:46] <bulldog98> shadeslayer: when was that commited?
[12:47] <shadeslayer> "Added by Dawit Alemayehu 19 days ago"
[12:47] <shadeslayer> https://projects.kde.org/projects/kde/kdelibs/repository/revisions/3bbd4496bc8a01e80df61763bfd0347e8ba7f09a/ << here you go
[12:48] <bulldog98> shadeslayer: there was no following up mails
[12:49] <bulldog98> but that was for 4.7 were only soft string freeze is in place
[12:49] <shadeslayer> hmm
[12:49] <bulldog98> for 4.6 there is hard string freeze
[12:50] <bulldog98> only what is essential is being added (= nearly nothing will got added)
[12:50] <shadeslayer> yeah
[12:52] <bulldog98> shadeslayer: but there can’t happen more than saing no to it
[12:52] <bulldog98> !info plasma-widget-networkmanagement
[12:54] <shadeslayer> bulldog98: sorry what?
[12:54] <bulldog98> shadeslayer: they can’t do more to you than saying no, you don’t get this permission
[12:56] <shadeslayer> bulldog98: right, so i'll send a mail to the l18n team asking for a exception
[12:56] <shadeslayer> or rather committer first
[12:58] <bulldog98> shadeslayer: first to the commiter to ask him what he thinks about that
[12:58] <shadeslayer> yeah
[13:01] <shadeslayer> done
[13:01] <shadeslayer> ok i'm sleeping now
[13:01] <shadeslayer> cya
[13:03] <yofel> re
[13:16]  * bulldog98_konver got an kernel error (nice null pointer)
[13:17]  * Quintasan calls freescale
[13:19]  * jussi crosses fingers for Quintasan
[13:20]  * yofel will probably wait for pandaboards to become available again
[13:20]  * jussi likes freescale
[13:21]  * jussi wonders how long before some one messes up the pattern
[13:22]  * yofel too ^^
[13:25]  * yofel wonders in the meanwhile what he did wrong with smokegen. Builds fine with cmak&make, but is FTBFS with dpkg-buildpackage
[13:26]  * jussi thinks yofel may be missing a dep in the control file perhaps?
[13:27]  * yofel doesn't think so, this is dpkg-buildpackage, not pbuilder
[13:28]  * yofel builds without library-packages.mk
[13:28]  * jussi says oh...
[13:28]  * jussi now has no idea
[13:41]  * yofel found the culprit: debian-qt-kde.mk, is confused and out of battery. BBL
[13:42]  * jussi hi 5's yofel
[13:44] <bulldog98> http://postimage.org/image/i5z7vbhg/de85831c/ kernel-error
[13:48] <bulldog98_konver> nice btrfs is broken in oneiric
[13:50] <bulldog98_konver> s/broken/my partions/
[13:50] <kubotu> bulldog98_konver meant: "nice btrfs is my partions in oneiric"
[14:24] <Quintasan> jussi: lol, the lady assured me I will have response today
[14:24]  * Quintasan waits
[14:25]  * apachelogger missed out on a great /me run :(
[14:34] <Quintasan> lol
[14:36] <Quintasan> We shall have Gluon in both in Debian and Ubuntu soon
[14:37] <Quintasan> That means, some awesum games for KDE
[14:40] <apachelogger> bulldog98_konver: kdepim looks fine except for the overwrite error
[14:45] <yofel> \o/
[14:45] <yofel> Quintasan: did someone write pong for it yet? :P
[14:46] <Quintasan> yofel: pong for what?
[14:47] <yofel> Quintasan: pong using gluon?
[14:48] <Quintasan> no idea
[14:48]  * apachelogger notes that there is quite the lack of pong clones
[14:48] <apachelogger> especially ascii only
[14:51] <Quintasan> yofel: there is :D
[14:51] <Tonio_> hey there :)
[14:52] <Tonio_> agateau: you there ?
[14:52] <yofel> then cool :)
[14:52]  * yofel goes back fighting smoke
[14:52] <agateau> Tonio_: yup, hi!
[14:52]  * Quintasan hugs Tonio_
[15:03] <yofel> great, #kubuntu -> kdegraphics 4.6.4 ships okular 0.12.1 which should be 0.12.4
[15:03] <yofel> wth is dirk doing...
[15:05] <bulldog98_konver> apachelogger: that should be fixed with ~ppa7
[15:12] <bulldog98_konver> yofel: great have you wrote a mail to kde-packagers?
[15:12] <yofel> no, was about to do that in a few mins
[15:13] <yofel> this git conversion is messing everything up...
[15:13] <Tonio_> hey agateau :)
[15:13] <Tonio_> I was wondering about the patches you wrote for kopete and konversation notification...
[15:13] <shadeslayer> indeed
[15:13] <Tonio_> when I close kopete window, it stays open and I have to file/quit to quit
[15:14] <Tonio_> that seems normal
[15:14] <Tonio_> konversation doesn't work the same way... is that on purpose ?
[15:14] <apachelogger> yofel: I actually blame dirk for not being on top of his game
[15:14] <Tonio_> I think konversation/any irc client, should stick in the same place, the same way an instant messaging does right ?
[15:14] <agateau> Tonio_: mmm that's old... I don't remember
[15:14] <Tonio_> hey Quintasan :)
[15:14] <Tonio_> agateau: okay... I'll look at your patches then
[15:15] <Quintasan> apachelogger: We are officialy loved by Calligra
[15:15] <Quintasan> and you should get Pong in Gluon some time soon
[15:15] <apachelogger> Quintasan: where is the love?
[15:15] <apachelogger> also do we have a snapshot build of calligra yet?
[15:15] <Quintasan> cookies at Akademy
[15:15]  * Quintasan looks at shadeslayer for snapshot
[15:15] <agateau> Tonio_: I think what happened is that support for message menu in Konversation did not involve messing with quit-vs-close like in Kopete, so I didn't change the close behavior
[15:16]  * agateau wonders if his sentence makes sense
[15:16] <yofel> apachelogger: _Groo_ was doing something for natty, ping him when you see him
[15:16] <apachelogger> shadeslayer: awaken my warrior, there is work to be done!
[15:16] <Quintasan> lol
[15:16] <yofel> lol, you just missed him ^^
[15:17] <apachelogger> yofel: perhaps I should make him a true minion
[15:17]  * apachelogger has too many mails
[15:17] <Quintasan> apachelogger: Do you know whether that magical patch that broke pressure support in Qt is there or not?
[15:17] <apachelogger> should still be there
[15:18] <Quintasan> hmm
[15:18] <apachelogger> targeted for alpha2 IIRC
[15:18] <apachelogger> reminds me that I should patchy patchy in upstream KDE
[15:18] <apachelogger> cripple phonon in KDE a bit
[15:18] <Quintasan> so it is bokred right now?
[15:18] <apachelogger> Quintasan: yes
[15:18] <Quintasan> crapz
[15:18] <apachelogger> y u ask?
[15:19] <Quintasan> apparently pressure support in Krita from Calligra doesn't work
[15:19] <Quintasan> We are building against kde-qt
[15:19] <Quintasan> That's the strangest thing
[15:19] <apachelogger> Quintasan: in neonz?
[15:20] <Quintasan> yes
[15:20] <Quintasan> magic
[15:20] <apachelogger> are you sure it loads the right Qt?
[15:20] <Quintasan> I asked for the mentioned user to join us in #project-neon and tell us how is he running it
[15:20] <apachelogger> also someone should try to get some wacom thingies sponsored we can QA that stuff actually
[15:21] <Quintasan> I have a Wacom tablet right here
[15:21] <apachelogger> Quintasan: pmap `pidof krita` | grep Qt
[15:21] <Quintasan> yofel: got a pn install?
[15:21] <yofel> yes
[15:21] <apachelogger> Quintasan: you just made yourself official Qt wacom QA lead
[15:21] <apachelogger> congrats
[15:21] <Quintasan> can you try what apachelogger said?
[15:23] <yofel> hm, krita does stupid things when being run from my normal session, let me start a VM
[15:24] <Quintasan> yofel: using Virtual Box?
[15:24] <apachelogger> export KDEHOME=$HOME/.project-neon-kde/
[15:24] <apachelogger> are you not patching kdelibs?
[15:24] <yofel> yes
[15:24] <Quintasan> yofel: Did you get the guest-additions grp. driver to work?
[15:24] <apachelogger> yes you are not or yes you are? ^^
[15:24] <yofel> apachelogger: we do build with -DKDE_DEFAULT_HOME=~/.project-neon-kde (or how that option was called)
[15:25] <apachelogger> hm, that var seems overly useless then :P
[15:25] <apachelogger> are you rpathing neon?
[15:25] <yofel> latter I don't think we do
[15:25] <yofel> more like I don't know enough about rpath
[15:25] <apachelogger> IMHO you should
[15:25] <yofel> need to read cmake docs
[15:26]  * yofel has the page open in a ffx tab actually
[15:26] <yofel> too much todo -.-
[15:26] <apachelogger> should be one command with cmake
[15:26] <apachelogger> actually IIRC cmake by default rpaths ^^
[15:26] <Quintasan> it does
[15:26] <ScottK> Do we have something like http://blog.gokmengoksel.com/2011/06/quickformat-–-an-exciting-removable-disk-formatter-for-pardus/ ?
[15:26] <Quintasan> and rpathing manually in CMake does some strange things if you don't know how to do it
[15:27] <Quintasan> ScottK: I tried to package it, then I tried to install it manually
[15:27] <Quintasan> it didn't show up
[15:27] <apachelogger> Quintasan: is it pyth0rn?
[15:27] <apachelogger> ScottK: no we do not
[15:27] <Quintasan> most likely
[15:27] <ScottK> Probably since it's Pardus.
[15:27] <apachelogger> Quintasan: plz check
[15:28] <ScottK> Someone should go talk to the Pardus dudes and help them get this upstream.
[15:28] <apachelogger> ScottK: solution: create one upstream and bash pardus for not doing upstream work
[15:28] <ScottK> I'd rather convince them to push it upstream.
[15:28] <ScottK> Pardus has done some interesting things and it'd be great to get them pushing stuff more upstream.
[15:30]  * apachelogger can live without overly fat script language utils with a use/fatness ratio that makes you wonder "why"
[15:40] <ScottK> apachelogger: You wanted armel PPAs: getting there - http://dmtechtalk.wordpress.com/2011/06/14/135/
[15:55] <bulldog98_konver> why is the kubuntu.org/support/deutsch broken?
[16:02] <afiestas> ScottK: I already talked with some people from there and since then I can say that they've improve the communication towards upstream
[16:03] <afiestas> I'm still not happy about it, but a step is a step :p
[16:03] <Quintasan> afiestas: Great. Now we get more awesome in KDE
[16:03] <Quintasan> afiestas: Would you help us getting plasma-contour in Neon at some point?
[16:07] <afiestas> I can help, yes, though right now I don't have it setup in my laptop
[16:07] <afiestas> to ahve contour in Neon you will have to invest time each week, since it changes each week
[16:08] <Quintasan> no hurry, I'm pretty busy right now
[16:08]  * Quintasan disappears for and hour or two
[16:09] <bulldog98_konver> yeah btrfsck works
[16:11] <yofel> doesn't fix anything though
[16:11] <bulldog98_konver> yofel: it did
[16:12] <yofel> then whatever you had wasn't really an inconsisten FS
[16:12] <yofel> the btrfsck in the archive changes nothing in the FS
[16:12] <yofel> and the one that does is still COMING SOON™
[16:13] <bulldog98_konver> yofel: it gave me a kernel null pointer, so I guess it was a corrupt
[16:13] <yofel> the trace you showed? wasn't that from nouveau?
[16:14] <bulldog98_konver> yofel: after I restarted there was one by btrfs
[16:14] <yofel> although kernel null pointer would be a btrfs.ko but
[16:14] <yofel> hm, dunno, I do have an image of an oopsing btrfs lying around here, not fixable with current btrfsck
[16:16] <bulldog98_konver> yofel: maybe it has changed with linux 3.0-0 in archive?
[16:17] <yofel> hm, could try that right, I reported the oops during 2.6.39
[16:18] <ScottK> afiestas: Good to hear.
[16:26] <yofel> bulldog98_konver: why does kdepim-runtime-dbg Breaks/Replaces kdepim-dbg?
[16:27] <bulldog98_konver> yofel: what
[16:27] <apachelogger> yofel: library move?
[16:27] <yofel> I'm talking about -dbg, and the problem is that it's unversioned
[16:27] <yofel>  39 Replaces: kdepim-dbg
[16:27] <yofel>  40 Breaks: kdepim-dbg
[16:28] <apachelogger> fun
[16:28] <yofel> now it wants to remove one when I try to upgrade to 4.6.0
[16:29] <bulldog98_konver> hm haven’t noticed that
[16:30]  * bulldog98_konver is going to fix that
[16:31] <yofel> should be << 4.6~ or so
[16:33] <bulldog98_konver> yofel: I took 4:4.5.96, cause there we moved that stuff
[16:34] <yofel> ah, that has 'Replaces: kdepim-dbg', still wrong, but harmless because it's missing the 'Breaks'
[16:35] <yofel> both should be versioned
[16:36] <bulldog98_konver> yofel: I versioned both now
[16:36] <yofel> then good :)
[16:36] <bulldog98_konver> yofel: had that even done before you sad me that :)
[16:36] <yofel> ^^
[16:37] <bulldog98_konver> Is the kdepim stuff ok?
[16:38] <yofel> hm, I aborted the upgrade just now due to the conflict, let me do it anyway
[16:39] <bulldog98_konver> yofel: wait ~10min an it’ll work
[16:41] <yofel> dpkg: error processing /var/cache/apt/archives/libkdepimdbusinterfaces4_4%3a4.6.0-0ubuntu0~ppa7_amd64.deb (--unpack):
[16:41] <yofel>  trying to overwrite '/usr/lib/libkdepimdbusinterfaces.so.4.6.0', which is also in package libkdepim4 4:4.5.96-0ubuntu0~ppa2~oneiric1
[16:41] <yofel> that was the mentioned overwrite?
[16:42] <yofel> otherwise fine
[16:47] <bulldog98_konver> yofel: no that wasn’t the override
[16:48] <bulldog98_konver> yofel: the one fixed was in ~ppa6
[16:48] <yofel> ah, well, here's the next one..
[16:49] <bulldog98_konver> yofel: hopefully the last one
[16:50] <yofel> once updated packages are up I'll do another upgrade test
[16:55] <yofel> anyone knows what the hell is up with smokegen? http://paste.kde.org/82237/ Builds fine as soon as I replace the debian-qt-kde.mk include with '%: dh $@'
[17:00] <ScottK> yofel: Look at line 1060 in your paste.  Find the equivalent line from your build that works and see what's different.
[17:00] <yofel> good point
[17:00] <ScottK> I believe that will be the source of your error.
[17:06] <yofel> the whole linking junk is missing...
[17:06] <yofel> -Wl,--as-needed -Wl,--no-undefined -Wl,--as-needed -Wl,--no-undefined
[17:11] <ScottK> I'd ask MoDaX then.
[17:14] <bulldog98_konver> somehow my kded and plasma is always crashing on login
[17:39] <_Groo_> hi/2 all
[17:40] <_Groo_> could anyone copy the kdepim 4.6 to experimental pls
[17:40] <_Groo_> experimental only has lib kde pim so far
[17:44] <yofel> _Groo_: it's in staging, and we're still Q/A-ing
[17:44] <yofel> _Groo_: and ping apachelogger re calligra packages
[17:45] <_Groo_> hey yofel
[17:45] <_Groo_> yeah, but experimental already has kdepim-runtime 	4:4.6.0-0ubuntu1~ppa1
[17:46] <_Groo_> someone mistakenly copied it to experimental?
[17:46] <_Groo_> or it passed the QA and went to experimental?
[17:48] <yofel> more like a mistake I guess
[17:58] <bulldog98_konver> _Groo_: thought it would be ready
[18:36] <bambee> evening
[18:36] <bambee> I sent my report to my mentor!!  report done!! :D
[18:37] <bambee> now... I've to prepare a talk o_O
[18:52] <_Groo_> bulldog98_konver: what would be ready bulldog?
[19:36] <LaserJock> apachelogger: do you have any wiki pages or anything on kubuntu-lowfat? ScottK told me you were interested in it
[19:41] <bulldog98_konver> _Groo_: kdepim-runtime
[19:43] <_Groo_> bulldog98_konver: it is ready :)
[19:44] <_Groo_> bulldog98_konver: what i asked was the rest of the chebang :D
[19:44] <_Groo_> just updated from stating, kinda works
[19:44] <bulldog98_konver> yofel: is it ready?
[19:44] <bulldog98_konver> what doesn’t work?
[19:45] <_Groo_> old kleopatra bitches about new kleopatra
[19:45] <_Groo_> when updating
[19:45] <bulldog98_konver> what exactly
[19:46] <_Groo_> actually new kleopatra bitches about old kdepim-doc
[19:46] <_Groo_> http://paste.ubuntu.com/626758
[19:46] <_Groo_> let me see what else
[19:47] <ScottK> kleopatra shouldn't ship that file.
[19:48] <_Groo_> http://paste.ubuntu.com/626760/
[19:48] <_Groo_> this one i forced and it went without intervencion (aka apt-get -f)
[19:49] <bulldog98_konver> the last one is fixed in a newer upload
[19:51] <_Groo_> bulldog98_konver: one strange thing
[19:51] <_Groo_> bulldog98_konver: if i install kdepim-dev , it installs libassuan-dev but removes the libassuan2-0
[19:51] <_Groo_> bulldog98_konver: is that correct?
[19:55] <bulldog98_konver> _Groo_: is something depending on libassuan2-0?
[19:55] <_Groo_> bulldog98_konver: let me check
[19:56] <_Groo_> bulldog98_konver: http://paste.ubuntu.com/626767/
[20:00] <Quintasan> lol
[20:00] <Quintasan> yofel, apachelogger: we are getting Gluon Pong today
[20:18] <yofel> _Groo_: yes, libassuan2-0 is supposed to be removed
[20:19] <yofel> at least in oneiric
[20:19] <_Groo_> yofel: ok then, if nothing else uses it
[20:19] <_Groo_> yofel: see http://paste.ubuntu.com/626767/
[20:20] <yofel> hm...
[20:20] <yofel> actually...
[20:20] <yofel> bulldog98_konver: I think you're building against wrong assuan in natty, needs to be libassuan2-dev
[20:20] <yofel> and libassuan-dev in oneiric
[20:30] <bulldog98_konver> yofel: ok I’ll fix that
[20:30] <bulldog98_konver> shadeslayer: your string seems to get a yes
[20:32] <bulldog98_konver> yofel: you’are right, I fixed that now
[20:33] <yofel_> k, upload a new build then, kdepim-runtime is fixed at least
[20:35] <bulldog98_konver> yofel: that’s what I’m doing
[20:35] <yofel> bulldog98_konver: did you remove the doc file from kleopatra?
[20:35]  * bulldog98_konver thinks the oneiric part is ok
[20:35] <bulldog98_konver> yofel: yes
[20:35] <yofel> :)
[20:35] <bulldog98_konver> maybe cause I’m on oneiric
[20:36] <yofel> nah, the oneiric build seems ok, just natty needs the different assuan package
[20:38] <bulldog98_konver> yofel: should I copy the oneiric part to experimental?
[20:39] <yofel> you still need to upload a new build with the overwrite error fix, ppa7 is broken
[20:39] <bulldog98_konver> and you do a release note on kubuntu.org? :)
[20:39] <yofel> bulldog98_konver: http://people.ubuntu.com/~yofel/pics/pim46.png
[20:39] <bulldog98_konver> yofel: 8 and 9 and 9~natty2 is uploaded
[20:40] <yofel> k
[20:41] <bulldog98_konver> yofel: that’s wrong we support downgrading
[20:41] <bulldog98_konver> you can ppa-purge ppa:kubuntu-ppa/experimental
[20:41] <bulldog98_konver> and the kmail stuff should work again
[20:42] <yofel> hm, yeah, there is ppa-purge
[20:42] <yofel> I guess if we keep it in exp.
[20:43] <bulldog98_konver> yofel: oneiric should go to archive, apachelogger?
[20:43] <yofel> yes
[20:44] <bulldog98_konver> yofel: so I should propose a branch merge. Right?
[20:45] <yofel> right
[20:45] <_Groo_> bulldog98_konver: ill update when the packages are available , in theory there wont be any errors... well since i uodated i wont get any errors anyway
[20:46] <_Groo_> yofel: im backporting calligra git from today
[20:46] <_Groo_> yofel: unfortunatelly beta1 as a lot of breakages... like plan who is a sore state
[20:46] <_Groo_> yofel: if git is more stable ill upload that to my ppa
[20:47] <_Groo_> yofel: but is a very cool release... im very happy kivio is back :D
[20:47] <_Groo_> yofel: we didnt had a first class proggie like that ina long time.. dia is just awful
[20:47] <yofel> yeah...
[20:47] <bulldog98_konver> _Groo_: I find git quite stable
[20:48] <_Groo_> bulldog98_konver: good to know, ill check it a  few hours
[20:49] <_Groo_> btw who is Adrien Grellier?
[20:49] <bulldog98_konver> _Groo_: I even mangaged to do thing with Calligra, I couldn’t find/do with LibreOffice
[20:49] <_Groo_> bulldog98_konver: im a great koffice/calligra fan
[20:49] <_Groo_> bulldog98_konver: im thrilled they are pushing foward the envelope
[20:49] <_Groo_> forward
[20:50] <_Groo_> i based my packages in is great work
[20:50] <_Groo_> btw guys, i did a little ugly hack cause im lazy
[20:50] <_Groo_> since calligra is still in flux, i created a calligra-others package where i dump the files that change so i dont have to keep changing all the .installs all the time
[20:50] <bulldog98_konver> I even haven’t LibreOffice installed. I only use Calligra git
[20:51] <_Groo_> when calligra goes gold, ill remove the -others and put the files in the proper places :D
[20:51] <_Groo_> laziness FTW!
[20:58] <ScottK> I'd suggest calligra-experimental.  We've used nomenclatures like that before.
[21:06] <bulldog98> yofel: http://bazaar.launchpad.net/~bulldog98/kdepim-runtime/4.6.0/ is this ok
[21:06] <bulldog98> or should I compile that into one commit?
[21:09] <yofel> nah, the commit count doesn't matter, stil the same merge
[21:09] <yofel> *still
[21:10] <bulldog98_konver> yofel: I’ll propose it then
[21:12] <bulldog98_konver> yofel: https://code.launchpad.net/~bulldog98/kdepim-runtime/4.6.0/+merge/64308
[21:21] <bulldog98_konver> yofel: https://code.launchpad.net/~bulldog98/kdepim/4.6.0/+merge/64604
[21:37] <bulldog98_konver> is having 2 udevd running normal?
[21:59] <ScottK> I have three.  No idea what's expected.
[22:06] <bulldog98_konver> ScottK: ok thought there would be zombie processes around
[22:06] <ScottK> Maybe, but if there are, you aren't alone.
[22:09] <_Groo_> guys where can i find gstreamer vdpau support?
[22:09] <_Groo_> is it part of the gstreamer project or an independent plugin?
[22:25] <tazz> hi maco
[22:25] <maco> hello
[22:25] <apachelogger> yofel: what goes to archive?
[22:26] <yofel> kdepim 4.6 oneiric
[22:26] <apachelogger> oh noes
[22:26] <apachelogger> not before QA
[22:26] <yofel> well, branch isn't merged yet either, too tired to do that today
[22:26] <apachelogger> last time we discussed it the consensus was: first test, if it works good enough -> upload to archive, if not -> ppa
[22:26] <yofel> and the packages in staging should mostly ~work
[22:27] <yofel> apachelogger: what's the difference if we'll have the same thing as 4.6.80 out in a bit?
[22:27] <apachelogger> yofel: because we know 4.7 will have production quality due to 7 releases before that with constant improvement
[22:27] <apachelogger> whereas 4.6 is entirely new and has yet to proof it self in life production envrionments
[22:28] <yofel> true, but whoever runs O should know that...
[22:29] <apachelogger> yofel: yes, but if it turns out crap we can wrap our minds inside out to get it replaced with 4.4 again
[22:29] <yofel> anyway, let's look at it again tomorrow
[22:29] <apachelogger> which btw then breaks every pim setup done in oneiric
[22:29] <yofel> 4.4 shouldn't be compatilbe with 4.7 anyway
[22:29] <yofel> -> tomorrow
[23:20] <Quintasan> apachelogger: ping
[23:20] <apachelogger> Quintasan: pogo
[23:20] <Quintasan> apachelogger: can u do C stuff without asking over 9000 questions?
[23:22] <Quintasan> apachelogger: I'm scanning for a char with scanf("%c",&znak);
[23:22] <Quintasan> apachelogger: however the next this that is called is fgets and I get no chance to input anything
[23:22]  * apachelogger points out that apachelogger is most of the time in verbose mode and thus it is iether 9000 questions or an explentation of why things are the way they are
[23:22] <Quintasan> How do I stop scanf from passing an newline there?
[23:23] <apachelogger> Quintasan: passing?
[23:23] <Quintasan> apachelogger: scanf("%c",&znak);
[23:23]  * apachelogger points out that apachelogger always implemented getchar solutions ^^
[23:23] <Quintasan> that goes to switch(znak)
[23:24] <Quintasan> and when I press 1 and then press enter
[23:24] <Quintasan> it calls a function which uses fgets
[23:24] <Quintasan> it uses it three times
[23:24] <Quintasan> the first time I get no chance to input anything
[23:25] <apachelogger> ehm
[23:25] <apachelogger> I will need more code than that
[23:25] <Quintasan> beware
[23:25] <Quintasan> I did not write that
[23:25] <apachelogger> generally what you need to watch out for:
[23:26] <Quintasan> http://paste.kde.org/82519
[23:26] <Quintasan> fragment of code
[23:26] <apachelogger> scanf leaves the newline
[23:26] <apachelogger> fgets will append newline and \o
[23:26] <apachelogger> \0 rather
[23:26] <apachelogger> Quintasan: I like how one does not understand the variable names :D
[23:27] <Quintasan> You shall not complain about that
[23:27] <Quintasan> I might get alcohol for fixing that
[23:27] <Quintasan> That's why I somehow agreed to trying to fix that
[23:27] <apachelogger> Quintasan: znak is filled with fgets?
[23:28] <Quintasan> nope
[23:28] <Quintasan> znak is only used to ask user for the choice in the whole switch(znak) statement
[23:28] <Quintasan> and the code used to get znak value from user is obviously scanf("%c",&znak);
[23:29] <apachelogger> hmhmmm
[23:29] <apachelogger> ok
[23:29] <apachelogger> Quintasan: so
[23:30] <apachelogger> switching over strings like that makes me wanna barf  :P
[23:31] <apachelogger> Quintasan: so the problem is in the part of the code that I do not see (aka fgets?)
[23:31] <Quintasan> apachelogger: you want that function which uses fgets?
[23:31] <apachelogger> not particularly
[23:31] <Quintasan> http://paste.kde.org/82531
[23:31] <apachelogger> I can say for sure that you have a \n in stdin left
[23:32] <Quintasan> I can conclude that as well
[23:32] <Quintasan> What I want to know, is how the hell do I get rid of it
[23:32] <apachelogger> so what is the problem?
[23:32] <apachelogger> Quintasan: getchar
[23:32] <apachelogger> sec
[23:32] <apachelogger> http://bytes.com/topic/c/answers/533187-scanf-problem
[23:32] <apachelogger> see second code snippet
[23:33] <apachelogger> essentially you scanf and then do a getchar without assignment to a variable
[23:33] <apachelogger> hence you get rid of the \n
[23:33] <apachelogger> I suppose you could also flush stdin
[23:33] <apachelogger> though that is more expensive I believe
[23:35] <apachelogger> Quintasan: do I also get alcohol now?
[23:35] <apachelogger> Quintasan: is that cpp?
[23:35] <Quintasan> apachelogger: nope, it's fucking mixed code
[23:36] <Quintasan> it uses cpp and c at once
[23:36] <Quintasan> @_@
[23:36] <apachelogger> well
[23:36] <apachelogger> cpp is c with more cruft :P
[23:36] <apachelogger> just wondering why one would use c functions there instead of streams, but oh wellz
[23:37] <apachelogger>   fgets(this->imie, sizeof(this->imie), stdin);
[23:37] <apachelogger> also those this just make me cry
[23:37] <Quintasan> why?
[23:37]  * Quintasan is a newfag
[23:37] <Quintasan> I'm just happy most of that code works
[23:38] <apachelogger> Quintasan: the this is useless unless you have a variable named imie at the scope of the code line
[23:38] <apachelogger> which is not the case
[23:38] <apachelogger> well, not unless there is a global imie floating around somewhere which would theEvil(tm)
[23:38] <Quintasan> I'm just making that shit work
[23:39] <apachelogger> as long as I get beer I am happy with all the code you throw at me :P
[23:39] <apachelogger> for sufficient amounts of beer you might even get me to fix up pyth0rn code
[23:39] <apachelogger> too bad sheytan is not around, he might like to know that


[15:51] <micahg> doko_: how do I run the TCK on openjdk?
[15:52] <doko_> micahg: http://icedtea.classpath.org/wiki/JCKDistilled
[15:52] <micahg> doko_: awesome, thank you
[15:53] <doko_> micahg: expect about one week of work to setup the test environment
[15:53] <micahg> doko_: wow, ok, is this a one time thing, or per test?
[15:54] <doko_> one time
[15:55] <micahg> doko_: k