[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#538968: marked as done (Can't install grub-pc)

Your message dated Wed, 14 Sep 2011 21:25:57 +0200
with message-id <CAAZ6_fAEut3HAyK5xxJn3ZJykdJFkJojrMSeXOELPR9aCGHHyw@mail.gmail.com>
and subject line Close: Can't install grub-pc
has caused the Debian Bug report #538968,
regarding Can't install grub-pc
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 owner@bugs.debian.org
immediately.)


-- 
538968: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=538968
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Package: grub-pc
Severity: important

sh-3.2# apt-get install grub-pc
Reading package lists... Done
Building dependency tree       
Reading state information... Done
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:

The following packages have unmet dependencies:
  grub-pc: Depends: grub-common (= 1.96+20090709-1) but 1.96+20090725-1 is to be installed
  E: Broken packages
  sh-3.2# 



-- System Information:
Debian Release: squeeze/sid
  APT prefers unstable
  APT policy: (500, 'unstable'), (500, 'testing'), (500, 'stable')
Architecture: i386 (i686)

Kernel: Linux 2.6.30-1-686 (SMP w/2 CPU cores)
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash

--- End Message ---
--- Begin Message --- 
Given that the bug is from 2009 with all comments on the same
day the chance is very high that this was a temporary glitch.

Goswin von Brederlow already said why apt and aptitude can
generate different solutions while Felix Zielcke gave a good
explanation why you might not have the required version available
at that time. Considering this and that it is hardly reproducible
two years later i am closing this bugreport.

If it reappears - as always - feel free to reopen it, of course!


Best regards

David Kalnischkies

--- End Message ---
Reply to: