[00:17] <arand> What does actually XSBC mean? (c.f. XSBC-Original-Maintainer: in ubuntu packages).
[00:19] <geser>  X=user-defined field, S=include in source, B=include in binary, C=include in .changes
[00:22] <arand> geser: Ah, ok... Completely not what I expected then, I though it just was a wierd acronym :)
[00:27] <bdrung> arand: i sponsored your pastebinit patch
[00:28] <arand> bdrung: Yea, I noticed, cheers. Sorry about the maintainer miss. Just a happy amateur so far :/
[00:28] <bdrung> arand: if you want to get other things sponsored, just drop me a note and i will work on that instead of grabbing a random item from http://qa.ubuntu.com/reports/sponsoring/
[00:29] <ari-tczew> what is rc bugs?
[00:29] <bdrung> rc = release candidate
[00:30] <kklimonda> and not release critical? I guess it depends on a context :)
[00:30] <ari-tczew> +1 ^^
[00:31] <kklimonda> ari-tczew: release critical bug (in debian) is a bug that has to be fixed before releasing stable
[00:31] <bdrung> yeah, release critical is probably the correct one ;)
[00:31] <ari-tczew> merge/sync is enough to fix?
[00:32] <kklimonda> what do you mean?
[00:32] <ari-tczew> http://qa.ubuntuwire.com/bugs/rcbugs/maverick/
[00:32] <ari-tczew> row Fixed Version
[00:33] <ari-tczew> so merging latest debian version is enough to fix rc bug?
[00:33] <ari-tczew> if fix was published in debian revision
[00:33] <kklimonda> Ubuntu doesn't have concept of release critical bugs AFAIK
[00:33] <arand> bdrung: Well there's Bug #510571 , but if I understand things correctly that'd need an SRU-ack first..?
[00:33] <ubottu> Launchpad bug 510571 in virtualbox-ose "Lucid guest won't boot with acpi in virtualbox" [Undecided,Fix released] https://launchpad.net/bugs/510571
[00:34] <kklimonda> the closest thing to RC bugs is targeting a bug to some milestone
[00:34] <ari-tczew> o-O
[00:35] <bdrung> arand: no, we don't need it. the common way is to upload the package to -proposed and then a ubuntu-sru member either approves the package or declines it
[00:36] <bdrung> arand: the next sponsored bug will be yours.
=== Philip6 is now known as Philip5
[00:37] <arand> bdrung: cheers :) Just hoping my debdiffs are all in order...
[00:38] <bdrung> arand: they look fine
=== traveller_ is now known as traveller
=== nobawk is now known as nobawk|away
[01:25] <bdrung> arand: did you build the packages in pbuilder?
[01:26] <arand> bdrung: Yes.
[01:27] <bdrung> arand: my root partition went out of space. therefore i build only one of both debdiffs.
=== PyObjectPtr is now known as static_name
[01:29] <bdrung> arand: uploaded
[01:29] <arand> bdrung: I've also built them in my ppa: https://edge.launchpad.net/~arand/+archive/virtualbox/+packages, (there's a newer unrelated patch for karmic there as well) So I hope they should be fine... Cheers :)
=== static_name is now known as apachelogger
=== gospch_ is now known as gospch
=== lfaraone_ is now known as lfaraone
[04:10] <lfaraone> james_w: with bzr merge-upstream, can I specify an upstream revision with with to merge with? (I want to get a specific tag, but using "-r TAG_NAME" gets me "bzr: ERROR: --revision is not allowed when merging a tarball                                                                                                                                                  ")
=== nobawk|away is now known as nobawk
[06:27] <lifeless> lfaraone: please file a bug on that
=== piju is now known as piju[QRT]
[12:46] <Breaking_Pitt> I'm getting this error someone knows?
[12:47] <Breaking_Pitt> dpkg-gencontrol: warning: unknown substitution variable ${python:Provides}
[12:55] <ari-tczew> bdrung: have you got time for sponsoring other 3 my syncs?
[13:02] <ari-tczew> Laney: ping
[13:16] <bdrung> ari-tczew: yes, i will process all sync requests
[13:16] <ari-tczew> ok
[13:18] <ari-tczew> bdrung: btw. do you will process sync requests subscribed to ~ubuntu-archive ?
[13:18] <bdrung> ari-tczew: not planned
[14:02] <ari-tczew> who is responsible to site http://packages.ubuntu.com ?
[14:11] <bdrung> ari-tczew: To report a problem with the web site, e-mail frank@lichtenheld.de.
[14:13] <ari-tczew> ok, mail sent
[14:23] <Breaking_Pitt> how can i avoid this error..I can't find info quilt-series-but-no-build-dep
[14:25] <bdrung> Breaking_Pitt: http://lintian.debian.org/tags/quilt-series-but-no-build-dep.html
[14:26] <bdrung> You should either remove the series file if it's effectively not useful or add quilt to the build-dependencies if quilt is used during the build process.
[14:26] <Breaking_Pitt> where is the series file?
[14:27] <Breaking_Pitt> i don't create any series file
[14:27] <carstenh> Breaking_Pitt: which dpkg source format do you use?
[14:27] <bdrung> debian/patches/series
[14:28] <Breaking_Pitt> hi carstenh!
[14:28] <Breaking_Pitt> I'm still figthing with my package
[14:28] <carstenh> hi :) yes, i see
[14:28] <carstenh> test -d debian && cat debian/source/format
[14:29] <carstenh> what does this command tell you?
[14:32] <Breaking_Pitt> let me see
[14:33] <Breaking_Pitt> nothing! :)
[14:37] <Breaking_Pitt> fixed.. now I only have this one native-package-with-dash-version
[14:39] <carstenh> Breaking_Pitt: then you need to cd into the package directory and run it again
[14:44] <Breaking_Pitt> no way of avoidint the error :(
[14:44] <carstenh> correct, no way to avoid errors without either reading documentation nor answering questions ;)
[14:45] <Breaking_Pitt> i know
[14:46] <Breaking_Pitt> but seems that i have no file called bicho_0.3.0.orig.tar.gz
[14:50] <carstenh> Breaking_Pitt: you could try man mv and man dpkg-source instead of answering my question
[14:50] <bdrung> ari-tczew: you keep me working. ;)
[14:51] <ari-tczew> bdrung: someone must :-)
[14:51] <Breaking_Pitt> fixed ;)
[14:51] <bdrung> ari-tczew: this list is already too long: http://qa.ubuntu.com/reports/sponsoring/
[14:51] <Breaking_Pitt> thanks carstenh
[14:53] <ari-tczew> bdrung: for this problem I want to join MOTU and help
[14:54] <ari-tczew> but someone do not understand this
[14:55] <bdrung> who?
[14:57] <ari-tczew> bdrung: Laney don't want see my in MOTU: https://wiki.ubuntu.com/ArturRona/MOTUApplication#Comments
[14:57] <ari-tczew> s/my/me
[14:59] <carstenh> ari-tczew: you do syncs to remove ubuntu diffs ... topgit would be easy, you just need to grep for a single line to verify
[15:00] <ari-tczew> carstenh: propably you don't know what I'm working
[15:01] <ari-tczew> I just interested more in security bug fixing instead FTBFS. is it wrong? lol :-D
[15:01] <carstenh> ari-tczew: i read what Laney wrote, so maybe he doesn't know it too
[15:02] <ari-tczew> carstenh: so please be quiet, if you don't know
[15:03] <carstenh> ari-tczew: if you want me to be quiet, why to you tell me to be and don't just ignore waht I said?
[15:03] <ari-tczew> bdrung: hmm, I guess that sync requests requested manually is not show in http://qa.ubuntu.com/reports/sponsoring/ is it true?
[15:03] <bdrung> carstenh: i don't understand the connection between syncs and topgit
[15:04] <bdrung> ari-tczew: if you subscribe ubuntu-sponsors to your sync request bug, it will
[15:04] <carstenh> bdrung: there is a ubuntu specific diff that could be dropped
[15:05] <bdrung> carstenh: are you talking about a specific package?
[15:05] <ari-tczew> carstenh: just I don't like people who are saying a lot, but don't know the wole situation (in this context - my work structure)
[15:06] <carstenh> bdrung: yes, the package topgit
[15:07] <ari-tczew> and second: you wrote this to me, so I just answered to you
[15:07] <ari-tczew> nothing abnormal
[15:07] <bdrung> carstenh: aha - i thought he should use topgit to make syncing easier :D
[15:07] <bdrung> ari-tczew: you sounded a little bit offending
[15:08] <bdrung> (probably just the wording)
[15:08] <carstenh> bdrung: indeed the concept of topgit could help with syncing if it would use bzr instead of git ;)
[15:09] <carstenh> so, yes, the wording was suboptimal
[15:09] <bdrung> carstenh: i'll sync topgit
[15:09] <carstenh> fine, thanks :)
[15:10] <carstenh> bdrung: if you have questions please ask, I wrote the upstream patch, did the debian upload and told persia to to the ubuntu upload
[15:11] <ari-tczew> carstenh: so what's your conclusion: my work is unnecessary and not enough for MOTU?
[15:12] <ari-tczew> if you want (you, Laney, and others) I can leave channel and launchpad, I'll leave more work for you! cheers :-D
[15:13] <ari-tczew> and sponsoring list will be smaller, same benefits
[15:13] <ari-tczew> and quantity of security bugs will be higher
[15:13] <ari-tczew> what else?
[15:14] <bdrung> carstenh: uploaded - no question
[15:15] <kklimonda> ari-tczew: the problem is that MOTU is more than syncing, merging and backporting. It's also performing library transitions, packaging from scratch etc.
[15:17] <ari-tczew> kklimonda: so or you are doing all, or you are too small for MOTU, right?
[15:17] <carstenh> ari-tczew: i did not judge your work in any way until, but since you ask me: i have the impression that MOTOs should work more on sync request and collaboration with debian, it the only critic on your work is that you to too much work on collaboration with debian by taking care of syncing then it is more a reason to make you a MOTO than to veto. the packaging from scratch is IMHO useless if you could do the same or less work to get ...
[15:17] <carstenh> ... packages into both debian and ubuntu
[15:18] <carstenh> s/packaging from scratch/packaging from scratch for ubuntu/
[15:18] <ari-tczew> everybody from this channel: please give me a comment on my wiki page that I'm not welcome in MOTU - please!!!!
[15:19] <carstenh> ari-tczew: I don't know anything about your other work so I can't comment on this
[15:19] <ari-tczew> just give
[15:19] <bdrung> ari-tczew: you are overreacting
[15:19] <ari-tczew> bdrung: no
[15:20] <bdrung> ari-tczew: noone said that you are not welcome in MOTU
=== piju[QRT] is now known as piju
[15:21] <ari-tczew> bdrung: but I see opinions
[15:21] <ari-tczew> that I said: just give me a comment masters :-D
[15:22] <ari-tczew> you are the best
[15:22] <bdrung> ?
[15:22] <ari-tczew> note: sarcasm is not the same as flamewar
[15:23] <bdrung> i didn't use sarcasm
[15:23] <ari-tczew> bdrung: I use
[15:23] <bdrung> i use sarcasm only in face to face discussions to avoid misunderstandings
[15:24] <bdrung> ari-tczew: please mark sarcasm as such in IRC discussions
[15:34] <ari-tczew> carstenh: FYI yesterday I've looked all packages which were rebuilt for fakesync. tiring and time consuming.
[15:35] <ari-tczew> but propably you and other (Laney) thinks that this is not enough
[15:35] <ari-tczew> yeaa
[15:36] <carstenh> ari-tczew: you don't need to convince me, my comment on 16:17:50 was clearly on favor for you becoming a motu, but I don't have any influence on this
[15:40] <ari-tczew> carstenh: if you're with me, I'm glad, sorry for attacks
[15:41] <bdrung> ari-tczew: i think nobody is against you. at most they want you to gain more experience.
[15:42] <ari-tczew> looking at the fresh MOTU members, I don't think that they are doing these things (also performing library transitions, packaging from scratch etc.)
[15:44] <om26er> I restored my gnupg dir and now dh_make shows om26er@unknown.com in changelog file :(
[15:44] <bdrung> ari-tczew: yeah, library transitions are not the usual thing a newcomer does
[15:45] <bdrung> ari-tczew: did you update a package to a new upstream version? do you maintain a package in debian? do you triage bugs?
[15:46] <bdrung> that are thing that are not covered by syncs/merges
[15:47] <ari-tczew> bdrung: I've packages a few packages manually, but when I met sync, I don't doing this. Not maintain packages in Debian. Only requests for new upstream releases, or sending delta from Ubuntu. Triages - when I'm looking on package for syncs or merge, I'll check what bugs are exist.
[15:48] <carstenh> om26er: setting DEBEMAIL and DEBFULLNAME would fix this
[15:48] <ari-tczew> bdrung: syncs/merges not covered to new upstream release? o_O
[15:48] <bdrung> ari-tczew: they do not cover updating the package by yourself.
[15:49] <ari-tczew> bdrung: what for me? packages in Debian have a maintainers
[15:50] <bdrung> let me rephrase it: it's a difference if you sync/merge a new upstream release from debian or if you update the package by yourself
[15:51] <om26er> carstenh, thanks alot it worked :)
[15:53] <ari-tczew> bdrung: I know what's the difference, but what's going on?
[15:54] <carstenh> ari-tczew: if you want to do a debian upload to be able to tell people about it when they ask such questions you could prepare cuneiform, i would sponsor it. there is a new upstream version and possibly there are some lintian warnings to be fixed. preparing the new version includess recreating the orig.tar.gz since there are non-distributable files in upstreams version.
[15:55] <carstenh> since QA maintains the package there is no need to take care of this package in future
[15:55] <ari-tczew> sorry, I must go, see you
[15:55] <carstenh> ok
[15:55] <ari-tczew> I'm late
=== piju is now known as piju[QRT]
=== nigelbabu is now known as nigelb
[16:39] <funkyHat> Can I use bzr to check out a branch of any ubuntu package, and what's the form of the URL I can use?
[16:40] <funkyHat> Can't find anything for this on the wiki and https://wiki.ubuntu.com/Packaging/Training/Logs/2009-04-09 seems to be out of date
[16:40] <funkyHat> I've tried bzr checkout lp:~ubuntu/fglrx-installer and a few other variations ⢁)
[16:41] <funkyHat> Aha. bzr branch lp:ubuntu/maverick/fglrx-installer
=== piju[QRT] is now known as piju
[16:52] <funkyHat> hm. This branch seems pretty heavy... is it possible to make a lighter branch?
[16:53] <funkyHat> Perhaps I'd be better of just working with apt-get source and submitting a debdiff ⢁ D
[17:00] <astraljava> funkyHat: Isn't the bzr way how it's supposed to be worked, in the future, however?
[17:01] <bdrung> funkyHat: the normal way is "bzr branch lp:ubuntu/fglrx-installer"
[17:01] <bdrung> or "lp:ubuntu/<series>/<package>" for a specific series
[17:01] <funkyHat> astraljava: yes I think so...
[17:03] <kklimonda> hmm.. I need to run setup.py configure, how can I do it using debhelper 7 in a nice and clean way?
[17:04] <funkyHat> bdrung: ah thanks
[17:04] <AnAnt>  /q bdrung
[17:09] <funkyHat> I was going to try and make a package which included these patches https://bugs.edge.launchpad.net/ubuntu/+source/fglrx-installer/+bug/573748 but that looks more complicated than I thought it would
[17:09] <ubottu> Launchpad bug 573748 in fglrx-installer "fglrx does not build on 2.6.34 kernel (Patch files available)" [Undecided,New]
=== yofel_ is now known as yofel
=== nobawk is now known as nobawk|away
[18:43] <AcePreshaw> !caps
[18:43] <ubottu> PLEASE DON'T SHOUT! We can read lowercase too.
[19:37] <kklimonda> hmm, pull-debian-source is broken?
[19:37] <kklimonda> ah, no - my bad (noty to myself: pull-*-source work on source packages ;))
[20:28] <nigelb> sigh, bugs like 'ubuntu wallpaper made in mac!' make be laugh and cry at the same time
[20:29] <nigelb> s/be/me
[20:30]  * JontheEchidna waits for "the font was made in windows" to become public knowledge.
[20:30] <nigelb> meh.  I liked the response to it :)
[20:30] <arand> Not even just made in windows, but made bu MS tools :D
[20:30] <nigelb> these are the stuff that are used to make fonts, can't run away from it.
[20:31] <JontheEchidna> yeah
[20:31] <JontheEchidna> heh
[20:31] <nigelb> same goes for the wallpaper made in mac bug.  I closed the bug and I'm wiating for the flood to hit my mailbox
[20:32] <nigelb> there is also a bug about an upstream change and users complaining in lp about it.  seb and I've reached breaking point explaining that its an upstream change
[20:32] <arand> Hmm, those kinds are numerous.
[20:33] <nigelb> we've adopted a middle patch by setting to triage and reporting upstream :D
[20:33] <nigelb> s/patch/path
[20:34] <nigelb> I wish there was someway that noone could mess with a Fix Released bug.
[20:34] <BlackZ> hey nigelb
[20:34] <nigelb> oh, yeah, the mail
[20:34]  * nigelb gets to it
[21:27]  * micr0spell Discounts!! Our Special Limited Time Offers Up To May,22!!! Notebooks,Plasma and LCD TV's.Buy your electronic needs at our unique prices. Laptop Sony VAIO® VGN-FW590FFD-575,57$!!!Apple MacBook® Air MC234LL/A-695,27$!!! http://www.elplace.com/
[21:28] <nigelb> what the...
[21:29] <astraljava> Oh dear.
[23:07] <imbrandon> JontheEchidna: what font/bug ?
[23:12] <JontheEchidna> imbrandon: Oh, the guy making the new Ubuntu font did a presentation/plenary at UDS. He admitted to using a windows font tool because none of the Linux ones were really up to snuff
[23:13] <JontheEchidna> Though I think I did hear that somebody wanted to use the python fontforge bindings and Quickly to make a GUI for what he needed :P
=== piju is now known as piju[QRT]
[23:45] <imbrandon> ahh
=== nobawk|away is now known as nobawk
=== nobawk is now known as nobawk|away