Please sync libgnucrypto-java (main) from unstabl

Bug #54771 reported by Martin Pitt
6
Affects Status Importance Assigned to Milestone
libgnucrypto-java (Ubuntu)
Invalid
Undecided
Unassigned

Bug Description

 affects distros/ubuntu/libgnucrypto-java
 status confirmed
 subscribe ubuntu-archive

Please sync libgnucrypto-java (main) from Debian unstable.

Overriding Ubuntu changes is ok.

Changelog since current edgy version 2.0.1-6ubuntu1:

 libgnucrypto-java (2.0.1-7) unstable; urgency=low

   * using java-gcj-compat-dev to build (closes: #377065).
   * split build-dep-indep and build-depends.

Revision history for this message
Scott James Remnant (Canonical) (canonical-scott) wrote :

Requires confirmation from the release team

Changed in libgnucrypto-java:
status: Confirmed → Needs Info
Revision history for this message
Martin Pitt (pitti) wrote :

Why does it need a confirmation? It's not a new upstream version and the only change is the adoption of our current delta, so that we get back in sync again.

Revision history for this message
Martin Pitt (pitti) wrote :

Setting back from needsinfo to confirmed, since RM approval is not necessary. (see Matt's comment in bug 54769).

Changed in libgnucrypto-java:
status: Needs Info → Confirmed
Revision history for this message
Scott James Remnant (Canonical) (canonical-scott) wrote :

Needs a manual merge

E: libgnucrypto-java_2.0.1-7.diff.gz: md5sum check failed (5a61ee476d3ffa60c360a955949993ff [actual] vs. e3cecfaf4aae89aa73bf4b37f953aea6 [expected]).

Changed in libgnucrypto-java:
status: Confirmed → Rejected
Revision history for this message
Martin Pitt (pitti) wrote : Re: [Bug 54771] Re: Please sync libgnucrypto-java (main) from unstabl

Hi,

Scott James Remnant [2006-08-08 6:38 -0000]:
> Needs a manual merge
>
> E: libgnucrypto-java_2.0.1-7.diff.gz: md5sum check failed
> (5a61ee476d3ffa60c360a955949993ff [actual] vs.
> e3cecfaf4aae89aa73bf4b37f953aea6 [expected]).

Strange, taking Debian's diff.gz/dsc and our orig.tar.gz worked just
fine. I did a manual sync, though.

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.