Ubuntu
python-coverage package

Please sync python-coverage 2.6-1 (universe) from Debian unstable (main)

Bug #173529 reported by Marco Rodrigues
6
Affects Status Importance Assigned to Milestone
python-coverage (Debian)
Fix Released
Unknown
python-coverage (Ubuntu)
Invalid
Wishlist
Unassigned

Bug Description

Binary package hint: python-coverage

Explanation of the Ubuntu delta and why it can be dropped:
The Ubuntu changes can be dropped because the package is now at Debian and with all Ubuntu changes merged and with debian python policy applied. It builds fine in Hardy pbuilder.

python-coverage (2.6-1) unstable; urgency=low

   * Initial version. Closes: #405230.

 -- Lars Wirzenius <email address hidden> Sun, 19 Aug 2007 22:53:59 +0300

Marco Rodrigues (gothicx)
Changed in python-coverage:
importance: Undecided → Wishlist
Revision history for this message
Daniel Holbach (dholbach) wrote :

This would overwrite the Ubuntu package, which is completely different. Please talk to the current Ubuntu maintainer before filing this bug.

Changed in python-coverage:
status: New → Incomplete
Revision history for this message
Elliot Murphy (statik) wrote :

This is fine with me, I only made the ubuntu package because there was not yet one in debian, and I did not find the time in recent months to look into contributing it to debian. It will be great to have a single package shared between debian and ubuntu for this.

Revision history for this message
Daniel Holbach (dholbach) wrote :

ACKed.

Changed in python-coverage:
status: Incomplete → Confirmed
Revision history for this message
Sebastien Bacher (seb128) wrote :

 [dpkg-source output:] dpkg-source: error: file python-coverage_2.6.orig.tar.gz has size 10514 instead of expected 10525

Changed in python-coverage:
status: Confirmed → Invalid
Revision history for this message
Marco Rodrigues (gothicx) wrote :

The debian one is correct...

The only difference between them is only when untar/gunzip, the ubuntu was changed because it unpacks to "python-coverage-2.6.orig" directory and debian to python-coverage-2.6. A diff -u against coverage.py (the only file inside the tarball) doesn't have any difference.

It can be synced without problems.

Changed in python-coverage:
status: Invalid → Confirmed
Revision history for this message
Daniel Holbach (dholbach) wrote :

Unfortunately it can't. The sync process will take our .tar.gz and the Debian .dsc and .diff.gz and will hiccup, because dpkg-source complains about it.

We either have to do a fake-sync (apply all Debian changes to our Tarball and call that 2.6-1ubuntu1) or wait until a new upstream version was packaged in Debian and sync that.

Cesare Tirabassi (norsetto)
Changed in python-coverage:
assignee: nobody → gothicx
status: Confirmed → In Progress
Bug Watch Updater (bug-watch-updater)
Changed in python-coverage:
status: Unknown → New
Revision history for this message
Martin Pitt (pitti) wrote :

Unsubscribing ubuntu-archive. This needs a fakesync (Ubuntu orig.tar.gz + debian's diff.gz, and a dch with just a build1 version suffix).

Marco Rodrigues (gothicx)
Changed in python-coverage:
status: In Progress → Triaged
Daniel Holbach (dholbach)
Changed in python-coverage:
assignee: gothicx → nobody
Bug Watch Updater (bug-watch-updater)
Changed in python-coverage:
status: New → Fix Released
Revision history for this message
Daniel Holbach (dholbach) wrote :

2.80-1 in Intrepid.

Changed in python-coverage:
status: Triaged → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

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