public inbox for development@lists.ipfire.org
 help / color / mirror / Atom feed
From: Michael Tremer <michael.tremer@ipfire.org>
To: development@lists.ipfire.org
Subject: Re: Build fails at cdrom stage
Date: Wed, 07 Aug 2024 13:03:52 +0100	[thread overview]
Message-ID: <4E859F5C-9D11-46C4-AFE1-1DABFCAC5861@ipfire.org> (raw)
In-Reply-To: <2ebe0626-84f2-4f70-b66a-7e2fc9f0594b@ipfire.org>

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

Hello,

Always try to pull :) But it is not wrong to complain to me on the list. I want to know what I am breaking to hopefully learn from it.

-Michael

> On 7 Aug 2024, at 11:14, Adolf Belka <adolf.belka(a)ipfire.org> wrote:
> 
> 
> 
> On 07/08/2024 11:31, Michael Tremer wrote:
>> Please pull again. I fixed this already yesterday…
> Yes, it is working now.
> 
> I think for future issues I will wait for the following day and do a pull to see if things have already been fixed.
> 
> Regards,
> Adolf.
> 
>> I cut the build environment off of any network, but it seems that Postfix wants at least something there…
>> The change that broke it:
>>   https://git.ipfire.org/?p=ipfire-2.x.git;a=commitdiff;h=91942800f96fbac354eba56714814831badfc88e
>> The fix:
>>   https://git.ipfire.org/?p=ipfire-2.x.git;a=commitdiff;h=f5160566b202677ffee1423aadc2ce7d87c03114
>>> On 6 Aug 2024, at 18:31, Adolf Belka <adolf.belka(a)ipfire.org> wrote:
>>> 
>>> I pulled but now it stops with postfix saying that it can't find any active network interfaces


      reply	other threads:[~2024-08-07 12:03 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-08-06 14:55 Adolf Belka
2024-08-06 14:56 ` Michael Tremer
2024-08-06 17:31   ` Adolf Belka
2024-08-07  9:31     ` Michael Tremer
2024-08-07 10:14       ` Adolf Belka
2024-08-07 12:03         ` Michael Tremer [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=4E859F5C-9D11-46C4-AFE1-1DABFCAC5861@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