Re: is there an offshoot or branch of early Fedora for simple UI
On 1/9/22 14:43, None Business wrote: I use(d) fedora to run my IDEs ( c++), now it is all floating-contracting windows , with gazilion 'drag-your-window' nonsense . I guess I am not cool enough to use this clusterfu..k, it is simply unusable for me , so I am looking for something that looks like early Fedora to simplify my development . Is there Fedora offshoot with a sane UI ? This is the wrong list and a rather rudely put question. It's not really clear what you're complaining about, but maybe try the gnome-classic session instead. ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Re: Self Introduction: Malcolm Inglis (mcinglis)
On Sat, Jan 08, 2022 at 10:56:50PM +0200, Otto Urpelainen wrote: > > Ok, I start to see this better now. I was under the impression that both > FE-NEEDSPONSOR and the tracker were on equal footing and generally speakin, > receive similar attention from the sponsors. But, if the reason for having > the tracker is (or: originally was) just the co-maintainer requests, where > the primary maintainer actually mentors the new packager, then it makes > sense that just a couple of sponsors keep an eye on that tracker and accept > the request on behalf of the primary maintainers. > > > Additionally, I fear it would also leed to 'HI, make me a packager' type > > tickets (with no other info). We could of course close those or ask for > > more info, but then someone has to manage that. > > One easy thing that can be done now is to add an issue template to the > tracker repo. Thats an excellent idea. I'll try and add one. > > > > Apart from co-maintenance, the tracker is also important for the case > > > where > > > somebody wants to become a pacakger to rescue an orphaned package. > > > > Well, in the past we have asked such folks to file a review request and > > get the orphaned package re-reviewed. > > Interesting. Previously, there was no documented process for handling this > case at all, so I wrote section "Adopting orphaned packages" [1] to How to > Get Sponsored page. As you can see, that section currently points to the > tracker. Do you think we should change that to ask for a re-review? The > current wording is not just my invention, though. There was discussion on > devel first, and the change went through a docs pull request. > > In case a review is required, I would like to understand, why? My > understanding was this: Orphaned packages are assumed to be is acceptable > condition, because existing maintainers can adopt them without a review. The > new packager are assumed to be equal to existing maintainers, because > somebody has agreed to sponsor them and is available for mentoring as > needed. Some caution is certainly needed, since some orphaned packages can > be minefields, it just did not occur to me that package review would be the > appropriate safeguard here. I think the idea was that the person who wanted to take on the orphaned package could suggest improvements to the existing package to prove that they know guidelines, etc. At least it shows that they could show they know the spec file and how to file a review, but I agree this is somewhat 'make work'. kevin signature.asc Description: PGP signature ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Re: is there an offshoot or branch of early Fedora for simple UI
On Sun, Jan 9, 2022 at 6:58 PM Peter Boy wrote: > > > > > Am 10.01.2022 um 00:25 schrieb Nico Kadel-Garcia : > > > > ... it has gotten out of hand. > > Indeed. When Gnome 3 hit Fedora years ago, I tried hard, but then decided > heavy heartedly to switch all my desktops and laptops to macOS. It has > remained that way until today. But I’m happy with Fedora Server for all our > servers. There is no window at all :-) > > > Is it worth trying to > > bring back "tvtwm", as an even lighter andmore stable window manager > > with very good hooks for managing multiple virtual windows? > > Taking the physical screen as a viewport onto a much larger, continuous > virtual screen is a very interesting idea. But if I understand the Wikipedia > article correctly, the number of users is currently very small. A port is > probably not very likely. But really a nice idea. Didn’t know that one. I used it last year. It's *really, really* stable. ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Re: is there an offshoot or branch of early Fedora for simple UI
> Am 10.01.2022 um 00:25 schrieb Nico Kadel-Garcia : > > ... it has gotten out of hand. Indeed. When Gnome 3 hit Fedora years ago, I tried hard, but then decided heavy heartedly to switch all my desktops and laptops to macOS. It has remained that way until today. But I’m happy with Fedora Server for all our servers. There is no window at all :-) > Is it worth trying to > bring back "tvtwm", as an even lighter andmore stable window manager > with very good hooks for managing multiple virtual windows? Taking the physical screen as a viewport onto a much larger, continuous virtual screen is a very interesting idea. But if I understand the Wikipedia article correctly, the number of users is currently very small. A port is probably not very likely. But really a nice idea. Didn’t know that one. ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Re: ppc64le build failure on F34 and EPEL8, EPEL8-next only
Thank you, and what about EPEL8 build failure? Such branch is not affected by that bug https://koji.fedoraproject.org/koji/taskinfo?taskID=81021476 Thank you ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Re: is there an offshoot or branch of early Fedora for simple UI
On Sun, Jan 9, 2022 at 6:02 PM Peter Boy wrote: > > Am 09.01.2022 um 23:43 schrieb None Business : > > > > I use(d) fedora to run my IDEs ( c++), now it is all floating-contracting > > windows , with gazilion 'drag-your-window' nonsense . I guess I am not cool > > enough to use this clusterfu..k, it is simply unusable for me , so I am > > looking for something that looks like early Fedora to simplify my > > development . Is there Fedora offshoot with a sane UI ? > > ___ > > > Apart from the fact that your style is not particularly respectful and > cooperative, others can't get along with the Gnome interface either. They > have developed alternatives, which now also work very stable and reliable. > Check out https://spins.fedoraproject.org/. There you will find more > "traditional" desktops, e.g. Mate or Cinnamon. > > You can install the desktops parallel to your current Gnome and try them out. > So you don't need to reinstall. Crudities aside, it has gotten out of hand. Is it worth trying to bring back "tvtwm", as an even lighter andmore stable window manager with very good hooks for managing multiple virtual windows? ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Re: is there an offshoot or branch of early Fedora for simple UI
> Am 09.01.2022 um 23:43 schrieb None Business : > > I use(d) fedora to run my IDEs ( c++), now it is all floating-contracting > windows , with gazilion 'drag-your-window' nonsense . I guess I am not cool > enough to use this clusterfu..k, it is simply unusable for me , so I am > looking for something that looks like early Fedora to simplify my > development . Is there Fedora offshoot with a sane UI ? > ___ Apart from the fact that your style is not particularly respectful and cooperative, others can't get along with the Gnome interface either. They have developed alternatives, which now also work very stable and reliable. Check out https://spins.fedoraproject.org/. There you will find more "traditional" desktops, e.g. Mate or Cinnamon. You can install the desktops parallel to your current Gnome and try them out. So you don't need to reinstall. ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
is there an offshoot or branch of early Fedora for simple UI
I use(d) fedora to run my IDEs ( c++), now it is all floating-contracting windows , with gazilion 'drag-your-window' nonsense . I guess I am not cool enough to use this clusterfu..k, it is simply unusable for me , so I am looking for something that looks like early Fedora to simplify my development . Is there Fedora offshoot with a sane UI ? ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
is there an offshoot or branch of early Fedora for simple UI
I use(d) fedora to run my IDEs ( c++), now it is all floating-contracting windows , with gazilion 'drag-your-window' nonsense . I guess I am not cool enough to use this clusterfu..k, it is simply unusable for me , so I am looking for something that looks like early Fedora to simplify my development . Is there Fedora offshoot with a sane UI ? ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
is there an offshoot or branch of early Fedora for simple UI
I use(d) fedora to run my IDEs ( c++), now it is all floating-contracting windows , with gazilion 'drag-your-window' nonsense . I guess I am not cool enough to use this clusterfu..k, it is simply unusable for me , so I am looking for something that looks like early Fedora to simplify my development . Is there Fedora offshoot with a sane UI ? ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
[Bug 2038692] Please branch and build perl-Lingua-EN-Sentence for EPEL-9
https://bugzilla.redhat.com/show_bug.cgi?id=2038692 Xavier Bachelot changed: What|Removed |Added Status|NEW |ASSIGNED --- Comment #3 from Xavier Bachelot --- https://pagure.io/releng/fedora-scm-requests/issue/40672 -- You are receiving this mail because: You are on the CC list for the bug. https://bugzilla.redhat.com/show_bug.cgi?id=2038692 ___ perl-devel mailing list -- perl-devel@lists.fedoraproject.org To unsubscribe send an email to perl-devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/perl-devel@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Re: ppc64le build failure on F34 and EPEL8, EPEL8-next only
On Sun, 9 Jan 2022 16:52:29 +0100 Germano Massullo wrote: > Good day. darktable maintainer here. > I am experiencing a ppc64le build failure on F34 and EPEL8, EPEL8-next only. > https://koji.fedoraproject.org/koji/taskinfo?taskID=81021540 > https://koji.fedoraproject.org/koji/taskinfo?taskID=81021476 > On F34 the error is > > /builddir/build/BUILD/darktable-3.8.0/src/iop/channelmixerrgb.c: In function > '_convert_GUI_colors.part.0.constprop': > /builddir/build/BUILD/darktable-3.8.0/src/iop/channelmixerrgb.c:3085:1: > internal compiler error: in patch_jump_insn, at cfgrtl.c:1299 > 3085 | } >| ^ > Please submit a full bug report, > with preprocessed source if appropriate. > > Other branches can successfully build on aarch64, x86_64, pcc64le. > Do you know what can be the problem? the ICE is an old bug (don't have the bz number handy), that already got fixed, but the fixed gcc hasn't been built for F-34 (F-34 is behind F-35 or rawhide) Dan ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Re: Does anybody still use `starship'?
Igor Raits kirjoitti 9.1.2022 klo 13.24: Hello, I'm interested to hear if there are any users of the `starship' application here in Fedora that consume it from the repositories. Please speak up if you do! I use it, too. ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
pghmcfc pushed to perl-Module-Extract-Use (rawhide). "Update to 1.049 (..more)"
Notification time stamped 2022-01-09 13:35:06 UTC
From bbc788a5b9447fc7a4178dcf97f8891ad0fb84e0 Mon Sep 17 00:00:00 2001
From: Paul Howarth
Date: Jan 09 2022 13:34:01 +
Subject: Update to 1.049
- New upstream release 1.049
- Fix a link in the README.pod
- Add patch to fix test failures in t/rt/79273.t (GH#7)
- Use %license unconditionally
---
diff --git a/perl-Module-Extract-Use-1.049-test.patch
b/perl-Module-Extract-Use-1.049-test.patch
new file mode 100644
index 000..3851f71
--- /dev/null
+++ b/perl-Module-Extract-Use-1.049-test.patch
@@ -0,0 +1,25 @@
+--- t/rt/79273.t
t/rt/79273.t
+@@ -29,7 +29,7 @@ is_deeply( $details, expected(), 'The da
+ sub expected {
+ return [
+ {
+- 'direct' => 0,
++ 'direct' => 1,
+ 'content' => q(use parent 'CGI::Snapp';),
+ 'pragma' => 'parent',
+ 'version' => undef,
+@@ -44,5 +44,13 @@ sub expected {
+ 'imports' => [qw(capture)],
+ 'module' => 'Capture::Tiny'
+ },
++ {
++ 'direct' => 0,
++ 'content' => q(use parent 'CGI::Snapp';),
++ 'pragma' => '',
++ 'version' => undef,
++ 'imports' => [],
++ 'module' => 'CGI::Snapp'
++ },
+ ];
+ }
diff --git a/perl-Module-Extract-Use.rpmlintrc
b/perl-Module-Extract-Use.rpmlintrc
deleted file mode 100644
index e4537db..000
--- a/perl-Module-Extract-Use.rpmlintrc
+++ /dev/null
@@ -1,3 +0,0 @@
-from Config import *
-addFilter("spelling-error %description -l en_US eval -> ")
-addFilter("spelling-error %description -l en_US pragmas -> ")
diff --git a/perl-Module-Extract-Use.spec b/perl-Module-Extract-Use.spec
index 5e9c605..6eee783 100644
--- a/perl-Module-Extract-Use.spec
+++ b/perl-Module-Extract-Use.spec
@@ -1,10 +1,11 @@
Summary: Pull out the modules a module explicitly uses
Name: perl-Module-Extract-Use
-Version: 1.047
-Release: 6%{?dist}
+Version: 1.049
+Release: 1%{?dist}
License: Artistic 2.0
URL: https://metacpan.org/release/Module-Extract-Use
Source0:
https://cpan.metacpan.org/modules/by-module/Module/Module-Extract-Use-%{version}.tar.gz
+Patch0:perl-Module-Extract-Use-1.049-test.patch
BuildArch: noarch
# Module Build
BuildRequires: coreutils
@@ -19,8 +20,6 @@ BuildRequires:perl(Test::Manifest) >= 1.21
# Module Runtime
BuildRequires: perl(PPI)
BuildRequires: perl(strict)
-BuildRequires: perl(subs)
-BuildRequires: perl(vars)
BuildRequires: perl(warnings)
# Test Suite
BuildRequires: perl(File::Basename)
@@ -43,6 +42,10 @@ returns.
%prep
%setup -q -n Module-Extract-Use-%{version}
+# Fix test failures in t/rt/79273.t
+# https://github.com/briandfoy/module-extract-use/pull/7
+%patch0
+
%build
perl Makefile.PL INSTALLDIRS=vendor
make %{?_smp_mflags}
@@ -56,16 +59,18 @@ find %{buildroot} -type f -name .packlist -delete
make test
%files
-%if 0%{?_licensedir:1}
%license LICENSE
-%else
-%doc LICENSE
-%endif
%doc Changes examples/ README.pod
%{perl_vendorlib}/Module/
%{_mandir}/man3/Module::Extract::Use.3*
%changelog
+* Sun Jan 9 2022 Paul Howarth - 1.049-1
+- Update to 1.049
+ - Fix a link in the README.pod
+- Add patch to fix test failures in t/rt/79273.t (GH#7)
+- Use %%license unconditionally
+
* Thu Jul 22 2021 Fedora Release Engineering -
1.047-6
- Rebuilt for https://fedoraproject.org/wiki/Fedora_35_Mass_Rebuild
diff --git a/sources b/sources
index 8c2cd2a..94e7afa 100644
--- a/sources
+++ b/sources
@@ -1 +1 @@
-SHA512 (Module-Extract-Use-1.047.tar.gz) =
b8f85b55f5492709ec23ffd986e2eda86376990c16f1499d6f5fe6e1e72bf97a5dc59f0dbd1f846338a67786b8bd754f2564ee12553590a4ab843a4f420b85a2
+SHA512 (Module-Extract-Use-1.049.tar.gz) =
ec59d1426dcca5b961a0ed15a5f87cd37738e6e048c16df781b0717be290f71c6bb4e89eb2c289f6d03563330803b0c17f6ec7356dad42ddafc60aed79b2dcb3
https://src.fedoraproject.org/rpms/perl-Module-Extract-Use/c/bbc788a5b9447fc7a4178dcf97f8891ad0fb84e0?branch=rawhide
___
perl-devel mailing list -- perl-devel@lists.fedoraproject.org
To unsubscribe send an email to perl-devel-le...@lists.fedoraproject.org
Fedora Code of Conduct:
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives:
https://lists.fedoraproject.org/archives/list/perl-devel@lists.fedoraproject.org
Do not reply to spam on the list, report it:
https://pagure.io/fedora-infrastructure
[Bug 2038576] Please branch and build perl-Email-Address-XS for EPEL-9
https://bugzilla.redhat.com/show_bug.cgi?id=2038576 Jitka Plesnikova changed: What|Removed |Added Doc Type|--- |If docs needed, set a value Status|NEW |ASSIGNED --- Comment #1 from Jitka Plesnikova --- https://pagure.io/releng/fedora-scm-requests/issue/40671 -- You are receiving this mail because: You are on the CC list for the bug. https://bugzilla.redhat.com/show_bug.cgi?id=2038576 ___ perl-devel mailing list -- perl-devel@lists.fedoraproject.org To unsubscribe send an email to perl-devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/perl-devel@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
[Bug 2038204] Please branch and build perl-Probe-Perl for EPEL-9
https://bugzilla.redhat.com/show_bug.cgi?id=2038204 Jitka Plesnikova changed: What|Removed |Added Doc Type|--- |If docs needed, set a value Status|NEW |ASSIGNED --- Comment #1 from Jitka Plesnikova --- https://pagure.io/releng/fedora-scm-requests/issue/40670 -- You are receiving this mail because: You are on the CC list for the bug. https://bugzilla.redhat.com/show_bug.cgi?id=2038204 ___ perl-devel mailing list -- perl-devel@lists.fedoraproject.org To unsubscribe send an email to perl-devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/perl-devel@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
[Bug 2038692] Please branch and build perl-Lingua-EN-Sentence for EPEL-9
https://bugzilla.redhat.com/show_bug.cgi?id=2038692 --- Comment #2 from Paul Howarth --- (In reply to Ralf Corsepius from comment #1) > xavierb already is "admin" and BZ-contact for epel. > > I've added you, Paul, as "collaborator". Probably not necessary this time as Xavier is doings lots of EPEL work. I'll handle it if Xavier hasn't touched it after a few days though, or if he wants to leave it to me... Thanks again. -- You are receiving this mail because: You are on the CC list for the bug. https://bugzilla.redhat.com/show_bug.cgi?id=2038692 ___ perl-devel mailing list -- perl-devel@lists.fedoraproject.org To unsubscribe send an email to perl-devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/perl-devel@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Re: Does anybody still use `starship'?
I used to until two days ago, when I switched to this COPR repo with a most recent version: https://copr.fedorainfracloud.org/coprs/atim/starship/ On Sun, 9 Jan 2022, at 12:24, Igor Raits wrote: > Hello, > > I saw some recent discussions (yet another time) how packaging Rust / > Go / Node.js is horrible, we should simply bundle everything and such. > Let's not discuss this here, though. > > I'm interested to hear if there are any users of the `starship' > application here in Fedora that consume it from the repositories. > Please speak up if you do! > > As pointed out in the other places, I don't think we are able to > update things like that as fast as releases popping out with just as > few people working on the packaging Rust stack these days (I'm pretty > much not contributing for last couple years due to the other work). > And the question, if we want to keep packaging it (with some slower > update cycle, as the time permits) or we want to retire it completely. > > Personally, I'd love to have more people working on packaging (and > most importantly keeping up-to-date) Rust crates / apps but I think > this is not so realistic :) > -- > — Igor Raits. > ___ > devel mailing list -- devel@lists.fedoraproject.org > To unsubscribe send an email to devel-le...@lists.fedoraproject.org > Fedora Code of Conduct: > https://docs.fedoraproject.org/en-US/project/code-of-conduct/ > List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines > List Archives: > https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org > Do not reply to spam on the list, report it: > https://pagure.io/fedora-infrastructure > ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
ppc64le build failure on F34 and EPEL8, EPEL8-next only
Good day. darktable maintainer here. I am experiencing a ppc64le build failure on F34 and EPEL8, EPEL8-next only. https://koji.fedoraproject.org/koji/taskinfo?taskID=81021540 https://koji.fedoraproject.org/koji/taskinfo?taskID=81021476 On F34 the error is /builddir/build/BUILD/darktable-3.8.0/src/iop/channelmixerrgb.c: In function '_convert_GUI_colors.part.0.constprop': /builddir/build/BUILD/darktable-3.8.0/src/iop/channelmixerrgb.c:3085:1: internal compiler error: in patch_jump_insn, at cfgrtl.c:1299 3085 | } | ^ Please submit a full bug report, with preprocessed source if appropriate. Other branches can successfully build on aarch64, x86_64, pcc64le. Do you know what can be the problem? Thank you___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
[Bug 2038692] Please branch and build perl-Lingua-EN-Sentence for EPEL-9
https://bugzilla.redhat.com/show_bug.cgi?id=2038692 Ralf Corsepius changed: What|Removed |Added Doc Type|--- |If docs needed, set a value --- Comment #1 from Ralf Corsepius --- xavierb already is "admin" and BZ-contact for epel. I've added you, Paul, as "collaborator". -- You are receiving this mail because: You are on the CC list for the bug. https://bugzilla.redhat.com/show_bug.cgi?id=2038692 ___ perl-devel mailing list -- perl-devel@lists.fedoraproject.org To unsubscribe send an email to perl-devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/perl-devel@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Re: Does anybody still use `starship'?
I use it as well straight from the repos :) ! ❯ starship --version starship 0.56.0 branch: commit_hash: build_time:2021-09-30 12:45:52 build_env:rustc 1.55.0 (Fedora 1.55.0-1.fc35), I'm not very familiar with rust packaging (though I do know and use rust itself), but I could try to do some rust packaging and maybe give some help if no one else is available to help. TBH, having an out of date starship is not that much of a problem for me (and I guess for most users), since updates do not usually have much changes, especially if the root of that issue is dependencies. Le 09/01/2022 à 12:24, Igor Raits a écrit : Hello, I saw some recent discussions (yet another time) how packaging Rust / Go / Node.js is horrible, we should simply bundle everything and such. Let's not discuss this here, though. I'm interested to hear if there are any users of the `starship' application here in Fedora that consume it from the repositories. Please speak up if you do! As pointed out in the other places, I don't think we are able to update things like that as fast as releases popping out with just as few people working on the packaging Rust stack these days (I'm pretty much not contributing for last couple years due to the other work). And the question, if we want to keep packaging it (with some slower update cycle, as the time permits) or we want to retire it completely. Personally, I'd love to have more people working on packaging (and most importantly keeping up-to-date) Rust crates / apps but I think this is not so realistic :) ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
[Bug 2038692] New: Please branch and build perl-Lingua-EN-Sentence for EPEL-9
https://bugzilla.redhat.com/show_bug.cgi?id=2038692 Bug ID: 2038692 Summary: Please branch and build perl-Lingua-EN-Sentence for EPEL-9 Product: Fedora EPEL Version: epel9 Status: NEW Component: perl-Lingua-EN-Sentence Assignee: xav...@bachelot.org Reporter: p...@city-fan.org QA Contact: extras...@fedoraproject.org CC: perl-devel@lists.fedoraproject.org, rc040...@freenet.de, xav...@bachelot.org Target Milestone: --- Classification: Fedora Could you please branch and build perl-Lingua-EN-Sentence for EPEL-9 ? If you prefer, you could add me (FAS: pghmcfc) as a committer and I'll do it myself. -- You are receiving this mail because: You are on the CC list for the bug. https://bugzilla.redhat.com/show_bug.cgi?id=2038692 ___ perl-devel mailing list -- perl-devel@lists.fedoraproject.org To unsubscribe send an email to perl-devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/perl-devel@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
[Bug 2036510] Please branch and build perl-Config-General for EPEL-9
https://bugzilla.redhat.com/show_bug.cgi?id=2036510 Paul Howarth changed: What|Removed |Added Doc Type|--- |If docs needed, set a value --- Comment #1 from Paul Howarth --- Will you be able to branch and build perl-Config-General in epel9? I would be happy to be a co-maintainer if you do not wish to build it on epel9. -- You are receiving this mail because: You are on the CC list for the bug. https://bugzilla.redhat.com/show_bug.cgi?id=2036510 ___ perl-devel mailing list -- perl-devel@lists.fedoraproject.org To unsubscribe send an email to perl-devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/perl-devel@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
[Bug 2036496] Please branch and build perl-Test-Trap for EPEL-9
https://bugzilla.redhat.com/show_bug.cgi?id=2036496 --- Comment #2 from Paul Howarth --- Will you be able to branch and build perl-Test-Trap in epel9? I would be happy to be a co-maintainer if you do not wish to build it on epel9. -- You are receiving this mail because: You are on the CC list for the bug. https://bugzilla.redhat.com/show_bug.cgi?id=2036496 ___ perl-devel mailing list -- perl-devel@lists.fedoraproject.org To unsubscribe send an email to perl-devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/perl-devel@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Re: Does anybody still use `starship'?
Yes, here is mine :) starship-0.56.0-4.fc35.x86_64 Name : starship Version : 0.56.0 Release : 4.fc35 Architecture : x86_64 Size : 5.4 M Source : rust-starship-0.56.0-4.fc35.src.rpm Repository : @System From repo : updates Summary : Minimal, blazing-fast, and infinitely customizable prompt for any : shell URL : https://crates.io/crates/starship License : ISC and ASL 2.0 and MIT and MPLv2.0 Description : Minimal, blazing-fast, and infinitely customizable prompt for any : shell! ☄️. Regards., El 9/1/22 a las 12:34, Abhiram Kuchibhotla escribió: Yup! I get my starship straight from the repos. On Sun, 9 Jan, 2022, 4:55 pm Igor Raits, wrote: Hello, I saw some recent discussions (yet another time) how packaging Rust / Go / Node.js is horrible, we should simply bundle everything and such. Let's not discuss this here, though. I'm interested to hear if there are any users of the `starship' application here in Fedora that consume it from the repositories. Please speak up if you do! As pointed out in the other places, I don't think we are able to update things like that as fast as releases popping out with just as few people working on the packaging Rust stack these days (I'm pretty much not contributing for last couple years due to the other work). And the question, if we want to keep packaging it (with some slower update cycle, as the time permits) or we want to retire it completely. Personally, I'd love to have more people working on packaging (and most importantly keeping up-to-date) Rust crates / apps but I think this is not so realistic :) -- — Igor Raits. ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure ___ devel mailing list --devel@lists.fedoraproject.org To unsubscribe send an email todevel-le...@lists.fedoraproject.org Fedora Code of Conduct:https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines:https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives:https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org Do not reply to spam on the list, report it:https://pagure.io/fedora-infrastructure___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
[Bug 2038673] New: perl-App-Cme-1.035 is available
https://bugzilla.redhat.com/show_bug.cgi?id=2038673 Bug ID: 2038673 Summary: perl-App-Cme-1.035 is available Product: Fedora Version: rawhide Status: NEW Component: perl-App-Cme Keywords: FutureFeature, Triaged Assignee: jples...@redhat.com Reporter: upstream-release-monitor...@fedoraproject.org QA Contact: extras...@fedoraproject.org CC: jples...@redhat.com, perl-devel@lists.fedoraproject.org Target Milestone: --- Classification: Fedora Latest upstream release: 1.035 Current version/release in rawhide: 1.034-1.fc36 URL: http://search.cpan.org/dist/App-Cme/ Please consult the package updates policy before you issue an update to a stable branch: https://docs.fedoraproject.org/en-US/fesco/Updates_Policy/ More information about the service that created this bug can be found at: https://fedoraproject.org/wiki/Upstream_release_monitoring Please keep in mind that with any upstream change, there may also be packaging changes that need to be made. Specifically, please remember that it is your responsibility to review the new version to ensure that the licensing is still correct and that no non-free or legally problematic items have been added upstream. Based on the information from Anitya: https://release-monitoring.org/project/9059/ -- You are receiving this mail because: You are on the CC list for the bug. https://bugzilla.redhat.com/show_bug.cgi?id=2038673 ___ perl-devel mailing list -- perl-devel@lists.fedoraproject.org To unsubscribe send an email to perl-devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/perl-devel@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Re: Does anybody still use `starship'?
Yup! I get my starship straight from the repos. On Sun, 9 Jan, 2022, 4:55 pm Igor Raits, wrote: > Hello, > > I saw some recent discussions (yet another time) how packaging Rust / > Go / Node.js is horrible, we should simply bundle everything and such. > Let's not discuss this here, though. > > I'm interested to hear if there are any users of the `starship' > application here in Fedora that consume it from the repositories. > Please speak up if you do! > > As pointed out in the other places, I don't think we are able to > update things like that as fast as releases popping out with just as > few people working on the packaging Rust stack these days (I'm pretty > much not contributing for last couple years due to the other work). > And the question, if we want to keep packaging it (with some slower > update cycle, as the time permits) or we want to retire it completely. > > Personally, I'd love to have more people working on packaging (and > most importantly keeping up-to-date) Rust crates / apps but I think > this is not so realistic :) > -- > — Igor Raits. > ___ > devel mailing list -- devel@lists.fedoraproject.org > To unsubscribe send an email to devel-le...@lists.fedoraproject.org > Fedora Code of Conduct: > https://docs.fedoraproject.org/en-US/project/code-of-conduct/ > List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines > List Archives: > https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org > Do not reply to spam on the list, report it: > https://pagure.io/fedora-infrastructure > ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Does anybody still use `starship'?
Hello, I saw some recent discussions (yet another time) how packaging Rust / Go / Node.js is horrible, we should simply bundle everything and such. Let's not discuss this here, though. I'm interested to hear if there are any users of the `starship' application here in Fedora that consume it from the repositories. Please speak up if you do! As pointed out in the other places, I don't think we are able to update things like that as fast as releases popping out with just as few people working on the packaging Rust stack these days (I'm pretty much not contributing for last couple years due to the other work). And the question, if we want to keep packaging it (with some slower update cycle, as the time permits) or we want to retire it completely. Personally, I'd love to have more people working on packaging (and most importantly keeping up-to-date) Rust crates / apps but I think this is not so realistic :) -- — Igor Raits. ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Re: Need help with some rpmlint errors
Il 08/01/22 23:41, Jerry James ha scritto: > On Sat, Jan 8, 2022 at 6:37 AM Mattia Verga via devel > wrote: >> `E: shared-library-without-dependency-information >> /usr/lib64/libapogee.so.3.2` >> I'm not sure if this is a rpmlint false positive. All I can found >> searching is an issue in rpmlint which says that the library could be >> statically linked [3], but running ldd on the file shows it is shared. >> (as far I understand, I'm not a software developer) > I see this happen with libraries that do not depend on any symbols in > libc. Check pretty much any ocaml-* package, for example, and rpmlint > will report this. If your library functions as expected, then ignore > this message. > >> `E: missing-PT_GNU_STACK-section /usr/lib64/libapogee.so.3.2` >> I can't find anything searching for this online. Maybe another false >> positive? > This means that the toolchain thinks your library needs an executable > stack. That usually happens because the project includes assembly > language files, and those files do not contain the magic to tell the > toolchain that the stack does not need to be executable. Try adding > -Wa,--noexecstack to the build flags or -Wl,-z,noexecstack to the > linker flags. Thanks, indeed the project itself sets those flags in a cmake module for both the build and linker flags. I originally avoided to have the project set custom flags because it also sets -fPIE and that caused build failures. But after having removed only the -fPIE from the custom flags, I get the same errors from rpmlint. Mattia ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Re: Heads up: libffi 3.4 rebuild in rawhide today
On 08. 01. 22 10:37, Miro Hrončok wrote: Hello packagers, I intent to rebuild the following packages with libffi 3.4 in Rawhide side tag f36-build-side-49314 today. The previous version remains available as libffi13.1, so failures to build will not result in uninstallable packages. You can inspect some known failures: ... And some previously unexpected failures: python2.7 and python3.6 === test_tkinter fails on i686 this is *not* related to new libffi unfortunately koschei does not build on 32bit arches, so we have no idea how long has this been happening :( will investigate and open bugzillas on Monday python3.7 = test_zlib fails on s390x not verified yet if related to libffi, but I don't think so koschei does not build on s390x either :( will investigate and open bugzilla on Monday llvm, llvm10, llvm11, and llvm12 failures on s390x or armv7hl llvm maintainers CC'ed gambas3 === broken build dependencies due to the recent libre2 unannounced soname bump I suppose I could tag in older libre2 just for the rebuild :/ -- Miro Hrončok -- Phone: +420777974800 IRC: mhroncok ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Fedora-Cloud-34-20220109.0 compose check report
No missing expected images. Soft failed openQA tests: 1/8 (x86_64), 1/8 (aarch64) (Tests completed, but using a workaround for a known bug) Old soft failures (same test soft failed in Fedora-Cloud-34-20220108.0): ID: 1099021 Test: x86_64 Cloud_Base-qcow2-qcow2 cloud_autocloud URL: https://openqa.fedoraproject.org/tests/1099021 ID: 1099032 Test: aarch64 Cloud_Base-qcow2-qcow2 cloud_autocloud@uefi URL: https://openqa.fedoraproject.org/tests/1099032 Passed openQA tests: 7/8 (x86_64), 7/8 (aarch64) -- Mail generated by check-compose: https://pagure.io/fedora-qa/check-compose ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Fedora-Cloud-35-20220109.0 compose check report
No missing expected images. Soft failed openQA tests: 1/8 (x86_64), 1/8 (aarch64) (Tests completed, but using a workaround for a known bug) Old soft failures (same test soft failed in Fedora-Cloud-35-20220108.0): ID: 1099005 Test: x86_64 Cloud_Base-qcow2-qcow2 cloud_autocloud URL: https://openqa.fedoraproject.org/tests/1099005 ID: 1099016 Test: aarch64 Cloud_Base-qcow2-qcow2 cloud_autocloud@uefi URL: https://openqa.fedoraproject.org/tests/1099016 Passed openQA tests: 7/8 (x86_64), 7/8 (aarch64) -- Mail generated by check-compose: https://pagure.io/fedora-qa/check-compose ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
