[elbe-devel] Elbe build Ubuntu?

[Olivier Dion]

On Wed, 06 May 2020, Köry Maincent <kory.maincent at bootlin.com> wrote:
> Hello,
>
> On 30/04/2020 15:47, Köry Maincent wrote:
>> Hello Olivier,
>> 
>> 
>>> The dbschema.xsd is used both on the host and in the initvm.  If you
>>> change it on the host, you will be able to send your xml file to the
>>> initvm.  However, the initvm also need its dbschema.xsd to be updated.
>>>
>>> If you have create your initvm without the --devel option, then you need
>>> to edit "/usr/share/xml/elbe-common/dbsfed.xsd".  If you have create the
>>> initvm with the --devel option, you need to edit
>>> "/var/cache/elbe/devel/schema/dbsfed.xsd".  Both of these paths are _in
>>> the initvm_ not on the host.
>> 
>> Thanks for your answer, It is working.
>> I can now build an Ubuntu image.
>
> I try to build my own package through Elbe pbuilder for an Ubuntu 
> project image.
> The package succeed to build for an Debian project image and I succeed 
> the build the Ubuntu image without my package.
>
> When I add my package I got the error:
> The following signatures couldn't be verified because the public key is 
> not available: NO_PUBKEY
>
> I tried to add Ubuntu-keyring to the initvm, I tried to add key to the 
> xml file, but nothing worked.
>
> Is there a way to do this?
> Do I have to use an Ubuntu initvm to build my own packages for an Ubuntu 
> project?
>

Please embedded a snippet of your log.txt, where there are [ERROR], in
your mail between bars (---) so we can easily understand what's
happening.

I'm not familiar with pbuilder, so perhaps someone could help you out
there.  But at first glance there's a missing public key on your initvm.

Could you try to build your project again with <noauth>?  Commit
7feae4d9ed08a5dd750a1821fcbe4ad3b11cd3ad seems to make apt-secure more
relax about unsigned repos.

-- 
Olivier Dion
Linutronix GmbH | Bahnhofstrasse 3 | D-88690 Uhldingen-Mühlhofen