[00:17] <zul> Adri2000: its being worked on its on my todo lsit
[00:22] <Adri2000> zul: have you uploaded the package to -proposed yet?
[00:23] <zul> Adri2000: yep it got rejected have to see why
[00:23] <zul> bbl
[00:25] <Adri2000> zul: ok
[00:53] <mib_lhfac4> Someone know the correct alternative of "update-manager -d" for kubuntu?
[01:04] <coppro> why doesn't ulimit -c work when I try to increase the core dump size limit?
[01:04] <coppro> I can decrease it fine, but increasing it is a nogo
[01:05] <coppro> a bad case of elision, possibly?
[01:13] <slangasek> coppro: by definition, non-root users aren't allowed to raise ulimits of a session beyond the defined hard limit
[01:13] <coppro> nonono, I can't raise at all
[01:13] <slangasek> well, that I don't know
[01:13] <coppro> ulimit -c 1 is okay, a subsequent call to ulimit -c 0 is okay, but another call to ulimit -c 1 fails
[01:14] <coppro> it's like the opposite of renicing a process as a non-priveleged user
[01:14] <slangasek> ah
[01:15] <slangasek> in that case, you probably want to read the section on ulimit in the bash(1) manpage
[01:15] <slangasek> "If neither -H nor -S is specified, both the soft and hard limits are set."
[01:16] <coppro> oh
[01:16] <coppro> always worked for me in the past :/
[01:17] <slangasek> I'm not sure why :)
[01:19] <coppro> so I should just always use -S?
[01:20] <slangasek> if it's not your intention to set a hard limit, then yes
[01:20] <coppro> ok
[01:20] <coppro> thanks
[07:09] <dholbach> good morning
[07:09]  * slangasek waves to dholbach 
[07:09]  * dholbach gives slangasek a hug
[07:09]  * slangasek grins
[07:26] <\sh> good morning
[07:26] <\sh> motu-release: please review bug #239734 and ack...it's needed badly for launchpadlib
[07:26] <emgent> morning \sh :)
[07:27] <\sh> hey emgent...how's life? :)
[07:28] <emgent> \sh: I preferred to stay on vacation, but we must go back to work :)
[07:29] <\sh> emgent: hehe..at least you had some vacation :)
[07:31] <emgent> \sh: yes, it`s true :)
[08:02] <iulian> Good morning.
[08:02] <dholbach> hiya iulian
[08:03] <bobbo> Hey guys, how many ACKs does an FFE need?
[08:04] <iulian> Hello dholbach
[08:05] <dholbach> bobbo: 2 and it gets set to Confirmed
[08:06] <bobbo> dholbach: ah cool
[08:07] <bobbo> dholbach: for https://bugs.edge.launchpad.net/ubuntu/+source/blobwars/+bug/268678, now I have to ACKs, do I also need to get ACKs from u-u-s before I subscribe the archive admins to sync it?
[08:08] <slangasek> yes, a freeze exception doesn't automatically double as sponsorship
[08:09] <bobbo> slangasek: ok, thanks alot :)
[08:09] <slangasek> so just as you would need a sponsor for any other upload that's been approved for FFe, you should have a MOTU that sponsors your request for a sync
[08:10] <dholbach> bobbo: taking a look at it
[08:14] <dholbach> bobbo: ACKing it - technically this should not have required a FFe - it wasn't a new upstream release, was it?
[08:15] <bobbo> dholbach: no it wasnt, but I asked in here and ScottK said I should get one...
[08:15] <bobbo> dholbach: thanks alot :)
[08:15] <dholbach> hm, weird
[08:15] <dholbach> *shrug*
[08:15] <dholbach> anyway.... it's ACKed now :)
[08:15] <bobbo> thanks :)
[08:16] <slangasek> dholbach: FeatureFreeze is a freeze on features, not just those introduced in new upstream releases, though?
[08:16] <slangasek> (I haven't looked at the particulars here)
[08:17] <dholbach> slangasek: usually the team has examined new upstream releases (which is a bit wonky.... native packages, huge diffs that can be just applied instead of a new upstream version, etc)
[08:19] <slangasek> ok; I guess FreezeExceptionProcess does imply, by omission, that only new upstream versions and new packages need exceptions
[08:21] <dholbach> *nod*
[08:42] <stefanlsd> Is there a way to pull stuff from packages.debian without having to go there and download the 3 files and dpkg-source them?
[08:43] <orly_owl> wget
[08:44] <stefanlsd> orly_owl: yeah, was wondering if there was a better way
[08:44]  * orly_owl shrugs.
[08:44] <joaopinto> sebner, dget -x file.dsc
[08:44] <joaopinto> ops, was stefanlsd
[08:45] <iulian> stefanlsd: Better go to packages.qa.d.o and dget the dsc file as joaopinto said.
[08:49] <stefanlsd> iulian: thanks. that helps
[08:53] <iulian> That's weird. I'm connected via PPP and it doesn't work anything, except ssh'ing. Any idea what could be the issue?
[08:54] <iulian> Also firefox turns automatically to offline mode.
[08:59] <joaopinto> iulian, firefox relies on networkmanager to detect the offline/online status
[08:59] <iulian> Ah
[09:01] <joaopinto> it maybe related to Bug 231540
[09:21] <huats> hello eveyrone
[10:25] <slytherin> geser: I have logged FFE for javassist - bug #268914
[11:15] <ScottK> dholbach: I said an FFe was needed for blobwars because I think the repackaging of the non-free data represents a feature change.
[11:16] <dholbach> ah
[11:16] <wgrant> Does it even run without it?
[11:17] <ScottK> As I read the bug, (and maybe I was wrong) it was split into a data package.
[11:17] <wgrant> Isn't it completely unredistributable and as illegal as it gets?
[11:17]  * ScottK just woke up, so will claim he doesn't recall.
[11:18] <dholbach> wgrant: yes, it runs
[11:18] <persia> Some people claim it's completely undistributable.  Others claim it can be distributed.  I don't know of any ruling that has been issued.
[11:18] <wgrant> Last I heard, the author claimed that data didn't need to be covered by a license.
[11:19] <persia> Yes, that's about the state of things.
[11:19] <wgrant> That is clearly wrong, so can be discounted.
[11:19] <persia> Whether the actual content infringes is a different question
[11:20] <dholbach> ScottK: http://paste.ubuntu.com/45720
[11:20] <dholbach> yes, and some stuff went into the new blobwars-data package
[11:21] <gaspa> hi
[11:21] <dholbach> hi gaspa
[11:21] <dholbach> gaspa: how's the bug jam organisation going?
[11:22] <gaspa> dholbach: lol. :) we still have to start. I'm preparing some slides to present the idea.
[11:22] <dholbach> gaspa: nice... do you use the ones from the Material section on the wiki as a start?
[11:22] <gaspa> dholbach: yeah. of course! :D
[11:22] <dholbach> great
[11:23] <ScottK> dholbach: The particular reason I thought that ought to have an FFe was that it went to New.
[11:23] <dholbach> ScottK: right-o
[11:23] <gaspa> doko: i think i fixed rules.conf in gcj-4.2 ... should control file be regenerated by hand, or souys takes care of it?
[11:23] <gaspa> ( in other terms: debdiff should include also changes to debian/control  or not? )
[11:25] <gaspa> s/souys/soyuz/
[11:53] <\sh> norsetto: replied to bug #239734
[11:54] <norsetto> \sh: well, I still would like to be sure that the other apps are still functional
[11:54] <\sh> norsetto: regarding the svn changes, they will...mostly bugfixes to old features...
[11:55] <norsetto> \sh: what svn changes? you mean the changelog?
[11:55] <\sh> norsetto: regarding the importance -> it's needed for lplib
[11:55] <\sh> norsetto: no...the upstream svn commit messages...
[11:55] <\sh> norsetto: http://code.google.com/p/httplib2/source/list
[11:55] <norsetto> \sh: I understand that
[11:57] <norsetto> \sh: btw, if launchpadlib needs 0.4.0 that should also be reflected in its depends ...
[11:58] <\sh> norsetto: bzr version...which will go into intrepid eventually, too
[11:58] <norsetto> \sh: so, the actual launchpadlib in intrepid doesn't need it
[12:04] <stefanlsd> how does cdbs know in which order to apply diff's ?
[12:05] <stefanlsd> i guess i need to use numbers in front...
[12:07] <ScottK> stefanlsd: It's alpha-numeric order, so that'll work.
[12:07] <stefanlsd> ScottK: thanks.
[12:10] <persia> stefanlsd: Be sure to be consistent in your patch names.  The application order is dependent on the locale in which the package is built.  While this is usually consistent, there are subtle differences sometimes.
[12:11] <stefanlsd> persia: yeah thanks, ive seen the diff in UTF8 and POSIX
[12:15] <\sh> norsetto: launchpadlib is in bzr on 0.2 while in ubuntu is 0.1 so yes...intrepids version now is using still the old httplib2...and the new has to use the new httplib2
[12:16] <norsetto> \sh: ok, then please add this info to the bug report and prepare an FFe for launchpadlib too
[12:17] <\sh> norsetto: FFe for launchpadlib needs to be discussed with the launchpadlib guys :) I'll talk to them...and theinfo that the new rel of launchpadlib needs httplib2 is written in the bug report by leonard
[12:18] <gaspa> someone knows whether changes to autogenerated control files should appear also in debdiff or not??
[12:18] <norsetto> \sh: btw, opensync-plugin-google-calendar is a pretty popular application, so, please check that its not broken by this change
[12:18] <\sh> norsetto: I can't test opensync...:(
[12:19] <\sh> or can I use it with evolution instead of an hotsync device?
[12:19] <norsetto> \sh: somebody ought to
[12:20] <azeem> \sh: or just with the plain file plugin
[12:21] <persia> gaspa: I always include changes in autogenerated control files in debdiffs.  The only thing I exclude is config.sub/configu.guess.
[12:21] <gaspa> that's ok.
[12:22] <gaspa> persia: thanks
[12:47] <RainCT> heya
[13:21] <stefanlsd> do i keep .in files in my debdiffs ?
[13:22] <persia> stefanlsd: If you changed them, typically.
[13:22] <stefanlsd> http://pastebin.ubuntu.com/45763/  is an example.     its a .in file of debian/control  and it was changed by    update-maintainers
[13:23] <stefanlsd> guess i should keep it then :)
[13:23] <persia> stefanlsd: Then you changed it (using a script), so it ought be included.
[13:23] <stefanlsd> persia: k. thanks. makes sense.
[13:27] <stefanlsd> what happened between  dapper and feisty.   the e...    ?
[13:27] <laga> edgy eft
[13:28] <persia> stefanlsd: It's gone out of support (18 months have passed)
[13:28] <stefanlsd> heh. yeah. thanks :)
[13:29] <Arc> hey guys
[13:29] <Arc> just an update, the community and technical councils have resolved that AGPLv3 licensed software is suitable for main/universe
[13:30] <Arc> to the earlier conversations here on that subject
[13:33] <slytherin> Don't we generally rely on Debian Legal team to decide which licenses are Free
[13:34] <Arc> I'm refering to the Ubuntu Community/Technical councils
[13:34] <Arc> and yes, I know that.
[13:36] <persia> slytherin: Not quite.  There are some differences between Ubuntu and Debian.  Most famously, GFDL.
[13:37] <Arc> Ubuntu isn't part of the Debian project, even though many people are shared
[13:37] <slytherin> What I was wondering is why was there such a discussion.
[13:37] <Arc> slytherin: because many MOTU people believed that AGPLv3 licensed packages belong in multiverse
[13:37] <slytherin> hmm
[13:37]  * slytherin plans to read it over weekend. :-)
[13:38] <Arc> the only difference between the GPLv3 and AGPLv3 is section 13.
[13:38] <wgrant> Arc: Where is this discussion, or at least the announcement of the decision?
[13:39] <Arc> wgrant: no idea where such announcements are made.  I was just CC'ed on an email from shuttleworth this morning stating that enough time had passed and enough council members had given +1 that the license is clear
[13:41] <slytherin> persia: I may not be able to attend java meeting. The only update I have is bunch of sync, move to universe and and ffe bugs. Please check MoveToUniverse page for details.
[13:41] <james_w> should we drop apt-listbugs from the archive? It only displays stuff from Debian, so it confuses users.
[13:41] <persia> james_w: Or patch it do be appropriate for our envionment.
[13:42] <james_w> yeah, but that's more work :-)
[13:43] <Hobbsee> ooh, interesting.
[13:43] <Hobbsee> that might be easier to use than reportbug.
[13:43] <james_w> and we don't have versioning information, so it would never be as good
[13:43] <Hobbsee> james_w: i think the argument will be the same as ditching reportbug.
[13:43] <james_w> and you get things like  bug 62720
[13:43] <Hobbsee> although, this doesn't send bugs, so will have even less reason to remove it.
[13:44] <james_w> I ask because of bug 268966
[13:44] <james_w> I can see arguments for wanting to use reportbug on Ubuntu, but not apt-listbugs
[13:44]  * Hobbsee would suggest that users actually read the long description, before installing things.
[13:45] <Hobbsee> a package rename might be an idea, too, just to make it more obvious it's debian.
[13:45] <Hobbsee>  apt-listbugs is a tool which retrieves bug reports from the Debian Bug
[13:45] <Hobbsee>  Tracking System and lists them.
[13:45] <Hobbsee> should make it pretty clear that there's no ubuntu stuff there.
[13:45] <james_w> yeah, that could work
[13:45] <james_w> I'll mail the list to see if there are any objections
[13:46] <Hobbsee> james_w: and re> that bug, i'd suggest explaining that only recently has launchpad grown an API, and it's not stable, so there's very little software out there for it, and probably won't be for some time.
[13:46] <wgrant> And the API requires people to authenticate for even read-only operations.
[13:47] <Hobbsee> yay, launchpad!
[13:47] <james_w> also, apt-listchanges should be patched to retrieve from Ubuntu I imagine
[13:47] <Hobbsee> james_w: when launchpad actually has a stable API, and so doesn't need repeated SRU's every time the lp devs decide to change things, sure.
[13:47] <persia> It used to do that: not pulling from Ubuntu is a new change for hardy, and exceedingly annoying to those of us who *like* to read changelogs.
[13:47] <Hobbsee> afaik, that's not the case yet.
[13:48] <Hobbsee> persia: oh?  were they screenscraping?
[13:48] <persia> fixing apt-listchanges doesn't even need the LP API: LP changelogs are known broken and wrong (there's a new bug been filed every summer since 2006), but changelogs.ubuntu.com is accurate.
[13:48] <persia> Hobbsee: No, just pulling from changelogs.ubuntu.com
[13:49] <Hobbsee> persia: er, are you aware that this discussion is on apt-list*bugs*, not apt-list*changes*?
[13:49] <persia> update-manager can do this today, on a per-package basis, and presents a nice interface, but I like to read them in a terminal.
[13:49] <persia> Hobbsee: I was commenting back to :47 <james_w> also, apt-listchanges ...
[13:49] <Hobbsee> oh, my bad, i misread james_w's latter statement.
[14:07] <\sh> norsetto: tested it with the opensync-plugin-google-calendar and file-plugin...works like a charm...
[14:07] <\sh> norsetto: bug #239734
[14:08] <norsetto> \sh: perfect! thx
[14:08] <RainCT> (to whoever didn't like the "index.py" in REVU's URL, now it's gone :P)
[14:12] <persia> RainCT: Does it still forget which package you're examining when you make a comment?
[14:13] <norsetto> \sh: if you hadn't pointed out, nobody would have read it ;-)
[14:14] <RainCT> persia: yes, but I shall have a look at that soon
[14:14] <\sh> norsetto: damn...I entered an event there (some couple of 12 or 14 HPs servers are delivered today..that's why I wrote that..." and wondered why I didn't remove it...but then it was too late...I just read it again when it was on LP ;)
[14:19] <huats> norsetto: hey
[14:19] <huats> how are you ?
[14:19] <norsetto> huats!
[14:20] <norsetto> huats: fine as a peach, you?
[14:20] <huats> great too
[14:21] <gaspa> peaches are fine?
[14:23] <directhex> princess peach from mario bros is.
[14:23] <directhex> even if she always is in another castle
[14:47] <leleobhz> someone can explain to me the g77 to gfortran transition on ubuntu
[14:47] <leleobhz> ?
[14:47] <leleobhz> ImportError: /usr/lib/atlas/libblas.so.3gf: undefined symbol: _gfortran_st_write_done
[14:48] <RainCT> persia: s/soon/now. Fixed :)
[14:50] <persia> RainCT: Thank you.
[15:02] <bddebian> Heya gang
[15:33] <iulian> Hello bddebian.
[15:35] <bddebian> Hi iulian
[15:41] <gaspa> wgrant: perhaps you could be interested in: http://hattory.no-ip.info/issues/edos/
[15:41] <geser> Hi bddebian
[15:42] <\sh> james_w: hi...are you planing an UVE for launchpadlib 0.2?
[15:42] <bddebian> Heya geser
[16:09] <gaspa> who are the mods of -devel mailing list?
[16:10] <iulian> gaspa: cjwatson iirc.
[16:10] <gaspa> iulian: thanks.
[16:10] <iulian> gaspa: Yes, he is running it.
[16:11] <iulian> gaspa: https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel and scroll down.
[16:11] <gaspa> yep
[16:12] <gaspa> contributors are not allowed to wrote on the list.
[16:14] <iulian> gaspa: Right - "posting moderated for non-developers"
[16:14] <iulian> Do you have to be a MOTU or a core developer in order to post?
[16:15] <gaspa> it seems
[16:19] <jdong> iulian: yes, for ubuntu-devel posting is moderated, -discuss is not
[16:21] <gaspa> perhaps contributors could be admintted to post, though
[16:21]  * gaspa feels selfish... :P
[16:21] <iulian> jdong: Got the idea but if you are a MOTU, you can post, right?
[16:23] <iulian> Ah
[16:32] <ScottK-laptop> iulian: Yes.  MOTU are ubuntu-dev so they can post.  Others are also allowed on a case by case basis.
[16:34] <iulian> ScottK-laptop: Aha, thanks.
[18:19] <ScottK> norsetto: Would you please ack and approve Bug 269057.  This definitely needs to be done and the sooner the better.
[18:20] <ScottK> norsetto: Nevermind.  It's in Main.
[18:20] <norsetto> ScottK: isn't that in main?
[18:20] <ScottK> Sorry.
[18:20] <slytherin> geser: there?
[18:23] <norsetto> slytherin: would you mind adding the info required in https://wiki.ubuntu.com/FreezeExceptionProcess to your FFe?
[18:23] <slytherin> norsetto: I files a bunch of FFE today. Which one are you talking about?
[18:23] <norsetto> slytherin: all
[18:25] <slytherin> norsetto: diffstat and changelog.diff is sufficient right?
[18:26] <norsetto> slytherin: build and install log also, you have them already in any case I expect
[18:27] <slytherin> norsetto: No I don't have them ready. But I plan to have them. I am currently updating my pbuilder.
[18:27] <norsetto> slytherin: no problem, thanks
[18:32] <geser> slytherin: yes, do you need an other ACK? :)
[18:33] <slytherin> geser: two syncs. bug #269074 and bug #269066. Please verify carefully. Hopefully they won't turn into FFE.
[18:34] <geser> norsetto: "Increase the upstream version number without changing the actual tarball to get the package uploaded to main." doesn't need a FFe, right?
[18:36] <norsetto> geser: now I heard them all :-) Doesn't look like it needs an FFe indeed
[18:38] <geser> slytherin: are the changes to cglib2.1 worth syncing?
[18:39] <slytherin> geser: I haven't actually checked that. But we will need that version to claim that package can be moved to universe as it has moved to Debian main
[18:39] <sebner> geser: our problem with r-base is solved ^^
[18:39] <norsetto> sebner: what problem with r-base?
[18:40] <sebner> norsetto: r-base-core-sa to be exactly. Well we were discussing aobut a FFe but archive admins synced the actual version. (I filed an older sync request and dholbach ACKed)
[18:41] <norsetto> sebner: r-base-core-ra you mean?
[18:41] <geser> slytherin: from the change it doesn't look worth syncing, and I hope that we don't need the sync just for the comment that it moved to Debian main. I already try to get it moved to universe, see bug 267816
[18:41] <sebner> norsetto: yep ah, right
[18:42] <slytherin> geser: yes I saw that.
[18:42] <norsetto> sebner: wasn't that about the tmp problem?
[18:42] <slytherin> geser: you are the one to ack. Whatever you feel is right.
[18:43] <sebner> norsetto: yes BUT later debian got a new upstream version and the archive admins synced it ( you know they automatically take the newest version available)
[18:43] <norsetto> sebner: ah yes, hmmm, I don't remember if we do need to rebuild something
[18:44] <geser> slytherin: IMHO it's not really worth syncing, let's try first without it
[18:44] <sebner> norsetto: We'll see but for now it seems to be ok
[18:45] <slytherin> geser: Ok. Anyway, I am working on FFE for javassist which should clear aspectwerkz2 and eventually cglib2.1
[18:49] <norsetto> sebner: r-cran packages are difficult beasts, we have to be carefull with build order wrt r-base
[18:50] <sebner> norsetto: I see :\
[19:18] <Arc> ok to refresh my memory
[19:18] <Arc> we have a PPA setup now on launchpad, and that can work for the next 6 months
[19:20] <Arc> the process we should follow then is to put our package(s) up on REVU, since they cannot be included in Debian yet, and then next April if it's included in Jaunty we can request it be backported to 8.04 LTS?
[19:21] <Arc> is it possible to get a package added to 8.10 universe post-release but before Jaunty?
[19:21] <laga> depends.
[19:22] <laga> if it's deemed important enough
[19:22] <laga> it should be possible to get it into intrepid first and then do a backport
[19:22] <laga> but it'll only be available to those using the intrepid-backports repo
[19:22] <Arc> we're nowhere near ready for packaging for intrepid
[19:22] <Arc> ok.  so our PPA for most people is good enough.
[19:23] <laga> well, most packages don't need big changes for intrepid, not sure about yours
[19:23] <Arc> we've never been packaged for Ubuntu
[19:24] <Arc> our package is a set of Python extension modules
[19:36] <sebner> DktrKranz: \o/
[19:37] <DktrKranz> huhu sebner
[20:44] <CarlFK> what is the policy for .py/c files in a .deb?  as in, they get installed by root, so written with root privs, which won't exist the first time they are run by a user, so the .pyc can't be written to the fs.
[20:46] <CarlFK> ﻿should they be pre-compiled and the .pyc included in the .deb, should the .py be compiled at install time, or should a .pyc never exist?
[20:49] <norsetto> CarlFK: no pyc shall be included in a .deb, they shall be compiled and installed when the .deb is installed. For your future reference: http://www.debian.org/doc/packaging-manuals/python-policy/ and http://wiki.debian.org/DebianPython/NewPolicy
[20:49] <CarlFK> thanks
[21:51] <gdfuego> Hey folks.  I was wondering if someone might be able to answer a question on what is covered under "package maintenance" according to the Ubuntu maintenance and life cycle document
[21:51] <gdfuego> http://www.ubuntu.com/products/whatisubuntu/serveredition/benefits/lifecycle
[21:52] <gdfuego> We have a number of Gutsy desktops at my company, and we were bitten by a rather bad pidgin/xmpp bug before Hardy was released
[21:52] <gdfuego> the bug was never fixed even though hardy was not yet released, and now it never will be
[21:53] <RAOF> gdfuego: Do you have the bug number handy?
[21:53] <gdfuego> The bug in question is 159020.  Pidgin fails to send user passwords to xmpp servers unless "save password" is checked.  You supply a password, and it throws it away
[21:55] <RAOF> gdfuego: That bug ha status "fixed released" in Hardy.
[21:56] <gdfuego> Yes, but we're not running Hardy yet.  The life cycle document states that the 6 month releases are provided "# Regular package maintenance until the next regular update or LTS, whichever comes first".  That seems to imply that this should have been fixed in the several months leading up to Hardy's release
[21:57] <gdfuego> Longer term we need to move to Hardy, but we are going to hit the same type of issue a year into Hardy's life cycle when attention is moved onto the next 6 month or LTS release?
[21:58] <RAOF> For bugs judged sufficiently serious we'd hope to do an SRU to fix it in previous versions, where possible.
[21:58] <RAOF> !sru
[21:58] <norsetto> and that doesn't apply to universe in any case
[21:59] <RAOF> Pidgin isn't in universe, though.
[21:59] <norsetto> ah ok, didn't know you were talking about pidgin (why do you talk about pidgin in ubuntu-motu ;-))
[21:59] <RAOF> And, yes, Universe packages have no guarantees attached, although we certainly want to fix the most egrarious bugs.
[22:00] <gdfuego> Yeah, I was a bit surprised when #ubuntu suggested coming into here
[22:00] <RAOF> It wasn't _bad_ advice, but ubuntu-devel may have been better.
[22:01] <gdfuego> This document was what I was looking for, although it concerns me a little bit
[22:01] <gdfuego> If the bug had been in Hardy rather than Gutsy, its not clear it would have been fixed in that release either
[22:01] <RAOF> Indeed, it may not have been, but is more likely to have been.
[22:02] <RAOF> We _can't_ fix all the bugs in released versions of Ubuntu.  At least, not without introducing regressions/changing behaviour.
[22:03] <RAOF> The SRU process is meant to be a compromise between "a release should work the same way tomorrow as it did today" and "it'd be nice to fix bugs".
[22:03]  * norsetto thinks it'd be nice not to have bugs but he is old school
[22:03] <sebner> norsetto: bugs are overrated :P
[22:03] <gdfuego> Yeah, I'm a big believer in stable releases with minimal changes myself
[22:03] <RAOF> It would be nice not to have bugs, yes :P
[22:04] <gdfuego> The bug in this case is pretty bad, but probably didn't impact too many companies
[22:04] <gdfuego> I just happened to be in the middle of a corporate xmpp rollout at the time, and we didn't want people storing their passwords in their pidgin config
[22:07] <RAOF> The bug was marked as 'low' importance, and no one in the bug presented a rationale why it should be higher; for you it obviously was.
[22:08] <gdfuego> Ok, thanks for the help.  The StableReleaseUpdates document explains a lot
[22:20]  * norsetto is undecided if he should go to bed or ask sebner to fix a bug
[23:15] <hdevalence> where is the correct place to request that a program be added into the APT repositories?
[23:16] <Ampelbein> hdevalence: https://wiki.ubuntu.com/UbuntuDevelopment/NewPackages
[23:16] <RAOF> Launchpad.net
[23:25] <norsetto> night all