Hi,
When I try to apply your patch that was made for 3.2.12 in the current
3.2.21, it just fails:
z...@gplhost:buzzig>_ ~/sources/yum-3.2.21$ patch --dry-run -p1
<chroot_patch.diff
patching file debian/changelog
Hunk #1 FAILED at 1.
1 out of 1 hunk FAILED -- saving rejects to file debian/changelog.rej
patching file cli.py
Hunk #1 succeeded at 1176 (offset 123 lines).
Hunk #2 succeeded at 1217 (offset 136 lines).
patching file yum/__init__.py
Hunk #1 succeeded at 289 (offset 19 lines).
Hunk #2 succeeded at 1044 (offset 148 lines).
Hunk #3 FAILED at 1078.
1 out of 3 hunks FAILED -- saving rejects to file yum/__init__.py.rej
patching file yum/config.py
Hunk #1 succeeded at 588 with fuzz 2 (offset 25 lines).
Hunk #2 succeeded at 621 with fuzz 2 (offset 25 lines).
Hunk #3 succeeded at 797 (offset 46 lines).
patching file docs/yum.conf.5
Having a look at the patch itself, the first hunk that fails is the
debian/changelog patching, which is fine. If I remove it, then there is
only one fail. Now, if I apply the patch after removing the
debian/changelog hunk, here is what I got in the __init.py.rej:
***************
*** 1081,1089 ****
if self.conf.uid != 0:
return
- root = self.conf.installroot
- lockfile = root + '/' + lockfile # lock in the chroot
-
self._unlock(lockfile)
def _lock(self, filename, contents='', mode=0777):
--- 1078,1085 ----
if self.conf.uid != 0:
return
+ lockfile=self.conf.lockfile
+
self._unlock(lockfile)
def _lock(self, filename, contents='', mode=0777):
Would you be able to provide a patch against version 3.2.21? Is there
one that exists already somewhere? Also, why this has not been applied
in the upstream version, if this is a so old issue? (please answer to
all of these if you can, or let me know if you simply have no explanation)
Also, my plan was to have the current 3.2.21-1 debian release reach
lenny proposed-updates in order to fix the current breakage. Would you
feel acceptable to wait for this to happen before we fix this issue? Can
you live with this bug in the mean while? We could work on a version to
be sent to Experimental if you wish. Let me know your thoughts.
Thomas
--
To UNSUBSCRIBE, email to [email protected]
with a subject of "unsubscribe". Trouble? Contact [email protected]
