[07:54] <Rhonda> ScottK: Who is Danilo?
[08:16] <chilicuil> hi, good afternoon, when dealing with bzr branches and quilt, should I remove the patches pile before using debcommit?
[08:26] <chilicuil> I've added a new patch to a pkg using quilt and then I've used debcommit (leaving the changes), when I run $ bzr bd -- -S -uc -us, I get the following error: "dpkg-source: error: cannot read xsane-0.997.orig.oG0rqG/debian/patches/fix_umask_permitions.patch: No such file or directory", that patch is the one I made, what I'm doing wrong?, is this the correct channel?, or should I ask in another one?
[08:33] <tumbleweed> did you bzr add that patch?
[08:34] <chilicuil> tumbleweed: not afaik
[08:36] <chilicuil> tumbleweed: ok, that made the trick, thx, and sry to bother u
[08:51] <tumbleweed> chilicuil: np
[10:36] <ScottK> Rhonda: No idea.
[10:36] <ScottK> Just odd that anyone not you is editing your page.
[11:59] <AnAnt> what's the difference between base.cow & base.tgz ? I mean
[11:59] <AnAnt> I mean, will creation of a base.cow will download packages again, if I already have a base.tgz ?
[12:01] <AnAnt> bilalakhtar: welcome back
[12:01] <AnAnt> does 616685 need FFe ?
[12:02] <AnAnt> ^ LP #616685
[12:02] <bilalakhtar> AnAnt: I don't think so
[12:03] <bilalakhtar> AnAnt: no feature is being added
[12:03] <ari-tczew> AnAnt, bilalakhtar: if this upload will fix any bug, it doesn't need FFe
[12:03] <Laney> no
[12:03] <Laney> if the upload does not introduce any new features, that's the test
[12:03] <bilalakhtar> ari-tczew and Laney: The only changes being incorporated are that an extra configure option is being added
[12:04] <bilalakhtar> and Standards-Version is being bumped
[12:04] <bilalakhtar> no need for FFe
[12:04] <Laney> bilalakhtar: It'd be nice if you pasted the entire new changelog into the bug
[12:04] <Laney> oh, sorry, AnAnt
[12:04] <bilalakhtar> Laney: I filed the merge
[12:04] <Laney> well, whoever :P
[12:04] <ari-tczew> bilalakhtar: upstream changelog
[12:05] <Laney> if it's a new upstream release then that too indeed
[12:05] <bilalakhtar> ari-tczew: Why?
[12:05] <bilalakhtar> ari-tczew: Its not a new upstream release
[12:06] <bilalakhtar> Laney: ^^
[12:06] <Laney> I know.
[12:06] <Laney> put in what's appropriate and sensible basically
[12:06] <bilalakhtar> The problem is
[12:07] <bilalakhtar> The current Ubuntu package installes files in /var/www
[12:07] <ari-tczew> if merge doesn't include new upstream, you don't need include upstream changelog :)
[12:07] <bilalakhtar> Laney: ^^
[12:07] <bilalakhtar> ari-tczew: We never include upstream changelog
[12:08] <Laney> If you want the sponsors to be able to easily confirm that it doesn't need a FFe then include as much detail as you can
[12:08] <ari-tczew> bilalakhtar: ehh, listen: if you want to upload a merge and this package includes new usptream release, then in bug you have to paste an upstream changelog
[12:08] <ari-tczew> during FFe of course
[12:08] <bilalakhtar> ari-tczew: But not in debian/changelog, right? That's what I meant
[12:09] <AnAnt> bilalakhtar: ?
[12:09] <bilalakhtar> AnAnt: ??
[12:09] <bilalakhtar> fta: You have been disconnecting every now and then
[12:09] <ari-tczew> bilalakhtar: yea, most upstream changelog is in file called ChangeLog
[12:09] <ari-tczew> or NEWS
[12:09] <Laney> in the bug
[12:09] <AnAnt> bilalakhtar: I think that you would have to put the changelog entry of -3
[12:09] <fta> bilalakhtar, i know. it sucks. that's my adsl link flapping
[12:10] <bilalakhtar> fta: I have also faced a problem like yours
[12:10] <bilalakhtar> AnAnt: Why?
[12:11] <AnAnt> bilalakhtar: in case the debian packaging introduced a new feature for example, you said something about adding an extra config option
[12:11] <bilalakhtar> config option? ^^
[12:11] <AnAnt> AFAIK, Debian is considered upstream for Ubuntu
[12:11] <bilalakhtar> AnAnt: yes
[12:11] <Laney> It's just nice for the sponsors
[12:11] <bilalakhtar> Debian is upstream for us
[12:11] <Laney> to be able to see what changes you are making
[12:11] <bilalakhtar> AnAnt: But FF blocks UP-Upstream updates
[12:11] <Laney> no
[12:11] <fta> bilalakhtar, started a few weeks ago, but nothing's wrong on my side. it's somewhere in the network but tricky to isolate
[12:34] <ari-tczew> bilalakhtar: I encourage you to fix RC bugs
[12:34] <ari-tczew> you can fix rc bug by sync/merge
[12:34] <bilalakhtar> ari-tczew: rc bugs?
[12:34] <ari-tczew> just you need to test if it works
[12:34] <bilalakhtar> What's that?
[12:35] <ari-tczew> bilalakhtar: http://qa.ubuntuwire.com/bugs/rcbugs/maverick/
[12:36] <bilalakhtar> fta_: again? :( I understand
[12:36] <fta_> bilalakhtar, yep, 20~30 times a day :(
[13:14] <LucidFox> Is there a specific team responsible for maintaining Wine in Ubuntu?
[13:14] <LucidFox> I'm in favor of including the winepulse patches into the Ubuntu build of Wine, but I feel like uploading them right away would be steamrolling.
[13:15] <geser> LucidFox: if things didn't change then YokoZar is taking care of wine in Ubuntu
[13:16] <YokoZar> LucidFox: the "Wine Team" is me
[13:16] <LucidFox> YokoZar> Ah, good
[13:16] <YokoZar> LucidFox: And I'm watching the pulse situation pretty closely
[13:17] <YokoZar> For openal-based games Wine 1.2 actually uses native OpenAL now (next step is to expand mmdevapi.dll to use openAL for other programs)
[13:17] <LucidFox> Well, I know they're going to implement a New and Improved sound architecture in some distant release, but until then, I have long been running the vivnet PPA builds with the winepulse patches
[13:32] <LucidFox> YokoZar> Why does Wine try to build on multiple architectures? Wouldn't Architecture: amd64, i386 make more sense?
[13:33] <LucidFox> it fails to build on any other one anyway
[13:37] <shadeslayer> YokoZar: poke
[13:38] <shadeslayer> do you know about software-properties package ?
[13:38] <shadeslayer> like the internal workings and stuff
[13:39] <shadeslayer> bah.. not here
[13:40] <shadeslayer> YokoZar: software-properties-kde is broken, it cant "Select Best Server" , backtrace here : http://pastebin.com/Jns8SW7X, will try and fix
[13:40] <shadeslayer> if the new package doesnt fix it already
[13:41] <YokoZar> shadeslayer: no
[13:41] <YokoZar> shadeslayer: I want to know more about it eventually though
[13:41] <shadeslayer> ok... well ill wait for mvo then
[13:42] <shadeslayer> and try to fix with no idea of python internals :p
[15:34] <bdrung> chilicui1: around?
[15:34] <chilicui1> bdrung: yep
[15:35] <bdrung> chilicui1: regarding bug #462193. i recommend to use the full name in the changelog stanza and not the nick name.
[15:35] <bdrung> "-- chilicuil <chilicuil@i.am>  Thu, 12 Aug 2010 17:02:53 -0500"
[15:38] <chilicui1> bdrung: ok, I'll do it next time, thx for the comment
[15:39] <bdrung> chilicui1: can you update the debdiff or give me your real name (then i can fix it)?
[15:40] <chilicui1> bdrung: sure, it's "Javier Perez Lopez"
[15:50] <bdrung> chilicui1: uploaded
[15:50] <chilicui1> bdrung: thx =)
[15:50] <bdrung> yw
[15:58] <bdrung> chilicui1: you might want to add your realname to https://launchpad.net/~chilicuil
[15:59] <chilicui1> bdrung: oki doki
[16:53] <AnAnt> Hello, is removing an un-necessary package from Depends , something that requires a FFe ?
[16:56] <geser> no
[16:57] <AnAnt> so I can immediately upload the package ?
[16:57] <geser> FF is to stop "adding features" and to concentrate on to fix/stabilise the existing ones
[16:58] <geser> sure
[16:58] <AnAnt> ok
[17:09] <AnAnt> hmm, I am using syncpackage to sync zekr from experimental. Currently maverick has the -0ubuntu1 revision, and I am syncing -1, now why is the source.changes having the orig tarball ?
[17:10] <Laney> just use requestsync ;)
[17:11] <AnAnt> Laney: and ?
[17:11] <bdrung> AnAnt: maybe a bug?
[17:11] <Laney> it does rather sound like a bug
[17:11] <AnAnt> bdrung: well, syncpackage gives those messages:
[17:11] <AnAnt> syncpackage: Warning: Overwriting modified Ubuntu version 1.0.0+repack-0ubuntu1, setting current version to 1.0.0+repack-0
[17:11] <AnAnt> parsechangelog/debian: warning: 'since' option specifies non-existing version
[17:11] <AnAnt> parsechangelog/debian: warning: use newest entry that is smaller than the one specified
[17:13] <bdrung> syncpackage: D: needs source tarball: False
[17:16] <AnAnt> bdrung: yup, I get that with verbose option
[17:17] <bdrung> AnAnt: ok, found it. i will fix it
[17:18] <AnAnt> bdrung: line 276 ?
[17:18] <bdrung> line 281
[17:19] <AnAnt> you want to add if ! need_orig ?
[17:19] <AnAnt> or just else:
[17:21] <bdrung> AnAnt: pushed
[17:21] <bdrung> to lp:ubuntu-dev-tools
[17:21] <AnAnt> bdrung: thanks, I manually fixed it here
[17:22] <bdrung> AnAnt: you're welcome.
[18:10] <Rhonda> ScottK: Didn't you edit it, too? :P
[21:08] <jenkins> I am trying to write a debian rules file for a project I am working on. I do not have any questions yet but which channel would be best to ask questions in?
[21:09] <geser> #ubuntu-packaging
[21:10] <jenkins> thanks geser
[23:41] <shadeslayer> bug 603831 if anyone is interested
[23:50] <geser> shadeslayer: as this a new upstream version (sort of), have you checked if any new features got added?
[23:50] <shadeslayer> err...no, ill do that right now
[23:51] <shadeslayer> i guess ill need a FFe  if that is true
[23:51] <geser> yes
[23:53] <shadeslayer> http://pastebin.com/yUqajX7j
[23:53] <shadeslayer> thats the NEWS file
[23:53] <shadeslayer> nothing new there
[23:56] <geser> and in the git commit log also nothing that would qualify as new feature
[23:57] <geser> so looks like you got lucky not needing a FFe :)
[23:58] <shadeslayer> ^_^