Re: Merb 1.1.0
Joshua Timberman dijo [Mon, Mar 29, 2010 at 01:23:20PM -0600]:
> Just wanted to note that I'm not planning on updating the Merb package
> for the latest release, 1.1.0 quite yet. Merb's existence in Debian is
> largely because of the dependency for Chef Server, and the WebUI
> component of Chef doesn't work with an internals change in Merb 1.1.0.
> Also, Merb switched to Yehuda Katz's bundler library for loading
> dependency libraries, so bundler needs to be packaged as well. I'll open
> a ticket for that and work on it later this week, unless someone wants to
> take that one before I get to it :-).
>
> We have ticket CHEF-1072 opened upstream[0] for this, and once complete
> I'll work to update the packaging.
Hi,
Let me suggest borrowing (yet another) common practice from the
pkg-perl group: If a group-maintained package is for some
not-always-obvious reason not ready for an update, add a note stating
so in the changelog (of course, making it an obviously illegal
changelog entry). As an example, I am committing this:
pkg-ruby-extras/trunk/merb$ svn diff
Index: debian/changelog
===================================================================
--- debian/changelog (revision 5077)
+++ debian/changelog (working copy)
@@ -1,3 +1,11 @@
+merb (1.1.0-1) UNRELEASED; urgency=low
+
+As per maintainer (Joshua Timberman) request, this package should _NOT_
+be updated to 1.1.0 as it breaks related tools.
+Message-ID: <8C338B42-C662-49E3-99CB-F0B2C4026061@opscode.com>
+
+ -- Gunnar Wolf <gwolf@debian.org> Fri, 09 Apr 2010 19:01:09 -0500
+
merb (1.0.12+dfsg-4) unstable; urgency=low
* Add merb-param-protection package.
Of course, this illegal changelog entry should be removed when
needed. Do you like the idea of using the changelog for this kind of
information?
--
Gunnar Wolf • gwolf@gwolf.org • (+52-55)5623-0154 / 1451-2244
Reply to: