tag 731730 pending
thanks

Hello,

Bug #731730 reported by you has been fixed in the Git repository. You can
see the changelog below, and you can check the diff of the fix at:

    http://git.debian.org/?p=dpkg/dpkg.git;a=commitdiff;h=5177119

---
commit 5177119c68b19154d091d0455b89db722686fbca
Author: Guillem Jover <[email protected]>
Date:   Tue Dec 10 07:07:25 2013 +0100

    dpkg-maintscript-helper: Fix symlink_to_dir and dir_to_symlink commands
    
    - Always run postinst code regardless of prior-version, as the package
      might have been never configured before.
    - Be more strict when checking the expected state of paths.
    - Rename subcommand shell code to check-files-ownership.
    - Change dir_to_symlink switch code to use a staging empty directory,
      to avoid dpkg removing files from other packages, when removing the
      package old files during upgrade.
    - Bump minimal version in man page to 1.17.5.
    
    Closes: #731730

diff --git a/debian/changelog b/debian/changelog
index 045b136..fac2c5d 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -9,6 +9,16 @@ dpkg (1.17.5) UNRELEASED; urgency=low
   * Fix segfault in update-alternatives when adding or renaming slaves for
     an existing alternative. Regression introduced in dpkg 1.17.2.
     Closes: #731710
+  * Fix dpkg-maintscript-helper symlink_to_dir and dir_to_symlink commands:
+    - Always run postinst code regardless of prior-version, as the package
+      might have been never configured before.
+    - Be more strict when checking the expected state of paths.
+    - Rename subcommand shell code to check-files-ownership.
+    - Change dir_to_symlink switch code to use a staging empty directory,
+      to avoid dpkg removing files from other packages, when removing the
+      package old files during upgrade.
+    - Bump minimal version in man page to 1.17.5.
+    Closes: #731730
 
   [ Updated dpkg translations ]
   * German (Sven Joachim).


-- 
To UNSUBSCRIBE, email to [email protected]
with a subject of "unsubscribe". Trouble? Contact [email protected]

Reply via email to