se($lockfh) || syserr(_g("cannot close %s"), "debian/control");
What is wrong with this patch? To me it looks OK.
I have limited knowledge on how dkpg uses the locking and what is protecting.
What I have difficult to understand is how the option -c will work without my
patch.
We use dpkg-gencontrol and supply a full path to "debian/control" with the -c
option. The full path to the control file is used, because dpkg-gencontrol is
not run from the directory where "debian/control" exists.
Do you have do run dpkg-gencontrol in the directory where "debian/control"
exists
The brief description (summary) should be "dpkg-dev: dpkg-gencontrol does NOT
use the control file specified with optin -c for the lock-file". I missed the
"not" when reported the bug.
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trou
Package: dpkg-dev
Version: 1.16.2
Severity: normal
Dear Maintainer,
The solution to Bug #642608 introduced another problem. The lock on the control
file always uses the file "debian/control".
The correct behavior should be to use the file specifed with the option -c.
/Mats
-- System Informat
4 matches
Mail list logo
