[02:08] <ScottL> sanity check:
[02:09] <ScottL> i want to create an SRU for a qjackctl bug that causes renamed ports to not be connected in qjackctl
[02:09] <ScottL> https://bugs.launchpad.net/ubuntu/+source/qjackctl/+bug/490436
[02:09] <ScottL> the bug was fixed by an new release upstream vs. a patch
[02:10] <ScottL> do i download qjacktl-0.3.5 (with the bug) source and the qjackctl-0.3.8 (which fixes the bug) source and run debdiff
[02:10] <ScottL> and use this as the patch to append to the SRU?
[02:18] <ScottL> i probably should mentioned that 0.3.8 is in maverick and the SRU is for lucid which has 0.3.5
[02:31] <maxwellian> ScottL: I'm a noob at this, but since no one else is answering yet...won't that bring in basically all the changes between the two versions?  Maybe you're supposed to isolate a patch to fix the bug?  (Go easy on me! :) )
[02:32] <RAOF> ScottL: You find the particular patch which is a part of 0.3.8 which fixes the bug of interest, and use that.
[02:33] <RAOF> ScottL: That generally means wandering through the VCS of qjackctl.
[02:34] <ScottL> RAOF, that is true with a new upstream version as well?
[02:34] <ScottL> i would hate to cherry pick a patch but introduce new bugs
[02:34] <RAOF> ScottL: Yes.  Generally new upstream versions are not SRU-worthy.
[02:35] <RAOF> Well, are the 3 new upstream versions between 0.3.5 and 0.3.8 *entirely* bugfixes?
[02:35] <ScottL> RAOF, okay, thanks, i'll start digging around in the VCS then
[02:36] <ScottL> RAOF, no i don't think they are just bug fixes, but i would have to check the qjackctl website but i seem to recall them adding dbus functionality
[02:37] <RAOF> Only bugfixes are allowed in SRUs, so the new upstream version isn't going to be a winner.
[02:38] <maxwellian> ScottL: Too bad upstream doesn't have a bug tracker, so you can just find the change that fixes said bug number.
[02:39] <ScottL> RAOF, ack, this might mean a significant problem then if i can't find a patch :(
[02:40] <ScottL> i guess the next step to ensure quality functionality is to get qjackctl backported to lucid so that users can at least update qjackctl to gain that functionality back
[02:41] <RAOF> Note that backports are explicitly not meant to be there for fixing bugs (to ensure that people actually bother with SRUs).
[02:42] <RAOF> If there's fun new functionality in the newer qjackctl then a backport probably still makes sense, though.
[02:43] <ScottL> RAOF, acknowledged, i will purse the SRU patch first and then follow up with backport if it doesn't pan out
[02:55] <ScottL> oh, and thanks RAOF
[02:55] <RAOF> NP
[05:03] <wrinkliez> hey guys.  im new to this whole packaging thing.  if i want to move a file from the package to the users computer, do i use dh_install?
[05:12] <RAOF> wrinkliez: No.  dh_install moves files from $SOMEWHERE to somewhere in the package tree.
[05:13] <wrinkliez> thank you
[05:13] <RAOF> As a part of the source package build process you'll create (almost certainly automatically, using debhelper or cdbs) the package tree which will get unpacked onto the installer's system.
[05:46] <bullgard> '~$ rgrep 'post-installation trigger' /usr/src/linux-source-2.6.32/Documentation/ 2>/dev/null' does not produce any output. What is the function of "post-installation trigger"?
[06:07] <RAOF> bullgard: It's a trigger to run things that want to run after a kernel is installed.
[06:07] <RAOF> eg: update-initramfs, update-grub.
[06:07] <RAOF> You won't find it in the kernel documentation because it's a packaging thing.
[06:14] <bullgard> RAOF: Thank you very much for your information.
[06:26] <bullgard> If "post-installation trigger"  is a packaging thing, what program or file does write out the name "post-installation trigger" when Update Manager is installing new packages?
[06:28] <ripps> can someone explain to me the purpose of the new queue? Also, why was linux-meta allowed to get into the maverick repo before linux-image for it was?
[06:53] <bilalakhtar> Hey there, everyone
[06:53] <bilalakhtar> After merging, what should I copy into the changelog message?
[06:53] <bilalakhtar> the debian changes from the last ubuntu one,
[06:53] <bilalakhtar> or
[06:53] <bilalakhtar> the ubuntu changes till now?
[07:58] <dholbach> good morning
[08:03] <iulian> G'morning dholbach.
[08:04] <dholbach> hey iulian
[08:10] <maxb> Is there a standard reference for where update-alternatives belongs in package maintainer scripts? I'm seeing it used differently in different packages when I look for an example.
[08:13] <Rhonda> In postinst, not?
[08:14] <lifeless> maxb: what sort of differences are you seeing?
[10:29] <VK7HSE-Eee> Hi I need some advice on the following Bug #602981 I requested a sync into maverick, but the problem lies in http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=575122 so what is the best way to resolve this ?
[10:30] <VK7HSE-Eee> its clearly a dependency issue (out dated source)
[10:31] <VK7HSE-Eee> as all builds fine in Debian...
[10:32] <Laney> right, we need the new xine-lib for dh_xine to be there
[10:32] <VK7HSE-Eee> but will that break anything else ?
[10:32] <Laney> I don't know
[10:32] <VK7HSE-Eee> that's what I'm concerned for...
[10:32] <Laney> have a word with siretart, he deals with that
[10:33] <VK7HSE-Eee> OK thanks ;)
[10:35] <VK7HSE-Eee> siretart: Can you advise on the issue above ? the need for xine-lib to be bought into maverick but to ensure that it won't break existing packages...
[10:41] <VK7HSE-Eee> hmm ok it appears that the version in Maverick (xine-lib) doesn't handle the make rule so I think I can get away by requesting a sync to the latest ...
[10:53] <VK7HSE-Eee> I've submitted Bug #603059 to resolve my initial query...
[10:54] <Laney> Err, I thought you were trying to check if we want that
[10:55] <VK7HSE-Eee> well xine-lib is already in maverick, just an earlier version ...
[10:56] <Laney> ...I would have waited for siretart
[10:57] <VK7HSE-Eee> well it can always be refused then I will need to find an alternate way  ;)
[12:41] <btommy> hello together
[12:44] <siretart> VK7HSE: the package needs to be merged, the ubuntu delta is important
[12:45] <VK7HSE> siretart: thanks, just about to discuss with the devloper ;)  I'll mark that sync as invalid
[12:46] <siretart> better change it to a 'please merge'
[12:47] <VK7HSE> ok done ...
[12:48] <VK7HSE> that's for Bug #603059
[12:49] <VK7HSE> I've not done a merge before, so I'll need to do some reading and most likely need some guidance with the process ...
[12:52] <siretart> I have the merge ready in a bzr branch, could you perhaps test it the package works?
[12:52] <VK7HSE> ok ... url ?
[12:53] <btommy> hi
[12:54] <btommy> i shortly intruduce myself. i work as dvd-editor for linux-magazin and build since 3 years repos for the dvds
[12:54] <btommy> in this production i have the following serious problem
[12:55] <btommy> i can add the repositoriy without any problems
[12:56] <btommy> if i want install software form this, apt-get said: error get packages from cdrom
[12:56] <btommy> but: the pathes to the packages in the error messages are correct
[12:57] <VK7HSE>  siretart: do you have a URL for that branch ?
[12:58] <btommy> but: this error concern not all packages: othe software form the same directory i can install without problems
[12:58] <btommy> any ideas, how i can solve the problem?
[13:11] <btommy> her i have paste the message:
[13:11] <btommy> http://paste.ubuntuusers.de/398597/
[13:38] <sebner> JontheEchidna: k3b is ready to upload :D
[13:38] <JontheEchidna> sebner: just saw. thanks :D
[13:38] <sebner> np
[14:03] <sebner> JontheEchidna: I'd have uploaded it myself but I think you deserve the honour ^_^
[14:03] <JontheEchidna> :)
[14:32] <siretart> VK7HSE: please try pulling: 'bzr get http://tauware.de/~siretart/xine/xine-lib' - can you build a source package from that?
[14:32] <siretart> ricotz: ^^
[14:33] <VK7HSE> siretart: ok will do ... let you know how I go ;)
[14:34] <ricotz> siretart, i will have a look
[14:34] <siretart> yes, the merge was rather straight forward, but I did it using bzr nevertheless
[14:35] <ricotz> siretart, you might want to merge 1.1.18.1-4
[14:35] <siretart> didn't I?
[14:35]  * VK7HSE just refreshing my bzr after using git for so long! ;)
[14:35] <siretart> ricotz: I did
[14:36] <ricotz> siretart, the changelog said 1.1.18.1-1
[14:36] <siretart> ricotz: the tree wasn't updated
[14:36] <siretart> reload
[14:37] <giskard> guys do you know what was the ircname of  andrea veri (i think he was also a motu)
[14:37] <ricotz> siretart, alright
[14:37] <siretart> giskard: I think it was bluekja
[14:38] <giskard> nick is not registered
[14:38] <giskard> uhm
[14:38] <sebner> giskard: bluekuja
[14:38] <giskard> same.
[14:38] <sebner> giskard: nowadays it's something with like av or av`
[14:39] <giskard> i thought so.. but av afaict at the moment is another guys
[14:39] <giskard> let's see av`
[14:39] <giskard> Last seen  : Dec 16 00:56:13 2009 (29 weeks, 1 day, 12:43:13 ago)
[14:39] <giskard> yes
[14:39] <giskard> him
[14:39] <sebner> :D
[14:40] <giskard> +stalking
[14:40] <giskard> do you red something from him after 16dec?
[14:42] <VK7HSE> siretart: revno 82 is that the latest ?
[14:42] <siretart> yes
[14:42] <VK7HSE> ok ...
[14:44] <sebner> giskard: dunno, might be the case that he was longer active on debian oftc
[14:44] <VK7HSE> just getting deps, for building locally here ... will advise once I have a valid build, now I'm using Lucid presently, I'm all set with pbuilder chroots for maverick, but should I built it for lucid and test that way or is there a different method to go about this ?
[14:45] <giskard> he didn't register with any of that ircname on oftc
[14:47] <ricotz> VK7HSE, this should be built with maverick
[14:48] <VK7HSE> ok, but how will I use the built package ? is there a specific syntax I need to append to pbuilder ?
[14:48] <ricotz> pbuilder-dist maverick build xine-lib
[14:49] <VK7HSE> ok .. yet to buid the package, will scream out if I strike trouble ;)
[14:52] <VK7HSE> should I be concerned over the lintian warnings ? http://paste.debian.net/79982/
[14:54]  * VK7HSE well currently building it with those warnings ...
[14:54] <ricotz> VK7HSE, no this should be fixed in debian, but the your version should be "1.1.18.1-4ubuntu1" ;-)
[14:55] <VK7HSE> only upped the version for local use ...
[15:00]  * VK7HSE times like this a quad core or greater would be nice! :-/
[15:05] <joaopinto> general question, is it allowed for a package on the same archive/release to be on multiple components ?
[15:07] <ScottK> joaopinto: I'm not sure I understand the question.  One source package can build multiple binaries that may be in Main and Universe.
[15:10] <joaopinto> ScottK, I mean doing a manual archive management, is it valid to have the same package available from multiple components ? e.g package A on both main and universe.
[15:10] <ricotz> siretart, works here using it with vdr and xineliboutput
[15:10] <joaopinto> I am not asking this from an Ubuntu archive management perspective, I am asking from a generic APT perspective
[15:10] <ScottK> joaopinto: No, it wouldn't be I don't think.
[15:11] <siretart> ricotz: cool. can you upload to main or shall I upload it?
[15:11] <ScottK> joaopinto: I think what people would get installed then would be a function of the order in their sources.list.
[15:11] <joaopinto> since Index's are kept on a per release/component basis it's not clear
[15:11] <ScottK> joaopinto: I take that back.
[15:11] <ScottK> It is OK.
[15:11] <ScottK> But it is then a function of sources.list functionality.
[15:11] <ScottK> functionality/sequence.
[15:11] <ricotz> siretart, i am not a motu ;-) (yet), so please do it
[15:12] <ScottK> joaopinto: Something very much like this happens with security updates that are published in -security and then copied to -updates (because it's mirrored).
[15:14] <joaopinto> ScottK, but those are different archives from an apt perspective, I am not sure they are handled int the same way as  different components from from the same archive
[15:15] <ScottK> joaopinto: Good point.  I'm not sure then.
[15:17] <joaopinto> I am arguing that releases and not components should be used to manage packages promotion, something like beta->stable, I had the idea that having the same package in multiple components was invalid, but I am not sure any longer :\
[15:21] <siretart> ricotz: VK7HSE: uploaded
[15:21] <VK7HSE> was going to say it failed to build here :( ...
[15:21] <VK7HSE> but I reckon it was a dependency that I didn't have installed here ..
[15:24] <ricotz> siretart, thanks
[15:32] <micahg> does one need upload rights for the package to upload to -proposed?
[15:33] <Laney> yes
[15:33] <micahg> Laney: ah, ok, do you have time sponsor something small then :)
[15:35] <Laney> not right now sorry, perhaps in a bit
[15:35] <micahg> k
[15:35] <Laney> sebner has lots of time right now though
[15:35] <Laney> :)
[15:35] <micahg> sebner: ?
[15:35] <sebner> rofl
[15:36] <sebner> micahg: what is it?
[15:36] <micahg> sebner: bug 597944 the lucid patch
[15:37] <sebner> micahg: your debdiff should target to lucid-proposed though, nvm .. I'll fix that
[15:39] <siretart> ricotz: didn't you say it worked for you, the package ftbfs :/
[15:40] <ricotz> siretart, you have built it in an updated maverick pbuilder and using it on maverick now - amd64
[15:41] <siretart> hmseems there is some imagemagik transition going on
[15:41] <micahg> sebner: did I miss that :(
[15:41] <micahg> sebner: oh, I forgot to change after I upload to PPA, sorry
[15:41] <ricotz> siretart, yes, it is a dependency problem
[15:41] <sebner> micahg: nvm, uploaded :)
[15:41] <micahg> sebner: thanks much :)
[15:41] <sebner> np
[15:42] <ricotz> siretart, seems like i had done it the right moment
[15:42] <micahg> sebner: I just realized I forgot to use -v on my first upload to maverick on my own :(, so I guess I need to be more careful
[15:43] <sebner> micahg: heh, I also did tend to forget it but it's really no stopper
[15:43] <sebner> micahg: in the past, not with the gjs upload now :P
[15:44] <micahg> sebner: I was noticing someone else forgot it this morning and I'm like, wait a second I forgot it too on my upload :-/
[15:44] <sebner> heh, happens. don't worry
[16:01] <VK7HSE> where was the build for xine-lib uploaded to ? (xine-lib_1.1.18.1-4ubuntu1) ??
[16:03] <sebner> VK7HSE: if FTBFS https://launchpad.net/ubuntu/+source/xine-lib/1.1.18.1-4ubuntu1
[16:04] <VK7HSE> but it failed to build ... :(
[16:04] <sebner> VK7HSE: I said that :P , speak to siretart
[16:06] <VK7HSE> getting rather late here! so I'll need to revisit this tomorrow...
[16:07] <VK7HSE> but thank you to all that have invested you time on me and the xine-lib build ... ;)
[16:09] <ricotz> sebner, it shouldnt be called FTBFS?, the dependencies are broken in the main archive somehow
[16:09]  * VK7HSE so good night/morning afternoon/evening to all ...
[16:09] <sebner> ricotz: does it build? no ... the reason doesn't matter
[16:10] <ricotz> sebner, ok
[16:13] <lfaraone> python-abiword is currently uninstallable (if you use apt-get) in Lucid because it has a = dep on a particular version of libabiword-2.8. The updated version doesn't seem to involve an ABI change (installing with aptitude and importing abiword works fine). What's the proper way to fix the dep so that it has the desired effect but is not borked by future updates? bug 601415
[16:31] <Laney> bah
[16:38] <shadeslayer> Laney: ??
[16:38] <Laney> nm
[16:38] <shadeslayer> btw any ideas on http://pastebin.com/dDNYKLS2
[16:40] <micahg> shadeslayer: update-maintainer?
[16:41] <shadeslayer> micahg: uh.. really? i just dget'd the stuff from launchpad....
[16:41] <shadeslayer> maverick
[16:43] <micahg> shadeslayer: if you didn't modify the version, maybe it's a bug :)
[16:43] <shadeslayer> micahg: hmm.. i actually did modify the version :P
[16:43] <micahg> shadeslayer: ah, then you need to do update-maintainer :)
[16:44] <shadeslayer> micahg: btw suppose i want to backport this package ( kraft ) then do i upload with a ubuntu in the version?
[16:44] <micahg> shadeslayer: backport how?, through -backports?
[16:44] <shadeslayer> yes
[16:45] <micahg> shadeslayer: the archive admins handle that w/a script
[16:45] <micahg> or the backporters
[16:45] <shadeslayer> micahg: uh.. that still doesnt answer if i should have 1ubuntu1 in my version ;)
[16:45] <Laney> does it need any changes
[16:45] <Laney> ?
[16:45] <shadeslayer> Laney: thats what im trying to check :D
[16:46] <Laney> if it builds unmodified then you don't have to do anything
[16:46] <Laney> if yes, then ~releaseX
[16:47] <Laney> jdong: btw, how does one join the backporters?
[18:06] <ari-tczew> tumbleweed: I'm not angelabad ...
[18:07] <tumbleweed> ari-tczew: did I assign something to the wrong person by mistake? :)
[18:08] <ari-tczew> tumbleweed: so please do not repeat this mistake in future and be more careful
[18:08] <tumbleweed> ari-tczew: bug #?
[18:09] <ari-tczew> tumbleweed: bug 602437 ; bug 602461 ; bug 602846
[18:10] <ari-tczew> and now angelabad got 3 uploads which are worked by me... nice
[18:10] <tumbleweed> wtf?
[18:10] <tumbleweed> ari-tczew: that's ack-sync being silly then
[18:11] <ari-tczew> tumbleweed: I don't understand.
[18:11] <Laney> . o O ( error prone scripts over approved procedure )
[18:11] <tumbleweed> ari-tczew: I'll look later, in an IRC meeting...
[18:14] <ari-tczew> what is ubuntu-font-beta-testing ?
[18:15] <highvoltage> ari-tczew: ubuntu is getting new default fonts that's specially developed (looking for the link...)
[18:16]  * shadeslayer thinks that highly classified stuff
[18:16] <Laney> they've been blogging about it
[18:16] <Laney> so not really
[18:16] <shadeslayer> Laney: uh... /me got a PPA as bonus :P
[18:17] <Laney> I know, but it's not classified really
[18:17] <highvoltage> ari-tczew: http://design.canonical.com/2010/07/the-ubuntu-font/
[18:17] <highvoltage> it's not agrigated on planet ubuntu for some reason
[18:17] <shadeslayer> Laney: ok :P
[18:17]  * shadeslayer thought he was special :(
[18:17] <highvoltage> I just subscribe to the design blog seperately
[18:17] <Laney> highvoltage: I saw it on planet...
[18:18] <highvoltage> Laney: heh, ok. it was probably added then recently
[18:18] <Laney> aye aye
[18:18] <shadeslayer> Today all Ubuntu Members will have access to a private PPA so that they can use, test and enjoy the font. << Ohhhhh thats why :P
[18:18] <Laney> yeah that invitation message could have been clearer
[18:20] <ari-tczew> yhy
[19:05] <strycore> Hi everyone
[19:06] <oxymoron> YokoZar: ping
[19:08] <strycore> Ok, I've got this ape-server I really want to package, there's a .deb for the stable version but not for the git version
[19:08] <strycore> there is no source package, so I package everything from scratch
[19:09] <strycore> I did the basic stuff such as debian/control
[19:10] <strycore> and now I'm starting to try getting the package to build
[19:11] <strycore> the problem with ape-server is that there is a build.sh script invoking the makefile
[19:11] <strycore> this is the script : http://github.com/APE-Project/APE_Server/blob/master/build.sh
[19:12] <strycore> you can all see in the script, it writes to src/configure.h
[19:12] <strycore> if you call 'make' by itself , there's no configure.h so the build fails
[19:13] <strycore> ok, so the question is :
[19:13] <strycore> what should it I do ? :D
[19:13] <strycore> (besides learning more about debian/rules, which I eventually will)
[19:49] <YokoZar> oxymoron: pong
[20:41] <ari-tczew> tumbleweed: have you got 5 minutes for sponsorship?
[21:44] <ari-tczew> I have a problem with requestsync: E: No credentials found for 'ubuntu-dev-tools', please see the manage-credentials manpage for help on how to create one for this consumer.
[21:45] <micahg> ari-tczew: there should be a flag to not use lp for the info
[21:46] <ari-tczew> micahg: hello! why? ^^
[21:46] <micahg> ari-tczew: I think it was fixed in either maverick or trunk for u-d-t
[21:46] <tumbleweed> why not just use lp?
[21:46] <micahg> tumbleweed: he didn't set up credentials
[21:46] <tumbleweed> so... set them up?
[21:46] <micahg> ari-tczew: you could just set up the credentials in LP ...
[21:46] <ari-tczew> micahg: yesterday requestsync worked
[21:48] <ari-tczew> my lp says: Application name: ubuntu-dev-tools
[21:48] <ari-tczew> Authorized applications
[21:48] <micahg> ari-tczew: ah, ok, maybe it timed out w/LP, did you try a couple times?
[21:49] <ari-tczew> micahg: it's not timeout. I got answer from script just-in-time
[21:50]  * micahg is out of ideas...
[21:50] <ari-tczew> today I tried to test of pam security bug. it requires link: ln -s /etc/shadow ~/.cache
[21:50] <tumbleweed> ari-tczew: ok yes it looks like ack-sync uses the first bug-filer e-mail address for all the syncs in a batch
[21:50]  * tumbleweed didn't know that
[21:50] <ari-tczew> maybe this is a problem?
[21:51] <dupondje> https://bugs.launchpad.net/ubuntu/+source/xorp/+bug/600813 => can somebody try to build it on i386 ? seems like it worked here :s
[21:52] <tumbleweed> dupondje: building...
[21:52] <dupondje> tumbleweed: seems so, was wondering today why it got a wrong email here https://bugs.launchpad.net/bugs/602476
[21:52] <tumbleweed> err yeah that was me too
[21:52] <dupondje> -- Jean-Louis Dupond <angelabad@gmail.com>   Thu, 24 Jun 2010 14:16:30 +0200
[21:52] <dupondje> :p
[21:53] <tumbleweed> lol
[21:53] <ari-tczew> tumbleweed: could you request a bug to this script?
[21:53] <ari-tczew> and second question: syncpackage is not enough?
[21:53] <dupondje> ah well, less spam for me :)
[21:53] <tumbleweed> ari-tczew: it's a wrapper around syncpackage
[21:53] <tumbleweed> I'll propose a fix
[21:54] <ari-tczew> has someone idead for me? ^^ ^^
[21:54] <ari-tczew> ideas *
[21:55] <tumbleweed> ari-tczew: do you only do sync requesting from one PC? each machine needs to be authenticated with lp
[21:55] <dupondje> ari-tczew: did you reatry running manage-credentials create -c ubuntu-dev-tools -l 2 ?
[21:56] <ari-tczew> tumbleweed: I'm use 1 PC. do I need log-out from LP or log-in to LP?
[21:56] <tumbleweed> ari-tczew: no
[21:57] <tumbleweed> ari-tczew: you just need to follow the link manage-credentials gives you, and accept it in the web browser
[21:59] <ari-tczew> tumbleweed: is it possible that I did today follow commands: rm -rf ~/.cache ; ln -s /etc/shadow ~/.cache
[22:00] <micahg> ari-tczew: that probably did it "_
[22:00] <micahg> :)
[22:01] <tumbleweed> ari-tczew: that second command. Um what
[22:01] <ari-tczew> can I back this change?
[22:01] <tumbleweed> rm ~/.cache
[22:02] <tumbleweed> delete the authorization in LP, re-run manage-cred
[22:02] <ari-tczew> wrrrrrrrrrrrrrrrrr
[22:02]  * ari-tczew is upset
[22:02] <tumbleweed> (excuse me, I'm trying a different keyboard, and it's affecting my typing badly)
[22:04] <jpds> tumbleweed: Isn't the seacom outage affecting your packets too?
[22:05] <ajmitch> ari-tczew: why are you upset? you removed the directory that stored the credentials
[22:05] <tumbleweed> jpds: hurting us badly. This is my university: http://monitor.net.tenet.ac.za/cacti/graph_view.php?action=tree&tree_id=3&leaf_id=94
[22:05] <ari-tczew> ajmitch: I'm upset due to lack of free time.
[22:06] <jpds> tumbleweed: Ouch.
[22:06] <ajmitch> it should hopefully only take a minute or two to do
[22:07] <tumbleweed> jpds: yeah don't know what caused the non-international outage there, but we have international some of the time, atm :)
[22:07] <tumbleweed> fortunatly not all the DSL providers are affected
[22:11] <tumbleweed> dupondje: oh, built btw
[22:11] <dupondje> tumbleweed: can you sync it then ? :)
[22:12] <tumbleweed> dupondje: wait, i386, /me builds again
[22:13] <ari-tczew> dupondje: can we do all mergeable outstanding packages before FeatureFreeze?
[22:14] <dupondje> mmm
[22:14] <dupondje> 1 month to go
[22:14] <dupondje> should go below 100 for sure
[22:14] <dupondje> lotsa merges that needs to get accepted also
[22:15] <ari-tczew> syncs got more sponsors than merges
[22:18] <tumbleweed> syncs are easier to review
[22:18] <tumbleweed> unless we have a 0ubuntuX
[22:18] <tumbleweed> in which case they are hell
[22:18] <ari-tczew> don't object for this opinion
[22:18] <ari-tczew> just I say what I see
[22:19] <ari-tczew> I hope that we can do merges small to ~50 packages per component
[22:19] <dupondje> some merges are easy also
[22:20] <tumbleweed> of course. But many involve finding out where these patches should be (or have been) forwarded to
[22:24] <dupondje> Also some packages don't get synced, because the change in debian is to small, or just an ubuntu patch that got into debian
[22:24] <dupondje> but we should sync that then no? else in next release we need to review it again ...
[22:25] <tumbleweed> my feeling is that if you've done the work finding out that we can sync it, we probably should. It saves someone else having to review it in the future. But you could also just leave a comment in MOM
[22:26] <pwnguin> quick question about the 10.10 schedule and MOTU: does the debianimportfreeze also affect universe?
[22:26] <ari-tczew> tumbleweed: you've done for me 4 syncs and I hope that you'll do more sponsorships for me. You're on my crosshair as candidate to sponsors comment on my MOTU App  :>
[22:26] <ari-tczew> pwnguin: yes
[22:26] <pwnguin> ok
[22:27] <pwnguin> just wanted to verify; schedule adherence seems to change release to release. thanks
[22:27] <tumbleweed> ari-tczew: can you mail me a list of syncs and merges I've done for you? I can only recall syncs right now
[22:27] <ari-tczew> tumbleweed: I'll wait for more sponsorships by you, okay?
[22:28] <tumbleweed> fine. I've only been a motu 2 weeks anyway :)
[22:28] <ari-tczew> cool
[22:30] <tumbleweed> dupondje: err yeah, I don't know why dholbach couldn't build xorp
[22:31] <dupondje> yea its weird :)
[22:35] <dupondje> https://launchpad.net/ubuntu/+source/xmakemol => We can drop the delta here ?
[22:36] <dupondje> xmakemol is in universe, so why does lesstif need to be in main for it ? :s
[22:37] <tumbleweed> the problem is that the gl library isn't built with lesstif support
[22:38] <tumbleweed> because it's in main, but lesstif isn't
[22:40] <dupondje> and why exactly we need lesstif support in gl ?
[22:42] <tumbleweed> xmakemol appears to need it. but I'm not diving to find out why, now. I'm guessing glut
[22:43]  * tumbleweed heads to bed
[23:04] <ari-tczew> dupondje: xorp built fine for me also.