[12:34] <pochu> slomo: uploaded at http://emilio.pozuelo.org/deb/ :) I've removed firefox.dpatch, so the delta with debian is small. Let me know if it's not a good idea ;)
[01:06] <pochu> I'm off to bed, cu folks!
[01:36] <DarkSun88> Notte a tutti
[02:30] <mattva01> hmm i'm a bit new to packaging and i have a question
[02:31] <mattva01> im packaging a python module using cdbs and when using pbuilder i get an error error: package directory 'distutils' does not exist
[02:33] <mattva01> are their any obvious reasons for that?
[02:43] <minghua> sounds like missing build dependency on python-dev
[02:44] <minghua> or something like that
[02:48] <mattva01> ok i'll check
[02:48] <mattva01> thanks
[02:55] <mattva01> ah think iv figured it out
[02:55] <mattva01> thanks
[03:07] <beuno> hello, anyone around who can answer me something about packages imported from Debian?
[03:08] <bddebian> We can try
[03:08] <beuno> I'm looking at this package: http://changelogs.ubuntu.com/changelogs/pool/universe/k/kflickr/kflickr_0.7-0ubuntu1/changelog
[03:08] <beuno> http://packages.debian.org/changelogs/pool/main/k/kflickr/current/changelog
[03:09] <beuno> sorry, that's the link
[03:09] <bddebian> OK and?
[03:09] <beuno> it's 0.7-0 in Ubuntu, but it's been 0.7-1 in Debian for a while now
[03:09] <beuno> http://packages.debian.org/changelogs/pool/main/k/kflickr/current/changelog
[03:09] <beuno> why hasn't it been resynced?
[03:09] <bddebian> Probably came in to Ubuntu first
[03:09] <bddebian> Possibly different orig.tar.gz
[03:11] <persia> beuno: The two versions are roughly identical (this is usually the case with Debian foo-1, and ubuntu foo-0ubuntu1.  There are probably no improvements to sync.
[03:12] <bddebian> Heya persia
[03:12] <beuno> persia: and the decision to import or not is automatic or by the package maintainer in Ubuntu?
[03:12] <bddebian>  ubuntuX versions are never autosynced
[03:12] <persia> beuno: By MOTU generally.
[03:14] <beuno> right, so it hasn't been synced due to the MOTU deciding no major changes where made to it?
[03:14] <bddebian> Probably
[03:15] <beuno> great, that helps me understand it a lot, thanks bddebian, persia
[03:16] <beuno> I'm trying to revive the "Debian Collaboration Team", so I'm going to be hanging around here a lot  :D
[03:16] <bddebian> Great welcome
[03:17] <bddebian> persia: Damnit, I had a question for you today and I totally forgot it
[03:18] <persia> bddebian: That's OK.  You will be reminded if you upload a new gmsh :)
[03:18] <bddebian> URL?
[03:18] <beuno> I'm going to re-check the progress that's been made up to now and cook up some sort of roadmap, then I'll start recruiting volunteers  :D
[03:18] <Lathiat> siretart: *nod
[03:19] <persia> bddebian: bug #112973
[03:19] <ubotu> Launchpad bug 112973 in gmsh "Please merge gmsh 2.0.7-1 from Debian unstable" [Undecided,Confirmed]  https://launchpad.net/bugs/112973
[03:20] <beuno> persia: is there any documentation on how Debian syncs (both to and from) are working at the moment?
[03:21] <beuno> I've read many pages in the wiki, but none of them are too clear on it
[03:22] <RAOF> Sync *from* Ubuntu to Debian?  Does that happen at all?  We try to push patches up, but it would seem strange for the Debian repository to contain a package with a -xubuntuy version :)
[03:23] <persia> beuno: I haven't seen a really good page.  Basically, in the beginning of each cycle, Ubuntu imports everything from that doesn't have local changes, and Ubuntu developers merge those that have changes.  After the freeze, this stops until the next cycle.  When bugs are found that also apply to Debian, often Ubuntu developers will open a bug in the BTS, and will provide a patch if one is available in Ubuntu.
[03:23] <persia> RAOF: It's manual.  Take a look at packages.qa.debian.org for something with an ubuntu version.
[03:24] <beuno> persia: great, that helps a lot, and what about upstream versions imported into Ubuntu, does Debian get any diff or notification on that?
[03:26] <persia> beuno: For new upstreams, usually not (AFAIK), as the Debian maintainer may have reasons to keep the current version.  Some Ubuntu developers are also Debian developers, and so will absorb Ubuntu changes into Debian.
[03:28] <beuno> persia: right, that leads me to two questions then, can you think of any way to semi-automate the notifications to Debian for new Upstream versions in Ubuntu taking the same approach as with patches?
[03:29] <persia> beuno: There'S patches.ubuntu.com, and the interface on packages.qa.debian.org, but I'm not sure if most Debian maintainers would want too much automation.  You'd do better to track down some of the DCT or utnubu folk for detailed answers.
[03:30] <beuno> persia: it seems I'm heading up the DCT team now since it's been dead for months (got admin on the launchpad group), and I've recruited a DD to help me out on the Debian side
[03:30] <beuno> so basically now we're starting from scratch
[03:31] <persia> beuno: You probably want to get in touch with the utnubu team (http://utnubu.alioth.debian.org/).  They are the natural counterparty to DCT.
[03:31] <beuno> persia: great, will do
[03:32] <beuno> now, my second question, I'd like to document a bit on how a DD can become a MOTU to encourage DDs to help out on both ends
[03:33] <bddebian> It's usually extremely easy for DDs to become MOTUs
[03:33] <beuno> do you think a special process con be made for DDs?  considering they already know how to package  :D
[03:33] <persia> beuno: It's the same process as a regular MOTU, but it's easier to demonstrate packaging skills.  First, become an Ubuntu Member, then apply to the MOTU Council.
[03:33] <bddebian> persia: Your build-deps are killing me :-)
[03:34] <beuno> persia: so for a DD to become MOTU, has to be a Ubuntu Member first?
[03:34] <persia> bddebian: Sorry.  I only end of with the little leaves at the edges :)
[03:34] <beuno> that seems a bit of on over kill, no?   I mean, it makes the process for them very ahrd since they have to contribute in a substantial way to ubuntu first
[03:34] <bddebian> :-)
[03:35] <persia> beuno: As far as I know, although the Community Council is usually very happy to welcome DDs to Ubuntu.
[03:35] <bddebian> What would be the point if they don't want to contribute to Ubuntu?
[03:35] <beuno> bddebian: they will, by maintaining packages for Ubuntu as well
[03:36] <beuno> it just seems like a "chicken and egg situation" to me
[03:36] <persia> beuno: All MOTU means is the ability to upload to universe.  For their own package, a DD has that (usually), and when not, can usually contact any MOTU and get a sync.  The process is to ensure they want to be involved enough with Ubuntu that when the upload other packages, they'll watch the breakage.
[03:36] <beuno> and I'm trying to build bridges, and since I'll be going to debconf, I want to have some of this layed out beforehand
[03:37] <persia> beuno: The Community Council usually considers contribution to Debian to amount to contribution to Ubuntu, so if a DD can point to good work to improve Debian, that counts towards improving Ubuntu as well.
[03:38] <beuno> persia: that's good to know (I'm going to document all this for DDs to know), but I still feel that it's too burocratic, and that both parties might benefit a lot if DDs could become MOTUs easier
[03:39] <bddebian> beuno: What is your expected result?  If they can upload/update their packages to Debian, they will get synced, they really don't even need to touch Ubuntu unless they want to be involved?
[03:39] <beuno> consider that I'm just starting to get involved in this, so feel free to point out anything I'm approaching the wrong way
[03:40] <beuno> bddebian: the package I mentioned before is a good example, the DD has a newer version uploaded and an even newer one to upload (0.8), plus a bug that's been reported both in Debian and Ubuntu, she would like to upload it to Ubuntu as well as Debian
[03:41] <bddebian> If "she" uploads it to Debian, we will sync it
[03:41] <bddebian> We brought the newer upstream in August 2006.  They didn't bring it in until Feb of 2007
[03:42] <persia> beuno: 0.8 will be synced or merged soon after upload (as long as Ubuntu is not in a freeze)
[03:42] <bddebian> And foo-1 in Debian is not a newer version then foo-0ubunt1.  They are roughly equivalent
[03:43] <beuno> right, I'm starting to understand this a bit more, the only thing that still puzzles me is the fact that she's willing to do the work *for* the MOTU, leaving him time to tend to other packages
[03:43] <bddebian> *for* the MOTU?  Is she not the package maintainer in Debian?
[03:43] <bddebian> We have no maintainers.
[03:44] <beuno> oh, well, it says that "Brandon Holtsclaw" is the uploader, so I assumed that he would have to check the diffs once the new package hits Debian
[03:45] <persia> beuno: The only work involved in a sync is the archive-admin marking it OK for sync.  MOTU doesn't have the ability to do that.  A sync is easier than parallel uploads, as then it only has to go into Debian in the future for automatic synchronisation.
[03:45] <bddebian> If she wants to ensure the newer version gets synced once she uploads it to Debian, she could file a bug on LP requesting a sync
[03:46] <beuno> persia: right, that helps me understand it better thanks
[03:46] <beuno> I'm trying to figure out a way to take advantage of the DDs that want to help with Ubuntu too
[03:47] <bddebian> I completely agree.  I am just asking in what way you are expecting that help?
[03:47] <bddebian> We would certainly welcome more MOTUs
[03:47] <beuno> I greatly appreciate both your time bddebian and persia, sorry for all the questions, I'm trying to have a complete picture on how things work
[03:48] <bddebian> No worries
[03:49] <beuno> and since I got a DD to take interest in this, I thought it would be a great opportunity to help get the team moving again
[03:49] <persia> beuno: If they want to help with their own packages, using launchpad to add Debian bugs to reported bugs, and request sync's would be great.  If they want to help with other packages, they should start by submitting patches, and following the process.
[03:49] <bddebian> :-)
[03:50] <bddebian> beuno: Trust me, Ubuntu tends to be much more inclusive than the Debian dev community.
[03:50] <beuno> ok, that's a good place to start, help associate Launchpad bugs with Debian bugs and mark them fixed and ask for syncing when fixed
[03:50] <bddebian> Not saying that we don't contribute enough back, that is still up for debate
[03:50] <beuno> bddebian: I've spend the last weeks surounded by Debian users/developers, so believe me, I know
[03:51] <bddebian> I wanted to be a DD for ages but got tired of getting abused.  Came here and wham, I started contributing.
[03:51] <persia> beuno: If you're up for serious effort, I believe the best way the DCT can help is to check all launchpad bugs against Debian, and make sure that if they apply to Debian, they are linked to Debian bugs, and that small, specific patches get back to Debian cleanly.  This is probably best done in collaboration with utnubu.
[03:53] <beuno> persia: I'm very serious about this, and I am willing to put a lot of effort into it, and that seems a very resonable way to start
[03:53] <beuno> once Debian bugs associated are marked as fixed, launchpad closes them as well, right?
[03:53] <persia> beuno: It'S 120,000 bugs :)
[03:54] <persia> beuno: LP closes them in Debian, but they aren't automatically closed in Ubuntu.  The subscribers to the Ubuntu bugs are notified.  For the packages I watch, I usually mark them Fix Released in Ubuntu when the next merge or sync happens (and I can see the bug is fixed).
[03:54] <bddebian> We can close the Debian bugs?
[03:56] <persia> bddebian: Anyone can.  Just send mail to to bug-closed@bugs.debian.org :)
[03:56] <bddebian> Is that a joke? :-)
[03:57] <bddebian> I mean the (Debian) bugs on LP
[03:57] <persia> bddebian: It's intended as a joke, but it works technically.  On the other hand, I wouldn't suggest closing Debian bugs unless they are really fixed in Debian.  Once the BTS closes, LP updates.
[03:58] <bddebian> Yeah, well I get tired of wading through them :-)
[03:59] <beuno> persia: in what cases does LP send the email to close a bug?
[03:59] <ASCIIGirl> persia, from BTS devel info "The person closing the bug, the person who submitted it" :-)
[03:59] <persia> bddebian: Unsubscribe, unless you want to be told when Debian fixes them.
[04:00] <bddebian> persia: I mean just when perusing some of the lists on LP.
[04:00] <persia> bddebian: That's a launchpad issue.  One hopes that the new Debian bug import system will make it easier to differentiate.
[04:01] <bddebian> I know it is :_)
[04:02] <persia> ASCIIGirl: My apologies, but I'm confused.  Looking at the BTS interface, I think foo-done@ should close from anyone (although submitter/maintainer are notified), as with closes foo to control@.  Am I mistaken?
[04:02] <ASCIIGirl> persia, http://www.debian.org/Bugs/Developer#closing
[04:04] <persia> ASCIIGirl: That's policy, not code.  That's the reason we don't close bugs: we're not supposed to do so.  The BTS accepts it anyway (and the Maintainer gets annoyed).
[04:04] <beuno> persia: so what's happening in practice?   is LP closing bugs or not?  if yes, do you have any exampls of this happening?
[04:05] <persia> bddebian: Thanks for gmsh.  Did you remember?
[04:06] <persia> beuno: bug #110788 is a good example of one that was fixed in Debian, and will soon be fixed in Ubuntu.
[04:06] <ubotu> Launchpad bug 110788 in scim "There should be a way to quit scim" [Undecided,Confirmed]  https://launchpad.net/bugs/110788
[04:08] <beuno> persia: so bugs *are not* being closed in BTS automatically, right?  even though it's tecnically possibe
[04:08] <persia> beuno: bug #44734 is an example of the opposite behaviour
[04:08] <ubotu> Launchpad bug 44734 in electric ".desktop file" [Low,Fix released]  https://launchpad.net/bugs/44734
[04:08] <persia> beuno: No: LP does not automatically close bugs in the BTS (see the policy link from ASCIIGirl).
[04:10] <bddebian> persia: Did I remember what?
[04:11] <persia> bddebian: You had a question for me, and had forgotten it.  I suggested an upload might help you remember, and I'm curious if I was correct.
[04:11] <beuno> persia: great, I'll start documenting and investigating all this, thanks a lot, you've been *extremely* helpful
[04:11] <mtaylor> anybody on here happen to be involved with kernel packages? 
[04:11] <bddebian> Oh, no.  I ran across a couple of packages today.  One used libflaac and one wx2.4 but I'll be dammned if I can recall what they were
[04:11] <persia> beuno: Please also check with others also.  I may well be incorrect about some details.
[04:12] <beuno> persia: will triple check, but at least I can start writing this up and then go back and fix it
[04:12] <beuno> I'm off to eat something now, again, thanks a bunch!
[04:13] <minghua> persia: the scim bug is probably a bad example...
[04:13] <persia> bddebian: For libflac, all the binaries imported from feisty (except kwave and prokyon3 on sparc) have been rebuilt, so the transition may be ignored.  For wx2.4, everything left needs significant code changes.  I'm working on patches, but they should all go upstream and back down before application.
[04:13] <beuno> (I'll stick around, so if anything comes up, I'll read it later)
[04:13] <persia> minghua: Why?
[04:13] <minghua> scim has ubuntu-specific patch, so a merge is needed
[04:13] <bddebian> persia: OK
[04:13] <beuno> and of course, ASCIIGirl is a DD, so she might benefit from all this too
[04:14] <beuno> aaaand I'm off
[04:14] <bddebian> Later
[04:14] <ASCIIGirl> byebye beuno :)
[04:14] <minghua> persia: and from my experience, the merge of scim is rather slow, as nobody understands the ubuntu patch very well
[04:14] <persia> minghua: Ah.  Do you have an example for a sync?  I didn't see any in a quick search.
[04:15] <minghua> persia: not from the top of my head, sorry
[04:15] <persia> minghua: No worries.
[04:19] <mattva01> hmm i'm confused, i'm trying to install my package on another computer and it keeps asking for the build  dependencies (like python-support)
[04:23] <bddebian> Install shouldn't ask for build dependencies.  I assume you mean dependencies?
[04:27] <bddebian> Geeps, the patch for F.E.A.R. is 600 freakin Mb :-(
[04:34] <bddebian> jdong: You up?
[04:36] <jdong> bddebian: that's what she said?
[04:36] <bddebian> hrm
[04:36] <bddebian> jdong: You've done stuff with xserver-xgl?
[04:37] <jdong> bddebian: some....
[04:37] <TheMuso>  /c
[04:37] <bddebian> jdong: Ever seen/heard about bug #48404
[04:37] <ubotu> Launchpad bug 48404 in xserver-xgl "netbeans java app gui is blank in xgl and java5" [Medium,Unconfirmed]  https://launchpad.net/bugs/48404
[04:38] <jdong> bddebian: only the most infamous Xgl limitation :D
[04:38] <bddebian> Oh yeah?
[04:38] <jdong> yep :(
[04:39] <jdong> it's a java+Xgl interaction
[04:39] <jdong> I don't know much more than that
[04:39] <jdong> other than there's apparently some workarounds you can export
[04:39] <bddebian> There's a patch for it on there ;-P
[04:39] <jdong> cool
[04:39] <bddebian> Crap, can someone please explain to me when we decide to do SRUs?
[04:39] <jdong> I don't know much about X server structures... so I don't feel qualified to do much with it :(
[04:39] <bddebian> jdong: Aye, me either really :-(
[04:41] <persia> bddebian: When it's really broken (https://wiki.ubuntu.com/MOTU/SRU (when))
[04:41] <mattva01> bddebian: no the installer is def asking for the build dependencies
[04:43] <bddebian> persia: Thanks, that's what I thought.  I sure question some updates then. :-)
[04:43] <bddebian> So why the hell then do we keep any bugs open for packages against older distros, "supported" or not?
[04:45] <persia> bddebian: I think in this case, "supported" only means security & no data loss, although it's not always treated that way.  Look at Debian stable updates for a counterexample.
[04:48] <bddebian> Ha, nice, the bug is in Debian too:  Tags: patch; 1 year and 172 days old.
[04:55] <persia> Could anyone point me to a good resource on what's happening with tetex / texlive?
[04:57] <bddebian> texlive is replacing tetex in Debian afaiui
[04:58] <persia> bddebian: That's all I know as well.  ia64 didn't like gmsh, and I'm wondering if I have to adjust my build-deps.
[05:01] <micahcowan> persia, the switch had already happened in Debian, so you might want to google around for Debian threads related to the change.
[05:01] <persia> micahcowan: Thanks.
[05:02] <micahcowan> bddebian, bugs for older releases are generally closed out I think, if they qualify for neither SRU nor backport.
[05:02] <bddebian> micahcowan: Not from what I see :)
[05:02] <micahcowan> bddebian, I mean, when we come across them and notice :)
[05:03] <persia> bddebian: What's an example bug?
[05:03] <micahcowan> At least, I have seen bugs closed for that very reason. Assuming it no longer applies in the latest release/development release.
[05:04] <bddebian> persia: About half the bugs UUS is subscribed to :-)
[05:04] <micahcowan> :o
[05:05] <micahcowan> bddebian: So, they're bugs that are fixed in the current release?
[05:05] <bddebian> In some cases, no, I'm working on that.  But I know if I close them I will catch shit :-)
[05:08] <persia> bddebian: I'm not familiar enough with most of the bugs I found in the list to specifically comment, but in general, I see U-U-S bugs marked "Needs Info" when the patch is outdated, but the bug exists.  I generally mark bugs "Fix Released" as soon as the latest version in the repository no longer contains the bug.  I've only ever had one user comment, and they were happy with the response that version x.y-z contained the fix, an
[05:15] <bddebian> persia: Maybe I'm over-reacting, I dunno
[05:16] <bddebian> Just seems like we have a shitload of old bugs out there
[05:18] <persia> bddebian: I think it's partly because we don't have "maintainers".  I personally watch about 5 packages closely, and try to manage their bugs, but the more active people can't concentrate like that, and the bug list just gets too long.
[06:06] (zul/#ubuntu-motu) bluekuja: what about it?
[06:06] (bluekuja/#ubuntu-motu) zul: I pm you something
[06:58] <ScottK> Any suggestions on how to find out why a package got deleted?  https://launchpad.net/ubuntu/+source/amavisd-new depends on https://launchpad.net/ubuntu/+source/libnet-perl and libnet-perl got removed?
[06:59] <lionel> check closed bugs
[06:59] <lionel> a general reason is "removed from Debian"
[07:00] <ScottK> lionel: Thanks.  Will do.
[07:00] <lionel> ScottK: np :)
[07:16] <ScottK> Well it looks like it got migrated into perl-modules, so no problem.  Thanks again.
[07:52] <jdong> someone say something in unicode :D
[07:55] <dothebart> in unicode
[07:55] <\sh> jdong: print u("")
[07:56] <beuno> espaol  :D
[07:57] <\sh> s ;)
[07:58] <jdong> excellent
[07:58] <jdong> thanks
[07:58] <jdong> now my freebsd is all unicode-happy :)
[07:58] <jdong> so I can see all those silly unicode smilies
[07:59] <\sh> freebsd? a new toy or just curious how a real OS is working ,-)
[08:00] <jdong> \sh: haha, a new toy... a 32MB FreeBSD VM on my home server for my persistent IRC sessions
[08:00] <jdong> and some educational purposes
[08:01] <jdong> I'm lovin it
[08:02] <\sh> well yeah, BSDi was my favorite in early internet days...
[08:03] <jdong> I am pleasantly surprised at how well it responds to me limiting its RAM so much
[08:04] <jdong> I would not expect Ubuntu cmdline to be able to build 3 packages at 32MB RAM and maintain some level of responsiveness
[08:08] <ScottK> jdong: Done - Bug #113665
[08:08] <ubotu> Launchpad bug 113665 in feisty-backports "Backport of pypolicyd-spf 0.3-1 to Feisty and Edgy" [Undecided,Unconfirmed]  https://launchpad.net/bugs/113665
[08:09] <\sh> how do we do backports? just test if gutsy source  compiles on feisty/edgy?
[08:09] <\sh> I'll think to join backporters, too :)
[08:10] <jdong> ScottK: thanks
[08:10] <ScottK> Not a problem.
[08:10] <jdong> \sh: yep, pretty much, pbuilder compile, and then preferably try to run it and make sure it doesn't eat anything :)
[08:55] <_MMA_> Wow. http://symphonyos.com/cms/?cat=1 "Ubuntu 7.04 Base system"
[08:56] <\sh> Automatix 2 argl
[08:56] <_MMA_> yeah :(
[08:56] <\sh> every new release == new install of the customer
[08:56] <\sh> great ,->
[08:56] <\sh> "linux is so stupid, I need to reinstall every release"
[09:03] <xxxxx1> simphonyos? wth is that
[09:03] <xxxxx1> oops. symphonyos
[09:04] <xxxxx1> :/
[09:36] <\sh> siretart, pingeling....fai-kernels...question
[09:49] <DktrKranz> Adri2000, Lutin, around?
[09:50] <Adri2000> DktrKranz: yes
[09:50] <DktrKranz> I'm not sure if this has been reported already
[09:50] <DktrKranz> but take a look at these pages:
[09:50] <DktrKranz> http://dad.dunnewind.net/dolphin/
[09:51] <DktrKranz> http://merges.ubuntu.com/d/dolphin/
[09:51] <DktrKranz> you'll notice dolphin_0.8.1-0ubuntu2.patch is null, while MoM one is 57K
[09:51] <DktrKranz> this breaks sync process (as happened to me)
[09:52] <Lutin> is it the 0ubuntuX-only thing ?
[09:52] <Adri2000> DktrKranz: known problem.
[09:52] <Adri2000> Lutin: it is
[09:52] <\sh> DktrKranz, use merges.ubuntu.com/universe.html
[09:52] <Adri2000> DktrKranz: it's on our TODO list and will be fixed asap
[09:52] <\sh> Adri2000, talk to keybuk (scott)
[09:52] <DktrKranz> ok, unluckily some of my syncs were published
[09:52] <Lutin> almost implemented actually ;)
[09:52] <DktrKranz> so I need to get ubuntu changes back
[09:52] <Adri2000> \sh: what for?
[09:53] <\sh> Adri2000, to join forces ,-)
[09:53] <\sh> he's the father of MoM ... and his mother is really pretty ,-)
[09:54] <Adri2000> I'm ok if they make MoM open-source, otherwise I can't work on it :)
[09:54] <\sh> Adri2000, http://linux.blogweb.de/archives/136-Its-Merging-Time.html .. well talk to scott...and ask him for help...he's good and knows some things ,-)
[09:55] <\sh> anyways..time to go out of the office
[10:31] <Ursinha> hi guys
[10:31] <Ursinha> i have a question about packaging
[10:33] <Ursinha> i need to repackage a metapackage, but i'm not the official maintainer
[10:34] <beuno> Ursinha: no reason for you to get sent to somewhere else unless it's a Debian package you are trying to repackage
[10:34] <Ursinha> thanks beuno :)
[10:35] <beuno> Ursinha: care to explain a bit more what you want to do?
[10:35] <Ursinha> it's simple
[10:35] <Ursinha> beuno, i have a metapackage of codecs, and i want to change one dependency
[10:36] <Ursinha> when i repackage with debuild, it runs lintian, and it says that i have to name it as a non-maintainer update
[10:36] <Ursinha> the original version is 0.8
[10:36] <Ursinha> my version, as a nmu, should be 0.8.1 or 0.8ubuntu1 or something, right?
[10:37] <Ursinha> but lintian complains, saying that is not the correct version number
[10:37] <beuno> that's a bit out of my league, but I'm sure someone else can help, bddebian?
[10:38] <afflux> 0.8-0ubuntu1 would be the right thing i think
[10:38] <Ursinha> if i version it simply 0.9, lintian complains too, saying that i should mention an nmu update, and that the version number is wrong
[10:38] <ScottK> NMU is a debian thing.  Don't worry about it here.
[10:38] <afflux> Ursinha: just ignore these warnungs about Nmu
[10:38] <Ursinha> afflux, hmmmm -0ubuntu1
[10:38] <Ursinha> afflux, can i just ignore them?
[10:39] <afflux> jep
[10:39] <Ursinha> i thought you at ubuntu care about all debian policy as much as they do
[10:39] <Ursinha> oh , okay
[10:39] <Ursinha> :)
[10:40] <Nafallo> Non-Maintainer Uploads becomes hard when you're not using the concept of Maintainers.
[10:40] <ScottK> Ursinha: There are some differences.
[10:40] <Ursinha> so which is the concept of ubuntu?
[10:40] <Ursinha> ScottK, where can i find about it?
[10:41] <ScottK> https://wiki.ubuntu.com/DebianMaintainerField talks about it in part.
[10:41] <ScottK> In general, packages are team maintained in Ubuntu.
[10:41] <afflux> I'll go to bed. n8
[10:41] <ScottK> Good night.
[10:42] <Ursinha> night
[10:42] <Ursinha> oh, late
[10:42] <Ursinha> ScottK, i see
[10:44] <xxxxx1> bddebian: <o/
[10:45] <Ursinha> ScottK, thanks
[10:45] <bluefoxicy> James Bunnell (jamesbunnell) added Contributors of packages for ubuntu universe (ubuntu-universe-contributors) (which you are a member of) as a member of Ubuntu New Mexico Team (ubuntu-newmexico).
[10:46] <bluefoxicy> <-- has no idea where new mexico is, aside from that it's somewhere west.. maybe middle of the US or closer to the west coast
[10:46] <ScottK> Yes and a bunch of other teams too.
[10:46] <Nafallo> ehrm
[10:46] <ScottK> He has no e-mail address on his LP profile either.
[10:47] <bluefoxicy> but apparently I'm in team new drunk-lazy-corona-vacation
[10:47] <Nafallo> how can what looks like a LoCo be a packagingteam? :-)
[10:47] <ScottK> It's not.
[10:47] <ScottK> Someone should go smack him.
[10:48] <bddebian> xxxxx1: ?
[10:48] <crimsun> bddebian: I think that's a "hello"
[10:48] <bddebian> Ahh :-)
[10:49] <\sh> re
[10:49] <crimsun> my ascii art interpretation may be off, though
[10:49] <Nafallo> I think it's a call for help :-)
[10:49] <xxxxx1> bddebian: hello
[10:49] <bddebian> Hello xxxxx1
[10:55] <ScottK> bluefoxicy: It's getting fixed on #launchpad right now.
[11:01] <\sh> k...going to bed...good night motus :)
[11:02] <pochu> night \sh_away 
[11:12] <crimsun> bluekuja: which?
[11:13] <bluekuja> crimsun, https://bugs.launchpad.net/ubuntu/+source/ivtv/+bug/113696
[11:13] <ubotu> Launchpad bug 113696 in ivtv "merge ivtv 0.10 .1 from debian unstable" [Undecided,Unconfirmed]  
[11:14] <crimsun> bluekuja: did you work with Mario on it?
[11:14] <bluekuja> crimsun, nope
[11:14] <jmg> bluekuja: how about luigi?
[11:15] <bluekuja> there were only 2 conflicts to be solved
[11:15] <bluekuja> jmg: lol
[11:15] <crimsun> bluekuja: superm1 (aka Mario Limonciello, #ubuntu-mythtv) should ACK it
[11:16] <crimsun> (I'm not familiar w/ the mythtv codebase)
[11:16] <bluekuja> crimsun, k gonna pm him when online
[11:16] <bluekuja> crimsun, tnx ;)
[11:17] <crimsun> np
[11:21] <xxxxx1> bye all
[11:21] <ScottK> Bye
[11:22] <bddebian> Later xxxxx1
[12:09] <TheMuso> Hey MOTUs.
[12:11] <nixternal> don't forget us MOTUwannabes as well ;)
[12:11] <TheMuso> Yeah I should change my greting then.
[12:12] <pochu> hey TheMuso