From: "Alexander von Gluck IV" <kallisti5@unixzen.com>
To: "Philippe Mathieu-Daudé" <philmd@linaro.org>,
"Thomas Huth" <thuth@redhat.com>
Cc: qemu-devel@nongnu.org
Subject: Re: [PATCH] tests/vm: Update haiku test vm to R1/Beta3
Date: Fri, 13 Jan 2023 14:20:22 +0000 [thread overview]
Message-ID: <5cb4fd7bbcd0d539fc9430e45fe14fe2@unixzen.com> (raw)
In-Reply-To: <27512349-0007-11bd-07fb-5fd8c3dae879@linaro.org>
January 13, 2023 7:30 AM, "Philippe Mathieu-Daudé" <philmd@linaro.org> wrote:
> On 13/1/23 12:05, Philippe Mathieu-Daudé wrote:
>
>> On 14/12/22 11:47, Thomas Huth wrote:
>>> On 16/02/2022 16.42, Alexander von Gluck IV wrote:
>>
>> ---
>> tests/vm/haiku.x86_64 | 8 ++++----
>> 1 file changed, 4 insertions(+), 4 deletions(-)
>>> [...]
>>
>> @@ -48,8 +48,8 @@ class HaikuVM(basevm.BaseVM):
>> name = "haiku"
>> arch = "x86_64"
>> - link = >>>
>> "https://app.vagrantup.com/haiku-os/boxes/r1beta2-x86_64/versions/20200702/providers/libvirt.box"
>> - csum = >>> "41c38b316e0cbdbc66b5dbaf3612b866700a4f35807cb1eb266a5bf83e9e68d5"
>> + link = >>>
>> "https://app.vagrantup.com/haiku-os/boxes/r1beta3-x86_64/versions/20220216/providers/libvirt.box"
>> + csum = >>> "e67d4aacbcc687013d5cc91990ddd86cc5d70a5d28432ae2691944f8ce5d5041"
>>> Hi Alexander!
>>>
>>> The Haiku VM started again to fail, I'm getting these error messages now:
>>>
>>> Encountered problems:
>>> problem 1: nothing provides haiku>=r1~beta4_hrev56578_4-1 needed by >> glib2_devel-2.75.0-1
>>> solution 1:
>>> - do not install "providing devel:libglib_2.0"
>>> problem 2: nothing provides haiku>=r1~beta4_hrev56578_31-1 needed by >> gettext-0.21.1-2
>>> solution 1:
>>> - do not install "providing devel:libintl"
>>> problem 3: nothing provides haiku>=r1~beta4_hrev56578_31-1 needed by >> curl-7.85.0-2
>>> solution 1:
>>> - do not install "providing devel:libcurl"
>>> problem 4: nothing provides haiku>=r1~beta4_hrev56578_31-1 needed by >> gnutls-3.7.8-1
>>> solution 1:
>>> - do not install "providing devel:libgnutls"
>>> problem 5: nothing provides haiku>=r1~beta4_hrev56578_4-1 needed by >> glib2-2.75.0-1
>>> solution 1:
>>> - do not install "providing devel:libslirp"
>>>
>>> Does it need an update to a newer version of Haiku?
>>
>> Per https://www.haiku-os.org/guides/daily-tasks/updating-system we
>> can keep the box image in sync with its repo by using:
>> # pkgman add https://eu.hpkg.haiku-os.org/haiku/r1beta3/$(getarch)/current
>> I will try this:
>> -- >8 --
>> diff --git a/tests/vm/haiku.x86_64 b/tests/vm/haiku.x86_64
>> index 29668bc272..9cbb46cfc1 100755
>> --- a/tests/vm/haiku.x86_64
>> +++ b/tests/vm/haiku.x86_64
>> @@ -112,2 +112,4 @@ class HaikuVM(basevm.BaseVM):
>> # Install packages
>> + self.ssh_root("pkgman add > https://eu.hpkg.haiku-os.org/haiku/r1beta3/x86_64/current")
>> + self.ssh_root("pkgman full-sync")
>> self.ssh_root("pkgman install -y %s" % " > ".join(self.requirements))
>> ---
>
> OS installed but is not usable...:
>
> runtime_loader: /boot/system/lib/libncurses.so.6.3.0: Could not resolve symbol '__ctype_b_loc'
> resolve symbol "__ctype_b_loc" returned: -2147478780
> runtime_loader: /boot/system/lib/libncurses.so.6.3.0: Troubles relocating: Symbol not found
> Connection to 127.0.0.1 closed.
Good morning!
I'll work on this one.
r1/beta4 came out a few weeks ago and I need to update the Vagrant image these are based on.
-- Alex
next prev parent reply other threads:[~2023-01-13 14:34 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-16 15:42 [PATCH] tests/vm: Update haiku test vm to R1/Beta3 Alexander von Gluck IV
2022-02-16 16:26 ` Thomas Huth
2022-02-16 16:26 ` Thomas Huth
2022-02-16 18:12 ` Alexander von Gluck IV
2022-02-16 18:12 ` Alexander von Gluck IV
2022-02-21 8:15 ` Thomas Huth
2022-02-21 8:15 ` Thomas Huth
2022-12-14 10:47 ` Thomas Huth
2023-01-13 11:05 ` Philippe Mathieu-Daudé
2023-01-13 13:30 ` Philippe Mathieu-Daudé
2023-01-13 14:20 ` Alexander von Gluck IV [this message]
2023-01-14 22:47 ` Alexander von Gluck IV
2023-01-16 8:19 ` Thomas Huth
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=5cb4fd7bbcd0d539fc9430e45fe14fe2@unixzen.com \
--to=kallisti5@unixzen.com \
--cc=philmd@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=thuth@redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.