unofficial mirror of bug-guix@gnu.org 
 help / color / mirror / code / Atom feed
From: ludo@gnu.org (Ludovic Courtès)
To: Hartmut Goebel <h.goebel@crazy-compilers.com>
Cc: 25020@debbugs.gnu.org
Subject: bug#25020: guix refresh does not discover updates if URLs are "non-standard"
Date: Tue, 24 Jan 2017 14:15:35 +0100	[thread overview]
Message-ID: <8760l4sio8.fsf@gnu.org> (raw)
In-Reply-To: <588712AE.60205@crazy-compilers.com> (Hartmut Goebel's message of "Tue, 24 Jan 2017 09:39:10 +0100")

Hartmut Goebel <h.goebel@crazy-compilers.com> skribis:

> Am 23.01.2017 um 23:14 schrieb Ludovic Courtès:
>> > Fixed for oxygen-icons in commit
>> > 683c5ab70accb909697717bb61741a7692c52c09.
>
> For  oxygen-icons  (those with a number behind the name), refresh works.
>
>
> For "kross" (additional directory level), it does not. Kross is still in
> my work-pipeline, so here is the WIP (stripped down):
>
> (define-public kross
>   (package
>     (name "kross")
>     (version "5.28.0")
>     (source
>      (origin
>        (method url-fetch)
>        (uri (string-append
>              "mirror://kde/stable/frameworks/"
>              (version-major+minor version) "/portingAids/"
>              name "-" version ".tar.xz"))

I see.

I suggest that we address it by specifying an ‘ftp-directory’ package
property in this case, just like the GNU updater does.

We’ll see once kross is committed.

Thanks for the clarification!

Ludo’.

  reply	other threads:[~2017-01-24 13:16 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <58372A9C.2000205@goebel-consult.de>
2016-11-26  2:52 ` bug#25020: guix refresh does not discover updates if URLs are "non-standard" Glenn Morris
2016-11-29 15:15   ` Ludovic Courtès
2017-01-23 22:14     ` Ludovic Courtès
2017-01-24  8:39       ` Hartmut Goebel
2017-01-24 13:15         ` Ludovic Courtès [this message]
2017-11-24 17:50           ` Ludovic Courtès

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=8760l4sio8.fsf@gnu.org \
    --to=ludo@gnu.org \
    --cc=25020@debbugs.gnu.org \
    --cc=h.goebel@crazy-compilers.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 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).