=== luciano_ is now known as virusuy
[05:01]  * virusuy is away: "partiendose la boca con un chivito, ya vuelvo"
[05:08] <micahg> !away > virusuy
[05:08] <ubottu> virusuy, please see my private message
[05:13]  * virusuy is back (gone 00:12:12)
=== Quintasan_ is now known as Quintasan
[15:46] <AnAnt> ScottK: regarding LP #769101, do you know what in launchpad to file a bug against ?
[15:46] <ubottu> Launchpad bug 769101 in lintian (Ubuntu) "[FFe] Please merge lintian 2.5.0~rc3 (main) from Debian unstable (main)" [Undecided,New] https://launchpad.net/bugs/769101
[16:09] <AnAnt> bdrung_: ^
[16:13] <bdrung_> AnAnt: i am not sure. you may ask in #launchpad
[16:36] <AnAnt> bdrung_: ok, there is a bug filed already, thanks to micahg
[20:00] <rgl> hi
=== nhandler_ is now known as nhandler
[21:05] <bdrung_> tumbleweed: what mapping do you need for mk-sbuild?
[21:06] <tumbleweed> bdrung_: both directions
[21:07] <bdrung_> tumbleweed: and api for it?
[21:07] <tumbleweed> --devel is useful for distro-info, but something that took "unstable" would be handy in debian
[21:08]  * tumbleweed thinks about an API
[21:09] <tumbleweed> is there agood name for debian's release synonyms?
[21:10] <bdrung_> i don't know any
[21:10] <bdrung_> "symlink" isn't a good name
[21:11] <tumbleweed> "distribution" seems common, but that's confusing in this scenario
[21:11] <tumbleweed> alias is about the best I can do
=== hannesw_ is now known as hannesw
[21:14] <tumbleweed> bdrung_: how about --codename-for=alias, --alias-for=codename, and --aliases ?
[21:14] <tumbleweed> that would still exclude experimental, I think, but that's ok. experimental is weird
[21:15] <tumbleweed> err maybe s/alias/dist/ ?
[21:16] <tumbleweed> or even suite
[21:17] <tumbleweed> that might be the most accurate (it matches Rleease files, for a start)
[21:54] <bdrung_> tumbleweed: so we have alias, dist, codename, and suite. which of them should we use?
[21:55] <tumbleweed> I think suite is the correct term, although we don't use it in many places, I use it in ubuntutools.archive
[21:55] <bdrung_> tumbleweed: is suite used in Debian?
[21:56] <tumbleweed> in Release files
[21:56] <tumbleweed> also in dak
[21:57] <bdrung_> tumbleweed: ok. then let's use codename and suite
[21:58] <bdrung_> --codename-for=suite and --suite-for=codename sounds ok for me
[21:58] <tumbleweed> DktrKranz: ^ is that correct usage of the term suite?
[22:21] <DktrKranz> tumbleweed: it is, if you refer to 'sid', 'wheezy', 'experimental'
[22:23] <tumbleweed> DktrKranz: thanks
[22:25] <DktrKranz> tumbleweed: 'unstable', 'testing' are now mappings to those
[22:25] <tumbleweed> DktrKranz: so you'd call unstable, testing, etc. "mappings" ?
[22:26] <DktrKranz> you can refer to suites, mappings are dak internals
[22:27] <tumbleweed> I want to know what to call "unstable" and "testing", as opposed to their code names "sid" and "wheezy"
[22:28] <bdrung_> suite = sid, wheezy, experimental, natty, lucid?
[22:32] <DktrKranz> http://paste.debian.net/plain/114988
[22:32] <tumbleweed> DktrKranz: fantastic, looks like suite is appropriate then
[22:32] <DktrKranz> we still use 'unstable' as suite, while 'sid' is codename
[22:33] <DktrKranz> not sure if that will change soon (plans for that)
[22:33] <tumbleweed> does that mean this will change?
[22:33] <tumbleweed> right
[22:33] <DktrKranz> but for now, you can use that scheme
[22:33] <tumbleweed> well someone will have to come up for a name for those aliases if it does change :)
[22:34] <DktrKranz> $whytheheckwedecidedtochangethem
[23:38] <Kano> hi, did anybody use bootchart with natty?