=== Chipzz_ is now known as Chipzz [00:48] Now that Raring has been released, can the packages that have been granted FFe still go into Raring stable? [00:53] 01:44 < maxb> It's slightly unclear what you mean by 'Raring stable' [00:53] 01:47 < maxb> The raring release pocket is absolutely and completely immutable at this point. Stable Release Updates can be processed into raring-updates, but a grant of FFe prior to release probably is invalid at this point [00:55] Ah well [00:56] saiarcot895: A new package? A new feature in an existing package? [00:56] New upstream version in three existing packages [00:56] all related [00:56] In either case an FFe isn't relevant any more, and your only option is probably to get it into saucy-backports [00:56] That sounds like a good case for -backports. [00:57] You mean raring-backports, right? [00:57] Er, yeah [00:57] saucy, and then raring-backports [00:57] https://wiki.ubuntu.com/UbuntuBackports [01:01] will work on that [01:01] I still have to follor the sponsorship process, right? [01:01] *follow [01:16] For backports you need to get it into saucy first [01:17] I know [01:17] To get it into Saucy itself, I still need to use the sponsorship process, right? [05:34] dpkg-buildpackage -rfakeroot -d -us -uc -S failed [05:34] bzr: ERROR: The build failed. [05:34] when i try to build s test package i get this output, what am i doing wrong? [05:36] We'd need to see the whole output (in a pastebin or similar). That looks like it follows some earlier error. [05:38] http://pastebin.com/UT3tdwBj [05:39] crhrabal: You need to satisfy the package's build-dependencies first. sudo apt-get build-dep mountmanager (unless this is a package you're developing, in which case install the Build-Depends listed in debian/control) [05:40] cjwatson: Thanks. === a16g__ is now known as ypwong === tkamppeter_ is now known as tkamppeter === jhe|away is now known as jhenke [09:47] hi guys, I'd like to contribute into bug-solving etc...what do you recommend to start? [09:47] *contribute to [09:53] guyys :) [12:54] i want to develop app for terminal using c++, but don't know where to start from :( could any one please help me [13:07] deeps_, you will have to be more specific [13:13] deeps_: echo -e "#include \nusing namespace stn ()\n{\n\tcout<<\"Hello World\";\n\treturn 0;\n}\n">hello-world.cpp&&g++ -o hello-world hello-world.cpp&&./hello-world;echo [13:14] deeps_: If you want something that puts characters at specific places on the terminal or has a menu like thing in a terminal then you might want to look at libncurses or libnewt [13:14] deeps_: echo C[C[C[C[C[C[C[C[C[C[C[C[C[C[C[C[C[C[C[C[C[C-e "#include \nusing namespace std;\nint main ()\n{\n\tcout<<\"Hello World\";\n\treturn 0;\n}\n">hello-world.cpp&&g++ -o hello-world hello-world.cpp&&./hello-world [13:14] meh [13:15] deeps_: echo -e "#include \nusing namespace std;\nint main ()\n{\n\tcout<<\"Hello World\";\n\treturn 0;\n}\n">hello-world.cpp&&g++ -o hello-world hello-world.cpp&&./hello-world [13:15] i have develop app [13:15] in c++ [13:15] its ready... [13:15] all i need to know is... [13:16] let me start again... [13:16] i have develop an app for terminal using c++ [13:16] deeps_: ...compile it? ...package it? ...port it? [13:17] run it ? [13:17] i am stuck with 2 parts... [13:17] 1st one... [13:17] in terminal we have feature like by pressing key it shows the possible commands for the application... [13:17] how do i do it with c++ [13:18] no idea at all :( [13:18] deeps_: readline [13:18] deeps_: http://www.gnu.org/software/readline/ [13:20] and how can i package it and make available as repo? [13:21] deeps_: http://developer.ubuntu.com/publish/my-apps-packages/ [13:22] thanx a lot...i think i should check those links :) [13:26] deeps_: https://launchpad.net/~sladen#email-addresses [13:34] wendar: ^^where do the app-review team hang out these days? [13:34] sladen: ubuntu-arb [13:35] though, the first question sounds more like #ubuntu-app-devel [13:39] wendar: ta, yes, the latter [13:53] Arer there Ubuntu project written in C++ I can contribute to? [14:03] Is there anyone alive here? [14:03] mzaza, be patient. Patience is one of the things needed when contributing:) [14:04] smartboyhw: Sure, OK :) [14:17] mzaza: yes, plenty of people are alive. There is alot of software in Ubuntu that is written in C++. Is there perhaps a particular bug you've noticed, or feature that you would like. That might narrow down where to look and work on [14:19] mzaza: apt-cache rdepends libgcc1 will show you a list of programmes using C++ [14:22] sladen: It will? [14:23] sladen: I think you mean libstdc++6 [14:25] mzaza: ^^ [14:25] libstdc++6 then? [14:26] mzaza: apt-cache rdepends libstdc++6 will show you a list of programs using C++ [14:27] sladen: Would you recomment an easy project to start on if I am new? I was think in Compiz but I think it might be complex for my level. [14:30] mzaza: Is there perhaps a particular bug in Ubuntu, or feature you've wanted to add? That would narrow down what types of software might be interesting. The best is often to have a goal, and to work back [14:30] mzaza: *Ubuntu, or any of the software packaged for Ubuntu [14:31] sladen: Yes, Unity. It's sluggish :D [14:33] mzaza: Pick a package you use a lot and look through the bugs for it or pick a bug that annoys you [14:36] penguin42: And download it's repos using git, right? But how to know which file is releated to the bug, I mean is there like a file I should check to know more about where everything goes to? [14:37] mzaza: That very much depends on the project - you have to get to know the source a bit - but that's learning [14:37] mzaza: debugging; although for instance a stack-trace might lead you to the file/line-number; or even just simply reading the code (particularly in a small program/package) [14:37] mzaza: did you have a bug number in mind/ [14:38] sladen: No not, yet I am checking the Bugsquad now and setting everything up. [14:41] mzaza: what software do you use (other than Unity) [14:45] sladen: Well Ubuntu with Unity, vim, g++, chromium, virtualbox, monodevelop, smplayer. That's what I use on daily basis [14:45] sladen: The software center too [14:46] & Ubuntu one [14:48] The most thing I wish to help in fixing, but it will be complex for my level is the performance of Unity. I was surprised to see Windows 8 out performance Ubuntu on both low-end and high-end machines. [14:50] yeh start simpler; although you might want to learn to use profiling tools like perf [14:50] the performance of the Unity-3D codebase is somewhat ... suboptimal. A lot of the good old performance of Unity-2D should be regained with the move back to Qt [14:54] So, is there like a PDF guide written in easy way I could read like the KDE Developer guide to help me set me up? [15:02] mzaza: why not work on a Qt/KDE application if you're already familiar with that area? [15:04] yeh and they're normally C++ [15:04] sladen: I am not familiar I just read the guid and I was going to start working with it. But I don't use KDe so I thought I should work on something I use. [15:06] mzaza: QML/Qt is the widget set and technology the Unity-Ubuntu stuff is using, so I don't think you'd go far wrong [15:08] mzaza: perhaps you should work on smplayer! that is Qt [15:10] sladen: I'll check it out. Is it normal if feel somewhat lost :D [15:10] at the beggining I mean [15:14] yes! [15:15] mzaza: There's a lot of source out there and a lot of bugs, and some packages are BIG [15:21] penguin42: Right... [15:22] Well, thanks guys for helping me out :) [15:22] exit [15:55] Well, I have perused documentation but can't find a lot of good tutorials. I have fixed a number of bugs within the code itself, I just don't know how to make a patch. I thought the actual development process was supposed to be the hard part, but it seems I'm mistaken. [15:58] crhrabal: Patch at what point ? [15:58] I got the source code on my computer, I fixed the source code [15:59] And that's where I'm stuck [15:59] ok, is it a debian package or just the upstream source, and did you download it as a tar or using git/svn/bzr/what? [15:59] downloaded in bzr [15:59] and its traced back to debian [16:00] do i need to push it to debian before it can be pushed into ubuntu? [16:01] crhrabal: https://wiki.ubuntu.com/UbuntuDevelopment for a start [16:01] crhrabal: it depends [16:01] crhrabal: If it's something ubuntu has screwed up then you can fix it in ubuntu, you can also fix it in ubuntu but generally it's preferred to fix it upstream if you can [16:02] Oh, I figured the way to go was fix it in ubuntu then push the change upstream [16:03] crhrabal: it's not a hard rule, however if it's fixed in ubuntu then it means ubuntu has to keep updates if upstream updates and it's a bit messy - if you can get it fixed upstream everyone is happy [16:04] crhrabal: Also if the upstream guys agree your patch is the right way, then the ubuntu guys are quicker to take the patch [16:11] okay thanks === hggdh_ is now known as hggdh [17:46] hello... I have been using ubuntu for some time and I want to figure out how I can contribute to ubuntu. [17:47] pianogmx: https://wiki.ubuntu.com/ContributeToUbuntu [17:48] penguin42: i already saw that.... [17:49] pianogmx: OK, are you a programmer? [17:49] i have learned how to program on WIndows with .NET and Java... but I want to learn how to program for ubuntu [17:50] i made a notepad program using C++ and QT a month ago [17:51] you could look at some bugs on Qt apps and see if you can fix them, or look at Qt upstream to see if you can help fix bugs there [17:58] penguin42: would that be considered working outside of the ubuntu project though if i wanted to contribute to ubuntu and be an ubuntu member? [18:00] pianogmx: Well Unity is moving (back) to using Qt - not sure of the details of that, best to ask someone involved - so not sure if you can get involved in that [18:01] pianogmx: But if you fix a bug in a package that Ubuntu makes use of then you help Ubuntu users as well as other users [18:01] okay thanks for the advice ill be back [18:11] penguin42: is there more value in me contributing to the ubuntu / unity flavor than the ubuntu / kde flavor? [18:13] pianogmx: There's value in your contributing to what you enjoy using and working on. [18:15] ok === Ursinha_ is now known as Ursinha === Ursinha is now known as Ursinha-afk