[EPEL-devel] Fedora EPEL 8 updates-testing report
The following Fedora EPEL 8 Security updates need testing: Age URL 7 https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2019-fabd190d13 clamav-0.101.4-1.el8 The following builds have been pushed to Fedora EPEL 8 updates-testing freeradius-client-1.1.7-20.el8 kim-api-2.1.3-1.el8 nagios-plugins-2.2.1-17.20190829gitfb792ff.el8.initial pdns-4.2.0-1.el8 python-catkin-sphinx-0.2.2-14.el8 python-catkin_pkg-0.4.13-2.el8 python-colorlog-4.0.1-5.el8 python-timeout-decorator-0.4.1-1.el8 python-vcstool-0.2.3-1.el8 tng-1.8.2-4.el8 Details about builds: freeradius-client-1.1.7-20.el8 (FEDORA-EPEL-2019-d051eada8e) RADIUS protocol client library Update Information: Added to EPEL-8 kim-api-2.1.3-1.el8 (FEDORA-EPEL-2019-58ce8eb177) Open Knowledgebase of Interatomic Models KIM API Update Information: Initial add nagios-plugins-2.2.1-17.20190829gitfb792ff.el8.initial (FEDORA-EPEL-2019-9a1181e13e) Host/service/network monitoring program plugins for Nagios Update Information: This is an initial port of nagios-plugins to EPEL-8 to get it in. Not assured to work. References: [ 1 ] Bug #1741319 - Package request: Nagios-plugins epel8 https://bugzilla.redhat.com/show_bug.cgi?id=1741319 pdns-4.2.0-1.el8 (FEDORA-EPEL-2019-db22d7c1de) A modern, advanced and high performance authoritative-only nameserver Update Information: - Update to 4.2.0 - Enable LUA records - Enable lua2 backend - Enable luajit - Enable experimental pkcs11 support - Added ixfrdist subpackage Release notes: https://doc.powerdns.com/authoritative/changelog/4.2.html#change-4.2.0 Blog post: https://blog.powerdns.com/2019/08/30/powerdns-authoritative-server-4-2-0/ ChangeLog: * Fri Aug 30 2019 Morten Stevens - 4.2.0-1 - Update to 4.2.0 - Enable LUA records - Enable lua2 backend - Enable luajit - Enable experimental pkcs11 support - Added ixfrdist subpackage python-catkin-sphinx-0.2.2-14.el8 (FEDORA-EPEL-2019-add3fdf630) Sphinx extension for Catkin projects Update Information: Introduction of python-catkin-sphinx into EPEL 8 python-catkin_pkg-0.4.13-2.el8 (FEDORA-EPEL-2019-3ec6ddfce9) Library for retrieving information about catkin packages Update Information: Introduction of catkin_pkg into EPEL 8 python-colorlog-4.0.1-5.el8 (FEDORA-EPEL-2019-dffaa040da) A colored formatter for the Python logging module Update Information: Rebuilt for Python 3.8 python-timeout-decorator-0.4.1-1.el8 (FEDORA-EPEL-2019-7fbed5eaec) Timeout decorator for Python Update Information: Initial packaging References: [ 1 ] Bug #1746017 - Review Request: python-timeout-decorator - a timeout decorator for Python https://bugzilla.redhat.com/show_bug.cgi?id=1746017
[389-devel] 389 DS nightly 2019-08-31 - 95% PASS
https://fedorapeople.org/groups/389ds/ci/nightly/2019/08/31/report-389-ds-base-1.4.1.6-20190830git0c94f21.fc30.x86_64.html ___ 389-devel mailing list -- 389-devel@lists.fedoraproject.org To unsubscribe send an email to 389-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/389-devel@lists.fedoraproject.org
[EPEL-devel] Fedora EPEL 6 updates-testing report
The following Fedora EPEL 6 Security updates need testing: Age URL 3 https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2019-af80b147c4 python-mitogen-0.2.8-1.el6 0 https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2019-54cf4d603d seamonkey-2.49.5-1.el6 The following builds have been pushed to Fedora EPEL 6 updates-testing nsd-4.2.2-1.el6 sslsplit-0.5.5-1.el6 Details about builds: nsd-4.2.2-1.el6 (FEDORA-EPEL-2019-0ba49c0abc) Fast and lean authoritative DNS Name Server Update Information: Resolves: rhbz#1609774 nsd-4.2.2 is available ChangeLog: * Fri Aug 30 2019 Paul Wouters - 4.2.2-1 - Resolves: rhbz#1609774 nsd-4.2.2 is available - Resolves: rhbz#1727689 CVE-2019-13207 nsd: stack-based overflow - Updated nsd.conf for new features - Added --enable-recvmmsg --enable-packed --enable-memclean --enable-zone-stats --enable-ratelimit --enable-pie --enable-relro-now References: [ 1 ] Bug #1609774 - nsd-4.2.2 is available https://bugzilla.redhat.com/show_bug.cgi?id=1609774 [ 2 ] Bug #1727689 - CVE-2019-13207 nsd: stack-based overflow in function dname_concatenate() in dname.c [fedora-all] https://bugzilla.redhat.com/show_bug.cgi?id=1727689 sslsplit-0.5.5-1.el6 (FEDORA-EPEL-2019-1a5005e893) Transparent and scalable SSL/TLS interception Update Information: Resolves: rhbz#1534305 sslsplit-0.5.5 is available References: [ 1 ] Bug #1534305 - sslsplit-0.5.5 is available https://bugzilla.redhat.com/show_bug.cgi?id=1534305 ___ epel-devel mailing list -- epel-devel@lists.fedoraproject.org To unsubscribe send an email to epel-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/epel-devel@lists.fedoraproject.org
[EPEL-devel] Fedora EPEL 7 updates-testing report
The following Fedora EPEL 7 Security updates need testing: Age URL 381 https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2018-3c9292b62d condor-8.6.11-1.el7 156 https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2019-d2c1368294 cinnamon-3.6.7-5.el7 122 https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2019-c499781e80 python-gnupg-0.4.4-1.el7 120 https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2019-bc0182548b bubblewrap-0.3.3-2.el7 57 https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2019-12067fc897 dosbox-0.74.3-2.el7 10 https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2019-1a711333e8 nghttp2-1.31.1-2.el7 10 https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2019-e1ddf9b607 sleuthkit-4.6.7-1.el7 3 https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2019-dea2d705d0 python-mitogen-0.2.8-1.el7 1 https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2019-b4713b164c chromium-76.0.3809.132-1.el7 1 https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2019-ca3444781e perl-SOAP-Lite-1.10-2.el7 1 https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2019-954cf3770a seamonkey-2.49.5-1.el7 The following builds have been pushed to Fedora EPEL 7 updates-testing nsd-4.2.2-1.el7 opari2-2.0.5-1.el7 python-vcstool-0.2.3-1.el7 sslsplit-0.5.5-1.el7 Details about builds: nsd-4.2.2-1.el7 (FEDORA-EPEL-2019-9bc2214140) Fast and lean authoritative DNS Name Server Update Information: Resolves: rhbz#1609774 nsd-4.2.2 is available ChangeLog: * Fri Aug 30 2019 Paul Wouters - 4.2.2-1 - Resolves: rhbz#1609774 nsd-4.2.2 is available - Resolves: rhbz#1727689 CVE-2019-13207 nsd: stack-based overflow - Update rundir to /run/ - Updated nsd.conf for new features - Added --enable-recvmmsg --enable-packed --enable-memclean --enable-zone-stats * Thu Jul 25 2019 Fedora Release Engineering - 4.1.24-4 - Rebuilt for https://fedoraproject.org/wiki/Fedora_31_Mass_Rebuild * Fri Feb 1 2019 Fedora Release Engineering - 4.1.24-3 - Rebuilt for https://fedoraproject.org/wiki/Fedora_30_Mass_Rebuild References: [ 1 ] Bug #1609774 - nsd-4.2.2 is available https://bugzilla.redhat.com/show_bug.cgi?id=1609774 [ 2 ] Bug #1727689 - CVE-2019-13207 nsd: stack-based overflow in function dname_concatenate() in dname.c [fedora-all] https://bugzilla.redhat.com/show_bug.cgi?id=1727689 opari2-2.0.5-1.el7 (FEDORA-EPEL-2019-effbf1bfbc) An OpenMP runtime performance measurement instrumenter Update Information: New version for current scorep ChangeLog: * Wed Aug 14 2019 Dave love - 2.0.5-1 - New version * Thu Jul 25 2019 Fedora Release Engineering - 2.0.4-2 - Rebuilt for https://fedoraproject.org/wiki/Fedora_31_Mass_Rebuild * Tue Feb 26 2019 Orion Poplawski - 2.0.4-1 - Update to 2.0.4 * Fri Feb 1 2019 Fedora Release Engineering - 2.0.3-4 - Rebuilt for https://fedoraproject.org/wiki/Fedora_30_Mass_Rebuild * Sun Jul 22 2018 Orion Poplawski - 2.0.3-3 - Add patch to fix bad string access (FTBFS bug #1605309) * Fri Jul 13 2018 Fedora Release Engineering - 2.0.3-2 - Rebuilt for https://fedoraproject.org/wiki/Fedora_29_Mass_Rebuild * Mon May 21 2018 Orion Poplawski - 2.0.3-1 - Update to 2.0.3 * Thu Feb 8 2018 Fedora Release Engineering - 2.0.2-4 - Rebuilt for https://fedoraproject.org/wiki/Fedora_28_Mass_Rebuild * Thu Aug 3 2017 Fedora Release Engineering - 2.0.2-3 - Rebuilt for https://fedoraproject.org/wiki/Fedora_27_Binutils_Mass_Rebuild * Thu Jul 27 2017 Fedora Release Engineering - 2.0.2-2 - Rebuilt for https://fedoraproject.org/wiki/Fedora_27_Mass_Rebuild * Mon Jun 12 2017 Orion Poplawski - 2.0.2-1 - Update to 2.0.2 * Sat Feb 11 2017 Fedora Release Engineering - 2.0.1-4 - Rebuilt for https://fedoraproject.org/wiki/Fedora_26_Mass_Rebuild * Mon Nov 7 2016 Orion Poplawski - 2.0.1-3 - Add upstream patch to fix ppc64 builds * Fri Nov 4 2016 Orion Poplawski - 2.0.1-2 - Add BR gcc-c++ - Output test logs if they fail * Tue Sep 20 2016 Orion Poplawski - 2.0.1-1 - Update to 2.0.1 * Fri Apr 15 2016 Orion Poplawski - 2.0-1 - Update to 2.0 * Thu Feb 4 2016 Fedora Release Engineering - 1.1.4-2 - Rebuilt for https://fedoraproject.org/wiki/Fedora_24_Mass_Rebuild * Fri Jun 19 2015 Orion Poplawski - 1.1.4-7 - Update to 1.1.4 * Wed Jun 17 2015 Fedora Release Engineering - 1.1.3-2 - Rebuilt
Re: RPM building on s390x sometimes is very slow on F-30+
On Wed, 2019-08-28 at 23:13 +0200, Peter Lemenkov wrote:
> Hello All,
>
> I've just got hit by this again - lockups on s390. Looks like I have
> 100% reproducer (just try to build Erlang and it will stuck
> eventually).
>
> * https://koji.fedoraproject.org/koji/taskinfo?taskID=37327589
>
> Where should I open a ticket? Bugzilla.redhat.com or somewhere else?
Maybe you should cancel this build and start a new one , this build [1]
seems stuck and stopped , some times may happen .
[1]
https://koji.fedoraproject.org/koji/watchlogs?taskID=37327589
>
> чт, 25 июл. 2019 г. в 17:44, Kevin Fenzi :
> > On 7/25/19 3:04 AM, Peter Lemenkov wrote:
> > > Hello All!
> > > It started to get stuck again. Right now I'm experiencing this
> > > issue
> > > with RabbitMQ for F-30 and F-31:
> > >
> > > * https://koji.fedoraproject.org/koji/taskinfo?taskID=36457376
> > > * https://koji.fedoraproject.org/koji/taskinfo?taskID=36457345
> >
> > So, yeah.
> >
> > > | |-kojid,31279 /usr/sbin/kojid --fg --force-lock --verbose
> > > | | `-mock,31584 -tt /usr/libexec/mock/mock -r koji/f30-
> > > build-16961487-1222718 --old-chroot --no-clean --target s390x ...
> > > | | `-rpmbuild,32205 -bb --target s390x --nodeps
> > > /builddir/build/SPECS/rabbitmq-server.spec
> > > | | `-sh,32237 -e /var/tmp/rpm-tmp.GwzEQt
> > > | | `-make,32238 -j4 VERSION=3.7.16 V=1
> > > | | `-sh,32318 -c...
> > > | | `-make,2112 -C
> > > /builddir/build/BUILD/rabbitmq-server-3.7.16/deps/amqp10_client
> > > IS_DEP=1
> > > | | `-make,2237 --no-print-
> > > directory app-build
> > > | | `-beam.smp,2302 -sbtu -A0
> > > -- -root /usr/lib64/erlang -progname erl -- -home /builddir --
> > > ...
> > > | | |-{beam.smp},2303
> > > | | |-{beam.smp},2304
> > > | | |-erl_child_setup,2305
> > > 1024
> > > | | |-{beam.smp},2306
> > > | | |-{beam.smp},2307
> > > | | |-{beam.smp},2308
> > > | | |-{beam.smp},2309
> > > | | |-{beam.smp},2310
> > > | | |-{beam.smp},2311
> > > | | |-{beam.smp},2312
> > > | | |-{beam.smp},2313
> > > | | |-{beam.smp},2314
> > > | | |-{beam.smp},2315
> > > | | |-{beam.smp},2316
> > > | | |-{beam.smp},2317
> > > | | |-{beam.smp},2318
> > > | | |-{beam.smp},2319
> > > | | |-{beam.smp},2320
> > > | | |-{beam.smp},2321
> > > | | |-{beam.smp},2322
> > > | | |-{beam.smp},2323
> > > | | |-{beam.smp},2324
> > > | | `-{beam.smp},2325
> >
> > When I strace the 2302 process:
> >
> > strace: Process 2302 attached with 23 threads
> > [pid 2324] ppoll([{fd=12, events=POLLIN|POLLRDNORM}], 1, NULL,
> > NULL, 8
> >
> > [pid 2320] futex(0x3ff58800550, FUTEX_WAIT_PRIVATE, 4294967295,
> > NULL
> >
> > [pid 2321] futex(0x3ff58800590, FUTEX_WAIT_PRIVATE, 4294967295,
> > NULL
> >
> > [pid 2319] futex(0x3ff58800510, FUTEX_WAIT_PRIVATE, 4294967295,
> > NULL
> >
> > [pid 2318] futex(0x3ff588004d0, FUTEX_WAIT_PRIVATE, 4294967295,
> > NULL
> >
> > [pid 2317] futex(0x3ff58800490, FUTEX_WAIT_PRIVATE, 4294967295,
> > NULL
> >
> > [pid 2316] futex(0x3ff58800450, FUTEX_WAIT_PRIVATE, 4294967295,
> > NULL
> >
> > [pid 2315] futex(0x3ff58800410, FUTEX_WAIT_PRIVATE, 4294967295,
> > NULL
> >
> > [pid 2313] futex(0x3ff58800390, FUTEX_WAIT_PRIVATE, 4294967295,
> > NULL
> >
> > [pid 2312] futex(0x3ff58800350, FUTEX_WAIT_PRIVATE, 4294967295,
> > NULL
> >
> > [pid 2308] restart_syscall(<... resuming interrupted
> > syscall_0xfdfc ...> > ed ...>
> > [pid 2303] read(14,
> > [pid 2302] select(0, NULL, NULL, NULL, NULL
> > [pid 2309] restart_syscall(<... resuming interrupted select ...>
> >
> > [pid 2323] futex(0x3ff58800610, FUTEX_WAIT_PRIVATE, 4294967295,
> > NULL
> >
> > [pid 2322] futex(0x3ff588005d0, FUTEX_WAIT_PRIVATE, 4294967295,
> > NULL
> >
> > [pid 2314] futex(0x3ff588003d0, FUTEX_WAIT_PRIVATE, 4294967295,
> > NULL
> >
> > [pid 2311] futex(0x3ff58800310, FUTEX_WAIT_PRIVATE, 4294967295,
> > NULL
> >
> > [pid 2310] futex(0x3ff588002d0, FUTEX_WAIT_PRIVATE, 4294967295,
> > NULL
> >
> > [pid 2306]
[Test-Announce] Proposal to CANCEL: 2019-09-02 Fedora QA Meeting
Hi folks! I'm proposing we cancel the QA meeting for Monday, as it's a public holiday in the US, Canada and India, so many folks would be missing. It would be good to follow up on the btrfs and Xen discussions, but we can do it the following week I think. Note that there will be a blocker review meeting, but it will be on *Tuesday*. Thanks! -- Adam Williamson Fedora QA Community Monkey IRC: adamw | Twitter: AdamW_Fedora | XMPP: adamw AT happyassassin . net http://www.happyassassin.net ___ test-announce mailing list -- test-annou...@lists.fedoraproject.org To unsubscribe send an email to test-announce-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/test-annou...@lists.fedoraproject.org ___ 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
[Test-Announce] **2019-09-03** (TUESDAY) @ 16:00 UTC - Fedora 31 Blocker Review Meeting
# F31 Blocker Review meeting # Date: 2019-09-03 # Time: 16:00 UTC # Location: #fedora-blocker-review on irc.freenode.net Hi folks! We have 4 proposed Beta blockers, 1 proposed Final blocker and 10 proposed Beta freeze exception to review, so let's have a Fedora 31 blocker review meeting ON **TUESDAY**! Note, TUESDAY. This is because Monday is a public holiday in the US, Canada and India, so lots of folks would be missing for a meeting on Monday, but as we're frozen for Beta now we shouldn't really skip a week. If you have time this weekend, you can take a look at the proposed or accepted blockers before the meeting - the full lists can be found here: https://qa.fedoraproject.org/blockerbugs/ . We'll be evaluating these bugs to see if they violate any of the Release Criteria and warrant the blocking of a release if they're not fixed. Information on the release criteria for F31 can be found on the wiki [0]. For more information about the Blocker and Freeze exception process, check out these links: - https://fedoraproject.org/wiki/QA:SOP_blocker_bug_process - https://fedoraproject.org/wiki/QA:SOP_freeze_exception_bug_process And for those of you who are curious how a Blocker Review Meeting works - or how it's supposed to go and you want to run one - check out the SOP on the wiki: - https://fedoraproject.org/wiki/QA:SOP_Blocker_Bug_Meeting Have a good weekend and see you on Tuesday! [0] https://fedoraproject.org/wiki/Fedora_Release_Criteria -- Adam Williamson Fedora QA Community Monkey IRC: adamw | Twitter: AdamW_Fedora | XMPP: adamw AT happyassassin . net http://www.happyassassin.net ___ test-announce mailing list -- test-annou...@lists.fedoraproject.org To unsubscribe send an email to test-announce-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/test-annou...@lists.fedoraproject.org ___ 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
Re: [Test-Announce] Fedora 31 Beta Freeze
On Fri, Aug 30, 2019 at 6:26 AM Martin Kolman wrote: > > I would personally still find even 24:00 confusing & would really suggest > something > clearly inambigous, such as 23:45 UTC or similar - that should clear any > doubt of which day > the freeze is part of once and for all & yet again no actualy changes in the > machinery are needed. 2400 is totally confusing, I'm only finding it used in military contexts and even there it seems to be vernacular. I'd rather be surprised if military police use it. But anyway, I did laugh a bit out loud at 23:45 UTC because *of course* there are many other totally unambiguous times to choose from instead. Some of the best comedy is pointing out the obvious. My suggestion would be, without respect to preference, 0015 UTC, 0030 UTC, or 0100 UTC. And that's only because it acts like a kind of grace period for anyone used to UTC, not paying attention to this thread, and maybe misses the next announcement. -- Chris Murphy ___ 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
Mondays's FESCo Meeting (2019-09-02) is cancelled
Due to the US holiday, several of us won't be there. The next meeting will be on Monday (2019-09-09). Thanks, Justin ___ 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
Re: University people in Fedora: Education/University SIG
On Wed, Aug 28, 2019 at 10:43 AM Timothée Floure wrote: > > Hello everyone, > > This is a follow-up email for some "coffee discussions" we had at flock a few > weeks ago. Sorry for the delay! > > The Fedora community contains a lot of university students, many of us > packaging tools for their courses and acting as first-level Linux support for > the local student community. The problems we encounter and work on are not > identical but share a common base: it only makes sense to collaborate. > > We found (over a few flock coffee breaks) 5-6 fedorans interested in joining > such an initiative and are currently creating a SIG as a mean to communicate. > We haven't decided on anything yet, except that we would like to work together > to make Fedora an accessible platform for student and courses in an university > context. We expect overlapping interests and collaboration with others SIGs, > especially if related to the academic world such as NeuroFedora or ML. > > We are aware of the dormant Education SIG [1] but have yet to discuss how to > position - or integrate - ourselve. > > A slightly more detailed description can be found on the related wiki page > [2]. > I invite you to add your name to its members section you're interested to work > with us. We will figure out communication and coordination mediums around next > week. Hi, I'm a new member of the Fedora Workstation working group, and would like to reach out to the University SIG with an invitation to keep us informed of your priorities and conclusions (wish lists, biggest complaints, whatever you see fit), so that we can also ensure Workstation edition is continuing to meet the changing needs of the student community. You are an explicitly listed target market! https://fedoraproject.org/wiki/Workstation -- Chris Murphy ___ 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
Re: f32/rawhide, nothing provides module(platform:f31)
On 30. 08. 19 18:25, Adam Williamson wrote: Not. If you're getting it on an installed system that you're upgrading, you probably need to manually switch the libgit2 module from the 0.27 stream to the 0.28 stream, that should clear it up. I'm hit by this when trying to upgrade to F31: Problém 2: problem with installed package exa-0.8.0-13.module_f30+4041+ebfd9240.x86_64 - package exa-0.9.0-2.module_f31+5365+04413d87.x86_64 requires libgit2.so.28()(64bit), but none of the providers can be installed - exa-0.8.0-13.module_f30+4041+ebfd9240.x86_64 does not belong to a distupgrade repository - package libgit2-0.28.2-2.module_f31+5411+fa1856a4.x86_64 is excluded - package exa-0.9.0-3.fc31.x86_64 is excluded - package libgit2-0.28.2-3.fc31.x86_64 is excluded I have never installed any module explicitly. As an user, I'm confused by this. If this indeed requires my intervention, maybe we should document it as a common bug? I had an impression that this was fixed via: https://pagure.io/fesco/issue/2146 I've opened https://bugzilla.redhat.com/show_bug.cgi?id=1747408 Is this a candidate for a blocker? -- 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
Re: libexempi SONAME bump in rawhide
Hey, On Fri, Aug 30, 2019 at 03:21:43PM +0200, Nikola Forr? wrote: > I'm planning to update exempi to version 2.5.1 in rawhide, and it > includes a SONAME change from "libexempi.so.3" to "libexempi.so.8". > > Affected packages are: > > caja > eog > eom > equalx > nemo > tellico > tracker-miners > > I've rebuilt all of them in Copr [1] without issues, except tellico, > which failed due to an unrelated bug [2]. Thanks for the heads-up! Were you looking for a go ahead to rebuild the affected packages in Fedora proper? In that case, you have my whole hearted appreciation for taking care of the eog and tracker-miners rebuilds. :) Cheers, Rishi ___ 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
Re: Best practice for local files in a package
On Fri, Aug 30, 2019 at 11:17:11 -0700, Kevin Fenzi wrote: Well, in the squashfs-tools case these are in the looaside cache, so you could (all be it ugly looking), use: https://src.fedoraproject.org/lookaside/pkgs/squashfs-tools/unsquashfs.1/sha512/6e1be535d370fb39b2a0e47c98052727bab94ae4f306bb3eb8f7dd07fb84bf985e82ba66bb2030e08261473cffc34d1c1973b27e77cb7127d588e24297f2f0a3/unsquashfs.1 You would have to change that if the file got uploaded again with changes of course. I'll give it a try. The files do need to change, so I won't be using that exact string. But if it isn't crazy to provide a lookaside cache reference then I'll give it a try when I do the update. I'll also see if I can find a place in the packaging documentation to note this solution for others. ___ 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
swap on ZRAM, zswap, and Rust was: Better interactivity in low-memory situations
Hi, This is yet another follow-up for this thread: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org/message/XUZLHJ5O32OX24LG44R7UZ2TMN6NY47N/ Basics: "zswap" compresses swap and uses a defined memory pool as a cache, with spill over (still compressed) going into a conventional swap partition. The memory pool doesn't appear as a separate block device. A conventional swap partition on a drive is required. https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/tree/Documentation/blockdev/zram.txt?h=v5.2.9 "swap on ZRAM" A ZRAM device appears as a block device, and is effectively a compressed RAM disk. It's common for this to be the exclusive swap device, of course it is volatile so in that configuration your system can't hibernate. But it's also possible to use swap priority in fstab to cause the ZRAM device to be used with higher priority, and a conventional swap partition on a drive with a lower priority. https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/tree/Documentation/vm/zswap.rst?h=v5.2.9 What they do: Either strategy can help avoid swap thrashing, by moderating the transition from exclusively RAM based work, to heavy swapping on disk. In my testing, the most aggressive memory starved workloads still result in an unresponsive system. Neither are a complete solution, they really seem to just be moderators that kick the can down the road. But I do think it's an improvement especially in the incidental swap use case, where transition from memory to swap isn't noticeable. Which is better? I don't know. Seriously, that's what all of my testing as come down to. A user won't likely notice the difference. Both dynamically allocate memory to their "memory pools" on demand. But otherwise, they really are two very different implementations. Regardless, Fedora Workstation and probably even Fedora Server, should use one of them by default out of the box. IoT folks are already using swap on ZRAM by default, in lieu of a disk based swap partition. And Anaconda folks are doing the same for low memory devices when the installer is launched. I've been using zswap on Fedora Workstation edition on my laptop, and Fedora Server on an Intel NUC, for maybe two years (earlier this summer I switched both of them swap on ZRAM to compare). How are they different? There are several "swap on ZRAM" implementations. The zram package in Fedora right now is what IoT folks are using which installs a systemd service unit to setup the ZRAM block device, mkswap on it, and then swapon, during system startup. Simple. The ideal scenario is to get everyone on the same page, and so far it looks like systemd's zram-generator, built in Rust, meets all the requirements. That needs to be confirmed, but also right now there's a small problem, it's not working. So we kinda need a someone familiar with Rust and systemd to take this on, if we want to use the same thing everywhere. https://github.com/systemd/zram-generator/issues/4 Whereas zswap is setup by using boot parameters, which we could have the installer set, contingent on a conventional swap partition being created. zswap.enabled=1 zswap.compressor=lz4 zswap.max_pool_percent=20 zswap.zpool=zbud Zswap upstream tells me they're close to dropping the experimental status, hopefully by the end of the summer. It might be a bit longer before they're as confident with zpool type z3fold. Hackfest anyone? -- Chris Murphy ___ 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
testing oomd, cgroupsv2, was: Better interactivity in low-memory situations
Hi, This is a follow-up for this thread: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org/message/XUZLHJ5O32OX24LG44R7UZ2TMN6NY47N/ Has anyone looked at oomd, or is anyone interested in testing and comparing it to alternatives? https://facebookmicrosites.github.io/oomd/docs/overview https://news.ycombinator.com/item?id=17590858 The origin for oomd is servers, and the case study at Facebook is also server centric. But oomd is also very flexible, with the option to arrive over the medium term a cooperative approach to resource management. However, my more immediate interest is to make heavy memory pressure and swap usage (versus incidental use of swap) result in a more predictable outcome. Right now this is all over the map, maybe the process you would have picked to kill (if you could) is killed. Maybe something else is killed and you don't notice, but it frees up just enough memory to prevent anything else from being killed, and now you're stuck in swap hell. It's a lot of maybes. And the final implosion of a system isn't really what matters because at this point, once it happens, the system is already in some kind of tail spin. And what that means is we can't even really iterate on any improvements because all the outcomes right now appear to suck. So how about avoiding tail spins in the first place? And a quick search, Lennart mentions oomd in the 'raise fileno limit...' thread from Oct 2018 during early discussions of cgroupsv2. -- Chris Murphy ___ 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
Re: Fedora Workstation and disabled by default firewall
On Wed, Aug 28, 2019 at 7:46 PM, Christopher wrote: Yeah, I also don't want a complicated installer. I just don't see this disagreement going anywhere without some sort of compromise, and I can't think of any others that will satisfy people. I think there's a good chance this could be implemented without much complexity, though. Thank you for giving the idea at least a little consideration, though, and not outright dismissing it. The potential compromise I see might involve exposing firewall zones in some well-considered and thoughtful way, including a rethink of what is blocked and allowed by the zones, and an understanding of what the goal of having each zone is. That would have to be done in both gnome-shell and gnome-control-center, and it'd need to receive buy-in from relevant designers and developers. Such an effort would need to be undertaken by developers who understand and accept a requirement to not break installed applications or services, to not expect users to be capable of editing firewall rules, and to not require the installation of a firewall GUI application that exposes technical details like ports. It would also need to firmly reject the assumption that users know (or even that users *should* know) the difference between a TCP port and a USB port. Otherwise, the gulf between the two sides here is just too great, and there's no hope for a useful discussion or compromise. But if these requirements are OK, maybe we can agree on something. The work would need to be undertaken by people actually interested in the problem. Expecting existing Workstation developers to work on this is not likely to turn out well, since we're busy, and I think most of us are already OK with the status quo. It'd also be helpful to get beyond this security myth that having a firewall is somehow essential to have a secure workstation. I'm firmly convinced this is not the case, and I'm unpersuaded by most of the comments in this thread that assume otherwise. The best argument I've seen so far in favor of a firewall was accidentally sharing your Rhythmbox media library on a public network, so focusing on that or similar issues would be helpful. Unplugging from trusted "wired connection 1" (e.g. a home router) and plugging into a different untrusted "wired connection 1" (e.g. a modem) is another good example from this thread of where mistakes can currently occur. We probably shouldn't allow users to share media on a network where the user has a public IP, for instance. But just repeated claiming that a firewall is essential for security isn't going to impress me. Iñaki seems to be batting in this direction with the issues he's filed. His approach seems constructive to me. I fear it might be easy to have missed his comment in this noisy thread. Michael ___ 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
Re: Fedora Workstation and disabled by default firewall
On Wed, Aug 28, 2019 at 5:33 AM, Jiri Eischmann wrote: And the same document says: "While our focus is on creating a top-class developer workstation, our developer focus will not compromise the aforementioned goal to be a polished and user friendly system that appeals to a wide general audience." Having a target audience in mind doesn't mean we have to make bad design for everyone else. Absolutely. In addition their preferences could be actually the same. Just look at macOS, it's made easy for our moms and dads and very popular with developers at the same time. If anybody with a good memory or interest in thread archaeology wants to investigate, I believe there was actually some problem with some specific tools used by web developers that were broken by the previous firewall configuration. Michael ___ 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
[Bug 1747549] New: perl-PPIx-Regexp-0.067 is available
https://bugzilla.redhat.com/show_bug.cgi?id=1747549 Bug ID: 1747549 Summary: perl-PPIx-Regexp-0.067 is available Product: Fedora Version: rawhide Status: NEW Component: perl-PPIx-Regexp Keywords: FutureFeature, Triaged Assignee: ppi...@redhat.com Reporter: upstream-release-monitor...@fedoraproject.org QA Contact: extras...@fedoraproject.org CC: perl-devel@lists.fedoraproject.org, ppi...@redhat.com Target Milestone: --- Classification: Fedora Latest upstream release: 0.067 Current version/release in rawhide: 0.066-1.fc32 URL: http://search.cpan.org/dist/PPIx-Regexp/ Please consult the package updates policy before you issue an update to a stable branch: https://fedoraproject.org/wiki/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/3288/ -- You are receiving this mail because: You are on the CC list for the bug. ___ 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
Fedora 31 compose report: 20190829.n.0 changes
OLD: Fedora-31-20190828.n.0 NEW: Fedora-31-20190829.n.0 = SUMMARY = Added images:1 Dropped images: 2 Added packages: 3 Dropped packages:23 Upgraded packages: 0 Downgraded packages: 0 Size of added packages: 7.13 MiB Size of dropped packages:245.40 MiB Size of upgraded packages: 0 B Size of downgraded packages: 0 B Size change of upgraded packages: 0 B Size change of downgraded packages: 0 B = ADDED IMAGES = Image: Container_Minimal_Base docker aarch64 Path: Container/aarch64/images/Fedora-Container-Minimal-Base-31-20190829.n.0.aarch64.tar.xz = DROPPED IMAGES = Image: Workstation raw-xz aarch64 Path: Workstation/aarch64/images/Fedora-Workstation-31-20190828.n.0.aarch64.raw.xz Image: Server raw-xz aarch64 Path: Server/aarch64/images/Fedora-Server-31-20190828.n.0.aarch64.raw.xz = ADDED PACKAGES = Package: gnome-python2-2.28.1-23.fc29 Summary: PyGNOME Python extension module RPMs:gnome-python2 gnome-python2-bonobo gnome-python2-canvas gnome-python2-devel gnome-python2-gconf gnome-python2-gnome gnome-python2-gnomevfs Size:2.52 MiB Package: gtksourceview2-2.11.2-27.fc29 Summary: A library for viewing source files RPMs:gtksourceview2 gtksourceview2-devel Size:4.60 MiB Package: nodejs-grunt-legacy-util-1.0.0-6.fc29 Summary: Deprecated Grunt utils provided for backwards compatibility RPMs:nodejs-grunt-legacy-util Size:14.86 KiB = DROPPED PACKAGES = Package: ailurus-10.10.3-19.fc31 Summary: A simple application installer and GNOME tweaker RPMs:ailurus Size:1.80 MiB Package: bleachbit-2.2-2.fc31 Summary: Python utility to free disk space and improve privacy RPMs:bleachbit Size:532.58 KiB Package: cherrytree-0.38.5-5.fc30 Summary: Hierarchical note taking application RPMs:cherrytree Size:1.03 MiB Package: cmpi-bindings-0.9.5-20.fc31 Summary: Adapter to write and run CMPI-type CIM providers RPMs:cmpi-bindings-pywbem Size:704.58 KiB Package: community-mysql-5.6.39-2.module_f31+3355+9ac64843 Summary: MySQL client programs and shared libraries RPMs:community-mysql community-mysql-bench community-mysql-common community-mysql-devel community-mysql-embedded community-mysql-embedded-devel community-mysql-errmsg community-mysql-libs community-mysql-server community-mysql-test Size:234.75 MiB Package: did-0.12-4.fc31 Summary: What did you do last week, month, year? RPMs:did Size:103.54 KiB Package: earcandy-0.9-12.fc31 Summary: Sound level manager RPMs:earcandy Size:100.61 KiB Package: fedwatch-0.5-11.fc30 Summary: Tool for watching fedmsg messages and running arbitrary scripts RPMs:fedwatch python2-fedwatch Size:33.75 KiB Package: gilmsg-0.1.2-9.fc30 Summary: A reliability layer on top of fedmsg RPMs:gilmsg Size:27.86 KiB Package: gjots2-3.0.2-7.fc31 Summary: A note jotter - Organise your ideas, notes, facts in a hierarchy RPMs:gjots2 Size:210.64 KiB Package: ipsilon-2.1.0-7.fc31 Summary: An Identity Provider Server RPMs:ipsilon ipsilon-authfas ipsilon-authform ipsilon-authgssapi ipsilon-authldap ipsilon-authpam ipsilon-base ipsilon-client ipsilon-filesystem ipsilon-infofas ipsilon-infosssd ipsilon-openid ipsilon-openidc ipsilon-persona ipsilon-saml2 ipsilon-saml2-base ipsilon-tools-ipa Size:702.58 KiB Package: ldtp-3.5.0-15.fc31 Summary: Desktop testing framework RPMs:ldtp Size:114.69 KiB Package: moksha-1.0.0-18.fc30 Summary: A platform for creating real-time web applications RPMs:moksha moksha-doc moksha-server Size:1.06 MiB Package: mote-0.6.2-10.fc30 Summary: A MeetBot log wrangler, providing a user-friendly interface for Fedora's logs RPMs:mote Size:157.09 KiB Package: packagedb-cli-2.14.1-10.fc31 Summary: A CLI for pkgdb RPMs:packagedb-cli Size:57.27 KiB Package: pybliographer-1.2.18-7.fc31 Summary: Framework for working with bibliographic databases RPMs:pybliographer Size:1.63 MiB Package: python-fedmsg-meta-debian-0.1-14.fc30 Summary: Metadata providers for Debian's fedmsg deployment RPMs:python2-fedmsg-meta-debian Size:15.43 KiB Package: python-fmn-consumer-1.0.3-9.fc31 Summary: Backend worker daemon for Fedora Notifications RPMs:python2-fmn-consumer Size:75.01 KiB Package: python-moksha-wsgi-1.2.4-12.fc31 Summary: WSGI components for Moksha RPMs:python2-moksha-wsgi Size:381.45 KiB Package: python-pwntools-3.12.2-2.fc31 Summary: A CTF framework and exploit development library RPMs:python2-pwntools Size:1.91 MiB Package: python-robosignatory-0.5.0-4.fc30 Summary: A fedmsg consumer that automatically signs artifacts RPMs:python2-robosignatory Size:32.03 KiB Package: python-summershum-0.1.5-11.fc30 Summary: A fedmsg consumer that extracts and stores hashes of source files RPMs:python2-summershum Size:29.93 KiB Package: trac-fedmsg-plugin-0.4.0-11.fc31 Summary: Emit fedmsg messages RPMs:
Re: University people in Fedora: Education/University SIG
If you're interested, feel free to add your name to the Members section of the University SIG [2] wiki. I don't see why grad students can't join as well :) As of now, I don't think there is a set "agenda" for the SIG to focus on. I believe around next week we will focus on figuring out the best way to communicate with one another, and come up with a roadmap. Afaik, the main goal at this point is to make Fedora more accessible and friendly towards students and courses. This may mean updating documentation, packaging software used in university courses, and everything in between :) - Tim Zabel On Fri, 2019-08-30 at 22:24 +0530, Manas Mangaonkar wrote: > +1 for this idea,i'd love to join this sig > > On Fri, Aug 30, 2019 at 9:01 PM Ben Rosser > wrote: > > On Wed, Aug 28, 2019 at 12:43 PM Timothée Floure > > wrote: > > > Hello everyone, > > > > > > This is a follow-up email for some "coffee discussions" we had at > > > flock a few > > > weeks ago. Sorry for the delay! > > > > > > The Fedora community contains a lot of university students, many > > > of us > > > packaging tools for their courses and acting as first-level Linux > > > support for > > > the local student community. The problems we encounter and work > > > on are not > > > identical but share a common base: it only makes sense to > > > collaborate. > > > > > > We found (over a few flock coffee breaks) 5-6 fedorans interested > > > in joining > > > such an initiative and are currently creating a SIG as a mean to > > > communicate. > > > We haven't decided on anything yet, except that we would like to > > > work together > > > to make Fedora an accessible platform for student and courses in > > > an university > > > context. We expect overlapping interests and collaboration with > > > others SIGs, > > > especially if related to the academic world such as NeuroFedora > > > or ML. > > > > > > We are aware of the dormant Education SIG [1] but have yet to > > > discuss how to > > > position - or integrate - ourselve. > > > > > > A slightly more detailed description can be found on the related > > > wiki page [2]. > > > I invite you to add your name to its members section you're > > > interested to work > > > with us. We will figure out communication and coordination > > > mediums around next > > > week. > > > > > > [1] https://fedoraproject.org/wiki/SIGs/Education > > > [2] https://fedoraproject.org/wiki/SIGs/University > > > > Hi Timothée, > > > > I think this is a great initiative! Maybe it's a bit early to ask, > > but > > I'm curious what sort of projects you see a SIG focusing on? > > > > (If grad students would be welcome here too, I might be interested. > > :) ) > > > > Cheers, > > Ben Rosser > > ___ > > 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 > ___ > 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 ___ 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
RE: getting below error in fedpkg clone
Hi Kevin, It's started working. Thanks for the help. Regards, Muneendra. -Original Message- From: Kevin Fenzi [mailto:ke...@scrye.com] Sent: Friday, August 30, 2019 8:58 PM To: devel@lists.fedoraproject.org Subject: Re: getting below error in fedpkg clone On 8/30/19 6:54 AM, Filipe Brandenburger wrote: > Hi, > > On Fri, Aug 30, 2019 at 1:58 AM Muneendra Kumar M via devel > wrote: >> I have added the ssh key in https://admin.fedoraproject.org/accounts >> Will it take sometime to propagate the keys ? > > I'm on the same boat. It's been at least ~5 hours since I added the > keys to FAS and I'm still not able to log in to pkgs.fedoraproject.org Can you all try again now? > Does this propagate on a once-a-day cron? (And, if so, can it be made > more frequent? Is it really *that* expensive?) no. It's supposed to trigger on fas account changes, but that part isn't working since we moved the account system to openshift. It's on the list to fix. > Or is there something else wrong with my particular case, and I should > try to escalate it? File an infrastructure ticket and we can look at it/force a refresh (which I have done). kevin ___ 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
Re: RPM building on s390x sometimes is very slow on F-30+
On 8/28/19 2:13 PM, Peter Lemenkov wrote:
> Hello All,
>
> I've just got hit by this again - lockups on s390. Looks like I have
> 100% reproducer (just try to build Erlang and it will stuck
> eventually).
>
> * https://koji.fedoraproject.org/koji/taskinfo?taskID=37327589
>
> Where should I open a ticket? Bugzilla.redhat.com or somewhere else?
I'm really not fully sure. ;(
Perhaps a kernel bug and get the s390x folks involved?
kevin
--
>
> чт, 25 июл. 2019 г. в 17:44, Kevin Fenzi :
>>
>> On 7/25/19 3:04 AM, Peter Lemenkov wrote:
>>> Hello All!
>>> It started to get stuck again. Right now I'm experiencing this issue
>>> with RabbitMQ for F-30 and F-31:
>>>
>>> * https://koji.fedoraproject.org/koji/taskinfo?taskID=36457376
>>> * https://koji.fedoraproject.org/koji/taskinfo?taskID=36457345
>>
>> So, yeah.
>>
>>> | |-kojid,31279 /usr/sbin/kojid --fg --force-lock --verbose
>>> | | `-mock,31584 -tt /usr/libexec/mock/mock -r
>>> koji/f30-build-16961487-1222718 --old-chroot --no-clean --target s390x ...
>>> | | `-rpmbuild,32205 -bb --target s390x --nodeps
>>> /builddir/build/SPECS/rabbitmq-server.spec
>>> | | `-sh,32237 -e /var/tmp/rpm-tmp.GwzEQt
>>> | | `-make,32238 -j4 VERSION=3.7.16 V=1
>>> | | `-sh,32318 -c...
>>> | | `-make,2112 -C
>>> /builddir/build/BUILD/rabbitmq-server-3.7.16/deps/amqp10_client IS_DEP=1
>>> | | `-make,2237 --no-print-directory app-build
>>> | | `-beam.smp,2302 -sbtu -A0 -- -root
>>> /usr/lib64/erlang -progname erl -- -home /builddir -- ...
>>> | | |-{beam.smp},2303
>>> | | |-{beam.smp},2304
>>> | | |-erl_child_setup,2305 1024
>>> | | |-{beam.smp},2306
>>> | | |-{beam.smp},2307
>>> | | |-{beam.smp},2308
>>> | | |-{beam.smp},2309
>>> | | |-{beam.smp},2310
>>> | | |-{beam.smp},2311
>>> | | |-{beam.smp},2312
>>> | | |-{beam.smp},2313
>>> | | |-{beam.smp},2314
>>> | | |-{beam.smp},2315
>>> | | |-{beam.smp},2316
>>> | | |-{beam.smp},2317
>>> | | |-{beam.smp},2318
>>> | | |-{beam.smp},2319
>>> | | |-{beam.smp},2320
>>> | | |-{beam.smp},2321
>>> | | |-{beam.smp},2322
>>> | | |-{beam.smp},2323
>>> | | |-{beam.smp},2324
>>> | | `-{beam.smp},2325
>>
>> When I strace the 2302 process:
>>
>> strace: Process 2302 attached with 23 threads
>> [pid 2324] ppoll([{fd=12, events=POLLIN|POLLRDNORM}], 1, NULL, NULL, 8
>>
>> [pid 2320] futex(0x3ff58800550, FUTEX_WAIT_PRIVATE, 4294967295, NULL
>>
>> [pid 2321] futex(0x3ff58800590, FUTEX_WAIT_PRIVATE, 4294967295, NULL
>>
>> [pid 2319] futex(0x3ff58800510, FUTEX_WAIT_PRIVATE, 4294967295, NULL
>>
>> [pid 2318] futex(0x3ff588004d0, FUTEX_WAIT_PRIVATE, 4294967295, NULL
>>
>> [pid 2317] futex(0x3ff58800490, FUTEX_WAIT_PRIVATE, 4294967295, NULL
>>
>> [pid 2316] futex(0x3ff58800450, FUTEX_WAIT_PRIVATE, 4294967295, NULL
>>
>> [pid 2315] futex(0x3ff58800410, FUTEX_WAIT_PRIVATE, 4294967295, NULL
>>
>> [pid 2313] futex(0x3ff58800390, FUTEX_WAIT_PRIVATE, 4294967295, NULL
>>
>> [pid 2312] futex(0x3ff58800350, FUTEX_WAIT_PRIVATE, 4294967295, NULL
>>
>> [pid 2308] restart_syscall(<... resuming interrupted
>> syscall_0xfdfc ...> > ed ...>
>> [pid 2303] read(14,
>> [pid 2302] select(0, NULL, NULL, NULL, NULL
>> [pid 2309] restart_syscall(<... resuming interrupted select ...>
>>
>> [pid 2323] futex(0x3ff58800610, FUTEX_WAIT_PRIVATE, 4294967295, NULL
>>
>> [pid 2322] futex(0x3ff588005d0, FUTEX_WAIT_PRIVATE, 4294967295, NULL
>>
>> [pid 2314] futex(0x3ff588003d0, FUTEX_WAIT_PRIVATE, 4294967295, NULL
>>
>> [pid 2311] futex(0x3ff58800310, FUTEX_WAIT_PRIVATE, 4294967295, NULL
>>
>> [pid 2310] futex(0x3ff588002d0, FUTEX_WAIT_PRIVATE, 4294967295, NULL
>>
>> [pid 2306] restart_syscall(<... resuming interrupted
>> syscall_0xfdfc ...> > ed ...>
>> [pid 2304] futex(0x2aa3d9af520, FUTEX_WAIT_PRIVATE, 0, NULL > ...>
>> [pid 2307] timerfd_settime(11, 0, {it_interval={tv_sec=0, tv_nsec=0},
>> it_value={tv_sec=0, tv_n
>> sec=0}}, NULL) = 0
>> [pid 2325] epoll_wait(4,
>> [pid 2307]
Re: Best practice for local files in a package
On 8/29/19 11:37 AM, Stephen John Smoogen wrote: > On Thu, 29 Aug 2019 at 14:26, Bruno Wolff III wrote: >> >> I got a warning about not having urls for a couple of files in the >> squashfs-tools package from release monitoring. >> The bug which has the comment is: >> https://bugzilla.redhat.com/show_bug.cgi?id=1747102 >> >> These are based on some man pages used in Debian at one time, but do not >> track changes in the originals. I need to look at these again since 4.4 >> has a number of new options. And I'm wondering what I should do to not >> break test release monitoring builds for files in the package that are local >> and not derived from (on an ongoing basis) an upstream? > > I got a similar one for nagios. I am wondering if it would make sense > to put these in some git repo and just point the source to that but no > idea Well, in the squashfs-tools case these are in the looaside cache, so you could (all be it ugly looking), use: https://src.fedoraproject.org/lookaside/pkgs/squashfs-tools/unsquashfs.1/sha512/6e1be535d370fb39b2a0e47c98052727bab94ae4f306bb3eb8f7dd07fb84bf985e82ba66bb2030e08261473cffc34d1c1973b27e77cb7127d588e24297f2f0a3/unsquashfs.1 You would have to change that if the file got uploaded again with changes of course. kevin signature.asc Description: OpenPGP digital 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
Re: Fedora 31 System-Wide Change proposal: Switch RPMs to zstd compression
On 8/29/19 11:44 PM, Miroslav Suchý wrote: > Dne 29. 08. 19 v 18:58 Kamil Dudka napsal(a): >> What is the recommended way to build Fedora 31+ RPMs on a RHEL-7 host? > > I think that no one contemplate supporting RHEL 7 regarding zstd. The real > thing is "how to build Fedora 31+ RPMs on a > RHEL-8 host"? > https://bugzilla.redhat.com/show_bug.cgi?id=1715799 > Couldn't this be a use for bootstrap mode? Or is it still not working? kevin signature.asc Description: OpenPGP digital 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
Fedora-31-20190829.n.0 compose check report
No missing expected images. Failed openQA tests: 18/152 (x86_64), 1/2 (arm) Old failures (same test failed in Fedora-31-20190828.n.0): ID: 438981 Test: x86_64 Server-dvd-iso modularity_tests URL: https://openqa.fedoraproject.org/tests/438981 ID: 438989 Test: x86_64 Workstation-live-iso install_default_upload URL: https://openqa.fedoraproject.org/tests/438989 ID: 438991 Test: x86_64 Workstation-live-iso install_default@uefi URL: https://openqa.fedoraproject.org/tests/438991 ID: 439016 Test: x86_64 KDE-live-iso desktop_background URL: https://openqa.fedoraproject.org/tests/439016 ID: 439019 Test: arm Minimal-raw_xz-raw.xz install_arm_image_deployment_upload URL: https://openqa.fedoraproject.org/tests/439019 ID: 439021 Test: x86_64 Silverblue-dvd_ostree-iso install_default_upload URL: https://openqa.fedoraproject.org/tests/439021 ID: 439023 Test: x86_64 Silverblue-dvd_ostree-iso install_default@uefi URL: https://openqa.fedoraproject.org/tests/439023 ID: 439042 Test: x86_64 universal install_no_swap URL: https://openqa.fedoraproject.org/tests/439042 ID: 439050 Test: x86_64 universal install_european_language URL: https://openqa.fedoraproject.org/tests/439050 ID: 439055 Test: x86_64 universal install_software_raid URL: https://openqa.fedoraproject.org/tests/439055 ID: 439057 Test: x86_64 universal upgrade_2_desktop_encrypted_64bit URL: https://openqa.fedoraproject.org/tests/439057 ID: 439074 Test: x86_64 universal install_software_raid@uefi URL: https://openqa.fedoraproject.org/tests/439074 ID: 439080 Test: x86_64 universal install_no_swap@uefi URL: https://openqa.fedoraproject.org/tests/439080 ID: 439083 Test: x86_64 universal upgrade_desktop_64bit URL: https://openqa.fedoraproject.org/tests/439083 ID: 439088 Test: x86_64 universal upgrade_desktop_encrypted_64bit URL: https://openqa.fedoraproject.org/tests/439088 ID: 439092 Test: x86_64 universal install_cyrillic_language URL: https://openqa.fedoraproject.org/tests/439092 ID: 439093 Test: x86_64 universal install_arabic_language URL: https://openqa.fedoraproject.org/tests/439093 ID: 439094 Test: x86_64 universal install_asian_language URL: https://openqa.fedoraproject.org/tests/439094 ID: 439097 Test: x86_64 universal upgrade_2_desktop_64bit URL: https://openqa.fedoraproject.org/tests/439097 Soft failed openQA tests: 2/152 (x86_64) (Tests completed, but using a workaround for a known bug) Old soft failures (same test soft failed in Fedora-31-20190828.n.0): ID: 439087 Test: x86_64 universal upgrade_kde_64bit URL: https://openqa.fedoraproject.org/tests/439087 ID: 439089 Test: x86_64 universal upgrade_2_kde_64bit URL: https://openqa.fedoraproject.org/tests/439089 Passed openQA tests: 112/152 (x86_64) Skipped non-gating openQA tests: 21 of 154 Installed system changes in test x86_64 Server-boot-iso install_default: 1 packages(s) added since previous compose: samba-libs Previous test data: https://openqa.fedoraproject.org/tests/437551#downloads Current test data: https://openqa.fedoraproject.org/tests/438952#downloads Installed system changes in test x86_64 Server-boot-iso install_default@uefi: 1 packages(s) added since previous compose: samba-libs Previous test data: https://openqa.fedoraproject.org/tests/437552#downloads Current test data: https://openqa.fedoraproject.org/tests/438953#downloads Installed system changes in test x86_64 KDE-live-iso install_default_upload: 1 services(s) added since previous compose: dbus-:1.6-org.freedesktop.problems@0.service loaded active running dbus-:1.6-org.freedesktop.problems@0.service 2 services(s) removed since previous compose: dbus-:1.7-org.freedesktop.problems@0.service loaded active running dbus-:1.7-org.freedesktop.problems@0.service, pcscd.service System load changed from 0.77 to 0.47 Previous test data: https://openqa.fedoraproject.org/tests/437773#downloads Current test data: https://openqa.fedoraproject.org/tests/439004#downloads Installed system changes in test x86_64 KDE-live-iso install_default@uefi: 1 services(s) added since previous compose: dbus-:1.7-org.freedesktop.problems@0.service loaded active running dbus-:1.7-org.freedesktop.problems@0.service 1 services(s) removed since previous compose: dbus-:1.6-org.freedesktop.problems@0.service loaded active running dbus-:1.6-org.freedesktop.problems@0.service System load changed from 0.38 to 0.54 Previous test data: https://openqa.fedoraproject.org/tests/437604#downloads Current test data: https://openqa.fedoraproject.org/tests/439006#downloads Installed system changes in test x86_64 universal install_package_set_kde: Used mem changed from 878 MiB to 754 MiB System load changed from 1.01 to 1.48 Average CPU
Re: Non-responsive maintainer
Jenkins in a container is begging for container churn with artifacts and logs. Jenkins *slaves* are another story, Sent from my iPhone > On Aug 29, 2019, at 9:38 PM, John Harris wrote: > >> On Thursday, August 29, 2019 11:11:43 AM MST Fabio Valentini wrote: >> On Thu, Aug 29, 2019 at 7:51 PM Greg Hellings >> wrote: >>> >>> >>> The jenkins pacakge is fearfully out of date and seems unmaintained. Does >>> anyone know how to get in touch with the maintainer(s) of the package? >> >>> >>> >>> https://bugzilla.redhat.com/show_bug.cgi?id=1560603 >> >> >> It's not only out of date, but also hilariously broken. Just check this >> page: https://apps.fedoraproject.org/koschei/search?q=jenkins >> >> Most of the packaged jenkins plugins have already been retired for >> fedora 31+, and jenkins itself is broken because a lot of its >> dependencies have been retired as well. >> >> Judging by the state of the Java stack in fedora, I'd recommend some >> kind of container workflow that doesn't actually include fedora >> packages for jenkins. >> Another approach might be for you to join the Java SIG and revive >> jenkins in fedora (which would require a lot of work). > > I would recommend Jenkins be installed in the vendor supported method. I fail > to see how containers would be useful here, but the correct way to do that in > a container would be in the method described here: > > https://fedoramagazine.org/container-technologies-fedora-systemd-nspawn/ > > -- > John M. Harris, Jr. > Splentity > https://splentity.com/ > > ___ > 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 ___ 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
Fedora 31 Beta blocker status email #4
Action summary Accepted blockers - 1. dracut-modules-olpc — Cannot be installed due to unsatisfied 'bitfrost' dependency — NEW ACTION: releng to make Pungi config changes 2. desktop-backgrounds — Fedora 31 still using Fedora 30 backgrounds — NEW ACTION: desktop-backgrounds maintainers to update subpackages to use new backgrounds package 3. gdm — GDM dies after the user has logged out of Gnome Desktop — ASSIGNED ACTION: gdm maintainers to diagnose issue Proposed blockers - 1. anaconda — TypeError: Argument 1 does not allow None as a value — POST ACTION: anaconda upstream to merge PR 2105 2. gnome-initial-setup — g-i-s fails to run after Workstation and Silverblue installs, even with SELinux permissive or disabled — NEW ACTION: gnome-initial-setup maintainers to diagnose issue 3. golang — Cannot pull images from registry.fedoraproject.org — ASSIGNED ACTION: jcajka to upgrade registry.fedoraproject.org to see if this resolves the issue 4. Package Review — Review Request: f31-backgrounds - Fedora 31 default desktop background — POST ACTION: desktop-backgrounds maintainers to push background pacakges. Bug-by-bug detail = Accepted blockers - 1. dracut-modules-olpc — https://bugzilla.redhat.com/show_bug.cgi?id=1734179 — NEW Cannot be installed due to unsatisfied 'bitfrost' dependency bitfrost package was retired, which prevents dracut-modules-olpc from building. adamwill opened an issue against pungi-fedora: https://pagure.io/pungi-fedora/issue/759 2. desktop-backgrounds — https://bugzilla.redhat.com/show_bug.cgi?id=1744266 — NEW Fedora 31 still using Fedora 30 backgrounds Package approved: https://bugzilla.redhat.com/show_bug.cgi?id=1745846. desktop-backgrounds subpackages and kde-settings need updating. 3. gdm — https://bugzilla.redhat.com/show_bug.cgi?id=1745554 — ASSIGNED GDM dies after the user has logged out of Gnome Desktop Switching desktops or logging out kills GDM, which does not restart automatically. Setting SELinux to permissive mode does not help. Proposed blockers - 1. anaconda — https://bugzilla.redhat.com/show_bug.cgi?id=1745933 — POST TypeError: Argument 1 does not allow None as a value Pull request is open upstream to fix the issue: https://github.com/rhinstaller/anaconda/pull/2105 2. gnome-initial-setup — https://bugzilla.redhat.com/show_bug.cgi?id=1746563 — NEW g-i-s fails to run after Workstation and Silverblue installs, even with SELinux permissive or disabled SELinux policy causes "oh no!" error screen. Policy fixed in BZ #1746584. But failures also occur with SELinux in permissive or disable mode, so there is another cause that has ye t to be identified. 3. golang — https://bugzilla.redhat.com/show_bug.cgi?id=1737471 — ASSIGNED Cannot pull images from registry.fedoraproject.org podman in F31 cannot pull images from registry, while F30 can. Disabling TLS 1.3 seems to be a workaround. jcajka has a ticket open in fedora-infrastructure (https://pagure.io/fed ora-infrastructure/issue/8154) to update the registry to see if this fixes it. 4. Package Review — https://bugzilla.redhat.com/show_bug.cgi?id=1745846 — POST Review Request: f31-backgrounds - Fedora 31 default desktop background Package is approved. -- Ben Cotton He / Him / His Fedora Program Manager Red Hat TZ=America/Indiana/Indianapolis ___ 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
BackupPC selinux help
I've got a bug report[1] for BackupPC where the user is having issues with
AVC denials when browsing hosts.
This is actually from my COPR but it's the same SRPM I use for Fedora.
There are almost 50k downloads and this is the only report of a problem so
I don't think there's a fundamental issue with the package but I would
still like to help them out.
They are getting AVC denials when browsing hosts which seems to cause
BackupPC_Admin to write LOCK files in the subdirectories of
/var/lib/BackupPC/. I can find plenty of LOCK files written in my instance
of BackupPC on Centos 7 (same as the user) but NO AVC denials for me.
Here's a snippit from the bug:
$ sudo tail -f /var/log/audit/audit.log | grep avc
type=AVC msg=audit(1567181425.724:40002): avc: denied { write } for
pid=3608 comm="BackupPC_Admin" name="LOCK" dev="sda1" ino=336086870
scontext=system_u:system_r:httpd_t:s0
tcontext=system_u:object_r:var_lib_t:s0 tclass=file permissive=0
type=AVC msg=audit(1567181425.730:40003): avc: denied { write } for
pid=3608 comm="BackupPC_Admin" name="LOCK" dev="sda1" ino=109977609
scontext=system_u:system_r:httpd_t:s0
tcontext=system_u:object_r:var_lib_t:s0 tclass=file permissive=0
...
It happens one for every host he backs up so the inodes are different but
the error is the same for all.
Currently the selinux policy built into the package doesn't modify
/var/lib/BackupPC but in my experience it hasn't needed to.
He's already tried restorecon, changed from a symlink to a bind mount (for
the backup root)...
I'm hesitant to modify the the selinux policy when I can reproduce the
problem...
Ideas?
[1] https://bugzilla.redhat.com/show_bug.cgi?id=1746598
___
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
Re: University people in Fedora: Education/University SIG
On Wed, Aug 28, 2019 at 06:42:15PM +0200, Timothée Floure wrote: > A slightly more detailed description can be found on the related wiki page > [2]. > I invite you to add your name to its members section you're interested to work > with us. We will figure out communication and coordination mediums around next > week. Hi! This is awesome. Please don't forget that Mindshare is providing $150 "mini-grants" for meetups and things like that, and we'd like to do at least two of those a week. One thing I think this SIG could do is put together some pre-packaged ideas for mini-events that could be held on campus for that kind of budget. (Right now, we often have Fedora release parties, but we need more things that aren't tied to the release schedule like that.) Also, university users are a strong interest for Red Hat's investment in the Silverblue initiative, so there's some connecting-up there which might be useful. -- Matthew Miller Fedora Project Leader ___ 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
Re: Non-responsive maintainer
On Fri, Aug 30, 2019 at 12:54 AM Michal Srb wrote: > /me sending the email second time as the first attempt bounced back to me > > Hi Greg, > > Thanks for bringing this to my attention. The package is, unfortunately, > broken in all supported Fedora releases. The version of the package is the > last stable release from 1.x branch, but upstream is now (and has been for > quite some time) on 2.x. Upgrading it to 2.x wouldn't be easy by any means, > it would require a ton of time (weeks, easily...) that unfortunately I > don't have at the moment and most likely won't have in foreseeable future. > In that case, neither will I! > So I am going to do what I should have done a long time ago - I am going > to retire the package. > > I will send a separate email that I am orphaning it (and its dependencies) > and if nobody takes it over, I will just retire it in a week or so. > Sounds perfect. Do you want to also tap the BZ for it? --Greg > Thanks, > Michal > > On Fri, Aug 30, 2019 at 7:45 AM Michal Srb wrote: > >> Hi Greg, >> >> Thanks for bringing this to my attention. The package is, unfortunately, >> broken in all supported Fedora releases. The version of the package is the >> last stable release from 1.x branch, but upstream is now (and has been for >> quite some time) on 2.x. Upgrading it to 2.x wouldn't be easy by any means, >> it would require a ton of time (weeks, easily...) that unfortunately I >> don't have at the moment and most likely won't have in foreseeable future. >> >> So I am going to do what I should have done a long time ago - I am going >> to retire the package. >> >> I will send a separate email that I am orphaning it (and its >> dependencies) and if nobody takes it over, I will just retire it in a week >> or so. >> >> Thanks, >> Michal >> >> On Thu, Aug 29, 2019 at 7:50 PM Greg Hellings >> wrote: >> >>> The jenkins pacakge is fearfully out of date and seems unmaintained. >>> Does anyone know how to get in touch with the maintainer(s) of the package? >>> >>> https://bugzilla.redhat.com/show_bug.cgi?id=1560603 >>> >>> --Greg >>> >> ___ 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
[EPEL-devel] Fedora EPEL 8 updates-testing report
The following Fedora EPEL 8 Security updates need testing: Age URL 6 https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2019-fabd190d13 clamav-0.101.4-1.el8 The following builds have been pushed to Fedora EPEL 8 updates-testing R-3.6.1-1.el8 R-rpm-macros-1.1.0-2.el8 aspell-sk-2.02-2.el8 java-latest-openjdk-12.0.2.9-1.rolling.el8 libnss-mysql-1.5-35.el8 python-pykwalify-1.7.0-4.el8 python-xlrd-1.2.0-3.el8 rpki-client-0.2.0-1.el8 sagator-2.0.0-0.beta34.el8 zabbix40-4.0.11-2.el8 Details about builds: R-3.6.1-1.el8 (FEDORA-EPEL-2019-16908d432e) A language for data analysis and graphics Update Information: Update R to 3.6.1. References: [ 1 ] Bug #1744723 - R-devel requires R-rpm-macros https://bugzilla.redhat.com/show_bug.cgi?id=1744723 [ 2 ] Bug #1727281 - R-3.6.1 is available https://bugzilla.redhat.com/show_bug.cgi?id=1727281 R-rpm-macros-1.1.0-2.el8 (FEDORA-EPEL-2019-16908d432e) Macros to help produce R packages Update Information: Update R to 3.6.1. References: [ 1 ] Bug #1744723 - R-devel requires R-rpm-macros https://bugzilla.redhat.com/show_bug.cgi?id=1744723 [ 2 ] Bug #1727281 - R-3.6.1 is available https://bugzilla.redhat.com/show_bug.cgi?id=1727281 aspell-sk-2.02-2.el8 (FEDORA-EPEL-2019-979e94ec98) Slovak dictionaries for Aspell Update Information: Rebuilt for EPEL8 java-latest-openjdk-12.0.2.9-1.rolling.el8 (FEDORA-EPEL-2019-be17ccd4ab) OpenJDK Runtime Environment 12 Update Information: java-latest-openjdk is now available for epel8. This package contains newest released OpenJDK (currently 12) . libnss-mysql-1.5-35.el8 (FEDORA-EPEL-2019-0fe7db83a2) NSS library for MySQL Update Information: Rebuild for EPEL8. python-pykwalify-1.7.0-4.el8 (FEDORA-EPEL-2019-cf95acfbb6) Python lib/cli for JSON/YAML schema validation Update Information: Initial build for EPEL 8. Initial build for EPEL 8. python-xlrd-1.2.0-3.el8 (FEDORA-EPEL-2019-2eb516a66b) Library to extract data from Microsoft Excel (TM) spreadsheet files Update Information: Rebuilt for EPEL8 rpki-client-0.2.0-1.el8 (FEDORA-EPEL-2019-21fc78d2da) RPKI client implementation Update Information: rpki-client is an implementation of RPKI (Resource Public Key Infrastructure), specified by RFC 6480. It implements the client side of RPKI, which is responsible for downloading, validating and converting ROAs (Route Origin Authorisations) into VRPs (Validated ROA Payloads). The client's output (VRPs) can be used to perform BGP Origin Validation (RFC 6811). The design focus of rpki-client is simplicity and security. To wit, it implements RPKI components necessary for validating route statements and omits superfluities (such as, for example, which X509 certificate sections must be labelled "Critical"). References: [ 1 ] Bug #1745770 - Review Request:
Re: University people in Fedora: Education/University SIG
+1 for this idea,i'd love to join this sig On Fri, Aug 30, 2019 at 9:01 PM Ben Rosser wrote: > > On Wed, Aug 28, 2019 at 12:43 PM Timothée Floure > wrote: > > > > Hello everyone, > > > > This is a follow-up email for some "coffee discussions" we had at flock a > > few > > weeks ago. Sorry for the delay! > > > > The Fedora community contains a lot of university students, many of us > > packaging tools for their courses and acting as first-level Linux support > > for > > the local student community. The problems we encounter and work on are not > > identical but share a common base: it only makes sense to collaborate. > > > > We found (over a few flock coffee breaks) 5-6 fedorans interested in joining > > such an initiative and are currently creating a SIG as a mean to > > communicate. > > We haven't decided on anything yet, except that we would like to work > > together > > to make Fedora an accessible platform for student and courses in an > > university > > context. We expect overlapping interests and collaboration with others SIGs, > > especially if related to the academic world such as NeuroFedora or ML. > > > > We are aware of the dormant Education SIG [1] but have yet to discuss how to > > position - or integrate - ourselve. > > > > A slightly more detailed description can be found on the related wiki page > > [2]. > > I invite you to add your name to its members section you're interested to > > work > > with us. We will figure out communication and coordination mediums around > > next > > week. > > > > [1] https://fedoraproject.org/wiki/SIGs/Education > > [2] https://fedoraproject.org/wiki/SIGs/University > > Hi Timothée, > > I think this is a great initiative! Maybe it's a bit early to ask, but > I'm curious what sort of projects you see a SIG focusing on? > > (If grad students would be welcome here too, I might be interested. :) ) > > Cheers, > Ben Rosser > ___ > 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 ___ 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
Re: f32/rawhide, nothing provides module(platform:f31)
On Fri, 2019-08-30 at 14:37 +0200, Miroslav Suchý wrote: > Dne 23. 08. 19 v 18:20 Kevin Fenzi napsal(a): > > There's nothing you can do, releng needs to rebuild modules: > > > > https://pagure.io/releng/issue/8664 > > > > Is this error: > > Problém 5: package kf5-ktexteditor-5.61.0-1.fc31.x86_64 requires > libgit2.so.28()(64bit), but none of the providers can > be installed > - cannot install the best update candidate for package > kf5-ktexteditor-5.59.0-1.fc30.x86_64 > - package libgit2-0.28.2-2.module_f31+5411+fa1856a4.x86_64 is excluded > - package libgit2-0.28.2-3.fc31.x86_64 is excluded > > the same bucket or not? Not. If you're getting it on an installed system that you're upgrading, you probably need to manually switch the libgit2 module from the 0.27 stream to the 0.28 stream, that should clear it up. -- Adam Williamson Fedora QA Community Monkey IRC: adamw | Twitter: AdamW_Fedora | XMPP: adamw AT happyassassin . net http://www.happyassassin.net ___ 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
[EPEL-devel] Fedora EPEL 6 updates-testing report
The following Fedora EPEL 6 Security updates need testing: Age URL 2 https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2019-af80b147c4 python-mitogen-0.2.8-1.el6 0 https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2019-54cf4d603d seamonkey-2.49.5-1.el6 The following builds have been pushed to Fedora EPEL 6 updates-testing nagios-plugins-2.2.1-17.20190829gitfb792ff.el6 rpki-client-0.2.0-1.el6 Details about builds: nagios-plugins-2.2.1-17.20190829gitfb792ff.el6 (FEDORA-EPEL-2019-9b63c08c0f) Host/service/network monitoring program plugins for Nagios Update Information: Update to latest git and fix release string to match again ChangeLog: * Thu Aug 29 2019 Stephen Smoogen - 2.2.1-17.20190829gitfb792ff - Update to latest git and fix release string to match again - check_ntp.pl was still getting installed as check_ntp. Fix BZ#1664981 - check_ntp.pl has ipv6 problem. Fix BZ#1731468 * Thu Jul 25 2019 Fedora Release Engineering - 2.2.1-16.20180725git3429dad - Rebuilt for https://fedoraproject.org/wiki/Fedora_31_Mass_Rebuild References: [ 1 ] Bug #1664981 - nagios-plugins-ntp contains old perl script instead of compiled binary check_ntp https://bugzilla.redhat.com/show_bug.cgi?id=1664981 [ 2 ] Bug #1698506 - nagios check_icmp fails when parameter "-s " used https://bugzilla.redhat.com/show_bug.cgi?id=1698506 [ 3 ] Bug #1707814 - check_icmp performance data output changed https://bugzilla.redhat.com/show_bug.cgi?id=1707814 [ 4 ] Bug #1741319 - Package request: Nagios-plugins epel8 https://bugzilla.redhat.com/show_bug.cgi?id=1741319 [ 5 ] Bug #1706859 - check_radius segfaults when tun interface is configured https://bugzilla.redhat.com/show_bug.cgi?id=1706859 [ 6 ] Bug #1731468 - check_ntp has too strict regexp for hostnames https://bugzilla.redhat.com/show_bug.cgi?id=1731468 [ 7 ] Bug #1743794 - Nagios check_dns plugin unable to parse output of nslookup -querytype= on RHEL7.7 https://bugzilla.redhat.com/show_bug.cgi?id=1743794 rpki-client-0.2.0-1.el6 (FEDORA-EPEL-2019-8a8bf6c622) RPKI client implementation Update Information: rpki-client is an implementation of RPKI (Resource Public Key Infrastructure), specified by RFC 6480. It implements the client side of RPKI, which is responsible for downloading, validating and converting ROAs (Route Origin Authorisations) into VRPs (Validated ROA Payloads). The client's output (VRPs) can be used to perform BGP Origin Validation (RFC 6811). The design focus of rpki-client is simplicity and security. To wit, it implements RPKI components necessary for validating route statements and omits superfluities (such as, for example, which X509 certificate sections must be labelled "Critical"). References: [ 1 ] Bug #1745770 - Review Request: rpki-client - RPKI client implementation https://bugzilla.redhat.com/show_bug.cgi?id=1745770 ___ epel-devel mailing list -- epel-devel@lists.fedoraproject.org To unsubscribe send an email to epel-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/epel-devel@lists.fedoraproject.org
Re: Please fix the aarch64 g++ pic problems in f32 rawhide
>>You're much better off including a couple of koji tasks/packages >>showing the issue, it's much easier to get some real context. >OK, here's one at least. I have had to manually add -DPIC to the spec for >aarch64 in order to get>that arch to pass. There were no problems with it up >until recently. >https://koji.fedoraproject.org/koji/taskinfo?taskID=37332928 checking for gcc option to produce PIC... -fPIC -DPICchecking if gcc PIC flag -fPIC -DPIC works... yeschecking for g++ option to produce PIC... -fPIC -DPIC checking if g++ PIC flag -fPIC -DPIC works... yeschecking for gcc option to produce PIC... -fPIC -DPIC checking if gcc PIC flag -fPIC -DPIC works... yeschecking for ld used by g++... /usr/bin/ld checking if the linker (/usr/bin/ld) is GNU ld... yes checking whether the g++ linker (/usr/bin/ld) supports shared libraries... yes checking for g++ option to produce PIC... -fPIC -DPIC checking if g++ PIC flag -fPIC -DPIC works... no <=== What ___ 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 ___ 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
[Bug 1747182] perl-Locale-Codes-3.62 is available
https://bugzilla.redhat.com/show_bug.cgi?id=1747182 --- Comment #7 from Fedora Update System --- perl-Locale-Codes-3.62-1.fc29 has been pushed to the Fedora 29 testing repository. If problems still persist, please make note of it in this bug report. See https://fedoraproject.org/wiki/QA:Updates_Testing for instructions on how to install test updates. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2019-3d48221f72 -- You are receiving this mail because: You are on the CC list for the bug. ___ 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
Re: Debates/back and forths
On Wed, Aug 28, 2019 at 06:27:56PM +0200, Chris Peters wrote: > Maybe the code of conduct could politely nudge people towards *quality* > over quantity (so that voices don't get drowned and big threads aren't so > tiresome to keep up with) I don't think that's a job for the code of conduct. However, I think it's good advice for mailing list discussions. Remember, replying to every point is more likely to get the entire thread muted and _fewer_ people to hear you than if you more judiciously reply when you definitely have something new to add. -- Matthew Miller Fedora Project Leader ___ 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
Re: University people in Fedora: Education/University SIG
On Wed, Aug 28, 2019 at 12:43 PM Timothée Floure wrote: > > Hello everyone, > > This is a follow-up email for some "coffee discussions" we had at flock a few > weeks ago. Sorry for the delay! > > The Fedora community contains a lot of university students, many of us > packaging tools for their courses and acting as first-level Linux support for > the local student community. The problems we encounter and work on are not > identical but share a common base: it only makes sense to collaborate. > > We found (over a few flock coffee breaks) 5-6 fedorans interested in joining > such an initiative and are currently creating a SIG as a mean to communicate. > We haven't decided on anything yet, except that we would like to work together > to make Fedora an accessible platform for student and courses in an university > context. We expect overlapping interests and collaboration with others SIGs, > especially if related to the academic world such as NeuroFedora or ML. > > We are aware of the dormant Education SIG [1] but have yet to discuss how to > position - or integrate - ourselve. > > A slightly more detailed description can be found on the related wiki page > [2]. > I invite you to add your name to its members section you're interested to work > with us. We will figure out communication and coordination mediums around next > week. > > [1] https://fedoraproject.org/wiki/SIGs/Education > [2] https://fedoraproject.org/wiki/SIGs/University Hi Timothée, I think this is a great initiative! Maybe it's a bit early to ask, but I'm curious what sort of projects you see a SIG focusing on? (If grad students would be welcome here too, I might be interested. :) ) Cheers, Ben Rosser ___ 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
[Bug 1747182] perl-Locale-Codes-3.62 is available
https://bugzilla.redhat.com/show_bug.cgi?id=1747182 --- Comment #6 from Fedora Update System --- perl-Locale-Codes-3.62-1.fc30 has been pushed to the Fedora 30 testing repository. If problems still persist, please make note of it in this bug report. See https://fedoraproject.org/wiki/QA:Updates_Testing for instructions on how to install test updates. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2019-79a7e5d478 -- You are receiving this mail because: You are on the CC list for the bug. ___ 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
Re: getting below error in fedpkg clone
On 8/30/19 6:54 AM, Filipe Brandenburger wrote: > Hi, > > On Fri, Aug 30, 2019 at 1:58 AM Muneendra Kumar M via devel > wrote: >> I have added the ssh key in https://admin.fedoraproject.org/accounts >> Will it take sometime to propagate the keys ? > > I'm on the same boat. It's been at least ~5 hours since I added the > keys to FAS and I'm still not able to log in to pkgs.fedoraproject.org Can you all try again now? > Does this propagate on a once-a-day cron? (And, if so, can it be made > more frequent? Is it really *that* expensive?) no. It's supposed to trigger on fas account changes, but that part isn't working since we moved the account system to openshift. It's on the list to fix. > Or is there something else wrong with my particular case, and I should > try to escalate it? File an infrastructure ticket and we can look at it/force a refresh (which I have done). kevin signature.asc Description: OpenPGP digital 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
Re: Fedora Workstation and disabled by default firewall
On Thu, Aug 29, 2019 at 06:54:48PM -0700, John Harris wrote: > Workstation is only the primary product because somebody decided GNOME was > the best default. This should be reconsidered, so that the various Spins, This is backwards. We (the Fedora Board) at the time, asked for a team to develop our primary desktop-focused edition, and the team that stepped up to do that chose GNOME as the best environment to use for that. I think this is still the case. But that doesn't mean that the other desktops and spins and solutions using them aren't important. I refer you to https://communityblog.fedoraproject.org/fedoras-strategic-direction-an-update-from-the-council/ for current Fedora Council thinking on this. -- Matthew Miller Fedora Project Leader ___ 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
Re: Please fix the aarch64 g++ pic problems in f32 rawhide
>On Friday, August 30, 2019, 07:45:19 AM EDT, Peter Robinson > wrote: >On Thu, Aug 29, 2019 at 10:21 PM Philip Kovacs via devel wrote: >> >> Several of us are getting errors in our c++ packages related to missing PIC >> flags in aarch64. >> >> Something is amiss there. A small snippet from openmpi: >You're much better off including a couple of koji tasks/packages >showing the issue, it's much easier to get some real context. OK, here's one at least. I have had to manually add -DPIC to the spec for aarch64 in order to getthat arch to pass. There were no problems with it up until recently. https://koji.fedoraproject.org/koji/taskinfo?taskID=37332928 ___ 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 ___ 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
Re: [Test-Announce] Fedora 31 Beta Freeze
On 8/30/19 8:25 AM, Martin Kolman wrote: But wouldn't 24:00/23:59 be even better than 18:00? And changing from 00:00 to 24:00 wouldn't even require changing the actual time (as changing to 18:00 does), just the way it is announced. That is a little confusing in my opinion. I would like to suggest this wording: The deadline is 18:00 UTC, with a six hour grace period ___ 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
Re: Orphaned packages looking for new maintainers
Am 26.08.19 um 10:20 schrieb Miro Hrončok: > python-cairosvg orphan, ralph 3 weeks ago I can take python-cairosvg as I need it for weasyprint (which I hope to update in the next weeks). releng ticket: https://pagure.io/releng/issue/8716 Felix ___ 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
[389-devel] Re: Please review: PRs 50551, 50570, 50573, 50579
Will do first thing next week :) > On 30 Aug 2019, at 21:14, Simon Pichugin wrote: > > Hi team, > there are few PRs on review from me. Please, check... > > https://pagure.io/389-ds-base/pull-request/50551 > https://pagure.io/389-ds-base/pull-request/50570 > https://pagure.io/389-ds-base/pull-request/50573 > https://pagure.io/389-ds-base/pull-request/50579 > > Thanks, > Simon > ___ > 389-devel mailing list -- 389-devel@lists.fedoraproject.org > To unsubscribe send an email to 389-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/389-devel@lists.fedoraproject.org — Sincerely, William Brown Senior Software Engineer, 389 Directory Server SUSE Labs ___ 389-devel mailing list -- 389-devel@lists.fedoraproject.org To unsubscribe send an email to 389-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/389-devel@lists.fedoraproject.org
Re: getting below error in fedpkg clone
Hi, On Fri, Aug 30, 2019 at 1:58 AM Muneendra Kumar M via devel wrote: > I have added the ssh key in https://admin.fedoraproject.org/accounts > Will it take sometime to propagate the keys ? I'm on the same boat. It's been at least ~5 hours since I added the keys to FAS and I'm still not able to log in to pkgs.fedoraproject.org Does this propagate on a once-a-day cron? (And, if so, can it be made more frequent? Is it really *that* expensive?) Or is there something else wrong with my particular case, and I should try to escalate it? Thanks! Filipe ___ 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
[EPEL-devel] Re: perl-LDAP in EPEL 8?
On Fri, 30 Aug 2019 at 09:06, Petr Pisar wrote: > > On Fri, Aug 30, 2019 at 08:51:11AM -0400, Stephen John Smoogen wrote: > > On Fri, 30 Aug 2019 at 07:28, Petr Pisar wrote: > > > > > > On Fri, Aug 30, 2019 at 12:32:12PM +0200, Maximilian Philipps wrote: > > > > It has now been several months since the release of RHEL 8 and I am > > > > still struggling to get a RHEL 8 into an usable state. Besides the > > > > already mentioned absence of fail2ban and nagios plugins I am now facing > > > > the lack of perl-LDAP. > > > > > > > > In RHEL 7 perl-LDAP was part of the base repo, in RHEL 8 it is > > > > completely missing. According to the epel 8 announcement mail I am > > > > supposed to contact the package maintainer, but from what I have found > > > > that > > > > package is always just owned by the project in Fedora/Centos. > > > > > > > > Petr > > > > I am confused you are listed as the admin of the package. > > > > owner: jplesnik; admin: ppisar; commit: mbarnes, rstrode, ssp, > > caolanm, caillon, alexl, johnp, rhughes > > > Owner means the primary maintainer who can administer the package. Admin means > another maintainer. Commit means a person who can change the package source > but who cannot administer the package like adding access to other people. > > Yes, I'm one of the maintainer of the package. > > Do you need to explain something else? I am confused because I misread what was being said. I thought you were having the person file against the base component 'Fedora' in bugzilla versus perl-LDAP. My apologies. -- Stephen J Smoogen. ___ epel-devel mailing list -- epel-de...@lists.fedoraproject.org To unsubscribe send an email to epel-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/epel-de...@lists.fedoraproject.org
libexempi SONAME bump in rawhide
Hello, I'm planning to update exempi to version 2.5.1 in rawhide, and it includes a SONAME change from "libexempi.so.3" to "libexempi.so.8". Affected packages are: caja eog eom equalx nemo tellico tracker-miners I've rebuilt all of them in Copr [1] without issues, except tellico, which failed due to an unrelated bug [2]. Regards, Nikola [1] https://copr.fedorainfracloud.org/coprs/nforro/exempi/builds/ [2] https://bugzilla.redhat.com/show_bug.cgi?id=1746013 ___ 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
[EPEL-devel] Re: perl-LDAP in EPEL 8?
On Fri, Aug 30, 2019 at 08:51:11AM -0400, Stephen John Smoogen wrote: > On Fri, 30 Aug 2019 at 07:28, Petr Pisar wrote: > > > > On Fri, Aug 30, 2019 at 12:32:12PM +0200, Maximilian Philipps wrote: > > > It has now been several months since the release of RHEL 8 and I am > > > still struggling to get a RHEL 8 into an usable state. Besides the > > > already mentioned absence of fail2ban and nagios plugins I am now facing > > > the lack of perl-LDAP. > > > > > > In RHEL 7 perl-LDAP was part of the base repo, in RHEL 8 it is > > > completely missing. According to the epel 8 announcement mail I am > > > supposed to contact the package maintainer, but from what I have found > > > that > > > package is always just owned by the project in Fedora/Centos. > > > > > Petr > > I am confused you are listed as the admin of the package. > > owner: jplesnik; admin: ppisar; commit: mbarnes, rstrode, ssp, > caolanm, caillon, alexl, johnp, rhughes > Owner means the primary maintainer who can administer the package. Admin means another maintainer. Commit means a person who can change the package source but who cannot administer the package like adding access to other people. Yes, I'm one of the maintainer of the package. Do you need to explain something else? -- Petr signature.asc Description: PGP signature ___ epel-devel mailing list -- epel-devel@lists.fedoraproject.org To unsubscribe send an email to epel-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/epel-devel@lists.fedoraproject.org
[EPEL-devel] Re: perl-LDAP in EPEL 8?
On Fri, 30 Aug 2019 at 07:28, Petr Pisar wrote: > > On Fri, Aug 30, 2019 at 12:32:12PM +0200, Maximilian Philipps wrote: > > It has now been several months since the release of RHEL 8 and I am > > still struggling to get a RHEL 8 into an usable state. Besides the > > already mentioned absence of fail2ban and nagios plugins I am now facing > > the lack of perl-LDAP. > > > > In RHEL 7 perl-LDAP was part of the base repo, in RHEL 8 it is > > completely missing. According to the epel 8 announcement mail I am > > supposed to contact the package maintainer, but from what I have found that > > package is always just owned by the project in Fedora/Centos. > > Petr I am confused you are listed as the admin of the package. owner: jplesnik; admin: ppisar; commit: mbarnes, rstrode, ssp, caolanm, caillon, alexl, johnp, rhughes > > What is required to get that package into epel? > > File the request in the Bugzilla against "perl-LDAP" component in "Fedora > EPEL" product in "Fedora" classification. If the component does not exist > there, use a component in "Fedora" product. > > -- Petr > ___ > epel-devel mailing list -- epel-devel@lists.fedoraproject.org > To unsubscribe send an email to epel-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/epel-devel@lists.fedoraproject.org -- Stephen J Smoogen. ___ epel-devel mailing list -- epel-devel@lists.fedoraproject.org To unsubscribe send an email to epel-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/epel-devel@lists.fedoraproject.org
Re: Debates/back and forths
On Thu, Aug 29, 2019 at 6:55 AM Chris Peters wrote: > > PS I won't take this thread any further. The irony of a back and forth in > the back and forth thread doesn't escape me! > > That's hilarious and true. I was thinking the exact same thing... ___ 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
Re: Debates/back and forths
You just explained exactly why it was different ;-) On Wed, Aug 28, 2019 at 9:23 PM John Harris wrote: > On Wednesday, August 28, 2019 5:09:23 AM MST Gerald B. Cox wrote: > > It's somewhat ironic that Discourse would solve this issue. As I > > previously mentioned, I also don't like having my inbox flooded with > forum > > threads that don't interest me. The mailing list solution requires you > > setup filters or continuously delete dozens of emails. Discourse however > > allows you to select what you want to read without needing to clean up > > afterwards. As I also pointed out RSS would make HyperKitty a somewhat > > acceptable alternative - or as Kevin K. pointed out, you could also use > > NNTP. I personally would rather not, but maybe that would fit your use > > case until a good solution could be implemented. > > > > On Wed, Aug 28, 2019 at 4:42 AM Markus Larsson > wrote: > > > On 28 August 2019 13:34:54 CEST, "Dan Čermák" < > > > > > > dan.cer...@cgc-instruments.com> wrote: > > > >Hi Danni, > > > > > > > >Danny Lee writes: > > > >> Hi all, > > > >> > > > >> I'm new to the devel list and fedora in general, but i was wondering > > > > > > > >if > > > > > > > >> these kind of back and forths between a few people is a frequent > > > >> occurrence. I came to Fedora to volunteer what little spare time I > > > > > > > >have > > > > > > > >> to help the Fedora project in some little ways. I don't feel that > > > > > > > >should > > > > > > > >> include wading through dozens of emailed back and forths between > > > >> individuals who seem to have strong, immovable opinions, I just > don't > > > >> > > > >> have time for that. > > > > > > > >Welcome to the club of all the "silent" contributors! > > > > > > > >Usually I try to follow discussions if they appear relevant or > > > >interesting to me, but once they "tip over", I mark that thread as > > > >deleted and mercilessly nuke everything new that comes in. > > > >Yeah, I might miss some important information, but it's unlikely tbh > > > >once you are 20 replies deep into a thread. > > > >On the other hand: I don't want to spend all my free time reading > > > >emails. > > > > > > > >So, if you don't care about a specific topic: just ignore & delete it. > > > > > > This is how I think most do it. Just read the interesting parts. > > > > > > >Btw, this list is imho still pretty moderate, only the occasional > > > >controversy causes a huge thread of replies (and people manage to stay > > > >civilized and tend to bring in new arguments). There's other lists > > > >(unnamed to protect the guilty) where the signal to noise ratio is > > > >much, > > > >much worse. > > > > > > The discourse debate and the fw debate are not the norm but the > exception. > > > We see a few of those from time to time. Most threads aren't like that > > > though. > > > > > > >> Is there any chance there is a moderated list or discussion group > > > > > > > >about > > > > > > > >> current project tasks and issues rather than debates about how to do > > > >> things? Or perhaps, a way to turn off certain threads or block > > > > > > > >certain > > > > > > > >> posters? > > > >> > > > >> Thanks for your time and info you can provide. > > Discourse is not much different from email here. You can see the threads, > and > you choose whether or not you want to read them. If you don't want them to > hit > your inbox or notifications, you can click a button on your client to stop > receiving future emails or notifications from that thread. > > -- > John M. Harris, Jr. > Splentity > https://splentity.com/ > > ___ > 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 > ___ 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
Re: f32/rawhide, nothing provides module(platform:f31)
Dne 23. 08. 19 v 18:20 Kevin Fenzi napsal(a): > There's nothing you can do, releng needs to rebuild modules: > > https://pagure.io/releng/issue/8664 > Is this error: Problém 5: package kf5-ktexteditor-5.61.0-1.fc31.x86_64 requires libgit2.so.28()(64bit), but none of the providers can be installed - cannot install the best update candidate for package kf5-ktexteditor-5.59.0-1.fc30.x86_64 - package libgit2-0.28.2-2.module_f31+5411+fa1856a4.x86_64 is excluded - package libgit2-0.28.2-3.fc31.x86_64 is excluded the same bucket or not? Miroslav signature.asc Description: OpenPGP digital 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
Fedora rawhide compose report: 20190830.n.0 changes
OLD: Fedora-Rawhide-20190829.n.0 NEW: Fedora-Rawhide-20190830.n.0 = SUMMARY = Added images:0 Dropped images: 0 Added packages: 10 Dropped packages:11 Upgraded packages: 90 Downgraded packages: 0 Size of added packages: 3.43 MiB Size of dropped packages:29.66 MiB Size of upgraded packages: 2.08 GiB Size of downgraded packages: 0 B Size change of upgraded packages: 14.50 MiB Size change of downgraded packages: 0 B = ADDED IMAGES = = DROPPED IMAGES = = ADDED PACKAGES = Package: golang-xorm-builder-0.3.5-1.fc32 Summary: Lightweight and fast SQL builder for Go language RPMs:compat-golang-github-xorm-builder-devel golang-xorm-builder-devel Size:39.28 KiB Package: golang-xorm-core-0.7.0-1.fc32 Summary: Lightweight & Compatible wrapper of database/sql RPMs:compat-golang-github-xorm-core-devel golang-xorm-core-devel Size:35.42 KiB Package: is-it-in-rhel-1.0-1.fc32 Summary: Command line tool to find out if a package is in RHEL RPMs:is-it-in-rhel Size:20.15 KiB Package: libspng-0.5.0-1.fc32 Summary: Simple, modern libpng alternative RPMs:libspng libspng-devel Size:270.71 KiB Package: nodejs-grunt-legacy-util-1.1.1-1.fc32 Summary: Deprecated Grunt utils provided for backwards compatibility RPMs:nodejs-grunt-legacy-util Size:13.94 KiB Package: python-boolean.py-3.6-1.fc32 Summary: Define boolean algebras, create and parse boolean expressions and create custom boolean DSL RPMs:python3-boolean.py Size:186.82 KiB Package: python2-pip-19.1.1-8.fc32 Summary: A tool for installing and managing Python 2 packages RPMs:python2-pip Size:1.61 MiB Package: python2-setuptools-41.0.1-9.fc32 Summary: Easily build and distribute Python packages RPMs:python2-setuptools Size:573.72 KiB Package: rpki-client-0.2.0-1.fc32 Summary: RPKI client implementation RPMs:rpki-client Size:318.73 KiB Package: rubygem-puppet-lint-2.3.6-1.fc32 Summary: Ensure your Puppet manifests conform with the Puppetlabs style guide RPMs:rubygem-puppet-lint rubygem-puppet-lint-doc Size:402.00 KiB = DROPPED PACKAGES = Package: compat-SFML16-1.6-21.fc31 Summary: Simple and Fast Multimedia Library RPMs:compat-SFML16 compat-SFML16-devel Size:5.60 MiB Package: dpm-contrib-admintools-0.2.5-2.fc31 Summary: DPM administration toolkit (contrib from GridPP) RPMs:dpm-contrib-admintools Size:322.17 KiB Package: jabber-roster-0.1.1-17.fc31 Summary: A Python tool for listing your Jabber roster contacts RPMs:jabber-roster Size:13.60 KiB Package: lcgdm-1.13.0-3.fc32 Summary: LHC Computing Grid Data Management RPMs:dpm dpm-copy-server-mysql dpm-devel dpm-libs dpm-name-server-mysql dpm-perl dpm-rfio-server dpm-server-mysql dpm-srm-server-mysql lcgdm-devel lcgdm-libs lfc lfc-devel lfc-dli lfc-libs lfc-perl lfc-server-mysql python2-dpm python2-lfc python3-dpm python3-lfc Size:19.57 MiB Package: pology-0.12-10.fc31 Summary: CLI tools for PO files processing RPMs:pology pology-doc python2-pology Size:2.65 MiB Package: puddletag-1.2.0-9.fc31 Summary: Feature rich, easy to use tag editor RPMs:puddletag Size:1.08 MiB Package: pystache-0.5.4-13.fc32 Summary: Mustache for Python RPMs:python2-pystache python3-pystache Size:256.93 KiB Package: python-ipaddress-1.0.18-7.fc31 Summary: Port of the python 3.3+ ipaddress module to 2.6+ RPMs:python2-ipaddress Size:38.19 KiB Package: python-mox-0.5.3-19.fc31 Summary: Mock object framework RPMs:python2-mox Size:38.95 KiB Package: standard-test-roles-4.3-1.module_f32+5937+28e21f11 Summary: Standard Test Interface Ansible roles RPMs:standard-test-roles standard-test-roles-inventory-docker standard-test-roles-inventory-qemu Size:72.90 KiB Package: surl-0.7.1.1-17.fc31 Summary: A URL shortening command line tool RPMs:surl Size:42.24 KiB = UPGRADED PACKAGES = Package: bibletime-2.11.2-5.fc32 Old package: bibletime-2.11.2-3.fc30 Summary: An easy to use Bible study tool RPMs: bibletime Size: 11.81 MiB Size change: -63.62 KiB Package: buildah-1.11.0-0.36.dev.gitecf5b72.fc32 Old package: buildah-1.11.0-0.34.dev.git689f8ed.fc32 Summary: A command line tool used for creating OCI Images RPMs: buildah Size: 44.64 MiB Size change: 7.60 MiB Changelog: * Thu Aug 29 2019 Lokesh Mandvekar (Bot) - 1.11.0-0.35.dev.git5671417 - autobuilt 5671417 * Thu Aug 29 2019 Lokesh Mandvekar (Bot) - 1.11.0-0.36.dev.gitecf5b72 - autobuilt ecf5b72 Package: ccdciel-0.9.60-1.fc32 Old package: ccdciel-0.9.55-2.fc31 Summary: CCD capture software RPMs: ccdciel Size: 24.05 MiB Size change: 1.21 MiB Changelog: * Thu Aug 29 2019 Mattia Verga - 0.9.60-1 - Update to 0.9.60 Package: compsize-1.3-1.fc32 Old package: compsize-1.1-4.fc31 Summary: Utility for measuring compression ratio of f
Re: [Test-Announce] Fedora 31 Beta Freeze
On Fri, 2019-08-30 at 13:59 +0200, Kevin Kofler wrote: > Panu Matilainen wrote: > > On 8/29/19 8:30 PM, Kevin Fenzi wrote: > > > I'd support changing the freeze dates to be something more like 18:00UTC > > > the date they are listed. That would give people more time/be actually > > > on the date when people are awake. I'll float the idea to releng and > > > then fesco. > > > > > > > That would be awesome. > > But wouldn't 24:00/23:59 be even better than 18:00? And changing from 00:00 > to 24:00 wouldn't even require changing the actual time (as changing to > 18:00 does), just the way it is announced. I would personally still find even 24:00 confusing & would really suggest something clearly inambigous, such as 23:45 UTC or similar - that should clear any doubt of which day the freeze is part of once and for all & yet again no actualy changes in the machinery are needed. > > > It's really annoying to wake up to find a freeze reminder in your inbox > > when the freeze already happened. > > Well, that one is really a different issue, that there is an announcement > when the freeze has happened, but no reminder before it happens. Changing > the time of the freeze won't really fix this, sending one or more reminder > mails before the freeze time would. But of course there's also a tradeoff in > that the reminders should not become spam. > > Kevin Kofler > ___ > 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 ___ 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
[Bug 1747182] perl-Locale-Codes-3.62 is available
https://bugzilla.redhat.com/show_bug.cgi?id=1747182 Fedora Update System changed: What|Removed |Added Status|MODIFIED|ON_QA --- Comment #5 from Fedora Update System --- perl-Locale-Codes-3.62-1.fc31 has been pushed to the Fedora 31 testing repository. If problems still persist, please make note of it in this bug report. See https://fedoraproject.org/wiki/QA:Updates_Testing for instructions on how to install test updates. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2019-23e8b01f66 -- You are receiving this mail because: You are on the CC list for the bug. ___ 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
[Bug 1747118] perl-HTTP-Daemon-6.06 is available
https://bugzilla.redhat.com/show_bug.cgi?id=1747118 Fedora Update System changed: What|Removed |Added Status|MODIFIED|ON_QA --- Comment #3 from Fedora Update System --- perl-HTTP-Daemon-6.06-1.fc31 has been pushed to the Fedora 31 testing repository. If problems still persist, please make note of it in this bug report. See https://fedoraproject.org/wiki/QA:Updates_Testing for instructions on how to install test updates. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2019-511f869511 -- You are receiving this mail because: You are on the CC list for the bug. ___ 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
Re: Fedora Workstation and disabled by default firewall
> On Aug 29, 2019, at 9:41 PM, John Harris wrote: > >> On Thursday, August 29, 2019 8:12:22 AM MST Dan Book wrote: >> I would agree, but people do install multiple desktops after installing a >> spin. Such a use case needs to be considered (not sure if it matters, >> though). > > This is definitely not the ideal scenario, especially not from the case of > the > installer for the GNOME spin. I don't know if there's really any reason to > consider it, as the user is taking things into their own hands at that point. Let us not try to outsmart what people *must have wanted*, and err on the side of not leaving their neckties hanging out the window for yanking by passing pranksters. Leave firewalls up by default. ___ 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
Re: [Test-Announce] Fedora 31 Beta Freeze
Panu Matilainen wrote: > On 8/29/19 8:30 PM, Kevin Fenzi wrote: >> I'd support changing the freeze dates to be something more like 18:00UTC >> the date they are listed. That would give people more time/be actually >> on the date when people are awake. I'll float the idea to releng and >> then fesco. >> > > That would be awesome. But wouldn't 24:00/23:59 be even better than 18:00? And changing from 00:00 to 24:00 wouldn't even require changing the actual time (as changing to 18:00 does), just the way it is announced. > It's really annoying to wake up to find a freeze reminder in your inbox > when the freeze already happened. Well, that one is really a different issue, that there is an announcement when the freeze has happened, but no reminder before it happens. Changing the time of the freeze won't really fix this, sending one or more reminder mails before the freeze time would. But of course there's also a tradeoff in that the reminders should not become spam. Kevin Kofler ___ 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
Re: Please fix the aarch64 g++ pic problems in f32 rawhide
On Thu, Aug 29, 2019 at 10:21 PM Philip Kovacs via devel wrote: > > Several of us are getting errors in our c++ packages related to missing PIC > flags in aarch64. > > Something is amiss there. A small snippet from openmpi: You're much better off including a couple of koji tasks/packages showing the issue, it's much easier to get some real context. > make[2]: Entering directory > '/builddir/build/BUILD/openmpi-4.0.2rc1/ompi/mpi/cxx' > /bin/sh ../../../libtool --tag=CXX --mode=link g++ -DNDEBUG -O2 -g -pipe > -Wall -Werror=format-security -Wp,-D_FORTIFY_SOURCE=2 > -Wp,-D_GLIBCXX_ASSERTIONS -fexceptions -fstack-protector-strong > -grecord-gcc-switches -specs=/usr/lib/rpm/redhat/redhat-hardened-cc1 > -specs=/usr/lib/rpm/redhat/redhat-annobin-cc1 -fasynchronous-unwind-tables > -fstack-clash-protection -finline-functions -pthread -version-info 60:1:20 > -Wl,-z,relro -Wl,--as-needed -Wl,-z,now > -specs=/usr/lib/rpm/redhat/redhat-hardened-ld-o libmpi_cxx.la -rpath > /usr/lib64/openmpi/lib mpicxx.lo intercepts.lo comm.lo datatype.lo file.lo > win.lo cxx_glue.lo ../../../ompi/libmpi.la -lrt -lm -lutil -lz -lhwloc > -levent -levent_pthreads > libtool: link: g++ -shared -nostdlib > /usr/lib/gcc/aarch64-redhat-linux/9/../../../../lib64/crti.o > /usr/lib/gcc/aarch64-redhat-linux/9/crtbeginS.o .libs/mpicxx.o > .libs/intercepts.o .libs/comm.o .libs/datatype.o .libs/file.o .libs/win.o > .libs/cxx_glue.o-Wl,-rpath > -Wl,/builddir/build/BUILD/openmpi-4.0.2rc1/ompi/.libs -Wl,-rpath > -Wl,/builddir/build/BUILD/openmpi-4.0.2rc1/orte/.libs -Wl,-rpath > -Wl,/builddir/build/BUILD/openmpi-4.0.2rc1/opal/.libs -Wl,-rpath > -Wl,/usr/lib64/openmpi/lib > -L/builddir/build/BUILD/openmpi-4.0.2rc1/orte/.libs > -L/builddir/build/BUILD/openmpi-4.0.2rc1/opal/.libs > ../../../ompi/.libs/libmpi.so > /builddir/build/BUILD/openmpi-4.0.2rc1/orte/.libs/libopen-rte.so > /builddir/build/BUILD/openmpi-4.0.2rc1/opal/.libs/libopen-pal.so -ldl -lrt > -lutil -lz -lhwloc -levent -levent_pthreads > -L/usr/lib/gcc/aarch64-redhat-linux/9 > -L/usr/lib/gcc/aarch64-redhat-linux/9/../../../../lib64 -L/lib/../lib64 > -L/usr/lib/../lib64 -L/usr/lib/gcc/aarch64-redhat-linux/9/../../.. -lstdc++ > -lm -lpthread -lc -lgcc_s /usr/lib/gcc/aarch64-redhat-linux/9/crtendS.o > /usr/lib/gcc/aarch64-redhat-linux/9/../../../../lib64/crtn.o -O2 -g > -fstack-protector-strong -grecord-gcc-switches -pthread -Wl,-z -Wl,relro > -Wl,--as-needed -Wl,-z -Wl,now -pthread -Wl,-soname -Wl,libmpi_cxx.so.40 -o > .libs/libmpi_cxx.so.40.20.1 > make[2]: Leaving directory > '/builddir/build/BUILD/openmpi-4.0.2rc1/ompi/mpi/cxx' > BUILDSTDERR: /usr/bin/ld: .libs/mpicxx.o: relocation > R_AARCH64_ADR_PREL_PG_HI21 against symbol `_ZTVN3MPI5GroupE' which may bind > externally can not be used when making a shared object; recompile with -fPIC > BUILDSTDERR: .libs/mpicxx.o: in function `MPI::Group::Group(ompi_group_t*)': > BUILDSTDERR: > /builddir/build/BUILD/openmpi-4.0.2rc1/ompi/mpi/cxx/../../../ompi/mpi/cxx/group.h:62:(.text._ZNK3MPI3Win9Get_groupEv[_ZNK3MPI3Win9Get_groupEv]+0x34): > dangerous relocation: unsupported relocation > BUILDSTDERR: /usr/bin/ld: .libs/mpicxx.o: relocation > R_AARCH64_ADR_PREL_PG_HI21 against symbol `_ZTVN3MPI10ErrhandlerE' which may > bind externally can not be used when making a shared object; recompile with > -fPIC > BUILDSTDERR: .libs/mpicxx.o: in function > `MPI::Errhandler::Errhandler(ompi_errhandler_t*)': > BUILDSTDERR: > /builddir/build/BUILD/openmpi-4.0.2rc1/ompi/mpi/cxx/../../../ompi/mpi/cxx/errhandler.h:30:(.text._ZNK3MPI3Win14Get_errhandlerEv[_ZNK3MPI3Win14Get_errhandlerEv]+0x34): > dangerous relocation: unsupported relocation > > > ___ > 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 ___ 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
Re: [HEADS UP] Retiring python2 and introducing python27 later this week
On 28. 08. 19 19:37, Miro Hrončok wrote: On 27. 08. 19 22:20, Miro Hrončok wrote: We are retiring python2 and introducing python27 later this week. Rawhide only. As for now, nothing should break, except python2-debug will exist no more. Packages (build)requiring python2 or python2-devel should continue to work for now. If not, let us know. If you plan to keep a Python 2 package in Fedora 32+, talk to me, I can help you draft an exception request. Will post a reply here once it is done. python27 build in progress. Will retire python2 later tomorrow or on Friday (in case something is terribly broken I want to have some maneuvering space). I've just retired python2. -- 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
Fedora-Rawhide-20190830.n.0 compose check report
No missing expected images. Compose FAILS proposed Rawhide gating check! 11 of 45 required tests failed, 6 results missing openQA tests matching unsatisfied gating requirements shown with **GATING** below Unsatisfied gating requirements that could not be mapped to openQA tests: FAILED: compose.cloud.all MISSING: fedora.Workstation-boot-iso.x86_64.64bit - compose.install_default MISSING: fedora.Workstation-boot-iso.x86_64.uefi - compose.install_default Failed openQA tests: 31/152 (x86_64), 1/2 (arm) New failures (same test not failed in Fedora-Rawhide-20190829.n.0): ID: 438742 Test: x86_64 KDE-live-iso install_no_user **GATING** URL: https://openqa.fedoraproject.org/tests/438742 ID: 438778 Test: x86_64 universal install_blivet_ext3 URL: https://openqa.fedoraproject.org/tests/438778 Old failures (same test failed in Fedora-Rawhide-20190829.n.0): ID: 438687 Test: x86_64 Server-boot-iso install_default **GATING** URL: https://openqa.fedoraproject.org/tests/438687 ID: 438688 Test: x86_64 Server-boot-iso install_default@uefi **GATING** URL: https://openqa.fedoraproject.org/tests/438688 ID: 438705 Test: x86_64 Server-dvd-iso server_role_deploy_domain_controller **GATING** URL: https://openqa.fedoraproject.org/tests/438705 ID: 438706 Test: x86_64 Server-dvd-iso server_freeipa_replication_master URL: https://openqa.fedoraproject.org/tests/438706 ID: 438707 Test: x86_64 Server-dvd-iso server_freeipa_replication_replica URL: https://openqa.fedoraproject.org/tests/438707 ID: 438708 Test: x86_64 Server-dvd-iso server_realmd_join_kickstart **GATING** URL: https://openqa.fedoraproject.org/tests/438708 ID: 438710 Test: x86_64 Server-dvd-iso realmd_join_sssd **GATING** URL: https://openqa.fedoraproject.org/tests/438710 ID: 438711 Test: x86_64 Server-dvd-iso server_freeipa_replication_client URL: https://openqa.fedoraproject.org/tests/438711 ID: 438716 Test: x86_64 Server-dvd-iso modularity_tests URL: https://openqa.fedoraproject.org/tests/438716 ID: 438720 Test: x86_64 Server-dvd-iso realmd_join_cockpit URL: https://openqa.fedoraproject.org/tests/438720 ID: 438721 Test: x86_64 Everything-boot-iso install_default **GATING** URL: https://openqa.fedoraproject.org/tests/438721 ID: 438722 Test: x86_64 Everything-boot-iso install_default@uefi **GATING** URL: https://openqa.fedoraproject.org/tests/438722 ID: 438724 Test: x86_64 Workstation-live-iso install_default_upload **GATING** URL: https://openqa.fedoraproject.org/tests/438724 ID: 438726 Test: x86_64 Workstation-live-iso install_default@uefi **GATING** URL: https://openqa.fedoraproject.org/tests/438726 ID: 438754 Test: arm Minimal-raw_xz-raw.xz install_arm_image_deployment_upload URL: https://openqa.fedoraproject.org/tests/438754 ID: 438756 Test: x86_64 Silverblue-dvd_ostree-iso install_default_upload URL: https://openqa.fedoraproject.org/tests/438756 ID: 438758 Test: x86_64 Silverblue-dvd_ostree-iso install_default@uefi URL: https://openqa.fedoraproject.org/tests/438758 ID: 438785 Test: x86_64 universal install_european_language URL: https://openqa.fedoraproject.org/tests/438785 ID: 438792 Test: x86_64 universal upgrade_2_desktop_encrypted_64bit URL: https://openqa.fedoraproject.org/tests/438792 ID: 438818 Test: x86_64 universal upgrade_desktop_64bit URL: https://openqa.fedoraproject.org/tests/438818 ID: 438820 Test: x86_64 universal upgrade_server_domain_controller URL: https://openqa.fedoraproject.org/tests/438820 ID: 438821 Test: x86_64 universal upgrade_realmd_client URL: https://openqa.fedoraproject.org/tests/438821 ID: 438823 Test: x86_64 universal upgrade_desktop_encrypted_64bit URL: https://openqa.fedoraproject.org/tests/438823 ID: 438824 Test: x86_64 universal upgrade_2_kde_64bit URL: https://openqa.fedoraproject.org/tests/438824 ID: 438827 Test: x86_64 universal install_cyrillic_language URL: https://openqa.fedoraproject.org/tests/438827 ID: 438828 Test: x86_64 universal install_arabic_language URL: https://openqa.fedoraproject.org/tests/438828 ID: 438829 Test: x86_64 universal install_asian_language URL: https://openqa.fedoraproject.org/tests/438829 ID: 438831 Test: x86_64 universal upgrade_2_minimal_64bit URL: https://openqa.fedoraproject.org/tests/438831 ID: 438832 Test: x86_64 universal upgrade_2_desktop_64bit URL: https://openqa.fedoraproject.org/tests/438832 ID: 438833 Test: x86_64 universal upgrade_2_server_64bit URL: https://openqa.fedoraproject.org/tests/438833 Soft failed openQA tests: 1/152 (x86_64) (Tests completed, but using a workaround for a known bug) Old soft failures (same test soft failed in Fedora-Rawhide-20190829.n.0): ID: 438822 Test: x86_64 universal upgrade_kde_64bit URL: https://openqa.fedoraproject.org/tests/438822 Passed openQA tests: 100/152 (x86_64) New passes (same test not passed in Fedora-Rawhide-20190829.n.0): ID: 438752 Test: x86_64 KDE-live-iso
Re: Fedora Workstation and disabled by default firewall
John Harris wrote: > Thing is, binding a port and expecting it to be open to every network > interface you've got are two very different things. Once again John Harris is completely wrong. The bind system call is precisely how a program specifies which network interfaces it wants to open a socket to. A program that calls bind with IN6ADDR_ANY_INIT or INADDR_ANY and a specific port number expects that port to be open to every network interface the computer has. A program that doesn't intend to listen on every network interface will bind to an IP address assigned to one interface to listen only on that network, or maybe a localhost address to listen only on the loopback interface. The port and the network interface are specified together in a single sockaddr object passed to a single system call, so it's very much the same thing. Björn Persson pgpAOVug6y7hZ.pgp Description: OpenPGP digital signatur ___ 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
[EPEL-devel] Re: perl-LDAP in EPEL 8?
On Fri, Aug 30, 2019 at 12:32:12PM +0200, Maximilian Philipps wrote: > It has now been several months since the release of RHEL 8 and I am > still struggling to get a RHEL 8 into an usable state. Besides the > already mentioned absence of fail2ban and nagios plugins I am now facing > the lack of perl-LDAP. > > In RHEL 7 perl-LDAP was part of the base repo, in RHEL 8 it is > completely missing. According to the epel 8 announcement mail I am > supposed to contact the package maintainer, but from what I have found that > package is always just owned by the project in Fedora/Centos. > > What is required to get that package into epel? File the request in the Bugzilla against "perl-LDAP" component in "Fedora EPEL" product in "Fedora" classification. If the component does not exist there, use a component in "Fedora" product. -- Petr signature.asc Description: PGP signature ___ epel-devel mailing list -- epel-devel@lists.fedoraproject.org To unsubscribe send an email to epel-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/epel-devel@lists.fedoraproject.org
[389-devel] Please review: PRs 50551, 50570, 50573, 50579
Hi team, there are few PRs on review from me. Please, check... https://pagure.io/389-ds-base/pull-request/50551 https://pagure.io/389-ds-base/pull-request/50570 https://pagure.io/389-ds-base/pull-request/50573 https://pagure.io/389-ds-base/pull-request/50579 Thanks, Simon signature.asc Description: PGP signature ___ 389-devel mailing list -- 389-devel@lists.fedoraproject.org To unsubscribe send an email to 389-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/389-devel@lists.fedoraproject.org
Re: Fedora 31 System-Wide Change proposal: Switch RPMs to zstd compression
On Friday, August 30, 2019 8:44:39 AM CEST Miroslav Suchý wrote: > I think that no one contemplate supporting RHEL 7 regarding zstd. Panu said that the backport would be almost trivial: https://lists.pagure.io/archives/list/devel@lists.fedoraproject.org/message/Z4EFFNJNVAP35KH74N3W5GC4E2AQXC7V/ I am not asking for a supported RHEL-7 update of rpm. A working patch would be sufficient for my needs. Kamil ___ 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
Re: Fedora 31 System-Wide Change proposal: Switch RPMs to zstd compression
On Thursday, August 29, 2019 11:17:18 PM CEST Nico Kadel-Garcia wrote: > Sent from my iPhone > > > > On Aug 29, 2019, at 12:58 PM, Kamil Dudka wrote: > > > > > >> On Tuesday, June 4, 2019 9:43:53 AM CEST Panu Matilainen wrote: > >> > >>> On 6/4/19 9:56 AM, Daniel Mach wrote: > >>> > >>> Dne 31. 05. 19 v 2:15 Pavel Raiskup napsal(a): > >>> > >>> > > On Thursday, May 30, 2019 10:38:25 AM CEST Miroslav Suchý wrote: > > > > Dne 29. 05. 19 v 23:52 Josh Boyer napsal(a): > > > > > >> If we did this, wouldn't it make it very difficult to use tools like > >> mock on RHEL / CentOS 7 to build for Fedora 3x? > > > > > > > > > > Speaking of Mock: > > Either the RPM on host need to understand the new format/compression > > **or** > > the packages in @buildsys group (including transitional deps) have to > > > > be in > > old format - then you can build for Fedora 3x using bootstrap > > feature. > > > > > I need to underline this, it would be really really really bad if we > were > not able to --installroot fedora chroots at least on RHEL 8. How > likely > is a backport of zstd support into RPM in EL7+? > >>> > >>> > >>> RHEL 8 should be quite easy - get zstd package into RHEL and recompile > >>> rpm with zstd support. > >>> > >>> RHEL 7 is a different story. The patch doesn't apply directly and a > >>> backport would be needed. > >>> > >>> Panu, > >>> how difficult it would be to backport the zstd support to RHEL 7 RPM? > >> > >> > >> > >> Technically, backporting rpmio backends is almost trivial, even to much > >> older rpm versions. > >> > >> Getting new features into older RHEL is a much bigger problem. > >> > >> > >>- Panu - > > > > > > Has there been any progress on this? > > > > What is the recommended way to build Fedora 31+ RPMs on a RHEL-7 > > > With “mock”, available from EPEL. It does not work because RHEL-7 rpm does not support zstd, so `mock --init` fails with a lot of unsatisfied dependencies on rpmlib(PayloadIsZstd). Kamil ___ 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
[EPEL-devel] perl-LDAP in EPEL 8?
hi, It has now been several months since the release of RHEL 8 and I am still struggling to get a RHEL 8 into an usable state. Besides the already mentioned absence of fail2ban and nagios plugins I am now facing the lack of perl-LDAP. In RHEL 7 perl-LDAP was part of the base repo, in RHEL 8 it is completely missing. According to the epel 8 announcement mail I am supposed to contact the package maintainer, but from what I have found that package is always just owned by the project in Fedora/Centos. What is required to get that package into epel? I feel like it is fairly important for anyone trying to access LDAP through perl. thank you ___ epel-devel mailing list -- epel-devel@lists.fedoraproject.org To unsubscribe send an email to epel-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/epel-devel@lists.fedoraproject.org
Re: No longer supporting mailing lists:
I use the gmail android app and on desktop I use the gmail web interface. On Thu, Aug 29, 2019 at 3:19 PM Przemek Klosowski via devel < devel@lists.fedoraproject.org> wrote: > On 8/27/19 8:36 PM, Gerald B. Cox wrote: > > Regarding NNTP I've haven't used newsreaders in years and to be honest > dealing with yet another tool isn't something I would want to do > > I forgot what email client you use, but all clients I ever used (Emacs > and Thunderbird) also do NNTP. After all, it's just another stream of > messages. > ___ > 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 > ___ 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
Re: [Test-Announce] Fedora 31 Beta Freeze
On Fri, 2019-08-30 at 10:08 +0300, Panu Matilainen wrote: > On 8/29/19 8:30 PM, Kevin Fenzi wrote: > > I'd support changing the freeze dates to be something more like 18:00UTC > > the date they are listed. That would give people more time/be actually > > on the date when people are awake. I'll float the idea to releng and > > then fesco. > > > > That would be awesome. > > It's really annoying to wake up to find a freeze reminder in your inbox > when the freeze already happened. At least, as I also understand 00:00 > to be the first second of a new day. We also hit this at least once with Anaconda in the past as we are basically setting an internal deadline a day before the freez date to avoid any such surprises. Just setting the freeze data on some sane time point would make think clear and we could stop doing that. :) > > - Panu - > ___ > 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 ___ 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
[Bug 1747182] perl-Locale-Codes-3.62 is available
https://bugzilla.redhat.com/show_bug.cgi?id=1747182 --- Comment #4 from Fedora Update System --- FEDORA-2019-3d48221f72 has been submitted as an update to Fedora 29. https://bodhi.fedoraproject.org/updates/FEDORA-2019-3d48221f72 -- You are receiving this mail because: You are on the CC list for the bug. ___ 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
[Bug 1747182] perl-Locale-Codes-3.62 is available
https://bugzilla.redhat.com/show_bug.cgi?id=1747182 --- Comment #3 from Fedora Update System --- FEDORA-2019-79a7e5d478 has been submitted as an update to Fedora 30. https://bodhi.fedoraproject.org/updates/FEDORA-2019-79a7e5d478 -- You are receiving this mail because: You are on the CC list for the bug. ___ 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
Re: [HEADS-UP] snakeyaml 1.25 update
On Thu, Aug 29, 2019 at 11:15 PM Fabio Valentini wrote: > > On Mon, Aug 26, 2019 at 10:36 AM Vít Ondruch wrote: > > > > > > Dne 25. 08. 19 v 14:06 Fabio Valentini napsal(a): > > > Hi everybody, > > > > > > Right now, the snakeyaml package in fedora is out of date by more than > > > three years (1.17, released in February 2016). We plan to merge the PR > > > rebasing it to the latest version (1.25, released this month) into > > > master / rawhide and f31. The new versions include *a lot of bug > > > fixes*, and some minor backwards-incompatible changes. > > > > > > https://src.fedoraproject.org/rpms/snakeyaml/pull-request/3 > > > > > > I ran test rebuilds of dependent packages in a COPR repository, and > > > every package that isn't already broken built successfully, except > > > jruby: > > > > > > https://copr.fedorainfracloud.org/coprs/decathorpe/snakeyaml-pr/monitor/ > > > > > > I checked JRuby upstream vs. the jruby package in fedora, and the > > > version we ship was released in August 2015 (!). I think compatibility > > > with the latest snakeyaml versions should be fixed with 9.2.0.0 and > > > newer, according to the upstream changelog (the versioning jumped from > > > 1.7.x series to "jruby 9000", with 9.x.y.z). > > > > > > If I ran the repoqueries correctly, JRuby is also only required by two > > > packages in fedora, both related to JRuby itself (joni and > > > jruby-maven-plugins). > > > > > > Well, JRuby is Ruby interpreter and in theory can run whatever Ruby code > > available in Fedora. And better integration with other Ruby packages in > > Fedora was always the plan. > > Yeah, that's what I assumed after skimming the Ruby packaging guidelines. > > > However, the problem of JRuby is that it is written in Java and I don't > > have enough expertise, together with different priorities, to properly > > maintain the package. Given this, the situation around java and another > > dependency (properties-maven-plugin) which is currently orphaned, it is > > probably time to orphan/retire the package from Fedora > > According to the snakeyaml changelog, the "minor > backwards-incompatible changes" should be either slightly changed > method signatures or renamed methods. So, *in theory*, it shouldn't be > too difficult to adapt jruby to these changes. > > But I agree - if none of the people who are interested in (j)ruby have > enough Java expertise to fix this, it might really be time to orphan > or eventually retire the package. > I'm sad to say that I don't have the Java skills (nor the time) to > tackle this myself - the Java code I had to write for university > courses didn't prepare me for dealing with this ;) Turns out, it wasn't so difficult after all. https://src.fedoraproject.org/rpms/jruby/pull-request/1 If you think the patch is good, I can merge and build jruby for f31+ and add it to the snakeyaml 1.25 bodhi update for f31. Fabio > Fabio > > > Of course any volunteers who could help are welcome. > > > > > > Vít > > > > > > ___ > > 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 ___ 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
[Bug 1747380] perl-Net-DNS-1.21 is available
https://bugzilla.redhat.com/show_bug.cgi?id=1747380 --- Comment #2 from Upstream Release Monitoring --- the-new-hotness/release-monitoring@fedoraproject.org's scratch build of perl-Net-DNS-1.21-1.fc29.src.rpm for rawhide completed http://koji.fedoraproject.org/koji/taskinfo?taskID=37350660 -- You are receiving this mail because: You are on the CC list for the bug. ___ 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
[Bug 1747380] perl-Net-DNS-1.21 is available
https://bugzilla.redhat.com/show_bug.cgi?id=1747380 --- Comment #1 from Upstream Release Monitoring --- Created attachment 1609816 --> https://bugzilla.redhat.com/attachment.cgi?id=1609816=edit [patch] Update to 1.21 (#1747380) -- You are receiving this mail because: You are on the CC list for the bug. ___ 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
[Bug 1747380] New: perl-Net-DNS-1.21 is available
https://bugzilla.redhat.com/show_bug.cgi?id=1747380 Bug ID: 1747380 Summary: perl-Net-DNS-1.21 is available Product: Fedora Version: rawhide Status: NEW Component: perl-Net-DNS Keywords: FutureFeature, Triaged Assignee: pwout...@redhat.com Reporter: upstream-release-monitor...@fedoraproject.org QA Contact: extras...@fedoraproject.org CC: caillon+fedoraproj...@gmail.com, john.j5l...@gmail.com, ka...@ucw.cz, perl-devel@lists.fedoraproject.org, pwout...@redhat.com, rhug...@redhat.com, rstr...@redhat.com, sandm...@redhat.com Target Milestone: --- Classification: Fedora Latest upstream release: 1.21 Current version/release in rawhide: 1.20-4.fc31 URL: http://search.cpan.org/dist/Net-DNS/ Please consult the package updates policy before you issue an update to a stable branch: https://fedoraproject.org/wiki/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/3147/ -- You are receiving this mail because: You are on the CC list for the bug. ___ 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
[Bug 1747182] perl-Locale-Codes-3.62 is available
https://bugzilla.redhat.com/show_bug.cgi?id=1747182 --- Comment #2 from Fedora Update System --- FEDORA-2019-23e8b01f66 has been submitted as an update to Fedora 31. https://bodhi.fedoraproject.org/updates/FEDORA-2019-23e8b01f66 -- You are receiving this mail because: You are on the CC list for the bug. ___ 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
[Bug 1747182] perl-Locale-Codes-3.62 is available
https://bugzilla.redhat.com/show_bug.cgi?id=1747182 Petr Pisar changed: What|Removed |Added Status|ASSIGNED|MODIFIED Fixed In Version||perl-Locale-Codes-3.62-1.fc ||32 --- Comment #1 from Petr Pisar --- A bug-fix release suitable for all Fedoras. -- You are receiving this mail because: You are on the CC list for the bug. ___ 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
RE: getting below error in fedpkg clone
Hi Jacob, I have added the ssh key in https://admin.fedoraproject.org/accounts Will it take sometime to propagate the keys ? Regards, Muneendra. -Original Message- From: Jakub Jelen [mailto:jje...@redhat.com] Sent: Friday, August 30, 2019 2:18 PM To: Muneendra Kumar M ; Development discussions related to Fedora Subject: Re: getting below error in fedpkg clone On Fri, 2019-08-30 at 14:15 +0530, Muneendra Kumar M wrote: > Hi Jacob, > Iam the packager of the given package(fctxpd). > > And in pkgs.fedoraproject.org I don't find an option to add ssh key as > we have in pagure.io . That is the reason why I pointed you to the Fedora Account page, where you should add your ssh key: https://admin.fedoraproject.org/accounts Regards, Jakub ___ 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
RE: getting below error in fedpkg clone
> Hi Jacob, > Iam the packager of the given package(fctxpd). > > And in pkgs.fedoraproject.org I don't find an option to add ssh key as we > have in pagure.io . You have to add the ssh key to your FAS account. https://admin.fedoraproject.org/accounts/ ___ 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
Re: getting below error in fedpkg clone
On Fri, 2019-08-30 at 14:15 +0530, Muneendra Kumar M wrote: > Hi Jacob, > Iam the packager of the given package(fctxpd). > > And in pkgs.fedoraproject.org I don't find an option to add ssh key > as we > have in pagure.io . That is the reason why I pointed you to the Fedora Account page, where you should add your ssh key: https://admin.fedoraproject.org/accounts Regards, Jakub ___ 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
RE: getting below error in fedpkg clone
Hi Jacob, Iam the packager of the given package(fctxpd). And in pkgs.fedoraproject.org I don't find an option to add ssh key as we have in pagure.io . Regards, Muneendra. -Original Message- From: Jakub Jelen [mailto:jje...@redhat.com] Sent: Friday, August 30, 2019 1:34 PM To: Development discussions related to Fedora Cc: Muneendra Kumar M Subject: Re: getting below error in fedpkg clone On Fri, 2019-08-30 at 12:50 +0530, Muneendra Kumar M via devel wrote: > Hi , > Iam getting the below error when I run fedpkg clone fctxpd > > > fedpkg clone fctxpd > Cloning into 'fctxpd'... > The authenticity of host 'pkgs.fedoraproject.org (209.132.181.4)' > can't be > established. > RSA key fingerprint is > SHA256:Q12OTyTeOHWlS54dTzy2BNu7wB8UKNf18+7WHIDsORc. > Are you sure you want to continue connecting (yes/no/[fingerprint])? > yes > Warning: Permanently added 'pkgs.fedoraproject.org,209.132.181.4' > (RSA) to > the list of known hosts. > muneen...@pkgs.fedoraproject.org: Permission denied (publickey). > fatal: Could not read from remote repository. > > Please make sure you have the correct access rights and the repository > exists. > Could not execute clone: Failed to execute command. > > > I have added the ssh-key at > https://pagure.io/settings#nav-ssh-tab > > But still iam getting the below error. > > Can anyone help me where iam doing the mistake. You need to add keys to your Fedora account [1] since you are using pkgs.fedoraproject.org, unlike the pagure.io, where you added your keys. It takes some time to propagate the keys. Other possibility (if you are not a packager of the given package), is to use anonymous http clone using -a switch: $ fedpkg clone -a fctxpd [1] https://admin.fedoraproject.org/accounts Regards, -- Jakub Jelen Senior Software Engineer Security Technologies Red Hat, Inc. ___ 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
Re: getting below error in fedpkg clone
On 30/08/2019 09:03, Jakub Jelen wrote: Other possibility (if you are not a packager of the given package), is to use anonymous http clone using -a switch: $ fedpkg clone -a fctxpd So long as you are in the packager group you can clone any package without having to use -a you just can't push to it unless you have access to it. Tom -- Tom Hughes (t...@compton.nu) http://compton.nu/ ___ 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
[Bug 1747118] perl-HTTP-Daemon-6.06 is available
https://bugzilla.redhat.com/show_bug.cgi?id=1747118 --- Comment #2 from Fedora Update System --- FEDORA-2019-511f869511 has been submitted as an update to Fedora 31. https://bodhi.fedoraproject.org/updates/FEDORA-2019-511f869511 -- You are receiving this mail because: You are on the CC list for the bug. ___ 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
Re: getting below error in fedpkg clone
On Fri, 2019-08-30 at 12:50 +0530, Muneendra Kumar M via devel wrote: > Hi , > Iam getting the below error when I run fedpkg clone fctxpd > > > fedpkg clone fctxpd > Cloning into 'fctxpd'... > The authenticity of host 'pkgs.fedoraproject.org (209.132.181.4)' > can't be > established. > RSA key fingerprint is > SHA256:Q12OTyTeOHWlS54dTzy2BNu7wB8UKNf18+7WHIDsORc. > Are you sure you want to continue connecting (yes/no/[fingerprint])? > yes > Warning: Permanently added 'pkgs.fedoraproject.org,209.132.181.4' > (RSA) to > the list of known hosts. > muneen...@pkgs.fedoraproject.org: Permission denied (publickey). > fatal: Could not read from remote repository. > > Please make sure you have the correct access rights > and the repository exists. > Could not execute clone: Failed to execute command. > > > I have added the ssh-key at > https://pagure.io/settings#nav-ssh-tab > > But still iam getting the below error. > > Can anyone help me where iam doing the mistake. You need to add keys to your Fedora account [1] since you are using pkgs.fedoraproject.org, unlike the pagure.io, where you added your keys. It takes some time to propagate the keys. Other possibility (if you are not a packager of the given package), is to use anonymous http clone using -a switch: $ fedpkg clone -a fctxpd [1] https://admin.fedoraproject.org/accounts Regards, -- Jakub Jelen Senior Software Engineer Security Technologies Red Hat, Inc. ___ 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
[Bug 1747118] perl-HTTP-Daemon-6.06 is available
https://bugzilla.redhat.com/show_bug.cgi?id=1747118 Petr Pisar changed: What|Removed |Added Status|ASSIGNED|MODIFIED Fixed In Version||perl-HTTP-Daemon-6.06-1.fc3 ||2 --- Comment #1 from Petr Pisar --- A bug-fix release suitable for Fedora ≥ 31. -- You are receiving this mail because: You are on the CC list for the bug. ___ 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
getting below error in fedpkg clone
Hi , Iam getting the below error when I run fedpkg clone fctxpd fedpkg clone fctxpd Cloning into 'fctxpd'... The authenticity of host 'pkgs.fedoraproject.org (209.132.181.4)' can't be established. RSA key fingerprint is SHA256:Q12OTyTeOHWlS54dTzy2BNu7wB8UKNf18+7WHIDsORc. Are you sure you want to continue connecting (yes/no/[fingerprint])? yes Warning: Permanently added 'pkgs.fedoraproject.org,209.132.181.4' (RSA) to the list of known hosts. muneen...@pkgs.fedoraproject.org: Permission denied (publickey). fatal: Could not read from remote repository. Please make sure you have the correct access rights and the repository exists. Could not execute clone: Failed to execute command. I have added the ssh-key at https://pagure.io/settings#nav-ssh-tab But still iam getting the below error. Can anyone help me where iam doing the mistake. Regards, Muneendra. ___ 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
Re: [Test-Announce] Fedora 31 Beta Freeze
On 8/29/19 8:30 PM, Kevin Fenzi wrote: I'd support changing the freeze dates to be something more like 18:00UTC the date they are listed. That would give people more time/be actually on the date when people are awake. I'll float the idea to releng and then fesco. That would be awesome. It's really annoying to wake up to find a freeze reminder in your inbox when the freeze already happened. At least, as I also understand 00:00 to be the first second of a new day. - Panu - ___ 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
Re: Fedora 31 System-Wide Change proposal: Switch RPMs to zstd compression
Dne 29. 08. 19 v 18:58 Kamil Dudka napsal(a): > What is the recommended way to build Fedora 31+ RPMs on a RHEL-7 host? I think that no one contemplate supporting RHEL 7 regarding zstd. The real thing is "how to build Fedora 31+ RPMs on a RHEL-8 host"? https://bugzilla.redhat.com/show_bug.cgi?id=1715799 -- Miroslav Suchy, RHCA Red Hat, Associate Manager ABRT/Copr, #brno, #fedora-buildsys ___ 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
Orphaning and planning to retire my old Java packages
Hello, I've orphaned all my Java packages and my plan is to retire them next week, if no one wants them. There is many of them, but all (except last 2 in the list) were added to the distribution as dependencies of Jenkins package. Thanks, Michal rpms/jenkins rpms/jenkins-antisamy-markup-formatter-plugin rpms/jenkins-ant-plugin rpms/jenkins-commons-jelly rpms/jenkins-credentials-plugin rpms/jenkins-crypto-util rpms/jenkins-executable-war rpms/jenkins-external-monitor-job-plugin rpms/jenkins-extras-memory-monitor rpms/jenkins-icon-shim rpms/jenkins-instance-identity rpms/jenkins-javadoc-plugin rpms/jenkins-jexl rpms/jenkins-junit-plugin rpms/jenkins-ldap-plugin rpms/jenkins-mailer-plugin rpms/jenkins-matrix-auth-plugin rpms/jenkins-matrix-project-plugin rpms/jenkins-pam-auth-plugin rpms/jenkins-remoting rpms/jenkins-script-security-plugin rpms/jenkins-ssh-cli-auth rpms/jenkins-sshd rpms/jenkins-ssh-slaves-plugin rpms/jenkins-task-reactor rpms/jenkins-version-number rpms/jenkins-winstone rpms/jenkins-xstream rpms/jmdns rpms/jruby-maven-plugins rpms/js-CodeMirror rpms/js-yui2 rpms/libpam4j rpms/maven-hpi-plugin rpms/metainf-services rpms/owasp-java-html-sanitizer rpms/robust-http-client rpms/rubygem-jruby-openssl rpms/sezpoz rpms/stapler rpms/stapler-adjunct-timeline rpms/trilead-putty-extension rpms/trilead-ssh2 rpms/localizer rpms/access-modifier-annotation rpms/acegisecurity rpms/akuma rpms/annotation-indexer rpms/bridge-method-injector rpms/bundling-detection-java rpms/bytecode-compatibility-transformer rpms/constant-pool-scanner rpms/groovy-sandbox rpms/jBCrypt rpms/apache-mina rpms/apache-sshd ___ 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
