[12:21] micahcowan: If you just provide the diff, you'll need to attach a sign-off, too. [12:22] From whom do I get that? And, if it's already been approved upstream (it hasn't, because I haven't tested yet, but it's light changes, fairly trivial)? [12:23] I do have git-core installed, but have only used it for things like fetching latest kernel sources. [12:23] if you wrote the patch, you provide the sign-off [12:24] A gpg signature against the patch, then? [12:24] what do you mean by "it's already been approved upstream (it hasn't, because I haven't tested yet"? [12:25] Well, what I meant, thinking that you meant I needed to get a sign-off/approval from someone else, was, "what about the case where it has been approved upstream?", even though, at this moment, such is not the case. :) [12:25] if it comes from upstream, you either need to attach the sign-off, or you need to explicitly mention it in the changeset commit entry. [12:25] take http://preview.tinyurl.com/3b6nqn for example. [12:26] is there a fast how to to make a .deb from a tar.gz ? [12:26] in that example, the patch comes from upstream, so I mention the author (Takashi) [12:26] leonel: see the Packaging Guide and the Debian New Maintainer's Guide [12:26] crimsun: thanks [12:27] the sign-off is required for any patch touching kernel source (Linus's policy to which we adhere) [12:28] I'm not familiar with that. Alrighty, then, assuming I've just got a vanilla patch, what would be the process I need to follow? [12:28] (a vanilla patch, and git-core :) ) [12:28] first, create a separate branch from master [12:29] I'd run ``git pull'' while in master, first, to make sure you're current [12:29] Ah. Well, I've only ever pulled from upstream. Where do I need to pull from to get Ubuntu's? [12:29] then you can ``git checkout -b your-branch'' === Hobbsee [n=Hobbsee@ubuntu/member/hobbsee] has joined #ubuntu-motu [12:30] ok, I think you'll want to read https://wiki.ubuntu.com/KernelGitGuide , then. [12:31] crimsun, I need to actually clone the repository, then? [12:31] yes. [12:32] hi crimsun [12:33] hi Hobbsee. [12:33] dang, Creative sucks. [12:34] /* Sound Blaster X-Fi Extreme Audio. This does not have an AC97. 53SB079000000 */ /* It is really just a normal SB Live 24bit. */ [12:37] Is it just me, or does dbus fail to purge for others as well? === Q-FUNK [n=q-funk@dsl-hkibras1-ff55c300-121.dhcp.inet.fi] has joined #ubuntu-motu [12:38] crimsun, okay, so once the pull is done, I'll run the checkout -b, make my changes, and then what do I run to commit to my local repo's branch (sorry, I'm git-ignorant)? [12:38] s/pull is done/clone is done/ === Q-FUNK [n=q-funk@dsl-hkibras1-ff55c300-121.dhcp.inet.fi] has joined #ubuntu-motu [12:39] micahcowan: git-update-index [12:39] micahcowan: then, git-commit -e === acm [n=acm@p57bca94c.dip0.t-ipconnect.de] has joined #ubuntu-motu [12:40] micahcowan: then, git-format-patch -o ~ master [12:40] crimsun, is git-update-index the equiv of "svn add", etc? I shouldn't need that, then: just mods of existing files. [12:41] micahcowan: no, -update-index marks modified files for commit. git-commit actually commits. You're thinking of git-add. [12:42] Okay. Guess I'm used to tools that do that in one step (the marking and committing). [12:42] micahcowan: the ~/0001-foo file is what you'll inlineto an email and send to kernel-team at lists dot ubuntu [12:42] inline to ^ [12:42] Which I should possibly join, temporarily? [12:43] that would be wise, as it's moderated. :-) [12:43] Aha. :) === dharrigan [n=dharriga@82-71-62-76.dsl.in-addr.zen.co.uk] has joined #ubuntu-motu [12:45] if your changeset closes an LP bug, then you should use the Bug: # syntax [12:46] e.g., http://preview.tinyurl.com/325zck [12:48] does that actually work now? [12:49] crimsun: at changelog he can uses LP: #number [12:49] launchpad will handle it [12:49] sladen: It's best practice [12:50] I've been doing it for the last year, yet I haven't seen it actually work yet [12:50] sladen: I've not seen it happen automatically. [12:50] Kmos: even for git changesets? We're not referring to debian/changelog entries here. [12:52] ^Bug: [0-9] + has namespace issues [12:52] crimsun: hmm.. sorry [12:53] Last I checked for the commits being merged into Ubuntu git, Bug: # wasn't being parsed for anything special. AFAIK it's simply a reference to a bug. [12:53] they use bug #number [12:53] http://kernel.org/pub/linux/kernel/v2.6/testing/ChangeLog-2.6.22-rc2 [12:53] like we can see here [12:53] crimsun: btw, saw you managed to get the Ubuntu Alsa workarounds into the latest kernel === xopher [n=xopher@unaffiliated/xopher] has joined #ubuntu-motu [12:55] Kmos, LP automaticall moves to Fix Released if it sees the bug # in the changelog? [12:55] micahcowan: It will (but with LP: #123456 instead) soon. [12:56] Sweet. [12:56] nice [12:56] The Ubuntu side of things has been implemented for months. [12:57] What's the procedure for moving things to multiverse? [12:57] Fujitsu: Things previously in universe, or new things? === vorian [n=grrr@ubuntu/member/Vorian] has joined #ubuntu-motu [12:57] It's currently in universe. [12:58] I presume you file a bug and subscribe ubuntu-archive. [12:58] I don't know then. Perhaps ubuntu-archive? [12:58] (ion3 is heading over there shortly) [12:58] yes. Simply ask for a demotion, and include the rationale. [12:58] Thanks. [12:58] I love people being over-protective of their trademarks. [12:59] which for? [01:00] ion3 upstream has said that nothing is allowed to be called ion3 unless it has no patches, and is the latest upstream version. Debian has complied (and so moved it to non-free). [01:01] I say some bug flames about that [01:01] *saw [01:02] brillian [01:02] t [01:02] anybody know if the backports policy is still that packages have to build without modification? [01:02] crimsun, should I wrap lines on my commit comment, or does it matter? === finalbeta [n=gggggggg@d54C6865D.access.telenet.be] has joined #ubuntu-motu === rrittenhouse [n=tad@unaffiliated/rrittenhouse] has joined #ubuntu-motu [01:05] nm, I see that it becomes the literal Subject of the mail. [01:09] Aaaaaargh, my universe bugmail folder is sort of a bit completely flooded. === persia [n=persia@ubuntu/member/persia] has left #ubuntu-motu [] [01:10] haha [01:12] Lots and lots of apport-retracings. [01:12] easy to filter, then [01:12] How? === persia [n=persia@ubuntu/member/persia] has joined #ubuntu-motu [01:13] depends on what you use for email [01:13] but search for teh email address, or teh [apport] in the subject would be my suggestoin [01:15] Unfortunately, they all come from pitti now, rather than a separate account. [01:15] crimsun, what should I do if I need to redo the commit message? [01:15] Fujitsu: ahhh [01:16] Fujitsu: then i'd filter via [apport] [01:16] or "needs-*-retrace" in the body [01:16] i think i filter by the latter [01:32] I renamed the source package. How could I merge the review of the old source package (libtom0) with the new source package (libtom)? === saispo [n=saispo@ryu.zarb.org] has joined #ubuntu-motu === bashelier [n=bashelie@gov91-1-82-234-91-6.fbx.proxad.net] has joined #ubuntu-motu [02:09] geser: the fix for the libdts bug has just been committed (thanks bashelier) [02:10] pgquiles: which review! [02:10] s/!/?/ [02:11] Hobbsee: http://revu.tauware.de/details.py?upid=5189 [02:11] pgquiles: you cant [02:12] pgquiles: upload the new source package, adn i'll archive that one [02:12] Hobbsee: thank you [02:12] Hobbsee: already uploaded: http://revu.tauware.de/details.py?upid=5208 [02:12] cool [02:13] every point in the review is fixed now except for that "not sure that we need libc6-dev and gcc build-dependency (even versionned)" which I'm not sure what to do with === bashelier [n=bashelie@gov91-1-82-234-91-6.fbx.proxad.net] has joined #ubuntu-motu [02:14] pgquiles: does it build without those two? [02:14] Hobbsee: no, that's why I don't understand what the reviewer meant [02:14] well, aren't libc6-dev and gcc build essential [02:15] They are. [02:15] pgquiles: build essential packages are considered a given when considering dependencies [02:15] LaserJock: oh, I didn't know [02:15] so you don't have to explictly depend on them === luisbg [n=d33p@87.217.145.175] has joined #ubuntu-motu [02:15] We have nothing less than those versions, so they're not necessary. === acm_ [n=acm@p57BC8F6C.dip0.t-ipconnect.de] has joined #ubuntu-motu === dylan_thomas [n=dylan@201.11.40.9] has joined #ubuntu-motu [02:27] hmm [02:30] correct me if I'm wrong please [02:31] a kernel package build requires the abifile from the previous kernel. Where can I find that? [02:32] I need a package from universe but I need the newest package, and that package won't make to universe and that's fine, but I need to install that newest package. IF I do not enable universe and install that newer package it should not break any thing right ? [02:34] leonel: well, depending on the package, you should be fine with having universe enabled [02:35] LaserJock: let me be more specific I need the newest clamav on Dapper and the newest clamav on dapper can break many things If I get clamav from feisty and install it on Dapper backported of course but I have nothing else from universe installed on dapper nothing should get break right ? [02:36] let me add puctuations .. [02:37] you may have trouble dist upgrading [02:37] LaserJock: let me be more specific. I need the newest clamav on Dapper, and the newest clamav on dapper can break many things on Dapper if I have universe enabled or packages from universe installed that requires Dapper's clamav. If I get clamav from feisty and install it on Dapper backported of course, but I have nothing else from universe installed on dapper nothing should get break right ? [02:37] but it wont break while you're on dapper, no, due to the lack of updates [02:37] Hobbsee: right [02:37] isn't clamav being updated? [02:37] didn't saw that [02:37] I thought we were working on a policy for that [02:37] LaserJock: i didnt think the entire new version of it? [02:38] yes [02:38] keep always the newest version [02:38] not patched o [02:38] or [02:38] I need the newest [02:38] It may be being upgraded. [02:38] I thought we were making it an exception to the "new new upstream versions" policy of SRUs [02:38] But it's a very difficult thing to do. [02:38] keescook would know what's up [02:39] LaserJock: ScottK told me something about that [02:39] ah [02:39] Hey all. [02:39] but there are other packages I need to be the newest [02:40] and Hobbsee hit the nail [02:40] dist-upgrade could not work [02:40] dist-upgrade probably would work. [02:40] and probably don't :) [02:41] let's work that new policy of SRUs .. [02:41] MOTUS thank you, always open to answer you ROCK ! === Ppjet6 [n=ppjet@81.56.130.254] has joined #ubuntu-motu === persia [n=persia@ubuntu/member/persia] has left #ubuntu-motu [] === tritium [n=tritium@ubuntu/member/tritium] has joined #ubuntu-motu [02:59] tritium! === zul_ [n=chuck@CPE0006258ec6c1-CM000a73655d0e.cpe.net.cable.rogers.com] has joined #ubuntu-motu [03:03] Fujitsu: who's got the latest and greates mdt? [03:04] I think I merged in some stuff from you [03:04] LaserJock: There's some Debian removals stuff in my branch as of about a month ago. [03:04] LaserJock: we can reject stuff from linuxmint, cant we? [03:04] https://bugs.launchpad.net/ubuntu/+source/hal/+bug/115696 [03:04] Launchpad bug 115696 in hal "LinuxMint 3.0 beta2 hardware information crashed onloading" [Undecided,Unconfirmed] [03:05] Hobbsee: if it's a real Ubuntu bug I think we should take a stab at it [03:05] Kill it, Hobbsee. [03:05] LaserJock: cant really tell what hte bug even is [03:05] if it's a display resolution issue, or what [03:06] "Non of the *buntu 7.04 will provide better than 800x600 graphics on this system." [03:06] or the crash [03:06] that implies at least that the reporter was having issues on more than just Linux Mint [03:06] exactly [03:06] which is why i asked [03:06] I'd ask for more clarification maybe and specificly what happened on *buntu [03:07] I really don't know how much Linux Mint changes things like that [03:07] LaserJock: Can you do something about plotdrop? Once that's done (and the various syncs are processed) we have a fully up-to-date science. [03:07] yeah [03:08] I'll work on it this weekend perhaps [03:08] Thanks. [03:09] Looking at my MDT branch, it has various improvements that you might want (http://people.ubuntu.org.au/~fujitsu/multidistrotools) [03:09] Hey Fujitsu, LaserJock, Hobbsee. [03:09] azeem is on vacation till the 23rd so I don't have a DD to upload for me right now [03:09] hi TheMuso [03:09] but I'll try to get it fixed up [03:10] The removals feature is a little, well experimental, particularly when packages have been in experimental. [03:10] ok, looks like I've already go your changes [03:11] I got packages added to ~ubuntu-tex bug contacts today [03:11] and had a talk with Norbert [03:12] Ah, good. [03:12] hmm ... how does one remove a corrupt .orig.tar.gz file from /incoming on REVU? [03:12] one asks a REVU admin to remove it ;-) [03:12] could one such admin please do so? :^) [03:13] basically: remove incoming/erc* [03:14] i'm still trying to figure out how to use the REVU system well [03:14] done [03:14] excellent, thanks; i now have a working upload of the erc package there [03:14] the important thing is to dput the _source.changes file [03:15] *nods* [03:15] that looks better :-) === Markus1 [n=thielman@i59F7431D.versanet.de] has joined #ubuntu-motu === Markus1 is now known as MarkusT [03:16] is the next to wait for an automated email to be sent to me? [03:16] s/the next/the next step/ [03:16] you won't get an email [03:16] just wait a few minutes [03:16] I think it's a 5min cron job that updates [03:17] sure enough [03:18] yep, it's there === jwhitlark [n=jwhitlar@h-67-102-70-2.snfccasy.covad.net] has joined #ubuntu-motu [03:22] from this point on, the package has to be manually approved by N number of MOTUs, right? [03:22] s/package/upload/ [03:24] yes, the package gets reviewed === micahcowan [n=micahcow@ubuntu/member/micahcowan] has joined #ubuntu-motu [03:24] when the package is approved by 2 MOTUs then it can be uploaded to Universe [03:25] should i email ubuntu-motu with the link to the upload on REVU, or just paste that link here? [03:28] whatever you'd like :-) [03:28] I would think reviewers are on the motu reviewers mailing list [03:29] I usually find out about new packages from that list. [03:29] hmm [03:29] although we're used to having automatic mail there, but yeah, that might be a good idea === bddebian [n=bdefrees@c-71-224-172-103.hsd1.pa.comcast.net] has joined #ubuntu-motu [03:31] hola senor barry [03:32] Hail bddebian. [03:32] Heya gang [03:32] Hi LaserJock, Fujitsu [03:32] in case somebody is bored and wants to take a look, I have uploaded what should be the 100% correct version of libtomcrypt: http://revu.tauware.de/details.py?upid=5208 [03:32] i'll assume that posts to gmane.linux.ubuntu.motu go to that list [03:32] curses, just had a nice hard lock of the system [03:32] Lovely. [03:33] yeah, I blame the proprietary nvidia drivers [03:33] since it went funny while I was playing a game [03:33] The nvidia drivers are known to do that. [03:33] therefore gmaes shouldnt be played [03:33] +1 Hobbsee. [03:33] (hi) [03:34] hiya [03:36] ah, it was gmane.linux.ubuntu.devel.motu.reviewers that I want, apparently [03:41] hey [03:42] LaserJock! :) [03:43] Heya tritium [03:44] Hi there bddebian [03:49] tritium: how's it going? [03:50] LaserJock: Not bad. You? [03:51] same [03:52] Good. Are you going to Ubucon-Boulder? [03:53] hi tritium === d33p__ [n=d33p@87.217.144.156] has joined #ubuntu-motu [03:53] Hi ajmitch :) [03:54] tritium: doubtful, I just got back from Ubuntu Education and Developer Summits in Sevilla [03:54] Nice! [03:55] it's still a little odd trying to explain to my boss [03:55] ;-) [03:55] Boss? Are you working now? Did you graduate? [03:55] "you do this for *free*?!" [03:55] lol [03:56] I think my excuse to my boss would be that I do it so that my brain doesn't atrophy from doing the job I do during the day ;) [03:56] heh [03:56] my boss is understanding [03:56] but my friends think I'm nuts [03:58] Heh, the ubiquity windows can't be resized to fit a 640x480 screen, so I have to install from the alternate CD on my mythtv box (unless I wantt to disconnect from TV) [03:58] ^ note to the mythbuntu folks [03:58] Fun. [04:00] TV supports 720p, but not until I install the nvidia drivers. [04:00] tritium: got time to be an active motu again? [04:00] ajmitch: I talked to crimsun about that very thing. [04:00] I'm going to do my best, but it's going to be a challenge. [04:00] oh good [04:01] Yeah, we had a nice long discussion. [04:01] we can do with every warm body we can get [04:01] I know. I'm going to figure out a way. === ajmitch wishes this would fsck a bit faster === Fujitsu apologises for being largely inactive lately. [04:02] me too [04:02] tritium: s/boss/advisor/ [04:02] LaserJock: ah, okay. [04:02] Fujitsu: more active than I am [04:03] ajmitch: Still not very active. [04:03] Fujitsu: Join the club :-( === ajmitch should have used reiserfs instead, everyone knows that's fast === Ppjet6 [n=ppjet@lns-bzn-51f-81-56-130-254.adsl.proxad.net] has joined #ubuntu-motu [04:06] tritium: my advisor did tell me to start looking for post-docs, so that's a good sign [04:06] reiserfs... fsck? Sounds fatal. [04:06] racarr demonstrated how great it was :) [04:06] now that I have spammed motu-reviewers with a e-mail requesting someone to review libtomcrypt, I think it's time to sleep. Please find the time to take a look at http://revu.tauware.de/details.py?upid=5210 [04:06] Fujitsu: it was unfortunately a moment of mirth at UDS [04:06] ajmitch: Pardon? [04:07] we were expecting a beryl demo, but got a screenful of reiserfs errors instead from racarr's laptop coming through the projector [04:07] Oh, I see. [04:07] Ah. [04:07] LaserJock: congratulations :) [04:07] LaserJock: the end is in sight, and you're still sane? [04:07] ajmitch: Ouch. [04:08] racarr: you enjoyed it [04:08] It was funny after the fact. Yes. === TheMuso currently usees JFS. === Fujitsu is quite happy with ext3. === ajmitch is waiting for his 450GB ext3 fs to fsck at the moment, just added dir_index [04:08] Plus. I got to ask people if they liked my ReiserFS error message verbosity demo. [04:09] apparently it's possible to "double-comment" on REVU uploads by refreshing the page after making an initial comment -- sorry about that [04:09] I guess thats one thing about ext3. Its well tested. [04:09] ajmitch: THat's quite a large filesystem you have there. I think I've got almost that much disk space around the house. [04:09] mwolson: Unfortunately yes. [04:10] Fujitsu: just a raid array === ogra [n=ogra@ubuntu/member/ogra] has joined #ubuntu-motu [04:21] tritium: well, it's getting there. I have some hope. Not sure about sanity though [04:21] tritium: I started an Ubuntu TeX team, btw [04:21] that might say something about the sanity ;-) [04:22] Fujitsu: remember when I did that svn checkout of debain-tex and it was 22GB? [04:22] LaserJock: oh, nice! I might be interested in that! [04:22] https://launchpad.net/~ubuntu-tex [04:23] I'll check it out! [04:24] we're going from tetex->texlive 2007 in Main [04:26] yay, system is back & finally turned on cpu frequency scaling in the bios [04:27] hopefully it'll run a little cooler at times now [04:30] ah! [04:30] ajmitch: are you good with apache 1.x? === ajmitch wonders why people ask things like "are you good with...?" [04:31] :P [04:31] heh, found this photo: http://she.geek.nz/gallery/view.php?f=/pony.jpg [04:32] or http://she.geek.nz/archives/424-taunting-Penny-day.html [04:33] haha === mwolson contemplates starting an Emacs Lisp team on launchpad [04:34] mwolson: :P === bddebian starts a nano team :_) [04:41] ah crap [04:41] 8226 messages (9 seen) for ajmitch at pop3.maxnet.co.nz (61712151 octets). [04:41] mwolson: why would you do that, Emacs is perfect ;-) [04:41] what happens when you had a broken mail setup & your isp chooses not to enforce mail limits [04:41] heh [04:41] too late! :^) [04:41] https://launchpad.net/~ubuntu-elisp [04:42] I thought there was already a lisp team [04:42] i couldn't find it [04:43] https://launchpad.net/people/?name=lisp&searchfor=teamsonly [04:43] only your team [04:44] yep [04:44] there's a passing mention of a Common Lisp MOTU team on the MOTU page of the wiki, but their page is blank [04:46] ah yeah [04:47] I think that is an old defunct team === Fujitsu recalls the gcl patch-hunt. === LaserJock shudders [04:49] It worked, but took a while. [04:58] LaserJock: There's a new annoyance fix in my mdt branch. patch links now link to the patch, rather than the directory. [05:11] Fujitsu: k [05:13] leonel: I was talking about possible changes to how we might do clamav backports (which is new versions). === ScottK thinks we need to do something, but nothing has been decided. [05:18] anybody been using VirtualBox? [05:18] ScottK: what is the current situation (including problems), and what do you propose? [05:22] One problem is that clamav doesn't shut up when it thinks it's out of date. === man-di_ [n=mkoch@dyndsl-080-228-192-227.ewe-ip-backbone.de] has joined #ubuntu-motu === hsitter [n=me@N925P006.adsl.highway.telekom.at] has joined #ubuntu-motu [05:42] StevenK: yes and for end users that message gives them panic [05:42] even that for clamav I think it's better to keep with the most recent version [05:42] It'd be nice if ClamAV didn't write their software such that it was inappropriate for distributions. [05:43] may be because it's not version 1 yet ? === freeflying [n=freeflyi@ubuntu/member/freeflying] has joined #ubuntu-motu [05:45] leonel: I can't see ClamAV changing their procedures just because the version they happen to release is 1.0 [05:46] you're right [05:47] crimsun: The problem is that the 0.882/4 variants we have in Dapper/Edgy are unmaintainable given our resources in Universe, but 0.90.2 cannot be backported per the regular backports policy because it breaks stuff. [05:47] yes I've tried that and was a no go [05:47] Actually the current 0.90.2-4 from Debian can't even be backported to Feisty (not that it's necessary). [05:48] what I was thinking was to have in producction servers universe disabled [05:48] crimsun: My proposal is to make a 2nd clamav source package [05:48] and install from other repo the clamav and things backported to dapper or keep new clamav on the current ubuntu version [05:49] so if there's no universe enabled no packages would break with the newest clamav [05:49] but that would be for some ubuntu antivirus servers only [05:49] crimsun: It'd be design specifically to be backportable, but because it has a different name (I'm currently thinking clamav-alt) a user has to explicitly install it, not just have backports enabled. [05:50] We could then have a page on the wiki about what was known to break/needed testing and then admins could make informed decisions. [05:50] ScottK: and can That clamav-alt would be updatable with new tarballs instead patching ? [05:51] leonel: No, but as long as we can keep backporting the lastest, it shouldn't matter. [05:51] hmm. Is there any way this work could be done in Debian? Are we dealing with process issues as well? [05:51] I don't think so. [05:51] They don't have so many supported versions. [05:52] like gentoo ... [05:52] ok. So "clamav-alt" will then Conflicts clamav? [05:52] leonel: If you install klamav on your desktop you can do that (it provides the functionality and I've tested it, but it's outside the packaging system). [05:52] Do you plan to ask clamav to be blacklisted from future Ubuntu devel cycle autosyncs? [05:52] crimsun: Conflicts/Provides, yes [05:52] klamav ? [05:53] crimsun: It already has to be merged. === zenrox [i=zenrox@pool-71-120-243-30.spknwa.dsl-w.verizon.net] has joined #ubuntu-motu [05:53] ScottK: ok. So do we plan to retain clamav source? [05:53] crimsun: We'd still do the regular clamav package that would be supported per the current no breakage policy. Alt would be for those who want that latest AV crack. [05:54] crimsun: Not sure I understand the question? [05:54] leonel: KDE GUI front end for clamav == klamav [05:54] I think you answered it in your most recent statement [05:54] OK [05:54] This still needs to get fleshed out of course, but that's the basic idea. [05:55] ScottK: need help to test it ? === ScottK made a 0.90.1 clamav package that works on Dapper, just had to adjust some dependency verions - I think it's doable to have a clamav-alt. [05:56] leonel: Yes, when we have such a package. [05:56] We'll probably make a clamav crack test team or some such. [05:57] ScottK: Ok I'm in to it I need to keep with the latest clamav and would be great to make it available for all users [05:58] crimsun: Comments? [05:59] The alternative is to carefully test all the clamav rdepends (and there are a bunch) and backport them all at the same time. I think that blows the backports policy even worse. [05:59] ScottK: I think it's feasible, but you'll really want to test from Dapper (LTS) forward through Gutsy+1 (LTS). [05:59] Yes. === ScottK has tested a 0.90.X package with Dapper, Edgy, and Feisty and got it working. [06:02] While I'm doing the current clamav merge, I'll see about doing a clamav-alt in parallel. If I get something that seems reasonable, I'll upload it to REVU. [06:03] Note that clamav-alt will have to go through NEW, so it'll be a while even after it's uploaded before it could be made available. [06:08] leonel: Got a few minutes to run a test for me? [06:10] leonel: If you have a Feisty desktop, see Bug #108612 and https://lists.ubuntu.com/archives/ubuntu-motu/2007-May/001646.html and comment on the bug if it works/doesn't for you. [06:10] Launchpad bug 108612 in pythoncad "[apport] pythoncad crashed with ExpatError in parse()" [Medium,Fix committed] https://launchpad.net/bugs/108612 [06:10] Anyone else too... [06:15] Good night all. [06:16] 'night. [06:16] night Scott [06:17] ScottK: I'll testit tomorrow [06:17] got to go too [06:18] good night ! [06:28] hmm, so Hobbsee's got a core-dev nomination [06:29] yes [06:30] And 3 fan club members. [06:30] well, I thought I was supposed to wait until after the TB decided on the "policy" [06:30] but no word from hobbsee yet [06:30] LaserJock: I'd assume so too [06:31] ajmitch: She needs to reply? [06:31] StevenK: afaik it's not just a matter of people being nominated & approved for core-dev [06:31] we've never operated that way [06:32] Is this actually documented anywhere? :-) [06:32] "common sense" [06:32] What's that? [06:32] there's no existing documentation for -core-dev nominations and MC, no. [06:32] it was never suggested to be nominations anyway, afaik [06:33] AFAICT TB remains in charge of -core-dev approvals [06:33] of course [06:33] well, that's part of the issue [06:33] the motu council shouldn't be granted that power [06:33] it seems like the TB (or at least Matt) changed the process on us [06:33] yes [06:34] and it was changed to be applying by email, while getting testimonials from others === LastUser [n=lastuser@189.156.32.214] has joined #ubuntu-motu [06:34] the MC just acts as a secretary & gives an opinion [06:34] I don't think the MC shouldn't approve or not approve -core-dev members, but recommend people to made -core-dev [06:34] it was never suggested that the MC would approve [06:35] it was suggested that the MC pass on its recommendation [06:35] and it's a proposal still === LastUser [n=lastuser@189.156.32.214] has left #ubuntu-motu ["Leaving"] === cables [n=cables@216-15-119-176.c3-0.nwt-ubr2.sbo-nwt.ma.cable.rcn.com] has joined #ubuntu-motu [06:36]