From: Linux for blind general discussion <blinux-list@redhat.com>
To: Linux for blind general discussion <blinux-list@redhat.com>
Subject: Re: working with nano
Date: Thu, 15 Jun 2017 13:08:49 -0400 (EDT) [thread overview]
Message-ID: <alpine.NEB.2.20.1706151306170.26559@panix1.panix.com> (raw)
In-Reply-To: <CAO2sX32ykMaqb3J2ntn+1gaJNv0wdB9xMrOGL_o_wCESAzBMxQ@mail.gmail.com>
archlinux has nano version 2.84 on it now.
Syntax for aptitude is first
aptitude update<cr> then
aptitude safe-upgrade<cr>
That should get you updates without breaking anything and will let you
know which packages were held back.
If you want to find out why packages were held back
aptitude why packagename<cr> ought to get that done.
On Thu, 15 Jun 2017,
Linux for
blind general discussion wrote:
> Date: Thu, 15 Jun 2017 10:11:58
> From: Linux for blind general discussion <blinux-list@redhat.com>
> To: blinux-list@redhat.com
> Subject: Re: working with nano
>
> I don't know which version of Debian you're running, but I just did
> some quick checks, and:
> Debian oldstable(Wheezy?) and Debian Stable(still Jessie for now
> though I believe Stretch is in Release Candidate) both offer a 2.2.6
> version of nano.
> Debian Testing, which is what I'm running, has a 2.7 version of Nano.
>
> I don't really follow Nano development, so I have no idea whey the
> version number changed so little during the previous Debian release
> cycle compared to the current one or what changed between 2.2 and 2.7.
>
>
--
next prev parent reply other threads:[~ UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
Linux for blind general discussion
` Linux for blind general discussion
` Linux for blind general discussion
` Linux for blind general discussion
` Linux for blind general discussion
` Linux for blind general discussion
` Linux for blind general discussion
` Linux for blind general discussion
` Linux for blind general discussion
` Linux for blind general discussion
` Linux for blind general discussion
` Linux for blind general discussion [this message]
` Linux for blind general discussion
` Linux for blind general discussion
` Linux for blind general discussion
` Linux for blind general discussion
` Linux for blind general discussion
` Linux for blind general discussion
` Linux for blind general discussion
` Linux for blind general discussion
` Linux for blind general discussion
-- strict thread matches above, loose matches on Subject: below --
Linux for blind general discussion
Linux for blind general discussion
` Linux for blind general discussion
Linux for blind general discussion
Linux for blind general discussion
` Linux for blind general discussion
Linux for blind general discussion
` Linux for blind general discussion
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=alpine.NEB.2.20.1706151306170.26559@panix1.panix.com \
--to=blinux-list@redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).