All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Mike Looijmans" <mike.looijmans@topic.nl>
To: "Mittal, Anuj" <anuj.mittal@intel.com>,
	"openembedded-core@lists.openembedded.org"
	<openembedded-core@lists.openembedded.org>
Subject: Re: [OE-core] [gatesgarth][PATCH] license_image.bbclass: Don't attempt to symlink to the same file
Date: Fri, 5 Feb 2021 15:51:50 +0100	[thread overview]
Message-ID: <75a74318-609e-916b-2180-8849ae7dcf21@topic.nl> (raw)
In-Reply-To: <89f603997b197c3fe883fbb8e74c710111dd569b.camel@intel.com>


Met vriendelijke groet / kind regards,

Mike Looijmans
System Expert


TOPIC Embedded Products B.V.
Materiaalweg 4, 5681 RJ Best
The Netherlands

T: +31 (0) 499 33 69 69
E: mike.looijmans@topicproducts.com
W: www.topicproducts.com

Please consider the environment before printing this e-mail
On 05-02-2021 15:44, Mittal, Anuj wrote:
> On Fri, 2021-02-05 at 15:24 +0100, Mike Looijmans wrote:
>> Sometimes (that is, in all my builds) the lic_manifest_dir and
>> lic_manifest_symlink_dir end up pointing to the same file, resulting
>> in an error like this:
>>    Exception: FileExistsError: [Errno 17] File exists: '/.../tmp-
>> glibc/deploy/licenses/my-image-tdkz15' -> '/.../tmp-
>> glibc/deploy/licenses/my-image-tdkz15'
>>
>> First check to see if this is the case before attempting to create
>> the link.
> Is this not required in master branch? I can't see this change there.

Probably yes, too.

And half the commit message got lost somewhere. I'll try a resend...


-- 
Mike Looijmans


  parent reply	other threads:[~2021-02-05 14:52 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-02-05 14:24 [gatesgarth][PATCH] license_image.bbclass: Don't attempt to symlink to the same file Mike Looijmans
2021-02-05 14:44 ` [OE-core] " Anuj Mittal
     [not found]   ` <1b153bce-a66a-45ee-a5c6-963ea6fb1c82.949ef384-8293-46b8-903f-40a477c056ae.2911e63c-9e5c-4e4f-ace5-3d0373a59996@emailsignatures365.codetwo.com>
     [not found]     ` <1b153bce-a66a-45ee-a5c6-963ea6fb1c82.0d2bd5fa-15cc-4b27-b94e-83614f9e5b38.0c810297-d118-4896-b755-845b359e15b7@emailsignatures365.codetwo.com>
2021-02-05 14:51       ` Mike Looijmans [this message]
     [not found]       ` <1660E19B8E4F9B35.26096@lists.openembedded.org>
2021-02-05 14:58         ` Mike Looijmans

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=75a74318-609e-916b-2180-8849ae7dcf21@topic.nl \
    --to=mike.looijmans@topic.nl \
    --cc=anuj.mittal@intel.com \
    --cc=openembedded-core@lists.openembedded.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 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.