[07:04] <dholbach> good morning
[10:25] <blackz> hi!
[10:25] <MohamedAlaa98> Can please someone explain me the error in this build? : https://launchpadlibrarian.net/117498874/buildlog_ubuntu-quantal-i386.gtk-nodoka-engine_0.7.5-0ubuntu1_FAILEDTOBUILD.txt.gz
[10:25] <tumbleweed> blackz: been a while
[10:26] <tumbleweed> MohamedAlaa98: looks like it was #including gtimer.h rather than glib.h
[10:27] <MohamedAlaa98> tumbleweed: I don't know but the build done succesfully on precise
[10:27] <blackz> tumbleweed: heh yeah..
[10:28] <MohamedAlaa98> tumbleweed: https://launchpad.net/~m-alaa8/+archive/ppa/+build/3804692
[10:29] <MohamedAlaa98> any ideas?
[10:29] <tumbleweed> MohamedAlaa98: something changed in gtk/glib?
[10:30] <MohamedAlaa98> tumbleweed: maybe the version in precise differs from quantal
[10:31] <MohamedAlaa98> tumbleweed: I don't know I came here for help
[10:31] <tumbleweed> I'd be very suprised if it didn't
[10:31] <geser> we had this same change also in precise but it was backed out again because it caused to much FTBFS and redone for quantal again
[10:32] <tumbleweed> there are quite a lot still to be fixed: http://udd.debian.org/cgi-bin/bts-usertags.cgi?tag=glib-single-include&user=pkg-gnome-maintainers%40lists.alioth.debian.org
[10:33] <MohamedAlaa98> that means it's a bug in nodoka engine itself?
[10:33] <geser> yes
[10:34] <geser> glib upstream decided that only glib.h should be included and nodoka-engine didn't adapt to it yet
[10:35] <MohamedAlaa98> Ok, Thank you very much geser, tumbleweed :)
[10:35] <Laney> it would be good to do some build log analysis from the rebuild test and file tagged bugs on this
[10:35] <Laney> quite a worthwhile bug fixing initiative
[12:53] <AnAnt> Hello, B2 should be released tonight ?
[13:04] <tumbleweed> yes
[13:20] <xnox> AnAnt: tonight for you, tomorrow morning for some.
[13:20] <xnox> 48 hours in a day after all =)
[13:23] <highvoltage> there's something very wrong in the tone of the ubuntu coc 2 draft.
[13:23] <highvoltage> it almost feels advarsarial or passive aggressive somehow, I can't pin the right word for it
[13:24] <MohamedAlaa98> tumbleweed: I'm a beginer here :) I want start with package upgrading from upstream :) can you please give me a simple work to do? and a little advice :) thank you :)
[13:24] <tumbleweed> MohamedAlaa98: now is not a useful time to be doing that
[13:24] <tumbleweed> we are releasing beta 2 today. We really aren't going around looking for things to update
[13:25] <MohamedAlaa98> Hmmm, what can I do now?
[13:25] <tumbleweed> highvoltage: yeah, I'm feeling that attitude from sabdfl in general, atm
[13:26] <tumbleweed> MohamedAlaa98: if you're a beginner, the most useful thing for you to do is learn some packaging skills. https://wiki.ubuntu.com/UbuntuDevelopment/BugFixingInitiative
[13:27] <tumbleweed> MohamedAlaa98: if you want to do something useful: find a neglected buggy package, and see if we can do something about it
[13:27] <highvoltage> tumbleweed: I've seen that for a long time so I guess it's something that I've accepted, but I liked the overall simplicity and positiveness of the old CoC, it set a stern and positive tone. the new one seems like a big regression. I can see how someone new to the project can read that and think "hmm, maybe this isn't for me"
[13:28] <tumbleweed> highvoltage: it certainly felt like something we should aspire to, in the past
[13:30]  * tumbleweed isn't finding this draft particularly adversarial, though (but still reading it)
[13:31] <MohamedAlaa98> tumbleweed: Ok :) thanks a lot
[13:34] <freeflying> dholbach: ping
[13:40] <highvoltage> tumbleweed: yeah that might have not been the right word, I'll have to think about it carefully before responsding
[13:41] <tumbleweed> highvoltage: I suspect it's at least partially due to the shortening of teh CoC
[13:42] <AnAnt> xnox: thanks
[13:46] <highvoltage> tumbleweed: ah the new one seemed quite longer to me
[13:48] <tumbleweed> highvoltage: I haven't diffed it for this revision. But in general, v2 added the leadership stuff, and removed cruft
[14:16] <dholbach> freeflying, pong
[14:17] <freeflying> dholbach: figured it out, thanks :)
[14:17] <dholbach> alright :)
[15:00] <geser> MohamedAlaa98: do you intent to try to fix the gtk-nodoka-engine FTBFS? I see that you reported a bug about it
[15:01] <MohamedAlaa98> geser: I just reported the bug and let them handle it
[15:01] <MohamedAlaa98> How can I fix it?
[15:03] <geser> in short: grab the source package, fix it (the fix is trivial), create a debdiff, attach it to your bug, add it to the sponsoring queue
[15:03] <Laney> geser: do you have a list?
[15:04]  * micahg hopes we don't end up with >1k build failures since it's so late in the cycle
[15:04] <MohamedAlaa98> hmm ok I'll try to fix it
[15:04] <geser> Laney: no, I just go through the FTBFS page for the rebuild and check for easy (time-wise) fixes
[15:04] <Laney> ok
[15:04] <micahg> current projections based on src pkg #s would be around 400
[15:05] <Laney> yeah, ideally we'd have had one earlier in the cycle
[15:05] <Laney> DIF?
[15:05] <micahg> AIUI we should've had 2 already :(
[15:05] <Laney> I remember discussing it in a session but not what was decided
[15:05] <geser> I try to get the quick fixes done first (better time usage) and focus on the time-consuming later (if I have available time left)
[15:06] <micahg> DIF or FF were the test points for the first round mention, neither happened
[15:06] <ogra_> micahg, did that planning take a DC move into account ?
[15:06] <micahg> ogra_: DIF would've been fine as it was long before the DC move
[15:07] <ogra_> oh, yeah
[15:07] <geser> MohamedAlaa98: if you have any questions or get stuck, just ask here
[15:07] <micahg> but it seems like a lot of the failures are gcc 4.7 and glib includes
[15:07] <micahg> at least the ones I've peeked at
[15:07] <Laney> that was an explicit reason for putting the glib include error back early in the cycle
[15:08] <Laney> we'd find them early and then be able to fix them, since the fix is so trivial
[15:08] <micahg> right, so that they would be fixed, but without a test rebuild they were blissfully forgotten about
[15:08] <Laney> sadly do
[15:08] <Laney> so
[15:09] <Laney> I suppose we could revert that and try again for R :-/
[15:10] <geser> do you think we will have a better success then?
[15:10] <Laney> depends if the effort is invested
[15:10] <Laney> we can leave it for a little while yet, see how we do now
[15:11] <ogra_> aarch64 might land in R, that would require a full archive rebuild in any case
[15:11] <geser> we would need an early test rebuild done to catch those but it's usually not done with the archive in flux due to auto-syncs (enough FTBFS from it)
[15:12] <ogra_> (no idea about the timeline here, just guessing)
[15:12] <cjwatson> I've got a month of +1 maintenance yet to use to attack these :)
[15:13]  * micahg hopefully has a month of +1 as well
[15:13] <cjwatson> ogra_: It wouldn't require rebuilding anything on existing architectures, surely
[15:13] <cjwatson> micahg: Oh good
[15:13] <geser> is there a quick switch to not have dch put UNRELEASED into the changelog or to have pass -D quantal everytime?
[15:13] <ogra_> cjwatson, well, but it would make sense to do it on all arches if we do it for aarch64 anyway
[15:14] <cjwatson> I vaguely remember that being controlled by DEBCHANGE_RELEASE_HEURISTIC
[15:14] <cjwatson> ogra_: We never have before for new ports
[15:14] <cjwatson> And a full rebuild is a big mirror hit
[15:14] <ogra_> just saying its an opportunity to do it in one go
[15:14]  * Laney never remembers what the release heuristics do
[15:15] <geser> ogra_: do you volunteer to do a rebuild upload of every package for it?
[15:15] <cjwatson> That isn't an opportunity, it's a risk :-)
[15:50] <obounaim> Please I need sponsoring here can any body review my merge proposal?
[15:52] <Laney> obounaim: is it really urgent?
[15:52] <Laney> if not, as long as it appears in http://reports.qa.ubuntu.com/reports/sponsoring/index.html it'll get looked at :-)
[15:53]  * Laney blinks at the swathe of misc:Depends branches there
[15:54] <obounaim> Laney, no it is not urgent but It has a while in there
[15:55] <Laney> ah, well I see them. Somebody will hopefully get to them soon
[15:55] <obounaim> Laney, yes hopefully
[15:56] <Laney> hmm, I should get on the pilot schedule really
[15:56] <Laney> dholbach: ^ ;-)
[15:56] <dholbach> laney: with pleasure
[15:56] <TheLordOfTime> how can i force apt-get to install dependencies?
[15:56] <xnox> Laney: yeah. But they are good to teach about packaging. E.g. mispelled (LP: #) or forgotten patches (direct modifications) or not updated maintainer field.
[15:56] <TheLordOfTime> its not installing the openjdk-6-jre dependencies, so...
[15:56] <Laney> xnox: I understand the idea.
[15:57] <TheLordOfTime> is there an argument i can provide to *force* dependency resolution?
[15:59] <dholbach> laney: added yourself - feel free to move it to some other day if that suits you better
[16:00] <Laney> thanking you
[16:01] <micahg> thelordOfTime: umm, there's -f, but that won't work if there's a real problem
[16:01] <TheLordOfTime> micahg:  lemme pastebin the errors, perhaps there's something i'm missing...
[16:02] <TheLordOfTime> or something dreadfully wrong with Precise
[16:03] <TheLordOfTime> micahg:  http://paste.ubuntu.com/1230639/  <-- the errors i'm getting
[16:03] <TheLordOfTime> there's also a pinning error according to apt, but i can't find it  :/
[16:04] <TheLordOfTime> and it always shows up.
[16:04] <micahg> apt-cache policy | grep ^0 ?
[16:05] <TheLordOfTime> oh i see where it is
[16:05] <TheLordOfTime> one moment
[16:05] <micahg> thelordOfTime: you can use -o Debug::pkgProblemResolver=true to see what it causing the issue
[16:07] <TheLordOfTime> micahg:  well, the apt pinning issue is unknown, its still showing up, and the grepped line from your command is not useful, just says this: W: No priority (or zero) specified for pin
[16:08] <micahg> well, you can look over apt-cache policy to see if anything is unusua;
[16:09] <TheLordOfTime> and now i'm getting update manager crashes because the "package system is broken"
[16:09] <TheLordOfTime> what hell is happening here...?
[16:11] <TheLordOfTime> ...
[16:11] <TheLordOfTime> oh wait a sec
[16:13] <MohamedAlaa98> Hello guys :) I've a notice
[16:13] <MohamedAlaa98> in this page: https://wiki.ubuntu.com/PackagingGuide/Recipes/PackageUpdate
[16:13] <TheLordOfTime> well, that was... different...
[16:14] <TheLordOfTime> micahg:  apparently someone tried to install a package here that broke everything
[16:14] <TheLordOfTime> and apt was whining because on this system, there were apt pins for each repo (main, -updates, -security, etc.)
[16:14] <TheLordOfTime> *shrugs*
[16:14] <MohamedAlaa98> you forgot to add launchpad building part :)
[16:14] <TheLordOfTime> removing the apt pinning prefs fixed that issue, and purging the attempted-to-install package fixed that issue
[16:15] <TheLordOfTime> time for sourcebuilds :P
[16:17] <MohamedAlaa98> sorry for interrupting
[16:18] <TheLordOfTime> no problem, was just mostly me griping about apt not working and something related to apt not resolving dependencies
[16:18] <TheLordOfTime> carry on, dude :)
[16:19] <MohamedAlaa98> :D
[16:20] <MohamedAlaa98> did you realize what i said?
[16:26] <MohamedAlaa98> hello?
[16:27]  * dholbach hugs laney
[16:27]  * dholbach hugs laney
[16:27]  * dholbach hugs laney
[16:27]  * dholbach hugs laney
[16:27]  * dholbach hugs laney
[16:28]  * MohamedAlaa98 hugs laney too :)
[16:29] <Laney> :-)
[16:29]  * Laney hugs dholbach 
[16:31] <ogra_> was that a hug for every donated dollar ?
[16:31]  * MohamedAlaa98 is awaiting for anyone to respond him
[16:35] <Laney> is it just me that can't boot recent dailies in vbox?
[16:35] <Laney> 5 minutes to get a grub selection, 5 more minutes to see plymouth, 5 minutes later that goes away to show me the console with loads of service stopping, then it goes black
[16:41] <Laney> 12.04.1 works well
[16:56] <MohamedAlaa98> sorry for disconnecting
[16:58] <MohamedAlaa98> I've done a fix, but I can't understad this step: http://developer.ubuntu.com/packaging/html/fixing-a-bug-example.html#getting-the-fix-included any ideas?
[16:59] <MohamedAlaa98> tumbleweed
[17:02] <MohamedAlaa98> sorrfor disconnecting
[17:02] <MohamedAlaa98> *sorry for
[17:02] <MohamedAlaa98> any ideas?
[17:03] <tumbleweed> MohamedAlaa98: you haven't said what the problem is
[17:04] <MohamedAlaa98> oh, connection problems
[17:04] <MohamedAlaa98> I've done a fix, but I can't understad this step: http://developer.ubuntu.com/packaging/html/fixing-a-bug-example.html#getting-the-fix-included what should I do?
[17:04] <tumbleweed> you haven't said what you don't understand
[17:04] <tumbleweed> also, please don't highlite me if you are just looking for someone to ansewr a question
[17:04] <MohamedAlaa98> ok, sorry
[17:05] <MohamedAlaa98> I can't understand how to get fix included
[17:05] <mitya57> MohamedAlaa98: that section is mostly for submitting the patch to debian/upstream
[17:05] <tumbleweed> MohamedAlaa98: what did you fix?
[17:05] <mitya57> MohamedAlaa98: Debian has already a bug report: http://bugs.debian.org/665549
[17:06] <mitya57> you can submit the patch there
[17:06] <MohamedAlaa98> homepage missing staff
[17:06] <mitya57> ah, sorry, you are talking about another thing
[17:06] <tumbleweed> MohamedAlaa98: the missing homepage bugs listed on that wiki page are ubuntu-only packages
[17:06] <MohamedAlaa98> mitya57 np :)
[17:06] <tumbleweed> they aren't in debian
[17:06] <MohamedAlaa98> yes i know :)
[17:07] <tumbleweed> so, follow the link to the ubuntu sponsoring process
[17:07] <MohamedAlaa98> okay
[17:10] <MohamedAlaa98> oops there's a added homepage in quantal https://code.launchpad.net/ubuntu/+source/z3c.pt
[17:12] <MohamedAlaa98> should I push my fix?
[17:12] <tumbleweed> if it's already done, I don't see any point
[17:13] <MohamedAlaa98> :( but you haven't marked it fixed here: https://wiki.ubuntu.com/UbuntuDevelopment/BugFixingInitiative
[17:13] <tumbleweed> it's not *me* who hasn't marked it there :)
[17:13] <tumbleweed> obounaim: ^^
[17:14]  * MohamedAlaa98 want's to cry :(
[17:15] <tumbleweed> well, now you know what to do :)
[17:17] <obounaim> MohamedAlaa98, refresh your browser.
[17:17] <MohamedAlaa98_> browser?
[17:17] <MohamedAlaa98_> what do you mean?
[17:18] <obounaim> MohamedAlaa98, I have marked them as fix proposed
[17:18] <obounaim> https://wiki.ubuntu.com/UbuntuDevelopment/BugFixingInitiative
[17:20] <MohamedAlaa98> obounaim: can you please repost what you said?
[17:21] <MohamedAlaa98> obounaim: sorry network problems.
[17:22] <obounaim> MohamedAlaa98, Concerning the bugs listed in https://wiki.ubuntu.com/UbuntuDevelopment/BugFixingInitiative that I have fixed they are now marked as fix proposed
[17:22] <MohamedAlaa98> obounaim: ok :)
[17:23] <MohamedAlaa98> obounaim: it's my mistake I should review all sections of a package before doing something
[17:39] <tumbleweed> MohamedAlaa98: I think it's just bad luck (and something that will happen when everyone works from the top of a list)
[17:40] <MohamedAlaa98> :D
[18:05] <MohamedAlaa98> tumbleweed: obounaim hasn't let anythng in this page t fix
[18:05] <MohamedAlaa98> *to
[18:05] <MohamedAlaa98> I mean No homepage field bugs
[18:06] <MohamedAlaa98> where I can find more?
[18:06] <MohamedAlaa98> *can i
[18:06] <jtaylor> MohamedAlaa98: you can check this list for useful syncs: http://qa.ubuntuwire.org/multidistrotools/universe.html#outdatedinB
[18:07] <MohamedAlaa98> jtaylor: ok, thanks