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: For information - changed rootfiles found for linux and samba
Date: Mon, 01 Feb 2021 11:17:36 +0000	[thread overview]
Message-ID: <BA8486E6-9728-44D1-8457-E8D04EE21BE1@ipfire.org> (raw)
In-Reply-To: <f6ebff44-04f1-9791-1f32-acf1970a198c@ipfire.org>

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

Hi,

> On 30 Jan 2021, at 17:27, Adolf Belka <adolf.belka(a)ipfire.org> wrote:
> 
> 
> 
> On 30/01/2021 18:00, Matthias Fischer wrote:
>> On 29.01.2021 23:25, Adolf Belka wrote:
>>> Hi all,
>>> 
>>> I have been updating some packages and while doing that I am continuously seeing two messages about rootfile changes for packages I have not worked on. In all cases I have run a git pull before doing the builds.
>>> 
>>> The messages are:-
>>> 
>>> Checking Logfiles for new Files
>>> Changes in linux-4.14.212-ipfire check rootfile!
>> Confirmed after building 32bit and 64bit.
>>> Changes in samba-4.13.1 check rootfile!
>>> 
>>> For Linux there is the following additional line in the logfile
>>> 
>>>          +lib/modules/4.14.212-ipfire/modules.builtin.alias.bin
>> Yep. Exactly.
>>> For Samba here is the following additional line in the logfile
>>> 
>>>          +var/ipfire/samba/samba-change-password
>> Not confirmed.
> The samba message has disappeared with the most recent build.

Yes, and I just pushed a patch to fix the kernel message, too :)

Thank you for letting me know.

Best,
-Michael

>>> Are these missing in the builds for these packages or do I have something wrong in my build setup
>>> 
>>> Regards,
>>> 
>>> Adolf.
>>> 
>> Best,
>> Matthias


      reply	other threads:[~2021-02-01 11:17 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-01-29 22:25 Adolf Belka
2021-01-30 17:00 ` Matthias Fischer
2021-01-30 17:27   ` Adolf Belka
2021-02-01 11:17     ` 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=BA8486E6-9728-44D1-8457-E8D04EE21BE1@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