serialorder | 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:00 |
---|---|---|
ScottK | Part of the merge | 00:01 |
serialorder | ok thanks ScottK | 00:02 |
=== binario_ is now known as BiNaRi0 | ||
=== coppro_ is now known as coppro | ||
=== emma_ is now known as emma | ||
serialorder | if a package i merged failed to build on two different architectures should I open two bugs in lp or just one? | 03:04 |
serialorder | 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:04 |
nhandler | emgent: ping | 03:21 |
emgent | pong | 03:21 |
nhandler | emgent: Why don't you have anyone seeding the nubuntu torrent? | 03:21 |
emgent | it`s fresh upload | 03:22 |
nhandler | emgent: Ok, so someone will be seeding it soon? | 03:22 |
coppro | anyone for REVU? | 03:22 |
emgent | use mirror :P | 03:22 |
nhandler | emgent: I will. I normally prefer to use a torrent, but I guess a mirror will have to do | 03:22 |
emgent | nhandler: yeah, but i suggest to use download button | 03:23 |
freakabcd | hi guys | 03:41 |
freakabcd | can someone please do a new build of evolution? | 03:41 |
freakabcd | for hardy | 03:41 |
Nafallo | ? | 03:41 |
freakabcd | because the one supplied doesn;t work with exchange :( | 03:41 |
freakabcd | i mean newer than the version supplied (2.24.2 ?) | 03:42 |
freakabcd | or soemone help me build the src package from jaunty in my hardy installation | 03:43 |
ScottK | !backports | freakabcd | 03:46 |
ubottu | 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:46 |
serialorder | a package I merged FTBFS on the ia64 and sparc architectures | 03:48 |
serialorder | i found some fixes from upstream and patched the package | 03:48 |
serialorder | i dont run those architectures though so i can testbuild | 03:49 |
serialorder | cant* | 03:49 |
serialorder | how should i proceed? | 03:49 |
Hobbsee | serialorder: good questoin. | 03:50 |
serialorder | Hobbsee: bad answer | 03:51 |
serialorder | hehe no im just joking | 03:51 |
Hobbsee | serialorder: i'm still thinking. | 03:51 |
Hobbsee | 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:51 |
Hobbsee | 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 |
StevenK | Or put your source somewhere and say "Please test build this" | 03:52 |
Hobbsee | (they don't have the HW, they don't have the technical knowledge to check if it's correct) | 03:52 |
Hobbsee | that too | 03:52 |
serialorder | ok i guess I will try and find a home for it somewhere and send a request to the list to test build | 03:55 |
ScottK | NCommander: You got IA64? | 03:59 |
NCommander | I have access to one | 03:59 |
serialorder | https://bugs.launchpad.net/ubuntu/+source/protobuf/+bug/308829 | 03:59 |
ubottu | Launchpad bug 308829 in protobuf "protobuf 2.0.2-1 (universe) FTBFS on ia64 and sparc" [Undecided,Confirmed] | 03:59 |
ScottK | NCommander: Need to test an FTBFS fix ... | 03:59 |
serialorder | i actually have to leave now, library is closing on me | 04:00 |
serialorder | thanks for the help | 04:01 |
NCommander | cya serialorder | 04:01 |
* NCommander looks for his IA64 keys | 04:01 | |
serialorder | ill probably be back tomorrow =) | 04:01 |
NCommander | Anyone from SRU awake? | 04:16 |
=== root is now known as Guest57157 | ||
=== Guest57157 is now known as dcypherd | ||
dcypherd | hey ppl I had a couple of packaging questions | 05:08 |
dcypherd | are programs like aircrack-ng and metasploit not in the repos because someone needs to make them or are there other reasons | 05:10 |
dcypherd | ? | 05:10 |
crimsun | dcypherd: aircrack-ng has been in universe | 05:15 |
crimsun | (since feisty from the looks of rmadison) | 05:15 |
crimsun | dcypherd: you may wish to inspect nubuntu for packages such as metasploit | 05:16 |
dcypherd | thx | 05:16 |
dcypherd | forgot about nubuntu | 05:17 |
crimsun | dcypherd: see also debian 323420 for metasploit's itp | 05:20 |
ubottu | Debian bug 323420 in wnpp "advanced platform for developing, testing, and using exploit code" [Wishlist,Open] http://bugs.debian.org/323420 | 05:20 |
nellery | iulian: Hi, are you planning on doing the httrack merge? | 05:55 |
dholbach | good morning | 07:09 |
fabrice_sp | morning Daniel! | 07:11 |
iulian | nellery: Please do it. I took a peek at it yesterday and obviously forgot about it. | 07:11 |
iulian | Good morning Daniel. | 07:11 |
nellery | iulian: thanks a lot | 07:11 |
iulian | Thank you. | 07:12 |
dholbach | hi fabrice_sp | 07:13 |
fabrice_sp | :-) How are you doing this morning? | 07:14 |
dholbach | very good - how are you? | 07:15 |
fabrice_sp | Very good also, thanks :-) | 07:15 |
fabrice_sp | Just have to leave to go to work :-/ | 07:16 |
fabrice_sp | bye | 07:16 |
dholbach | fabrice_sp: have a great day! | 07:18 |
geser | good morning | 07:26 |
iulian | Heya geser. | 07:26 |
dholbach | stgraber: CONGRATULATIONS! | 07:27 |
didrocks | morning o/ | 07:38 |
=== dholbach_ is now known as dholbach | ||
=== jmarsden is now known as jmarsden-the-mag | ||
=== jmarsden-the-mag is now known as jmarsden-magicia | ||
mgdm | "libdmtx 0.6.0-1 is in Ubuntu already" - it wasn't when I filed the bug with the patch :) | 09:17 |
=== jmarsden-magicia is now known as jmarsden | ||
dholbach | mgdm: for sync (overwrite current ubuntu package with newest from Debian) requests, just use https://wiki.ubuntu.com/SyncRequestProcess the next time :) | 09:20 |
dholbach | (so you don't need to attach a patch to it) | 09:20 |
mgdm | dholbach: Nice one, thanks. I didn't know about that, and did the patch for practice anyway | 09:20 |
dholbach | anytime :) | 09:20 |
mgdm | I have another couple of things that aren't in Debian to do though | 09:21 |
dholbach | https://wiki.ubuntu.com/SponsorshipProcess | 09:22 |
mgdm | I have read that one, my current issue is a bizarre build system in one of them | 09:24 |
dholbach | ah ok | 09:24 |
mgdm | with luck I'll get them done tomorrow | 09:25 |
mgdm | well, sent to REVU anyway | 09:25 |
* norsetto wonders why its so quiet in here ... | 10:30 | |
=== boshhead_ is now known as boshhead | ||
* dholbach hugs norsetto | 10:42 | |
dholbach | hey norsetto | 10:42 |
* norsetto hugs master mixer dholbach back :-) | 10:43 | |
dholbach | :) | 10:43 |
dholbach | how are you doing? | 10:43 |
norsetto | dholbach: fine, at least I will be at home for a couple of days | 10:44 |
=== spacey_ is now known as spacey | ||
norsetto | dholbach: and you? Still freezing in Berlin ? | 10:45 |
dholbach | yeah, it's 4°C here | 10:45 |
dholbach | but I'm fine :) | 10:45 |
DktrKranz | hi dholbach, norsetto! long time no see! :) | 11:01 |
dholbach | hiya DktrKranz | 11:01 |
DktrKranz | norsetto: how about Tiber and rivers? | 11:01 |
mok0 | norsetto! | 11:04 |
norsetto | DktrKranz: Glou, glou, glou :-) | 11:07 |
norsetto | mok0: hey!!! | 11:07 |
sebner | norsetto: \o/ | 11:08 |
norsetto | mok0: I must confess something to you, something really really shaming ... | 11:09 |
DktrKranz | 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 | |
norsetto | sebner: hi seb! | 11:09 |
mok0 | norsetto? | 11:09 |
sebner | norsetto: +ner ^ ^ | 11:09 |
sebner | norsetto: long time no see. how are you? =) | 11:10 |
sebner | DktrKranz: drink and drive ^^ | 11:10 |
norsetto | mok0: you know, you convinced me to use emacs, and I actually LIKE it | 11:10 |
norsetto | sebner: pretty fine, and you? | 11:11 |
mok0 | norsetto: :-) | 11:11 |
mok0 | norsetto: It has some really nice debian modes too | 11:12 |
mok0 | norsetto: did you install those? | 11:12 |
norsetto | mok0: yes, I saw your bug on emacs-goodies-el :-) | 11:12 |
mok0 | norsetto: hehe | 11:13 |
mok0 | It's a one-byte patch :-) | 11:13 |
norsetto | mok0: those are the hardest ones ;-) | 11:13 |
sebner | norsetto: some days ago we had 3meters of snow ^^ my poor back. :( geeks are poor ^^ | 11:14 |
mok0 | norsetto: yeah, several kilobytes of overhead | 11:14 |
norsetto | sebner: must be cool going to school by skying | 11:14 |
mok0 | sebner: why bother? snow melts you know | 11:14 |
norsetto | sebner: here they are going to school by boat now ... | 11:15 |
sebner | norsetto: heh, well, I finished school in summer already | 11:15 |
sebner | mok0: sure but when there are already 2 meters of snow and you have to put another meter somewhere ... | 11:15 |
jack_ | 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:16 |
mok0 | sebner: I see your point... perhaps: cat snow > /dev/null | 11:17 |
norsetto | sebner: oh well, going to work then, or whatever else is it you up in the mountains once school is over ... | 11:17 |
sebner | mok0: I'll tell the snow next time | 11:18 |
mok0 | sebner: yeah, just stand there with the pipe while it's snowing | 11:18 |
sebner | norsetto: heh, currently (since 2 months) I'm on vacation ^ ^ Next month I'll start my basic military service | 11:19 |
sebner | mok0: xD | 11:19 |
* norsetto stands on attention and salutes | 11:19 | |
mok0 | sebner: uh oh | 11:19 |
sebner | norsetto: no mercy? =) | 11:20 |
jack_ | ?? | 11:22 |
norsetto | DktrKranz: see, you should do some time in the army too, it will straighten your dorsal spine ... | 11:22 |
sebner | DktrKranz: hahaha! | 11:26 |
norsetto | jack_: what do you mean by check, checking the build log or the content of the resulting binaries? | 11:26 |
jack_ | norsetto, Iḿ not sure... | 11:27 |
jack_ | I saw it in the youtube tutorial... | 11:28 |
norsetto | 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:29 |
norsetto | 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 |
jack_ | you give the --log option when building with pbuilder? | 11:30 |
norsetto | 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 |
jack_ | ok | 11:31 |
jack_ | 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 |
jack_ | find . -name '*.C' | xargs heac | less | 11:32 |
norsetto | jack_: man is your friend (ok, I'm old fashioned but even a youngster like mok0 should agree...) | 11:32 |
mok0 | licensecheck | 11:34 |
norsetto | jack_: err, you know what a pipe is? | 11:34 |
jack_ | norsetto, no | 11:34 |
mok0 | puff puff | 11:35 |
jack_ | a puff puff, yes I puff know | 11:36 |
mok0 | jack_: if you're talking about dholbach's tutorial on YouTube, he was using licensecheck | 11:36 |
jack_ | mmh ok... | 11:37 |
jack_ | then he did it nicely hidden.... | 11:37 |
norsetto | jack_: maybe you should read something like this: http://www.ee.surrey.ac.uk/Teaching/Unix/ | 11:37 |
mok0 | jack_: find . -name '*.C' | xargs head | less will list the first 10 lines of every file that ends with ".C" | 11:39 |
jack_ | ok | 11:39 |
mok0 | jack_: and display it in the pager | 11:39 |
jack_ | ok, I'll check the teaching link... | 11:41 |
jack_ | one question remains... | 11:41 |
norsetto | jack_: pls. do, it will help you a lot I think | 11:41 |
jack_ | 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 |
jack_ | s=on&field.has_patch=&field.has_no_package= | 11:41 |
jack_ | wow.... | 11:42 |
jack_ | I mean for example the package nted on launchpad... | 11:42 |
jack_ | https://bugs.launchpad.net/ubuntu/+source/nted/+bug/253378 | 11:42 |
ubottu | Launchpad bug 253378 in nted "Please update to latest version (1.3.0)" [Undecided,New] | 11:42 |
norsetto | jack_: just give a bug number, ubotu will fetch the link for you | 11:43 |
jack_ | Let assume I want to have a newer version and maintain it.... how can I do it? | 11:43 |
jack_ | maintain = keep it up to date in Ubuntu | 11:43 |
norsetto | 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:45 |
jack_ | and is an update only for the new version of Ubuntu or can I ask for an update in Intrepid? | 11:46 |
norsetto | jack_: only for the current development version (right now jaunty). But once there a backport can be looked up | 11:47 |
jack_ | 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:48 |
norsetto | jack_: once is there it can be done | 11:49 |
jack_ | norsetto, ok thanks. Where can I find info how to make a backport package? | 11:50 |
norsetto | jack_: hmm, I don' t have links here readily available, just a sec | 11:50 |
jack_ | k | 11:51 |
norsetto | 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 |
jack_ | norsetto, ok thanks! | 11:52 |
norsetto | jack_: np | 11:52 |
jack_ | 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:54 |
jack_ | or contact people about it | 11:55 |
norsetto | jack_: I guess you talk about cross-compiling | 11:56 |
jack_ | 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? | 11:57 |
norsetto | jack_: I don' t think that you need a lot of stuff to build a kernel actually | 12:05 |
jack_ | norsetto, ok I'll check it out.... | 12:05 |
norsetto | jack_: at least from memory (last I build one was more than a year ago) | 12:06 |
jack_ | k | 12:08 |
norsetto | tseliot: Hola! How is the nvidia wizard doing? | 12:32 |
tseliot | norsetto: I'm trying to recover from jet-lag but otherwise I'm very happy about how the UDS went | 12:33 |
norsetto | tseliot: was it better than the one in Prague? | 12:34 |
tseliot | norsetto: definitely | 12:35 |
norsetto | tseliot: glad to hear that | 12:35 |
jack_ | can you use prevu to build official backport packages? | 12:35 |
jack_ | http://ubuntuforums.org/showthread.php?t=268687 | 12:38 |
jack_ | ok I see the answer is yes... | 12:40 |
jack_ | how do you use pbuilder to make a backport package? | 12:40 |
stgraber | dholbach: thanks | 12:47 |
* nxvl HUGS norsetto | 12:50 | |
norsetto | nxvl: hola bandido! | 12:52 |
mok0 | jack_: you need to specify the -proposed repo in the --othermirror switch | 13:13 |
mok0 | jack_: if I understood your question | 13:13 |
jack_ | mok0, and how can I do that? | 13:14 |
mok0 | jack_: if the package you are building is for backports, you need to put that in the changelog entry: e.g. interpid-backports | 13:14 |
jack_ | mok0, ok and do I use the jaunty version of the package? How do I get that package? | 13:15 |
mok0 | jack_: eerrr what package? The one you're building? | 13:16 |
jack_ | mok0, there is already a package of the version in Jaunty which will be backported... that package | 13:16 |
jack_ | or do you use just a tar.gz file from the makers website? | 13:17 |
mok0 | jack_: and you want to backport it to intrepid? | 13:17 |
jack_ | mok0, yes | 13:17 |
mok0 | jack_: https://help.ubuntu.com/community/UbuntuBackports#Source%20Change%20Backports | 13:17 |
mok0 | jack_: make a new changelog entry describing the backport | 13:18 |
mok0 | jack_: and name the version like it is described in that document | 13:18 |
mok0 | jack_: then you need to see if it builds AND works on the target distro | 13:18 |
jack_ | mok0, ok but Iḿ not a Motu, and I just use the tar.gz? | 13:19 |
jack_ | so nothing with the Jaunty package? | 13:19 |
mok0 | jack_: you have the package from jaunty, I presume | 13:19 |
jack_ | mok0, how do I get that? | 13:19 |
mok0 | jack_: you add this changelog entry to the jaunty package | 13:19 |
mok0 | jack_: go to packages.ubuntu.com | 13:20 |
mok0 | jack_: get the source package (3 files) | 13:20 |
jack_ | mok0, ah, not the deb | 13:20 |
mok0 | jack_: no the source package | 13:20 |
mok0 | jack_: it includes upstreams tarball | 13:20 |
jack_ | mok0, .dsc, orig.tar.gz and diff.gz? | 13:21 |
mok0 | jack_: yes | 13:22 |
mok0 | jack_: in fact all you need to fetch is the .dsc | 13:22 |
mok0 | jack_: then use dget -xu <file.dsc> | 13:22 |
jack_ | mok0, ah ok, I see... so it's almost the same as updating a package? | 13:22 |
mok0 | jack_: yes | 13:22 |
jack_ | mok0, could you describe the steps for me? | 13:23 |
mok0 | jack_: except the newer version may have dependencies that are not available in the older distro | 13:23 |
mok0 | jack_: and that's what you must check to make sure it will compile | 13:23 |
jack_ | mok0, and what to do in that case? | 13:23 |
mok0 | jack_: then you can't backport | 13:23 |
jack_ | mok0, ok | 13:24 |
mok0 | jack_: time is unidirectional, unfortunately :-) | 13:24 |
jack_ | mok0, here are some notes for updating a packages: http://pastebin.com/m1ec1eceb | 13:24 |
mok0 | jack_: but often it will work | 13:24 |
jack_ | mok0, :) | 13:24 |
jack_ | mok0, what is different between the notes and backporting? | 13:25 |
* mok0 looks | 13:25 | |
mok0 | jack_: there are several differences | 13:25 |
mok0 | jack_: but it depends what version of Ubuntu your are working on | 13:26 |
mok0 | jack_: in a way, backporting is simpler | 13:26 |
jack_ | mok0, ok, now on Intrepid... | 13:26 |
mok0 | jack_: ok, so first of all you can't get the source package from jaunty using "apt-get source ..." | 13:27 |
jack_ | mok0, check | 13:27 |
mok0 | jack_: because that will get you the intrepid version | 13:27 |
jack_ | mok0, yes | 13:27 |
mok0 | jack_: so you have to get the source package from packages.ubuntu.com | 13:27 |
jack_ | mok0, check | 13:28 |
mok0 | then you go into packagexx/debian and edit changelog | 13:28 |
mok0 | jack_: make a new entry, e.g. "backported from jaunty" | 13:28 |
hannesw | can somebody here help me with a basic packaging question? | 13:29 |
hannesw | is there a way to controll how changed files are handled? | 13:29 |
jack_ | mok0, ok | 13:29 |
mok0 | jack_: and you make sure the version number in the top changelog entry is appropriate according to the link I gave you above | 13:29 |
hannesw | i.e. overwritten or not, or prompting the user which version to keep | 13:30 |
jack_ | mok0, ok | 13:30 |
mok0 | jack_: then you build a new source package | 13:30 |
mok0 | jack_: debuild -S -sa | 13:30 |
jack_ | mok0, ok | 13:30 |
mok0 | jack_: that will give you a new .dsc file | 13:30 |
mok0 | jack_: and you pass that to pbuilder | 13:30 |
jack_ | mok0, yes | 13:30 |
jack_ | mok0, ok | 13:31 |
mok0 | jack_: ... that's it | 13:31 |
mok0 | jack_: (if you're lucky :-)) | 13:31 |
jack_ | mok0, thanks! :) should I check the build file? | 13:31 |
mok0 | jack_: sure | 13:31 |
jack_ | mok0, how | 13:31 |
mok0 | jack_: never mind, it doesn't matter if the build succeeds | 13:32 |
jack_ | mok0, ok | 13:32 |
mok0 | jack_: then you install the package and check that the program works | 13:32 |
jack_ | mok0, ok | 13:32 |
mok0 | 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:33 |
jack_ | mok0, how do I make a debdiff? | 13:34 |
mok0 | jack_: we'll save that for next lesson. Now go and make your backport. | 13:34 |
jack_ | mok0, ok thanks :) | 13:34 |
mok0 | hannesw: debconf | 13:36 |
hannesw | mok0: thanks | 13:37 |
hannesw | so i just use dh_installdebconf in debian rules instead of dh_install? | 13:38 |
mok0 | hannesw: no you need to use both. But TBH, I've never used debconf so I don't know the details. You | 13:40 |
mok0 | will have to ask Mr. Google | 13:40 |
hannesw | mok0: thanks, will do. | 13:40 |
sirderigo | hello everybody, i am interested in start packaging software for ubuntu | 14:30 |
MagicFab | sirderigo, a good start may be https://wiki.ubuntu.com/MOTU/GettingStarted | 14:32 |
sirderigo | 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:32 |
pmjdebruijn | I've fixed my package again http://revu.ubuntuwire.com/details.py?package=lensfun I'd like a new review... | 14:57 |
luckyone | 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:57 |
slytherin | luckyone: which repos? for jaunty? | 14:58 |
handschuh | slytherin: intrepid | 15:00 |
* slytherin checks | 15:01 | |
slytherin | luckyone: pulseaudio is in main, so you should probably thank people on #ubuntu-devel. :-) | 15:04 |
=== Czessi_ is now known as Czessi | ||
=== quentusrex23 is now known as quentusrex | ||
skorasaurus | hi everybody. | 16:13 |
skorasaurus | im followed the youtube learning MOTU video, and I have a question regarding pbuilder. | 16:14 |
skorasaurus | pbuilder is reporting my distribution as jaunty instead of intrepid. | 16:14 |
skorasaurus | after i ran 'sudo pbuilder create' for the first time, the prompt said 'distribution is jaunty' even though i'm running intrepid :/ | 16:15 |
Nafallo | skorasaurus: what distribution in the chroot though? | 16:15 |
skorasaurus | Nafallo, how do i determine that, i didnt set anything ever to jaunty. | 16:16 |
skorasaurus | AFIAK, of course. | 16:16 |
skorasaurus | AFAIK* | 16:16 |
Nafallo | but you know what distribution you told pbuilder to create, no? | 16:17 |
skorasaurus | not sure. | 16:17 |
skorasaurus | i download the necessary pkgs in apt-get, and my sources are set for intrepid. | 16:18 |
skorasaurus | and i created pbuilderrc | 16:18 |
Nafallo | grep for jaunty in your pbuilderrc then | 16:19 |
skorasaurus | nothing 'jaunty' in pbuilderrc | 16:19 |
skorasaurus | pbuilderrc is COMPONENTS="main restricted universe multiverse" | 16:19 |
skorasaurus | hi, i was going to make my first package and i chose one from the 'needs-packaging' in lp | 16:34 |
skorasaurus | was = am | 16:34 |
mok0 | skorasaurus: go on | 16:36 |
skorasaurus | 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 |
skorasaurus | i found the directions to build from src | 16:37 |
mok0 | skorasaurus: that's what you want to do | 16:37 |
skorasaurus | but not to use an existing deb (i presume its easier to use an existing deb) | 16:37 |
skorasaurus | even though the program creator has a generic deb on his website ?/ | 16:38 |
mok0 | 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:38 |
mok0 | skorasaurus: another thing is if you can trust it if it's not from the official archive | 16:39 |
skorasaurus | 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 |
mok0 | skorasaurus: you can try to install it | 16:40 |
skorasaurus | i'm not trying to be hard on you or disagree for the sake of it, im just trying to understand :) | 16:40 |
mok0 | skorasaurus: I know | 16:41 |
skorasaurus | should I just ignore the deb on the dev's website and get the source instead then ? | 16:42 |
mok0 | skorasaurus: yeah why not? | 16:42 |
mok0 | skorasaurus: you can learn how to build the binary packages | 16:42 |
skorasaurus | k | 16:43 |
mok0 | skorasaurus: perhaps you know that already | 16:43 |
iulian | Hey | 16:49 |
skorasaurus | hi. | 16:52 |
skorasaurus | there isn't a source package in the repository for my package. | 16:54 |
skorasaurus | wait, nevermind, think i figured out. | 16:55 |
* skorasaurus is an obvious newbie. | 16:55 | |
mok0 | heh | 16:56 |
skorasaurus | so, i'm reading https://wiki.ubuntu.com/PackagingGuide/Complete#Packaging%20With%20CDBS and | 16:57 |
pmjdebruijn | 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:57 |
mok0 | pmjdebruijn: I'll bit | 16:59 |
mok0 | bite | 16:59 |
mok0 | pmjdebruijn: are you upstream? | 17:00 |
pmjdebruijn | mok0: I'm not a Debian developer | 17:06 |
pmjdebruijn | mok0: I made this package from scratch | 17:06 |
pmjdebruijn | mok0: first for private use... then I fixed it for inclusion into Ubuntu | 17:06 |
mok0 | pmjdebruijn: never mind I was asking if you are the author of the lensfun program | 17:07 |
pmjdebruijn | mok0: oh no sorry | 17:07 |
mok0 | library sorry | 17:07 |
pmjdebruijn | mok0: it's a library that can be used with the ufraw raw conversion program | 17:07 |
pmjdebruijn | 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 |
mok0 | pmjdebruijn: well that's a step forward :-) | 17:09 |
pmjdebruijn | mok0: I had a lot of "little" things to fix | 17:10 |
pmjdebruijn | no big issues | 17:10 |
mok0 | pmjdebruijn: there is one big issue | 17:10 |
pmjdebruijn | which is? | 17:10 |
mok0 | pmjdebruijn: missing copyright from upstream | 17:10 |
pmjdebruijn | http://revu.ubuntuwire.com/revu1-incoming/lensfun-0812151457/lensfun-0.2.3/debian/copyright | 17:11 |
pmjdebruijn | what's wrong with that? | 17:11 |
mok0 | pmjdebruijn: we can't distribute without it | 17:11 |
pmjdebruijn | mok0: I don't see what I'm missing | 17:11 |
mok0 | pmjdebruijn: you will need to contact him | 17:11 |
pmjdebruijn | mok0: for what? | 17:12 |
pmjdebruijn | mok0: it says Copyright (c) 2007-2008 Andrew Zabolotny | 17:12 |
mok0 | pmjdebruijn: to put GPL clauses in source files + place a COPYING file in the tarball | 17:12 |
pmjdebruijn | oh | 17:12 |
mok0 | pmjdebruijn: yeah :-( | 17:12 |
pmjdebruijn | now I understand | 17:13 |
pmjdebruijn | mok0: ok, that not a big problem, I can ask Andrew about that... he seems responsive... | 17:13 |
pmjdebruijn | mok0: but there are no other issues? | 17:13 |
mok0 | pmjdebruijn: A lot of packaging work is communicating with upstream distributors. | 17:13 |
pmjdebruijn | mok0: no problem... | 17:13 |
mok0 | pmjdebruijn: oh, I'm not that fast | 17:13 |
mok0 | pmjdebruijn: I need to check to see if CCPL is compatible with DFSG | 17:17 |
pmjdebruijn | mok0: Ubuntu has other CCPL licensed content I thing | 17:17 |
pmjdebruijn | think* | 17:17 |
mok0 | pmjdebruijn: yes | 17:18 |
pmjdebruijn | so there should be an issue there...? right? | 17:18 |
mok0 | pmjdebruijn: no worries, CC-SA 3.0 is compatible it seems | 17:18 |
pmjdebruijn | shouldn't | 17:18 |
pmjdebruijn | ok | 17:18 |
mok0 | There are also bits of code that are MIT/X11 (BSD-like) | 17:19 |
mok0 | pmjdebruijn: in tools/makedep/ | 17:19 |
mok0 | pmjdebruijn: but the code in libs/lensfun only has copyright for Zabolotny, no license | 17:21 |
pmjdebruijn | mok0: it's GPL3 if I'm not mistaken, but I have already contacted Andrew about this | 17:21 |
mok0 | pmjdebruijn: I'll put all my notes on REVU for your reference later | 17:21 |
mok0 | pmjdebruijn: It's good if you're in contact with him | 17:22 |
mok0 | pmjdebruijn: otherwise packaging looks good | 17:23 |
pmjdebruijn | mok0: I just hope he has some times this month... I hoped to get it in before new year... | 17:23 |
mok0 | pmjdebruijn: that's optimistic | 17:23 |
pmjdebruijn | but if not... too bad... | 17:23 |
pmjdebruijn | mok0: yeah... | 17:24 |
mok0 | pmjdebruijn: but there's a good possibility to get it into jaunty | 17:24 |
pmjdebruijn | everybody's busy in december :) | 17:24 |
pmjdebruijn | mok0: yeah, I never expected it to get it into intrepid | 17:24 |
pmjdebruijn | mok0: I also need to modify the ufraw package to actually use lensfun | 17:24 |
mok0 | pmjdebruijn: Almost nothing new got into intrepid | 17:24 |
pmjdebruijn | mok0: but I'll cross that bridge when I get to it | 17:24 |
mok0 | pmjdebruijn: great | 17:24 |
pmjdebruijn | mok0: can I submit "revised" packaged to revu as well? | 17:25 |
mok0 | pmjdebruijn: sure | 17:25 |
pmjdebruijn | for packages which already exist downstream Debian | 17:25 |
mok0 | pmjdebruijn: oh | 17:25 |
mok0 | pmjdebruijn: hijacking a package is likely to get you unpopular | 17:25 |
pmjdebruijn | mok0: it's just a modification to ./configure, nothing more | 17:25 |
mok0 | pmjdebruijn: best thing is to get friendly with the Debian maintainer | 17:26 |
pmjdebruijn | ok | 17:26 |
mok0 | pmjdebruijn: most maintainers will be happy for contributions | 17:26 |
pmjdebruijn | mok0: but it's a pointless change since it would require Debian to include Lensfun as well | 17:26 |
mok0 | pmjdebruijn: The change can be done as a Ubuntu specific merge then | 17:27 |
mok0 | pmjdebruijn: if it's small no problem | 17:27 |
mok0 | pmjdebruijn: but then you should create a bug in Launchpad explaining the situation, and attach a diff to that bug | 17:28 |
DRebellion | Could anybody take a look at http://revu.ubuntuwire.com/details.py?package=cifer ? It's been advocated once previously, so it should be in pretty good shape. | 17:29 |
mok0 | pmjdebruijn: the soname version looks funny | 17:32 |
=== freeflyi1g is now known as freeflying | ||
pmjdebruijn | mok0: ok, clear | 17:34 |
pmjdebruijn | mok0: that's funny about it...? | 17:34 |
mok0 | pmjdebruijn: it's versioned like the source code | 17:34 |
pmjdebruijn | oh | 17:35 |
pmjdebruijn | mok0: you'd like single decimals? | 17:35 |
mok0 | pmjdebruijn: who designed the shared library? You or upstream? | 17:35 |
pmjdebruijn | mok0: increased whever the API changes? | 17:35 |
mok0 | pmjdebruijn: yes, start at 0 | 17:35 |
pmjdebruijn | mok0: upstream I guess | 17:35 |
mok0 | pmjdebruijn: we need to get this correct | 17:35 |
mok0 | pmjdebruijn: I'll dig out some urls I have somewhere explaining how to choose the .so version number | 17:36 |
pmjdebruijn | cool :) | 17:36 |
mok0 | pmjdebruijn: Most likely, upstream has no experience with distributions | 17:37 |
pmjdebruijn | mok0: quite likely | 17:37 |
pmjdebruijn | I'm quite moticated to make this work... | 17:37 |
pmjdebruijn | without UFRaw I'd already have bought a Mac... | 17:37 |
pmjdebruijn | UFRaw allows me to stick with Ubuntu :) | 17:37 |
pmjdebruijn | and LensFun makes UFRaw a lot better | 17:38 |
pmjdebruijn | I also hope we'll be able to pull in exiv2-0.18 which should be released before christmas | 17:38 |
mok0 | pmjdebruijn: cool | 17:38 |
pmjdebruijn | big improvements there as well | 17:39 |
mok0 | pmjdebruijn: great news for the photo enthusiasts! | 17:39 |
pmjdebruijn | writing EXIF to TIFF... Recognition of Canon lenses types | 17:39 |
pmjdebruijn | which previously only worked with Nikon | 17:39 |
pmjdebruijn | mok0: I'm currently maintaining an external repository with these goodies... | 17:39 |
pmjdebruijn | but for examples upgrading exiv2 on intrepid, breaks digikam... which I don't care about, but other people do | 17:40 |
mok0 | pmjdebruijn: Sounds interesting! | 17:40 |
pmjdebruijn | getting stuff into jaunty, seems like the best way to go | 17:40 |
mok0 | pmjdebruijn: yes | 17:40 |
mok0 | pmjdebruijn: Feature freeze is 19th of Feb IIRC | 17:40 |
pmjdebruijn | yeah | 17:40 |
pmjdebruijn | can Debian packages (exiv2-0.18) still get imported after christmas? | 17:41 |
pmjdebruijn | it'll be released around christmas upstream... so it'll take a few days for the Debian folks to repackage it, so it'll be after newyear until it's ready to get imported into jaunty | 17:41 |
ScottK | pmjdebruijn: Yes. | 17:42 |
pmjdebruijn | ScottK: great! | 17:43 |
pmjdebruijn | ScottK: yes request as sync as usual? | 17:44 |
pmjdebruijn | mok0: thanks for the review and the information, I'll talk to upstream and get things fixed... do you still have that soname URL for me, so I can pass that along to upstream? | 17:44 |
ScottK | pmjdebruijn: Yes. | 17:45 |
pmjdebruijn | ScottK: good thanks, I'll keep an eye on Debian's exiv2 package | 17:45 |
iulian | DRebellion: You might want to merge rm -f args into dh_clean. | 17:45 |
DRebellion | iulian, sorry, I'm not sure what you mean? | 17:46 |
azeem | pmjdebruijn: e.g. http://www.manpagez.com/info/libtool/libtool_37.php#SEC37 | 17:46 |
iulian | DRebellion: dh_clean build-stamp configure-stamp | 17:47 |
DRebellion | iulian, ah right. I just used the default dh_make way. | 17:47 |
pmjdebruijn | azeem: thanks! | 17:47 |
DRebellion | iulian, I will do that, thanks. | 17:48 |
iulian | DRebellion: The program looks intreresting. I see that it's written in C which is nice. I might try it out. | 17:49 |
DRebellion | iulian, great : ) | 17:50 |
DRebellion | iulian, we went C as an exercise in coding mainly, but the performance side helped with some of the bruteforcing | 17:50 |
mok0 | pmjdebruijn: ah, there are license files in the tarball, they are in docs | 17:50 |
iulian | DRebellion: Are you upstream? | 17:50 |
DRebellion | iulian, yes | 17:50 |
iulian | Is it maintained in a vcs? | 17:52 |
DRebellion | iulian, yes, we use google code: code.google.com/p/cifer | 17:53 |
iulian | Ah right, svn. | 17:55 |
pmjdebruijn | mok0: yeah | 17:59 |
mok0 | pmjdebruijn: one less thing to worry about. | 17:59 |
ScottK | jmarsden: Fixed setools is now available for testing in intrepid-proposed. Please give it a try and comment in bug 308350. | 18:10 |
ubottu | Launchpad bug 308350 in setools "FTBFS on amd64 and lpia due to dpkg-buildpackage failure." [Medium,Fix committed] https://launchpad.net/bugs/308350 | 18:10 |
mok0 | pmjdebruijn: review is up | 18:16 |
pmjdebruijn | mok0: thankyou! | 18:17 |
mok0 | pmjdebruijn: you're welcome | 18:17 |
pmjdebruijn | I have another question for something I'm making myself... (I=upstream) | 18:18 |
pmjdebruijn | it's an ICC color profile... | 18:18 |
pmjdebruijn | how can I best make the upstream tarball? the .icc file, and README and a LICENSE file (cc-by-sa-3) | 18:18 |
pmjdebruijn | all in a descriptive directory of course | 18:20 |
X-Sleepy-X | I have a really newbie question. I've downloaded alot of stuff to be able to make .deb files out of source code. However, I haven't found a good guide on how to acctually create the .deb files. Does anyone here sit on a good guide that they wish to share with me? | 18:21 |
iulian | X-Sleepy-X: https://wiki.ubuntu.com/PackagingGuide | 18:22 |
iulian | X-Sleepy-X: I believe /Complete is what you're looking for. | 18:23 |
X-Sleepy-X | iulian: Thank you very much! :) | 18:23 |
mok0 | pmjdebruijn: By definition, you can't make an upstream tarball, unless you distribute the software | 18:24 |
iulian | X-Sleepy-X: Don't mention it. If you have questions/ideas/remarks or anything else please say it here. | 18:24 |
pmjdebruijn | mok0: I was talking about my own "software" distribution | 18:25 |
mok0 | pmjdebruijn: ah | 18:25 |
X-Sleepy-X | ok | 18:25 |
mok0 | pmjdebruijn: but suited for packaging? | 18:25 |
pmjdebruijn | yeah | 18:25 |
mok0 | pmjdebruijn: what you said before sounds sensible,,, but what's the icc profile? | 18:26 |
pmjdebruijn | mok0: it's a color correction profile | 18:26 |
pmjdebruijn | mok0: digital camera's are color blind | 18:27 |
mok0 | binary? | 18:27 |
pmjdebruijn | mok0: well blind... they're crosseyed about color | 18:27 |
pmjdebruijn | mok0: yeah, binary | 18:27 |
pmjdebruijn | mok0: it's generated from an image | 18:27 |
pmjdebruijn | mok0: but the "sources" are not much use | 18:27 |
mok0 | pmjdebruijn: hmm | 18:27 |
mok0 | pmjdebruijn: that's a problem for the "lawyers" :-) | 18:28 |
mok0 | pmjdebruijn: there's a huge discussion going on these days in Debian, concerning distribution of binary blobs for firmware | 18:28 |
pmjdebruijn | mok0: the "sources" is a 10MB image, which is read into a textfile with values, which is converted into a 1.5K profile | 18:28 |
pmjdebruijn | mok0: it's not firmware... the icc profile is a documentation format... | 18:28 |
pmjdebruijn | mok0: it's just some math parameters | 18:29 |
mok0 | pmjdebruijn: you may want to include the ascii file, plus program to convert it... | 18:29 |
mok0 | pmjdebruijn: the philosophy is that anyone should be able to "compile" | 18:29 |
mok0 | pmjdebruijn: and modify the "sources" | 18:30 |
mok0 | pmjdebruijn: anyway, the subject is worthy of a discussion on one of the mailing lists | 18:30 |
mok0 | pmjdebruijn: but for example, we have to exclude a PDF file if there is no source for it | 18:31 |
pmjdebruijn | mok0: not including a PDF without source is silly | 18:34 |
mok0 | pmjdebruijn: It's policy | 18:35 |
pmjdebruijn | mok0: nobody distributes icc sources | 18:35 |
pmjdebruijn | mok0: it's not really good for anything | 18:35 |
mok0 | pmjdebruijn: I wont dispute that | 18:35 |
pmjdebruijn | mok0: anyway sounds like policy gone bonkers | 18:36 |
mok0 | pmjdebruijn: heh | 18:36 |
pmjdebruijn | about the PDFs... | 18:36 |
pmjdebruijn | although it could be desirable... | 18:36 |
mok0 | pmjdebruijn: you have the software that creates the profile? | 18:36 |
pmjdebruijn | mok0: yeah, argyllcms, it's not in Ubuntu/Debian yet, but there are debian packages | 18:37 |
mok0 | pmjdebruijn: ok, that makes it easier I guess | 18:37 |
pmjdebruijn | mok0: generating the profile from source is problematic actually, since algorithm in argyll can change, and you don't want the profile to change along with it | 18:37 |
mok0 | pmjdebruijn: I understand | 18:37 |
pmjdebruijn | as profile are used for consistency, and a change profile is basically useless | 18:38 |
pmjdebruijn | I could include the text files and the prebuilt profiles of course... | 18:38 |
mok0 | pmjdebruijn: otoh, what if a huge error is discovered in a PDF file for which there is no modifiable source. Then it can't be corrected | 18:38 |
mok0 | pmjdebruijn: policy operates with something called the preferred human-readable and human-modifiable formats | 18:40 |
skorasaurus | i compiled a package, according to https://wiki.ubuntu.com/PackagingGuide/Complete#Binary%20and%20Source%20Packages but i don't know which distro i made it for | 18:40 |
skorasaurus | (jaunty or intrepid), i completely forgot about that. | 18:40 |
mok0 | skorasaurus: it given in debian/changelog | 18:41 |
mok0 | skorasaurus: top line | 18:41 |
skorasaurus | mok0, it says unstable | 18:41 |
pmjdebruijn | mok0: well, you never manually "want" to modify a profile | 18:41 |
pmjdebruijn | mok0: at least not really | 18:41 |
pmjdebruijn | mok0: but I get your point, power to the people | 18:41 |
pmjdebruijn | mok0: I understand it for PDFs as well, although I wouldn't reject, but just put it in non-free/multiverse | 18:42 |
mok0 | pmjdebruijn: heh, yeah. Like I said there's a heated discussion going on in Debian, concerning binary firmware blobs | 18:42 |
pmjdebruijn | yeah | 18:42 |
pmjdebruijn | mok0: even then, non-free/multiverse is the wya | 18:43 |
mok0 | pmjdebruijn: it's threatening to delay the release of Lenny | 18:43 |
pmjdebruijn | manually downloading a binary blob just because of policy is a massive nuisance | 18:43 |
* pmjdebruijn has blob free hardware... | 18:43 | |
mok0 | pmjdebruijn: yeah, but it is important to make a distinction | 18:43 |
pmjdebruijn | yeah, of course... but not including them will turn away users... | 18:44 |
mok0 | pmjdebruijn: Ubuntu ships binary drivers as restricted | 18:44 |
mok0 | pmjdebruijn: yes | 18:44 |
pmjdebruijn | and a firmware blobs are not as bad as binary kernel modules that like ATi/nVidia shit | 18:44 |
mok0 | pmjdebruijn: I agree. | 18:44 |
pmjdebruijn | I wouldn't include it on the CD, but I would make it easyily downloadable through restricted | 18:45 |
mok0 | pmjdebruijn: but some of this stuff is just given in C statements in hex numbers which nobody knows what mean. That is not satisfactory either | 18:45 |
pmjdebruijn | mok0: I know... it's though | 18:46 |
mok0 | pmjdebruijn: when you have a distribution, users expect that bugs will be fixed, and the blobs make it hard | 18:46 |
mok0 | pmjdebruijn, I will follow your progress with interest :-) | 18:47 |
pmjdebruijn | mok0: I never said, we should do nVidia's work for them... | 18:47 |
mok0 | pmjdebruijn: just be prepared for problems ahead :-) | 18:47 |
pmjdebruijn | mok0: I have no issues with telling people they bought crappy hardware from a crappy vendor | 18:48 |
mok0 | pmjdebruijn: I can't imaging what trade secret nVidia have in those drivers. It's crazy | 18:48 |
pmjdebruijn | yeah | 18:48 |
pmjdebruijn | mok0: probably afriad of publicising code cruft... performance hacks/shortcuts | 18:48 |
* mok0 confesses to having nVidia hardware. *blush* | 18:48 | |
mok0 | pmjdebruijn: hah! | 18:48 |
* pmjdebruijn rounds up the angry mob... *burn the witch* *burn the heretic* | 18:49 | |
norsetto | mok0: well, at least you have fully compliant opengl 3.0 drivers | 18:49 |
* mok0 runs | 18:49 | |
pmjdebruijn | mok0: confessing the first step to be absolved of your sins... | 18:49 |
mok0 | norsetto: that's always something | 18:49 |
norsetto | mok0: hmmm, wait, what card you have? | 18:49 |
mok0 | norsetto: oh... it's an 8500 | 18:50 |
norsetto | mok0: ok, you do then | 18:50 |
mok0 | norsetto: I had lots of problems with under Hardy, but with Intrepid it works great | 18:50 |
mok0 | norsetto: with restricted drivers... | 18:50 |
fabrice_sp | Hi. Anybody to review dvdstyler? it's at http://revu.ubuntuwire.com/details.py?package=dvdstyler | 18:50 |
* mok0 hides | 18:50 | |
mok0 | fabrice_sp: ah, sorry I have to go for dinner. but norsetto's not doing anything sensible ;-) | 18:51 |
fabrice_sp | mok0, lol. I've tried ;-) | 18:51 |
norsetto | mok0: I must admit, the last time I looked at a package in revu was ... err ... couple of months ago!? | 18:52 |
mok0 | norsetto: we have a huge backlog | 18:52 |
fabrice_sp | and a lot of 'desperate' new packager asking for review :-) | 18:53 |
mok0 | norsetto: I'm about to catch up with you in # of reviews :-) | 18:53 |
norsetto | mok0: he, I'm still listed as number 5 reviewer, and haven't done any review for so long, so, its not surprising | 18:54 |
mok0 | norsetto: dktrkranz is biting your ass | 18:54 |
norsetto | mok0: dktrkranz is amazing, I don't know how he can find the time to breath ... | 18:55 |
mok0 | norsetto: haha | 18:55 |
mok0 | norsetto: what have you been up to? | 18:55 |
norsetto | mok0: pretty bad stuff unfortunately | 18:56 |
mok0 | norsetto: oh noes | 18:56 |
pmjdebruijn | I'm fiddling a bit with UFraw as well, but dpkg tells me this: | 18:57 |
* pmjdebruijn rounds up the angry mob... *burn the witch* *burn the heretic*dpkg-shlibdeps: warning: dependency on libpangoft2-1.0.so.0 could be | 18:57 | |
pmjdebruijn | avoided if "debian/gimp-ufraw/usr/lib/gimp/2.0/plug-ins/ufraw-gimp" were | 18:57 |
pmjdebruijn | not uselessly linked against it (they use none of its symbols).B[B[B | 18:57 |
pmjdebruijn | is this an issue in the makefiles? | 18:57 |
norsetto | mok0: oh well, wifey is calling for dinner, catch you up l8r | 18:58 |
mok0 | norsetto: bye-bye see you | 18:58 |
mok0 | pmjdebruijn: I think you can ignore that | 18:58 |
mok0 | pmjdebruijn: but you may be able to avoid the -lpangoft2 switch | 18:59 |
mok0 | pmjdebruijn: otoh then users need to remember it | 19:00 |
pmjdebruijn | huh? | 19:00 |
pmjdebruijn | I don't really understand why there warning are given... it's the first time I've seen this... | 19:00 |
mok0 | pmjdebruijn: shared libraries can contain information about symbols from other libraries | 19:00 |
pmjdebruijn | ok | 19:00 |
mok0 | pmjdebruijn: I generally ignore it | 19:01 |
* mok0 goes to dinner now. See you all | 19:02 | |
pmjdebruijn | mok0: bon apetit... | 19:02 |
hyperair | can anyone review my packages codelite and sigx? | 19:02 |
fabrice_sp | hyperair, about sigx, you didn't do any update since my comment, so I think it's difficult to have more review until then | 19:09 |
fabrice_sp | about the copyright header and the soname | 19:10 |
hyperair | ah | 19:35 |
hyperair | oh right | 19:35 |
skorasaurus | is the upstream author the actual developer of the program/library that i am packaging ? | 19:35 |
hyperair | fabrice_sp: how about codelite then? i've the lintian stuff | 19:35 |
hyperair | except for man pages | 19:35 |
hyperair | but considering it's a gui app with hardly any options, i think a man page is rather pointless | 19:35 |
fabrice_sp | hyperair, you need a manpage | 19:36 |
fabrice_sp | event if it's a gui app | 19:36 |
* fabrice_sp checking codelite | 19:38 | |
fabrice_sp | skorasaurus, in general, yes | 19:38 |
skorasaurus | k | 19:38 |
skorasaurus | fabrice_sp, thanks. | 19:38 |
hyperair | damn. | 19:42 |
hyperair | but banshee is a gui app and it doesn't have man pages, yet it's fine? | 19:42 |
fabrice_sp | I'm packaging dvdstyler, and I had to add a manpage to get rid of all lintian warnings | 19:43 |
fabrice_sp | a new package has to be lintian error free | 19:44 |
hyperair | damn. | 19:44 |
hyperair | okay. | 19:44 |
* fabrice_sp building codelite | 19:44 | |
fabrice_sp | hyperair, you also miss copyright headers in codelite :-/ | 19:46 |
fabrice_sp | hyperair, and also in debian/copyright, you should details the different copyrights that are used in codelite (I see LGPL, for example in some sources, but it's not mentioned in debian/copyright) | 19:49 |
fabrice_sp | I'll update the package comments in revu | 19:49 |
hyperair | fabrice_sp: thanks | 19:50 |
fabrice_sp | General questions: is it mandatory to have a COPYING file in the root directory of a package? | 19:52 |
ScottK | fabrice_sp: It's manadatory to have a copy of the full text of the license. Doesn't have to be named COPYING. | 20:08 |
fabrice_sp | ScottK, ok. I was having a look at codelite in revu, and found strange not to have this file in the root directory of the package | 20:09 |
fabrice_sp | thanks | 20:09 |
skorasaurus | hi, a package that im compiling, its rules file is different than the one in the packaging guide. | 20:20 |
skorasaurus | i'm a bit confused what to do now | 20:20 |
fabrice_sp | skorasaurus, each package can have (and actually has) a different rules file | 20:22 |
skorasaurus | fabrice_sp, there's one rules file in the debian folder | 20:22 |
fabrice_sp | what I mean is that a rules file from one package is different from the one of the another package | 20:23 |
fabrice_sp | the rule file depends on a lot of parameters | 20:23 |
LaserJock | what's a good versioning for a rebuild-only SRU? | 20:29 |
directhex | append "build1" | 20:30 |
LaserJock | so perhaps 1ubuntu1~build1? | 20:31 |
ScottK | LaserJock: I just did one as 1ubuntu1 when we already had a later version in Jaunty | 20:32 |
LaserJock | ScottK: current Intrepid/Jaunty version is 1ubuntu1, I'm going to upload a rebuild-only to both | 20:33 |
LaserJock | I'm just a little rusty here :( | 20:33 |
ScottK | LaserJock: In that case I'd just do 1ubuntu2 in Jaunty and 1ubuntu1.1 in Intrepid | 20:34 |
ScottK | The ...build1 is really only relevant if it's otherwise unchanged from debian and you want autosync to get it at the next chance. | 20:35 |
LaserJock | actually, I was wrong about the version being the same, but I get your point | 20:35 |
quadrispro | sebner: can you take a look to http://revu.ubuntuwire.com/details.py?package=uck ? | 20:38 |
quadrispro | sebner: (hi! :)) | 20:38 |
sebner | quadrispro: maybe tomorrow | 20:40 |
quadrispro | sebner: ok, thanks! | 20:40 |
LaserJock | can I get somebody to unsub u-u-s from bug #263173 please | 21:02 |
ubottu | Launchpad bug 263173 in sugar-hulahop "Sugar Browse fails on startup" [Undecided,Confirmed] https://launchpad.net/bugs/263173 | 21:02 |
sebner | LaserJock: on the way | 21:02 |
sebner | LaserJock: done | 21:03 |
LaserJock | sebner: thanks | 21:04 |
sebner | np =) | 21:04 |
jack_ | how do I get a debdiff? | 21:05 |
sebner | jack_: debdiff old.dsc new.dsc > xy.debdiff | 21:06 |
=== doko__ is now known as doko | ||
jack_ | sebner, ok thanks | 21:06 |
jack_ | debdiff: fatal error at line 269: | 21:11 |
jack_ | Need exactly two deb files or changes files to compare | 21:11 |
NCommander | hey DktrKranz | 21:12 |
sebner | DktrKranz: you were right. nvidia is b0rken on jaunty ^ ^ | 21:13 |
sebner | hi NCommander =) | 21:13 |
DktrKranz | we NCommander sebner | 21:13 |
NCommander | hey sebner | 21:13 |
jack_ | why do I get that error? | 21:14 |
sebner | jack_: post your command you use | 21:14 |
jack_ | sebner, debdiff nted_1.4.15-1.dsc nted_1.4.15-1ubuntu1~intrepid1.dsc > xy .debdiff | 21:15 |
sebner | jack_: I'd you nted.debdiff instead of xy .debdiff | 21:16 |
sebner | *use | 21:16 |
sebner | the error is the whitespace between xy and . | 21:16 |
jack_ | sebner, ok thanks | 21:17 |
serialorder | can someone please tell me a good way to save the output of pbuilder when a package FTBFS | 21:18 |
DktrKranz | sebner, IIRC, it hasn't been rebuilt against new xorg | 21:18 |
sebner | DktrKranz: well, it's generally b0rken. rebuild wouldn't fix it | 21:18 |
DktrKranz | serialorder, --logfile option could help you | 21:18 |
sebner | DktrKranz: we have to wait for a new upstream release. besides I reinstalled intrepid ^^ | 21:19 |
DktrKranz | sebner, ask tseliot about it, I'm sure he has an opinion | 21:19 |
sebner | DktrKranz: well, after reading his comments on the bugs his opinion is to wait until upstream (nvidia) fixes it ^^ | 21:19 |
DktrKranz | no compiz, my party! | 21:20 |
sebner | DktrKranz: never used that ;) | 21:20 |
* DktrKranz too | 21:21 | |
DktrKranz | probably because my hardware is too old to support anything useful | 21:21 |
* sebner parties with DktrKranz together \o/ | 21:21 | |
DktrKranz | sebner, does qmail actually build? | 21:25 |
sebner | DktrKranz: doesn't do since 2 years ;) | 21:26 |
DktrKranz | wasn't it fixed? or am I wrong? | 21:27 |
sebner | DktrKranz: O_o | 21:27 |
sebner | DktrKranz: not that I know | 21:27 |
DktrKranz | wasn't license clarified? | 21:28 |
DktrKranz | if so, I think it can actually be built | 21:28 |
DktrKranz | it keep FTBFS just because binaries were not distributable (IIRC) | 21:28 |
serialorder | DktrKranz: thanks that was exactly what i was looking for | 21:29 |
sebner | DktrKranz: really? since on Debian it always built ... | 21:30 |
DktrKranz | serialorder, you're welcome :) | 21:30 |
DktrKranz | sebner, did it? | 21:30 |
sebner | DktrKranz: if the build logs aren't lying | 21:30 |
DktrKranz | and why it FTBFS in our buildds? | 21:32 |
azeem | sebner: are you sure that wasn't a wrapper package or something? | 21:32 |
azeem | AFAIK qmail is currently in Debian NEW | 21:32 |
sebner | DktrKranz: build log says missing orig.tar.gz | 21:32 |
sebner | azeem: well, we merge from debian. if wrapper package or not | 21:33 |
DktrKranz | sebner, arch: all, so it's not built from Debian | 21:37 |
* sebner is confused | 21:38 | |
DktrKranz | sebner, when you upload to Debian, you upload resulting binaries too, Ubuntu developer just upload sources | 21:40 |
sebner | I see | 21:40 |
=== mitsuhiko is now known as mitzzzuhiko | ||
DktrKranz | if you have an arch: all package, you upload your own copy of the package | 21:40 |
DktrKranz | and no build process is required | 21:40 |
sebner | DktrKranz: =) | 21:41 |
sebner | DktrKranz: do you know if netqmail is the source successor? | 21:41 |
DktrKranz | no idea | 21:43 |
DktrKranz | probably yes | 21:43 |
sebner | DktrKranz: I'll take a look tomorrow =) | 21:44 |
sebner | DktrKranz: thx for the infos. any special reason you are interested in qmail? | 21:44 |
DktrKranz | sebner, I'm having a look if I try to build it in my pbuilder | 21:45 |
DktrKranz | sebner, just trying to finish some merges ;) | 21:45 |
sebner | DktrKranz: it actually builds in pbuilder but not on the LP servers | 21:45 |
sebner | heh | 21:45 |
DktrKranz | so, I guess it lacks .tar.gz archive and needs to fetch it from internet | 21:46 |
DktrKranz | ubuntu buildds haven't internet access | 21:46 |
sebner | DktrKranz: could be a reason | 21:46 |
sebner | DktrKranz: debian build servers have? if no, then it's really just a binary upload | 21:47 |
DktrKranz | sebner, they have | 21:47 |
sebner | I see | 21:47 |
* DktrKranz is curious to see if upstream tarball could be legally inserted in debian/ | 21:49 | |
sebner | DktrKranz: is there any server which contains the sources files of packages which are in NEW ? | 21:50 |
DktrKranz | sebner, in debian? | 21:51 |
serialorder | in the process of merging protobuf it was decided that we should adopt the latest version from upstream even though it is not in debian yet | 21:51 |
sebner | DktrKranz: yes | 21:51 |
serialorder | i volunteered to do this but I am unsure how to proceed | 21:51 |
DktrKranz | sebner, packages.d.o has latest source packages | 21:51 |
sebner | DktrKranz: but there are packages in NEW which are Initial release | 21:51 |
serialorder | should i attempt it like it was a new package (ive never packaged something from scratch before) | 21:51 |
DktrKranz | sebner, if sources are accepted, they're mirrored | 21:53 |
DktrKranz | if you look for source NEW, you have to go at ftp-master.debian.org | 21:53 |
sebner | DktrKranz: that's what I wanted to know ^^ | 21:54 |
azeem | sebner: NEW is not accessible | 21:54 |
sebner | ARGHS | 21:54 |
sebner | right | 21:54 |
azeem | however, if this is still about qmail, I guess the maintainer provides the packages elsewhere | 21:55 |
azeem | note though that they got rejected due to packaging issues before | 21:55 |
nhandler | soren: ping | 22:12 |
norsetto | hmmm, is it me or bazaar.launchpad.net is "down"? | 22:37 |
pochu | norsetto: launchpad is down :-) | 22:38 |
pochu | norsetto: being upgraded, should be up and running in 20 minutes | 22:38 |
norsetto | puchu: ahhh! thx | 22:39 |
norsetto | pochu: ops. I mean, pochu ... | 22:39 |
=== mitzzzuhiko is now known as mitsuhiko | ||
serialorder | in the process of merging protobuf it was decided that we should adopt the latest version from upstream even though it is not in debian yet. I volunteered to do this but I am unsure how to proceed. Should I treat it like packaging a new package or is there some other process? | 22:41 |
skorasaurus | mok0, how was dinner :D | 22:41 |
jdong | sigh, stupid bluetooth bugginess. | 22:42 |
jdong | my capslock inverted. | 22:42 |
skorasaurus | I issued debuild and it failed to compile because gtk was not found, although i had it installed (at least on my own computer). | 22:43 |
skorasaurus | how should I remedy this ? | 22:43 |
mok0 | skorasaurus: great. Sushi :-P | 22:43 |
* skorasaurus is envious | 22:44 | |
jmarsden|work | skorasaurus: You are probably missing some gtk -dev package or other? | 22:44 |
skorasaurus | i looked in the config.log file, saw that in the output variables, GTK_LIBS='' | 22:45 |
jdong | humor does NOT work with airline representatives for rescheduling flights without charge | 22:57 |
jdong | just as a FYI :) | 22:57 |
Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!