=== asac_ is now known as asac === pace_t_zulu_ is now known as pace_t_zulu [01:00] vorian, ping [02:15] anyone feel like helping me troubleshoot this package build error from pbuilder: http://pastebin.ubuntu.com/218445/ I have both libboost-dev and libboost_thread-dev installed but it looks like it can't find them [02:17] stochastic: You need to make it use libboot_thread-mt if you are using the newest boost libs [02:17] bddebian, okay I'll hunt that down. thanks. [02:18] NP, just wherever it is linking use -lboost_thread-mt [02:22] I've got a normal 'dh $@' package, but for some reason it can't copy to debian/ . Why is this happening? [02:23] what do you mean with "can't copy"? [02:25] pochu, erm not copy but it can't build into debian/ [02:25] pochu, dh_auto_install: command returned error code 512 [02:27] well, that alone is not very helpful [02:27] how about a pastebin with more context? [02:28] how many binary packages your package builds? [02:28] pochu, just 1 [02:29] if it only builds one, wouldn't it not use debian/packagename? isn't that reserved for foo.install (rather than just install) situations? [02:30] directhe`: if it only builds one, debhelper defaults to debian/ rather than debian/tmp, which is used when there are more than one [02:30] can anyone please review/advocate: http://revu.ubuntuwire.com/p/gnome-gmail-notifier http://revu.ubuntuwire.com/p/lekhonee thank you :) [02:30] pochu, http://paste.ubuntu.com/218457/ if this helps [02:30] Maybe it doesn't support DESTDIR? [02:32] bddebian, I think it does [02:33] this is my Makefile http://paste.ubuntu.com/218463/ [02:35] binarymutant: did you create usr/lib first? [02:36] it seems you didn't [02:38] dirs? [02:43] awesome thanks everyone :) [02:49] I'm trying to build a deb for this software that builds but doesn't install system wide (i.e. it just creates an executable in the local build file) How do I make the deb install it system wide? [02:56] stochastic: If there are no commands in a makefile etc to install the binary, you just ahve to copy the binary into place. [02:57] TheMuso, in a deb that would be done by "cp name /usr/bin/name" in debian/rules? or is it more/less complex than that? [02:57] Thats what you would have to do, yes. [02:58] If you are using cdbs however, you have to do it a different way. [02:58] cdbs? [02:59] I just did dh_make to get the basic deb started [03:00] stochastic: look at dh_install [03:07] stochastic: ok then you just copy the file. [03:08] a|wen: Thats really only useful if there are many many files to copy. If there is only one file, then its probably pointless using it. [03:08] stochastic: Mind you, using dh_install would be useful if there is ever likely to be more files that need to be put into place. [03:09] TheMuso: dh_install and then just point to the single file in rules works well ... i'd say use dh_install always [03:11] TheMuso, a|wen, but whichever method I use, the correct path should be /usr/bin/name [03:11] a|wen: Right, but I always think that if you use dh_install, its much better to use debian/$packagename.install files. [03:11] stochastic: right [03:11] RoAkSoAx: yo [03:12] TheMuso: with multiple files it is ... if we are talking one file, i would just use it in rules [03:12] rules shmules [03:12] who needs em [03:12] a|wen, TheMuso, thanks. [03:13] vorian: you almost get your wish ... getting close to doing without the file with dh7 ;) [03:14] a|wen: Yes but using install files from the get go allows for much less work when more files need to be copied. [03:14] TheMuso: true ... but using cp in rules instead of dh_install doesn't help on that :) [03:15] Yeah I know. So use whatever you wish stochastic. [03:30] TheMuso, when I try to use "cp name /usr/bin/name" I get a "Cannot create /usr/bin/name: Permission Denied" error while building. Here's the full build output if that helps: http://launchpadlibrarian.net/29030820/buildlog_ubuntu-jaunty-i386.xwax_0.5-0ubuntu1~ppa~jaunty3_FAILEDTOBUILD.txt.gz [03:30] is that because it's using cdbs? [03:31] a|wen ^ (looks like TheMuso just left) [03:34] stochastic: it is not located in /usr/bin/name when building, but in (build-dir)/debian/name-of-package/usr/bin/name [03:34] stochastic: dh_install takes care of all that automatic ... another reason for using that over cp [03:35] a|wen, if I use dh_install how do I format the specification of which file to move? [03:36] is it just like "dh_install name /usr/bin/name" [03:36] that should work [03:36] or "dh_install name usr/bin/" [03:43] vorian, heya hwo's it going? [03:58] stochastic: have to go now ... if you haven't got it working, just speak up in here; there is probably some other people who can help out === ApOgEE__ is now known as ApOgEE [04:50] Hello, is CC-BY-ND a non-free license ? [04:50] Attribution-No Derivative [04:51] pochu: I was asking about the virtual machine so I could try and fix my first bug, I'm a prospective MOTU. Is this really the wrong channel? [04:51] Sounds non-free to me. [04:51] Also, CC licenses are crap. [04:51] Thanks for the help though, I'll try #ubuntu-server. [04:51] They point towards this totally vague and incomplete motherhood license. [04:52] RAOF: One of the reasons a package has to include a full copy of the license in the tarball. [04:54] AnAnt: ND is definitely going to make it non-free; we're unable to alter it. [04:54] AnAnt: Absolutely what RAOF said. [04:54] ok [04:55] evanrmurphy, what do you wanna do? [04:58] RoAkSoAx: I was trying to decide whether to set up KVM or VirtualBox to run a VM of a different Ubuntu release. I noticed that KVM seemed to be preferred for various reasons, but that it always comes with the warning of needing a processor with VT extensions. [04:59] evanrmurphy, I'm running KVM in a non VT processor and works fine but kinda slow [05:00] evanrmurphy: I use VirtualBox for the same reason... no VT here... so it seems different folks take different approaches to this :) [05:01] RoAkSoAx: Ah, that's good to know. Do you remember choosing between running paravirtualization and full virtualization (or something like that)? [05:02] jmarsden: I appreciate the response, glad I'm not the only one. :) [05:02] evanrmurphy, I actually don't remember :) sorry :( [05:02] RoAkSoAx: Don't worry about it. Thanks all for the help! (Off to bed.) [05:03] how about CC-BY ? [05:04] http://creativecommons.org/licenses/by/3.0/legalcode [05:04] Attribution [05:04] AnAnt: http://wiki.debian.org/DFSGLicenses [05:05] RAOF: thank ! [05:05] RAOF: thanks ! [05:05] evanrmurphy, night :) [05:07] AnAnt: Note the bit under the "CC-BY-SA 2.5 is DFSG incompatible" has a statement that the ftpmasters are OK with CC-BY-SA 3.0 [05:07] RAOF: and CC-BY 3.0 too [05:08] Ftpmasters have already accepted CC-by and CC-by-sa 3.0 [05:08] Right. [05:09] thanks for that wiki link [05:12] nhandler: would you please have a look at bug 389654 when you have time and leave a comment [05:13] Launchpad bug 389654 in lyricue "Please upgrade lyricue" [Wishlist,In progress] https://launchpad.net/bugs/389654 [05:13] porthose: Yeah, although it might need to wait until tomorrow, I'm heading to bed soon [05:14] nhandler: works for me gnight [06:04] good morning! While merging a package (pilot-link), I've found a .udev file in debian directory, but it doesn't seems to be installed in any package. What is it for? [06:20] other question: what should I do if the changelog's entries for Ubuntu has been lost in previous merge? Should I restore them or respect the previous merger choice (pitti)? [06:27] Is there a way to tell why ganglia-monitor wasn't auto-synced into karmic before DIF? (Bug #302640) [06:27] Launchpad bug 302640 in ganglia-monitor-core "Please sync 3.1.1-1 from experimental" [Undecided,New] https://launchpad.net/bugs/302640 [06:28] btm: We don't sync from experimental by default. [06:28] wgrant: it's in testing now actually. [06:28] wgrant: although the date of that change may have something to do with that. [06:29] wgrant: it was just in experimental six months ago when I opened that bug. [06:29] btm: You mean the 'ganglia' source, not 'ganglia-monitor-core'? [06:30] It entered unstable a day under two weeks ago. [06:30] After DIF. [06:30] word, yeah, that makes sense. [06:31] IS the perl artistic license compatible with Ubuntu? [06:31] I believe we have lots of perl code under said licence in Ubuntu already [06:32] wgrant: so I should track someone down who'll issue an FFE? [06:33] micahg: The Perl license isn't really a license of its own, IIRC. [06:33] But Artistic License 1.0 and 2.0 are DFSG-free. [06:34] btm: No - you just have to request a sync. [06:34] btm: DIF is just when automatic imports stop. No exception is needed until FF. [06:36] wgrant: got it. i'll edit that bug [06:38] Hey everyone, I've found a tutorial that walked me through writing my first man page for this package I'm working on, but now I'm wondering if there's any adjustment to debian/rules that's needed to make sure the binaryName.1 files are installed to the right place? [06:41] stochastic: dh_installman, if using dh 7 should be automatic [06:42] porthose, and as long as the binaryName.1 files are inside the debian/ subdirectory everything will be golden? [06:42] stochastic: yes [06:47] stochastic: you may need to add binaryName.manpages file to the debian dir [06:48] porthose, do you know of any howto or help page in the wiki that can walk me through this? [06:48] have a look at man dh_installman [06:54] Does anyone want to do a revu of http://revu.ubuntuwire.com/p/a2jmidid ? The latest update fixes all the issues fabrice_sp had touched on last time. [06:59] stochastic, did you test build the package and run lintian on the deb? [06:59] fabrice_sp, pbuilder is working away right now [07:00] fabrice_sp, would you like me to upload the latest to my PPA for a more public build/test ground? [07:02] just run lintian on the resulting deb: that would throw all 'basic' errors. Any reviewer should build the package, anyway, so no need to upload to a ppa [07:04] fabrice_sp, now lintian is telling me that binary-idep is a required target, but you had told me to delete those targets... [07:04] <\sh> moins [07:05] stochastic, hmm, I think I told you you to empty them [07:05] \sh, moins [07:05] my misunderstanding [07:06] statik, before writing my comments, I thought about it, but remember that they should exist :-) [07:06] You just confirmed me that :-) [07:06] sorry statik, , not for you [07:06] stochastic, ^ [07:10] fabrice_sp, lintian is also telling me that there's no manpages for items I have manpages for, and that it doesn't have a copyright file when clearly it does. Any hints on how to fix these warnings? [07:14] check that you have dh_installman called, the file .manpages in debian. For copyright, perhaps you miss a dh_installdocs call? [07:14] stochastic, ^ [07:18] fabrice_sp, you told me to get rid of dh_installdocs because there were no docs to install [07:19] stochastic, my bad: it installs automatically the copyright file. sorry [07:19] (checked with man dh_installdocs [07:20] fabrice_sp, in the .manpages, is it just a listing of the manpages to install or is there further formatting that is needed? [07:20] this is the proff that I still have a lot ot learn! [07:20] stochastic, just the list [07:20] but the full path [07:20] for example: debian/man/pilot-undelete.1 [07:21] well, the relative path [07:21] one path per line? [07:22] yes [07:22] path + file per line [07:23] good morning [07:24] stochastic, actually, of you want to check what this command is doing during the build, you can export DH_VERBOSE=1 at the beginning of your rules file [07:24] Hey dholbach ! [07:24] stochastic, have to go now, but you can still ask questions here. bye [07:25] hey fabrice_sp [07:59] can someone help me get dh_installman to work for me? it's man page is not helping me and thats all anyone has been able to point me to so far. I just need to get four simple man pages installed but it's not working. [08:07] stochastic: Whats happening exactly? [08:10] TheMuso, this is the latest error: http://pastebin.ubuntu.com/218642/ [08:11] stochastic: what does a2jmidi.manpages contain [08:12] TheMuso, the contents of debian/a2jmidid.manpages http://pastebin.ubuntu.com/218644/ [08:12] Hrm ok my guess is the manpges themselves are not written properly/malformed. [08:13] one or more of them [08:14] TheMuso, here are the contents of the four manpages: http://pastebin.ubuntu.com/218645/ [08:15] ahh, I think I see the last one is missing the .TH header [08:15] wait, nope, it's there [08:16] could it be that I'm calling dh_installman improperly? === ripps_ is now known as ripps === cjwatson_ is now known as cjwatson === ogra_ is now known as ogra === ember_ is now known as ember [11:34] If an app works both from terminal and from GUI, what's the best option for the needs: field in debian/menu? [11:46] warp10: is debian/menu still used? [11:48] slytherin: maybe on some kind of very old machine. In any case, I'm packaging a software for Debian, and a menu file doesn't hurt [11:48] warp10: what does 'old machine' have to do with it? [11:50] slytherin: I just mean that a tipical machine uses a .desktop files based menu system, and I expect that menu files based ones are more common on machines that are not that recent [11:53] warp10: Your choice. I wouldn't create menu file if I was packaging from scratch. [12:07] could someone have a look at my packages? Would like to have them in karmic: [12:08] http://revu.ubuntuwire.com/p/swtcalendar [12:08] http://revu.ubuntuwire.com/p/willuhnutil [12:09] http://revu.ubuntuwire.com/p/h2database [12:09] http://revu.ubuntuwire.com/p/willuhndatasource [12:37] how do i deal with patches that need to modify autotools files (configure.in, Makefile.am etc)? [12:38] do i need to include the resulting changes to "configure" in the patch, or is there a way to trigger regenerating this one via boostrap / autogen.sh ? [12:45] Are the MC going to send a coordinated response to the new application process? [12:45] hhb: There are two common ways - include a patch with the results of rerunning the autotools stuff, or running it at build-time (make sure your clean target works properly if you do this) [12:47] hm, i think i'll try the first option first. thanks. [12:47] Laney: I guess will we discuss it today on our weekly MC call [12:50] geser: cool. Might be nice to invite wider comment? === proppy1 is now known as proppy [12:53] Laney: will mention it, but feel free to comment on your own [12:54] might just do that [12:59] just a stupid question on revu: the Warnings telling "The GPL is mentionned in debian/copyright, but ... not in source ..." is not a showstopper? (some packages are uploaded without it. I reckon this is because we have the copy in our debian FS). And this is an added check to lintian (lintian file size is 0 and we still see this warning)? [13:00] I thought that upstream were supposed to include a copy of the GPL [13:01] yes, I think that, but some package are accepted without having it. That's why I wanted to be sure about the policy we have (and I'm surprised that this is not a lintian check) [13:02] ask an archive admin ;) [13:03] yes, that's a possibility :) [13:03] every source package is required to have a verbatim copy of the license text [13:04] conquently, some packages are wrongly advocated [13:09] didrocks: No, some packages simply name the license file differently. Or they are located in a sub folder. [13:10] didrocks: revu checks for presence of LICENSE or COPYING file AFAIK. [13:11] slytherin: ok, thanks for the update. Are there somewhere listed the additionnal control made by revu compared to lintian? [13:17] didrocks: You can ask revu hackers, or if you are brave enough check revu code on launchpad. [13:18] slytherin: I will have a look, thanks :) [13:26] <_andre> would anyone like to review/recommend the following packages? http://revu.ubuntuwire.com/p/watchcatd http://revu.ubuntuwire.com/p/libwcat http://revu.ubuntuwire.com/p/libapache2-mod-watchcat [13:27] <_andre> they're lintian/revu clean [13:28] <_andre> i finally managed to convince my boss to move our servers to ubuntu, and these packages are fundamental for our web servers [13:28] <_andre> :) [13:33] Hi, I'm using reprepro to manage a repository, and I'm getting "gpgme gave GPGME error: Bad passphrase". I don't have GUI access to use seahorse, and it seems that I'm unable to get gpg-agent to cooperate with reprepro... Any help? [13:46] OK, got it :) [13:50] james_w: I've just uploaded Zeitgeist again, I'd appreciate if you could take a look at it :) [13:51] RainCT: I'll take a look after lunch [13:51] james_w: Great, thanks. [13:54] what is this Zeitgeist I keep hearing of? [13:59] LarstiQ: http://bloc.eurion.net/archives/2009/zeitgeist-is-out/ :) [14:00] RainCT: thanks! === dholbach_ is now known as dholbach [15:01] ttx: ping [15:02] slytherin: pong [15:02] ttx: pm? [15:02] slytherin: sure === proppy1 is now known as proppy === mterry_ is now known as mterry [16:02] nn/win 20 [16:17] has anyone familiar with intltoor ever happened to see something similar to http://launchpadlibrarian.net/29048481/buildlog_ubuntu-karmic-i386.kupfer_0%2Bc3-0ubuntu1_FAILEDTOBUILD.txt.gz? [16:51] dholbach: Need to move my UDW talk to friday, going to be at a conference the rest of that week [16:51] anyone want monday 1800? [16:52] Laney: are you happy with any of the slots still available? [16:52] Friday's ones are fine [16:52] Laney: then just move it [16:52] that's fine [16:52] alright [16:52] I'll update it in the booklet thingie [16:53] * Laney goes cross-eyed at wiki table syntax [17:24] Hey.. what means the "Done" queue on lunchpad? https://launchpad.net/ubuntu/karmic/+queue?queue_state=3&queue_text= . Done means accepted by the archive admins? rejected?? [17:30] cpscotti: "done" means that processing of the file is finished, i.e. accepted, built and published. [17:31] Ampelbein: thanks! [18:14] Hi [18:14] How do I teach pdebuild about karmic until a proper fix is released? -> bug 399830 [18:14] Launchpad bug 399830 in pbuilder "karmic pdebuild is unaware of the Karmic distribution/release" [Undecided,New] https://launchpad.net/bugs/399830 === Laibsch1 is now known as Laibsch [19:01] I'm browsing the harvest list because I want to fix my first bug. Would any bug I work on be for the development release, or does it depend? Thank you. [19:07] evanrmurphy: Bugs are usually fixed first in the development release (i.e. Karmic right now) [19:07] They may later be backported to stable releases [19:07] Laibsch: Thank you! === boshhead_ is now known as boshhead [20:40] Hello @all [20:41] is there someone who likes reviewing http://revu.ubuntuwire.com/p/h2database ? [20:52] Sorry that I ask this, but is it really the right way here to get packages in Ubuntu? [20:55] therm, yes. but auditing packages is lengthy and boring work, so you need to rely on someone with the appropriate knowledge to take their free time and spend it reading copyright [20:58] broadly speaking it looks okay, given i have no java skill - but i'd strongly recommend relicensing your debian/ to something else, i.e. the same license as the app itself, to eliminate the big revu warning [20:59] directhex: I know that this is much work, but I have feeling that no one really cares about the packages uploaded on revu. I would like to help later when my experience is greater, but for now I am waiting every day that some on gives a comment for my packages so that this might be in karmic [21:00] therm: The other option is to get it into Debian and then we sync from there. [21:01] therm, there's your comment. due to the licensing of debian/ you now have to worry whether the contents of debian/patches/ which are GPL can be linked against the rest [21:01] which just causes issues [21:01] oh, and the current standards version is 3.8.2 [21:01] directhex: thank you very much [21:02] therm: the best option IMHO is to find a team in Debian/Ubuntu that cares for the area your package is in [21:02] ScottK: I heard of that but never found a website wich is telling the process, like revu for ubuntu [21:02] you are likely to get faster and better reviews then [21:02] therm: Look at mentors.debian.net [21:03] ScottK: thanks I will read it [21:03] I've found that to be an even worse black hole, fwiw [21:04] "talk to the java team" is what Laney is saying [21:04] yes sir [21:05] Laney: would like to do that but dont now how^^, the only one I had contact to was https://launchpad.net/~onkarshinde [21:06] therm: google "debian java team" and find an IRC channel or mailing list [21:06] or ubuntu java team [21:07] ok thanks [21:22] nellery, ping === so is now known as simon-o === ajmitch_ is now known as ajmitch === RoAk is now known as RoAkSoAx [22:07] Hey guys. I'm updating a package. The new version contains hidden folders: ".svn". Should I remove those hidden folders from the source directory and tarball? [22:07] RoAkSoAx: yes and tell upstream [22:09] sebner: you'd remove them from the orig? [22:09] sebner, Ok. will do thanks :). What about the debian directory provided by upstream? (It's adding entries to the changelog for Hardy, because they have seen to be doing their tests in a Hardy box) [22:09] urgh [22:09] Laney: sure, you donÄt? [22:09] no I wouldn't repack for that [22:09] Laney: gnah see. Upstream debian folder too [22:09] lovely upstream [22:10] sebner, So i should remove upstream debian directory too in this case to not have those changelog entries? [22:11] RoAkSoAx: Upstream *should not* provide a debian directory. That's packagers job [22:13] sebner, right. They also provided the debian dir on the previous version. I just don't know how to handle that in this case, because it seems that in the previous version, Debian has removed the debian/ dir to create their own. I'm updating ipvsadm btw [22:14] RoAkSoAx: that's the prefered way. You can do that by implementing a get-orig-source rule in debian/rules but collaborating with debian is the most prefered way :) [22:15] sebner, Ok. Will talk to debian maintainer then :). Thanks a lot [22:17] np. let's have fun =) [22:18] Hi. gpiv is building fine in a clean chroot (using sbuild). Is it possible to relaunch the building of this package? [22:18] According to http://qa.ubuntuwire.com/ftbfs/, it's failing to build [22:20] yes, a "give-back" to the buildds [22:21] geser: \o/ [22:21] and who can do that? Motus or it has to be an archive admin? [22:22] anyone who can upload to that component [22:22] so MOTUs for universe/multiverse and core-devs for everything [22:22] ok [22:23] fabrice_sp: done [22:23] as gpiv is in universe, shall I assume you will do it? :-D [22:23] great! tahnks :-) [22:25] 6 hours to go for amd64 build, but only 8 minutes for i386 ?! [22:26] PPA or main archive? [22:28] main archive: gpiv [22:28] by the way: this error is suppose to be fixed ,right? : dpkg: error processing ca-certificates-java (--configure): [22:29] yes [22:29] so could you please force the rebuild of jabsorb package? :-D [22:29] hmm, the queue doesn't look that long for both i386 and amd64: [22:30] https://edge.launchpad.net/builders/ [22:30] fabrice_sp: have you checked that it builds not and not fails due to an other reason? [22:31] good point geser: I'll sbuild it locally before [22:32] Can someone point me to any docs about package configuration (ie. how to have something show up when dpkg-reconfigure is run)? [22:41] geser, you were right: it FTBFS because of a missing dependency (it seems to miss package javax.servlet). Will have a look tomorrow. bye [22:49] * RainCT tries debconf-doc [23:34] i'm not aware of the right procedures, who to poke etc. basically silc-* in hardy has a security vulnerability, debian old-stable has a version which fixes this issue, there's a bug on launchpad and no action. [23:34] so, what's next? [23:37] kwadronaut: Make a patch (debdiff preferred) and attach it to the bug. [23:37] Make sure the ubuntu-security team is subscribed to it and mark it in progress after it has the patch. [23:39] ScottK: pulling from 'upstream' debian is not an option? [23:40] we need a minimal patch to fix the issue [23:41] kwadronaut: If you look at the diff between the old-stable version that's fixed and the one before that's not fixed you should be well on your way to having a minimal patch. [23:48] ok, thanks for the info