Your message dated Fri, 19 Aug 2011 18:50:08 +0200
with message-id <[email protected]>
and subject line Re: Bug#240092: any plans to address this?
has caused the Debian Bug report #240092,
regarding dpkg: lockfile location
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 [email protected]
immediately.)


-- 
240092: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=240092
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: dpkg
Version: 1.10.20
Severity: wishlist


What about moving, or at least linking, the default location for the
dpkg lockfile from /var/lib/dpkg/lock to /var/lock/ ?


-- System Information:
Debian Release: testing/unstable
  APT prefers unstable
  APT policy: (500, 'unstable')
Architecture: i386 (i686)
Kernel: Linux 2.6.4
Locale: LANG=de_DE@euro, LC_CTYPE=de_DE@euro

Versions of packages dpkg depends on:
ii  dselect                     1.10.20      a user tool to manage Debian packa
ii  libc6                       2.3.2.ds1-11 GNU C Library: Shared libraries an

-- no debconf information


--- End Message ---
--- Begin Message ---
On Fri, 2011-08-19 at 18:35:01 +0200, martin f krafft wrote:
> also sprach Guillem Jover <[email protected]> [2011.08.19.1425 +0200]:
> > I've pondered about this bug report for some time now, and I don't
> > really see the point in it. Conformance for conformance sake? What's
> > gained by moving the lock files to /var/lock?
> 
> I think my main driver back then was that /var/lock was auto-ignored
> by backup software, and I've run into the problem that after
> a restore, I had to manually remove the lockfile, since it was
> included in the backup.

Oh, but then dpkg never tries to remove the lock file, it will create
it if missing though, so you should not need to do that either.

> Wontfix is fine by me. Thank you for considering this old bug!

Ok, then I'm closing it with this mail.

regards,
guillem


--- End Message ---

Reply via email to