[03:06] <veebers> Hi all, I'm having issues installing using the "raring-desktop-i386.iso" Build: Ubuntu 13.04 "Raring Ringtail" - Alpha i386 (20130212)
[03:06] <veebers> it drops into busybox. Is there any useful information that I can extract at this point to submit a bug?
[03:13] <veebers> actually, the prompt says '(initramfs)', is that different to dropping to busybox proper?


[02:18] <Laney> anyone have any objections to merging broder's u-d-t branch? bdrung? tumbleweed?
[02:18] <Laney> it will need to be a divergance for debian
[02:18] <Laney> or dpkg-vendored in rules
[09:23] <bdrung> Laney: yes. i like to see ubuntu-qa-tools in Debian NEW first.
[10:28] <Rhonda> So I guess the slides from this UDS session makes my classroom session offer obsolete: http://agateau.wordpress.com/2010/10/28/git-for-bzr-users/
[10:37] <nigelb> Rhonda: the class is still worth taking, not everyone are at UDS :)
[10:38] <Rhonda> Yes, but they can read the slides themself.
[10:38] <Rhonda> Is there much benefit in c&p from the slides into the IRC channel?
[10:38] <nigelb> Yes, queestions
[10:38] <Rhonda> Feared you'd say that. ;)
[10:39] <nigelb> heh
[10:40] <ari-tczew> can I do small QA things in QA upload like bump Standards-Version?
[10:40] <ari-tczew> (in DEbian
[10:41] <tumbleweed> ari-tczew: yes, that's part of keeping a package up to date
[10:42] <Rhonda> What I heard from a specific release team member they don't like such changes during the freeze. On the other hand, a lot of packages got approved without mentioning that, so it's a tough call.
[10:42] <ari-tczew> tumbleweed: what about packaging new upstream releases?
[10:42] <ari-tczew> as QA
[10:42] <tumbleweed> ari-tczew: if necessary, but you should consider adopting the package
[10:43] <Rhonda> ari-tczew: What did you refer to with (in Debian)? Are you thinking of getting these changes into Debian, or into Ubuntu?
[10:43] <ari-tczew> tumbleweed: ah, then not. I'm main interested in forward patches from Ubuntu, if package is QA.
[10:43] <ari-tczew> Rhonda: from Ubuntu to Debian.
[10:43] <ari-tczew> and I need a sponsor (DD).
[10:43] <bilalakhtar> ari-tczew: hey! I would request you to be a bit patient when it comes to fixing FTBFS
[10:44] <Rhonda> New upstream versions shouldn't get uploaded during the freeze to not ruin the possibility to get updates into squeeze.
[10:44] <bilalakhtar> ari-tczew: I just merged something, FTBFS came, and I had the fix
[10:44] <bilalakhtar> ari-tczew: I am talking about package e16
[10:44] <bilalakhtar> and I uploaded the version with FTBFS to Ubuntu
[10:44] <ari-tczew> tumbleweed: I have to set-up my pbuilder-dist to build on sid.
[10:44] <tumbleweed> Rhonda: well they could go into experimental, but that's just weird for an orphaned package
[10:44] <ari-tczew> I remember that you gave me some tips, but now I couldn't find these in logs.
[10:44] <bilalakhtar> and when I went to upload the fixed version, I noticed you already have uplaoded it
[10:45] <ari-tczew> bilalakhtar: heh, are you upset?
[10:45] <Rhonda> tumbleweed: Right, but I'm not sure wether ari-tczew is targetting at experimental.
[10:45] <bilalakhtar> ari-tczew: This is the 3rd time this happened in the last week
[10:45] <bilalakhtar> This is the first time it happened because of ari-tczew , Previously, coolbhavi was to blame
[10:45] <bilalakhtar> So what I want to say is
[10:45] <ari-tczew> Rhonda: no, I want forward only patches from Ubuntu (bug fixes)
[10:45] <Rhonda> And I'm not too sure if preparing updates for natty through debian experimental is really the way to go. It's an effort in the wrong direction.
[10:46] <bilalakhtar> Leave FTBFS fixing to the previous uploader and work on it ONLY and _ONLY_ and *ONLY* if he is unresponsive for 3+ days
[10:46] <ari-tczew> Rhonda: cjwatson did a QA upload when I asked him. to unstable.
[10:46] <tumbleweed> bilalakhtar: um, why aren't you picking up these failures before upload?
[10:46] <Rhonda> ari-tczew: keep it to bugfixes then only please, to get chances high that they will get accepted into squeeze, too.
[10:46] <bilalakhtar> tumbleweed: Hm, the build succeeded on my pbuilder, later I realised I had built it on maverick
[10:47] <ari-tczew> Rhonda: sure, only bugfixes. no new features.
[10:47] <bilalakhtar> tumbleweed: my first upload mistake :(
[10:47] <Rhonda> ari-tczew: standards-version in the control file is just a comment for most things anyway, but release team members have different opinion and you don't want to trigger any responses based on that.
[10:47] <tumbleweed> bilalakhtar: :)
[10:47] <ari-tczew> bilalakhtar: you build on maverick for natty? rofl
[10:47]  * bilalakhtar deletes his maverick chroot
[10:47] <bilalakhtar> done, now I am on the _SAFE_ side
[10:47] <ari-tczew> bilalakhtar: I'm not your enemy, but if you're doing this... sorry man
[10:47] <bilalakhtar> ari-tczew: no problem :D
[10:48] <Rhonda> ari-tczew: So new upstream versions are definitely out of scope for the time being, unless they would also during regular times make a good target for experimental.
[10:48] <ari-tczew> Rhonda: example: https://launchpad.net/ubuntu/+source/smarty/2.6.26-0.1ubuntu1
[10:48] <ari-tczew> Rhonda: debian bug 514305
[10:49] <ari-tczew> I'd like to QA upload this one.
[10:49] <bilalakhtar> ari-tczew: I think DDs recommend RC bugfixes only now?
[10:49] <ari-tczew> It's available as remaining merge. I'll prepare debdiff and look for sponsor, instead merging. Then clear sync.
[10:49] <bilalakhtar> ari-tczew: Good luck in uploading to Debian
[10:49] <ari-tczew> bilalakhtar: I gave debian bug number, didn't I?
[10:50] <bilalakhtar> ari-tczew: but that's not RC
[10:50] <tumbleweed> ari-tczew: um, it looks like smarty is no longer orphaned and has an active maintainer who's rejected this change for squeeze.
[10:50] <ari-tczew> bilalakhtar: o_O and? Bug-fixes upload and they don't want these things?
[10:50] <bilalakhtar> ari-tczew: I don't think so, ask experienced DDs like Rhonda
[10:51] <ari-tczew> Rhonda is DD?
[10:51] <bilalakhtar> ari-tczew: Well, that bug is about co-ordination with Ubuntu, and something which isn't important from a DD point of view
[10:51] <ari-tczew> tumbleweed: maint    Debian QA Group
[10:51] <tumbleweed> ari-tczew: read the bug you just posed
[10:51] <tumbleweed> posted
[10:51] <bilalakhtar> ari-tczew: yes of course! She was one of the earliest DDs and still she is one!
[10:52] <bilalakhtar> She -> Rhonda
[10:54] <Rhonda> Since over 10 years now. :)
[10:54] <ari-tczew> tumbleweed: I didn't find any words like 'PLEASE DON'T DO THIS'
[10:54] <Rhonda> ari-tczew: See, and the mess in that smarty bug is reason to not carry the gap along but rather to get rid of it, right from the start. :)
[10:55] <tumbleweed> ari-tczew: "Obviously we
[10:55] <tumbleweed> cannot have this changed for Squeeze anymore"
[10:56] <ari-tczew> ok, I changed my decision. I won't prepare patches for QA packages.
[10:56] <ari-tczew> :]
[10:56] <ari-tczew> I'll merge package insetad.
[10:56] <ari-tczew> instead*
[11:00] <bilalakhtar> ari-tczew: So you will not participate in Debian Development?
[11:00] <ari-tczew> bilalakhtar: sorry, I'm not convinced.
[11:01] <ari-tczew> eventually I can do QA for e16.
[11:01] <ari-tczew> but I'm sure that I'll hear in a couple of minutes "we are not interested blah blah blah, anymore"
[11:15] <ari-tczew> tumbleweed: could you help me with pbuilder later?
[11:16] <vish> tumbleweed: hi, are you at the UDS?
[11:16] <vish> bilalakhtar: i'll look at that bug , i dint forget you ;)
[11:21] <tumbleweed> vish: nope - remote...
[11:21] <tumbleweed> (which is probably not worth the effort - it's exhasting and hard to contribute to)
[11:24] <vish> tumbleweed: hmm! i thought you were attending UDS ... now sure why i thought that … had you in the "people to meet and thank" list .. ;)
[11:25] <tumbleweed> vish: well thanks anyway :)
[11:40] <bilalakhtar> ari-tczew: Merged, now test-building the package
[11:41] <bilalakhtar> ari-tczew: Always remember to ignore ubuntu delta in files like config.guess and config.sub
[11:41] <bilalakhtar> They are automatically generated by configure
[11:41] <bilalakhtar> So even if they carry Debian data, configure willl automatically modify it accordingly
[11:42] <bilalakhtar> BTW, does anyone know how to sync a package using UDD?
[11:44] <ari-tczew> bilalakhtar: UDD?
[11:44] <ari-tczew> sync?
[11:45] <ari-tczew> I think that UDD is related to branches.
[11:45] <bilalakhtar> yes
[11:45] <bilalakhtar> but you can do much using UDD
[11:58] <ari-tczew> bilalakhtar: can I ignore also changes in aclocal.m4 ?
[11:59] <bilalakhtar> ari-tczew: yes you can
[12:01] <ari-tczew> tumbleweed: again about smarty: it might not to be included in squezee, or it never be applied?
[12:56] <Laney> Just mail a diff to the release team in advance of uploading
[12:56] <Laney> s'what I've been doing
[13:30] <tumbleweed> ari-tczew: it looks like Thijs (who's taken over that package) is happy to make the change, but after squeeze releases
[13:48] <ari-tczew> I'm confused. persia and Rhonda said 'better help Debian in release instead merging packages' and today I got to know, that only RC bug fixes are welcome.
[13:48] <tumbleweed> ari-tczew: helping deiban to release means helping them fixing RC bugs
[13:49] <ari-tczew> tumbleweed: no, they said forwarding/applying (help) patches in Debian
[13:50] <tumbleweed> that is often also helpful, but it's up to the maintainer and release team whether a patch is acceptable now or not.
[13:50] <micahg> ari-tczew: perhaps they meant where we have an RC fix in UBuntu already
[13:50] <mr_pouit> no, they said that forwarding patches to debian is good, but that if you do qa uploads, they should only fix rc bugs
[13:50] <Rhonda> ari-tczew: Yes, fixing RC bugs does help the release indeed.
[13:51] <ari-tczew> hmmm. if QA package has got FTBFS in Ubuntu, we have fixed it, can I QA it to Debian?
[13:51] <micahg> mr_pouit: I need to talk to you next week about helping with xubuntu-dev stuff :)
[13:52] <Rhonda> ari-tczew: The FTBFS does potential affect Debian when switching gcc (or whatever toolchain part does do the FTBFS in Ubuntu) so yes, I'd consider those appropriate. I'm though no release team member.
[13:53] <micahg> FTBFS due to our new toolchain probably should be fwded, but at a lower severity than RC since Debian shouldn't be affected until Wheezy
[13:54] <ari-tczew> Rhonda: So what's the way of QA upload ATM? Theoretically: I have a debdiff, you as a DD want to sponsor it. do I need to ACK?
[13:54] <mr_pouit> micahg: ah, good :P
[13:55] <Rhonda> ari-tczew: You just would need to convince me that it makes sense to get the change into squeeze. Then either you or me (still theoretically) would have to open a bugreport against release.debian.org package for unblock request with convincing information why this is improving the state of the package in squeeze.
[13:56] <mr_pouit> Rhonda: I'm not sure about the appropriateness, e.g. for ftbfs with binutils-gold, the severity seems to be 'minor' in the bts...
[13:57] <ari-tczew> lol, too much to do, I don't have a time
[13:57] <Rhonda> mr_pouit: Hmm, right actually. It will get raised after the release.
[13:58] <mr_pouit> yeah, I think so
[13:58] <Rhonda> Some people are heated on too high severity, so rather listen to mr_pouit :)
[13:58] <tumbleweed> alhtough I'm pretty sure one of the gold-related patches I forwarded resulted in an upload, but that may have been experimental
[13:59]  * geser usually forwards patches with normal severity and let the Debian maintainer figure the right severity out
[13:59] <ari-tczew> geser: we talk about QA packages
[14:00] <geser> I do it there too as I usually don't look who is the maintainer
[14:01] <Rhonda> ari-tczew: What's the main difference with QA packages for you?
[14:01] <ari-tczew> Rhonda: reduce the time for contact with maintainer
[14:01] <ari-tczew> only contact with DD
[14:01] <ari-tczew> $DD = sponsor
[14:06] <ari-tczew> tumbleweed: got a 10 minutes?
[14:07] <tumbleweed> ari-tczew: for what?
[14:07] <ari-tczew> tumbleweed: explain me how can I run pbuilder-dist sid on my ubuntu
[14:09] <tumbleweed> note: I don't know pbuilder-dist at all :) What happens if you do that?
[14:09] <RainCT> pbuilder-dist sid create   should work
[14:18] <ari-tczew> tumbleweed, RainCT: http://paste.ubuntu.com/522097/
[14:20] <Laney> bdrung: please say so on the merge proposal
[14:21] <bdrung> Laney: i did
[14:21] <Laney> ok thanks
[14:21] <ari-tczew> also update failed: http://paste.ubuntu.com/522098/
[14:21] <mr_pouit> ari-tczew: Bug #599695 maybe?
[14:22] <mr_pouit> (well of course, if you didn't create first, update won't work)
[14:22] <DktrKranz> ari-tczew: you have to selegt a specific keyring, i.e. http://bazaar.launchpad.net/~dktrkranz/debomatic/debomatic.dev/annotate/head%3A/etc/debomatic/distributions/unstable
[14:23] <ari-tczew> DktrKranz: what it means for me?
[14:24] <DktrKranz> pass the keyring param to debuildstrapoptz
[14:26]  * ari-tczew doesn't know what to do with these advices.
[14:27] <tumbleweed> ari-tczew: try --debootstrapopts --keyring=/usr/share/keyrings/debian-archive-keyring.gpg
[14:27] <tumbleweed> assuming pbuilde-dist can pass through argumnets...
[14:29] <kklimonda_> I don't use pbuilder-dist exactly because I couldn't configure it to work with both ubuntu and debian chroots
[14:30] <kklimonda_> I have a somewhat complicated ~/.pbuilderrc file and use pbuilder directly to deal with that.
[14:30] <tumbleweed> yeah, my pbuilder config grew legs...
[14:30] <ari-tczew> tumbleweed: http://paste.ubuntu.com/522101/
[14:30] <ari-tczew> I prefer to use pbuilder-dist, it's more clearly for me.
[14:31] <Laney> i never had to pass the debian keyring to build sid chroots with pbuilder on ubuntu
[14:31] <Laney> this must be a recent break
[14:32] <mr_pouit> ari-tczew: you didn't pass an action (e.g. 'create') in your last attempt
[14:32] <tumbleweed> Laney: one has the inverse issue building ubuntu packages on debian, and that's how I deal with it
[14:32] <Laney> yes
[14:32] <Laney> I am familiar with that one. :)
[14:32] <ari-tczew> mr_pouit: lol, look @ http://paste.ubuntu.com/522097/
[14:32] <mr_pouit> ari-tczew: pass create and the extra arguments...
[14:34] <ari-tczew> mr_pouit: http://paste.ubuntu.com/522103/
[14:35] <tumbleweed> yeah, so it doesn't pass through...
[14:35] <micahg> ari-tczew: the release keyring changed recently in Debian
[14:36] <ari-tczew> micahg: aha
[14:36] <ari-tczew> .
[14:37] <micahg> ari-tczew: you might want to make a personal backport of the latest debian-archive-keyring
[14:37] <Laney> if that's the break, then it should be srued
[14:38] <mr_pouit> (check if it is installed first...)
[14:38] <tumbleweed> easy enough to find out. ari-tczew gpg --keyring /usr/share/keyrings/debian-archive-keyring.gpg --list-keys 0x9AA38DCD55BE302B
[14:39] <ari-tczew> micahg: yes, debian-archive-keyring is outdated in maverick
[14:39] <micahg> ari-tczew: right
[14:39] <Laney> so install the new one from sid and see if you can build the chroot then
[14:39] <tumbleweed> that key was created in 2009-01-27 - it should be there... :/
[14:39] <micahg> Laney: we've never SRU'd the debian keyring before from what I can tell
[14:40]  * Laney shrugs
[14:40] <ari-tczew> micahg: but I don't have installed it... :P
[14:40] <micahg> ari-tczew: oh
[14:40] <tumbleweed> +1 to mr_pouit :P
[14:41] <mr_pouit> :]
[14:41] <ari-tczew> massacre, please but this discuss from logs
[14:41] <ari-tczew> s/but/cut
[14:41] <mr_pouit> huhuhu
[14:42] <Laney> yeah it works if you install that
[14:42] <Laney> oh
[14:42] <Laney> no it doesn't :P
[14:42]  * ari-tczew needs check whether wiki.ubuntu says about install debian-archive-keyring before creating pbuilder for sid
[14:45] <Laney> pbuilder-dist sid create --debootstrapopts --keyring=/usr/share/keyrings/debian-archive-keyring.gpg
[14:45] <Laney> this works
[14:45] <ari-tczew> Laney: and I used this 5 minutes ago. still working
[14:45] <Laney> good :)
[14:45] <ari-tczew> now downloading from ftp
[14:46] <ari-tczew> toolchain, if I'm correct
[14:46] <Laney> pbuilder-dist can work around this
[14:48] <ari-tczew> okay, sid created.
[14:48] <ari-tczew> now I'll test build of package
[15:09] <Laney> https://code.launchpad.net/~laney/ubuntu-dev-tools/use-debian-keyring
[15:09] <Laney> sanity check please
[15:12] <ari-tczew> Laney: +1 for Depends on debian-archive-keyring !!!
[15:13] <Laney> it's not good enough on its own
[15:13] <ari-tczew> :(
[15:17] <micahg> Laney: I would say at most it should be recommends since it's only if you're doing Debian stuff (an Ubuntu dev never needs this)
[15:18] <Laney> 64kb
[15:18] <Laney> I am entirely uninterested in having a discussion about that, so do what you want
[15:18] <Laney> maybe recommends is right given that that's where pbuilder is
[15:21] <micahg> Laney: it's interesting that cdebootstrap has a depends on debian-archive-keyring, but debootstrap doesn't
[15:22] <Laney> yeah
[15:22] <Laney> debian bug?
[15:23] <micahg> Laney: ah, the explanation is in debian 560038
[17:18] <kklimonda_> can someone take a look at bug 668414 ? vdk2 has to be rebuilt to catch the migration of gdk-pixbuf-2.0 library into a different directory under /usr/include
[17:20] <BlackZ> kklimonda_: can you please subscribe "ubuntu-sponsors" to the bug?
[17:20] <kklimonda_> sure
[17:27] <debfx> kklimonda_: I'll handle it
[17:36] <BlackZ> kklimonda_: I forgot, first create a debdiff to do the rebuild and then subscribe "ubuntu-sponsors" (however, if you already did that, can you please prepare a debdiff to do the rebuild?)
[17:37] <kklimonda_> BlackZ: it takes just as much time to create a rebuild only debdiff as it takes to check if its right. And isn't there some sort of script that can do that for you anyway? I'm not really opposed to do that, just that it's not going to be any faster for a sponsor to handle a debdiff anyway.
[17:39] <kklimonda_> it is* - really, the longer I write in English, the more stupid mistakes I seem to make
[17:39] <Laney> yes indeed
[17:39] <Laney> for rebuilds I wouldn't bother with a debdfiff
[17:43] <BlackZ> Laney: so was "subscribing "ubuntu-sponsors" to the bug" enough?
[17:43] <Laney> yeah
[17:43] <BlackZ> s/was/is
[17:46] <BlackZ> kklimonda_: then I was right.. just subscribe "ubuntu-sponsors" to the bug :P you can also skip the step to "create a debdiff for the rebuild" :)
[17:47] <kklimonda_> BlackZ: I didn't really object the subscribe part :)
[17:49] <BlackZ> kklimonda_: I didn't say you did as you didn't ;)
[17:50] <debfx> kklimonda_: uploaded
[17:50] <debfx> I guess it affects maverick as well
[17:50] <debfx> is it worth a SRU?
[17:58] <kklimonda_> debfx: hmm.. it may be worth it, all packages that use vdk-config-2 are going to ftbfs in maverick too
[17:59] <kklimonda_> debfx: but there aren't that many of them and, from a quick look, they are not that popular (the library itself hasn't been updated in 6 years, I guess the similar may be true for applications - vdkxdb2 hasn't been updated since at least hardy)
[18:00] <kklimonda_> ok, lunch time
[18:06] <ari-tczew> porthose: are you going to merge rosegarden ?
[18:34] <ari-tczew> xteejx: ping on bug 592328. still interested?
[18:35] <xteejx> ar9-tczew: Hi, feel free to take it if you want :)
[18:36] <ari-tczew> xteejx: if you want to quute nicks, press [TAB]
[18:36] <ari-tczew> s/quute/quote
[18:36] <xteejx> didn't know empathy has autocomplete :D
[18:38] <ari-tczew> xteejx: a lot of IRC clients has got autocomplete by pressing a [TAB]
[18:38] <xteejx> ari-tczew: I didn't realise :) Thanks for that, another little helpful thing
[18:42] <ari-tczew> you're welcome
[18:44] <porthose> ari-tczew, go ahead if you like
[18:54] <Rhonda> rotfl. Für den Tripp Trapp Hochstuhl gibt es einen Tisch-Zusatz, der nennt sich clic clac.
[18:54] <xteejx> !de | Rhonda
[18:54] <Rhonda> uups.
[18:54] <Rhonda> xteejx: Rather EWIN :)
[18:54] <xteejx> EWIN?
[18:55] <Rhonda> Error Window.
[18:55] <xteejx> Kein Problem :)
[18:55] <Rhonda> Or in wow speech: fc
[18:55]  * Rhonda . o O ( falscher channel …  wc in english for wrong channel? )
[18:58]  * xteejx we don't tend to use wc or fc, but wc is better, although it is also an abbreviation for toilet lol
[19:06] <xteejx> Is it possible to rebuild debian-installer-netboot-images on the autobuilers?
[19:07] <xteejx> I think there was a timeout with the ftp.debian.org server that's all I jut checked its fine
[19:36] <cjwatson> xteejx: eh, I think I'll need to customise it for Ubuntu anyway so it's probably not worth bothering
[19:37] <xteejx> cjwatson: Oh ok, no worries, just saw it in the FTBFS list and had a look :)
[19:38] <cjwatson> could be that the buildd isn't allowed to do external HTTP access
[19:38] <cjwatson> (haven't double-checked but seems probable)
[19:38] <cjwatson> thanks for checking though :)
[19:39] <xteejx> cjwatson: No problem, glad to be of some kind of help :)
[20:09] <simar> ari-tczew, heya
[20:11] <ari-tczew> simar: hey
[20:11] <simar> ari-tczew, could we resume the lesson today??
[20:11] <simar> ari-tczew, I got my maverick installed.
[20:12] <simar> :--))
[20:12] <ari-tczew> simar: sorry, no. I'm eating now and go out soon
[20:12] <ari-tczew> maybe tomoroow
[20:12] <simar> ari-tczew, no problem..
[20:12] <ari-tczew> in normal time, not in the night :P
[20:12] <simar> ari-tczew, approximately at what time ??
[20:13] <ari-tczew> simar: UTC 12:00 ?
[20:13] <simar> ari-tczew, ok done..
[20:13] <ari-tczew> fine
[20:13] <simar> ari-tczew, c ya
[20:13] <ari-tczew> see you
[20:21] <andreserl> a/win 15
[20:23] <ari-tczew> andreserl: thanks for your response. I'd like to ask you about change comment on MoM to more details like 'andreserl on it' or similiar
[20:29] <andreserl> ari-tczew: yeah I usually do that, but when I put do not touch it is usually in packages I've uploaded
[20:31] <ari-tczew> andreserl: it's not clear for all. I thought that it's like BLACKLISTED or something.
[20:31] <ari-tczew> I encourage to change it.
[20:32] <andreserl> ari-tczew: it is clear to me :)
[20:32] <ari-tczew> andreserl: you're not the one user of MoM
[20:33] <andreserl> ari-tczew: yes I'm not the only one, nbut if it says "do not touch" must be for something either if I'm working on it or iof there's something wrong with it or whatever
[20:34] <ari-tczew> andreserl: so, do you will change it or not?
[20:34] <andreserl> ari-tczew: I'm not gonna change the "do not touch" comment at the bug report, but will work in the merge.
[20:36] <andreserl> s/bug report/merges.ubuntu.com
[20:36] <ari-tczew> andreserl: not good activity for community
[20:37] <andreserl> ari-tczew: never had problems before with it, so I don't see how is a bad activity for community
[20:37] <Laney> why is it a problem?
[20:37] <ari-tczew> Laney: [21:31] <ari-tczew> andreserl: it's not clear for all. I thought that it's like BLACKLISTED or something.
[20:38] <Laney> the outcome is the same in either case though :-)
[20:39] <ari-tczew> Laney: no comment
[21:33] <paultag> Hey MOTU. I've got a package pending in the NEW queue in Debian. It won't make it in until after Deb freeze. Can I upload to REVU for inclusion in -N ?
[21:48] <borealis> Hello, I'm a newcomer to the ubuntu packager stuff. I'm also one of the crew in the qtjambi group, and I want to get some guidance into how to get QtJambi back in the official ubuntu repos again.
[21:49] <borealis> I was thinking that a good start for me would be to look at the package files for the old qtjambi packages.
[21:51] <tumbleweed> borealis: https://edge.launchpad.net/ubuntu/+source/qtjambi <- "get it back in? it's there"
[21:52] <borealis> Oh, really? Well, it's based on pretty old stuff.
[21:52] <borealis> We have reached 4.7 on QtJambi.
[21:52] <bdrung> how do i get apport to file a bug with the crash information attached? please answer in bug #668508.
[21:53] <borealis> tubleweed: How do I proceed to update those packages?
[21:54] <borealis> I'm a total newbie to this business, I'm afraid, so if someone is willing to lead me a bit by the hand, I am willing to update that stuff.
[21:56] <tumbleweed> borealis: well the preferred way is to get them into debian and actively maintain them there, but short term: https://wiki.ubuntu.com/PackagingGuide/Recipes/PackageUpdate
[22:01] <borealis> Hmm, do I need to be an active debian user to do that? Which IRC forum do I need to get in touch with to get some guides there?
[22:03] <tumbleweed> borealis: yeah, that probably helps.  Debian's stronger maintainership seems to help