[08:09] <dholbach> good morning
[08:10] <geser> good morning
[08:10] <ajmitch> hello dholbach, geser
[08:10] <geser> good evening ajmitch
[08:10] <dholbach> hey ajmitch, hi geser
[11:55] <Daviey> jdstrand: Hey, Is anyone other than you handling source NEW?
[13:57] <jdstrand> Daviey: the short answer is 'yes', but the longer answer is 'in practice, not really'. Friday is my aa day and I was off last friday. I was already a bit behind. it and mir audits are on my list of things to catch up on this week
[14:00] <Daviey> jdstrand: roaksoax just uploaded 6 packages for your delight :)
[14:01] <Daviey> jdstrand: I uploaded a package intended for universe last night.. You might question why it's of type native.. it was intentional.
[14:02] <jdstrand> Daviey: ok
[14:37] <geser> l3on: re your apt SRU question: it looks like apt got copied from lucid-security to lucid-updates, so you can pick either one but target your upload to lucid-proposed with version 0.7.25.3ubuntu9.10
[14:38] <l3on> ok, thanks geser :)
[14:46] <dholbach> https://wiki.ubuntu.com/UbuntuDeveloperWeek starting in 14 minutes in #ubuntu-classroom
[15:38] <aboudreault> If I have a directory libXYZ/, which contains the source files + the debian directory. Can I generate a orig.tar.gz on the fly of that libXYZ? which would remove the debian direcoty
[15:39] <l3on> geser, If you're still around...
[15:39] <tumbleweed> aboudreault: you don't need to worry about the debian directory if you use source format 3.0
[15:40] <l3on> but have I to push branch over lp:~me/ubuntu/lucid/apt/sru-XXXX ?
[15:40] <l3on> and not lucid-updates, right ?
[15:40] <directhex> aboudreault, not necessarily in the way you mean. you don't know for sure whether there are any patches to the source or not
[15:41] <directhex> not in the general case, anyway
[15:46] <aboudreault> Yes I use source format 3.0 but quilt is complaining about the missing orig
[15:47] <tumbleweed> why don't you have one?
[15:47] <aboudreault> because everything is in git
[15:48] <aboudreault> directhex, pkg-source: error: can't build with source format '3.0 (quilt)': no orig.tar file found
[15:48] <tumbleweed> so the upsstream doesn't release any tarball at all?
[15:48] <tumbleweed> then you can generate one yourself, but why does it have to be done on the fly?
[15:48] <aboudreault> it's a trunk-snapshot, I do not want to mess with that, I would to build it as it is
[15:48] <tumbleweed> ah, daily build?
[15:48] <aboudreault> kind of
[15:49] <aboudreault> but it fails to build when I call debuild -S -sd (or -sa, or -S only)
[15:49] <tumbleweed> yes, 3.0 (quilt) does require an upstream tarball
[15:50] <aboudreault> I also see that all git repository now includes the software sources
[15:50] <aboudreault> ha
[15:50] <tumbleweed> how often are you wanting to build packages from trunk?
[15:50] <directhex> aboudreault, i never said debsrc 3 would help
[15:50] <tumbleweed> if it's just the occasional snapshot, a rule in debian/rules for building an orig tarball would be handy
[15:50] <aboudreault> tumbleweed, I just want to build it now.
[15:51] <tumbleweed> then just create an orig tarball by hand?
[15:52] <tumbleweed> git archive ../foo.orig.tar.gz would probably suffice
[15:55] <aboudreault> trying the git archive
[16:41] <micahg> tumbleweed: I found a case where seeded-in-ubuntu lies, synaptic
[17:46] <jtaylor> during freeze I can still upload unseeded stuff?
[17:47] <micahg> jtaylor: well, stuff that's not on any images
[17:47] <jtaylor> micahg: isn't that the meaning of seeded?
[17:47] <micahg> jtaylor: well, sort of
[17:49] <micahg> there can be a supported seed which isn't subject to the alpha freezes
[17:51] <micahg> or even the beta freezes for that matter, only final freeze
[18:04] <achiang> hello, is it ok to requestsync from debian/unstable, or should i really wait until it hits testing?
[18:05] <achiang> (for a package in universe, natch)
[18:06] <achiang> ah, i guess it will be in testing soonish: Too young, only 3 of 10 days old
[18:08] <micahg> achiang: it's a new package, so unless you need it for something right now, I'd suggest waiting until it migrates
[18:09] <micahg> of course, that's also granting you have over 2 weeks until Feature Freeze :)
[18:09] <achiang> micahg: ok, i'm just concerned that i'll miss the cutoff date, since we're past DIF, but it's unclear to me the true freeze date after which syncs are disallowed (without justification)
[18:10] <achiang> micahg: ah, feature freeze is the date i care about?
[18:10] <micahg> achiang: Feature Freeze, Feb 16
[18:10] <achiang> micahg: ok, thanks
[18:10] <achiang> micahg: i'll wait until it his testing then
[18:10] <achiang> thanks
[19:06] <oier> hi, when uploading to revu I get "Directory to upload to does not exist.", any idea on what is going on?
[19:07] <oier> I am reuploading a package, so the page exists
[19:12] <oier> the package is called indicator-bug
[19:13] <oier> I would appreciate your help
[19:35] <geser> l3on: you should push to lp:~me/ubuntu/lucid-proposed/apt/sru-XXXX (the same target distribution as the upload it for)
[19:47] <tumbleweed> micahg: is that maybe due to the build failures?
[19:55] <aboudreault> can we tell pbuilder somehow to fully use all my CPUs when compiling?
[19:56] <jtaylor> that must be told to the package not pbuilder
[19:56] <jtaylor> how depends on the package
[19:56] <jtaylor> + setting DEB_BUILD_OPTIONS
[20:01] <aboudreault> jtaylor, ok. I have to modify the debian/rules accordingly... but I don't have to modify the original Makefile, right?
[20:01] <jtaylor> depends
[20:01] <jtaylor> if the original makefile supports parallel builds
[20:02] <aboudreault> ok
[21:33] <aboudreault> I see 5-6 X.symbols file in the debian dir. (symboles.amd64 etc..) How are they generated?
[21:35] <jtaylor> dpkg-gensymbols
[21:35] <jtaylor> or the kde helper tools
[21:35] <jtaylor> http://pkg-kde.alioth.debian.org/symbolfiles.html
[21:37] <aboudreault> jtaylor, but dpkg-gensymbols are generated during the build, aren't they?
[21:38] <aboudreault> I see the symbols file in the repo. why are they kept.
[21:38] <jtaylor> no they are generated by the packager
[21:39] <jtaylor> they are used to minimize the version dependencies of rdepends and a very coarse check for abi breakage
[21:42] <aboudreault> ok, will read the doc of dpkg-gensymbols. thanks.
[21:43] <jtaylor> are you packaging a C or C++ library?
[21:43] <aboudreault> C++
[21:43] <jtaylor> :/
[21:44] <jtaylor> symbol files and c++ are a very ugly combination
[21:44] <aboudreault> well... it's C/C++ a lot.
[21:57] <micahg> tumbleweed: idk, if it is, that's bad IMHO
[21:57] <micahg> should I file a bug?