maxb at f2s.com
Tue Mar 24 07:53:52 GMT 2009
Charlie Smotherman wrote:
> I have a little problem that I need some help with. I just update the
> python-coherence package Bug #338408. As you can tell from the bug I
> collaborated with the Debian Maintainer to update the package in Debian
> first. During this collaboration I used a bzr branch to keep track of
> what changes I made to the package and referred upstream to it along
> with attaching a debdiff to the bug for upstream and for the
> MOTU-release team.
> It has come to my attention the the package is now broken and several
> bugs have been filed against it. This is the culprit
> Setting up python-coherence (0.6.2-1) ...
> file does not exist:
> During the package update Lintian complained of MochiKit.js as being a
> violation of policy 4.13 so I took steps to correct this. As part of
> correcting this problem I add debian/links to link to the package
> libjs-mochikit. If you look at the attached branch and the attached
> debdiff on Bug #338408 you will notice that debian/links reads
> The branch is what I used to build and test with, upstream was also
> using the branch to help and advise me. Once upstream (debian
> maintainer) was satisfied, he told me that he would upload the branch.
> Now if you download the debian package and take a look at the diff.gz
> debian/links now reads:
> As you can tell this is *not* what I sent upstream to the debian
> My question is what would be the best course of action to correct this
> now broken package.
I don't understand, what's the problem with simply treating it the same
as any other bug in a Debian package, and reporting it to their BTS /
working with a Debian Developer to get a fix uploaded?
-------------- next part --------------
A non-text attachment was scrubbed...
Size: 197 bytes
Desc: OpenPGP digital signature
Url : https://lists.ubuntu.com/archives/ubuntu-motu/attachments/20090324/b3a4ae01/attachment.pgp
More information about the Ubuntu-motu