[00:00] <joejaxx> LaserJock: why? :\ that violates debian packaging policy does it not?
[00:01] <ScottK> minghua: I would imagine so, but I haven't looked to see if stuff if failing to build there or not.
[00:01] <ScottK> minghua: Situation should be identical.
[00:01] <joejaxx> hello ScottK minghua
[00:01] <ScottK> In particular, their version of mime-tools doesn't have the same dependency as the newer one that just FTBFS for me.
[00:01] <minghua> joejaxx: Not necessarily.  What is your kde4base-data version?
[00:01]  * ScottK runs off to dinner.
[00:01] <minghua> ScottK: Let me have a look.
[00:03] <minghua> ScottK: Do you have another example (that builds arch:any packages)?  Mime-tools is arch:all.
[00:03] <LaserJock> joejaxx: has that stopped people before? ;-)
[00:04] <joejaxx> LaserJock: transitional packages and conflicts are nice :)
[00:05] <joejaxx> minghua:   Installed: 3.94.0-0ubuntu1
[00:05] <TheMuso> jdong, nenolod, first tests with a basic headset and a jazz trio track reveal some mushiness. I need to encode a track with iTunes, faac, and have an uncompressed version as well to do some real testing with my good headphones.
[00:06] <joejaxx> LaserJock: yeah but it werid to me to see that lol :P
[00:06] <joejaxx> LaserJock: weird*
[00:07] <joejaxx> that is one of the reasons i have not uploaded a -settings package
[00:07] <minghua> joejaxx: I wonder if there is any versioned conflicts/replaces between kde4base-data and other packages.
[00:07] <joejaxx> because packages are not supposed to do that
[00:07] <joejaxx> minghua: i wish there was
[00:07] <joejaxx> but it would want to remove those packages if it did
[00:08] <minghua> joejaxx: So you checked there wasn't?
[00:08] <joejaxx> Replaces: kdelibs5-data (<< 3.93.0-0ubuntu1~ppa1), kde4multimedia-data (<< 3.93.0-0ubuntu1~ppa1)
[00:08] <joejaxx> Conflicts: kde4multimedia-data (<< 3.93.0-0ubuntu1~ppa1)
[00:08] <joejaxx> wth is ppa doing in there?
[00:08] <minghua> joejaxx: You are installing an auto-backported package, versioned relations may well be broken.
[00:09] <minghua> Well...
[00:09] <joejaxx> stuff in -backports is automatically backported?
[00:09] <joejaxx> lol wth?
[00:09]  * minghua checks the hardy version.
[00:09]  * LaserJock hands joejaxx some wth pills ;-)
[00:09] <minghua> joejaxx: auto-backported after manual checking/confirming.
[00:09] <joejaxx> it seems hacky for us to be doing that lol
[00:10] <joejaxx> minghua: sure :)
[00:10] <LaserJock> joejaxx: umm, that's backports
[00:10] <joejaxx> LaserJock: that stinks :\
[00:10] <minghua> Hah.  There is *no* hardy version of kde4base.  It must have been backported from PPA. :-)
[00:11] <joejaxx> :(
[00:11] <joejaxx> i thought that was the whole point of the debian packaging policy
[00:11] <joejaxx> to stop things like this from happening
[00:11] <joejaxx> lol
[00:11] <joejaxx> not to go around it :\
[00:11] <LaserJock> I get kde4 from ~kubuntu-members-kde4 PPA
[00:11] <joejaxx> yeah
[00:11] <LaserJock> but it's got some issues still presently
[00:12] <joejaxx> the archive should be in a more stable state than a ppa :P
[00:12] <joejaxx> package wise
[00:12] <joejaxx> since it is official :D
[00:12] <LaserJock> well, it's -backports
[00:12] <LaserJock> there's only like a couple people that work on it
[00:12] <minghua> joejaxx: I think you need the 3.95.0-0ubuntu1~gutsy1 version of kde4base-data in -backports for everything to work properly.
[00:12] <minghua> joejaxx: However it currently FTFBS.
[00:14] <joejaxx> LaserJock: i do not know what to say :(
[00:14] <minghua> If you don't like the status of -backports, join the team to work on it. :-)
[00:14] <joejaxx> lol i am not motu :(
[00:14]  * minghua personally won't touch -backports without a pole.
[00:15] <LaserJock> joejaxx: it doesn't take being a motu
[00:15] <minghua> You don't need to be an MOTU to work on -backports.
[00:15] <minghua> Just ask jdong. :-P
[00:15] <joejaxx> minghua: i am more worried about the DPP and the state of the archive's integrity
[00:15] <joejaxx> :\
[00:15] <minghua> DPP?
[00:15] <LaserJock> hehe
[00:16] <joejaxx> debian packaging policy
[00:16] <LaserJock> there are way bigger issues than a FTBFS and a slightly broken package to worry about
[00:16] <minghua> Oh.  It's usually called just "Debian Policy".
[00:16] <joejaxx> oh ok
[00:17] <LaserJock> it just needs to get fixed, that's all
[00:17] <LaserJock> happens all the time
[00:17] <joejaxx> lol
[00:18] <minghua> We still get "can't install, broken dependencies" bugs against gutsy once in a while, and don't have enough manpower to fix them, let alone gutsy-backcports.
[00:21] <LaserJock> joejaxx: check out http://qa.ubuntuwire.com/debcheck/ for instance
[00:22] <Hobbsee> TheMuso: ping
[00:22] <TheMuso> Hobbsee: pong
[00:23] <joejaxx> LaserJock: :(
[00:23]  * Hobbsee wishes they wouldn't automatically crackport kde4.
[00:25] <joejaxx> Hobbsee: :)
[00:25] <Hobbsee> heya joejaxx!
[00:25] <LaserJock> well, there's KDE4 packages flying everywhere
[00:25] <joejaxx> hi
[00:25] <LaserJock> it's hard to know what to use
[00:25] <joejaxx> official repos! :D
[00:25] <joejaxx> lol
[00:26] <Hobbsee> LaserJock: not crackports.
[00:26] <joejaxx> lolol
[00:26] <Hobbsee> LaserJock: kde4 ppa is better, iirc
[00:26] <joejaxx> will it fix my broken package system ? :D
[00:26] <joejaxx> lol
[00:26] <azeem> huh, I've been reading `crackpot' all the way
[00:26] <joejaxx> azeem: LOL
[00:26] <joejaxx> ah interesting
[00:27] <LaserJock> joejaxx: well, kinda
[00:27] <joejaxx> the launchpad buildds remove packages
[00:27] <joejaxx> where is this magically package fixing ppa?
[00:27] <joejaxx> :(
[00:29]  * joejaxx is not going to use his ppa until the remove package option is implemented :D
[00:29] <joejaxx> :P
[00:29]  * joejaxx is bored
[00:29] <joejaxx> :(
[00:30] <LaserJock> joejaxx: what the heck are you talking about?
[00:30] <joejaxx> the kde4 ppa
[00:30] <joejaxx> that everyone is talking about
[00:31] <LaserJock> should be https://launchpad.net/~kubuntu-members-kde4/+archive
[00:31] <LaserJock> but it's not all the way updated yet, but it does seem to work a bit better
[00:34] <joejaxx> gah
[00:36] <LaserJock> joejaxx: what are you wanting to install?
[00:36] <joejaxx> kde4
[00:36] <LaserJock> well, how much of it?
[00:36] <joejaxx> just the DE
[00:37] <LaserJock> well, you can probably just do kdebase then
[00:38] <joejaxx> yeah i really do not know what to install package wise i just followed the instructions on the kubuntu website
[00:38] <LaserJock> http://kubuntu.org/announcements/kde4-rc2.php ?
[00:39] <joejaxx> i have not used kde since version 1.0
[00:39] <joejaxx> no not that one there was another one
[00:40] <LaserJock> I think the link I gave is the latest and probably best to go on
[00:40] <joejaxx> yeah
[00:40] <joejaxx> bah
[00:41] <joejaxx> i need to for apt to remove these packages now
[00:41] <joejaxx> force*
[00:44] <joejaxx> fun
[00:44] <joejaxx> hello minghua
[00:44] <joejaxx> MatthewV: *
[00:44] <MatthewV> hi joejaxx
[00:45] <ScottK> minghua: How about libmail-box-perl
[00:45] <joejaxx> oh perl
[00:45] <joejaxx> :)
[00:45] <joejaxx> perl is fun
[00:45] <ScottK> minghua: Oops.  That's arch all too
[00:45] <ScottK> joejaxx: You got the first two letters right.
[00:46] <joejaxx> LOL
[00:49] <joejaxx> bah
[00:49] <joejaxx> this is hacky
[00:54] <jscinoz_> persia are you here?
[00:55] <minghua> ScottK: Right. So there were never built in sbuild for Debian.
[00:56] <ScottK> OK.  So it won't hit Debian until it hits an arch:any package?
[00:58] <slangasek> in terms of sbuild, yes
[00:59] <jscinoz_> hmm
[01:00] <jscinoz_> are any of you guys familiar with the licensing on the quake3 SDK?
[01:01] <DarkMageZ> didn't the quake 3 engine get gpl'ed?
[01:01] <joejaxx> that is what i thought
[01:02] <joejaxx> yeap
[01:02] <joejaxx> the source for quake 3 is gpl
[01:04] <joejaxx> joejaxx@venus:~/Desktop$ head -n 2 quake3-1.32b/COPYING.txt
[01:04] <joejaxx>                     GNU GENERAL PUBLIC LICENSE
[01:04] <joejaxx>                        Version 2, June 1991
[01:04] <joejaxx> :)
[01:04] <jscinoz_> hmm
[01:05] <jscinoz_> im packaging a supposedly gpl game, UrbanTerror that is based on the quake 3 engine, however it includes a very non-GPL license of the "Quake3 SDK"
[01:05] <joejaxx> interesting
[01:06] <jscinoz_> this is what persia said about it
[01:06] <jscinoz_> "Given that ID licenses this with an explicit prohibition to not "disassemble, reverse engineer, decompile, modify or alter the Software including, without limitation, creating or developing extra or add-on levels for the Software;", I’m not convinced FrozenSand LLC has the right to distribute this."
[01:06] <joejaxx> oh ok
[01:08] <joejaxx> kde4 is installing :)
[01:09] <jscinoz_> hmm
[01:09]  * minghua agrees with persia.
[01:09] <joejaxx> i wonder where they got that from
[01:10] <joejaxx> jscinoz_: how old is this game?
[01:10] <jscinoz_> im packaging the release from 20th of dec 2007
[01:10] <jscinoz_> so not old at all
[01:10] <joejaxx> bbl going use kde for the first time since 1998
[01:10] <joejaxx> :)
[01:10] <jscinoz_> argh
[01:11] <jscinoz_> what should my preinst script be called to have it automatically executed before installation?
[01:11] <minghua> preinst is the correct name.
[01:13] <jscinoz_> thanks
[01:14] <joejaxx> uh oh
[01:15] <joejaxx> all i see is a background lol
[01:18] <zul> heylo
[01:18] <joejaxx> hello
[01:18]  * joejaxx is having fun with trying to get the kde4 de to run correctly :)
[01:26] <bddebian> Heya
[01:28] <joejaxx> hi
[01:28] <joejaxx> i got kwin to run :)
[01:28] <bddebian> Hi joejaxx, congrats :)
[01:28] <joejaxx> and i used xterm -display :0
[01:28] <joejaxx> so now i have a terminal
[01:28] <joejaxx> lol
[01:28] <joejaxx> and that is it
[01:29] <joejaxx> X Error: BadDrawable (invalid Pixmap or Window parameter)
[01:29] <ScottK> But it's a KDE4 terminal, so that makes it totally cool.
[01:29] <joejaxx> ScottK: :)
[01:43] <nenolod> jscinoz_, that license is outdated, cause urbanterror runs on ioquake3 now
[01:44] <jscinoz_> hmm
[01:44] <jscinoz_> thats what i though
[01:44] <jscinoz_> do any sections of the game remain under ID softwares copyright?
[01:45] <jscinoz_> because persia also mentions "9) debian/copyright is fairly comprehensive, but still fails to mention that portions of the code are copyright Id Software. Might also be nice to have explicit licensing for the packaging."
[02:02] <slangasek> nenolod: why does upse-audiacious only Recommend: audacious instead of depending on it?  Is it somehow useful without the application?
[02:05] <jscinoz_> what exit code would need to be in my preinst screen to make it cancel the package installation
[02:05] <slangasek> any non-zero exit code
[02:05] <jscinoz_> i tried that
[02:05] <jscinoz_> 1 and 2 both continued installation
[02:06] <slangasek> then your preinst isn't reaching that exit statement
[02:06] <jscinoz_> can i pastebin it, its only 16lins
[02:06] <jscinoz_> lines*
[02:06] <slangasek> sure
[02:07] <slangasek> (I don't think there's a line limit on pastebin, anyway?)
[02:07] <jscinoz_> no, but i wouldnt want someoen to go over a huge amount of script :P
[02:07] <jscinoz_> http://pastebin.ubuntu-nl.org/51167/
[02:08] <slangasek> jscinoz_: well, the comparison with "$RET" is going to be case-sensitive; I think it's supposed to be lower case
[02:08] <slangasek> (I had a doubt about this last time you showed this script, but neglected to comment)
[02:08] <jscinoz_> hmm
[02:09] <jscinoz_> one second
[02:10] <jscinoz_> yep that works
[02:10] <jscinoz_> one other thing
[02:11] <jscinoz_> see how it echoes that the user didnt accept the license, if the package is installed via a graphical tool (ie synaptic or gdebi-gtk) is that still going to show up?
[02:11] <slangasek> it's going to show up wherever the rest of the console output goes
[02:11] <jscinoz_> would it be better to call an info template?
[02:11] <slangasek> I don't think so
[02:12] <slangasek> I think the license prompt, with a clear explanation that refusing the license will abort the installation, is all you should need
[02:12] <jscinoz_> ok thanks
[02:12] <Romney08> Launch A New Type Of Marshall Plan Unifying Nonmilitary Sources Of Power To Support Moderate Muslims. As President, Governor Romney will call together our Middle East allies and the major nations of the developed world to establish a "Partnership for Progress and Prosperity."
[02:12] <Romney08> This Partnership will assemble the resources of all developed nations to assure that threatened Islamic states have public schools, micro-credit and banking, the rule of law, human rights, basic health care, and competitive economic policies. Resources would be drawn from public and private institutions, and from volunteers and NGOs.
[02:12] <slangasek> !ops | Romney08
[02:12] <ubotu> Romney08: Help! Hobbsee, Riddell, sladen, fbond, mneptok, gnomefreak, Seveas, dholbach, elkbuntu or PriceChild!
[02:14] <jscinoz_> in the changelog, is (LP: #179646) the correct format for saying which bug the package closes?
[02:15] <ScottK> Yes
[02:15] <Romney08> GOVERNOR ROMNEY: "Are we going to stay ahead of the world, are we going to lead the world, or are we going to instead pull up the drawbridge and try to hang on to everything we've got and say we can't compete with the world?" (Ryan J. Halliday, "Romney Defends His Health-Care Plan," Nashua Telegraph, 6/7/07)
[02:15] <Romney08> GOVERNOR ROMNEY: "[W]e face a much tougher competitor or group of competitors coming from Asia than we've ever faced before. Asia is tough. There are a lot of Asians. They are hard working people. And they’re going to give us a run for our money in terms of our economic vitality." (Governor Mitt Romney, Remarks At The Club For Growth, 3/29/07)
[02:17] <jscinoz_> go away kthn
[02:18] <jscinoz> slangasek, when i make the install end via the exit status 1 in preinst, do i need to do anything to clean up after that?
[02:18] <slangasek> jscinoz: nope - if the preinst fails, there's nothing to clean up because that's the first step of installing a package
[02:20] <slangasek> Hobbsee: hi, you may want to summarily execute Romney08's connection
[02:20]  * Fujitsu would agree with slangasek.
[02:20]  * ScottK too
[02:20] <elkbuntu> cs kb Romney08
[02:20] <elkbuntu> stupid / key :(
[02:20] <Fujitsu> Thanks elkbuntu.
[02:20] <ScottK> elkbuntu: Thanks
[02:20] <Hobbsee> slangasek: right, sorry.
[02:21] <slangasek> heh, no worries
[02:21] <minghua> elkbuntu: Maybe -devel too.  He appeared there as well.
[02:21] <slangasek> TBH, that's the weirdest bit of political spam I've ever seen
[02:21] <Hobbsee> nuked
[02:21] <jscinoz> lol
[02:22] <slangasek> hum, cheers, whoever that was
[02:22] <azeem> Romney08 is still in #u, btw
[02:22] <Hobbsee> you're welcome
[02:23] <Hobbsee> too slow, apparently
[02:23] <Hobbsee> elkbuntu: did you get him in there?
[02:23] <joejaxx> elkbuntu: ! :D
[02:24] <elkbuntu> hi joejaxx! :)
[02:24] <joejaxx> :)
[02:24] <joejaxx> i just wiped my install
[02:24] <joejaxx> giving kde4 another chance :)
[02:25] <elkbuntu> heh
[02:25] <elkbuntu> i'm not even going to bother until at least one point release
[02:25] <joejaxx> :)
[02:26] <joejaxx> elkbuntu: i have not used kde since version 1.0
[02:26] <joejaxx> lol
[02:26] <elkbuntu> joejaxx, every time i go to use kde, i want to make it work like gnome, so i just give up and go back to the devil i know ;)
[02:26] <ScottK> joejaxx: KDE 4.0 is not even feature complete.  If you really want to try KDE, either try KDE 3.5 or wait for 4.1.
[02:26] <joejaxx> lol :)
[02:27] <joejaxx> ScottK: i do not like 3.5 :\
[02:27] <ScottK> Then I'd wait unless you just want to play around.
[02:27] <joejaxx> oh ok
[02:27] <ScottK> A lot of apps aren't ported or the ports aren't complete.
[02:27] <Fujitsu> ScottK: What was the rationale for leaving the completeness to a point-release? Just so they could say they got KDE4 out the door early?
[02:28] <joejaxx> it is installing already so i might as well
[02:28] <joejaxx> Fujitsu: is it not late? i thought it was supposed to be released in december
[02:28] <imbrandon> Fujitsu: 4.0 wasent supose to ever be feature complete
[02:28] <ScottK> Fujitsu: I think it was that the KDE APIs are stable enough to reliably develop on, so call it 4.0 for API stability, but dunno.
[02:28] <Fujitsu> imbrandon: Well that's silly.
[02:28] <imbrandon> ( and its late not early )
[02:28] <imbrandon> Fujitsu: no, api stability for porting apps
[02:28] <Fujitsu> joejaxx: Well, not *too* late, then.
[02:29] <minghua> There was a long blog post from a KDE dev talking about this.
[02:29] <imbrandon> same happened with kde 3 and kde 2
[02:29] <imbrandon> :)
[02:29] <minghua> http://aseigo.blogspot.com/2008/01/talking-bluntly.html
[02:29] <ScottK> Which is why I think this "we have to focus on KDE4 so no Kubuntu LTS" seems really odd to me.
[02:29] <joejaxx> is that why some of the versioning is still 3.9x?
[02:29] <ScottK> Since the final isn't released yet
[02:29] <wolfger> Can somebody help me figure where I went wrong with debhelper?
[02:29] <minghua> Worth reading, though I'm not sure I agree with their rationale, at least you know what they think about it.
[02:30] <ScottK> Definitely worth reading.
[02:30] <ScottK> wolfger: Probably, but we'll need some details.
[02:30] <Fujitsu> ScottK: It sounds strange that we're dropping LTS because of some incomplete preview.
[02:30] <wolfger> ScottK: http://paste.ubuntu-nl.org/51169/
[02:30] <ScottK> Fujitsu: Absolutely.
[02:31]  * Hobbsee sets a ban on *!*@*!#ubuntu-ops
[02:31] <joejaxx> yay
[02:31] <joejaxx> all ban
[02:31] <Fujitsu> Better to do that in #ubuntu, I think. That would make #ubuntu-ops happy.
[02:33] <Hobbsee> hehe
[02:33] <ScottK> wolfger: I'm in the middle of stuff, so don't really have time to look.  I'd suggest also pastebinning your debian/rules
[02:34] <wolfger> ok, I'll do that, and probably pick back up tomorrow...
[02:48] <joejaxx> hmm
[02:48] <joejaxx> kde4 is not dual screen aware
[02:48] <joejaxx> fun
[02:52] <StevenK> joejaxx: That's a "feature"
[02:52] <DarkMageZ> joejaxx, file a bug in the kde bug tracker =D this soon to release would trip them out =D
[02:53] <joejaxx> lol
[02:54] <StevenK> "We have spent so long writing KDE 4 all of us lost our jobs and can't afford dual screen setups any more."
[02:54]  * StevenK hides
[02:54] <joejaxx> Lol
[02:54] <ion_> Typical to KDE, somewhere among the thousands of checkboxes there’s one labeled “disable multiscreen support” and it’s checked by default. ;-)
[02:54] <joejaxx> the system config for kde4 is not launching  for me
[02:55] <joejaxx> and plasma looks like it is in 8bit mode
[02:55] <DarkMageZ> you can launch it from the command line
[02:55] <StevenK> The system is not configurable in KDE 4.
[02:55] <DarkMageZ> /usr/lib/kde4/bin/systemsettings
[02:55] <joejaxx> DarkMageZ: command??
[02:55] <joejaxx> ok
[02:55]  * StevenK waits for ScottK to snap.
[02:55] <joejaxx> wow
[02:55] <joejaxx> that worked
[02:56] <DarkMageZ> kde4's rc2 reminds me of microsoft's alpha's.
[02:56]  * RAOF boggles quietly
[03:00] <joejaxx> DarkMageZ: it worked when i logged out
[03:00] <joejaxx> and logged back in
[03:01] <DarkMageZ> sounds like "restart your computer" as far as i'm concerned.
[03:02] <joejaxx> yeah
[03:03] <joejaxx> also when i hit log out on the menu
[03:03] <joejaxx> it brings up the log out dialog
[03:03] <joejaxx> which makes no sense to me since the other options are available right under log out on the menu
[03:04] <joejaxx> i need to find out what resolution this is running in
[03:04] <joejaxx> xrandr is broken because of Xinerama
[03:08] <joejaxx> anyone have any suggestions? :)
[03:08] <joejaxx> :P
[03:08] <joejaxx> hello Toadstool :D
[03:14] <joejaxx> hey LaserJock
[03:14] <LaserJock> hmm
[03:15] <LaserJock> I can't seem to get pbuilder-dist to work
[03:16] <LaserJock> has anybody used it lately?
[03:23] <joejaxx> is packages.debian.org down for anyone else?
[03:25] <LaserJock> down for me
[03:32] <nenolod> slangasek, there are other programs which can load audacious plugins and use them
[03:32] <minghua> packages.d.o is up here, FWIW.
[03:34] <nenolod> slangasek, however, you are indeed correct, upse-audacious should probably be a Depends:
[03:34] <nenolod> slangasek, i'll fix it when i upload 0.5
[03:34] <nenolod> :D
[03:38] <ion_> Could i get a second advocation for http://revu.tauware.de/details.py?package=hardware-connected (a program that checks whether given hardware is connected to the system, useful for scripting)? Thanks.
[03:43] <jscinoz> can anyone see any references to GPLv3 on either of these manpages (http://pastebin.ubuntu-nl.org/51174/) (http://pastebin.ubuntu-nl.org/51173/), persia says there is one that i need to change, but i cant see it anywhere in them
[03:43] <nenolod> ion_, package looks fine. if debian import freeze wasn't in effect, i'd say it might be easier just to submit it to debian
[03:44] <nenolod> ion_, at any rate, not a motu, so can't advocate ;p
[03:44] <LaserJock> nenolod: I don't think that DIF should dissuade people from getting packages into Debian
[03:45] <nenolod> LaserJock, well i mean putting it in debian as a way to put it in ubuntu
[03:45] <nenolod> LaserJock, although he could do a sync bug
[03:45] <LaserJock> yep
[03:45] <nenolod> nobody answered my question though about collateral examples of work when applying to be a MOTU though
[03:45] <ion_> To submit it to Debian, do i need to get someone to sign up as its maintainer? I’m not running Debian anywhere.
[03:46] <nenolod> e.g. does stuff in Debian that is in Ubuntu count as collateral examples of work? ;p
[03:47] <nenolod> ion_, not really
[03:47] <nenolod> ion_, it's fully possible to maintain packages in debian and use ubuntu -- all you need to do is make sure they build on sid
[03:48] <nenolod> ion_, you can make a pbuilder to accomplish that ;)
[03:48] <ion_> True...
[03:49] <minghua> nenolod: I would disagree.  I think it's quite irresponsible if the maintainer doesn't use the package (in the intended system) him/herself.
[03:49] <nenolod> minghua, well, i run a debian desktop on alpha and ubuntu on amd64 for multilib
[03:49] <nenolod> minghua, it's a pretty nice alpha, and i do test my packages, but the amd64 is much faster ;)
[03:50] <minghua> nenolod: I am talking about "all you need to do is make sure they build on sid".
[03:50] <minghua> nenolod: I think it's bad advice.
[03:50] <nenolod> minghua, hmm, thinking about it, i agree
[03:51] <nenolod> minghua, i would think testing it somehow is implied though (e.g. pbuilder --login, vmware, etc)
[03:52] <minghua> nenolod: Yeah, brief testing is good enough for me, as long as you also use it in some similar system (Ubuntu, or Debian stable/testing).
[03:52] <nenolod> minghua, yeah. of course, i don't use the upse package (i build the upse package using an hg snapshot for local use)
[03:52] <nenolod> :P
[03:53] <nenolod> minghua, but i do test the package before i send it off
[03:54] <minghua> nenolod: Running a newer version can be excused. :-)
[03:54] <nenolod> once i start packaging my playstation emulator, it'll be the same thing. ;)
[03:54] <minghua> By "use it", I mean the package, not necessarily the same version.
[03:55] <wasabi> Hiya! Looking for the help on how to request a merge in this day and age.
[03:55] <nenolod> minghua, at any rate, i'm still wondering if work in debian counts as evidence of packaging quality in MOTU. ;)
[03:55] <LaserJock> nenolod: it definitely can be taken into consideration
[03:56] <nenolod> ok, groovy.
[03:56] <nenolod> because i maintain some amount of packages (13 at the moment) in debian, and 8 of them are in ubuntu
[03:56] <nenolod> ;)
[03:57] <minghua> nenolod: It is.  Debian work was an big part of the reasons in my application to MOTU.
[03:57] <nenolod>   + pulseaudio support patches for audacious (my only major work in Ubuntu only atm)
[03:57] <minghua> nenolod: Though the application procedure then was pretty different than what it is now...
[03:57] <nenolod> minghua, yes, that's why i am wondering
[03:59] <nenolod> oh well, i'll apply in a couple of months then, as i get more ubuntu-specific work done
[04:00] <nenolod> i should probably poke somebody to look at fixing ia32-libs again :D
[04:22] <guest22> I'd like to request a review of http://revu.tauware.de/details.py?package=photoml  It's already been advocated once (the previous upload, at least), so it should be very close to being acceptable.
[05:01] <ScottK> StevenK: You've missed it by years.
[05:02]  * StevenK whistles innocently.
[05:03] <Hobbsee> wha'ts he missed?
[05:03] <ScottK> [21:55] * StevenK waits for ScottK to snap.
[05:04]  * ScottK goes to be now.
[05:04] <ScottK> be/bed
[05:04] <ScottK> Urgh.
[05:04] <Fujitsu> There was some nice KDE4 criticisum above.
[05:04] <Fujitsu> *criticism
[05:04] <Hobbsee> ah right
[05:04] <Hobbsee> Fujitsu: well, yeah, tha'ts known
[05:04] <ScottK> I would say Kubuntu criticism.  I understand why KDE is doing what it's doing.
[05:04]  * Fujitsu shoots people who still use .htm in this day and age, thus causing the world to explode when one drops index.htm from DirectoryIndex declarations.
[05:05]  * Hobbsee is looking forward to the final packages being done soon, so that they can actually be fixed to not die when attempting to install.
[05:05] <ScottK> I don't understand why Kubuntu going out of it's way to hang out a sign that says "For 'enthusiasts' only"
[05:05] <ScottK> Good night.
[05:05] <Fujitsu> ScottK: This looked like more general KDE.
[05:05] <Fujitsu> Night ScottK.
[05:08] <ion_> fujitsu: A bunch of packages ubuntu-desktop depends on install .jpg files. :-P
[05:59] <joejaxx> i am back :)
[05:59] <joejaxx> is anyone else? :D
[06:09] <parthan> joejaxx, doesn't fluxbuntu support non-free drivers?
[06:12] <joejaxx> parthan: ?
[06:13] <joejaxx> sure
[06:13] <joejaxx> why?
[06:17] <joejaxx> :)
[06:20] <joejaxx> :(
[06:20] <joejaxx> !monologue
[06:20] <ubotu> Sorry, I don't know anything about monologue - try searching on http://ubotu.ubuntu-nl.org/factoids.cgi
[06:27] <parthan> joejaxx, because if i have to use it here, i need help of some non-free divers ;)
[06:32] <parthan> joejaxx, and also because the website reads "Fluxbuntu is 100% Free Software" ;)
[06:58] <dholbach> good morning
[06:59] <Fujitsu> Hi dholbach.
[06:59] <Fujitsu> Oops.
[06:59] <Fujitsu> Wrong button.
[07:00] <dholbach> Fujitsu: you have a "Hi dholbach" button somewhere? :)
[07:00] <Hobbsee> no, of course not
[07:00] <Fujitsu> No, I haven't cut my nails in a while, and hit the up button or something similar :P
[07:00] <Hobbsee> he has a "Hi $last_person_that_entered"
[07:01] <dholbach> Hobbsee: a "Hi dholbach" button would be much cooler :)
[07:01] <Fujitsu> Hobbsee: That's a good idea, actually.
[07:01] <Hobbsee> dholbach: not scalable, though
[07:11] <wallyweek> g'morning all
[07:27] <ChrisGibbs> gday all
[07:36] <wallyweek> g'morning all!
[07:57] <wallyweek> anyone wishing to review online?
[08:11] <AnAnt> persia: hello
[08:12] <AnAnt> persia: thanks for reviewing the ubuntume artwork packages, I need to ask you some questions though
[08:21] <AnAnt> can anyone help me with gconf ?
[08:33] <AnAnt> I am doing a gconf-defaults file in debian package, one of the keys I want to modify is of type list
[08:33] <AnAnt> how do I write it's entry in gconf-defaults ?
 ["value"] ?
[08:33] <huats> morning everyone
[08:34] <dholbach> AnAnt:
[08:34] <dholbach> oops
[08:34] <dholbach>  /desktop/gnome/interface/gtk_theme      Human
[08:34] <dholbach>  /desktop/gnome/interface/icon_theme     Human
[08:34] <dholbach>  /desktop/gnome/peripherals/mouse/cursor_theme   Human
[08:34] <AnAnt> dholbach: thanks for reviewing the packages
[08:34] <dholbach> from /usr/share/gconf/defaults/16_ubuntu-artwork
[08:34] <dholbach> heya huats
[08:34] <dholbach> AnAnt: no problem
[08:35] <huats> hey dholbach
[08:35] <AnAnt> dholbach: yes, but all those keys are of string type, not list
[08:35] <dholbach> ah, hang on
[08:35] <AnAnt> dholbach: oh, I found it in update-gconf-defaults man page, thanks
[08:35] <dholbach>  /apps/compiz/plugins/scale/allscreens/options/initiate_edge             []
[08:35] <dholbach> is the best I found :)
[08:36] <AnAnt> yeah it's: <key> [value1,value2]
[08:43] <AnAnt> dholbach: how should I indicated the GPL version for package license ?
[08:44] <dholbach> AnAnt: You need to refer to whatever license the upstream tarball contains
[08:44] <dholbach> AnAnt: or do you mean a license for the packaging?
[08:45] <AnAnt> dholbach: license for packaging indeed
[08:45] <dholbach> I'm not sure the archive admins want a copy of the GPL shipped just because your packaging is under the GPL
[08:45] <dholbach> I normally don't license my packaging separately
[08:47] <AnAnt> ?
[08:47] <AnAnt> I don't understand
[08:48] <dholbach> best to ask in #ubuntu-devel (the archive admins will be around there) if you need to ship a copy of $license for your packaging
[08:48] <dholbach> I never added the "Packaging is licensed under $license" note
[08:48] <AnAnt> dholbach: GPL is already existing in /usr/share/common-licenses/
[08:49] <dholbach> normally the archive admins want the upstream tarball to contain a copy of whatever license it is under
[08:50] <AnAnt> dholbach: I think you got me wrong
[08:50] <dholbach> ok... maybe you can re-phrase your question
[08:50] <AnAnt> dholbach: you said in your review "Please specify which version of the GPL applies to the packaging"
[08:52] <dholbach> AnAnt: do you have the link somewhere?
[08:52] <AnAnt> dholbach: http://revu.tauware.de/details.py?package=ubuntume-gdm-themes (point #3)
[08:52] <dholbach> oh http://revu.tauware.de/details.py?package=usplash-theme-ubuntume - I'm not Emmet :)
[08:52] <dholbach> persia is Emmet Hikory :)
[08:53] <dholbach> in http://revu.tauware.de/revu1-incoming/usplash-theme-ubuntume-0801071011/usplash-theme-ubuntume-1.1/debian/copyright you say: "The Debian packaging is (C) 2007, أحمد المحمودي (Ahmed El-Mahmoudy)
 and is licensed under the GPL, see
[08:53] <dholbach> `/usr/share/common-licenses/GPL'."
[08:53] <AnAnt> oh ok
[08:53] <dholbach> persia wants to know which version of the GPL you are talking about
[08:54] <AnAnt> -2 or -3 ?
[08:54] <dholbach> right
[08:54] <AnAnt> I don't know the difference
[08:54] <AnAnt> well, I'll ask him about that later
[08:55] <AnAnt> dholbach: as for your comment on UbuntuME-v0.1, actually the package has several themes
[08:56] <dholbach> I can't spare you the pain of reading up on those license
[08:56] <AnAnt> dholbach: 3 themes
[08:56] <dholbach> AnAnt: what happens if I choose v0.1 and you decide to ship v0.2 in the next release?
[08:57] <AnAnt> dholbach: in the next release I'm supposed to keep v0.1 too
[08:57] <dholbach> ok
[08:57] <AnAnt> dholbach: actually UbuntuME-v0.1 is an old GDM theme indeed
[08:57] <AnAnt> dholbach: I prefer that the upstream would give them names indeed
[08:57] <dholbach> ok... I just wanted to know what your thoughts are
[08:58] <AnAnt> dholbach: but he got a new life (job & marriage), so he's pretty tied up those days
[08:58] <AnAnt> dholbach: ok, thanks a lot for your help
[08:59] <AnAnt> I'll be working on the points mentioned
[08:59] <dholbach> ok great - thanks :)
[08:59]  * dholbach -> dogwalk
[08:59] <AnAnt> bye
[09:18] <\sh> moins
[09:18] <BugMaN> hi \sh!
[09:32] <Ng> in relation to the hardy schedule, when is the last realistic point for getting a new little package into universe?
[09:33] <slangasek> you should plan to have it done prior to feature freeze
[09:33] <DaveMorris> which is when?
[09:33] <Ng> slangasek: k, thanks :)
[09:34] <Ng> DaveMorris: https://wiki.ubuntu.com/HardyReleaseSchedule
[09:34] <DaveMorris> thanks
[09:34] <DaveMorris> since it revu day, my package still require revu.  All previous comments have been addressed - http://revu.tauware.de/details.py?package=libserial
[09:34] <Ng> ah and it's February 14th, so that means hardy stops getting new love on valentine's day ;)
[09:37] <astharot> good morning :)
[09:38] <liri> in an attempt to recover the revu password I get "gpg -d <<EOT ; echo 	Now paste the text below, and enter EOT<return>" and nothing else, any ideas?
[09:39] <geser> good morning
[09:43] <wallyweek> anyone to review http://revu.tauware.de/details.py?package=sdlmame before revu day ends? thank you! :)
[09:44] <wallyweek> we should be near advocation, please help me upload it before featurefreeze
[10:02]  * rzr advertises for this snd app : http://revu.tauware.de/details.py?package=jaaa
[10:36]  * wallyweek knows is quite annoying but calls once again for reviews on his package http://revu.tauware.de/details.py?package=sdlmame
[10:58] <slangasek> pochu: hmm, how does installing liboobs-1-4 break gnome-system-tools << 2.21.4, when that version of gnome-system-tools depends on liboobs-1-3?
[11:00]  * persia thanks slangasek for the comprehensive announcement
[11:00] <Hobbsee> yay, it's not revu day now!
[11:00] <slangasek> persia: I am occasionally capable of learning from past mistakes
[11:04] <pochu> slangasek: g-s-t 2.21.3-0ubuntu1 depends on liboobs-1-4 (>= 2.21.2.1) here.
[11:05] <pochu> slangasek: and there's a typo in the changelog, shold read << 2.6.23:
[11:06] <pochu> Breaks: gnome-system-tools (<< 2.21.3)
[11:06] <geser> pochu: Hi, are you going to merge mono-tools from Debian unstable? mono-tools doesn't build on hardy anymore (fixed in Debian)
[11:06] <pochu> err, 2.21.3 :)
[11:06] <pochu> geser: I'll do it when I have some time if you don't do it first ;) so please do it yourself if you can
[11:21] <slangasek> pochu: but 2.21.3-0ubuntu1 is not << 2.21.3 which is what the breaks is; so this appears to force deconfiguration of the old version of gnome-system-tools, which doesn't depend on liboobs-1-4 at all...
[11:31] <persia> StevenK: Given the imminent promotion to main, does bug #180624 interest you?
[11:31] <ubotu> Launchpad bug 180624 in cheese "cheese new upstream version 0.3.0" [Undecided,Confirmed] https://launchpad.net/bugs/180624
[11:33] <StevenK> Hrm, not really.
[11:34] <jscinoz> RAWR
[11:34] <jscinoz> hey everyone
[11:34] <persia> OK.  Kicking for standard reasons then :)
[11:34] <persia> jscinoz: /usr/share/common-licenses/GPL is GPL 3.
[11:34] <jscinoz> oh? on gutsy it shows gpl2
[11:34] <persia> jscinoz: In gutsy is it GPL 2.
[11:35] <jscinoz> ah
[11:35] <jscinoz> so i should ref /usr/share/common-licenses/GPL-2 then :P
[11:35] <StevenK> persia: I'll leave it to lool.
[11:36] <jscinoz> persia have you had a chance to redownload the package?
[11:36] <persia> StevenK: Makes sense, just as matter of highlighting it to your attention given the list in your MIR.
[11:36] <liri> persia: I'm having some troubles recovering the revu website password for my account.
[11:36] <jscinoz> because im not sure if the ftp server was down when you tried to uscan, because it seems to be working now
[11:36] <persia> jscinoz: Err..  I was avoiding that :)  I'll grab again and test the watch files.
[11:36] <jscinoz> :P
[11:36] <persia> liri: Have you uploaded something to REVU yet?
[11:36] <jscinoz> i could just pastebin you the watch file itself
[11:36] <jscinoz> wouldnt that be enough to test the uscan?
[11:37] <liri> persia: yes I have.
[11:37] <persia> jscinoz: Actually, I can just grab it from REVU, which means I only have to download it once.  Thanks for reminding me :)
[11:37] <liri> persia: when recovering the revu password I get "gpg -d <<EOT ; echo 	Now paste the text below, and enter EOT<return>" and nothing else, any ideas?
[11:37] <jscinoz> ok :P
[11:37] <jscinoz> "4) debian/copyright fails to mention files copyright Id software" are you wanting me to state specifically which files are copyright ID?
[11:37] <persia> liri: There is no text?  Hrm.  That bug has appeared before, but I don't happen to remember the cause.  When did you join ubuntu-universe-sponsors?
[11:38] <liri> uhm, let me check on that
[11:38] <persia> jscinoz: At least indicate somewhere that they are a copyright holder.  The current debian/copyright isn't an accurate summary of the files in the package.
[11:39] <liri> persia: I'm a member of                Contributors of packages for ubuntu universe      or is it not enough?
[11:39] <persia> jscinoz: If you haven't already reviewed http://lists.debian.org/debian-devel-announce/2006/03/msg00023.html, it is definitely worth a read.
[11:40] <persia> liri: That is supposed to be enough, and that you can upload makes me think it really should be.  It's just that I vaguely remember that another resync helped some people to recover their password, so I wonder when you joined the team, and when you first uploaded.
[11:43] <liri> persia: well the upload date is there on the packages page, as for the contributors groupI joined on 2007-12-25
[11:43] <persia> jscinoz: Fails for me right now.
[11:43] <persia> liri: Which package?
[11:43] <liri> persia: daloradius
[11:44] <persia> liri: Well, that's recent.  I'll try syncing again, but no guarantees: you might need a REVU-hacker to sort this out.
[11:44] <jscinoz> strange.
[11:44] <persia> jscinoz: What do you get for output?
[11:44] <liri> persia: ok thanks, tell me after the resync is over I'll give it another shot
[11:44] <jscinoz> Newest version on remote site is 4.1, local version is 4.1
[11:45] <persia> jscinoz: OK.  How about with --force-download?  Does it download?
[11:45] <jscinoz> one sec
[11:46] <jscinoz> yes
[11:46] <persia> jscinoz: You'd do best to get someone else to test then.  I have no explanation as to why it might work for you and not for me.
[11:46] <jscinoz> hmm
[11:46] <jscinoz> also
[11:47] <jscinoz> i could have sworn the quake3 sdk is GPL nowadays
[11:47] <persia> jscinoz: Maybe.  http://revu.ubuntuwire.com/revu1-incoming/urbanterror-data-0801012251/urbanterror-data-4.1/debian/copyright doesn't look like GPL to me.
[11:48] <jscinoz> i know it isnt stated in the orig or anything...
[11:48] <persia> I'm not even certain we can distribute that in Ubuntu
[11:48] <jscinoz> wait
[11:48] <jscinoz> i think the engine is gpl in the urbanterror package
[11:48] <jscinoz> its the data that isnt.
[11:48] <persia> That sounds like what I've heard before about quake3
[11:49] <jscinoz> brb going to go ask UrT devs in #urbanterror on quakenet
[11:49] <pochu> slangasek: I'm not sure what is wrong here. liboobs breaks g-s-t << 2.21.3, since g-s-t 2.21.2.1 won't work with liboobs < 2.21.3 IIRC
[11:50] <pochu> slangasek: and g-s-t 2.21.2.1 depends on liboobs-1-4, see https://edge.launchpad.net/ubuntu/hardy/i386/gnome-system-tools/2.21.2.1-0ubuntu2
[11:53] <frenchy> How long does it normally take for a source package to get through the build queue ATM?
[11:54] <persia> frenchy: A few hours to a day (depending on who uploaded a heap of things recently, or whether an archive admin just approved all the sync requests).  me-tv was available for my last aptitude check.
[11:56] <frenchy> persia: Thanks for info, have I been that much of a pain-in-the-ass that you remember me and my little package :).  It's only available as a source package though right, when does it get built?
[11:57] <persia> frenchy: It's a binary package for me, and it was more your plight of working on a package that required special hardware to test that remembers you to me.
[11:58] <frenchy> persia: Ohhh, I've been checking packages.ubuntu.com ... not the authoritative source obviously.
[12:00] <persia> frenchy: Not at all.  You want https://launchpad.net/ubuntu/+source/me-tv
[12:01] <persia> liri: Done.  Try again.
[12:02] <frenchy> persia: Thanks dude, you rock.
[12:04] <liri> persia: unfortunately this is the same
[12:04] <persia> liri: Yep.  You need a REVU Hacker then.
[12:06] <persia> liri: Why were you logging in anyway: was there a specific note you needed to add to your package?
[12:06] <Hobbsee> liri: which address is on your package?
[12:06] <liri> persia: not really, not for now.
[12:06] <liri> Hobbsee: I believe liran@enginx.com
[12:07]  * Hobbsee thinks it's broken.
[12:07] <persia> Well, yes, but the question is "How?".  We've seen this bug before, but it usually goes away after a while.
[12:08]  * Fujitsu pokes a bit.
[12:09] <Fujitsu> There's no GPG key set on the account...
[12:09] <Hobbsee> the email is set, and there's a p/w set
[12:10] <Hobbsee> but the lack fo gpg key is...interesting
[12:10]  * persia greps sync logs
[12:10] <Fujitsu> Hobbsee: Did you set the password on it? That looks... decidedly non-random.
[12:11] <Hobbsee> Fujitsu: yes, i reset it, then set it back
[12:11] <Hobbsee> :)
[12:11] <Hobbsee> holy flipping potatoes
[12:11]  * Hobbsee gets her lart bat.
[12:12] <Hobbsee> stdin: please don't use dcut on revu.  it doesn't work.
[12:12] <stdin> Hobbsee: I did once, last year...
[12:12] <Hobbsee> johan_kiviniemi, pavel_madman2k_net, same thing
[12:12]  * persia notes that the correct keyID is DB2E67D1, which was just sync'd
[12:12] <Fujitsu> Very, very few people seem to have OpenPGP keys assigned...
[12:12] <Hobbsee> stdin: no one's looked on here for a while
[12:12] <liri> yep
[12:12]  * Fujitsu adds that to the DB.
[12:13] <Hobbsee> Fujitsu: dat not good.  those in ~ubuntu-dev, perhpas?
[12:13] <Fujitsu> Hobbsee: No, only less than a dozen, I think
[12:13]  * Fujitsu checks.
[12:13] <Hobbsee> Johan Kiviniemi also gets larted with the cluebat.
[12:13] <Fujitsu> liri: Can you please try again?
[12:13] <liri> Fujitsu: the recovery thing?
[12:13] <persia> Hobbsee: ion_?
[12:13] <Fujitsu> liri: Correct.
[12:14] <liri> Fujitsu: still the same.
[12:14] <Fujitsu> process-upload should be assigning the key when it creates the account, no?
[12:14] <Hobbsee> ion_: for the love of the green spaghetti monster, please *don't* use dcut, and please *don't* upload binary packages.
[12:14] <Fujitsu> liri: Completely blank? /me tries.
[12:14] <Hobbsee> ion_: i don't know where you're finding info about uploading binary packages
[12:14] <persia> Fujitsu: No.  It assigns the email address, and the key is supposed to be assigned by the key sync.
[12:14] <Hobbsee> persia: did you just resync?
[12:15] <Fujitsu> persia: Hm, that's odd.
[12:15] <persia> Hobbsee: minutes ago.
[12:15] <Fujitsu> liri: Is that address on your key?
[12:15] <Hobbsee> cool
[12:15] <liri> Fujitsu: yeap
[12:15]  * persia did reverse lookup in the keysync log to pull the keyid
[12:17] <Fujitsu> If that key is on the keyring, and the address matches...
[12:17] <Hobbsee> persia: more stuff for you to review :)
[12:17]  * Hobbsee continues to clean up
[12:17] <persia> Hobbsee: It's not REVU day anymore :)
[12:17] <Hobbsee> heh
[12:18] <Hobbsee> persia: yes, but there's enough of it that ithad better be, for you
[12:18]  * persia took this one (mostly) off to give others a fair chance, but will look at the packages again next week.
[12:18] <Hobbsee> sure sure
[12:18] <persia> Hobbsee: Why?  I did 5 this week.  How many have you done since gutsy opened?
[12:18] <Hobbsee> i accepted 2.
[12:19] <persia> See.  We're almost even (as accepting counts double)
[12:19] <liri> Hobbsee: if you accept mine that will be 3 :-)
[12:19]  * persia only rejects packages on REVU anyway
[12:19] <Hobbsee> hehe
[12:19] <Hobbsee> persia: oh, since gutsy?  lots - but most were translations
[12:19] <persia> liri: You need to get someone to upload it before Hobbsee can accept it.
[12:20] <liri> persia: upload it where?
[12:20] <liri> persia: to universe?
[12:20] <Fujitsu> Hobbsee: What happens if you run `revu-key encrypt <email>' manually? I don't have privs to do it.
[12:20] <persia> liri: To the archives (the process is that the second advocate usually uploads, and you can complain here if they don't)
[12:22] <Hobbsee> hobbsee@sparky:~/incoming% sudo -u revu1 -H ~/revu/bin/revu-key encrypt liran@enginx.com                                            1:22PM
[12:22] <Hobbsee> gpg: WARNING: unsafe permissions on homedir `/srv/revu-production'
[12:22] <Hobbsee> gpg: liran@enginx.com: skipped: unusable public key
[12:22] <Hobbsee> gpg: [stdin]: encryption failed: unusable public key
[12:22] <Hobbsee> Fujitsu: ^
[12:22] <liri> persia: can you elaborate on "the second advocate usually uploads" ?
[12:22] <Hobbsee> revu1@sparky:/home/hobbsee/incoming$ ls
[12:23]  * Hobbsee wins!
[12:23] <Fujitsu> Hobbsee: Right, let me try something locally.
[12:23] <persia> liri: Your key is unusable :(
[12:23] <Fujitsu> No encrypting part?
[12:23] <liri> uhm, I wonder how that happens
[12:23] <liri> is that the key used to sign the package or on the launchpad account?
[12:23] <Fujitsu> They must be identical.
[12:24] <persia> liri: The REVU process consists of Ubuntu developers reviewing your package, and either commenting requesting more work, or advocating for upload.  The second person to advocate will typically upload to the archive and mail ubuntu-motu@l.u.c to announce they have done so.
[12:24] <liri> Fujitsu: how would that happen?
[12:24] <Fujitsu> Hmm...
[12:24] <Fujitsu> I don't see any subkeys on that key.
[12:24] <Fujitsu> It is indeed unusable.
[12:24] <persia> liri: Rather they must be the same key: LP should have the public key, and you should sign the package with the private key.
[12:24]  * Hobbsee wonders who is Thomas Butter
[12:25]  * Hobbsee ponders removing this stuff whcih has multiple errors, and which people haven't asked about
[12:25] <liri> persia: yeah just wondering if something could have went wrong in the copy&paste on the launchpad website
[12:25] <persia> Hobbsee: No registered IRC nick reported in LP.
[12:25] <StevenK> Hobbsee: Thomas Margarine's less spreadable brother
[12:25]  * StevenK hides
[12:25] <Hobbsee> haha
[12:25] <geser> Fujitsu: that key has no encryption capability
[12:26] <Fujitsu> geser: Exactly. No encrypting bits, so no subkeys.
[12:26] <Hobbsee> Michael Lamothe here?
[12:26] <persia> Hobbsee: Removing packages pending review?  Just comment explaining why it's crack.  For random stuff that couldn't get past uploads/, just delete.
[12:26] <liri> I'll double check
[12:27] <Hobbsee> persia: it doesn't even make it to the web UI
[12:27]  * Hobbsee wonders what the heck this guy was on
[12:27] <persia> Hobbsee: Anything that can't get to the web UI, and didn't get a complaint here may be considered cruft.
[12:27] <Hobbsee> heh
[12:27] <Hobbsee> good
[12:28] <persia> frenchy: Hobbsee seeks you (or I'm confused)
[12:28] <persia> frenchy: Also, if I'm correct, please add your IRC nick to LP.
[12:29] <frenchy> persia: Ok.
[12:29] <geser> Fujitsu: does a RSA key need a sub-key for encryption?
[12:29] <Fujitsu> geser: I thought all OpenPGP keys did, but I couldn't be quite sure about RSA. I rarely see them in the wild.
[12:29] <mruiz> hi all
[12:30] <frenchy> Hobbsee: Here!
[12:30] <Hobbsee> frenchy: you're michael?
[12:30] <geser> Fujitsu: DSA/ElGamal keys have a ElGamal encryption subkey as DSA is only for signing
[12:30] <Hobbsee> frenchy: any reason why me-tv_0.4.8-0ubuntu1_source.changes was an empty file?
[12:30] <geser> but RSA keys can have SCE
[12:31] <Fujitsu> geser: Ah, right.
[12:31] <frenchy> Hobbsee: Yes, that's me ... Ummm none that I can think off.  Where was this?
[12:31] <Hobbsee> frenchy: to revu
[12:32] <Hobbsee> frenchy: as in, did you upload it empty, or did revu manage to delete the contents?
[12:32] <frenchy> Hobbsee: I would not have intentially removed the contents of the changes file.
[12:32] <frenchy> intentionally
[12:32] <Hobbsee> frenchy: well, tha't swhat i thought.
[12:32] <Hobbsee> strange.
[12:32]  * Hobbsee nuked the upload, anyway
[12:33]  * persia notes that me-tv is in the archives now, so all is good
[12:33] <Hobbsee> oh, even better
[12:34] <frenchy> Hobbsee: I'm still a noob to packaging but I see no reason why I wouldv'e done that ... unless I had a connection dropout.  My wireless sometimes does funny things.  I believe that you're familiar with this.
[12:34] <Hobbsee> yeah, true
[12:34] <Hobbsee> i mean, dput wouldn't have even taken that
[12:35] <frenchy> Hobbsee: Good point.
[12:36] <Hobbsee> so you'd have to use some form of ftp
[12:36] <Hobbsee> which makes me wonder why revu is losing data
[12:38] <frenchy> Only ever used dput.
[12:38] <Hobbsee> strange.  oh well
[12:40] <broonie> I've had that happen to me due to a connectivity issue before.
[12:40] <frenchy> persia: LP updated.
[12:41] <persia> frenchy: Thanks.
[12:48] <AnAnt> persia: hello
[12:49] <persia> AnAnt: Hello.
[12:49] <AnAnt> persia: thanks for reviewing ubuntume artwork packages
[12:49] <persia> AnAnt: Thanks for bringing them into Ubuntu.  I like it best why we all work on the same codebase.
[12:50] <AnAnt> persia: erm, I don't understand what you mean by "I like it best why we all work on the same codebase."
[12:50] <AnAnt> persia: anyways I got some questions
[12:51] <AnAnt> persia: you say, GPL cannot be relicensed to CC
[12:51] <persia> AnAnt: All the different groups making different flavours of Ubuntu all working on the same packages in the same repositories, rather than trying to maintain separate changes, which are hard to keep up-to-date.
[12:52] <AnAnt> persia: well, that Human Ultra theme is actually based on Human theme that is CC licensed
[12:52] <persia> AnAnt: As far as I understand it.  That statement does not constitute legal advice, and may not apply in any given jurisdiction.
[12:52] <AnAnt> persia: huh ?
[12:53] <persia> AnAnt: Maybe that package has a bug :)  Anyway, some of the code / data was GPL, so I complained.  Better to reference the GPL in debian/copyright, as the GPL tends to require relicensing as GPL (if the work was received under the GPL).
[12:55] <AnAnt> persia: erm, I don't get it, btw, for the packaging license, what difference does it make between GPL-2 & GPL-3 ?
[12:56] <persia> AnAnt: http://www.fsf.org/licensing/licenses/rms-why-gplv3.html has a basic overview of the differences.  For a true understanding, you should read and compare the licenses.
[12:57] <AnAnt> persia: oh, about modifying gdm.conf, I am working on a ubuntume-artwork package, that does modify /etc/gdm/gdm.conf-custom ,it asks the user (using debconf) if he wants the gdm.conf-custom to be modified in order to use the themes, if he/she accepts, then the postinst modifies (not replaces) the gdm.conf-custom (using sed)
[12:57] <persia> However, my issue with the package was that you referenced /usr/share/common-licenses/GPL (which is GPL3), didn't specify a version, and the only GPL code I found was GPLv2.
[12:58] <persia> AnAnt: You may or may not be permitted to do that.  Check to see if gdm defines gdm.conf as a conffile.  It is considered bad to modify another packages conffile.  There may be a workaround (or maybe someone will grant a policy violation exception).
[12:59] <AnAnt> persia: oh
[12:59] <AnAnt> persia: it is a conffile
[13:00] <AnAnt> persia: but I'm not replacing the file, just made a script that modifies it
[13:00] <persia> AnAnt: Then you need to either work with gdm people to figure out how to work around that, or someone needs to grant a policy exception to allow you to do that.
[13:01] <AnAnt> persia: even if it is done after user is asked wether to do it or not ?
[13:03] <persia> AnAnt: I don't think you.  You can check the policy from the debian-policy package.  Hardy currently has 3.7.3.0 (and while not everything complies, that is the standard against which new entrants are judged).
[13:03] <persia> s/you/so/1
[13:05] <AnAnt> ok
[13:06] <AnAnt> persia: in the usplash, can the C file be CC licensed ?
[13:07] <persia> AnAnt: Sure, but only the copyright holder can relicense it.  If you received it (or significant portions of it) under GPL, it needs to stay GPL.
[13:08] <AnAnt> ok thanks
[13:09] <ScottK> Significant defined as not very much at all for copyright purposes.
[13:10] <persia> ScottK: Depends on the jurisdiction, really.  Where you are, having glanced once at a similar source that had part of one line in common might be considered infringement, but not everywhere is that draconian.
[13:11] <persia> But even there, one cannot copyright "int main(argc, *argv)"
[13:12] <ScottK> True, but if someone has claimed copyright on something (at least here) the burden is to prove it's not copyrightable.
[13:13] <persia> Frustratingly true :(  Especially so with automatic grant of copyright.
[13:13] <ScottK> So assuming something isn't copyrightable is risky at best.
[13:15] <ScottK> Speaking of which I just had a scam mail land in my inbox that claimed I was due a tax refund and said: "© Copyright 2008, Internal Revenue Service U.S.A."
[13:15] <ScottK> The one entity (in the US) that you know didn't copyright something is the US Government.  They're prohibited from doing it.
[13:15] <StevenK> Interesting
[13:15]  * persia notes that under that copyright regime, that government cannot copyright anything at all.
[13:16] <StevenK> ScottK: How do they protect their forms, then?
[13:16] <ScottK> If one modifies their form to perpetrate a fraud, there are other laws to deal with that.
[13:16] <persia> StevenK: Used to be special paper sizes.  Now open (PDF downloads).
[13:16] <ScottK> Otherwise, why would they care?
[13:17] <ScottK> The tricky bit is the under some circumstances when they hire a contractor to develop a work, the contractor can retain copyright if the US Government doesn't actually buy the rights.
[13:18] <broonie> Often some forms are controlled in various ways (for example, blanks some of the more important tax forms in the UK are only allowed to be held by employers)
[13:18] <persia> Vorian: Would you mind updating bug #179606?  I'm not able to unsubscribe the sponsors team, and it just needs a bit of editorial work.
[13:18] <ubotu> Launchpad bug 179606 in xdg-utils "xdg-util new upstream needs packaging" [Wishlist,Confirmed] https://launchpad.net/bugs/179606
[13:18] <broonie> It's crude security, not worth too much these days.
[13:18] <Vorian> persia: sure thing
[13:19] <persia> broonie: Seems odd.  How does that help Inland Revenue? (disclaimer: I live in a tax jurisdiction where the laws have been adjusted for ease of computer programs)
[13:19] <persia> Vorian: Thanks.
[13:20] <broonie> persia: It makes it a bit easier for employers to pass over tax data when they need to (for a new job, say). It also makes it easier for them to LART anyone doing anything stupid.
[13:20] <Vorian> not a problem at all
[13:20] <Vorian> :)
[13:21] <broonie> I suspect they wouldn't bother if writing the rules today.
[13:21] <persia> broonie: Hmm.  I guess.  Here there are special red stamps, registered with the government, and if you don't have the appropriate red stamp from your last employer on your handover documentation, it gets rejected.  The forms are available to anyone, but the stamps are hand-constructed to be difficult to duplicate.
[13:22] <persia> ember: Are you still working on deskscribe?
[13:22] <broonie> persia: Yes, that's the same sort of idea (the forms are relatively difficult to reproduce).
[13:24] <persia> broonie: The difference being that they are mass-produced, so it leaves open a gap for unscrupulous HR.  Here if the fancy red stamp is missing, the company has a problem, and reports it within the day.  Anyway, subverting non-computer systems is a far cry from Ubuntu development :)
[13:25] <liri> Fujitsu: should I upload my key to subkeys.pgp.net for it to be valid on revu?
[13:26] <bluekuja> liri, nope, use keyserver.ubuntu.com
[13:27] <bluekuja> liri, the key-sync script updates the keyring using keyserver.u.c atm
[13:27]  * persia notes that most keyservers (including ks.u.c) sync to each other several times daily
[13:28] <bluekuja> persia, yes, and does ks.u.c sync from subkeys.pgp.net as well?
[13:28] <liri> bluekuja: I'm not sure if that would solve the error from gpg: skipped: unusable public key
[13:28] <ember> persia: yes.
[13:28] <persia> bluekuja: I believe so.
[13:28] <bluekuja> persia, ah ok so liri nvm my comment
[13:28] <bluekuja> :)
[13:28] <persia> ember: Please upload a new revision soon.  It's been a few weeks, there are only about three weeks left before the deadline.
[13:29] <ember> will do
[13:29] <persia> ember: Thanks.
[13:29] <liri> bluekuja: I sent my key to subkeys.pgp.net
[13:30] <bluekuja> liri, today?
[13:31] <bluekuja> liri, key ID?
[13:32] <liri> bluekuja: a few minutes ago, DB2E67D1, revu rejected with a "skipped: unusable public key" message, actually locally I get the same results for some reason
[13:33] <bluekuja> liri, it should'nt be available on ks.u.c then
[13:34] <bluekuja> liri, I don't know how often keys gets synced from other keyrings
[13:34] <bluekuja> liri, what do you mean with locally?
[13:34] <bluekuja> liri, e.g signing your package with debsign?
[13:35] <liri> bluekuja: encrypting a file, like gpg --encrypt --recipient liran@enginx.com <file>
[13:35] <liri> bluekuja: I think the package signing was successful but I can't remember now (although I can verify it quite easily)
[13:36]  * persia notes that signing and encrypting are different
[13:36] <liri> bluekuja: yeah signing asks for passphrase and completes just fine.
[13:36] <liri> true.
[13:36] <bluekuja> liri, are you trying to *upload* or to *decrypt* to get your pwd?
[13:37] <liri> bluekuja: well I'm currently trying to encrypt a file locally on my computer to test my key
[13:38] <bluekuja> liri, and what's the problem with REVU?
[13:38] <bluekuja> liri, actually as persia stated signing and encrypting is different...maybe you're doing something wrong? :)
[13:38] <liri> bluekuja: well no idea then :)
[13:39] <liri> while before gesser and fujitsu noted: geser: Fujitsu: that key has no encryption capability Fujitsu: geser: Exactly. No encrypting bits, so no subkeys.
[13:39] <persia> bluekuja: Nothing being done wrong, just that the key is RSA rather than DSA.  Needs more subkeys, or if they were recently added, needs to wait for the keyservers to sync.
[13:39] <bluekuja> persia, I wasnt sure he was trying to upload to REVU or not
[13:40] <bluekuja> persia, and I guess liri didnt upload anything to revu yet
[13:40] <persia> liri: Unless you've lots of signatures you wish to preserve, consider creating a DSA key, and signing it with your RSA key to indicate you know you are you.
[13:40] <bluekuja> liri, did you upload something to revu yet?
[13:40] <persia> bluekuja: Uploading works, just not password retrieval (signing works, but not encryption)
[13:40]  * Hobbsee is not me, just someone else pretending to be me.
[13:40] <bluekuja> persia, got it
[13:41] <bluekuja> Hobbsee, heya :D
[13:41] <Hobbsee> greets!
[13:41]  * persia sees LongPointyStick and is suspicious of that claim
[13:41] <Hobbsee> that's on another machine
[13:41] <liri> persia: I'll just get over with it by creating a new dsa key and that's it.
[13:42] <bluekuja> Hobbsee, happy new year, sarah!
[13:42] <Hobbsee> :)
[13:42] <bluekuja> Hobbsee, everything went fine with your holidays?
[13:42] <Hobbsee> yeah, mostly :)
[13:43] <bluekuja> great :)
[13:44] <bluekuja> persia, someone should promote you to Keys master
[13:45] <bluekuja> persia, it seems you have a good knowledge about keys
[13:45] <bluekuja> ;)
[13:45] <persia> bluekuja: I learned most of it here, or in links posted here.
[13:46] <bluekuja> cool :)
[13:50]  * persia found the issue with rhythmbox.  Somehow the "変換" key happens to send the same scancode as the "Media" key on some random internet keyboard.  Bad hardware designers!
[13:50] <StevenK> I don't have one of those keys
[13:51] <persia> StevenK: It's people like you who thought it would be a good idea to double-map the keysym :p
[13:51]  * Hobbsee mutters somethign about how people should all speak english
[13:52] <persia> (for those unfamiliar with jp106, 変換 is right next to a very small spacebar)
[13:52] <StevenK> Hobbsee: Personally, I dislike that attitude.
[13:53] <Hobbsee> or, all speak some chosen language
[13:53] <persia> Hobbsee: Even if everyone spoke a common language, why shouldn't they use others too?  Also, it's fun to have nifty characters be easy to type.
[13:53] <Hobbsee> persia: because they expect me to understand them, when they're speaking in mangled $language_of_country, and getting increasingly pissed off when i can't undersatnd them.
[13:53] <Hobbsee> s/speaking/mumbling/
[13:54]  * persia especially likes 全角／半角 for ｅｘｔｒａ　ｗｉｄｅ characters :)
[13:54] <Hobbsee> hehe
[13:54] <rzr> persia: hi
[13:54] <rzr> persia: just got your email
[13:54] <persia> rzr: Hello.  Wasn't actually mail :)
[13:55] <rzr> persia: I'd like to make it enter ubuntu 1st
[13:55] <persia> rzr: makes sense.
[13:55] <rzr> persia: just to test the process
[13:55] <rzr> persia: i have pending ITP in debian
[13:55] <rzr> i wanted to compare
[13:56] <rzr> persia: well u're right i'll have to ITP it too
[13:57] <Hobbsee> dholbach: so what is hte date of doom?
[13:57] <persia> rzr: Even while you're getting it into Ubuntu, it's best to ITP.  It's frustrating when someone uploads a different tarball the day before it goes into Ubuntu (happened to me once), and you have a very annoying merge later.
[13:57] <rzr> yea I know that it happended to me once
[13:59] <persia> rzr: Anyway, your package was selected by the review assigner, so you've just received a special, non-REVU day review.  Please upload a new candidate addressing the points raised in the REVU comment.
[13:59] <rzr> great
[13:59] <rzr> thx persia
[14:09] <dholbach> Hobbsee: what are you referring to?
[14:09] <Hobbsee> dholbach: mid jan, MC was going to make a decision, yes?
[14:11] <dholbach> Hobbsee: the MC will wait for the report that is due mid January
[14:11] <Hobbsee> ...right
[14:11] <persia> Vorian: Please update the Bug Description with the contents of your last comment.  Makes life easier for the archive-admins.
[14:12] <Hobbsee> dholbach: which is written by the MC?
[14:12] <Vorian> persia: will do, thanks again for the tip
[14:12] <dholbach> Hobbsee: no, norsetto and I will write it
[14:12] <persia> Hobbsee: Only accidentially.  Written by the supervisors (50% of whom coincidentally are also MC members)
[14:13] <dholbach> ?
[14:13] <persia> Hobbsee: Please, keep your pitchforks and torches sharp and dry if you like, but wait, and don't mix things.  There's too much tension already :)
[14:14] <Hobbsee> right.
[14:15] <ScottK> Well so far everything I've dealt with that he messed up was in Main.
[14:15]  * Hobbsee just wants a date to see everything done by, as a vote of confidence that the MC can, and will do what it says, in this matter.
[14:21] <ion_> hobbsee: Never heard of pavel_madman2k_net. I accidentally uploaded a binary package to REVU ages ago, and immediately reuploaded the source-only package.
[14:23] <zul> morning
[14:24] <ion_> hobbsee: I just assumed the cron job there would just remove it. Had i known it’s left lurking there, i’d have requested it to be removed back then.
[14:30] <ion_> hobbsee: 2007-12-28 05:16:22 < ion_> Oh, i accidentally uploaded a .changes file with both source and binary files. I wonder how REVU handles it?  2007-12-28 05:16:48 < Fujitsu> It won't even see it.  2007-12-28 05:16:59 < Fujitsu> It globs for *_source.changes
[14:30] <ion_> hobbsee: And that was about it.
[14:31] <martoss> hi all, i have a ppa repo related questions.
[14:31] <ion_> ...and now would be a good time to realize she’s not online. :-P
[14:32] <martoss> if i upload via dput a ".changes" file, i get an error message that it contains binary parts since the debs are uploaded as well.
[14:32] <ion_> Build with -S
[14:32] <martoss> how can i create a changes file without the binary deb files just for the .tar.gz and the desc?
[14:32] <bluekuja> martoss, debuild -S -sa
[14:32] <bluekuja> martoss, for revu upload
[14:33] <bluekuja> martoss, you did something like dpkg-buildpackage -rfakeroot with no other options...so you get the binaries in the .changes as well
[14:33] <bluekuja> martoss, just use the command above and that's fixed
[14:33] <martoss> yepp, revu would be the next test, i think my key should be in keychain since resync should be done at least once per day
[14:34] <persia> martoss: When did you join the group?
[14:34] <martoss> think it was sunday
[14:35] <persia> martoss: It's definitely sync'd then.
[14:35] <persia> (resync doesn't happen every day, just most days)
[14:36] <mok0> Perlit Rendehest
[14:36] <martoss> ok, is uploaded
[14:37] <martoss> revu login is the same as the launchpad account?
[14:38] <soren> mok0: ?
[14:38] <amarillion> martoss, fill out your email address and let the login fail, then you can request a new one
[14:38] <persia> martoss: Not at all.  If you've uploaded to revu, you can recover your password from REVU.
[14:38] <martoss> ok
[14:40] <martoss> how long must i wait for the "Recover"  not giving me a message like "No REVU account for martin.hoefling@gmx.de exists yet." :-)
[14:41] <martoss> kk, got it
[14:42] <martoss> great, login works now...
[14:45] <DarkSun88> Hi all
[14:45] <martoss> ok, first thing would be to fix lintian stuff in eric
[14:48] <DarkSun88> persia: Ping
[14:48] <martoss> can someone look at my lintian report of eric? I do not fully understand it's meaning.
[14:49] <persia> martoss: Pastebin it (with lintian -iIv)
[14:56] <martoss> http://www.pastebin.org/14549
[15:01] <Ng> persia: in your review of Terminator you mentioned using DEB_CHANGELOGS_INSTALL_ALL - I'm a little confused in that the package seems to include the upstream and debian changelogs already anyway
[15:18] <bddebian> Heya gang
[15:21] <martoss> hi bddebian
[15:21] <bddebian> Hello martoss
[15:23] <DarkSun88> Hi bddebian :)
[15:25] <bddebian> Hi DarkSun88
[15:28] <DarkSun88> bddebian: Thanks :)
[15:33] <martoss> can sb look through http://revu.tauware.de/details.py?package=eric and give me comments about the standards error?
[15:37] <broonie> martoss: It means that your package says that it complies with a newer version of Debian policy than the lintian that is being used supports.
[15:38] <broonie> Presumably because you are syncing a Debian package more current with policy than the Ubuntu lintian.
[15:38] <martoss> hmm ok, should i decrease the version then?
[15:40] <broonie> I'd just ignore it myself unless the policy changes broke something in Ubuntu (which is unlikely)
[15:42] <martoss> ok, so this is not a problem for accepting a package
[15:46] <amarillion> I get that problem as well in my package. I think that means lintian on revu needs to be updated
[15:47] <amarillion> Locally I'm using the latest version of lintian in gutsy backports and it gives the reverse error: if you use standards version 3.7.2 it suggests upgrading to 3.7.3
[15:50] <geser> Hi bddebian
[15:50] <bddebian> Heya geser
[15:51] <ScottK> martoss: 3.7.3 is what you should be using now.
[15:53] <martoss> yepp, its 3.7.3 in mine as well
[16:14] <Peaker> hi, how do I skip unit tests when building the python2.5 package?
[16:36] <tuxmaniac> will tiber ever be back?
[16:48] <tuxmaniac> how long does it take to get ones revu account activated after first revu upload?
[16:48] <Ng> tuxmaniac: I did that recently and it didn't email me the password, so I used the revu website's password recovery feature and it worked fine :)
[16:49] <tuxmaniac> Ng, Neither does the password recovery works for me
[16:49] <Ng> ah
[16:58] <martoss> tuxmaniac, several minutes
[16:58] <martoss> cu later
[17:03] <saivann> Hi everybody, I worked on bug #131530 and I would need a MOTU to approve and upload my debdiff for package bluez-gnome
[17:03] <ubotu> Launchpad bug 131530 in bluez-gnome "'Browse device...' in the bluetooth applet is useless without gnome-vfs-obexftp" [Unknown,Fix committed] https://launchpad.net/bugs/131530
[17:03] <saivann> ( for hardy )
[17:06] <saivann> This debdiff only adds dependency for gnome-vfs-obexftp which is in main since yesterday, approved by Martin Pitt
[17:06] <DarkSun88> See you later
[17:07] <saivann> I will be busy for the next minutes but if someone want to take care of this, here's the debdiff :
[17:07] <saivann> http://upload.leservicetechnique.com/bugs/bluez-gnome.debdiff
[17:22] <geser> saivann: you need a core-dev for bluez-gnome, subscribe the ubuntu-main-sponsors team to the bug
[17:25] <jdong> LucidFox: ok I'm gonna have a look at gtkpod-aac
[17:46] <jdong> is dh_iconcache now gone for good and dh_icons should be used instead?
[17:46] <saivann> geser : thanks
[17:47] <pochu> jdong: yup
[17:48] <jdong> pochu: ok, thanks.
[17:48] <slangasek> pochu: no, liboobs-1-4 does not break g-s-t << 2.21.3, because there is no g-s-t << 2.21.3 that will *look* for liboobs-1-4
[17:48] <slangasek> pochu: so it's a spurious breaks:
[17:50] <pochu> slangasek: what about g-s-t 2.21.2.1?
[17:50] <LucidFox> jdong> yes
[17:51] <LucidFox> in fact, I have an updated version of gtkpod-aac
[17:51] <pochu> slangasek: it depends on liboobs-1-4
[17:51] <LucidFox> I'll upload it
[17:55] <slangasek> pochu: hrm, well, that package doesn't seem to exist anymore :)
[17:55] <pochu> slangasek: it did before seb128 sponsored g-s-t 2.21.3 ;)
[17:56] <slangasek> pochu: so if it did exist and had a wrong dep, ok, that would explain it
[17:58] <pochu> I think it was: we had liboobs-1-4 2.21.2.1 and g-s-t 2.21.2.1 depending on liboobs-1-4. Then with the liboobs 2.21.3 update which broke the api without bumping the soname because it was already bumped and this was an unstable release, we needed to bump the liboobs-1-4's Breaks for g-s-t
[17:59] <pochu> Otherwise g-s-t 2.21.2.1 would use liboobs-1-4 2.21.3 and would break
[18:02] <DarkSun88> Hi
[18:08] <EtienneG> hey gang
[18:09] <mneptok> everybody look busy! here comes ... oh shit. too late.
[18:09] <LucidFox> jdong> I have uploaded updated gtkpod-aac interdiffs for the libmp4v2 transition
[18:09] <EtienneG> any chance a fix for the flashplugin-nonfree ever get an official update through the repo ?
[18:09] <EtienneG> just wondering if it is only a matter of time ...
[18:10] <EtienneG> mneptok, dude!
[18:10] <mneptok> EtienneG: i think the change has been uploaded, but returns 1 even though it actually works.
[18:10] <mneptok> >:)
[18:15] <amarillion> Where can I find docs on writing .desktop files?
[18:16] <amarillion> Googling for "desktop files" gives a lot of false positives
[18:16] <tuxmaniac> Hello. request a motu to review the package http://revu.tauware.de/details.py?package=alliance and comment/advocate if found ok.
[18:17] <ScottK> amarillion: I believer that freedesktop.org is the place to look
[18:18] <amarillion> thx I'll look into it
[18:33] <\sh> grmpf..does anyone has a clue how to edit a patch from afterstep, which is not applying correctly...well it's the first one..I can't see anything wrong with dbs-edit-patch
[18:39] <mneptok> amarillion: probably the best way to educate yourself is to take an example of a properly crafted .desktop (gedit may be a good bet) and dissect it.
[18:55] <amarillion> How do I add binary files to a source package? I've got an icon for my app, and I put it in the debian dir.
[18:56] <amarillion> But when I try to build the source package, I get
[18:56] <amarillion> dpkg-source: cannot represent change to debian/alex.png: binary file contents changed
[18:56] <\sh> amarillion: you should use uuencode/uudecode to push binary stuff inside a source package
[18:57] <bddebian> amarillion: You cannot add a binary file that way.  You either have to use uuencode or some such, or better yet, use an xpm icon
[18:57] <amarillion> ok, in this case xpm is easiest I guess
[18:57] <amarillion> So you can't add binary files at all? I didn't know that
[18:57] <\sh> amarillion: source package == binary stuff in debian/ dir
[18:57] <LucidFox> Is it allowed to have a package that's a simple collection of themes under different licenses?
[18:58] <\sh> hey bddebian btw :)
[18:58] <bddebian> Hi \sh
[19:32] <mok0> Suggestion: All MOTUs should have a special character in their nick, for example "@"
[19:33] <LaserJock> heh
[19:33] <LaserJock> that would make it more difficult for us to hide ;-)
[19:33] <mok0> If  that is the first character, ppl can immediately see MOTUs online
[19:33] <mok0> LaserJock: :-)
[19:35] <mok0> It took me a while to figure out who in this channel are MOTUs -- there are probably still a lot I don't know...
[19:37] <amarillion> not a bad suggestion
[19:39] <mok0> Perhaps I should send a note to u-m
[19:39] <LaserJock> if you think it'd be a good idea
[19:40] <LaserJock> I'm not sure many MOTU would like the idea or if it's even possible to do only in #ubuntu-motu, but it may be worth looking at
[19:40] <mok0> People may not want it, but I will suggest it anyway :-)
[19:41] <stdin> LaserJock: just give them all an access level of 5 and set the channel AUTOVOICE level to 5 (like how it's done in -ops)
[19:42] <LaserJock> stdin: yes, but I'm not sure that is a desired thing
[19:42] <stdin> well you could set CMDVOICE to 5 instead, then they could choose when to be +v and when not
[19:43] <stdin> (if I understand chanserv that is)
[19:43] <mok0> stdin: that is also a possibility, but can it be seen in a /who listing?
[19:43] <zul> its kind of like having a target on your back which alot of people probably dont want
[19:44] <stdin> mok0: yeah, shows as H+
[19:44] <mok0> But if you don't want to do MOTU stuff, you just use the ordinary nick
[19:44] <stdin> you just devoice yourself
[19:44] <mok0> (or don't set the + option)
[19:44] <stdin> kind of like how it's done in #freenode
[19:44] <mok0> stdin: exactly
[19:45] <jdong> LucidFox: grumble I kinda did that while offline too
[19:45] <jdong> LucidFox: lol lemme take a look at the new interdiff
[19:47] <jdong> LucidFox: can you (1) version libmp4v2-dev (>= 1:1.6-0.1) (2) dh_iconcache -> dh_icons in debian/rules (3) put LP: #180406 in the changelog and repost the interdiff?
[19:48] <LucidFox> jdong> it already has dh_icons
[19:48] <ScottK> mok0: Back when I needed to know I just looked up the team on LP to see who was in it.
[19:48] <LucidFox> as for the other two, sure
[19:49] <jdong> LucidFox: ok you're right, I was looking at the wrong interdiff
[19:49] <jdong> thanks
[19:49]  * ScottK wouldn't want to be any more of a target.
[19:49] <mok0> ScottK: OK, but it doesn't quickly show you who is online
[19:49] <ScottK> True.
[19:49] <LucidFox> should I also update Standards-Version to 3.7.3?
[19:49] <ScottK> LucidFox: Yes
[19:50] <mok0> Like stdin said, if MOTUs are made IRCops, then you can set the +H option to hide
[19:51] <ScottK> Sounds like more work then to be in the same place I am now.
[19:51] <ScottK> I'm not in favor.
[19:51] <stdin> they don't need to have OP access to just have voice
[19:52] <mok0> stdin: ok? I've never really used irc modes
[19:52] <ScottK> My solution would probably be to just be grumpier so people would bother someone else.
[19:52] <stdin> ChanServ will give them +v if they have access to CMDVOICE on the channel
[19:52] <mok0> ScottK: You? Grumpy? Naaa
[19:53] <LucidFox> jdong> reuploaded
[19:54] <jdong> LucidFox: thanks
[19:56] <mok0> ScottK: My concern is to make it easier for people to communicate efficiently on IRC.
[19:57] <ScottK> I understand.  My concern is to be able to idle on the channel and jump in where I care to without getting pinged on to much.
[19:57] <ScottK> If I can't, I probably won't.
[19:57] <ScottK> So there may be unintended consequences to your proposal.
[19:57] <mok0> ScottK: Perhaps there could be a watch schedule
[19:58] <ScottK> If we were paid to be here, sure.
[19:58] <mok0> he
[19:59] <nxvl_work> mok0: what are we talking about?
[19:59] <stdin> you could set +v when you're "available to help" and leave yourself unvoiced when you're just popping in, up to you
[19:59] <mok0> stdin: +1
[19:59] <slangasek> nxvl_work: he's talking about painting targets on the MOTUs
[20:00] <nxvl_work> why?
[20:00] <bddebian> easier to hit :-)
[20:00] <nxvl_work> and its needed because...
[20:00] <jpatrick> poor us... :(
[20:01] <nxvl_work> i don't see in which case that would be useful
[20:01] <jpatrick> nxvl_work: https://lists.ubuntu.com/archives/ubuntu-motu/2008-January/002994.html
[20:01] <stdin> if you need a mentor or someone to look in revu
[20:01] <mok0> easier for newbies to become involved & effective
[20:01] <nxvl_work> because then we are going to need a paint for the MOTUs, one for the u-u-s, one for the main developers, and so one
[20:02] <jdong> LucidFox: gtkpod-aac uploaded
[20:02] <nxvl_work> stdin: a MOTU, isn't necessary working on revu
[20:02] <ScottK> mok0: I'd say easier for motus to get bugged.
[20:02] <ScottK> Generally I think it's better to ask questions of the channel and let whoever answer.
[20:02] <nxvl_work> and any contributor with experience will be able to mentor any other, not only a MOTU
[20:02] <stdin> nxvl_work: I just said look at it, not approve it ;)
[20:03] <nxvl_work> stdin: i'm just saying what i think :D
[20:03] <mok0> nxvl_work: true
[20:03] <stdin> I think what I say, I think... :p
[20:03] <nxvl_work> ScottK: right
[20:03] <jpatrick> I don't think a ubuntu/motu/* cloak is possible
[20:04] <nxvl_work> it isn't a good practice to look for someone to help without a good reason to look for him/her
[20:04] <mok0> jpatrick: I think there is a mode where you can hide (?)
[20:04]  * LaserJock suggests we give the new people a target instead ;-)
[20:04] <nxvl_work> it's better to ask on the channel and the one who can help does it
[20:04] <LucidFox> jdong> Thanks!
[20:05] <mok0> nxvl_work: ... ppl can still do that
[20:05] <nxvl_work> mok0: newbies wont
[20:05] <nxvl_work> i have been a newbie 3 moths ago, and i'm still kind of it
[20:06] <amarillion> Why is the ISC license preferred over BSD?
[20:06]  * ScottK thinks jdong should be the designated target.
[20:06] <mok0> nxvl_work: I thought you were MOTU ;-)
[20:06] <nxvl_work> and newbies don't ask on the channels
[20:06]  * ScottK did when I was new
[20:06] <nxvl_work> mok0: nop, still not, just contributos
[20:06] <nxvl_work> contributor*
[20:07] <LaserJock> amarillion: what are you referring to?
[20:07] <nxvl_work> i have gone trough the mentor program and i'm not a mentee anymore, but still not a MOTU
[20:07] <amarillion> Well, a few days ago I was discussing the license of speed-game, the package I'm working on right now
[20:07] <amarillion> It currently doesn't have a license at all
[20:07] <nxvl_work> ScottK: did you take a look at the bug i ask?
[20:07] <mok0> amarillion: then it can't be distributed
[20:07] <amarillion> somebody here mentioned the ISC licence
[20:08] <nxvl_work> wrong channel
[20:08] <amarillion> mok0, no worries
[20:08] <ScottK> Yes
[20:08] <amarillion> I contacted the author and he said to go ahead with the ISC license
[20:08] <ScottK> amarillion: It was persia
[20:08] <amarillion> right
[20:09] <amarillion> so the package is in good shape, and I'm ready to put the appropriate licensing text there
[20:09] <LaserJock> according to wikipedia it's "It is functionally equivalent to the 2-clause BSD licence, with language "made unnecessary by the Berne convention" removed."
[20:09] <amarillion> and I'm googling for the actual text. It's not in /usr/share/common-licenses
[20:09] <amarillion> BSD is
[20:09] <LaserJock> yes, I've never heard of ISC
[20:09] <amarillion> LaserJock, right. So that made me wonder why persia suggested ISC and not simply BSD
[20:10] <LaserJock> well, I suppose it's a bit free-er and simpler
[20:10] <LaserJock> it's not that BSD wouldn't work
[20:11] <amarillion> So which text should I include in the package? Is it this: http://ictlab.tyict.vtc.edu.hk/pub/tarball/dhcp-3.0b2pl3/ISC-LICENSE?
[20:11] <jdong> oops some half-asleep idiot forgot to call debuild with -sa... :D
[20:13] <LaserJock> amarillion: whatever text the author uses
[20:14] <amarillion> LaserJock, yeah but I have to apply it. The original author told me to go ahead and not bother him :)
[20:14] <LaserJock> hah
[20:14] <amarillion> it's a little game that is finished, not some library or other ongoing project
[20:15] <LaserJock> yeah, well it's completely undistributable legally without a license
[20:17] <amarillion> Well, here is what he said: http://paste.ubuntu-nl.org/51254/
[20:20] <jdong> hmm why did I get two Accepted e-mails for the same sponsored pload?
[20:22] <joejaxx> mok0: are you sure that is not going to become a ping list?
[20:24] <amarillion> I'll wait to see if persia can clarify
[20:26] <mok0> joejaxx: Not really
[20:26] <mok0> joejaxx: but some of the MOTUs seem to .-)
[20:26] <joejaxx> mok0: :)
[20:27] <joejaxx> i was just wondering how the symbol would help since we have the queue and revu system
[20:27] <joejaxx> and mostly everyone here answers questions if they {see it,know the answer}
[20:27] <joejaxx> :)
[20:28] <mok0> joejaxx: just so ppl can recognize what MOTUs are online
[20:28] <joejaxx> so you would only have the +v if you are not idle?
[20:29] <mok0> joejaxx: yes
[20:29] <joejaxx> ah ok
[20:29] <joejaxx> that clears up the confusion :)
[20:29] <mok0> joejaxx: it's probably better to use the mechanisms that are build into IRC
[20:29] <mok0> joejaxx: better than a special character in the nick
[20:30] <joejaxx> i thought you meant like #gentoo-dev where devs/contributors have a mode set all the time
[20:30] <joejaxx> which is the equivalient to a ping list
[20:30] <joejaxx> but your suggestion is interesting
[20:30] <mok0> joejaxx: I guess you can set/unset it as you please
[20:30] <joejaxx> equivalent*
[20:31] <mok0> joejaxx: it should be discussed at a motu-meeting I guess
[20:31] <mok0> joejaxx: ... it could also be voluntary
[20:31] <joejaxx> oh ok
[20:32] <mok0> joejaxx: anything is possible :-)
[20:32] <pochu> mok0: that should be discussed with the IRC council too I guess, since '@' is operator and '+' is voiced.
[20:33] <mok0> pochu: sure, those characters were just "random" ones
[20:33] <pochu> oh, is it possible to set others?
[20:34] <mok0> pochu: I think you can use any ascii character in a nick, right?
[20:36] <mok0> Another way of doing it is giving MOTUs CMDVOICE rights, stdin said that before
[20:36]  * RainCT fully agrees with ScottK's reply to mok0's proposal
[20:36] <mok0> RainCT: no hard feelings :-)
[20:36] <joejaxx> i keep confusing ScottK and Steve.*K
[20:37]  * joejaxx keeps forgeting who is who :\
[20:37] <ion_> They’re really the same person.
[20:37] <mok0> me too
[20:37] <joejaxx> Toadstool: lol
[20:37] <joejaxx> gah
[20:37] <joejaxx> ion_: *
[20:38] <ScottK> Between the two of us we make up one person who never sleeps, but seems to know a lot less when it's daylight in North America.
[20:38] <joejaxx> lol :P
[20:38]  * ion_ tries to figure out how someone could mistype ‘ion’ as ‘Toadstool’. :-)
[20:38] <joejaxx> ion_: haha
[20:38] <joejaxx> :P
[20:38] <joejaxx> autotabwhileshiftingfingers ftl
[20:53] <ScottK> mok0: Just hurry up and get MOTU and then you can change your nick to MOTU-mok0.
[20:53] <mok0> ScottK: lol
[20:54] <mok0> ScottK: Still educating myself...
[20:54] <mok0> ScottK: Trying to get my packages from gutsy -> debian
[20:55] <ScottK> Sure.  No problem.  By the time you think you are ready, you will have already have been ready for some time.
[20:55] <mok0> ScottK: You think I should apply now?
[20:55] <nxvl_work> mok0: you need much to became a MOTU, you only need to hug everyone
[20:55]  * joejaxx has that problem as well
[20:56]  * mok0 hugs nxvl_work 
[20:56] <ScottK> mok0: I haven't been paying close enough attention to what's going on here to have a strong opinion.
[20:56] <joejaxx> i do not know when i am going for it
[20:56] <ScottK> It's possible you're ready.
[20:56] <joejaxx> maybe next release cycle
[20:56] <joejaxx> lol
[20:56] <Amaranth> i've been at this since 2005 and only recently tried to become a motu :P
[20:57] <joejaxx> lol
[20:57] <mok0> Amaranth: so, either you are lazy or incompetent :-P
[20:57] <nxvl_work> Amaranth: define "at this"
[20:57] <ScottK> Or inconsistent.
[20:57] <Amaranth> packaging and such
[20:57]  * mok0 hugs Amaranth 
[20:57] <Amaranth> although since becoming MOTU i haven't uploaded a single thing...
[20:58] <Amaranth> probably because the only thing i want to has to be uploaded in sync with stuff in main so mvo just does it too :)
[20:58] <nxvl_work> i plan to become a motu by hardy release
[21:05] <ScottK> mok0: So why is theseus FTBFS on everything but i386 it's tried so far?
[21:06] <mok0> ScottK: Beats me. I have looked at the logs and I can't see what's going on
[21:07] <mok0> ScottK: I have no problems building on amd64, but that fails too
[21:07] <ScottK> I suspect I know what it is.  Let me have a look at the package...
[21:07] <mok0> ScottK: Thanks!
[21:10] <slangasek> looks clear to me, arch: any package and the binary-indep target is populated by mistake
[21:10] <slangasek> so it builds with dpkg-buildpackage -b and FTBFS with -B
[21:10] <ScottK> mok0: ^^^
[21:11] <ScottK> Is it meant to be arch all or arch any?
[21:11]  * mok0 tries to understand slangasek
[21:11] <slangasek> it's compiling stuff, so it needs to be arch: any
[21:12] <mok0> slangasek: I will take a look
[21:13] <mok0> It's supposed to be "any"
[21:13] <ScottK> mok0: Look at Debian New Maintainer's Guide section 4.4
[21:14] <mok0> there isn't even an "indep" target
[21:14]  * mok0 looks at DNMG
[21:15] <mok0> ScottK: Still don't understand what you guys mean...
[21:16] <ScottK> You don't define binary-arch
[21:17] <mok0> I thought only "install" was mandatory...
[21:17] <ScottK> Since it's arch:any then you need to define the per-archicture build requirements.
[21:18] <ScottK> i386 works because that's (by coincidence) where arch all packages get build
[21:18] <mok0> ScottK: OK...
[21:19] <mok0> I can introduce the install-arch and install-indep targets
[21:19] <ScottK> So right now you have an arch:any package with nothing to build for the other archs.  I think, but I'm not an expert on this.
[21:19] <mok0> ScottK: However, I can't see that explained in DNMG
[21:20] <ScottK> I was more thinking of the example where on line 51 and on it shows how to set your rules files for arch dependent builds
[21:21] <mok0> ScottK: Got it. Thanks. I guess I should fix it and re-upload to REVU?
[21:21] <ScottK> No.  Since it's just a new debian revision, file a bug and attach a debdiff.
[21:22] <ScottK> Then subscribe UUS
[21:22] <mok0> ScottK: I'll get right on it
[21:23] <mok0> ScottK: So, with every arch except i386, it is built with the -B flag?
[21:23] <ScottK> Yes
[21:23] <ScottK> That sounds right.
[21:23]  * mok0 finally gets it
[21:24] <amarillion> I uploaded a new version of speed-game: http://revu.tauware.de/details.py?package=speed-game
[21:24] <amarillion> All issues have been addressed, it's ready for a review again
[21:26] <ScottK> mok0: Then you're one step closer to being ready.  FYI, I broke Spamassassin to learn this.
[21:27] <mok0> ScottK: yikes
[21:28] <ScottK> I fixed an arch:any problem in the indep part of debian/rules.  It worked for my on i386.  I uploaded and everything else broke.
[21:30] <mok0> ScottK: one of the more tricky packaging bugs...
[21:30] <ScottK> Well now I know.
[21:31] <mok0> So, in fact, binary-arch should be a mandatory target
[21:42]  * rzr updated http://revu.tauware.de/details.py?package=jaaa
[21:43] <ScottK> mok0: It's mandatory for an arch:any package.  Not for an arch:all package
[21:44] <jpatrick> Perdente: welcome!
[21:44]  * mok0 has to check up on his reading...
[21:44] <Perdente> hey!
[21:44] <ScottK> mok0: Here's an arch:all that's the other way around: http://www.openspf.org/svn/software/postfix-policyd-spf-perl/tags/2.005/debian/rules
[21:45] <Perdente> I was looking to help programming any way I can, I have taken some classes and I've been running ubuntu for about a year now and I really want to help program any way I can
[21:45] <mok0> ScottK: thx
[21:46] <mok0> ScottK: ... and that only builds an "all" binary package. Makes sense to me
[21:46] <ScottK> Yes.  And that's all there is for that package
[21:46] <jpatrick> Perdente: prehaps reading the packguide?
[21:46] <mok0> ScottK: What's XS-DM-Upload-Allowed: yes ?
[21:47] <pochu> mok0: to allow Debian Maintainers to upload those specific packages if they are the Maintainers
[21:47] <ScottK> That's a Debian specific thing for Debian Maintainer (which I'm not quite yet) uploading allowed
[21:47] <mok0> ScottK: ah
[21:47] <Perdente> jpatrick, I know this sounds really dumb, but I'm a quick learner, where' the packguide again?
[21:47] <jpatrick> !packguide > Perdente
[21:54] <TheMuso> !packguide
[21:54] <ubotu> The packaging guide is at http://wiki.ubuntu.com/PackagingGuide - See https://wiki.ubuntu.com/UbuntuDevelopment/NewPackages for information on getting a package integrated into Ubuntu - Other developer resources are at https://wiki.ubuntu.com/UbuntuDevelopment - See also !backports
[21:54] <TheMuso> ah right. Thought that didn't work.
[21:58] <pochu> TheMuso: heh, I /msg'ed ubotu too :)
[21:59] <jpatrick> I forwarded it to him ">"
[22:00] <pochu> jpatrick: yeah but packguide vs packagingguide :)
[22:00] <TheMuso> jpatrick: Yeah I saw. Didn't think that was possible either.
[22:00] <jpatrick> pochu: it's an alias now
[22:01] <pochu> looks easier to write :)
[22:10] <RainCT> will Hardy ship with Firefox 2 or 3 by default?
[22:11] <pochu> 3
[22:12] <RainCT> nice :)
[22:12]  * joejaxx is hoping Hardy is not an Edgy-ng :P
[22:14] <Perdente> jpatrick, well looks like this is a nice read how late will you be here today?
[22:15] <jpatrick> Perdente: woah, I should of been off ages ago.., but I'm sure someone would be able to help you out from here, and I'll be on later :)
[22:17] <Perdente> ok, thanks!  I'm just now trying the Debhelper packaging so it will take a little while anyway
[22:18] <ScottK> Perdente: Generally if you have questions it's better to ask the channel so whoever is here and know can answer.
[22:18] <Kmos> RainCT: it will be default after alpha 3
[22:19] <Perdente> ScottK, done and done. :)
[22:20] <persia> Just for reference, in case anyone wants to answer amarillion next time, ISC is preferred to BSD if you are not the Regents of the University of California because /usr/share/common-licenses/BSD can only be used if the the Regents hold copyright on the source, and ISC is shorter, so wastes less archive space when duplicated.
[22:20] <persia> Ng: If you see a changelog in your binary package, ignore my complaint about it being missing.  I didn't see one.
[22:39] <mok0> ScottK: theseus package fixed. I set bug status to "confirmed" but I can't remember if that's the right thing to do.
[22:41] <ScottK> Confirmed or Triaged are fine.  Did you subscribe UUS?
[22:41] <mok0> ScottK: yep
[22:41] <ScottK> Then you should be done except maybe to answer questions.
[22:41] <mok0> Great
[22:42] <ScottK> What bug?
[22:42] <mok0> Bug #181359
[22:42] <ubotu> Launchpad bug 181359 in theseus "FTBFS error on all archs but i386" [Undecided,Confirmed] https://launchpad.net/bugs/181359
[22:43] <ScottK> Maybe persia will take pity on you and have a look at it ^^^.  I'm out of here in 2 minutes.
[22:43]  * persia has very limited time now, and is expected to be deep idle in about 7
[22:44] <mok0> No rush
[22:45] <persia> mok0: Looks sane,  I don't have time to build twice right now, but it ought get picked up soon.
[22:45] <mok0> persia: yeah I think so
[22:46] <ScottK> See you all later.
[22:46] <RainCT> good night
[22:46] <mok0> Goodnight
[22:51] <Ng> persia: I'll check with a fresh build, but I seem to see changelog.gz and changelog.Debian.gz locally
[22:52] <persia> Ng: Sorry about that.  My missing-changelog comment was based entirely on linda's checking logic, but that may not be accurate.  Be sure to try a build against hardy.
[22:52] <Ng> ah that's a good point, I've just been building on gutsy :)
[23:15] <the_belgain> hello - quick question: what's the version naming convention for packaging software which doesn't have fixed release numbers, but just SVN revisions and dates?
[23:16] <mok0> http://www.debian.org/doc/debian-policy/ch-binary.html#s-versions
[23:18] <the_belgain> great, thanks - so the SVN revision isn't appended to the version number
[23:18] <the_belgain> does the SVN revision usually get mentioned anywhere in particular in the package?
[23:18] <the_belgain> debian/changelog maybe?
[23:19] <mok0> the_belgain: doesn't harm to put it theer
[23:19] <pochu> If it's a svn checkout and not an stable tarball, then yes, in the version string (which is both in the files and in debian/changelog)
[23:21] <the_belgain> so the directory name (when using dh_make) should be eg. "packagename_20071219-svn578" ? to get the version string picked up correctly
[23:22] <the_belgain> sorry, i mean packagename-20071219_svn578
[23:23] <jscinoz> persia you here?
[23:25] <pochu> the_belgain: is it a new package?
[23:25] <pochu> or an update?
[23:25] <the_belgain> new package
[23:25] <persia> jscinoz: No.  You'll do better to ask your questions generally, rather than asking me, as I'm really not around much right now (and no, this isn't a joking "no", I just happened to see that on my way out).
[23:27] <pochu> the_belgain: I'd use packagename_0+svn578 then, just in case they release 0.x or 1.x so you don't need to add an epoch
[23:27] <pochu> some people
[23:27] <pochu> already get lots of useless pings
[23:28] <pochu> persia: s/some people/I/ ? ;-)
[23:28]  * pochu runs
[23:28] <the_belgain> will do, thanks (that doesn't seem to be inline with the debian policy manual, but I guess that's OK?)
[23:31] <pochu> the_belgain: why not? If it's a pure svn checkout it does.
[23:32] <the_belgain> ok, fair enough - thanks for all the quick replies
[23:32] <pochu> the_belgain: Or does upstream release tarballs as 20071219?
[23:32] <pochu> In that case it should be 20071219+svn578
[23:33] <the_belgain> http://fuppes.ulrich-voelkel.de/download/
[23:33] <the_belgain> the tarballs aren't explicitly dated
[23:34] <pochu> that's  fuppes-SVN-578.tar.gz, so I'd go with 0+svn578
[23:45] <jscinoz> :P
[23:49] <jscinoz> hey guys
[23:50] <jscinoz> if i have non-free components that cant be included in the source package and are small file size can these be downloaded via the preinst script?
[23:54] <slangasek> only if the package is in multiverse
[23:54] <slangasek> if it's in universe, installing it shouldn't pull non-free bits onto the system
[23:55] <the_belgain> i have a package which has dependencies in multiverse (lame in this case) - does that mean the package should be in multiverse?
[23:55] <the_belgain> presumably yes?
[23:55] <ScottK> Yes
[23:55] <the_belgain> just checking, thanks