Fix a broken call to new_protect_filename for bug #147010. This is a regression...
authorZac Medico <zmedico@gentoo.org>
Sun, 10 Sep 2006 21:34:27 +0000 (21:34 -0000)
committerZac Medico <zmedico@gentoo.org>
Sun, 10 Sep 2006 21:34:27 +0000 (21:34 -0000)
svn path=/main/trunk/; revision=4433

pym/portage_update.py

index 2d61e6a75706c3a94178b7228616f0e19a4b802e..0184f04e3659cd0a0888a9ca1efb754b186d9f51 100644 (file)
@@ -193,7 +193,7 @@ def update_config_files(config_root, protect, protect_mask, update_iter):
        for x in update_files:
                updating_file = os.path.join(abs_user_config, x)
                if protect_obj.isprotected(updating_file):
-                       updating_file = new_protect_filename(updating_file)[0]
+                       updating_file = new_protect_filename(updating_file)
                try:
                        write_atomic(updating_file, "".join(file_contents[x]))
                except PortageException, e: