https://git.openrobots.org/https://git.openrobots.org/favicon.ico?14752240372023-01-23T08:51:02ZOpenrobotsrobotpkg - Bug #377: apt packages missinghttps://git.openrobots.org/issues/377?journal_id=10732023-01-23T08:51:02ZGuilhem Saurel
<ul></ul><p>I triggered a rebuild, in case this was transient.</p> robotpkg - Bug #377: apt packages missinghttps://git.openrobots.org/issues/377?journal_id=10742023-01-23T09:00:26ZAnthony Malletanthony.mallet@laas.fr
<ul></ul><p>There were issues during the last bulk build: the main server storage<br />was full and this eventually led to the bulk report database<br />corruption. (and one distfile corruption as you may have seen in the report).</p>
<p>I repaired the database and the distfile but a few entries have been<br />lost, this should recover by itself when packages are rebuilt,<br />although without an explcit change they wont be rebuilt automatically<br />(only if some dependencies change).</p>
<p>I will check if there are still issues for omniORB.</p>
<p>The timeouts and exit 2 are a different thing: systemd does not always<br />properly start the bulk daemon for some reason (usually it does not<br />find the ldap user or the remote filesystem), although the service<br />file mentions "after remote_fs" and network online etc. If you know a<br />magic way to debug this ... :)</p> robotpkg - Bug #377: apt packages missinghttps://git.openrobots.org/issues/377?journal_id=10752023-01-23T12:43:30ZAnthony Malletanthony.mallet@laas.fr
<ul><li><strong>Status</strong> changed from <i>New</i> to <i>Feedback</i></li></ul><p>It seems that the Release files were also impacted by the ENOSPC<br />error. I manually rebuilt the apt repository, robotpkg-py38-omniorbpy<br />is now found. (You may need to apt-update).</p>
<p>Is it fixed for you?</p> robotpkg - Bug #377: apt packages missinghttps://git.openrobots.org/issues/377?journal_id=10782023-01-24T10:17:26ZGuilhem Saurel
<ul><li><strong>Status</strong> changed from <i>Feedback</i> to <i>Closed</i></li></ul><p>Everything looks good for me now, thanks !</p>