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