#16149: HaikuDepot doesn't shows packages from all other repos
--------------------------------------+----------------------------
Reporter: lorglas | Owner: apl-haiku
Type: bug | Status: new
Priority: normal | Milestone: Unscheduled
Component: Applications/HaikuDepot | Version: R1/Development
Resolution: | Keywords:
Blocked By: | Blocking:
Platform: All |
--------------------------------------+----------------------------
Comment (by apl-haiku):
The issue has been caused by change
e31b3cb943b1e05393b3e3e7565dd65a3404735f together with the data in the
HPKR file. Inside the HPKR is a serialized {{{BMessage}}} that contains a
{{{BRepositoryInfo}}} and inside this data is a value for the key
{{{url}}};
{{{
<http://haiku.kacperkasper.pl/repo/x86_64>
}}}
Note the "<" and ">" are the problem here because the change is taking the
{{{url}}} key to be the {{{identifier}}} and then taking the
{{{identifier}}} to be the {{{baseUrl}}} and then it checks to make sure
that the {{{baseUrl}}} starts with "http", but this does not; it starts
with "<" and so it fails to read.
The same applies to the Clasqm repository which has a value of;
{{{
<http://clasquin-Johnson.co.za/michel/repo>
}}}
I think if you make the {{{url}}} in the HPKR a well-formed "http" URL
then it will most likely work again.
---
Adrien; A couple of questions...
Would it be a good idea to also write the {{{identifier}}} into the
{{{BMessage}}} in {{{BRepositoryInfo::Archive(..)}}} so that in the future
the {{{BMessage}}} is populated with this field?
In {{{BRepositoryInfo::_SetTo}}} things can go wrong (as is the case in
this ticket) and there is no way for the user to know what happened and no
way for somebody technical to diagnose what is wrong without code-level
debugging. What is the best way to signal the problem -- {{{fprintf}}}
statements to stderr or should it return kit-specific error codes?
--
Ticket URL: <https://dev.haiku-os.org/ticket/16149#comment:13>
Haiku <https://dev.haiku-os.org>
The Haiku operating system.
