crown-beach-config silently diverged from upstream

Bug #191063 reported by Steve Magoun
2
Affects Status Importance Assigned to Milestone
crown-beach-config (Ubuntu)
Fix Released
Undecided
Unassigned

Bug Description

crown-beach-config 0.17 is currently in hardy. It's different than crown-beach-config upstream at moblin.org, and there's no indication that this version doesn't match upstream (nor is there any indication that the version in Hardy is a fork of upstream). For example, crown-beach-config in Hardy includes a call to gconftool-2 in the postinst; there's no such call in the upstream version at moblin.org.

I think one of two things needs to happen:
1) crown-beach-config gets converted to a non-native package
2) crown-beach-config gets officially forked and has a name change to avoid confusion with the version at moblin.org

I assume #1 is the better option, since upstream is active.

Upstream has moved on to crown-beach-config 0.24, which should be considered for Hardy as part of the work in fixing this.

Revision history for this message
Loïc Minier (lool) wrote :

This bug was fixed in the package crown-beach-config - 0.28+repack-0ubuntu1
---------------
crown-beach-config (0.28+repack-0ubuntu1) hardy; urgency=low

  [ Steve Magoun ]
  [ Steve Kowalik]
  * Stop shipping hostname.sh again

  [ Steve Magoun]
  * Synchronize with the moblin release of 0.28, which is
    different than the 0.28 release in the Ubuntu Mobile PPA. (LP: #191063)
  * Convert to non-native package
  * Repack without upstream debian directory or git directory
  * Updated dependency on ume-config-common (LP: #191064)

  [ Loic Minier ]
  * Include #DEBHELPER# snippets in postrm.

 -- Steve Magoun <email address hidden> Tue, 04 Mar 2008 11:12:40 -0500

Changed in crown-beach-config:
status: New → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

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