[02:51] <Jazzva> Can a bug have both mt-needtestcase and mt-needtester tags?
[02:54] <gnomefreak> Jazzva: testcase forst
[02:54] <gnomefreak> first
[02:54] <gnomefreak> to make our life easier
[02:55] <Jazzva> gnomefreak: Hmm... Well, I came across a bug that is tagged with both tags. That's why I asked :/...
[02:55] <Jazzva> bug 41294
[02:55] <ubotu> Launchpad bug 41294 in firefox "Monospace fonts are displayed as proportional" [Medium,Incomplete]  https://launchpad.net/bugs/41294
[02:55] <gnomefreak> Jazzva: ill look
[02:55] <Jazzva> Ok :)...
[02:58] <gnomefreak> done
[03:04] <Jazzva> Coll...
[03:04] <Jazzva> *Cool
[03:09] <gnomefreak> ok set firefox a7 to build ill look at it in morning if it fails, im out for the night
[03:10] <Jazzva> Have fun...
[03:10] <gnomefreak> you too
[03:11] <Jazzva> Will try :)...
[03:11] <Jazzva> *edit: Will try (to catch some sleep) :)...
[04:37] <gnomefreak> update: looks like firefox-trunk will work out if so i will spin granparadiso as well and give to asac for upload
[05:14] <Jazzva> gnomefreak: What's granparadiso?
[05:19] <Jazzva> If someone could take a look at bug 107261. It's a known bug upstream, said that it'll be fixed in FF3, but still has a mt-needtester tag. I think it should be tagged with mt-confirm, but I'm not sure (a beginner :)).
[05:19] <ubotu> Launchpad bug 107261 in firefox "Hebrew Vowels Incorrectly Placed in Firefox" [Medium,In progress]  https://launchpad.net/bugs/107261
[05:49] <Jazzva> Off to sleep...
[05:52] <Admiral_Chicago> Jazzva: firefox 3 while in development
[11:12] <gnomefreak> asac: trunk almost builds :)
[11:13] <gnomefreak> so close i can taste it :(
[11:24] <gnomefreak> something is wrong with this. how in the hell is debian/tmp empty
[11:30] <gnomefreak> son of a bitch that where i saw that error before
[11:36] <gnomefreak> i cant see what we did to fix that error
[01:56] <Jazzva> Thanks Admiral_Chicago :)
[02:21] <gnomefreak> ok this is getting weird now :(
[02:21] <Jazzva> The building?
[02:21] <gnomefreak> yes
[02:21] <gnomefreak> upstream had to of changed something im not seeing
[02:21] <gnomefreak> gonna rebuild to see if a fluke
[02:22] <gnomefreak> with 20070804 build
[02:22] <Jazzva> Good luck...
[02:22] <gnomefreak> ty
[02:22] <gnomefreak> asac: sorry wanted this ready for upload for when you got home for monday but i doubt it
[06:07] <asac> ok i am more or less avail :)
[06:08] <Jazzva> Welcome back...
[06:08] <hjmf> hi
[06:08] <Jazzva> asac: I have a few questions... I'll be back in a minute...
[06:08] <asac> sure
[06:08] <asac> ... but remember that i am more or less in minor mode today ;)
[06:13] <Jazzva> It's ok, just 2 or 3 minor bug questions :)
[06:14] <hjmf> I have one quick question too :); in the retrace of bug #129415 there really are garbage characters or do I have a problem with locales or somewhat?
[06:14] <ubotu> Bug 129415 on http://launchpad.net/bugs/129415 is private
[06:15] <hjmf> I cannot read first stacks of the stacktrace
[06:15] <hjmf> the same when I retrace here at home
[06:18] <Jazzva> asac: Well, here are my questions, take a look when you have time :)...
[06:19] <Jazzva> Bug 107261: Marked as In Progress, like upstream, but still has mt-needtester tag. I wasn't sure if retagging with mt-confirm is the right thing...
[06:19] <ubotu> Launchpad bug 107261 in firefox "Hebrew Vowels Incorrectly Placed in Firefox" [Medium,In progress]  https://launchpad.net/bugs/107261
[06:20] <hjmf> I'll be back in half an hour or so
[06:21] <Jazzva> Bug 81543: I think I found out why the Preferences get truncated (left in comments). And I think it's confirmed... but again, wasn't sure if I should retag it with mt-confirm.
[06:21] <ubotu> Launchpad bug 81543 in firefox "Firefox child windows width too small (german version)" [Medium,Incomplete]  https://launchpad.net/bugs/81543
[06:21] <Jazzva> It might be an upstream bug :/
[06:22] <Jazzva> And bug 72812: Has both mt-needtester and mt-needtestcase. Isn't that wrong *unsure*?
[06:22] <ubotu> Launchpad bug 72812 in firefox "Firefox does not display new page after click." [Medium,Incomplete]  https://launchpad.net/bugs/72812
[06:22] <asac> Jazzva: you can always tagg mt-confirm if you want feedback from me
[06:22] <asac> e.g. mt-confirm is ment to be a staging tag you should set if you think you are done with current state but are not yet sure
[06:22] <Jazzva> Oh... Ok.
[06:23] <asac> In Progress ... though doesn't have any tags atm
[06:23] <asac> so feel free to remove any tag you find at that stage
[06:23] <asac> its in fact a "triaging bug" if "In Progress" bugs have a tag at all
[06:23] <asac> e.g 107261 is on track in upstream bug
[06:24] <asac> so its usually more or less done from ubuntu point of view... which is why its "In Progress"
[06:24] <asac> bug 107261
[06:24] <ubotu> Launchpad bug 107261 in firefox "Hebrew Vowels Incorrectly Placed in Firefox" [Medium,In progress]  https://launchpad.net/bugs/107261
[06:24] <Jazzva> Mhm, but shouldn't it be untagged if it's in progress?
[06:24] <asac> yeah
[06:25] <asac> definitly
[06:25] <asac> its like i call it a "triaging bug"
[06:25] <Jazzva> And tagged with mt-confirm?
[06:25] <asac> no "in progress" has no tags at all
[06:25] <asac> so just remove it
[06:25] <asac> http://daniel.holba.ch/bugs/
[06:25] <Jazzva> What's the "triaging" part of that bug? :)
[06:26] <asac> Jazzva: well its done :)
[06:26] <asac> Jazzva: its been submitted upstreawm ... upstream has someone assigned to it
[06:26] <asac> so from ubuntu its just "look and see that upstream makes progress"
[06:26] <asac> of course ... anybody can take a look and see if he can help upstream fixing this
[06:26] <Jazzva> Oh, ok... I thought there is maybe something else to be triaged about it :)...
[06:27] <asac> the page above is a bughelper result ... among other things it tries to list bugs that have bad tag/state combinations
[06:27] <asac> some false-positives, are in that list though
[06:27] <asac> Jazzva: no ... not for that bug ... its in progress in that upstream deals with it
[06:28] <Jazzva> bughelper results... I think I read about it somewhere, though I completly forgot... :)
[06:28] <Jazzva> Aaaah... firefox.html looks nice :).
[06:28] <asac> Jazzva: yeah ... bughelper allows you to do multiple things
[06:29] <asac> we maintain a firefox clue file ... but Admiral_Chicago can tell you more about that
[06:29] <asac> main purpose is auto-detection of duplicates + detecting bugs that are not properly tagged ... as that often indicates that some user or unexperienced triager did something ... which is often enough wrong
[06:30] <Jazzva> I see...
[06:30] <Jazzva> And that clue file is firefox.html?
[06:31] <asac> no the clue file is a rule file for bughelper ... which produces firefox.html as a result
[06:31] <asac> basically you can match things ... and print infos for bugs that match some conditions
[06:32] <asac> but ask Admiral_Chicago about that ;) ... he is bughelper guru
[06:32] <Jazzva> Ok, when he gets back...
[06:32] <asac> Jazzva: usually firefox.html just gives you a list of bugs that need some attention
[06:32] <asac> thats all you need to know as a triager too start with :)
[06:32] <Jazzva> That's what I wanted to say :)...
[06:34] <Jazzva> asac: Two more questions :)...
[06:35] <Jazzva> Aren't mt-needtester and mt-needtestcase in XOR relation?
[06:35] <Jazzva> As in there can be only mt-needtester or mt-needtestcase, but not both...
[06:36] <asac> well ... usually yes
[06:37] <asac> but practically it might be that you want people to test an existing testcase, while you still search for a more reproducible one
[06:37] <Jazzva> Ok...
[06:37] <asac> but yes ... bugs that have both might need to be worked on
[06:37] <asac> at least they are worth a look
[06:37] <asac> e.g. is there a step by step testcase in summary?
[06:38] <asac> has this testcase already been verified to "not reproduce it" ... et al
[06:38] <Jazzva> I see... I'll take a look.\
[06:40] <Jazzva> asac: And about bzr... I read the wiki, tried out pulling the sources, everything went well :). I read about pushing, still didn't try it out.
[06:40] <Jazzva> So, you want me to send the packages I prepare to bazaar?
[06:44] <asac> Jazzva: yes
[06:44] <asac> please
[06:44] <asac> its pretty good to review et al
[06:44] <Jazzva> Hmm, ok...
[06:46] <Jazzva> I finished packaging gnome-voice-control last night and uploaded to REVU... Wasn't sure about bzr, but I'll upload it now. So, the address would be sftp://jazzva@bazzar.launchpad.net/~jazzva/gnome-voice-control/<branchname>?
[06:46] <Jazzva> asac: And what's the right branchname?
[06:48] <asac> Jazzva: yes ... you have to register a project for gnome-voice-control
[06:48] <asac> then you can push it
[06:48] <Jazzva> Mhm... And I should push only source?
[06:48] <asac> if you push with debian/ directory we usually call branchname: "debian" ... or "ubuntu"
[06:48] <asac> if its just plain upstream sources then its "upstream"
[06:49] <Jazzva> Ok... thanks :)
[06:49] <Jazzva> Should I report to you once I'm done?
[06:49] <asac> Jazzva: yes always only sources please
[06:49] <asac> never push binaries ;)
[06:49] <asac> Jazzva: sure
[06:49] <asac> just tell me the branchname you want to get reviewed
[06:49] <Jazzva> Ok :).
[06:49] <asac> at best send a mail
[06:50] <asac> so in case i don't have time right away, I won't forget it
[06:50] <asac> :)
[06:50] <Jazzva> Understood :D.
[06:50] <asac> but usually i should be able to do a look within a few hours
[06:50] <asac> initial upload might be different, because check needs to be more thoroug
[06:50] <asac> h
[06:50] <Jazzva> Mail it is :).
[07:07] <Jazzva> asac: Here is the link: https://code.launchpad.net/~jazzva/gnome-voice-control/ubuntu
[07:07] <Jazzva> Will send a mail too... :)
[07:12] <asac> Jazzva: its pretty important that you have an upstream branch as well
[07:12] <Jazzva> asac: BTW, how can I set the name and e-mail for Bzr?
[07:13] <Jazzva> asac: Uh-huh... I'll upload it now :)
[07:13] <asac> and since it won't help you when merging new upstream releases
[07:13] <asac> you have to take care
[07:13] <asac> that your ubuntu branch is initially branched from that upstream branch
[07:13] <asac> which you didn't do
[07:13] <asac> (i guess
[07:13] <asac> )
[07:13] <asac> so ... start with the upstream branch
[07:14] <asac> add the debian directory in another commit
[07:14] <asac> and push that buranch to <ubuntu> again
[07:14] <Jazzva> You mean, to upload the upstream branch, then download that one, put in debian and upload as ubuntu or debian?
[07:14] <asac> yes
[07:14] <Jazzva> Ok
[07:14] <asac> its important that both branches have the same root
[07:14] <asac> otherwise you cannot really merge later
[07:14] <asac> you can use --overwrite on push ... to overwrite your current ubuntu branch
[07:15] <Jazzva> Cool :)
[07:15] <asac> if you have both branches up (upstream + ubuntu) let me know :)
[07:15] <Jazzva> Ok
[07:15] <Jazzva> And how can I set e-mail and name?
[07:15] <Jazzva> Currently it's "Sasa <sasa@SID>"
[07:17] <asac> wait a sec
[07:17] <asac> read man bzr
[07:17] <asac> its on bottom i guess
[07:17] <Jazzva> Ok
[07:17] <asac> you have to set env variables
[07:17] <asac> BZR_EMAIL it is
[07:17] <Jazzva> Ok, thanks :)...
[07:18] <asac> but it uses EMAIL alone if the BZR_ is not set
[07:18] <asac> interesting is that i don't have any set, but it works for me :)
[07:18] <Jazzva> Lucky you :)
[07:19] <asac> i think it needs to be name + email in that env
[07:19] <Jazzva> bzr whoami
[07:19] <Jazzva> :)
[07:19] <asac> e.g. EMAIL="Alexander Sack <asac@jwsdot.com>"
[07:19] <Jazzva> To show or set user id :D
[07:20] <asac> yeah you can set the id as well
[07:20] <asac> with bzr config i guess
[07:20] <asac> agh
[07:20] <asac> now i see :)
[07:20] <asac> in ~/.bazaar/bazaar.conf
[07:20] <asac> i have
[07:20] <asac> [DEFAULT] 
[07:20] <asac> email = Alexander Sack <asac@jwsdot.com>
[07:20] <Jazzva> I was looking for that, but there wasn't one in .bazaar *sighs*... Maybe because I still didn't run bzr config or something *doh*...
[07:21] <asac> yeah .. try bzr config :)
[07:21] <Jazzva> Doesn't work... bzr whoami 'name <mail>'
[07:21] <Jazzva> :)
[07:23] <asac> well ... i think you will figure out :)
[07:23] <asac> if nothing works, you can use env variable :)
[07:23] <Jazzva> This one is working :)
[07:23] <Jazzva> ...at least, for now
[07:24] <asac> hehe
[07:33] <asac> ok out for a while ... dinner et al
[07:42] <Jazzva> asac: Uploaded both upstream and ubuntu :).
[07:42] <Jazzva> Out for a dinner and a bit of studying... see you later.
[07:49] <asac> sure ... will look later
[08:21] <Jazzva> asac: Thanks :)...
[08:23] <Jazzva> BTW, I just tried granparadiso-alpha7 now... It seems a lot faster then FF2. Gmail's interface can cause FF2 stop responding for a few seconds. On gp nothing :D... It's all smoother.
[08:23] <Jazzva> Well, back to studying...
[09:40] <Admiral_Chicago> Jazzva: i can tell you about bughelper later, I'm fairly busy today
[10:54] <Jazzva> Back
[10:55] <Jazzva> Admiral_Chicago: Thanks, I'll see what can I find on Bughelper and to get prepared :).
[11:06] <asac> yeah ... we should try to get paradiso 7 packaged ... last trunk builds crashed for us though
[11:12] <Jazzva> asac: Packed for Gutsy?
[11:13] <Jazzva> Well, it crashed once for now... On Demonoid.
[11:23] <asac> Jazzva: hey
[11:23] <asac> one question: why do you build-depend on gnome-devel?
[11:24] <asac> can you try to do it more fine grained?
[11:24] <asac> PKG_CHECK_MODULES(GNOME_PANEL, libpanelapplet-2.0 gtk+-2.0 libgnomeui-2.0 gstreamer-0.10 gstreamer-base-0.10 gdk-2.0 libwnck-1.0 cspi-1.0)
[11:24] <Jazzva> Hmm, I think it's reported in INSTALL...
[11:24] <asac> thats what i see in configure.ac
[11:24] <asac> i guess adding the -dev packages from those should be good enoug
[11:24] <Jazzva> Ok, I'll try that and see if it builds
[11:24] <asac> should
[11:25] <asac> otherwise ad those missing
[11:25] <Jazzva> Didn't know for that :)...
[11:25] <asac> using gnoma-devel doesn't sound right ;)
[11:25] <asac> Note: those meta -devel packages are not ment for package dependencies
[11:25] <asac> its for developers that want to do arbitrary gnome development
[11:25] <asac> at least thats what used to know ;)
[11:26] <asac> if it build please push update to bzr
[11:26] <Jazzva> used to know?
[11:26] <Jazzva> Well, I'll give it a try in a minute (waiting for computer to finish something)...
[11:29] <asac> sure
[11:32] <Jazzva> asac: Just to edit files in the directory I pulled from bazzar? (the one where I put debian/)
[11:35] <asac> yes
[11:35] <asac> you can edit there
[11:35] <asac> then commit changes
[11:35] <asac> if you are happy with your commits you can push again
[11:36] <Jazzva> Ok
[11:36] <asac> but please take the habbit to have nice per-feature checkins
[11:36] <Jazzva> per-feature checkins?
[11:36] <asac> e.g. commit locally ... reorganize your branch locally before you push :)
[11:36] <asac> not that important :)
[11:36] <asac> its just to prevent micro-checkins
[11:36] <asac> which make it hard to track back regressions
[11:37] <asac> its not important :) .... but i take every oppertunity to talk this in to people :=
[11:37] <Jazzva> Umm... I don't think I understand you :)...
[11:37] <Jazzva> Well, I'm listening :)... But just don't get the meaning of "micro-checkin"
[11:37] <asac> well ... most people use  cvs et al just to get versioned backups
[11:37] <asac> so they checkin whatever they have at some point
[11:37] <asac> sometimes they just checkin a bunch of unrelated things from top level
[11:38] <asac> et al
[11:38] <asac> sometimes they check in test revisions as a kind of checkpoint
[11:38] <asac> since you don't commit directly to online repository you have the chance to reorganize your checkins so they are clean
[11:38] <asac> with bzr
[11:38] <asac> you see what i mean?
[11:38] <Jazzva> Mhm :)
[11:39] <Jazzva> So, to check everything I can before pushing, and not to upload for every little change...
[11:39] <Jazzva> Right?
[11:39] <asac> hmm
[11:39] <asac> no idea
[11:39] <asac> just use it
[11:40] <Jazzva> lol...
[11:40] <asac> if i see a pattern which i put into one of those two types I will let you know :)
[11:40] <Jazzva> Ok
[11:40] <Jazzva> :)
[11:40] <asac> hehe
[11:40] <asac> finally those are your branches ;)
[11:41] <Jazzva> One more question... I read before about ${misc:Depends}, but I couldn't find it after that... What does it stand for?
[11:43] <asac> its a debhelper variable
[11:43] <asac> you can add specific depends during build by setting those variables
[11:45] <asac>  actually i think its used by debhelper tools that don't belong to other categories like perl et al
[11:45] <asac> afaik debconf is one example?
[11:46] <asac> e.g. debconf dependency is added automatically if you use debconf in your scritps?
[11:46] <Jazzva> Hmm, supposed to
[11:46] <asac> but ... this is all is dubious to me too
[11:46] <asac> :)
[11:46] <asac> would have to look
[11:46] <asac> basically its a just a debhelper variable
[11:46] <Jazzva> This one uses automake, and it debhelper added autotools...
[11:47] <asac> he?
[11:47] <asac> to depends?
[11:47] <Jazzva> Build-Depends :)
[11:47] <asac> yeah
[11:47] <asac> but thats not ${mis:depends} :)
[11:47] <Jazzva> So, I figured it uses the same thing for Depends
[11:47] <Jazzva> or something like that...
[11:48] <Jazzva> "the same thing" = "the same way of getting dependencies sorted out"...
[11:48] <asac> well ... its the same ... and not
[11:48] <asac> depends are mostly automatically detected
[11:48] <asac> while build-depends are usually manually
[11:49] <Jazzva> I see....
[11:49] <asac> depends are automatic at least for shared libraries linked into any of your binary/library
[11:53] <Jazzva> Hmm... I'm getting some errors :/
[11:54] <Jazzva> Something like "dpkg-source: cannot represent change to .bzr/repository/knits/57/potfiles.skip-20070805165354-v7ytazn1plhvpf7q-55.knit: binary file contents changed"
[11:54] <Jazzva> When I try to build the source
[11:56] <Jazzva> Uh-huh... there is a hidden .bzr directory...
[11:57] <Jazzva> asac: So, I have to build sources in a directory that is not used for uploading to bazaar.
[11:58] <Jazzva> asac: Ok, found a way to make it work :). No problem anymore :)
[11:59] <asac> Jazzva: there is bzr-builddeb
[11:59] <asac> you should take a look at it
[11:59] <asac> its pretty great to build packages that way
[12:00] <asac> its a package
[12:00] <Jazzva> Hmm... Ok, will do it, after pbuilder finishes updating :).
[12:23] <Jazzva> asac: I installed it and took a quick look at readme file. Is "bzr-buildpackage --builder='debuild -S -rfakeroot'" and then to test it "bzr-buildpackage --builder='pbuilder-gutsy build ../*.dsc'" a legal way to do the building?
[12:24] <asac> depends on what you want todo :)
[12:24] <asac> actually i have i don't use pbuilder that much so i can't tell
[12:24] <asac> but yes
[12:24] <Jazzva> To build a source package which I will use to test in chroot :)...
[12:24] <asac> i usually do
[12:24] <asac> bzr bd --merge .
[12:24] <asac> which requires a orig.tar.gz i tarballs directory
[12:24] <asac> next to your checkout dir (in case you don't tweak config)
[12:25] <asac> in your case I do a bzr bd --export-upstream=../gnome*.upstream --merge .
[12:25] <asac> on first time
[12:25] <asac> then copy created orig.tar.gz from build-area to tarballs
[12:25] <asac> but just when new upstream release is out
[12:25] <asac> otherwise i will reuse the orig.tar.gz generated
[12:26] <asac> so ...
[12:26] <Jazzva> Ok... I think I need to play a bit more with this thing to get used to it :)...
[12:26] <asac> bzr-buildpackage --builder='pbuilder-gutsy build ../build-area/*.dsc' might work
[12:27] <asac> sure
[12:27] <asac> its a matter of preference
[12:27] <asac> usually its smart to have one directory where you put all your bzr branches
[12:28] <asac> then you have one tarballs directory where you have all your tarballs etc.
[12:28] <asac> at least i found it smart ;)
[12:28] <Jazzva> Hmm, I think I have something like that
[12:28] <Jazzva> ~/bzr/upstreams/ for upstream sources
[12:28] <Jazzva> and ~/bzr/ubuntu for branches
[12:28] <asac> yeah ... you can reconfigure it