[00:01] <CarlFK> English
[00:03] <CarlFK> ﻿im trying to remove some of the manual steps from http://www.voxforge.org/home/dev/autoaudioseg "Step 2 - Add Missing Words ... [WINWARD] w ih n w er d
[00:07] <persia> CarlFK: Apparently not.  I thought maybe one of the speech synthesizer lexicons would have such a thing, but they are entirely phonemic, rather than having phonetic spellings.
[00:08] <persia> (Also, most aren't GPL: generally closer to ISC)
[00:09] <wgrant> Uh. Can I reject bug #240934, or do we support compilation on architectures that don't exist?
[00:09] <CarlFK> persia: yeah. but that may be ok.  apparently festival can do what is needed, but someone (me) needs to ... um.  make the output usable :)
[00:14] <persia> CarlFK: Right.  I've just dug a bit more: You can get (non-GPL) lists in festival-oald (oald-0.4.out) or festival-cmu (cmudict-04.out), depending on the pronunciation you prefer.
[00:16] <CarlFK> persia: thanks
[00:19] <emgent> heya people
[00:20] <YokoZar> jdong: can I poke you for a backport?
[00:21] <YokoZar> I've tested it :)  https://bugs.edge.launchpad.net/hardy-backports/+bug/240755
[00:26] <persia> motu-release: The DIF notice has been posted to u-d-a@ : could someone please send the related information re: the DIF exception process, etc.?
[00:27] <persia> (or tell me to do it, but I don't want to ursurp release planning activities)
[00:32] <cyberix> Where can I find a guide for splitting one source package into multiple binary packages?
[00:33] <persia> cyberix: http://wiki.debian.org/PkgSplit, but I found this confusingly Java-specific.
[00:34] <persia> cyberix: The general rules are 1) put the right names in debian/control, 2) use -p, -a, and -i in debhelper calls in debian/rules.
[00:35] <cyberix> What disturbs me most is that the two pieces of software probably share some files
[00:35] <cyberix> e.g. AUTHORS
[00:35] <cyberix> and maybe some documentation
[00:35] <persia> cyberix: AUTHORS doesn't typically belong in the binary package.  If you have shared docs, consider having a foo-doc package.
[00:36] <cyberix> Also, there are probably related things that I don't see currently
[00:37] <cyberix> It would be useful to get a list of typical problems
[00:38] <LinuxMonkey> anyone here know when the next packaging 101 is, cause trying to follow the guide I got lost.lol
[00:48] <persia> LinuxMonkey: What are you packaging, and where did you get lost?
[00:50] <LinuxMonkey> persia: well im trying to learn packaging, therefore following the guide at https://wiki.ubuntu.com/PackagingGuide/Complete and doing that hello thing. however someone first told me i needed to create a chroot and do everything from there, however someone else told me thats not the case so I guess im lost
[00:50] <LinuxMonkey> and the guide is not quite clear on that
[00:51] <persia> LinuxMonkey: There's no right answers in packaging.  Personally, I strongly recommend seeking a different goal than "to learn packaging".  Good goals might be "to package some application", "to fix some class of packaging bugs", or the like.
[00:51] <persia> Or rather, there are several, equally right answers (and there are some wrong answers).
[00:52] <persia> To address the need for a chroot specifically: if you are building something that can generate a source package using the tools in your current release, you may proceed without a chroot.  If you rely on tools in a different release to build the source package, you must do that in a chroot.
[00:54] <baron1984> is there anyone from the kernel team in here?
[00:55] <persia> baron1984: While there often is, #ubuntu-kernel is almost always a better place to ask about the kernel, as it then becomes on-topic.
[01:01] <LinuxMonkey> well persia i love the way you change the goals but  in fact they are the same goals I have however in order to "Package some application" "fix a bug and repackage" you infact need to learn packaging in a way. and thats what I want to do. im just following the advise of the WIKI to start with
[01:02] <persia> LinuxMonkey: I can see that argument, although the level of knowledge required to package one application or fix some class of bugs is not as high as is typically expected by those who claim to understand packaging :)
[01:02] <persia> So, what are you seeking to accomplish as a result of your study of the wiki?
[01:06] <LinuxMonkey> well I guess its whatever you guys want me to do really, untill i learn more, I was trying to follow the guides on the wiki but im starting to understand thats probably NOT the best way to aproach this, probably the best way is to get someone to show me how to do something and continously work on that type of stuff untill at ease with it and learn something else as I go along
[01:07] <baron1984> well, #ubunt-kernel is dead, can you guys at least tell me how to go about filing a suspend/resume bug?
[01:07] <baron1984> what kind of information is needed, etc
[01:09] <nxvl> if i have a source package inside another, do i need to the copyrights of them to the copyritght file or just mention there is this other package
[01:09] <persia> LinuxMonkey: I'd recommend working on bugfixes for a bit.  If you want packaging-specific bugfixes, trying to fix the packages that cannot install (apt-cache unmet -i) can be an interesting way to become familiar with debian/control
[01:10] <persia> nxvl: You need both copyrights.  Ideally you'll also complain to upstream about the extra security work involved in bundling embedded sources, and you won't have that problem anymore.
[01:12] <nxvl> persia: the embed source is gnulib
[01:12] <persia> nxvl: Ah.  Right.  You want to mention that in debian/copyright, and find a saner package then.
[01:12] <nxvl> persia: i have already talk with cjwatson and he told me it's better to keep it there than linking
[01:13] <nxvl> persia: but my question is: should i list the copyright under "Copyright:" or just mention it with it's license under "License:"
[01:13] <LinuxMonkey> persia: ok I wouldnt mind working on bug fixes, just dont know were to start. what to do. think of me as fresh meat, willing to do anything and learn what i need to do as long as u point me in right direction
[01:14] <persia> LinuxMonkey: Right.  Are there any bugs that you experience that irritate you?
[01:16] <LinuxMonkey> no not really persia the bugs ive encountered have been fixed really fast
[01:16] <persia> LinuxMonkey: OK.  Are there any packages that you use a lot and find especially useful?
[01:18] <LinuxMonkey> I dont use much mostly wine. lol as in windows wine
[01:19] <persia> LinuxMonkey: Hmm.  It's hard from that to tell what might interest you.  You might look through the bugs tagged "packaging" on launchpad, and see if you can find a good fix for one.
[01:26] <crimsun_> baron1984: https://wiki.ubuntu.com/DebuggingKernelSuspend
[01:50] <m-c> superm1: ping
[01:52] <emgent> argh.. I cant sleep
[01:53] <m-c> Micheal larabel from phoronix.com has been working on an interesting project.  Have you heard about it?
[01:55] <m-c> With the development of the open source drivers, from Intel, AMD, and Novell, there are reasons why people will want independent comparisons of open source graphic drivers.
[01:56] <m-c> Michael has created a GPL-based benchmark suite for testing these drivers against GPL-based benchmark programs.  I have tried this software out, and I can attest that it is worth incorporating into the next Ubuntu release.
[01:56] <m-c> Michael says he has discussed this with superm1 already, but so far I have not been able to contact him or see a write up in Launchpad.
[01:56] <persia> m-c: Does it have a needs-packaging bug?
[01:57] <baron1984> m-c: I'd kill for any kind of open source drivers, binary blobs are why you can't improve a distro without hosing people's video cards, etc.
[01:57] <persia> baron1984: Select different hardware :)
[01:57] <baron1984> Nvidia's drivers aren't entirely compatible with even Hardy, they just hacked their way around a lot of things
[01:57] <baron1984> and XRandr doesn't work well
[01:58] <baron1984> I'd take compatibility over a few more frames a second
[01:58] <m-c> I invited Michael to the channel.  Persia, is the next step to enter a need-packaging bug report?  If so, then I will get on it.
[01:59] <m-c> michaellarabel: hi
[01:59] <michaellarabel> Hi
[01:59] <persia> m-c: The best first step for any new package request is a needs-packaging request.  That is the list of software that is available to be packaged for those packaging things.
[02:00] <m-c> Right.  I understand.  Is there any information that might be needed from Michael while he is present, regarding license or other information?
[02:00] <persia> The next step would be for someone to claim the request, and build a candidate package for REVU.  It's also worth reviewing the Debian bugs against wnpp, and linking to any relevant RFP or ITP: if a package is going into Debian, it makes sense not to duplicate the work.
[02:01] <persia> I think a good needs-packaging bug contains the software name, the license, the homepage, and a brief description.
[02:01] <m-c> Would it be more applicable for this package to be entered upstream, into Debian?
[02:03] <m-c> Right, I can enter this into Debian first, then, with the information you specified.
[02:03] <persia> michaellarabel: If you are upstream for software that ought be included, there are some things that can be done in your release planning to make packaging easier: including the license in the root directory of the release tarball, providing versioned gzip-compressed tarballs for download (and maintaining the old version archive), and the like.  More suggestions are available from https://wiki.ubuntu.com/UpstreamGuide (althoug
[02:03] <persia> h this is incomplete).
[02:03] <m-c> Thank you for your advice.
[02:04] <michaellarabel> persia: License is already in root directory, the tarballs are versioned, and there is still an old version archive, etc. :)
[02:04] <persia> m-c: I can't say whether it belongs in Debian: depends on interest and utility.  If getting it in faster is a goal, it may be easier to put in Ubuntu now, as Ubuntu is unfrozen, and Debian is entering a release freeze.  Of course, this is a soft freeze, so it may not matter.
[02:05] <persia> michaellarabel: Excellent :)
[02:06] <m-c> My perception is that getting it into Ibex would be superb, with the AMD open source drivers coming to maturity at that time
[02:08] <nxvl> finally got it packaged!
[02:08] <michaellarabel> persia: Any other tips?
[02:09] <nxvl> persia: what was the process for revu, just upload and wait, or send an e-mail somewhere?
[02:10] <persia> michaellarabel: As upstream?  No.  As a potential packager?  I can point you at various guides, but need more information about what you need.
[02:10] <persia> nxvl: Upload, wait, and ask here on REVU days.
[02:10] <persia> You can also ask here once a day when it's not REVU day.
[02:10] <persia> nxvl: Also, if you've time, feel free to review others packages :)
[02:11] <nxvl> :D
[02:11] <nxvl> i will try
[02:12] <michaellarabel> persia: No other real questions... I just have never went through the Ubuntu/Debian package submission process before.
[02:12] <persia> michaellarabel: I'm not deeply familar with the Debian process, but the Ubuntu process is to use REVU.  Let's see if the bot has the link...
[02:13] <persia> !revu
[02:13] <nxvl> i am familiar with the debian one
[02:13] <nxvl> :D
[02:13]  * nxvl is NM
[02:14] <nxvl> for debian you need to be psicological prepared or have a friend
[02:14] <nxvl> :D
[02:14] <nxvl> they are evil
[02:14] <nxvl> :P
[02:14] <nxvl> you need to upload your package to mentors.debian.net
[02:17] <nxvl> and somewhere in mentor you have the info about the ITP Bug, mailling list and stuff
[02:35] <nixternal> oi oi
[02:48] <superm1> persia, yeah i offered to help provide some advice when a package is ready
[02:48] <superm1> and to look it over and such
[02:49] <superm1> if no one else was going to step up to package it in the next month or two i was going to take a look near the middle to end of summer at doing it
[02:49] <michaellarabel> superm1: Hi, yeah, m-c will probably submit that package to you then as he's offered to do it and has more time than me.
[02:49] <superm1> wonderful
[02:49] <superm1> time is a great thing to have :)
[02:49] <nixternal> time sucks!
[02:50] <superm1> hopefully i'll get around to giving it more of a thorough look and get you some more input on its functionality
[02:50] <michaellarabel> superm1: Great. What was the test/suite that had taken you all day to do? Did you get my email about that?
[02:51] <superm1> yeah i got the email about it, but  got swamped on other things so it's added to the "Todo"
[02:51] <michaellarabel> ok
[02:51] <superm1> when i get a chance to look again i'll just do universe
[02:51] <superm1> or universe-x
[02:51] <superm1> and go from there
[02:52] <michaellarabel> k
[03:26] <SpookyET> I keep getting this email http://pastie.org/217736
[03:27] <SpookyET> http://pastie.org/private/byvfyjge9ysotzfryinivq
[04:49] <nxvl> where can i find an explanation about what the sections means?
[04:50] <persia> nxvl: http://www.debian.org/doc/debian-policy/ch-archive.html#s-subsections
[04:54] <nxvl> persia: yes, i'm reading that, but it only lists the sections
[04:54] <nxvl> well, they are pretty obvious
[04:55] <bimberi> nxvl: http://packages.debian.org/unstable/
[04:55] <persia> nxvl: Oh, you want an explanantion of each section?  Hmmm...
[04:56] <persia> nxvl: I don't know where the official source lives.  http://packages.debian.org/unstable/ has a nice overview of each of them.
[04:57]  * nxvl HUGS persia and bimberi 
[04:57] <nxvl> :D
[04:57] <bimberi> :)
[05:51] <Zombie> Hello.
[05:51] <Zombie> I'd like some upgrade help. I have a Kubuntu Hardy CD and a Ubuntu DVD. I want to use thsee as my upgrade sources instead of the network.
[05:53] <persia> Zombie: This isn't a support channel: you want #ubuntu, but you just change your sources.list
[05:55] <Zombie> I got a rediculously stupid answer there, is there an advanced Ubuntu channel?
[05:56] <persia> Zombie: No.  Try again :)
[05:58] <joejaxx> that has to be a classic quote
[05:58] <joejaxx> lol
[05:58] <ScottK> I'd have said there is, but I have a consulting rate.
[06:00] <joejaxx> 00:47:59 -!- Irssi: Join to #ubuntu-motu was synced in 869472 secs
[06:00] <joejaxx> hahahahahahahaha
[06:00] <joejaxx> 10 days
[06:00] <joejaxx> that HAS to be a record
[06:00] <wgrant> Nice!
[06:01] <ajmitch> joejaxx: it's not unusual to have that
[06:01] <joejaxx> really?
[06:03] <ajmitch> nah, irssi has often done that for me in the past until I closed or /cycle'd windows that where out of sync after a disconnect
[06:03] <joejaxx> oh
[06:03] <joejaxx> that is unfortunate
[06:04] <ajmitch> usually if I was over the 20-channel limit & hadn't identified before irssi tried to rejoin them all
[06:06] <joejaxx> oh
[06:06] <joejaxx> sounds like me :D
[06:06] <lifeless> has anyone filed that irssi bug?
[06:06] <joejaxx> no
[06:06] <joejaxx> :P
[06:06] <joejaxx> i did not think of it
[06:07] <joejaxx> as i am in over 500 channels lol
[06:07] <ajmitch> yeah, that's just madness
[06:07] <joejaxx> so i thought it might just be my user case
[06:07] <joejaxx> :)
[06:15] <Zombie> I have a systemic question about where Ubuntu stores downloaded debs.
[06:15] <Zombie> Where does it store them.?
[06:17] <joejaxx> Zombie: /var/cache/apt/archives
[06:21] <wgrant> nixternal: Why does smb4k keep destroying /etc/sudoers?
[06:21] <wgrant> It has at least 4 separate instances of it in its bug history.
[06:21] <wgrant> This is probably a very bad thing.
[06:22] <ScottK> Adri2000 or Lutin: You might want to look at the current spamassassin on DaD.  debian/changelog is mssing all the Ubuntu entries.
[06:22] <ajmitch> wgrant: because it's an evil package that should be removed, given its potential for serious breakage?
[06:23] <wgrant> ajmitch: That's what I was thinking.
[06:23] <wgrant> Destroying once, maybe.
[06:23] <wgrant> But 4 separate bugs.
[06:23] <wgrant> Seriously.
[06:24] <ajmitch> looking at the bug for it, it must do some stupid things with that file
[06:25] <persia> Isn't there some policy statement about not touching conffiles from other packages?
[06:25] <wgrant> sudoers is a special case.
[06:25] <ajmitch> yes, don't do it in maintainer scripts
[06:25] <wgrant> Which is even more reason to *keep the $#*($#@ away from it*
[06:25] <ScottK> Ambitious maintainer is all it is ....
[06:26] <ajmitch> bug 238011 for those who want to cry
[06:26] <wgrant> Nothing else manages to eat config files - why something that touches sudoers?
[06:26] <wgrant> ajmitch: Ah, I apparently failed to paste that here earlier. Oops.
[06:29] <wgrant> I see that the first incarnation managed to stick some X error crap at the start.
[06:29] <wgrant> This is truly impressive.
[06:29] <wgrant> I'd like to know how it does it.
[06:30] <ajmitch> crossing the streams
[06:30] <wgrant> Hm?
[06:30] <ajmitch> never mind
[06:30] <persia> ajmitch: Yes :)
[06:30] <joejaxx> wgrant: possible movie reference :P
[06:30] <joejaxx> haha
[06:30] <joejaxx> :)
[06:30] <ajmitch> you're probably too young for that one :)
[06:31] <wgrant> Blah/
[06:31] <joejaxx> :P
[06:31]  * bimberi offers ajmitch a marshmallow ;p
[06:31] <ajmitch> heh
[06:31]  * StevenK chuckles
[06:39] <wgrant> I like the summary of bug #226722
[06:39] <wgrant> Fits a lot in.
[06:45] <LinuxMonkey> now thats funny
[06:46] <Ekushey> rofl
[06:52] <Zombie> Folks.
[06:52] <Zombie> You people need to add an option for CD and DVD based upgrades.
[06:52] <Zombie> I can't get my system to do that
[06:52] <persia> Zombie: It should be present (and this still isn't a support channel).
[06:53]  * persia thinks the "upgrade from CD" function was added in edgy
[06:53] <joejaxx> yeah
[06:53] <joejaxx> that should be on the optical media
[06:54] <wgrant> Zombie: You should be in #ubuntu. Make sure that you're not trying to use a desktop CD.
[07:04] <Ekushey> what do i need to do to be able to upload to REVU? i already joined the LP revu-uploaders team
[07:05] <wgrant> Ekushey: You need to request that the REVU keyring be synced.
[07:05] <wgrant> I really must improve that process one day.
[07:06] <Ekushey> wgrant, are you in charge?
[07:06] <wgrant> Ekushey: I have the power.
[07:06] <wgrant> It is now running, but will take several minutes.
[07:07] <persia> wgrant: Back to a cron job?
[07:07] <Ekushey> wgrant, my LP ID is russell.john
[07:07]  * persia tries to remember why the cron job was cancelled
[07:07] <wgrant> persia: I was thinking that a minimal version of the sync - that is, picking up only new keys - could run immediately before the upload processor each time.
[07:07] <wgrant> And refresh all keys once a day
[07:08] <\sh> moins
[07:08] <wgrant> Hey \sh.
[07:08] <wgrant> Ekushey: So you'll be quite close to the end.
[07:08] <persia> wgrant: That sounds complete, but I remember something going wrong and the keyring being corrupt back on the original sparky.  Maybe my memory is faulty.  Maybe the new infrastructure is sufficiently better.
[07:12] <Ekushey> wgrant, so i can try uploading tomorrow?
[07:13] <wgrant> Ekushey: Give it another couple of minutes...
[07:13] <Ekushey> so fast? wow :)
[07:13] <wgrant> It is done.
[07:14] <wgrant> Upload now - your upload should be on REVU in about 6 minutes.
[07:14] <Ekushey> great, thanks wgrant!
[07:16] <Ekushey> i'll do it at night from home
[07:17] <Ekushey> i've question one question, why isn't flock available on the repo? what's wrong with it?
[07:17] <jussi01> its closed source?
[07:18] <Ekushey> is it? isn't it based on firefox?
[07:21]  * jussi01 cant find source anywhere...
[07:21] <LinuxMonkey> i found the source
[07:22] <LinuxMonkey> http://downloads.flock.com/index.php?product=flock-source-current&os=linux
[07:22] <Ekushey> it's licensed under MPL / LGPL dual license
[07:22]  * jussi01 must be going blind...
[07:23] <LinuxMonkey> jussi01: just tired
[07:23] <Ekushey> so there must be some other reason why it's not available on ubuntu
[07:23] <jussi01> LinuxMonkey: havent woken up yet...
[07:23] <jussi01> Ekushey: hasnt been done yet?
[07:23] <LinuxMonkey> its 2:32am and i havent gone to bed yet
[07:25] <Ekushey> no clue... is there a way to find out if someone is packaging it or not?
[07:25] <persia> Ekushey: Look for a needs-packaging bug on launchpad, or an RFP/ITP bug in the BTS.  These are the means by which people request/announce packaging
[07:26] <Ekushey> ok persia
[07:27] <jussi01> LinuxMonkey: its 9.27 am, im not awake yet
[07:32] <dholbach> good morning
[07:34] <LinuxMonkey> morning dholbach were either so tired were not responding (my case) or not awake yet (everyone else)
[07:35] <dholbach> LinuxMonkey: bed time then? :)
[07:35] <LinuxMonkey> yeah another 25 minutes or so. its only 3:35am anyways
[07:36] <dholbach> that's OK then ;-)
[08:55] <emgent> morning
[09:18] <huats> morning dear motu world
[09:29] <RAOF> Howdie.
[09:35] <RAOF> bigon: I'm looking at telepathy-butterfly (because miro's blocked).  It seems that the Ubuntu divergence (don't pull in python-ctypes, which introduces an unnecessary 2.4 dependency) should go back to Debian.  Would you like me to file a bug in the BTS?
[09:35]  * persia is amused at the complaint that courier-imap is too new.  Usually it's about things being outdated.
[09:35] <RAOF> Someone's merged it from the future :)
[09:36] <persia> Perhaps the idea is to get the average version to some ideal...
[09:36] <RAOF> Hm.  Awkward.  subversion FTBFS, and libsvn-perl is uninstallable.
[09:37] <persia> RAOF: It's part of the master plan to get everyone to go back to RCS
[09:37] <RAOF> svn-buildpackage ain't gonna be working for me in the immediate future.
[09:37] <wgrant> persia: Shingle version control!
[09:38] <RAOF> Ah.  Subversion needs a merge, apparently.
[09:38] <persia> wgrant: I'm not sure I trust those newfangled things.
[10:18] <bigon> RAOF, fixed in the tp-butterfly bzr branch
[10:21] <Adri2000> ScottK: yes, base version (3.2.4-2
[10:21] <Adri2000> err
[10:22] <Adri2000> ScottK: ) not available on snapshot.d.n, so empty patches and broken merge
[10:51] <RicardoPerez> can any MOTU member apply the patch in bug #222038?
[10:52] <james_w> hi askand
[10:52] <askand> ﻿ james_w:  hi
[10:53] <james_w> would you like to look at http://merges.ubuntu.com/universe.html and see if there are any packages on there you are familiar with/use/like the sound of?
[10:56] <askand> ﻿james_w: quite a lot..but i like the sound of freetennis for example :P
[10:56] <james_w> cool, so look at what name is next to the package, as we need to make sure that they are not currently working on it.
[10:57] <james_w> unfortunately I don't know who that person is, I was hoping they would be on IRC so that we could get a quick answer.
[10:59] <askand> Oh
[10:59] <james_w> would you like to pick another so that we can go ahead and do one, and once we've done that you can proceed with freetennis?
[10:59] <james_w> I don't think there would be any problem in merging this one as the person doesn't seem to be very active.
[10:59] <james_w> Does anyone know William Lima?
[11:00] <askand> he doesnt seem to be very active according to launchpad
[11:02] <james_w> ok, let's go ahead and do it
[11:03] <james_w> if you click the name of the package then you will be taken to a page named REPORT that tells you a bit about what's going on.
[11:04] <james_w> let me know once you've read the page, and if there is something that you don't understand.
[11:04] <TheMuso> Who wants to join me cleaning the sponsors queue somewhat?
[11:05] <james_w> hi TheMuso
[11:05] <TheMuso> Hey james_w.
[11:06] <dholbach> TheMuso: I already did a few and plan to do some more
[11:07]  * directhex is finally working on an actual universe package, rather than main or debian
[11:09] <askand> ﻿james_w: looks pretty clear to me
[11:09] <TheMuso> dholbach: Right, I'm going to clear some as well, since DIF is so close.
[11:10] <james_w> askand: cool, so in this case as it failed to merge cleanly there is a tarball with the results
[11:10] <james_w> askand: if you remove the "REPORT" from the end of the URL you will find the files. Please download and extract the tarball
[11:10] <james_w> (not the .orig.tar.gz one)
[11:10] <dholbach> TheMuso: right - let's chat in here and say which ones we're looking at - so we don't look both at the same :)
[11:11]  * dholbach looks at xmms2
[11:11]  * TheMuso has a lock on spread
[11:11]  * sebner waves
[11:12] <dholbach> hi sebner
[11:12] <sebner> can anybody tell me when a nvidia-glx update is planned (support for 2.6.26 kernel)
[11:12] <askand> ﻿james_w: ok downloaded and extracted the ubuntu.src.tar.gz one
[11:12] <dholbach> sebner: best to ask in #ubuntu-kernel or #ubuntu-x
[11:13] <james_w> askand: cool, so if you go back to the REPORT file you will see a list of conflicted files, we need to sort those out.
[11:13] <sebner> dholbach: cool, thanks =) though 800*600 isn't that bad since this forces me to learn :P
[11:13] <james_w> askand: the first is debian/control, so please open that in a text editor.
[11:15] <directhex> sebner, in intrepid, or generally?
[11:15] <james_w> askand: you will see that on the Ubuntu side we just changed the Maintainer as normal. On the Debian side they changed maintainer as well, but also updated the Build-Depends, and added some more information.
[11:15] <sebner> directhex: intrepid since there we have a new kernel =)
[11:15] <james_w> askand: we want all of Debian's changes, but we want to modify the maintainer field as well.
[11:16] <james_w> askand: but ensure that the "Original-Maintainer:" refers to the new Debian Maintainer.
[11:16] <james_w> askand: got it?
[11:16]  * TheMuso takes a lock on zsnes.
[11:18] <askand> ﻿james_w: hm..how do I ensure that the original-maintainer (﻿bart martens) refers to the new debian maintainer?
[11:19] <gnomefreak> What is the name of the hardy-backports team that you use when a bug needs to be backported?
[11:19] <james_w> askand: the line you leave as "XSBC-Original-Maintainer:" should be "XSBC-Original-Maintainer: Debian OCaml Maintainers <debian-ocaml-maint@lists.debian.org>" rather than "XSBC-Original-Maintainer: Bart Martens <bartm@knars.be>"
[11:20] <james_w> askand: as this line refers to the Debian maintainer, which has changed, so we need to make sure we get the right one.
[11:20] <askand> ah ok got it
[11:21]  * dholbach looks at gtkglarea
[11:21] <askand> ﻿james_w:  and I should also change the build-deps ?
[11:22] <james_w> askand: you should probably go with what Debian has.
[11:23] <askand> ﻿ james_w: yes
[11:23] <james_w> askand: if you look at the last two Ubuntu entries in debian/changelog you can see if Ubuntu changed them, in which case you should look in to it a bit more.
[11:23] <james_w> http://merges.ubuntu.com/f/freetennis/freetennis_0.4.8-3ubuntu2.patch
[11:23] <james_w> that's the Ubuntu changes, and you can see that the Build-Depends weren't modified, so you can just take what Debian has.
[11:25] <askand> ﻿ james_w: ok done
[11:25] <james_w> askand: great, so save that file and we can move on to the next one.
[11:25] <rzr> hi
[11:25] <james_w> askand: feel free to stick anything in a pastebin if you would like me to glance over it.
[11:26] <james_w> askand: the next file is debian/freetennis.8, which is the manpage.
[11:26] <askand> ﻿james_w:  should I also add homepagefield ?
[11:26] <james_w> askand: looking at the changelogs both sides improved the file, so this may be easy or difficult.
[11:26] <rzr> As a debian maintainer I am about to release a package which closes some ubuntu bugs, should I also add (LP:#xyz) in debian/control ?
[11:26] <rzr> then the debian package will just need to be imported
[11:27] <james_w> askand: yup, that's useful to have.
[11:27] <james_w> askand: when merging you want to follow Debian as closely as possible, just sticking with Ubuntu changes where there is good reason to.
[11:28]  * dholbach takes a look at tkdiff
[11:29] <askand> ﻿james_w: how does this look? http://pastebin.com/m38d07c00
[11:30] <james_w> askand: good, we also want the Uploaders line
[11:30] <james_w> askand: and you need to delete the conflict markers and the Debian section.
[11:31] <askand> ﻿james_w: http://pastebin.com/m7b881a22 not sure what the <<<<<<<<< is?
[11:32]  * dholbach takes a look at libofx
[11:32] <james_w> askand: that's one of the conflict markers. They are just there to denote the areas which need some attention. When you are done you need to delete them.
[11:33] <Laney> askand, james_w: If you're trying to merge freetennis, you should be aware of bug #241249
[11:33] <james_w> Laney: thanks
[11:34] <james_w> askand: sorry, that should of course be the first step, check to see if the work has already been done. In this case it has, sorry.
[11:34]  * rzr waves _o/
[11:34] <askand> ﻿james_w:  oh
[11:35] <TheMuso> dholbach: I'm still here, I'm just being careful with a somewhat hackish change in zsnes. :)
[11:35] <james_w> though in this case it apparently happened concurrently, so there was little we could have done.
[11:35] <dholbach> TheMuso: I didn't think you had vanished :)
[11:35] <directhex> dholbach, can never have too many mono merges
[11:35] <dholbach> Mr TheMuso-vich :)
[11:36] <dholbach> directhex: hm?
[11:36] <TheMuso> dholbach: har har har. That still makes me laugh.
[11:36] <james_w> askand: in this case Debian adopted our changes, so we can take their package directly, which is what it means by "sync".
[11:36] <james_w> askand: sorry about that. If you like we can look at another package.
[11:36] <directhex> dholbach, LP:240671
[11:36] <dholbach> bug 240671
[11:36] <dholbach> directhex: what about it?
[11:37] <directhex> dholbach, just commenting. it's the second merge in a couple of weeks, and i wouldn't be surprised if there were more, when more bugs appear
[11:37] <dholbach> right
[11:38] <dholbach> I don't know any mono at all, that's why I asked slomo to take a look at it
[11:38] <rzr> vorian: around ?
[11:38]  * dholbach takes a look at xgrep
[11:39] <RAOF> bigon: Cool; that'll be syncable then.
[11:43]  * TheMuso takes a look at ming
[11:44] <nixternal> wgrant: dunno why it is still doing that...file a bug upstream on that please
[11:44] <nixternal> for smb4k that is
[11:48] <askand> ﻿james_w: no worries :) i think I come back later a bit
[11:48] <james_w> askand: great.
[11:49]  * TheMuso looks at paprefs.
[11:50]  * dholbach lunches
[11:52] <rzr> I guess I have to RTFM again :)
[11:52] <rzr> As a debian maintainer I am about to release a package which closes some ubuntu bugs, should I also add (LP:#xyz) in debian/control when possible?
[11:54] <directhex> ooh, that'd be nice
[11:56] <rzr> i cant find this info on the wiki
[11:57] <rzr> let's ommit them then
[12:00]  * TheMuso looks at extace
[12:06] <RAOF> rzr: You're very welcome to add LP:#xyz tags.  To debian/changelog (that's what you meant, right?).  The syntax is exactly the same as for the BTS, but with "LP: #" rather than "closes: #".
[12:06] <rzr> no my question  was
[12:06] <rzr> can I mix Closes:# and LP:# on the same release ?
[12:07] <RAOF> Yes, absolutely.
[12:07] <rzr> are you sure ?
[12:07] <RAOF> The BTS understands closes: and ignores LP:, launchpad understands LP: and ignores closes:
[12:07] <directhex> which is why LP uses LP: and not closes:
[12:07] <rzr> but debian doesnt care about derived distro bug trackers
[12:08] <rzr> so this info is useless to debian
[12:08] <RAOF> That's right.
[12:08] <rzr> well I wanted to make sure
[12:08] <RAOF> It would be nice if you added them, but you're certainly not expected or obligated to do so :)
[12:08] <rzr> I see benefits and drawbacks :)
[12:09] <rzr> polution vs factorisation
[12:10] <rzr> let's add both then
[12:11] <RAOF> Very good of you, thanks :).
[12:14] <rzr> thank you RAOF , now Let's open a debian specific help desk for copperation
[12:19]  * TheMuso looks at guidedog
[12:27]  * TheMuso looks at rpld
[12:29] <RAOF> rzr: You mean, the Ubuntu version of the Debian utnubu team? :)
[12:30] <rzr> we'll call it the naibed team
[12:32]  * TheMuso looks at apcalc
[12:32] <RAOF> That's got a bit of a ring to it.
[12:32] <Hobbsee> 238 outstanding.  ouch
[12:34] <TheMuso> Hobbsee: Yeah, clearing the sponsors queue will help get that down somewhat.
[12:53] <afflux> siretart: hi... I have some questions about the cryptsetup initramfs script
[12:53] <afflux> siretart: first thing is, I wonder why we don't use udev_settle anymore, and do a "normal" 3-minute sleep
[12:56] <afflux> siretart: second thing is, the break condition in this sleep waits for ${ROOT}, which is the "resulting" device, instead of the cryptsource. I think this is why the sleep does not work for me (on my system, it just hangs. looking at the source, it should be working after 3 minutes though, because the panic condition some lines later checks for $cryptsource again).
[12:57] <wgrant> Has anybody upgraded to Intrepid recently? Am I likely to be condemning my system to a fiery death if I try it now?
[12:57] <jpds> wgrant: Hobbsee has.
[12:58] <afflux> siretart: third thing is, after manually changing the initramfs script  I found out that neither /sbin/cryptsetup nor /lib/cryptsetup/askpass exist. both are referred to from the script.
[12:58] <afflux> wgrant: it works quite well on my desktop machine, currently, except the cryptroot I mentioned above ;)
[12:59] <Hobbsee> wgrant: no, it should be reasonable.  i'd be interested to see if your mime types bugger up though
[12:59] <wgrant> Hobbsee: We shall see, though I don't use anything that uses mimetypes.
[12:59]  * wgrant stopped using cryptroot a while ago.
[12:59] <Hobbsee> wgrant: right, so you don't use nautilus.
[12:59] <siretart> afflux: yeah, I noticed that my merge isn't correct yet. I'm still at setting up a kvm instance for testing
[13:00] <afflux> siretart: it looks like I have a quick solution for the third thing
[13:00] <Hobbsee> wgrant: no matter what you double click on, it'll load in whatever the last program you set was.
[13:00] <siretart> afflux: AFAIC, even in hardy plain crypted partitions seem to be somehwat broken. I see that when I'm trying to manually set them up (read: without d-i)
[13:00] <Hobbsee> at least, that's what i'm finding
[13:01] <siretart> afflux: are you famillar with bzr? - if yes please fix that in a branch. that makes it easier for me to review, okay?
[13:01] <afflux> yup okay
[13:01] <afflux> siretart: udev_settle or (fixed) manual waiting?
[13:02] <afflux> where manual waiting is "check for partition every 100ms"
[13:03] <siretart> sorry?
[13:06] <afflux> siretart: we have two ways to wait for the cryptsource, if it didn't appear yet. We used to use "udevadm settle --timeout=30" in hardy, but changed to do a 180*100ms sleep
[13:07] <siretart> afflux: I think the loop is the only reliable way to go.
[13:07] <afflux> okay
[13:07] <siretart> afflux: because udevsettle only helps if the kernel is currently processing an event which might cause the device to pop up
[13:08] <afflux> I see
[13:08] <siretart> afflux: if you have a very slow device, like an pendrive or slow scsi device that needs intensive initialisiation, udev_settle wont help you
[13:08] <afflux> siretart: which branch should I use for branching? ~siretart/cryptsetup/ubuntu or ~ubuntu-core-dev/cryptsetup/ubuntu
[13:08] <siretart> the one with the latest commit. I think it is the latter one
[13:08] <afflux> okay thanks
[13:11] <vorian> rzr, I am now
[13:18] <siretart> afflux: btw, if you think you think you fixed a bug in a bzr commit, do a 'bzr commit --fixes lp:12345' with the correct bugnumber. lp will automatically associate your branch with the bug
[13:18] <afflux> oh okay, nice to know, thanks
[13:24] <ffm> Hey, I'm a bit bored. How can I search through needs-packaging requests?
[13:26] <wgrant> ffm: Just do an advanced search for the needs-packaging tag at https://bugs.launchpad.net/ubuntu/+bugs?advanced=1
[13:27] <ffm> wgrant: thanks.
[13:31] <dholbach> TheMuso is doing AWESOME work in the sponsoring queue
[13:31] <dholbach> let's join him!
[13:31] <emgent> rheya dholbach :)
[13:32]  * Laney highfives TheMuso 
[13:32] <Laney> Thanks for the uploads :D
[13:32] <TheMuso> dholbach: No longer unfrotunately, I'm starting to find it hard to concentrate, as its getting late  here, so I'll have to call it a night, but will attempt to find time tomorrw to do some more.
[13:32] <TheMuso> gah as evident by my typing. :p
[13:32] <dholbach> TheMuso: I'll do some myself - who else is interested?
[13:33]  * Laney is going to carry on giving you stuff to sponsor ;)
[13:40]  * dholbach checks out sdlmame
[13:42]  * DktrKranz did 5/6 earlier, will do more this evening
[13:42] <dholbach> woohoo
[13:42] <dholbach> thanks DktrKranz
[13:42]  * dholbach high-fives DktrKranz and TheMuso
[13:43]  * DktrKranz high-five-a-day dholbach 
[13:43] <dholbach> hehe
[13:51] <ScottK> DktrKranz: Are you an avscan user or were you just triaging in general when you marked up an avscan bug earlier today.
[13:52] <DktrKranz> ScottK: just triaging.
[13:53] <ScottK> OK.
[13:53]  * ScottK was hoping for someone to package a new upstream.
[13:53] <DktrKranz> IIRC, I subscribed (or assigned) to a bug, feel free to take it if you want to.
[13:54]  * dholbach takes a look at keurocalc-kde4
[13:54] <afflux> siretart: my branch is https://code.launchpad.net/~afflux/cryptsetup/ubuntu.initramfs-fixes . The latest changes are not tested yet, I'll do that now.
[13:54] <DktrKranz> ScottK: myon put it into adoption (or orphaned it), it could be interesting to take maintainership.
[13:55] <ScottK> Yes.  I'm hoping someone will do that.
[13:55]  * ScottK doesn't use it either, but it's a clamav rdepend and currently FTBFS in Intrepid needing the new version.
[13:59] <siretart> afflux: yes, your commits look pretty relevant. will merge them!
[14:02] <afflux> siretart: okay, worked. Only thing is: when not using usplash I get two warnings about not being able to run /sbin/udevsettle because it does not exist. They don't seem to be critical (for me?) though. I also get the message described in bug 151532. But, as the initial reporter states too, the system boots up without any further problems.
[14:02] <DktrKranz> ScottK: if you need it, I can have a look at it, maintaining packages is fine, especially if they are needed by others
[14:03] <ScottK> DktrKranz: I've played with it in testing a bit and it looks like a reasonably decent anti-virus frontend.  I think it's worth keeping.
[14:04] <ScottK> If you want to adopt it in Debian, I know who I could get to sponsor you.
[14:04] <DktrKranz> myon directly?
[14:04] <ScottK> Actually I was thinking sgran (the clamav maintainer).
[14:04] <DktrKranz> I haven't a fixex sponsor
[14:05] <ScottK> He's been decent about sponsoring clamav related NMUs for me.
[14:06] <DktrKranz> I can give it a try, I need to understand package logic before, since I'm not a user, it could be harder
[14:07] <ScottK> It seems reasonably well designed.
[14:08] <ScottK> When I was trying to get clamav 0.92 back to Dapper avscan was a tough one.
[14:09] <DktrKranz> any particular issues?
[14:09] <siretart> afflux: cool. thanks for your commits, I'll merge them into the next upload!
[14:09] <ScottK> I ended up taking the Feisty package, using the Dapper debian/rules, grabbing one file that had the libclamav interfaces out of the avscan internals of the hardy package, slamming them all together and it worked.
[14:10] <ScottK> I couldn't backport the entire Hardy package due to other dependency issues.
[14:10] <DktrKranz> mh... sounds complex
[14:10] <ScottK> In any case that fact that that worked suggest to me a reasonably well designed program with good stable internals.
[14:10] <ScottK> That was complex., but it was a one time problem.
[14:11] <ScottK> The biggest issue with it is it'll need watching as clamav evolves as they have a habit of doing interface changes with no warning.
[14:11] <ScottK> avscan upstream seems responsive to it though.
[14:12] <DktrKranz> are they linked or follow a separate development plan?
[14:13] <ScottK> Separate.  avscan is a user of libclamav.
[14:15] <ScottK> DktrKranz: Why don't you look at what it'd take to get the new avscan packaged and see how comfortable you are with it.
[14:16] <ScottK> DktrKranz: If you need to build against the new clamav on Hardy, it's in the ubuntu-clamav PPA: https://launchpad.net/~ubuntu-clamav/+archive
[14:16] <DktrKranz> I was thinking about it, since we want clamav and no-one jump in to take responsibility in Debian so fare
[14:17] <ScottK> Currently we have 3 A/V gui packages: Klamav, Clamtk, and Avscan.
[14:18] <ScottK> Klamav is very KDE focused.  Clamtk is somewhat limited.  I think having Avscan is useful.
[14:18] <ScottK> It's still under development, so it may well end up being the best of them.
[14:19] <DktrKranz> Avscan is for GNOME, I suppose
[14:19] <DktrKranz> gtk+1.2, wasn't it being removed from Debian?
[14:22] <ScottK> Ah.  That was the other problem.
[14:22] <ScottK> I knew there was something.
[14:22] <ScottK> Who knows, maybe the new version is updated ...
[14:23] <DktrKranz> let's see
[14:23] <ScottK> If not, it'd still be useful to get it updated in Ubuntu so eventually I can backport clamav 0.93 and later.
[14:24] <DktrKranz> looking at myon's comments, new version requires new endeavour, and SONAME handling seems problematic
[14:25] <wgrant> ScottK: Have you not yet managed to convince upstream to be less distro-hostile?
[14:25] <ScottK> So it's a 'learning experience'.
[14:25] <ScottK> wgrant: No.
[14:26] <ScottK> I've asked them to add some Ubuntu specific info to their web site just yesterday.  We'll see how that goes.
[14:26] <DktrKranz> mh... avscan homepage is unreachable
[14:26] <ScottK> That's not a good sign.
[14:28] <ScottK> I can get to it.  It's just pretty empty.
[14:29] <ScottK> Sorry.  Wrong page.
[14:29] <DktrKranz> I get 404
[14:30]  * ScottK too.
[14:32] <cyberix> I have a package in Hardy. The upstream has released a new release. Should I create a huge debdiff and try to get that applied for intrepid or what?
[14:32] <cyberix> i.e. are debdiffs the right tool for all package upgrades?
[14:33] <LucidFox> cyberix> Only within the same upstream version
[14:33] <LucidFox> for a new upstream version, attach the diff.gz
[14:34] <cyberix> LucidFox: Should that contain both packaging and upstream changes or only upstream changes?
[14:34] <LucidFox> Erm... it should contain only packaging changes
[14:34] <LucidFox> diff.gzs by definition contain only packaging changes
[14:39] <cyberix> LucidFox: So how do I get the upstream tar ball updated?
[14:39] <LucidFox> cyberix> The sponsor will download it
[14:39] <LucidFox> and your diff.gz
[14:39] <directhex> (try using uupdate, it's made for this kind of thing)
[14:43] <cyberix> The new upstream release goes throught revu?
[14:44] <LucidFox> cyberix> No.
[14:44] <LucidFox> REVU is only for new packages.
[14:44] <LucidFox> cyberix> You file a bug report on LP, attach the diff.gz and subscribe ubuntu-universe-sponsors.
[14:49] <cyberix> LucidFox: And how do the sponsor know he should get the new upstream tar ball?
[14:49] <persia> cyberix: debian/watch or debian/rules get-orig-source :)
[14:51] <cyberix> And if I'm not aware of the new upstream release, then things will break.
[16:04] <ivoks> motu wannabes?
[16:04] <ivoks> there's one very simple task if someone is interested
[16:05] <persia> ivoks: We try not to use that term :)  What's the task?
[16:05]  * santiago-ve rises hand but is at work ATM
[16:05] <ivoks> there's wifi-radar package in ubuntu
[16:05] <ivoks> it is very old and i'm an official maintainer
[16:05] <ivoks> it's time to drop it and merge debian's package
[16:06] <ivoks> there are only two patches that should be applied to new debian package
[16:06] <ivoks> it's dpatch system, IIRC
[16:06] <ivoks> so, low hanging fruit
[16:06] <ivoks> if no one is interested, i'll do it, but it looks like good exercise...
[16:06] <vorian> ivoks: I requested a sync with bug #240809 for wifi radar
[16:07] <ivoks> vorian: right, wifi-radar was packaged for ubuntu first, and then for debian, so weare out of sync for a very long time; it's time to move on and drop our package
[16:07] <vorian> ah, good good
[16:08] <ivoks> santiago-ve: interested?
[16:08] <santiago-ve> ivoks: aye, but werrr not for now... at work atm :p
[16:08] <dholbach> ivoks: vorian requested a sync - is a merge necessary?
[16:09] <ivoks> dholbach: there is one GUI related patch
[16:09] <ivoks> and one for atheros cards... i don't have atheros, so i can't tell if it's needed any more
[16:09] <dholbach> right
[16:09] <vorian> hmm
[16:10] <ivoks> blaa.... just sync it and move on... just one note
[16:10] <ivoks> last time i checked debian's package, it asked questions during install
[16:10] <ivoks> and it didn't have daemon
[16:10] <ivoks> while ubuntu package didn't ask questions and had daemon for auto-connecting
[16:13] <ivoks> you are free to decide, i don't mind any of those two options
[16:54] <siretart> afflux: I just uploaded your changes to intrepid. thanks for your commits, and keep up your good work! :)
[16:54] <afflux> siretart: thanks and you're welcome ;)
[17:11] <rzr> go a message for me ? i lost it
[20:01] <nand> Hi! I've one package, ike, that is now present on intrepid, and which was not a debian merge (packaged only for Ubuntu). It's now also present in Debian. Upstream plans to do a release this week end: I'll update the debian package on Debian. The deadline in this situation is the debian import freeze, or the feature freeze?
[20:02] <nand> (forgot one sentence in the middle :) => I want to push this new version to ubuntu)
[20:07] <mario_limonciell> nand, you can pull the update from debian afterward after DIF, you will just manually need to request a sync
[20:07] <mario_limonciell> the DIF turns off all automatic syncing
[20:07] <nand> ah ok! So the deadline in this case is feature freeze
[20:07] <nand> cool, thanks!
[20:17] <mario_limonciell> nand, but if you can do it sooner than feature freeze, that's more ideal as you don't have to go and prod as many people :)
[20:18] <nand> I guess so :)
[20:20] <HoellP> hello, can anyone help me with debian packaging?
[20:20] <HoellP> i set up everything and it seems to work
[20:21] <HoellP> but when i try to build, i get the following error:
[20:21] <HoellP> checking for XML::Parser... configure: error: XML::Parser perl module is required for intltool
[20:21] <HoellP> make: *** [config.status] Error 1
[20:21] <ScottK> Then you're missing a build-dep.
[20:24] <Kopfgeldjaeger> HoellP: try libxml-parser-perl
[20:25] <HoellP> but i can't control the packages controlled by pbuilder, can i?
[20:26] <HoellP> ah
[20:26] <HoellP> *working*
[20:42] <highvoltage> g'night motus
[20:51] <cody-somerville> night highvoltage
[21:50] <norsetto> heya heya
[21:53] <RainCT> hey norsetto
[21:54] <norsetto> Hola RainCT
[21:54] <RainCT> :)
[22:02] <geser> Hi norsetto
[22:10] <norsetto> heya geser, any new event on the horizon?
[22:11] <lukehasnoname> http://www.imdb.com/title/tt0119081/
[22:11] <norsetto> huats!!!
[22:11] <laga> i love that movie. it's a bit scary sometimes tho
[22:11] <huats> norsetto: !!!
[22:17]  * norsetto must be the only living being on this planet that not only has not seen that movie but before yesterday didn't even know it existed
[22:17]  * ajmitch waits for the laptop to load to be able to see what it is
[22:17] <ajmitch> ubuntu needs to boot faster :)
[22:17] <persia> ajmitch: You need a solid-state drive...
[22:18] <laga> no. ubuntu needs to boot faster. :)
[22:18] <ajmitch> wouldn't make it much faster
[22:18] <persia> Well, maybe.  I recently saw a 27 second bootchart for Ubuntu.
[22:18]  * ajmitch needs to not run certain things like apache, mysql/postgresql, zope, etc on the laptop
[22:18] <persia> Yes.  That would do it :)
[22:19] <laga> heh
[22:19] <ajmitch> oh, and an openldap server, of course
[22:20] <ajmitch> all the useful things I need to test on a box somewhere :)
[22:20] <persia> ajmitch: Hmm.  You need a laptop with two distinct computers (one headless with internal serial console bridge).  That way you can boot quick for client stuff, and still play with your server.
[22:21] <ajmitch> heh
[22:21] <ajmitch> sadly it's because it's faster than the desktop box I have at work
[22:45] <james_w> persia: mind if I take cecilia out for a dance?
[22:47] <persia> james_w: Please do.  If you find a way to get her to play with the updated csound, I'd be especially happy.
[22:47] <james_w> you mean debian bug 438611??
[22:48] <james_w> or debian bug 476300?
[22:48] <Zombie> I have an advisory for Ubuntu Hardy/.
[22:48] <Zombie> The version of Open Arena included is Deprecated.
[22:49] <Zombie> And will not play on line with other Open Arena servers.
[22:49] <ScottK> What does deprecated mean in Open Arean terms?
[22:49] <ScottK> Ah.
[22:49] <ajmitch> various games tend to do this, unfortunately
[22:50] <norsetto> james_w: I think bug 438611 is obsolete now
[22:50] <Zombie> Another game that is broken, but because of technical issues is Warzone 2100
[22:50] <Zombie> Warzone 2100 used to operate fine under Gutsy.
[22:50] <Zombie> Now it skips like it uses software rendering
[22:50] <ajmitch> are there bugs failed about these issues in launchpad?
[22:51] <james_w> norsetto: yep, I just followed the paper trail all the way to the end.
[22:51] <norsetto> filed failed or failed filed?
[22:51] <ajmitch> norsetto: forgive me, I was looking at another screen while typing :P
[22:51] <Zombie> One more bug.
[22:52] <Zombie> OpenVPN deletes its own user account when upgrading from Gutsy causing it not to launch.
[22:53] <norsetto> ajmitch: ever seen my typing? Thats something to ask to be excused about
[22:53] <ajmitch> Zombie: again, launchpad is the first place to go to put in bugs
[22:54] <ajmitch> it may still get lost, but at least there'll be a record of it beyond 5 minutes of IRC :)
[22:58] <EagleScreen> hello
[22:58] <EagleScreen> i am learning to use pbuilder
[22:59] <EagleScreen> what happens if i am running Debian and i want to build a Ubuntu hardy package?
[22:59] <EagleScreen> i think i should use: sudo pbuilder update --distribution DIST-NAME --override-config
[22:59] <EagleScreen> in addiction, should I change repositories to hardy?
[23:00] <persia> EagleScreen: You might want to get debootstrap and pbuilder from Ubuntu to ease creating the chroot, but once you have a chroot, you can just build normally.
[23:01] <persia> Note that there are some extra checks in the developer tools (e.g. dpkg-buildpackage) in Ubuntu to verify complinace with additional Ubuntu policies that you'll miss working from Debian: it may also be worth having a working chroot with Ubuntu for building the packages.
[23:01] <EagleScreen> but i want to build for Debian and also for Ubuntu
[23:01] <james_w> persia: hmm, do you know if the patch in debian bug 476300 is sufficient for the updated csound?
[23:02] <ScottK> persia: The Debian debchroot knows about Ubuntu releases.
[23:02] <persia> ScottK: It does?  Cool.
[23:02]  * persia hasn't used Debian dev tools in a bit.
[23:03] <james_w> if an upload fixes a CVE then do I need to do anything more than mention the CVE number for it to be correctly tracked?
[23:03] <persia> james_w: My memory from the csound mailing list was that there was a more complex issue involved, and that the regex described served more to protect cecilia than as the main cause of incompatibility.  You might test it, and see what you find.
[23:04] <ScottK> james_w: There is a separate CVE tracker.
[23:05] <james_w> ScottK: is it based on changelog notification, or is it more manual than that?
[23:05] <ScottK> It's more manual than that.
[23:05] <persia> Anyone from MOTU SWAT around?
[23:05] <ScottK> emgent would know the details.
[23:05] <persia> james_w: If nobody steps up with details, ask in #ubuntu-hardened
[23:05] <EagleScreen> then, i dont need to change nothing to build for Ubuntu??
[23:05] <ScottK> james_w: You should also go back and look at which supported releases are also vulnerable.
[23:05] <james_w> there's no bug in lp, so I want to make sure that it gets picked up as we get the fix for free.
[23:06] <james_w> ah -hardened, thanks.
[23:06] <emgent> uhm ?
[23:06] <persia> james_w: Please do create a bug in LP, and link the bug to a CVE.
[23:06] <ScottK> james_w: Yeah.  You'll want to make bug and then nominate it for all affected releases.
[23:06] <ScottK> james_w: Now that emgent is here, I'm sure he can guide you through the process.
[23:06] <EagleScreen> i will investigate
[23:06] <persia> And subscribe ubuntu-security or motu-swat, as appropriate
[23:07] <ScottK> EagleScreen: You need to make a pbuilder chroot for the appropriate ubuntu release, but you can do it using the Debian packages.
[23:07] <james_w> hi emgent, I'm merging a package that includes a CVE fix from Debian, and I just want to make sure that I do the right things.
[23:08] <emgent> hi james_w uhm, ok
[23:08]  * ScottK needs to run off.  See you all later.
[23:08] <emgent> please join -hardened we can talk in this room
[23:08] <emgent> bye ScottK
[23:09] <EagleScreen> thanks Scottk, i supuse it must be done using command i said, but is needed anything more? may be temporaly use ubuntu repository in menu.lst???
[23:09] <EagleScreen> godbye scottk