[05:41] <freeflying> I wonder have we rebuild all packages in universe before we release?
[05:43] <persia_ume> freeflying: Ideally, we would, as there are many that have issues if not rebuilt.  Historically, we haven't due to the buildd processor load.  Please rebuild anything where you know it will have a positive effect.
[05:44] <persia_ume> Note also that for FTBFS detection, there are universe rebuild logs available from ubuntuwire, although I wouldn't expect the first intrepid run until after DIF.
[05:45] <freeflying> persia_ume: I found eva in hardy can not run
[05:58] <persia_ume> freeflying: And it runs with a rebuild?  Sounds like an SRU candidate to me (although I'm not an SRU person)
[05:59] <freeflying> persia_ume: ok, thanks, I'd like sync it from sid directly :)
[06:00] <persia_ume> freeflying: A SY
[06:00]  * persia_ume grumbles at mismath
[06:01] <persia_ume> ched timn y keybaords
[06:01] <persia_ume> freeflying: A sync?  What
[06:01] <persia_ume> For hardy?  What changed?  Isn't there a simpler way for SRU?
[06:04] <freeflying> persia_ume: eva in universe is really not in a good shape, was pacakged about 2 years ago, And recently I repacakge it, it in debian new queue, so I prefer to drop the one in universe, and sync it directly from debian :)
[06:04] <persia_ume> freeflying: Understood.  For intrepid, that makes sense.  FOr hardy, I'd recommend getting the opinion of someone in motu-sru beforehand.
[06:05] <freeflying> persia_ume: yes :)
[06:06] <bluefoxicy> fuck
[06:06] <bluefoxicy> Ubuntu was like, REBOOT
[06:06] <bluefoxicy> and I'm like ?_?
[06:07] <bluefoxicy> start tabbing around... system rebooted via gdm
[06:07] <bluefoxicy> so while I'm looking at stuff on the net it just DECIDES it's a good idea to reboot
[06:07] <freeflying> bluefoxicy: sure not
[08:56] <AnAnt_> Hello, is there a way that I can know which physical volume does a logical volume map to ?
[08:57] <Hobbsee> surely that's an #ubuntu question...
[08:58] <AnAnt_> Hobbsee: ah, ok. I asked here because I need to do it for a package
[08:58] <AnAnt_> Hobbsee: to install grub splash
[08:58] <AlfaOmega08> Hello, I've a new deb package for nasm... From version 0.99 to 2.02. How can I upload it? I'm part of revu-uploaders group on Launchpad
[09:18] <soren> AnAnt_: "lvdisplay -m" is your friend, though.
[09:22] <AnAnt_> soren: thanks
[09:25] <soren> np
[10:01] <AlfaOmega08> Hello
[10:01] <AlfaOmega08> I've send a new nasm package to revu
[10:01] <AlfaOmega08> can someone review that package? Thanks
[11:31] <bobbo> When syncing do you create a debdiff between the two ubuntu versions or the latest debian version and the new ubuntu version?
[11:33] <bobbo> s/syncing/merging/
[11:35] <Laney> bobbo: Both
[11:35] <bobbo> Laney: ah, thanks :)
[13:23] <sebner> persia: around?
[13:26] <Hobbsee> sebner: probably not - they're out exploring cz today.
[13:27] <sebner> Hobbsee: damn. whois says that he was active 8 min ago. but nvm :)
[13:27] <Hobbsee> sebner: hmm, he may be around hacking, then.
[13:27] <sebner> Hobbsee: kk, thanks. not that important :)
[13:29] <persia> sebner: Yes, but delayed
[13:30] <sebner> persia: nvm. just wanted to tell you that we *won* the gmsh fight =)
[13:31] <persia> sebner: Fight?  Won?  Do you mean that my very old bug finally got closed, as an example of cooperation in the free software community?
[13:31] <sebner> persia: yes ^^
[13:31] <persia> \o/
[13:31] <askand> Hi! I while ago I got help from this channel when making a debdiff for gmail-notify to fix a bug in gmail-notify. Now I want to fix bug 213367 but first I want to know if there is a reason iptcsupport has been left out? Anybody knows?
[13:31] <sebner> persia: I added a comment and the maintainer accepted it \o/
[13:32] <persia> sebner: Does the old .desktop file still validate, or did you update it?
[13:33] <persia> askand: Have you reviewed /usr/share/doc/gthumb/changelog.Debian.gz?  If it's not listed there, probably not (although main/universe concerns may aly, depending)
[13:33] <persia> s/aly/apply/
[13:34] <sebner> persia: hmm to be honest I didn't except a reaction. just the Encoding thing is obsolete IIRC. And the dh_desktop thing was ignored since they use cdbs now
[13:36] <sebner> persia: I'll file a bug about the Encoding key ^^
[13:37] <sebner> persia: oh. no no no
[13:37] <sebner> persia: the debian maintainer rocks
[13:37] <sebner> persia: he removed the encoding thing. *happy*
[13:41] <askand> ﻿ persia: There is nothing in the changelogs about iptc, only that bug 438716 has been fixed
[13:41] <askand> ﻿ persia: Hm, I guess the bug is really gone since ubottu doesnt tell what it is about..
[13:42] <askand> ﻿ persia: "Fixed Bug #438716 - IPTC comments are not seen by Picasa"
[13:43] <\sh> moins
[13:44] <sebner> hiuhu \sh
[13:44] <LucidFox> By the way, why was ubotu renamed ubottu?
[13:44] <geser> Hi \sh
[13:45] <Hobbsee> LucidFox: owner change.
[13:45] <Hobbsee> LucidFox: they havent' got the old passwords, etc, for the old bot.
[13:45]  * \sh tries to give gajim now a qt frontend
[13:45] <\sh> let's see what's the new world order in qt4
[13:46] <sebner> \sh: -.-
[13:46] <sebner> I can't understand what everybody has with this kde4 and qt4 thing -.-
[13:48] <LucidFox> ah
[13:49] <\sh> sebner: it's a german proudness thing ;)
[13:49] <sebner> \sh: hmm? qt = trolltech = norway?
[13:50] <\sh> sebner: kde == germany ,-)
[13:51] <sebner> \sh: no comment ;P
[13:54]  * Nafallo steals \sh crackpipe.
[13:54] <persia> askand: Sorry.  Tech demo.  That sounds like a bug number in the Debian BTS.  Check out bugs.debian.org
[13:56] <askand> ﻿persia: no luck
[13:56]  * \sh doesn't smoke crack...I'm serious ;)
[13:56] <sebner> \sh: heroin, heroin, heroin
[13:56] <sebner> persia: are you now proud of my? ^^
[13:58] <\sh> oh no da reportbug again
[14:00] <persia> sebner: I've lost reference
[14:00] <sebner> persia: -.- Now I'm disappointed xD
[14:01] <sebner> persia: I asked if you are proud of my now because we won the gmsh fight, with at least my comment ;)
[14:05] <askand> ﻿persia: I find no reason it is built without iptc support
[14:10] <geser> askand: the problem is gthumb is in main and libiptcdata in universe.
[14:11] <geser> askand: to make it possible to build gthumb with libiptcdata either gthumb should be moved to universe or libiptcdata to main
[14:12] <askand> ﻿geser:  and if I understand things correctly the first should be easier to achieve? :P
[14:13] <persia> askand: To do that, nothing else in main can depend on gthumb, including the metapackages.
[14:15] <sebner> persia: you are in the same timezone like me. wicked, isn't it?
[14:17] <sebner> \sh: you comment on the ML is strange. what speaks against the current DaD comments system?
[14:17] <askand> ﻿persia: I see..what is keeping libiptcdata out of main?
[14:18] <geser> askand: probably because nobody tried to move it to main yet (the was no reason till now)
[14:19] <askand> ﻿geser: I see, well im ready to try :)
[14:19] <\sh> sebner: as I said before, I do think it's bad to use two different tools...MoM and DaD are going to merge at sometime, and using LP for working tasks is also useless...
[14:20] <persia> \sh: But some of us don't use either MoM or DaD, but we all use LP for various reasons.
[14:20] <sebner> \sh: well, we need one tool with comment function and if everybody uses it we can be happy. for LP. we have this great tool, why not using it
[14:21] <geser> !MIR
[14:21] <geser> askand: ^^^
[14:21] <\sh> persia: yes..that's why we should improve the tools, or if it's not wanted to be improved (remember, LP is a businesscase and not a playground for community) we need to find something else...
[14:22] <\sh> persia: I need MoM also only for checking what I touched last..nothing else...the rest is done via console and some mail tools like requestsync ...
[14:23] <persia> \sh: I'm not sure about "not wanting to be improved", and I also consider that LP is a default tool, rather than a subject for change.  I think not using LP makes it not Ubuntu (and there is a lot of that)
[14:23] <\sh> persia: if we would have proper tools to query LP fast enough to get a list of working tasks, ok..if not, we need something else
[14:23] <sebner> however. /me ---> nexuiz =)
[14:23] <askand> ﻿geser: Im not sure I understand how to get all the info required for  https://wiki.ubuntu.com/MainInclusionReportTemplate
[14:23] <persia> \sh: Speed aside, don't we?
[14:25] <\sh> persia: no we don't have those tools...e.g. it would be an easy way to file "merge bugs" to LP from our merging tools .. why not implementing it...and having a "lpquery --lu <your changelog eMailaddr> --type merge" would be great...
[14:26] <\sh> persia: but seeing that Canonical/Ubuntu QA has something against using LP as task tracker...I doubt we will get so far in the near future
[14:26]  * \sh <-- having a smoke
[14:27] <geser> askand: just ask, I assume someone might help you with specific points
[14:27] <persia> \sh: I'm not that bothered about that.  Consider that Ubuntu is the interesting user, rather than Canonical.  While Canonical is a major sponsor of Ubuntu, it is meaningfully distinct.
[14:32] <\sh> persia: Well, Ubuntu is the "main customer" of LP, and therefore a good business usecase for Canonica, no discussion here. But if we want to pull more contributors for our tasks, we should be able to find ways to use LP for our needs, so that nobody intereferes how we use it...and right now, there is a lot going on regarding using LP as tool for workflow and the disagreement of Canonical/Ubuntu QA of doing so. I don't say, we should move away from
[14:32] <\sh> LP, but we need a bit more freedom to make it work for our workflow needs.
[14:34] <\sh> If we have an agreement of filing workflow reports to LP for haveing one merge bug per package, -> good ... if someone is going to mark them invalid and close them -> bad
[14:34] <persia> \sh: I agree with a lot of that, but...
[14:35] <geser> where ever we file our workflow bugs/tickets it should be in one place and not split across several tools: e.g. one for handling merges and LP for handling syncs
[14:35] <Hobbsee> LP is supposed to have API's soon.
[14:35] <persia> Firstly, I very much believe we ought be looking at the bugs anyway.  I find it veryfrustrating when encountering packages ith easy bugs ignored for years just because it was merged blindly.
[14:35] <Hobbsee> so it should only be a problem this cycle, i guess.
[14:35] <geser> Hobbsee: please define "soon"
[14:36] <Hobbsee> geser: not allowed, and i don't know the exact date.
[14:36] <geser> will it more this year or this decade?
[14:36] <Hobbsee> this year
[14:37] <persia> That said, I think MOTU is a considerable part of the QA process, and we need to better coordinate how we manage the bug process.  It's not just about triage, or about merging, it's about improving quality.
[14:38] <\sh> Hobbsee: I'm a non believer in feature announcements ;) it's done when it's done is much better...
[14:39] <Hobbsee> heh
[14:39] <Hobbsee> OTOH, there's little point in discussing bugs, until heno and crew decide how MOTU should actually use the bugtracker.
[14:39] <persia> Hobbsee: No.
[14:40] <\sh> persia: yes...so what's the problem to make MoM/DaD file merge bugs against packages and assign them to the last uploader? so we are able to track our own "assigned" bug lists?
[14:40] <persia> It's for us (being developers and bug triagers) to determine that.  Not only heno.
[14:40] <persia> \sh: Actually, I kinda like that model.
[14:40] <Hobbsee> persia: doesn't matter what we decide.  if heno doesn't agree, all documentataion about it will be removed, and bugsquad will play with the bugs, unless it follows their rules.
[14:42] <persia> Hobbsee: Once is maybe miscommunication.  Multiple times would be wiki-wars, and something for CC.
[14:42] <persia> Anyway, heno wants to talk about it this coming week.  Let's see how the discussion goes.
[14:42] <\sh> Quote of Constantine: "I saw a fullfleged QA boss [demon] out there and he attacked me and I pulled out a QA boss [demon] out of a little girl" "Constantine, we are fingerpuppets to them, not doorways"
[14:44] <lifeless> someone remind me: do we care to accelerate removals in ubuntu when the debian removal bug is already filed ?
[14:45] <\sh> lifeless: if it's reasonable and agreed, yes we can do it much more quicker then debian...but sometimes it's good to wait for debian to do so
[14:46] <\sh> but sometimes it makes a mess to other packages (thinking about the baz  stuff removal and ftbfs of some packages because of that, because no one checked beforehand)
[14:48] <\sh> and seeing it now in intrepid again to be re-introduced
[14:51] <\sh> lifeless: any idea of pybaz now in intrepid again, when you asked for removal on 2008-04-11 during hardy cycle?
[14:51] <\sh> bug #214955
[14:54]  * \sh is asking, because config-manager has now a missing feature, and I would like to reintroduce it again without having fear that the package is broken after release
[14:54] <askand> How do I know if it is "any binaries running as root or suid/sgid ?"
[14:55] <\sh> lintian message?
[14:57]  * \sh goes to sleep for an hour or so...
[14:59] <LucidFox> What's with all the random chroot problems?
[15:30] <wolfger> good morning, Motu
[15:31] <wolfger> I'm trying to update a package following the packaging guide, and it fails. Need some help (it's a python app).http://www.paste2.org/p/29202
[15:32] <cyberix> What is it with popularity contest?
[16:30] <emgent_UDS> heya
[16:32] <sebner> huhu emgent you UDS guy :)
[16:32] <sebner> huhu emgent_UDS  you UDS guy :)
[16:32] <sebner> ^^
[16:33] <emgent_UDS> heya sebner :D
[16:36] <sebner> emgent_UDS: How is the weather 450km away from me? ^^
[16:42] <LucidFox> What's UDS?
[16:44] <wolfger> LucidFox: Ubuntu Developer Summit
[16:44] <LucidFox> ah
[16:44] <Iulian> LucidFox: https://wiki.ubuntu.com/UDS-Intrepid
[16:58] <geser> LucidFox: debconf (or some other package) broke the buildd chroots. it needs manual fixing by the admins.
[17:00] <Iulian> I'm trying to upload a package to revu but I get a strange error - http://paste.ubuntu.com/13056/plain/
[17:00] <Iulian> Am I missing something?
[17:04] <geser> Iulian: how did you try to upload?
[17:05] <Iulian> geser: dput revu *_sources.changes
[17:05] <geser> and it tried to use scp? hmm.
[17:06] <Iulian> geser: This is my /etc/dput.cf file - http://paste.ubuntu.com/13057/plain/
[17:07] <geser> try adding "method = ftp" to it
[17:07] <Iulian> geser: God bless you.
[17:09] <Iulian> It worked.
[17:19] <LucidFox> PPA doesn't support backports, does it?
[17:19] <LucidFox> that is... build-depends from the official hardy-backports
[17:28] <bddebian> Heya gang
[17:28] <sebner> hiuhi bddebian
[17:29] <bddebian> Hi sebner
[17:29] <bddebian> sebner: belated congratulations btw!
[17:29] <sebner> bddebian: hmm? ahh. thanks ^^
[17:30] <emgent`UDS> heya
[17:31] <bddebian> Heya emgent`UDS
[17:31] <geser> Hi bddebian
[17:31] <bddebian> Heya geser
[17:36] <Iulian> Hello bddebian
[17:45] <bddebian> Hello Iulian
[18:30] <theseinfeld> I have a question
[18:30] <theseinfeld> i have to migrate from debian/*.files to *.install
[18:31] <theseinfeld> any good ideas how to do it?
[18:31] <theseinfeld> :D
[18:33] <laga> ScottK-uds: did you hunt down the pulseaudio guy? ;)
[18:34] <ScottK-uds> No.  I've just arrived.
[18:34] <ScottK-uds> I don't actually know for sure that's the problem yet.
[19:16] <pwnguin> is awk considered slow at what it does?
[19:16] <pwnguin> awk '{ total += $NF } END { print total }' big-access-log
[19:18] <pwnguin> im reading a set of slides about python generators (continuation based stuff) and python's beating out awk
[19:28] <jdong> pwnguin: awk is probably slow at what it does
[19:29] <jdong> pwnguin: and yeah python (bytecode compiled) and JIT'ed languages of course will be faster
[19:37] <pwnguin> jdong: what?
[19:37] <pwnguin> its an I/O bound process
[19:38] <jdong> pwnguin: are you sure that's IO bound?
[19:38] <jdong> pwnguin: awk can get pretty CPU intensive on something like that
[19:39] <pwnguin> then I guess awk does suck
[19:39] <pwnguin> i thought it was one of those highly engineered ancient unix programs like grep
[19:41] <pwnguin> its run on an apache log file, so its not a very complex domain
[19:43] <jdong> pwnguin: I think the tinier awk implementations such as mawk do better than GNU AWK in terms of performance.
[19:43] <jdong> pwnguin: but IMO they were written with the mantra of simplicity first.
[19:46] <pwnguin> jdong: I found an irate MIT professor who might be pacified by a backport (once the requirements are met)
[19:47] <pwnguin> apparently the xournal developer is an MIT math professor and fedora user upset that hardy didnt catch his latest release two months ago
[19:47] <jdong> pwnguin: yay :)
[19:48] <jdong> pwnguin: should I watch my back on campus in the mean time?
[19:48] <pwnguin> or you might ask him how he decides to release things
[19:50] <ihavenoname>  i would like to create a debian packaging software that will cater to all kinds of debian based distro but dunno what's the differences between distros. can anyone kind anough to point me to the right direction?
[19:52] <pwnguin> ihavenoname: find your nearest university
 : great you're being helpful
[19:53] <pwnguin> well ok, which part of the current software are you aiming to replace?
 : if you're so all knowing can you explain why a debian package packed for ubuntu does not work on other debian based? i know how to pack a package
 : im not aiming to replace any
 : my aim is to create a user-friendly gui for dpkg-build
[19:54] <pwnguin> there is a core set of packages that are assumed to be present
[19:55] <pwnguin> if libc is newer on debian, you could be in a heap of trouble
 : correct me if im wrong ... the only differences between debian packages is how you structure the install path and how to link the dependencies that will satisfy to the target distro's package naming convention ...
[19:57] <RainCT> ihavenoname: Debian and Ubuntu packages are essentialy the same (actually, most of Ubuntu's packages are taken unchanged from Debian)
[19:57] <pwnguin> source packages are ok, but the binaries are not generally compatible
[19:57] <azeem> ihavenoname: it's a matter of recompiling against the respective distribution environment
[19:57] <laga> ihavenoname: are you talking about source packages or about binary packages? it'll be easier if you jsut create source packages which are built on the target distro.
[19:57] <laga> jinx.
[19:58] <RainCT> ihavenoname: the "problem" (which is not really a problem) is that many packages are not binary compatible. that is, if it was build for Debian it will only work on Debian, and the other way around
 <azeem> : i have to cater both source and binary... and most if not all debian based distributions
[19:58] <azeem> ihavenoname: then you've lost
[19:58] <azeem> ihavenoname: you could as well just do LSB packages
 : like i said i have to cater both
[19:58] <laga> or you link your packages statically. which isn't a good idea.
[19:59] <pwnguin> that said, if you're writing a gui frontend to pbuilder / dpkg-build, that's at least the best approach
[20:00] <laga> yeah, if you have pbuilder, you can build individual packages for each distro.
[20:01] <ihavenoname> so u guys come in to conclusion that this idea is a complete waste ( a lost cause that is ) ---> http://brainstorm.ubuntu.com/idea/8258/
[20:02] <laga> if you want to make a GUI app which builds _one_ binary package which is to work on _all_ debian-ish distros.. then that's a waste of time. of course, source packages will work and you can rebuild them on the distros you need.
[20:03] <laga> and TBH, a GUI tool to create deb packages sounds like something which will cause much grief among developers. there's no one-size-fits-all packaging approach. much brokenness might ensue.
 : that's what i was thinking about...
[20:03] <laga> ihavenoname: besides, http://brainstorm.ubuntu.com/idea/8258/ is different from your requirement.
[20:04] <laga> that person said nothing about the packages having to work on all debian-ish distros
[20:04] <pwnguin> laga: it cant be worse than checkpkg
[20:04] <pwnguin> or makeinstall
[20:04] <pwnguin> err
[20:04] <pwnguin> checkinstall
[20:04] <emgent`UDS> heya
[20:05] <laga> jhoger sums it up nicely. "Sorry, there's no way to "can" the abilities of a good DD. "
[20:05] <laga> pwnguin: yeah, but the sheer amount of packages created by such a tool :)
 : not actually totally different personally i like the way debian package maker creates the package but i saw this post ---> http://code.google.com/p/debianpackagemaker/issues/detail?id=3 ...  a user asking for a gui app that caters to most of debian based distros...
[20:06] <ihavenoname> !pastebin
[20:07] <laga> ihavenoname: the posting written by lexen1 is still different from your requirements. he talks about a tool which will output a package that is specific to one distribution (eg gutsy) and can do so for many distros. you were talking about a piece of software that'll generate one package for all distros.
[20:07] <laga> maybe you'd like to find out what you actually wanna do :)
 : you got me all wrong.. ....
 : i want to implement lexen1's idea
[20:10] <pwnguin> that gui's a bit of a nightmare
[20:10] <ihavenoname> i would like to create a guid app for dpkg-builder that will cater to most debian based distro i am not talking about one debian for all but gui app that will let you select what type of debian package you will going to create...
 : what gui?
[20:11] <pwnguin> debianpackagemanager
 : but it's a good start
 : so can you point me to the right direction?
[20:12] <pwnguin> ihavenoname: if you just want an app to take a source package and generate _one_binary package to work on a _specific_ distro, that's possible
 : i know its possible but i dunno where to start.. im not familiar with all debian system... all am familiar with is ubuntu
[20:13] <azeem> ihavenoname: just setup a chroot for every distro you want to build with
 : what about package dependencies am sure various debian system have different package dependencies
[20:14] <azeem> ihavenoname: as mention above, most of them are
[20:14] <azeem> done at build time
[20:14] <Laney> ihavenoname: The source package specifies the build-dependencies
[20:14] <pwnguin> ihavenoname: most build deps are versioned
[20:14] <pwnguin> if they need to be
[20:14] <azeem> most build-deps are unversioned
[20:15] <ihavenoname> which is which? versioned or unversioned?
[20:15] <pwnguin> dont listen to me
[20:16] <laga> there's lots of *excellent* drama on brainstorm. i'd want some real discussion instead, though :)
[20:17] <ihavenoname> do sources have to be present? i mean some developers are not using standard make files
[20:17] <ihavenoname> or using standard programming lang
[20:17] <azeem> ihavenoname: that's a seperate issue
[20:18] <emgent`UDS> hi persia :)
[20:18] <ihavenoname> ok thanx for the info
[20:21] <TheMuso> mgeHey there. Nice to know you arrived safely.
[21:29] <Adri2000> for those who are wondering about DaD, yes it's broken, sorry about that. no space left on / + DaD not handling that correctly ate all the merges. it should be up again soon, with a few days old comments backup.
[21:30] <sebner> Adri2000: ah, thx for the status update =)
[21:39] <sebner> gno folks
[22:38] <imbrandon> ello™ ello™
[22:38] <RAOF> Yo!  imbrandon.
[22:40] <ajmitch> hi imbrandon
[22:49] <jdong> imbrandon: dey know! dey know!
[22:49] <jdong> (anyone who got that song reference should seek professional help)
[23:05] <Syntux> Good day
[23:06] <imbrandon> ugh anyone else here semi familiar with java + mysql ?
[23:07] <mok0> ugh. Not me
[23:24] <pwnguin> i propose debian should patch openSSL to add the newest clint adams blog entry as a source of entropy
[23:25] <jdong> pwnguin: my GPA is a better source of entropy...
[23:26] <wgrant_> pwnguin: Agreed.
[23:35] <mok0> I vote for random.org
[23:36] <ScottK-uds> I didn't see anything that seemed abnormal for his blog.
[23:36] <mok0> Heyyyy Scott!
[23:36] <mok0> How's Prague?
[23:41] <ScottK-uds> mok0: I haven't seen much of it.
[23:42] <ScottK-uds> Hotel is very expensive.
[23:42] <ScottK-uds> mok0: I just replied to your mail in the contributions thread.  I don't think there's any API exposed by LP to file a bug and get a bug number back.
[23:42] <ScottK-uds> I could be wrong though.
[23:43]  * ScottK-uds needs to get to bed.
[23:43] <pwnguin> ScottK-uds: i just mean in general. if you use the same one, its not random
[23:44] <ScottK-uds> Right
[23:44] <mok0> OK, good night, ScottK
[23:45] <mok0> ScottK, I think you can do it with bugnumbers
[23:52] <ScottK-uds> Then that'd take away most of my non I find LP annoying reasons.