On 7/11/07, Daniel Burrows <[EMAIL PROTECTED]> wrote:
Yes, /var/lock/aptitude always exists. As I said before, it's not
necessary to remove it and aptitude contains no code to do so (so if it
was removed, it would be a bug!)
OK, understand now. This bug is fixed then with the patch.
--
Web:
On Tue, Jul 10, 2007 at 09:05:44PM +1200, Ian McDonald <[EMAIL PROTECTED]> was
heard to say:
> On 7/6/07, Daniel Burrows <[EMAIL PROTECTED]> wrote:
>>
>> This patch should fix your problem. If you can rebuild aptitude with
>> it applied and check whether it helps, that would be great.
>>
>> D
On 7/6/07, Daniel Burrows <[EMAIL PROTECTED]> wrote:
This patch should fix your problem. If you can rebuild aptitude with
it applied and check whether it helps, that would be great.
Daniel
The warning message goes away now but /var/lock/aptitude still exists
after exit.
--
Web: http://wa
On 7/6/07, Daniel Burrows <[EMAIL PROTECTED]> wrote:
This patch should fix your problem. If you can rebuild aptitude with
it applied and check whether it helps, that would be great.
Compiled and built. Waiting for problem to reoccur to see if fixed.
The way to reproduce (for me) is to try an
On Fri, Jul 06, 2007 at 09:39:20AM +1200, Ian McDonald <[EMAIL PROTECTED]> was
heard to say:
> When I do "sudo aptitude -PV upgrade" and it cannot get all the files I
> get this:
>
> W: Could not lock the cache file. Opening in read-only mode; any
> changes you make to the states of packages wil
Package: aptitude
Version: 0.4.5.4-1
Severity: important
When I do "sudo aptitude -PV upgrade" and it cannot get all the files I
get this:
W: Could not lock the cache file. Opening in read-only mode; any
changes you make to the states of packages will NOT be preserved!
immediately prior is this
6 matches
Mail list logo
