/srv/irclogs.ubuntu.com/2009/06/24/#kubuntu-devel.txt

GonI have a friend who need to add a IPP printer, but he can't found the GUI ...00:03
Gonsystem-config-printer-kde is loaded ween I plug a usb-printer00:03
Gonwhen*00:03
JontheEchidna~seen a|wen00:38
kubotua|wen was last seen 1 month, 9 days, 2 hours, 9 minutes and 24 seconds ago, quitting IRC (Read error: 104 (Connection reset by peer)) and a moment before saying "good luck with the packaging ... i expect you to have the beta done, when i look in again next time :)"00:38
JontheEchidnaeek00:38
JontheEchidnaoh, the quit message explains taht00:38
JontheEchidnaAlso explains why the kile updates stopped last month :D00:39
voriana|wen :'(00:47
vorian~seen obama00:48
kubotunope!00:48
vorianme either00:48
ryanakcaseele: Should I place the wiki's editbar at the top of the page or under the breadcrumb, with a "Show editing options" link on the same line as the breadcrumb, but far right? Nice thing about having an editbar above the page contents is that you don't have to look for it in the page, shezam, it's right there for you....01:13
ryanakca(The question is open for all to answer, please give me input on what we want the wiki theme to be like)01:14
nhandlerryanakca: What exactly is the "breadcrumb"?01:24
ryanakcanhandler: You are here: Foo >> Bar >> Baz01:35
nhandlerryanakca: Ah, one of the bars I filed a bug about ;)01:36
ryanakcanhandler: Aye. To see it at the top, see http://wiki.ryanak.ca/kubuntu/ ... you'll need to login01:37
nhandlerI personally think a link on the same line as the breadcrumb on the far right would be too small and out of the way to be useful01:38
ryanakcaIt was for bug 390253... that fix there also fixes 389722...01:38
ubottuLaunchpad bug 390253 in kubuntu-website "KubuntuNew theme: Edit panel should be at top of page, not bottom" [Undecided,In progress] https://launchpad.net/bugs/39025301:38
ryanakcabug 38972201:38
ubottuLaunchpad bug 389722 in mysql-dfsg-5.0 "skip-name-resolve is not included in default my.cnf" [Undecided,New] https://launchpad.net/bugs/38972201:38
ryanakcabug 38977201:38
ubottuLaunchpad bug 389772 in kubuntu-website "Kubuntu New Wiki Theme - Bottom div too tall on short pages" [Undecided,In progress] https://launchpad.net/bugs/38977201:38
nhandlerI like having it at the top/bottom of the page because it is very easy to get there when you need to edit a wiki page01:38
ryanakcaMy opinion as well. OK, I'll commit, mark them as fix commited and move on :)01:39
lex79JontheEchidna: don't forget launchpad bug 390069 :P01:40
ubottuLaunchpad bug 390069 in kmhtconvert "New upstream release kmhtconvert 0.7.4" [Undecided,New] https://launchpad.net/bugs/39006901:40
nhandlerryanakca: It does cover up the search box a little. Not sure if that matters though01:40
nhandlerIt also would be useful to have some way to always have the edit options at the top showing (a preference)01:41
ryanakcanhandler: I can always move the content block down a tad... as for always on, I'm not sure... I can set it to always be on by default... but we'd probably have to have a vote and see what everybody's preference is if we set a default that affects everybody01:41
nhandlerryanakca: I don't think having it always on would be a good default, but a preference would be awesome (if possible)01:43
ryanakcanhandler: I'll find out01:44
ryanakcanhandler: As for bug 389955, can we really expect people to be using the Kubuntu theme on the Ubuntu wiki? I could fix it, but it would require javascript which a) the sysadmins would probably rather I avoid, and b) would fail on browsers that don't support javascript01:53
ubottuLaunchpad bug 389955 in kubuntu-website "Kubuntu New Wiki Theme - "You are here" text is incorrect" [Undecided,New] https://launchpad.net/bugs/38995501:53
nhandlerryanakca: I would expect a fair number of Kubuntu theme users to use wiki.ubuntu.com since a lot of links point there. However, if a good solution doesn't exist, I don't think it is pressing that the bug be fixed now01:56
ryanakcanhandler: Hmmm... now that I think of it, the current implementation for having the editbar at the top fails if users are in graphical browsers (works fine in text browsers, w3m, etc) without js... because I'm hiding the bar off the screen, 4000px to the left, and sliding it in when it's wanted. But I can't slide it in / out without JS...02:09
lex79Riddell: launchpad bug 39142602:10
ubottuLaunchpad bug 391426 in kde-style-qtcurve "New upstream release kde-style-qtcurve 0.65.0" [Undecided,New] https://launchpad.net/bugs/39142602:10
ryanakcanhandler: Therefore, should I place it at the very bottom of a page and slide it up to the top of the window when it's wanted? Or do you think the distance between Show editing options in the top left corner of your window and having the edit bar at the very bottom of the page would cause confusion / seperate the two?02:10
JontheEchidnalex79: lol, another new qtcurve? upstream is way too fast02:11
lex79yes, too fast :)02:13
JontheEchidnafor MIR reports they ask how active upstream is: "dead", "calm", "vigorous", "frentic"02:14
lex79I'm trying qtcurve style and is very nice but oxygen is oxygen :)02:14
JontheEchidnathey need a new one: "like the QtCurve dudes"02:14
nhandlerryanakca: Would it be possible to check if javascript is enabled and to fall back to the old style if it isn't?02:18
ryanakcanhandler: Ummm... quick google says no, not without something serverside... which for us, means no.02:22
ryanakcanhandler: hmmm... setting the bar to the bottom of the page and then calling it up reintroduces bug 389772 ... so I guess that since NetSurf and dillo are the only two graphical web browsers (excluding Mosaic, etc. from the 90s) that don't support javascript, I'll stick to the javascript support for the bar... text browsers, even though most don't support javascript, are unaffected.02:45
ubottuLaunchpad bug 389772 in kubuntu-website "Kubuntu New Wiki Theme - Bottom div too tall on short pages" [Undecided,Fix committed] https://launchpad.net/bugs/38977202:45
nhandlerryanakca: If we are using javascript for the bar, is there a reason not to use it to differentiate between wiki.ubuntu.com and wiki.kubuntu.org for bug 38995502:46
ubottuLaunchpad bug 389955 in kubuntu-website "Kubuntu New Wiki Theme - "You are here" text is incorrect" [Undecided,New] https://launchpad.net/bugs/38995502:46
ryanakcanhandler: Nope. It can be done... It just isn't high on my priority list :)02:47
nhandlerNo problem. You got the ToC bug fixed, which was the most annoying one ;)02:48
ryanakcanhandler: Well, almost fixed... it's only commited... I'm going to fix as many bugs as I can before starting the eternal process of prodding sysadmins...02:49
nhandlerryanakca: Did we see if any of these bugs are valid in ubuntunew?02:50
ryanakcanhandler: Nope, feel free to check for them though and file against the ubuntu-website project...02:50
nhandlerryanakca: I'll look tomorrow. I need to prep for a Packaging Training session now ;)02:54
ryanakcanhandler: OK02:54
e-jatnixternal: +1 from me about the new kernel :)03:04
=== shadeslayer is now known as Guest86530
=== nellery_ is now known as nellery
shadeslayerwould someone give me their opinions on bug 39148106:45
ubottuLaunchpad bug 391481 in hundredpapercuts "Improving IRC Support" [Undecided,New] https://launchpad.net/bugs/39148106:45
=== shadesla2er is now known as shadeslayer
freinhardlaunchpad doesn't support git repos yet?09:25
Selihello, I'd need help with packaging - I have a tarball with wrong layout, and https://wiki.ubuntu.com/PackagingGuide/Complete says it's not a reason to redo the tarball, but it actually doesn't say how to fix it - can somebody tell me?09:28
freinhardRiddell: seems like plasma-widget-network-mamanger-dbgsys still can't live with plasma-widget-network-mamanger09:32
freinhardSeli: debian/source/format09:45
Selifreinhard: could you be a bit more specific? I don't see anything about that in the guide09:49
freinhardSeli: see man dpkg-source09:57
Selifreinhard: I already have, but I still don't see how that helps me09:58
Seliwhat I want is basically just rpm's "%setup -c", since the tarball misses one directory level09:59
Selior, put differently, I want to package the tarball contents, but the buildsystem adds additional mess to the extracted data10:00
freinhardSeli: tried to clean it up with a rule in rules?10:11
Selino, why should I? I somehow expected turning tarball contents into a _all.deb package wouldn't be a rocket science10:13
Selinot to mention if I clean up debian/ it will presumably stop working very quickly10:23
DreadKnightffs... latest updates screwed up my install11:14
DreadKnightintel gma 945 user..11:14
DreadKnighti don't know how to fix it...11:15
DreadKnighthow would i go for booting another kernel?11:15
DreadKnightif i still have an older one.11:16
freinhardDreadKnight: put Driver "intel" in your xorg.conf11:18
DreadKnighti managed with another kernel11:18
DreadKnightor not hmm11:18
freinhardDreadKnight: doesn't boot? adding acpi=off to the kernel boot params did it for me11:19
DreadKnighti managed to boot using another kernel so far11:19
freinhard-8 works -10 doesn't11:19
DreadKnighti get the login screen, but not able to log in...11:19
DreadKnighti'm into -11 atm.. lol11:20
freinhardwhere did you get that one from?11:23
DreadKnightlatest updates..11:23
DreadKnight-9 is fail as well .. even -811:23
DreadKnighti just can't log in for some reason11:24
DreadKnight get an x session, but x crashes or something when loging in... and i get the login screen again...11:24
DreadKnightfail11:24
DreadKnighti could log in with -7, but video acceleration is a total joke11:32
DreadKnightnixternal blogged about this.. then deleted post or something.. meh11:33
neversfeldeis 4.3 rc already tagged and if, can I help with packaging?11:55
sygma1982halihoooo12:33
sygma1982van itt valak?i12:33
sygma1982anybody here rák?12:33
freinhardneversfelde: can't a 4.3rc yet: http://websvn.kde.org/tags/KDE/12:39
freinhard+see12:39
shadeslayerhey anyone here?13:59
shadeslayeri need to ask if this is normal : http://imagebin.ca/view/NAY6f7.html13:59
shadeslayerif it is , then im not filing a bug...if it is ill file one at night14:03
shadeslayer*if it is not14:04
shadeslayerill be right back14:04
rgreeninganyone else get bitten by the mesa/dri update last night?14:05
shadeslayerso....14:12
JontheEchidnashadeslayer: I think it is on purpose14:16
shadeslayerJontheEchidna: really?14:21
JontheEchidnayeah, can't say that I agree with the implementation though :/14:21
shadeslayerme neither...doesnt look good14:21
JontheEchidnait looks really retarded, like they're making it the width of the task entry just for the hell of it14:22
shadeslayertotally agree....14:22
shadeslayerif they had to make it this way,at least those arrows should be on the extreme right...14:23
rgreeningseele: ping14:27
shadeslayeris there a gui option to set different wallpapers on each desktop (not activity)14:37
rgreeningseele: here's a papercut - Akregator - can't interact with the icon in system tray (possibly only when integrated with Kontact)14:41
JontheEchidnashadeslayer: zoom out, then there should be a "plasma settings" button14:49
shadeslayerJontheEchidna: then??14:52
JontheEchidnaok, after configure plasma14:53
JontheEchidnadifferent activity for each desktop14:53
JontheEchidnathen zoom back in14:53
JontheEchidnaeach virtual desktop should now have a different plasma activity14:53
shadeslayeryum!14:54
shadeslayerJontheEchidna: will this increase mem usage??14:55
JontheEchidnaa bit I suppose14:55
shadeslayerhmm14:56
shadeslayerthanks for the ttip14:58
shadeslayer*tip14:58
seelergreening: pong15:20
seelergreening: is that something easy to fix? add it to the papercut project15:20
rgreeningdunno how easy/hard. I suspect easy...15:20
seelepart of the problem is i dont know how hard some stuff is to fix which is a qualifier for papercuts :(15:20
rgreeningWell, it's a keyboard accelerator and a system tray icon.. theoretically, easy.15:21
rgreeningrather mouse/not keyboard15:21
seeleok, i say add it and if it becomes too hard then we'll just make it not a papercut15:22
=== akonadi is now known as nihui
rgreeningseele: whats the process to add it? DO we need to open a bug for it? And how/where do we add it? I'm also sort of tied up today...15:26
=== akonadi is now known as nihui
rgreeningseele: nm. seems it was fixed since I last used that feature. YAY!15:28
rgreeninglol. I'll crawl under a rock again...15:28
nixternalgood morning kubunauts16:21
ScottKSo we have a netbook seed now.17:31
ScottKrickspencer3: ^^17:31
rickspencer3ScottK!17:31
rickspencer3when can I try it?17:32
rgreeningScottK: good stuff.17:32
ScottKNext we need to upload the metapackages (just did a diff for that and Tonio_ is reviewing).17:32
ScottKThen we need the new default settings packages (Tonio doing)17:32
rgreeningScottK: I'm going to work on packaging usb-creator-kde today. It works.. but has bugs we need to resolve.17:32
ScottKThen we ask slangasek to start cranking out some images.17:32
rgreeningwhee17:33
ScottKrgreening: Excellent.  That's an important component of the netbook strategy17:33
rgreeningIt took me a while to remove all the gtk/glib/gobject references. I had to get REALLY creative :)17:33
rgreeningcallbacks, lambda, all the fun python bits...17:34
* agateau remembers17:34
rgreeningmucho thanks agateau :)17:34
rgreeninglambda rulez17:34
rgreening:)17:34
agateau:)17:34
rgreeningI owe beers to agateau next UDS17:35
* ScottK would insist on something harder.17:35
rgreeningnow, now... this is a public channel17:35
* agateau does not drink alcohol, but a coke would be fine!17:35
rgreening:P17:36
* rgreening prob shouldn't either17:36
rgreeningScottK: are you on jaunty still or have a system with karmic?17:36
rgreeningor anyone else for that matter with karmic?17:37
ScottKrgreening: On Jaunty still, but my netbook will be karmic once it arrives and your usb thingy works.17:37
rgreeningNeed to see if update-notifier-kde is working for them. FOr me it complains and fails.17:37
rgreeningdunno why17:37
rgreeningImportError: No module named QtCore.. but thats not true...17:38
ScottKrgreening: What happens if you go into a python shell (python) and try import QtCore17:40
rgreeningworks as expected17:40
rgreeningIt's like there's a hidden character in the program... and it's not actually looking for QtCore but something else...17:41
rgreeningother python apps work (like my usb-creator-kde) and has the same import line...17:41
ScottKWeird17:43
* seele pokes agateau to look at some paperkuts17:48
rgreeningScottK: yeah. boggles my mind.17:48
rgreeningScottK: ok, so I can the contents of the file to another file and run it... it works.17:49
rgreenings/can/cat/17:49
rgreeningaaaaaaaaaaahhhhhhhhh!!!!!!!!!17:50
* agateau adds seele poke for tomorrow todo17:50
agateaurgreening: wrong version of python interpreter?17:52
agateauhave to go17:52
agateaubye17:52
rgreeningnope.bye17:52
rgreening:)17:52
* Quintasan just deleted all his bookmarks18:11
rgreeningRiddell, JontheEchidna: either of you running karmic?18:16
JontheEchidnayus18:17
rgreeningneed to test update-notifier-kde (it doesn't run for me) from the pyshared dir. If I move it somewhere else, I can make it run.. strange.18:17
rgreeningJontheEchidna: ^18:17
rgreeningcan you see if it runs for you?18:17
JontheEchidnapyshared dir?18:17
freinhard/usr/share/pyshared/18:18
rgreening/usr/bin/update-notifier-kde is a link18:18
rgreeningya18:18
JontheEchidnaoh, ok18:18
JontheEchidnaImportError: No module named QtCore18:18
rgreeningok, not just me then. Riddell ^18:19
rgreeningupdate-notifier-kde is busted when run from the pyshared dir... dunno why.18:19
rgreeningI think it needs to be somewhere else (python-support)?18:19
freinhardrgreening: that's where it is on jaunty18:20
rgreeningbizzarre.18:20
ScottKrgreening: Riddell is on vacation.  Please fix.18:20
rgreeningsomething is definately amis. And it's not a problem in the actual file. I tested moving/renaming, and it runs if not in the pyshare dir.18:21
ScottKrgreening: What I'd do to troubleshoot this is edit the update-notifier-kde file to print sys.path right before the import and see if it's missing something.18:22
rgreeningJontheEchidna, Riddell: update-notifier-kde fails to exec from pyshared dir in karmic. However, moving to any other dir, it can be executed.18:22
rgreeningScottK: ^18:23
rgreeningthis seems a python issue18:23
rgreeningperhaps18:23
ScottKrgreening: Yes.  Thus my advice.18:23
rgreeningI tried with both 2.5 and 2.6. Same result also.18:23
Quintasanoh, if I'm also running karmic, if noone's around poke me :P18:24
rgreeningScottK: sys.path reports the same path (with the exception of the first entry (the dir it was run from)18:27
ScottKrgreening: Next I'd try to reinstall it and see if that helps.18:30
rgreeningdone that18:30
ScottKrgreening: OK. How about a no change rebuild and install that?18:30
rgreeningScottK: here's the problem. I don't know how to fix though. PyQt4 and dbus exist in /usr/share/pyshared. The import statement will look in current dir beofre system wide for import classes/modules. update-notifier-kde.py cannot exist in the top level pyshared dir. period. Someone care to offer fixes :)18:32
rgreeningI think this differs from where PyQt4 and dbus install modules in Jaunty... and hence why broke here.18:33
ScottKI don't understand.  Why can't it exist there?18:34
rgreeningfrom PyQt4.QtCore import * ... theres a dir PyQt4 in pyshared, so it thinks that's where QtCore exists. It doesn'.18:35
rgreeningthe current path is in sys.path as first in list.18:35
rgreeningsame for a dbus dir.18:36
rgreeningand these lines break as the imports will fail using the current dir.18:36
ScottKI see18:36
rgreeningthis must have change from jaunty.18:36
ScottKYes.  I believe so.18:36
rgreeningScottK: do you have a PyQt4 dir in usr/share/pyshared?18:37
ScottKrgreening: I do18:37
rgreeningcheck you sys.path18:37
rgreeningmaybe that changed18:38
ScottKrgreening: http://paste.ubuntu.com:80/203036/18:39
rgreeningyour first entry is blank. mine wasn't. it was the current dir.18:40
rgreeningso, that's changed. and broken some things we do. prob others.18:41
ScottKI think that may be an actual on purpose change.18:41
rgreeningAny ideas on correct fix ScottK, Riddell? I think it needs to move directories or be in a subdir off pyshared18:47
rgreeningScottK: it runs if I move to a subdir update-notifier-kde in usr/share/pyshared18:48
ScottKrgreening: I don't think update-notifier-kde should be in /usr/share/pyshared.18:53
rgreeningshould be in pysupport (my guess)18:54
ScottKrgreening: Nope.18:54
ScottKWe don't use helper specfic directories anymore18:54
ScottKEither it's an application and should be in some place like /usr/share or it's a private module and shouldn't be in the public module space.18:55
ScottKshare/bin18:55
rgreeningScottK: this package is messed up. In install it say copy the .py to python-support but it gets installed to pyshared.18:57
rgreeningwtf18:57
rgreening:{18:57
ScottKThat's a recent change in python-support (new to Karmic, IIRC)18:57
rgreeninggrr18:57
rgreeningok, I have no idea. I have to get back to usb-creator. Can you look at a fix or enlist someone else to address?18:58
rgreeningschmidtm: ^18:58
rgreeningsry.. meant ScottK^18:58
* ScottK is ENOTIME for the next few days.18:59
rgreeningfeel free to enlist18:59
ScottKAlready did that once a long time ago.  I don't care to repeat it.18:59
rgreeningyou are the recuiter in this case19:00
rgreening:P19:00
rgreeningdeal out the pain19:00
rgreening Bug #39173119:07
ubottuLaunchpad bug 391731 in update-notifier-kde "update-notifier-kde fails to run from /usr/share/pyshared dir" [Critical,Confirmed] https://launchpad.net/bugs/39173119:07
rgreeningthere, maybe someone who has some time can resolve ( JontheEchidna perhaps )19:08
Quintasanrgreening: I'm supposed to make update-notifier-kde to be installed into /usr/share/bin?19:15
rgreeningQuintasan: I have no idea on the '''Correct''' way to do this. Things have changes in Karmic. Previously it would have been in python-support and we had a link in /usr/bin to it. I personally think we should install update-notifier-kde.py as /usr/bin/update-notifier-kde and not a symlink. Everything else gets installed correctly.19:20
rgreeningso, no symlink, but the actual file, renamed as update-notifier-kde in /usr/bin19:21
Quintasanrgreening: I will remove *.links files then, and place the *.py into /usr/bin19:21
rgreeningIt's how (for example) ufw does it.19:21
rgreeningSure, it will at least make it work. If someone else wants to change, they can make the case...19:21
rgreeningQuintasan: make sure you work from trunk and update19:22
rgreeningor send me the diff so I can apply to trunk19:22
QuintasanI need to practice working with bzr so I will try doing it with bzr first :P19:24
rgreeningbzr checkout http://bazaar.launchpad.net/~kubuntu-members/update-notifier-kde/trunk19:30
rgreeningthen make your changes in trunk dir.19:30
rgreeningonce done, bzr export update-notifier-kde from in trunk. creates a new dir above trunk. test build from the exported dir.19:31
rgreeningQuintasan: ^19:31
Quintasanthx19:31
rgreeningif it builds and installs/runs fine, go back to trunk and bzr commit (add your comments) and then bzr push. Then it's in bzr yay. Then we can upload from there.19:32
rgreeningdon't forget to dch -i in the trunk/debian dir before export. Update the revision to next .. etc.19:33
rgreeningQuintasan: ^19:33
=== blueyed_ is now known as blueyed
Quintasanwhy on earth devscripts need postfix?19:37
ScottKQuintasan: Install it without recommends19:40
=== rickspencer3 is now known as rickspencer3-afk
seaLneok that was impressive just plugged a hp470 usb printer in for the first time and karmic set it all up for me, sweet :)19:52
Quintasanrgreening: It's alive :D20:03
rgreeninggood stuf20:04
Quintasanbzr: ERROR: Cannot lock LockDir(http://bazaar.launchpad.net/%7Ekubuntu-members/update-notifier-kde/trunk/.bzr/branch/lock): Transport operation not possible: http does not support mkdir()20:08
Quintasan?20:08
Quintasanrgreening: ^20:13
rgreeningQuintasan: are you a member of kubuntu-members team in launchpad?20:15
Quintasanyup20:15
rgreeningand you did a checkout?20:15
Quintasanerr, bzr checkout?20:15
rgreeningyeah20:15
Quintasanyup20:15
rgreeningand then a bzr commit20:15
Quintasanthis is what  I get at commit20:16
Quintasanrgreening: I did bzr commit -m " too long to paste here" and this is what I got20:20
rgreeningQuintasan: I think it's cause the checkout url was http ...20:21
rgreeningQuintasan: edit trunk/.bzr/branch/branch.conf so it has this as the bound_location20:22
rgreeningbzr+ssh://bazaar.launchpad.net/%7Ekubuntu-members/update-notifier-kde/trunk/20:22
rgreeningsee if that fixes it20:22
rgreeningbzr+ssh instead of http20:24
Quintasanhm it's doing something but stuck at 0%20:25
rgreeningare you behind any fw that could block ssh?20:27
Quintasanhmm wrong20:28
Quintasanit uses port 666 dunno why :D20:28
Quintasanmaybe cause of ssh config20:28
rgreeninglol20:28
QuintasanARGH20:29
Quintasannow I have wrong permissions on .ssh20:29
Quintasanwhat permissions I should have rgreening?20:29
rgreeningls -al .ssh/20:30
rgreeningtotal 2420:30
rgreeningdrwx------20:30
Quintasan700?20:30
rgreeningyeah20:30
rgreeningwhat you have20:30
* Quintasan guessed that20:30
Quintasan75520:30
Quintasanyay20:31
Quintasanworked20:31
Quintasannow bzr push?20:31
rgreening3 bits. 4(r=on)+2(w=on)+1(x=on)20:31
rgreeningyep20:31
Quintasanno push location known or specified20:32
rgreeningnp, do this...20:32
rgreeningbzr push lp:~kubuntu-members/update-notifier-kde/trunk20:33
rgreeningand that should now save the location so next time, bzr push works20:33
Quintasanno new revisions to push, is this good?20:34
rgreeninghmm..20:35
Quintasanhttps://code.launchpad.net/~kubuntu-members/update-notifier-kde/trunk <- mine commit is listed there20:35
rgreeningQuintasan = Michał Zając?20:36
Quintasany20:36
Quintasanyes20:36
rgreeningyou pushed /trun and not trunk20:36
rgreeningessentially a new branch20:36
rgreeninglol20:36
Quintasanhmm20:36
QuintasanI did20:36
Quintasanlol20:36
Quintasanhow do I revert this?20:37
rgreeningoh, wait....20:37
rgreeningI think both a new branch was created and you also updated the original... two different runs I guess...20:37
Quintasanlet me check20:38
rgreeninghttps://code.launchpad.net/~kubuntu-members/update-notifier-kde/trunk20:38
Quintasanlooks like I screwd it20:39
rgreeningQuintasan: ?20:39
rgreeninglooks ok in the url I posted above20:39
Quintasanrgreening: nothing, just wondering how I missed "k",  can I delete the other branch?20:40
rgreeningyep.20:40
rgreeningopen... https://code.launchpad.net/~kubuntu-members/update-notifier-kde/trun20:40
rgreeningsee the trash can icon near to middle of page just after lp:~kubuntu-members/update-notifier-kde/trun20:41
rgreeningclick it20:41
Quintasandone20:41
rgreening:)20:42
* Quintasan will double-check letters next time20:42
Quintasan:P20:42
rgreeninglol20:42
rgreeningI know we all want to drop the K in kde programs, but that was extreme20:42
* Quintasan points at paperKuts20:43
rgreeningQuintasan: testbuilding now20:51
rgreeningQuintasan: you need to change something...20:54
Quintasanhm?20:54
rgreeningIt should be called update-notifier-kde (no .py at end).20:55
rgreening:)20:55
rgreeningQuintasan: change this line in the .install - *py usr/bin/20:55
rgreeningchange it to : *py usr/bin/20:56
rgreeningchange it to : update-notifier-kde.py usr/bin/update-notifier-kde20:56
rgreeningI think that will work20:56
rgreeningQuintasan: ^20:56
rgreeningQuintasan: apparantly that does NOT work as I thought...21:02
rgreeninglol21:02
rgreeningmaybe we should just rename the python program in the package itself to not have the .py on it. It's a main program executable afterall.21:03
rgreeningQuintasan: I'll leave it to you to figure out the best way to handle. You'll need a core dev to review and upload (ScottK, Riddell, etc) as it's in main. When you make changes to bzr now, no need to bump to another version in changelog (as it's not released yet).21:05
rgreeningI have to run....21:06
Quintasanrgreening: the solution you proposed worked for me :P21:06
rgreeninghmm... maybe I screwed up... It created a dir with the .py in it when I tested...21:07
Quintasanor not21:07
rgreeningyeah21:07
rgreeninglol21:07
Quintasanit made a directory :/21:07
rgreeningyep21:07
Quintasanguess I will rename the .py file21:07
rgreeningbzr mv it21:07
rgreeningto keep history intact21:07
Quintasanok, I will work on it21:08
rgreeningbzr mv update-notifier-kde.py update-notifier-kde21:08
rgreeningok, later. good luck.21:08
Quintasanthanks21:08
rgreeningnp21:08
QuintasanScottK:https://code.launchpad.net/~kubuntu-members/update-notifier-kde/trunk  <-- please review rev. 80 and upload if it's good :)21:51
=== blizzzek is now known as blizzz
=== blizzzek is now known as blizzz
=== mcasadevall is now known as NCommander
=== word_ is now known as worde
=== worde is now known as word

Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!