dpkg-raw git fetch

dpkg-raw git fetch

[sven.schultschik]

[-- Attachment #1.1: Type: text/plain, Size: 1260 bytes --]

Hi all,



once again me. I always used dpkg-raw with local files, but now I want to use a git repository to copy some files.



I added as always the SRC_URI = "git://....." etc., but the ${S}/git folder keeps empty.



Does dpkg-raw not fetching remote files automatically?



Mit freundlichen Grüßen
Sven Angelo Schultschik

Siemens AG
Digital Industries
Process Automation
Software House Khe
DI PA CI R&D 2
Östliche Rheinbrückenstr. 50
76187 Karlsruhe, Deutschland
Tel.: +49 721 595-2827
mailto:sven.schultschik@siemens.com
www.siemens.com/ingenuityforlife<https://siemens.com/ingenuityforlife>

Siemens Aktiengesellschaft: Vorsitzender des Aufsichtsrats: Jim Hagemann Snabe; Vorstand: Joe Kaeser, Vorsitzender; Roland Busch, Lisa Davis, Klaus Helmrich, Cedrik Neike, Michael Sen, Ralf P. Thomas; Sitz der Gesellschaft: Berlin und München, Deutschland; Registergericht: Berlin Charlottenburg, HRB 12300, München, HRB 6684; WEEE-Reg.-Nr. DE 23691322

Wichtiger Hinweis: Diese E-Mail und etwaige Anlagen enthalten firmenvertrauliche Informationen. Sollten Sie diese E-Mail irrtümlich erhalten haben, benachrichtigen Sie uns bitte durch Antwort-Mail und löschen Sie diese E-Mail nebst Anlagen von Ihrem System. Vielen Dank.


[-- Attachment #1.2: Type: text/html, Size: 4263 bytes --]

[-- Attachment #2: image001.gif --]
[-- Type: image/gif, Size: 3536 bytes --]

Re: dpkg-raw git fetch

[Jan Kiszka]

On 27.02.20 15:51, [ext] sven.schultschik@siemens.com wrote:
> Hi all,
> 
> once again me. I always used dpkg-raw with local files, but now I want 
> to use a git repository to copy some files.
> 
> I added as always the SRC_URI = “git://…..” etc., but the ${S}/git 
> folder keeps empty.
> 
> Does dpkg-raw not fetching remote files automatically?

Fetching is implemented in the base class which all classes inherit from.

Check the logs of that fetching step for potential problems.

Jan

-- 
Siemens AG, Corporate Technology, CT RDA IOT SES-DE
Corporate Competence Center Embedded Linux

AW: dpkg-raw git fetch

[sven.schultschik]

Fetch does put the repository into the downloads folder.

Which task is responsible to bring the files from downloads/../git-repo to ${S} ??

S = "${WORKDIR}/git" ist defined in the recipe.

Log.unpack says clone -s -n downloads/git recipe-name/version/git without an error

Shouldn't the see the files then?

Mit freundlichen Grüßen
Sven Angelo Schultschik

Siemens AG
Digital Industries
Process Automation
Software House Khe
DI PA CI R&D 2
Östliche Rheinbrückenstr. 50
76187 Karlsruhe, Deutschland
Tel.: +49 721 595-2827
mailto:sven.schultschik@siemens.com

www.siemens.com/ingenuityforlife

Siemens Aktiengesellschaft: Vorsitzender des Aufsichtsrats: Jim Hagemann Snabe; Vorstand: Joe Kaeser, Vorsitzender; Roland Busch, Lisa Davis, Klaus Helmrich, Cedrik Neike, Michael Sen, Ralf P. Thomas; Sitz der Gesellschaft: Berlin und München, Deutschland; Registergericht: Berlin Charlottenburg, HRB 12300, München, HRB 6684; WEEE-Reg.-Nr. DE 23691322

Wichtiger Hinweis: Diese E-Mail und etwaige Anlagen enthalten firmenvertrauliche Informationen. Sollten Sie diese E-Mail irrtümlich erhalten haben, benachrichtigen Sie uns bitte durch Antwort-Mail und löschen Sie diese E-Mail nebst Anlagen von Ihrem System. Vielen Dank.
-----Ursprüngliche Nachricht-----
Von: Jan Kiszka <jan.kiszka@siemens.com> 
Gesendet: Donnerstag, 27. Februar 2020 15:58
An: Schultschik, Sven (DI PA CI R&D 2) <sven.schultschik@siemens.com>; isar-users@googlegroups.com
Betreff: Re: dpkg-raw git fetch

On 27.02.20 15:51, [ext] sven.schultschik@siemens.com wrote:
> Hi all,
> 
> once again me. I always used dpkg-raw with local files, but now I want 
> to use a git repository to copy some files.
> 
> I added as always the SRC_URI = “git://…..” etc., but the ${S}/git 
> folder keeps empty.
> 
> Does dpkg-raw not fetching remote files automatically?

Fetching is implemented in the base class which all classes inherit from.

Check the logs of that fetching step for potential problems.

Jan

--
Siemens AG, Corporate Technology, CT RDA IOT SES-DE Corporate Competence Center Embedded Linux

Re: dpkg-raw git fetch

[Jan Kiszka]

On 27.02.20 17:39, Schultschik, Sven (DI PA CI R&D 2) wrote:
> Fetch does put the repository into the downloads folder.
> 
> Which task is responsible to bring the files from downloads/../git-repo to ${S} ??
> 

Right: unpack.

> S = "${WORKDIR}/git" ist defined in the recipe.
> 
> Log.unpack says clone -s -n downloads/git recipe-name/version/git without an error
> 
> Shouldn't the see the files then?

Yes - provided the default revision checked out contains anything.

Jan

-- 
Siemens AG, Corporate Technology, CT RDA IOT SES-DE
Corporate Competence Center Embedded Linux

AW: dpkg-raw git fetch

[sven.schultschik]

Hi,

I'm a little bit confused. In the task unpack the SRC_URI files will be put into WORKDIR https://github.com/ilbers/isar/blob/f3d50cfb9b7a5740c6dd11ee58fc4ba1a1815eca/meta/classes/base.bbclass#L182 

But in the next task S (workdir/git) will be cleared. https://github.com/ilbers/isar/blob/f3d50cfb9b7a5740c6dd11ee58fc4ba1a1815eca/meta/classes/dpkg-raw.bbclass#L15 

Should I understand why ${S} will be cleard before do_install is called?

Mit freundlichen Grüßen
Sven Angelo Schultschik

Siemens AG
Digital Industries
Process Automation
Software House Khe
DI PA CI R&D 2
Östliche Rheinbrückenstr. 50
76187 Karlsruhe, Deutschland
Tel.: +49 721 595-2827
mailto:sven.schultschik@siemens.com

www.siemens.com/ingenuityforlife

Siemens Aktiengesellschaft: Vorsitzender des Aufsichtsrats: Jim Hagemann Snabe; Vorstand: Joe Kaeser, Vorsitzender; Roland Busch, Lisa Davis, Klaus Helmrich, Cedrik Neike, Michael Sen, Ralf P. Thomas; Sitz der Gesellschaft: Berlin und München, Deutschland; Registergericht: Berlin Charlottenburg, HRB 12300, München, HRB 6684; WEEE-Reg.-Nr. DE 23691322

Wichtiger Hinweis: Diese E-Mail und etwaige Anlagen enthalten firmenvertrauliche Informationen. Sollten Sie diese E-Mail irrtümlich erhalten haben, benachrichtigen Sie uns bitte durch Antwort-Mail und löschen Sie diese E-Mail nebst Anlagen von Ihrem System. Vielen Dank.
-----Ursprüngliche Nachricht-----
Von: Jan Kiszka <jan.kiszka@siemens.com> 
Gesendet: Donnerstag, 27. Februar 2020 18:00
An: Schultschik, Sven (DI PA CI R&D 2) <sven.schultschik@siemens.com>; isar-users@googlegroups.com
Betreff: Re: dpkg-raw git fetch

On 27.02.20 17:39, Schultschik, Sven (DI PA CI R&D 2) wrote:
> Fetch does put the repository into the downloads folder.
> 
> Which task is responsible to bring the files from downloads/../git-repo to ${S} ??
> 

Right: unpack.

> S = "${WORKDIR}/git" ist defined in the recipe.
> 
> Log.unpack says clone -s -n downloads/git recipe-name/version/git 
> without an error
> 
> Shouldn't the see the files then?

Yes - provided the default revision checked out contains anything.

Jan

--
Siemens AG, Corporate Technology, CT RDA IOT SES-DE Corporate Competence Center Embedded Linux

Re: AW: dpkg-raw git fetch

[Gylstorff Quirin]

Hi Sven,
On 2/28/20 2:08 PM, [ext] sven.schultschik@siemens.com wrote:
> Hi,
> 
> I'm a little bit confused. In the task unpack the SRC_URI files will be put into WORKDIR https://github.com/ilbers/isar/blob/f3d50cfb9b7a5740c6dd11ee58fc4ba1a1815eca/meta/classes/base.bbclass#L182
> 
> But in the next task S (workdir/git) will be cleared. https://github.com/ilbers/isar/blob/f3d50cfb9b7a5740c6dd11ee58fc4ba1a1815eca/meta/classes/dpkg-raw.bbclass#L15
> 
That cleans the destination directory "${D}" not the source directory "${S}"

Quirin
> Should I understand why ${S} will be cleard before do_install is called?
> 
> Mit freundlichen Grüßen
> Sven Angelo Schultschik
> 
> Siemens AG
> Digital Industries
> Process Automation
> Software House Khe
> DI PA CI R&D 2
> Östliche Rheinbrückenstr. 50
> 76187 Karlsruhe, Deutschland
> Tel.: +49 721 595-2827
> mailto:sven.schultschik@siemens.com
> 
> www.siemens.com/ingenuityforlife
> 
> Siemens Aktiengesellschaft: Vorsitzender des Aufsichtsrats: Jim Hagemann Snabe; Vorstand: Joe Kaeser, Vorsitzender; Roland Busch, Lisa Davis, Klaus Helmrich, Cedrik Neike, Michael Sen, Ralf P. Thomas; Sitz der Gesellschaft: Berlin und München, Deutschland; Registergericht: Berlin Charlottenburg, HRB 12300, München, HRB 6684; WEEE-Reg.-Nr. DE 23691322
> 
> Wichtiger Hinweis: Diese E-Mail und etwaige Anlagen enthalten firmenvertrauliche Informationen. Sollten Sie diese E-Mail irrtümlich erhalten haben, benachrichtigen Sie uns bitte durch Antwort-Mail und löschen Sie diese E-Mail nebst Anlagen von Ihrem System. Vielen Dank.
> -----Ursprüngliche Nachricht-----
> Von: Jan Kiszka <jan.kiszka@siemens.com>
> Gesendet: Donnerstag, 27. Februar 2020 18:00
> An: Schultschik, Sven (DI PA CI R&D 2) <sven.schultschik@siemens.com>; isar-users@googlegroups.com
> Betreff: Re: dpkg-raw git fetch
> 
> On 27.02.20 17:39, Schultschik, Sven (DI PA CI R&D 2) wrote:
>> Fetch does put the repository into the downloads folder.
>>
>> Which task is responsible to bring the files from downloads/../git-repo to ${S} ??
>>
> 
> Right: unpack.
> 
>> S = "${WORKDIR}/git" ist defined in the recipe.
>>
>> Log.unpack says clone -s -n downloads/git recipe-name/version/git
>> without an error
>>
>> Shouldn't the see the files then?
> 
> Yes - provided the default revision checked out contains anything.
> 
> Jan
> 
> --
> Siemens AG, Corporate Technology, CT RDA IOT SES-DE Corporate Competence Center Embedded Linux
> 

Re: dpkg-raw git fetch

[Henning Schild]

On Fri, 28 Feb 2020 13:08:10 +0000
"[ext] sven.schultschik@siemens.com" <sven.schultschik@siemens.com>
wrote:

> Hi,
> 
> I'm a little bit confused. In the task unpack the SRC_URI files will
> be put into WORKDIR
> https://github.com/ilbers/isar/blob/f3d50cfb9b7a5740c6dd11ee58fc4ba1a1815eca/meta/classes/base.bbclass#L182 
> 
> But in the next task S (workdir/git) will be cleared.
> https://github.com/ilbers/isar/blob/f3d50cfb9b7a5740c6dd11ee58fc4ba1a1815eca/meta/classes/dpkg-raw.bbclass#L15 
> 
> Should I understand why ${S} will be cleard before do_install is
> called?

I think you might have found an issue with the distinction of S and D.
In fact they should be different folders but for dpkg-raw they are not.
I think also the debianize class does not clearly distinguish them.

One workaround would be to create that second copy on your own. So you
clone i.e with destsuffix and make sure that the unpacked copy and the
installed copy are not the same directory.

Once you have found a solution and have a clue where the line between S
and D should be drawn, please give feedback on how to improve the class.

Henning

> Mit freundlichen Grüßen
> Sven Angelo Schultschik
> 
> Siemens AG
> Digital Industries
> Process Automation
> Software House Khe
> DI PA CI R&D 2
> Östliche Rheinbrückenstr. 50
> 76187 Karlsruhe, Deutschland
> Tel.: +49 721 595-2827
> mailto:sven.schultschik@siemens.com
> 
> www.siemens.com/ingenuityforlife
> 
> Siemens Aktiengesellschaft: Vorsitzender des Aufsichtsrats: Jim
> Hagemann Snabe; Vorstand: Joe Kaeser, Vorsitzender; Roland Busch,
> Lisa Davis, Klaus Helmrich, Cedrik Neike, Michael Sen, Ralf P.
> Thomas; Sitz der Gesellschaft: Berlin und München, Deutschland;
> Registergericht: Berlin Charlottenburg, HRB 12300, München, HRB 6684;
> WEEE-Reg.-Nr. DE 23691322
> 
> Wichtiger Hinweis: Diese E-Mail und etwaige Anlagen enthalten
> firmenvertrauliche Informationen. Sollten Sie diese E-Mail irrtümlich
> erhalten haben, benachrichtigen Sie uns bitte durch Antwort-Mail und
> löschen Sie diese E-Mail nebst Anlagen von Ihrem System. Vielen Dank.
> -----Ursprüngliche Nachricht----- Von: Jan Kiszka
> <jan.kiszka@siemens.com> Gesendet: Donnerstag, 27. Februar 2020 18:00
> An: Schultschik, Sven (DI PA CI R&D 2)
> <sven.schultschik@siemens.com>; isar-users@googlegroups.com Betreff:
> Re: dpkg-raw git fetch
> 
> On 27.02.20 17:39, Schultschik, Sven (DI PA CI R&D 2) wrote:
> > Fetch does put the repository into the downloads folder.
> > 
> > Which task is responsible to bring the files from
> > downloads/../git-repo to ${S} ?? 
> 
> Right: unpack.
> 
> > S = "${WORKDIR}/git" ist defined in the recipe.
> > 
> > Log.unpack says clone -s -n downloads/git recipe-name/version/git 
> > without an error
> > 
> > Shouldn't the see the files then?  
> 
> Yes - provided the default revision checked out contains anything.
> 
> Jan
> 
> --
> Siemens AG, Corporate Technology, CT RDA IOT SES-DE Corporate
> Competence Center Embedded Linux
> 

Re: dpkg-raw git fetch

[cedric_hombourger]

[-- Attachment #1.1: Type: text/plain, Size: 3670 bytes --]

On Monday, March 9, 2020 at 5:59:40 PM UTC+1, Henning Schild wrote:
>
> On Fri, 28 Feb 2020 13:08:10 +0000 
> "[ext] sven.sc...@siemens.com <javascript:>" <sven.sc...@siemens.com 
> <javascript:>> 
> wrote: 
>
> > Hi, 
> > 
> > I'm a little bit confused. In the task unpack the SRC_URI files will 
> > be put into WORKDIR 
> > 
> https://github.com/ilbers/isar/blob/f3d50cfb9b7a5740c6dd11ee58fc4ba1a1815eca/meta/classes/base.bbclass#L182 
> > 
> > But in the next task S (workdir/git) will be cleared. 
> > 
> https://github.com/ilbers/isar/blob/f3d50cfb9b7a5740c6dd11ee58fc4ba1a1815eca/meta/classes/dpkg-raw.bbclass#L15 
> > 
> > Should I understand why ${S} will be cleard before do_install is 
> > called? 
>
> I think you might have found an issue with the distinction of S and D. 
> In fact they should be different folders but for dpkg-raw they are not. 
> I think also the debianize class does not clearly distinguish them. 
>
>
I coincidentally ran into the same issue yesterday and yes debianize 
assumes all the work should be done in ${S}
should debianize expose a DEBIANIZE_DIR defaulting to ${S} and let dpkg-raw 
set it to ${D} instead?

One workaround would be to create that second copy on your own. So you 
> clone i.e with destsuffix and make sure that the unpacked copy and the 
> installed copy are not the same directory. 
>
> Once you have found a solution and have a clue where the line between S 
> and D should be drawn, please give feedback on how to improve the class. 
>
> Henning 
>
> > Mit freundlichen Grüßen 
> > Sven Angelo Schultschik 
> > 
> > Siemens AG 
> > Digital Industries 
> > Process Automation 
> > Software House Khe 
> > DI PA CI R&D 2 
> > Östliche Rheinbrückenstr. 50 
> > 76187 Karlsruhe, Deutschland 
> > Tel.: +49 721 595-2827 
> > mailto:sven.sc...@siemens.com <javascript:> 
> > 
> > www.siemens.com/ingenuityforlife 
> > 
> > Siemens Aktiengesellschaft: Vorsitzender des Aufsichtsrats: Jim 
> > Hagemann Snabe; Vorstand: Joe Kaeser, Vorsitzender; Roland Busch, 
> > Lisa Davis, Klaus Helmrich, Cedrik Neike, Michael Sen, Ralf P. 
> > Thomas; Sitz der Gesellschaft: Berlin und München, Deutschland; 
> > Registergericht: Berlin Charlottenburg, HRB 12300, München, HRB 6684; 
> > WEEE-Reg.-Nr. DE 23691322 
> > 
> > Wichtiger Hinweis: Diese E-Mail und etwaige Anlagen enthalten 
> > firmenvertrauliche Informationen. Sollten Sie diese E-Mail irrtümlich 
> > erhalten haben, benachrichtigen Sie uns bitte durch Antwort-Mail und 
> > löschen Sie diese E-Mail nebst Anlagen von Ihrem System. Vielen Dank. 
> > -----Ursprüngliche Nachricht----- Von: Jan Kiszka 
> > <jan....@siemens.com <javascript:>> Gesendet: Donnerstag, 27. Februar 
> 2020 18:00 
> > An: Schultschik, Sven (DI PA CI R&D 2) 
> > <sven.sc...@siemens.com <javascript:>>; isar-...@googlegroups.com 
> <javascript:> Betreff: 
> > Re: dpkg-raw git fetch 
> > 
> > On 27.02.20 17:39, Schultschik, Sven (DI PA CI R&D 2) wrote: 
> > > Fetch does put the repository into the downloads folder. 
> > > 
> > > Which task is responsible to bring the files from 
> > > downloads/../git-repo to ${S} ?? 
> > 
> > Right: unpack. 
> > 
> > > S = "${WORKDIR}/git" ist defined in the recipe. 
> > > 
> > > Log.unpack says clone -s -n downloads/git recipe-name/version/git 
> > > without an error 
> > > 
> > > Shouldn't the see the files then?   
> > 
> > Yes - provided the default revision checked out contains anything. 
> > 
> > Jan 
> > 
> > -- 
> > Siemens AG, Corporate Technology, CT RDA IOT SES-DE Corporate 
> > Competence Center Embedded Linux 
> > 
>
>

[-- Attachment #1.2: Type: text/html, Size: 7480 bytes --]

Re: dpkg-raw git fetch

[Henning Schild]

On Tue, 10 Mar 2020 08:08:27 -0700
<cedric_hombourger@mentor.com> wrote:

> On Monday, March 9, 2020 at 5:59:40 PM UTC+1, Henning Schild wrote:
> >
> > On Fri, 28 Feb 2020 13:08:10 +0000 
> > "[ext] sven.sc...@siemens.com <javascript:>"
> > <sven.sc...@siemens.com <javascript:>> 
> > wrote: 
> >  
> > > Hi, 
> > > 
> > > I'm a little bit confused. In the task unpack the SRC_URI files
> > > will be put into WORKDIR 
> > >   
> > https://github.com/ilbers/isar/blob/f3d50cfb9b7a5740c6dd11ee58fc4ba1a1815eca/meta/classes/base.bbclass#L182
> >   
> > > 
> > > But in the next task S (workdir/git) will be cleared. 
> > >   
> > https://github.com/ilbers/isar/blob/f3d50cfb9b7a5740c6dd11ee58fc4ba1a1815eca/meta/classes/dpkg-raw.bbclass#L15
> >   
> > > 
> > > Should I understand why ${S} will be cleard before do_install is 
> > > called?   
> >
> > I think you might have found an issue with the distinction of S and
> > D. In fact they should be different folders but for dpkg-raw they
> > are not. I think also the debianize class does not clearly
> > distinguish them. 
> >
> >  
> I coincidentally ran into the same issue yesterday and yes debianize 
> assumes all the work should be done in ${S}
> should debianize expose a DEBIANIZE_DIR defaulting to ${S} and let
> dpkg-raw set it to ${D} instead?

Unfortunately bitbake/oe lack good descriptions of the two. But those
can be found here:
https://devmanual.gentoo.org/ebuild-writing/variables/ and probably
also in FreeBSD

That means that debianization should be done on S, not D.

And OE also has 'D = "${WORKDIR}/image"', which seems to be missing in
Isar.

Henning

> One workaround would be to create that second copy on your own. So
> you 
> > clone i.e with destsuffix and make sure that the unpacked copy and
> > the installed copy are not the same directory. 
> >
> > Once you have found a solution and have a clue where the line
> > between S and D should be drawn, please give feedback on how to
> > improve the class. 
> >
> > Henning 
> >  
> > > Mit freundlichen Grüßen 
> > > Sven Angelo Schultschik 
> > > 
> > > Siemens AG 
> > > Digital Industries 
> > > Process Automation 
> > > Software House Khe 
> > > DI PA CI R&D 2 
> > > Östliche Rheinbrückenstr. 50 
> > > 76187 Karlsruhe, Deutschland 
> > > Tel.: +49 721 595-2827 
> > > mailto:sven.sc...@siemens.com <javascript:> 
> > > 
> > > www.siemens.com/ingenuityforlife 
> > > 
> > > Siemens Aktiengesellschaft: Vorsitzender des Aufsichtsrats: Jim 
> > > Hagemann Snabe; Vorstand: Joe Kaeser, Vorsitzender; Roland Busch, 
> > > Lisa Davis, Klaus Helmrich, Cedrik Neike, Michael Sen, Ralf P. 
> > > Thomas; Sitz der Gesellschaft: Berlin und München, Deutschland; 
> > > Registergericht: Berlin Charlottenburg, HRB 12300, München, HRB
> > > 6684; WEEE-Reg.-Nr. DE 23691322 
> > > 
> > > Wichtiger Hinweis: Diese E-Mail und etwaige Anlagen enthalten 
> > > firmenvertrauliche Informationen. Sollten Sie diese E-Mail
> > > irrtümlich erhalten haben, benachrichtigen Sie uns bitte durch
> > > Antwort-Mail und löschen Sie diese E-Mail nebst Anlagen von Ihrem
> > > System. Vielen Dank. -----Ursprüngliche Nachricht----- Von: Jan
> > > Kiszka <jan....@siemens.com <javascript:>> Gesendet: Donnerstag,
> > > 27. Februar   
> > 2020 18:00   
> > > An: Schultschik, Sven (DI PA CI R&D 2) 
> > > <sven.sc...@siemens.com <javascript:>>; isar-...@googlegroups.com
> > >   
> > <javascript:> Betreff:   
> > > Re: dpkg-raw git fetch 
> > > 
> > > On 27.02.20 17:39, Schultschik, Sven (DI PA CI R&D 2) wrote:   
> > > > Fetch does put the repository into the downloads folder. 
> > > > 
> > > > Which task is responsible to bring the files from 
> > > > downloads/../git-repo to ${S} ??   
> > > 
> > > Right: unpack. 
> > >   
> > > > S = "${WORKDIR}/git" ist defined in the recipe. 
> > > > 
> > > > Log.unpack says clone -s -n downloads/git
> > > > recipe-name/version/git without an error 
> > > > 
> > > > Shouldn't the see the files then?     
> > > 
> > > Yes - provided the default revision checked out contains
> > > anything. 
> > > 
> > > Jan 
> > > 
> > > -- 
> > > Siemens AG, Corporate Technology, CT RDA IOT SES-DE Corporate 
> > > Competence Center Embedded Linux 
> > >   
> >
> >  
> 

Re: dpkg-raw git fetch

[Jan Kiszka]

On 10.03.20 16:36, [ext] Henning Schild wrote:
> On Tue, 10 Mar 2020 08:08:27 -0700
> <cedric_hombourger@mentor.com> wrote:
> 
>> On Monday, March 9, 2020 at 5:59:40 PM UTC+1, Henning Schild wrote:
>>>
>>> On Fri, 28 Feb 2020 13:08:10 +0000
>>> "[ext] sven.sc...@siemens.com <javascript:>"
>>> <sven.sc...@siemens.com <javascript:>>
>>> wrote:
>>>   
>>>> Hi,
>>>>
>>>> I'm a little bit confused. In the task unpack the SRC_URI files
>>>> will be put into WORKDIR
>>>>    
>>> https://github.com/ilbers/isar/blob/f3d50cfb9b7a5740c6dd11ee58fc4ba1a1815eca/meta/classes/base.bbclass#L182
>>>    
>>>>
>>>> But in the next task S (workdir/git) will be cleared.
>>>>    
>>> https://github.com/ilbers/isar/blob/f3d50cfb9b7a5740c6dd11ee58fc4ba1a1815eca/meta/classes/dpkg-raw.bbclass#L15
>>>    
>>>>
>>>> Should I understand why ${S} will be cleard before do_install is
>>>> called?
>>>
>>> I think you might have found an issue with the distinction of S and
>>> D. In fact they should be different folders but for dpkg-raw they
>>> are not. I think also the debianize class does not clearly
>>> distinguish them.
>>>
>>>   
>> I coincidentally ran into the same issue yesterday and yes debianize
>> assumes all the work should be done in ${S}
>> should debianize expose a DEBIANIZE_DIR defaulting to ${S} and let
>> dpkg-raw set it to ${D} instead?
> 
> Unfortunately bitbake/oe lack good descriptions of the two. But those
> can be found here:
> https://devmanual.gentoo.org/ebuild-writing/variables/ and probably
> also in FreeBSD
> 
> That means that debianization should be done on S, not D.
> 
> And OE also has 'D = "${WORKDIR}/image"', which seems to be missing in
> Isar.

OK, now I'm running into the same mess, wondering why some recipe was 
carrying a patch that targeted the installation dir, rather than the 
source (which broke randomly).

Do you have the patch for this issue already?

Jan

-- 
Siemens AG, Corporate Technology, CT RDA IOT SES-DE
Corporate Competence Center Embedded Linux