[haiku-depot-web] Re: depot.haiku-os.org stuck on 2019-06-09
- From: "Alexander von Gluck IV" <kallisti5@xxxxxxxxxxx>
- To: haiku-depot-web@xxxxxxxxxxxxx
- Date: Thu, 18 Jul 2019 13:25:12 +0000
July 18, 2019 7:11 AM, "Humdinger" <dmarc-noreply@xxxxxxxxxxxxx> wrote:
On 2019-07-18 at 10:59:28 [+0200], Andrew Lindesay <apl@xxxxxxxxxxxxxx>
wrote:
On Tue, 9 Jul 2019, at 04:03, Humdinger wrote:
Last update at https://depot.haiku-os.org is from 2019-06-09.
Is some update process stuck somewhere?
I am unable to see in the logs, but from a test system locally I see...
[...]
* repo sources "haikuports_x86_gcc2" and "haikuports_x86_64" seem to be
importing OK.
Weird. At HDS the latest update is still:
libutf8proc_x86_devel 1.3.1~3-3 2019-06-09 22:17:34
I checked haikuports buildmaster repository on disk..
[root@walter packages]# ls -la libutf8proc_x86_devel*
-rw-r--r-- 2 root root 87412 Jun 9 19:53
libutf8proc_x86_devel-1.3.1~3-3-x86_gcc2.hpkg
Good luck trying to find the status of latest build of libutf8prod in the
buildmaster
gui.
https://build.haiku-os.org/buildmaster/master/x86_gcc2/
ahahahahahhaahahahaahaha(random UTF8 characters).
(kallisti5 short circuits dies inside pointing at his inferior build system:
https://github.com/kallisti5/haikeuken/blob/master/docs/screenshot_recipe_info.png)
... ok. Rebooted.
After much searching and grepping...
/var/lib/docker/volumes/buildmaster_data_master_x86_gcc2/_data/haikuports/buildmaster/output/builds
Here are all the relevant build attempts:
# grep -R "building port libutf8proc" *.log
25672.log:building port libutf8proc_x86-1.3.1~3
28035.log:building port libutf8proc_x86-1.3.1~3
32682.log:building port libutf8proc_x86-1.3.1~3
32830.log:building port libutf8proc2_x86-2.4.0
5865.log:building port libutf8proc_x86-1.3.1~3
743.log:building port libutf8proc_x86-1.3.1~2
You can look up those build id's in
https://build.haiku-os.org/buildmaster/master/x86_gcc2/
so, looks like "haikuporter buildmaster" hasn't built anything newer than
libutf8proc_x86-1.3.1~3
(unless you're looking for libutf8proc2 instead?)
-- Alex
Other related posts:
