From: Michael Tremer <michael.tremer@ipfire.org>
To: development@lists.ipfire.org
Subject: Re: IPFire 2.29 - Core Update 185 is available for testing
Date: Mon, 25 Mar 2024 11:12:46 +0000 [thread overview]
Message-ID: <D6271D26-31DB-4217-A59E-74C9C7250EEB@ipfire.org> (raw)
In-Reply-To: <30039094-2c9a-45da-8ee7-d85ea2712868@ipfire.org>
[-- Attachment #1: Type: text/plain, Size: 2016 bytes --]
Hello Adolf,
I also slightly cramp when I see emails regarding to these announcements.
But this isn’t a big problem at all. It is an add-ons so we don’t even have to touch the updater.
-Michael
> On 25 Mar 2024, at 11:10, Adolf Belka <adolf.belka(a)ipfire.org> wrote:
>
> Hi Michael,
>
> First issue found. Due to a boo-boo made by me related to wsdd.
>
> I had submitted what I thought was a patch set for the samba initscript together with an update of the samba lfs file to add wsdd as a dependency. Unfortunately it turned out I had provided a single patch with both changes in the same patch
>
> You raised the question about not having the samba initscript calling the wsdd initscript. I updated that script and submitted it but thought the change of adding the wsdd as a dependency had been merged so did not send a v2 of that change.
>
> So wsdd is not getting installed when samba is being updated.
>
> I will submit a new patch for the samba lfs update to add wsdd as a dependency.
>
> Regards,
>
> Adolf.
>
>
> On 25/03/2024 10:15, IPFire Project wrote:
>> This update is another testing version for IPFire: It comes with the brand release of the IPFire IPS, a number of bug fixes across the entire system and a good amount of package updates. Test it while it's still hot!
>>
>> IPFire_
>> IPFire 2.29 - Core Update 185 is available for testing
>> This update is another testing version for IPFire: It comes with the brand release of the IPFire IPS, a number of bug fixes across the entire system and a good amount of package updates. Test it while it's still hot!
>> Read The Full Post On Our Blog <https://www.ipfire.org/blog/ipfire-2-29-core-update-185-is-available-for-testing?utm_medium=email&utm_source=blog-announcement>
>> The IPFire Project, c/o Lightning Wire Labs GmbH, Gerhardstraße 8, 45711 Datteln, Germany
>> Unsubscribe <https://www.ipfire.org/unsubscribe>
next prev parent reply other threads:[~2024-03-25 11:12 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <171135811429.1850211.10643578824706352392.ipfire@ipfire.org>
2024-03-25 11:10 ` Adolf Belka
2024-03-25 11:12 ` Michael Tremer [this message]
2024-03-25 13:09 ` Adolf Belka
2024-03-25 15:02 ` Adolf Belka
2024-03-25 15:49 ` Nick Howitt
2024-03-25 16:29 ` Adolf Belka
2024-03-26 10:55 ` Michael Tremer
2024-03-26 11:37 ` Adolf Belka
2024-03-26 11:45 ` Michael Tremer
2024-03-26 12:35 ` Adolf Belka
2024-03-26 14:44 ` Michael Tremer
2024-03-27 10:05 ` Adolf Belka
2024-03-27 10:14 ` Michael Tremer
2024-03-27 11:25 ` Adolf Belka
2024-03-26 12:36 ` Nick Howitt
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=D6271D26-31DB-4217-A59E-74C9C7250EEB@ipfire.org \
--to=michael.tremer@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