Re: Accepted: ubuntu-vm-builder 0.2 (source)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Soren Hansen wrote: > On Fri, Feb 22, 2008 at 12:35:14AM -, Soren Hansen wrote: >>* New release. > > Sorry, that was a little.. um.. terse :) > > 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? 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. When I saw this earlier, and checked for an appropriate bug, I found nothing. Why? Hobbsee -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.6 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFHviPj7/o1b30rzoURAsktAKCDWEnEm+SE3F+ulDwGVIklEhPqFwCeIiDs fTo32S/wWM/q9yOTMnjx+oE= =uxWb -END PGP 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: Accepted: ubuntu-vm-builder 0.2 (source)
On Fri, Feb 22, 2008 at 12:35:14AM -, Soren Hansen wrote: >* New release. Sorry, that was a little.. um.. terse :) 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. -- 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: Ubuntu QA presents: Hardy platform bug list
> The Ubuntu QA team has assembled a list of bugs that we think should > be fixed for Hardy. These are often long-standing bugs or bugs with > many subscribers, comments or duplicates. They are generally in a > mature triage state and should be ready to work on. We've split the > list into four general categories, desktop, server, platform and > kernel. The platform list is by far the longest (a bit of a > catch-all) so I'll highlight that here on -devel: > > http://people.ubuntu.com/~ogasawara/qa-hardy-list-archive/sort-by-package/platform-buglist.html > > Or simply as a search of the 'qa-hardy-platform' tag in Launchpad: > https://bugs.launchpad.net/ubuntu/+bugs?field.tag=qa-hardy-platform > > I've posted these lists to the individual team mailing lists: > https://bugs.launchpad.net/ubuntu/+bugs?field.tag=qa-hardy-desktop > https://bugs.launchpad.net/ubuntu/+bugs?field.tag=qa-hardy-server > https://bugs.launchpad.net/ubuntu/+bugs?field.tag=qa-hardy-kernel > > Please help us close these out! Could bug #107326 please be included in that to-fix list, please? I'd say is severe enough to deserve it -- Pau Garcia i Quiles http://www.elpauer.org (Due to my workload, I may need 10 days to answer) -- 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
On 22/02/08 07:22, Emmet Hikory wrote: > From a maintenance perspective, it is significantly easier when > there is only one copy of any given source in the archive. While it > may be a little more complicated to download the source providing > linux-restricted-modules-`uname -r` to patch, a full solution needs to > either be integrated with this source, or a result of a breakdown of > this source, rather than the reintroduction of code duplication for > each set of modules, with the attendant support issues related to > which version of the module happens to be installed on a user system, > etc. > [..] > [..] More generally, module-assistant needs a cleanup after many of > the duplicated sources in individual -source packages were removed. I completely understand that we don't want the same source in two places, but I would have thought that linux-restricted-modules depended on madwifi-source (and others), but that appears not to be the case. All I could see was a relationship with NVIDIA and AVM Fritz! hardware. Alternatively, can we kill two birds with one stone, that is, update module-assistant to download linux-restricted-modules-`uname -r `-source and compile the appropriate module(s) from that, or is that idea heading for a world of hurt? -- Onno Benschop Connected via Optus B3 at S31°54'06" - E115°50'39" (Yokine, WA) -- ()/)/)()..ASCII for Onno.. |>>?..EBCDIC for Onno.. --- -. -. --- ..Morse for Onno.. ITmaze - ABN: 56 178 057 063 - ph: 04 1219 - [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
Re: madwifi-source
On 21/02/08 20:28, Matthew Garrett wrote: > The madwifi code is already in linux-restricted-modules, so there's no > benefit in providing a separate source package as well. > 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. Of course it's possible that my understanding of the above is incorrect, in which case I would like to know how users are expected to manage this situation. 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. -- Onno Benschop Connected via Optus B3 at S31°54'06" - E115°50'39" (Yokine, WA) -- ()/)/)()..ASCII for Onno.. |>>?..EBCDIC for Onno.. --- -. -. --- ..Morse for Onno.. ITmaze - ABN: 56 178 057 063 - ph: 04 1219 - [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
Re: madwifi-source
Onno Benschop wrote: > On 21/02/08 20:28, Matthew Garrett wrote: > > The madwifi code is already in linux-restricted-modules, so there's no > > benefit in providing a separate source package as well. > > > 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. From a maintenance perspective, it is significantly easier when there is only one copy of any given source in the archive. While it may be a little more complicated to download the source providing linux-restricted-modules-`uname -r` to patch, a full solution needs to either be integrated with this source, or a result of a breakdown of this source, rather than the reintroduction of code duplication for each set of modules, with the attendant support issues related to which version of the module happens to be installed on a user system, etc. > 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. This is bug #136852 (1). More generally, module-assistant needs a cleanup after many of the duplicated sources in individual -source packages were removed. 1: https://bugs.launchpad.net/ubuntu/+source/module-assistant/+bug/136852 -- Emmet HIKORY -- 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: UNDELETION EXT3 workaround
On Wednesday 20 February 2008 07:16:11 Michael T wrote: > Wouldn't the solution for this just be to add a couple of extra utilities, > like e.g. srm (== saferm)? This provides the functionality without > breaking anything. The utilities could also be aliases. And finally, there is libtrash for all you interactive shell rubbish bin needs. Cheers, Florian -- DI Florian Hackenberger [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
Re: [hardy] How Do You Get Back to Firefox 2?
On Thursday 21 February 2008 13:29, Kenneth Loafman wrote: > I made the mistake of upgrading to Firefox 3 Beta on Hardy. It has many > many problems, but the main one is that you can't launch a URL from > Thunderbird, or elsewhere. You have to copy&paste the URL into the > browser windows. [ Are AOL folks having their revenge? ;-) ] > > Long story short, its too time consuming to 'test' this until this > particular *critical* bug is fixed, so I want to regress Firefox back to > version 2 so I have my clickable URLs that work. > > I think that including the Gutsy repository may be the way, but I'm afraid > it will break something else in the process. Has anyone done this? If > so, could you document how? > > Or is there a Firefox 2 package in Hardy that I'm just not seeing? It's not there now. There's a plan being worked to re-introduce it. Scott K -- 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: [hardy] How Do You Get Back to Firefox 2?
What I just now found was that when I swapped from 'Custom' back to 'Firefox' the links are now being launched. On my system (a Hardy upgraded from Gutsy), /usr/bin/firefox links to firefox-3.0 which links to /usr/lib/firefox-3.0b3/firefox.sh. I'm guessing the upgrade may have done something different than an original install. The path you gave does not exist on my system. ...Ken Matthew Nicholson wrote: > You should be able to launch URL's from any application just fine in > Firefox 3. Check System->Preferences->Preferred Applications, set Web > Browser to Custom, and use '/usr/lib/firefox-3.0b3/firefox "%s" ' for > the command (this is assuming you have the Firefox3 beta from the Hardy > repos, and not a manual install of it.) > > Matt > > On Thu, 2008-02-21 at 12:29 -0600, Kenneth Loafman wrote: >> I made the mistake of upgrading to Firefox 3 Beta on Hardy. It has many >> many problems, but the main one is that you can't launch a URL from >> Thunderbird, or elsewhere. You have to copy&paste the URL into the >> browser windows. [ Are AOL folks having their revenge? ;-) ] >> >> Long story short, its too time consuming to 'test' this until this >> particular *critical* bug is fixed, so I want to regress Firefox back to >> version 2 so I have my clickable URLs that work. >> >> I think that including the Gutsy repository may be the way, but I'm afraid >> it will break something else in the process. Has anyone done this? If >> so, could you document how? >> >> Or is there a Firefox 2 package in Hardy that I'm just not seeing? >> >> ...Thanks, >> ...Ken >> > > -- 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: [hardy] How Do You Get Back to Firefox 2?
You should be able to launch URL's from any application just fine in Firefox 3. Check System->Preferences->Preferred Applications, set Web Browser to Custom, and use '/usr/lib/firefox-3.0b3/firefox "%s" ' for the command (this is assuming you have the Firefox3 beta from the Hardy repos, and not a manual install of it.) Matt On Thu, 2008-02-21 at 12:29 -0600, Kenneth Loafman wrote: > I made the mistake of upgrading to Firefox 3 Beta on Hardy. It has many > many problems, but the main one is that you can't launch a URL from > Thunderbird, or elsewhere. You have to copy&paste the URL into the > browser windows. [ Are AOL folks having their revenge? ;-) ] > > Long story short, its too time consuming to 'test' this until this > particular *critical* bug is fixed, so I want to regress Firefox back to > version 2 so I have my clickable URLs that work. > > I think that including the Gutsy repository may be the way, but I'm afraid > it will break something else in the process. Has anyone done this? If > so, could you document how? > > Or is there a Firefox 2 package in Hardy that I'm just not seeing? > > ...Thanks, > ...Ken > -- 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
[hardy] How Do You Get Back to Firefox 2?
I made the mistake of upgrading to Firefox 3 Beta on Hardy. It has many many problems, but the main one is that you can't launch a URL from Thunderbird, or elsewhere. You have to copy&paste the URL into the browser windows. [ Are AOL folks having their revenge? ;-) ] Long story short, its too time consuming to 'test' this until this particular *critical* bug is fixed, so I want to regress Firefox back to version 2 so I have my clickable URLs that work. I think that including the Gutsy repository may be the way, but I'm afraid it will break something else in the process. Has anyone done this? If so, could you document how? Or is there a Firefox 2 package in Hardy that I'm just not seeing? ...Thanks, ...Ken -- 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
The madwifi code is already in linux-restricted-modules, so there's no benefit in providing a separate source package as well. -- 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
Re: HAL fix for multiple battaries
On Wed, Feb 20, 2008 at 09:19:04AM -0800, Ted Gould wrote: > Yes, but that HAL patch ignores all battery entries in /proc if it finds > one in /sys. Which seems rather risky to me... but I was curious if > that seems logical to those who know the kernel better. Yes, the only way a battery can end up in /proc/acpi is if it's supported by the acpi battery driver, which has now been ported to sysfs. -- 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
