I am considering using Packit-as-a-Service [1] for an upstream
project, as the maintainer of the project suggested managing the RPM
spec file on the upstream's repository in Github.
Could you tell me some case studies of the upstream project using
Packit-as-a-Service?
I know rebase-helper [2] is u
> * How to manage a RPM spec file on the upstream repository,
synchronizing it with Fedora rawhide's one.
As my first step, I am trying to use Packit, having separately managed
the RPM spec file that is only used to run the %check section on the
Fedora scratch build at the pull-request in the upst
Hi Jun, thanks for reaching out! I'd suggest CCing someone from our
team in future to make sure we see your message. It's good though you
started the discussion on fedora-devel.
On Thu, Apr 2, 2020 at 8:54 PM Jun Aruga wrote:
>
> I am considering using Packit-as-a-Service [1] for an upstream
> pr
On 08. 04. 20 11:33, Tomas Tomecek wrote:
My questions are
* How to manage a RPM spec file on the upstream repository,
synchronizing it with Fedora rawhide's one.
Ideally, you'd maintain the spec upstream and packit will copy [1] it
for you when you perform releases.
Once again I would like to
On Wed, 2020-04-08 at 11:39 +0200, Miro Hrončok wrote:
> On 08. 04. 20 11:33, Tomas Tomecek wrote:
> > > My questions are
> > > * How to manage a RPM spec file on the upstream repository,
> > > synchronizing it with Fedora rawhide's one.
> > Ideally, you'd maintain the spec upstream and packit will
On 08. 04. 20 12:26, Ernestas Kulik wrote:
As someone who also maintains the code for multiple packages, I say
tough luck. The workflow for keeping upstream changes buildable (and
having the ability to test the changes) and downstream package
specification in sync with said changes could not be w
