I am working on implementing a piece of code that allows BOINC client
 to detect the desktop environment used by the user (mainly GNOME,
KDE Plasma, XFCE, LXDE/LXQT).
This feature will be needed for various reason that are off topic.
One idea is to use GDBus to scan DBus to detect the running d.e.
What do you think about?
I'm investigating whether it makes sense to switch to a scheme where the
glibc locale data is built from source, during package installation,
based on the langpack configuration system. This is similar to what
The reason is that the compressed locale source code (without the
charmaps, which are not strictly needed once we patch localedef) is
smaller than the subset of locales of a langpack package which people
actually. For example, glibc-langpack-en on Fedora 29 is 6.7 MiB when
installed, but en_US.utf8 is 2.9 MiB, and the locale sources are
3.4 MiB, so even the common case realizes a small saving.
For the installer, the savings might be much larger. If we can teach
anaconda to generate the appropriate locale only after the user has
selected the language, then we no longer need the full locale archive in
the installation image (and in RAM).
I'd like to appologize for the delay in this email.
The notices I get were being filtered and I didn't realize I wasn't
seeing them for a while. ;(
We've been told that the email addresses for these package maintainers
are no longer valid. I'm starting the unresponsive maintainer policy to
find out if they are still interested in maintaining their packages (and
if so, have them update their email addresses in FAS).
If they're not interested in maintaining or we can't locate them in 1
week, I'll have FESCo orphan the packages so that others can take them
If you have a way to contact these maintainers, please let them know
that we'd appreciate knowing what to do with their packages. Thanks!
Hey. pep8 is no longer released upstream and its successor is called pycodestyle.
I plan to retire python-pep8, as tracked in , however there are still too
many consumers of python3-pep8. On the other hand, python2-pep8 is only
cachedir - already FTBFS, not dependent upon
genbackupdata - already FTBFS, fails to install, not dependent upon
ovirt-guest-agent - already FTBFS, not dependent upon outside of subpackages
pylast - python2-pylast is not dependent upon
python-cliapp - python2-cliapp is required by:
cmdtest - FTBFS, fails to install, required by:
python-larch - FTBFS, not dependent upon outside of subpackages
Maintainers by package:
ovirt-guest-agent evilissimo nyoxi
Packages by maintainer:
salimma cmdtest genbackupdata python-cliapp python-larch
Would you like to take python2-pep8? I'd advice against, please update to Python
3 and/or pycodestyle instead.
This is my attempt to follow .
I have a bunch of packages in a local repo built for various versions
of Fedora and CentOS, and am looking to build some of them for EL-8.
Clearly the way to go for an EL-8 add-on repo is to build modules, so
that it what I'd like to do. However, I want to do it on my own
infrastructure and hence use the lower-level tooling such as
mbs-manager/mock and local git repos rather than fedpkg/koji/dist-git.
There's quite a bit of documentation around about building modules but
what I've found seems to be either out of date (e.g. uses "mbs-build",
which no longer exists) or is based on fedpkg, which abstracts away the
lower-level operation and is geared towards Fedora infrastructure.
Is there some documentation somewhere that covers getting started with
the tools like mbs-manager?
I thought this workshop looked like a good starting point:
When I discovered that "mbs-build" no longer exists, I tried using
"mbs-manager" but clearly I'm missing something:
$ mbs-manager build_module_locally --file test-module.yaml -s platform:f30
2019-05-30 09:51:04,712 - MainThread - urllib3.util.retry - DEBUG - Converted retries value: 3 -> Retry(total=3, connect=None, read=None, redirect=None, status=None)
2019-05-30 09:51:04,863 - MainThread - moksha.hub - WARNING - Cannot find qpid python module. Make sure you have python-qpid installed.
2019-05-30 09:51:05,577 - MainThread - MBS.utils.submit - DEBUG - Submitted normal module build for test-module:f30:20190530085105
Traceback (most recent call last):
File "/usr/bin/mbs-manager", line 11, in <module>
load_entry_point('module-build-service==2.19.1', 'console_scripts', 'mbs-manager')()
File "/usr/lib/python3.7/site-packages/module_build_service/manage.py", line 251, in manager_wrapper
File "/usr/lib/python3.7/site-packages/flask_script/__init__.py", line 417, in run
result = self.handle(argv, argv[1:])
File "/usr/lib/python3.7/site-packages/flask_script/__init__.py", line 386, in handle
res = handle(*args, **config)
File "/usr/lib/python3.7/site-packages/flask_script/commands.py", line 216, in __call__
return self.run(*args, **kwargs)
File "/usr/lib/python3.7/site-packages/module_build_service/manage.py", line 167, in build_module_locally
username, handle, params, stream=str(stream), skiptests=skiptests)
File "/usr/lib/python3.7/site-packages/module_build_service/utils/submit.py", line 503, in submit_module_build_from_yaml
return submit_module_build(username, mmd, params)
File "/usr/lib/python3.7/site-packages/module_build_service/utils/submit.py", line 633, in submit_module_build
mmds = generate_expanded_mmds(db.session, mmd, raise_if_stream_ambigous, default_streams)
File "/usr/lib/python3.7/site-packages/module_build_service/utils/mse.py", line 417, in generate_expanded_mmds
current_mmd = Modulemd.Module.new_from_string(mmd.dumps())
TypeError: <flask_script.commands.Command object at 0x7f89f21409e8>:
Argument 0 does not allow None as a value
Any pointers anyone?
I'd like to announce a Fedora Special Interest Group dedicated to the
topics of Continuous Integration, Continuous Delivery, Gating and
I've created a wiki page with the initial data:
Please join, add yourself to member list, bring your ideas and work items.
I'd like to also setup a bi-weekly IRC meeting, so please think about what
time would work best for you. Let's have a separate discussion on that next
Feedback is welcome.
Quote from the wiki:
== Goal ==
The goal of the SIG is to bring together CI enthusiasts interested in
developing tools, best practices, standards, and workflows to implement
Continuous Integration at a larger scale.
While CI is well-known and used by many software projects, it is usually
applied at an individual component level. Scaling it up is a challenge from
both technical and organizational points of view. Here in Fedora, we have
an opportunity to explore and develop the CI/CD topic beyond simple
== Topics ==
* CI for Fedora
* Containerized CI
* CI on bare-metal
* Gating at scale
* Packaging and CI
* CI and Upstream
* CI engines, Artifact storages, Test analytics
== Benefit to Fedora ==
CI is rarely associated with packaged Linux distributions even though it is
nowadays used in most of them. We’d like to change this perception, to show
that packaging and CI can and should be used together.
We also would like to establish Fedora as a perfect CI platform.
Virtualization, containerization and many other tools available in Fedora
provide a good foundation to build flexible, open and modern CI solutions
and CI architectures on top of it. Let's make use of them.
bookwar on IRC
I'm co-maintaining a C++ library that has been continuously updated in
CentOS 7 but a recent change made it incompatible with the default GCC
version available in el7. I.e. the next release (scheduled for the end
of 2019) will FTBFS in CentOS/RHEL 7.
Would it be fine to require a gcc version from a SCL to build this
library? I'm afraid that due to the nature of C++'s non-standardized ABI
it would require all dependent packages to be rebuild with gcc from the
I created a LiveCD for my own personal use (with openbox) in Fedora 30. I have created such a live cd for the past several cycles (I think
In the past, I have the SLiM (slim) screen show up with username (that I say is liveuser) and does not prompt me for a password. However, in Fedora 30, I am prompted for password from the created LiveCD. So I can not get in.
Here are the lines in my kickstart file:
# Show harddisk install on the desktop
sed -i -e 's/NoDisplay=true/NoDisplay=false/' /usr/share/applications/liveinst.desktop
cp /usr/share/applications/liveinst.desktop /home/liveuser/Desktop
# this goes at the end after all other changes.
chown -R liveuser:liveuser /home/liveuser
restorecon -R /home/liveuser
So, I was wondering what to do in this case, or at the very least, try and provide a password for the livecd which can be used to login.
Thanks for any suggestions!