public inbox for isar-users@googlegroups.com
 help / color / mirror / Atom feed
From: Silvano Cirujano Cuesta <silvano.cirujano-cuesta@siemens.com>
To: isar-users@googlegroups.com, Claudius Heine <ch@denx.de>
Subject: Re: image-postproc-extension.bbclass modifying /etc/os-release
Date: Mon, 18 Jan 2021 12:35:27 +0100	[thread overview]
Message-ID: <79cdea42-8338-2e7f-33dd-f396db634a14@siemens.com> (raw)
In-Reply-To: <67e1fac9-5af5-29aa-de57-9a0de0cdd165@siemens.com>

I might try to provide a fix, if we agree that the current implementation has an issue.

@Claudius: you wrote the original code [1]. Do you remember why you implemented it this way? Do you remember if you were aware of the issue I mentioned and you provided a mitigation for the issue that I see (assuming my analysis is right)?

[1] https://github.com/ilbers/isar/commit/13ce96e5bc84b60f2fa7ccfe93dde045461884e6

  Silvano

On 15/01/2021 15:26, [ext] Silvano Cirujano Cuesta wrote:
> Hi,
>
> I've noticed that '/etc/os-release' is being changed on the image in meta/classes/image-postproc-extension.bbclass [1].  What BTW ends up changing '/usr/lib/os-release', since it's only a symlink. But both '/etc/os-release' and '/usr/lib/os-release' are owned by 'base-files'...
>
> An upgrade of 'base-files' would be replacing (silently, since is not marked as a configuration file) '/usr/lib/os-release' with the version of the upstream 'base-files' package and possibly breaking any tools in the system relying on certain values in that file.
>
> Is there a reason that I'm missing for doing so instead of the Debian-way (file diversion with dpkg-divert)? Or any hack that I've overseen that avoids the mentioned breakage?
>
> Hasta la vista,
>
>   Silvano
>
> [1] https://github.com/ilbers/isar/blob/a0d6de4ac7dfb926b38cfcd44f2bc8852f2e43e3/meta/classes/image-postproc-extension.bbclass#L20
>

  reply	other threads:[~2021-01-18 11:35 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-01-15 14:26 Silvano Cirujano Cuesta
2021-01-18 11:35 ` Silvano Cirujano Cuesta [this message]
2021-01-18 12:35   ` Claudius Heine
2021-01-18 14:52     ` Silvano Cirujano Cuesta
2021-01-19  8:25     ` Henning Schild
2021-01-19  8:33       ` Henning Schild
2021-01-19  8:50         ` Silvano Cirujano Cuesta
2021-01-19  9:22           ` Henning Schild
2021-01-19 10:37             ` Silvano Cirujano Cuesta
2021-01-22  8:52               ` Claudius Heine
2021-01-22  9:47                 ` Silvano Cirujano Cuesta
2021-01-22 10:33                   ` Claudius Heine
2021-01-22 11:36                     ` Silvano Cirujano Cuesta
2021-02-05 11:55                       ` vijaikumar....@gmail.com
2021-02-05 14:57                         ` Silvano Cirujano Cuesta
2021-02-07  9:02                           ` vijai kumar
2021-02-08  8:50                             ` Silvano Cirujano Cuesta
2021-02-09  6:02                               ` vijai kumar
2021-02-10  9:22                                 ` Baurzhan Ismagulov
2021-02-11  5:54                                   ` vijaikumar....@gmail.com
2021-02-11  8:49                                     ` Baurzhan Ismagulov
2021-02-11 10:34                                       ` vijaikumar....@gmail.com
2021-01-19  8:43       ` Silvano Cirujano Cuesta
2021-01-19  9:08         ` Henning Schild
2021-01-19  9:14           ` Henning Schild
2021-01-19  9:30           ` Silvano Cirujano Cuesta
2021-01-19  9:11   ` Claudius Heine
2021-01-19  8:43 ` Henning Schild
2021-01-19  9:03   ` Silvano Cirujano Cuesta
2021-01-19  9:38 ` Henning Schild
2021-02-08 17:20 ` Baurzhan Ismagulov

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=79cdea42-8338-2e7f-33dd-f396db634a14@siemens.com \
    --to=silvano.cirujano-cuesta@siemens.com \
    --cc=ch@denx.de \
    --cc=isar-users@googlegroups.com \
    /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