Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: yann.morin@orange.com
To: Peter Korsgaard <peter@korsgaard.com>,
	Thomas Petazzoni <thomas.petazzoni@bootlin.com>,
	Romain Naour <romain.naour@smile.fr>,
	Julien Olivain <ju.o@free.fr>,
	Arnout Vandecappelle <arnout@rnout.be>
Cc: buildroot <buildroot@buildroot.org>
Subject: Re: [Buildroot] [autobuild.buildroot.org] Your daily results for 2026-04-19
Date: Mon, 20 Apr 2026 11:32:10 +0200	[thread overview]
Message-ID: <aeXymikPfNmmnA67@yd-6wlzhs3> (raw)
In-Reply-To: <69e59cd7.050a0220.1ab584.974e@mx.google.com>

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

       reply	other threads:[~2026-04-20  9:32 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <69e59cd7.050a0220.1ab584.974e@mx.google.com>
2026-04-20  9:32 ` yann.morin [this message]
2026-04-20 10:12   ` [Buildroot] [autobuild.buildroot.org] Your daily results for 2026-04-19 Peter Korsgaard
2026-04-20 11:48     ` Thomas Petazzoni via buildroot
2026-04-20 12:22       ` Peter Korsgaard
2026-04-20 12:30       ` yann.morin

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=aeXymikPfNmmnA67@yd-6wlzhs3 \
    --to=yann.morin@orange.com \
    --cc=arnout@rnout.be \
    --cc=buildroot@buildroot.org \
    --cc=ju.o@free.fr \
    --cc=peter@korsgaard.com \
    --cc=romain.naour@smile.fr \
    --cc=thomas.petazzoni@bootlin.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox