please merge hdapsd 1:20090401-1 from Debian/Sid

Bug #300814 reported by Evgeni Golov
38
This bug affects 3 people
Affects Status Importance Assigned to Milestone
hdapsd (Ubuntu)
Fix Released
Undecided
MOTU

Bug Description

Binary package hint: hdapsd

Hey,

please sync hdapsd 1:0.0.20081004-1 from Debian with the attached diff ontop.
This version is currently only in experimental because we are in freeze for Lenny and no new upstreams should be uploaded to unstable in that time. It's stable and should go to jaunty without problems.

This releases fixes #218072 in the Debian version and #258342 in the attached Ubuntu-version.

regards
Evgeni

Tags: upgrade

Related branches

Revision history for this message
Evgeni Golov (evgeni) wrote :
Revision history for this message
Jonas Pedersen (jonasped) wrote :

A new version is available in Debian/Experimental. Please sync 1:20090129-1 from Debian/Experimental. Attached debdiff includes Evgenis changes as well as a change to run "udevadm trigger --action=change" after installation. This is to ensure that udev rule is applied.

Revision history for this message
Emilio Pozuelo Monfort (pochu) wrote :

You should subscribe the sponsors team per https://wiki.ubuntu.com/SponsorshipProcess

Changed in hdapsd:
status: New → Confirmed
Revision history for this message
Luke Yelavich (themuso) wrote : Re: please sync hdapsd 1:0.0.20081004-1 from Debian/experimental

This is in fact a merge, and the latest debdiff is not complete, due to the update being a merge. The previous changelog entries from Ubuntu are not present, and one of the changes itself at least, is not present either. Please see http://wiki.ubuntu.com/Merging for a starting point on what a merge is, and how you do one. There are likely other useful documents on the wiki about merging, but I don't have the URLs to hand at the moment.

Revision history for this message
Jonas Pedersen (jonasped) wrote :

Agree with the missing changelog entries. Regarding one of the Ubuntu chages, are you referring to "Breaks: udev (<< 136-1)" and "Build-Depends: debhelper (>= 7.0.17ubuntu2)"? Is that needed as only newer or same versions are available in Jaunty? If not please let me know which change you are referring to.

Revision history for this message
Jonas Pedersen (jonasped) wrote :

Not recieved any comments on above, so have created a new debdiff that includes breaks and build-depends to be on the safe side. Please see attached debdiff and consider including new version in Jaunty.

Revision history for this message
Evgeni Golov (evgeni) wrote : Re: [Bug 300814] Re: please sync hdapsd 1:0.0.20081004-1 from Debian/experimental

On Thu, 26 Feb 2009 20:24:41 -0000 Jonas Pedersen wrote:

> Breaks: udev (<< 136-1)

Shouldn't that be Conflicts: udev (...)?
For anything else: ACK from me.

Regards

--
Bruce Schneier Fact Number 372:
Bruce Schneier is the Bombe

Revision history for this message
Jonas Pedersen (jonasped) wrote : Re: [Bug 300814] Re: please sync hdapsd 1:0.0.20081004-1 from Debian/experimental

Evgeni Golov wrote:
> On Thu, 26 Feb 2009 20:24:41 -0000 Jonas Pedersen wrote:
>
>> Breaks: udev (<< 136-1)
>
> Shouldn't that be Conflicts: udev (...)?

I don't think so. I just copied the Breaks part from the existing
version in Ubuntu. Looked at bit in the documentation and below quotes
are from the documentation.

"A Conflicts entry should almost never have an "earlier than" version
clause. This would prevent dpkg from upgrading or installing the package
which declared such a conflict until the upgrade or removal of the
conflicted-with package had been completed. Instead, Breaks may be used
(once Breaks is supported by the stable release of Debian). "

Above is from the Conflicts parts. This Breaks have an "earlier than" part.

"Normally a Breaks entry will have an "earlier than" version clause;
such a Breaks is introduced in the version of an (implicit or explicit)
dependency which violates an assumption or reveals a bug in earlier
versions of the broken package. This use of Breaks will inform
higher-level package management tools that broken package must be
upgraded before the new one. "

And above is from the Breaks part of the debian-policy documentation.

Revision history for this message
Jonas Pedersen (jonasped) wrote : Re: please sync hdapsd 1:0.0.20081004-1 from Debian/experimental

Any chance to get this sponsored before Jaunty release?

Revision history for this message
Peter Meiser (meiser79) wrote :

Please sync latest version from debian unstable, version 20090401-1.

Revision history for this message
Stefan Hammer (j-4-deactivatedaccount) wrote :

Yes, please sync this version, the current version is fairly old and doesn't work with newer thinkpads.
And everybody likes to have hdaps working with the new kernel!

Changed in hdapsd (Ubuntu):
assignee: nobody → motu
Revision history for this message
Evgeni Golov (evgeni) wrote :

The latest version in Debian only needs the drop of "Recommends: tp-smapi-modules" (#258342) to fit perfectly into Ubuntu. The udev/debhelper dance isn't needed, as we don't ship the udev rule anymore.

Please sync ASAP.
Without the sync, Karmic users won't have working HDAPS at all.

summary: - please sync hdapsd 1:0.0.20081004-1 from Debian/experimental
+ please sync hdapsd 1:20090401-1 from Debian/Sid
Revision history for this message
Evgeni Golov (evgeni) wrote : Re: please sync hdapsd 1:20090401-1 from Debian/Sid

Attached is a debdiff for a merge as requested by ajmitch and directhex on IRC.

summary: - please sync hdapsd 1:20090401-1 from Debian/Sid
+ please merge hdapsd 1:20090401-1 from Debian/Sid
Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package hdapsd - 1:20090401-1ubuntu1

---------------
hdapsd (1:20090401-1ubuntu1) karmic; urgency=low

  * Merge with Debian (LP: #300814).
  * debian/control:
    + Drop Recommends on tp-smapi-modules, Ubuntu doesn't have these.
      (LP: #258342)
    + Add lpia to the list of Architectures.

 -- Evgeni Golov <email address hidden> Tue, 16 Jun 2009 01:48:11 +0200

Changed in hdapsd (Ubuntu):
status: Confirmed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.