[00:00] I think I have fixed the problem but my question is if i should file that as a seperate bug in LP or post as part of the merge request [00:01] Part of the merge [00:02] ok thanks ScottK === binario_ is now known as BiNaRi0 === coppro_ is now known as coppro === emma_ is now known as emma [03:04] if a package i merged failed to build on two different architectures should I open two bugs in lp or just one? [03:04] also what should I do if I (think) I have found fixes for the problem but cant build since I don't have those architectures? [03:21] emgent: ping [03:21] pong [03:21] emgent: Why don't you have anyone seeding the nubuntu torrent? [03:22] it`s fresh upload [03:22] emgent: Ok, so someone will be seeding it soon? [03:22] anyone for REVU? [03:22] use mirror :P [03:22] emgent: I will. I normally prefer to use a torrent, but I guess a mirror will have to do [03:23] nhandler: yeah, but i suggest to use download button [03:41] hi guys [03:41] can someone please do a new build of evolution? [03:41] for hardy [03:41] ? [03:41] because the one supplied doesn;t work with exchange :( [03:42] i mean newer than the version supplied (2.24.2 ?) [03:43] or soemone help me build the src package from jaunty in my hardy installation [03:46] !backports | freakabcd [03:46] freakabcd: If new updated Ubuntu packages are built for an application, then they may go into Ubuntu Backports. See https://help.ubuntu.com/community/UbuntuBackports - See also !packaging [03:48] a package I merged FTBFS on the ia64 and sparc architectures [03:48] i found some fixes from upstream and patched the package [03:49] i dont run those architectures though so i can testbuild [03:49] cant* [03:49] how should i proceed? [03:50] serialorder: good questoin. [03:51] Hobbsee: bad answer [03:51] hehe no im just joking [03:51] serialorder: i'm still thinking. [03:51] serialorder: what you can do is ask on the list if anyone's got some hardware that you can get an ssh account on, to run it [03:52] you can try putting it in the sponsorship queue, but it's likely that it'll sit for a while, as most people will be in your situation [03:52] Or put your source somewhere and say "Please test build this" [03:52] (they don't have the HW, they don't have the technical knowledge to check if it's correct) [03:52] that too [03:55] ok i guess I will try and find a home for it somewhere and send a request to the list to test build [03:59] NCommander: You got IA64? [03:59] I have access to one [03:59] https://bugs.launchpad.net/ubuntu/+source/protobuf/+bug/308829 [03:59] Launchpad bug 308829 in protobuf "protobuf 2.0.2-1 (universe) FTBFS on ia64 and sparc" [Undecided,Confirmed] [03:59] NCommander: Need to test an FTBFS fix ... [04:00] i actually have to leave now, library is closing on me [04:01] thanks for the help [04:01] cya serialorder [04:01] * NCommander looks for his IA64 keys [04:01] ill probably be back tomorrow =) [04:16] Anyone from SRU awake? === root is now known as Guest57157 === Guest57157 is now known as dcypherd [05:08] hey ppl I had a couple of packaging questions [05:10] are programs like aircrack-ng and metasploit not in the repos because someone needs to make them or are there other reasons [05:10] ? [05:15] dcypherd: aircrack-ng has been in universe [05:15] (since feisty from the looks of rmadison) [05:16] dcypherd: you may wish to inspect nubuntu for packages such as metasploit [05:16] thx [05:17] forgot about nubuntu [05:20] dcypherd: see also debian 323420 for metasploit's itp [05:20] Debian bug 323420 in wnpp "advanced platform for developing, testing, and using exploit code" [Wishlist,Open] http://bugs.debian.org/323420 [05:55] iulian: Hi, are you planning on doing the httrack merge? [07:09] good morning [07:11] morning Daniel! [07:11] nellery: Please do it. I took a peek at it yesterday and obviously forgot about it. [07:11] Good morning Daniel. [07:11] iulian: thanks a lot [07:12] Thank you. [07:13] hi fabrice_sp [07:14] :-) How are you doing this morning? [07:15] very good - how are you? [07:15] Very good also, thanks :-) [07:16] Just have to leave to go to work :-/ [07:16] bye [07:18] fabrice_sp: have a great day! [07:26] good morning [07:26] Heya geser. [07:27] stgraber: CONGRATULATIONS! [07:38] morning o/ === dholbach_ is now known as dholbach === jmarsden is now known as jmarsden-the-mag === jmarsden-the-mag is now known as jmarsden-magicia [09:17] "libdmtx 0.6.0-1 is in Ubuntu already" - it wasn't when I filed the bug with the patch :) === jmarsden-magicia is now known as jmarsden [09:20] mgdm: for sync (overwrite current ubuntu package with newest from Debian) requests, just use https://wiki.ubuntu.com/SyncRequestProcess the next time :) [09:20] (so you don't need to attach a patch to it) [09:20] dholbach: Nice one, thanks. I didn't know about that, and did the patch for practice anyway [09:20] anytime :) [09:21] I have another couple of things that aren't in Debian to do though [09:22] https://wiki.ubuntu.com/SponsorshipProcess [09:24] I have read that one, my current issue is a bizarre build system in one of them [09:24] ah ok [09:25] with luck I'll get them done tomorrow [09:25] well, sent to REVU anyway [10:30] * norsetto wonders why its so quiet in here ... === boshhead_ is now known as boshhead [10:42] * dholbach hugs norsetto [10:42] hey norsetto [10:43] * norsetto hugs master mixer dholbach back :-) [10:43] :) [10:43] how are you doing? [10:44] dholbach: fine, at least I will be at home for a couple of days === spacey_ is now known as spacey [10:45] dholbach: and you? Still freezing in Berlin ? [10:45] yeah, it's 4°C here [10:45] but I'm fine :) [11:01] hi dholbach, norsetto! long time no see! :) [11:01] hiya DktrKranz [11:01] norsetto: how about Tiber and rivers? [11:04] norsetto! [11:07] DktrKranz: Glou, glou, glou :-) [11:07] mok0: hey!!! [11:08] norsetto: \o/ [11:09] mok0: I must confess something to you, something really really shaming ... [11:09] norsetto: don't drink Tiber, or you'll get drunk soon. If you want your driving license to get burst, have some beer instead! :) [11:09] * DktrKranz is looking at Po right now, hoping not to "glou glou glou" himself too [11:09] sebner: hi seb! [11:09] norsetto? [11:09] norsetto: +ner ^ ^ [11:10] norsetto: long time no see. how are you? =) [11:10] DktrKranz: drink and drive ^^ [11:10] mok0: you know, you convinced me to use emacs, and I actually LIKE it [11:11] sebner: pretty fine, and you? [11:11] norsetto: :-) [11:12] norsetto: It has some really nice debian modes too [11:12] norsetto: did you install those? [11:12] mok0: yes, I saw your bug on emacs-goodies-el :-) [11:13] norsetto: hehe [11:13] It's a one-byte patch :-) [11:13] mok0: those are the hardest ones ;-) [11:14] norsetto: some days ago we had 3meters of snow ^^ my poor back. :( geeks are poor ^^ [11:14] norsetto: yeah, several kilobytes of overhead [11:14] sebner: must be cool going to school by skying [11:14] sebner: why bother? snow melts you know [11:15] sebner: here they are going to school by boat now ... [11:15] norsetto: heh, well, I finished school in summer already [11:15] mok0: sure but when there are already 2 meters of snow and you have to put another meter somewhere ... [11:16] what is a good way to check a build package? On a video tutorial I saw: less /var/cache/pbuilder/result/package.deb but that doesn work her [11:17] sebner: I see your point... perhaps: cat snow > /dev/null [11:17] sebner: oh well, going to work then, or whatever else is it you up in the mountains once school is over ... [11:18] mok0: I'll tell the snow next time [11:18] sebner: yeah, just stand there with the pipe while it's snowing [11:19] norsetto: heh, currently (since 2 months) I'm on vacation ^ ^ Next month I'll start my basic military service [11:19] mok0: xD [11:19] * norsetto stands on attention and salutes [11:19] sebner: uh oh [11:20] norsetto: no mercy? =) [11:22] ?? [11:22] DktrKranz: see, you should do some time in the army too, it will straighten your dorsal spine ... [11:26] DktrKranz: hahaha! [11:26] jack_: what do you mean by check, checking the build log or the content of the resulting binaries? [11:27] norsetto, Iḿ not sure... [11:28] I saw it in the youtube tutorial... [11:29] jack_: well, no idea what tutorial is that, in any case, for the first case you have to tell pbuilder to log into a log file (I think --log its the option for that) [11:30] jack_: the latter case use dpkg -c on the resulting .debs (deb is the extension for our binary packages, can' t use less on those) [11:30] you give the --log option when building with pbuilder? [11:31] jack_: right, but don' t quote me on that, I'm not on my machine now, can't check it myself (you can check it by doing man pbuilder on yours) [11:31] ok [11:32] I also saw this command, but couldn t see what it was exactly, it was used to check the people with copyright or who worked on the app [11:32] find . -name '*.C' | xargs heac | less [11:32] jack_: man is your friend (ok, I'm old fashioned but even a youngster like mok0 should agree...) [11:34] licensecheck [11:34] jack_: err, you know what a pipe is? [11:34] norsetto, no [11:35] puff puff [11:36] a puff puff, yes I puff know [11:36] jack_: if you're talking about dholbach's tutorial on YouTube, he was using licensecheck [11:37] mmh ok... [11:37] then he did it nicely hidden.... [11:37] jack_: maybe you should read something like this: http://www.ee.surrey.ac.uk/Teaching/Unix/ [11:39] jack_: find . -name '*.C' | xargs head | less will list the first 10 lines of every file that ends with ".C" [11:39] ok [11:39] jack_: and display it in the pager [11:41] ok, I'll check the teaching link... [11:41] one question remains... [11:41] jack_: pls. do, it will help you a lot I think [11:41] let assume there is a outdated package in Ubuntu, for example https://launchpad.net/ubuntu/+bugs?field.searchtext=nted&orderby=-importance&search=Search&field.status%3Alist=NEW&field.status%3Alist=INCOMPLETE_WITH_RESPONSE&field.status%3Alist=INCOMPLETE_WITHOUT_RESPONSE&field.status%3Alist=CONFIRMED&field.status%3Alist=TRIAGED&field.status%3Alist=INPROGRESS&field.status%3Alist=FIXCOMMITTED&field.assignee=&field.bug_reporter=&field.omit_dupe [11:41] s=on&field.has_patch=&field.has_no_package= [11:42] wow.... [11:42] I mean for example the package nted on launchpad... [11:42] https://bugs.launchpad.net/ubuntu/+source/nted/+bug/253378 [11:42] Launchpad bug 253378 in nted "Please update to latest version (1.3.0)" [Undecided,New] [11:43] jack_: just give a bug number, ubotu will fetch the link for you [11:43] Let assume I want to have a newer version and maintain it.... how can I do it? [11:43] maintain = keep it up to date in Ubuntu [11:45] jack_: well, you would have to prepare the update, subscribe the sponsors for approval, and then subscribe to the package to keep up to date with bugs [11:46] and is an update only for the new version of Ubuntu or can I ask for an update in Intrepid? [11:47] jack_: only for the current development version (right now jaunty). But once there a backport can be looked up [11:48] norsetto, ok, so if a package is in the development release (jaunty) a backport can be looked up, or is it only possible after jaunty is official released? [11:49] jack_: once is there it can be done [11:50] norsetto, ok thanks. Where can I find info how to make a backport package? [11:50] jack_: hmm, I don' t have links here readily available, just a sec [11:51] k [11:52] jack_: its a new page (the one I remembered was on the wiki) but this should do too: https://help.ubuntu.com/community/UbuntuBackports [11:52] norsetto, ok thanks! [11:52] jack_: np [11:54] I like the system to build a chroot and be able to build packages. Are they build kernels for different computers the same way? By building a chroot? Where can I find info about it? [11:55] or contact people about it [11:56] jack_: I guess you talk about cross-compiling [11:57] norsetto, I mean, for building a kernel you have a lot of (-dev) packages installed isn t it? so do solve that problem with a chroot? [12:05] jack_: I don' t think that you need a lot of stuff to build a kernel actually [12:05] norsetto, ok I'll check it out.... [12:06] jack_: at least from memory (last I build one was more than a year ago) [12:08] k [12:32] tseliot: Hola! How is the nvidia wizard doing? [12:33] norsetto: I'm trying to recover from jet-lag but otherwise I'm very happy about how the UDS went [12:34] tseliot: was it better than the one in Prague? [12:35] norsetto: definitely [12:35] tseliot: glad to hear that [12:35] can you use prevu to build official backport packages? [12:38] http://ubuntuforums.org/showthread.php?t=268687 [12:40] ok I see the answer is yes... [12:40] how do you use pbuilder to make a backport package? [12:47] dholbach: thanks [12:50] * nxvl HUGS norsetto [12:52] nxvl: hola bandido! [13:13] jack_: you need to specify the -proposed repo in the --othermirror switch [13:13] jack_: if I understood your question [13:14] mok0, and how can I do that? [13:14] jack_: if the package you are building is for backports, you need to put that in the changelog entry: e.g. interpid-backports [13:15] mok0, ok and do I use the jaunty version of the package? How do I get that package? [13:16] jack_: eerrr what package? The one you're building? [13:16] mok0, there is already a package of the version in Jaunty which will be backported... that package [13:17] or do you use just a tar.gz file from the makers website? [13:17] jack_: and you want to backport it to intrepid? [13:17] mok0, yes [13:17] jack_: https://help.ubuntu.com/community/UbuntuBackports#Source%20Change%20Backports [13:18] jack_: make a new changelog entry describing the backport [13:18] jack_: and name the version like it is described in that document [13:18] jack_: then you need to see if it builds AND works on the target distro [13:19] mok0, ok but Iḿ not a Motu, and I just use the tar.gz? [13:19] so nothing with the Jaunty package? [13:19] jack_: you have the package from jaunty, I presume [13:19] mok0, how do I get that? [13:19] jack_: you add this changelog entry to the jaunty package [13:20] jack_: go to packages.ubuntu.com [13:20] jack_: get the source package (3 files) [13:20] mok0, ah, not the deb [13:20] jack_: no the source package [13:20] jack_: it includes upstreams tarball [13:21] mok0, .dsc, orig.tar.gz and diff.gz? [13:22] jack_: yes [13:22] jack_: in fact all you need to fetch is the .dsc [13:22] jack_: then use dget -xu [13:22] mok0, ah ok, I see... so it's almost the same as updating a package? [13:22] jack_: yes [13:23] mok0, could you describe the steps for me? [13:23] jack_: except the newer version may have dependencies that are not available in the older distro [13:23] jack_: and that's what you must check to make sure it will compile [13:23] mok0, and what to do in that case? [13:23] jack_: then you can't backport [13:24] mok0, ok [13:24] jack_: time is unidirectional, unfortunately :-) [13:24] mok0, here are some notes for updating a packages: http://pastebin.com/m1ec1eceb [13:24] jack_: but often it will work [13:24] mok0, :) [13:25] mok0, what is different between the notes and backporting? [13:25] * mok0 looks [13:25] jack_: there are several differences [13:26] jack_: but it depends what version of Ubuntu your are working on [13:26] jack_: in a way, backporting is simpler [13:26] mok0, ok, now on Intrepid... [13:27] jack_: ok, so first of all you can't get the source package from jaunty using "apt-get source ..." [13:27] mok0, check [13:27] jack_: because that will get you the intrepid version [13:27] mok0, yes [13:27] jack_: so you have to get the source package from packages.ubuntu.com [13:28] mok0, check [13:28] then you go into packagexx/debian and edit changelog [13:28] jack_: make a new entry, e.g. "backported from jaunty" [13:29] can somebody here help me with a basic packaging question? [13:29] is there a way to controll how changed files are handled? [13:29] mok0, ok [13:29] jack_: and you make sure the version number in the top changelog entry is appropriate according to the link I gave you above [13:30] i.e. overwritten or not, or prompting the user which version to keep [13:30] mok0, ok [13:30] jack_: then you build a new source package [13:30] jack_: debuild -S -sa [13:30] mok0, ok [13:30] jack_: that will give you a new .dsc file [13:30] jack_: and you pass that to pbuilder [13:30] mok0, yes [13:31] mok0, ok [13:31] jack_: ... that's it [13:31] jack_: (if you're lucky :-)) [13:31] mok0, thanks! :) should I check the build file? [13:31] jack_: sure [13:31] mok0, how [13:32] jack_: never mind, it doesn't matter if the build succeeds [13:32] mok0, ok [13:32] jack_: then you install the package and check that the program works [13:32] mok0, ok [13:33] jack_: if you want to submit it to Ubuntu, you make a debdiff between the "old" and "backported" versions, and attach that to a bug request in LP [13:34] mok0, how do I make a debdiff? [13:34] jack_: we'll save that for next lesson. Now go and make your backport. [13:34] mok0, ok thanks :) [13:36] hannesw: debconf [13:37] mok0: thanks [13:38] so i just use dh_installdebconf in debian rules instead of dh_install? [13:40] hannesw: no you need to use both. But TBH, I've never used debconf so I don't know the details. You [13:40] will have to ask Mr. Google [13:40] mok0: thanks, will do. [14:30] hello everybody, i am interested in start packaging software for ubuntu [14:32] sirderigo, a good start may be https://wiki.ubuntu.com/MOTU/GettingStarted [14:32] why? because this is a good way to help, and because i dont like to compile software when i need it, but i can do it, but i am pretty sure, what a lot of people cant do it, [14:57] I've fixed my package again http://revu.ubuntuwire.com/details.py?package=lensfun I'd like a new review... [14:57] Dear MOTU, The new 64-bit package for pulseaudio that hit repos last night is such an amazing improvement. I want to sincerely thank everyone who played a part in putting it together. Best regards, luckyone! [14:58] luckyone: which repos? for jaunty? [15:00] slytherin: intrepid [15:01] * slytherin checks [15:04] luckyone: pulseaudio is in main, so you should probably thank people on #ubuntu-devel. :-) === Czessi_ is now known as Czessi === quentusrex23 is now known as quentusrex [16:13] hi everybody. [16:14] im followed the youtube learning MOTU video, and I have a question regarding pbuilder. [16:14] pbuilder is reporting my distribution as jaunty instead of intrepid. [16:15] after i ran 'sudo pbuilder create' for the first time, the prompt said 'distribution is jaunty' even though i'm running intrepid :/ [16:15] skorasaurus: what distribution in the chroot though? [16:16] Nafallo, how do i determine that, i didnt set anything ever to jaunty. [16:16] AFIAK, of course. [16:16] AFAIK* [16:17] but you know what distribution you told pbuilder to create, no? [16:17] not sure. [16:18] i download the necessary pkgs in apt-get, and my sources are set for intrepid. [16:18] and i created pbuilderrc [16:19] grep for jaunty in your pbuilderrc then [16:19] nothing 'jaunty' in pbuilderrc [16:19] pbuilderrc is COMPONENTS="main restricted universe multiverse" [16:34] hi, i was going to make my first package and i chose one from the 'needs-packaging' in lp [16:34] was = am [16:36] skorasaurus: go on [16:37] and there's already a .deb (generic debian) file and i don't know how to build a package (for ubuntu) using that. [16:37] i found the directions to build from src [16:37] skorasaurus: that's what you want to do [16:37] but not to use an existing deb (i presume its easier to use an existing deb) [16:38] even though the program creator has a generic deb on his website ?/ [16:38] skorasaurus: a .deb file normally contains the binary code for a program, so it needs to be right for the Ubuntu version you have [16:39] skorasaurus: another thing is if you can trust it if it's not from the official archive [16:40] mok0, i understand the reason for trust (to be hesitant to use the deb package), but the .deb package was on the developer's website [16:40] skorasaurus: you can try to install it [16:40] i'm not trying to be hard on you or disagree for the sake of it, im just trying to understand :) [16:41] skorasaurus: I know [16:42] should I just ignore the deb on the dev's website and get the source instead then ? [16:42] skorasaurus: yeah why not? [16:42] skorasaurus: you can learn how to build the binary packages [16:43] k [16:43] skorasaurus: perhaps you know that already [16:49] Hey [16:52] hi. [16:54] there isn't a source package in the repository for my package. [16:55] wait, nevermind, think i figured out. [16:55] * skorasaurus is an obvious newbie. [16:56] heh [16:57] so, i'm reading https://wiki.ubuntu.com/PackagingGuide/Complete#Packaging%20With%20CDBS and [16:57] can anybody take a look at http://revu.ubuntuwire.com/details.py?package=lensfun I'd like to get endorsed, if there are no remaining issues [16:59] pmjdebruijn: I'll bit [16:59] bite [17:00] pmjdebruijn: are you upstream? [17:06] mok0: I'm not a Debian developer [17:06] mok0: I made this package from scratch [17:06] mok0: first for private use... then I fixed it for inclusion into Ubuntu [17:07] pmjdebruijn: never mind I was asking if you are the author of the lensfun program [17:07] mok0: oh no sorry [17:07] library sorry [17:07] mok0: it's a library that can be used with the ufraw raw conversion program [17:09] mok0: I did have some previous packaging experience... though I never really used lintian... so I'm getting used to that... the lensfun package should be lint free now (finally) [17:09] pmjdebruijn: well that's a step forward :-) [17:10] mok0: I had a lot of "little" things to fix [17:10] no big issues [17:10] pmjdebruijn: there is one big issue [17:10] which is? [17:10] pmjdebruijn: missing copyright from upstream [17:11] http://revu.ubuntuwire.com/revu1-incoming/lensfun-0812151457/lensfun-0.2.3/debian/copyright [17:11] what's wrong with that? [17:11] pmjdebruijn: we can't distribute without it [17:11] mok0: I don't see what I'm missing [17:11] pmjdebruijn: you will need to contact him [17:12] mok0: for what? [17:12] mok0: it says Copyright (c) 2007-2008 Andrew Zabolotny [17:12] pmjdebruijn: to put GPL clauses in source files + place a COPYING file in the tarball [17:12] oh [17:12] pmjdebruijn: yeah :-( [17:13] now I understand [17:13] mok0: ok, that not a big problem, I can ask Andrew about that... he seems responsive... [17:13] mok0: but there are no other issues? [17:13] pmjdebruijn: A lot of packaging work is communicating with upstream distributors. [17:13] mok0: no problem... [17:13] pmjdebruijn: oh, I'm not that fast [17:17] pmjdebruijn: I need to check to see if CCPL is compatible with DFSG [17:17] mok0: Ubuntu has other CCPL licensed content I thing [17:17] think* [17:18] pmjdebruijn: yes [17:18] so there should be an issue there...? right? [17:18] pmjdebruijn: no worries, CC-SA 3.0 is compatible it seems [17:18] shouldn't [17:18] ok [17:19] There are also bits of code that are MIT/X11 (BSD-like) [17:19] pmjdebruijn: in tools/makedep/ [17:21] pmjdebruijn: but the code in libs/lensfun only has copyright for Zabolotny, no license [17:21] mok0: it's GPL3 if I'm not mistaken, but I have already contacted Andrew about this [17:21] pmjdebruijn: I'll put all my notes on REVU for your reference later [17:22] pmjdebruijn: It's good if you're in contact with him [17:23] pmjdebruijn: otherwise packaging looks good [17:23] mok0: I just hope he has some times this month... I hoped to get it in before new year... [17:23] pmjdebruijn: that's optimistic [17:23] but if not... too bad... [17:24] mok0: yeah... [17:24] pmjdebruijn: but there's a good possibility to get it into jaunty [17:24] everybody's busy in december :) [17:24] mok0: yeah, I never expected it to get it into intrepid [17:24] mok0: I also need to modify the ufraw package to actually use lensfun [17:24] pmjdebruijn: Almost nothing new got into intrepid [17:24] mok0: but I'll cross that bridge when I get to it [17:24] pmjdebruijn: great [17:25] mok0: can I submit "revised" packaged to revu as well? [17:25] pmjdebruijn: sure [17:25] for packages which already exist downstream Debian [17:25] pmjdebruijn: oh [17:25] pmjdebruijn: hijacking a package is likely to get you unpopular [17:25]