public inbox for development@lists.ipfire.org
 help / color / mirror / Atom feed
From: Adolf Belka <adolf.belka@ipfire.org>
To: development@lists.ipfire.org
Subject: [PATCH 4/4] minidlna: bump PAK_VER due to ffmpeg library sobump
Date: Tue, 02 May 2023 19:54:00 +0200	[thread overview]
Message-ID: <20230502175400.3769686-4-adolf.belka@ipfire.org> (raw)
In-Reply-To: <20230502175400.3769686-1-adolf.belka@ipfire.org>

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

Signed-off-by: Adolf Belka <adolf.belka(a)ipfire.org>
---
 lfs/minidlna | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/lfs/minidlna b/lfs/minidlna
index 82a9d7f38..1ef104743 100644
--- a/lfs/minidlna
+++ b/lfs/minidlna
@@ -1,7 +1,7 @@
 ###############################################################################
 #                                                                             #
 # IPFire.org - A linux based firewall                                         #
-# Copyright (C) 2007-2021  IPFire Team  <info(a)ipfire.org>                     #
+# Copyright (C) 2007-2023  IPFire Team  <info(a)ipfire.org>                     #
 #                                                                             #
 # This program is free software: you can redistribute it and/or modify        #
 # it under the terms of the GNU General Public License as published by        #
@@ -34,7 +34,7 @@ DL_FROM    = $(URL_IPFIRE)
 DIR_APP    = $(DIR_SRC)/$(THISAPP)
 TARGET     = $(DIR_INFO)/$(THISAPP)
 PROG       = minidlna
-PAK_VER    = 11
+PAK_VER    = 12
 
 DEPS       = ffmpeg flac libexif libid3tag libogg
 
-- 
2.40.1


      parent reply	other threads:[~2023-05-02 17:54 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-05-02 17:53 [PATCH 1/4] ffmpeg: Update to version 6.0 Adolf Belka
2023-05-02 17:53 ` [PATCH 2/4] mpd: bump PAK_VER due to ffmpeg library sobump Adolf Belka
2023-05-02 17:53 ` [PATCH 3/4] shairport-sync: " Adolf Belka
2023-05-02 17:54 ` Adolf Belka [this message]

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=20230502175400.3769686-4-adolf.belka@ipfire.org \
    --to=adolf.belka@ipfire.org \
    --cc=development@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