This seems to repeat every 6 months: rawhide mock is broken on stable
Fedora, people are scrambling to install the right gpg keys, dnf reports
unsigned packages.
Looking at https://bodhi.fedoraproject.org/updates/?packages=fedora-repos,
there is still no F30 package with the right keys.
Can we *please* send out the FN+1 and FN+2 keys a month before branching,
to *all* releases of Fedora, so we can avoid this pointless scramble?
Zbyszek
Too many people (like also me) try to use samba-dc on fedora for deploy
a production AD DC controller, without know that MIT kerberos is
experimental and some useful things cannot work (es. win to win
access).
An recent last example:
https://lists.samba.org/archive/samba/2019-November/226845.html
> On 01/11/2019 22:23, Vex Mage wrote:
> > The script is expecting dpkg however this is a Red Hat
> > derived distro (Fedora Server.)
>
> Where did you get the Samba packages from ?
>
> If they are the default OS packages, then you should stop using
> them, they use MIT kerberos and are experimental.
There is many approach for resolve this issue:
a) Stop use MIT kerberos and rebuild samba with Heimdal Kerberos.
b) Produce a samba alternative package version (like, for example,
firefox-x11) build it with Heimdal Kerberos (es samba-hk-*)
c) Stop enable DC on Fedora, like RH/Centos do.
d) Notify users at the end of the installation that Fedora Samba DC is
experimental.
e) Solve the problems that make MIT kerberos experimental and put us in
a position to ask for help on the samba team.
f) ... some other proposal ?
What is the best approach chosen by Fedora ?
Many thanks
--
Dario Lesca
(inviato dal mio Linux Fedora 31 Workstation)
Il giorno gio 24 ott 2019 alle ore 19:28 Strahil <hunter86_bg(a)yahoo.com> ha
scritto:
> Hi Sandro,All,
>
> Can I upgrade the tools on existing VM , or it requires a fresh one? Best
> Regards
>
If you have oVirt windows guest tools already installed suggestion is to
uninstall it before installing this new installer.
> Best Regards,
> Strahil Nikolov
> On Oct 24, 2019 14:35, Sandro Bonazzola <sbonazzo(a)redhat.com> wrote:
>
> Hi,
> as part of the work on oVirt 4.4, the team rewrote the VirtiIO Windows
> Drivers installer using the open source framework WiX.
> Thanks to the virtio-win maintainer, the new installer is not shipped
> anymore within oVirt Guest Tools ISO: it's shipped now directly into VirtIO
> Windows ISO[1]
>
> Please give it a run on your testing environment / testing VMs and let us
> know about your experience at devel(a)ovirt.org.
> Thanks,
>
>
> [1]
> https://fedorapeople.org/groups/virt/virtio-win/direct-downloads/archive-vi…
>
> --
>
> Sandro Bonazzola
>
> MANAGER, SOFTWARE ENGINEERING, EMEA R&D RHV
>
> Red Hat EMEA <https://www.redhat.com/>
>
> sbonazzo(a)redhat.com
> <https://www.redhat.com/>*Red Hat respects your work life balance.
> Therefore there is no need to answer this email out of your office hours.*
>
>
--
Sandro Bonazzola
MANAGER, SOFTWARE ENGINEERING, EMEA R&D RHV
Red Hat EMEA <https://www.redhat.com/>
sbonazzo(a)redhat.com
<https://www.redhat.com/>*Red Hat respects your work life balance.
Therefore there is no need to answer this email out of your office hours.
<https://mojo.redhat.com/docs/DOC-1199578>*
Hello devel,
I got nerdslipped and I ahve created some HTML only mockup of a thing that I
find very useful. A Fedora Packager Dashboard.
You can find the early mockup at:
https://hroncok.cz/packager-dashboard-mockup/
The idea is to collect some data about your packages and present them in some
nice form. Such data would be gathered by plugins. Examples on the mockup:
- active updates
- active buildroot overrides
- open PRs
- orphaned or broken depnddencies
- bugzillas
- FTBFS (from koschei)
Ideas not included in the mockup:
- running Koji builds
Let me know what you think. I can work on this on the backend level (plugin
architecture design, gathering data, cache...) but even copy pasting HTML from
Bodhi to present the mockup was very painful for me, so if we want this,
somebody with more fronted experience would need to help.
--
Miro Hrončok
--
Phone: +420777974800
IRC: mhroncok
Hello,
my name is Philip Matura and I'm currently a student in mathematics. In
my freetime I'm doing audio/music and electronics stuff. I've been
converted to the Linux world with Fedora about 10 years ago and would
like to give some things back.
So there are currently four packages I would like to see included in
Fedora eventually, to which I would lend a hand in order to make that
happen. Three of them already were submitted in the past, but didn't
make it through (yet):
aelous (https://bugzilla.redhat.com/show_bug.cgi?id=789390)
drumgizmo (https://bugzilla.redhat.com/show_bug.cgi?id=1210356)
helm (https://bugzilla.redhat.com/show_bug.cgi?id=1661657)
But for now I'll start with this one:
zita-njbridge (https://bugzilla.redhat.com/show_bug.cgi?id=1780297)
So I am looking for a sponsor.
Greetings,
Philip
GPG: 44300632B5E49E6A81528B9EE0538557D42A4B04
https://fedoraproject.org/wiki/Changes/Use-Update-Alternatives-For-usr-bin-…
== Summary ==
Modify the gcc package so that the /usr/bin/cc and /usr/bin/c++
symlinks are managed by update-alternatives.
== Owner ==
* Name: [[User:tstellar| Tom Stellard]]
* Email: <tstellar(a)redhat.com>
== Detailed Description ==
The gcc package currently installs symlinks to /usr/bin/cc and
/usr/bin/c++ which point to /usr/bin/gcc and /usr/bin/g++
respectively. For this change, the gcc package will be modified so
that update-alternatives creates and manages these symlinks.
In addition to modifying the gcc package, the clang package will be
modified so that /usr/bin/clang and /usr/bin/clang++ can be used as
alternatives for /usr/bin/cc and /usr/bin/c++. The clang alternatives
will have a lower priority than the gcc alternatives, so that by
default, gcc will provide the /usr/bin/cc and /usr/bin/c++
implementations.
The clang package currently has a run-time dependency on gcc, so this
ensures that gcc will always provide the default implementation,
because it's impossible to install clang without gcc.
The only way users will be able to change the /usr/bin/cc or
/usr/bin/c++ implementations will be by explicitly using the
update-alternatives tool.
== Benefit to Fedora ==
Many build systems default to using /usr/bin/cc and /usr/bin/c++ as
the default C/C++ compilers. Being able to easily swap out these
implementation will provide a lot of flexibility within Fedora for
doing things like:
* Setting up alternative buildroots for testing.
* Installing a gcc wrapper script to /usr/bin/cc to help migrate
packages to new compiler flags or to capture statistics about compiler
usage.
* Letting users experiment easily with alternate compilers.
* Easily switch between system gcc and a development version of gcc.
== Scope ==
* Proposal owners: The proposal owner will implement the necessary
changes in the gcc and clang packages.
* Other developers: The gcc maintainers will be responsible for
reviewing and approving changes to the gcc package.
* Release engineering: (a check of an impact with Release Engineering is needed)
* Policies and guidelines: No policies or guidelines will need to be
updated as a result of this change.
* Trademark approval: N/A (not needed for this Change)
== Upgrade/compatibility impact ==
This change should not impact upgradeability.
== How To Test ==
CI tests will be added to the gcc package to ensure that /usr/bin/cc
and /usr/bin/c++ still point to /usr/bin/gcc and /usr/bin/g++ when
installed. There will also be a CI test added to the clang package to
ensure that /usr/bin/gcc and /usr/bin/g++ remain the default when
clang is installed.
== User Experience ==
This change will give users a much better way to experiment using
other compilers for their own development. They will be able to
easily switch between different compilers without having to modify
their projects build system or make non-standard changes to their
Fedora system.
== Dependencies ==
This change has no other dependencies besides the changes to the gcc
and clang packages.
== Contingency Plan ==
* Contingency mechanism: (What to do? Who will do it?) Proposal Owner
will revert changes made to gcc and clang packages and rebuild.
* Contingency deadline: If the changes are not complete by 2 weeks
before the mass rebuild, then we will consider postponing to the next
Fedora release and back out any changes that were made.
* Blocks release? No
* Blocks product? None
== Documentation ==
Release notes will be added for this change.
== Release Notes ==
The user /usr/bin/cc and /usr/bin/c++ symlinks are now managed by
update-alternatives. If you would like to change these symlinks to
point to another compiler, like clang, for example, you can use these
commands:
`update-alternatives --set cc /usr/bin/clang`
`update-alternatives --set c++ /usr/bin/clang++`
--
Ben Cotton
He / Him / His
Fedora Program Manager
Red Hat
TZ=America/Indiana/Indianapolis
Hello to everyone,
My name is Joerg Kastning and I'm a Sysadmin who is currently working for the Bielefeld University.
On my carreer counter I have round about 15 years of expierience as Sysadmin, DevOp and IT Project Manager. Using Linux since 2009 as a user and working with it as a professional (more or less) since 2012. Some of my Open Source Projects and the ones I have contributed to, you could find at [0].
At the office I'm using Timewarrior (timew) to track the time I spend on different topics. And it came to my mind that it would be nice to package this software to be able to install it using the package manager that I know. And why build the package only for me when I could build it could get it into an official repository?
So I did some reading [1] and have found Ankur who maintains timew for Fedora. I've told him that I'm eager to learn the bits of package building and maintainig and he agreed coaching me to become a co-maintainer for timew. And here I am. Looking forward to learn new things about the operating system I enjoy.
Best regards,
Joerg
[0] https://github.com/Tronde
[1] https://fedoraproject.org/wiki/Join_the_package_collection_maintainers
The Minimization Objective[1] has been going on for a while. There are two
high-level goals: making things smaller, and keeping things smaller. On the
keeping smaller side, the team prototyped a service called Feedback
Pipeline [2] that monitors use cases for their installation size and
dependencies, including a size history. This will help us see bigger
changes in size for things the community cares about [3].
I already got some feedback from a few individuals I asked while developing
it, but I feel it's in a good enough state for a more broad feedback. So I
have a few questions:
1/ We plan to send weekly size updates to the devel list. Would that be
useful? What should they include?
2/ Regarding the use cases [4], especially the container ones, could people
please review and give feedback to those? Are all the packages there
actually required? I'm specifically looking at the "nss_wrapper" package
that drags in Perl and cmake which makes it huge.
3/ Are there any other use cases we should track? I'm sure there are!
4/ And a more general one: is there something you're working on that's
related Minimization? Please let me know.
Cheers,
Adam
PS: The service is a prototype, so please excuse if there are some rough
edges — like the history graph showing multiple values of the same color.
If you happen to be interested to contribute, I'd be glad to accept issues
(or even PRs!) in the repo [5].
[1] Objective: https://docs.fedoraproject.org/en-US/minimization/
[2] Feedback Pipeline: https://minimization.github.io
<https://minimization.github.io/reports/>\
[3] Things the community cares about: There is an initial list [4] of use
cases defined by the Minimization Team, and we're now looking for feedback
and suggestions for new ones.
[4] Use cases:
https://minimization.github.io/reports/view--use-cases-definitions.html
[5] Feedback Pipeline repo:
https://github.com/minimization/feedback-pipeline/
--
Adam Šamalík
---------------------------
Senior Software Engineer
Red Hat