Hi all,
I'm Kyle Knoepfel, a software developer at Fermi National Accelerator Laboratory. The majority of my projects are C++ based with a little Python mixed in (a few of them can be found at https://github.com/knoepfel).
I've volunteered to maintain the EPEL7 branch of nlohmann_json, which one of our projects relies upon (https://bugzilla.redhat.com/show_bug.cgi?id=1979694).
I'm glad to join your ranks, and thanks upfront for your patience as I get acclimated.
Best regards,
Kyle
Hi,
[1] apache-ivy is only required by ivy-local from javapackages-tools-
6.0.0~alpha-7.fc35.src.rpm
apache-ivy is a FTBFS on rawhide
https://kojipkgs.fedoraproject.org/work/tasks/6387/71866387/build.log
I'd bring back to Fedora fedora-review-plugin-java
Review Request: fedora-review-plugin-java - Java plugin for
FedoraReview https://bugzilla.redhat.com/show_bug.cgi?id=1982370
Review Request: biglybt - Source for BiglyBT, a feature filled, open
source, ad-free, bittorrent client. to replace azureus
https://bugzilla.redhat.com/show_bug.cgi?id=1981982
[1]
dnf repoquery --disablerepo='*' --enablerepo=rawhide --recursive --
whatrequires "mvn(jayasoft:ivy*)" or "mvn(org.apache.ivy*)" or apache-
ivy or apache-ivy
--
Sérgio M. B.
https://fedoraproject.org/wiki/Changes/Enhanced_Inscript_as_default_Indic_IM
== Summary ==
The recommended default input method for Indic languages will be
changed from Inscript to Enhanced Inscript keymaps.
== Owner ==
* Name: [[User:Pnemade| Parag Nemade]]
* Email: <pnemade(a)fedoraproject.org>
== Detailed Description ==
We have enhanced Inscript keyboard layouts available in Fedora. But
they were implemented some time back as draft implementation. We now
want to update them to follow the final released standard keymappings.
It is available as
[https://standardsbis.bsbedge.com/BIS_searchstandard.aspx?Standard_Number=IS…
IS 16350:2016] standard.
{| border="1"
|-
| '''Language''' || ''' Locale code ''' ||'''Existing Input
method''' ||'''New Input method'''
|-
| Assamese || as_IN || as-phonetic.mim || as-inscript2.mim
|-
| Bengali || bn_IN || bn-inscript.mim || bn-inscript2.mim
|-
| Bodo || brx_IN || brx-inscript2-deva.mim || brx-inscript2-deva.mim
|-
| Dogri || doi_IN || doi-inscript2-deva.mim || doi-inscript2-deva.mim
|-
| Gujarati || gu_IN || gu-inscript.mim || gu-inscript2.mim
|-
| Hindi || hi_IN || hi-inscript.mim || hi-inscript2.mim
|-
| Kannada || kn_IN || kn-kgp.mim || kn-inscript2.mim
|-
| Kashmiri || ks_IN@devanagari || ks-inscript.mim || ks-inscript2-deva.mim
|-
| Konkani || kok_IN || kok-inscript2-deva.mim || kok-inscript2-deva.mim
|-
| Maithili || mai_IN || mai-inscript.mim || mai-inscript2.mim
|-
| Malayalam || ml_IN || ml-inscript.mim || ml-inscript2.mim
|-
| Manipuri || mni_IN ||mni-inscript2-beng.mim ||mni-inscript2-beng.mim
|-
| Marathi || mr_IN || mr-inscript.mim || mr-inscript2.mim
|-
| Nepali || ne_NP || ne-rom.mim ||ne-inscript2-deva.mim
|-
| Odia || or_IN || or-inscript.mim || or-inscript2.mim
|-
| Punjabi || pa_IN || pa-inscript.mim || pa-inscript2-guru.mim
|-
| Sanskrit || sa_IN ||sa-harvard-kyoto.mim ||sa-inscript2.mim
|-
| Santhali || sat_IN ||sat-inscript2-deva.mim ||sat-inscript2-deva.mim
|-
| Sindhi || sd_IN@devanagri || sd-inscript.mim || sd-inscript2-deva.mim
|-
| Tamil || ta_IN || ta-typewriter.mim || ta-inscript2.mim
|-
| Telugu || te_IN || te-inscript.mim || te-inscript2.mim
|}
== Benefit to Fedora ==
Users who want to use Enhanced Inscript keymaps will get to use them
which will now use final released implementation of IS 16350:2016
standard.
== Scope ==
* Proposal owners:
Update the final released Enhanced Inscript Keyboard Layouts standard.
This requires to update m17n-db package which uses
https://pagure.io/inscript2 as upstream for these Enhanced Inscript
keymaps. We will also need to update default keymaps for Indic
languages from Inscript to Enhanced Inscript. This will be done in
ibus-m17n package.
* Other developers:
* Release engineering: N/A (not needed for this Change)
* Policies and guidelines: N/A (not needed for this Change)
* Trademark approval: N/A (not needed for this Change)
== Upgrade/compatibility impact ==
Users will be moved from Inscript keymaps to Enhanced Inscript
keymaps. Both are compatible to each other except some keymappings
changed for Normal characters as well as Shifted Characters and 3rd
layer (using AltGr) is added to type extra characters.
== How To Test ==
We already have Enhanced Inscript keymaps in Fedora but their
implementation is following draft released standard by Government.
With this Change users can test final released standard keymaps.
They can still use the same testcase
https://fedoraproject.org/wiki/QA:Inscript2_Keymaps
== User Experience ==
* Users will type characters as per final released Enhanced Inscript
standard keymaps.
== Dependencies ==
m17n-db and ibus-m17n packages will be updated
== Contingency Plan ==
Revert to older Inscript keymaps.
== Documentation ==
We will add some information about this in Release notes.
--
Ben Cotton
He / Him / His
Fedora Program Manager
Red Hat
TZ=America/Indiana/Indianapolis
Hi,
I'm announcing the soname bump of the *libpcre2-posix.so *library (pcre2
package) happening this Wednesday.
Library has some ABI changes which lead to this bump (you can read more
about it here <https://www.pcre.org/changelog.txt> under 10.37 version).
We are including the old soname library to prevent some running errors for
the dependencies. After rebuilding all of the packages, we will remove it
from the pcre2 package.
This change impact several packages listed below:
carbon-c-relay-3.7.2-1.fc35.src.rpm
haproxy-2.4.0-5.fc35.src.rpm
mariadb-10.5.11-1.fc35.src.rpm
metis-5.1.0-29.fc34.src.rpm
pcre2-10.36-4.fc35.src.rpm
util-linux-2.37-2.fc35.src.rpm
xterm-368-1.fc35.src.rpm
I'm CCing all the main maintainers of these packages to give them heads-up.
We're planning the rebuild on the 14th of July 2021 (07.14.2021), so if you
have any questions or reasons why not to do that, please let me know ASAP.
The actual rebase PR is here:
https://src.fedoraproject.org/rpms/pcre2/pull-request/2#
<https://src.fedoraproject.org/rpms/pcre2/pull-request/2#>
Thanks and have a great day
Lukas
--
S pozdravom/ Best regards
Lukáš Javorský
Associate Software Engineer, Core service - Databases
Red Hat <https://www.redhat.com>
Purkyňova 115 (TPB-C)
612 00 Brno - Královo Pole
ljavorsk(a)redhat.com
<https://www.redhat.com>
Hi folks!
As everyone may remember, last year our annual contributor conference Flock
to Fedora was moved to a virtual event, Nest with Fedora. *Please join us
for the second edition of Nest with Fedora, August 5th-7th.* We are excited
to see all of the familiar (and new!) faces and to catch up on what
everybody has been up to in Fedora.
The *Call for Proposals has been extended until July 23rd*, and we are
looking forward to great submissions from the Fedora community. Submissions
can range by type of session, topic, and presenters of all skill levels
should feel encouraged to submit.
*CfP open here: *
https://pagure.io/flock/issues
*Registration open here: *
https://hopin.com/events/nest-with-fedora-2021
*For more information see:*
https://communityblog.fedoraproject.org/update-nest-with-fedora-cfp-registr…
Cheers!
--
Marie Nordin
Fedora Community Action and Impact Coordinator
Red Hat <https://www.redhat.com/> • Fedora Project <https://getfedora.org/>
She/Her/Hers
T: +1.973.800.4967
IRC: riecatnor
<https://red.ht/sig>
FYI - I think this is worth a copy to Fedora devel.
Miroslav
-------- Přeposlaná zpráva --------
Předmět: Architecture "ppc64le" again in Fedora Copr
Datum: Wed, 14 Jul 2021 16:25:46 +0200
Od: Pavel Raiskup <praiskup(a)redhat.com>
Adresa pro odpověď: Discussion of Fedora build system <buildsys(a)lists.fedoraproject.org>
Společnost: Red Hat, Inc.
Komu: copr-devel(a)lists.fedorahosted.org
Kopie: Discussion of Fedora build system <buildsys(a)lists.fedoraproject.org>
Hi all,
I'm glad I can announce that we have again (native) support for ppc64le builds
in Fedora Copr. Currently we have two Power8 boxes (in RDU):
https://pagure.io/fedora-infrastructure/issue/9059
The ppc64le chroots were re-enabled, feel free to use them. I noticed several
build failures caused by missing repodata in ppc64le chroots, please re-generate
the repodata manually if you happen to see those problems.
Happy building!
Pavel
Following is the list of topics that will be discussed in the FPC
meeting Thursday at 2021-07-15 16:00 UTC in #fedora-meeting-1 on
irc.libera.chat.
Local time information (via. uitime):
================= Day: Thursday ==================
2021-07-15 09:00 PDT US/Pacific
2021-07-15 12:00 EDT --> US/Eastern <--
2021-07-15 16:00 UTC UTC
2021-07-15 17:00 BST Europe/London
2021-07-15 18:00 CEST Europe/Berlin
2021-07-15 18:00 CEST Europe/Paris
2021-07-15 21:30 IST Asia/Calcutta
---------------- New Day: Friday -----------------
2021-07-16 00:00 HKT Asia/Hong_Kong
2021-07-16 00:00 +08 Asia/Singapore
2021-07-16 01:00 JST Asia/Tokyo
2021-07-16 02:00 AEST Australia/Brisbane
Links to all tickets below can be found at:
https://pagure.io/packaging-committee/issues?status=Open&tags=meeting
= Followup Actions =
#topic #pr-814
* mhroncok
talk to authors again, having a working example might help a lot
= Followup Issues =
#topic #886 Enable BRP for detecting RPATH
.fpc 886
https://pagure.io/packaging-committee/issue/886
#topic #907 Which %__foo macros for executables are acceptable?
.fpc 907
https://pagure.io/packaging-committee/issue/907
#topic #1058 How to handle %lang files in package owned directories? .fpc 1058
https://pagure.io/packaging-committee/issue/1058
= Followup Pull Requests =
#topic #pr-814 Add SELinux Independent Policy Guidelines.
https://pagure.io/packaging-committee/pull-request/814
#topic #pr-1045 WIP: Add discussion of macro names beginning with underscores.
https://pagure.io/packaging-committee/pull-request/1045
#topic #pr-1071 Overhaul the RPATH section of the guidelines.
https://pagure.io/packaging-committee/pull-request/1071
#topic #pr-1072 Python Packaging Guidelines overhaul
https://pagure.io/packaging-committee/pull-request/1072
= Open Floor =
For more complete details, please visit each individual ticket. The
report of the agenda items can be found at:
https://pagure.io/packaging-committee/issues?status=Open&tags=meeting
If you would like to add something to this agenda, you can:
* Reply to this e-mail
* File a new ticket at: https://pagure.io/packaging-committee
* E-mail me directly
* Bring it up at the end of the meeting, during the open floor topic. Note
that added topics may be deferred until the following meeting.