mp3 encoding now ok
by Christian Schaller
Hi,
So just wanted everyone to know that we now have the go ahead to ship mp3 encoding in Fedora too. So anyone involved with packaging
mp3 encoders can now start migrating them to the Fedora repositories. We are still in the process of evaluating other codecs.
Christian
6 years, 11 months
Wild changes in nsswitch.conf
by Tomas Mraz
My current Fedora 26 default nsswitch.conf contains these lines:
passwd: sss files systemd
shadow: files sss
group: sss files systemd
Not sure which package created this configuration, but:
* Where is the consistency?
* Where is the Fedora Change page that talks about these modifications
of fairly critical systemwide configuration file?
* From which time systemd started to manage user accounts of the
machine, again where is the Fedora Change page for such change?
Regards,
--
Tomas Mraz
No matter how far down the wrong road you've gone, turn back.
Turkish proverb
(You'll never know whether the road is wrong though.)
6 years, 11 months
Introduction of squimrel, a summer of code participant
by squimrel
I'm a nobody who accomplished nothing in life. You may call me squimrel.
As the title suggests I'll write source code this summer. Specifically I'll
work on the [Fedora Media Writer
project](<https://github.com/MartinBriza/MediaWriter/>) which is able to write
live Fedora images on portable media devices.
One (me) should make it possible so that the images on the portable drives have
persistent storage enabled. This will be achieved by modifying two
configuration files and adding another partition for persistent storage.
It's not clear how exactly the program should modify the configuration files on
the live image in which the flags for persistent storage can be set yet.
[There are multiple approaches](<https://medium.com/@squimrel/caeb668848>) and
every single one of them comes with different challenges about which I'll talk
on [my Blog](<https://medium.com/@squimrel>) when I face them.
It's doesn't have to be said that making this work on Windows and Mac comes as
an extra challenge itself.
I'm a bit uncertain how this project will work out but I'm confident that
source code will be written and that I'll learn a lot about accomplishing this
task using C++.
If you wish to know more about me, my "experience", etc. you can read [my
summer coding application at the Fedora Project
Wiki](<https://fedoraproject.org/wiki/GSOC_2017/Student_Application_squimrel>).
squimrel
6 years, 11 months
Finding conflicts in /usr/bin
by Mattia Verga
After a recent bug report I've received [1] I thought to conduct a
survey on all packages available in Fedora to find conflicts between
binary names under /usr/bin but I don't know how exactly do that. Is
there a way to extract the list of all files installed under /usr/bin
from all packages?
I tried with 'dnf repoquery --disablerepo="updates" -l *.x86_64 | grep
"/usr/bin" &> filelist.txt' but it seems to only list files for packages
I've installed on my system.
My suspect is that this survey will result in many packages are using
the same very common binary names.
I would like also to discuss the proposal to have a check in the rpm
build process on filenames that get installed under /usr/bin. This would
prevent these type of conflicts.
Maybe this can be allowed in very special cases with the usage of a mark
in file section, just like we do with %config.
What's your opinion?
Mattia
[1] https://bugzilla.redhat.com/show_bug.cgi?id=1450190
6 years, 11 months
Deprecated net-tools? Mass bug filing?
by James Hogarth
Hi,
It was pointed out on IRC to me tonight that there are actually a
reasonable number of packages that still depend on net-tools[0].
This has been deprecated for a long time now and we really should
strive to have everything use iproute2 instead so that there is no
longer a need to keep the deprecated package about, other than if
someone explicitly really wants netstat or ifconfig for some reason.
Is the best way to handle this a mass bug filing?
If we can at least start cutting down this list in the FC27 cycle I
think it would be a worthy effort.
James
[0] package list:
sudo dnf repoquery --alldeps --whatrequires net-tools
WALinuxAgent-0:2.0.18-2.fc26.noarch
beakerlib-0:1.15-2.fc26.noarch
chkrootkit-0:0.52-1.fc26.x86_64
cloud-init-0:0.7.9-4.fc26.noarch
cloud-init-0:0.7.9-5.fc26.noarch
ctdb-2:4.6.3-0.fc26.x86_64
facter-0:2.4.3-1.fc23.x86_64
gnome-nettool-0:3.8.1-9.fc26.x86_64
inxi-0:2.3.8-2.fc26.noarch
iodine-server-0:0.7.0-7.fc26.x86_64
mariadb-server-3:10.1.21-3.fc26.x86_64
mediatomb-0:0.12.1-40.fc26.20120403gitb66dc1.x86_64
open-vm-tools-0:10.1.5-4.fc26.i686
open-vm-tools-0:10.1.5-4.fc26.x86_64
openslp-server-0:2.0.0-12.fc26.x86_64
openwsman-server-0:2.6.3-2.git4391e5c.fc26.i686
openwsman-server-0:2.6.3-2.git4391e5c.fc26.x86_64
peervpn-0:0.044-1.fc25.x86_64
pki-server-0:10.3.5-12.fc26.noarch
psad-0:2.4.3-4.fc26.x86_64
redhat-lsb-supplemental-0:4.1-34.fc26.x86_64
resource-agents-0:4.0.1-1.fc26.1.x86_64
synce-connector-0:0.15.2-13.fc24.i686
synce-connector-0:0.15.2-13.fc24.x86_64
systemtap-runtime-java-0:3.1-3.fc26.x86_64
testcloud-0:0.1.11-1.fc26.noarch
tunir-0:0.17.1-1.fc26.noarch
tunir-0:0.17.2-1.fc26.noarch
vpnc-script-0:20140805-5.gitdf5808b.fc26.noarch
wicd-common-0:1.7.4-2.fc26.noarch
wifi-radar-0:2.0.s10-4.fc26.noarch
wlassistant-0:0.5.7-25.fc26.x86_64
x2goserver-0:4.0.1.20-2.fc26.x86_64
6 years, 11 months
Unhelpful message about noarch packages differing between arches...
by Richard Shaw
Ok, I was just doing a simple rebuilt of root as OCE was updated to a new
version in rawhide...
The F26 rebuild worked fine but on rawhide I'm getting:
BuildError: The following noarch package built differently on
different architectures: root-doc-6.08.06-4.fc27.noarch.rpm
rpmdiff output was:
error: cannot open Packages index using db5 - Permission denied (13)
error: cannot open Packages database in /var/lib/rpm
error: cannot open Packages database in /var/lib/rpm
removed /usr/share/doc/root/html/pict1_rs701_BayesianCalculator.C.png
removed /usr/share/doc/root/html/pict1_zdemo.py.png
Why would the output be different on rawhide and not other releases?
It would be REALLY helpful if the error message also included which arch
was different...
Thanks,
Richard
https://koji.fedoraproject.org/koji/taskinfo?taskID=19507659
6 years, 11 months
psi4 license change: GPLv2+ -> LGPLv3
by Susi Lehtola
Dear all,
starting from version 1.1 (building in rawhide), the license of psi4 has
been changed from GPLv2+ to LGPLv3.
--
Susi Lehtola
Fedora Project Contributor
jussilehtola(a)fedoraproject.org
6 years, 11 months
libint license change
by Susi Lehtola
Dear all,
starting from version 1.2 (building in rawhide), the license of libint
has been changed from GPLv2+ to LGPLv3.
--
Susi Lehtola
Fedora Project Contributor
jussilehtola(a)fedoraproject.org
6 years, 11 months
Schedule for Thursday's FPC Meeting (2017-05-18 16:00 UTC)
by James Antill
Following is the list of topics that will be discussed in the FPC
meeting Thursday at 2017-05-18 16:00 UTC in #fedora-meeting-1 on
irc.freenode.net.
Local time information (via. rktime):
================= Day: Thursday ==================
2017-05-18 09:00
PDT US/Pacific
2017-05-18 12:00 EDT -->
US/Eastern <--
2017-05-18 16:00 UTC UTC
2017-
05-18 17:00 BST Europe/London
2017-05-18 18:00
CEST Europe/Paris
2017-05-18 18:00 CEST Europe/Berlin
2017-05-18 21:30 IST Asia/Calcutta
---------------- New Day:
Friday -----------------
2017-05-19 00:00 +08 Asia/Singapore
201
7-05-19 00:00 HKT Asia/Hong_Kong
2017-05-19 01:00
JST Asia/Tokyo
2017-05-19 02:00 AEST Australia/Brisbane
Links to all tickets below can be found at:
https://pagure.io/packaging-committee/issues?status=Open&tags=meeting
= New business =
#topic #685 Enforce new naming scheme for Python binary packages
.fpc 685
https://pagure.io/packaging-committee/issue/685
= 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://fedorahosted.org/fpc,
e-mail me directly, or 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.
6 years, 11 months