public inbox for ipfire-scm@lists.ipfire.org
 help / color / mirror / Atom feed
From: "Peter Müller" <git@ipfire.org>
To: ipfire-scm@lists.ipfire.org
Subject: [git.ipfire.org] IPFire 2.x development tree branch, next, updated. 9ce9514bad8109a9ffa0f4206a7668757221287c
Date: Sun, 21 Apr 2024 20:09:51 +0000	[thread overview]
Message-ID: <4VMzxq1kRdz2xSL@people01.haj.ipfire.org> (raw)

[-- Attachment #1: Type: text/plain, Size: 2077 bytes --]

This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project "IPFire 2.x development tree".

The branch, next has been updated
       via  9ce9514bad8109a9ffa0f4206a7668757221287c (commit)
      from  658e1675f7da0d7d02216a083f71e34d4eeabd5e (commit)

Those revisions listed above that are new to this repository have
not appeared on any other notification email; so we list those
revisions in full, below.

- Log -----------------------------------------------------------------
commit 9ce9514bad8109a9ffa0f4206a7668757221287c
Author: Peter Müller <peter.mueller(a)ipfire.org>
Date:   Sun Apr 21 20:09:40 2024 +0000

    libloc: Adjust changed URL format
    
    Signed-off-by: Peter Müller <peter.mueller(a)ipfire.org>

-----------------------------------------------------------------------

Summary of changes:
 lfs/libloc | 3 ++-
 1 file changed, 2 insertions(+), 1 deletion(-)

Difference in files:
diff --git a/lfs/libloc b/lfs/libloc
index ddd38e941..8e753672a 100644
--- a/lfs/libloc
+++ b/lfs/libloc
@@ -26,6 +26,7 @@ include Config
 
 VER        = 0.9.17
 DB_DATE    = 2024-04-16
+DB_TIME    = 03:45
 
 THISAPP    = libloc-$(VER)
 DL_FILE    = $(THISAPP).tar.gz
@@ -41,7 +42,7 @@ objects = $(DL_FILE) \
 	location-$(DB_DATE).db.xz
 
 $(DL_FILE)                    = https://source.ipfire.org/releases/libloc/$(DL_FILE)
-location-$(DB_DATE).db.xz     = https://location.ipfire.org/databases/1/archive/location-$(DB_DATE).db.xz
+location-$(DB_DATE).db.xz     = https://location.ipfire.org/databases/1/archive/location-$(DB_DATE)-$(DB_TIME).db.xz
 
 $(DL_FILE)_BLAKE2 = b0bf860ebaccd3cb49c58c066c430f7a1f936a2029957db9b88e22c04240af0268a8f6388e8ca512102f14033037a2ab8bbb93fe83e525b9859c790c5c382df4
 location-$(DB_DATE).db.xz_BLAKE2 = f60ca7c2e3ac7cb7e6dc94501f0028dfb76f65330ba4f35934addc65bac8af9b3ce0149956aa3ca9211c9843b34d94255328af840d250f1e4612d9af90e7b6e9


hooks/post-receive
--
IPFire 2.x development tree

                 reply	other threads:[~2024-04-21 20:09 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=4VMzxq1kRdz2xSL@people01.haj.ipfire.org \
    --to=git@ipfire.org \
    --cc=ipfire-scm@lists.ipfire.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