Apologies for not replying earlier -- I didn't get your reply because
mail to [EMAIL PROTECTED] does not automatically reach the submitter, just
the maintainer (but then noticed it while browsing the BTS).

Dave Beckett <[EMAIL PROTECTED]> writes:

> "When muine jumped the gun on gtk-sharp2 2.3.91, it did so only for
> i386; on other architectures, the autobuilders naturally continued to
> use 1.9.5. ..."
>
> nope.  It requires gtk-sharp2 1.9.2+ and was uploaded with that
> dependency in the build which is recorded in, for example, the i386 deb.
> Any 2.3.x series gtk-sharp2 appeared after the last muine was built.  If
> this fails to build muine, please report that as a bug explaining it
> or update this one.

My concern is with runtime dependencies, not build-dependencies -- the
issue is that gtk-sharp2's .clilibs files conservatively impose both a
minimum *and a maximum* version: e.g.,

libgtk2.0-cil (>= 1.9.5), libgtk2.0-cil (<< 1.9.6)

or

libgtk2.0-cil (>= 2.3.90), libgtk2.0-cil (<< 2.5.0)

When you built 0.8.3-7 on i386, you seem to have built it against
2.3.91, leading to #329906; the subsequent upload of gtk-sharp2 2.3.91
to unstable resolved that for i386, but left packages built for other
architectures, with dependencies on 1.9.6 or older, in the lurch.

> "... As such, could you please reupload the package, preferably
> with updated build-dependencies to be safe?"
> You don't say what to update.  require gtk-sharp2 1.9.x?

No, require 2.3.90 or newer, though I imagine all the buildds have
that by now anyway.

> Also your report was made on amd64 / x86_64 which is not a debian project
> architecture.  Please report bugs against an architecture that the project
> supports.

As the bottom of
http://qa.debian.org/debcheck.php?dist=unstable&package=muine
indicates, the official powerpc .deb has the same problem.  (There
appear to be no packages for any other architectures.)

-- 
Aaron M. Ucko, KB1CJC (amu at alum.mit.edu, ucko at debian.org)
Finger [EMAIL PROTECTED] (NOT a valid e-mail address) for more info.


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Reply via email to