gmane.linux.ubuntu.devel

If you REALLY want to share a taxi...

Daniel Holbach — 2008-12-02T07:40:19

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 ...please mention WHEN you arrive and WHERE! There are a lot of entries with * no data about the arrival departure at all * no information if you’re going to land at San Jose or San Francisco Another minor point is that everybody uses a different format for specifying date and time, which makes it very hard to spot who arrives when. (It’s probably just me, but I prefer something like "2008-09-12 15:45" ... local time.) I sorted https://wiki.ubuntu.com/UDSJaunty/Attendees and tried to make things easier to spot. Please update your information... if you really want to share a taxi at UDS. Have a nice day, Daniel - -- My 5 today: #278418 (human-icon-theme), #275989 (silc-toolkit), #304105 (jcc), #303783 (openal-soft), #303916 (nginx) Do 5 a day - every day! https://wiki.ubuntu.com/5-A-Day -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iEYEARECAAYFAkk05mMACgkQRjrlnQWd1evungCaAtQqaz+PYPMe+HkQ4Cu+4kRe yCYAn3HsbSxDNEkq3JKG9wtTItvrmyQI =ek6R -----END PGP SIGNATURE-----

armel architecture info wanted

Morten Kjeldgaard — 2008-11-29T13:54:19

Hi, Will someone with access to a machine running the armel platform please run the following commands: touch foo.c gcc -E -dM foo.c ... and post the output here? (Or perhaps even better, on the Wiki, where similar information from other platforms could be added). Thanks, Morten

Foundations Team Weekly Summary, 2008-11-26

Robbie Williamson — 2008-11-26T17:52:27

== Apologies == * EvanDandrea - vacation * LarsWirzenius - vacation * ScottJamesRemnant - vacation == Activity reports == === Colin Watson === * Jaunty Alpha 1: * Fixed some dmraid issues in hw-detect. Later, realised that the same bug affected four other installer components (base-installer, grub-installer, os-prober, and partman-base), and fixed them all. Filed dmraid #300825 about the general issue. * Tracked down and fixed udev #300426. * Basic smoke-testing and release. * ARM porting assistance: * No-change rebuilds: contact-lookup-applet, foomatic-filters * lynx-cur build-dependency adjustment so that it can build now that it needs to be in main. * Fixed misbuilt libtool on armel (noticed while investigating dictd build failure; filed as #299931). * Sent patch series to kernel-team< at > to add d-i modules for armel. * Some fiddling with the d-i build system, but it won't quite work yet. * Merges: * Finished debian-installer merge. * installation-guide, klibc, network-console, refit, openssh * Sponsorship: * Most of the core mono 2.0 stack. * lintian #292872 (not really sponsorship but it was on the list due to other bug tasks and this cleared it off). * Miscellaneous installer work: * Fixed oem-config build failure. * Tried to get the d-i GTK frontend working. Seems to be running into a bug in the GDK directfb backend that I haven't quite managed to fix yet. * Made console-setup default to not autodetecting the keyboard. * Investigated applying a "human" theme to cdebconf; tricky due to 16-colour VGA palette (hello, 1987). * Investigated choose-mirror #209691 (WPAD proxy autodetection). The DHCP option side of things is straightforward, but dealing with the returned file is a bit harder than I thought. * CD images: * Fixed cdimage lpia mirroring problem for Steve Kowalik. * Arranged to remove installer components from the CDs that are in both the cdrom and netboot initrds already. Saved several megabytes. * Minor script polishing for things that irritated me while publishing Jaunty Alpha 1. * UDS preparation: * Boot performance call with OEM Services. * Some analysis of historical bug-fixing performance. Call on the subject. * Server installer polish call. * Went through some of the old bugs assigned to me, including: * SRU write-up and upload for partman-base #149832. * Fixed grub-installer #10661. * Checked information provided on parted #229388; still need more information here. * Fixed console-common/kbd #18448. * Diagnosed tzsetup #140934 and reassigned to system-tools-backends. * Dealt with some bits of console-setup #94177, but more bits keep on popping up ... * 8.10 post-mortem. * Conversation with Celso on Soyuz #159585. * Fortnightly IS review call. === James Westby === * Distributed Development * Worked with IS to get the pieces in place so we can announce. Hoping to have the last bits done today. * Worked on documentation for the initial availability of branches. * Ubuntu * Lots of sponsoring. Again I won't itemise. * Fixed a bunch of build failures. A lot of the issues are related to libtool. * Started a discussion on how to do "developer news". === Luke Yelavich === * Accessibility * Updated more GNOME accessibility stack packages, libgail-gnome, gnome-speech. * Started preparing an SRU for gnome-orca 2.24.2. * Audio * With the help of the community, was able to track down, and sponsor an upload to fix a long standing bug where for some users, the system would appear to freeze for a variable amount of time when it came to saving alsa audio settings on shutdown or restart. * Other audio bug triaging. Sheesh we are receiving jaunty audio bugs already, and I'm not even running it on anything yet. * Merged pulseaudio again, to include some extra fixes and patches that debian has grabbed from Trunk. Fedora is also supposed to have some patches worth looking into, will look at grabbing them in the next week. * Proposed a spec for managing alsa modules outside the kernel. * Merged libcanberra, and set it to be built against pulseaudio in the process. * dmraid * Uploaded an update for dmraid to intrepid-proposed to fix the permissions for a script that gets run in the initramfs. Still need to verify it, and get a second verification. * Started digging into how dmraid can be made to report more information using exit codes, rather than having text that has to be grepped for all the time. * Misc * Some alpha 1 testing. * Registered attendance for UDS as well as marked areas of interest. === Matthias Klose === * armel bootstrap: * babysitting armel buildd; this should be finished now. the alternative would have been to give back all failed packages and waste a lot of build time. * armel specific fixes for OOo, and some other packages. * KDE is still problematic. * more syncs and merges * openjdk-6 updates * python3.0 updates and upstream fixes * weekend fun: fix hppa packages (rebuilds for uninstallable packages) === Michael Vogt === * compiz * debug compiz/expo plugin screensaver bypass (LP #247088) * report bypass problem upstream (both g-s-s and compiz) * add inhibit plugin as (possible) solution, not accepted upstream * fix bypass problem with expo patch from upstream (yeah) * uploaded for gutsy, hardy, intrepid (compiz-fusion-plugins-main) * fix/update/create matching bzr repos * translated package description * improve workflow for translated package description uploads further * add cmp-translations.py file that can compare two Translations-$lang files and give useful stats * add gen-sync.sh script that can generate "patch" files for the Translation files (useful for sharing our translations with debian) * apt * debugging with cprov on soyuz/apt-ftparchive issue * coded on apt-ftparchive pool expire tool (for cprov/soyuz) * merged apt from debian-sid and upload new version into jaunty * merged python-apt consolidation branch that moves code from gdebi/update-manager into python-apt (thanks glatzor) * Work on replay-attack-prevention code (debian #463030) by add "Valid-Until" header and "Acquire::Max-Default-Age::Label" options (in lp:~mvo/apt/prevent-replay-attacks) * update-manager * fix update-manager xorg.conf rewriting for multiseat setups * add update-manager modaliases check for fglrx in jaunty too (#284408) * fix ssh detection in update-manager (#301787) (now that sudo eats the environment) * misc * spec work * sponsoring/merges (kdelibs4, pylibenchant, pnm2ppa, libglade2, intltool, inkscape, apt) * new notification-daemon/libnotify * rename app-install-data-commercial -> app-install-data-partner * partner repository * work on app-install-data-partner with brian * UDS planning for future of partner (brian has interessting ideas, togehter with apturl) === Steve Langasek === * Packages * merges: liferea, boost, kipi-plugins * Sponsorship * liferea (bug #295490) * Misc * Lexington November Nexus * Monday archive duties

python3.0 upgrade issues

Kjell Braden — 2008-11-24T14:57:37

init scripts, /var/run and dpkg-statoverride

James Westby — 2008-11-24T15:26:46

Hi, Some packages require certain ownership of or permissions on directories in /var/run. These packages chown/chmod the directories in the postinst. As we all know Ubuntu has /var/run on a tmpfs, and as such we move code to do this from the postinst to the init script. The correct thing to do is to guard these operations by a call to dpkg-statoverride to allow the admin to override permissions. However, I have seen cases where we have a bare chown/chmod in the init script, so we don't support that. Is this something that we want to support? Does it even make any sense for directories on a tmpfs? Thanks, James P.S. it is important to actually move code that changes permissions on /var/run directories from the postinst to the init script, i.e. don't leave it in the postinst. This is because a reboot between the package being unpacked and configured will cause an error as the directory will not be present. If the postinst needs the directory before running init script then have an explicit mkdir in the postinst, and don't rely on the directory being shipped in the package.

help: pythonpackage: gconf-schemas --unregister does not deleteeverything

Francesco Fumanti — 2008-11-21T15:20:55

Hello, I am trying to add gconf schemas to the python package named onboard. The package uses cdbs and python-distutils.mk. The call to gh_gconf in debian/rules generates the corresponding gconf-schemas --register and gconf-schemas --unregister calls in the postinst and prerm scripts. After building the debian package in the pbuilder environment, the installation of the bin package registers the schemas; uninstalling the package unregisters the keys, but not completely: the keys are all deleted, but the /apps/onboard and the /schemas/apps/onboard entries remain listed in the gconf database (at least they continue to show up in the gconf editor). Could anybody please tell me what is going on or how to make also the two remaining entries disappear? You can have a look at the debian/rules file and at the gconf schemas file in the following thread: http://ubuntuforums.org/showthread.php?t=984014 Many thanks in advance for any help. Cheers Francesco

pbuilder-satisfydepends-dummy thinks libmilter-dev is avirtualpackage

Alban Deniz — 2008-11-22T14:55:41

Hello, I'm packaging for Ubuntu an application I'm developing, and I've encountered a problem I wasn't able find a solution in the docs. I'm getting error when attempting to create a binary package using pbuilder (entire output is below): The following packages have unmet dependencies: pbuilder-satisfydepends-dummy: Depends: libmilter-dev which is a virtual package. Depends: libmilter1 which is a virtual package. However, neither libmilter-dev nor libmilter1 are listed as virtual packages, according to 'aptitude search libmilter-dev libmilter1'. I'd like to know how to solve this (either a solution or a reference would be great). I wasn't able to find this issue mentioned on any of the packaging manuals or searches. Also, if this isn't the appropriate list, I apologize (and please let me know of a more appropriate list). I'm using debhelper (single binary package). Contents of control: Source: snfmilter Section: unknown Priority: extra Maintainer: Alban Deniz microneil.com> Build-Depends: debhelper (>= 5), autotools-dev, libmilter1, libmilter-dev, wget, gzip Standards-Version: 3.7.2 Package: snfmilter Architecture: any Depends: ${shlibs:Depends}, ${misc:Depends} Recommends: sendmail, postfix Description: MicroNeil milter for blocking spam and IP scanning SNFMilter is a milter that interfaces with an MTA (such as postfix or sendmail) to tag any email message that looks like spam. The criteria for judging a message to be spam includes the message content and also the originating IP address. Built source package with 'debuild -S -rfakeroot' Attempted to build binary package with 'pbuilder --build ../*.dsc' Full output of pbuilder: root< at >orkey:/home/adeniz/microNeil/SNFMilter-debhelper/snfmilter-0.0.9# pbuilder --build ../*.dsc W: /root/.pbuilderrc does not exist I: using fakeroot in build. Current time: Sat Nov 22 09:17:36 EST 2008 pbuilder-time-stamp: 1227363456 Building the build Environment -> extracting base tarball [/var/cache/pbuilder/base.tgz] -> creating local configuration -> copying local configuration -> mounting /proc filesystem -> mounting /dev/pts filesystem -> policy-rc.d already exists Obtaining the cached apt archive contents Installing the build-deps -> Attempting to satisfy build-dependencies -> Creating pbuilder-satisfydepends-dummy package Package: pbuilder-satisfydepends-dummy Version: 0.invalid.0 Architecture: i386 Maintainer: Debian Pbuilder Team lists.alioth.debian.org> Description: Dummy package to satisfy dependencies with aptitude - created by pbuilder This package was created automatically by pbuilder and should Depends: autotools-dev, debhelper (>= 5), gzip, libmilter-dev, libmilter1, wget dpkg-deb: building package `pbuilder-satisfydepends-dummy' in `/tmp/satisfydepends-aptitude/pbu ilder-satisfydepends-dummy.deb'. Reading package lists... Done Building dependency tree Reading state information... Done aptitude is already the newest version. 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. Selecting previously deselected package pbuilder-satisfydepends-dummy. (Reading database ... 12190 files and directories currently installed.) Unpacking pbuilder-satisfydepends-dummy (from .../pbuilder-satisfydepends-dummy.deb) ... dpkg: dependency problems prevent configuration of pbuilder-satisfydepends-dummy: pbuilder-satisfydepends-dummy depends on autotools-dev; however: Package autotools-dev is not installed. pbuilder-satisfydepends-dummy depends on debhelper (>= 5); however: Package debhelper is not installed. pbuilder-satisfydepends-dummy depends on libmilter-dev; however: Package libmilter-dev is not installed. pbuilder-satisfydepends-dummy depends on libmilter1; however: Package libmilter1 is not installed. pbuilder-satisfydepends-dummy depends on wget; however: Package wget is not installed. dpkg: error processing pbuilder-satisfydepends-dummy (--install): dependency problems - leaving unconfigured Errors were encountered while processing: pbuilder-satisfydepends-dummy Reading package lists... Done Building dependency tree Reading state information... Done Initializing package states... Done Writing extended state information... Done Building tag database... Done The following packages are BROKEN: pbuilder-satisfydepends-dummy The following NEW packages will be automatically installed: autotools-dev debhelper file gettext html2text intltool-debian libmagic1 po-debconf wget The following NEW packages will be installed: autotools-dev debhelper file gettext html2text intltool-debian libmagic1 po-debconf wget 0 packages upgraded, 9 newly installed, 0 to remove and 0 not upgraded. Need to get 0B/3517kB of archives. After unpacking 14.1MB will be used. The following packages have unmet dependencies: pbuilder-satisfydepends-dummy: Depends: libmilter-dev which is a virtual package. Depends: libmilter1 which is a virtual package. Resolving dependencies... The following actions will resolve these dependencies: Remove the following packages: pbuilder-satisfydepends-dummy Score is -9850 The following NEW packages will be automatically installed: file libmagic1 The following packages will be automatically REMOVED: pbuilder-satisfydepends-dummy The following NEW packages will be installed: file libmagic1 The following packages will be REMOVED: pbuilder-satisfydepends-dummy 0 packages upgraded, 2 newly installed, 1 to remove and 0 not upgraded. Need to get 0B/373kB of archives. After unpacking 1950kB will be used. Writing extended state information... Done (Reading database ... 12190 files and directories currently installed.) Removing pbuilder-satisfydepends-dummy ... Selecting previously deselected package libmagic1. (Reading database ... 12190 files and directories currently installed.) Unpacking libmagic1 (from .../libmagic1_4.21-3_i386.deb) ... Selecting previously deselected package file. Unpacking file (from .../archives/file_4.21-3_i386.deb) ... Setting up libmagic1 (4.21-3) ... Setting up file (4.21-3) ... Processing triggers for libc6 ... ldconfig deferred processing now taking place Reading package lists... Done Building dependency tree Reading state information... Done Reading extended state information Initializing package states... Done Writing extended state information... Done Building tag database... Done Aptitude couldn't satisfy the build dependencies E: pbuilder-satisfydepends failed. Copying back the cached apt archive contents -> unmounting dev/pts filesystem -> unmounting proc filesystem -> cleaning the build env -> removing directory /var/cache/pbuilder/build//12885 and its subdirectories root< at >orkey:/home/adeniz/microNeil/SNFMilter-debhelper/snfmilter-0.0.9# Thanks, Alban

Foundations Team Weekly Summary, 2008-11-21

Robbie Williamson — 2008-11-22T06:09:45

== Activity reports == === Colin Watson === * Fixed gfxboot-theme-ubuntu #294840. * Helped Kyle Nitzsche (OEM) out with taking over Classmate PC work. * Merged: memtest86+, partman-auto, partman-auto-lvm,partman-auto-crypto, network-console, installation-report,localechooser, and most of debian-installer * Made powermanagement-interface build on armel, and cleared out some old bugs in it (#45680, #149678, #182651). * Typo fix in language-selector. * Bits of man-db and dpkg bug triage. * Fix gamin build failure (noticed by Matthias on armel). * Fix palo build failure. * Various armel-related buildability and installability fixes; also some related archive administration work. * Worked to get the GTK debian-installer frontend buildable in Ubuntu (including vte packaging merge). * Wrote archive script to check for override mismatches between architectures; output at http://people.ubuntu.com/~ubuntu-archive/architecture-mismatches.txt (may well be empty when you read this, but it does work ...). === Evan Dandrea === * Short week, off on Friday, November 14th. * oem-config work * partman-target merge. * Specification work: JauntyUbiquityUsability, usb-creator (still in progress) === James Westby === ==== Distributed Development ==== * Machine moved to the DMZ so that it can be exposed to the public to serve branches. No loggerhead/playground set up yet. * Move meant that the firewall is currently preventing the importers from working, so a backlog is building up. RT ticket filed requesting the needed holes to be punched in the firewall or alternative solution proposed. * Discovered that my user account on the machine had a wacky locale set. Changed to a sane one and reduced the failure count by ~1000 (exact number not available at present due to previous point, somewhere around 500 failures remain, ~4%) * Basic documentation written for how to use the branches, need to incorporate Colin's feedback, and detail what is different for working with the temporary branches. * Spoke to Celso last week about getting the needed APIs, apparently shouldn't be too hard, but isn't top of his priority list. Current situation works, but isn't ideal. I can work on a solution that will improve most cases. * Spoke to Kubuntu team about bzr for packaging. * Also spoke to Celso about building packages directly from bzr. This is hard to do if we want to retain signed source packages, but not impossible. ==== Ubuntu ==== * Sponsoring feast. >50 items sponsored in the last few days. * UDS specs === Lars Wirzenius === * Thinking about wonderful things Cruft Remover could do in jaunty. No coding or wiki activity yet. * Started preparing my Ubuntu Contributing Developer application. * Looked at the lockfile-progs merge, and prodded the previous uploader about it (looked like an easy one). * Verified that the buildd-built system-cleaner SRU binaries fix the bugs the SRU is supposed to fix. === Luke Yelavich === ==== Audio ==== * Audio bug triaging. * Ongoing consideration and examination on how the alsa kernel modules could be maintained outside the kernel in their own package, for the several kernels Ubuntu has. * Merged alsa-driver, alsa-lib, alsa-plugins, alsa-utils, and pulseaudio. Jaunty will have 0.9,13 at a minimum, and hopefully one or two releases newer than that will be available before feature freeze. ==== Dmraid ==== * Spent some time checking that the dmraid package in Debian has all the bits I put into the ubuntu package, and fakesynced it into intrepid, due to the newer upstream version in alioth svn not being in debian experimental yet. * Resume packaging work for the pieces needed for dmraid event monitoring. ==== Misc ==== * Cleared the debian-installer component merges that my name was next to, as well as the universe merges that I care about. * Updated some newly released gnome 2.25 accessibility packages. === Matthias Klose === * armel bootstrap * toolchain updates * bug triage === Michael Vogt === ==== SRU ==== * update compoiz-fusion-plugins-unsupported * SRU for the package description translations to jaunty-proposed ==== sponsoring ==== * Review/sponsor system-cleaner ==== apt ==== * fix apt pty problem with background processes (debian #463030) * Work on updating ddtp debian import script (debian does no longer publish the Translations tarball on ddtp.debian.net) ==== synaptic ==== * add (basic) support for screenshots.debian.net by adding a button fetch thumbs/full screenshots * hack a bit on screenshotMaker.py - a script that can create screenshots automatically and unattended in xvfb ==== popularity-conetest ==== * create backup of the data (we have a lot of it) * write code so that it can give the most popular packages that are not part of a meta-package (in g-a-i utils/analyzePopconData.py) ==== merges ==== * Merge cron, unzip, vorbisgain, upx-ucl, tracker, smartmontools, moin, libxslt, lockfile-progs, libgsf, lapack, aptitude, gpm, popularity-contest, apmd, alacarte, python-gdata, xsane (and submit changes to debian when appropriate) ==== update-manager ==== * look into libvirt and if the auto-upgrade-tester can be ported to it easily * setup auto-upgrade-tester for intrepid-jauny * Fix --ssh-key to install a ssh server in ubuntu-vm-builder and push to lp * fix sources.list inconsistencies on upgrade as discussed on ubuntu-devel * enable interpid->jaunty upgrades in the meta-release-development file (and test-upgrade to it) ==== misc ==== * research the various backup tools and look at the various solutions === Steve Langasek === ===== Release management ===== * finish getting the archive ready for jaunty * jaunty opening merges: emacs-goodies-el * preparations for alpha-1 ==== Packages ==== * further cleanup of PAM bugs * pick up assigned (== t-i-l) merges for jaunty: choose-mirror,cracklib2, djvulibre, mime-tools, wireless-tools, libpam-ldap ==== Misc ==== * aid with indoctrination of new kernel team members < at > Portland sprint * Lexington November Nexus * Monday archive duties

tarball-in-tarball packaging

Emmet Hikory — 2008-11-22T03:09:59

Fellow Developers, I am sure that some of you like tarball-in-tarball packaging, and that others of you dislike it. Some of you may have no special preference I've seen discussions where strong arguments were presented for doing it each way, and have built my own set of personal preferences on the matter. On this contentious topic, I'd like to ask that one thing *never* be done in this area: if you are updating to a new upstream of a package that is present in Debian, and not yet updated, please never alter the previous choice of whether to use tarball-in-tarball or not. If the package is orphaned, and you *really* want to change whether it uses tarball-in-tarball, please contact the Debian QA team to get the update in Debian. If there is an active maintainer, please defer to their wishes. Not doing so makes it impossible to achieve sync within that upstream version, and will complicate any merging process. Please consider that those later working on a package may not share your preference strongly enough to find working around such adjustments an acceptable cost for having had the package in the "right" state. Thank you.

Ubuntu 8.04 / 8.10 graphics detection changes?

Zachary Amsden — 2008-11-20T14:58:05

Hi, I'm triaging a VMware related Ubuntu bug where the Ubuntu desktop fails to load, and will only run in low-graphics mode if VMI is enabled when running in a virtual machine. Notably, the bug only happens on AMD hosts; Intel machines are unaffected. Also, it does not occur in 8.04, but it a regression observed in 8.10. This leads me to suspect some kind of CPUID type detection was added between the two that could possibly be misvirtualized when running with paravirtualization. Could someone point me to the right place to be looking at how graphics mode selection selection might have changed between these two? Thanks, Zach

/etc/motd template

Dustin Kirkland — 2008-11-20T15:49:08

In Intrepid, the Ubuntu Server Team created a new package, update-motd, which provides a very flexible framework for dynamically and regularly generating a more interesting and informative /etc/motd. From a command-line-only (Ubuntu Server) perspective, a dynamic MOTD approximates a text-based alternative to the Desktop's system tray. In Intrepid, the primary user of update-motd is landscape-sysinfo, which provides some useful statistics about the current system. In Jaunty, we have already added hooks to update-notifier to provide the number of updates available, and when a system restart is required using update-motd. I have a few more ideas about programs that could "grow" update-motd hooks, and I'm sure you can think of a few too... My question to you is about the stock /etc/motd used in Ubuntu, pasted here for convenience: -------- Linux t61p 2.6.27-8-generic #1 SMP Thu Nov 6 17:38:14 UTC 2008 x86_64 The programs included with the Ubuntu system are free software; the exact distribution terms for each program are described in the individual files in /usr/share/doc/*/copyright. Ubuntu comes with ABSOLUTELY NO WARRANTY, to the extent permitted by applicable law. To access official Ubuntu documentation, please visit: http://help.ubuntu.com/ -------- This "stock" information is provided by /etc/motd.tail (plus the uname line). update-motd is currently using this, because, well, we always have. I'm curious if the "free software" and "no warranty" paragraphs are still necessary/useful? Do they belong in the MOTD, printed *every* time a user logs onto a system on the command line? My thought is that these aren't exactly "Messages of the Day" (and we really now have the capability to make the MOTD be "Messages of the Day"). They're more like the "tips" you get the first time you open Gimp, or something. Would it be better to display these on first boot, or first-login, and then stow them away elsewhere, and leave /etc/motd to the more interesting, dynamic messages that provide relevant information about your system?

Foundations Team Weekly Summary, 2008-11-14

Robbie Williamson — 2008-11-14T17:07:19

== Apologies == * LukeYelavich - on vacation * JamesWestby - at November Nexus == Activity reports == === Colin Watson === * Merged: clock-setup, kbd, console-setup, lilo-installer, busybox(including fix for #293586, though that will need to be backported to intrepid), anna, finish-install, netcfg, silo-installer, yaboot-installer, grub-installer, palo-installer, parted, base-files, partman-newworld, partman-crypto, partman-ext3, partman-jfs, partman-xfs, partman-reiserfs, iso-scan (phew) * Some debian-installer bug review, including cleaning up very old daily-installer-* directories from the archive (#40186). * Followed up to upstart/util-linux #273189 with a more detailed description of work to be done (noticed during finish-install merge). * Investigated casper #70566 at some length by way of sponsorship processing; I have a cleaned-up version of the proposed patch in my casper working tree now, but this is likely to need more complex fixes in usplash in order to display non-ASCII characters properly,including perhaps switching to unifont. === Evan Dandrea === * Prepared for and presented a usb-creator UbuntuOpenWeek talk (https://wiki.ubuntu.com/MeetingLogs/openweekintrepid/UsbCreator). * Added a warning about what operating systems will be removed when selecting the "use entire disk" option in ubiquity. Still needs to be added to the advanced page. * Wrote up instructions on using the Ubuntu USB disks. Still in progress as I need to verify that they do not work on Intel Macs (firmware issue) other than my aging 2006 iMac. If anyone has an Intel Mac, I would greatly appreciate your assistance in this. * Modified ubiquity to notify the user of what operating systems will be deleted if they choose to use the entire disk. I still need to provide proper i18n support for this. * Dropped the timezone setting code from casper as it's unnecessary and resets the time on every reboot in persistent mode. Looking into why update-initramfs is disabled on the Live CD, especially in persistent mode, with the hope of fixing LP: #292159. * Made numerous fixes to usb-creator in preparation for an SRU for Intrepid and a backport for Hardy. Merged with Mario's branch and added i18n support. === Lars Wirzenius === * Fixes for system-cleaner's many bugs in intrepid, to prepare an SRU. (The upload has now been done, kindly sponsored by Michael Vogt.) === Matthias Klose === * Nov 04 - Nov 07: OOo ESC meeting / OOoCon, planning report * Nov 11: email catch up, catchup on bug reports, openjdk 6b13 build, gcc-snapshot update === Steve Langasek === Release management: * working on getting the archive ready for jaunty * post-release email roundup * change around the mythbuntu image builds from alternates to liveCDs, per Mario * SRU reviews Packages: * cleanup of PAM bugs Archive Administration: * partner archive cleanup Misc: * Monday archive duties

Proposal for restricted drivers policy adjustment

Michael Hrabanek — 2008-11-09T16:50:33

I have been thinking recently about the restricted driver policy. It's nice to get hardware directly not supported by kernel to work at least by using non-free drivers, but on the other side this could be two-edged and lead to ignorance from hw manufacturer because of weakening the demand for free drivers or open hardware specification. So I believe it would be very useful to take the strenght of Ubuntu community and send the clean message to hardware vendors that we demand free drivers by adding for example checkbox for something like 'I agree with contacting the manufacturer of my hardware with demand for free drivers so I won't need to mess with this in the future again' and ask for user's name so that ubuntu community can send perhaps once per a month an e-mail with every signed name to vendor... Or something like that When our voices will be loud enough we can make change and get rid of proprietary drivers.

Help Needed on Language pack Testing.

Sanjeev Bhise — 2008-11-13T08:21:14

libtool updates

Scott James Remnant — 2008-11-17T10:13:23

package removal explanation?

Dustin Kirkland — 2008-11-12T00:15:23

Can anyone point me to documentation or mailing list discussion as to why xmms was removed from Ubuntu universe? * https://launchpad.net/ubuntu/+source/xmms I mean, I know that upstream for the project is essentially dead, and there are tons of other alternative music players available. But xmms remains rock-solid for my use cases (streaming over http), and I continue to build it in my PPA for each Ubuntu release.

Promoting a package in a pocket to main

Michael Casadevall — 2008-11-08T08:04:39

Relevant bug: https://bugs.edge.launchpad.net/ubuntu/+source/xfprint4/+bug/211335 Essentially xfprint4 should depend on a2ps, but that is impossible since xfprint4 is in main (in gutsy, and dapper), and a2ps is in universe. Talking with the LP admins, promotion within a pocket is possible, but I'd believe this requires discussion before any actions are taken. Michael.

merges galore

Stefan Potyra — 2008-11-05T14:25:53

Merge-o-Matic and bzr packages

Scott James Remnant — 2008-11-05T11:56:29

Server Team 20081104 meeting minutes

Mathias Gug — 2008-11-04T20:06:12

Hi, Here are the minutes of the meeting. They can also be found online with the irc logs here: https://wiki.ubuntu.com/MeetingLogs/Server/20081104. ==== Server FAQ ==== nijaba reviewed the questions from the ServerFaQ[1]. He added new ones at the bottom of the page. The next step is now to update the answers. ACTION: mathiaz to add a section about updating the ServerFAQ to the Roadmap ACTION: sommer and nijaba to start updating the answers ACTION: kirkland to review the RAID related questions [1]: https://help.ubuntu.com/community/ServerFaq ==== Ideas for Jaunty ==== mathiaz reminded that ideas for Jaunty should be added to the ServerTeam IdeaPool[2] page so that they can be reviewed and included in discussions for the next UDS. [2]: https://wiki.ubuntu.com/ServerTeam/IdeaPool ==== Agree on next meeting date and time ==== Next meeting will be on Tuesday, November 11th at 16:00 UTC in #ubuntu- meeting.

Upcoming Ubuntu Kernel Team Meeting - Tuesday, 4th of November -17:00UTC - #ubuntu-meeting

Pete Graner — 2008-11-04T15:28:45

Hi, The next Ubuntu Kernel Team Meeting is scheduled for Tuesday, November 4th, 17:00 UTC in #ubuntu-meeting. NOTE: This is a channel and time change from previous meetings. If there are any discussion points or items for decision that you would like to add to the agenda [1], add an item to it and begin preparations to present a short introduction to the topic on #ubuntu-meeting during the scheduled session. [1]: https://wiki.ubuntu.com/KernelTeam/Meeting If you have have been working hard on the project and want to let others know what you have been up to, try to summarize it on the Reporting Page [2]. [2]: https://wiki.ubuntu.com/KernelTeam/ReportingPage As usual, anyone interested in the development of Ubuntu Kernel is welcome to attend. Thanks ~pete