Re: [Buildroot] [autobuild.buildroot.org] Your daily results for 2026-04-19

Re: [Buildroot] [autobuild.buildroot.org] Your daily results for 2026-04-19

[yann.morin]

Peter, Thomas, All,

On 2026-04-20 03:26 -0000, Buildroot Notifications spake thusly:
>       gpsd |  DISTRO  | https://release-monitoring.org/project/006846 | 3.27.2       | 3.27.5
>  mosquitto |  DISTRO  | https://release-monitoring.org/project/006078 | 2.0.22       | 2.1.2

Not sure what is happening with this weekly outdated packages notice:

* gpsd has been updated end of February, with  commit 13daf36ee2dc
  (package/gpsd: Bump version to 3.27.5),
* mosquitto since mid-march, more than a month ago now, with commit
  583a02e39888 (package/mosquitto: bump to version 2.1.2).

Is the git-pull before the check is made still working?

Regards,
Yann E. MORIN.

-- 
                                        ____________
.-----------------.--------------------:       _    :------------------.
|  Yann E. MORIN  | Real-Time Embedded |    __/ )   | /"\ ASCII RIBBON |
|                 | Software  Designer |  _/ - /'   | \ / CAMPAIGN     |
| +33 638.411.245 '--------------------: (_    `--, |  X  AGAINST      |
| yann.morin (at) orange.com           |_="    ,--' | / \ HTML MAIL    |
'--------------------------------------:______/_____:------------------'

____________________________________________________________________________________________________________
Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc
pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le signaler
a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles d'alteration,
Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci.

This message and its attachments may contain confidential or privileged information that may be protected by law;
they should not be distributed, used or copied without authorisation.
If you have received this email in error, please notify the sender and delete this message and its attachments.
As emails may be altered, Orange is not liable for messages that have been modified, changed or falsified.
Thank you.
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot

Re: [Buildroot] [autobuild.buildroot.org] Your daily results for 2026-04-19

[Peter Korsgaard]

>>>>> "yann" == yann morin <yann.morin@orange.com> writes:

 > Peter, Thomas, All,
 > On 2026-04-20 03:26 -0000, Buildroot Notifications spake thusly:
 >> gpsd | DISTRO | https://release-monitoring.org/project/006846
 >> | 3.27.2 | 3.27.5
 >> mosquitto |  DISTRO  | https://release-monitoring.org/project/006078 | 2.0.22       | 2.1.2

 > Not sure what is happening with this weekly outdated packages notice:

 > * gpsd has been updated end of February, with  commit 13daf36ee2dc
 >   (package/gpsd: Bump version to 3.27.5),
 > * mosquitto since mid-march, more than a month ago now, with commit
 >   583a02e39888 (package/mosquitto: bump to version 2.1.2).

 > Is the git-pull before the check is made still working?

Yes, I noticed the same and mailed Thomas as I was away on holiday last
week. I'm back now but with a big email backlog, and I will take a look
once I get a bit of time unless someone else beats me to it.

-- 
Bye, Peter Korsgaard
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot

Re: [Buildroot] [autobuild.buildroot.org] Your daily results for 2026-04-19

[Thomas Petazzoni via buildroot]

On Mon, Apr 20, 2026 at 12:12:15PM +0200, Peter Korsgaard wrote:

> Yes, I noticed the same and mailed Thomas as I was away on holiday last
> week. I'm back now but with a big email backlog, and I will take a look
> once I get a bit of time unless someone else beats me to it.

We figured this out with Titouan earlier today. The "next" branch was
still referenced in the list of branches in
buildroot-test/web/branches, and the script takes the "next" branch as
the baseline when doing this "outdated packages" check. But since next
no longer exists on the main Buildroot Git repo, it was using whatever
old next branch was there.

Immediate fix: drop next from buildroot-test/web/branches (which is
the file telling the autobuilders which branches to test).

Long-term fix: somehow automate this.

Thomas
-- 
Thomas Petazzoni, co-owner and CEO, Bootlin
Embedded Linux and Kernel engineering and training
https://bootlin.com
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot

Re: [Buildroot] [autobuild.buildroot.org] Your daily results for 2026-04-19

[Peter Korsgaard]

>>>>> "Thomas" == Thomas Petazzoni <thomas.petazzoni@bootlin.com> writes:

Hi,

 > We figured this out with Titouan earlier today. The "next" branch was
 > still referenced in the list of branches in
 > buildroot-test/web/branches, and the script takes the "next" branch as
 > the baseline when doing this "outdated packages" check. But since next
 > no longer exists on the main Buildroot Git repo, it was using whatever
 > old next branch was there.

 > Immediate fix: drop next from buildroot-test/web/branches (which is
 > the file telling the autobuilders which branches to test).

Ups, I normally update it but must have forgotten when I released
2026.02. Thanks for fixing it!

I have also replaced 2025.11.x with 2026.02.x so it get monitored and
tested by the autobuilders.


 > Long-term fix: somehow automate this.

Hmm, that does not seem trivial to do.

-- 
Bye, Peter Korsgaard
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot

Re: [Buildroot] [autobuild.buildroot.org] Your daily results for 2026-04-19

[yann.morin]

Thomas, All,

On 2026-04-20 13:48 +0200, Thomas Petazzoni spake thusly:
> We figured this out with Titouan earlier today. The "next" branch was
> still referenced in the list of branches in
> buildroot-test/web/branches, and the script takes the "next" branch as
> the baseline when doing this "outdated packages" check. But since next
> no longer exists on the main Buildroot Git repo, it was using whatever
> old next branch was there.

Ah, thanks for the explanations.

> Immediate fix: drop next from buildroot-test/web/branches (which is
> the file telling the autobuilders which branches to test).

... and maybe add the commit sha1 that was used to generate the list
in the mail, so that it is easier to see what's going on?

> Long-term fix: somehow automate this.

Maybe ask an AI agent to do it in your stead? ;-) Arf-arf-arf...

Regards,
Yann E. MORIN.

-- 
                                        ____________
.-----------------.--------------------:       _    :------------------.
|  Yann E. MORIN  | Real-Time Embedded |    __/ )   | /"\ ASCII RIBBON |
|                 | Software  Designer |  _/ - /'   | \ / CAMPAIGN     |
| +33 638.411.245 '--------------------: (_    `--, |  X  AGAINST      |
| yann.morin (at) orange.com           |_="    ,--' | / \ HTML MAIL    |
'--------------------------------------:______/_____:------------------'

____________________________________________________________________________________________________________
Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc
pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le signaler
a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles d'alteration,
Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci.

This message and its attachments may contain confidential or privileged information that may be protected by law;
they should not be distributed, used or copied without authorisation.
If you have received this email in error, please notify the sender and delete this message and its attachments.
As emails may be altered, Orange is not liable for messages that have been modified, changed or falsified.
Thank you.
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot