[haiku-bugs] Re: [Haiku] #14927: HaikuDepot doesn't show any packages
- From: "Haiku" <trac@xxxxxxxxxxxx>
- To: undisclosed-recipients: ;
- Date: Mon, 18 Nov 2019 08:52:47 -0000
#14927: HaikuDepot doesn't show any packages
---------------------------------------+----------------------------
Reporter: KapiX | Owner: apl-haiku
Type: bug | Status: reopened
Priority: normal | Milestone: Unscheduled
Component: Applications/HaikuDepot | Version: R1/Development
Resolution: | Keywords:
Blocked By: | Blocking:
Has a Patch: 0 | Platform: All
---------------------------------------+----------------------------
Comment (by apl-haiku):
1 What website could the alert point users
I am not aware of there being such a web page at this point in time. In
retrospect this would have been a good idea -- or a blog post or
something. I think I did post in a mailing list, but I don't recall.
2 Is it likely that the URL currently used as identifier at least for
HaikuPorts and Haiku will ever change again?
I hope not, but I am not too sure; Alex would be best placed to answer
this question. I hope not!
... fuzzy logic to automatically fix this situation without the user
becoming aware of it?
I guess as Adrien mentioned it would be possible to hard-code former
repository "url" values in there and have some sort of mapping old-to-new.
Probably safer would be an instructional web page.
... The featured packages are still empty ...
I did not appreciate that this issue is causing the "all packages list" to
fail as well -- HD should definitely handle this case so that the "all
packages list" will work even if this problem happens. The "all packages
list" should be displaying even if there is no "url" (identifier) because
the "url" should only be required to marry-up the data on-host with the
data from HDS. Probably some handling needs to be corrected that can cope
with a missing "url" for "all packages list".
Because the icon data is common across all repositories, the icons will be
loading fine even if the "url" is corrupted.
It is not surprising that the "featured packages" is empty because HD will
be unable to correlate data from HDS and thus will be unable to find out
which packages are currently "featured". In this sort of situation where
there are no "featured" packages, maybe it is best to disable this mode?
... What was rejected is breaking the repository format, and preventing
seamless upgrades. ...
If an "identifier" with a UUID were added into the "repo.info" file in the
repository then the HPKR update operation could be amended to update the
"identifier" when it refreshes if it is missing locally. After 6-12
months it would probably be possible to make this change without impacting
too many people. It would be some work to achieve this.
... This has, however, no impact on how we name things ...
Previous to this change, it was very confusing having multiple uses for
the term "url" and also different terms for this conceptual "identifier".
At the moment the term "url" is consistent in the HDS database, the HDS
source, the HDS API signatures, the HD source, the package library and
through the {{{repo.info}}} file. Somebody can trace it from start to
finish by name and that is of significant value for maintenance. It was
quite a bit of work to achieve that so I would be averse to renaming
anything without ensuring follow-through to ensure the work were done
consistently across both data and software.
... and not some man-in-the-middle trying to add malware to your install
That is a good point.
Still, base-url and url are not, in general, interchangeable. base-url
is where ...
Yes that is correct.
--
Ticket URL: <
https://dev.haiku-os.org/ticket/14927#comment:13>
Haiku <
https://dev.haiku-os.org>
The Haiku operating system.
Other related posts:
