Re: Accepted: ubuntu-vm-builder 0.2 (source)

2008-02-22 Thread Soren Hansen
On Fri, Feb 22, 2008 at 12:22:43PM +1100, Sarah Hobbs wrote:
 This is a bugfix release that fixes a few typos (well, several
 instances of the same typo, really), and fixes a call to qemu-img
 that breaks because I added more sanity checks to qemu-img and this
 particular call was bit lacking in the sanity department.
 Even so, where is the bug?  

Line 892 of ubuntu-vm-builder. Oh, you mean bug *report*?

 As far as i'm aware, it still classes under the new MOTU feature
 freeze process, and so should still have a bug, as it's a bug fix
 release.

Oh, this again.. I continue to fail to see the point of me having to do
additional paperwork just because I chose to use native versioning (so
every upload involves an upstream version bump).  Well, at least it'll
bost my LP karma a bit.

 When I saw this earlier, and checked for an appropriate bug, I found
 nothing.  Why?

Because I was more interested in fixing the bug than doing paperwork.

-- 
Soren Hansen
Virtualisation specialist
Ubuntu Server Team
http://www.ubuntu.com/


signature.asc
Description: Digital signature
-- 
Ubuntu-devel-discuss mailing list
Ubuntu-devel-discuss@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-discuss


Re: madwifi-source

2008-02-22 Thread Matthew Garrett
On Fri, Feb 22, 2008 at 07:11:08AM +0900, Onno Benschop wrote:

 I understand that, however, if you have a machine that has a card that
 is not supported by the linux-restricted-modules, you would use
 module-assistant to create a module to match your kernel.
 
 If you had the madwifi-source package, you could patch it and compile a
 module in such a way that it would continue to be maintainable, rather
 than get the source from madwifi.org, unpack it, make and make install
 it and have unknown files scattered all over your file-system.

Or you could apply the patch against linux-restricted-modules.

 Finally, if the madwifi-source isn't available, then I suspect there's a
 bug in module-assistant, seeing that it still has madwifi as an option.

Yes, that's true.

-- 
Matthew Garrett | [EMAIL PROTECTED]

-- 
Ubuntu-devel-discuss mailing list
Ubuntu-devel-discuss@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-discuss