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