Hi

I just noticed that the 2.1.1 release reports itself as 2.1.0

Cheers


Bob

Thanks and no worries.

Also friendly greetings - this from a hot Brisbane, Australia!

Bob

On Tue, 18 Feb 2020 at 10:47, Leon Plickat
<leonhenrik.plickat@stud.uni-goettingen.de> wrote:
>
> On Di 18.02.2020, 08:13, Bob Hepple wrote:
> > Here you go, hopefully final until the next release (if you could let
> > me know when you release I can trigger the packaging).
>
> LavaLauncher is essentially feature complete. There are a few things I'd like to

double whoops! Sorry about that; doing too many things at once!!!

Here you go, hopefully final until the next release (if you could let
me know when you release I can trigger the packaging).

Cheers


Bob


Name:     lavalauncher
Version:  1.6
Release:  3%{?dist}.wef

whoops!

COPR is fixed up, here is the new spec file:

Name:     lavalauncher
Version:  1.6
Release:  2%{?dist}.wef
Summary:  LavaLauncher is a simple launcher for Wayland
License:  GPL2
URL:      https://git.sr.ht/~leon_plickat/lavalauncher

# use this to fetch the source: spectool -g lavalauncher.spec
Source0:  %{url}/archive/v%{version}/%{name}-%{version}.tar.gz

Hi Leon,

Your code change worked very well - we now have some builds available
for lavalaunch-1.6 for fedora-30 and 31 at
https://copr.fedorainfracloud.org/coprs/wef/lavalauncher/builds/

To install lavalauncher on f-30/31 a user need simply do this:

sudo dnf copr enable wef/lavalauncher
sudo dnf install lavalauncher

If any other RPM builds are wanted, let me know - it should just be a
case of ticking some boxes and rebuilding.

Thanks for that - I'll take a look later today.

On Sun, 16 Feb 2020 at 23:22, Leon Plickat
<leonhenrik.plickat@stud.uni-goettingen.de> wrote:
>
> On So 16.02.2020, 15:08, Bob Hepple wrote:
> > Yeah - I doubt the fedora guys would accept that (modifying the
> > compiler options, that is), they're pretty starchy when it comes to
> > that sort of thing.
> >
> > I could compile it into my own very obscure COPR repo without using
> > the fedora macros. I think that you'd be better served by fixing the
> > compiler error and having it in fedora proper. Your choice, of course.
>