From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: Afshin Pir <Afshin.Pir@gallagher.com>
Cc: "buildroot@buildroot.org" <buildroot@buildroot.org>
Subject: Re: [Buildroot] Update schedule of sources.buildroot.org
Date: Tue, 1 Aug 2023 12:11:18 +0200 [thread overview]
Message-ID: <20230801121118.72610acf@windsurf> (raw)
In-Reply-To: <SY2PR01MB2778500474B41D29E8E7D54C940AA@SY2PR01MB2778.ausprd01.prod.outlook.com>
Hello Afshin,
On Tue, 1 Aug 2023 04:36:24 +0000
Afshin Pir <Afshin.Pir@gallagher.com> wrote:
> I wonder when http://sources.buildroot.org is updated normally.
> Because from what I see, it is normally updates pretty quickly when
> packages are changed, but there has been no update for last 2 weeks
> while some packages like openssh have been updated.
It is normally updated constantly. I see right now the script from
Peter Korsgaard is running on the machine to do the update. But I
indeed see in http://sources.buildroot.net/openssh/ that the latest
openssh version is not there even though the bump was done quite some
time ago. I'll try to see what's going on, though it's usually Peter
that takes care of maintaining this part of the infrastructure, so I'm
not super familiar with it.
Best regards,
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
next prev parent reply other threads:[~2023-08-01 10:11 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-01 4:36 [Buildroot] Update schedule of sources.buildroot.org Afshin Pir
2023-08-01 10:11 ` Thomas Petazzoni via buildroot [this message]
2023-08-01 21:30 ` Afshin Pir
2023-08-02 22:30 ` Afshin Pir
2023-08-03 18:51 ` Yann E. MORIN
2023-08-24 21:10 ` Peter Korsgaard
2023-08-24 21:16 ` Thomas Petazzoni via buildroot
2023-08-24 21:23 ` Peter Korsgaard
2023-08-24 21:26 ` Thomas Petazzoni via buildroot
2023-08-25 6:56 ` Peter Korsgaard
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=20230801121118.72610acf@windsurf \
--to=buildroot@buildroot.org \
--cc=Afshin.Pir@gallagher.com \
--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