[03:48] o/ === NoklaM_ is now known as NoklaM [15:25] hi ! [15:25] o/ [15:25] i think i just assigned flocculant as reviewer for bug-1183096 [15:26] hi NoklaM :) [15:28] How's it going sakrecoer_ [15:28] ? [15:28] bug #1183096 [15:28] bug 1183096 in Ubuntu Manual Tests "Test Needed: Scribus" [Undecided,New] https://launchpad.net/bugs/1183096 [15:31] Spent half a night figuring out why the microphone wasn't working [15:31] Hmm there is no link from the bug to the testcase. [15:32] Wasn't studios fault although before I realised what was wrong(loose cable) i reinstalled the system temporarly [15:32] sakrecoer_: https://code.launchpad.net/~sakrecoer/ubuntu-manual-tests/bug-1183096/+linkbug [15:33] krytarik: where do i find the link to that page... [15:34] sakrecoer_: "Link a bug report" on: https://code.launchpad.net/~sakrecoer/ubuntu-manual-tests/bug-1183096 [15:34] sakrecoer_: if you check your personal launchpad it's there also [15:34] linked in i think Code tab [15:34] ah :) of course :) :faceplaming myself: [15:34] thanks! [15:34] Sure. [15:35] i followed this template to bzr prush: bzr push lp:~username/ubuntu-manual-tests/bug-BUGNO [15:36] yup that should do it [15:36] if i would do that again, but with a different /bug-BUGNO, will it create a new branch? or does bzr... understand the bugnumber? [15:37] since i had to link the bug from the testcase, i assume it will create a new branch if i change the bug-BUGNO? [15:37] sakrecoer_: the bugnumber becomes the name of your personal package [15:38] or directory in this case [15:38] sakrecoer_: Funny commit log, btw. :P [15:38] why? :) [15:39] it is my first ever so i expect it to be funky :D [15:39] sakrecoer_: Generally you'd want the commit messages to reflect the actual changes - and having them all the same doesn't particularly help. :P [15:40] http://bazaar.launchpad.net/~sakrecoer/ubuntu-manual-tests/bug-1183096/files/head:/testcases/packages/Studio/ lists four test cases. scribuse is the only one with no number. [15:41] Is that assigned later? [15:41] Yup after review OvenWerks [15:41] * OvenWerks thought that might be the case [15:41] OvenWerks: mind if i pm you about silly stuff I meant to ask you the other day? [15:41] krytarik: ok, i'll keep it in mind for next one :) [15:42] ok [15:44] krytarik: if i make a new manual testcase, should i push it to the same branch althought the LP bug has a different number? [15:45] or does it matter if i have one brnach for each manual testcase? [15:46] I'd work on one file at a time sakrecoer_ , personal experience with bzr, if you work on more then one it gets messy [15:46] sakrecoer_: Well, since you follow "bzr push lp:~username/ubuntu-manual-tests/bug-BUGNO", it'll be a different one, of course. [15:47] ok... i feel like i missing some part of the required informartion... [15:47] NoklaM: That's not true though. [15:48] NoklaM: that is confusing,... i need to make one file for each testcase... and if i have to wait for reviewm i will never get them done.. [15:49] sakrecoer_: That's why you push to different branches. [15:49] Last time i worked on 2 files with bzr it kept pushing commits to the 1st file where's the commit was 2nd file [15:49] krytarik: ok... i think i get it :) [15:50] NoklaM: Because I think you did something wrong there. :P [15:50] krytarik: ofc i did something wrong hehe :P [15:51] butso its perfectly fine to have one new branch for each manual testcase, althought they all are going to end up in the same branch? [15:52] branch will be same ubuntu-manual-tests, but each one will have a seprate case [15:54] sakrecoer_: https://code.launchpad.net/ubuntu-manual-tests/+code?field.lifecycle=MERGED&field.lifecycle-empty-marker=1&field.sort_by=by+most+interesting&field.sort_by-empty-marker=1 [15:54] Illustrates it very well. [15:55] ok :) now i feel my infor is integer again thanks! :) [15:58] NoklaM: For example, this isn't right either: ' it's done by bzr commit -m "Text of what you did goes here" filename'. [15:58] Isn't it? [16:00] krytarik: I'm preaty sure i got it of one of the ubuntu websites [16:00] NoklaM: In fact, that's how you messed it up. :D [16:00] D'oh [16:01] → http://doc.bazaar.canonical.com/latest/en/user-reference/commit-help.html [16:01] cheers [16:02] hmm... i also did bzr commit -m "lazytext of what i did" [16:04] krytarik: what should be done instead? [16:04] sakrecoer_: No, that's the right, more usual way. [16:05] krytarik: hmm... i can't see the difference with what NoklaM wrote... [16:05] The file name specified. [16:05] That limits the commit to just that one file. [16:05] aah! of course hah :) tahnks for your patience krytarik :) [16:08] sakrecoer_: You're welcome, of course. :) [16:16] while writing a testcase for blender, some stuff didn't work... [16:16] krytarik: what should i do then? file a bug? [16:17] sakrecoer_: Of course. [16:17] sakrecoer_: best to do a bit of checking first. does ubuntu have the latest that debian has? [16:18] blender is crashing when choosing jack as sound engine... [16:18] sakrecoer_: that is: should bug report be the bug itself or pulling in the newer blender [16:18] sakrecoer_: jack is running? [16:18] yes [16:19] That should not be new code... [16:19] OvenWerks: jack is running, touching any of the options in audio makes blender freeze- [16:20] The jack API has not changed for a long time. [16:24] so what do you suggest i do? [16:27] * OvenWerks open blender [16:27] * OvenWerks is now lost :P [16:27] I don't have a clue how to even find how to set audio in blender [16:30] OvenWerks: file>user preferences> system tab [16:31] i didn't even know blender had audio settings i always thought it only did 3d modeling and such [16:32] blender is the perfect "blend" between 3d studio max, finalcut, after effects, z-brush, and photoshop [16:33] Didn't know that wow [16:33] I used it once tho and got lost in the UI [16:34] Ya the learning curve is high [16:34] check out this short made with it :) https://youtu.be/41hv2tW5Lc4 [16:34] I don't have enough of a use for it to go there. [16:35] Are those actors or CGI? [16:35] the difficult part is to learn to 3d terminology, and the 3d "thinking" the UI is very unique and scary at first, but very soon it becomes just aweseom [16:35] the actors are humans.. [16:35] its the first openmovie whree they mix 3d with real images... its gotten even better now, that was back in 2012 and lots has happened... [16:36] did i mention how much i love blender ? :D [16:37] OvenWerks: it works! but you have to set blender to use JACK before jack is started :) [16:37] then save user settings, quit blender, start jack, open blender and set AV-sync [16:38] so feature, not bug :D [16:38] i wish all blender build would come with jack, turns blender into a great VSE with ardour for the audio part :) [16:43] sakrecoer_: that was one weird short, i have no idea what I've just watched, but it looks like blender capabilities are just wow [16:51] NoklaM: yeah... the scenarios of the openmovies are not always very good... i think they work on it collectively a bit like surrealist used to do: cadaver exquis :) [16:54] wb NoklaM :) [16:55] https://en.wikipedia.org/wiki/Exquisite_corpse this is what the openmovie scenario remind me of... sorry for OT.. [17:05] zequence: So, let's have an offtopic channel, too! :P [17:06] * sakrecoer_ puts on shamehat and walks over to corner [17:06] :) [17:12] sakrecoer_: Like I indicated, no need to feel bad here. :) [17:15] krytarik: (^^,) thanks! [17:19] zequence: Ftm, is there a particular reason why this one has the 's' mode? ("This channel will not appear on channel lists or WHO or WHOIS output unless you are on it.") [17:34] krytarik: becasue that way we don't get #ubuntustudio types of questions here [17:35] or at least as many [17:36] Heh. [17:42] Ftm, we don't have so many in #xubuntu-devel and #lubuntu-devel either. [17:43] (And they aren't set to be secret.) [17:44] not my decision, Just a guess on my part as to why. [20:16] sakrecoer_: thanks - seen your MPs - need a little bit of fixing then push again and I'll be happy [20:17] as I say in comments any action is

and the reaction

:) [21:22] sakrecoer_: Also, the Scribus file shouldn't be in your Blender branch. [21:36] flocculant: ok :) cool! so... if the scribus file shouldn't be in the blender branch, should i pull a new clone of ubuntu.manual-tests for each testcase? [21:37] krytarik: [21:38] how do i push the branch while ommitting all the other testcase files? [21:49] hmm... "bzr: ERROR: Permission denied: "~sakrecoer/ubuntu.manual/tests/bug-1183096/": : Cannot create branch at '/~sakrecoer/ubuntu.manual/tests/bug-1183096' [21:49] ah... osrry.. of course... [21:52] flocculant: i pushed the fixes, i hope that will make it... cant seem propose a merge, because the old one is still active.. [21:53] (for scirbus) need to sleep, will look into the blender branche tomorrow... [21:53] thaks for your patience guys! read you soon! [22:20] sakrecoer_: "should i pull a new clone of ubuntu.manual-tests for each testcase?" - Yes, but in this case, it's better to just remove the Scribus file and commit that. [22:28] sakrecoer_: And with your latest push to the Scribus branch, you now mixed it up with Blender, too. :P [22:29] Nvm, I see you reverted that. [22:38] sakrecoer_: You didn't have to do a new MP either, btw.