From: John MacFarlane <jgm-TVLZxgkOlNX2fBVCVOL8/A@public.gmane.org>
To: pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
Subject: Re: Outdated package in `apt-get` (stuck at v1.16.0.2)
Date: Sun, 8 Oct 2017 21:16:47 -0700 [thread overview]
Message-ID: <20171009041647.GJ20728@Johns-MacBook-Pro.local> (raw)
In-Reply-To: <1c234eb5-3076-4528-93c1-e3feef9b632e-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
+++ Hazem AbuMostafa [Oct 08 17 20:55 ]:
> I get that, and that's how I install it usually.
> The question is if there's anyway to get the package in `apt` updated
> to this latest version.
It has to trickle up through the very careful process of
debian updates. This just takes a while, and it depends
a bit on how fast the debian maintainers react to a new
version.
next prev parent reply other threads:[~2017-10-09 4:16 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-09 2:24 Hazem AbuMostafa
[not found] ` <1e142d8b-959b-43f6-b3d2-59191bcd3e85-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2017-10-09 2:36 ` Ivan Lazar Miljenovic
[not found] ` <CA+u6gbzp_jf9rpAoXfcBMCp5Q4AmHPQzJjMXMkEdwSs8ARggpQ-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2017-10-09 2:54 ` Hazem AbuMostafa
[not found] ` <22906d3c-9395-40ba-873b-6989bdb307e3-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2017-10-09 3:33 ` Ivan Lazar Miljenovic
[not found] ` <CA+u6gbxnC5+Tz54azzeFh-fRu+TaAqtgVcTng1O1g-Uxj1fHQQ-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2017-10-09 3:48 ` John MacFarlane
[not found] ` <20171009034854.GE20728-9Rnp8PDaXcadBw3G0RLmbRFnWt+6NQIA@public.gmane.org>
2017-10-09 3:55 ` Hazem AbuMostafa
[not found] ` <1c234eb5-3076-4528-93c1-e3feef9b632e-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2017-10-09 4:16 ` John MacFarlane [this message]
2017-10-09 4:25 ` Ivan Lazar Miljenovic
[not found] ` <CA+u6gbxZt3=sz1=2dSY95P0i2GGQ7a=vzFpYzRHjeVcXu8DPMg-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2017-10-10 0:37 ` Hazem AbuMostafa
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=20171009041647.GJ20728@Johns-MacBook-Pro.local \
--to=jgm-tvlzxgkolnx2fbvcvol8/a@public.gmane.org \
--cc=pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org \
/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 NNTP newsgroup(s).