From: Tobias Geerinckx-Rice <me@tobias.gr>
To: arunisaac@systemreboot.net, 27657@debbugs.gnu.org
Subject: [bug#27657] Acknowledgement ([PATCH] gnu: graphviz: Update to 2.40.1.)
Date: Wed, 12 Jul 2017 00:02:09 +0200 [thread overview]
Message-ID: <0b3b89e9-c7ca-e0b5-ed1c-8354fcf9d60d@tobias.gr> (raw)
In-Reply-To: <ae7275b1.AEUAMrcZk4sAAAAAAAAAAAPUoLsAAAACwQwAAAAAAAW9WABZZUSF@mailjet.com>
[-- Attachment #1.1: Type: text/plain, Size: 839 bytes --]
Arun,
On 11/07/17 23:34, Arun Isaac wrote:
> Both appear to be the same tarball. I don't know why they have two
> copies on the server. Should we change the source URL of our package?
In general, dual-directory schemes like this — anything involving
‘current’ vs. ‘archive’ — often suggest that the project intends to
periodically prune the former.
For example, they might keep only the latest release of a series and
move the rest to an ‘archive’ directory. Therefore, it's common to use
the latter directly, or hedge our bets by trying both.
The ‘sudo’ package is a good example of this.
In this case, as you've no doubt already noticed, both directories are
identical. I'd say: before changing anything, ask upstream why they do
this and which URI we should prefer.
Kind regards,
T G-R
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 504 bytes --]
next prev parent reply other threads:[~2017-07-11 22:01 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-11 21:21 [bug#27657] [PATCH] gnu: graphviz: Update to 2.40.1 Arun Isaac
[not found] ` <handler.27657.B.149980812621470.ack@debbugs.gnu.org>
2017-07-11 21:34 ` [bug#27657] Acknowledgement ([PATCH] gnu: graphviz: Update to 2.40.1.) Arun Isaac
2017-07-11 22:02 ` Tobias Geerinckx-Rice [this message]
2017-07-11 22:07 ` Marius Bakke
2017-07-12 14:32 ` Arun Isaac
2017-07-11 21:52 ` [bug#27657] [PATCH] gnu: graphviz: Update to 2.40.1 Marius Bakke
2017-07-12 12:19 ` Ludovic Courtès
2017-07-12 14:44 ` Arun Isaac
[not found] ` <6e577250.AEQAM_HdOgAAAAAAAAAAAAOzWv8AAAACwQwAAAAAAAW9WABZZjXO@mailjet.com>
2017-07-12 20:48 ` Ludovic Courtès
2017-07-14 11:15 ` Arun Isaac
2017-07-14 13:58 ` Leo Famulari
2017-07-14 14:16 ` Arun Isaac
2017-07-12 14:41 ` Arun Isaac
2017-07-12 14:25 ` [bug#27657] [PATCH 1/3] gnu: graphviz: Use modify-phases Arun Isaac
2017-07-12 20:07 ` Marius Bakke
2017-07-14 11:37 ` [bug#27657] [PATCH] gnu: graphviz: Remove unnecessary inputs Arun Isaac
2017-07-17 9:31 ` Ludovic Courtès
2017-07-20 1:38 ` Arun Isaac
[not found] ` <cc8cb77c.ADkAACVAtRsAAAAAAAAAAAOzWv8AAAACwQwAAAAAAAW9WABZcAmW@mailjet.com>
2017-07-20 8:32 ` Ludovic Courtès
2017-07-20 1:35 ` [bug#27657] [PATCH] gnu: wayland: Improve fix-graphviz phase Arun Isaac
2017-07-20 8:34 ` Ludovic Courtès
2017-07-20 14:13 ` bug#27657: " Arun Isaac
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
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=0b3b89e9-c7ca-e0b5-ed1c-8354fcf9d60d@tobias.gr \
--to=me@tobias.gr \
--cc=27657@debbugs.gnu.org \
--cc=arunisaac@systemreboot.net \
/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 public inbox
https://git.savannah.gnu.org/cgit/guix.git
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).