Steve Langasek wrote:
> Very strange. What does 'apt-cache policy gconf2' show? Does apt-get
> update change anything?
>
client:/home/blackm# apt-cache policy gconf2
gconf2:
Installed: (none)
Candidate: (none)
Package pin: (not found)
Version table:
2.12.1-8 1000
500 ftp://
On Sun, Jan 15, 2006 at 12:05:27PM +0100, Martin Lohmeier wrote:
> Steve Langasek wrote:
> > On Sun, Jan 15, 2006 at 11:17:22AM +0100, Martin Lohmeier wrote:
> >>Package: gksu
> >>Version: 1.3.6-1
> >>Severity: grave
> >>Justification: renders package unusable
> >>gksu depend on gconf2 which has
Steve Langasek wrote:
> On Sun, Jan 15, 2006 at 11:17:22AM +0100, Martin Lohmeier wrote:
>
>>Package: gksu
>>Version: 1.3.6-1
>>Severity: grave
>>Justification: renders package unusable
>
>
>>gksu depend on gconf2 which has been replaced by gconf2-common.
>
>
> How is this grave? There is sti
On Sun, Jan 15, 2006 at 11:17:22AM +0100, Martin Lohmeier wrote:
> Package: gksu
> Version: 1.3.6-1
> Severity: grave
> Justification: renders package unusable
> gksu depend on gconf2 which has been replaced by gconf2-common.
How is this grave? There is still a gconf2 binary package in unstable,
Package: gksu
Version: 1.3.6-1
Severity: grave
Justification: renders package unusable
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
gksu depend on gconf2 which has been replaced by gconf2-common.
bye, Martin
- -- System Information:
Debian Release: testing/unstable
APT prefers unstable
APT
5 matches
Mail list logo