Hello!
In Packit, we believe that our Fedora automation is simple to set up,
but there are still many people who could benefit from it and are too
busy to onboard or just not sure if this is the right thing for their
package.
If you are one of those, the Packit team offers to prepare a
um 11:24 Uhr schrieb Frantisek Lachman
> :
> >
> > Thank you everyone for your responses!
> >
> > I have a few updates for you that made it to production this morning
> > as part of our weekly release cycle:
> >
> > * Thanks to Ankur Sinha, the pull r
Williamson
wrote:
>
> On Fri, 2023-09-15 at 16:02 +0200, Frantisek Lachman wrote:
> > Thanks Dan and Daniel for the responses. You both are right. For our
> > defence, this is always setup by an existing Fedora user (=human).
> >
> > I can't speak of rel-eng (and honest
implement the config option to let the user decide.
Here's the issue I've just created for that:
https://github.com/packit/packit/issues/2082
František
On Fri, Sep 15, 2023 at 4:10 PM Dan Horák wrote:
>
> On Fri, 15 Sep 2023 16:02:04 +0200
> Frantisek Lachman wrote:
>
> > Tha
I quite like these checks but wouldn't it be better to have these as
part of Fedora CI? (Or any other CI system running on dist-git PRs?)
František
On Fri, Sep 15, 2023 at 4:13 PM Daniel P. Berrangé wrote:
> If you wanted to be especially helpful, perhaps Packit could compare
> the old and new
uploading the source to the lookaside cache (or make
it configurable),
but the benefit of such automation is significantly reduced.
František
On Fri, Sep 15, 2023 at 3:39 PM Dan Horák wrote:
>
> On Fri, 15 Sep 2023 15:13:58 +0200
> Frantisek Lachman wrote:
>
> > Hi Petr,
> >
.g. CI
> purposes here:
>
> https://pagure.io/packaging-committee/issue/1132#comment-769233
>
> But without too much success.
>
> But of course, CI could also be improved to download the required sources, if
> there is proper source URL.
>
>
> Vít
>
>
> Dne 15. 09
not go through the whole pipeline without any
human approval.)
František
On Fri, Sep 15, 2023 at 3:13 PM Frantisek Lachman wrote:
>
> Hi Petr,
>
> we would like to avoid storing the archive in the lookaside cache before
> approving but the problem is that the CI on the PR (mai
Hi Petr,
we would like to avoid storing the archive in the lookaside cache before
approving but the problem is that the CI on the PR (mainly the scratch
build) does not work without the archive being in the lookaside cache
already. Once this becomes possible, we (=Packit) would be happy to do
Hello,
as Fabio has pointed out, you can use Packit to get your releases to
Fedora via pull-requests. Packit supports both push and newly also
pull workflow. (So you don't need to have access to the upstream
repository because it gets the info about the new version from Release
Monitoring.)
On Fri, May 6, 2022 at 4:12 PM Miro Hrončok wrote:
>
> That is the case for any rebuilds that happen in side tags. Most recently e.g.
> the boost rebuilds. Sometimes, maintainers do that for their own packages as
> well, but provenpackagers do that at larger scale. For Python packages,
> that'll
Yes, sure. Thanks for the example.
František
On Fri, May 6, 2022 at 2:21 PM Miro Hrončok wrote:
> On 06. 05. 22 11:06, Frantisek Lachman wrote:
> > You can also check the activities of the packit FAS user in Koji
> > (https://koji.fedoraproject.org/koji/userinfo?userID=
wrote:
> On 06. 05. 22 11:06, Frantisek Lachman wrote:
> > Hello all,
> >
> > You might have heard some rumours that the Packit team is working on
> automation
> > for downstream activities you need to do when working on a new release
> of a
> > package to
Hello all,
You might have heard some rumours that the Packit team is working on
automation for downstream activities you need to do when working on a new
release of a package to Fedora. And the rumours are true – I am really
pleased to announce that Packit now covers the whole workflow from
Thank you for your quick answer Aurélien!
I hope this workflow can work for us.
Maybe a few related questions (sorry if it is documented somewhere, any
link is welcome):
* What is the expiration period? Or, can we set the expiration date
ourselves?
* Can we use multiple tokens in parallel to
Hi Aurélien!
thanks for the hard work on the new Bodhi release!
I have a question on the non-interactive way of Bodhi authentication. I
understand that supporting OpenID is hard, but are there some other options
to support this workflow in the future?
A little bit of context:
* We, as a Packit
Hello all!
We would like to share with you what happened in Packit last year. Here,
two blog posts sum it up for you:
* https://packit.dev/posts/2021-features/
* https://packit.dev/posts/2021-in-numbers/
Thank all of you who has helped us to achieve that!
On behalf of the Packit team,
Hi,
The Bugzilla account has been created for the usercont user. I hope it is
not a problem that we use a mailing list as an email address for that
account.
Regards,
František
On Mon, Jul 27, 2020 at 11:21 AM Frantisek Lachman
wrote:
> Hi Pierre,
>
> I am really sorry about that.
Hi Pierre,
I am really sorry about that. This user is used for automation run by our
team (https://github.com/user-cont and https://github.com/packit-service/).
I'll take a look into that.
František
On Mon, Jul 27, 2020 at 10:44 AM Pierre-Yves Chibon
wrote:
> Good Morning Everyone,
>
> I have
19 matches
Mail list logo
