https://fedoraproject.org/wiki/Changes/RemoveNSCD
== Summary ==
This proposal intends to replace the ''nscd'' cache for named services
with ''systemd-resolved'' for the `hosts` database and the ''sssd''
daemon for everything else.
== Owner ==
* Name: [[User:submachine| Arjun Shankar]]
* Email: arjun(a)redhat.com
== Detailed Description ==
''nscd'' is a daemon that provides caching for accesses of the
`passwd`, `group`, `hosts`, `services`, and `netgroup` databases
through standard libc interfaces (such as `getpwnam`, `getpwuid`,
`getgrnam`, `getgrgid`, `gethostbyname`, etc.). This proposal intends
to replace ''nscd'' in Fedora with ''systemd-resolved'' for the
`hosts` database and the ''sssd'' daemon for everything else.
Accordingly, the `nscd` sub-package of glibc will be removed and
obsoleted.
== Benefit to Fedora ==
While still maintained within the glibc source tree, ''nscd'' has
received less than forty commits in the past three years and has
gathered significant technical debt, and has bugs which are hard to
fix. There are concurrency bugs in the shared mappings, cache
unification (IPv4 vs. IPv6 vs. AF_UNSPEC) issues, and more which would
require significant investment to fix in nscd. Such an investment
seems like duplicate effort among our communities given the quality
and state of ''sssd'', and ''systemd-resolved'' which is already
proposed to be enabled by default from [[Changes/systemd-resolved |
Fedora 33 onwards]].
At a high level, sssd and systemd-resolved together provide a caching
solution that has feature parity with nscd, with systemd-resolved
covering the hosts cache and sssd the rest. The removal of nscd from
Fedora will:
* move the user base over to a more modern solution for named services
caching, and
* reduce maintenance work on the Fedora glibc package and the
duplication of effort on nscd upstream.
== Scope ==
* Proposal owners:
The volume of work required is minimal, with the only change being the
removal and obsolescence of the nscd sub-package offered by glibc
which can be achieved by minor changes to the spec file. Since nscd is
not installed by default, the affect on the distribution is minimal.
Users who have installed nscd in an earlier release of Fedora will
need to install and configure sssd instead.
* Other developers: `nss-pam-ldapd` has a weak dependency on nscd that
will need to be removed. `libuser` has a build dependency on nscd that
will also need to be removed.
* Release engineering:
This change does not require coordination with or have impact on
release engineering and does not require a mass rebuild.
* Policies and guidelines: N/A (not a System Wide Change)
* Trademark approval: N/A (not needed for this Change)
* Alignment with Objectives: Yes, this proposal aligns with the
[https://docs.fedoraproject.org/en-US/project/objectives current
objective] of "Fedora Minimization".
== Upgrade/compatibility impact ==
N/A (not a System Wide Change)
== User Experience ==
* Most users will be unaffected by this change because nscd is not
installed by default. It is usually used on systems configured with
LDAP, where nscd provides caching of remote queries.
* On a system using nscd that is updated to Fedora 34 from a previous
version, the system administrator will need to install and configure
sssd to replace it after the update. Even when this is not done, the
only visible affect will be slower resolution of named service queries
due to a missing cache.
* Users on a system running sssd and systemd-resolved instead of nscd
shouldn't see any noticeable difference in system behaviour or latency
in resolving named services.
== Dependencies ==
* `nss-pam-ldapd` has a weak dependency on nscd that will need to be removed.
* `libuser` has a build dependency on nscd that will also need to be removed.
Both changes are minimal, requiring a removal of the dependency in the
spec file, and a rebuild.
== Contingency Plan ==
* Contingency mechanism: Revert changes to glibc spec file and
continue to ship nscd. Revert changes to libuser and nss-pam-ldapd
packages; this will need to be done by the respective package
maintainers.
* Contingency deadline: Fedora 34 Beta Freeze
* Blocks release? N/A (not a System Wide Change)
* Blocks product? None
== Documentation ==
N/A (not a System Wide Change)
--
Ben Cotton
He / Him / His
Senior Program Manager, Fedora & CentOS Stream
Red Hat
TZ=America/Indiana/Indianapolis
We are working on dropping Python 2 version of Mercurial in Fedora[0] entirely.
Currently there is a working version of Mercurial 5.6 in COPR[1] that
needs further testing. If anyone who uses Mercurial would be able to
test it and give me some feedback, I would be glad!
Also there is a question if we should make the change in F34 or in
"older" F33. Is it worth it to push this into F33?
Best regards,
Ondřej Pohořelský
[0]https://src.fedoraproject.org/rpms/mercurial/pull-request/13
[1]https://copr.fedorainfracloud.org/coprs/opohorel/mercurial/
[I posted to the Fedora Council list, but reposting here for wider
distribution.]
As mentioned, we're looking at moving the Fedora Council's main chat to
Matrix. And as part of that, we're considering a hosted Element server --
which obviously could go quite beyond just #fedora-council. Neal suggested a
video meeting to talk with interested people about this, and so I set up
this when-is-good
http://whenisgood.net/k5brwbd
Anyone interested in a preliminary chat about all of this, please sign up
with your FAS id and availability. Nothing is sent in stone or decided
already, although I must say I'm pretty excited about Element's open source
software-as-a-service offering based on what I've heard from them so far.
--
Matthew Miller
<mattdm(a)fedoraproject.org>
Fedora Project Leader
Hello. I want to buy myself Dell XPS 13 9310 (2020). The unit will arrive in few weeks, so I used the time to ask this questio. It has a fingerprint sensor Goodix 27c6:533c. But official driver is for Ubuntu and no RPM. There is a post how to install it, but replacing packages' files is very likely to break after update.
Post link: https://aboutcher.co.uk/2020/10/goodix-fingerprint-reader-on-fedora-linux/
It is absolutely unecessary to do write to modules.alias, I think.
That Ubuntu package has a TOD library, which enables to use OEM drivers but there is no TOD for fedora. It would be nice to do TOD libfprint package, which provides libfprint (so no ugly replacements which will disappear after update) and that driver package or make it one package.
If it can be possible, can someone please make good, quality and nice RPM(s), which I have to install and and "at the drop of the hat" run into GNOME Settings and setup fingerprint? It will help me and many XPS 13 users, because according to reviews, this computer is very good for running Linux (not that one I have, which is Ok, but not very good).
Thank you!
# Fedora Quality Assurance Meeting
# Date: 2020-11-30
# Time: 16:00 UTC
(https://fedoraproject.org/wiki/Infrastructure/UTCHowto)
# Location: #fedora-meeting on irc.freenode.net
Greetings testers!
We didn't meet for a few weeks, and this is the last slot before lots
of folks will be away over December, so let's have a meeting tomorrow.
Sorry for the short notice, I forgot to send this out Friday night.
I recall telling someone I'd put something on the agenda for this
meeting, but I can't remember who or what it was. Please, if you
remember, let me know and we'll work it in. Sorry about that!
If anyone has any other items for the agenda, please reply to this
email and suggest them! Thanks.
== Proposed Agenda Topics ==
1. Previous meeting follow-up
2. Fedora 34 status and Changes
3. IRC vs. Matrix?
4. Test Day / community event status
5. Open floor
--
Adam Williamson
Fedora QA
IRC: adamw | Twitter: adamw_ha
https://www.happyassassin.net
_______________________________________________
test-announce mailing list -- test-announce(a)lists.fedoraproject.org
To unsubscribe send an email to test-announce-leave(a)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-announce@lists.fedorapro…
There seems to be a fairly major bug in the new systemd release that
recently landed in Rawhide which commonly causes systemd - that is, PID
1 - to segfault on system shutdown or reboot. Several openQA tests are
hitting this. I have filed
https://bugzilla.redhat.com/show_bug.cgi?id=1902819 and been advised
this is likely upstream issue
https://github.com/systemd/systemd/issues/17768 . It's probably a good
idea to avoid updating to 247-1.fc34, if you haven't already, until
this is sorted out.
--
Adam Williamson
Fedora QA
IRC: adamw | Twitter: adamw_ha
https://www.happyassassin.net
Hi guys,
not sure whether I missed something, but I have realized troubles
with building for the armhfp arch. The build process crash on
installation of requirements because of inssuficient space:
https://download.copr.fedorainfracloud.org/results/opohorel/mercurial/fedor…
I am going to skip that arch for now in building. But sharing just in case
someone has the same issue.
Cheers,
--
Petr Stodulka
OS & Application Modernization
IRC nicks: pstodulk, skytak
Senior Software Engineer
Red Hat Czech s.r.o.
KiCAD has a large package containing 3D component models. It takes a long time to compress with the new zstd compressor. So long in fact that the copr build system is throwing a timeout. You can see an example here:
https://download.copr.fedorainfracloud.org/results/@kicad/kicad/fedora-33-x…
Here is the text at the end of the above log - basically it times out when compressing the 3D models into the RPM file:
...
Wrote: /builddir/build/RPMS/kicad-debuginfo-r23934-fc2bdc49.fc33.x86_64.rpm
Wrote: /builddir/build/RPMS/kicad-r23934-fc2bdc49.fc33.x86_64.rpm
Wrote: /builddir/build/RPMS/kicad-doc-r23934-fc2bdc49.fc33.noarch.rpm
Wrote: /builddir/build/RPMS/kicad-debugsource-r23934-fc2bdc49.fc33.x86_64.rpm
!! Copr timeout => sending INT
Copr build error: Build failed
The package is named kicad-packages3d. Compressed size is around 390 Mbytes and decompressed it is about 5.5 Gbytes. So far, only F33 is throwing the timeout; other targets are successfully building the package. But I have no idea how close to a similar problem those other targets may be.
Is there a way to increase the Copr builder timeout?
Alternatively, I could perhaps tell Copr not to use zstd for the 3D models, but I'd hate to do that, given how large the resulting RPM would be. On my desktop I do use:
--rpmbuild-opts='--define=_binary_payload\ w3.zstdio'
to bypass the compression and expedite my testing.
Steve