/srv/irclogs.ubuntu.com/2010/06/06/#ubuntu-motu.txt

=== nobawk|away is now known as nobawk
shadeslayerhi,i would like a mentor for training me02:17
shadeslayerah looks like the mentor program is being revamped...02:18
micahglfaraone: I'm going to try to clean up the pyjamas situation03:41
lfaraonemicahg: cool, thanks.05:16
micahglfaraone: I'll subscribe you to the new bug I'm going to make if you want05:16
lfaraonemicahg: that'd be awesome. I'm about to zzz, so I'll see you tomorrow. :)05:19
micahglfaraone: k05:19
diwicI'm considering packaging four small upstream apps into one deb, should I 1) unpack all upstream sources and repack them as one and considering that my original tarball or 2) just pack the upstream sources into an additional package and unpack the upstream sources during the build process?06:17
micahgdiwic: why not package them individually?06:19
=== andreas__ is now known as anoteng
diwicmicahg: because they are so small, and strongly related to each other06:20
=== happyaron is now known as iDestine
geserdupondje: re qmail FTBFS: not all targets are called as root: "The build target must not do anything that might require root privilege." while "The binary targets must be invoked as root."08:24
=== iDestine is now known as happyaron
geserdupondje: you might fix it by re-arranging the targets a little bit in debian/rules: make the build target don't depend on binary-src but instead make binary-indep depend on binary-src instead of build08:26
loolbdmurray: I only merged the testing version; the unstable version would be needed indeed08:48
loolbdmurray: sorry, ENICK08:48
loneowaishey everyone.... have some question about getting started with devel and packaging09:12
loneowaisfirst of all... a linux program is scattered all across the filesystem.. to /usr/bin and /usr/share etc09:13
loneowaisunlike windows where almost everything stays in one directory09:13
loneowaishow do i lay out my project?09:13
loneowaisdo i create local bin and share directories09:14
loneowaisi've not seen anyone do this09:14
geser!FHS09:14
ubottuAn explanation of how files and directories are organized on Ubuntu, and how they can be manipulated, can be found at https://help.ubuntu.com/community/LinuxFilesystemTreeOverview  see also: man hier09:14
loneowaisubottu: i know that09:14
ubottuError: I am only a bot, please don't think I'm intelligent :)09:14
loneowaisoh09:15
loneowaislol09:15
geser:)09:15
loneowaisso.. when i start writing my app.. how do i layout my source files09:16
loneowaisalso09:16
loneowaiswhile packaging... all examples show hello world or something09:16
loneowaishow do i generate the .dsc and other files when packing a new app... say my own app.i wrote from scratch09:16
geserhow your organize your source is up to you09:17
loneowaisok... so then how does everything end up in /usr/share and other directories09:18
loneowaisi mean09:18
loneowaiswhen converting from source to deb09:18
loneowaishow does the debuild or any packaging system know what file to keep in share and what in lib09:19
loneowaishow to mention that09:19
dupondjeHow can I request a new package into universe? An update of another package is now depending on libopensync-plugin-vformat, but thats not in universe yet ...09:19
oojahloneowais: Typically all packages have a makefile which determines how it is built.09:19
geserthe most part of it does your Makefile (which can also be used by others)09:19
oojahloneowais: It will also provide a way to install files to the appropriate locations.09:20
geserbuild a deb mostly involves: installing the build-dependencies, apply patches if needed, build using the upstream Makefile, install using the upstream Makefile into a stage directory, build the debs from that staging directory09:21
loneowaisoojah: hmmm09:21
loneowaisoojah: so deb packager read the makefile and decides09:21
oojahloneowais: The deb build scrC[C[C[C[C[C[C[C[C[C[C[C[C[C[Cipts will run the Makefile to create the binaries and then install them into the .deb.09:23
oojahOoops, I don't know what happened there.09:23
loneowaisok.. will look into it deeper09:24
loneowaisalso09:24
loneowaissuppose i'm writing an app from scratch09:24
loneowaisa new one...09:24
loneowaishow do i generate the files required for building09:24
oojahloneowais: My recommendation would be to not worry about deb or other packaging quite yet - get your project started and building and go on to that later.09:25
tumbleweeddupondje: before debian import freeze, it should come in by itself, afterwards, a sync request works09:25
dupondjetumbleweed: ok :) lets hope its gets here fast :D09:26
tumbleweeddupondje: what is this for?09:27
oojahloneowais: Or you could try looking at Quickly to get you going: http://bit.ly/404wgL09:27
oojahloneowais: Quickly will do a lot of what you're asking I think.09:27
tumbleweeddupondje: according to http://packages.qa.debian.org/libo/libopensync-plugin-vformat.html it's been in debian for a while, so it must have been blacklisted09:28
oojahOtherwise it's mostly just "write them yourself".09:28
tumbleweedoojah: or dh_make09:30
dupondjetumbleweed: http://packages.debian.org/sid/opensync-plugin-evolution09:30
dupondjefor this one09:30
dupondjenewest versions depends on it09:30
tumbleweeddupondje: you have seen http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=580867 ?09:31
ubottuDebian bug 580867 in opensync "opensync: Unfit for release" [Serious,Open]09:31
tumbleweed(the excuses for all those packages lead to it as the reason for them not being in debian testing)09:31
oojahtumbleweed: Yeah, you're right. I'd made the assumption we were still talking about building source not building packages.09:32
tumbleweedoojah: that's true, but for say a python app there's not much to a setup.py :)09:32
oojahtumbleweed: You've exposed my unconcious bias towards compiled code :)09:33
dupondjebleh, without additional comment ...09:34
tumbleweedyou're the one who suggested quickly :)09:34
oojah:)09:34
tumbleweeddupondje: anyway, it doesn't appear to be blacklisted (http://people.canonical.com/~ubuntu-archive/sync-blacklist.txt) so I don't know what the problem is09:43
geserwhich package?09:46
tumbleweedlibopensync-plugin-vformat09:47
dupondjegeser: http://dupondje.be/qmail.debdiff => like this you mean ?09:48
gesernew (as in not yet in Ubuntu) packages get synced by an other script run by the archive admins, as they review the list of new packages this isn't done very often (compared to auto-sync) and with a long list of new packages it takes some time till the list gets reviewed (which is a cumbersome task)09:50
geserif you need this package now in maverick and can't wait till it find it's way into maverick on its own, file a sync request09:51
geserdupondje: yes (if it works), the build dependency in the binary-indep target should get dropped (and it doesn't do anything anyways)09:52
loneowaisright now i'm backing up eveything from /var/cache/pbuilder/build/6999/var/cache/apt09:52
loneowaismanually09:52
geserloneowais: pbuilder should do it for you (unless you have deactivated it), check /var/cache/pbuilder/aptcache09:54
loneowaisi checked09:54
loneowaisit's empty09:54
geserdo you use pbuilder directly or pbuilder-dist (from ubuntu-dev-tools)?09:55
loneowaispbuilder09:55
dupondjegeser: it seems to build, but only qmail-src package :s09:55
geserdupondje: which is correct09:56
dupondjehmz ok :D09:57
BlackZgeser: steam FTBFS again?09:58
geserloneowais: check if you have set APTCACHE to a directory in /etc/pbuilderrc or ~/.pbuilderrc09:58
geserBlackZ: looks like someone gave it back to the buildd09:58
BlackZgeser: we should fix it ASAP09:59
loneowaisno09:59
loneowaisnothing is mentioned about any cahce09:59
BlackZgeser: so adding the flag -wno-stack-protector is dangerous?10:01
geserBlackZ: see the patch in bug 588519, but I don't know if this change has any other side-effects or not10:01
ubottuLaunchpad bug 588519 in steam (Ubuntu) "[FTBFS] on i368 with "xslt.c:(.text+0x1bb4): undefined reference to `__stack_chk_fail_local'"" [Undecided,Confirmed] https://launchpad.net/bugs/58851910:01
geserBlackZ: only in the sense that it disables the stack protection, which IMHO should only be done if nothing else works10:03
dupondjehttps://bugs.launchpad.net/ubuntu/+source/qmail/+bug/590343 there it is :P10:03
ubottuUbuntu bug 590343 in qmail (Ubuntu) "Fix FTBFS due to root usage in debian/rules" [Undecided,New]10:03
BlackZgeser: seems good to go10:04
BlackZbut I will test the patch10:04
geserdupondje: could you please also forward it to Debian so we can sync in future again?10:05
BlackZgeser: if it works I will unsubscribe the ~ubuntu-reviewers team and I will subscribe ~ubuntu-sponsors with a new debdiff generated (I think that'd be correct)10:05
BlackZgeser: do you think a direct-modify to the interested file would be fine? or we have to include the patch mandatory?10:10
dupondjegeser: i'll do10:10
dupondjedone :)10:12
loneowaisso how do i setup a local cache for pbuilder10:13
toabctlis there a good guide how to manage a debian package with bzr and launchpad?10:13
=== happyaron is now known as iDestine
=== giskard_ is now known as giskard
=== freeflyi1g is now known as freeflying
BlackZgeser: ^ http://launchpadlibrarian.net/49761636/buildlog_ubuntu-maverick-i386.steam_2.2.31-6ubuntu2~maverick1_FULLYBUILT.txt.gz10:37
arandBlackZ: Oh, what do you say about the change there? I just noticed that it worked, but have no idea about it's implications...10:56
BlackZarand: I have applied your proposed patch10:56
BlackZit works, thanks10:56
BlackZarand: looks good10:58
arandOk, yea, I tested and saw that it built and installed, but I haven't really used the program, nor know exactly what it's supposed to do. And I have absolutely no idea what my patch *actually* does, so cheers for picking it up and verifying that it is sane :)10:59
BlackZarand: I have just renamed it in fix-ftbfs.dpatch11:00
arandBlackZ: I was looking for an upstream, but it seem like the package is unmaintained in debian as well, so I was kind of out of luck trying to find someone who knew it thouroghly..11:01
arandIt doesn't seems to ftbfs in debian though... hang on... debian builds a deb for all archs instead it seems...11:05
BlackZarand: in fact it is a change just in ubuntu11:05
dupondjethanks to whoever sponsored my qmail fix ;)12:27
sebnerdupondje: LP says it was geser ;)12:30
dupondjedidn't find :P12:34
ari-tczewsebner: ping12:38
kobrienhey, any core devs about?12:38
ari-tczewkobrien: check in #ubuntu-devel12:39
sebnerari-tczew: I know, I know. I'm a lazy guy. I leave now. Would you mind pinging me again in 8hours? You write a mail, then I promise I'll do it *today*12:39
ari-tczewsebner: ok I'll send an e-mail to you12:40
sebnerari-tczew: thx, sorry for the delay12:40
kobrienari-tczew: ah, wasn't aware of that. cheers12:45
ari-tczewcan someone open a task on nominated releases @ bug 521659 ?12:49
ubottuLaunchpad bug 521659 in lighttpd (Ubuntu) "New upstream 1.4.26, fixes CVE-2010-0295" [High,Fix released] https://launchpad.net/bugs/52165912:49
kobriencan any of you approve an ubuntu blueprint for me?13:11
ari-tczewRoAkSoAx: are you interested in fix CVE-2010-0295 lighttpd package? bug 52165913:11
ubottuLaunchpad bug 521659 in lighttpd (Ubuntu) "New upstream 1.4.26, fixes CVE-2010-0295" [High,Fix released] https://launchpad.net/bugs/52165913:11
ubottulighttpd before 1.4.26, and 1.5.x, allocates a buffer for each read operation that occurs for a request, which allows remote attackers to cause a denial of service (memory consumption) by breaking a request into small pieces that are sent at a slow rate. (http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2010-0295)13:12
johndescshi, i'm a beginner in ubuntu packaging. I'm trying to help with gajim, where I've done a merge from testing.13:31
johndescsnow i'm working on the bugs and one recurent problem is indicator13:32
johndescssomeone posted a patch which applies but now several problems occure13:33
johndescs- the option has to be translated but i can translate only into my mothertongue13:34
johndescs- neither me nor the other know how to make the gajim line disappear when someone unchecks the option13:34
johndescs- no way seem available to integrate easily to indicator-me which has few documentation13:35
johndescsany hint from gurus here (if it's the right place to ask)?13:36
BlackZjohndescs: I don't understand your problem13:42
kobrienI'm packaging a new app. How do I get it approved for Maverick?13:43
johndescsBlackZ: the first: how can a string be translated when no upstream exists?13:43
BlackZkobrien: the best way would be send it to debian then it will be synced in ubuntu as well13:43
BlackZjohndescs: what do you mean "no upstream exists" ? do you mean no project exist in launchpad or... ?13:45
johndescsBlackZ: gajim's upstream don't want indicator support, so there is no upstream for the new option we try to get for indicator13:45
BlackZjohndescs: ah, now it's more clear, I'd say a patch would be sufficient13:46
johndescsBlackZ: sorry to be ambiguous and yes a patch is OK but I don't know how to call for translators13:47
johndescs"translations" is greyed out on launchpad13:47
johndescsbug report of the implementation: https://bugs.launchpad.net/bugs/58727213:48
ubottuUbuntu bug 587272 in gajim (Ubuntu) "gajim doesn't have indicator support" [Undecided,In progress]13:48
ScottKari-tczew: Dapper is not end of life for servers.  Please do not say it is in bugs for server packages (I'm looking at one you did for lighttpd (which is a web server)).13:49
ari-tczewScottK: I know that server support is not end, but it's in universe, so community will fix it eventually13:50
ari-tczewI wrote: feel free if you are affected13:51
ScottKari-tczew: Then why did you mark the bug invalid?13:51
BlackZjohndescs: if there's a patch somebody from the ~ubuntu-reviewers team will review your patch, but please don't subscribe the ~ubuntu-sponsors team until ~ubuntu-reviewers isn't unsubscribed13:51
ari-tczewfeel free to open *13:51
BlackZs/review/review & test13:51
ScottKari-tczew: I did, but I'm not subscribed to every bug.13:51
ScottKari-tczew: Do NOT close such bugs.13:51
ari-tczewScottK: I think that there are not servers using dapper13:52
ScottKari-tczew: It's not end of life and there are.13:52
ScottKI get Dapper related bugs on clamav, so there are users.13:52
ScottKEven if there weren't, it's not your place to declare EOL for Dapper on servers.13:53
johndescsBlackZ: is it ~ubuntu-reviewers' role to translate it and make it work better when we don't know how to progress or shouldn't the patch be already almost ready for upload?13:54
ari-tczewScottK: can we feel your activity to fix these bugs?13:54
BlackZjohndescs: it should be already ready13:54
ScottKari-tczew: How does that relate?13:54
BlackZBTW, I can't help you right now, sorry13:54
ScottKari-tczew: I'm marking on your MOTU app right know that you knowing mark bugs inorrectly.13:54
johndescsBlackZ: Ok will hope not to do wrond things ;)13:55
ari-tczewScottK: hmm, it's very interesting. I've explained with jdstrand support for packages in dapper. There are an UCT. It's got a file called dapper-supported.txt. If package doesn't exist in this file, I can close bug.13:56
ScottKari-tczew: That only applies to Main.13:57
ari-tczewScottK: nice13:57
ScottKari-tczew: Please stop damaging the bug tracker.13:58
ari-tczewScottK: I don't damage anything.14:00
ari-tczewif you're interested in fix this, feel free14:00
ari-tczewScottK: you said "damaging" like I did 100000 mistakes on launchpad. calm down. this question with supporting dapper is to discuss14:02
vishScottK: hi , could you get someone to triage the kde papercuts? https://bugs.launchpad.net/hundredpapercuts/+bugs?field.tag=kde , we've tagged the bugs , "kde" , should be easier to follow14:07
ari-tczewScottK: thanks for comment, love you14:07
ari-tczewthen I think you were always flawless14:08
vishScottK: i had asked yofe-l for help there earlier  , but he seems busy :(14:08
ScottKari-tczew: There's nothing to discuss.14:08
ScottKIt's still supported on servers.14:09
ScottKvish: It's ask txwkinger (when he's around).14:09
vishScottK: will do , thanks14:09
ari-tczewScottK: fine fine, 2 bugs touched and comment like "NOT READY", you're golden14:09
ScottKari-tczew: It's not because of the bugs.  It's because of your reaction to my calling you on it.14:10
geserari-tczew: it's not about mistakes (everyone does one from time to time) but how one reacts if pointed at them. Don't forget that we all work together as a team.14:10
* ScottK has to go now.14:10
ari-tczewcya!14:11
BlackZgeser: have you got the time to check bug #588519 ?14:15
ubottuLaunchpad bug 588519 in steam (Ubuntu) "[FTBFS] on i368 with "xslt.c:(.text+0x1bb4): undefined reference to `__stack_chk_fail_local'"" [High,Confirmed] https://launchpad.net/bugs/58851914:15
BlackZit should be fixed now, there's a proposed debdiff with the arand's patch (proposed) applied14:16
arandBlackZ: I've asked before. I think both of us are kind of unsure about if the fix is a good one...14:17
geserBlackZ: although the debdiff looks fine, I still don't know if it doesn't have any unexpected side-effects on the library. I don't know enough about linking to answer this.14:37
BlackZgeser: thought so14:38
dutchieBlackZ: did you ever get bug-buddy to build?14:38
BlackZdutchie: well, I will work at it tomorrow14:38
BlackZBTW no14:39
BlackZs/at/to14:39
=== nobawk is now known as nobawk|away
=== nobawk|away is now known as nobawk
xteejxHey guys, I'm working on converting the patch in bug 589909 into a debdiff. I think aptitude uses a patch system but my debdiff is a small source change and I don't know about patch systems. Is the debdiff ok? It's at http://paste.ubuntu.com/445634/16:57
ubottuLaunchpad bug 589909 in aptitude (Ubuntu) "aptitude why error message has no newline" [Undecided,New] https://launchpad.net/bugs/58990916:57
micahgxteejx: no, you have to add a new patch w/dpatch17:00
xteejxmicahg: How do I do that? :S17:00
micahgxteejx: http://www.tuxmaniac.com/blog/2008/01/25/dpatch-just-superb-a-short-how-to/ skip to step 517:02
xteejxmicahg: So I edit what I want and tell it to make a dpatch from it? That's easy17:03
micahgxteejx: here's our wiki page on it: https://wiki.ubuntu.com/PackagingGuide/Howtos/Dpatch17:03
micahgxteejx: yeah17:04
xteejxmicahg: Glad our documentation is full of helpful hints lol ;)17:04
xteejxThanks though I'll get on it :)17:04
micahgxteejx: k, thanks17:06
xteejxHow do I do the M-G on the keyboard in nano to go to a line?17:12
xteejxline number*17:12
xteejxdon't worry M=Alt :)17:12
=== nobawk is now known as nobawk|away
xteejxQuestion: If I'm only making up diffs/debdiffs does signing the package matter since it's only local?17:41
Laneyno, it doesn't matter unless you are distributing it17:42
xteejxbug 589909, I have subscribed sponsors, anything else need to be done?17:42
ubottuLaunchpad bug 589909 in aptitude (Ubuntu) "aptitude why error message has no newline" [Medium,Triaged] https://launchpad.net/bugs/58990917:42
xteejxLaney: That's cool thank you :)17:42
Laneyxteejx: forward it to Debian please17:42
xteejxWith the debdiff?17:42
Laneya patch against their vcs would be best17:43
xteejxvcs??17:43
Laneyotherwise a debdiff against the latest version in debian17:43
cody-somervilleno17:44
xteejxwell its against the maverick version of aptitude I assumed that would be enough?17:44
Laneydon't assume, check17:45
xteejxI'm new to this :(17:45
Laneybut at least the changelog entry won't be right for Debian17:45
Laneycody-somerville: what does "no" mean? If you think I'm giving incorrect advice then please correct me properly17:46
xteejxoh I didn't realise I had to do it for Debian17:46
cody-somervilleLaney, I said no first.17:46
LaneyI don't know what you were saying no to17:47
cody-somervilleLaney, so I think we were giving the same answer to xteejx's question.17:47
Laneyoh, it appeared out of order17:47
xteejxIt did here too :)17:47
* cody-somerville is on crappy hotel wifi.17:47
xteejxSorry if I ignored it17:47
Laneywow, nobody has merged aptitude in a long time17:49
xteejxThe version of aptitude in Maverick is 0.4.11.11-1ubuntu10, Debian sid is 0.6.2.1-2 ermmmm isn't it WELL out of date anyway?17:49
xteejxAm I missing something here?17:52
* xteejx is confused17:52
Laneythose versions are right17:53
geser0.4.11-1 got uploaded to Debian unstable on 2008-11-20, the next version which went into unstable was 0.6.0.1-1 on 2009-10-25 and only 0.6.1.5-3 made it into testing on 2010-03-23 (don't forget lucid synced with testing)17:54
geserso it doesn't look that bad17:55
xteejxSo if there's going to be a merge for aptitude the patch is probably irrelevant?17:55
geserdepends if it's still an issue or not17:56
xteejxI see :) So when will the merge happen?17:56
xteejxI think I'll leave that bug report and come back to it at a later date, there is a debdiff for it anyway but my head is hurting now lol :P17:57
Laneyall you need to do is set up a Debian chroot and then reproduce the bug there17:58
Laneyand if you can then submit the patch to the BTS17:58
geserxteejx: depends on how long you will need to prepare a merge :) (if you are interested in merging it of course)17:59
xteejxLaney: When I learn how to hehe :)18:01
xteejxgeser: I don't know, I'm taking MOTU stuff a step at a time18:01
xteejxDon't get me wrong, I would love to started really getting involved, but I get headaches easy ;)18:01
=== yofel_ is now known as yofel
=== fta_ is now known as fta
arandDoes anyone have some time over to sponsor Bug #581331 (sru:s, in order that we can restore functionality for msn...)22:57
ubottuLaunchpad bug 581331 in bitlbee (Ubuntu Karmic) "error message while trying to use my MSN account in bitlbee" [High,Triaged] https://launchpad.net/bugs/58133122:57
Laneyarand: yeah alright23:06
* arand hugs Laney 23:07
=== cr3_ is now known as cr3
Laneygood job it's quick to build23:13
Laneyarand: done, thanks for your contributions23:27
arandLaney: Cheers!23:27
Laneyit would maybe have been better to try and use the "patchsys" that the package has already, but I don't think it's a big issue since it's a weird one anyway23:29
arandLaney: Hmm, well, I looked into that, and that patches is simply called by debian/rules, after the compilation steps it seems, and I though that it might've simply been stuck in there manually, thus it made litte sense for me to try to shove this into there in some arbitrary way as well, but I don't know if it's just an odd patch system, which I didn't figure out?23:41
Laneyarand: You would have stuck the diff in debian/patches and then added a patch line in the rules file23:43
arandYea, I tried that, but when I saw that I wouldn't be able to place it just in the same place as the other one, I figured it would be better to just use patchless. I asked here before, and was pretty much told to do either, with little preference.23:45
arandBut if policy is policy, I should've gone with that still?23:46
LaneyI think it is probably slightly preferred, but like I said it shouldn't matter23:48
arandOk, just making sure I'm on the right track.23:49

Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!