On Monday, January 19, 2015 at 3:00:05 PM UTC+5:30, Lisi Reisz wrote:
> On Monday 19 January 2015 05:30:40 Rusi Mody wrote:
> > On Monday, January 19, 2015 at 10:50:04 AM UTC+5:30, Rusi Mody wrote:
> > > Running testing
> > >
> > > While trying to upgrade, listbugs was giving a bunch of
> > > critical/grave errors.
> > >
> > > Ran
> > > $ aptitude hold
> > >
> > > on all these packages then did upgrade.
> > >
> > > One of these packages was dpkg
> > >
> > > Now after upgrade tried running
> > > aptitude unhold dpkg
> > >
> > > However still...
> > >
> > > synaptic shows it as 1.17.13 both installed and latest
> > > and no upgradation possible
> > >
> > > https://packages.debian.org/jessie/dpkg
> > > shows it as 1.17.23
> >
> > Yeah synaptic and aptitude (and dpkg) dont mix too well
> > especially wrt pinning
> >
> > http://askubuntu.com/questions/18654/how-to-prevent-updating-of-a-specific-
> >package
> >
> > However cant find dpkg in aptitude(!!)
> > [Yeah I am not very adept at aptitude curses-gui]
> > Can only see
> > dpkg:i386
> > and
> > dpkg-repack
>
> $ aptitude search dpkg
>
> Any luck?
>
> # aptitude update
>
> $ aptitude search dpkg
>
> any luck?
This is what I get
i dpkg - Debian package management system
>
> Then I'd look at your sources.list.
Tried changing that -- no change in effect
Now
aptitude dist-upgrade
The following NEW packages will be installed:
dpkg:i386{ab} libbz2-1.0:i386{a} libjpeg62-turbo:i386{a} libsystemd0:i386{a}
some other stuff
The following packages have unmet dependencies:
dpkg : Conflicts: dpkg:i386 but 1.17.23 is to be installed.
dpkg:i386 : Conflicts: dpkg but 1.17.13 is installed.
So I can only conclude that aptitude sees the need to upgrade
from .13 to .23 but for some reason it cant 'get out' of the
installed dpkg:amd64
>
> Lisi
--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive:
https://lists.debian.org/eec793a2-8f0c-45bd-bfcc-ee0be3ec0...@googlegroups.com
