[00:04] <ianm_> how should I get rid of the old/unused branch?  https://code.launchpad.net/luz
[00:05] <ianm_> by vcs-imports
[00:06] <mwhudson> ianm_: ask a question at answers.launchpad.net/launchpad-bazaar
[00:09] <ianm_> mwhudson: done https://answers.launchpad.net/launchpad-bazaar/+question/54488
[00:13] <ianm_> thanks
[00:19] <guax> Sorry, there was a problem connecting to the Launchpad server.  - Try reloading this page in a minute or two. If the problem persists, let us know in the #launchpad IRC channel on Freenode.
[00:19] <guax> got this on http://bazaar.launchpad.net/~wicd-devel/wicd/trunk/files
[00:24] <spm> well guax has left, fyi everyone else, just bounced codebrowse.
[00:30] <tim_abell> nuts. when it said 'name' i thought it meant /my/ name! https://launchpad.net/tim-abell
[00:30] <tim_abell> apparently i am now a piece of software
[00:31] <tim_abell> would anyone care to file a bug against me? eg, '... is an idiot'
[00:31] <spm> tim_abell: would you like me to remove that for you?
[00:31] <tim_abell> yes please :)
[00:31] <spm> or rather rename?
[00:31] <tim_abell> rename would be better
[00:31] <tim_abell> photo-frame-prep is what i was after
[00:32] <tim_abell> :D
[00:32] <spm> one sec
[00:32] <tim_abell> nice one
[00:32] <tim_abell> ps, launchpad is the best idea ever
[00:32] <spm> https://edge.launchpad.net/photo-frame-prep
[00:33] <johannes> are you moving from github to lp? outof curiosity: why?
[00:33] <spm> err - drop the edge bit - sorry
[00:33] <tim_abell> super, thanks a millions
[00:33] <tim_abell> or many millions perhaps
[00:33] <spm> tim_abell: heh - you're as imaginative at names as we tend to be :-) we almost had something like "this_is_a_script_to_separate_wodgets_from_wibbles_on_pyhton_and_postgresql.py"
[00:34] <tim_abell> lol
[00:34] <tim_abell> it's a little geeky gift for the gf and her photo frame
[00:34] <spm> cool
[00:34] <tim_abell> engineer!=creative type
[00:35] <spm> Terry Pratchett's: Leonard of Quirm is my role model ;-)
[00:35]  * tim_abell breaks out wikipedia to pretend he remebers
[00:35] <tim_abell> and can spel
[00:36] <johannes> now that here's life: how to milestones and releases work together? I expected to be able to link a release t milestone ("hey that's done") but I don't find a way but they seem to be independent ...
[00:37] <jml> spm: mine's Bloody Stupid Johnson.
[00:37] <tim_abell> heh, excellent
[00:37] <tim_abell> thanks again for your help
[00:37]  * tim_abell returns to semi-reality
[00:38] <spm> jml: remind me to never run any of your code in production. oh. wait. epic fai........<beeeeeeep> ;-)
[00:38] <jml> spm: not *all* of my software has a horribly fatal flaw.
[00:39] <spm> spm 1, jml 0 :-P
[00:41] <spm> ... more like spm 1, jml 7395. but lets not quibble over details
[00:41] <jml> :)
[00:42] <ianm_> how do you specify that a branch is part of a series?
[00:42] <spm> johannes: tbh, aren't too sure myself. I tend to use milestones as a "target" - something to aim towards; "releases" being a stake in the ground - this happened then. type of thing.
[00:45] <ianm_> mwhudson: so I've switched the "initial-import" series over to use my trunk branch, is that enough to now delete the ~vcs-imports/luz/trunk branch?
[00:46] <ianm_> mwhudson: https://code.launchpad.net/luz
[00:53] <tim_abell> well, after all that, i'm pleased to announce https://launchpad.net/photo-frame-prep version 0.00000001 :)
[00:54] <tim_abell> can launchpad read from github? not that it matters, i'm just curious
[00:58] <ianm_> watch for roundoff error on the version number ;)
[00:58] <ianm_> tim_abell: want some feedback on the GUI?  ﻿http://www.github.com/timabell/photo-frame-prep/wikis/screenshots
[01:00] <tim_abell> um, sure
[01:00]  * tim_abell hides
[01:00] <mwhudson> ianm_: it's gone
[01:01] <ianm_> mwhudson: thanks!  can I rename the series too?
[01:01] <mwhudson> ianm_: yep
[01:01] <tim_abell> ok, hit me ianm_
[01:02] <ianm_> ﻿tim_abell: (I'll be gentle) ok, in no particular order...
[01:02] <ianm_> tim_abell: are you using GLADE for the GUI?
[01:03] <tim_abell> to be honest, i can't remember, it was my first encounter with python guis
[01:03] <tim_abell> and i did it a few months back now
[01:03] <ianm_> tim_abell: did you use a graphical GUI design tool?
[01:03] <tim_abell> yes
[01:04] <tim_abell> oh yeah, there we go http://www.github.com/timabell/photo-frame-prep/tree/master/gui.wxg wxGlade
[01:04] <johannes> spiv: and how do you say "aim reached"? Simply setting the miletone inactive?
[01:05] <ianm_> tim_abell: 1) window should have a 6px border width
[01:05]  * tim_abell takes notes
[01:05] <ianm_> tim_abell: GTK has a "pick directory" button widget, I recommend you use that
[01:06] <ianm_> tim_abell: 3) use a stock button for Go, which will give it an icon and free translation
[01:06] <spiv> johannes: ?
[01:06] <johannes> ag
[01:06] <johannes> arg
[01:06] <johannes> was to spm :-)
[01:06] <tim_abell> cool, thanks ianm_
[01:06] <ianm_> tim_abell: the "process subfolders" checkbox belongs up with the Input Directory widgets, probably right under the new "Pick Directory" button
[01:07] <tim_abell> i'll make a note for myself in the bug tracker for next time i look at it
[01:07] <tim_abell> yes, good point
[01:07] <spm> johannes: heh. you aren't the only one to do that; usually it's the other way. People ping me vs spiv :-)
[01:08] <johannes> that goes worse,myformer boss was called "johann" and a colleague "jo" - that's fun on internal irc :-)
[01:08] <spm> johannes: in answer tho: via "here's the new hotness tarball"; that is the release, an annouce is separately made (ooo reminds me did a release on the w/e - need to announce). the milestone is then ignored - effectively - expect for historical purposes.
[01:08] <spm> I'm not suggesting I like this tho. Seems.. untidy.
[01:09] <tim_abell> logged as https://bugs.launchpad.net/photo-frame-prep/+bug/308044 seeing as i have a memory like a sieve
[01:09] <tim_abell> ooh, spooky
[01:12] <ianm_> tim_abell: http://launchpadlibrarian.net/20426976/Export%20to%20Photo%20Frame.png
[01:12] <ianm_> tim_abell: something like that...
[01:12] <tim_abell> wow
[01:12] <tim_abell> that's cool
[01:15] <johannes> spm: ok, good, I at least didn't miss an option to do that then :-)
[01:15] <ianm_> tim_abell: http://developer.gnome.org/projects/gup/hig/2.0/design-window.html
[01:16] <ianm_> mwhudson: thanks for the help.  it looks way better now.  just "lp:luz.  Series: trunk"
[01:16] <tim_abell> oh, i'd never looked at that (as you can tell). thanks, this is all most helpful
[01:17] <mwhudson> ianm_: good :)
[01:17] <ianm_> mwhudson: it was becoming a problem, people checking out the old version via the instructions "bzr branch lp:luz"
[01:19] <ianm_> mwhudson: how can I 'bzr upgrade' the branch in launchpad?  it keeps telling me to do that for better performance
[01:19] <ianm_> Format <RepositoryFormatKnit1> for lp-44825360:///~ian-mcintosh/luz/trunk/.bzr is deprecated - please use 'bzr upgrade' to get better performance
[01:20] <mwhudson> ianm_: bzr upgrade lp:luz should do it
[01:20] <mwhudson> ianm_: though i can do that for you from a machine in the data centre if you like, which will be much quicker
[01:20] <ianm_> sure if you like.  is it safe?  I don't have a complete checkout (just lightweight ones)
[01:21] <ianm_> maybe I'll branch now then we can go ahead with the upgrade
[01:21] <mwhudson> it's probably a good idea to have a back up, yes
[01:21] <mwhudson> (though bzr upgrade makes a backup first)
[01:22] <ianm_> it's up to rev 950.  do balloons fall in the data center when it hits 1000 commits?
[01:22] <ianm_> if not maybe you could set that up when you're in there
[01:23] <mwhudson> heh
[01:23] <mwhudson> ianm_: what format do you want it upgraded to?  packs?
[01:24] <ianm_> mwhudson: recommendation?
[01:25] <ianm_> mwhudson: I know nothing about the formats
[01:25] <mwhudson> ianm_: packs is probably the best performance/compatibility trade-off now
[01:26] <ianm_> mwhudson: can it be changed later?
[01:26] <mwhudson> yes
[01:26] <ianm_> mwhudson: in that case, OK let's go with packs
[01:27] <mwhudson> in progress
[01:27] <ianm_> mwhudson: great.  I've branched it successfully
[01:28] <mwhudson> ianm_: and done
[01:30] <ianm_> mwhudson: thanks!
[01:30] <ianm_> the message is gone
[01:31] <S-i-A> again
[01:31] <S-i-A> hi
[01:31] <ianm_> mwhudson: although it still takes ages to branch!  is that just a property of bzr?
[01:31] <mwhudson> ianm_: are you branching into a repo?
[01:31] <S-i-A> again my files isn't imported from rosseta*!!??
[01:31] <ianm_> mwhudson: just running  bzr branch lp:luz
[01:31] <S-i-A> and the msgfmt -c finde nor errors
[01:32] <S-i-A> why u don't accept that!?
[01:32] <spm> S-i-A: rosetta was closed over the w/e for Jaunty updates. Has been re-enabled about 40ish minutes ago.
[01:33] <spm> S-i-A: wasn't *meant* to be such a long period - oversight. :-(
[01:33] <mwhudson> ianm_: it should be pretty quick
[01:33] <S-i-A> spm: must i upload againd or what ?
[01:33] <ianm_> mwhudson: I'll time it here
[01:33] <spm> S-i-A: I shouldn't think so - the backlog should be pickedup and carried forward. But I may be wrong...
[01:34] <ianm_> mwhudson: I assume this is known "Server is too old for streaming pull, reconnecting.  (Upgrade the server to Bazaar 1.2 to avoid this)"
[01:34] <mwhudson> ianm_: you must be using a fairly old bazaar to be seeing that
[01:35] <ianm_> mwhudson: Bazaar (bzr) 1.3.1
[01:35] <spiv> That counts as fairly old :)
[01:35] <mwhudson> ianm_: newest is 1.10 now
[01:36] <ianm_> is that apt-get installable in 8.04 ?
[01:37] <mwhudson> if you enable the bzr ppa, yes
[01:37] <spiv> (deb http://ppa.launchpad.net/bzr/ubuntu hardy main
[01:37] <spiv> )
[02:17] <ianm_> spiv: thanks!
[02:19] <ianm_> cool, that is many times faster doing a branch
[02:40] <ianm_> 3m32.082s to 1m4.870s
[02:40] <mwhudson> wow
[02:41] <ianm_> mwhudson: ?
[02:41] <mwhudson> ianm_: quite an improvement
[02:42] <mwhudson> the .bzr is about 13 megs, so that comes out at about 200kb/s average speed
[02:42] <mwhudson> which seems decent enough
[05:14] <wgrant> Launchpad, you have failed hard.
[09:02] <BUGabundo_work> hi everyone
[09:02] <BUGabundo_work> any one knows that launchpad bug
[09:03] <BUGabundo_work> where an extra string is attached to the /+filebug/ and it returns a "lost something" page?
[09:03] <BUGabundo_work> its a bug in apport-cli, I think
[09:10] <thekorn> BUGabundo_work, In my experience this is because launchpad is a bit slow, you can solve this problem by refreshing the page a bit later
[09:12]  * BUGabundo_work trying again
[09:12] <BUGabundo_work> yeah
[09:12] <BUGabundo_work> now it worked!
[09:12] <BUGabundo_work> should I file a bug?
[09:13] <thekorn> I think this issue is known, there where some discussions on friday here in this channel about it
[09:14] <BUGabundo_work> okay
[09:14] <BUGabundo_work> I remember seeing an email about it, on lp-users
[09:19] <BjornT> BUGabundo_work: did you first get a 404, and then when you reloaded you got the page you expected (still with the string attached at the end)?
[09:23]  * wgrant blames replication, as he has seen a looooot of lag on staging since it was introduced there.
[09:23] <BUGabundo_work> well the 1st 2 times it failed with a some what 404
[09:24] <BUGabundo_work> then when you told me to refresh, I had to open a new apport-cli bug, and it worked, so I couldn't test the refresh
[09:24] <BUGabundo_work> FYI I'm on edge
[10:57] <MvG> Hi! Anyone here from vcs-imports who can try to get https://code.launchpad.net/~vcs-imports/vpnc/trunk working again, possibly by re-importing it, or should I file a question for Launchpad itself to get this done?
[13:03] <abli> Hi! what are valid 'section' names I can use in a package I want to upload to my PPA?
[13:03] <abli> (I tried 'main' and 'universe' and they were not accepted)
[13:03] <intellectronica> cprov, do you know the answer to that?
[13:04] <cprov> abli: those are components.
[13:04] <cprov> abli: there is a open bug to expose the the valid sections
[13:04] <cprov> abli: go with 'Section: misc' for now
[13:04] <abli> so, how do I find out a valid section?
[13:05] <abli> ok.
[13:05] <cprov> abli: https://bugs.edge.launchpad.net/soyuz/+bug/299034
[13:30] <BUGabundo_work> good afternoon intellectronica
[13:30] <intellectronica> hi BUGabundo_work
[13:31] <intellectronica> i'm just off to get something to eat, but how can i help you today?
[13:31] <BUGabundo_work> oh nothing
[13:31] <BUGabundo_work> just saying hi
[13:31] <abli> I published my package, with got built on all three archs (i386, amd64 and lpia) but my ppa page (https://launchpad.net/~abeld/+archive) still says "Packages [...] 0 binary packages". Shouldn't those 3 binary packages show up there? (after all, it did get built.)
[13:31] <BUGabundo_work> just got from lunch my self
[13:32] <FarInTheWoods> Hi people, I have a little question for you : I'm actually translating english text to french... but when I find a typing error in the english text, what can I do to fix it?
[13:32] <intellectronica> BUGabundo_work: ah cool :)
[13:32] <cprov> abli: binaries take up to 20 minutes to be published.
[13:32] <intellectronica> henninge: can you answer FarInTheWoods?
[13:32] <abli> cprov, even after getting built? ok. Thanks.
[13:32] <cprov> abli: yes.
[13:33] <henninge> FarInTheWoods: Hi!
[13:33] <FarInTheWoods> I just woke up and I'm kinda dizzy, anyone can help me? ^^
[13:33] <FarInTheWoods> Hi :D
[13:33] <abli> FarInTheWoods, I would notify the maintainer of the english text, ie. file a bug
[13:33] <henninge> FarInTheWoods: You will have to contact the maintainer of the project.
[13:33] <FarInTheWoods> Ah, I see
[13:33] <FarInTheWoods> Thanks then
[13:33] <FarInTheWoods> Have a nice day
[13:34] <henninge> FarInTheWoods: The English text is usually found directly in the source code and must be fixed there.
[13:34] <FarInTheWoods> Yeah
[13:34] <henninge> FarInTheWoods: Have a nice day, too.
[13:34] <FarInTheWoods> ;)
[13:34] <henninge> :)
[13:35] <FarInTheWoods> Oh, another thing, when I file the bug... I assign it to the package where there was the typing error, or anywhere else? (just to be sure)
[13:36] <intellectronica> FarInTheWoods: if you can file it on the upstream project, that would probably be more appropriate
[13:38] <FarInTheWoods> An "upstream project" is like ddtp-ubuntu-main, ddtp-ubuntu-universe, ... ?
[13:39] <FarInTheWoods> I'm new to launchpad :p
[13:41] <FarInTheWoods> For exemple
[13:42] <FarInTheWoods> This bug 'https://bugs.launchpad.net/ddtp-ubuntu/+bug/307074' take us to 'https://translations.launchpad.net/ddtp-ubuntu/ubuntu/+pots/ddtp-ubuntu-universe/en_CA/23916/+translate'. In this case, on what project I should assign the bug?
[13:46] <FarInTheWoods> Ok, I found, thanks anyway
[14:31] <splodge> Is there any way to delete a blueprint on launchpad? I can't seem to find a button or a link anywhere.
[14:33] <BUGabundo_work> AFAIK no splodge. you have to mark it as invalid
[14:33] <splodge> Ok thanks
[14:44] <BUGabundo_work> BjornT & wgrant refreshing after a 404 seems to work! it just happened again!
[14:44] <BUGabundo_work> and the attached file of the apport-cli doesn't get lost
[15:08] <Peng_> Is LP going to stackify mirrored branches?
[15:09] <Peng_> Somehow? Magically?
[15:24] <Ursinha> Peng_, I'm not sure, maybe if you define a mirrored branch as focus of development
[15:24] <Ursinha> but I'm just logically guessing, not sure
[15:25] <Ursinha> don't know if it's possible, actually
[15:27] <Peng_> That's where the magic comes in. :)
[15:31] <intellectronica> Peng_: sounds like it would make sense for imported branches. don't know about mirrored ones. i'll try to find an answer from someone who knows better
[16:56] <bac> hi intellectronica
[16:56] <intellectronica> hi bac
[16:57] <bac> intellectronica:  as CHR please ignore email to feedback re: project sachco.  those are due to me testing a script
[16:57] <intellectronica> bac: ok. thanks for letting me know
[17:08] <zwnj> hi there
[17:08] <zwnj> https://translations.edge.launchpad.net/~ubuntu-l10n-fa says "No translations recorded from       Ubuntu Persian Translation Reviewers.".
[17:08] <zwnj> Why the "Translations" tab doesn't show a summary about team-members' translations?
[17:09] <zwnj> that could be very useful...
[17:18] <Peng_> I hope someone will send a confirmation email so everyone will know for sure if they made it onto the new launchpad-users list.
[17:57] <MTecknology> kiko... where are you
[17:59] <cody-somerville> not here
[17:59] <beuno> MTecknology, last time I saw kiko, he had a raging fever
[18:00] <beuno> so I'd expect him to be getting some rest
[18:00] <MTecknology> oh
[18:00] <MTecknology> that explains the delay in my question
[18:00] <MTecknology> I hope he gets better soon
[18:00] <MTecknology> Being sick - never fun
[18:01] <cody-somerville> MTecknology, whats your question?
[18:01] <MTecknology> https://answers.edge.launchpad.net/launchpad/+question/53961
[18:03] <MTecknology> cody-somerville: Sum it up: I'm trying to use those plugins and need my trust root added to launchpad. I figured out how to use the thing, but it doesn't look like the trust root was setup right.
[18:03] <cody-somerville> Rinchen, ^^
[18:07] <MTecknology> cody-somerville: Rinchen: Stuart Metcalfe said "Your site's
[18:07] <MTecknology> trust root should be shown at the top of the page when you attempt to
[18:07] <MTecknology> log in to launchpad."
[18:07] <MTecknology> When I try to log in I see "SD Loco RP"
[18:08] <MTecknology> Sorry for the line breaks, I'm not sure why tbird is doing that on my emails.
[18:13] <MTecknology> cody-somerville: so, is somebody going to get to it? It seems like every time somebody expresses interest they run off. Apparently my question makes people sick too.
[18:14] <MTecknology> I gotta run, I'm gonna try to sell back some books of mine - ttyal
[18:17] <Rinchen> hi
[18:23] <CarlFK> https://edge.launchpad.net/ubuntu/+source/landscape-client    ﻿lp  >  Ubuntu > “landscape-client” package 
[18:23] <CarlFK> links to: https://edge.launchpad.net/ubuntu/+source
[18:24] <CarlFK> shouldn't it go to something about landsacpe-client?
[18:24] <CarlFK> I am trying to find a description of what landscape is, and failing... not sure whos problem that is
[18:25] <Nafallo> http://www.canonical.com/projects/landscape
[18:25] <CarlFK> https://edge.launchpad.net/landscape  too :)
[18:27] <CarlFK> shouldn't there be a link from ﻿https://edge.launchpad.net/ubuntu/+source ?
[19:24] <MTecknology> Rinchen: thanks :)
[19:25] <MTecknology> Rinchen: Go figure I'd be the one to find a bug in something :P - I tend to break things like that.
[19:25] <MTecknology> Thanks for fixing the issue in it so fast. :D
[20:05] <Hobbsee> kiko: thanks :)
[20:07] <kiko> Hobbsee, ah, glad you liked it. it was my last one
[20:07] <Hobbsee> kiko: :)
[20:07] <Hobbsee> kiko: after wondering "why me?", yes
[20:08] <beuno> kiko!
[20:08]  * Hobbsee waves to beuno
[20:08] <beuno> hey hey Hobbsee
[20:08] <beuno> how's it going?
[20:08] <Hobbsee> beuno: pretty good.  Got home eventually :)
[20:09] <kiko> wgrant, mail me your address so I can send you one, we ran out of Ls before I found you
[20:09] <beuno> Hobbsee, I'm glad you did. When did you get there?
[20:09] <Hobbsee> beuno: ~20 hours ago?
[20:09] <Hobbsee> beuno: we only had a 10pm SF time flight, though
[20:10] <Hobbsee> had an interesting time trying to get there - a fair bit of it on foot.
[20:10] <Rinchen> MTecknology, did it work? and you're welcome
[20:11] <beuno> Hobbsee, welcome back to IRC then  :p
[20:13] <Hobbsee> beuno: :P
[20:13] <Rinchen> MTecknology, unping, I see the reply in the ticket. Thanks! I'll get the docs updated
[20:13] <Hobbsee> beuno: i was going to leave it, but forgot
[20:13] <beuno> Hobbsee, this channel would be very quiet if you did  ;)
[20:14] <Hobbsee> beuno: oh really now?  That seems like an interesting test.
[20:14] <Hobbsee> artigas needs a poke too.  wonder where infinity is
[20:59] <_Groo_> hi/all
[20:59] <_Groo_> any lauchpad devs around?
[21:00] <beuno> _Groo_, all kinds of them
[21:00] <beuno> what can we help you with?
[21:00] <_Groo_> hi beuno
[21:00] <_Groo_> im assisting the kubuntu devs, and im in the process of packaging the new koffice2 beta4
[21:01] <_Groo_> unfortunatelly it appears that the ABS cant use universe packages, is that true?
[21:01] <kiko> ABS?
[21:01] <beuno> ABS?
[21:01] <kiko> isn't that braking technology
[21:01] <_Groo_> the automated build system
[21:01] <_Groo_> the PPA builder :P
[21:02] <_Groo_> im a getdeb dev also, and thats how we call the builder :D
[21:02] <kiko> _Groo_, do you mean our PPA build system or something else?
[21:02] <_Groo_> yeah, the PPA build system.. aparently he cant use universe packages, so im having a hard time compiling the koffice package
[21:02] <kiko> you absolutely can use universe packages
[21:03] <kiko> that's just plain 100% untrue. :)
[21:03] <kiko> next question!!
[21:03] <_Groo_> kiko: so why is the ppa complaining about not found libs which ARE in universe? i already activated it to use backport
[21:04] <_Groo_> can you guys check it out?
[21:04] <kiko> _Groo_, would have to see your build log to answer that.
[21:04] <_Groo_> sure:
[21:04] <kiko> but your build log will tell you
[21:04] <_Groo_> https://edge.launchpad.net/~paulo-miguel-dias
[21:05] <_Groo_> kiko: the build logs just tell me he cant find/use the packages..
[21:05] <kiko> _Groo_, o log do build em si, não o link do seu PPA
[21:05] <_Groo_> kiko: brasieiro ou portugues?
[21:06] <_Groo_> kiko: so um seg
[21:06] <kiko> sou brasileiro
[21:07] <_Groo_> https://edge.launchpad.net/~paulo-miguel-dias/+archive/+build/811078/+files/buildlog_ubuntu-intrepid-i386.koffice2_1.9.98.3-1ubuntu4~padoka3_FAILEDTOBUILD.txt.gz
[21:12] <Hobbsee> hrm.  thatshould be there
[21:12] <_Groo_> kiko: ? viste?
[21:13] <kiko> _Groo_, Hobbsee: there's something wrong with the dependencies being set for that archive. hang on.
[21:13] <kiko> Hobbsee, note that it only requests main packages
[21:13] <kiko> cprov, you still around?
[21:13] <Hobbsee> kiko: good point
[21:14] <Hobbsee> how odd.  they used to work
[21:14] <kiko> padoca. me amarro nesse nome
[21:15] <_Groo_> kiko: padoca.wordpress.com :)
[21:16] <kiko> yeah, something's broken.
[21:16] <kiko> I'll call cprov, wanted to call him wanyway
[21:16] <_Groo_> kiko: something in the ppa or with my package?
[21:16] <kiko> with the PPA dependency config, I want to know how bad this is
[21:17] <_Groo_> kiko: nice, so im not crazy
[21:17] <Hobbsee> kiko: extremely, i'd expect.  I'm surprised that this is the first lot of screaming, so it must be fairly new
[21:17] <kiko> Hobbsee, that's why I think it's not so bad
[21:17] <Hobbsee> kiko: unless i'ts this particular buildd?
[21:17] <kiko> nothing's changed for the past weeks
[21:17] <wgrant> kiko: Ah, thanks, I had wondered about that.
[21:18] <kiko> Hobbsee, no, it looks like we're telling it lies
[21:18]  * wgrant wonders if his mail is unbroken yet.
[21:18]  * Hobbsee borks wgrant's entire system
[21:18] <Hobbsee> kiko: ah
[21:18] <wgrant> kiko: Jaunty's doing quite a good job itself.
[21:18] <wgrant> Er, Hobbsee^^
[21:19] <Hobbsee> hah
[21:19] <_Groo_> kiko: can you fix the build system without me having to upload the entire beast again?
[21:21] <kiko> heh
[21:21] <kiko> maybe. let's see
[21:21] <_Groo_> kiko: :)
[21:26] <_Groo_> kiko: ?
[21:33] <kiko> _Groo_, Hobbsee: so interesting problem (but not a new one)
[21:34] <kiko> the thing is that this package is actually in main, currently
[21:34] <kiko> so because the ogre model is being enforced, it doesn't ask for universe dependencies
[21:34] <Hobbsee> ppa obliterated ogre model long ago, though
[21:34] <kiko> it actually didn't
[21:34] <Hobbsee> it shouldn't be being enforced.
[21:34] <kiko> it's just that you usually don't notice it
[21:34] <Hobbsee> errr.....
[21:35] <_Groo_> kiko: so how can i build this damn pakcage?
[21:35]  * Hobbsee is fairly sure that that's *wrong*
[21:35] <Hobbsee> or if it's not, the changelogs for launchpad were wrong
[21:36] <cprov> _Groo_: let me adjust your dependencies to override ogre-model (the way it should be for backports)
[21:36] <kiko> _Groo_, the easy way is to get cprov to hack in a dependency for your PPA, but I had a quick chat with him about the ogre model and PPAs and I kinda feel like Hobbsee -- that the ogre model does more harm than help in PPAs..
[21:37] <cprov> _Groo_: what's lp-name ?
[21:37] <_Groo_> cprov: paulo.miguel.dias
[21:37] <_Groo_> cprov: thanks btw :)
[21:37] <_Groo_> where can i get more info about ogre model? and ppa building in general? the help is not very helpfull :D
[21:38] <kiko> the help is generally pretty complete unless you run into corner cases :)
[21:38] <_Groo_> kiko: hmm ok
[21:39] <_Groo_> kiko: and this is one of those corner cases :P
[21:39] <LarstiQ> ogres, hmm
[21:40] <_Groo_> kiko: is it fixed now? can i try rebuild the package?
[21:40] <cprov> _Groo_: that's not your lp name :-/
[21:40]  * kiko gives _Groo_ 5 ounces of patience
[21:41] <_Groo_> https://edge.launchpad.net/~paulo-miguel-dias
[21:41] <_Groo_> kiko: :)
[21:41] <_Groo_> cprov: sorry cprov :P
[21:41] <cprov> _Groo_: oh, dashes ;)
[21:42] <_Groo_> cprov: yeah, sorry :(
[21:43] <_Groo_> so can you guys explain to me exactly what happend to my ppa account?
[21:43] <_Groo_> since koffice-kde4 exists it wasnt using universe, thats it?
[21:44] <kiko> it is in main in ubuntu proper
[21:44] <cprov> _Groo_: ppa builders are following the ogre-model for the component where koffice is published in the ubuntu primary archive (main)
[21:45] <Hobbsee> cprov: why, and when was this change made?
[21:45] <_Groo_> cprov: whats the ogre-model? besides being green and full of layers
[21:46] <cprov> _Groo_: source published in main and only build-dep on other packages in main, restricted -> main + restricted, universe -> main + universe, ..
[21:46] <Hobbsee> _Groo_: main can only build against main, basically
[21:46] <cprov> Hobbsee: this change was made when we enabled you to include -backports  or -proposed in PPAs.
[21:47] <_Groo_> cprov: so i would have to rename the package koffice2-kde4 for ex? that would build against universe?
[21:47] <Hobbsee> cprov: where was that decision published?
[21:47] <Hobbsee> (and when was it made?)
[21:48] <kiko> cprov, how surprising, I dind't know that either. how long ago was that?
[21:49] <_Groo_> there is this little technoloy called blogging that does wonders for this kind of info...
[21:49] <cprov> https://bugs.edge.launchpad.net/soyuz/+bug/249860, https://bugs.edge.launchpad.net/soyuz/+bug/276024
[21:49] <wgrant> cprov: That was done to remove the security special-casing?
[21:49] <Hobbsee> _Groo_: launchpad used to do comprehensive user-facing changelogs.  Then it stopped
[21:50] <wgrant> Maybe you can give us back components and let us do PPA overrides now...
[21:52] <cprov> wgrant: getting there, the -backports case is special, it's the only case we want to explicitly override ogre-model.
[21:52] <wgrant> cprov: In primary, yes. But in PPAs it is different...
[21:52] <cprov> _Groo_: can you retry your build, please
[21:52] <wgrant> And why is IArchive.syncSource restricted to launchpad.Edit? I hope that was just a quick fix for the bug.
[21:52] <_Groo_> cprov: ok, rebuilding
[21:53] <cprov> wgrant: PPAs only have main, or do you mean ppas build-deps from primary ?
[21:53] <Hobbsee> cprov: and why do these changes require the ogre model existing again for ppas?
[21:54] <cprov> wgrant: it was, I have a branch with the proper fix
[21:54] <wgrant> cprov: Wasn't the problem here that it's following ogre-model with the Ubuntu overrides in PPAs?
[21:54] <wgrant> Note that I haven't read the whole conversation, and am still asleep.
[21:54] <Hobbsee> wgrant: yes, but this is now a feature, not a bug.
[21:54] <wgrant> cprov: With a fix for the other permissions bug too? I can hope...
[21:55] <cprov> wgrant: yes, everything under control
[21:55] <wgrant> Good, good.
[21:56]  * wgrant is also a bit unsure that 'default' is the best name for the initial PPA, which is all that most people will have.
[21:56] <_Groo_> i would love to see a better search for packages in ppas... like package.ubuntu but for ppas
[21:56] <Hobbsee> _Groo_: i thought there was one
[21:56] <cprov> _Groo_: has it already started to build ?
[21:56] <oojah> Hobbsee: I think that useful changelogs are a key feature of open source software.
[21:57] <wgrant> oojah: It's not open source, yet...
[21:57] <Hobbsee> oojah: launchpad isn't open sourced.  But yes, i'd agree (and do not work for the company)
[21:57] <oojah> Yeah yeah, you understand the point though.
[21:57] <oojah> I wasn't trying to dig about that.
[21:58] <_Groo_> cprov: started 4 min ago.. still building.. it it passes the dependency fase it will take a while to finish :D
[21:59] <_Groo_> Hobbsee: wheres that search feature?
[21:59] <cprov> _Groo_: and that means *issue fixed*
[21:59] <wgrant> _Groo_: https://launchpad.net/ubuntu/+ppas lets you find which PPAs have various packages.
[22:00] <Hobbsee> ah yes, that.
[22:00] <_Groo_> wgrant: niiiiiiiice :)
[22:00] <_Groo_> wgrant: not going to ask where i could find that info :P
[22:02] <_Groo_> cprov: aparently its building.. 8 min now :)
[22:03] <mkanat> Even once launchpad is OSS, you guys still expect it to be centralized, yeah?
[22:03] <mkanat> That is, not something that people would go around installing locally.
[22:05] <_Groo_> mkanat: yeah sure.. wink wink...
[22:06] <_Groo_> mkanat: i dont have ANY use for it locally.. i swear... ahn ahn..
[22:06] <mkanat> lol
[22:06] <oojah> The strength of launchpad for me is the community around it, so I'm not particularly bothered about local installs.
[22:06] <_Groo_> mkanat: so, just open up the source. ill just look at it..
[22:07] <mkanat> Honestly, I suspect nobody would want to go to the hassle of setting it up locally, just from experience with these sorts of things...
[22:07] <_Groo_> oojah: true.. i like launchy but the build system integration is too powerful to just dont use it for a internal lab for ex
[22:07] <mkanat> Also, I highly doubt that it has the kind of installation instrumentation required for normal humans to run it elsewhere.
[22:08]  * wgrant is hoping that that will be a sufficient barrier.
[22:08] <oojah> I wouldn't be surprised if other sites pop up much like there are sourceforge installs - just very few.
[22:08] <der|kunstler> how do I remove milestones ?
[22:08] <_Groo_> wgrant: mkanat: so you are releasing it as open source and praying for no one to use it.. that makes sense
[22:09] <mkanat> _Groo_: I'm not part of the "you".
[22:10] <_Groo_> mkanat: so to speak.. i dont know who is who anyway :D
[22:10] <mkanat> _Groo_: Fair enough. :-)
[22:10] <mkanat> I do, but I figured I'd come and ask the channel instead. :-)
[22:13] <wgrant> I'm not part of the 'you' either.
[22:16] <mkanat> kiko: Is Graham in here or should I email him if I have questions?
[22:16] <kiko> gmb should be here, but he's going to be long gone by now
[22:16] <rockstar> mkanat, it's best to just ask the questions in general.
[22:16] <mkanat> rockstar: These are very gmb-specific questions about how the external-bugtracker access stuff works.
[22:17] <mkanat> rockstar: But I suppose other people might know.
[22:17] <mkanat> kiko: Okay. :-)
[22:17] <rockstar> mkanat, yea, those are pretty gmb specific, but the bugs team could probably help.
[22:18] <mkanat> Basically, I was wondering what Launchpad uses Launchpad.count() for in the Bugzilla plugin.
[22:18] <kiko> wgrant, you know.. I hate default too. but what could we have instead?
[22:27] <wgrant> kiko: I don't know either...
[22:29] <gmb> mkanat: I am around if you want to ask me some questions. I am, however, jetlagged, so no promises about how coherent I'll be...
[22:29] <mkanat> gmb: Hahaha, okay.
[22:29] <mkanat> gmb: What do you use Launchpad.count() for?
[22:30] <mkanat> gmb: I'm working on a requirements document for upstreaming the stuff that's currently in the plugin, and I don't think upstream will want a count() function, so I'm looking for what we can do that would give you what you need equivalently.
[22:32] <gmb> mkanat: At the moment I don't think we use it for anything. I'm not sure that losing it would be all that painful.
[22:32] <mkanat> gmb: Ah, okay.
[22:32] <gmb> s/I don't think// - I just checked :)
[22:32] <mkanat> gmb: What about the limit/offset stuff for get_bugs?
[22:33] <mkanat> gmb: Although actually, that's not that hard.
[22:33] <mkanat> That's something that we can do upstream.
[22:34] <gmb> mkanat: Right. We don't use it at present but once we start syncing whole bug reports I suspect we'll use it quite a bit.
[22:34] <mkanat> Okay.
[22:35] <mkanat> gmb: One of the things may be implementing a "search" function upstream--have you seen any particularly good APIs for searching bugs, in any of the trackers you've interfaced with?
[22:36] <gmb> mkanat: Not really, no. That said, I've not really been look for them.
[22:36] <mkanat> gmb: Okay. It's fine, I think I have some ideas.
[22:38] <gmb> Cool.
[22:42] <mkanat> gmb: You need to be able to link to specific comments in bugs, yeah?
[22:42] <mkanat> gmb: So Bug.comments() has to return sufficient information for you to be able to do that, yeah?
[22:42] <mkanat> (I ask because, unfortunately, calculating that information is the most intensive thing that Bug.comments() has to do. :-( )
[22:44] <MFen> ok! i have my python package for my PPA building.
[22:44] <gmb> mkanat: Right. Basically, we need the bug id and the comment id; everything else we can (and do) work out for ourselves.
[22:45] <mkanat> gmb: But you need the comment number as it is relative on the bug, yeah?
[22:45] <kiko> is that number stable?
[22:45] <mkanat> Not just the global comment id?
[22:45] <mkanat> kiko: Mm, theoretically.
[22:45] <kiko> we don't have stable IDs in our DB
[22:46] <kiko> (launchpad)
[22:46] <mkanat> kiko: It could change.
[22:46] <MFen> so my next question regards this: Version numbers must be unique, even for identical packages that are targetting different Ubuntu distributions. If you want to upload the same package for more than one Ubuntu distribution you should add a suffix of the distribution name to the version number.
[22:46] <mkanat> kiko: The comment id never changes, the comment number possibly could.
[22:46] <mkanat> Particularly in the DST hour. :-(
[22:46] <gmb> mkanat: So, we currently do this:
[22:47] <gmb> 1) Get all comment IDS for the bug
[22:47] <MFen> what's the correct thing to if i want to make identical packages? should there be one entry in the changelog for each distribution per package change? or are we talking about completely forked debian/ directories and changelogs?
[22:47] <gmb> mkanat: 2) Work out what we haven't imported
[22:47] <kiko> MFen, if it's /exactly/ the same source and binaries you can just copy them to other releases
[22:47] <gmb> mkanat: 3) Fetch those that we need
[22:47] <kiko> MFen, if it requires a rebuild, then you need a new source version
[22:47] <gmb> mkanat: So, as long as we can say to Bugzilla "Give me the comments for this bug" we're okay.
[22:48] <mkanat> gmb: Okay. So if the "number" return argument of Launchpad.comments() went away, you'd still be OK?
[22:48] <MFen> kiko: i think i need a new source version; it's linked against a library which conceivably is different between distributions
[22:48] <gmb> mkanat: Yes. We don't use the 'number' parameter at the moment.
[22:48] <kiko> MFen, if it requires a rebuild, yeah
[22:48] <MFen> kiko: so how do i manage that? do i have to make two changelog entries every time i want to publish to my ppa?
[22:48] <mkanat> gmb: Great!
[22:49] <kiko> MFen, well, it depends -- can you not really make a single compile work on both releases?
[22:50] <MFen> kiko: well, suppose hardy has libqdbm14 1.4.13 and intrepid has libqdbm14 1.4.14 .. there's no reasonable way to set that up in one compile is there?
[22:50] <MFen> that's one of the libraries i link against
[22:51] <kiko> MFen, and the binary API is different?
[22:51] <wgrant> If the ABI doesn't change (which it looks like it didn't in this case), you don't need to rebuild.
[22:51] <MFen> i'll be honest, i'm not 100% sure what that means. i think they export almost all of the same symbols?
[22:51] <wgrant> We don't rebuild the whole archive just to open a new release.
[22:52] <mkanat> gmb: If we switched to using Bugzilla's normal login system, with a username and password (instead of the token system), would that work?
[22:52] <wgrant> A new ABI version is required only when old symbols are broken.
[22:52] <wgrant> Introducing new symbols is OK.
[22:52] <MFen> ok
[22:52] <wgrant> If the package name is the same, you don't need to rebuild.
[22:52] <MFen> and that would mean a new package name (libqdbm15) right?
[22:52] <MFen> i see
[22:53] <gmb> mkanat: Hmm... That, I'm unsure about. That means having to maintain per-bugtracker authentication data in Launchpad, which means granting *someone* the permission to update it, which is then open to annoying abuse.
[22:54] <mkanat> gmb: The token-based authentication system would be the most intensive thing to upstream. Well, maybe the second-most-intensive.
[22:54] <gmb> mkanat: Intensive how? In terms of the network traffic?
[22:54] <mkanat> gmb: No, in terms of coding work required. :-)
[22:55] <gmb> Ah.
[22:55] <gmb> :)
[22:55] <MFen> so the solution is: upload one set of sources, at version ~ppa1, and don't worry about the ~distro tag
[22:55] <mkanat> gmb: Because I can't just upstream a Launchpad-specific system. I'd have to make something generic.
[22:55] <gmb> Hmm. True.
[22:56] <gmb> mkanat: Could we use OAuth somehow?
[22:56] <gmb> Oh, wait.
[22:56] <gmb> mkanat: ignore me, that makes no sense; I'm getting the authentication flow backawards.
[22:56] <mkanat> You'd have the same problem, I suspect. :-)
[22:56] <gmb> Yeah.
[22:56] <mkanat> People already have to register their bugtracker, right?
[22:57] <mkanat> You could just allow them to specify a username/pass for login, in whatever administrative screens are in use, there.
[22:57] <gmb> mkanat: True, but all they need to do is give us a URL and a name for the tracker.
[22:57] <mkanat> gmb: Hmm. You could email the maintainer, for Bugzilla, since that information is accessible through config.cgi...
[22:58] <mkanat> That is, when somebody sets that info.
[22:58] <gmb> mkanat: *If* someone sets that info; it's not required.
[22:58] <mkanat> Yeah.
[22:58] <gmb> Moreover, the problem isn't with the initial registration
[22:58] <gmb> But with changing authentication data where necessary.
[22:59] <mkanat> Yea.h
[23:00] <mkanat> We could do something Facebooky, like "give this site access to Bugzilla via your account," or something.
[23:00] <mkanat> And give out a super-long forever-use token.
[23:00] <oojah> Forever is a long time.
[23:00] <gmb> mkanat: We shouldn't be asking for external site passwords. (Nor should FB for that matter).
[23:01] <mkanat> Yeah.
[23:01] <gmb> We certainly shouldn't say "give us your password"
[23:01] <mkanat> gmb: No, no.
[23:01] <mkanat> gmb: It'd be something like OpenID where you get redirected and asked if you want to authorize.
[23:01] <MFen> yeah, all the social network sites do something like "hey, what's your email password? we're going to snoop through your email and bug some of your friends"
[23:01] <mkanat> I meant more like, say, authorizing a desktop app to upload to Flickr.
[23:02] <gmb> mkanat: But then isn't that just OAuth?
[23:02] <mkanat> gmb: Yeah, I think it is. :-)
[23:02] <gmb> :)
[23:08] <oojah> Ok, I'm confused by the multiple distro ppa business. I've been working with ~distro1 as a version name because copying packages didn't seem to work. The +archive/+copy-packages page seems to imply that you can copy a package freely between different distros within the same PPA. If I do "Copy existing binaries" then it seems to work (status is still pending), but if I do "Rebuild the copied sources" hardy->dapper (for ...
[23:08] <oojah> ... example) then I get the error "(same version already has published binaries in the destination archive)". Is this right?
[23:09] <cprov> oojah: yes, you can't rebuild a source within the same archive
[23:09] <cprov> oojah: it would result in a different binary with the same name & version than the one previously built.
[23:10] <oojah> Right, but copying is ok.
[23:10] <oojah> That makes more sense.
[23:10] <oojah> But...
[23:11] <cprov> oojah: copying the existing binaries, yes it's fine.
[23:11] <oojah> Surely that's the same if I do "Rebuild..." into a different PPA?
[23:12] <cprov> oojah: yes, but that's a "different" repository, fine as you wish.
[23:12] <cprov> oojah: we assume they have different audience.
[23:12] <oojah> Fair enough.
[23:13] <oojah> Personally I'd take the different distros as being different repositories, but I can see it your way as well :)
[23:14] <wgrant> That's not how Debian archives work (it's how they used to work, but that was really inefficient).
[23:16] <oojah> Right, gotcha. That does make sense. I can get away with just copying, so my life is easier anyway.
[23:16]  * wgrant wonders why PARTNER is a special archive type, and not just a PPA at a different URL.
[23:17] <wgrant> Especially now yu have signed PPAs and NMAF doesn't suck.
[23:19] <_Groo_> wgrant: signed ppas? oO? where? oo Oo oO -.-
[23:20] <wgrant> Over there (/me points one day into the future)
[23:20] <_Groo_> wgrant: ah :P
[23:20] <cprov> wgrant: PARTNER is different than PPAs, it has a much more explicit relationship with the primary archive
[23:21] <wgrant> cprov: It lets you upload to the release pocket of a non-development distroseries, it has only one component, it has a different set of uploaders, it shouldn't have bugs polluting our bugtracker....
[23:21] <cprov> wgrant: but, you know, these things can always change if it's for the better. Maybe someday.
[23:22] <cprov> wgrant: but packages are shown in ubuntu/+source and Co
[23:22] <wgrant> cprov: That's a bug.
[23:22] <wgrant> They are not part of Ubuntu.
[23:22] <cprov> wgrant: well, ISVs *think* they are ;)
[23:23] <oojah> wgrant: I was going to say a similar thing about the ppa search url you posted earlier.
[23:23] <wgrant> oojah: Hm?
[23:23] <wgrant> cprov: Pfft.
[23:24] <oojah> https://launchpad.net/ubuntu/+ppas <- these aren't necessarily part of ubuntu
[23:24] <wgrant> No.
[23:24] <wgrant> They're not.
[23:24] <wgrant> But they're labelled as PPAs.
[23:24] <wgrant> "personal" being the critical bit.
[23:25] <Hobbsee> hmmm.  my filtering is'nt working.  darn.
[23:27] <MFen> is this a valid changelog version line?
[23:27] <MFen> ﻿hypy (0.7.0~ppa1) hardy intrepid; urgency=low
[23:27] <Hobbsee> and there's no X-Launchpad-Bug-Duplicate header.  double darn.
[23:27] <wgrant> MFen: No.
[23:28] <MFen> (particularly the distributions).  the policy manual says those distributions are space-separated, but vim didn't like it
[23:28] <wgrant> I thought they were comma-separated, but they haven't been used since before my time.
[23:28] <oojah> The reason I didn't say anything before was because I figured that in the hypothetical future where launchpad hosts distros that are not related to ubuntu then you'd want to be able to split out the ppas per ubuntu/madeup-ix.
[23:28] <wgrant> Since everybody moved to using package pools many years ago, that syntax doesn't work properly any more.
[23:28] <MFen> how do i tell launchpad to build me a package for intrepid then?
[23:29] <wgrant> oojah: Exactly.
[23:29] <MFen> (maybe that's a dput option?)
[23:29] <wgrant> MFen: Put intrepid in that line instead of hardy, or copy the binaries from hardy to intrepid.
[23:29] <oojah> MFen: And that's when you'll need ~ppa1~intrepid1 as a version.
[23:29] <MFen> wait, how do i copy anything? do i have read-write access to the filesystem after i upload to my ppa? i've never done it before
[23:30] <wgrant> MFen: You click the 'Copy packages' button on your PPA.
[23:30] <_Groo_> is there any way to tell ppa to rebuild the package with -nc (not compile)?
[23:31] <_Groo_> in order to only rebuild the packaging and not the code?
[23:31] <wgrant> No, that doesn't make a whole lot of sense, I don't think.
[23:32] <MFen> oojah: are you saying 'copy packages' has an option to give a package a new version or something?
[23:32] <wgrant> It would mean that Launchpad would have to keep around the build trees.
[23:32] <wgrant> MFen: 'Copy packages' lets you copy a source package or binary package to another PPA or series.
[23:32] <_Groo_> wgrant: hmm ok
[23:32] <MFen> that's what i thought, but that doesn't leave any opportunity to change the version to add a ~distro tag
[23:33] <oojah> Right, you don't need to in that case - as long as the dependencies are identical.
[23:33] <wgrant> MFen: Right, if you need to do that you need to reupload.
[23:33] <wgrant> Why do you need to do it?
[23:33] <MFen> i don't, oojah said i did. :-) got it now.
[23:33] <oojah> i.e. what kiko was saying earlier.
[23:35] <oojah> MFen: I meant that if want to *upload* separate versions that need building for the different distros then you'll need a unique version string (which can be achieved by appending ~distro1 for example)
[23:35] <MFen> right. understood
[23:35] <cprov> MFen: the use-case is trivial (but can get more involving in reality) "does your source benefit of new features in newer build-deps versions " ?
[23:36] <MFen> cprov: well conceivably other reasons. "did your dependency split into multiple parts, join, or get renamed in later distro version?"
[23:36] <cprov> MFen: if it doesn't (and your build-deps keep backward compatibility) you can copy binaries from the last supported version (dapper) up to the the newest one jaunty
[23:36] <MFen> iguess you could handle that with a | though
[23:36] <wgrant> We (Ubuntu) don't often rebuild unless the package is broken.
[23:37] <wgrant> We have quite a few packages that haven't been rebuilt since Warty, for example.
[23:37] <MFen> seems like almost every package has a ubuntu1 version on it
[23:37] <wgrant> No.....
[23:37] <wgrant> Most of the archive is untouched.
[23:38] <wgrant> The sources are unchanged from Debian, that is.
[23:39] <MFen> yeah.. i just looked through my dpkg -l and 948 of 1555 have an ubuntu[0-9] in the version
[23:39] <MFen> maybe there's a lot of the package warehouse i'm missing, though
[23:41] <wgrant> Lots of the desktop stuff is modified, yes.
[23:41] <wgrant> But most of universe isn't.
[23:41] <wgrant> We have ~23000 packages.
[23:41] <MFen> right
[23:41] <MFen> the Deep Catalog.
[23:55] <Rocket2DMn> Can an admin please ban this spammer (again) and close the bugs - https://bugs.launchpad.net/~maurizio-live
[23:56] <Hobbsee> may the rollout happen soon...
[23:57] <Rocket2DMn> i dont understand why they cant keep people banned
[23:58] <kiko> because of a bug
[23:58] <Hobbsee> Rocket2DMn: because of a few bugs about reactivations.