[yocto] [layerindex][PATCH 19/18] templates/*: staticfiles -> static

In Django 3.0 the staticfiles tag was changed to static Signed-off-by: Tim Orling --- templates/layerindex/classicstats.html | 2 +- templates/rrs/base_toplevel.html | 2 +- templates/rrs/maintainers.html | 2 +- templates/rrs/recipedetail.html| 2 +- templates/rrs/recipes.

Re: [yocto] Question of Yocto dunfell LTS period

Hello together, I would like to add a question to the topic: Why was the LTS period for dunfell extended? Can we expect the same for kirstone? Many greetings, Matthias -Ursprüngliche Nachricht- Von: yocto@lists.yoctoproject.org Im Auftrag von Chanho Park via lists.yoctoproject.org Ges

[yocto] [layerindex][PATCH 18/18] requirements.txt: bump all to latest

Run pip-upgrade and update all to latest Signed-off-by: Tim Orling --- requirements.txt | 36 ++-- 1 file changed, 18 insertions(+), 18 deletions(-) diff --git a/requirements.txt b/requirements.txt index 41a0b1e..77b1aa9 100644 --- a/requirements.txt +++ b/requir

[yocto] [layerindex][PATCH 17/18] Dockerfile: add back python2 dependencies

We have some layers and especially older releases that still support python2. Add python2 dependencies back to the container so that the older releases still function. Signed-off-by: Tim Orling --- Dockerfile | 5 + 1 file changed, 5 insertions(+) diff --git a/Dockerfile b/Dockerfile index

[yocto] [layerindex][PATCH 16/18] rrs: add 0030_alter_recipeupgrade_maintainer.py miagration

Signed-off-by: Tim Orling --- .../0030_alter_recipeupgrade_maintainer.py| 20 +++ 1 file changed, 20 insertions(+) create mode 100644 rrs/migrations/0030_alter_recipeupgrade_maintainer.py diff --git a/rrs/migrations/0030_alter_recipeupgrade_maintainer.py b/rrs/migrations/00

[yocto] [layerindex][PATCH 15/18] Dockerfile: fix warnings

* Define LANGUAGE * Set DEBIAN_FRONTEND=noninteractive before apt call Signed-off-by: Tim Orling --- Dockerfile | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/Dockerfile b/Dockerfile index f6623fa..25ab5ea 100644 --- a/Dockerfile +++ b/Dockerfile @@ -4,6 +4,7 @@ FROM debia

[yocto] [layerindex][PATCH 14/18] rrs/admin.py: drop curry import

Dropped in Django 3.0 [1] Suggested replacements are functools.partial() or functools.partialmethod() [2] [1] https://docs.djangoproject.com/en/4.0/releases/3.0/ [2] https://github.com/django/django/commit/5b1c389603a353625ae1603ba345147356336afb Signed-off-by: Tim Orling --- rrs/admin.py | 2

[yocto] [layerindex][PATCH v2 13/18] README.devel: update versions

This updated code-base should be compatible with Django 3.1 and obviously 3.2 (but not 3.0 or earlier). Django 3.2 requires Python 3.6+. With the upgrade to Celery 5, it is safer to recommend RabbitMQ 3.8.x, since that is what we are using. Signed-off-by: Tim Orling --- README.devel | 6 +++---

[yocto] [layerindex][PATCH v2 11/18] settings: set DEFAULT_AUTO_FIELD

New in Django 3.2 To quiet warnings, set DEFAULT_AUTO_FIELD to the default value 'django.db.models.AutoField' NOTE: The default value for newly created Django 3.2 projects is django.db.models.BigAutoField, but this causes the need for a migration in 'captcha'. Signed-off-by: Tim Orli

[yocto] [layerindex][PATCH v2 12/18] docker-compose: fix celery

In celery 5, the --workdir argument must come before the 'worker' subcommand. Without this, celery cannot load the layerindex module and this causes the celery container to continually restart. Signed-off-by: Tim Orling --- docker-compose.yml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-

[yocto] [layerindex][PATCH v2 10/18] requirements.txt: bump to Django 3.2 LTS

Upgrade to the latest Django 3.2.x LTS for extended support up until April 2024. Signed-off-by: Tim Orling --- requirements.txt | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/requirements.txt b/requirements.txt index 7704ac0..41a0b1e 100644 --- a/requirements.txt +++ b/requi

[yocto] [layerindex][PATCH v2 09/18] requirements.txt: update all to latest

Since we are on a "modern" version of Python in Debian buster container (3.7) and a modern version of Django (3.1.x) we should be able to run with the latest of all dependencies. Signed-off-by: Tim Orling --- requirements.txt | 34 +- 1 file changed, 17 insertions

[yocto] [layerindex][PATCH v2 07/18] requirements.txt: bump to Django 3.1

Another incremental upgrade towards 3.2 LTS Signed-off-by: Tim Orling --- requirements.txt | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/requirements.txt b/requirements.txt index 895994b..865960c 100644 --- a/requirements.txt +++ b/requirements.txt @@ -3,7 +3,7 @@ beautiful

[yocto] [layerindex][PATCH v2 08/18] docker-compose: bump mariadb to 10.3

10.2 was based on Ubuntu bionic 18.04, bumping to 10.3 as it is the first release on Ubuntu focal 20.04 Signed-off-by: Tim Orling --- docker-compose.yml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docker-compose.yml b/docker-compose.yml index 44260b6..3e16e95 100644 --- a

[yocto] [layerindex][PATCH v2 06/18] Updates for Django 3.0

* Update requirements.txt versions - Mostly update to latest pre-Django 3.1 versions * Fix deprecated axes.backends.AxesModelBackend - settings.py - docker/settings.py * Fix template syntax 'staticfiles' -> 'static' - base.html * Add migrations for layerbranch classicrecipe Signed-off-by:

[yocto] [layerindex][PATCH v2 05/18] requirements.txt: bump to Django 3.0

Incremental upgrade towards 3.2 LTS version. Signed-off-by: Tim Orling --- requirements.txt | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/requirements.txt b/requirements.txt index 1c2c4a1..ac69589 100644 --- a/requirements.txt +++ b/requirements.txt @@ -3,7 +3,7 @@ beautifu

[yocto] [layerindex][PATCH v2 04/18] layerindex/*: make all shebangs python3

Several scripts still had /usr/bin/env python Signed-off-by: Tim Orling --- layerindex/bulkchange.py | 2 +- layerindex/recipedesc.py | 2 +- layerindex/tools/import_classic_wiki.py | 2 +- layerindex/tools/import_wiki_layers.py| 2 +- layerindex/tools/sit

[yocto] [layerindex][PATCH v2 03/18] dockersetup.py: letsencrypt 2048 bit rsa

The minimum length for an RSA pem is 2048 for the dummy cert. Signed-off-by: Tim Orling --- dockersetup.py | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/dockersetup.py b/dockersetup.py index 04dec91..6a0ab67 100755 --- a/dockersetup.py +++ b/dockersetup.py @@ -483,7 +483,7

[yocto] [layerindex][PATCH v2 02/18] Dockerfile: cleanup, install python3-wheel

Remove duplicate python3-pip, etc. lines Need python3-wheel for bdist_wheel command Signed-off-by: Tim Orling --- Dockerfile | 4 +--- 1 file changed, 1 insertion(+), 3 deletions(-) diff --git a/Dockerfile b/Dockerfile index 8c4c847..f6623fa 100644 --- a/Dockerfile +++ b/Dockerfile @@ -24,10 +2

[yocto] [layerindex][PATCH v2 01/18] dockersetup.py: fix EMAIL_USE_SSL/TLS

From: Tim Orling Need to concatenate str(boolean), not bool Signed-off-by: Tim Orling --- dockersetup.py | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/dockersetup.py b/dockersetup.py index e45a846..04dec91 100755 --- a/dockersetup.py +++ b/dockersetup.py @@ -353,13 +3

[yocto] [layerindex][PATCH v2 00/18] Upgrade to Django 3.2 LTS and Celery 5

The current code base uses Django 2.2.x which will go out of extended support in April 2022, but also holds us back from updating a number of dependencies and is currently failing to update layers. Update to the current Django 3.2.11 LTS and also the latest Celery 5.2.3. Celery 4 has not had any c

[yocto] Installing specific systemd service file according to selected distro

Hello, I have a recipe that contains two service files( A and B) and I build for two distros where each include the foo recipe. When I build for distro A, I need to use foo's service file A but when I build distro B, I need to use foo's service file B. I could add some logic in the foo recipe to

Re: [yocto] [OE-core] Question of Yocto dunfell LTS period

On 1/14/22 2:36 AM, Jate Sujjavanich wrote: > I received the answer to this question in IRC on 10/29/2021. > > 16:06 >   > I saw a wiki edit that said dunfell's LTS period is now through April > 2024, but I've seen no announcements. A

Re: [yocto] [OE-core] Question of Yocto dunfell LTS period

I received the answer to this question in IRC on 10/29/2021. 16:06 < jatedev> I saw a wiki edit that said dunfell's LTS period is now through April 2024, but I've seen no announcements. Any truth to this rumor? 16:20

[yocto] Question of Yocto dunfell LTS period

Dear folks, I found the lts period of Yocto dunfell has been extended from 2022.04 to 2024.04[1]. AFAIK, a Yocto LTS version has 2 years period. I tried to find any notice regarding this but I just found Richard's e-mail[2] in last year. Can I find any thread or notice regarding this extension? [

Re: [yocto] Red alert but apparently harmless setscene errors

Richard Purdie escreveu no dia quinta, 13/01/2022 à(s) 21:53: > On Thu, 2022-01-13 at 19:37 +0100, Michael Opdenacker wrote: > > Hi Jose, > > > > Thanks for your advice! > > > > On 1/13/22 6:37 PM, Jose Quaresma wrote: > > > Hi, > > > > > > I've seen the same for some time now when building core-

Re: [yocto] Red alert but apparently harmless setscene errors

On Thu, 2022-01-13 at 19:37 +0100, Michael Opdenacker wrote: > Hi Jose, > > Thanks for your advice! > > On 1/13/22 6:37 PM, Jose Quaresma wrote: > > Hi, > > > > I've seen the same for some time now when building core-image-minimal > > with yocto state mirror and hashequiv servers. > > > > After

[yocto] wic create mkhybridiso core-image-minimal failure (honister)

I'm new to Yocto so this may be simple operator input. I built a qemux86-64 image with core-image-minimal using the honister branch of a day or so ago. The build finishes fine, however trying to use: *wic create mkhybridiso -e core-image-minimal,* gives the failure below. It looks like a director

Re: [yocto] problem with interpreter

Thanks man, I appreciate it. After reading your response, I understood the issue and was able to create a bunch of patches to mak it work. On Wed, Jan 12, 2022, 3:52 PM Ross Burton wrote: > On Wed, 12 Jan 2022 at 18:34, swhite wrote: > > I need to include an old open source project named judy f

Re: [yocto] Red alert but apparently harmless setscene errors

Hi Jose, Thanks for your advice! On 1/13/22 6:37 PM, Jose Quaresma wrote: > Hi, > > I've seen the same for some time now when building core-image-minimal > with yocto state mirror and hashequiv servers. > > After some investigation I think the root cause is some > bandwidth/connection limitation

Re: [yocto] Red alert but apparently harmless setscene errors

On Thu, Jan 13, 2022 at 11:23 AM Michael Opdenacker wrote: > > Hi, > > Sharing this before opening a bug if needed... > > I'm building the latest Poky ("core-image-minimal" plus a few extra > packages). > > I'm always getting the below setscene errors after upgrading my Poky > sources: > > ... >

Re: [yocto] Red alert but apparently harmless setscene errors

Hi, I've seen the same for some time now when building core-image-minimal with yocto state mirror and hashequiv servers. After some investigation I think the root cause is some bandwidth/connection limitation on the http yocto mirror. Reducing the BB_NUMBER_THREADS="1" to a single core solves ma

[yocto] Red alert but apparently harmless setscene errors

Hi, Sharing this before opening a bug if needed... I'm building the latest Poky ("core-image-minimal" plus a few extra packages). I'm always getting the below setscene errors after upgrading my Poky sources: ... WARNING: libffi-native-3.4.2-r0 do_populate_sysroot_setscene: Failed to fetch URL

[yocto] Minutes: Yocto Project Weekly Triage Meeting 1/13/2022

*Wiki: *https://wiki.yoctoproject.org/wiki/Bug_Triage *Attendees: *Alexandre, Bruce, Michael, Randy, Richard, Ross, Saul, Stephen, Steve, Tim, Trevor *ARs:* N/A *Notes:* - ~50% of AB workers have been switched to SSDs. Still too early to determine what effect they are having on failure rat

[yocto] gdb with a broken sdk

Hello! I'd like debug an application that is running on my target board. I installed gdbserver on the target, and I'd like to connect to it from a gdb instance running locally. Because of a broken 3rd party meta-layer, I'm currently unable to build the SDK. In short, the `populate_sdk` task fai

[yocto] perf compilation fails

Hi guys I'm no table to build correctly perf package. It looks like some sources have no been compiled because I'm getting an "undefined reference to" error. This problem has appeared since we have upgraded the version of yocto zeus. I'm getting this error arm-poky-linux-gnueabi-ld --sysr

Re: [yocto] Reproducible build website broken (CORS setting on git.yoctoproject.org?)

On 1/11/22 8:48 PM, Joshua Watt wrote: > Michael, > > I noticed that the > https://www.yoctoproject.org/reproducible-build-results/ website went > down (it always shows "Error fetching test results"). I did a little > debugging and I think that the CORS setting on git.yoctoproject.org is > not all

Re: [yocto] The "/etc/resolv.conf" file becomes empty after each restart #yocto

Hello, Some more details would be needed (ie. you have systemd?), but this could be a good point to start: https://wiki.archlinux.org/title/Systemd-resolved (ie. see a bit down, like: https://wiki.archlinux.org/title/Systemd-resolved#Manually ) Cheers, Federico Il giorno gio 13 gen 2022 alle ore

[yocto] The "/etc/resolv.conf" file becomes empty after each restart #yocto

Hi, I assume it shouldn't be empty resov. conf. Manually I am updating nameserver always. but when I reboot my machine it's empty. So for this, I want to make permanent my nameserver always. I have added packages support IMAGE_INSTALL_append = " resolvconf" but I am not able to fix this solutio