Hi dnf and libsolv developers,
this mail is a continuation of an FPC  and a FESCo  tickets.
A proposal was made is to disallow packages in Fedora from using file
deps, and to optimize dnf to not load filelists.xml. File deps would
still be supported, because external packages and users want to use
them, but they would not be allowed for distro packages.
Not downloading or loading filelists.xml which are required for file
deps would provide significant bandwidth savings (~47 MB compressed)
and noticeable runtime savings (~10s at dnf startup) in many common
So this is something that is worth exploring, but it's not clear if it
is at all feasible. It seems that dnf would need to support loading
filelists.xml lazily. In the mailing list discussions, some people
said that this would be hard, some people said that it would be
possible… What is the situation here? IIUC, dnf would need to restart
the resolution of a transaction mid-flight once it encounters a file dep,
which would require support across the different layers.
If Fedora commits to making use of this, would it be possible to
implement this in dnf? What kind of changes would be required?
Zbyszek, on behalf of FESCo (but not that this writeup is based
on my understanding, so all errors are mine.)
On 2018-08-24 01:27 PM, Ben Cotton wrote:
> Hi design team,
> Today we have reached the Beta Wallpapers deadline for Fedora 29. The
> schedule has until 27 August to finish packaging. The packaging
> needs to be finished before Beta Freeze of the F28 release, which is
> planned on Tue 2018-08-28.
>  https://fedorapeople.org/groups/schedule/f-29/f-29-design-tasks.html
Packaged f29-backgrounds ready for review:
Should I be unable to push the package into the repository after the
review, someone makes sure to update desktops-backgrounds as well.
Thanks in advance.
Graphic & Web Designer
The container effort in Fedora has until now been looked after by the
Atomic WG, since this Working Group is now going to focus mostly on
Fedora CoreOS, I propose to create a new container SIG to regroup
people interested in the maintenance of application containers in
This SIG would look after the container guidelines , the container
review process  and also the release process and tooling.
Please Reply if you're interested with helping out making the
Container story great in Fedora. If there is a good response, I will
create a Container SIG wiki page, and I guess we can ask for
container-devel mailing list for SIG discussions.
 - https://fedoraproject.org/wiki/Container:Guidelines
 - https://fedoraproject.org/wiki/Container:Review_Process