Your message dated Sat, 15 Nov 2014 16:34:01 +0000
with message-id <e1xpgit-0003cx...@franck.debian.org>
and subject line Bug#769359: fixed in ruby-fog-sakuracloud 0.1.1-3
has caused the Debian Bug report #769359,
regarding ruby-fog-sakuracloud,ruby-fog: 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
immediately.)


-- 
769359: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=769359
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: ruby-fog-sakuracloud,ruby-fog
Version: 0.1.1-1
Severity: serious
Tags: sid
User: trei...@debian.org
Usertags: edos-file-overwrite

Architecture: amd64
Distribution: sid

Hi,

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 ruby-fog.
  Preparing to unpack .../ruby-fog_1.22.0-2_all.deb ...
  Unpacking ruby-fog (1.22.0-2) ...
  dpkg: error processing archive 
/var/cache/apt/archives/ruby-fog_1.22.0-2_all.deb (--unpack):
   trying to overwrite '/usr/lib/ruby/vendor_ruby/fog/sakuracloud/compute.rb', 
which is also in package ruby-fog-sakuracloud 0.1.1-1
  dpkg-deb: error: subprocess paste was killed by signal (Broken pipe)
  Errors were encountered while processing:
   /var/cache/apt/archives/ruby-fog_1.22.0-2_all.deb

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):

  usr/lib/ruby/vendor_ruby/fog/bin/sakuracloud.rb
  usr/lib/ruby/vendor_ruby/fog/sakuracloud.rb
  usr/lib/ruby/vendor_ruby/fog/sakuracloud/compute.rb
  usr/lib/ruby/vendor_ruby/fog/sakuracloud/models/compute/plan.rb
  usr/lib/ruby/vendor_ruby/fog/sakuracloud/models/compute/plans.rb
  usr/lib/ruby/vendor_ruby/fog/sakuracloud/models/compute/server.rb
  usr/lib/ruby/vendor_ruby/fog/sakuracloud/models/compute/servers.rb
  usr/lib/ruby/vendor_ruby/fog/sakuracloud/models/compute/ssh_key.rb
  usr/lib/ruby/vendor_ruby/fog/sakuracloud/models/compute/ssh_keys.rb
  usr/lib/ruby/vendor_ruby/fog/sakuracloud/models/compute/zone.rb
  usr/lib/ruby/vendor_ruby/fog/sakuracloud/models/compute/zones.rb
  usr/lib/ruby/vendor_ruby/fog/sakuracloud/models/volume/archive.rb
  usr/lib/ruby/vendor_ruby/fog/sakuracloud/models/volume/archives.rb
  usr/lib/ruby/vendor_ruby/fog/sakuracloud/models/volume/disk.rb
  usr/lib/ruby/vendor_ruby/fog/sakuracloud/models/volume/disks.rb
  usr/lib/ruby/vendor_ruby/fog/sakuracloud/models/volume/plan.rb
  usr/lib/ruby/vendor_ruby/fog/sakuracloud/models/volume/plans.rb
  usr/lib/ruby/vendor_ruby/fog/sakuracloud/requests/compute/boot_server.rb
  usr/lib/ruby/vendor_ruby/fog/sakuracloud/requests/compute/create_server.rb
  usr/lib/ruby/vendor_ruby/fog/sakuracloud/requests/compute/delete_server.rb
  usr/lib/ruby/vendor_ruby/fog/sakuracloud/requests/compute/list_plans.rb
  usr/lib/ruby/vendor_ruby/fog/sakuracloud/requests/compute/list_servers.rb
  usr/lib/ruby/vendor_ruby/fog/sakuracloud/requests/compute/list_ssh_keys.rb
  usr/lib/ruby/vendor_ruby/fog/sakuracloud/requests/compute/list_zones.rb
  usr/lib/ruby/vendor_ruby/fog/sakuracloud/requests/compute/stop_server.rb
  usr/lib/ruby/vendor_ruby/fog/sakuracloud/requests/volume/attach_disk.rb
  usr/lib/ruby/vendor_ruby/fog/sakuracloud/requests/volume/configure_disk.rb
  usr/lib/ruby/vendor_ruby/fog/sakuracloud/requests/volume/create_disk.rb
  usr/lib/ruby/vendor_ruby/fog/sakuracloud/requests/volume/delete_disk.rb
  usr/lib/ruby/vendor_ruby/fog/sakuracloud/requests/volume/list_archives.rb
  usr/lib/ruby/vendor_ruby/fog/sakuracloud/requests/volume/list_disks.rb
  usr/lib/ruby/vendor_ruby/fog/sakuracloud/requests/volume/list_plans.rb
  usr/lib/ruby/vendor_ruby/fog/sakuracloud/volume.rb

This bug is assigned to 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
also register in the BTS that the other package is affected by the bug.


Cheers,

Andreas

PS: for more information about the detection of file overwrite errors
of this kind see http://edos.debian.net/file-overwrites/.

Attachment: ruby-fog-sakuracloud=0.1.1-1_ruby-fog=1.22.0-2.log.gz
Description: application/gzip


--- End Message ---
--- Begin Message ---
Source: ruby-fog-sakuracloud
Source-Version: 0.1.1-3

We believe that the bug you reported is fixed in the latest version of
ruby-fog-sakuracloud, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 769...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Sebastien Badia <s...@sebian.fr> (supplier of updated ruby-fog-sakuracloud 
package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

Format: 1.8
Date: Sat, 15 Nov 2014 17:21:32 +0100
Source: ruby-fog-sakuracloud
Binary: ruby-fog-sakuracloud
Architecture: source all
Version: 0.1.1-3
Distribution: unstable
Urgency: medium
Maintainer: Debian Ruby Extras Maintainers 
<pkg-ruby-extras-maintain...@lists.alioth.debian.org>
Changed-By: Sebastien Badia <s...@sebian.fr>
Description:
 ruby-fog-sakuracloud - Module for the 'fog' gem to support Sakura no Cloud
Closes: 769359
Changes:
 ruby-fog-sakuracloud (0.1.1-3) unstable; urgency=medium
 .
   * Team upload.
   * Prevent installing ruby-fog-sakuracloud and ruby-fog
     together (Closes: 769359)
Checksums-Sha1:
 bb99b5f8ef49bfb895af108c376456ef0a37927f 1777 ruby-fog-sakuracloud_0.1.1-3.dsc
 c784e1d8354c91e846bb618a289b2cc6a1e6c2da 2192 
ruby-fog-sakuracloud_0.1.1-3.debian.tar.xz
 8970c501e80a7e99ced9909199bb7f5f9f1a1095 11364 
ruby-fog-sakuracloud_0.1.1-3_all.deb
Checksums-Sha256:
 d7f203897a6f62705b113e341472a894f61f3ab843da7bcc953f304f3a8bb911 1777 
ruby-fog-sakuracloud_0.1.1-3.dsc
 0bee359311678401e532f43500e74ee75837238a183a1ff3322bfe11dd2da212 2192 
ruby-fog-sakuracloud_0.1.1-3.debian.tar.xz
 807e0d0e0b86f0b5696a613a9cfb3ec7fa0707c997736d843e93190498352c45 11364 
ruby-fog-sakuracloud_0.1.1-3_all.deb
Files:
 8374ec666d70f22e021f8194b88972d6 1777 ruby optional 
ruby-fog-sakuracloud_0.1.1-3.dsc
 97b9ab878c12da7aa7d3000a7c649c39 2192 ruby optional 
ruby-fog-sakuracloud_0.1.1-3.debian.tar.xz
 a74dbda55aaa81f08337dd888c7ca373 11364 ruby optional 
ruby-fog-sakuracloud_0.1.1-3_all.deb

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1

iQEcBAEBCAAGBQJUZ37pAAoJEImvgrc5zSF6YdsIAJuOvL58pGGn5UmPKyL8YoZN
YTBiOO1JOzV+aCqrDy5isrGS97VhXQROccueMK9Z3JefK50aaTMzV3vFU7pfXQu0
R43eSc9OSq3kPRaN/+BLod9cEBfGJ+8Rtzh+iDuLyR7teOO3BSWZ81BsHCUFf0PB
WDDB1ORpvVa7/NAoSJrEvewhHtyHL6vwxTbVNEIe4atuLZziHhvujdpMdS4XouSx
qko6n3idgczy1tpoPwvG80TL38ClxLlmmykkRJk+TC64kEGzvuc8tprv5J6zrQ68
GF0Z/ZMuJVKCXyIqrPg8nSODEnqC0rcwHo5vFPi/8BTR8vk/AiQ72YuxLEAGXZs=
=+pmg
-----END PGP SIGNATURE-----

--- End Message ---

Reply via email to