[02:02] <micahg> YokoZar: wine1.4 is the last gcc-4.5 dependency that we're keeping in quantal, any chance we can switch it to something else?
[02:03] <YokoZar> micahg: I will investigate gcc-4.7, but 4.6 is known bad
[02:03]  * micahg will file a tracking bug for it
[02:07] <YokoZar> http://wiki.winehq.org/GccVersions  doesn't mention 4.7 yet
[02:08] <micahg> YokoZar: Debian seems to have built 1.4 with gcc-4.7
[02:08] <YokoZar> micahg: Yes, it will build, but that doesn't mean subtle stuff like copy protection didn't break
[02:08] <micahg> hrm, I might have been mistaken, we seem blocked by the same thing as Debian (parts of gcc-4.4 require gcc-4.5), I'll have to chat with doko about that
[02:22] <paultag> Anyone know where I can find zulcss?
[02:22] <paultag> zul: Ah, there you are. Are you around?
[02:24] <paultag> zul: OK, since you're likely AFK, here's what's up - someone filed an ITP in Debian for Melange (the Cream app, not OpenStack), and someone else mentioned there's already Melange in Ubuntu. Would you be open to the following: - rename (in Debian and Ubuntu) to melange-openstack
[02:24] <paultag> zul: and in Ubuntu, introduce a new metapackage, melange, which transitions old deps to melange-openstack
[02:25] <paultag> zul: if you'd like to get melange in Debian, as a token of my thanks for clearing the namespace (this ITP would take melange-cream or something), I'd be happy to sponsor your work on this package in Debian
[02:25] <paultag> if you'd like that, of course.
[02:27] <micahg> YokoZar: can I give you the wine task on the gcc4.5 bug?
[02:33] <ScottK> paultag: You can't reuse the name melange in Ubuntu until after 14.10.
[02:34] <paultag> ScottK: If you re-read what I was thinking, I didn't suggest using it
[02:34] <paultag> ScottK: if he's already using melange, moving it to melange-openstack, and dropping a transitional package will be fine
[02:34] <paultag> the ITP would be for melange-cream or something
[02:34] <ScottK> The transitional package needs to stay through 14.04
[02:34] <paultag> that's fine
[02:35] <paultag> it'd be Ubuntu-only, too
[02:35] <paultag> I'd much rather see no one use the name
[02:35] <micahg> ScottK: he's saying that the new package won't be using that name either :)
[02:35] <paultag> it's very generic -- and also google-melange :)
[02:35] <paultag> micahg++ :)
[02:35] <ScottK> I was confused by him callling a transitional package a metapackage.  It's not.
[02:35] <paultag> transitional metapackage.
[02:35] <paultag> whatever
[02:36] <ScottK> Transitional package.
[02:36] <ScottK> Metapackage is something entirely different.
[02:36] <paultag> whatever, we're getting wrapped up with something silly, you can lecture me later :)
[02:36] <paultag> but I conceed the point
[02:36] <paultag> erm, conceded
[02:37] <lifeless> thats like saying my car is a bus because they are both road vehicles ;)
[02:37] <ScottK> Right, just saying why I got confused.
[02:37] <paultag> Ah, sorry. That's my fault, ScottK.
[02:38] <ScottK> BTW, did your man who wanted to use Git get straightened out?
[02:38] <paultag> ScottK: he hasn't got back to me over IRC. What did you end up doing with the app?
[02:38] <paultag> application to join*
[02:41] <ScottK> Nothing yet.
[02:41] <ScottK> I told him he could use git-svn if he wanted, but DPMT stuff needed to get into the DPMT svn repo somehow.
[02:41] <ScottK> Then I didn't hear back.
[02:41] <paultag> ACK
[02:42] <paultag> I think he's .de, so might need a TZ-Round-trip
[02:44] <paultag> ScottK: sorry if I came off as brash earler on there, I've had a pretty rough day. I just re-read it, and I was out of line. Sorry dude.
[02:44] <ScottK> No problem.
[02:56] <YokoZar> micahg: Yeah
[02:56] <micahg> YokoZar: done, thanks
[02:57] <YokoZar> micahg: by the way, first response on wine-devel is that the issues that broke wine in 4.6 are still in 4.7
[02:57] <micahg> YokoZar: is rolling back to gcc-4.4 an option?
[02:58] <YokoZar> micahg: also no, GCC 4.4 is broken too
[02:58] <YokoZar> (see wiki page)
[02:58] <micahg> YokoZar: awesome :), any chance we can get one of the upstreams to fix something before quantal release?
[02:59] <YokoZar> micahg: GCC maybe, but I don't know how difficult that sort of change is.  Wine has test cases to demonstrate it, but unfortunately they're really huge (on the order of run this 1.2 GB proprietary app and see it break), so probably aren't in GCC process
[03:00] <micahg> YokoZar: can you get infinity a test case?
[14:02] <Blazemore|Work> I'm trying to package some code and put it in a PPA but I'm very new at this. I'm following the instructions here (http://developer.ubuntu.com/packaging/html/packaging-new-software.html) but bzr builddeb fails because no key is found. I have a PGP private key, but it seems to be ignoring it
[14:02] <Blazemore|Work> The key was generated on another machine, but it is my key
[14:11] <tumbleweed> Blazemore|Work: if the package is something that'd be useful for many others, you should aim to get it into Debian eventually, rather than just having it in a PPA
[14:11] <tumbleweed> but back to your question
[14:11] <Blazemore|Work> Yes, debs first
[14:11] <tumbleweed> you need to have the private key on the machine you are working on
[14:12] <tumbleweed> gpg --list-secret-keys must list it
[14:12] <Blazemore|Work> I do, it is in ~/.gnupg/secring.gpg
[14:12] <Blazemore|Work> debuild -k works
[14:12] <Blazemore|Work> Build bzr builddeb doesn't support that
[14:12] <tumbleweed> does it have an ID with the same e-mail address that you used in the changelog?
[14:12] <Blazemore|Work> How do I change the changelog?
[14:12] <tumbleweed> bzr builddeb does, try -- -kFOOBAR
[14:13] <tumbleweed> usually with dch
[14:13] <Blazemore|Work> bzr builddeb -k3A460FC1
[14:13] <Blazemore|Work> bzr: ERROR: no such option: -k
[14:13] <tumbleweed> but you can use any text editor if you don't want to be helped
[14:13] <tumbleweed> you left out the --
[14:13] <Blazemore|Work> Nothing to see here
[14:13] <Blazemore|Work> Thanks
[14:14] <Blazemore|Work> See, I don't really understand the process. I was under the impression you uploaded source files to Launchpad, and it built them for you. But the closest I can find to that is Suse Build Service
[14:14] <tumbleweed> correct. you upload the sources to LP and it builds them for you
[14:14] <tumbleweed> you need to tell it how to, of course
[14:14] <Blazemore|Work> I'm happy to just have a deb file I can distribute myself, but a nightly build system pulling from git would be amazing
[14:14] <Blazemore|Work> sure
[14:15] <tumbleweed> LP can do that
[14:15] <Blazemore|Work> Is it easy?
[14:15] <tumbleweed> that's hard question to answer
[14:15] <tumbleweed> it depends on how easy packaging your application is
[14:15] <Blazemore|Work> Very, very easy. no weird build dependencies
[14:15] <tumbleweed> producing a good daily build is certainly more involved than a once-off package
[14:16] <Blazemore|Work> Only one runtime dependency that doesn't ship with Debian and Ubuntu already
[14:16] <tumbleweed> but it's not particularly hard, either
[14:16] <Blazemore|Work> I'm happy to produce packages manually every time a stable version is manually released. Once I feel more comfortable with the whole packaging process, I'll look at a more automatic process
[14:17] <tumbleweed> yeah, start by getting comfortable with packaging it
[14:21] <blizzkid> hi ppl, I'm trying to package for the first time, but now run in to trouble when running "pbuilder build ../*.dsc". I get the error "gpgv: Can't check signature: public key not found". Tried running both as root and with sudo. Same error every time. Googled, but non of the suggestions found, solve the issue. Any ideas?
[14:24] <geser> blizzkid: does it fail with this message? I'd except it's a non-fatal error and you can ignore it for your own packages
[14:25] <tumbleweed> blizzkid: more output would certainly be helpful
[14:27] <blizzkid> tumbleweed, geser: see http://pastebin.com/GgkyMh15
[14:28] <blizzkid> pbuilder.log is in http://pastebin.com/m9KAaBSE
[14:29] <tumbleweed> your error there is:
[14:29] <tumbleweed> configure: error: ./configure failed for lib/dnscore
[14:29] <tumbleweed> dh_auto_configure: ./configure --build=i686-linux-gnu --prefix=/usr --includedir=${prefix}/include --mandir=${prefix}/share/man --infodir=${prefix}/share/info --sysconfdir=/etc --localstatedir=/var --libexecdir=${prefix}/lib/yadifa --disable-maintainer-mode --disable-dependency-tracking returned exit code 1
[14:29] <tumbleweed> and helpfully the second log includes the config.log
[14:32] <geser> "checking for SSL_library_init in -lssl... no" -> you're missing a build-dependency on libssl-dev (if the license allows linking with OpenSSL, didn't check)
[14:32] <tumbleweed> I'm assuming the cause of failure is:
[14:32] <tumbleweed> SSL is required by this setup ...
[14:32] <tumbleweed> checking if SSL is available... no
[14:32] <blizzkid> geser: that's weird... saw that the first time; installed libssl-dev and didn't see that again
[14:32] <Blazemore|Work> OK I put the package in the PPA, but I never logged into Launchpad. How does it know it's me?
[14:33] <paultag> Blazemore|Work: GPG keys :)
[14:33] <Blazemore|Work> My key isn't on Launchpad
[14:33] <paultag> then it should have been rejected.
[14:33] <Blazemore|Work> Not this key, or any key on my system
[14:33] <Blazemore|Work> You're right, it should have. How long does it take to appear in the PPA? I did it about 10 minutes ago
[14:33] <paultag> anyone can upload, Blazemore|Work, but it will only get accepted if it's signed with an authorized user's GPG key
[14:33] <paultag> Blazemore|Work: It'll email you. The awesome folks in #launchpad might be able to help more
[14:33] <Blazemore|Work> OK
[14:34] <tumbleweed> Blazemore|Work: but basically, if your key isn't in launchpad, then what are you expecting?
[14:34] <tumbleweed> it certainly won't accept the upload
[14:34] <paultag> tumbleweed: he'll figure it out :)
[14:34] <Blazemore|Work> I was wondering if it would prompt me for a password
[14:34] <paultag> tumbleweed: also, hi :)
[14:34] <Blazemore|Work> I've got it, don't worry
[14:34] <tumbleweed> paultag: hi
[14:35] <blizzkid> geser: how should I solve it?
[14:35] <blizzkid> since I do have libssl-dev installed (or should I put a depend in the control file?)
[14:35] <geser> blizzkid: you need to add "libssl-dev" to the Build-Depends line in your debian/control file (so that pbuilder know it has to install that package when building your package)
[14:36] <blizzkid> geser: ok, I'll try again with that one added
[14:36] <geser> pbuilder uses a clean chroot, so what you do outside (package installs) don't have an effect on the pbuilder
[14:37] <blizzkid> geser: I see.
[14:37] <Blazemore|Work> The thing is, I have now added my key, but dput says "Package has already been uploaded to ppa on ppa.launchpad.net" when I try to upload it with the proper credentials
[14:37] <geser> dput -f
[14:38] <Blazemore|Work> OK it was client side iving that error? Not Launchpad?
[14:38] <geser> yes
[14:38] <paultag> Blazemore|Work: it's just using FTP in this case
[14:38] <blizzkid> geser: added it, but still get the ss
[14:38] <blizzkid> checking ssl... no
[14:38] <paultag> and it sees the file is already on the server, so it bails out
[14:39] <Blazemore|Work> It is still giving me an error. I have multiple email addresses on the same key, I think they are "subkeys" in gpg but I don't know how that works
[14:39] <geser> dput creates an $dsc.upload file after uploading, so it doesn't try to upload it again unless you forces it (-f), it doesn't know if the archive software did accept or reject that upload
[14:39] <Blazemore|Work> I have my personal, and my work, emails
[14:39] <Blazemore|Work> And the error is on my work one, whereas only my personal one is authorised on lp
[14:39] <Blazemore|Work> This key is not certified with a trusted signature!
[14:41] <Blazemore|Work> For some reason my own key was not signed by me. I fixed it
[14:41] <Blazemore|Work> This is what happens when you use the same key on multiple devices
[14:43] <blizzkid> geser: nm, had to add it in the .dsc too
[14:43] <Blazemore|Work> Where do I edit the distroseries?
[14:43] <tumbleweed> Blazemore|Work: you're editing the .dsc by hand?
[14:43] <tumbleweed> err blizzkid
[14:43] <tumbleweed> too many bl<tab> people today
[14:43] <Blazemore|Work> tumbleweed: Apparently
[14:43] <Blazemore|Work> Oh OK
[14:44] <blizzkid> tumbleweed: for this one, yeah. The only change was the dep.
[14:44] <tumbleweed> blizzkid: edit debian/control; debuild -S
[14:45] <blizzkid> tumbleweed: will do so in the second run :) (first one was trial, now I'll create a decent package)
[14:45] <Blazemore|Work> Unable to find distroseries: unstable
[14:46] <blizzkid> what files are needed to upload to lp for possible inclusion in ubuntu?
[14:47] <tumbleweed> Blazemore|Work: LP PPAs build for Ubuntu not Debian
[14:48] <tumbleweed> blizzkid: I don't know quite how to answer that, so instead I'll point you at https://wiki.ubuntu.com/UbuntuDevelopment/NewPackages
[14:49] <Blazemore|Work> Yeah I fixed it tumbleweed . I think maybe it's working now. I got no gpg errors, and Launchpad didn't immediately email me
[14:49] <Blazemore|Work> How long should I expect to wait? It takes seconds to build
[14:50] <paultag> Blazemore|Work: https://launchpad.net/builders/ ← shows how swamped the builders are
[14:50] <tumbleweed> Blazemore|Work: you should get an e-mail within 5 minutes of uploading
[14:50] <Blazemore|Work> Great
[14:51] <tumbleweed> the cron job only runs every 5 minutes
[14:51] <paultag> Blazemore|Work: the 64bit queue looks ~ 1:20 i386 looks like 1:10
[14:57] <paultag> zul: Did you happen to catch my messages last night?
[14:57] <zul> paultag: nope i was probably sleeping
[14:57] <paultag> zul: I'll pastebin them -- I figured you'd have the backscroll
[14:57] <paultag> one sec.
[14:58] <paultag> zul: http://paste.debian.net/180486/
[14:58] <paultag> zul: please note that ScottK was correct to point out that I mean to say transitional package, not metapackage.
[14:58] <zul> paultag: there was an open bug to remove melange from ubuntu so i dont know where that is
[14:59] <paultag> zul: Oh there was?
[14:59] <paultag> LP: #1017609
[14:59] <zul> https://bugs.launchpad.net/ubuntu/+source/melange/+bug/1017609
[14:59] <paultag> zul: ACK
[14:59] <paultag> zul: is melange going to ever live again in some form?
[15:00] <paultag> (more exactly, under the `melange' name in Ubuntu)
[15:00] <paultag> Ah, it says there it's deprecated.
[15:00] <paultag> Fantastic. Thanks for your time zul.
[15:00]  * paultag warms up the ole' MUA
[15:01] <zul> paultag:  not reallly
[19:54] <blizzkid> lo all. call me stupid, but how do I file a "needs packaging" bug in lp?
[19:54] <blizzkid> I just can't seem to find the correct link
[19:55] <tumbleweed> blizzkid: I don't know if anyone really looks at needs packaging bugs
[19:55] <tumbleweed> https://wiki.ubuntu.com/UbuntuDevelopment/NewPackages
[19:55] <blizzkid> tumbleweed: I quote from that exact page: "To get a package into Ubuntu, please file a bug in Launchpad and make sure it has the tag needs-packaging."
[19:55] <blizzkid> I read it before I asked :)
[19:56] <highvoltage> tumbleweed: that's something that might be worth while discussing at a motu meeting, perhaps most of them should be closed in favor of ITP/RFP bugs in Debian instead
[19:56] <tumbleweed> blizzkid: no, that page actually says: go through debian :)
[19:57] <blizzkid> tumbleweed: read the second paragraph under "Requesting a new package for Ubuntu" ;-)
[19:58] <blizzkid> btw, going through Debian would suit me fine, but the docs are confusing me
[19:59] <blizzkid> I want to package for Ubuntu, so I do, and when I finally have a package, I have to redo everything because Debian does things differently?
[19:59] <blizzkid> Is there an easy way to go from what I have now (ppa is ok) to a Debian-ready package?
[19:59] <blizzkid> brb
[20:03] <tumbleweed> blizzkid: there's a good reason why it suggests going through Debina first
[20:04] <tumbleweed> highvoltage: agendaify it!
[20:04] <tumbleweed> blizzkid: if you don't say how the docs are confusing you, we can't help
[20:04] <tumbleweed> and no, everything is not different in Debian
[20:04] <tumbleweed> >70% of Ubuntu is unmodified Debian
[20:30] <blizzkid> tumbleweed: confusing: same doc tells me to file a needs-packaging bug, and tells you to go through debian.
[20:30] <blizzkid> All ubuntu packaging docs I read on the ubuntu wiki, told me the steps I took now
[20:30] <blizzkid> being: debuild -S dput
[20:31] <blizzkid> so I guess after debuild -S I have to do something to get a Debianized package apart from an Ubuntu one
[20:31] <blizzkid> don't get me wrong, I am in no way upset. I'm just completely lost in translation :)
[20:33] <blizzkid> and btw, I know Ubuntu is largely Debian, but packaging is quite different in details
[20:33] <blizzkid> (as far as I know)
[20:35] <tumbleweed> no, it's the same
[20:35] <tumbleweed> some procedures are different, that' sabout it
[20:47] <blizzkid> tumbleweed: ok, so any short introduction/manual to help me get from my Ubuntu package to a Debian one and get it in Debian?
[21:01] <alucardni> blizzkid: This may help you --> https://wiki.ubuntu.com/Debian/ForUbuntuDevelopers
[21:03] <blizzkid> thx a million alucardni that looks quite good indeed
[21:13] <nigelb> Isn't there a way to mount my current home inside a pbuilder env? I forget how :/
[21:14] <jtaylor> --bindmounts
[21:17] <nigelb> thanks jtaylor :)