On Fri, 2020-12-04 at 16:11 +0100, Marius Schwarz wrote:
Hi,
as you may have heared, Fedora is now running on Pinephone and other
devices, that need bleeding edge versions to function.
Status of Fedora Pine as of 15:15 CET
Cams now working, but app needs rework
Mobile INET working
WIFI working
Touch working
SMS working
GPS working
Calls partly, "calls app" does not connect to pulseaudio.
Headphones ( sort of )
Mali400 GPU support working ( MPV rulez )
and with Gnome(38) instead of Phosh.. no window problems! Big Thanks to
nikhiljha <
https://github.com/nikhiljha>and his copr repo.
O== my request
In the last 3 days alone several updates ( i.e. bind-libs, gnome-shell
40~alpha ) caused a lot of bugs and needed to be downgraded directly
from koji,
by first finding & downloading them with wget ( because of the slow wifi
and dependency checks, direct http links work ofcourse ), and later
downgraded with
dnf, which is so to speak, a pain in the ass. Of course, the best way to
handle it would be, if the os compenents came from stable repos, so that
these problems do not happen. But as i said, bleeding edge is needed atm.
Is it possible to keep at least the last version of a package around in
rawhide repo, to make dnf downgrade work? That would ease a lot of this
pain.
I know that there is a native koji tool to handle rawhide, but i must
say, that won't work in most cases. Let me explain:
Pine has announced to open stores in the US and Canada, because of the
huge amount of requests for a pinephone. As it looks, this phone, as
cheap as it compontants are, fills a gap of some kind. Therefor we will
have much more user using it, and (i hope i can help with it) will use
Fedora with Gnome-Shell.
Phosh is more like Android, it has it charm, but tbh I, and people I
showned it to, love they way gnome-shell handles stuff.
We "may" get them to downgrade stuff with dnf, but that needs to be as
simple as it could.
I don't think there's an easy way to do this, because of how we build
stuff. The Rawhide and Branched trees are rsynced over top of the
previous content from the most recent successful compose, with metadata
pre-built at the compose level. The old thing is thrown away and
replaced with the new thing, which is a very simple process.
If you want to keep old stuff around it suddenly gets a ton more
complex, because now you have to keep track of what is "old stuff" and
when to get rid of it, and you have to add a step to the process that
(re-)generates the repo metadata after the new stuff has been added to
the old stuff.
Limited downgrading possibilities exist for stable releases because we
freeze those and add updates repos alongside the frozen stable release,
but that's not how we build development releases.
I don't really think it makes sense to do a ton of engineering to
support an explicitly non-recommended use case. Rawhide is not for
running on your phone.
Having said that, there are more efficient ways to do what you're
doing. You don't need to download with wget; you can use the 'koji' CLI
tool directly (koji download-build --arch=XX --arch=noarch NVR). You
can also find the older Rawhide content in older composes, at
https://kojipkgs.fedoraproject.org/compose/rawhide/ - you can configure
the Everything repo from any of those as a local repo and its content
will be available for downgrading. Of course, that server doesn't
expect heavy traffic, so if lots of pinephone people start trying to do
it at once, it might start choking.
--
Adam Williamson
Fedora QA
IRC: adamw | Twitter: adamw_ha
https://www.happyassassin.net