[00:16] <meoblast001> joaopinto: my deb is done :)
[01:18] <CarlFK1> https://bugs.edge.launchpad.net/poppler-python/+bug/312462/comments/4  can someone walk me though adding that to rules?
[01:19] <CarlFK1> currently there are no patches for that package, so no patches/ dir
[01:33] <meoblast001> making debs is fun :)
[01:34] <Laney> breaking debs is more fun
[01:35] <CarlFK1> where does fixing broken fall?
[01:35] <ScottK> Somewhere below breaking Laney and above making debs.
[01:35] <CarlFK1> cuz it seems the one I want to add a patch to is broken out of the box: http://dpaste.com/14543/
[01:36] <CarlFK1> I promise I didn't actually touch rules yet
[01:37] <CarlFK1> I thought about trying to add my patch, then figured maybe I should make sure it builds without it... and BAM!
[01:39] <meoblast001> Laney: my debs arent perfect but they work :P
[01:39] <Laney> always a good start
[01:39] <meoblast001> Laney: i'm publishing them on http://www.meoblast001.mysticgalaxies.com
[01:41] <CarlFK1> apt-get remove python-poppler-dbg = no error.  is that a bug, or expected?
[02:59] <crimsun> any main sponsors want to upload a fix for a PulseAudio syslog DoS?
[03:23] <stgraber>         ltspfs - 0.5.10-0ubuntu1~ppa1
[03:23] <stgraber> oops
[05:29] <adelie421> So I am trying to follow https://help.launchpad.net/BranchMergeProposals, but when I go to the page mentioned at 'grep XS-Vcs-Bzr ./deb/control', there is no 'action' menu. What am I doing wrong?
[05:30] <adelie421> the page only has two directories: changes and files. There is also a search bar, but nothing else.
[05:33] <adelie421> Hmm.. if the guide meant the launchpad overview page, I see no "Action" menu there either
[11:49] <pmjdebruijn> I built gnash-0.8.5 properly on my local system (Jaunty), but when I build it on PPA, it fails:
[11:49] <pmjdebruijn> http://launchpadlibrarian.net/23865538/buildlog_ubuntu-jaunty-amd64.gnash_0.8.5-0pmjdebruijn1~jaunty_FAILEDTOBUILD.txt.gz
[14:17] <geser> a|wen: Hi, as you were involved with the arts removal could you look at http://builder.ubuntuwire.com:9998/job/45324 ? there are several packages FTBFS in the rebuild test due to this. Is adding --without-arts the right fix without breaking the package?
[14:23]  * sebner winks geser :)
[14:27]  * geser waves back at sebner
[14:27] <sebner> geser: basic education done, starting with office job on monday :P
[14:28] <geser> nice, do you know what kind of office job you get?
[14:30] <sebner> geser: what kind?
[14:37] <geser> sebner: what will you do next week exactly?
[14:38] <geser> I got in a totally different unit after my basic training.
[14:41] <a|wen> geser: --without-arts should work in 95% of the cases; so trying that first should be the way to go
[14:41] <a|wen> geser: i can take a look at kxstitch now
[14:42] <sebner> geser: well, we got splited into 3 groups ( funker, antennenaufbauer, kabelträger). Ich wäre normal funker geworden (ist das beste, mit laptops arbeiten ..) aber da ich kanzleigehilfe bin, bin ich jetzt kabelträger (da fällts nicht auf wenn einer fehlt). es gibt ja bei uns offiziell keine schreiber weil wir reine "funker" sind. einer wird halt abgezogen und ist offiziell immer noch in einer der 3 gruppen und inoffiziell kanzleigehilfe
[14:43] <geser> a|wen: looks like the remaining KDE 3.5.x packages are affected from a first glance (like kde-i18n-*; see http://builder.ubuntuwire.com:9998/dist/jaunty/arch/i386/failed)
[14:43] <a|wen> geser: yeah ... all the kde-i18n packages failed, we are in the middle of fixing right now
[14:44] <geser> sebner: nett :)
[14:44] <geser> a|wen: so I can ignore them as you (kubuntu-devs) take care of them?
[14:45] <a|wen> geser: you can ignore all the kde-i18n-* packages ... but you are more than welcome to fix some of the other k* packages
[14:45] <a|wen> geser: after we get the kde-i18n-* up i'll try to look through the list as well
[14:46] <geser> a|wen: will do as I fight myself through the rebuild results
[14:46] <sebner> geser: mal schaun, normal sollte ich jetzt das schönste leben haben. ich hab halt angst das es mal heißt: Heute ist wenig zutun, du fährst mit gefechtsdienst oder anderer blödsinn. Weil der aktuelle gehilfe ist nämlich von ner anderen kompanie und den können sie nicht so einfach wegschicken. hoffe bei mir ist es aber auch nicht anderst als bei ihm
[14:47] <a|wen> geser: it is a long list it seems ... a lot of transitions happening this time around
[14:52] <a|wen> geser: if you want me to fix some of them, just ping me or/and add the package to bug 320915 and i'll look at it
[14:55] <maix> hi, to what status do i have to set a bug if i've attached a patch?
[14:57] <slytherin> maix: is it a patch or debdiff?
[14:58] <maix> patch
[14:58] <maix> ah and it's set to fix released atm
[15:02] <maix> slytherin:
[15:03] <slytherin> maix: so that means there is nothing more to be done.
[15:03] <maix> slytherin: yes, but i've found something that's wrong
[15:04] <maix> it's that one here: https://bugs.launchpad.net/ubuntu/+source/transmission/+bug/182644
[15:06] <a|wen> hmm, how do you unsubscribe u-u-s from a bug?
[15:17] <geser> a|wen: ask someone from u-u-s to unsubscribe
[15:18] <a|wen> geser: i'm member of u-u-s now; how do i unsubscribe us?
[15:19] <geser> use the unsubscribe action on the bug
[15:20] <slytherin> maix: in that case, reopen the bug (set to new) and add comment.
[15:20] <maix> ok thanks
[15:20] <maix> (i commented already, marian sigler is me)
[15:21] <a|wen> geser: hmm; do i need to be direct member of u-u-s to do that; i only get the option to unsubscribe myself
[15:22] <geser> a|wen: yes
[15:23] <a|wen> ahh, everything makes sense then ... i wonder why ~motu is not a member of ~u-u-s
[15:24] <geser> if it's about bug 320915 I've unsubscribed u-u-s
[15:25] <porthose> Would a member of MOTU -release please have a look at Bug #186184, thank you ;-)
[15:25] <a|wen> geser: thx ... guess i should poke someone for a membership then
[15:27]  * ScottK grumbles about non-standard K* packages.
[15:28] <sebner> ScottK: it's KDE :P
[15:28]  * ScottK added --without-arts to CDBS so K* packages packaged in the standard way for KDE would work fine.
[15:29] <iulian> porthose: Commented.
[15:29] <a|wen> ScottK: and we're thankful for that :) ... but seems a lot of packages does not use the "standard way"
[15:29] <ScottK> Yep.  Apparently.
[15:30] <ScottK> Between that and Python 2.6 I think I know what I'm doing for the rest of this cycle.
[15:30] <porthose> iulian: Thank you :)
[15:32]  * iulian wonders why python3.0 has Ubuntu Core devs as the Maintainer and the package is in universe.
[15:32] <iulian> porthose: You're welcome.
[15:33] <iulian> Looking at https://edge.launchpad.net/ubuntu/+source/python3.0/+publishinghistory, the package has never been in main.
[15:36] <geser> iulian: probably the debian dir was c&p as python3 was also essential till it got fixed
[15:37] <slytherin> iulian: another copy paste error, similar to how it was set to 'Essential: yes'
[15:38] <slytherin> a|wen: not every motu is interested in working as sponsor.
[15:38] <jpds> geser: Thanks for the debootstrap Recommends catch, fixed.
[15:38] <joaopinto> I am trying to automate the console-setup install into a chroot, any tip on how to force it to install without asking for the kbd layout ?
[15:39] <geser> joaopinto: export DEBIAN_FRONTEND=noninteractive
[15:39] <a|wen> slytherin: and everybody would get all the bugmail for u-u-s if it was that way i presume... then it makes sense
[15:40] <slytherin> a|wen: right
[15:40] <joaopinto> geser, tried that, didn't help
[15:40] <joaopinto> debconf: falling back to frontend: Readline
[15:41] <joaopinto> debconf overrides it
[15:41] <joaopinto> the latest console-setup update broke my schroot build script :(
[15:44] <iulian> geser, slytherin: Oh, thanks for clarifying it.
[15:57] <a|wen> if the package doesn't use a patch system and i want to make a small patch to "configure" is it then best parctice to add a patch system or not?
[15:57] <geser> a|wen: don't add a patch system as the package will probably end with some patches applied directly and some through a patch system
[15:58] <a|wen> geser: thx ... also my rationale; just wanted a confirmation
[16:19] <mcnicholls> hi
[16:20] <mcnicholls> got a quick question about cdbs patches. Anyone around?
[16:21] <slytherin> mcnicholls: just ask
[16:21] <imbrandon> just ask
[16:21] <imbrandon> :)
[16:21] <mcnicholls> ok thanks...
[16:22] <mcnicholls> when naming a patch, is the nuumber you give it at the start of the filename important? does it dictate the order patches are applied? if i am adding a patch do i just take the next highest avaliable number?
[16:23] <imbrandon> yes and yes
[16:23] <azeem> mcnicholls: depends on the patch system
[16:23] <mcnicholls> sorry it is cdbs
[16:23] <imbrandon> azeem: i think he means cdbs simple patchsys
[16:23] <azeem> oh, didn't read that far back, sorry
[16:24] <mcnicholls> np. thanks for that. can i just run by you guys what i am attempting to do...
[16:24] <mcnicholls> https://bugs.launchpad.net/ubuntu/+source/tsclient/+bug/270374
[16:25] <imbrandon> yea that bug bits me in te arse almost daily
[16:25] <imbrandon> lol
[16:25] <imbrandon> bites*
[16:25] <mcnicholls> Someone has posted a generic patch, this has been submitted upstream, but i was wondering if i could patch it up for jaunty release?
[16:25] <mcnicholls> lol me too, would love to get it fixed and want to learn about fixing bugs
[16:25] <mcnicholls> so if i use that patch and produce a debdiff, do you think i could get it included?
[16:26] <imbrandon> should be able to as long as you follow the process
[16:26] <imbrandon> its a bug only fix
[16:30] <mcnicholls> so once i have a debdiff that i attach to the report, i read i just add the sponorship group and someone should upload it? anything else i need to do?
[16:30] <imbrandon> i'm not sure with the exact process this cycle, but that sounds right
[16:30] <mcnicholls> ok thanks
[16:30] <mcnicholls> i shall attempt to get the diff, but am sure i shall be back for more help
[16:30] <imbrandon> sure thing :)
[16:30] <imbrandon> ok time to kill off this screen session, bbiab
[16:30] <slytherin> mcnicholls: yes, that is how sponsorship works
[16:30] <mcnicholls> one question i do have now though, i know you can run a script to submit patches and bug reports to debian. should i do this or would you normally wait for upstream to come down?
[16:31] <slytherin> mcnicholls: Once the patch is accepted in Ubuntu, you can forward it to Debian if you want.
[16:32] <mcnicholls> suppose it is up to them deb maintainer to decide if it is worth having
[16:33] <mcnicholls> i was just wondering if i should run the submittodebian script once i have my patch. I suppose i would wait till ubuntu accept it like you say
[17:06] <mcnicholls> if i am generating a patched package from someone elses source patch, should i give them credit in the change log somehow?
[17:07] <a|wen> mcnicholls: allways a good idea to give credit to the original author
[17:08] <mcnicholls> a|wen: yeah i thought so. any particular recommended way of putting this in the changelog?
[17:10] <a|wen> mcnicholls: not really... you can just append an "Original patch by ...", "Patch taken from ..." or "Thanks to ..." at the end of the line about adding the patch
[17:10] <mcnicholls> ok, will do. thanks
[17:10] <a|wen> mcnicholls: depends on if it is a person (then i prefer the last) or a project, like upstream / debian / $linuxdist (then i use one of the first two)
[17:11] <a|wen> but everyone has there favourite method ...
[17:11] <mcnicholls> yeah it's a person who posted the patch against the bug, so i have gone for the last one ;-)
[17:11] <a|wen> :)
[17:33] <a|wen> how do you figure out what goes wrong with ld in such a case "/usr/bin/ld: cannot find -lMagick++"?
[17:43] <geser> a|wen: first check if libMagick++.so is available in /usr/lib (or /lib for some special libs)
[17:44] <geser> if it's due to missing build-depends
[17:46] <geser> if that's the case then the next step is: who is missing this build-dependency? is it direct (the app using the lib itself) or if it's dragged in through an other lib (.la files or .pc files)
[17:50] <a|wen> geser: okay; so that is how you get from the -l option to the filename ... hmm, it depends on libmagick++9-dev, provided by libmagick++-dev, which has the file
[17:57] <a|wen> ahh, it actually complains about "Magick" ... libmagick++9-dev used to have /usr/bin/libMagick.so; it is now replaced/provided by libmagick++-dev which does neither have the file nor depend on a package with it
[18:01] <a|wen> geser: do you know of any way to search for a file in jaunty (if you are not currently running it, then apt-file can of course be used)
[18:01] <geser> packages.ubuntu.com :)
[18:02] <mcnicholls> If i wanted to help clear the NBS but i am not a registered developer, would i do this by filing a bug report and getting sponsorship as with other bugs?
[18:03] <geser> mcnicholls: yes
[18:04] <a|wen> ahh, great
[18:11] <mcnicholls> geser: cheers
[18:13] <a|wen> geser: thanks for pointing me in the right direction, it finally build :) ... for the record if you ever have a package FTBFS with a depends on libmagick++9-dev you might need to change it to graphicsmagick-libmagick-dev-compat
[18:15] <geser> a|wen: that will only work for packages in universe. what about libmagick++-dev? doesn't it work with it?
[18:15] <a|wen> geser: not if it uses "Magick" features as well as "Magick++"
[18:16] <a|wen> geser: /usr/lib/libMagick.so is only in graphicsmagick-libmagick-dev-compat in jaunty
[18:22] <a|wen> geser: and the /usr/lib/libMagick.so.* files which used to be in libmagick10 is no more
[18:49] <fabrice_sp> Hi. Should a package that depends on python2.5 (>= 2.5) be rebuilt to depend on python2.6 (>=2,6)? or it's ok for Jaunty?
[18:50] <fabrice_sp> package is ekg (http://packages.ubuntu.com/jaunty/ekg)
[18:51] <geser> it would be good if we minimize the dependencies on python2.5
[18:51] <ScottK> fabrice_sp: It should be rebuilt.
[18:52] <fabrice_sp> ok. quadrispro let me thought it's ok. I'll reactivate 2 bug reports I invalidated. Thnaks
[19:44] <Adri2000> could a backporter push forward bug #335692 please?
[20:53] <fatal_> Hi.. recently upgraded from Intrepid to Jaunty. I'm seeing graphics corruption on Intel using compiz.... anyone know if there are any driver updates planned before the release?
[21:41] <maix> I've created a debdiff using this manual: https://wiki.ubuntu.com/PackagingGuide/Recipes/Debdiff . I had to use my gpg key for that. Why?
[21:43] <directhex> maix, because debuild will sign a changes file by default, using the gpg key corresponding to the most recent entry in changelog
[21:43] <maix> directhex: but for the debdiff is it not needed?
[21:43] <directhex> debdiff itself? no.
[21:44] <maix> k
[21:44] <ScottK> Pass -us -uc to debuild and then it won't sign the packages.
[21:44] <maix> I've created a debdiff now, is there anything else I can do or is the rest done by the maintainers?
[21:44] <directhex> indeedy, hence "by default"
[21:45] <maix> yes that was mentioned in the guide
[21:45] <ScottK> maix: Did you attach the debdiff to a bug and subscribe ubuntu-universe-sponsors to the bug?
[21:45] <maix> I'm just about to attach it, but wanted to ask before submitting
[21:45] <maix> it's main afaik
[21:45] <directhex> did you remember to update-maintainer (if required)?
[21:45] <ScottK> Then it's ubuntu-main-sponsors.
[21:45] <maix> directhex: yes, but it was already ubuntu main devs
[21:46] <maix> ScottK: ok
[21:46] <maix> they'll contact me then?
[21:47] <maix> ah and when i'm here: check the patch checkbox for debdiffs?
[21:47] <maix> (and what's the use of that checkbox btw?)
[21:48] <maix> do I have to set the status to something? in progress or so?
[21:51] <maix> directhex: ^
[21:51] <directhex> just leave it be, IME
[21:52] <maix> ok
[21:57] <maix> directhex: one more question: when fetching the source (apt-get source), it told me that this package is maintained using svn and told me the url of some svn repo at debian. is that important for this case?
[22:01]  * porthose hangs up his "gone fishin" sign ;-)
[22:02] <directhex> maix, it can provide you access to more recent packaging work, where e.g. bugfixes may exist
[22:03] <maix> hm it's just a little patch that has already been fixed in upstream and in other ubuntu releases
[22:06] <wardi> I've tried to follow the FFe guidelines for https://bugs.launchpad.net/ubuntu/+source/urwid/+bug/343347  Would someone mind having a look and let me know if I'm missing anything?
[22:13] <nhandler> wardi: Why is the bug marked Fix released?
[22:13] <dennda> Hi. Am I right assuming that universe is already frozen for jaunty? That's not too clear from the release schedule...
[22:14] <dennda> Ah I should read the /topic
[22:20] <wardi> nhandler: I guess I misunderstood that.  The fix is in upstream (debian unstable)
[22:20] <wardi> nhandler: what should I have it set to?
[22:21] <wardi> s/it/the bug status
[22:21] <nhandler> The status should be New since no FFe has been granted yet
[22:21] <wardi> ok
[22:22] <nhandler> wardi: You will want to mention what testing you have done
[22:22] <wardi> nhandler: "when the upload is done" confused me here: https://wiki.ubuntu.com/FreezeExceptionProcess#FeatureFreeze for bug fix only updates (process agreed by motu-release)
[22:24] <nhandler> wardi: I missed the part about bug fix only. If that is the case, subscribe ubuntu-universe-sponsors to the bug
[22:24] <wardi> nhandler: is updating the description or adding a comment preferred?
[22:24] <nhandler> For what?
[22:25] <nhandler> wardi: ^^^
[22:25] <wardi> adding description of testing done
[22:26] <nhandler> You can do that in a comment.
[22:26] <nhandler> Also attach a build log so that the MOTU that reviews it knows that it builds fine
[22:26] <nhandler> But you do *not* need a FFe
[22:27] <wardi> nhandler: ok, thanks :-)
[22:30] <mcnicholls> hi
[22:30] <wardi> nhandler: is a debian build log acceptable, or should I set up a jaunty chroot and rebuild?
[22:30] <mcnicholls> had a google, but can't seem to find what FTFBS stands for. Can someone fill me in?
[22:30] <wardi> fails to build from source
[22:31] <nhandler> wardi: A Debian build log will not work. We need to know that it builds in Ubuntu. If you don't have a Jaunty chroot, you can upload it to your PPA
[22:31] <pochu> mcnicholls: you should try the 'wtf' binary :)
[22:32] <wardi> nhandler: PPA?
[22:32] <nhandler> mcnicholls: https://wiki.ubuntu.com/UbuntuDevelopment/Abbreviations might also help
[22:32] <nhandler> !ppa | wardi
[22:34] <mcnicholls> pochu: hmmm not seen the wtf binary before ;-)
[22:34] <eMerzh> If a MOTU have some time to review my package at http://revu.ubuntuwire.com/details.py?package=sqliteman
[22:34] <mcnicholls> nhandler: cheers thats what i am looking for really
[22:34] <pochu> mcnicholls: it will tell you what acronyms mean :) try $ wtf FTBFS
[22:35] <nhandler> eMerzh: We are past Feature Freeze, the package will most likely not get uploaded until karmic
[22:35] <mcnicholls> i am reading the NBS page on the wiki and it is down as FTFBS which hasn't helped lol
[22:36] <mcnicholls> hmmmm even wtf FTBFS doesn't seem to work
[22:36] <mcnicholls> but i can see it on the Abbreviations page
[22:36] <eMerzh> nhandler: I know... but i want to be sure that nothing block the acceptation again .. it already missed jaunty .... :)
[22:37] <nhandler> eMerzh: Ok, that is fine. But just as a warning, most MOTUs will not be looking at REVU until the karmic repositories open up
[22:38] <eMerzh> nhandler: ok, i'll wait :)
[22:54] <ScottK> fabrice_sp: setools uploaded.  Thank you for your contribution to Ubuntu.
[23:05] <mcnicholls> if i was doing a rebuild to help remove an NBS package, in the example it says add build1 as ubuntu hasn't modified it, but what if ubuntu has all ready modified this package? If it is ubuntu1 do you go for ubuntu2 even if it is just a straight rebuild?
[23:05] <Laney> yep
[23:07] <mcnicholls> ok thanks. also if i want to create a bug to attach the rebuilt debdiff too, i suppose i create that against the source package i am rebuilding? Any particular format to create tat bug with?
[23:07] <Laney> just give it a decent title and description and attach the debdiff
[23:07] <Laney> make sure it closes that bug
[23:10] <mcnicholls> so i am looking at rebuilding libddm-1-0 to build against libempathy22 instead of 19. So in the desktop-data-model source package i just create a bug something like "libddm-1-0 rebuild to remove libempathy19 dependancy" and attach my debdiff?
[23:11] <Laney> yep
[23:11] <mcnicholls> and if i have the LP# in the change log then it will close it on build won't it?
[23:11] <Laney> * rebuild for foo (LP: #xxxxx)
[23:11] <mcnicholls> thats the one
[23:12] <mcnicholls> thanks. thats a lot of questions, but want to get it right as these are the first things i have submitted
[23:13] <Laney> no worries, it's good to ask
[23:14] <mcnicholls> and if i subscribe ubuntu-universe-sponsorship then some should come along and pick it up? or do i need to do more than that?
[23:44] <ryanakca> Could someone take a look at bug 343380 please?
[23:46] <nhandler> ryanakca: I'll take a look
[23:54] <Adri2000> ryanakca: why was the bug confirmed while not acked?