Your message dated Mon, 04 Jul 2016 12:43:00 +0000
with message-id <e1bk3di-00047c...@franck.debian.org>
and subject line Bug#824089: Removed package(s) from unstable
has caused the Debian Bug report #824089,
regarding golang-github-jonboulle-clockwork-dev and golang-clockwork-dev: error
when trying to install together
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
automatic installation tests of packages that share a file and at the
same time do not conflict by their package dependency relationships has
detected the following problem:
Selecting previously unselected package golang-src.
(Reading database ... 10961 files and directories currently installed.)
Preparing to unpack .../golang-src_2%3a1.6.1-2_amd64.deb ...
Unpacking golang-src (2:1.6.1-2) ...
Selecting previously unselected package golang-go.
Preparing to unpack .../golang-go_2%3a1.6.1-2_amd64.deb ...
Unpacking golang-go (2:1.6.1-2) ...
Selecting previously unselected package golang-clockwork-dev.
Preparing to unpack .../golang-clockwork-dev_0.0~git20141217-1_all.deb ...
Unpacking golang-clockwork-dev (0.0~git20141217-1) ...
Selecting previously unselected package golang-github-jonboulle-clockwork-dev.
Preparing to unpack
Unpacking golang-github-jonboulle-clockwork-dev (0.0~git20141217-3) ...
dpkg: error processing archive
trying to overwrite
is also in package golang-clockwork-dev 0.0~git20141217-1
Processing triggers for man-db (2.7.5-1) ...
Errors were encountered while processing:
E: Sub-process /usr/bin/dpkg returned an error code (1)
This is a serious bug as it makes installation fail, and violates
sections 7.6.1 and 10.1 of the policy. An optimal solution would
consist in only one of the packages installing that file, and renaming
or removing the file in the other package. Depending on the
circumstances you might also consider Replace relations or file
diversions. If the conflicting situation cannot be resolved then, as a
last resort, the two packages have to declare a mutual
Conflict. Please take into account that Replaces, Conflicts and
diversions should only be used when packages provide different
implementations for the same functionality.
Here is a list of files that are known to be shared by both packages
(according to the Contents file for sid/amd64, which may be
slightly out of sync):
This bug has been filed against both packages. If you, the maintainers of
the two packages in question, have agreed on which of the packages will
resolve the problem please reassign the bug to that package. You may then
also register in the BTS that the other package is affected by the bug.
PS: for more information about the detection of file overwrite errors
of this kind see http://qa.debian.org/dose/file-overwrites.html.
--- End Message ---
--- Begin Message ---
We believe that the bug you reported is now fixed; the following
package(s) have been removed from unstable:
golang-clockwork | 0.0~git20141217-1 | source
golang-clockwork-dev | 0.0~git20141217-1 | all
------------------- Reason -------------------
ROM; replaced by golang-github-jonboulle-clockwork
Note that the package(s) have simply been removed from the tag
database and may (or may not) still be in the pool; this is not a bug.
The package(s) will be physically removed automatically when no suite
references them (and in the case of source, when no binary references
it). Please also remember that the changes have been done on the
master archive and will not propagate to any mirrors until the next
dinstall run at the earliest.
Packages are usually not removed from testing by hand. Testing tracks
unstable and will automatically remove packages which were removed
from unstable when removing them from testing causes no dependency
problems. The release team can force a removal from testing if it is
really needed, please contact them if this should be the case.
We try to close bugs which have been reported against this package
automatically. But please check all old bugs, if they were closed
correctly or should have been re-assigned to another package.
Thank you for reporting the bug, which will now be closed. If you
have further comments please address them to 824...@bugs.debian.org.
The full log for this bug can be viewed at https://bugs.debian.org/824089
This message was generated automatically; if you believe that there is
a problem with it please contact the archive administrators by mailing
Debian distribution maintenance software
Paul Richards Tagliamonte (the ftpmaster behind the curtain)
--- End Message ---
Pkg-go-maintainers mailing list