[00:06] RoAkSoAx: I'm no autoreconf expert... [00:06] 'autoreconf -fiv' may be a start [00:07] or you may just need to rerun aclocal [00:07] pochu, Ok. Well I'm just trying by doing: aclocal and it creates the aclocal.m4 file [00:10] OK so, I've run aclocal and it generates an aclocal.m4 file that does not include the changes I need to have python2.6 support, so should I just summit my patch? [00:13] RoAkSoAx: was there an error displayed when running aclocal? [00:16] Ampelbein, aclocal: configure.ac: 27: macro `AM_CHECK_PYTHON_HEADERS' not found in library [00:17] RoAkSoAx: sounds like that is the problem? (Disclaimer: I don't know it) ;-) [00:17] Ampelbein, not actually, I've deleted that line just to test and the same thing [00:19] well the changes in the aclocal file are actually changing for example from site-packages to *-packages and adding python2.6 to the list of interpreters, but it's not doing that automatically, so that's why I made manual changes since those changes are required to add support for python2.6 [00:32] did dh_make go away? [00:32] i have at least 50 other dh_* commands, but no dh_make [00:32] it's in its own package [00:33] did it used to be part of the debhelper package? [00:33] no [00:34] as far as I know, it's always been in dh-make [00:35] oh. alrighty === TheMuso` is now known as TheMuso [00:53] Packaging Training session about pbuilder in #ubuntu-classroom in 7 minutes === lukjad007 is now known as ShadowChild [01:52] it seems that requestsync over mail no longer does the sponsorship check [01:54] james_w, what error does it shows you? [01:54] none [01:55] so what seems to be the problem then cuz I've also had some issues with it earlier today [01:56] jjam [01:56] james_w, it's lacked appropriate sponsorship checks (i.e. motu can requestsync directly to main without sponsorship) for a while [02:11] james_w: i just tried requestsync and it tells me that i need sponsorship. the resulting mail has "status new" and subscribe "ubuntu-universe/main-sponsors" (whichever is appropriate) [02:15] james_w: for universe: http://paste.ubuntu.com/203269/ [02:15] james_w: for main: http://paste.ubuntu.com/203270/ [02:17] hey [02:17] sorry, phone call [02:17] I'm seeing quite a few bugs subscribe ubuntu-archive directly [02:18] the common theme is that they are filed by mail [02:18] james_w: I'm guessing that they're all filed by MOTUs, if it's the bug that directhex was referring to? [02:18] nope, by others [02:18] hm [02:18] * ajmitch can't easily test that [02:19] * directhex sponsors ajmitch for effort [02:19] directhex: sure, I'll setup another identity & apply for MOTU then :) [02:20] you should be part of debian front desk. even more useful! [02:20] still trying to read through that thread on -project [02:21] my mind is melting [02:22] ? [02:23] the thread about DAM & front desk [02:23] it's a long read [02:26] james_w: were those reports filed before May 23rd? (or shortly thereafter). the check for sponsoring was changed with version 0.74 [02:27] there were some before [02:27] some today, but I don't know what version they were using [02:27] nhandler, i get home from work at ~1810. day of the week doesn't bother me [02:29] nhandler, i can do a session from work as a general "probably" i.e. if a cluster explodes, i need to cancel with 0 notice [02:29] james_w: just tried with version 0.73, it fails to detect i need sponsoring: http://paste.ubuntu.com/203273/ [02:29] nhandler, otherwise i need to limit ~1810 as a minimum start time [02:29] james_w: so i guess that there's the problem and 0.74 should go to jaunty-backports as well. [02:30] directhex: It is up to you when you want to do the session. [02:30] * ajmitch isn't quite qualified for those packaging sessions [02:30] lol ajmitch [02:30] Ampelbein: thanks for checking [02:30] I need to catch up on the latest toys [02:30] james_w: you're welcome. [02:30] like most of the contents of ubuntu-dev-tools which I've never used :) [02:31] * nhandler needs to finish looking through devscripts [02:31] devscripts is fine, it hasn't changed much in the last few years [02:31] nhandler, i would be happy with a 1830 session - can you please send me an e-mail reminder? i'm filled with free memory-destroying vendor-paid alcohol [02:31] directhex: what would you teach? [02:32] ajmitch: True, but I still haven't looked at all of the tools. I'm looking at it now since it is a Debian NM question [02:32] directhex: So you want to lead a session on July 16th at 18:30, correct? Are you going to cut the session short or simply go until 19:30? [02:32] ajmitch, truth, justice, and the $NATIONALiTY way [02:33] james_w: I hope you don't mind me doing a little session scheduling for July [02:33] nhandler, i'd go until 19:30. actually, I'm on BST, so subtract 1 hour from the above? or am i totally lost in timexones... [02:33] nhandler: of course not :-) [02:33] * james_w hugs nhandler [02:33] directhex: Isn't BST UTC+1 right now? [02:34] nhandler, yes [02:34] james_w: Also, at the session earlier today, they expressed an interest in a python packaging session to go along with the java one we had and the upcoming perl one [02:34] * ajmitch is glad to be in a nice sane timezone [02:34] i'm extra confused as i'm in europe/berlin timezone to0day [02:34] directhex: So 18:30 UTC would be 19:30 BST [02:35] nhandler: excellent [02:35] nhandler: what else do you have on the books? [02:35] nhandler, okay, so... a 1800 utc session is more than fine then. [02:36] directhex: Great. Do you have a title for your session? [02:36] nhandler, should i blame the alcohol, or my stupid understanding of timezones? [02:36] ajmitch: The only currently scheduled session other than the one directhex will give is the one the pkg-perl team is doing [02:36] There are some ideas for future sessions on https://wiki.ubuntu.com/Packaging/Training [02:37] nhandler, try for "Mono packaging: quick, easy, and awesome" [02:37] nhandler, but PLEASE email me a reminder. i'll forget otherwise [02:37] for this i blka [02:37] blame the booze [02:37] directhex: Ok, thanks a lot. I'll take care of updating the necessary schedules. It will be on the Fridge, but I will also email you ;) [02:37] thanks! [02:38] now, it's 25 to 4am. bedtime! [02:39] Night directhex, and thank you [03:14] nhandler: you are teaching teh pbuilder pwn eh? [03:15] vorian: he taught, and we were enlightened [03:16] shucks [03:16] vorian: I linked to the Ninja wiki and hooks [03:16] traitor [03:16] * ajmitch wonders how that is traitorous [03:17] * vorian is medicated atm, so pardon crazy [03:17] this isn't you normally? [03:18] heh, good point [03:18] this channel attracts crazy [03:19] the importatnt thing is if nhandler was able to recruit anyone over to the darkside [03:19] Hey, who are you calling crazy, crazy? [03:19] vorian: Quintasan expressed an interest in packaging the core KDE stuff [03:19] fantastic [03:19] * ajmitch hasn't been seduced by the dark side yet [03:20] we really should get a extras type team together to look after the non-core stuff a bit closer [03:53] nhandler: though art missing from a channel [04:04] what's the differences b/w syslog and messages from /var/log ? [04:16] Heya guys what is the difference between "dh_installchangelogs -i" and "dh_installchangelogs -i Changelog" in debian/rules? === hggdh_ is now known as hggdh [04:23] RoAkSoAx: the Changelog is just specifying the name of the upstream changelog. The -i is unrelated to this, it specifies to act on indep architectures [04:23] the -i option is specified in the debhelper manpage I think [04:23] nellery, k thanks, will take a look at it :) [04:23] there's just no option necessary to specify where the upstream changelog is [04:25] nellery, ok thanks :). Now, should we remove "only in patch2: unchanged:" from debdiff's ? [04:28] RoAkSoAx: diff will ignore those lines, so you should be okay [04:28] ok thanks StevenK :) === Amaranth_ is now known as Amaranth [06:43] good morning [06:43] nhandler: thanks for that great packaging training session! [06:43] who wants to give another session at any of the open dates on https://wiki.ubuntu.com/Packaging/Training ? [07:02] Good mornibg dholbach ! You scared everybody asking for a trainer ;-) [07:20] hi dholbach [07:21] hi ajmitch [07:21] what fun stuff do you have for us today? :) [07:22] ajmitch: I didn't know I was the entertainer for this place :) [07:22] ajmitch: how about doing some sponsoring or giving a session at any of the open dates on https://wiki.ubuntu.com/Packaging/Training ? [07:22] you liven the place up [07:23] yeah, I was talking to nhandler about what he wanted for that earlier [07:23] there's a lot of requests on the page :) [07:23] & I have the sponsoring list open, don't worry :) [07:23] yooohooooo! [07:23] :)( [07:24] 06:00 UTC is about the only timeslot there that'd be suitable for me I think [07:26] of the requests there, maybe the one of packaging a php web app, however I'd probably need a fair bit of time to prepare something suitable, because they can be downright evil :) [07:26] sounds great [07:26] it's completely fine if you just prepare ... say ... 15 minutes of hands-on session and just keep on answering questions [07:27] web apps that require the installation pages to have write access to the directory all the code is in make me cry a bit [07:27] sure [07:27] yeah, I think I know what you mean :) [07:27] * ajmitch had that issue recently with silverstripe [07:27] plus other issues regarding licensing which are a little harder to solve [07:28] plus the usual bundling of "packages" [07:28] yeah [07:29] besides that, I have a php5 merge to redo now [07:29] asomething, bigkevmcd and I are looking into packaging civicrm which has a lot of these problems [07:29] ok... enjoy [07:29] * dholbach will take the dog for a walk [07:29] see you in a bit :) [09:05] DktrKranz: Hi Luca, are you there for a python 2.6 transition question ? :) === ripps_ is now known as ripps [09:13] didrocks: sure, but I'm taken with some things at work, so I could lag a bit [09:16] DktrKranz: no pb :) I'm trying to merge planner which uses pysupport. Nothing special so, I updated .install files but pkgbinarymangler hates me because of files in site-packages... I tried to include /usr/share/python/python.mk without any success. The rules file is here: http://paste.ubuntu.com/203412/ [09:21] didrocks: any *.install files hard-coding site-packages? [09:22] DktrKranz: no, they all have *-packages. Do you want the source package? [09:27] didrocks: that would help [09:28] DktrKranz: dget http://www.didrocks.fr/temp/planner_0.14.4-1ubuntu1.dsc (no hurry, when you have some time to take a look at it :)) === korn_ is now known as c_korn === cjwatson_ is now known as cjwatson [09:59] didrocks: testbuilding [10:01] DktrKranz: thanks :) [10:06] didrocks: mmh, it seems a cdbs bug, but I'll dig it deeper [10:07] DktrKranz: ok, that's what I thought (python stack seems to be broken: if I try to build the current package, I got the same behavior) [10:09] didrocks: [10:09] checking for python version... 2.6 [10:09] checking for python platform... linux2 [10:09] checking for python script directory... ${prefix}/lib/python2.6/site-packages [10:09] checking for python extension module directory... ${exec_prefix}/lib/python2.6/site-packages [10:10] DktrKranz: in the configure traces, yes. I'm currently seeing that. I thought that adding /usr/share/python/python.mk will change the behavior [10:12] didrocks: what about running autoconf? it's hardcoded in configure, recreating it would have some good, I'll try it [10:12] DktrKranz: oh, good idea [10:28] didrocks: that doesn't work, it gets overwritten each time :/ [10:33] didrocks: see debian #524176 [10:33] Debian bug 524176 in automake1.10 "AM_PATH_PYTHON should honor python's idea about the site directory" [Unknown,Open] http://bugs.debian.org/524176 [10:37] hi all [10:40] I have been told to enable boot logging and post the output ( https://bugs.launchpad.net/ubuntu/+source/gnome-power-manager/+bug/389930 ) but this feature has not worked for ages and does nothing in jaunty. Do they just mean /var/log/dmesg ? [10:40] Ubuntu bug 389930 in grub "grub menu skipped after shutdown" [Low,New] [10:40] I really can't see how a dmesg output could help as it never says anything about grub [10:41] DktrKranz: good catch :) [10:42] any ideas? [10:42] didrocks: it has been implemented in Ubuntu already, just I've no enough automake knowledge to understand its logic [10:42] e.g. if there's any AC_* variable to set [10:43] DktrKranz: I will ask doko for it, though [10:43] DktrKranz: thanks a lot for your help :) [10:44] lesshaste: What do you mean by bootlogging? Does it have anything to do with bootchart? [10:46] didrocks, DktrKranz: you need to regenerate the aclocal.m4/configure [10:46] slytherin, no.. I mean bootlogd and /var/log/boot.. see the bug report request by Scoott [10:46] Scott H [10:47] doko: so, autoreconf shoud do the trick? [10:47] yes [10:47] * didrocks testing it [10:49] didrocks: there seems working good [10:49] *here [10:57] Hey, I need a expert MOTU's help, I'm creating an alternative mpd package that runs in the userspace, but if someone has had mpd installed before hand, it's /etc/mpd.conf will interfere. What's the proper way of going about replacing it. I don't think I should just straight out delete it without asking the user [11:00] Indeed, it's working. Thanks DktrKranz and doko :) [11:00] ripps: you can ask a question with debconf [11:01] or move it to another file and show the user a prompt saying what you did [11:01] Laney: any good examples of debconf? [11:02] hmm, not sure [11:02] I think exim uses it and maybe mrtg [11:23] Laney: I see bunch of packages when upgrading ubuntu ask what I want to do with old configs, whether I want to replace, keep, or merge them. How can I get that? [11:23] that's just dpkg conffile handling [11:23] google around for dpkg conffile [11:32] ripps: That has nothing to do with two separate packages sharing the same configuration file lcation tho. [11:32] yeah sorry [11:52] Hmm... maybe ucf can help... [12:15] a package should not modify a config file from an other package [12:17] hm, what package is missing to make ld happy? "ld: cannot find -lfb" I tried the xserver-xorg-core package. [12:18] does it happen during linking? [12:20] yes, http://pastebin.com/d156b2a1f [12:20] hm, maybe this fb lib is some library from the freebasic compiler [12:21] that would be my guess too [12:22] ah, it is in /usr/lib/freebasic/linux/libfb.a so I have to move it to /usr/lob [12:22] *lib [12:23] no, better add -L/usr/lib/freebasic/linux to the linker call/flags [12:24] I lost my wireless (proprietary) broadcom driver in the last kernel upgrade... now I can't get it back... :-( [12:24] the pastebin shows that it tries the right thing but uses /usr/local/lib/... instead of /usr/lib/... [12:26] c_korn: fb could be frame buffer as well. [12:28] mok0: which chipset? [12:28] slythering bmc4312 [12:29] mok0: Does it require binary only firmware? And did you try installing bcmwl package? [12:29] slytherin: When I installed jaunty, I just had to activate the restricted driver in jocket [12:30] mok0: So you are on karmic now? [12:30] slytherin: apt-cache doesn't know it [12:30] slytherin: no, jaunty [12:30] slytherin: I have to get video-drivers from ~ubuntu-mobile to get full resolution [12:31] slytherin: they don't have karmic yet [12:31] mok0: Then you probably lost only firmware, although it should not happen. See if jockey helps you. If not try installing b43-fwcutter. [12:32] slytherin: jockey has nothing in the list .... it did b4 the upgrade [12:33] mok0: paste the output of dmesg on pastebin [12:33] slytherin: uhm... the machine is not on the net :-) [12:33] slytherin: I'm on my workstation now [12:34] slytherin: I can't get wire-net where I am [12:34] mok0: Ok. See if you see any firmware loading problems in dmesg output. Search for b43 [12:34] slytherin: nothing there [12:36] mok0: check if 'lsmod |grep b43' shows anything. [12:36] slytherin: nothing [12:37] mok0: Try 'sudo modprobe b43' and then check dmesg output. [12:37] slytherin: the drivers are not there, and are also blacklisted [12:37] ah [12:37] slytherin: b43 loaded now [12:38] mok0: why is the driver blacklisted? [12:38] slytherin: by default I guess... I commented-out b43 [12:39] Still no drivers in jockey, thoug [12:39] mok0: no it is not blacklisted by default [12:39] slytherin: I never touched that file before [12:39] mok0: Then your chipset probably needs other driver. [12:40] slytherin: I guess... [12:40] the file "blacklist-bcm43xx" is not a part of any package [12:40] so must be generated in config step [12:44] Hello MOTUs, could you please advise. I want to package Cobertura lib. Currently 1.9.1 release is available but I need Cobertura 1.9. Is it allowed to package 1.9 which is tested and stable enough instead of 1.9.1? [12:45] mok0: I am guessing b43 does not support your chipset. [12:45] mok0: in any case, after loading the module, did you check if any wireless connections show up in network manager? [12:45] slytherin: probably not... the problem is I don't know what driver it was running before [12:45] juli_: sure [12:46] juli_: Sure. if 1.9.1 is kind of alpha/beta then it is recommended to package lower but stable version. [12:46] slytherin: nope nothing [12:46] slytherin: could be a regression on the kernel [12:47] It worked right after primary install [12:48] sladen, 1.9.1 is released 4 months ago and it pretends to be final. But I'm not sure about it since some tests fail for me. [12:48] I stayed with 2.6.28-11-lpia because of the graphics, but they updated the psb drivers, and not wireless is gone... [12:48] mok0: do you still have old kernel? You can try booting to that and check which driver it is. [12:48] slytherin: I do [12:49] juli_: some tests as in unit test? Are you packaging the library because some other application depends on it? [12:49] slytherin, netbeans depends on it [12:50] juli_: hmm, then you should package the version that works. [12:50] juli_: just package the version you need [12:50] slytherin, geser thank you! [12:51] slytherin, the graphics are acting up [12:51] ah [12:52] Yep wireless works [12:52] building a package where it gets compiled 4 or 5 times ends up not being fun [12:53] slytherin, now it's using the "Broadcom STA wireless driver" [12:54] ajmitch: so many different flavours? [12:54] geser: yeah, unfortunately [12:55] times like these I think a computer upgrade is overdue :) [12:55] mok0: now you can check which driver was loaded in dmesg output [12:56] slytherin: it's called "wl" [12:58] slytherin: where would that driver be located (filesystem)? [12:58] mok0: 'modinfo wl', you should have path of driver file. then dpkg -S filepath to check which package contains that file. Then see if corresponding package is installed for your latest kernel. [12:59] slytherin: nice tricks I'm learning here :-) [12:59] slytherin: the file is not part of any package [13:00] mok0: impossible [13:00] mok0: what command did you use? [13:00] dpkg -S volatile/ wl.ko [13:01] mok0: you need complete path [13:01] slytherin: same result [13:01] slytherin: it might be compiled in place, or unzipped or something [13:02] slytherin: nvidias drivers are compiled when you install the package [13:02] mok0: Ok. Then it is possible that it is done using dkms. In that case I think you need to install -headers package for latest kernel installed. [13:03] slytherin: yes... I am currently very puzzled... [13:03] slytherin: at least now I know what kernel module I need [13:04] slytherin: but it really should have been re-installed with the new kernel version [13:04] mok0: can you tell em complete path of the module? [13:04] slytherin: I've just been using the update-manager thing [13:05] slytherin: /lib/modules/2.6.28-13-lpia/volatile/wl.ko [13:05] slytherin: sorry that 13 is a 11 [13:05] mok0: this doesn't look like standard path. So you may be right that module is compiled inline. [13:13] slytherin: It might come from linux-restricted-modules-lpia [13:15] slytherin: it does [13:24] mok0: Looks like that package is not in repositories. So if you used some PPA better talk with its owner. In this case you should discuss with #ubuntu-mobile [13:24] slytherin: ubuntu-mobile is only for the psb X-driver [13:25] mok0: still, if there kernel made your wireless go away, you should talk with them. [13:25] slytherin: The package is called linux-restricted-modules and it contains the broadcom stuff [13:25] slytherin: it wasn't their kernel, it was Ubuntu's [13:26] slytherin: from jaunty-update [13:26] mok0: then ask kernel team on their channel to check if they messed anything in the update [13:26] slytherin: I will... thanks a LOT for your help I am much further now === dholbach_ is now known as dholbach === yofel_ is now known as yofel [14:59] slytherin: note that Java-related builds in karmic are currently failing because of bug 392104 [14:59] Launchpad bug 392104 in ca-certificates-java "[Karmic] Update to ca-certificates 20090624 prevents ca-certificates-java from installing" [High,New] https://launchpad.net/bugs/392104 [15:02] ttx: what a timing. I've filed 392103 probably a few seconds before you :) (duped it to your bug now) [15:02] geser: argh :) [15:03] geser: i've a dirtyfix patch on that bug, though I expect Phillip kern to fix it properly in Debian very soon === funkyHat is now known as funkyJackHat [15:18] ttx: thanks for info. === tuantub_ is now known as tuantub [15:47] Heya gang [15:47] Hi bddebian [15:47] Heya geser === funkyJackHat is now known as funkyHat === Amaranth_ is now known as Amaranth [17:25] <\sh> fabrice_sp: ping bug #373873 [17:25] Launchpad bug 373873 in librep "Sync librep 0.17.3-3 (universe) from Debian unstable (main)." [Wishlist,New] https://launchpad.net/bugs/373873 [17:57] Ampelbein: let us know in #ubuntu-meeting when you're back [18:00] Ampelbein: don't worry - you're not confused, we moved the meeting an hour early because anant couldn't attend later on [18:01] does anyone knos how to create a package from scratch without reading the docs or debian n-m-g? :) [18:01] s/knos/know/ [18:06] hope for a godly inspiration [18:24] can I make a sync request here [18:24] since it's the last day? [18:27] micahg: No, the archive admins only take bugs reports. [18:28] ok [18:29] well, let me ask then, do you guys plan on moving in php 5.3 or is it dependent on getting into unstable sometime soon? [18:29] it's going to be released very soon [18:29] and if it's in, will it just replace the current version [18:33] I just want to know if it's worth filing a sync request for 5.2.10 if 5.3 will replace it later [18:38] \sh: yes? [18:38] <\sh> fabrice_sp: is there any update on the debian sync? [18:39] no: the debian maintainer told me that is was working in Debian with PPC and don't see the point of adopting the changes [18:39] and I've not been able to find someone with ppc knowledge to check it [18:40] <\sh> fabrice_sp: well...in case of no PPC knowledge (as I don't have) I would say, let's merge it, and when it's a problem later on, we can SRU it without the change [18:41] and why not doing at at the contrary if Debian is saying there i no issues? [18:41] <\sh> fabrice_sp: because I don't trust the maintainer (he's new) and upstream is not always correct ;) [18:41] I mean sync it from Debian and SRU if it fails [18:41] ok [18:41] I'll do the merge then :-) [18:42] can you just unsubscribe MOTU form there, and I'll update the debdiff [18:42] s/form/from/ [18:42] <\sh> fabrice_sp: do you not have upload powers? [18:43] no: I'm only a u-u-c :-) [18:44] <\sh> Don't get me wrong on my last statement...there was a reason why we had this change to our package...and from my web of trust I do trust our people more then others...but that's just me. [18:44] <\sh> fabrice_sp: ah ok...happy to be your sponsor :) [18:46] cool: I'lll do the merge, and ping you ;-) [18:46] <\sh> fabrice_sp: go for it :) [18:46] Hi, I've got an app I'm packaging which makes use of a library (bundled with the app) where abouts do I credit the author of the lib in the copyright file? [18:46] also, it's under public domain, where would I say that? [18:46] the rest of the app is gpl [18:48] elzary: what do you mean by library bundles with app? [18:48] Can I put the lib developers name in the "upstream authors" section of debian/copyright? or is that reserved for the devs of the app? [18:48] slytherin, I'm not quite sure how else to explain [18:48] elzary: where is the source of the library? [18:49] with the source of the app to be packages [18:49] *packaged [18:49] it's just one .c file [18:50] elzary: You can have multiple copyright/license sections in debian/copyright file. [18:50] bigon: any idea why telepathy-glib failed to build on sparc/powerpc? There is a unit test failure, but I am not able to make out the root cause from build log. [18:50] slytherin, ok thanks, shall I also list the dev for the library as an upstream developer or not? [18:50] or just put his name in the copyright section? [18:50] and not the upstream dev bit [18:51] elzary: you should in my opinion. [18:51] ok [18:52] Are there any conventions I should adhere to when listing the second license? [18:52] or can I just say: Within this application there is a library that has been placed into the public domain? [18:52] and do I need to name the library or give it's location? [18:53] elzary: You can simply say, file.c is placed into public domain [18:53] I dont want to repo admins to be confused [18:53] oh rite [18:53] that should do [18:53] thanks [18:53] I'm just trying to tread carefully in the copyright file [18:53] elzary: you need to specify the path of .c file in the repo. as in folder1/folder2/file.c is in public domain [18:54] yeah [18:54] if something is in the public domain has the upstream dev forfeited any claim to copyright? [18:54] if so I won't list him in the "copyright" section [18:54] or should I? [18:55] <\sh> elzary: you have to...but that's my interpretation between copyright and license [18:55] ok [18:55] THere isn't a date for the copyright though [18:56] I guess I can't really help that [18:56] <\sh> elzary: no webpage? no google fragment on this? [18:58] \sh, yes but [18:58] it only talks about recent developments in the software [18:58] the dev that worked on this version is long gone [18:59] this is an old library, it's had alot done to it since this guy made the release [18:59] <\sh> ask upstream :) they should know what they are using ;) [18:59] ? [18:59] I don't understand [18:59] They aren't relevent [18:59] <\sh> elzary: it's only one or more files which are having a new license...so upstream should know about the history of the used stuff... [19:00] \sh, please excuse my ignorance, I've done alot of reading around packaing and I don't see how your suggestions play a part [19:00] some guy public domained some software years ago [19:00] then someone else took over, re-licensed and re-released an altered version [19:01] <\sh> shermann@buildserver01:~/packages/karmic/dojotoolkit/dojotoolkit-1.3.1$ ls -la debian/copyright [19:01] <\sh> -rw-r--r-- 1 shermann shermann 84794 2009-05-25 07:02 debian/copyright [19:01] <\sh> e.g. this is my copyright file for dojotoolkit... [19:01] yes [19:02] I think I need to re-explain [19:02] I have an application I am packaging, all the copyright stuff is sorted [19:02] except: I have found one file with someone elses name onit [19:02] and a public domain release message [19:02] <\sh> there are only a few files, which are not under the same license as the dojotoolkit itself...so people who are developing upstream software should know about the history of the tools they are using...if there is no copyright date publicly available from webpages or similar, the upstream devs should know since when the guy started it [19:03] So you're telling me to contact them and ask them what year this guy released this file? [19:03] <\sh> elzary: that's the plan, yes :) [19:03] Hypothetically, what if they dont know? [19:04] after all, it has no version number and was released a few years ago by a dev who is no longer around [19:06] <\sh> the version number is not important...dev X wrote a piece of problem solving software, somewhat around year X and release it to the public domain in year Y...public domain doesn't have to do anything with losing copyright...diff between license/usage policy and the work done by dev X (the work done by Dev X will always be his work...even being released under public domain) [19:07] I'm contacting them now, all I know is this library was written AT LEAST 4 years ago [19:07] and the name of the developer [19:08] another quick question, is it right to list this guy as an upstream developer just because one of his libraries(un-beknown) to him is being used> [19:08] ? [19:08] <\sh> elzary: if upstream doesn't know anything else then you, you can state that file/lib XY was developed by Dev X, he has the copyright at least since most probably before ... that's all we can document inside debian/copyright [19:09] I see [19:10] <\sh> as said...lib X can rely on software Y, upstream developer is always of lib X...and upstream is using a software which is (C) by dev Y...so you need to state this...the dev Y has nothing to do with your upstream package..but dev Y can always object against distribution (in the way the license is allowing that) of his source, without even telling upstream about it [19:11] <\sh> that said, software Y is shipped with upstream source ... [19:13] * \sh had problems regarding software being (C) by Dev X , licensed under (L)GPL but patented by Frauenhofer so, there are three different views to discover and a lot of money to be paid ;) [19:13] hy all..i feel so difficult to understand the "packaging" process.. i tried to learn debian's..but that was hard too..so confusing about the different tools and everything.. aarg.. i know to code in java and c/c++..also i can learn any new language as required.. can i be of any help? [19:14] truthordare, it's not perfect but check this out > https://wiki.ubuntu.com/PackagingGuide/Complete [19:14] i almost made a package using debconf.. so confusing..and i have totally forgot [19:14] okay am reading that now.. thanks elzary [19:15] truthordare: debian process is not different from ours [19:15] \sh, there are many ways in which you can word such statements, do the repo admins have a rigid preference or do they just care that it's clear? [19:16] <\sh> elzary: I don't know who our archive admins are today...but regarding some debian packages in the past..I would say, they are sometimes rigid but mostly want a clear statement [19:16] <\sh> debian packages here means really uploaded to debian...not ubuntu [19:17] yeah I'm specifically doing this ubuntu, if it works on debian then so be it. If there are rigid rules on how things need to be worded then there should be docs [19:18] the documents are pretty vague when it comes to anything that isn't totally straightforward [19:18] I'll just make it clear, they can always send it back with comments if there is an issue [19:18] althoutgh i dropped my debian plans.. i actually almost made it..by adopting an orphaned package.. but by the time my mentor asked me for the final package for submission.. i kinda gave it up... then i switched to fedora..but quickly gave it up coz i hated yum more than i hated my ex-gf..i have been using ubuntu since then..been 3 years..i have also been an erly user.. i still have 5.x cd that was shipped to me ;)... [19:18] <\sh> elzary: we are not lawyers, that's the thing :) [19:18] slytherin: maybe ask on #telepathy but it's the same thing on debian [19:19] <\sh> truthordare: building packages for redhat/suse has almost the same quality standards/difficulty level as debian packages (without making any diff between Debian and Ubuntu) [19:20] bigon: just discussed it there. the test is broken on big endian machines. A fix has been committed. I am testing the fix. [19:20] i now run 9.04 64bit + vmware on my workstation rig.. 8gbram, q9550. its a breeze... i just use xp on my laptop..(for playing cod4) [19:21] i hated about yum..was the fact..u could never install pacjages from ur local cd/dvd..u needed to create a yum local repository.. well may be i am wrong..but i could never install a single thing from my dvd's unless i created local hdd repos [19:22] <\sh> truthordare: I would say you don't know the diff between yum & rpm and apt-get/aptitude and dpkg...but could be just me [19:22] and not to mention..a lot of crashes... and my mind was playing games...i couldnt resist putting blame on redhat for each crash i encountered... it was like a beta project.. [19:24] i only use apt-get for all my install needs.. its very convinient... in fedora..i had to use yum and it wasnt yummy for me... i asked many people..but i couldnt solve.. i had to create local repo's(copy of all packages in the dvd into my hdd partition/folder) inorder to install packages with dependencies [19:26] truthordare: fedora is waaay behind getting a sensible dependence treatment in place [19:26]