All of lore.kernel.org
 help / color / mirror / Atom feed
From: Gylstorff Quirin <quirin.gylstorff@siemens.com>
To: "Moessbauer, Felix (T CED INW-CN)" <felix.moessbauer@siemens.com>,
	"cip-dev@lists.cip-project.org" <cip-dev@lists.cip-project.org>
Subject: Re: Override of sid distro config breaks mirrors
Date: Mon, 30 Jan 2023 12:01:42 +0100	[thread overview]
Message-ID: <65f143aa-3e48-9075-357a-08087a5e922c@siemens.com> (raw)
In-Reply-To: <0236184cd3f04ecb0a3282bdc6c8fb7eeb04ae81.camel@siemens.com>



On 1/30/23 10:58, Moessbauer, Felix (T CED INW-CN) wrote:
> Dear devs,
> 
> the distro "debian-sid" and "debian-sid-ports" is currently specified
> both in ISAR and in isar-cip-core. While in ISAR standard debian
> mirrors are used, cip-core pins that to a specific release on
> snapshots.debian.org.
You mean the list files, which override the list files provided by ISAR? 
Because the only distribution in isar-cip-core is `cip-core-sid-ports`.

This looks to me like a workaround to override DISTRO_APT_SOURCES
from `conf/distro/debian-sid-ports.conf`.

I pushed a fix at 
https://gitlab.com/cip-project/cip-core/isar-cip-core/-/tree/quirin/sid-lists/

> 
> This breaks use-cases where local mirrors shall be used, as these do
> not support snapshots. Also, this "infects" other layers that actually
> want to use sid "as-is".
> 
> Please consider renaming this distro to "cip-<distro>" to get rid of
> this ambiguity.
> 
> Best regards,
> Felix Moessbauer
> Siemens AG
Best regards

Quirin


  reply	other threads:[~2023-01-30 11:02 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-01-30  9:58 Override of sid distro config breaks mirrors Moessbauer, Felix
2023-01-30 11:01 ` Gylstorff Quirin [this message]
2023-01-31  9:09   ` Moessbauer, Felix
2023-02-02 14:59     ` Jan Kiszka

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=65f143aa-3e48-9075-357a-08087a5e922c@siemens.com \
    --to=quirin.gylstorff@siemens.com \
    --cc=cip-dev@lists.cip-project.org \
    --cc=felix.moessbauer@siemens.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.