2.80-1 in Intrepid.
** Changed in: python-coverage (Ubuntu)
Status: Triaged = Invalid
--
Please sync python-coverage 2.6-1 (universe) from Debian unstable (main)
https://bugs.launchpad.net/bugs/173529
You received this bug notification because you are a member of Ubuntu
Bugs, which is
** Changed in: python-coverage (Debian)
Status: New = Fix Released
--
Please sync python-coverage 2.6-1 (universe) from Debian unstable (main)
https://bugs.launchpad.net/bugs/173529
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Changed in: python-coverage (Ubuntu)
Assignee: Marco Rodrigues (gothicx) = (unassigned)
--
Please sync python-coverage 2.6-1 (universe) from Debian unstable (main)
https://bugs.launchpad.net/bugs/173529
You received this bug notification because you are a member of Ubuntu
Bugs, which is
** Changed in: python-coverage (Ubuntu)
Status: In Progress = Triaged
--
Please sync python-coverage 2.6-1 (universe) from Debian unstable (main)
https://bugs.launchpad.net/bugs/173529
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for
Unsubscribing ubuntu-archive. This needs a fakesync (Ubuntu orig.tar.gz
+ debian's diff.gz, and a dch with just a build1 version suffix).
--
Please sync python-coverage 2.6-1 (universe) from Debian unstable (main)
https://bugs.launchpad.net/bugs/173529
You received this bug notification because
** Changed in: python-coverage (Debian)
Status: Unknown = New
--
Please sync python-coverage 2.6-1 (universe) from Debian unstable (main)
https://bugs.launchpad.net/bugs/173529
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
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.
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
** Bug watch added: Debian Bug tracker #454982
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=454982
** Also affects: python-coverage (Debian) via
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=454982
Importance: Unknown
Status: Unknown
--
Please sync python-coverage 2.6-1
** Changed in: python-coverage (Ubuntu)
Assignee: (unassigned) = Marco Rodrigues (gothicx)
Status: Confirmed = In Progress
--
Please sync python-coverage 2.6-1 (universe) from Debian unstable (main)
https://bugs.launchpad.net/bugs/173529
You received this bug notification because you
[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 (Ubuntu)
Status: Confirmed = Invalid
--
Please sync python-coverage 2.6-1 (universe) from Debian unstable (main)
ACKed.
** Changed in: python-coverage (Ubuntu)
Status: Incomplete = Confirmed
--
Please sync python-coverage 2.6-1 (universe) from Debian unstable (main)
https://bugs.launchpad.net/bugs/173529
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug
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.
--
Please sync python-coverage
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 (Ubuntu)
Status: New = Incomplete
--
Please sync python-coverage 2.6-1 (universe) from Debian unstable (main)
14 matches
Mail list logo
