=== almaisan-away is now known as al-maisan === lifeless_ is now known as lifeless === al-maisan is now known as almaisan-away [07:04] good morning === herac|ide is now known as heraclide [07:19] good morning dholbach [07:19] hey geser === chrisccoulson_ is now known as chrisccoulson === almaisan-away is now known as al-maisan [08:21] hi all [08:23] I have just read some guides.... and I am wondering what should I do now [08:23] can someone follow me for a short period of time? [09:09] I want to see what's inside a library, can i do that ? [09:10] get the source? [09:11] i have the source [09:12] Zhenech: i got it using apt-get install liblightdm [09:12] Zhenech, i'm sorry i'm a newb, is that the source ? [09:13] apt-get source liblightdm will give you the source [09:14] Zhenech, i see, thanks [09:14] Zhenech, where will it save the source code ? [09:14] it will tell you :) [09:14] Zhenech, thanks alot :D === al-maisan is now known as almaisan-away [10:45] hi.. [10:46] when I am upgrading a package, should I put "quantal" as release? [10:50] yofel: could help me for a while? [10:52] alo21: the release in the changelog is the release you are uploading to [10:52] which is almost always going to be the development release, currently: quantal [10:52] tumbleweed: for example I am trying to fix this (https://bugs.launchpad.net/ubuntu/+source/gajim/+bug/1044292) [10:52] Launchpad bug 1044292 in gajim (Ubuntu) "[new-upstream]Gajim 0.15.1" [Undecided,New] [10:53] tumbleweed: Is a good idea to put 'quantal'? [10:54] yes [10:54] tumbleweed: and as I learnd I should write 'new upstream' as a comment. Right? [10:55] new upstream release* [10:55] yes, and then mention all teh packaging changes you had to make (if there are any) [10:56] tumbleweed: I have just applied the debdiff to the new version [10:56] tumbleweed: Should I list it? [10:57] no, that's not a change [10:57] does this new release have new features? or only bugfixes? [10:58] tumbleweed: how I know it? [11:01] tumbleweed: I did not introduce any other changes, a part joining the debdiff [11:03] alo21: read the diff? look at the upstream commit history? [11:04] from the changelog in the bug, the only potential issue looks like farsight -> farstream (I don't know enough about them to know offhand how invasive that is) [12:15] Nafallo: [12:15] Nafallo: hi.. I am fixing this bug (https://bugs.launchpad.net/ubuntu/+source/gajim/+bug/1044292) [12:15] Launchpad bug 1044292 in gajim (Ubuntu) "[new-upstream]Gajim 0.15.1" [Undecided,New] [12:15] and I create the package. Where should I upload it? [12:18] alo21: sorry. I haven't touched the package for years, and I probably haven't got upload rights anymore. [12:18] -EPERSON [12:19] alo21: I think you should contact the current maintainer (check https://launchpad.net/ubuntu/+source/gajim for his name) [12:19] Nafallo: ok.. thanks [12:21] actually, looking at that page, we're using the debian package these days [12:21] alo21: don't touch it. the only thing necessary is getting it synced from debian :-) [12:22] what's the pre-release freeze currently in effect about? [12:22] Nafallo: I downloaded the source from the website (http://gajim.org/downloads.php?lang=en#tarball). Isn't right? [12:22] alo21: no [12:23] alo21: it's a sync from Debian these days. not an ubuntu package at all. [12:23] Nafallo: ok [12:24] we're in beta1 freeze? [12:25] yesyes [12:25] DOUBLE YES [12:26] :-) [12:27] so yeah, get it synced. it's a bugfix release :-) [12:27] gajim (0.15-1.1) unstable; urgency=high [12:27] * Non-maintainer upload by the Security Team. [12:27] * Fix CVE-2012-2093: insecure use of temporary files when convering LaTeX [12:27] IM messages to png images. Closes: #668710 [12:27] src/common/latex.py in Gajim 0.15 allows local users to overwrite arbitrary files via a symlink attack on a temporary latex file, related to the get_tmpfile_name function. (http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2012-2093) [12:27] -- Luk Claes