Re: RC:bug:debconf: unable to initialize frontend: Newt

To: Guddla Rupesh <rupeshforu3@gmail.com>
Cc: deity@lists.debian.org
Subject: Re: RC:bug:debconf: unable to initialize frontend: Newt
From: Daniel Hartwig <mandyke@gmail.com>
Date: Sun, 30 Jun 2013 15:23:48 +0800
Message-id: <[🔎] CAN3veRfnZ5jij399HH6-4RxW0uXARsVaoe9o0rjS7y0npBYfvQ@mail.gmail.com>
In-reply-to: <[🔎] CAOJioue9Ly6fGgtuE-ghA7ecEEjr8HKwOX+FgDzj6s-RCLjg5w@mail.gmail.com>
References: <CAOJioueOAs0VEkJUv6Lf-xqP3uQu_rJnwt5PkxD7LReubmOaWA@mail.gmail.com> <[🔎] CAOJioue9Ly6fGgtuE-ghA7ecEEjr8HKwOX+FgDzj6s-RCLjg5w@mail.gmail.com>

On 30 June 2013 10:44, Guddla Rupesh <rupeshforu3@gmail.com> wrote:
> previously also same thing happened so this time I have locked the package
> libnewt0.52 in synaptic but unfortunately it was installed while installing
> other package.

This version lock is only effective for synaptic; apt-get does not
know about it.  You should instead use ‘apt-mark hold libnewt0.52’
that all tools will notice.  See <http://bugs.debian.org/276655>.

Reply to:

References:
- RC:bug:debconf: unable to initialize frontend: Newt
  - From: Guddla Rupesh <rupeshforu3@gmail.com>

Prev by Date: RC:bug:debconf: unable to initialize frontend: Newt
Previous by thread: RC:bug:debconf: unable to initialize frontend: Newt
Index(es):
- Date
- Thread