On Mon, Apr 29, 2024 at 01:44:05PM +0200, Fabio Valentini wrote:
> On Mon, Apr 29, 2024 at 1:28 PM Richard W.M. Jones wrote:
> >
> > On Sat, Apr 27, 2024 at 10:41:59PM +0200, Julian Sikorski wrote:
> > > Hello,
> > >
> > > I need to rebuild mame on F40 only for qt-6.7. On rawhide,
> > >
On Mon, Apr 29, 2024 at 11:44 AM Fabio Valentini wrote:
> No, this will make a Release like 2.1.fc40 - which is not what's
> needed (which would be 1.fc40.1).
> So it doesn't work because -e adds a component *before* the dist-tag,
> *and* because the main number is still incremented.
Since
On Mon, Apr 29, 2024 at 1:28 PM Richard W.M. Jones wrote:
>
> On Sat, Apr 27, 2024 at 10:41:59PM +0200, Julian Sikorski wrote:
> > Hello,
> >
> > I need to rebuild mame on F40 only for qt-6.7. On rawhide,
> > mame-0.265-1.fc41 is already built against it so I only need to
> > build
On Sat, Apr 27, 2024 at 10:41:59PM +0200, Julian Sikorski wrote:
> Hello,
>
> I need to rebuild mame on F40 only for qt-6.7. On rawhide,
> mame-0.265-1.fc41 is already built against it so I only need to
> build mame-0.265-1.fc40.1. Can it be done using %autorelease?
I don't think anyone answered
Fabio Valentini wrote:
> No, that's just wrong.
> The "upgrade path" (wrt/ NVRs) is no longer enforced across release
> boundaries. AFAIK, all supported release-upgrade methods now use
> distro-sync or something equivalent, so NVR-based "upgrade path" is just
> not important any more.
That just
On Mon, Apr 29, 2024 at 11:17 AM Kevin Kofler via devel
wrote:
>
> Michael J Gruber wrote:
> > A minor bump (as in %{?dist}[.]) only comes into play
> > if a "lower" branch needs to move forward without creating a version
> > ahead of a "higher" branch. And (independent of autorelease) you cannot
Michael J Gruber wrote:
> A minor bump (as in %{?dist}[.]) only comes into play
> if a "lower" branch needs to move forward without creating a version
> ahead of a "higher" branch. And (independent of autorelease) you cannot
> do that unless you use divergent git branches and cherry-picks in
>
Kevin Kofler via devel venit, vidit, dixit 2024-04-28 23:55:37:
> Julian Sikorski wrote:
> > I need to rebuild mame on F40 only for qt-6.7. On rawhide,
> > mame-0.265-1.fc41 is already built against it so I only need to build
> > mame-0.265-1.fc40.1. Can it be done using %autorelease?
>
> No,
Julian Sikorski wrote:
> I need to rebuild mame on F40 only for qt-6.7. On rawhide,
> mame-0.265-1.fc41 is already built against it so I only need to build
> mame-0.265-1.fc40.1. Can it be done using %autorelease?
No, which is why you should not be using %autorelease.
I would just replace
On Sat, Apr 27, 2024 at 11:51 PM Sandro wrote:
>
> On 27-04-2024 22:41, Julian Sikorski wrote:
> > I need to rebuild mame on F40 only for qt-6.7. On rawhide,
> > mame-0.265-1.fc41 is already built against it so I only need to build
> > mame-0.265-1.fc40.1. Can it be done using %autorelease?
>
>
On 27-04-2024 23:51, Sandro wrote:
On 27-04-2024 22:41, Julian Sikorski wrote:
I need to rebuild mame on F40 only for qt-6.7. On rawhide,
mame-0.265-1.fc41 is already built against it so I only need to build
mame-0.265-1.fc40.1. Can it be done using %autorelease?
Make an empty commit:
git
On 27-04-2024 22:41, Julian Sikorski wrote:
I need to rebuild mame on F40 only for qt-6.7. On rawhide,
mame-0.265-1.fc41 is already built against it so I only need to build
mame-0.265-1.fc40.1. Can it be done using %autorelease?
Make an empty commit:
git commit -m 'Rebuild for mame'
Hello,
I need to rebuild mame on F40 only for qt-6.7. On rawhide,
mame-0.265-1.fc41 is already built against it so I only need to build
mame-0.265-1.fc40.1. Can it be done using %autorelease?
Best regards,
Julian
--
___
devel mailing list --
13 matches
Mail list logo
