[00:10] <shadeslayer> simar: ever heard of the gnusim8085?
[00:10] <shadeslayer> i made this program on it : http://pastebin.com/81qsAbdG
[00:11] <shadeslayer> but im getting Execution branched to invalid memory location <6H>. Execution will be stopped! << please reply in PM
[00:30] <simar> shadeslayer: no idea in assembly. I work in c
[01:22] <simar> shadeslayer: there?
[01:23] <simar> shadeslayer: oh sorry .. soo jaa kaaka .. shhh!!!
[03:59] <ebroder> micahg: Still around?
[03:59] <micahg> ebroder: yes
[04:00] <ebroder> I'm looking at bug #622914, but I can't find those two CVEs anywhere. Is there an announcement somewhere?
[04:00] <ebroder> Sorry - wrong bug. bug #622900
[04:00] <micahg> ebroder: in the changelog
[04:01] <micahg> ebroder: I figured since it was the devel release that would be enough, I plan on a full bug with all the info for the SRUs
[04:01] <ebroder> micahg: Yeah, yeah - I see the numbers. I want to know what the actual vulnerabilities are
[04:01] <ebroder> Curiosity as much as anything else
[04:02] <micahg> ebroder: http://www.phpmyadmin.net/home_page/security/PMASA-2010-5.php
[04:02] <ebroder> Ah - XSS bug. Boring :-P
[04:02] <nigelb> heh
[04:04] <ebroder> micahg: Anyway, yeah - I agree. Security microrelease == no FFe. I'll ACK it
[04:04] <micahg> ebroder: thanks
[04:04] <micahg> there will probably be a 3.3.6 before Maverick release, but we'll see if it's bug fix or features
[04:07] <ebroder> Can you punt the ubuntu-sponsors subscription? I've been too lazy to get my membership renewed :)
[04:15] <micahg> ebroder: sure
[06:00] <Obsidian1723> anyone here know about packaging deb files? I'm in the process of reading https://wiki.ubuntu.com/PackagingGuide/Complete but this is more of a question of, "is this the best way to do it?" than anything else. I want to find the best way to distribute images for wallpapers, fonts, document files, and also an install-setup.sh for setting up new installs. Basically the idea is to do a new Ubuntu install, add the PPA, update it
[06:00] <Obsidian1723> and then the file downloads and does all of the work. Is this the best way to do that? One issue that may arise is the shell script does reqire some user input to it. Forgive me. I am not a programmer, new to packaging, etc. Just want some feedback on my method really. Right now I have an alternaitve Ubuntu ISO with a kickstart file that does a wget to.dropbox.com -O- | sh and it works, but it's crude.
[06:45] <micahg> directhex: do you know what linux-vdso.so.1 is?
[06:47] <jetienne> q. apt-get doesnt support http proxy ?
[06:48] <jetienne> due fixed it
[06:49] <jetienne> sudo export http_proxy and not just export
[07:12] <directhex> micahg, if memory serves, it's an imaginary library (i.e. it's part of the kernel)
[07:13] <directhex> used to be linux-gate
[07:13] <micahg> directhex: k, I was wondering if that's why moonlight was crashing due to an unavailable lib
[08:04] <dholbach> good morning
[11:31] <simon-o> tumbleweed, I'm not quite sure, what the FFE for bug 622914 would look like. I would like to get this in, because tmux 1.3 has some nice features http://tmux.cvs.sourceforge.net/viewvc/tmux/tmux/CHANGES (like mouse-wheel support) and fixes many bugs
[11:32] <tumbleweed> simon-o: just say excatly that and subscribe ubuntu-release (bug numbers are good)
[11:35] <simon-o> tumbleweed, thanks. will do :)
[11:41] <AnAnt> Hello
[13:46] <bilalakhtar> If a package has a dfsg bit, and has no ubuntu changes, and I want to upgrade it in Ubuntu only (special case), what should be done ? Can I just remove the dfsg bit and mark -0ubuntu1 ?
[13:47] <tumbleweed> bilalakhtar: +dfsg means a repack
[13:47] <tumbleweed> so if you are upgrading it in ubuntu, do the same repack
[13:47] <tumbleweed> (there should be a get-orig-source rule to do it)
[13:47] <bilalakhtar> tumbleweed: ok, got it
[13:48] <bilalakhtar> tumbleweed: yes there is
[13:48] <bilalakhtar> tumbleweed: so I should go ahead and just do as I do normally?
[13:48] <bilalakhtar> no
[13:48] <bilalakhtar> I understood
[13:48] <bilalakhtar> now
[13:49] <tumbleweed> bilalakhtar: yeah except that you are using the repacka you created, not the upstream tarball
[13:50] <bilalakhtar> tumbleweed: ok so I will need to repackage, will I need to upload the repack somewhere else?
[13:50] <ari-tczew> bilalakhtar: do you plan join motu?
[13:50] <tumbleweed> bilalakhtar: no, the sponsor can do the same repack
[13:51] <bilalakhtar> ari-tczew: yes
[13:52] <persia> Hrm?  If there's a repack in Debian, it's best to use the *exact same* binary artifacts that Debian produced for the repack, rather than re-repacking it.
[13:52] <ari-tczew> bilalakhtar: any particular date?
[13:52] <bilalakhtar> ari-tczew: it happened long ago
[13:52] <bilalakhtar> There's good news, people
[13:52] <bilalakhtar> No need, since the repack was done to remove a file
[13:52] <bilalakhtar> Upstream has removed it now
[13:53] <bilalakhtar> tumbleweed: so I am dumping the dfsg bit in the version. Okay?
[13:54] <bilalakhtar> BRB
[13:54] <ari-tczew> bilalakhtar: what happened long ago?
[13:54] <tumbleweed> bilalakhtar: why?
[13:54] <tumbleweed> bilalakhtar: oh, I see
[13:54] <tumbleweed> nm
[13:54] <tumbleweed> persia: bilalakhtar was talking about a new upstream release
[13:58] <persia> Ah, right.
[14:02] <bilalakhtar> ari-tczew: The repack happened long ago
[14:02] <ari-tczew> bilalakhtar: I asked when do you plan sign up on meeting...
[14:03] <bilalakhtar> ari-tczew: In the september 14 meeting
[14:03] <bilalakhtar> ari-tczew: By then, I hope to gain a little bit more experience
[14:04] <ari-tczew> bilalakhtar: do some security fixes :)
[14:06] <ari-tczew> tumbleweed: are you busy?
[14:06] <tumbleweed> ari-tczew: afraid so, yes
[14:06] <ari-tczew> aha
[14:13] <bilalakhtar> tumbleweed: Like merges, in package upgrades also should I outline all debian/ubuntu changes in the changelog?
[14:13] <bilalakhtar> I have added a message in changelog why I dropped the repack
[14:15] <tumbleweed> bilalakhtar: in merges you don't have to outline debian changes, but yes you should always outline *your* changes in the changelog
[14:15] <bilalakhtar> tumbleweed: in merges we outline Ubuntu changes
[14:15] <tumbleweed> yes, the changes you are applying
[14:15] <bilalakhtar> tumbleweed: here I am outlining non-upstream changes
[14:15] <bilalakhtar> yes
[14:16] <bilalakhtar> building now
[14:20] <bilalakhtar> Built!
[14:27] <bilalakhtar> Hey! When I ran update-maintainer, it added the old maintainer to the uploaders! Is it right?
[14:28] <Laney> I don't think it should touch the Uploaders field
[14:28] <bilalakhtar> No, I saw it the wrong way
[14:28] <bilalakhtar> It did it correct
[14:28] <Laney> (nor does it from the code)
[14:28] <Laney> ok
[14:29] <bilalakhtar> I was actually looking at the DSC
[14:29]  * bilalakhtar will leave now
[14:31] <zul> we have a team meeting today dont we?
[14:38] <ari-tczew> zul: which meeting? DMB?
[14:38] <zul> oops...wrong channel
[14:52] <james_w> of the web tools that we have that support adding comments on packages (e.g. merge-o-matic) do those comments persist with new versions?
[14:53] <james_w> i.e. is the comment field blank after a new version is uploaded, or does it keep the same value as it had before?
[14:55] <Laney> IIRC they were reset
[14:55] <Laney> but you can get the source of mom
[14:55] <james_w> yeah
[14:55] <james_w> getting it is one thing, answering that question for sure is another
[14:55] <james_w> from what I've seen it looks like they aren't reset but I'm not sure
[14:55] <Laney> I wonder what happened to merges.ubuntu.com/xxx.html
[14:56] <james_w> ENOSPC I believe
[14:56] <Laney> is there an RT about it?
[14:57] <james_w> don't know
[14:57] <Laney> anyway it makes sense to me for them to be linked to versions, as the kind of things they were used for were transient
[14:57] <Laney> bug numbers and assignment tracking mainly
[15:03] <james_w> it appears that they persist
[15:04] <tumbleweed> that's my memory of them, you'd often come across comments that related to previous merges
[15:06] <Laney> if that's true, then I feel retrospectively bad for putting bug numbers in the comments ;)
[15:18] <fabrice_sp> tumbleweed, working on the sponsorship queue?
[15:18] <fabrice_sp> (I won on bug 623358 by 4 minutes :-) )
[15:19] <tumbleweed> fabrice_sp: heh
[15:20] <tumbleweed> you can have the upload then :)
[15:20] <fabrice_sp> :-) I just wanted to avoid double work ;-)
[15:20] <ari-tczew> fabrice_sp: wanna do some sponsorships for me?
[15:21] <fabrice_sp> ari-tczew, I'm looking at bug 623372
[15:21] <fabrice_sp> ;-)
[15:21] <ari-tczew> aha ok
[15:21] <tumbleweed> didn't my ack-sync lock it?
[15:21] <fabrice_sp> hmm, you too?
[15:22] <fabrice_sp> still in New in the ack-sync output
[15:22] <fabrice_sp> ack-sync throw me an exception, so it may be true
[15:22] <tumbleweed> you're riht, still new, but it assigned me (didn't it used to set in progress?)
[15:23] <fabrice_sp> should be, yes
[15:25] <fabrice_sp> IIRC, bdrung added it and also a control on status to avoid 2 people working on the same bug report at the same time
[15:26] <tumbleweed> fabrice_sp: I can't see any sign of In Progress in the source (or the bzr log)
[15:26] <fabrice_sp> bdrung perhaps forgot to commit the change, then
[15:26] <tumbleweed> I was going to ammend it to set Fix Committed before uploading, but determining which task we are looking at is quite complex
[15:26] <fabrice_sp> perhaps we should be using IRC to avoid clashes. Something like /me looking at #623358
[15:27] <tumbleweed> I normally unsubscribe sponsors and subscribe myself when starting to look, then reload the bug to be sure nobody else has
[15:27] <fabrice_sp> so do I
[15:27] <fabrice_sp> except with ack-sync
[15:33] <tumbleweed> fabrice_sp: looks like ack-sync locks by assignee - it must have been a race during assignment
[15:34] <fabrice_sp> tumbleweed, could be, yes. I'm updating also my ack-sync script, in case something has been fixed recently
[15:36] <tumbleweed> I've done a couple of tweaks, testing now.
[16:04] <shane2peru> ok, I followed this guide:  https://wiki.ubuntu.com/PackagingGuide/Python  and my deb comes out small, and only installed the control files, where did I go wrong??
[16:06] <shane2peru> Is this the right channel to get help with packaging?
[16:07] <tumbleweed> shane2peru: #ubuntu-packaging
[16:07] <shane2peru> tumbleweed, ok, thanks
[16:13] <ari-tczew> could someone check whether it can be synced or not? package xserver-xorg-video-sunleo
[16:13] <ari-tczew> https://launchpad.net/ubuntu/+source/xserver-xorg-video-sunleo
[16:13] <tumbleweed> ari-tczew: #ubuntu-x ?
[16:15] <ari-tczew> tumbleweed: I should ask doko, but he is not around here or #ubuntu-x
[16:16] <Laney> no
[16:16] <Laney> it's not a new upstream yet so the tarballs will still be different
[16:16] <Laney> → fakesync or merge
[16:17] <ari-tczew> Laney: I know that tarballs are different - I can read changelog... but there is a change - b-d on quilt - what's the reason?
[16:18] <Laney> what? You asked if it could be synced and I answered you
[16:18] <Laney> I don't know what the build dep is for either, the changelog should have been more verbose
[18:18] <Korbit> hello
[18:18] <Korbit> i'm trying to create my first ubuntu package
[18:19] <Korbit> since this is a java program i'm getting this error in pbuilder
[18:19] <Korbit> Can't exec "ant": No such file or directory at /usr/share/perl5/Debian/Debhelper/Dh_Lib.pm line 179.
[18:19] <Korbit> dh_auto_clean: ant clean failed to to execute: No such file or directory
[18:20] <Korbit> how can i say that this program needs ant to build?
[18:20] <Korbit> i tried this: Depends: ${shlibs:Depends}, ${misc:Depends}, ant
[18:20] <Korbit> in the debian/control file
[18:20] <Korbit> but it didn't work
[18:20] <Korbit> any help?
[18:20] <azeem> it's a Build-Depends
[18:21] <Korbit> ups, sorry for noobness
[18:22] <Korbit> didn't notice the build-depends variable
[18:24] <Korbit> trying to build the package again
[18:25] <Korbit> it's downloading java so i suppose it's working now =)
[18:26] <Korbit> azeem, Unpacking ant (from .../ant_1.7.1-4build1_all.deb) ...
[18:26] <Korbit> thanks man! =)
[18:28] <Korbit> i'm so stupid... obviously i have to say that i also need a java compiler
[18:31] <azeem> no problem
[18:31] <Korbit> which java compiler should i use?
[18:31] <azeem> the default one
[18:31] <Korbit> i should use a meta java compiler right?
[18:31] <azeem> didn't you say it downloaded one?
[18:32] <Korbit> instead of saying openjdk-jdk for example
[18:32] <azeem> why instead?
[18:32] <Korbit> i'll see the dependencies of ant
[18:32] <Korbit> because the binary package will depend on a java runtime
[18:33] <azeem> check its Suggests as well
[18:36] <Korbit> trying again
[18:41] <Korbit> azeem, it worked! =)
[18:41] <Korbit> i'm happy
[18:42] <Korbit> i'm going home now and when i arrive i'll learn how to get my package uploaded
[18:58] <canesin> anyone knows why a lucid build would resut in a dependancy on libav.* (>= 4:0.5.1-3) ????
[18:58] <canesin> If the distro version is libav* 4:0.5.1-1
[19:02] <Bachstelze> canesin: what package?
[19:03] <Bachstelze> probably a bad import from Debian
[19:05] <canesin> Bachstelze: I did the package .. imported it, it is paraview
[19:05] <canesin> I commited .. compiled ok in maverick..
[19:05] <canesin> but now I want to backport it..
[19:06] <canesin> I'm not a MOTU
[19:06] <canesin> I just filled the bug and so on
[19:09] <ari-tczew> canesin: give a bug number
[19:16]  * Jarvis tickles Laney 
[19:17]  * Laney roars
[19:17] <Jarvis> :D
[19:22] <bilalakhtar> tumbleweed: Thanks for that bug-buddy upload!
[19:23] <canesin> ??
[19:25] <canesin> bilalakhtar: How do I fix this ??
[19:25] <bilalakhtar> canesin: Please elaborate
[19:25] <canesin> bilalakhtar: It compiles, install, run and everything else fine in maverick
[19:26] <canesin> bilalakhtar: compile fine in lucid also...
[19:26] <canesin> bilalakhtar: but gives a dependency on libav.* (>= 4:0.5.1-3)  when installing
[19:26] <canesin> bilalakhtar: if I force it to install, it runs and do everything else perfect..
[19:27] <Bachstelze> canesin: give the bug number or an URL to your source package or something
[19:27] <canesin> bilalakhtar: how do I fix that dependency on libav* (>= 4:0.5.1-3) to (>= 4:0.5.1-1) to ask for a backport in lucid
[19:27] <Bachstelze> nobody here has a crystal ball
[19:28] <bilalakhtar> I agree with Bachstelze
[19:28] <canesin> https://launchpad.net/ubuntu/+source/paraview/3.8.1-1ubuntu1
[19:28] <bilalakhtar> canesin: It would be a lot better to ask your question in public rather than refer me!
[19:28] <canesin> sorry
[19:29] <fabrice_sp> canesin, is this a build dependency or a generated one for the binary package?
[19:29] <canesin> a generated one
[19:29] <canesin> only ocours when trying to install the generated deb in lucid
[19:29] <lfaraone> fabrice_sp: by the way, I saw your upload doing a libao4 transition, should I request a rebuild of my package in Debian as well?
[19:29] <canesin> used pbuilder-dist lucid build %.dsc
[19:30] <fabrice_sp> canesin, so if you rebuild the package, the right dependency should be picked
[19:30] <fabrice_sp> lfaraone, not sure: I'm parsing the NBS, and libao2 was one of those
[19:30] <canesin> That is why I'm asking here.. it does not.. it still shows  libav.* (>= 4:0.5.1-3)
[19:31] <fabrice_sp> lfaraone, Debian has libao4. Which package is it?
[19:31] <lfaraone> fabrice_sp: pianobar.
[19:32] <fabrice_sp> it's ok in Debian
[19:32] <fabrice_sp> canesin, why is there so many python2.5 stuff there?
[19:32] <bilalakhtar> Hi fabrice_sp seeing you here after a long time!
[19:32] <fabrice_sp> Hey bilalakhtar :-)
[19:33] <fabrice_sp> on holidays tomorrow, so you'll have to wait even longer ;-)
[19:34] <fabrice_sp> canesin, do you have a build log somewhere?
[19:34] <fabrice_sp> for Lucid
[19:35] <canesin> fabrice_sp, the program has a Python API..
[19:35] <canesin> fabrice_sp, I'm rebuilding it now.. sorry.. only "last_operation.log" ..
[19:35] <canesin> fabrice_sp, It is in 40% ....
[19:38] <fabrice_sp> canesin, take your time
[19:38] <fabrice_sp> even if it has a python API, why isn't 2.6 referenced?
[19:40] <canesin> fabrice_sp, I believe that in version 3.8.1 it is 2.6 .. but in olders no
[19:40] <canesin> this package was very outdated..
[19:41] <canesin> that was why I filled the FFe
[19:41] <fabrice_sp> yeah :-/
[19:41] <fabrice_sp> 3.8.1 still reference python2.5
[19:41] <fabrice_sp> at least, in the debian directory
[19:41] <canesin> ? .. in the build log it don't call it
[19:42] <fabrice_sp> you have it in paraview.lintian-overrides
[19:42] <fabrice_sp> debian/python-paraview.install
[19:42] <tumbleweed> oh dear I missed that. I sponsored it
[19:42] <fabrice_sp> and that's it
[19:42]  * tumbleweed assumes the python scripting is broken in it then?
[19:43] <bilalakhtar> tumbleweed: hey1
[19:43] <fabrice_sp> it seems so, yes
[19:43] <bilalakhtar> s/1/!/
[19:43] <bilalakhtar> tumbleweed: Thanks for that upload!
[19:43] <tumbleweed> bilalakhtar: np
[19:43] <fabrice_sp> s/1/?/
[19:44] <bilalakhtar> tumbleweed: And, what about the mail I sent you? Can you answer it now?
[19:44]  * tumbleweed sees some more SRU uploads from you first
[19:44] <bilalakhtar> tumbleweed: I have none right noq
[19:44] <bilalakhtar> *now
[19:44] <tumbleweed> oh, nm
[19:45] <bilalakhtar> tumbleweed: did you upload a few SRUs before becoming MOTU?
[19:45] <tumbleweed> no, but I probably should have.
[19:46] <bilalakhtar> tumbleweed: then?
[19:46] <bilalakhtar> so its a 'Wait some more time'
[19:46] <bilalakhtar> Thanks for the review tumbleweed !
[19:46] <tumbleweed> bilalakhtar: no, that is unrelated, my mistake, nm
[19:49] <bilalakhtar> tumbleweed: The problem is, I cannot find bugs which can be SRUed
[19:49] <bilalakhtar> I tried one, but pitti declined
[19:49] <tumbleweed> bilalakhtar: don't worry about that - you'll come across them soon enough
[19:49] <tumbleweed> http://launchpadlibrarian.net/54310767/buildlog_ubuntu-maverick-amd64.utouch-grail_1.0.10-0ubuntu1_FAILEDTOBUILD.txt.gz <- eh? sh: gcc: not found
[19:52] <Laney> don't worry about that
[19:52] <Laney> all builds are saying it
[19:52] <canesin> fabrice_sp: so what is the problem ??
[19:52] <canesin> fabrice_sp: It has something broken ?
[19:53] <fabrice_sp> canesin, did you posted a lucid build?
[19:53] <fabrice_sp> ohh, about python: yes
[19:53] <canesin> fabrice_sp: wierd, because I had run some python scripts to test
[19:53] <canesin> before upload
[19:54] <fabrice_sp> according to the install file, you should be missing debian/tmp/usr/lib/paraview/python2.5/lib-dynload/*.so files
[19:55] <fabrice_sp> but as it's building fine, the build system seems to find those files
[19:56] <canesin> ok...
[19:56] <canesin> so no problem in that ..
[19:56] <canesin> it runs
[19:56] <fabrice_sp> not sure
[19:57] <fabrice_sp> I'll build the package in a clean chroot, and see if the files are there or not
[19:59] <canesin> okay
[19:59] <canesin> and the dependency problem ?? how do I fix that ??
[20:00] <vish> could someone upload bug 395692 ? it has a debdiff waiting for a very long time...
[20:01] <vish> I asked Amaranth and he said upstream is unmaintained too
[20:06] <bilalakhtar> vish: You're better off asking it in #ubuntu-desktop
[20:53] <Korbit> hello everyone
[20:53] <Korbit> i've followed the motu videos by daniel holbach to create my first package
[20:53] <Korbit> now that pbuilder ran successfully, what should i do?
[20:54] <Bachstelze> Korbit: depends, what kind of package is it?
[20:54] <Korbit> i just packaged a java program that is not currently in the ubuntu reps
[20:55] <Korbit> basically, i download the program (in .zip) and changed it to a .tar.gz like daniel holbach says in the video
[20:55] <Bachstelze> if it's not in Ubuntu, it's probably not in Debian either, the "preferred" way is to get it into Debian, and let it merge in Ubuntu automatically
[20:56] <Korbit> is it similar to create a package for debian?
[20:56] <Bachstelze> yes
[20:56] <Bachstelze> obviously, the packaging format it the same ;)
[20:56] <Korbit> ok, i'll look into that on the debian website
[21:08] <Korbit> it's A LOT to read
[21:09] <Korbit> i'll just unzip the program and use it
[21:10] <Korbit> i'm not into reading all this stuff just to create a package now :(
[21:57] <fabrice_sp> canesin, the build failed because I don't have enough space on my HD. Sorry, I have to leave now
[22:07] <canesin> fabrice_sp :
[22:07] <canesin> Okey
[23:38] <Laney> sparc and ia64 finally died eh?
[23:38]  * Laney twiddles a script or two
[23:39] <directhex> aw, now i can't install ubuntu on our altix
[23:39] <Laney> nah, you just get the fun of rolling your own