Re: Overview of Jockey replacement; options for Kubuntu?
Hello Jonathan, Jonathan Thomas [2012-05-29 8:24 -0400]: > > Please note that it just provides a PackageKit API. We don't use the > > actual PackageKit in Ubuntu as well, but the python-aptdaemon.pkcompat > > wrapper. Kubuntu does the same. > > This is incorrect, Kubuntu does not use aptdaemon at all Both aptdaemon and python-aptdaemon.pkcompat are on the Kubuntu images. > and doing so would bring in a considerable amount of GTK libraries It does depend on glib and python-gi, but there's little chance of avoiding glib in Kubuntu. I'm less sure about python-gi, though, that might be new. > not to mention yet another apt implementation aptdaemon does not reimplement apt, it provides the python-apt functionality over D-BUS (similar to PackageKit, but it's a lot faster on Ubuntu). > If at all I possible, I would like to write a QApt backend for > ubuntu-drivers-common. Sure, I don't have an opinion about whether or not this is better, as I don't know QApt myself. > > This provides an upstream friendly API, so that our GUIs for driver > > detection do not have to stay distro specific for all times. However, > > you don't have to use it, of course. > > Currently it's being dragged in by nvidia-common, so it's not exactly > optional if you have an nvidia card... nvidia-common was renamed to ubuntu-drivers-common, as it is not just for NVidia, but also for fglrx and the pvr-omap4 driver. As it is taking over Jockey's functionality, it is pretty much mandatory in 12.10, but in exchange we can drop Jockey. Thanks, Martin -- Martin Pitt| http://www.piware.de Ubuntu Developer (www.ubuntu.com) | Debian Developer (www.debian.org) -- ubuntu-devel mailing list ubuntu-devel@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel
The future of migration-assistant
Following a review[1] of the quality of migration-assistant[2] and the resources available to support it at the Ubuntu Development Summit in Oakland for the Quantal release Ubuntu we have decided to remove migration-assistant from the installer for Quantal and to move the package to universe. Additionally, migration-assistant will be removed from ubiquity in the 12.04.1 release. However, the Ubuntu Foundations team will be happy to reintroduce migration-assistant if someone is willing to maintain it and fix some of its current bugs. Thanks! [1] https://blueprints.launchpad.net/ubuntu/+spec/foundations-q-testing-migration-assistant You can find some of the bugs that need fixing here too. [2] https://launchpad.net/migration-assistant -- Brian Murray Ubuntu Bug Master -- ubuntu-devel mailing list ubuntu-devel@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel
Minutes from the Ubuntu Kernel Team meeting, 2012-05-29
= Meeting Minutes = [[http://irclogs.ubuntu.com/2012/05/29/%23ubuntu-meeting.txt|IRC Log of the meeting.]] [[http://voices.canonical.com/kernelteam|Meeting minutes.]] == Agenda == [[https://wiki.ubuntu.com/KernelTeam/Meeting#Tues, 29 May, 2012|20120529 Meeting Agenda]] === ARM Status === Q/omap4: Ubuntu-3.4.0-201.3 is out, with hdmi and jack audio support. Some of the new features (like video and audio offloading to gpu/dsp) will have to wait until 3.5rcX hits master, since we need CMA and dma-map support (already present in linus vanilla). only fools rush in === Release Metrics and Incoming Bugs === Release metrics and incoming bug data can be reviewed at the following link: http://people.canonical.com/~kernel/reports/kt-meeting.txt === Milestone Targeted Work Items === || apw || hardware-q-kernel-config-review || 4 work item || || || hardware-q-kernel-delta-review || 3 work items || || || hardware-q-kernel-versions-and-flavors || 1 work item || || smb || hardware-q-kernel-config-review || 1 work item || || || hardware-q-kernel-delta-review || 1 work item || || ppisati || hardware-q-kernel-config-review || 1 work item || || jk- || hardware-q-kernel-config-review || 2 work items || || ogasawara || hardware-q-kernel-config-review || 1 work item || || || hardware-q-kernel-delta-review || 1 work item || || cking || hardware-q-kernel-delta-review || 3 work items || || jjohansen || hardware-q-kernel-config-review || 2 work item || || kernel-team || hardware-q-kernel-config-review || 10 work items || || || hardware-q-kernel-versions-and-flavors || 2 work items || If your name is in the above table, please review your Alpha-1 work items. If anyone has a spare cycle, feel free to take one of the work items assigned to the team. Last week we uploaded the 3.4.0-3.8 Quantal kernel. This included an updated AppArmor patch set and misc config updates and bug fixes. Please note that Alpha-1 is next Thurs June 7. I'll intend to upload a final Alpha-1 kernel early next week, ie Monday. We've also began providing the 12.10 kernel for 12.04. We welcome any early adopters to plaes install, test, and let us know your feedback. It is available from the following PPA: https://launchpad.net/~ubuntu-x-swat/+archive/q-lts-backport Important upcoming dates: * Thurs Jun 7 - Alpha 1 (~1 week) === Status: CVE's === == 2012-05-29 (weekly) == Currently we have 88 CVEs on our radar, with 2 new CVEs added this week. See the CVE matrix for the current list: http://people.canonical.com/~kernel/cve/pkg/ALL-linux.html Overall the backlog has increased slightly slightly this week: http://people.canonical.com/~kernel/status/cve-metrics.txt http://people.canonical.com/~kernel/cve/pkg/CVE-linux.txt === Status: Stable, Security, and Bugfix Kernel Updates - Precise/Oneiric/Natty/Lucid/Hardy === Here is the status for the main kernels, until today (May 29): * Hardy- 2.6.24-31.101 - No change this cycle * Lucid- 2.6.32-41.90 - Testing; Single CVE * Natty- 2.6.38-15.60 - Testing: 7 CVEs * Oneiric - 3.0.0-21.35 - Verification; 2 stable upstream releases (approx. 111 commits) * Precise - 3.2.0-25.39 - Verification; 2 stable upstream releases (approx. 271 commits) Current opened tracking bugs details: * http://people.canonical.com/~kernel/reports/kernel-sru-workflow.html For SRUs, SRU report is a good source of information: * http://people.canonical.com/~kernel/reports/sru-report.html Future stable cadence cycles: * https://wiki.ubuntu.com/QuantalQuetzal/ReleaseInterlock === Open Discussion or Questions? Raise your hand to be recognized === An old colleague of mine, Dave Taht, is a member of the http://www.bufferbloat.net/ group. Some of their work will be landing in the 3.5 kernel (codel and fq_codel - a new active TCP queue management algo). Dave would like to be in contact with someone on the Ubuntu kernel team to talk about configuration and usage issues for that stuff. Shall I direct him to anyone in particular? Is there a networking point-person? kamal, i'd say just get him to send email to kernel-team@ kamal, he can start with me or apw kernel-team@ works as well ok, two names + the kernel-team@ list :-)that'll do :-) thanks. -- ubuntu-devel mailing list ubuntu-devel@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel
Quantal 12.10 Kernel Flavors
Hi All, With the Quantal 12.10 Alpha-1 milestone on the horizon, the Ubuntu Kernel Team felt this would be an appropriate time to highlight and publicize some of the restructuring efforts that have surrounded the 12.10 Kernel flavors: * As previously discussed in the 12.04 cycle [1] and approved by the Tech Board [2], the i386 non-pae generic kernel flavor has been dropped for 12.10. * We have re-named the generic-pae flavor to a generic flavor for 12.10. * We have collapsed the virtual flavor into the generic flavor offering for 12.10. At this time I would also like to point out that we have modified the kernel packaging for x86 such that the generic flavor is actually bundled and delivered via 2 packages to allow support for both the virtual and non-virtual instances and installations. For a detailed overview of the transitions which have taken place, please refer to the thread on the kernel-team mailing list [3]. As a final note, for those upgrading from Precise 12.04, the flavor changes should go unnoticed assuming the appropriate meta packages have been installed. If there are any questions or concerns, please let us know. Thanks, Leann [1] https://lists.ubuntu.com/archives/ubuntu-devel/2011-November/034399.html [2] https://wiki.ubuntu.com/TechnicalBoard/TeamReports/11/December [3] https://lists.ubuntu.com/archives/kernel-team/2012-May/020318.html -- ubuntu-devel mailing list ubuntu-devel@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel
reminder: Feature Definition Freeze on 5/31 2100 UTC
Dear Developers, Just a reminder to get your blueprints set into the appropriate priority and approved for Quantal before Thursday 5/31[1]. We'll be resetting the trend lines for this release right after the FeatureDefinitionFreeze. Blueprints should have all Work Items, in the new "Work Items" section, rather than in the Whiteboard section for this release [2]. Also, in order to show up properly on status.ubuntu.com, blueprints must be marked as approved, have an importance set and targetted to the release. If anyone needs help setting up a topic to track cross team activities, please ping me before 2100 UTC on Wednesday 5/30. Thank you for your help getting the Quantal planning figured out before we start doing our milestone releases. :) Kate. on behalf of the Ubuntu Release Team [1] https://wiki.ubuntu.com/FeatureDefinitionFreeze [2] https://wiki.ubuntu.com/BlueprintSpec#Blueprint_Work_Items -- ubuntu-devel mailing list ubuntu-devel@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel
Re: Overview of Jockey replacement; options for Kubuntu?
Hi, On Tue, May 29, 2012 at 1:23 AM, Martin Pitt wrote: > Hello Jonathan, > > Jonathan Thomas [2012-05-25 9:09 -0400]: >> I think that we'd rather not use PackageKit (for Kubuntu at least). > > Please note that it just provides a PackageKit API. We don't use the > actual PackageKit in Ubuntu as well, but the python-aptdaemon.pkcompat > wrapper. Kubuntu does the same. This is incorrect, Kubuntu does not use aptdaemon at all, and doing so would bring in a considerable amount of GTK libraries, not to mention yet another apt implementation. If at all I possible, I would like to write a QApt backend for ubuntu-drivers-common. > > This provides an upstream friendly API, so that our GUIs for driver > detection do not have to stay distro specific for all times. However, > you don't have to use it, of course. Currently it's being dragged in by nvidia-common, so it's not exactly optional if you have an nvidia card... > >> We already have python-apt and QApt as part of the default Kubuntu >> install, so having a third apt worker implementation would be >> undesirable. Could the new jockey communicate with a "what >> provides-helper" written with libqapt that uses DBus for >> communication, and use the qaptworker for running installs if I were >> to implement such a helper? > > ubuntu-drivers-common also provides a simple custom API: > > UbuntuDrivers.detect.system_driver_packages() > > → give me all driver packages for this system > > UbuntuDrivers.detect.packages_for_modalias(apt_cache, modalias) > > → give me the driver package(s) for this piece of hardware > > which you can use and wrap however you like. > >> > * Kubuntu implements a similar (or their own) design using the >> > ubuntu-drivers-common API in the KDE control center as an embedded >> > tab. Then we can also drop jockey-kde. >> ... then I think it would be beneficial to write a KConfig Module so >> that it could be integrated as a sub-page of the "Display and Monitor" >> page in KDE's System Settings. I attempted to write a Jockey frontend >> for this a few years back, but was foiled due to the multithreading in >> jockey not playing nice with the KDE plugin apis. > > That could work better now. The "basic" API (system_driver_packages() > and packages_for_modalias()) does not use anything fancy like threads, > D-BUS, async, etc, just plain python-apt. > > I agree. > > Thanks, > > Martin > -- > Martin Pitt | http://www.piware.de > Ubuntu Developer (www.ubuntu.com) | Debian Developer (www.debian.org) > > -- > kubuntu-devel mailing list > kubuntu-de...@lists.ubuntu.com > Modify settings or unsubscribe at: > https://lists.ubuntu.com/mailman/listinfo/kubuntu-devel -- ubuntu-devel mailing list ubuntu-devel@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel
Patch Pilot report 2012-05-29
Hello everybody, this is what I got through in my shift today: lp:~jjesse/ubuntu-packaging-guide/fixes-bug978493 - reviewed it, might still need a bit of work. lp:~andrewsomething/ubuntu/quantal/sphinx/merge1.1.3+dfsg-4 - uploaded. fwts V0.25.02 release (pad.lv/1004410) - uploaded. Please merge open-font-design-toolkit 1.2 (universe) from Debian unstable (main) (pad.lv/1004879) - uploaded. SRU: update to onboard 0.97.1 bugfix release (debian source supplied) (pad.lv/999111) - uploaded. Sync mkvtoolnix 5.5.0-1 (universe) from Debian unstable (main) (pad.lv/1004533) - reviewed, might need a merge. lp:~logatron/ubuntu/quantal/imagemagick/fix-for-993041 - forwarded the patch to Debian instead. [SRU] Unity-Mail 0.92.3 bugfix release (pad.lv/1002802) - uploaded to quantal and precise-proposed. Please merge fuse 2.9.0-1 (main) from Debian unstable (main) (pad.lv/1003613) - uploaded. Sync policycoreutils 2.1.10-6 (universe) from Debian unstable (main) (pad.lv/1004480) - synced. Failure trying to purge policycoreutils (pad.lv/1005398) - fixed in quantal through sync, asked bigon, if he could have a look at the precise fix. Have a great day, Daniel -- Get involved in Ubuntu development! developer.ubuntu.com/packaging And follow @ubuntudev on identi.ca/twitter.com/facebook.com/gplus.to -- ubuntu-devel mailing list ubuntu-devel@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel
Re: syncing from testing? [was: Quantal open for development]
On Thu, May 24, 2012 at 06:28:55AM -0400, Scott Kitterman wrote: > Where can I read about this plan for our own version of a Testing > migration? It's not very well written up, but it's covered by: https://blueprints.launchpad.net/ubuntu/+spec/foundations-p-upload-intermediary https://blueprints.launchpad.net/ubuntu/+spec/other-q-freeze-use-of-proposed Essentially the aim is to auto-migrate from -proposed to once doing so doesn't worsen installability, perhaps with a sprinkling of automatic testing thrown in; however we don't intend to duplicate the multi-day delays of Debian testing. -- Colin Watson [cjwat...@ubuntu.com] -- ubuntu-devel mailing list ubuntu-devel@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel
