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. 149d8e83e5f547241a450ea0a68d8afac1e107fa
Date: Tue, 16 Aug 2022 15:36:30 +0000	[thread overview]
Message-ID: <4M6Zxp2cXGz2xp5@people01.haj.ipfire.org> (raw)

[-- Attachment #1: Type: text/plain, Size: 1583 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  149d8e83e5f547241a450ea0a68d8afac1e107fa (commit)
      from  f241a8c867b3f669a6eb561a33a8c4bfce3683ed (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 149d8e83e5f547241a450ea0a68d8afac1e107fa
Author: Arne Fitzenreiter <arne_f(a)ipfire.org>
Date:   Mon Aug 15 19:14:27 2022 +0200

    qemu: add alsa to dependency list
    
    qemu now links against libasound.so.2 so it need alsa to run.
    
    fixes: #12911
    
    Signed-off-by: Arne Fitzenreiter <arne_f(a)ipfire.org>
    Reviewed-by: Peter Müller <peter.mueller(a)ipfire.org>

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

Summary of changes:
 lfs/qemu | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

Difference in files:
diff --git a/lfs/qemu b/lfs/qemu
index 1edab05d1..cf31c4622 100644
--- a/lfs/qemu
+++ b/lfs/qemu
@@ -35,9 +35,9 @@ DL_FROM    = $(URL_IPFIRE)
 DIR_APP    = $(DIR_SRC)/$(THISAPP)
 TARGET     = $(DIR_INFO)/$(THISAPP)
 PROG       = qemu
-PAK_VER    = 33
+PAK_VER    = 34
 
-DEPS       = libusbredir spice libseccomp
+DEPS       = alsa libusbredir spice libseccomp
 
 SERVICES   =
 


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

                 reply	other threads:[~2022-08-16 15:36 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=4M6Zxp2cXGz2xp5@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