[00:00] learn something new everyday === heHATEme is now known as Vorian [00:15] Shouldn't the archive admin's be subscribed to bug #368505? it's been ACKed [00:16] Launchpad bug 368505 in ampache "Please sync Ampache-3.4.4-1 from Debian unstable (main)" [Undecided,Confirmed] https://launchpad.net/bugs/368505 [00:17] porthose: james_w may have removed ubuntu-archive from the subscribers if he thought it needed a fakesync (not sure why) [00:18] I did [00:18] it does need a fakesync [00:18] ok just checking :) [00:18] ubuntu-archive admin aren't better placed to do that than any random developer [00:18] different orig.tar.gz in that case? [00:18] yeah [00:19] so I unsubscribed the archive and subscribed the sponsors, so a larger pool of people where aware of it [00:20] james_w: I think it could have been useful to have that in the bug comment - I can see you doing that from the +activity page though [00:21] yes, it would have been [00:21] however, I had a bunch of things to do [00:21] and if someone didn't understand what a fakesync was they could ask [00:23] has there been any interest in have the Doctrine ORM Framework as a package? === ShadowChild is now known as lukjad007 [00:40] Hi, is there a channel for the Multiverse Repos, or is this it here? [00:40] here [00:40] maxb Ah. [00:41] Well, I've noticed something for the last couple of releases. The "Funguloids" game has unresolved dependencies. [00:41] what a weird name [00:42] maxb I wouldn't know, I've never been able to play it. ;) [00:42] hmm, so it does. File a bug? [00:42] (If there isn't already one) [00:42] I think there must be. I only heard of the game because of it. [00:43] But, I will look for it. [00:43] * maxb wonders when it last build... [00:43] Here it is: https://bugs.launchpad.net/ubuntu/+source/funguloids/+bug/194686 [00:43] Ubuntu bug 194686 in ogre-contrib "Error installing Funguloids: ogre-plugins-cgprogrammanager doesnt exist" [Medium,Confirmed] [00:44] jm, intrepid/jaunty, not that old [00:44] *hm [00:44] What's ogre, do you know? [00:45] maxb Sorry, No. [00:46] * maxb initializes a karmic cowbuilder [00:47] maxb I am only an advanced user. [00:47] Anyway, I've confirmed the conformation. [00:48] !fakesync [00:48] Sorry, I don't know anything about fakesync [00:48] what is a fakesync? [00:49] IIUC, it's a upload to Ubuntu that has a version number and content as if it was a sync [00:49] usually done because Debian and Ubuntu have ended up with bytewise different .orig.tar.gz files for the same version, so the normal sync process is invalid [00:50] Aha. And how do you fix "fakesyncs" from both sides (Ubuntu/Debian) so that regular syncs can procede? [00:50] by using same tarball in the next upload in both? [00:51] If the reason is .orig.tar.gz mismatch, I think the problem fixes itself automatically once a new upstream version is uploaded to Debian [00:52] * maxb notes that funguloids is now FTBFS in karmic [00:53] ok cool. Another question - Distro specific patches. For example I'm patching upstream docs to instead of saying "report bugs to upstream@mailing list" to say "report bugs to BTS" but I would also would like to include an ubuntu specific patch which will then instead say "report bugs to launchpad". [00:53] Is there a was to create such smart patches. I'm thinking some extra metadata in the patch such that the ubuntu builders will pick it up. [00:55] The idea is to have the debian-syncs to still work. On the other hand it brings a security risk in a way that a patch which isn't applied in Debian ends up breaking Ubuntu (although the intend was different) [00:55] xnox`, possible but annoying === popey_ is now known as popey [00:57] As a kind debian maintainer I would still include debian/patches/ubuntu_fix_ftbs_new_python.patch but not add it to series file just to keep the diff smaller. [00:58] * xnox` loves quilt & latest dh7 way better than cdbs [01:01] we do things like this a little bit in pkg-cli-apps [01:01] and pkg-mono [01:10] it's about to get somewhat easier in karmic, I hope [01:10] dpkg 1.15.1 will have a 'dpkg-vendor' script, so you can test the exit code of 'dpkg-vendor --derived-from Ubuntu' [01:11] (or 'dpkg-vendor --is Ubuntu') [01:19] cjwatson, that would be nicer than lsb_release [01:19] cjwatson, i'm pretty sure i'm breaking things on distros like mint [01:23] these are some of the issues even though in our ecosystem we all use dpkg we do have our own little things which gives as advantages but on the other hand create barriers for fixes and security issues, resulting in delays between the members in the DAG of Debian-like systems. (think all types*architectures*variant) [02:24] hi, is zippo popular in your area? [02:27] LucidFox: I'm not real happy about it. I am happy it wasn't imposed on Kubuntu for Jaunty. [02:27] ah === ApOgEE__ is now known as ApOgEE- [02:51] hello room [02:51] how do you install java? [02:52] mib_x96owjor: This isn't a support channel, please ask in #ubuntu [02:56] ok, thanks [02:56] bye [03:00] how might I add a comment to merge-o-matic? would like to link twitux to a bug/sync [03:16] jacob: There is a column on the far right that has a hidden text box. Just click on it to add a comment [03:19] jacob: If you can't find the text box, tell me the name of the package and the comment you want to add, and I can add it for you [03:35] ^ was about to respond! d'oh. found it, someone tell him I said thanks if he returns tonight. :P === fabrice_sp__ is now known as fabrice_sp === hggdh_ is now known as hggdh === savvas_ is now known as savvas === rawang is now known as rawang|lunch === hanska is now known as Guest67703 [05:28] ScottK: btw, you can use it with ubuntuone; its the generic Ubuntu they mean. [05:32] someone asked me today, "What do you know about Ubuntu One?" I responded, "You mean Canonical One, Mark's jet, it's an airplane, it flys." :) [05:33] had no clue about Ubuntu One until today, well I knew about it, just didn't know what it was going to be called [05:34] is it something like dropbox? with similar features? [05:34] looks like it...I think Mark hinted on going for more of a "Mobile Me" type system [05:36] a bit expensive.. [05:36] but i shouldn't complain as I probably won't use 2GB ;) [05:36] I haven't even used a 1gb on dropbox yet [05:40] nixternal: so u use dropbox n ubuntuone? [05:40] just dropbox [05:40] just try the ubuntuone .. already file a bugs .. :( [05:40] don't you need an invite to try it? [05:41] yeah .. u can request the invitation .. [05:41] im just lucky to see invitation in my inbox .. [05:41] how did they decide who to invite then? [05:41] hrmm, speaking of that, I just noticed that my dropbox isn't working on this machine [05:41] thats why i give a try [05:41] e-jat: lucky you :) [05:41] heh, after I said that about the invite, I got one sitting in my inbox...didn't even see that [05:41] thanks kklimonda [05:41] superm1: maybe ubuntu members got it .. [05:42] e-jat, oh i was gonna say if that's it then nixternal should have one, and then i saw he did :) [05:43] "but we are not releasing the source code to the servers at this time." heh ;) [05:43] superm1: :) [05:45] wb RoAkSoAx [05:45] hello e-jat [05:46] bug 375249 [05:46] Launchpad bug 375249 in ubuntuone-client "Segmentation fault" [Undecided,New] https://launchpad.net/bugs/375249 [05:47] kklimonda: me unlucky .. cant get the applet work [05:48] ehehehe, welcome to the hell of beta testing ;} [05:48] e-jat: at least you can play with web interface :) [05:48] all i can see is some not so bad front page :) [05:49] i like the fact that canonical is using openid for all pages.. [05:49] I don't have to remember another set of l/p.. [05:50] greetings [05:50] hey [06:00] kklimonda: :) [06:00] kklimonda: openid is c00l [06:00] brb .. going to take my launch .. [07:11] hi siretart [07:11] hey ajmitch! [07:12] how are you? [07:13] good, how are you? [07:32] fine, thanks [07:32] rather busy this week, have to finish a conference paper and stuff.. [07:33] * ajmitch is still finishing off a project at work this week [07:33] and then it's onto the next one in the pile :) [07:35] good morning [07:35] good morning dholbach [07:36] hiya ajmitch === Lure_ is now known as Lure [07:41] morning everybody o/ [07:42] DktrKranz: do you have some minutes for a python transition related question? [07:43] didrocks: fire it [07:43] (and good morning, btw) [07:44] DktrKranz: so, I updated some days again vte to 0.20.1-0ubuntu1. All was well, sun was shining... :) [07:44] then, I merged with the debian version producing 0.20.1-1ubuntu1 and troubles come around :) it FTBFS: [07:44] https://launchpad.net/ubuntu/+source/vte/1:0.20.1-1ubuntu1/+build/992606/+files/buildlog_ubuntu-karmic-i386.vte_1:0.20.1-1ubuntu1_FAILEDTOBUILD.txt.gz [07:45] the issue is that it's still using site-packages [07:45] I found no clue why the behavior changes (no explicit setup.py call) [07:45] * DktrKranz looks [07:46] the bzr branch is there : ~ubuntu-desktop/vte/ubuntu [07:46] The only thing which worked out was to pass -d to dh_pysupport as in the old package [07:47] but it copies files in usr/lib/pyshared/python2.6/ instead of usr/lib/python-support/python-vte/python2.6 [07:47] (I don't know the difference between pyshared, which seems to be used in debian and python-support/package-name) [07:48] new pysupport places files in new locations [07:48] ok, so python-support/package-name is the new location? [07:49] what I tried too in this package is to add again debian/pyversions and set XS-Python-Version to 2.4... but nothing worked. I'm really stucked :( [07:49] didrocks: I just got the same problem with a human-theme upload [07:50] dholbach: did you achieve to fix it? :) [07:50] https://bugs.edge.launchpad.net/ubuntu/+source/cdbs/+bug/374892 [07:50] Ubuntu bug 374892 in cdbs "Use correct root path when converting dist- to site- in arch packages" [Undecided,New] [07:50] that could be it [07:50] let me check [07:50] let's move to #ubuntu-devel [07:52] didrocks: could you please grep upstream code to see if they hardcode site-packages somewhere? [07:52] DktrKranz: I did and it's the case in configure.ac file. But it was already the case in the previous revision with no patch [07:52] I see, I'll have a testbuild [07:53] DktrKranz: look at the link that dholbach provided. I may be related [07:55] didrocks: probably [07:56] DktrKranz: that's really strange. If you bzr diff last revision and -r -3 [07:56] you will see that changes aren't huge :/ [07:58] q: http://launchpadlibrarian.net/26622104/buildlog_ubuntu-karmic-powerpc.hotkeys_0.5.7.4-0.2_FAILEDTOBUILD.txt.gz i believe this happened because the build happened during a libxmu upgrade [07:58] will this automatically be rebuilt or will i need to bug report it? [07:59] When a file is moved between binary packages, what is the correct incantation to avoid a dpkg file overwrite error? [08:00] Should a versioned Replaces be used, or a versioned Conflicts+Replaces ? [08:00] binary packages built by the same source, if that matters [08:01] maxb: the source in which a file was moved between a package should deal with conflicts/replaces itself i would think [08:01] at least, the conflict portion [08:02] hmm [08:03] yes that's my point, the maintainer has moved a file between packages without being aware they need to provide the necessary extra hinting to allow clean upgrades [08:12] didrocks: "checking for python script directory... ${prefix}/lib/python2.6/site-packages [08:12] it hardcodes it somewhere, so it has to be adjusted, I'll have a look [08:29] so how should we feel about syncing a debian package that does not use patches for it's changes to the source (they're shown within the diff.gz)? either that or we fork with the same changes but reflected as patches [08:29] We sync [08:29] k [08:32] DktrKranz: it was already the case with the previous version [08:34] DktrKranz: I think this is a cdbs issue. Because compiling today the old revision have the same behavior [08:37] didrocks: indeed, just noticed that. I prefer debhelper over cdbs, so I need to look at how it handles Python stuff, the patch you mentioned is for distutils, so it should not impact vte, though. [08:38] DktrKranz: ok. If you have any idea about this, you're really welcome :) [08:41] didrocks: are other packages FTBFS? dholbach said somethinh about human-theme [08:41] DktrKranz: this is related to his bug report [08:49] what is the ubuntu policy on various sections in .desktop files? i am working on a package in which section = video want to know if that is fine or if it should be AudioVideo [08:52] doh, bad changelog entry got me. it was referring to debian's video repository ;) [08:53] didrocks: did you try to give-back it? I see different results here [08:53] and it could probably be OK [08:54] DktrKranz: the layout is different? [08:54] yes [08:54] you don't have a pyshared but a python-support ? [08:55] didrocks: oh, I didn't look at -dbg package, it was that which has the offending path [08:55] yes [08:55] so a give-back would FTBFS again [08:55] ok... so that's not where it failed [08:56] DktrKranz: I really think that's an exterior element which makes it fail (as the previous version has now the same issue) [08:57] yeah [08:58] maybe doko is aware of that. I will try to ping him [08:59] dholbach, do i have a comment sat in moderation/spam on behind motu? [09:04] directhex: at least I didn't get an email about it [09:04] dholbach, no mail usually means akismet [09:05] directhex: you're right [09:05] approved [09:05] ;) [09:19] didrocks: what .PRECIOUS does exactly? [09:24] DktrKranz: it's telling what files must not be cleaned in the clean rules for makefile. Debian dropped it [09:27] should i be doing anything if a package i had synced FTBFS. the failure has nothing to do with the package itself. the sync bug was marked as 'fix released' [09:28] LordKow: If it has nothing to do with it, no, other than fix the other package. [09:28] LordKow: Sync is done => fix released. [09:29] jpds: the problem was/is that one of the deps was partially upgraded when it tried building [09:29] libxmu to be precise [09:30] so i dont think there is anything i can do except maybe feed the build farm some energy ;) [09:30] Oh, they get plenty of power. [09:30] LordKow: Link to build log? [09:30] jpds: https://launchpad.net/ubuntu/+source/hotkeys/0.5.7.4-0.2/+build/997649/+files/buildlog_ubuntu-karmic-powerpc.hotkeys_0.5.7.4-0.2_FAILEDTOBUILD.txt.gz [09:35] LordKow: Oh, ppc and the other arches are usually slow to catch up [09:36] yea, so will it be automatically rebuilt or is some sort of user intervention required to make that happen when the time is right? [09:36] It should automatically build later. [09:37] jpds: ty === rawang|lunch is now known as rawang [09:52] didrocks: maybe I found something... === azeem_ is now known as azeem [10:03] DktrKranz: really ? :) === \sh_ is now known as \sh === Nicke_ is now known as Nicke [10:07] didrocks: uploading to my PPA to be sure [10:12] DktrKranz: ok, keep me in touch :) [10:15] Ive got an mplayer karmic failure to build because of missing liblzo-dev dependency in my ppa. I checked http://packages.ubuntu.com/karmic/mplayer and the dependency is in the control file (see the diff.gz) but not listed on the web page [10:15] Is there a reason it builds in ubuntu's repos but not my ppa? [10:16] (I'm using the same source package) [10:17] I could remove the dependency myself, but i'm test building the rdepends of xvidcore, and need to use the same source pkg as in the repos [10:17] loic-m: I don't know if ppa have pkgbinarymangler installed [10:19] loic-m: rmadison says there is no liblzo-dev in karmic [10:19] PPAs deliberately don't binarymangle [10:20] There's no man page for pkgbinarymangler on manpages.ubuntu.com and I'm a bit lost atm [10:21] pkgbinarymangler is not the issue [10:22] loic-m: liblzo-dev doesn't exist in karmic [10:22] maxb: yes, but then how comes mplayer builds in karmic? [10:23] It probably doesn't any more [10:23] Hello, can someone review sabily-keyring (http://revu.ubuntuwire.com/details.py?upid=5729) ? [10:23] Which mean if something is attempting a rebuild of mplayer for karmic in Ubuntu's repositories, it will fail? [10:23] Likely [10:24] launchpad says it last built in jaunty [10:24] https://launchpad.net/ubuntu/+source/mplayer/2:1.0~rc2-0ubuntu19 [10:24] maxb: I thought they were rebuild at each new cycle [10:25] loic-m: if you catch someone who actually work on mplayer in ubuntu, please report him to me [10:25] maxb: do you have any idea how I can test build it in the meantime (for bug #306399)? [10:25] Launchpad bug 306399 in xvidcore "New upstream version available (1.2.1)" [Wishlist,In progress] https://launchpad.net/bugs/306399 [10:25] siretart: no clue at all [10:26] loic-m: best thing we can do about mplayer (IMO) is to take the debian package as basis, and enhance it to build mencoder in addition to mplayer [10:26] I tried, but don't think i'll manage to finish that this or next week [10:27] loic-m: Why do you need to rebuild it? [10:27] (Sorry, that's a long bug to read quickly) [10:27] maxb: to test if it still builds using latest xvidcore [10:28] oh, right. Well, you'll need to either fix it to not require lzo, or build it in jaunty, I guess [10:28] didrocks: it builds (waiting for i386 to finish, but it should be ok): https://edge.launchpad.net/~dktrkranz/+archive/ppa/+files/vte_1:0.20.1-1ubuntu1_1:0.20.1-1ubuntu2.diff.gz [10:28] siretart: If you work on mplayer, can you try with xvidcore-1.2.1 instead of 1.1.2? [10:28] in 2-3 weeks, remind me again :) [10:29] siretart: packages are at https://launchpad.net/~loic-martin3/+archive/xvid and the diff.gz on the bug report [10:29] siretart: thanks [10:29] sorry [10:29] bbl, sigfood caught. [10:29] maxb: I guess atm I'll try on Jaunty [10:30] DktrKranz: I have to look at the package layout, first :) [10:30] siretart: no pb for the delay. mine is one cycle late ;) [10:40] please go on that link: [10:40] http://www.schwimmbadspiel.de/?refId=99828434 [10:40] http://www.schwimmbadspiel.de/?refId=99828434 [10:40] http://www.schwimmbadspiel.de/?refId=99828434 [10:40] http://www.schwimmbadspiel.de/?refId=99828434 [10:40] http://www.schwimmbadspiel.de/?refId=99828434 [10:40] http://www.schwimmbadspiel.de/?refId=99828434 [10:40] Stop that. [10:40] !ops [10:40] Help! Hobbsee, Riddell, sladen, fbond, mneptok, gnomefreak, Seveas, dholbach, elkbuntu, PriceChild, or jpatrick! [10:40] iulian: it's a spammer [10:41] Pointy stick of DOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOM! [10:41] Hobbsee! [10:41] * Hobbsee MUHAHAHAHAHAHAHA [10:41] iulian: heya! [10:41] Hobbsee: he was here with another name yesterday [10:41] mok0: same IP? [10:41] @btlogin [10:42] Hobbsee: I don't knw [10:42] got him, and got him again. [10:42] Hobbsee: great, thx [10:42] and he's not even restricting activities to ubuntu channels [10:42] Sounds like a K-line to me. [10:43] one would hope so [10:43] Hobbsee: you joined #plone about 3 seconds too late [10:43] ajmitch: yeah, i suspected so [10:43] nothing i can do there [10:44] and now he hits the world of warcraft channels on freenode :) [10:44] ah well [10:44] DktrKranz: it's still in usr/lib/psyhared/python2.x and not python-support/package-name. So, the issue still remains [10:44] * ajmitch goes back to hunting stuff [10:45] or fixing up the merge which still had jaunty in the changelog... [10:45] There's WoW channels? [10:45] StevenK: mostly addon development channels [10:46] * ajmitch uploads again, this time with karmic [10:51] * StevenK mourns for maintaince [10:51] StevenK: 12 hour maintenance for your usual realm? [10:52] Yup [10:52] fun [10:52] I suspect they have teams all over the Blizzard datacentres swapping out machines [10:53] I suspect db reindexing [10:53] They specifically said hardware, too [10:53] oh, interesting [10:53] its a shame they don't get clustering and HA [10:54] I suspect each realm really is a cluster of 6-8 machines [10:54] But I guess I'll never know [10:54] it supposedly is, from what we've heard [10:55] StevenK: there are services per map region; instance servers, battlegroup servers, common db for storage [10:55] StevenK: counts unknown [10:55] clustering tech may be known, but I haven't gone looking [10:55] sigh, I've passed my package upload count for jaunty already, I think [10:56] ajmitch: good thing karmic is there! [10:56] azeem: yes, I was unclear - with the packages I uploaded to karmic alrady, it's more than I uploaded to jaunty :) [10:57] didrocks, DktrKranz: don't depend on python-support's internals (usr/lib/psyhared/python2.x vs. python-support/package-name issue) [10:57] do all you have to do *before* invoking dh_pysupport [10:58] (same with dh_pycentral, btw) [10:58] StevenK: what's the status of the poulsbo drivers for jaunty? [10:59] POX: I don't really get you. The previous upload (two weeks ago), was working well, with the same dh_pysupport call [10:59] mok0: Underway [11:00] StevenK: Cool ;-) [11:00] didn't you sync python-support ~2 weeks ago? [11:00] if yes, its internals changed [11:00] and since apparently this package depends on it, it fails === dpm_ is now known as dpm [11:00] ergo: don't depend on pysupport's internals [11:01] POX: Debian depends on it. The idea is to merge as close as possible to Debian [11:01] POX: let me check python-support upload [11:01] (and everything that contains "pyshared" or "python-support/package-name" is using py{support,central} internals [11:02] didrocks: pysupport 1.0 was in Debian experimental for a while (so that packages that use its internals could be fixed before it hit unstable) [11:03] so if this package still uses these internals, just sync it with Debian [11:03] Hm, gcalctool is so amazingly buggy that we should remove it from the distro [11:03] POX: We still have ubuntu changes in it, that's why we can't sync it [11:05] POX: I will check the python-support version used to build it [11:05] afk for lunch :) [11:06] didrocks: anyway, solution will be to sync with Debian or at least merge debian/rules [11:06] What's ubuntuone? Is is a scam? [11:06] (even if I don't know what package is it, only few are still not fixed in Debian) [11:07] mok0: it's a canonical service, at least [11:07] ajmitch: I got an "invitation" by email to join [11:07] mok0: yes, all ubuntu members got that. [11:07] ajmitch: ... amazingly simple way to get access to peoples files :-) [11:08] the intentions were good, not so sure if they did the mass-invite the right way :) [11:08] POX: I didn't look at it well, one of Ubuntu deltas is a -dbg package, but it doesn't seem it relies on pysupport internals (hardcoded path or so) === mcasadevall is now known as NCommander [11:32] just been having a fiddle with squid for possible merge, I've got it down to only one warning being, W: squid source: patch-system-but-direct-changes-in-diff cfgaux/config.guess and 1 more any suggestions ??? [11:33] * VK7HSE has just been called out of the room! (Gahh!) [11:36] VK7HSE, config.guess should be deleted in the "clean" rule. [11:38] VK7HSE: is the same warning emitted for the Debian package? [11:40] cjwatson, i can't imagine why it wouldn't [11:40] or i can begin to imagine, then my brain blocks it out [11:40] if it is, then there's no need to worry about it at merge time [11:41] VK7HSE: squid was uploaded a few hours ago [11:45] POX: I merged it with Debian :) [11:45] POX: and they have pyshared and not python-support [11:45] as a path [11:48] didrocks: then it's still not fixed in Debian as well [11:49] file a bug (or reopen the old one) [11:49] POX: I think Debian install in /usr/lib/pyshared and don't bother about /usr/lib/python-support/package_name [11:50] POX: ok, the previous version (with the right path) was installed with previous python-support version. I have to figure out how to test it in my pbuilder [11:50] no, package shoudl install to standard Python paths, dh_pysupport will move it to /usr/{share,lib}/pyshared [11:50] but package shold not depend on it [11:51] /usr/lib/python-support/package_name is old path, new python-support uses pyshared (to be compatible with python-central) [11:51] POX: really? I found no documentation on that [11:52] but python-central doesn't use /usr/lib/pyshared (one of the reasons we use python-support now in Debian) [11:52] didrocks: /usr/share/doc/python-support/README.gz [11:52] POX: thanks, reading it now :) [11:56] POX: ok "Public extensions (.so files) are handled just like public modules [...] will be located in /usr/lib/pyshared/pythonX.Y/" [11:56] so, pyshared is the right location for .so [11:57] it is, but dh_pysupport will handle moving the files [11:58] you can install to /usr/{,local/}lib/python2.X/site-packages - dh_pysupport will detect it and move the files [11:58] POX: that is what it is doing. So everything's right now. Thanks to DktrKranz, -dbg package is also fixed :) [12:00] (thanks DktrKranz and POX for the clarification, btw :D) [12:11] <\sh> hmm...do i miss something or is the "request team membership" button on LP missing? (especially for universe sponsors) [12:17] \sh: it's a restricted team, you have to be added [12:17] congratulations btw [12:17] <\sh> james_w: thx :) [12:18] <\sh> james_w: sure..I know...but somehow there needs to be an "apply for membership" link or something ... to make it easier then to write an email to the team owner... [12:18] <\sh> afaik there was in the past... [12:19] you can just ping Emmet or Luke here [12:20] * persia goes to add \sh to the team [12:20] congratulations? i'm congratulating \sh for something? [12:20] <\sh> persia: readd ;) [12:20] <\sh> directhex: I became daddy of a wonderful boy:) [12:20] \sh, Indeed, for the fourth time or so, if I remember correctly. [12:21] \sh, oh, yes, i remember now. i'm still of a maturity level where i see infants as something to run in fear from... congrats though! [12:22] <\sh> directhex: hehe..I know that feeling..but now everything is different :) [12:22] \sh: let me add my congratulations to the pile :) [12:23] <\sh> ajmitch: thx :) [12:26] \sh, Your gold star has been restored. [12:27] <\sh> persia: thx a lot [12:38] What's the procedure in launchpad to request an upgrade from upstream on a multiverse package (in karmic)? Attach the diff.gz then subscribe motu-release? [12:41] loic-m, subscribe the sponsors, not the release team. [12:41] (or just upload, if you have another way to do that) [12:42] persia: thanks [12:45] hello [12:46] I've been dealing with bugs 221332 and 373767 and I've been wondering whether the maintainers are interested in one or both patches [12:46] Launchpad bug 221332 in tiemu "The tiemu package is heavily outdated" [Wishlist,Confirmed] https://launchpad.net/bugs/221332 [12:46] Launchpad bug 373767 in tiemu "Incorrect keyboard mapping" [Undecided,New] https://launchpad.net/bugs/373767 === jcfp is now known as Guest13093 === Guest13093 is now known as jcfp [12:55] papo, You've exposed a documentation failure :) Thanks. [12:55] !sponsoring [12:55] Sorry, I don't know anything about sponsoring [12:55] Bother. Two of them. === santiago-pgsql is now known as santiago-ve [12:56] papo, I think you want https://wiki.ubuntu.com/DeveloperGuide/Sponsorship : this documents the best way to get visibility for your patches, and get them applied. [12:59] well [13:02] persia: to be honest, I'm very lazy. The point is that the "patch" (I'm not even using dpatch in the PPA) should be broken into two parts and some ubuntu guys should decide which one (or both) should go into the package. Now it would be quite annoying if I would have done that work for nothing. That's why I'd prefer it if someone actually would make the decision before I continue with any work. After that, I'd really love to clean it up [13:02] persia: Oh and there's also a couple of fixes I applied because lintian was complaining [13:03] and what do you mean by documentation failure? [13:03] In that we didn't document that the best way to request patch review was in that manner so that you came here. [13:03] ah I see :) [13:03] The issue is mostly that there aren't any "maintainers" of any specific packages in Ubuntu: it's all rather team-oriented. [13:04] If you need a decision, that needs someone specifically familiar with tiemu, which makes it extra complicaed. [13:05] On the other hand, if you care about tiemu, and want to keep it going well, there's no reason you can't be the person who takes care of it. [13:05] (looks like nobody has given it much thought for the past year or so) [13:05] persia: I mean the patch is not trivial in some sense. I'm changing something which is done the wrong way in my opinion and the implement this properly needs quite some testing. tiemu can implement several calculators and I'm just using one etc. [13:05] yep indeed [13:06] cjwatson: sorry I got called away from the PC!... just read the result about it already being done so I'll pick another one to have a try at!... [13:08] papo, With a bit more looking, it appears there is no tiemu maintainer, either in Debian or Ubuntu. [13:08] aw [13:08] And nobody who made significant changes in a while. It may as well be you, if you're up for it. [13:09] well I could do it. I've been Debian maintainer some years ago and started the developer process thing but I had to give it away because if time issues [13:09] now things look better again [13:10] if you're looking for a tiemu expert, I suspect the best person to talk to would be the upstream maintainer ... [13:10] papo, Given that it's orphaned in Debian, I'd recommend reviewing the bugs (in both LP and the BTS), and pushing the new version there. If that takes too long, please come back, and we'll help you get it here first. [13:10] (assuming they're still active) [13:11] cjwatson: yes they are active [13:11] cjwatson: I'm about to hand in my patch there too, of course [13:11] good afternoon everybody [13:13] persia: Ok, I'll check with my favorite debian sponsor then [13:14] didrocks: I tried to import modules (debug ones too) and they work. If you have a test case to run, I could launch it [13:14] papo, Thanks a lot! It's always great to see someone take over one of these orphaned packaged. [13:14] hey Toadstool [13:15] yw [13:15] hi persia [13:16] DktrKranz: it seems to be ok. I tested it too and it's working. I ask pitti and he sponsored it before Alpha-1 [13:16]