=== nhandler_ is now known as nhandler [00:57] <_16aR_> I'll just have fixed the problems Dave hasn't fixed on fsniper (watch file, and distrib version name change). Can anyone review it ? It is a directory watcher/script automater based on inotify (very practical to sync directories on the fly) : http://revu.ubuntuwire.com/details.py?package=fsniper [01:02] <_16aR_> and another one : hexdiff, a package to visually analyse binary differences between 2 files (in hexa off course). Nobody has put any comments right now, so it could be cool to look at it : http://revu.ubuntuwire.com/details.py?package=hexdiff [01:06] <_16aR_> just added some debian/examples for fsniper [01:34] would a new Debian release fixing only incorrect licensing in a package (which is serious severity on debian BTS) be worthy of a merge? [01:34] nellery, depends. Is the package violating Ubuntu policies? [01:35] cody-somerville: the packages debian/copyright file claims that the package is distributed under LGPL, when it is GPL [01:36] slangasek, ^^ [01:36] hrm? [01:36] (note that there are 6 related packages involved) [01:36] slangasek, Can you advise nellery? [01:36] nellery, Is there a bug report in Ubuntu yet? [01:37] cody-somerville: I don't believe so [01:37] I would say it's worth merging, but I'm not volunteering to merge it... [01:37] nellery, theres your answer :) [01:37] cody-somerville, slangasek: thanks [01:48] does anyone has experience with random mini-dinstall hick-ups? [01:52] I dput local *.changes; then mini-dinstall --batch; then apt-get update; [01:52] and when I do apt-get install my_package [01:52] it gives me errors mismatched size [01:54] Odd [01:54] All I can say is that I found reprepro more to my taste than mini-dinstall [01:55] Unless it's a *really* trivial local repo, in which case I can post the shellscript I use for my "dump some debs in a directory" style repo for pbuilder [01:58] maxb: that would be *really* usefull for me know [01:58] maxb: And i'll checkout reprepro [02:01] http://bazaar.launchpad.net/~maxb/%2Bjunk/apt-generate/annotate/head%3A/apt-generate [02:02] maxb: thanks! === freeflyi1g is now known as freeflying [03:18] I'm trying to build the mono package in Jaunty. I get this error: debian/dh_makeclilibs -i -m 1.0 --internal-mono [03:18] Unknown option: internal-mono [03:19] Does anybody recognise what error this is and/or how to fix it? [03:39] Can anyone point me to a tutorial to build multi binary debs... I want to package and host kde 3.5x built against Ubuntu Current... I am not entirely ignorant of how dpkg works used it for single binaries. [03:39] if i need to remove PDO from PHP, should I bother with recompiling the debian package, or just install PHP from source? [03:40] I looked through the Debian New Maintainer's Guide and it didn't go into multibinary debs [03:40] Don't know about a tutorial, but there's really not all that much to it - you just have multiple binary stanzas in debian/control, and install the relevant files into debian/PACKAGENAME as you would be doing in a single-binary package, but for more than one [03:41] Bsims: you can look at the KDE 3.5 packages to get an idea [03:41] Bsims: but that is an enormous task to do right [03:41] maxb: Hrm I may took a look see at the current packages [03:41] LaserJock: I was hoping there was a script kind of like buildkde that dumped a Pile'O'Debs [03:42] Bsims: I have to say.... packaging an entire DE sounds incredibly hard. Is it really worth it? [03:42] Bsims: no, you'll want pbuilder/sbuild and build the packages in the right order [03:42] maxb: Well I run nightly neon and well 4.x as it stands at the moment sucks at least as far as I am concerned [03:42] * Bsims nods thanks LaserJock nice to know the RIGHT tool to research [03:44] there's a reason why Kubuntu has dropped 3.5, it's a lot of work to maintain [03:44] any project that size is [03:44] * Bsims nods I remember the transition to 3.x for KDE [03:45] thing is I've refined my dot file from 1999 to current... I /know/ how 3.5 works at least from a user perspective [03:45] pbuilder is a tool for building packages in a clean build environment. Making packages that build in a clean environment is important, but you would probably want to start out simply building the packages in your existing installation. For that, see dpkg-buildpackage (or debuild, a thin wrapper over that) [03:45] Bsims: sure [03:45] And for me 4.x isn't there yet [03:45] persia: Are you going to upload gebabbel from REVU? Or do you want me to go ahead an upload it for you? [03:45] When you do want to prove that it builds cleanly, I think pbuilder is a bit easier to get to understand than sbuild [03:46] * Bsims nods maxb I've used dpkg-buildbackage but only for single binary packages [03:46] when you want .debs that are distributable you want pbuilder/sbuild [03:46] You definitely want to look into using cowdancer's cowbuilder wrapper for pbuilder - the speed benefit is considerable [03:46] Coool [03:46] I don't trust dpkg-buildpackage alone for any binary building [03:46] * Bsims makes notes [03:46] LaserJock: worked for me for pan [03:47] for personal consumption yeah [03:47] * Bsims grins well yeah but that was my focus before [03:47] dpkg-buildpackage is appropriate for when you are developing the package. pbuilder or sbuild is for when you are checking its sane for release to an audience [03:47] or when it needs to build for a different distro than you are running [03:48] * Bsims /does/ have to whine about kubuntu deciding to convert existing .kde directories to kde4 surely .kde4 would have been less disruptive [03:48] The invocation of dpkg-buildpackage is the same whether you're building a single-binary or multi-binary source [03:48] * Bsims adds notes about what to use when [03:48] Bsims: That's what we did during Hardy when we were trying to support co-installability [03:49] maxb: I tried turning it loose on the source and telling it multi-binary and it got confuseled [03:49] ScottK: IIRC its how Debian handled it back then [03:49] you don't tell it multi-binary [03:49] Bsims: If you want current KDE, kde3.5.10 is packaged and in Hardy. It'd just be a matter of rebuilding them. [03:49] What do you mean "telling it multi-binary". There's no such option [03:49] * Bsims nods I'll look there [03:49] multi-binaryness is a property of the source package - not the command you use to build the source package [03:49] Not for dpkg-build package [03:50] Sorry telling dh_make that its multiple binary [03:50] Bsims: you shouldn't be using dh_make [03:51] dh_make is for getting a template for creating a source package from scratch [03:51] LaserJock: what should I be using, I was following the Debian New Maintainers guide [03:52] Mostly thats what I use it for.... is converting tar.gz that is too new to be packaged on ubuntu [03:52] Bsims: ok, but you really really don't want to do that for KDE [03:52] Bsims: you want to grab the Hardy source packages and just rebuild them on Intrepid or whatever release you running [03:53] * Bsims nods does sound like far less work [03:53] when you consider how much time went into those packages, yeah [03:54] * Bsims grins and I appriciate it... [03:54] * Bsims sends donations at tax time labled packager's beer fund [03:56] I guess in part my hostility to 4.x for kde is I have spent years refining how kde works for me and don't wanna change [03:56] that's reasonable, it's just hard for a project to progress without breaking some old habits first [03:57] But would it kill them to let me add a shortcut to that toolbar with a right click? [03:57] * Bsims winks [03:57] LaserJock: when I got started Debian was bragging about how the Potato had landed [03:58] and that was after a year or so of SuSe back when they spelled it that way [03:58] * Bsims winces damn 1999 doesn't seem that long ago [03:59] * Bsims smiles 4.x will get there... 3.x did eventually [03:59] 4.2 is very nice [03:59] and I've been using gnome for years [04:00] LaserJock: I am running nightly neon to avoid conficts with the 3.5 packages I installed third party... I know bad bad me [04:00] * Bsims grins and well its purty... but I can't figure out how to add shortcuts to it's toolbar nor install themes for kopete [04:00] minor issues I know but still [04:01] That and k3b hasn't made the move yet... its my prefered cd burner app on any platform [04:02] * Bsims laughs sad as I spend the time not in Pan, firefox, transmission and K3B is in a urxvt terminal running GNU Screen === calc_ is now known as calc === nschembr is now known as nschembr-sleep === hyperair__ is now known as hyperair [06:43] is it an RC bug if the source code files have licensing information missing? [07:06] good morning [07:06] Good morning Daniel! [07:06] hiya iulian [07:07] How are you this morning? [07:07] very good, just need another coffee to get going :) [07:07] how are you? [07:08] I am drinking my tea... [07:08] No more school till 9th of Feb! [07:08] :-) [07:08] Yaay! [07:09] yoohoo :) [07:18] /j #ruby [07:18] oops [07:18] still 1/2 asleep [07:20] lies! [07:21] heh it's 8am here [07:22] * jamesty1 grabs coffee [09:23] Hello! I need some help with Debian Policy versioning: will Hardy support building packages with Standards-Version bumped to 3.8.0? [09:24] artfwo: the Standards-Version field should not affect build-ability :) [09:25] but what if I specify "Homepage" field in debian/control? It's unsupported in 3.7 series, that's the "default" for Hardy, as far as I can tell [09:27] will such a control file be parsed without errors by packaging tools on Hardy? [09:27] leleobhz@dsp2:~$ sudo ld -Bdynamic -r -lxview -lolgx [09:27] ld: cannot find -lxview [09:27] for ubuntu, what is wrong? [09:28] (libs instaled) may be a bug? [09:38] artfwo, If you use a newer standards version than is available in a given release, you may not have support for certain new features: you'd have to check the underlying tools (dpkg in the case of Homepage). [09:39] leleobhz, Do you also have the -dev packages installed? Can you find the libraries manually (in /usr/lib)? [09:40] persia: there's a lot of features for 3.8.0 standards; is there an automated way to check compability with all the tools? Or is it just okay to stick my package at 3.7.3 if I want to build it on older Ubuntu releases? [09:43] artf [09:43] artfwo, The actual number you use doesn't really matter, although it's nice when it's accurate. [09:44] More important is that if you rely on any tool features you should check to see if they are supported for a given target. [09:44] There's no automated way to do this: far too many tools, and far too many use cases for the tools. [09:45] So just changing Standards-Version: won't make any difference at all: it's changing the other things that make a difference. [09:45] understood, thanks! [09:45] For example, if you want to know if Homepage is supported, determine which tools are likely to look (at least dpkg, maybe others), and check their changelogs. === hyperair__ is now known as hyper195 === hyper195 is now known as hyperair === _neversfelde is now known as neversfelde [10:34] can some one unsubscribe universe-sponsors from bug 322648. It looks like its invalid because of a merge needed. Another pair of eyes is appreciated [10:34] Launchpad bug 322648 in libgeda "Please update libgeda to the latest version 1.4.3" [Undecided,Confirmed] https://launchpad.net/bugs/322648 === asac_ is now known as asac [10:37] another question. How do I find the reason for the removal of a package from multiverse? the bug in question is bug 293585 [10:37] Launchpad bug 293585 in spim "spim package missing in intrepid" [Undecided,New] https://launchpad.net/bugs/293585 [10:39] tuxmaniac: I replied to the libgeda bug [10:45] tuxmaniac: no idea when it was removed - in any case it was removed from Debian too [10:47] dholbach: aah thanks for the second answer [10:47] regarding the first one, i missed it completely. Relied a bit on http://qa.ubuntuwire.com/multidistrotools/science.html#outdatedandlocalinB [10:47] and forgot to see the naming of the package [10:47] dholbach: thanks for the review comment [10:49] If I want to something which has two configure scripts, with CDBS, how would I go about doing this. It's like I want to do the whole process twice, I guess. [10:56] could someone review my package geanyvc please? http://revu.ubuntuwire.com/details.py?package=geanyvc [10:59] tuxmaniac: https://launchpad.net/ubuntu/+source/spim/+publishinghistory [11:00] tuxmaniac: click on the expander in the "Deleted" row [11:00] dholbach: i already did that. Thanks for digging that info [11:01] no worries [11:02] mok0: codelite seems to ftbfs on a few architectures. do you know where i can get access to an ia64 buildd for testing purposes? [11:02] hyperair: no, sorry [11:02] sigh. [11:02] did you ask on #ubuntu-devel? [11:02] so what should i do about it? [11:02] eh? [11:03] no i didn't [11:03] i'll go ask [11:03] no wait, i did [11:03] a few days ago [11:03] no reply [11:03] yeah, it a problem [11:03] i tried using qemubuilder, but it doesn't support ia64 [11:03] hyperair: perhaps refer upstream to the errormessage? Perhaps he'll know what to do [11:04] mok0: i did refer upstream. he's the one who came up with the fix, but i can't test it without an ia64 buildd [11:04] mok0: and he doesn't have an ia64 machine to test out either [11:04] hyperair: sigx still has problems also, seems only to work on i386-derived archs [11:04] mok0: so it seems [11:04] stupid scons [11:05] hyperair: of course the poor-mans fix is to exclude those archs [11:05] that would mean anything depending on that library wouldn't work [11:05] hyperair: yes, but it wouldn't anyway, since the library doesn't build [11:06] mok0: true. [11:07] hyperair: Fortunately, the packages built on the most important archs [11:07] yeah [11:08] but failed for every other. [11:08] i tried looking into qemubuilder for ia64, but it seems qemu doesn't have ia64 support [11:09] hyperair: no [11:09] * mok0 goes to meet buddy for lunch... see you in a while [11:09] alright see you [11:14] if one is modifying the debian part of a package sync'd from debian (a file in debian which is copied in wholesale) should you be adding that as a patch in the patches directory or just modifying it directly? [11:15] also can someone remind me of thee magic command to build a patch [11:17] apw: diff -Nurp package-directory.old/ package-directory.new/ > name.patch [11:17] there was some debfoo command which you could debfoo and then edit the source and it did the right thing [11:18] apw: do you mean dpatch? [11:19] ahhh that sounds more like it thanks [11:20] apw: http://www.tuxmaniac.com/blog/2008/01/25/dpatch-just-superb-a-short-how-to/ [12:29] hmm, zapping in jaunty calls MAKEDEV in the postinst, and no newer version in debian ... that doesn't look good [12:34] Hi! I have just confirmed a bug, Can I assign myself to fix it?: https://bugs.launchpad.net/ubuntu/+source/sun-java6/+bug/321863 [12:34] Launchpad bug 321863 in sun-java6 "Name of JDK documentation zip has changed" [Undecided,Confirmed] [12:35] This will be my first ever attempt..Seems like a easy fix. So can I just go ahead and assign it? === warp10_ is now known as warp10 [12:41] cornucopic, Yes: please assign yourself if you plan to fix it. [12:42] Cool.. [12:42] persia, Is it also necessary to confirm the issue in a latest dev release? [12:43] cornucopic, No, but it's necessary to fix the issue in the latest dev release *first*, and it's likely that confirming/testing there will be a component of that. [12:44] persia, That brings me to my next question: What is the best way to setup a development test bed? [12:44] I am looking at https://wiki.ubuntu.com/UbuntuDevelopment/UsingDevelopmentReleases [12:45] cornucopic: chroot+Xephy [12:45] cornucopic, Install on a spare machine, install on a machine that you can afford to troubleshoot when it breaks, install in a VM, or use a chroot. [12:45] I am looking at using VirtualBox/KVM m/c as my test bed.. [12:46] Which bits do I install there? the nightly ISO;s..? If that is the case, how do I keep updated.. by updating the packages? [12:47] freeflying, What is Xephy? [12:47] freeflying, Google doesn't have a answer [12:47] cornucopic: xserver-xephyr - nested X serve [12:48] cornucopic, I'd suggest installing a recent Alpha, and dist-upgrading. [12:48] cornucopic: sorry for typo :) [12:48] freeflying, xephyr has other issues ... [12:48] persia: what's that? [12:48] freeflying, np. [12:48] persia, hmm.. [12:49] freeflying, Need for locally installed support for remote X access (e.g. Xinput, etc.), which can mix parts of the test system and local system in confusing ways. [12:51] persia: hehe [12:51] freeflying, So, if you're testing e.g. Xubuntu Jaunty on Kubuntu Jaunty, Xephyr works great, but if you're e.g. testing Ubuntu MID Jaunty on Kubuntu Intrepid, it's painful. [12:52] persia: for such a case, I would use emulator :) [12:52] freeflying, Yeah. A VM is easier :) [12:54] persia, So I am done installing a Alpha version..Now where do I get the package sources? [12:54] cornucopic, apt-get source foo [12:54] ah..okay..thanks :-) [13:02] persia, Once the source modifications are made, I will build the package with Pbuilder? PPA? sbuild? [13:03] Any of those work. pbuilder or sbuild are probably better for an initial test build, just because they can build the same version twice. Of those, I happen to use sbuild, but many here use pbuilder. [13:04] hmm.. [13:06] <_16aR_> I'll just have fixed the problems Dave hasn't fixed on fsniper (watch file, and distrib version name change). Can anyone review it ? It is a directory watcher/script automater based on inotify (very practical to sync directories on the fly) : http://revu.ubuntuwire.com/details.py?package=fsniper [13:18] * mok0 takes a look at fsniper [13:20] MOTUs, sabnzbdplus (binary newsreader, written in python) needs a second advocate - please consider for review: http://revu.ubuntuwire.com/details.py?package=sabnzbdplus === sommer_ is now known as sommer === azeem_ is now known as azeem [13:56] Just fixed a package with WiFi drivers... (rt28xx-linux-sta) but this was split into two by request from superm1. [13:57] Can anyone have a look? Being WiFi drivers IMO they need to make it into Jaunty before deadline. [13:57] henrik-hw0: I agree [13:58] henrik-hw0: I already advocated the unsplit package AFAIR [13:58] henrik-hw0: link? [13:59] http://revu.ubuntuwire.com/details.py?package=rt2870-linux-sta [13:59] http://revu.ubuntuwire.com/details.py?package=rt2860-linux-sta [13:59] thx [14:00] henrik-hw0: I guess they should go -> main eventuall [14:02] main - that's for officially supported packages, no? [14:04] henrik-hw0: yes, and packages that ship on the CD [14:04] henrik-hw0: The archive-admins will decide [14:06] henrik-hw0: Be prepared for 1 problem [14:15] I'll email RALink about the problem. [14:23] ScottK: what to do with a package that does use makedev in the postinst? (remember seeing a message on ubuntu-devel-announce about it not being feasible) [14:23] * ScottK looks around for someone who knows .... [14:24] henrik-hw0: great, thanks! [14:25] * a|wen considered filing a bug and get someone with powers to give it a reasonable importance [14:25] https://lists.ubuntu.com/archives/ubuntu-devel/2009-January/027184.html [14:25] a|wen: what does said package do with makedev? [14:27] james_w: try to create /dev/v4l [14:28] a|wen: and what does that device do? [14:28] is it associated with hardware? [14:28] the fact that it is not numbered suggest it isn't, or at least that it will be problematic to migrate away from it [14:29] james_w: it has something to do with video4linux ... i guess [14:29] * a|wen tries to find out exactly what it does ... it checks for /dev/video0 as well [14:30] the idea is that the kernel creates device nodes via udev [14:32] james_w: running it seems to generate 196 device creation errors [14:35] I've packaged a couple of new applications now, what would be recommended for me to do next? Patch testing and reviewing? [14:36] Piratenaapje: stick'em in your PPA. We're short on reviewers :-) [14:38] mok0: I didn't create one yet, guess I'll do that next :p [14:38] james_w: the big question is: is it important, so we need to do something about it? [14:39] Piratenaapje: it's real easy, on LP [14:39] a|wen: Isn't /dev/v4l normally a directory? [14:39] oojah: no, it's probably created by the driver [14:39] oojah: it's very likely [14:40] * a|wen has no video devices to check it [14:40] mok0: should i just leave sigx and codelite as it is, or find some fix/exclude the architectures? [14:40] mok0: You sure? I'm fairly certain /dev/v4l/video0 would be created by the driver. [14:42] a|wen: i've some... what's the package in question? [14:42] gaspa: zapping [14:49] Hmm why does my ppa only build the i386 version? :s [14:50] Piratenaapje: it should build all, aren't they queued? [14:50] No, only the i386 is queued [14:50] Piratenaapje: give it some time [14:51] mok0: One package is building the rest as well, just the one with architecture "all" is only build i386 [14:51] a|wen: I've not Tv devices, only bttv framegrabber... but i guess postinst of zapping is not the right place to have device creation... [14:52] Piratenaapje: that's because it only needs to be built once [14:52] gaspa: exactly what i noted ... but the question is if it actually hurts anything [14:52] mok0: Right :p [14:52] Piratenaapje: i386 builder builds "all" arch [14:53] mok0: Ok, it's just a bit confusing [14:53] a|wen: do you mean "without makedev"? [14:53] Piratenaapje: he, yeah [14:53] gaspa: as it is read only i don't suppose it gets allowed to do anything with makedev [14:54] Piratenaapje: what is confusing is the arch name "all" ... it should be called "indep", "noarch" or the like [14:54] a|wen: in fact [14:55] gaspa: or can it actually hurt so it should be patched out? [14:56] a|wen: i think it doesn't hurt, though it's irritating having so much errors. [14:57] http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=148831 [14:57] Debian bug 148831 in zapping "zapping: Zapping should create video-devices" [Important,Closed] [14:58] james_w: but devices shouldn't be created by apps... [14:58] * iulian wonders why ubottu is not capable of showing a link when writing the bug # privately. [14:58] xawtv does "test -c /dev/.devfsd -o -c /dev/video0 -o -c /dev/v4l/video0 && mkdev="false"" [14:59] gaspa: I know, just adding to the information [14:59] * mok0 just got another 4G RAM in his rig today :-P [14:59] james_w: i see. [14:59] I assume the "/dev/.devfsd" check is for udev not running [15:01] dholbach: I made some suggested changes in the package (ubuntu-qa-tools) and I uploaded a new version [15:01] james_w: ok, xawtv does it better ( :P ), anyway I still don't like it ... they simply shouldn't crash without a /dev/video-something... [15:02] gaspa: for sure [15:02] gaspa: if you know what the solution is then please go ahead, I'm just trying to work out what to do [15:03] gaspa: i have a pending debdiff on the package already (for something completely different); that was why i noted it [15:04] a|wen: you could reply to the ubuntu-devel mail asking for guidance in this situation [15:04] ok [15:06] a|wen, james_w: i didn't have the right hardware to fully test it, but I'll have a look. [15:06] cool, thanks gaspa [15:07] gaspa: cool, thx ... please let me know if you want to start patching before my debdiff is in (ends in ubuntu1) [15:08] a|wen: ok. ( looking at sources... oh, what a mess... :| ) [15:09] gaspa: i know... [15:19] What are my chances of actually getting a mentor after applying? [15:20] Everyone seems kind of busy now [15:20] Piratenaapje: Pretty good last I checked [15:20] Piratenaapje, about 1 in 16 [15:20] hauts and the mentoring reception have been doing a nice job of getting mentors for people [15:20] Alright, time to have a go at it :p [15:21] Heya gang [15:21] Hiya bddebian. [15:21] Hi iulian [15:23] Hey bddebian [15:23] Hi bddebian [15:23] Hi nhandler, cody-somerville [15:26] Hi bddebian [15:34] geser: after long time. :-) [15:35] Piratenaapje: You can just ask questions here as you have them too. A formal mentor isn't required. [15:37] nhandler: ping. need to discuss your comments on monajat [15:38] what is the usual process to upload a package from revu into archive? How do I generate the notification mail? [15:38] ScottK: well, basicly I need to know what I should do next, I've packaged a couple new applications myself, but am not sure where to look now. [15:39] slytherin: You'll get mail back from Soyuz after the upload. Just add REVU to the subject and forward to the list. I usually trim it a bit for readability, but it's not required. [15:41] ScottK: Ok. I thought they were auto generated mails [15:46] hi everyone... we have a goal of getting rid of aRts (the kde3 soundserver) for intrepid. in that regard there is a number of packages that needs rebuilding w/o arts-support [15:47] arts is so unsupported that upstream closed every single pending bug as wontfix. [15:47] the status is tracked on https://wiki.kubuntu.org/RemoveArts if anybody wants to help out ... [15:47] * ScottK encourages people to help out... [15:48] Piratenaapje: It's really a question of what you want to do as you're a volunteer. [15:48] a|wen: for intrepid? [15:48] dholbach: For Jaunty. [15:48] dholbach: for jaunty of course [15:48] a|wen: right-o - I was a bit scared already :-) [15:49] hehe :) [15:49] I would also really appreciate a review on the 3 debdiff's awaiting in bug 320915 - zapping, cmus and xsidplay [15:49] Launchpad bug 320915 in libsdl "Remove aRts from the archive - rebuild all dependencies" [Undecided,In progress] https://launchpad.net/bugs/320915 [15:51] ScottK: Well, basicly any task that a MOTU should do, but I'm not sure what task I should try first [15:52] Piratenaapje: At this point we're getting to where we need to focus on bug fixes. [15:52] ScottK: so I should review and test patches? [15:52] If you look at the output of the Universe section of merges.ubuntu.com and see anything that looks like we really ought to have it, preparing a merge would be useful. [15:52] That too. [15:53] dholbach: scared? Hardy had a library transition via SRU ;) [15:53] ScottK: Doesn't the last uploader usually provide the merge? [15:54] Piratenaapje: Generally, but after Debian Import Freeze, it's usually considered a free for all. [15:54] The question is there anything that really needs doing that's been missed. [15:57] ScottK: Alright, I'll try to see if anything comes up [15:57] Who do I subscribe to sync requests for packages in main? [15:58] ubuntu-main-sponsors [15:58] Thanks [15:59] Can I upload a package to the revu site if it is not mine? It's the ubuntu-tweak package witch needs to be added another repo to make people able to apt-get it? [16:00] Can I ack my own universe sync request and subscribe the archive admins? [16:00] JontheEchidna: Yes. [16:00] sweet [16:00] oh no, JontheEchidna with pow'as [16:00] muwahahaha [16:01] hola [16:01] sorry hello everyone.. [16:01] I have a quick ? [16:04] I have a launchpad account and I have been packaging items. When you send to revu is it better to have it in you ppa and revu..?? [16:04] ScottK: would you recommend me to apply for mentorship, or will I be able to become a MOTU anyway if I contribute? [16:04] lajjr: It won't hurt to have it in both places [16:05] great.. [16:05] Piratenaapje: It's a question of personal style. Getting a mentor is absolutely not required. I'm not convinced it helps much, but if you're to shy to ask questions in public, then maybe you should... [16:06] Up to you really. [16:06] JontheEchidna: thank you.. [16:06] ScottK: I don't mind that much really with asking questions, but I guess I prefer to have someone to fall back to. [16:06] I guess it's a bit harder to find tasks at the start without a mentor feeding them to you, but I managed to get along fine (did I?) without one [16:07] lajjr: you're welcome. If you do put it in a PPA it does show that it at least builds and it makes for easier runtime testing [16:07] but putting it in a PPA is definitely not required [16:08] Ok thanks for the advice, I guess I'll ask for mentorship anyhow :p. [16:08] argh, it supports 81 music formats, and i've heard about none of them! ... removing arts also consist of testing obscure music players [16:09] ok cause I just completed all the setup from my building systems and testing. But the ppc has to be tested by me..ppa does't build that one..right? [16:12] * lajjr leaving [16:26] Heya geser (late) :) === nschembr-sleep is now known as nschembr-work [16:48] How does one go about getting backporters for a package? [16:49] Chris`: you can backport it yourself in a first time [16:49] !backport [16:49] 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 [16:49] What if the distro doesn't have that package and if it is new in Jaunty? [16:50] it's the same [16:50] (AFAIK), ScottK can confirm [16:50] That's correct [16:51] could someone review my package http://revu.ubuntuwire.com/details.py?package=geanyvc please? [16:51] Actually I'm even more inclined to approve those as they have a 0% chance of breaking the existing package. [16:52] ScottK: when are backport request processed? 1 every two weeks? [16:52] It varies. [16:52] There's a multi-step process. [16:53] First it has to get tested, then a backporter has to approve, then an archive admin has to do it. [16:53] Chris`: you can make the process easier by trying to build it for the release you want it to be backported to, using f.e. "prevu pkge_name", then checking if it runs [16:53] None of those have a particularly fixed schedule. [16:53] Chris`: also providing backported packages on the bug report so others can try it [16:54] Hey guys, does anyone have a second to help me with an amd64 build problem? It seems it can't find libc.so.6 on that platform. [16:54] ScottK: thanks [16:57] info: for french speaking people, there is a packaging session in #u-classroom beginning in a few minutes [16:57] Adri2000: About what? [16:57] packaging :) === dholbach_ is now known as dholbach [17:04] g'evening dholbach. [17:04] hiya jpds [17:06] doctormo: Hmm, odd, could you possibly pastebin the error at paste.ubuntu.com? [17:07] james_w: Since when were you an archive admin? Or is this random sync processing? :O [17:07] jpds: http://launchpadlibrarian.net/21693635/buildlog_ubuntu-intrepid-amd64.wizardpen_0.6.0.3-0doctormo2_FAILEDTOBUILD.txt.gz [17:07] no need to pastebin, it's available for all [17:07] Laney: nothing gets past you does it? :-) [17:07] The maxima and wxmaxima packages are outdated in Ubuntu and Debian. Can I help fix that? [17:07] not when it's my bugs ;) [17:08] Laney: I'm in training, that was my first sync run. [17:08] To be honest, I saw your name and thought I'd cocked something up [17:08] heh [17:09] don't worry though, I'm being "sponsored", so I can't rm the archive or anything :-) [17:10] bah, that's no fun [17:10] doctormo: Maybe you need to heed: "To help dpkg-shlibdeps find private libraries, you might need to set LD_LIBRARY_PATH." [17:10] nice one though, moar power! [17:11] jpds: I don't think I know enough about deb packaging to do to that. Is LD_LIBRARY_PATH something that's set in the rules? [17:11] jpds: And how would I know what the correct dir to add is? [17:11] libc.so.6 should be in the default search path === Pricey is now known as Guest39261 [17:13] azeem: could it be that the build server go muddled? it was very busy, took 5 hours to build. [17:13] does it build in your pbuilder? [17:14] and did you test-build it on amd64? [17:14] azeem: no, I'll have to look up what that is [17:20] azeem: OK found howtos and running through them now. It's taking it's time to make the pbuilder. this is to be expected? [17:20] azeem: oh it only happened on amd64 too [17:20] What is the way to get a translation (man page, .po file...) for a packaged program? I'm thinking it doesn't go into the package, so where do we send it (as well as upstream of course ;) )? [17:20] s/get/upload/ [17:21] doctormo: you'll probably have to inspect the build system and see whether it does anything weird with RPATH on amd64 (or maybe if $libdir is /usr/lib64 or something) === _neversfelde is now known as neversfelde === emh is now known as emnh [17:51] ScottK: ping [17:51] rgreening: Pong. [17:51] ScottK: bug/321891 [17:52] ScottK: I have updated the bug and made the required changes to ensure this packages builds and operates as expected. [17:52] rgreening: OK. I'll have a look at it. I appreciate you sticking with it. kvirc is a bit of a pain. [17:52]