Heya, first off, thanks for this contribution to the LTS, it's much appreciated!
As it happens, Ubuntu Precise has now progressed into Final Freeze. Right now changes to the distro are limited to just ultra-critical release bugs that the release team has flagged as priorities. Most other bugs, including this one, need to now be handled as Stable Release Updates (SRUs) or left until the next release (Q-series) opens for development. For reference, here is the SRU Policy Doc: https://wiki.ubuntu.com/StableReleaseUpdates I've looked at your patch and think it may qualify as an SRU, but there's a bit extra paperwork, which helps establish the justification for the change and makes the change easier for reviewers. Would you mind helping by filling in some blanks? I've pasted in the standard SRU template into the bug description. Click the yellow pencil icon to the right of 'Bug Description', and fill in the empty sections. Also, while the patch itself looks ok, there are a few changes necessary to target it as an SRU: 1. In the changelog entry, target the upload to 'precise-proposed' rather than just 'precise'. 2. The version number should increment by a point rather than a full number. Examples: Currently in precise Proposed for precise-proposed foobar-1.2-1 ---> foobar-1.2-1ubuntu0.1 foobar-1.2-1ubuntu2 ---> foobar-1.2-1ubuntu2.1 foobar-1.2~dfsg.1-1 ---> foobar-1.2~dfsg.1-1ubuntu0.1 foobar-1.2-1ubuntu1.5 ---> foobar-1.2-1ubuntu1.6 3. Make certain the correct bug # is listed in the changelog entry description, in this format: (LP: #123456) 4. Doublecheck the maintainer is set to Ubuntu. Easy to do, just run `update-maintainer` and it'll fix it. ** Description changed: + [Problem] + <1-2 sentence summary of the issue> + + [Impact] + <fill me in with explanation of severity and frequency of bug on users and justification for backporting the fix to the stable release> + + [Development Fix] + <fill me in with an explanation of how the bug has been addressed in the development branch, including the relevant version numbers of packages modified in order to implement the fix. > + + [Stable Fix] + <fill me in by pointing out a minimal patch applicable to the stable version of the package.> + + [Text Case] + <fill me in with detailed *instructions* on how to reproduce the bug. This will be used by people later on to verify the updated package fixes the problem.> + 1. + 2. + 3. + Broken Behavior: + Fixed Behavior: + + [Regression Potential] + <fill me in with a discussion of likelihood and potential severity of regressions and how users could get inadvertently affected.> + + [Original Report] + + consolekit can't find dbus-1 when cross-building: From the build log: http://people.linaro.org/~wookey/buildd/precise/sbuild-ma/consolekit_0.4.5-2-precise-ma-cross-armel-20120417-025041.38177.log Package dbus-1 was not found in the pkg-config search path. Perhaps you should add the directory containing `dbus-1.pc' to the PKG_CONFIG_PATH environment variable No package 'dbus-1' found Error: Couldn't determine the version of your DBUS package. This turns out to be because a local test in configure.ac used hard- coded 'pkg-config' instead of $PKG_CONFIG which autoconf has set to the correct path (/usr/bin/<triplet>-pkg-config) (This patch is not sufficient to cross-build this package which has other issues). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/984962 Title: Uses wrong pkg-config for dbus test when cross-building To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/consolekit/+bug/984962/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
