public inbox for git-commits@fedoraproject.org
help / color / mirror / Atom feed
From: Benson Muite <fed500@fedoraproject.org>
To: git-commits@fedoraproject.org
Subject: [rpms/lfortran] epel10: Version bump 0.49.0 (bz# 2352738)
Date: Thu, 16 Jul 2026 14:32:02 GMT [thread overview]
Message-ID: <178421232238.1.8053575184740037861.rpms-lfortran-4b2df81909a0@fedoraproject.org> (raw)
A new commit has been pushed.
Repo : rpms/lfortran
Branch : epel10
Commit : 4b2df81909a0bae6fff70f85047e96c9a67306f7
Author : Benson Muite <fed500@fedoraproject.org>
Date : 2025-03-16T08:41:49+03:00
Stats : +9/-17 in 3 file(s)
URL : https://src.fedoraproject.org/rpms/lfortran/c/4b2df81909a0bae6fff70f85047e96c9a67306f7?branch=epel10
Log:
Version bump 0.49.0 (bz# 2352738)
---
diff --git a/.gitignore b/.gitignore
index 82a1a50..6b0f01f 100644
--- a/.gitignore
+++ b/.gitignore
@@ -17,3 +17,4 @@
/lfortran-0.46.0.tar.gz
/lfortran-0.47.0.tar.gz
/lfortran-0.48.0.tar.gz
+/lfortran-0.49.0.tar.gz
diff --git a/lfortran.spec b/lfortran.spec
index 21a4be7..a52aa45 100644
--- a/lfortran.spec
+++ b/lfortran.spec
@@ -1,6 +1,6 @@
-Version: 0.48.0
+Version: 0.49.0
Name: lfortran
-Release: 2%{?dist}
+Release: 1%{?dist}
Summary: A modern Fortran compiler
# Main code is BSD-3-Clause
@@ -9,19 +9,11 @@ Summary: A modern Fortran compiler
License: BSD-3-Clause AND Apache-2.0 WITH LLVM-exception
URL: https://lfortran.org/
Source0: https://github.com/lfortran/lfortran/releases/download/v%{version}/lfortran-%{version}.tar.gz
-Patch0: https://patch-diff.githubusercontent.com/raw/lfortran/lfortran/pull/6571.patch
+#Patch0: https://patch-diff.githubusercontent.com/raw/lfortran/lfortran/pull/6571.patch
# https://github.com/lfortran/lfortran/issues/2981
ExclusiveArch: x86_64
%global with_jupyter 1
-%if 0%{?fedora} < 39
-# F38 has no jupyterlab
-%global with_jupyter 0
-%endif
-%if 0%{?fedora} > 39
-# F41 has too new xeus version
-%global with_jupyter 0
-%endif
BuildRequires: binutils-devel
BuildRequires: bison
@@ -36,13 +28,8 @@ BuildRequires: llvm-devel
BuildRequires: python3-devel
BuildRequires: rapidjson-devel
BuildRequires: re2c
-%if 0%{?fedora} > 39
BuildRequires: zlib-ng-compat-devel
BuildRequires: zlib-ng-compat-static
-%else
-BuildRequires: zlib-devel
-BuildRequires: zlib-static
-%endif
%if %{with_jupyter}
# Needed for Jupyter kernel
BuildRequires: cppzmq-devel
@@ -165,9 +152,13 @@ This package contains the jupyter kernel for %{name}.
%files jupyter
%dir %{_datadir}/jupyter/kernels/fortran
%{_datadir}/jupyter/kernels/fortran/kernel.json
+%{_datadir}/jupyter/kernels/fortran/logo-svg.svg
%endif
%changelog
+* Sun Mar 16 2025 Benson Muite <fed500@fedoraproject.org> - 0.49.0-1
+- Version bump to v0.49.0 (bug #2352738)
+
* Mon Mar 10 2025 Christoph Junghans <junghans@votca.org> - 0.48.0-2
- Fix build with llvm-20
diff --git a/sources b/sources
index e2c19e8..cfa6b27 100644
--- a/sources
+++ b/sources
@@ -1 +1 @@
-SHA512 (lfortran-0.48.0.tar.gz) = 916f5134a83cc16006a99d80851f7588eafbaca63929c441c5426594363bf8659bfa2b5fd1fecdf69b2d101aa0c00f6349e6aadb51039e7a9596b8802048cd74
+SHA512 (lfortran-0.49.0.tar.gz) = 37e695ff0e649309ccf9d0d4543841aa09c56b5588a0eae68e1f8d898d0342ec0587e86eed462b0e0325016d673cb4ba41d43d28aac3c18725bb781a37c5e239
reply other threads:[~2026-07-16 14:32 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=178421232238.1.8053575184740037861.rpms-lfortran-4b2df81909a0@fedoraproject.org \
--to=fed500@fedoraproject.org \
--cc=git-commits@fedoraproject.org \
/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