From: Josh Marshall <joshua.r.marshall.1991@gmail.com>
To: Marius Bakke <mbakke@fastmail.com>
Cc: 41301@debbugs.gnu.org
Subject: bug#41301: Django 3 dependency: gettext
Date: Sat, 16 May 2020 10:39:42 -0400 [thread overview]
Message-ID: <CAFkJGRcbfmRsE-3mHt2SrS3-sHOrVL5BR1OqqaK+wbsQ4gK9Xg@mail.gmail.com> (raw)
In-Reply-To: <87blmot4j2.fsf@devup.no>
[-- Attachment #1: Type: text/plain, Size: 967 bytes --]
I just saw that lint said it was out of date. I'm doing this to track down
a dep tree to order my work in packaging and to become more familiar with
packaging.
On Sat, May 16, 2020, 09:04 Marius Bakke <mbakke@fastmail.com> wrote:
> Josh Marshall <joshua.r.marshall.1991@gmail.com> writes:
>
> > The following needs to be updated: gettext
>
> Why does it need to be updated? gettext 0.20.2 was released just a
> month ago[0], and Django runs on a wide range of distributions that
> surely has older versions.
>
> Updating gettext is also a full-rebuild change which means this will
> have to wait for the next "core-updates" branch.
>
> Note that if you really need the newer gettext, you can give Django a
> special variant like so without having to wait for core-updates:
>
> (define-public gettext-0.20.2
> (package
> (inherit gettext)
> (version "0.20.2")
> (source (origin ...))))
>
> 0: https://savannah.gnu.org/forum/forum.php?forum_id=9716
>
[-- Attachment #2: Type: text/html, Size: 1539 bytes --]
next prev parent reply other threads:[~2020-05-16 16:37 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-16 4:36 bug#41301: Django 3 dependency: gettext Josh Marshall
2020-05-16 13:04 ` Marius Bakke
2020-05-16 14:39 ` Josh Marshall [this message]
[not found] ` <handler.41301.B.158960517615651.ack@debbugs.gnu.org>
2020-05-16 20:29 ` bug#41301: Acknowledgement (Django 3 dependency: gettext) Josh Marshall
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=CAFkJGRcbfmRsE-3mHt2SrS3-sHOrVL5BR1OqqaK+wbsQ4gK9Xg@mail.gmail.com \
--to=joshua.r.marshall.1991@gmail.com \
--cc=41301@debbugs.gnu.org \
--cc=mbakke@fastmail.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.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.