Re: integrate bluez with ISAR

[Uladzimir Bely <ubely@ilbers.de>]

In mail from пятница, 11 ноября 2022 г. 10:32:18 +03 user 'Balasubramanian 
Sundaram' via isar-users wrote:
> Hi Jan
> 
> *Still It is not getting included in isar*
> 
> WARNING: bluez-1.0-r0 do_fetch: Failed to fetch URL
> https://sources.debian.org/patches/bluez/5.55-3.1/, attempting MIRRORS if
> available
> ERROR: bluez-1.0-r0 do_fetch: Fetcher failure for URL: '
> https://sources.debian.org/patches/bluez/5.55-3.1/'. The fetch command
> returned success for url https://sources.debian.org/patches/bluez/5.55-3.1/
> but /work/build/downloads/sources.debian.org.patches.bluez.5.55-3.1.
> doesn't exist?!
> ERROR: bluez-1.0-r0 do_fetch: Fetcher failure for URL: '
> https://sources.debian.org/patches/bluez/5.55-3.1/'. Unable to fetch URL
> from any source.
> ERROR: Logfile of failure stored in:
> /work/build/tmp/work/cip-core-buster-armhf/bluez/1.0-r0/temp/log.do_fetch.91
> 7 ERROR: Task (/repo/recipes-core/bluez/bluez.bb:do_fetch) failed with exit
> code '1'
> NOTE: Tasks Summary: Attempted 20 tasks of which 19 didn't need to be rerun
> and 1 failed.
> 
> Summary: 1 task failed:
>   /repo/recipes-core/bluez/bluez.bb:do_fetch
> Summary: There was 1 WARNING message shown.
> Summary: There were 2 ERROR messages shown, returning a non-zero exit code.
> builder@05bb7ca9f421:/work/build$
> 
> 
> *Is there anything to change in the .bb file*
> 
> # This software is a part of ISAR.
> # Copyright (c) Siemens AG, 2019
> #
> # SPDX-License-Identifier: MIT
> 
> inherit dpkg
> 
> # This will fetch and unpack the sources from upstream Debian.
> # Note that you can also choose a version but have to pick the exact one
> # i.e. "apt://bluez".
> # You may also select the desired release in case multiples are configured
> and
> # you do want to pin the version: "apt://hello/buster".
> #SRC_URI = "apt://bluez-5.50"
> SRC_URI = "https://sources.debian.org/patches/bluez/5.55-3.1/"
> 
> 
> 
> 
> 
> MAINTAINER = "isar-users <isar-users@googlegroups.com>"
> #CHANGELOG_V = "<orig-version>+isar"
> 
> DEB_BUILD_OPTIONS += "${@ 'nocheck' if d.getVar('ISAR_CROSS_COMPILE', True)
> == '1' else '' }"
> 
> do_prepare_build() {
> deb_add_changelog
> # this seems to be a build dep missing in the upstream control file
> if ! grep texinfo ${S}/debian/control; then
> sed -i -e 's/Build-Depends:/Build-Depends: texinfo,/g' ${S}/debian/control
> fi
> }
> 
> 
> can you give any file to need to do exact changes for including the bluez
> 

You don't need your own recipe for blues (except you want to add some stuff 
and maintain it by your own).

Just install Debian package via IMAGE_PREINSTALL in your `local.conf` (or in 
image recipe or somewhere else, depending on your project structure).

> Regards
> 
> On Thu, Nov 10, 2022 at 9:42 PM Jan Kiszka <jan.kiszka@siemens.com> wrote:
> > On 10.11.22 13:37, 'Balasubramanian Sundaram' via isar-users wrote:
> > >  Hi Team,
> > > 
> > > Iam using ISAR build system i'm trying to integrate bluez but iam
> > > getting following error
> > > image.png
> > > and this is my bb file for it anything is missing
> > > image.png
> > 
> > I think this question was raised elsewhere already, but it is very
> > essential: WHY do you want to fork bluez away from Debian mainline? You
> > will inherit maintenance and testing efforts that can be critical,
> > specifically for product development. If you have a bug report against
> > bluez or the Debian package, file that first. Ideally, the issue will be
> > resolved and the new package will be available before you are done with
> > rebuilding your own one.
> > 
> > Jan
> > 
> > PS: Please share logs, not screenshots, whenever technically possible
> > (like in this case).
> > 
> > --
> > Siemens AG, Technology
> > Competence Center Embedded Linux