Ubuntu QA Tracker: New build notification [20110329]
You are receiving this email because you have been subscribed to the following test case: Ubuntu Studio Alternate i386 [20110329]: http://iso.qa.ubuntu.com/qatracker/info/5218 Install (auto-resize): http://iso.qa.ubuntu.com/qatracker/result/5218/222 Install (entire disk): http://iso.qa.ubuntu.com/qatracker/result/5218/223 Install (entire disk with encryption): http://iso.qa.ubuntu.com/qatracker/result/5218/221 Ubuntu Studio Alternate amd64 [20110329]: http://iso.qa.ubuntu.com/qatracker/info/5217 Install (entire disk with encryption): http://iso.qa.ubuntu.com/qatracker/result/5217/225 Install (entire disk): http://iso.qa.ubuntu.com/qatracker/result/5217/227 Install (auto-resize): http://iso.qa.ubuntu.com/qatracker/result/5217/226 Please report any bugs you identify in Launchpad and report on the success or failure of the test in the tracker: https://launchpad.net/ubuntu/ Please see the testing team wiki pages for for further information: https://wiki.ubuntu.com/Testing For questions about the procedure or to coordinate testing, please join #ubuntu-testing on freenode. Thank you for helping us to test Ubuntu. -- Ubuntu-Studio-devel mailing list Ubuntu-Studio-devel@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-studio-devel
Re: A feature for -lowlatency kernel?
2011/3/25 Alessio Igor Bogani abog...@ubuntu.com: Dear Ubuntu Studio Developers, Yesterday Ailo has reported in IRC channel that the 2.6.39 mainline Linux kernel is going to provide an useful and interesting feature: threaded irqs. Until now that feature was provided by realtime kernels only. It is the piece of code that permit to prioritize hardware interrupts which is very useful thing when you have a firewire/usb device. I think that we should have it for Natty. So I could provide a -lowlatency kernel based on 39 kernel if enough testers will offer theirs help. Sincerely I would want avoid to waste time for make something that no one will use. What do you think? I can't wait to try this kernel/feature with my firewire setup (which, sadly, is still having xruns in -lowlatency on Natty). Kind regards, --Artem -- Ubuntu-Studio-devel mailing list Ubuntu-Studio-devel@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-studio-devel
Ubuntu QA Tracker: New build notification [20110329.1]
You are receiving this email because you have been subscribed to the following test case: Ubuntu Studio Alternate amd64 [20110329.1]: http://iso.qa.ubuntu.com/qatracker/info/5316 Install (auto-resize): http://iso.qa.ubuntu.com/qatracker/result/5316/226 Install (entire disk with encryption): http://iso.qa.ubuntu.com/qatracker/result/5316/225 Install (entire disk): http://iso.qa.ubuntu.com/qatracker/result/5316/227 Ubuntu Studio Alternate i386 [20110329.1]: http://iso.qa.ubuntu.com/qatracker/info/5317 Install (auto-resize): http://iso.qa.ubuntu.com/qatracker/result/5317/222 Install (entire disk with encryption): http://iso.qa.ubuntu.com/qatracker/result/5317/221 Install (entire disk): http://iso.qa.ubuntu.com/qatracker/result/5317/223 Please report any bugs you identify in Launchpad and report on the success or failure of the test in the tracker: https://launchpad.net/ubuntu/ Please see the testing team wiki pages for for further information: https://wiki.ubuntu.com/Testing For questions about the procedure or to coordinate testing, please join #ubuntu-testing on freenode. Thank you for helping us to test Ubuntu. -- Ubuntu-Studio-devel mailing list Ubuntu-Studio-devel@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-studio-devel
Re: Kokito and Ubuntu Studio Website Update
On Mon, Mar 28, 2011 at 5:22 PM, Jorge G. Mare jorge.g.m...@gmail.com wrote: Hey, Jorge, glad to see you're interested in helping! First, I'm sorry I haven't had any website updates for the last few weeks. Real life has swamped me, and I haven't had much time to do any work. I'm hoping to get some time in over the next few days. Jorge, right now the very basic aspects of the theme are in place (you can see it in action here: http://mousike.dyndns.org/ubuntustudio/). I would say that what we need to do next is get the back end and initial content of the site organized, and then we will know precisely what CSS remains to be done. I'll send out a more detailed e-mail about how I think this stuff should be implemented in Drupal (i.e. what modules to use and with what settings, content types, user roles, etc) the next time I get the chance. If you have ideas on these things as well, definitely let us know! -- -Brian David -- Ubuntu-Studio-devel mailing list Ubuntu-Studio-devel@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-studio-devel
Re: Please do not use syncpackage during hard-freeze periods
What kind of problem do you have with accepting packages based on syncpackage? Do you need a bug for see explanation why it should be synced? It is, in file *_source.changes which is uploaded every time on ftp via dput. There is a line called 'Launchpad-Bugs-Fixed' where you can find a bug number which is leading to request of sync. Dnia 2011-03-26, sob o godzinie 10:39 +, Colin Watson pisze: During hard-freeze periods (such as the current beta freeze) all uploads to the queue must have an easily-found rationale (preferably in the changelog or a linked bug) in order to be accepted. syncpackage does not permit this, because all we get in the queue is the changelog written by the Debian maintainer, which doesn't typically explain why the changes matter for the Ubuntu 11.04 beta-1 release. I have rejected three uploads made using syncpackage: aview bbrun papaya If these need to be in the 11.04 beta-1 release, please file sync request bugs using requestsync, and include an appropriate rationale. Thank you, -- Colin Watson [cjwat...@ubuntu.com] -- Pozdrawiam / Kind regards, Artur Rona -- ubuntu-devel mailing list ubuntu-devel@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel
Re: Upstart Cookbook
On Mon, 2011-03-28 at 15:32 -0700, Scott James Remnant wrote: More comments 1.4 - the footnote here is [2], where is [1] ? As of right now, [1] is here: http://upstart.ubuntu.com/cookbook/#id9 The auto numbering seems a bit odd, not sure why [1] is so far down in the doc. 2.2 - the indented blocks aren't indented Fix Released -- Though my fix may not be IE7 friendly (something with margin's and pre in IE7 not working right). 3.1.2 - should be NIH Utility Library (qv. http://launchpad.net/libnih) Fix Released 4.1.1 4.1.2 - worth explaining the real difference between task and service here, perhaps? or later? 4.2 - the footnote here is [7], where are [2] thru [6] ?! :p - you leap into blocking here, which is a very very core upstart concept, without explaining it 4.2.1 - signal events are created with the --no-wait option to emit, there is no --emit option 5.3 - this is basically all completely wrong ... Ouch, I see that now. Ok, I've rewritten this and the task section completely. 5.4 - I wouldn't use the word started here, because it's easily confused with the event and the started event is emitted when a task is running not when it's finished - and your example is wrong Right, rewrote these entirely, including fixing the example to use 'stopped' with the task appropriately. Here is the commit: http://bazaar.launchpad.net/~upstart-documenters/upstart-cookbook/trunk/revision/45 5.6 - one of the things you can do in pre-start is cancel the start! worth mentioning? 5.8 - and the big feature of pre-stop is you can cancel the stop! worth mentioning? Added these reminders. 5.9 seems to run-in with the next paragraph Not sure what this means. Can you elaborate at all? 8.2.3 - worth a | sort in there? 9.15 - start on stopped mydb EXIT_SIGNAL=SEGV ... ;-) 9.39 - really script/exec ? I'd just use exec there 17 - that should read Scott James Remnant (Google) no? This begs the question, what are we trying to convey here? I think we want to say these people, in an official compacity for their respective companies, contributed. What about (Canonical, Google) ? -- ubuntu-devel mailing list ubuntu-devel@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel
Ubuntu Kernel Team Meeting Minutes - 2011-03-29
= Meeting Minutes = [[http://irclogs.ubuntu.com/2011/03/29/%23ubuntu-meeting.txt|IRC Log of the meeting.]] BR [[http://voices.canonical.com/kernelteam|Meeting minutes.]] == Agenda == [[https://wiki.ubuntu.com/KernelTeam/Meeting#Tues, 29 Mar, 2011|20110329 Meeting Agenda]] === Release Metrics === Release Meeting Bugs (6 bugs, 8 Blueprints) Beta 1 Milestoned Bugs (59 across all packages (down 29)) * 4 linux kernel bugs (no change) * 0 linux-ti-omap bugs (no change) * 0 linux-meta-ti-omap bug (no change) Release Targeted Bugs (274 across all packages (up 1)) * 22 linux kernel bugs (up 2) * 0 linux-ti-omap bugs (no change) * 0 linux-meta-ti-omap bug (no change) Milestoned Features * 7 blueprints (Including HWE Blueprints) Maverick Updates Bugs * 60 Linux Bugs (down 13) Lucid Updates Bugs * 94 Linux Bugs (no change) Bugs with Patches Attached:84 (up 1) * [[https://bugs.edge.launchpad.net/ubuntu/+source/linux/+bugs?field.has_patch=on | Bugs with Patches]] * [[http://qa.ubuntu.com/reports/ogasawara/csv-stats/bugs-with-patches/linux/ | Breakdown by status]] === Blueprints: Natty Bug Handling === * I am reviewing the items this week (had planned to do last week, but didn't get to it) to determine what, if any, items need to be postponed or require further discussion at UDS. There are several items that are relatively straightforward and simply need to have the time allotted for them to be completed. I'll plan and implement that schedule for myself also this week. === Status: General Natty === Beta-1 is this Thursday, March 31. Beta-1 will ship with the 2.6.38-7.39 kernel which is based on mainline v2.6.38. Do not expect any further uploads of the kernel until after Beta. In the mean time we've been queueing patches in the master-next branch including rebasing to the most recent 2.6.38.2 stable update. Also keep in mind that Kernel Freeze is April 14, ~2weeks away. After kernel freeze we will transition to our SRU policy when submitting and accepting patches. See: BR [[https://wiki.ubuntu.com/KernelTeam/KernelUpdates]] BR [[https://wiki.ubuntu.com/Kernel/Dev/StablePatchFormat]] BR BR I'd like to also note that Kernel Freeze is also the same date as Beta 2. Any uploads beyond that would likely have to be of the kitten killing nature. === Status: Stable Kernel Team === We are extending the verification phase of this kernel cycle to two weeks in order to resync with master Natty interlock schedule. BR BR Due to a shortage of testing resources and testing required for the upcoming Natty release, there will not be a normal two-week kernel release cadence for the next few weeks. The schedule is as follows: BR BR kernel (maverick, lucid) -) proposed 3/25 verification in progress this week hw cert/qa - 4/1-4/7 kernel (maveric, lucid) -) update 4/7 kernel ( maverick, lucid?)-) proposed 4/22 verification 4/25-4/29 hw cert/qa - 4/29 - 5/5 kernel (maverick, lucid? ) to update 5/5 BR BR * We will complete verification (or revert of patches) by this Friday for the current kernels. * We will have no uploads on the 8th of April, effectively skipping one of the two week cycles that we have been on. * We will upload Maverick and Lucid to -proposed on Friday, April 22 BR BR We still have not found the root cause of a build failure for the hppa architecture for the Hardy linux-backports-modules package. This must be understood and resolved before we can release the Hardy kernel packages, so if it is not resolved by the end of this week we will have to delay the testing phase for Hardy until we understand it. === Security bugfix kernels - Maverick/Lucid/Karmic/Hardy/Dapper === || Package|| Upd/Sec || Proposed || TiP || Verified || |||| || || || || || dapper linux-source-2.6.15 || 2.6.15-57.94 || 2.6.15-57.95 ||0 ||0 || |||| || || || || || hardylinux-restricted-modules-2.6.24 || || 2.6.24.18-29.9 ||0 ||0 || || --- linux-ubuntu-modules-2.6.24 || 2.6.24-28.47 || 2.6.24-29.49 ||0 ||0 || || --- linux-backports-modules-2.6.24|| 2.6.24-28.37 || 2.6.24-29.39 ||0 ||0 || || --- linux-meta|| 2.6.24.28.30 || 2.6.24.29.31 ||0 ||0 || || --- linux || 2.6.24-28.86 || 2.6.24-29.88 ||3 ||3 || |||| || || || || || karmic linux-ec2 || 2.6.31-308.28
Edubuntu Monthly Meeting Reminder
Hi Edubuntu Developers This is a reminder for the Edubuntu monthly meeting, taking place tomorrow, 29 March 2011 at 19:00 UTC in #ubuntu-meeting Agenda is at: https://wiki.ubuntu.com/Edubuntu/Meetings/Agenda We'll have some guests over from the Debian-Edu/Skolelinux community and will be discussing some areas for collaboration. Thanks and have a great day! -Jonathan -- edubuntu-devel mailing list edubuntu-de...@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/edubuntu-devel
Re: Integrating new console colors in D-I (was Re: Call for testing: Aubergine-love for Server folks!)
On Sat, Mar 26, 2011 at 10:21 AM, Colin Watson cjwat...@ubuntu.com wrote: It would have to go on the kernel command line, not in the CD preseed file. The latter is read too late for this. It would probably be better to add new values for the existing FRONTEND_BACKGROUND environment variable (which can also go on the kernel command line) rather than inventing a new preseeded template which would basically just be a synonym for it. Great idea, Colin. I have this now working, with an upload of cdebconf-0.154ubuntu2 to Natty archive. This will not make Beta1, but should absolutely land in Beta2, and will need release-team approval. Note that it will also require a re-spin of debian-installer. I'm tracking this in Bug #730672. There's a debdiff for cdebconf there. As of that upload, any user of the text installer will be able to optionally specify a FRONTEND_BACKGROUND value on the kernel command line. The cdebconf-newt-udeb package provides the following: * dark -- high contrast, accessibility theme * original -- the traditional, legacy newt theme * ubuntu -- the aubergine theme (basically, s/blue/magenta/g) These are installed to: * /etc/newt/palette.dark * /etc/newt/palette.original * /etc/newt/palette.ubuntu By default, there is a symlink installed by cdebconf-newt-udeb in the ISO filesystem: * /etc/newt/palette - /etc/newt/palette.ubuntu At debian-installer/cdebconf initialization of the newt frontend, if a kernel parameter FRONTEND_BACKGROUND=whatever is found, then the symlink at /etc/newt/palette is broken and replaced with a symlink to /etc/newt/palette.whatever. In this way, any derivative of Ubuntu can ship their own palette in a udeb that's included in their ISO build, install that palette at /etc/newt/palette.kubuntu, for example, and append FRONTEND_BACKGROUND=kubuntu to the kernel parameters. If you (or your Ubuntu derivative) just want the legacy behavior, then don't bother shipping your own palette, but simply append FRONTEND_BACKGROUND=original to the kernel parameters. I hope this helps with your calls for reconfigurability! I've enjoyed working with everyone on this ;-) Cheers, -- :-Dustin Dustin Kirkland Ubuntu Server, Core Developer Canonical, LTD -- ubuntu-devel mailing list ubuntu-devel@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel
Re: Integrating new console colors in D-I (was Re: Call for testing: Aubergine-love for Server folks!)
Dustin Kirkland kirkl...@canonical.com wrote: On Sat, Mar 26, 2011 at 10:21 AM, Colin Watson cjwat...@ubuntu.com wrote: It would have to go on the kernel command line, not in the CD preseed file. The latter is read too late for this. It would probably be better to add new values for the existing FRONTEND_BACKGROUND environment variable (which can also go on the kernel command line) rather than inventing a new preseeded template which would basically just be a synonym for it. Great idea, Colin. I have this now working, with an upload of cdebconf-0.154ubuntu2 to Natty archive. This will not make Beta1, but should absolutely land in Beta2, and will need release-team approval. Note that it will also require a re-spin of debian-installer. I'm tracking this in Bug #730672. There's a debdiff for cdebconf there. As of that upload, any user of the text installer will be able to optionally specify a FRONTEND_BACKGROUND value on the kernel command line. The cdebconf-newt-udeb package provides the following: * dark -- high contrast, accessibility theme * original -- the traditional, legacy newt theme * ubuntu -- the aubergine theme (basically, s/blue/magenta/g) These are installed to: * /etc/newt/palette.dark * /etc/newt/palette.original * /etc/newt/palette.ubuntu By default, there is a symlink installed by cdebconf-newt-udeb in the ISO filesystem: * /etc/newt/palette - /etc/newt/palette.ubuntu At debian-installer/cdebconf initialization of the newt frontend, if a kernel parameter FRONTEND_BACKGROUND=whatever is found, then the symlink at /etc/newt/palette is broken and replaced with a symlink to /etc/newt/palette.whatever. In this way, any derivative of Ubuntu can ship their own palette in a udeb that's included in their ISO build, install that palette at /etc/newt/palette.kubuntu, for example, and append FRONTEND_BACKGROUND=kubuntu to the kernel parameters. If you (or your Ubuntu derivative) just want the legacy behavior, then don't bother shipping your own palette, but simply append FRONTEND_BACKGROUND=original to the kernel parameters. I hope this helps with your calls for reconfigurability! I've enjoyed working with everyone on this ;-) Could we please make the post-freeze design changes opt-in instead of opt-out so other teams don't have to keep getting distracted from their planned work? Scott K -- ubuntu-devel mailing list ubuntu-devel@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel
Re: planning for UDS-O
On 03/29/2011 11:53 AM, Jorge O. Castro wrote: On Thu, Mar 24, 2011 at 7:28 PM, Allison Randal alli...@canonical.com wrote: * April 29th-May 5th: Natty release is done, get blueprints ready for UDS. The idea is not to hard-bake plans and specifications for the Oneiric cycle before UDS, but to have a clear idea of what needs discussion at UDS, so we make the best use of our limited time together in person. [The UDS schedulers will have some input here about when they need blueprints.] I'd just like to add that Launchpad is ready for blueprints so if you want to do them now that would be a boon. You can easily get your deferred ones from last cycle up to speed: https://blueprints.launchpad.net/sprints/uds-o Everyone please try to get your blueprints in by the *** 5th of May ***; if everyone waits until the end there's a massive amount of change in the scheduler and then people's sessions keep shifting the week before UDS, which makes it tougher for people to plan out their personal schedule when they attend. To clarify, we should only bother if said deferred blueprint actually needs another session, rather than simply more work ;) -- ubuntu-devel mailing list ubuntu-devel@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel
Natty test rebuild for amd64, armel, i386 (all components)
Another natty test rebuild for amd64, armel and i386 was started yesterday, including all components. Packages in the main component will build first. The test archives are: https://launchpad.net/ubuntu/+archive/test-rebuild-20110329/ https://launchpad.net/ubuntu/+archive/test-rebuild-20110329-arm Build failures are tracked in http://people.ubuntuwire.org/~wgrant/rebuild-ftbfs-test/test-rebuild-20110329-natty.html http://people.ubuntuwire.org/~wgrant/rebuild-ftbfs-test/test-rebuild-20110329-arm-natty.html The status pages are updated hourly. The rebuilds are expected to complete sometime next week for amd64 and i386. Matthias -- ubuntu-devel mailing list ubuntu-devel@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel
