[00:11] <ari-tczew> DktrKranz: ping
[00:45] <paultag> Hey MOTU. I've got a package pending in the NEW queue in Debian. It won't make it in until after Deb freeze. Can I upload to REVU for inclusion in -N ? -- I'm guessing it's not great to request a sync from NEW -- I have a package prepared for Ubuntu, should I upload it or do something else?
[00:59] <DktrKranz> paultag: which one?
[01:10] <paultag> DktrKranz, fbautostart
[01:10] <paultag> DktrKranz, it's lintian clean up to iIE pedantic
[01:11] <paultag> DktrKranz, and I'm also upstream, so no copyright issues :)
[01:11] <paultag> We'd like it for Fluxbox ( which I'm co-maintainer on ) to stop complaints about xdg stuff
[01:14] <DktrKranz> paultag: I'll have a look at it tomorrow
[01:14] <paultag> DktrKranz, cheers, thanks :)
[10:59] <DktrKranz> paultag: fbautostart accepted
[11:37] <ari-tczew> DktrKranz: around?
[11:37] <geser> DktrKranz: re your stepulator.app upload: would it be better to get it removed in Ubuntu too (like you did in Debian)?
[11:38] <ari-tczew> how can I know whether package needs a rdepends rebuild?
[11:39] <geser> e.g. from http://people.canonical.com/~ubuntu-archive/NBS/ or from "apt-cache unmet -i" output
[11:40] <ari-tczew> hmmm, on this site ^^ it might be a lot related to kernel
[11:40] <geser> ignore the kernel ones
[11:41] <geser> and every other file with a size of 0 (those are ready to get removed from the archive)
[11:41] <ari-tczew> ok, but do I have to know before uploading, whether package needs a rebuild rdepends?
[11:41] <ari-tczew> (perhaps answer is yes)
[11:42] <DktrKranz> geser: uh, indeed. I thought packages would have been removed accordingly, so I didn't check
[11:42] <geser> only if you upload a library and it changes the packagename
[11:42] <DktrKranz> ari-tczew: kind of
[11:42] <geser> DktrKranz: it's semi-automatic; an AA needs to run a script to import the removals
[11:43] <ari-tczew> DktrKranz:  I'm just talking with geser about rebuild rdepends ;))
[11:44] <ari-tczew> geser: ok, so if I'm merging package from Debian which include new upstream release (it;s not a lib), rebuilds are not necessary?
[11:45] <geser> usually not
[11:47] <ari-tczew> ok, another question. I've forwarded patch for fix FTBFS (missed linking in LDFLAGS) and maintainer answered, that there is no FTBFS in Debian. how can I explain him, that this is related to our toolchain?
[11:48] <geser> rebuilds are only needed if a package name changed which is used as a dependency (most common case libraries)
[11:57] <geser> ari-tczew: have you tried to mention that he should be able to reproduce it with binutils-gold?
[11:58] <ari-tczew> geser: no, I'm preparing an answer, so I'm asking. well, do I have to tell him, that he should reproduce it with binutils-gold?
[11:59] <geser> I don't have a Debian pbuilder to double-check but using binutils-gold should do it
[12:09] <tumbleweed> ari-tczew: point him at http://wiki.debian.org/ToolChain/DSOLinking
[12:26] <DktrKranz> geser: steptalk needs another rebuild as soon as gnustep-dl2 clears bin-NEW
[13:31] <ari-tczew> stgraber: do you planning merge bcfg2 ?
[13:43] <stgraber> ari-tczew: bcfg2 should be synced from Debian without any Ubuntu change as it's a major version change
[13:43] <stgraber> ari-tczew: I have two patches I'll apply on top of it later on
[13:43] <stgraber> ari-tczew: so if you want to do the sync, feel free
[13:43] <bilalakhtar> ari-tczew: Lucky, stgraber did the whole work for ya, told you directly its a sync
[13:44] <ari-tczew> bilalakhtar: I see.
[13:44] <ari-tczew> stgraber: so, now I'll sync package, then you are going to add 2 patches to synced package?
[13:44] <stgraber> ari-tczew: yep
[13:45] <ari-tczew> bilalakhtar: now we are in the moment, where most of packages require contact with TIL
[13:45] <bilalakhtar> TIL?
[13:45] <ari-tczew> bilalakhtar: Touched In Last. I didn't know this acronym. micahg told me about it.
[13:46] <bilalakhtar> ah
[13:46] <stgraber> upstream bcfg2 is at 1.1.0 and I'll probably want that in the archive beforeNatty is released but I'll probably get it in Debian and request the sync (if after DIF). For now having Debian's 1.0.1 will do the trick.
[13:47] <ari-tczew> ok
[13:47] <ari-tczew> bilalakhtar: look on http://bazaar.launchpad.net/~ubuntu-branches/ubuntu/natty/katoob/natty/revision/9
[13:48] <ari-tczew> inttool* files - what do you think about 3 files inttool* ?
[13:57] <wakandan> hello
[13:57] <ari-tczew> hello wakandan
[13:59] <bilalakhtar> ari-tczew: sorry, I went somewhere, letme look at the branch
[14:01] <wakandan1> hi everybody
[14:01] <wakandan1> I'm trying out IRC channel while reading the meeting log from Ubuntu
[14:01] <bilalakhtar> ari-tczew: hmm, this seems like a new file addition. Does the package run autoreconf or autoconf or any auto* in its rules file?
[14:01] <bilalakhtar> Or, does it have an autogen.sh in the root?
[14:03] <coolbhavi> bilalakhtar, I have added many keys to my gpg keyring public keys but still it shows a import error
[14:03] <bilalakhtar> coolbhavi: Import error when doing what?
[14:03] <ari-tczew> bilalakhtar: I don't think so. You can review files in the branch via this link.
[14:04] <coolbhavi> the keys are not getting recognised
[14:04] <ari-tczew> coolbhavi: could you forward to Debian your FTBFS-fix changes?
[14:04] <coolbhavi> ari-tczew, yes
[14:04] <ari-tczew> nice
[14:05] <ari-tczew> tumbleweed: I tried to run syncpackage for fakesync, but I got error about missing key. what's going on?
[14:05] <coolbhavi> i ve to add something called DSCVERIFY= line in .devscripts
[14:06] <coolbhavi> but m not getting that path I forgot
[14:06] <coolbhavi> :(
[14:06] <ari-tczew> bigon: ping
[14:07] <ari-tczew> wakandan1: how we can help you?
[14:08] <wakandan1> ari-tczew: Uhm I'm following the meeting log
[14:08] <wakandan1> ari-tczew: no question so far
[14:08] <ari-tczew> aha
[14:08] <wakandan1> ari-tczew: but I'm just wondering.....
[14:08] <wakandan1> ari-tczew: Should I do this whole thing?
[14:10] <ari-tczew> wakandan1: could you be more verbosity?
[14:10] <wakandan1> ari-tczew: I always wanted to make contribution to Ubuntu
[14:11] <ari-tczew> wakandan1: nice. we are looking for new contributors.
[14:11] <wakandan1> and I just found how I can proceed
[14:11] <wakandan1> :D
[14:11] <ari-tczew> bilalakhtar: IMO we should get only changes to fix FTBFS and drop the rest.
[14:11] <bilalakhtar> ari-tczew: hmm, yes
[14:11] <wakandan1> ari-tczew: just one thing, my goal is to become a hacker
[14:12] <ari-tczew> wakandan1: oh! I'm scared ;))
[14:12] <wakandan1> ari-tczew: it's just that I like to be it
[14:12] <bigon> ari-tczew: yep?
[14:12] <wakandan1> ari-tczew: so my question is, how would doing this helps me?
[14:12] <ari-tczew> wakandan1: what do you think about fixing security issues then?
[14:13] <wakandan1> ari-tczew: that's would be awesome
[14:13] <ari-tczew> bigon: could you merge libhildon ?
[14:13] <ari-tczew> wakandan1: great! you made my day
[14:13] <wakandan1> ari-tczew: I would love to help
[14:13] <wakandan1> ari-tczew: but in order to do that, I need to have more knowledge on how to package and every thing
[14:14] <ari-tczew> wakandan1: I encourage you to start reading about development Ubuntu.
[14:14] <bilalakhtar> Hmm, while merging I am facing a wierd problem
[14:14] <bilalakhtar> A Package in Debian has no source section
[14:14] <bilalakhtar> And its being rejected from getting into Ubuntu
[14:14] <bigon> ari-tczew: I can have a look at it, but I've no way to test if the merge is fine
[14:14] <wakandan1> ari-tczew: would learning packaging in Ubuntu help me to help out later in fixing security bugs?
[14:15] <ari-tczew> wakandan1: of course. we base on debdiffs or bazaar.
[14:16] <ari-tczew> wakandan1: for security issues we have dedicated channel: #ubuntu-hardened
[14:16] <ari-tczew> wakandan1: let's follow with https://wiki.ubuntu.com/SecurityTeam/UpdatePreparation
[14:17] <wakandan1> ari-tczew: so if I'm right, every developing related contributions must start at learning packaging, so that we can contribute our fixes later?
[14:17] <ari-tczew> wakandan1: I;m a member of motu-swat team, which is like a department of security team.
[14:17] <ari-tczew> and I can drive you through security fixing
[14:17] <wakandan1> ari-tczew: haha yeah it's funny
[14:17] <wakandan1> ari-tczew: my current team's name is also SWAT
[14:18] <wakandan1> I'm working as an intern
[14:18] <ari-tczew> wakandan1: are you a policeman?
[14:18] <wakandan1> ari-tczew: may be in future :P
[14:18] <wakandan1> ari-tczew: I'm just a student lol
[14:19] <ari-tczew> bilalakhtar: which package?
[14:19] <wakandan1> ari-tczew: ok, to confirm, I need to be able to do packaging before anything else, right?
[14:19] <tumbleweed> ari-tczew: I'd need some more details...
[14:20] <ari-tczew> wakandan1: you should be familiar with Ubuntu polices and familiar with basic development tools
[14:20] <ari-tczew> of course you can ask
[14:20] <wakandan1> ari-tczew: I would read first before asking anything :D
[14:20] <ari-tczew> wakandan1: ok, read then https://wiki.ubuntu.com/UbuntuDevelopment
[14:21] <wakandan1> ari-tczew: start off as packaging
[14:22] <wakandan1> ari-tczew: what will be the road map to become a fixer in security team?
[14:22] <ari-tczew> wakandan1: just prepare fixes :)
[14:22] <wakandan1> ari-tczew: haha I know
[14:22] <ari-tczew> show your skill and involvement
[14:23] <ari-tczew> then ask to being a security contributor :)
[14:23] <BlackZ> bilalakhtar: add the section to the source package in debian/control and forward that change to Debian, if there's not a section for the source package soyuz will reject the upload with an error
[14:23] <wakandan1> ari-tczew: is there any special requirements then?
[14:23] <bilalakhtar> BlackZ: Yes, already done
[14:31] <ari-tczew> wakandan1: requirements for?
[14:36] <wakandan1> ari-tczew: haha I don't know
[14:37] <wakandan1> ari-tczew: I should proceed on reading then
[14:38] <ari-tczew> would be nice
[14:53] <Quintasan> hmm, how do I force pbuilder to store a buildlog in ./BUILDLOG?
[14:55] <bdrung> ari-tczew: can you show me the output if you run it with -v?
[14:55] <ari-tczew> bdrung: ekhm... in which case?
[14:56] <bdrung> ari-tczew: syncpackage for fakesync
[14:56] <ari-tczew> Quintasan: --logfile [file to log]
[14:57] <ari-tczew> man pbuilder
[14:57] <bdrung> the question targetted at tumbleweed
[14:57] <ari-tczew> ok w8
[15:01] <ari-tczew> bdrung: http://paste.ubuntu.com/522717/
[15:03] <bdrung> ari-tczew: you may have to specify a key with -k
[15:03] <tumbleweed> yeah, that's my bet
[15:03] <Quintasan> ari-tczew: well, the --logifile option seems to be ignoring me, I get no log file at the end of the build :/
[15:04] <bdrung> and we have to improve the error message
[15:04] <kklimonda_> good morning
[15:04] <bdrung> ari-tczew: can you file a bug for a having a better error message?
[15:05] <ari-tczew> hi kklimonda_, I have to talk with you
[15:05] <kklimonda_> ari-tczew: sure. I have some time before I have to leave my room, do you want to talk now?
[15:05] <kklimonda_> (if not I won't be available until tomorrow evening
[15:06] <ari-tczew> kklimonda_: yes, on PM
[15:06] <kklimonda_> k
[15:32] <ari-tczew> bdrung: bug 668749
[15:32] <Quintasan> kklimonda_: \o
[15:33] <kklimonda_> o/
[15:33] <Quintasan> grr
[15:34] <Quintasan> ari-tczew: sudo DIST=maverick pbuilder --build project-neon-kdebindings_1.0+5537-4.dsc --logfile trolololol  <-- should yield "trololol" upon exit, right?
[15:35] <ari-tczew> Quintasan: try use --logfile before *dsc file
[15:35] <ari-tczew> btw. I suggest to use pbuilder-dist
[15:35] <ari-tczew> instead default pbuilder
[15:36] <Quintasan> I'm too lazy to set it up, I have been using that for ages and it has been working
[15:36] <Quintasan> Slow, but working
[15:37] <ari-tczew> bdrung: http://paste.ubuntu.com/522733/
[15:38] <kklimonda_> Quintasan: you can also add PKGNAME_LOGFILE=yes to your pbuilderrc - then every build will create, alongside deb files, a log file with package's name.
[15:41] <paultag> DktrKranz, thanks a ton! You rock :)
[16:03] <bdrung> ari-tczew: debsign: gpg error occurred!  Aborting....
[16:04] <ari-tczew> bdrung: what it means?
[16:06] <bdrung> ari-tczew: can you run it again with "-v" added?
[16:06] <ari-tczew> bdrung: it was with -v
[16:07] <bdrung> ari-tczew: then show me the complete output of the command
[16:08] <ari-tczew> bdrung: http://paste.ubuntu.com/522750/
[16:08] <kklimonda_> ari-tczew: shouldn't you sign with your own key?
[16:13] <ari-tczew> kklimonda_: /facepalm, yes
[16:19] <bdrung> ari-tczew: according to the log, the signing of the changes file failed => not a syncpackage problem.
[16:20] <ari-tczew> bdrung: yes, but reported bug is related to poor warnings by syncpackage
[16:21] <bdrung> ari-tczew: yes. the warning is poor and that's why i asked you to file the bug.
[16:28] <ari-tczew> bdrung: look on changelog https://launchpad.net/ubuntu/+source/tap-plugins/0.7.1-1fakesync1
[16:28] <ari-tczew> " " is good ?
[16:29] <bdrung> ari-tczew: no, that's a bug too
[16:29] <ari-tczew> bdrung: need a report?
[16:29] <bdrung> yes
[16:32] <Laney> you should double check what you are uploading
[16:32] <ari-tczew> bdrung: I'll die due to reporting bugs
[16:33] <ari-tczew> Laney: fix this bug then you can talk to me
[16:33] <lfaraone> ari-tczew: as the uploader, checking that the package is correct is *your* responsibility.
[16:33] <bdrung> ari-tczew: nope. Laney is right.
[16:34] <bdrung> ari-tczew: syncpackages doesn't upload because the uploader has to check it before uploading the changes
[16:34] <ari-tczew> bdrung, lfaraone, Laney: I checked *.changes file. I was too lazy to update d/changelog. Kill me please.
[16:35] <bdrung> ari-tczew: too lazy is an even worse excuse for it.
[16:36] <ari-tczew> bdrung: relax, we have an example of bug!
[16:42] <ari-tczew> what about debian-changes-* in series file? I'm merging package and I dunno what should do I? drop it or keep?
[16:44] <bdrung> ari-tczew: do you have it in Debian too?
[16:45] <ari-tczew> bdrung: just this file is in Debian.
[16:45] <ari-tczew> I'm adding Ubuntu delta on clean unpacked Debian package.
[16:46] <bdrung> ari-tczew: then keep it. on which package do you work?
[16:46] <ari-tczew> bdrung: katoob
[16:51] <ari-tczew> bdrung: why you ask?
[17:00] <bdrung> ari-tczew: i just wanted to have a look at it
[17:03] <coolbhavi> ari-tczew, I m gonna work on zsh-beta now
[17:04] <coolbhavi> other two katoob n scim-chewing you are free to take :)
[17:14] <ari-tczew> coolbhavi: ok
[17:44] <ari-tczew> coolbhavi: I really encourage to use pbuilder for build testing, not PPA
[17:44] <ari-tczew> again you dropped the delta for fix FTBFS and now we have FTBFS
[17:45] <ari-tczew> we must end this situation
[17:45] <coolbhavi> ari-tczew, I use pbuilder too
[17:45] <coolbhavi> mate
[17:46] <paultag> coolbhavi, be nice :)
[17:46] <ari-tczew> coolbhavi: for natty?
[17:46] <coolbhavi> ari-tczew, yes
[17:46] <ari-tczew> because bilalaktar has been used maverick for natty
[17:47] <ari-tczew> so I don't understand, why pbuilder show you built fine
[17:47] <andreserl> ari-tczew: sometimes it happens
[17:47] <ari-tczew> I never had this situation
[17:48] <andreserl> ari-tczew: i've had long time ago. that's why we usually should test builds in clean pbuilders because that might be a reason why it builds there, and not in archives
[17:49] <coolbhavi> andreserl, right and some time there might be transients too
[17:49] <fabrice_sp> it also happened to me. That's why I switched to sbuild
[17:49] <fabrice_sp> sbuild does not requires lvm anymore, so it may be a good solution
[17:50] <fabrice_sp> to use it
[17:50] <andreserl> coolbhavi: indeed
[17:52] <ari-tczew> coolbhavi: please remember, I don't attack you. I just care about universe quality.
[17:53] <coolbhavi> ari-tczew, sure mate
[17:57] <ari-tczew> bdrung: bug 668805
[17:57] <bdrung> ari-tczew: thanks
[17:58] <ari-tczew> np
[17:59] <bdrung> ari-tczew: sometimes it builds in pbuilder but not on buildd. example: xdotool
[17:59] <ari-tczew> aha
[18:04] <bdrung> ari-tczew: it's better to ask instead of assuming. asking "did you try to build in with pbuilder or sbuild?" instead of complaining "you didn't build it with pbuilder"
[18:05] <coolbhavi> bdrung, in openmpi case it built on pbuilder and my PPA too (since I use both for test building) but failing on official buildds as libtorque2-dev not installed but rmadison shows libtorque2-dev present
[18:06] <bdrung> coolbhavi: did the package build depend on libtorque2-dev?
[18:06] <coolbhavi> bdrung, yes
[18:08] <bdrung> coolbhavi: looking at http://launchpadlibrarian.net/58312312/buildlog_ubuntu-natty-amd64.openmpi_1.4.2-4_FAILEDTOBUILD.txt.gz - it's libtorque2-dev fault
[18:09] <bdrung> just retry the build once the dependency is installable
[18:09] <coolbhavi> yes bdrung but it builds fine on my ppa and pbuilder
[18:10] <paultag> coolbhavi, it might have not been ready for use yet, getting pushed out
[18:10] <bdrung> coolbhavi: it looks like a timing issue
[18:10] <paultag> coolbhavi, it happened to one of my packages off a live build. Totally random
[18:10] <paultag> well, not random, but you know
[18:11] <coolbhavi> bdrung, yes its available as its copied from maverick repos
[18:12] <ari-tczew> bdrung: could you take a look on bug 663343 ?
[18:13] <coolbhavi> ari-tczew, thats also another py 2.7 issue mate until support is fixed its deferred by barry
[18:14] <ari-tczew> so unsubscribe sponsors ?
[18:14] <coolbhavi> ari-tczew, not sure as barry is working on it afaict
[18:15] <ari-tczew> so bug 662276 is outstanding
[18:16]  * ari-tczew is amazed due to how developers work on merges this cycle!
[18:16] <andreserl> ari-tczew: yes unsubscribe it from u-s with a message "Once this is fixed, please re-subscribe"
[18:16] <Laney> what's the problem with vim?
[18:17] <geser> ari-tczew: cjwatson will sponsor it once he is back from UDS
[18:17] <bdrung> coolbhavi: i found the issue: torque is in multiverse
[18:18] <ari-tczew> Laney: who said that there is problem?
[18:18] <coolbhavi> bdrung, so what are next steps?
[18:19] <Laney> :)
[18:21] <bdrung> coolbhavi: check the license if it suitable for universe. if yes, file a bug for moving it to universe
[18:22] <coolbhavi> bdrung, but the same thing built fine in maverick when I backported a patch
[18:22] <coolbhavi> to fix ftbfs
[18:23] <bdrung> coolbhavi: where did it build? in the PPA multiverse is enabled
[18:23] <coolbhavi> I ll link the log a second
[18:24] <coolbhavi> bdrung, https://launchpad.net/ubuntu/+source/openmpi/1.4.1-3ubuntu1/+build/1981045/+files/buildlog_ubuntu-maverick-i386.openmpi_1.4.1-3ubuntu1_BUILDING.txt.gz
[18:25] <coolbhavi> this is on official buildd
[18:25] <coolbhavi> on maverick
[18:25] <bdrung> hm, strange
[18:26] <bdrung> coolbhavi: ok. this version didn't depend on torque
[18:28] <coolbhavi> bdrung, okay I got the catch now
[18:28] <coolbhavi> thanks
[18:29] <coolbhavi> universe packages on official buildds doesnt depend on multiverse
[18:29] <bdrung> yes main -> main; restricted -> main, restricted; universe -> main, universe; multiverse -> all
[18:30] <geser> figure out why the package is in multiverse (it's in Debian main)
[18:32] <coolbhavi> yes I ll have a mail to morten and clarify shortly thanks
[18:32] <bdrung> geser: it has a special license
[18:35] <geser> bdrung: which part of the license make it go to multiverse?
[18:36] <bdrung> geser: dunno - i just skim-read debian/copyright
[18:36] <bdrung> it may contain problematic parts
[18:37] <geser> me too, but as it's in Debian main, it could also make it to universe
[18:37] <geser> the only problematic parts that I see have expired
[18:37] <bdrung> geser: expired?
[18:37] <geser> a good idea would be to let the AA check the copyright file again and move it to universe if possible
[18:39] <geser> bdrung: http://packages.debian.org/changelogs/pool/main/t/torque/current/copyright ; paragraphs 1 and 2 from the license look like non-free but the don't apply since 2002-01-01 anymore
[18:40] <bdrung> geser: ok. that seems fine
[18:41] <coolbhavi> bdrung, geser so shall I open a bug?
[18:41] <bdrung> coolbhavi: yes
[18:51] <coolbhavi> bdrung, can I include this irc bit as a support?
[18:51] <bdrung> coolbhavi: yes, but stating that it's in Debian main is the best support
[18:51] <ari-tczew> debian-changes-0.5.9.1-1.2 don't allow me apply patch from Ubuntu. bdrung, is it file necessary?
[18:52] <coolbhavi> bdrung, sure thanks
[18:53] <bdrung> ari-tczew: really?
[18:53] <bdrung> ari-tczew: this file contains the debian changes. you may have to update the ubuntu changes
[18:54] <ari-tczew> bdrung: I tried to this way: create seperate directory, put files there, apply patch debian-changes*, then apply patch from Ubuntu
[18:54] <ari-tczew> but there is a lot of warnings :/
[18:54] <bdrung> ari-tczew: use quilt
[18:55] <bdrung> ari-tczew: lot of warnings are caused by the patch because it contains many changes (including build system changes)
[19:09] <bdrung> coolbhavi: have you opened a bug?
[19:09] <coolbhavi> bdrung, doing it now just 2 minutes please
[19:11] <ari-tczew> bdrung: yay, quilt pop -a fixed problem
[19:12] <bdrung> ari-tczew: but quilt push -a will unfix it ;)
[19:13] <ari-tczew> bdrung: but now I got built source and good looking debdiff. what's the conclusion?>
[19:14] <bdrung> ari-tczew: hm
[19:16] <coolbhavi> bdrung, https://bugs.launchpad.net/ubuntu/+source/torque/+bug/668830
[19:17] <ari-tczew> bdrung: http://paste.ubuntu.com/522856/ commands used
[19:17] <bdrung> "quilt refresh" was the trick
[19:17] <coolbhavi> bdrung, edited a small typo now
[19:17] <coolbhavi>  https://bugs.launchpad.net/ubuntu/+source/torque/+bug/668830
[19:18] <coolbhavi> please have your comments
[19:19] <bdrung> coolbhavi: i subscribed ubuntu-archive
[19:19] <coolbhavi> bdrung, thanks
[19:25] <ari-tczew> coolbhavi: let's keep under 75-80 till 1th Nov (ATM is 84)
[19:26] <coolbhavi> ari-tczew, sure!
[19:26] <ari-tczew> going out, thanks
[20:36] <tumbleweed> bdrung: busy evening? :) BTW your fix for bug 665202 doesn't address DEBEMAIL="name name <email@domain>" does it?
[21:03] <bdrung> tumbleweed: no. that is another issue.
[21:03] <tumbleweed> it's probably an issue that affects more scripts than syncpackage, anyway
[21:04] <bdrung> tumbleweed: is DEBEMAIL meant to used that way?
[21:04] <tumbleweed> bdrung: I don't know, but apparently people do that...
[21:05] <tumbleweed> at some point ubuntu-dev-tools is going to have to get a configuration file
[21:05] <bdrung> tumbleweed: configuration file for what?
[21:06] <tumbleweed> yeah, unrelated issue, this just made me think of it. Things like using pbuilder / sbuild for test building
[21:06] <tumbleweed> also, I'd like to add an option to specify a local mirror for pull-{lp,debian}-source
[21:06] <bdrung> tumbleweed: for that we could have an environment variable in addition to programm parameter
[21:07] <ebroder> tumbleweed: ++ on the local mirror thing
[21:07] <bdrung> tumbleweed: can you code in pearl?
[21:07] <tumbleweed> bdrung: no, I've tried to avoid that for years :)
[21:07] <tumbleweed> but I can patch perl :P
[21:08] <bdrung> i need someone helping me porting a script from python to pearl
[21:10] <tumbleweed> yeah, sorry I'm no help there. Adding something to devscripts?
[21:13] <bdrung> tumbleweed: yes
[21:50] <paissad> hello all, i would like to know if it's possible to do a request for packaging for some software and/or libraries ?
[21:51] <paissad> there are some Java libraries i would like to have them available in official repositories :)
[21:51] <iulian> It is possible.
[21:52] <paissad> happy to know that ;)
[21:52] <iulian> paissad: https://wiki.ubuntu.com/UbuntuDevelopment/NewPackages.
[21:53] <iulian> You might want to give the above link a try.
[21:54] <paissad> ok
[21:54] <iulian> Oh, and just for your information, there is also a Debian Java team as well.
[21:55] <iulian> It's not on that list but if you click on "more" you end up with http://wiki.debian.org/Teams/JavaPackaging
[21:55] <iulian> Or "here".